[BUG] VM hangs after few minutes

General information

OS: macOS
Hypervisor: hyperkit

Logs
With bundle 4.7.2, few minutes after the cluster is running, the VM hangs.
I reproduced it 4 or 5 times on my machine.
dmesg:
[  216.205125] device veth32dbca82 left promiscuous mode
[  216.418573] device veth77ebf074 left promiscuous mode
[  216.761833] device veth0ed62c94 left promiscuous mode
[  219.156833] device vethb593bb8f left promiscuous mode
[  241.226202] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  241.235491] IPv6: ADDRCONF(NETDEV_UP): vethf073c0ce: link is not ready
[  241.236909] IPv6: ADDRCONF(NETDEV_CHANGE): vethf073c0ce: link becomes ready
[  241.238288] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  241.371335] device vethf073c0ce entered promiscuous mode
[  241.624296] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  241.662537] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  241.841077] device veth04874446 entered promiscuous mode
[  253.916590] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  253.935487] IPv6: ADDRCONF(NETDEV_UP): veth673314bb: link is not ready
[  253.939868] IPv6: ADDRCONF(NETDEV_CHANGE): veth673314bb: link becomes ready
[  253.941288] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  254.048549] device veth673314bb entered promiscuous mode
[  256.539689] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  256.546704] IPv6: ADDRCONF(NETDEV_UP): vethdb63b6b5: link is not ready
[  256.549705] IPv6: ADDRCONF(NETDEV_CHANGE): vethdb63b6b5: link becomes ready
[  256.551136] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  256.591294] device vethdb63b6b5 entered promiscuous mode
[  269.773626] device veth04874446 left promiscuous mode
[  273.813593] device vethf073c0ce left promiscuous mode
[  276.619427] device veth673314bb left promiscuous mode
[  276.823530] device veth1180d43c left promiscuous mode
[  297.076414] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  297.087783] IPv6: ADDRCONF(NETDEV_UP): vethfae7ba80: link is not ready
[  297.089304] IPv6: ADDRCONF(NETDEV_CHANGE): vethfae7ba80: link becomes ready
[  297.090667] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  297.126456] device vethfae7ba80 entered promiscuous mode
[  306.997739] device vethb2682656 left promiscuous mode
[  310.417147] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  310.429694] IPv6: ADDRCONF(NETDEV_UP): veth1486ba39: link is not ready
[  310.430924] IPv6: ADDRCONF(NETDEV_CHANGE): veth1486ba39: link becomes ready
[  310.432269] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  310.465125] device veth1486ba39 entered promiscuous mode
[  322.396022] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  322.405737] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  322.442714] device vethebdb760e entered promiscuous mode
[  347.831558] device veth0038331e left promiscuous mode
[  352.300008] device vethb97b301b left promiscuous mode
[  572.848038] hrtimer: interrupt took 1244936 ns
[  731.340540] systemd[1]: session-51.scope: Succeeded.
[  731.341662] systemd[1]: session-51.scope: Consumed 245ms CPU time
[  737.288825] systemd[1]: Started Session 52 of user core.
[  737.766311] INFO: task kworker/u8:1:34 blocked for more than 120 seconds.
[  737.767239]       Not tainted 4.18.0-240.15.1.el8_3.x86_64 #1
[  737.768010] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  737.769037] kworker/u8:1    D    0    34      2 0x80004000
[  737.769764] Workqueue: writeback wb_workfn (flush-252:0)
[  737.770489] Call Trace:
[  737.770843]  __schedule+0x2a6/0x700
[  737.771450]  ? wbt_exit+0x30/0x30
[  737.772155]  ? __wbt_done+0x30/0x30
[  737.772722]  schedule+0x38/0xa0
[  737.773231]  io_schedule+0x12/0x40
[  737.773772]  rq_qos_wait+0xfa/0x170
[  737.774307]  ? karma_partition+0x210/0x210
[  737.774874]  ? wbt_exit+0x30/0x30
[  737.775356]  wbt_wait+0x99/0xe0
[  737.775796]  __rq_qos_throttle+0x23/0x30
[  737.776325]  blk_mq_make_request+0x125/0x5d0
[  737.776875]  generic_make_request+0xcf/0x310
[  737.777463]  submit_bio+0x3c/0x160
[  737.778005]  ? xfs_prepare_ioend+0xc2/0xd0 [xfs]
[  737.778649]  iomap_submit_ioend.isra.38+0x4a/0x70
[  737.779357]  xfs_vm_writepages+0x64/0x90 [xfs]
[  737.780019]  do_writepages+0x41/0xd0
[  737.780714]  ? select_idle_sibling+0x21/0x560
[  737.781500]  ? __switch_to_asm+0x41/0x70
[  737.782247]  ? __switch_to_asm+0x35/0x70
[  737.783002]  ? __switch_to_asm+0x41/0x70
[  737.783601]  ? __switch_to_asm+0x35/0x70
[  737.784130]  __writeback_single_inode+0x3d/0x370
[  737.784775]  writeback_sb_inodes+0x1e7/0x440
[  737.785354]  __writeback_inodes_wb+0x5f/0xc0
[  737.785909]  wb_writeback+0x25b/0x2f0
[  737.786411]  ? cpumask_next+0x17/0x20
[  737.786947]  wb_workfn+0x352/0x4a0
[  737.787436]  ? __switch_to_asm+0x41/0x70
[  737.788003]  ? __switch_to_asm+0x35/0x70
[  737.788550]  ? __switch_to_asm+0x41/0x70
[  737.789073]  ? __switch_to_asm+0x35/0x70
[  737.789629]  ? __switch_to_asm+0x41/0x70
[  737.790141]  ? __switch_to_asm+0x35/0x70
[  737.790711]  ? __switch_to_asm+0x41/0x70
[  737.791275]  ? __switch_to_asm+0x35/0x70
[  737.791786]  process_one_work+0x1a7/0x360
[  737.792323]  worker_thread+0x30/0x390
[  737.792800]  ? create_worker+0x1a0/0x1a0
[  737.793369]  kthread+0x112/0x130
[  737.793832]  ? kthread_flush_work_fn+0x10/0x10
[  737.794446]  ret_from_fork+0x35/0x40
[  737.794940] INFO: task kworker/0:3:368 blocked for more than 120 seconds.
[  737.795876]       Not tainted 4.18.0-240.15.1.el8_3.x86_64 #1
[  737.796703] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  737.797757] kworker/0:3     D    0   368      2 0x80004000
[  737.798540] Workqueue: xfs-sync/vda4 xfs_log_worker [xfs]
[  737.799275] Call Trace:
[  737.799601]  __schedule+0x2a6/0x700
[  737.800058]  ? wbt_exit+0x30/0x30
[  737.800510]  ? __wbt_done+0x30/0x30
[  737.800964]  schedule+0x38/0xa0
[  737.801422]  io_schedule+0x12/0x40
[  737.801880]  rq_qos_wait+0xfa/0x170
[  737.802388]  ? karma_partition+0x210/0x210
[  737.802933]  ? wbt_exit+0x30/0x30
[  737.803393]  wbt_wait+0x99/0xe0
[  737.803871]  __rq_qos_throttle+0x23/0x30
[  737.804498]  blk_mq_make_request+0x125/0x5d0
[  737.805176]  generic_make_request+0xcf/0x310
[  737.805929]  ? bio_add_page+0x42/0x50
[  737.806537]  submit_bio+0x3c/0x160
[  737.807126]  xlog_state_release_iclog+0x5f/0xa0 [xfs]
[  737.807990]  xfs_log_force+0x23c/0x2e0 [xfs]
[  737.808559]  ? __switch_to_asm+0x35/0x70
[  737.809068]  ? __switch_to_asm+0x41/0x70
[  737.809614]  ? __switch_to+0x7a/0x3f0
[  737.810108]  xfs_log_worker+0x2f/0xf0 [xfs]
[  737.810686]  process_one_work+0x1a7/0x360
[  737.811229]  worker_thread+0x30/0x390
[  737.811704]  ? create_worker+0x1a0/0x1a0
[  737.812232]  kthread+0x112/0x130
[  737.812657]  ? kthread_flush_work_fn+0x10/0x10
[  737.813315]  ret_from_fork+0x35/0x40
[  737.813813] INFO: task journal-offline:31971 blocked for more than 120 seconds.
[  737.814855]       Not tainted 4.18.0-240.15.1.el8_3.x86_64 #1
[  737.815646] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  737.816672] journal-offline D    0 31971      1 0x00000184
[  737.817420] Call Trace:
[  737.817746]  __schedule+0x2a6/0x700
[  737.818222]  ? wbt_exit+0x30/0x30
[  737.818657]  ? __wbt_done+0x30/0x30
[  737.819112]  schedule+0x38/0xa0
[  737.819540]  io_schedule+0x12/0x40
[  737.820036]  rq_qos_wait+0xfa/0x170
[  737.820545]  ? karma_partition+0x210/0x210
[  737.821074]  ? wbt_exit+0x30/0x30
[  737.821541]  wbt_wait+0x99/0xe0
[  737.821954]  __rq_qos_throttle+0x23/0x30
[  737.822480]  blk_mq_make_request+0x125/0x5d0
[  737.823036]  generic_make_request+0xcf/0x310
[  737.823620]  ? page_mkclean+0xa4/0xc0
[  737.824095]  submit_bio+0x3c/0x160
[  737.824551]  ? __test_set_page_writeback+0x17a/0x340
[  737.825249]  iomap_submit_ioend.isra.38+0x4a/0x70
[  737.825944]  iomap_writepage_map+0x45b/0x6b0
[  737.826563]  write_cache_pages+0x1aa/0x440
[  737.827091]  ? iomap_invalidatepage+0xe0/0xe0
[  737.827696]  iomap_writepages+0x1c/0x40
[  737.828314]  xfs_vm_writepages+0x64/0x90 [xfs]
[  737.828908]  do_writepages+0x41/0xd0
[  737.829400]  __filemap_fdatawrite_range+0xbe/0xf0
[  737.830005]  file_write_and_wait_range+0x4c/0xa0
[  737.830645]  xfs_file_fsync+0x5d/0x1e0 [xfs]
[  737.831219]  do_fsync+0x38/0x70
[  737.831633]  __x64_sys_fsync+0x10/0x20
[  737.832120]  do_syscall_64+0x5b/0x1a0
[  737.832633]  entry_SYSCALL_64_after_hwframe+0x65/0xca
[  737.833334] RIP: 0033:0x7f7113d52e67
[  737.833804] Code: Bad RIP value.
[  737.834268] RSP: 002b:00007f710cd1cc70 EFLAGS: 00000293 ORIG_RAX:<PHONE_NUMBER>00004a
[  737.835253] RAX: ffffffffffffffda RBX:<PHONE_NUMBER>000013 RCX: 00007f7113d52e67
[  737.836214] RDX:<PHONE_NUMBER>000000 RSI: 00007f711455eefc RDI:<PHONE_NUMBER>000013
[  737.837139] RBP: 00007f711455eee0 R08: 00007f710cd1d700 R09: 00007f710cd1d700
[  737.838095] R10:<PHONE_NUMBER>00001c R11:<PHONE_NUMBER>000293 R12:<PHONE_NUMBER>000002
[  737.839013] R13: 00007ffc77a43f8f R14:<PHONE_NUMBER>000000 R15: 00007f710cd1cd80
[  737.839931] INFO: task journal-offline:31972 blocked for more than 120 seconds.
[  737.840908]       Not tainted 4.18.0-240.15.1.el8_3.x86_64 #1
[  737.841755] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  737.842953] journal-offline D    0 31972      1 0x00000184
[  737.843689] Call Trace:
[  737.844019]  __schedule+0x2a6/0x700
[  737.844491]  ? wbt_exit+0x30/0x30
[  737.844923]  ? __wbt_done+0x30/0x30
[  737.845411]  schedule+0x38/0xa0
[  737.845824]  io_schedule+0x12/0x40
[  737.846306]  rq_qos_wait+0xfa/0x170
[  737.846836]  ? karma_partition+0x210/0x210
[  737.847422]  ? wbt_exit+0x30/0x30
[  737.847856]  wbt_wait+0x99/0xe0
[  737.848317]  __rq_qos_throttle+0x23/0x30
[  737.848830]  blk_mq_make_request+0x125/0x5d0
[  737.849420]  generic_make_request+0xcf/0x310
[  737.849974]  ? page_mkclean+0xa4/0xc0
[  737.850472]  submit_bio+0x3c/0x160
[  737.850918]  ? __test_set_page_writeback+0x17a/0x340
[  737.851619]  iomap_submit_ioend.isra.38+0x4a/0x70
[  737.852462]  iomap_writepage_map+0x45b/0x6b0
[  737.853053]  write_cache_pages+0x1aa/0x440
[  737.853628]  ? iomap_invalidatepage+0xe0/0xe0
[  737.854416]  iomap_writepages+0x1c/0x40
[  737.855144]  xfs_vm_writepages+0x64/0x90 [xfs]
[  737.855773]  do_writepages+0x41/0xd0
[  737.856331]  __filemap_fdatawrite_range+0xbe/0xf0
[  737.857119]  file_write_and_wait_range+0x4c/0xa0
[  737.857932]  xfs_file_fsync+0x5d/0x1e0 [xfs]
[  737.858675]  do_fsync+0x38/0x70
[  737.859092]  __x64_sys_fsync+0x10/0x20
[  737.859616]  do_syscall_64+0x5b/0x1a0
[  737.860098]  entry_SYSCALL_64_after_hwframe+0x65/0xca
[  737.860767] RIP: 0033:0x7f7113d52e67
[  737.861287] Code: Bad RIP value.
[  737.861710] RSP: 002b:00007f710f323c70 EFLAGS: 00000293 ORIG_RAX:<PHONE_NUMBER>00004a
[  737.862769] RAX: ffffffffffffffda RBX:<PHONE_NUMBER>000017 RCX: 00007f7113d52e67
[  737.863781] RDX:<PHONE_NUMBER>000000 RSI: 00007f711455eefc RDI:<PHONE_NUMBER>000017
[  737.864763] RBP: 00007f711455eee0 R08: 00007f710f324700 R09: 00007f710f324700
[  737.865741] R10:<PHONE_NUMBER>00001c R11:<PHONE_NUMBER>000293 R12:<PHONE_NUMBER>000002
[  737.866894] R13: 00007ffc77a43f8f R14:<PHONE_NUMBER>000000 R15: 00007f710f323d80
[  737.868280] INFO: task auditd:1004 blocked for more than 120 seconds.
[  737.869219]       Not tainted 4.18.0-240.15.1.el8_3.x86_64 #1
[  737.869983] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  737.871063] auditd          D    0  1004      1 0x00000100
[  737.871775] Call Trace:
[  737.872102]  __schedule+0x2a6/0x700
[  737.872588]  ? mempool_alloc+0x67/0x190
[  737.873087]  ? wbt_exit+0x30/0x30
[  737.873557]  ? __wbt_done+0x30/0x30
[  737.874014]  schedule+0x38/0xa0
[  737.874459]  io_schedule+0x12/0x40
[  737.874903]  rq_qos_wait+0xfa/0x170
[  737.875411]  ? __mod_lruvec_state+0x44/0x110
[  737.875963]  ? karma_partition+0x210/0x210
[  737.876530]  ? wbt_exit+0x30/0x30
[  737.876962]  wbt_wait+0x99/0xe0
[  737.877413]  __rq_qos_throttle+0x23/0x30
[  737.877921]  blk_mq_make_request+0x125/0x5d0
[  737.878557]  generic_make_request+0xcf/0x310
[  737.879112]  submit_bio+0x3c/0x160
[  737.879600]  ? xfs_prepare_ioend+0xc2/0xd0 [xfs]
[  737.880219]  iomap_submit_ioend.isra.38+0x4a/0x70
[  737.880850]  xfs_vm_writepages+0x64/0x90 [xfs]
[  737.881498]  do_writepages+0x41/0xd0
[  737.882068]  __filemap_fdatawrite_range+0xbe/0xf0
[  737.882761]  file_write_and_wait_range+0x4c/0xa0
[  737.883448]  xfs_file_fsync+0x5d/0x1e0 [xfs]
[  737.884005]  do_fsync+0x38/0x70
[  737.884434]  __x64_sys_fsync+0x10/0x20
[  737.884943]  do_syscall_64+0x5b/0x1a0
[  737.885467]  entry_SYSCALL_64_after_hwframe+0x65/0xca
[  737.886114] RIP: 0033:0x7f2641991e67
[  737.886819] Code: Bad RIP value.
[  737.887403] RSP: 002b:00007f263f309d00 EFLAGS: 00000293 ORIG_RAX:<PHONE_NUMBER>00004a
[  737.888875] RAX: ffffffffffffffda RBX:<PHONE_NUMBER>000006 RCX: 00007f2641991e67
[  737.890161] RDX:<PHONE_NUMBER>000000 RSI:<PHONE_NUMBER>000000 RDI:<PHONE_NUMBER>000006
[  737.891602] RBP:<PHONE_NUMBER>000000 R08:<PHONE_NUMBER>000000 R09: 00007f263f30a700
[  737.892738] R10:<PHONE_NUMBER>000000 R11:<PHONE_NUMBER>000293 R12: 00007ffc9b027a6e
[  737.893688] R13: 00007ffc9b027a6f R14:<PHONE_NUMBER>000000 R15: 00007f263f309e80
[  737.894654] INFO: task NetworkManager:1353 blocked for more than 120 seconds.
[  737.895639]       Not tainted 4.18.0-240.15.1.el8_3.x86_64 #1
[  737.896564] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  737.897748] NetworkManager  D    0  1353      1 0x00000080
[  737.898589] Call Trace:
[  737.898989]  __schedule+0x2a6/0x700
[  737.899547]  ? mempool_alloc+0x67/0x190
[  737.900254]  ? wbt_exit+0x30/0x30
[  737.900786]  ? __wbt_done+0x30/0x30
[  737.901429]  schedule+0x38/0xa0
[  737.901966]  io_schedule+0x12/0x40
[  737.902609]  rq_qos_wait+0xfa/0x170
[  737.903409]  ? karma_partition+0x210/0x210
[  737.904123]  ? wbt_exit+0x30/0x30
[  737.904736]  wbt_wait+0x99/0xe0
[  737.905347]  __rq_qos_throttle+0x23/0x30
[  737.906037]  blk_mq_make_request+0x125/0x5d0
[  737.906834]  generic_make_request+0xcf/0x310
[  737.907596]  submit_bio+0x3c/0x160
[  737.908229]  ? terminate_walk+0x7a/0xe0
[  737.908898]  iomap_submit_ioend.isra.38+0x4a/0x70
[  737.909784]  xfs_vm_writepages+0x64/0x90 [xfs]
[  737.910606]  do_writepages+0x41/0xd0
[  737.911298]  ? selinux_inode_getattr+0x6d/0x90
[  737.912075]  __filemap_fdatawrite_range+0xbe/0xf0
[  737.912906]  file_write_and_wait_range+0x4c/0xa0
[  737.913774]  xfs_file_fsync+0x5d/0x1e0 [xfs]
[  737.914536]  do_fsync+0x38/0x70
[  737.915084]  __x64_sys_fsync+0x10/0x20
[  737.915760]  do_syscall_64+0x5b/0x1a0
[  737.916424]  entry_SYSCALL_64_after_hwframe+0x65/0xca
[  737.917326] RIP: 0033:0x7fa3e6495e67
[  737.917956] Code: Bad RIP value.
[  737.918550] RSP: 002b:00007ffe334e25b0 EFLAGS: 00000293 ORIG_RAX:<PHONE_NUMBER>00004a
[  737.919878] RAX: ffffffffffffffda RBX:<PHONE_NUMBER>00001a RCX: 00007fa3e6495e67
[  737.921128] RDX:<PHONE_NUMBER>000000 RSI: 00007ffe334e25e0 RDI:<PHONE_NUMBER>00001a
[  737.922485] RBP:<PHONE_NUMBER>00001a R08:<PHONE_NUMBER>000000 R09:<PHONE_NUMBER>000006
[  737.923724] R10:<PHONE_NUMBER>00009d R11:<PHONE_NUMBER>000293 R12: 00007fa3e8c9d088
[  737.924956] R13:<PHONE_NUMBER>9eb980 R14:<PHONE_NUMBER>869c9d R15:<PHONE_NUMBER>000000
[  737.926250] INFO: task etcd:7291 blocked for more than 120 seconds.
[  737.927342]       Not tainted 4.18.0-240.15.1.el8_3.x86_64 #1
[  737.928349] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  737.929693] etcd            D    0  7291   5493 0x00000080
[  737.930651] Call Trace:
[  737.931087]  __schedule+0x2a6/0x700
[  737.931718]  ? wbt_exit+0x30/0x30
[  737.932320]  ? __wbt_done+0x30/0x30
[  737.932927]  schedule+0x38/0xa0
[  737.933509]  io_schedule+0x12/0x40
[  737.934103]  rq_qos_wait+0xfa/0x170
[  737.934728]  ? karma_partition+0x210/0x210
[  737.935452]  ? wbt_exit+0x30/0x30
[  737.936029]  wbt_wait+0x99/0xe0
[  737.936635]  __rq_qos_throttle+0x23/0x30
[  737.937344]  blk_mq_make_request+0x125/0x5d0
[  737.938233]  generic_make_request+0xcf/0x310
[  737.939097]  submit_bio+0x3c/0x160
[  737.939751]  ? xfs_quota_calc_throttle+0xb0/0xb0 [xfs]
[  737.940659]  ? iomap_apply+0x132/0x310
[  737.941336]  iomap_submit_ioend.isra.38+0x4a/0x70
[  737.942170]  xfs_vm_writepages+0x64/0x90 [xfs]
[  737.942963]  do_writepages+0x41/0xd0
[  737.943609]  ? iomap_file_buffered_write+0x62/0x90
[  737.944459]  ? iomap_write_begin+0x4c0/0x4c0
[  737.945262]  ? xfs_iunlock+0xf9/0x100 [xfs]
[  737.945985]  __filemap_fdatawrite_range+0xbe/0xf0
[  737.946878]  file_write_and_wait_range+0x4c/0xa0
[  737.947726]  xfs_file_fsync+0x5d/0x1e0 [xfs]
[  737.948499]  do_fsync+0x38/0x70
[  737.949048]  __x64_sys_fdatasync+0x13/0x20
[  737.949821]  do_syscall_64+0x5b/0x1a0
[  737.950557]  entry_SYSCALL_64_after_hwframe+0x65/0xca
[  737.951455] RIP: 0033:0x4a9740
[  737.952002] Code: Bad RIP value.
[  737.952625] RSP: 002b:000000c0081d0da8 EFLAGS: 00000216 ORIG_RAX:<PHONE_NUMBER>00004b
[  737.954177] RAX: ffffffffffffffda RBX: 000000c000056f00 RCX:<PHONE_NUMBER>4a9740
[  737.955412] RDX:<PHONE_NUMBER>000000 RSI:<PHONE_NUMBER>000000 RDI:<PHONE_NUMBER>000008
[  737.956650] RBP: 000000c0081d0de8 R08:<PHONE_NUMBER>000000 R09:<PHONE_NUMBER>000000
[  737.957878] R10:<PHONE_NUMBER>000000 R11:<PHONE_NUMBER>000216 R12: ffffffffffffffff
[  737.959108] R13:<PHONE_NUMBER>0000dc R14:<PHONE_NUMBER>0000db R15:<PHONE_NUMBER>000200
[  742.348219] systemd[1]: session-52.scope: Succeeded.
[  742.349474] systemd[1]: session-52.scope: Consumed 246ms CPU time
[  748.312641] systemd[1]: Started Session 53 of user core.
[  753.387892] systemd[1]: session-53.scope: Succeeded.
[  753.389239] systemd[1]: session-53.scope: Consumed 258ms CPU time
[  759.394931] systemd[1]: Started Session 54 of user core.
[  764.499650] systemd[1]: session-54.scope: Succeeded.
[  764.501108] systemd[1]: session-54.scope: Consumed 278ms CPU time
[  770.500711] systemd[1]: Started Session 55 of user core.
[  775.582609] systemd[1]: session-55.scope: Succeeded.
[  775.583768] systemd[1]: session-55.scope: Consumed 255ms CPU time
[  781.532347] systemd[1]: Started Session 56 of user core.
[  819.221842] systemd[1]: systemd-journald.service: State 'stop-sigabrt' timed out. Terminating.
[  860.645160] INFO: task kworker/u8:1:34 blocked for more than 120 seconds.
[  860.646060]       Not tainted 4.18.0-240.15.1.el8_3.x86_64 #1
[  860.646792] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  860.647793] kworker/u8:1    D    0    34      2 0x80004000
[  860.648510] Workqueue: writeback wb_workfn (flush-252:0)
[  860.649208] Call Trace:
[  860.649534]  __schedule+0x2a6/0x700
[  860.650029]  ? wbt_exit+0x30/0x30
[  860.650567]  ? __wbt_done+0x30/0x30
[  860.651100]  schedule+0x38/0xa0
[  860.651562]  io_schedule+0x12/0x40
[  860.652155]  rq_qos_wait+0xfa/0x170
[  860.652718]  ? karma_partition+0x210/0x210
[  860.653340]  ? wbt_exit+0x30/0x30
[  860.653808]  wbt_wait+0x99/0xe0
[  860.654306]  __rq_qos_throttle+0x23/0x30
[  860.654889]  blk_mq_make_request+0x125/0x5d0
[  860.655535]  generic_make_request+0xcf/0x310
[  860.656210]  submit_bio+0x3c/0x160
[  860.656742]  ? xfs_prepare_ioend+0xc2/0xd0 [xfs]
[  860.657526]  iomap_submit_ioend.isra.38+0x4a/0x70
[  860.658247]  xfs_vm_writepages+0x64/0x90 [xfs]
[  860.658844]  do_writepages+0x41/0xd0
[  860.659369]  ? select_idle_sibling+0x21/0x560
[  860.660130]  ? __switch_to_asm+0x41/0x70
[  860.660784]  ? __switch_to_asm+0x35/0x70
[  860.661518]  ? __switch_to_asm+0x41/0x70
[  860.662133]  ? __switch_to_asm+0x35/0x70
[  860.662717]  __writeback_single_inode+0x3d/0x370
[  860.663495]  writeback_sb_inodes+0x1e7/0x440
[  860.664208]  __writeback_inodes_wb+0x5f/0xc0
[  860.664863]  wb_writeback+0x25b/0x2f0
[  860.665411]  ? cpumask_next+0x17/0x20
[  860.665895]  wb_workfn+0x352/0x4a0
[  860.666365]  ? __switch_to_asm+0x41/0x70
[  860.666882]  ? __switch_to_asm+0x35/0x70
[  860.667415]  ? __switch_to_asm+0x41/0x70
[  860.667971]  ? __switch_to_asm+0x35/0x70
[  860.668486]  ? __switch_to_asm+0x41/0x70
[  860.669037]  ? __switch_to_asm+0x35/0x70
[  860.669555]  ? __switch_to_asm+0x41/0x70
[  860.670098]  ? __switch_to_asm+0x35/0x70
[  860.670640]  process_one_work+0x1a7/0x360
[  860.671231]  worker_thread+0x30/0x390
[  860.671830]  ? create_worker+0x1a0/0x1a0
[  860.672403]  kthread+0x112/0x130
[  860.672825]  ? kthread_flush_work_fn+0x10/0x10
[  860.673478]  ret_from_fork+0x35/0x40
[  860.674003] INFO: task kworker/0:3:368 blocked for more than 120 seconds.
[  860.674953]       Not tainted 4.18.0-240.15.1.el8_3.x86_64 #1
[  860.675714] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  860.676703] kworker/0:3     D    0   368      2 0x80004000
[  860.677484] Workqueue: xfs-sync/vda4 xfs_log_worker [xfs]
[  860.678175] Call Trace:
[  860.678491]  __schedule+0x2a6/0x700
[  860.679068]  ? wbt_exit+0x30/0x30
[  860.679583]  ? __wbt_done+0x30/0x30
[  860.680105]  schedule+0x38/0xa0
[  860.680610]  io_schedule+0x12/0x40
[  860.681293]  rq_qos_wait+0xfa/0x170
[  860.682063]  ? karma_partition+0x210/0x210
[  860.682617]  ? wbt_exit+0x30/0x30
[  860.683081]  wbt_wait+0x99/0xe0
[  860.683531]  __rq_qos_throttle+0x23/0x30
[  860.684187]  blk_mq_make_request+0x125/0x5d0
[  860.684817]  generic_make_request+0xcf/0x310
[  860.685511]  ? bio_add_page+0x42/0x50
[  860.686134]  submit_bio+0x3c/0x160
[  860.686610]  xlog_state_release_iclog+0x5f/0xa0 [xfs]
[  860.687281]  xfs_log_force+0x23c/0x2e0 [xfs]
[  860.687818]  ? __switch_to_asm+0x35/0x70
[  860.688430]  ? __switch_to_asm+0x41/0x70
[  860.689218]  ? __switch_to+0x7a/0x3f0
[  860.689977]  xfs_log_worker+0x2f/0xf0 [xfs]
[  860.690568]  process_one_work+0x1a7/0x360
[  860.691150]  worker_thread+0x30/0x390
[  860.691622]  ? create_worker+0x1a0/0x1a0
[  860.692162]  kthread+0x112/0x130
[  860.692617]  ? kthread_flush_work_fn+0x10/0x10
[  860.693237]  ret_from_fork+0x35/0x40
[  860.693731] INFO: task journal-offline:31971 blocked for more than 120 seconds.
[  860.694669]       Not tainted 4.18.0-240.15.1.el8_3.x86_64 #1
[  860.695428] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  860.696457] journal-offline D    0 31971      1 0x00000184
[  860.697266] Call Trace:
[  860.697601]  __schedule+0x2a6/0x700
[  860.698234]  ? wbt_exit+0x30/0x30
[  860.698857]  ? __wbt_done+0x30/0x30
[  860.699313]  schedule+0x38/0xa0
[  860.699715]  io_schedule+0x12/0x40
[  860.700237]  rq_qos_wait+0xfa/0x170
[  860.700836]  ? karma_partition+0x210/0x210
[  860.701503]  ? wbt_exit+0x30/0x30
[  860.702007]  wbt_wait+0x99/0xe0
[  860.702453]  __rq_qos_throttle+0x23/0x30
[  860.702985]  blk_mq_make_request+0x125/0x5d0
[  860.703829]  generic_make_request+0xcf/0x310
[  860.704679]  ? page_mkclean+0xa4/0xc0
[  860.705397]  submit_bio+0x3c/0x160
[  860.705829]  ? __test_set_page_writeback+0x17a/0x340
[  860.706537]  iomap_submit_ioend.isra.38+0x4a/0x70
[  860.707145]  iomap_writepage_map+0x45b/0x6b0
[  860.707743]  write_cache_pages+0x1aa/0x440
[  860.708348]  ? iomap_invalidatepage+0xe0/0xe0
[  860.709036]  iomap_writepages+0x1c/0x40
[  860.709732]  xfs_vm_writepages+0x64/0x90 [xfs]
[  860.710476]  do_writepages+0x41/0xd0
[  860.710990]  __filemap_fdatawrite_range+0xbe/0xf0
[  860.711653]  file_write_and_wait_range+0x4c/0xa0
[  860.712523]  xfs_file_fsync+0x5d/0x1e0 [xfs]
[  860.713165]  do_fsync+0x38/0x70
[  860.713579]  __x64_sys_fsync+0x10/0x20
[  860.714109]  do_syscall_64+0x5b/0x1a0
[  860.714600]  entry_SYSCALL_64_after_hwframe+0x65/0xca
[  860.715300] RIP: 0033:0x7f7113d52e67
[  860.715766] Code: Bad RIP value.
[  860.716204] RSP: 002b:00007f710cd1cc70 EFLAGS: 00000293 ORIG_RAX:<PHONE_NUMBER>00004a
[  860.717183] RAX: ffffffffffffffda RBX:<PHONE_NUMBER>000013 RCX: 00007f7113d52e67
[  860.718119] RDX:<PHONE_NUMBER>000000 RSI: 00007f711455eefc RDI:<PHONE_NUMBER>000013
[  860.719047] RBP: 00007f711455eee0 R08: 00007f710cd1d700 R09: 00007f710cd1d700
[  860.720148] R10:<PHONE_NUMBER>00001c R11:<PHONE_NUMBER>000293 R12:<PHONE_NUMBER>000002
[  860.721237] R13: 00007ffc77a43f8f R14:<PHONE_NUMBER>000000 R15: 00007f710cd1cd80
[  907.973238] systemd[1]: Starting Cleanup of Temporary Directories...
[  909.470922] systemd[1]: systemd-journald.service: State 'stop-sigterm' timed out. Killing.
[  909.472107] systemd[1]: systemd-journald.service: Killing process 823 (systemd-journal) with signal SIGKILL.
[  999.720181] systemd[1]: systemd-journald.service: Processes still around after SIGKILL. Ignoring.
[ 1063.356232] systemd[1]: Started Session 57 of user core.
[ 1063.402126] systemd[1]: session-57.scope: Succeeded.
[ 1063.403548] systemd[1]: session-57.scope: Consumed 28ms CPU time
[ 1067.487627] systemd[1]: Started Session 58 of user core.

