Don't Merge! PR real time test for webhook case

Docs Build status updates of commit 897fa08:
:clock10: Pending: waiting for processors (18 builds ahead of you)
:warning: Docs Build is busy, currently there are 18 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 897fa08:
:clock10: Full build: the average full build time is 7 min(s) 43 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit 897fa08:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-conceptual/testing.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/testing.md

[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Button to load all missing repositories that have subscribed issues

Description
The /notifications/subscriptions feature has a Repository/Filter by repository dropdown on the page. Unfortunately it only includes a small and seemingly random (from what I can tell) subset of repositories containing issues you have subscribed to. The filter list is generated by this SSR endpoint. The feature I'm proposing to add is a button that once clicked would background load the missing repositories containing subscribed issues by using some form of this API query:
query {
  viewer {
    issues(filterBy: {viewerSubscribed: true}, first: 100) {
      nodes {
        repository {
          id
          nameWithOwner
          owner {
            avatarUrl(size: 30)
          }
        }
      }
    }
  }
}

Any repositories missing from the filter list would be merged into the SSRed DOM fragment so they would be present and searchable in the dropdown.
Screenshot

An example of a repository that's completely missing from the list.

The location where the "Load All"/"Load Missing" button should be added
Example URL
https://github.com/notifications/subscriptions

You should also send this report to GitHub, that looks like their bug.

My assumption is that they did this to avoid excessive load since there could be hundreds of repos there. I don’t think we'll add this as it would involve managing API pagination and lazy-loading in an already-interactive widget.
Asking GitHub would be best as it would be easier to add it natively.

I've created a GitHub Issues Feedback discussion for this problem. Feel free to close this one out in favor of https://github.com/github/feedback/discussions/7144.

FYI for anyone trying to work around this, the GraphQL query I mentioned is completely useless for solving this problem and doesn't even do what I originally thought it did. The viewerSubscribed filter in the GraphQL API is a complete lie, it doesn't List issues subscribed to by viewer. as it says it does. It only includes issues which you have created and subscribed to (which is the default after creation) and does not include additional issues not created by you that you subscribe to.


Fix indentation in react-native link for Android

If I am not mistaken, react-native link introduces wrong indentation in MainApplication.java.
Proposed changes accounts for both backwards compatibility (react-native unlink will be able to handle libs added either before or after the change) and any future change in whitespace.
The revokePatch.js file was a bit problematic since it expects to remove exactly what was added, therefore I've introduced regexp field to the patch object which is used in the revokePatch.js if present. This way it is compatible with all other patches and allows for handling regexp changes easily.
BUT in order to not introduce any mess to the codebase, this way of using regexp field should be accepted and expected for future changes like this one regarding react-native link for Android.
Test Plan:

Create empty react-native-init $PROJECT_NAME.
Install any lib requiring linking, link it on current build via react-native link $LIBRARY_NAME.
Switch to RN version with proposed changes (quickest way is to manually modify your local /node_modules/react-native with those two patches).
Link another library.

NOTE: _There should be now two linked libraries in android/app/src/main/java/com/$PROJECT_NAME/MainApplication.java: one with correct and one with incorrect indentation.

Run react-native unlink $LIBRARY_NAME; react-native unlink $ANOTHER_LIBRARY_NAME.

Now both libraries should be gone (i.e. the one added before and the one added after proposed change).
Release Notes:
[INTERNAL] [ENHANCEMENT] [/local-cli/link/android/patches] - Fix indentation in react-native link for Android

Sorry for the eslint problems.
Changed tests to expect new amount of spaces. Not sure if should:
a) change it to regexp
b) account for both old and new value
c) leave it as it is.

Thank you for your PR. We just moved this code to https://github.com/react-native-community/react-native-cli so please submit your PR there.


Unit Hunter without locking 3* and 4*

Hi, is it possible to have the unit hunter function without it locking 3* and 4* units in the game when the 'Sell 3*' and 'Sell 4*' are de-selected?

You can use UnfavoriteAll() to get rid of the locks

the unit hunter was working but now it crashes on me. is there anything that i have done wrong? thanks for your time

No tickets?

"You can use UnfavoriteAll() to get rid of the locks" how to do this?

Unit hunter only works if you have 10+1 tickets leftover from injection.


Update typo in sortable parameter description

Description
It says "the default is true False", I'm assuming its just meant to say False, based on other defaults?
All SDK Contribution checklist:

[X] The pull request does not introduce [breaking changes]
[X] CHANGELOG is updated for new features, bug fixes or other significant changes.
[X] I have read the contribution guidelines.

General Guidelines and Best Practices

[X] Title of the pull request is clear and informative.
[X] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[X] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.


Use convention name for context variables

As per recommendation https://github.com/chef/automate/pull/852#discussion_r302424873
Signed-off-by: Salim Afiune<EMAIL_ADDRESS>

Thank you! 🎈


[No ticket] Reroute users if draft loading fails

Ticket: [No ticket]
Feature flag: n/a

Purpose

reroute users to the page-not-found if they are not a contributor on the draft

Summary of Changes

reimplement try-catch and reroute

Side Effects

none

QA Notes

Users that aren't contributors should be rerouted to page-not-found

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

13 of 13 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 71.914%

Totals

Change from base Build<PHONE_NUMBER>:
0.04%

Covered Lines:
4770

Relevant Lines:
6361

💛  - Coveralls


Shall we move long hard-coded coordinate arrays in the test files to separate files?

Hm, we also hard code the coordinates for the RectangularTank tests. Is it worth loading the coordinates from a separate file? It took me a while to generate this, and I need to generate this again for a csv file. Can we leave it as is and if it gets complicated we can still add a separate csv file. @efaulhaber what's your opinion on this?
On the other hand, it's a good point to put coordinates for setup tests in a separate csv file...
Originally posted by @LasNikas in https://github.com/trixi-framework/TrixiParticles.jl/pull/437#discussion_r1547822656

A quick thought on this: Most of these long arrays are three-liners, right? So when reading it in an editor without line-wrapping, it's just three lines that one can easily ignore.

A quick thought on this: Most of these long arrays are three-liners, right? So when reading it in an editor without line-wrapping, it's just three lines that one can easily ignore.

yes:

This depends on the array some will be formatted in a way that they will follow the 90 char length limit.


init creates the default component files #371

Description
dapr init creates default components folder with files inside.
#371
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[* ] Code compiles correctly
[ *] Created/updated tests
[ *] Extended the documentation

/ok-to-test

/ok-to-test

This command is used to run e2e tests in the dapr/dapr repo :)

build tests failing due to linter: https://github.com/dapr/cli/pull/373/checks?check_run_id=773484056


🐛 [firebase_crashlytics] Does not compile on iOS due to non-modular headers

Bug report
Describe the bug
When trying to compile my app for iOS the build process fails with the following error:
Click To Expand
Could not build the precompiled application for the device.
Swift Compiler Error (Xcode): Include of non-modular header inside framework module 'FirebaseSessions.FIRSESNanoPBHelpers': '/Users/mario/Desktop/ecoforest_control/ios/Pods/Headers/Public/nanopb/pb.h'
/Users/mario/Desktop/ecoforest_control/ios/Pods/FirebaseSessions/FirebaseSessions/SourcesObjC/NanoPB/FIRSESNanoPBHelpers.h:28:8

Swift Compiler Error (Xcode): Include of non-modular header inside framework module 'FirebaseSessions.FIRSESNanoPBHelpers': '/Users/mario/Desktop/ecoforest_control/ios/Pods/Headers/Public/nanopb/pb_decode.h'
/Users/mario/Desktop/ecoforest_control/ios/Pods/FirebaseSessions/FirebaseSessions/SourcesObjC/NanoPB/FIRSESNanoPBHelpers.h:29:8

Swift Compiler Error (Xcode): Include of non-modular header inside framework module 'FirebaseSessions.FIRSESNanoPBHelpers': '/Users/mario/Desktop/ecoforest_control/ios/Pods/Headers/Public/nanopb/pb_encode.h'
/Users/mario/Desktop/ecoforest_control/ios/Pods/FirebaseSessions/FirebaseSessions/SourcesObjC/NanoPB/FIRSESNanoPBHelpers.h:30:8

Swift Compiler Error (Xcode): Include of non-modular header inside framework module 'FirebaseSessions.sessions_nanopb': '/Users/mario/Desktop/ecoforest_control/ios/Pods/Headers/Public/nanopb/pb.h'
/Users/mario/Desktop/ecoforest_control/ios/Pods/FirebaseSessions/FirebaseSessions/SourcesObjC/Protogen/nanopb/sessions.nanopb.h:21:9

Swift Compiler Error (Xcode): Could not build Objective-C module 'FirebaseSessions'

Error launching application on iPhone.

Expected behavior
Xcode should build the app.
Sample project
https://github.com/mrcsilva/crashlytics_error

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.7.7, on macOS 12.6.2 21G320 darwin-x64, locale en-PT)
[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0-rc1)
[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.3)
[✓] IntelliJ IDEA Community Edition (version 2022.3.3)
[✓] VS Code (version 1.71.2)
[✓] Connected device (3 available)
    ! Error: (null) needs to connect to determine its availability. Check the connection between the device and its companion iPhone, and the connection between the iPhone and Xcode. Both devices may also
      need to be restarted and unlocked. (code 1)
[✓] HTTP Host Availability

• No issues found!

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.19.4
Flutter SDK 3.7.7
ecoforest_control 2.3.7+58

dependencies:
- app_tracking_transparency 2.0.3 [flutter]
- collapsible 1.0.0 [flutter]
- cupertino_icons 1.0.5
- device_info_plus 7.0.1 [device_info_plus_platform_interface ffi file flutter flutter_web_plugins meta win32]
- firebase_analytics 10.1.6 [firebase_analytics_platform_interface firebase_analytics_web firebase_core firebase_core_platform_interface flutter]
- firebase_crashlytics 3.0.17 [firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface flutter stack_trace]
- firebase_performance 0.9.0+16 [firebase_core firebase_core_platform_interface firebase_performance_platform_interface firebase_performance_web flutter]
- firebase_remote_config 3.0.15 [firebase_core firebase_core_platform_interface firebase_remote_config_platform_interface firebase_remote_config_web flutter]
- flutter 0.0.0 [characters collection js material_color_utilities meta vector_math sky_engine]
- flutter_localizations 0.0.0 [flutter intl characters clock collection js material_color_utilities meta path vector_math]
- fluttericon 2.0.0 [flutter]
- font_awesome_flutter 10.4.0 [flutter]
- google_mobile_ads 2.3.0 [meta flutter visibility_detector]
- http 0.13.5 [async http_parser meta path]
- intl 0.17.0 [clock path]
- ionicons 0.2.2 [flutter]
- mediation_test 0.0.3 [flutter]
- path 1.8.2
- provider 6.0.5 [collection flutter nested]
- purchases_flutter 4.11.0 [flutter freezed_annotation json_annotation]
- shared_preferences 2.0.18 [flutter shared_preferences_android shared_preferences_foundation shared_preferences_linux shared_preferences_platform_interface shared_preferences_web shared_preferences_windows]
- sprintf 7.0.0
- sqflite 2.2.6 [flutter sqflite_common path]
- url_launcher 6.1.10 [flutter url_launcher_android url_launcher_ios url_launcher_linux url_launcher_macos url_launcher_platform_interface url_launcher_web url_launcher_windows]
- weather_icons 3.0.0 [flutter]
- webview_flutter 4.0.6 [flutter webview_flutter_android webview_flutter_platform_interface webview_flutter_wkwebview]
- wifi_info_flutter 2.0.2 [flutter wifi_info_flutter_platform_interface]

