Incrementally show items / bullet points of a page

Is your feature request related to a problem? Please describe.
Yes, I want to create a presentation that I can talk along to. I do not want the full page to be shown when sliding to it but only show up to a certain marker, and then be able to press a key (say j etc) to incrementally populate the page with each new part (e.g. bullet point or paragraph) that is to be shown.
Describe the solution you'd like
What I can think of is to use line markers, just like --- for pagination. But that would only work on a paragraph level AFAIK and probably a more sophisticated solution should be chosen, a string delimiter that can be anywhere in a line, even multiple times in a single line. That way it would be possible to incrementally populate/show the page as one talks along with it. This would especially also work with incrementally showing more bullet points.
Describe alternatives you've considered
Using MS PowerPoint? No, I don't think anything terminal related does support that yet. But for getting slides into more serious use, I can see a great benefit in that.
Additional context
Finding a marker might be hard and I don't want to mandate anything here. Anything that's distinguishable from the actual content and yet easy to type and read at the end of the lines where a split ought to happen. e.g. what about ^^^ (I doubt that'll rarely happen that someone wants to write that).
p.s.: whatever marker is decided to be taken, code blocks should not be subject to be split up (or should then?). 🤔

Hey I believe this is a duplicate of #177 (feel free to reopen this issue if I am mistaken)

Proposal to fix: https://github.com/maaslalani/slides/pull/276#issuecomment-1872677592


Restore private key from mnemonic

How could one go about restoring your secret from a mnemonic?

Shortly thereafter I had found the answer! Apologies. Excellent work, thank you for this valuable contribution to the Stellar network.


crash in 3.8.0 and 3.8.1 from many users

New Issue Checklist

[x] I have read and understood the CONTRIBUTING guide
[x] I have read the Documentation
[x] I have searched for a similar issue in the project and found none

Issue Info

Info
Value

Platform Name
ios

Platform Version
8.0

SDWebImage Version
3.8.0

Integration Method
cocoapods

Xcode Version
e.g. Xcode 7.3.1

Repro rate
not clear from crash reports

Repro with our demo prj
n/a

Demo project link
n/a

Issue Description and Steps
We have Fabric reporting a lot of the crashes
Please fill in the detailed description of the issue (full output of any stack trace, compiler error, ...) and the steps to reproduce the issue.
Crashed: NSOperationQueue 0x145699b0 :: NSOperation 0x145c13c0 (QOS: LEGACY)
0  libobjc.A.dylib                0x2393fa66 objc_msgSend + 5
1  CFNetwork                      0x2478877f -[NSURLCache cachedResponseForRequest:] + 114
2  SDWebImage                     0x23bd795 -[SDWebImageDownloaderOperation URLSession:task:didCompleteWithError:] (SDWebImageDownloaderOperation.m:407)
3  SDWebImage                     0x23bb7f3 -[SDWebImageDownloader URLSession:task:didCompleteWithError:] (SDWebImageDownloader.m:306)
4  CFNetwork                      0x24781505 __51-[NSURLSession delegate_task:didCompleteWithError:]_block_invoke170 + 76
5  Foundation                     0x249a9679 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 8
6  Foundation                     0x2490a5f3 -[NSBlockOperation main] + 146
7  Foundation                     0x248fcbc9 -[__NSOperationInternal _start:] + 768
8  Foundation                     0x249ab931 __NSOQSchedule_f + 192
9  libdispatch.dylib              0x23d12423 _dispatch_queue_drain$VARIANT$mp + 1758
10 libdispatch.dylib              0x23d11a61 _dispatch_queue_invoke$VARIANT$mp + 284
11 libdispatch.dylib              0x23d1415d _dispatch_root_queue_drain + 396
12 libdispatch.dylib              0x23d13fcd _dispatch_worker_thread3 + 96
13 libsystem_pthread.dylib        0x23ec9b29 _pthread_wqthread + 1024
14 libsystem_pthread.dylib        0x23ec9718 start_wqthread + 8

We have also plenty of exactly the same crashes. It started to happen after updating to a version with NSURLSession

@smogun have you manage to reproduce it, I am wondering if that's relevant to the url query changes which were revered in 3.8.1 and if it fixes the crash?

Confirm. After updating to 3.8.1 getting lots of crashes with same reason:
Crashed: NSOperationQueue 0x144ff0570 :: NSOperation 0x14602c890 (QOS: LEGACY)
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000000

Interesting that most of crashes even don't have SDWebImage in the stack trace so found that ticket only after investigation what I updated since previous version so getting so many crashes.

@romk1n 3.8.1 seems broken as well

i am just curios if it is safe to downgrade to 3.7.6

luckily I had this happen while I was debugging. here's the output of bt all. hopefully it's of some help.
warning: could not load any Objective-C class information. This will significantly reduce the quality of type information available.

  thread #1: tid = 0x10e731, 0x0000000188d7334c libsystem_kernel.dylib`mach_msg_trap + 8, queue = 'com.apple.main-thread'

    frame #0: 0x0000000188d7334c libsystem_kernel.dylib`mach_msg_trap + 8

    frame #1: 0x0000000188d731bc libsystem_kernel.dylib`mach_msg + 72

    frame #2: 0x00000001891ade64 CoreFoundation`__CFRunLoopServiceMachPort + 192

    frame #3: 0x00000001891aba80 CoreFoundation`__CFRunLoopRun + 1132

    frame #4: 0x00000001890de2e4 CoreFoundation`CFRunLoopRunSpecific + 292

    frame #5: 0x000000018aab715c GraphicsServices`GSEventRunModal + 180

    frame #6: 0x000000018eff26fc UIKit`-[UIApplication _run] + 692

    frame #7: 0x000000018efed438 UIKit`UIApplicationMain + 208

    frame #8: 0x000000010016f550 Project`main(argc=1, argv=0x000000016fd3ba18) + 124 at main.m:16

    frame #9: 0x0000000188c80600 libdyld.dylib`start + 4

  thread #3: tid = 0x10e782, 0x0000000188d91a88 libsystem_kernel.dylib`__workq_kernreturn + 8

    frame #0: 0x0000000188d91a88 libsystem_kernel.dylib`__workq_kernreturn + 8

    frame #1: 0x0000000188e52298 libsystem_pthread.dylib`_pthread_wqthread + 956

    frame #2: 0x0000000188e51ed0 libsystem_pthread.dylib`start_wqthread + 4

  thread #4: tid = 0x10e783, 0x0000000188d91a88 libsystem_kernel.dylib`__workq_kernreturn + 8

    frame #0: 0x0000000188d91a88 libsystem_kernel.dylib`__workq_kernreturn + 8

    frame #1: 0x0000000188e5247c libsystem_pthread.dylib`_pthread_wqthread + 1440

    frame #2: 0x0000000188e51ed0 libsystem_pthread.dylib`start_wqthread + 4

* thread #5: tid = 0x10e784, 0x000000018880aa50 libobjc.A.dylib`objc_msgSend + 16, queue = 'NSOperationQueue 0x174025e60 :: NSOperation 0x17425bc90 (QOS: LEGACY)', stop reason = EXC_BAD_ACCESS (code=1, address=0xcb1d0beb8)

    frame #0: 0x000000018880aa50 libobjc.A.dylib`objc_msgSend + 16

    frame #1: 0x0000000189976948 CFNetwork`-[NSURLCache cachedResponseForRequest:] + 124

  * frame #2: 0x0000000103711574 SDWebImage`-[SDWebImageDownloaderOperation URLSession:task:didCompleteWithError:](self=0x0000000170154530, _cmd="URLSession:task:didCompleteWithError:", session=0x00000001741d0c20, task=0x000000010971aae0, error=0x0000000000000000) + 748 at SDWebImageDownloaderOperation.m:407

    frame #3: 0x000000010370d8a0 SDWebImage`-[SDWebImageDownloader URLSession:task:didCompleteWithError:](self=0x00000001700ea400, _cmd="URLSession:task:didCompleteWithError:", session=0x00000001741d0c20, task=0x000000010971aae0, error=0x0000000000000000) + 184 at SDWebImageDownloader.m:306

    frame #4: 0x000000018996dee8 CFNetwork`__51-[NSURLSession delegate_task:didCompleteWithError:]_block_invoke.185 + 72

    frame #5: 0x0000000189c58428 Foundation`__NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 16

    frame #6: 0x0000000189ba61ac Foundation`-[NSBlockOperation main] + 96

    frame #7: 0x0000000189b967a4 Foundation`-[__NSOperationInternal _start:] + 620

    frame #8: 0x0000000189c5a810 Foundation`__NSOQSchedule_f + 224

    frame #9: 0x0000000103ffd1d4 libdispatch.dylib`_dispatch_client_callout + 16

    frame #10: 0x000000010400ae70 libdispatch.dylib`_dispatch_queue_serial_drain + 1132

    frame #11: 0x0000000104000db8 libdispatch.dylib`_dispatch_queue_invoke + 744

    frame #12: 0x000000010400d058 libdispatch.dylib`_dispatch_root_queue_drain + 584

    frame #13: 0x000000010400cda8 libdispatch.dylib`_dispatch_worker_thread3 + 140

    frame #14: 0x0000000188e523d8 libsystem_pthread.dylib`_pthread_wqthread + 1276

    frame #15: 0x0000000188e51ed0 libsystem_pthread.dylib`start_wqthread + 4

  thread #6: tid = 0x10e785, 0x0000000188d91a88 libsystem_kernel.dylib`__workq_kernreturn + 8

    frame #0: 0x0000000188d91a88 libsystem_kernel.dylib`__workq_kernreturn + 8

    frame #1: 0x0000000188e5247c libsystem_pthread.dylib`_pthread_wqthread + 1440

    frame #2: 0x0000000188e51ed0 libsystem_pthread.dylib`start_wqthread + 4

  thread #7: tid = 0x10e786, 0x0000000103b78090 libswiftCore.dylib`@objc Swift._NSContiguousString._fastCharacterContents () -> Swift.UnsafeMutablePointer<Swift.UInt16>, queue = 'com.apple.NSURLSession-work'

    frame #0: 0x0000000103b78090 libswiftCore.dylib`@objc Swift._NSContiguousString._fastCharacterContents () -> Swift.UnsafeMutablePointer<Swift.UInt16>

    frame #1: 0x00000001890ec260 CoreFoundation`CFStringCompareWithOptionsAndLocale + 1620

    frame #2: 0x0000000189b99174 Foundation`-[NSString isEqualToString:] + 76

    frame #3: 0x0000000189b9910c Foundation`-[NSString isEqual:] + 68

    frame #4: 0x00000001890db94c CoreFoundation`CFEqual + 380

    frame #5: 0x00000001890dc904 CoreFoundation`CFBasicHashAddValue + 852

    frame #6: 0x00000001890dd8bc CoreFoundation`CFDictionaryAddValue + 256

    frame #7: 0x0000000189846394 CFNetwork`__CFURLCache::CreateAndStoreCacheNode(__CFURLCacheNode*, _CFCachedURLResponse const*, __CFString const*, _CFURLRequest const*, void const*, bool, bool&) + 724

    frame #8: 0x0000000189845ffc CFNetwork`__CFURLCache::AddCacheTask0(std::__1::unique_ptr<__CFURLCacheNode, std::__1::default_delete<__CFURLCacheNode> >&) + 472

    frame #9: 0x0000000189845df8 CFNetwork`__CFURLCache::AddCacheTask(std::__1::unique_ptr<__CFURLCacheNode, std::__1::default_delete<__CFURLCacheNode> >&) + 52

    frame #10: 0x00000001898480d8 CFNetwork`__CFURLCacheAddCachedResponseForRequestWithSession(_CFURLCache const*, NSURLSession const*, _CFCachedURLResponse const*, _CFURLRequest const*, void const*) + 732

    frame #11: 0x000000018987870c CFNetwork`__57-[__NSCFURLLocalSessionConnection afterDelegateWithTick:]_block_invoke + 72

    frame #12: 0x0000000103ffd214 libdispatch.dylib`_dispatch_call_block_and_release + 24

    frame #13: 0x0000000103ffd1d4 libdispatch.dylib`_dispatch_client_callout + 16

    frame #14: 0x000000010400ae70 libdispatch.dylib`_dispatch_queue_serial_drain + 1132

    frame #15: 0x0000000104000db8 libdispatch.dylib`_dispatch_queue_invoke + 744

    frame #16: 0x000000010400d058 libdispatch.dylib`_dispatch_root_queue_drain + 584

    frame #17: 0x000000010400cda8 libdispatch.dylib`_dispatch_worker_thread3 + 140

    frame #18: 0x0000000188e523d8 libsystem_pthread.dylib`_pthread_wqthread + 1276

    frame #19: 0x0000000188e51ed0 libsystem_pthread.dylib`start_wqthread + 4

  thread #9: tid = 0x10e791, 0x0000000188d912f0 libsystem_kernel.dylib`__semwait_signal + 8, name = 'gputools.smt_poll.0x174021b40'

    frame #0: 0x0000000188d912f0 libsystem_kernel.dylib`__semwait_signal + 8

    frame #1: 0x0000000188cb0774 libsystem_c.dylib`nanosleep + 212

    frame #2: 0x0000000188cb0694 libsystem_c.dylib`usleep + 64

    frame #3: 0x0000000104095874 GPUToolsCore`smt_poll_thread_entry(void*) + 136

    frame #4: 0x0000000188e549bc libsystem_pthread.dylib`_pthread_body + 240

    frame #5: 0x0000000188e548cc libsystem_pthread.dylib`_pthread_start + 276

    frame #6: 0x0000000188e51ed8 libsystem_pthread.dylib`thread_start + 4

  thread #10: tid = 0x10e794, 0x0000000188d7334c libsystem_kernel.dylib`mach_msg_trap + 8, name = 'com.apple.uikit.eventfetch-thread'

    frame #0: 0x0000000188d7334c libsystem_kernel.dylib`mach_msg_trap + 8

    frame #1: 0x0000000188d731bc libsystem_kernel.dylib`mach_msg + 72

    frame #2: 0x00000001891ade64 CoreFoundation`__CFRunLoopServiceMachPort + 192

    frame #3: 0x00000001891aba80 CoreFoundation`__CFRunLoopRun + 1132

    frame #4: 0x00000001890de2e4 CoreFoundation`CFRunLoopRunSpecific + 292

    frame #5: 0x0000000189b8893c Foundation`-[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 304

    frame #6: 0x0000000189ba9460 Foundation`-[NSRunLoop(NSRunLoop) runUntilDate:] + 96

    frame #7: 0x000000018f928134 UIKit`-[UIEventFetcher threadMain] + 136

    frame #8: 0x0000000189c73b9c Foundation`__NSThread__start__ + 1052

    frame #9: 0x0000000188e549bc libsystem_pthread.dylib`_pthread_body + 240

    frame #10: 0x0000000188e548cc libsystem_pthread.dylib`_pthread_start + 276

    frame #11: 0x0000000188e51ed8 libsystem_pthread.dylib`thread_start + 4

  thread #11: tid = 0x10e79c, 0x0000000188d7334c libsystem_kernel.dylib`mach_msg_trap + 8, name = 'com.apple.NSURLConnectionLoader'

    frame #0: 0x0000000188d7334c libsystem_kernel.dylib`mach_msg_trap + 8

    frame #1: 0x0000000188d731bc libsystem_kernel.dylib`mach_msg + 72

    frame #2: 0x00000001891ade64 CoreFoundation`__CFRunLoopServiceMachPort + 192

    frame #3: 0x00000001891aba80 CoreFoundation`__CFRunLoopRun + 1132

    frame #4: 0x00000001890de2e4 CoreFoundation`CFRunLoopRunSpecific + 292

    frame #5: 0x0000000189887a18 CFNetwork`+[NSURLConnection(Loader) _resourceLoadLoop:] + 336

    frame #6: 0x0000000189c73b9c Foundation`__NSThread__start__ + 1052

    frame #7: 0x0000000188e549bc libsystem_pthread.dylib`_pthread_body + 240

    frame #8: 0x0000000188e548cc libsystem_pthread.dylib`_pthread_start + 276

    frame #9: 0x0000000188e51ed8 libsystem_pthread.dylib`thread_start + 4

  thread #12: tid = 0x10e79f, 0x0000000188d7334c libsystem_kernel.dylib`mach_msg_trap + 8, name = 'com.squareup.SocketRocket.NetworkThread'

    frame #0: 0x0000000188d7334c libsystem_kernel.dylib`mach_msg_trap + 8

    frame #1: 0x0000000188d731bc libsystem_kernel.dylib`mach_msg + 72

    frame #2: 0x00000001891ade64 CoreFoundation`__CFRunLoopServiceMachPort + 192

    frame #3: 0x00000001891aba80 CoreFoundation`__CFRunLoopRun + 1132

    frame #4: 0x00000001890de2e4 CoreFoundation`CFRunLoopRunSpecific + 292

    frame #5: 0x0000000189b8893c Foundation`-[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 304

    frame #6: 0x00000001038febf0 SocketRocket`-[_SRRunLoopThread main](self=0x00000001702893d0, _cmd="main") + 360 at SRWebSocket.m:1903

    frame #7: 0x0000000189c73b9c Foundation`__NSThread__start__ + 1052

    frame #8: 0x0000000188e549bc libsystem_pthread.dylib`_pthread_body + 240

    frame #9: 0x0000000188e548cc libsystem_pthread.dylib`_pthread_start + 276

    frame #10: 0x0000000188e51ed8 libsystem_pthread.dylib`thread_start + 4

  thread #13: tid = 0x10e7a0, 0x0000000188d7334c libsystem_kernel.dylib`mach_msg_trap + 8, name = 'com.apple.CoreMotion.MotionThread'

    frame #0: 0x0000000188d7334c libsystem_kernel.dylib`mach_msg_trap + 8

    frame #1: 0x0000000188d731bc libsystem_kernel.dylib`mach_msg + 72

    frame #2: 0x00000001891ade64 CoreFoundation`__CFRunLoopServiceMachPort + 192

    frame #3: 0x00000001891aba80 CoreFoundation`__CFRunLoopRun + 1132

    frame #4: 0x00000001890de2e4 CoreFoundation`CFRunLoopRunSpecific + 292

    frame #5: 0x000000018912b904 CoreFoundation`CFRunLoopRun + 112

    frame #6: 0x000000018fe030d4 CoreMotion`___lldb_unnamed_function2430$$CoreMotion + 824

    frame #7: 0x0000000188e549bc libsystem_pthread.dylib`_pthread_body + 240

    frame #8: 0x0000000188e548cc libsystem_pthread.dylib`_pthread_start + 276

    frame #9: 0x0000000188e51ed8 libsystem_pthread.dylib`thread_start + 4

  thread #14: tid = 0x10e7a1, 0x0000000188e51ecc libsystem_pthread.dylib`start_wqthread

    frame #0: 0x0000000188e51ecc libsystem_pthread.dylib`start_wqthread

  thread #15: tid = 0x10e7a2, 0x0000000188d7334c libsystem_kernel.dylib`mach_msg_trap + 8, name = 'AVAudioSession Notify Thread'

    frame #0: 0x0000000188d7334c libsystem_kernel.dylib`mach_msg_trap + 8

    frame #1: 0x0000000188d731bc libsystem_kernel.dylib`mach_msg + 72

    frame #2: 0x00000001891ade64 CoreFoundation`__CFRunLoopServiceMachPort + 192

    frame #3: 0x00000001891aba80 CoreFoundation`__CFRunLoopRun + 1132

    frame #4: 0x00000001890de2e4 CoreFoundation`CFRunLoopRunSpecific + 292

    frame #5: 0x00000001a24a8e60 AVFAudio`GenericRunLoopThread::Entry(void*) + 164

    frame #6: 0x00000001a24c6804 AVFAudio`CAPThread::Entry(CAPThread*) + 84

    frame #7: 0x0000000188e549bc libsystem_pthread.dylib`_pthread_body + 240

    frame #8: 0x0000000188e548cc libsystem_pthread.dylib`_pthread_start + 276

    frame #9: 0x0000000188e51ed8 libsystem_pthread.dylib`thread_start + 4

  thread #16: tid = 0x10e7a3, 0x0000000188d91218 libsystem_kernel.dylib`__select + 8, name = 'com.apple.CFSocket.private'

    frame #0: 0x0000000188d91218 libsystem_kernel.dylib`__select + 8

    frame #1: 0x00000001891b4d08 CoreFoundation`__CFSocketManager + 640

    frame #2: 0x0000000188e549bc libsystem_pthread.dylib`_pthread_body + 240

    frame #3: 0x0000000188e548cc libsystem_pthread.dylib`_pthread_start + 276

    frame #4: 0x0000000188e51ed8 libsystem_pthread.dylib`thread_start + 4

  thread #17: tid = 0x10e7a9, 0x0000000188d91a88 libsystem_kernel.dylib`__workq_kernreturn + 8

    frame #0: 0x0000000188d91a88 libsystem_kernel.dylib`__workq_kernreturn + 8

    frame #1: 0x0000000188e5247c libsystem_pthread.dylib`_pthread_wqthread + 1440

    frame #2: 0x0000000188e51ed0 libsystem_pthread.dylib`start_wqthread + 4

  thread #18: tid = 0x10e7ab, 0x0000000188d91a88 libsystem_kernel.dylib`__workq_kernreturn + 8

    frame #0: 0x0000000188d91a88 libsystem_kernel.dylib`__workq_kernreturn + 8

    frame #1: 0x0000000188e5247c libsystem_pthread.dylib`_pthread_wqthread + 1440

    frame #2: 0x0000000188e51ed0 libsystem_pthread.dylib`start_wqthread + 4

Same here from Fabric/Crashlytics for multiple users :
Crashed: NSOperationQueue 0x13f82c3d0 :: NSOperation 0x13e7a05c0 (QOS: LEGACY)
0  libobjc.A.dylib                0x182f8c0b0 objc_retain + 16
1  SDWebImage                     0x1005a1a6c -[SDWebImageDownloader URLSession:dataTask:willCacheResponse:completionHandler:] (SDWebImageDownloader.m:289)
2  Foundation                     0x1842c8540 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 16
3  Foundation                     0x18421a870 -[NSBlockOperation main] + 96
4  Foundation                     0x18420ae48 -[__NSOperationInternal _start:] + 604
5  Foundation                     0x1842ca934 __NSOQSchedule_f + 224
6  libdispatch.dylib              0x18335947c _dispatch_client_callout + 16
7  libdispatch.dylib              0x1833654c0 _dispatch_queue_drain + 864
8  libdispatch.dylib              0x18335cf80 _dispatch_queue_invoke + 464
9  libdispatch.dylib              0x183367390 _dispatch_root_queue_drain + 728
10 libdispatch.dylib              0x1833670b0 _dispatch_worker_thread3 + 112
11 libsystem_pthread.dylib        0x183571470 _pthread_wqthread + 1092
12 libsystem_pthread.dylib        0x183571020 start_wqthread + 4

--

#0. com.apple.main-thread
0  libsystem_kernel.dylib         0x18348cfd8 mach_msg_trap + 8
1  libsystem_kernel.dylib         0x18348ce54 mach_msg + 72
2  CoreFoundation                 0x1838c4c60 __CFRunLoopServiceMachPort + 196
3  CoreFoundation                 0x1838c2964 __CFRunLoopRun + 1032
4  CoreFoundation                 0x1837ecc50 CFRunLoopRunSpecific + 384
5  GraphicsServices               0x1850d4088 GSEventRunModal + 180
6  UIKit                          0x188ad6088 UIApplicationMain + 204
7  check                          0x1000ab180 main (main.m:14)
8  libdispatch.dylib              0x18338a8b8 (Missing)

#1. com.apple.libdispatch-manager
0  libsystem_kernel.dylib         0x1834a94d8 kevent_qos + 8
1  libdispatch.dylib              0x18336c7d8 _dispatch_mgr_invoke + 232
2  libdispatch.dylib              0x18335b648 _dispatch_source_invoke + 50

#2. com.twitter.crashlytics.ios.MachExceptionServer
0  check                          0x100181ed0 CLSProcessRecordAllThreads (CLSProcess.c:376)
1  check                          0x100181ed0 CLSProcessRecordAllThreads (CLSProcess.c:376)
2  check                          0x1001822f0 CLSProcessRecordAllThreads (CLSProcess.c:403)
3  check                          0x100172fb0 CLSHandler (CLSHandler.m:24)
4  check                          0x10016e134 CLSMachExceptionServer (CLSMachException.c:444)
5  libsystem_pthread.dylib        0x183573b28 _pthread_body + 156
6  libsystem_pthread.dylib        0x183573a8c _pthread_body + 154
7  libsystem_pthread.dylib        0x183571028 thread_start + 4

#3. com.apple.NSURLConnectionLoader
0  libsystem_kernel.dylib         0x18348cfd8 mach_msg_trap + 8
1  libsystem_kernel.dylib         0x18348ce54 mach_msg + 72
2  CoreFoundation                 0x1838c4c60 __CFRunLoopServiceMachPort + 196
3  CoreFoundation                 0x1838c2964 __CFRunLoopRun + 1032
4  CoreFoundation                 0x1837ecc50 CFRunLoopRunSpecific + 384
5  CFNetwork                      0x183f6dc68 +[NSURLConnection(Loader) _resourceLoadLoop:] + 412
6  Foundation                     0x1842e3e4c __NSThread__start__ + 1000
7  libsystem_pthread.dylib        0x183573b28 _pthread_body + 156
8  libsystem_pthread.dylib        0x183573a8c _pthread_body + 154
9  libsystem_pthread.dylib        0x183571028 thread_start + 4

#4. CHKBeaconsManagerThread
0  libsystem_kernel.dylib         0x18348cfd8 mach_msg_trap + 8
1  libsystem_kernel.dylib         0x18348ce54 mach_msg + 72
2  CoreFoundation                 0x1838c4c60 __CFRunLoopServiceMachPort + 196
3  CoreFoundation                 0x1838c2964 __CFRunLoopRun + 1032
4  CoreFoundation                 0x1837ecc50 CFRunLoopRunSpecific + 384
5  Foundation                     0x1841fccfc -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 308
6  Foundation                     0x184252030 -[NSRunLoop(NSRunLoop) run] + 88
7  check                          0x1000fc2dc +[CHKBeaconsManager beaconsThreadEntryPoint:] (CHKBeaconsManager.m:44)
8  Foundation                     0x1842e3e4c __NSThread__start__ + 1000
9  libsystem_pthread.dylib        0x183573b28 _pthread_body + 156
10 libsystem_pthread.dylib        0x183573a8c _pthread_body + 154
11 libsystem_pthread.dylib        0x183571028 thread_start + 4

#5. com.hackemist.SDWebImageCache
0  libsystem_kernel.dylib         0x183490724 mkdir + 8
1  Foundation                     0x18421451c __49-[NSFileManager _URLForReplacingItemAtURL:error:]_block_invoke + 44
2  Foundation                     0x184213efc -[NSFileManager _URLForReplacingItemAtURL:error:] + 1008
3  Foundation                     0x1842cd854 _NSCreateTemporaryFile_Protected + 500
4  Foundation                     0x184212fa8 _NSWriteDataToFileWithExtendedAttributes + 420
5  Foundation                     0x184299b50 -[NSFileManager createFileAtPath:contents:attributes:] + 84
6  SDWebImage                     0x10059c440 -[SDImageCache storeImageDataToDisk:forKey:] (SDImageCache.m:275)
7  SDWebImage                     0x10059c21c __72-[SDImageCache storeImage:recalculateFromImage:imageData:forKey:toDisk:]_block_invoke (SDImageCache.m:245)
8  libdispatch.dylib              0x1833594bc _dispatch_call_block_and_release + 24
9  libdispatch.dylib              0x18335947c _dispatch_client_callout + 16
10 libdispatch.dylib              0x1833654c0 _dispatch_queue_drain + 864
11 libdispatch.dylib              0x18335cf80 _dispatch_queue_invoke + 464
12 libdispatch.dylib              0x18335947c _dispatch_client_callout + 16
13 libdispatch.dylib              0x183367914 _dispatch_root_queue_drain + 2140
14 libdispatch.dylib              0x1833670b0 _dispatch_worker_thread3 + 112
15 libsystem_pthread.dylib        0x183571470 _pthread_wqthread + 1092
16 libsystem_pthread.dylib        0x183571020 start_wqthread + 4

#10. Crashed: NSOperationQueue 0x13f82c3d0 :: NSOperation 0x13e7a05c0 (QOS: LEGACY)
0  libobjc.A.dylib                0x182f8c0b0 objc_retain + 16
1  SDWebImage                     0x1005a1a6c -[SDWebImageDownloader URLSession:dataTask:willCacheResponse:completionHandler:] (SDWebImageDownloader.m:289)
2  Foundation                     0x1842c8540 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 16
3  Foundation                     0x18421a870 -[NSBlockOperation main] + 96
4  Foundation                     0x18420ae48 -[__NSOperationInternal _start:] + 604
5  Foundation                     0x1842ca934 __NSOQSchedule_f + 224
6  libdispatch.dylib              0x18335947c _dispatch_client_callout + 16
7  libdispatch.dylib              0x1833654c0 _dispatch_queue_drain + 864
8  libdispatch.dylib              0x18335cf80 _dispatch_queue_invoke + 464
9  libdispatch.dylib              0x183367390 _dispatch_root_queue_drain + 728
10 libdispatch.dylib              0x1833670b0 _dispatch_worker_thread3 + 112
11 libsystem_pthread.dylib        0x183571470 _pthread_wqthread + 1092
12 libsystem_pthread.dylib        0x183571020 start_wqthread + 4

#13. com.squareup.SocketRocket.NetworkThread
0  libsystem_kernel.dylib         0x18348cfd8 mach_msg_trap + 8
1  libsystem_kernel.dylib         0x18348ce54 mach_msg + 72
2  CoreFoundation                 0x1838c4c60 __CFRunLoopServiceMachPort + 196
3  CoreFoundation                 0x1838c2964 __CFRunLoopRun + 1032
4  CoreFoundation                 0x1837ecc50 CFRunLoopRunSpecific + 384
5  Foundation                     0x1841fccfc -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 308
6  SocketRocket                   0x1005dee70 -[_SRRunLoopThread main] (SRWebSocket.m:1903)
7  Foundation                     0x1842e3e4c __NSThread__start__ + 1000
8  libsystem_pthread.dylib        0x183573b28 _pthread_body + 156
9  libsystem_pthread.dylib        0x183573a8c _pthread_body + 154
10 libsystem_pthread.dylib        0x183571028 thread_start + 4

I have the same issues too.

I will look at this issue asap. Looks like more than an isolated issue

I'm also having this issue. Critical. Downgraded to 3.7.6.

I got same issue too.
#1623 looks like same issue.

Same for me too. Next time it happens I will try to debug a bit and see if I can find out something useful.

Hope anyone can try this https://github.com/rs/SDWebImage/issues/1623#issuecomment-236508764 , I just can't reproduce the crash by myself.

Hi guys,
Same problem (3.8.1)
Any updates about it?
Thanks!

I will take a proper look at this issue this weekend.

I have spent some time trying to figure this out, but without success.
I'm currently at the state where I think it's related to NSURLCache and perhaps race conditioning there when one thread writes to the cache and this one reads. I'm on this thought path because I noticed in https://github.com/rs/SDWebImage/issues/1608#issuecomment-230932690 that on thread 7, the NSURLSession is writing stuff to the NSURLCache. I would be very curious if this is the case for other crashlogs as well. Could you (who use Fabric), just use the share option from Fabric so you can send me the link to the issue (I will be able to look at all the threads, iOS versions and other info).

@bpoplauschi Yes, of course. Use this link to see crash: http://crashes.to/s/330b8587fe4

Many thanks @DarkDarius. It seems my assumption was wrong. In your crashlog, there is no other thread working with the NSURLCache - dead end here, will need a new hypothesis.
Another thing I tried was to pass nil to [[NSURLCache sharedURLCache] cachedResponseForRequest:] but it won't crash.
Another idea is that somehow, the NSURLRequest gets deallocated, but that makes little sense since the SDWebImageDownloaderOperation has a strong reference to the NSURLRequest.

@bpoplauschi here the one i found http://crashes.to/s/4af2fa1f4c7

Thanks @romk1n

Guys, I'm in a bit of dead-end here. I need help. I've added 1 commit on master with a small change, could you try it and see if the issue still occurs? Also, if anyone can reproduce the issue constantly, could you create a small demo project so I can debug it properly? (maybe @bsjcho)
Note: I was able to simulate the same crashlog by using a deallocated instance of NSURLRequest passed to [NSURLCache cachedResponseForRequest:], but I forced that. Not able to properly reproduce with the current code.

I have made an attempt fix in e7bd5ab: Apparently there is a race condition on NSURLCache and we avoid making those checks unless necessary (basically we will query the NSURLCache only when SDWebImageRefreshCached is used and the image cannot be cached by the system when it's too big or behind authentication). Will release a new version soon.

Guys, 3.8.2 is now available via CocoaPods, please try it out and let me know if the issue still happens or not.

@bpoplauschi Did you file a radar on that race condition in NSURLCache (if yes, can you provide a link to it)? Recently we have received similar crash reports that seem to be caused by the same issue -- not in SDWebImage though :-)

@kaspermunck I did not create a radar, as I am not sure that is the cause. I'm waiting for people that had the issue and upgraded to comment back, if it's fixed. Basically, I only reduced the number of calls to NSURLCache

Dug a little deeper (i.e. actually studied the documentation of NSURLCache) and unfortunately it looks like the race condition is expected in certain cases (read more here).

Thanks to @zaczh, this issue will entirely go away in version 4.1.0.


Resolved issue #20

Added a new function to calculate volume

We realized that this pull request was reversed.
Attempted to merge main into branch 20-update-spherepy-function instead of merging 20-updated-spherepy-function into main.
Closing this pull request to make new, revised pull request


Skip creation of catalog entry when it already exists

Is your feature request related to a problem? Please describe.
When running this for a service that has a catalog info already in the repository or was otherwise created, running this action will overwrite the information.
Describe the solution you'd like
The action should have a toggle to skip creating an entry if it already exists for that service. This can be done by quering the datadog api.
Describe alternatives you've considered
For now I created an additional step to query the api and then skip this action if an entry already exists.

I'm sorry friend, I don't quite understand this issue and I'm hoping you can help me out.
If you're using a GitHub Action to update a service in the Datadog Service Catalog and you supply information for a service—even if it already exists—the idea is that updating it with the same information (or different information) is desired behavior because this is the path through which updates come.
Could you help me understand the use case where you wouldn't want to update a service?

Sure we have the use case where a lot of services don't have a catalog entry yet so we automatically create one in the pipeline using this great action.
But as adaption progresses more and more teams are putting the catalog info in a yaml in their repository with more information, there is a conflict if I would still run it from the pipeline.
Totally fine if you think this is not appropriate for this action. :-)

