Using FirebaseOSX login yields strange errors

   @IBAction func loginClicked(_ sender:Any?) {
        if let email = emailTextField?.stringValue,
            let pw = pwTExtField?.stringValue {
            Auth.auth().signIn(withEmail: email, password: pw) { [weak self] user, error in
                guard let strongSelf = self else { return }
                SwiftyBeaver.debug("user = \(user), error = \(error)")
            }
        }
    }

Using this code to login I never see my debug message. instead I see:
2019-03-18 21:00:00.552207-0500 Tracktive[16337:621029] SecTaskLoadEntitlements failed error=22 cs_flags=20, pid=16337
2019-03-18 21:00:00.552275-0500 Tracktive[16337:621029] SecTaskCopyDebugDescription: Tracktive[16337]/0#-1 LF=0
2019-03-18 21:00:00.954806-0500 Tracktive[16337:621029] [BoringSSL] nw_protocol_boringssl_get_output_frames(1301) [C1.1:2][0x1017270c0] get output frames failed, state 8196
2019-03-18 21:00:00.954844-0500 Tracktive[16337:621029] [BoringSSL] nw_protocol_boringssl_get_output_frames(1301) [C1.1:2][0x1017270c0] get output frames failed, state 8196
2019-03-18 21:00:00.955029-0500 Tracktive[16337:621029] TIC Read Status [1:0x0]: 1:57
2019-03-18 21:00:00.955052-0500 Tracktive[16337:621029] TIC Read Status [1:0x0]: 1:57
2019-03-18 21:00:06.024447-0500 Tracktive[16337:621130] [BoringSSL] nw_protocol_boringssl_get_output_frames(1301) [C2.1:2][0x1030286b0] get output frames failed, state 8196
2019-03-18 21:00:06.024493-0500 Tracktive[16337:621130] [BoringSSL] nw_protocol_boringssl_get_output_frames(1301) [C2.1:2][0x1030286b0] get output frames failed, state 8196
2019-03-18 21:00:06.024683-0500 Tracktive[16337:621130] TIC Read Status [2:0x0]: 1:57
2019-03-18 21:00:06.024700-0500 Tracktive[16337:621130] TIC Read Status [2:0x0]: 1:57
2019-03-18 21:00:06.329748-0500 Tracktive[16337:621130] [BoringSSL] nw_protocol_boringssl_get_output_frames(1301) [C3.1:2][0x10163a2a0] get output frames failed, state 8196
2019-03-18 21:00:06.329792-0500 Tracktive[16337:621130] [BoringSSL] nw_protocol_boringssl_get_output_frames(1301) [C3.1:2][0x10163a2a0] get output frames failed, state 8196
2019-03-18 21:00:06.330027-0500 Tracktive[16337:621130] TIC Read Status [3:0x0]: 1:57
2019-03-18 21:00:06.330050-0500 Tracktive[16337:621130] TIC Read Status [3:0x0]: 1:57
2019-03-18 21:00:06.334273-0500 Tracktive[16337:621164] [logging-persist] cannot open file at line 42263 of [95fbac39ba]
2019-03-18 21:00:06.334293-0500 Tracktive[16337:621164] [logging-persist] os_unix.c:42263: (0) open(/var/db/DetachedSignatures) - Undefined error: 0
2019-03-18 21:00:06.335076-0500 Tracktive[16337:621164] [logging-persist] cannot open file at line 42263 of [95fbac39ba]
2019-03-18 21:00:06.335087-0500 Tracktive[16337:621164] [logging-persist] os_unix.c:42263: (0) open(/var/db/DetachedSignatures) - Undefined error: 0

I have no idea what these mean and nor does google. My app is NOT sandboxed, if that is relevant.
I'm afraid I'm going to be another one of those "Wish I hadn't chose Firebase" bloggers soon.

See https://github.com/firebase/firebase-ios-sdk/issues/2188#issuecomment-467115665

I appreciate the link but the problem is no, things arent working normally.
Ive seen BoringSSL chattiness before but not so many errors.
The issue is fir example i call the signing method and it spits oit those errors and never calls the conpletion.
The JS SDK works.

@jhoughjr Please stop add non-constructive, snarky comments to other issues. If you have something tangible to add to shed further light on your issue, please add it here.
Also note that Firebase OSX support is documented to be community supported and is on a best-effort basis from the Firebase team.

@jhoughjr Are you using https://cocoapods.org/pods/FirebaseOSX versus the Firebase OSX support documented in this repo?

Which ones are the latest, official known to work docs? I've tried both as well as my own creative solutions to no avail.
The closest I've gotten yielded the errors above.

The FirebaseOSX pod dates from early 2016 and only includes the Firebase Real-time Database.  It will likely soon be deprecated.
The docs in this pod are expected to work for the scope defined. However, as noted, OSX support is not currently officially supported.
The more information you can share about install configuration and reproducibility increases the likelihood of a quicker resolution.

Digging through issues and PRs I've found:https://github.com/firebase/firebase-ios-sdk/pull/2241
Says on the tin it will do what I need, so I'll try that.
Build config is a developer ID non sandboxed app using the old build system.
Using cocoapods.
Xcode 10, Swift 4.2 on macOS 10.14.
Firebase is the only external dependency.
Where are the docs for the procedure I should be using?
In lieu of docs I'll try whats listed in that PR, as its been merged.

Thanks.  To be clear, the is the Firebase pod does not support for OSX.  FirebaseAuth, FirebaseCore, FirebaseDatabase, FirebaseFirestore, FirebaseFunctions and FirebaseStorage CocoaPods are available.

Auth and Firestore are all I think i need.
I cloned the repo but i don't see the :
[Firestore/README.md](Firestore/README.md) and
[Functions/README.md](Functions/README.md).

in firebase-ios-sdk. Are those different repos or is it under my nose?

Both are in this repo, but you shouldn't need to clone since they're published to CocoaPods master. It's sufficient to add the following to the Podfile:
pod 'FirebaseAuth'
pod 'FirebaseFirestore'

Everything seems to be working ok now. Seeing some BoringSSL errors, but auth works.
Thanks for bearing with an autist and guiding me to the solution.
I'm not so sure what is different in my config that what I tried before,
(erhaps not having firestore pod and my app using it on the backend) but I'm gald it works.
Closing the issue.

Note that the BoringSSL output you're seeing is actually coming from iOS and is a result of the underlying sockets we're using being very chatty. There's plenty of discussion about these messages elsewhere.
https://stackoverflow.com/questions/46352735/what-is-tic-read-status-157-in-ios11-xcode-9
You can safely ignore these.

Maybe so, but I am seeing SSL errors.
Just as in this https://github.com/firebase/firebase-ios-sdk/issues/1661
https://stackoverflow.com/questions/55261199/firestore-internal-assertion-failed-could-not-load-root-certificates-from-the-b#_=_
So I can auth, but not actually use the Firestore. I'm going to try and step down the pod version until it works since that is what was indicated in the issue thread i found form the SO post.
Any advice? I've tried disabling SSL and changing the url in the plist. I also tried explicitly adding the bundle to copy resources for the app target.

As described in the other issue, you need to ensure that the gRPCCertificates.bundle is a part of your app.
We do have some logging you can enable that could shed some light on what it's trying to find. Can you post the actual error message you're seeing?

