property 'keyvault_' doesn't exist

Encountered the following runtime error in the logic flow Get Client Secret step.

InvalidTemplate. Unable to process template language expressions in action 'Get_Client_Secret' inputs at line '1' and column '4084': 'The template language expression 'parameters('$connections')['keyvault_']['connectionId']' cannot be evaluated because property 'keyvault_' doesn't exist, available properties are 'azureautomation, keyvault, office365, office365users, sharepointonline, teams'. Please see https://aka.ms/logicexpressions for usage details.'. >>

In processteamrequestbeta.json line 1585, the "keyvault_" should be without the underscore at the end.
                        "type": "ApiConnection",
                        "inputs": {
                            "host": {
                                "connection": {
                                    "name": "@parameters('$connections')['keyvault_']['connectionId']"
                                }
                            },
                            "method": "get",
                            "path": "/secrets/@{encodeURIComponent('appsecret')}/value"
                        },

@shuenSL good spot, I've created a PR to fix this.


Xnero: Watch maxicus.com

Xnero requests the watch of the watch_keyword maxicus\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

maxicus\.com has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by Ryan M in Charcoal HQ


Port Flows primitives to Java

See https://github.com/CategoricalData/hydra/blob/main/hydra-haskell/src/main/haskell/Hydra/Dsl/Lib/Flows.hs

This is done. I consider the expansion of the language-agnostic test suite to be a separate task.


adding gridscale driver to libcloud

adding gridscale driver to libcloud
Description
This change brings in the driver for the cloud provider gridscale.
This pull request will contribute the necessary changes in libcloud, for gridscale to support a libcloud implementation.
Status

done, ready for review

Checklist

[x] Code linting (required, can be done after the PR checks)
[x] Documentation
[x] Tests
[x] ICLA (required for bigger changes)

Thank you for your contribution.
We will review it when we get a chance.

@PrinceSydney Thanks again for the contribution. I finally had a chance to review it today.
Overall, the PR looks like a great start, but there are some small things which need to be improved or fixed.

I've made some fixes and changes and merged PR into master (please see a list of changes I made here - https://github.com/apache/libcloud/commits/trunk).
In theory deploy_node should also work now, but I didn't test it. Something along those lines:
ssh_key = driver.list_key_pairs()[0]
ssh_key_uuid = ssh_key.fingerprint

auth = NodeAuthSSHKey(ssh_key.pubkey)

node = conn.deploy_node(name='test', image=image], size=size, auth=auth,
                        deploy=..., ex_ssh_key_ids=[ssh_key_uuid])

Thanks again for the contribution.


No devices found with name or id matching. Apple M1 Mac and real device. Happens frequently

Steps to Reproduce

Connect iPhone device to Macbook M1 laptop.
It will show up on the device list but when installing, we get an error.

Expected results:
Able to install on the real device on Apple M1 Mac and using latest Android Studio.
It works sometimes but doesn't work a lot of time.
Actual results:

Searched internet and past suggestions but nothing helped so far.
When I reboot laptop, then it works for a little while but starts to happen again.

Logs
[✓] Flutter (Channel stable, 1.22.5, on macOS 11.1 20C69 darwin-arm, locale en-US)
    • Flutter version 1.22.5 at /Users/vmacair/development/flutter
    • Framework revision<PHONE_NUMBER> (6 weeks ago), 2020-12-10 11:54:40 -0800
    • Engine revision ae90085a84
    • Dart version 2.10.4

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

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

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin installed
    • Dart plugin version 201.9317
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[!] Connected device
    ! Error: Errors were encountered while preparing your device for development. Please check the Devices and Simulators Window.  (code -1)

! Doctor found issues in 1 category.

Hi @dgurudot
Is there anything relevant logged to flutter run -v or the device console?
Is there anything useful in Devices and Simulators?
I'm not seeing this with our M1.
Thank you

Hi @dgurudot
Is there anything relevant logged to flutter run -v or the device console?
Is there anything useful in Devices and Simulators?
I'm not seeing this with our M1.
Thank you

I am finding the following error while running "flutter run -v". I checked
that my device is using latest iOS 14.3 and Xcode is latest version 12.3
============================================================================================================================
                2021-01-22 08:19:25.707 xcdevice[51186:6970077]

DTDeviceKit: Failed to mount DDI from
'<DVTFilePath:0x11170d210:'/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport/14.3/Develop
erDiskImage.dmg'>', error=-402653066: Error
Domain=com.apple.dtdevicekit Code=806 "Failed to prepare device for
development."
UserInfo={AssociatedMobileDeviceFunction=AMDeviceMountImage,
NSUnderlyingError=0x12a894d90 {Error
Domain=com.apple.dt.MobileDeviceErrorDomain
Code=-402653066 "Could not support development."
UserInfo={MobileDeviceErrorCode=(0xE8000076),
com.apple.dtdevicekit.stacktrace=(
0   DTDeviceKitBase
0x00000001044612f8 DTDKCreateNSErrorFromAMDErrorCode + 272
1   DTDeviceKitBase
0x000000010449ad84 -[DTDKMobileDeviceToken
_mountDeveloperDiskImage:withError:] +
916
2   DTDeviceKitBase
0x000000010449b76c __58-[DTDKMobileDeviceToken
mountDeveloperDiskImageWithError:]_block_invoke +
556
3   libdispatch.dylib
0x000000018b298420 _dispatch_client_callout + 20
4   libdispatch.dylib
0x000000018b2a6a98 _dispatch_lane_barrier_sync_invoke_and_complete + 60
5   DTDeviceKitBase
0x000000010449b4d8 -[DTDKMobileDeviceToken
mountDeveloperDiskImageWithError:] + 168
6   IDEiOSSupportCore
0x00000001186d7dc8 __37-[DVTiOSDevice(Connect) hasConnected]_block_invoke_2

272
7   DVTFoundation
0x0000000105976730 DVT_CALLING_CLIENT_BLOCK + 16
8   DVTFoundation
0x000000010597b3a4 __DVTDispatchGroupAsync_block_invoke + 680
9   libdispatch.dylib
0x000000018b2968bc _dispatch_call_block_and_release + 32
10  libdispatch.dylib
0x000000018b298420 _dispatch_client_callout + 20
11  libdispatch.dylib
0x000000018b29b82c _dispatch_continuation_pop + 560
12  libdispatch.dylib
0x000000018b29aec4 _dispatch_async_redirect_invoke + 592
13  libdispatch.dylib
0x000000018b2a8fac _dispatch_root_queue_drain + 356
14  libdispatch.dylib
0x000000018b2a97a4 _dispatch_worker_thread2 + 116
15  libsystem_pthread.dylib
0x000000018b441024 _pthread_wqthread + 216
16  libsystem_pthread.dylib
0x000000018b43fd94 start_wqthread + 8
), DVTRadarComponentKey=261622,
NSLocalizedDescription=Could not support development.}},
NSLocalizedRecoverySuggestion=If
you are certain that Xcode supports development on this
device, try disconnecting and reconnecting the device.,
NSLocalizedFailure=This operation can fail if the
version of the OS on the device is newer than the version of Xcode that is
running., DVTRadarComponentKey=487927,
NSLocalizedDescription=Failed to prepare device for development.}
2021-01-22 08:19:25.707 xcdevice[51186:6970077]
iPhoneConnect: 📱<DVTiOSDevice (0x119686660), VIPhone, iPhone, 14.3
(18C66), 71abd87bd654537024591e3131cb4fd1ade326c6>
unable to mount developer disk image, (Error Domain=com.apple.dtdevicekit
Code=806 "Failed to prepare device for development."
UserInfo={AssociatedMobileDeviceFunction=AMDeviceMountImage,
NSUnderlyingError=0x12a894d90 {Error
Domain=com.apple.dt.MobileDeviceErrorDomain Code=-402653066 "Could not
support
development."
UserInfo={MobileDeviceErrorCode=(0xE8000076),
com.apple.dtdevicekit.stacktrace=(
0   DTDeviceKitBase
0x00000001044612f8 DTDKCreateNSErrorFromAMDErrorCode + 272
1   DTDeviceKitBase
0x000000010449ad84 -[DTDKMobileDeviceToken
_mountDeveloperDiskImage:withError:] +
916
2   DTDeviceKitBase
0x000000010449b76c __58-[DTDKMobileDeviceToken
mountDeveloperDiskImageWithError:]_block_invoke +
556
3   libdispatch.dylib
0x000000018b298420 _dispatch_client_callout + 20
4   libdispatch.dylib
0x000000018b2a6a98 _dispatch_lane_barrier_sync_invoke_and_complete + 60
5   DTDeviceKitBase
0x000000010449b4d8 -[DTDKMobileDeviceToken
mountDeveloperDiskImageWithError:] + 168
6   IDEiOSSupportCore
0x00000001186d7dc8 __37-[DVTiOSDevice(Connect) hasConnected]_block_invoke_2
272
7   DVTFoundation
0x0000000105976730 DVT_CALLING_CLIENT_BLOCK + 16
8   DVTFoundation
0x000000010597b3a4 __DVTDispatchGroupAsync_block_invoke + 680
9   libdispatch.dylib
0x000000018b2968bc _dispatch_call_block_and_release + 32
10  libdispatch.dylib
0x000000018b298420 _dispatch_client_callout + 20
11  libdispatch.dylib
0x000000018b29b82c _dispatch_continuation_pop + 560
12  libdispatch.dylib
0x000000018b29aec4 _dispatch_async_redirect_invoke + 592
13  libdispatch.dylib
0x000000018b2a8fac _dispatch_root_queue_drain + 356
14  libdispatch.dylib
0x000000018b2a97a4 _dispatch_worker_thread2 + 116
15  libsystem_pthread.dylib
0x000000018b441024 _pthread_wqthread + 216
16  libsystem_pthread.dylib
0x000000018b43fd94 start_wqthread + 8
), DVTRadarComponentKey=261622,
NSLocalizedDescription=Could not support development.}},
NSLocalizedRecoverySuggestion=If
you are certain that Xcode supports development on this
device, try disconnecting and reconnecting the device.,
NSLocalizedFailure=This operation can fail if the
version of the OS on the device is newer than the version of Xcode that is
running., DVTRadarComponentKey=487927,
NSLocalizedDescription=Failed to prepare device for development.}) {
AssociatedMobileDeviceFunction = AMDeviceMountImage;
DVTRadarComponentKey = 487927;
NSLocalizedDescription = "Failed to prepare device
for development.";
NSLocalizedFailure = "This operation can fail if
the version of the OS on the device is newer than the version of Xcode
that is running.";
NSLocalizedRecoverySuggestion = "If you are certain
that Xcode supports development on this device, try disconnecting
and reconnecting the device.";
NSUnderlyingError = "Error
Domain=com.apple.dt.MobileDeviceErrorDomain Code=-402653066 "Could not
support
development."
UserInfo={MobileDeviceErrorCode=(0xE8000076),
com.apple.dtdevicekit.stacktrace=(\n\t0   DTDeviceKitBase
0x00000001044612f8
DTDKCreateNSErrorFromAMDErrorCode + 272\n\t1   DTDeviceKitBase
0x000000010449ad84
-[DTDKMobileDeviceToken
_mountDeveloperDiskImage:withError:] + 916\n\t2   DTDeviceKitBase
0x000000010449b76c __58-[DTDKMobileDeviceToken
mountDeveloperDiskImageWithError:]_block_invoke + 556\n\t3
libdispatch.dylib
0x000000018b298420 _dispatch_client_callout + 20\n\t4   libdispatch.dylib
0x000000018b2a6a98
_dispatch_lane_barrier_sync_invoke_and_complete + 60\n\t5   DTDeviceKitBase
0x000000010449b4d8 -[DTDKMobileDeviceToken
mountDeveloperDiskImageWithError:] + 168\n\t6   IDEiOSSupportCore
0x00000001186d7dc8 __37-[DVTiOSDevice(Connect)
hasConnected]_block_invoke_2 + 272\n\t7   DVTFoundation
0x0000000105976730 DVT_CALLING_CLIENT_BLOCK +
16\n\t8   DVTFoundation                       0x000000010597b3a4
__DVTDispatchGroupAsync_block_invoke + 680\n\t9
libdispatch.dylib                   0x000000018b2968bc
_dispatch_call_block_and_release + 32\n\t10
libdispatch.dylib                   0x000000018b298420
_dispatch_client_callout + 20\n\t11
libdispatch.dylib                   0x000000018b29b82c
_dispatch_continuation_pop +
560\n\t12  libdispatch.dylib
0x000000018b29aec4 _dispatch_async_redirect_invoke + 592\n\t13
libdispatch.dylib
0x000000018b2a8fac _dispatch_root_queue_drain + 356\n\t14  libdispatch.dylib
0x000000018b2a97a4 _dispatch_worker_thread2 +
116\n\t15  libsystem_pthread.dylib             0x000000018b441024
_pthread_wqthread + 216\n\t16
libsystem_pthread.dylib             0x000000018b43fd94 start_wqthread +
8\n),
DVTRadarComponentKey=261622,
NSLocalizedDescription=Could not support development.}";
}
2021-01-22 08:19:25.708 xcdevice[51186:6969905] [MT]
iPhoneConnect: 📱<DVTiOSDevice (0x119686660), VIPhone, iPhone, 14.3
(18C66), 71abd87bd654537024591e3131cb4fd1ade326c6> --
An error occurred whilst preparing device for development -- Failed to
prepare device for development.
Domain: com.apple.dtdevicekit
Code: 806
Recovery Suggestion: If you are certain that Xcode
supports development on this device, try disconnecting and reconnecting
the device.
User Info: {
AssociatedMobileDeviceFunction = AMDeviceMountImage;
DVTRadarComponentKey = 487927;
NSLocalizedFailure = "This operation can fail if
the version of the OS on the device is newer than the version of Xcode
that is running.";
}

