Engine 빌드 후 코드 실행했을때 흰 화면에 무한로딩이 걸립니다... 어떻게 해결하나요??

강의 10: 21부분입니다.교수님께서 61번째 문장 dest = "Start something"; //Error에서 에러가 발생한다고 말하셨는데, 어째서 에러가 발생하게 되는 것인지 잘 모르겠습니다.error C2106: '=': left operand must be l-value빌드를 실행해보면 왼쪽은 l-value로서 작동해야한다고 합니다.이미 공간(주소)을 할당받은 배열 dest가 있고,배열의 이름 dest, 즉 포인터에다가, (수정불가능한/읽기만 가능한 프로그램 코드에 있는) "Start something"이라는 문자열의 주소를 대입함으로서 그걸 수정(?)하려 시도했기에 에러가 발생하는걸까 싶기도 하고.. 머릿 속의 개념이 꼬여버렸습니다.※그치만 이것이 안되는 경우는,'포인터로 정의한 문자열이 있을 때 포인터를 통해 인덱싱하여 값을 수정하려고 했을 때" 문제가 발생하는 경우였습니다.이번 dest = "Start something"; //Error의 경우에 해당하진 않을 것 같습니다.

안녕하세요 다름이 아니라 강의들을 쭉 듣다보니앞에 @Enumerated 어노테이션을 설명하실때도EnumType.ORDINAL이 순서를 DB에 저장하는 것이라 실무에서 쓰지 말라고 하셨고이번에 JPQL에서도 파라미터 바인딩에서 위치 기준으로 바인딩하는건 쓰지말라고 하셨는데(이것도 순서를 기준으로 하는 것이니까 그런 것이겠죠??)Q. 실무에서 Spring이나 JPA뿐만이 아니라 다른 기술들을 쓰더라도 웬만한 상황들에 대해서 순서를 기준으로 데이터를 저장하거나 조회한다거나 이런 코드들은 데이터의 변화에 따라서 순서가 바뀔 수 있으므로 안쓰는 것이 좋은 가요?!

유익한 강의 올려주셔서 감사합니다 :) 유니티 관련 모듈화 프로그래밍 강의 중 가장 퀄리티가 좋아 매우 만족하며 수강하고있습니다 :)질문드리고 싶은 부분은 QuestSystem 기능 입니다. QustSystem.cs 의 instance 에서 NullReferenceException 오류가 발생하고 있습니다.(퀘스트 Save & Load (with JSON) 구현 부분까지 수강, 실습 다 완료한 상태라 관련 스크립트까지 오류목록에 떳지만, Save & Load 수강 전에도 NullReferenceException오류가 있었습니다!) 아래캡처는 오류 부분 더블클릭시 이동되어진 코드부분입니다. (QuestSystem.cs) 의심되는 코드부분 몇개 더 첨부해봅니다..instance에 Null이 들어가서 그러는걸까요..? 원본 코드랑 비교도 해보고 이것저것 찾아봣지만 해결이 안되서 3일째 되는날 주섬주섬 질문해봅니다.😥

