04/06/2021, 18:36:46 [TV] DidFinishLaunching
04/06/2021, 18:36:46 [TV] WARNING - Removing Accessories
04/06/2021, 18:36:46 [TV] (TV)INFO - Loading activities...
04/06/2021, 18:36:46 Preparing Advertiser for 'HOOBS A281' using bonjour-hap backend!
04/06/2021, 18:36:47 Starting to advertise 'HOOBS A281' using bonjour-hap backend!
04/06/2021, 18:36:47 Bridge is running on port 51826.
04/06/2021, 18:36:48 [TV] (TV)INFO - Adding Accessory : TV-TV
04/06/2021, 18:36:48 [TV] (TV)INFO - configuring Main TV Service
04/06/2021, 18:36:48 [TV] (TV)INFO - Creating TV Service
04/06/2021, 18:36:48 [TV] (TV)INFO - Creating Input Service - PS5
04/06/2021, 18:36:48 [TV] (TV)INFO - Creating Input Service - YouTube
04/06/2021, 18:36:48 [TV] (TV)INFO - Creating Input Service - Amazon Prime
04/06/2021, 18:36:48 [TV] (TV)INFO - Creating Input Service - Sonos
04/06/2021, 18:36:48 [TV] (TV)INFO - Creating Input Service - Xbox
04/06/2021, 18:36:48 [TV] (TV)INFO - Creating Input Service - Watch TV
04/06/2021, 18:36:48 [TV] (TV)INFO - Creating Input Service - Apple TV
04/06/2021, 18:36:48 [TV] (TV)INFO - Creating Input Service - Netflix
04/06/2021, 18:36:48 [TV] (TV)WARNING - No main Activity that match config file found, default to first one
04/06/2021, 18:36:48 [TV] (TV)INFO - Configuring Main Activity PS5
04/06/2021, 18:36:48 [TV] (TV)INFO - Creating TV Speaker Service
04/06/2021, 18:36:48 [TV] (TV)INFO - Adding Accessory : TV-PS5
04/06/2021, 18:36:48 [TV] (TV)INFO - Discovered Activity : PS5
04/06/2021, 18:36:48 [TV] (TV)INFO - Creating Switch Service PS5/PS5
04/06/2021, 18:36:48 [TV] (TV)INFO - Adding Accessory : TV-YouTube
04/06/2021, 18:36:48 [TV] (TV)INFO - Discovered Activity : YouTube
04/06/2021, 18:36:48 [TV] (TV)INFO - Creating Switch Service YouTube/YouTube
04/06/2021, 18:36:48 [TV] (TV)INFO - Adding Accessory : TV-Amazon Prime
04/06/2021, 18:36:48 [TV] (TV)INFO - Discovered Activity : Amazon Prime
04/06/2021, 18:36:48 [TV] (TV)INFO - Creating Switch Service Amazon Prime/Amazon Prime
04/06/2021, 18:36:48 [TV] (TV)INFO - Adding Accessory : TV-Sonos
04/06/2021, 18:36:48 [TV] (TV)INFO - Discovered Activity : Sonos
04/06/2021, 18:36:48 [TV] (TV)INFO - Creating Switch Service Sonos/Sonos
04/06/2021, 18:36:48 [TV] (TV)INFO - Adding Accessory : TV-Xbox
04/06/2021, 18:36:48 [TV] (TV)INFO - Discovered Activity : Xbox
04/06/2021, 18:36:48 [TV] (TV)INFO - Creating Switch Service Xbox/Xbox
04/06/2021, 18:36:48 [TV] (TV)INFO - Adding Accessory : TV-Watch TV
04/06/2021, 18:36:48 [TV] (TV)INFO - Discovered Activity : Watch TV
04/06/2021, 18:36:48 [TV] (TV)INFO - Creating Switch Service Watch TV/Watch TV
04/06/2021, 18:36:48 [TV] (TV)INFO - Adding Accessory : TV-Apple TV
04/06/2021, 18:36:48 [TV] (TV)INFO - Discovered Activity : Apple TV
04/06/2021, 18:36:48 [TV] (TV)INFO - Creating Switch Service Apple TV/Apple TV
04/06/2021, 18:36:48 [TV] (TV)INFO - Adding Accessory : TV-Netflix
04/06/2021, 18:36:48 [TV] (TV)INFO - Discovered Activity : Netflix
04/06/2021, 18:36:48 [TV] (TV)INFO - Creating Switch Service Netflix/Netflix
04/06/2021, 18:36:48 [TV] (TV)WARNING - setupFoundAccessories - TV accessory added in your bridge, if another plugin is exposing a TV accessory this one might not be visible in your remote widget
04/06/2021, 18:36:48 [TV] (TV)INFO - Loading sequences...
04/06/2021, 18:36:48 [TV] (TV)INFO - Discovered sequence : Pause2(1615029)
04/06/2021, 18:36:48 [TV] (TV)INFO - Adding Accessory : TV-Pause2(1615029)
04/06/2021, 18:36:48 [TV] (TV)INFO - Creating Switch Service Pause2(1615029)/Pause2(1615029)-Sequence
04/06/2021, 18:36:48 [TV] (TV)INFO - Discovered sequence : Pause3(1615030)
04/06/2021, 18:36:48 [TV] (TV)INFO - Adding Accessory : TV-Pause3(1615030)
04/06/2021, 18:36:48 [TV] (TV)INFO - Creating Switch Service Pause3(1615030)/Pause3(1615030)-Sequence
04/06/2021, 18:36:48 [TV] (TV)INFO - Discovered sequence : Pause4(1615031)
04/06/2021, 18:36:48 [TV] (TV)INFO - Adding Accessory : TV-Pause4(1615031)
04/06/2021, 18:36:48 [TV] (TV)INFO - Creating Switch Service Pause4(1615031)/Pause4(1615031)-Sequence
04/06/2021, 18:36:49 [TV] (TV)INFO - Discovered sequence : Pause1(1615028)
04/06/2021, 18:36:49 [TV] (TV)INFO - Adding Accessory : TV-Pause1(1615028)
04/06/2021, 18:36:49 [TV] (TV)INFO - Creating Switch Service Pause1(1615028)/Pause1(1615028)-Sequence
04/06/2021, 18:41:37 Got SIGINT, shutting down Bridge...
04/06/2021, 18:41:37 [TV] INFO - shutdown
04/06/2021, 18:41:37 [TV] INFO - shutdown
04/06/2021, 18:41:45 Initializing HAP-NodeJS v0.9.3...
04/06/2021, 18:41:47 [6/4/2021, 11:41:47 AM] The plugin "homebridge-deebot" requires Node.js version of ^14.16.1 which does not satisfy the current Node.js version of v14.16.0. You may need to upgrade your installation of Node.js - see https://git.io/JTKEF
04/06/2021, 18:41:47 Loaded plugin 'homebridge-deebot'
04/06/2021, 18:41:47 [6/4/2021, 11:41:47 AM] Registering platform 'homebridge-deebot.Deebot'
04/06/2021, 18:41:47 Loaded plugin 'homebridge-harmony'
04/06/2021, 18:41:47 [6/4/2021, 11:41:47 AM] Registering platform 'homebridge-harmony.HarmonyHubWebSocket'
04/06/2021, 18:41:49 Loaded plugin 'homebridge-smartthings'
04/06/2021, 18:41:49 [6/4/2021, 11:41:49 AM] Registering platform 'homebridge-smartthings.SmartThings-v2'
04/06/2021, 18:41:49 Loading 3 platforms...
04/06/2021, 18:41:49 [TV] Initializing HarmonyHubWebSocket platform...
04/06/2021, 18:41:49 [TV] HarmonyPlatform Init
04/06/2021, 18:41:49 [Deebot] Initializing Deebot platform...
04/06/2021, 18:41:49 [Deebot] ***** Disabling plugin [v3.0.3]. *****
04/06/2021, 18:41:49 [Deebot] ***** ECOVACS credentials missing from config. *****
04/06/2021, 18:41:49 [SmartThings-v2] Initializing SmartThings-v2 platform...
04/06/2021, 18:41:50 INFO: Homebridge Version: 2.7
04/06/2021, 18:41:50 INFO: SmartThings-v2 Plugin Version: 2.3.8
04/06/2021, 18:41:50 INFO: Checking Package Version for Updates...
04/06/2021, 18:41:50 [TV] DidFinishLaunching
04/06/2021, 18:41:50 [TV] WARNING - Removing Accessories
04/06/2021, 18:41:50 [TV] (TV)INFO - Loading activities...
04/06/2021, 18:41:50 INFO: Fetching SmartThings-v2 Devices. NOTICE: This may take a moment if you have a large number of device data is being loaded!
04/06/2021, 18:41:50 GOOD: Refreshing All Device Data | Source: (First Launch)
04/06/2021, 18:41:51 Preparing Advertiser for 'HOOBS A281' using bonjour-hap backend!
04/06/2021, 18:41:51 Starting to advertise 'HOOBS A281' using bonjour-hap backend!
04/06/2021, 18:41:51 Bridge is running on port 51826.
04/06/2021, 18:41:52 NOTICE: Temperature Unit is Now: (C)
04/06/2021, 18:41:52 NOTICE: Updating Global Values | HubIP: <IP_ADDRESS> | UseLocal: false
04/06/2021, 18:41:52 WARN: Devices to Remove: (0) []
04/06/2021, 18:41:52 INFO: Devices to Update: (0)
04/06/2021, 18:41:52 GOOD: Devices to Create: (9) [
04/06/2021, 18:41:52 'IKEA Motion Sensor',
04/06/2021, 18:41:52 'Lounge Socket 1',
04/06/2021, 18:41:52 'Lounge Socket 2',
04/06/2021, 18:41:52 'Lounge lights 1',
04/06/2021, 18:41:52 'Lounge lights 2',
04/06/2021, 18:41:52 'Virtual Switch 1',
04/06/2021, 18:41:52 'Virtual Switch 2',
04/06/2021, 18:41:52 'Virtual Switch 3',
04/06/2021, 18:41:52 'Virtual Switch 4'
04/06/2021, 18:41:52 ]
04/06/2021, 18:41:52 INFO: Added Device: (IKEA Motion Sensor | ce0687b8-f5a1-4ada-b07c-d05640a5bb62)
04/06/2021, 18:41:52 INFO: Added Device: (Lounge Socket 1 | e0914380-9cff-408b-8984-2ed17ac5df34)
04/06/2021, 18:41:52 INFO: Added Device: (Lounge Socket 2 | 48f324bf-e6fa-4dc6-8442-df086c9aa83c)
04/06/2021, 18:41:52 INFO: Added Device: (Lounge lights 1 | 1a2eb44e-d2cc-42e3-b1a5-079d1d2ce9f0)
04/06/2021, 18:41:52 INFO: Added Device: (Lounge lights 2 | c05c57f3-71da-436c-a7a4-d7ad993d68eb)
04/06/2021, 18:41:53 INFO: Added Device: (Virtual Switch 1 | 6bf8fd0a-91a7-4925-9a6e-0e610d5062a1)
04/06/2021, 18:41:53 INFO: Added Device: (Virtual Switch 2 | 4f1f165e-93fb-4c65-a75a-3739d6a4338e)
04/06/2021, 18:41:53 INFO: Added Device: (Virtual Switch 3 | bfd505f1-004c-49d6-b8ce-252091ab027b)
04/06/2021, 18:41:53 INFO: Added Device: (Virtual Switch 4 | d57ba780-8843-44cf-8bf0-e8381278d4d8)
04/06/2021, 18:41:53 ALERT: Total Initialization Time: (2 seconds)
04/06/2021, 18:41:53 NOTICE: Unknown Capabilities: []
04/06/2021, 18:41:53 INFO: SmartThings DeviceCache Size: (9)
04/06/2021, 18:41:53 INFO: WebServer Initiated...
04/06/2021, 18:41:53 INFO: Sending StartDirect Request to SmartThings | SendToLocalHub: (false)
04/06/2021, 18:41:53 INFO: Direct Connect Active | Listening at <IP_ADDRESS>:8000
04/06/2021, 18:41:53 [TV] (TV)INFO - Adding Accessory : TV-TV
04/06/2021, 18:41:53 [TV] (TV)INFO - configuring Main TV Service
04/06/2021, 18:41:53 [TV] (TV)INFO - Creating TV Service
04/06/2021, 18:41:53 [TV] (TV)INFO - Creating Input Service - PS5
04/06/2021, 18:41:53 [TV] (TV)INFO - Creating Input Service - YouTube
04/06/2021, 18:41:53 [TV] (TV)INFO - Creating Input Service - Amazon Prime
04/06/2021, 18:41:53 [TV] (TV)INFO - Creating Input Service - Sonos
04/06/2021, 18:41:53 [TV] (TV)INFO - Creating Input Service - Xbox
04/06/2021, 18:41:53 [TV] (TV)INFO - Creating Input Service - Watch TV
04/06/2021, 18:41:53 [TV] (TV)INFO - Creating Input Service - Apple TV
04/06/2021, 18:41:53 [TV] (TV)INFO - Creating Input Service - Netflix
04/06/2021, 18:41:53 [TV] (TV)WARNING - No main Activity that match config file found, default to first one
04/06/2021, 18:41:53 [TV] (TV)INFO - Configuring Main Activity PS5
04/06/2021, 18:41:53 [TV] (TV)INFO - Creating TV Speaker Service
04/06/2021, 18:41:53 [TV] (TV)INFO - Adding Accessory : TV-PS5
04/06/2021, 18:41:53 [TV] (TV)INFO - Discovered Activity : PS5
04/06/2021, 18:41:53 [TV] (TV)INFO - Creating Switch Service PS5/PS5
04/06/2021, 18:41:53 [TV] (TV)INFO - Adding Accessory : TV-YouTube
04/06/2021, 18:41:53 [TV] (TV)INFO - Discovered Activity : YouTube
04/06/2021, 18:41:53 [TV] (TV)INFO - Creating Switch Service YouTube/YouTube
04/06/2021, 18:41:53 [TV] (TV)INFO - Adding Accessory : TV-Amazon Prime
04/06/2021, 18:41:53 [TV] (TV)INFO - Discovered Activity : Amazon Prime
04/06/2021, 18:41:53 [TV] (TV)INFO - Creating Switch Service Amazon Prime/Amazon Prime
04/06/2021, 18:41:53 [TV] (TV)INFO - Adding Accessory : TV-Sonos
04/06/2021, 18:41:53 [TV] (TV)INFO - Discovered Activity : Sonos
04/06/2021, 18:41:53 [TV] (TV)INFO - Creating Switch Service Sonos/Sonos
04/06/2021, 18:41:53 [TV] (TV)INFO - Adding Accessory : TV-Xbox
04/06/2021, 18:41:53 [TV] (TV)INFO - Discovered Activity : Xbox
04/06/2021, 18:41:53 [TV] (TV)INFO - Creating Switch Service Xbox/Xbox
04/06/2021, 18:41:53 [TV] (TV)INFO - Adding Accessory : TV-Watch TV
04/06/2021, 18:41:53 [TV] (TV)INFO - Discovered Activity : Watch TV
04/06/2021, 18:41:53 [TV] (TV)INFO - Creating Switch Service Watch TV/Watch TV
04/06/2021, 18:41:53 [TV] (TV)INFO - Adding Accessory : TV-Apple TV
04/06/2021, 18:41:53 [TV] (TV)INFO - Discovered Activity : Apple TV
04/06/2021, 18:41:53 [TV] (TV)INFO - Creating Switch Service Apple TV/Apple TV
04/06/2021, 18:41:53 [TV] (TV)INFO - Adding Accessory : TV-Netflix
04/06/2021, 18:41:53 [TV] (TV)INFO - Discovered Activity : Netflix
04/06/2021, 18:41:53 [TV] (TV)INFO - Creating Switch Service Netflix/Netflix
04/06/2021, 18:41:53 [TV] (TV)WARNING - setupFoundAccessories - TV accessory added in your bridge, if another plugin is exposing a TV accessory this one might not be visible in your remote widget
04/06/2021, 18:41:53 [TV] (TV)INFO - Loading sequences...
04/06/2021, 18:41:53 [TV] (TV)INFO - Discovered sequence : Pause2(1615029)
04/06/2021, 18:41:53 [TV] (TV)INFO - Adding Accessory : TV-Pause2(1615029)
04/06/2021, 18:41:53 [TV] (TV)INFO - Creating Switch Service Pause2(1615029)/Pause2(1615029)-Sequence
04/06/2021, 18:41:53 [TV] (TV)INFO - Discovered sequence : Pause3(1615030)
04/06/2021, 18:41:53 [TV] (TV)INFO - Adding Accessory : TV-Pause3(1615030)
04/06/2021, 18:41:53 [TV] (TV)INFO - Creating Switch Service Pause3(1615030)/Pause3(1615030)-Sequence
04/06/2021, 18:41:53 [TV] (TV)INFO - Discovered sequence : Pause4(1615031)
04/06/2021, 18:41:53 [TV] (TV)INFO - Adding Accessory : TV-Pause4(1615031)
04/06/2021, 18:41:53 [TV] (TV)INFO - Creating Switch Service Pause4(1615031)/Pause4(1615031)-Sequence
04/06/2021, 18:41:53 [TV] (TV)INFO - Discovered sequence : Pause1(1615028)
04/06/2021, 18:41:53 [TV] (TV)INFO - Adding Accessory : TV-Pause1(1615028)
04/06/2021, 18:41:53 [TV] (TV)INFO - Creating Switch Service Pause1(1615028)/Pause1(1615028)-Sequence
04/06/2021, 18:41:54 INFO: SmartThings-v2 Hub Communication Established
04/06/2021, 18:41:57 INFO: INFO: Your plugin version is up-to-date
04/06/2021, 18:41:57 NOTICE: Sending Plugin Status to SmartThings | UpdateAvailable: false | newVersion: 2.3.8
04/06/2021, 18:49:55 Got SIGINT, shutting down Bridge...
04/06/2021, 18:49:55 [TV] INFO - shutdown
04/06/2021, 18:49:55 [TV] INFO - shutdown
04/06/2021, 18:50:03 Initializing HAP-NodeJS v0.9.3...
04/06/2021, 18:50:06 [6/4/2021, 11:50:06 AM] The plugin "homebridge-deebot" requires Node.js version of ^14.16.1 which does not satisfy the current Node.js version of v14.16.0. You may need to upgrade your installation of Node.js - see https://git.io/JTKEF
04/06/2021, 18:50:06 Loaded plugin 'homebridge-deebot'
04/06/2021, 18:50:06 [6/4/2021, 11:50:06 AM] Registering platform 'homebridge-deebot.Deebot'
04/06/2021, 18:50:06 Loaded plugin 'homebridge-harmony'
04/06/2021, 18:50:06 [6/4/2021, 11:50:06 AM] Registering platform 'homebridge-harmony.HarmonyHubWebSocket'
04/06/2021, 18:50:08 Loaded plugin 'homebridge-smartthings'
04/06/2021, 18:50:08 [6/4/2021, 11:50:08 AM] Registering platform 'homebridge-smartthings.SmartThings-v2'
04/06/2021, 18:50:08 Loading 3 platforms...
04/06/2021, 18:50:08 [TV] Initializing HarmonyHubWebSocket platform...
04/06/2021, 18:50:08 [TV] HarmonyPlatform Init
04/06/2021, 18:50:08 [Deebot] Initializing Deebot platform...
04/06/2021, 18:50:08 [SmartThings-v2] Initializing SmartThings-v2 platform...
04/06/2021, 18:50:09 INFO: Homebridge Version: 2.7
04/06/2021, 18:50:09 INFO: SmartThings-v2 Plugin Version: 2.3.8
04/06/2021, 18:50:09 INFO: Checking Package Version for Updates...
04/06/2021, 18:50:09 [TV] DidFinishLaunching
04/06/2021, 18:50:09 [TV] WARNING - Removing Accessories
04/06/2021, 18:50:09 [TV] (TV)INFO - Loading activities...
04/06/2021, 18:50:09 [Deebot] [v3.0.3] initialised. Syncing with ECOVACS.
04/06/2021, 18:50:10 INFO: Fetching SmartThings-v2 Devices. NOTICE: This may take a moment if you have a large number of device data is being loaded!
04/06/2021, 18:50:10 GOOD: Refreshing All Device Data | Source: (First Launch)
04/06/2021, 18:50:10 Preparing Advertiser for 'HOOBS A281' using bonjour-hap backend!
04/06/2021, 18:50:10 Starting to advertise 'HOOBS A281' using bonjour-hap backend!
04/06/2021, 18:50:10 Bridge is running on port 51826.
04/06/2021, 18:50:11 NOTICE: Temperature Unit is Now: (C)
04/06/2021, 18:50:11 NOTICE: Updating Global Values | HubIP: <IP_ADDRESS> | UseLocal: false
04/06/2021, 18:50:11 WARN: Devices to Remove: (0) []
04/06/2021, 18:50:11 INFO: Devices to Update: (9)
04/06/2021, 18:50:11 GOOD: Devices to Create: (0) []
04/06/2021, 18:50:11 ALERT: Total Initialization Time: (1 seconds)
04/06/2021, 18:50:11 NOTICE: Unknown Capabilities: []
04/06/2021, 18:50:11 INFO: SmartThings DeviceCache Size: (9)
04/06/2021, 18:50:11 INFO: WebServer Initiated...
04/06/2021, 18:50:11 INFO: Sending StartDirect Request to SmartThings | SendToLocalHub: (false)
04/06/2021, 18:50:11 INFO: Direct Connect Active | Listening at <IP_ADDRESS>:8000
04/06/2021, 18:50:12 INFO: SmartThings-v2 Hub Communication Established
04/06/2021, 18:50:12 [TV] (TV)INFO - Adding Accessory : TV-TV
04/06/2021, 18:50:12 [TV] (TV)INFO - configuring Main TV Service
04/06/2021, 18:50:12 [TV] (TV)INFO - Creating TV Service
04/06/2021, 18:50:12 [TV] (TV)INFO - Creating Input Service - PS5
04/06/2021, 18:50:12 [TV] (TV)INFO - Creating Input Service - YouTube
04/06/2021, 18:50:12 [TV] (TV)INFO - Creating Input Service - Amazon Prime
04/06/2021, 18:50:12 [TV] (TV)INFO - Creating Input Service - Sonos
04/06/2021, 18:50:12 [TV] (TV)INFO - Creating Input Service - Xbox
04/06/2021, 18:50:12 [TV] (TV)INFO - Creating Input Service - Watch TV
04/06/2021, 18:50:12 [TV] (TV)INFO - Creating Input Service - Apple TV
04/06/2021, 18:50:12 [TV] (TV)INFO - Creating Input Service - Netflix
04/06/2021, 18:50:12 [TV] (TV)WARNING - No main Activity that match config file found, default to first one
04/06/2021, 18:50:12 [TV] (TV)INFO - Configuring Main Activity PS5
04/06/2021, 18:50:12 [TV] (TV)INFO - Creating TV Speaker Service
04/06/2021, 18:50:12 [TV] (TV)INFO - Adding Accessory : TV-PS5
04/06/2021, 18:50:12 [TV] (TV)INFO - Discovered Activity : PS5
04/06/2021, 18:50:12 [TV] (TV)INFO - Creating Switch Service PS5/PS5
04/06/2021, 18:50:12 [TV] (TV)INFO - Adding Accessory : TV-YouTube
04/06/2021, 18:50:12 [TV] (TV)INFO - Discovered Activity : YouTube
04/06/2021, 18:50:12 [TV] (TV)INFO - Creating Switch Service YouTube/YouTube
04/06/2021, 18:50:12 [TV] (TV)INFO - Adding Accessory : TV-Amazon Prime
04/06/2021, 18:50:12 [TV] (TV)INFO - Discovered Activity : Amazon Prime
04/06/2021, 18:50:12 [TV] (TV)INFO - Creating Switch Service Amazon Prime/Amazon Prime
04/06/2021, 18:50:12 [TV] (TV)INFO - Adding Accessory : TV-Sonos
04/06/2021, 18:50:12 [TV] (TV)INFO - Discovered Activity : Sonos
04/06/2021, 18:50:12 [TV] (TV)INFO - Creating Switch Service Sonos/Sonos
04/06/2021, 18:50:12 [TV] (TV)INFO - Adding Accessory : TV-Xbox
04/06/2021, 18:50:12 [TV] (TV)INFO - Discovered Activity : Xbox
04/06/2021, 18:50:12 [TV] (TV)INFO - Creating Switch Service Xbox/Xbox
04/06/2021, 18:50:12 [TV] (TV)INFO - Adding Accessory : TV-Watch TV
04/06/2021, 18:50:12 [TV] (TV)INFO - Discovered Activity : Watch TV
04/06/2021, 18:50:12 [TV] (TV)INFO - Creating Switch Service Watch TV/Watch TV
04/06/2021, 18:50:12 [TV] (TV)INFO - Adding Accessory : TV-Apple TV
04/06/2021, 18:50:12 [TV] (TV)INFO - Discovered Activity : Apple TV
04/06/2021, 18:50:12 [TV] (TV)INFO - Creating Switch Service Apple TV/Apple TV
04/06/2021, 18:50:12 [TV] (TV)INFO - Adding Accessory : TV-Netflix
04/06/2021, 18:50:12 [TV] (TV)INFO - Discovered Activity : Netflix
04/06/2021, 18:50:12 [TV] (TV)INFO - Creating Switch Service Netflix/Netflix
04/06/2021, 18:50:12 [TV] (TV)WARNING - setupFoundAccessories - TV accessory added in your bridge, if another plugin is exposing a TV accessory this one might not be visible in your remote widget
04/06/2021, 18:50:12 [TV] (TV)INFO - Loading sequences...
04/06/2021, 18:50:12 [TV] (TV)INFO - Discovered sequence : Pause2(1615029)
04/06/2021, 18:50:12 [TV] (TV)INFO - Adding Accessory : TV-Pause2(1615029)
04/06/2021, 18:50:12 [TV] (TV)INFO - Creating Switch Service Pause2(1615029)/Pause2(1615029)-Sequence
04/06/2021, 18:50:12 [TV] (TV)INFO - Discovered sequence : Pause3(1615030)
04/06/2021, 18:50:12 [TV] (TV)INFO - Adding Accessory : TV-Pause3(1615030)
04/06/2021, 18:50:12 [TV] (TV)INFO - Creating Switch Service Pause3(1615030)/Pause3(1615030)-Sequence
04/06/2021, 18:50:12 [TV] (TV)INFO - Discovered sequence : Pause4(1615031)
04/06/2021, 18:50:12 [TV] (TV)INFO - Adding Accessory : TV-Pause4(1615031)
04/06/2021, 18:50:12 [TV] (TV)INFO - Creating Switch Service Pause4(1615031)/Pause4(1615031)-Sequence
04/06/2021, 18:50:12 [TV] (TV)INFO - Discovered sequence : Pause1(1615028)
04/06/2021, 18:50:12 [TV] (TV)INFO - Adding Accessory : TV-Pause1(1615028)
04/06/2021, 18:50:12 [TV] (TV)INFO - Creating Switch Service Pause1(1615028)/Pause1(1615028)-Sequence
04/06/2021, 18:50:15 [Deebot] [Dave] has been added to Homebridge.
04/06/2021, 18:50:15 [Deebot] [Dave] initialising with options: {"hideMotionSensor":false,"motionDuration":30,"lowBattThreshold":15,"showMotionLowBatt":false,"showBattHumidity":false}.
04/06/2021, 18:50:15 [Deebot] [Dave] additional info: {"did":"E2001229192017052169","name":"E2001229192017052169","class":"155","resource":"atom","nick":"Dave","company":"eco-legacy"}.
04/06/2021, 18:50:15 [Deebot] [Dave] initialised with id E2001229192017052169.
04/06/2021, 18:50:15 [Deebot] ✓ Setup complete. Want to see this plugin in your own language? Let me know!
04/06/2021, 18:50:16 INFO: INFO: Your plugin version is up-to-date
04/06/2021, 18:50:16 NOTICE: Sending Plugin Status to SmartThings | UpdateAvailable: false | newVersion: 2.3.8
04/06/2021, 18:50:17 [Deebot] [Dave] current battery [100%].
04/06/2021, 18:50:17 [Deebot] [Dave] current charging state [charging].
04/06/2021, 18:50:17 [Deebot] [Dave] current cleaning state [stop].
04/06/2021, 18:52:16 TypeError: Cannot read property 'replace' of undefined
at Object.getEventNameForCommandString (/home/hoobs/.hoobs/node_modules/ecovacs-deebot/library/tools.js:111:23)
at EcovacsXMPP.handleCommand (/home/hoobs/.hoobs/node_modules/ecovacs-deebot/library/ecovacs.js:71:23)
at EventEmitter. (/home/hoobs/.hoobs/node_modules/ecovacs-deebot/library/ecovacsXMPP.js:42:26)
at EventEmitter.emit (events.js:315:20)
at Client. (/home/hoobs/.hoobs/node_modules/simple-xmpp/lib/simple-xmpp.js:322:20)
at Client.emit (events.js:315:20)
at Client._handleStanza (/home/hoobs/.hoobs/node_modules/node-xmpp-client/lib/Client.js:227:12)
at Client.onStanza (/home/hoobs/.hoobs/node_modules/node-xmpp-client/lib/Client.js:221:8)
at Connection.emit (events.js:315:20)
at Connection.onStanza (/home/hoobs/.hoobs/node_modules/node-xmpp-core/lib/Connection.js:377:10)
at StreamParser. (/home/hoobs/.hoobs/node_modules/node-xmpp-core/lib/Connection.js:231:10)
at StreamParser.emit (events.js:315:20)
at SaxLtx. (/home/hoobs/.hoobs/node_modules/@xmpp/streamparser/index.js:69:14)
at SaxLtx.emit (events.js:315:20)
at SaxLtx._handleTagOpening (/home/hoobs/.hoobs/node_modules/ltx/lib/parsers/ltx.js:40:12)
at SaxLtx.write (/home/hoobs/.hoobs/node_modules/ltx/lib/parsers/ltx.js:159:18)
04/06/2021, 18:52:16 ERROR: uncaughtException: Cannot read property 'replace' of undefined
04/06/2021, 18:52:16 TypeError: Cannot read property 'replace' of undefined
04/06/2021, 18:52:16 at Object.getEventNameForCommandString (/home/hoobs/.hoobs/node_modules/ecovacs-deebot/library/tools.js:111:23)
04/06/2021, 18:52:16 at EcovacsXMPP.handleCommand (/home/hoobs/.hoobs/node_modules/ecovacs-deebot/library/ecovacs.js:71:23)
04/06/2021, 18:52:16 at EventEmitter. (/home/hoobs/.hoobs/node_modules/ecovacs-deebot/library/ecovacsXMPP.js:42:26)
04/06/2021, 18:52:16 at EventEmitter.emit (events.js:315:20)
04/06/2021, 18:52:16 at Client. (/home/hoobs/.hoobs/node_modules/simple-xmpp/lib/simple-xmpp.js:322:20)
04/06/2021, 18:52:16 at Client.emit (events.js:315:20)
04/06/2021, 18:52:16 at Client._handleStanza (/home/hoobs/.hoobs/node_modules/node-xmpp-client/lib/Client.js:227:12)
04/06/2021, 18:52:16 at Client.onStanza (/home/hoobs/.hoobs/node_modules/node-xmpp-client/lib/Client.js:221:8)
04/06/2021, 18:52:16 at Connection.emit (events.js:315:20)
04/06/2021, 18:52:16 at Connection.onStanza (/home/hoobs/.hoobs/node_modules/node-xmpp-core/lib/Connection.js:377:10)
04/06/2021, 18:52:16 at StreamParser. (/home/hoobs/.hoobs/node_modules/node-xmpp-core/lib/Connection.js:231:10)
04/06/2021, 18:52:16 at StreamParser.emit (events.js:315:20)
04/06/2021, 18:52:16 at SaxLtx. (/home/hoobs/.hoobs/node_modules/@xmpp/streamparser/index.js:69:14)
04/06/2021, 18:52:16 at SaxLtx.emit (events.js:315:20)
04/06/2021, 18:52:16 at SaxLtx._handleTagOpening (/home/hoobs/.hoobs/node_modules/ltx/lib/parsers/ltx.js:40:12)
04/06/2021, 18:52:16 at SaxLtx.write (/home/hoobs/.hoobs/node_modules/ltx/lib/parsers/ltx.js:159:18)
04/06/2021, 18:52:16 Got SIGTERM, shutting down Bridge...
04/06/2021, 18:52:16 [TV] INFO - shutdown
04/06/2021, 18:52:16 [TV] INFO - shutdown
04/06/2021, 18:52:16 TypeError: Cannot read property 'replace' of undefined
at Object.getEventNameForCommandString (/home/hoobs/.hoobs/node_modules/ecovacs-deebot/library/tools.js:111:23)
at EcovacsXMPP.handleCommand (/home/hoobs/.hoobs/node_modules/ecovacs-deebot/library/ecovacs.js:71:23)
at EventEmitter. (/home/hoobs/.hoobs/node_modules/ecovacs-deebot/library/ecovacsXMPP.js:42:26)
at EventEmitter.emit (events.js:315:20)
at Client. (/home/hoobs/.hoobs/node_modules/simple-xmpp/lib/simple-xmpp.js:322:20)
at Client.emit (events.js:315:20)
at Client._handleStanza (/home/hoobs/.hoobs/node_modules/node-xmpp-client/lib/Client.js:227:12)
at Client.onStanza (/home/hoobs/.hoobs/node_modules/node-xmpp-client/lib/Client.js:221:8)
at Connection.emit (events.js:315:20)
at Connection.onStanza (/home/hoobs/.hoobs/node_modules/node-xmpp-core/lib/Connection.js:377:10)
at StreamParser. (/home/hoobs/.hoobs/node_modules/node-xmpp-core/lib/Connection.js:231:10)
at StreamParser.emit (events.js:315:20)
at SaxLtx. (/home/hoobs/.hoobs/node_modules/@xmpp/streamparser/index.js:69:14)
at SaxLtx.emit (events.js:315:20)
at SaxLtx._handleTagOpening (/home/hoobs/.hoobs/node_modules/ltx/lib/parsers/ltx.js:40:12)
at SaxLtx.write (/home/hoobs/.hoobs/node_modules/ltx/lib/parsers/ltx.js:159:18)
04/06/2021, 18:52:16 ERROR: uncaughtException: Cannot read property 'replace' of undefined
04/06/2021, 18:52:16 TypeError: Cannot read property 'replace' of undefined
04/06/2021, 18:52:16 at Object.getEventNameForCommandString (/home/hoobs/.hoobs/node_modules/ecovacs-deebot/library/tools.js:111:23)
04/06/2021, 18:52:16 at EcovacsXMPP.handleCommand (/home/hoobs/.hoobs/node_modules/ecovacs-deebot/library/ecovacs.js:71:23)
04/06/2021, 18:52:16 at EventEmitter. (/home/hoobs/.hoobs/node_modules/ecovacs-deebot/library/ecovacsXMPP.js:42:26)
04/06/2021, 18:52:16 at EventEmitter.emit (events.js:315:20)
04/06/2021, 18:52:16 at Client. (/home/hoobs/.hoobs/node_modules/simple-xmpp/lib/simple-xmpp.js:322:20)
04/06/2021, 18:52:16 at Client.emit (events.js:315:20)
04/06/2021, 18:52:16 at Client._handleStanza (/home/hoobs/.hoobs/node_modules/node-xmpp-client/lib/Client.js:227:12)
04/06/2021, 18:52:16 at Client.onStanza (/home/hoobs/.hoobs/node_modules/node-xmpp-client/lib/Client.js:221:8)
04/06/2021, 18:52:16 at Connection.emit (events.js:315:20)
04/06/2021, 18:52:16 at Connection.onStanza (/home/hoobs/.hoobs/node_modules/node-xmpp-core/lib/Connection.js:377:10)
04/06/2021, 18:52:16 at StreamParser. (/home/hoobs/.hoobs/node_modules/node-xmpp-core/lib/Connection.js:231:10)
04/06/2021, 18:52:16 at StreamParser.emit (events.js:315:20)
04/06/2021, 18:52:16 at SaxLtx. (/home/hoobs/.hoobs/node_modules/@xmpp/streamparser/index.js:69:14)
04/06/2021, 18:52:16 at SaxLtx.emit (events.js:315:20)
04/06/2021, 18:52:16 at SaxLtx._handleTagOpening (/home/hoobs/.hoobs/node_modules/ltx/lib/parsers/ltx.js:40:12)
04/06/2021, 18:52:16 at SaxLtx.write (/home/hoobs/.hoobs/node_modules/ltx/lib/parsers/ltx.js:159:18)