On Wed, Jan 20, 2021 at 2:57 AM Markus Aksli<EMAIL_ADDRESS>wrote:

Hi @dgurudot https://github.com/dgurudot
Is there anything relevant logged to flutter run -v or the device console?
Is there anything useful in Devices and Simulators?
I'm not seeing this with our M1.
Thank you
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/74244#issuecomment-763411791,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOASKKX5DJ2MVZ5X3E2OCDTS22EGZANCNFSM4WJEJLRQ
.

I am finding the following error while running "flutter run -v". I checked
that my device is using latest iOS 14.3 and Xcode is latest version 12.3
============================================================================================================================
                2021-01-22 08:19:25.707 xcdevice[51186:6970077]

DTDeviceKit: Failed to mount DDI from
'<DVTFilePath:0x11170d210:'/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport/14.3/Develop
erDiskImage.dmg'>', error=-402653066: Error
Domain=com.apple.dtdevicekit Code=806 "Failed to prepare device for
development."
UserInfo={AssociatedMobileDeviceFunction=AMDeviceMountImage,
NSUnderlyingError=0x12a894d90 {Error
Domain=com.apple.dt.MobileDeviceErrorDomain
Code=-402653066 "Could not support development."
UserInfo={MobileDeviceErrorCode=(0xE8000076),
com.apple.dtdevicekit.stacktrace=(
0   DTDeviceKitBase
0x00000001044612f8 DTDKCreateNSErrorFromAMDErrorCode + 272
1   DTDeviceKitBase
0x000000010449ad84 -[DTDKMobileDeviceToken
_mountDeveloperDiskImage:withError:] +
916
2   DTDeviceKitBase
0x000000010449b76c __58-[DTDKMobileDeviceToken
mountDeveloperDiskImageWithError:]_block_invoke +
556
3   libdispatch.dylib
0x000000018b298420 _dispatch_client_callout + 20
4   libdispatch.dylib
0x000000018b2a6a98 _dispatch_lane_barrier_sync_invoke_and_complete + 60
5   DTDeviceKitBase
0x000000010449b4d8 -[DTDKMobileDeviceToken
mountDeveloperDiskImageWithError:] + 168
6   IDEiOSSupportCore
0x00000001186d7dc8 __37-[DVTiOSDevice(Connect) hasConnected]_block_invoke_2

272
7   DVTFoundation
0x0000000105976730 DVT_CALLING_CLIENT_BLOCK + 16
8   DVTFoundation
0x000000010597b3a4 __DVTDispatchGroupAsync_block_invoke + 680
9   libdispatch.dylib
0x000000018b2968bc _dispatch_call_block_and_release + 32
10  libdispatch.dylib
0x000000018b298420 _dispatch_client_callout + 20
11  libdispatch.dylib
0x000000018b29b82c _dispatch_continuation_pop + 560
12  libdispatch.dylib
0x000000018b29aec4 _dispatch_async_redirect_invoke + 592
13  libdispatch.dylib
0x000000018b2a8fac _dispatch_root_queue_drain + 356
14  libdispatch.dylib
0x000000018b2a97a4 _dispatch_worker_thread2 + 116
15  libsystem_pthread.dylib
0x000000018b441024 _pthread_wqthread + 216
16  libsystem_pthread.dylib
0x000000018b43fd94 start_wqthread + 8
), DVTRadarComponentKey=261622,
NSLocalizedDescription=Could not support development.}},
NSLocalizedRecoverySuggestion=If
you are certain that Xcode supports development on this
device, try disconnecting and reconnecting the device.,
NSLocalizedFailure=This operation can fail if the
version of the OS on the device is newer than the version of Xcode that is
running., DVTRadarComponentKey=487927,
NSLocalizedDescription=Failed to prepare device for development.}
2021-01-22 08:19:25.707 xcdevice[51186:6970077]
iPhoneConnect: 📱<DVTiOSDevice (0x119686660), VIPhone, iPhone, 14.3
(18C66), 71abd87bd654537024591e3131cb4fd1ade326c6>
unable to mount developer disk image, (Error Domain=com.apple.dtdevicekit
Code=806 "Failed to prepare device for development."
UserInfo={AssociatedMobileDeviceFunction=AMDeviceMountImage,
NSUnderlyingError=0x12a894d90 {Error
Domain=com.apple.dt.MobileDeviceErrorDomain Code=-402653066 "Could not
support
development."
UserInfo={MobileDeviceErrorCode=(0xE8000076),
com.apple.dtdevicekit.stacktrace=(
0   DTDeviceKitBase
0x00000001044612f8 DTDKCreateNSErrorFromAMDErrorCode + 272
1   DTDeviceKitBase
0x000000010449ad84 -[DTDKMobileDeviceToken
_mountDeveloperDiskImage:withError:] +
916
2   DTDeviceKitBase
0x000000010449b76c __58-[DTDKMobileDeviceToken
mountDeveloperDiskImageWithError:]_block_invoke +
556
3   libdispatch.dylib
0x000000018b298420 _dispatch_client_callout + 20
4   libdispatch.dylib
0x000000018b2a6a98 _dispatch_lane_barrier_sync_invoke_and_complete + 60
5   DTDeviceKitBase
0x000000010449b4d8 -[DTDKMobileDeviceToken
mountDeveloperDiskImageWithError:] + 168
6   IDEiOSSupportCore
0x00000001186d7dc8 __37-[DVTiOSDevice(Connect) hasConnected]_block_invoke_2
272
7   DVTFoundation
0x0000000105976730 DVT_CALLING_CLIENT_BLOCK + 16
8   DVTFoundation
0x000000010597b3a4 __DVTDispatchGroupAsync_block_invoke + 680
9   libdispatch.dylib
0x000000018b2968bc _dispatch_call_block_and_release + 32
10  libdispatch.dylib
0x000000018b298420 _dispatch_client_callout + 20
11  libdispatch.dylib
0x000000018b29b82c _dispatch_continuation_pop + 560
12  libdispatch.dylib
0x000000018b29aec4 _dispatch_async_redirect_invoke + 592
13  libdispatch.dylib
0x000000018b2a8fac _dispatch_root_queue_drain + 356
14  libdispatch.dylib
0x000000018b2a97a4 _dispatch_worker_thread2 + 116
15  libsystem_pthread.dylib
0x000000018b441024 _pthread_wqthread + 216
16  libsystem_pthread.dylib
0x000000018b43fd94 start_wqthread + 8
), DVTRadarComponentKey=261622,
NSLocalizedDescription=Could not support development.}},
NSLocalizedRecoverySuggestion=If
you are certain that Xcode supports development on this
device, try disconnecting and reconnecting the device.,
NSLocalizedFailure=This operation can fail if the
version of the OS on the device is newer than the version of Xcode that is
running., DVTRadarComponentKey=487927,
NSLocalizedDescription=Failed to prepare device for development.}) {
AssociatedMobileDeviceFunction = AMDeviceMountImage;
DVTRadarComponentKey = 487927;
NSLocalizedDescription = "Failed to prepare device
for development.";
NSLocalizedFailure = "This operation can fail if
the version of the OS on the device is newer than the version of Xcode
that is running.";
NSLocalizedRecoverySuggestion = "If you are certain
that Xcode supports development on this device, try disconnecting
and reconnecting the device.";
NSUnderlyingError = "Error
Domain=com.apple.dt.MobileDeviceErrorDomain Code=-402653066 "Could not
support
development."
UserInfo={MobileDeviceErrorCode=(0xE8000076),
com.apple.dtdevicekit.stacktrace=(\n\t0   DTDeviceKitBase
0x00000001044612f8
DTDKCreateNSErrorFromAMDErrorCode + 272\n\t1   DTDeviceKitBase
0x000000010449ad84
-[DTDKMobileDeviceToken
_mountDeveloperDiskImage:withError:] + 916\n\t2   DTDeviceKitBase
0x000000010449b76c __58-[DTDKMobileDeviceToken
mountDeveloperDiskImageWithError:]_block_invoke + 556\n\t3
libdispatch.dylib
0x000000018b298420 _dispatch_client_callout + 20\n\t4   libdispatch.dylib
0x000000018b2a6a98
_dispatch_lane_barrier_sync_invoke_and_complete + 60\n\t5   DTDeviceKitBase
0x000000010449b4d8 -[DTDKMobileDeviceToken
mountDeveloperDiskImageWithError:] + 168\n\t6   IDEiOSSupportCore
0x00000001186d7dc8 __37-[DVTiOSDevice(Connect)
hasConnected]_block_invoke_2 + 272\n\t7   DVTFoundation
0x0000000105976730 DVT_CALLING_CLIENT_BLOCK +
16\n\t8   DVTFoundation                       0x000000010597b3a4
__DVTDispatchGroupAsync_block_invoke + 680\n\t9
libdispatch.dylib                   0x000000018b2968bc
_dispatch_call_block_and_release + 32\n\t10
libdispatch.dylib                   0x000000018b298420
_dispatch_client_callout + 20\n\t11
libdispatch.dylib                   0x000000018b29b82c
_dispatch_continuation_pop +
560\n\t12  libdispatch.dylib
0x000000018b29aec4 _dispatch_async_redirect_invoke + 592\n\t13
libdispatch.dylib
0x000000018b2a8fac _dispatch_root_queue_drain + 356\n\t14  libdispatch.dylib
0x000000018b2a97a4 _dispatch_worker_thread2 +
116\n\t15  libsystem_pthread.dylib             0x000000018b441024
_pthread_wqthread + 216\n\t16
libsystem_pthread.dylib             0x000000018b43fd94 start_wqthread +
8\n),
DVTRadarComponentKey=261622,
NSLocalizedDescription=Could not support development.}";
}
2021-01-22 08:19:25.708 xcdevice[51186:6969905] [MT]
iPhoneConnect: 📱<DVTiOSDevice (0x119686660), VIPhone, iPhone, 14.3
(18C66), 71abd87bd654537024591e3131cb4fd1ade326c6> --
An error occurred whilst preparing device for development -- Failed to
prepare device for development.
Domain: com.apple.dtdevicekit
Code: 806
Recovery Suggestion: If you are certain that Xcode
supports development on this device, try disconnecting and reconnecting
the device.
User Info: {
AssociatedMobileDeviceFunction = AMDeviceMountImage;
DVTRadarComponentKey = 487927;
NSLocalizedFailure = "This operation can fail if
the version of the OS on the device is newer than the version of Xcode
that is running.";
}

