Search results

CI: Consider using more <code>AC_REPLACE_FUNCS()</code>

CIEntries related to continuous integration infrastructure (here CI = tools + scripts + recipes)Entries related to continuous integration infrastructure (here CI = tools + scripts + recipes)

packaging

portabilityWe want NUT to build and run everywhere possibleWe want NUT to build and run everywhere possible

refactor/fightwarnPR or issue proposal to improve code maintainability without functional changes, or to fix warningsPR or issue proposal to improve code maintainability without functional changes, or to fix warnings

Status: Open.

#2830 In networkupstools/nut;

· jimklimov opened on Mar 2, 2025

· 

2.8.4

Tightening NUT

C-strIssues and PRs about C/C++ methods, headers and data types dealing with strings and memory blocksIssues and PRs about C/C++ methods, headers and data types dealing with strings and memory blocks

portabilityWe want NUT to build and run everywhere possibleWe want NUT to build and run everywhere possible

refactor/fightwarnPR or issue proposal to improve code maintainability without functional changes, or to fix warningsPR or issue proposal to improve code maintainability without functional changes, or to fix warnings

Status: Open.

#2824 In networkupstools/nut;

· jimklimov opened on Feb 26, 2025

· 

2.8.4

Consolidate bool string parsing into a common method

augeasConfiguration file parser (reader, writer) multi-tool for scripting, etc.Configuration file parser (reader, writer) multi-tool for scripting, etc.

C++

C-boolIssues and PRs about C/C++ methods, headers and data types dealing with boolean typesIssues and PRs about C/C++ methods, headers and data types dealing with boolean types

C-strIssues and PRs about C/C++ methods, headers and data types dealing with strings and memory blocksIssues and PRs about C/C++ methods, headers and data types dealing with strings and memory blocks

enhancement

refactor/fightwarnPR or issue proposal to improve code maintainability without functional changes, or to fix warningsPR or issue proposal to improve code maintainability without functional changes, or to fix warnings

Status: Open.

#2811 In networkupstools/nut;

· jimklimov opened on Feb 23, 2025

· 

2.8.4

Clean-up or legalise: revise <code>status_set()</code> values vs. the NUT standard dictionary

documentation

NUT protocols

portabilityWe want NUT to build and run everywhere possibleWe want NUT to build and run everywhere possible

refactor/fightwarnPR or issue proposal to improve code maintainability without functional changes, or to fix warningsPR or issue proposal to improve code maintainability without functional changes, or to fix warnings

upsmon

Status: Open.

#2708 In networkupstools/nut;

· jimklimov opened on Dec 3, 2024

· 

2.8.4

CI: a step towards faster builds: use <code>libcommon*</code> as layers or separate flavours, not as independent builds where avoidable

CIEntries related to continuous integration infrastructure (here CI = tools + scripts + recipes)Entries related to continuous integration infrastructure (here CI = tools + scripts + recipes)

portabilityWe want NUT to build and run everywhere possibleWe want NUT to build and run everywhere possible

refactor/fightwarnPR or issue proposal to improve code maintainability without functional changes, or to fix warningsPR or issue proposal to improve code maintainability without functional changes, or to fix warnings

Status: Open.

#2584 In networkupstools/nut;

· jimklimov opened on Aug 5, 2024

· 

2.8.4

<code>pijuice</code> driver uses <code>status_set()</code> unidiomatically

GPIO and I2CDrivers talking to devices (or their chips) over internal GPIO or I2C interfacesDrivers talking to devices (or their chips) over internal GPIO or I2C interfaces

raspberry

refactor/fightwarnPR or issue proposal to improve code maintainability without functional changes, or to fix warningsPR or issue proposal to improve code maintainability without functional changes, or to fix warnings

Status: Open.

#2436 In networkupstools/nut;

· jimklimov opened on May 10, 2024

· 

2.8.4

Revise driver man pages to include all known options (and their data types)

documentation

enhancement

impacts-release-2.8.2Issues reported against NUT release 2.8.2 (maybe vanilla or with minor packaging tweaks)Issues reported against NUT release 2.8.2 (maybe vanilla or with minor packaging tweaks)

Low-hanging fruitA proposal or issue that is good for newcomers to codebase or otherwise a quick winA proposal or issue that is good for newcomers to codebase or otherwise a quick win

