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
This issue is between aleph-message and aleph-client.
Querying a message using get_message(item_hash) raises the exception MessageNotFoundError if the message has been forgotten. This is not clear to users since the message is found and does exist, but has been forgotten.
When using get_messages(hashes=[item_hash], ignore_invalid_messages=False), a mapping error appears from aleph-message, indicating that the item_content field cannot be parsed (obviously, since it has been deleted when forgetting the message).
We should have a way to make get_message(item_hash) either return an object of class ForgottenMessage, or raise an exception ForgottenMessageError to explicitly inform the user that the message requested has been forgotten.
The text was updated successfully, but these errors were encountered:
This issue is between aleph-message and aleph-client.
Querying a message using
get_message(item_hash)
raises the exceptionMessageNotFoundError
if the message has been forgotten. This is not clear to users since the message is found and does exist, but has been forgotten.When using
get_messages(hashes=[item_hash], ignore_invalid_messages=False)
, a mapping error appears fromaleph-message
, indicating that theitem_content
field cannot be parsed (obviously, since it has been deleted when forgetting the message).We should have a way to make
get_message(item_hash)
either return an object of classForgottenMessage
, or raise an exceptionForgottenMessageError
to explicitly inform the user that the message requested has been forgotten.The text was updated successfully, but these errors were encountered: