[BUG] TableClient.CreateIfNotExistsAsync creates entry for failed request in Application Insights if table already exists

Library name and version
Azure.Data.Tables 12.6.1
Describe the bug
If I call TableClient.CreateIfNotExistsAsync() for an existing table, a request is sent to create it and the resulting exception is caught and dismissed.
Expected behavior
The call to the table storage to create the table is not logged by Application Insights as a failed request.
Actual behavior
The failed call to the table storage should not be logged by Application Insights, because it is expected and dealt with.
At least, there should be an option to turn on this behavior.
Reproduction Steps
var tableServiceClient = new TableServiceClient(connectionString);
var tableClient = tableServiceClient.GetTableClient(tableName);
await tableClient.CreateIfNotExistsAsync();
Environment
Azure App Service, Linux x64, .NET 6

Hi @thomasneubergersdx.  Thank you for reaching out and we regret that you're experiencing difficulties.   This is a known behavior of the Storage library, and one that a fix is planned for.   This work is tracked under #9934.    I'm going to link this to that issue and close out as a duplicate.


MudAutocomplete Required validation error is not displayed

Bug type
Component
Component name
MudAutocomplete
What happened?
All other inputs perform validation and show validation errors on missing focus (i.e. after clicking outside or after pressing tab), but MudAutoComplete performes validation only after some value was selected and them was removed

Issue is probably related to #2306
Expected behavior
MudAutocomplete validates it's input after losing focus
Reproduction link
https://try.mudblazor.com/snippet/GEQGbabnUACiwnMi
Reproduction steps

Go to https://try.mudblazor.com/snippet/GEQGbabnUACiwnMi
Click on Text
Press TAB two times
Validation error is diplayed for Text, but not for Autocomplete

Relevant log output
No response
Version (bug)
6.0.17
Version (working)
No response
What browsers are you seeing the problem on?
Chrome
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

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

Same issue here. Used the workaround here https://stackoverflow.com/questions/73241567/mudblazor-mudselect-validation


fix: update include/exclude docs

The schema would need updating too, it's at frontend/static/schema/config-file.v1.json


Remove console messages

The console.log messages are appearing in the console tab.

Please assign me this issue so that I can remove the console.log messages under GSSOC-23

Yes sure, go ahead!! @Avinash905

Yes sure, go ahead!! @Avinash905

Can you please add GSSOC'23 label to this issue?

Yes sure, go ahead!! @Avinash905

Can you please add GSSOC'23 label to this issue?

@Avinash905 Open a PR , we will review it and the label soon

Yes sure, go ahead!! @Avinash905

Can you please add GSSOC'23 label to this issue?

@Avinash905 Open a PR , we will review it and the label soon

Ok sure

@akshathar-navada is this counted in the GSSOC'23?

Yes, I will add the label:)

Yes, I will add the label:)

Thank You


bowern_and_atkinson2012: Pama-Nyungan

Authors contacted with request for posterior probability distribution 17 April 2019.

In touch with Claire Bowern about this - first set of files shared were log files rather than posterior trees.

Files lost in hard drive crash :(


Incorrect defining of type in links_search

https://github.com/howtographql/graphql-ruby/blob/540ac70b67b81a26ec04b35e59ecd9942898099a/app/graphql/resolvers/links_search.rb#L9
type types[Types::LinkType] =>  type [Types::LinkType]
Causes error when trying to query an allLinks filtered search
"error": {
    "message": "Failed to build return type for Query.allLinks from #<GraphQL::Schema::List:0x00007fcce5b4d7f0 @of_type=Types::LinkType>: Unexpected type input: #<GraphQL::Schema::List:0x00007fcce5b4d7f0> (GraphQL::Schema::List)"

Correct defining of type can be seen in SearchObjectGraphQL README.md

Duplicate issue


No incoming calls after bad network state.

We have received reports from our customers that they are unable to receive incoming calls. We were able to reproduce the issue using the 100% network loss setting using the device's Network Link Conditioner. If the device receives a call while in this 100% network loss state, the device will not receive any VOIP notifications for incoming calls after setting network conditions back to normal. The only way we have found to resolve the issue is to delete and reinstall the app on the device.

Hi @kjmacaul
I've tried the steps using the quickstart with the built-in network conditioner but was not able to reproduce the issue. Can you provide us the Call SIDs when the mobile client is not getting incoming call push notifications after the network dance? You can also check the Programmable Voice Dashboard and see if there is any error related to the call.
From our side we can take a look and see if there is any notification delivery failure being logged when the Twilio service is trying to send the call notification, but the VoIP notification is basically enabled by the Apple VoIP Service so it should work if the connectivity is restored.
-bobie

Here is an example of one of the call SIDs where the notifications are not received:
Call SID: CAfc674d193092c30a063692b2c9ec631f
Parent Call SID: CAfda4d8fbd561af1d148ed6b91e961512
There are no errors related to these calls on the dashboard.
Upon further testing, we also confirmed that the same issue occurs on the Android version of our app.

Hi @kjmacaul
I've checked the Call SIDs and couldn't find anything related to notification delivery wrong. I've also noticed that push notifications of the missed call were received when the network is back.
Any chance you can try the same steps using the quickstart? Both myself and our QE team have tried the same steps but we were able to receive notifications afterwards.

I've been working on reproducing  in the quickstart project since my last message. I was indeed able to reproduce it but it must be a call between two devices (not just hitting the /placeCall URL in a browser). I will provide steps below as best I can. If you still can't reproduce I'd be happy to send you my project files.

Launch the quickstart app on device A with the identity set to "alice".
Launch the quickstart app on device B with the identity set to "bob".
On device B, type "alice" in the call field and tap the "Call" button.
Verify that the call was received successfully on Device A.
On device A, turn on Network Link Conditioner with the setting of "100% Loss".
On device B, type "alice" in the call field and tap the "Call" button.
Verify that the call was NOT received successfully on Device A.
On device A, disable Network Link Conditioner.
On device B, type "alice" in the call field and tap the "Call" button.
Device A did not receive a call.

Hi @kjmacaul
Although the call delivery path are the same regardless the call is made from a browser or another mobile client, I did try using two mobile devices with the steps - I am still able to get the call notifications after the network is back.
I've also asked the Twilio Notify team to check the Call SID and they confirmed the notifications were successfully sent.

I've recorded a video of the reproduction of the issue using my devices. Is there some way I can provide this to you? Or is there any other way I can assist in the investigation?

I've noticed that there are 3 registration bindings for client-143 when I was checking CAfc674d193092c30a063692b2c9ec631f. Technically they should all be getting call notifications for that identity unless explicitly unregistered, but for investigation purposes, could you try to use a different identity which is only used on one mobile client?

I've moved over to a demo Twilio account for further investigation. Please check the call SID below. The client "newId" should only have one registration binding.
Call SID: CAf5b169aadb13c5e7f907ff436cd1268d
Parent Call SID: CAf9488065106a4b9c9493208be918fd16

Hi @kjmacaul
I've checked the Call SIDs but again things are looking fine and notification was sent to the device.
FWIW, when you are not able to receive incoming notifications after network is back, is the app in the background or foreground?
Does this happen on a specific device (device model, iOS version) or is also happening on other devices?

Also are there different Push Credential SIDs being used on the same client?

Hi @kjmacaul
I think I've run out of wits for now and I am ready for the video.
Could send the link to the video to my work email address? you know where to find it ;)
Thanks.

I just sent you the link. Thank you for your assistance.

Hi @kjmacaul
I've checked the video and it is indeed really odd. If you can run via the debugger, are you able to see logs of the incoming call notification or error messages after network conditioner is switched off?

Below are the only logs in the console from the point of the link conditioner being turned off until the call ends due to being unanswered:

2018-03-26 15:00:28.139648 SwiftVoiceCallKitQuickstart[825:196774] [VERBOSE TwilioVoice] Application did become active
2018-03-26 15:00:28.140401 SwiftVoiceCallKitQuickstart[825:196774] [DEBUG TVOReachability] Reachability Flag Status: -R ------- networkStatusForFlags

I tried to do some debugging with the device log from the Console app on MacOS (you will need the device attached). When I got the notification after switching off conditioner, although I didn't see the exact notification payload that comes to the app, I am still seeing messages with keyword like sandbox.push.apple.com and voIP.
Could you help us check if you can find these messages via the Console app?

Here are the logs from the Console app. Again, they are from the point of the link conditioner being turned off until the call ends due to being unanswered:

default	15:40:05.210757 -0700	SpringBoard	Running <SBAppToAppWorkspaceTransaction: 0x10adc3a80> for transition request:
<SBMainWorkspaceTransitionRequest: 0x1748e9800; eventLabel: ActivateSpringBoard; display: Main; source: Unspecified> {
applicationContext = <SBWorkspaceApplicationTransitionContext: 0x1744da240; background: NO> entities = {
SBLayoutPrimaryRole = <SBWorkspaceHomeScreenEntity: 0x175041aa0; ID: com.apple.SpringBoard.builtin.HomeScreen; layoutRole: primary>;
};
}
default	15:40:05.266758 -0700	sharingd	SystemUI changed: 0x0 -> 0x10
default	15:40:05.275235 -0700	SpringBoard	Starting device motion, mode=0x22,useAccelerometer=0,useGyro=1,useCompass=0,fUseNorthRef=0,buildingGYTT=0
default	15:40:05.309660 -0700	SpringBoard	Disabling home screen icon rotation for reason: SBCrossfadeIconZoomAnimator:0x10ad8df30
default	15:40:05.312450 -0700	SpringBoard	Dismissing banner for notification (null)
default	15:40:05.334059 -0700	locationd	Client com.apple.springboard connected
default	15:40:05.334793 -0700	locationd	getClientEffectiveRegistrationResult, /System/Library/CoreServices/SpringBoard.app/SpringBoard, com.apple.springboard, , CLClientRegistrationResult, kCLClientRegistrationResultFailedUnavailable, CLCommonLocationServicesEnabled, 1
default	15:40:05.335289 -0700	locationd	message 'kCLConnectionMessageGyroBiasEstimation' received from client 'com.apple.springboard'
default	15:40:05.335537 -0700	locationd	Client com.apple.springboard (0x102086200) is subscribing to notification kCLConnectionMessageGyroBiasEstimation
default	15:40:05.340033 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client 'com.apple.springboard'
default	15:40:05.340952 -0700	locationd	Client com.apple.springboard disconnected
default	15:40:05.833715 -0700	passd	 (0x10dd7cbc0:376): connection suspended
default	15:40:05.839102 -0700	passd	 (0x10dd2d870:376): connection suspended
default	15:40:05.868499 -0700	mediaserverd	-CMSessionMgr- cmsmHandleApplicationStateChange: CMSession: Client com.apple.Preferences with pid '376' is now Background Running. Background entitlement: NO
default	15:40:05.869296 -0700	backboardd	Turning off orientation events.
default	15:40:05.869765 -0700	mediaserverd	1067: pid 376(Preferences)
default	15:40:05.874536 -0700	backboardd	Stopping orientation detection.
default	15:40:05.875592 -0700	backboardd	Effective device orientation changed to: unknown
default	15:40:05.889832 -0700	SpringBoard	Undimming for source: programmatic
default	15:40:05.889951 -0700	SpringBoard	returning the workspace lock time (300.000000) from _nextLockTimeDuration
default	15:40:05.890140 -0700	SpringBoard	returning the workspace dim time (280.000000) from _nextIdleTimeDuration
default	15:40:05.890263 -0700	SpringBoard	Setting next idle duration (source:1) to: 280.000000 lockAfterDim: 20.000000
default	15:40:05.890381 -0700	SpringBoard	Setting _lastBKUserEventTimerMode=2 with duration=280.000000
error	15:40:05.892669 -0700	backboardd	Unable to bootstrap_look_up port with name .gsEvents: unknown error code (1102)
default	15:40:05.911589 -0700	SpringBoard	Enabling home screen icon rotation for reason: SBCrossfadeIconZoomAnimator:0x10ad8df30
default	15:40:05.913850 -0700	SpringBoard	Nudging home screen window orientation because icon rotation changed.
error	15:40:05.918114 -0700	SpringBoard	HW kbd: Failed to set (null) as keyboard focus
default	15:40:05.918390 -0700	SpringBoard	Starting device motion, mode=0x22,useAccelerometer=0,useGyro=1,useCompass=0,fUseNorthRef=0,buildingGYTT=0
default	15:40:05.921878 -0700	CommCenter	#I SIM has not requested to be notified on entering idle screen, not processing
default	15:40:05.934440 -0700	SpringBoard	SB orientation locked: NO; user lock: NO, overrides: NO
default	15:40:05.936161 -0700	CommCenter	#I CSIAppInfo.AppObserver: observe: 1. app got notification state: 4 for app: ; front app = ; calls = 0; inc = 0; active=true
default	15:40:05.936499 -0700	CommCenter	#I CSIAppInfo.AppObserver: notifyAboutFrontAppChange: notifyAboutFrontAppChange : app: ; pid: 0; net: 0
default	15:40:05.938655 -0700	locationd	Client com.apple.springboard connected
default	15:40:05.940650 -0700	SpringBoard	Root transaction complete: <SBAppToAppWorkspaceTransaction: 0x10adc3a80>
default	15:40:05.942656 -0700	locationd	getClientEffectiveRegistrationResult, /System/Library/CoreServices/SpringBoard.app/SpringBoard, com.apple.springboard, , CLClientRegistrationResult, kCLClientRegistrationResultFailedUnavailable, CLCommonLocationServicesEnabled, 1
default	15:40:05.943015 -0700	locationd	message 'kCLConnectionMessageGyroBiasEstimation' received from client 'com.apple.springboard'
default	15:40:05.943257 -0700	locationd	Client com.apple.springboard (0x10288ec00) is subscribing to notification kCLConnectionMessageGyroBiasEstimation
default	15:40:05.943883 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client 'com.apple.springboard'
default	15:40:05.975144 -0700	CommCenter	#I App state[(376)] is suspended
default	15:40:05.975307 -0700	CommCenter	#I CSIAppInfo.AppObserver: observe: 1. app got notification state: 2 for app: ; front app = ; calls = 0; inc = 0; active=false
default	15:40:05.975484 -0700	CommCenter	#I CTServerConnection from pid 376 has closed (conn=0x101421f50)
default	15:40:05.976111 -0700	locationd	Client com.apple.Home disconnected
default	15:40:05.976910 -0700	mediaserverd	-CMSessionMgr- cmsmHandleApplicationStateChange: CMSession: Client com.apple.Preferences with pid '376' is now Background Suspended. Background entitlement: NO
default	15:40:05.977765 -0700	mediaserverd	1067: pid 376(Preferences)
default	15:40:05.998844 -0700	symptomsd	376 com.apple.Preferences: BackgroundRunning (most elevated: BackgroundRunning)
default	15:40:06.999956 -0700	symptomsd	376 com.apple.Preferences: BackgroundTaskSuspended (most elevated: BackgroundTaskSuspended)
default	15:40:06.000319 -0700	symptomsd	Entry, display name com.apple.Preferences uuid 2E6641D4-6EF9-3E0C-998D-1025ABBBDF95 pid 376 isFront 0
default	15:40:06.003401 -0700	symptomsd	Check for bundle name com.apple.Preferences returns 0
default	15:40:06.004962 -0700	symptomsd	app name com.apple.Preferences isForeground 0  hasForegroundApps 0, current idea of foreground 1 disp (null)
default	15:40:06.006124 -0700	symptomsd	Going to background, new flags 0x0 enabled 0
default	15:40:06.007129 -0700	symptomsd	Continue with bundle name com.apple.Preferences, is front 0
default	15:40:06.007463 -0700	symptomsd	com.apple.Preferences: Foreground: false
default	15:40:06.007879 -0700	symptomsd	Remove appCompactState key com.apple.Preferences
default	15:40:06.008254 -0700	symptomsd	Entry, display name com.apple.Preferences uuid 2E6641D4-6EF9-3E0C-998D-1025ABBBDF95 pid 376 isFront 0
default	15:40:06.008396 -0700	symptomsd	UUID 2E6641D4-6EF9-3E0C-998D-1025ABBBDF95 already removed
default	15:40:06.009634 -0700	CommCenter	#I BundleID:  is no longer a foreground app
default	15:40:06.010741 -0700	IDSRemoteURLConnectionAgent	 => Pid 376 suspended!
default	15:40:06.010922 -0700	CommCenter	#I BundleID:  is no longer a foreground app
default	15:40:06.011302 -0700	IDSRemoteURLConnectionAgent	PID: 376 was suspended
default	15:40:06.024988 -0700	symptomsd	CFSM2 foreground (current/proposed/state) in = (1/0/1)
default	15:40:06.025588 -0700	symptomsd	CFSM2 foreground (current/state) out = (1/3)
default	15:40:06.031750 -0700	symptomsd	0x10035e0f0 keys: {
canUseOnAlternate = 1;
}, opt: {
arg1 = "{(\n    "com.apple.mobilemail",\n    "com.apple.InCallService",\n    "com.apple.Preferences"\n)}";
}
default	15:40:06.032019 -0700	symptomsd	Operating on async key: canUseOnAlternate
default	15:40:06.033046 -0700	symptomsd	returning: {
canUseOnAlternate =     {
codes =         {
"com.apple.InCallService" = 1;
"com.apple.Preferences" = 1;
"com.apple.mobilemail" = 1;
};
reasons =         {
"com.apple.InCallService" = AppWhitelisted;
"com.apple.Preferences" = AppWhitelisted;
"com.apple.mobilemail" = AppWhitelisted;
};
};
}
default	15:40:06.033214 -0700	symptomsd	CFSM dynamic blacklist short returning (value/reason): {
"com.apple.InCallService" = 1;
"com.apple.Preferences" = 1;
"com.apple.mobilemail" = 1;
}/{
"com.apple.InCallService" = AppWhitelisted;
"com.apple.Preferences" = AppWhitelisted;
"com.apple.mobilemail" = AppWhitelisted;
}
default	15:40:06.155001 -0700	symptomsd	0x10035e0f0 keys: {
canUseOnAlternate = 1;
}, opt: {
arg1 = "{(\n    "com.apple.InCallService",\n    "com.apple.mobilemail"\n)}";
}
default	15:40:06.155338 -0700	symptomsd	Operating on async key: canUseOnAlternate
default	15:40:06.155990 -0700	symptomsd	returning: {
canUseOnAlternate =     {
codes =         {
"com.apple.InCallService" = 1;
"com.apple.mobilemail" = 1;
};
reasons =         {
"com.apple.InCallService" = AppWhitelisted;
"com.apple.mobilemail" = AppWhitelisted;
};
};
}
default	15:40:06.156473 -0700	symptomsd	CFSM dynamic blacklist short returning (value/reason): {
"com.apple.InCallService" = 1;
"com.apple.mobilemail" = 1;
}/{
"com.apple.InCallService" = AppWhitelisted;
"com.apple.mobilemail" = AppWhitelisted;
}
default	15:40:06.228164 -0700	SpringBoard	Destination SBNotificationBannerDestination is now ready to receive notifications
default	15:40:06.357860 -0700	locationd	Client com.apple.springboard disconnected
default	15:40:07.076921 -0700	SpringBoard	could not enable test hierarchy: ApplePinningAllowTestCertsiPhoneApplicationSigning not true
default	15:40:07.086126 -0700	securityd	cert[0]: SubjectCommonName =(leaf)[]> 0
default	15:40:07.087573 -0700	securityd	cert[0]: CheckLeafMarkerOid =(leaf)[]> 0
default	15:40:07.136724 -0700	securityd	cert[0]: IssuerCommonName =(path)[]> 0
default	15:40:07.144404 -0700	SpringBoard	 [leaf CheckLeafMarkerOid IssuerCommonName SubjectCommonName]
default	15:40:07.145935 -0700	securityd	cert[0]: SubjectCommonName =(leaf)[]> 0
default	15:40:07.146363 -0700	securityd	cert[0]: CheckLeafMarkerOid =(leaf)[]> 0
default	15:40:07.147099 -0700	SpringBoard	could not enable test hierarchy: ApplePinningAllowTestCertsiPhoneApplicationSigning not true
default	15:40:07.151916 -0700	securityd	cert[0]: IssuerCommonName =(path)[]> 0
default	15:40:07.161409 -0700	SpringBoard	 [leaf CheckLeafMarkerOid IssuerCommonName SubjectCommonName]
default	15:40:07.291466 -0700	SpringBoard	Running <SBAppToAppWorkspaceTransaction: 0x1097ee900> for transition request:
<SBMainWorkspaceTransitionRequest: 0x1746e7400; eventLabel: ActivateApplication = com.softwareops.SwiftVoiceCallKitQuickstart; display: Main; source: HomeScreen> {
applicationContext = <SBWorkspaceApplicationTransitionContext: 0x1744de4c0; background: NO> entities = {
SBLayoutPrimaryRole = <SBWorkspaceApplication: 0x170690950; ID: com.softwareops.SwiftVoiceCallKitQuickstart; layoutRole: primary>;
};
}
default	15:40:07.371901 -0700	UserEventAgent	spd:spd_audit_token_has_legacyvoip_entitlement:865 Audit check failed, error:
default	15:40:07.372364 -0700	UserEventAgent	spd:spd_allow_client_wakeup:213 App linked on IOS_VERSION_10_0+, but doesnt have legacyVoip entitlement
default	15:40:07.378336 -0700	mediaserverd	-CMSessionMgr- cmsmHandleApplicationStateChange: CMSession: Client com.softwareops.SwiftVoiceCallKitQuickstart with pid '858' is now Background Running. Background entitlement: YES
default	15:40:07.378731 -0700	mediaserverd	3138: sid:0x1ebf0, SwiftVoiceCallKi(858), 'prim' new state = Background Running
default	15:40:07.379074 -0700	mediaserverd	-CMSessionMgr- cmsmHandleApplicationStateChange: CMSession: Client com.softwareops.SwiftVoiceCallKitQuickstart with pid '858' is now Foreground Running. Background entitlement: YES
default	15:40:07.379891 -0700	mediaserverd	3138: sid:0x1ebf0, SwiftVoiceCallKi(858), 'prim' new state = Foreground Running
default	15:40:07.385967 -0700	SpringBoard	Disabling home screen icon rotation for reason: SBAppToAppWorkspaceTransaction
default	15:40:07.390727 -0700	CommCenter	#I CSIAppInfo.AppObserver: observe: 1. app got notification state: 4 for app: ; front app = ; calls = 0; inc = 0; active=true
default	15:40:07.393787 -0700	SpringBoard	Disabling home screen icon rotation for reason: SBCrossfadeIconZoomAnimator:0x1097b2df0
default	15:40:07.394025 -0700	SpringBoard	Dismissing banner for notification (null)
default	15:40:07.399874 -0700	CommCenter	#I CSIAppInfo.AppObserver: observe: 4. app got notification state: pid=858 for
default	15:40:07.399988 -0700	CommCenter	#I CSIAppInfo.AppObserver: notifyAboutFrontAppChange: notifyAboutFrontAppChange : app: ; pid: 858; net: 0
default	15:40:07.400132 -0700	CommCenter	#I CSIAppInfo.AppObserver: observe: 1. app got notification state: 8 for app: ; front app = ; calls = 0; inc = 0; active=true
default	15:40:07.400701 -0700	CommCenter	#I CSIAppInfo.AppObserver: observe: 2. app got notification state: new counter=330
default	15:40:07.402697 -0700	sharingd	SystemUI unknown identifier: 'com.softwareops.SwiftVoiceCallKitQuickstart'
default	15:40:07.402962 -0700	sharingd	SystemUI changed: 0x10 -> 0x0
default	15:40:07.426417 -0700	CommCenter	#watchdog #I Callback Watchdog: checkin 1986
default	15:40:07.426580 -0700	CommCenter	#watchdog #I Server Watchdog: checkin 1986
default	15:40:07.440197 -0700	CommCenter	#I BundleID:  is no longer a foreground app
default	15:40:07.440336 -0700	CommCenter	#I BundleID:  is a foreground app
default	15:40:07.441108 -0700	symptomsd	858 com.softwareops.SwiftVoiceCallKitQuickstart: BackgroundRunning (most elevated: BackgroundRunning)
default	15:40:07.441494 -0700	symptomsd	858 com.softwareops.SwiftVoiceCallKitQuickstart: ForegroundRunning (most elevated: ForegroundRunning)
default	15:40:07.442169 -0700	callservicesd	Updated isRunning for  because new application state is 4
default	15:40:07.442331 -0700	callservicesd	Updated isRunning for  because new application state is 8
default	15:40:07.444401 -0700	symptomsd	Entry, display name com.softwareops.SwiftVoiceCallKitQuickstart uuid 540739B1-AC41-3423-9975-A40EA042038F pid 858 isFront 0
default	15:40:07.444576 -0700	symptomsd	UUID 540739B1-AC41-3423-9975-A40EA042038F already removed
default	15:40:07.444654 -0700	symptomsd	Entry, display name com.softwareops.SwiftVoiceCallKitQuickstart uuid 540739B1-AC41-3423-9975-A40EA042038F pid 858 isFront 1
default	15:40:07.445039 -0700	symptomsd	Check for bundle name com.softwareops.SwiftVoiceCallKitQuickstart returns 0
default	15:40:07.445451 -0700	symptomsd	app name com.softwareops.SwiftVoiceCallKitQuickstart isForeground 1  hasForegroundApps 1, current idea of foreground 0 disp (null)
default	15:40:07.445604 -0700	symptomsd	Going to Foreground, new flags 0x0, initial value 0x0, enabled 0
default	15:40:07.445832 -0700	symptomsd	Continue with bundle name com.softwareops.SwiftVoiceCallKitQuickstart, is front 1
default	15:40:07.446140 -0700	symptomsd	com.softwareops.SwiftVoiceCallKitQuickstart: Foreground: true
default	15:40:07.446530 -0700	symptomsd	Set appCompactState object 9858407 for key com.softwareops.SwiftVoiceCallKitQuickstart
default	15:40:07.452513 -0700	symptomsd	CFSM2 foreground (current/proposed/state) in = (1/1/3)
default	15:40:07.452698 -0700	symptomsd	CFSM2 foreground (current/state) out = (1/1)
default	15:40:07.456588 -0700	symptomsd	0x10035e0f0 keys: {
canUseOnAlternate = 1;
}, opt: {
arg1 = "{(\n    "com.apple.mobilemail",\n    "com.softwareops.SwiftVoiceCallKitQuickstart",\n    "com.apple.InCallService"\n)}";
}
default	15:40:07.457000 -0700	symptomsd	Operating on async key: canUseOnAlternate
default	15:40:07.458091 -0700	symptomsd	CFSM dynamic blacklist for app: com.softwareops.SwiftVoiceCallKitQuickstart, (wifi/cell/rnf/jumbo/allflows) 9858407/0/0/0/802, allow, code: WithinAllowance
default	15:40:07.458391 -0700	symptomsd	returning: {
canUseOnAlternate =     {
codes =         {
"com.apple.InCallService" = 1;
"com.apple.mobilemail" = 1;
"com.softwareops.SwiftVoiceCallKitQuickstart" = 1;
};
reasons =         {
"com.apple.InCallService" = AppWhitelisted;
"com.apple.mobilemail" = AppWhitelisted;
"com.softwareops.SwiftVoiceCallKitQuickstart" = WithinAllowance;
};
};
}
default	15:40:07.459031 -0700	symptomsd	CFSM dynamic blacklist returning (value/reason): {
"com.apple.InCallService" = 1;
"com.apple.mobilemail" = 1;
"com.softwareops.SwiftVoiceCallKitQuickstart" = 1;
}/{
"com.apple.InCallService" = AppWhitelisted;
"com.apple.mobilemail" = AppWhitelisted;
"com.softwareops.SwiftVoiceCallKitQuickstart" = WithinAllowance;
}
default	15:40:07.553924 -0700	symptomsd	0x10035e0f0 keys: {
canUseOnAlternate = 1;
}, opt: {
arg1 = "{(\n    "com.apple.InCallService",\n    "com.softwareops.SwiftVoiceCallKitQuickstart",\n    "com.apple.mobilemail"\n)}";
}
default	15:40:07.554150 -0700	symptomsd	Operating on async key: canUseOnAlternate
default	15:40:07.554865 -0700	symptomsd	CFSM dynamic blacklist for app: com.softwareops.SwiftVoiceCallKitQuickstart, (wifi/cell/rnf/jumbo/allflows) 9858407/0/0/0/802, allow, code: WithinAllowance
default	15:40:07.556268 -0700	symptomsd	returning: {
canUseOnAlternate =     {
codes =         {
"com.apple.InCallService" = 1;
"com.apple.mobilemail" = 1;
"com.softwareops.SwiftVoiceCallKitQuickstart" = 1;
};
reasons =         {
"com.apple.InCallService" = AppWhitelisted;
"com.apple.mobilemail" = AppWhitelisted;
"com.softwareops.SwiftVoiceCallKitQuickstart" = WithinAllowance;
};
};
}
default	15:40:07.556536 -0700	symptomsd	CFSM dynamic blacklist returning (value/reason): {
"com.apple.InCallService" = 1;
"com.apple.mobilemail" = 1;
"com.softwareops.SwiftVoiceCallKitQuickstart" = 1;
}/{
"com.apple.InCallService" = AppWhitelisted;
"com.apple.mobilemail" = AppWhitelisted;
"com.softwareops.SwiftVoiceCallKitQuickstart" = WithinAllowance;
}
default	15:40:07.690145 -0700	SwiftVoiceCallKitQuickstart	[VERBOSE TwilioVoice] Application did become active
default	15:40:07.690898 -0700	SwiftVoiceCallKitQuickstart	[DEBUG TVOReachability] Reachability Flag Status: -R ------- networkStatusForFlags
default	15:40:08.084130 -0700	SpringBoard	Undimming for source: programmatic
default	15:40:08.084598 -0700	SpringBoard	returning the workspace lock time (-1.000000) from _nextLockTimeDuration
default	15:40:08.086741 -0700	SpringBoard	returning the workspace dim time (-1.000000) from _nextIdleTimeDuration
default	15:40:08.087070 -0700	SpringBoard	Disabling idle timer because the next idle duration < 0.
default	15:40:08.088251 -0700	SpringBoard	Setting _lastBKUserEventTimerMode=0 with duration=-1.000000
default	15:40:08.101963 -0700	SpringBoard	Enabling home screen icon rotation for reason: SBCrossfadeIconZoomAnimator:0x1097b2df0
default	15:40:08.104992 -0700	SpringBoard	Starting device motion, mode=0x22,useAccelerometer=0,useGyro=1,useCompass=0,fUseNorthRef=0,buildingGYTT=0
default	15:40:08.107092 -0700	backboardd	Turning on orientation events.
default	15:40:08.108473 -0700	backboardd	fHasSeenACaseLatchCoverOnce, 0
default	15:40:08.111488 -0700	backboardd	Starting orientation detection with accelFrequency 10.000000, isIpad, 0, decimationRate, 1
default	15:40:08.124815 -0700	backboardd	Waiting for the first orientation to come in
error	15:40:08.125262 -0700	backboardd	Unable to bootstrap_look_up port with name .gsEvents: unknown error code (1102)
default	15:40:08.127917 -0700	backboardd	Notify from, Unexpected -> FaceUp
default	15:40:08.128429 -0700	backboardd	Received orientation. (Ambiguous to FaceUp) Timestamp 29958.927225
default	15:40:08.128701 -0700	backboardd	Updating client handler: Orientation FaceUp, Callback mode: -1
default	15:40:08.128971 -0700	backboardd	Got latest sample: 5 @ 29958.927225
default	15:40:08.129670 -0700	backboardd	Effective device orientation changed to: faceUp
default	15:40:08.136261 -0700	SpringBoard	SB orientation locked: NO; user lock: NO, overrides: NO
default	15:40:08.136426 -0700	SpringBoard	Enabling home screen icon rotation for reason: SBAppToAppWorkspaceTransaction
default	15:40:08.136533 -0700	SpringBoard	Root transaction complete: <SBAppToAppWorkspaceTransaction: 0x1097ee900>
default	15:40:08.148912 -0700	locationd	Client com.apple.springboard connected
default	15:40:08.149084 -0700	locationd	getClientEffectiveRegistrationResult, /System/Library/CoreServices/SpringBoard.app/SpringBoard, com.apple.springboard, , CLClientRegistrationResult, kCLClientRegistrationResultFailedUnavailable, CLCommonLocationServicesEnabled, 1
default	15:40:08.149340 -0700	locationd	message 'kCLConnectionMessageGyroBiasEstimation' received from client 'com.apple.springboard'
default	15:40:08.149987 -0700	locationd	Client com.apple.springboard (0x10288ec00) is subscribing to notification kCLConnectionMessageGyroBiasEstimation
default	15:40:08.154850 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client 'com.apple.springboard'
default	15:40:08.155406 -0700	locationd	Client com.apple.springboard disconnected
default	15:40:08.233634 -0700	SpringBoard	Destination SBNotificationBannerDestination is now ready to receive notifications
default	15:40:09.243002 -0700	identityservicesd	Tearing Down Global Link Due To Inactivity
default	15:40:09.243622 -0700	identityservicesd	disconnectGlobalLink - sessionID 12345678-7654-DADA-DADA-DADADADADADA
error	15:40:09.899124 -0700	assistantd	ADAnalyticsEventGroupsCreate Dropped 4 events because no key events can be found.
default	15:40:12.482478 -0700	symptomsd	eLQM: Received BB link fingerprint notification (type = 17): payload = <01000000 7c09ac01 7c010000 00000000 00000000 64000000 32000000 0a000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000>
default	15:40:12.500841 -0700	CommCenter	QMI: Svc=0xe7(ELQM) Ind MsgId=0x0002 Bin=[]
default	15:40:12.506665 -0700	symptomsd	eLQM: Link fingerprint for Cell 0: Cell Id = , Duration = (380, 0, 0), LQM = (100, 50, 10), Throughput(UL, DL) = (0, 0) Kbps
default	15:40:12.507320 -0700	symptomsd	eLQM: Link fingerprint for Cell 1: Cell Id = , Duration = (0, 0, 0), LQM = (0, 0, 0), Throughput(UL, DL) = (0, 0) Kbps
default	15:40:12.507607 -0700	symptomsd	eLQM: Link fingerprint for Cell 2: Cell Id = , Duration = (0, 0, 0), LQM = (0, 0, 0), Throughput(UL, DL) = (0, 0) Kbps
default	15:40:12.508215 -0700	symptomsd	eLQM: Link fingerprint for Cell 3: Cell Id = , Duration = (0, 0, 0), LQM = (0, 0, 0), Throughput(UL, DL) = (0, 0) Kbps
default	15:40:12.509874 -0700	symptomsd	eLQM: Link fingerprint for Cell 4: Cell Id = , Duration = (0, 0, 0), LQM = (0, 0, 0), Throughput(UL, DL) = (0, 0) Kbps
default	15:40:12.730023 -0700	locationd	{"msg":"adapter details", "adaperDescription":"usb host", "batteryChargerType":"kChargerTypeUsb"}
default	15:40:12.730396 -0700	locationd	{"msg":"battery capacity info", "batteryStatus":"", "":"", "currentCapacity":"", "maximumCapacity":"1800", "batteryIsDifferent":"8"}
default	15:40:12.745477 -0700	coreduetd	CDDBatteryMonitor:	received batterycallback, currentPercentage:100.000000!
default	15:40:22.380941 -0700	CommCenter	#watchdog #I Callback Watchdog: checkin 1987
default	15:40:22.382667 -0700	CommCenter	#watchdog #I Server Watchdog: checkin 1987
default	15:40:24.299957 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/PrivateFrameworks/PassKitCore.framework'
default	15:40:24.627115 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/PassbookRelevancy.bundle'
default	15:40:24.632660 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/PrivateFrameworks/PassKitCore.framework'
default	15:40:25.729807 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client 'com.apple.HealthKit'
default	15:40:25.731522 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client 'com.apple.HealthKit'
default	15:40:25.732740 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client 'com.apple.HealthKit'
default	15:40:26.123895 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/PrivateFrameworks/CoreParsec.framework'
default	15:40:26.616299 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/PrivateFrameworks/HomeKitDaemon.framework'
default	15:40:29.974959 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/PrivateFrameworks/CoreParsec.framework'
default	15:40:31.708286 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/PrivateFrameworks/WirelessDiagnostics.framework'
default	15:40:32.781412 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client 'com.apple.locationd'
default	15:40:33.226161 -0700	locationd	{"msg":"adapter details", "adaperDescription":"usb host", "batteryChargerType":"kChargerTypeUsb"}
default	15:40:33.226683 -0700	locationd	{"msg":"battery capacity info", "batteryStatus":"", "":"", "currentCapacity":"", "maximumCapacity":"1800", "batteryIsDifferent":"8"}
default	15:40:33.253596 -0700	coreduetd	CDDBatteryMonitor:	received batterycallback, currentPercentage:100.000000!
default	15:40:36.243573 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/Frameworks/CoreTelephony.framework'
default	15:40:37.123283 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/WifiCalling.bundle'
default	15:40:37.367016 -0700	CommCenter	#watchdog #I Callback Watchdog: checkin 1988
default	15:40:37.367567 -0700	CommCenter	#watchdog #I Server Watchdog: checkin 1988
default	15:40:37.997106 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/PrivateFrameworks/MobileWiFi.framework'
default	15:40:40.976883 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/Traffic.bundle'
default	15:40:40.981136 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/MotionCalibration.bundle'
default	15:40:40.982433 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/CompassCalibration.bundle'
default	15:40:40.987719 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/TimeZone.bundle'
default	15:40:40.990305 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/MotionCalibration.bundle'
default	15:40:40.991752 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/MotionCalibration.bundle'
default	15:40:40.993069 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/AppGenius.bundle'
default	15:40:40.994226 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/Routine.bundle'
default	15:40:40.995324 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/AppSuggestions.bundle'
default	15:40:41.023365 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/Traffic.bundle'
default	15:40:41.025414 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client 'com.apple.AppStore'
default	15:40:41.027490 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/MotionCalibration.bundle'
default	15:40:41.029294 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/AppGenius.bundle'
default	15:40:41.031564 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/Routine.bundle'
default	15:40:41.034370 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/Traffic.bundle'
default	15:40:41.036322 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/Traffic.bundle'
default	15:40:41.038108 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/Routine.bundle'
default	15:40:41.039912 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/AppGenius.bundle'
default	15:40:41.142540 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/Routine.bundle'
default	15:40:42.129123 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/MagicalMoments.bundle'
default	15:40:44.121201 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/TimeZone.bundle'
default	15:40:47.309883 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client 'com.apple.Home'
default	15:40:47.680431 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/NavdLocationBundleiOS.bundle'
default	15:40:47.696061 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/NavdLocationBundleiOS.bundle'
default	15:40:47.942602 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/PrivateFrameworks/BulletinBoard.framework'
default	15:40:48.157756 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/RemindersAlerts.bundle'
default	15:40:48.293207 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/LocationBundles/CalendarLocation.bundle'
default	15:40:50.047354 -0700	locationd	message 'kCLConnectionMessageWatchdog' received from client '/System/Library/PrivateFrameworks/FMF.framework'
default	15:40:52.371919 -0700	CommCenter	#watchdog #I Callback Watchdog: checkin 1989
default	15:40:52.374096 -0700	CommCenter	#watchdog #I Server Watchdog: checkin 1989
default	15:40:53.768110 -0700	locationd	{"msg":"adapter details", "adaperDescription":"usb host", "batteryChargerType":"kChargerTypeUsb"}
default	15:40:53.769846 -0700	locationd	{"msg":"battery capacity info", "batteryStatus":"", "":"", "currentCapacity":"", "maximumCapacity":"1800", "batteryIsDifferent":"8"}
default	15:40:53.781181 -0700	coreduetd	CDDBatteryMonitor:	received batterycallback, currentPercentage:100.000000!
default	15:41:00.015067 -0700	accountsd	" () received"
default	15:41:00.061429 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25] BTA-com.apple.timed: Invalidating simple timer <PCSimpleTimer: 0x153e23b90>
default	15:41:00.062130 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: <PCDispatchTimer: 0x153f2c680> is invalidated
Callstack (
0   PersistentConnection                0x00000001868e85cc  + 116
1   PersistentConnection                0x00000001868e5fb8  + 292
2   com.apple.BackgroundTaskAgentPlugin 0x0000000101e13b34 com.apple.BackgroundTaskAgentPlugin + 15156
3   com.apple.BackgroundTaskAgentPlugin 0x0000000101e12d8c com.apple.BackgroundTaskAgentPlugin + 11660
4   com.apple.BackgroundTaskAgentPlugin 0x0000000101e12978 com.apple.BackgroundTaskAgentPlugin + 10616
5   libdispatch.dylib                   0x000000018299a1bc  + 16
6   libdispatch.dylib                   0x00000001829a6f94  + 576
7   libdispatch.dylib                   0x00000001829b3634  + 204
8   libdispatch.dylib                   0x000000018299c160  + 820
9   libdispatch.dylib                   0x00000001829a8210  + 468
10  libdispatch.dylib                   0x000000018299d9a4 <redacte
default	15:41:00.062583 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: <PCDispatchTimer: 0x153f2c680> dealloced
default	15:41:00.063178 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: <PCDispatchTimer: 0x153f2edc0> is invalidated
Callstack (
0   PersistentConnection                0x00000001868e85cc  + 116
1   PersistentConnection                0x00000001868e5fd4  + 320
2   com.apple.BackgroundTaskAgentPlugin 0x0000000101e13b34 com.apple.BackgroundTaskAgentPlugin + 15156
3   com.apple.BackgroundTaskAgentPlugin 0x0000000101e12d8c com.apple.BackgroundTaskAgentPlugin + 11660
4   com.apple.BackgroundTaskAgentPlugin 0x0000000101e12978 com.apple.BackgroundTaskAgentPlugin + 10616
5   libdispatch.dylib                   0x000000018299a1bc  + 16
6   libdispatch.dylib                   0x00000001829a6f94  + 576
7   libdispatch.dylib                   0x00000001829b3634  + 204
8   libdispatch.dylib                   0x000000018299c160  + 820
9   libdispatch.dylib                   0x00000001829a8210  + 468
10  libdispatch.dylib                   0x000000018299d9a4 <redacte
default	15:41:00.063518 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: <PCDispatchTimer: 0x153f2edc0> dealloced
default	15:41:00.064300 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25] BTA-com.apple.timed: Started simple timer <PCSimpleTimer: 0x153dceb40> with fire date [2018-03-26 15:48:06 -0700]
default	15:41:00.064932 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: <PCDispatchTimer: 0x153d8f4b0> initialized with target <PCSimpleTimer: 0x153dceb40> selector _preventSleepFired timerSource <OS_dispatch_source: 0x153f10020>
default	15:41:00.065672 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: <PCDispatchTimer: 0x153d71f00> initialized with target <PCSimpleTimer: 0x153dceb40> selector _fireTimerFired timerSource <OS_dispatch_source: 0x153f55590>
default	15:41:00.066472 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: Disabling power monitoring for <PCSimpleTimer: 0x153e23b90> - 2 timers
default	15:41:00.066929 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25] BTA-com.apple.timed: <PCSimpleTimer: 0x153dceb40> created preventSleepTimer <PCDispatchTimer: 0x153d8f4b0> and fireTimer <PCDispatchTimer: 0x153d71f00> on queue <OS_dispatch_queue: PCSimpleTimer-timerQ[0x153dcbec0]>
default	15:41:00.067413 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: <PCDispatchTimer: 0x153d71f00> start with target <CUTWeakReference: 0x153d8a5a0> selector _fireTimerFired firetime<PHONE_NUMBER>3709551615 timerSource <OS_dispatch_source: 0x153f55590>
default	15:41:00.067772 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: <PCDispatchTimer: 0x153d8f4b0> start with target <CUTWeakReference: 0x153f54420> selector _preventSleepFired firetime<PHONE_NUMBER>3709551615 timerSource <OS_dispatch_source: 0x153f10020>
default	15:41:00.068251 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: <PCDispatchTimer: 0x153d8f4b0> setFireDate 4001-01-01 00:00:00 +0000 and start with target <PCSimpleTimer: 0x153dceb40> selector _preventSleepFired fireTime<PHONE_NUMBER>3709551615 deltaNanosec 2310-07-06 15:28:16 -0700 timerSource <OS_dispatch_source: 0x153f10020>
default	15:41:00.068510 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: Enabling power monitoring for <PCSimpleTimer: 0x153dceb40> - 3 timers
default	15:41:00.071084 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: <PCDispatchTimer: 0x153d71f00> setFireDate 2018-03-26 22:48:06 +0000 and start with target <PCSimpleTimer: 0x153dceb40> selector _fireTimerFired fireTime<PHONE_NUMBER>80 deltaNanosec 2018-03-26 15:48:06 -0700 timerSource <OS_dispatch_source: 0x153f55590>
default	15:41:00.071932 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25] BTA-PeriodicConditionMonitor: Invalidating timer <PCPersistentTimer: 0x153d828f0>
default	15:41:00.072317 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25] BTA-PeriodicConditionMonitor: Invalidating simple timer <PCSimpleTimer: 0x153f11bd0>
default	15:41:00.073238 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: <PCDispatchTimer: 0x153f0a920> is invalidated
Callstack (
0   PersistentConnection                0x00000001868e85cc  + 116
1   PersistentConnection                0x00000001868e5fb8  + 292
2   PersistentConnection                0x00000001868d2170  + 188
3   com.apple.BackgroundTaskAgentPlugin 0x0000000101e13f28 com.apple.BackgroundTaskAgentPlugin + 16168
4   com.apple.BackgroundTaskAgentPlugin 0x0000000101e12d8c com.apple.BackgroundTaskAgentPlugin + 11660
5   com.apple.BackgroundTaskAgentPlugin 0x0000000101e12978 com.apple.BackgroundTaskAgentPlugin + 10616
6   libdispatch.dylib                   0x000000018299a1bc  + 16
7   libdispatch.dylib                   0x00000001829a6f94  + 576
8   libdispatch.dylib                   0x00000001829b3634  + 204
9   libdispatch.dylib                   0x000000018299c160  + 820
10  libdispatch.dylib                   0x00000001829a8210 <redacte
default	15:41:00.073539 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: <PCDispatchTimer: 0x153f0a920> dealloced
default	15:41:00.074078 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: <PCDispatchTimer: 0x153e5baa0> is invalidated
Callstack (
0   PersistentConnection                0x00000001868e85cc  + 116
1   PersistentConnection                0x00000001868e5fd4  + 320
2   PersistentConnection                0x00000001868d2170  + 188
3   com.apple.BackgroundTaskAgentPlugin 0x0000000101e13f28 com.apple.BackgroundTaskAgentPlugin + 16168
4   com.apple.BackgroundTaskAgentPlugin 0x0000000101e12d8c com.apple.BackgroundTaskAgentPlugin + 11660
5   com.apple.BackgroundTaskAgentPlugin 0x0000000101e12978 com.apple.BackgroundTaskAgentPlugin + 10616
6   libdispatch.dylib                   0x000000018299a1bc  + 16
7   libdispatch.dylib                   0x00000001829a6f94  + 576
8   libdispatch.dylib                   0x00000001829b3634  + 204
9   libdispatch.dylib                   0x000000018299c160  + 820
10  libdispatch.dylib                   0x00000001829a8210 <redacte
default	15:41:00.074641 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: <PCDispatchTimer: 0x153e5baa0> dealloced
default	15:41:00.075046 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25] BTA-PeriodicConditionMonitor: Canceling system wake for simpletimer [2018-03-26 16:36:43 -0700]
default	15:41:00.075786 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: Request to schedule wake 0 date 2018-03-26 16:36:43 -0700 leeway 0 service identifier BTA-PeriodicConditionMonitor unique identifier <PCSimpleTimer: 0x153f11bd0>
default	15:41:00.076378 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25] BTA-PeriodicConditionMonitor: <PCPersistentTimer: 0x153dc3150> created <PCSimpleTimer: 0x153f25d80>
default	15:41:00.076700 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25] BTA-PeriodicConditionMonitor: Started simple timer <PCSimpleTimer: 0x153f25d80> with fire date [2018-03-26 16:41:00 -0700]
default	15:41:00.076871 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: <PCDispatchTimer: 0x153f54340> initialized with target <PCSimpleTimer: 0x153f25d80> selector _preventSleepFired timerSource <OS_dispatch_source: 0x153f29fd0>
default	15:41:00.080109 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: <PCDispatchTimer: 0x153ea08a0> initialized with target <PCSimpleTimer: 0x153f25d80> selector _fireTimerFired timerSource <OS_dispatch_source: 0x15501b160>
default	15:41:00.080419 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25] BTA-PeriodicConditionMonitor: <PCSimpleTimer: 0x153f25d80> created preventSleepTimer <PCDispatchTimer: 0x153f54340> and fireTimer <PCDispatchTimer: 0x153ea08a0> on queue <OS_dispatch_queue: PCSimpleTimer-timerQ[0x153f11b10]>
default	15:41:00.080554 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: <PCDispatchTimer: 0x153ea08a0> start with target <CUTWeakReference: 0x153ee2d10> selector _fireTimerFired firetime<PHONE_NUMBER>3709551615 timerSource <OS_dispatch_source: 0x15501b160>
default	15:41:00.080886 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: <PCDispatchTimer: 0x153f54340> start with target <CUTWeakReference: 0x153dcb3e0> selector _preventSleepFired firetime<PHONE_NUMBER>3709551615 timerSource <OS_dispatch_source: 0x153f29fd0>
default	15:41:00.081056 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: <PCDispatchTimer: 0x153f54340> setFireDate 2018-03-26 23:40:45 +0000 and start with target <PCSimpleTimer: 0x153f25d80> selector _preventSleepFired fireTime<PHONE_NUMBER>58 deltaNanosec 2018-03-26 16:40:45 -0700 timerSource <OS_dispatch_source: 0x153f29fd0>
default	15:41:00.081198 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: Disabling power monitoring for <PCSimpleTimer: 0x153f11bd0> - 2 timers
default	15:41:00.081356 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: Enabling power monitoring for <PCSimpleTimer: 0x153f25d80> - 3 timers
default	15:41:00.081543 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: Cancelling scheduled wake for 2018-03-26 16:36:43 -0700 wake identifier com.apple.persistentconnection[UserEventAgent,25,0x153f11bd0,BTA-PeriodicConditionMonitor]
default	15:41:00.081659 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: <PCDispatchTimer: 0x153ea08a0> setFireDate 2018-03-26 23:41:00 +0000 and start with target <PCSimpleTimer: 0x153f25d80> selector _fireTimerFired fireTime<PHONE_NUMBER>50 deltaNanosec 2018-03-26 16:41:00 -0700 timerSource <OS_dispatch_source: 0x15501b160>
default	15:41:00.081816 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25] BTA-PeriodicConditionMonitor: <PCSimpleTimer: 0x153f25d80> Existing wake at (null) re-scheduling to 2018-03-26 16:40:45 -0700 with leeway of 0
default	15:41:00.081959 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: Request to schedule wake 1 date 2018-03-26 16:40:45 -0700 leeway 0 service identifier BTA-PeriodicConditionMonitor unique identifier <PCSimpleTimer: 0x153f25d80>
default	15:41:00.082259 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: <PCInterfaceUsabilityMonitor: 0x153dbe910> NonCellular: isInterfaceUsable? YES reachable YES linkQuality 100 isNetworkCaptive? NO
default	15:41:00.082367 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25] BTA-PeriodicConditionMonitor: <PCPersistentTimer: 0x153dc3150> calculating _earlyFireDate. powerStateDetectionSupported = NO = (detectionSupported(NO) && (wwanIsUp(NO) || ! internetReachable(YES)))
default	15:41:00.082525 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25] BTA-PeriodicConditionMonitor: Last system wake date (2018-03-26 14:53:48 -0700) was longer than half of the timer duration, so setting minimum fire date to fire date.
default	15:41:00.082641 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25] BTA-PeriodicConditionMonitor: <PCPersistentTimer: 0x153dc3150> Device is plugged in, overriding earlyFireProportion to be 1.0
default	15:41:00.082814 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25] BTA-PeriodicConditionMonitor: <PCPersistentTimer: 0x153dc3150> Calculated minimum fire date [2018-03-26 16:41:00 -0700] (100%) with fire date [2018-03-26 16:41:00 -0700], start date [2018-03-26 15:41:00 -0700], minimum early fire proportion 0.45, power state detection supported: no, in high power state: no
default	15:41:00.082923 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: Wake cancel for 'com.apple.persistentconnection[UserEventAgent,25,0x153f11bd0,BTA-PeriodicConditionMonitor]'(com.apple.persistentconnection[UserEventAgent,25,schedulingwake-BTA-PeriodicConditionMonitor-SystemWakeManager(0x153f2edc0)]) completed for [2018-03-26 16:36:43 -0700] (took 0.004 seconds; result code 0)
default	15:41:00.083029 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: Scheduling a wake for date 2018-03-26 16:40:45 -0700 leeway 0 wake identifier com.apple.persistentconnection[UserEventAgent,25,0x153f25d80,BTA-PeriodicConditionMonitor]
default	15:41:00.083175 -0700	UserEventAgent	2018-03-26 15:41:00 -0700 UserEventAgent[25]: Wake schedule for 'com.apple.persistentconnection[UserEventAgent,25,0x153f25d80,BTA-PeriodicConditionMonitor]'(com.apple.persistentconnection[UserEventAgent,25,schedulingwake-BTA-PeriodicConditionMonitor-SystemWakeManager(0x153d452c0)]) completed for [2018-03-26 16:40:45 -0700] (took 0.002 seconds; result code 0)

I noticed this log line from during the time the network conditioner was on:

default	16:02:29.869540 -0700	apsd	2018-03-26 16:02:29 -0700 apsd[85] com.apple.apsd(sandbox.push.apple.com)-NonCellular: <PCPersistentTimer: 0x10033b5f0> Calculated minimum fire date [2018-03-26 16:15:06 -0700] (100%) with fire date [2018-03-26 16:15:06 -0700], start date [2018-03-26 16:02:29 -0700], minimum early fire proportion 0, power state detection supported: no, in high power state: no

I tried calling a few more times between 16:02 and 16:10 and didn't receive any of the notifications. Then, at 16:11 I called and received the notification. It seems like something (Possibly Apple) is discarding notifications for a certain period of time after failure to deliver.

Hi @kjmacaul
Not sure if that's the root cause but I am seeing messages about invalid:
UserEventAgent	spd:spd_audit_token_has_legacyvoip_entitlement:865 Audit check failed, error:
UserEventAgent	spd:spd_allow_client_wakeup:213 App linked on IOS_VERSION_10_0+, but doesnt have legacyVoip entitlement

Still not sure why these messages are logged, but can you help us check couple of things in the project settings?

The YOUR_APP.entitlement file in the project tree
The entitlement file should have {APS Environment: development} or {APS Environment: production}
Signing, of course
In the "Capabilities" tab, both bullets of the "Push Notifications" section should be checked

