I've got a couple of returners configured using the schedule state.
One works fine, the other logs an error:
Job state.sls using invalid returner: <name of returner>. Ignoring
I have found no documentation on what this means; reading the salt code doesn't enlighten me.
Can someone point me in the right direction about what this means?
This appears to have been caused by a syntax error in the returner. I just wish the salt error messages were a bit more useful.
Related
I am trying to connect to gmail and in the search option trying to search an email. I am getting the following error when executing in Dex but when i execute it in my local it works fine. Please help me understanding this issue. I have used the waiton option and usersimulation option but none of them has been helpful. TIA.
Error: The browser was not ready after 60000 ms. Please refer to the setting (TBox.Synchronization.SynchronizationTimeout) or the testconfiguration parameter (SynchronizationTimeout)
I'm swapping tokens using web3.js sometimes it succeeds and sometimes it fails, but when it fails I get this error in my console:
VM Exception while processing transaction: revert callBytes failed: Unknown(0x)
and I believe it is the same as the error below from etherscan:
enter image description here
can someone please tell me what is this error and how to solve it?
thank you for your time.
The error message itself.
The code causing the error.
(Due to issues with shared clipboards, I can't copy/paste code from the VM I'm working in to the host machine.)
This seems to have something to do with the fact that I am supplying an anchor.BN as an argument, which I've managed to do elsewhere successfully, albeit not in the browser. On the Anchor discord, I heard that toArrayLike, one of the functions in the error's stack trace, does not exist in the browser, but I expect this was out of date. Any idea what might be going wrong here?
When I start my jobs using fast export they sometimes end with an error:
TDWALLETERROR(543): Teradata Wallet error. The helper process is already being traced
When I restart them, they work.
I'm using saved-key protection scheme.
Can someone explain to me why is that error occuring and how to fix it?
Looks like you have a trace activated in one of the scripts, run in the system.
Teradata has a shiffer code that attempts to validate if tracing is running during the wallet invocation - which triggers this error.
I am facing this error since some time, it is very intermittent in nature so, unable to understand why this error and what needs t be done t fix this.
Issue:
We have a workflow 4.5 WCF service. Everything goes well, but intermittently we see suddenly that a workflow instance gets suspended with an error in the table "DurableInstancing.InstancesTable"
The error is "Keyword Not supported: 'DB Name,1433';Initial Catalog'.
Since most times this ust workd fine without any error, I do not think this problem is related to web.config entry for connectionstring. Most times the workflow completes without any error. We have verified multiple times that the connection string is proper and there is no issue with parsing the connection string.
I suspect this issue is happening while Workflow instance is being recreated from persistence storage, and because some reason it is unable to recreate , the workflow is getting suspended with this error in DB.
I really appreciate any help in getting us through this error.
Thanks,
GD
What we found was it was an issue with permission in Database. We gave "dbo" user permission to the workflow database, and after that we have not seen this problem occur again. Has the error or exception that gets logged in the table is mre informative then it would have been better.
Thanks,
GD