traces not showing up / finishing | Dagger | Page 1

open girder Jun 13, 2024, 4:41 PM

#

👋 sorry to hear! do you have a link to affected traces? (you can DM me if you want to keep it private)

mellow pasture Jun 14, 2024, 6:40 AM

#

https://dagger.cloud/Safespring/traces/2368d67a02af6e04783b6c9823e8c8d4 here is an example of one that is still running according to the ui but the job itself failed yesterday

open girder Jun 14, 2024, 3:42 PM

#

mellow pasture https://dagger.cloud/Safespring/traces/2368d67a02af6e04783b6c9823e8c8d4 here is ...

ah, did the build time out in CI? that can sometimes cut off the telemetry going to Cloud, and our background job that cleans those up has been going haywire for a bit, we've got a fix in progress

mellow pasture Jun 14, 2024, 4:54 PM

#

No it didn’t time out. More likely that the code panicked(still under dev). Would that cause the same thing?

open girder Jun 14, 2024, 5:29 PM

#

Yeah could do - the session CLI might have been stopped ungracefully

#

Make sure you do a defer client.Close() (assuming Go SDK?)

#traces not showing up / finishing