1.5버전 실습환경 구축을 위해 Virtual box와 vagrant 설치 후 공유해 주신 1.5버전 설치 중 에러가 계속 발생하여 Virtualbox와 vagrant를 재설치 해 보았으나, 여전히 동일한 문제가 발생합니다. 혹시 문제 해결에 도움을 주실 수 있을지 문의 드립니다. 문제된 화면 캡쳐 올려 드립니다. Microsoft Windows [Version 10.0.18362.1256] (c) 2019 Microsoft Corporation. All rights reserved. C:\Users\Administrator>cd \ C:\>cd hashicorp C:\HashiCorp>dir/w C 드라이브의 볼륨에는 이름이 없습니다. 볼륨 일련 번호: 5A62-A4BD C:\HashiCorp 디렉터리 [.] [..] [Vagrant] [_Lecture_k8s_learning.kit-main] _Lecture_k8s_learning.kit-main.zip 1개 파일 438,711 바이트 4개 디렉터리 66,036,817,920 바이트 남음 C:\HashiCorp>cd _Lecture_k8s_learning.kit-main C:\HashiCorp\_Lecture_k8s_learning.kit-main>dir C 드라이브의 볼륨에는 이름이 없습니다. 볼륨 일련 번호: 5A62-A4BD C:\HashiCorp\_Lecture_k8s_learning.kit-main 디렉터리 2021-10-06 오후 01:48 <DIR> . 2021-10-06 오후 01:48 <DIR> .. 2021-10-05 오전 01:00 9 .gitignore 2021-10-06 오후 01:46 <DIR> A 2021-10-06 오후 01:46 <DIR> ch1 2021-10-06 오후 01:46 <DIR> ch2 2021-10-06 오후 01:46 <DIR> ch3 2021-10-06 오후 01:46 <DIR> ch4 2021-10-06 오후 01:46 <DIR> ch5 2021-10-06 오후 01:46 <DIR> ch6 2021-10-06 오후 01:46 <DIR> ch7 2021-10-06 오후 01:46 <DIR> ch8 2021-10-06 오후 01:46 <DIR> ch9 2021-10-05 오전 01:00 1,472 README.md 2개 파일 1,481 바이트 12개 디렉터리 66,036,817,920 바이트 남음 C:\HashiCorp\_Lecture_k8s_learning.kit-main>cd ch1 C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1>dir C 드라이브의 볼륨에는 이름이 없습니다. 볼륨 일련 번호: 5A62-A4BD C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1 디렉터리 2021-10-06 오후 01:46 <DIR> . 2021-10-06 오후 01:46 <DIR> .. 2021-10-06 오후 01:46 <DIR> 1.5 2021-10-06 오후 01:46 <DIR> 1.6 2021-10-05 오전 01:00 182 README.md 1개 파일 182 바이트 4개 디렉터리 66,036,817,920 바이트 남음 C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1>cd 1.5 C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1\1.5>dir/w C 드라이브의 볼륨에는 이름이 없습니다. 볼륨 일련 번호: 5A62-A4BD C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1\1.5 디렉터리 [.] [..] [k8s-min-5GiB-wo-add-nodes] Sessions(k8s_learning).XML 1개 파일 1,373 바이트 3개 디렉터리 66,036,822,016 바이트 남음 C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1\1.5>cd k8s-min-5GiB-wo-add-nodes C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1\1.5\k8s-min-5GiB-wo-add-nodes>dir C 드라이브의 볼륨에는 이름이 없습니다. 볼륨 일련 번호: 5A62-A4BD C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1\1.5\k8s-min-5GiB-wo-add-nodes 디렉터리 2021-10-06 오후 01:46 <DIR> . 2021-10-06 오후 01:46 <DIR> .. 2021-10-05 오전 01:00 1,395 k8s_env_build.sh 2021-10-05 오전 01:00 475 k8s_pkg_cfg.sh 2021-10-05 오전 01:00 524 k_cfg_n_git_clone.sh 2021-10-05 오전 01:00 2,275 Vagrantfile 4개 파일 4,669 바이트 2개 디렉터리 66,036,707,328 바이트 남음 C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1\1.5\k8s-min-5GiB-wo-add-nodes>dir/w C 드라이브의 볼륨에는 이름이 없습니다. 볼륨 일련 번호: 5A62-A4BD C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1\1.5\k8s-min-5GiB-wo-add-nodes 디렉터리 [.] [..] k8s_env_build.sh k8s_pkg_cfg.sh k_cfg_n_git_clone.sh Vagrantfile 4개 파일 4,669 바이트 2개 디렉터리 66,036,707,328 바이트 남음 C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1\1.5\k8s-min-5GiB-wo-add-nodes>vagrant up Bringing machine 'WO-m-k8s-1.20' up with 'virtualbox' provider... Bringing machine 'WO-w1-k8s-1.20' up with 'virtualbox' provider... Bringing machine 'WO-w2-k8s-1.20' up with 'virtualbox' provider... Bringing machine 'WO-w3-k8s-1.20' up with 'virtualbox' provider... ==> WO-m-k8s-1.20: Box 'sysnet4admin/CentOS-k8s' could not be found. Attempting to find and install... WO-m-k8s-1.20: Box Provider: virtualbox WO-m-k8s-1.20: Box Version: >= 0 ==> WO-m-k8s-1.20: Loading metadata for box 'sysnet4admin/CentOS-k8s' WO-m-k8s-1.20: URL: https://vagrantcloud.com/sysnet4admin/CentOS-k8s ==> WO-m-k8s-1.20: Adding box 'sysnet4admin/CentOS-k8s' (v0.7.4) for provider: virtualbox WO-m-k8s-1.20: Downloading: https://vagrantcloud.com/sysnet4admin/boxes/CentOS-k8s/versions/0.7.4/providers/virtualbox.box WO-m-k8s-1.20: ==> WO-m-k8s-1.20: Successfully added box 'sysnet4admin/CentOS-k8s' (v0.7.4) for 'virtualbox'! ==> WO-m-k8s-1.20: Importing base box 'sysnet4admin/CentOS-k8s'... ==> WO-m-k8s-1.20: Matching MAC address for NAT networking... ==> WO-m-k8s-1.20: Checking if box 'sysnet4admin/CentOS-k8s' version '0.7.4' is up to date... ==> WO-m-k8s-1.20: Setting the name of the VM: WO-m-k8s-1.20(github_SysNet4Admin) ==> WO-m-k8s-1.20: Clearing any previously set network interfaces... ==> WO-m-k8s-1.20: Preparing network interfaces based on configuration... WO-m-k8s-1.20: Adapter 1: nat WO-m-k8s-1.20: Adapter 2: hostonly ==> WO-m-k8s-1.20: Forwarding ports... WO-m-k8s-1.20: 22 (guest) => 60010 (host) (adapter 1) ==> WO-m-k8s-1.20: Running 'pre-boot' VM customizations... ==> WO-m-k8s-1.20: Booting VM... ==> WO-m-k8s-1.20: Waiting for machine to boot. This may take a few minutes... WO-m-k8s-1.20: SSH address: 127.0.0.1:60010 WO-m-k8s-1.20: SSH username: vagrant WO-m-k8s-1.20: SSH auth method: private key WO-m-k8s-1.20: Warning: Remote connection disconnect. Retrying... WO-m-k8s-1.20: Warning: Connection aborted. Retrying... WO-m-k8s-1.20: Warning: Remote connection disconnect. Retrying... WO-m-k8s-1.20: Warning: Remote connection disconnect. Retrying... WO-m-k8s-1.20: Warning: Connection aborted. Retrying... WO-m-k8s-1.20: WO-m-k8s-1.20: Vagrant insecure key detected. Vagrant will automatically replace WO-m-k8s-1.20: this with a newly generated keypair for better security. WO-m-k8s-1.20: WO-m-k8s-1.20: Inserting generated public key within guest... WO-m-k8s-1.20: Removing insecure key from the guest if it's present... WO-m-k8s-1.20: Key inserted! Disconnecting and reconnecting using new SSH key... ==> WO-m-k8s-1.20: Machine booted and ready! ==> WO-m-k8s-1.20: Checking for guest additions in VM... ==> WO-m-k8s-1.20: Setting hostname... ==> WO-m-k8s-1.20: Configuring and enabling network interfaces... ==> WO-m-k8s-1.20: Running provisioner: shell... WO-m-k8s-1.20: Running: C:/Users/ADMINI~1/AppData/Local/Temp/vagrant-shell20211006-15576-1w8qnwz.sh WO-m-k8s-1.20: Loaded plugins: fastestmirror WO-m-k8s-1.20: Determining fastest mirrors WO-m-k8s-1.20: * base: mirror.kakao.com WO-m-k8s-1.20: * extras: mirror.kakao.com WO-m-k8s-1.20: * updates: mirror.kakao.com WO-m-k8s-1.20: Package yum-utils-1.1.31-54.el7_8.noarch already installed and latest version WO-m-k8s-1.20: Nothing to do WO-m-k8s-1.20: Loaded plugins: fastestmirror WO-m-k8s-1.20: adding repo from: https://download.docker.com/linux/centos/docker-ce.repo WO-m-k8s-1.20: grabbing file https://download.docker.com/linux/centos/docker-ce.repo to /etc/yum.repos.d/docker-ce.repo WO-m-k8s-1.20: repo saved to /etc/yum.repos.d/docker-ce.repo ==> WO-m-k8s-1.20: Running provisioner: shell... WO-m-k8s-1.20: Running: C:/Users/ADMINI~1/AppData/Local/Temp/vagrant-shell20211006-15576-e5eysz.sh WO-m-k8s-1.20: Loaded plugins: fastestmirror WO-m-k8s-1.20: Loading mirror speeds from cached hostfile WO-m-k8s-1.20: * base: mirror.kakao.com WO-m-k8s-1.20: * extras: mirror.kakao.com WO-m-k8s-1.20: * updates: mirror.kakao.com WO-m-k8s-1.20: Resolving Dependencies WO-m-k8s-1.20: --> Running transaction check WO-m-k8s-1.20: ---> Package epel-release.noarch 0:7-11 will be installed WO-m-k8s-1.20: --> Finished Dependency Resolution WO-m-k8s-1.20: WO-m-k8s-1.20: Dependencies Resolved WO-m-k8s-1.20: WO-m-k8s-1.20: ================================================================================ WO-m-k8s-1.20: Package Arch Version Repository Size WO-m-k8s-1.20: ================================================================================ WO-m-k8s-1.20: Installing: WO-m-k8s-1.20: epel-release noarch 7-11 extras 15 k WO-m-k8s-1.20: WO-m-k8s-1.20: Transaction Summary WO-m-k8s-1.20: ================================================================================ WO-m-k8s-1.20: Install 1 Package WO-m-k8s-1.20: WO-m-k8s-1.20: Total download size: 15 k WO-m-k8s-1.20: Installed size: 24 k WO-m-k8s-1.20: Downloading packages: WO-m-k8s-1.20: Running transaction check WO-m-k8s-1.20: Running transaction test WO-m-k8s-1.20: Transaction test succeeded WO-m-k8s-1.20: Running transaction WO-m-k8s-1.20: Installing : epel-release-7-11.noarch 1/1 WO-m-k8s-1.20: Verifying : epel-release-7-11.noarch 1/1 WO-m-k8s-1.20: WO-m-k8s-1.20: Installed: WO-m-k8s-1.20: epel-release.noarch 0:7-11 WO-m-k8s-1.20: WO-m-k8s-1.20: Complete! WO-m-k8s-1.20: Loaded plugins: fastestmirror WO-m-k8s-1.20: Loading mirror speeds from cached hostfile WO-m-k8s-1.20: WO-m-k8s-1.20: WO-m-k8s-1.20: One of the configured repositories failed (Unknown), WO-m-k8s-1.20: and yum doesn't have enough cached data to continue. At this point the only WO-m-k8s-1.20: safe thing yum can do is fail. There are a few ways to work "fix" this: WO-m-k8s-1.20: WO-m-k8s-1.20: 1. Contact the upstream for the repository and get them to fix the problem. WO-m-k8s-1.20: WO-m-k8s-1.20: 2. Reconfigure the baseurl/etc. for the repository, to point to a working WO-m-k8s-1.20: upstream. This is most often useful if you are using a newer WO-m-k8s-1.20: distribution release than is supported by the repository (and the WO-m-k8s-1.20: packages for the previous distribution release still work). WO-m-k8s-1.20: WO-m-k8s-1.20: 3. Run the command with the repository temporarily disabled WO-m-k8s-1.20: yum --disablerepo=<repoid> ... WO-m-k8s-1.20: WO-m-k8s-1.20: 4. Disable the repository permanently, so yum won't use it by default. Yum WO-m-k8s-1.20: will then just ignore the repository until you permanently enable it WO-m-k8s-1.20: again or use --enablerepo for temporary usage: WO-m-k8s-1.20: WO-m-k8s-1.20: yum-config-manager --disable <repoid> WO-m-k8s-1.20: or WO-m-k8s-1.20: subscription-manager repos --disable=<repoid> WO-m-k8s-1.20: WO-m-k8s-1.20: 5. Configure the failing repository to be skipped, if it is unavailable. WO-m-k8s-1.20: Note that yum will try to contact the repo. when it runs most commands, WO-m-k8s-1.20: so will have to try and fail each time (and thus. yum will be be much WO-m-k8s-1.20: slower). If it is a very temporary problem though, this is often a nice WO-m-k8s-1.20: compromise: WO-m-k8s-1.20: WO-m-k8s-1.20: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true WO-m-k8s-1.20: WO-m-k8s-1.20: Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again WO-m-k8s-1.20: Loaded plugins: fastestmirror WO-m-k8s-1.20: Loading mirror speeds from cached hostfile WO-m-k8s-1.20: WO-m-k8s-1.20: WO-m-k8s-1.20: One of the configured repositories failed (Unknown), WO-m-k8s-1.20: and yum doesn't have enough cached data to continue. At this point the only WO-m-k8s-1.20: safe thing yum can do is fail. There are a few ways to work "fix" this: WO-m-k8s-1.20: WO-m-k8s-1.20: 1. Contact the upstream for the repository and get them to fix the problem. WO-m-k8s-1.20: WO-m-k8s-1.20: 2. Reconfigure the baseurl/etc. for the repository, to point to a working WO-m-k8s-1.20: upstream. This is most often useful if you are using a newer WO-m-k8s-1.20: distribution release than is supported by the repository (and the WO-m-k8s-1.20: packages for the previous distribution release still work). WO-m-k8s-1.20: WO-m-k8s-1.20: 3. Run the command with the repository temporarily disabled WO-m-k8s-1.20: yum --disablerepo=<repoid> ... WO-m-k8s-1.20: WO-m-k8s-1.20: 4. Disable the repository permanently, so yum won't use it by default. Yum WO-m-k8s-1.20: will then just ignore the repository until you permanently enable it WO-m-k8s-1.20: again or use --enablerepo for temporary usage: WO-m-k8s-1.20: WO-m-k8s-1.20: yum-config-manager --disable <repoid> WO-m-k8s-1.20: or WO-m-k8s-1.20: subscription-manager repos --disable=<repoid> WO-m-k8s-1.20: WO-m-k8s-1.20: 5. Configure the failing repository to be skipped, if it is unavailable. WO-m-k8s-1.20: Note that yum will try to contact the repo. when it runs most commands, WO-m-k8s-1.20: so will have to try and fail each time (and thus. yum will be be much WO-m-k8s-1.20: slower). If it is a very temporary problem though, this is often a nice WO-m-k8s-1.20: compromise: WO-m-k8s-1.20: WO-m-k8s-1.20: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true WO-m-k8s-1.20: WO-m-k8s-1.20: Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again WO-m-k8s-1.20: Loaded plugins: fastestmirror WO-m-k8s-1.20: Loading mirror speeds from cached hostfile WO-m-k8s-1.20: WO-m-k8s-1.20: WO-m-k8s-1.20: One of the configured repositories failed (Unknown), WO-m-k8s-1.20: and yum doesn't have enough cached data to continue. At this point the only WO-m-k8s-1.20: safe thing yum can do is fail. There are a few ways to work "fix" this: WO-m-k8s-1.20: WO-m-k8s-1.20: 1. Contact the upstream for the repository and get them to fix the problem. WO-m-k8s-1.20: WO-m-k8s-1.20: 2. Reconfigure the baseurl/etc. for the repository, to point to a working WO-m-k8s-1.20: upstream. This is most often useful if you are using a newer WO-m-k8s-1.20: distribution release than is supported by the repository (and the WO-m-k8s-1.20: packages for the previous distribution release still work). WO-m-k8s-1.20: WO-m-k8s-1.20: 3. Run the command with the repository temporarily disabled WO-m-k8s-1.20: yum --disablerepo=<repoid> ... WO-m-k8s-1.20: WO-m-k8s-1.20: 4. Disable the repository permanently, so yum won't use it by default. Yum WO-m-k8s-1.20: will then just ignore the repository until you permanently enable it WO-m-k8s-1.20: again or use --enablerepo for temporary usage: WO-m-k8s-1.20: WO-m-k8s-1.20: yum-config-manager --disable <repoid> WO-m-k8s-1.20: or WO-m-k8s-1.20: subscription-manager repos --disable=<repoid> WO-m-k8s-1.20: WO-m-k8s-1.20: 5. Configure the failing repository to be skipped, if it is unavailable. WO-m-k8s-1.20: Note that yum will try to contact the repo. when it runs most commands, WO-m-k8s-1.20: so will have to try and fail each time (and thus. yum will be be much WO-m-k8s-1.20: slower). If it is a very temporary problem though, this is often a nice WO-m-k8s-1.20: compromise: WO-m-k8s-1.20: WO-m-k8s-1.20: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true WO-m-k8s-1.20: WO-m-k8s-1.20: Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again WO-m-k8s-1.20: Loaded plugins: fastestmirror WO-m-k8s-1.20: Loading mirror speeds from cached hostfile WO-m-k8s-1.20: WO-m-k8s-1.20: WO-m-k8s-1.20: One of the configured repositories failed (Unknown), WO-m-k8s-1.20: and yum doesn't have enough cached data to continue. At this point the only WO-m-k8s-1.20: safe thing yum can do is fail. There are a few ways to work "fix" this: WO-m-k8s-1.20: WO-m-k8s-1.20: 1. Contact the upstream for the repository and get them to fix the problem. WO-m-k8s-1.20: WO-m-k8s-1.20: 2. Reconfigure the baseurl/etc. for the repository, to point to a working WO-m-k8s-1.20: upstream. This is most often useful if you are using a newer WO-m-k8s-1.20: distribution release than is supported by the repository (and the WO-m-k8s-1.20: packages for the previous distribution release still work). WO-m-k8s-1.20: WO-m-k8s-1.20: 3. Run the command with the repository temporarily disabled WO-m-k8s-1.20: yum --disablerepo=<repoid> ... WO-m-k8s-1.20: WO-m-k8s-1.20: 4. Disable the repository permanently, so yum won't use it by default. Yum WO-m-k8s-1.20: will then just ignore the repository until you permanently enable it WO-m-k8s-1.20: again or use --enablerepo for temporary usage: WO-m-k8s-1.20: WO-m-k8s-1.20: yum-config-manager --disable <repoid> WO-m-k8s-1.20: or WO-m-k8s-1.20: subscription-manager repos --disable=<repoid> WO-m-k8s-1.20: WO-m-k8s-1.20: 5. Configure the failing repository to be skipped, if it is unavailable. WO-m-k8s-1.20: Note that yum will try to contact the repo. when it runs most commands, WO-m-k8s-1.20: so will have to try and fail each time (and thus. yum will be be much WO-m-k8s-1.20: slower). If it is a very temporary problem though, this is often a nice WO-m-k8s-1.20: compromise: WO-m-k8s-1.20: WO-m-k8s-1.20: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true WO-m-k8s-1.20: WO-m-k8s-1.20: Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again WO-m-k8s-1.20: Failed to execute operation: No such file or directory WO-m-k8s-1.20: Failed to execute operation: No such file or directory The SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed. The output for this command should be in the log above. Please read the output to determine what went wrong. C:\HashiCorp\_Lecture_k8s_learning.kit-main\ch1\1.5\k8s-min-5GiB-wo-add-nodes> * 참고 * 강의에서 다루지 않는 쿠버네티스 범위를 넘는 질문은 쿠버네티스 오픈 채팅 및 유저 그룹을 이용하는게 도움이 될 수 있습니다. (https://open.kakao.com/o/gxSooElb {암호: kubectl}- 잠깐! 인프런 서비스 운영 관련 문의는 1:1 문의하기를 이용해주세요.