I also checked the service status but things seem to be working at least from the last update https://developer.apple.com/system-status
By the way, our Android expert is asking anxiously if this is happening on Android.
Thanks

The entitlement file is present with APNS Environment: development.
The app is properly signed (automatic signing enabled).
Both steps under "Push Notifications" capabilities have a checkmark.
Audio, AirPlay and Picture in Picture and Remote Notifications are enabled in the Background Modes section.

And yes, the issue is also happening on Android.

And is it resolved on Android? we are curious about how it is reproduced on Android.

It appear to be exactly the same case on Android. Right down to my last comment of the notifications being discarded for some period of time and then being received again.
Since Android doesn't have the Network Link Conditioner, we used an iPhone as a personal hotspot and connected the Android device to it. We were then able to use the Network Link Conditioning settings on the iPhone and follow the same steps I listed earlier.

Thanks @kjmacaul!
Another thing I'd like to confirm - when the app is launched, iOS or Android, call notifications are being sent and received fine. The no-notification issue only happens after the network dance, is that correct?

That is correct. As shown in the video I provided, a call was first received successfully before changing the settings to simulate a bad network.

FWIW, we've just done a quick investigation but we couldn't find any outage on the service path where the call and notification happen.
Now that things seem to be back normal and I can't ask you to try the cellular network (in the video the devices were connected to wifi) - could it be that when the conditioner was switched off, it took longer than usual for the socket connection responsible for VoIP Service to re-establish, therefore when we tried to make the second call immediately, the VoIP notification couldn't make it through?
Anyway, really appreciate your patience and your help providing us debugging info.
Thanks!
-bobie