I was able to trace it to the user token refresh.
Trying Firestore from git master yields the same errors,:
2019-03-21 11:32:38.936089-0500 Tracktive[65303:1647287] [BoringSSL] nw_protocol_boringssl_get_output_frames(1301) [C2.1:2][0x102959cf0] get output frames failed, state 8196
2019-03-21 11:32:38.936236-0500 Tracktive[65303:1647287] TIC Read Status [2:0x0]: 1:57
2019-03-21 11:32:38.936248-0500 Tracktive[65303:1647287] TIC Read Status [2:0x0]: 1:57
2019-03-21 11:32:51.321702-0500 Tracktive[65303:1646500] [BoringSSL] nw_protocol_boringssl_get_output_frames(1301) [C3.1:2][0x102c34470] get output frames failed, state 8196
2019-03-21 11:32:51.321745-0500 Tracktive[65303:1646500] [BoringSSL] nw_protocol_boringssl_get_output_frames(1301) [C3.1:2][0x102c34470] get output frames failed, state 8196
2019-03-21 11:32:51.321920-0500 Tracktive[65303:1646500] TIC Read Status [3:0x0]: 1:57
2019-03-21 11:32:51.321938-0500 Tracktive[65303:1646500] TIC Read Status [3:0x0]: 1:57
2019-03-21 11:32:51.586393-0500 Tracktive[65303:1646467] [BoringSSL] nw_protocol_boringssl_get_output_frames(1301) [C4.1:2][0x102b44e50] get output frames failed, state 8196
2019-03-21 11:32:51.586437-0500 Tracktive[65303:1646467] [BoringSSL] nw_protocol_boringssl_get_output_frames(1301) [C4.1:2][0x102b44e50] get output frames failed, state 8196
2019-03-21 11:32:51.586577-0500 Tracktive[65303:1646467] TIC Read Status [4:0x0]: 1:57
2019-03-21 11:32:51.586597-0500 Tracktive[65303:1646467] TIC Read Status [4:0x0]: 1:57
2019-03-21 11:32:51.591574-0500 Tracktive[65303:1646500] [logging-persist] cannot open file at line 42263 of [95fbac39ba]
2019-03-21 11:32:51.591591-0500 Tracktive[65303:1646500] [logging-persist] os_unix.c:42263: (0) open(/var/db/DetachedSignatures) - Undefined error: 0
sending event ["email": "", "timestamp": "2019-03-21T16:33:05Z", "place": ["long": -92.65272160045807, "alt":<PHONE_NUMBER>1171875, "lat": 37.67016915322354], "type": "active"]
2019-03-21 11:33:05.373995-0500 Tracktive[65303:1647287] *** Assertion failure in std::string firebase::firestore::remote::LoadGrpcRootCertificate()(), /Users/jimmyhoughjr/workspace/ghostnoteapp/mac/tracktivity-osx-client/Tracktive/Pods/FirebaseFirestore/Firestore/core/src/firebase/firestore/remote/grpc_root_certificate_finder_apple.mm:80
2019-03-21 11:33:05.375670-0500 Tracktive[65303:1647287] [General] An uncaught exception was raised
2019-03-21 11:33:05.375684-0500 Tracktive[65303:1647287] [General] FIRESTORE INTERNAL ASSERTION FAILED: Could not load root certificates from the bundle. SSL cannot work. (expected path)
2019-03-21 11:33:05.375749-0500 Tracktive[65303:1647287] [General] (
	0   CoreFoundation                      0x00007fff42730ded __exceptionPreprocess + 256
	1   libobjc.A.dylib                     0x00007fff6e7fc720 objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff4274ba4a +[NSException raise:format:arguments:] + 98
	3   Foundation                          0x00007fff44b3eeed -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:] + 166
	4   Tracktive                           0x0000000100275f55 _ZN8firebase9firestore4util8internal4FailEPKcS4_iRKNSt3__112basic_stringIcNS5_11char_traitsIcEENS5_9allocatorIcEEEE + 533
	5   Tracktive                           0x0000000100276612 _ZN8firebase9firestore4util8internal4FailEPKcS4_iRKNSt3__112basic_stringIcNS5_11char_traitsIcEENS5_9allocatorIcEEEES4_ + 1538
	6   Tracktive                           0x000000010025afb6 _ZN8firebase9firestore6remote23LoadGrpcRootCertificateEv + 118
	7   Tracktive                           0x000000010024cc00 _ZNK8firebase9firestore6remote14GrpcConnection13CreateChannelEv + 96
	8   Tracktive                           0x000000010024c71b _ZN8firebase9firestore6remote14GrpcConnection16EnsureActiveStubEv + 267
	9   Tracktive                           0x000000010024f375 _ZN8firebase9firestore6remote14GrpcConnection12CreateStreamEN4absl11string_viewERKNS0_4auth5TokenEPNS1_18GrpcStreamObserverE + 85
	10  Tracktive                           0x000000010034f315 _ZN8firebase9firestore6remote11WriteStream16CreateGrpcStreamEPNS1_14GrpcConnectionERKNS0_4auth5TokenE + 101
	11  Tracktive                           0x000000010031848f _ZN8firebase9firestore6remote6Stream26ResumeStartWithCredentialsERKNS0_4util8StatusOrINS0_4auth5TokenEEE + 351
	12  Tracktive                           0x000000010031cd8e _ZZZN8firebase9firestore6remote6Stream18RequestCredentialsEvENK3$_0clERKNS0_4util8StatusOrINS0_4auth5TokenEEEENKUlvE_clEv + 142
	13  Tracktive                           0x000000010031cced _ZNSt3__128__invoke_void_return_wrapperIvE6__callIJRZZN8firebase9firestore6remote6Stream18RequestCredentialsEvENK3$_0clERKNS4_4util8StatusOrINS4_4auth5TokenEEEEUlvE_EEEvDpOT_ + 45
	14  Tracktive                           0x000000010031c9b9 _ZNSt3__110__function6__funcIZZN8firebase9firestore6remote6Stream18RequestCredentialsEvENK3$_0clERKNS3_4util8StatusOrINS3_4auth5TokenEEEEUlvE_NS_9allocatorISE_EEFvvEEclEv + 41
	15  Tracktive                           0x0000000100134546 _ZNKSt3__18functionIFvvEEclEv + 102
	16  Tracktive                           0x0000000100065ece _ZN8firebase9firestore4util10AsyncQueue15ExecuteBlockingERKNSt3__18functionIFvvEEE + 478
	17  Tracktive                           0x0000000100068a57 _ZZN8firebase9firestore4util10AsyncQueue4WrapERKNSt3__18functionIFvvEEEENK3$_0clEv + 39
	18  Tracktive                           0x0000000100068a1d _ZNSt3__128__invoke_void_return_wrapperIvE6__callIJRZN8firebase9firestore4util10AsyncQueue4WrapERKNS_8functionIFvvEEEE3$_0EEEvDpOT_ + 45
	19  Tracktive                           0x00000001000687d9 _ZNSt3__110__function6__funcIZN8firebase9firestore4util10AsyncQueue4WrapERKNS_8functionIFvvEEEE3$_0NS_9allocatorISB_EES7_EclEv + 41
	20  Tracktive                           0x0000000100134546 _ZNKSt3__18functionIFvvEEclEv + 102
	21  Tracktive                           0x00000001000a9221 _ZZN8firebase9firestore4util8internal13DispatchAsyncEPU28objcproto17OS_dispatch_queue8NSObjectONSt3__18functionIFvvEEEENK3$_0clEPv + 33
	22  Tracktive                           0x00000001000a91f8 _ZZN8firebase9firestore4util8internal13DispatchAsyncEPU28objcproto17OS_dispatch_queue8NSObjectONSt3__18functionIFvvEEEEN3$_08__invokeEPv + 24
	23  libdispatch.dylib                   0x00000001026287c3 _dispatch_client_callout + 8
	24  libdispatch.dylib                   0x00000001026309c7 _dispatch_lane_serial_drain + 789
	25  libdispatch.dylib                   0x000000010263187e _dispatch_lane_invoke + 446
	26  libdispatch.dylib                   0x000000010263cf44 _dispatch_workloop_worker_thread + 691
	27  libsystem_pthread.dylib             0x00000001026a3047 _pthread_wqthread + 409
	28  libsystem_pthread.dylib             0x00000001026a2e41 start_wqthread + 13
)
2019-03-21 11:33:05.376968-0500 Tracktive[65303:1647287] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'FIRESTORE INTERNAL ASSERTION FAILED: Could not load root certificates from the bundle. SSL cannot work. (expected path)'
*** First throw call stack:
(
	0   CoreFoundation                      0x00007fff42730ded __exceptionPreprocess + 256
	1   libobjc.A.dylib                     0x00007fff6e7fc720 objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff4274ba4a +[NSException raise:format:arguments:] + 98
	3   Foundation                          0x00007fff44b3eeed -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:] + 166
	4   Tracktive                           0x0000000100275f55 _ZN8firebase9firestore4util8internal4FailEPKcS4_iRKNSt3__112basic_stringIcNS5_11char_traitsIcEENS5_9allocatorIcEEEE + 533
	5   Tracktive                           0x0000000100276612 _ZN8firebase9firestore4util8internal4FailEPKcS4_iRKNSt3__112basic_stringIcNS5_11char_traitsIcEENS5_9allocatorIcEEEES4_ + 1538
	6   Tracktive                           0x000000010025afb6 _ZN8firebase9firestore6remote23LoadGrpcRootCertificateEv + 118
	7   Tracktive                           0x000000010024cc00 _ZNK8firebase9firestore6remote14GrpcConnection13CreateChannelEv + 96
	8   Tracktive                           0x000000010024c71b _ZN8firebase9firestore6remote14GrpcConnection16EnsureActiveStubEv + 267
	9   Tracktive                           0x000000010024f375 _ZN8firebase9firestore6remote14GrpcConnection12CreateStreamEN4absl11string_viewERKNS0_4auth5TokenEPNS1_18GrpcStreamObserverE + 85
	10  Tracktive                           0x000000010034f315 _ZN8firebase9firestore6remote11WriteStream16CreateGrpcStreamEPNS1_14GrpcConnectionERKNS0_4auth5TokenE + 101
	11  Tracktive                           0x000000010031848f _ZN8firebase9firestore6remote6Stream26ResumeStartWithCredentialsERKNS0_4util8StatusOrINS0_4auth5TokenEEE + 351
	12  Tracktive                           0x000000010031cd8e _ZZZN8firebase9firestore6remote6Stream18RequestCredentialsEvENK3$_0clERKNS0_4util8StatusOrINS0_4auth5TokenEEEENKUlvE_clEv + 142
	13  Tracktive                           0x000000010031cced _ZNSt3__128__invoke_void_return_wrapperIvE6__callIJRZZN8firebase9firestore6remote6Stream18RequestCredentialsEvENK3$_0clERKNS4_4util8StatusOrINS4_4auth5TokenEEEEUlvE_EEEvDpOT_ + 45
	14  Tracktive                           0x000000010031c9b9 _ZNSt3__110__function6__funcIZZN8firebase9firestore6remote6Stream18RequestCredentialsEvENK3$_0clERKNS3_4util8StatusOrINS3_4auth5TokenEEEEUlvE_NS_9allocatorISE_EEFvvEEclEv + 41
	15  Tracktive                           0x0000000100134546 _ZNKSt3__18functionIFvvEEclEv + 102
	16  Tracktive                           0x0000000100065ece _ZN8firebase9firestore4util10AsyncQueue15ExecuteBlockingERKNSt3__18functionIFvvEEE + 478
	17  Tracktive                           0x0000000100068a57 _ZZN8firebase9firestore4util10AsyncQueue4WrapERKNSt3__18functionIFvvEEEENK3$_0clEv + 39
	18  Tracktive                           0x0000000100068a1d _ZNSt3__128__invoke_void_return_wrapperIvE6__callIJRZN8firebase9firestore4util10AsyncQueue4WrapERKNS_8functionIFvvEEEE3$_0EEEvDpOT_ + 45
	19  Tracktive                           0x00000001000687d9 _ZNSt3__110__function6__funcIZN8firebase9firestore4util10AsyncQueue4WrapERKNS_8functionIFvvEEEE3$_0NS_9allocatorISB_EES7_EclEv + 41
	20  Tracktive                           0x0000000100134546 _ZNKSt3__18functionIFvvEEclEv + 102
	21  Tracktive                           0x00000001000a9221 _ZZN8firebase9firestore4util8internal13DispatchAsyncEPU28objcproto17OS_dispatch_queue8NSObjectONSt3__18functionIFvvEEEENK3$_0clEPv + 33
	22  Tracktive                           0x00000001000a91f8 _ZZN8firebase9firestore4util8internal13DispatchAsyncEPU28objcproto17OS_dispatch_queue8NSObjectONSt3__18functionIFvvEEEEN3$_08__invokeEPv + 24
	23  libdispatch.dylib                   0x00000001026287c3 _dispatch_client_callout + 8
	24  libdispatch.dylib                   0x00000001026309c7 _dispatch_lane_serial_drain + 789
	25  libdispatch.dylib                   0x000000010263187e _dispatch_lane_invoke + 446
	26  libdispatch.dylib                   0x000000010263cf44 _dispatch_workloop_worker_thread + 691
	27  libsystem_pthread.dylib             0x00000001026a3047 _pthread_wqthread + 409
	28  libsystem_pthread.dylib             0x00000001026a2e41 start_wqthread + 13
)
libc++abi.dylib: terminating with uncaught exception of type NSException
(lldb)

I have verified in a build that has the same errors as above that
gRPCCertificates.bunlde is in my app product in the grpcpp framework.

Just adding that I see these errors on auth, though it appears to sign in normally
2019-03-21 11:55:56.852603-0500 Tracktive[70382:1741025] [logging-persist] cannot open file at line 42263 of [95fbac39ba]
2019-03-21 11:55:56.852620-0500 Tracktive[70382:1741025] [logging-persist] os_unix.c:42263: (0) open(/var/db/DetachedSignatures) - Undefined error: 0

Here is the eror with firebase logging enabled
019-03-21 11:55:56.852620-0500 Tracktive[70382:1741025] [logging-persist] os_unix.c:42263: (0) open(/var/db/DetachedSignatures) - Undefined error: 0
sending event ["place": ["alt":<PHONE_NUMBER>386719, "lat": 37.67014633351815, "long": -92.65257419546845], "email": "", "timestamp": "2019-03-21T16:57:03Z", "type": "active"]
2019-03-21 11:57:03.777444-0500 Tracktive[70382:1744098] 5.19.0 - [Firebase/Firestore][I-FST000001] Initializing. Current user: 4046ZCQ1dbXqqiKRYf0SMtDDktH3
2019-03-21 11:57:03.786341-0500 Tracktive[70382:1744180] 5.19.0 - [Firebase/Firestore][I-FST000001] Committing transaction: <LevelDbTransaction Start LevelDB: 0 changes (0 bytes):>
2019-03-21 11:57:03.790084-0500 Tracktive[70382:1744098] 5.19.0 - [Firebase/Firestore][I-FST000001] Committing transaction: <LevelDbTransaction Start MutationQueue: 0 changes (0 bytes):>
2019-03-21 11:57:03.816463-0500 Tracktive[70382:1744098] 5.19.0 - [Firebase/Firestore][I-FST000001] Committing transaction: <LevelDbTransaction NextMutationBatchAfterBatchID: 0 changes (0 bytes):>
2019-03-21 11:57:03.816761-0500 Tracktive[70382:1744098] 5.19.0 - [Firebase/Firestore][I-FST000001] Committing transaction: <LevelDbTransaction NextMutationBatchAfterBatchID: 0 changes (0 bytes):>
2019-03-21 11:57:03.816942-0500 Tracktive[70382:1744098] 5.19.0 - [Firebase/Firestore][I-FST000001] Committing transaction: <LevelDbTransaction NextMutationBatchAfterBatchID: 0 changes (0 bytes):>
2019-03-21 11:57:03.817191-0500 Tracktive[70382:1744098] 5.19.0 - [Firebase/Firestore][I-FST000001] Committing transaction: <LevelDbTransaction NextMutationBatchAfterBatchID: 0 changes (0 bytes):>
2019-03-21 11:57:03.817426-0500 Tracktive[70382:1744098] 5.19.0 - [Firebase/Firestore][I-FST000001] Committing transaction: <LevelDbTransaction NextMutationBatchAfterBatchID: 0 changes (0 bytes):>
2019-03-21 11:57:03.817610-0500 Tracktive[70382:1744098] 5.19.0 - [Firebase/Firestore][I-FST000001] Committing transaction: <LevelDbTransaction NextMutationBatchAfterBatchID: 0 changes (0 bytes):>
2019-03-21 11:57:03.817906-0500 Tracktive[70382:1744098] 5.19.0 - [Firebase/Firestore][I-FST000001] Committing transaction: <LevelDbTransaction NextMutationBatchAfterBatchID: 0 changes (0 bytes):>
2019-03-21 11:57:03.818147-0500 Tracktive[70382:1744098] 5.19.0 - [Firebase/Firestore][I-FST000001] Committing transaction: <LevelDbTransaction NextMutationBatchAfterBatchID: 0 changes (0 bytes):>
2019-03-21 11:57:03.818330-0500 Tracktive[70382:1744098] 5.19.0 - [Firebase/Firestore][I-FST000001] Committing transaction: <LevelDbTransaction NextMutationBatchAfterBatchID: 0 changes (0 bytes):>
2019-03-21 11:57:03.818503-0500 Tracktive[70382:1744098] 5.19.0 - [Firebase/Firestore][I-FST000001] Committing transaction: <LevelDbTransaction NextMutationBatchAfterBatchID: 0 changes (0 bytes):>
2019-03-21 11:57:03.818625-0500 Tracktive[70382:1744098] 5.19.0 - [Firebase/Firestore][I-FST000001] WriteStream (10402cec0) start
2019-03-21 11:57:03.818797-0500 Tracktive[70382:1744098] 5.19.0 - [Firebase/Auth][I-AUT000002] Token auto-refresh enabled.
2019-03-21 11:57:03.818811-0500 Tracktive[70382:1744098] 5.19.0 - [Firebase/Auth][I-AUT000004] Token auto-refresh scheduled in 53:53 for the new token.
2019-03-21 11:57:03.820210-0500 Tracktive[70382:1744098] 5.19.0 - [Firebase/Firestore][I-FST000001] Committing transaction: <LevelDbTransaction Locally write mutations: 3 changes (255 bytes):
  - Put [collection_parent: collection_id=events] (0 bytes)
  - Put [document_mutation: user_id=4046ZCQ1dbXqqiKRYf0SMtDDktH3 path=events/RlbmTky74R9qT4PdeYln batch_id=13] (0 bytes)
  - Put [mutation: user_id=4046ZCQ1dbXqqiKRYf0SMtDDktH3 batch_id=13] (255 bytes)>
