keyko-io / filecoin-verifier-frontend

9 stars 4 forks source link

[ Bug Report ]The bot large-datacap-requests do not create DataCap Allocation requested after triggering #818

Closed Sunnyiscoming closed 1 year ago

Sunnyiscoming commented 1 year ago

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

  1. Go to https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/2102
  2. Enter

    Datacap Request Trigger

    Total DataCap requested

    1PiB

Expected weekly DataCap usage rate

10TiB

Client address

f1ys5m675da4ao4vwefbewtyafuw3zhgemya6jnky

Click on Comment

  1. Scroll down to https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/2102
  2. See error

Expected behavior The bot large-datacap-requests create

DataCap Allocation requested

Multisig Notary address f02049625

Client address f1ys5m675da4ao4vwefbewtyafuw3zhgemya6jnky

DataCap allocation requested 5TiB

Id

Screenshots image

Desktop (please complete the following information):

Sunnyiscoming commented 1 year ago

https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/2107 https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/2106 The same problem exists in the above issues.

fabriziogianni7 commented 1 year ago

hey @Sunnyiscoming please have a look at this: https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/2102#issuecomment-1647606802

I had to add efil identifier in the issue.

Schermata 2023-07-24 alle 12 06 42

the same solution can be applied to the 2107 and 2106

please just update the parent comment of the issues with "efil" under Identifier field

kevzak commented 1 year ago

Not EFil @fabriziogianni7

kevzak commented 1 year ago

https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/2102#issuecomment-1652511855

comment from notary who signed. he had to use v3 credentials

clriesco commented 1 year ago

Couldn't reproduce the failure in dev environment. The codebase does not present bugs related to this issue, so most likely it is due to some infrastructure problem.