If exactOptionalPropertyTypes: true, undefined is not allowed when using withDefault

Environment
Operating System: Darwin
Node Version: v18.0.0
Nuxt Version: 3.4.1
Nitro Version: 2.3.3
Package Manager<EMAIL_ADDRESS>Builder: vite
User Config: -
Runtime Modules: -
Build Modules: -
IDE: VSCode 1.77.3
volar 1.2.0
Reproduction
https://stackblitz.com/edit/github-6rhv3z?file=components/Hoge.vue
Describe the bug
If exactOptionalPropertyTypes is set to true in tsconfig, then props implementations using withDefault will get an error when adding undefined to the type.
const props = withDefaults(
  defineProps<{
    hoge?: string | undefined;
  }>(),
  {
    hoge: undefined,
  },
);

The following error occurs
Argument of type '{ hoge: undefined; }' is not assignable to parameter of type 'InferDefaults<Readonly<Omit<{ hoge?: string | undefined; }, never> & {}>>' with 'exactOptionalPropertyTypes: true'. Consider adding 'undefined' to the types of the target's properties.
  Types of property 'hoge' are incompatible.ts(2379)

For now, we are using @ts-ignore or modifying the runtime declaration, but we would like to write it in type-based format if possible.
Additional context
No response
Logs
No response

This is an upstream vuejs/core issue: https://github.com/vuejs/core/issues/6532


Crash with nouveau in gbm_bo_destroy

With latest sources, swaymsg exit consistently crashes:
#0  0x00007f739fdc93fc in  () at /usr/lib/libgbm.so.1
#1  0x00007f73a06b9475 in buffer_destroy (wlr_buffer=0x564f90f46a70) at ../subprojects/wlroots/render/gbm_allocator.c:58
        buffer = 0x564f90f46a70
#2  0x00007f73a06f3dfb in buffer_consider_destroy (buffer=0x564f90f46a70) at ../subprojects/wlroots/types/wlr_buffer.c:26
#3  0x00007f73a06f3e55 in wlr_buffer_drop (buffer=0x564f90f46a70) at ../subprojects/wlroots/types/wlr_buffer.c:36
        __PRETTY_FUNCTION__ = "wlr_buffer_drop"
#4  0x00007f73a06bd350 in slot_reset (slot=0x564f90dfeba8) at ../subprojects/wlroots/render/swapchain.c:43
#5  0x00007f73a06bd3af in wlr_swapchain_destroy (swapchain=0x564f90dfeb40) at ../subprojects/wlroots/render/swapchain.c:52
        i = 2
#6  0x00007f73a06c6ea3 in finish_drm_surface (surf=0x564f90009db8) at ../subprojects/wlroots/backend/drm/renderer.c:106
#7  0x00007f73a06c7352 in drm_plane_finish_surface (plane=0x564f90009db0) at ../subprojects/wlroots/backend/drm/renderer.c:194
#8  0x00007f73a06c3f28 in dealloc_crtc (conn=0x564f90edf5c0) at ../subprojects/wlroots/backend/drm/drm.c:1072
        drm = 0x564f90006ce0
#9  0x00007f73a06c3d5e in drm_connector_destroy_output (output=0x564f90edf5c0) at ../subprojects/wlroots/backend/drm/drm.c:1015
        conn = 0x564f90edf5c0
        mode = 0x564f8f7df2e0
        mode_tmp = 0x0
#10 0x00007f73a070a456 in wlr_output_destroy (output=0x564f90edf5c0) at ../subprojects/wlroots/types/wlr_output.c:393
        cursor = 0x564f90edf800
        tmp_cursor = 0x564f90edf800
#11 0x00007f73a06c5e70 in disconnect_drm_connector (conn=0x564f90edf5c0) at ../subprojects/wlroots/backend/drm/drm.c:1565
        __PRETTY_FUNCTION__ = "disconnect_drm_connector"
#12 0x00007f73a06c5eb8 in destroy_drm_connector (conn=0x564f90edf5c0) at ../subprojects/wlroots/backend/drm/drm.c:1571
#13 0x00007f73a06c009b in backend_destroy (backend=0x564f90006ce0) at ../subprojects/wlroots/backend/drm/backend.c:41
        drm = 0x564f90006ce0
        conn = 0x564f90edf5c0
        next = 0x564f90ed5700
#14 0x00007f73a06be937 in wlr_backend_destroy (backend=0x564f90006ce0) at ../subprojects/wlroots/backend/backend.c:47
#15 0x00007f73a06cf0a3 in multi_backend_destroy (wlr_backend=0x564f8f7df3c0) at ../subprojects/wlroots/backend/multi/backend.c:57
        sub = 0x564f9005e780
        backend = 0x564f8f7df3c0
#16 0x00007f73a06cf223 in handle_display_destroy (listener=0x564f8f7df410, data=0x564f8f7df2e0) at ../subprojects/wlroots/backend/multi/backend.c:110
        backend = 0x564f8f7df3c0
#17 0x00007f73a005fe0f in  () at /usr/lib/libwayland-server.so.0
#18 0x00007f73a00605a7 in wl_display_destroy () at /usr/lib/libwayland-server.so.0
#19 0x0000564f8dc27886 in server_fini (server=0x564f8dc9f340 <server>) at ../sway/server.c:203
#20 0x0000564f8dc26ff3 in main (argc=2, argv=0x7fffe2804f18) at ../sway/main.c:436

This is missing debug logs.

This is missing debug logs.

Same as https://github.com/swaywm/wlroots/issues/2526#issuecomment-751205380, this is likely nouveau-specific.

Same as https://github.com/swaywm/wlroots/issues/2526#issuecomment-751205380, this is likely nouveau-specific.

It would help if you could run Sway with a locally-compiled Mesa which has debugging symbols. Potentially with Valgrind too.
Compile Mesa with meson build/ --prefix=build/prefix, then you can use this env to run Sway: https://paste.sr.ht/~emersion/b5cff882b95ce3c3f89c957d66a5e03e9a00b762

It would help if you could run Sway with a locally-compiled Mesa which has debugging symbols. Potentially with Valgrind too.
Compile Mesa with meson build/ --prefix=build/prefix, then you can use this env to run Sway: https://paste.sr.ht/~emersion/b5cff882b95ce3c3f89c957d66a5e03e9a00b762

Ok, I'll try this and report back. thanks.

Ok, I'll try this and report back. thanks.

Here is the trace with mesa debug. Do you want me to upload massif files for the valgrind run?
#0  0x00007fa1606f03fc in gbm_dri_bo_destroy (_bo=0x562d51484b20) at ../mesa/src/gbm/backends/dri/gbm_dri.c:868
        dri = 0x562d50482e40
        arg = {handle = 0}
#1  0x00007fa160fe2e92 in buffer_destroy (wlr_buffer=0x562d51489b20) at ../subprojects/wlroots/render/gbm_allocator.c:58
        buffer = 0x562d51489b20
#2  0x00007fa16101db13 in buffer_consider_destroy (buffer=0x562d51489b20) at ../subprojects/wlroots/types/wlr_buffer.c:26
#3  0x00007fa16101db6d in wlr_buffer_drop (buffer=0x562d51489b20) at ../subprojects/wlroots/types/wlr_buffer.c:36
        __PRETTY_FUNCTION__ = "wlr_buffer_drop"
#4  0x00007fa160fe6d28 in slot_reset (slot=0x562d51489790) at ../subprojects/wlroots/render/swapchain.c:43
#5  0x00007fa160fe6d87 in wlr_swapchain_destroy (swapchain=0x562d51489700) at ../subprojects/wlroots/render/swapchain.c:52
        i = 3
#6  0x00007fa160ff076c in finish_drm_surface (surf=0x562d504a2578) at ../subprojects/wlroots/backend/drm/renderer.c:104
#7  0x00007fa160ff0c26 in drm_plane_finish_surface (plane=0x562d504a2570) at ../subprojects/wlroots/backend/drm/renderer.c:194
#8  0x00007fa160fed814 in dealloc_crtc (conn=0x562d514a0480) at ../subprojects/wlroots/backend/drm/drm.c:1076
        drm = 0x562d505c5800
#9  0x00007fa160fed64a in drm_connector_destroy_output (output=0x562d514a0480) at ../subprojects/wlroots/backend/drm/drm.c:1019
        conn = 0x562d514a0480
        mode = 0x562d4fd712e0
        mode_tmp = 0x0
#10 0x00007fa1610340d0 in wlr_output_destroy (output=0x562d514a0480) at ../subprojects/wlroots/types/wlr_output.c:393
        cursor = 0x562d514a06c0
        tmp_cursor = 0x562d514a06c0
#11 0x00007fa160fef752 in disconnect_drm_connector (conn=0x562d514a0480) at ../subprojects/wlroots/backend/drm/drm.c:1569
        __PRETTY_FUNCTION__ = "disconnect_drm_connector"
#12 0x00007fa160fef79a in destroy_drm_connector (conn=0x562d514a0480) at ../subprojects/wlroots/backend/drm/drm.c:1575
#13 0x00007fa160fe994a in backend_destroy (backend=0x562d505c5800) at ../subprojects/wlroots/backend/drm/backend.c:40
        drm = 0x562d505c5800
        conn = 0x562d514a0480
        next = 0x562d5149b8b0
        fb = 0x562d4fd72f70
        fb_tmp = 0x562d4fd72f70
#14 0x00007fa160fe81dc in wlr_backend_destroy (backend=0x562d505c5800) at ../subprojects/wlroots/backend/backend.c:47
#15 0x00007fa160ff8a07 in multi_backend_destroy (wlr_backend=0x562d4fd713c0) at ../subprojects/wlroots/backend/multi/backend.c:57
        sub = 0x562d50bc39d0
        backend = 0x562d4fd713c0
#16 0x00007fa160ff8b87 in handle_display_destroy (listener=0x562d4fd71410, data=0x562d4fd712e0) at ../subprojects/wlroots/backend/multi/backend.c:110
        backend = 0x562d4fd713c0