2019-03-21 11:57:03.820391-0500 Tracktive[70382:1744098] 5.19.0 - [Firebase/Firestore][I-FST000001] Committing transaction: <LevelDbTransaction NotifyLocalViewChanges: 0 changes (0 bytes):>
2019-03-21 11:57:03.820493-0500 Tracktive[70382:1744098] 5.19.0 - [Firebase/Firestore][I-FST000001] Creating Firestore stub.
2019-03-21 11:57:03.821863-0500 Tracktive[70382:1744098] 5.19.0 - [Firebase/Firestore][I-FST000001] gRPCCertificates.bundle/roots.pem not found in bundle org.cocoapods.grpcpp
2019-03-21 11:57:03.822142-0500 Tracktive[70382:1744098] 5.19.0 - [Firebase/Firestore][I-FST000001] roots.pem not found in bundle org.cocoapods.grpcpp
2019-03-21 11:57:03.822177-0500 Tracktive[70382:1744098] 5.19.0 - [Firebase/Firestore][I-FST000001] gRPCCertificates.bundle/roots.pem not found in bundle com.firstprinciple.tractivity
2019-03-21 11:57:03.822188-0500 Tracktive[70382:1744098] 5.19.0 - [Firebase/Firestore][I-FST000001] roots.pem not found in bundle com.firstprinciple.tractivity
2019-03-21 11:57:03.822223-0500 Tracktive[70382:1741025] *** Assertion failure in std::string firebase::firestore::remote::LoadGrpcRootCertificate()(), /Users/jimmyhoughjr/workspace/ghostnoteapp/mac/tracktivity-osx-client/Tracktive/Pods/FirebaseFirestore/Firestore/core/src/firebase/firestore/remote/grpc_root_certificate_finder_apple.mm:80
2019-03-21 11:57:03.823759-0500 Tracktive[70382:1741025] [General] An uncaught exception was raised
2019-03-21 11:57:03.823773-0500 Tracktive[70382:1741025] [General] FIRESTORE INTERNAL ASSERTION FAILED: Could not load root certificates from the bundle. SSL cannot work. (expected path)
2019-03-21 11:57:03.823843-0500 Tracktive[70382:1741025] [General] (
	0   CoreFoundation                      0x00007fff42730ded __exceptionPreprocess + 256
	1   libobjc.A.dylib                     0x00007fff6e7fc720 objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff4274ba4a +[NSException raise:format:arguments:] + 98
	3   Foundation                          0x00007fff44b3eeed -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:] + 166
	4   Tracktive                           0x0000000100269965 _ZN8firebase9firestore4util8internal4FailEPKcS4_iRKNSt3__112basic_stringIcNS5_11char_traitsIcEENS5_9allocatorIcEEEE + 533
	5   Tracktive                           0x000000010026a022 _ZN8firebase9firestore4util8internal4FailEPKcS4_iRKNSt3__112basic_stringIcNS5_11char_traitsIcEENS5_9allocatorIcEEEES4_ + 1538
	6   Tracktive                           0x000000010024e9c6 _ZN8firebase9firestore6remote23LoadGrpcRootCertificateEv + 118
	7   Tracktive                           0x0000000100240610 _ZNK8firebase9firestore6remote14GrpcConnection13CreateChannelEv + 96
	8   Tracktive                           0x000000010024012b _ZN8firebase9firestore6remote14GrpcConnection16EnsureActiveStubEv + 267
	9   Tracktive                           0x0000000100242d85 _ZN8firebase9firestore6remote14GrpcConnection12CreateStreamEN4absl11string_viewERKNS0_4auth5TokenEPNS1_18GrpcStreamObserverE + 85
	10  Tracktive                           0x000000010033c175 _ZN8firebase9firestore6remote11WriteStream16CreateGrpcStreamEPNS1_14GrpcConnectionERKNS0_4auth5TokenE + 101
	11  Tracktive                           0x00000001003051ff _ZN8firebase9firestore6remote6Stream26ResumeStartWithCredentialsERKNS0_4util8StatusOrINS0_4auth5TokenEEE + 351
	12  Tracktive                           0x0000000100309afe _ZZZN8firebase9firestore6remote6Stream18RequestCredentialsEvENK3$_0clERKNS0_4util8StatusOrINS0_4auth5TokenEEEENKUlvE_clEv + 142
	13  Tracktive                           0x0000000100309a5d _ZNSt3__128__invoke_void_return_wrapperIvE6__callIJRZZN8firebase9firestore6remote6Stream18RequestCredentialsEvENK3$_0clERKNS4_4util8StatusOrINS4_4auth5TokenEEEEUlvE_EEEvDpOT_ + 45
	14  Tracktive                           0x0000000100309729 _ZNSt3__110__function6__funcIZZN8firebase9firestore6remote6Stream18RequestCredentialsEvENK3$_0clERKNS3_4util8StatusOrINS3_4auth5TokenEEEEUlvE_NS_9allocatorISE_EEFvvEEclEv + 41
	15  Tracktive                           0x000000010012f136 _ZNKSt3__18functionIFvvEEclEv + 102
	16  Tracktive                           0x000000010006617e _ZN8firebase9firestore4util10AsyncQueue15ExecuteBlockingERKNSt3__18functionIFvvEEE + 478
	17  Tracktive                           0x0000000100068d07 _ZZN8firebase9firestore4util10AsyncQueue4WrapERKNSt3__18functionIFvvEEEENK3$_0clEv + 39
	18  Tracktive                           0x0000000100068ccd _ZNSt3__128__invoke_void_return_wrapperIvE6__callIJRZN8firebase9firestore4util10AsyncQueue4WrapERKNS_8functionIFvvEEEE3$_0EEEvDpOT_ + 45
	19  Tracktive                           0x0000000100068a89 _ZNSt3__110__function6__funcIZN8firebase9firestore4util10AsyncQueue4WrapERKNS_8functionIFvvEEEE3$_0NS_9allocatorISB_EES7_EclEv + 41
	20  Tracktive                           0x000000010012f136 _ZNKSt3__18functionIFvvEEclEv + 102
	21  Tracktive                           0x00000001000a7231 _ZZN8firebase9firestore4util8internal13DispatchAsyncEPU28objcproto17OS_dispatch_queue8NSObjectONSt3__18functionIFvvEEEENK3$_0clEPv + 33
	22  Tracktive                           0x00000001000a7208 _ZZN8firebase9firestore4util8internal13DispatchAsyncEPU28objcproto17OS_dispatch_queue8NSObjectONSt3__18functionIFvvEEEEN3$_08__invokeEPv + 24
	23  libdispatch.dylib                   0x00000001025ef7c3 _dispatch_client_callout + 8
	24  libdispatch.dylib                   0x00000001025f79c7 _dispatch_lane_serial_drain + 789
	25  libdispatch.dylib                   0x00000001025f887e _dispatch_lane_invoke + 446
	26  libdispatch.dylib                   0x0000000102603f44 _dispatch_workloop_worker_thread + 691
	27  libsystem_pthread.dylib             0x000000010266a047 _pthread_wqthread + 409
	28  libsystem_pthread.dylib             0x0000000102669e41 start_wqthread + 13
)
2019-03-21 11:57:03.824692-0500 Tracktive[70382:1741025] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'FIRESTORE INTERNAL ASSERTION FAILED: Could not load root certificates from the bundle. SSL cannot work. (expected path)'
*** First throw call stack:
(
	0   CoreFoundation                      0x00007fff42730ded __exceptionPreprocess + 256
	1   libobjc.A.dylib                     0x00007fff6e7fc720 objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff4274ba4a +[NSException raise:format:arguments:] + 98
	3   Foundation                          0x00007fff44b3eeed -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:] + 166
	4   Tracktive                           0x0000000100269965 _ZN8firebase9firestore4util8internal4FailEPKcS4_iRKNSt3__112basic_stringIcNS5_11char_traitsIcEENS5_9allocatorIcEEEE + 533
	5   Tracktive                           0x000000010026a022 _ZN8firebase9firestore4util8internal4FailEPKcS4_iRKNSt3__112basic_stringIcNS5_11char_traitsIcEENS5_9allocatorIcEEEES4_ + 1538
	6   Tracktive                           0x000000010024e9c6 _ZN8firebase9firestore6remote23LoadGrpcRootCertificateEv + 118
	7   Tracktive                           0x0000000100240610 _ZNK8firebase9firestore6remote14GrpcConnection13CreateChannelEv + 96
	8   Tracktive                           0x000000010024012b _ZN8firebase9firestore6remote14GrpcConnection16EnsureActiveStubEv + 267
	9   Tracktive                           0x0000000100242d85 _ZN8firebase9firestore6remote14GrpcConnection12CreateStreamEN4absl11string_viewERKNS0_4auth5TokenEPNS1_18GrpcStreamObserverE + 85
	10  Tracktive                           0x000000010033c175 _ZN8firebase9firestore6remote11WriteStream16CreateGrpcStreamEPNS1_14GrpcConnectionERKNS0_4auth5TokenE + 101
	11  Tracktive                           0x00000001003051ff _ZN8firebase9firestore6remote6Stream26ResumeStartWithCredentialsERKNS0_4util8StatusOrINS0_4auth5TokenEEE + 351
	12  Tracktive                           0x0000000100309afe _ZZZN8firebase9firestore6remote6Stream18RequestCredentialsEvENK3$_0clERKNS0_4util8StatusOrINS0_4auth5TokenEEEENKUlvE_clEv + 142
	13  Tracktive                           0x0000000100309a5d _ZNSt3__128__invoke_void_return_wrapperIvE6__callIJRZZN8firebase9firestore6remote6Stream18RequestCredentialsEvENK3$_0clERKNS4_4util8StatusOrINS4_4auth5TokenEEEEUlvE_EEEvDpOT_ + 45
	14  Tracktive                           0x0000000100309729 _ZNSt3__110__function6__funcIZZN8firebase9firestore6remote6Stream18RequestCredentialsEvENK3$_0clERKNS3_4util8StatusOrINS3_4auth5TokenEEEEUlvE_NS_9allocatorISE_EEFvvEEclEv + 41
	15  Tracktive                           0x000000010012f136 _ZNKSt3__18functionIFvvEEclEv + 102
	16  Tracktive                           0x000000010006617e _ZN8firebase9firestore4util10AsyncQueue15ExecuteBlockingERKNSt3__18functionIFvvEEE + 478
	17  Tracktive                           0x0000000100068d07 _ZZN8firebase9firestore4util10AsyncQueue4WrapERKNSt3__18functionIFvvEEEENK3$_0clEv + 39
	18  Tracktive                           0x0000000100068ccd _ZNSt3__128__invoke_void_return_wrapperIvE6__callIJRZN8firebase9firestore4util10AsyncQueue4WrapERKNS_8functionIFvvEEEE3$_0EEEvDpOT_ + 45
	19  Tracktive                           0x0000000100068a89 _ZNSt3__110__function6__funcIZN8firebase9firestore4util10AsyncQueue4WrapERKNS_8functionIFvvEEEE3$_0NS_9allocatorISB_EES7_EclEv + 41
	20  Tracktive                           0x000000010012f136 _ZNKSt3__18functionIFvvEEclEv + 102
	21  Tracktive                           0x00000001000a7231 _ZZN8firebase9firestore4util8internal13DispatchAsyncEPU28objcproto17OS_dispatch_queue8NSObjectONSt3__18functionIFvvEEEENK3$_0clEPv + 33
	22  Tracktive                           0x00000001000a7208 _ZZN8firebase9firestore4util8internal13DispatchAsyncEPU28objcproto17OS_dispatch_queue8NSObjectONSt3__18functionIFvvEEEEN3$_08__invokeEPv + 24
	23  libdispatch.dylib                   0x00000001025ef7c3 _dispatch_client_callout + 8
	24  libdispatch.dylib                   0x00000001025f79c7 _dispatch_lane_serial_drain + 789
	25  libdispatch.dylib                   0x00000001025f887e _dispatch_lane_invoke + 446
	26  libdispatch.dylib                   0x0000000102603f44 _dispatch_workloop_worker_thread + 691
	27  libsystem_pthread.dylib             0x000000010266a047 _pthread_wqthread + 409
	28  libsystem_pthread.dylib             0x0000000102669e41 start_wqthread + 13
)
libc++abi.dylib: terminating with uncaught exception of type NSException
(lldb)

