Stream-Mapparr

13 Commits 1 Branch 0 Tags

2 Commits

Author	SHA1	Message	Date
Claude	03b8bfc31e	Add emojis, fix visibility logic, and add WebSocket notifications Changes: - Add tasteful emojis to plugin GUI fields and action labels - Fix bug: iterate sorted_channels instead of group_channels (line 1411) - Fix visibility logic: enable channels with >= 1 streams instead of 0-1 * Channels with >= 1 streams are now enabled (highest priority only) * Channels with 0 streams are disabled * Duplicate channels (lower priority in group) are disabled * Attached channels remain disabled - Add real-time WebSocket progress notifications for: * Preview Changes action (stream_mapparr_preview) * Add Streams to Channels action (stream_mapparr_add) * Manage Channel Visibility action (stream_mapparr_visibility) - Update action descriptions to reflect corrected behavior This resolves the contradiction where add_streams_to_channels would create channels with multiple streams, and manage_channel_visibility would immediately disable them.	2025-11-06 13:11:31 +00:00
Claude	331355e846	Fix KeyError: 'stream_count' in manage_channel_visibility Root cause: Lines 1414-1415 were trying to access non-existent fields 'stream_count' and 'attached' directly from channel objects. These values are actually stored in the channel_stream_counts dictionary and channels_attached_to_others set respectively. Changes: - Fixed field access to use correct data structures - Added error handling to check if channel exists in stream_counts - Added debug logging to show evaluation details for each channel - Added full traceback logging in exception handler for better debugging This fixes the error: "Error managing channel visibility: 'stream_count'"	2025-11-03 14:20:05 +00:00

Author

SHA1

Message

Date

Claude

03b8bfc31e

Add emojis, fix visibility logic, and add WebSocket notifications

Changes:
- Add tasteful emojis to plugin GUI fields and action labels
- Fix bug: iterate sorted_channels instead of group_channels (line 1411)
- Fix visibility logic: enable channels with >= 1 streams instead of 0-1
  * Channels with >= 1 streams are now enabled (highest priority only)
  * Channels with 0 streams are disabled
  * Duplicate channels (lower priority in group) are disabled
  * Attached channels remain disabled
- Add real-time WebSocket progress notifications for:
  * Preview Changes action (stream_mapparr_preview)
  * Add Streams to Channels action (stream_mapparr_add)
  * Manage Channel Visibility action (stream_mapparr_visibility)
- Update action descriptions to reflect corrected behavior

This resolves the contradiction where add_streams_to_channels would
create channels with multiple streams, and manage_channel_visibility
would immediately disable them.

2025-11-06 13:11:31 +00:00

Claude

331355e846

Fix KeyError: 'stream_count' in manage_channel_visibility

Root cause: Lines 1414-1415 were trying to access non-existent fields
'stream_count' and 'attached' directly from channel objects. These values
are actually stored in the channel_stream_counts dictionary and
channels_attached_to_others set respectively.

Changes:
- Fixed field access to use correct data structures
- Added error handling to check if channel exists in stream_counts
- Added debug logging to show evaluation details for each channel
- Added full traceback logging in exception handler for better debugging

This fixes the error: "Error managing channel visibility: 'stream_count'"

2025-11-03 14:20:05 +00:00