On Wed, Jan 20, 2021 at 2:57 AM Markus Aksli<EMAIL_ADDRESS>wrote:

Hi @dgurudot https://github.com/dgurudot
Is there anything relevant logged to flutter run -v or the device console?
Is there anything useful in Devices and Simulators?
I'm not seeing this with our M1.
Thank you
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/74244#issuecomment-763411791,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOASKKX5DJ2MVZ5X3E2OCDTS22EGZANCNFSM4WJEJLRQ
.

If I reboot the laptop then everything works perfectly fine.
I am puzzled if something or another app is creating conflict here

On Jan 22, 2021, at 8:24 AM, Digital Guru<EMAIL_ADDRESS>wrote:

I am finding the following error while running "flutter run -v". I checked that my device is using latest iOS 14.3 and Xcode is latest version 12.3
============================================================================================================================
                2021-01-22 08:19:25.707 xcdevice[51186:6970077]  DTDeviceKit: Failed to mount DDI from
                '<DVTFilePath:0x11170d210:'/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport/14.3/Develop
                erDiskImage.dmg'>', error=-402653066: Error Domain=com.apple.dtdevicekit Code=806 "Failed to prepare device for
                development." UserInfo={AssociatedMobileDeviceFunction=AMDeviceMountImage, NSUnderlyingError=0x12a894d90 {Error
                Domain=com.apple.dt.MobileDeviceErrorDomain Code=-402653066 "Could not support development."
                UserInfo={MobileDeviceErrorCode=(0xE8000076), com.apple.dtdevicekit.stacktrace=(
                    0   DTDeviceKitBase                     0x00000001044612f8 DTDKCreateNSErrorFromAMDErrorCode + 272
                    1   DTDeviceKitBase                     0x000000010449ad84 -[DTDKMobileDeviceToken _mountDeveloperDiskImage:withError:] +
                    916
                    2   DTDeviceKitBase                     0x000000010449b76c __58-[DTDKMobileDeviceToken
                    mountDeveloperDiskImageWithError:]_block_invoke + 556
                    3   libdispatch.dylib                   0x000000018b298420 _dispatch_client_callout + 20
                    4   libdispatch.dylib                   0x000000018b2a6a98 _dispatch_lane_barrier_sync_invoke_and_complete + 60
                    5   DTDeviceKitBase                     0x000000010449b4d8 -[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:] + 168
                    6   IDEiOSSupportCore                   0x00000001186d7dc8 __37-[DVTiOSDevice(Connect) hasConnected]_block_invoke_2 + 272
                    7   DVTFoundation                       0x0000000105976730 __DVT_CALLING_CLIENT_BLOCK__ + 16
                    8   DVTFoundation                       0x000000010597b3a4 __DVTDispatchGroupAsync_block_invoke + 680
                    9   libdispatch.dylib                   0x000000018b2968bc _dispatch_call_block_and_release + 32
                    10  libdispatch.dylib                   0x000000018b298420 _dispatch_client_callout + 20
                    11  libdispatch.dylib                   0x000000018b29b82c _dispatch_continuation_pop + 560
                    12  libdispatch.dylib                   0x000000018b29aec4 _dispatch_async_redirect_invoke + 592
                    13  libdispatch.dylib                   0x000000018b2a8fac _dispatch_root_queue_drain + 356
                    14  libdispatch.dylib                   0x000000018b2a97a4 _dispatch_worker_thread2 + 116
                    15  libsystem_pthread.dylib             0x000000018b441024 _pthread_wqthread + 216
                    16  libsystem_pthread.dylib             0x000000018b43fd94 start_wqthread + 8
                ), DVTRadarComponentKey=261622, NSLocalizedDescription=Could not support development.}}, NSLocalizedRecoverySuggestion=If
                you are certain that Xcode supports development on this device, try disconnecting and reconnecting the device.,
                NSLocalizedFailure=This operation can fail if the version of the OS on the device is newer than the version of Xcode that is
                running., DVTRadarComponentKey=487927, NSLocalizedDescription=Failed to prepare device for development.}
                2021-01-22 08:19:25.707 xcdevice[51186:6970077]  iPhoneConnect: 📱<DVTiOSDevice (0x119686660), VIPhone, iPhone, 14.3
                (18C66), 71abd87bd654537024591e3131cb4fd1ade326c6> unable to mount developer disk image, (Error Domain=com.apple.dtdevicekit
                Code=806 "Failed to prepare device for development." UserInfo={AssociatedMobileDeviceFunction=AMDeviceMountImage,
                NSUnderlyingError=0x12a894d90 {Error Domain=com.apple.dt.MobileDeviceErrorDomain Code=-402653066 "Could not support
                development." UserInfo={MobileDeviceErrorCode=(0xE8000076), com.apple.dtdevicekit.stacktrace=(
                    0   DTDeviceKitBase                     0x00000001044612f8 DTDKCreateNSErrorFromAMDErrorCode + 272
                    1   DTDeviceKitBase                     0x000000010449ad84 -[DTDKMobileDeviceToken _mountDeveloperDiskImage:withError:] +
                    916
                    2   DTDeviceKitBase                     0x000000010449b76c __58-[DTDKMobileDeviceToken
                    mountDeveloperDiskImageWithError:]_block_invoke + 556
                    3   libdispatch.dylib                   0x000000018b298420 _dispatch_client_callout + 20
                    4   libdispatch.dylib                   0x000000018b2a6a98 _dispatch_lane_barrier_sync_invoke_and_complete + 60
                    5   DTDeviceKitBase                     0x000000010449b4d8 -[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:] + 168
                    6   IDEiOSSupportCore                   0x00000001186d7dc8 __37-[DVTiOSDevice(Connect) hasConnected]_block_invoke_2 + 272
                    7   DVTFoundation                       0x0000000105976730 __DVT_CALLING_CLIENT_BLOCK__ + 16
                    8   DVTFoundation                       0x000000010597b3a4 __DVTDispatchGroupAsync_block_invoke + 680
                    9   libdispatch.dylib                   0x000000018b2968bc _dispatch_call_block_and_release + 32
                    10  libdispatch.dylib                   0x000000018b298420 _dispatch_client_callout + 20
                    11  libdispatch.dylib                   0x000000018b29b82c _dispatch_continuation_pop + 560
                    12  libdispatch.dylib                   0x000000018b29aec4 _dispatch_async_redirect_invoke + 592
                    13  libdispatch.dylib                   0x000000018b2a8fac _dispatch_root_queue_drain + 356
                    14  libdispatch.dylib                   0x000000018b2a97a4 _dispatch_worker_thread2 + 116
                    15  libsystem_pthread.dylib             0x000000018b441024 _pthread_wqthread + 216
                    16  libsystem_pthread.dylib             0x000000018b43fd94 start_wqthread + 8
                ), DVTRadarComponentKey=261622, NSLocalizedDescription=Could not support development.}}, NSLocalizedRecoverySuggestion=If
                you are certain that Xcode supports development on this device, try disconnecting and reconnecting the device.,
                NSLocalizedFailure=This operation can fail if the version of the OS on the device is newer than the version of Xcode that is
                running., DVTRadarComponentKey=487927, NSLocalizedDescription=Failed to prepare device for development.}) {
                    AssociatedMobileDeviceFunction = AMDeviceMountImage;
                    DVTRadarComponentKey = 487927;
                    NSLocalizedDescription = "Failed to prepare device for development.";
                    NSLocalizedFailure = "This operation can fail if the version of the OS on the device is newer than the version of Xcode
                    that is running.";
                    NSLocalizedRecoverySuggestion = "If you are certain that Xcode supports development on this device, try disconnecting
                    and reconnecting the device.";
                    NSUnderlyingError = "Error Domain=com.apple.dt.MobileDeviceErrorDomain Code=-402653066 \"Could not support
                    development.\" UserInfo={MobileDeviceErrorCode=(0xE8000076), com.apple.dtdevicekit.stacktrace=(\n\t0   DTDeviceKitBase
                    0x00000001044612f8 DTDKCreateNSErrorFromAMDErrorCode + 272\n\t1   DTDeviceKitBase                     0x000000010449ad84
                    -[DTDKMobileDeviceToken _mountDeveloperDiskImage:withError:] + 916\n\t2   DTDeviceKitBase
                    0x000000010449b76c __58-[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:]_block_invoke + 556\n\t3
                    libdispatch.dylib                   0x000000018b298420 _dispatch_client_callout + 20\n\t4   libdispatch.dylib
                    0x000000018b2a6a98 _dispatch_lane_barrier_sync_invoke_and_complete + 60\n\t5   DTDeviceKitBase
                    0x000000010449b4d8 -[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:] + 168\n\t6   IDEiOSSupportCore
                    0x00000001186d7dc8 __37-[DVTiOSDevice(Connect) hasConnected]_block_invoke_2 + 272\n\t7   DVTFoundation
                    0x0000000105976730 __DVT_CALLING_CLIENT_BLOCK__ + 16\n\t8   DVTFoundation                       0x000000010597b3a4
                    __DVTDispatchGroupAsync_block_invoke + 680\n\t9   libdispatch.dylib                   0x000000018b2968bc
                    _dispatch_call_block_and_release + 32\n\t10  libdispatch.dylib                   0x000000018b298420
                    _dispatch_client_callout + 20\n\t11  libdispatch.dylib                   0x000000018b29b82c _dispatch_continuation_pop +
                    560\n\t12  libdispatch.dylib                   0x000000018b29aec4 _dispatch_async_redirect_invoke + 592\n\t13
                    libdispatch.dylib                   0x000000018b2a8fac _dispatch_root_queue_drain + 356\n\t14  libdispatch.dylib
                    0x000000018b2a97a4 _dispatch_worker_thread2 + 116\n\t15  libsystem_pthread.dylib             0x000000018b441024
                    _pthread_wqthread + 216\n\t16  libsystem_pthread.dylib             0x000000018b43fd94 start_wqthread + 8\n),
                    DVTRadarComponentKey=261622, NSLocalizedDescription=Could not support development.}";
                }
                2021-01-22 08:19:25.708 xcdevice[51186:6969905] [MT] iPhoneConnect: 📱<DVTiOSDevice (0x119686660), VIPhone, iPhone, 14.3
                (18C66), 71abd87bd654537024591e3131cb4fd1ade326c6> -- An error occurred whilst preparing device for development -- Failed to
                prepare device for development.
                Domain: com.apple.dtdevicekit
                Code: 806
                Recovery Suggestion: If you are certain that Xcode supports development on this device, try disconnecting and reconnecting
                the device.
                User Info: {
                    AssociatedMobileDeviceFunction = AMDeviceMountImage;
                    DVTRadarComponentKey = 487927;
                    NSLocalizedFailure = "This operation can fail if the version of the OS on the device is newer than the version of Xcode
                    that is running.";
                }

On Wed, Jan 20, 2021 at 2:57 AM Markus Aksli<EMAIL_ADDRESS>wrote:
Hi @dgurudot
Is there anything relevant logged to flutter run -v or the device console?
Is there anything useful in Devices and Simulators?
I'm not seeing this with our M1.
Thank you
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

If I reboot the laptop then everything works perfectly fine.
I am puzzled if something or another app is creating conflict here

On Jan 22, 2021, at 8:24 AM, Digital Guru<EMAIL_ADDRESS>wrote:

I am finding the following error while running "flutter run -v". I checked that my device is using latest iOS 14.3 and Xcode is latest version 12.3
============================================================================================================================
                2021-01-22 08:19:25.707 xcdevice[51186:6970077]  DTDeviceKit: Failed to mount DDI from
                '<DVTFilePath:0x11170d210:'/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport/14.3/Develop
                erDiskImage.dmg'>', error=-402653066: Error Domain=com.apple.dtdevicekit Code=806 "Failed to prepare device for
                development." UserInfo={AssociatedMobileDeviceFunction=AMDeviceMountImage, NSUnderlyingError=0x12a894d90 {Error
                Domain=com.apple.dt.MobileDeviceErrorDomain Code=-402653066 "Could not support development."
                UserInfo={MobileDeviceErrorCode=(0xE8000076), com.apple.dtdevicekit.stacktrace=(
                    0   DTDeviceKitBase                     0x00000001044612f8 DTDKCreateNSErrorFromAMDErrorCode + 272
                    1   DTDeviceKitBase                     0x000000010449ad84 -[DTDKMobileDeviceToken _mountDeveloperDiskImage:withError:] +
                    916
                    2   DTDeviceKitBase                     0x000000010449b76c __58-[DTDKMobileDeviceToken
                    mountDeveloperDiskImageWithError:]_block_invoke + 556
                    3   libdispatch.dylib                   0x000000018b298420 _dispatch_client_callout + 20
                    4   libdispatch.dylib                   0x000000018b2a6a98 _dispatch_lane_barrier_sync_invoke_and_complete + 60
                    5   DTDeviceKitBase                     0x000000010449b4d8 -[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:] + 168
                    6   IDEiOSSupportCore                   0x00000001186d7dc8 __37-[DVTiOSDevice(Connect) hasConnected]_block_invoke_2 + 272
                    7   DVTFoundation                       0x0000000105976730 __DVT_CALLING_CLIENT_BLOCK__ + 16
                    8   DVTFoundation                       0x000000010597b3a4 __DVTDispatchGroupAsync_block_invoke + 680
                    9   libdispatch.dylib                   0x000000018b2968bc _dispatch_call_block_and_release + 32
                    10  libdispatch.dylib                   0x000000018b298420 _dispatch_client_callout + 20
                    11  libdispatch.dylib                   0x000000018b29b82c _dispatch_continuation_pop + 560
                    12  libdispatch.dylib                   0x000000018b29aec4 _dispatch_async_redirect_invoke + 592
                    13  libdispatch.dylib                   0x000000018b2a8fac _dispatch_root_queue_drain + 356
                    14  libdispatch.dylib                   0x000000018b2a97a4 _dispatch_worker_thread2 + 116
                    15  libsystem_pthread.dylib             0x000000018b441024 _pthread_wqthread + 216
                    16  libsystem_pthread.dylib             0x000000018b43fd94 start_wqthread + 8
                ), DVTRadarComponentKey=261622, NSLocalizedDescription=Could not support development.}}, NSLocalizedRecoverySuggestion=If
                you are certain that Xcode supports development on this device, try disconnecting and reconnecting the device.,
                NSLocalizedFailure=This operation can fail if the version of the OS on the device is newer than the version of Xcode that is
                running., DVTRadarComponentKey=487927, NSLocalizedDescription=Failed to prepare device for development.}
                2021-01-22 08:19:25.707 xcdevice[51186:6970077]  iPhoneConnect: 📱<DVTiOSDevice (0x119686660), VIPhone, iPhone, 14.3
                (18C66), 71abd87bd654537024591e3131cb4fd1ade326c6> unable to mount developer disk image, (Error Domain=com.apple.dtdevicekit
                Code=806 "Failed to prepare device for development." UserInfo={AssociatedMobileDeviceFunction=AMDeviceMountImage,
                NSUnderlyingError=0x12a894d90 {Error Domain=com.apple.dt.MobileDeviceErrorDomain Code=-402653066 "Could not support
                development." UserInfo={MobileDeviceErrorCode=(0xE8000076), com.apple.dtdevicekit.stacktrace=(
                    0   DTDeviceKitBase                     0x00000001044612f8 DTDKCreateNSErrorFromAMDErrorCode + 272
                    1   DTDeviceKitBase                     0x000000010449ad84 -[DTDKMobileDeviceToken _mountDeveloperDiskImage:withError:] +
                    916
                    2   DTDeviceKitBase                     0x000000010449b76c __58-[DTDKMobileDeviceToken
                    mountDeveloperDiskImageWithError:]_block_invoke + 556
                    3   libdispatch.dylib                   0x000000018b298420 _dispatch_client_callout + 20
                    4   libdispatch.dylib                   0x000000018b2a6a98 _dispatch_lane_barrier_sync_invoke_and_complete + 60
                    5   DTDeviceKitBase                     0x000000010449b4d8 -[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:] + 168
                    6   IDEiOSSupportCore                   0x00000001186d7dc8 __37-[DVTiOSDevice(Connect) hasConnected]_block_invoke_2 + 272
                    7   DVTFoundation                       0x0000000105976730 __DVT_CALLING_CLIENT_BLOCK__ + 16
                    8   DVTFoundation                       0x000000010597b3a4 __DVTDispatchGroupAsync_block_invoke + 680
                    9   libdispatch.dylib                   0x000000018b2968bc _dispatch_call_block_and_release + 32
                    10  libdispatch.dylib                   0x000000018b298420 _dispatch_client_callout + 20
                    11  libdispatch.dylib                   0x000000018b29b82c _dispatch_continuation_pop + 560
                    12  libdispatch.dylib                   0x000000018b29aec4 _dispatch_async_redirect_invoke + 592
                    13  libdispatch.dylib                   0x000000018b2a8fac _dispatch_root_queue_drain + 356
                    14  libdispatch.dylib                   0x000000018b2a97a4 _dispatch_worker_thread2 + 116
                    15  libsystem_pthread.dylib             0x000000018b441024 _pthread_wqthread + 216
                    16  libsystem_pthread.dylib             0x000000018b43fd94 start_wqthread + 8
                ), DVTRadarComponentKey=261622, NSLocalizedDescription=Could not support development.}}, NSLocalizedRecoverySuggestion=If
                you are certain that Xcode supports development on this device, try disconnecting and reconnecting the device.,
                NSLocalizedFailure=This operation can fail if the version of the OS on the device is newer than the version of Xcode that is
                running., DVTRadarComponentKey=487927, NSLocalizedDescription=Failed to prepare device for development.}) {
                    AssociatedMobileDeviceFunction = AMDeviceMountImage;
                    DVTRadarComponentKey = 487927;
                    NSLocalizedDescription = "Failed to prepare device for development.";
                    NSLocalizedFailure = "This operation can fail if the version of the OS on the device is newer than the version of Xcode
                    that is running.";
                    NSLocalizedRecoverySuggestion = "If you are certain that Xcode supports development on this device, try disconnecting
                    and reconnecting the device.";
                    NSUnderlyingError = "Error Domain=com.apple.dt.MobileDeviceErrorDomain Code=-402653066 \"Could not support
                    development.\" UserInfo={MobileDeviceErrorCode=(0xE8000076), com.apple.dtdevicekit.stacktrace=(\n\t0   DTDeviceKitBase
                    0x00000001044612f8 DTDKCreateNSErrorFromAMDErrorCode + 272\n\t1   DTDeviceKitBase                     0x000000010449ad84
                    -[DTDKMobileDeviceToken _mountDeveloperDiskImage:withError:] + 916\n\t2   DTDeviceKitBase
                    0x000000010449b76c __58-[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:]_block_invoke + 556\n\t3
                    libdispatch.dylib                   0x000000018b298420 _dispatch_client_callout + 20\n\t4   libdispatch.dylib
                    0x000000018b2a6a98 _dispatch_lane_barrier_sync_invoke_and_complete + 60\n\t5   DTDeviceKitBase
                    0x000000010449b4d8 -[DTDKMobileDeviceToken mountDeveloperDiskImageWithError:] + 168\n\t6   IDEiOSSupportCore
                    0x00000001186d7dc8 __37-[DVTiOSDevice(Connect) hasConnected]_block_invoke_2 + 272\n\t7   DVTFoundation
                    0x0000000105976730 __DVT_CALLING_CLIENT_BLOCK__ + 16\n\t8   DVTFoundation                       0x000000010597b3a4
                    __DVTDispatchGroupAsync_block_invoke + 680\n\t9   libdispatch.dylib                   0x000000018b2968bc
                    _dispatch_call_block_and_release + 32\n\t10  libdispatch.dylib                   0x000000018b298420
                    _dispatch_client_callout + 20\n\t11  libdispatch.dylib                   0x000000018b29b82c _dispatch_continuation_pop +
                    560\n\t12  libdispatch.dylib                   0x000000018b29aec4 _dispatch_async_redirect_invoke + 592\n\t13
                    libdispatch.dylib                   0x000000018b2a8fac _dispatch_root_queue_drain + 356\n\t14  libdispatch.dylib
                    0x000000018b2a97a4 _dispatch_worker_thread2 + 116\n\t15  libsystem_pthread.dylib             0x000000018b441024
                    _pthread_wqthread + 216\n\t16  libsystem_pthread.dylib             0x000000018b43fd94 start_wqthread + 8\n),
                    DVTRadarComponentKey=261622, NSLocalizedDescription=Could not support development.}";
                }
                2021-01-22 08:19:25.708 xcdevice[51186:6969905] [MT] iPhoneConnect: 📱<DVTiOSDevice (0x119686660), VIPhone, iPhone, 14.3
                (18C66), 71abd87bd654537024591e3131cb4fd1ade326c6> -- An error occurred whilst preparing device for development -- Failed to
                prepare device for development.
                Domain: com.apple.dtdevicekit
                Code: 806
                Recovery Suggestion: If you are certain that Xcode supports development on this device, try disconnecting and reconnecting
                the device.
                User Info: {
                    AssociatedMobileDeviceFunction = AMDeviceMountImage;
                    DVTRadarComponentKey = 487927;
                    NSLocalizedFailure = "This operation can fail if the version of the OS on the device is newer than the version of Xcode
                    that is running.";
                }

On Wed, Jan 20, 2021 at 2:57 AM Markus Aksli<EMAIL_ADDRESS>wrote:
Hi @dgurudot
Is there anything relevant logged to flutter run -v or the device console?
Is there anything useful in Devices and Simulators?
I'm not seeing this with our M1.
Thank you
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

In any case this doesn't seem like an issue with flutter, but rather the apple development environment. You could try submitting this to https://feedbackassistant.apple.com/ or the Xcode forums but for now it seems like this isn't the place for the issue so I'm going to close it.
If this does turn out to be an issue with flutter just let me know and I will reopen.

In any case this doesn't seem like an issue with flutter, but rather the apple development environment. You could try submitting this to https://feedbackassistant.apple.com/ or the Xcode forums but for now it seems like this isn't the place for the issue so I'm going to close it.
If this does turn out to be an issue with flutter just let me know and I will reopen.

Just wanted to add an update that latest android studio update and flutter upgrade automatically fixed this issue.

On Jan 25, 2021, at 8:26 AM, Markus Aksli<EMAIL_ADDRESS>wrote:

Closed #74244.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


Settings are not sorted when the language is other than English

Microsoft PowerToys version
0.74.1
Installation method
GitHub, PowerToys auto-update
Running as admin
No
Area(s) with issue?
Settings
Steps to reproduce
Set the Windows language to a value other than English
✔ Expected Behavior
Settings are reordered in alphabetical order
❌ Actual Behavior
Settings remain in the order of the English language, creating confusion when searching for a specific setting
Other Software
No response

Thanks for your message. This is a Duplicate of an other issue. Additional comments may be added there. /dup #23763


Idempotent creationPolicy option that tries to 'Merge' but reverts to 'Owner'