I see it says the bundle is not there but i can see it is there in finder in the built product.

OK. I think we've abused this original issue long enough. I've created #2604 specifically to track the certificate loading issue on macOS. Let's continue discussion on this there.

The FirebaseOSX pod is now deprecated in favor of the Firebase* pods from this repo.


fix ffi::clear_area call

Pass down width and height to clear_area instead of bottom right corner coordinates.
see clear_area.

Released in v1.3.3

Thanks for getting to this quickly and for this nice set of bindings!

You got it fam :fingerguns:


Add option to change the tolerance for the complex-conjugate check.

Codecov Report

Merging #88 into dev will decrease coverage by 0.09%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              dev      #88      +/-   ##
==========================================
- Coverage   99.05%   98.96%   -0.10%
==========================================
  Files          11       11
  Lines        1063     1060       -3
==========================================
- Hits         1053     1049       -4
- Misses         10       11       +1

Impacted Files
Coverage Δ

tbmodels/_tb_model.py
98.64% <100.00%> (-0.13%)
:arrow_down:

Continue to review full report at Codecov.

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


Fix tests, add code coverage reports

Fix tests by excluding ServletTestExecutionListener, DirtiesContextTestExecutionListener, TransactionalTestExecutionListener, SqlScriptsTestExecutionListener from TestExecutionListeners\
Add jacoco and cobertura test coverage, nicer test console output, html reports

Spring4 Test framework can't instantiate some of the default test listeners since they aren't on the classpath.  ServletTestExecutionListener and TransactionalTestExecutionListener in particular cause problems. The other ones I excluded aren't harmful, but aren't needed.
I used your example as the basis of my project, so I thought I'd backport my fixes to your example. Thanks for helping me out by having shared this project.

Thanks Steve!
That was the reason to create example - to help setting up Groovy-based projects.

Steve, I had an intention to switch license of this project to public domain, so that people do not have any troubles in reusing this code in own projects. But seems there are still remnants of Apache 2 license remaining. Will it be okay with you if I will clean up Apache 2 remnants and leave only public domain license?

Sure. I hereby give you permission to change the license to whatever you like now or in the future. :)
Thanks again for sharing something that helped me out when I needed it.

Thanks Steve!


Sensitive info is displayed on screen

See https://github.com/chef/chef/issues/5695 for more details

This could go away, I think, withwindows autologon utility https://docs.microsoft.com/en-us/sysinternals/downloads/autologon.  See tools\chocolateyInstall.ps1 in https://chocolatey.org/packages/autologon for an example of how to do this.

I think it would be better to use autologon:  https://docs.microsoft.com/en-us/sysinternals/downloads/autologon
This is more secure since is doesn't expose password in registry.


Future of repo + maintenance

Hi there, I noticed there hasnt been an update in ~2.5 yrs. What is the plan/intention for maintenance of this repo?

There's an official github fork that look much more recently maintained. We will be switching to that one.
https://github.com/github/s3gof3r


Fixed deploy stage condition in travis .yml

Fixes https://github.com/eclipse/repairnator/issues/1076
Signed-off-by: Javier Ron<EMAIL_ADDRESS>

Thanks a lot! Merging is the ultimate test here!


Inconsistent Naming

Describe the Bug
This isn't a bug as such, but I've noticed some inconsistent naming around shelves.
When creating shelves the copy reads "Create New Shelf". The item in the navigation bar reads "Shelves".
However when editing shelves the copy reads "Edit Bookshelf". The same is true for deleting as the copy reads "Delete Bookshelf".
I think it would be good to standardise on one name for shelves on the frontend. As a new user it was slightly jarring to be presented with two terms for the same thing. Either "Bookshelf" or "Shelf" is fine, but I think being consistent is important.
Steps to Reproduce
See above.
Expected Behaviour
See above.
Screenshots or Additional Context
No response
Browser Details
No response
Exact BookStack Version
N/A
PHP Version
No response
Hosting Environment
N/A

So what is the proposed wording, "Bookshelf" or just "Shelf"

I assume that question is for @ssddanbrown, but I'm happy to share my opinion if it helps:
I would propose using the word "Shelf". I think it's clear that in the context of BookStack a shelf would only contain books.
It's also a shorter word! :)

Thanks for raising @tyfai.
Have aligned the term to be "Shelf" in commit 9da3130a12301c9b2cc52a3bb6ada2d65a66c106.
Might take a while for non-English languages to catch-up with this change.
Will be part of the next release.

Excellent, thank you for sorting this.


Swin IR  and  LAM

I encountered this situation while doing LAM, please seek help！

Sorry, we do not encounter this issue, but from the figures, it seems that you have already obtained the visual results?


.Net: Switch to using DefaultAzureCredential in Azure OpenAI integration tests

Motivation and Context

Description

Contribution Checklist

[ ] The code builds clean without any errors or warnings
[ ] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[ ] All unit tests pass, and I have added new tests where possible
[ ] I didn't break anyone :smile:

Some nullable warnings


showCircularIcon and showCloseButton not working anymore

Hi, It appears that with new version the:
showCircularIcon and
showCloseButton boolean properties
are not working anymore. Alert says SCAlertView has no members with those names.
Am I doing anything wrong?  Thank you!

im getting the same

ops...it was indeed my mistake. You just need to use the appearance setting such as:
let appearance = SCLAlertView.SCLAppearance(showCloseButton: false, showCircularIcon: true)
let alertView = SCLAlertView(appearance: appearance)


ERR_ELECTRON_BUILDER_CANNOT_EXECUTE when trying to build a desktop app for Ubunto

I believe I am having a similar problem to what is found here and here. The error message I get is different so I will write a new issue.   My goal is to produce a desktop app that will run on Linux.  Per this issue I think what I am doing is supported.
Environment:
Windows 10 22H2 19045.2846
Visual Studio 2022 / latest
Unbutu running on WSL2 same physical machine as Windows

sam@UGLY:~/stuff/BlazorServerTest1$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.2 LTS
Release:        22.04
Codename:       jammy

dotnet, node and x11 are installed.  xeyes/gedit runs correctly.
My app is Hello World, only mods from default Blazor template are to install Electron.Net
Electron.Net versions 23.6.1 and 23.6.2-alpha-13 - both give same result.
Steps to reproduce
On Windows open command line in .csproj folder:
dotnet electronize start

This works fine - Blazor runs in an Electron window.
In same command window:
C:\Projects\BlazorServerTest1\BlazorServerTest1>dotnet electronize build /target linux

Build Electron Application...
Arguments:
target = linux
Build ASP.NET Core App for linux-x64...
Executing dotnet publish in this directory: C:\Projects\BlazorServerTest1\BlazorServerTest1\obj\desktop\linux
Build ASP.NET Core App for linux-x64 under Release-Configuration...
dotnet publish -r linux-x64 -c "Release" --output "C:\Projects\BlazorServerTest1\BlazorServerTest1\obj\desktop\linux\bin" /p:PublishReadyToRun=true /p:PublishSingleFile=true --self-contained
dotnet publish -r linux-x64 -c "Release" --output "C:\Projects\BlazorServerTest1\BlazorServerTest1\obj\desktop\linux\bin" /p:PublishReadyToRun=true /p:PublishSingleFile=true --self-contained
MSBuild version 17.5.1+f6fdcf537 for .NET
Determining projects to restore...
Restored C:\Projects\BlazorServerTest1\BlazorServerTest1\BlazorServerTest1.csproj (in 345 ms).
BlazorServerTest1 -> C:\Projects\BlazorServerTest1\BlazorServerTest1\bin\Release\net6.0\linux-x64\BlazorServerTest1.dll
BlazorServerTest1 -> C:\Projects\BlazorServerTest1\BlazorServerTest1\obj\desktop\linux\bin\

Start npm install...
npm install --production

added 49 packages, and audited 50 packages in 8s

found 0 vulnerabilities

ElectronHostHook handling started...
Build Electron Desktop Application...
Executing electron magic in this directory: C:\Projects\BlazorServerTest1\BlazorServerTest1\bin\desktop
Create electron-builder configuration file...
node build-helper.js electron.manifest.json