dev dependencies:
- flutter_launcher_icons 0.12.0 [args checked_yaml cli_util image json_annotation path yaml]
- flutter_lints 2.0.1 [lints]
- intl_utils 2.8.2 [analyzer archive args dart_style http intl path petitparser yaml]

transitive dependencies:
- _fe_analyzer_shared 56.0.0 [meta]
- _flutterfire_internals 1.0.18 [collection firebase_core firebase_core_platform_interface flutter meta]
- analyzer 5.8.0 [_fe_analyzer_shared collection convert crypto glob meta package_config path pub_semver source_span watcher yaml]
- archive 3.3.6 [crypto path pointycastle]
- args 2.4.0
- async 2.10.0 [collection meta]
- boolean_selector 2.1.1 [source_span string_scanner]
- characters 1.2.1
- checked_yaml 2.0.2 [json_annotation source_span yaml]
- cli_util 0.3.5 [meta path]
- clock 1.1.1
- collection 1.17.0
- convert 3.1.1 [typed_data]
- crypto 3.0.2 [typed_data]
- dart_style 2.3.0 [analyzer args path pub_semver source_span]
- device_info_plus_platform_interface 6.0.1 [flutter meta plugin_platform_interface]
- fake_async 1.3.1 [clock collection]
- ffi 2.0.1
- file 6.1.4 [meta path]
- firebase_analytics_platform_interface 3.3.23 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_analytics_web 0.5.1+14 [_flutterfire_internals firebase_analytics_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- firebase_core 2.8.0 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_core_platform_interface 4.5.3 [collection flutter flutter_test meta plugin_platform_interface]
- firebase_core_web 2.2.2 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_crashlytics_platform_interface 3.3.17 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_performance_platform_interface 0.1.1+35 [_flutterfire_internals firebase_core flutter plugin_platform_interface]
- firebase_performance_web 0.1.1+24 [_flutterfire_internals firebase_core firebase_core_web firebase_performance_platform_interface flutter flutter_web_plugins js]
- firebase_remote_config_platform_interface 1.1.35 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_remote_config_web 1.1.24 [firebase_core firebase_core_web firebase_remote_config_platform_interface flutter flutter_web_plugins js]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters collection js matcher material_color_utilities meta source_span stream_channel string_scanner term_glyph]
- flutter_web_plugins 0.0.0 [flutter js characters collection material_color_utilities meta vector_math]
- freezed_annotation 2.2.0 [collection json_annotation meta]
- glob 2.1.1 [async collection file path string_scanner]
- http_parser 4.0.2 [collection source_span string_scanner typed_data]
- image 4.0.15 [archive meta xml]
- js 0.6.5 [meta]
- json_annotation 4.8.0 [meta]
- lints 2.0.1
- matcher 0.12.13 [meta stack_trace]
- material_color_utilities 0.2.0
- meta 1.8.0
- nested 1.0.0 [flutter]
- package_config 2.1.0 [path]
- path_provider_linux 2.1.10 [ffi flutter path path_provider_platform_interface xdg_directories]
- path_provider_platform_interface 2.0.6 [flutter platform plugin_platform_interface]
- path_provider_windows 2.1.5 [ffi flutter path path_provider_platform_interface win32]
- petitparser 5.1.0 [meta]
- platform 3.1.0
- plugin_platform_interface 2.1.4 [meta]
- pointycastle 3.7.0 [collection convert js]
- process 4.2.4 [file path platform]
- pub_semver 2.1.3 [collection meta]
- shared_preferences_android 2.0.17 [flutter shared_preferences_platform_interface]
- shared_preferences_foundation 2.1.5 [flutter shared_preferences_platform_interface]
- shared_preferences_linux 2.1.5 [file flutter path path_provider_linux path_provider_platform_interface shared_preferences_platform_interface]
- shared_preferences_platform_interface 2.1.1 [flutter plugin_platform_interface]
- shared_preferences_web 2.0.6 [flutter flutter_web_plugins shared_preferences_platform_interface]
- shared_preferences_windows 2.1.5 [file flutter path path_provider_platform_interface path_provider_windows shared_preferences_platform_interface]
- sky_engine 0.0.99
- source_span 1.9.1 [collection path term_glyph]
- sqflite_common 2.4.3 [synchronized path meta]
- stack_trace 1.11.0 [path]
- stream_channel 2.1.1 [async]
- string_scanner 1.2.0 [source_span]
- synchronized 3.0.1
- term_glyph 1.2.1
- test_api 0.4.16 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph matcher]
- typed_data 1.3.1 [collection]
- url_launcher_android 6.0.25 [flutter url_launcher_platform_interface]
- url_launcher_ios 6.1.2 [flutter url_launcher_platform_interface]
- url_launcher_linux 3.0.4 [flutter url_launcher_platform_interface]
- url_launcher_macos 3.0.4 [flutter url_launcher_platform_interface]
- url_launcher_platform_interface 2.1.2 [flutter plugin_platform_interface]
- url_launcher_web 2.0.16 [flutter flutter_web_plugins url_launcher_platform_interface]
- url_launcher_windows 3.0.5 [flutter url_launcher_platform_interface]
- vector_math 2.1.4
- visibility_detector 0.3.3 [flutter]
- watcher 1.0.2 [async path]
- webview_flutter_android 3.4.2 [flutter webview_flutter_platform_interface]
- webview_flutter_platform_interface 2.1.0 [flutter meta plugin_platform_interface]
- webview_flutter_wkwebview 3.2.1 [flutter path webview_flutter_platform_interface]
- wifi_info_flutter_platform_interface 2.0.1 [plugin_platform_interface flutter]
- win32 3.1.3 [ffi]
- xdg_directories 1.0.0 [meta path process]
- xml 6.2.2 [collection meta petitparser]
- yaml 3.1.1 [collection source_span string_scanner]

Updated with project where the build process fails

Having the same issue with the latest versions

Yes had exactly the same issue, had to revert to previous version and lock it in pubspec

Yes had exactly the same issue, had to revert to previous version and lock it in pubspec

@kbudulski Can you paste here the version you're using? I tried that but got the same error

Sure, here are the versions:
firebase_core: 2.7.1
firebase_crashlytics: 3.0.16
firebase_analytics: 10.1.5
firebase_messaging: 14.2.6
Remember not to use ^ symbol. When you run pod install, it should download 10.3.0 versions of dependencies :)

@mrcsilva and everyone facing this issue.
Since the error is Swift Compiler Error (Xcode): Include of non-modular header inside framework module from the log you shared, does setting the same in Xcode -> Target -> Build Settings -> Allow Non-modular Includes in Framework Modules to Yes help to resolve ?

@darshankawar Just retested and I face the same error when changing that to Yes

@mrcsilva
Upon running the repo, I am getting below error:
Error (Xcode): Undefined symbol: _MDFInsetsFlippedHorizontally

Error (Xcode): Undefined symbol: _MDFRectFlippedHorizontally

Could not build the application for the simulator.
Error launching application on iPhone 13.
dhs@Dhss-MacBook-Pro crashlytics_error %

From the pubspec.yaml, I see that you have other community packages, so in order to narrow down the original issue you reported, please try to have only flutterfire plugins, make sure they are on latest versions and then try to run the app again to see if you still get same error or not while building.

@darshankawar Updated the repo to only have flutterfire dependencies (they were already in the latest version). I still get the same error

@mrcsilva
So the error seems to be pointing to FirebaseSessions pods. This file in particular FIRSESnanoPBHelpers.h which seems to be coming from nanopb https://github.com/nanopb.
Also, this doesn't seem specific to firebase_crashlytics I guess, because I commented the plugin in pubspec.yaml and ran the app again which gave me same error.
Maybe it is related to FirebaseSessions pod with firebase_crashlytics, so maybe check if this is useful.

@mrcsilva Right, it's not a problem with firebase_crashlytics. However, that package along side with firebase_performance include the respective Firebase<library> pod.
Those pods have the FirebaseSessions pod as a dependency (check under ios/Podfile.lock), that's why removing only the Crashlytics doesn't remove the error.
Since all the dependencies are automatically managed by Flutter and CocoaPods I don't see a way of using the link you provided to solve the error.
For now I'm using the firebase_core package with a fixed version (2.7.1) in order to not fetch the SDK 10.6.0 that is causing the error.

i have same issue in with
firebase_analytics: ^10.1.5
firebase_auth: ^4.2.10
firebase_crashlytics: ^3.0.16
firebase_messaging: ^14.2.6
firebase_core: ^2.7.1
/ios/Pods/FirebaseSessions/FirebaseSessions/Sources/SessionStartEvent.swift:192:56: Cannot convert value of type 'UnsafeRawPointer' to expected argument type 'UnsafePointer<pb_byte_t>?' (aka 'Optional<UnsafePointer>')
problem in firebase_crashlytics after remove working fine . and problem only ios app.

Same here

I used the dependencies that you have in your project, @mrcsilva, but I used the latest versions:
dependencies:
  firebase_analytics: ^10.2.0
  firebase_core: ^2.9.0
  firebase_crashlytics: ^3.1.0
  firebase_performance: ^0.9.1
  firebase_remote_config: ^4.0.0
  flutter:
    sdk: flutter

I was able to build successfully via flutter CLI and Xcode. Do you still experience the issue with the latest versions?

@russellwheatley  I'm still getting the same error with the exact versions you mentioned.
I performed this before rebuilding to be sure no other versions were being used:
rm -rf Pods                                                                                [15:41:26]
rm -rf Podfile.lock
rm -rf ../pubspec.lock
rm -rf ~/.pub-cache/hosted/pub.dartlang.org/
rm -rf ~/Library/Developer/Xcode/DerivedData
pod cache clean --all
pod deintegrate
flutter pub cache repair
flutter clean
flutter pub get
pod setup
pod install
pod repo update

Also having the same issue, using all of the absolute latest package versions:
Package Versions:
cloud_firestore: ^4.5.1
cloud_functions: ^4.1.0
firebase_analytics: ^10.2.0
firebase_auth: ^4.4.1
firebase_core: ^2.9.0
firebase_crashlytics: ^3.1.0
firebase_database: ^10.1.0
firebase_dynamic_links: ^5.1.0
firebase_messaging: ^14.4.0
firebase_storage: ^11.1.0

Swift Compiler Error:
Swift Compiler Error (Xcode): Include of non-modular header inside framework module
'FirebaseSessions.FIRSESNanoPBHelpers': './nanopb/pb.h'
/Users/taza/Projects/daily-tsp/flutter/ios/Pods/FirebaseSessions/FirebaseSessions/SourcesObjC/NanoPB/FIRSESNanoPB
Helpers.h:28:8

Swift Compiler Error (Xcode): Include of non-modular header inside framework module
'FirebaseSessions.FIRSESNanoPBHelpers': './nanopb/pb_decode.h'
/Users/taza/Projects/daily-tsp/flutter/ios/Pods/FirebaseSessions/FirebaseSessions/SourcesObjC/NanoPB/FIRSESNanoPB
Helpers.h:29:8