Did you hit this with git master / latest crc-driver-hyperkit release, or with something else?

Yes git master and latest hyperkit driver.
$ ~/.crc/bin/crc-driver-hyperkit
This is a hypervisor plugin binary for CodeReady Containers.
Please use this plugin through the main 'crc' binary.
(Driver version: 0.12.14, API version: 1)

$ ~/.crc/bin/hyperkit -v
hyperkit: v0.20200224-44-gb54460

Homepage: https://github.com/docker/hyperkit
License: BSD

Does the image pass the checksum?
Which version of macOS?

On my macOS 10.14 machine, it's trivial to reproduce as soon as you use a machine driver newer than 0.12.11.

trivial

unable to run macOS at the moment. Is this also the case for our automated
tests? Can we create a testcase to at least detect this... after which we
can start to bisect and determine the cause of this.
On Mon, Mar 29, 2021 at 6:36 PM Christophe Fergeau @.***>
wrote:

On my macOS 10.14 machine, it's trivial to reproduce as soon as you use a
machine driver newer than 0.12.11.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/code-ready/crc/issues/2158#issuecomment-809273425,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAAOZS6SVUXMHB3DLUWCB3TGBQ4NANCNFSM4Z3MUTFQ
.

--
Gerard Braad | http://gbraad.nl
STEM is the source, but BUILD is how you develop!
[ Better Understanding Involves Learning and Doing ]

