search for: fightwarn

I'm starting down the path of testing. There are commits in the rc tag that are not on master: $ git log --oneline ..v2.8.3-rc1 3d286fb1b (tag: v2.8.3-rc1, jimklimov/pre-283-2) appveyor.yml: handle also FTY and fightwarn branches 4e92275c1 .github/workflows/codeql.yml: handle also FTY and fightwarn branches 504706d45 Makefile.am: nut-scanner does directly depend on clients after all 051b49d9f Revert "Revert "NEWS.adoc, UPGRADING.adoc, docs/docinfo.xml.in: finalize text before NUT v2.8.3 release&quot...

I'm starting down the path of testing. There are commits in the rc tag that are not on master: $ git log --oneline ..v2.8.3-rc1 3d286fb1b (tag: v2.8.3-rc1, jimklimov/pre-283-2) appveyor.yml: handle also FTY and fightwarn branches 4e92275c1 .github/workflows/codeql.yml: handle also FTY and fightwarn branches 504706d45 Makefile.am: nut-scanner does directly depend on clients after all 051b49d9f Revert "Revert "NEWS.adoc, UPGRADING.adoc, docs/docinfo.xml.in: finalize text before NUT v2.8.3 release&quot...

...v at alioth-lists.debian.net> wrote: > I'm starting down the path of testing. > > > There are commits in the rc tag that are not on master: > > $ git log --oneline ..v2.8.3-rc1 > 3d286fb1b (tag: v2.8.3-rc1, jimklimov/pre-283-2) appveyor.yml: handle > also FTY and fightwarn branches > 4e92275c1 .github/workflows/codeql.yml: handle also FTY and fightwarn > branches > 504706d45 Makefile.am: nut-scanner does directly depend on clients after > all > 051b49d9f Revert "Revert "NEWS.adoc, UPGRADING.adoc, docs/docinfo.xml.in: > finalize text...

...v at alioth-lists.debian.net> wrote: > I'm starting down the path of testing. > > > There are commits in the rc tag that are not on master: > > $ git log --oneline ..v2.8.3-rc1 > 3d286fb1b (tag: v2.8.3-rc1, jimklimov/pre-283-2) appveyor.yml: handle > also FTY and fightwarn branches > 4e92275c1 .github/workflows/codeql.yml: handle also FTY and fightwarn > branches > 504706d45 Makefile.am: nut-scanner does directly depend on clients after > all > 051b49d9f Revert "Revert "NEWS.adoc, UPGRADING.adoc, docs/docinfo.xml.in: > finalize text...

So, NUT v2.8.3-rc1 is out. I first thought it was the release, but some CI runs convinced me otherwise, so there would be a bit of back and forth on the master branch as some recipes get fixed. Apparently, some parallel runs stepped onto each other's toes sometimes, but coinciding the wrong way just once in a few hundred builds. Hopefully I found why and will re-publish in a few hours. Jim

So, NUT v2.8.3-rc1 is out. I first thought it was the release, but some CI runs convinced me otherwise, so there would be a bit of back and forth on the master branch as some recipes get fixed. Apparently, some parallel runs stepped onto each other's toes sometimes, but coinciding the wrong way just once in a few hundred builds. Hopefully I found why and will re-publish in a few hours. Jim

...ould "shutdown/reboot" the USB port acting as an UPS for Pi... * The Pi power socket is dumb-USB so the host does not "see" any IDs about it. * Currently trying with a USB-C port on the MoBo, and a USB-C to USB-C cable rated for 60W -- and so far it survived a few loops of NUT fightwarn builds. Complains of undervoltage fairly frequently (every 30-60s), but now did not crash yet. Jim On Mon, Sep 16, 2024, 13:57 Greg Troxel via Nut-upsuser < nut-upsuser at alioth-lists.debian.net> wrote: > Kelly Byrd <kbyrd at memcpy.com> writes: > > > With USB-C ports a...

...uot; the USB port acting as an UPS for Pi... > > * The Pi power socket is dumb-USB so the host does not "see" any IDs about > it. > > * Currently trying with a USB-C port on the MoBo, and a USB-C to USB-C > cable rated for 60W -- and so far it survived a few loops of NUT fightwarn > builds. Complains of undervoltage fairly frequently (every 30-60s), but now > did not crash yet. > > Jim > > > On Mon, Sep 16, 2024, 13:57 Greg Troxel via Nut-upsuser < > nut-upsuser at alioth-lists.debian.net> wrote: > >> Kelly Byrd <kbyrd at memcpy.com&...

...as an UPS for Pi... >> >> * The Pi power socket is dumb-USB so the host does not "see" any IDs >> about it. >> >> * Currently trying with a USB-C port on the MoBo, and a USB-C to USB-C >> cable rated for 60W -- and so far it survived a few loops of NUT fightwarn >> builds. Complains of undervoltage fairly frequently (every 30-60s), but now >> did not crash yet. >> >> Jim >> >> >> On Mon, Sep 16, 2024, 13:57 Greg Troxel via Nut-upsuser < >> nut-upsuser at alioth-lists.debian.net> wrote: >> >>...

...;>> >>> * The Pi power socket is dumb-USB so the host does not "see" any IDs >>> about it. >>> >>> * Currently trying with a USB-C port on the MoBo, and a USB-C to USB-C >>> cable rated for 60W -- and so far it survived a few loops of NUT fightwarn >>> builds. Complains of undervoltage fairly frequently (every 30-60s), but now >>> did not crash yet. >>> >>> Jim >>> >>> >>> On Mon, Sep 16, 2024, 13:57 Greg Troxel via Nut-upsuser < >>> nut-upsuser at alioth-lists.debian....

..., which just now finally went online as a usable MVP (chiseling needed, but many things work and bring value). The farm is now replaying some historical commits from the master branch, starting with v2.7.4 tag, to save some code-quality analysis history so we can gauge its evolution with the "fightwarn" branch effort and beyond. Many of these builds are expected to be "flaky" as their state of codebase was evolving the tooling and warnings for CI. Hopefully current master will fare better ;) The dynaMatrix Jenkins Shared Library is this way a new open-source project in our fold: h...

..., which just now finally went online as a usable MVP (chiseling needed, but many things work and bring value). The farm is now replaying some historical commits from the master branch, starting with v2.7.4 tag, to save some code-quality analysis history so we can gauge its evolution with the "fightwarn" branch effort and beyond. Many of these builds are expected to be "flaky" as their state of codebase was evolving the tooling and warnings for CI. Hopefully current master will fare better ;) The dynaMatrix Jenkins Shared Library is this way a new open-source project in our fold: h...

Kelly Byrd <kbyrd at memcpy.com> writes: > With USB-C ports and cables, there are a ton of profiles, I don't know what > the new Pi's support, but likely something like 3A @ 5V, 9V, or 12V over > USB-C Up to the RPI4, I was pretty sure there wasn't PD, just 5V and it drew what it drew, and you hoped that the supply was big enough. It seems the RPI5 will use PD if