수업을 들으면서 chapter02-1 파일을 만들고 print('pyhon start') 라고 작성하니까 아무 반응이 나타나지 않네요

- 학습 관련 질문을 남겨주세요. 상세히 작성하면 더 좋아요! - 먼저 유사한 질문이 있었는지 검색해보세요. - 서로 예의를 지키며 존중하는 문화를 만들어가요. - 잠깐! 인프런 서비스 운영 관련 문의는 1:1 문의하기를 이용해주세요.

안녕하세요? Zynq 공부에 큰 도움이되고 있습니다. 감사합니다. 강의 내용은 아니지만 PL to PS Interrupt 관련해서 질문드립니다. 질문 ========================================================================== 블럭 디자인에서 포트를 생성하여 interrupt 설정 후 IRQ_F2P[0:0]에 연결하면 Interrupt가 활성화 됩니다. (실제 실행 확인) 강의에 사용된 IP를 사용하는 경우 Interrupt가 활성화가 않됩니다. 추가 설정해야 하는 부분이 있는건가요? ========================================================================== 10_fsm_counter 프로젝트의 IP를 사용하여 첨부된 그림1과 같이 수정 하였으며  블럭은 첨부된 그림2와 같습니다. Bitstream 완료 후 Export Hardware로 Inculde bitstream 하여  Vits에서 xparameters.h 를 확인하면 첨부된 그림3과 같은 인터럽트 정의가 없어서 문의 드립니다. 추가 설정해야 하는 부분이 있는것인지 어떤 부분에서 문제가 발생했는지 혹시 알수 있을까요? 감사합니다.