Yes some of our tests detected this or it would have slipped into the release.

In https://github.com/moby/hyperkit/commits/master/go https://github.com/moby/hyperkit/commit/ddc56f702668e46900330f0a7e22fccc156e2062 is the first bad commit (go: improve logging) and https://github.com/moby/hyperkit/commit/1d2506619d57a9952b890fc44acf1189920d812c the last good one, which is fairly mysterious...
This one line change applied on top of the 0.13.0 release is enough to trigger the bug, this is both a good starting point, and very puzzling...
diff --git a/pkg/hyperkit/driver.go b/pkg/hyperkit/driver.go
index 3a7f5c2..136515a 100644
--- a/pkg/hyperkit/driver.go
+++ b/pkg/hyperkit/driver.go
@@ -167,6 +167,7 @@ func (d *Driver) Start() error {
        if err != nil {
                return errors.Wrap(err, "new-ing Hyperkit")
        }
+       h.SetLogger(log.New())
        log.Debugf("Using hyperkit binary from %s", h.HyperKit)
        // TODO: handle the rest of our settings.
        h.Kernel = d.VmlinuzPath

And with one more line, the hang is avoided:
diff --git a/pkg/hyperkit/driver.go b/pkg/hyperkit/driver.go
index 3a7f5c2..15862fe 100644
--- a/pkg/hyperkit/driver.go
+++ b/pkg/hyperkit/driver.go
@@ -167,12 +167,13 @@ func (d *Driver) Start() error {
        if err != nil {
                return errors.Wrap(err, "new-ing Hyperkit")
        }
+       h.SetLogger(log.New())
        log.Debugf("Using hyperkit binary from %s", h.HyperKit)
        // TODO: handle the rest of our settings.
        h.Kernel = d.VmlinuzPath
        h.Initrd = d.InitrdPath
        h.VMNet = d.VMNet
-       h.Console = hyperkit.ConsoleFile
+       h.Console = hyperkit.ConsoleStdio
        h.CPUs = d.CPU
        h.Memory = d.Memory
        h.UUID = d.UUID

I suspect this is related to this code path https://github.com/moby/hyperkit/blob/db2be112567e719c7218ecc2b8d19e7f8ae15067/go/hyperkit.go#L543-L606 which we don't take if h.log == nil (0.13.0 behaviour), but which we end up taking with the call to SetLogger. I think this code changed quite a bit with latest version of the hyperkit go module, so I haven't looked yet how the hang can be avoided with it.


Aicourses

What does this PR do?
Add resource(s)
For resources
Description
Added two courses on Artificial Intelligence and Deep Learning by Alfredo Canziani, who is known for delivering high-quality content in the AI field.
Why is this valuable (or not)?
These courses are valuable because Alfredo Canziani is highly regarded in the field of AI, providing a deep understanding of the topics with practical examples and strong theoretical foundations.
How do we know it's really free?
Both courses are freely available on YouTube without requiring any payment or subscription.
For book lists, is it a book? For course lists, is it a course? etc.
These are courses, specifically video tutorials on AI and Deep Learning.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Thanks, and welcome to free-programming-books!


Need more examples for the documents

@Nikhil0504
as you ask, I pin you here XD
We need to complete docs with more examples
docs like this
ideal of docs should be like this
(may be not that much ideal, but a good display of animations will help a lot)
Appreciate your contribution in advance XD

I did one PR for checking. #1366 check and tell if it’s fine

Currently, ManimCommunity contributors are not given Triage permissions... although this may change in the future. This issue seems apt for multiple assignees. It'd be good to have a checklist of which modules need examples and who is being assigned to them so that work can be distributed with redundancy.

I looked into the indication module and feel like there are quite a few problems with the classes defined there:

Naming inconsistencies (for example ShowCreationThenDestruction instead of CreateThenUncreate)
Generally useless classes (why would you use
AnimationOnSurroundingRectangle(mob, AnyAnimation) instead of
AnyAnimation(SurroundingRectangle(mob)) ?)
Overall somewhat confusing

Therefor I propose we delay the creation of example animations until after we decided how to change the interfaces. I will create an Issue with my suggestions shortly.

This issue doesn't really have an explicit goal; we are continuously working on improving the documentation. Closing.


WIP tests for get_forms and has_form?

Tests for proposed api for get_forms/2, and extending has_form?/2 to work on a list of forms. see #42
get_forms/2 to find single or list of forms, but always returns a list.
Let me know how this looks and I'll have a go at the implementation.
Contributor checklist

[ ] Bug fixes include regression tests
[X] Features include unit/acceptance tests

Looks perfect 🔥

beat me to it 😸

Having a look at this now, I've started writing some tests for get_form just to get my head around the current implementation (and there aren't any tests currently), and found an inconsistency.
      form =
        Post
        |> Form.for_create(:create,
          api: Api,
          forms: [
            comments: [
              type: :list,
              resource: Comment,
              create_action: :create
            ]
          ]
        )

      # All good
      assert Form.get_form(form, [:comments]) == nil
      assert Form.get_form(form, "form[comments]") == nil

      # Inconsistent
      assert Form.get_form(form, [:comments, 0]) == nil
      assert Form.get_form(form, "form[comments][0]") == nil # <-- raises Invalid Path: form[comments][0]

Is that intended (the query path version raise and the list version not)?

That sounds problematic and undesired. It would be interesting to see if we can't find out why it fails to parse that path though....nevermind. Its because it is using parse_path! which expects to find a form at that path. We need a different utility that returns nil (or something) when it encounters an index that doesn't exist, so that we can return nil from get_form/2

Cool, I'll have a go at fixing that first

Going to close this since its been stale for a while.

(7 months, to be exact 😆 )


Archived workflows deletion with GC stopped working after move to managed namespace

Pre-requisites

[X] I have double-checked my configuration
[X] I have tested with the :latest image tag (i.e. quay.io/argoproj/workflow-controller:latest) and can confirm the issue still exists on :latest. If not, I have explained why, in detail, in my description below.
[X] I have searched existing issues and could not find a match for this bug
[X] I'd like to contribute the fix myself (see contributing guide)

What happened/what did you expect to happen?
We have lately noticed that in all the clusters where we moved to managed namespaces solution for workflow controllers, deletion of archived workflow has stopped.
Version
latest
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
ConfigMap:
#containerRuntimeExecutor: emissary
podGCGracePeriodSeconds: 60
executor:
  resources:
    requests:
      cpu: 200m
      memory: 128Mi
  env:
    - name: GCE_METADATA_TIMEOUT
      value: 10s
persistence:
  archive: true
  archiveTTL: 10d
  nodeStatusOffLoad: true
  postgresql:
    port:<>
    host: <>
    database: argoworkflows
    tableName: argo_workflows
    userNameSecret:
      name: <>
      key: username
    passwordSecret:
      name: <>
      key: password
workflowDefaults:
  spec:
    ttlStrategy:
      secondsAfterCompletion: 10
      secondsAfterFailure: 20
      secondsAfterSuccess: 10
sso:
  clientId:
    key: client-id
    name: <>
  clientSecret:
    key: client-secret
    name: <>
  issuer: <>
  rbac:
    enabled: true
  scopes:
  - groups
  - email
  sessionExpiry: 168h

Controller deployment:
containers:
    - name: controller
      image: <>/workflow-controller:latest
      command:
        - workflow-controller
      args:
        - '--configmap'
        - workflow-controller-configmap
        - '--loglevel'
        - warn
        - '--gloglevel'
        - '3'
        - '--namespaced'
        - '--workflow-workers'
        - '128'
        - '--workflow-ttl-workers'
        - '32'
        - '--pod-cleanup-workers'
        - '32'
        - '--qps'
        - '60'
        - '--burst'
        - '90'

Logs from the workflow controller
No errors or warning related to GC in logs

Logs from in your workflow's wait container
No errors or warning related to GC in logs

To clarify, do you mean that your archiveTTL setting is not working? Are new Workflows still being correctly archived? They just fail to delete?
Also what namespaces are you deployed in? Which namespace has your Controller ConfigMap, which has your Controller Deployment, and which runs your Workflow Pods?

Yes, the archiveTTL setting is not is not working
New workflows are being correctly archived. They are not getting deleted
Every namespace that has workflow-controller running, has a separate configmap, and runs workflow pods in same namespace.

Explicitly setting up environment variable ARCHIVED_WORKFLOW_GC_PERIOD worked, but this is not something I want to keep in production.

3. Every namespace that has workflow-controller running, has a separate configmap, and runs workflow pods in same namespace.

Oh, you're running everything in the same namespace? The Controller, its ConfigMap, and Workflow Pods are in the same namespace?
In the docs that is defined as a "namespace install", not a "managed namespace", where the Workflows run in a separate NS.

Version
v3.0.0

Also I see you updated your "Version" from latest to v3.0.0. The latter is very old and long unsupported; I suspect you wrote that as a mistake? If you have the Server installed, the UI lists the version in the top left corner. If you're using latest as you have in your manifest, you'd have a specific commit hash

Hey, yes we are running everything in same namespace. So whole package in each namespace.
On the version, we are actually using v3.0.0, apparently, we pushed the v3.0.0 as latest in our registry.

Hey, yes we are running everything in same namespace.

Ok, I've edited your issue title and description to reflect that, as that is a "namespace install" but not a "managed namespace", as I described above.

On the version, we are actually using v3.0.0, apparently, we pushed the v3.0.0 as latest in our registry.

That's an unsupported and very outdated version, so we can't help with that and would not backport any bugfixes in such an old version -- those may have already been long fixed as well.
I've also unticked your :latest checkbox to reflect that as well.
We would highly recommend updating to a supported version, such as 3.4.17 or 3.5.7.


Edge API requests return 502 in response to invalid JSON

How are you running Flagsmith

[ ] Self Hosted with Docker
[ ] Self Hosted with Kubernetes
[X] SaaS at flagsmith.com
[ ] Some other way (add details in description below)

Describe the bug
Requests to the Edge API with invalid JSON payloads return 502 instead of 400 like the Core API does. This can make it seem like a problem with our API when it's not.
Steps To Reproduce
POST invalid JSON to any Edge API endpoint, get 502 in response:
curl -i -X POST 'https://edge.api.flagsmith.com/api/v1/identities' -H 'Content-Type: application/json' -H 'X-Environment-Key: 123' -d '}{'

HTTP/2 502
server: awselb/2.0
date: Wed, 17 Apr 2024 14:42:10 GMT
content-type: text/html
content-length: 122

<title>502 Bad Gateway</title>

502 Bad Gateway

Expected behavior
Any requests made with invalid JSON should return 400 and not 502.
Screenshots
No response

may I be assigned this issue

This code isn't open source yet!


How to ascertain an application is running in 3 tier mode.

Hi,
I have implemented my wcf service and hosted on Local IIS. With the URL I am able to see its metadata (through wsdl).
But I am not sure if my app is running in 3 tier mode.
Please let me know how can I check the same.
Thanks

Can't see how this is related to Moq.


Branch 2.7- Upgrade of related components

Can you upgrade Zookeeper to 3.5. x, Hbase to 2.4. x, Kafka to 2.7. x, and scala to 2.12? Because Flink1.15 does not currently support Zookeeper 3.4 and scala 2.11 。

Please use JIRA instead of PR to ask questions, thanks.


update rector link

Update rector repository link.
Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[x] User guide updated
[ ] Conforms to style guide

@arif-rh Thank you!


J/K syntax highlighting.

Might be a bad idea ... idk \o/

J - I don't know enough about the syntax to write something. k - i've thought about it, maybe

have added some k highlighting


some question about deepmimic architecture

I have a few doubts about states and action spaces. It would be great if you could clarify those. Where is the state and action size computed? humanoid has 34 dof but the actionsize of 36 and statesize of 197. Please help me understand these numbers. and also let me know a way to change them as I may need to remove a few items from the state and experiment.

The state features are using maximum coordinates, so there are more features than dof. You can find the code for computing the state features here:
https://github.com/xbpeng/DeepMimic/blob/ea26c3f2c35fb271d8bfefd53fd49397547c514d/DeepMimicCore/sim/DeepMimicCharController.cpp#L156
For the actions, target angles for spherical joints are represented as quaternion with 4 components. So the number of action parameters can end up being more than the number of dofs. Here's a link to the code for applying actions:
https://github.com/xbpeng/DeepMimic/blob/ea26c3f2c35fb271d8bfefd53fd49397547c514d/DeepMimicCore/sim/CtPDController.cpp#L78


Error: Unknown object type "asyncfunction"

Since last release v0.5.0, there is an issue with compilation;
Logs
[!] (plugin rpt2) Error: Unknown object type "asyncfunction"
src/index.ts
Error: Unknown object type "asyncfunction"
    at Object._object (/home/travis/build/[secure]/[secure]/node_modules/rollup-plugin-typescript2/node_modules/object-hash/index.js:218:17)
    at Object._function (/home/travis/build/[secure]/[secure]/node_modules/rollup-plugin-typescript2/node_modules/object-hash/index.js:319:14)
    at Object.dispatch (/home/travis/build/[secure]/[secure]/node_modules/rollup-plugin-typescript2/node_modules/object-hash/index.js:185:30)
    at /home/travis/build/[secure]/[secure]/node_modules/rollup-plugin-typescript2/node_modules/object-hash/index.js:246:18
    at Array.forEach (<anonymous>)
    at Object._object (/home/travis/build/[secure]/[secure]/node_modules/rollup-plugin-typescript2/node_modules/object-hash/index.js:242:21)
    at Object.dispatch (/home/travis/build/[secure]/[secure]/node_modules/rollup-plugin-typescript2/node_modules/object-hash/index.js:185:30)
    at /home/travis/build/[secure]/[secure]/node_modules/rollup-plugin-typescript2/node_modules/object-hash/index.js:260:23
    at Array.forEach (<anonymous>)
    at Object._array (/home/travis/build/[secure]/[secure]/node_modules/rollup-plugin-typescript2/node_modules/object-hash/index.js:259:20)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Looks like this is an issue with rollup-plugin-typescript2 failing if a plugin uses async functions https://github.com/ezolenko/rollup-plugin-typescript2/issues/105.
Please check https://github.com/ezolenko/rollup-plugin-typescript2#plugins-using-asyncawait for a workaround.

Fixed this by replacing rollup-plugin-typescript with @wessberg/rollup-plugin-ts.

Fixed this by replacing rollup-plugin-typescript with @wessberg/rollup-plugin-ts.

Can you explain what you did please?

@wordisthebird you probably already figured this out, but for future people who come here: rollup-plugin-typescript or some other library is probably out of date and you just need to replace the reference (as seen here) or upgrade it npm install <package name>. You can figure out what node_module is out of date by looking at the stack trace and seeing which one corresponds with this error.


Upgrading Toast View

Description

Fixes #20
Type of Change:

Updated exiting applications

Checklist:

[x] My PR follows the style guidelines of this project
[x] I have performed a self-review of my own code or materials
[x] My branch is up-to-date with the Upstream development branch
[x] I have added necessary images/screenshots of my changes

Please create an issue first describing about your PR then link this issue here,
Add follow all points of PR,
add images of app testing after changing your code.

Upgrading Toast View #20 Created the issue!

Linked issue #20 to the PR!

Hi
You haven't added images of testing and actual working of app, as mentioned above and please go through the README.md , create your commits on separate branch, make sure your project is updated!

Thanks, @aadityamp01  Demo images pinned!

@thisisshivamgupta Thanks for your contribution!


docs: update min k8s version to match 2.10 requirements

Updated the minimum Kubernetes version to match 2.10/2.11 requirements.
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO)

