Mislabelled project

[hucker]

Sorry if this sounds official or rude, Gemini constructed it for me with technical information:

Bug Report: Critical Project Naming Collision & Data Inconsistency
�Software: BoincTasks JS (Version 2.8.6)
Environment: 24-core Ryzen / High-thread count / Multi-Project Monitoring
Projects Involved: ODLK (Natalia/Termit), ODLK1 (Italy/ice00), and ODLK 2025 (Unlisted).
�The Core Issue
�BoincTasks JS is failing to maintain a unique identity for different projects that share a common directory name. This is causing "Identity Theft" in the UI where distinct projects are merged into one label, making it impossible to distinguish between work from different servers.
�Detailed Observations:
�The "Folder vs. Name" Parser Conflict:
�I am running ODLK (Natalia) and Latin Squares (ODLK1 Italy) simultaneously.
�Both projects use the directory /latinsquares/ on the local disk.
�BoincTasks JS is inconsistently overriding the Project Name with the Directory Name.
�Live "Name-Flipping" on Active Tasks:
�On my 24-core machine, I can see running tasks for the same project being labeled differently at the same time. Some say "ODLK Project" and some say "Latin Squares Project."
�The label appears to flip during the 30-second refresh cycle, suggesting a race condition in the live data parser.
�The "Ready to Report" Identity Jump:
�I have witnessed tasks labeled ODLK while running "jump" to the Latin Squares label the moment they move to the "Ready to Report" status.
�This indicates the software stops trusting the "Friendly Name" from RAM once a task is no longer "Active" and defaults to the disk folder name.
�Identical Application Name Collision:
�Both projects use identical application names (e.g., odlk3@home, odlkmin@home).
�Since the Project Name, Directory Name, and Application Name are all now identical or overlapping in the UI, it is impossible for a user to know which task belongs to which server without checking the Master URL column.
�Impact on User:
�For power users running dozens of threads, the current behavior makes monitoring server health impossible. If one server (e.g., the Italian solar-powered server) goes offline, the UI does not show which tasks are stalled because they are all labeled as "Latin Squares."
�Requested Fix:
�Please prioritize the Project Name provided by the BOINC client's client_state.xml as the primary key for the "Project" column. The software should never fall back to the directory name if a Friendly Name is available, especially in the "Ready to Report" queue.