Community
Chat Logs
Sunday, October 11, 2026 (America/New_York)
- phalethI was trying to read #392, but it's just like walls of text
- phalethI think only the description of the current state is useful, the rest should just be abandoned, it's not helpful at all
- blueok, I'll make it better phaleth
- phalethwait, it's just like waste of tokens
- phalethit doesn't give any important detail, except for the git to ssh part, but that part of the description is difficult to read
- blueno I mean, I'll separate what we currently have, from the desireable state, and break it up into tasks
- bluebreaking up something big into small digestable parts is a central part of making things work :)
- bluewe'll create an `architecture` directory, with different documents
- blueinstead of a huge file
- phalethyeah, but the new ideas there are not great :D
- bluesome of them we need to retain somewhere. like using *.in.repopack.app etc.
- phaleththat one we will need for sure, but why not just implement that already for each user?
- phalethbtw you should change porkbun credentials since clanker was in the haproxy dir it knows them
- blueyou mean the API ones?
- blueI can change the API key, but where do I need to update it?
- bluehttps://repopack.com/project/repopack/tasks/560
- bluethis is on your suggestion phaleth
- phalethit's stored in vaultwarden as two values
- phalethI do not have those keys anywhere else
- bluenow I mean, if I revoke the old API key, and cfeate a new one, where do I need to record it on the server
- bluejust haproxy config?
- blues/now/no/
- phalethjust in vaultwarden, haproxy configs do not matter at the moment, I will be moving haproxy to a container
- bluek
- phalethI like https://repopack.com/project/repopack/tasks/560
- blueyes, will be done done
- bluesoon done*
- bluephaleth: #570 is active
- phalethyeah, clanker has no idea what to do prolly
- blueI think it's almost ready
- blueas you can see the problem was that the full job json object, with id, wasn't accepted
- blueI'm now moving to a flag-based design which is anyway easier to work with
- blueI also discovered that the route code it produced was terrible
- blueso told it to make it more the way it should be in primate
- bluewith proper pema validation
- phalethit looked terrible when I looked at it yesterday
- phalethit's prolly not using rcompat as well in majority of the places
- blueyes
- phalethit does not tell what should I run instead of that command above, it's just mudding the waters
- blueit's not done yet
- bluebtw pha
- bluephaleth
- bluehttps://repopack.com/project/repopack/code/blob/web/routes/api/v0/jobs/%5Bjob%5D/index.ts?ref=task%2F570-unable-to-make-job-artifacts-public-for-a-projec
- blueif you look at lines 39-41
- bluethat's a pema gap
- bluehttps://repopack.com/project/primate/tasks/192
- blueso sometimes the ugly isn't the clanker: it's upstream primate lacking smth
- bluethose unknown keys, or at least one key must be present, those are missing pema capabilities that will be added in 0.43
- phalethtime to go back to the roots
- blueya
- blueplanning primate 0.43 for today
- phalethgreat
- bluethis release already kinda has too much
- bluephaleth: https://repopack.com/project/repopack/tasks/569
- bluethis is just for public repos, yes?
- bluewe don't have yet proper support for public repos, until I can figure out excluding .js from it
- phalethit mentions that there should be some sort of access token for private repos provided via query string param
- bluehm, ok
- phalethyeah, it means scope for the token and so on, it's a rabbit hole
- bluek, yeah
- bluephaleth: could you do me a favour
- bluerun `rp update`
- bluethen in flog project, update the job;s artifacts to public?
- blue`rp job update` will help you
- blueusage: rp job update <job-number> [--source <ref|trigger:branch-ref>] [--artifact-access project|public] [--description <text>]
- blue`rp job update 1 --artifact-access public`
- bluecan you try it?
- phalethyeah, it updated the access to public
- bluegreat
- blueand now you can download artifacts?
- phalethyeah, the download urls are public
- bluegood
- bluephaleth: soon rebuilding flog with your fix
- bluejust making it build automatically from master, and I need a small fix in repopack for that
- bluephaleth: flog job now automatically rebuild on master merges
- phalethok
- bluedid it fix your issue that you reported?
- phalethI'm gonna try
- bluewould be nice to completely move to flog, as part of 0.43
- blueand get rid of all nub/pnpm nonsense in the monorepo
- phalethneither curl or wget can download the new artifact file
- phalethI guess it's a problem of quotes
- phalethnope, just can't download that
- phalethcurl -v -L -C - -o flog.tar.gz 'https://repopack.com/project/flog/jobs/1/runs/4/artifacts/flog-0.0.0-dev.98af3a547abd-linux-amd64.tar.gz'
- phalethseems to be blocked again
- bluelet me see
- phalethwill have to put it to superarch.org again :D
- bluephaleth: curl -fL -o flog.tar.gz 'https://repopack.com/api/v0/jobs/1/runs/4/artifacts/flog-0.0.0-dev.98af3a547abd-linux-amd64.tar.gz?project=flog'
- bluethis should work. but I will improve the ergonomics of it so you don't need to go via the api
- bluephaleth: https://repopack.com/project/repopack/tasks/591
- phalethyeah, that works, no need to worry about ergonomics
- phaleth[1/2] STEP 9/12: RUN flog install --ignore-scripts --no-lockfile
- phalethflog: error: install importer . dependency apekit: validate typescript@6.0.3 package manifest: /app/primate/.flog-install-1628046316/node_modules/apekit/node_modules/typescript/package.json: field "devDependencies.@types/node" has invalid value "latest": invalid registry range: invalid comparator "latest": expected decimal digits
- phalethError: building at STEP "RUN flog install --ignore-scripts --no-lockfile": while running runtime: exit status 1
- phalethI can report that
- blueyes report, I'll have it fixed
- phalethflog#22
- bluethx
- bluephaleth: flog 22 is in, https://repopack.com/project/flog/jobs/1?run=8
- blueoof, the job failed
- phalethhmm
- phaleththat one should be easy for clanker to fix
- blueyes
- phalethhow to push a commit to remote branch without triggering a review?
- bluehttps://repopack.com/project/flog/jobs/1?run=9
- bluephaleth: commits never trigger a review automatically, that's an rp/API actoin
- phalethgit push does not work
- bluewhat do you get
- bluebtw the build succeeded phaleth
- phalethhttps://paste.debian.net/plainh/099c19fc
- phalethanother error
- phalethflog#24
- bluephaleth: https://dpaste.com/9FH9BL47J
- blue24 is in flight
- phalethI will not be able to access dpaste
- phalethactually I can access that
- phalethok, that helped, got few of those files to remote without changing state of the task
- blueok. if you need rp helpers for that, tell me. trying to kill git
- bluehttps://repopack.com/project/flog/jobs/1?run=10
- bluephaleth: ^
- phalethclanker just barfled more go files
- blueyes
- blueactually, #24's commit didn't add any new files
- phalethinstalled 561 packages and 0 workspace links (431 cache hits, 130 downloads)
- phalethfails on build step
- bluetask?
- phalethsure, will create
- phalethbut 431 cache hits sounds cool
- blueya, aiming for the stars here
- phalethflog#25
- blueon it
- phalethmore go code
- blueyes
- phalethit learns to parse pnpm-workspace.yaml, that's nice
- phalethmaybe it'll be a drop in replacement for pnpm
- blueI intend to remove that, pnpm-workspace.yaml is an abomination
- blueit's better to support workspaces inside package.json
- blueit's so nice now that rp can reparent tasks
- phalethheh, ok
- bluebecause sometimes you have code dependencies you don't know about from the get-go
- bluelook at this
- bluehttps://repopack.com/project/repopack/tasks/564
- blue564 started with 593, 594 and 595 all being its direct children
- bluebut they kind of build on each other, so rp needed to reparent 594 on 593, and 595 on 594
- bluethis reduces the amount of times you need to solve conflicts
- blue#25 is merged, job rebuilding
- phalethyeah, but I'm building pnpm monorepo with flog
- bluethe primate repo?
- phalethand if it can support that then that means it's usable
- phalethyeah, I'm building old primate repo
- phalethfrom github
- blueok, fair enough. I get we can leave pnpm support in
- blueI guess*
- phalethyeah, absolutely
- bluepnpm-workspace.yaml* support
- bluebut I'm not gonna support foreign lock files like bun.lock
- blueflog.lock will be the standard
- phalethclanker just gotta figure out how to fix all the security problems so repos can be made public
- blueya
- phalethwhy make another lock file?
- bluefor identity, mostly
- phalethand probably json
- blueya it's json
- phalethyou can take a look at nub.lock
- phalethlarge json is difficult to process
- bluewhat does nub.lock do?
- phalethnot sure, but not json
- phalethhttps://repopack.com/project/primate/code/blob/nub.lock
- bluethat's ugly
- phalethlol, all of them are ugly
- phaleththe thing is to not make yet another standard
- phalethdeno.lock, nub.lock, bun.lock, ...
- phalethcan you tell how to execute primate with flog?
- phaleth[1/2] STEP 12/12: RUN flog primate build --target=node
- phalethflog: error: unknown command "primate"
- phalethit got very far
- blueit should be `flog run`, no?
- blueor better, `flog x`
- phalethok, help isn't saying anything about x
- phalethflog: error: unknown command "x"
- blueyes, flog x doesn't exist yet :)
- phalethheh
- bluebecause flog isn't a runtime
- bluethough it should work anyway
- bluethere's npx, pnpx
- phalethok, then I ll use npx
- bluecan you create a task for `flog x`?
- bluewe wnat to be able to use primate without npm / pnpm / bun
- phalethnpx cannot find packages
- phalethok, sure
- bluehttps://repopack.com/project/flog/tasks/13
- bluehype
- phalethhttps://repopack.com/project/flog/tasks/27
- bluethx
- bluephaleth: https://flog.repopack.app/
- nevetflog — predictable JavaScript package management
- bluemaybe you can point flog.run at that
- bluephaleth: https://repopack.com/project/flog/code/blob/flog.lock?ref=task%2F13-launch-the-self-hosted-flog-run-primate-website
- phalethcool
- bluephaleth: flog x is being done
- phalethhttps://flog.run/
- nevetflog — predictable JavaScript package management
- blueNICE!