- open browser가 검색이 안되고 use application/broswer만 검색이 됩니다. - 다른 템플릿에서 open browser를 긁어왔는데 click이 "opening.xaml: 타겟 또는 입력 UI 엘리먼트를 설정해야 합니다."라는 오류 메시지와 함께 설정이 안됩니다. 해결 방법이 무엇이 있을까요?
Win32Exception: ApplicationName='C:\Program Files\Unity\Editor\Data\Tools\RoslynScripts\unity_csc.bat', CommandLine='/noconfig @Temp/UnityTempFile-ba6ab091483534d4c8005ffa081b9d1f', CurrentDirectory='', Native error= 지정된 파일을 찾을 수 없습니다. 유니티를 실행하면 자동적으로 이 오류 메시지가 뜨면서 오브젝트에 스크립트를 붙일 수가 없습니다. can't add scripts 뜨면서 거부되네요 ㅜㅜ 혹시 해결법이 있을 까요? 아무리 찾아봐도 못 찾겠어서;;;; 재부팅해도 해결 안되고 유니티를 재설치 해도 해결이 안됩니다;;;
지금에서야 듣는데 설치 에러가 자꾸 떠서 고민중에 버전을 최신버전으로 자동 설치한다면 어떨까라는 의문에 구글링하고 뒤에 버전 정보를 지우면 최신 버전으로 자동으로 찾아준다고 합니다 아래와 같이 requirements.txt를 변경했습니다 pandas numpy seaborn matplotlib finance-datareader ipython 완강까지 쉴새없이 달려보겠습니다!
아래 같은 오류가 떠요... 오토컴플릿-파이썬 디스에이블 하면 아나뜨구요..왜이런걸까요..? - 학습 관련 질문을 남겨주세요. 상세히 작성하면 더 좋아요! - 먼저 유사한 질문이 있었는지 검색해보세요. - 서로 예의를 지키며 존중하는 문화를 만들어가요. - 잠깐! 인프런 서비스 운영 관련 문의는 1:1 문의하기를 이용해주세요.
안녕하세요 열심히 수강하고 있는 수강생입니다. Local 환경에서 설치 하고 테스트 하다보니 회사 내 보안적인 이슈 때문에 테스트가 쉽지 않아 구글 클라우드 플랫폼 환경에서 VM을 이용하여 마스터 서버와 work 노드를 구성하려고 합니다. 알려주신 절차대로 수행 중에 kubeadm init를 수행하면 아래와 같은 오류가 발생합니다. 여러번 반복해 보았는데도 오류가 계속 발생되는데 도움이 될 만한 사항이 있으면 알려주세요.. ps) 내부적인 보안 때문에 네트워크 문제가 아닌가 의심은 가는데 어떻게 조치를 해야 되는지 알 수가 없네요. 감사합니다. ======================================================================== Hit:2 http://asia-northeast3.gce.archive.ubuntu.com/ubuntu bionic InRelease Hit:3 http://asia-northeast3.gce.archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:4 http://asia-northeast3.gce.archive.ubuntu.com/ubuntu bionic-backports InRelease Hit:1 https://packages.cloud.google.com/apt kubernetes-xenial InRelease Get:5 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB] Fetched 88.7 kB in 1s (72.9 kB/s) Reading package lists... Done Reading package lists... Done Building dependency tree Reading state information... Done curl is already the newest version (7.58.0-2ubuntu3.14). apt-transport-https is already the newest version (1.6.14). The following package was automatically installed and is no longer required: libnuma1 Use 'sudo apt autoremove' to remove it. 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. OK deb https://apt.kubernetes.io/ kubernetes-xenial main Hit:1 http://asia-northeast3.gce.archive.ubuntu.com/ubuntu bionic InRelease Hit:2 http://asia-northeast3.gce.archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:3 http://asia-northeast3.gce.archive.ubuntu.com/ubuntu bionic-backports InRelease Hit:4 https://packages.cloud.google.com/apt kubernetes-xenial InRelease [etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests" [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s [kubelet-check] Initial timeout of 40s passed. [kubelet-check] It seems like the kubelet isn't running or healthy. [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: conn ect: connection refused. [kubelet-check] It seems like the kubelet isn't running or healthy. [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: conn ect: connection refused. [kubelet-check] It seems like the kubelet isn't running or healthy. [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: conn ect: connection refused. [kubelet-check] It seems like the kubelet isn't running or healthy. [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: conn ect: connection refused. [kubelet-check] It seems like the kubelet isn't running or healthy. [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp 127.0.0.1:10248: conn ect: connection refused. Unfortunately, an error has occurred: timed out waiting for the condition This error is likely caused by: - The kubelet is not running - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled) If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands: - 'systemctl status kubelet' - 'journalctl -xeu kubelet' Additionally, a control plane component may have crashed or exited when started by the container runtime. To troubleshoot, list all containers using your preferred container runtimes CLI. Here is one example how you may list all Kubernetes containers running in docker: - 'docker ps -a | grep kube | grep -v pause' Once you have found the failing container, you can inspect its logs with: - 'docker logs CONTAINERID' error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster To see the stack trace of this error execute with --v=5 or higher root@kube-master-1:~#
- 학습 관련 질문을 남겨주세요. 상세히 작성하면 더 좋아요! - 먼저 유사한 질문이 있었는지 검색해보세요. - 서로 예의를 지키며 존중하는 문화를 만들어가요. - 잠깐! 인프런 서비스 운영 관련 문의는 1:1 문의하기를 이용해주세요. 더운 여름에도 좋은 강의제공해주셔서 항상 감사합니다 선생님. 집에 F103RB이 없고 L053R8이 있어 이 보드로 RTOS 실습을 진행하고자 합니다. 첫 예제인 '01.TASKMAN'을 디버깅 하던 도중 Error! Failed to read target status Debugger connection lost. Shutting down... 이라는 오류를 만나고 정상적으로 디버깅이 되지 않는 문제를 만났습니다. 해당 오류에 대해 구글링을 해봤지만, 마땅한 해결책이 나오지 않아 실습에 어려움을 겪고 있습니다. ST-LINK를 지웠다가 다시 설치해도 동일한 문제가 반복됩니다. CubeIDE의 'Build Analyzer'를 보니 빌드된 프로그램이 RAM을 18.35KB, flash는 17.3KB를 사용하는 것 같습니다. F103RB는 20KB SRAM 과 128KB flash를 가지고 있고, L053R8은 8KB SRAM 과 64KB flash를 가지고 있는데, 메모리 부족 때문에 디버깅 문제가 생기는 것일까요? Debug console 전문을 올립니다! 감사합니다! STMicroelectronics ST-LINK GDB server. Version 5.9.1 Copyright (c) 2021, STMicroelectronics. All rights reserved. Starting server with the following options: Persistent Mode : Disabled Logging Level : 31 Listen Port Number : 61234 Status Refresh Delay : 15s Verbose Mode : Enabled SWD Debug : Enabled InitWhile : Enabled COM frequency = 4000 kHz Target connection mode: Under reset Reading ROM table for AP 0 @0xf0000fd0 Hardware watchpoint supported by the target ST-LINK Firmware version : V2J38M27 Device ID: 0x417 PC: 0x8002ae8 ST-LINK device status: HALT_MODE ST-LINK detects target voltage = 3.26 V ST-LINK device status: HALT_MODE ST-LINK device initialization OK Waiting for debugger connection... Waiting for connection on port 61234... Waiting for connection on port 61235... Accepted connection on port 61234... Debugger connected ------ Switching to STM32CubeProgrammer ----- ------------------------------------------------------------------- STM32CubeProgrammer v2.8.0 ------------------------------------------------------------------- ST-LINK SN : 066DFF565653756687162247 ST-LINK FW : V2J38M27 Board : NUCLEO-L053R8 Voltage : 3.25V SWD freq : 4000 KHz Connect mode: Under Reset Reset mode : Hardware reset Device ID : 0x417 Revision ID : Rev X Device name : STM32L05x/L06x/L010 Flash size : 64 KBytes Device type : MCU Device CPU : Cortex-M0+ BL Version : 0x__ Memory Programming ... Opening and parsing file: ST-LINK_GDB_server_a05200.srec File : ST-LINK_GDB_server_a05200.srec Size : 17720 Bytes Address : 0x08000000 Erasing memory corresponding to segment 0: Erasing internal memory sectors [0 138] Download in Progress: �������������������������������������������������� 0% ������������� 26%������������� 52%������������� 78%����������� 100% File download complete Time elapsed during download operation: 00:00:01.752 Verifying ... Read progress: �������������������������������������������������� 50% ����� 11%������ 23%������ 34%������ 46%����� 57%������ 69%������ 80%������ 92%���� 100% Download verified successfully ------ Switching context ----- COM frequency = 4000 kHz Target connection mode: Under reset Reading ROM table for AP 0 @0xf0000fd0 Hardware watchpoint supported by the target ST-LINK Firmware version : V2J38M27 Device ID: 0x417 PC: 0x8002ae8 ST-LINK detects target voltage = 3.26 V ST-LINK device status: HALT_MODE ST-LINK device initialization OK SWV poll delay set to 3413µs for baudrate 0Hz Accepted connection on port 61235... handle_vCont_c, continue thread ST-LINK device status: LOCKUP Enter STM32_SystemReset() function NVIC_DFSR_REG = 0x0000000B NVIC_CFGFSR_REG = 0x00000000 Error! Failed to read target status Debugger connection lost. Shutting down... Stopping port 61235