@GetMapping("/api/v2/simple-orders")public Result<SimpleOrderDTO> orders() { List<Order> orders = orderRepository.findByString(new OrderSearch()); List<SimpleOrderDTO> result = orders.stream() .map(SimpleOrderDTO::new) // 람다식 -> 메서드 참조 (Method Reference) .collect(Collectors.toList()); return new Result<SimpleOrderDTO>(result.size(), result);}@Data@AllArgsConstructorstatic class Result<T> { private int count; private List<T> simpleOrderDTO;} 이렇게 작성하면 될까요?? 결과 화면은 아래처럼 나옵니다!

cors 모듈 이용해서   access-control-allow-credentials access-control-allow-origin 을 설정해야하는건 알겠습니다.   만약에 client에 proxy -> http-proxy-middleware를 이용해서 세팅하면 cors는 잡히는데 credentials는 따로 셋팅할 필요가 없나요 ?

안녕하세요  그랩님의 영상으로 학습한상태입니다  그런데 아래 블로그에서도 같은내용의 정보인것같아서요 굳이 영상으로 학습한거라면 블로그 내용이랑 같아서 따로 다시 볼필요는 없는거겠죠? https://www.grabbing.me/IT-A-to-Z-By-1e1fbc981b7c4c03ac44943085ac8304

    선생님, csv 파일 불러오기 그대로 코드에 나와있는데로 df = pd.read_csv(file_name, encoding="utf-8") 하는데 파일낫파운드에러가 나와요! 제가 혹시 csv파일을 다운로드 폴더에 노트북에 받고 실습은 코랩으로 해서 그런가요??? 구글 드라이브에 저 제시해주신 파일(seoul-covid19_6_30_)이 있어야 불러오기가 가능한지요?   선생님도 좋은하루되세요 감사합니다.

1. 만약, 컴포넌트 스캔만 쓰는 경우에,  메인에서 ApplicationContext를 호출하는 이유가 뭘까요? 어차피 @SpringBootApplication에 @ComponentScan이 있이니 호출할 이유가 없지 않을까요?   2. 싱글톤으로 바꾸는 @Configuration이 없어도 @ComponentScan만으로 싱글톤 빈등록이 되는건가요?

안녕하세요 c 드라이브에 올려주는 코드를 두지 않고 D 드라이브에서 따라 하고 싶은데 꼭 c드라이브로 진행해야 하나요? d 드라이브에서 하고 싶었는데 사실 bundle install이 잘 되지도 않고 어쩌다가 보니 설치가 되었는데  bundle exec jekyll serve 이 작업을 할려고 하는데  이미지와 같이 문제가 계속 발생이 됩니다 ㅠ

../node_modules/@react-navigation/core/lib/module/types.jsModule not found: Can't resolve '@babel/runtime/helpers/classCallCheck' in 'C:\Users\LG\node_modules\@react-navigation\core\lib\module'라고 뜨는데 이건 어떻게 해결하나요?

코드 중 하기 부분이 이해되지 않습니다. # 평균 손실을 측정합니다 average_loss += current_loss/total_batch   batch for loop 안에서 average_loss += current_loss 를 계산하고 이후 epoch for loop 뒷단에서 average_loss = average_loss/total_batch 를 계산해야 1 epoch당 평균 loss가 계산되는 것이 아닌가요?  

강사님 안녕하세요 유용하고 재미있는 수업 잘 듣고 있습니다! :)   flex 관련 책을 별도로 보다가   챕터는 flex-grow, shrink, basis에 관한 내용을 다루는 챕터였고요.   W3C 플렉서블 박스 기술 명세에 따르면 '박스의 크기 증감 속성을 개별적으로 사용하는 것'을 추천하지 않고 있습니다.   라고 되어 있어서 궁금해서 사이트를 가보았는데 별다른 내용(?)을 찾지 못했는데요.   https://www.w3schools.com/css/css3_flexbox.asp   여기를 보았고 제가 엉뚱한 곳을 보고 있는것인지요.   이유가 정말! 궁금합니다 . 혹시 알려주실 수 있을까요? ㅠㅠ   시간 내주셔서 감사합니다!

