[script.module.pyrollbar@matrix] 1.4.0

[zim514]

Add-on details:

• General

  • Add-on name: pyrollbar
  • Add-on ID: script.module.pyrollbar
  • Version number: 1.4.0
  • Kodi/repository version: matrix

• Code location

  • URL: https://github.com/rollbar/pyrollbar

Python notifier for reporting exceptions, errors, and log messages to Rollbar.

Description of changes:

Update Rollbar API to 1.4.0

Checklist:

• My code follows the add-on rules and piracy stance of this project.
• I have read the CONTRIBUTING document
• Each add-on submission should be a single commit with using the following style: [plugin.video.foo] v1.0.0

[keithah]

@kodiai review

[kodiai]

Kodiai Add-on Review

Summary

Reviewed 1 changed addon on matrix across 23 scoped patches in 17 evidence chunks. Found 19 model-backed contextual rule findings.

Findings

• ERROR script.module.pyrollbar/LICENSE: License file must be named LICENSE.txt; changed path is script.module.pyrollbar/LICENSE.
• ERROR script.module.pyrollbar/lib/rollbar/kodi/__init__.py:1: Added text uses CRLF line endings; Kodi add-on text files must use UNIX LF line endings.
• ERROR script.module.pyrollbar/lib/rollbar/__init__.py:477: External endpoint parameter configures transmission of telemetry data to api.rollbar.com, implementing prohibited client-side analytics.
• ERROR script.module.pyrollbar/lib/rollbar/__init__.py:468: IP address capture parameter enables collection of personally identifiable information for external telemetry transmission.
• ERROR script.module.pyrollbar/lib/rollbar/__init__.py:472: Email capture parameter enables collection of PII for external analytics transmission.
• ERROR script.module.pyrollbar/lib/rollbar/__init__.py:473: Username capture parameter enables collection of PII for external analytics transmission.
• ERROR script.module.pyrollbar/lib/rollbar/__init__.py:485: HTTP proxy configuration parameter enables transmission of reports to Rollbar service through proxy servers.
• ERROR script.module.pyrollbar/lib/rollbar/__init__.py:535: Thread pool handler initialization enables asynchronous transmission of collected telemetry and error data.
• ERROR script.module.pyrollbar/lib/rollbar/__init__.py:677: Function send_payload directly transmits exception data, session information, and user details to external services via HTTP, violating the analytics transmission rule.
• WARN script.module.pyrollbar/lib/rollbar/__init__.py:1627: Functions (lines 1353–1400, 1405–1625, 1627–1628) build request/error data payloads for Rollbar telemetry transmission service. Kodi rules forbid direct analytics/telemetry transmission in addons. Confirm whether module exceptions apply.
• ERROR script.module.pyrollbar/lib/rollbar/cli.py:15: Direct transmission of telemetry to Rollbar service via rollbar.report_message(). Kodi rules prohibit direct usage of analytics within add-ons.
• ERROR script.module.pyrollbar/lib/rollbar/__init__.py:1731: Function _send_payload_pool() transmits payload to external Rollbar API endpoint. Direct analytics transmission violates Kodi submission rules.
• ERROR script.module.pyrollbar/lib/rollbar/__init__.py:1869: Function _send_payload_httpx() transmits payload via httpx to Rollbar 'item/' endpoint. This constitutes prohibited direct analytics usage.
• ERROR script.module.pyrollbar/lib/rollbar/kodi/__init__.py:41: Direct initialization of external analytics service Rollbar violates Kodi rule prohibiting analytics transmission from addons.
• ERROR script.module.pyrollbar/lib/rollbar/kodi/__init__.py:42: Direct transmission of error and system data to external Rollbar service violates prohibition on analytics use from addons.
• ERROR script.module.pyrollbar/lib/rollbar/lib/_async.py:44: Function report_exc_info reports exceptions to Rollbar servers. Direct analytics/telemetry transmission from add-ons is prohibited; this must be handled server-side using user-agent.
• ERROR script.module.pyrollbar/lib/rollbar/lib/_async.py:78: Function report_message reports messages to Rollbar servers. Direct analytics/telemetry transmission from add-ons is prohibited; this must be handled server-side using user-agent.
• ERROR script.module.pyrollbar/lib/rollbar/lib/_async.py:138: Code directly transmits error tracking data to external Rollbar service via HTTP POST, violating the ban on analytics/telemetry transmission from add-ons.
• WARN script.module.pyrollbar/lib/rollbar/lib/thread_pool.py:38: Module submits payloads with access tokens to external services. Verify that analytics transmission requires explicit dependent add-on initialization and does not auto-occur on module import.
• WARN script.module.pyrollbar/lib/rollbar/lib/transforms/batched.py:1: Add-on is the Rollbar analytics library designed to transmit telemetry to external servers, which may violate the usage-analytics rule.
• ERROR script.module.pyrollbar/lib/rollbar/logger.py:86: RollbarHandler initializes Rollbar error reporting service without user consent mechanism, enabling automatic telemetry transmission to external servers