@GMarty93
You've installed v3.0.3 (not v3.1.1-beta.4), right?

Oops yeah sorry just reloaded I installed it in the wrong directory have just reinstalled to the right location and fingers crossed it appears to be working for now. I’ll update if it crashes again

So everything still seems to be working, I have full control via the home app and have had no further crashes.

great. i think the rate it was crashing before... if it was going to again it would have done so by now.
stay on the beta version of the plugin for now, and when a proper release is available the hoobs ui will let you know.


e.trees is not iterable[Validate odsp snapshot in trees latest]

Describe the bug
Validate the snapshot returned by odsp for contents like presence of trees/blobs etc.
Refer to this ICM incident: https://portal.microsofticm.com/imp/v3/incidents/details/234849739/home
The snapshot expected is:
export interface IOdspSnapshot {
id: string;
trees: IOdspSnapshotCommit[];
blobs?: IOdspSnapshotBlob[];
ops?: ISequencedDeltaOpMessage[];
}
But we are seeing that in some rare case, we are seeing no trees. So validate and throw proper error.

Before we add any validation, I'm curious to better understand

when it happens
what does it mean
how client handles it today (i.e. actual behavior we are about to change).

As per the investigation by FFX folks, it seems that they had a code path where they allowed creating an empty file and then load that. So in that way we get this error where the snapshot is without any trees. They are removing such code path at their end, so we just need to add validation of snapshot and throw a proper error.


