-
Notifications
You must be signed in to change notification settings - Fork 3
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
Installing on fresh installation of chronicle-app produces error #33
Comments
I am also seeing a similar issue with the shell history plugin, so it might be an issue with the "plugins installed" code in general. Is the registry somehow out of date with the adapters' current names? |
Thanks for reporting this! I moved this issue to the main chronicle-etl issue because it's a problem in the way plugins/dependencies are loaded. Someone else hit this issue a few days ago too but the error handling was swallowing up too much information to give a provide a useful error. I just released a version of chronicle-etl (v0.4.3) that does a slightly better job of handling exceptions and messaging when plugins fail to load. Can you give it a shot and let me know if you're able to get it working? Running with Also, what shows up when you run |
No prob! Looks like installing the plugin fails now too, after updating the gem.
Plugins list:
When trying to run the extractor:
|
Ahh, in fixing the previous issue, I forgot to remove a I released a fixed version. You can run: A few takeaways:
|
Thank you! Progress now. I am able to get a job running. Running into a slightly different error now - though this one may be specific to imessage? I wonder if I to let it access some permission ?
|
Great, the plugin is loading successfully and this is now just a normal, boring bug! I created a new issue: chronicle-app/chronicle-imessage#3 and should be pretty straightforward to fix. |
After installing using the commands in the README, I attempted to run:
chronicle-etl --extractor imessage --since "2022-02-07" --transformer imessage
It was them prompted with:
This is a little odd, since I just installed it. However, when going with "Y" or "n", I both run into a stack trace:
The text was updated successfully, but these errors were encountered: