i get this warning ``` Diagnostics pulumi pulumi Stack proje

Question

i get this warning ``` Diagnostics pulumi pulumi Stack project factory prod lt coroutine object get project at 0x7f761ffaf448 gt main py 61 RuntimeWarning coroutine get project was never awaited a prj create RuntimeWarning Enable tracemalloc to get the object allocation traceback ```

bitter-oil-46081 · Answer

I am 100 not a python expert but I believe that the problem here is that get project actually returns a future instead of a prompt value and if you don t wait for it you ll never see the underlying value and get this error How are you using the `get project` that you defined

high-translator-22614 · Answer

yeah currently all `get ` stuff is async based coroutines

high-translator-22614 · Answer

there s discussion on github to change this because it s a pain in the butt and doesn t really provide much

high-translator-22614 · Answer

so you should probably ``` async def get project self return await gcp organizations get project project id=self project name ``` Now the weird thing is that this should still work assuming the return value got handed to pulumi

high-translator-22614 · Answer

or if you tried to use it it should have given type related errors

brief-apartment-69928 · Answer

I tried that too making it a async function but when calling that function from somewhere using asyncio run self get project gives a eventloop error

brief-apartment-69928 · Answer

Even if i try to get the same eventloop used pulumi and add this task part of that loop ``` loop = asyncio get running loop proj exist = loop create task self get project print proj exist ```

brief-apartment-69928 · Answer

this task is created as a future task but basically what i want to do is if project exist skip some task

brief-apartment-69928 · Answer

Also what is the proper way suggested to do some check like ```if proj exist `stop pulumi run` ```

high-translator-22614 · Answer

well you re supposed to use it like an Input so if you give a resource an awaitable directly or burried pulumi will resolve it

high-translator-22614 · Answer

you just need to wrap it in a task because pulumi attempts to await stuff more than once internally

bitter-oil-46081 · Answer

FWIW we are going to be landing changes over the next few days to make these `get ` methods complete synchronously <https github com pulumi pulumi pull 3019> is the core work in our runtime to support this and we ll be pushing changes out to our providers over the next few days to consume this Once this is complete these calls should behave like you d like

high-translator-22614 · Answer

because inner event loops are fun