I deployed a contract with truffle on the mainnet and it's been successfully verified(here's the contract https://etherscan.io/tx/0xeb0a0f698d0e6a0081c6d95a4e03175d61582115f920fdf4acd7e77ba40136a5). So i payed for the gas and it should be deployed by now but whenever i try to use it in the truffle console(let instance = await MyContract.deployed(); i get
Uncaught:
Error: MyContract has not been deployed to detected network (network/artifact mismatch)
Why is that? I payed for the deployment. What else truffle needs?
Truffle suite is very buggy . I myself have been having issues with truffle from time to time . So i highly recommend for you to move to hardhat instead.
Related
deployed Lumen micro services using azure devops and suddenly it started giving 500 internal server error after successful deployment.
Set the same package version on deploying to Azure App Service as the package version that worked locally, for local environment.
App Service runs your app in production mode, so you need to make sure that your project works as expected in production mode locally. Depending on your composer.json, different packages may be installed for production mode (require vs. require-dev).
Thanks, for the answers but I got it fixed by adding flag --ignore-platform-reqs to composer install in yml file.
My firebase hosting deployments have suddenly started failing both in my Github CI Workflows and from my local machine.
$ firebase deploy --only hosting
=== Deploying to '<project>'...
i deploying hosting
Error: Failed to list functions for <project>
The project in question does not have any functions, and only hosts a static site. Google searches for "Failed to list functions" turn up empty, it seems like not a common problem. The only leads I can find indicate some kind of network error.
I have updated my firebase-tools, logged out and in again to generate a new CI token, tried the process from my Github workflows and also manually from my machine, all to the same effect.
I can't find any information about this problem, except that the error seems to come from this part of the firebase-tools codebase:
https://github.com/firebase/firebase-tools/blob/c0f19a32845135108c75a1050024965cb1e3f52d/src/gcp/cloudfunctions.ts
My firebase tools version was 11.14.0. I changed that to 11.13.0. Installed this specific version through npm install -g firebase-tools#11.13.0. After that I could successfully deploy.
I came across the issue. using firebase-tools version 10.5 or upgrading it to blaze plan fixed my issue
I had deployed the app last on friday and it got deployed successfully.But since, today morning the deployment is not happening at all.It is checking for conflicting process and failing.
I'm doing this from the webide and i'm not able to check what are the conflicting process and how to resolve it.
WebIDE lacks the ability to do proper investigation on deploying apps to SAP Cloud Foundry.
The best way to do this is to install the Cloud Foundry Multi-apps plugin (see this tutorial). This will allow you to use the local terminal to control the deployment (or alternatively use SAP Business Application Studio which already has the commands built in).
Then use the command cf mta-ops to get the list of ongoing operations and cf dmol <operation_id> to download the logs for that operation. cf deploy can be used to abort/retry operations.
I tried to launch our Scala application on the Swisscom Cloud Foundry (CF) infrastructure. To do so, the matching Heroku buildpack was used:
https://github.com/heroku/heroku-buildpack-scala
As this did not work, I tried to deploy the 'hello-scala' example using this buildpack.
My fork to be able to build the slightly outdated example:
https://github.com/AlwinEgger/hello-scala
I have to underline that I am fetching the port I have to use as env variable 'PORT'.
Unfortunately, there is not much on the log. "failed to accept connections within health check timeout" message indicates that there is no one listening...
My questions: Did anyone succeed in deploying Scala apps on CF infrastructures (# Swisscom)?
A workaround I found:
I'm not using the scala- but the java-buildback. This with the major advantage and inconvenience that the project is not any more build on the instance.
Advantage: It speeds up the whole process considerably
Inconvenience: A build server is needed
So what do we have to do?
An example may be found here (this is the actual application):
https://github.com/OpenOlitor/openolitor-server
Add the sbt-native-packager to your project
Execute the action 'universal:packageBin' building by hand or configure your build server to do so
Change the buildpack in the manifest.yml and add some parameters, if necessary. Configure the path of the artifact to deploy.
Run cf push or let the build server do so.
It seems to me like the latest code that I submitted to WSO2 App cloud is not deployed. I tried to access the jenkins server (https://jenkins.cloud.wso2.com/t/cleancoders/webapps/jenkins/job/draft-trunk-default/) I see there that the latest code is built(upto build 29) but on the App cloud still build 24 is deployed. It seems to like the jenkins builds are not synced and deployed.
I also tried to build and deploy manually but It seems that it is not having an effect.
Please suggest what should be done in order to deploy the latest build.
Thanks in advance.
This is a kind of problem which you can get when your app is not properly deployed in jenkins. (There may be configuration issues). Please do contact cloud#wso2.com for assistance.