jabber.developer
0 Followers · 0 Following
  • Joined on 2025-06-19
Repositories Projects Packages Public Activity Starred Repositories
2
jabber.developer pushed to feat/pikaur-parity-arch at devs/cproof 2026-04-18 16:36:55 +00:00
4611bd339d Revert "build(pikaur): Fix failure due to duplicated flag and warnings"
jabber.developer created pull request devs/cproof#108 2026-04-18 16:13:54 +00:00
ci: simulate Pikaur flag duplication in Arch Linux CI
jabber.developer created branch feat/pikaur-parity-arch in devs/cproof 2026-04-18 16:09:10 +00:00
jabber.developer pushed to feat/pikaur-parity-arch at devs/cproof 2026-04-18 16:09:10 +00:00
8c6c9f4f42 ci: simulate Pikaur flag duplication in Arch Linux CI
jabber.developer merged pull request devs/cproof#106 2026-04-13 20:02:36 +00:00
Quickfix for pikaur build failures (not sustainable)
jabber.developer pushed to master at devs/cproof 2026-04-13 20:02:33 +00:00
0722dc9e36 build(pikaur): Fix failure due to duplicated flag and warnings
jabber.developer created pull request devs/cproof#106 2026-04-13 19:53:22 +00:00
Quickfix for pikaur build failures (not sustainable)
jabber.developer pushed to fix-pikaur-build at devs/cproof 2026-04-13 19:52:38 +00:00
0722dc9e36 build(pikaur): Fix failure due to duplicated flag and warnings
jabber.developer pushed to fix-pikaur-build at devs/cproof 2026-04-13 19:25:27 +00:00
35ce847e48 build(pikaur): fix failure due to duplicated flag and warnings
jabber.developer pushed to fix-pikaur-build at devs/cproof 2026-04-13 18:57:48 +00:00
46f5d28de3 Fix build on pikaur due to warnings
jabber.developer created branch fix-pikaur-build in devs/cproof 2026-04-13 18:25:48 +00:00
jabber.developer pushed to fix-pikaur-build at devs/cproof 2026-04-13 18:25:48 +00:00
655789e636 Fix build on pikaur due to duplicated flag
jabber.developer commented on pull request devs/cproof#94 2026-03-31 15:46:46 +00:00
no-DB mode implementation

I don't understand the need for gstring and step1. I propose a simpler solution that might be more efficient, but I might've missed some intricacies:

jabber.developer suggested changes for devs/cproof#94 2026-03-31 15:46:46 +00:00
no-DB mode implementation
jabber.developer commented on pull request devs/cproof#94 2026-03-25 13:39:46 +00:00
no-DB mode implementation

the logic seemingly mirrors the one from _ff_state_build, creating repetition. I suggest extracting it to a different method to keep things DRYer and more maintainable

jabber.developer commented on pull request devs/cproof#94 2026-03-25 13:39:46 +00:00
no-DB mode implementation

nit: I suggest this version for readability (avoid magic number of 3 and 4).

jabber.developer commented on pull request devs/cproof#94 2026-03-25 13:39:46 +00:00
no-DB mode implementation

Instead of loop, we can do something like that:

jabber.developer commented on pull request devs/cproof#94 2026-03-25 13:39:46 +00:00
no-DB mode implementation

Shouldn't it be a warning, since it's not an expected state?

jabber.developer commented on pull request devs/cproof#94 2026-03-25 13:39:46 +00:00
no-DB mode implementation

Typically, prefs are not autosaved and need manual saving via /save command. This place creates an exception, which needs to be discussed (e.g., later we might add /autosave command).

jabber.developer commented on pull request devs/cproof#94 2026-03-25 13:39:46 +00:00
no-DB mode implementation

here and in other places: if the method does not exists, then it just passes. I think that we need to log this invalid state.