DBus is broken on Xfce

Issue description
When starting Xfce after an update, I get this:
$ echo $DBUS_SESSION_BUS_ADDRESS
unix:abstract=/tmp/dbus-yvEWqzlS5z,guid=ce9642d21b094b432feae6cf5809f6bb;unix:abstract=/tmp/dbus-SZQEK1FwoS,guid=2276c0f34b70c1db887a93125809f6bb
$ ls /tmp/dbus-yvEWqzlS5z
ls: cannot access '/tmp/dbus-yvEWqzlS5z': No such file or directory

All applications that require DBus fail to start (e.g. taffybar).
Steps to reproduce

Start Xfce session;
Run anything dbus-dependent;
Observe an error.

Technical details

System: (NixOS: nixos-version, Ubuntu/Fedora: lsb_release -a, ...) 09e4b78b48fa9b5da00f44d2c01f0f9f16c3d406 (with unrelated patches on top)

Funny things happen when I try to use dbus-launch by myself.
Let's create a new DBus session daemon:
$ dbus-launch
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-GGeRMqFbPf,guid=d0021bc574263ed05cffbe485809fafd;unix:abstract=/tmp/dbus-cyeuTtqrgQ,guid=9c245041979c97f9d9e9e17b5809fafd
DBUS_SESSION_BUS_PID=9425