쿠버네틱스 강의 듣고 있는데 계속 에러가 떠서 뭐 할 수가 없네요 2일간 구글링 해봤는데 안되서 여기다가 질문 날립니다. 아래는 쿠버넷 에러나는 곳만 발췌한 부분입니다. w3-k8s-1.25.0: Loaded plugins: fastestmirror w3-k8s-1.25.0: Determining fastest mirrors w3-k8s-1.25.0: * base: mirror.navercorp.com w3-k8s-1.25.0: * extras: mirror.navercorp.com w3-k8s-1.25.0: * updates: mirror.navercorp.com w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time." w3-k8s-1.25.0: Trying other mirror. w3-k8s-1.25.0: It was impossible to connect to the CentOS servers. w3-k8s-1.25.0: This could mean a connectivity issue in your environment, such as the requirement to configure a proxy, w3-k8s-1.25.0: or a transparent proxy that tampers with TLS security, or an incorrect system clock. w3-k8s-1.25.0: You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors w3-k8s-1.25.0: If above article doesn't help to resolve this issue please use https://bugs.centos.org/. w3-k8s-1.25.0: w3-k8s-1.25.0: w3-k8s-1.25.0: w3-k8s-1.25.0: One of the configured repositories failed (Kubernetes), w3-k8s-1.25.0: and yum doesn't have enough cached data to continue. At this point the only w3-k8s-1.25.0: safe thing yum can do is fail. There are a few ways to work "fix" this: w3-k8s-1.25.0: w3-k8s-1.25.0: 1. Contact the upstream for the repository and get them to fix the problem. w3-k8s-1.25.0: w3-k8s-1.25.0: 2. Reconfigure the baseurl/etc. for the repository, to point to a working w3-k8s-1.25.0: upstream. This is most often useful if you are using a newer w3-k8s-1.25.0: distribution release than is supported by the repository (and the w3-k8s-1.25.0: packages for the previous distribution release still work). w3-k8s-1.25.0: w3-k8s-1.25.0: 3. Run the command with the repository temporarily disabled w3-k8s-1.25.0: yum --disablerepo=kubernetes ... w3-k8s-1.25.0: w3-k8s-1.25.0: 4. Disable the repository permanently, so yum won't use it by default. Yum w3-k8s-1.25.0: will then just ignore the repository until you permanently enable it w3-k8s-1.25.0: again or use --enablerepo for temporary usage: w3-k8s-1.25.0: w3-k8s-1.25.0: yum-config-manager --disable kubernetes w3-k8s-1.25.0: or w3-k8s-1.25.0: subscription-manager repos --disable=kubernetes w3-k8s-1.25.0: w3-k8s-1.25.0: 5. Configure the failing repository to be skipped, if it is unavailable. w3-k8s-1.25.0: Note that yum will try to contact the repo. when it runs most commands, w3-k8s-1.25.0: so will have to try and fail each time (and thus. yum will be be much w3-k8s-1.25.0: slower). If it is a very temporary problem though, this is often a nice w3-k8s-1.25.0: compromise: w3-k8s-1.25.0: w3-k8s-1.25.0: yum-config-manager --save --setopt=kubernetes.skip_if_unavailable=true w3-k8s-1.25.0: w3-k8s-1.25.0: failure: repodata/repomd.xml from kubernetes: [Errno 256] No more mirrors to try. w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time."  여기서 아래는 Vagrant Up 한 이후의 전문입니다.$ vagrant up Bringing machine 'm-k8s-1.25.0' up with 'virtualbox' provider... Bringing machine 'w1-k8s-1.25.0' up with 'virtualbox' provider... Bringing machine 'w2-k8s-1.25.0' up with 'virtualbox' provider... Bringing machine 'w3-k8s-1.25.0' up with 'virtualbox' provider... ==> m-k8s-1.25.0: Checking if box 'sysnet4admin/CentOS-k8s' version '0.7.4' is up to date... ==> m-k8s-1.25.0: Clearing any previously set forwarded ports... ==> m-k8s-1.25.0: Clearing any previously set network interfaces... ==> m-k8s-1.25.0: Preparing network interfaces based on configuration... m-k8s-1.25.0: Adapter 1: nat m-k8s-1.25.0: Adapter 2: hostonly ==> m-k8s-1.25.0: Forwarding ports... m-k8s-1.25.0: 22 (guest) => 60010 (host) (adapter 1) ==> m-k8s-1.25.0: Running 'pre-boot' VM customizations... ==> m-k8s-1.25.0: Booting VM... ==> m-k8s-1.25.0: Waiting for machine to boot. This may take a few minutes... m-k8s-1.25.0: SSH address: 127.0.0.1:60010 m-k8s-1.25.0: SSH username: vagrant m-k8s-1.25.0: SSH auth method: private key ==> m-k8s-1.25.0: Machine booted and ready! ==> m-k8s-1.25.0: Checking for guest additions in VM... m-k8s-1.25.0: The guest additions on this VM do not match the installed version of m-k8s-1.25.0: VirtualBox! In most cases this is fine, but in rare cases it can m-k8s-1.25.0: prevent things such as shared folders from working properly. If you see m-k8s-1.25.0: shared folder errors, please make sure the guest additions within the m-k8s-1.25.0: virtual machine match the version of VirtualBox you have installed on m-k8s-1.25.0: your host and reload your VM. m-k8s-1.25.0: m-k8s-1.25.0: Guest Additions Version: 5.2.12 m-k8s-1.25.0: VirtualBox Version: 6.1 ==> m-k8s-1.25.0: Setting hostname... ==> m-k8s-1.25.0: Configuring and enabling network interfaces... ==> m-k8s-1.25.0: Machine already provisioned. Run `vagrant provision` or use the `--provision` ==> m-k8s-1.25.0: flag to force provisioning. Provisioners marked to run always will still run. ==> w1-k8s-1.25.0: Checking if box 'sysnet4admin/CentOS-k8s' version '0.7.4' is up to date... ==> w1-k8s-1.25.0: Clearing any previously set forwarded ports... ==> w1-k8s-1.25.0: Clearing any previously set network interfaces... ==> w1-k8s-1.25.0: Preparing network interfaces based on configuration... w1-k8s-1.25.0: Adapter 1: nat w1-k8s-1.25.0: Adapter 2: hostonly ==> w1-k8s-1.25.0: Forwarding ports... w1-k8s-1.25.0: 22 (guest) => 60101 (host) (adapter 1) ==> w1-k8s-1.25.0: Running 'pre-boot' VM customizations... ==> w1-k8s-1.25.0: Booting VM... ==> w1-k8s-1.25.0: Waiting for machine to boot. This may take a few minutes... w1-k8s-1.25.0: SSH address: 127.0.0.1:60101 w1-k8s-1.25.0: SSH username: vagrant w1-k8s-1.25.0: SSH auth method: private key ==> w1-k8s-1.25.0: Machine booted and ready! ==> w1-k8s-1.25.0: Checking for guest additions in VM... w1-k8s-1.25.0: The guest additions on this VM do not match the installed version of w1-k8s-1.25.0: VirtualBox! In most cases this is fine, but in rare cases it can w1-k8s-1.25.0: prevent things such as shared folders from working properly. If you see w1-k8s-1.25.0: shared folder errors, please make sure the guest additions within the w1-k8s-1.25.0: virtual machine match the version of VirtualBox you have installed on w1-k8s-1.25.0: your host and reload your VM. w1-k8s-1.25.0: w1-k8s-1.25.0: Guest Additions Version: 5.2.12 w1-k8s-1.25.0: VirtualBox Version: 6.1 ==> w1-k8s-1.25.0: Setting hostname... ==> w1-k8s-1.25.0: Configuring and enabling network interfaces... ==> w1-k8s-1.25.0: Machine already provisioned. Run `vagrant provision` or use the `--provision` ==> w1-k8s-1.25.0: flag to force provisioning. Provisioners marked to run always will still run. ==> w2-k8s-1.25.0: Checking if box 'sysnet4admin/CentOS-k8s' version '0.7.4' is up to date... ==> w2-k8s-1.25.0: Clearing any previously set forwarded ports... ==> w2-k8s-1.25.0: Clearing any previously set network interfaces... ==> w2-k8s-1.25.0: Preparing network interfaces based on configuration... w2-k8s-1.25.0: Adapter 1: nat w2-k8s-1.25.0: Adapter 2: hostonly ==> w2-k8s-1.25.0: Forwarding ports... w2-k8s-1.25.0: 22 (guest) => 60102 (host) (adapter 1) ==> w2-k8s-1.25.0: Running 'pre-boot' VM customizations... ==> w2-k8s-1.25.0: Booting VM... ==> w2-k8s-1.25.0: Waiting for machine to boot. This may take a few minutes... w2-k8s-1.25.0: SSH address: 127.0.0.1:60102 w2-k8s-1.25.0: SSH username: vagrant w2-k8s-1.25.0: SSH auth method: private key w2-k8s-1.25.0: Warning: Connection reset. Retrying... ==> w2-k8s-1.25.0: Machine booted and ready! ==> w2-k8s-1.25.0: Checking for guest additions in VM... w2-k8s-1.25.0: The guest additions on this VM do not match the installed version of w2-k8s-1.25.0: VirtualBox! In most cases this is fine, but in rare cases it can w2-k8s-1.25.0: prevent things such as shared folders from working properly. If you see w2-k8s-1.25.0: shared folder errors, please make sure the guest additions within the w2-k8s-1.25.0: virtual machine match the version of VirtualBox you have installed on w2-k8s-1.25.0: your host and reload your VM. w2-k8s-1.25.0: w2-k8s-1.25.0: Guest Additions Version: 5.2.12 w2-k8s-1.25.0: VirtualBox Version: 6.1 ==> w2-k8s-1.25.0: Setting hostname... ==> w2-k8s-1.25.0: Configuring and enabling network interfaces... ==> w2-k8s-1.25.0: Machine already provisioned. Run `vagrant provision` or use the `--provision` ==> w2-k8s-1.25.0: flag to force provisioning. Provisioners marked to run always will still run. ==> w3-k8s-1.25.0: Importing base box 'sysnet4admin/CentOS-k8s'... ==> w3-k8s-1.25.0: Matching MAC address for NAT networking... ==> w3-k8s-1.25.0: Checking if box 'sysnet4admin/CentOS-k8s' version '0.7.4' is up to date... ==> w3-k8s-1.25.0: Setting the name of the VM: w3-k8s-1.25.0(github_SysNet4Admin) ==> w3-k8s-1.25.0: Clearing any previously set network interfaces... ==> w3-k8s-1.25.0: Preparing network interfaces based on configuration... w3-k8s-1.25.0: Adapter 1: nat w3-k8s-1.25.0: Adapter 2: hostonly ==> w3-k8s-1.25.0: Forwarding ports... w3-k8s-1.25.0: 22 (guest) => 60103 (host) (adapter 1) ==> w3-k8s-1.25.0: Running 'pre-boot' VM customizations... ==> w3-k8s-1.25.0: Booting VM... ==> w3-k8s-1.25.0: Waiting for machine to boot. This may take a few minutes... w3-k8s-1.25.0: SSH address: 127.0.0.1:60103 w3-k8s-1.25.0: SSH username: vagrant w3-k8s-1.25.0: SSH auth method: private key w3-k8s-1.25.0: Warning: Connection reset. Retrying... w3-k8s-1.25.0: w3-k8s-1.25.0: Vagrant insecure key detected. Vagrant will automatically replace w3-k8s-1.25.0: this with a newly generated keypair for better security. w3-k8s-1.25.0: w3-k8s-1.25.0: Inserting generated public key within guest... w3-k8s-1.25.0: Removing insecure key from the guest if it's present... w3-k8s-1.25.0: Key inserted! Disconnecting and reconnecting using new SSH key... ==> w3-k8s-1.25.0: Machine booted and ready! ==> w3-k8s-1.25.0: Checking for guest additions in VM... w3-k8s-1.25.0: The guest additions on this VM do not match the installed version of w3-k8s-1.25.0: VirtualBox! In most cases this is fine, but in rare cases it can w3-k8s-1.25.0: prevent things such as shared folders from working properly. If you see w3-k8s-1.25.0: shared folder errors, please make sure the guest additions within the w3-k8s-1.25.0: virtual machine match the version of VirtualBox you have installed on w3-k8s-1.25.0: your host and reload your VM. w3-k8s-1.25.0: w3-k8s-1.25.0: Guest Additions Version: 5.2.12 w3-k8s-1.25.0: VirtualBox Version: 6.1 ==> w3-k8s-1.25.0: Setting hostname... ==> w3-k8s-1.25.0: Configuring and enabling network interfaces... ==> w3-k8s-1.25.0: Running provisioner: shell... w3-k8s-1.25.0: Running: /tmp/vagrant-shell20221101-5892-1o7k64u.sh ==> w3-k8s-1.25.0: Running provisioner: shell... w3-k8s-1.25.0: Running: /tmp/vagrant-shell20221101-5892-1a62ito.sh w3-k8s-1.25.0: Loaded plugins: fastestmirror w3-k8s-1.25.0: Determining fastest mirrors w3-k8s-1.25.0: * base: mirror.navercorp.com w3-k8s-1.25.0: * extras: mirror.navercorp.com w3-k8s-1.25.0: * updates: mirror.navercorp.com w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time." w3-k8s-1.25.0: Trying other mirror. w3-k8s-1.25.0: It was impossible to connect to the CentOS servers. w3-k8s-1.25.0: This could mean a connectivity issue in your environment, such as the requirement to configure a proxy, w3-k8s-1.25.0: or a transparent proxy that tampers with TLS security, or an incorrect system clock. w3-k8s-1.25.0: You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors w3-k8s-1.25.0: If above article doesn't help to resolve this issue please use https://bugs.centos.org/. w3-k8s-1.25.0: w3-k8s-1.25.0: w3-k8s-1.25.0: w3-k8s-1.25.0: One of the configured repositories failed (Kubernetes), w3-k8s-1.25.0: and yum doesn't have enough cached data to continue. At this point the only w3-k8s-1.25.0: safe thing yum can do is fail. There are a few ways to work "fix" this: w3-k8s-1.25.0: w3-k8s-1.25.0: 1. Contact the upstream for the repository and get them to fix the problem. w3-k8s-1.25.0: w3-k8s-1.25.0: 2. Reconfigure the baseurl/etc. for the repository, to point to a working w3-k8s-1.25.0: upstream. This is most often useful if you are using a newer w3-k8s-1.25.0: distribution release than is supported by the repository (and the w3-k8s-1.25.0: packages for the previous distribution release still work). w3-k8s-1.25.0: w3-k8s-1.25.0: 3. Run the command with the repository temporarily disabled w3-k8s-1.25.0: yum --disablerepo=kubernetes ... w3-k8s-1.25.0: w3-k8s-1.25.0: 4. Disable the repository permanently, so yum won't use it by default. Yum w3-k8s-1.25.0: will then just ignore the repository until you permanently enable it w3-k8s-1.25.0: again or use --enablerepo for temporary usage: w3-k8s-1.25.0: w3-k8s-1.25.0: yum-config-manager --disable kubernetes w3-k8s-1.25.0: or w3-k8s-1.25.0: subscription-manager repos --disable=kubernetes w3-k8s-1.25.0: w3-k8s-1.25.0: 5. Configure the failing repository to be skipped, if it is unavailable. w3-k8s-1.25.0: Note that yum will try to contact the repo. when it runs most commands, w3-k8s-1.25.0: so will have to try and fail each time (and thus. yum will be be much w3-k8s-1.25.0: slower). If it is a very temporary problem though, this is often a nice w3-k8s-1.25.0: compromise: w3-k8s-1.25.0: w3-k8s-1.25.0: yum-config-manager --save --setopt=kubernetes.skip_if_unavailable=true w3-k8s-1.25.0: w3-k8s-1.25.0: failure: repodata/repomd.xml from kubernetes: [Errno 256] No more mirrors to try. w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time." w3-k8s-1.25.0: Loaded plugins: fastestmirror w3-k8s-1.25.0: Loading mirror speeds from cached hostfile w3-k8s-1.25.0: * base: mirror.navercorp.com w3-k8s-1.25.0: * extras: mirror.navercorp.com w3-k8s-1.25.0: * updates: mirror.navercorp.com w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time." w3-k8s-1.25.0: Trying other mirror. w3-k8s-1.25.0: It was impossible to connect to the CentOS servers. w3-k8s-1.25.0: This could mean a connectivity issue in your environment, such as the requirement to configure a proxy, w3-k8s-1.25.0: or a transparent proxy that tampers with TLS security, or an incorrect system clock. w3-k8s-1.25.0: You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors w3-k8s-1.25.0: If above article doesn't help to resolve this issue please use https://bugs.centos.org/. w3-k8s-1.25.0: w3-k8s-1.25.0: w3-k8s-1.25.0: w3-k8s-1.25.0: One of the configured repositories failed (Kubernetes), w3-k8s-1.25.0: and yum doesn't have enough cached data to continue. At this point the only w3-k8s-1.25.0: safe thing yum can do is fail. There are a few ways to work "fix" this: w3-k8s-1.25.0: w3-k8s-1.25.0: 1. Contact the upstream for the repository and get them to fix the problem. w3-k8s-1.25.0: w3-k8s-1.25.0: 2. Reconfigure the baseurl/etc. for the repository, to point to a working w3-k8s-1.25.0: upstream. This is most often useful if you are using a newer w3-k8s-1.25.0: distribution release than is supported by the repository (and the w3-k8s-1.25.0: packages for the previous distribution release still work). w3-k8s-1.25.0: w3-k8s-1.25.0: 3. Run the command with the repository temporarily disabled w3-k8s-1.25.0: yum --disablerepo=kubernetes ... w3-k8s-1.25.0: w3-k8s-1.25.0: 4. Disable the repository permanently, so yum won't use it by default. Yum w3-k8s-1.25.0: will then just ignore the repository until you permanently enable it w3-k8s-1.25.0: again or use --enablerepo for temporary usage: w3-k8s-1.25.0: w3-k8s-1.25.0: yum-config-manager --disable kubernetes w3-k8s-1.25.0: or w3-k8s-1.25.0: subscription-manager repos --disable=kubernetes w3-k8s-1.25.0: w3-k8s-1.25.0: 5. Configure the failing repository to be skipped, if it is unavailable. w3-k8s-1.25.0: Note that yum will try to contact the repo. when it runs most commands, w3-k8s-1.25.0: so will have to try and fail each time (and thus. yum will be be much w3-k8s-1.25.0: slower). If it is a very temporary problem though, this is often a nice w3-k8s-1.25.0: compromise: w3-k8s-1.25.0: w3-k8s-1.25.0: yum-config-manager --save --setopt=kubernetes.skip_if_unavailable=true w3-k8s-1.25.0: w3-k8s-1.25.0: failure: repodata/repomd.xml from kubernetes: [Errno 256] No more mirrors to try. w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time." w3-k8s-1.25.0: Loaded plugins: fastestmirror w3-k8s-1.25.0: Loading mirror speeds from cached hostfile w3-k8s-1.25.0: * base: mirror.navercorp.com w3-k8s-1.25.0: * extras: mirror.navercorp.com w3-k8s-1.25.0: * updates: mirror.navercorp.com w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time." w3-k8s-1.25.0: Trying other mirror. w3-k8s-1.25.0: It was impossible to connect to the CentOS servers. w3-k8s-1.25.0: This could mean a connectivity issue in your environment, such as the requirement to configure a proxy, w3-k8s-1.25.0: or a transparent proxy that tampers with TLS security, or an incorrect system clock. w3-k8s-1.25.0: You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors w3-k8s-1.25.0: If above article doesn't help to resolve this issue please use https://bugs.centos.org/. w3-k8s-1.25.0: w3-k8s-1.25.0: w3-k8s-1.25.0: w3-k8s-1.25.0: One of the configured repositories failed (Kubernetes), w3-k8s-1.25.0: and yum doesn't have enough cached data to continue. At this point the only w3-k8s-1.25.0: safe thing yum can do is fail. There are a few ways to work "fix" this: w3-k8s-1.25.0: w3-k8s-1.25.0: 1. Contact the upstream for the repository and get them to fix the problem. w3-k8s-1.25.0: w3-k8s-1.25.0: 2. Reconfigure the baseurl/etc. for the repository, to point to a working w3-k8s-1.25.0: upstream. This is most often useful if you are using a newer w3-k8s-1.25.0: distribution release than is supported by the repository (and the w3-k8s-1.25.0: packages for the previous distribution release still work). w3-k8s-1.25.0: w3-k8s-1.25.0: 3. Run the command with the repository temporarily disabled w3-k8s-1.25.0: yum --disablerepo=kubernetes ... w3-k8s-1.25.0: w3-k8s-1.25.0: 4. Disable the repository permanently, so yum won't use it by default. Yum w3-k8s-1.25.0: will then just ignore the repository until you permanently enable it w3-k8s-1.25.0: again or use --enablerepo for temporary usage: w3-k8s-1.25.0: w3-k8s-1.25.0: yum-config-manager --disable kubernetes w3-k8s-1.25.0: or w3-k8s-1.25.0: subscription-manager repos --disable=kubernetes w3-k8s-1.25.0: w3-k8s-1.25.0: 5. Configure the failing repository to be skipped, if it is unavailable. w3-k8s-1.25.0: Note that yum will try to contact the repo. when it runs most commands, w3-k8s-1.25.0: so will have to try and fail each time (and thus. yum will be be much w3-k8s-1.25.0: slower). If it is a very temporary problem though, this is often a nice w3-k8s-1.25.0: compromise: w3-k8s-1.25.0: w3-k8s-1.25.0: yum-config-manager --save --setopt=kubernetes.skip_if_unavailable=true w3-k8s-1.25.0: w3-k8s-1.25.0: failure: repodata/repomd.xml from kubernetes: [Errno 256] No more mirrors to try. w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time." w3-k8s-1.25.0: Loaded plugins: fastestmirror w3-k8s-1.25.0: Loading mirror speeds from cached hostfile w3-k8s-1.25.0: * base: mirror.navercorp.com w3-k8s-1.25.0: * extras: mirror.navercorp.com w3-k8s-1.25.0: * updates: mirror.navercorp.com w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time." w3-k8s-1.25.0: Trying other mirror. w3-k8s-1.25.0: It was impossible to connect to the CentOS servers. w3-k8s-1.25.0: This could mean a connectivity issue in your environment, such as the requirement to configure a proxy, w3-k8s-1.25.0: or a transparent proxy that tampers with TLS security, or an incorrect system clock. w3-k8s-1.25.0: You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors w3-k8s-1.25.0: If above article doesn't help to resolve this issue please use https://bugs.centos.org/. w3-k8s-1.25.0: w3-k8s-1.25.0: w3-k8s-1.25.0: w3-k8s-1.25.0: One of the configured repositories failed (Kubernetes), w3-k8s-1.25.0: and yum doesn't have enough cached data to continue. At this point the only w3-k8s-1.25.0: safe thing yum can do is fail. There are a few ways to work "fix" this: w3-k8s-1.25.0: w3-k8s-1.25.0: 1. Contact the upstream for the repository and get them to fix the problem. w3-k8s-1.25.0: w3-k8s-1.25.0: 2. Reconfigure the baseurl/etc. for the repository, to point to a working w3-k8s-1.25.0: upstream. This is most often useful if you are using a newer w3-k8s-1.25.0: distribution release than is supported by the repository (and the w3-k8s-1.25.0: packages for the previous distribution release still work). w3-k8s-1.25.0: w3-k8s-1.25.0: 3. Run the command with the repository temporarily disabled w3-k8s-1.25.0: yum --disablerepo=kubernetes ... w3-k8s-1.25.0: w3-k8s-1.25.0: 4. Disable the repository permanently, so yum won't use it by default. Yum w3-k8s-1.25.0: will then just ignore the repository until you permanently enable it w3-k8s-1.25.0: again or use --enablerepo for temporary usage: w3-k8s-1.25.0: w3-k8s-1.25.0: yum-config-manager --disable kubernetes w3-k8s-1.25.0: or w3-k8s-1.25.0: subscription-manager repos --disable=kubernetes w3-k8s-1.25.0: w3-k8s-1.25.0: 5. Configure the failing repository to be skipped, if it is unavailable. w3-k8s-1.25.0: Note that yum will try to contact the repo. when it runs most commands, w3-k8s-1.25.0: so will have to try and fail each time (and thus. yum will be be much w3-k8s-1.25.0: slower). If it is a very temporary problem though, this is often a nice w3-k8s-1.25.0: compromise: w3-k8s-1.25.0: w3-k8s-1.25.0: yum-config-manager --save --setopt=kubernetes.skip_if_unavailable=true w3-k8s-1.25.0: w3-k8s-1.25.0: failure: repodata/repomd.xml from kubernetes: [Errno 256] No more mirrors to try. w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time." w3-k8s-1.25.0: Loaded plugins: fastestmirror w3-k8s-1.25.0: adding repo from: https://download.docker.com/linux/centos/docker-ce.repo w3-k8s-1.25.0: grabbing file https://download.docker.com/linux/centos/docker-ce.repo to /etc/yum.repos.d/docker-ce.repo w3-k8s-1.25.0: Could not fetch/save url https://download.docker.com/linux/centos/docker-ce.repo to file /etc/yum.repos.d/docker-ce.repo: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time." w3-k8s-1.25.0: Loaded plugins: fastestmirror w3-k8s-1.25.0: Loading mirror speeds from cached hostfile w3-k8s-1.25.0: * base: mirror.navercorp.com w3-k8s-1.25.0: * extras: mirror.navercorp.com w3-k8s-1.25.0: * updates: mirror.navercorp.com w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time." w3-k8s-1.25.0: Trying other mirror. w3-k8s-1.25.0: It was impossible to connect to the CentOS servers. w3-k8s-1.25.0: This could mean a connectivity issue in your environment, such as the requirement to configure a proxy, w3-k8s-1.25.0: or a transparent proxy that tampers with TLS security, or an incorrect system clock. w3-k8s-1.25.0: You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors w3-k8s-1.25.0: If above article doesn't help to resolve this issue please use https://bugs.centos.org/. w3-k8s-1.25.0: w3-k8s-1.25.0: w3-k8s-1.25.0: w3-k8s-1.25.0: One of the configured repositories failed (Kubernetes), w3-k8s-1.25.0: and yum doesn't have enough cached data to continue. At this point the only w3-k8s-1.25.0: safe thing yum can do is fail. There are a few ways to work "fix" this: w3-k8s-1.25.0: w3-k8s-1.25.0: 1. Contact the upstream for the repository and get them to fix the problem. w3-k8s-1.25.0: w3-k8s-1.25.0: 2. Reconfigure the baseurl/etc. for the repository, to point to a working w3-k8s-1.25.0: upstream. This is most often useful if you are using a newer w3-k8s-1.25.0: distribution release than is supported by the repository (and the w3-k8s-1.25.0: packages for the previous distribution release still work). w3-k8s-1.25.0: w3-k8s-1.25.0: 3. Run the command with the repository temporarily disabled w3-k8s-1.25.0: yum --disablerepo=kubernetes ... w3-k8s-1.25.0: w3-k8s-1.25.0: 4. Disable the repository permanently, so yum won't use it by default. Yum w3-k8s-1.25.0: will then just ignore the repository until you permanently enable it w3-k8s-1.25.0: again or use --enablerepo for temporary usage: w3-k8s-1.25.0: w3-k8s-1.25.0: yum-config-manager --disable kubernetes w3-k8s-1.25.0: or w3-k8s-1.25.0: subscription-manager repos --disable=kubernetes w3-k8s-1.25.0: w3-k8s-1.25.0: 5. Configure the failing repository to be skipped, if it is unavailable. w3-k8s-1.25.0: Note that yum will try to contact the repo. when it runs most commands, w3-k8s-1.25.0: so will have to try and fail each time (and thus. yum will be be much w3-k8s-1.25.0: slower). If it is a very temporary problem though, this is often a nice w3-k8s-1.25.0: compromise: w3-k8s-1.25.0: w3-k8s-1.25.0: yum-config-manager --save --setopt=kubernetes.skip_if_unavailable=true w3-k8s-1.25.0: w3-k8s-1.25.0: failure: repodata/repomd.xml from kubernetes: [Errno 256] No more mirrors to try. w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time." w3-k8s-1.25.0: Loaded plugins: fastestmirror w3-k8s-1.25.0: Loading mirror speeds from cached hostfile w3-k8s-1.25.0: * base: mirror.navercorp.com w3-k8s-1.25.0: * extras: mirror.navercorp.com w3-k8s-1.25.0: * updates: mirror.navercorp.com w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time." w3-k8s-1.25.0: Trying other mirror. w3-k8s-1.25.0: It was impossible to connect to the CentOS servers. w3-k8s-1.25.0: This could mean a connectivity issue in your environment, such as the requirement to configure a proxy, w3-k8s-1.25.0: or a transparent proxy that tampers with TLS security, or an incorrect system clock. w3-k8s-1.25.0: You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors w3-k8s-1.25.0: If above article doesn't help to resolve this issue please use https://bugs.centos.org/. w3-k8s-1.25.0: w3-k8s-1.25.0: w3-k8s-1.25.0: w3-k8s-1.25.0: One of the configured repositories failed (Kubernetes), w3-k8s-1.25.0: and yum doesn't have enough cached data to continue. At this point the only w3-k8s-1.25.0: safe thing yum can do is fail. There are a few ways to work "fix" this: w3-k8s-1.25.0: w3-k8s-1.25.0: 1. Contact the upstream for the repository and get them to fix the problem. w3-k8s-1.25.0: w3-k8s-1.25.0: 2. Reconfigure the baseurl/etc. for the repository, to point to a working w3-k8s-1.25.0: upstream. This is most often useful if you are using a newer w3-k8s-1.25.0: distribution release than is supported by the repository (and the w3-k8s-1.25.0: packages for the previous distribution release still work). w3-k8s-1.25.0: w3-k8s-1.25.0: 3. Run the command with the repository temporarily disabled w3-k8s-1.25.0: yum --disablerepo=kubernetes ... w3-k8s-1.25.0: w3-k8s-1.25.0: 4. Disable the repository permanently, so yum won't use it by default. Yum w3-k8s-1.25.0: will then just ignore the repository until you permanently enable it w3-k8s-1.25.0: again or use --enablerepo for temporary usage: w3-k8s-1.25.0: w3-k8s-1.25.0: yum-config-manager --disable kubernetes w3-k8s-1.25.0: or w3-k8s-1.25.0: subscription-manager repos --disable=kubernetes w3-k8s-1.25.0: w3-k8s-1.25.0: 5. Configure the failing repository to be skipped, if it is unavailable. w3-k8s-1.25.0: Note that yum will try to contact the repo. when it runs most commands, w3-k8s-1.25.0: so will have to try and fail each time (and thus. yum will be be much w3-k8s-1.25.0: slower). If it is a very temporary problem though, this is often a nice w3-k8s-1.25.0: compromise: w3-k8s-1.25.0: w3-k8s-1.25.0: yum-config-manager --save --setopt=kubernetes.skip_if_unavailable=true w3-k8s-1.25.0: w3-k8s-1.25.0: failure: repodata/repomd.xml from kubernetes: [Errno 256] No more mirrors to try. w3-k8s-1.25.0: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "The certificate issuer's certificate has expired. Check your system date and time." w3-k8s-1.25.0: /tmp/vagrant-shell: line 21: /etc/containerd/config.toml: No such file or directory w3-k8s-1.25.0: Failed to execute operation: No such file or directory w3-k8s-1.25.0: Failed to execute operation: No such file or directory w3-k8s-1.25.0: 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.