One of the items I have on my TODO for this Action is to allow folks to just supply the YAML file directly to the action, so I think that might be my preferred middle-ground here. I don't know when I'll have time to get to that, but that's issue #103.

sounds good then I will close my issue


remove incubator notice

appears in web site footers

@mdedetrich I gave up on this because I could not get it to work for persistence-cassandra module.

@mdedetrich does this change look about right? Unfortunately, I don't have to test this on my laptop this afternoon.

I ran this locally and it seems to work.


Integrate kitchen tests

@JasonGiedymin

Making mesos master/slave enabled by default
Integrating Kitchen & tests

Very reluctant to put such a small test, in ruby, in an Ansible repo. Please explain why the existing test folder and scripts are not good enough.

Tests are cumbersome to run/setup
Limited testing abilities
Does not cover running / listening state

Tests were failing because mesos 28 is not yet available for Ubuntu

'mesos=0.28.0-0.2.70.ubuntu1204'' failed: E: Version '0.28.0-0.2.70.ubuntu1204' for 'mesos' was not found

Your spec test looks for a running instance, and if it is listening on a port.
I don't understand still why you cannot either use Ansible commands or a shell execute for this in
https://github.com/AnsibleShipyard/ansible-mesos/blob/master/tests/main.yml
What am I missing?
-Jason