Nice catch! Could you update version 2.11 too?

Done

Thanks!


[BUG] bad translation in spanish version

Describe the bug
translation of farming is "cultivando" not "joseando". Joseando doesn't exist in RAE https://www.rae.es/
To Reproduce
Steps to reproduce the behavior:
Go to 'Language'
Click on 'Spanish'
Go to "Parcelas" or "Granja"
See error
Expected behavior
I expect "Cultivando". Joseando doesn't have meaning in spanish language. Maybe in latam spanish but not in spanish.
This error is in 1.1.3 version. In 1.1.2 the word is "cultivando".

This issue was already fixed.

correct, in the file main.js line 28750 Farming: "Joseando",
in this file shoeld be change Joseando with Cultivando

I guess this is in a issue with the tool for i18n and the current project, probably some sort of cache or something @seeden please have a look, as we mentioned earlier this issue is still present and shouldn't be closed.

Hi.
It was already fixed and merged a few days ago. Version 1.1.5 is using the old version of the GUI.
There is no "joseando" in the es-ES anymore https://github.com/Chia-Network/chia-blockchain-gui/blob/main/src/locales/es-ES/messages.po

How do we get the new version, as I'm running the code from electron (cloning it separately) and it also says Joseando tho, maybe I need to do a different step?

+1

