Comments (11)
Hm, actually this might only happen when using Nix: in the Git repository, scripts are already .rw-r--r--
, but in the Nix store they are .r--r--r--
(which is to be expected). I'll see if we can add a non-invasive change to the file-copying logic to reset permissions correctly.
from code-compass.
right, maybe it is just a matter of modifying the postInstall clause in your nix recipe no?
from code-compass.
Hmmm no, all files in the Nix store are read-only, this is not negotiable or modifiable in any way 😅 This is a fundamental aspect of Nix.
I can think of 2 ways:
- stop copying the scripts, and instead just run them from the
c/path-to-code-compass
location - we add a
set-file-modes
command aftercopy-file
inc/copy-file
. I think this would be transparent for non-Nix users
I think the first suggestion is the most sensible, right? Or is there a reason to copy/duplicate the scripts that I am missing?
from code-compass.
mmm, I like the copying as you can see what scripts were used for your analysis in the artefact directory. Going to add the set-file-modes
from code-compass.
hopefully this solves your issue
from code-compass.
I think you missed c/generate-host-edge-bundling-html
😅 These also trigger an error on second execution
from code-compass.
PS: I notice that from a fresh start (after I remove /tmp/code-compass-<REDACTED>
):
- if I run
c/show-coupling-graph
, everything works as expected, including opening the browser - if I run
c/show-coupling-graph-sync
(useful because with the async mode, the log messages are not displayed in*Messages*
buffer), then it correctly generates all the files in/tmp/code-compass-<REDACTED>
but it does not open the browser 🤔
Is that the expected behavior? 😅
from code-compass.
I think you missed
c/generate-host-edge-bundling-html
sweat_smile These also trigger an error on second execution
those file shouldn't be executable as the browser should deal with them. What error did you get?
from code-compass.
- if I run
c/show-coupling-graph
, everything works as expected, including opening the browser- if I run
c/show-coupling-graph-sync
(useful because with the async mode, the log messages are not displayed in*Messages*
buffer), then it correctly generates all the files in/tmp/code-compass-<REDACTED>
but it does not open the browser thinkingIs that the expected behavior
expected: the async-run is opening the server. I used the sync analyses for debugging mostly. If I have time I will redesign that
from code-compass.
those file shouldn't be executable as the browser should deal with them. What error did you get?
On second execution of c/show-coupling-graph-sync
, c/generate-host-edge-bundling-html
is executed a second time, which copies the edge-bundling
files. So similarly to the other files, if they don't have the w
permission, the second copying fails.
from code-compass.
lol sorry, working on this in the evening means that I am very slow at understanding what is going on. I just needed read write permission. Fixed both issues you raised: thanks for spotting this through Nix.
from code-compass.
Related Issues (20)
- Integrate with magit for better visibility HOT 4
- Improve filtering of reports by directory, particularly for use with monorepos HOT 2
- Typo in c/show-gource HOT 1
- Change hotspot color interpolation HOT 3
- Unclear how to use code-compass HOT 2
- Unable to use graph commands HOT 3
- Publish on MELPA HOT 3
- Some `defcustom`s are not correctly passed to async code HOT 2
- Error handling should fail earlier and louder HOT 1
- Incorrect assumption about `/tmp` vs `/data` HOT 5
- Naming convention HOT 1
- Slack Features
- Rename variable `c/slack-main-contributor`
- Run `checkdoc` on project HOT 1
- Store coupling file info on disk HOT 3
- Couple Files finds non-existing files HOT 6
- Don't show full path for coupled files results
- Extend Hashmap on cache load instead of overwritting HOT 1
- Scripts are missing in MELPA package ? HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from code-compass.