Swift Compiler Error (Xcode): Include of non-modular header inside framework module
'FirebaseSessions.FIRSESNanoPBHelpers': './nanopb/pb_encode.h'
/Users/taza/Projects/daily-tsp/flutter/ios/Pods/FirebaseSessions/FirebaseSessions/SourcesObjC/NanoPB/FIRSESNanoPB
Helpers.h:30:8

Swift Compiler Error (Xcode): Include of non-modular header inside framework module
'FirebaseSessions.sessions_nanopb': './nanopb/pb.h'
/Users/taza/Projects/daily-tsp/flutter/ios/Pods/FirebaseSessions/FirebaseSessions/SourcesObjC/Protogen/nanopb/ses
sions.nanopb.h:21:9

Swift Compiler Error (Xcode): Could not build Objective-C module 'FirebaseSessions'

Encountered error while building for device.

I also ensured that full pod clean before each flutter build. This is overkill, but wanted to make sure there were no lingering pod artifacts:
cd ios
rm -rf Podfile.lock
rm -rf Pods
rm -rf pubspec.lock
pod repo update
pod cache clean --all
pod deintegrate
pod setup
pod install --repo-update

I just created a new Flutter project and added the dependencies you mentioned, @walsha2:
cloud_firestore: ^4.5.1
cloud_functions: ^4.1.0
firebase_analytics: ^10.2.0
firebase_auth: ^4.4.1
firebase_core: ^2.9.0
firebase_crashlytics: ^3.1.0
firebase_database: ^10.1.0
firebase_dynamic_links: ^5.1.0
firebase_messaging: ^14.4.0
firebase_storage: ^11.1.0

I was able to build and run the app successfully.  I noticed that in the time I posted my comment and you tested, all the firebase packages were updated (today). Sadly, this did not fix the issue. It does seem to be nanopb that is causing the Swift compiler to error.
Here were my steps. From a fresh flutter create project:
flutter create nanopb_bug_app

Add the latest firebase dependencies (as of today, April 18, 2022):
cloud_firestore: ^4.5.2
cloud_functions: ^4.1.1
firebase_analytics: ^10.2.1
firebase_auth: ^4.4.2
firebase_core: ^2.10.0
firebase_crashlytics: ^3.1.1
firebase_database: ^10.1.1
firebase_dynamic_links: ^5.1.1
firebase_messaging: ^14.4.1
firebase_storage: ^11.1.1

Build the app
flutter build ios

Error:
Swift Compiler Error (Xcode): Include of non-modular header inside framework module
'FirebaseSessions.FIRSESNanoPBHelpers': './nanopb/pb.h'
/nanopb_bug_app/ios/Pods/FirebaseSessions/FirebaseSessions/SourcesObjC/NanoPB/FIRSESNanoPBH
elpers.h:28:8
...

I even tried to enable CLANG_ALLOW_NON_MODULAR_INCLUDES_IN_FRAMEWORK_MODULES in Xcode and that did not work either, unfortunately.