On Mar 28, 2016, at 12:18 PM, Ernestas Poskus<EMAIL_ADDRESS>wrote:
Tests are cumbersome to run/setup
Limited testing abilities
Does not cover running / listening state
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

It is cumbersome to run tests on local machine. I think using Ansble commands for testing is abusing. Writing shell scripts in .travis to test role makes it hard to run locally.

Integration
I had some time to look at this PR. The tests are integration level with kitchen ansible, and I'm ok with that. I'm no stranger to Test Kitchen and have used it for literally years doing chef development (both server and cookbooks).
Travis
However, do note that the travis tests will remain and they will continue to run indefinitely. They serve as the only remote unit test check for PRs.
Travis runs tests/playbook.yml.
# Check the role/playbook's syntax.
- "ansible-playbook -i tests/inventory tests/$SITE --syntax-check"

# Run the role/playbook with ansible-playbook.
- "ansible-playbook -i tests/inventory tests/playbook.yml --connection=local --sudo"

That playbook file has only Ansible tasks.
Local Development
Regarding local development, I enjoy running tests fast.  Even with cachier or base boxes preloaded. In some of the other AnsibleShipyard repos we have a Dockerfile for running those ansible tests locally. Running that locally is faster than vagrant on vbox or parallels (even though docker-machine is on a VM! It would be one less VM that needs spinning up from zero). This is something I'd like to expand using docker-compose.yml.
The speed of local development and testing is literally one of the major reasons why I went to Ansible. So you see, going back to any of those tools is not something I want to push for. There are only a handful of complex cluster related playbooks which I have no problem loading a vagrantfile for. However for any other simpler playbook there are other ways of achieving the same with much more simplicity.
This PR will be on hold until we get the zookeeper playbook in galaxy (will get to that real real soon!)


