I was stuck on step 11 and couldn’t get the step to pass. I came across this post here and realized I had the same issue this poster had. The question I have is why does the answer have to be this specific? Wouldn’t that app still work with the function body and semi-colon?
We should open an issue for this.
Can you clarify though what you thought should work?
Subject: Help Needed with Docker Pull Rate Limit Error
Message:
Hi hbar1st,
I’m encountering an issue while working on the challenge “Learn Relational Databases by Build a Celestial Bodies Database.” Every time I try to pull the image gitpod/workspace-postgres
, I receive the following error:
Error: 13 INTERNAL: cannot resolve image: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/gitpod/workspace-postgres/manifests/sha256:4273247fd39ecd9d0186e133fe7f8955cabf56982d8d5634df20c0f7091bebc3: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: Understanding Your Docker Hub Rate Limit | Docker
It seems that I’ve exceeded Docker Hub’s pull rate limit, and I’m unsure how to proceed. I’ve tried several times but keep getting the same error.
Could you please assist me in resolving this issue? Any guidance on how to bypass this limit or alternative approaches would be greatly appreciated.
Thank you for your help!
Best regards,
paker
it was something like
const dataArrIndex = taskData.findIndex((item) => {
item.id === currentTask.id;
});
Would you like to go ahead and open an issue for the developers to discuss this on GitHub? Info below:
Thank you for helping make FCC better. Bugs can be reported as GitHub Issues. Whenever reporting a bug, please check first that there isn’t already an issue for it and provide as much detail as possible.
I can do that. But, before I do would you agree this should pass the step? Don’t want to go to them and have them point out something blatantly obvious that I missed.
yes your code should pass because the step didn’t explicitly ask for an ‘implicit return statement’.
Issue logged. Thanks for posting that GitHub Issues list I didn’t know that existed!