#17 0x00007fa160986e0f in  () at /usr/lib/libwayland-server.so.0
#18 0x00007fa1609875a7 in wl_display_destroy () at /usr/lib/libwayland-server.so.0
#19 0x0000562d4e3ce886 in server_fini (server=0x562d4e446340 <server>) at ../sway/server.c:203
#20 0x0000562d4e3cdff3 in main (argc=1, argv=0x7ffc619cf2b8) at ../sway/main.c:436
        verbose = 0
        debug = 0
        validate = 0
        allow_unsupported_gpu = 0
        long_options =
            {{name = 0x562d4e428150 "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x562d4e428155 "config", has_arg = 1, flag = 0x0, val = 99}, {name = 0x562d4e42815c "validate", has_arg = 0, flag = 0x0, val = 67}, {name = 0x562d4e428165 "debug", has_arg = 0, flag = 0x0, val = 100}, {name = 0x562d4e42816b "version", has_arg = 0, flag = 0x0, val = 118}, {name = 0x562d4e428173 "verbose", has_arg = 0, flag = 0x0, val = 86}, {name = 0x562d4e42817b "get-socketpath", has_arg = 0, flag = 0x0, val = 112}, {name = 0x562d4e42818a "unsupported-gpu", has_arg = 0, flag = 0x0, val = 117}, {name = 0x562d4e42819a "my-next-gpu-wont-be-nvidia", has_arg = 0, flag = 0x0, val = 117}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}}
        config_path = 0x0
        usage = 0x562d4e427be0 "Usage: sway [options] [command]\n\n  -h, --help", ' ' <repeats 13 times>, "Show help message and quit.\n  -c, --config <config>  Specify a config file.\n  -C, --validate         Check the validity of the config file, th"...
        c = -1

Here is the trace with mesa debug. Do you want me to upload massif files for the valgrind run?
#0  0x00007fa1606f03fc in gbm_dri_bo_destroy (_bo=0x562d51484b20) at ../mesa/src/gbm/backends/dri/gbm_dri.c:868
        dri = 0x562d50482e40
        arg = {handle = 0}
#1  0x00007fa160fe2e92 in buffer_destroy (wlr_buffer=0x562d51489b20) at ../subprojects/wlroots/render/gbm_allocator.c:58
        buffer = 0x562d51489b20
#2  0x00007fa16101db13 in buffer_consider_destroy (buffer=0x562d51489b20) at ../subprojects/wlroots/types/wlr_buffer.c:26
#3  0x00007fa16101db6d in wlr_buffer_drop (buffer=0x562d51489b20) at ../subprojects/wlroots/types/wlr_buffer.c:36
        __PRETTY_FUNCTION__ = "wlr_buffer_drop"
#4  0x00007fa160fe6d28 in slot_reset (slot=0x562d51489790) at ../subprojects/wlroots/render/swapchain.c:43
#5  0x00007fa160fe6d87 in wlr_swapchain_destroy (swapchain=0x562d51489700) at ../subprojects/wlroots/render/swapchain.c:52
        i = 3
#6  0x00007fa160ff076c in finish_drm_surface (surf=0x562d504a2578) at ../subprojects/wlroots/backend/drm/renderer.c:104
#7  0x00007fa160ff0c26 in drm_plane_finish_surface (plane=0x562d504a2570) at ../subprojects/wlroots/backend/drm/renderer.c:194
#8  0x00007fa160fed814 in dealloc_crtc (conn=0x562d514a0480) at ../subprojects/wlroots/backend/drm/drm.c:1076
        drm = 0x562d505c5800
#9  0x00007fa160fed64a in drm_connector_destroy_output (output=0x562d514a0480) at ../subprojects/wlroots/backend/drm/drm.c:1019
        conn = 0x562d514a0480
        mode = 0x562d4fd712e0
        mode_tmp = 0x0
#10 0x00007fa1610340d0 in wlr_output_destroy (output=0x562d514a0480) at ../subprojects/wlroots/types/wlr_output.c:393
        cursor = 0x562d514a06c0
        tmp_cursor = 0x562d514a06c0
#11 0x00007fa160fef752 in disconnect_drm_connector (conn=0x562d514a0480) at ../subprojects/wlroots/backend/drm/drm.c:1569
        __PRETTY_FUNCTION__ = "disconnect_drm_connector"
#12 0x00007fa160fef79a in destroy_drm_connector (conn=0x562d514a0480) at ../subprojects/wlroots/backend/drm/drm.c:1575
#13 0x00007fa160fe994a in backend_destroy (backend=0x562d505c5800) at ../subprojects/wlroots/backend/drm/backend.c:40
        drm = 0x562d505c5800
        conn = 0x562d514a0480
        next = 0x562d5149b8b0
        fb = 0x562d4fd72f70
        fb_tmp = 0x562d4fd72f70
#14 0x00007fa160fe81dc in wlr_backend_destroy (backend=0x562d505c5800) at ../subprojects/wlroots/backend/backend.c:47
#15 0x00007fa160ff8a07 in multi_backend_destroy (wlr_backend=0x562d4fd713c0) at ../subprojects/wlroots/backend/multi/backend.c:57
        sub = 0x562d50bc39d0
        backend = 0x562d4fd713c0
#16 0x00007fa160ff8b87 in handle_display_destroy (listener=0x562d4fd71410, data=0x562d4fd712e0) at ../subprojects/wlroots/backend/multi/backend.c:110
        backend = 0x562d4fd713c0
#17 0x00007fa160986e0f in  () at /usr/lib/libwayland-server.so.0
#18 0x00007fa1609875a7 in wl_display_destroy () at /usr/lib/libwayland-server.so.0
#19 0x0000562d4e3ce886 in server_fini (server=0x562d4e446340 <server>) at ../sway/server.c:203
#20 0x0000562d4e3cdff3 in main (argc=1, argv=0x7ffc619cf2b8) at ../sway/main.c:436
        verbose = 0
        debug = 0
        validate = 0
        allow_unsupported_gpu = 0
        long_options =
            {{name = 0x562d4e428150 "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x562d4e428155 "config", has_arg = 1, flag = 0x0, val = 99}, {name = 0x562d4e42815c "validate", has_arg = 0, flag = 0x0, val = 67}, {name = 0x562d4e428165 "debug", has_arg = 0, flag = 0x0, val = 100}, {name = 0x562d4e42816b "version", has_arg = 0, flag = 0x0, val = 118}, {name = 0x562d4e428173 "verbose", has_arg = 0, flag = 0x0, val = 86}, {name = 0x562d4e42817b "get-socketpath", has_arg = 0, flag = 0x0, val = 112}, {name = 0x562d4e42818a "unsupported-gpu", has_arg = 0, flag = 0x0, val = 117}, {name = 0x562d4e42819a "my-next-gpu-wont-be-nvidia", has_arg = 0, flag = 0x0, val = 117}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}}
        config_path = 0x0
        usage = 0x562d4e427be0 "Usage: sway [options] [command]\n\n  -h, --help", ' ' <repeats 13 times>, "Show help message and quit.\n  -c, --config <config>  Specify a config file.\n  -C, --validate         Check the validity of the config file, th"...
        c = -1

Thanks, that's helpful.

Do you want me to upload massif files for the valgrind run?

Hm, did Valgrind not print any stack trace on its own? Can you check the Sway logs?

Thanks, that's helpful.

Do you want me to upload massif files for the valgrind run?

Hm, did Valgrind not print any stack trace on its own? Can you check the Sway logs?

It sounds like bo->image is not NULL but is already free'd by Mesa. Maybe https://github.com/swaywm/wlroots/pull/2639 will help because it uses two separate GBM devices.

It sounds like bo->image is not NULL but is already free'd by Mesa. Maybe https://github.com/swaywm/wlroots/pull/2639 will help because it uses two separate GBM devices.

Wasn't sure about format for valgrind. Attaching log.
sway-valgrind-medium.log

Wasn't sure about format for valgrind. Attaching log.
sway-valgrind-medium.log

Thanks a lot, that's very helpful. This crash happens because we destroy the gbm_device before the gbm_bo.
==5792== Invalid read of size 8
==5792==    at 0x51ED26B: gbm_bo_destroy (gbm.c:445)
==5792==    by 0x4873E91: buffer_destroy (gbm_allocator.c:58)
==5792==    by 0x48AEB39: buffer_consider_destroy (wlr_buffer.c:26)
==5792==    by 0x48AEB93: wlr_buffer_drop (wlr_buffer.c:36)
==5792==    by 0x4877D4E: slot_reset (swapchain.c:43)
==5792==    by 0x4877DAD: wlr_swapchain_destroy (swapchain.c:52)
==5792==    by 0x4881792: finish_drm_surface (renderer.c:104)
==5792==    by 0x4881C4C: drm_plane_finish_surface (renderer.c:194)
==5792==    by 0x487E83A: dealloc_crtc (drm.c:1073)
==5792==    by 0x487E670: drm_connector_destroy_output (drm.c:1016)
==5792==    by 0x48C50F6: wlr_output_destroy (wlr_output.c:393)
==5792==    by 0x4880778: disconnect_drm_connector (drm.c:1566)
==5792==  Address 0x9c64200 is 288 bytes inside a block of size 568 free'd
==5792==    at 0x483B9AB: free (vg_replace_malloc.c:538)
==5792==    by 0x4874300: allocator_destroy (gbm_allocator.c:162)
==5792==    by 0x4870EB0: wlr_allocator_destroy (allocator.c:17)
==5792==    by 0x4881624: finish_drm_renderer (renderer.c:66)
==5792==    by 0x487AA84: backend_destroy (backend.c:56)
==5792==    by 0x4879202: wlr_backend_destroy (backend.c:47)
==5792==    by 0x4889A2D: multi_backend_destroy (backend.c:57)
==5792==    by 0x4889BAD: handle_display_destroy (backend.c:110)
==5792==    by 0x4F53E0E: ??? (in /usr/lib/libwayland-server.so.0.1.0)
==5792==    by 0x4F545A6: wl_display_destroy (in /usr/lib/libwayland-server.so.0.1.0)
==5792==    by 0x128885: server_fini (server.c:203)
==5792==    by 0x127FF2: main (main.c:436)
==5792==  Block was alloc'd at
==5792==    at 0x483CB65: calloc (vg_replace_malloc.c:760)
==5792==    by 0x51EC70F: dri_device_create (gbm_dri.c:1363)
==5792==    by 0x51E8E00: UnknownInlinedFun (backend.c:100)
==5792==    by 0x51E8E00: gbm_create_device (gbm.c:137)
==5792==    by 0x4874284: wlr_gbm_allocator_create (gbm_allocator.c:150)
==5792==    by 0x4881590: init_drm_renderer (renderer.c:45)
==5792==    by 0x487B041: wlr_drm_backend_create (backend.c:189)
==5792==    by 0x48795F1: attempt_drm_backend (backend.c:163)
==5792==    by 0x4879BF1: wlr_backend_autocreate (backend.c:302)
==5792==    by 0x1280D6: server_privileged_prepare (server.c:46)
==5792==    by 0x127E17: main (main.c:378)

Thanks a lot, that's very helpful. This crash happens because we destroy the gbm_device before the gbm_bo.
==5792== Invalid read of size 8
==5792==    at 0x51ED26B: gbm_bo_destroy (gbm.c:445)
==5792==    by 0x4873E91: buffer_destroy (gbm_allocator.c:58)
==5792==    by 0x48AEB39: buffer_consider_destroy (wlr_buffer.c:26)
==5792==    by 0x48AEB93: wlr_buffer_drop (wlr_buffer.c:36)
==5792==    by 0x4877D4E: slot_reset (swapchain.c:43)
==5792==    by 0x4877DAD: wlr_swapchain_destroy (swapchain.c:52)
==5792==    by 0x4881792: finish_drm_surface (renderer.c:104)
==5792==    by 0x4881C4C: drm_plane_finish_surface (renderer.c:194)
==5792==    by 0x487E83A: dealloc_crtc (drm.c:1073)
==5792==    by 0x487E670: drm_connector_destroy_output (drm.c:1016)
==5792==    by 0x48C50F6: wlr_output_destroy (wlr_output.c:393)
==5792==    by 0x4880778: disconnect_drm_connector (drm.c:1566)
==5792==  Address 0x9c64200 is 288 bytes inside a block of size 568 free'd
==5792==    at 0x483B9AB: free (vg_replace_malloc.c:538)
==5792==    by 0x4874300: allocator_destroy (gbm_allocator.c:162)
==5792==    by 0x4870EB0: wlr_allocator_destroy (allocator.c:17)
==5792==    by 0x4881624: finish_drm_renderer (renderer.c:66)
==5792==    by 0x487AA84: backend_destroy (backend.c:56)
==5792==    by 0x4879202: wlr_backend_destroy (backend.c:47)
==5792==    by 0x4889A2D: multi_backend_destroy (backend.c:57)
==5792==    by 0x4889BAD: handle_display_destroy (backend.c:110)
==5792==    by 0x4F53E0E: ??? (in /usr/lib/libwayland-server.so.0.1.0)
==5792==    by 0x4F545A6: wl_display_destroy (in /usr/lib/libwayland-server.so.0.1.0)
==5792==    by 0x128885: server_fini (server.c:203)
==5792==    by 0x127FF2: main (main.c:436)
==5792==  Block was alloc'd at
==5792==    at 0x483CB65: calloc (vg_replace_malloc.c:760)
==5792==    by 0x51EC70F: dri_device_create (gbm_dri.c:1363)
==5792==    by 0x51E8E00: UnknownInlinedFun (backend.c:100)
==5792==    by 0x51E8E00: gbm_create_device (gbm.c:137)
==5792==    by 0x4874284: wlr_gbm_allocator_create (gbm_allocator.c:150)
==5792==    by 0x4881590: init_drm_renderer (renderer.c:45)
==5792==    by 0x487B041: wlr_drm_backend_create (backend.c:189)
==5792==    by 0x48795F1: attempt_drm_backend (backend.c:163)
==5792==    by 0x4879BF1: wlr_backend_autocreate (backend.c:302)
==5792==    by 0x1280D6: server_privileged_prepare (server.c:46)
==5792==    by 0x127E17: main (main.c:378)

Can you try https://github.com/swaywm/wlroots/pull/2642?

Can you try https://github.com/swaywm/wlroots/pull/2642?


TypeError: Style.new() got an unexpected keyword argument 'themes_file'

I get this error after the command python ui.py (I also had to install mcschematic manually) : TypeError: Style.__new__() got an unexpected keyword argument 'themes_file'
The whole error message is :
PS D:\Downloads\BuilderGPT-main> python ui.py
Traceback (most recent call last):
  File "D:\Downloads\BuilderGPT-main\ui.py", line 285, in <module>
    root = CreateQGUI(title="BuilderGPT",
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\Downloads\BuilderGPT-main\cube_qgui\factory.py", line 52, in __init__
    self.root.style = Style(**QStyle.default)
                      ^^^^^^^^^^^^^^^^^^^^^^^
TypeError: Style.__new__() got an unexpected keyword argument 'themes_file'

Download
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
In the installer menu, select "gcc."

I looked in their discord and found this pip uninstall -y ttkbootstrap && pip install ttkbootstrap==0.5.1 and got the gui to work

Oh it seems that it fixed the issue, thank you so much @CortCannon!


Add a license to the repository

I recently came across your project 2024_IBM_Quantum_Challenge_Solutions and I noticed that the repository github.com/FreesiaG/2024_IBM_Quantum_Challenge_Solutions currently does not have a license specified.
Why Adding a License is Important?
As GitHub documents

Public repositories on GitHub are often used to share open source software. For your repository to truly be open source, you'll need to license it so that others are free to use, change, and distribute the software.

Would be possible to add a valid license to this repository? Probably something really OpenSource such as the Apache 2.0 license would fit really well.
Thanks!

Thank you cbjuan, all fixed up! :)

Thank you!


Create Account Documentation is Incorrect

The swagger templated body is:
{
  "account": null,
  "name": "Checking",
  "offbudget": false
}

But the correct body is:
{
  "account": {
    "name": "Checking",
    "offbudget": false
  }
}

Kept on hitting 500 till I read the Actual API and noticed it expects type Account as the first param :)
https://actualbudget.org/docs/api/reference/#examples
createAccount(account, initialBalance = 0) → Promise<id>

Relevant part in source:
https://github.com/jhonderson/actual-http-api/blob/main/src/v1/routes/accounts.js#L177-L234
I'm sorry, I don't code JS/Swagger much so it will take me a bit, but I will try and raise a PR against this issue

Hello, thanks for reporting. Please go ahead with the CR, happy to help if needed.

The documentation is correct.
I was using a Docker image that was cached (and 7 months old) which had the wrong API documentation.
In forking and attempting a fix I noticed I was wrong.
Apologies for the confusion!


Check if file is not null before deleting it

relates to https://github.com/monitorjbl/excel-streaming-reader/issues/171

Whoops, forgot about this one. Good catch!


Allow events

Just a placeholder for initial code review before adding support for more types.

https://github.com/SpringerPE/firehose-to-syslog/pull/4
Is a much better implementation of this.


VerneMQ in bridge mode fails to get data from it's upstream peer

To help us save time and help you faster
Before opening a new issue, please make sure that isn't already an open (or
closed/resolved) issue concerning the problem. If unsure if older issues are
about the exact same thing, just open a new issue rather than posting in the old
one - but please reference the possibly related issues in the new issue.
Please do not insert images of text, but insert the text instead.
Environment

VerneMQ Version: 1.9.2
OS: Alpine
Erlang/OTP version (if building from source):
VerneMQ configuration (vernemq.conf) or the changes from the default
########## Start ##########
vmq_bridge.ssl.sbr0=mqtt.zodiac.iot.openocean.studio:8883
vmq_bridge.ssl.sbr0.certfile=/etc/ssl/vernemq/bridge_tls.crt
listener.ssl.default=<IP_ADDRESS>:8883
vmq_bridge.ssl.sbr0.keyfile=/etc/ssl/vernemq/bridge_tls.key
listener.ssl.keyfile=/etc/ssl/vernemq/tls.key
listener.ssl.require_certificate=on
vmq_bridge.ssl.sbr0.tls_version=tlsv1.2
allow_subscribe_during_netsplit=on
vmq_bridge.ssl.sbr0.topic.2=v1.zodiac.openocean.studio/+/bridge/* in
vmq_bridge.ssl.sbr0.topic.3=v1.zodiac.openocean.studio/+/app/* in
vmq_bridge.ssl.sbr0.topic.1=v1.zodiac.openocean.studio/+/ecr/* in
listener.ssl.certfile=/etc/ssl/vernemq/tls.crt
vmq_bridge.ssl.sbr0.insecure=off
listener.ssl.allowed_protocol_versions=3,4,5,131
allow_publish_during_netsplit=on
allow_anonymous=on
listener.ssl.cafile=/etc/ssl/vernemq/ca.crt
allow_unsubscribe_during_netsplit=on
plugins.vmq_bridge=on
listener.ssl.use_identity_as_username=on
vmq_bridge.ssl.sbr0.max_outgoing_buffered_messages=10000
log.console=console
allow_register_during_netsplit=on
listener.tcp.localhost=<IP_ADDRESS>:1883
vmq_bridge.ssl.sbr0.cafile=/etc/ssl/vernemq/bridge_ca.crt
erlang.distribution.port_range.minimum = 9100
erlang.distribution.port_range.maximum = 9109
listener.tcp.default = <IP_ADDRESS>:1883
listener.ws.default = <IP_ADDRESS>:8080
listener.vmq.clustering = <IP_ADDRESS>:44053
listener.http.metrics = <IP_ADDRESS>:8888
Cluster size/standalone: standalone

Expected behavior

Please describe the expected behaviour.
VerneMQ should connect to master via bridge and start pulling data in.

Actual behaviour
No data flowing in. Error messages are:
10:46:00.937 [error] Supervisor vmq_bridge_sup had child {vmq_bridge,"mqtt.zodiac.iot.openocean.studio",8883} started with vmq_bridge:start_link(ssl, "mqtt.zodiac.iot.openocean.studio", 8883, {vmq_reg,direct_plugin_exports,[vmq_bridge]}, [{cleansession,false},{client_id,"vernemq-0.sbr0"},{keepalive_interval,60},{restart_timeout,10},...]) at <0.573.0> exit with reason no case clause matching 0 in vmq_reg:publish/4 line 308 in context child_terminated
10:46:01.245 [error] gen_server <0.581.0> terminated with reason: no case clause matching 0 in vmq_reg:publish/4 line 308
10:46:01.245 [error] CRASH REPORT Process <0.581.0> with 2 neighbours crashed with reason: no case clause matching 0 in vmq_reg:publish/4 line 308
10:46:01.246 [error] Supervisor vmq_bridge_sup had child {vmq_bridge,"mqtt.zodiac.iot.openocean.studio",8883} started with vmq_bridge:start_link(ssl, "mqtt.zodiac.iot.openocean.studio", 8883, {vmq_reg,direct_plugin_exports,[vmq_bridge]}, [{cleansession,false},{client_id,"vernemq-0.sbr0"},{keepalive_interval,60},{restart_timeout,10},...]) at <0.581.0> exit with reason no case clause matching 0 in vmq_reg:publish/4 line 308 in context child_terminated
10:46:04.492 [error] gen_server <0.589.0> terminated with reason: no case clause matching 0 in vmq_reg:publish/4 line 308
10:46:04.492 [error] CRASH REPORT Process <0.589.0> with 2 neighbours crashed with reason: no case clause matching 0 in vmq_reg:publish/4 line 308
10:46:04.492 [error] Supervisor vmq_bridge_sup had child {vmq_bridge,"mqtt.zodiac.iot.openocean.studio",8883} started with vmq_bridge:start_link(ssl, "mqtt.zodiac.iot.openocean.studio", 8883, {vmq_reg,direct_plugin_exports,[vmq_bridge]}, [{cleansession,false},{client_id,"vernemq-0.sbr0"},{keepalive_interval,60},{restart_timeout,10},...]) at <0.589.0> exit with reason no case clause matching 0 in vmq_reg:publish/4 line 308 in context child_terminated
10:46:04.492 [error] Supervisor vmq_bridge_sup had child {vmq_bridge,"mqtt.zodiac.iot.openocean.studio",8883} started with vmq_bridge:start_link(ssl, "mqtt.zodiac.iot.openocean.studio", 8883, {vmq_reg,direct_plugin_exports,[vmq_bridge]}, [{cleansession,false},{client_id,"vernemq-0.sbr0"},{keepalive_interval,60},{restart_timeout,10},...]) at <0.589.0> exit with reason reached_max_restart_intensity in context shutdown
10:46:04.493 [info] Application vmq_bridge exited with reason: shutdown

Please include minimal steps to reproduce the issue, if possible.

Thank you for opening the issue! PR is on it's way.


Make an ADR on signal types and enforce

Following https://github.com/bluesky/ophyd-async/issues/310#issuecomment-2324326509 we have a well defined list of types that signals are allowed. However, there are still old devices in dodal that use different types e.g. https://github.com/DiamondLightSource/dodal/blob/f2e63c2c55d49ed35cef73531be7d4bcceb42546/src/dodal/devices/zocalo/zocalo_results.py#L133. To make sure these get phased out and more don't get introduced we should prohibit other types ideally through the typing system. To make it clear why this is the case we should make an ADR too.
Acceptance Criteria

An ADR is made on the types that signals are allowed
If try and make a signal with an unsupported type e.g. soft_signal_r_and_setter(MyArbitraryType) the type system will complain

Agreed.
https://github.com/bluesky/ophyd-async/pull/594 will do the type checking.
https://github.com/bluesky/ophyd-async/pull/594/files#r1790651259 shows the types that will be in the ADR


Docker-based environment for integration testing

I suppose there's not much to unittest on the rdkafka side of things, because all the functionality is really in the underlying libs, but it would be really helpful to have integration tests so bumping versions can be done safely.
There's a start for this in the dockerise branch, but there's a lot more plumbing to do to tie it into nose etc.

I'm going to close this in favor of our current integration test setup.

Thanks, was just about to come here to do the same! Your testinstances setup works great here, and it's indeed much easier to avoid a 'dirty' cluster causing odd interactions between test runs.


Rebase to kubernetes v1.6.0-beta.1

Rebase cluster capacity to kubernetes v1.6.0-beta.1.

Its already done so closing this.


Fix for no tqdm

Fixes https://github.com/pytorch/vision/issues/769
The interface for PyTorch's tqdm doesn't support not passing the total argument, but it does support None.
Also adds tests, which should run in the "no-tqdm" configuration.

Codecov Report

Merging #770 into master will increase coverage by 0.67%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #770      +/-   ##
==========================================
+ Coverage   40.31%   40.99%   +0.67%
==========================================
  Files          29       29
  Lines        2746     2747       +1
  Branches      432      432
==========================================
+ Hits         1107     1126      +19
+ Misses       1563     1542      -21
- Partials       76       79       +3

Impacted Files
Coverage Δ

torchvision/datasets/utils.py
48.38% <100%> (+30.35%)
:arrow_up:

Continue to review full report at Codecov.

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

Thanks @fmassa !


Build errors

I get some build-time errors when building the gem.
~> gem install fusuma-plugin-remap
Building native extensions. This could take a while...
ERROR:  Error installing fusuma-plugin-remap:
        ERROR: Failed to build gem native extension.

    current directory: /home/rw/.local/share/gem/ruby/3.3.0/gems/ruinput-0.1.1/ext/ruinput
/usr/bin/ruby extconf.rb
creating Makefile

current directory: /home/rw/.local/share/gem/ruby/3.3.0/gems/ruinput-0.1.1/ext/ruinput
make DESTDIR\= sitearchdir\=./.gem.20241126-8788-t3m0lu sitelibdir\=./.gem.20241126-8788-t3m0lu clean

current directory: /home/rw/.local/share/gem/ruby/3.3.0/gems/ruinput-0.1.1/ext/ruinput
make DESTDIR\= sitearchdir\=./.gem.20241126-8788-t3m0lu sitelibdir\=./.gem.20241126-8788-t3m0lu
compiling ruinput.c
ruinput.c:13:9: warning: "FALSE" redefined
   13 | #define FALSE 0
      |         ^~~~~
In file included from /usr/include/ruby-3.3.0/ruby/defines.h:74,
                 from /usr/include/ruby-3.3.0/ruby/ruby.h:25,
                 from /usr/include/ruby-3.3.0/ruby.h:38,
                 from ruinput.c:8:
/usr/include/ruby-3.3.0/ruby/backward/2/bool.h:25:10: note: this is the location of the previous definition
   25 | # define FALSE false
      |          ^~~~~
ruinput.c:14:9: warning: "TRUE" redefined
   14 | #define TRUE !FALSE
      |         ^~~~
/usr/include/ruby-3.3.0/ruby/backward/2/bool.h:31:10: note: this is the location of the previous definition
   31 | # define TRUE true
      |          ^~~~
ruinput.c: In function ‘uinput_user_dev_raw_initalize’:
ruinput.c:48:7: error: assignment to ‘struct uinput_user_dev *’ from incompatible pointer type ‘char *’ [-Wincompatible-pointer-types]
   48 |   uud = RSTRING_PTR(bytes);
      |       ^
In file included from /usr/include/ruby-3.3.0/ruby/intern.h:56,
                 from /usr/include/ruby-3.3.0/ruby/ruby.h:194:
ruinput.c: In function ‘uinput_user_dev_to_byte_string’:
ruinput.c:95:21: error: passing argument 1 of ‘rb_str_new’ from incompatible pointer type [-Wincompatible-pointer-types]
   95 |   return rb_str_new(&uud, sizeof(struct uinput_user_dev));
/usr/include/ruby-3.3.0/ruby/internal/intern/string.h:1502:21: note: in definition of macro ‘rb_str_new’
 1502 |       rb_str_new) ((str), (len)))
      |                     ^~~
ruinput.c:95:21: note: expected ‘const char *’ but argument is of type ‘struct uinput_user_dev *’
   95 |   return rb_str_new(&uud, sizeof(struct uinput_user_dev));
/usr/include/ruby-3.3.0/ruby/internal/intern/string.h:1502:21: note: in definition of macro ‘rb_str_new’
 1502 |       rb_str_new) ((str), (len)))
      |                     ^~~
make: *** [Makefile:248: ruinput.o] Error 1

make failed, exit code 2

Gem files will remain installed in /home/rw/.local/share/gem/ruby/3.3.0/gems/ruinput-0.1.1 for inspection.
Results logged to /home/rw/.local/share/gem/ruby/3.3.0/extensions/x86_64-linux/3.3.0/ruinput-0.1.1/gem_make.out

Thanks for all your work, and let me know if I can provide additional information.
System information

distro: Arch (Wayland)
libinput: 1.27.0
gcc: 14.2.1

$ libinput list-devices
libinput-config: initializing
libinput-config: replacing the device config functions
libinput-config: initializing the key mapper
libinput-config: option 'scroll-factor' is '0.25'
libinput-config: initialized
libinput-config: configuring device 'Video Bus'
Device:           Video Bus
Kernel:           /dev/input/event3
Group:            1
Seat:             seat0, default
Capabilities:     keyboard
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         0,0

libinput-config: configuring device 'Lid Switch'
Device:           Lid Switch
Kernel:           /dev/input/event0
Group:            2
Seat:             seat0, default
Capabilities:     switch
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         0,0

libinput-config: configuring device 'Power Button'
Device:           Power Button
Kernel:           /dev/input/event1
Group:            3
Seat:             seat0, default
Capabilities:     keyboard
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         0,0

libinput-config: configuring device 'FRMW0004:00 32AC:0006 Wireless Radio Control'
Device:           FRMW0004:00 32AC:0006 Wireless Radio Control
Kernel:           /dev/input/event4
Group:            4
Seat:             seat0, default
Capabilities:     keyboard
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         0,0

libinput-config: configuring device 'FRMW0004:00 32AC:0006 Consumer Control'
Device:           FRMW0004:00 32AC:0006 Consumer Control
Kernel:           /dev/input/event5
Group:            4
Seat:             seat0, default
Capabilities:     keyboard pointer
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    disabled
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         0,0

libinput-config: configuring device 'PIXA3854:00 093A:0274 Mouse'
Device:           PIXA3854:00 093A:0274 Mouse
Kernel:           /dev/input/event10
Group:            5
Seat:             seat0, default
Capabilities:     pointer
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   *button
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   flat *adaptive custom
Rotation:         n/a

libinput-config: configuring device 'PIXA3854:00 093A:0274 Touchpad'
Device:           PIXA3854:00 093A:0274 Touchpad
Kernel:           /dev/input/event11
Group:            5
Seat:             seat0, default
Size:             111x73mm
Capabilities:     pointer gesture
Tap-to-click:     disabled
Tap-and-drag:     enabled
Tap drag lock:    disabled
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: disabled
Calibration:      n/a
Scroll methods:   *two-finger edge
Click methods:    *button-areas clickfinger
Disable-w-typing: enabled
Disable-w-trackpointing: enabled
Accel profiles:   flat *adaptive custom
Rotation:         n/a

libinput-config: configuring device 'AT Translated Set 2 keyboard'
Device:           AT Translated Set 2 keyboard
Kernel:           /dev/input/event6
Group:            6
Seat:             seat0, default
Capabilities:     keyboard
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles:   n/a
Rotation:         0,0

Oh I didn't inspect the logs correctly, its not this gem that fails to build, but one of its dependencies.


Running in gossip mode on mainnet results in failed to verify protocol message signature InvalidPullRequest

Description
Building from tip for tree and running in gossipmode against mainnet results in:
time=2023-12-21T17:11:34Z level=debug  failed to verify protocol message signature InvalidPullResponse
Not sure if this is expected based on current state of codebase or not hence filing issue
How to Reproduce the Bug

Clone 949eb15dbecc1cbd091ccf8344aa5c65b16278a8
Follow instructions from new (much better!) readme.md to run against mainnet
Result: above error message.

Additional Context
No response

Did you make any changes to the code before running this?
With spy_node = false, I see a similar log message that I'd like to investigate:
time=2023-12-22T21:23:15Z level=debug  gossip: packet_verify: failed to verify signature

No changes and I didn't change any flags

So far, I've narrowed this down to be an issue with ContactInfo pull responses.
All other pull responses are working fine. Every ContactInfo pull response received from either mainnet or devnet fails signature validation. Hundreds of messages are succeeding the signature validation for every one failed ContactInfo.
Like the rust implementation, Sig expects the ContactInfo to be signed by the private key corresponding to the public key contained within the ContactInfo. But the signature included alongside the ContactInfo is failing that validation. We have some tests on serialization/deserialization, plus I just added one more, and I haven't found a problem there. I'll have to keep digging to figure this out.


Switch from 128-bit to 16-bit service UUID - Validated

Migrated to 16-bit service UUID to enable advertising of TxPower and PseudoDeviceAddress
Separation of static and app configurable parameters in BLESensorConfiguration
Tested on Pixel 2, iPhone 6S, iPhone 6 Plus

Closes #18
Signed-off-by: c19x<EMAIL_ADDRESS>

Holding off on acceptance until we investigate any interference / clashes by using the generic networking short UUID

Holding until dedicated 16-bit UUID is available.


[5.2] We need to work on URL validation

I've brought this up a long time ago, but we never did something about it.
URL validation in Laravel is rather broken; some perfectly valid URLs are not validated, and some invalid (and quite dangerous ones) are let through, like this good boy:

javascript://test%0Aalert(321)

Some more information on why filter_var() is not the best way to do URL validation:
http://www.d-mueller.de/blog/why-url-validation-with-filter_var-might-not-be-a-good-idea/
I only added some new tests, which prove that something should be done about this.
Some of our options:

Using Symfony's regex: https://github.com/symfony/Validator/blob/master/Constraints/UrlValidator.php
I think we have a rather complete one in FluxBB: https://github.com/fluxbb/fluxbb/blob/207d7e4a12938857d3c0b4d7a01da382e3873603/include/functions.php#L1910-L2017
I'm sure there are packages for this purpose.

/cc @willrowe @borys-p You guys may be interested in this
/ref #10088 and #10103

I'd argue this is somewhat security-relevant, since people may trust the validator to ensure a perfectly safe URL; and falsely assume it's safe for use in HTML links. The example shows that that opens XSS vulnerabilities.

Some of the ones you've put in invalid are actually valid like these:

http://laravel.com?
http://laravel.com/?
http://laravel.com#

There is nothing wrong with having those validated as successful.

I'm OK with using Symfony's regex.

Anyone want to volunteer to integrate Symfony's regex into 5.2?

@taylorotwell I went ahead and integrated Symfony's regex into that check for you in #10196.
I decided to keep the scope fairly small and target ONLY the url regex. I also only targeted the http, https, and ftp protocols (since that's what made sense to me, open to suggestions).

@scrothers: The loop is redundant, you have to parse the regex three times. Simply pass "(ftp|https?)" to the sprintf(). You can also integrate the full IANA schemes list ;)
Perhaps you should also throw ValidatorException with preg_last_error() when preg_match() returns false?

@borys-p I like the idea of the IANA scheme list and adjustment to the filter, but, I don't like the idea of introducing a new exception into this particular area because one didn't exist previously, and I feel that's changing the fundamental function of this method.
Example, only one of the validators tossing an exception possibly out of all? Seems inconsistent to me. I do like the IANA list idea though, I'll add it and rebase. Thanks for the tip!

Upon the suggestion of @crynobone in #10197 I also added the tests from #10149 with the exception of 'http://laravel.com/?' being marked invalid as in #10149 because it is most definitely a valid url and most likely was an accident in being in the invalid list.
Tests succeed for all 26 tests/assertions and I also changed the regex as @borys-p suggested to included all the IANA approved protocol prefixes for uris.
Overall I think this is an improvement to the existing url validator as it was previously :)
Thank you everyone for your help!

@scrothers: you're right, I didn't check if Validator throws any exceptions. But if the regex is valid then there should be no errors (like the the stack overflow in #9588 where I'm still waiting for any comment from @taylorotwell ;)

I concur with your thoughts on that (I honestly didn't even notice the dots) but I also added tests for all the URIs to make sure they test good.

I assume this can be closed now that other PR is merged. Let me know if I've overlooked anything.


Eagerly Awaiting the Open Source Release！(●'◡'●)

Everyday comments，🤭

Hey,
The code will be shared in the week. Probably today or tomorrow :)


Enable clipboard support for image/png

As the title says. This is because image copied may posses alpha channels. By default, copying an image w/ transparent background from Host results to pasted image in remote app w/ black background which is incorrect. For details, see: https://github.com/FreeRDP/FreeRDP/issues/9467

Please read what I have written in https://github.com/FreeRDP/FreeRDP/issues/9467 and stop creating new issues for answered questions.


Auto Tracking in "history" router's mode

Hello!
It seems to me that the auto tracking does not work when vue-router's history mode is on.
I this expected? Am i'm doing something wrong?

Actually It does work.
I've figured out that it was another issue on my code. I'm closing the issue


add example doc

Codecov Report

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

@@            Coverage Diff             @@
##             develop      #88   +/-   ##
==========================================
  Coverage           ?   52.79%
==========================================
  Files              ?      200
  Lines              ?    20791
  Branches           ?        0
==========================================
  Hits               ?    10976
  Misses             ?     8598
  Partials           ?     1217

Continue to review full report at Codecov.

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


Bump minimum version of pydantic to work on Python 3.12.4.

Bump minimum pydantic version to 2.7.4 which works on Python 3.12.4. Fresh installs get it automatically, but in-place updates fail to do so with the old requirements.txt, as the version on disk is already satisfied.
Fixes #1391
Issue resolved by this Pull Request:
Resolves #1391
Checklist:

[X] Commit Message Formatting: Commit titles and messages follow guidelines in the
conventional commits.
[ ] Changelog updated with breaking and/or notable changes for the next minor release.
[ ] Documentation has been updated, if necessary.
[ ] Unit tests have been added, if necessary.
[ ] Integration tests have been added, if necessary.

@leseb ok

@Mergifyio backport release-v0.17


Used the same OModificationLock object of storage

Used the same OModificationLock object of storage

Luca we can not remove modification lock from index in 2.1
because indexes before 2.2 directly go to data structures and do not participate in storage modification lock it is fixed in https://github.com/orientechnologies/orientdb/issues/4831

I didn't remove modification lock in indexes, but I used the same object as for storage.

Well probably it will work, let me think till tomorrow.

@lvca could you trace all usages of prohibit modifications from indexes and remove them, so we will leave storage as central point of control, then I think we may merge pull request ?

So you mean to completely remove the usage of modification lock, right?

In all the indexes?


s3-us-west-2.amazonaws.com -> s3.amazonaws.com

Motivation for this change
s3-us-west-2.amazonaws.com is not a worldwide available domain.
In particular, it is blocked in Russia:
# wget s3-us-west-2.amazonaws.com
--2017-12-19 23:15:33--  http://s3-us-west-2.amazonaws.com/
Resolving s3-us-west-2.amazonaws.com (s3-us-west-2.amazonaws.com)... <IP_ADDRESS>
Connecting to s3-us-west-2.amazonaws.com (s3-us-west-2.amazonaws.com)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 307 Temporary Redirect
Location: http://forbidden.yota.ru/ [following]
--2017-12-19 23:15:33--  http://forbidden.yota.ru/

Also https://roskomsvoboda.org/32259/

I've tried to access s3-us-west-2.amazonaws.com using Yota (the provider above) and MGTS and in both cases it doesn't seem to be blocked.

Nevertheless the previous sources were not at canonical s3 domains, so I've fixed this PR (https://s3.amazonaws.com/grafana-releases/release/grafana-4.6.3.linux-x64.tar.gz was incorrect) and merged it.

It is still being blocked by Yota (at least in St.Petersburg)

@volth I'm in Moscow, so that is likely the case.


Signal 11 crash when using Firestore with .NET Core 3.0

See:

https://stackoverflow.com/questions/58613778
https://github.com/aaad/firestore-crash

(Just leaving this as a note to myself to investigate.)

I've managed to reproduce the crash using k8s. It does seem to still have Grpc.Core 1.x, which was my first concern. Still investigating what's going on. I'll try using another API, with a non-streaming call, to see if that fails too.

Okay, so far I've determined this isn't about .NET Core 3.0 - it's about .NET Core on Alpine. I can reproduce the issue with a console app in .NET Core 2.1 on Alpine. Continuing to investigate.

The workaround here: https://github.com/grpc/grpc/pull/17272/files - works for a console app. Trying it for ASP.NET Core 3.0 now...

I've now posted an answer including a way forward on the Stack Overflow question, as probably the best place for it to live. Closing this issue now, as we've resolved it as far as we expect to.


Can we download and update the software with a separate component?

Description of the new feature / enhancement
I only use the rename component from powertoys now. And I don't want to download such a big installation package every time to update.
Scenario when this would be used?
--
Supporting information
No response

No plans currently.


This crate only works with a nightly compiler, meaning 1.2.0 isn't appropriate and this behaviour is expected. You may be interested in https://github.com/brson/multirust to help juggle Rust versions.
Thanks for filing!

thank you for the very quick response!


A confusion about interface

hello, i am studying typescript now.It is pretty good.However, there are some confusion in the process.
interface Counter {     (start: number): string;     interval: number;     reset(): void; } function getCounter(): Counter {     let counter = <Counter>function (start: number) {};     counter.interval = 123;     counter.reset = function () { };     return counter; }
interface Counter {     (start: number): void;     interval: number;     reset(): void; } function getCounter(): Counter {     let counter = <Counter>function (start: number) {return '12'};     counter.interval = 123;     counter.reset = function () { };     return counter; }
Why the first one performs well but the second meets a error.what is the mean for  foo(){}?Is it  mean that a interface can be consider as a class and serves every class.Hope someone can understand what i mean.Thanks a lot.

This is not a support forum.
Questions should be asked at StackOverflow or on Gitter.im.


gitpython version 3.1.29 has a RCE vulnerability (CVE-2022-24439)

Describe the bug
There is a Remote Code Execution vulnerability in all versions of gitpython.
See: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24439
Reproduction steps
1. Install bandit version 1.7.4
2. It requires gitpython >=1.0.1 (but installs 3.1.29)
3. gitpython 3.1.29 has the reported vulnerability

Expected behavior
Proper input validation for git URLs needs to exist so that it is NOT possible to inject a maliciously crafted remote URL into the clone command.
Bandit version
1.7.4 (Default)
Python version
3.11 (Default)
Additional context
No response

Closing for now since GitHub has a new mechanism for reporting potential vulnerabilities. I have just enabled it. In the future you can open one here: https://github.com/PyCQA/bandit/security/advisories

It looks like gitpython has now patched this vulnerability https://github.com/gitpython-developers/GitPython/issues/1515#issuecomment-1367120052


access: +2 and Editors for roland@

@rolandshoemaker joined the Go Security team 🎉
Please grant him access to GitHub (https://github.com/orgs/golang/teams/go-approvers, @rolandshoemaker) and Gerrit (https://go-review.googlesource.com/#/admin/groups/1005,members, rolandshoemaker@gmail.com).
See https://golang.org/wiki/GithubAccess. /cc @golang/osp-team

Done. Welcome, Roland!


.Hidden() alternative

Is there any way i can do the .Hidden() extension like .Hidden(false|true)?

No, you would have to create extension for your use.

Oh I see. Would love to see it as a feature if possible. Thanks anyway.

What's the point though? Currently there is only back end support for hiding the column, and you can't unhide it through any UI. So using .Hidden() is almost the same as not adding column at all.

I have an external search which depends on the user's lookup choice.
My grid datasource is like this:
public class ViewModel{
public bool HideUnhide{get;set;}
public IEnumerable<GridData> GridData {get;set;}}
and in my partial view:
@(Html.Grid(Model.GridData )
                            .Build(columns =>{
columns.Add(m => m.columnA).Titled("Column Title").Hidden(Model.HideUnhide);
HideUnhide will be set based on what the user chooses as search option.

I can do it using some hacky client-side jquery and css but i want to do less of it as much as possible

Would still go with
if (Model.HideUnhide)
    columns.Add(m => m.columnA).Titled("Column Title");

Less html to be rendered if you are not planning to unhide dynamically.


Nicer documentation

Personally I was thinking using this repo to get it going, thoughts?

Should we proceed with this? It would be quite an effort, and we're not in the league yet, though I understand it can be used outside of the league.

I think so, better documentation is always a good thing, and we can remove League-related stuff for now (and add it back in if Config is accepted)

I agree :+1.


No new podman releases in ubuntu ppa

Dear developers,
Can you please push podman 1.6.1 and all dependencies to ubuntu ppa?  I thought it was happening automatically.
Thank you in advance,

Didn't mean to sound rude.  My apologies.
@lsm5 Does the failure on ppa has to do with the latest change in autobulder?
https://gitlab.com/lsm5/rpm-builder/commit/da3aa936697c5171da8ef5261caec4ba8e5bf5f4
Looks like credentials changed and it possibly broke the pipeline.  Just a thought.
`

To gitlab:lsm5/podman.git
 + 8ec04502...3b589904 bionic -> bionic (forced update)
Branch 'bionic' set up to track remote branch 'bionic' from 'gitlab'.
Adding github mirror...
Pushing changes to github/podman...
To github:lsm5/podman.git
 + 1b423ce8...3b589904 bionic -> bionic (forced update)
Branch 'bionic' set up to track remote branch 'bionic' from 'github'.
Submitting build to PPA...
no such identity: /home/lsm5-bot/.ssh/id_rsa: No such file or directory
<EMAIL_ADDRESS>Permission denied (publickey).
gpg: ../podman_1.6.1-1~ubuntu18.04~ppa1_source.changes: Error checking signature from 6FD26B91A57D528C: SignatureVerifyError: 0
gpg: ../podman_1.6.1-1~ubuntu18.04~ppa1.dsc: Error checking signature from 6FD26B91A57D528C: SignatureVerifyError: 0
Checking signature on .changes
Checking signature on .dsc
Uploading to ppa (via sftp to ppa.launchpad.net):
EOF during negotiation
E: Error connecting to remote host.
Failed to send build to PPA. Exiting...
ERROR: Job failed: exit code 1

Launchpad is rejecting the GPG key used to sign the changes and dsc uploads, there's also a build failure for buildah (the ubuntu-specific rebase is failing)

ya, I probably messed up while changing identities. I'll put this on today's TODO.

.dput.cf in the container image used for CI still had my older id, which was causing ssh issues. The pipeline at https://gitlab.com/lsm5/rpm-builder/pipelines/87610518 seems to be working. Failures in buildah are merge conflicts which I'll fix later today. HTH.

:tada: PPA is up-to-date (except for buildah):
# apt list --upgradable
Listing... Done
conmon/bionic 2.0.1-1~ubuntu18.04~ppa3 amd64 [upgradable from: 2.0.0-1~ubuntu18.04~ppa2]
containernetworking-plugins/bionic 0.8.2-1~ubuntu18.04~ppa3 amd64 [upgradable from: 0.8.2-1~ubuntu18.04~ppa1]
containers-common/bionic,bionic 0.1.39-1~ubuntu18.04~ppa3 all [upgradable from: 0.1.39-1~ubuntu18.04~ppa1]
containers-golang/bionic,bionic 0.3.1-1~ubuntu18.04~ppa3 all [upgradable from: 0.3.1-1~ubuntu18.04~ppa1]
containers-image/bionic,bionic 4.0.1-1~ubuntu18.04~ppa3 all [upgradable from: 3.0.2-1~ubuntu18.04~ppa1]
libvarlink/bionic 18-2~ubuntu18.04~ppa4 amd64 [upgradable from: 18-2~ubuntu18.04~ppa2]
podman/bionic 1.6.1-1~ubuntu18.04~ppa3 amd64 [upgradable from: 1.5.1-1~ubuntu18.04~ppa1]
skopeo/bionic 0.1.39-1~ubuntu18.04~ppa3 amd64 [upgradable from: 0.1.39-1~ubuntu18.04~ppa1]
slirp4netns/bionic 0.4.1-1~ubuntu18.04~ppa4 amd64 [upgradable from: 0.4.1-1~ubuntu18.04~ppa2]

I guess this can be closed...

Issue opened for buildah: https://github.com/containers/buildah/issues/1918

Podman 1.6.3 not on Ubuntu not built

I thought that 1.6.3 was not released yet.

It is semi-released.  We have not built packages for Fedora yet.
@mheon What is the state?

It is released, but we're probably not building for Fedora. We're going to get a few more patches landed and make a separate 1.6.4 release specifically for Fedora (to better handle the F31 cgroupsv2 migration, among other things).

Nevertheless @lsm5 could you please check if the release can make it to ppa?  There are definitely some bug fixes I and others can be interested in.

Having 1.6.3 packaged for non-Fedora distros would finally land the fix for #4318, otherwise we'd have to wait for 1.6.5 (given that 1.6.4 would be a Fedora-specific release).

1.6.4 will not be a Fedora Specific release.  It is a release for anyone who wants to use cgroup V2.

So other than that is there a reason not to release package for ubuntu
users?  I believe the build on ppa is automatic.
On Thu, Nov 7, 2019, 9:31 AM Daniel J Walsh<EMAIL_ADDRESS>wrote:

1.6.4 will not be a Fedora Specific release. It is a release for anyone
who wants to use cgroup V2.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/containers/libpod/issues/4213?email_source=notifications&email_token=ABWJN3GY3IQQUF5ZW2NRDDLQSQYEDA5CNFSM4I6GBU2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDMZBNY#issuecomment-551129271,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABWJN3FUU2GDO5HVJYFGEDTQSQYEDANCNFSM4I6GBU2A
.

I think it ought to be autobuilding.

autobuilding yes, but afaict, it's broken atm, will take a look asap.

@lsm5 any news on 1.6.3 auto-building?

@lsm5 it looks like build of bionic failed with
make[1]: Entering directory '/<<PKGBUILDDIR>>' /usr/lib/go-1.13/bin/go generate ./cmd/podman/varlink/... make[1]: /usr/lib/go-1.13/bin/go: Command not found make[1]: *** [debian/rules:35: override_dh_auto_build] Error 127 make[1]: Leaving directory '/<<PKGBUILDDIR>>' make: *** [debian/rules:24: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 --------------------------------------------------------------------------------

@lsm5 any news on 1.6.3 auto-building?

some upcoming change in setup: https://github.com/containers/libpod/issues/1742#issuecomment-555061785 . So please wait a little longer, apologies about the lag.

@lsm5 I wanted to get away from the flame war involving debian guys.  I wonder if can answer few questions here.  Sorry for nube ones.
In OBS, I see a successful build of 1.6.3~15 but when going to download repo link I don't see the package version there.  I see 1.6.3~14.  Is it normal?
How much of the work is needed to make ubuntu packaging somewhat complete?  If Debian guys care more about there distribution maybe you can put out ubuntu ones first.  It may be selfish but there is nobody doing work integrating podman and friends with ubuntu from ubuntu community.  We are currently rewriting our VoIP platform to get away from rkt and some other non-supported orchestration tools so we are following podman development very closely and packaging helps us to push ahead.  So at least we will test and report the bugs if we get ones.

hey @alitvak69 appreciate your support, both podman use and on the thread! Not sure why the deb package isn't showing up, the buildlogs didn't show anything fishy. I just retriggered the build, let's see how it goes. And sure, I can prioritize ubuntu lts :)

i can see the deb here https://build.opensuse.org/package/binaries/home:rhcontainerbot:stable/podman/xUbuntu_18.04 .. but there's another issue with containers-common installation, which I'm fixing now ..

@lsm5
I see the package there as well
https://build.opensuse.org/package/binary/download/home:rhcontainerbot:stable/podman/xUbuntu_18.04/x86_64/podman_1.6.3~15_amd64.deb
However, it is not showing here:
https://download.opensuse.org/repositories/home:/rhcontainerbot:/stable/xUbuntu_18.04/
The download site is how I normally add and use repos in my opensuse and probably same for r other distros. The download repo link shows files dated by November 21st for bionic.  I.e. podman 1.6.3-14 and friends.
Looking forward to working with you and all libpod team members.

@lsm5
I see the package there as well
https://build.opensuse.org/package/binary/download/home:rhcontainerbot:stable/podman/xUbuntu_18.04/x86_64/podman_1.6.3~15_amd64.deb
However, it is not showing here:
https://download.opensuse.org/repositories/home:/rhcontainerbot:/stable/xUbuntu_18.04/

hmm, beats me. I'll check with OBS people on that.

The download site is how I normally add and use repos in my opensuse and probably same for r other distros. The download repo link shows files dated by November 21st for bionic. I.e. podman 1.6.3-14 and friends.

Btw, do you mean you use the following to add repos (of course, podman isn't installable atm, but this should help for repo addition)
For xUbuntu 18.04 run the following:
Keep in mind that the owner of the key may distribute updates, packages and repositories that your system will trust (more information).

sudo sh -c "echo 'deb http://download.opensuse.org/repositories/home:/rhcontainerbot:/stable/xUbuntu_18.04/ /' > /etc/apt/sources.list.d/home:rhcontainerbot:stable.list"
wget -nv https://download.opensuse.org/repositories/home:rhcontainerbot:stable/xUbuntu_18.04/Release.key -O Release.key
sudo apt-key add - < Release.key
sudo apt-get update
sudo apt-get install podman

Looking forward to working with you and all libpod team members.

Likewise, thanks again! :)

Yes this is the link I use.  And if you go there and then click on amd64 you will not find latest podman package i.e. 1.6.3-15, just 1.6.3-14.

Yes this is the link I use. And if you go there and then click on amd64 you will not find latest podman package i.e. 1.6.3-15, just 1.6.3-14.

Ack yes, I meant if those were the steps you used to install packages, as the steps to enable it weren't obvious on the OBS homepage, but I see what you mean. I'll ping OBS people, but don't think I'll have anything before Monday.

@lsm5 Any news about 1.6.3-15 in the repo or / and if 1.6.3 becoming installable on bionic?

hi @alitvak69 , sorry not yet, been involved in some other issues past 2 days, but today I managed to get skopeo and containers-common fixed, so the only pending thing is podman not being installable on 18.04, I'll try another rebuild later today, if it doesn't work, I'll ping OBS folks tomorrow morning.

sent 1.6.4 to OBS just now, fingers crossed..

hmm, seems like skopeo and containers-common are still not available on 18.04 repo (even though built successfully) along with podman. Let me check with OBS people tomorrow morning. Sorry about the delay.

Thank you for the updates.

@lsm5  Any news from OBS?  So far I see no changes.

@alitvak69 no response from OBS people on IRC, I'll keep trying. Meanwhile, I've begun sending packages to the testing repo (mostly same as stable repo but will have rc content as well) as well to see if things are any different.
The testing repo is at https://software.opensuse.org//download.html?project=home%3Arhcontainerbot%3Atesting&package=podman
Would you mind adding this repo as well and fetching podman from it? Please keep both stable and testing enabled since the latter doesn't have all packages included yet.
NOTE: This is only to get you unblocked immediately, and long term I plan to have everything working on a single repo itself.

Looks like their website down this morning.

I tested both repositories and were able to install podman 1.6.4 on ubuntu 18.04.   I hope that release propagation can be fixed.  They do have bugzilla FWIW

hey @alitvak69  the testing repo is now self-contained and will have 1.7.0-rc1 in a bit (right now 1.6.4 is installable). Could you please give it a try and report back any issues?

Testing repo works self-contained, installed 1.7.0-rc1.
It would be a good idea to fix stable because some people may stick with stable at some places.
Any chance that buildah will make to those repos as well?

Yes, I'll add buildah and fix stable too.
Btw, there's probably more changes upcoming to the repository location. I've been in discussions with @sysrich (thanks to @vrothberg) who maintains podman and other tools for openSUSE's kubic project, and I'll be moving our packages there, hopefully we can have a combined effort to accommodate majority distros and arches. I can update the stable subproject in there and get back to you.
Thanks again for helping out with testing!

Will the project-atomic PPA still be updated or do we have to use a new repo to get the latest podman release on Ubuntu? I'm not entirely sure if the the latest podman releases are already available via a package repository.

PPA won't be updated anymore. All new stuff going to OBS.
The kubic:libcontainers:stable project repo works now for podman 1.6.4, I'm working on buildah and cri-o now. Repo setup instructions can be found here: https://software.opensuse.org//download.html?project=devel%3Akubic%3Alibcontainers%3Astable&package=podman
Let me know if any issues..

buildah 1.12.0 should be available as well, cri-o coming up..

Works perfectly for me. Thank you!
It would be great if someone updated the installation instructions on the official homepage:
https://podman.io/getting-started/installation

Works perfectly for me. Thank you!
It would be great if someone updated the installation instructions on the official homepage:
https://podman.io/getting-started/installation

yup, I'll send a PR today. Thanks for testing this!

@lsm5 Found the issue with 1.6.4 build today, please take a look at #4734
Thank you

@lsm5 Sorry for bugging you, but could you add seccomp to your tags?

@lsm5 Sorry for bugging you, but could you add seccomp to your tags and push a new build?

No worries, always a pleasure to help dedicated podman users :) .. I sent 1.6.4~2 to OBS stable repo just now, should be available in an hour or less I guess.

is there a reason why conmon is not provided in the repo for arm64?

is there a reason why conmon is not provided in the repo for arm64?

@Knapoc the OBS build env is messed up for ubuntu on non-x86_64 arches. I'll nag them about it after new years. Happy holidays!


Documentation: Finalize the RepoDb vs Dapper page.

The communities keep asking the author what sets RepoDb apart from Dapper. In response to this, there should be a page where the communities should be able to visit and read when it comes to compelling reason why they should use RepoDb.
Links: https://github.com/mikependon/RepoDb/blob/master/RepoDb.Docs/RepoDb vs Dapper.md

The consolidated information is now checked-in and is now open to the .NET community.
Links: https://github.com/mikependon/RepoDb/blob/master/RepoDb.Docs/RepoDb vs Dapper.md


deep_sort on custom video

hello @ZQPei ,  i hope that you are doing well. i am going to use deep_sort to track custom objects (human head), i have darknet on my dataset ,  i have yolov3 model trained on head dataset.  when i tried to use deep-sort_yolov3 repository, the identification is erroneous. there is a huge difference between the ids of tracked objects. i want to use  the original deep_sort  repository, in order to track human in my own video. in deep_sort ,the detection ground truth is required. since i don't have the groundtruth label of my video, i am wondering , how can i use deep_sort to track objects in custom video. your suggestion will  be helpful.

hello @adouwitti
Since your goal is tracking human head, then original deep_sort repository will not be useful. Because that is for tracking human.
Here is my suggestions,

use SORT algorithm. SORT is basicly part of deep sort without deep feature, and is easy to run. However, SORT is bad at occlusion problems.
still use deep sort algorithm. But you will nead to train a good deep CNN model to compute human head feature first. You cannot use the parameter in ckpt.t7 in my repo directly, because it is for extracting human feature. Same reason on original deep sort repo.

@ZQPei  thanks for your response. i will not use SORT since it suffers from occlusion. first , i want to test your repository on my video.

@ZQPei  hello, i tried to run you demo on windows (cpu), but i couldnot , i was getting this message "  Torch not compiled with CUDA enabled " . i tried to run it on server (gpu) also, i am getting another error "cannot connect to x server". i  wanna test   original deep_sort  on my video to track people, since the code requires detection labels, i think that i should modify the code so that i can  test it on my video.  thanks

@adouwitti

If you want run on windows(cpu), please comment any line with net = net.cuda() or x = x.cuda(), and it will be super slow running on cpu.
If you want run it on server(gpu) without x server, which is a common user interface of linux, you should comment cv2.imshow(...) and cv2.waitKey(...). The result video will be saved automaticly by the control flag self.write_video = True.
You can also generate and save your detection results to feed into original deep_sort codes.

thanks for response.  i tried your suggestion and the error has disappeared. is there a script that generate detections for deep_sort ?  i am getting this

. thanks in advance

You overwrote my code, and error occurs...
identity shall be a digit number, and what is i in your code?

i didn't modify your code. but that message occurs

OK, this is a bug.
Can you tell me more information about it please?

hello @ZQPei , i hope that you are doing well. i am going to use deep_sort to track custom objects (human head), i have darknet on my dataset , i have yolov3 model trained on head dataset. when i tried to use deep-sort_yolov3 repository, the identification is erroneous. there is a huge difference between the ids of tracked objects. i want to use the original deep_sort repository, in order to track human in my own video. in deep_sort ,the detection ground truth is required. since i don't have the groundtruth label of my video, i am wondering , how can i use deep_sort to track objects in custom video. your suggestion will be helpful.

Hi,
Could you share the yolov3 model you train on the head dataset. We need a model like this.
Best Regards.

hi @m-peker , sorry I don't have permission  because, I was in internship when I trained yolov3 on head dataset. but if you have the dataset, I suggest you to have a look at this link https://github.com/AlexeyAB/darknet in order to train the model.

@adouwitti Thank you for your response. I know the training processes. But it takes too long. There are many images. And they all need to be labeled. I understand you too. Thanks again.

you are welcome. I am sorry,
I don't have the permission. thanks for your understanding.
Le lun. 6 avr. 2020 à 14:07, mpeker<EMAIL_ADDRESS>a écrit :

@adouwitti https://github.com/adouwitti Thank you for your response. I
know the training processes. But it takes too long. There are many images.
And they all need to be labeled. I understand you too. Thanks again.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ZQPei/deep_sort_pytorch/issues/22#issuecomment-609584057,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKV7UJLDJV5EADDNI5QVJDTRLFWSFANCNFSM4HHU2YYA
.


File: label_studio_ml/model.py label_studio_sdk.label_interface does not exist anymore

Hello all,
The model.py file uses a module that no longer exists in the Label Studio Python SDK.
In line 25: from label_studio_sdk.label_interface import LabelInterface
Either the requirements need to be updated, so we know which version of the SDK to use or the usage of this module needs to be removed/replaced.
Many thanks and kind regards,
Justin

Hello, @justinmacp !
The ML backend uses the Label Studio Python SDK installed from the latest master branch
https://github.com/HumanSignal/label-studio-ml-backend/blob/master/requirements.txt#L8
Do you still face the issue if you force reinstall the packages?

Same issue, tried force installing manually. Doesn't work.

Went through the repo for label-studio-sdk. They have deprecated the labelInterface module so it would no longer work there would probably be an update on the requirements soon but till then you can use the older version of the sdk using pip install "label-studio-sdk<1". This fixed the issue for me.


Inconsistent calculations in CategoricalCrossentropy using logits

Describe the problem.
It seems like a bug in the calculation of cross entropy while calculating the log.
Describe the current behavior.
If the logits get too big, the calculation of CategoricalCrossEntropy is effected. We expect two of them to be same:
logits = tf.constant([[14.4, 10.1, 3.5]])
y_true = tf.constant([[1, 0, 0]], dtype=tf.float32)

cce_obj = keras.losses.CategoricalCrossentropy(
                      from_logits=True)(y_true, logits)

cce_obj_logits = keras.losses.CategoricalCrossentropy(
                      from_logits=False)(y_true, tf.nn.softmax(logits))

which returns the same value, 0.01349.
If the logits get bigger, they will return different values.
Describe the expected behavior.
Those two losses should produce the same result.

Do you want to contribute a PR? (yes/no): Yes. Thim seems like an issue while calculating the log in categorical cross entropy losses.

Standalone code to reproduce the issue.
Please check the gist here.
Edit (13/03/2023):
Here are the results when logits are larger:
logits = tf.constant([[14.4, 50.1, 3.5]], dtype = tf.float64)
y_true = tf.constant([[1, 0, 0]], dtype=tf.float64)

cce_obj = keras.losses.CategoricalCrossentropy(
                      from_logits=True)

loss = cce_obj(y_true, logits)
loss.numpy() # 35.7

cce_obj = keras.losses.CategoricalCrossentropy(
                      from_logits=False)

loss = cce_obj(y_true, tf.nn.softmax(logits))
loss.numpy() # 16.11

@Frightera,
This may be expected because the cross entropy operation is unstable and a suggestion would be to try with float64 everywhere. Thank you!

Hi @tilakrayal,
For convention I'll copy paste what I mean:
import tensorflow as tf
from tensorflow import keras

logits = tf.constant([[14.4, 50.1, 3.5]], dtype=tf.float64)
y_true = tf.constant([[1, 0, 0]], dtype=tf.float64)

cce_obj = keras.losses.CategoricalCrossentropy(
                      from_logits=True)

loss = cce_obj(y_true, logits)
loss.numpy() # Returns 35.7

## -- Testing Keras backend calculation

cce_obj = keras.losses.CategoricalCrossentropy(
                      from_logits=False)

loss = cce_obj(y_true, tf.nn.softmax(logits))
loss.numpy() # Returns 16.11

So it has nothing to do with tf.float64, please check the gist for the comparison, thanks.

Tracking down the issue, it is because of the values are clipped:
https://github.com/keras-team/keras/blob/0468c5cfd09a4d4bed7b810b58c14c3278231120/keras/backend.py#L5572-L5574

@tilakrayal
I think you missed the above comments. Could you please add team-review-pending tag so this can be further discussed?

@sachinprasadhs,
I was able to reproduce the issue on tensorflow v2.11 and tf-nightly. Kindly find the gist of it here.

@sachinprasadhs
Is there any specific reason why 1e-7 is used as epsilon for cross entropy losses?
This creates confusion from time to time: https://stackoverflow.com/questions/76494166/why-tf-keras-losses-categoricalcrossentropy-result-different-to-tf-nn-softmax-cr/76495702
Maybe this value can be changed for CE losses.

1e-7 epsilon value is added as it is in the acceptable range of precession errors and it does not cause big difference in numerical computations.
Refer the comment here for more details https://github.com/tensorflow/tensorflow/issues/60113#issuecomment-1504081934


s2i build error: Invalid reference format

Hello everyone,
I am running into an s2i build error invalid reference format and I couldn't find any solution for this. can  you guys help me out in solving this ???.
I0810 16:51:38.781182     320 sti.go:369] error: Execution of post execute step failed
I0810 16:51:38.781208     320 docker.go:948] Removing container "bcc0f25b8e884536e242e132b755a723cc63ee49d1f09c5587cdbae7aa3cee7e" ...
I0810 16:51:38.800286     320 docker.go:952] Removed container "bcc0f25b8e884536e242e132b755a723cc63ee49d1f09c5587cdbae7aa3cee7e"
I0810 16:51:38.800796     320 cleanup.go:33] Removing temporary directory /tmp/s2i524513920
I0810 16:51:38.800830     320 fs.go:159] Removing directory '/tmp/s2i524513920'
E0810 16:51:38.808576     320 main.go:358] An error occurred: building ptf-pick-controller-1-0- failed when committing the image due to error: invalid reference format
E0810 16:51:38.808604     320 main.go:359] Suggested solution: check the build output for errors
I0810 16:51:38.808615     320 main.go:361] # _Details: invalid reference format
E0810 16:51:38.808623     320 main.go:365] If the problem persists consult the docs at https://github.com/openshift/source-to-image/tree/master/docs. Eventually reach us on freenode #openshift or file an issue at https://github.com/openshift/source-to-image/issues providing us with a log from your build using --loglevel=3

closing due to lack of information.


Updates after repository transfer

Should there also be an action for publishing to npm? (or will that be done manually?)

@ptrus, did you just volunteer for that :slightly_smiling_face:?

Should there also be an action for publishing to npm? (or will that be done manually?)

Also for the release process, but let's do that separately once we introduce a proper release process (will open an issue).


Update fulcrum.md to include NGINX reverse proxy configuration

What
Need to configure NGINX reverse proxy for Fulcrum, otherwise SSL connection won't work.
Why
Otherwise SSL connection won't work.
How
Create NGINX config file for Fulcrum; method copied from the Electrs guide.

It works perfectly on my RaspiBolt mainnet & testnet node:

NACK

Fulcrum does not need NGINX config to work with SSL

Fulcrum does not need NGINX config to work with SSL

Okay, thanks. I did a clean install on a PC running Debian 12 (no electrs or other electrum install) and it didn’t work for me — until I created an NGINX config file for it. I’ll go back, delete the file and see what happens.


Are there any command line options that can improve the resolution

Some generations seem a bit grainy, is there a way from the command line to increase the resolution? I want to see if there is anything I can do here before trying to get this to work with SDXL.

You can try latent view size of 128 (check the config.py file). Though it seemed that using an even higher resolution using SD1.5 might have negative impact on the image quality?

--latent_tex_size=2048 --latent_view_size=192 seems to help significantly for my use case

Interesting. Would you mind sharing the use case you are working on, and the comparisons before and after the resolution change if possible? By the way, did you face any memory issue when you go for a larger resolution?

Buildings. So far I've gotten ride of the prompts for "side", "front", "back" and use 4 cameras above (3 at 3 different angles and one straight above) and then I use 3 on the bottom. Yes, I run out of memory on a 4090 an the above parameters are basically the limits of what 24GB Vram GPU can handle. I also use a building fine tuned model from CivitAI instead of standard SD.

@jloveric I'm also working on building texture generation. Could you provide more clues about the use of prompts  for "side," "front," "back"? In addition, the building fine tuned model from CivitAI. Can this model be shared?

@jloveric Hello, can you help me to generate different styles of building textures, for example, the prompt text: modern style residential building, red bricks wall, wooden roof, etc,
The obj of the building can be downloaded from this website https://free3d.com/3d-model/buildinghouse-04-40137.html
Thank you very much. Looking forward to your reply.

Buildings. So far I've gotten ride of the prompts for "side", "front", "back" and use 4 cameras above (3 at 3 different angles and one straight above) and then I use 3 on the bottom. Yes, I run out of memory on a 4090 an the above parameters are basically the limits of what 24GB Vram GPU can handle. I also use a building fine tuned model from CivitAI instead of standard SD.

@jloveric I'm also working on building texture generation. Could you provide more clues about the use of prompts for "side," "front," "back"?
In addition, the model you mentioned was trained and fine-tuned from CivitAI through what process exactly? Could you provide more advice if possible? It would be great if you could share the model files. Thank you very much.

@jloveric @LIU-Yuxin I have another question. When the building model is very simple, even represented by just a simple cuboid, the generated textures for such a simple building appear too basic. The facade of the building may just have a plain color without any structural details such as windows or balconies being generated. I would like to hear some suggestions on how to improve this. Thank you.

@bdcms1 This is one of my forks of the repo where I have some of my changes https://github.com/LIU-Yuxin/SyncMVD/compare/main...jloveric:SyncMVD:main and you can see it looks like I used architecturerealmix_v1repair from civitAI (I may have found a version on hugging face...). Also there is one other parameter I had to switch, I believe it was "depth" vs "normal" for the controlnet. You need to use "depth" if I recall.

@jloveric @LIU-Yuxin I have another question. When the building model is very simple, even represented by just a simple cuboid, the generated textures for such a simple building appear too basic. The facade of the building may just have a plain color without any structural details such as windows or balconies being generated. I would like to hear some suggestions on how to improve this. Thank you.

I have updated an extra hyper parameter in the latest commit. It will help the generation of some fine details when the sd+controlnet model is uncertain about the object appearance, for example, the chair sample in the readme page. You may try it out, but not very certain if it will help in your specific case.

Thank you very much for your assistance. I truly appreciate it. I also wanted to inquire if SyncMVD supports using image prompt. Additionally, do you have any recommendations or tips for utilizing image prompt effectively?


Bad param passed into EventManager::attachAggregate

We have in \Zend\EventManager\EventManager::attach:
        // Proxy ListenerAggregateInterface arguments to attachAggregate()
        if ($event instanceof ListenerAggregateInterface) {
            return $this->attachAggregate($event, $callback);
        }

https://github.com/zendframework/zf2/blob/master/library/Zend/EventManager/EventManager.php#L279
but the \Zend\EventManager\EventManager::attachAggregate looks like:
    public function attachAggregate(ListenerAggregateInterface $aggregate, $priority = 1)
    {
        return $aggregate->attach($this, $priority);
    }

shouldn't be there:
$this->attachAggregate($event, $priority);

?
But it's still probably wrong, as long as \Zend\EventManager\ListenerAggregateInterface::attach has only one param...

This won't fix because on v3 Aggregate listeners not exists and this is not enough important for to be applied on 2.4 LTS


Saving base64 string as a tmp file in Electron then trying to print

Trying to print a pdf from a base64 and having a couple of problems
const base64String = require('../assets/pdf.json'); // Update the path as needed

const pdfBuffer = Buffer.from(base64String.pdfData, 'base64');

const app = remote.app;

const tempFilePath = path.join(app.getPath('temp'), 'temp_pdf.pdf');

fs.writeFile(tempFilePath, pdfBuffer, (err) => {
  if (err) {
    console.error('Error writing PDF:', err);
    return;
  }

  console.log('PDF saved:', tempFilePath);
  this.printPDF(tempFilePath);
});

printPDF(tempFilePath){
  let options = {
    printer: 'Zebra Technologies ZTC GK420d',
    size: 'custom_4x2in_4x2in'
  };

  print(tempFilePath, options)
  .then(result => {
    console.log(result);
  }).catch(error => {
    console.error(error);
  })
}

console.log from pdf saving:
PDF saved: /var/folders/hy/zd7d20y91vx7w1l7s53z2y5xv18rb0/T/temp_pdf.pdf
Error from print function:
Error: Command failed: lp '/var/folders/hy/zd7d20y91vx7w1l7s53z2y5xv18rb0/T/temp_pdf.pdf' -d [object Object] lp: Error - unable to access “Object]” - No such file or directory
I have also tried creating a blob and printing that but I get this error in the print function:
No such file

Never mind, was using pdf-to-printer syntax, coding on a mac for an app that will be on a windows machine...


Unable to fing AdoptOpenJDK8 build with Shenondoah GC algo. Please suggest

The default codebase for jdk8u which adoptopenjdk uses does not have Shenandoah support, although there is an alternate repository in mercurial for it.

@samifazal2004 Which platform is this for and is it possible for you to move to OpenJDK 11?

ZGC is in JDK 11. Shenandoah was integrated with JDK 12. All of the Red Hat builds include Shenandoah since jdk8u, apparently, but you'd need to go to them for that.

Hi,
Request you to share the link for the same
Br//
Sami
On Wed, Apr 3, 2019 at 10:19 PM Stewart X Addison<EMAIL_ADDRESS>wrote:

The default codebase for jdk8u which adoptopenjdk uses does not have
Shenandoah support, although there is an alternate repository in mercurial
for it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/AdoptOpenJDK/openjdk-build/issues/1010#issuecomment-479570464,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALl9B--tF_WNbY5RtClBcy9XVLRQy-isks5vdNu2gaJpZM4cZykZ
.

--
Br,
Sami Fazal
+919887005319


How to use SubscribeOnMainThread? It seems never working

Simple code for test. ObserveOnMainThread works perfectly. Is there something I misunderstand with
SubscribeOnMainThread?
Observable.Start(() => Unit.Default) // asynchronous work
    .SubscribeOnMainThread()
    .Subscribe(_ =>
    {
        GameObject.CreatePrimitive(PrimitiveType.Cube);
    });

I read the code and find that SubscribeOnObservable line:24. observer is subscribed to source and source never knows the scheduler.
m.Disposable = scheduler.Schedule(() =>
            {
                d.Disposable = new ScheduledDisposable(scheduler, source.Subscribe(observer));
            });

Well, it seems like the issues that I encountered with, happened due to Unity's bug:
(827984) - Scripting: Fixed deadlocks and pauses when using System.Threading.Monitor.
After promoting my Unity version to 2017.3.03p the deadlock and pauses vanished :)

SubscribeOnMainThread means that you are subscribing (therefore starting the task [for cold observables]) in main thread whereas ObserveOnMainThread means that you are observing (listening) onNext messages in main thread.
When you are using Observable.Start method, the task will be run on the ThreadPool by default. So use it with the ObserveOnMainThread to access Unity API in the Subscribe method.

Hi @dogramacigokhan ,
Thank you very much!


Format markdown

Produced via: prettier --write --prose-wrap=always $(find -name '*.md' | grep -v vendor | grep -v .github)

/close
Already taken care in https://github.com/knative/build-pipeline/pull/349
cc @mattmoor we should update the bot to open a new PR only if there is not a existing one :angel:


Forwarding VIRTUAL_HOST to other containers in docker-compose.yml

I'm using a docker-compose.yml to run my web app and have brought in nginx-proxy as a container:
# docker-compose.yml

nginxproxy:
   restart: always
   image: jwilder/nginx-proxy
   volumes:
     - /var/run/docker.sock:/tmp/docker.sock:ro
   ports:
     - "80:80"

web:
  build: .
  command: ./script/start_docker
  environment:
    VIRTUAL_HOST: app.docker
    VIRTUAL_PORT: 3000
  ports:
    - "3000:3000"
    - "3010:3010"
  links:
    ...

other-container:
  ...
  ^^ can't reach app.docker:3000

This works fine and is reachable by my web app container if I pass a VIRTUAL_HOST=app.docker and VIRTUAL_PORT=3000. However, in other containers, where I'd like to reach the VIRTUAL_HOST, I can't. Even in my "web" container I can't curl by the VIRTUAL_HOST. Any ideas how to make the VIRTUAL_HOST available on my other containers? Do I need to pass VIRTUAL_HOST for every container? I'm still unsure. Any help would be appreciated. Thanks.

You need to send the request from your other containers to your nginxproxy container's port 80 and specify the correct Host header. You could probably specify some extra_hosts config options to your other containers to create hosts entry for app.docker   <your host ip>.    You could also look at: http://engineering.ifttt.com/oss/2015/10/06/developing-with-docker/ which uses dnsmasq to handle DNS resolution locally.

@jwilder thanks for response.
Okay, that makes sense. It seemed I was missing a step somewhere. It was almost too easy ;). I'll take a look at both solutions. Thanks.


add new icon

Story/Ticket Reference ID from JIRA:
https://intersective.atlassian.net/browse/AV2-854
Additional Comments:
Add here
Checklist:

[ x ] Unit test completed?: (Y/N)
[ x ] Docs folder up to date?: (Y/N)
[ x ] Add if anything missed: (Y/N)

All Checklist are okay.
This PR looks great - it's ready to merge! Please review and let's ship it. :)

@ronakamani could you please attach a screenshot or a video of the result to the jira story? Thank you 🙏


Release

Would you mind cutting a release build with current master?
https://github.com/Netflix/PigPen/commit/939c4c1bc2ef55968d50661346998b0057ff05bc

Sure - np
-Matt
On Wednesday, February 18, 2015 at 9:55 AM, Kurt Harriger wrote:

Would you mind cutting a release build with current master?
939c4c1 (https://github.com/Netflix/PigPen/commit/939c4c1bc2ef55968d50661346998b0057ff05bc)
—
Reply to this email directly or view it on GitHub (https://github.com/Netflix/PigPen/issues/130).

Released as 0.2.14 to maven. Should show up within an hour or so.


Playerstats - Incorrect wire format

Incorrect wire format for field 3, expected: 0 got: 2
Incorrect wire format for field 10, expected: 0 got: 2

Can you try adding [packed=true] behind field 3 and 10, and then recompile?
Like done here https://github.com/AeonLucid/POGOProtos/blob/d20dcab6dded587399b1bfc54430bb7536f5adfa/src/POGOProtos/Data/Capture/CaptureAward.proto#L9.
I remember that this was a fix for errors like that sometimes.

Thanks, closing this issue.


test: support validating allowed_errors against a logfile

this will make it easier to test if an added allowed_error does in fact match.
this version does not however work, asking help from @bayandin:
$ poetry run python3 test_runner/fixtures/neon_fixtures.py --help
Traceback (most recent call last):
  File "/home/admin/src/neon/neon/test_runner/fixtures/neon_fixtures.py", line 42, in <module>
    from fixtures.broker import NeonBroker
ModuleNotFoundError: No module named 'fixtures'

Ok, now it works, updating description.


Fast-serve updated to the latest version and serve warnings fixed.

Q
A

Enhancement
✅

New feature?

New sample?

Related issues?

What's in this Pull Request?
Fast-serve was updated to the latest version, which additionally improves rebuild speed 2-3x times. Also some webpack warnings were fixed for fast-serve (basically the export of interfaces with type keyword and also css value was missing flex attribute)

@s-KaiNet you are awesome! Many thanks for the update!


[INTER-4629] [INTER-4630] Create Express Pay API Endpoints

Resolves INTER-4629
Resolves INTER-4630
Adds new Magento Web API endpoints for creating, updating and retrieving Express Pay (mobile wallet) orders.

URI
Method
Parameters
Returns

/V1/express_pay/order/create
POST
quote_mask_id,gateway_id
paypal_order_id

/V1/express_pay/order/mine/create
POST
quote_id,gateway_id
paypal_order_id

/V1/express_pay/order/update
POST
quote_mask_id,paypal_order_id
VOID

/V1/express_pay/order/mine/update
POST
quote_id,paypal_order_id
VOID

/V1/express_pay/order/get
POST
paypal_order_id,gateway_id
See spec

/V1/express_pay/order/mine/get
POST
paypal_order_id,gateway_id
See spec

Full spec

I think we might want to create our own feature branch off of the v2 work being done on branch INTER-3706 and merge this in there instead of into main. That way we can be sure we're in line and compatible with v2 for when it's ready. Let me know what you think so I can coordinate the front end work as well.

I was thinking about this. I'm planning to see what needs to be done to make it compatible.


Improve default configuration for Zen

Description
Users are frequently having trouble configuring their Zen node to form enough contracts for use. It can often be frustrating to figure out why and get it to work.
Nodes on Zen should be able to function with minimal (initial) configuration. Since Zen uses paper money, I think it should be fine to increase the default pricing by a lot.
Version
No response
What operating system are you running (e.g. Ubuntu 22.04, macOS, Windows 11)?
No response
Anything else?
No response

Is it the pricing that is causing the issues for you? In theory the pricing on Mainnet and Zen should be quite similar and we are trying to make updating those prices very easy via recommendations.
I'm asking because we are hesitant to ship renterd with very high settings for Zen because Zen is meant to be a reflection of the mainnet to make sure the experience is the same. If we set high pricing for Zen by default, we are just ending up not testing that the price settings work and testing is really what Zen is for. Not just for app developers to test their applications but also for us to make sure renterd is working as expected.

I just created a fresh node. I eventually ended up with 3 contracts with only touching these settings. Allowance was configured based on default prices.

Only after waiting some time longer, price suggestions started popping up.


[EBPF] Add kmt.selftest task

What does this PR do?
Adds a new kmt.selftest task that can be used to ensure correctness of the KMT code and installation.
For now only basic tests are added, more tests can follow in subsequent PRs.
Motivation
Facilitating development and ensuring consistency when refactoring KMT code (e.g., future cross-compiling support).
Additional Notes

Some arguments have been added to other tasks to facilitate automated testing:

--yes argument to  kmt.gen-config so that changes to the config are applied without confirmation
--compile-only argument to kmt.prepare so that the consistency of the generated binaries can be checked without having to transfer them to VMs.

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/trigger-ci --variable RUN_ALL_BUILDS=true --variable RUN_KITCHEN_TESTS=true --variable RUN_E2E_TESTS=on --variable RUN_UNIT_TESTS=on --variable RUN_KMT_TESTS=on

/trigger-ci --variable RUN_ALL_BUILDS=true --variable RUN_KITCHEN_TESTS=true --variable RUN_E2E_TESTS=on --variable RUN_UNIT_TESTS=on --variable RUN_KMT_TESTS=on

/merge


[4.0] Stop swallowing test interruption exceptions thrown during XCTAssert evaluation.

4.0 merge of https://github.com/apple/swift/pull/10905.
Explanation: Fix the implementation of the XCTAssert functions so that test interruption exceptions thrown by XCTest during evaluation of the expression get rethrown rather than treated as an unexpected test failure.
Scope: This affects XCTest users that have set their test case's continueAfterFailure property to false. Without this change, that setting is effectively is effectively ignored for failures which occur while evaluating an assertion expression. The conditions for this are particularly common during UI tests.
Radar: rdar://problem/33255447
Risk: Very low. The change is isolated and the rethrowing behavior is well-understood and has been in use for the Objective-C version of the assertions for several releases.
Testing: CI testing, including a new unit test exercising this behavior.

@swift-ci please test


Notification overlaps save button

Wonderful app! I love it. Since I see UI/UX is a driving force behind the project, might I suggest that we change the notification placement or some other solution where it does not overlap with the save button when editing a page?

Thanks for the suggestion.
Since it doesn't seem that many others have found this to be a particular annoyance in the last few years I'm going to close this off. Moving the notification may make it easier to miss, and there's always a risk of overlapping something. Notifications will auto-hide anyway unless deemed important to be read, in which case a simple press will dismiss it.


Display problem with bash completion using fzf

[x] I have read through the manual page (man fzf)
[x] I have the latest version of fzf
[x] I have searched through the existing issues
OS

[x] Linux

Shell

[x] bash

Problem / Steps to reproduce
Lately I have been playing with bash completion, defining my own completion scripts to be sourced by bash-completion: https://github.com/scop/bash-completion. I can define a completion script for any command: my_command by placing it in file: ~/.local/share/bash-completion/completions/my_command and it will be sourced when bash is executed.
Although he does seem like the completion works as expected, I then have a display problem.
Here is an asciinema of the issue, where I go through the steps of coming up with an initial completion script for a completely fictitious command: my_command, before I adapt the same script with fzf. We can see the display being messed up, the result of the completion being written at the beginning of the line, overwritting the end of my PS1 and the current command: my_command.
https://asciinema.org/a/0KUWwuH60gSBoEPmLYlDeVtwH
I've been going through the options of: complete and compgen but I can't find anything relevant, I'm mostly lost here. Below is the completion script for the command: my_command. If used in conjunction with bash-completion, it can be placed under: ~/.local/share/bash-completion/completions/my_command and can be reloaded by running: $ exec bash and then typing: my_command <TAB>:
_my_command() {
  local cur="${COMP_WORDS[COMP_CWORD]}" prev="${COMP_WORDS[COMP_CWORD-1]}"
  stu=$(ls ~ | fzf)
  #stu="hi marc"
  COMPREPLY+=($(compgen -W "${stu[@]}" -- ${cur}))
  return 0
}

complete -F _my_command my_command

Any thoughts?

Sorry I'll close and re-raise the issue with my personal Github account.