Sorry, it seems my last few messages were unclear. I wasn't trying to say that the issue has been resolved. The issue is still easily reproducible by us. I was trying to say that once a device enters this "bad state" of not receiving notifications, it will not receive any notifications for approximately 10 minutes from our observations. After about 10 minutes, the device will begin receiving new notifications again.
We have other devices that have cellular service. We were able to reproduce on those devices as well using the same steps with wifi disabled.

Hi @kjmacaul
Unfortunately the SDK does not have control to the socket connection between Apple APN service and the mobile devices, if the phone happens to experience connectivity problem while the call notification is being sent and thus results a missed call, one can only rely on the retry mechanism from the notification platform (Apple/FCM/GCM) to make sure messages are delivered.

I'll add my 2 cents here. I've noticed that notifications delivery on APN depends a lot on the network conditions. The issue @kjmacaul is experiencing I've noticed it also in production, it happens so much that we started tracking clients availability with a keep-alive VoIP notification, but then we had to disable it because of the number of notifications that weren't delivered.
While its true that Twilio doesn't controls what happens between the Notification Platform and the devices, its also true that the resulting experience from an end-user standpoint is not right: The user making the call will think the phone on the other side is ringing, and the user receiving the call will not see anything.
Right now we're thinking of handling that on the app logic by setting a timeout on the server before routing the call to VoIP a client, and having the client send an acknowledge that it started ringing. If that acknoledge is not received in the server before the timeout we will cancel the call leg and do whatever is next (say the call failed, hangup, route the call to an alternative client or to a cellphone number).
However, it'll be nice if that kind of failures are detected by Twilio itself, and if the TwiML dials a VoIP client and its not reachable then have a fail status instead of a ringing with no answer as a result, because that is not what is really happening.


