2 years ago
Seems like my variables aren't being made available to the container when I'm sealing 'em. Value becomes null (or doesn't make it to the container at all - not sure which) and throws errors as a result.
33 Replies
2 years ago
b4d5b2fe-0269-4ddf-8196-c06381b56b14
2 years ago
I wasn't able to reproduce this, if you are able to, i would greatly appreciate steps.


2 years ago
working fine now 👍
2 years ago
we haven't done anything, so I can only assume this was somehow with your app
2 years ago
I think I ran a deployment on an old snapshot somehow
2 years ago
anyways, solved, will mention again if I come accross it ¯_(ツ)_/¯
2 years ago
sounds good
2 years ago
happened again
2 years ago
deploy id: 49f57125-1398-484a-bd71-aeff067b627c
2 years ago
(look at the red error, rest is just me messing with config)
2 years ago
application-secret=${APPLICATION_SECRET}APPLICATION_SECRET being a sealed variable.
2 years ago
we have just under 400 sealed variables, and this has been the only report, leading me to believe its an issue with your app, do you have any way to show that this isn't an issue with your app?
2 years ago
it happens pretty randomly, re-deploying worked fine
2 years ago
no idea what's going on, or any good way to trace what's going on
2 years ago
looks like someone else did have this issue a while ago though: https://discord.com/channels/713503345364697088/1287718233331339347/1287736542663671912
2 years ago
I stand corrected, thank you
2 years ago
I'll try to whip up something to test for this
2 years ago
if there's anything you can think of to enable me to help, feel free to shoot
2 years ago
deep link to the affected service, and what environment it's in, and if you could provide a similar variable to what you have sealed, same format, character set and length that would be helpful
2 years ago
environment: staging ("2d8278ac-9087-4a7c-aa19-0f0f0959ec35")
variable:
32 numeric (e.g. 30262362628612951243030485761496)
2 years ago
perfect
2 years ago
it's inconsistent, first time it's popped up in a few days, so yeah, seems difficult to reproduce
2 years ago
gl <:kekw:788259314607325204>
2 years ago
ill test every minute
2 years ago
how often do you deploy?
2 years ago
atm - in fairly early dev, so, more often than I'd like to:
2 years ago
update here, i started running a test script about 12 hours after this convo every minute (auto redeploy), i have yet to receive any notifications that the sealed variable was undefined.
2 years ago
have a hunch that it happens when you set a variable & seal it in the same post request
2 years ago
managed to repeat it that way
2 years ago
oh yeah?
2 years ago
could not reproduce
2 years ago
can you send detailed steps please