nutconfNUT configuration library and toolNUT configuration library and tool

refactor/fightwarnPR or issue proposal to improve code maintainability without functional changes, or to fix warningsPR or issue proposal to improve code maintainability without functional changes, or to fix warnings

Status: Open.

#2422 In networkupstools/nut;

· jimklimov opened on Apr 27, 2024

· 

2.8.4

Refactor: boolean settings not treated as booleans

C-boolIssues and PRs about C/C++ methods, headers and data types dealing with boolean typesIssues and PRs about C/C++ methods, headers and data types dealing with boolean types

C-strIssues and PRs about C/C++ methods, headers and data types dealing with strings and memory blocksIssues and PRs about C/C++ methods, headers and data types dealing with strings and memory blocks

impacts-release-2.8.2Issues reported against NUT release 2.8.2 (maybe vanilla or with minor packaging tweaks)Issues reported against NUT release 2.8.2 (maybe vanilla or with minor packaging tweaks)

portabilityWe want NUT to build and run everywhere possibleWe want NUT to build and run everywhere possible

Qx protocol driverDriver based on Megatec Q<number> such as new nutdrv_qx, or obsoleted blazer and some othersDriver based on Megatec Q<number> such as new nutdrv_qx, or obsoleted blazer and some others

refactor/fightwarnPR or issue proposal to improve code maintainability without functional changes, or to fix warningsPR or issue proposal to improve code maintainability without functional changes, or to fix warnings

Status: Open.

#2421 In networkupstools/nut;

· jimklimov opened on Apr 27, 2024

· 

2.8.4

Refactor: min/max voltage settings to guesstimate battery charge remaining runtime - promote <code>runtimecal</code> as one common solution/pattern

enhancement

impacts-release-2.8.2Issues reported against NUT release 2.8.2 (maybe vanilla or with minor packaging tweaks)Issues reported against NUT release 2.8.2 (maybe vanilla or with minor packaging tweaks)

portabilityWe want NUT to build and run everywhere possibleWe want NUT to build and run everywhere possible

refactor/fightwarnPR or issue proposal to improve code maintainability without functional changes, or to fix warningsPR or issue proposal to improve code maintainability without functional changes, or to fix warnings

Status: Open.

#2420 In networkupstools/nut;

· jimklimov opened on Apr 27, 2024

· 

NUT 2.9

Refactor: Unify config options for <code>apc_modbus</code> and other Modbus drivers (at least)

documentation

impacts-release-2.8.2Issues reported against NUT release 2.8.2 (maybe vanilla or with minor packaging tweaks)Issues reported against NUT release 2.8.2 (maybe vanilla or with minor packaging tweaks)

modbus

refactor/fightwarnPR or issue proposal to improve code maintainability without functional changes, or to fix warningsPR or issue proposal to improve code maintainability without functional changes, or to fix warnings

Status: Open.

#2419 In networkupstools/nut;

· jimklimov opened on Apr 26, 2024

· 

2.8.4

Implement missing WIN32 bits for <code>nutconf</code> (library, test and tool)

C++

Low-hanging fruitA proposal or issue that is good for newcomers to codebase or otherwise a quick winA proposal or issue that is good for newcomers to codebase or otherwise a quick win

nutconfNUT configuration library and toolNUT configuration library and tool

portabilityWe want NUT to build and run everywhere possibleWe want NUT to build and run everywhere possible

refactor/fightwarnPR or issue proposal to improve code maintainability without functional changes, or to fix warningsPR or issue proposal to improve code maintainability without functional changes, or to fix warnings

Windows

Windows-not-on-par-with-POSIXAspect of Windows builds known to be dysfunctional compared to POSIX builds; fix needed to be on parAspect of Windows builds known to be dysfunctional compared to POSIX builds; fix needed to be on par

Status: Open.

#2293 In networkupstools/nut;

· jimklimov opened on Jan 29, 2024

· 

2.8.4

Rectify definition and use of <code>#if(def) HAVE_SOMETHING</code> (<code>WITH_SOMETHING</code>, etc.)

enhancement

refactor/fightwarnPR or issue proposal to improve code maintainability without functional changes, or to fix warningsPR or issue proposal to improve code maintainability without functional changes, or to fix warnings

Status: Open.

#1739 In networkupstools/nut;

· jimklimov opened on Dec 22, 2022