Show storage stats in settings

In Settings -> Debug -> can add a Statistics option. Tapping on it could show data such as current disk space in use, blocks downloaded, peers connected, any other stats available.

Resolved in https://github.com/planetdecred/dcrandroid/pull/440


Terminals/profiles/icon only supports codicon

Testing #127194
In the package.json I am only allowed to define an icon via codicons, not as path. We should as this aligns it with commands/icon and the vscode.d.ts definition of icons

definition of command icons: https://github.com/microsoft/vscode/blob/9510b91e7e6645d2ad72f92af00e8ee7a7178e13/src/vs/workbench/api/common/menusExtensionPoint.ts#L545-L563

Let's push this as it's a little too involved than we're comfortable with at this stage in endgame.

This doesn't seem to work a configuration like this

I'll reopen this issue because

Even with a codicon, though the icon shows up in the quickpick, it doesn't show up in the terminal editor tab (my terminals are being created in the editor area). Instead, it shows a rounded rectangle with a > symbol inside.
PNG icons aren't showing up in the quickpick. After selecting that profile, I get the same icon as in point 1 in the terminal editor tab.

We haven't gotten any requests for supporting this, thus closing as I don't think we'll get to it.


Remove incorrect flag for cmdlet

"CacheSummary" was never added as a flag (may have been a left over in an old spec)

(ref. #5620)


 The same happend if I try to build a xarray.Dataset and then unstack the multiindex as shown below:
ds = xr.Dataset(df)
ds.unstack('dim_0')
<xarray.Dataset>
Dimensions:       (lat: 5, lon: 5, time: 1)
Coordinates:
  * lat           (lat) float64 34.51 34.52 34.52 34.52 34.52
  * lon           (lon) float64 16.47 16.72 16.85 16.98 17.11
  * time          (time) object '1971-01-10 12:00:00'
Data variables:
    wind_surface  (lat, lon, time) float32 29.658546 nan nan ... nan 32.724174
    hurs          (lat, lon, time) float32 70.48129 nan nan ... nan nan 72.10611
    precip        (lat, lon, time) float32 0.0 nan nan nan ... nan nan nan 0.0

Maybe it's not an issue. I don't know. I'm lost. Any help is welcome.
 This typically happens if your DataFrame does not contain a row for every combination of Dataset coordinates, for whatever reason.

I know what "NaN" means. I was hoping that by transforming the dataset into a dataframe and then returning back, the dataset variables would recover its original shape.

You will need to share a full example in order for me to explain why it
works that way
On Wed, Jun 12, 2019 at 7:36 AM santianmen<EMAIL_ADDRESS>wrote:

I know what "NaN" means. I was hoping that by transforming the dataset
into a dataframe and then returning back, the dataset variables would
recover its original shape.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pydata/xarray/issues/3007?email_source=notifications&email_token=AAJJFVUBDLFYNW2KB26SNQTP2ECX3A5CNFSM4HWRYQZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXQUM2Q#issuecomment-501302890,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJJFVVIXVCD6GUVFRIBEPDP2ECX3ANCNFSM4HWRYQZA
.

I recently had a similar issue and found out the cause: When transforming from a dataframe to an xarray, the xarray allocates memory for all possible combinations of the coordinates. In this particular case, you have 5 unique values for latitude and longitude in your five rows, which means there are 5*5=25 possible combinations of lat/long values. All missing values are then filled in as NaN.
Let me illustrate by recreating just your data on latitude, longitude, wind_surface and hurs:
In [3]: data = [
    ...:     [34.511383, 16.467664, 29.658546, 70.481293],
    ...:     [34.515558, 16.723973, 30.896049, 71.356644],
    ...:     [34.517359, 16.852138, 31.514799, 71.708603],
    ...:     [34.518970, 16.980310, 32.105423, 72.023773],
    ...:     [34.520391, 17.108487, 32.724174, 72.106110],
    ...: ]
In [4]: df = pd.DataFrame(data=data, columns=['lat', 'long', 'wind_surface', 'hurs']).set_index(['lat', 'long'])
In [5]: df
Out[5]:
                     wind_surface       hurs
lat       long
34.511383 16.467664     29.658546  70.481293
34.515558 16.723973     30.896049  71.356644
34.517359 16.852138     31.514799  71.708603
34.518970 16.980310     32.105423  72.023773
34.520391 17.108487     32.724174  72.106110

But for the xarray, this means it will end up creating a 5x5 array, of which only 5 values are given along the diagonal. This is very clearly visible when showing just the DataArray for a single column:
In [6]: df.to_xarray()['wind_surface']
Out[6]:
<xarray.DataArray 'wind_surface' (lat: 5, long: 5)>
array([[29.658546,       nan,       nan,       nan,       nan],
       [      nan, 30.896049,       nan,       nan,       nan],
       [      nan,       nan, 31.514799,       nan,       nan],
       [      nan,       nan,       nan, 32.105423,       nan],
       [      nan,       nan,       nan,       nan, 32.724174]])
Coordinates:
  * lat      (lat) float64 34.51 34.52 34.52 34.52 34.52
  * long     (long) float64 16.47 16.72 16.85 16.98 17.11

However, as to_xarray() outputs a DataSet, each DataArray, i.e. column from the dataframe, is summarized as a 1D array, which makes it seem like a lot of data is just 'missing':
In [7]: df.to_xarray()
Out[7]:
<xarray.Dataset>
Dimensions:       (lat: 5, long: 5)
Coordinates:
  * lat           (lat) float64 34.51 34.52 34.52 34.52 34.52
  * long          (long) float64 16.47 16.72 16.85 16.98 17.11
Data variables:
    wind_surface  (lat, long) float64 29.66 nan nan nan ... nan nan nan 32.72
    hurs          (lat, long) float64 70.48 nan nan nan ... nan nan nan 72.11

So it works as intended, but can throw you for a loop if you don't realize it's creating an array the size of all possible index combinations.
@shoyer can you close this issue?

Thanks @sjvrijn


Feature/play pause stop step/86bx9ub1x

-Finished Timer Panel with FPS Histogram and other Timer data
-Camera input not dependant on framerate
-Play/Pause/Stop/Step work properly and Timer Panel interacts well with them. Also the buttons only can be pressed if it makes sense to press them (depending on the game state)
-Modified Module::Update() (also pre and post) to Module::Update(float dt) to pass the delta time from the application in case it's needed.

@MarcGabernet remember to comment back the comments that you resolve, else resolve them yourself so we can be aware that you resolved them, thanks!


✅ Table fails at automatic generated sparql-queries

Describe the bug
The automatic generated sparql-query for tables seems to be  broken or not updated. (does not work).
To Reproduce Steps to reproduce the behavior:

Go to '... '
Click on 'choose table view' The table loads.
Click on generate sparql query'
table does not load -> timeout.

Expected behavior I would expect the table to load. probably also a #pragma off and a "select distinct" at the beginning.
Environment (please complete the following information): PROD
@Rdataflow  @l00mi

federal chancellery wants to use this feature more extensively.
Also relevant for distribution of Schwermetalbelastung.

Thanks for reporting @CDiGallo I was able to reproduce the bug with the dataset: "Bodenbelastung durch Schwermetalle
"
Screenshot of the timeout on LINDAS to support with investigating

@CDiGallo the fix is ready for review on INT.
I tested with the following charts and in all cases the SPARQL query loaded in the editing mode.

https://int.visualize.admin.ch/v/9gnYPJJwFugh?dataSource=Prod
https://int.visualize.admin.ch/v/rcI7YTuBKDPT?dataSource=Prod

@sosiology  Thank you very muc!
@https://github.com/l00mi
@l00mi
Does this fix your problem in general?


PR855 support (v4010)

This PR adds support for Purchase Order Acknowledgment. I added 2 fixtures, but they are not used by the tests at the moment.
@irobayna you can have a look.
Thanks!

@samueltc Thank you, sorry for the delay


🐛 [firebase_storage] Swift Compiler Error (Xcode): Value of optional type StorageProvider must be unwrapped

Bug report
Describe the bug
Xcode build error on Flutter project
Swift Compiler Error (Xcode): Value of optional type '(any StorageProvider)?' must be unwrapped to refer to member 'storage' of wrapped base type 'any StorageProvider'
and
Swift Compiler Error (Xcode): Cannot assign value of type '(any AuthInterop)?' to type 'any AuthInterop'
Here is the build output of Android Studio,
Launching lib/main.dart on iPhone 15 Pro Max in debug mode...
Running pod install...
Running Xcode build...
Xcode build done.                                           47.4s
Failed to build iOS app
Swift Compiler Error (Xcode): Value of optional type '(any StorageProvider)?' must be unwrapped to refer to member 'storage' of wrapped base type 'any StorageProvider'
/StudioProjects/storage_bugs/ios/Pods/FirebaseStorage/FirebaseStorage/Sources/Storage.swift:72:11

Swift Compiler Error (Xcode): Value of optional type '(any StorageProvider)?' must be unwrapped to refer to member 'storage' of wrapped base type 'any StorageProvider'
/StudioProjects/storage_bugs/ios/Pods/FirebaseStorage/FirebaseStorage/Sources/Storage.swift:87:11

Swift Compiler Error (Xcode): Cannot assign value of type '(any AuthInterop)?' to type 'any AuthInterop'
/StudioProjects/storage_bugs/ios/Pods/FirebaseStorage/FirebaseStorage/Sources/Storage.swift:290:38

Swift Compiler Error (Xcode): Cannot assign value of type '(any AppCheckInterop)?' to type 'any AppCheckInterop'
/StudioProjects/storage_bugs/ios/Pods/FirebaseStorage/FirebaseStorage/Sources/Storage.swift:292:46

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

Could not build the application for the simulator.
Error launching application on iPhone 15 Pro Max.

Steps to reproduce
Steps to reproduce the behavior:
Run the sample project
OR,

Create a new Flutter project
Copy paste the pubspec.yaml from the sample project to the new project
Go to ios/Podfile and use, platform :ios, '13.0'
Build the project to run on any iOS simulator

Expected behavior
Expected to run the project successfully on the iOS simulator
Sample project
https://github.com/tausiq/storage_bugs

Additional context
Add any other context about the problem here.

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.19.2, on macOS 14.3.1 23D60 darwin-arm64, locale en-CA)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.2)
[✓] IntelliJ IDEA Ultimate Edition (version 2023.3.4)
[✓] VS Code (version 1.87.0)
[✓] Connected device (3 available)
[✓] Network resources

