traffic_graphs.widget: start when widgets is visible

Hi!
after a long investigation in the "messages" on the forum, it turned out that the traffic_graph widget is still not quite stable in the Firefox browser. The FF can start requests before the widgets are visible. As a result, the chart plugin assigns the canvas height to 0 (chartjs does not like if the parent element is hidden when the chart is initialized) and it start to look like https://github.com/opnsense/core/issues/4750.
To reproduce the behavior, you can set a breakpoint on the         $("#traffic_graphs-configure").removeClass("disabled"); in FF and refresh the page. It should be seen that the widgets div are not yet visible before executing the request.
Could you consider adding an event after placing widgets and launching a widget functions on this trigger?
This change tested and gave: "TF loads every time on both my desktop (with all extensions enabled) and mobile FF!"
Thanks!
and that trigger can be used on other client-side widget to start fetching when all page is set
ps.
and its looks like this lines not needed any more. since we cut scripts from widgets. works with or without it
https://github.com/opnsense/core/blob/7ac736d46920a4e81c55ee82be304d9b9713d1d7/src/www/widgets/widgets/traffic_graphs.widget.php#L67-L72

you're right, we can drop the traffic_graph_widget_loaded as well now, thanks! if you update the PR, I'll make sure to pull both in.

@AdSchellevis thanks!! updated

@kulikov-a looks good, thanks! I haven't tried it myself yet, but it looks safe enough to pull in now

@AdSchellevis thanks again!


fix(firestore, ios): exclude relevant architecture

