Open FlacoJones opened 1 year ago
Most of them, [address.js]3, 4 or 6 come from getServerSideProps of the contract page - would seem to me that there were hiccups when getting the data (3: get bounty from API, 4: fetching issue from Github and 6: getting a bounty from subgraph)
Was able to reproduce part of these locally by just entering a wrong bountyId and address in the link for the contract - so part of it could have been just accidentally deleting a character from the contract link when moving between bounties:
Specifically on the prod messages:
One of the messages says "OpenQ could not find a contract with address: 0xc450b7d396e53f2f64b77b0598624b010368157f" and indeed, when checking the graph it seems like this bounty is non-existent... does it exist in our database? (unsure how to check this on staging or prod)
The other message with the id of "mdu6sxnzdwu2odixmdu1mze=": it seems the code was trying to fetch an issue by that id, but there is no issue with that id to be found on GitHhub
But maybe in both cases there might be a close enough id / address?
One of the messages says "OpenQ could not find a contract with address: 0xc450b7d396e53f2f64b77b0598624b010368157f" and indeed, when checking the graph it seems like this bounty is non-existent... does it exist in our database? (unsure how to check this on staging or prod)
No it doesn't exist in our db, its the one that was up there before Eth Denver. I'll try to complete it for them over the weekend and, if possible get them to mint a new contract, then blacklist the old one in the api.
These are some error logs with line identifiers from the past day in prod - any ideas on what might be causing them, if they're serious or not, and how we can address them?