• No issues found!

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 3.3.0
Flutter SDK 3.19.2
storage_bugs 1.0.0+1

dependencies:
- about 2.1.3 [flutter flutter_markdown markdown path simple_mustache url_launcher]
- another_stepper 1.2.2 [flutter]
- avatar_glow 3.0.1 [flutter]
- cached_network_image 3.3.1 [cached_network_image_platform_interface cached_network_image_web flutter flutter_cache_manager octo_image]
- cloud_firestore 4.15.6 [cloud_firestore_platform_interface cloud_firestore_web collection firebase_core firebase_core_platform_interface flutter meta]
- cloud_functions 4.6.6 [cloud_functions_platform_interface cloud_functions_web firebase_core firebase_core_platform_interface flutter]
- comment_tree 0.3.0 [flutter provider]
- custom_navigation_bar 0.8.2 [flutter]
- date_picker_timeline 1.2.5 [flutter intl]
- date_time_format 2.0.1
- enum_to_string 2.0.1
- equatable 2.0.5 [collection meta]
- faker 2.1.0 [crypto]
- favorite_button 0.0.4 [flutter]
- feedback 3.0.1 [flutter flutter_localizations]
- feedback_sentry 3.0.0 [flutter feedback sentry]
- firebase_analytics 10.8.7 [firebase_analytics_platform_interface firebase_analytics_web firebase_core firebase_core_platform_interface flutter]
- firebase_auth 4.17.6 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 2.25.5 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_crashlytics 3.4.16 [firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface flutter stack_trace]
- firebase_database 10.4.7 [firebase_core firebase_core_platform_interface firebase_database_platform_interface firebase_database_web flutter]
- firebase_messaging 14.7.17 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
- firebase_remote_config 4.3.15 [firebase_core firebase_core_platform_interface firebase_remote_config_platform_interface firebase_remote_config_web flutter]
- firebase_storage 11.6.7 [firebase_core firebase_core_platform_interface firebase_storage_platform_interface firebase_storage_web flutter]
- flex_color_scheme 7.3.1 [flex_seed_scheme flutter meta]
- flutter 0.0.0 [characters collection material_color_utilities meta vector_math sky_engine]
- flutter_cache 0.1.0 [flutter shared_preferences]
- flutter_chat_types 3.6.2 [equatable json_annotation meta]
- flutter_chat_ui 1.6.12 [diffutil_dart equatable flutter flutter_chat_types flutter_link_previewer flutter_parsed_text intl meta photo_view scroll_to_index url_launcher visibility_detector]
- flutter_datetime_picker_plus 2.1.0 [flutter]
- flutter_dotenv 5.1.0 [flutter]
- flutter_firebase_chat_core 1.6.7 [cloud_firestore firebase_auth firebase_core flutter flutter_chat_types meta]
- flutter_image_compress 2.1.0 [flutter flutter_image_compress_platform_interface flutter_image_compress_common flutter_image_compress_web flutter_image_compress_macos]
- flutter_local_notifications 16.3.2 [clock flutter flutter_local_notifications_linux flutter_local_notifications_platform_interface timezone]
- flutter_markdown 0.6.20+1 [flutter markdown meta path]
- flutter_multi_formatter 2.12.4 [flutter collection base58check bech32]
- flutter_polyline_points 2.0.0 [flutter http]
- flutter_rating_bar 4.0.1 [flutter]
- flutter_slidable 3.0.1 [flutter]
- flutter_stripe 10.1.0 [flutter meta stripe_android stripe_ios stripe_platform_interface]
- flutter_svg 2.0.10+1 [flutter http vector_graphics vector_graphics_codec vector_graphics_compiler]
- geocoding 2.2.0 [flutter geocoding_platform_interface geocoding_android geocoding_ios]
- geoflutterfire2 2.3.15 [flutter cloud_firestore rxdart]
- geolocator 11.0.0 [flutter geolocator_platform_interface geolocator_android geolocator_apple geolocator_web geolocator_windows]
- get 4.6.6 [flutter]
- get_storage 2.1.1 [flutter get path_provider]
- google_fonts 6.2.1 [flutter http path_provider crypto]
- google_maps_flutter 2.5.3 [flutter google_maps_flutter_android google_maps_flutter_ios google_maps_flutter_platform_interface google_maps_flutter_web]
- google_sign_in 6.2.1 [flutter google_sign_in_android google_sign_in_ios google_sign_in_platform_interface google_sign_in_web]
- grouped_list 5.1.2 [flutter]
- http 1.2.0 [async http_parser meta web]
- iconify_flutter_plus 1.0.3 [flutter flutter_svg]
- image 4.1.7 [archive meta xml]
- image_picker 1.0.7 [flutter image_picker_android image_picker_for_web image_picker_ios image_picker_linux image_picker_macos image_picker_platform_interface image_picker_windows]
- intl 0.18.1 [clock meta path]
- location 5.0.3 [flutter location_platform_interface location_web]
- logger 2.1.0
- lottie 3.1.0 [archive flutter http path vector_math]
- material_segmented_control 5.0.0 [flutter]
- mime 1.0.5
- mocktail 1.0.3 [collection matcher test_api]
- package_info_plus 5.0.1 [ffi flutter flutter_web_plugins http meta path package_info_plus_platform_interface web win32]
- path 1.9.0
- path_provider 2.1.2 [flutter path_provider_android path_provider_foundation path_provider_linux path_provider_platform_interface path_provider_windows]
- percent_indicator 4.2.3 [flutter]
- permission_handler 11.3.0 [flutter meta permission_handler_android permission_handler_apple permission_handler_html permission_handler_windows permission_handler_platform_interface]
- photo_view 0.14.0 [flutter]
- pull_to_refresh 2.0.0 [flutter]
- retry 3.1.2
- rxdart 0.27.7
- sentry_flutter 7.16.1 [flutter flutter_web_plugins sentry package_info_plus meta ffi]
- share_plus 7.2.2 [cross_file meta mime flutter flutter_web_plugins share_plus_platform_interface file url_launcher_web url_launcher_windows url_launcher_linux url_launcher_platform_interface ffi win32]
- sign_in_with_apple 5.0.0 [flutter meta sign_in_with_apple_platform_interface sign_in_with_apple_web]
- smooth_page_indicator 1.1.0 [flutter]
- solid_bottom_sheet 0.1.10 [flutter]
- stack_trace 1.11.1 [path]
- timeago 3.6.1 [intl]
- tuple 2.0.2
- uni_links 0.5.1 [flutter uni_links_platform_interface uni_links_web]
- url_launcher 6.2.5 [flutter url_launcher_android url_launcher_ios url_launcher_linux url_launcher_macos url_launcher_platform_interface url_launcher_web url_launcher_windows]
- uuid 4.3.3 [crypto sprintf meta fixnum]

dev dependencies:
- csv 5.1.1
- dart_code_metrics_presets 2.9.0
- flutter_lints 3.0.1 [lints]
- flutter_test 0.0.0 [flutter test_api matcher path fake_async clock stack_trace vector_math leak_tracker_flutter_testing async boolean_selector characters collection leak_tracker leak_tracker_testing material_color_utilities meta source_span stream_channel string_scanner term_glyph vm_service]

transitive dependencies:
- _flutterfire_internals 1.3.23 [collection firebase_core firebase_core_platform_interface flutter meta]
- archive 3.4.10 [crypto path pointycastle]
- args 2.4.2
- async 2.11.0 [collection meta]
- base58check 2.0.0 [crypto collection]
- bech32 0.2.2 [convert]
- boolean_selector 2.1.1 [source_span string_scanner]
- cached_network_image_platform_interface 4.0.0 [flutter flutter_cache_manager]
- cached_network_image_web 1.1.1 [cached_network_image_platform_interface flutter flutter_cache_manager]
- characters 1.3.0
- clock 1.1.1
- cloud_firestore_platform_interface 6.1.7 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- cloud_firestore_web 3.10.6 [_flutterfire_internals cloud_firestore_platform_interface collection firebase_core firebase_core_web flutter flutter_web_plugins js]
- cloud_functions_platform_interface 5.5.17 [firebase_core flutter meta plugin_platform_interface]
- cloud_functions_web 4.7.0 [cloud_functions_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js web]
- collection 1.18.0
- convert 3.1.1 [typed_data]
- cross_file 0.3.3+8 [meta web]
- crypto 3.0.3 [typed_data]
- csslib 1.0.0 [source_span]
- dbus 0.7.10 [args ffi meta xml]
- diffutil_dart 3.0.0
- fake_async 1.3.1 [clock collection]
- ffi 2.1.2
- file 7.0.0 [meta path]
- file_selector_linux 0.9.2+1 [cross_file file_selector_platform_interface flutter]
- file_selector_macos 0.9.3+3 [cross_file file_selector_platform_interface flutter]
- file_selector_platform_interface 2.6.2 [cross_file flutter http plugin_platform_interface]
- file_selector_windows 0.9.3+1 [cross_file file_selector_platform_interface flutter]
- firebase_analytics_platform_interface 3.9.7 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_analytics_web 0.5.5+19 [_flutterfire_internals firebase_analytics_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- firebase_auth_platform_interface 7.1.6 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 5.9.6 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser js meta web]
- firebase_core_platform_interface 5.0.0 [collection flutter flutter_test meta plugin_platform_interface]
- firebase_core_web 2.11.5 [firebase_core_platform_interface flutter flutter_web_plugins js meta web]
- firebase_crashlytics_platform_interface 3.6.23 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_database_platform_interface 0.2.5+23 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_database_web 0.2.3+23 [firebase_core firebase_core_web firebase_database_platform_interface flutter flutter_web_plugins js]
- firebase_messaging_platform_interface 4.5.25 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_web 3.6.6 [_flutterfire_internals firebase_core firebase_core_web firebase_messaging_platform_interface flutter flutter_web_plugins js meta web]
- firebase_remote_config_platform_interface 1.4.23 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_remote_config_web 1.4.23 [firebase_core firebase_core_web firebase_remote_config_platform_interface flutter flutter_web_plugins js]
- firebase_storage_platform_interface 5.1.10 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_storage_web 3.7.1 [_flutterfire_internals async firebase_core firebase_core_web firebase_storage_platform_interface flutter flutter_web_plugins http js meta web]
- fixnum 1.1.0
- flex_seed_scheme 1.4.0 [collection flutter meta]
- flutter_cache_manager 3.3.1 [clock collection file flutter http path path_provider rxdart sqflite uuid]
- flutter_image_compress_common 1.0.3 [flutter flutter_image_compress_platform_interface]
- flutter_image_compress_macos 1.0.1 [flutter flutter_image_compress_platform_interface]
- flutter_image_compress_platform_interface 1.0.3 [flutter plugin_platform_interface cross_file]
- flutter_image_compress_web 0.1.3+2 [flutter flutter_web_plugins flutter_image_compress_platform_interface js]
- flutter_link_previewer 3.2.2 [flutter flutter_chat_types flutter_linkify html http linkify meta url_launcher]
- flutter_linkify 6.0.0 [flutter linkify]
- flutter_local_notifications_linux 4.0.0+1 [dbus ffi flutter flutter_local_notifications_platform_interface path xdg_directories]
- flutter_local_notifications_platform_interface 7.0.0+1 [flutter plugin_platform_interface]
- flutter_localizations 0.0.0 [flutter intl characters clock collection material_color_utilities meta path vector_math]
- flutter_parsed_text 2.2.1 [flutter]
- flutter_plugin_android_lifecycle 2.0.17 [flutter]
- flutter_web_plugins 0.0.0 [flutter characters collection material_color_utilities meta vector_math]
- freezed_annotation 2.4.1 [collection json_annotation meta]
- geocoding_android 3.2.0 [flutter geocoding_platform_interface]
- geocoding_ios 2.3.0 [flutter geocoding_platform_interface]
- geocoding_platform_interface 3.2.0 [flutter meta plugin_platform_interface]
- geolocator_android 4.5.2 [flutter geolocator_platform_interface meta uuid]
- geolocator_apple 2.3.6 [flutter geolocator_platform_interface]
- geolocator_platform_interface 4.2.2 [flutter plugin_platform_interface vector_math meta]
- geolocator_web 3.0.0 [flutter flutter_web_plugins geolocator_platform_interface]
- geolocator_windows 0.2.2 [flutter geolocator_platform_interface]
- google_identity_services_web 0.3.0+2 [meta web]
- google_maps 6.3.0 [js js_wrapping meta]
- google_maps_flutter_android 2.7.0 [flutter flutter_plugin_android_lifecycle google_maps_flutter_platform_interface stream_transform]
- google_maps_flutter_ios 2.5.0 [flutter google_maps_flutter_platform_interface stream_transform]
- google_maps_flutter_platform_interface 2.6.0 [collection flutter plugin_platform_interface stream_transform]
- google_maps_flutter_web 0.5.4+3 [collection flutter flutter_web_plugins google_maps google_maps_flutter_platform_interface sanitize_html stream_transform]
- google_sign_in_android 6.1.21 [flutter google_sign_in_platform_interface]
- google_sign_in_ios 5.7.4 [flutter google_sign_in_platform_interface]
- google_sign_in_platform_interface 2.4.5 [flutter plugin_platform_interface]
- google_sign_in_web 0.12.3+3 [flutter flutter_web_plugins google_identity_services_web google_sign_in_platform_interface http web]
- html 0.15.4 [csslib source_span]
- http_parser 4.0.2 [collection source_span string_scanner typed_data]
- image_picker_android 0.8.9+3 [flutter flutter_plugin_android_lifecycle image_picker_platform_interface]
- image_picker_for_web 3.0.2 [flutter flutter_web_plugins image_picker_platform_interface mime]
- image_picker_ios 0.8.9+1 [flutter image_picker_platform_interface]
- image_picker_linux 0.2.1+1 [file_selector_linux file_selector_platform_interface flutter image_picker_platform_interface]
- image_picker_macos 0.2.1+1 [file_selector_macos file_selector_platform_interface flutter image_picker_platform_interface]
- image_picker_platform_interface 2.9.4 [cross_file flutter http plugin_platform_interface]
- image_picker_windows 0.2.1+1 [file_selector_platform_interface file_selector_windows flutter image_picker_platform_interface]
- js 0.6.7 [meta]
- js_wrapping 0.7.4 [js]
- json_annotation 4.8.1 [meta]
- leak_tracker 10.0.0 [clock collection meta path vm_service]
- leak_tracker_flutter_testing 2.0.1 [flutter leak_tracker leak_tracker_testing matcher meta]
- leak_tracker_testing 2.0.1 [leak_tracker matcher meta]
- linkify 5.0.0
- lints 3.0.0
- location_platform_interface 3.1.2 [flutter plugin_platform_interface]
- location_web 4.2.0 [flutter flutter_web_plugins http_parser js location_platform_interface]
- logging 1.2.0
- markdown 7.2.1 [args meta]
- matcher 0.12.16+1 [async meta stack_trace term_glyph test_api]
- material_color_utilities 0.8.0 [collection]
- meta 1.11.0
- nested 1.0.0 [flutter]
- octo_image 2.0.0 [flutter]
- package_info_plus_platform_interface 2.0.1 [flutter meta plugin_platform_interface]
- path_parsing 1.0.1 [vector_math meta]
- path_provider_android 2.2.2 [flutter path_provider_platform_interface]
- path_provider_foundation 2.3.2 [flutter path_provider_platform_interface]
- path_provider_linux 2.2.1 [ffi flutter path path_provider_platform_interface xdg_directories]
- path_provider_platform_interface 2.1.2 [flutter platform plugin_platform_interface]
- path_provider_windows 2.2.1 [ffi flutter path path_provider_platform_interface win32]
- permission_handler_android 12.0.5 [flutter permission_handler_platform_interface]
- permission_handler_apple 9.4.0 [flutter permission_handler_platform_interface]
- permission_handler_html 0.1.1 [flutter flutter_web_plugins permission_handler_platform_interface]
- permission_handler_platform_interface 4.2.0 [flutter meta plugin_platform_interface]
- permission_handler_windows 0.2.1 [flutter permission_handler_platform_interface]
- petitparser 6.0.2 [meta]
- platform 3.1.4
- plugin_platform_interface 2.1.8 [meta]
- pointycastle 3.7.4 [collection convert js]
- provider 6.1.2 [collection flutter nested]
- sanitize_html 2.1.0 [html meta]
- scroll_to_index 3.0.1 [flutter]
- sentry 7.16.1 [http meta stack_trace uuid]
- share_plus_platform_interface 3.3.1 [cross_file flutter meta mime plugin_platform_interface path_provider uuid]
- shared_preferences 2.2.2 [flutter shared_preferences_android shared_preferences_foundation shared_preferences_linux shared_preferences_platform_interface shared_preferences_web shared_preferences_windows]
- shared_preferences_android 2.2.1 [flutter shared_preferences_platform_interface]
- shared_preferences_foundation 2.3.5 [flutter shared_preferences_platform_interface]
- shared_preferences_linux 2.3.2 [file flutter path path_provider_linux path_provider_platform_interface shared_preferences_platform_interface]
- shared_preferences_platform_interface 2.3.2 [flutter plugin_platform_interface]
- shared_preferences_web 2.2.2 [flutter flutter_web_plugins shared_preferences_platform_interface web]
- shared_preferences_windows 2.3.2 [file flutter path path_provider_platform_interface path_provider_windows shared_preferences_platform_interface]
- sign_in_with_apple_platform_interface 1.0.0 [flutter plugin_platform_interface meta]
- sign_in_with_apple_web 1.0.1 [flutter flutter_web_plugins sign_in_with_apple_platform_interface js]
- simple_mustache 2.1.0 [logging]
- sky_engine 0.0.99
- source_span 1.10.0 [collection path term_glyph]
- sprintf 7.0.0
- sqflite 2.3.2 [flutter sqflite_common path]
- sqflite_common 2.5.3 [synchronized path meta]
- stream_channel 2.1.2 [async]
- stream_transform 2.1.0
- string_scanner 1.2.0 [source_span]
- stripe_android 10.1.0 [flutter]
- stripe_ios 10.1.0 [flutter]
- stripe_platform_interface 10.1.0 [flutter freezed_annotation json_annotation meta plugin_platform_interface]
- synchronized 3.1.0+1
- term_glyph 1.2.1
- test_api 0.6.1 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph]
- timezone 0.9.2 [path]
- typed_data 1.3.2 [collection]
- uni_links_platform_interface 1.0.0 [flutter plugin_platform_interface]
- uni_links_web 0.1.0 [flutter flutter_web_plugins uni_links_platform_interface]
- url_launcher_android 6.3.0 [flutter url_launcher_platform_interface]
- url_launcher_ios 6.2.5 [flutter url_launcher_platform_interface]
- url_launcher_linux 3.1.1 [flutter url_launcher_platform_interface]
- url_launcher_macos 3.1.0 [flutter url_launcher_platform_interface]
- url_launcher_platform_interface 2.3.2 [flutter plugin_platform_interface]
- url_launcher_web 2.2.3 [flutter flutter_web_plugins url_launcher_platform_interface web]
- url_launcher_windows 3.1.1 [flutter url_launcher_platform_interface]
- vector_graphics 1.1.11+1 [flutter http vector_graphics_codec]
- vector_graphics_codec 1.1.11+1
- vector_graphics_compiler 1.1.11+1 [args meta path_parsing xml vector_graphics_codec path]
- vector_math 2.1.4
- visibility_detector 0.4.0+2 [flutter]
- vm_service 13.0.0
- web 0.4.2
- win32 5.2.0 [ffi]
- xdg_directories 1.0.4 [meta path]
- xml 6.5.0 [collection meta petitparser]

Having the same issue here.

+1

+1

Hey folks. Sorry to hear about this problem. The team will triage and get to this as soon as possible.
If you are affected by this issue, leave a 👍 in the original comment. Please only add additional comments if you have new to information about the issue.

Perhaps it's related to the latest firebase-ios-sdk 10.22.0?
If I manually override the FirebaseSDKVersion in my Podfile I'm able to build the project.
# Override Firebase SDK Version
$FirebaseSDKVersion = '10.22.0'

+1

Same issue deploying from Flutterflow.
Flutterflow V 4.1
Flutter 3.13.7
Failed to build iOS app Swift Compiler Error (Xcode): Value of optional type '(any StorageProvider)?' must be unwrapped to refer to member 'storage' of wrapped base type 'any StorageProvider'

Same issue on the Unity SDK as well.

same issue using flutterflow, any ideas what that is? im not even using firebase storage and im getting this!

ah okay, flutterflow folks here check this out from flutterflow:
We are actively working to resolve an iOS deployment outage cause by a recent Firebase issue. We are awaiting a fix while investigating workarounds and hope to have this back online soon! Thank you for your patience 💜