"Vârteșcoiu" is listed in the drop down menu

Description:
"Vârteșcoiu"  is listed in the drop-down menu alongside its corresponding county according to the law
Precondition:
The website is up an running.

Step 1
Type "Vârteșcoiu" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Vârteșcoiu ,  VRANCEA".


PartsUnlimited Empty repos

Starting today onward, the PartsUnlimited DevOps generator provide an empty repos. This has happen to me and my participants. I am sure it can be reproduce.

Confirming this issue. I just reproduced it a few times. I tried templates from the General Section and from the DevOpsLabs section and only the ones from General seem to have this problem. I use different templates fairly often. I will try to look into this over the weekend and contribute a fix.

Hi,
Could you please retry?

Dear All,
I have tested and the generator is working fine now. Thank you for the
prompt response.
Have a nice day.
On Fri, May 22, 2020 at 10:25 AM Akshay H<EMAIL_ADDRESS>wrote:

Hi,
Could you please retry?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/AzureDevOpsDemoGenerator/issues/263#issuecomment-632442450,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APVKSIJIZXGMXEKHQ356ETDRSXPALANCNFSM4NHH3VKA
.

@devops-app thank you for your confirmation. We are closing the issue.
Thanks.


Non-destructive Cropping

Is there an option to revert to the original image after cropping? Often times I need to try various croppings and I think the only way to do this currently is by reuploading the original image.
Thanks!

Just saw that a feature request for non-destructive resizing was open.


Format URL links

Format URL links

Hi @singhkay, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (kasing). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@singhkay : Thanks for your contribution to the Azure documentation! The author, @singhkay, has been notified to review your proposed change.

@singhkay - Please use the private repository - see "Authors working in the public repo" for details.


UI CSS interfers with custom blade on home page.

Bug report -  Default theme!
Title
The CSS of of the default theme overwrites the @include('...') on the shop home page.
Issue Description
I want to have a simple calculator on the home page. I found this one, copied CSS and HTML to a Blade view.
Expected result

It actually appears correctly, briefly on page load, then it goes to that actual result below.
Actual result

@jitendra-webkul  this might help- Tailwind CSS - I've checked out the UI CSS it seems largely abandoned and it's very opinionated  CSS! The good thing about it: very clean UI, and semi-mobile friendly.
However, the downside something is overriding the CSS in my blade, not sure if UI CSS or Laravel.
My personal feeling, is that go with a CSS framework that is under active use, and has a good following.
The nice thing about Tailwind, it's that it makes it very easy to customise the look and feel without changing CSS everywhere. Much easier to create themes. Hope this helps.
There seems to be a lot of UX issues with the Velocity theme, which why I'm not using it currently.

Hi @adavie1
Could you please share blade file you've created and the screenshot, where you've included that file.

I hope above reply solved your issue. I am closing this issue for now. Feel free to reopen this issue if needed.


Sdk219 embeding

Issue #, if available:
Add embedding as input for mistral model in transformers-neuronx(Neuron SDK 2.19)
Description of changes:
Have tested this change.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

update title


kapp-controller should allow configuration of metrics service port

Describe the problem/challenge you have
if kapp-controller is run with hostNetwork=true on the Deployment, default metrics service port 8080 may conflict with other services running on the node. need to determine whats the best configuration -- should port be some high numbered port? should it be configurable via flag?

Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.

Leaving some notes here on implementation details.
The metrics service port can be configured here: https://github.com/vmware-tanzu/carvel-kapp-controller/blob/69c59a6e0d9007213ecddd8b8d934c3e47f822f9/cmd/controller/run.go#L56
It can be set using the MetricsBindAddress:
property: mgr, err := manager.New(restConfig, manager.Options{Namespace: opts.Namespace,
    Scheme: kcconfig.Scheme, MetricsBindAddress: "8080"})

Flags for kapp-controller can be found here: https://github.com/vmware-tanzu/carvel-kapp-controller/blob/69c59a6e0d9007213ecddd8b8d934c3e47f822f9/cmd/main.go#L25


Support for Python 3.12-style f-strings

Great project!
I saw that you moved your Python parsing into Rust, and there's one limitation I want to bring to your attention. At a high level, the problem is that by using a third-party parser, you're not guaranteed to support parsing all valid Python programs for the current Python version (i.e., whatever version the user is running), since the parser may not support all syntax.
In this case, the acute limitation is that the RustPython parser doesn't support the revised f-string syntax from Python 3.12. So any projects that use Python 3.12-style f-strings won't be analyzable by Deptry right now.
To reproduce, create a file like foo/__init__.py, with f"abc{"def"}". Then run deptry foo:
❯ deptry foo
Scanning 1 file...
Traceback (most recent call last):
  File "/Users/crmarsh/.local/share/rtx/installs/python/3.12.1/bin/deptry", line 8, in <module>
    sys.exit(deptry())
             ^^^^^^^^
  File "/Users/crmarsh/.local/share/rtx/installs/python/3.12.1/lib/python3.12/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/crmarsh/.local/share/rtx/installs/python/3.12.1/lib/python3.12/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/Users/crmarsh/.local/share/rtx/installs/python/3.12.1/lib/python3.12/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/crmarsh/.local/share/rtx/installs/python/3.12.1/lib/python3.12/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/crmarsh/.local/share/rtx/installs/python/3.12.1/lib/python3.12/site-packages/deptry/cli.py", line 356, in deptry
    ).run()
      ^^^^^
  File "/Users/crmarsh/.local/share/rtx/installs/python/3.12.1/lib/python3.12/site-packages/deptry/core.py", line 83, in run
    for module, locations in get_imported_modules_from_list_of_files(all_python_files).items()
                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/crmarsh/.local/share/rtx/installs/python/3.12.1/lib/python3.12/site-packages/deptry/imports/extract.py", line 28, in get_imported_modules_from_list_of_files
    rust_result = get_imports_from_py_files(py_files)
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SyntaxError: Error parsing file foo/__init__.py: SyntaxError: Error parsing file foo/__init__.py: invalid syntax. Got unexpected token 'def' at byte offset 7