Environment
Per the issue thread, @russellwheatley it looks like you have tried twice with various package versions and did not run into issues. However, @darshankawar was able to reproduce.
At this point it could be related to the development environment? This issue is tricky. Here are all of the relevant environment related details regarding hardware and software versions on my end. This seems to reliably reproduce the issue for me with any of the recent firebase package versions (versions after https://github.com/firebase/flutterfire/issues/10621#issuecomment-1509984049 - "Workaround").
# Mac (Apple MacBook Pro "M1 Pro")
>>> sysctl hw.model
hw.model: MacBookPro18,1

# MacOS version (Ventura)
>>> sw_vers -productVersion
13.3.1

# Xcode version
>>> xcodebuild -version
Xcode 14.3
Build version 14E222b

# CocoaPods version
>>> pod --version
1.12.0

# Flutter version
>>> flutter --version
Flutter 3.7.11 • channel stable • https://github.com/flutter/flutter.git
Framework • revision f72efea43c (7 days ago) • 2023-04-11 11:57:21 -0700
Engine • revision 1a65d409c7
Tools • Dart 2.19.6 • DevTools 2.20.1

My environment:
Apple M1 Max macbook
Flutter (Channel stable, 3.7.7, on macOS 12.5.1 21G83 darwin-arm64
Cocoapods: 1.11.3
Xcode: 14.2
It is worth checking the diff in your Podfile.lock with mine to be sure they are the same.

It is worth checking the diff in your Podfile.lock with mine to be sure they are the same.

It was a little hard to actually run  a diff with your Podfile.lock because the full file was not raw uploaded so the formatting was off. I did spot check and it looked like they were all the same versions.  The PODFILE CHECKSUM values were exactly the same.
Here is my Podfile.lock as a txt file.

Same issue here, using these versions building on Codemagic
firebase_core: ^2.9.0
firebase_analytics: ^10.2.0
firebase_crashlytics: ^3.1.0
firebase_performance: ^0.9.1

Log:
Running pod install...                                             42.9s
Upgrading Pods-Runner-frameworks.sh
Running Xcode build...
Xcode archive done.                                         23.6s
Failed to build iOS app
Swift Compiler Error (Xcode): Include of non-modular header inside framework module 'FirebaseSessions.FIRSESNanoPBHelpers': '/Users/builder/clone/ios/Pods/Headers/Public/nanopb/pb.h'
/Users/builder/clone/ios/Pods/FirebaseSessions/FirebaseSessions/SourcesObjC/NanoPB/FIRSESNanoPBHelpers.h:28:8

Swift Compiler Error (Xcode): Include of non-modular header inside framework module 'FirebaseSessions.FIRSESNanoPBHelpers': '/Users/builder/clone/ios/Pods/Headers/Public/nanopb/pb_decode.h'
/Users/builder/clone/ios/Pods/FirebaseSessions/FirebaseSessions/SourcesObjC/NanoPB/FIRSESNanoPBHelpers.h:29:8

Swift Compiler Error (Xcode): Include of non-modular header inside framework module 'FirebaseSessions.FIRSESNanoPBHelpers': '/Users/builder/clone/ios/Pods/Headers/Public/nanopb/pb_encode.h'
/Users/builder/clone/ios/Pods/FirebaseSessions/FirebaseSessions/SourcesObjC/NanoPB/FIRSESNanoPBHelpers.h:30:8

Swift Compiler Error (Xcode): Include of non-modular header inside framework module 'FirebaseSessions.sessions_nanopb': '/Users/builder/clone/ios/Pods/Headers/Public/nanopb/pb.h'
/Users/builder/clone/ios/Pods/FirebaseSessions/FirebaseSessions/SourcesObjC/Protogen/nanopb/sessions.nanopb.h:21:9

Swift Compiler Error (Xcode): Could not build Objective-C module 'FirebaseSessions'

Encountered error while archiving for device.

Build failed :|
Failed to build for iOS

Same issue here, using these versions building on Codemagic:
firebase_core: ^2.9.0
firebase_analytics: ^10.2.0
firebase_crashlytics: ^3.1.0
firebase_performance: ^0.9.1

Log:
Running pod install...                                             42.9s
Upgrading Pods-Runner-frameworks.sh
Running Xcode build...
Xcode archive done.                                         23.6s
Failed to build iOS app
Swift Compiler Error (Xcode): Include of non-modular header inside framework module 'FirebaseSessions.FIRSESNanoPBHelpers': '/Users/builder/clone/ios/Pods/Headers/Public/nanopb/pb.h'
/Users/builder/clone/ios/Pods/FirebaseSessions/FirebaseSessions/SourcesObjC/NanoPB/FIRSESNanoPBHelpers.h:28:8

Swift Compiler Error (Xcode): Include of non-modular header inside framework module 'FirebaseSessions.FIRSESNanoPBHelpers': '/Users/builder/clone/ios/Pods/Headers/Public/nanopb/pb_decode.h'
/Users/builder/clone/ios/Pods/FirebaseSessions/FirebaseSessions/SourcesObjC/NanoPB/FIRSESNanoPBHelpers.h:29:8

Swift Compiler Error (Xcode): Include of non-modular header inside framework module 'FirebaseSessions.FIRSESNanoPBHelpers': '/Users/builder/clone/ios/Pods/Headers/Public/nanopb/pb_encode.h'
/Users/builder/clone/ios/Pods/FirebaseSessions/FirebaseSessions/SourcesObjC/NanoPB/FIRSESNanoPBHelpers.h:30:8

Swift Compiler Error (Xcode): Include of non-modular header inside framework module 'FirebaseSessions.sessions_nanopb': '/Users/builder/clone/ios/Pods/Headers/Public/nanopb/pb.h'
/Users/builder/clone/ios/Pods/FirebaseSessions/FirebaseSessions/SourcesObjC/Protogen/nanopb/sessions.nanopb.h:21:9

Swift Compiler Error (Xcode): Could not build Objective-C module 'FirebaseSessions'

Encountered error while archiving for device.

Build failed :|
Failed to build for iOS

Current configuration: Flutter channel: stable Mode: release Xcode version: 14.3 Machine: Mac mini M1

Commenting out the platform :ios, '11.0' line in Podfile solved the issue:
# Uncomment this line to define a global platform for your project
# platform :ios, '11.0'

Not sure why though.

@russellwheatley Still running into this same issue with the most recent package versions as of this comment.
Again, completely fresh repo: flutter create nanopb_bug_app with only the following package dependencies (on top of what is in the pubspec.yaml default)
cloud_firestore: ^4.6.0
cloud_functions: ^4.2.0
firebase_analytics: ^10.3.0
firebase_auth: ^4.5.0
firebase_core: ^2.11.0
firebase_crashlytics: ^3.2.0
firebase_database: ^10.1.2
firebase_dynamic_links: ^5.2.0
firebase_messaging: ^14.5.0
firebase_storage: ^11.1.2

Once those deps are added: flutter build ios - the error is encountered during Xcode build step:
Swift Compiler Error (Xcode): Include of non-modular header inside framework module
'FirebaseSessions.FIRSESNanoPBHelpers': './nanopb/pb.h'
/Desktop/nanopb_bug_app/ios/Pods/FirebaseSessions/FirebaseSessions/SourcesObjC/NanoPB/FIRSESNanoP
BHelpers.h:28:8

ios/Podfile:L30
target 'Runner' do
  pod 'GoogleUtilities', :modular_headers => true

  flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
end

Having the same issue with the latest Firebase versions 😢 Please don't close this issue, @google-oss-bot 🤖

@mrcsilva does this solve your problem?
target 'Runner' do
+  pod 'Firebase', :modular_headers => true
+  pod 'FirebaseCore', :modular_headers => true
+  pod 'FirebaseCoreInternal', :modular_headers => true
+  pod 'GoogleUtilities', :modular_headers => true

  flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
end

@russellwheatley

pod 'Firebase', :modular_headers => true
+  pod 'FirebaseCore', :modular_headers => true
+  pod 'FirebaseCoreInternal', :modular_headers => true
+  pod 'GoogleUtilities', :modular_headers => true

Added this to the podfile and updated the packages to the latest versions but I'm still having the same error when building
  firebase_core: ^2.13.0
  firebase_crashlytics: ^3.3.1
  firebase_performance: ^0.9.2+1
  firebase_analytics: ^10.4.1
  firebase_remote_config: ^4.2.1

Recap and Recreate
@russellwheatley just echoing what @mrcsilva said - have been tracking this Github issue for a while and with every new firebase release I hope that it resolves the issue, but no such luck.
To reiterate, this is easily reproducible for me from a fresh repo:
flutter create -i swift --platforms ios modular_headers

Then I incrementally added dependencies one by one, until the Xcode build fails:
  firebase_core: ^2.13.0
  firebase_crashlytics: ^3.3.1

That's it... as soon as I added firebase_crashlytics (any of the recent versions) the error crops up. Again, these are the only two dependencies in a fresh application, aside whatever else is in the stock pubspec.yaml file. No other changes were made to the stock flutter create application aside from adding those two deps.
Swift Compiler Error (Xcode): Include of non-modular header inside framework module
'FirebaseSessions.FIRSESNanoPBHelpers': './nanopb/pb.h'
/Users/user/Desktop/modular_headers/ios/Pods/FirebaseSessions/FirebaseSessions/SourcesObjC/NanoPB/FIRSE
SNanoPBHelpers.h:28:8

Feedback
Since this is so easily reproducible and you have not been able to reproduce it @russellwheatley, is there some other MacOS or XCode thing we need to dig into? I know you and I shared our system config information prior but nothing looked like a smoking gun. Summarized again below, M1 Macbook Pro running MacOS 13.4:
>>> swift --version
swift-driver version: 1.75.2 Apple Swift version 5.8 (swiftlang-<IP_ADDRESS>.2 clang-14<IP_ADDRESS>.100)
Target: arm64-apple-macosx13.0

>>> xcodebuild -version
Xcode 14.3
Build version 14E222b

>> pod --version
1.12.1

What could possibly be so different in your setup than mine or some of the other users who have come across this issue? Are there any global Swift build flags that you may have configured? Is there anything we can do to help this issue along? All of the solutions here have not worked and seem to be a little unrelated to the core issue.
Also - it does look like @darshankawar was able to reproduce this (https://github.com/firebase/flutterfire/issues/10621#issuecomment-1477652908), but I dont think he has chimed in since.

I followed your steps, I could not recreate I'm afraid.
I do have different versions to yourself 🤔. Let me know if changing any of these makes a difference, we can narrow down the search to some specific tool that will possibly allow me to recreate the issue.
>>> swift --version
swift-driver version: 1.62.15 Apple Swift version 5.7.2 (swiftlang-<IP_ADDRESS>.5 clang-14<IP_ADDRESS>)
Target: arm64-apple-macosx12.0

>>> xcodebuild -version
Xcode 14.2
Build version 14C18

>> pod --version
1.11.3

@russellwheatley

Xcode 14.2 includes Swift 5.7 and SDKs for iOS 16.2, iPadOS 16.2, tvOS 16.1, watchOS 9.1, and macOS Ventura 13.1. The Xcode 14.2 release supports on-device debugging in iOS 11 and later, tvOS 11 and later, and watchOS 4 and later. Xcode 14.2 requires a Mac running macOS Monterey 12.5 or later. - Release Notes

I downloaded an alternate Xcode image and downgraded to Xcode 14.2 because that is the version you have and the one that is bundled with Swift 5.7
>>> sudo xcode-select --switch /Applications/Xcode14.2.app

>>> xcodebuild -version

Xcode 14.2
Build version 14C18

>>> swift --version

swift-driver version: 1.62.15 Apple Swift version 5.7.2 (swiftlang-<IP_ADDRESS>.5 clang-14<IP_ADDRESS>)
Target: arm64-apple-macosx13.0

I even updated the cocoapods version to match:
>>> pod --version

1.11.3

After I made these changes, I tried to rebuild using the same exact project.  No luck, sadly. Same error.
Aside from downgrading my entire MacOS version (which I am not going to do) to match your older version, I am not sure what else I can do to throughly address any user/machine inconsistencies.

I've just wasted hours on this error, very annoying. I was defining some pods manually like that :
**pod 'GoogleMobileAdsMediationFacebook'
pod 'GoogleMobileAdsMediationAppLovin'**

target 'Runner' do
  use_frameworks!
  use_modular_headers!

  flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
end

Moving the pods definition just before flutter_install_all_ios_pods solved the issue
target 'Runner' do
  use_frameworks!
  use_modular_headers!

  **pod 'GoogleMobileAdsMediationFacebook'
  pod 'GoogleMobileAdsMediationAppLovin'**

  flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
end

I really hope it will help some of you :)

Error logs
Launching lib/main.dart on iPad (Dmytrij) in debug mode...
Disabling deprecated bitcode Xcode build setting. See https://github.com/flutter/flutter/issues/107887 for additional details.

Upgrading project.pbxproj
Automatically signing iOS for device deployment using specified development team in Xcode project: QN4KSWVM8M
Xcode build done.                                           27,2s
Failed to build iOS app
Could not build the precompiled application for the device.
Swift Compiler Error (Xcode): Include of non-modular header inside framework module 'FirebaseSessions.FIRSESNanoPBHelpers': './nanopb/pb.h'
/Users/okji/work/freelance/blowy/ios/Pods/FirebaseSessions/FirebaseSessions/SourcesObjC/NanoPB/FIRSESNanoPBHelpers.h:28:8

Swift Compiler Error (Xcode): Include of non-modular header inside framework module 'FirebaseSessions.FIRSESNanoPBHelpers': './nanopb/pb_decode.h'
/Users/okji/work/freelance/blowy/ios/Pods/FirebaseSessions/FirebaseSessions/SourcesObjC/NanoPB/FIRSESNanoPBHelpers.h:29:8

Swift Compiler Error (Xcode): Include of non-modular header inside framework module 'FirebaseSessions.FIRSESNanoPBHelpers': './nanopb/pb_encode.h'
/Users/okji/work/freelance/blowy/ios/Pods/FirebaseSessions/FirebaseSessions/SourcesObjC/NanoPB/FIRSESNanoPBHelpers.h:30:8

Swift Compiler Error (Xcode): Include of non-modular header inside framework module 'FirebaseSessions.sessions_nanopb': './nanopb/pb.h'
/Users/okji/work/freelance/blowy/ios/Pods/FirebaseSessions/FirebaseSessions/SourcesObjC/Protogen/nanopb/sessions.nanopb.h:21:9

Swift Compiler Error (Xcode): Could not build Objective-C module 'FirebaseSessions'

Uncategorized (Xcode): Command SwiftCompile failed with a nonzero exit code

Error launching application on iPad (Dmytrij).

ENV['COCOAPODS_DISABLE_STATS'] = 'true'

project 'Runner', {
  'Debug' => :debug,
  'Profile' => :release,
  'Release' => :release,
}

def flutter_root
  generated_xcode_build_settings_path = File.expand_path(File.join('..', 'Flutter', 'Generated.xcconfig'), __FILE__)
  unless File.exist?(generated_xcode_build_settings_path)
    raise "#{generated_xcode_build_settings_path} must exist. If you're running pod install manually, make sure flutter pub get is executed first"
  end

  File.foreach(generated_xcode_build_settings_path) do |line|
    matches = line.match(/FLUTTER_ROOT\=(.*)/)
    return matches[1].strip if matches
  end
  raise "FLUTTER_ROOT not found in #{generated_xcode_build_settings_path}. Try deleting Generated.xcconfig, then run flutter pub get"
end

require File.expand_path(File.join('packages', 'flutter_tools', 'bin', 'podhelper'), flutter_root)

flutter_ios_podfile_setup

target 'Runner' do
  use_frameworks!
  use_modular_headers!

  flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
end

post_install do |installer|
  installer.pods_project.targets.each do |target|
    flutter_additional_ios_build_settings(target)
  end
end

The comments on this issue have really not progressed determining what is wrong and how to actually solve it. Seems like any "solution" is just some odd patch that gets it to work in that user's environment, but does not actually address the core issue with modular headers and the Firebase pods, chiefly from FirebaseSessions.FIRSESNanoPBHelpers
@mrcsilva have you been able to resolve this issue somehow or have you just pinned the Firebase package versions to some older state? Since the update to Dart 3 and latest Flutter stable versions I am now getting into dependency hell as the locked Firebase package versions are limiting me from updating other, unrelated, packages.
Plus battling the google-oss-bot from labeling this issue as stale every couple of weeks 😅

@walsha2 I haven't had to update my app for a while so I just kept a specific version. That will be a problem soon.
From time to time I use the sample app that I created for this issue to check if it solved or not.
I don't think that modifying podfiles is a solution. The Firebase packages alone should compile as is and not force the user to change the podfile.
We'll have to wait a little more I guess 😅

Even though I git clone the same repository, it sometimes worked and sometimes didn't.
When it works, ios/Pods/Target Support Files/nanopb/ directory exists.
When it fails, ios/Pods/Target Support Files/nanopb-framework and ios/Pods/Target Support Files/ nanopb-library exist instead of ios/Pods/Target Support Files/nanopb/.
non-modular headers Error
>>> ls -Rl ios/Pods/Target\ Support\ Files/nanopb*
ios/Pods/Target Support Files/nanopb-framework:
total 56
-rw-r--r--  1 kzrnm  staff  858  7 12 22:59 nanopb-framework-Info.plist
-rw-r--r--  1 kzrnm  staff  136  7 12 22:59 nanopb-framework-dummy.m
-rw-r--r--  1 kzrnm  staff  195  7 12 22:59 nanopb-framework-prefix.pch
-rw-r--r--  1 kzrnm  staff  503  7 12 22:59 nanopb-framework-umbrella.h
-rw-r--r--  1 kzrnm  staff  791  7 12 22:59 nanopb-framework.debug.xcconfig
-rw-r--r--  1 kzrnm  staff  112  7 12 22:59 nanopb-framework.modulemap
-rw-r--r--  1 kzrnm  staff  791  7 12 22:59 nanopb-framework.release.xcconfig

ios/Pods/Target Support Files/nanopb-library:
total 32
-rw-r--r--  1 kzrnm  staff  132  7 12 22:59 nanopb-library-dummy.m
-rw-r--r--  1 kzrnm  staff  195  7 12 22:59 nanopb-library-prefix.pch
-rw-r--r--  1 kzrnm  staff  895  7 12 22:59 nanopb-library.debug.xcconfig
-rw-r--r--  1 kzrnm  staff  895  7 12 22:59 nanopb-library.release.xcconfig

Worked
>>> ls -Rl ios/Pods/Target\ Support\ Files/nanopb*
total 56
-rw-r--r--  1 kzrnm  staff  858  7 12 19:51 nanopb-Info.plist
-rw-r--r--  1 kzrnm  staff  116  7 12 19:51 nanopb-dummy.m
-rw-r--r--  1 kzrnm  staff  195  7 12 19:51 nanopb-prefix.pch
-rw-r--r--  1 kzrnm  staff  503  7 12 19:51 nanopb-umbrella.h
-rw-r--r--  1 kzrnm  staff  716  7 12 19:51 nanopb.debug.xcconfig
-rw-r--r--  1 kzrnm  staff  102  7 12 19:51 nanopb.modulemap
-rw-r--r--  1 kzrnm  staff  716  7 12 19:51 nanopb.release.xcconfig

>>> ls -Rl ios/Pods/Target\ Support\ Files/nanopb-*
drwxr-xr-x  9 kzrnm  staff  288  7 12 19:51 ios/Pods/Target Support Files/nanopb/

Env

Versions
>>> swift --version
swift-driver version: 1.75.2 Apple Swift version 5.8.1 (swiftlang-<IP_ADDRESS>.5 clang-14<IP_ADDRESS>.100)
Target: arm64-apple-macosx13.0

>>> xcodebuild -version
Xcode 14.3.1
Build version 14E300c

>> pod --version
1.12.1

Although it is a provisional method, I was able to build iOS project.

Make ios/nanopb directory.
Download files of nanopb and nanopb-podspec to ios/nanopb.
Add pod 'nanopb', :path => './nanopb' to ios/Podfile

https://github.com/mrcsilva/crashlytics_error/pull/1

After all these months, finally some sort of build solution, albeit a workaround.
@kzrnm is spot on. The minimal changes in https://github.com/mrcsilva/crashlytics_error/pull/1/files (described in https://github.com/firebase/flutterfire/issues/10621#issuecomment-1634522430) do indeed get this to finally build.
Thank you for providing that workaround.

@kzrnm Thanks for the workaround. However, I'll stick to specifying old versions until Google fixes this. I hope they will soon

I decided to circle back to this issue. This comment was interesting to me, and indeed is the cause of the issue.
The quickest way to test whether nanopb dependency is installed correctly and can be located is by running
pod install --verbose in the ios directory. If it was installed correctly, you would see this in your console:
    - Installing target `nanopb` iOS 9.0
      - Generating module map file at `Pods/Target Support Files/nanopb/nanopb.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/nanopb/nanopb-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/nanopb/nanopb-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/nanopb/nanopb-dummy.m`

If it isn't installed as expected by the Firebase SDK, it would look like this:
    - Installing target `nanopb-framework` iOS 9.0
      - Generating module map file at `Pods/Target Support Files/nanopb-framework/nanopb-framework.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/nanopb-framework/nanopb-framework-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/nanopb-framework/nanopb-framework-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/nanopb-framework/nanopb-framework-dummy.m`
    - Installing target `nanopb-library` iOS 9.0
      - Generating dummy source at `Pods/Target Support Files/nanopb-library/nanopb-library-dummy.m`

I found that if I commented out this line in your Podfile, @mrcsilva, it would install nanopb dependency on the correct path.
To check whether this was a result of the FlutterFire plugins, I removed them (all FlutterFire plugins) from the pubspec.yaml, ran flutter clean and added them as dependencies in the Podfile:
  pod 'Firebase/Core'
  pod 'Firebase/Crashlytics'

I ran pod install --verbose and got the same results when commenting/uncommenting out the global platform setting at the top of the Podfile. In fact, I completely cleared out the Podfile of all Flutter configuration and still got the same results. This leads me to believe it isn't a result of FlutterFire nor anything set in the Podfile.
I also created a Swift project from scratch and added the pods like above:
  pod 'Firebase/Core'
  pod 'Firebase/Crashlytics'

But got the correct nanopb installation no matter whether the global platform setting in the Podfile was commented out/uncommented.
I can only surmise that it is something set in the project.pbxproj or Xcode that is making the difference. But not sure what could make cocoapods install it differently.

@russellwheatley
Still hadn't time to test your findings. I'll try to do so this week

I found that if I commented out this line in your Podfile, @mrcsilva, it would install nanopb dependency on the correct path and the app would build correctly.

This is the critical line buried in my last comment. It is presumably the key to the solution I think.

Closing this based on above comment as resolved.

@darshankawar Please reopen this issue. In my repository the installation fails even if I comment out platform :ios, '12.0'.

I ran pod install --verbose and got the same results when commenting/uncommenting out the global platform setting at the top of the Podfile.
...
But got the correct nanopb installation no matter whether the global platform setting in the Podfile was commented out/uncommented.

As @russellwheatley wrote, commenting out or not did not change the result.
Regardless of the settings, it may succeed or fail.


Log formatting in shim

As discussed at the containerd summit, many people agree that adding log driver capabilities to containerd seems useful.  Having thought about this some, there are two major drawbacks that have been brought up.  1) shim is already part of a plug-in, so adding plug-ins to a plug-in is a bit odd.  2) log drivers could be extremely expensive and burdensome to add to the shim.  Following the suggestion of @thockin maybe we should look at a simpler approach of having a format flag.
When you think about it, the majority of log drivers are just shipping content elsewhere.  From that perspective containerd could just write to a file and driver read the file.  The fundamental downside here is that you lose the context of when the data was written.  So the key thing missing here is just the timestamp.  What I propose is that the shim take one arguement for "--structured-output."
If true:  shim reads from process stdout/err, formats data into timestamped segments, writes to passed in file or fifo.
If false: shim reads from process stdout/err writes to passed in file or fifo.
The key thing here is to decide on a standard format.  I don't know if I'd want to do a fmt style configuration but instead pick some efficient binary format.  Even json is not so efficient as you have to reencode the data as a string.  I'm not a serialization format expert, but maybe a simple protobuf structure could do?  Something that would be as close to "TIMESTAMP", "DATA LENGTH", "DATA".