Joseando ando y mi granja cultivando....


ec ioc instances missing some tags?

Running command:
'ec --repo https://github.com/epics-containers/bl38p.git ioc instances bl38p-di-dcam-01'
Returns:
Nothing
Expected:
2023.11.1

hmm maybe this is #39 which I thought I hadd fixed.

If you try 'ec --repo "https://github.com/epics-containers/bl38p.git" ioc instances bl38p-ea-ioc-03' then I would also expect to see "2023.11.1". This case is not "new iocs that have never changed"  or "it gets an error if one of the tags is on the 1st commit"

My take is that that is expected. The idea of my tagging algorithm for IOC instances is that it only shows tags for which the IOC instance has changes since the last tag. That way an IOC that is really stable stays at an old version until it gets modifiied.
This image shows that there were no changes to the folder bl38p-ea-ioc-03 between tags 2023.10.61 and 2023.11.1`. So I think the output of your command above is correct.

Oops I thought I was looking at the changelog of 2023.11.1 at the time but it was actually the commits ahead - therefore i thought the changes were included but they are not released yet


Clean benign errors

That method can be used/overriden by extending code so changing its signature will be a BC break.
It would be better to default $hostname to true and simplify following check to:
if ($local && $hostname && $length) {
    return true;
}

Thank you @Xerkus for you review. I did changes to my code.

Thanks, @codisart


Added Logo

Hi sir @shenzekun ,,, thank you for accepting my proposal .. you can download editables file , .png, .pdf, .ai, eps in Gdrive ..
Best Regard.
Mirza Zulfan

thanks:)


04/11/2018 00:06 : Create Pull Request for branch prTesting_2018041100 -> master

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Logo proposal for 1.0

Since the Kontena 1.0 is nearing, I'm suggesting that the currently very rounded ascii logo is revamped with something like this.
Features include:

3 lines of height (more suitable for displaying in various places because it takes less screen estate) (the current one is 5 lines)
3D looks
Great for t-shirts and hoodies
Less characters
Street credibility

Nice!

Cool! Transparent png with Monaco font:

Sketch, SVG and friends in zip.
kontena-v1-logo.zip

Sweet! Now we have several good candidates for 1.0. Let's figure out a way how to choose the best one :)

@miskun My bad! Actually it's @matti's logo with transparent bitmaps and scalable vectors 😎

Hi Matti, thanks for your submission. Unfortunately it wasn't chosen this time. We appreciate you taking the time and effort to design and submit your design though.


Upload Multiple Files

I tried to upload a 2x5 set of files and ran into
ShadowBatchUploadResponse { file_name: "example_10", status: Error("ShadowDriveServerError { status: 400, message: Object({\"error\": String(\"Error: failed to send transaction: Transaction simulation failed: Error processing Instruction 0: Cross-program invocation with unauthorized signer or writable account\")}) }"), location: None, transaction_signature: None }

for one batch of five, and successful upload for the other batch of five.  I believe this is because instead of waiting for max confirmations on a batch the library instead does
            //wait 1/2 second before going to next batch
            //without this the latest blockhash doesn't align with the server's recent blockhash
            tokio::time::sleep(Duration::from_millis(500)).await;

before proceeding to the next batch with five retries. I have several suggestions. The first is to change this so that instead of sleeping we simply wait for the previous batch to reach max confirmations. The second is to perhaps move this sleep into the retry loop (with a 50-100 ms wait) so that you aren't just spamming retry. The third is to make this retry parameter an input to the function so that the user decides the number of retries (not super sure about this one so let me know what you think about it first).

actually feel free to hold off until v1.5 is finalized, as there or may not may be some breaking changes in this dept

hold off on this for now. closing issue

I know you closed this one for now @cavemanloverboy, but I did take a quick look at it and retest locally. Seems like there may be a race condition in my test where txns aren't finalized server side? We could probably guard against this by inserting a confirmation of the txn id returned from the http call. I might do a little more digging and see if adding that alleviates the intermittent issues I'm seeing.


Write docs 1.0.0

Added docs, updated some instance APIs to match the docs. Added docs for matplotlib despite there being no matplotlib implementation at the moment.

Coverage decreased (-0.02%) to 93.112% when pulling ea28fe4b89be555830117f227f5621a9994c9af6 on write_docs_1.0.0 into 3e3fcc2fceb55e0a2a875d55607d42fe2cac7fc0 on fireant1.0.


SelectedIndex is not working

I'm setting a number in setInchI using useEffect and passing InchI to selectedIndex on scrollPicker as below but its not working and if I pass a static number it is working fine.
useEffect(() => {
inchData().map((i, inx) => {
if (i.value.toString() == heightin) {
setInchI(inx);
let selItem = inchData()[inx];
setInch({
name: selItem.name,
value: selItem.value,
});
}
});
}
}, []);
  <ScrollPicker
        dataSource={inchData().map((item) => item.name)}
        selectedIndex={inchI}
        onValueChange={(data, selectedIndex) => {
          handleChangeInch(selectedIndex);
        }}
        itemTextStyle={{ color: "#6359a6", fontSize: 25 }}
        activeItemTextStyle={{ color: "#6359a6", fontSize: 30 }}
        wrapperHeight={200}
        wrapperBackground="#FFFFFF"
        itemHeight={50}
        highlightColor="#d8d8d8"
        highlightBorderWidth={2}
      />

      please suggest a quick reply. Thanks in advance

Hi @RonakBansal321
Can you provide more code and context.
What is not working, is the activeIndex number wrong?

Hi @RonakBansal321
Can you provide more code and context?

I have used useeffect through which I'm assigning the required data to useState . setInchI is the value of index which is set at useEffect when component loads but selectedIndex is not accepting the number . After that I have passed the data from the previous page now its working fine after that.


Opt-in should be a configuration option

Currently it is always on.

We (Clojurists Together) are using CIVS to distribute ballots to our 200+ members. Making the ballots opt-in is quite tricky as we'll need to keep track of which users have told us that they have opted in so we can send their ballot.
I'd be supportive of a manual verification step for poll senders to change this to opt-out. Perhaps this could be coupled with paying a fee to prevent this being an attractive spam tool?

When you send ballots out, you'll get a list (and a CSV file, if you like) of all the users who haven't opted in, so you can then communicate with them out of band. You can always resend the ballot link later.

Yep, the CSV is definitely very helpful but it's still a fairly laborious process to handle. This is our problem, not yours though! Thanks for CIVS!


Uncaught TypeError: Cannot read property 'path' of null

[Enter steps to reproduce below:]

...
...

Atom Version: 1.2.4
System: Mac OS X 10.11.1
Thrown From: emmet package, v2.3.16
Stack Trace
Uncaught TypeError: Cannot read property 'path' of null
At /Applications/Atom.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/text-buffer.js:770

TypeError: Cannot read property 'path' of null
    at Object.module.exports.getFilePath (/Users/gabrielduncan/.atom/packages/emmet/lib/editor-proxy.coffee:237:24)
    at encodeToBase64 (/Users/gabrielduncan/.atom/packages/emmet/node_modules/emmet/lib/action/base64.js:40:27)
    at Object.encodeDecodeDataUrlAction (/Users/gabrielduncan/.atom/packages/emmet/node_modules/emmet/lib/action/base64.js:131:13)
    at Object.run (/Users/gabrielduncan/.atom/packages/emmet/node_modules/emmet/lib/action/main.js:150:21)
    at Object.run (/Users/gabrielduncan/.atom/packages/emmet/node_modules/emmet/lib/emmet.js:81:23)
    at runAction (/Users/gabrielduncan/.atom/packages/emmet/lib/emmet.coffee:92:12)
    at /Users/gabrielduncan/.atom/packages/emmet/lib/emmet.coffee:57:1
    at Object.module.exports.exec (/Users/gabrielduncan/.atom/packages/emmet/lib/editor-proxy.coffee:80:10)
    at /Users/gabrielduncan/.atom/packages/emmet/lib/emmet.coffee:1:1
    at TextBuffer.module.exports.TextBuffer.transact (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/text-buffer.js:765:18)
    at TextEditor.module.exports.TextEditor.transact (/Applications/Atom.app/Contents/Resources/app.asar/src/text-editor.js:1152:26)
    at atom-text-editor.<anonymous> (/Users/gabrielduncan/.atom/packages/emmet/lib/emmet.coffee:47:19)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:533:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:356:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeydown (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:99:36)
    at HTMLDocument.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:3:61)

Commands
     -2:21.9.0 snippets:next-tab-stop (atom-text-editor.editor.is-focused)
     -2:21.9.0 snippets:expand (atom-text-editor.editor.is-focused)
     -2:21.9.0 editor:indent (atom-text-editor.editor.is-focused)
     -2:07.4.0 editor:select-to-end-of-line (atom-text-editor.editor.is-focused)
     -1:52.4.0 editor:move-to-end-of-screen-line (atom-text-editor.editor.is-focused)
     -1:37 core:move-left (atom-text-editor.editor.is-focused)
  3x -1:31.9.0 core:undo (atom-text-editor.editor.is-focused)
     -1:08.2.0 core:move-down (atom-text-editor.editor.is-focused)
     -1:06.1.0 emmet:insert-formatted-line-break-only (atom-text-editor.editor.is-focused)
     -1:06.1.0 editor:newline (atom-text-editor.editor.is-focused)
     -1:04.9.0 emmet:insert-formatted-line-break-only (atom-text-editor.editor.is-focused)
     -1:04.9.0 editor:newline (atom-text-editor.editor.is-focused)
     -1:01.1.0 core:move-left (atom-text-editor.editor.is-focused)
     -0:47.9.0 core:copy (atom-text-editor.editor.is-focused)
  2x -0:44.4.0 core:undo (atom-text-editor.editor.is-focused)
     -0:01.1.0 emmet:encode-decode-data-url (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "disabledPackages": [
      "vim-mode"
    ]
  }
}

Installed Packages
# User
Stylus, v1.2.1
angularjs, v0.3.3
atom-jade, v0.3.0
emmet, v2.3.16
linter, v1.11.3
linter-eslint, v5.2.4
linter-jade, v0.3.2
markdown-preview-plus, v2.2.2
source-preview-jade, v0.1.1
terminal-plus, v0.14.5

# Dev
No dev packages

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

1

[Enter steps to reproduce below:]

1. ...
2. ...

**Atom Version**: 1.7.3
**System**: Microsoft Windows 10 Pro
**Thrown From**: [emmet](https://github.com/emmetio/emmet-atom) package, v2.4.3

### Stack Trace

Uncaught TypeError: Cannot read property 'path' of null

At C:\Users\Cristian\AppData\Local\atom\app-1.7.3\resources\app.asar\node_modules\text-buffer\lib\text-buffer.js:833
TypeError: Cannot read property 'path' of null
at Object.module.exports.getFilePath (file:///C:/Users/Cristian/.atom/packages/emmet/lib/editor-proxy.coffee:238:24)
at encodeToBase64 (C:\Users\Cristian.atom\packages\emmet\node_modules\emmet\lib\action\base64.js:40:27)
at Object.encodeDecodeDataUrlAction (C:\Users\Cristian.atom\packages\emmet\node_modules\emmet\lib\action\base64.js:131:13)
at Object.run (C:\Users\Cristian.atom\packages\emmet\node_modules\emmet\lib\action\main.js:150:21)
at Object.run (C:\Users\Cristian.atom\packages\emmet\node_modules\emmet\lib\emmet.js:81:23)
at runAction (file:///C:/Users/Cristian/.atom/packages/emmet/lib/emmet.coffee:94:9)
at file:///C:/Users/Cristian/.atom/packages/emmet/lib/emmet.coffee:62:9
at Object.module.exports.exec (file:///C:/Users/Cristian/.atom/packages/emmet/lib/editor-proxy.coffee:80:10)
at file:///C:/Users/Cristian/.atom/packages/emmet/lib/emmet.coffee:61:19
at TextBuffer.module.exports.TextBuffer.transact (C:\Users\Cristian\AppData\Local\atom\app-1.7.3\resources\app.asar\node_modules\text-buffer\lib\text-buffer.js:828:18)
at TextEditor.module.exports.TextEditor.transact (C:\Users\Cristian\AppData\Local\atom\app-1.7.3\resources\app.asar\src\text-editor.js:1274:26)
at atom-text-editor. (file:///C:/Users/Cristian/.atom/packages/emmet/lib/emmet.coffee:60:24)
at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (C:\Users\Cristian\AppData\Local\atom\app-1.7.3\resources\app.asar\src\command-registry.js:260:29)
at CommandRegistry.handleCommandEvent (C:\Users\Cristian\AppData\Local\atom\app-1.7.3\resources\app.asar\src\command-registry.js:3:61)
at CommandRegistry.module.exports.CommandRegistry.dispatch (C:\Users\Cristian\AppData\Local\atom\app-1.7.3\resources\app.asar\src\command-registry.js:160:19)
at AtomEnvironment.module.exports.AtomEnvironment.dispatchApplicationMenuCommand (C:\Users\Cristian\AppData\Local\atom\app-1.7.3\resources\app.asar\src\atom-environment.js:1100:28)
at EventEmitter.outerCallback (C:\Users\Cristian\AppData\Local\atom\app-1.7.3\resources\app.asar\src\application-delegate.js:314:25)
at emitTwo (events.js:87:13)
at EventEmitter.emit (events.js:172:7)

### Commands

3x -1:06.8.0 core:backspace (atom-text-editor.editor.is-focused)
-0:59.3.0 docblockr:parse-enter (atom-text-editor.editor.is-focused)
-0:59.3.0 editor:newline (atom-text-editor.editor.is-focused)
3x -0:58.7.0 core:backspace (atom-text-editor.editor.is-focused)
-0:56 editor:consolidate-selections (atom-text-editor.editor.is-focused)
-0:56 core:cancel (atom-text-editor.editor.is-focused)
-0:43.9.0 core:save (atom-text-editor.editor.is-focused)
-0:42.6.0 tree-view:rename (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)
3x -0:41.9.0 core:move-right (atom-text-editor.editor.mini.is-focused)
3x -0:41.4.0 core:delete (atom-text-editor.editor.mini.is-focused)
-0:40.9.0 core:backspace (atom-text-editor.editor.mini.is-focused)
-0:39.5.0 core:confirm (atom-text-editor.editor.mini.is-focused)
-0:32.8.0 core:save (atom-text-editor.editor.is-focused)
-0:18.4.0 find-and-replace:show (atom-text-editor.editor.is-focused.autocomplete-active)
-0:17.3.0 emmet:encode-decode-data-url (atom-text-editor.editor.mini.is-focused)
-0:14.7.0 find-and-replace:focus-next (atom-text-editor.editor.mini.is-focused)

### Config

```json
{
  "core": {
    "autoHideMenuBar": true,
    "disabledPackages": [
      "spell-check",
      "language-csharp",
      "language-c",
      "language-ruby",
      "language-python",
      "language-ruby-on-rails",
      "atom-minify",
      "linter-jshint",
      "environment",
      "css-clean"
    ],
    "packagesWithKeymapsDisabled": [
      "spell-check",
      "markdown-preview-plus",
      "atom-minify",
      "highlight-line",
      "tree-view",
      "linter",
      "linter-sass-lint"
    ],
    "themes": [
      "atom-light-ui",
      "one-light-syntax"
    ]
  }
}

