https://www.dendron.so/ logo
Join Discord
Powered by
# dev
  • l
    Linux and Cygwin build agents maybe? Sounds good, I’ll fix that up today 🦾
  • k
    @cameron cool break down of the github globe animation 🌎. makes me think about animated uis for dendron and showing links between notes 🙈 https://github.blog/2020-12-21-how-we-built-the-github-globe/
  • c
    Ah yes we had a mini chat about this writeup in our team chat, it was nice that github made this public. Vasco at Cloudflare made a reusable component for this type of animated data globe: https://github.com/vasturiano/globe.gl
  • c
    For a first cut at visualizing notes node-link relations, http://js.cytoscape.org/ or vis.js could both be decent options
  • c
    I can’t read the Chinese parts of the docs that well and haven’t personally used it, but Alibaba’s graph explorer library seems quite promising and offers a lot of interactivity / layout cleaning functionality out of the box
  • c
  • l
    Calling it for today, but I have made some pretty good progress with the remaining CI issues: https://github.com/LukeCarrier/dendron/projects/1
  • l
    Windows CLI tests largely pass now after some finicky path separator voodoo, some issues with shelling out to rsync and Git left to fix. Not sure why the VS Code extension tests never complete on Windows and intermittently fail on macOS yet
  • k
    its been really cool to see the progress here. also nice use of projects! for reducing the test timeout, we can check for a flag to indicate CI and switch the timeout to something reasonable
  • l
    Yup, that was the plan. I believe mom already alters it’s behaviour when the CI env var, so I was going to match its behaviour
  • k
    mom?
  • k
    saw this on hacker news and thought for a moment that gatsby.js was entering the public domain 😅 https://www.openculture.com/2021/01/whats-entering-the-public-domain-in-2021.html
  • k
    i guess it is open source so it already is
  • s
    Ah yes, the great gatsby.js
  • l
    npm... 😅
  • k
    lol, got it
  • l
    The publishing issue with Windows is a little messy. I'm seeing the weird 8.3-style directory name in place of my user's profile directory and I don't think the Cygwin build of rsync understands the weird hybrid path the rsync module generates 😬
  • l
    I'm definitely in favour of standardising on 💩 as the path separator
  • l
    Weirdly if I manually prefix the paths with 
    /cygdrive/c
    they work...?
  • k
    hmm, if you can give me a repro case then i can look into making it better
  • l
    I'll include a workaround on the 
    github-actions
    branch, I think I have it down now
  • l
    If it looks sane we can always upstream it
  • k
    👍
  • l
    I'm not really sure how the rsync module's code could ever have worked with a cygwin rsync though
  • l
    I tried a bunch of variations on the paths it was generating and none of them worked without the leading /cygdrive
  • k
    hmm, it might not have worked with cygwin then? i think most people were using WSL on windows
  • l
    I don't think there is value in testing under WSL2 since that's basically just a VM with some filesystem magic to allow bidirectional file access, but maybe WSL1. Some telemetry on usage numbers would be really useful here
  • k
    yeah, i’m currently relying on user reports. planning on adding some optional telemetry to collect os and error reports in late january
  • f
    depending on where I am I only have WSL 1 as an option
  • b
    It's been a long time since I last used cygwin but I seem to recall that this cygdrive was always needed? These days I mostly use WSL1 due to weird DNS issues with WSL2 and Mingw/Msys in case that helps
1...424344...108Latest