Instinctively, the VAST majority of the log line is the data itself, so any
optimization here is moot.  Make it simple and easy to consume.
On Fri, Mar 3, 2017 at 9:06 AM, Darren Shepherd<EMAIL_ADDRESS>wrote:

As discussed at the containerd summit
https://github.com/docker/containerd/blob/master/reports/2017-02-24.md,
many people agree that adding log driver capabilities to containerd seems
useful. Having thought about this some, there are two major drawbacks that
have been brought up. 1) shim is already part of a plug-in, so adding
plug-ins to a plug-in is a bit odd. 2) log drivers could be extremely
expensive and burdensome to add to the shim. Following the suggestion
https://github.com/docker/containerd/issues/563#issuecomment-282821252
of @thockin https://github.com/thockin maybe we should look at a
simpler approach of having a format flag.
When you think about it, the majority of log drivers are just shipping
content elsewhere. From that perspective containerd could just write to a
file and driver read the file. The fundamental downside here is that you
lose the context of when the data was written. So the key thing missing
here is just the timestamp. What I propose is that the shim take one
arguement for "--structured-output."
If true: shim reads from process stdout/err, formats data into timestamped
segments, writes to passed in file or fifo.
If false: shim reads from process stdout/err writes to passed in file or
fifo.
The key thing here is to decide on a standard format. I don't know if I'd
want to do a fmt style configuration but instead pick some efficient
binary format. Even json is not so efficient as you have to reencode the
data as a string. I'm not a serialization format expert, but maybe a simple
protobuf structure could do? Something that would be as close to
"TIMESTAMP", "DATA LENGTH", "DATA".
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/containerd/issues/603, or mute the thread
https://github.com/notifications/unsubscribe-auth/AFVgVGERfY7TCtMGhhqRV52ICVTAqBo7ks5riEiIgaJpZM4MSgZr
.

From the perspective of CRI, log of a container should be in one file, and the log format is expected to be:
2016-10-06T00:17:09.669794202Z stdout log content 1

Timestamp is absolutely needed. However, at least in current CRI, we also need the stream type (stdout/stderr) to be included in the log.
It would be very helpful to make it possible to include this information in the container log. Or else, we have to:

Add another layer to convert logging format.
Change CRI (Really not a good option for us).

Would it be helpful or harmful to un-mix stdout and stderr ?
On Fri, Mar 3, 2017 at 2:28 PM, Lantao Liu<EMAIL_ADDRESS>wrote:

From the perspective of CRI, log of a container should be in one file, and
the log format is expected to be:
2016-10-06T00:17:09.669794202Z stdout log content 1
Timestamp is absolutely needed. However, at least in current CRI, we also
need the stream type (stdout/stderr) to be included in the log.
It would be very helpful to make it possible to include this information
in the container log. Or else, we have to:

Add another layer to convert logging format.
Change CRI (Really not a good option for us).

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/containerd/issues/603#issuecomment-284087805,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFVgVPGG3FG4FjshVpJFZoRP0iKSlAtkks5riJP2gaJpZM4MSgZr
.

Should it be split by new line or write() based chunks?  For binary data you will never get a new line and have to have extra logic around when to flush.  If its based on what we get on the write its much simpler and robust for all types of output.

Would it be helpful or harmful to un-mix stdout and stderr ?

If we un-mix stdout and stderr in containerd, but still assume they are combined in CRI, then we still have to add another layer in containerd shim to combine them continuously.
If we un-mix stdout and stderr in CRI, we need to change current CRI. :)

Can we safely know the size of a write() on one end of a FIFO from the
other end?  I don't think POSIX guarantees that a read() will get all of a
write(), even with an enormous buffer.
On Fri, Mar 3, 2017 at 2:50 PM, Michael Crosby<EMAIL_ADDRESS>wrote:

Should it be split by new line or write() based chunks? For binary data
you will never get a new line and have to have extra logic around when to
flush. If its based on what we get on the write its much simpler and
robust for all types of output.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/containerd/issues/603#issuecomment-284092345,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFVgVBoSP5B1bav6tX6x_ByC1g5AmeFKks5riJkhgaJpZM4MSgZr
.

Even if it does not guarantee that they match it is much more robust than looking for a newline that may never come.

Is it bad to use something like go templates here?
We could require a template to be passed to the shim and then the template author has control on the payload.
{{timestamp "shortdate"}} {{data}}
# ioname can be stdout/stderr and added if that is what you want in your data or
# just place both times in a single file
{{timestamp}} {{ioname}} {{data}}
{{timestamp}} {{len data}} {{data}}

This would be more flexible than just a sprintf

That terrifies me.
On Mar 3, 2017 3:04 PM, "Michael Crosby"<EMAIL_ADDRESS>wrote:

Even if it does not guarantee that they match it is much more robust than
looking for a newline that may never come.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/containerd/issues/603#issuecomment-284095120,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFVgVKc8XiX-278hKHZPFAlMZyNqB8rKks5riJyLgaJpZM4MSgZr
.

To clarify:

Should it be split by new line or write() based chunks?
I don't think POSIX guarantees that a read() will get all of a write()
Even if it does not guarantee that they match it is much more robust than looking for a newline that may never come.

That terrifies me.  What will happen is the user writes a long line, and we'll have a too-small buffer, so we can only read part of it, and we'll corrupt their logs.  Any value of buffer size is subject to this eventually.
Simply put, we're trying to parse and decorate an unknown stream of data.  I think it's more likely to succeed if we simply say that stdout/stderr log records are delimited by newlines.  The only other alternative is to take some hints from the container spec itself.  I.e. you could imagine a parameter like logFormat: asciiLines or logFormat: recordSentry, logSentry: "^[IWEF]".  We could argue about API schema laterm but the point is to let the container tell the shim how to extract records from the stream.
Or the shim could have a lua interpreter, and take a blob of lua code :)

I think it's more likely to succeed if we simply say that stdout/stderr log records are delimited by newlines.

How does it work with binary data?
Support for binary data shouldn't be needed for k8s/swarm, but needed for piping stdio of  docker run.
So maybe we should better split the binary logger from the generic logger.
(logFormat: rawBinary?)

I'm personally with @crosbymichael on this one.
Pick a buffer size and log whatever we get out of it. We could first check for \n to split the output into several records although that would slow down the process of logging.
I'm found of considering all the output from containers as binary data since it can really be anything and everything. The timestamp is always going to be off anyway since it would be added by the shim after the output has been emitted by the container.

