Sealed variables aren't available to container

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

b4d5b2fe-0269-4ddf-8196-c06381b56b14


a year ago

I wasn't able to reproduce this, if you are able to, i would greatly appreciate steps.

1292918579523752000
1292918579792052200


working fine now 👍


a year ago

we haven't done anything, so I can only assume this was somehow with your app


I think I ran a deployment on an old snapshot somehow


anyways, solved, will mention again if I come accross it ¯_(ツ)_/¯


a year ago

sounds good



happened again


deploy id: 49f57125-1398-484a-bd71-aeff067b627c


(look at the red error, rest is just me messing with config)


application-secret=${APPLICATION_SECRET}

APPLICATION_SECRET being a sealed variable.


a year 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?


it happens pretty randomly, re-deploying worked fine


no idea what's going on, or any good way to trace what's going on


looks like someone else did have this issue a while ago though: https://discord.com/channels/713503345364697088/1287718233331339347/1287736542663671912


a year ago

I stand corrected, thank you


a year ago

I'll try to whip up something to test for this


if there's anything you can think of to enable me to help, feel free to shoot


a year 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


https://railway.app/project/b4d5b2fe-0269-4ddf-8196-c06381b56b14/service/54c990ec-cd3c-440e-8c0a-00c5428b81a2?id=f92b7a48-2d1f-4d9e-b184-303eed5255be

environment: staging ("2d8278ac-9087-4a7c-aa19-0f0f0959ec35")

variable:
32 numeric (e.g. 30262362628612951243030485761496)


a year ago

perfect


it's inconsistent, first time it's popped up in a few days, so yeah, seems difficult to reproduce


gl <:kekw:788259314607325204>


a year ago

ill test every minute


a year ago

how often do you deploy?


atm - in fairly early dev, so, more often than I'd like to:

https://i.imgur.com/cMgsr03.png


a year 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.


have a hunch that it happens when you set a variable & seal it in the same post request


managed to repeat it that way


a year ago

oh yeah?


a year ago

could not reproduce


a year ago

can you send detailed steps please


Loading...