#taha_code
sharp nightBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1347646108825817240
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
valid chasm
Hi, I'm asking a teammate for help as they have more expertise with Terminal. Thank you for your patience.
flint harbor
Hello! I don't know for sure, but I believe when it hits 65% it's waiting for a response from the reader, and that response depends on the reader doing some work that takes a bit of time. It only progresses further when it hears back that those things are done.
south agate
I have noticed that the reader probably reboots as the lights on the reader starts flashing
flint harbor
Ah, yeah, that could be.
south agate
Is it a normal process to wait for the response from the reader at a specific percentage? because as I mentioned it starts smoothly and once the flashing lights are turned off it finishes smoothly as well.
flint harbor
Yeah, that sounds normal to me. I don't think anything is wrong or unusual if that's what you're worried about.
south agate
and during the period of rebooting does the reader makes a new connection or does it disconnects from its previous connection?
flint harbor
I'm honestly not sure. It might reestablish the connection. This isn't really stuff you need to worry about, though. Can you tell me more about why you're interested in the specifics of the update process? Are you running into issues?
south agate
Well the issue I am facing is that I am making the user wait for the updates to complete by showing them a wait message everytime I receive the callback with progress but the process breaks after after waiting sometime which is after 65%
flint harbor
I recommend you show them an indeterminate "working" message/graphic, like a circular spinner instead of a progress bar.
south agate
I am trying it understand is there any way to reduce that time of waiting?
flint harbor
No, there's no way to change this. The update takes as long as it takes, and it's not going to be a smooth progression from one point to the next.
south agate
Alright, Thank you for your help