Module 2 Exercise 3 [MARVIN AYEH]

Please "drag & drop" exercise 3 file below.

Please UPDATE THE TITLE of this "Issue" in the title bar above with your name.
M.A_W4M2E3.docx

Great analysis!


Detected as Trojan.

VirusTotal detected the .exe file as a trojan as seen in the image below.

Here is the complete VirusTotal log:  https://www.virustotal.com/gui/file/ac959daa83029d3c9dc10c5721d6f5d766587c3fbe7885125a499b3c705aa0af/detection

This is false positive tho. You can manually compile it using pkg yourself and get the same result in virustotal.


builtin CSV plugin have to become removed too

Mmmh. This is a mess. Why are the CSV plugins added at a different place than the FTML "plugins"? Why do we initialize self.import_plugins in a method without checking it is empty?
I suggest moving the CSV adding to the constructor, where the FTML stuff is added. This seems to be a more sensible change (make things consistent, not complicated. In addition we might want to make an issue for making this whole thing more robust (do not initialize values in a subfunction, check on proper class-state before adding plugins, etc.) as an easy issue?

when you save a configuration, the msui gets restarted. The old one kept the initial state of CSV in the menu because we missed to remove it too.
The cleanest solution is not to add io plugins silently and have all only by configuration of the users msui_settings.conf.


Create a CONTRIBUTORS.md

Did tiff updated the requirements? I am not seeing CONTRIBUTORS.md being mentioned in the milestone 1 page  anymore...

@Marcony1 Do you think we can close this issue?

Yes, I think she updated the instructions. Now the contributors should be listed in the Readme file. So, I believe we can close this one.

Oh yes I just saw the convo on Slack (https://ubc-mds.slack.com/archives/C24GEK3PV/p1704860185813519). Thanks for the confirmation!
Closing this issue.


Subdirectories should be standalone

As an example, Chapter 1's lists file should contain a call to cmake_minimum_required, so it is buildable on its own.

Thanks for mentioning it. It's fixed now.


Typing on a TextField removes full-screen mode

I have set the flutter application to full-screen mode using this line
void main() async {
  // Enable Fullscreen Mode
  await SystemChrome.setEnabledSystemUIOverlays([SystemUiOverlay.bottom]);

  runApp(MainApp());
}

Here is my navigational strucuture
MainApp -> HomeScreen -> TasksScreen
There is a Text Field in TasksScreen which if selected would add padding from the top and when text is submitted would display the top notification bar, and the bar would stay there even if we press the back button.
Here's the entire issue in video : https://drive.google.com/open?id=1GYAIaswc6Mw-RF2kHqGexwmeHQ0FViGN

Please add the output of flutter doctor -v.

cc @jonahwilliams

This is actually something that is forced by the OS (likely as a way to prevent apps from trapping users in their app). Whenever the keyboard appears, the UI will be re-enabled even if it was set to be disabled via SystemChrome. We provide a utility method called SystemChrome.restoreSystemUIOverlays() to restore previous settings set by the last SystemChrom.setEnabledSystemUIOverlays() call. The restore call should be made whenever the keyboard goes away or when you otherwise need to ensure the UI is disabled again.
See https://docs.flutter.io/flutter/services/SystemChrome/restoreSystemUIOverlays.html for more details.
The relevant PR: https://github.com/flutter/flutter/pull/22221


Terminal inline chat: Down navigates history instead of variable completion

Prerequisite: "chat.experimental.variables.terminal": true

the challenge is the suggest widget context key is not available here.


Fix grammar docs for type aliases in AST

[x] I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Noticed issues when researching this mystical "class alias" feature. There are a few issues still:

The AST node TypeAlias has a getter called typedefKeyword which says it will return the token for the 'typedef' token. This, however, is not true. For a class type alias this will return the token for 'class'. Is that something that should be fixed (at least the docs)?
The language spec calls this feature "mixin classes" or "mixin application class" https://github.com/dart-lang/language/blob/cc2c933b1ae5a2c837f89ca4490040ff158a676f/specification/dartLangSpec.tex#L5428. In the AST this is called "ClassTypeAlias". This is somewhat confusing, especially when trying to find any documentation for this feature. Which, to my knowledge is very scares. I could not find any mention of it on dart.dev. The lang spec is also outdated, since it does not mention dart 3 class modifiers.

Maybe I am nitpicking here, but is this really a "type alias"? It introduces a new nominal type which exists at runtime, unlike standard typedefs. TBH it is quite unclear what this feature is for exactly.
Let me know if I should convert any of the above to an issue.
closes #35485

It looks like this PR may be stale now?

I am waiting for a review still. All comments have been addressed.

Thanks for the ping! Sorry for the delay, I had missed the email indicating that you'd addressed my comments.

Looks like there are conflicts now, I'll rebase the branch


Client never saves remote metadata locally

It looks like Client never actually saves metadata locally. We should fix this so we don't have to hit the remote host all the time.

Well, not only for efficiency reasons, but you gotta cache the previous metadata to avoid rollback attacks.


AuthenticationData decoding never decodes extension

While auditing the code, I noticed that AuthenticationData's parseAttestedData() greedily assumes that the rest of the range is the public key. However, if the extensionDataIncluded flag is set, extension data would not exist (because it was gobbled into the public key), and thus decoding would fail rendering a potentially valid AuthenticationData unusable.
Here, we instead try decoding a CBOR item, and if successful, use only its bytes for the public key, leaving the rest for the extension.

@swift-server-bot please test


Fix tests, bump python version to 3.11

Tests are failing on lines of code that do not exist?

It seems that it is not checking out the right version / commit, it is checking out main.

For some reason the actions/checkout was checking out the base branch instead of the pushed commit. Setting refin the CI fixes it:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0
          ref: ${{ github.event.pull_request.head.sha }}

I have also updated to python 3.11 and the action versions.

The issue with the actions/checkout might be related to https://github.com/actions/checkout/issues/881. Setting refmanually looks fine to me.


Cannot use custom event params in can-EVENT callbacks with explicit arguments

The trigger method in jQuery allows passing an additional argument when triggering events, which is particularly useful when firing custom events. These are passed to can-EVENT handlers in simple examples like this:
<input type="text" id="test" can-foobar="{doStuff}">

$('#test').trigger('foobar', data);

// view model
doStuff: function(context, element, event, data) {}

This works because the whole argument list is passed to the handler:
https://github.com/bitovi/canjs/blob/master/view/bindings/bindings.js#L257
However, if you use the newer syntax to specify what you want to send to your handler...
<input type="text" id="test" can-foobar="{doStuff @event arg2}">

Only the specified arguments are passed and the additional param is dropped. One solution would be to add a new @ key (e.g., @data) to the context like @element and @event, which looks like it would be pretty easy to add here.

@dylanrtt how would multiple args be passed?  I agree that we should fix this.  Thanks for pointing it out.

You can only pass one extra argument to trigger() and the rest are dropped. The jQuery docs recommend passing an array.

Closing for: https://github.com/canjs/can-stache-bindings/issues/9


C26932: Escaping '!' character.

Hello, @mairaw ,
Localization team has reported source content issue that causes localized version to have broken/different format compared to en-us version.
"'!' character should be escaped to avoid localization issues"
Please review and merge the proposed file change to fix to target versions. If you make related fix in another PR  then share your PR number so we can confirm and close this PR.
Many thanks in advance.

Thanks @mairaw


TF_SelectV2Op gets legalized to TFL_SelectOp

1. System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 22.04
TensorFlow installation (pip package or built from source): pip package
TensorFlow library (version, if pip package or github SHA, if built from source): v2.17.0

2. Code
tf.where(condition, x, y)
3. Failure after conversion
The model cannot run on TFLite Micro, as it doesn't support the old SELECT op, only the new SELECT_V2 one.
5. (optional) Any other info / logs
The change was introduced 5 years ago by @abattery to improve compatibility with the older runtimes: https://github.com/tensorflow/tensorflow/commit/061d2e0a0d998623a2b0f191038c0aa918a08027
But now it breaks compatibility with TFLite Micro, which only supports the newer op.
Here's the legalization in question: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/compiler/mlir/lite/transforms/legalize_patterns.td#L302
UPD: I believe that https://github.com/google-ai-edge/ai-edge-torch/issues/93 is basically the same.

Hi, @pkgoogle
Please take look into this issue. Thank you.

Looks like we'll have to break something... @abattery, can you please take a look?

Hi, @tagunil
Thanks for raising this issue. Are you aware of AI-Edge-Torch? As we believe this issue is better supported by and more relevant to AI-Edge-Torch we are moving your issue there. Please follow progress here: https://github.com/google-ai-edge/ai-edge-torch/issues/383
Let us know if you have any questions. Thanks.

Hi, @tagunil
Thanks for raising this issue. Are you aware of AI-Edge-Torch? As we believe this issue is better supported by and more relevant to AI-Edge-Torch we are moving your issue there. Please follow progress here: https://github.com/google-ai-edge/ai-edge-torch/issues/383
Let us know if you have any questions. Thanks.

Hi @gaikwadrahul8,
I've reported the issue here primarily because it's where the code lives. If you're going to track it in a different place, that's fine for me. If you're going to move the code to a different place, that's also fine. But if you're going to drop this code completely and force everyone to migrate to PyTorch, it's a different story, because the product I've been working on when I hit the problem isn't going to migrate from TF to PyTorch anytime soon.

We may end up moving this issue ultimately to LiteRT. For now we are closing this current issue but please follow progress on the new issue.


Can we benefit from uncontrollable approach?

https://github.com/jquense/uncontrollable

Reactabular already follows this pattern. Didn't provide a formatter? We'll just use a default one. However, this is a very simple thing to do and I don't think we need to adopt this dependency to do it. In practice we can just consult 'props' to see if things are there and use a sane default if it's not provided. The presence of the tapsHash in the code is suspicious to me.
However, one thing that I did like is the use of React.PropTypes. :)

However, one thing that I did like is the use of React.PropTypes. We should definitely adopt that. :)

Yeah, let's leave this open for now till that gets resolved.


setModalVisible not working/

I Have been trying to make a toggleable Modal. I practically copy pasted this code from the Read_Me, but it doesn't seem to work. I have the modal visible by default and have it on an onBackDropPress it calls this function. const [isModalVisible, setModalVisible] = useState(false);     const toggleModal = () => {       setModalVisible(!isModalVisible);       console.log('aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa')     };. It prints the 'aaaaaaaaaaaaaaaaa' but doesn't actually hide the Modal. I also tried just doing false instead of !isModalVisible. Any help would be greatly appreciated!

