My action used to work fine, this problem started from about two months ago, the users complaiming the lock is unlocked successfully, but Google Assist reponse him with not responding.
Then I try run the test suite, the test suite failed too for a long time( about 30s) with error message: AssertionError: Expected state to include: {"isLocked":false}, actual state: {"isLocked":true,"isJammed":false,"online":true}: expected false to be true
But I've responed in the fullfillment in about 4s with right results like following:
{"payload":{"agentUserId":11424,"commands":[{"ids":["2240971"],"status":"SUCCESS","states":{"isLocked":false,"isJammed":false,"online":true}}]},"requestId":"9734864624346816785"}
I just don't know what's wrong, please help.
Related
In my Cypress tests, I create some data in before block and then my test script is run that locates in it block. I checked business side flow and it seems like there is no error about app side. I just want to understand that why my test's result is success after second attempt. Does Cypress has this kind of solution to handle an error maybe?
Cypress has the ability to automatically retry any failed tests. I would check your Cypress configuration's value for retries.openMode.
I received the above error when using the SwiftUI previews feature and can't figure out why this happens. The error always looks something like this:
GenericHumanReadableError: unexpected error occurred
messageRepliedWithError("Connecting to launched interactive agent 1894", Optional(Error Domain=com.apple.dt.xcodepreviews.service Code=17 "connectToPreviewHost: Failed to connect to 1894: (null)" UserInfo={NSLocalizedDescription=connectToPreviewHost: Failed to connect to 1894: (null)}))
I managed to figure out a good way to debug this, please see below
If you head into /Users/USERNAME/Library/Logs/DiagnosticReports you will see the latest crash reports. Open the most recent one (should start with your app name), and it should tell you the reason the app crashed. It'll look something like this:
Application Specific Information:
Fatal error: This request requires an authenticated account: file /Users/USERNAME/Work/AppName/Models/CloudKitAlbumManager.swift, line 101
In my case, it was a fatalError i threw in development for debugging. The previews loads your app and thus call your whole stack and will crash if you like me throws fatalErrors for debugging.
I hope this helps
I'm new to cypress and I want to create tests for a rather oldfashioned website which is unfortunatelly not available on the internet.
When I perform a simple call to the website cypress crashes:
cy.visit('http://10.0.0.6:8080/dmc')
The message I get within the chromium instance is: "Whoops, there is no test to run. Choose a test to run from the desktop application."
Shortly before I get this message, I see some messages in red in the left chromium task-runner-pannel (sorry for not knowing the correct term). But the timespan is too short to read it.
So my questions are, any ideas why cypress is crashing? I know this may gonna be a tough one since the website is not accessable.
Can I find these "red-messages" somewhere else? eg a logfile?
BR,
Richard
I have try to test my project in google home simulator. up to yesterday it was working but today it is showing error "There was an error completing your request"
URL: "https://console.actions.google.com/project/tell-you-profile/simulator/"
I was just having the same issue starting my simulator. The problem was: I was signed into Google Chrome, with my other (personal) email address. Once I went to cloud.google.com, signed out, and signed back in with the account that matched the needed user for the Cloud Services, the simulator loads fine.
This was my simulator issue (just to confirm):
Most times this error is caused by an error in your fulfillment server. Check your code to make sure it compiled or is interpreted correctly and then check your logs for any errors.
We're using "burst_pdf" conversions and they have been working fine until recently.
However, since two days back all jobs fail, and looking at the Blitline dashboard we see that queued jobs fail with the following error:
"Image processing failed. comparison of String with 1.2 failed"
Also, the error messages say:
"Original Photo Metadata -> null", but I'm not sure if that's related to what's causing the errors.
The original submissiosn to the queue work just fine and we get a valid response back from Blitline. However, we no longer get any postbacks, even though I was expecting one even if a job fails (to notify us that an error occured)?
Have reached out to Blitline for help but haven't heard anything back yet.
Turns out this was due to a Blitline bug which has since been fixed.