안녕하세요! 유튜브를 보다가 우연히 이 강의의 미리보기를 발견했고, 그 강의가 도움이 됐을뿐만 아니라 저에게 필요한 강의여서 강의를 수강하게 되었습니다! 현재, 필요한 부분들을 먼저 듣고 있는데 정말 많은 소스들을 제공해주셔서 저에게 도움이 많이 되고 있습니다! 감사합니다!여러가지 질문이 있어서 질문을 남깁니다!저는 24살 전공자로 졸업예정이며 취준기간은 최소 6개월에서 1년 반 정도 생각중입니다.먼저, 현재 SSAFY에 지원하려고 결정을 했는데 이 결정이 맞는지 조언을 구하고 싶습니다.저는 산업군은 정하지 못했고, 백엔드를 희망합니다. 하지만, 제가 정보보안 전공이어서 개발 관련 프로젝트가 있긴 하지만 지금까지 해온 프로젝트들 중에선 JAVA+Spring 관련된 프로젝트가 없으며 JAVA라는 언어 또한 잘 다루지 못합니다. 코딩테스트와 백엔드 개발 역량을 키워야 하는 저에게 SSAFY라는 교육코스가 도움이 될 것이라고 생각했습니다. 하지만 CS 지식을 쌓을 수 있는 시간이 있는지 1년이라는 시간동안 정해진 커리큘럼을 따라가야 하는 것이기 때문에 고민이 됐지만 긍정적인 방향으로 생각하기로 했는데요. 이 결정이 맞을까요..? 독학이나 인턴이 나을까요..? SSAFY에 지원하게 된다면 경쟁률을 생각해서 멀리 있는 캠퍼스에 지원해야 하는 걸까요..? 산업군을 선택하는 방법에 관해 듣고 싶습니다.여러 산업군들이 하는 일들을 봤는데 처음엔 핀테크, 모빌리티에 관심이 생겼는데 또 보니 다른 산업군들도 재밌어보였습니다.. 그래서 프로젝트를 직접해봐야 알 수 있는건지.. 또 다른 방법이 있는지.. 궁금합니다! 그리고 인공지능을 제외한 모든 산업군(보안포함)이 JAVA + Spring 기반인지 궁금합니다. 인턴 지원시에도 미래를 생각하여 산업군을 고려하여 선택해야 하는지 궁금합니다! 

