You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If we look at the current someUTxO implementation for GYTxMonadNode:
someUTxO lang =do
addrs <- ownAddresses
utxosToConsider <- availableUTxOs
case lang ofPlutusV2->case someTxOutRef utxosToConsider ofJust (oref, _) ->return oref
Nothing-> throwError .GYQueryUTxOException$GYNoUtxosAtAddress addrs
PlutusV1->case find utxoTranslatableToV1 $ utxosToList utxosToConsider ofJust u ->return$ utxoRef u
Nothing-> throwError .GYQueryUTxOException$GYNoUtxosAtAddress addrs -- TODO: Better error message here?
We notice that the returned UTxO isn't actually removed from envUsedSomeUTxO. This seems problematic since the point of envUsedSomeUTxO is to track previously yielded someUTxOs so they aren't returned repeatedly.
As it currently stands, the field envUsedSomeUTxO is actually useless.
Expected behavior
envUsedSomeUTxO should be updated accordingly.
Additional context
Has this always been like this? I thought it used to work.
The text was updated successfully, but these errors were encountered:
As it currently stands, the field envUsedSomeUTxO is actually useless.
That is true, I think it never served any meaningful purpose and was just there in case we wanted to give it some meaning.
We notice that the returned UTxO isn't actually removed from envUsedSomeUTxO. This seems problematic since the point of envUsedSomeUTxO is to track previously yielded someUTxOs so they aren't returned repeatedly.
I think you meant that it is not added to envUsedSomeUTxOs?
Describe the bug
If we look at the current
someUTxO
implementation forGYTxMonadNode
:We notice that the returned UTxO isn't actually removed from
envUsedSomeUTxO
. This seems problematic since the point ofenvUsedSomeUTxO
is to track previously yieldedsomeUTxO
s so they aren't returned repeatedly.As it currently stands, the field
envUsedSomeUTxO
is actually useless.Expected behavior
envUsedSomeUTxO
should be updated accordingly.Additional context
Has this always been like this? I thought it used to work.
The text was updated successfully, but these errors were encountered: