Skip to content
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

position indicators may be wrong in tab-indented scripts #91

Open
3 tasks
abathur opened this issue Jan 7, 2023 · 0 comments
Open
3 tasks

position indicators may be wrong in tab-indented scripts #91

abathur opened this issue Jan 7, 2023 · 0 comments

Comments

@abathur
Copy link
Owner

abathur commented Jan 7, 2023

       last 10 log lines:
       > post-installation fixup
       > [resholve context] : invoking resholve with PWD=/nix/store/5r2xy79g5gfh72i19psz6a9sqrx5pski-wgnord-0.1.10
       > [resholve context] RESHOLVE_LORE=/nix/store/4mhb1m4lcnhgzh0q0d9hshap9a9p2hrw-more-binlore
       > [resholve context] RESHOLVE_EXECER='cannot:/nix/store/vs4303zaqb1grq6kgf2z7wsjzlrz71xy-iproute2-6.0.0/bin/ip cannot:/nix/store/asdp7lnwclv2s08ajm0v6srmwc1wpv09-wireguard-tools-1.0.20210914/bin/wg-quick'
       > [resholve context] RESHOLVE_INPUTS=/nix/store/h8gvq6r4hgpa71h44dmg9qfx03mj81sv-coreutils-9.1/bin:/nix/store/bcvccw6y9bfil6xrl5j7psza7hnd16ry-gnugrep-3.7/bin:/nix/store/5dv5cq1lwvsijr9p16p2kp79g1dbajk3-gnused-4.8/bin:/nix/store/vw9lf2d0cfw92dsascyv7q1l5w260r2g-jq-1.6-bin/bin
       > [resholve context] RESHOLVE_INTERPRETER=/nix/store/4xw8n979xpivdc46a9ndcvyhwgif00hz-bash-5.1-p16/bin/sh
       > [resholve context] /nix/store/n1hczz7pkhvg61xgdjwxc7am6a86nld6-resholve-0.8.4/bin/resholve --overwrite bin/wgnord
       >                    wg-quick strip wgnord | wg setconf wgnord /dev/stdin
       >                           ^~~~~~~~
       > /nix/store/5r2xy79g5gfh72i19psz6a9sqrx5pski-wgnord-0.1.10/bin/wgnord:80: Couldn't resolve command 'wg-quick'

This is technically Oil/OSH code, but I'll start here until I:

  • Confirm that there isn't a lever for controlling this already
  • Confirm that it hasn't already been fixed/reported upstream
  • If it isn't fixed in a newer version, noodle whether there's a trivial local workaround
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant