Segfault in the test suite on Arch Linux

In the process of upgrading our (Arch Linux) package to 4.0.1 (from 3.3.6), I’ve encountered a segfault during the test suite (they are also some errors, but we will get to that once the segfault is solved):
============================= test session starts ==============================
platform linux -- Python 3.8.1, pytest-5.3.5, py-1.8.1, pluggy-0.13.1
PyQt5 5.14.1 -- Qt runtime 5.14.1 -- Qt compiled 5.14.1
rootdir: /build/spyder/src/spyder-4.0.1, inifile: pytest.ini
plugins: qt-3.3.0, mock-2.0.0, cov-2.8.1, xvfb-1.2.0, ordering-0.6, lazy-fixture-0.6.3, flaky-3.6.1
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-builduser'
collected 970 items

spyder/plugins/editor/widgets/tests/test_editorsplitter.py s             [  0%]
spyder/plugins/editor/widgets/tests/test_introspection.py ssssssssss     [  1%]
spyder/plugins/editor/widgets/tests/test_classfunc_selector.py s         [  1%]
spyder/plugins/editor/widgets/tests/test_folding.py sss                  [  1%]
spyder/plugins/editor/widgets/tests/test_hints_and_calltips.py sssssssss [  2%]
ss                                                                       [  2%]
spyder/plugins/editor/widgets/tests/test_warnings.py sssssss             [  3%]
spyder/plugins/completion/languageserver/tests/test_client.py ssssssssss [  4%]
                                                                         [  4%]
spyder/app/tests/test_cli_options.py .                                   [  4%]
spyder/app/tests/test_mainwindow.py ssssssssssssssssssssssssssssssssssss [  8%]
sssss.s..ssssssssssssssssssssss                                          [ 11%]
spyder/app/tests/test_tour.py .                                          [ 11%]
spyder/config/tests/test_base.py ...                                     [ 11%]
spyder/config/tests/test_manager.py ..                                   [ 12%]
spyder/config/tests/test_user.py ....................................... [ 16%]
..........................                                               [ 18%]
spyder/plugins/completion/fallback/tests/test_fallback.py s.ssssssssssss [ 20%]
                                                                         [ 20%]
spyder/plugins/completion/kite/parsing/tests/test_parsing.py .           [ 20%]
spyder/plugins/completion/kite/utils/tests/test_install.py s             [ 20%]
spyder/plugins/completion/languageserver/tests/test_lsp_config_dialog.py . [ 20%]
                                                                         [ 20%]
spyder/plugins/console/tests/test_plugin.py ..                           [ 20%]
spyder/plugins/editor/extensions/tests/test_closebrackets.py ........... [ 21%]
...                                                                      [ 22%]
spyder/plugins/editor/extensions/tests/test_closequotes.py ............. [ 23%]
........                                                                 [ 24%]
spyder/plugins/editor/extensions/tests/test_docstring.py ............... [ 25%]
..............                                                           [ 27%]
spyder/plugins/editor/panels/tests/test_scrollflag.py .sss               [ 27%]
spyder/plugins/editor/tests/test_editor_config_dialog.py .               [ 27%]
spyder/plugins/editor/tests/test_plugin.py ................              [ 29%]
spyder/plugins/editor/utils/tests/test_autosave.py .................     [ 31%]
spyder/plugins/editor/widgets/tests/test_autocolon.py ..........xxx      [ 32%]
spyder/plugins/editor/widgets/tests/test_autoindent.py ................. [ 34%]
.............                                                            [ 35%]
spyder/plugins/editor/widgets/tests/test_autosaveerror.py .              [ 35%]
spyder/plugins/editor/widgets/tests/test_bookmarks.py ......             [ 36%]
spyder/plugins/editor/widgets/tests/test_breakpoints.py ......           [ 37%]
spyder/plugins/editor/widgets/tests/test_codeeditor.py ..s.............. [ 38%]
.......................                                                  [ 41%]
spyder/plugins/editor/widgets/tests/test_codeeditor_1.py ...........     [ 42%]
spyder/plugins/editor/widgets/tests/test_comments.py ..                  [ 42%]
spyder/plugins/editor/widgets/tests/test_editor.py .............s....... [ 44%]
.ss..............                                                        [ 46%]
spyder/plugins/editor/widgets/tests/test_editor_and_outline.py ......s.  [ 47%]
spyder/plugins/editor/widgets/tests/test_editorsplitter.py .......       [ 47%]
spyder/plugins/editor/widgets/tests/test_extra_selections.py .           [ 48%]
spyder/plugins/editor/widgets/tests/test_goto.py ...............FF       [ 49%]
spyder/plugins/editor/widgets/tests/test_indentation.py .......          [ 50%]
spyder/plugins/editor/widgets/tests/test_introspection.py s              [ 50%]
spyder/plugins/editor/widgets/tests/test_panels.py ........              [ 51%]
spyder/plugins/editor/widgets/tests/test_recover.py ...............     [ 52%]
spyder/plugins/editor/widgets/tests/test_save.py ........                [ 53%]
spyder/plugins/editor/widgets/tests/test_shortcuts.py .....sssss.s       [ 55%]
spyder/plugins/editor/widgets/tests/test_status.py .                     [ 55%]
spyder/plugins/explorer/tests/test_explorer_config_dialog.py .           [ 55%]
spyder/plugins/explorer/widgets/tests/test_explorer.py ................. [ 57%]
......................                                                   [ 59%]
spyder/plugins/explorer/widgets/tests/test_fileassociations.py ...       [ 59%]
spyder/plugins/findinfiles/tests/test_plugin.py .                        [ 59%]
spyder/plugins/findinfiles/tests/test_widgets.py ...................     [ 61%]
spyder/plugins/help/tests/test_plugin.py sss                             [ 61%]
spyder/plugins/help/tests/test_widgets.py ..                             [ 62%]
spyder/plugins/history/tests/test_history_config_dialog.py .             [ 62%]
spyder/plugins/history/tests/test_plugin.py .......                      [ 62%]
spyder/plugins/ipythonconsole/comms/tests/test_comms.py ..               [ 63%]
spyder/plugins/ipythonconsole/tests/test_ipython_config_dialog.py .      [ 63%]
spyder/plugins/ipythonconsole/tests/test_ipythonconsole.py ............. [ 64%]
.........F..s..Fs...........s.....                                       [ 68%]
spyder/plugins/ipythonconsole/utils/tests/test_spyder_kernel.py ...s     [ 68%]
spyder/plugins/ipythonconsole/widgets/tests/test_kernelconnect.py F.F.   [ 68%]
spyder/plugins/onlinehelp/tests/test_pydocgui.py ...                     [ 69%]
spyder/plugins/outlineexplorer/tests/test_outline_explorer.py .s         [ 69%]
spyder/plugins/outlineexplorer/tests/test_outline_explorer_editor.py .   [ 69%]
spyder/plugins/outlineexplorer/tests/test_widgets.py .......             [ 70%]
spyder/plugins/plots/widgets/tests/test_plots_widgets.py ............... [ 71%]
..............                                                           [ 73%]
spyder/plugins/profiler/tests/test_profiler.py ...                       [ 73%]
spyder/plugins/profiler/tests/test_profiler_config_dialog.py .           [ 73%]
spyder/plugins/projects/tests/test_plugin.py ..................          [ 75%]
spyder/plugins/projects/widgets/tests/test_configdialog.py .             [ 75%]
spyder/plugins/projects/widgets/tests/test_project.py ..                 [ 75%]
spyder/plugins/projects/widgets/tests/test_project_explorer.py ..        [ 76%]
spyder/plugins/projects/widgets/tests/test_projectdialog.py .s           [ 76%]
spyder/plugins/pylint/tests/test_pylint_config_dialog.py .               [ 76%]
spyder/plugins/variableexplorer/tests/test_variableexplorer.py .         [ 76%]
spyder/plugins/variableexplorer/tests/test_variableexplorer_config_dialog.py . [ 76%]
                                                                         [ 76%]
spyder/plugins/variableexplorer/widgets/objectexplorer/tests/test_objectexplorer.py . [ 76%]
.........                                                                [ 77%]
spyder/plugins/variableexplorer/widgets/tests/test_arrayeditor.py ...... [ 78%]
...s.........Fatal Python error: Aborted

Thread 0x00007f546dff9700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 306 in wait
  File "/usr/lib/python3.8/queue.py", line 179 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 361 in dispatch_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 196 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f54deffd700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 302 in wait
  File "/usr/lib/python3.8/site-packages/watchdog/utils/delayed_queue.py", line 54 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 43 in read_event
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify.py", line 131 in queue_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 145 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f54dd7fa700 (most recent call first):
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_c.py", line 311 in read_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 88 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f546f7fc700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 306 in wait
  File "/usr/lib/python3.8/queue.py", line 179 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 361 in dispatch_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 196 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f546fffd700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 302 in wait
  File "/usr/lib/python3.8/site-packages/watchdog/utils/delayed_queue.py", line 54 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 43 in read_event
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify.py", line 131 in queue_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 145 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f54bcff9700 (most recent call first):
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_c.py", line 311 in read_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 88 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f54bd7fa700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 306 in wait
  File "/usr/lib/python3.8/queue.py", line 179 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 361 in dispatch_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 196 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f54bdffb700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 302 in wait
  File "/usr/lib/python3.8/site-packages/watchdog/utils/delayed_queue.py", line 54 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 43 in read_event
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify.py", line 131 in queue_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 145 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f54be7fc700 (most recent call first):
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_c.py", line 311 in read_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 88 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f54df7fe700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 306 in wait
  File "/usr/lib/python3.8/queue.py", line 179 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 361 in dispatch_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 196 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f54dffff700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 302 in wait
  File "/usr/lib/python3.8/site-packages/watchdog/utils/delayed_queue.py", line 54 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 43 in read_event
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify.py", line 131 in queue_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 145 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f54fcff9700 (most recent call first):
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_c.py", line 311 in read_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 88 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f54fdffb700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 306 in wait
  File "/usr/lib/python3.8/queue.py", line 179 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 361 in dispatch_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 196 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f54fe7fc700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 302 in wait
  File "/usr/lib/python3.8/site-packages/watchdog/utils/delayed_queue.py", line 54 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 43 in read_event
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify.py", line 131 in queue_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 145 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f54feffd700 (most recent call first):
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_c.py", line 311 in read_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 88 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f54ff7fe700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 306 in wait
  File "/usr/lib/python3.8/queue.py", line 179 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 361 in dispatch_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 196 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f54fffff700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 302 in wait
  File "/usr/lib/python3.8/site-packages/watchdog/utils/delayed_queue.py", line 54 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 43 in read_event
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify.py", line 131 in queue_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 145 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f551cff9700 (most recent call first):
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_c.py", line 311 in read_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 88 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f551dffb700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 306 in wait
  File "/usr/lib/python3.8/queue.py", line 179 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 361 in dispatch_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 196 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f551e7fc700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 302 in wait
  File "/usr/lib/python3.8/site-packages/watchdog/utils/delayed_queue.py", line 54 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 43 in read_event
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify.py", line 131 in queue_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 145 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f563d7fa700 (most recent call first):
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_c.py", line 311 in read_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 88 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f5661ffb700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 306 in wait
  File "/usr/lib/python3.8/queue.py", line 179 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 361 in dispatch_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 196 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f55bdffb700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 302 in wait
  File "/usr/lib/python3.8/site-packages/watchdog/utils/delayed_queue.py", line 54 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 43 in read_event
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify.py", line 131 in queue_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 145 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f55bd7fa700 (most recent call first):
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_c.py", line 311 in read_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 88 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f553effd700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 306 in wait
  File "/usr/lib/python3.8/queue.py", line 179 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 361 in dispatch_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 196 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f555cff9700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 302 in wait
  File "/usr/lib/python3.8/site-packages/watchdog/utils/delayed_queue.py", line 54 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 43 in read_event
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify.py", line 131 in queue_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 145 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f551ffff700 (most recent call first):
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_c.py", line 311 in read_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 88 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f555effd700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 306 in wait
  File "/usr/lib/python3.8/queue.py", line 179 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 361 in dispatch_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 196 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f557ffff700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 302 in wait
  File "/usr/lib/python3.8/site-packages/watchdog/utils/delayed_queue.py", line 54 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 43 in read_event
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify.py", line 131 in queue_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 145 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f559cff9700 (most recent call first):
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_c.py", line 311 in read_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 88 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f55bf7fe700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 306 in wait
  File "/usr/lib/python3.8/queue.py", line 179 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 361 in dispatch_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 196 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f55bffff700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 302 in wait
  File "/usr/lib/python3.8/site-packages/watchdog/utils/delayed_queue.py", line 54 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 43 in read_event
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify.py", line 131 in queue_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 145 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f55beffd700 (most recent call first):
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_c.py", line 311 in read_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 88 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f55de7fc700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 306 in wait
  File "/usr/lib/python3.8/queue.py", line 179 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 361 in dispatch_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 196 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f55deffd700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 302 in wait
  File "/usr/lib/python3.8/site-packages/watchdog/utils/delayed_queue.py", line 54 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 43 in read_event
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify.py", line 131 in queue_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 145 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f55ddffb700 (most recent call first):
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_c.py", line 311 in read_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 88 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f55fd7fa700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 306 in wait
  File "/usr/lib/python3.8/queue.py", line 179 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 361 in dispatch_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 196 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f55fdffb700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 302 in wait
  File "/usr/lib/python3.8/site-packages/watchdog/utils/delayed_queue.py", line 54 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 43 in read_event
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify.py", line 131 in queue_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 145 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f561f7fe700 (most recent call first):
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_c.py", line 311 in read_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 88 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f5662ffd700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 306 in wait
  File "/usr/lib/python3.8/queue.py", line 179 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 361 in dispatch_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 196 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f5690fff700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 302 in wait
  File "/usr/lib/python3.8/site-packages/watchdog/utils/delayed_queue.py", line 54 in get
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 43 in read_event
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify.py", line 131 in queue_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/api.py", line 145 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f56637fe700 (most recent call first):
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_c.py", line 311 in read_events
  File "/usr/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 88 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f551d7fa700 (most recent call first):
  File "/build/spyder/src/spyder-4.0.1/spyder/plugins/onlinehelp/pydoc_patch.py", line 65 in serve_until_quit
  File "/build/spyder/src/spyder-4.0.1/spyder/plugins/onlinehelp/pydoc_patch.py", line 94 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f54ddffb700 (most recent call first):
  File "/build/spyder/src/spyder-4.0.1/spyder/plugins/onlinehelp/pydoc_patch.py", line 65 in serve_until_quit
  File "/build/spyder/src/spyder-4.0.1/spyder/plugins/onlinehelp/pydoc_patch.py", line 94 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f553dffb700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 302 in wait
  File "/usr/lib/python3.8/threading.py", line 558 in wait
  File "/usr/lib/python3.8/site-packages/IPython/core/history.py", line 829 in run
  File "/usr/lib/python3.8/site-packages/IPython/core/history.py", line 58 in needs_sqlite
  File "</usr/lib/python3.8/site-packages/decorator.py:decorator-gen-25>", line 2 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f55fe7fc700 (most recent call first):
  File "/usr/lib/python3.8/site-packages/zmq/sugar/poll.py", line 99 in poll
  File "/usr/lib/python3.8/site-packages/jupyter_client/channels.py", line 114 in _poll
  File "/usr/lib/python3.8/site-packages/jupyter_client/channels.py", line 151 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f561dffb700 (most recent call first):
  File "/usr/lib/python3.8/selectors.py", line 468 in select
  File "/usr/lib/python3.8/asyncio/base_events.py", line 1819 in _run_once
  File "/usr/lib/python3.8/asyncio/base_events.py", line 567 in run_forever
  File "/usr/lib/python3.8/site-packages/tornado/platform/asyncio.py", line 148 in start
  File "/usr/lib/python3.8/site-packages/jupyter_client/threaded.py", line 188 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f561e7fc700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 302 in wait
  File "/usr/lib/python3.8/threading.py", line 558 in wait
  File "/usr/lib/python3.8/site-packages/IPython/core/history.py", line 829 in run
  File "/usr/lib/python3.8/site-packages/IPython/core/history.py", line 58 in needs_sqlite
  File "</usr/lib/python3.8/site-packages/decorator.py:decorator-gen-25>", line 2 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f55feffd700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 302 in wait
  File "/usr/lib/python3.8/threading.py", line 558 in wait
  File "/usr/lib/python3.8/site-packages/IPython/core/history.py", line 829 in run
  File "/usr/lib/python3.8/site-packages/IPython/core/history.py", line 58 in needs_sqlite
  File "</usr/lib/python3.8/site-packages/decorator.py:decorator-gen-25>", line 2 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f561cff9700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 302 in wait
  File "/usr/lib/python3.8/threading.py", line 558 in wait
  File "/usr/lib/python3.8/site-packages/IPython/core/history.py", line 829 in run
  File "/usr/lib/python3.8/site-packages/IPython/core/history.py", line 58 in needs_sqlite
  File "</usr/lib/python3.8/site-packages/decorator.py:decorator-gen-25>", line 2 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f5660ff9700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 302 in wait
  File "/usr/lib/python3.8/threading.py", line 558 in wait
  File "/usr/lib/python3.8/site-packages/IPython/core/history.py", line 829 in run
  File "/usr/lib/python3.8/site-packages/IPython/core/history.py", line 58 in needs_sqlite
  File "</usr/lib/python3.8/site-packages/decorator.py:decorator-gen-25>", line 2 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f55dffff700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 302 in wait
  File "/usr/lib/python3.8/threading.py", line 558 in wait
  File "/usr/lib/python3.8/site-packages/IPython/core/history.py", line 829 in run
  File "/usr/lib/python3.8/site-packages/IPython/core/history.py", line 58 in needs_sqlite
  File "</usr/lib/python3.8/site-packages/decorator.py:decorator-gen-25>", line 2 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Thread 0x00007f54bffff700 (most recent call first):
  File "/usr/lib/python3.8/threading.py", line 302 in wait
  File "/usr/lib/python3.8/threading.py", line 558 in wait
  File "/usr/lib/python3.8/site-packages/IPython/core/history.py", line 829 in run
  File "/usr/lib/python3.8/site-packages/IPython/core/history.py", line 58 in needs_sqlite
  File "</usr/lib/python3.8/site-packages/decorator.py:decorator-gen-25>", line 2 in run
  File "/usr/lib/python3.8/threading.py", line 932 in _bootstrap_inner
  File "/usr/lib/python3.8/threading.py", line 890 in _bootstrap

Current thread 0x00007f57367aa740 (most recent call first):
  File "/usr/lib/python3.8/site-packages/pytestqt/qtbot.py", line 626 in result
  File "/build/spyder/src/spyder-4.0.1/spyder/plugins/variableexplorer/widgets/tests/test_arrayeditor.py", line 241 in test_arrayeditor_edit_complex_array
  File "/usr/lib/python3.8/site-packages/_pytest/python.py", line 167 in pytest_pyfunc_call
  File "/usr/lib/python3.8/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/usr/lib/python3.8/site-packages/pluggy/manager.py", line 84 in <lambda>
  File "/usr/lib/python3.8/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/usr/lib/python3.8/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/usr/lib/python3.8/site-packages/_pytest/python.py", line 1445 in runtest
  File "/usr/lib/python3.8/site-packages/_pytest/runner.py", line 134 in pytest_runtest_call
  File "/usr/lib/python3.8/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/usr/lib/python3.8/site-packages/pluggy/manager.py", line 84 in <lambda>
  File "/usr/lib/python3.8/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/usr/lib/python3.8/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/usr/lib/python3.8/site-packages/_pytest/runner.py", line 210 in <lambda>
  File "/usr/lib/python3.8/site-packages/_pytest/runner.py", line 237 in from_call
  File "/usr/lib/python3.8/site-packages/_pytest/runner.py", line 209 in call_runtest_hook
  File "/usr/lib/python3.8/site-packages/flaky/flaky_pytest_plugin.py", line 129 in call_and_report
  File "/usr/lib/python3.8/site-packages/_pytest/runner.py", line 99 in runtestprotocol
  File "/usr/lib/python3.8/site-packages/_pytest/runner.py", line 84 in pytest_runtest_protocol
  File "/usr/lib/python3.8/site-packages/flaky/flaky_pytest_plugin.py", line 92 in pytest_runtest_protocol
  File "/usr/lib/python3.8/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/usr/lib/python3.8/site-packages/pluggy/manager.py", line 84 in <lambda>
  File "/usr/lib/python3.8/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/usr/lib/python3.8/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/usr/lib/python3.8/site-packages/_pytest/main.py", line 271 in pytest_runtestloop
  File "/usr/lib/python3.8/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/usr/lib/python3.8/site-packages/pluggy/manager.py", line 84 in <lambda>
  File "/usr/lib/python3.8/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/usr/lib/python3.8/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/usr/lib/python3.8/site-packages/_pytest/main.py", line 247 in _main
  File "/usr/lib/python3.8/site-packages/_pytest/main.py", line 197 in wrap_session
  File "/usr/lib/python3.8/site-packages/_pytest/main.py", line 240 in pytest_cmdline_main
  File "/usr/lib/python3.8/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/usr/lib/python3.8/site-packages/pluggy/manager.py", line 84 in <lambda>
  File "/usr/lib/python3.8/site-packages/pluggy/manager.py", line 93 in _hookexec
  File "/usr/lib/python3.8/site-packages/pluggy/hooks.py", line 286 in __call__
  File "/usr/lib/python3.8/site-packages/_pytest/config/__init__.py", line 92 in main
  File "/usr/bin/pytest", line 11 in <module>
/startdir/PKGBUILD: line 87:  2667 Aborted                 (core dumped) pytest

Some packages version are outputed at the beginning of the test suite, any other can be retrieved by looking at the dependencies here.
I suppose the appropriate way of handling this is identifying the part of spyder that triggers this segfault, report it to the relevant upstream and workaround it in the testsuite meanwhile.

@andfoy I think you worked on the watchdog observers. Please take a look at this one

PyQt5 5.14.1 -- Qt runtime 5.14.1 -- Qt compiled 5.14.1

Updating to a new Qt/PyQt version is huge effort and we don't plan to do that until a new Qt Long Term Support (LTS) version is released (i.e. Qt/PyQt 5.15).
So sorry but I'm going to close this bug because we are not going to support Qt/PyQt 5.14. For the time being, please use Anaconda or pip. Both will correctly install PyQt 5.12 or older version, which are the ones that we support at the moment.

Of course, we will reconsider to open this bug if you send us a PR that make our test suite pass for Qt/PyQt 5.14 in all operating systems we support (i.e. Windows, macOS and Linux, not just Linux).

@ArchangeGabriel, sorry, I just saw that you're the Spyder maintainer on Arch. Still, the only way progress would be made on this front is for you to send us a PR as I described above, sorry.

Well indeed Anaconda is not a solution in this case, but since I don’t have the necessary knowledge of either Qt or your codebase to do this PR, we will do like Debian and Fedora and keep spyder 3.3.6 that works perfectly well with Qt 5.14 in the mean time. ;)

I'm sorry to say it but Linux distros are not our main distribution channel (and haven't been for years, actually). So we're fine with it.


DEVELOPMENT: Format the output of the report in a table.

The format done for display in console. Waiting for team's approval


Selection Bug

Describe the bug
File/Folder Select All Bug
To Reproduce
Steps to reproduce the behavior:

Select all from the bottom menu
Click Somewhere blank to clear the selection
now the normal click and the long click do not work at all for all files and folders

Desktop (please complete the following information):

OS Version: [e.g. Windows 10 1903 18363.815]
App version: [v<IP_ADDRESS>]

This also happens when a single file or folder is long pressed ( when the menu opens once this happens regardless of actually selecting an action or just dismissing the menu). By the way, I am using a surface with a touch screen.

Thank you for creating this feedback item. This issue is currently resolved in our active development branch and will be shipped soon once we've validated that everything works properly. Please subscribe to our releases to be notified when this is available.


Music Time for Spotify Extension host terminated unexpectedly on when opened javascript file in apple silicon on stable version.

Describe the bug
A clear and concise description of what the bug is.
Extension host terminated unexpectedly

ISSUE TYPE

Bug Report

Steps to reproduce

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.

ACTUAL RESULTS

Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. macOS]
Plugin version [e.g. Code Time v1.2.1]

Additional context
Add any other context about the problem here.

Thank you for the issue report and the error details. This helps and we'll look at this right away.
Regards.

Hi @premkumar5012002. I was able to reproduce a similar error and found that it may be due to opening a non-git based project. I've deployed a new version, v2.1.9, to fix that issue but let us know if there's any other issues, thank you.

Still facing the same bug after installing v2.1.9 on my apple silicon m1 version of macbook in vs code stable version.

Ok, my apologies about the previous update not resolving the issue. I'll work with a resource to see what may be happing today, thank you.

music for spotify extension working properly without issue.

again facing the same issue after the update.

Ok, thanks for the update. We'll look into this.

Hi @premkumar5012002 , do you have "git" installed? The errors seem related to git not being installed. It's ok if it's not installed, we need to make sure the plugin works without that but this information will help us reproduce the error, thank you.

Yes I have git. For git initiated it works fine but not for non-git projects.

I see, that helps. We should have a fix for this very soon based on that information, thank you.

We've reproduced the issue when opening vscode with a non-git based project and fixed the underlying problem. The fix is now in v2.1.13. Please let us know if there's any other issues. Thank you.


Bug in legendColor() updating?

I believe there is a bug in legendColor when passing it updated scales.  If I start with scale data like so (omitting quotes):
domain = [a, b, c]  and range = [green, blue, gold]
The initial legend renders fine.  But if I then call it again with:
domain = [b, c] and range = [blue, gold]
then the first two cells are both blue.
Likewise, updating by progressively dropping the last cell and adding it back  with subsequent calls causes the last cell color to repeat.
I am using D3 v4.  Looking at the source code, legendColor appears to be updating, exiting, and entering, but it is not updating correctly on the screen, and I can't see where the issue is.  I noted though that it does not appear to be using a key function.
This is being done on a closed system, so unfortunately I cannot post the code.

Would you be able to make a scaled down example in codepen?

I just ended up doing it by hand. But thank for following up. I also switched to one of the built in color scales versus a manual one I was using.
I was doing all this in an angular 4 app so TypeScript.  Maybe that was a factor?
Thanks,
John
Sent from my iPhone

On Nov 12, 2017, at 3:39 PM, Susie<EMAIL_ADDRESS>wrote:
Would you be able to make a scaled down example in codepen?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I'll see if I can replicate it in an example, thanks!


 First i'm sorry to make a request here.
I havent legit hacked on CSGO since some time but i remember using the recoil crosshair on a paid cheat (dont want to share names not sure if its allowed) and the crosshair was always visible. When you were not shooting it was at the middle, like a simple crosshair.
This allows people to play with the original game crosshair disabled (with the command crosshair 0), so you only have one, the recoil crosshair. Its SO MUCH better than having your two crosshairs at the same time. I think this is pretty important for legit hacking.
Hopefully someone explain me how i could do that by editing the code. Thank you.

well that was pretty easy,
go the the recoil crosshair code in Misc.cpp and remove the line that says the condition "if player is shooting" and voila.
The crosshair is shaking a little bit in game when you move (its really small) because our real recoil move when you move, its already WAY better like that, if anyone has an idea to make it stable when i'm not shooting feel free to tell me thank you!

well that was pretty easy,
go to the recoil crosshair code in Misc.cpp and remove the line that says the condition "if player is shooting" and voila.
The crosshair is shaking a little bit in game when you move (its really small) because our real recoil move when you move, its already WAY better like that, if anyone has an idea to make it stable when i'm not shooting feel free to tell me thank you!

Hey! Just draw the crosshair in the center of the screen if they are not shooting, otherwise run the default code. something like this...
// if the player is shooting, draw the recoil crosshair
if (localPlayerData.shooting)
{
   if (ImVec2 pos; Helpers::worldToScreenPixelAligned(localPlayerData.aimPunch, pos))
      drawCrosshair(drawList, pos, Helpers::calculateColor(miscConfig.recoilCrosshair.asColorToggle().asColor4()));
}
// otherwise draw in the center, to remove the shaking
else
{
   int w, h;
   interfaces->engine->getScreenSize(w, h); // get screen width/height
   // draw the crosshair in the center of the screen
   drawCrosshair(drawList, ImVec2(w/2, h/2), Helpers::calculateColor(miscConfig.recoilCrosshair.asColorToggle().asColor4()));
}

@Okay5041 Can't get in the middle. My resolution is 1280x720 (16:9) running CSGO on Linux.


Either don't create a new cell in the .py file on run and advance or allow an option

I personally don't like this, so figure that we can discuss this in triage. I like to use shift-enter to run cells, but I don't like my .py file being edited without asking.

Add a setting?


Casting non-string headers

First wanted to thank you for the effort of this plugin, it's been making my transition off of UIWebView so much easier for my use cases.
I've noticed one different behavior between the way the normal XHR method works with headers though. Previously if we set header values by enumerating a JSON object and call:
request.setRequestHeader(key, value);
If value is anything other than a string (in my case a number) the original XHR would cast it to a string and use it. It seems like this plugin throws out these values though when going through the header dictionary though:
if (![key isKindOfClass:NSString.class] || ![obj isKindOfClass:NSString.class])
return;
[request setValue:(NSString *)obj forHTTPHeaderField:(NSString *)key];
Would it be possible to add casting for numbers? I don't know Objective-C too well yet but something like this?
NSString* strKey = ![key isKindOfClass:NSString.class] ? [key stringValue] : (NSString *)key;
NSString* strValue = ![obj isKindOfClass:NSString.class] ? [obj stringValue] : (NSString *)obj;
[request setValue:strValue forHTTPHeaderField:strKey];
Thank you!

Thanks for reporting the issue.  I think we need to address this at the JavaScript level versus on the iOS side.  We should be normalizing the header values.
You might not have access to the JS code setting the header request values but that might be a workaround until we can get this addressed.
request.setRequestHeader(key, "" + value);

I don't have access to this specific JS like you said but I was able to put something in place in the meantime that seems to be working.
Normalizing at the JS level sounds good as well, thank you for the quick response!


New option to always show decimals

We have an requirement to always show the decimals even if there are all zero.
Example:
10.00 (instead of 10)
I think currently it is not possible to configure cleave to do it. So i suggest a new option in NumeralFormatter: alwaysShowDecimals (boolean)

Ich have a poc here: https://github.com/onlineandy/cleave.js/tree/option-show-decimals
But during typing it is a bad idea to add ".00" because it needs fixing the cursor postion. I think this is too complex to handle it well.
So I am closing this issue. If someone has a good idea to fix this, feel free to comment.

if no decimal value - add ".00" after left the field focus?

Hi, this fork (https://github.com/running-web-dev07/cleave.js) was modified the have the requested feature.
Take a look at
https://github.com/running-web-dev07/cleave.js/blob/master/test/browser/numeral-manual.html
to now how to configure.
Take advise that after the modifications i don't made any regression test to verify if i had broke others features.

Cool! exactly what I need! Thanks! Looking forward to see this feature on master!

One more question please - in french currency sign goes after the number
ex:  not $10,00 but 10.00$
I have multilang website and need to change the way price shows based on the selected language.
Is there a way to add $ at the end on the value?

was this implemented in the end?


Api and worker integration issue. Api never calls onFinish and repeats  is at 42%

I use the nexrender/api to push a job to the nexrender/server, that is then picked up by the nexrender/worker binary.
  console.log("project  JSON size" + memorySizeOf(project));
  const result = await client.addJob(project);
  return new Promise((resolve, reject) => {
    result.on('created', (job) => console.log('project has been created'));
    result.on('started', (job) => console.log('project rendering started'));
    result.on('progress', (job, percents) => console.log('project is at: ' + percents + '%'));
    result.on('finished', (job) => {
      console.log('project rendering finished');
      resolve(job);
    });
    result.on('error', (err) => {
      console.log('project rendering error', err);
      reject(err);
    });
  });

the logs of the binary are as expected.
the logs that reach  the api client are all out of order.

result.on(finish) is never called.  even after the worker has been finished for quite a while.
api logs:
Project JSON size: 9.384 MiB
project has been created
project rendering started
project is at: 9%
project is at: 9%
project is at: 9%
project is at: 9%
project is at: 9%
project is at: 9%
project is at: 9%
project is at: 9%
project is at: 9%
project is at: 1%
project is at: 34%
project is at: 75%
project is at: 84%
project is at: 84%
project is at: 67%
project is at: 50%
project is at: 76%
project is at: 42%
project is at: 42%
project is at: 42%
project is at: 42%
project is at: 42%
project is at: 42%
project is at: 42%
[project is at: 42%] //  infinite

what could be the  source of that?

Wow, that is indeed weird. Does it happen with all projects, or only with particular?
Does it maybe depend on project rendering time?
P.S. Nice picture :D

it happens with all projects that are of a certain size. i encode some scripts and assets in base64 and thus my projects are easily 10mb in size.
the issue was the implementation of the database. since its a pretty simple json file database, there is no caching or diffing. everytime the api or the worker post an update, the entire content of alll projects is read and written. since my proejcts are large, it gets slow. the issue above emerges from inconsistent io.
i went around this by saving the project body (assets, tempalte) in a seperate  file and keeping only meta info inside the database.
generally, everywhere in communication  with the server, you allways send the entire job object. this can/should be optimized.

Yeah, I see the issue. The job-network communication was not designed for "heavy" jobs. Probably a good thing to think about for the next major release.


@microsoft microsoft locked as too heated and limited conversation to collaborators

VSCode Version:
OS Version:

Steps to Reproduce:

Does this issue occur when all extensions are disabled?: Yes/No

That's just censorship.

inb4 thread locked for being too hot

I'm offended by temperatures above 30 degrees celsius

Stop censoring us!!! They are showing their true colors!

:fire:


Remaining Test cases for QANet

[x] Payments + snapp transactions from the same account are accepted
[x] A Snapp that's guaranteed to fail
[ ] Txns with multiple proofs
[ ] Update all the fields in one txn
[ ] transactions are ordered fee per weight unit
[ ] Max transactions per block

Note: currently, we can't use the parties in a snapp as sender or receiver in a payment, so the test uses separate accounts for the payment. That will change eventually, and the test can be updated to use the parties accounts in the payment.

Suggest adding a test that check snark work is happening for snapp transactions. This might be higher priority than
the tests for Transactions are ordered fee per weight unit and Max transactions per block

All the checklist items are done.


Issue Bridging native SUI

I'm running into issues when trying to bridge native SUI to any other chain, Im seeing a No valid gas coins found for the transaction. error. And I ONLY get this when bridging native SUI, not getting this for other assets like usdc or eth. Pasting the error trace below:
Transaction failed: Error: No valid gas coins found for the transaction.
    at _TransactionBlock.prepareGasPayment_fn (popup.js:723406:11)
    at async _TransactionBlock.prepare_fn (popup.js:723562:5)
    at async _TransactionBlock.build (popup.js:723308:5)
    at async WhSuiSigner.signAndSend (popup.js:591451:47)
    at async ssw (popup.js:791151:28)
    at async signSendWait (popup.js:791120:22)
    at async AutomaticTokenBridgeRoute.initiate (popup.js:793246:23)
    at async WormholeClient.executeSwap (popup.js:590902:25)
    at async sendTransactionWormhole (popup.js:569983:12)
    at async popup.js:570386:38

And when I try setting a gas owner, budget & payment, I get a MutableObjectUsedMoreThanOnce error,
Error checking transaction input objects: MutableObjectUsedMoreThanOnce { object_id: 0x7f7...ce1fc8 }

I'm running into issues when trying to bridge native SUI to any other chain, Im seeing a No valid gas coins found for the transaction. error. And I ONLY get this when bridging native SUI, not getting this for other assets like usdc or eth. Pasting the error trace below:
Transaction failed: Error: No valid gas coins found for the transaction.
    at _TransactionBlock.prepareGasPayment_fn (popup.js:723406:11)
    at async _TransactionBlock.prepare_fn (popup.js:723562:5)
    at async _TransactionBlock.build (popup.js:723308:5)
    at async WhSuiSigner.signAndSend (popup.js:591451:47)
    at async ssw (popup.js:791151:28)
    at async signSendWait (popup.js:791120:22)
    at async AutomaticTokenBridgeRoute.initiate (popup.js:793246:23)
    at async WormholeClient.executeSwap (popup.js:590902:25)
    at async sendTransactionWormhole (popup.js:569983:12)
    at async popup.js:570386:38

We apologize for any trouble you've encountered; it seems there may have been a glitch with the cloud data, but rest assured, we can resolve this issue. To expedite the process, kindly follow the link below to reach our specialized support team:
Sologenic Support Request
Use the live chat button at the bottom right to connect with a support agent for prompt assistance.
Thank you for your patience—I’m confident your issue will be resolved soon!

@xhuppa there is no official Sui support team, so do not attempt to engage with such actors as the one that I just deleted (in case you saw the previous comment).
I will pass this to the right team member and have a look at it asap. Thanks for the report!

Yes

It does not sound like you are using the native bridge in Sui. Are you using Wormhole or another bridge?

@xhuppa thanks for confirming. We'd suggest to ask the Wormhole folks on how to deal with this error, that's probably the best place to get help!

@stefan-mysten Im not sure if this is a wormhole issue, regardless of the bridge I use, Im getting this error when trying to build the transaction using the mysten sdk.
I'm able to build any other tx, but when I build a native SUI tx I run into this issue. Heres some code for context:
   const { transaction } = txn as {
        transaction: SuiTransaction;
      };
      transaction.setSender(senderAddress);
      transaction.setGasBudget(SUI_DEFAULT_TX_BUDGET);

      const serializedTransaction = await transaction.build({
        client: this.client.provider,
      });

      const dryRun = await this.client.simTransaction({
        tx: Buffer.from(serializedTransaction).toString("base64"),
        senderAddress,
      });


"sponsors.svg" and "backers.svg" are outdated

Describe the bug
"sponsors.svg" is outdated
To Reproduce
Steps to reproduce the behavior:

Go to 'https://opencollective.com/friends-of-groovy/sponsors.svg?width=890'
Compare the above sponsors with 'https://opencollective.com/friends-of-groovy'
Find the difference

Expected behavior
The sponsors in picture should be updated in time.
Desktop (please complete the following information):

OS: Win10
Browser Chrome
Version 72.0.3626.121

It's similar to:
https://github.com/opencollective/opencollective/issues/1368
https://github.com/opencollective/opencollective/issues/1578
This is happening because there is for historical reasons conflicting definitions of "Backers" and "Sponsors".

Tiers based: in your case $5+ -> "backer" $100+ -> "sponsor"
Type based: Supporting individual -> "backer", Supporting organization -> "sponsor"

In your Readme, this is the second definition that is currently used.
To match the "sponsor" tier, use:
https://opencollective.com/friends-of-groovy/tiers/sponsor.svg?width=890

Thanks for your quick response.
I have another similar issue: 'https://opencollective.com/friends-of-groovy/backers.svg?width=890' is outdated too... Some sponsors appear in the backers too...

For backers, same problem, similar answer, use:
https://opencollective.com/friends-of-groovy/tiers/backer.svg?width=890

Gotcha. Thanks :-)

@znarf
I found  'https://opencollective.com/friends-of-groovy/tiers/backer.svg?width=890' does not contains backer donating once(not monthly)...
How can I show all the backers?

Or how can I show backers donating once?

@danielsun1106 in these SVGs, it's unfortunately not possible to target only backers donating once at the moment.

OK. I see. Thanks.


optional chaining Syntax Highlight

There are syntax highlighting issues within the template using optional chaining
vscode v1.59.1
Volar v0.27.7

Please show your installed Extensions.

If I disable volar, I get vue files without any syntax highlighting.

<template>

id: {{ user?.id }}

</template>

It's works for me, I think the greater chance is the influence of other expansions.

The interesting thing is that your comment's code block has the same problem.

After I tried to disable the extensions one by one, I found that it was this extension that was affecting.
Thank you very much for your patient reply!


Set LED does not work

The LED api does not work, error below
  File "r2d2_hw1_solution.py", line 157, in <module>     api.set_front_led(Color(0, 255, 0))   File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/colour.py", line 983, in __init__     color = picker(pick_key(pick_for)) TypeError: 'int' object is not callable
And can you change the input to a common tuple instead of a colour object, the students have to import colour before using this api.

>>> api.set_main_led(Color(r=0, g=0, b=255))
Traceback (most recent call last):   File "r2d2_hw1_solution.py", line 157, in <module>     api.set_main_led(Color(r=0, g=0, b=255))   File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/colour.py", line 993, in __init__     setattr(self, k, v)   File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/colour.py", line 1005, in __setattr__     fc = getattr(self, 'set_' + label)   File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages/colour.py", line 1001, in __getattr__     raise AttributeError("'%s' not found" % label) AttributeError: 'set_r' not found

You should use Color from spherov2.types, e.g.
from spherov2 import scanner
from spherov2.sphero_edu import SpheroEduAPI
from spherov2.types import Color

toy = scanner.find_R2Q5()
with SpheroEduAPI(toy) as droid:
    droid.set_main_led(Color(r=0, g=0, b=255))


Front-End-Project : Calculator

-Adding more features of a Scientific calculator to the Existing Simple Calculator Using Javascript & adding corresponding Html and CSS.
Features like -
Trigonometric Operations
Logarithmic Operations
Exponential Operations
Inverse Operations
Inverse Trigonometric Operations

@TusharKesarwani sir this issue is assigned to me or not?

sir please assign this issue to me

@TusharKesarwani Please assign this issue to me under ssoc'23 program .

please open this issue


Incomplete module path emitted when using the 'node' module resolution strategy

Ok, so here we go... we're building a large app, and we really, really need this.
Background
Say I'm building a single page app structured like this, compiled using the node module resolution strategy and the AMD module format:
 app
 ├── module1
 │   ├── service1.ts
 │   ├── service1-helper.ts
 │   └── index.ts
 ├──  home.ts
 └──  home.html

Where home.ts represents a page in the app - it contains this:
import {Service1} from "./module1";
...

Where index.ts represents the interface of a complex module used by the page - it contains this:
export {Service1} from "./service1";
...

