Error in event handler: Error: Failed to read the 'cssRules' property from 'CSSStyleSheet': Cannot access rules
enter image description here
Error in event handler: Error: Failed to read the 'cssRules' property from 'CSSStyleSheet': Cannot access rules
at findStyleSheets (chrome-extension://diebikgmpmeppiilkaijjbdgciafajmg/scripts/content-script.js:1014:12)
at chrome-extension://diebikgmpmeppiilkaijjbdgciafajmg/scripts/content-script.js:1052:13
Related
I'm creating accounts using the json rpc for NEAR but when things fail, there isn't really an error that is passed back, so I'm unable to catch anything.
The object with key status is a test, this is returned after the function call has finished, but if there are no errors to catch, I can't tell if anything failed.
How are you catching errors here.
Receipts: 4epNvrYNDK2u4p7K4RKMqbqmoV6WMKjCFtE926uiTQEu, HMnN8FXcJVT4PjQxi5RAmBLLRn2gNaZwgDkNKXX66jj5
Failure [myaccount.mintspace2.testnet]: Error: {"index":0,"kind":{"ExecutionError":"Smart contract panicked: panicked at 'Failed to deserialize input from JSON.: Error(\"missing field `receiver_id`\", line: 1, column: 79)', store/src/core.rs:41:1"}}
{
status: 'success',
}
I am trying to build a simple coin flip game in solana.
Full code here
I get this error:
Error: failed to send transaction: Transaction simulation failed: Error processing Instruction 0: custom program error: 0x0
I followed some tutorials on how to use PDA's but couldn't find a report/workaround to an error as such.
Tests are running on localhost
I did some research and it might be that the account was already initialized ( maybe, no idea)
the part that is giving the error:
try {
await program.rpc.initialize(bump,
{
accounts: {
treasury: treasuryPda, // publickey for our new account
user: provider.wallet.publicKey,
systemProgram: SystemProgram.programId // just for Anchor reference
},
});
} catch (error) {
console.log("Transaction error: ", error);
console.log("blabla:", error.toString());
}
I'm new in blockchain, smart contract and near protocol. I'm trying to learn from https://near.academy/ . There's a sample contract on testnet : museum.testnet.
I'm using windows and i installed wsl2.
I can login with
near login command. But after that, when i called near view museum.testnet getmemecount command its giving me error below. Can anyone help me on this?
View call: museum.testnet.getmemecount()
An error occured
Error: Querying [object Object] failed: wasm execution failed with error: FunctionCallError(MethodResolveError(MethodNotFound)).
{
"block_hash": "SZv8UsCeNXLkhjPa9KeZY6xJXmKNb6MLyKXqHVddiT5",
"block_height": 65109663,
"error": "wasm execution failed with error: FunctionCallError(MethodResolveError(MethodNotFound))",
"logs": []
}
at JsonRpcProvider.query (/home/cinar/.nvm/versions/node/v14.18.0/lib/node_modules/near-cli/node_modules/near-api-js/lib/providers/json-rpc-provider.js:116:19)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at async Account.viewFunction (/home/cinar/.nvm/versions/node/v14.18.0/lib/node_modules/near-cli/node_modules/near-api-js/lib/account.js:351:24)
at async exports.callViewFunction (/home/cinar/.nvm/versions/node/v14.18.0/lib/node_modules/near-cli/index.js:75:48)
at async Object.handler (/home/cinar/.nvm/versions/node/v14.18.0/lib/node_modules/near-cli/utils/exit-on-error.js:52:9)
TypedError: Querying [object Object] failed: wasm execution failed with error: FunctionCallError(MethodResolveError(MethodNotFound)).
{
"block_hash": "SZv8UsCeNXLkhjPa9KeZY6xJXmKNb6MLyKXqHVddiT5",
"block_height": 65109663,
"error": "wasm execution failed with error: FunctionCallError(MethodResolveError(MethodNotFound))",
"logs": []
}
at JsonRpcProvider.query (/home/cinar/.nvm/versions/node/v14.18.0/lib/node_modules/near-cli/node_modules/near-api-js/lib/providers/json-rpc-provider.js:116:19)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at async Account.viewFunction (/home/cinar/.nvm/versions/node/v14.18.0/lib/node_modules/near-cli/node_modules/near-api-js/lib/account.js:351:24)
at async exports.callViewFunction (/home/cinar/.nvm/versions/node/v14.18.0/lib/node_modules/near-cli/index.js:75:48)
at async Object.handler (/home/cinar/.nvm/versions/node/v14.18.0/lib/node_modules/near-cli/utils/exit-on-error.js:52:9) {
type: 'UntypedError',
context: undefined
}
The method name is get_meme_count, not getmemecount. See the source code of the museum here.
$ near view museum.testnet get_meme_count
View call: museum.testnet.get_meme_count()
67
Does some part of near academy mention it as getmemecount?
I am working on an automation prototype using Nightwatch js and when I am trying to save screenshot, it is giving below error
Error while running .getScreenshot() protocol action: An unknown
server-side error occurred while processing the command. – An unknown
server-side error occurred while proces...
TEST FAILURE: 1 error during execution; 0 tests failed, 0 passed
(10.032s)
TypeError: The "data" argument must be of type string or an instance
of Buffer, TypedArray, or DataView. Received an instance of Object
at Object.writeFile (fs.js:1487:5)
at FSReqCallback.oncomplete (fs.js:180:23)
FAILED: 1 errors and 1 passed (9.662s)
relevant data for nightwatch.config.js:
test_settings: {
"screenshots": {
"enabled": true, // if you want to keep screenshots
"path": './screenshots' // save screenshots here
},
test file data:
.pause(3000).saveScreenshot('./screnshots/test.png');
Nightwatch version: "1.5.1"
please note that due to office policy cannot paste complete testcase data here.
I have a problem within one of my camel routes. It is a route that handles soap requests and does some exchanges...
After the exchange the route just hangs and after setting logging to TRACE I found out, that camel does an endless converting, that never stops:
2015-09-24 10:24:03,227 [TRACE]
(org.apache.camel.impl.converter.DefaultTypeConverter:231) -
Converting org.apache.camel.impl.DefaultMessage -> java.lang.String
with value: Message: Message: Message: Message: Message: Message:
Message: Message: Message: Message: Message: Message: Message:
Message: Message: Message: Message: Message: Message: Message: [Body
is null] 2015-09-24 10:24:03,230 [TRACE]
(org.apache.camel.impl.converter.DefaultTypeConverter:231) -
Converting org.apache.camel.impl.DefaultMessage -> java.lang.String
with value: Message: Message: Message: Message: Message: Message:
Message: Message: Message: Message: Message: [Body is null] 2015-09-24
10:24:03,232 [TRACE]
(org.apache.camel.impl.converter.DefaultTypeConverter:231) -
Converting org.apache.camel.impl.DefaultMessage -> java.lang.String
with value: Message: Message: Message: Message: Message: Message:
Message: Message: Message: Message: [Body is null] 2015-09-24
10:24:03,234 [TRACE]
(org.apache.camel.impl.converter.DefaultTypeConverter:231) -
Converting org.apache.camel.impl.DefaultMessage -> java.lang.String
with value: Message: Message: Message: Message: Message: Message:
Message: Message: Message: [Body is null]
...
This seems to happen after an exchange, before sending the message to an remote soap endpoint.
Strangely I have some other routes, where this works without hanging in the endless loop.
I just updated to camel 2.15.3, but this still happens.
I'm using java 7 and tomcat 7.
How can I find out, where the problem is and how to fix this?
Thanks, C
I found out, why the endless converting happened: It was our proxy server, that blocked the request being send to the forreign endpoint...