#v3 spinning

1 messages · Page 1 of 1 (latest)

astral raptor
#

I was chatting to a Jeremy on web chat, but the web chat is presently broken and now no longer showing the conversation when I click on it.

To Jeremy: I was able to get it by navigating to the home page of dagger.cloud and navigating to my build, but for me at least the deep link from the client to the build is redirecting me to a v3 page with a spinning load icon and no further loading.

paper ridge
#

cc @exotic vigil

astral raptor
#

I can get a har if it happens again

exotic vigil
#

Would appreciate checking console logs next time - I suspect there's an unauthorized error being returned somewhere

paper ridge
#

Thanks, @astral raptor. So the v3 link was coming from "deep link from the client to the build"...do you mean the TUI?

Wondering what version of the Dagger CLI you're on.
dagger version
because for me on 0.15.3 I don't get a v3 link:

#

Or maybe you have a link like mine that is doing a quick redirect to v3

#

which is what mine does https://v3.dagger.cloud/my-actions-org/traces/4aaf3d262e16164629f680fc4d100407

exotic vigil
paper ridge
astral raptor
#

yeah, my link is from 0.15.3, and it's a v2 link. I clicked over to the v3 interface manually, and I suppose that set a user setting to always redirect to v3 from there forward

#

one sec bringing one of the links up again and capturing console

#

it appears that I'm now logged in properly because I'm not hanging with the v3 UI

proper vessel
#

i hit some of these auth issues and endless spinners myself, but had assumed it was something to do with dagger-engineer level accesses.... if you check the console with endless spinner up, do you have any errors that look like this?

[Error] error fetching org dagger input: org.subscription unauthorized
input: org.subscription unauthorized
input: org.members unauthorized
input: org.members unauthorized
input: org.invites unauthorized
input: org.invites unauthorized

    (anonymous function) (recorder.js:1:104034)
    syscall/js.valueCall (wasm_exec.js:356)
    <?>.wasm-function[syscall_js.valueCall]
    <?>.wasm-function[syscall_js.Value.Call]
    <?>.wasm-function[syscall_js.__Value_.Call]
    <?>.wasm-function[github.com_maxence_charriere_go_app_v10_pkg_app.value.Call]
    <?>.wasm-function[github.com_maxence_charriere_go_app_v10_pkg_app.__value_.Call]
    <?>.wasm-function[11129]
    <?>.wasm-function[11127]
    <?>.wasm-function[22205]
    <?>.wasm-function[wasm_pc_f_loop]
    <?>.wasm-function[wasm_export_resume]
    _resume (wasm_exec.js:545)
    (anonymous function) (wasm_exec.js:556)
[Error] Failed to load resource: the server responded with a status of 404 () (f32adf9c0c87f6a0f86c5adcf6282a144615060de46e5dffb337ca6aa7e2fd90.map, line 0)
proper vessel
#

hit this again just now, backing out to dagger.cloud will give a login page, then reloading the trace works

astral raptor
#

unfortunately it only did this until I hit the front page of dagger.cloud then it all started working

exotic vigil
exotic vigil
astral raptor
exotic vigil
#

@astral raptor the fix is out, so next time it comes up it should be fixed by a hard refresh (it probably loaded the cached broken version that time, the cache is very sticky)

astral raptor
#

might want to add a version hash to your resources

exotic vigil
astral raptor
#

ah alright

proper vessel
sacred hawk
#

I had this issue when I was logged out of dagger cloud.