search

deltaDAO / nautilus

The Data Economy TypeScript Toolkit
https://nautilus.delta-dao.com
Apache License 2.0
4 stars 2 forks source link

[BUG] empty computeStatus response caused by different provider #111

Closed Abrom8 closed 5 months ago

Abrom8 commented 5 months ago

Nautilus asks the configured provider and not the asset's provider for its status. This results in an empty/undefined response if the provider of the assets is different from the nautilus config:

    algoDID: 'did:op:926098d058b017dcf3736370f3c3d77e6046ca6622af111229accf5f9c83e308',
    inputDID: [
      'did:op:55939e969f36d6879d1f9c1ebd0b51f8a4d7c0673a84c050b21224840e997ec7'
    ]
[compute] Retrieve job status: {
  jobId: 'e2b3c4445d7e4ee18ce38ed4311b82a1',
  providerUri: 'https://provider.dev.pontus-x.eu', // should be https://dd1.provider.dev.pontus-x.eu
  account: '0x96F7eD242f58FAbb0d4EB5AD6C8301582447d136'
}

Should be defined:

[compute] computeStatus response:  []
Compute Job Status:  undefined