#approval smoke

1 messages Β· Page 1 of 1 (latest)

worthy lake
#

I reproduced this locally on current main.
The direct gateway approval RPC path works. The approval request is created, resolve with allow-once succeeds, and waitDecision returns allow-once.
The provider chat flow reproduces the issue. The approval is shown as pending and resolve with allow-once succeeds, but the later waitDecision call fails with INVALID_REQUEST: approval expired or not found.
The command still finishes afterward and smoke appears through the follow-up run. So the visible result can look successful, while the gateway still logs the failed waitDecision.
I only tested current main locally in this run.

grave ibex
#

ok cool - if you can try using telegram too just to validate it breaks there too

worthy lake
#

Is a shaped local repro ok for u ?

#

Telegram-shaped local test also reproduces it.

Turn source was telegram, resolve with allow-once succeeded, then waitDecision failed with INVALID_REQUEST: approval expired or not found.

Smoke still appeared afterward through the follow-up path.

grave ibex
#

Thank you

worthy lake
#

Hope it could help u.

grave ibex
#

what is ur github @?

worthy lake
#

For what do u need it when i can ask for that ? xD

grave ibex
#

to credit you and say thanks for the help testing :)

@timid sapphire when we fix ^^ would be nice :)

timid sapphire
grave ibex
#

Sounds good - let me test it with slack, discord and webui to validate

worthy lake
#

Thx for the Credit on fix. Can i close this since Fix is done ?