Yes, that link brings you to this thread :D
Thats how I came here lol

ah okay, flutterflow folks here check this out from flutterflow: We are actively working to resolve an iOS deployment outage cause by a recent Firebase issue. We are awaiting a fix while investigating workarounds and hope to have this back online soon! Thank you for your patience 💜

Alex from FlutterFlow here. We've taken down the link to this issue for now so as not to flood this thread (originally added it just to allow folks to track the issue).
I can second that downgrading to use FirebaseSDKVersion = '10.22.0' works (thanks @minusoneman), which we'll temporarily do for our apps.
This issue surfaces across different Flutter, firebase_storage, and Xcode versions so it does appear to be an issue with the FirebaseSDKVersion 10.23.0 release from just a few hours ago.

Thanks @agreaves
Can you help guide how to downgrade the SDK inside Flutterflow?

We're tracking it here: https://github.com/FlutterFlow/flutterflow-issues/issues/2445, so if you're coming from FlutterFlow please add any comments there (unless of course it provides useful info to others outside of FF).

Thanks for the report, I'm investigating this

Perhaps it's related to the latest firebase-ios-sdk 10.22.0?
If I manually override the FirebaseSDKVersion in my Podfile I'm able to build the project.
# Override Firebase SDK Version
$FirebaseSDKVersion = '10.22.0'

Thanks! It worked.

Perhaps it's related to the latest firebase-ios-sdk 10.22.0?
If I manually override the FirebaseSDKVersion in my Podfile I'm able to build the project.
# Override Firebase SDK Version
$FirebaseSDKVersion = '10.22.0'

This method worked for me too. I dont use FF.

After investigation, it seems that some internal libraries in the native iOS SDK are not strongly linked to a version. When the iOS team released 10.22.0 yesterday some dependencies got upgraded without the main package.
https://github.com/firebase/flutterfire/pull/12430 will properly update all the plugins to 10.22.0.
As mentioned before, you can force the SDK on 10.22.0 with
$FirebaseSDKVersion = '10.22.0'

I'll release the new version this afternoon

Alex from FlutterFlow here. We've taken down the above link to this issue for now so as not to flood this thread (originally added it just to allow folks to track the issue).
~I can second that downgrading to use FirebaseSDKVersion = '10.21.0' works (thanks @minusoneman), which we'll temporarily do for our apps.~
~This issue surfaces across different Flutter, firebase_storage, and Xcode versions so it does appear to be an issue with the FirebaseSDKVersion 10.22.0 release from just a few hours ago.~
Upon further investigation, it looks like the newest FirebaseSDKVersion 10.22.0 release is incompatible with at least some older Firebase pods. By default (without FirebaseSDKVersion 10.22.0 hardcoded), when installing pods certain internal pods such as FirebaseCoreInternal use the newest version 10.22.0, while others still use older versions based on the version specified in pubspec.yaml (the latest Firebase packages appear to use 10.20.0).

How Brother?

Perhaps it's related to the latest firebase-ios-sdk 10.22.0?
If I manually override the FirebaseSDKVersion in my Podfile I'm able to build the project.
# Override Firebase SDK Version
$FirebaseSDKVersion = '10.22.0'

Where to change brother?

Perhaps it's related to the latest firebase-ios-sdk 10.22.0?
If I manually override the FirebaseSDKVersion in my Podfile I'm able to build the project.
# Override Firebase SDK Version
$FirebaseSDKVersion = '10.22.0'

Where to change brother?

Podfile
target 'Runner' do
use_frameworks!
use_modular_headers!
$FirebaseSDKVersion = '10.22.0'
flutter_install_all_ios_pods File.dirname(File.realpath(FILE))
end

@Lyokone
Are you able to estimate ~when are you gonna release new version?
It's kind of blocker for release to us 😕

@LukaszWojcikIteo it has been released as part of firebase_core: ^2.26.0

This worked for me with the new version of firebase_core on Flutter.
There is no need to modify the Podfile as mentioned before in this issue.

flutter pub upgrade
flutter clean
Delete /ios/Pods
Delete /ios/Podfile.lock
flutter pub get
From inside ios folder: pod install

Just delete everything in your Podfile, and put the code below;
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!
Override Firebase SDK Version
$FirebaseSDKVersion = '10.22.0'
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

What about older Firebase versions? We can't update to latest atm, the only way would be to upgrade?

How can stuff like this even be released? SDK is not compiling...

How to fix?

Update firebase_core to the latest

Perhaps it's related to the latest firebase-ios-sdk 10.22.0?
If I manually override the FirebaseSDKVersion in my Podfile I'm able to build the project.
# Override Firebase SDK Version
$FirebaseSDKVersion = '10.22.0'

Thanks! It worked.

thank you so much.Worked for me

Hi guys, I am in older versions of firebase, and I can't upgrade because I am not ready to go to dart sdk>3.0.0
Why is this affecting my build? Is there a way of resolving this without upgrading firebase versions?

Hey folks. Sorry to hear about this problem. The team will triage and get to this as soon as possible.
If you are affected by this issue, leave a 👍 in the original comment. Please only add additional comments if you have new to information about the issue.

What is the resolution for this?

Hi guys, I am in older versions of firebase, and I can't upgrade because I am not ready to go to dart sdk>3.0.0 Why is this affecting my build? Is there a way of resolving this without upgrading firebase versions?

Same here. Fortunately, overriding the Firebase SDK version worked for me.
What's wrong with this picture?

I built my Flutter app for iOS on February 16. It works.
I do not change any of my Flutter dependency. I built my Flutter app for iOS on March 8. It does not work.

Well, "not changing dependencies and not working" is what's wrong here. I pin my versions in Flutter, but the Firebase iOS libraries pull in new versions. How can I prevent that?

This issue has been resolve in firebase ios SDK 10.22.0
If you're using firebase dependencies you can upgrade them as follow(whichever you're using right now)
firebase_analytics: 10.8.9
firebase_auth: 4.17.8
firebase_core: 2.27.0
firebase_crashlytics: 3.4.18
firebase_messaging: 14.7.19
firebase_storage: 11.6.9

then flutter clean and pod install. Should work

This issue has been resolve in firebase ios SDK 10.22.0. You don't need to edit podfile to hard-code the firebase ios sdk version
If you're using firebase dependencies you can upgrade them as follow(whichever you're using right now)
firebase_analytics: 10.8.9
firebase_auth: 4.17.8
firebase_core: 2.27.0
firebase_crashlytics: 3.4.18
firebase_messaging: 14.7.19
firebase_storage: 11.6.9

then flutter clean and pod install. Should work

What if I can't upgrade dependencies for another issues? Is there a solution that doesn't need upgrade?

If you can't upgrade dependencies, you can always manually force the underlying native iOS SDK:
$FirebaseSDKVersion = '10.22.0'

@Lyokone That only results in a pod dependency error:
[!] CocoaPods could not find compatible versions for pod "Firebase/Auth":
      In snapshot (Podfile.lock):
        Firebase/Auth (= 10.18.0)

      In Podfile:
        firebase_auth (from `.symlinks/plugins/firebase_auth/ios`) was resolved to 4.16.0, which depends on
          Firebase/Auth (= 10.22.0)

We're stuck on Flutter 3.7.12 for now, and managing dependencies is fast becoming a nightmare.

how to fix with unity?
I try what you said but did not work


Details regarding saved image.

I wanted to know the PNG you save contains RGB map, how can it be used when training a deep learning network.

@defaultcute12 Check README. This tool has nothing to do with any deeplearning framework.


install: Add --wipe_destdir option

If specified, wipe destination directory before installing.
Fixes #893.

The test error seemed unrelated to my patch. How do I re-run the test?

The test error seemed unrelated to my patch. How do I re-run the test?

They are unrelated errors. Something change in Bazel at head that is breaking a few of these. It's not that Bazel is really broken either, it's that we have tests for compatibility against WORKSPACE too, and Bazel is rapidly deprecating support for that.
I will force merge.


QG checks Release 24.12

QG checks
Please keep this issue open until QG is concluded and will be managed by the Issue Creator!
We will inform you about finding and proposals in separated issues, this issue here is for the Overview of the Checks!
Please keep this issue open until QG is concluded!
Product Owner: @obalandi
Dev SPOC: @drcgjung
Helm Chart Version: 1.14.24
App Version: 1.14.24
Release Managemnet Reference Issue:
Check of Tractus-X Release Guidelines

Currently implemented automatic checks can be found under your product on our Release Guidelines Checks Board
This QG Check is depending on the mandatory information from our current Release Guidelines

TRG 1 Documentation

[x] TRG 1.01 appropriate README.md
[x] TRG 1.02 appropriate install instructions either INSTALL.md or in README.md
[x] TRG 1.03 appropriate CHANGELOG.md
[x] TRG 1.04 editable static files
[ ] #120
[ ] #121
[x] TRG 1.07 user manual
[ ] #122

TRG 2 Git

[x] TRG 2.01 default branch is named main
[x] TRG 2.03 repository structure
[x] TRG 2.04 leading product repository
[x] TRG 2.05 .tractusx metafile in a proper format
[x] TRG 2.06 Dependabot

TRG 3 Kubernetes

[x] TRG 3.02 persistent volume and persistent volume claim or database dependency (subchart) are in place when needed

TRG 4 Container

[x] TRG 4.01 semantic versioning and tagging
[x] TRG 4.02 base image is agreed
[x] TRG 4.03 image has USER command and Non Root Container
[x] TRG 4.05 released image must be placed in DockerHub, remove GHCR references
[x] TRG 4.06 separate notice file for DockerHub has all necessary information
[x] TRG 4.07 root file system is set to read access by default, but can be overwritten by the user

TRG 5 Helm

[x] TRG 5.01 Helm chart requirements
[x] TRG 5.02 Helm chart location in /charts directory and correct structure
[x] TRG 5.03 proper version strategy
[x] TRG 5.04 CPU / MEM resource requests and limits and are properly set
[x] TRG 5.06 Application must be configurable through the Helm chart
[x] TRG 5.07 Dependencies are present and properly configured in the Chart.yaml
[x] TRG 5.08 Product has a single deployable helm chart that contains all components
[x] TRG 5.09 Helm Test running properly
[x] TRG 5.10 Products need to support 3 versions at a time
[x] TRG 5.11 Upgradeability

TRG 6 Released Helm Chart

[x] TRG 6.01 Released Helm Chart