Is your feature request related to a problem? Please describe.
Currently if I am determining a strategy to propagate a secret that is common to many namespaces on a Kubernetes cluster after the cluster has been bootstrapped. Due to the nature of ESO creation policies, if I need to deploy my registry credentials into a handful of namespaces, I can't create a ExternalClusterSecret that will create the secret if it doesn't exist in the namespace, or instead merge the secret contents into an existing secret.  So I could define 2 external cluster secrets with different creation policies, but why not have a creation policy that is more or less idempotent - make sure the secret exists one way or the other - and try if anything to update relevant keys (ie merge) when there is a secret.
Describe the solution you'd like
a creation policy that is more or less idempotent - make sure the secret exists one way or the other - and try if anything to update relevant keys (ie merge) when there is a secret.
ie if the secret exists, apply the merge creationpolicy. if the secret does not exist create the secret.
Describe alternatives you've considered
I could define 2 external cluster secrets with different creation policies, depending on whether or not the secret should exist in a bootstrapping/day2 provisioning scenario
Additional context
Add any other context or screenshots about the feature request here.

Hi @charles-horel-rogers !  The problem with the revert behavior you're mentioning is that CreationPolicy: Owner means as soon as the ExternalSecret manifest is deleted, the secret is also deleted. This is not true for CreationPolicy: Merge (where only some keys of that secret are cleaned up.
To your point in question - have you tried CreationPolicy: Orphan? I believe it will have the outcomes as you'd wish.


Moving dbatools test to Pester 5.1

General Info
This is for informational and discussion...
Jakub will be releasing Pester 5.1 within this week (if not today). I have been writing tests exclusively for this version in a module for work while it was in beta and have discovered many things that make it more efficient. As well, test output can be manipulated much easier among other things.
Technical
We've discussed in Slack a few times of just moving bits around in our tests so it plays nice with Pester 5 and will at least run. After working with it now I'm in disagreement with this method and think it will benefit us going forward if we migrate our tests to the new structure and syntax.
I'll also pin this so just it brings attention.
Plan
I believe we should treat this work as a release, as we did with the 1.0 release. I'll create a branch that we can work from and being migrating a few so we can figure out a new "template". This will give us a starting reference. I'll likely save the "big" tests for the end (e.g. Backup commands) to ensure the proper folks review these separately...since they hold more weight on our module.
Additionally, integration tests that we have not been able to write previously due to Appveyor limitations will be created so we can run them locally. The AG commands being the primary use case. These will just be skipped for the Appveyor workload. It might be possible to also have these tests exempt from Appveyor and being transitioning to GitHub Actions since we can create an AG in that environment (at least using Linux containers) more easily.

Note for contributors: At this time this will be work done by the maintainers until we can reach a point with the template that will provide a stable "guide" for contributors to follow. At that time this issue will be updated. You can "subscribe" to this issue if you would like to receive updates as the progress moves forward.

if it is faster and has coverage (which were the main pain points a few months back when we evaluated this possibility) then okay

Code coverage is in the same state it was. Pester 5.1 at this time your PowerShell process will crash when you use -CI parameter to generate a code coverage report.
Ref: pester/pester#1769

then it still is a major letdown/con for the "migration" ?

It's not a priority for them to fix right now in Pester unless someone from the community is going to contribute to help Jakub fix it. I see no reason to wait as the code coverage is only used for reference. We are not dependent upon it with PRs or overall contributions to the module.
I do not see it as something that will hold us back from migrating to the newer version and features of Pester. As well, the knowledge we (maintainers and authors) have of our commands is sufficient to know whether a given test covers the primary functionality in the associated command.
We can't sit back and wait indefinitely for code coverage support to come back.

I'm just stating what was the end of the previous discussion, which was, more or less "the cons are that pester5 is slightly slower and it does not have coverage".
I agree we can't sit back indefinitely but coverage, especially for dbatools with loads of functions which are just tested with a few params combination, if not at all, for me is a huge deal (and I wasn't the only one advocating for it).

Code coverage is now functioning in Pester.


enhance: set Input or Textarea component carert position when user call element foucs function

[ ] I'm sure this does not appear in the issue list of the repository

Basic Info
What are the similar cases of this feature

What problem does this feature solve?
set Input or Textarea component caret position when user call element focus function

related issue: #758


Adds tests for travis2tox

@msabramo could you please review this when you get a chance?

Thanks, @caioariede!


Flask-Restful XML output

This is the code below is from the examply .py file for Flask restful to output in XML.
from simplexml import dumps
from flask import make_response, Flask
from flask_restful import Api, Resource

def output_xml(data, code, headers=None):
    """Makes a Flask response with a XML encoded body"""
    resp = make_response(dumps({'response' :data}), code)
    resp.headers.extend(headers or {})
    return resp

app = Flask(__name__)
api = Api(app, default_mediatype='application/xml')
api.representations['application/xml'] = output_xml

class Hello(Resource):
    """
        # you need requests
        >>> from requests import get
        >>> get('http://localhost:5000/me').content # default_mediatype
        '<?xml version="1.0" ?><response><hello>me</hello></response>'
        >>> get('http://localhost:5000/me', headers={"accept":"application/json"}).content
        '{"hello": "me"}'
        >>> get('http://localhost:5000/me', headers={"accept":"application/xml"}).content
        '<?xml version="1.0" ?><response><hello>me</hello></response>'
    """
    def get(self, entry):
        return {'hello': entry}

api.add_resource(Hello, '/<string:entry>')

if __name__ == '__main__':
    app.run(debug=True)

What I notice in my testing with the requests library is I need to add the header headers={'Accept': 'application/xml'} for the Flask app to return XML. Is it possible to edit the Flask code above to always output XML regardless of a header?
import requests
import xml
from xml.etree import ElementTree

response = requests.post("http://<IP_ADDRESS>:5000/scenarioThree", headers={'Accept': 'application/xml'})
#response = requests.post("http://<IP_ADDRESS>:5000/scenarioThree")

root = ElementTree.fromstring(response.content)
for child in root.iter('*'):
    print(child.tag)

If I do a:
response = requests.get("http://<IP_ADDRESS>:5000/scenarioThree")

print(response.content)

This gives me a JSON response back..
b'{\n    "hello": "scenarioThree"\n}\n'
Using:
response = requests.post("http://<IP_ADDRESS>:5000/scenarioThree", headers={'Accept': 'application/xml'})
Gives me XML:
b'<?xml version="1.0" ?><response><message>The method is not allowed for the requested URL.</message></response>'

Would I always need to pass a header to define the content type no matter what? Thanks

Else in the example code for XML. This doesnt work on my machine

For others that find this, it looks like Flask-RESTful grabs the first KV in the OrderedDict api.representations
The workaround I used (where I wanted default_mediatype="text/yaml") was to use after all the representations are setup:
api.representations.move_to_end('text/yaml', last=False)


The question is undefined about "$".

Hi,friend!
I have a question,took a look at code below:
seajs.use(['zepto','frozen','layzr','{:ADDON_PUBLIC_PATH}/js/Course'],function(Zepto,frozen,layzr,course){
console.log(Zepto);
course.init();
});
Why is "Zepto" undefined?

open your browser's console to check if your zepto.js is loaded

Thanks friend,I have resolved this question.


Problem: pg_rewind fails in presence of omni_httpd extension files in postgres data directory

Solution: use temp directory to store omni_httpd unix socket file
#479

I found that there's TempTablespacePath
Worth a quick research to see if the dedicated temp path in the tablespace would be tolerated by pg_rewind?

I considered using it but found out it is used by postgres to spill data that can't fit in memory for eg. sorting


[Feature Request] Add optional headers to notification config

It would be good to be able to pass arbitrary headers when setting up notifications in the config. In my case, I'm connecting to an SMSC API and need to pass in some Basic Auth:
# post to SMSC proxy for text messaging
notification sms{
    post = "https://some.box.com/api/sms/1/outbound/tel:+5555/requests/"
    body = { "outboundSMSMessageRequest": { "senderAddress": "tel:+5555", "outboundSMSTextMessage": { "message": {{.|json}} }, "address": [ "tel:+1234567890" ], "receiptRequest":{} } }
    contentType = "application/json"
    # add zero or more headers
    headers = { "Authorization": "Basic jkflsdjlfdsjfjslfjskfjs=", "Accept": "application/json", "Cache-Control": "no-cache" }
}

Will be fixed in https://github.com/bosun-monitor/bosun/pull/2135

@kylebrandt Can you clarify how #2135 implements this? I don't see anything in that PR or in the documentation on how to set headers besides the content-type header.


Fix svd tests on GPU

Description
Fixes #328

Moves tensors to CPU before checking with assert
Checks absolute value of SVD vectors instead of the vectors themselves.

As I mentioned in #328, SVD is not numerically stable so different hardware gives different results. From the pytorch docs: This non-uniqueness is caused by the fact that multiplying any pair of singular vectors u_k, v_k by -1 in the real case produces another two valid singular vectors of the matrix. So I think comparing v.abs() in the tests should get around this issue.
I have run the tests on M1 Mac, Ubuntu with GPU, Ubuntu without GPU.
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] New and existing unit tests pass locally with my changes
[x] I have not rewritten tests relating to key interfaces which would affect backward compatibility

cheers.


fix(application request): display documents

Description
display appropriate document information in the company details overlay
Why
document is present in the api but not displayed in the ui
Issue
#915
Checklist
Please delete options that are not relevant.

[x] I have followed the contributing guidelines
[ ] I have performed IP checks for added or updated 3rd party libraries
[ ] I have created and linked IP issues or requested their creation by a committer
[x] I have performed a self-review of my own code
[x] I have successfully tested my changes locally
[ ] I have added tests that prove my changes work
[ ] I have checked that new and existing tests pass locally with my changes
[ ] I have commented my code, particularly in hard-to-understand areas

@oyo pr check failed here but in local all working fine
capelit81991526:portal-frontend mgkoush$ yarn pretty --check
yarn run v1.22.19
$ prettier --write "**/*.{ts,tsx,js,jsx,json,css,sass,scss,xml,yml,yaml,md}" --check
Checking formatting...
All matched files use Prettier code style!
✨  Done in 4.21s.


Refunds

Hi, I have been reading the docs but can't see anything about refunds. Great package by the way :) Let me know, thanks

Refunds are straightforward and not needed to be done via the package, you simply standard cashier, feeding in the ID of the payment intent / charge.
Happy to assist further if you're stuck.


Add Appsignal configuration

This adds Appsignal to the app. We're evaluating to see if it is a good replacement for Errbit, while also adding performance tracking.
It's only activated if APPSIGNAL_API_KEY is set, which is currently only in integration (https://github.com/alphagov/govuk-puppet/pull/5376 https://github.gds/gds/deployment/pull/1215).
cc @carvil
https://trello.com/c/J3kDeZD7

Merging now that puppet ran on the backend servers in integration and the key is set.


Generate and review yosemite_oai_dc data validation reports

More details in line 8: https://docs.google.com/spreadsheets/d/1XkBwi8jiuGgrWvQBqjkrbavSl13yyrQNyRyEb_CQ4z0/edit#gid=1100474517

oai.yosemite: 2 endpoints, 4 published collections