the problem its only on iOS or android too? im haveing that problem on iOS only :/

I'm also having this problem. Have either of you found any work-around?

https://github.com/react-native-modal/react-native-modal/issues/534#issuecomment-841331077
I commented about my found solution for this bug.
It's because IOS not allow two modals in same time

@hmarques98 this is not the same bug

Hi!
I'm closing this issue because it's a question and not a bug report. Please don't take it personally, I'm just trying to make it easier to maintain this project by separating questions from bug reports 🙏.
If you're still looking for feedback/answers, could you please ask your question in a new discussion?
Thank you!


refactor: :recycle: Testing data-color cascading

fixes #2834

Just putting up for review to get visual tests running.

Putting to review only to see visual differences


Have --verbose and --wait-time flags exposed for operator-sdk scorecard inside preflight to simplify debug

Is your feature request related to a problem? Please describe.
I debug the scorecard command by preflight
operator-sdk scorecard --output json --selector=test=basic-check-spec-test --kubeconfig /kubeconfig --namespace default --service-account default --config /tmp/scorecard-test-config-719719153.yaml /tmp/preflight-1476094131/fs

Here is the current error output I have, and it's not enough for me to debug properly. I'd like to have more logs and more time to connect to my cluster and check failing pods and their logs
time="2021-09-28T10:08:50Z" level=trace msg="running scorecard with the following invocation[operator-sdk scorecard --output json --selector=test=basic-check-spec-test --kubeconfig /kubeconfig --namespace default --service-account default --config /tmp/scorecard-test-config-719719153.yaml /tmp/preflight-1476094131/fs]"
time="2021-09-28T10:09:20Z" level=error msg="stdout: "
time="2021-09-28T10:09:20Z" level=error msg="stderr: Error: error running tests context deadline exceeded\nUsage:\n  operator-sdk scorecard [flags]\n\nFlags:\n  -c, --config string            path to scorecard config file\n  -h, --help                     help for scorecard\n      --kubeconfig string        kubeconfig path\n  -L, --list                     Option to enable listing which tests are run\n  -n, --namespace string         namespace to run the test images in\n  -o, --output string            Output format for results. Valid values: text, json, xunit (default \"text\")\n  -l, --selector string          label selector to determine which tests are run\n  -s, --service-account string   Service account to use for tests (default \"default\")\n  -x, --skip-cleanup             Disable resource cleanup after tests are run\n  -t, --test-output string       Test output directory. (default \"test-output\")\n  -w, --wait-time duration       seconds to wait for tests to complete. Example: 35s (default 30s)\n\nGlobal Flags:\n      --plugins strings   plugin keys to be used for this subcommand execution\n      --verbose           Enable verbose logging\n\ntime=\"2021-09-28T10:09:20Z\" level=fatal msg=\"error running tests context deadline exceeded\"\n"

Describe the solution you'd like.
I'd like to have:

--verbose flag to be exposed to have more logs.
--wait-time flag to be exposed to connect to my cluster and check pods status

Describe alternatives you've considered.
Right now I have to run operator-sdk scorecard without preflight to use verbose and wait-time options.

Adding the --verbose flag should be covered in #281.
The --wait-time seems reasonable as well, but it's not currently a preexisting configuration, so we'll need to look at this closer and see if there are other timeouts we need to synchronize for this test.

Hi team, I was opening this issue while testing preflight v0.0.0, and my main concern was that the preflight was failing too fast for me to debug manually. Now, with preflight v1.0.3, I have an impression that all time-related concerns are managed in a better way, and I also found how to retrieve the logs from my cluster in an automated way during the preflight execution.
So exposing the --wait-time  flag has no added value for me anymore, and we could close this feature request if it's ok for everyone.


allow numerical operators in filters for numerical variables

It would be desirable to filter numerical variables like sample size using numerical operators. e.g., a filter to plot only studies with sample size >30

I resolved this issue using sliders instead of inequalities. So now if you click on a column filter text box, it should bring up a slider so the user can select a range. However, this does create a slightly annoying bug where the first time you select a filter box, it resets the position of the table on the page. I'll open a separate issue to fix this later on, but the main functionality should work as expected afterwards.


Enable perfsprint linter and fix up code issues

This PR enables perfsprint linter and fixes its issues.
Changes that improve both readability and performance are:

replace fmt.Sprintf("%d", x), fmt.Sprint(x)  with strconv.Itoa(x) for int values;
replace fmt.Sprintf("%t", b) with strconv.FormatBool(b) for bool values;
replace fmt.Sprintf("%d", x) with strconv.FormatInt for int64 values;
replace fmt.Sprintf("%d", x) with strconv.FormatUint for uint64 values;
remove redundant fmt.Sprint statements.

Thanks @alexandear for this and @beorn7 for the review.


Carousel slide size responsive issue

Resizing the browser window on desktops or changing orientation on mobile devices does not have a responsive behaviour. This issue is due to the custom script that forces all slides to become the same size irrespective of how much space the varying content takes (previously the slides were not all a consistent size).
Proposed solution: include an event listener that listens for width/ height of the window and recalculate appropriate size of the carousel.

Useful reference in solving this issue : https://developer.mozilla.org/en-US/docs/Web/API/Window/resize_event


(Backend) CAWP Women Legislators

Description

collect data on number of women in state legislatures nationally, by state, by race from multiple CAWP csv files, process the data and then send to bigquery for use by frontend

Motivation and Context
#1441
How has this been tested?

unit tests on new helper functions
integration tests using sample subset csvs and mocking the API call to those; comparing against a pre-generated json file with expected output

Types of changes

New feature (non-breaking change which adds functionality)

I think we could get birthdates for all representative (at least nationally) and calculate age, allowing us to enable the by age report toggle and not just by race. Something to consider

Decision to include territorial delegates (for US Congress) and legislators (for state legislatures) in our rate calculations. More discussion and detail in this Google Doc

Should i merge this now or wait until the merge_state_info fn is done ?

Should i merge this now or wait until the merge_state_info fn is done ?

Lets go ahead and merge. I will submit a pr with the new pattern later


Skip artifacts from adding them to the scanner that do not exist.

Proposed solution to issue #1631

Rethinking that pull request, I think it should not be applied. The reason is that the behavior of skipping an artifact that does not exist should take place as late as possible; that is, the moment when the scanner actually runs. The pull request implements eager behavior: an artifact is not added if it does not exist at Gradle's configuration phase. In general, an artifact may very well be created only after configuration phase.
In summary, the additional test whether a file/artifact does actually exist should be implemented directly inside Flyway's scanner, not in the Gradle plugin.

@twwwt I hadn't looked at the code yet. Agreed.


Add theme for tables

Notes for Reviewers
This PR adds theme for data tables
Signed commits

[x] Yes, I signed my commits.

[!NOTE]
i need to test this with meshery also then we can merge this


[Select] Easily make Select and Multiple Select with Chip the same height

I'm trying to make my Select inputs the same height, and more specifically when using multiple: true with Chips, while keeping them nice and centered.

This appears to have been done for Autocomplete in this section, but I can't get it to work easily for a basic Select, while adjusting sizes.
Here's the simplest setup for this: https://codesandbox.io/s/zen-hertz-rzxy9?file=/src/Demo.js
I wonder if there are some styling changes from Autocomplete that could be ported over to TextField or Select? It'd be great if this worked out of the box.
Or maybe the long-term goal is to completely replace Select with Autocomplete, in which case these styling issues will inevitably disappear?
Follow-up on #20811

@Floriferous You will need to provide your own overrides, the Select is meant to used the same rendering logic as the Input.

Alright, but then why fix this for Autocomplete? To me they both render the same stuff: Chips inside an Input, yet their styling is not coherent.
Autocomplete’s default styles work, whereas Select requires overrides. I don’t see the rationale for leaving it this way. Either they both expand with their children, or they keep things centered and aligned with other regular Inputs.

@Floriferous I start to believe we should remove the multi-select support from the Select component, keep it as <=> with a native select as much as possible.

Yeah it will reduce the inevitable overlap in features and maintenance between Select and Autocomplete!
Though then the API between the 2 components should ideally be quite similar for the migration to be easy. If all you need to do is replace Select with Autocomplete, and remove the multiple prop, that’d be great :)
Am wondering whether Autocomplete really is a good name for the component if it can simply be a MultiSelect.


Assessment ui 2

In the course victory modal:

Only show challenge after finishing however much practice we needed (so if they get a practice level next, don't show the assessment yet). The assessment shows after the last practice level, or whenever you beat the current level fast enough to not need practice.
If you have already beaten an assessment, don't suggest it in the course victory modal.

Coverage increased (+0.007%) to 62.267% when pulling 6d62cdc8ba97f7597a7c73677ce6c0415450f2f8 on assessment-ui-2 into ad84e16d1b3206f5ffc3fffad469ac801200a4a3 on master.


Implement Auto Tag Builder

Types of Changes
Prerequisites
Please make sure you can check the following two boxes:

[x] I have read the CONTRIBUTING document
[x] My code follows the code style of this project

Contribution Type
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue, please reference the issue id)
[x] New feature (non-breaking change which adds functionality, make sure to open an associated issue first)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] My change requires a change to the documentation
[x] I have updated the documentation accordingly
[x] I have added tests to cover my changes
[x] All new and existing tests passed

Description
[Place a meaningful description here.]

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.8 out of 9 committers have signed the CLA.:white_check_mark: FlorianRappl:white_check_mark: guiherzog:white_check_mark: ZEISSLaurinAgostini:white_check_mark: kotielnikov:white_check_mark: boromo:white_check_mark: magneticz:white_check_mark: sambou:white_check_mark: dimabory:x: ivan.kolosinskyiivan.kolosinskyi seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


 I'm adding a change to the parse_yaml in the util.sh to accomodate for this. If your template has any white spaces, they will automatically be removed when read in by pegasus.
Currently working on the memsql branch and will have that feature soon!

@emhoa fix is in the memsql pull request if you want to check it out.

hey @aouyang1 it does work! only thing that it fails on -- that I was able to catch -- was the extra trailing space on the purchase_type field. it fails on that

@emhoa Yikes ok. I'm going to test this as well. Thanks for checking up on this.

Hmm just checked it and I see it removing trailing white spaces on purchase_type. What's the error you are getting or what is the template file you are using?

hey austin, i'll try to see if i can do more testing but when i put an extra space in the purchase_type value of 'on_demand ' on the master template, the error that gets returned is "must specify spot or on_demand for purchase_type"

@emhoa Oh also this is only on the memsql branch. Haven't merged these changes into master yet.

hey @aouyang1 you were right...I was on the wrong branch. I tested on_demand and it works but there's something funky about spot right now that the creation stage hangs with or without the space so it's likely an aws thing. once that's resolved, i'll be sure to test it again. thanks for fixing that!

@emhoa Hmm ok. I will check it out as well. I know lately spot prices have been really bad, so pegasus may be waiting forever for the spot request to be fulfilled. every few seconds or so, pegasus pings aws for the spot request ids to see if they are fulfilled.

@emhoa This issue looks resolved so far. If you find that the spot pricing is bringing up issues, we can open a separate one. Closing for now.


⚠ Bofrost.be has degraded performance

In 02a536c, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 991 ms

Resolved: Bofrost.be performance has improved in c034431.


Unleash the power of FnOnce

FnOnce is called no more than once. It is the perfect type for callbacks. Turns out this allows us to only have one update implementation.

The big difference here is taking by value not reference. I believe this ensures we only use closures here, not passing in functions. This may be the only use-case we want to support, but want to check.
The other issue, is that is uses generics. Since every update call in the same contract will be a different generic, this can lead to code bloat. I should check the diff in contract_0.8.wasm size. The use of &dyn Fn lets us use the same bytecode for all instances. (Maybe this is a minor size effect and this point can be ignored).
Other than that, the code looks fine.

I believe this ensures we only use closures here, not passing in functions. This may be the only use-case we want to support, but want to check.

