After every successful step on https://developers.google.com/assistant/sdk/guides/service/python/
I now am hard stuck.
I can not get the line: "googlesamples-assistant-hotword --project-id "project id" --device-model-id "model id" " to work.
nor can i get the line "google-assistant-demo --project-id "project id" --device-model-id "model id" " to work.
I keep getting the error code: "Segmentation fault" (nothing else)
Note that i do get every other test to work, like the audio test and the "googlesamples-assistant-pushtotalk" flawlessly.
I have been looking for answers but most of the answers are outdated and have been solved by updating to the latest google-library (1.0.1).
Since i already have that installed (also checked pip list to be sure) must mean that i realy am stuck.
Is anyone able to help.
That would mean the world to me, thanks.
Problem has been solved, for all people who get this 'segmentation fault', the solution is simple, download the previous version of rasbian ( Raspbian Stretch )
Google assistant is not compatible with Raspbian Buster.
Leave a like if this solved your problem
Related
This happens in the package manager console. What does the red text mean?
After I run the command, the migration file is generated, but it's empty.
I can't find an answer anywhere else. I'm very frustrated. I've done a research in google but that error happens in many situations different than this one.
The solution to this problem was to "downgrade" Entity Framework to 6.1.3. I guess the cause was a bug with the beta version. I was using: 6.2.0 beta.
Thank you guys for pointing this out! Thank you Gert Arnold. You rock!
I'm trying to figure out how a server can work on an iOS device. And I found this fantastic tool.
I'm trying to follow this example. Following these instructions, everything seems to work, but when I open EndToEnd.Xcworkspace, Change scheme to "ClientSide" and build, I get the following error: <unknown>:0: error: missing required module 'CHTTPParser', also report here .
I also saw that a similar error was reported here as well, and seems to have been fixed here, at least in xcode 8.3.1 and 8.3.2 (I use 8.3.3).
In a comment it is written: "remove ServerSide and rerun make", I have tried but the error persists.
Any suggestions ? Which may be the cause of
Missing required module 'CHTTPParser'
#emacos Let me debug it during the weekend.
July, 23, 2017 Fixed in this PR - https://github.com/IBM-Swift/Kitura-Builder-iOS/pull/1
I've got a very curious error to share regarding Xcode localization process. I will try to share as much detail as legally possible.
From Xcode, I am trying to export an XLIFF file to send to our translators, via "Editor > Export for Localizations". However, this immediately throws error with the message:
The operation couldn't be completed. Argument list too long
This is indeed confusing, as I cannot find a more verbose log anywhere (I have already tried checking my Console.app). So, I spent quite a few time googling – to no avail. I couldn't find similar case like this. The error itself happens only when I am trying to export for localization. I can build and run the app just fine.
Facts
~ $ xcodebuild -version
Xcode 8.2
Build version 8C38
~ $ xcode-select -version
xcode-select version 2347.
~ $ echo $PATH
/Users/david.christiandy/.rbenv/shims:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/david.christiandy/arctools/arcanist/bin:/usr/local/go/bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands
I am using Xcode 8.2 on macOS Sierra 10.12.5.
The error happens only when I try exporting from localization. This is also true when I run the localization process via xcodebuild -exportLocalizations.
I can build and run the app just fine. (I believe) there's no problem with my header search paths.
Attempts
Thought there was something wrong in the code, so I tried to run the export process (via xcodebuild command) in a CI. Somehow, it's working. For the record, I am using Bitrise CI with the same stack as my system (Xcode 8.2.x, macOS 10.12)
Asked colleagues to run export process on their machines, and they have the same error.
This leads me to think that there must be something wrong with the configuration. So I made a standalone project to confirm that the export process fails consistently. Turns out, it works just fine!
So, the hypothesis I got currently is:
There's probably something wrong in the code, and
There might be tools/software (that most of our iOS engineers installed) that might contribute to the error (since the CI completes just fine).
I don't know why the CI can run the export process just fine, and I don't know when it might suddenly stop functioning (just like our local machines).
Appreciate any help on this matter. Thank you!
I also asked this question on Apple developer forums, here is the link: https://forums.developer.apple.com/thread/86762
“Argument list too long” sounds like E2BIG, which you get when you try to run a child process with a huge argument list (I believe the current limit is 256 KiB). I suspect that Export for Localizations is running some sort of command line tool to do that work (probably the extractLocStrings tool, which you’ll find lurking within Xcode’s app bundle) and passing it full paths to each of the files in your project. Depending on how many files you have and how long those paths are, it’s easy to run into problems like this.
One of the ‘fun’ things about bugs like this is that they are dependent on where you place your project. Things might work if the project is at the top of your home directory but fail if it’s nested deep inside a subdirectory.
That also suggests a potential workaround, namely, to move your project further up in the directory hierarchy.
Finally, you should definitely file a bug about this. I believe we’ve seen this before (r. 30703294) but your report will help reinforce that this is causing problems for developers in the field. Please post your bug number, just for the record.
Several days ago before I read this answer, I managed to get the export working by deleting some folders via Xcode (remove references only). Initially I suspected that there's an invalid format within the folders that I deleted, but when I tried deleting other folders, the export process works just fine.
I also tried exporting strings using Xcode 9, and I didn't encounter the problem. So hopefully this bug is only for Xcode 8.3.3 and below.
I've got a real head scratcher here. I just upgraded to Xcode 7.3.1 and all my Bots have hit the floor during the integration process. For some reason or another the Bots get stuck on step 7 of 9 "Processing results". I let it sit for about 24 hours to see if it would work itself out but had no luck.
Anyone ran into this problem and have any idea what a fix might be? Short of reinstalling Xcode and Server on the build server, I'm not sure what else to try as I've tried a lot of random fixes that I've seen out on the interwebs.
Thanks in advance for any help?
UPDATE - The last thing to run in the raw build log is:
Test Suite 'All tests' failed at 2016-05-19 13:32:16.765.
Executed 131 tests, with 1 failure (0 unexpected) in 4.500 (4.592) seconds
Update: Fixed
Here's what I did:
Stopped the server.
deleted all bots from Xcode.
Went into /Library/Developer/XcodeServer and removed (you will need Admin access):
Logs
Integrations
Removed my derivedData directory
Restarted everything and rebuilt the bots using different names for them.
I had the same problem once. I think it happened after updating Xcode. Only solution was to reinstall OS X. After that I have not had any problems. I tried everything I could find from the web but there weren't any solutions out. I tried to delete everything that belongs to Xcode but I think I didn't find all of them. So my suggestion is to reinstall OS X. Copy all your important stuff to external hard drive or to cloud.
I know this is not the suggestion or answer you are looking for but it helps you out.
Has anyone else noticed that Xcode 6.3 (6D570) is showing the "Test Succeeded" popup (and displaying the test success sound, if configured) for a failing test when you run the test by itself?
When you run all tests in the file, everything works as expected.
For example, the following assertion fails, but Xcode shows "Test Succeeded".
XCTAssertTrue([queryStringLat isEqualToNumber:expectedLat], #"Expected: %# but got: %#\n", expectedLat, queryStringLat);
The debugger output shows that it failed, Xcode just seems to be getting confused.
Here is the debugger output:
Foo_Tests.m: test failure: -[Foo_Tests test_sendRequestForApp_with_coordinates_validate_that_coordinates_exist] failed: (([queryStringLat isEqualToNumber:expectedLat]) is true) failed - Expected: 37.33233 but got: 0
Has anyone else experienced the same type of thing?
This isn't a huge "bug", but is really annoying when working on tests.
Thanks!
SOLVED!
I received a response from Apple. They said that they could not reproduce the problem, and asked me to remove all plugins and provide them with a complete sample of code that reproduced the issue.
Hmm, PLUGINS, brilliant!
I started to remove plugins, a few at a time, and after a few attempts, the "bug" went away!
I then tracked it down to the MCLog plugin, which I had installed using the Alcatraz package manager in Xcode.
I've also filed an issue with the MCLog author.
If I find out, or figure out, exactly what was causing this issue, I'll post that information here. I find it interesting that MCLog was able to confuse Xcode so it reported "Test Succeeded" upon failures.