Installed Packages
# User
auto-indent, v0.5.0
autocomplete-go, v1.0.8
builder-go, v1.0.0
docblockr, v0.7.3
emmet, v2.4.3
file-icons, v1.7.8
go-config, v1.1.4
go-get, v1.0.3
go-plus, v4.1.0
gofmt, v1.1.6
gometalinter-linter, v1.1.0
gorename, v1.0.2
highlight-selected, v0.11.2
language-babel, v2.18.5
linter, v1.11.4
linter-csslint, v1.3.2
linter-sass-lint, v1.4.2
markdown-preview-plus, v2.4.0
navigator-godef, v1.0.3
pigments, v0.26.0
source-preview-babel, v0.1.1
tester-go, v1.0.4

# Dev
No dev packages

[Enter steps to reproduce below:]

...
...

Atom Version: 1.11.2
Electron Version: 0.37.8
System: Microsoft Windows 10 Home
Thrown From: emmet package, v2.4.3
Stack Trace
Uncaught TypeError: Cannot read property 'path' of null
At C:\Users\micha\AppData\Local\atom\app-1.11.2\resources\app.asar\node_modules\text-buffer\lib\text-buffer.js:871

TypeError: Cannot read property 'path' of null
    at Object.module.exports.getFilePath (file:///C:/Users/micha/.atom/packages/emmet/lib/editor-proxy.coffee:238:24)
    at encodeToBase64 (C:\Users\micha\.atom\packages\emmet\node_modules\emmet\lib\action\base64.js:40:27)
    at Object.encodeDecodeDataUrlAction (C:\Users\micha\.atom\packages\emmet\node_modules\emmet\lib\action\base64.js:143:13)
    at Object.run (C:\Users\micha\.atom\packages\emmet\node_modules\emmet\lib\action\main.js:150:21)
    at Object.run (C:\Users\micha\.atom\packages\emmet\node_modules\emmet\lib\emmet.js:81:23)
    at runAction (file:///C:/Users/micha/.atom/packages/emmet/lib/emmet.coffee:94:9)
    at file:///C:/Users/micha/.atom/packages/emmet/lib/emmet.coffee:62:9
    at Object.module.exports.exec (file:///C:/Users/micha/.atom/packages/emmet/lib/editor-proxy.coffee:80:10)
    at file:///C:/Users/micha/.atom/packages/emmet/lib/emmet.coffee:61:19
    at TextBuffer.module.exports.TextBuffer.transact (C:\Users\micha\AppData\Local\atom\app-1.11.2\resources\app.asar\node_modules\text-buffer\lib\text-buffer.js:866:18)
    at TextEditor.module.exports.TextEditor.transact (C:\Users\micha\AppData\Local\atom\app-1.11.2\resources\app.asar\src\text-editor.js:1519:26)
    at atom-text-editor.<anonymous> (file:///C:/Users/micha/.atom/packages/emmet/lib/emmet.coffee:60:24)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (C:\Users\micha\AppData\Local\atom\app-1.11.2\resources\app.asar\src\command-registry.js:260:29)
    at CommandRegistry.handleCommandEvent (C:\Users\micha\AppData\Local\atom\app-1.11.2\resources\app.asar\src\command-registry.js:3:61)
    at CommandRegistry.module.exports.CommandRegistry.dispatch (C:\Users\micha\AppData\Local\atom\app-1.11.2\resources\app.asar\src\command-registry.js:160:19)
    at AtomEnvironment.module.exports.AtomEnvironment.dispatchApplicationMenuCommand (C:\Users\micha\AppData\Local\atom\app-1.11.2\resources\app.asar\src\atom-environment.js:1127:28)
    at EventEmitter.outerCallback (C:\Users\micha\AppData\Local\atom\app-1.11.2\resources\app.asar\src\application-delegate.js:341:25)
    at emitTwo (events.js:100:13)
    at EventEmitter.emit (events.js:185:7)

Commands
     -2:12.1.0 application:add-project-folder (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)
     -1:58.3.0 core:save-as (atom-pane.pane.active)
     -1:56.1.0 application:new-file (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)
     -1:47.2.0 find-and-replace:use-selection-as-find-pattern (atom-text-editor.editor.is-focused)
     -1:45.8.0 editor:consolidate-selections (atom-text-editor.editor.mini.is-focused)
     -1:45.8.0 core:cancel (atom-text-editor.editor.mini.is-focused)
  7x -0:17.9.0 find-and-replace:use-selection-as-find-pattern (atom-text-editor.editor.is-focused)
     -0:13 editor:consolidate-selections (atom-text-editor.editor.is-focused)
     -0:13 core:cancel (atom-text-editor.editor.is-focused)
     -0:11.6.0 find-and-replace:use-selection-as-find-pattern (atom-text-editor.editor.is-focused)
     -0:03.0 emmet:encode-decode-data-url (atom-text-editor.editor.mini.is-focused)

Config
{
  "core": {
    "telemetryConsent": "no",
    "themes": [
      "hacking-the-kernel-ui",
      "eighty-shades-syntax"
    ]
  }
}

Installed Packages
# User
angularjs, vundefined (active)
atom-beautify, v0.29.9 (active)
atom-ternjs, v0.14.2 (active)
autoclose-html, vundefined (active)
color-picker, vundefined (active)
eighty-shades-syntax, v0.0.0 (active)
emmet, v2.4.3 (active)
file-icons, v1.7.17 (active)
git-plus, v5.16.2 (inactive)
hacking-the-kernel, v1.6.1 (inactive)
hacking-the-kernel-ui, v1.5.0 (active)
javascript-snippets, vundefined (active)
linter, v1.11.14 (active)
minimap, v4.24.7 (active)
oceanic-next, vundefined (active)
open-recent, v5.0.0 (active)
pigments, v0.31.2 (active)
sync-settings, v0.7.2 (active)
todo-show, vundefined (active)
tool-bar, vundefined (active)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.52.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.44.0 (inactive)
base16-tomorrow-dark-theme, v1.2.0 (inactive)
base16-tomorrow-light-theme, v1.2.0 (inactive)
one-dark-ui, v1.6.0 (inactive)
one-light-ui, v1.6.0 (inactive)
one-dark-syntax, v1.3.0 (inactive)
one-light-syntax, v1.3.0 (inactive)
solarized-dark-syntax, v1.0.2 (inactive)
solarized-light-syntax, v1.0.2 (inactive)
about, v1.7.0 (active)
archive-view, v0.61.1 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.11.2 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.31.1 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (active)
background-tips, v0.26.1 (active)
bookmarks, v0.42.0 (active)
bracket-matcher, v0.82.1 (active)
command-palette, v0.38.0 (inactive)
deprecation-cop, v0.54.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.40.0 (active)
find-and-replace, v0.201.1 (active)
fuzzy-finder, v1.4.0 (active)
git-diff, v1.1.0 (active)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.2 (active)
image-view, v0.59.0 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.1 (inactive)
markdown-preview, v0.158.0 (active)
metrics, v1.0.0 (active)
notifications, v0.65.1 (active)
open-on-github, v1.2.0 (inactive)
package-generator, v1.0.0 (inactive)
settings-view, v0.242.2-hotfix1 (active)
snippets, v1.0.2 (active)
spell-check, v0.68.2 (active)
status-bar, v1.4.1 (active)
styleguide, v0.47.0 (active)
symbols-view, v0.113.1 (inactive)
tabs, v0.101.0 (active)
timecop, v0.33.2 (active)
tree-view, v0.209.3 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.35.1 (active)
whitespace, v0.33.0 (active)
wrap-guide, v0.38.2 (active)
language-c, v0.52.1 (active)
language-clojure, v0.21.0 (active)
language-coffee-script, v0.47.2 (active)
language-csharp, v0.12.1 (active)
language-css, v0.37.1 (active)
language-gfm, v0.88.0 (active)
language-git, v0.15.0 (active)
language-go, v0.42.1 (active)
language-html, v0.45.1 (active)
language-hyperlink, v0.16.0 (active)
language-java, v0.23.0 (active)
language-javascript, v0.119.0 (active)
language-json, v0.18.2 (active)
language-less, v0.29.5 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.35.0 (active)
language-php, v0.37.2 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.0 (active)
language-ruby, v0.69.0 (active)
language-ruby-on-rails, v0.25.0 (active)
language-sass, v0.56.0 (active)
language-shellscript, v0.22.4 (active)
language-source, v0.9.0 (active)
language-sql, v0.23.0 (active)
language-text, v0.7.1 (active)
language-todo, v0.28.0 (active)
language-toml, v0.18.0 (active)
language-xml, v0.34.9 (active)
language-yaml, v0.26.0 (active)

# Dev
No dev packages


Fixed failing test case.

close #40

Removed the linux-vapor jobs and replaced with. macos tests since some/most devs that use vapor are using macos.


Wrong sensor type in homekit

model: Smart Curtain Motor MJSGCLBL01LM
The light sensor appear as motion sensor in homekit
It’s that true? or it’s a bug?

You need write to Hass repo. Because HomeKit component don't support binary light sensor as light sensor.
https://github.com/home-assistant/core/blob/27bc5e1d7479170cbc3bdb2f4e43e6c525dcfdcc/homeassistant/components/homekit/type_sensors.py#L352-L354


Convert all resources to HQRM

Each module needs to be converted to HQRM standards:

[x] MSFT_xComputer
[x] MSFT_xOfflineDomainJoin
[x] MSFT_xPowerPlan
[x] MSFT_xScheduledTask
[x] MSFT_xVirtualMemory

I'll close this one once the Pester tests are at V4 (issue #106).

This has been completed now.


TransactionConfirmationCheck

Yes. We should check if the transactions that were sent to the network did get confirmations.

hej - sorry didn't see the comment--- finishing this already as we speak... tnx @alexbarnsley...


trainNYU ValueError: num_samples should be a positive integer value,but got num_samples=0

Dear author, hello again.
Thank you for your patient response. I have a new question now and am looking forward to your reply.

Sorry for the late reply. As shown, the dataloader is broken, you should check the directory path and data structure of the NYU V2 data set.

已收到，感谢。


Anvil pipeline

Creates anvil task

Adds anvil dataset getter
Adds anvil data metadata
Adds anvil annotator (uses new dug anvil parser)
Parses all dbgap files GapExchange files are not yet supported by dug

Adds config option for clearing HTTP cache for dug to third party calls.

Holding merge till requirements file is updated with a new dug release.


fix #544

remove dash from maker name key

WAIT -- do not merge yet until discussion in #544 resolved

Thanks!
I came up with #547 already, which includes some style fixes, so I am closing this in favor of that.


Finished Minesweeper levels

Check out my previous pul request for more things to do :-)

:white_check_mark: Build TimeHACK AppVeyor-372 completed (commit https://github.com/TimeHACKDevs/TimeHACK/commit/c7f77ab51c by @jtsshieh)


balancer_by_lua

Here is my first attempt at porting balancer_by_lua from the http module to stream. I have verified that lua code executes in this context, I have not yet ported the FFI module - so I havent verified the upstream manipulation functions yet.
TODO:

Port FFI module & test
Implement ngx_stream_lua_ffi_balancer_get_last_failure, if its possible?

If you have any comments, please dont hesitate. This is an early pull request to facilitate that discussion. I have tried to make it a direct conversion, and used a few string replacements where possible, some comments are hence a bit silly.
I have also thrown #if (NGX_DEBUG) around the unused ngx_connection_t's that where annoying me with errors (and with the right flags, warnings). I can take them out, but I guess they are a plus?

@splitice Thanks for looking into this. Will you port the tests too?

I dont have an environment to run them, but a bit of regex would probably do the configuration changes necessary. The error messages would need to be done manually I guess.
I'd be happy to do that much.

@splitice There are perl scripts under util/ that can do most of the modifications needed when porting the tests.

I'll take a look, its probably not dissimilar to what I whipped up.
Currently looking for the cause of a bug, s->connection->log is null in the balancer context causing a segfault when any error occurs or with ngx.log.

Fix stream session session passing, now it works. Successfully set the current peer to a dynamic value.

There is a bunch of style fixes

@splitice The ngx-releng does not follow symlinks BTW.

@splitice Thanks for your quick updates.
@doujiang24 Please have a look at this PR when you have a chance. Thanks!

@splitice
Could you give me your balancer_by_lua source code,I'd like to have a look.
Thank you.

This is a pull request for the code.

@splitice
The pull request has not been accepted,has it ?
How can I get your source code?

Its in my branch - https://github.com/splitice/stream-lua-nginx-module

@splitice
In the page of https://github.com/splitice/stream-lua-nginx-module

@splitice
Hi,
Cloud you give me some advises to use the function of balance_by_lua,I have been trapped here for long time,please help me.
One more question,In the balancer_by_lua_block,can I set the proxy address .

@daxiong380380 balancer_by_lua* is officially documented in lua-nginx-module:
https://github.com/openresty/lua-nginx-module#balancer_by_lua_block
What is implemented here should be (mostly) compatible.

@agentzh any ETA on when this PR will be merged? What needs to be done to get this merged into upstream? I can try to help, if I manage to get my head around the nginx module stuff.

This needs to be rebased to the latest master branch before it can get merged.
Also it has various coding style issues that need to be fixed before the merge.

@rshriram No ETA yet since it has unresolved issues (see my comments above).

We need to pass as many test cases as possible from ngx_http_lua_module for balancer_by_lua* and ngx.balancer here.

I currently do not have any time to spend on this patch. PR's welcome to my fork.
I am happy to re-base, but without style work its frivolous currently. I just don't have time for that currently.

@splitice @agentzh I have fixed all the styling issues.. and my branch is here: https://github.com/rshriram/stream-lua-nginx-module
Should I send a PR to @splitice so that the issue history is maintained, or shall I open up a new PR ? All of @splitice 's commit history is maintained in either case. Just want to avoid the extra hop.

@rshriram Creating your own PR is more convenient given that @splitice is busy atm.

No concerns on my end, do whichever is easiest / Github allows :)

Closed in favour of further work by @rshriram


As VALIDATOR, I want to cross-check my study data against the study define.xml for lack of comments or not indicating no data for expected variables that are always null so that I meet the business rule stated in the Define-XML specifications

This check applies to SEND and SDTM data. ADaM does not have Core = Expected.
This check needs CDISC Library for the Core metadata.
This check is IG-version-agnostic.
This check is an extension to SD1149.

From the Define-XML v2.1 specifications:

Used to indicate that an ItemRef that represent a dataset’s variable has no data. Note that variables refer to both standard and non-standard/ supplemental qualifiers variables (/ODM/Study/MetaDataVersion/ItemGroupDef/ItemRef or /ODM/Study/MetdataVersion/def:ValueListDef/ItemRef).
Business Rule: A comment must be included to explain why no data is present for dataset’s variables that were planned for use in the study.

Create "define_variable_has_comment"


[FLINK-2043] Change the KMeansDataGenerator to allow passing a custom path

https://issues.apache.org/jira/browse/FLINK-2043

Thank you for taking care of this.
The change looks good, +1 to merge

Thanks! Looks good. Will merge


Factory installers not keeping settings.

Yo, finally got around to testing my suggestion! Fund out they don't keep the factory's settings when installed (Input/output OR upgrades)

Also, the purification chamber when upgraded it doesn't accept gas upgrades, though it says they're supported.

  Working on it right now.

Fixed in development! :)

Thank you!


Raise error when ip command not found instead of skipping if OS is Mac.

How to categorize this PR?

/area dev-productivity testing
/kind bug test
What this PR does / why we need it:
This PR raises error when ip not found instead of skipping if OS is Mac. By default, in Mac ip command is not installed and it's better to fail fast than waiting until e2e test to fail.
Recent PR https://github.com/gardener/gardener/pull/7245 introduced ip command to adapt multi availability zone handling of istio to local mac requirements.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

/test pull-gardener-e2e-kind-ha-multi-zone

FYI @juergenschneider


Add hex colors support

Basically what the title says :D

asd#FFFFFF123 results in asd&x§f§f§f§f§f§f123 I don't think that will work? Shouldn't it be asd§x§f§f§f§f§f§f123.
(ChatColor.translateAlternateColorCodes checks if it's a valid color code at least in 1.8.8 API)


Passthrough of USB gamepad

Is it possible to pass a game controller through to the remote session? I am using a retropad via usb on the local machine. I have enabled RemoteFX USB Device Redirection on the windows box. I'm not sure how I could even check to see if the gamepad is showing up on the remote box (Ubuntu 20). Is this even possible?

It is not possible right now.


Error

Oh come on. This is their server error, ie., 5xx error. Their server can't handle all the requests from time to time.


Regerate JS docs + host on GH pages

resolved in https://github.com/IBM-Bluemix/cf-nodejs-client/commit/51b4181d440db2b831243fe164986717acea6611#diff-04c6e90faac2675aa89e2176d2eec7d8


balena-image: moved kernel to rootfs

Moved out kernel to rootfs partition.
Changelog-entry: no space left on boot partition fixed
Signed-off-by: Alvaro Guzman<EMAIL_ADDRESS>

@floion just moved the same changes to this PR because the other had some merged-based issues.


client

Client

Author(s): Tanner

Introduction
The client helper will allow Vapor applications to communicate with other APIs or services.
Motivation
APIs frequently need to use or post data to other services.
Proposed solution
Add a client helper on the Application class that wraps VeniceX/HTTPClient or NSURLSession in the future.
Code snippets
app.client.get("http://google.com", ["q": "test"]) { response in
    switch response {
        case .Success(let response):
            print("Response: \(response)")
        case .Error(let message):
            print("Uh oh: \(message)")
    }

    do {
        let response = try response.extract()
        print("Response: \(response)")
    } catch {
        print("Uh oh: \(error)")
    }

    let response = try? response.extract()
    print("Response?: \(response)")
}

Impact
This only adds functionality.
Alternatives considered
Using only a closure for getting the response value was considered, but the .extract() method gives all possibly desired functionality.

I know this is already approved, but I'd like to make a counterproposal. I'd like to make this client library something that is very dynamic and reuses as much code as possible. I also think this library should be a separate repository than Vapor, but integrates with it very well. Maybe call it something like Condensation or Deposition. 😉

Initially, the library would look a lot like Alamofire by having requests like:
Client.get("http://url.com/hello/world").success { request, response in

    }.failure { request, response in

    }.run()

However, where it begins being unique is having the ability to use conditionals to deal with responses. For example, to use conditionals to have different success callbacks for different response codes, one would code this:
let request = Client.get("http://url.com/hello/world")
    .condition({ request, response in return response.code == 204 }) { request in
        request.success { request, response in }
    }.condition({ return $1.headers[.Connection: "keep-alive"] ) { request in
        request.success { request, response in }
        request.failure { request, response in }
    }.success { request, response in // If none of the above conditions are true, run this

    }.failure { request, response in

    }.run()

Another key concept for this framework is being able to build requests off each other. For instance, say we make a base request like so:
let base = Client.base("http://url.com/").headers([.UserAgent: "Vapor"]).params(["api-key": "abc"]).auth(/* Some stuff */)

We can then make a request to http://url.com/hello/world by using the base request and sharing the headers and parameters like this:
base.get("hello/world").success { request, response in

    }.failure { request, response in

    }.run()

One can even create an endpoint base off another endpoint base like this:
let helloBase = base.base("hello")
helloBase.get("world").run()

One can then build a hierarchy of endpoints like this:
struct Endpoints {
    static let base = // Same as above
    static let helloWorld = base.get("hello/world").response { request, response in

    }
    static let apiTest = base.get("api/test").response { request, response in

    }

    struct Base {
        static let base = Endpoints.base.base("/some-base")
        static let someOtherEndpoint = base.get("some-endpoint").response { request, response in

        }
    }
}

Then developers can easily access any of their preconfigured endpoints like this:
Endpoints.helloWorld.run()
Endpoints.Base.someOtherEndpoint.run()

However, that's just scratching the surface. Another handy feature would be the ability to overwrite properties of the base endpoint, like this:
let base = Client.get("http://url.com/hello/world").params(["test1": "abc", "test2": 123, "test3": true])
base.params(["test1": "def", "test2": nil]).run()

Executing this code would send a request with the parameters of ["test1": "def", "test3": true]. Setting the test2 key to nil removed the key completely. This would theoretically work with any other value too.

Then, there's the ability to insert variables into request parameters. For instance, one could execute...
let base = Client.get("http://url.com/search/{search-key}").params(["page": "{page-num}", "result-count": 10])
base.vars(["search-key": "hello world!", "page-num": 5]).run()

...which would send a request to the URL http://url.com/search/hello%20world! with the parameters ["page": 5, "result-count": 10].

In addition, one would be able to chain success blocks like so:
Client.get("http://url.com/hello/world").success { request, response, next in
        if /* something wrong with data */ {
            throw Error("Oh no!") // Goes to `error` callback
        } else {
            next() // Goes to next `success` callback, there could be many chained success callbacks in a row
        }
    }.success { request, response in
        // Do something else with the data
    }.failure { request, response in
        // Only a request failure, like a 404
    }.error { error in
        // An actual error thrown
    }.run()

Finally, the library would be able to cast responses into Swift serializable objects. This would make it possible to share objects between Vapor and clients.
endpoint
    .success(User.self, dataSource: .body) { user in /* Do something with the user */ }
    .failure(RequestFailure.self, dataSource: .body) { requestFailure in /* Do something with the failure */ }
    .error { error, request, response in
        // Error casting User or Error
    }.run()

The dataSource property would define where the data for the object comes from, such as a JSON body or the parameters.
Notice that you can still retrieve the request and response variables if needed or exclude them if necessary.
In addition, response bodies are automatically casted into their respective datatypes, like JSON or images. For instance, one could get the JSON data by saying this:
endpoint
    .success { request, response in
        if let json = response.data as? JSON {
        /* or */
        if let json = JSON(data: response.rawData) {

        }
    }.failure { request, response in }
    .run()

However, using the ability to automatically cast data into data types, one could do this in a much more elegant fashion like this:
endpoint
    .success(JSON.self) { json in /* Do do something with the JSON */ }
    .failure(XML.self) { xml in /* Do somethign with the XML */ }
    .run()

I could go on, but I think I've written enough to give you a good idea of what I'm talking about. I started implementing this idea with someone else about a year ago, but didn't get too far. To reiterate, I think that this would be a good project to put in a separate repository.


Merging changes from master

[x] Merging changes from master to feature_branch

Codecov Report

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

@@               Coverage Diff                @@
##             feature/style     #188   +/-   ##
================================================
  Coverage                 ?   86.13%
================================================
  Files                    ?       10
  Lines                    ?      642
  Branches                 ?        0
================================================
  Hits                     ?      553
  Misses                   ?       89
  Partials                 ?        0

Continue to review full report at Codecov.

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


Zoom to focal point on double tap and scale gestures

It uses GestureDetector wrapper package as a dependency that I wrote to achieve this behavior.

Sorry, some other PR's caused merge conflicts, would you mind taking a look and fixing that up?

Latest commits are now merged into the branch.

Thanks for letting me know, the conflict is now fixed.


spirv-opt: An off-by-1 error in constant folding

Consider the following SPIR-V
               OpCapability Shader
          %1 = OpExtInstImport "GLSL.std.450"
               OpMemoryModel Logical GLSL450
               OpEntryPoint Fragment %4 "main"
               OpExecutionMode %4 OriginUpperLeft
               OpSource ESSL 310
          %2 = OpTypeVoid
          %3 = OpTypeFunction %2
          %6 = OpTypeFloat 32
          %7 = OpTypeVector %6 3
          %8 = OpConstant %6 0
          %9 = OpConstantComposite %7 %8 %8 %8
         %10 = OpTypeVector %6 4
          %4 = OpFunction %2 None %3
          %5 = OpLabel
         %11 = OpCompositeConstruct %10 %9 %8
         %12 = OpCompositeExtract %6 %11 3
               OpReturn
               OpFunctionEnd

An attempt to replace the use of %11 in %12 fails because of the off-by-1 error in
https://github.com/KhronosGroup/SPIRV-Tools/blob/b78f4b1518e0052491f4e7e01ace4ee915cb5de2/source/opt/folding_rules.cpp#L1469-L1479

@s-perron, @alan-baker ping

@Vasniktel For things like this, feel free to submit a PR with the fix.  You seem to have already done all of the work it identify the exact change that is required.

@s-perron, added a PR.


Mutiny support on Apollo Android (Java/kotlin) GraphQL client

Hi @cescoffier @jponge,
I'm new to Mutiny, I tried to translate ReactorApollo to MutinyApollo.
I was a bit confused about Emitter and Cancelable. What is the equivalent of Disposable in Mutiny ?
Thanks
Moncef

Please use https://github.com/smallrye/smallrye-mutiny/discussions


Update integration tests, add config files

PR summary
This PR adds following changes:

the search and tagging integration tests were fixed so that they will skip tests if the ghost.env file is not present, but will also run if it IS present
added the search/tagging config file to the project
added the config file for iam-access-groups to the project

Fixes: n/a
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] New tests
[x] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

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


user defined params in authorize phrase not supported

certain service, such as flickr, needs to use 'perms=read' in authorize url to specify permission requested.  I don't see this is supported in latest version yet.
supporting user defined parameter for authorize url can fix this problem and more

With oauth2 the equivalent parameter is scope and there is also a dictionary parameters
But Flickr use oauth1 and there is no parameters
So the current workaround is to specify the url with the query parameter ie. ....authorize?perm=read

this is a good workaround, I will check it out

this workaround works


Angles function of safe API have wrong docstrings

[TBD]

Fixed in #454.

Specifically, https://github.com/poliastro/poliastro/commit/face44f72ecfe200bf4f0048cdf98e1af3063805.


Need a setting about indentation of broken down attributes

By default now, attributes start at the column which was the start of the first attribute of the element. I want a setting to switch the following behavior: when breaking up attribute in lines, indent a second line by stable 4 spaces from the start of the element.

fixed in 2.1


Tip of wing should technically be wing color

Not 0 (default pixel color)

Description
It does not do much
Compatibility
Not breaking
Caveats
I just think this is funny, not super important to fix since the background should default to white anyway.

Thanks. LGTM 👍
But this PR has commitlint error.
Could you change your commit message? 🤔
# edit your commit message
$ git commit --amend -m "fix: tip of wing should technically be wing color "

# force push branch
$ git push --force-with-lease origin patch-1

ref #349
Thank you for your PR, but I will close it. 🙇🙇🙇


MPI_Comm_create hangs for disjoint groups

Original author: Xiang Ni
Original issue: https://charm.cs.illinois.edu/redmine/issues/894

When different groups are passed by different subsets of processors, the call hangs. Example code can be found in MPI1/DGEMM from https://github.com/ParRes/Kernels.

Original date: 2015-11-21 20:47:20

In MPI-1.1, it was an error for users to call MPI_Comm_create with multiple groups. In MPI-2.2, MPI_Comm_create was changed to allow users to pass multiple disjoint groups with an intra-communicator, to simplify user code. AMPI currently hangs for the case with multiple disjoint groups.

Original date: 2015-11-25 19:06:35

~~https://charm.cs.illinois.edu/gerrit/#/c/919/~~ https://github.com/UIUC-PPL/charm/commit/6afa9951a48ec6e4cc9527f05f1fe4556c043a7f


check devel with last commit

In order to keep waybar-updates AUR Helper-agnostic I'm now checking if devel packages need an update using the latest commit on the git repository.
This version works for me at the moment, I'm still testing it.
Depending on the number of "devel" packages installed, the first run may take more or less time, but inside "check_updates offline", you only check the packages that have been previously flagged with changes upstream.

I think this PR is ready to be reviewed / merged !
Development packages have a suffix denoting their Version Control System.
Because these packages only download the latest available source when you execute makepkg, their pkgver() in the AUR does not reflect upstream changes.
AUR Helpers (like paru, yay etc.) maintain a database during installation/update to keep track of the last commit, and thus detect when an update is required after a new commit.
Advantage: speed because a database is used.
Disadvantage: if you install a package using an AUR Helper, others won't be able to detect that an update is needed.
You can enable development package checking (-git) using waybar-updates -d (or --devel, disabled by default).
The first run may take some time (depending on how many development packages you have) because we need to retrieve the git repository url then use git ls-remote to find the latest commit.
Once done, since the necessary informations are known, we just need to check the last commit.

@jlaunay could you run shellcheck on it and fix any issues it will highlight? (JetBrains IDEs support it mostly out of the box). Also I am confused by "from Devel" terminology. Devel is not a source like pacman or AUR repos, it's just a kind of AUR-packages. So maybe we will use something like "1 devel-update available from AUR"?

I have added ShellCheck GitHub action, but seems like there is no way to launch this check on already created PR...

@jlaunay could you run shellcheck on it and fix any issues it will highlight? (JetBrains IDEs support it mostly out of the box). Also I am confused by "from Devel" terminology. Devel is not a source like pacman or AUR repos, it's just a kind of AUR-packages. So maybe we will use something like "1 devel-update available from AUR"?

I run this against shellcheck and change for "devel-update available from AUR".
French translation is OK, you should check for "ru" and "tr_TR"

@ouztheone do you have time to check Turkey tranlation?

@ouztheone do you have time to check Turkey translation?

Hey, thanks for the heads up. I added my suggestions. :)

@jlaunay I will release update tomorrow, out of desk now!

@jlaunay I will release update tomorrow, out of desk now!

Thanks a lot, in the meantime, I published a waybar-updates-git package on AUR.


Pages of long scripts become choppy

I'm using an old MacBook and struggling with its pitiful performance. The extension works just fine on other GitHub pages. But when it comes to a long script with several hundred lines, the page becomes extremely slow and scrolls choppy. Which features could I switch off to help with this?
Also: What would be the most efficient way to go through all the features, find out what each of them does and rule out the ones I don't need?
Many thanks in advance! ♥

a long script with several hundred lines

Do you mean source files? Maybe disabling show-whitespace would help.

What would be the most efficient way to go through all the features, find out what each of them does and rule out the ones I don't need?

Go to the options page, there's a list of toggable features with a short description and a screenshot for each one.

What browser? Does it happen without Refined Github?
With Safari, performance on long PRs is terrible even without RGH on my 2019 i9 MacBook too. It's a combination of bad browser and bad GitHub.

Do you mean source files? Maybe disabling show-whitespace would help.

I sure hope not since we specifically do not touch lines outside the viewport (other than for watching them via IntersectionObserver) 😬

Also: What would be the most efficient way to go through all the features, find out what each of them does and rule out the ones I don't need?

There's also a "Find feature…" button that lets you find out whether there's a specific feature slowing you down (unlikely, but…)

What browser? Does it happen without Refined Github?

@fregante I'm using Chrome and yes, it performs properly without Refined GitHub.

Do you mean source files? Maybe disabling show-whitespace would help.

This actually helps...😂  I tried back and forth, and this specific one does make differences. @cheap-glitch Thanks a lot!
Thank you both for the advices :)


Frontend rewrite

The frontend works well, but it has become hard to maintain in the long run:

The plotting library limits what we can display, we have to switch to something more flexible
It's a big hack to share code between the pipeline and the frontend, we can only share a single file with some inlined bits of yojson
It's hard to display pipeline informations on the frontend, since they can only communicate via postgres on one side and graphql on the other
And yeah, I'm not happy that Rescript is slowly changing OCaml semantics, is stuck on 4.09, the abysimal build system, etc. and I haven't even mentionned the npm/nodejs monster that creeps under a mountain of code.

The good news is that we don't actually that much javascript on the frontend! We could just have a standard webserver written in OCaml and push HTML to the browser.

Only the graphs require javascript, since we have to know their size to draw them properly.
We could also drop the Hasura/GraphQL. It's cool and all, but it creates another mismatch / redundancy between the existing SQL code in the pipeline and the frontend.

The good news is that we don't actually that much javascript on the frontend! We could just have a standard webserver written in OCaml and push HTML to the browser.

We've a lot of Rescript right now, though!


Update torustrooper to 0.22.2

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Thank you for the contribution. It was merged directly as 000645fe463eb8d377695c72df1cf871cf97cae7. Your contribution is still credited to you.


Yosef dev2

The major additions so far:

Seperated the protein metadata from AbundanceTable so that AbundanceTable does not need the list of uniprot id's from the metadata.
Added more metadata to the protein page
Added tooltips to Taxonomic Similarity and Chemical Similarity

Pull Request Test Coverage Report for Build 933

65 of 68 (95.59%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 91.76%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/scenes/BiochemicalEntityDetails/DataTable/DataTable.js
15
16
93.75%

src/scenes/BiochemicalEntityDetails/Protein/AbundanceDataTable.js
17
18
94.44%

src/scenes/BiochemicalEntityDetails/Protein/MetadataSection.js
17
18
94.44%

Totals

Change from base Build 920:
-0.2%

Covered Lines:
1181

Relevant Lines:
1243

💛  - Coveralls

I have made those changes. I also updated taxonomy in the metabolites page.
There is currently one integration test which is failing -- TaxonomyFilter. I made some changes to TaxonomyFilter, so this makes sense, but I cannot figure out why the test is failing. The filter appears to work normally in the actualy page. Do you think you could take a look?


Poland test files for 1.2.1 schema

Hi @SchulzeStTSI @daniel-eder, could you accept the PR?

@gregsons Schema 1.2.1 is not yet being merged - @SchulzeStTSI may be able to give more insight