Dropping in the list of URLs generated in Airflow:
[2023-10-25, 22:48:12 UTC] {{logging_mixin.py:137}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/26989/validation/10-25-2023T22:47:30.csv [2023-10-25, 22:48:12 UTC] {{logging_mixin.py:137}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#26989/ [2023-10-25, 22:48:12 UTC] {{logging_mixin.py:137}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27016/validation/10-25-2023T22:47:31.csv [2023-10-25, 22:48:12 UTC] {{logging_mixin.py:137}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27016/ [2023-10-25, 22:48:12 UTC] {{logging_mixin.py:137}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27631/validation/10-25-2023T22:47:35.csv [2023-10-25, 22:48:12 UTC] {{logging_mixin.py:137}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27631/ [2023-10-25, 22:48:12 UTC] {{logging_mixin.py:137}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27632/validation/10-25-2023T22:48:11.csv [2023-10-25, 22:48:12 UTC] {{logging_mixin.py:137}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27632/

Validation results reported here: https://github.com/ucldc/rikolti/issues/606

[2024-01-24, 01:47:06 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/26989/vernacular_metadata_2024-01-24T01:40:36/mapped_metadata_2024-01-24T01:45:41/validation_2024-01-24T01:46:24.csv
[2024-01-24, 01:47:06 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#26989/vernacular_metadata_2024-01-24T01:40:36/mapped_metadata_2024-01-24T01:45:41/data/
[2024-01-24, 01:47:06 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27016/vernacular_metadata_2024-01-24T01:40:39/mapped_metadata_2024-01-24T01:45:41/validation_2024-01-24T01:46:25.csv
[2024-01-24, 01:47:06 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27016/vernacular_metadata_2024-01-24T01:40:39/mapped_metadata_2024-01-24T01:45:41/data/
[2024-01-24, 01:47:06 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27631/vernacular_metadata_2024-01-24T01:40:45/mapped_metadata_2024-01-24T01:45:42/validation_2024-01-24T01:46:28.csv
[2024-01-24, 01:47:06 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27631/vernacular_metadata_2024-01-24T01:40:45/mapped_metadata_2024-01-24T01:45:42/data/
[2024-01-24, 01:47:06 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27632/vernacular_metadata_2024-01-24T01:41:15/mapped_metadata_2024-01-24T01:45:47/validation_2024-01-24T01:47:06.csv
[2024-01-24, 01:47:06 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27632/vernacular_metadata_2024-01-24T01:41:15/mapped_metadata_2024-01-24T01:45:47/data/

Accepted on 2024-01-26.


TimeZone parsing not resilient

I received following execution.time in execDetails: "'20230928 11:17:24 MET'"
in this case condition if "/" in execution.time: is not executed and exception is thrown during datetime.strptime(time_str, "%Y%m%d  %H:%M:%S") -> sth like "MET not expected"
Not all TimeZones have "/" in the name: https://www.ibm.com/docs/en/cloudpakw3700/<IP_ADDRESS>?topic=SS6PD2_2.3.0/doc/psapsys_restapi/time_zone_list.htm

https://www.dataquest.io/blog/python-datetime/

sample testcase:
from datetime import datetime
from unittest import TestCase
from unittest.mock import Mock

from ibapi.contract import Contract
from ibapi.execution import Execution

from vnpy_ib.ib_gateway import IbApi

class TestIbGateway(TestCase):

    def test_SHOULD_convert_EST_date_properly(self):
        # given
        contract = a_contract()
        execution = an_execution(time='20230424 17:15:00 EST')

        ib_gateway = Mock()
        # ib_gateway.normalize = lambda number: round(number, 2)
        ib_api = IbApi(gateway=ib_gateway)

        # when
        ib_api.execDetails(reqId=1, contract=contract, execution=execution)

        # then
        ib_gateway.on_trade.assert_called_once()
        ib_gateway.on_trade.call_args[0][0].datetime.strftime('%Y%m%d %H:%M:%S %Z') == '20230424 17:15:00 EST'

def a_contract():
    return Contract()

def a_time_str():
    datetime.now().strftime('%Y%m%d %H:%M:%S %Z')

def an_execution(time=a_time_str(), side='BOT'):
    execution = Execution()
    execution.time = time
    execution.side = side
    return execution

Thanks. I will check on this.

已修复https://github.com/vnpy/vnpy_ib/pull/29

The strftime function cannot identify IANA time zone such as Hongkong and US/Eastern. Therefore, it is better to split spaces of the time string and convert them separately.


Merge string keys import support commit

I found that neither command line nor http endpoint support string keys import on master branch.
When master merge the commit Support keys on import CLI. on develop branch?

@zhyhang you can track this in #1599. It's awaiting review, but should be on master later today.

@zhyhang this has been merged.
There is a follow up PR #1601 related to importing with keys into integer fields.

#1601 has been merged as well.


Date de situation actuelle socio pro : modification du phrasé

#915

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


Combine lists in submission data to strings so they are decoded

This fix converts checkbox responses from a list to a string before returning the submission data.
This is necessary to ensure the contents of the list are decoded when the submission is displayed.

👍


fix: add  to the blog markdown files #240

Fixes: #240
Changes:
update blogs
Screenshots of the change:

ping @LiteSun


Updated list of artifacts that have signed up for automated releases.

Added 2 more libraries the Azure SDK team owns that were missing from this list.

/check-enforcer override

/check-enforcer override


added TodoList

I have added my Todolist project

ok

I have made the changes

add item not working

it works after some time

it works after some time

please fix it


need to remove dependabot in our repos

now we decided to use renovate and it fulfills the task. Need to disable dependabot on all our repos

Dependabot is disabled on all repos.


TT-3661 - validate mnemonic based signing

Task linked: TT-3661 [KMS, CELO] signing a mnemonic based transaction without an index doesn't raise any validation and passes normally


Login Via Truecaller not working in webview, but works in Chrome

[x] I have read the Get Started - Installation section
[x] I have read and done the Get Started - Setup Android section
[x] I have read and done the Get Started - Setup iOS section
[x] I have already searched for the same problem

Environment

Technology
Version

Flutter version
2.10.5

Plugin version
flutter_inappwebview: ^5.4.3+7

Android version
12

iOS version
NA

Xcode version
NA

Device information:
Description

Login Via Truecaller is suggesting name on loggin pop up but when trying to login via truecaller, its not working. Whereas when try same in chrome browser, its working.
Install Truecaller
Try https://www.purplle.com/ in mobile webivew, go to login section.

Expected behavior:
Current behavior:
Steps to reproduce

This
Than that
Then

Images
Stacktrace/Logcat

@pichillilorenzo Basically, Truecaller launch a intent-
truecallersdk://truesdk/web_verify?requestNonce=0f6a5b72-365f-4a86-ac5b-d71581a75ef2&partnerKey=FOXvM3bc9658bc7f8420498b7337e61a995ca&partnerName=1MG&lang=en&title=Sign%20in&skipOption=useAnotherNum
how to handle this, and make login successful, and return to exisitng web page.

we cannot always invoke truecaller SDK from webview, as the user may or may not have TrueCaller installed in app.
One way which worked for me was to skip this TrueCaller verification invocation, on website which do it before loggin in the user.
we can override shouldOverrideUrlLoading the and add following code to skip TrueCallerSDK URI
 String url = request.getUrl().toString(); if (url.startsWith("truecallersdk://")) {                    isTrueCallerSDKCalled = true;                    return true;                 }


Improve flexibility of release scripts

This changeset accomplishes three things:

Allow specifying a different GPG key identifier (can be name or email). The default is the old value, releasedocker.
Allow specifying a path inside the S3 bucket to upload files to. The default is empty string, to preserve the old behavior.
Upload the apt/yum repository files to S3 as well as binaries. This is a new behavior.

These goal of changes are to aid testing of the release workflow as well as support alternate releases (e.g. LTS).

ping @tianon @jfrazelle for review, thanks!

Why did you remove the setup_gpg function? if that's on purpose, there is a reference to it that needs to be removed too.

@calavera thanks for noticing, honestly i think maybe it was from a poor rebase/conflict resolution. this has been moved around on a few different forks/branches. fixing things up now!

Are we planning an LTS release? :smile:

@tianon In response to both LTS and repo comments:
Yea, this is actually for the commerically supported (CS) releases which will have LTS and 'current' versions. Currently we're planning on hosting through S3 so putting the repos up there is part of my requirements. Given that, is there a concern with including the release_repos step in addition to the nginx+CDN hosting Jessie does?

Yes -- the "release_repos" step is done from a separate machine from the
one running "release.sh", so it won't actually work for the project's
official releases.

Hm, maybe I'm not understanding completely. I don't see another release_repos anywhere (just the one I added here). Am I missing something?

for some reason i fell out of this conversation without realizing there was something else for me to do. I just put back release_ubuntu in place of release_repos and rebased+pushed. sorry for the delay; have another look!

Seems sane enough; LGTM

LGTM


Bug Report -  | sign does not work using a german language keyboard (QWERTZ)

-->
Environment
Windows build number: Windows 1903
Windows Terminal version (if applicable): 0.2.1715.0
Any other software?
Tried different version of PSh (5.x / 6.2.1 / 7.0.0), and CMD
Steps to reproduce
the sign | cannot by typed using a german keyboard in Windows 10.
Expected behavior
I expected this sign to work as it is one of the most important commands in PoSh
Actual behavior
the output is < instead of |
parent issues:
#521
related duplicate issues:
#1596,#940,#1027,#1010

If this issue isn’t different from its parent issue, please don’t file it. I don’t think we need a new issue for every single keyboard key that doesn’t work with AltGr


fail to build on macOS

There are several problems in the Makefile
rm -f parser.go; make
make parser
bin/goyacc -o /dev/null parser.y
Parse table entries: 758041 of 1909026, x 16 bits == 1516082 bytes
bin/goyacc -o parser.go parser.y 2>&1 | egrep "(shift|reduce)/reduce" | awk '{print} END {if (NR > 0) {print "Find conflict in parser.y. Please check y.output for more information."; exit 1;}}'
rm -f y.output
sed: -e: No such file or directory
make[1]: *** [parser] Error 1
make: *** [parser.go] Error 2

@darren parser has be removed to http://github/pingcap/parser, please update project and remove /parser folder

@lysu
you mean https://github.com/pingcap/parser/?

Please merge the master branch and make again. @darren


Need to assert on identity type mismatch in FetchForWriting()

Had a user issue the other day. When using the FetchForWriting() functionality, the aggregate document identity type has to match the stream type in order to function. We need to make the exception be very clear about what's wrong when this happens.

I don't remember why (maybe based on some older examples), but I had this line in the Marten configuration code for the Product aggregate:
_.Events.AddEventType(typeof(Product));

As a result the issue with the mismatch reproduced to me. When I removed that line everything started working normal. According to the description of that AddEventType method it's optional, but helps Marten in some way. How would I need to call it not to break the FetchForWriting()?


Minor Enhacnement: Change name of module from "library" to something branch related

In android studio your Project lists the downloaded External Libraries:
crashlytics-2.5.3
facebook-android-sdk-4.5.0
gson-2.4
...
and then shows the branch sdk as:
library-1.10.1
it would be nicer if the library had a name indicating that it was the branch sdk

@jt-gilkeson  Thanks for suggesting this. We will change to more meaning full name in coming versions

@jt-gilkeson if change the library name, our partners need to change the grade dependency name in order to upgrade to newer versions of SDK. So unless they change the dependency they may not get the  updated versions. We would really like to name it as you suggested but seems like  existing users  will have  lot of confusion

@sojanpr Wonder if you could publish on maven to both names?  i.e. publish to the "meaningful name" and also publish to "library" (to handle people who don't update their gradle)

@jt-gilkeson at this point we don't want to introduce a confusion for partners with having multiple artifacts in maven. Your suggestion is really valid and we will make the change some time later.So closing this issue for now. Thank you for your suggestion.


cmd/go: improve go help goproxy

'go help goproxy' describes the module proxy protocol, and it needs to document more details to guide correct proxy implementation.

'go get; issues a  /latest query to go proxy, (https://go.googlesource.com/go/+/master/src/cmd/go/internal/modfetch/proxy.go#185) but this type of query is not documented.

document what's the expected results for for non modules.
For example, what's the expected results or error code for the following module or package?

   golang.org/x/tools/@v/list
   golang.org/x/tools/@latest
   golang.org/x/tools/go/@latest

   github.com/rogpeppe/godef/go/@v/list
   github.com/rogpeppe/godef/go/@latest

specify appropriate error codes the go command expects for various error conditions.

@bcmills @rsc

CC @marwan-at-work

@ianthehat

Is this still in go1.12 milestone?
Is it a possibility to get rid of the /@latest query in the protocol?
Would be nice if the document can help figuring out why go get (without -m) issues both list and latest queries.

> go get -v -d golang.org/x/tools/cmd/guru/serial
Fetching http://localhost:8080/golang.org/x/tools/cmd/guru/serial/@v/list
go: finding golang.org/x/tools/cmd/guru/serial latest
Fetching http://localhost:8080/golang.org/x/tools/cmd/guru/serial/@latest
Fetching http://localhost:8080/golang.org/x/tools/cmd/guru/serial/@v/list
Fetching http://localhost:8080/golang.org/x/tools/cmd/guru/@v/list
go: finding golang.org/x/tools/cmd/guru latest
Fetching http://localhost:8080/golang.org/x/tools/cmd/guru/@latest
Fetching http://localhost:8080/golang.org/x/tools/cmd/guru/@v/list
Fetching http://localhost:8080/golang.org/x/tools/cmd/@v/list
go: finding golang.org/x/tools/cmd latest
Fetching http://localhost:8080/golang.org/x/tools/cmd/@latest
Fetching http://localhost:8080/golang.org/x/tools/cmd/@v/list
Fetching http://localhost:8080/golang.org/x/tools/@v/list
go: finding golang.org/x/tools v0.0.0-20181212200058-49db546f375e
Fetching<EMAIL_ADDRESS>go: downloading golang.org/x/tools v0.0.0-20181212200058-49db546f375e
Fetching<EMAIL_ADDRESS>go: extracting golang.org/x/tools v0.0.0-20181212200058-49db546f375e
Fetching<EMAIL_ADDRESS>

Ops, I've missed the cc notification on this one.
So I opened a CL a while ago (https://go-review.googlesource.com/c/go/+/126615) that updated the documentation and @bcmills suggested to look at potentially removing @latest endpoint from the GOPROXY contract.
From what I know, having @latest is a nice separation from @v/list because @latest has one clear intention: give me the latest pseudo version that is available in the "upstream"
@v/list on the other hand can be one of a few things: maybe a GOPROXY only wants to list certain versions, maybe it wants a combination of upstream and whatever it has stored, etc.
GOPROXY implementers therefore, can easily miss the fact that when the implement their own @v/list endpoint, that that they have to go to upstream and get the latest commit sha and turn it into a pseudo version, and then lump it with the other versions.
BTW, go list -m -versions -json gives you a "Latest" and a "Versions" response accordingly.

Thanks @marwan-at-work for the explanation. Can you update your cl to mention this bug?
One minor thing - If the @latest query corresponds to the 'Version' field of the go list -m -json output, it doesn't necessarily mean the latest pseudo version.

> go list -m -versions -json golang.org/x/textgo: finding golang.org/x/text v0.3.0
{
	"Path": "golang.org/x/text",
	"Version": "v0.3.0",
	"Versions": [
		"v0.1.0",
		"v0.2.0",
		"v0.3.0"
	],
	"Time": "2017-12-14T13:08:43Z"
}

vs.

go list -m -versions -json golang.org/x/text@master
go: finding golang.org/x/text master
{
	"Path": "golang.org/x/text",
	"Version": "v0.0.0-20181211190257-17bcc049122f",
	"Versions": [
		"v0.1.0",
		"v0.2.0",
		"v0.3.0"
	],
	"Time": "2018-12-11T19:02:57Z"
}

I don't know why the pseudo version picks up v0.0.0 instead of v0.3.0 (maybe related to #29262).

@hyangah this is because you specified @master explicitly. You're looking to get the latest from that branch, therefore you get the pseudo version (note it's not really v0.0.0 but v0.0.0-20181211190257-17bcc049122f which denotes the "latest" commit from master.
But good call out, go list will give you the latest semver tag, unless there are no tags. Similarly, the go command will pick the latest version from @v/list and not ping @latest unless @v/list returns an empty list.

Looking again into the go list -m -json -versions output, there is no "Latest" field. I think the "Version" field indicates the version the main module is using (so in the module cache) or specified version, not the latest.
So, I am still not sure what's the purpose of this latest query.
Regarding the v0.0.0 comment, I meant the prefix used to generate the pseudo version.

Let's close this since now there is a comprehensive set of documentation about modules.


Comment tag for primitive types

Feature Request
Thank you for making this, I'm super grateful for all your effort.
I would really appreciate if this library supported comment tags on primitive types.
For example I would like to be able to do this:
// @type int
type Int = number;
typia.assert<Int>(500.5); // Should throw

Would that be possible?

Awesome lib, I was always so lazy to write complex types + complex validation and now I can mostly just write good types 🚀
I needed to do something similar to this, maybe would fit into this feature request
/**
 * @format date
 */
type LatestUpdateDate = string | undefined;

export type TableStates = {
  [K in keyof PossibleTables]: LatestUpdateDate;
};

where the expected outcome was to validate each string for date format

Not possible, getting comment tags in TS API is only possible for object property type.

/**
 * @minimum 3
 * @maximum 100
 */
type MyNumber = number;

@chmanie When you type like above, TS compiler just considers the MyNumber type as an alias type of number, and do not archive comment tags in API. Therefore, I don't have any way to come true your suggestion. @LucasSegersFabro  About the dynamic key property type, it is not possible, either.
Instead, what about validating through wrapping like below?
import typia from "typia";

interface IntWrapper {
    /**
     * @type int
     */
    value: number;
}
typia.assert<IntWrapper>({ value: 500.5 });

@samchon yeah, that should work fine, thanks for the suggestion


Added Simple Paint App Extension

🛠 Fixes Issue
#251
👨💻 Changes proposed

🔧 Check List (Check the type of issue it fixes)

[ ] Bug Fix
[x] New Extension
[ ] Enhancement
[ ] Documentation

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers
📷 Screenshots

https://user-images.githubusercontent.com/72568715/166144033-e2915f7b-6af0-4848-9b7f-89bca011cb1d.mp4

@Sulagna-Dutta-Roy thanks for contributing!!


Cherry-pick #26324 to 2.47.0 branch.

Note: if you are far ahead in building an RC, you don't need to rebuild for the sake of this change.


Refactoring framework group structure

Moving external and system frameworks into Framework groups.

I plan to take a look at this in the next couple of days.

No problem. Meanwhile, I'll keep studying Vienna code.


Fix unknown addresses issue

fixed in 9ea5f04491209937e89e6804185140685d7d41c7 (v1.7.5). Bug was introduced while adding pseudo coinbase inputs in v1.7.0. After that change only new coinbase txs where inserted.


Release F branch PR

Profile pages improvements

Added lazy load approach to fetching civilServant entity (with custom hql queries utilizing lazy fetch)
added userId (for usage on lpg-ui)
added an optional accessLog filter for logging request details

Restored eager loading of children entitities for now

Co-authored-by: Michal Piatek<EMAIL_ADDRESS>Co-authored-by: Matt Doherty<EMAIL_ADDRESS>

Build connector from Github side seems to have timed out... need to push a readme change to trigger branch build


Nightly redeploy with RGD main branch

This deployment regularly lags pretty far behind RGD dev. I'd like for it to stay up to date between releases
Can we change the depends to pull from RGD's main branch and have Heroku rebuild more frequently if not nightly?

1c30fa3 set it up so that Heroku installs from the main branch of the RGD repo

The recent introduction of dependabot should keep the pinned versions of RGD up to date as releases are cut. Pinning the version helps us work around Heroku's build cache


[FEAT]ip被封无法登入，能不能像pandora一样绕开cf的检查？或者增加一个手动设置令牌的方式？

Is your feature request related to a problem? / 你想要的功能和什么问题相关？
ip被封，导致使用gpt3.5的时候一直卡在登入的cf检查中，一直循环

Describe the solution you'd like. / 你想要的解决方案是什么？
绕开cf检查，或者手动设置token的快捷入口
Describe alternatives you've considered. / 你考虑过的其他方案是什么？
No response
Additional context / 其他信息
No response

怎么绕开 cf 检查啊？

怎么绕开 cf 检查啊？

Use Cloudflare Workers

有个开源项目Cloudflare Workers，你可以参考一下

我现在用Poe的ChatGPT3.5，但感觉POE好像是阉割版本

不知道是心理作用还是真的就是阉割

作者可以去看看Pandora项目，它是利用一个虚拟网站获取openai的api，然后在验证的时候填写，它的那个虚拟站的域名就好，其实就是添加一个自定义api接口的选项，刚才我试了设置，但没成功

作者可以去看看Pandora项目，它是利用一个虚拟网站获取openai的api，然后在验证的时候填写，它的那个虚拟站的域名就好，其实就是添加一个自定义api接口的选项，刚才我试了设置，但没成功

或许需要加上v1

怎么绕开 cf 检查啊？

Use Cloudflare Workers

@msaong 这是需要在 cf 开个服务当跳板？

作者可以去看看Pandora项目，它是利用一个虚拟网站获取openai的api，然后在验证的时候填写，它的那个虚拟站的域名就好，其实就是添加一个自定义api接口的选项，刚才我试了设置，但没成功

ChatALL 不会以这种方式部署服务端的。会坚持客户端、只可以「人」用的定位

怎么绕开 cf 检查啊？

Use Cloudflare Workers

@msaong 这是需要在 cf 开个服务当跳板？

Yes, that's pretty much it. Do you have time to work on this? I see that there are quite a few tagged requirements at the moment, and I'm not sure about the current priority level. Do you need me to take this? However, I'm also short on time, so it would probably take me a while to get it done.

作者可以去看看Pandora项目，它是利用一个虚拟网站获取openai的api，然后在验证的时候填写，它的那个虚拟站的域名就好，其实就是添加一个自定义api接口的选项，刚才我试了设置，但没成功

ChatALL 不会以这种方式部署服务端的。会坚持客户端、只可以「人」用的定位

Simple solution,  we only need a domain replacement feature to replace the OpenAI domain. This feature is only for API requests.

Simple solution, we only need a domain replacement feature to replace the OpenAI domain. This feature is only for API requests.

What you mean is a customizable setting of ChatGPT base URL or ChatALL setup a proxy in cf worker?

Yes, that's pretty much it. Do you have time to work on this? I see that there are quite a few tagged requirements at the moment, and I'm not sure about the current priority level. Do you need me to take this? However, I'm also short on time, so it would probably take me a while to get it done.

It is funny to use Cloudflare to skip Cloudflare anti-spam checking. If it is a general solution and can have effects on all websites which depends on CF anti-spam checking, that will be great. There are several other LLMs usually request the checking and block direct API access.
It is great that you can finish this.

The statements in this section are mainly aimed at OpenAI's API solutions. There are now many API forwarding services available, and the code is very straightforward. However, this solution is only applicable to OpenAI's API (including Azure's API).

The feature has been provided. I misunderstood the previous discussion.


Implement REST API for listing, creating and deleting address spaces

This fixes issue #86

The 'update' operation is not exposed since we haven't defined how that should work yet.


Move optional=True in toml

I am removing the optional=True from tool.poetry.group.dev.dependencies.
Reason:
I converted sssom-py to be a product of this cookiecutter. When I poetry install for the first time, all's well. But when I do it the second time or run any of the following:

poetry install --all-extras
poetry install -E docs
poetry install -E tests

It deletes virtualenv and 3 other packages.
  • Removing distlib (0.3.6)
  • Removing filelock (3.12.2)
  • Removing platformdirs (3.6.0)
  • Removing virtualenv (20.23.1)
  • Updating urllib3 (1.26.16 -> 2.0.3)

The next time I run any poetry command it errors out saying virtualenv doesn't exist.
ModuleNotFoundError: No module named 'virtualenv'

The only fix is to reinstall poetry and start over again.
Investigation:
It seemed like in the poetry.lock file all the libraries that were uninstalled had optional=True. When I took them out from the toml file.
Using the latest version of poetry v1.5.1

Solution:
A new design of the toml file where:

We get rid of the extras section [[tool.poetry.extras]]
We create groups of packages depending on their purpose: e.g.

[tool.poetry.group.docs]
optional = true

[tool.poetry.group.docs.dependencies]
sphinx = {version = ">=6.1.3"}
sphinx-rtd-theme = {version = ">=1.0.0"}
sphinx-autodoc-typehints = {version = ">=1.2.0"}
sphinx-click = {version = ">=4.3.0"}
myst-parser = {version = ">=0.18.1"}

optional packages are declared as shown above


Template Literals newline.

Looked everywhere and could not find anything about template literals and newlines.  I am on windows and have not tried on *NIX.  this is with the console logger
winston.info(`
-------OrderTable-------
Total Unmatched Orders: ${results[0]}
Unmatched Buys: ${results[1]}
Unmatched Sells: ${results[2]}
Unmatched Buy Range: ${results[5][0].price} - ${results[5][1].price}
Unmatched Sell Range: ${results[6][0].price} - ${results[6][1].price}
Open Buys: ${results[3]}
Open Sells: ${results[4]}
------------------------
`);

Results in
{"message":"\n-------OrderTable-------\nTotal Unmatched Orders: 21\nUnmatched Buys: 18\nUnmatched Sells: 3\nUnmatched Buy Range: 0.00055581 - 0.00055112\nUnmatched Sell Range: 0.00055695 - 0.00055578\nOpen
Buys: 3\nOpen Sells: 0\n------------------------\n","level":"info"}

Is there a way to make winston respect the new lines?  I also tried adding a \r to the end of each line and it didn't work.

Same issue
code:
 logger.debug(err.message, {
    data: err.data,
    stack: err.stack
  })

got
"data": {
    "email"<EMAIL_ADDRESS>    "id": "5aa05f8b9d4e3247656215a4"
  },
  "stack": "Error: Token info altered, token being hacked\n    at _callee5$ (/home/hansen/projects/gooloo/back-end/src/controller/adminController.js:80:17)\n    at tryCatch (/home/hansen/projects/gooloo/back-end/node_modules/babel-polyfill/node_modules/regenerator-runtime/runtime.js:65:40)\n    at Generator.invoke [as _invoke] (/home/hansen/projects/gooloo/back-end/node_modules/babel-polyfill/node_modules/regenerator-runtime/runtime.js:303:22)\n    at Generator.prototype.(anonymous function) [as next] (/home/hansen/projects/gooloo/back-end/node_modules/babel-polyfill/node_modules/regenerator-runtime/runtime.js:117:21)\n
}

You want to define a custom formats. e.g.
'use strict';

const { createLogger, format, transports } = require('../');
const logger = createLogger({
  format: format.printf(info => info.message),
  transports: [new transports.Console()]
});

logger.info(`
  Hey this is a multi line string
  wouldn't it be great it if it was displayed
  in the console as a multi-line string instead
  of a JSON.stringify-ed object with \\n characters?
`)

Outputs:
$ node scratch/newlines.js

  Hey this is a multi line string
  wouldn't it be great it if it was displayed
  in the console as a multi-line string instead
  of a JSON.stringify-ed object with \n characters?


Dynamic element not showing list item..

Item was not show but the ajax post is fine... The list not showing..help...
.find('#j_input_'+inc).each(function () {
$(this).easyAutocomplete({
url: "products.json",
getValue: "item_code",
ajaxSettings: {
dataType: "json",
method: "POST",
data: {
dataType: "json"
}
}
});
})

@kyawhtetsan facing same issue. @pawelczak need your help on this.


Problems with my deployment of the project to hololens2:DllNotFoundException: Unable to load DLL 'ws2_32.dll'.

The "InTheHand.Net.Bluetooth" can perform good in the Unity 3D
but after deployment of the project to the Hololens2 there is bug shown .
DllNotFoundException: Unable to load DLL 'ws2_32.dll'. Tried the load the following dynamic libraries: Unable to load dynamic library 'ws2_32.dll' because of 'C:\buildslave\unity\build\External\il2cpp\builds\external\baselib\Source\WinApi\Baselib_DynamicLibrary_WinApi.inl.h(36):Baselib_DynamicLibrary_OpenUtf16: Failed to open the requested dynamic library (0x06000000) - The specified module could not be found.  (WinError:0000007e)
at InTheHand.Net.Sockets.Win32Socket+NativeMethods.socket (System.Net.Sockets.AddressFamily af, System.Net.Sockets.SocketType type, System.Net.Sockets.ProtocolType protocol)
How can I solve this issue?
Thank you so much for your reading.

Yes, this is a complicated one because there are two Windows APIs for Bluetooth classic - the original Win32 using Sockets and the Windows 10 API. Hololens doesn't have the legacy Win32 APIs and that is why you are seeing this error.
At the moment there isn't a single dll build of InTheHand.Net.Bluetooth containing both implementations so it depends what your consuming project targets as to which dll you get from the NuGet package. A UWP App will always get the Windows 10 API. If you use Unity in .NET 4.x compatibility it will use the .NET 4.6.1 dll which uses the Win32 API.
With Windows versions prior to 10 leaving support it might be the case that we eventually switch the .NET4.6.1 dll to use the Windows 10 API, but at the moment I know there are still people supporting Windows 7 and 8.1 and using the library.

I'm getting pretty much the exact same error but for a different dll. My error is
DllNotFoundException: Unable to load DLL 'kernel32.dll'. Tried the load the following dynamic libraries: Unable to load dynamic library 'kernel32.dll' because of 'C:\build\output\unity\unity\External\il2cpp\builds\external\baselib\Source\WinApi\Baselib_DynamicLibrary_WinApi.inl.h(36):Baselib_DynamicLibrary_OpenUtf16: Failed to open the requested dynamic library (0x06000000) - The specified module could not be found.  (WinError:0000007e)
For my project, I'm trying to communicate to the hololens from my laptop over tcp sockets. My program works locally but gives this error when I deploy to the hololens. How can I get the right packages or DLLs so that my program runs on the hololens?


[NNBD] Type bounds issue

The following code produces an error in analyzer and no issues in VM
class C<X> {
  test(X x) {
    var v = {x, 1, 2}; // Analyzer error - The element type 'X' can't be assigned to the set type 'Object'
  }
}

main() {
  C<int>().test(42);
}

Similarly
class C<K, V> {
  test(K k, V v) {
    var m = {k: v, 1: 2};//  Analyzer:  error - The element type 'K' can't be assigned to the map key type 'Object'.
                         // error - The element type 'V' can't be assigned to the map value type 'Object'.
  }
}

main() {
  C<int, int>().test(3, 4);
}

@eernstg Is analyzer behavior correct here?
Dart SDK version: 2.10.0-59.0.dev (dev) (Tue Aug 25 18:05:44 2020 -0700) on "windows_x64"

I won't make a promise of understanding all the intricacies of type parameter bound based computations, but it doesn't seem right!
The analyzer infers Object as the element type of the set, likely as the least upper bound of X and int, but the bound of X is Object?/dynamic, so Object is not an upper bound of X and anything.
It mainly appears to affect collection literals. If I change the set literal to a list literal, I get the error:
Couldn't infer type parameter 'E'. Tried to infer 'Object' for 'E' which doesn't work: Parameter 'element' declared as 'E' but argument is 'X'. The type 'Object' was inferred from: Parameter 'element' declared as 'E' but argument is 'int'. Consider passing explicit type argument(s) to the generic. - line 3
``
instead.

If I add `extends Object`, `extends Object?` or `extends dynamic` to the declaration of `X`, the error goes away, so the problem appears to be based on the *default* bound, which is no longer `Object` in null safe code. (Did we make it `Obejct?`, or is it `dynamic`?)

It's not just collection literals, though. I get the same error for
```dart
class C<X> {
  test(X x) {
    var v = G(x, 1, 2);
  }
}

class G<Z> {
  G(Z x, Z y, Z z);
}
main() {
  C<int>().test(42);
}

as for the list literal.

The analyzer might be using a pre-null-safety assumed bound for the type variable in this situation. In any case, the element type of {x, 1, 2} should be UP(UP(X, int), int)) which is Object?

I believe this was fixed in cf5e8a7a2f9f36ed70a9d74da2d7869fdd557c45.
In these examples the analyzer infers now Set<Object?> and Map<Object?, Object?>.


README: E.123 number for meeting call

And fix a period/paren swap.  The period/paren swap and contry-code addition both bring the local version more in line with the image-spec version and seem like good changes.
I've diverged from the image-spec version by using space separation in the phone number instead of hyphens.  From E.123:

9.1  Grouping of digits in a telephone number⁵ should be accomplished by means or spaces⁶ unless an agreed upon explicit symbol (e.g. hyphen) is necessary for procedural purposes. Only spaces should be used in an international number.

LGTM

LGTM


cuda error in 4.0 alpha when trying to download from browser.

2023-01-18 16-37-17: set full screen mode
2023-01-18 16-37-17: network: get simulation list
2023-01-18 16-37-21: 1 CUDA device found
2023-01-18 16-37-21: device 0: NVIDIA GeForce RTX 3070 Ti with compute capability 8.6
2023-01-18 16-37-21: device 0 is set
2023-01-18 16-37-24: initialize simulation
2023-01-18 16-37-25: resize arrays
2023-01-18 16-37-25: cell array size: 200000
2023-01-18 16-37-25: particle array size: 200000
2023-01-18 16-37-25: token array size: 66666
2023-01-18 16-37-25: 760 MB GPU memory acquired
2023-01-18 16-37-39: network: download simulation with id=125
2023-01-18 16-37-43: close simulation
2023-01-18 16-37-43: initialize simulation
2023-01-18 16-37-43: The following exception occurred: CUDA error at C:\alien\source\EngineGpuKernels\CudaMemoryManager.cuh:30 code=2(cudaErrorMemoryAllocation) "cudaMalloc(&result, sizeof(T)*arraySize)"

Here is the log.txt

您好，您的邮件已收到，我会尽快回复，谢谢。
蔡陈翼

东南大学建筑学院

南京市玄武区四牌楼2号Tel：18652966253

I just noticed I forgot to checkout to the v4 branch 🤦


use Material for wireframes

Objective

Use the Material abstraction for the Wireframes

Right now this doesn't have many benefits other than simplifying some of the rendering code
We can reuse the default vertex shader and avoid rendering inconsistencies
The goal is to have a material with a color on each mesh so this approach will make it easier to implement

Originally done in https://github.com/bevyengine/bevy/pull/5303 but I decided to split the Material part to it's own PR and then adding per-entity colors and globally configurable colors will be a much simpler diff.

Solution

Use the new Material abstraction for the Wireframes

Notes
It's possible this isn't ideal since this adds a Handle<WireframeMaterial> to all the meshes compared to the original approach that didn't need anything. I didn't notice any performance impact on my machine.
This might be a surprising usage of Material at first, because intuitively you only have one material per mesh, but the way it's implemented you can have as many different types of materials as you want on a mesh.
Migration Guide
WireframePipeline was removed. If you were using it directly, please create an issue explaining your use case.

I'm on board with this direction; unifying this is nice.

@alice-i-cecile from a user perspective there is no breaking change right now

It's the same WireframePlugin and Wireframe Component that was used before, it's just the internals that changed, so I don't think it counts as breaking.

It may be worth turning the original version without the material into an example since it was a good reference for rendering something simple without using the material system.

I think the mesh2d_manual serves that purpose pretty well. Maybe we should have a 3d version

How does this relate to #5303?

How does this relate to https://github.com/bevyengine/bevy/pull/5303?

I think it was just me trying to aggressively reduce the size of the PR and have the customizable color in it's own PR

I think I addressed everything. Should be good to got now.

I realized we don't need the vertex shader anymore since we can use the vertex shader from the Material api. This also fixed a bug where wireframes are broken in DX12 because of some vertex shader issues.

There's now a few conflicts because of the wireframe override PR. I personally think the api of that PR is flawed so I I'll submit a PR with an API that isn't a breaking change and should create less conflict with this PR.

I fixed the conflicts with the NoWireframe feature. I believe this is ready for a final review.

I don't know what's up with the CI failure. It works fine locally and it's complaining about completely unrelated parts of the codebase.