TRG 7 Open Source Governance

[x] TRG 7.01 Legal Documentation
[x] TRG 7.02 License and copyright header
[x] TRG 7.03 IP checks for project content
[x] TRG 7.04 IP checks for 3rd party content
[x] TRG 7.05 Legal information for distributions
[x] TRG 7.06 Legal information for end user content
[x] TRG 7.07 Legal notice for documentation
[x] TRG 7.08 Legal notice for KIT documentation

TRG 8 Security

[x] TRG 8.01 Mitigate high and above findings in CodeQL
[x] TRG 8.02 Mitigate high and above findings in KICS
[x] TRG 8.04 Mitigate high and above findings in Trivy
[x] TRG 8.03 No secret findings by GitGuardian or TruffleHog

Hints
Information Sharing

TRG 1.05, 1.06, 1.08 still missing and I created issues for them. These are regarding documentation and will be pushed to the repository this week.


Change manifest naming to avoid conflicts with internal Resolve files

Resolve Free ends up installing multiple desktop entries due to identical naming in the desktop file shipped with Resolve.
Change the flatpak naming to avoid packaging these internal files unnecessarily.

there are a ton of commits here, this probably needs to be rebased and squashed.
can you help me to understand why this PR is required though? i hadn't previously seen any conflicts with internal files, since we choose what to install and when.

there are a ton of commits here, this probably needs to be rebased and squashed.
can you help me to understand why this PR is required though? i hadn't previously seen any conflicts with internal files, since we choose what to install and when.

It's mainly down to the free Resolve version having duplicate desktop entries which are both installed due to sharing a common filename, so if that could be fixed by another method this wouldn't be required

@RobotRoss can you verify this with the latest commits I just pushed? I've absorbed a bunch of fixes and made some more.


NavBar links

The login button redirects to the register form instead of the login form.

The login button now goes to the login page, but the other button on the login page does not work. (The submit button.)

The bug was fixed! The url on the form was incorrect.


fix: add clear

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Downgrade DRBD to v9.0.32 and Utils to v9.12.1 for compatibilty with Hwameistor

This PR downgrade versions to:

DRBD: v9.0.32
Utils: v9.12.1

DRBD v9.0.32 does not compile on Ubuntu Jammy, therefore install DRBD v9.1.10 on Ubuntu Jammy just for test purpose.
Readme and Chart Notes are updated accordingly.

LGTM


Add Nodeasy.com file

Please make sure your node is up and running now. Join #validators on Discord for help: https://discord.gg/QeJWCrE.


Autoprefixer doesn't handle selectors

Most browsers don't support the standard :fullscreen pseudoclass yet, so I thought the prefixer would automatically generate the relevant variants (like -webkit-full-screen) but it turns out that it only handles properties, not selectors.
As far as I can tell, implementing this would require duplicating the styles because browsers ignore selectors if they contain any unknown parts (like the vendor prefixed pseudoclasses for other browsers) even when there's more than one of them.
Are there any plans to support selector prefixing?

we already do this manually for :placeholder, I would consider one for :fullscreen too. as a workaround, you could do this manually for now?

Do you have a handy list of selectors that need to be prefixed?

:fullscreen and its variants were the only ones I've run into. It's possible to work around but it's a bit ugly because the styles need to be duplicated for each variant. Thanks for looking into this.

this should work in 2.20.27. feel free to reopen if it doesn't.

Awesome, thanks!


[Bug] Nested record field is not quoted and causes build error when contract enforced enabled.

Is this a new bug in dbt-bigquery?

[X] I believe this is a new bug in dbt-bigquery
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
Hello,
I have the following model that use two reserved keywords groups and full as example:
{{
    config(
        materialized='table'
    )
}}

WITH data AS (
  SELECT 1 AS id, [STRUCT(11 AS id, 'Peter' AS name, ['a', 'b', 'c'] AS `full`)] AS `groups`
  UNION ALL
  SELECT 2 AS id, [STRUCT(22 AS id, 'Bob' AS name, ['a', 'b', 'c'] AS `full`)] AS `groups`
)

SELECT
  id,
  `groups`
FROM data

and the following model schema:
version: 2

models:
  - name: model_bug
    config:
      contract:
        enforced: true
    columns:
      - name: id
        data_type: INTEGER
        constraints:
          - type: not_null
        description: "ID Description."
      - name: groups
        quote: true
        data_type: ARRAY
        description: "Groups description."
      - name: groups.id
        quote: true
        data_type: INTEGER
        constraints:
          - type: not_null
        description: "Group ID description."
      - name: groups.name
        quote: true
        data_type: STRING
        constraints:
          - type: not_null
        description: "Group name description."
      - name: groups.full
        quote: true
        data_type: ARRAY<STRING>
        description: "Group full description."

The model cannot be build because the nested column full is not quoted during contract validation step. However, the groups column is correctly quoted. Here is the generated query that causes the issue:
select * from (
        select

    cast(null as INT64)
 as id,

    cast(null as array<struct<id INT64, name STRING, full ARRAY<STRING>>>)
 as `groups`
    ) as __dbt_sbq
    where false and current_timestamp() = current_timestamp()
    limit 0

Expected Behavior
The dbt-bigquery adapter should quote any reference of the full column during table schema validation and next steps.
Steps To Reproduce

Open your DBT project

Create the following model_bug.sql:

{{
    config(
        materialized='table'
    )
}}

WITH data AS (
  SELECT 1 AS id, [STRUCT(11 AS id, 'Peter' AS name, ['a', 'b', 'c'] AS `full`)] AS `groups`
  UNION ALL
  SELECT 2 AS id, [STRUCT(22 AS id, 'Bob' AS name, ['a', 'b', 'c'] AS `full`)] AS `groups`
)

SELECT
  id,
  `groups`
FROM data

Create the following schema.yml:

version: 2

models:
  - name: model_bug
    config:
      contract:
        enforced: true
    columns:
      - name: id
        data_type: INTEGER
        constraints:
          - type: not_null
        description: "ID Description."
      - name: groups
        quote: true
        data_type: ARRAY
        description: "Groups description."
      - name: groups.id
        quote: true
        data_type: INTEGER
        constraints:
          - type: not_null
        description: "Group ID description."
      - name: groups.name
        quote: true
        data_type: STRING
        constraints:
          - type: not_null
        description: "Group name description."
      - name: groups.full
        quote: true
        data_type: ARRAY<STRING>
        description: "Group full description."

Run dbt build

Relevant log output
No response
Environment
- dbt-cloud: 2024.7.209

Additional Context
No response

After reviewing the code, it seems the issue is related to the methods get_nested_column_data_types and _update_nested_column_data_types, where the method is called from the adapter bigquery__get_empty_schema_sql method.
Problem: The current _update_nested_column_data_types method may not handle nested records where quoting is necessary (as indicated by the YAML configuration) to correctly represent data types.
Solution: Introducing a quote boolean parameter allows explicit control over whether values within the nested record should be quoted. This aligns the method's behavior with the YAML configuration.

If you remove the below, the error should be gone

name: groups
quote: true
data_type: ARRAY
description: "Groups description."


Question about the embedding range (weight initialization and phase normalization)

Hello, first of all many thanks for providing the source code alongside the paper.
I was comparing the implementation of RotatE against the paper and I found something which seems quite important, the embedding range, which is defined as (gamma+2)/hidden_dim.
This raises two questions that could be related to each other:

The paper says "Both the real and imaginary parts of the entity embeddings are uniformly initialized, and the phases of the relation embeddings are uniformly initialized between 0 and 2π.", while in the code both the entities and relations are initialized with Uniform(-embedding_range, embedding_range).
The phase relation is divided by the embedding range in the metric implementation, while that does not seem explicitly mentioned in the paper from my reading.

Could you help me understand these two points, or maybe point out in the paper the explanation behind them?
Thank you very much.

Hi, thank you for your attention in our work.

Yes, they are both initialized with [-embedding_range, embedding_range]. We implement initialization in this way because we want a unified initialization approach across different KGE methods.

The embedding of relations is scaled to 0 to 2π before calculating the real parts and imaginary part. Along with 1), this constitutes a valid implementation of "Both the real and imaginary parts of the entity embeddings are uniformly initialized, and the phases of the relation embeddings are uniformly initialized between 0 and 2π."


Fix for snapshot stuck deletion

When multiple snapshots are taken within snap window for version2 volume then snapshot deletion was getting stuck. This fix resolves this snapshot deletion stuck issue introduced with shallow copy feature.
Please check the type of change your PR introduces:

[ x] Bugfix
[ ] Feature Enhancement
[ ] Test Automation
[ ] Code Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Community Operator listing
[ ] Other (please describe):

What is the current behavior?

Snapshot deletion is getting stuck when multiple snapshots are taken within snap window for version2 volume

What is the new behavior?

Snapshot deletion works fine if multiple snapshots are taken within snap window for version2 volume

How risky is this change?

[ ] Small, isolated change
[ x] Medium, requires regression testing
[ ] Large, requires functional and regression testing

quay.io/hemalatha_gajendran/snapshot_stuck_issue_final - Use this latest one

Image: quay.io/hemalatha_gajendran/remote_fsfix:latest (Fix for remotefs issue)

clone of shallow copy is not working on ocp

quay.io/hemalatha_gajendran/shallowcopy_multiple_fixes_final:latest


Support receiving patches via e-mail

I recently heard that SourceHut and/or Gitlab have a feature where each repo has a project-specific e-mail address where someone can send a .patch file to in order to open a pull-request. This would not require contributors to create an account in order to contribute.
This is kinda in parallel to https://github.com/go-gitea/gitea/issues/184, as it's also about federation, but not really full federation between instances, just using e-mail and git in their already "federated" context.
Ideally, this would

[ ] assign a project-specific e-mail address
[ ] allow incoming e-mail with a .patch file as attachment and publish that as a PR
[ ] reply to that e-mail with some unique identifier so that this user can somehow post new .patch files to update the PR

But we still need the email has been registered on this instance?

No the idea is that users don't have to register in order to submit patches. F.e. on a single-user instance, which I think is an important use case, one shouldn't want anyone to register, but everyone to be able to interact via e-mail.

This also would allow users to use the same workflow that they use with standard git repos. In many setups, users clone the upstream repo, make their changes, and then email a patch to a mailing list. A maintainer reviews the patch (replying with suggested changes if necessary) and applies it if it looks good.
 There’s a reason why git uses email addresses to label commit authors!