With 9.2.0 onwards this is happening without this chage:
Xcode's output:
↳
    Writing result bundle at path:
    	/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/flutter_tools.8UFPl6/flutter_ios_build_temp_diryBNGa1/temporary_xcresult_bundle
    warning: [CP] BoringSSL-GRPC.xcframework: Unable to find matching slice in 'ios-arm64 ios-arm64_x[86](https://github.com/firebase/flutterfire/runs/7094273749?check_suite_focus=true#step:9:87)_64-maccatalyst ios-arm64_x86_64-simulator' for the current build architectures (arm64 x86_64 i386) and platform (-iphonesimulator).
    warning: [CP] FirebaseFirestore.xcframework: Unable to find matching slice in 'ios-arm64_x86_64-simulator ios-arm64_x86_64-maccatalyst ios-arm64' for the current build architectures (arm64 x86_64 i386) and platform (-iphonesimulator).
    warning: [CP] FirebaseFirestoreSwift.xcframework: Unable to find matching slice in 'ios-arm64 ios-arm64_x86_64-maccatalyst ios-arm64_x86_64-simulator' for the current build architectures (arm64 x86_64 i386) and platform (-iphonesimulator).
    warning: [CP] Libuv-gRPC.xcframework: Unable to find matching slice in 'ios-arm64_x86_64-simulator ios-arm64 ios-arm64_x86_64-maccatalyst' for the current build architectures (arm64 x86_64 i386) and platform (-iphonesimulator).
    warning: [CP] abseil.xcframework: Unable to find matching slice in 'ios-arm64 ios-arm64_x86_64-simulator ios-arm64_x86_64-maccatalyst' for the current build architectures (arm64 x86_64 i386) and platform (-iphonesimulator).
    warning: [CP] gRPC-C++.xcframework: Unable to find matching slice in 'ios-arm64_x86_64-simulator ios-arm64 ios-arm64_x86_64-maccatalyst' for the current build architectures (arm64 x86_64 i386) and platform (-iphonesimulator).
    warning: [CP] gRPC-Core.xcframework: Unable to find matching slice in 'ios-arm64_x86_64-maccatalyst ios-arm64_x86_64-simulator ios-arm64' for the current build architectures (arm64 x86_64 i386) and platform (-iphonesimulator).
    While building module 'FirebaseMessaging' imported from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/Headers/Public/Firebase/Firebase.h:66:
    In file included from <module-includes>:1:
    In file included from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/Target Support Files/FirebaseMessaging/FirebaseMessaging-umbrella.h:13:
    In file included from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FirebaseMessaging.h:18:
    /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FIRMessagingExtensionHelper.h:37:38: warning: 'UNMutableNotificationContent' is only available on iOS 10.0 or newer [-Wunguarded-availability]
    - (void)populateNotificationContent:(UNMutableNotificationContent *)content
                                         ^
    In module 'UserNotifications' imported from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FIRMessagingExtensionHelper.h:22:
    /Applications/Xcode_13.3.1.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator15.4.sdk/System/Library/Frameworks/UserNotifications.framework/Headers/UNNotificationContent.h:[97](https://github.com/firebase/flutterfire/runs/7094273749?check_suite_focus=true#step:9:98):12: note: 'UNMutableNotificationContent' has been marked as being introduced in iOS 10.0 here, but the deployment target is iOS 9.0.0
    @interface UNMutableNotificationContent : UNNotificationContent
               ^
    While building module 'FirebaseMessaging' imported from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/Headers/Public/Firebase/Firebase.h:66:
    In file included from <module-includes>:1:
    In file included from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/Target Support Files/FirebaseMessaging/FirebaseMessaging-umbrella.h:13:
    In file included from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FirebaseMessaging.h:18:
    /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FIRMessagingExtensionHelper.h:37:1: note: annotate 'populateNotificationContent:withContentHandler:' with an availability attribute to silence this warning
    - (void)populateNotificationContent:(UNMutableNotificationContent *)content
    ^
    /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FIRMessagingExtensionHelper.h:38:47: warning: 'UNNotificationContent' is only available on iOS 10.0 or newer [-Wunguarded-availability]
                     withContentHandler:(void (^)(UNNotificationContent *_Nonnull))contentHandler;
                                                  ^
    In module 'UserNotifications' imported from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FIRMessagingExtensionHelper.h:22:
    /Applications/Xcode_13.3.1.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator15.4.sdk/System/Library/Frameworks/UserNotifications.framework/Headers/UNNotificationContent.h:37:12: note: 'UNNotificationContent' has been marked as being introduced in iOS 10.0 here, but the deployment target is iOS 9.0.0
    @interface UNNotificationContent : NSObject <NSCopying, NSMutableCopying, NSSecureCoding>
               ^
    While building module 'FirebaseMessaging' imported from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/Headers/Public/Firebase/Firebase.h:66:
    In file included from <module-includes>:1:
    In file included from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/Target Support Files/FirebaseMessaging/FirebaseMessaging-umbrella.h:13:
    In file included from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FirebaseMessaging.h:18:
    /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FIRMessagingExtensionHelper.h:37:1: note: annotate 'populateNotificationContent:withContentHandler:' with an availability attribute to silence this warning
    - (void)populateNotificationContent:(UNMutableNotificationContent *)content
    ^
    2 warnings generated.
    2 warnings generated.
    While building module 'FirebaseMessaging' imported from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/Headers/Public/Firebase/Firebase.h:66:
    In file included from <module-includes>:1:
    In file included from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/Target Support Files/FirebaseMessaging/FirebaseMessaging-umbrella.h:13:
    In file included from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FirebaseMessaging.h:18:
    /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FIRMessagingExtensionHelper.h:37:38: warning: 'UNMutableNotificationContent' is only available on iOS 10.0 or newer [-Wunguarded-availability]
    - (void)populateNotificationContent:(UNMutableNotificationContent *)content
                                         ^
    In module 'UserNotifications' imported from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FIRMessagingExtensionHelper.h:22:
    /Applications/Xcode_13.3.1.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator15.4.sdk/System/Library/Frameworks/UserNotifications.framework/Headers/UNNotificationContent.h:97:12: note: 'UNMutableNotificationContent' has been marked as being introduced in iOS 10.0 here, but the deployment target is iOS 9.0.0
    @interface UNMutableNotificationContent : UNNotificationContent
               ^
    While building module 'FirebaseMessaging' imported from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/Headers/Public/Firebase/Firebase.h:66:
    In file included from <module-includes>:1:
    In file included from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/Target Support Files/FirebaseMessaging/FirebaseMessaging-umbrella.h:13:
    In file included from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FirebaseMessaging.h:18:
    /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FIRMessagingExtensionHelper.h:37:1: note: annotate 'populateNotificationContent:withContentHandler:' with an availability attribute to silence this warning
    - (void)populateNotificationContent:(UNMutableNotificationContent *)content
    ^
    /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FIRMessagingExtensionHelper.h:38:47: warning: 'UNNotificationContent' is only available on iOS 10.0 or newer [-Wunguarded-availability]
                     withContentHandler:(void (^)(UNNotificationContent *_Nonnull))contentHandler;
                                                  ^
    In module 'UserNotifications' imported from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FIRMessagingExtensionHelper.h:22:
    /Applications/Xcode_13.3.1.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator15.4.sdk/System/Library/Frameworks/UserNotifications.framework/Headers/UNNotificationContent.h:37:12: note: 'UNNotificationContent' has been marked as being introduced in iOS 10.0 here, but the deployment target is iOS 9.0.0
    @interface UNNotificationContent : NSObject <NSCopying, NSMutableCopying, NSSecureCoding>
               ^
    While building module 'FirebaseMessaging' imported from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/Headers/Public/Firebase/Firebase.h:66:
    In file included from <module-includes>:1:
    In file included from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/Target Support Files/FirebaseMessaging/FirebaseMessaging-umbrella.h:13:
    In file included from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FirebaseMessaging.h:18:
    /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FIRMessagingExtensionHelper.h:37:1: note: annotate 'populateNotificationContent:withContentHandler:' with an availability attribute to silence this warning
    - (void)populateNotificationContent:(UNMutableNotificationContent *)content
    ^
    2 warnings generated.
    2 warnings generated.
    Command CompileSwiftSources failed with a nonzero exit code
    While building module 'FirebaseMessaging' imported from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/Headers/Public/Firebase/Firebase.h:66:
    In file included from <module-includes>:1:
    In file included from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/Target Support Files/FirebaseMessaging/FirebaseMessaging-umbrella.h:13:
    In file included from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FirebaseMessaging.h:18:
    /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FIRMessagingExtensionHelper.h:37:38: warning: 'UNMutableNotificationContent' is only available on iOS 10.0 or newer [-Wunguarded-availability]
    - (void)populateNotificationContent:(UNMutableNotificationContent *)content
                                         ^
    In module 'UserNotifications' imported from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FIRMessagingExtensionHelper.h:22:
    /Applications/Xcode_13.3.1.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator15.4.sdk/System/Library/Frameworks/UserNotifications.framework/Headers/UNNotificationContent.h:97:12: note: 'UNMutableNotificationContent' has been marked as being introduced in iOS 10.0 here, but the deployment target is iOS 9.0.0
    @interface UNMutableNotificationContent : UNNotificationContent
               ^
    While building module 'FirebaseMessaging' imported from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/Headers/Public/Firebase/Firebase.h:66:
    In file included from <module-includes>:1:
    In file included from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/Target Support Files/FirebaseMessaging/FirebaseMessaging-umbrella.h:13:
    In file included from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FirebaseMessaging.h:18:
    /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FIRMessagingExtensionHelper.h:37:1: note: annotate 'populateNotificationContent:withContentHandler:' with an availability attribute to silence this warning
    - (void)populateNotificationContent:(UNMutableNotificationContent *)content
    ^
    /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FIRMessagingExtensionHelper.h:38:47: warning: 'UNNotificationContent' is only available on iOS 10.0 or newer [-Wunguarded-availability]
                     withContentHandler:(void (^)(UNNotificationContent *_Nonnull))contentHandler;
                                                  ^
    In module 'UserNotifications' imported from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FIRMessagingExtensionHelper.h:22:
    /Applications/Xcode_13.3.1.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator15.4.sdk/System/Library/Frameworks/UserNotifications.framework/Headers/UNNotificationContent.h:37:12: note: 'UNNotificationContent' has been marked as being introduced in iOS 10.0 here, but the deployment target is iOS 9.0.0
    @interface UNNotificationContent : NSObject <NSCopying, NSMutableCopying, NSSecureCoding>
               ^
    While building module 'FirebaseMessaging' imported from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/Headers/Public/Firebase/Firebase.h:66:
    In file included from <module-includes>:1:
    In file included from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/Target Support Files/FirebaseMessaging/FirebaseMessaging-umbrella.h:13:
    In file included from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FirebaseMessaging.h:18:
    /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FIRMessagingExtensionHelper.h:37:1: note: annotate 'populateNotificationContent:withContentHandler:' with an availability attribute to silence this warning
    - (void)populateNotificationContent:(UNMutableNotificationContent *)content
    ^
    2 warnings generated.
    2 warnings generated.
    While building module 'FirebaseMessaging' imported from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/Headers/Public/Firebase/Firebase.h:66:
    In file included from <module-includes>:1:
    In file included from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/Target Support Files/FirebaseMessaging/FirebaseMessaging-umbrella.h:13:
    In file included from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FirebaseMessaging.h:18:
    /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FIRMessagingExtensionHelper.h:37:38: warning: 'UNMutableNotificationContent' is only available on iOS 10.0 or newer [-Wunguarded-availability]
    - (void)populateNotificationContent:(UNMutableNotificationContent *)content
                                         ^
    In module 'UserNotifications' imported from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FIRMessagingExtensionHelper.h:22:Xcode's output:
↳
    Writing result bundle at path:
    	/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/flutter_tools.8UFPl6/flutter_ios_build_temp_diryBNGa1/temporary_xcresult_bundle
    warning: [CP] BoringSSL-GRPC.xcframework: Unable to find matching slice in 'ios-arm64 ios-arm64_x[86](https://github.com/firebase/flutterfire/runs/7094273749?check_suite_focus=true#step:9:87)_64-maccatalyst ios-arm64_x86_64-simulator' for the current build architectures (arm64 x86_64 i386) and platform (-iphonesimulator).
    warning: [CP] FirebaseFirestore.xcframework: Unable to find matching slice in 'ios-arm64_x86_64-simulator ios-arm64_x86_64-maccatalyst ios-arm64' for the current build architectures (arm64 x86_64 i386) and platform (-iphonesimulator).
    warning: [CP] FirebaseFirestoreSwift.xcframework: Unable to find matching slice in 'ios-arm64 ios-arm64_x86_64-maccatalyst ios-arm64_x86_64-simulator' for the current build architectures (arm64 x86_64 i386) and platform (-iphonesimulator).
    warning: [CP] Libuv-gRPC.xcframework: Unable to find matching slice in 'ios-arm64_x86_64-simulator ios-arm64 ios-arm64_x86_64-maccatalyst' for the current build architectures (arm64 x86_64 i386) and platform (-iphonesimulator).
    warning: [CP] abseil.xcframework: Unable to find matching slice in 'ios-arm64 ios-arm64_x86_64-simulator ios-arm64_x86_64-maccatalyst' for the current build architectures (arm64 x86_64 i386) and platform (-iphonesimulator).
    warning: [CP] gRPC-C++.xcframework: Unable to find matching slice in 'ios-arm64_x86_64-simulator ios-arm64 ios-arm64_x86_64-maccatalyst' for the current build architectures (arm64 x86_64 i386) and platform (-iphonesimulator).
    warning: [CP] gRPC-Core.xcframework: Unable to find matching slice in 'ios-arm64_x86_64-maccatalyst ios-arm64_x86_64-simulator ios-arm64' for the current build architectures (arm64 x86_64 i386) and platform (-iphonesimulator).
    While building module 'FirebaseMessaging' imported from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/Headers/Public/Firebase/Firebase.h:66:
    In file included from <module-includes>:1:
    In file included from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/Target Support Files/FirebaseMessaging/FirebaseMessaging-umbrella.h:13:
    In file included from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FirebaseMessaging.h:18:
    /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FIRMessagingExtensionHelper.h:37:38: warning: 'UNMutableNotificationContent' is only available on iOS 10.0 or newer [-Wunguarded-availability]
    - (void)populateNotificationContent:(UNMutableNotificationContent *)content
                                         ^
    In module 'UserNotifications' imported from /Users/runner/work/flutterfire/flutterfire/tests/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Public/FirebaseMessaging/FIRMessagingExtensionHelper.h:22:
    /Applications/Xcode_13.3.1.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator15.4.sdk/System/Library/Frameworks/UserNotifications.framework/Headers/UNNotificationContent.h:[97](https://github.com/firebase/flutterfire/runs/7094273749?check_suite_focus=true#step:9:98):12: note: 'UNMutableNotificationContent' has been marked as being introduced in iOS 10.0 here, but the deployment target is iOS 9.0.0
    @interface UNMutableNotificationContent : UNNotificationContent
               ^
    While building module 'FirebaseMessaging' imported from
...

Using the exclude branch for testing currently


Add Loading for Data Fetching

Describe the issue
When table is fetching data, add a loading UI to indicate it's fetching.
Acceptance Criteria

[ ] Add loading UI

SSR doesn't seem compatible with loading since it's server-side.

Look into this package: https://www.npmjs.com/package/next-progress

Documented issues here: https://github.com/vercel/next.js/issues/13910

De-prioritized b/c it may not be feasible and the time to investigate isn't currently worth it.


[$500] MacOS/Chrome - Background color is stuck on right click/long press on year in year search

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open the app
Open settings->profile->personal details->date of birth
Click on year to open year search
Right click on any unselected value and click on another value to close right click popup or long press on any value on mWeb
Hover on other messages in web and observe that background color is stuck on value used in step 4

Expected Result:
App should remove background color as soon as we hover on other value
Actual Result:
Background color is stuck on right click/long press on year in year search even on hovering on other value
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: v1.3.71-8
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/115492554/1ff17eef-05e1-4c00-8e27-ecf6595e57b7
https://github.com/Expensify/App/assets/115492554/88672770-0de8-4ae8-9c1e-46dac73ef7c5
Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant Dattaram Sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1695112322258699
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01790aaa0a663bd0f8
Upwork Job ID:<PHONE_NUMBER>281148928
Last Price Increase: 2023-09-20
Automatic offers:

bernhardoj | Contributor | 26982141
dhanashree-sawant | Reporter | 26982143

Proposal
Please re-state the problem that we are trying to solve in this issue
What is the root cause of that problem?
The hover state is not being updated correctly when right-clicking on an element. This is because the PressableWithoutFeedback component does not have an event handler for right-click events. As a result, the hover state remains stuck when right-clicking on the element.
What changes do you think we should make in order to solve the problem?
To fix the issue and make the hover state active when hovering over another element, you can add an onContextMenu event handler to the PressableWithoutFeedback component. This event handler will update the hoveredDay state to null when a right-click event occurs. and also keep tracking onMouseEnter & Leave to track the hovered state
Then on hovered, make the background change
<PressableWithoutFeedback
    key={`${index}_day-${day}`}
    disabled={isDisabled}
    onPress={() => this.onDayPressed(day)}
    onContextMenu={() => this.setState({ hoveredDay: null })}
    style={styles.calendarDayRoot}
    accessibilityLabel={day ? day.toString() : undefined}
    focusable={Boolean(day)}
    accessible={Boolean(day)}
    dataSet={{[CONST.SELECTION_SCRAPER_HIDDEN_ELEMENT]: true}}
    onMouseEnter={() => this.setState({ hoveredDay: day })}
    onMouseLeave={() => this.setState({ hoveredDay: null })}
>
    {({ hovered, pressed }) => (
        <View
            style={[
                styles.calendarDayContainer,
                isSelected ? styles.calendarDayContainerSelected : {},
                !isDisabled ? StyleUtils.getButtonBackgroundColorStyle(getButtonState(hovered || day === this.state.hoveredDay, pressed)) : {},
            ]}
        >
            <Text style={isDisabled ? styles.buttonOpacityDisabled : styles.dayText}>{day}</Text>
        </View>
    )}
</PressableWithoutFeedback>

What alternative solutions did you explore? (Optional)
Instead of using theonMouseEnter and onMouseLeave event handlers, we can use the onMouseOver event handler to update the hoveredDay state. The onMouseOver event will be triggered when the mouse pointer enters or leaves the element or any of its child elements.
<PressableWithoutFeedback
    key={`${index}_day-${day}`}
    disabled={isDisabled}
    onPress={() => this.onDayPressed(day)}
    onContextMenu={() => this.setState({ hoveredDay: null })}
    style={styles.calendarDayRoot}
    accessibilityLabel={day ? day.toString() : undefined}
    focusable={Boolean(day)}
    accessible={Boolean(day)}
    dataSet={{[CONST.SELECTION_SCRAPER_HIDDEN_ELEMENT]: true}}
    onMouseOver={() => this.setState({ hoveredDay: day })}
>
    {({ hovered, pressed }) => (
        <View
            style={[
                styles.calendarDayContainer,
                isSelected ? styles.calendarDayContainerSelected : {},
                !isDisabled ? StyleUtils.getButtonBackgroundColorStyle(getButtonState(hovered || day === this.state.hoveredDay, pressed)) : {},
            ]}
        >
            <Text style={isDisabled ? styles.buttonOpacityDisabled : styles.dayText}>{day}</Text>
        </View>
    )}
</PressableWithoutFeedback>

Hi @mallenexpensify, @thesahindia whenever you are available, can you change the reported by to my correct handle? currently I am not getting emails due to it.
Correct handle: @dhanashree-sawant

@dhanashree-sawant has reported another issue with the background colour being stuck, I think we should combine the two into one issue? @thesahindia what do you think?
https://expensify.slack.com/archives/C049HHMV9SM/p1695223040847299

They are 2 different components with different cause I guess.

@thesahindia I'd be curious for your input here as although they're different components, the behaviour is basically identical, so perhaps there is just one root cause that we can identify here.

I see we fixed it here https://github.com/Expensify/App/pull/24577
Where was it updated recently and there's also no blame? anyone has any idea

Welp thanks! That makes sense 👍
It was deploy last month, so let's handle it separately

I don't think this fixes the issue at the root, the background is not highlighted any more but the option is still focused and if you press enter, it will still select that option (which is confusing to the user because there's no indication that the option will be selected if pressing enter).

We should either remove the focus in that case, or keep the focus but also keep the highlight so the user knows what will happen if they press enter.

@dukenv0307 sorry I didn't get the concern here regarding expected behavior. The highlighted background displays the option user is currently viewing and about to select. so on pressing enter, it is expected that it will selected, no?

It also works like this in other sections of the app, so I'm fine 👍 cc @miljakljajic @mallenexpensify would like to have your opinion on this

Also fine by me

Thanks! We're good to go then 👍

Right! In that case, I think we close this issue? @miljakljajic

Also unable to reproduce, closing. Comment and/ore reopen if you disagree or if you're able to reproduce


NO-TICKET: improve Key error reporting and tests

This PR adjusts the way in which Key enums are parsed from their formatted string formats.  The objective is to give more meaningful feedback to users when a parsing error occurs.
Previously we'd try to parse to each variant, and once all attempts had failed we'd report InvalidPrefix.  This was misleading in the case where the user provided a valid prefix, but the Key still failed parsing.  For example, we saw multiple cases where the user mistakenly supplied a public key instead of an account hash.  This would result in a string like account-hash-<66 hex chars> yielding an InvalidPrefix error, when in fact the prefix was correct, but the body was incorrect.
Now parsing will be attempted based on the supplied prefix, and will only fall through to the UnknownPrefix error if the prefix doesn't match one of the valid prefixes.  The example mentioned above now yields an error stating account-key from string error: address portion is wrong length: could not convert slice to array.
This PR also improves the unit test coverage of Key since some tests were not covering newer Key variants.

bors merge


User should be able to send a video chat link for the patient from the admin panel

For a confirmed order there should be a mechanism by which the user can send a video chat link to the patient

Enhancement added


Document Package Source Mapping error NU1110

I'm adding a NU1110 in https://github.com/NuGet/NuGet.Client/pull/5468.

I don't understand the warnings. If you click the preview link, the 3 links mentioned all work. I've looked at this multiple times and it appears correct to me?

Apparently, validation fails if missing .md even though the URL actually works in practice. If you try the preview, the links work.
🤷♂

If you edit the markdown documents in VSCode with the markdownlnt extension, then it'll give you intellisense when editing links to other markdown files, even intellisense for #anchors when/if you use them.

If you edit the markdown documents in VSCode with the markdownlint extension, then it'll give you intellisense when editing links to other markdown files, even intellisense for #anchors when/if you use them.

I actually did get intellisense without having that extension in VSCode, and in fact it sees the files in a box that pops up. Additionally, as mentioned, the preview links above work for me.
Going to try markdownlint now and see if it somehow makes a difference.

This time, I double-clicked on the suggestion and low-and-behold, the difference was capitalization. Apparently, Friday Brain had me just seeing that the suggestion was finding the file, but I didn't select the intellisense suggestion 🤦♂. Thanks for your patience!


Add external policy mode

Closes: https://github.com/mercurius-js/auth/issues/18
TODO:

[ ] Documentation
[ ] Types
[ ] Type tests
[ ] Re-run benchmarks
[ ] Examples

Awesome! I'll sort out the final bits :)


move to new blackduck synopsys-action

What this PR does / why we need it:
update Black Duck workflow to use new synopsys-action
Release note:

NONE

/lgtm
/approve


Tenant provisioning did not detect exceeded compute quota

During application setup, choosing a compute size that will cause account limits for compute (i.e. number of CPUs) to be exceeded was not detected, causing a tenant provisioning failure.
Reproduction Steps

Choose x-large compute size and-or increase max instances.
What did you expect to happen?
Error or warning message would appear to prevent tenant provisioning until condition was satisfied.

Provision a tenant
What actually happened?

Expected a warning or error during application config - error not seen until CF stack failed during ECSAutoScaling substack execution.
Environment

AWS Region  : us-west-2
**AWS SaaS Boost Version :v0 - dev
**Workload OS  (Linux or Windows) :Windows ASP.NET Framework 4.7.2

Other

This is :bug: Bug Report

Windows workloads provision a EC2 and the Quota service needs to be updated to check for limits of EC2 vCPUs.


syncMobs() missing?

I'm confused. I install MV-Core b452 on a fresh 1696 CB, then run mvm set monsters false world from console, and get:
17:52:51 [INFO] java.lang.NoSuchMethodException: com.onarandombox.MultiverseCore.MVWorld.syncMobs()

...huh? There's no trace - just this line - and MV dumps out 'monsters' must either be: true or false afterward.

@FernFerret added "active" config-properties" in 53c801bb81ed6a34b1880b087ad143b3d75ef7ba. A previously set method is executed with reflection when they're changed. "animals" and "monsters" are configured to call "syncMobs()". But that method does not exist. Apparently, @FernFerret forgot to add it.

I thought it was something like that too, and then this.

That's strange...
Maybe because the method is private?

Yep, I just looked it up and it's true: "getMethod()" only works with public methods.
Now we can either use "getDeclaredMethod()" instead or make "syncMobs()" public (...and write javadoc for it!).

Closed in b006a458dbcd31c54ae5d04c65748c21432e66be

I'm reopening this issue because DifficultyConfigProperty is broken, too. Apparently all difficulty config-properties are using setDifficulty() as method. But that method doesn't exist in MVWorld.


"Runtime Error"

When I finish a game, whether I end up losing or winning the round, my screen freezes and I get an error from Microsoft Visual C++, and I can't find a way to fix this. (It happens with versions after 2.1)


Execute Phase 1 of Data Dashboard to Daily Data Comms Plan

Problem Statement
The Comms plan and transition plan has been defined. We need to execute the first step of the plan.
What you need to know

Comms Plan and Timeline
Adding Data Dashboard banner 1 (yellow banner alert) to top of Data Dashboard page is happening in a separate engineering ticket #13759

Acceptance Criteria

[ ] Send email to Data Dashboard users 1 week before transition
[ ] Chris sends slack message out to internal users

Post made: https://nava.slack.com/archives/C024MGSJZ38/p1712329295820579

Email sent at noon ET 4/5


fix NDTreeTraining Build Tree.

NDTreeTraining build wrong tree

not obey min count option, as long as left or right < min count, it stop
it may not create bucket evenly if median happens to be the min element.

@deerzq @christhetree @saurfang

LGTM

@deerzq @saurfang Thanks for review! all updated!

LGTM


#7479 Trace connection open and close in RelationalConnection

Fixes #7479

cc @avanderhoorn

This looks great! I'm wondering if we can include some of the same info we do with the commands (i.e. InstanceId, Timestamp & Duration)? Also on the command we have an exception version of the close message, do we need that here for connection?
Lastly is there anyway to deterministically way which commands where a part of which connection? Like I know that the commands have a connection property, but if I was trying to save a connectionId as part of the data that I collect command message, how would you recommend that we do that and who is responsible for tracking that. Specifically, I could try and derive that Id from GetHash on the connection object, but I'm not sure if that would be what we would want people to be doing or if there is any gotchas in using that value for that sort of correlation and we should provide a different id. Thoughts?

I think that adding a ConnectionId (guid) to RelationalConnection would be great addition. Than it will be needed to be passed to the other methods like the commands and also I want to add TransactionCommitted and TransactionRolledback which I added in a new commit.

@avanderhoorn Added connection identifier. This is really great addition!

FYI - I amended the "#7479 Trace connection open and close in RelationalConnection" commit a few times until #07dce52.

If anything else I'll add is the latest commit which handle errors. This is one unified way to handle all exceptions.

Also did you have a chance to look at (note this could apply to the transaction as well as the connection):

This looks great! I'm wondering if we can include some of the same info we do with the commands (i.e. InstanceId, Timestamp & Duration)?

Hi, I included InstanceId, Timestamp & Duration for connection.
InstanceId is used to corolate between ConnectionOpening to ConnectionOpened or ConnectionError.
As as now for transaction I didn't add BeforeTransactionCommit, but just TransactionCommited so there is not need for InstanceId there.

I fixed conflicts and rebased.

@anpete just wondering about that last question I had (https://github.com/aspnet/EntityFramework/pull/7483#discussion_r98745178)? Any reason for the early merge?

@avanderhoorn We are making a push to get our PR count down and I thought this one was good to go. Sorry if I jumped the gun 😄 Happy to address remaining concerns on the new PR.

No worries :) just making sure that I hadn't missed anything.


chore(main): release 0.0.13

:robot: I have created a release beep boop
0.0.13 (2024-03-11)
Other

fix broken build link in README (#147) (c6e6ae7)
upgrade to validator v0.0.36 (#153) (a2d6d9b)
deps: update kubernetes packages to v0.29.2 (#140) (6a0d006)
deps: update module github.com/onsi/ginkgo/v2 to v2.16.0 (#149) (45db49d)
deps: update module sigs.k8s.io/controller-runtime to v0.17.1 (#119) (ace6047)
deps: update module sigs.k8s.io/controller-runtime to v0.17.2 (#143) (18bc184)
deps: update actions/upload-artifact digest to 5d5d22a (#136) (10d9b75)
deps: update anchore/sbom-action action to v0.15.9 (#150) (224d8b0)
deps: update azure/setup-helm action to v4 (#148) (ad470b1)
deps: update codecov/codecov-action digest to 54bcd87 (#145) (1f0d1dc)
deps: update docker/build-push-action digest to af5a7ed (#151) (2b1091e)
deps: update docker/setup-buildx-action digest to 0d103c3 (#146) (b274a04)
deps: update helm/kind-action action to v1.9.0 (#139) (8a94dc6)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/spectrocloud-labs/validator-plugin-network/releases/tag/v0.0.13 :sunflower:


Low Throughput iperf on ESP32-C3-DevKitC-02 (IDFGH-8572)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
We are trying to run a stress test to a router. To do so, we need to simulate multiple nodes that are connecting through WiFi. These nodes are ESP32 running iperf. Connected to the router using ethernet there is a laptop running Linux. In the laptop we run the iperf server  and in the ESP32-C3 nodes we run the iperf client from the esp-idf example.
Our problem is: when using a single ESP32 we can achieve speeds of up to 40 Mbps. But if we try to add more nodes, i.e., running 2, 3, 4 ESP32s in parallel, there seems to be a cap in our maximum speed, and in total we never achieve more than 40 Mbps. We can understand that a single ESP32 may not be able to get a higher throughput, but the combined throughput should get higher, given we're not close to the limit of Wi-Fi 4. What's preventing the combined throughput to grow? Is there anyway to fix it or improve it?
Thanks

Hi @SelcRGIO
There are some related issues maybe you need to check

Test environment: in the shield box or in the open air environment?
The Router's info, such as bandwith(ht20 or ht40), brand and types, any other special configs etc.
ESP-IDF commit and ESP32 or ESP32C3 modules?
Test method: only test UDP both TX and RX, then provide the new test result.

Hi @MaxwellAlan

The environment is open air, but we have conducted test in different locations (checking with a WiFi analyzer that there wasn't to many networks/traffic interfering) with more or less the same results.
The router info is: RT-AX68U ASUS (configured only ht20)
Using esp-idf-v4.4.2 on a ESP32-C3-DevKitC-02 module
See attachments of results with a single device and 4 devices in parallel

Thanks for reporting, feel free to reopen.


Cur outposts rds

Issue #, if available:
Description of changes: CUR Query for RDS Outposts and minor update to EC2 Outposts query
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Modified annotations.


Remove jcenter repository due to shutdown

This PR removes the use of jcenter as a dependency source in favor of mavenCentral. A minor bump to volley version 1.2.1 was required as a result of this change.

thank you for taking care of this!

thank ya!


Migrate to android x

Some of the packages use old android support packages.
Android wants everyone to migrate to androidx packages. Can we bump these imports?

// MultiImageChooserActivity.java

import android.support.v7.app.ActionBar;
import android.support.v7.app.AppCompatActivity;

// ImagePicker.java

import android.support.v4.app.ActivityCompat;
import android.support.v4.content.ContextCompat;

Any progress on this ? We have almost 2 weeks left if I'm not wrong. Otherwise, we'll have to ditch this plugin.

Any progress on this ? We have almost 2 weeks left if I'm not wrong. Otherwise, we'll have to ditch this plugin.

@ugurcagridogan
If you can you can run jetifier to update your packages. I found this out way to late as well.
If you can run the npx jetifier command in your build pipeline somewhere you'll be safe in your builds.
good luck champ!

Any progress on this ? We have almost 2 weeks left if I'm not wrong. Otherwise, we'll have to ditch this plugin.

@ugurcagridogan
If you can you can run jetifier to update your packages. I found this out way to late as well.
If you can run the npx jetifier command in your build pipeline somewhere you'll be safe in your builds.
good luck champ!

Somehow I managed to build it successfully after struggling with gradle and capacitor versions. Thank you.

@ugurcagridogan Are you building it on Cordova? I am still struggling with it....maybe it would be easier to import the changes for the next version update for the plugin.


Instead of writing tasks inside the apply block create extra classes for tasks

You currently define all tasks specifics inside the plugin class.
It would be better to extract the task as classes and extends the DefaultTask. Something like this
Inside this you can use a temporary folder generated with Gradle internal mechanic temporaryDir which is given by task mechanics: https://docs.gradle.org/current/dsl/org.gradle.api.Task.html#org.gradle.api.Task:temporaryDir

@Mazorius what you are proposing looks better, but I did not succeed to register a task in an external file. I tried many things but I can not register un build.gradle a task from another file and I did not succeed to run it. Do you have any working example on how to register a Task extending DefaultTask ?

Will have a look and create a PR at the weekend.

@Mazorius I finally found the way to make it :
       project.tasks.register(TASK_HIDE_SECRET, HideSecretTask::class.java)
I might do it later in a PR.


As a data owner/manager I want the system to create a DOI for my dataset as I upload so that I can track subsequent uses of my data

SYSTEM created DOI
BIG TICKET as DOIing methods vary, this is a workshop in itself

ICES is developing a new accession system (Accesion Information Management System - AIMS), which will roll-out later in the year, and will allow the minting of DOI's on upload to system. So it will be in the ICES bag; however a discussion is still needed on how the user would trigger this.

ICES is developing a new accession system (Accesion Information Management System - AIMS), which will roll-out later in the year, and will allow the minting of DOI's on upload to system. So it will be in the ICES bag; however a discussion is still needed on how the user would trigger this.

@neil-ices-dk should this (and #175) have an 'in the ICES bag' label yet?

@neil-ices-dk should this (and #175) have an 'in the ICES bag' label yet?

i think we're at the 'two in the bush' part of the old saying about a 'bird in hand'; so would prefer to be conservative and not label it as in the bag, although it will be 🐦

Notes from Steering Group Jan2020
•	Allows minting of DOIs on upload to the system.
•	Likely that each dataset would need to have a DOI and would be created by the systems each time a data owner uploaded a dataset.
•	Providers can opt out of (or opt in to) a DOI.
•	Providers can also provide existing DOIs if they exist.
•	Need to consider what happens when data are overwritten - existing DOI would no longer link to the original dataset. JR (ICES) was confident that the working group developing this will have considered how to avoid “overwriting”
•	ICES will deliver the ‘in perpetuity’ access to the version of the data that is DOI’ed and also the landing page that is required.
@neil-ices-dk is this enough info or do we still need a discussion around how users trigger the process? I presume a button/option on upload (submission of new/updated dataset) to assign a new one, which then triggers any additional info/questions needed?

thanks @LynnHeeley i think the above is enough for the time being; we perhaps need to clarify what where the overwriting occurs in the above - assume we're talking about the version at ICES.

Further work needed on this task?


"Access key added" doesn't describe which key is added

When I view transaction which added / removed key – it is interesting which key was removed/added and with which permissions.
It is currently not visible https://explorer.near.org/transactions/DmAncJcrxCt4mPFmbmvdc8E3RfQbhTdSisoJ5Mmyzaok

@icerove Let's update our template for detailed action view to include the public key and information about permissions (full access or function-call only with the method name(s)) and nonce


Added PR template

Added a pull request template markdown file based on the required template by you. Also added a checklist section to help a contributer dev to check all the checks written so as to avoid unnecessary faulty PRs. :v:
Fixes #28

Great 👍


JSON render duplicate bug

JSON render duplicate bug

env

macOS 10.15.17
Version 87.0.4280.88 (Official Build) (x86_64)

multi plugins conflict bug

Sorry, for that!

multi plugins conflict bug

Sorry, for that!


Add 'Choose from an existing component' option to CC part of forms

Similar to what we currently have now for the BP part of the Default form, i.e. 'Choose From an Existing Process', we would like to have an option to 'Choose From an Existing Component' option for the CC part of each form.
This will allow curators to annotate to the same instance of a component just like they do for biological process.

@vanaukenk see https://github.com/geneontology/simple-annoton-editor/issues/83 for comments


chore(main): release 0.1.3

:robot: I have created a release beep boop
0.1.3 (2023-10-04)
Bug Fixes

casing (b4bea04)
error message component (e13c62b)
event inline record url (1c5f43d)
invalid workflow file (0ce986d)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/crea-orkest/crea-public/releases/tag/v0.1.3 :sunflower:


Can I put our company's logo as one of maintainer of this plugin?

I will be happy to see our logo in footer of README file, like this:
Maintained by
 &
Because we use this plugin in production for all of our services, and we love to improve it to provide better exception information and support all of Sentry features on time. We want to be one of a company behind this plugin who use it in production and release bugfixes.
If it's okay with you, I glad to see us in the footer.
By the way, I already create PR for this: https://github.com/agorapulse/grails-raven/pull/24

Close this issue, due PR already merged.


[WIP] segregate block and blocklet cache

segregate block and blocklet cache

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[ ] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6718/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5545/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5567/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5558/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6728/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5568/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5580/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6738/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5608/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5598/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6776/

@ravipesala ..handled review comments. Kindly review and merge

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6796/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5625/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/6846/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/5642/

LGTM


Can it deploy via jumpstations?

I've been using capistrano for a while but am looking to cut down on external dependencies, so looking into a PHP solution. Unfortunately so far most can't cope with a jumpstation or so called bastion server (as in you cannot SSH directly to the target server because it is in a DMZ, you have to go trough another). SSH can handle this fine via a ProxyCommand (and Capistrano has no issues with it either (Net::SSH::Proxy::Command). PHP solutions however, cannot it seems.

I'm afraid I'm not familiar with jumpstations at all, so I guess it depends on whether the SSH library we use underneath supports it https://github.com/phpseclib/phpseclib

https://github.com/phpseclib/phpseclib/issues/461
Guess I'll be sticking with Capistrano for now. Thanks for the reply.


Mouse selection will not highlight in terminal

Whenever I try to select text to copy using the mouse it will not highlight the selection. You can still select the content and copy/paste. There is no indication of what has been selected.
OSX 10.11.6
Atom 1.11.2
Platformio-ide-terminal 2.2.1

I have a similar issue where I defined a selection background-color and the colour coded in styles.less is not the same colour rendered in the terminal.

I have the same issue.  Doesn't matter the theme I use, I cannot highlight anything in the terminal, especially for copy/pasting.

+1

Has anyone found a solution for this?

@liamdkane
I ended up overwriting the config file for solarized-dark.less with my own color scheme since no one really resolved this.
If you go to Settings -> Packages -> patformio-ide-terminal (click on package) and below see "View Code"
It will open another project and I change the file under:
platformio-ide-terminal

styles

themes
solarized-dark.less

and I paste in this color scheme
.solarized-dark {
  background-color: #1d1f21;
  color: #708284;

  ::selection {
    background-color: #8f7799;
  }

  .terminal-cursor {
    background-color: #819090;
  }
}

This fix needs to be done after every upgrade to that package though.
These are some custom color schemes I came up with after experimenting, but they are not solarized colors and i'm not sure what they should be.

Also I did some more messing around, and found background-color: #252931; is a close match to the editor window and makes the terminal feel alot like the atom dark theme which is what I was attempting to accomplish with my settings.

Also tried to fix the actual solarized colors and this is as close as I got to a "solarized-dark" solution:
.solarized-dark {
  background-color: #042029;
  color: #708284;

  ::selection {
    background-color: #839496;
  }

  .terminal-cursor {
    background-color: #819090;
  }
}

Neither had an effect.  And I tried various different themes.

I ended up fixing both the solarized-dark and one-dark themes as per the merged PR associated with this ticket. I'm going to close this ticket.

@alsGitHub270 whats not taking effect. If you are referring to manually modifying the themes, you need to modify the theme you selected. You also need to save and quit all running atom instances so the changes take effect on next start.

rm -r ~/.atom/packages/nuclide/pkg/nuclide-terminal  then restart atom will fix the problem if you have nuclide installed

In my case it was the ink package. I disabled it and selection in the terminal worked as expected.

Had the same issue, disabling ink worked for me (Debian 9 / Atom 1.2.3 / Ink 0.8.2 / Plaformio 2.8.0 for the records)

I don't have the nuclide-terminal I have atom-ide-ui installed. And my selection highlight wasn't working, I have platformio-atom-ide-terminal installed
My solution was:
I went the atom-ide-ui/modules/atom-ide-ui/pkg/ and I deleted the atom-ide-terminal folder
then restarted Atom
Worked for me!

just disable terminal feature under atom-ide-ui


EEPROM too small -> no update possible?

Hi,
I tried to use my DFK 72AUC02 with an UBUNTU distribution, but the update
prompted that there is an issue considering the EEPROM, which is too low to get the firmware (16..kB vs. 19...).
How can I manage that?
Thanks

Unfortunately you did not write, which firmware file you want to write in the camera. Thus I recommend to use dmk72uc02_129.euvc.
Stefan

Hi Stefan,
I tried the dfk72uc02_3012.euvc, which is mentioned in the WIKI.

The update with dfk72uc02_129.euvc worked (the Windows version?), but the dmesg doesn't show
uvcvideo: Found UVC 1.00 device

I tried your recommendation, but the dmesg shows
[27658.306155] usb 1-3: new high-speed USB device number 5 using ehci-pci
[27658.707499] usb 1-3: New USB device found, idVendor=199e, idProduct=8207
[27658.707512] usb 1-3: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[27658.707519] usb 1-3: Product: DFK 72AUC02
[27658.707526] usb 1-3: Manufacturer: The Imaging Source Europe GmbH
[27658.707531] usb 1-3: SerialNumber: 06110418
but not uvcvideo: Found UVC 1.00 device
as mentioned by TIS-Edgar
TIS-Edgar commented on 7 Sep 2015
Hi,
Let's start with getting your devices working properly.
What does the command 'dmesg' say when you connect a camera?
Ideally it would be something like:
[ 3634.269253] usb 3-14: new high-speed USB device number 5 using xhci_hcd
[ 3635.996841] usb 3-14: config index 0 descriptor too short (expected 392, got 308)
[ 3635.997125] usb 3-14: New USB device found, idVendor=199e, idProduct=8302
[ 3635.997127] usb 3-14: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[ 3635.997128] usb 3-14: Product: DMK 22BUC03
[ 3635.997129] usb 3-14: Manufacturer: The Imaging Source Europe GmbH
[ 3635.997130] usb 3-14: SerialNumber: 21110463
[ 3635.997497] uvcvideo: Found UVC 1.00 device DMK 22BUC03 (199e:8302)
[ 3636.932874] input: DMK 22BUC03 as /devices/pci0000:00/0000:00:14.0/usb3/3-14/3-14:1.0/input/input18

My fault sorry. Use "dmk72uc02_162_uvc.euvc" That is the file for your camera. It makes a mono, but UVC compatible camera. Debayering should be done in software.
Stefan

Thank you
that worked for me
Andreas


feat: add existEvent function

ee.listenerCount() can be used for this.
let n = ee.listenerCount('event');

if (!n) {
  // There are no listeners for the `'event'` event.
} else {
  // There are `n` listeners for the `'event'` event.
}

I'm 👎  on adding a new method.

I'm closing this. Thank you anyway.

Sorry for the late reply, I submitted this pr because I felt that the listenerCount method did some extra steps and I thought it might be better to provide a way to handle it specifically.


Support for python 3 ?

Hi,
would this docker image work if I installed and started using python 3 ?

Hi,
What do you mean about installing and starting using python 3? I ran a SQL Server 2017 container and checked the python3 version. It shows
root@c29764794d4c:/# python3 --version
Python 3.5.2

@forkazmoden sorry for delay - have overlooked your message.
Yes, I am writing SQL Server python client application and would like to use Python 3 in Python Development Environment for SQL Server?. Would that work ?

You are free to create your own docker image with Python 3 for now. For now, I am marking this as an ask that we will evalaute in the future.

I find the example provided for python (https://github.com/microsoft/mssql-docker/blob/master/oss-drivers/pyodbc/Dockerfile) is very bloated and unnecessary. A much simpler one based on the official python:3 image would be better.
# Use specific version that has microsoft odbc drivers available
FROM python:3.8.4-buster

# adding custom MS repository
RUN curl https://packages.microsoft.com/keys/microsoft.asc | apt-key add -
# Buster = 10. And python image is built on buster.
RUN curl https://packages.microsoft.com/config/debian/10/prod.list > /etc/apt/sources.list.d/mssql-release.list

# install SQL Server drivers
RUN apt-get update && ACCEPT_EULA=Y apt-get install -y msodbcsql17 unixodbc-dev

# We copy this file first to leverage docker cache
COPY ./requirements.txt /app/requirements.txt

WORKDIR /app

RUN pip --trusted-host pypi.org --trusted-host files.pythonhosted.org install -r requirements.txt

COPY . /app

ENV PYTHONUNBUFFERED 1

CMD [ "python", "main.py" ]


Injecting ClaimsPrincipal in service layer

Is there a clean way to get ClaimPrincipal or IIdentity from DI? So it can be used in service layers.
This was ugly, but possible with the "good old" HttpContext.Current.User :smile:

You can use the IHttpContextAccessor in your services.

Ye, I guess that's doable, thx.


Refactor signing keys, Publisher Id into classes

This changes the PublisherId type into a js class instead of just a flow object literal type, and adds some handy sign and verify methods to it, as well as static load and save to persist to disk.  It also wraps the callback-based libp2p-crypto key interfaces with PublicSigningKey and PrivateSigningKey classes that use a Promise interface instead.
Also adds a test for loading a publisher id from concat and using it to sign and verify a message.

hooray


Print labels in code stepper

Example with absolute labels:

Example with displacement labels:

The _nop5 example is clearly contrived, I just needed to make something to test if the displacement labels were working lol

siiiiiiiiiick thanks!


Does client ID really need to be input manually?

If chatterino's client id can be changed then ignore and close this, but is there a reason that LogInWithCredentials (and more specifically AdvancedLoginWidget) require a specific field for client ID? Can't it just be 7ue61iz46fz11y3cugd0l3tawb4taal, or at least default to it?

Yes but there's a reason that the advanced tab is there

I don't think the client ID should be pre-filled in with a default value. I could possibly concede with a "copy c2 client id" button but that'd be a separate issue.


wip/6.0 Fix final entity class creating ProxyFactory issue

https://trello.com/c/CgVHHg3A/85-fix-problem-building-model-for-final-classes
The root cause is the following code snippet from EntityMetamodel:

Its usage was dropped during new code logic refactoring.

@sebersole I am not confident about the code change, though I am sure about the root cause. Feel free to take over and modify it to your content. I lack the big picture to go about the most effective refactoring.


Question on: MiSeq SOP

Hi, I ran the SOP on targeted V4 region of the 16S rRNA sequences. I used the latest mothur version, Silva Database v132, and RDP classifier version 18. I aligned the silva Database to the V4 region without the primers. After performing the Phylotype based analysis and opening the shared and taxonomy files, a lot of the samples show quantity 0 in archaea and bacteria, which I don't expect.
So I am wondering if I misaligned the database, or if it's a result of bad classification.
For some reason mothur didn't save a logfile, but I have the results saved for reference.
I highly appreciate the help!

Hi there - could you possibly repost your question at forum.mothur.org? If you could clarify whether you are looking at the kingdom level or genus level that would be helpful. If you've followed the SOP, there won't be any Archaea since those would have been removed in get.linage


Add missing Git in alpine version

With the gitlab-runner:alpine version, this error is thrown when a build is runs.
gitlab-ci-multi-runner 1.0.4 (014aa8c)
Using Shell executor...
Running on 084238b313b4...
Cloning repository...
bash: line 34: git: command not found

ERROR: Build failed with: exit status 1

Please create the MR for this project: https://gitlab.com/gitlab-org/gitlab-ci-multi-runner  :)


Refactor Mem2Mem driver

Thank you for your contribution!
We appreciate the time and effort you've put into this pull request.
To help us review it efficiently, please ensure you've gone through the following checklist:
Submission Checklist 📝

[x] I have updated existing examples or added new ones (if applicable).
[x] I have used cargo xtask fmt-packages command to ensure that all changed code is formatted correctly.
[x] My changes were added to the CHANGELOG.md in the proper section.
[x] I have added necessary changes to user code to the Migration Guide.
[x] My changes are in accordance to the esp-rs API guidelines

Extra:

[x] I have read the CONTRIBUTING.md guide and followed its instructions.

Pull Request Details 📖
Description
Part of #2269 .
Two big changes here:

I've split the Mem2Mem driver into an RX half and a TX half. Each half could be sent to a different task.
I've added support for DmaTxBuffer/DmaRxBuffer.

A nice side effect of this is that the driver can now be used as a queue/channel to communicate between tasks. (Dunno if anyone would do this in practice)
It also allows us to easily HIL test DmaTxBuffer/DmaRxBuffer implementations.
Testing
Ran HIL tests and examples

The "I have to fill a buffer so that I can avoid using the CPU to copy, then copy out of that buffer" seems to be missing the idea of why someone would use mem2mem in the first place. This whole API should be, from a user's point of view, a single memcpy-like function that takes a slice, and puts it in a different, mutable slice. Whether that, then, returns a handle with a .wait() or a future that can be awaited, doesn't matter.
If you need two buffers to do mem2mem, you might as well fill one, and swap pointers without the need for DMA.

If you need two buffers to do mem2mem, you might as well fill one, and swap pointers without the need for DMA.

Wasn't the existing API doing this already? I'm not sure I understand what you mean.

This whole API should be, from a user's point of view, a single memcpy-like function that takes a slice, and puts it in a different, mutable slice.

I don't agree that this whole API should be just that, that would be too opinionated of an API. Though, if PSRAM weren't in the picture I would've agreed.
In my project I use DMA memcpy to workaround PSRAM bandwidth limitations (basically an async version of the "bounce buffers" in esp-idf).
I hear what you're saying though, so I can add a (secretly unsafe, like the existing API) wrapper on top of this API that takes two slices, for those that want to do the simple thing.

Unfortunately DmaRxBuf doesn't support PSRAM yet so a wrapper won't be trivial. I'll come back to this later.


Export using use_active_scene=True fails with keyword unrecognized

Describe the bug
Trying to export the active scene only as a glb using the following command
bpy.ops.export_scene.gltf(
            filepath=finalPath,
            check_existing=False,
            export_format='GLB',
            export_cameras=True,
            export_lights=True,
            use_active_scene=True,

To Reproduce
Steps to reproduce the behavior:

Create a new py script
run the command above

optionally create a blend file with two scenes
Expected behavior
glb gets exported and contains one scene
Version

OS: win10
Blender Version 3.1.2

Additional context
Traceback (most recent call last):
  File "C:\Users\marce\AppData\Roaming\Blender Foundation\Blender\3.1\scripts\addons\blender\__init__.py", line 49, in saved
    bpy.ops.scene.export("INVOKE_DEFAULT")
  File "c:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\modules\bpy\ops.py", line 130, in __call__
    ret = _op_call(self.idname_py(), C_dict, kw, C_exec, C_undo)
RuntimeError: Error: Python: Traceback (most recent call last):
  File "C:\Users\marce\AppData\Roaming\Blender Foundation\Blender\3.1\scripts\addons\blender\operators_components.py", line 44, in execute
    exportScene(self, fileName="scene.glb")
  File "C:\Users\marce\AppData\Roaming\Blender Foundation\Blender\3.1\scripts\addons\blender\blender_export.py", line 62, in exportScene
    bpy.ops.export_scene.gltf(
  File "c:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\modules\bpy\ops.py", line 132, in __call__
    ret = _op_call(self.idname_py(), None, kw)
TypeError: Converting py args to operator properties: : keyword "use_active_scene" unrecognized

location: c:\Program Files\Blender Foundation\Blender 3.1\3.1\scripts\modules\bpy\ops.py:130

i have seen that the bool is declared here: https://github.com/KhronosGroup/glTF-Blender-IO/blob/9be538a53c374b50e109022965886f49d1eb4806/addons/io_scene_gltf2/init.py#L359
exporting use_active_collection kind of works but then I get a glb file with the two scenes which is not what I want here unfortunately
also noteable is that the settings is not in the export window so maybe the blender version is too old?

so maybe the blender version is too old

Yes, you are using 3.1. If you look at that file in blender-v3.1-release you see use_active_scene does not exist.

Hello,
Yes, as scurest said, this option was not available on 3.1.
Please use a more recent version!

Thank you will do

Works perfectly on 3.3.1 - thanks again


Cannot resolve package main

I get this error when trying to start the dev server with
hq

Console error log:
(c) hqjs @ 0.0.21
internal/modules/esm/default_resolve.js:96
  let url = moduleWrapResolve(specifier, parentURL);
            ^

Error: Cannot resolve package main '[object Object]'<EMAIL_ADDRESS>imported from<EMAIL_ADDRESS>    at Loader.resolve [as _resolve] (internal/modules/esm/default_resolve.js:96:13)
    at Loader.resolve (internal/modules/esm/loader.js:73:33)
    at Loader.getModuleJob (internal/modules/esm/loader.js:147:40)
    at ModuleWrap.<anonymous> (internal/modules/esm/module_job.js:41:40)
    at link (internal/modules/esm/module_job.js:40:36) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Can you please provide your nodejs version and operation system name?

Yes of course:
Node v13.3.0
OS X 10.15.5 (19F101)

I can reproduce, seems like some problem with module loader in that specific node version.
Please try to use different nodejs version. I've check it works with 12.16.1, 13.10.1, 14.0.0

13.10.1 works thanks!

 You can probably try different 13.x.x, I tried random versions that I have installed in my system. It just that specific version (and might be some others as well) that has this problem with the loader. I'll try to investigate anyway, but chances for simple solution are low and effort might not worth to spend time on the fix.

Totally agree! Thanks so much for the fast resolution.


correct execution of some tests on OSX machine

(CR/LF OS depedent)

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] New feature or enhancement
[ ] UI change (please include screenshot!)
[ ] Code style update (formatting, renaming)
[X] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Internationalization and localization
[ ] Other (please describe):

What is the current behavior?
modified some tests to work on non-windows machines, comparing strings with new lines.
Issue Number: N/A
What is the new behavior?
Changed the newline's behavior based on the operating system
WIN \r\n  OTHER  \n

Other information
ON macOs I still have 75 errors, you can confirm that unit tests are having problems on Mac ?
(thank you)
Quality check
Before creating this PR:

[ ] Did you follow the code style guideline as described in CONTRIBUTING.md
[X] Did you build the app and test your changes?
[ ] Did you check for accessibility? On Windows, you can use Accessibility Insights for this.
[ ] Did you verify that the change work in Release build configuration
[ ] Did you verify that all unit tests pass
[ ] If necessary and if possible, did you verify your changes on:

[ ] Windows
[X] macOS (DevToys 2.0)
[ ] Linux (DevToys 2.0)

Hi,
Thanks for this contribution. I'm sorry but I already fixed these tests.
Thanks for your understanding.

Hi, no problem. I'll try to do something else, and check your changes.
Thank you
A


pyproject.toml missing from Wiki

The wiki page on configuration doesn't list pyproject.toml, which can also be used for isort configuration. Can the Wiki be updated to include it please?
Thanks!

Hi,
The wiki has write access for all registrated users.
I bet the maintainer would appriciate any contribution to the project. 😊

I would add it, but where does it go in the hierarchy? (Or can you point me to the code that handles said hierarchy?)
From the (current) wiki:

Settings manually passed into the Python SortImports class.
Settings manually passed into the command line utility.
Settings placed in a setup.cfg file within the project's directory
Settings placed in a .isort.cfg file within the project's directory.
Settings placed in a .isort.cfg file within the users home directory.
Settings placed in a .editorconfig file within the project's directory.
Settings placed in a .editorconfig file within the users home directory.

I belive that this can be of use.  Don't quote me on it though. 😉

This is now documented on the new isort website:
https://timothycrosley.github.io/isort/docs/configuration/config_files/
Thanks for reporting!


Automated cherry pick of #1068: fix: baremetal MegaRaid mul adapter parse error

Cherry pick of #1068 on release/2.10.0.
#1068: fix: baremetal MegaRaid mul adapter parse error

/lgtm
/approve

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.10.0@a8de9f5). Click here to learn what that means.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             release/2.10.0   #1070   +/-   ##
================================================
  Coverage                  ?    7.9%
================================================
  Files                     ?     356
  Lines                     ?   56439
  Branches                  ?       0
================================================
  Hits                      ?    4464
  Misses                    ?   51580
  Partials                  ?     395

Flag
Coverage Δ

#aFlag
7.9% <ø> (?)

Continue to review full report at Codecov.

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


Strange route with publicPath config in 5.0.0-rc.1

Version
5.0.0-rc.1
Reproduction link
github.com
Environment info
Vue 2
 "dependencies": {
    "core-js": "^3.8.3",
    "vue": "^2.6.14",
    "vue-router": "^3.5.1",
    "vuex": "^3.6.2"
  },
  "devDependencies": {
    "@typescript-eslint/eslint-plugin": "^5.4.0",
    "@typescript-eslint/parser": "^5.4.0",
    "@vue/cli-plugin-babel": "~5.0.0-rc.1",
    "@vue/cli-plugin-eslint": "~5.0.0-rc.1",
    "@vue/cli-plugin-router": "~5.0.0-rc.1",
    "@vue/cli-plugin-typescript": "~5.0.0-rc.1",
    "@vue/cli-plugin-vuex": "~5.0.0-rc.1",
    "@vue/cli-service": "~5.0.0-rc.1",
    "@vue/eslint-config-typescript": "^9.1.0",
    "eslint": "^7.32.0",
    "eslint-config-prettier": "^8.3.0",
    "eslint-plugin-prettier": "^4.0.0",
    "eslint-plugin-vue": "^8.0.3",
    "lint-staged": "^11.1.2",
    "prettier": "^2.4.1",
    "sass": "^1.32.7",
    "sass-loader": "^12.0.0",
    "typescript": "~4.1.5",
    "vue-template-compiler": "^2.6.14"
  }

Vue 3
"dependencies": {
    "core-js": "^3.8.3",
    "vue": "^3.2.13",
    "vue-router": "^4.0.3",
    "vuex": "^4.0.0"
  },
  "devDependencies": {
    "@typescript-eslint/eslint-plugin": "^5.4.0",
    "@typescript-eslint/parser": "^5.4.0",
    "@vue/cli-plugin-babel": "~5.0.0-rc.1",
    "@vue/cli-plugin-eslint": "~5.0.0-rc.1",
    "@vue/cli-plugin-router": "~5.0.0-rc.1",
    "@vue/cli-plugin-typescript": "~5.0.0-rc.1",
    "@vue/cli-plugin-vuex": "~5.0.0-rc.1",
    "@vue/cli-service": "~5.0.0-rc.1",
    "@vue/eslint-config-typescript": "^9.1.0",
    "eslint": "^7.32.0",
    "eslint-config-prettier": "^8.3.0",
    "eslint-plugin-prettier": "^4.0.0",
    "eslint-plugin-vue": "^8.0.3",
    "lint-staged": "^11.1.2",
    "prettier": "^2.4.1",
    "sass": "^1.32.7",
    "sass-loader": "^12.0.0",
    "typescript": "~4.1.5"
  }

Steps to reproduce
Trying to use Module federation with Vue and vue-router, however, if it is with publicPath set up, the actual route becomes weird.

use vue-cli to create a new Vue app with vue-router
set publicPath and devServer port in vue.config.js

const { defineConfig } = require("@vue/cli-service");
module.exports = defineConfig({
  transpileDependencies: true,
  publicPath: "http://localhost:9001/",
  devServer: {
    port: 9001,
  },
});

Run the app via npm run serve
For Vue 2 app, the route looks ok on the home page, which is http://localhost:9001
When navigating to the about page, the route becomes http://localhost:9001/http:/localhost:9001/about
When navigating back to the home page from the about page, the route becomes http://localhost:9001/http:/localhost:9001/

For Vue 3 app, the route is already http://localhost:9001/http://localhost:9001/ on the home page by default. Navigating behaves the same as Vue 2 app, showing duplicated http://localhost:9001/.
What is expected?
No duplication in the actual route
What is actually happening?
showing http://localhost:9001/http://localhost:9001/ instead of http://localhost:9001/

If the project is set up with Webpack 5 and vue-router, the route is all good

Experiencing the same issue.

I am having the same problem

I had the same issue in context of federated modules and it seems that it's caused by the "BASE_URL" env parameter. Set the "base" parameter from the router to "/" and the problem should be solved.
const router = new VueRouter({
  mode: 'history',
  **base: process.env.BASE_URL,**
  routes
})


fix(region): avoid auzre request timeout

这个 PR 实现什么功能/修复什么问题:

[ ] 功能、bugfix描述
[x] 冒烟测试
[ ] 单元测试编写

是否需要 backport 到之前的 release 分支:

release/3.5

/area region
/cc @zexi

Codecov Report

Merging #9778 (0ba3100) into master (be959d9) will increase coverage by 5.98%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master    #9778       +/-   ##
===========================================
+ Coverage    5.98%   11.96%    +5.98%
===========================================
  Files         848      231      -617
  Lines      131796    25758   -106038
===========================================
- Hits         7887     3082     -4805
+ Misses     123207    22365   -100842
+ Partials      702      311      -391

Flag
Coverage Δ

aFlag
11.96% <ø> (+5.98%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/compute/models/i18nresource.go

pkg/mcclient/options/k8s/pvc.go

pkg/keystone/tokens/policy.go

pkg/cloudcommon/db/managed.go

pkg/cloudprovider/images.go

pkg/cloudcommon/db/enabledstatusdomainresource.go

pkg/compute/models/wireresource.go

pkg/compute/models/vpcs.go

pkg/mcclient/options/k8s/configmap.go

pkg/baremetal/utils/ipmitool/ipmitool.go

... and 607 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #9778 (0ba3100) into master (be959d9) will increase coverage by 5.98%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master    #9778       +/-   ##
===========================================
+ Coverage    5.98%   11.96%    +5.98%
===========================================
  Files         848      231      -617
  Lines      131796    25758   -106038
===========================================
- Hits         7887     3082     -4805
+ Misses     123207    22365   -100842
+ Partials      702      311      -391

Flag
Coverage Δ

aFlag
11.96% <ø> (+5.98%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/compute/models/i18nresource.go

pkg/mcclient/options/k8s/pvc.go

pkg/keystone/tokens/policy.go

pkg/cloudcommon/db/managed.go

pkg/cloudprovider/images.go

pkg/cloudcommon/db/enabledstatusdomainresource.go

pkg/compute/models/wireresource.go

pkg/compute/models/vpcs.go

pkg/mcclient/options/k8s/configmap.go

pkg/baremetal/utils/ipmitool/ipmitool.go

... and 607 more

Continue to review full report at Codecov.

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


Refactor SourceInfo and add support for pretty printing diagnostics

A lot of code has been rewritten. I tested it against several previous submissions, which have shown that the code is working well. Just in case I add this to a new branch.

I'd move everything inside the span package into a separate Maven module, as the code is basically independent of the Autograder itself (similar to the regex parser treeg)


Develop Data Validation Rules for Excel Upload

Before generating reports, the application needs to validate the data upload from the filled out template. The rules should check for the following:

That data dictionary and data tabs exist in the file

Column check for data dictionary, must include:

measurement_group
measurement_group_label
column_name
order
abbr
unit
abbr_unit

Data Dictionary must include AT MINIMUM one record

Check for required columns in Data tab, make sure they are correct data types.

year - integer
sample_id - varcar
farm_name - varchar
producer-id - varchar
field_name - varchar
field_id - integer
county - varchar
crop - varchar
longitude - numeric
latitude - numeric
texture - varchar

Is there at least one additional column Data tab in addition to required fields? (Needs at least one variable)

Ensure that additional columns present in Data tab are present in Data Dictionary. Reverse check to make sure all named keys in Data Dictionary appear as columns in Data tab.

Check for missing values in both tabs for all records

@jadeynryan, thoughts/questions:
2nd Validation Rule. I think we discussed removing order as a required field. to simplify it further, we could also omit abbr_unit and generate it in the back end by combining abbr and unit with the html break. what do you think?

7th Validation Rule. Will need some input from you here, which columns are a hardstop vs. warning? e.g. if they are missing lat/long for one record, should that bar them from generating the report?

2nd rule:  I think I can simplify by removing measurement_group_label, order, and abbr_unit. I'll need to refactor some of the .qmd code and {soils} functions.
4th rule: field_id doesn't have to be numeric,
7th rule: I did some refactoring today so that the map will just not appear, rather than have report generation halt in error, if the lat/long are missing.
The columns that must not be blank are:

year
sample_id
producer_id
field_id
texture

Another rule to consider: sample_id must be unique.

I simplified the data dictionary and refactored the code for the reports to still render okay in this commit  to {soils}.


[Gradle] Root component group and version info missing

Currently the group ID and version are missing from generated purls for the root project and child projects despite being specified in the settings.gradle file. Example with sbom in this repo.
For eg: pkg:maven/dependency-diff-check@latest?type=jar should be pkg:maven/com.ajmalab/dependency-diff-check@0.0.1-SNAPSHOT?type=jar

build.gradle is currently not parsed to get this info. Could you use the workaround to pass the --project-group and --project-version?

Can use the workaround, but figured it's worth raising an issue/feature request for future refinement!

Is there a command or logic to determining the group and version? Parsing could be used as a fallback.

@prabhu The gradle properties task should do the trick. The output is much more machine readable too, so you could perhaps use this to populate the project metadata section fully. It includes version, group and childProjects keys that contains the relevant info.
The task needs to be run separately for each sub-project (if any), just like the projects task with gradle :subproject1:properties to get the relevant properties.

@ajmalab PR https://github.com/CycloneDX/cdxgen/pull/332 is ready for your testing and review. This should fix both #328 and #317.

@heubeck, Could you also review and test PR #332 since it's a significant rewrite to remove the GRADLE_MULTI_PROJECT_MODE env variable?

@heubeck, Could you also review and test PR #332 since it's a significant rewrite to remove the GRADLE_MULTI_PROJECT_MODE env variable?

oh nice. will do, give me some days.

@heubeck, Could you also review and test PR #332 since it's a significant rewrite to remove the GRADLE_MULTI_PROJECT_MODE env variable?

Ok, @prabhu, did some tests with PR #332 .
Ordinary gradle projects work well, with and without the -r flag.
But I've a mixed project, that's structured like:
build.gradle # just some plugin config, no dependencies
module1/build.gradle # java app, build config and dependencies
module2/build.gradle # no dependencies, only the plugin "com.github.node-gradle.node" configured to wrap around a node app
module2/package-lock.json
module2/package.json # the node app used to produce a react app

this projects worked fine before using -r and captured all gradle and node dependencies.
now it fails with
No packages were found in gradle project {
   name: 'module2'
...

regardless of the -r parameter.

@heubeck how do I reproduce this issue? Also is there a line number shown in the error?

@prabhu were not able to create a reproducer so far, not quite sure where the problem lies.
here's the debug log:
Starting '/home/heubeck/w/github/cdxgen/bin/cdxgen -o sbom.json -r --fail-on-error --project-name my-project' in /home/heubeck/w/sbom-test/my-project
 Scanning .
 Performing babel-based package usage analysis with source code at .
 Parsing /home/heubeck/w/sbom-test/my-project/package-lock.json
 Parsing /home/heubeck/w/sbom-test/my-project/ui-app/package-lock.json
 Found 1308 npm packages at .
 Executing /home/heubeck/w/sbom-test/my-project/gradlew properties -q --console plain in .
 Executing /home/heubeck/w/sbom-test/my-project/gradlew :ui-app:properties -q --console plain in .
 Executing /home/heubeck/w/sbom-test/my-project/gradlew :ui-server:properties -q --console plain in .
 Executing /home/heubeck/w/sbom-test/my-project/gradlew :ui-app:dependencies -q --console plain in .
 No packages were found in gradle project {
   name: 'ui-app',
   type: 'library',
   group: 'my-project',
   version: 'latest',
   properties: [
     {
       name: 'buildFile',
       value: '/home/heubeck/w/sbom-test/my-project/ui-app/build.gradle.kts'
     },
     {
       name: 'projectDir',
       value: '/home/heubeck/w/sbom-test/my-project/ui-app'
     },
     {
       name: 'rootDir',
       value: '/home/heubeck/w/sbom-test/my-project'
     }
   ],
   purl: 'pkg:maven/my-project/ui-app@latest?type=jar',
   'bom-ref': 'pkg:maven/my-project/ui-app@latest?type=jar'
 }

but it doesn't seem to be related to the mixed setup, as without -r it only runs the gradle part and fails as well:
Starting '/home/heubeck/w/github/cdxgen/bin/cdxgen -o sbom.json --fail-on-error --project-name my-project' in /home/heubeck/w/sbom-test/my-project
 Executing /home/heubeck/w/sbom-test/my-project/gradlew properties -q --console plain in .
 Executing /home/heubeck/w/sbom-test/my-project/gradlew :ui-app:properties -q --console plain in .
 Executing /home/heubeck/w/sbom-test/my-project/gradlew :ui-server:properties -q --console plain in .
 Executing /home/heubeck/w/sbom-test/my-project/gradlew :ui-app:dependencies -q --console plain in .
 No packages were found in gradle project {
   name: 'ui-app',
   type: 'library',
   group: 'my-project',
   version: 'latest',
   properties: [
     {
       name: 'buildFile',
       value: '/home/heubeck/w/sbom-test/my-project/ui-app/build.gradle.kts'
     },
     {
       name: 'projectDir',
       value: '/home/heubeck/w/sbom-test/my-project/ui-app'
     },
     {
       name: 'rootDir',
       value: '/home/heubeck/w/sbom-test/my-project'
     }
   ],
   purl: 'pkg:maven/my-project/ui-app@latest?type=jar',
   'bom-ref': 'pkg:maven/my-project/ui-app@latest?type=jar'
 }

working on the reproducer...

@heubeck does it work without --fail-on-error? That option is quite strict.

yes, without --fail-on-error it works.
got the reproducer. it's not related to the mixed project, but the "package less" submodule.
pr-332.zip
cdxgen -o sbom.json --fail-on-error:
Executing gradle properties -q --console plain in .
Executing gradle :ui-app:properties -q --console plain in .
Executing gradle :ui-server:properties -q --console plain in .
Executing gradle :ui-app:dependencies -q --console plain in .
No packages were found in gradle project {
  name: 'ui-app',
  type: 'library',
  group: 'my-project',
  version: 'latest',
  properties: [
    {
      name: 'buildFile',
      value: '/home/heubeck/w/sbom-test/pr-332/ui-app/build.gradle.kts'
    },
    {
      name: 'projectDir',
      value: '/home/heubeck/w/sbom-test/pr-332/ui-app'
    },
    { name: 'rootDir', value: '/home/heubeck/w/sbom-test/pr-332' }
  ],
  purl: 'pkg:maven/my-project/ui-app@latest?type=jar',
  'bom-ref': 'pkg:maven/my-project/ui-app@latest?type=jar'
}

cdxgen -o sbom.json:
Executing gradle properties -q --console plain in .
Executing gradle :ui-app:properties -q --console plain in .
Executing gradle :ui-server:properties -q --console plain in .
Executing gradle :ui-app:dependencies -q --console plain in .
Executing gradle :ui-server:dependencies -q --console plain in .
Obtained 227 from this gradle multi-project. De-duping this list ...

I use --fail-on-error as default, as I'd like to rather have an error but an unrealiable sbom ;)

sorry, here's the answer to "what's with cdxgen 8.4.13":
 →  cdxgen -o sbom.json                                                                                8.3s  Sat 27 May 2023 09:57:13 PM CEST
Executing gradle dependencies -q --console plain in /home/heubeck/w/sbom-test/pr-332
 ~   w  s  pr-332 
 →  cdxgen -o sbom.json --fail-on-error
Executing gradle dependencies -q --console plain in /home/heubeck/w/sbom-test/pr-332
 ~   w  s  pr-332 
 →  cdxgen -o sbom.json --fail-on-error -r
Executing gradle projects -q --console plain projects in .
Found 2 gradle sub-projects. This might take a while ...
Executing gradle :ui-app:dependencies -q --console plain in .
Executing gradle :ui-server:dependencies -q --console plain in .
Obtained 229 from this gradle multi-project. De-duping this list ...
 ~   w  s  pr-332 
 →  GRADLE_MULTI_PROJECT_MODE=true cdxgen -o sbom.json --fail-on-error -r
Executing gradle projects -q --console plain projects in .
Found 2 gradle sub-projects. This might take a while ...
Executing gradle :ui-app:dependencies -q --console plain in .
Executing gradle :ui-server:dependencies -q --console plain in .
Obtained 229 from this gradle multi-project. De-duping this list ...
 ~   w  s  pr-332 
 →  GRADLE_MULTI_PROJECT_MODE=true cdxgen -o sbom.json --fail-on-error
Executing gradle projects -q --console plain projects in .
Found 2 gradle sub-projects. This might take a while ...
Executing gradle :ui-app:dependencies -q --console plain in .
Executing gradle :ui-server:dependencies -q --console plain in .
Obtained 229 from this gradle multi-project. De-duping this list ...

@heubeck What is the output for gradle :ui-app:dependencies -q --console plain. If it is empty then it is an incorrect fail on error which could be removed.

# gradle :ui-app:dependencies -q --console plain

------------------------------------------------------------
Project ':ui-app'
------------------------------------------------------------

No configurations

A web-based, searchable dependency report is available by adding the --scan option.

@heubeck Just like I suspected. Must be a left over from the old check which could be removed. Will let you know once I push something new tomorrow. Thank you so much for your help!

:1st_place_medal:
youre the one who should be thanked

@heubeck Just like I suspected. Must be a left over from the old check which could be removed. Will let you know once I push something new tomorrow. Thank you so much for your help!

reproducer as well as real project are working now after your last changes on PR #332, @prabhu

@heubeck I tested against elasticsearch last night and there were too many errors. Not sure how the older versions performed. Not sure if there are any bugs reading gradle properties to determine the sub-projects.

@heubeck @ajmalab
For some subprojects, gradle projects command is succeeding while properties command is failing. Any thoughts?
./gradlew :client:transport:projects
------------------------------------------------------------
Project ':client:transport' - Elasticsearch subproject :client:transport
------------------------------------------------------------

Project ':client:transport' - Elasticsearch subproject :client:transport
No sub-projects

To see a list of the tasks of a project, run gradlew <project-path>:tasks
For example, try running gradlew :client:transport:tasks

To see a list of all the projects in this build, run gradlew :projects

BUILD SUCCESSFUL in 16s
20 actionable tasks: 12 executed, 8 up-to-date

./gradlew :client:transport:properties
> Task :client:transport:properties FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':client:transport:properties'.
> Basedir /home/almalinux/work/elastic/elasticsearch/client/transport does not exist

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.

* Get more help at https://help.gradle.org

BUILD FAILED in 4s
20 actionable tasks: 1 executed, 19 up-to-date

Pardon me, I've no real clue about gradle.

@heubeck I have added a workaround to only run properties command for the first level of sub-projects. Could you kindly test the latest and let me know how it looks?

Tried my usual projects, everything continues to work fine with your latest push on pr #332, @prabhu. Thank you!

@prabhu Just tested this out, looks brilliant, especially automating the multi project check for gradle!
As for the error you're encountering when running the projects task on some sub-projects: elasticsearch has manually configured the list of subprojects here. However certain sub-projects don't exist anymore (you can see that the client/transport directory was created in this PR), but their gradle config hasn't been updated accordingly, so gradle still sees that subproject, but fails to run the task since the directory simply doesn't exist. I would simply ignore those edge cases.

Thank you so much for confirming. Learnt a number of things about gradle in the last few days thanks to you guys. 8.5.0 is released with this new feature. Enjoy!

@prabhu just noticed a very minor bug, in the metadata.componentseciton, the purl and bom-ref have values beginning with pkg:application rather than pkg:maven. This is still correctly shown as pkg:maven in the dependencies section though, so just the one place.

@ajmalab This is interesting. Shouldn't it be application under dependencies section as well for sub-projects?

@prabhu Another small one I've noticed, in single project builds, the metadata.component.components is populated with the info of the root project itself. Essentially, metadata.component is replicated inside metadata.component.components. Don't know if this is intended behaviour, but seems inaccurate. Ideally it should be empty in single project builds.

@ajmalab This is interesting. Shouldn't it be application under dependencies section as well for sub-projects?

Nop, can only find a single occurrence of pkg:application in the entire sbom. As for whether application or maven is most accurate for the root of a multi-project build, I believe it definitely should be maven according to the purl-spec (but I', not expert on this).

@prabhu Another small one I've noticed, in single project builds, the metadata.component.components is populated with the info of the root project itself. Essentially, metadata.component is replicated inside metadata.component.components. Don't know if this is intended behaviour, but seems inaccurate. Ideally it should be empty in single project builds.

I am unable to reproduce this with java-test. Do you have an example?

@prabhu Interesting, this is the latest sbom for java-test I could produce with this branch.

@ajmalab Could you kindly test with https://github.com/CycloneDX/cdxgen/pull/339

Thank you so much for your help. 8.5.1 released with the fixes now.


Allow serializing public key to compressed form

Fixes https://github.com/sorpaas/libsecp256k1-rs/issues/1
Add PublicKey::serialize_compressed.

I just noticed you'd added this. Thanks tons :D !


[FEEDSTOCK REQUEST] Huggingface Accelerate

Describe the package you'd like added
The Huggingface Accelerate lib provides "A simple way to train and use PyTorch models with multi-GPU, TPU, mixed-precision."
Describe how this package fits in with the project
A number of other huggingface packages have already been added to this project.
Additional context
This package does seem to make it very easy to used multiple devices: https://github.com/huggingface/accelerate#easy-to-integrate

Thanks @asmith26 ! We will see if it can be included in our coming release.

@asmith26, I see that Anaconda has recently released huggingface_accelerate v0.15.0 for both PPC and x86.
$ conda search huggingface_accelerate
Loading channels: done
# Name                       Version           Build  Channel
huggingface_accelerate          0.15.0 py310h06a4308_0  pkgs/main
huggingface_accelerate          0.15.0  py37h06a4308_0  pkgs/main
huggingface_accelerate          0.15.0  py38h06a4308_0  pkgs/main
huggingface_accelerate          0.15.0  py39h06a4308_0  pkgs/main

Many thanks @cdeepali for the info, can confirm mamba install huggingface_accelerate installs the latest version for me.


Compiled figure S3

Rest of #47
Here is Fig S3, but it has lots of whitespace if we want everything at 8.5x11!
Here's also a screenshot of what it might look like if we wanted to, for example, fill some whitespace with download images, but as @allyhawkins pointed out in https://github.com/AlexsLemonade/scpca-paper-figures/issues/47#issuecomment-1932970232, if we add the download images here we'd probably want to do it for all figures with workflows, which might not be something we actually want.

This is now updated with a larger font, with only panels A-B and at paper size 8.5x11 as per the original issue. There is inevitably a lot of whitespace with this paper size, so if we have other ideas about filling this whitespace (or accepting it as it is what it is?) let me know!

Argh I borked this branch because I thought I had it stacked so I merged something into it, but that was wrong! Going to close out this PR and open a fresh one.


Bold project title in registration success email

Purpose
Bold project titles in registration success email. close issue #3304.
Changes
Puts <b> tag on project title.
Side Effects
None.

Tiny change with no side effects. Good to go.


Add declare

Q
A

Is bugfix?
✔/❌

New feature?
✔/❌

Breaks BC?
✔/❌

Tests pass?
✔/❌

Fixed issues
comma-separated list of tickets # fixed by the PR, if any

Tests failed. Would you please re-check it?

Thks.


Initial release of Robbus Kidsy V1.0.0 library

This is the initial release of the Rocket Launcher - Robbus Kidsy library V1.0.0, compatible with hardware V3.2

@ArduinoBot