The compiler allows this, as the node strategy knows it should look for an index.ts file. This is a really nice way to structure things, as it allows us to keep things structured within module1 while at the same time ensuring that the rest of the app only needs a single import statement to use that module, without having to know anything about its internal structure.
The problem
Now, while this looks all fine in the editor, the generated javascript files will not actually load in the browser, as a loader like SystemJS does not know it should look for the index.js file. This is what the above home.ts compiles to:
define(["require", "exports", "./module1"], function (require, exports, module1_1) {
    ...

Here we see that even though the compiler resolved the import path to the index.ts file correctly, the emitted javascript does not actually reference that file - it still only references ./module1, which is obviously not a valid file path when the loader tries to load it.
Of course, I could just change all my imports to explicitly reference the index.ts file, but that is not just really annoying, it is also quite dangerous to rely on, as the compiler will not complain if I forget it - I will only see that error at runtime, when the app crashes because it can't find some module.
The solution
I believe this can be fixed very easily, by simply having the compiler emit the path including the /index part it resolved itself, thus resulting in this javascript:
define(["require", "exports", "./module1/index"], function (require, exports, module1_1) {
    ...

Now the module loader in the browser has a valid file path to load, and everything works beautifully. I see absolutely no reason not to do this, and it would make structuring large apps so much easier.
Is this something you could please consider for your next release?

@vladima You seem to be involved in all the module resolution stuff - could you please take a look at this really quick? It's something I feel is really important and it would help us a lot :-)

Module Resolution just allows the compiler to find declarations for your modules. the node resolution is mainly to allow you to use node-like systems just like how you would if you wrote directly in JavaScript. so node.js looks for index.js, so the ts compiler looks for index.ts/index.d.ts.
The compiler does not rewrite module names. module names have module-loader-specific semantics, any write the compiler does will break part of the population, e.g. loader plugins, loader configurations, post build scripts that are moving files around, module bundelers etc..
options, you can import the index directly, e.g. import m from "./module1/index", or you can just not use node module resolution.

I understand that, and maybe this issue is more complex than it appears, but if the compiler resolves the path to an index.ts file, then how much would it really hurt to simply rewrite the path to point to that file? - I mean, if the loader were to resolve that path any different than the compiler, then I wouldn't expect things to work correctly anyway... am I missing something?
It seems there are more and more people using node resolution for SPA's, and even the getting started guide for Angular 2 suggests it. There's clearly also a lot of people who find it's concept of an index.ts file / folder-as-module to be extremely helpful when structuring large projects, and I don't believe there is a similar concept of a default index file in the classic resolution mode, right? Would you consider adding such a feature?
Also, please note the problem with using node resolution and at the same time having to reference the index.ts file directly, is that the compiler would still be happy if it forgot it and only referenced the folder - but then at runtime, the loader will fail, and that's a nasty surprise. I'm sure that is confusing more than a few developers...
Finally, this issue aside, there seem to be so many changes going on with how path resolution works that I really miss some clear guidance and documentation on this whole thing - is the classic resolution even recommended anymore? it seems like all the talk is centered around node these days, and honestly I started getting the feeling that classic was more like legacy, and that you wanted to align more with the ES6 and node specifications going forward... So just to be clear, are you saying that classic is the officially recommended resolution strategy for new SPA projects? and if so, can you shed some light on why Angular 2 is going against that recommendation?

Actually, this quote is an example of why I'm confused about what is recommended:
https://github.com/Microsoft/TypeScript-Handbook/blob/master/pages/Module Resolution.md

Module Resolution Strategies

There are two possible module resolution strategies: Node and Classic. You can use the --moduleResolution flag to specify the module resolution strategy. The default if not specified is Node.

Classic

This used to be TypeScript's default resolution strategy. Nowadays, this strategy is mainly present for backward compatibility.

This very clearly states that classic is legacy and node is recommended, so it's a little strange that you guys so often point to that as the solution - honestly, it sometimes feel a little bit like you're focusing too much on server-side node apps, and that people writing for the browser are second-class citizens. From my point of view, it is a pretty big problem that the compiler is happy about code that will never actually work in the browser - such as an import statement pointing to a folder path.
I still strongly believe this needs to work - you absolutely need to do something about this.

This very clearly states that classic is legacy and node is recommended, so it's a little strange that you guys so often point to that as the solution - honestly, it sometimes feel a little bit like you're focusing too much on server-side node apps, and that people writing for the browser are second-class citizens.

The browser case is much simpler, it was working since 0.8.* time using classic module resolution. do not see this going away anytime soon. so do not see an issue using it.
The text in the documentation needs to be less harsh, and do not make it come out as a bad option. we have users with millions of lines of code using this option, and it is not going any where.
Node on the other hand was not working. you import a module from node_modules, and the compiler did not find it. so we added the node module resolution to support that.
The reason why it is recommended, is more library authors use npm as a mean of package distribution, e.g. angular, rxjs, react, etc.. these libraries, can bundle their definition files with them instead of their users having to go to definitely typed separately. node resolution makes this all work nicely.

I still strongly believe this needs to work - you absolutely need to do something about this.

not sure i understand the request here.

Fair enough - and yeah, the docs definitely need an update then :-)
But still, that means, that if I were to write an Angular 2 app, then I would still like to use node, as that would allow it to find the typings. But then the compiler will happily let me to import a folder path, without the /index part, even though this is guaranteed to fail at runtime when the browser tries to load it. That's a problem, and that's something that will confuse a lot of people - I know I was at first.
I fully understand that it is up to the loader to interpret module names, and that's fine for a loader running on the server - it can look at the file system and determine that a folder import should actually resolve to the index.js file. But in the browser, those import statements are always supposed to reference files - the loader in the browser can't possibly know whether an import is a file or folder, as it does not have access to the file system - so it always expects a file.
Therefore my request still stands:
In my opinion, the emitted path should include the /index part. Maybe what's really missing here is an option or a node-for-the-browser resolution strategy that enables this behavior?
If you won't do that, then at least an option to disallow import statements referencing folder paths, as those will fail in the browser anyway...

I would recommend then using classic as a module resolution technique, with baseUrl to point to your module root base URL.
For typings for used packages, e.g. angular2, i would use paths to specify where to locate them.
see https://github.com/Microsoft/TypeScript-Handbook/blob/release-2.0/pages/Module Resolution.md#path-mapping for more details.


Paperclip Button for File Attachments Not Displaying in ChatComposite

I am using the ChatComposite component from the @azure/communication-react package (version 1.6.0) to implement a chat feature in my Framework7 mobile app. However, I am facing an issue where the paperclip button for file attachments is not displaying within the ChatComposite.
I have configured the fileSharing option in the ChatComposite with proper uploadHandler and downloadHandler functions for file sharing. Despite the upgrade to version 1.6.0, the button is still not visible.
Steps to Reproduce:

Install @azure/communication-react version 1.6.0.
Implement the ChatComposite component with the file sharing options and appropriate handlers (uploadHandler and downloadHandler).
Authenticate the user and open the ChatComposite view.

Expected Result:
The ChatComposite should display a paperclip button for file attachments, allowing users to upload and download files.
Actual Result:
The paperclip button for file attachments is missing from the ChatComposite view, and users are unable to perform file sharing actions.
Additional Information:
I have tried testing the application in multiple environments (development, staging, production), but the issue persists.
There are no console errors or warnings related to the ChatComposite or file sharing functionality.
No custom CSS styles have been applied to the ChatComposite that could hide the button.
Environment:
@azure/communication-react: v1.6.0
React: 18.2.0
Browser: Google Chrome
Operating System: MacOS
Any assistance or insights into resolving this issue would be greatly appreciated. Thank you!

Hi @bogdanmartinescu,
Thanks for your patience, the file sharing feature is currently in public preview and isn't available in 1.6.0. I was able reproduce this issue and the attachment icon ("paperclip button") is indeed not available in this version.
To leverage this feature, please consider to use the beta version of the UI library. Furthermore, you can take a look of this documentation or check out the sample project
Please let me know if you have any more questions.
Thanks,
John

Hello @jpeng-ms ,
Thanks for pointing that out, managed to display the paperclip button in the end.
Thanks for your help!

No problem! Glad to know you got it working. I will go ahead and close this issue. Feel free to let me know if you run into any issues. Thanks!


[ansible] Fix Cluster Addons for CentOS

Cluster addons were fixed for coreos deployments with https://github.com/kubernetes/contrib/pull/672/files
However, the addons are not functioning for centos. Review https://github.com/kubernetes/contrib/pull/672/files and investigate why it only works on coreos, port the req'd functionality to centos

/cc: @rutsky @stephenrlouie @adamschaub

Having the same issue for redhat (should be similar to centos, I guess)

This should be fixed https://github.com/kubernetes/contrib/issues/886

Closing as duplicate of #886.


Fix bug in cwltoil tool

If no args are passed to cwltoil tool main method, use system args (the default None will cause exception on the [workdir] + args)

Can one of the admins verify this patch?

Jenkins, test this please.

@scottfrazer looks like this is the same thing you ran into.


ios build failed after updating to 3.7?

Could not build the precompiled application for the device.
Uncategorized (Xcode): Command CompileSwift failed with a nonzero exit code
Swift Compiler Error (Xcode): Type 'WKDataDetectorTypes' has no member 'WKDataDetectorTypes'
/Users/kp/.pub-cache/hosted/pub.dev/flutter_inappwebview-5.7.2+3/ios/Classes/Util.swift:85:20
I am not using flutter_inappwebview this package in used in your package as dependency so please update it to the new one .

i am facing same issue i don't know if you have found a solution yet


403 forbidden when using with oobabooga

An image says more than a hundred words, any idea what it can be?

It's because it's deployed on cloudflare, if it where local it would have worked.
Closing this issue


getting the build process to recognize a lower python version

I'm trying to get operon to install with Python 3.7 on systems that ship with Python 3.8. Every time, cmake's findpackage() for Python picks the newer version. It's relevant for srbench environment because one of the methods requires Python 3.7: https://github.com/EpistasisLab/srbench/runs/2424814127?check_suite_focus=true#step:6:48
I'm trying variations of build arguments like:
SOURCE_DATE_EPOCH=`date +%s` cmake .. -DCMAKE_BUILD_TYPE=Release  -DBUILD_PYBIND=ON -DUSE_OPENLIBM=ON -DUSE_SINGLE_PRECISION=ON -DCERES_TINY_SOLVER=ON -DPython3_EXECUTABLE=$CONDA_PREFIX/bin/python -DPython3_LIBRARY=$CONDA_PREFIX/lib/ -DPython3_INCLUDE_DIR=$CONDA_PREFIX/include/
#-DPython3_ROOT_DIR=$CONDA_PREFIX
# -DPython3_FIND_STRATEGY=LOCATION

Based on the cmake docs.
However, cmake either finds the newer version of Python or throws an errror.
Any ideas?

Hmm, maybe we can use pkg-config as a workaround. Could you try this patch:
diff --git a/CMakeLists.txt b/CMakeLists.txt
index d5af4c8..80f2c3c 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -20,9 +20,9 @@ find_package(Eigen3)
 find_package(Ceres)
 find_package(Threads)
 find_package(TBB)
-find_package(Python3 COMPONENTS Development Interpreter)
 find_package(pybind11)
 find_package(doctest)
+find_package(PkgConfig REQUIRED)

 # operon library
 set_package_properties(Git     PROPERTIES TYPE REQUIRED)
@@ -36,7 +36,7 @@ set_package_properties(doctest PROPERTIES TYPE OPTIONAL) # unit tests
 set_package_properties(cxxopts PROPERTIES TYPE OPTIONAL) # command-line parser

 # python binding
-set_package_properties(Python3 PROPERTIES TYPE OPTIONAL)
+pkg_check_modules(Python3 python-3.7 REQUIRED)
 set_package_properties(pybind11 PROPERTIES TYPE OPTIONAL)

 # get revision information from git

My hope is that pkg-config inside the conda environment will find the correct python version.

thanks for the help! the least intrusive option turned out to be building with -DPython3_FIND_VIRTUALENV=ONLY
SOURCE_DATE_EPOCH=`date +%s` cmake .. -DCMAKE_BUILD_TYPE=Release  -DBUILD_PYBIND=ON -DUSE_OPENLIBM=ON -DUSE_SINGLE_PRECISION=ON -DCERES_TINY_SOLVER=ON -DPython3_FIND_VIRTUALENV=ONLY


feat: Implement service metrics for Events and Readings persisted

closes #3901
Related dependent PRs:

https://github.com/edgexfoundry/go-mod-core-contracts/pull/709
bootstrap TBD

Signed-off-by: Leonard Goodell<EMAIL_ADDRESS>

If your build fails  due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[x] I have added unit tests for the new feature or bug fix (if not, why?)
[x] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?) TBD on agreement on approach

Testing Instructions

Run non-secure EdgeX stack with MQTT as the MessageBus and stop core data

make run no-secty ds-virtual mqtt-bus

Clone this branch, Build and run Core Data with DEBUG logging on

Also clone related PR branches for go-mod-core-contracts and go-mod-boostrap

Run MQTT.fx , connect to broker on localhost and subscribe to edgex/telemetry/# topic
When data received, copy the Base64 encoded payload and paste it in Decoder tool (https://www.base64decode.org/)
Verify payload is a Metric DTO for EventsPersisted or ReadingsPersisted
Repeat for next message received and verify it is the other Metric DTO.

New Dependency Instructions (If applicable)
N/A

All the make commands need to use CGOFLAGS in conjunction with GOCGO.

@bnevis-i Fixed now.

On Hold till resolve new (sort of) dependency.


Add support for tf.sigmoid_cross_entropy_with_logits and tf.where

I couldn't find current implementations for tf.sigmoid_cross_entropy_with_logits and tf.where. If they are indeed still not available in the project, I will send a pull request in the next minutes with their implementation.

Merged.


Authorization in Prefect server

Prefect server is currently available for everyone within NIH vpn. We need to add some form of authorization (Bearer token for api without refresh for now, and Basic auth with username and password).

Closed by https://github.com/niaid/tf-hedwig-workflow-api/commit/4b782675f0130bc295fc82ce63a42872f3ed2715


[Broken] Soundcloud converting wav to mp3 despite "best" option

Checklist

[x] I'm reporting a broken site support
[x] I've verified that I'm running youtube-dlc version 2020.09.16
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar issues including closed ones

Verbose log

youtube-dlc -v -x --audio-format "best" https://soundcloud.com/belikboom/harry-potter
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', '-x', '--audio-format', 'best', 'https://soundcloud.com/belikboom/harry-potter']
[debug] Loading archive file None
[debug] Encodings: locale cp1252, fs utf-8, out utf-8, pref cp1252
[debug] youtube-dlc version 2020.10.09
[debug] Python version 3.8.6 (CPython) - Windows-10-10.0.19041-SP0
[debug] exe versions: ffmpeg 4.3.1-2020-11-19-full_build-www.gyan.dev, ffprobe 4.3.1-2020-11-19-full_build-www.gyan.dev
[debug] Proxy map: {}
[soundcloud] belikboom/harry-potter: Downloading info JSON
[soundcloud] 172989719: Downloading JSON metadata
[soundcloud] 172989719: Downloading webpage
[soundcloud] 172989719: Downloading JSON metadata
[soundcloud] 172989719: Downloading JSON metadata
[soundcloud] 172989719: Downloading JSON metadata
[debug] Invoking downloader on 'https://cf-media.sndcdn.com/WYHtGMNj90Yp?Policy=eyJTdGF0ZW1lbnQiOlt7IlJlc291cmNlIjoiKjovL2NmLW1lZGlhLnNuZGNkbi5jb20vV1lIdEdNTmo5MFlwIiwiQ29uZGl0aW9uIjp7IkRhdGVMZXNzVGhhbiI6eyJBV1M6RXBvY2hUaW1lIjoxNjA5MzA3MDMxfX19XX0_&Signature=WJhd4byXEUIoKzdnrYXk-0oxJzRnwirPBzLaIFJIxKVu5zXqPALV~nBV994RS60Yuc~7l2Ac4BpkA3BtUcxXwV9nVqFxYwbCpI8AiCwEHw1-rCesQHjyrydj~7sC15bbWy~t0I0C4i25GflVW8kn3AJp3jHaBtpQ55ScHu2Hq6B4uiWBXabRB4WVfVZ1ouSBzSaocapZMs6eVb0EpcMSfa0GAnUSgPFxeekxxosux7QKmSX1uAxkUmzUbj5sdVnYp5Q4P-QJdLB23A3475cosVc5yMsLZ1sSOX7NY2ydLTASijYjfXNIZi7oeWRnetRRF731yNj8lQPNImuNR81Mpg__&Key-Pair-Id=APKAI6TU7MMXM5DG6EPQ'
[download] Destination: Avada kadabra (FREE DOWNLOAD)-172989719.wav
[download] 100% of 67.68MiB in 00:01
[debug] ffmpeg command line: ffprobe -show_streams "file:Avada kadabra (FREE DOWNLOAD)-172989719.wav"
[ffmpeg] Destination: Avada kadabra (FREE DOWNLOAD)-172989719.mp3
[debug] ffmpeg command line: ffmpeg -y -loglevel "repeat+info" -i "file:Avada kadabra (FREE DOWNLOAD)-172989719.wav" -vn -acodec libmp3lame "-q:a" 5 "file:Avada kadabra (FREE DOWNLOAD)-172989719.mp3"
Deleting original file Avada kadabra (FREE DOWNLOAD)-172989719.wav (pass -k to keep)

Description

Wav file downloads successfully, but is then converted to a very low-quality (137 kbps) mp3 file, and wav is deleted despite specifying "best".
Downloading mp3s and aacs works properly with this option (mp3 remains same, aac -> m4a), only wav does not. The goal is to convert all 3 formats in bulk, which is why I am using the "best" argument and not just "wav".
I believe this is a similar issue to #212, just for soundcloud and I don't know which arguments to add to fix the sort.

Try:
youtube-dlc -v -f best https://soundcloud.com/belikboom/harry-potter
youtube-dlc -v --ignore-config -f best https://soundcloud.com/belikboom/harry-potter
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', '--ignore-config', '-f', 'best', 'https://soundcloud.com/belikboom/harry-potter']
[debug] Loading archive file None
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dlc version 2020.12.29
[debug] Python version 3.6.9 (CPython) - Linux-4.15.0-128-generic-x86_64-with-LinuxMint-19.3-tricia
[debug] exe versions: ffmpeg N-100367-g8d19b3c-Nico-20201210, ffprobe N-100367-g8d19b3c-Nico-20201210
[debug] Proxy map: {}
[soundcloud] belikboom/harry-potter: Downloading info JSON
[soundcloud] 172989719: Downloading JSON metadata
[soundcloud] 172989719: Downloading webpage
[soundcloud] 172989719: Downloading JSON metadata
[soundcloud] 172989719: Downloading JSON metadata
[soundcloud] 172989719: Downloading JSON metadata
[debug] Invoking downloader on 'https://cf-media.sndcdn.com/WYHtGMNj90Yp?Policy=eyJTdGF0ZW1lbnQiOlt7IlJlc291cmNlIjoiKjovL2NmLW1lZGlhLnNuZGNkbi5jb20vV1lIdEdNTmo5MFlwIiwiQ29uZGl0aW9uIjp7IkRhdGVMZXNzVGhhbiI6eyJBV1M6RXBvY2hUaW1lIjoxNjA5MzM4NjgxfX19XX0_&Signature=eIi1IftkaTgAUZnWGw5syhoukAA58Z4VKaEVAFl083iVjyUIdwipgxxB9XZEHcIspIq1spBmUOFURTvDFBTVharug6iHVVbEyMLUYxfE6N5ZIzoX6Oq76tcxaT2pZRe79d6z5i3wJgZSEoyuM8LaHDCMvNqQYfbCGTHNKo7ssqFP8mSDZLbi3SuJ9y3apoY7MHWjcSYyUNnEYjVEmYhOpgA0~KgW3ZT~HIIzrANBJgwpWwgQu4yMOyj4SWWGT0fMTyqgMtrQXiLYOQupDpl9jhrPhf9Gzy2D3ZFE8U3ak7j5tWTfGs0VvY56QFbsgZ7wjpZvM0jkZmspbz74yrAJ9Q__&Key-Pair-Id=APKAI6TU7MMXM5DG6EPQ'
[download] Destination: Avada kadabra (FREE DOWNLOAD)-172989719.wav
[download] 100% of 67.68MiB in 00:11

Side note:
The official youtube-dlc repo is now here:
https://github.com/blackjack4494/yt-dlc
(since the DMCA debacle...)

Oh my bad on using the wrong repo. Thanks for the responses here and on reddit though! This works, but makes things slightly less automated for me. Ultimately --audio-format is the only option I know of that will also convert soundcloud's native aac to m4a which is ideal, but this will have to do. Thanks again!


Some unicode symbols are displayed as squares

When I commented out lean4-mode, 𝕜 can be displayed without problem.  However when I enable lean4-mode, 𝕜 becomes square with unicode value (01D55C) in it.  There are other symbols also having this problem.  This happens even I comment out everything in init.el and turn on lean4-mode only.

Here is the output of what-cursor-position when 𝕜 can be displayed (lean4-mode turned-off):

             position: 898 of 5816 (15%), column: 9
            character: 𝕜 (displayed as 𝕜) (codepoint 120156, #o352534, #x1d55c)
              charset: unicode (Unicode (ISO10646))
code point in charset: 0x1D55C
               script: mathematical
               syntax: w 	which means: word
             category: .:Base, L:Strong L2R
             to input: type "C-x 8 RET 1d55c" or "C-x 8 RET MATHEMATICAL DOUBLE-STRUCK SMALL K"
          buffer code: #xF0 #x9D #x95 #x9C
            file code: #xF0 #x9D #x95 #x9C (encoded by coding system utf-8-unix)
              display: by this font (glyph code):
    ftcrhb:-STIX-STIXGeneral-normal-normal-normal-*-17-*-*-*-*-0-iso10646-1 (#xA47)

Character code properties: customize what to show
  name: MATHEMATICAL DOUBLE-STRUCK SMALL K
  general-category: Ll (Letter, Lowercase)
  decomposition: (font 107) (font 'k')

When 𝕜 cannot be displayed:

             position: 898 of 5816 (15%), column: 9
            character: 𝕜 (displayed as 𝕜) (codepoint 120156, #o352534, #x1d55c)
              charset: unicode (Unicode (ISO10646))
code point in charset: 0x1D55C
               script: mathematical
               syntax: w 	which means: word
             category: .:Base, L:Strong L2R
             to input: type "\bbk" with Lean input method
          buffer code: #xF0 #x9D #x95 #x9C
            file code: #xF0 #x9D #x95 #x9C (encoded by coding system utf-8-unix)
              display: no font available

Character code properties: customize what to show
  name: MATHEMATICAL DOUBLE-STRUCK SMALL K
  general-category: Ll (Letter, Lowercase)
  decomposition: (font 107) (font 'k')

There is an overlay here:
 From 898 to 900
  face                 lsp-face-highlight-textual
  lsp-highlight        t

There are text properties here:
  face                 lsp-face-semhl-variable
  fontified            t

Both (face-all-attributes 'lsp-face-highlight-textual) and (face-all-attributes 'lsp-face-semhl-variable) are:
((:family . unspecified) (:foundry . unspecified) (:width . unspecified) (:height . unspecified) (:weight . unspecified) (:slant . unspecified) (:underline . unspecified) (:overline . unspecified) (:extend . unspecified) (:strike-through . unspecified) (:box . unspecified) (:inverse-video . unspecified) (:foreground . unspecified) (:background . unspecified) (:stipple . unspecified) (:inherit . unspecified))


data: krshkun testimonials

Added testimonials for @Pradumnasaraf @avie-dev @eddiejaoude @loftwah @thebarshblog @tobySolutions @WebXDAO/core-team, if anyone of you would like to add it to your linkfree profile, please refer: docs

Added testimonials for @Pradumnasaraf @avie-dev @eddiejaoude @loftwah @thebarshblog @tobySolutions @WebXDAO/core-team, if anyone of you would like to add it to your linkfree profile, please refer: docs

Hey Krish! Did you write me a testimonial? Well, my handle is @thebarshablog . Thank you!

Thank you so much Krish!!

Added testimonials for @Pradumnasaraf @avie-dev @eddiejaoude @loftwah @thebarshblog @tobySolutions @WebXDAO/core-team, if anyone of you would like to add it to your linkfree profile, please refer: docs

Thank you for the testimonial @krshkun

Please elaborate this method! How do I include it? Where do I put the .json code?

@thebarshablog create a testimonials array in your linkfree file's JSON and enter my username it it 👍


custom URL

Proposed changes
I want to use a custom url to access sonweb, like https://site.domain.com/sonweb, it this possible ?
In this way I can use the same hassio url.
I tried with Nginx proxy but it fail because on webpage the urls are absolute, for example "/start"
Thank you
Alessandro
404 Error - Page Not Found

Hi @aferraz,
You have to setup a reverse proxy for this indeed, like NGinx or Caddy.
Nevertheless, this is kinda out of scope for this add-on.
There are multiple topics on the community forums, you should check it out!
../Frenck


Add examples chapter to docs for various edge cases users requests

#186

Coverage remained the same at 96.341% when pulling b2fd3875dbbb75b6029b4c68d9cc06e51de7c08a on KaczuH:ISSUE/186 into ec98227c6c7f9285c3854f62de8c95030f78d65d on sunscrapers:master.

Coverage remained the same at 96.341% when pulling c6f64e5df0333b452a62d4e65ba119c7fe1f52f3 on KaczuH:ISSUE/186 into ec98227c6c7f9285c3854f62de8c95030f78d65d on sunscrapers:master.


When the default version is set for the template, the version will be cleared

When the default version is set for the template, the version will be cleared

Fixed, @WuJun2016 could you check and update the issue

close in favor of https://github.com/rancher/harvester/pull/39


updating Obsidian Minimal Publish

Hello,
i was wondering if obsidian minimal publish gets updated with obsidian itself ? if not, do i make a clean install again to update with the latest version ?

No there is no update mechanism for Publish themes. You have to get the latest version and re-publish it.
https://minimal.guide/publish/download

Thank you


Position error

Checklist

[X] I read the troubleshooting guide before raising this issue
[X] I made sure that the issue I am raising doesn't already exist

Current bug behaviour
When the mp3 audio is playing, the onPositionChanged method begins to return the correct position but, after a few seconds, the position value is reset even though the audio continues to play correctly.
Expected behaviour
The position value must not be reset.
Steps to reproduce
No response
Code sample
No response
Affected platforms
Android, iOS
Platform details
No response
AudioPlayers Version
6.0.0
Build mode
debug, release
Audio Files/URLs/Sources
No response
Screenshots
No response
Logs

my relevant logs

Full Logs

my full logs or a link to a gist

Flutter doctor:
Output of: flutter doctor -v

Related issues / more information
No response
Working on PR
no way

I have the same issue on Android on my project, but also on the example of this repo, on Android, around 9:30s and 10s :
https://youtu.be/EF4CoXBBmu8

I found a tricky fix inside the code but this is not beautiful sorry
Stream<Duration> currentPosition() async* {     yield* audioPlayer.onPositionChanged.map((event) {       // Weird bug Android https://github.com/bluefireteam/audioplayers/issues/1815       if (event < Duration(milliseconds: 300) && previousPosition != null) {         if (previousPosition!.inMilliseconds - event.inMilliseconds > 5000) {           developer.log("previousPosition: $previousPosition, currentPosition $event");           Duration fixedPosition = Duration(milliseconds: (previousPosition!.inMilliseconds + event.inMilliseconds).round());           audioPlayer.seek(fixedPosition);           return fixedPosition;         }       }       previousPosition = event;       // end fixinf weird bug       return event;     });   }

I'm also facing same issue...


Provide a way for 3rd party packages to add internalization paths

For example we have 3 themes:
        "backpack/theme-coreuiv2": "dev-main",
        "backpack/theme-coreuiv4": "dev-main",
        "backpack/theme-tabler": "dev-main"

All 3 would like to do something in their ServiceProvider's boot() method:
BassetManager::addPath()

Also, CRUD and PRO would need to do the same thing, in their service providers.

Moving to https://github.com/Laravel-Backpack/basset/pull/24 🙌


[NEW]: Shinu Iba AWS token leak

Date
2022-9-8
Description
Shinu Iba leaks credentials to GitHub in commit. No bug bounty or responsible disclosure policy in place so researcher has to post online to draw teams attention.
Links
https://blog.pingsafe.com/shiba-inu-cloud-credentials-leaked-in-a-major-security-breach-394ad54382c1
https://www.cyberkendra.com/2022/09/shiba-inu-leaked-their-aws-cloud.html
Agreement

[X] I irrevocably agree to release my contribution under the CC-BY 3.0 License

Attribution name
No response
Personal link
No response

Thanks! https://web3isgoinggreat.com/?id=shiba-inu-developers-leak-aws-credentials-on-github


Modify VerifyUpgradeAndUpdateState to set client/consensus states in light client implementations

Summary
same reasoning as #284. ICS specs need to be checked to see if they need to be updated

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

closed by #598!


Bug?  Stuck on "searching for alt. covers"

Did a quick search of the issues, but did not see this in there.
When using the GUI (at least, may be CLI also, dunno) and it comes back with a low-confident match, it will show the "normal" cover on the right but the text underneath says "searching for alt. covers" and just....stays there?  It doesn't seem to actually be searching for alternates because, if it did, it probably would find a match.
Looks like the same is happening when using the Auto-Identify function.  Once you find the right series and issue, it will also showing "searching for alt. covers" but it never comes up with any (and there definitely are with the issue I just tried).
I know this worked previously because I have looked through alternate covers before.  Not sure if some change in the code is the cause or maybe it's a CV thing?

It should just be the GUI, this is because we use Qt's library for network requests when we run the GUI and I've had some trouble getting it to work consistently.

I'm also seeing this issue, which is limiting my ability to match issues without manually going to CV. Any options here?

@ducky0518 @musictrivianut there is still an issue when using the search button to browse the comic issues that it will not retrieve the alternate covers, in the mean time you will need to use the auto-identify or the auto-tag feature for it to retrieve the alternate covers, on the latest release 1.5.3.

Please ignore 1.5.3 1.5.4 is released now

Even on v1.5.4 I'm not seeing the alternative covers with auto-identify. It still says "Searching for alt. covers" - and yes I have an issue where I've verified there are multiple covers on CV. Here's an example:
https://comicvine.gamespot.com/no-hero-2/4000-141243/

OK - I think I see how this works now. It's only if it doesn't think its a match will you see the arrows for the additional covers show up. Is that correct? When I moved the covers around in the file so the first one was different than the primary one on CV, then the multiple covers arrows showed up. Interesting.

Yeah, it's really buggy right now. When #341 is merged this should all work consistently.

Yeah, It seems to be working like 5% of the time for me. Definitely it doesn't work far more than it does. As long as you're seeing this same behavior. We're good.

This can be closed now?

Yes this was fixed by @mizaki in #341


Fix various C++ warnings

Summary
Fix warnings about implicit type truncation.
Changelog
[Internal] [Fixed] - Fix various C++ warnings
Test Plan
Almost all the changes here are simply making explicit conversions which are already occurring.  With the exception of a couple of constants being changed from doubles to floats.
With these changes I am able to remove a bunch of warning suppressions in react-native-windows.

@acoates-ms I'll take a look at this after you respond to @asklar's comments :)


Update the PlonK solidity verifier for production readiness

duplicate with https://github.com/ConsenSys/gnark/issues/524 https://github.com/ConsenSys/gnark/issues/465


upd(pipewire): 0.3.44 -> 0.3.47

https://github.com/pacstall/pacstall-programs/runs/5261730506?check_suite_focus=true#step:9:1587
This issue can be fixed by removing apt's meson and installing it from pip. Although I remember this working fine in a VM a while back

WTF happened with the CI.

I guess since you've requested a review from @D-Brox I'll just enable auto squash for now.


Reproduce alertmanager resending alerts

This reproduces the issue mentioned in #2447:
With some combinations of group_interval and group_delay ratios alerts in a clustered alertmanager can be resend multiple times

Maybe @beorn7 has an opinion on this.

Maybe @beorn7 has an opinion on this.

Thanks for reproducing this.
I am actually not an expert for Alertmanager. I needed some thinking to understand this behavior completely.
@simonpasquier is the maintainer. Perhaps he will understand this more readily or knows someone who will.

Thanks for reproducing this.
I am actually not an expert for Alertmanager. I needed some thinking to understand this behavior completely.
@simonpasquier is the maintainer. Perhaps he will understand this more readily or knows someone who will.

I've commented on #2447 why this may happen (not saying that we shouldn't improve the situation :smiley:). I think we can close this PR since we have all data in the originating issue. What do you think @simonswine?

I've commented on #2447 why this may happen (not saying that we shouldn't improve the situation :smiley:). I think we can close this PR since we have all data in the originating issue. What do you think @simonswine?