- 학습 관련 질문을 남겨주세요. 상세히 작성하면 더 좋아요! - 먼저 유사한 질문이 있었는지 검색해보세요. - 서로 예의를 지키며 존중하는 문화를 만들어가요. - 잠깐! 인프런 서비스 운영 관련 문의는 1:1 문의하기를 이용해주세요. 항상 답변해주셔서 감사합니다.다름이 아니라 혹시 강의에서이 부분에서 꼭 /search?q= 의 형식으로 해야하는 건가요? 어떠한 정해진 양식인건가요??뒷부분에서 useLocation으로 해당 값을 확인하고 search부분을 가져와 search부분에서 q= 다음의 값을 가져오기 위해 query.get("q")를 하셨는데handleChange에서 저희가 만든 /search?q=에 의해서 값을 저런 형식으로 가져온건가요?? 어떻게 navigate에서 저 위의 경로로 저희가 만든 searchPage의 컴포넌트로 이동하는지 부터 제가 이해를 잘 못한 것 같습니다.navigate(`/search?q= 부분을 설명해주시면 감사드리겠습니다 ㅠㅠ 

안녕하세요 범 선생님! 정말 필요했던 수업인데 덕분에 잘 듣고있습니다! 컬러 팔레트 관련해서 질문 드립니다! 저같은 경우에는 라이트모드에서 primary 컬러와, 다크모드에서 primary 컬러 다르게 가져갔는데 (grayscale 컬러 빼고는 명도차이를 줬기 때문에 테마에 따라 primary, secondary, action{강의에서는 accent에 해당}, success{positive에 해당}, warning, error{negative에 해당}컬러가 전부 다릅니다.) 그렇게 될 경우엔 피그마토큰 글로벌에서 라이트모드에서의 컬러와 다크모드에서의 컬러 바리에이션값을 전부 넣어야 하나요?

/bin/bash가 쉘이다 정도로만 알고 있고 잘은 모르는데 혹시 /bin/bash가 무엇 인지하고 echo 파일에 왜 /bin/bash를 입력하셨는지 궁금합니다!

학습하는 분들께 도움이 되고, 더 좋은 답변을 드릴 수 있도록 질문전에 다음을 꼭 확인해주세요.1. 강의 내용과 관련된 질문을 남겨주세요.2. 인프런의 질문 게시판과 자주 하는 질문(링크)을 먼저 확인해주세요.(자주 하는 질문 링크: https://bit.ly/3fX6ygx)3. 질문 잘하기 메뉴얼(링크)을 먼저 읽어주세요.(질문 잘하기 메뉴얼 링크: https://bit.ly/2UfeqCG)질문 시에는 위 내용은 삭제하고 다음 내용을 남겨주세요.=========================================[질문 템플릿]1. 강의 내용과 관련된 질문인가요? (예/아니오)2. 인프런의 질문 게시판과 자주 하는 질문에 없는 내용인가요? (예/아니오)3. 질문 잘하기 메뉴얼을 읽어보셨나요? (예/아니오)[질문 내용]여기에 질문 내용을 남겨주세요.

import matplotlib.pyplot as pltimport matplotlibimport seaborn as snssns.set_style("darkgrid")def plotDateTopic(topic_id): label = "Topic #%d:\n" % topic_id label += " ".join([vectorizer.get_feature_names()[i] for i in W[topic_id].argsort()[:-6:-1]]) h = H / H.sum(1, keepdims=True) h = h[:, topic_id].ravel() plt.plot(dateNews['date'], h) plt.fill_between(dateNews['date'], h, alpha=0.5, label=label) plt.figure(figsize=(40, 10))plotDateTopic(2)plotDateTopic(0)plotDateTopic(4)plotDateTopic(13)plotDateTopic(17)plotDateTopic(9)plt.xticks(fontsize=25)plt.legend(fontsize=25, bbox_to_anchor=(0.1, 0.2))plt.show() 이렇게 식을 사용해서 데이터를 추출했더니 이런 그림이 나오는데요.주신 자료의 4) 토픽모델링의 16번은 월별로 나오는데 어떤 부분이 잘못됐는지 궁금합니다!그리고 맥에서 한글 오류가 나는 건 어떻게 수정하면 될까요?좋은 강의 감사드립니다.

스프링 시큐리티 - Spring Boot 기반으로 개발하는 Spring Security 강좌 내용을 확인하기 위해'2) 실전 프로젝트 예제 미리보기' 를 보는데, 해당 강의의 3분19초~3분 30초 사이, 4분15초 이후 부터 정상적인 플레이가 안 됩니다.확인 부탁드립니다.강의 결제 예정인데, 미리보기 강의와 결제한 강의의 동영상 플레이 품질이 같은 건가요?

print()만 쓰면 아무것도 출력되지 않을텐데라 생각해서 없애뒤에 돌려보니 좀 다르게 나오던데 그이유가 print() 자체에 \n이 포함되어 있는거였나요?? 신기하네요

김영한님 좋은 강의 감사합니다. 다름이 아니라 제가 열심히 교육 드는데,초보자라 아직 모르게 좀 많습니다. 특히 실습환경 구축 시 오류가 뜨는 경우가 제법 있는데,아무리 검토하고 복붙을 활용해도 안되는 케이스가 있던데, 이게 노트북OS마다 다르겠지만, 적어도 실습할 수 있는 환경파일이나 최근에 촬영한 실습환경 구축 영상이라도 번외로 제공해주시면 오류 문제들이 최소화될 것 같습니다. 감사합니다 :)  

메일이 안되어서 여기로 질문합니다.수업 자료가 아님에도 부탁 드려서 실례합니다.궤도차량을 보고 마음이 설레어 질문합니다.어떻게 그렇게 큰 물체와 아이의 하중을 버티고 돌릴 수 있나요? 3D 프린터로 바퀴 재료들은 만든 것 같았습니다. 근데, 3D 프린터 재료로 아이의 하중을 버틸 수 있나요?저는 또한, 궁금합니다.1.사용 센서와 아두이노를 알 수 있을까요?2.혹시, 제품의 소스 코드를 받을 수 있을까요? 불가능하다면 순서도 힌트라도 부탁합니다.3.제품 설계 과정을 알 수 있을까요? 하중 계산이나 3D 설계나 자유도 변수 설정 어떻게 했을지 너무 궁금합니다.일단, 강의 모든 과정을 수행했습니다. 필요한 부분이 있다면 더 학습하겠습니다. 글을 읽어주셔서 감사합니다. 

[질문 내용]안녕하세요! mvc2강좌에 파일 업로드 강의가 있는데 관련해서 질문드리고 싶은게 있습니다. 인프런에 질문글 작성시 drag & drop으로 사진을 첨부하여 올릴 수 있는데요.이 기능을 구현하고 싶은데 어떻게 검색해서 찾아보면 좋을까요? 개인프로젝트에 post 등록시 해당기능을 넣으면 좋을것 같단생각인데 찾아보니 방법이 너무 많아서, 영한님 강좌를 듣는걸 베이스로 하면 어떤 방법이 short cut인지 궁금합니다. 백엔드이다보니 view쪽은 부트스트랩+thymeleaf로 연명하고 있는데 javascript를 많이 써야할지도 한번 말씀해주시면 감사하겠습니다!

안녕하세요. 환불 관련 게시판 문의를 드렸는데6일째 답변이 없습니다. 고객센터 전화 번호도찾기가 힘들어서 여기 다시 남깁니다. 답변 주세요.

안녕하세요 수업 잘 듣고 있습니다.제가 자바로 안드로이드 수업을 듣고 있는데 part3, part4가 자바 수업은 없고 코틀린 수업은 있더라구요.혹시 코틀린 수업으로 수강해도 문제 없을까요? 참고로 코틀린 언어는 쓸줄 모릅니다.. 그리고 혹시 자바 part3, part4 업로드 일정이 있다면 알려주시면 감사드리겠습니다. 

토픽 모델링 중에 오류가 나서요

올려주신 https://app.diagrams.net/에서 pdf로 도표자표를 다운로드 받을려고 하니 자꾸 에러가 나서요. 9개 파일 모두 pdf로 일괄 다운로드 받을수 있게 링크 부탁드립니다.