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
The script currently registers each repo involved in the deployment process that was not already registered on the aragonPM registry by default. The particular line of code that does that: here
This is an issue cause the registration data is malformed and provoke the following RPC error: Error: Invalid JSON RPC response: ""
The text was updated successfully, but these errors were encountered:
So are we able to provide an empty repo object so the RPC request keep working? Otherwise I don’t think users will be able to publish new versions of their templates even if we handle the RPC error
The problem is with the repo of the template itself. The current script also registers the repo for the template been deployed so the content of that repo becomes malformed. Then when trying to publish a new version (e.i actually publishing the template by the user) the RPC is not able to fetch the repo causing the above error
The script currently registers each repo involved in the deployment process that was not already registered on the aragonPM registry by default. The particular line of code that does that: here
This is an issue cause the registration data is malformed and provoke the following RPC error:
Error: Invalid JSON RPC response: ""
The text was updated successfully, but these errors were encountered: