-
-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: No module named 'isodate' - dependencies from requirements.txt not installed #233
Comments
worth mentioning that during skill setup I also was unable to import via GH link and had the same error as #230 |
Same here. Tried to import via GitHub too, but results on error... |
How did you upload it? I dont see that option |
when it gives you the error about failing to provision resources ignore the error and go ahead with creating the skill, then go into the code editor having created "from scratch" and select the option to upload it, will overwrite the "hello world" files Registrazione.schermo.2024-02-15.alle.23.06.00.mp4 |
Thanks, sadly this doesn't solve the error by the looks of things, the tests are still failing. |
Guys is this is unrelated to the original issue. Please move to a discussion chat created #232. |
There are 2 issues here guys. So first there is languages not being supported currently like Indian. The second one is with importing because of library that is not installing. I suspect I know whats the issue, let me confirm if its the issue indeed |
I dont know anything about AWS (first day) but I see the logs point to missing dependencies. Is AWS not supposed to import the packages on build? 2024-02-21T01:31:51.224+01:00 The third-party imports are failing |
Ok so got some news. The issue seems to be with isodate library specifically. My guess is that AWS is not compiling isodate properly in the backend. The solution will be so remove isodate and make my own iso to seconds converter. Hot fix will come soon |
Ok so fix is done. Please try the code in the branch associated with this Issue and let me know if it works or not for you guys. Hope to get some feedback before merging into master |
@DEADSEC-SECURITY tested now, good news is the isodate error is gone 👍🏻
|
the libs imports are not working, doesnt matter how you place the lambda code into the skill, |
This is because aws bosted from python 3.7 to 3.8. It must've messed with the environments for python3. |
I dont seems to have the option to downgrade or select a different python version upon skill creation, wish they put some migration guide or something but cant find anything by sheer googling, one would hope they d respect the version specified in the toml file but that doesn't seem the case... |
I'm trying to weigh my options because there are solutions but those same solutions are too complicated for non-developers and will make it way harder to use |
I was able to make it work, but I had to, in my case, Export do VSCode. It creates a local git with the code on your machine. Then, using pip, I've installed dependencies manually and push back the code with libraries. After that, I have all necessary libraries in place and I can do the Hello World testing of the skill. |
That's one workaround but not ideal. |
Also if any lib is compiled it wont work @vfranchi because compiling in windows wont work in lambda which runs linux. Thats one of the reasons Im trying to avoid that |
Maybe this could work. I created a ZIP file of my lambda folder, with everything needed to run the code. Amazon has a limit of 100 files per Import from a Zip file, so I had to do the import in parts. I replicated these steps and the Skill worked sucessfully:
@DEADSEC-SECURITY If you want I can provide you with this ZIP file, or if you prefer I'm sure you can create one yourself. I think this is a good approach for non-developers as well. It'll require just a manual import of the code. |
For now if anyone wants to replicate @vfranchi go ahead. I will keep this issue open until we come up with something more permanent. We have a guy contacting AWS, I might do the same and I'm keeping on researching it too. @vfranchi feel free to add the zip file to this issue for people hwo want to implement the current workaround |
@vfranchi and @DEADSEC-SECURITY thanks for keep in touch with the problem. |
same |
You will need to update your Invocation Skill Name and use the JSON Editor to update the Skill intents |
Testing result: When I say yes or no it now states "You just triggered hello world intent" and home assistant doesn't pick up any event |
@vfranchi it worked 🚀 |
That part works but when you try to do yes or no responses testing the functionality, it doesn't. |
Did you click the Deploy button on the Code page? |
Yes |
Maybe you've missed the JSON Editor part. Under Build, Interaction Model, JSON Editor. Paste the content of this file there. Hit Save on the top and Build. Then proceed with the testing guide. |
That was it, cheers. |
i confirm it works, thanks to all. |
Hey guys I just got confirmation that this is the way to go from now on so I will be updating the documentation very soon to reflect the new requirements. |
I figured. Might as well compile the zip files using github actions when a new release is made so you guys can just download the zip files. It should make it a bit easier for noobies |
This is now partially fixed guys. It will be under the name AlexaActionsLinux.zip. Now last step will be to update the wiki to reflect these changes. If anyone would like to test this new version please feel free to do so and give me some feedback. |
Wiki updated |
Did you check our FAQ and Issue/PR for similar issues?
Contact Details
simone.rescio@gmail.com
What happened?
Followed all prerequisite and configs steps, Dev skill is linked and visible by echo,
Upon invocation it should reply with the JSON payload stored in my homeassistant input_text helper
instead it still complains of the skills response,
cloudwatch logs contain runtime errors about imports not found
Version
0.9.1
What Alexa device are you using?
Echo
What other Alexa device are you using?
No response
Relevant log output
The text was updated successfully, but these errors were encountered: