"Bald Eagle" <cre### [at] netscapenet> wrote:
>
> Here again, I will shamelessly make a plug for some kind of project management
> system.
>

Github has that and many other tools, but you have to pay.
https://github.com/features/issues I'm not a github user so I know little of it.

I asked their "thing" for a summary:

Copilot said: Here is a summary of the issues

Here is a summary of the issues for POV-Ray, ordered by severity (highest to
lowest). Please note: this is based on public issue titles, labels, and visible

project maintainers.
Critical Bugs & Vulnerabilities

    Potential Vulnerabilities (Cloned Functions)
        Fix potential vulnerable cloned function
        Fix potential vulnerable cloned functions
        Fix potential vulnerable cloned function Severity: Security-related,
likely the most urgent.

    Bug: Functionality Failure
        [BUG] function "trace" fails to find intersections in distances of more
than 10⁷ units Severity: Major feature broken for large distances.

    Build/Compatibility Failures
        [BUILD][UNIX] Failure on macOS w/ Xcode 16.4, error: unknown type name
'Fixed'
        [BUILD][UNIX] Build fails with strict-aliasing violations
        [BUILD][UNIX] Test for Boost Libraries fail on Apple silicon (Homebrew
path change) Severity: Prevents build on certain platforms.

    Bug: Parse/Error Handling
        [BUG] Parse error when using povray built by GCC 13, no error with GCC
12
        [BUG] doesn't give an error if a polygon is not 2D
        [BUG][UNIX] Failed to parse command line option with space in filename
Severity: Could lead to silent failures or unpredictable behavior.

    Bug: Memory/Allocation
        Assigned interior causes a bad allocation error Severity: May cause
crashes or data corruption.

    Bug: Incorrect Rendering
        Photons do not work properly with true inverse power fading
        Option "Keep Single Instance" is not working for *.inc files
        Error in POV-RAY output generated from Project Chrono Demo Severity: Can
result in incorrect output or broken features.

Medium Severity

    Performance/Optimization
        Usage of Enhanced Math Library for better performance
        AVX512 version for POVRAY Severity: Performance improvements, not
critical but useful.

    Feature Requests: Important for Users
        [FEATURE] support all Opentype font formats
        [FEATURE] LaTeX support
        Can we develop POV-RayMCP similar to BlenderMCP? Severity: Not bugs, but
could be important for project adoption.

Low Severity / Minor Issues

    Minor Bugs and UI Issues
        Debug string is not displayed in console if start with more than 14
hyphens
        Need to run POVRAY on a single thread
        Updates to screen.inc
        Issue a parse warning for out-of-domain arguments to the srgb keywords
        remove unecessary nullptr check before 'delete' and 'delete[]'
        Apply translate and rotate to user_defined cameras.
        Fixing some missing stuff in VS 2022
        What about 3.7 branch ? Severity: Minor bugs, enhancements, or
low-priority tasks.

Note:

    This list is based on 30 issues (API limit). For a complete and up-to-date
list, view all POV-Ray issues on GitHub.

on user impact, security, or strategic goals.
    If you want a more detailed triage or deeper analysis of a specific issue,
let me know!


ingo

Post a reply to this message