Should it be split by new line or write() based chunks? For binary data you will never get a new line and have to have extra logic around when to flush. If its based on what we get on the write its much simpler and robust for all types of output.

On the log writer side:
Newline-based with buffer size limit is also acceptable, but chunk-based is preferred, because it's easier and potentially more efficient.
On the log reader side:
As long as the reader understands the logging format and could restore the original container output (e.g. docker logs, kubectl logs), newline-based or chunk-based makes no difference.
However, the problem is that not all log readers understand the format. Users are also using tools like fluentd, firebeat, rsyslog etc. It's more likely that they'll directly parse the log file, because it's too hard to teach them all to understand the format.
In this case, chunk-based logging is too arbitrary for them to parse directly, and newline-based seems to be preferred.
Overall, newline-based logging seems to be a more reasonable solution now, unless we could solve the problem for other logging tools.
/cc @thockin @yujuhong @crassirostris

Is this still relevant today? Right now, the shim writes container stdio back into fifos that can be consumed directly. Chunk-based or newline based should be supported with the current functionality.
I think we could bolster the existing functionality with tools make this more accessible, but it seems like needs can be easily met with the existing feature set.

@stevvooe Today we start a goroutine in cri-containerd to redirect and decorate container output. But actually we still don't know what is the overhead now.
If it turns out the overhead is negligible, I think we are good. If not, we may still need to think about this. But I do agree it's not a priority for now.
Given so, can we keep this issue open for now?

@Random-Liu that’s fine. How can we measure that?


[joy-ui][docs] Double vertical scrollbars

Duplicates

[X] I have searched the existing issues

Related page
https://mui.com/joy-ui/react-autocomplete/
Kind of issue
Other
Issue description
Double vertical scrollbars
Context 🔦
Going to any pages under Components sections on Joy page
I use Edge Version 116.0.1938.54 on linux-x64, the same with Firefox 116.0.3 on linux-x64
Docs version: v5.0.0-beta.4

Could you add a video of the bug that you are describing?

You can go to the attached link and the issue will occur, no need video, btw see the attached file

Hey @sang-au! Are you referring to these scrollbars? Or is it something else? Want to understand if it's something Autocomplete-related, given that was the page you linked, but I'm sensing it's not.

This is expected since content is more than the available area. On MacOS, it's not an issue because scrollbars are hidden by default.
Maybe there might be a similar setting at OS level to hide scrollbars by default.
cc: @danilo-leal

Yup, I'm aware! Wanted to see if that's really what they're referring to because if it is, it's just the docs scrollbars ⎯ not a bug/problem (and not Joy UI-related, too).

I did not see this issue on previous version

Just the issue on the doc page, that show 2 vertical scrollbar on the right side, not related to any component!

@sang-au Got it! Thanks for the clarification! As we mentioned above, I don't think that's a bug/problem ⎯ the two scrollbars are there because one is for the table of contents & the other is for the entire page. Is that getting in your way somehow, causing navigation experience issues?
Let us know if you have any suggestions, too. Otherwise, I think we can close the issue!

I see... my point is: is it an issue? I don't think the table of contents scroll should be tied to the entire page scroll ⎯ having a scrollbar allows you to scroll it independently from the page. If you were expecting just one scrollbar, that would mean that you'd need to go to the bottom of the page to see more TOC content, which is not a great experience. Does that make sense? Were you expecting something else?

Ideas:

We could make the table of contents items a bit denser, there is maybe too much gap between each item.
We could make the table of contents scroll container behave like on macOS: https://github.com/mui/mui-x/issues/510, e.g. https://www.radix-ui.com/primitives/docs/components/dialog
We could split the Autocomplete docs page into more pages in Base UI, and move more content away from Joy UI & Material UI to Base UI: https://github.com/mui/material-ui/issues/37519.

We could move the sponsors back to the main side nav. https://github.com/mui/material-ui/issues/38033#issuecomment-1703075284 using less space in the tocs.

Yup, agreed! Making sure content is well distributed and organized is always positive, and we should do so, but unless the second option there ("...behave like macOS") does do something to the scrollbar (saying that because it's not clear to me what behaving like macOS in this context means exactly), I don't think we'll be able to avoid it. At the end of the day, not sure if it's a problem at all 😬

saying that because it's not clear to me what behaving like macOS in this context means exactly

@danilo-leal illustration added.

Today I see the docs on https://material-web.dev/components/button/
so MUI can apply some thing like bellow


Add JSON support to FromRow derive

Hello :wave:
This PR is a proposal to discuss JSON support for the FromRow derive. The proposal is to add a new json attribute to indicate that a field should be decoded using sqlx::types::Json instead of the field type.
Motivation
The currently existing derive for FromRow allows quick and easy type conversions using TryFrom. This saves us a lot of boilerplate code just for the sake of converting types. Unfortunately TryFrom-based conversions are not enough for json values:
#[derive(FromRow)]
struct Record {
  #[sqlx(try_from = "i64")]
  counter: u64,
  #[sqlx(try_from = "Json<Metadata>")] // <- Does not work
  metadata: Metadata
}

#[derive(serde::Deserialize)]
struct Metadata {
  some: String,
  fields: String.
}

Due to Rust's rules, we can't just add an impl<T> From<Json<T>> for T as that would violate the orphan rules, so at the moment, we are stuck with one of two solutions:

Change the type of the metadata field from Metadata to Json<Metadata>.
Manually implement FromRow.

Neither of these two solutions are ideal IMHO, hence this proposal of adding a new json attribute that will take care of the JSON deserialization and all the necessary type conversions. Using this new attribute, the previous example would become:
#[derive(FromRow)]
struct Record {
    #[sqlx(try_from = "i64")]
    counter: u64,
    #[sqlx(json)] // <- New attribute
    metadata: Metadata
}

#[derive(serde::Deserialize)]
struct Metadata {
    some: String,
    fields: String.
}

Example generated code
The example above would (roughly) expand to:
#[derive(serde::Deserialize)]
struct Metadata {
    some: String,
    fields: String.
}

struct Record {
    counter: u64,
    metadata: Metadata
}

impl<'a, R: sqlx::Row> sqlx::FromRow<'a, R> for Record
where
    &'a str: sqlx::ColumnIndex<R>,
    i64: sqlx::decode::Decode<'a, R::Database>,
    i64: sqlx::types::Type<R::Database>,
    sqlx::types::Json<Metadata>: sqlx::decode::Decode<'a, R::Database>, // <- New bound
    sqlx::types::Json<Metadata>: sqlx::types::Type<R::Database>, // <- New bound
{
    fn from_row(row: &'a R) -> sqlx::Result<Self> {
        // Code generated by `try_from`.
        let counter = row.try_get("counter")
            .and_then(|v| <u64 as ::std::convert::TryFrom::<i64>>::try_from(v)
                .map_err(|e| ::sqlx::Error::ColumnNotFound("FromRow: try_from failed".to_string())
            ))?;

        // NEW: Code generated by json. Uses `try_get` with `sqlx::types::Json` instead of `Metadata`.
        let metadata: Metadata = row.try_get::<sqlx::types::Json<_>, _>("metadata").map(|x| x.0)?;

        Ok(Record {
            counter,
            metadata,
        })
    }
}

Interactions with the already existing attributes

rename and default. They work as before, no interference with json.
flatten. I don't think it makes sense to use both flatten and json on the same field, so this combination is rejected.
try_from. If we have a field#[sqlx(json, try_from = "X")] field: Y, the value will be first deserialized to X and then converted using std::convert::TryFrom to Y.

Would love to see this happen!

@95ulisse Why is wrapping metadata in Json<_> unacceptable? It forwards almost all relevant traits and also implements Deref/DerefMut so you can access the fields of Metadata through it?
I'm wary of having more than one thing to do something, cause that's just more to teach.

Why is wrapping metadata in Json<_> unacceptable?

@abonander It's not unacceptable, it's just a bit inconvenient in some situations. I think of this #[sqlx(json)] as a little helper to make deriving FromRow easier on the same level of #[sqlx(try_from)]. It's not strictly essential, but it's helpful as it avoids writing a bunch of glue code.
Just to keep the example of a generic metadata field, I often find myself writing a model like this one that I keep passing around in my application:
pub struct SomeModel {
    pub id: Uuid,
    pub metadata: HashMap<string, string>,
}

As it is right now, I can't just #[derive(FromRow)] and call it a day. I see three solutions to this:

Wrap that HashMap in Json<_>.
Write my own wrapper and implement Decode and Type manually (deferring to Json<_> internally).
Introduce an intermediate struct SomeModelDb with the same fields but with the map wrapped in Json<_> and then implement From<SomeModelDb> for SomeModel.

And that's why I'm not a huge fan of each of them:

IMHO it just feels wrong to let an sqlx type leak to higher abstraction levels of the application. It's not a matter of ergonomics as Json<_> is almost transparent as you said, but it's more of an encapsulation/isolation concern. HTTP/gRPC/whatever layers should not be aware of sqlx.
That's definitely too much boilerplate to basically just reimplement Json<_>.
This is the route I've been following until now in practice, but it causes a lot of duplication and boilerplate conversions.

Having an #[sqlx(json)] attribute would allow me to sidestep all these problems and have a single model that can be cleanly shared in all layers of the application.
As I said at the beginning, these are all just annoyances, not real blocking problems. If we could find a way to make it work with the existing try_from I'd be perfectly ok with it, but I just couldn't find a solution, so that's why this PR with a new json attribute. You can think of it as a "specialized" form of try_from for JSON data.

After thinking about this more, I will accept this as I want to land something similar for converting to/from types using their FromStr and Display impls, respectively. I agree it would be more convenient than the wrapper type.
@95ulisse do you mind rebasing and fixing the merge conflicts?

@abonander I've rebased the PR and fixed the conflicts. I've also added a bit of docs to the FromRow trait itself to document the new json attribute.


Add an unsafe API to unload process trap handlers

This commit adds a new unsafe API Engine::unload_process_handlers which can be used to de-initialize trap-handling state in a process. In general this is an unsafe operation that we have no means of making safe, hence the unsafe. There are particular situations where this can be done safely though and this is provided for such situations. The safety conditions rely on invariants that Wasmtime itself cannot maintain so the burden is on callers to ensure that this is invoked in a safe manner.
This is inspired by discussion on Zulip where Wasmtime's trap handling infrastructure prevented unloading a DLL with Wasmtime in it. There's possibly other reasons that unloading DLLs are unsafe in Rust but it feels appropriate to at least provide this knob to embedders to be able to turn if they like.

Good suggestions/questions! I've tried to wordsmith and update a bit.


Content overflows on mobile devices

Take a look at the site with the device simulator in your browser's developer tools to see what I mean. The page is really, really messed up.

Sorry, I'm not a front-end web developer (TBH I didn't even know about "the device simulator in your browser's developer tools").  It seems like this is caused by the tables, mostly the results table.  I used bootstrap (with a theme from bootswatch) for everything, so I've added the table-responsive class to the tables, I hope that's a bit better.  If you are a front-end dev, suggestions are welcome as long as it doesn't ruin the experience on larger devices.
Also, if you rotate your phone things should be a lot better.
That said, I don't think this is going to be a very good resource for a phone without a lot of work (if ever). It's simply too much data for a small screen.  It is okay on a tablet.

