Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update_nft request return error on the first start of browser app in incognito tab and send errors to console #1909

Closed
anarkiVan opened this issue Jul 11, 2023 · 2 comments
Assignees

Comments

@anarkiVan
Copy link

Describe the bug
I updated wasm module to 01bc10e and i have a problem with update_nft request.
It happens with new clear tab in browser when mm2 have never run yet.

  1. Open app in new clear tab(i.e. incognito)
  2. Import/login to wallet with nfts
  3. Send update_nft request
  4. Got an error
{
  "mmrpc":"2.0",
  "error":"DB error ErrorSaving(\"Error uploading an item: \\\"DomException { obj: Object { obj: JsValue(ConstraintError: Unable to add key to index 'chain_tx_hash_index': at least one key does not satisfy the uniqueness requirements.\\\\nundefined) } }\\\"\")",
  "error_path":"nft.wasm_storage.object_store",
  "error_trace":"nft:115] wasm_storage:362] object_store:42]",
  "error_type":"DbError",
  "error_data":"ErrorSaving(\"Error uploading an item: \\\"DomException { obj: Object { obj: JsValue(ConstraintError: Unable to add key to index 'chain_tx_hash_index': at least one key does not satisfy the uniqueness requirements.\\\\nundefined) } }\\\"\")",
  "id":null
  }
  1. send get_nft_list request
  2. got empty nft list
  3. Send after some time update_nft and get_nft_list again
  4. It works but every time i see errors in my console
    image

Please answer following questions and attach requested info - it'll help to solve issue faster

  • What OS do you use?
    Windows 11 Chrome 114.0.5735.199
  • What marketmaker version do you run?
    1.0.6-beta_01bc10e
Recording.2023-07-11.185059.mp4
@smk762
Copy link

smk762 commented Jul 22, 2023

This issue seems resolved in webdex dev branch now when using api version e72a0ab

@anarkiVan
Copy link
Author

I did not catch any errors too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants