Rishabh - @DOPΣ Why are we still seeing the 404...
@DOPΣ Why are we still seeing the 404 pages even after saving the package? I don't know how long this has been going on.
Dtbh im not able to repro it, its working fine for me
the issue with that is your package release isnt created, idk if why your browser didnt sen t that request, or you navigated earlier while load
tbh i need suggestion how should i handle that, where pkg request is succesfull but create pkg release and uploading files request is terminated somehow by user
the issue with that is your package release isnt created, idk if why your browser didnt sen t that request, or you navigated earlier while load
tbh i need suggestion how should i handle that, where pkg request is succesfull but create pkg release and uploading files request is terminated somehow by user
Dor if its consistently failing for you, kindly send network request response
RI didn't navigate early, when I press the package should be created and release should also be sent
Dpkg is created, as we can see on your profile, but release isnt, cos browser didnt sent req? or you didnt wait longer, idk really
is it consistently failing for you or just exception rn?
is it consistently failing for you or just exception rn?
RI have created multiple packages and all of those show 404, cause the release didn't create
Dit would be good if you send network requests, im unable to repro ;/ apologies
RMy personal org was misconfigured I don't know how. It was because of that the release failed with forbidden
D
umm yeah it not always frontend errorRI my defence the error message could have better haha
DYeah I can modify axios handle to show toast for 403 just like 401
Sgood debugging, 404s are painful so maybe we can even show historical failed network requests or something (I think we can track network requests?)