One thing I played with during development was having the first three columns in the results table with colspan="3", then using one row each for the compression speed, decompression speed, and ratio graphs (progress bars).  If you know how to make that happen responsively, that would probably solve the issue, and I'd be happy to merge it.

If you know how to make that happen responsively, that would probably solve the issue, and I'd be happy to merge it.

Alright, I'll take a look at it!

Actually, I started to do that (by creating two tables, one with hidden-xs, one with visible-xs), but then I remembered the other reason I wanted to get rid of it—it ruined the possibility of sorting by compression speed, decompression speed, or ratio.
Anyways, things actually look pretty decent for me now as long as I orient my phone in landscape mode, but I'm still open to suggestions.

Oh I see something wrong. The class table-responsive applies to a <div> that contains the table - not the table itself.

Fixed—does that help?

Yep.

Excellent.  Thank you very much for figuring this out, it's greatly appreciated.


Revert deprecation warning on json type aliases

This has been causing troubles all around with no actual benefit.

Does this mean that they're not going to be deprecated then? :-)  If so, a release of Yojson master to opam would be appreciated, as the released version still emits them.


Test to verify the 'Attached to VM' field for volume

Create a volume
Verify that 'Attached to VM' field for volume shows 'detached'
Attach the volume to a VM
Verify that 'Attached to VM' field for volume

PR #831


To fix vulnerable dependency SQLitePCLRaw.lib.e_sqlite<IP_ADDRESS>

Hi,
We are developing a project in .net framework WPF application for windows. In that application we have implemented AppCenter to track analytics and diagnostics.
We use three packages for AppCenter implementation,
Microsoft.AppCenter - version 4.3.0
Microsoft.Appcenter.Analytics - version 4.3.0
Microsoft.AppCenter.Crashes - version 4.3.0 .
Some of the dependency packages were also installed along with the AppCenter packages like
SQLitePCLRaw.lib.e_sqlite<IP_ADDRESS>
SQLitePCLRaw.core.2.0.4
SQLitePCLRaw.bundle_green.2.0.4
SQLitePCLRaw.provider.dynamic_cdec<IP_ADDRESS>.
When we try running the OWASP dependency check report for vulnerabilities in our project. We got ten vulnerable dependencies due to these packages (screenshot_1 attached below),
SQLitePCLRaw.lib.e_sqlite3.v110_xp.1.1.14
SQLitePCLRaw.lib.e_sqlite<IP_ADDRESS>

we tried to install the AppCenter packages with Lowest Dependency behavior, which removes SQLitePCLRaw.lib.e_sqlite3.v110_xp.1.1.2 package from the report.
Now it is showing eight vulnerable dependencies due to (screenshot_2 attached below)
SQLitePCLRaw.lib.e_sqlite<IP_ADDRESS>.

Please suggest us how to fix this vulnerability, since AppCenter is not working without this packages.

Hi! Thanks for getting in touch with us!
Could you tell me please where I can find information about this vulnerability? Also, you can leave the report about this issue in SQLitePCLRaw repository directly.

I agree with @beeradmoore, the App Center SDK uses SQLitePCLRaw.bundle_green of version 2.0.2. We don't have any other dependencies which may install the vulnerable sqlite packages from the security reports mentioned above.
@Arivazhagan-s do you have any other dependencies that use SQLitePCLRaw or sqlite3?
Could you try to remove AppCenter SDK dependency from your project and check if the alerts disappear.
You can also try to create an empty project with AppCenter SDK integrated and perform the security check on it.

@DmitriyKirakosyan Only AppCenter uses SQLitePCLRaw.bundle_green in our project. But when we install the SQLitePCLRaw.bundle_green package with Dependency Behaviour option as Highest, It install the some other packages along with it.
Will try create an empty project with AppCenter SDK integrated and perform the security check and let the output know here. Thanks !!!!

@DmitriyKirakosyan I have a created an empty WPF project and integrated AppCenter to it. I have installed the latest version of AppCenter and its dependencies. Still I am getting the same vulnerability list along with some new items.
I am attaching the report here in the command for your reference.
report.zip

Hi @Arivazhagan-s
It does seem like a problem is in the utility you use to check the dependency vulnerabilities.
I'm closing this issue since the one in SQLitePCLRaw was closed.

Hi @DmitriyKirakosyan,
As per the suggestion from SQLitePCLRaw, we have tried updating SQLitePCLRaw to 2.0.5 through NuGet Packages UI. AppCenter integration works fine.
Can you advise on one thing

We tried updating AppCenter4.4.0, but it requires PackageReference format. Packagereference is not compatible with our installer project.
Can we install Appcenter4.3.0 which supports Package.Config format, and update SQLitePCLRaw to 2.0.5 through NuGet Packages UI. Will it lead to any security issue.

Hi @Arivazhagan-s , Yes you can use AppCenter SDK 4.3.0 without any issues. And yes, your approach of updating SQLitePCLRaw Nuget should work.


Fix environment on Windows

See #74

I now found a better solution than https://github.com/jscissr/atom-terminal/commit/44b322f27f626e1f00f221ca13bbca886fac5175.


 I am going to :ship: this as soon as the build gets :green_heart:.
/cc: @atom/feedback @nathansobo

The only failing spec is a flaky one in symbols-view which I have seen fail elsewhere as well (i.e. it doesn't seem related to the changes made in this PR).
Merging this now! :racehorse: :racehorse: :racehorse:


Creation options auto passing empty array breaks Boolean Filter

With the change of #127 empty creation options are now passed as empty arrays rather than NULL to the constructors of services.
This results in a breaking change affecting the Zend\Filter\Boolean.
https://github.com/zendframework/zend-filter/blob/master/src/Boolean.php#L64
Before the PR, NULL would have been passed to the constructor by default, defaulting the "type" value to TYPE_PHP which would do regular PHP-style casts. Now that an empty array is passed instead, it assumes 0 as the type and keeps it there, because there is no 'type' override in the "creation options".
AKA this gets executed:
https://github.com/zendframework/zend-filter/blob/master/src/Boolean.php#L73
https://github.com/zendframework/zend-filter/blob/master/src/Boolean.php#L95
https://github.com/zendframework/zend-filter/blob/master/src/Boolean.php#L104
https://github.com/zendframework/zend-filter/blob/master/src/Boolean.php#L117
Setting the 'type' to 0, and as such everything is casted to TRUE due to 'casting' being TRUE by default
https://github.com/zendframework/zend-filter/blob/master/src/Boolean.php#L289
So even e.g. NULL gets filtered to TRUE

Yes I detect same issue too!
When forms are created automatically by annotation builder, the issue reveals itself.
Thanks amci!

Having this same problem! Thank you amcsi for the fix, hopefully it will be accepted soon.

@amcsi Would it be better to fix the issue in the place where it actually happens? I'd guess the fact that null is suddenly [] seems like it might cause issues in more than just this one place.
That said, I also had issues with only the Boolean filter, so who know.

@Aeolun I actually agree, I just thought that there was some good reason they wanted to make sure that creation options are [] in #127, but if not, then yes it would be better to actually change that. Perhaps ->setCreationOptions(null) would work

@Aeolun I have created this fix here: #159

Found out that i'm having the same issue using the ToNull filter today.

Closing this, because the Service Manager fix #164 has been merged.

Unfortunately by regression from #205, I'm reopening this ticket

Fixed with #210.


Cannot install new themes

I have tried installing the dev theme locally, as well as a custom-made theme using the instructions in the docs, but every time I get this error when trying to set the new theme:
There is no theme in the theme-folder. Please add a theme from https://themes.typemill.net
If I remove the new theme, the error persists. The only way I can solve the issue is to remove the entire typemill directory and starting from scratch.
I have not tried this on a Linux server. This is all tested through my Mac.
PHP version PHP 7.3.11.

I resolved this my commenting out line 37 in Settings.php, which allowed me to view and set the theme. Then I un-commented it and now it seems to work fine. This doesn't seem like a normal part of the workflow though.

Hi Tim, thank you for reporting it, I will have a look into it and optimize the theme handling in the next release...

improvement published with version 1.3.5
The minimum requirement of a new theme is an index.twig-file, so the system looks for it. If there is a theme-folder without that file (and other valid theme), then the system will die with an error.


Adding Notes of Powershell install Script to readme

It might be worth adding a like to the Wiki page in the readme.md and noting that you can install with the Powershell script if the batch scripts fails. I tried the batch script with 2018.2 on Windows 10, and it did not work. The PowerShell script worked beautifully on Windows 10. Let me know if you would like me to submit a PR outlining this, and I can whip something up.

Hi @pgensler - totally failed to reply to this. Yep would be great if you want to improve install instructions.


How to get "STABILITY_KEY" data? Thanks.

How to get "STABILITY_KEY" data? Thanks.

log in to https://beta.dreamstudio.ai, create an account if necessary.
Click on the circular icon in the top right corner to activate a drop down menu
click on "Membership"
click on the "API Key" tab

The text string that begins sk- is your STABILITY_KEY.
Treat this value with the same care as you would treat a password.


Adds console command to remove phone from Customer.io profiles if not subscribed to SMS

What's this PR do?
This pull request adds a northstar:cio-remove-mobile Artisan command that finds all users that have not had promotions muted, have a mobile set, and a null or unsubscribed SMS status. Then, for each user found:

if they are subscribed to email, update their Customer.io profile (which will remove their phone attribute per #1142)
if they are not subscribed, set their promotions_muted_at attribute to trigger deleting their Customer.io profile (per #1124)

This PR also adds a migration to create a compound index to the mobile, promotions_muted_at, and  sms_status fields on our users MongoDB collection to optimize finding the ~1M out of ~11-12M documents we want to update. Because of this migration -- this should not be merged until we're in a good spot to put Northstar into maintenance mode for a deploy.
How should this be reviewed?
👀
Any background context you want to provide?

I left a TODO for fixing the test that asserts muting promotions for each still-subscribed-to-email user for now, not sure why this is falling. When I've tested locally, I've verified the promotions_muted_at field is set correctly.

I think we may want to delete the BackfillCustomerIo job entirely -- as it makes it somewhat easy to accidentally re-add profiles we spent a weekend deleting if someone ran it on production. Left out that deletion for now, but any objections?

Relevant tickets
References Pivotal #177168318.
Checklist

[x] This PR has been added to the relevant Pivotal card.
[ ] Documentation added for new features/changed endpoints.
[x] Added appropriate feature/unit tests.
[ ] If new attributes were added to users, there is a corresponding PR to surface these in Aurora.
[ ] If new attributes were added to users, then the data team already knows about these changes.

I think this is ready for merge... but I want to hold off on doing so until we're ready to go in maintenance mode on production to run the MongoDB migration with its deployment.


Issue with notification icon in header

The notification icon(bell) shows that I still have pending notifications even though I have already checked all the notifications, even after multiple refreshes.

Hey there - is there a purpose to this issue?


Refactor how metrics exporter config file are included in VM image

Instead of adding them late in the build process, when putting together the final VM image, include them in the earlier compute image already. That makes it more convenient to edit the files, and to test them.
https://github.com/neondatabase/cloud/issues/16812

I'll include this change in PR #9090, so closing this as a separate PR.


Is .form-group.col-- valid?

More generally, since form-groups can be rows, need to ensure that row checks apply to form-groups too when applicable.
X-Ref: http://stackoverflow.com/a/26685690/3342739

I wanted to follow up about this and get some clarification about what this bug actually means. Once #250 is done I may be willing to tackle this one next if I understand what needs to be done.

Irrelevant for v4+.


Reorder pages

You can preview this change here:
Built with commit f0b4750aa5d86e06ec247e69e97e147d251bc5d7
https://deploy-preview-1299--govuk-design-system-preview.netlify.app


SQL error with some bootstrap queries

Hi, nice tool ! Juste one bug for me : Bootstrap queries are executed with a preparedstatement (according to this) but one of my init queries works only with a regular Statement (obtained with a createStatement() call).
Caused by: org.jkiss.dbeaver.model.impl.jdbc.JDBCException: SQL Error [2500] [42000]: Syntax error on line 1.  Last symbol read was: 'SET LOCKMODE'. at org.jkiss.dbeaver.model.impl.jdbc.exec.JDBCConnectionImpl.prepareStatement(JDBCConnectionImpl.java:189)
Not sure about how to manage this kind of very specific case. Maybe manage a switch if the query starts with 'SET', 'ALTER', 'MODIFY', or some other session related commands...

This is actually a bug.  Bootstrap queries should be processed with createStatement().
Thanks for noticing.


[BUG] SessionNotCreatedException on Mobile Browser Creation

Before submitting a bug report...

[x] This bug wasn't already reported.
(I have checked every bug report on GitHub)

Title

[x] The title is no longer "[BUG] Title" and I edited it with the right error name.

Describe the bug
SessionNotCreatedException occurs when the mobile browser instance is created on my Mac. Looking at the issue list, this error has been observed periodically on various platforms, but all the issues in the list are currently closed.
This is probably because the same session data is shared between the desktop and mobile webdrivers, the desktop webdriver is not destroyed, and the mobile webdriver is denied access to the session data.
Destroying the webdriver instance seems to be necessary.
Copy and paste your error
2024-06-18 19:13:18,534 [ERROR] SessionNotCreatedException: Message: session not created: cannot connect to chrome at <IP_ADDRESS>:63462
from chrome not reachable

Screenshots
NA
Value of dashboard variable
NA

This was happening to me, I added a sleep between closing the desktop browser and opening the mobile which appears to have fixed the issue in #137. Give it a shot and let me know if it fixes it for you.

This was happening to me, I added a sleep between closing the desktop browser and opening the mobile which appears to have fixed the issue in #137. Give it a shot and let me know if it fixes it for you.

I actually didn't have any luck with this. Quit was working for me to start the mobile searches but would leave hanging processes and close would break it. Sleeping didn't help. Finally got the best of both worlds with this in browser.py. The previous fix of .close and .quit together did not work but for some reason ensuring the process is active before attempting to close anything and then dereferencing it works.  Please let me know if this works for you all. @klept0
    def closeBrowser(self) -> None:
        """Perform actions to close the browser cleanly."""
        # Close the web browser
        if self.webdriver:
            with contextlib.suppress(Exception):
                self.webdriver.close()
            with contextlib.suppress(Exception):
                self.webdriver.quit()
        self.webdriver = None


Automated Package Upgrade

:tada: This PR is included in version 2.0.60 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


CPU mem allocate failure for matrix csr dim greater than 300k

I have many matrix with dim greater than 300k, then i got below failure for ref/OMP constantly
terminate called after throwing an instance of 'gko::AllocationError'
what():  /home/abc/ginkgo-git/core/base/memory.cpp:20: cpu: failed to allocate memory block of<PHONE_NUMBER>776B
I used IndexType long int, ValueType double

Can you please provide some more information? Which matrix format are you using? Can you share your matrix? What is the full backtrace (run gdb ./your_application your parameters and type bt once the exception occurred)? It seems like somewhere an index/offset calculation is running completely out of bounds (this is more storage than would be required for storing the elements in Dense format)

Hi,
It happened in ilu_gmres->apply(b, x);
I attached the matrix, please rename it to xxx.bz2 file
ginkgo1.mtx.bz2.zip

What is your krylov_dim in GMRES?

ahhh, i think i need to just set it same as maxiter
let me try

That definitely works, we allocate a matrix of size num_rows * krylov_dim for storing the Krylov basis vectors, so that may lead to huge storage requirements if you set it to num_rows as well


TextField longpress dialog beyonds SafeArea.

import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: SafeArea(
        child: Scaffold(
          appBar: AppBar(
            title: TextField(),
          ),
          body: Center(
              child: Container(
            width: 100,
            height: 100,
            color: Colors.blue,
          )),
        ),
      ),
    );
  }
}

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.2.1, on Mac OS X 10.14.1 18B75, locale en-CN)
[!] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses
[!] iOS toolchain - develop for iOS devices (Xcode 10.1)
✗ libimobiledevice and ideviceinstaller are not installed. To install with Brew, run:
brew update
brew install --HEAD usbmuxd
brew link usbmuxd
brew install --HEAD libimobiledevice
brew install ideviceinstaller
✗ ios-deploy not installed. To install:
brew install ios-deploy
✗ CocoaPods not installed.
CocoaPods is used to retrieve the iOS platform side's plugin code that responds to your plugin usage on the Dart side.
Without resolving iOS dependencies with CocoaPods, plugins will not work on iOS.
For more info, see https://flutter.io/platform-plugins
To install:
brew install cocoapods
pod setup
[✓] Android Studio (version 3.3)
[!] IntelliJ IDEA Community Edition (version 2018.1.1)
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
[✓] VS Code (version 1.31.1)
[✓] Connected device (1 available)

