You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Question]: Recent need for API key undocumented in this repo #12589
Hi @dls314!. Thanks for the question. The root cause of the 500 error was that each fileId is valid only once, so subsequent requests tried to access a file that had already been deleted. Because the code attempted to read the file before checking whether it still existed, it triggered an exception instead of returning the intended 404. The prepared fix #12651 adds a proper null/filename check, removes file from map and returns 404 when the file has already been consumed, ensuring the response now matches the documented behavior. The fix will be included in the next release.
Activity
[-][Question]:[/-][+][Question]: Recent need for API key undocumented in this repo[/+]daniel-kmiecik commentedon Nov 17, 2025
Hi @dls314!. Thanks for the question. The root cause of the 500 error was that each fileId is valid only once, so subsequent requests tried to access a file that had already been deleted. Because the code attempted to read the file before checking whether it still existed, it triggered an exception instead of returning the intended 404. The prepared fix #12651 adds a proper null/filename check, removes file from map and returns 404 when the file has already been consumed, ensuring the response now matches the documented behavior. The fix will be included in the next release.