Package Electron App for Platform linux...
npx electron-builder --config=./bin/electron-builder.json --linux --x64 -c.electronVersion=23.2.0
ΓÇó electron-builder  version=23.6.0 os=10.0.19045
ΓÇó loaded configuration  file=C:\Projects\BlazorServerTest1\BlazorServerTest1\obj\desktop\linux\bin\electron-builder.json
ΓÇó description is missed in the package.json  appPackageFile=C:\Projects\BlazorServerTest1\BlazorServerTest1\obj\desktop\linux\package.json
ΓÇó packaging       platform=linux arch=x64 electron=23.2.0 appOutDir=C:\Projects\BlazorServerTest1\BlazorServerTest1\bin\Desktop\linux-unpacked
ΓÇó scheduling remote build  target=snap arch=x64
ΓÇó scheduling remote build  target=appImage arch=x64
ΓÇó cannot get, wait  error=Get "https://service.electron.build/find-build-agent?no-cache=1i4dems": dial tcp <IP_ADDRESS>:443: connectex: No connection could be made because the target machine
actively refused it.
attempt=0
waitTime=2
ΓÇó cannot get, wait  error=Get "https://service.electron.build/find-build-agent?no-cache=1i4dems": dial tcp <IP_ADDRESS>:443: connectex: No connection could be made because the target machine
actively refused it.
attempt=1
waitTime=4
ΓÇó cannot get, wait  error=Get "https://service.electron.build/find-build-agent?no-cache=1i4dems": dial tcp <IP_ADDRESS>:443: connectex: No connection could be made because the target machine
actively refused it.
attempt=2
waitTime=6
Γ¿» Get "https://service.electron.build/find-build-agent?no-cache=1i4dems": dial tcp <IP_ADDRESS>:443: connectex: No connection could be made because the target machine actively refused it.
Γ¿» C:\Users\sam\AppData\Local\npm-cache_npx\009083ec26dc578f\node_modules\app-builder-bin\win\x64\app-builder.exe process failed ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
Exit code:
1  failedTask=build stackTrace=Error: C:\Users\sam\AppData\Local\npm-cache_npx\009083ec26dc578f\node_modules\app-builder-bin\win\x64\app-builder.exe process failed
ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
Exit code:
1
at ChildProcess. (C:\Users\sam\AppData\Local\npm-cache_npx\009083ec26dc578f\node_modules\builder-util\src\util.ts:250:14)
at Object.onceWrapper (node:events:510:26)
at ChildProcess.emit (node:events:390:28)
at ChildProcess.cp.emit (C:\Users\sam\AppData\Local\npm-cache_npx\009083ec26dc578f\node_modules\cross-spawn\lib\enoent.js:34:29)
at maybeClose (node:internal/child_process:1064:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
From previous event:
at processImmediate (node:internal/timers:464:21)
From previous event:
at RemoteBuilder.build (C:\Users\sam\AppData\Local\npm-cache_npx\009083ec26dc578f\node_modules\app-builder-lib\src\remoteBuilder\RemoteBuilder.ts:51:28)
at RemoteTarget.finishBuild (C:\Users\sam\AppData\Local\npm-cache_npx\009083ec26dc578f\node_modules\app-builder-lib\src\linuxPackager.ts:105:30)
at async Promise.all (index 2)
at AsyncTaskManager.awaitTasks (C:\Users\sam\AppData\Local\npm-cache_npx\009083ec26dc578f\node_modules\builder-util\src\asyncTaskManager.ts:65:25)
at Packager.doBuild (C:\Users\sam\AppData\Local\npm-cache_npx\009083ec26dc578f\node_modules\app-builder-lib\src\packager.ts:453:5)
at Object.executeFinally (C:\Users\sam\AppData\Local\npm-cache_npx\009083ec26dc578f\node_modules\builder-util\src\promise.ts:12:14)
at Packager._build (C:\Users\sam\AppData\Local\npm-cache_npx\009083ec26dc578f\node_modules\app-builder-lib\src\packager.ts:376:31)
at Packager.build (C:\Users\sam\AppData\Local\npm-cache_npx\009083ec26dc578f\node_modules\app-builder-lib\src\packager.ts:337:12)
at Object.executeFinally (C:\Users\sam\AppData\Local\npm-cache_npx\009083ec26dc578f\node_modules\builder-util\src\promise.ts:12:14)

... done

Despite the above error msg binaries are still produced in bin\Desktop\linux-unpacked\resources\bin.
Copy files in folder above to home folder in WSL file subsystem.  In my case this is \\wsl.localhost\Ubuntu\home\sam\stuff\BlazorServerTest1
In a terminal window on the Linux VM run the following:
sam@UGLY:~/stuff/BlazorServerTest1$ chmod 777 BlazorServerTest1

sam@UGLY:~/stuff/BlazorServerTest1$ ./BlazorServerTest1

Unhandled exception. SocketIOClient.ConnectionException: Cannot connect to server 'http://localhost/'
---> System.TimeoutException: The operation has timed out.
--- End of inner exception stack trace ---
at SocketIOClient.SocketIO.ConnectAsync()
at ElectronNET.API.SocketIoFacade.Connect()
at ElectronNET.API.BridgeConnector.get_Socket()
at ElectronNET.API.WindowManager.CreateWindowAsync(BrowserWindowOptions options, String loadUrl)
at ElectronNET.API.WindowManager.CreateWindowAsync(String loadUrl)
at BlazorServerTest1.Program.ElectronBootstrap() in C:\Projects\BlazorServerTest1\BlazorServerTest1\Program.cs:line 80
at BlazorServerTest1.Program.<>c__DisplayClass0_0.<b__0>d.MoveNext() in C:\Projects\BlazorServerTest1\BlazorServerTest1\Program.cs:line 36
--- End of stack trace from previous location ---
at System.Threading.Tasks.Task.<>c.b__128_1(Object state)
at System.Threading.QueueUserWorkItemCallbackDefaultContext.Execute()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart()
at System.Threading.Thread.StartCallback()
Aborted

Am I supposed to have a HTTP server runing on the Linux machine? Error message references files on my windows machine.... IDK why.

In [this issue] it was requested to copy the project source to Ubunto and build.  I did that - here is what I got:
sam@UGLY:~/stuff/BlazorServerTest1$ dotnet build

MSBuild version 17.3.2+561848881 for .NET
Determining projects to restore...
Restored /home/sam/stuff/BlazorServerTest1/BlazorServerTest1.csproj (in 458 ms).
BlazorServerTest1 -> /home/sam/stuff/BlazorServerTest1/bin/Debug/net6.0/BlazorServerTest1.dll

Build succeeded.
0 Warning(s)
0 Error(s)

Time Elapsed 00:00:03.73

sam@UGLY:~/stuff/BlazorServerTest1$ electronize start

Start Electron Desktop Application...
Arguments:

dotnet publish -r linux-x64 -c "Debug" --output "/home/sam/stuff/BlazorServerTest1/obj/Host/bin" /p:PublishReadyToRun=true /p:PublishSingleFile=true --no-self-contained
MSBuild version 17.3.2+561848881 for .NET
Determining projects to restore...
Restored /home/sam/stuff/BlazorServerTest1/BlazorServerTest1.csproj (in 473 ms).
BlazorServerTest1 -> /home/sam/stuff/BlazorServerTest1/bin/Debug/net6.0/linux-x64/BlazorServerTest1.dll
BlazorServerTest1 -> /home/sam/stuff/BlazorServerTest1/obj/Host/bin/

node_modules missing in: /home/sam/stuff/BlazorServerTest1/obj/Host/node_modules
Start npm install...
npm install
/usr/bin/env: ‘bash\r’: No such file or directory

ElectronHostHook handling started...
Invoke electron - in dir: /home/sam/stuff/BlazorServerTest1/obj/Host/node_modules/.bin
./electron "../../main.js"
Unhandled exception. System.AggregateException: One or more errors occurred. (An error occurred trying to start process '/usr/bin/bash' with working directory
'/home/sam/stuff/BlazorServerTest1/obj/Host/node_modules/.bin'. No such file or directory)
---> System.ComponentModel.Win32Exception (2): An error occurred trying to start process '/usr/bin/bash' with working directory '/home/sam/stuff/BlazorServerTest1/obj/Host/node_modules/.bin'. No
such file or directory
at System.Diagnostics.Process.ForkAndExecProcess(ProcessStartInfo startInfo, String resolvedFilename, String[] argv, String[] envp, String cwd, Boolean setCredentials, UInt32 userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec)
at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at ElectronNET.CLI.ProcessHelper.CmdExecute(String command, String workingDirectoryPath, Boolean output, Boolean waitForExit) in C:_PrivateRepo\Electron.NET\ElectronNET.CLI\ProcessHelper.cs:line 40
at ElectronNET.CLI.Commands.StartElectronCommand.b__17_0() in C:_PrivateRepo\Electron.NET\ElectronNET.CLI\Commands\StartElectronCommand.cs:line 178
at System.Threading.Tasks.Task1.InnerInvoke()    at System.Threading.Tasks.Task.<>c.<.cctor>b__272_0(Object obj)    at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location ---    at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)    at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)    --- End of inner exception stack trace ---    at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)    at System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotification)
at System.Threading.Tasks.Task`1.get_Result()
at ElectronNET.CLI.Program.Main(String[] args) in C:_PrivateRepo\Electron.NET\ElectronNET.CLI\Program.cs:line 59
Aborted

I fixed the npm error using the answer to this question.
Tried to run my app from source again at Ubunto terminal prompt:
sam@UGLY:~/stuff/BlazorServerTest1$ electronize start

Start Electron Desktop Application...
Arguments:
dotnet publish -r linux-x64 -c "Debug" --output "/home/sam/stuff/BlazorServerTest1/obj/Host/bin" /p:PublishReadyToRun=true /p:PublishSingleFile=true --no-self-contained
MSBuild version 17.3.2+561848881 for .NET
Determining projects to restore...
All projects are up-to-date for restore.
BlazorServerTest1 -> /home/sam/stuff/BlazorServerTest1/bin/Debug/net6.0/linux-x64/BlazorServerTest1.dll
BlazorServerTest1 -> /home/sam/stuff/BlazorServerTest1/obj/Host/bin/
node_modules missing in: /home/sam/stuff/BlazorServerTest1/obj/Host/node_modules
Start npm install...
npm install
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package<EMAIL_ADDRESS>npm WARN EBADENGINE   required: { node: '>=14.0.0' },
npm WARN EBADENGINE   current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
up to date, audited 153 packages in 815ms
22 packages are looking for funding
run npm fund for details
found 0 vulnerabilities
ElectronHostHook handling started...
Invoke electron - in dir: /home/sam/stuff/BlazorServerTest1/obj/Host/node_modules/.bin
./electron "../../main.js"
Electron Socket IO Port: 8000
Electron Socket started on port 8000 at ::1
ASP.NET Core Port: 8001
[1185:0424/180630.352942:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[1235:0424/180630.428464:ERROR:gpu_memory_buffer_support_x11.cc(49)] dri3 extension not supported.
stdout: Use Electron Port: 8000
ASP.NET Core Application connected... global.electronsocket vs057hfhE7d3iR9xAAAC 2023-04-25T01:06:30.707Z
stdout: BridgeConnector connected!
stdout: Called Event BrowserWindowCreated - data 1
(node:1158) electron: Failed to load URL: http://localhost:8001/ with error: ERR_CONNECTION_REFUSED
(Use electron --trace-warnings ... to show where the warning was created)
stdout: info: Microsoft.Hosting.Lifetime[14]
Now listening on: http://localhost:8001
stdout: ASP.NET Core host has fully started.
stdout: info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
stdout: info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
Content root path: /home/sam/stuff/BlazorServerTest1/obj/Host/bin/
Electron can't find my app but when I go to http://localhost:8001/ in my browser my app loads immediately without error.
	"Kestrel": {
		"EndPoints": {
		  "Http": {
			"Url": "http://localhost:8001"
		  }
		}

I'm getting the exact same error on ubuntu with the demo api app. I just created an issue over there a few minutes ago before I saw this.
Frankly I've been working for several days to get ANY type of project to run or build on Linux with no success. If you figure this out PLEASE let me know.
I've tried creating various types of new dotnet projects, then "electronizing" them. They all work on Windows but none work on Linux. All with different types of errors. I was hoping to use Linux as a build server to target Mac but this is a bit dis-heartening.
This error seems to be related to the graphics driver? My ubuntu instance is a VM running in Hyper-V

@andrewschuler Andrew, you may want to try Photiono.  I had problems with it initially, but they released a new build in the last few days.  I just got a basic hello world app running on both Windows and Ubunto.

@sam-wheat Thanks for that.
Some more information for you as well. All the errors I've been seeing have been with "electronize start". However I just tried to build the project with "electronize build /target linux" on Ubuntu. That builds successfully with the errors and the app runs as it should. From this experience it seems maybe 'electronize start' should only be used on Windows?

@andrewschuler  I'm just another user so I can't offer any guidance.  You made it further than I did however.  I was never able to get it to run on linux even if I built it on the linux machine.

@andrewschuler  and @sam-wheat, did any of you find a solution? I'm getting the SocketIOClient.ConnectionException: Cannot connect to server 'http://localhost/' error, but on Windows.

I ended up using a different platform and have not looked back.  See my link to Photino above.

From: Lukas Lapinskas @.>
Sent: Thursday, June 27, 2024 8:06 AM
To: ElectronNET/Electron.NET @.>
Cc: Sam Wheat @.>; Mention @.>
Subject: Re: [ElectronNET/Electron.NET] ERR_ELECTRON_BUILDER_CANNOT_EXECUTE when trying to build a desktop app for Ubunto (Issue #770)
@andrewschulerhttps://github.com/andrewschuler and @sam-wheathttps://github.com/sam-wheat, did any of you find a solution? I'm getting the SocketIOClient.ConnectionException: Cannot connect to server 'http://localhost/' error, but on Windows.
—
Reply to this email directly, view it on GitHubhttps://github.com/ElectronNET/Electron.NET/issues/770#issuecomment-2194966984, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEA2LWQMYFXRBKD3Z6DWVZTZJQS5XAVCNFSM6AAAAABKAEDCQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJUHE3DMOJYGQ.
You are receiving this because you were mentioned.Message ID: @.***>

Same as @sam-wheat  , I punted on Linux support and jumped over to MAUI.


CUDA out of memory. Tried to allocate 36.00 MiB (GPU 0; 4.00 GiB total capacity; 2.88 GiB already allocated; 627.20 KiB free; 2.95 GiB reserved in total by PyTorch)

Description
I having problem with my CUDA.? Any Help is greatly appreciated?
Other Comments

Try reducing the batch size or the image size or both. That way the model should fit into memory.

Thank you!


🐞 -  Migration failed: Cannot read properties of undefined (reading 'getInitializer')

Which @taiga-ui/* package(s) are the source of the bug?
taiga-schematics
Please provide a link to a minimal reproduction of the bug
No response
Is this issue blocking you?
Blocking
Description
When migrating to version 3 I get the following error:
[error] TypeError: Cannot read properties of undefined (reading 'getInitializer')
    at decoratorToTemplateResource (C:\Dev\ionity\cockpit-frontend\node_modules\@taiga-ui\cdk\schematics\utils\templates\get-component-templates.js:30:39)
    at Array.map (<anonymous>)
    at Object.getComponentTemplates (C:\Dev\ionity\cockpit-frontend\node_modules\@taiga-ui\cdk\schematics\utils\templates\get-component-templates.js:11:10)
    at Object.migrateTemplates (C:\Dev\ionity\cockpit-frontend\node_modules\@taiga-ui\cdk\schematics\ng-update\steps\migrate-templates.js:22:67)
    at C:\Dev\ionity\cockpit-frontend\node_modules\@taiga-ui\cdk\schematics\ng-update\index.js:53:29
    at Generator.next (<anonymous>)
    at C:\Dev\ionity\cockpit-frontend\node_modules\tslib\tslib.js:118:75
    at new Promise (<anonymous>)
    at Object.__awaiter (C:\Dev\ionity\cockpit-frontend\node_modules\tslib\tslib.js:114:16)
    at C:\Dev\ionity\cockpit-frontend\node_modules\@taiga-ui\cdk\schematics\ng-update\index.js:44:39

I cannot provide more information. Any hint how to debug?
Angular version
14.0.2
Taiga UI version
3.1.0
Which browsers have you used?

[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

Which operating systems have you used?

[ ] macOS
[X] Windows
[ ] Linux
[ ] iOS
[ ] Android

i think we can improve our migrations to show a warning
show a minimal example of such a component, please

The component looked like:
@Component({ selector: 'app-tma-filters' })
class TmaFiltersStubComponent {}

And I added a required template:
@Component({ selector: 'app-tma-filters', template: '' })
class TmaFiltersStubComponent {}

In your migration this is not checked:
https://github.com/Tinkoff/taiga-ui/blob/e34550be8e335be08716c47552cf27ffec656155/projects/cdk/schematics/utils/templates/get-component-templates.ts#L43
I've added a log to your compiled code to find the wrong definitions. I mean, you can ignore if there is no template  and put a warning. But the problem is more on our side, I guess

I'll close it because @Component requires either template or templateRef so it's not a valid case.


bug: arbitrum watch: true and block time

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
<EMAIL_ADDRESS>Current Behavior
I've tried using watch: true on arbitrum, which kills the API rate limits, as the current block time on Arbitrum is less than a second (https://arbiscan.io/blocks).
Since it queries for every new block, it makes quite a lot of queries, which kills the APIs rate limit.
I've tried with "cacheTime" and "staleTime", both separately and together, and with and without watch true and false.
And the only thing that seems to be relevant is "watch".
It either refreshes more than once a second, of never refreshes.
Expected Behavior
Allow to refresh every x milliseconds.
Steps To Reproduce
No response
Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)
No response
Anything else?
No response

Do you really need the "minimal reproducible example"?

Yes, this helps us jump right into fixing an issue without needing to set up anything. See Why Reproductions are Required for more info. You can pop in a dummy API key and use new.wagmi.sh as a baseline for the example.

Regarding the "cacheTime" and "staleTime", ...

See the React Query docs for more info on "cacheTime" and "staleTime". We are planning on improving wagmi's docs around this for the first major release.

You could switch to polling instead of using websockets. This is a limitation of ethers and since wagmi uses ethers for the time-being, unfortunately there's not much that can be done.


feat(sandbox): chat example

auth tables values added
MIGRATION CHANGE:
migration-20210421113036- auth tables setup
migration-20210421113146- auth table values added
migration-20210823080434- auth table roles added
migration-20210823081005- chat tables added
migration-20210823082119- tables moved to public
migration-20210501132806- auth tables setup
BREAKING CHANGE:
auth tables roles added
notification tables added
Description

An example has been added which uses chat service and notification service of sourceloop. This is mentioned in Issue No - 331.
The microservices are working in complete sense. The facade is still in progress.
Migrations for both services have been built separately for better understanding.

Fixes #331
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[X] Intermediate change (work in progress)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[x] Performed a self-review of my own code
[ ] npm test passes on your machine
[ ] New tests added or existing tests modified to cover all changes
[x] Code conforms with the style guide
[ ] API Documentation in code was updated
[ ] Any dependent changes have been merged and published in downstream modules

@sunishka1 also make the changes to run through docker compose.


ticdc lag is more than 4m after inject one tikv network partition to all

What did you do?
inject one tikv network partition to all last for 10m
http://perf.pingcap.net:3000/d/WOw1JWmVk/ha-test-case-detail?orgId=1&refresh=10s&var-case_id=3060013
What did you expect to see?
changefeed lag is less than 30s
What did you see instead?
ticdc lag is more than 4m after inject one tikv network partition to all

Versions of the cluster
git hash：5252420517ce5497ed053aa6322fdb2a33f898e1
current status of DM cluster (execute query-status <task-name> in dmctl)
No response

/remove-area dm
/area ticdc
/assign overvenus

/unassign @overvenus
/assign @hicqu

/severity major

By the design
/close

Does this issue can be fixed by https://github.com/pingcap/tiflow/issues/8858 ?

fixed by the  https://github.com/pingcap/tiflow/pull/9771

/close


chore(tools): switch to yarn

Addresses #65

Hi @ojongerius
Thanks for the feedback. I left both the Manual deployment and the CI part on purpose.
Travis will automatically use Yarn or npm. So, its installation is not needed. Plus npm i -g yarn is a bad idea and should be avoided. This install form is deprecated.
For the manual deployment, it would make sense to use npm because its a global install for serverless and we are restricting yarn for our project. So others may or may not face issues?
My assumption and reason for the PR is that Yarn plays well for all scenarios and npm does not. Hence leaving global installs via npm will still mean Yarn is good to go and use if needed?

@raisedadead 🏆

Thanks @ojongerius !


Training process got stuck when loss=dpo sample_during_eval=true trainer=FSDPTrainer

Thanks for sharing this repo.
When I run dpo with FSDPTrainer and sample_during_eval, it just got stuck with the following info:
Processing HH: 100%|█████████████████| 160800/160800 [00:04<00:00, 39073.07it/s]
Running evaluation after 0 train examples
Computing eval metrics: 100%|█████████████████████| 8/8 [00:04<00:00,  1.71it/s]
Warning: n_eval_model_samples (16) < eval_batch_size (32). Sampling from the first complete eval batch of prompts.
Generating samples...:   0%|                                               | 0/1 [00:00<?, ?it/s]
Concretely, it got stuck when doing model.generate(). Several issues reporting some thing wrong with FSDP + HuggingFace generate (also mentioned in your code annotation: https://github.com/pytorch/pytorch/issues/100069). I want to check whether you came across this situation and how to handel it?
Looking forward to your response, thanks in advance!

Just found the warning info in readme... It seems no tractable solution to handle this, so I closed this issue.

Just found the warning info in readme... It seems no tractable solution to handle this, so I closed this issue.


[🐛 BUG]: Worker after SIGTERM not wait for finish activity

No duplicates 🥲.

[X] I have searched for a similar issue in our bug tracker and didn't find any solutions.

What happened?
Workflow
#[Workflow\WorkflowInterface]
class Workflow
{
    #[Workflow\WorkflowMethod(name: 'Workflow')]
    public function run()
    {
        $simple = Workflow::newActivityStub(
            SimpleActivity::class,
            ActivityOptions::new()
                ->withStartToCloseTimeout(60)
                ->withRetryOptions(RetryOptions::new()->withMaximumAttempts(1))
        );

        yield $simple->sendRequest('request');
    }
}

Acitivity:
#[ActivityInterface(prefix: "SimpleActivity.")]
class SimpleActivity
{
    #[ActivityMethod]
    public function sendRequest(
        string $input
    ): string {
        sleep(40);

        return strtolower($input);
    }
}

Let's imagine situation when one of activity is responsible for sending POST request (this request can be send only one time) and it takes around 30 seconds.
In the 15th second while sending request, one of developer made a deployment - so he send a SIGTERM to kill container.
In logs after sent SIGTERM I see
2022-09-30T11:03:44.501Z	WARN	temporal    	Failed to poll for task.	{"Namespace": "default", "TaskQueue": "default", "WorkerID": "default:37c72875-bdf1-49a8-9730-b686e60194b0", "WorkerType": "WorkflowWorker", "Error": "worker stopping"}

Activity was interrupted and is not processed anymore so in result in Temporal I see
{
  "message": "activity StartToClose timeout",
  "source": "Server",
  "stackTrace": "",
  "cause": null,
  "timeoutFailureInfo": {
    "timeoutType": "StartToClose",
    "lastHeartbeatDetails": {
      "payloads": [
        {
          "metadata": {
            "encoding": "anNvbi9wbGFpbg=="
          },
          "data": "eyJ2YWx1ZSI6MTh9"
        }
      ]
    }
  }
}

From my perspective worker should wait for finish this activity as a secure way. Only SIGKILL should immediately kill process.
Functionality available in java-sdk - https://www.javadoc.io/static/io.temporal/temporal-sdk/1.0.0/io/temporal/worker/WorkerFactory.html#awaitTermination-long-java.util.concurrent.TimeUnit-
Or maybe I am doing something wrong.
Version
v2.11.3
Relevant log output
No response

Hey @cv65kr 👋🏻

From my perspective worker should wait for finish this activity as a secure way. Only SIGKILL should immediately kill process.

The worker does wait for the workflow. To set the grace_period please, set this option: https://github.com/roadrunner-server/roadrunner/blob/master/.rr.yaml#L1921
But, worker can't wait for an indefinite timeout. This functionality exists in any SDK. For the given Java SDK (shutdown):
 This method does not wait for previously received tasks to complete execution.

If you want to wait a bigger amount of time, just pass grace_period: 9999h value.

Only SIGKILL should immediately kill process

SIGKILL kills the process, not the workflow. After the restart, the workflow will be restarted. Even if you kill the temporal server, the history journal will be present in DB and will be recovered.

Activity was interrupted and is not processed anymore so in result in Temporal I see...

->withRetryOptions(RetryOptions::new()->withMaximumAttempts(1))

This is the reason, why the activity started only once.

Hi @rustatian
I already checked the grace_period and looks like this can solve the issue. I need to test once again very carefully. But thanks for fast response 👍

Only SIGKILL should immediately kill process

SIGKILL kills the process, not the workflow. After the restart, the workflow will be restarted. Even if you kill the temporal server, the history journal will be present in DB and will be recovered.

Yes, that's my point but ofc is dependent of various factors e.g. if activity was in the middle of the processing then it cannot be recovered after restart.

Activity was interrupted and is not processed anymore so in result in Temporal I see...

->withRetryOptions(RetryOptions::new()->withMaximumAttempts(1))

This is the reason, why the activity started only once.

I just give you a code to reproduce, and that's the case sometimes activity cannot be reattempted. And need to be safe during redeployments.
I will close topic for now, and if something pop up I will reopen it. Once again big thanks!


bazel + spm

it's possible to use spm   + bazel with some scripts by  @cgrindel
I want to do it with firebase - there's a long discussion here - and Google haven't been able to come to the party....
I'm thinking with your xcframework approach - it maybe possible.
I don't expect you to invest too much time -
https://github.com/firebase/firebase-ios-sdk/issues/6115
here's a top level write up with spm + bazel
https://chuckgrindel.com/swift-packages-in-bazel

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

http_archive(
    name = "cgrindel_rules_spm",
    sha256 = "03718eb865a100ba4449ebcbca6d97bf6ea78fa17346ce6d55532312e8bf9aa8",
    strip_prefix = "rules_spm-0.11.0",
    urls = [
        "http://github.com/cgrindel/rules_spm/archive/v0.11.0.tar.gz",
    ],
)

load(
    "@cgrindel_rules_spm//spm:deps.bzl",
    "spm_rules_dependencies",
)

spm_rules_dependencies()

load(
    "@build_bazel_rules_swift//swift:repositories.bzl",
    "swift_rules_dependencies",
)

swift_rules_dependencies()

load(
    "@build_bazel_rules_swift//swift:extras.bzl",
    "swift_rules_extra_dependencies",
)

swift_rules_extra_dependencies()

load("@cgrindel_rules_spm//spm:defs.bzl", "spm_pkg", "spm_repositories")

spm_repositories(
    name = "swift_pkgs",
    dependencies = [
        spm_pkg(
            "https://github.com/firebase/firebase-ios-sdk.git",
            from_version = "8.10.0",
            products = ["Firebase"],
        ),
    ],
)

unfortunately -
spm_repositories(
name = "swift_pkgs",
dependencies = [
spm_pkg(
"https://github.com/akaffenberger/firebase-ios-sdk-xcframeworks.git",
from_version = "8.10.0",
products = ["Firebase"],
),
],
)
couldn't get it to work with your spm either.
"@swift_pkgs//Firebase:Firebase",

I got it working - but it's not as elegant as your solution using xcframeworks.
would be nice to automate.


Single-element memory operations

Current assembly instructions for memory access deal with words (4 field elements). This creates quite a bit of over head for use case when we want to read/write a single field element. The overhead is in both places: the VM itself and the assembly instruction sequences needed to accomplish single-element reads/writes.
Adding dedicated operations to read/write single elements at the VM level is possible, but we should probably do it at a later date, once we have a better picture of how frequently these operations are used. However, we could add instructions at the assembly level to help with this. The instructions I'm thinking of are:

push.mem.addr - pushes the first element of the word at addr onto the stack.
push.local.idx - same as above but for a local.
pop.mem.addr- pops the element off the stack and saves it addr.
pop.local.idx- same as above but for a local.

Adding dedicated operations to read/write single elements at the VM level is possible, but we should probably do it at a later date, once we have a better picture of how frequently these operations are used.

Yeah, I think it makes sense to hold off on this.

However, we could add instructions at the assembly level to help with this.

Sounds good. Do we also want to allow passing the address via the stack for the mem operations like we do when dealing with words?

Do we also want to allow passing the address via the stack for the mem operations like we do when dealing with words?

Yes, I think it would make sense to do that.

Great, I'll take a look as I finish the rest of the io push refactor

Sounds good! I've updated the sepcs to include these new instructions.

Closed by #110


New genesis ledgers should always start with amendments enabled

Summary
When starting a new ledger chain/network, by default no amendments are on (except ones whose previous functionality has been retired) unless you explicitly specify --start.
The default way of creating a new genesis ledger should work like --start instead, to prevent situations where private/test/dev networks need to wait 2 weeks to get features from old amendments.
Motivation
Several times, we've reset or started up a new network (feature-specific devnets like NFT-Devnet and AMM-Devnet for example) and then noticed that various amendments are not actually enabled. (Usually DeletableAccounts is the one people notice first because their account sequence numbers all start at 1 instead of the latest ledger index.) That means that the network has to go through a two-week waiting period for lots of amendments, including important ones that have been enabled on Mainnet for years like "Flow".
Solution
Instead of having two ways to create a genesis ledger, with one enabling Amendments initially and one not, there should only be one sensible way to create a new genesis ledger, and it should match what --start does now. Amendments whose default vote is "Yes" should be enabled to begin with, and maybe even ones with a default "No" vote too?
Preferably, there should also be some way to explicitly control which amendments are on or off in the genesis ledger, so you could turn on a default-no or turn off a default-yes amendment if you wanted to exert more control. (That's what issue XRPLF/xrpl-dev-portal#1762 is about.)
But, regardless, there should not be two different new genesis ledger behaviors with the less useful one being the default.

If somebody is struggling with this, you can do the following to enable all required amendments on a fresh network without waiting for 2 weeks:
You can tell rippled to load a specific ledger on loading with rippled —ledgerfile <path_to_file>
You can create this file (e.g.myledger.json, name doesn’t matter) and put some desired configuration inside of it, for example here is how to enable the DeletableAccounts amendment (its ID is 30CD365592B8EE40489BA01AE2F7555CAC9C983145871DC82A42A31CF5BAE7D9)
{
  "ledger": {
    "accepted": true,
    "accountState": [
      {
        "Account": "rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh",
        "Balance": "100000000000000000",
        "Flags": 0,
        "LedgerEntryType": "AccountRoot",
        "OwnerCount": 0,
        "PreviousTxnID": "A92EF82C3C68F771927E3892A2F708F12CBD492EF68A860F042E4053C8EC6C8D",
        "PreviousTxnLgrSeq": 3,
        "Sequence": 4,
        "index": "2B6AC232AA4C4BE41BF49D2459FA4A0347E1B543A4C92FCEE0821C0201E2E9A8"
      },
      {
        "Amendments": [
          "30CD365592B8EE40489BA01AE2F7555CAC9C983145871DC82A42A31CF5BAE7D9"
        ],
        "Flags": 0,
        "LedgerEntryType": "Amendments",
        "index": "7DB0788C020F02780A673DC74757F23823FA3014C1866E72CC4CD8B226CD6EF4"
      }
    ],
    "account_hash": "5DF3A98772FB73E782B8740E87885C6BAD9BA486422E3626DEF968AD2CB2C514",
    "close_flags": 0,
    "close_time": 733708800,
    "close_time_human": "2023-Apr-02 00:00:00.000000",
    "close_time_resolution": 10,
    "closed": true,
    "hash": "56DA0940767AC2F17F0E384F04816002403D0756432B9D503DDA20128A2AAF11",
    "ledger_hash": "56DA0940767AC2F17F0E384F04816002403D0756432B9D503DDA20128A2AAF11",
    "ledger_index": "5",
    "parent_close_time": 733708800,
    "parent_hash": "56DA0940767AC2F17F0E384F04816002403D0756432B9D503DDA20128A2AAF11",
    "seqNum": "5",
    "totalCoins": "100000000000000000",
    "total_coins": "100000000000000000",
    "transaction_hash": "9A77D1D1A4B36DA77B9C4DC63FDEB8F821741D157802F9C42A6ED86003D8B4A0",
    "transactions": []
  },
  "ledger_current_index": 5,
  "status": "success",
  "validated": true
}

Notes:

The hashes are not real, but seems that rippled doesn’t check them when loading.
The hash for amendments object (index) is indeed check, can’t put random stuff in there. But thankfully the amendments object index is always the same 7DB0788C020F02780A673DC74757F23823FA3014C1866E72CC4CD8B226CD6EF4
Since this ledger started back in the past (April 2nd start of day in this case) - rippled will show warning to you that ledger timing is suspicious. But seems that it doesn’t really affect anything it seems. Same for missing ancestor hashes

Here is the list of all amendment IDs that are enabled on mainnet that you can plug into the Amendments array:
"6781F8368C4771B83E8B821D88F580202BCB4228075297B19E4FDC5233F1EFDC",
"4C97EBA926031A7CF7D7B36FDE3ED66DDA5421192D63DE53FFB46E43B9DC8373",
"42426C4D4F1009EE67080A9B7965B44656D7714D104A72F9B4369F97ABF044EE",
"740352F2412A9909880C23A559FCECEDA3BE2126FED62FC7660D628A06927F11",
"08DE7D96082187F6E6578530258C77FAABABE4C20474BDB82F04B021F1A68647",
"532651B4FD58DF8922A49BA101AB3E996E5BFBF95A913B3E392504863E63B164",
"1562511F573A19AE9BD103B5D6B9E01B3B46805AEC5D3C4805C902B514399146",
"E2E6F2866106419B88C50045ACE96368558C345566AC8F2BDF5A5B5587F0E6FA",
"07D43DCE529B15A10827E5E04943B496762F9A88E3268269D69C44BE49E21104",
"DC9CA96AEA1DCF83E527D1AFC916EFAF5D27388ECA4060A88817C1238CAEE0BF",
"3012E8230864E95A58C60FD61430D7E1B4D3353195F2981DC12B0C7C0950FFAC",
"42EEA5E28A97824821D4EF97081FE36A54E9593C6E4F20CBAE098C69D2E072DC",
"CC5ABAE4F3EC92E94A59B1908C2BE82D2228B6485C00AFF8F22DF930D89C194E",
"B4D44CC3111ADD964E846FC57760C8B50FFCD5A82C86A72756F6B058DDDF96AD",
"6C92211186613F9647A89DFFBAB8F94C99D4C7E956D495270789128569177DA1",
"B9E739B8296B4A1BB29BE990B17D66E21B62A300A909F25AC55C22D6C72E1F9D",
"1D3463A5891F9E589C5AE839FFAC4A917CE96197098A1EF22304E1BC5B98A454",
"F64E1EABBE79D55B3BB82020516CEC2C582A98A6BFE20FBE9BB6A0D233418064",
"67A34F2CF55BFC0F93AACD5B281413176FEE195269FA6D95219A2DF738671172",
"157D2D480E006395B76F948E3E07A45A05FE10230D88A7993C71F97AE4B1F2D1",
"CA7C02118BA27599528543DFE77BA6838D1B0F43B447D4D7F53523CE6A0E9AC2",
"58BE9B5968C4DA7C59BA900961828B113E5490699B21877DEF9A31E9D0FE5D5F",
"7117E2EC2DBF119CA55181D69819F1999ECEE1A0225A7FD2B9ED47940968479C",
"5D08145F0A4983F23AFFFF514E83FAD355C5ABFBB6CAB76FB5BC8519FF5F33BE",
"3CBC5C4E630A1B82380295CDA84B32B49DD066602E74E39B85EF64137FA65194",
"FBD513F1B893AC765B78F250E6FFA6A11B573209D1842ADC787C850696741288",
"586480873651E106F1D6339B0C4A8945BA705A777F3F4524626FF1FC07EFE41D",
"2CD5286D8D687E98B41102BDD797198E81EA41DF7BD104E6561FEB104EFF2561",
"C4483A1896170C66C098DEA5B0E024309C60DC960DE5F01CD7AF986AA3D9AD37",
"621A0B264970359869E3C0363A899909AAB7A887C8B73519E4ECF952D33258A8",
"8F81B066ED20DAECA20DF57187767685EEF3980B228E0667A650BAF24426D3B4",
"30CD365592B8EE40489BA01AE2F7555CAC9C983145871DC82A42A31CF5BAE7D9",
"00C1FC4A53E60AB02C864641002B3172F38677E29C26C5406685179B37E1EDAC",
"89308AF3B8B10B7192C4E613E1D2E4D9BA64B2EE2D5232402AE82A6A7220D953",
"4F46DF03559967AC60F2EB272FEFE3928A7594A45FF774B87A7E540DB0F8F068",
"25BA44241B3BD880770BFA4DA21C7180576831855368CBEC6A3154FDE4A7676E",
"1F4AFA8FA1BC8827AD4C0F682C03A8B671DCDF6B5C4DE36D44243A684103EF88",
"AF8DF7465C338AE64B1E937D6C8DA138C0D63AD5134A68792BBBE1F63356C422",
"955DF3FA5891195A9DAEFA1DDC6BB244B545DDE1BAA84CBB25D5F12A8DA68A0C",
"452F5906C46D46F407883344BFDD90E672B672C5E9943DB4891E3A34FEEEB9DB",
"B6B3EEDC0267AB50491FDC450A398AF30DBCD977CECED8BEF2499CAB5DAC19E2",
"B4E4F5D2D6FB84DF7399960A732309C9FD530EAE5941838160042833625A6076",
"98DECF327BF79997AEC178323AD51A830E457BFC6D454DAF3E46E5EC42DC619F",
"B2A4DB846F0891BF2C76AB2F2ACC8F5B4EC64437135C6E56F3F859DE5FFD5856",
"32A122F1352A4C7B3A6D790362CC34749C5E57FCE896377BFDC6CCD14F6CD627",
"DF8B4536989BDACE3F934F29423848B9F1D76D09BE6A1FCFE7E7F06AA26ABEAD"

They correspond to this human readable list:
TrustSetAuth
MultiSign
FeeEscalation
Flow
TickSize
CryptoConditions
fix1368
Escrow
EnforceInvariants
FlowCross
fix1373
SortedDirectories
fix1201
fix1512
fix1523
fix1528
DepositAuth
fix1513
Checks
fix1543
fix1623
fix1571
fix1515
DepositPreauth
fix1578
MultiSignReserve
fixTakerDryOfferRemoval
fixMasterKeyAsRegularKey
fixPayChanRecipientOwnerDir
fixCheckThreading
DeletableAccounts
RequireFullyCanonicalSig
fixQualityUpperBound
fixAmendmentMajorityCalc
fix1781
HardenedValidations
FlowSortStrands
TicketBatch
fixSTAmountCanonicalize
fixRmSmallIncreasedQOffers
NegativeUNL
CheckCashMakesTrustLine
ExpandedSignerList
NonFungibleTokensV1_1
fixRemoveNFTokenAutoTrustLine

If you want some non-enabled-on-mainnet amendments - just put it in the array, for example DisallowIncoming amendment ID is 47C3002ABA31628447E8E9A8B315FAA935CE30183F9A9B86845E469CA2CDC3DF
Use https://xrpscan.com/amendments as a reference.
Having said that it would indeed be nice to have some simple flag to:

Enable all amendments that are enabled on mainnet
Provide a list of other amendments to be enabled on your network immediately


bubble

my bubble was really big,
can you help me fix my bubble?
thanks, I'm on Android btw.

get better kid


Added other bodies to the file

Added all other bodies apart from moon, earth and the sun
@ritzvik

Hello @obi-wan-shinobi! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file src/einsteinpy/bodies.py:

Line 127:1: E302 expected 2 blank lines, found 1
Line 135:1: E305 expected 2 blank lines after class or function definition, found 1
Line 137:1: E302 expected 2 blank lines, found 1
Line 145:1: E305 expected 2 blank lines after class or function definition, found 1
Line 147:1: E302 expected 2 blank lines, found 1
Line 155:1: E305 expected 2 blank lines after class or function definition, found 1
Line 157:1: E302 expected 2 blank lines, found 1
Line 165:1: E305 expected 2 blank lines after class or function definition, found 1
Line 167:1: E302 expected 2 blank lines, found 1
Line 175:1: E305 expected 2 blank lines after class or function definition, found 1
Line 177:1: E302 expected 2 blank lines, found 1
Line 185:1: E305 expected 2 blank lines after class or function definition, found 1
Line 187:1: E302 expected 2 blank lines, found 1
Line 195:1: E305 expected 2 blank lines after class or function definition, found 1
Line 197:1: E302 expected 2 blank lines, found 1
Line 205:1: E305 expected 2 blank lines after class or function definition, found 1

For quality checks, follow this
https://docs.einsteinpy.org/en/latest/dev_guide.html#code-linting

For quality checks, follow this
https://docs.einsteinpy.org/en/latest/dev_guide.html#code-linting

Okay, I'll keep this in mind before making changes the next tim

Can you squash the commits into 1 or 2?
Otherwise seems fine

Can you squash the commits into 1 or 2?
Otherwise seems fine

@shreyasbapat Why the git diff is so weird?

@obi-wan-shinobi Thanks for hanging in there :p
Merging :)


Only specify storageclass key if storage class specified …

Blank value will disable dynamic provisioning

don't we need that here too? https://github.com/pachyderm/pachyderm/blob/master/etc/helm/pachyderm/templates/postgresql/statefulset.yaml#L67-L68

Good catch! I'll fix that up (but also, I'm nuking the built in postgres config shortly with bitnami lol)

Oh yeah haha

On Aug 17, 2021, at 3:54 PM, Kyle White @.***> wrote:
Good catch! I'll fix that up (but also, I'm nuking the built in postgres config shortly with bitnami lol)
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub https://github.com/pachyderm/pachyderm/pull/6743#issuecomment-900586885, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOYC4FHDP23UCEFUYI67WTT5K45XANCNFSM5CKNB37A.


Allow parameters filtering

This is a 🙋♂ feature or enhancement

[x] I've added tests (if it's a bug, feature or enhancement)
[x] I've adjusted the documentation (if it's a feature or enhancement)
[x] The test suite passes (run bundle exec rspec to verify this)

Summary
This pull request adds support for parameters filtering in order to filter sensitive information out of the logs. ActiveSupport::ParameterFilter was used for this task.
Context
Related to this issue: https://github.com/tongueroo/jets/issues/399
How to Test
I created this repo https://github.com/josediaz16/jets_demo following guides from https://github.com/tongueroo/jets/blob/master/readme/testing.md.
I had some troubles during testing:

I had to add cfn_status to Gemfile because an error like mentioned here occurs.
When running the local integration tests I got 4 failures because of InvalidAuthenticityToken, but the same happens using current version of Jets, I wouldn't think this PR affects that.

It took me much longer than I expected, I got caught up in work and had some issues with local testing. I believe it's ready for review. Looking forward for feedback 😄

Thanks for the specs!


App Extensions failing when building with new build system

tl;dr
Copying app extensions in a post-build phase includes the CodeSignOnCopy attribute, which creates a cycle when using the new build system. Xcode doesn't add the attribute, so it probably shouldn't be included.
Problem
Copying the app extension into the main target creates a cycle when using the new build system:

Showing Recent Messages
:-1: Cycle inside MyApp; building could produce unreliable results.
Cycle details:
→ Target 'MyApp' : CodeSign /Users/caesar/Library/Developer/Xcode/DerivedData/MyApp-akrqtdfekistduerxppbnpbmbzhr/Build/Products/Debug-iphonesimulator/MyApp.app/PlugIns/iMessageApp.appex
○ Target 'MyApp' : ValidateEmbeddedBinary /Users/caesar/Library/Developer/Xcode/DerivedData/MyApp-akrqtdfekistduerxppbnpbmbzhr/Build/Products/Debug-iphonesimulator/MyApp.app/PlugIns/iMessageApp.appex
○ Target 'MyApp' : CodeSign /Users/caesar/Library/Developer/Xcode/DerivedData/MyApp-akrqtdfekistduerxppbnpbmbzhr/Build/Products/Debug-iphonesimulator/MyApp.app/PlugIns/iMessageApp.appex

I have a sample project that illustrates this.
I'm embedding the app extension using this build phase:
postBuildScripts:
  - name: Embed App Extensions
    script: |
      cp -r ${BUILT_PRODUCTS_DIR}/iMessage.appex ${TARGET_BUILD_DIR}/${PLUGINS_FOLDER_PATH}/iMessage.appex

Maybe I'm just doing this bit wrong, and this problem is just user error 🤷♂
Workaround
I am able to get the project to build by going into the Copy Files build phase that is created, removing the iMessage.appex from it, and then manually re-adding it to the build phase (which is what the this commit in the sample project is doing).
We use XcodeGen pretty heavily, so having to remember to manually remove/re-add the file each time isn't great.
Explanation
The relevant part of the diff is basically:
- BF_887147700664 /* iMessageApp.appex in CopyFiles */ = {isa = PBXBuildFile; fileRef = FR_935153865209 /* iMessageApp.appex */; settings = {ATTRIBUTES = (CodeSignOnCopy, RemoveHeadersOnCopy, ); }; };
+ 397D8E8520C85D0E00FFACDE /* iMessageApp.appex in CopyFiles */ = {isa = PBXBuildFile; fileRef = FR_935153865209 /* iMessageApp.appex */; settings = {ATTRIBUTES = (RemoveHeadersOnCopy, ); }; };

Or to zero in on it, the CodeSignOnCopy attribute isn't included when manually including the file through Xcode.
This kind of makes sense looking at the error message, then --> it looks like it's trying to codesign the same file twice, which isn't something that the new build system wants to do (?).
Metadata

XcodeGen Version: 1.8.0
Xcode Version: 10.0 beta 1 (10L176w) (although also fails in Xcode 9.4)
macOS Version: 10.13.4 (17E202)

It's definitely possible that I'm just not using the correct settings in the project.yml to include the app extension. In which case this was a fun exploration into the project.pbxproj file 🤷♂

For what it's worth, I also submitted a radar to either add the "Code Sign On Copy" checkbox to app extensions, or ignore the attribute when building with the new build system, since it's able to detect it and hide the checkbox for extensions.
It was marked as a duplicate of 40839160.

Thats a dupe of my radar! I'll let you know if I hear anything back

It looks like CodeSignOnCopy defaults to true for all dependencies
https://github.com/yonaskolb/XcodeGen/blob/master/Sources/ProjectSpec/Dependency.swift#L38
A workaround is to set codeSign to false for your dependency.
The default for this value should be changed based on what type of target it's referencing. Are you aware of what sort of dependencies should be code signed?
@cjwirth in addition you may not need your postbuild script if you set embed to true as well. The default for this could be changed too.
dependencies:
  - target: MyExtension
    codeSign: false
    embed: true

😄 I just spent a day to track down this issue and came here to let others know about it but glad to see others also figured it out.
It seems frameworks are set to be code signed by default but extensions are not.
I think XcodeGen should change the default value, based on dependency targets type.

I talked with an engineer today, and he said that since the entire bundle will be code signed at the end, it's probably not necessary to code sign files that are being copied into the bundle (and in this case causing problems). He also said that he wasn't entirely sure about it, but that's what he thought.

By the logic would it be fair to assume anything that's not being embedded should be code signed?

I've opened #324 for this 👍


Get list of local users details in single query

Description
Simplify the way we get the list of local users for the sign in process.
The existing way selected a list of users, and then looped thru the userIds and selected userDetails but did one select for each userId found in the origional select.
This gets the userDetails in one select statement...
Reviewer Notes
Not sure if this speeds up our tests... The main bottleneck is after logging in when loading the index page.
Setup
add code to show the queries in cmd/webserver/main.go in the main() function: pop.Debug = true
run single e2e test and watch logs... It should only query the db once for the users when logging in.
Code Review Verification Steps

[ ] Request review from a member of a different team.
[ ] Have the Pivotal acceptance criteria been met for this change?

Screenshots
the current way: get a list of users and then run a select for each user...

this change: run a select w/ a sub query that returns all the users data in 1 trip to the db

Not sure if this speeds up our tests... The main bottleneck is after logging in when loading the index page.

This query is being run many (many) times in our e2e tests in the login process. This might speed things up when hitting /devlocal-auth/login, but I think our main slowdown is querying the shipments using Eager after logging in.
Like here for the tsp side: https://github.com/transcom/mymove/blob/master/pkg/models/shipment.go#L781


Update os_setup.md

Changed all Cuda 7.5 to Cuda 8.0 as it is now the supported version for the pip files.

Can one of the admins verify this patch?

Thanks for your PR @wagonhelm! We have updated the instruction in our release branch via #5097, as well as on our website, but looks like it did not get merge back to master properly.
We plan to do another merge soon. Closing this for now so we don't get conflicts during the merge. Sorry for the inconvenience and thanks again for your contribution!


Cancel outstanding http posts in probe when it exists

See https://github.com/weaveworks/scope/pull/459

Will this actually have any positive effect?

s/exists/exits/
It might help with ctrl-c'ing scope.
On Saturday, September 12, 2015, Peter Bourgon<EMAIL_ADDRESS>wrote:

Will this actually have any positive effect?
—
Reply to this email directly or view it on GitHub
https://github.com/weaveworks/scope/issues/472#issuecomment-139596554.

I don't see how it could. To the best of my knowledge, outstanding HTTP requests have no way to preempt termination. Let's close this until we get some evidence.

In testing for #503, I never experienced a problem with outstanding HTTP requests. Accordingly, I'll close this.


[web]  image stutters when resizing.

##Discription
image stutters when resizing window.
Image is not cropping or moving.
( i know i should just css + html for something like this but meh)
##gif
https://giphy.com/gifs/cnujHKXj66ghQM8CHf/html5
Steps to Reproduce
@override
  Widget build(BuildContext context) {
    return Stack(
      children: <Widget>[
        Image.asset("monokimonoXL.jpg",
        fit: BoxFit.cover,),
        Row(
          children: <Widget>[
            Container(
              width: 400,
            ),

            Column(
              children: <Widget>[
                Expanded(
                  flex: 1,
                  child: Container(),
                ),
                Text(
                  "monokimono",
                  style:

                   TextStyle(
                    fontFamily: "title1",
                    fontSize: 100,
                    color: Colors.white70,
                  ),
                ),
                Expanded(
                  flex:4,
                  child: Container(),
                ),
              ],
            ),
            Expanded(
              flex: 4,
              child: Container(),
            )
          ],
        )
      ],
    );

@NicTanghe I cant reproduce on my machine. Maybe upload your project so it can be downloaded and tested?

You can find evrything at
https://github.com/NicTanghe/nictanghe.github.io
hosted is nictanghe.github.io

Jeah the link i provided is no longer working becouse i updated the site and now it's broke.

@NicTanghe
Tried your code sample on latest dev and was able to see the image being resized and moved as I resized the window. Didn't notice any stutter / shake while doing it.
33941.mov.zip

flutter doctor -v
[✓] Flutter (Channel dev, 1.24.0-1.0.pre, on Mac OS X 10.15.4 19E2269
    darwin-x64, locale en-IN)
    • Flutter version 1.24.0-1.0.pre at /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision 12bea61c29 (8 days ago), 2020-10-14 15:57:04 -0700
    • Engine revision 069b3cf8f0
    • Dart version 2.11.0 (build 2.11.0-218.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.0.1, Build version 12A7300
    • CocoaPods version 1.9.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.50.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.11.0

[✓] Connected device (4 available)
    • SM A260G (mobile) • 5200763ebcfa861f • android-arm    • Android 8.1.0 (API
      27)
    • macOS (desktop)   • macos            • darwin-x64     • Mac OS X 10.15.4
      19E2269 darwin-x64
    • Web Server (web)  • web-server       • web-javascript • Flutter Tools
    • Chrome (web)      • chrome           • web-javascript • Google Chrome
      86.0.4240.111

• No issues found!

Based on the code sample you shared earlier (which now works) and since the link to your project isn't working, I am going ahead and closing this as fixed. If you disagree, write in comments and I'll reopen.
Thanks.


Add support for raw_input_contents and raw_output_contents in gRPC

Fixes #48
Changelog

Update proto to include raw_input_contents and raw_output_contents
Include new mlserver.raw module with some utilities to unpack / pack data into raw format
Update gRPC converters module to take into account the new raw fields

Looks good. One question when you pack back into raw contents to you remove the explicit data contents as with Triton you get one set but never both? Just wasn't clear on first glance.

Thanks for your review @sakoush !
To answer the points on the main comment:
- The implementation is very similar to Triton's. Bytes are actually encoded on the same way. The only difference is with tensors, where we use `struct` and they use the `tobytes()` and `frombuffer()` helpers from `numpy`. Both should be equivalent though. Architecture-wise, the `BYTES` encoding sets explicitly the endianness to ensure there're no issues. Perhaps we could investigate what `numpy` does for tensors to ensure we do the same thing?
-  Yes, it should. The `raw -> InferenceRequest` conversion occurs before any codecs are applied. So after that, the normal MLServer flow should kick off. Regarding how to write the request, same principle applies. You could use the `PandasCodec.encode_request()` helper and then call the `mlserver.raw.extract_raw` method to convert the normal data to raw (or you could do it using `tritonclient`, or manually).
- Not sure what you mean about this one. On both Triton and MLServer, the `raw_input_contents` / `raw_output_contents` fields are set on the same position of their respective protobuf objects (i.e. `7` and `6`).

tobytes() and frombuffer() helpers from numpy.

the ultimate test is to have mlserver -> triton inference pipeline with raw_contents perhaps which we can do with your change :)

fields are set on the same position of their respective protobuf objects (i.e. 7 and 6).

I am not saying they are different I am just trying to think a bit in the future and consider if there are any further optimisations that we could do, especially in SCv2 pipelines if we know that the raw_contents happen to be the last thing. I dont have anything concrete yet thought that we could explore.


"Vultureni" commune is listed in the drop-down menu

Description:
The commune is listed in the drop-down menu according to the law
Preconditions : the website (https://peviitor-ro.github.io/ui.orase/) is up and runing. After every step delete the text you typed from the search bar.

Step 1
Type "Vultureni" in the search bar.
Expected results
The location is listed in the drop-down menu as "Comuna Vultureni, Bacău"