When uploading the wasm binary, as a compiled smart contract on the 'ink-workshop' - the canvas-ui that I am running just errors.
Canvas-ui error:
Uncaught error. Something went wrong with the query and rendering of this component.
Cannot read properties of undefined (reading 'args')
Step: 'Drag the flipper.contract file that contains the bundled wasm blob....'
The Github issues section associated is read-only, hence why I am posting here. Anyone know what might be the problem here?
Incase others are wondering what to do in this instance. I was able to deploy using the official polkadot web interface.
Connect your local running node via settings and there you can deploy your flipper contract.
This is a good article on the astar network docs on how to do it, using the basic flipper contract example.
There is a maintenance problem and they wanna fix it.
https://github.com/paritytech/canvas-ui/issues/119#issuecomment-1020114242
Related
We have a Cloud Service that we have been deploying/updating without issue. In the past two weeks every time we try to deploy the package we are getting the error "Deployment could not be created - There was an error processing your request. Try again in a few moments".
I am at a loss as to how to even debug the issue to get more detail. if anybody has any advice on how to get a better error description would be appreciated.
The only changes in this deployment are some changes to the static files in the package so it is unclear what is causing the issue. The process we use is (1) build the package, (2) upload the package, (3) deploy in the staging environment. The package gets uploaded but fails to deploy (step 3).
Any help as to what the issue is or how to get better diagnostic information woudl be great.
Hey guys attempting to test deployment of the example api get contract provided in chainlink docs. Is there a reason why
https://docs.chain.link/docs/make-a-http-get-request/
fails to deploy?
Even when using a polygon supported oracle and job id? Is something wrong with the v8 example contracts? compiles fine, but cannot deploy -
execution reverted
.
Initially I modified using it as a base example for my own version. That failed and now revisiting the original contract, this fails too. Telling me that there is an issue with this v8 example.
There are no changes to the contract in the link. Copy paste into remix and attempt to deploy to polygon main net. Execution reverted
Thanks!
need to set chainlink token and comment out constructor function of
setPublicChainlinkToken();
I'm trying to push a Laravel installation from development to a live-environment on a Laravel Forge-server. When pushing, I'm getting an error, that I'm not getting on my local environment.
I can't figure out, how I connect directly to the provisioned server (through FTP or SFTP), to change single files manually (to debug).
Which means that in order to try something, then I need to make a new commit and an entirely new deployment, for every thing I want to test. Quite tedious and it clutters my git history!
... I can't even do a commit --amend, since that gives me the error:
fatal: refusing to merge unrelated histories
Attempt 1) I can't find anything about it in the Forge knowledge base.
Attempt 2) I've found several articles talking about a good guide, but that guide gives an error 404:
It's this one: https://freek.dev/2016/03/let-your-clients-use-sftp-on-a-forge-provisioned-server/
Am I missing something obvious? Or is the commit-n-push really the way to go? Is this normal for automated deployment systems?
For others who find this question, then Forge-support got back to me really quickly and linked to this blogpost, explaining how to get sftp-access to a Forge-provisioned server
What I did wrong, was that I didn't use the username: forge (I was using my email).
I am trying to get the NagVis module working with Icinga2, but after following the installation guides for both NagVis and the Icinga2 module, I am getting
The requested URL /nagvis-sys/frontend/nagvis-js/index.php was not found on this server.
When I go onto the module on the UI.
I also cannot navigate to the nagvis ui outside of icinga2.
I have looked at this topic here: Issues with Icingaweb and Nagvis integration after moving to root but I do not really understand the solution, and I have tried to follow it, and it still does not work.
I should mention that I am working inside the docker image of IcingaWeb2, not a normal installation.
Any help would be greatly appreciated.
I tried to deploy my project with capifony, becouse I found here an answer, that with capifony deployment is easy. Well I don't think it is, so my question is:
How can I deploy my project via ftp, I put all my files on the server but even if I browse to web/app.php, the only thing I get is an empty page, whatever route I write in the url. So someone please explain me how can I get this work! Thank you!
A couple of things to think of when deploying a Symfony2 project to a new server or computer (as far as I've encountered) might be:
Make sure that the server and it's PHP installation meets the Symfony2 requirements (and perhaps also the recommendations)
Check that you've somewhat followed the installation instructions (found here)
Try to clear the cache
Make sure that the web server and it's PHP process have write permissions to the cache folder
If none of these helps, try to modify the app_dev.php to temporarily allow access from your current (client) IP (instead of restraining it to localhost). Then, hopefully, you'll get a more useful and detailed error message, instead of the blank page (which often is caused by some fatal error that have occurred during the initialization of the framework and its kernel)
Update: Noticed now that you've tagged your question with 'windows', but that you don't mention which server you're trying to deploy to. I wrote the above with some *nix based server in mind, but hopefully some of it are applicable to Windows servers too (but there might be other common sources of error running under Windows that I'm not familliar with