We (Astral) did add support for type statements to the RustPython parser (https://github.com/RustPython/Parser/pull/97), so it does support PEP 695, which was another big syntax change in Python 3.12. But we've since forked the parser. Our updates to Ruff's parser to support Python 3.12-style f-strings were never backported to RustPython, and our parser and AST have diverged a lot more since then.
(This genuinely isn't intended to be an advertisement for Ruff's parser. In fact, while you're obviously welcome to use it, we don't publish it to crates.io and we don't make any guarantees around its public API / stability right now, so having users that depend on it is actually not totally desirable for us. I just wanted you to be aware of some of the limitations that come with using a non-CPython parser.)

Hi Charlie, nice to see you there 🙂
I must say that this is not something we were aware of, so thanks a lot for taking the time to write this heads up, this is indeed an important limitation to be aware of.

In fact, while you're obviously welcome to use it, we don't publish it to crates.io and we don't make any guarantees around its public API / stability right now, so having users that depend on it is actually not totally desirable for us. I just wanted you to be aware of some of the limitations that come with using a non-CPython parser.

The idea of supporting new Python 3.12 syntax (and future changes in newer versions) by switching to Ruff's parser instead of having syntax errors, even if this means having breaking changes to handle from time to time, looks like a good deal to me.
Given that we are mostly interested in imports and their locations when parsing the AST, the rate of breaking changes in the API might be something we could accommodate.
Do you know other projects that use Ruff's parser instead of RustPython one? And since you mention some reservation about having projects depend on Ruff's parser (I guess mostly because you don't want to commit on a public API, as this is intended to be use Ruff, which is perfectly understandable), how would you feel if deptry was to switch to Ruff's parser to support newer Python syntax?

Thanks @charliermarsh for raising this issue and for your clear explanation.
I agree with @mkniewallner that this project could definitely benefit by switching to ruff's internal parser, with the obvious note that we would take responsibility for that and that, won't expect a stable API, and we would simply deal with any future breaking changes as they come. Give the limited scope of deptry I think that sounds doable.
I created a quick draft PR to see what the impact currently would be, and that is very limited.
Curious for your thoughts on this :)

I think it's totally reasonable for you all to use Ruff's parser. It would obviously be a shame for us to invest all this effort in building a greater parser, only for other projects to have no way to benefit from it. I mostly just want to be clear in setting expectations around it, i.e.:

It'd need to be pulled in as a Git dependency, as in your PR, since we aren't planning to publish it to crates.io yet. (I assume we will publish it to crates.io some day when we feel we can adhere to SemVer.)
We just can't make any guarantees around the stability of the API. We generally develop those internal libraries with ourselves as the sole consumer in mind, and so you likely will experience breaking changes when you upgrade. Honestly, I wouldn't expect it to be that bad in practice, especially since you need such a narrow subset of the AST anyway, but I need to reserve the right for it to be fairly annoying, just in case... (Relatedly, we're in the process of rewriting the parser entirely. The API and AST will be similar, but the internals will be completely rewritten. So that may affect you in some way whenever you choose to bump your version.)

In short, I would feel okay with it (and, in fact, glad that we could help out the project), just don't hate me when we ship breaking changes.

Thank you for the details, we acknowledge that there could be breaking changes, and fully understand why, so we obviously won't hate you when that happens, especially since we will depend on the parser for free. Thanks for your hard work maintaining the parser 🙂


Not able to access National Structure Inventory Dataset

Clicking on the NSI tool does not open the download tool. It gives an error message saying server cannot be reached. Is there any way around to download the data?

Not urgent. I will check back next week if I can access it. Currently Im getting the following error while accessing the data.

what link are you using? where did you find the link?

It is the hyperlink "NIS download tool" in this page: https://www.hec.usace.army.mil/confluence/nsi/userguides/download-tool

Thanks. I can access it now.

service has been restored with links to download data now working.


Changes to handle drop case iac column

Motivation and Context
to support changes for generating a new access (IAC) code
What has changed
iac column has been dropped from case table and only caseiacaudit iac column should be used
How to test?
Test in conjunction with rm-case-service PR
Links

 SUS004: Generate a new access code (IAC) for an LMS case


The sign in button is visible

Fixes #241
Describe the changes you have made in this PR -
In the main.stylesheet.css
From class user-field
Removed the overflow:hidden
Screenshots of the changes (If any) -

Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

already fixed by #212


If you have https you have https 👍🏻

I suppose this could also just be [npms.io](https://npms.io)
Thanks for the awesome site!

Ahaha ty.


Alternative squid plots

Downweighted age comps from fishery or survey
Squid plots for models with downweighted fishery or survey ages were discussed in issue #410 as a way to explore the influence of each data set on the estimation of deviations. These were not included in the 2018 assessment but they might be worth considering for future documents. Even without the squid plots, the models with one or the other data set downweighted could be considered as additional sensitivities.
Squid plot based on historical assessments
Separately, at the 2018 JMC meeting, Paul Ryall asked if it would be possible to make a squid plot showing the retrospective estimates over the true history of assessments applied in each year, rather than the current assessment with data peeled back one year at a time. This required an edit to the SSsummarize function in r4ss (commit cbced3b6f0acf461db52f15893e48fa9f75555cb) but is now possible using commands below, which produced the figure pasted below. Over the period 2011 to 2018, things have been pretty stable, although the low survey biomass estimated in 2011 first included in the 2012 assessment cause a drop for the in between the first 2 points for the '05, '06, and '08 cohorts.
I'm not convinced that this plot is that useful, but perhaps a side-by-side comparison with the base model squid plot would be informative.
# read base model MLE assessments from each year starting in 2011
# (model files are archived on NWFSC network but available upon request to anyone)
h2011 <- SS_output('PWhiting2011/SS_2011_base_case_model_files', covar=FALSE, forecast=FALSE)
h2012 <- SS_output('PWhiting2012/2012 MLE model files (not base model)')
h2013 <- SS_output('PWhiting2013/2013hake_mle_notBase')
h2014 <- SS_output('PWhiting2014/2014hake_21_TVselex1991start_MLE')
h2015 <- SS_output('PWhiting2015/base_model_MLE')
h2016 <- SS_output('PWhiting2016/base_model_MLE', forecast=FALSE)
h2017 <- SS_output('PWhiting2017/MLE model files', covar=FALSE, forecast=FALSE)
h2018 <- base.model

# summarize output across assessments
h.sum <- SSsummarize(list(h2011, h2012, h2013, h2014, h2015, h2016, h2017, h2018))
# make squid plot
SSplotRetroRecruits(h.sum, endyrvec=2011:2018, cohorts=1999:2016)

You're still working on hake! ;)
Yes, not sure how useful that new plot is - impressed you got it working though. Bit of a dismembered squid though....

Just trying to write down anything lingering in my mind before it completely gets taken over by other stuff.
It was good to realize that the SSsummarize step wasn't working right for comparing models from different years because the parameter labeled "Main_RecrDev_2016" in the 2018 base model was labeled "Late_RecrDev_2016" or "ForeRecr_2016" in earlier models with different ending year and different range of "main" recdevs. I don't think that issue impacted anything we've done in the past, but is good to have fixed in general (they now show up in the same row of the $recdev table output from SSsummarize, rather than different rows).


can't install macrogauracore to /usr/bin

https://imgur.com/C3zruqG
Hi, I can't install macrogauracore into /usr/bin on Catalina 10.15.7, disabled SIP and gatekeeper, but it won't help.

In recent versions of macOS, it's supposed to be installed at /usr/local/bin

Cool, I've just copied/installed as you guided me at /usr/local/bin , everything seems okay, it works now, thanks, nice day! ^^

Fixed at 116eef972a38285732a90fc77c3e61cfe18a7ef8 ✅


Add ability to have more than 1 meeting of the same type per day

This work will help with:

Have multiple slots of meetings for one type of meeting (useful for Informational and API Review)
Reschedule meetings for the same day but different time

Planning epic: https://github.com/Azure/azure-sdk-pr/issues/1256

Figma design: https://www.figma.com/file/OdYeiVYd0PYK8qC5FnsNMU/Multiple-meetings-per-day-in-Scheduling-Tool?type=whiteboard&node-id=0-1&t=i6G7tY9hRu16j7Z3-0

The first iteration of this calendar has been deployed to PROD


Low power mode on iOS

E.g., Something like this if done outside of direct support in TSDK

on phone sleep, disconnect Ziti (disabling identities should be sufficient, assuming disabling attempts to access the controller and ERs causes the majority of battery usage)
on wake, reconnect
Button on UI to enable/disable this mode (presuming since some apps will need connectivity while phone is sleeping

Alt: consider supporting this mode in TSDK (e.g., connect to ERs only on Dial attempt - perceived performance would be impacted, and doesn't address hosting services...)

Also - make sure that "low power mode" requires interceptDnsByMatchingDomains==true to avoid DNS traffic routing through the appex...

some notes from The Eskimo: https://developer.apple.com/forums/thread/95988

Disabling identities on sleep and re-enabling on wake so fair if a big failure.  When not in Do-no-disturb, phone sleeps and wakes up very vert frequently, having the opposite of intended effect on the battery.
Need a new strategy:
a) only disable if been asleep for some time period (e.g., a couple of mins)?
b) only disable if also in Do-not-disturb mode?
c) add a setting in TSDK or CSDK that allows a quick "tune down" (dramatically slow down things like service requests and posture checks, anything else running on a timer...)?
d) Just setting tunnel networking to nil so no apps using the tunnel can cause traffic?  prob not enough.  maybe combine with c)?

I was wondering if this can be prioritized again? As of right now the mobile client massively drains the battery, making it impractical to leave it enabled all the time. It would be great if it could get to the level of the WireGuard iOS client, which consumes very little power.

Yes. We have heard from a handful of users that they are having this issue and are discussing potential approaches to address it.  When we have something, I'll post it in Discourse and on this issue and solicit users to join a TestFlight.


fix release workflow

Renames the binary from rlwy to railway

Also fixes the install script (points at the main repo)


PackageSources: do not print feed password to output #1224

In NuGetV2.GetVersions use the same approach as in GetPackageDetails to just print the feed url instead of the full record including the password, to avoid leaking the password unnecessarily to the console output.
It is correct that the password is lying around (at least encrypted) in paket.config, but it's still awkward seeing your personal password floating by on the console when pair-programming ;)
See also #1224

thx


Add potato peel to continuum imaging

Add in the initial infrastructure to support peeling reference sources via potato peel.

Addresses #64


Adding time extensions

Hello!
I got the code produced by jogboms on https://github.com/jogboms/time.dart and merged his great libraries into dartx.
This commit introduces all the jogbom's extensions to time types, like producing durations through integers and some other utility methods.

Thanks for your contribution!
The .seconds, .milliseconds, etc. getters are already defined on num so they will work on int and double (Source).
The extensions on Date and Duration are new and I will merge them if you remove the int extensions.

Just removed the duplicated int extensions!

I have a slight tingle in my stomach that copying source code and tests may not be an elegant solution.

I agree. I would never copy your without asking. I actually took this functionality from Kotlin before your package was released.

with your permission, the improvements on Time.dart to support both variants of num would indeed be a good idea and both libraries could exists as different entities. What do you think?

Yeah sure, no problem. Do you think I should remove all time related getters? My vision with dartx was to create a single library which contains every extension you could dream of because with Kotlin I always had to use multiple libraries with overlapping functionality and that was annoying and created name conflicts.

My objective of doing the merge was to make dartx the only library needed for all this small extensions that we use all the time on our work days.
In my opinion, one library with all extensions is much better than multiple multiple libraries.
Imagine if you want to use timer extensions, you will have to import it manually.
Than, if you want to use another extensions library, you will also have to import it manually.
See the problem? Dartx fix it by doing just one import line.

I agree. I would never copy your without asking. I actually took this functionality from Kotlin before your package was released.

No issues really, I was just more worried on how to proceed when things start to diverge.

Do you think I should remove all time related getters?

If you wouldn't mind, I could make Time.dart more robust with those inclusions.

Kotlin I always had to use multiple libraries with overlapping functionality and that was annoying and created name conflicts.

At least with the current implementation of extensions for dart we shouldn't be worried about this, There is an open discussion about global scoping (even though I wouldn't want that to be honest) and that could break projects down the road for every one.