This flow is much easier than creating an account for a gitea instance, forking a repo, cloning your fork, checking out a branch, making your commits, and finally filling out a web form to merge them upstream.
This flow can be implemented step-by-step:

Allow the option to create a PR from a patch generated by git format-patch, if users prefer that over creating and cloning a fork.
In email notifications for new PRs, attach the patch to the email as if it was sent by git send-email so the maintainer can apply the patch like they normally would.
Allow users to reply to notification emails and have those replies show up in the web interface. GitHub already does this.
Allow creating PRs by sending an email using git send-email

If these four steps are completed, Gitea repos will support both GitHub-style PRs and the standard email flow used by projects such as Linux, ffmpeg, all the projects on Sourcehut.
I'll make issues for these if they don't already exist.

this would require a mailing list software already in place, wouldn't it?
or is the idea to integrate it fully into Gitea? @stevenroose

I think the best way woul be if email server is a seperate deamon(s) (e.g Postfix and Dovecot), and gitea has an accout witch is checked by gitea's cron job via pop3/imap.

Just wanted to chime in to express my interest in this feature. In my opinion, this is a big deal for https://docs.gitea.io/en-us/comparison/. I don't see why accepting mailed patches should be a "sourcehut special".
In addition, this has the potential to suddenly make gitea a viable home for some large patch-based projects.
This seems like something gitea could be proud of.
Patch acception seems to already be coming in https://github.com/go-gitea/gitea/pull/10007, accepting with email seems like a logical next step, and could proceed some really nifty features like making CI available to patch mailing lists.

I'm also very interested in email-related features, but I would propose to take it a bit further.
I'm not sure this is the right place for a discussion about this, so tell me if you'd rather have me open another issue about this.
TL;DR: enable email-based federation for PRs in the UI (may benefit from discussion about possible overlap with work on ActivityPub-based federation)
Details
Rather than just enabling email one way, how would you feel about making it a first class citizen in the UI?
Since Gitea probably already runs everything that's required to both send or receive emails via/from git send-email so I don't think anything additional would be required on the server.
As mentioned, one would need an email address associated to each project.
Then, when creating a PR, the UI could provide the option to target an email address rather than pick a local target branch.
This would enable Gitea to federate PRs across Gitea servers but also with other forges using email-based workflows.
Maybe naively, I don't think it would require a lot more work compared to supporting patches from emails but it would enable users that do not know how to use email-based workflows (or just don't like it) to interact easily with these forges.

Maybe we can create a email proxy user, all PRs from emails could be counted as this user but attach the original author's email address in every PR.

If the plan is to support mirroring comments on PRs to/from the web UI and email, you'll probably need to figure out how to properly support bottom-posting, to not overly annoy the users on the email side?

Since seemingly so many people are in favour of this feature, I'd like to add a different perspective on this.
I think, it is not expedient to support such an antiquated feature. It arose from a time, when mailing lists were common & a lot of functionality on the internet went through e-mail technology.
It's a comparatively cumbersome feature, which does not complement or even replace the existing features to apply pull requests or patches or anything like that.
It's simply an alternative, which is only there, due to historical reasons.
I'm also a bit surprised how this feature is so much hyped up by some. This isn't anything special or useful. It's just something that people were doing back then, because they lacked the resources & technology to do better. Which we have & do now.
While I'm not against additional features, adding features can add issues, too. There is more to be maintained, fixed, make work with other features, etc. I don't see how maintaining this feature adds significant value to Gitea as a product.
It's a nice gag feature.
I'm sure there's a tiny niche using this, but I'm not sure if that is worth the effort.
This is a different view on the issue, which I made public, because I was a bit surprised by the support & hype around it, even though it evolved basically into a gag feature, over the decades.

What's the definition of a gag feature?

definition of a gag feature

Thanks for asking, I should've been clearer.
It's a feature for fun, only. It's like when Star Wars/Star Trek fans create a theme for something. It's cool & funny, but rarely anyone uses it, because it's more of a joke (something for the laughs), than an actual theme one would want to apply, since it's not about usability or something that fits the current needs & demands of the users, but about being fun.
Another example would be running Doom on a calculator. It's really fun. It's really cool. It looks cool. But nobody actually seriously plays Doom on a calculator. Even the amount of people playing actual Doom on an actual computer the way it was originally intended is far from being popular, anymore.
Still, everyone knows about this, because it's fun!
Same with this one. It's fun. I'm not "against" this, or something. I'm just saying, it's unnecessary & overhyped. It's funny, but not useful in 2022.

Check out the links above about kernel development and try to decide for yourself how much of a niche use-case email workflows are

Check out the links above about kernel development

😆
I really have to laugh now, because I actually was recently touching the world of kernel development and noticed how terrible e-mailed patches are. The whole system is absolutely terrible. Atrocious to the bone.
This was another reason, why I was surprised by the hype for this issue, because I was thinking about how terrible kernel development works now. 😄

That said, Kernel development is a niché.
Obviously, using a kernel is widespread, but barely any user is putting effort in Kernel development. It's a highly closed up system, where one reason for this is exactly this antiquated form of patch management.
So, it's important to not confuse usage with actual development efforts. Actual development efforts on the Linux Kernel are not done by the majority of developers. Not even close.

I really have to laugh now, because I actually was recently touching the world of kernel development and noticed how terrible e-mailed patches are. The whole system is absolutely terrible. Atrocious to the bone.
This was another reason, why I was surprised by the hype for this issue, because I was thinking about how terribly inaccessible kernel development works now. smile

Maybe you could explain why you don't like it so we can attempt to avoid those pitfalls if this or a similar feature ever gets developed? It may be relatively niche, but it's still quite a popular workflow (sourcehut, for example, uses it exclusively and plenty of projects other than the kernel use email based workflows). I tend to prefer it and strongly disagree with what you said, but since you didn't detail why it's hard to know if it's a legit criticism or just your personal preference. Tastes differ, naturally.

Maybe you could explain why you don't like it so we can attempt to avoid those pitfalls if this or a similar feature ever gets developed?

It's not that I "dislike" or "don't like it", it's just that I don't really see a realistic point in why anyone should use it, except it is absolutely necessary, for example in an extremely restricted environment.
For example, doing any kind of patch work requires the user to get used to manually creating the diffs & make e-mailing work, etc.
If the user needs to get used to manual stuff like this, then he might as well get used to the normal process of applying a patch, like what developers use all the time.
Now, based on that, we could say, that it's not necessary to do it manually. Let's make a GUI for it. That's what usually happens. If something is too complicated on the CLI or otherwise too difficult to construct, a GUI is usually created for it.
However.... if we are going to make a GUI for it, then why do we need the e-mail patches to begin with? We already have GUIs on Git frontend platforms. We don't need a second GUI or an extended GUI for e-mail patches, because it's not necessary.
So, from what I know, there is literally no reason to ever use e-mail patches, except someone lives in a wild forest, where there is only e-mail client access for users. Otherwise, if a developer has a normal computer with a normal browser, with a fair enough internet connection, there is no objective reason to actively use e-mail patches. At least, I know of none. Maybe someone can shine some light on it, because so far I have read no significant advantage beyond "we have always done it like this" and "it's cool" and "look, the Kernel team does it, too".

It may be relatively niche, but it's still quite a popular workflow (sourcehut, for example, uses it exclusively and plenty of projects other than the kernel use email based workflows).

I don't think so, but I don't have enough data to back that thought up, so maybe you, or anyone else here, could enlighten me on that.
The SourceHut example is, in my view, as mentioned previously, backing up my statements. If SourceHut is the lone wolf doing it, there must be a catch. And the catch is, there is little to no point in using it over alternatives.
As for the other projects you hint on:
Can you name a single modern project, which uses e-mail based patches?
Not one of those dinosaur projects literally coming from a different millenium...
Is there a single modern project that actively uses e-mail patches? I doubt it.
And whether those dinosaur projects use it, does not matter, because 95% of their reasoning for using stuff like this is the reason nobody should ever use to do something:
"We have always done it like this."
As soon, as people in decision focused positions take over that argument and deem it valid, the project associated with it, will go down the drain, eventually.
Never do something, because "we have always done it like this". Else, we would still be using horses to travel the lands & landline phones for an expensive call. Or perhaps we would still be running around with spears & swords.
That said, I honestly am interested in the projects that use this workflow and perhaps even favour it over the more obvious alternatives. I really do not understand, besides "we have always done it like this". There is no other point in doing that.

I tend to prefer it and strongly disagree with what you said, but since you didn't detail why it's hard to know if it's a legit criticism or just your personal preference. Tastes differ, naturally.

Again, I do not "dislike" or "don't like" it. I am not "against" it. If this feature gets implemented, I won't break into anyone's home for it. 😄
What I'm saying is, that this issue focuses on something, that is ultimately unnecessary. It's like using a dangerous and easy to break plane from the 1900's, when you have the choice to use a modern Boeing for the same cost, which basically almost flies on its own and you don't have to constantly worry about it breaking mid-flight, essentially killing all passengers.
Any project, especially open source projects, have a limited amount of resources. The biggest & most obvious ones are developer time & money. While time is money, so actually it's all about money in our world, unfortunately.
So, if developer time is spent on this issue, it will indubitably, lack on some other issue/bug/improvement/whatever. It's simply logical, that this will happen & it cannot be avoided without magic.
Which basically leads me to my final point in this explanation.
I am not "against" it. I think your reasons are understandable, from a human perspective.
All I am trying to do is to lessen the hype about this & pointing out, how this feature extension is not really necessary, especially when you look at the cost/performance ratio.
Even more so, when I look at quotes like these.

Rather than just enabling email one way, how would you feel about making it a first class citizen in the UI?

Just wanted to chime in to express my interest in this feature. In my opinion, this is a big deal for https://docs.gitea.io/en-us/comparison/.

