After updating near-bindgen and nearlib when trying to call one of our viewMethods through nearlib called get_all_markets
When calling the method I now get the following error:
Querying call/flux-test39/get_all_markets failed: wasm execution failed with error: FunctionCallError(LinkError("link error: Import not found, namespace: env, name: account_locked_balance")).
{
"error": "wasm execution failed with error: FunctionCallError(LinkError(\"link error: Import not found, namespace: env, name: account_locked_balance\"))",
"logs": []
}
I see that account balance locks are exposed since the last commit, is there any documentation around this?
It seems the PR (https://github.com/nearprotocol/nearcore/pull/1714) that introduces account_locked_balance is not merged into nearcore. Sorry about this. Please use the previous version of near-bindgen for now.
Here is the fix, sorry for that: https://github.com/nearprotocol/nearcore/pull/1873
Related
I deployed the contract on another computer and it worked, and now on a new envirenment and account the NEAR dApp is failing; here is the code:
https://github.com/bobmakesmagics/Multi-Near-NFT-Minter
// Get blockchian state once on component load and wallet is connected:f
nft.nftSupply(wallet.accountId)
.then(setTotalSupply)
.catch(console)
Error: [-32700] Parse error: Failed parsing args: missing field
account_id"
before I make the RPC call I actually console.log the args.. and there you see the account_id not missing... so what's the problem?
I am running an EC2 instance on aws which I need to import to pulumi by running the following command pulumi import -f resources.json.
I have the following JSON file as my resource file resource.json.
{
"resources": [{
"type": "aws:ec2/instance:Instance",
"name": "my-server",
"id": "i-08f92a261a2ef6650",
"ami": "ami-0fdb3f3ff5d7c40db"
}
]
}
But get the following error:
aws:ec2:Instance (my-server):
error: aws:ec2/instance:Instance resource 'my-server' has a problem: Missing required argument: "instance_type": one of `instance_type,launch_template` must be specifie
d. Examine values at 'Instance.InstanceType'.
error: aws:ec2/instance:Instance resource 'my-server' has a problem: Missing required argument: "launch_template": one of `ami,instance_type,launch_template` must be sp
ecified. Examine values at 'Instance.LaunchTemplate'.
error: aws:ec2/instance:Instance resource 'my-server' has a problem: Missing required argument: "ami": one of `ami,launch_template` must be specified. Examine values at
'Instance.Ami'.
error: Preview failed: one or more inputs failed to validate
This is a bug, please see this GitHub issue:
https://github.com/pulumi/pulumi-aws/issues/1605
and this one: https://github.com/pulumi/pulumi/issues/7160#issuecomment-912093311
The best workaround at this stage is to define the EC2 instance in your code, and then set the import resource property as defined here
I am quite stuck in including Aurelia-Bootstrap-Datetimepicker and aurelia-datatable in my project. I have followed these two tutorials word by word:
https://www.npmjs.com/package/aurelia-bootstrap-datetimepicker
https://www.npmjs.com/package/aurelia-datatable
Unluckily in both of them I am getting same issue:
Unhandled Promise Rejection: Error: Unable to find module with ID: aurelia-bootstrap-datetimepicker
Unhandled Promise Rejection: Error: Unable to find module with ID: aurelia-datatable
I have observed that this error comes by including plugin in main.ts, like:
export function configure(aurelia: Aurelia) {
aurelia.use
.standardConfiguration()
.plugin(PLATFORM.moduleName('aurelia-validation'))
.feature(PLATFORM.moduleName('resources/index'))
.plugin('aurelia-bootstrap-datetimepicker');
aurelia.use.developmentLogging(environment.debug ? 'debug' : 'warn');
if (environment.testing) {
aurelia.use.plugin(PLATFORM.moduleName('aurelia-testing'));
}
aurelia.start().then(() => aurelia.setRoot(PLATFORM.moduleName('app')));
}
Is there any developer who have successfully configured both of these in his/her project? I could create a gist or something to share more stuff..
Or suggest me some other tutorial to follow for meeting both purposes.. Any help would be highly appreciated.
Since you're using Aurelia with Webpack,try to init the plugin with
.plugin(PLATFORM.moduleName('aurelia-bootstrap-datetimepicker'));
I'm working on a lambda function and when I try to invoke it I get the following error
"errorMessage": "Cannot find module 'semver'".
details
Unable to import module 'dist/index': Error
If I add semver to package.json then it works fine. This started happening suddenly. A bit of background information, I'm using a monorepo with yarn and lerna.
Thanks for reading my question in advance. I am just start to use graphql and prisma following this tutorial.
I have the following Error when Deploying the Prisma database service:
Error: No cluster set. Please set the "cluster" property in your prisma.yml
at /Users/judy/howtographql/server/node_modules/graphql-config-extension-prisma/src/index.ts:89:11
at step (/Users/judy/howtographql/server/node_modules/graphql-config-extension-prisma/dist/index.js:40:23)
at Object.next (/Users/judy/howtographql/server/node_modules/graphql-config-extension-prisma/dist/index.js:21:53)
at fulfilled (/Users/judy/howtographql/server/node_modules/graphql-config-extension-prisma/dist/index.js:12:58)
at <anonymous>
error Command failed with exit code 1.
ERROR: "playground" exited with 1.
error Command failed with exit code 1.
I looked over the tutorial to find that there is nothing about how to set the cluster. I wonder how to fix this problem.
The default prisma.yaml is:
# the name for the service (will be part of the service's HTTP endpoint)
service: hackernews-graphql-js
# the cluster and stage the service is deployed to
stage: dev
# to disable authentication:
# disableAuth: true
secret: mysecret123
# the file path pointing to your data model
datamodel: datamodel.graphql
It could be just that you may have entered an incorrect endpoint address. Please refer https://github.com/prisma/graphql-config-extension-graphcool/issues/8