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

Dev 2023 #39

Merged
merged 91 commits into from
Oct 2, 2023
Merged

Dev 2023 #39

merged 91 commits into from
Oct 2, 2023

Conversation

fstamour
Copy link
Owner

No description provided.

Before, you had to provide a node, to find its sibling. But it makes
more sense to use a position in the string. Still support passing a
node, it'll be converted to a position using `node-start`.
This breaks a few tests, but instead of trying to fix the code with a
bad architecture, I'll fix the architecture
- it's much much more robust now
- the chance of commands interfering went down drastically
- can run multiple commands concurrently (technically)
@fstamour
Copy link
Owner Author

fstamour commented Apr 18, 2023

I just fixed the ci, making it fail if any tests fails.

finally

@fstamour
Copy link
Owner Author

On MacOs, log4cl fails to load with a weird error about package-lock violation.

It sounds like log4cl is using sb-c::lambda-parent or sb-c:lambda-parent (not sure if it's supposed to be exported from sb-c, but for some reason the symbol doesn't exists. Just reading the file makes it intern the symbol lambda-parent, but the package sb-c is locked..

; Loading "log4cl"
[package log4cl.package-setup]....................
; 
; caught ERROR:
;   READ error during COMPILE-FILE:
;   
;     Lock on package SB-C violated when interning LAMBDA-PARENT while in package
;     LOG4CL-IMPL.
;   See also:
;     The SBCL Manual, Node "Package Locks"
;   
;     (in form starting at line: 99, column: 0, position: 3779)
Unhandled UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread #<SB-THREAD:THREAD "main thread" RUNNING
                                                          {10010A0003}>:
  COMPILE-FILE-ERROR while
  compiling #<CL-SOURCE-FILE "log4cl" "src" "naming-sbcl">

I noticed that under sbcl, on linux, *debug-io* prints out directly to
the tty, making it impossible to pipe that output somewhere.
@fstamour fstamour merged commit 06b5947 into master Oct 2, 2023
3 checks passed
@fstamour fstamour deleted the dev branch October 2, 2023 02:11
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

Successfully merging this pull request may close these issues.

1 participant