Bug report rules

Bug reports for SVR.JS itself.
This forum is locked, please report issues on SVR.JS Git server.
Locked
User avatar
DorianNiemiecSVRJS
Administrator
Posts: 31
Joined: July 7th, 2023, 12:00 am
Location: Poland
Gender:
Contact:

exclamation Bug report rules

Post by DorianNiemiecSVRJS »

  1. Stay on topic: This subboard is solely for reporting bugs related to our platform/software. Please refrain from discussing unrelated topics or posting general questions.
  2. Search before posting: Before submitting a new bug report, please search the subboard to ensure that the issue hasn't already been reported. Duplicate reports will be removed to keep the board organized.
  3. Provide a clear title: When creating a new bug report, use a concise and descriptive title that accurately summarizes the issue. This will help others quickly identify and address the problem.
  4. Use a standardized bug reporting format: To ensure consistency and clarity, please follow the bug reporting format outlined below:
    • Title: Briefly describe the bug.
    • Platform/Software Version: Specify the version of the platform/software where the bug occurred.
    • Steps to Reproduce: Provide a detailed list of steps required to reproduce the bug. Be as specific as possible to help others recreate the issue.
    • Expected Behavior: Explain what you expected to happen when performing the steps above.
    • Actual Behavior: Describe what actually happened when performing the steps above.
    • Additional Information: Include any additional details that might be relevant to the bug, such as error messages, screenshots, or system configurations.
  5. Be respectful: When discussing bugs, remember to be polite and respectful towards other users. Avoid personal attacks or offensive language. Constructive criticism is encouraged, but keep the focus on resolving the issue at hand.
  6. Avoid spamming or excessive bumping: Please refrain from repeatedly posting the same bug report or unnecessarily bumping threads. This will help maintain a clean and organized subboard.
  7. Follow up on your bug reports: If you receive responses or requests for additional information regarding your bug report, please respond in a timely manner. This will help facilitate the resolution process.
  8. Report security vulnerabilities privately: If you discover a security vulnerability, please do not post it publicly on the subboard. Instead, report it privately to vulnerability-reports[at]svrjs[dot]org.
Remember, these rules are subject to change or modification as needed. Thank you for your cooperation in making our bug report subboard a helpful and organized resource!
I oppose "You may be a victim of software counterfeiting" windows.
When I see school students' PHP code, I may ask: But where is mysqli_real_escape_string?
Download SVR.JS
Locked