CC @justinmc

@loongliu Thanks for pointing this out.  The positioning of the selection menu is on my radar as something I'd like to improve asap.  I'm going to close this issue to consolidate with https://github.com/flutter/flutter/issues/3945, but I'll mention this over there so we're sure we get this specific problem of it overlapping the cutout.


Make sure the from date is selected when opening the datepicker

Regression fix. When opening the datepicker dropdown, the "blur" event was triggered so that the selected date was not selected anymore.

Codecov Report

Merging #282 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #282   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files         133    133
  Lines        3019   3019
  Branches      652    652
=====================================
  Hits         3019   3019

Impacted Files
Coverage Δ

src/components/datePicker/DatePicker.tsx
100% <100%> (ø)
:arrow_up:

...ponents/datePicker/DatePickerDropdownConnected.tsx
100% <100%> (ø)
:arrow_up:

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 9d7247c...66574c1. Read the comment docs.


Incorrect sigterm handler causes false netsplits for docker swarm mode

I seems that the sigterm handler for docker swarm does not execute the "vmq-admin cluster leave" command. Thus, whenever the swarm size is reduced (or the swarm code is updated and the IP adresses of the nodes changes), VerneMQ does not realize that the swarm nodes which went offline are not coming back, which causes it to act as if there were a netsplit.
If i look through the code of the "start_vernemq" script, it seems that nodes going offline in a docker swarm used to be handled correctly, but then there was some code refactoring, and now I think it only works for Kubernetes clusters.
If believe the bug was introduced in this commit:
https://github.com/vernemq/docker-vernemq/commit/da6c60893853c8c68f58ac4473d75b8d4ceb0740
Thank you for looking at this issue!

@Pistro Thanks for reporting. Breaking Swarm compatibility certainly wasn't the idea... will look into it.


Problems in training stage

Hello,
I'm trying to train the model, and I'm having some errors.
I listed each of the tests I ran, the commands that were run on each one, and the output from these.
I'm running each test in a clean environment, on a Google Colab notebook.
1:
> git clone https://github.com/likyoo/open-cd.git
> cd open-cd
> pip install -v -e .
> python3 tools/train.py configs/changer/changer_ex_r18_512x512_40k_levircd.py --work-dir ./changer_r18_levir_workdir --gpu-id 0 --seed 307
Traceback (most recent call last):
File "/content/tools/train.py", line 10, in <module> import mmcv
ModuleNotFoundError: No module named 'mmcv'

2:
> git clone https://github.com/likyoo/open-cd.git
> cd open-cd
> pip install -v -e .
> cat /requirements/mminstall.txt
mmcls>=0.20.1
mmcv-full>=1.5.0,<=1.7.0

> pip install -r ./requirements/mminstall.txt
> python3 tools/train.py  configs/changer/changer_ex_r18_512x512_40k_levircd.py --work-dir ./changer_r18_levir_workdir --gpu-id 0 --seed 307
AssertionError: MMCV==1.7.0 is used but incompatible. Please install mmcv>=2.0.0rc4.

3:
> git clone https://github.com/likyoo/open-cd.git
> cd open-cd
> pip install -v -e .
> pip install mmcv==2.0.0rc4
> python3 tools/train.py  configs/changer/changer_ex_r18_512x512_40k_levircd.py --work-dir ./changer_r18_levir_workdir --gpu-id 0 --seed 307
Traceback (most recent call last):
File "/content/tools/train.py", line 13, in <module> from mmcv.cnn.utils import revert_sync_batchnorm
ImportError: cannot import name 'revert_sync_batchnorm' from 'mmcv.cnn.utils' (/usr/local/lib/python3.9/dist-packages/mmcv/cnn/utils/__init__.py)

4:
> git clone https://github.com/likyoo/open-cd.git
> cd open-cd
> pip install -v -e .
> pip install mmcv
> python3 tools/train.py  configs/changer/changer_ex_r18_512x512_40k_levircd.py --work-dir ./changer_r18_levir_workdir --gpu-id 0 --seed 307
Traceback (most recent call last):
File "/content/tools/train.py", line 13, in <module> from mmcv.cnn.utils import revert_sync_batchnorm
ImportError: cannot import name 'revert_sync_batchnorm' from 'mmcv.cnn.utils' (/usr/local/lib/python3.9/dist-packages/mmcv/cnn/utils/__init__.py)

I would appreciate any help!
Greetings!

I forgot to look at the reference to open-mmlab/mmsegmentation.
I will try to solve it using the documentation of that repository!
Sorry


Update the footer to enable opening links in a new tab

I Observed that when clicked on social media links which are after the subscribe part upon clicking open in the same tab as the active tab...
I wanted to make all these links open in new tab as that would ease out and will be convenient to use the site after following up on socials rather than user has to go to previous tab to get back to the site.

Also would love to update this

pls let me know about the same ☝🏼 @kaal-coder

@tmsagarofficial you are good to go. All the best.

@tmsagarofficial please complete the issues assigned to you ASAP, else I have to transfer it to someone else.

Will do it by EOD @kaal-coder

Great @tmsagarofficial. I hope you do all the 3 assigned issues by EOD.
Make sure you keep the branch updated while making a PR. And share a preview of the changes made in the form of a screenshot/video.

Yeah


[Bug]: GPU for Image embedding

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
I want to extract emb from images as there are many images I want to use GPU, but I'm unable to use GPU in colab.
dc = (towhee.glob('/path/to/folder/*')
.image_decode()
.image_embedding.timm(model_name='resnet50')
.to_list()
)
How can I use GPU?
Expected Behavior
No response
Steps To Reproduce
No response
Environment
- Towhee version(e.g. v0.1.3 or 8b23a93):
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:

Anything else?
No response

@jaelgu
Could you help to answer this question? Thanks.