Verdict

Needs human review: 18 errors and 3 warnings found. Final approval remains with a human reviewer.

[zim514]

@romanvm It turns out that rollbar 1.4.0 requires python 3.10+ and therefore does not work with any of the windows kodi packages. Rollbar 1.3.0 will work

Would releasing 1.3.0 under a version number like "2026.08.08+1.3.0" to force a rollback be an acceptable solution, or is there another rollback option?

Alternatively I could remove the rollbar dependency from my addon, but some old addons use it as well (which are presumably broken now):

INFO: Reverse dependencies: plugin.video.spurs-tv, script.service.hue (2)
INFO: Reverse dependencies (in lower branches): plugin.video.ecbtv, plugin.video.kermodeandmayo, plugin.video.spurs-tv (3)

[romanvm]

That is unfortunate, considering that the submission has been pushed into "matrix" branch that is supposed to be compatible with the older Kodi version, starting from Matrix. Direct downgrading is not an option because Kodi uses so called lexicographic comparison for comparing version numbers. In short, it compares ASCII codes of the respective characters, so "1.2" is considered higher than "1.1" and "1". Yes, technically "2026.08.08+1.3.0" will be higher than "1.4.0", but I'm thinking for consistent version numbering for the future versions. If a person who will maintain this library in the Kodi repo will be able to maitain the consistent version numbering with the new schema then I see no problem with that.

[zim514]

Sadly it looks like the addon checker will not accept this format:

ERROR: Invalid version 2026.08.09+1.3.0 in addon.xml. Please use the major.minor.revision (e.g. 1.0.0) format or major.minor.revision+localversion_identifier (e.g. 1.0.0+matrix.1)

Any recommendations?

[romanvm]

Sorry for a late reply. Claude code suggests "1.4.0.1+v1_3_0" version that should pass validation and will be considered higher than "1.4.0" to trigger an update. Try this variant. And include an explanation somewhere in the changelog.

[zim514]

Though it gets through the addoncheck, it doesn't get through create_repository.py. I'm using the chad_parry script. I can work around it for my repo, but I'm worried about breaking the official repo if I submit it. Do you know if it uses the same script?

Run

Traceback (most recent call last):
  File "./repo/create_repository.py", line 465, in <module>
    main()
  File "./repo/create_repository.py", line 455, in main
    create_repository(
  File "./repo/create_repository.py", line 388, in create_repository
    raise result.exc_info[1]
  File "./repo/create_repository.py", line 332, in fetch_addon_to_result_slot
    addon_metadata = fetch_addon(addon_location, target_folder)
  File "./repo/create_repository.py", line 320, in fetch_addon
    addon_metadata = fetch_addon_from_git(addon_location, target_folder)
  File "./repo/create_repository.py", line 206, in fetch_addon_from_git
    addon_metadata = parse_metadata(metadata_path)
  File "./repo/create_repository.py", line 143, in parse_metadata
    raise RuntimeError(
RuntimeError: Invalid add-on verson: 1.4.0.1+v1_3_0

[romanvm]

I have no idea what that script does but you can always create a pull request with addon submission manually. You don't need a script for that. As the last resort I can bypass the addon checker and merge the PR after review.

[zim514]

I went ahead and opened a PR here