Okay, is the daemon running?
$ ps -A | grep 9425
 9425 ?        00:00:00 dbus-daemon

Good, does it listen for something?
$ lsof -p 9425
COMMAND    PID   USER   FD      TYPE             DEVICE SIZE/OFF      NODE NAME
...
dbus-daem 9425 abbradar    4u     unix 0x0000000000000000      0t0     61584 @/tmp/dbus-cyeuTtqrgQ type=STREAM
dbus-daem 9425 abbradar    5r  a_inode               0,11        0      7359 inotify
dbus-daem 9425 abbradar    6u     unix 0x0000000000000000      0t0     61585 @/tmp/dbus-GGeRMqFbPf type=STREAM
dbus-daem 9425 abbradar    7u     unix 0x0000000000000000      0t0     55916 type=STREAM
dbus-daem 9425 abbradar    8u     unix 0x0000000000000000      0t0     55917 type=STREAM

Oh, nice, it actually does listen on the socket that it advertised. Let's check this out!
$ ls /tmp/dbus-GGeRMqFbPf
ls: cannot access '/tmp/dbus-GGeRMqFbPf': No such file or directory

...now what? But wait, there's more! There is another socket, at least it should be!...
$ ls /tmp/dbus-cyeuTtqrgQ
ls: cannot access '/tmp/dbus-cyeuTtqrgQ': No such file or directory

...uh-oh. At this point my faith in everything is shattered.
I did a rollback for now. Any ideas what might this be? I'm not sure what to try next.