I did not test this but therer is

FnOnce is implemented automatically by closure that might consume captured variables, as well as all types that implement FnMut, e.g., (safe) function pointers (since FnOnce is a supertrait of FnMut).

on https://doc.rust-lang.org/std/ops/trait.FnOnce.html.

Okay, I tested recompiling the staking contract (which uses plenty of update) on the two branches:
utilize-FnOnce: 215274 bytes
master: 212888 bytes
Okay, this is 3k overhead for a contract that has a significant number of calls to update. Let's use your solution.


Optimize the performance of dot by using universal intrinsics in X86/ARM

Introduction
Compare with develop branch, when operating float dot, the new implementation has about 3x faster in AVX2, about 10%~30% faster in SSE2/SSE3/NEON.
Benchmark
Each test has run for 10 loops and then take the average result, The radio is the MFlops division of Baseline and optimized branch(The bigger the radio is, the better performance is achieved).

X86 BaseLine(auto vectorized)

data size(10^3)
develop(float)

4000
772.81 MFlops   0.010352 sec

8000
769.16 MFlops   0.020802 sec

X86-SSE2 enabled

data size(10^3)
usimd-floatdot(float)
ratio

4000
819.17 MFlops   0.009766 sec
1.05

8000
815.09 MFlops   0.019630 sec
1.05

X86-SSE3 enabled

data size(10^3)
usimd-floatdot(float)
ratio

4000
853.32 MFlops   0.009375 sec
1.10

8000
848.88 MFlops   0.018848 sec
1.10

X86-AVX2 enabled

data size(10^3)
usimd-floatdot(float)
ratio

4000
2482.31 MFlops 0.003223 sec
3.21

8000
2307.47 MFlops 0.006934 sec
2.99

ARM BaseLine(dot.s)

data size(10^3)
develop(float)

4000
1009.15 MFlops   0.007927 sec

8000
1042.69 MFlops   0.015345 sec

ARM-Neon enabled

data size
usimd-floatdot(float)
ratio

4000
1311.65 MFlops   0.006099 sec
1.30

8000
1274.01 MFlops   0.012559 sec
1.22

System Info

Arm
x86

Hardware
KunPeng

Processor
ARMv8 2.6GMHZ 8 processors
Intel(R) Xeon(R) Gold 6161 CPU @ 2.20GHz

OS
Linux ecs-9d50 4.19.36-vhulk1905.1.0.h276.eulerosv2r8.aarch64
Windows Server 2008 R2 Enterprise

Compiler
gcc (GCC) 7.3.0
MSVC14.06

Co-Author
@seiko2plus
Reference

https://software.intel.com/sites/landingpage/IntrinsicsGuide/
https://www.thetopsites.net/article/58234904.shtml
https://github.com/numpy/numpy/tree/master/numpy/core/src/common/simd
https://github.com/opencv/opencv/tree/master/modules/core/include/opencv2/core/hal

It's looks like -msse3 is not enabled during compiling while HAVE_SSE3 is detected.

Might well be - so far any uses of particular SSE levels must have been in assembly code where the HAVE_SSE3 would only be used to guard wether the mnemonic should be used or not. For using them with intrinsics it would be necessary to add the compiler option in Makefile.x86_64, kernel/Makefile and cmake/system.cmake (as it is currenlty done to add -mavx2 for HAVE_AVX2)


[BUG] setuptools>=60 fails to find Python.h on Pyston

setuptools version
setuptools>=60
Python version
Pyston 2.3.1
OS
Ubuntu 20.04, 21.10. Gentoo. Debian 11.
Additional environment information
Pyston-2.3.1 installed via pyenv inside of an isolated Docker-Container with no system Python-Components installed.
Description
Trying to install numpy results in an error about it not finding Python.h when calling distutils try_compile.
It does not give any indication on where it's looking for it, but another package, Pandas also exhibits this issue, though when calling gcc. It's passing -I/usr/local/pyenv/versions/pyston-2.3.1/include/python3.8 to gcc. While the correct path would be /usr/local/pyenv/versions/pyston-2.3.1/include/python3.8-pyston2.3.
Dumping sysconfig.get_paths() does show the correct include path, so that's not where it is getting it from.
This is a relatively recent issue. This worked a week ago, and downgrading to setuptools<60 makes the issue go away.
Expected behavior
Well, I'd expect a successful build.
How to Reproduce

Setup a pyenv environment with latest Pyston (currentls 2.3.1).
Upgrade pip/setuptools/wheel inside of that environment to latest versions.
pip install numpy

