jabber.developer
  • Joined on 2025-06-19
jabber.developer commented on pull request devs/cproof#105 2026-04-23 15:04:46 +00:00
merge/upstream-full

We also clean it on line 138. Potential for double free. We need to set it to NULL in resource.c for safety. At least the resource itself.

jabber.developer commented on pull request devs/cproof#105 2026-04-23 15:04:46 +00:00
merge/upstream-full

We might want to point to our fork

jabber.developer commented on pull request devs/cproof#105 2026-04-23 15:04:46 +00:00
merge/upstream-full

Most of the messages will have this value as NULL. Luckily, SQLite treats them as unique values.

jabber.developer suggested changes for devs/cproof#105 2026-04-23 15:04:46 +00:00
merge/upstream-full

Nice job. I generally tried to make less comments to avoid unnecessary increase in the workload, but there are many places which are incompatible with our code style/approach.

jabber.developer commented on pull request devs/cproof#105 2026-04-23 15:04:46 +00:00
merge/upstream-full

We have a different website. Please remove this instruction

jabber.developer commented on pull request devs/cproof#105 2026-04-23 15:04:46 +00:00
merge/upstream-full

Why though?

jabber.developer commented on pull request devs/cproof#105 2026-04-23 15:04:46 +00:00
merge/upstream-full

Without (int) typecasting, _tabs_width always returns result > 0. And it's so hard to maintain such part since we need to keep in mind that result is unsigned. It's a hack rather than a normal implementation. I suggest we revert these changes: they decrease maintainability, and reduce compiler's ability to detect issues.

jabber.developer commented on pull request devs/cproof#105 2026-04-23 15:04:46 +00:00
merge/upstream-full

All these guint might lead to unexpected bugs.

jabber.developer commented on pull request devs/cproof#105 2026-04-23 15:04:46 +00:00
merge/upstream-full

we should set it to NULL for safety

jabber.developer opened issue devs/cproof#109 2026-04-22 12:53:44 +00:00
Reenable build flags
jabber.developer merged pull request devs/cproof#108 2026-04-21 14:00:23 +00:00
CI: Simulate Pikaur flag duplication in Arch Linux builds (fix #55)
jabber.developer pushed to master at devs/cproof 2026-04-21 14:00:18 +00:00
0feacbc9da ci: simulate Pikaur flag duplication in Arch Linux CI
jabber.developer pushed to feat/pikaur-parity-arch at devs/cproof 2026-04-21 13:44:58 +00:00
jabber.developer commented on pull request devs/cproof#108 2026-04-21 13:43:25 +00:00
CI: Simulate Pikaur flag duplication in Arch Linux builds (fix #55)

Notes: After review by @jabber.developer2, it was decided to use source /etc/makepkg.conf method instead. It was also tested via the same method. Results:

  1. [without](https://git.jabber.space/…
jabber.developer pushed to feat/pikaur-parity-arch at devs/cproof 2026-04-21 10:18:38 +00:00
04dafdf36f Revert "build(pikaur): Fix failure due to duplicated flag and warnings"
0feacbc9da ci: simulate Pikaur flag duplication in Arch Linux CI
Compare 2 commits »
jabber.developer pushed to feat/pikaur-parity-arch at devs/cproof 2026-04-20 05:59:39 +00:00
4a59ccaa80 Revert "build(pikaur): Fix failure due to duplicated flag and warnings"
jabber.developer pushed to feat/pikaur-parity-arch at devs/cproof 2026-04-19 13:14:16 +00:00
7ef45977c8 ci: simulate Pikaur flag duplication in Arch Linux CI
jabber.developer pushed to feat/pikaur-parity-arch at devs/cproof 2026-04-18 16:46:57 +00:00
jabber.developer commented on pull request devs/cproof#108 2026-04-18 16:46:11 +00:00
CI: Simulate Pikaur flag duplication in Arch Linux builds (fix #55)

As expected, build failed on Arch (only on Arch, confirming that Ubuntu and Debian are not affected). Code Coverage job has also failed due to the fact that it's also run on Arch. Collision and…

jabber.developer commented on pull request devs/cproof#108 2026-04-18 16:38:11 +00:00
CI: Simulate Pikaur flag duplication in Arch Linux builds (fix #55)

Last build should fail, indicating parity with Pikaur builds