O.o interesting. I suspected the upgrade (https://github.com/NixOS/nixpkgs/pull/19682) but this is much later.

Well, I did jump from a (pretty old) previous channel -- adfcc2d9531e78bf6a9e3b56e2f4fc873cb3d87b, so there might be many things involved. Maybe I'll do a bisect if I come up with a clever automated test for this.

Note that AFAIK @/tmp/dbus-cyeuTtqrgQ and /tmp/dbus-cyeuTtqrgQ are different - the @ one works in an abstract namespace, it doesn't exist in the file system.
(Probably this trivia doesn't help solving the problem though ;))

Actually it does help -- I didn't know what @ signifies. Also it probably means that it's dbus that is doing something shady -- it's not like something forces it to create an abstract namespace I presume.

From http://unix.stackexchange.com/questions/206386/what-does-an-symbol-denotes-in-the-beginning-of-a-unix-domain-socket-path-in-l it seems that it's known DBus behaviour, and indeed, I observe the same thing on my current generation (which works). So my analysis above is incorrect.

From http://unix.stackexchange.com/questions/206386/what-does-an-symbol-denotes-in-the-beginning-of-a-unix-domain-socket-path-in-l it seems that it's known DBus behaviour, and indeed, I observe the same thing on my current generation (which works). So my analysis above is incorrect.

Hm, perhaps I was wrong in assessing this -- can someone suggest a good DBus test, and also DBus-dependent applications? I feel that only taffybar doesn't work.

It's just taffybar (haskell-dbus) which can't handle semicolons in DBUS_SESSION_BUS_ADDRESS. I posted a possible workaround to the mailing list.

Yes, it seems my cause seeking was inadequate. Thank you for the pointer!


fix dep

github.com/devopsfaith/krakend has migrated to github.com/luraproject/lura.
close #1

@x1ah nice! merged


[python3] Fix building x86-windows-static triplet on VS 2017.

This fixes building python3 with the x86-windows-static triplet on Visual Studio 2017, which was unintentionally broken in #11708.

Thanks for the fix!


Change request from Fee Estimate to On Hold

As an IAO analsyst
I want to change a request with an approved CFR form to On Hold
so that I can notify the applicant of the assessed fee

Assumptions & Scope
What are the assumptions for this story?
An request can only be put On Hold if the CFR Form has been approved.
An applicant without an email address will be notified of the fee payment following the current process in AXIS.
An applicant with an email address on file will be notified of the fee payment through the new applicaiton. They will be able to pay the fee online via PayBC.
What is IN scope?
Changing a request to the On Hold state. Includes exception handling if the form is not approved.
What is NOT in scope?
The applicant notification and fee payment will be covered in other stories.
Approving the CFR Form is covered in #2268
Stopping the clock - that is already in place.
Acceptance Criteria
Scenario 1: Form is not Approved

GIVEN the CFR Form has not be approved
WHEN the IAO analyst clicks On Hold in the state dropdown
THEN a modal will open with the message: "You must review and approve the CFR Form before you can put this request On Hold."
AND there will be only a close button in the modal.

Scenario 2: Form is Approved but there is no applicant email on file

GIVEN the CFR Form is approved
AND there is no applicant email on file
WHEN the IAO analyst clicks On Hold in the state dropdown
THEN a modal will open with the message: "There is no applicant email on file. Please check the box to confirm that you have sent the applicant a letter in AXIS before you put this request On Hold."
AND there will be an empty checkbox
AND as is now there will be the IAO and ministry assignees
AND there will be a 'Save Change' and 'Cancel' button
AND the 'Save Change' button will be disabled

Scenario 3: Click Checkbox when there is no applicant email on file

GIVEN the CFR Form is approved
AND there is no applicant email on file
AND the analyst is on the  IAO analyst modal with the message: "There is no applicant email on file. Please check the box to confirm that you have sent the applicant a letter in AXIS before you put this request On Hold."
WHEN  the analyst clicks the checkbox
THEN the checkbox will turn green with a white checkmark
AND  the 'Save Change' button will turn blue and be active

Scenario 4: Form is Approved and there is an applicant email on file

GIVEN the CFR Form is approved
AND there is an applicant email in file
WHEN the IAO analyst clicks On Hold in the state dropdown
THEN a modal will open with the message: "Are you sure you want to change Request #MIN-YEAR-12345 to On Hold?
This will stop the clock and automatically email the applicant the fee estimate "
AND as is now there will be the IAO and ministry assignees
AND there will be a 'Save Change' and 'Cancel' button
AND the 'Save Change' button will be be blue and active

**Scenario 5: Save On Hold **

GIVEN the analyst is on the On Hold modal
AND the 'Save Change' button is blue and be active
WHEN the analyst clicks the 'Save Change' button
THEN the request state will be update to 'On Hold'
AND the modal will close
AND the clock will stop

Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)
Validation Rules? (If yes, list here)
Design
@xxx - please link the Design here
Definition of Ready

[ ] Is there a well articulated User Story?
[ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
[ ] If there is a user interface, is there a design?
[ ] Does the user story need user research/validation?
[ ] Does this User Story needs stakeholder approval?
[ ] Design / Solution accepted by Product Owner
[ ] Is this user story small enough to be completed in a Sprint? Should it be split?
[ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
[ ] Has the story been estimated?

Definition of Done

[ ] Passes developer unit tests
[ ] Passes peer code review
[ ] If there's a user interface, passes UX assurance
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Confirm Test cases built and succeeding
[ ] No regression test failures
[ ] Test coverage acceptable by Product Owner
[ ] Ticket ready to be merged to master or story branch
[ ] Developer to list Config changes/ Update documents and designs
[ ] Can be demoed in Sprint Review
[ ] Tagged as part of a Release
[ ] Feature flagged if required
[ ] Change Management activities done?

Looks good to me Loren! Sorry for the delay in reviewing, had to help some users troubleshoot issues.

We will need a design for this story as well, @JHarrietha-AOT

Design Links added to stories above: @lmullane

Will rewrite AC to reflect decision to have letter drafted in AXIS and uploaded into Flow when putting the request On Hold.

@abin-aot, @JHarrietha-AOT, @m-prodan, updated the AC with the letter upload. Will need to review the adjusted AC to see if the estimate changes.
Using the same approach as we do for other required uploads for state change, except that it must be a PDF (no Word docs).

Will go into TEST marshal.

I like that idea - it's not immediately clear how long its been on hold, so that would be a nice way to show it.

@m-prodan @JHarrietha-AOT @nkan-aot   A/C's function as they should. Great work!


Major impact of using ValueExprEvaluationException for flow control

One of the design decisions in Sesame and later RDF4J is using exceptions for flow control in some cases. Probably the most notable example is ValueExprEvaluationException thrown when a value is incompatible in a certain expression. Using exceptions for flow control is OK per se but throwing exception in general is very expensive because the stack trace needs to be collected. I have observed some simple queries (for example using LANG(?x) where ?x is bound to an IRI or ORDER BY ?x where there is no binding for ?x) throwing ~44 million ValueExprEvaluationException instances. On the test machine the query completed in about 4,5 minutes. There is a way to disable stack trace collection for a given exception so I tried that with ValueExprEvaluationException and the same query completed in about a minute.
I propose a simple fix (PR coming) that disables stack trace collection for ValueExprEvaluationException. This will allow us to keep using the exception for flow control as it is now but not pay the stack trace collection penalty.

Good find, thanks.
If we could do things over I would have chosen to introduce a "type error" return type for all value operators, instead of using exceptions - but it's probably not worth the effort and pain to make that change now.
So disabling stack trace collection seems a decent compromise.


Multiple instances will unpublish each others subscriptions

Version: v0.49.0
Problem
We have multiple serverless stacks running inside a docker container. Also there's a localstack instance within the same docker-compose environment. Each sls stack has the following configuration:
serverless-offline-sns:
  debug: true
  port: 4002
  host: <IP_ADDRESS>
  sns-subscribe-endpoint: backend-${self:custom.stack}
  sns-endpoint: http://localstack:4575

The problem with this set up is that when booting up each serverless-offline-sns instance (inside each stack) will unpublish each other's subscriptions, based on the startup order of the containers.
Possible solution
Unpublishing is done based on port, but the sns-subscribe-endpoint is not taken into account. A possible solution would be to add this to the .filter statement in unsubscribeAll method of index.ts.
Locally I have fixed it by letting each stack listen on a different port. But thought I'd propose my findings here.

Thanks for the bug report, happy to accept a pull request on this with the .filter added.

Maybe this is related: https://github.com/mj1618/serverless-offline-sns/issues/99
The problem is that when a sls offline start service A, B and C, and latter i kill B, service A will fail to publish to C because B was not unsubscribed when killed...

Thank you I have merged chichicuervo's fix


Version change exceptions

Version
4.9.1
Describe the bug
There have been multiple reports from customers using the latest 4.9.1 SDK whereby they are reporting sudden Version Change exceptions being surfaced which haven't been seen before.
From conversations with SDK there is new (undocumented) behaviour whereby an event is fired if the SDK detects a conversation is resuming when a Dialog may have changed. If this event is not handled an exception is raised to trigger state being cleared out. If the user handles the event they can make a call on whether to ignore, re-constitute state, etc.
I agree with the overall direction – we’ve had instances in the past for persistent channels like Teams having users that are stuck and having to have a “/reset” type command to clear out state. However I think this new behaviour change should be opt-in not enforced due to the side affects it's causing.
To Reproduce
Two causes have been identified so far:

Customer deploys a Bot, users start conversations to these bots through a persistent channel (e.g. Teams). The Bot is then later updated (new dialogs added, dialogs changed, etc.). When a user resumes the conversation a version Change exception is surfaced.

Customer starts a conversation, dialogs are added statically at the beginning of a dialog but due to multi-locale scenarios another dialog might be registered dynamically. This then triggers the same version change exception.

Expected behavior
Behaviour change does not impact existing bots especially those with persistent/long-running conversations or those using dynamic dialog registration scenarios
Suggestion

Make this behaviour opt-in so existing customers don’t run into it
Ensure all Samples and Templates have a default implementation (currently none do)
Update documentation with guidance about this behaviour

Other information
With VA (due to multi-locale requirements and issues with Conversation Update not setting locale property) we have to dynamically add QnAMaker dialog when needed and this triggers the problem easily.

Deploy a Virtual Assistant Sample in TypeScript
Run the Virtual Assistant Sample on Bot Emulator
Complete the Onboarding Dialog
Send 'What's a Virtual Assistant?' (Adds QnAMaker dialog to the stack)
Wait for reply and send 'What's a Virtual Assistant?' again
The bot should show an exception with the message 'Version change detected for MainDialog dialog'

[bug]

Fixed as part of 4.9.3


Create vassboskovice.txt

Main domain of our school is vassboskovice.cz, but all email adresses are on @vassboskovice.eu. All students have @stud.vassboskovice.eu (is already registred) and teachers have @vassboskovice.eu. Here is confirmation https://www.dropbox.com/s/n1biyv5tm7tk0n8/Confirmation.pdf?dl=0

thank you @danielvitek - i'm adding the domain!

Thank you @zweizwei!


Issue with k8s.io/docs/tasks/configure-pod-container/configure-gmsa/

Following each step on the doc, when creating a pod with the gmsa account I get an error:
deployment.yaml": error validating data: ValidationError(Deployment.spec.template.spec.securityContext): unknown field "windowsOptions" in io.k8s.api.core.v1.PodSecurityContext; if you choose to ignore these errors, turn validation off with --validate=false

Problem:
Cant deploy pod with gmsa account in the deployment
Page to Update:
https://kubernetes.io/...

v1.14.6

deployment.yaml
apiVersion: apps/v1beta1
kind: Deployment
metadata:
labels:
app: webapp
name: webapp
spec:
replicas: 1
template:
metadata:
labels:
app: webapp
spec:
securityContext:
windowsOptions:
gmsaCredentialSpecName: gmsa-web
containers:
- name: simba-platformworker
image: somerepo.azurecr.io/someimage
ports:
- containerPort: 80
dnsPolicy: "ClusterFirst"
nodeSelector:
beta.kubernetes.io/os: windows

Hi @jjburr . Sorry you're getting an error. This issue sounds first like a request for support, and then maybe a documetation issue. I encourage you to ask
your question to the #kubernetes-users channel in
Kubernetes slack. You can also search
resources like
Stack Overflow
for answers to similar questions.
You can  open issues for Kubernetes functionality in
https://github.com/kubernetes/kubernetes.
If you discover that the Configure GMSA for Windows pods and containers page needs to be updated, please edit this Issue to explain exactly what needs to change.
Thanks!
/triage support

Thanks will close this out and ask in slack


add auth support to marathon namer

modify marathon namer to read credentials from an environment variable,
and, if found, authenticate against a login endpoint
fixes #743

I took a stab for my own understanding.  Here's what I came up with: https://gist.github.com/olix0r/2585d60de53533249dc2baff4504720c
The main goal was to make the state stuff (what the activity does in this review) more explicit:
The authenticator has 3 states, Init, Authenticating(token: Future[String]), and Closed.  The authenticator is in the Init state before it has processed any requests.  As soon as it tries to process the request, it tries to update the state to Authenticating with a future that will be satisfied with the token once it's authenticated.  If another thread races this and starts getting a token before we update the state, we start over again (probably off of the other thread's authentication result).
I think this accomplishes roughly the same thing as your review but is easier (for me) to think about. Happy to chat more about this.

needs updates to CHANGES, and probably to marathon docs?


295 scmrun v2

Pull request
Please confirm that this pull request has done the following:

[x] Tests added
[x] Documentation added (where applicable)
[x] Example added (either to an existing notebook or as a new notebook, where applicable)
[x] Description in CHANGELOG.rst added

Closes #295
Replaces #296

@lewisjared I merged #308, feel free to merge/undo depending on success with https://github.com/openscm/scmdata/pull/91


Huawei Example Configs - Update v0.2

Description
Added examples of the card yaml that can be used by Huawei / iStore users, allowing copy and paste to configure the card, with limited editing required (i.e. just tweak solar --> max_power:  to reflect your actual setup. Also example AUX / Non-Essential devices and groups created.
Just needing to add in some example yaml files that use the energy_meter integration to automatically create the Energy Meters (i.e. utility meters, but with sensors for costs, pulled from tariff plans in the yaml) that the card then uses for the Imported from Grid / Exported to Grid / AUX and Non-Essential Daily kWh used display,

Related issues

Motivation and Context

Add support for users of Huawei (and iStore in Australia) inverters and LUNA batteries
How has this been tested

Testing with a 2 x M1 6kW 3 phase inverter site (no battery) and 2 x L1 5kW 1 phase inverter with 1 x 15kWh LUNA battery site.

Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] Any dependent changes have been merged and published in downstream modules
[x] I have updated the version in package.json following semver

Can you remove the README

@slipx06 Oops. Edited after submitting but seems github keeps adding them to the request. Any idea how to fix, instead of a 'don't pull' option on the file, as best as I can work out I need to revert the README.md back to how it was, which I have done (copied current contents of yours back in),
Looking at the Pull and it now shows only 5 files that have changed, with README.md not being one of them.
Would you have any idea of how I can edit the readme.md file and keep it seperate from yours / not have it merge when I submit a pull request?

You would need more than one branch in your repository. Once branch for the pull request and another that you are using for development and the custom README.

Is this OL to merge now? Following this I'll create the branch(es) on my side.

No thank you ! Hopefully this makes it easy with 80-90% of the work done for Huawei / iStore inverter users to rapidly get started.
Now we just need that 'wide' card option to allow showing multiple batteries and inverters ;-) LoL.
Will update with electricity / tariff plans as people ask how they can support their setup.
Just noticed the banner updated with the & LUNA Batteries, might be to remove that to follow the format of other inverters names in the Examples Doco.


feat: Add link for card

Requirements for a pull request
Fill out the template below. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.

[ ] Unit tests related to the change have been updated
[ ] Documentation related to the change has been updated

Description of the Change
Added a link to the top of the card display for easy access to the card URL for sharing.

Alternate Designs
-
Possible Drawbacks
-
Verification Process
Navigate to a task with a card. See the link button. Click on the link button to open the card in its own tab.
Release Notes

I tend to see the link symbol copy the URL to the clipboard, while there's a box with an arrow that more often indicates that something will open in a new window/tab.

Would you prefer a button to copy the link? Or a link itself?

On Jan 3, 2023, at 10:47 AM, James Budarz @.***> wrote:

I tend to see the link symbol copy the URL to the clipboard, while there's a box with an arrow that more often indicates that something will open in a new window/tab.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.

Would you prefer a button to copy the link? Or a link itself?

Either one would be useful, but what you've done here is even better than what I originally suggested.
My original desire was to have a link that would let users share the URL of a card with their team, so just a link to part of the page... Having an "open in new tab" button might be even better, to be honest- I would just change the icon.

Updated


Enable extension according to file type

Issue Type: Feature Request
In order to make my VSCode more lightweight, I disable extensions related to some programming languages (like Python, Pascal, Clojure extensions).
I did this because, some times, I use VSCode to write SQL scripts, making notes and other stuff not related to these programming languages. But if I need to open a file of these languages (not in a workspace) I've to manually enable the extensions.
Would be great if we could set, in settings.json, which extensions we want to enable per language, like:
"[python]": {
    "files.insertFinalNewline": true,
    "files.encoding": "utf8",
    "Extensions.Enabled": [ms-python.python, donjayamanne.python-extension-pack, ms-python.anaconda-extension-pack]
        }
VS Code version: Code - Insiders 1.41.0-insider (fdeb9aa9b8306a2d3da989ccb9d2ad288d0ae347, 2019-11-08T05:28:30.394Z)
OS version: Windows_NT x64 10.0.18362

@RicaBenhossi VS Code extensions are usually behaving in the way in which you describe. Simply having an extension installed and enabled does not mean it is executing any code. Extensions in VS Code activate on activation events and one such event is onLanguage:X. Most extensions respect this and do not activate on * (startup). You can check this by running F1 > Show running extensions.


Add steps for deploying an existing node.js app to OpenShift. Fixes R…

…HOARDOC-1190

@lholmquist @Ladicek let me know what you think.

👍

Otherwise LGTM.

thanks for the feedback @Ladicek
fixed.


Middleware -  doc and code sample improvements

@cloudmelon can you please provide more context on the work required?


Feature/save project

Depends on #10

When transcription is complete, goes to bare bones project page
Save button in corner
Clicking save opens save dialog and then writes currentProject state from store into file

Added more changes to this:

Support opening project files
Add file submenu - save and open with keyboard shortcuts
Refactor IPC so that main can send messages to renderer as well as vice versa
Pull out react-router; we don't need it since we don't have URLs. Instead use an enum on the redux store root, which is updatable outside the react context. Design doc: https://docs.google.com/document/d/10ACSzFhQGU8RoE0LwWMAwbr2v7NUSyj2SPeXwrzb-a0/edit


[ENH] Use executor in segment.py

Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

...

New functionality

...

Test plan
How are these changes tested?

[ ] Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

#2951  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Sicheng-Pan and the rest of your teammates on  Graphite


Gradle 6.3

Gradle 6.3 is available.
This is sent by @gradleupdate. See https://gradleupdate.appspot.com/Knotx/knotx-gradle-plugins/status for more.

Verified on Windows.


Fix g:clap_layout is not applied in v0.49

I fixed extending layout with g:clap_layout.

Thank you!


[Task]: Add support for loading multiple snippets via query string for Playground

What needs to happen?
Current state:

Currently Embedded Playground can load only 1 code snippet for 1 SDK.

Requirements:

After embedding Playground to Apache Beam web-site, we need to load an example for each SDK. When user switches between SDKs, Playground reads the examples from its state and presents the code (instead of reloading the example for switched SDK).

This task depends on state preservation feature:

#22430

Issue Priority
Priority: 3
Issue Component
Component: beam-playground

.take-issue

Made in #22735


Fixed redundant and messy and not working code

Fixed cave mode.
Problem was:
If not than this
and else the same

Not really working
Merge #14


Is there any way to get estimated time to completion?

Hi, I was wondering if we can get the real time output of the remaining time to completion in ffmpeg-python?
For example, this is the code.
import ffmpeg
video_part = ffmpeg.input(<<VIDEO_PATH>>)
audio_part = ffmpeg.input(<<AUDIO_PATH>>)
ffmpeg.output(audio_part, video_part, <<OUTPUT_PATH>>).overwrite_output().run_async(pipe_stdout=True)

And I want something like this:
ETA: 2:36
Is it possible? Sorry if it's duplicate.

Did you notice a number like 'speed=5x' at the end of the line when using ffmpeg? This indicates the processing speed in real-time while playing the video. For example, if your video is 10 minutes long, it will take approximately 2 minutes to process at 5x speed
frame= 4849 fps=293 q=28.0 size=     512kB time=00:03:11.84 bitrate=  21.9kbits/s speed=5.1x


Table not segmented in PutCarrotOnPlateInScene-v1 environment

Hello,
Thank you for this great work!
I am using "PutCarrotOnPlateInScene-v1" environment, and I want to extract the segmentation map of the environment which I will use in a learning task.
However, the table is not segmented. I checked the human rendering mode, and there is a table object but it is not seperated from the environment.
Is there a way to fix this?
Example code:
import gymnasium as gym
import numpy as np
import matplotlib.pyplot as plt

from mani_skill.envs.tasks.digital_twins.bridge_dataset_eval import *
from mani_skill.envs.sapien_env import BaseEnv
from mani_skill.sensors.camera import camera_observations_to_images

env: BaseEnv = gym.make(
  "PutCarrotOnPlateInScene-v1",
  obs_mode="rgb+segmentation",
  render_mode="human",
  num_envs=1, # if num_envs > 1, GPU simulation backend is used.
)
obs, _ = env.reset()
images = camera_observations_to_images(obs["sensor_data"]["3rd_view_camera"])
rgb = np.concatenate(images["rgb"].cpu().numpy(), axis=1)
segment = np.concatenate(images["segmentation"].cpu().numpy(), axis=1)

combined = np.concatenate([rgb, segment], axis=0)
plt.imshow(combined)
plt.show()

Output:

Human rendering mode:

that also works!


cmd/compile: possible typo in ssa.go

https://github.com/golang/go/blob/master/src/cmd/compile/internal/gc/ssa.go#L3699
// checkgoto checks that a goto from from to to does not
// jump into a block or jump over variable declarations.
// It is a copy of checkgoto in the pre-SSA backend,
// modified only for line number handling.
// TODO: document how this works and why it is designed the way it is.
func (s *state) checkgoto(from *Node, to *Node) {
	if from.Sym == to.Sym {
		return
	}
...

I just came across this cryptic comment from from to to.
Is this typo? If not, can anybody help me understand this comment?
If it's not a typo, please feel free to close this :)
Thanks a lot!

// checkgoto checks that a goto from [the] from [parameter] to [the] to [parameter] does not...

@ALTree Makes sense. Thanks for providing the contexts!


Upgrade pip on CircleCI

This fixes CircleCI failures caused by an old version of pip. I've also updated the docker base to use a Python 3.6-based image.
Pull Request Checklist
(Please keep this section. It will make maintainer's life easier.)

[x] Privileged views and APIs are guarded by proper permission checks.
[x] All visible strings are translated with proper context.
[x] All data-formatting is locale-aware (dates, numbers, and so on).
[x] Database queries are optimized and the number of queries is constant.
[x] The changes are tested.
[x] The code is documented (docstrings, project documentation).
[x] Python code quality checks pass: pycodestyle, pydocstyle, pylint.
[x] JavaScript code quality checks pass: eslint.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@d08733c). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master   #1719   +/-   ##
========================================
  Coverage          ?     83%
========================================
  Files             ?     142
  Lines             ?    6056
  Branches          ?     660
========================================
  Hits              ?    5027
  Misses            ?     859
  Partials          ?     170

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d08733c...24f73b2. Read the comment docs.


Revert "Bump @azure/msal-node-extension in @azure/identity-cache-pers…

This reverts commit 9baa991c5695b4eca44a46d4630d002fd08064d0. This should have not been merged as the current version of the extensions does not support Node 16 for 3.4.x
Packages impacted by this PR

@azure/identity

Issues associated with this PR
Describe the problem that is addressed by this PR
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.


Add support for overloading the call operator

With this in place, @numba.extending.overload_method(ExtensionType, '__call__') appears to work.

Possibly a fix for #5885.

CI failures are because _ResolutionFailures.format assumes that Template.key is a function, but with this change it is sometimes a tuple:
https://github.com/numba/numba/blob/92df8df57dd31a3da51d3b0cf94a4ec2b591f71a/numba/core/types/functions.py#L142-L149
Any suggestion for what source_fn should be for an overloaded call operator?


fix error "runtime error: index out of range [0] with length 0"

fix for this error

Thank you!  I'm hitting the error consistently while trying to update dependencies. Even with your suggested update I'm still hitting the error. I'll look into root cause...

hyperledger/fabric/integration/gateway/gateway_bft_test.go
line 236 need to be replaced
pickfirstBalancer: UpdateSubConnState.*%d

on
Received SubConn state update:

line 242 need to be replaced (don't forget the space at the end of the line)
pickfirstBalancer: UpdateSubConnState:

on
Received SubConn state update:

Thank you, I've updated https://github.com/hyperledger/fabric/pull/4664 accordingly. I'll close this one now.


dockerutil.BuildEmptyImage() fails with bad API version

I've got a CI/CD pipeline that's run occasionally when we rebuild a image and create an optimized version with Slim. Without anything having changed that I'm aware of (same Slim version, same pipeline runner), this process has started failing with:
dockerutil.BuildEmptyImage: dockerapi.BuildImage() error = API error (400): client version 1.12 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version

I thought this might be related to #637, but it seems to be a separate issue, and the same thing happens whether or not I try setting --crt-api-version. Having updated everything to the latest versions, the problem continues. The issue seems to be specific to this environment, as a local build works.

Steps to Reproduce the Problem

slim build --http-probe-off --continue-after=enter alpine

(trivial reproduction; of course not our actual image)
cmd=build state=started
cmd=build info=params target.image='alpine' continue.mode='enter' rt.as.user='true' keep.perms='true' tags='' image-build-engine='internal' target.type='image'
cmd=build state=image.inspection.start
cmd=build info=image id='sha256:05455a08881ea9cf0e752bc48e61bbd71a34c029bb13df01e40e3e70e0d007bd' size.bytes='0' size.human='0 B'
cmd=build info=image.stack index='0' name='alpine:latest' id='sha256:05455a08881ea9cf0e752bc48e61bbd71a34c029bb13df01e40e3e70e0d007bd'
cmd=build state=image.inspection.done
cmd=build state=container.inspection.start
time="2024-02-26T18:12:39Z" level=error msg="dockerutil.BuildEmptyImage: dockerapi.BuildImage() error = API error (400): client version 1.12 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version\n / output: "
time="2024-02-26T18:12:39Z" level=fatal msg="slim: failure" error="API error (400): client version 1.12 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version\n" stack="goroutine 1 [running]:\nruntime/debug.Stack()\n\truntime/debug/stack.go:24 +0x5e\ngithub.com/slimtoolkit/slim/pkg/util/errutil.FailOn({0x231e3e0, 0xc0007e62a0})\n\tgithub.com/slimtoolkit/slim/pkg/util/errutil/errutil.go:32 +0x4b\ngithub.com/slimtoolkit/slim/pkg/app/master/inspectors/container.(*Inspector).RunContainer(0xc000464b00)\n\tgithub.com/slimtoolkit/slim/pkg/app/master/inspectors/container/container_inspector.go:430 +0x77a\ngithub.com/slimtoolkit/slim/pkg/app/master/command/build.OnCommand(_, _, {_, _}, _, {_, _}, {_, _}, {0x0, ...}, ...)\n\tgithub.com/slimtoolkit/slim/pkg/app/master/command/build/handler.go:1132 +0x4632\[ngithub.com/slimtoolkit/slim/pkg/app/master/command/build.glob..func1(0xc0003d35c0)\n\tgithub.com/slimtoolkit/slim/pkg/app/master/command/build/cli.go:760](http://ngithub.com/slimtoolkit/slim/pkg/app/master/command/build.glob..func1(0xc0003d35c0)/n/tgithub.com/slimtoolkit/slim/pkg/app/master/command/build/cli.go:760) +0x5d51\[ngithub.com/urfave/cli/v2.(*Command](http://ngithub.com/urfave/cli/v2.(*Command)).Run(0x3396180, 0xc0000af480)\n\[tgithub.com/urfave/cli/v2@v2.3.0/command.go:163](http://tgithub.com/urfave/cli/v2@v2.3.0/command.go:163) +0x583\[ngithub.com/urfave/cli/v2.(*App](http://ngithub.com/urfave/cli/v2.(*App)).RunContext(0xc000266d00, {0x233bb88?, 0x340d500}, {0xc00012e000, 0x7, 0x7})\n\[tgithub.com/urfave/cli/v2@v2.3.0/app.go:313](http://tgithub.com/urfave/cli/v2@v2.3.0/app.go:313) +0xaa5\[ngithub.com/urfave/cli/v2.(*App](http://ngithub.com/urfave/cli/v2.(*App)).Run(...)\n\[tgithub.com/urfave/cli/v2@v2.3.0/app.go:224\ngithub.com/slimtoolkit/slim/pkg/app/master.Run()\n\tgithub.com/slimtoolkit/slim/pkg/app/master/app.go:15](http://tgithub.com/urfave/cli/v2@v2.3.0/app.go:224/ngithub.com/slimtoolkit/slim/pkg/app/master.Run()/n/tgithub.com/slimtoolkit/slim/pkg/app/master/app.go:15) +0x45\nmain.main()\n\[tgithub.com/slimtoolkit/slim/cmd/slim/main.go:15](http://tgithub.com/slimtoolkit/slim/cmd/slim/main.go:15) +0x187\n" version="linux/amd64|Transformer|1.40.11|1b271555882eacdfb4e6598d6d0552e9b9b1449b|2024-02-02_01:36:22PM"

Specifications

Version: 1.40.11
Platform: linux/amd64 (self-hosted Bitbucket pipeline runner, which is configured for privileged Docker access so Slim can run)
Output of slim version:

cmd=version info=app container='true' dsimage='false' location='/opt/atlassian/pipelines/agent/build/dist_linux' current='1.40.11' verdict='you have the latest version' cmd='version' version='linux/amd64|Transformer|1.40.11|1b271555882eacdfb4e6598d6d0552e9b9b1449b|2024-02-02_01:36:22PM'
cmd=version info=host cmd='version' osname='Ubuntu 22.04.3 LTS' osbuild='' version='#18~22.04.1-Ubuntu SMP Wed Jan 10 22:54:16 UTC 2024' release='6.2.0-1018-aws' sysname='Linux'
cmd=version info=docker server.version='25.0.3' architecture='x86_64' cmd='version' name='a640edfcc04d' kernel.version='6.2.0-1018-aws' operating.system='Alpine Linux v3.19 (containerized)' ostype='linux'
cmd=version info=dclient build.time='2024-02-06T21:13:08.000000000+00:00' git.commit='f417435' cmd='version' api.version='1.44' min.api.version='1.24'
app='slim' message='GitHub Discussions' info='https://github.com/slimtoolkit/slim/discussions'
app='slim' message='Join the CNCF Slack channel to ask questions or to share your feedback' info='https://cloud-native.slack.com/archives/C059QP1RH1S'
app='slim' message='Join the Discord server to ask questions or to share your feedback' info='https://discord.gg/9tDyxYS'
app='slim' message='Join the Gitter channel to ask questions or to share your feedback' info='https://gitter.im/docker-slim/community'

Interesting... need to investigate/repro. Either way, the next release should address this. Check back a bit later or follow me on Github or Twitter to be notified when the new release is out.

Sounds good, thanks. I'll see how the next version works out. We're still having some build issues, but it looks like if we set a DOCKER_API_VERSION environment variable, we can at least get past this error.

For reference, other versions may work (1.44 did not), but we seem to be back in business with
export DOCKER_API_VERSION='1.25'

in our pipeline

@jimcottrell this might work as-is https://github.com/mintoolkit/mint/releases/tag/1.41.1 let me know if you still have problems there

I've tried with v1.41.1 and no explicit DOCKER_API_VERSION and I get that same error: client version 1.12 is too old

@jimcottrell which version of Docker do you have installed? Are you on Mac or Linux? If you are on Linux are you using Docker Desktop or only Docker Engine? If you are on a Mac is it an AMD or an M1/M2? Trying to repro... more info on your environment will help

Getting this on Fedora 39 with the latest stable docker-ce and slim installed.
slim build --target nvapi --tag slim --http-probe=false --dockerfile Dockerfile --dockerfile-context .
...
cmd=build info=build.error status='standard.image.build.error' value='API /build requires version 1.25, requested version 1.24 is insufficient'
cmd=build state=exited code=33554435 version=linux/amd64|Transformer|1.40.11|1b271555882eacdfb4e6598d6d0552e9b9b1449b|2024-02-02_01:36:22PM location=/usr/local/bin

dnf info docker-ce-26.1.1-1.fc39.x86_64
Last metadata expiration check: 4:53:24 ago on Sun 05 May 2024 09:04:18.
Installed Packages
Name         : docker-ce
Epoch        : 3
Version      : 26.1.1
Release      : 1.fc39
Architecture : x86_64
Size         : 104 M
Source       : docker-ce-26.1.1-1.fc39.src.rpm
Repository   : @System
From repo    : docker-ce-stable
Summary      : The open-source application container engine
URL          : https://www.docker.com

@sammcj do you get the same result with this version?

@sammcj will try to repro with Fedora 39

@kcq Sorry for the delay in responding. As noted before, this is happening only on a self-hosted Bitbucket pipeline runner (linux/amd64). When I run locally, I have no issue. To make Slim work in the pipeline environment, it has to run via the docker:dind image.
Host Docker
+ docker version
Client:
 Version:           20.10.24
 API version:       1.41
 Go version:        go1.19.7
 Git commit:        297e128
 Built:             Tue Apr  4 18:17:06 2023
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true
Server: Docker Engine - Community
 Engine:
  Version:          25.0.2
  API version:      1.44 (minimum version 1.24)
  Go version:       go1.21.6
  Git commit:       fce6e0c
  Built:            Thu Feb  1 00:23:45 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.7.13
  GitCommit:        7c3aca7a610df76212171d200ca3811ff6096eb8
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker:dind
+ docker version
Client:
 Version:           20.10.24
 API version:       1.41
 Go version:        go1.19.7
 Git commit:        297e128
 Built:             Tue Apr  4 18:17:06 2023
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true
Server: Docker Engine - Community
 Engine:
  Version:          26.1.3
  API version:      1.45 (minimum version 1.24)
  Go version:       go1.21.10
  Git commit:       8e96db1
  Built:            Thu May 16 08:33:58 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.7.15
  GitCommit:        926c9586fe4a6236699318391cd44976a98e31f1
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Looking at this does seem to explain why I couldn't set it to use v1.44.

@kcq Sorry for the delay in responding. As noted before, this is happening only on a self-hosted Bitbucket pipeline runner (linux/amd64). When I run locally, I have no issue. To make Slim work in the pipeline environment, it has to run via the docker:dind image.
Host Docker
+ docker version
Client:
 Version:           20.10.24
 API version:       1.41
 Go version:        go1.19.7
 Git commit:        297e128
 Built:             Tue Apr  4 18:17:06 2023
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true
Server: Docker Engine - Community
 Engine:
  Version:          25.0.2
  API version:      1.44 (minimum version 1.24)
  Go version:       go1.21.6
  Git commit:       fce6e0c
  Built:            Thu Feb  1 00:23:45 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.7.13
  GitCommit:        7c3aca7a610df76212171d200ca3811ff6096eb8
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker:dind
+ docker version
Client:
 Version:           20.10.24
 API version:       1.41
 Go version:        go1.19.7
 Git commit:        297e128
 Built:             Tue Apr  4 18:17:06 2023
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true
Server: Docker Engine - Community
 Engine:
  Version:          26.1.3
  API version:      1.45 (minimum version 1.24)
  Go version:       go1.21.10
  Git commit:       8e96db1
  Built:            Thu May 16 08:33:58 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.7.15
  GitCommit:        926c9586fe4a6236699318391cd44976a98e31f1
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Looking at this does seem to explain why I couldn't set it to use v1.44.

Running with dind in Bitbucket runners makes it more complicated because each CI/CD vendor does the dind setup in slightly different ways, which requires different ways to connect to the (correct) Docker runtime. Some environments don't expose the Docker unix socket. Other environments needs certs to connect to the Docker runtime. Some have more advanced network configurations that prevents direct container communication, so the --sensor-ipc-mode and --sensor-ipc-endpoint flags need to be used. The RUNNING CONTAINERIZED README section covers a few examples
To troubleshoot your setup we need two things to get started:

How you invoke the slim command in your dind setup.
Your Bitbucket runner config that defines how the dind magic is configured.

Here's a simplified version of our bitbucket-pipelines.yml that fails with client version 1.12 is too old:
image:
  name: atlassian/default-image:4
definitions:
  services:
    privileged-docker:
      type: docker
      image:
        name: docker:dind
pipelines:
  custom:
    test:
      - step:
          runs-on:
            - linux
            - self.hosted
          name: Build Optimized Image
          services:
            - privileged-docker
          script:
            - curl https://downloads.dockerslim.com/releases/1.40.11/dist_linux.tar.gz -o slim.tar.gz
            - tar xvf slim.tar.gz
            #- export DOCKER_API_VERSION='1.25' # Temporary, see https://github.com/slimtoolkit/slim/issues/646
            - ./dist_linux/slim build --continue-after=enter alpine

I tried it with --in-container=true which didn't make any difference. What needs to be updated to point to the dind Docker runtime? Apart from this one case, I'm not very familiar with dind. The DOCKER_HOST environment variable exists, but I don't believe the Docker UNIX socket is present.

Are there any updates here?
I am having the same problem with a gitlab pipeline and dind

The latest release, 1.41.5, shouldn't have the docker API problem.
To connect to the Docker daemon it might be necessary to extract the daemon IP address from the /etc/hosts file if the environment doesn't configure DOCKER_HOST on its own properly. Here's an example for Gitlab (need to double check if it still works): docker run -e DOCKER_HOST=tcp://$(grep docker /etc/hosts | cut -f1):2375 mintoolkit/mint slim your-docker-image-name
Might need to use the --sensor-ipc-mode and --sensor-ipc-endpoint flags too for dind depending on the CI/CD vendor.
I'll repro it with Gitlab first to confirm that the setup is still ok. Then I'll try to repro with a Bitbucket setup.

Okay, than the installation routine should be adapted:
I installed it via:
curl -sL https://raw.githubusercontent.com/slimtoolkit/slim/master/scripts/install-slim.sh | bash -
and in the script, the latest version is:
curl -sL https://api.github.com/repos/slimtoolkit/slim/releases | grep tag_name | head -n1 | cut -d'"' -f4
1.40.11

Okay, than the installation routine should be adapted: I installed it via:
curl -sL https://raw.githubusercontent.com/slimtoolkit/slim/master/scripts/install-slim.sh | bash -  and in the script, the latest version is:
curl -sL https://api.github.com/repos/slimtoolkit/slim/releases | grep tag_name | head -n1 | cut -d'"' -f4 1.40.11

should be this install script: https://raw.githubusercontent.com/mintoolkit/mint/master/scripts/install-mint.sh

Hello there!
I had same problem with latest mint 1.41.7, Docker latest (27.3.1), Docker API v1.47, and the only solution was to set explicitely => DOCKER_API_VERSION=1.47

Hello @kcq !
I had same problem with latest mint 1.41.7, Docker latest (27.3.1), Docker API v1.47, and the only solution was to set explicitely => DOCKER_API_VERSION=1.47

What image did you try to slim or was it a different command? Do you have a repro?

Hello @kcq !
I had same problem with latest mint 1.41.7, Docker latest (27.3.1), Docker API v1.47, and the only solution was to set explicitely => DOCKER_API_VERSION=1.47

What image did you try to slim or was it a different command? Do you have a repro?

It is a custom internal image, already created.
Found just now that i'm forced to use the 'export' =>
export DOCKER_API_VERSION=1.47
mint slim [...]

or
to put the variable definition inline =>
DOCKER_API_VERSION=1.47 mint slim [...]
While if i do:
DOCKER_API_VERSION=1.47
mint slim [...]

It says again client API 1.12 is too old.

Thank you for the additional context @marcoaversanoigt ! This will help with my repro. We have the environment and the command context that should be enough. Working on the repro (hopefully can repro it without the Github workflow part :-))

Hello guys.
I was running through the same issue discussed here a few days ago. I started the resolution it by reinstalling dockerd then I ensured that docker slim installed version matches with my OS/WSL distro then the famous command slim build <image-name> hopefully worked.

For anyone confused like me regarding the updates, version problem or whatever, mint is deprecated, you now need to install mint: https://github.com/mintoolkit/mint

For anyone confused like me regarding the updates, version problem or whatever, mint is deprecated, you now need to install mint: https://github.com/mintoolkit/mint

Yes, the latest enhancements are there. There's a new release coming soon too.

For anyone confused like me regarding the updates, version problem or whatever, mint is deprecated, you now need to install mint: https://github.com/mintoolkit/mint

You said mint is deprecated twice. Did you mean to say slim in one of those? Which one is deprecated and which one should be used? I'm running into the same problem. slim version tells me the api version is 1.44 but I'm still getting this error for version 1.12 in bitbucket pipelines (not self hosted).

NilsMoller

It was a typo. He meant to say slim :-) It's not really deprecated, but the current updates are in the mint releases. @NilsMoller are you using the latest release ? If not try using it and let me know if you are getting the same behavior. This particular API version problem has been tricky to track down / repro. The upcoming release will have a number docker client/API enhancements and also container image format handling enhancements for XRAY among other things.

I am using the latest version (as far as i know). I will move to mint and try again. Thanks!

I am now using Mint installed using the scripted install (as specified in the README). It works locally, but in the Bitbucket pipeline it fails with the same error.
In the pipeline, the output of mint --version is as follows:
mint version linux/amd64|Aurora|1.41.7|a2a53d2348aeedf0d650d47debf477a2cad47111|2024-09-25_03:07:42PM

Thanks for the update @NilsMoller ! Good that it's functional locally. That's a useful data point for the repro. Next is for me to repro a bitbucket setup.


[SP-5746] - Backport of PDI-18178 - Data Validator step - error messa…

…ge during "Expected end string" validation it's not visible on MacOS (8.3 Suite)
cherry-pic of #7716
@ssamora
@ppatricio

:white_check_mark: Build finished in 17m 2s
Build command:
mvn clean verify -B -e -Daudit -amd -pl ui

:ok_hand: All tests passed!
Tests run: 1103, Failures: 0, Skipped: 0    Test Results

:information_source:  This is an automatic message


How to integrate with responder lib?

Hi. I'm attempting to use the spdm-emu to act as a requester to a device that runs libspdm by having it make reads and writes to a DOE mailbox on a system. However, when running the emulator, I'm seeing the following error:
local-system$ ./spdm_requester_emu --ver 1.2 --trans PCI_DOE

spdm_requester_emu version 0.1
ver - 0x12
trans - 0x2
Connect Error - 6f

I think I have some fundamental misunderstandings with how to use this tool. Why is TCP being used if reads and writes just need to be made to a mailbox?

For that use case you probably want to use https://github.com/westerndigitalcorporation/spdm-utils.

SPDM-Utils uses libspdm and supports testing a DOE responder: https://github.com/westerndigitalcorporation/spdm-utils?tab=readme-ov-file#testing-a-real-device


Add jsonOnly option to merge command

Following discussion thread https://github.com/CesiumGS/3d-tiles-tools/issues/44
This option is meant to avoid copying resources (tileset.json and tile contents) when merging multiple input tilesets. Results in a tileset.json that references input tilesets where they are stored.
Can add another commit to remove the --jsonOnly flag from the merge command to instead create a new command, mergeJson

Thanks. I tried it out locally, and ran the tests, and verified that the CLA was signed, and everything seems to be fine....
...except for that line endings thing. Quickly looking at the documentation, it seems like --end-of-line lf is the default, so that should not be given explicitly. If this is removed, I can merge this PR.
There's still the question about the line endings, though: I'll have to check what the best practices/policies are here. This should be unrelated to this PR, and may be handled in a small cleanup PR later.

Woops sorry for pushing that change in package.json. Indeed this was just testing on my side, I reverted to the original package.json prettier command.

Note I also tried enforcing line endings to LF in .gitattributes at the root directry of the repo, it might be a good option to have it in the repo for future external windows-based contributors (eol can also be set to auto).
# .gitattributes
# Auto detect text files and perform LF normalization
* text eol=lf

Yes, it seems like using a .gitattributes seems to be the way to go here. The desired behavior can also be configured by each user locally, but for the case that a user did not do this, the .gitattributes should take care of it. I'll confirm this internally, and likely add create a PR to add this soon.
Thanks again for the mergeJson functionality.
(I'm usually updating things like the CHANGES.md and README.md prior to a release. So I'll probably schedule a release soon, and then also update these files accordingly)

Thanks for helping me design that PR, and happy that I could help!


Invoices and emails

Added 4 emails

We send emails if:
-payment failed
-payment succeeded
-payment not required (a user used the service, but credits covered the expenses)
To run tsx email templates outside of the next.js environment (worker or manual scripts), I added the tsconfig.server.json file that allows using tsx/jsx.
The helper "tsx": "tsx --tsconfig tsconfig.server.json" allows to run scripts without specifying the tsconfig file, but the "dev:worker"/"worker" scripts still require an explicit path.
Invoice logic change
We are issuing invoices at 2 AM UTC on the first day of each month, and trying to charge them right away.
If a payment fails, we run a job that tries to charge again, on the next day at 8 AM. A user will have 28 hours to add a payment method. Should we change the time? Maybe add one more job that runs in a week?
Invoices page design change

Database change
Added indexes to FineTune model and Dataset model.
Added the FREE enum to invoice status.
Fixed a relation typo from Invoice to invoice in CreditAdjustment table.
Scripts
To rename all existing invoices from CANCELLED to FREE, use the script:
pnpm tsx src/server/scripts/renameCancelledInvoicesToFree.ts
I could not combine it into a single migration, postgress does not allow to do it in one transaction.
Another script sends emails to existing clients who have pending invoices or used credits.
pnpm tsx src/server/scripts/sendInvoiceEmailToExistingClients.ts

Let's see how this goes!

Famous last words


Add client id field here

https://github.com/shaikhAhmedRaza/hms_new/blob/d4acaea48576be18076c082236c37168db63afd9/src/app/models/client.ts#L32

Id is already there


Example for Images

I'm excited to apply this model to image data. I was wondering if you could give a trivial example for how to apply this library to individual images instead of video. Thank you!

@jpfeil hey Jacob! thanks for your interest
you can pretrain on images by setting the dataset_type to images https://github.com/lucidrains/magvit2-pytorch/commit/ec2696d55f0c4cb1028b258e621ed207873fc7b1

🤔 i need to take my dog down to Santa Cruz at some point for a hike, and for the boardwalk of course


Include landing and take-off phases

Good idea!
For take-off, it might be needed to include the ground (forces) in the model.
Any suggestions how to launch and land the kite?


Fix sign in

https://idobata.io/users/sign_in seems no longer available

Thank you for your reporting. I'm working now in another branch.
See https://github.com/harukasan/butter/tree/feature/brand-new-idobata.

:+1:


Self contained CLI

Can we document the init command in the top level README before the create instructions? Thanks!

All set.


Options | Add additional options for update settings

We should provide more options to user about how the .json files should be merged with current settings (currently the only thing users can do is to check if "Groups" names should be updated or not).
Requirements:

[ ] Move the checkbox "Enable groups" (for useGroups option) to the "Search Results Options" column (since this option should exclusively be used for show/hide groups on the context menu, we should have a completely separate option to check if groups names should be updated when refreshing the settings).
[ ] Rename the label "Last Refreshed on" to "Last Updated on".
[ ] Rename the "Refresh now" button to "Update now".
[ ] Rename the "Refresh automatically" label to "Update periodically (once per week)".
[ ] Add a new title (with is own list of items) called "Merge Settings Options".
[ ] One merge option should be a dropdown with values "Merge", "Override" and "Ignore" and a side label "Search Providers". Default value for the dropdown should be "merge".
[ ] Next to the previous label should be a info icon that, when clicked, will open a popover explaining that with "Override" all local search providers will be deleted and replaced when settings are updated, that "Merge" will just add (to the current list of search providers) the search providers that aren't already added from the settings file, and that "Ignore" will keep current list and ignore anything on the settings file.
[ ] Another merge option should be a checkbox called "Override Groups names" (defaulted to false).
[ ] Another merge option should be a checkbox with label "Override Carbon Black Configuration", defaulted to false.
[ ] Another merge option should be a dropdown with values "Merge", "Override" and "Ignore" and a side label "Carbon Black Queries". Here we should also have a info icon similar to the one of "Search Providers".
[ ] The finales merge options will be the same checkbox and dropdown from Carbon Black, but for Security Analytics and NetWitness.
[ ] The values for these merge options should be should also be stored into the Chrome's storage, inside the object from StoreKey.SETTINGS, using the field names: mergeSearchProviders, mergeGroups, mergeCBC, mergeRSA and mergeNWI (these last three with fields config and queries).
[ ] Optimize the implementation on settings.html use Mustache, by defining a template that will render the checkboxs, inputs and dropdowns (like currently done by the template_providerConfig template).
[ ] On utils.js create constants MERGE_OPTIONS, SEARCH_RESULT_OPTIONS and CONFIG_FILE_OPTIONS for define arrays with the data which will be used to generate all inputs from the previous step.
[ ] Update the parseJSONFile function so all these settings are keeping in mind when merging the a JSON file with current settings.
[ ] Finally, on migration.js the value for "Override Groups names" should be initialized to the same value of useGroups.

Please note that, for simplify code when update merge options for CBC / RSA / NWI, you can use the _.set and _.get methods from Lodash for doing things like var mergeCBCConfig = _.get( await LocalStore.getOne(StoreKey.SETTINGS), "mergeCBC.config", {}) and var settings = await LocalStore.getOne(StoreKey.SETTINGS); _.set(settings, "mergeCBC.config", newCBCConfigSettings).
This will also simplify how you define MERGE_OPTIONS, since you will be able to do something like:
var MERGE_OPTIONS = [
   { storeKey: "mergeSearchProviders", label: "Search Providers", fields: [...], ... }
   { storeKey: "mergeGroups", label: "Providers Groups", fields: [...], ... }
   { storeKey: "mergeCBC.config", label: "Carbon Black Configuration", fields: [...], ... }
   { storeKey: "mergeCBC.queries", label: "Carbon Black Queries", fields: [...], ... }
  ...
];

@jfmdev Will this UI work?

@pushpendraKh Not quite... the "Merge Settings Options" should  be outside "Configuration File Options" (i.e. the "Merge Settings Options" text should be in a <h1> and his options should be in is own list).

Also, the "Update now" button should be inside the "Last updated on" item (like it's now), otherwise gives the impression that clicking it will save the form (instead of re-fetching the configuration file).

Like this right?

@pushpendraKh Yes, exactly 👍


Refine document of VS Code extension

Coverage decreased (-0.01%) to 53.064% when pulling 2f672763f870c9131f5b828fb702542cd30bfed4 on squirrelsc:vscode into 49dde84ff524ca2bc788a9cceaedb0b8eab88445 on Microsoft:master.


add vendor folder

Will close it for now - it is outdated. If later decide to include vendor folder will create a new PR.


New command !flavor {card} which fetches the flavor text of a card

Perhaps also interesting would be getting a random flavor text?
!randomflavor {set|format}
which gives the flavor text of a random card in the specified set or format

We do not currently store flavor text although it is available in the scryfall data as flavor_text. It is per-printing information – we would store it in a new table or in the printings table.
I quite like:
!flavor {cardname} – gives the latest flavor text for a particular card.
!flavor – gives a random flavor text. We'd probably have to provide reverse-lookup else this might be maddening.
Doing per-set flavor text would probably come a distant second to enabling the same thing for images and would use whatever mechanism we implement there.


js: application/x-javascript is obsolete

Should be application/javascript.
http://www.ietf.org/rfc/rfc4329.txt

Fixed, thanks for pointing it out.


Telegram markdown

Hello!
I encounter an issue with the telegram markdown.
I want to use inline URL, but it doesn't work. My config is:
alert_text_type: "alert_text_only"
alert_text: |
  Happened at {0}
  Index: {1}
  You can view it in [Kibana]({2})
alert_text_args:
  - "@timestamp"
  - "_index"
  - "kibana_link"
#Kibana
generate_kibana_link: true
use_kibana4_dashboard: "https://very_big_link_to_dashboard"

I just get full URL in telegram message:
Happened at 2017-10-19T10:49:44.729Z
Index: heartbeat-2017.10.19
You can view it in [Kibana](https://kibana/app/kibana#/dashboard/e6a12d30-ae87-11e7-ad73-dd0a84ddbc42?_g=(refreshInterval:(display:Off,pause:!f,value:0),time:.....

any help would be appreciated!
Thanks!

As a workaround I inserted triple backticks in alert_text block and the problem was solved.
alert_text_type: "alert_text_only"
alert_text: |

    ```
    Happened at {0}
    Index: {1}
    You can view it in [Kibana](http://somelink)
    ```
alert_text_args:
  - "@timestamp"
  - "_index"


katawa-shoujo: init at 1.3.1

Description of changes
Packages Katawa Shoujo, a free visual novel game.
Things done

Built on platform(s)

[x] x86_64-linux
[x] i686-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1902

An icon for a desktop file cannot be extracted from the game assets on master due to https://github.com/NixOS/nixpkgs/issues/218108#issuecomment-1445274449, removed that code.


Update index.md

Summary
Adding content to example post
Basic example
Include a basic example, screenshots, or links.
Motivation
Why are we doing this? What use cases does it support? What is the expected outcome?
Checks

[x] Read Create a Pull Request
[x] Supports all screen sizes (if relevant)
[x] Supports both light and dark mode (if relevant)
[x] Passes npm run test

Thanks for the idea! Added more descriptive content: https://doks.netlify.app/blog/example-post/


Fixes merge mishap.

@QuincyLarson and I had edited the same text, so the merge added a bunch of weird Git stuff that prevented the site from building.

Should've called this branch "build-fix", my bad.
The JSON is now correct, at least according to jsonlint and your seed.js program.

Thanks. By the time I saw this, I'd already fixed this on my end and pushed the fix.

Sort of figured that would happen. :)


[Feature Request]: Add more features of the home page

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Add text of the page as well as the colour and many more
Use Case
Use css properties
Benefits
Make more eye catching
Add ScreenShots
No response
Priority
Low
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

Add some transition, colour contrast and etc this kind of css modification
On Mon, 14 Oct 2024, 2:39 pm Trisha Sahu, @.***> wrote:

Is there an existing issue for this?

I have searched the existing issues

Feature Description
Add text of the page as well as the colour and many more
Use Case
Use css properties
Benefits
Make more eye catching
Add ScreenShots
No response
Priority
Low
Record

I have read the Contributing Guidelines
I'm a GSSOC'24 contributor
I have starred the repository

Kindly describe in detail of what changes you are supposed to do.
@Dipanita45 https://github.com/Dipanita45
—
Reply to this email directly, view it on GitHub
https://github.com/Trisha-tech/OnlineBookSales/issues/470#issuecomment-2410530807,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A7SRZ6ATFIIULQSY6SCJX2DZ3OC47AVCNFSM6AAAAABP4KZPYSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJQGUZTAOBQG4
.
You are receiving this because you were mentioned.Message ID:
@.***>


.har files not parsing

Similar to #3. har file from Firefox is not parsed
Left "Error in $.log.pages[0]: When parsing the record Page of type HAR.Page.Page the key title was not present."

Are you suggesting Page.title is optional?

doesn't seem title is optional from spec. http://www.softwareishard.com/blog/har-12-spec
curious what page you are testing or maybe shared the HAR file?


feat(openapi-tooling): add support for fuzzing with schemathesis

Hey, I just made a Pull Request!
This adds fuzzing capabilities for plugins documented with OpenAPI using Schemathesis 🎉 !
search and todo were able to integrate with no issues, but the catalog has some API weirdnesses. Basically, defining fields for /by-refs or /entities causes the return value to be missing "required" fields. Would be curious to hear thoughts on if this is just something we ignore. It would be a breaking change on the client, but it's already codified behavior in the API.
Following this work, I'd like to make this into a GH workflow for use with Uffizzi deployments.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

not stale :)

Happy to see this merged! If you’ll ever need any support from the Schemathesis side, feel free to tag me.


Prerequisites for classification in Machine Learning

Description
Cover the prerequisite libraries and functions needed for Classification in Machine Learning
Type of Contribution
Documentation
### Code of Conduct

[x] I follow Contributing Guidelines & Code of conduct of this project.

please assign it to me

I will love to contribute assign it to me.

I guess you should self assign yourself .. read other issues people are doing like this :
/*assign

I will love to contribute assign it to me.

I guess you should self assign yourself .. read other issues people are doing like this : /*assign

In the previous issue, I done the self-assign but owner assign it to the person who came after me.

/assign

/assign

Did it work?

@m0hit-kumar Go ahead

/assign

/assign

Did it work?

yes but you have to comment first and then use /assignn

/assign