Output
# pip install --no-cache-dir numpy
Collecting numpy
  Downloading numpy-1.21.5.zip (10.7 MB)
     |████████████████████████████████| 10.7 MB 4.1 MB/s
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Building wheels for collected packages: numpy
  Building wheel for numpy (pyproject.toml) ... error
  ERROR: Command errored out with exit status 1:
   command: /usr/local/pyenv/versions/pyston-2.3.1/bin/python /usr/local/pyenv/versions/pyston-2.3.1/lib/python3.8-pyston2.3/site-packages/pip/_vendor/pep517/in_process/_in_process.py build_wheel /tmp/tmp5il3akyy
       cwd: /tmp/pip-install-xkdkddw0/numpy_d7c39e368b80449c84a5556ec68ea3b9
  Complete output (95 lines):
  Processing numpy/random/_bounded_integers.pxd.in
  Processing numpy/random/mtrand.pyx
  Processing numpy/random/_sfc64.pyx
  Processing numpy/random/_mt19937.pyx
  Processing numpy/random/_philox.pyx
  Processing numpy/random/_pcg64.pyx
  Processing numpy/random/_common.pyx
  Processing numpy/random/_generator.pyx
  Processing numpy/random/_bounded_integers.pyx.in
  Processing numpy/random/bit_generator.pyx
  Cythonizing sources
  creating /tmp/tmpficqc93o/tmp
  creating /tmp/tmpficqc93o/tmp/tmpficqc93o
  non-existing path in 'numpy/distutils': 'site.cfg'
  running bdist_wheel
  running build
  running config_cc
  running config_fc
  running build_src
  creating build
  creating build/src.linux-x86_64-3.8
  creating build/src.linux-x86_64-3.8/numpy
  creating build/src.linux-x86_64-3.8/numpy/distutils
  creating build/src.linux-x86_64-3.8/numpy/core
  creating build/src.linux-x86_64-3.8/numpy/core/src
  creating build/src.linux-x86_64-3.8/numpy/core/src/npymath
  creating build/src.linux-x86_64-3.8/numpy/core/src/multiarray
  Running from numpy source directory.
  /tmp/pip-install-xkdkddw0/numpy_d7c39e368b80449c84a5556ec68ea3b9/numpy/distutils/system_info.py:2026: UserWarning:
      Optimized (vendor) Blas libraries are not found.
      Falls back to netlib Blas library which has worse performance.
      A better performance should be easily gained by switching
      Blas library.
    if self._calc_info(blas):
  Warning: attempted relative import with no known parent package
  /tmp/pip-build-env-yaf4w4eu/overlay/lib/python3.8-pyston2.3/site-packages/setuptools/_distutils/dist.py:275: UserWarning: Unknown distribution option: 'define_macros'
    warnings.warn(msg)
  Traceback (most recent call last):
    File "/usr/local/pyenv/versions/pyston-2.3.1/lib/python3.8-pyston2.3/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 363, in <module>
      main()
    File "/usr/local/pyenv/versions/pyston-2.3.1/lib/python3.8-pyston2.3/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 345, in main
      json_out['return_val'] = hook(**hook_input['kwargs'])
    File "/usr/local/pyenv/versions/pyston-2.3.1/lib/python3.8-pyston2.3/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 261, in build_wheel
      return _build_backend().build_wheel(wheel_directory, config_settings,
    File "/tmp/pip-build-env-yaf4w4eu/overlay/lib/python3.8-pyston2.3/site-packages/setuptools/build_meta.py", line 230, in build_wheel
      return self._build_with_temp_dir(['bdist_wheel'], '.whl',
    File "/tmp/pip-build-env-yaf4w4eu/overlay/lib/python3.8-pyston2.3/site-packages/setuptools/build_meta.py", line 215, in _build_with_temp_dir
      self.run_setup()
    File "/tmp/pip-build-env-yaf4w4eu/overlay/lib/python3.8-pyston2.3/site-packages/setuptools/build_meta.py", line 267, in run_setup
      super(_BuildMetaLegacyBackend,
    File "/tmp/pip-build-env-yaf4w4eu/overlay/lib/python3.8-pyston2.3/site-packages/setuptools/build_meta.py", line 158, in run_setup
      exec(compile(code, __file__, 'exec'), locals())
    File "setup.py", line 448, in <module>
      setup_package()
    File "setup.py", line 440, in setup_package
      setup(**metadata)
    File "/tmp/pip-install-xkdkddw0/numpy_d7c39e368b80449c84a5556ec68ea3b9/numpy/distutils/core.py", line 169, in setup
      return old_setup(**new_attr)
    File "/tmp/pip-build-env-yaf4w4eu/overlay/lib/python3.8-pyston2.3/site-packages/setuptools/__init__.py", line 153, in setup
      return distutils.core.setup(**attrs)
    File "/tmp/pip-build-env-yaf4w4eu/overlay/lib/python3.8-pyston2.3/site-packages/setuptools/_distutils/core.py", line 148, in setup
      dist.run_commands()
    File "/tmp/pip-build-env-yaf4w4eu/overlay/lib/python3.8-pyston2.3/site-packages/setuptools/_distutils/dist.py", line 967, in run_commands
      self.run_command(cmd)
    File "/tmp/pip-build-env-yaf4w4eu/overlay/lib/python3.8-pyston2.3/site-packages/setuptools/_distutils/dist.py", line 986, in run_command
      cmd_obj.run()
    File "/tmp/pip-build-env-yaf4w4eu/overlay/lib/python3.8-pyston2.3/site-packages/wheel/bdist_wheel.py", line 299, in run
      self.run_command('build')
    File "/tmp/pip-build-env-yaf4w4eu/overlay/lib/python3.8-pyston2.3/site-packages/setuptools/_distutils/cmd.py", line 313, in run_command
      self.distribution.run_command(command)
    File "/tmp/pip-build-env-yaf4w4eu/overlay/lib/python3.8-pyston2.3/site-packages/setuptools/_distutils/dist.py", line 986, in run_command
      cmd_obj.run()
    File "/tmp/pip-install-xkdkddw0/numpy_d7c39e368b80449c84a5556ec68ea3b9/numpy/distutils/command/build.py", line 61, in run
      old_build.run(self)
    File "/tmp/pip-build-env-yaf4w4eu/overlay/lib/python3.8-pyston2.3/site-packages/setuptools/_distutils/command/build.py", line 135, in run
      self.run_command(cmd_name)
    File "/tmp/pip-build-env-yaf4w4eu/overlay/lib/python3.8-pyston2.3/site-packages/setuptools/_distutils/cmd.py", line 313, in run_command
      self.distribution.run_command(command)
    File "/tmp/pip-build-env-yaf4w4eu/overlay/lib/python3.8-pyston2.3/site-packages/setuptools/_distutils/dist.py", line 986, in run_command
      cmd_obj.run()
    File "/tmp/pip-install-xkdkddw0/numpy_d7c39e368b80449c84a5556ec68ea3b9/numpy/distutils/command/build_src.py", line 144, in run
      self.build_sources()
    File "/tmp/pip-install-xkdkddw0/numpy_d7c39e368b80449c84a5556ec68ea3b9/numpy/distutils/command/build_src.py", line 161, in build_sources
      self.build_extension_sources(ext)
    File "/tmp/pip-install-xkdkddw0/numpy_d7c39e368b80449c84a5556ec68ea3b9/numpy/distutils/command/build_src.py", line 318, in build_extension_sources
      sources = self.generate_sources(sources, ext)
    File "/tmp/pip-install-xkdkddw0/numpy_d7c39e368b80449c84a5556ec68ea3b9/numpy/distutils/command/build_src.py", line 378, in generate_sources
      source = func(extension, build_dir)
    File "numpy/core/setup.py", line 434, in generate_config_h
      moredefs, ignored = cocache.check_types(config_cmd, ext, build_dir)
    File "numpy/core/setup.py", line 44, in check_types
      out = check_types(*a, **kw)
    File "numpy/core/setup.py", line 289, in check_types
      raise SystemError(
  SystemError: Cannot compile 'Python.h'. Perhaps you need to install python-dev|python-devel.
  ----------------------------------------
  ERROR: Failed building wheel for numpy
Failed to build numpy
ERROR: Could not build wheels for numpy, which is required to install pyproject.toml-based projects

Code of Conduct

[X] I agree to follow the PSF Code of Conduct

For background, Setuptools intentionally made a breaking change in version 60, making the local copy of distutils the preferred version. As a result, any behaviors that rely on a patched or monkey-patched version of distutils in the standard library will not work. The temporary escape hatch is to set SETUPTOOLS_USE_DISTUTILS=stdlib.
There are known incompatibilities between Setuptools and numpy (see #2372).

Dumping sysconfig.get_paths() does show the correct include path

Unfortunately, the "include" paths presented by sysconfig are insufficient for distutils, which instead requires a path called "headers". Distutils works around this limitation by supplying the "headers" path for schemes that don't include it (see https://github.com/pypa/distutils/issues/88#issuecomment-1000388214).
As I see it, this issue is essentially a duplicate of #2372 and numpy users should rely on SETUPTOOLS_USE_DISTUTILS=stdlib until numpy no longer relies on monkeypatching.


Installation only tasks always check crates.io

I'd expect the following tasks to behave the same:
[tasks.run-1]
install_crate = "cargo-limit"
command = "cargo"
args = ["lrun"]

[tasks.run-2]
dependencies = ["install-cargo-limit"]
command = "cargo"
args = ["lrun"]

[tasks.install-cargo-limit]
install_crate = "cargo-limit"

But the second one seems to always check crates.io:
$ cargo make run-1
[cargo-make] INFO - cargo make 0.37.10
[cargo-make] INFO - Calling cargo metadata to extract project info
[cargo-make] INFO - Cargo metadata done
[cargo-make] INFO - Build File: Makefile.toml
[cargo-make] INFO - Task: run-1
[cargo-make] INFO - Profile: development
[cargo-make] INFO - Running Task: legacy-migration
[cargo-make] INFO - Execute Command: "cargo" "lrun"

$ cargo make run-2
[cargo-make] INFO - cargo make 0.37.10
[cargo-make] INFO - Calling cargo metadata to extract project info
[cargo-make] INFO - Cargo metadata done
[cargo-make] INFO - Build File: Makefile.toml
[cargo-make] INFO - Task: run-2
[cargo-make] INFO - Profile: development
[cargo-make] INFO - Running Task: legacy-migration
[cargo-make] INFO - Execute Command: "cargo" "install" "cargo-limit"
    Updating crates.io index
     Ignored package `cargo-limit v0.0.10` is already installed, use --force to override
[cargo-make] INFO - Execute Command: "cargo" "lrun"

this is due to the fact that in the second example you dont have metadata for cargo make on how to test it is installed correctly already.
in the first you tell it the binary is lrun but in the second it doesn't have this information and it is trying to find a binary named limit (or more correctly a cargo plugin command limit).
you can fix this by providing this metal information as part of the install_crate attribute which also accepts I fielded it object with all the meta information needed

The updated task definition is
[tasks.install-cargo-limit]
install_crate = { crate_name = "cargo-limit", binary = "cargo", test_arg = [
  "lcheck",
  "--help",
] }

Thank you :pray:


Fix BaseConverter misspell

Description
Fix the BaseConverter misspell as BaseConvertor in the documentation.
Fixes #1

Thanks OBITORASU for the contribution ... We really Appreciate that ...


feat(paymaster-proxy): support rpc calls with policyId

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#320  👈
#319
#318
#317
#309
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jakim929 and the rest of your teammates on  Graphite


Minor s/2004/2204/

Description
Substituted a 2004 into 2204.
Why is this needed
Avoiding Oh old documentation, let it rot further
Fixes: __

Today I learnt that git commit --amend --signoff --no-edit has to done before a git push, that you can't do a --signoff in git commit --amend after git push of the original commit.
Closing this merge request, because there is now #162.
Regards
Geert Stappers
Who also closed MR #160


Support GC Logging option

Elasticsearch contains some logic to properly enable GC logging if ES_GC_LOG_FILE defined.
A "$gc_log_file" option in the module would be nice, that would then add export ES_GC_LOG_FILE if defined.

I'm planning on writing something to address this myself.

Rather than writing it in as an option, it's better to add it into an init_defaults hash.  If export ES_GC_LOG_FILE is present in the init file, but has no value, GC logging is not enabled.  Only if there's a definition for the env var does it enable.


tweak find packages API

This PR changes the registry to be a keyword argument, and allows passing a list or varargs package names as strings to look up from the registry. I found it just makes it a bit less tedious than lots of joinpath(general_registry(), "F", "Flux") stuff. (I had a non-breaking version of this in #11 but I pulled it out here since it's entirely separate).
julia> pkgs = find_packages("AbstractPlotting", "GLMakie", "CairoMakie")
3-element Vector{String}:
 "/Users/eh540/.julia/registries/General/A/AbstractPlotting"
 "/Users/eh540/.julia/registries/General/G/GLMakie"
 "/Users/eh540/.julia/registries/General/C/CairoMakie"

julia> results = analyze_from_registry!(root, pkgs) #...

(This is a breaking change!).

Very weird CI failure...

Looks like a / vs \ issue?

Ohhh, didn't catch that. Ok, I'll try to debug that.

Ah, the issue is that the registry stores the paths with /, but when I construct the path here, I use joinpath which then uses \\. It seem like \\ is correct, so I tried to fix the paths coming out of the registry.

(This is a breaking change!).

I don't care much about breaking changes, the package isn't registered nor highly advertised, so I don't expect many users besides me and you :sweat_smile:
It's good to do improvement to the API at this point, the first version was the result of half-day not-so-serious fiddling, if you have other breaking improvements in mind, please go ahead!


sql and type fields on metrics are ambiguously named

Is there an existing feature request for this?

[X] I have searched the existing issues

Describe the Feature
In this metric definition:
metrics:
  - name: new_customers
    label: New Customers
    model: ref('dim_customers')

    type: count
    sql: user_id # superflous here, but shown as an example

sql is an ambiguous term. Everything dbt does is SQL.
Could we call it something else?
Describe alternatives you've considered
I'm thinking expression vibes. I'd like to clarify what will happen to the expression, which takes me to agg_expression but I don't want people to start writing avg in there (maybe that's an argument to rename type to agg_style or something?
Open to other words!
Who will this benefit?
Metrics users, so every single dbt user right? 😉
Are you interested in contributing this feature?
No, because when I discussed it with @drewbanin he muttered under his breath "oh that'd be a real pain to implement"
Anything else?
No response

A sweetener: I just got tripped up by {{ aggregate_primary_metric(metric.type, metric.sql) }} because I thought metric.sql was a filename

sql is an ambiguous term.
I think the intent here is to say, "You can put any SQL you want in here." I think expression still manages to get that across; I'd also be happy with the slightly longer sql_expression.

No, because when I discussed it with @drewbanin he muttered under his breath "oh that'd be a real pain to implement"

It's fairly straightforward for us. It's a pain for the folks who have started building experimental things with metrics :)
We'd just want to:

update this line
update v4 manifest schema (at schemas.getdbt.com)
update docs

Could I get a final call from you + @drewbanin on whether this needs to happen pre-v1?
From my point of view: We're calling metrics an "experimental" feature, and we're reserving the rights to make breaking changes to the metrics schema in minor versions after v1. It wouldn't be hard for dbt Core to offer backwards compatibility for users who call this sql instead of expression in project code, but it would be a breaking change for manifest.json + an uglier migration for downstream metadata consumers.

just hear to +1 this now that i've started to get my feet wet with metrics -- this feels very ambiguous and a good thing to switch up in future revisions!

my preference:
sql -> expression
type -> aggregate or aggregation

nooo come back

Closing in favor of https://github.com/dbt-labs/dbt-core/issues/5774!


camera.snapshot 'no access to path!' error in 0.65.x

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.65.2 and 0.65.3 0.64.3
Python release (python3 --version):
Component/platform:
Raspberry Pi 3
Description of problem:
camera.snapshot seems to have broken in the 0.65.x 0.64.3 release. I was running 0.64.2 and it worked fine untill I updated to 0.65.2, I then received the error 'Can’t write ‘/tmp/snapshot_front_door_1.jpg’, no access to path!'
Expected:
Expected it to write to the given path :)
Problem-relevant configuration.yaml entries and steps to reproduce:
whitelist_external_dirs: /tmp/

homeassistant user has full access to the /tmp/ folder
        entity_id: camera.front_door_camera
        filename: "/tmp/snapshot_front_door_1.jpg"

Additional info:
Reverting to version before 0.64.3 fixes the problem, it now works as before. I'm now running version 0.64.2 again and it works as expected.
Seem to be related to a fix in the 0.64.3 release:
https://github.com/home-assistant/home-assistant/releases/tag/0.64.3

@mvdarend as you mentioned in the forum, likely to #12810.
File paths and directory paths must be handled differently and will look into this for you

Found a workaround while it gets fixed: create a file with the same name of the snapshot in the same folder.
The camera.snapshot service won't throw an error.


⚠ Bofrost.lu has degraded performance

In 60bc6c3, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1214 ms

Resolved: Bofrost.lu performance has improved in 9751722 after 16 minutes.


How do I turn off go templating

I have done this but it gives the error
{{`{{ .Values.spec.version | replace "." "-" | lower }}` }}

I get this error,
 error converting YAML to JSON: yaml: invalid map key:

What I want?
I want helm to render it as {{ .Values.spec.version | replace "." "-" | lower }} instead of substituting the value

duplicate of https://github.com/helm/helm/issues/2798. Use {{ "{{" }} to escape template syntax.


CMake build, some targets fail linking sycl

Bug Description
When building some of the targets, getting linker error on sycl
Not seeing this as a dependency, any advice on where to get this library?
Reproduction Steps
CMake command:
cmake .. -DCMAKE_INCLUDE_PATH=/home/myhome/.local/include/ -DFL_BACKEND=CPU
No errors, when building with make I get linker error pasted below
[ 94%] Linking CXX executable Benchmark
/usr/bin/ld: cannot find -lsycl
collect2: error: ld returned 1 exit status
make[2]: *** [flashlight/fl/examples/CMakeFiles/Benchmark.dir/build.make:104: flashlight/fl/examples/Benchmark] Error 1
make[1]: *** [CMakeFiles/Makefile2:1074: flashlight/fl/examples/CMakeFiles/Benchmark.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 94%] Linking CXX executable RnnLm
[ 94%] Linking CXX executable Perceptron
/usr/bin/ld: cannot find -lsycl
collect2: error: ld returned 1 exit status
make[2]: *** [flashlight/fl/examples/CMakeFiles/RnnLm.dir/build.make:104: flashlight/fl/examples/RnnLm] Error 1
make[1]: *** [CMakeFiles/Makefile2:1158: flashlight/fl/examples/CMakeFiles/RnnLm.dir/all] Error 2
/usr/bin/ld: cannot find -lsycl
collect2: error: ld returned 1 exit status
make[2]: *** [flashlight/fl/examples/CMakeFiles/Perceptron.dir/build.make:104: flashlight/fl/examples/Perceptron] Error 1
make[1]: *** [CMakeFiles/Makefile2:1130: flashlight/fl/examples/CMakeFiles/Perceptron.dir/all] Error 2
[ 94%] Linking CXX executable Mnist
/usr/bin/ld: cannot find -lsycl
collect2: error: ld returned 1 exit status
make[2]: *** [flashlight/fl/examples/CMakeFiles/Mnist.dir/build.make:104: flashlight/fl/examples/Mnist] Error 1
make[1]: *** [CMakeFiles/Makefile2:1102: flashlight/fl/examples/CMakeFiles/Mnist.dir/all] Error 2
make: *** [Makefile:141: all] Error 2
Platform and Hardware
Ubuntu 20.04, Intel CPU

@mboros1 Can you confirm the path where libsycl is installed? It's failing to link, but this should be caught when running CMake...

I do not have libsycl installed; is it part of a dependency that I'm missing? Sorry, trying to find out what it is but not having much luck

@mboros1 — you'll need to have libsycl - that's the linker error. CMake should surface something nicer, but it's not (sorry)...
Do you have Intel MKL installed? The library should be in a path like /opt/intel/inteloneapi/compiler/latest/linux/lib/libsycl.so depending on where you installed MKL...

@jacobkahn okay thanks for the tip, CMake was getting confused by a version of MKL installed as an apt package. Removed it, set export MKLROOT=/opt/intel/oneapi/mkl/latest and now CMake is finding the correct MKL package. However, I still have the same linker error:
[ 76%] Linking CXX executable AutogradTest
/usr/bin/ld: cannot find -lsycl
collect2: error: ld returned 1 exit status
make[2]: *** [flashlight/fl/test/CMakeFiles/MeterTest.dir/build.make:109: flashlight/fl/test/MeterTest] Error 1
make[1]: *** [CMakeFiles/Makefile2:1581: flashlight/fl/test/CMakeFiles/MeterTest.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
/usr/bin/ld: cannot find -lsycl
collect2: error: ld returned 1 exit status
make[2]: *** [flashlight/fl/test/CMakeFiles/DatasetUtilsTest.dir/build.make:109: flashlight/fl/test/DatasetUtilsTest] Error 1
make[1]: *** [CMakeFiles/Makefile2:1609: flashlight/fl/test/CMakeFiles/DatasetUtilsTest.dir/all] Error 2
/usr/bin/ld: cannot find -lsycl
collect2: error: ld returned 1 exit status
make[2]: *** [flashlight/fl/test/CMakeFiles/AutogradTest.dir/build.make:109: flashlight/fl/test/AutogradTest] Error 1
make[1]: *** [CMakeFiles/Makefile2:1637: flashlight/fl/test/CMakeFiles/AutogradTest.dir/all] Error 2
/usr/bin/ld: cannot find -lsycl
collect2: error: ld returned 1 exit status
make[2]: *** [flashlight/fl/test/CMakeFiles/ContribSerializationTest.dir/build.make:109: flashlight/fl/test/ContribSerializationTest] Error 1
make[1]: *** [CMakeFiles/Makefile2:1553: flashlight/fl/test/CMakeFiles/ContribSerializationTest.dir/all] Error 2
make: *** [Makefile:141: all] Error 2
I found libsycl.so, but my path is slightly different, /opt/intel/oneapi/mkl/latest/lib/intel64, but still my CMake output:
-- MKL_THREADING = OMP
-- Checking for [mkl_intel_lp64 - mkl_gnu_thread - mkl_core - gomp - pthread - m - dl]
--   Library mkl_intel_lp64: /opt/intel/oneapi/mkl/latest/lib/intel64/libmkl_intel_lp64.so
--   Library mkl_gnu_thread: /opt/intel/oneapi/mkl/latest/lib/intel64/libmkl_gnu_thread.so
--   Library mkl_core: /opt/intel/oneapi/mkl/latest/lib/intel64/libmkl_core.so
--   Library gomp: -fopenmp
--   Library pthread: /usr/lib/x86_64-linux-gnu/libpthread.so
--   Library m: /usr/lib/x86_64-linux-gnu/libm.so
--   Library dl: /usr/lib/x86_64-linux-gnu/libdl.so
-- MKL library found
Seems like it should be on the library path. Any thoughts?

I missed a step configuring OneAPI: . /opt/intel/oneapi/setvars.sh sets up all the environment variables for the SYCL toolchain, getting a different linker error now but it's unrelated to this

@mboros1 good to know -- thanks for sharing that... that's a weird setup step. Feel free to open another issue if you're having trouble linking other things.

@jacobkahn thanks for the help, tough project to build but I found out the last step I was missing and for the sake of documentation for the next person searching the issues, the error was:
DistributedBackend.cpp:(.text+0x18d): undefined reference to gloo::mpi::Context::createManaged()'`
Caused because I did not build gloo with MPI, fixed with USE_MPI=ON which is mentioned in build documentation here. Now I can finally test it out!


Special-case trimIndent?

This might be an easy close, not sure.
But following an ending """ with .trimIndent() is arguably an inherent part of the language idiom for many many use cases, and I wondered if those could feasibly be kept together on the same line, as a special carve-out.
Current
    loader(
        """
        Foobar
        ${decl.joinToString("") { "$it\n" }}
        """
            .trimIndent())

Seems nicer
    loader(
        """
        Foobar
        ${decl.joinToString("") { "$it\n" }}
        """.trimIndent())

Eh?

There's two ways to getting this I can see:

Better multiline string handling: Not really possible, see discussion in #343.
Special casing for trimIndent: We try not to special case any particular functions.

Leaving this open to see if others have thoughts, but I think this is unlikely to work.

Special casing for trimIndent: We try not to special case any particular functions.

And I do think that's the right way. The case to make here would be that this function is just about as close to a language feature as a thing could be. Like, it's more that it is a special case than that the tool is making it so. Again... "Eh?"
(I mentioned in another issue that I still sometimes guiltily counteract what the formatter does in my code, so I feel some certain responsibility to file those things for consideration, but don't feel too invested in what happens to them after that.)

This is a duplicate of #251 I believe.

I don't believe it is; that one seems to be about reindenting the actual string contents using the signal of trimIndent as a way to know that is safe. This is about how to format the trimIndent call itself.

Ya, your right, sorry I misread.

This here is what Google Java Format does
➜ cat Test.java
class Test {
  public static final String msg1 = """
      foo asfasf asdf asf asdfasf asdf.
      bar asdf sf asdf asdfasdf as.
      baz asdf dsaf asdf sfd .
  """.trimIndent();

  void foo() {
    loader(
        """
        Foobar
        %s
        """.formatted(decl.joinToString(""))
    );
  }
}

➜  java -jar google-java-format-1.22.0-all-deps.jar Test.java
class Test {
  public static final String msg1 =
      """
          foo asfasf asdf asf asdfasf asdf.
          bar asdf sf asdf asdfasdf as.
          baz asdf dsaf asdf sfd .
      """
          .trimIndent();

  void foo() {
    loader(
        """
        Foobar
        %s
        """
            .formatted(decl.joinToString("")));
  }
}

Since we inherit from GJF, maybe we should request for the capability to handle exceptions for text blocks in there.
Could you open an issue in that repo (https://github.com/google/google-java-format)?

I would add trimMargin() to this. It is similarly at the level of "core language feature", like trimIndent().


Stable Diffusion support

AUTOMATIC1111 has an API:
https://github.com/AUTOMATIC1111/stable-diffusion-webui/wiki/API
This looks really easy to build with! Here are some notes:
The function definition would look something like:
class CreateImage:
  def __init__(self, app):
    self.app = app
    self.reg = app.ai_functions.define(self.run, 'create_image', 'Create a new image',
        short_description="create images")
    self.reg.add_argument('description', 'An in-depth one line description of the image to create', question="What is the description of the image?")
    self.reg.add_argument('count', 'Number of sample images to create (default is 1)', question="How many images did the user request?")
    self.reg.add_to('Artist')

Add a config file section for it:
[a1111]
base_url = 'http://localhost:7860/' # App will append /sdapi/v1/txt2img

Then it's just a matter of sending the description to the API, writing the images to the data/uploads/ folder, and sending the response back, like f"I created an image for you: "

Got a test version of this working. Here's what's left to do:

Create an ID for the image returned (UserStore.create(data_type='upload', name=filename, content=description))
Save the image returned to data/uploads/{id}-{filename} (note: should probably use jpg instead of png)
Add a /uploads/ endpoint to serve the file

Running into some issues getting flask to send a test file. Once that's working, this should be ready to release.


oci: reconsider to remove the restriction of image name must match the chart name

please reconsider to remove the restriction of image name must match the chart name:

To successfully pull dependencies, the image name in the registry must match the chart name and the tag must match the chart version. The repository entry in Chart.yaml is specified as the repository name on the registry without the image name.

from: https://helm.sh/docs/topics/registries/
(this is analogous to #9378 that is about tags/versions)
It is a super common situation that we want the container image and a helm chart that deploys it to have the same name. With OCI the container image name and the helm chart name in the registry share the same name space, so they can't have the same name. In our case, the container "wins". That forces us to postfix all charts and dependences e.g. with "-helm".
It would also make it impossible to host e.g. both a copy of an upstream nginx container image and an nginx helm chart in the same registry because of the name clash.

Hi @pmorch!
Thank you for providing your use case along with the proposal. It really helps us understand the motivation behind your ask so that we can consider these use cases going forward.
Currently the roadmap for the OCI experimental feature is laid out in HIP 6. That document explains what work is needed to unmark it as experimental. The goal is to complete the MVP and mark the feature as stable, then once implemented the community/maintainers can start to consider other use cases.
Have you reached out to @jdolitsky yet? I would start a conversation with him as he's most familiar with the HIP. From there we can determine next steps and see whether this is something we should consider prior to GA or if it's something that can be addressed at a later date.
Let me know if I can be of any assistance. Thanks!

No I didn't reach out to @jdolitsky yet. I'm still wrapping my head around how to setup a CI/CD pipeline including helm and for the time being, I'll accept that:

To successfully pull dependencies, the image name in the registry must match the chart name and the tag must match the chart version.

For that reason, feel free to close this issue if it doesn't contribute to your project. I'll likely have moved on by the time you're ready to consider it.

I suggest that given:

To successfully pull dependencies, the image name in the registry must match the chart name and the tag must match the chart version.

and assuming Chart.yaml has:
name: mychart
version: 0.1.2

Then:
helm chart save . harbor.example.com/dev/mychart:0.1.2

should work, but these should fail:
helm chart save . harbor.example.com/dev/othername:0.1.2
helm chart save . harbor.example.com/dev/mychart:0.1.3
helm chart save . harbor.example.com/dev/mychart:foobar

Otherwise you can push, pull and export the chart, but it cannot be used as soon as somebody wants to use it as a dependency for another chart. This is similar to how you don't get to decide the file name with helm package $dir.
Perhaps helm chart save shouldn't even accept the chart name and tag/version so the only legal variation in the above circumstances should be:
helm chart save . harbor.example.com/dev

It is just weird that you can create and push a chart that cannot later be used as a dependency.
Let me know if you want me to open a separate issue for this. Also, feel free to ignore this comment or the entire issue, if I'm just spamming you guys with noise.

FYI, HIP 6 talks about removing helm chart save in favour of helm package, so most of those discussion topics would likely fall under helm push with the new model. I'd highly suggest giving the proposal a read.

You're right. I've been too lazy.
It is just much easier to have an uninformed opinion :-)


Shed cli logic

Don't merge until after trufflesuite/ganache-core#67 is merged.
Also I will likely need to update package-lock.json again when that happens.

@davidmurdoch is doing some work which invalidates the need for this


Validation Error

Hi,
I trying to make Get Request with Yelp api search endpoint in postman and I am getting validation error.
I am passing the 3 headers, term , location and authorization.
endpoint : https://api.yelp.com/v3/businesses/search
Header
term: food
location: San Francisco
Authorization: Bearer [access_token]
I even tried using the latitude and longitude in header section I am still getting the same error.
term: food
location: 37.7749,122.4194
Authorization: Bearer [access_token]
{
"error": {
"code": "VALIDATION_ERROR",
"description": "Please specify a location or a latitude and longitude"
}
}
Am i missing something here?
Thank you.

@aaduru : Term and location are parameters and go in the query string, not as headers:
URL: https://api.yelp.com/v3/businesses/search?term=food&location=San+Francisco
Header
Authorization: Bearer [access_token]

https://www.yelp.com/developers/documentation/v3/business_search

Does that make sense?

(Also, this Github repo is for the older V2 API --- in the future, you can post V3 Fusion questions at https://github.com/Yelp/yelp-fusion ).

Thank you so much.


modified: removed duplicated mastodon_s3_hostname settings.

mastodon_s3_hostname was duplicated on data.tf.
It seems meaningless, so deleted.

nice catch 👍