TiFlash crash in failpoint test

Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)

[2023/06/19 06:54:16.425 +08:00] [ERROR] [BaseDaemon.cpp:376] [########################################] [source=BaseDaemon] [thread_id=1585]
[2023/06/19 06:54:16.425 +08:00] [ERROR] [BaseDaemon.cpp:377] ["(from thread 263) Received signal Segmentation fault(11)."] [source=BaseDaemon] [thread_id=1585]
[2023/06/19 06:54:16.425 +08:00] [ERROR] [BaseDaemon.cpp:405] ["Address: NULL pointer."] [source=BaseDaemon] [thread_id=1585]
[2023/06/19 06:54:16.426 +08:00] [ERROR] [BaseDaemon.cpp:413] ["Access: read."] [source=BaseDaemon] [thread_id=1585]
[2023/06/19 06:54:16.426 +08:00] [ERROR] [BaseDaemon.cpp:425] ["Unknown si_code."] [source=BaseDaemon] [thread_id=1585]
[2023/06/19 06:54:16.438 +08:00] [WARN] [ExchangeReceiver.cpp:1004] ["connection end. meet error: true, err msg: Exchange receiver meet error : From MPP<query:<query_ts:1687128853723203110, local_query_id:9879, server_id:1736808, start_ts:442270706204147713>,task_id:14>: Code: 0, e.displayText() = DB::Exception: write to tunnel tunnel14+15 which is already closed, , e.what() = DB::Exception,, current alive connections: 2"] [source="MPP<query:<query_ts:1687128853723203110, local_query_id:9879, server_id:1736808, start_ts:442270706204147713>,task_id:16> ExchangeReceiver_69 tunnel9+16"] [thread_id=1209]
[2023/06/19 06:54:16.438 +08:00] [WARN] [ExchangeReceiver.cpp:1004] ["connection end. meet error: true, err msg: Exchange receiver meet error : From MPP<query:<query_ts:1687128853723203110, local_query_id:9879, server_id:1736808, start_ts:442270706204147713>,task_id:14>: Code: 0, e.displayText() = DB::Exception: write to tunnel tunnel14+15 which is already closed, , e.what() = DB::Exception,, current alive connections: 2"] [source="MPP<query:<query_ts:1687128853723203110, local_query_id:9879, server_id:1736808, start_ts:442270706204147713>,task_id:16> ExchangeReceiver_75 tunnel14+16"] [thread_id=240]
[2023/06/19 06:54:16.451 +08:00] [WARN] [ExchangeReceiver.cpp:1023] ["Finish receiver channels, meet error: true, error message: Exchange receiver meet error : From MPP<query:<query_ts:1687128853723203110, local_query_id:9879, server_id:1736808, start_ts:442270706204147713>,task_id:14>: Code: 0, e.displayText() = DB::Exception: write to tunnel tunnel14+15 which is already closed, , e.what() = DB::Exception,"] [source="MPP<query:<query_ts:1687128853723203110, local_query_id:9879, server_id:1736808, start_ts:442270706204147713>,task_id:16> ExchangeReceiver_69"] [thread_id=1209]
[2023/06/19 06:54:16.453 +08:00] [WARN] [ExchangeReceiver.cpp:1023] ["Finish receiver channels, meet error: true, error message: Exchange receiver meet error : From MPP<query:<query_ts:1687128853723203110, local_query_id:9879, server_id:1736808, start_ts:442270706204147713>,task_id:14>: Code: 0, e.displayText() = DB::Exception: write to tunnel tunnel14+15 which is already closed, , e.what() = DB::Exception,"] [source="MPP<query:<query_ts:1687128853723203110, local_query_id:9879, server_id:1736808, start_ts:442270706204147713>,task_id:16> ExchangeReceiver_75"] [thread_id=240]
[2023/06/19 06:54:16.491 +08:00] [WARN] [ExchangeReceiver.cpp:1004] ["connection end. meet error: true, err msg: Exchange receiver meet error : From MPP<query:<query_ts:1687128853723203110, local_query_id:9879, server_id:1736808, start_ts:442270706204147713>,task_id:14>: Code: 0, e.displayText() = DB::Exception: write to tunnel tunnel14+15 which is already closed, , e.what() = DB::Exception,, current alive connections: 2"] [source="MPP<query:<query_ts:1687128853723203110, local_query_id:9879, server_id:1736808, start_ts:442270706204147713>,task_id:19> ExchangeReceiver_139 tunnel15+19"] [thread_id=941]
[2023/06/19 06:54:16.492 +08:00] [WARN] [ExchangeReceiver.cpp:1023] ["Finish receiver channels, meet error: true, error message: Exchange receiver meet error : From MPP<query:<query_ts:1687128853723203110, local_query_id:9879, server_id:1736808, start_ts:442270706204147713>,task_id:14>: Code: 0, e.displayText() = DB::Exception: write to tunnel tunnel14+15 which is already closed, , e.what() = DB::Exception,"] [source="MPP<query:<query_ts:1687128853723203110, local_query_id:9879, server_id:1736808, start_ts:442270706204147713>,task_id:19> ExchangeReceiver_139"] [thread_id=941]
[2023/06/19 06:54:16.497 +08:00] [WARN] [TiRemoteBlockInputStream.h:74] ["remote reader meets error: Receiver state: ERROR, error message: Exchange receiver meet error : From MPP<query:<query_ts:1687128853723203110, local_query_id:9879, server_id:1736808, start_ts:442270706204147713>,task_id:14>: Code: 0, e.displayText() = DB::Exception: write to tunnel tunnel14+15 which is already closed, , e.what() = DB::Exception,"] [source="TiRemote(ExchangeReceiver) MPP<query:<query_ts:1687128853723203110, local_query_id:9879, server_id:1736808, start_ts:442270706204147713>,task_id:19> ExchangeReceiver ExchangeReceiver_139 ExchangeReceiver_139"] [thread_id=285]
[2023/06/19 06:54:16.497 +08:00] [WARN] [TiRemoteBlockInputStream.h:74] ["remote reader meets error: Receiver state: ERROR, error message: Exchange receiver meet error : From MPP<query:<query_ts:1687128853723203110, local_query_id:9879, server_id:1736808, start_ts:442270706204147713>,task_id:14>: Code: 0, e.displayText() = DB::Exception: write to tunnel tunnel14+15 which is already closed, , e.what() = DB::Exception,"] [source="TiRemote(ExchangeReceiver) MPP<query:<query_ts:1687128853723203110, local_query_id:9879, server_id:1736808, start_ts:442270706204147713>,task_id:19> ExchangeReceiver ExchangeReceiver_139 ExchangeReceiver_139"] [thread_id=324]
[2023/06/19 06:54:16.498 +08:00] [WARN] [TiRemoteBlockInputStream.h:74] ["remote reader meets error: Receiver state: ERROR, error message: Exchange receiver meet error : From MPP<query:<query_ts:1687128853723203110, local_query_id:9879, server_id:1736808, start_ts:442270706204147713>,task_id:14>: Code: 0, e.displayText() = DB::Exception: write to tunnel tunnel14+15 which is already closed, , e.what() = DB::Exception,"] [source="TiRemote(ExchangeReceiver) MPP<query:<query_ts:1687128853723203110, local_query_id:9879, server_id:1736808, start_ts:442270706204147713>,task_id:19> ExchangeReceiver ExchangeReceiver_139 ExchangeReceiver_139"] [thread_id=745]
[2023/06/19 06:54:16.498 +08:00] [WARN] [TiRemoteBlockInputStream.h:74] ["remote reader meets error: Receiver state: ERROR, error message: Exchange receiver meet error : From MPP<query:<query_ts:1687128853723203110, local_query_id:9879, server_id:1736808, start_ts:442270706204147713>,task_id:14>: Code: 0, e.displayText() = DB::Exception: write to tunnel tunnel14+15 which is already closed, , e.what() = DB::Exception,"] [source="TiRemote(ExchangeReceiver) MPP<query:<query_ts:1687128853723203110, local_query_id:9879, server_id:1736808, start_ts:442270706204147713>,task_id:19> ExchangeReceiver ExchangeReceiver_139 ExchangeReceiver_139"] [thread_id=330]
[2023/06/19 06:54:16.498 +08:00] [WARN] [TiRemoteBlockInputStream.h:74] ["remote reader meets error: Receiver state: ERROR, error message: Exchange receiver meet error : From MPP<query:<query_ts:1687128853723203110, local_query_id:9879, server_id:1736808, start_ts:442270706204147713>,task_id:14>: Code: 0, e.displayText() = DB::Exception: write to tunnel tunnel14+15 which is already closed, , e.what() = DB::Exception,"] [source="TiRemote(ExchangeReceiver) MPP<query:<query_ts:1687128853723203110, local_query_id:9879, server_id:1736808, start_ts:442270706204147713>,task_id:19> ExchangeReceiver ExchangeReceiver_139 ExchangeReceiver_139"] [thread_id=343]
[2023/06/19 06:54:16.499 +08:00] [ERROR] [BaseDaemon.cpp:569] ["\n       0xad20b5d\tfaultSignalHandler(int, siginfo_t*, void*) [tiflash+181537629]\n                \tlibs/libdaemon/src/BaseDaemon.cpp:220\n  0x7f65e1cb2d90\t<unknown symbol> [libc.so.6+347536]\n       0x42b0989\tlong std::__1::__cxx_atomic_fetch_sub<long>(std::__1::__cxx_atomic_base_impl<long>*, long, std::__1::memory_order) [tiflash+69929353]\n                \t/usr/local/bin/../include/c++/v1/atomic:1082\n       0x42b06f3\tstd::__1::__atomic_base<long, true>::fetch_sub(long, std::__1::memory_order) [tiflash+69928691]\n                \t/usr/local/bin/../include/c++/v1/atomic:1736\n       0x42be7a7\tMemoryTracker::free(long) [tiflash+69986215]\n                \tdbms/src/Common/MemoryTracker.cpp:182\n       0x42be811\tMemoryTracker::free(long) [tiflash+69986321]\n                \tdbms/src/Common/MemoryTracker.cpp:197\n       0xbd6dfc9\tDB::MemTrackerWrapper::free(unsigned long) [tiflash+198631369]\n                \tdbms/src/Flash/Mpp/TrackedMppDataPacket.h:81\n       0xbd6df29\tDB::MemTrackerWrapper::freeAll() [tiflash+198631209]\n                \tdbms/src/Flash/Mpp/TrackedMppDataPacket.h:104\n       0x41ddfc5\tDB::MemTrackerWrapper::~MemTrackerWrapper() [tiflash+69066693]\n                \tdbms/src/Flash/Mpp/TrackedMppDataPacket.h:99\n       0x41e489e\tDB::TrackedMppDataPacket::~TrackedMppDataPacket() [tiflash+69093534]\n                \tdbms/src/Flash/Mpp/TrackedMppDataPacket.h:111\n       0x41e485b\tvoid std::__1::destroy_at<DB::TrackedMppDataPacket>(DB::TrackedMppDataPacket*) [tiflash+69093467]\n                \t/usr/local/bin/../include/c++/v1/__memory/construct_at.h:50\n       0x41e47f9\tvoid std::__1::allocator_traits<std::__1::allocator<DB::TrackedMppDataPacket> >::destroy<DB::TrackedMppDataPacket, void, void>(std::__1::allocator<DB::TrackedMppDataPacket>&, DB::TrackedMppDataPacket*) [tiflash+69093369]\n                \t/usr/local/bin/../include/c++/v1/__memory/allocator_traits.h:317\n       0x41e471d\tstd::__1::__shared_ptr_emplace<DB::TrackedMppDataPacket, std::__1::allocator<DB::TrackedMppDataPacket> >::__on_zero_shared() [tiflash+69093149]\n                \t/usr/local/bin/../include/c++/v1/__memory/shared_ptr.h:313\n       0x42adf3c\tstd::__1::__shared_count::__release_shared() [tiflash+69918524]\n                \t/usr/local/bin/../include/c++/v1/__memory/shared_ptr.h:177\n       0x42adef6\tstd::__1::__shared_weak_count::__release_shared() [tiflash+69918454]\n                \t/usr/local/bin/../include/c++/v1/__memory/shared_ptr.h:219\n       0xbd6a2b0\tstd::__1::shared_ptr<DB::TrackedMppDataPacket>::~shared_ptr() [tiflash+198615728]\n                \t/usr/local/bin/../include/c++/v1/__memory/shared_ptr.h:959\n       0xbfe8d4e\tDB::ReceivedMessage::~ReceivedMessage() [tiflash+201231694]\n                \tdbms/src/Flash/Mpp/ReceivedMessage.h:26\n       0xbfe8cfb\tvoid std::__1::destroy_at<DB::ReceivedMessage>(DB::ReceivedMessage*) [tiflash+201231611]\n                \t/usr/local/bin/../include/c++/v1/__memory/construct_at.h:50\n       0xbfe8c99\tvoid std::__1::allocator_traits<std::__1::allocator<DB::ReceivedMessage> >::destroy<DB::ReceivedMessage, void, void>(std::__1::allocator<DB::ReceivedMessage>&, DB::ReceivedMessage*) [tiflash+201231513]\n                \t/usr/local/bin/../include/c++/v1/__memory/allocator_traits.h:317\n       0xbfe8a7d\tstd::__1::__shared_ptr_emplace<DB::ReceivedMessage, std::__1::allocator<DB::ReceivedMessage> >::__on_zero_shared() [tiflash+201230973]\n                \t/usr/local/bin/../include/c++/v1/__memory/shared_ptr.h:313\n       0x42adf3c\tstd::__1::__shared_count::__release_shared() [tiflash+69918524]\n                \t/usr/local/bin/../include/c++/v1/__memory/shared_ptr.h:177\n       0x42adef6\tstd::__1::__shared_weak_count::__release_shared() [tiflash+69918454]\n                \t/usr/local/bin/../include/c++/v1/__memory/shared_ptr.h:219\n       0xbe99c60\tstd::__1::shared_ptr<DB::ReceivedMessage>::~shared_ptr() [tiflash+199859296]\n                \t/usr/local/bin/../include/c++/v1/__memory/shared_ptr.h:959\n       0xbfe0c95\tDB::LooseBoundedMPMCQueue<std::__1::shared_ptr<DB::ReceivedMessage> >::DataWithMemoryUsage::~DataWithMemoryUsage() [tiflash+201198741]\n                \tdbms/src/Common/LooseBoundedMPMCQueue.h:258\n       0xbfe0c6b\tvoid std::__1::destroy_at<DB::LooseBoundedMPMCQueue<std::__1::shared_ptr<DB::ReceivedMessage> >::DataWithMemoryUsage>(DB::LooseBoundedMPMCQueue<std::__1::shared_ptr<DB::ReceivedMessage> >::DataWithMemoryUsage*) [tiflash+201198699]\n                \t/usr/local/bin/../include/c++/v1/__memory/construct_at.h:50\n       0xbfe0b39\tvoid std::__1::allocator_traits<std::__1::allocator<DB::LooseBoundedMPMCQueue<std::__1::shared_ptr<DB::ReceivedMessage> >::DataWithMemoryUsage> >::destroy<DB::LooseBoundedMPMCQueue<std::__1::shared_ptr<DB::ReceivedMessage> >::DataWithMemoryUsage, void, void>(std::__1::allocator<DB::LooseBoundedMPMCQueue<std::__1::shared_ptr<DB::ReceivedMessage> >::DataWithMemoryUsage>&, DB::LooseBoundedMPMCQueue<std::__1::shared_ptr<DB::ReceivedMessage> >::DataWithMemoryUsage*) [tiflash+201198393]\n                \t/usr/local/bin/../include/c++/v1/__memory/allocator_traits.h:317\n       0xbfe09b4\tstd::__1::__deque_base<DB::LooseBoundedMPMCQueue<std::__1::shared_ptr<DB::ReceivedMessage> >::DataWithMemoryUsage, std::__1::allocator<DB::LooseBoundedMPMCQueue<std::__1::shared_ptr<DB::ReceivedMessage> >::DataWithMemoryUsage> >::clear() [tiflash+201198004]\n                \t/usr/local/bin/../include/c++/v1/deque:1253\n       0xbfe08d9\tstd::__1::__deque_base<DB::LooseBoundedMPMCQueue<std::__1::shared_ptr<DB::ReceivedMessage> >::DataWithMemoryUsage, std::__1::allocator<DB::LooseBoundedMPMCQueue<std::__1::shared_ptr<DB::ReceivedMessage> >::DataWithMemoryUsage> >::~__deque_base() [tiflash+201197785]\n                \t/usr/local/bin/../include/c++/v1/deque:1190\n       0xbfdf215\tstd::__1::deque<DB::LooseBoundedMPMCQueue<std::__1::shared_ptr<DB::ReceivedMessage> >::DataWithMemoryUsage, std::__1::allocator<DB::LooseBoundedMPMCQueue<std::__1::shared_ptr<DB::ReceivedMessage> >::DataWithMemoryUsage> >::~deque() [tiflash+201191957]\n                \t/usr/local/bin/../include/c++/v1/deque:1272\n       0xbfe0e62\tDB::LooseBoundedMPMCQueue<std::__1::shared_ptr<DB::ReceivedMessage> >::~LooseBoundedMPMCQueue() [tiflash+201199202]\n                \tdbms/src/Common/LooseBoundedMPMCQueue.h:31\n       0xbfe0deb\tvoid std::__1::destroy_at<DB::LooseBoundedMPMCQueue<std::__1::shared_ptr<DB::ReceivedMessage> > >(DB::LooseBoundedMPMCQueue<std::__1::shared_ptr<DB::ReceivedMessage> >*) [tiflash+201199083]\n                \t/usr/local/bin/../include/c++/v1/__memory/construct_at.h:50\n       0xbfe0d89\tvoid std::__1::allocator_traits<std::__1::allocator<DB::LooseBoundedMPMCQueue<std::__1::shared_ptr<DB::ReceivedMessage> > > >::destroy<DB::LooseBoundedMPMCQueue<std::__1::shared_ptr<DB::ReceivedMessage> >, void, void>(std::__1::allocator<DB::LooseBoundedMPMCQueue<std::__1::shared_ptr<DB::ReceivedMessage> > >&, DB::LooseBoundedMPMCQueue<std::__1::shared_ptr<DB::ReceivedMessage> >*) [tiflash+201198985]\n                \t/usr/local/bin/../include/c++/v1/__memory/allocator_traits.h:317\n       0xbfdda4d\tstd::__1::__shared_ptr_emplace<DB::LooseBoundedMPMCQueue<std::__1::shared_ptr<DB::ReceivedMessage> >, std::__1::allocator<DB::LooseBoundedMPMCQueue<std::__1::shared_ptr<DB::ReceivedMessage> > > >::__on_zero_shared() [tiflash+201185869]\n                \t/usr/local/bin/../include/c++/v1/__memory/shared_ptr.h:313\n       0x42adf3c\tstd::__1::__shared_count::__release_shared() [tiflash+69918524]\n                \t/usr/local/bin/../include/c++/v1/__memory/shared_ptr.h:177\n       0x42adef6\tstd::__1::__shared_weak_count::__release_shared() [tiflash+69918454]\n                \t/usr/local/bin/../include/c++/v1/__memory/shared_ptr.h:219\n       0x4200290\tstd::__1::shared_ptr<DB::LooseBoundedMPMCQueue<std::__1::shared_ptr<DB::ReceivedMessage> > >::~shared_ptr() [tiflash+69206672]\n                \t/usr/local/bin/../include/c++/v1/__memory/shared_ptr.h:959\n       0x4200222\tDB::ReceivedMessageQueue::~ReceivedMessageQueue() [tiflash+69206562]\n                \tdbms/src/Flash/Mpp/ReceivedMessageQueue.h:37\n       0x42001d3\tstd::__1::default_delete<DB::ReceivedMessageQueue>::operator()(DB::ReceivedMessageQueue*) const [tiflash+69206483]\n                \t/usr/local/bin/../include/c++/v1/__memory/unique_ptr.h:57\n       0x4200160\tstd::__1::unique_ptr<DB::ReceivedMessageQueue, std::__1::default_delete<DB::ReceivedMessageQueue> >::reset(DB::ReceivedMessageQueue*) [tiflash+69206368]\n                \t/usr/local/bin/../include/c++/v1/__memory/unique_ptr.h:318\n       0x41dffc7\tstd::__1::unique_ptr<DB::ReceivedMessageQueue, std::__1::default_delete<DB::ReceivedMessageQueue> >::~unique_ptr() [tiflash+69074887]\n                \t/usr/local/bin/../include/c++/v1/__memory/unique_ptr.h:272\n       0x42017f1\tDB::ExchangeReceiverBase<DB::GRPCReceiverContext>::~ExchangeReceiverBase() [tiflash+69212145]\n                \tdbms/src/Flash/Mpp/ExchangeReceiver.cpp:390\n       0xb1384c5\tDB::ExchangeReceiver::~ExchangeReceiver() [tiflash+185828549]\n                \tdbms/src/Flash/Mpp/ExchangeReceiver.h:251\n       0xb13849b\tvoid std::__1::destroy_at<DB::ExchangeReceiver>(DB::ExchangeReceiver*) [tiflash+185828507]\n                \t/usr/local/bin/../include/c++/v1/__memory/construct_at.h:50\n       0xb138439\tvoid std::__1::allocator_traits<std::__1::allocator<DB::ExchangeReceiver> >::destroy<DB::ExchangeReceiver, void, void>(std::__1::allocator<DB::ExchangeReceiver>&, DB::ExchangeReceiver*) [tiflash+185828409]\n                \t/usr/local/bin/../include/c++/v1/__memory/allocator_traits.h:317\n       0xb1376bd\tstd::__1::__shared_ptr_emplace<DB::ExchangeReceiver, std::__1::allocator<DB::ExchangeReceiver> >::__on_zero_shared() [tiflash+185824957]\n                \t/usr/local/bin/../include/c++/v1/__memory/shared_ptr.h:313\n       0x42adf3c\tstd::__1::__shared_count::__release_shared() [tiflash+69918524]\n                \t/usr/local/bin/../include/c++/v1/__memory/shared_ptr.h:177\n       0x42adef6\tstd::__1::__shared_weak_count::__release_shared() [tiflash+69918454]\n                \t/usr/local/bin/../include/c++/v1/__memory/shared_ptr.h:219\n       0xb129ae0\tstd::__1::shared_ptr<DB::ExchangeReceiver>::~shared_ptr() [tiflash+185768672]\n                \t/usr/local/bin/../include/c++/v1/__memory/shared_ptr.h:959\n       0xb139577\tDB::TiRemoteBlockInputStream<DB::ExchangeReceiver>::~TiRemoteBlockInputStream() [tiflash+185832823]\n                \tdbms/src/DataStreams/TiRemoteBlockInputStream.h:38\n       0xb13afdb\tvoid std::__1::destroy_at<DB::TiRemoteBlockInputStream<DB::ExchangeReceiver> >(DB::TiRemoteBlockInputStream<DB::ExchangeReceiver>*) [tiflash+185839579]\n                \t/usr/local/bin/../include/c++/v1/__memory/construct_at.h:50"] [source=BaseDaemon] [thread_id=1585]

2. What did you expect to see? (Required)
3. What did you see instead (Required)
4. What is your TiFlash version? (Required)
[2023/06/19 03:16:24.043 +08:00] [INFO] [client.go:514] ["Cluster version information"] [type=tikv] [version=7.2.0-alpha] [git_hash=0daa38c454c8d518a62f372f5fe679c1e858871e]
[2023/06/19 03:16:24.043 +08:00] [INFO] [client.go:514] ["Cluster version information"] [type=tidb] [version=7.2.0-alpha] [git_hash=5bd56cb5d5597e106a511007d42c93ee4fc20f50]
[2023/06/19 03:16:24.043 +08:00] [INFO] [client.go:514] ["Cluster version information"] [type=pd] [version=7.2.0-alpha] [git_hash=1c5ca17da988a71e7293a8ec2de3d5b13d841fa2]
[2023/06/19 03:16:24.043 +08:00] [INFO] [client.go:514] ["Cluster version information"] [type=tiflash] [version=7.2.0-alpha] [git_hash=7aafea8835af8f8c77f48fb197fec660eb9f850d]

Looks like it is related with https://github.com/pingcap/tiflash/pull/7644


Controllability of the snow effect

Hi,
I'm wondering how to control the level of the snow effect?

I'm wondering how to control the level of the snow effect

Can you reproduce the effect of snow? Using Colmap's Garden Data

I'm wondering how to control the level of the snow effect

Can you reproduce the effect of snow? Using Colmap's Garden Data

I used the Kitti scene, didn't try the Garden one. And i'm not really sure i produced the snow ball correctly because i felt like it was only stylized and not many snow accumulated on the object surface. What about you?

I'm wondering how to control the level of the snow effect

Can you reproduce the effect of snow? Using Colmap's Garden Data

I used the Kitti scene, didn't try the Garden one. And i'm not really sure i produced the snow ball correctly because i felt like it was only stylized and not many snow accumulated on the object surface. What about you?

@cici19850

used the Kitti scene, didn't try the Garden one. And i'm not really sure i produced the snow ball correctly because i felt like it was only stylized and not many snow accumulated on the object surface. What about you?

I used garden data but failed to reproduce the effect of snow,  I don't know why rendering everything black. What are the version numbers of CUDA and PyTorch Lightning that you have installed? I am using CUDA118 and PyTorch Lightning 1.9.5, and I am not sure if it is due to a version number issue that caused my rendering to fail

used the Kitti scene, didn't try the Garden one. And i'm not really sure i produced the snow ball correctly because i felt like it was only stylized and not many snow accumulated on the object surface. What about you?

I used garden data but failed to reproduce the effect of snow,  I don't know why rendering everything black. What are the version numbers of CUDA and PyTorch Lightning that you have installed? I am using CUDA118 and PyTorch Lightning 1.9.5, and I am not sure if it is due to a version number issue that caused my rendering to fail

I'm not really sure if it is the version problem. But my setting is align with the official setting :CUDA11.3 and PyTorch lightning 1.7.
Btw did you stylize it?


Cant run 'go mod init' as non-root-user in Go

VSCode Version:

Version: 1.41.1
Commit: 26076a4de974ead31f97692a0d32f90d735645c0
Date: 2019-12-18T15:04:31.999Z
Electron: 6.1.5
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Linux x64 4.19.99-1-MANJARO

Local OS Version:

Linux manjaro 4.19.99-1-MANJARO #1 SMP Mon Jan 27 16:36:28 UTC 2020 x86_64 GNU/Linux

Name of Dev Container Definition with Issue:

vscode-dev-containers/containers/go/.devcontainer/Dockerfile

Steps to Reproduce:

Set remoteUser as vscode.
Open vscode inside the go dev container.
Try to run go mod init in a non gopath folder.

Example command and error:
go mod init test.com/test/tmp

go: creating new go.mod: module test.com/test/tmp
go: failed to create cache directory /go/pkg/mod/cache: mkdir /go/pkg/mod: permission denied

I have noticed that the /go/pkg folder only has write permissions for root. I think this is the issue.

Should be resolved with your PR (#227)!


Overflow menu

https://github.com/IBM/carbon-components-builder/issues/46

@zvonimirfras please review and merge


Automated cherry pick of #4313: fix: 避免在域管理后台rules不可见

Cherry pick of #4313 on release/2.12.
#4313: fix: 避免在域管理后台rules不可见

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.12@2835fed). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.12   #4315   +/-   ##
==============================================
  Coverage                ?   6.86%
==============================================
  Files                   ?     501
  Lines                   ?   85116
  Branches                ?       0
==============================================
  Hits                    ?    5839
  Misses                  ?   78784
  Partials                ?     493

Flag
Coverage Δ

#aFlag
6.86% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/secgrouprules.go
4.45% <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 2835fed...9e4efab. Read the comment docs.

/lgtm

/approve


np.linalg.cond behaviour and test needs updating for np 1.15

As noted here https://github.com/conda-forge/numba-feedstock/pull/13#issuecomment-412308077
For a certain class of poorly conditioned matrices, overflow will occur if the condition number is computed via SVD, NumPy patched against this in v1.15 here, but the Numba impl and indeed tests for the Numba impl replicate the prior to 1.15 behaviour. This ticket is a reminder to fix this as part of accommodating NumPy 1.15.

Fixed in https://github.com/numba/numba/pull/3227, closing.


update log messages

Description

Release required?

[ ] No release
[x] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

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


Generate pdf from url

Now you can also generate a PDF from a URL.
pdf_path = PdfGenerator.generate "http://www.google.com"

Included a basic test as well.

Reading the code I was first glance not sure if https would work. Both http and https works just fine however.

@nivanson It's because I pattern match the url like this "http" <> url and then later create the full_url back with the url part. full_url  = "http#{url}".
So if the parameter was let's say "https://www.google.com", it would bind url to "s://www.google.com". And then later full_url will become "https://www.google.com" back.

Heloo @egze,
first of all, thanks a lot for your contribution. It's cool seeing this library being use.
I will not accept/merge this PR.

I do not want the dependency to Poison and its dependencies
Many users of this library already use some some of HTTP retrieval or even render their HTML on their own with one of the many libraries to do that out there. So adding this extra dependency is a cost for no benefit.

In production  code, one should split the generation/retrieval of your HTML source from PDF generation anyways as it's a different concern. HTTP can always fail and handling errors their should belong to some HTTP-handling code.
with {:ok, invoice} <- MyApp.Invoicing.Queries.get_by_id("foo-bar-id"),
     {:ok, html}    <- MyApp.Invoicing.Transformations.get_htmlfor(invoce),
     {:ok, pdf}     <- PdfGenerator.generate(html) do
{:ok, pdf}
end

or using some API wrapper
with {:ok, html} <- ExternalSystem.InvoiceAPI.get_invoice_html(id: "foo-bar-id"),
     {:ok, pdf}     <- PdfGenerator.generate(html) do
{:ok, pdf}
end

@gutschilla Thanks for your input.
But I have to disagree.

About poison - it is a dependency for fake_server, which is only used for testing. It is not needed at all for end users. If poison is really a problem - maybe we can think of some alternative way how to test it?

The benefit. 1 big problem when you render HTML to PDF - is how you resolve other assets (images and css). Just rendering a pdf from string forces you to have all the resources either inline or available on disc. If you are in control of the html output - sure, no problem. But if you are forced to convert a 3rd party url - this is where it gets difficult. Because web pages can be quite complex - I find it hard to believe, that someone wrote a library that prepares the whole package that they can feed to elixir-pdf-generator. Also wkhtmltopdf supports passing a url, so for a wrapper, it would be nice to support the original functionality.

Please reconsider. I think this something that elixir-pdf-generator do need.

@egze Thanks for your input and reflection on the topic.
You are right, in my use cases external CSS and imagery uses absolute URLs as the underlying framework makes it easy to do so. So I get your point and will reconsider. Thank you.
Please allow for another day for me to get through the sources.

I think it makes sense to keep api different for url and html.
Something like PdfGenerator.generate(html) and PdfGenerator.generate_from_url(url)

@nivanson @egze There's a new version 0.5.0 that that

support URLs via generate({url: url})
supports chrome-headless via generate(content, generator: :chrome)

See: https://github.com/gutschilla/elixir-pdf-generator/releases/tag/v0.5.0

Thanks a lot! This is great news!

Sure, thanks a lot or the input. It's very valuable.


Scan "client.exe" by default

Change scan() in Defaults.js to
function scan(name, sig) {
    if (sig == undefined) {
        sig = name;
        name = 'client.exe';
    }

So that the order of the parameters stays the same and the interface doesnt change.


Use native-tls stuff when making clients and requests.

Ran into this issue with http::send_files a few days ago, but found out that the problem was also in http::get_messages. I decided to just change all occurrences that I could find.

Thanks


Data to yml

I'm writing all the data from the original airports.csv file into individual .yml files so the site can use Middleman natively to read and write from the source data.
Another valuable thing will be the ability for better organized pull requests if anyone submits data improvements in the future.
Now all the airports will be in data/#{icao}.yml format. If an airport doesn't have an icao id it will be data/iata-#{iata}.yml. Airports that have neither are in data.incomplete as a reference for future improvements.

Actually... this was a bad idea. It's so slow it'll never load. You live. You learn. :(


Auto generate sleep times

Add default 20s-40s interval to the end.
Add between groups (if there are any).
Auto-generate? Maybe.

Don't add between groups. Bad idea.
Auto-generate only. Partially done - adds sleep times inside groups when it should be above the group start.

Now ends up in the right place. Threshold is 2 seconds hard coded!


Make it possible to colour image markers via marker-fill

low priority right now

This is torque, right?

yep!

Yep, low priority

Yeah I assumed. Just leaving it here for future updates.

This is already happening by setting image-filters: colorize() with just one color and full opacity, example:
marker-file: url(star.png);
image-filters: colorize(blue);
marker-fill-opacity: 1;


Tidb is recommended instead of SQLite, remove the dependency on CGO

No chance... Sqlite is battle tested, meddler doesn't support it, the migration lib doesn't support it.

Well then, the problem is closed.

@insionng we've considered tidb in the past and I would certainly like to remove the CGO dependency. I think it is definitely something we'd consider once it is more mature. Thanks!

@bradrydzewski Okay.


refactor: migrate history to TypeScript

Summary
Migrating history to TypeScript
Test plan
Run current tests

Hm... I renamed files in separate commit, but it still can't properly diff collections.ts


RabbitMQ does not allow specifying config file

Currently the only way to replace default RMQ config file is to manually copy the file to the mounted directory. If, however, the chart would allow mounting specified file as configmap (e.g. as specified here: https://github.com/kubernetes/kubernetes/issues/44815#issuecomment-297077509), it would be possible to use config map and all its goodies (e.g. value expansion).

If you use th rabbitmq-ha chart, it does allow you to create your own configmap:
https://github.com/kubernetes/charts/blob/master/stable/rabbitmq-ha/values.yaml#L114
Which could be used to inject definitions similar to this:
apiVersion: v1
kind: ConfigMap
metadata:
  name: my-release-rabbitmq-ha
data:
  enabled_plugins: |
    [rabbitmq_consistent_hash_exchange,rabbitmq_federation,rabbitmq_federation_management,rabbitmq_management,rabbitmq_mqtt,rabbitmq_peer_discovery_k8s,rabbitmq_shovel,rabbitmq_shovel_management,rabbitmq_stomp,rabbitmq_web_stomp,rabbitmq_delayed_message_exchange].
  rabbitmq.conf: |
    # ....
    management.load_definitions = /etc/rabbitmq/definitions.json
  definitions.json: |
    {
      "permissions": [],
      "users": [],
      "policies: []
    }

This don't actually works.
I get this error:
Error: release condohub failed: configmaps "condohub-rabbitmq-ha" already exists

/remove-lifecycle stale
If its supported, then it should at least be documented how to use it. At the moment that file merely has a spot for saying true or false for an existing configmap. Without documentation how to use this and, in an ideal world, an example of using it to specify a user, a vhost and some permissions for the user+vhost combination, this remains a major stumbling block for potential new users.

@techdragon, agreed.
@marcoskichel, you need to set existingConfigMap: true as well, so the chart doesn’t try to create one.

IMO this issue ought to be closed.


add stale yaml file

@masters3d @kytrinyx
Addresses issue 23
Adds the empty stale.yaml file to .github dir, in case that's something desired for the repo. If so, merge it, if not, can close.

That's a good question. My experience with the probot/stale integration so far has been that it's mostly useful in repositories with lots of issues/PRs and lots of activity, where things are more likely to fall between the cracks.
I'll leave it up to @masters3d to decide whether or not it's likely to be useful here.

Let's give it a try.


TCZ extension for the binary

[ ] describe how to create extension package
[ ] Add automated release of binary

$ mkdir -p ./tmp/bin
$ cp ./out/hvkvp ./tmp/bin
$ mksquashfs -no-xattrs ./tmp go-hvkvp.tcz


Create blank.yml

طلب سحب

ما هي مشكلتي كي يتم استخدام بيانتي أنا لم افهم شئ

Thank you very much And my files were received and received without any problem Thanks

Excuse me, sir Do you know the problem? Are you looking for knowledge of the withdrawal? Thank you very much


[Bug] WebFluxSkyWalkingTraceContext.traceId(exchange) 无效

Search before asking

[X] I had searched in the issues and found no similar issues.

Apache SkyWalking Component
Java Agent (apache/skywalking-java)
What happened
从这里获取的最新文档中

实际使用中String traceId = WebFluxSkyWalkingTraceContext.traceId(exchange);并无法获取到想要的内容，似乎文档有差异？
What you expected to happen
获取到TraceId。
How to reproduce
参考文档：
https://skywalking.apache.org/docs/skywalking-java/next/en/setup/service-agent/java-agent/application-toolkit-webflux/#fetch-trace-context-relative-ids
Anything else
No response
Are you willing to submit a pull request to fix on your own?

[ ] Yes I am willing to submit a pull request on my own!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

We use English to discuss on Github.
Close it.
And what you are facing just a discussion, not an issue. Use discussion to see who has experiences about your use cases.


While running alphafold2 : requests.exceptions.ReadTimeout: UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)

When I started running Alphafold2 in the server
Command:
nohup python3 docker/run_docker.py --fasta_paths=/data/hkumar1/software/alphafold/InputFASTA/6_CARS_ALK.fasta --max_template_date=2020-05-14 --data_dir=/data/hkumar1/software/AlphaFold2/DataBase/ --output_dir=/data/hkumar1/software/alphafold/OutputAlphafold &
Getting the following error (detail attached in image file).
requests.exceptions.ReadTimeout: UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60

)

This seems to be a docker issue related to resource contention on the server your instance is running on. Is there any way you can free more resources on the host?

Closing this issue now, feel free to reopen if this is still a problem.

Anyone find a solution, I am running into the same error.
My resource allocation I think is beyond what is required for the software, so I am confused on the real  #issue:

I have also tried to increase the timeout limit, up to 180 seconds, as suggested by other threads. But this has not worked either.


Protection against putting anchors within other anchors, thereby destroying the anchor

We have observed this thing while working:
<7bd6dbb9-4935-4051-b54b-a4c8c936c87b>quod primo ivit ad
domum Hugolini de Monte Chalvuli, Mutinensis
diocesis</7bd6dbb9-4935-4051-b54b-a4c8c936c87b>,<12eeaa22-3d01-4ab0-b27f-cdd030bfc85f> et ibi
receptatus fuit per dictum Hugolinum</12eeaa22-3d01-4ab0-b27f-cdd030bfc85f> et stetit octo diebus
vel circa. Interrogatus si dictus Hugolinus et domina Veçosa, uxor sua,
cognoverunt**<5ae19369-d163-420e-a0c1-d9db7<2171843b-a4e6-494e-adc3-2a44d0db06ee>f9462f8>**
</<17d324d7-1e42-473e-862f-4e9b2bb10220>2171843b-a4e6-494e-adc3-2a44d</17d324d7-1e42-473e-862f-4e9b2bb10220>0db06ee>eum
et</5ae19369-d163-420e-a0c1-d9db7f9462f8> sciverunt eum esse fugitivum dicti inquisitoris,
respondit et dixit quod sic.

I.e. some uuid anchors got destroyed by other anchors. We cannot totally exclude it was some mistyping in the still not very convenient full-text editor and then saving, but doubt it strongly - we think it is a misbehaviour of the application.

@davidzbiral Are you seeing these <> tags at all in annotator btw? I do not see them at all unless I export, which is currently the only way I have to check my work

@rljshaw We saw them, yes, in the Edit mode (instead of Highlight mode).

I see it now thanks

Partly fixed in recent updates - correct opening/closing tag placement. More updates coming.

Closing this issue, the main reason that caused this in the app logic should be sanitized in reworked algoithm. Feel free to reopen if persists.


Whats up with the windows build?

is the windows build dead?

The latest OpenCL for TensorFlow work now lives here https://github.com/codeplaysoftware/tensorflow It has not been tested with Windows.

Failed to load the native TensorFlow runtime
with missing DLL
i used pip install tf-nightly-gpu with python 3.7


Consumer latency grows with consumer count

Our application interacts with dozens of topics.  As we've been transitioning functionality bit-by-bit to using Confluent, we've noticed an unfortunate increase in consumer latency.
I was finally able to replicate the issue outside of our application.  The scenario is having multiple consumers but only sending messages to one of them (or a small subset).  When messages are round-robin'd to all present consumers this behavior does not occur.  Using KafkaJS running the same scenario, this behavior does not occur.
I'm hoping there is a configuration-driven solution to this problem, but I was unable to determine one on my own.
import {KafkaJS as Confluent, RdKafka} from "@confluentinc/kafka-javascript";
import {fail} from "assert";

const groupId = (t: number) => `test-confluent-group-${t}`;
const topic = (t: number) => `test-confluent-topic-${t}`;

describe("Consumer latency", () => {
  let kafka: Confluent.Kafka;
  let admin: Confluent.Admin;
  let producer: Confluent.Producer;
  let consumers: Confluent.Consumer[] = [];
  let consumersReady = new Set<number>();
  let messagesReceived: string[] = [];

  beforeEach(async () => {
    consumers = [];
    consumersReady.clear();

    kafka = new Confluent.Kafka({kafkaJS: {brokers: ["localhost:9092"]}});
    admin = kafka.admin();
    await admin.connect();
  });

  afterEach(async () => {
    const promises: Promise<void>[] = [];
    promises.push(admin.disconnect());
    promises.push(producer.disconnect());
    for (const consumer of consumers) {
      promises.push(consumer.disconnect());
    }
    await Promise.all(promises);
  });

  it("with 1 topic & consumer", async () => {
    await runTest(1, 16);
  });

  it("with 2 topics & consumers", async () => {
    await runTest(2, 16);
  });

  it("with 4 topics & consumers", async () => {
    await runTest(4, 16);
  });

  it("with 8 topics & consumers", async () => {
    await runTest(8, 16);
  });

  it("with 16 topics & consumers", async () => {
    await runTest(16, 16);
  });

  it("with 32 topics & consumers", async () => {
    await runTest(32, 16);
  });

  async function runTest(topicCount: number, messageCount: number) {
    // clear all groupIds to avoid contamination from previous runs
    const groupIds: string[] = [];
    for (let t = 0; t < topicCount; t++) {
      groupIds.push(groupId(t));
    }
    await admin.deleteGroups(groupIds);

    // ensure topics exist
    const topics: Confluent.ITopicConfig[] = [];
    for (let t = 0; t < topicCount; t++) {
      topics.push({topic: topic(t)});
    }
    await admin.createTopics({topics});

    let promises: Promise<any>[] = [];
    for (let t = 0; t < topicCount; t++) {
      promises.push(setupConsumer(t, messageCount));
    }
    await Promise.all(promises);

    producer = kafka.producer({"linger.ms": 0});
    await producer.connect();

    await until(() => consumersReady.size === topicCount);

    messagesReceived = [];

    promises = [];
    for (let m = 0; m < messageCount; m++) {
      const theTopic = topic(0);
      const headers = {created: new Date().toISOString()};
      const value = `Confluent Message ${m + 1}`;
      console.log(`[Sending] @ ${theTopic}: ${value}`);
      promises.push(producer.send({topic: theTopic, messages: [{headers, value}]}));
    }
    await Promise.all(promises);

    await until(() => messagesReceived.length === messageCount);
  }

  async function setupConsumer(t: number, messageCount: number) {
    let ready = false;
    const consumer = kafka.consumer({
      kafkaJS: {groupId: groupId(t), maxWaitTimeInMs: 100},
      rebalance_cb: (err: any, assignment: any, consumer: any) => {
        if (err.code !== RdKafka.CODES.ERRORS.ERR__ASSIGN_PARTITIONS) return;
        if (!ready) {
          ready = true;
          consumersReady.add(t);
        }
      }
    });
    await consumer.connect();
    await consumer.subscribe({topic: topic(t)});
    await consumer.run({
      eachMessage: async ({message}) => {
        const value = message.value?.toString() ?? "";
        messagesReceived.push(value);
        const delay = Date.now() - new Date(message.headers?.created as string).getTime();
        console.log(`[Received] @ ${topic(t)} (#${messagesReceived.length} of ${messageCount}): ${value} (${delay}ms)`);
      }
    });
    consumers.push(consumer);
  }

  async function until(condition: () => boolean) {
    const timeout = 60000;
    const finish = Date.now() + timeout;
    while (Date.now() <= finish) {
      const result = await condition();
      if (result) return;
      await new Promise(resolve => setTimeout(resolve, 50));
    }
    fail(`Failed within ${timeout!}ms`);
  }
});

With 1 topic results are consistent from the first to last message.
[Received] @ test-confluent-topic-0 (#1 of 16): Confluent Message 1 (955ms)
...
[Received] @ test-confluent-topic-0 (#16 of 16): Confluent Message 16 (957ms)

With 2 and 4 topics, the results are similar.
As  we jump to 8 topics, the issue shows itself.  The 16th message takes an additional 4 seconds to show up in the consumer.
[Received] @ test-confluent-topic-0 (#1 of 16): Confluent Message 1 (1006ms)
...
[Received] @ test-confluent-topic-0 (#16 of 16): Confluent Message 16 (5019ms)

16 topics and now we have an additional 16 seconds!
[Received] @ test-confluent-topic-0 (#1 of 16): Confluent Message 1 (1004ms)
...
[Received] @ test-confluent-topic-0 (#16 of 16): Confluent Message 16 (17062ms)

32 topics, the test never completed its setup and was left in a hung state.
Please help us find a path forward.

Hey @apeloquin-agilysys , thanks for the great report. I've been able to reproduce this - I wanted to confirm one thing, in the actual production use case, are the consumers all running in the same node process just like this example?
More context:
I don't quite have a complete answer yet but changing one of the internally (not yet exposed via the public interface) configurable parameters fixes the problem.
It seems that with the current settings, the event loop spends most of its time idling when there are consumers trying to fetch messages without availability of messages on their topics and this blocks the actual useful consumers. This isn't quite solved yet, since we need to work through the repercussions of changing the parameter (it might affect the throughput), and check if there is a better way.

Hi @milindl.  Thanks for the response.

I wanted to confirm one thing, in the actual production use case, are the consumers all running in the same node process just like this example?

Yes, that is the case.

For a workaround based on environment variables, you can set UV_THREADPOOL_SIZE to a number greater than or equal to the number of consumers.

I will try this out.

we would ideally wish for this to be opaque to the user, or be able to work with just the default number of threads.

I agree!  With KafkaJS we were easily able to establish 100+ consumers (in tests) with the default configuration and negligible latency, would hope for similar flexibility with Confluent.

Hi @milindl.  I must be missing something.  Setting the UV_THREADPOOL_SIZE environment variable to 32 makes no difference in the performance of this test for me.
I added the following to the beforeEach method to confirm the value:
console.log(`UV_THREADPOOL_SIZE=${process.env.UV_THREADPOOL_SIZE}`);

Results from 16 topic test:
UV_THREADPOOL_SIZE=32
...
[Received] @ test-confluent-topic-0 (#1 of 16): Confluent Message 1 (1004ms)
...
[Received] @ test-confluent-topic-0 (#16 of 16): Confluent Message 16 (18053ms)

Thanks @apeloquin-agilysys . I'm running my test like this (I stripped out the type annotations). I'm on node v22 and on a WSL system with 8 logical cpus.
export UV_THREADPOOL_SIZE=32
node ../path/to/mocha.js --timeout 120000 filename.js

I'm getting all the consumers to pretty much finish < 1000 ms in all the cases (and when I unset the env variable, I get similar results to you).
Perhaps it's related to OS or node version, but that won't really help if that's the case. Given what worked for me and what my perf profiles looked like, I was pretty certain of the root cause but I'll think if it can be something else, too.
Would it be possible for you to take a performance profile of both the cases (with both values of UV_THREADPOOL_SIZE)?
For taking the profile:
While running only the 16 or 32 consumer one (whichever finishes on your system), I added this code:
    console.profile();
    await until(() => messagesReceived.length === messageCount);
    console.profileEnd();

I then used vscode to attach to the test process to grab a profile. (You might need to add a sleep somewhere before the tests start to attach the process). I think you can also take a similar profile with chrome if you don't use vscode.
(This doesn't capture 100% of the consume duration but it gets most of it, we're only really looking for a representative sample)

Hi @milindl.  The reason it wasn't working for me is the UV_THREADPOOL_SIZE must exist in the environment before node is launched.  Setting the environment variable from within the node app, or via dotenv/config (which we use for managing environment variables required by the app) makes the value available to node but not apparently not librdkafka.  (Is it possible to feed the node process.env to librdkafka?)
With it set, the 32 consumer test messages are all at ~1s.
That's the good news.  The bad news is that this is an unwieldy workaround since this setting must be effectively managed outside the application.  Looking forward to the real solution!

@apeloquin-agilysys Thanks - while I agree the workaround isn't the best, the fact that it works for you too is some strong evidence that the root cause we were thinking of it correct. That's a relief.
I'm not quite certain why it doesn't work when you set it from within node. Maybe by that time, libuv has already initialized its threadpool (libuv is one of the components used by node itself to run their event loop). But it's just a guess.

Closing with #135  being released. Let me know if it persists.


How to setup istio to send metrics to skywalking

Please answer these questions before submitting your issue.

Why do you submit this issue?
[X ] Question or discussion
[ ] Bug
[ ] Requirement
[ ] Feature or performance improvement

Question

What do you want to know?
How to setup istio to send metrics to skywalking? I found this link but there is no information here: https://github.com/apache/skywalking/blob/master/docs/en/setup/istio/README.md this links to https://github.com/apache/skywalking-kubernetes#setup-istio-to-send-metrics-to-oap which also has no information.

Bug

Which version of SkyWalking, OS and JRE?

Which company or project?

What happen?
If possible, provide a way for reproducing the error. e.g. demo application, component version.

Requirement or improvement

Please describe about your requirements or improvement suggestions.

Yes. I just bring it by through #3376.


nesting of string literals with the same quote type inside f-string

before
email = factory.LazyAttribute(lambda obj: f"info@{obj.name.lower().replace(' ', '')}.de")

after
email = factory.LazyAttribute(lambda obj: f"info@{obj.name.lower().replace(" ", "")}.de")

issue
(tooltip from PyCharm)

Python version 3.11 does not allow nesting of string literals with the same quote type inside f-strings

solution
email = factory.LazyAttribute(lambda obj: f'info@{obj.name.lower().replace(" ", "")}.de')

ruff 0.2.2 with preview enabled
[tool.ruff]
line-length = 100
output-format = "grouped"
extend-exclude = ["apps/*/migrations/*", "static", "staticfilles", "templates"]
target-version = "py312"
fix = true

[tool.ruff.format]
preview = true
docstring-code-format = true

[tool.ruff.lint]
preview = true
ignore = [
    "E501",
    "S101",
    "S106",
    "RUF012",
    "PT027",
    "ISC001",
    "FBT001",
    "FBT002",
    "FBT003",
    "PLC0415"
]
select = [
    "F",     # Pyflakes
    "E",     # pycodestyle errors
    "W",     # pycodestyle warnings
    "C90",   # mccabe
    "I",     # isort"
    "N",     # pep8-naming
    "UP",    # pyupgrade
    "PL",    # pylint
    "PERF",  # perflint
    "S",     # flake8-bandit
    "FBT",   # flake8-boolean-trap
    "B",     # flake8-bugbear
    "DJ",    # flake8-django
    "ICN",   # flake8-import-conventions
    "ASYNC", # flake8-async
    "C4",    # flake8-comprehensions
    "Q",     # flake8-quotes
    "RET",   # flake8-return
    "SIM",   # flake8-simplify
    "TID",   # flake8-tidy-imports
    "TCH",   # flake8-type-checking
    "PTH",   # flake8-use-pathlib
    "INT",   # flake8-gettext
    "SLOT",  # flake8-slots
    "SLF",   # flake8-self
    "RSE",   # flake8-raise
    "PYI",   # flake8-pyi"
    "PIE",   # flake8-pie"
    "ISC",   # flake8-implicit-str-concat
    "A",     # flake8-builtins
    "COM",   # flake8-commas
    "T10",   # flake8-debugger
    "YTT",   # flake8-2020
    "G",     # flake8-logging-format
    "ERA",   # eradicate
    "RUF",   # ruff
    "FLY",   # flynt
    "FURB",  # refurb
]

Is this after you ran ruff format or after you applied a fix? Do you remember the name of the rule that you applied?

Yes, it must be rust format.
If I remove preview = true from format, it doesn't replace the single quotes

Yeah, that's expected because you configured target-version = "py312", which allows the formatter to re-use the same quotes. However, the style is still in preview and we're open to change how the formatter picks quotes.
What are your reasons for preferring alternating quotes? What's your preferred formatting if the f-string has one more level of nesting?

What are your reasons for preferring alternating quotes? What's your preferred formatting if the f-string has one more level of nesting?

I prefer double quotes and I try to avoid nesting f-strings. You are right that with Python 3.12 the f-string behavior has changed. I was just a bit confused at the beginning because PyCharm marked it.
Even though we define Python 3.12 as required, the alternating style would also allow Python 3.11 to work properly (better backward compatibility)

Even though we define Python 3.12 as required, the alternating style would also allow Python 3.11 to work properly (better backward compatibility)

That's true. I'm leaning towards leaving it as is and allow users to configure whether they want backwards compatibility or not by setting the target-version.


Avoid infinite loop in GetRandomEvenPort

Thanks @jech !
Would you like me to tag a new version?

Would you like me to tag a new version?

No need, it's just a minor cleanup that i did while I get to grok the TURN code.  I don't think the infinite loop can actually trigger on a Linux kernel.


Update wifi script/executable to use includes and modules

Once #2 is done, update wifi to use it.

Once #10 is done, update wifi to use it.


[ BUG ] Unable to run apps/showcase on Android emulator44

Describe the bug
Unable to run the showcase app on android emulator
To Reproduce
Steps to reproduce the behavior:

Start the  apps/showcase with p android
See error

Expected behavior
Should be able to run the demo apps on Android emulators
Screenshots

Platform (please complete the following information):

Type: Android emulator
OS: Android

Additional context
Add any other context about the problem here.

@atanaskanchev Are you still having this issue?
If you did not use pnpm, please you follow the instructions found here: https://github.com/mrzachnugent/react-native-reusables/issues/97#issuecomment-1983505171 and let me know if that works.

@mrzachnugent unfortunately yes. I've updated the emulator to the latest Pixel_8_Pro_API_34 but still get the same error

@atanaskanchev  I was not able to reproduce your error.
I recently updated some libraries. Can you pull the latest version, delete your node_modules, pnpm i and try again.

Closing due to inactivity


[Enum Request] Table 311 and 312  Field "Default Posting Date"

Table 311 "Sales & Receivables Setup" Field "Default Posting Date"
Table 312 "Purchases & Payables Setup" Field "Default Posting Date"
We don't require additional publishers to make additional options work.
Many thanks.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Translate most of the not-translated text in it.json

Lots of translation was needed so I wrote most of them, still needs some more tho, there are a lot of blank spaces.

Translations for BD are done through POEditor: https://poeditor.com/join/project?hash=nRljcnV0ET

Where is this wrote? i can't find it in the readme/contributing.md

https://github.com/BetterDiscord/BetterDiscord/blob/main/CONTRIBUTING.md#translations


WIP load user supplied plugins

Closes https://github.com/chris48s/v8r/issues/481
Closes https://github.com/chris48s/v8r/issues/483
Closes https://github.com/chris48s/v8r/issues/488

OK. I think this is basically done.
Next steps are:

https://github.com/chris48s/v8r/pull/487/commits/4431f7310afdfb484754acf0ca7ec8bb5b58fc4e implements the changes from https://github.com/chris48s/v8r/issues/488

Are you definitely 100% happy with the terminology now? Was the previous terminology actually better? Is there a secret third option?
Have you accounted for this in 100% of the places? Is there anything else that needs to change?
Once you push this release, this becomes public interface so any future changes are breaking
Naming things is hard :sob:

Another round of self-review. Have another good look over all this with fresh eyes

Then I think you are good to :rocket:

OK. I am FINALLY happy with the plugin interface. It is:
Input:

registerInputFileParsers()
parseInputFile(contents, fileLocation, parser)

Output:

registerOutputFormats()
getSingleResultLogMessage(result, fileLocation, format)
getAllResultsLogMessage(results, format)

This has been such a vivid exercise in "naming things is hard"


Made changes to fix issue with Multi model serving when deployed as raw deployment

What this PR does / why we need it:
Raw deployment mode in kserve does not require knative to be installed. However, the environment variables are set from queue proxy. Since  knative is not present, mms agent throws error for missing fields.
Made changes to get readiness probe from pod spec and use it as env to agent
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #1857
Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

NONE

Thanks @andyi2it !
/lgtm
/approve


Starlight overrides the defaultNS type definition of i18next so it conflicts with other i18next type definitions.

What version of starlight are you using?
0.30.0
What version of astro are you using?
5.1.1
What package manager are you using?
pnpm
What operating system are you using?
Mac
What browser are you using?
Chrome
Describe the Bug
I was integrating i18next into my Astro site with Starlight and found that the TypeScript compiler will force the defaultNS field for any i18next instance to be 'starlight', which will make the t function type errors if the keys don't match.
Link to Minimal Reproducible Example
https://stackblitz.com/edit/github-ytqftcmh?file=src%2Fpages%2Ftest.astro
Participation

[X] I am willing to submit a pull request for this issue.

Seems like stackblitz doesn't have type checking, but this is what I have on my IDE:

the T function's Namespace field is forced to be 'starlight'


Fixed missing closing b-tag in docs

Half of the docs screamed at us in boldface due to this misspelled tag.

Fixed in 10b7df9f95ac883d89b184048a13613a7808a0b3


[core] Fix extra GitHub Action permission

This PR adds explicit permissions section to workflows. This is a security best practice because by default workflows run with extended set of permissions (except from on: pull_request from external forks). By specifying any permission explicitly all others are set to none. By using the principle of least privilege the damage a compromised workflow can do (because of an injection or compromised third party tool or action) is restricted.
It is recommended to have most strict permissions on the top level and grant write permissions on job level case by case.

@sashashura Thanks for opening this PR. I wasn't aware that you had opened this when I worked on #34769. I have rebased taking the fix that you had identified.

but I would keep the top level permissions: {}.

What does this do? Does it remove the content and metadata read access?


Cannot open more than one tab of code simultaneously

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

VS Code Version: 1.62.0
b3318bc0524af3d74034b8bb8a64df0ccf35549a
arm64
OS Version:
ProductName:	macOS
ProductVersion:	11.6
BuildVersion:	20G165

Steps to Reproduce:

Open VS Code
On side bar, click to open a file and edit the file (the tab name goes from italic to normal).
Click another file on the sidebar to open, it should open in another tab but it doesn't.
It also happens with any other kind of tab, not only code.  I didn't know about the Tab Visibility toggle... That solved it for me. Thanks!


feature_request(enhancement): skip steps

1. Summary
It would be nice, if would be possible skip some steps of appveyor.yml file.
2. Argumentation
If user works on usual working PC:
user don't need steps init and install. User already all initialize and install. These steps take a lot of user time for big projects.
3. Example of expected behavior

localappveyor.yml

skip:
- init
- install

User run:
LocalAppVeyor build --job 0 --skip

init and install steps will skip; init and install scripts will not run.
4. Examples on other apps
wwtd — Travis CI local builds runner — can skip install step.
Thanks.

Replying a bit out of time. Sorry about that.
This is a really good idea and it makes total sense.
I just added the ability to skip steps through the command line. E.g.:
localappveyor build --job 0 --skip init --skip install

I know it's not exactly what you requested for tho. I like the idea of having a localappveyor.yml but I want to give it a bit more thought, in particular about its format and what it's exactly its purpose when working together with the command line options.
Will leave this open in the meantime.
Tks for your input and new ideas!


Explore producing an updated IUCn

Can we, given the current IUCn list, and an update of the species in it on our demo, regularly produce an updated list where we move species based on what we learn about them? Perhaps we can identify certain statements that we can take as meaning a species is no longer endangered? Or has become endangered? Perhaps @Blahah or @rossmounce can provide input here.

We could combine regex and species in same sentence. Regex would be words such as endangered vulnerable most concern etc
Sent from my iPhone
On 21 Oct 2015, at 10:23, markmacgillivray<EMAIL_ADDRESS>wrote:

Can we, given the current IUCn list, and an update of the species in it on our demo, regularly produce an updated list where we move species based on what we learn about them? Perhaps we can identify certain statements that we can take as meaning a species is no longer endangered? Or has become endangered? Perhaps @Blahah or @rossmounce can provide input here.
—
Reply to this email directly or view it on GitHub.

I like the basic idea. IUCN classifications are quite involved and usually require a panel of experts to set or change the status. We could do something like, given the existing status and the data we have mined, indicate whether the species seems to be improving, declining, or being maintained relative to when it was last assessed? A classification like that avoids treading on the toes of the existing experts, but provides value beyond the simple facts.

This sounds good. I think we only need the species plugin, not regex - once
we have the species I can search for the ones with interesting words in
their pre and post strings. From this we could provide a heat map of
research activity around the species we can match on the iucn red list.
Then consider what further statements we can say about them, in support of
the experts.
On 21 Oct 2015 16:51, "Richard Smith-Unna"<EMAIL_ADDRESS>wrote:

I like the basic idea. IUCN classifications are quite involved and usually
require a panel of experts to set or change the status. We could do
something like, given the existing status and the data we have mined,
indicate whether the species seems to be improving, declining, or being
maintained relative to when it was last assessed? A classification like
that avoids treading on the toes of the existing experts, but provides
value beyond the simple facts.
—
Reply to this email directly or view it on GitHub
https://github.com/ContentMine/canary/issues/8#issuecomment-149940451.


UI changed #170

[x] I am making a proper pull request, not a spam.
[x] I've checked the issue list before deciding what to submit.

Related Issues or Pull Requests
#170

@nilisha-jais pls review my pr.

Looks great! Thank you :)


Reorganize version header generation code

This is now desirable for both REST and gRPC APIs, so it's in the
Google.Api.Gax package, and is renamed to VersionHeaderBuilder as
it's not building a User-Agent header.
(Most of the changes are just renames.)

Right - I've now done a search for "gent" to make sure it doesn't occur anywhere we don't want it :)


Get next available IP CLI

I have the PowerShell Module installed, but dont know how to use it.
How would a powershell command looks like? If I want to create a invoke restmethod?
do you have an example? and what is the api url?
thanks

please check readme.md first
获取 Outlook for Androidhttps://aka.ms/ghei36

From: sudo77<EMAIL_ADDRESS>Sent: Thursday, November 7, 2019 2:06:43 AM
To: yoke88/PSPHPIPAM<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [yoke88/PSPHPIPAM] Get next available IP CLI (#16)
I have the PowerShell Module installed, but dont know how to use it.
How would a powershell command looks like? If I want to create a invoke restmethod?
do you have an example? and what is the api url?
thanks
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/yoke88/PSPHPIPAM/issues/16?email_source=notifications&email_token=AAYAD4QGI7CFTNFE7W2M7XDQSMBTHA5CNFSM4JJZOJB2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HXJ2PTQ, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAYAD4S3TV6WLDDKMB3CKPTQSMBTHANCNFSM4JJZOJBQ.


Data race in pkg/collectsub/datasource/csubsource

Describe the bug
There is a data race in pkg/collectsub/datasource/csubsource as seen in the failing unit tests of #1333.
To Reproduce
Upgrade to go 1.21 and run make test.
GUAC version
The CI uses the latest commit, and the bug can be reproduced with the same.
Additional context
Although the data race is not detected by make test with go version 1.19, it can still be reproduced with 1.19 by running the package tests manually: run go test -race -count=2 in the directorypkg/collectsub/datasource/csubsource.

good catch @mdeicas


MultiSelectComboBox Karibu 1.3.21

Hello Martin,
Support for MultiSelectComboBox(Since Karibu-Testing 1.3.21)
Should be available.
But yet despite using version <karibu.version>1.3.23</karibu.version>
I cannot find that static methode.
Could you please check?

Hi, according to https://github.com/mvysny/karibu-testing/tree/master/karibu-testing-v10#support-for-multiselectcombobox you need to pull in the karibu-testing-v23 dependency. Have you tried that please?

This should be ok, right?

Or do you mean this?

Should I switch to this?

Then this dependency is missing:

Now I understand this comment "Make sure to depend on karibu-testing-v23 to gain access to these functions."

And there is even another comment "For Vaadin 23, use karibu-testing-v23 instead (starting with Karibu-Testing 1.3.16)."
Ok, I thought just <karibu.version>1.3.23</karibu.version> would be enough to configure everything.
So the question then is how to use karibu-testing-v23 with spring?

Hi, you're right, the documentation should have been clearer. I've improved the readme and added more information here: https://github.com/mvysny/karibu-testing/tree/master/karibu-testing-v10#using-karibu-testing-with-spring
Please let me know whether it makes sense. In short, if you need both Vaadin 23 integration and Spring integration, simply depend on both karibu-testing-v10-spring and karibu-testing-v23 Maven modules.

Hello Martin,
now it makes sense and works.
Thanks alot!


Update README.md for better readability

Signed-off-by: Chinu Anand<EMAIL_ADDRESS>Notes for Reviewers
This PR fixes #6777
All the table alignment and image size issues are solved in this.
The only problem left is with the Meshery community section's paragraph where there are 3 components: the community icon, a paragraph and a slack icon, the property "display: flex" is working fine in other markdown editors but in GitHub, it's not rendering it correctly and overriding internally with "display: inline", I think its the issue with GitHub as 5 other markdown editors can't be wrong.
Signed commits

[x] Yes, I signed my commits.

Right: GitHub Markdown strips many HTML and CSS tags, intentionally not supporting them.

Yeah sure @eeshaanSA , I mainly focused on improving the readability issue in the doc.

I commend you use of English and understanding of markdown syntax. Looks good to me

This is no small thing either. We all could use a composition 101 refresher.

@UtkarshMishra12 @Chadha93  we have a broken link to the Meshery Project Overview deck that one of our community members deleted.


Allow multi Google Search Console verification codes in config/templates

See what was done for Besu
and update all sites mkdocs.yml

Will not be required.
We will either :

have the doc ecosystem migrated to our own hosting, so we will be able to define the redirect as we want
be able to use the correct 301 redirect with cloudflare.
create a new property


linter-spell: Dictionary request failed

Call to hunspell failed with a code of null.
Hi, It seems that the spell checker can not be found, how could I solve this problem?

Try putting the full path to hunspell into the settings page.

Can you run hunspell from the command line and show the output?

i have the same, after reading and trying arround im now asking what to do next.
I have done these steps:

downloaded this pack and copied the .dat, .aff and .dic to ~/Library/Spelling/ where i also renamed them to only de_CH.dat ..
set the path with method nr. 2 from this source to:  /etc/paths.d/hunspell : /usr/local/bin/hunspell.
$ hunspell -D shows now a long list of paths but seams to find them as it says:

LOADED DICTIONARY:
/Users/novski/Library/Spelling/de_CH.aff
/Users/novski/Library/Spelling/de_CH.dic
Hunspell 1.6.2

but atom still shows the same error.

I'm having similar issues. ;(


Question: Ability to get Authorization_Code via a direct api call.

I probably committed heresy against the OIDC Spec, but whatever.
I modified IdentityServer4 directly to achieve the ability to get an authorization_code without going through a UI login/consent flow.
Authorize2 API
Note the access_token here works against the user_info api.
https://localhost:44312/connect/authorize2
Content-Type:application/x-www-form-urlencoded
Authorization:Bearer { access_token}

scope:offline_access
client_id:resource-owner-client
client_secret:secret
beneficiary_client_id:resource-owner-client_2
redirect_uri:https://blah
response_type:code
prompt:none

Produces
{
    "code": "7073566239a4218154c4ecfc2be89e6ebd674028e6ca5a3a55b9792772b0b84d"
}

I then can make an ordinary token call with the code
Retrieve the tokens
https://localhost:44312/connect/token
Content-Type:application/x-www-form-urlencoded

grant_type:authorization_code
client_id:resource-owner-client
client_secret:secret
code:a4c3d55860266d204265f0661de4d34282726805060830bb1481720ca9900bef
redirect_uri:https://blah

Produces
{
    "access_token": "eyJhbGciOiJSUzI1NiIsImtpZCI6Ijc4OGRhZjMxYmRjYWUwMzE1MWUwYzRkMWQ1MDNjOTU0IiwidHlwIjoiSldUIn0.eyJuYmYiOjE1MjQ0MzE2NjksImV4cCI6MTUyNDQzNTI2OSwiaXNzIjoiaHR0cHM6Ly9sb2NhbGhvc3Q6NDQzMTIiLCJhdWQiOiJodHRwczovL2xvY2FsaG9zdDo0NDMxMi9yZXNvdXJjZXMiLCJjbGllbnRfaWQiOiJyZXNvdXJjZS1vd25lci1jbGllbnQiLCJzdWIiOiJyYXQiLCJhdXRoX3RpbWUiOjE1MjQ0MzEyNjQsImlkcCI6ImxvY2FsIiwic2NvcGUiOlsib2ZmbGluZV9hY2Nlc3MiXSwiYW1yIjpbInB3ZCJdfQ.iMHN-xTuaAm8PBLARYJpkpuu_oy1a5eVBP6xSZlIdFGFOfLkJ_HvGjywZcSagzrPgYeQSN_pPSzf2QwZLg6wFwoZkvsaW-qD9ebiqZZqSTGTYxGGafapYR8Vn_VIIfC48va1bkwlo5F04UAw6uBPKI5Bq3_NQuklBgWsUveHAfkOt0A8OvPrgvfS870n7CZ58u31EvdkHlF1cz2_u4UcdoT8MvwZUXVA5VhFUW3e2sZocVQqUuoua8W7u9p6muKufC5zJ00vzwg-LPYooIxEc0ouFVFfRguMCdLrDY_3lrDTe8B8iE48F5zvVqSkjmH6H-_5s8MV_8f39TVsTLuUYQ",
    "expires_in": 3600,
    "token_type": "Bearer",
    "refresh_token": "f4705f92e510659cdb777b70d8b806d982015119f8f18e7f4a718b27c3b4fb95"
}

So here is the questions:
I introduced a new custom/non-spec endpoint to IdentityServer4 which required access to a handful of internal classes.

Would there be a better way to do this than getting access to internal class you haven't opened up to be publicly consumed?
Would you be open to exploring opening up some of these classes so I can do this without forking IdentityServer4?
Would you be open to letting endpoints to registered so they are part of your endpoint router?

Stuff I need direct access to;
AuthorizeResult as I needed to typecast from IEndpointResult, so I could get the internal Response.
AuthorizeEndpointBase as my Endpoint leveraged some helpers in there to produce the authorization_code.
internal class Authorize2Endpoint : AuthorizeEndpointBase
{
}

Why not use an extension grant? That's what it's designed for.

Ok then, I will get back to you with that implementation's result.

Extension Grants rock, and worked as expect.  I still have an ask to have a context object that is passed from IExtentionGrant all the way to IProfileService.  I have another issue about that, but we can close this.  Thanks.


Ordered List (ol) is missing styling

Bitters &%default-ol fails to take the "type" attribute into consideration.
Ordered list have an attribute called "type", which controls the bullet point style, i.e. roman numerals, letters, etc..., see more http://www.w3schools.com/cssref/pr_list-style-type.asp
&%default-ol needs to have something along these lines:
&%default-ol {
    list-style-type: decimal;
    margin-bottom: $small-spacing;
    padding-left: $base-spacing;
    &[type=a] {
      list-style-type: lower-alpha;
    }
    &[type=A] {
      list-style-type: upper-alpha;
    }
    &[type=i] {
      list-style-type: lower-roman;
    }
    &[type=I] {
      list-style-type: upper-roman;
    }
}

There is only one issue with the proposed solution... Attribute selectors are not case sensitive, so
 will be treated as
. See http://stackoverflow.com/questions/27104096
Maybe instead add more extenders, such as:
&%default-ol,
&%default-ol-1 {
    list-style-type: decimal;
    margin-bottom: $small-spacing;
    padding-left: $base-spacing;
}

&%default-ol-a {
    list-style-type: lower-alpha;
    margin-bottom: $small-spacing;
    padding-left: $base-spacing;
}

&%default-ol-A {
    list-style-type: upper-alpha;
    margin-bottom: $small-spacing;
    padding-left: $base-spacing;
}

&%default-ol-i {
    list-style-type: lower-roman;
    margin-bottom: $small-spacing;
    padding-left: $base-spacing;
}

&%default-ol-I {
    list-style-type: upper-roman;
    margin-bottom: $small-spacing;
    padding-left: $base-spacing;
}

@drtimofey Is there a particular reason you’re using these attributes rather than styling via CSS’s list-style-type?
MDN notes:

Unless the value of the list number matters (e.g. in legal or technical documents where items are to be referenced by their number/letter), the CSS list-style-type property should be used instead.

I think for the purpose of Bitters, we would always recommend—and most commonly use—using CSS to style, rather than use these HTML attributes.

@tysongach, you're right! I'm closing the issue!


sqlite3.OperationalError: no such table: processes

we are getting back to https://github.com/ReproNim/reproman development where we used reprozip. Unfortunately one test started to fail with cryptic error which I hoped you might have an immediate clue about to guide us from the dark corner:
❯ REPROMAN_TESTS_SSH=1 python -m pytest -s -v -k 'test_trace_local' --tb=short --integration -v -v --pdb reproman
================================== test session starts ===================================
platform linux -- Python 3.10.7, pytest-7.2.0, pluggy-1.0.0 -- /home/yoh/proj/repronim/reproman-master/venvs/dev3/bin/python
cachedir: .pytest_cache
rootdir: /home/yoh/proj/repronim/reproman-master
collected 431 items / 430 deselected / 1 selected

reproman/interface/tests/test_execute.py::test_trace_local 2022-12-15 17:46:16,881 [INFO   ] Downloading tracer...
2022-12-15 17:46:17,868 [INFO   ] Tracer downloaded to /home/yoh/.tmp/pytest-of-yoh/pytest-349/local0/tracers/d8561c1bc528592b21c0e28d6f32c0a4/reproman_trace.gz
2022-12-15 17:46:17,965 [INFO   ] Copied tracing artifacts under /home/yoh/.tmp/pytest-of-yoh/pytest-349/local0/traces/20221215174616-e5
FAILED
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> traceback >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
reproman/interface/tests/test_execute.py:137: in test_trace_local
    execute("ls", ["-l"], trace=True, resref="testing-local")
reproman/interface/execute.py:354: in __call__
    out, err = cmd()
reproman/interface/execute.py:82: in __call__
    self.post_command()
reproman/interface/execute.py:256: in post_command
    write_configuration(
../../misc/reprozip/reprozip/reprozip/tracer/trace.py:388: in write_configuration
    files, inputs, outputs = get_files(conn)
../../misc/reprozip/reprozip/reprozip/tracer/trace.py:116: in get_files
    executions = proc_cursor.execute(
E   sqlite3.OperationalError: no such table: processes
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> entering PDB >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> PDB post_mortem >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> /home/yoh/proj/misc/reprozip/reprozip/reprozip/tracer/trace.py(116)get_files()
-> executions = proc_cursor.execute(
(Pdb) l
111  	    files = {}
112  	    access_files = [set()]
113
114  	    # Finds run timestamps, so we can sort input/output files by run
115  	    proc_cursor = conn.cursor()
116  ->	    executions = proc_cursor.execute(
117  	        '''
118  	        SELECT timestamp
119  	        FROM processes
120  	        WHERE parent ISNULL
121  	        ORDER BY id;

This is the error you would get if trace.sqlite3 doesn't exist in the directory where you call write_configuration() (or doesn't contain the expected data). There is no check that the file exists on the ReproZip side, so if the file is not there it will treat it as an empty database and say this too.
https://github.com/VIDA-NYU/reprozip/blob/81e3ea426007617c57a1a3be51ace4af4faf1fc3/reprozip/reprozip/tracer/trace.py#L377
Are you sure there is a valid trace.sqlite3 file in the directory?

we will check -- thank you @remram44 for the pointers!
attn @asmacdo . I will close it for now, and will come back if there is need for more info ;) Cheers!


[wordy] exercise

@exercism/clojure , added wordy exercise

Thanks @leetwinski! @exercism/clojure Would you have a chance to review?

LGTM. Thanks, @leetwinski.

@yurrriq thanks!


Add a test for the Catalog API

Should this test live in a tests directory? Can we also add and update to the travis.yml to run the tests on PRs, etc.?

AFAIK "spec"  is the standard place to put Ruby tests.

@yonpols your changes look great!

Squashed commits.


Adding category and region counters to search view.

:+1: after comments

I guess as you mentioned earlier @cynthialee, we could probably put regions and categories into the same loop. Either way, looks good :+1:

@lkysow @Jareechang Take another look please. I've changed the spacing. I've kept the var mappings because of new data (activity vs category, i.e. FOOD includes Food Security and Nutritional Status Impovement) and to make it easier semantically.

nice! :+1:


Adding info about limitations in debugger statements in README

Suggestion in #309

I've tested with debugger statement and it works thx to #311.
This PR should be reverted (please don't be as prompt to merge PR - let it be 24h so people can comment and/or the author can improve its PR).
ts-jest version 20.0.14 + outDir inside tsconfig.json + a file src/subdir/file.test.ts:

Everything works as expected. The issue was all about removing outDir from tsconfig.json inside ts-jest source code.

Thanks @tkrotoff
I've confirmed that both breakpoints and debugger statements work in VSCode in this private branch

I agree that this PR should be reverted.


Geenrate SVG displaying palette for docs

I was thinking yesterday it might be nice to show the palette in the readme. I see you've done that now with a PNG. Github supports SVG files in markdown.
Perhaps we could generate an SVG for display in the readme? Happy to give it a go

very rough code:
const svg = `
  <svg viewBox="0 0 100 100" xmlns="http://www.w3.org/2000/svg">
    ${Object.values(colors).map(
      (color, i) =>
        `<circle
            r="5"
            stroke="rgba(0,0,0,0.1)"
            stroke-width="1px"
            cy="${Math.ceil((i + 1) / 4) * 10}"
            cx="${((i % 4) + 1) * 10}"
            fill=${color}
          />`
    )}
  </svg>

sounds good, you could generate it inside the watcher.
just npm install, npm run start, and when you edit and save theme.js it creates these themes (and the svg perhaps).

something like:
const { colors } = eval(`${data};noitalics`)

should give you fresh colors on file-save.

Yeah i was just hacking something together locally. Will continue later today.
I was wondering why you eval the file, instead of using exports and requiring? You can bust the require cache like:
function requireUncached(module) {
  delete require.cache[require.resolve(module)]
  return require(module)
}
requireUncached("./theme")

Or is there some other reason i'm not seeing?

i had no idea, let's use requireUncached and real exports then :-)

OK will do


Add bgfxdotnim

Add bgfxdotnim (BGFX C99 bindings)

@dom96 how do you feel about removing a package from nimble?

@zacharycarter Before merging, I would recommend adding README.md to your repository, where you explain what your package does, and how to use it.

@narimiran - will add a README this morning.
Regarding the existing BGFX package in nimble's dir - I can certainly amend the PR to keep the existing BGFX bindings from halsyss but since they haven't been updated in over a year and they're not usable with the current version of BGFX, I wonder if there's any point in keeping them in the nimble package repo.

@narimiran A Nimble "package repository" where stuff can disappear from nilly-willy is unusable IMHO. Nimble needs to fork every registered nimble package and old stuff should live forever. Exception: Packages with terrible security implications.

@Araq I thought that might be the case. Now I closed #944 for the same reason.
@zacharycarter will you modify this PR to only add your package?

Will do, thanks!

Yes, what @Araq said. Packages should not be removed, for any reason. This is one of the reasons why we need our own centralised package repo.

@narimiran done!


Removed deprecations for Symfony 2.8

Hi all,
I removed the deprecation warnings for use with Symfony 2.8 and above. Would be nice if you can merge it so we do not have to maintain our own version. If I need to do more work before you will merge please let me know. I tried to make the changes as minimal as possible.

Thank you very much for this excellent concise PR!


A way to expand tiles without moving other tiles (and also expand on top)

I love all the work that you have done with metafizzy (I am still pretty new to coding and so far I have spent a good amount of time playing around with packery, which was phenomenal at helping me grasp JS due to how much visual feedback you get as you work on it) and now I am back looking at yet another awesome project you put together. Here is my question...
http://codepen.io/7ruth/pen/GNBwJw
In the demo above, when I click the expand button on a tile, the tile expands, its canvas moves under subsequent tiles (if they are on the same Y level) and pushes all tiles below it, further down.
However if I expand the last created tile, it does not affect any previously created tiles while its canvas also rests on top of other tiles.
Is there a way to get all tiles to behave like the last created tile? (on expand, their canvas to be the highest one in the order as well as not moving away any sibling tiles?)
Is this possible? Thank you for any tips/help!

I played around with it over the weekend and realized how simple it was. Draggabilly is awesome.
Demo: http://codepen.io/7ruth/pen/GNBwJw
Just need to add 'position':'absolute' to the css.


Upgrade PostCSS to 7.0.2

Thank you, @ansballard. This will be handled in https://github.com/jonathantneal/postcss-color-mod-function/pull/22


iOS14.6 WebViewJavascriptBridge not work but iOS14.3 works

WVJB Bug Report
iOS14.6 WebViewJavascriptBridge register events, but couldn't got callback from wkwebview, but it works on iOS14.3
Wkwebview load success, got finish load it, no errors.
Cheers,
@marcuswestin

兄弟中文描述一下, 没看懂这机翻的啥意思


Phone window clearing doesn't work properly

In most places with phones, once a person to call is chosen, the text for phone contacts remains in the tiles. When the text for the phone call is displayed, the phone contacts' names obscure parts of the text in places where there was previously no text.
It's a little hard to explain in words, but we've encountered it for a while. Example screenshot (Lost Underworld gets hit especially hard since it has such a short text line):

This was worked around in d78af6a.

Same happens with shops. And Stored Goods iirc.


Starting draft of Syntax and Semantics Standards

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

fyi: @johnjcasey I'm working to move these onto the website. I'd like your advice to figure out which should/shouldn't be here. Happy to discuss on the doc or the PR: https://docs.google.com/document/d/1V2FkGGunVgvLwi1dKHr-7mtDuwYjTuvuESV_oPzVnfQ/edit?resourcekey=0-KvfQq-5iCcMlu3f3MFJ-GQ#heading=h.xl97lw3dyot7

also, the staged page: https://apache-beam-website-pull-requests.storage.googleapis.com/23427/documentation/io/syntax-semantic-standards-io/index.html

On the staged page itself, I think we should keep some gridlines to keep it
easier to read
On Thu, Sep 29, 2022 at 10:18 PM Pablo @.***> wrote:

also, the staged page:
https://apache-beam-website-pull-requests.storage.googleapis.com/23427/documentation/io/syntax-semantic-standards-io/index.html
—
Reply to this email directly, view it on GitHub
https://github.com/apache/beam/pull/23427#issuecomment-1263025643, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AWXHCHDYBLNKHNPVAP3BXZTWAZEYZANCNFSM6AAAAAAQZDTZ5A
.
You are receiving this because you were mentioned.Message ID:
@.***>


fix a potential problem in RBAC test and refactor the test utility

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: yangminzhu
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ozevren
If they are not already assigned, you can assign the PR to them by writing /assign @ozevren in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pkg/OWNERS
tests/integration/security/OWNERS [yangminzhu]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Thank you for working on this. I'm also working on the extended RBAC tests + refactoring after https://github.com/istio/istio/pull/13824 was merged  but this refactoring seems cleaner than mine.
Another thing I want to say is https://github.com/istio/istio/pull/13824 seems to be prematurely merged. I think we need to have another OWNER file for rbac test folder. This has happened a couple of times where a PR is merged and was changed right away.

nit: I think we should change the function name Check back to CheckRBACRequest (https://github.com/istio/istio/pull/13824#discussion_r281738656). I can do it in my extended test PR, wdyt @yangminzhu

New changes are detected. LGTM label has been removed.

@yangminzhu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
016b6055c0ca7f41dd7fbf8d4a22293ac1df916f
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
016b6055c0ca7f41dd7fbf8d4a22293ac1df916f
link
/test istio-unit-tests

prow/istio-integ-local-tests.sh
016b6055c0ca7f41dd7fbf8d4a22293ac1df916f
link
/test istio-integ-local-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@yangminzhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
016b6055c0ca7f41dd7fbf8d4a22293ac1df916f
link
/test istio-unit-tests

prow/istio-integ-local-tests.sh
016b6055c0ca7f41dd7fbf8d4a22293ac1df916f
link
/test istio-integ-local-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-integ-local-tests

@yangminzhu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
016b6055c0ca7f41dd7fbf8d4a22293ac1df916f
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-unit-tests

/lgtm

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: pitlv2109, yangminzhu
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ozevren
If they are not already assigned, you can assign the PR to them by writing /assign @ozevren in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pkg/OWNERS
tests/integration/security/OWNERS [yangminzhu]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@yangminzhu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
016b6055c0ca7f41dd7fbf8d4a22293ac1df916f
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
016b6055c0ca7f41dd7fbf8d4a22293ac1df916f
link
/test istio-integ-k8s-tests

prow/release-test.sh
016b6055c0ca7f41dd7fbf8d4a22293ac1df916f
link
/test release-test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@yangminzhu looks like the tests are still failing on prow.  A few are returning 503s ... so maybe a logic error in the test?

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: nmittler, pitlv2109, yangminzhu
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pkg/OWNERS [nmittler]
tests/integration/security/rbac/OWNERS [nmittler,yangminzhu]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@yangminzhu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
016b6055c0ca7f41dd7fbf8d4a22293ac1df916f
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Playing and stopping midis causes short freezes

Description
Playing or stopping a midi, or being near one of these events will cause the console to display "error midi.fluidsynth: not a soundfont file" a few times and temporarily freeze the screen, though your character will still move in the direction you were holding down. The midi still plays.
Reproduction

Play or stop a midi, or be near a player who does the same
Screen freezes, midi.fluidsynth error

I apologise if I haven't used the correct terminology for what is occurring, but these videos of the issue should show the problem better than I can describe it.
https://github.com/space-wizards/space-station-14/assets/146871669/f46c45e2-b4f5-4cc3-8d88-b8aa3139ec03
https://github.com/space-wizards/space-station-14/assets/146871669/c715c8bd-bd89-401d-9991-f6df04e3be3c

Getting similar issues, its very bad if there is a band playing, literally 1 fps.

Dupe https://github.com/space-wizards/RobustToolbox/issues/4229


Move variables in src/sbuttons.less to new file src/_variables.less

Just move the variables in src/sbuttons.less to new file src/_variables.less then import src/_variables.less in the beginning of sbuttons.less before any file
You should also change the link in the README for sbuttons.less under Modifying Button Colors to the new variables.less file and change the text as well to "_variables.less"

Would like to work on this

Ok @annettomcy I will assign you

is anyone working on this?

Yes me

okay

Is this issue still open?

@faraz16iqbal this issue is assigned. Please look for unassigned issues.

I want to work on it? is this still open?

@abhishekrawe someone is working on this.

Unassigning @annettomcy as they are taking too long and this is a high priority issue.

I would like to be assigned to this, if that's possible? @shahednasser

Can i work on this?

@tmott13 I need someone to not take long with it can you do that?

Hi @shahednasser
I can do it quickly.
Is the problem Statement same as
https://github.com/sButtons/sbuttons/issues/395#issue-712643930 ?

Yes @shahednasser  i can do it quickly.

Assigned @kuldeep123kd


MAINT: rename MaximumFlowResult.residual to flow

The attribute MaximumFlowResult.residual was poorly named: It in fact
represents the flow function of the maximum flow, whereas the residual
is given by the difference between the input graph and this flow
function. As such, we simply rename it from residual to flow to
avoid the risk of confusion.
A different possible fix would be to change the attribute to actually be
the residual graph, but that would change its value and therefore lead
to a slightly trickier deprecation. The flow is also useful in itself,
so for now, we simply include that, and let it be up to the user to make
the more or less trivial calculation of the residual if that's ever
needed.
This closes https://github.com/scipy/scipy/issues/14731
I think this is the first time I add a DeprecationWarning, so I'd appreciate
if the prospective reviewer could take a look at the form of that.
cc @czgdp1807 @pmla

Great, thanks both for checking.

@h-vetinari a future deprecation to be added to #15765

A removal after one release (i.e. deprecation in 1.9, removal in 1.10) is a bit aggressive, no? I think we should adapt the warning to promise removal by 1.11. Could you send a follow-up PR @fuglede?
(Thanks for the ping @j-bowhay 🙃)

@h-vetinari Note that our policy is flexible. In this case I did not think it was necessary. Feel free to send a quick fix otherwise.

I know that the policy if flexible, and I get that the naming was suboptimal, but just removing the old way of doing things will result in a hard break for everyone who had warning-less code in 1.8.
It's not uncommon that people don't upgrade for a while and then bump more than one version in one go. Of course we cannot accommodate that indefinitely, but two releases (~= 1 year) seems like a decent trade-off.
I'd be less outspoken if this was just a necessary behaviour-change, but for removing something entirely, we should leave more time IMO.
I'd ask @fuglede to do this, since it was their PR and I just didn't see it in time before it got merged.

@h-vetinari First, a maintainer approved, and for such small thing it's more important to have a common voice than debating and have such conversation. We can meet offline to talk about these of course.
Second, it took me the same time to make a PR than it certainly took you to comment. So please, next time just do the change. If you really look at it, we have very limited people contributing to SciPy. So let's help everyone by not asking to make extra PRs to fix a single char.

I made the PR and updated the version. Thanks again everyone. All close here 😃