@Configuration 적용시 클래스에 싱글톤 패턴 구현 안해도 되나요? 실무에선 어떻게 사용되나요? 현재 DI컨테이너에다가 @Configuration해놓고 메인에 불러와서 쓰고 있는데, 어차피 빈 등록할 때 CGLIB로 싱글톤 형태로 반환해주니까, 여기(AppContext)에 등록된 Bean 클래스 안에 굳이 싱글톤 패턴 적용 안해도 괜찮을까요?

윈도우 커맨드 : 기능 설명입니다.   dir : ls - 디렉토리 내 파일 확인 cls : clear - CLI 화면 비움  del, rmdir : rm / rm -r 기능, 삭제이므로 굉장히 주의 필요 type : cat - 텍스트 형식 파일 cli 내 출력 cd , : pwd - 현재 경로 출력      

axure 프로그램에서 보이는 페이지들이 공유한 URL에서는 페이지가 노출되지 않습니다. 예를 들면 axure 프로그램에서 아래 '자료리스트' 페이지를 만들었는데요.   타인에게 공유한 URL에서 보면 없어요.. ㅠㅠ   왜 그런걸까요?

geth --networkid 4386 --mine --miner.threads 2 --datadir "./" --nodiscover --http --http.port "8544" --http.corsdomain "*" --nat "any" --http.api eth,web3,personal,net --allow-insecure-unlock --password ./password.sec   공부하시는 분들을 위해서 글 남깁니다.  위 명령어로 하니 실행이 되었습니다  버전업이 되면서 명령어 일부가 deprecate된거 같습니다.   - miner 다음에 "." 명령어가 삽입되어야 하는거 같습니다.  - 현재로서는 rpc관련 명령어가 Legacy되어서 http로 변경되어야 했습니다.   더불어 Mac 에서는 nodestart.sh로 파일명 수정후 ./nodestart.sh 로 실행하면 됩니다.    

안녕하세요, 강사님 혹시 UBUNTU 20 ROOT id 및 패스워드가 어떻게될까요?   이전 올려주신 18 이랑은 다르네용

'배틀로얄 게임을 만들어보며 배우는 언리얼 게임 개발' 교육을 듣고 싶어요. 그런데 강의 신청 페이지에 '수강제한'이라고 되어 있습니다. 강의를 들을수 있는 방법이 있을까요? 답변 부탁드립니다.

허프만 코딩 강의중 12:21 에서  prefix 트리로 봤을때 Fixed-length code 에 b 값이 110 이 아닌 001 이되어야 될것 같은데 제가 잘 이해하지 못한 건지 아니면 오타인지 궁금합니다.