Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +70 ms] ** (triage:13849): WARNING **: 13:56:11.946: Unable to retrieve framework response: Message is not valid JSON
[   +2 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +64 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[        ] ** (triage:13849): WARNING **: 13:56:12.015: Unable to retrieve framework response: Message is not valid JSON
[   +1 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[        ] ** (triage:13849): WARNING **: 13:56:12.018: Unable to retrieve framework response: Message is not valid JSON
[   +2 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[        ] ** (triage:13849): WARNING **: 13:56:12.022: Unable to retrieve framework response: Message is not valid JSON
[   +1 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[        ] ** (triage:13849): WARNING **: 13:56:12.023: Unable to retrieve framework response: Message is not valid JSON
[  +18 ms] ** (triage:13849): WARNING **: 13:56:12.041: Unable to retrieve framework response: Message is not valid JSON
[   +1 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +17 ms] ** (triage:13849): WARNING **: 13:56:12.061: Unable to retrieve framework response: Message is not valid JSON
[   +1 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +90 ms] ** (triage:13849): WARNING **: 13:56:12.149: Unable to retrieve framework response: Message is not valid JSON
[   +5 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +10 ms] ** (triage:13849): WARNING **: 13:56:12.165: Unable to retrieve framework response: Message is not valid JSON
[   +4 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +12 ms] ** (triage:13849): WARNING **: 13:56:12.184: Unable to retrieve framework response: Message is not valid JSON
[   +2 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +75 ms] ** (triage:13849): WARNING **: 13:56:12.261: Unable to retrieve framework response: Message is not valid JSON
[   +4 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[   +9 ms] ** (triage:13849): WARNING **: 13:56:12.274: Unable to retrieve framework response: Message is not valid JSON
[   +6 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[   +8 ms] ** (triage:13849): WARNING **: 13:56:12.289: Unable to retrieve framework response: Message is not valid JSON
[   +3 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +38 ms] ** (triage:13849): WARNING **: 13:56:12.332: Unable to retrieve framework response: Message is not valid JSON
[   +2 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +46 ms] ** (triage:13849): WARNING **: 13:56:12.381: Unable to retrieve framework response: Message is not valid JSON
[   +2 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +58 ms] ** (triage:13849): WARNING **: 13:56:12.443: Unable to retrieve framework response: Message is not valid JSON
[   +3 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +16 ms] ** (triage:13849): WARNING **: 13:56:12.461: Unable to retrieve framework response: Message is not valid JSON
[   +3 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +11 ms] ** (triage:13849): WARNING **: 13:56:12.476: Unable to retrieve framework response: Message is not valid JSON
[   +2 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +44 ms] ** (triage:13849): WARNING **: 13:56:12.525: Unable to retrieve framework response: Message is not valid JSON
[   +2 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +41 ms] ** (triage:13849): WARNING **: 13:56:12.567: Unable to retrieve framework response: Message is not valid JSON
[   +2 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +21 ms] ** (triage:13849): WARNING **: 13:56:12.591: Unable to retrieve framework response: Message is not valid JSON
[   +4 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +16 ms] ** (triage:13849): WARNING **: 13:56:12.614: Unable to retrieve framework response: Message is not valid JSON
[   +5 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +64 ms] ** (triage:13849): WARNING **: 13:56:12.682: Unable to retrieve framework response: Message is not valid JSON
[   +2 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[   +6 ms] ** (triage:13849): WARNING **: 13:56:12.691: Unable to retrieve framework response: Message is not valid JSON
[   +3 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +34 ms] ** (triage:13849): WARNING **: 13:56:12.729: Unable to retrieve framework response: Message is not valid JSON
[   +2 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +59 ms] ** (triage:13849): WARNING **: 13:56:12.792: Unable to retrieve framework response: Message is not valid JSON
[   +2 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +31 ms] ** (triage:13849): WARNING **: 13:56:12.818: Unable to retrieve framework response: Message is not valid JSON
[   +3 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[   +4 ms] ** (triage:13849): WARNING **: 13:56:12.829: Unable to retrieve framework response: Message is not valid JSON
[   +4 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[ +108 ms] ** (triage:13849): WARNING **: 13:56:12.945: Unable to retrieve framework response: Message is not valid JSON
[   +4 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[   +5 ms] ** (triage:13849): WARNING **: 13:56:12.957: Unable to retrieve framework response: Message is not valid JSON
[   +5 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[   +4 ms] ** (triage:13849): WARNING **: 13:56:12.968: Unable to retrieve framework response: Message is not valid JSON
[   +1 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +19 ms] ** (triage:13849): WARNING **: 13:56:12.989: Unable to retrieve framework response: Message is not valid JSON
[   +1 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +22 ms] ** (triage:13849): WARNING **: 13:56:13.013: Unable to retrieve framework response: Message is not valid JSON
[   +1 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +23 ms] ** (triage:13849): WARNING **: 13:56:13.038: Unable to retrieve framework response: Message is not valid JSON
[   +1 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +23 ms] ** (triage:13849): WARNING **: 13:56:13.063: Unable to retrieve framework response: Message is not valid JSON
[   +1 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +12 ms] ** (triage:13849): WARNING **: 13:56:13.076: Unable to retrieve framework response: Message is not valid JSON
[   +2 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +65 ms] ** (triage:13849): WARNING **: 13:56:13.143: Unable to retrieve framework response: Message is not valid JSON
[   +4 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +31 ms] ** (triage:13849): WARNING **: 13:56:13.179: Unable to retrieve framework response: Message is not valid JSON
[   +4 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[   +7 ms] ** (triage:13849): WARNING **: 13:56:13.193: Unable to retrieve framework response: Message is not valid JSON
[   +1 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[ +125 ms] ** (triage:13849): WARNING **: 13:56:13.319: Unable to retrieve framework response: Message is not valid JSON
[   +3 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")
[  +22 ms] ** (triage:13849): WARNING **: 13:56:13.347: Unable to retrieve framework response: Message is not valid JSON
[   +4 ms]
           Another exception was thrown: A KeyUpEvent is dispatched, but the state shows that the physical key is pressed on a different logical key. If this
occurs in
           real application, please report this bug to Flutter. If this occurs in unit tests, please ensure that simulated events follow Flutter's event
model as
           documented in `HardwareKeyboard`. This was the event: KeyUpEvent#c9dab(physicalKey: PhysicalKeyboardKey#7000b(usbHidUsage: "0x0007000b",
debugName: "Key H"),
           logicalKey: LogicalKeyboardKey#005c7(keyId: "0x15000005c7", keyLabel: "", debugName: "Key with ID 0x015000005c7"), character: null, timeStamp:
           4:12:19.337000) and the recorded logical key LogicalKeyboardKey#00068(keyId: "0x00000068", keyLabel: "H", debugName: "Key H")

stable
master

❗
❗

Check flutter doctor -v outputs for each channel below

flutter doctor -v
[✓] Flutter (Channel stable, 2.5.0, on Zorin OS 16 5.11.0-34-generic, locale en_US.UTF-8)
    • Flutter version 2.5.0 at /home/taha/Code/flutter_stable
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 4cc385b4b8 (9 days ago), 2021-09-07 23:01:49 -0700
    • Engine revision f0826da7ef
    • Dart version 2.14.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /home/taha/Code/android-sdk
    • Platform android-31, build-tools 31.0.0
    • ANDROID_SDK_ROOT = /home/taha/Code/android-sdk
    • Java binary at: /home/taha/Code/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Linux toolchain - develop for Linux desktop
    • clang version 10.0.0-4ubuntu1
    • cmake version 3.16.3
    • ninja version 1.10.0
    • pkg-config version 0.29.1

[✓] Android Studio (version 2020.3)
    • Android Studio at /home/taha/Code/android-studio
    • Flutter plugin version 60.1.2
    • Dart plugin version 203.8292
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] VS Code
    • VS Code at /snap/code/current
    • Flutter extension version 3.26.0

[✓] Connected device (2 available)
    • Linux (desktop) • linux  • linux-x64      • Zorin OS 16 5.11.0-34-generic
    • Chrome (web)    • chrome • web-javascript • Google Chrome 93.0.4577.82

• No issues found!

[✓] Flutter (Channel master, 2.6.0-6.0.pre.128, on Zorin OS 16 5.11.0-34-generic, locale en_US.UTF-8)
    • Flutter version 2.6.0-6.0.pre.128 at /home/taha/Code/flutter_master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision fa9790ca47 (6 hours ago), 2021-09-17 01:37:03 -0400
    • Engine revision e70febab63
    • Dart version 2.15.0 (build 2.15.0-118.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /home/taha/Code/android-sdk
    • Platform android-31, build-tools 31.0.0
    • ANDROID_SDK_ROOT = /home/taha/Code/android-sdk
    • Java binary at: /home/taha/Code/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Linux toolchain - develop for Linux desktop
    • clang version 10.0.0-4ubuntu1
    • cmake version 3.16.3
    • ninja version 1.10.0
    • pkg-config version 0.29.1

[✓] Android Studio (version 2020.3)
    • Android Studio at /home/taha/Code/android-studio
    • Flutter plugin version 60.1.2
    • Dart plugin version 203.8292
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] VS Code
    • VS Code at /snap/code/current
    • Flutter extension version 3.26.0

[✓] Connected device (2 available)
    • Linux (desktop) • linux  • linux-x64      • Zorin OS 16 5.11.0-34-generic
    • Chrome (web)    • chrome • web-javascript • Google Chrome 93.0.4577.82

• No issues found!

✅: No Issue ❗: Issue reproduced
See https://github.com/flutter/flutter/issues/89729#issuecomment-916047260
duplicate of https://github.com/flutter/flutter/issues/89729


set alpine latest version

Severity: Major Always tag the version of an image explicitly
ref: https://www.codefactor.io/repository/github/prest/prest/file/master/Dockerfile

What is distroless? Where's the code for that image?

Very very good  https://github.com/GoogleContainerTools/distroless


Channels current state is unavailable

Hello,
I have installed everything but when I click "connect" I am receiving the message:
"Channels current state is unavailable"
I am running Laravel 5.7.28
I have also ran the artisan server command. I am getting this error both on my windows machine and my centos OS installation.
Any idea why could cause this please with Laravel 5.7.28
Thank you.

Ok, this seems to happen only under https. And I think the reason is because I need to add the SSL path.

Hi @FreddyCrugger, did you solve the puzzle? Can you connect through https to your laravel app after set the path? How you did set this path? My websockets.config already have the path: 'local_cert' => env('LARAVEL_WEBSOCKETS_SSL_LOCAL_CERT', '/etc/letsencrypt/live/[MYSITE]/fullcert.crt'),
My websocket only work with http :(

No I went back to using pusher.
I cannot believe there isn't anymore help from Laravel to help us setting up web sockets on the app.
I spent days and days on this, no chance.

After days and days finally I got it working, I needed to change my ssl provider and check the passed all ssl checks. Ther are many sites that if your ssl is really ok, mine was fail on the chaing test so may be was it. But the error do not help to find the solution. Thanks you @FreddyCrugger :)

I use Laragon locally. It provides SSL support for testing. I want to take advantage of this. But I don't know how to define "local_cert" and "local_pk" paths in websockets.php.
Laragon SSL config paths:
C:/laragon/etc/ssl/laragon.crt
C:/laragon/etc/ssl/laragon.key
Can you help me? @FreddyCrugger @albertord84 @cesaric  @canhkieu @eldor

@ghost I'm also using laragon. Did you manage to fix this mistake?

I opened two terminals.
One with php artisan websocket:serve
The second with php artisan serve

@MrEduar have you found a way using SSL with laragon

We have the same problem using Laravel Valet (for Linux). It works like a charm with Chromium, no way to get it working with Firefox. We spent hours and hours on this. Good luck. :)

in my case when i set PUSHER_APP_PATH facing this issue so removed. still don't understand what is the problem.

PUSHER_APP_PATH

Where you put it?


[Bug]: different format in function  string.toLocaleString('pt-BR', { style: 'currency', currency: 'BRL' }) comma instead of dot in thousands of places

Bug description
using a string.toLocaleString('pt-BR', { style: 'currency', currency: 'BRL' }) is getting me commas instead of dots in the thousands place. I use puppeteer with ejs, can someone help me with this little problem?
This error started to appear after I updated the dependencies, I don't remember which version it was in before.
Puppeteer version
6.14.6
Node.js version
v12.18.4
npm version
6.14.6
What operating system are you seeing the problem on?
Linux, Windows
Relevant log output
No response

We no longer support Node 12, please try this again with the latest version of Puppeteer and Node 14+.


Update README, Add Makefile and minor tweaks

Update documentation. Describe how to use and build the images.
Add a Makefile to build the artefacts
Add .gitignore
Minor tweak to init-lcow and updated package

minor thing but otherwise LGTM


Fix dry-validation on ruby < 2.4

Dry-validation 0.13.1 dropped support for rubies less than 2.4 in
https://github.com/dry-rb/dry-validation/commit/451af83cc0a0e4943ed33f5205d534b56707f2cd
which was released in 0.13.1.
This is causing all of the providers to fail travis on ruby 2.3.8, e.g. https://travis-ci.org/ManageIQ/manageiq-providers-lenovo/jobs/510453001

cc @Fryguy

Hm bundler seems to be picking up the right version of dry-validation now

So should this be closed then?  Note that @juliancheal is blasting out changes to the supported Rubies, and 2.3 is not on the list, so maybe we can ignore this?  Thoughts?

Yeah if we're dropping 2.3 then there is no need for this.


Stop penalising forums and mailing lists

Until now, Facebook, Slack, and Reddit were always listed above forums, mailinglists, and IRC for a same-sized area. This fails to give a true picture of the OSM community in all but a small number of countries. Furthermore,

Facebook, Slack, and Reddit are closed, proprietary platforms where you can only participate by giving up some of your privacy and we should not over-eagerly promote them;
Facebook and Reddit are proven to harbour the most obnoxious people on the planet, and we have no control over these platforms to exclude people we don't like (whereas we have, and do exert, this control on the forums and mailing lists).

It is ok to list Facebook/Reddit/Slack if the community in a country has chosen to use them, but it is not ok to make the knee-jerk assumption that as soon as there's any Facebook/Reddit/Slack channel in one country, it should automatically be recommended above a forum or mailing list.

Yes this is an open issue in the community index itself, see
https://github.com/osmlab/osm-community-index/issues/114
I'd strongly prefer for local communities to control the sort order of their own entries rather than using hardcoded values in iD.  So anyway, that's the place to fix the issue, not in iD.
I'm not bothering to respond to your other points, but I had a chuckle about where you feel the "most obnoxious people on the planet" spend their time.  Frederik, you are so consistently wrong on so many things that sometimes I feel we're talking about two different OSMs.

I had a chuckle about where you feel the "most obnoxious people on the planet" spend their time

Ummm.... we're talking about reddit here.... The OpenStreetMap reddit (/r/openstreetmap) is pretty good and nice and helpful, I contribute often to it. I've used reddit for 10+ years, it's a great resource.
 Are you really sure you want to defend a site which steps up to protect GamerGate?

@rory This is only about the OpenStreetMap reddit (/r/openstreetmap) (or any other subreddits people might set up for local OSM talk - I don't know of any), and how they might rank relative to other things.
The people there are mostly nice, and there are moderators (spanholz and others) who mostly keep it that way.
Please don't drag the other shitty things that people do elsewhere on Reddit into the discussion.

Update: For the record, I can totally understand why one would want to "demote" IRC & the mailing lists, that's certainly something reasonable people can disagree about, and discuss.

There is a comment in the code saying why we rank them the way we do.  @woodpeck tried to remove it with this PR and replace it with his own opinion.
👉 The point of showing the community index in iD is to let mappers know that there are people around where they have edited that care about the map.  The old post-save screen had some stuff about "share your changes on social media" and put the user first.  The current post-save screen has stuff like "reach out to people around you" and puts the community first.  This was a direct response to the kinds of edits we saw people doing when the Pokemon Go craze first hit OSM.
A potential Pokemon Go vandal or someone who just dropped in to make some play edits and evaluate the project isn't going to be convinced to care about mapping by seeing that there is a mailing list.  They might potentially be converted into a useful mapper by seeing that there is a Meetup or Reddit group and that this is a thing that actual humans can do for fun.
It's worth mentioning too that other apps which use the community-index might use it differently than iD does.  "community" is not just a list of links to show people.

we have no control over these platforms

https://wiki.osmfoundation.org/wiki/FAQ#What_is_the_purpose_of_the_OpenStreetMap_Foundation.3F
What is the purpose of the OpenStreetMap Foundation?
The goal of the foundation is to support but not control the OpenStreetMap project.

Both versions clearly show what @woodpeck and @bhousel value. I don't feel comfortable with either of you being in control of what is shown worldwide. I'd like people to be directed to the channel that is most likely to help them, no further values attached. Changing the sort order on a global level does not fix that, and makes smaller countries a victim of your "geopolitics".

@joostschouppe, thank you for stating that the current situation is undesirable. The issue could be somewhat mitigated by allowing the repository that collects the available channels to indicate a preferred sort order. Of course we'd have to make sure that pull requests to that repository are then handled by someone independent.

I believe on a local level there will be much less contention:

in most cases the choice will be quite obvious (as there is usually one, maybe two, dominant channels)
in most cases the usual power-to-whom-does-the-work will apply (which we usually don't find problematic)
in most cases, in case of conflict the parties will have a more personal relationship and work things out together
It's true that when things do go wrong, it's another chance for the admins to make gutsy decisions. But at least that would be a relatively small decision affecting not too many people. And it wouldn't be as hard to find a solution that makes everybody equally unhappy.

I would prefer to drop the sorting altogether until a better solution is implemented though.


Add support for SECRET words

The WordSearch object can now accept a list of hidden bonus words. These words are included in the letter grid but are segregated or suppressed in the answer key and "find these words" sections.
Hidden words are currently hard-coded to be inserted at Level 3, regardless of base puzzle difficulty.

@duck57, at quick glance, this looks like a neat addition. I'm deep in the middle of rewriting another project right now but will definitely look over this next week. Thanks for your work on this 👍

@duck57, I really like what you've done. This is a feature I don't think I would have ever thought of.
I had a few comments as you can see above. I made the adjustments matching up to the comments (commit 5071ca7) as I had a little free time. Have a look and let me know what you think. Nice work 👍

I've left a few replies above—either tomorrow or next weekend, I'll write a commit that incorporates them and adds some greater flexibility.
Also, when I make this commit, I'll replace the nomenclature of "hidden" with "secret."  All the words are hidden in a word search.  Being hidden isn't what makes the words that are included without being on the list of words to find special—it's that they're excluded from the "find me" list.

I agree that secret makes more sense.

Two other comments before I push a few commits I made this afternoon:

Although I'm reading from tea leaves into your intentions here, it seems that we have different use cases.  Your primary focus seems to be the CLI input > PDF output workflow, while I'm focused on calling the generation engine programmatically.  Is this accurate?  If so, please let me know if I messed up your CLI ergonomics so I can add the new flexability without disrupting the CLI behavior.
In the answer key, the coords are given as (row, column) pairs.  This tripped me up, as it's backward from the (x, y) coordinate pairs I've grown to expect.  Would you like me to swap those numbers in the display or just leave them alone?

Also, I noticed that the description that the printed answer key uses 1-based indexing in the README is inaccurate.  Fix that in the README (say it uses 0-based indices) or in the code (display with 1-based indexing)?

I had/have no intended usage for this. It simply started as a script I needed to complete a bunch of puzzles. After I had it working I thought it would be a good script to learn how to crate a package with so that's where it stands.

The cli was also added because I wanted to learn the process of including a full cli into a pypi package.
PDF, output just seemed logical for this as people would need an easy way to print them out.
I'm mainly just trying to keep it simple. It's just word search puzzles so I didn't want to have too many options are presets that could potentially scare people away from using it.

The api references the grid coordinates (row or y, col or x) because that's how they are accessed programmatically. I know it's opposite of what we all learned in school but storing the key (x, y) would require accessing any coordinate as puzzle[y][x] which just looks weird and is not how I think when programming.

All front facing output (cli and pdf,csv export) should be 1-based and in format (x, y). I've found most people are not familiar with 0-based indexing. All api output is 0-based so that I don't have subtract from the 1-based values for every operation.

It looks like it's outputting the info incorrectly at the moment though so I may have made a boo-boo in one of my latest commits. All of the testing I have built only checks the API so it would catch any errors in the cli or PDF output. I'll need to build testing for that once I get it fixed in the repo.
And please excuse any typos or run-on thoughts. I'm writing this while waiting for a table at a restaurant with a 2 year old 🤦♂

This is excellent work! 👍 I left a few comments above so let me know what you think.

I'm still not sure I understand why anyone would want separate direction settings for regular and secret words... Seems over complex for a word-search puzzle tbh. It's not really harming anything to have it, I would just have to figure out how best to display it on the PDF and CSV output.
I guess it would be best to just combine the possible directions of both types of words but I could see a case where the regular and secret directions don't overlap at all, leaving someone looking for regular words in directions they would never go. Probably a very small possibility that would ever happen though.
And, you obviously have a use case for it, so there is at least one user.

Overall, this is really nice and makes the package way more extensible...

Once, we finalize and merge this in, I can easily add your new features to the cli. I pushed a small update the other day to the cli portion so I can certainly roll this into it.
I'll also need to redo some docstrings and plan to create some tests for the actual visible output (terminal, csv, and PDF)

Thanks for your work on this!

Quickly replying during a break at work.  If I make an in-depth reply (or large commit) during this week, whack me with a stick b/c that means I’m procrastinating.
It looks like you’re actively poking at this right now, so I’ll refrain from doing too much other than pushing a small commit I made to config.py after I finish this post so that we’re not stepping on each other’s toes with duplicate work.  I’ll have time to give an in-depth look at this discussion+your changes either over the weekend or next Monday.
I think I saw a question as to why I’d want the secret words hidden hidden while skimming this thread—part of what inspired me to make the feature in the first place was to share a word search where I embedded our nicknames to a group of friends.  Easter eggs more so than extra content, if that makes sense to you [some of my turns of phrase can be comprehensible to only myself].
Time to push my change and get back to work.

On Oct 3, 2022, at 12:58, Josh Duncan @.***> wrote:
This is excellent work! 👍 I left a few comments above so let me know what you think.
I'm still not sure I understand why anyone would want separate direction settings for regular and secret words... Seems over complex for a word-search puzzle tbh. It's not really harming anything to have it, I would just have to figure out how best to display it on the PDF and CSV output.
I guess it would be best to just combine the possible directions of both types of words but I could see a case where the regular and secret directions don't overlap at all, leaving someone looking for regular words in directions they would never go. Probably a very small possibility that would ever happen though.
And, you obviously have a use case for it, so there is at least one user.
Overall, this is really nice and makes the package way more extensible...
Once, we finalize and merge this in, I can easily add your new features to the cli. I pushed a small update the other day to the cli portion so I can certainly roll this into it.
I'll also need to redo some docstrings and plan to create some tests for the actual visible output (terminal, csv, and PDF)
Thanks for your work on this!
—
Reply to this email directly, view it on GitHub https://github.com/joshbduncan/word-search-generator/pull/17#issuecomment-1265753154, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADYG7CXCHVVNV2HFQROXYITWBMGEVANCNFSM6AAAAAAQTNNHLY.
You are receiving this because you were mentioned.

I completely understand wanting "secret" words I just didn't understand why you would want different sets of directions for regular and secret words. Take your time and checkout what I've done when you can. Thanks!

why I would want different sets of directions

This one I can answer quickly.  When generating Level 1 puzzles, the secret words were far too easy to find when they were also placed according to level 1 rules.

On Oct 3, 2022, at 15:41, Josh Duncan @.***> wrote:
I completely understand wanting "secret" words I just didn't understand why you would want different sets of directions for regular and secret words. Take your time and checkout what I've done when you can. Thanks!
—
Reply to this email directly, view it on GitHub https://github.com/joshbduncan/word-search-generator/pull/17#issuecomment-1265944526, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADYG7CUZRD56RWSZOYNN543WBMZHZANCNFSM6AAAAAAQTNNHLY.
You are receiving this because you were mentioned.

While I haven’t had time to give it a full review, I did see that you added a way to handle the display of word searches that contain only secret words. Good catch.
This message is also a reminder to myself to try generating a search containing ONLY secret words when I get time to do a proper review (and write a test to assert that they are valid to create, if one does not already exist)

Yep, I think it's ready. I'm going to clean up some of the docstrings and get it merged in. Thanks for your great work on this!

Hey, I added support to the cli for:

setting difficulty (-d, --difficulty) which accepts either a level number or directions

you can't call -l and -d as they are now in a mutually exclusive group
I'm main keeping -l around for backward compatibility

changed the flag for secret difficulty to -xd

Made a slight adjustment to the validate_level() function.
def validate_level(d) -> DirectionSet:
    """Given a d, try to turn it into a list of valid moves."""
    if isinstance(d, int):  # traditional numeric level
        return validate_level_int(d)
    if isinstance(d, str):  # comma-delimited list
        # check if the provided string is actually a level int
        if d.isnumeric():
            return validate_level_int(d)
        else:
            return validate_direction_iterable(d.split(","))
    if isinstance(d, Iterable):  # probably used by external code
        return validate_direction_iterable(d)
    raise TypeError(f"{type(d)} given, not str, int, or Iterable[str]\n{d}")

def validate_level_int(n) -> DirectionSet:
    try:
        return config.level_dirs[int(n)]
    except KeyError:
        raise ValueError(
            f"{n} is not a valid difficulty number"
            + f"[{', '.join([str(i) for i in config.level_dirs.keys()])}]"
        )

This allows the cli -d argument to just pass through as a string, keeping the validation out of the cli. I did it this way because it also has the nice side effect that if a user of the API passes a level numeric value inside of a string it won't throw an error it just catches that using the isnumeric() method, processes it as an int and moves on.
Created testing for the new options too!
Let me know if you are good with these changes and I'll get this merged in. I'll update the docstring, docs, and changelog on the main branch once merged.

I've actually changed my mind on this. I'm going to combine -l and -d into one argument and validate the input using argparse. This will keep the cli backward compatible but elemental the needs for the mutually exclusive argument flags.

@duck57, the revisions to the cli have been made. I will merge this over the weekend unless you have any objections.

When generating a search from the CLI with only hidden words, it errors out because no words are provided.  Did we decide if this was the intended behavior?

word-search -x "this is a test post of only secret words and duplicate words"

I forgot to implement that. Won't take but a min to fix.

@duck57 it's fixed!

I'm going to make a few small changes after this gets merged and that will be part of them.

Agree with A.
Chris
On Oct 14, 2022 at 11:31 AM -0400, Josh Duncan @.***>, wrote:

@joshbduncan commented on this pull request.
In src/word_search_generator/init.py:

@@ -33,12 +37,19 @@ def init(
level (Optional[int], optional): Difficulty level. Defaults to None.
size (Optional[int], optional): Puzzle size. Defaults to None.
"""

   self._clear_solution: Puzzle = []

@duck57, I just saw this particular and agree. I like the '' option so which of the following do you prefer?
Option A (prepended): Answer Key: REGUALR E @ (2, 12), WORDS S @ (12, 1), ZEBRA E @ (4, 11)
Option B (appended): Answer Key: REGUALR E @ (2, 12), WORDS S @ (12, 1), ZEBRA E @ (4, 11)
Option C (appended after start): Answer Key: REGUALR E @ (2, 12), WORDS S @ (12, 1), ZEBRA E @ (4, 11)
I prefer A myself...
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@duck57, one last thing... I'm updating the README with all of the new changes and I'm noticing we are using a few terms to reference the puzzle difficulty (which I could see being slightly confusing). This is because we have combined the old preset numeric levels with your new directions objects which I think is the right solution, I just wonder then if we should change the property name from 'valid_directions' to just 'directions'? It's shorter, says exactly what it holds, and just looks cleaner in my opinion. It's a simple fix, that I can knock out today with the other small updates and get this merged in. Let me know what you think.

Would it be renamed to directions and secret_directions?
(Plus, in retrospect, "available" would be a better prefix than "valid")

@duck57, I think the two properties for direction should be 'directions' for standard "non-secret" words and 'secret_directions' for "secret" words.
Honestly, we are kind of in a weird place with levels, directions, and difficulty. Since we are keeping levels (which are really just directions) around for backward compatibility, I think just 'directions' makes the most sense for that property.
My other thought is to create an all-encompassing method called difficulty or set_diffifulty. For now, it would just accept either a level or directions but could easily be expanded later to accept other parameters that could define the difficulty.

I'm not even sure what those others parameters could be but I'm certain we'll come up with something in the future.

This would allow valid_directions (or directions) to be a "getter-only" property that the user doesn't have to interact with helping with the confusion. If someone still needs to use level it's there but we would only promote the difficulty method going forward and in the readme.
def difficulty(self, level, directions, secret_directions):
    ...

While updating the README (the only real docs), I'm trying to look at this API as a newbie. We are in the weeds so we know what all of these properties mean, I just think it could be confusing at first glance from a user...
Thoughts?

directions and secret_directions are just fine as far as nomenclature is concerned.
In your proposed set_difficulty function, how would someone passing in both a numeric level and a set of Directions be handled?
[Also, will the secret words be directions-only, or will they also accept level presets?]
README-wise, perhaps it would be best to explain that the numeric levels are simply predefined sets of Directions and that passing level=1 is the same as sending in directions={Direction.E, Direction.S}

I'm going to go with just removing 'valid' for now. No need to overcomplicate this PR as it's already a lot. And secret_directions already accepts either numeric levels or cardinal directions.

Good choice. I’m going to be on the road for the next few hours, so I wouldn’t be able to give you timely feedback if you wanted a quick implementation suggestion.
Chris
On Oct 14, 2022 at 4:05 PM -0400, Josh Duncan @.***>, wrote:

I'm going to go with just removing 'valid' for now. No need to overcomplicate this PR as it's already a lot. And secret_directions already accepts either numeric levels or cardinal directions.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@duck57, I didn't really make it clear in the commit notes but the reason I changed words and secret_words to private properties with accompanying getters was to keep users from making adjustment to both sets.
Before when they were public properties and just regular sets, users could act on those sets using normal set methods like add and update, the problem was that the WordSearch class didn't recognize these changes so the words would be in the list but not in the puzzle unless the user specifically called the _reset_puzzle method. Modifying the sets also bypassed the word cleanup functions allowing bad things to be inserted.
Maybe in the future I'll create word and words classes to handle this but for now making them private and only providing a getter means the user can't change the sets without using the add_words, remove_words, and replace_words functions.

@duck57, I've got the Word class fully implemented. As you'll see there were a lot of changes made to make it work but I think it's much cleaner. There may be a few straggling things that need to be removed that aren't being accessed anymore but it's passing all tests and coverage is 100%.
A few key notes:

All puzzle words are now stored in the .words property (even if they weren't placed on the board)

Now if a word didn't fit when the puzzle was created it may fit if attributes of the puzzle are changed
Allowed me to clean up the add_words, remove_words, and replace_words methods since we are now working with a simple set of Word objects

All word lists and keys are generated on the fly from the .word property
Word class stores the position, position_xy, direction, key_string, key_json and more.

Also includes custom hash and equal functions for add for easy comparison

There was a lot more too but it is late and I can't remember it all now. I may add more detail to this tomorrow if I have time.
Please let me know your thoughts. Cheers ✌

I like this approach, especially for CLI use.  Adjusting the puzzle and emitting an error seems to be a better “do what they mean” than miscounting a puzzle size of 6 when the shortest word has 7 letters causing the program to be obstinate and refuse to generate a puzzle.
That said, I wouldn’t consider it to be unreasonable for the program to halt if the shortest word is close to twice the puzzle dimension (but it’s probably not worth the extra code to check for that case)
Chris
On Oct 21, 2022 at 1:10 PM -0400, Josh Duncan @.***>, wrote:

@joshbduncan commented on this pull request.
In src/word_search_generator/generate.py:

 if not size:

   longest = max(10, len(max(words, key=len)))

   # calculate multipler for larger word lists so that most have room to fit

   multiplier = len(words) / 15 if len(words) > 15 else 1

   size = int(longest + level * 2 * multiplier)

   longest = max(10, longest_word_length)

   # calculate multiplier for larger word lists so that most have room to fit

   multiplier = len(all_words) / 15 if len(all_words) > 15 else 1

   # level lengths in config.py are nice multiples of 2

   l_size = log2(len(level)) if level else 1  # protect against log(0) in tests

   size = round(longest + l_size * 2 * multiplier)

else:

   if size < shortest_word_length:

@duck57, what are your thoughts on this approach? For example, if the user specifies a puzzle of size 5 but provides a word list with the shortest word being 6 characters long, obviously none of the words will fit into the puzzle. So instead of just throwing an exception, I adjust the puzzle to fit the smallest word and then output a notification to stderr about the change.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@duck57, ok I'm done making any changes for now. There are a few things I want to tidy up later but they have no real interaction with your shape masks plan and can wait.

@duck57, if you are good with where we are now, I will get this all merged into the main branch.

I think it's ready to go.

Good catch on the markdown end of line spacing. I've been needing to change my VSCode settings for ever but can never remember. It strips those out every time I save. My daughter turns two this weekend so it may be Monday before I get this merged in. Thanks again for your work on this 👍

@duck57, for some reason an entry point test is failing on Windows now. Who knows why but I'll try and get it figured out today. It failed on your commit and my latest. BTW, I had someone ask last week about using this package on Google collab which is still on python 3.7 so I updated the typing to allow this to run all the way back to 3.7.

@duck57, so after a lot of digging it seems the "≤" you used in the small change to the help menu in the cli size parser isn't included in windows so it breaks the cli tests. I'm just going to "<=" so we can move on.


Release 3.0.1

Coverage decreased (-7.0e-05%) to 95.458% when pulling 05d5838d144399c82b87204c358ea5e7f9a3b841 on Release-3.0.1 into 08ee745442afeca4fe471ce24afd93c0ff717bdc on master.


Fix subresource update logic.

Signed-off-by: Ville Aikas<EMAIL_ADDRESS>
Changes
While working on: https://github.com/sigstore/policy-controller/pull/88 I noticed that subresources are not being correctly handled.
🐛 Fix a bug where subresource was not correctly set when doing webhook validation.

/kind bug

Fixes #

Release Note

Fix a bug where subresource updates were being ignored.

Docs

fixes: https://github.com/knative/pkg/issues/2184
/lgtm
/approve


Kavanoz asks for androguard 3.3.5 but Quark requests androguard 3.4.0a1

Your requirement file asks for androguard==3.3.5, which is incompatible with another tool Quark Engine. While I agree it's not really your business to be compatible with other tools, actually it seems to me that Kavanoz works fine with Androguard 3.4.0a1, so you can probably modify the requirement file to ask for >=3.3.5.
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
quark-engine 23.9.1 requires androguard==3.4.0a1, but you have androguard 3.3.5 which is incompatible.

Done!


fileLink not allowed by Schema

Hello everyone,
I'm trying to use Simple Schema in my current Meteor React project but for some reason I can't get it to work.
This is my schema:
Comments.schema = new SimpleSchema({
  city: {
    type: String,
    label: 'The name of the city.'
  },

  person: {
    type: String,
    label: 'The name of the person.'
  },
  location: {
    type: String,
    label: 'The name of the location.'
  },
  title: {
    type: String,
    label: 'The title of the comment.'
  },

  content: {
  type: String,
  label: 'The content of the comment.'
  },

  fileLink: {
  type: String,
  regEx: SimpleSchema.RegEx.Url,
  label: 'The url of the file.'
  },

  createdBy: {
  type: String,
  autoValue: function(){ return this.userId },
  label: 'The id of the user.'
  }
});

And this is my insert:

  createSpark(event){
    event.preventDefault();

    const city = this.city.value;
    const person = this.person.value;
    const location = this.location.value;
    const title = this.title.value;
    const content = this.content.value;
    const fileLink = s3Url;

    insertComment.call({
      city, person, location, title, content, fileLink
      }, (error) => {
        if (error) {
              Bert.alert(error.reason, 'danger');
          } else {
              target.value = '';
              Bert.alert('Comment added!', 'success');
          }
      });
    }

I'm saving the value I get back from amazon in a global variable called s3Url. I am able to console.log this variable without a problem but when I want to write it to the database I am getting a "fileLink is not allowed by schema" error.
Anyone see what I am doing wrong?

There aren't any obvious issues with what you posted. It might be that you attached the wrong schema or some other user error.


Add background/fill color for outline icons

There are various icon packs like lucide_icons which only supply outlined icon which is good, but If I want a filled star or a liked heart(filled) then it won't be possible with bare flutter.
If we can fill those outlined icons then this would become a very useful package as we can already add borders to an icon.

While I understand the interest for such a feature, I don't think it is realizable without re-implementing entirely the way RichText is painted. As mentionned in the Flutter Icon widget documentation:

This widget assumes that the rendered icon is squared.

Which means that it is not aware of the icon's real shape. I've tested by using the backgroundColor property of TextStyle and this is the result:

As you can see the background is rendered inside a square without consideraing the shape of the icon and the TextStyle API does not provide a way to clip or customize the path of the background.

How do you draw the border then?


missing product name/hyperlink in a collection

One of the reviews in https://freeyourstuff.cc/view/amazon/5716d1408708521e387a83e7 ("Sheila Shine", I gather from the text of the review) doesn't have the name of the product in the Product column -- it's blank -- and thus there's also no link to the thing being reviewed. Import error?

Thanks for noticing that! Amazon.com sometimes removes product listings, but still keeps the reviews attached to their product ID. So you end up with productless review pages like this:
https://www.amazon.com/gp/review/R3DFFJTX6HZI5T
As far as I can tell, there's no reference to the original product anywhere - let me know if you find anything! Incidentally, a reason to backup one's reviews .. ;-)

Closed for now as issue appears to be on Amazon's end, per above.


[FALSE-POSITIVE]

Hello Phishing Database,
This is Hari Prakash, Developer of Thisisthrive.com
We have Found a Phishing attack in the Platform "VirusTotal", where I found the Phishing Error. Previously, there is Malware present on the website, Now We have rectified all the Files in Thisisthrive.com. All our Files are Clean and the Website looks Healthier in Google Webmasters as it Highlightsed as Error-free (Tested with Security and Manual Actions). We have removed all the Malware and other unhealthy Pages now. As a leading Security Vendor, I kindly request Phishing Database to make our website "Blacklist-free" on your Platform.
Error Link: https://www.virustotal.com/gui/url/d19049a6e73e2ac1f9d1f8c126427ff93bb36bd6e6a22ac8e6d2081a5640f968
I kindly request you to reconsider the website and make it as Listed. That would be very helpful, for us and business if you do the needful.
Company Description: We're in the business of supporting personal and professional development. Our mission is to create a work environment where all employees can thrive, both personally and professionally. We do this by offering training and coaching in areas such as leadership, communication, teamwork, and resilience. We also developed the Resilience Quotient Inventory (RQi), the most comprehensive psychometric measure of resilience available anywhere in the world.
Regards
Hari Prakash

Hello Mitchell
But Still, the URL is Marked as Phishing, Can You Please Check it.
Error URL: https://thisisthrive.com/covid
Error Source: https://www.virustotal.com/gui/url/d19049a6e73e2ac1f9d1f8c126427ff93bb36bd6e6a22ac8e6d2081a5640f968?nocache=1


SocketTransport: Remove rebind workaround?

Can  this workaround removed since https://github.com/dotnet/corefx/issues/24562 has been fixed since?

@drieseng thanks for the catch! Would you be interested in sending a PR?


Add an explicit platform parameter to the kf_is_ready_test.py

For GCP blueprints we no longer provide a KFDef file so we need some
other mechanism to tell it that the test is running on GCP and
to invoke GCP specific tests.

Related to kubeflow/gcp-blueprints#74 and kubeflow/gcp-blueprints#73

ISTIO telemetry, tracing, and prometheus are no longer included in
the default profile.

/assign @Bobgy

/lgtm

/approved

/approve


Hotfix develop - Silence output on no errors

Please merge #170 first, also see #170 for the description of why the tests are failing here.
Silences error output when no warnings or errors are present in linted files. Also improves the handling of writing output to the file system with completion/error messages but no error thrown.
closes #141
DCO 1.1 Signed-off-by: Dan Purdy<EMAIL_ADDRESS>

Will close for the time being.

Don't know why i ended up opening this again.. Should remain closed until the master hotfix is merged

Update this and I'll merge.

I know what the errors will be here, it's a consequence of merging in the silence output on no errors work in #171 and #170 will update later on.

This all looks good to me, just need the merge conflict resolved

@Snugug @bgriffith it's good to go.


update member flow logic

I made two changes here:

On Edition, the sign up form is present even when members are disabled in the admin. I wrapped the form in a conditional block that checks for @site.members_enabled. A wrinkle here is that someone who has the site in invite-only mode also won't want this shown, so I also added a conditional for @site.members_invite_only
The login button also appears when members are disabled. I check for @site.members_enabled and then enable/disable accordingly.

Ref #154 There is also a discussion about Journal, which I'll also take a look at.
{{#if @site.description}}
            <div class="cover-description">
                {{#if @custom.email_signup_text}}
<EMAIL_ADDRESS>                {{else}}
<EMAIL_ADDRESS>                {{/if}}
            </div>
 {{/if}}

This code is also included. Here, the custom email signup text could still be shown, even when members are disabled. We could also wrap this in a conditional, but I think the easier solution is to just to leave this custom field blank in the Admin.
References this Forum post: https://forum.ghost.org/t/editon-theme-bug-on-home-page/32176

Is there a way for us to add automated tests to catch regressions?


Solving issue #1 (adding musical notes)

The sounds still sound like individual frequencies...... I can't merge this PR

Have a look at Hyperplexed's Video, in the README. If you manage to fix this before 10 I'll definitely merge it 👍

@Shaatvika take a look at this codepen https://codepen.io/Hyperplexed/pen/XWxqgGE


Detox test hangs sometime on CI

Description
My test cases run fine most of the times, but some times oddly it just can't run tests at all. It works fine on my local always. I tried to put trace mode on to see what exactly was going wrong and logs attached below just keep on repeating. If I just start it all over again, the issue won't repeat and tests go just fine. Any ideas on what could be messing up here

[x] I have tested this issue on the latest Detox release and it still reproduces

Expected behavior
Test should just run fine every time
Environment (please complete the following information):

Detox: 18.7.0
React Native: 0.63.2
Node: 12
Device: iPhone 11 Pro
Xcode: 12.1
iOS: 14
macOS:  10.15.7

Logs
Device and verbose Detox logs

[x] I have run my tests using the --loglevel trace argument and am providing the verbose log below:

detox[16880] INFO:  [actions.js] The system is busy with the following tasks:
Dispatch Queue
⏱ Queue: “Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)” with 3 work items
Run Loop
⏱ “Main Run Loop”
UI Elements
⏱ 2 views awaiting display
⏱ 3 layers awaiting layout
⏱ 12 layers awaiting display
detox[16880] TRACE: [AsyncWebSocket.js/WEBSOCKET_SEND] {"type":"currentStatus","params":{},"messageId":509}
detox[16880] TRACE: [DetoxServer.js/MESSAGE] role=tester action=currentStatus (sessionId=f34922c9-14ed-3803-5c17-284782d6a344)
detox[16880] TRACE: [DetoxServer.js/MESSAGE] role=app action=currentStatusResult (sessionId=f34922c9-14ed-3803-5c17-284782d6a344)
detox[16880] TRACE: [AsyncWebSocket.js/WEBSOCKET_MESSAGE] {"params":{"messageId":509,"status":"The system is busy with the following tasks:\n\nDispatch Queue\n⏱ Queue: “Main Queue (<OS_dispatch_queue_main: com.apple.main-thread>)” with 3 work items\n\nRun Loop\n⏱ “Main Run Loop”\n\nUI Elements\n⏱ 2 views awaiting display\n⏱ 3 layers awaiting layout\n⏱ 12 layers awaiting display"},"messageId":509,"type":"currentStatusResult"}

@saransh-malik seems there's an issue with your app, perhaps a race-condition that keeps it from loading. It doesn't seem like an issue with Detox (rather, Detox seems to report the status quite clearly).


Feature/fix perlcritic

Requirements

Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion;
Review the contributing guidelines for this repository; remember in particular:

do not modify code without testing for regression
provide simple unit tests to test the changes
if you change the schema you must patch the test databases as well, see Updating the schema
the PR must not fail unit testing

Description
Using one or more sentences, describe in detail the proposed changes.
Change perl critic severity from 3 to 4 and address all perl critics complaints
This includes adding missing PODs for parsers
Use case
Describe the problem. Please provide an example representing the motivation behind the need for having these changes in place.
We want a test suite that passes when no changes are made, so that any failure can be traced back to the latest changes that break it
Benefits
If applicable, describe the advantages the changes will have.
A more usable test suite
Possible Drawbacks
If applicable, describe any possible undesirable consequence of the changes.
Perl critic still fails, although it does not say why. Any suggestions as to what is missing would be welcome.
Perl critic fails horribly when coveralls is false for some wrong version of a library.
The test suite still fails outside of critic because one test case is being fixed in a separate PR, and checksum_xref started failing some while ago but I cannot figure out what is causing this.
Critic now only checks severity 4 and not 3. But we have been failing at 3 for a long while now.
Testing
Have you added/modified unit tests to test the changes?
No changes needed
If so, do the tests pass/fail?
A bit of both
Have you run the entire test suite and no regression was detected?
Ran the whole test and it is failing, as it was before, so we're not worse off that we were before

It's because, the test is generating 4 additional "no unexpected warnings" after the one triggered by done_testing(). and their output is emitted after that one which is not expected by 'prove'.

Ok, I've removed one import from the test and it does pass with prove as well.


Do not parse json-seq as json

There's an odd mimetype json-seq which is a delimited series of JSON
objects (see RFC 7464).
This format is not parseable JSON, so isJSON('application/json-seq')
should return false.

Thank you


jhack could not get current model

It seems that jack has a problem finding the name of the current model. I have seen this error with multiple commands.
x1:➜  ~ jhack fire ubuntu/0 update-status
Traceback (most recent call last):
  File "/snap/jhack/135/bin/jhack", line 8, in <module>
    sys.exit(main())
  File "/snap/jhack/135/lib/python3.8/site-packages/jhack/main.py", line 140, in main
    app()
  File "/snap/jhack/135/lib/python3.8/site-packages/typer/main.py", line 214, in __call__
    return get_command(self)(*args, **kwargs)
  File "/snap/jhack/135/lib/python3.8/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/snap/jhack/135/lib/python3.8/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/snap/jhack/135/lib/python3.8/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/snap/jhack/135/lib/python3.8/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/snap/jhack/135/lib/python3.8/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/snap/jhack/135/lib/python3.8/site-packages/typer/main.py", line 500, in wrapper
    return callback(**use_params)  # type: ignore
  File "/snap/jhack/135/lib/python3.8/site-packages/jhack/utils/simulate_event.py", line 191, in simulate_event
    return _simulate_event(
  File "/snap/jhack/135/lib/python3.8/site-packages/jhack/utils/simulate_event.py", line 122, in _simulate_event
    env = _get_env(
  File "/snap/jhack/135/lib/python3.8/site-packages/jhack/utils/simulate_event.py", line 52, in _get_env
    "JUJU_MODEL_NAME": current_model(),
  File "/snap/jhack/135/lib/python3.8/site-packages/jhack/helpers.py", line 187, in current_model
    return next(filter(key, all_models)).strip("*")
StopIteration                                                                                [1.66s]

x1:➜  ~ juju models
Controller: u1

Model        Cloud/Region  Type  Status     Machines  Units  Access  Last connection
controller   u1-lxd/u1     lxd   available         1      -  admin   just now
default      u1-lxd/u1     lxd   available         0      -  admin   2023-01-20
juju-spell*  u1-lxd/u1     lxd   available         2      4  admin   4 seconds ago
                                                                                [1.02s]
x1:➜  ~ snap info jhack
name:      jhack
summary:   Make charming charming again.
publisher: Pietro Pasotti (ppasotti)
store-url: https://snapcraft.io/jhack
contact<EMAIL_ADDRESS>license:   unset
description: |
  An opinionated collection of scripts and utilities for charmers.

  In order to use the cli tools that hit the juju api, you'll need to connect the
  dot-local-share-juju interface.

  Command: `sudo snap connect jhack:dot-local-share-juju snapd`

  Jhack needs that interface to obtain WRITE access to `~/.local/share/juju`, which is the folder
  where your local juju client stores its state, including:
    - cloud credentials
    - what controllers are registered, which controller is current
    - what models are present on each controller, which model is current

  If you see errors like:

      ERROR cannot load ssh client keys: open /home/pietro/.local/share/juju/ssh: permission denied
      No relations found in model None.

  Then you probably forgot to connect that plug.
commands:
  - jhack
snap-id:      gnxWJ9Sdlew4qfduWHEW8oczvdo2mvTT
tracking:     latest/candidate
refresh-date: today at 10:13 CET
channels:
  latest/stable:    0.3.2 2022-11-02 (120) 99MB -
  latest/candidate: 0.3.4 2023-01-02 (135) 99MB -
  latest/beta:      0.3.4 2023-01-02 (135) 99MB -
  latest/edge:      0.3.7 2023-01-25 (166) 99MB -
installed:          0.3.4            (135) 99MB -                                                                                [0.27s]

the get_models code is very messy either way, I'm busy cleaning it up in #49

This should be fixed by #49. Could you please try again and let me know if there's still an issue?

I tried to install latest/edge and it seems working fine. I hit another issue, but I think it's because I'm using juju < 3.


fix(usager): tickets 68 61 62 63 64  65

:tada: This PR is included in version 0.1.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Is there restriction in custom dataset image size?

Is there restriction in custom dataset image size?
Can I use any size of image for custom dataset?

The only restriction is your GPU memory. Of course you may need to choose hyper parameters according to the image size.

The only restriction is your GPU memory. Of course you may need to choose hyper parameters according to the image size.

hi, hellock,  can you give me some ideas about hyper parameteres related to image size?


Add "Website Visitor" Widget in Footer

Is your feature request related to a problem? Please describe.
The current website does not display the number of visitors it has received, which could be useful for tracking engagement and performance metrics.
Describe the solution you'd like
I would like to add a "Website Visitor" widget in the footer of the website that shows the number of visitors so far. This widget will update in real-time or upon page refresh to provide an accurate count of the total visitors.
Describe alternatives you've considered
An alternative could be using a third-party service like Google Analytics for more detailed visitor statistics, but it does not provide a simple, on-page visitor count.
Demo Video/Screenshot (Mandatory )
Preview of proposed Website Visitor widget:

Are you contributing under any open-source program ?
Please assign this issue to me under the gssoc label

@rohitinu6 u are assigned


Adds a method to supply a context to the db.client

Needed to add this to use this library on google app engine. Simply gives an option to set a context to a Dropbox option, in my case the context being from appengine.NewContext(request). Personally I think they're should also be an option to provide a full http.Client to the dropbox client similar to how its done in "google.golang.org/api/drive/v2".

Thank you.


Add license information

Hello!
I found link to this project from https://hackaday.com/2021/04/08/18650-brings-esp8266-wifi-repeater-along-for-the-ride/
Could you please add information about the license of this repository — is it allowed to copy, change and use the code in any purpose?
It would be great to see any popular open source license.

done.

MIT — great!
@martin-ger, thank you!


Add Support for the Floor Division Operator (//)

At least for the Minify mode.
local x = 10 // 5
print(x) --> 2

1:21: Unexpected symbol. Symbol /

Compound:
local x = 10
x //= 2
print(x) --> 5

2:5: `=` expected.

Sources:
https://luau-lang.org/syntax#floor-division-
https://devforum.roblox.com/t/luau-recap-october-2023/2685332#floor-division-1

Added this in the latest publish (1.5.0).


Use apiBase for regional data hosting?

Describe the bug
Not sure if it's still a bug, but rather wanted to clarify whether it's possible to use the api_base correctly with react-use-intercom before I start trying to use the library?
https://github.com/devrnt/react-use-intercom/pull/96#issuecomment-1377103945
there are two comments on this MR that sound like others that wanted to use "https://api-iam.eu.intercom.io" but it didn't work for them and they ended up not using this library?

Please don't create an issue with a question. This module is still working as expected. If the underlying functionality is not working please ask this to the Intercom support.
See https://developers.intercom.com/installing-intercom/docs/basic-javascript

ok, thanks for the quick reply! for future reference (and others that might be reading along): where would you prefer that people ask questions instead of here? :)

Prefer using "Q&A" in Discussions


System bell causes XRDP to hang

Any time I trigger the system bell [eg: double-tap tab in bash-completion] my XRDP session hangs while the sound plays. It doesn't matter if I mute everything at every possible level, the bell comes through as a very low bass noise and the session hangs until it completes. If several are triggered quickly I have to wait for every single one to play out before the session starts responding again.
OS: Fedora 29
Packages:

xorgxrdp.x86_64 0.2.9-3.fc29
xrdp.x86_64 1:0.9.10-1.fc29

I have the same issue and "xset b off" helps me as a workaround.

Thanks @vladrich, that is an excellent bandaid.

I can't reproduce this on a later development build, either with or without pulseaudio enabled.
I'm closing it for now. If it's still current, feel free to open another issue.

Yeah I just checked it on my system and it's no longer an issue.
Tough to recall when I stopped having to xset b off on restart, but I feel like it was fairly recently. I want to say that it might have been around the time I upgraded to Fedora 35 or 36?

Last change I can find in this area is 87c89f0aa28f68fb1599bd97b9b7bde5c258d25b which made it into v0.9.16. That went into F35, so maybe that's it.


Support for Rails API

Any plans or discussion for being able to support Rails API mode in the future?
Biggest change seems to be adding a respond_to? for helper_method as ActionController::API doesn't have that func.

I would likely accept a PR that did this.

The was done in #748


Exclude interactions for self dns records in wildcard mode

If you run a dedicated interact-sh server, and then attach to this server interact-sh client, client show all request (include ns1.domain.com, etc)
Please add flag to show only generated domain in client part

@kiriknik just to be sure, you were running the server in -wildcard mode, right?

Yes - to check all domains)
maybe you can add flag (like --show-only-registered) - to show only generated domain?)

@ehsandeep -wildcard seems to be working as expected here. I think a better option would be adding --show-only/match/filter *.xxxx.yyy.zzzz,*.aaa.bbb. What do you think?

@Mzack9999 updated the issue with the suggested flag and example.


[to v16] First steps to proper JSON.Parse and JSON.Stringify in the world of C#.

Fixes #98 and #1306.
Could also help with #1192 and #1432 once some other issues are fixed, which are mentioned in comments in the code.

Hi @TriEdgeAI,
Thank you for the implementation of JSON parsing that is very useful thing.
We are planning to include your feature into next Bridge 16.0.
A new branch v16 created for 16.0 release.
Can you please create a new Pull Request to be merged into branch v16.

Awesome! Thanks! I'll have time to do it in a few days.

#2043 has been fixed

Hi @TriEdgeAI, the following issues has been fixed for 15.7 release and merged into v16 branch:
#2050
#2051
#2052
#2056

Awesome! I'll see how I can improve the JSON methods based on that :)

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: TriEdgeAI:x: Vladimir AngelovVladimir Angelov seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.

I'll remake this pull request, because I've messed up my fork by committing with multiple emails.


File download to WSl disto

Is your feature request related to a problem? Please describe.
I try to download a file from edge on Windows and I am choosing where to save the file. I am unable to directly save the file inside WSL distro. I have to save the file in local partition and then put the copy paste the file into WSL distro using windows file explorer,
Describe the solution you'd like
I want to be able to directly download a file into WSL distro.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Type \\wsl$ in the File name: dialog and navigate to your distro and path inside the distro. For example, a save-link-as on WSL's README.md below.