question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Failure to start due to assets/v0.8.0.json not found (fix known)

See original GitHub issue

Having applied (local) fixes for #72 and #73, sudo supervisord start scheduler-v8 fails with (full trace):

/home/eac/opt/eac-client-8.0.0b1/env/lib/python3.5/site-packages/dotenv/main.py:24:
    UserWarning: Not loading .env - it doesn't exist.
...
  File "/home/eac/opt/eac-client-8.0.0b1/env/lib/python3.5/site-packages/alarm_client/config.py", line 195, in compiled_assets
    with open(self.compiled_assets_path) as assets_file:
FileNotFoundError: [Errno 2] No such file or directory:
    '/home/eac/opt/eac-client-8.0.0b1/env/lib/python3.5/site-packages/alarm_client/assets/v0.8.0.json'

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:6 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
veoxcommented, Apr 18, 2017

MANIFEST.in has

include alarm_client/assets/v8.0.0.json

but the file is called alarm_client/assets/v0.8.0.json in the tree.


The file describes the ABI of EAC contracts, so it should probably have v0.8.0 in the name (version of EAC), not v8.0.0 (version of the client, as seen on PyPI).

Release versioning seems a bit confusing to me, and it’s possible that the v8.0.0b1 tag was a typo in itself, and should have been v0.8.0b1.


To launch with currently deployed version of EAC (0.7.0), a different JSON should probably be written up, decribing that version’s ABI. However, it seems that specifyng the ABI in a separate JSON has only been introduced between v0.7 and v0.8, and there might be are other incompatible changes improvements (described in a blog post).

I’ve gotten acquainted enough with v0.8 to like it, so won’t be doing this back-porting analysis. Fixing the string in MANIFEST.in should therefore be enough.

0reactions
pipermerriamcommented, Dec 18, 2017

The current code in this repo isn’t supported or expected to work. Revamp of the service is underway. Stay tuned. No set timeline.

Read more comments on GitHub >

github_iconTop Results From Across the Web

manifest.json does not include assets · Issue #2375 · vitejs/vite
Statically imported assets (SVG file in my case) will get bundled and created in the outDir , but are missing in the generated...
Read more >
java json schema validation relative path not working (URI not ...
The problem is that you load the JSON then turn it into a schema. And your schema does not have an absolute URI...
Read more >
SimpleSAMLphp changelog
This document lists the changes between versions of SimpleSAMLphp. See the upgrade notes for specific information about upgrading. Version 1.18.9. Released 2021 ...
Read more >
config.json file not found : r/learnjava - Reddit
I am trying to connect my AstraDatabase (Cassandra) with my spring boot application. I had done all the configuration needed when I used...
Read more >
Can't use json file from StreamingAssets on Android and iOS
I researched a lot on the internet and tried to fix it by myself, ... Hi this is not working for me as...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found