+1 to @jogboms
A more elegant solution is to have dartx depend on @jogboms's solution. Then use the export directive to expose them.

Shit sorry I edited you comment...

A more elegant solution is to have dartx depend on @jogboms's solution. Then use the export directive to expose them.

I didn't even think of that. Great idea. I'll do that if @jogboms agrees 👍

@rrousselGit good of you to join in :)

In my opinion, one library with all extensions is much better than multiple multiple libraries.

@shinayser, considering the fact that extensions are scoped to their imports, I would not think this is the way to go.

@leisim I was already edging towards that idea in my mind. Good to know we are all in sync 💙 👍

Awesome. So, making dartx depend on dart will be the best sollution.
Will you do this @leisim, or you want me to push that change?

@leisim I was already edging towards that idea in my mind. Good to know we are all in sync 💙 👍

Perfect, let's do that. You create extensions for num, right?

Awesome. So, making dartx depend on dart will be the best sollution.

This is also a future proof solution to solve these kinds of conflict.

Yes @leisim will do that and add more tests.

Great then. So, this issue is closed. Thanks @leisim and @jogboms.
Let's keep dart rocking :)

That was a nice smooth discussion! Epic ❤

@jogboms @rrousselGit @shinayser
I made the changes and added a small example to the readme. A new version will be published once time.dart supports num.

I made the changes and added a small example to the readme. A new version will be published once time.dart supports num.

Amazing! Can't wait to use it with Flutter! Anyone got any idea when we getting dart 2.6 on it?

@shinayser not so sure on the timeline.
@leisim published v1.1.0 of Time.dart


Improve docker image versioning.

Describe the enhancement you'd like
For example instead tagging images only as "latest" and "dev", doing v1, v1.1, v1.2 builds.
Describe why this will benefit the LibrePhotos
Would be useful also to prevent regresions on latest/dev tag.
Additional context
Would be nice for people (like me) who wants to control versioning and jump between versions instead always pulling latest on production environments and dev on testing ones.

To my knowledge you have versioning for containers, although they do not come with a vMajor.Minor.Build numbering, but with a ${year}w${week} numbering,
Please have a look at the DockerHub https://hub.docker.com/r/reallibrephotos/librephotos/tags and you will understand what I mean.

Yes, understood. But they seem not up to date with "latest" images:

Those are supposed to be "weekly builds" but are updated once per month. Would be nice to have an update per week like latest image.

I am not sure where you got that these are weekly builds, sure the version ing suggests it, but as you can see that is clearly not the case.
Also remarkable that you seem to ignore the fact that latest and 2023w26.1 have the same digest signature.
There are no newer containers at this moment  latest is 223w26.1, only dev is newer.

I am not sure where you got that these are weekly builds, sure the version ing suggests it, but as you can see that is clearly not the case.
Also remarkable that you seem to ignore the fact that latest and 2023w26.1 have the same digest signature.
There are no newer containers at this moment latest is 223w26.1, only dev is newer.

Well i assume that this w on "2023w26" references the "week". And what i say is that would be nice to have weekly builds, as dev updates every week would be nice to follow the same procedure on "latest tagged images", but i understand that this is up to the developers.
And yes. Didn't see the digests.

And what i say is that would be nice to have weekly builds, as dev updates every week would be nice to follow the same procedure on "latest tagged images", but i understand that this is up to the developers.
And yes. Didn't see the digests.

It would be nice to do nightly builds based of the dev branch for those who want to check out the latest changes.
But given the current development cycle I do not know whether this is really useful. Functions might be more broken than in the more stable periodic release.
As there aren't that many developers a more streamlined release cycle with QA/pre release doesn't make sense to me.


uploaded images are not updated in real time

Gitea version (or commit ref): 1.4.2
Git version: 2.7.4
Operating system: ubuntu 16.04 64bit
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[X ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ X] Yes (provide example URL)
[ ] No
[ ] Not relevant

Log gist:

Description
Upload images to a directory via web UI(or command line git-push), refer it in a markdown file in the same directory, first displayed fine, then replace it with a different image, or same image with different name, the markdown will display the old images, i.e. the markdark inside gitea web interface is not syncing up with the real image files in git repositories.

Could you provide a URL on https://try.gitea.io


[Bug] 'go get' in no longer supported outside a module error

Which version of MSAL Go are you using?
latest.
Where is the issue?
I am relatively new to Go language environment and try to follow this README steps. This is a part of my new project in Go.
I am getting below error with 'go get' command. Google search did not show any helpful contents.
The file 'go.mod' exists in the path. Where does this error come from?
The 'go install' also failed with another error. I'd like to understand this error meaning.
ju-hyounglee@Ju-Hyoungs-MacBook-Air Documents % go get -u github.com/AzureAD/microsoft-authentication-library-for-go/
go: go.mod file not found in current directory or any parent directory.
'go get' is no longer supported outside a module.
To build and install a command, use 'go install' with a version,
like 'go install example.com/cmd@latest'
For more information, see https://golang.org/doc/go-get-install-deprecation
or run 'go help get' or 'go help install'.
ju-hyounglee@Ju-Hyoungs-MacBook-Air Documents %
Is this a new or an existing app?
N/A
What version of Go are you using (go version)?
go version go1.21.6 darwin/arm64
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
ju-hyounglee@Ju-Hyoungs-MacBook-Air Documents % go env
GO111MODULE=''
GOARCH='arm64'
GOBIN=''
GOCACHE='/Users/ju-hyounglee/Library/Caches/go-build'
GOENV='/Users/ju-hyounglee/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='arm64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/ju-hyounglee/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='darwin'
GOPATH='/Users/ju-hyounglee/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/local/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/usr/local/go/pkg/tool/darwin_arm64'
GOVCS=''
GOVERSION='go1.21.6'
GCCGO='gccgo'
AR='ar'
CC='clang'
CXX='clang++'
CGO_ENABLED='1'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/pd/dfs8k70d5gzdcpjx95wnghy00000gn/T/go-build2391299166=/tmp/go-build -gno-record-gcc-switches -fno-common'
ju-hyounglee@Ju-Hyoungs-MacBook-Air Documents %
Repro
Expected behavior
getting microsoft-authentication-library-for-go repo
Actual behavior
go: go.mod file not found in current directory or any parent directory.
'go get' is no longer supported outside a module.
To build and install a command, use 'go install' with a version,
like 'go install example.com/cmd@latest'
For more information, see https://golang.org/doc/go-get-install-deprecation
or run 'go help get' or 'go help install'.
Possible solution
Additional context / logs / screenshots
Add any other context about the problem here, such as logs and screenshots.

Out of curisoity have you created a go module via go mod init command and ran the go get command while in that directory?
From your go env output I see that you're in the Documents directory, which makes me think that you might not be in the correct directory.
As for the go install command, it is for go module repository that can be compiled to an executable binary which doesn't apply to this repository.

Does not seem like an issue.


[24.04] Reset Power-Off Doesn't Trigger As Expected

BlueRetro firmware version
24.04
BlueRetro firmware specification
HW2
BlueRetro firmware variant
System specific
BlueRetro hardware type
Internal install modkit
Manufacturer
LaserBear
System used
Nintendo GameCube
Bluetooth controller brand & name
8bitdo Ultimate BT
What is problem? (only list ONE problem per report)
The "double-tap reset to turn off the system" functionality is more miss than hit. If anything, when it does work, I notice that when I start to double-press reset a second time, it will turn off more often if tapped the right timing.
What did you expect to happen?
Expected the system to turn off via relay after the double-tap every time, without having the console reset when the command is done proper.
Attach files like logs or Bluetooth traces here
No response

It work this way, you just need to get use to it.
I not ideal but I the best it can be.


Add a test for the select/deselect all functionality

This adds test for the fix in #138.
To prove that these tests actually test against the problem fixed by #138, look at the test run here against master which doesn't have the fix from #138.

To be clear - this PR was closed automatically

To be clear - this PR was closed automatically

Also, I cannot reopen it

Also, I cannot reopen it

I can't reopen it either, I'll open a new one with your feedback incorporated.


Editor Playground, Release Notes don't respect underline setting

Testing #217636
Expect links in Editor Playground (Help > Editor Playground) to support underline setting:

Same issues in Help > Release Notes.
May be same as #217810

Another instance that was fixed by https://github.com/microsoft/vscode/pull/216859 but wasn't caught in time


Sorting at a price in different ranges doesn't work properly

Relates to:
#2890
Current behavior
Sorting at a price in different ranges doesn't work properly - only the last selected price range is taken into account.

Expected behavior
Available products should be displayed according to the selected price ranges.
Steps to reproduce the issue

Go to any category page, e.g. Men
Select Price > $ 50
Select also $100-150 and see results

Repository

Can you handle fixing this bug by yourself?

[ ] YES
[ ] NO

Which Release Cycle state this refers to? Info for developer.
Pick one option.

[ ] This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
[ ] This is a bug report for current Release Candidate version on https://next.storefrontcloud.io - In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
[ ] This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.

Environment details

Browser:
OS:
Node:
Code Version:

Additional information

fixed ! @patzick could you  do the same solution for Erin recommendations?

this goes to #2322


HTML reporter unusable when hosted with relative pathnames

Describe the bug
We are deploying all our test reports to github pages in different directories.
/report-integration - shows vitest
/report-e2e - shows playwright html report
The issue we are facing is that Vitest HTML report requires pathname to empty. Eg sannajammeh.github.io/. So when deployed to sannajammeh.github.io/report-integration, the UI is a complete black screen.
I tested this during development as well. Using npx vite preview --outDir ./reports serves without a pathname successfully and the tests show. When opening an HTML server using Live Server in vscode from the testing directory, the pathname is set at <live server host>/reports. Vitest loads all JS files successfully, even the gzipped test data, yet shows a black screen with no tests.
Reproduction
I think the description suffices. There is no way to reproduce with an example without hosting to a specific pathname.
System Info
System:
    OS: macOS 13.2
    CPU: (8) x64 Apple M1
    Memory: 19.38 MB / 8.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 19.9.0 - ~/Library/pnpm/node
    Yarn: 1.22.11 - /usr/local/bin/yarn
    npm: 9.6.3 - ~/Library/pnpm/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Browsers:
    Chrome: 112.0.5615.121
    Firefox Developer Edition: 108.0
    Safari: 16.3
  npmPackages:
    @vitest/ui: ^0.30.1 => 0.30.1
    vite: ^4.3.0 => 4.3.0
    vitest: ^0.30.1 => 0.30.1

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Is there anything missing for some feedback on this one?