Like what? 🤔
The first one would be a huge change taking tons of resources (correct me if I'm wrong) for essentially no real improvement.
The second one is simply not reflecting reality. It ain't a big deal. It's far away from a "big deal". It doesn't matter. Else, you would see this feature all over the Git world. Yet, you don't. Because, honestly, nobody (as in, by far the most developers) cares. (Bringing back the point about SourceHut being the only provider... Yes, because it's not like this is a super demanded feature.)
I do not want developers using up their resources on something, that is essentially very unnecessary, when they at the same time could (looking at the amazing Gitea developers; great people with great work!) improve Gitea performance, UX, etc. I have tons of UX improvements for Gitea, for example. I think, they matter like 100 million times more than some weird fringe feature, most developers don't care about. Perhaps, they don't even know about it....
P.S.:
I feel like I have to emphasize this, so people don't hate me for "hating" when I actually just try to explain a different view on the topic:
I do not "dislike" this. I do not "not like" it. It's just a waste of energy and I'm trying to point that out.
I could imagine this being created as a plugin by a third party, that would otherwise not do any development on the core Gitea project, in the first place. Then, we don't "lose" core maintainer time over this.

Fun fact:
"We have always done it like this." has brought us the QWERTY keyboard layout, which is essentially a very bad one. However, "we have always done it like this", because of typewriters.
Now, the whole world is stuck with some crappy QWERTY-derived layout, which does not make sense for any language. It only makes sense on typewriters.
If people wouldn't have thought "we have always done it like this", everyone would use DVORAK, Colemak, Workman or even Neo2, which are objectively superior layouts. Yet, barely anyone uses them, because the QWERTY virus is spread all over the world.
There are plenty of examples like this and I have just one thing to say to whoever supports the old ways:
It's time to move on.

Using an inferior method of doing something voluntarily is not a matter of personal preference. It's a matter of not willing to accommodate to the usage something better.
A method is "inferior" if it has worse performance for the same cost or if the cost/performance ratio is generally comparatively bad.
In this specific case of submitting Git patches, there is no real advantage in using e-mail patches over what we have & do now.

I think, it is not expedient to support such an antiquated feature. It arose from a time, when mailing lists were common & a lot of functionality on the internet went through e-mail technology.
It's a comparatively cumbersome feature, which does not complement or even replace the existing features to apply pull requests or patches or anything like that.

This is simply not accurate. You might say that in your own (limited?) usage, you have not found mailing list development to work well, but you seem to be mixing personal taste and general truths.
Mailing lists allow for an alternate development workflow, which is arguably cumbersome without good tools (I'd hate to try this using Outlook as my email client), but that offers a number of advantages compared to PR-based development, such as the ability to mix discussion and code: e.g. Someone asks if a feature would be a good idea, the community discusses it, someone produces a patch, the patch is reviewed, etc. all within the same thread. Here's an example of a this sort of thing happening with a bug report:

With good tools, mailing-list development can end up being more convenient than web forges. However, quite a few people (like yourself!) are put off by the idea of using a mailing list. Hence, this is why having a forge that supports both modes of development at once is (to quote past me) "a big deal".
If you were actually interested in finding more out about mailing list development, rather than just spewing "lol, email? so outdated" into this issue, there are numerous writings on this you could have looked at, e.g.:

https://web.archive.org/web/20180522180815/https://dpc.pw/blog/2017/08/youre-using-git-wrong/
https://drewdevault.com/2018/07/02/Email-driven-git.html
https://begriffs.com/posts/2018-06-05-mailing-list-vs-github.html

I'll also note that while the LKML is most often raised as a prime example of Mailing-list development, there are plenty of other large FOSS projects actively developed this way, e.g.

Nginx
Most Apache projects (e.g. Cassandra, Arrow, Apache HTTP server, etc.)
Git itself
Most GNU projects (e.g. GCC, Ghostscript, Coreutils, Guile, Guix, Nano, Octave, ...)
LibreOffice
Xen
The R programming language
and more...

While I do appreciate the discussion on this topic, I'm temporarily locking the issue. I think there are pros/cons to this and a lot if those details have been captured.


ENH: Add chunksizes argument to Pipeline.map and Pipeline.map_async

Description of the changes
Adding a mapspec_chunksize option for Pipeline.map() and Pipeline.map_async().

Chunksizes can be specified for individual outputs or as default with the empty string key

The user can specify chunksizes as an integer or pass a callback which recieves the number of iterations of a pipefunc resulting from its mapspec and returns the desired chunksize (the latter option is a likely bit more handy, especially when running Pipeline.map() with arbitrary input shapes).

invalid chunksizes (not an int, or smaller than 1) are detected and result in a

Introduced helper functions _process_chunk, _chunk_indices, and _chunksize_for_func in pipefunc/map/_run.py to process and handle chunk sizes for MapSpec computations.

Modified the _maybe_parallel_map function to use the new chunk size handling logic.

Adjusted the _process_task and _process_task_async functions to handle chunked outputs correctly.

Tests

Added a new test test_pipeline_with_heterogeneous_chunksize in tests/map/test_map.py to verify the functionality of the mapspec_chunksizes parameter.
Testcoverage of added/modified methods at 100%
Might want to add a unit test which validates whether the Executor.submit method is called the expected ammount of times?

Related Issues
resolves #484
Feel free to propose any enhancements, especially for how the feature should be documented in the docstring.
We could also add a small chapter in the FAQ after the Overhead/Performance chapter where choosing adequate chunksizes and their performance gain is detailed.

@LennartGevers, awesome job!
Trying it out right now and figuring out why now all CI jobs are triggered...

Merged 48 minutes after submitting the PR :tada:
Really great job and thanks for your contribution, I am sure this will help out others!


error on framewor7 cordova dont work all controls after load the map

im tryng to use cordova with framework7 and this plugin map but after loaded the map, i cant use any controls of framework7 , i dont know what is the bug because i dont have how debug, this bug i have been seen too on bootstrap, can some one help me?

We don't support compatibility with any JS frameworks.
Sorry, but it's too much work for us.
Please adjust/resolve your issue by yourself.


feature request: generate redirects json

Would be cool to also generate the redirects.json to make sure search engines and users that have bookmarked pages on medium can access them on the new ghost blog.

I was assuming that most people would be moving from medium.com to their own domain, so they wouldn't need rediects on their domain.
I did try to implement canonical url links in the imported blog posts so you wouldn't have any SEO impact by duplicating your content on a new domain, but at the time I wrote this tool, there was no way to set canonical urls in Ghost. I filed a feature request on Ghost, but I'm not sure if it was ever implemented.


Problem installing pinpoint 2.0.2

Prerequisites
I have checked the FAQ, and issues and found no answer.
What version of pinpoint are you using?
Pinpoint 2.0.2
apache-tomcat-8.5.43
hbase-1.3.5 (standalone)
openjdk version "1.8.0_191"
Describe your problem**
Pinpoint web + collector webapplication don't start.
Error reported by tomcat in catalina*.log
What have you done?
(Upgrade from a previous working pinpoint 1.8.4 server)

Delete all datas from hbase datadir
Delete all datas from hbase zookeeper datadir

cd $TOMCAT
./bin/shutdown.sh
rm ../logs/*
rm -fr tomcat/webapps/*
cp pinpoint-web-2.0.2.war  $TOMCAT/webapps/ROOT.war
cp pinpoint-collector-2.0.2.war $TOMCAT/webapps/
echo "export JAVA_OPTS="-Dpinpoint.zookeeper.address=<IP_ADDRESS>"' >> setenv.sh
./bin/startup.sh
Screenshots
N/A
Logs
04-Jun-2020 13:47:56.882 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 346 ms
04-Jun-2020 13:47:56.900 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
04-Jun-2020 13:47:56.900 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.5.43
04-Jun-2020 13:47:56.916 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [/opt/pinpoint/apach
e-tomcat-8.5.43/webapps/pinpoint-collector-2.0.2.war]
04-Jun-2020 13:48:01.475 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TL
Ds. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning
can improve startup time and JSP compilation time.
04-Jun-2020 13:48:07.543 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [/opt/pinpoint/a
pache-tomcat-8.5.43/webapps/pinpoint-collector-2.0.2.war] has finished in [10,626] ms
04-Jun-2020 13:48:07.544 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [/opt/pinpoint/apach
e-tomcat-8.5.43/webapps/ROOT.war]
04-Jun-2020 13:48:12.279 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
04-Jun-2020 13:48:16.441 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
04-Jun-2020 13:48:16.441 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [] startup failed due to previous errors
04-Jun-2020 13:48:16.570 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [localhost-startStop-1-SendThread(<IP_ADDRESS>:2181)] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
java.lang.Thread.sleep(Native Method)
org.apache.hadoop.hbase.shaded.org.apache.zookeeper.ClientCnxnSocketNIO.cleanup(ClientCnxnSocketNIO.java:230)
org.apache.hadoop.hbase.shaded.org.apache.zookeeper.ClientCnxn$SendThread.cleanup(ClientCnxn.java:1185)
org.apache.hadoop.hbase.shaded.org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1122)
04-Jun-2020 13:48:16.572 WARNING [localhost-startStop-1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [localhost-startStop-1-SendThread(localhost.localdomain:2181)] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
java.lang.Thread.sleep(Native Method)
org.apache.zookeeper.ClientCnxnSocketNIO.cleanup(ClientCnxnSocketNIO.java:230)
org.apache.zookeeper.ClientCnxn$SendThread.cleanup(ClientCnxn.java:1246)
org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1182)
04-Jun-2020 13:48:16.579 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [/opt/pinpoint/apache-tomcat-8.5.43/webapps/ROOT.war] has finished in [9,035] ms
04-Jun-2020 13:48:16.580 INFO [localhost-startStop-1-SendThread(localhost.localdomain:2181)] org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading Illegal access: this web application instance has been stopped already. Could not load [org.apache.zookeeper.server.ZooTrace]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
java.lang.IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load [org.apache.zookeeper.server.ZooTrace]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1380)
at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1368)
at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1220)
at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1182)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1188)
0404-Jun-2020 13:48:16.589 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-9090"]
04-Jun-2020 13:48:16.631 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-nio-8009"]
04-Jun-2020 13:48:16.641 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 19759 ms
04-Jun-2020 13:48:16.643 INFO [localhost-startStop-1-SendThread(<IP_ADDRESS>:2181)] org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading Illegal access: this web application instance has been stopped already. Could not load [org.apache.hadoop.hbase.shaded.org.apache.zookeeper.server.ZooTrace]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
java.lang.IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load [org.apache.hadoop.hbase.shaded.org.apache.zookeeper.server.ZooTrace]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1380)
at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1368)
at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1220)
at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1182)
at org.apache.hadoop.hbase.shaded.org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1128)

Thanks, I'll test with increasing log level with logging.properties.
Do I need a standalone Zookeeper Server, or HBase provides Zookeeper services ?
In this case, is export JAVA_OPTS="-Dpinpoint.zookeeper.address=<IP_ADDRESS>" the correct
setting ?
Thanks

I am also facing the same issue, Please suggest

webAppRootKey
SomeUniqueValue

Your solution worked @ofauchon


rpm

https://earthly.dev/blog/creating-and-hosting-your-own-rpm-packages-and-yum-repo/
https://linuxconfig.org/how-to-create-a-custom-rpm-repository-on-linux
Creates the rpm artifacts:
$ apt install rpm createrepo_c
$ cd /path/to/ppa && mkdir rpm
$ cd rpm && cp <my_rpm> . && createrepo_c .`

TODO:

sign
make synthclient.repo configuration file and host it at repo root.

@Ravna For signing the package itself, there's an instruction:
rpm --addsign ~/example/packages/*.rpm in https://earthly.dev/blog/creating-and-hosting-your-own-rpm-packages-and-yum-repo/ under section 2 "creating a repo"
In that section there's also a step to sign the metadata with gpg --detach-sign --armor repodata/repomd.xml
I'll make a synthclient.repo file shortly.

Sounds similar to what I'm doing for the .deb.  About to be on a call for two hours but will investigate when I'm off.


check behavior of integrator settings panel in 4.0

To work around issue #153, a line that could be updating the integrator settings panel in CMC, RRA was commented out. Seems hard to test when most files we have use defaults. This is a place holder to check the behavior vs. 3.3

Check that integrator settings behave correctly.

@aymanhab could you provide more details about what we should test

The call that was removed was to "use time steps from states file", the checkbox is unused except in ForwardTool. We need to make sure this continues to function properly in ForwardTool  (if we have test data/files)

Im not entirely sure what the expected behavior is here- when the 'Use time steps from states file' is checked, what is supposed to happen?
There is no input states file for FWDTool; there is an initial states file, is that what is meant? My first thought is that I should be able to input a full states file and get the exact time steps from the file- so the time steps seen in the output states file from FWDTool, should match exactly the time steps from some (arbitrary) input states file.
If so that is not what is currently occurring. I specify a states file that I generated with a constant step size in the 'Initial State' dialogue box;

I check the box for  "use time steps from states file".  When I run the tool, I get a strange result and with the output state looking like this;

Like I mentioned above, I would expect that the output state would have the exact time steps as the input state, which isn't happening here.
Let me know if that is not the correct use case and we can drill down on the changes that need to be made for the test. Thanks!

@jimmyDunne I'd say the main reference/documentation is what happens in 3.3 since the behavior is undocumented elsewhere and this is rarely used functionality AFAIK.

I tested the files in 3.3 and got completely erroneous results (the model starts below the floor and shoots upward)

The functionality is broken in 3.3 as well as in 4.0 so we have an opportunity to define the behavior now :)
A few candidate solutions;
(1) We get rid of the checkbox all together since it is not clear what the feature even is.
(2) We keep "Use time steps from states file", and when someone checks the box the output file step sizes must match the input step sizes from the file.
(3) We keep "Use time steps from states file", rename it to "Use initial time step from initial states file", and set the step size to a constant rate from the initial states file.

If it is rarely used, undocumented and the expected behavior is not well-known, I vote to remove it.
An improvement would be an option to use a fixed reporting interval, which we could pass to underlying reporters. This could be a feature for 4.1.

Removed in PR #702

@aymanhab Could you explain what needs to be tested for this one?

Verified using forward simulations of the ToyDropLanding model.

the option to "Use time steps from states file" has been removed.
some integrator settings have the expected effects:

setting max and min step size results in fixed-time step integration
tightening the accuracy increases the number of integration steps

The "Maximum number of steps" setting appears to have no effect (also in 3.3). Opened core #2228 to track.

@aseth1 I will mark this one as verified on windows and mac since you opened the additional issue.


fix: update outdated link to Celestia docs

Hello,
I've found, that link to Celestia docs is not working, this PR fixes it.

Without any comment ???


[BUG] Solving dependency errors to be able to run code

Description
This is an issue with the packackages.json, and we would love to have assistance on how to navigate and fix this error so that when cloning this repo for the first time and running npm i, the following screenshot doesn't show these errors, and additionally this issue is affecting the preview deployment from being built.
Screenshots

Checklist

[X] I have checked for duplicate issues
[X] I have read the Contribution Guidelines
[ ] I am willing to work on this issue (optional)

I've looked into the problem with the packages.json file, and I want to help fix it. I understand how crucial it is to have a smooth experience when they clone the repository and deploy the preview.
I'm ready to dig into the issue and find a solution. If you have more details or information that could help, please share. I'll keep you posted on what I find, and once it's sorted, I'll submit a pull request.
Could you please assign this issue to me? I'm eager to contribute to the project. Thanks!

Thank you so much for the update! I really appreciate your guidance. I'm open to being tagged for the first claim on the new issues you plan to create. 💜

Thank you so much for the update! I really appreciate your guidance. I'm open to being tagged for the first claim on the new issues you plan to create. 💜

Excellent! How would you like to assist with adding a button for directing users on the main page to the Contributors Map page?

This issue has been successfully closed by contributor @ben-dh3 from pull request #181


llm.get_model() should return default model, make get_default_model()/set_default_model() documented APIs

The default model stuff is currently in llm/cli.py but it should be part of LLM core instead.
This should work:
import llm
model = llm.get_model() # Defaults to `gpt-4o-mini` or whatever was set as default
print(model.prompt("hi"))

Inspired by this change:

#552

Updated documentation: https://github.com/simonw/llm/blob/6deed8f97680281433abb158fe023c2bf225d99d/docs/python-api.md


Add better docs

Just saw that you released subscription for Android, will IOS come soon also? And does the documentation work for subscription?

iOS will come in the next few days. Subscriptions should work with the buy function.

Just tried with a subscription like in the docs but it says: Not working? Check that you set up in app purchases...
And so I tried with a normal IAP and that it could find and fetch.
List<String> productIds = [Constants.subscription30];

IAPResponse response = await FlutterIap.fetchProducts(productIds);
productIds = response.products
    .map((IAPProduct product) => product.productIdentifier)
    .toList();

This returned no product but I have an active subscription in the play console

Thanks. I'll look into this.

Also get type EfficientLengthFollowedByIterable<Widget> is not a subtype of type 'List<Widget>' from the .followedBy(list)


Add dockerfile for HTTP fault injector

HTTP fault injector is used in storage stress tests for Java. To simplify and speed up the test setup, we'd like to build a docker image for it and reuse it across test runs.

Thank you! Can you also add an entry to the pipeline so we can auto-build/publish? https://github.com/Azure/azure-sdk-tools/blob/main/eng/containers/ci.yml#L2

Fixes #7187


Retrieve organizational root OU and master account programmatically

At the moment we need to provide the root OU id and the master account ID to the script. It should be possible to retrieve this from the organizations API using the describe_organization() method.

master account id is retrieved automatically from release https://github.com/thiezn/awsaccountmgr/releases/tag/v0.0.5


Design Azure Event Hub Connector

Description:
$subject

Please find the design at https://docs.google.com/document/d/1yfFwSkaLtcJAGSHDzi-shsYzrnaI8jwFTDCxiL6ecGo/edit?usp=sharing


Add different compilers support

Add support for different compilers in the script to choose from

The compilers are to be selected from https://gitlab.com/stormbreaker-project/google-clang


chore(package): upgrade axe-core

As requested in https://github.com/crawlkit/runner-axe/issues/147

Thanks! Are you sure the HTML lang attribute is correctly represented with no errors in 2.x?

didn't look into it that much. just looked at what the response was :)

turned out that the rule name had changed. i've fixed that now. so should be good to merge!

Thank you @badtant - new release should be imminent - let me know if it worked, on phone only.

doesn't seem to be any new release. so please look at that :)

Semantic release failed ;(
> semantic-release pre && npm publish && semantic-release post
npm ERR! publish Failed PUT 401
npm ERR! Linux 4.8.12-040812-generic
npm ERR! argv "/home/travis/.nvm/versions/node/v4.7.2/bin/node" "/home/travis/.nvm/versions/node/v4.7.2/bin/npm" "publish"
npm ERR! node v4.7.2
npm ERR! npm  v2.15.11
npm ERR! code E401
npm ERR! You must be logged in to publish packages : crawlkit-runner-axe
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>
npm ERR! Please include the following file with any support request:
npm ERR!     /home/travis/build/crawlkit/runner-axe/npm-debug.log
npm ERR! Linux 4.8.12-040812-generic
npm ERR! argv "/home/travis/.nvm/versions/node/v4.7.2/bin/node" "/home/travis/.nvm/versions/node/v4.7.2/bin/npm" "run" "semantic-release"
npm ERR! node v4.7.2
npm ERR! npm  v2.15.11
npm ERR! code ELIFECYCLE
npm ERR! crawlkit-runner-axe@ semantic-release: `semantic-release pre && npm publish && semantic-release post`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the crawlkit-runner-axe@ semantic-release script 'semantic-release pre && npm publish && semantic-release post'.
npm ERR! This is most likely a problem with the crawlkit-runner-axe package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     semantic-release pre && npm publish && semantic-release post
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs crawlkit-runner-axe
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR!     npm owner ls crawlkit-runner-axe
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/travis/build/crawlkit/runner-axe/npm-debug.log

Will look at it once I am not mobile...

1.0.3 is out

I got this message when installing:
npm ERR<EMAIL_ADDRESS>postinstall: validate-commit-msg
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'validate-commit-msg'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the crawlkit-runner-axe package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     validate-commit-msg
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs crawlkit-runner-axe
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls crawlkit-runner-axe
npm ERR! There is likely additional logging output above.

This was a direct install in the cloned repo, right? Which version of node?
On 16 Jan. 2017 21:41, "Niklas Holmberg"<EMAIL_ADDRESS>wrote:

I got this message when installing:
npm ERR<EMAIL_ADDRESS>postinstall: validate-commit-msg
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script
'validate-commit-msg'.
npm ERR! Make sure you have the latest version of node.js and npm
installed.
npm ERR! If you do, this is most likely a problem with the
crawlkit-runner-axe package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! validate-commit-msg
npm ERR! You can get information on how to open an issue for this project
with:
npm ERR! npm bugs crawlkit-runner-axe
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls crawlkit-runner-axe
npm ERR! There is likely additional logging output above.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/crawlkit/runner-axe/pull/149#issuecomment-272827844,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALehlTw0-gW0ev52UDbrgr90wt88Rwpks5rS0llgaJpZM4LgcaR
.

No, it's when I have 1.0.3 as a dependency to my project. Node 6.9.1

fixed via 248b421 in 1.0.4, sorry about that.