Issue #SB-7869 feat: Design for front end review comments

@lakhanmandloi - Please review PR

@lakhanmandloi - Please review PR

@ttplsudhir pls resolve this conflict asap.

@lakhanmandloi Resolved


Remove sacrebleu from sockeye. Add dependency on pip's sacrebleu

Pull Request Checklist

[x] Changes are complete (if posting work-in-progress code, prefix your pull request title with '[WIP]'
until you can check this box.
[x] Unit tests pass (pytest)
[x] Were system tests modified? If so did you run these at least 5 times to account for the variation across runs?
[x] System tests pass (pytest test/system)
[x] Passed code style checking (./style-check.sh)
[x] You have considered writing a test
[x] Updated major/minor version in sockeye/__init__.py. Major version bump if this is a backwards incompatible change.
[x] Updated CHANGELOG.md

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Ah, I was halfway through doing this myself.
Would this pull down sacrebleu 1.3.0? I think with that I will introduce some backwards-incompatible method signatures, so that I can expand the set of smoothing techniques that are available (https://github.com/mjpost/sacreBLEU/tree/smoothing). I could submit the Sockeye changes, but want to make sure it won't accidentally break.

Good point @mjpost. It probably makes sense to fix the version in the requirements for now to <1.3.0. We can then consciously update to 1.3.0 by making the corresponding changes in Sockeye.


pwsh on debian buster - buffers problem in shell mode

Steps to reproduce
Run pwsh on Debian Buster (Debian 10) and starts to type commands.
Expected behavior
pwsh is usable, user can type commands and read outputs.
Actual behavior
There seems to be a problem with the buffers. Typing commands and running them does not work after the first one. Like if the buffers get unsynchronized with the inputs/outputs of the terminal.
Environment data
I reproduce this problem with a snap install of pwsh and with the tar.zf archive.
PS /opt> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.2.3
PSEdition                      Core
GitCommitId                    6.2.3
OS                             Linux 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2 (2019-08-28)
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

@gvcgael Can you remove PSReadline module ( Remove-Module PSReadline ) and test again?

Ok, it seems that the problems comes from my setup.
I connect from Git bash via SSH to my Debian buster VM. In this case, I get these buffers problem.
Using directly the console, powershell behaviour is ok.
Any idea what could be the cause ?

I guess the scenario was never tested.
At first we should check that C# API works right in the scenario. You could create simple C# application and check that Console.ReadKey() and Readline() methods work well.

Ok, it seems that I was wrong. It comes from the fact that I run git bash on Visual Studio Code.
Outside of studio code, it behaves properly. So it seems to come from the terminal integrated in VSC.

So it seems to come from the terminal integrated in VSC.

@TylerLeonhardt In which repository should we track this?

@gvcgael are you using the "PowerShell Integrated Console" that is exposed via the PowerShell extension for VSCode?
Or are you using VSCode's integrated terminal which is just running pwsh/powershell?
You can tell by looking at the little drop down at the top right of the terminal pane.

Hello,
I'm using VSCode Git bash integrated terminal, from which I connect to the VM where I run pwsh.


[in progress] Send an email to the core members of the collective to approve expense

Fixes https://github.com/OpenCollective/opencollective
It uses JWT token to automatically log in the website.
So we need a new page on the website /:slug/expenses/:expenseId/approve that would approve the expense if logged in and then redirect to /:slug/expenses/:expenseId.
@carlosascari is that something that you can do?

Sure can however I don't believe I'll get to it this week, is that alright?

Already did this... closing.


Don't require Git from user/user-config-system

Since it was unused, there's no reason to load it.  The only other solution to #34 that I can think of is to make this require optional.
Closes #34.

I'm going to merge this without review since #34 is a breaking issue for me.


Resizing messes up multi-point lines

Not sure if this is a regression...

repro: https://excalidraw.com/#json=5419770895663104,6V0pnKrRHUwBnufr4kCD4w

It wasn't working ideally, but definitely not like this. The regression seems to have been introduced in https://github.com/excalidraw/excalidraw/pull/955 during rewrite to immutable objects I believe.
/cc @petehunt


Add reST language (fix #552)

Examples preview:

I suspect that this could be simplified a lot, but merging anyway, since we don’t have a definition for reST. Thanks so much!

@Golmote Thanks so much!

@LeaVerou Yes, I know this looks overcomplicated. But those kind of markup languages (markdown, rest, textile, etc.) are quite hard to highlight, since they are merged with raw text...
Feel free to suggest some simplifications if you have the time to review this deeply. ;)


fix: handle "." in path lookup

Such lookup usually happens when reading a preopened directory entries through wasi-libc

I just needed to update the binary artifacts 😅


WebSocket doesn't accept secure sockets

Right now, the deferred then callback in Client\WebSocket::open expects a \React\Stream\Stream argument. However, when working with secure WebSockets (wss://), the argument is instead a \React\Stream\SecureStream.
As far as I can see, this should expect a \React\Stream\DuplexStreamInterface instead. Any objections to changing this?

wss not work for me too, errors:
"PHP message: PHP Catchable fatal error: Argument 1 passed to Devristo\Phpws\Client\WebSocket::Devristo\Phpws\Client{closure}() must be an instance of React\Stream\Stream, instance of React\SocketClient\SecureStream given, called in /var/www//vendor/react/promise/src/FulfilledPromise.php on line 24 and defined in /var/www//vendor/devristo/phpws/src/Devristo/Phpws/Client/WebSocket.php on line 95" while reading response header from upstream, client: , server: *, request: "GET /api.php HTTP/1.1", upstream: "fastcgi://<IP_ADDRESS>:9000", host: ""

As far as I can see, this should expect a \React\Stream\DuplexStreamInterface instead. Any objections to changing this?

Changing this to a DuplexStreamInterface should fix this, however this is a BC break and requires a dependency on react/stream: >= 0.4.2, < 0.5.0. This is caused by a BC break in react/socket-client (https://github.com/reactphp/socket-client/issues/21), suggested fix is in https://github.com/reactphp/socket-client/pull/25.

This works!

will that be merged?


Path collision on git clone

$ git clone git@github.com:wrouesnel/postgres_exporter.git
Cloning into 'postgres_exporter'...
Warning: Permanently added 'github.com,<IP_ADDRESS>' (RSA) to the list of known hosts.
remote: Enumerating objects: 2946, done.
remote: Total 2946 (delta 0), reused 0 (delta 0), pack-reused 2946
Receiving objects: 100% (2946/2946), 6.48 MiB | 3.71 MiB/s, done.
Resolving deltas: 100% (1087/1087), done.
warning: the following paths have collided (e.g. case-sensitive paths
on a case-insensitive filesystem) and only one from the same
colliding group is in the working tree:

  'vendor/github.com/Sirupsen/logrus/alt_exit.go'
  'vendor/github.com/sirupsen/logrus/alt_exit.go'
  'vendor/github.com/Sirupsen/logrus/appveyor.yml'
  'vendor/github.com/sirupsen/logrus/appveyor.yml'
  'vendor/github.com/Sirupsen/logrus/CHANGELOG.md'
  'vendor/github.com/sirupsen/logrus/CHANGELOG.md'
  'vendor/github.com/Sirupsen/logrus/doc.go'
  'vendor/github.com/sirupsen/logrus/doc.go'
  'vendor/github.com/Sirupsen/logrus/entry.go'
  'vendor/github.com/sirupsen/logrus/entry.go'
  'vendor/github.com/Sirupsen/logrus/exported.go'
  'vendor/github.com/sirupsen/logrus/exported.go'
  'vendor/github.com/Sirupsen/logrus/formatter.go'
  'vendor/github.com/sirupsen/logrus/formatter.go'
  'vendor/github.com/Sirupsen/logrus/hooks.go'
  'vendor/github.com/sirupsen/logrus/hooks.go'
  'vendor/github.com/Sirupsen/logrus/json_formatter.go'
  'vendor/github.com/sirupsen/logrus/json_formatter.go'
  'vendor/github.com/Sirupsen/logrus/LICENSE'
  'vendor/github.com/sirupsen/logrus/LICENSE'
  'vendor/github.com/Sirupsen/logrus/logger.go'
  'vendor/github.com/sirupsen/logrus/logger.go'
  'vendor/github.com/Sirupsen/logrus/logrus.go'
  'vendor/github.com/sirupsen/logrus/logrus.go'
  'vendor/github.com/Sirupsen/logrus/README.md'
  'vendor/github.com/sirupsen/logrus/README.md'
  'vendor/github.com/Sirupsen/logrus/terminal_bsd.go'
  'vendor/github.com/sirupsen/logrus/terminal_bsd.go'
  'vendor/github.com/Sirupsen/logrus/terminal_linux.go'
  'vendor/github.com/sirupsen/logrus/terminal_linux.go'
  'vendor/github.com/Sirupsen/logrus/text_formatter.go'
  'vendor/github.com/sirupsen/logrus/text_formatter.go'
  'vendor/github.com/Sirupsen/logrus/writer.go'
  'vendor/github.com/sirupsen/logrus/writer.go'

Not a lot I can do about this - logrus has created an interesting vendoring situation since the name really did change.


add Javadoc step, add Java 8 & 11 matrix build, cleanup names

Change log description
Add Javadoc step from Travis CI. Add Java 8 and Java 11 matrix build. Improve step names.
Purpose of the change
Improve Actions CI.
What the code does
Runs javadocs gradle task. Sets up a matrix of 8 & 11 to run steps in parallel.
How to verify it
See this PR.

These changes have been incorporated into PR #4.


[Image_v1.5]: Notebook Porting

Initial pull request for jupyter notebook porting to new architecture

The repository should be forked off of xilinx/PYNQ instead of PeterOgden/PYNQ.
New Pull request created based of the new repository forked off xilinx/PYNQ : #319

reopening in #319


🐛 [firebase_dynamic_links] App cannot push routes from inside FirebaseDynamicLinks.instance.onLink

Bug report
Both Android and iOS receive the deep link successfully, but on iOS, my app cannot navigate to a page if the invoked handler is the one defined in FirebaseDynamicLinks.instance.onLink. It is able to navigate successfully if the handler is the one called as part of App.initState(), which means I can only navigate once in the application's lifetime.
This issue does not happen in the Android version.
Steps to reproduce
Steps to reproduce the behavior:

Launch the application from scratch (whether with a deep link or not). Minimize the app.
Open a deep link.

Expected behavior
The application should navigate to the desired route.

Additional context
We're using a layer of indirection in MaterialApp to customize API endpoints between staging and production environments.
I've tried using a GlobalKey to fetch the MaterialApp's context, but it still doesn't work.

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 unknown, 1.20.3, on Mac OS X 10.14.6 18G6042, locale es-AR)
[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, set ANDROID_SDK_ROOT to that location.
      You may also want to add it to your PATH environment variable.

[✓] Xcode - develop for iOS and macOS (Xcode 11.3.1)
[!] Android Studio (not installed)
[✓] Connected device (1 available)

! Doctor found issues in 2 categories.

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.9.2
Flutter SDK 1.20.3
test_app 4.2.2+438

dependencies:
- advertising_id 0.9.2 [flutter]
- apple_sign_in 0.1.0 [flutter]
- background_fetch 0.3.2 [flutter]
- cached_network_image 2.0.0 [flutter flutter_cache_manager]
- carousel_pro 1.0.0 [flutter]
- carousel_slider 1.4.1 [flutter]
- csv 4.0.3
- device_apps 1.0.9 [flutter]
- device_info 0.4.2+1 [flutter]
- facebook_app_events 0.6.0 [flutter]
- firebase_analytics 6.0.0 [meta flutter firebase_core firebase_analytics_web firebase_analytics_platform_interface]
- firebase_core 0.5.2 [firebase_core_platform_interface flutter quiver meta firebase_core_web]
- firebase_crashlytics 0.1.3+3 [flutter stack_trace]
- firebase_dynamic_links 0.6.2 [flutter firebase_core]
- firebase_messaging 6.0.13 [meta platform flutter]
- flare_flutter 2.0.1 [flutter flare_dart meta]
- flutter 0.0.0 [characters collection meta typed_data vector_math sky_engine]
- flutter_animation_progress_bar 1.0.0 [flutter]
- flutter_app_badger 1.1.2 [flutter]
- flutter_chips_input 1.9.1 [flutter]
- flutter_facebook_login 3.0.0 [flutter collection]
- flutter_form_builder 3.6.1 [flutter flutter_typeahead intl sy_flutter_widgets flutter_chips_input datetime_picker_formfield validators date_range_picker]
- flutter_launcher_icons 0.7.4 [image args yaml]
- flutter_linkify 2.1.0 [flutter linkify]
- flutter_local_notifications 1.4.0 [flutter platform flutter_local_notifications_platform_interface]
- flutter_localizations 0.0.0 [flutter intl characters collection meta path typed_data vector_math]
- flutter_markdown 0.3.4 [flutter markdown meta path]
- flutter_native_splash 0.1.9 [yaml image color]
- font_awesome_flutter 8.7.0 [flutter]
- geolocator 5.3.0 [flutter meta equatable google_api_availability location_permissions vector_math]
- google_sign_in 4.2.0 [google_sign_in_platform_interface flutter meta google_sign_in_web]
- horizontal_blocked_scroll_physics 3.0.0 [flutter pedantic]
- image_cropper 1.2.1 [flutter]
- image_picker 0.6.3+4 [flutter flutter_plugin_android_lifecycle]
- intl 0.16.1 [path]
- intl_phone_number_input 0.2.1 [flutter provider libphonenumber]
- jiffy 2.2.0 [intl]
- native_shared_preferences 1.0.4 [flutter meta]
- package_info 0.4.0+16 [flutter]
- path 1.7.0
- percent_indicator 2.1.1+1 [flutter]
- permission_handler 5.0.0+hotfix.3 [flutter meta permission_handler_platform_interface]
- petitparser 2.4.0 [meta]
- photo_view 0.9.2 [flutter]
- shared_preferences 0.5.8 [meta flutter shared_preferences_platform_interface shared_preferences_linux shared_preferences_macos shared_preferences_web]
- sleek_circular_slider 1.1.0 [flutter]
- sqflite 1.3.0 [flutter sqflite_common path]
- step_progress_indicator 0.2.1+4 [flutter]
- super_tooltip 0.9.0 [flutter]
- timeago 2.0.26
- tuple 1.0.3 [quiver]
- url_launcher 5.4.2 [flutter url_launcher_platform_interface url_launcher_web url_launcher_macos]
- webview_flutter 0.3.19+9 [flutter]

dev dependencies:
- build_web_compilers 2.11.0 [analyzer archive bazel_worker build build_config build_modules collection glob js logging meta path pool scratch_space source_maps source_span stack_trace]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher meta source_span stream_channel string_scanner term_glyph typed_data]
- intl_translation 0.17.9 [analyzer args dart_style intl path petitparser]
- mockito 4.1.1 [collection matcher meta test_api]
- sqflite_ffi_test 0.3.0-dev.1 [flutter sqflite_common_ffi sqflite path synchronized]
- test 1.15.2 [analyzer async boolean_selector coverage http http_multi_server io js node_preamble package_config path pedantic pool shelf shelf_packages_handler shelf_static shelf_web_socket source_span stack_trace stream_channel typed_data web_socket_channel webkit_inspection_protocol yaml test_api test_core]

transitive dependencies:
- _fe_analyzer_shared 7.0.0 [meta]
- analyzer 0.39.17 [_fe_analyzer_shared args charcode cli_util collection convert crypto glob html meta package_config path pub_semver source_span watcher yaml]
- archive 2.0.13 [crypto args path]
- args 1.6.0
- async 2.4.2 [collection]
- bazel_worker 0.1.25 [async pedantic protobuf]
- boolean_selector 2.0.0 [source_span string_scanner]
- build 1.3.0 [analyzer async convert crypto logging meta path glob]
- build_config 0.4.2 [checked_yaml json_annotation meta path pubspec_parse yaml]
- build_modules 2.10.1 [analyzer async bazel_worker build build_config collection crypto glob graphs json_annotation logging meta path pedantic scratch_space]
- built_collection 4.3.2 [collection quiver]
- built_value 7.0.9 [built_collection collection fixnum quiver]
- characters 1.0.0
- charcode 1.1.3
- checked_yaml 1.0.2 [json_annotation source_span yaml]
- cli_util 0.2.0 [path]
- clock 1.0.1 [meta]
- collection 1.14.13
- color 2.1.1
- convert 2.1.1 [charcode typed_data]
- coverage 0.13.9 [args logging package_config path source_maps stack_trace vm_service]
- crypto 2.1.4 [collection convert typed_data]
- csslib 0.16.1 [source_span]
- dart_style 1.3.3 [analyzer args path source_span]
- date_range_picker 1.0.6 [flutter]
- datetime_picker_formfield 1.0.0 [flutter intl]
- equatable 1.1.1 [collection meta]
- fake_async 1.1.0 [clock collection]
- ffi 0.1.3
- file 5.2.1 [intl meta path]
- firebase 7.3.0 [http http_parser js]
- firebase_analytics_platform_interface 1.0.3 [flutter meta]
- firebase_analytics_web 0.1.1 [flutter flutter_web_plugins firebase firebase_analytics_platform_interface meta]
- firebase_core_platform_interface 2.0.0 [flutter meta plugin_platform_interface quiver]
- firebase_core_web 0.2.1 [firebase_core_platform_interface flutter flutter_web_plugins meta js]
- fixnum 0.10.11
- flare_dart 2.3.3
- flutter_cache_manager 1.1.3 [flutter path_provider uuid http path sqflite]
- flutter_keyboard_visibility 0.7.0 [flutter]
- flutter_local_notifications_platform_interface 1.0.1 [flutter plugin_platform_interface]
- flutter_plugin_android_lifecycle 1.0.6 [flutter]
- flutter_typeahead 1.8.0 [flutter flutter_keyboard_visibility]
- flutter_web_plugins 0.0.0 [flutter characters collection meta typed_data vector_math]
- glob 1.2.0 [async collection node_io path pedantic string_scanner]
- google_api_availability 2.0.3 [flutter]
- google_sign_in_platform_interface 1.1.0 [flutter meta quiver]
- google_sign_in_web 0.8.4 [google_sign_in_platform_interface flutter flutter_web_plugins meta js]
- graphs 0.2.0
- html 0.14.0+3 [csslib source_span]
- http 0.12.0+4 [async http_parser path pedantic]
- http_multi_server 2.2.0 [async]
- http_parser 3.1.3 [charcode collection source_span string_scanner typed_data]
- image 2.1.12 [archive xml]
- io 0.3.3 [charcode meta path string_scanner]
- js 0.6.1+1
- json_annotation 3.0.1
- libphonenumber 1.0.1 [flutter built_value]
- linkify 1.0.1
- location_permissions 2.0.5 [flutter meta]
- logging 0.11.4
- markdown 2.1.3 [args charcode]
- matcher 0.12.8 [stack_trace]
- meta 1.1.8
- mime 0.9.6+3
- moor 2.4.2 [meta convert collection synchronized pedantic]
- moor_ffi 0.4.0 [moor ffi collection meta]
- nested 0.0.4 [flutter]
- node_interop 1.0.3 [js]
- node_io 1.0.1+2 [node_interop path]
- node_preamble 1.4.8
- package_config 1.9.2 [path charcode]
- package_resolver 1.0.10 [collection http package_config path]
- path_provider 1.6.5 [flutter path_provider_platform_interface path_provider_macos]
- path_provider_linux 0.0.1+2 [path xdg_directories path_provider_platform_interface flutter]
- path_provider_macos 0.0.4 [flutter]
- path_provider_platform_interface 1.0.1 [flutter meta platform plugin_platform_interface]
- pedantic 1.8.0+1
- permission_handler_platform_interface 2.0.0 [flutter meta plugin_platform_interface]
- platform 2.2.1
- plugin_platform_interface 1.0.2 [meta]
- pool 1.4.0 [async stack_trace]
- process 3.0.13 [file intl meta path platform]
- protobuf 1.0.1 [fixnum]
- provider 4.0.4 [flutter nested collection]
- pub_semver 1.4.4 [collection]
- pubspec_parse 0.1.5 [checked_yaml json_annotation pub_semver yaml]
- quiver 2.1.3 [matcher meta]
- scratch_space 0.0.4+2 [build crypto path pedantic pool]
- shared_preferences_linux 0.0.2+1 [file flutter meta path path_provider_linux shared_preferences_platform_interface]
- shared_preferences_macos 0.0.1+6 [shared_preferences_platform_interface flutter]
- shared_preferences_platform_interface 1.0.3 [meta flutter]
- shared_preferences_web 0.1.2+4 [shared_preferences_platform_interface flutter flutter_web_plugins meta]
- shelf 0.7.5 [async collection http_parser path stack_trace stream_channel]
- shelf_packages_handler 1.0.4 [async path shelf shelf_static package_resolver]
- shelf_static 0.2.8 [convert http_parser mime path shelf]
- shelf_web_socket 0.2.3 [shelf web_socket_channel stream_channel]
- sky_engine 0.0.99
- source_map_stack_trace 2.0.0 [path stack_trace source_maps]
- source_maps 0.10.9 [source_span]
- source_span 1.7.0 [charcode collection meta path term_glyph]
- sqflite_common 1.0.0+1 [synchronized path meta]
- sqflite_common_ffi 1.0.0+1 [moor_ffi sqflite_common synchronized path meta]
- stack_trace 1.9.5 [path]
- stream_channel 2.0.0 [async]
- string_scanner 1.0.5 [charcode meta source_span]
- sy_flutter_widgets 0.1.4 [flutter]
- synchronized 2.2.0
- term_glyph 1.1.0
- test_api 0.2.17 [async boolean_selector collection meta path source_span stack_trace stream_channel string_scanner term_glyph matcher]
- test_core 0.3.10 [analyzer async args boolean_selector collection coverage glob io meta package_config path pedantic pool source_map_stack_trace source_maps source_span stack_trace stream_channel vm_service yaml matcher test_api]
- typed_data 1.2.0 [collection]
- url_launcher_macos 0.0.1+4 [flutter]
- url_launcher_platform_interface 1.0.6 [flutter meta plugin_platform_interface]
- url_launcher_web 0.1.1+1 [url_launcher_platform_interface flutter flutter_web_plugins meta]
- uuid 2.0.4 [crypto convert]
- validators 2.0.0+1
- vector_math 2.0.8
- vm_service 2.3.1 [meta]
- watcher 0.9.7+14 [async path pedantic]
- web_socket_channel 1.1.0 [async crypto stream_channel]
- webkit_inspection_protocol 0.5.3 [logging]
- xdg_directories 0.1.0 [path process flutter]
- xml 3.6.1 [collection convert meta petitparser]
- yaml 2.2.0 [charcode collection string_scanner source_span]

Hi @amyspark
Is there any error thrown or any relevant logs in flutter run -v or Xcode console?
The official example already includes navigation to a deep link from onLink that works for me on the latest flutter master 1.24.0-8.0.pre.291 with
  firebase_core: ^0.5.2
  firebase_dynamic_links: ^0.6.2
  url_launcher: ^5.7.10

flutter doctor -v
[✓] Flutter (Channel master, 1.24.0-8.0.pre.291, on Mac OS X 10.15.7 19H2 darwin-x64, locale en-GB)
    • Flutter version 1.24.0-8.0.pre.291 at /Users/markus/development/flutter_master
    • Framework revision c1042314a9 (2 hours ago), 2020-11-18 01:38:02 -0500
    • Engine revision 35a0b9fe68
    • Dart version 2.12.0 (build 2.12.0-50.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
    • Android SDK at /Users/markus/Library/Android/sdk
    • Platform android-30, build-tools 30.0.1
    • Java binary at: /Users/markus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.6858069/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

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

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Users/markus/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.6858069/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      � https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      � https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] Connected device (4 available)
    • Nevercode’s iPhone (mobile) • b668e524315069f3db3661ac11ff1f66afafebdb • ios            • iOS 14.2
    • macOS (desktop)             • macos                                    • darwin-x64     • Mac OS X 10.15.7 19H2 darwin-x64
    • Web Server (web)            • web-server                               • web-javascript • Flutter Tools
    • Chrome (web)                • chrome                                   • web-javascript • Google Chrome 86.0.4240.198

• No issues found!

If all else fails you could try starting from the official example with an unmodified flutter SDK and then adding your modifications in to see where the navigation stops working.
Thank you

Hi! I don't have much time to test right now with the new SDK, I'll reopen as soon as I can do it.


Fix Typo

Description of changes:
Fix typo
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks! Gonna merge soon!


Proposal: Outsourcing of examples and documentation

Hello @KingHenne, @fahrradflucht, @KnisterPeter,
In order to guarantee a high software quality we have expensive review processes, CI checks and code standards including 100% test coverage.
Our examples and documentation are currently still very rudimentary and difficult to understand. I believe that in order to improve the accessibility of this repository as quickly as possible we should be able to develop our documentation and examples more lightweight and faster.
For example, today I set up a minimal counter example, including a CodeSandbox environment:
https://codesandbox.io/s/github/clebert/feature-hub-counter
https://github.com/clebert/feature-hub-counter
So my suggestion is to remove the documentation and examples from this repo and develop them separately, with softer rules, faster. At the same time it reduces the size and complexity of this repo and we can continue to develop this software with high standards.

I have created a new organization: https://github.com/feature-hub
We can create all feature hub projects within this organization.
We should also move this repo.

As just decided in the Daily, we will remove the examples from this repo.


Acknowledgement of de.NBI cloud

Nothing technical, but I was just informed at another project, that we should acknowledge de.NBI somewhere for the hosting, e.g. in an impressum or footer.
And in a publication, something like this link should be added:
https://cloud.denbi.de/wiki/citation_and_publication/#citation-information

Of course! I can add it. I'll do that quick :)
So I put this?
‘This work was supported by the BMBF-funded de.NBI Cloud within the German Network for Bioinformatics Infrastructure (de.NBI) (031A532B, 031A533A, 031A533B, 031A534A, 031A535A, 031A537A, 031A537B, 031A537C, 031A537D, 031A538A)'
Can I remove the last part for ProteoBench? '(031A532B, 031A533A, 031A533B, 031A534A, 031A535A, 031A537A, 031A537B, 031A537C, 031A537D, 031A538A)'
And you may have to remind me for the publication.

These are the "real" grant numbers of the BMBF. But yes, leave them out on the home page and poster. But please keep them in a manuscript.

Actually, maybe for the home page I can be a bit more specific and add under the logos:
"This site is hosted by the BMBF-funded de.NBI Cloud within the German Network for Bioinformatics Infrastructure (de.NBI)"
?
You decide really, I'll do as you say

Yes, that sounds good for the homepage 👍


Upload windows wheels to PyPI on tagged builds

This PR adds automated upload of windows wheels from successful Appveyor jobs to PyPI.
Closes #88 #98 #101 #114 #118 #122
Also, it directly addresses several issues in dependent package repos, e.g.

onelogin/python3-saml#110
onelogin/python3-saml#186
onelogin/python3-saml#192

(maybe there's more of them)
Example of a tagged build on Appveyor and the resulting version on TestPyPI.
@bgaifullin @mehcode if you decide to merge the PR, you have to replace the authentication token first. I have generated my own for a test upload, it won't work anymore for the real uploads. Go to your PyPI account, generate a new API token, encrypt it on Appveyor and replace the value of TWINE_PASSWORD env var in .appveyor config.
I am also willing to maintain the PyPI uploads if you want to, add me to project maintainers on PyPI and I will organize the rest.

To anyone with installation issues on Windows: you can use the wheels I have built to test the installation. Run
$ pip install xmlsec --extra-index-url=https://test.pypi.org/simple

This will install a version 1.3.6.post2 which isn't on PyPI, thus the special tag. The wheels are built from current master and are usable already, but I wouldn't rely on TestPyPI for the long run as it cleans up the uploaded packages once in a while.

Another thing - I've added a small code change to fix building the wheels for Python 2.7; not that it matters much though as Python 2.7 is EOL anyway.

Obsolete, 1.3.7 includes windows wheels on PyPI.


Initial styleswitcher theme looks off

Note the discontinuous line and rectangle rendering.  This does curiously not happen with the other themes.

Yeah, that happens because of the tile stretch hint enabled by default in frames. This is fixed by setting the hint to false when using this tileset.
A more elaborate solution would be analysing the pixels in the filling tiles and detect automatically if they can be stretched. I'll do that later. Thanks for your report!


Disable or move item to left in Vertical Display

I use Surface Pro and switch to vertical mode frequently but Falcon will center icons by calculating vertical width, which will make it show less items on the taskbar.
Can I have an option to disable Falcon when in vertical mode or auto detect it?
thank you for developing this app making my windows looks beautiful

Hmm, don't know if i can detect that. I think what i can do is to have an option where you can set a width that would be skipped. Like if your resolution 1920x1080 holding it in landscape mode will be 1920 pixels wide and when you hold your screen in vertical mode it will be 1080 pixels wide. So if you put 1080 in that option and your resolution becomes 1080 pixels wide it will just stop centering.
And as soon it changes to anything else in this case 1920 pixels wide it will continue centering.
Conclusion:
Add option "Do not center when resolution equals ... pixels wide"

Hmm, don't know if i can detect that. I think what i can do is to have an option where you can set a width that would be skipped. Like if your resolution 1920x1080 holding it in landscape mode will be 1920 pixels wide and when you hold your screen in vertical mode it will be 1080 pixels wide. So if you put 1080 in that option and your resolution becomes 1080 pixels wide it will just stop centering.
And as soon it changes to anything else in this case 1920 pixels wide it will continue centering.
Conclusion:
Add option "Do not center when resolution equals ... pixels wide"
GENIUS IDEA
once again, thank you for providing us a solution.

@vsnst Added it to the <IP_ADDRESS> pre-release. Can you test it out?
https://github.com/ChrisAnd1998/TaskbarX/releases/tag/<IP_ADDRESS>

@vsnst Added it to the <IP_ADDRESS> pre-release. Can you test it out?
https://github.com/ChrisAnd1998/TaskbarX/releases/tag/<IP_ADDRESS>

It works on my New Surface Pro (Runing 2004 Build19608.1006), but it took 23sec to update in both landscape and portrait mode.
How it happened?
I set the "Skip Resolution" to 1824 which is the width when the display switch to vertical mode. Once I thought it didn't work, all the icons disappear.
After 20sec those icons finally move to the left. Then, I rotated my Surface Pro switching to landscape mode, it takes the same 23sec to recover to center.
How to improved?
I hope when I switch to vertical(/portrait) mode, icons immediately appear on the left.
What has been improved?
In this build, CPU usage is surprisingly better than my current build(about 1.5%) on average. Good work
And I love the new UI, looks clean. Hope to see Fluent Design in TaskbarX as well.
Question
Does animation speed shorter or longer would consume lesser CPU, battery?

Thank you @Chris for taking time on my features request.

@vsnst Thx for testing! I'll look into this.
The use of animations don't make a difference on battery life but, someone requested it so i added it.

@vsnst Allright, i updated the pre-release <IP_ADDRESS> with the
Automation.ConnectionTimeout set to 1 second | default is 2 seconds
Automation.TransactionTimeout set to 1 second | default is 20 seconds

@vsnst Did you try it out already? I need to know so i can work on the next update. Sorry for pushing you ;)

@vsnst Did you try it out already? I need to know so i can work on the next update. Sorry for pushing you ;)

Sorry, I did not think you would be that fast fixing it.
I just tested, i can't feel the difference. I don't know if I had downloaded the wrong version, the about page said it is version <IP_ADDRESS>.

What i hoped was that this fixed it 😓

that's the one I downloaded, yeah, similar issue, about 15~20sec update.
maybe I need to clean the cache or something before I tested the pre-release?

@vsnst Nah, if you replaced the exe file and then re-run it then it should do what it's coded to. There is no cache. The weird thing is that if the display changes it should restart it's self after 1 second. This clearly doesn't happen or it's stuck on the beginning after the restart. Now i have no idea why it's waiting so long 😩.

@vsnst Nah, if you replaced the exe file and then re-run it then it should do what it's coded to. There is no cache. The weird thing is that if the display changes it should restart it's self after 1 second. This clearly doesn't happen or it's stuck on the beginning after the restart. Now i have no idea why it's waiting so long 😩.

that's alright, don't push yourself too hard on that.
It's already so much more useful to me.

@vsnst But, it's not perfect XD
Here is another try
Release.zip
Instead of finding all taskbars using the UIAutomation API it now finds it using EnumWindows Pinvoke Message

@vsnst But, it's not perfect XD
Here is another try
Release.zip
Instead of finding all taskbars using the UIAutomation API it now finds it using EnumWindows Pinvoke Message

This time much better, totally usable.
Vertical mode immediate move to left, except switching back takes 15sec, but this time icons won't disappear, I could live with that.
Thank you

Opps
seems Windows autorotation uses different dethod.
This time, if I rotate the Display, icons won't move.
But If I manually rotate the screen in the settings/ Intel graphics command center to switch it, it works

I did another test on surface pro. It didn't work well on Surface Book 2.
It actually work like above two on SP, no big issue.
It's weird ,I'll make another test when I get home.
Thank you

I have position of taskbar vertically on the left side and external monitor
look of the taskbar on ext 24' 1440 monitor:

look of the taskbar on internal laptop 14' monitor 1080:

don't know if i should start new bug or comment on this one
thank you for great work


several optional libraries are not included

From the latest run of the CI on the stable release of octopus  we see:
https://github.com/fangohr/octopus-in-docker/actions/runs/7268660840/job/19804911757
#24 0.511     <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
#24 0.511
#24 0.511                            Running octopus
#24 0.511
#24 0.511 Version                : 13.0
#24 0.511 Commit                 :
#24 0.511 Configuration time     : Tue Dec 19 23:13:36 UTC 2023
#24 0.511 Configuration options  : maxdim3 openmp mpi sse2 libxc_fxc libxc_kxc
#24 0.511 Optional libraries     : cgal etsf_io metis netcdf nlopt
#24 0.511 Architecture           : x86_64
#24 0.511 C compiler             : mpicc (gcc)
#24 0.511 C compiler flags       : -g -O2
#24 0.511 C++ compiler           : g++
#24 0.511 C++ compiler flags     : -g -O2
#24 0.511 Fortran compiler       : mpif90 (gfortran) (GCC version 10.2.1 20210110)
#24 0.511 Fortran compiler flags : -O3 -fopenmp
#24 0.511
#24 0.511           The octopus is swimming in buildkitsandbox (Linux)
#24 0.511
#24 0.511
#24 0.511             Calculation started on 2023/12/19 at 23:25:09

that the libraries elpa, scalapack, pfft are not included even though they are installed via Debian package.

Well spotted.
So we need to update the ./configure line. (Perhaps to re-use the configure line used for the Debian package?)

@iamashwin99 Could you add the correct flags to the configure line so that Octopus discovers the available libraries? You are probably the expert for this now...
If we have this in a script already somewhere, we could include the script here?

With the new script https://github.com/fangohr/octopus-in-docker/blob/main/install_octopus.sh , can this issue be closed?

Okay, thanks. I'll update the title, and we can keep the issue to remind us of the missing pfft.


Support Env registry and create from string

What type of PR is this：

[ ] bug
[ ] feature
[x] enhancement
[ ] others

Problem Summary(Required) ：

Support Env registry and create an instance of Env from string

[BE PR Coverage check]
:heart_eyes: pass : 0 / 0 (0%)

run starrocks_be_unittest


visualvm: 1.4 -> 1.4.1

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/visualvm/versions.
These checks were done:

built on NixOS
Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
found 1.4.1 with grep in /nix/store/a6lr7j812ja6z31lzkpr2j2hf6wc842c-visualvm-1.4.1
directory tree listing: https://gist.github.com/40c8f8eac649d32dcacc80c5e64dd0fe

cc @michalrus @moaxcp for review

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: visualvm
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-darwin (full log)
Attempted: visualvm
Partial log (click to expand)
building
no Makefile, doing nothing
installing
post-installation fixup
strip is /nix/store/kdff2gim6417493yha769kh00n63lnrw-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/gfzabph5623zpy439zc6269h5jyadgng-visualvm-1.4.1/bin
patching script interpreter paths in /nix/store/gfzabph5623zpy439zc6269h5jyadgng-visualvm-1.4.1
/nix/store/gfzabph5623zpy439zc6269h5jyadgng-visualvm-1.4.1/bin/.visualvm-wrapped: interpreter directive changed from "/bin/sh" to "/nix/store/r8bx3qf1bpncb14i9gzma4vr089pc3pv-bash-4.4-p19/bin/sh"
/nix/store/gfzabph5623zpy439zc6269h5jyadgng-visualvm-1.4.1/platform/lib/nbexec: interpreter directive changed from "/bin/sh" to "/nix/store/r8bx3qf1bpncb14i9gzma4vr089pc3pv-bash-4.4-p19/bin/sh"
/nix/store/gfzabph5623zpy439zc6269h5jyadgng-visualvm-1.4.1

Success on x86_64-linux (full log)
Attempted: visualvm
Partial log (click to expand)
shrinking /nix/store/5vfv0z5w0g2hgcs9g9n0chxi8nwhnyw7-visualvm-1.4.1/profiler/lib/deployed/jdk16/linux/libprofilerinterface.so
shrinking /nix/store/5vfv0z5w0g2hgcs9g9n0chxi8nwhnyw7-visualvm-1.4.1/profiler/lib/deployed/jdk16/solaris-amd64/libprofilerinterface.so
shrinking /nix/store/5vfv0z5w0g2hgcs9g9n0chxi8nwhnyw7-visualvm-1.4.1/profiler/lib/deployed/jdk16/linux-arm/libprofilerinterface.so
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/5vfv0z5w0g2hgcs9g9n0chxi8nwhnyw7-visualvm-1.4.1/bin
patching script interpreter paths in /nix/store/5vfv0z5w0g2hgcs9g9n0chxi8nwhnyw7-visualvm-1.4.1
/nix/store/5vfv0z5w0g2hgcs9g9n0chxi8nwhnyw7-visualvm-1.4.1/platform/lib/nbexec: interpreter directive changed from "/bin/sh" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/sh"
/nix/store/5vfv0z5w0g2hgcs9g9n0chxi8nwhnyw7-visualvm-1.4.1/bin/.visualvm-wrapped: interpreter directive changed from "/bin/sh" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/5vfv0z5w0g2hgcs9g9n0chxi8nwhnyw7-visualvm-1.4.1...
/nix/store/5vfv0z5w0g2hgcs9g9n0chxi8nwhnyw7-visualvm-1.4.1

LGTM :+1:


Deleting more objects

Moving changes from pr to branch in redhat-chaos org to be able to run with secrets

@tsebastiani @chaitanyaenr can you ptal, I have updated with pydoc and tests


Add PHP 7.2 support, drop HHVM

Update Travis configuration
Check Travis results

Related #36

@weierophinney could you please merge this pull request as it supports PHP 7.2

@froschdesign It can be closed now, as 2.7.0 has been released.


upload plugin using a key shortcut doesn't work

This may be an issue with other things as well.  I can't seem to get a key to work for upload even though it seems to be working in terms of saying in the UI that the shortcut is active.

Can I see a code sample and explain which keys you hit?


python3Packages.adafruit-platformdetect: 3.5.0 -> 3.6.0

Motivation for this change
Update to latest upstream release 3.6.0
Change log: https://github.com/adafruit/Adafruit_Python_PlatformDetect/releases/tag/3.6.0
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 119975 run on x86_64-linux 1

2 packages built:

python38Packages.adafruit-platformdetect
python39Packages.adafruit-platformdetect

Result of nixpkgs-review pr 119975 at b3e22b9c run on aarch64-linux 1

2 packages built successfully:

python38Packages.adafruit-platformdetect
python39Packages.adafruit-platformdetect


I Use it open a file and cursor is Thickening and i can‘t write in anything.

As a problem，if i change Typewriting to english and write in ‘ssss’,then i can write something.then i can't use "Ctrl + A" Shortcut key

i  me too,how to change

感觉是vscode开启了vim模式，试试输入q（退出vim模式）

Is it possible that you have the vim extension enabled?

This sounds like caused by an extension. Please report to them or delete it.


feat: verify remote report for oracle registration event

Verify Remote Report for Oracle Registration
Get nodePubKey and nodePubKeyRemoteReport from querying panacea-core
If the verification is passed, Vote Tx will be executed. (It will be implemented next branch)

@inchori
Just merge my PR #37 to yours. So, we are in the same boat :sunglasses:.


spin up returns an error with a trivial Grain module that works on Wasmtime

With the latest version of Grain, I get a Spin error with even the most trivial programs. (wasmtime works fine)
$ grain --version
0.5.2

main.gr:
print("content-type: text/plain")
print("")
print("Hello, World")

spin.toml:
spin_version = "1"
authors = ["Matt Butcher<EMAIL_ADDRESS>description = "Test Grain"
name = "mygrain"
trigger = { type = "http", base = "/" }
version = "0.1.0"

[[component]]
id = "mygrain"
source = "main.wasm"
[component.trigger]
route = "/..."
executor = { type = "wagi" }
[component.build]
command = "grain compile -o main.wasm main.gr"

Wasmtime:
$ wasmtime main.wasm
content-type: text/plain

Hello, World

Spin:
$ spin up
Error: Cannot create module for component mygrain from file /Users/technosophos/Code/Swift/test-spin-template/mygrain/main.wasm

Caused by:
    0: failed to parse WebAssembly module
    1: Invalid input WebAssembly code at offset 327: duplicate import name `wasi_snapshot_preview1::fd_write` already defined
Error: exit status: 1

Incidentally, using the --release flag on the Grain compiler seems to have fixed this issue. I am guessing that this may have to do with de-duplicating imports

I couldn't reproduce it using (with and w/o --release flag)
spin 0.5.0 (1ce374a 2022-09-20)
grain-linux-x64 0.5.3

Thanks @etehtsea - tried it here too, and I can't reproduce it either.  @technosophos I'm going to close this for now, but do reopen if you see it again!


Handle assertions in conditionals branches in Minitest/MultipleAssertions cop

These changes are to allow to have assertions like:
def test_foo
  if ActiveRecord::VERSION >= "7.0"
    assert ActiveRecord.old_foo_method(1, 2)
  else
    assert ActiveRecord.new_foo_method(1, 2)
  end
end

A recent example that inspired this - https://github.com/ixti/sidekiq-throttled/pull/142/files#diff-87c291ea2af263111982285d3dea3083faa62260cc6080cc5396f4bf82a37cf4R22-R27 (it is using rspec, but it does not matter)

Applied suggested changes. CI is failing, because rubocop now requires ruby 2.7, but this gem - ruby 2.6. So it is needed to first drop support for ruby 2.6 and then this PR can be updated.
Should I open a separate PR with that change or should you?

Should I open a separate PR with that change or should you?

The build error has been fixed by https://github.com/rubocop/rubocop-minitest/pull/250. Either way, I understand that the issue is unrelated to this PR change. Thank you :-)

Updated, now CI is green 🟢


License?

Hi all, thanks for this awesome library! May I ask what the license is for using it?

The license appears to be MIT. I'd argue that you can ignore the mention of "ISC" in package.json as it is the npm initdefault.

Thanks @mootari!


docs: add sado0823.github.io to showcase

Pre-flight checklist

[x] I have read the Contributing Guidelines on pull requests.
[ ] If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
[ ] If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

Test Plan

Test links

Deploy preview: https://deploy-preview-7584--docusaurus-2.netlify.app/
Related issues/PRs

💯
Seems you already optimized the image—very impressive! I just resized it to 640px to be consistent with others.

thanks ❤


Run init only once, won't redirect through /home

How do I get it to redirect to init? It doesn't at the moment. Tried restarted the server and the daemon, always just went to home.

You need to point your ipns somewhere else to reset, try
ipfs name publish QmUNLLsPACCz1vLxQVkXqqLX5R1X345qqfHbsf67hvA3Nn

Ok. How do I do that? Right now, I have two terminals running:
$ ipfs daemon
# And..
$ npm run serve

Should I cancel one, and run ipfs name ...? What information am I missing?

Just run it in a separate terminal

Ok. So, if I run that in another terminal, I need to cancel npm run serve and rerun it in order to not have init come up every time.
I don't understand why this needs to be done. Can you write up something about this? I think it should be in the Readme.

No, init should not appear every time in this branch, did you test it?

will merge this in the meantime

Ran daemon, ran server, init showed up once, then not again. Repointed ipns elsewhere without stopping or starting server, and init showed up twice, and then never again. Not sure why twice. On second time, ran ipfs object get... :
10:50 ~/src/starlog $ ipfs object get  $(ipfs name resolve)
{
  "Links": [
    {
      "Name": "log",
      "Hash": "QmQoSGNifuzm9fZ3vUFHHhrpn1fKxcKxonRit9vXVN7iJN",
      "Size": 432231
    }
  ],
  "Data": "{\"type\":\"starlog-feed\",\"feed\":\"QmXBgD6XuHDp2N5XMPcrnXxLtZgVz3rg2YitPEdY6DzZtw\",\"name\":\"

Which make sense. Confusing.


Interstate 75 support different refresh

I have a 64x32 panel (interestingly on the back it says P4-256*128-2121-A5) and it repeats rows and doesn't allow for full control of the panel with the interstate 75 W board.
The following code :
import hub75

WIDTH = 64
HEIGHT = 32

matrix = hub75.Hub75(WIDTH, HEIGHT, stb_invert=False)

matrix.start()
matrix.clear()

for x in range(WIDTH):
    matrix.set_pixel(x,0,255,0,0)
for x in range(WIDTH):
    matrix.set_pixel(x,2,0,255,0)
for x in range(WIDTH):
    matrix.set_pixel(x,8,0,0,255)
for x in range(WIDTH):
    matrix.set_pixel(x,10,0,255,0)
for x in range(WIDTH):
    matrix.set_pixel(x,16,255,0,255)
for x in range(WIDTH):
    matrix.set_pixel(x,18,0,255,255)
for x in range(WIDTH):
    matrix.set_pixel(x,24,128,128,255)
for x in range(WIDTH):
    matrix.set_pixel(x,26,128,255,128)

produces this output :

As you can see, the panel is reacting correctly to the colours, but instead of a 64*32 LCD I have a weirdly interleaved 64*8 board!
As I understand it, this could be the difference between a refresh rate of different boards, so it would be really nice to let us set that and then we can figure out a mapping that works.
[edit because I selected the wrong file for github!]

Hello! Is that a panel you've sourced from us, or from elsewhere?

This has come up before in #233 and #249 and the same problems apply here- a mixture of a desperate shortage of time, energy and hardware to test with.
The pixels are arranged internally like so:
https://github.com/pimoroni/pimoroni-pico/blob/f06d7c2e83debff09d5ac69969864e7e76dff95e/drivers/hub75/hub75.cpp#L47-L58
With an interleaved pattern reflecting the fact the panel is split into two logical sections- top and bottom- which are driven by shift register chains that handle WIDTH * 2 pixels for the top/bottom segments of the display.
Pretty much the best you can do right now if you're using MicroPython is fork this repo, delete the remapping code, let GitHub Actions spit you out a build and give it a go. Rinse & repeat.

@helgibbons it is an AliExpress panel I had from before the good ship started stocking them.
Thanks @Gadgetoid that feels like it will have an overly high cycle time for me too but at least I can start with a zero mapping and see if I can write to all the pixels without it.

That being said, I still don't think this will make a difference because I don't think it's the mapping that's the problem but the refresh rate.  Look carefully and you'll see I'm setting 64 pixels of red and getting 64*4 pixels of red.


TFBuildEngineModule is internal

No reason for TFBuildEngineModule to be internal. Should make it public, and will also make @patriksvensson happy :smile:

Should also rename it to TFBuildModule 😄

@patriksvensson Version 0.1.2 has been released and makes the newly-renamed TFBuildModule class public 👍

@agc93 Sweet :)


Update MULTI_NIC_SETUP.md

modified to show that STN only applies when all NICs are being grabbed by VPP - where one more more NICs remain for the kernel (the out of band management case) there is no need for STN.

Coverage remained the same at 76.71% when pulling 7a6159cf4333265d7742e93bb13390d6581b1816 on gilesheron-patch-4 into 22c60db66322646610998f140304f3cf4b0b1bde on master.


program to check palindrome in python

@IbadMukrom contribute here https://github.com/Ishaan28malik/Get-Dev-Resources


⚠ Mobitopup has degraded performance

In dabe0ba, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 6531 ms

Resolved: Mobitopup performance has improved in eaf6eb0.


bonfire: fix build

Motivation for this change
The requirement's constraint for pythonPackages.keyring didn't allow
keyring v11. However it has been bumped in 93a16a2ace93fd96866d98181a07a8c5a779acce
by @FRidh.
Current failure: https://nix-cache.s3.amazonaws.com/log/2nw5adfx86jwiax32mn11kqpc35xwhsh-bonfire-unstable-2017-01-19.drv
See ticket #36453
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

see discussion (and patch) in https://github.com/blue-yonder/bonfire/pull/24 for further reference.

also affects 18.03?

@GrahamcOfBorg build pythonPackages.bonfire

Failure on x86_64-darwin (full log)
Partial log (click to expand)
error: attribute 'bonfire' in selection path 'pythonPackages.bonfire' not found

Failure on aarch64-linux (full log)
Partial log (click to expand)
error: attribute 'bonfire' in selection path 'pythonPackages.bonfire' not found

Failure on x86_64-darwin (full log)
Partial log (click to expand)
error: attribute 'bonfire' in selection path 'pythonPackages.bonfire' not found

Failure on x86_64-linux (full log)
Partial log (click to expand)
error: attribute ‘bonfire’ in selection path ‘pythonPackages.bonfire’ not found

Failure on x86_64-linux (full log)
Partial log (click to expand)
error: attribute ‘bonfire’ in selection path ‘pythonPackages.bonfire’ not found

Failure on aarch64-linux (full log)
Partial log (click to expand)
error: attribute 'bonfire' in selection path 'pythonPackages.bonfire' not found

@GrahamcOfBorg build bonfire

Failure on x86_64-darwin (full log)
Partial log (click to expand)
Package ‘bonfire-unstable-2017-01-19’ in /Users/graham/nix-borg/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-ndnd/pkgs/tools/misc/bonfire/default.nix:38 is not supported on ‘x86_64-darwin’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Partial log (click to expand)

=============================== warnings summary ===============================
None
  [pytest] section in setup.cfg files is deprecated, use [tool:pytest] instead.

-- Docs: http://doc.pytest.org/en/latest/warnings.html
==================== 17 passed, 1 warnings in 3.32 seconds =====================
/nix/store/l6w82h1y7jh6di2h5sxgr8m7rdjykki7-python3.6-bootstrapped-pip-9.0.1/lib/python3.6/site-packages/setuptools/dist.py:364: UserWarning: The version specified ('2017-01-19') is an invalid version, this may not work as expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 for more details.
  "details." % self.metadata.version
/nix/store/5n01q6brxv3fz02ir2fxd7bjyg3285c4-bonfire-unstable-2017-01-19

Success on aarch64-linux (full log)
Partial log (click to expand)

=============================== warnings summary ===============================
None
  [pytest] section in setup.cfg files is deprecated, use [tool:pytest] instead.

-- Docs: http://doc.pytest.org/en/latest/warnings.html
==================== 17 passed, 1 warnings in 4.22 seconds =====================
/nix/store/b0aiccyaw74crz9ibj2g22blw4r414pj-python3.6-bootstrapped-pip-9.0.1/lib/python3.6/site-packages/setuptools/dist.py:364: UserWarning: The version specified ('2017-01-19') is an invalid version, this may not work as expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 for more details.
  "details." % self.metadata.version
/nix/store/yy5q05wnlmqxd97csbmjmih32hz3fd4s-bonfire-unstable-2017-01-19

backport in d308c7fc7a7


JCGM 100:2008 (EN): Subfigures notation (continues #112)

Subfigures notation differs in the original and generated document. In cross-references, original uses Figure 1 a), while generated doc uses Figure 1-1). Below the figure itself, original places a) only, while generated doc keeps the same notation as in cross-references.
Original:

Generated:

Again, JCGM needs to inherit ISO behaviour.


Investigate using codecov for c++ tests

It would be good to get coverage reports for the C++ code as well.
See https://github.com/codecov/example-c
See #692

It is also possible to check the cython coverage https://cython.readthedocs.io/en/latest/src/tutorial/profiling_tutorial.html


Update last-created Anki card command no longer works

What is the issue and how what do you do to make it happen
Exact same issue as "Update last-created Anki card command no longer works #536" but mine didn't start working overnight
What browser?
Google Chrome
I've restarted Anki, ASB, the PC, checked for updates on add-ons, made sure Anki's card browser is closed

In case anyone is having the same issue, it turns out all my settings were deleted


Content is blurring because of decimal numbers in css transform

Hey there,
the plugin works fine. Thanks a lot! :) However the placement of the react-user-tour-container insides is calculated in decimal numbers (eg. transform: translate3d(146.5px, 164px, 0px)) so it causes blurring of the actual content inside in Chrome on non Retina displays.
Is there a way to round the calculated placement so it would use CSS translate with whole pixels only?
Thanks,
Florian

@floschie sure, we could probably use Math.floor or Math.ceil , feel free to make a PR, not sure when i'll have time to get it

published v2.5.0

thanks conor!


[fix](s3 client)add default ca cert list for s3 client to avoid problem:'curlCode:77' #32285

cherry pick from #32285

run buildall


Plumb standalone cluster network arguments

This plumbs through the --pod-cidr and --service-cidr CLI arguments to
kind cluster creation. Input validation still needs to be done, but
assuming the correct CIDR format is used, clusters will be set up with
the corresponding pod and service subnets.
This also gets things in place to be able to perform other future kind
configuration customizations by populating the kind cluster struct
rather than parsing a static string.

Pod CIDR setting can be verified with kubectl get nodes -o jsonpath='{.items[*].spec.podCIDR}' and service CIDR can be seen with kubectl get svc -A, and I'm sure 20 other possible ways.


Improve Nix (flakes) setup

Depends on #194

I rebased the PR, the errors are a bit mysterious for me.

This broke the examples: for example when I do nix-shell in examples/Haskell, I get:
error: attribute 'jupyter_contrib_core' missing

       at /home/juan/tweag/jupyterWith/nix/default.nix:35:9:

           34|         python3.ipykernel
           35|         python3.jupyter_contrib_core
             |         ^
           36|         python3.jupyter_nbextensions_configurator

We have a segmentation fault in the CI:
/Users/runner/work/_temp/99d61551-9df3-4fa8-85c1-830f8737f76e.sh: line 5:  1610 Segmentation fault: 11  nix build .#jupyterEnvironment .#build .#core --accept-flake-config --show-trace

I am not sure how to test that locally.

@guaraqe I think we have some funny bug in Nix :) but I managed to trick it to pass.

I need to do the following change to make the Haskell kernel work:
-  flake = import ../../default.nix {};
+  flake = import ../../default.nix;

Is that expected?
The Python example is not working, I would like to refactor it. Is the example of the Haskell shell what we are expecting?

NOTICE: This PR is closed, but will be used as the basis for the next major version of JupyterWith. The new version will be developed around the next branch.
@garbas @k1nkreet


[BUG] DR volume fails to reattach and faulted after node stop and start during incremental restore

Describe the bug
When I was working on the [TEST] [ROBOT] implementation of the manual test case for 'The node the DR volume is attached to is rebooted' (#8425), I discovered the issue. When the node with the attached DR volume is stopped during the incremental restore, we expect the DR volume to reattach to another available node. However, the DR volume goes into a Faulted state. Even after restarting the previously stopped node, the DR volume remains in a Faulted state and does not recover as expected.
To Reproduce
https://longhorn.github.io/longhorn-tests/manual/pre-release/node-not-ready/node-restart/dr-volume-node-rebooted/

Scenario 2

Create a pod with a Longhorn volume.
Write data to the volume and get its MD5 checksum.
Create the first backup for the volume.
Create a DR (Disaster Recovery) volume from this backup.
Wait for the DR volume to complete the initial restore.
Write more data to the original volume and get the new MD5 checksum.
Create a second backup for the volume.
During the incremental restore of the DR volume, immediately stop the node to which the DR volume is attached.
Wait for the instance status change to stopped and then start the node
Wait for the DR volume to detach and then reattach itself to the node.
Wait for the DR volume to complete the restore after reattachment.
Activate the DR volume and check the MD5 checksum of the data.

Expected behavior
The DR volume should reattach to an available node and continue the restore process without entering a faulted state, even after a node reboot.
Support bundle for troubleshooting
supportbundle_295c69fd-6ae1-4b69-a7be-8b0b023fbf84_2024-11-04T04-08-10Z.zip
Environment

Longhorn version: master-head
Impacted volume (PV): vol-1
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): Kubectl
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: v1.31.1+k3s1

Number of control plane nodes in the cluster: 1
Number of worker nodes in the cluster: 3

Node config

OS type and version:  SLES 15-sp5
Kernel version:
CPU per node:
Memory per node:
Disk type (e.g. SSD/NVMe/HDD):
Network bandwidth between the nodes (Gbps):

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): AWS
Number of Longhorn volumes in the cluster: 2

Additional context
https://github.com/longhorn/longhorn/issues/8425
Workaround and Mitigation
N/A

@roger-ryao Can you check v1.6.x and 1.7.x as well? Thanks.

@roger-ryao Can you check v1.6.3 and 1.7.2 as well? Thanks.

Hi @derekbit @c3y1huang
I tried a few more times and found that if the DR volume is attached to the same node as the longhorn-test-minio pod’s node, the issue can be reproduced. This seems to be an environment-related issue, and I still need to think about how to prevent this from happening.
cc @longhorn/qa

@roger-ryao Can you check v1.6.3 and 1.7.2 as well? Thanks.

Hi @derekbit @c3y1huang I tried a few more times and found that if the DR volume is attached to the same node as the longhorn-test-minio pod’s node, the issue can be reproduced. This seems to be an environment-related issue, and I still need to think about how to prevent this from happening.
cc @longhorn/qa

After consulting with @yangchiu & @chriscchien , we should use a customized backup store YAML to deploy the backup store on the control node instead of worker nodes, so it won't be affected by node reboot operations.

After consulting with @yangchiu & @chriscchien , we should use a customized backup store YAML to deploy the backup store on the control node instead of worker nodes, so it won't be affected by node reboot operations.

@roger-ryao  Let's check if the issue remains after re-testing it by an external backup target.

@roger-ryao could you also share the robot case? I cannot find in https://github.com/longhorn/longhorn/issues/8425.

@roger-ryao could you share the robot case? I cannot find it in #8425.

Hi @c3y1huang
I submitted the case at https://github.com/roger-ryao/longhorn-tests/tree/issue9752.
I haven’t submitted a PR yet since I’m still verifying the stability of the case, but it should help you clarify the issue.

@roger-ryao Can you check v1.6.3 and 1.7.2 as well? Thanks.

I was able to reproduce the issue using an external backup target and will test it on v1.7.x and v1.6.x next week.

I was able to reproduce the issue on longhorn-v1.7.3-dev-20241103 using the test case (reproduced once out of four attempts), but I haven’t observed it yet on longhorn-v1.6.4-dev-20241103 (the case is still running; no failures observed in eight attempts, will continue for four more).
For reference, the issue reproduction rate is around 25-50%.

@roger-ryao Can you check v1.6.3 and 1.7.2 as well? Thanks.

I was able to reproduce the issue using an external backup target and will test it on v1.7.x and v1.6.x next week.
I was able to reproduce the issue on longhorn-v1.7.3-dev-20241103 using the test case (reproduced once out of four attempts), but I haven’t observed any failures in 12 attempts on longhorn-v1.6.4-dev-20241103. I’ll continue testing on v1.6.4 and v1.7.2.

I haven’t observed any failures in 15 attempts on v1.6.3, while on v1.7.2, I observed only one failure in 15 attempts.

Discussed with @c3y1huang  and assisted in replicating the issue.
Here is a brief summary of the current test results:
We observed the issue on versions v1.7.0, v1.7.2, v1.7.3-dev-20241103, and v1.8.0-dev-20241103 (We did not test v1.7.1, but we infer that it likely has the same issue.). However, when running the same case on v1.6.3, we did not observe any failures.
The support bundle for v1.7.0 ( volume e2e-test-volume-1 ). :
170-supportbundle_c022ef54-5c0f-47df-acd3-2dffce86cadb_2024-11-12T05-28-01Z.zip

Check with conditions (WIP):

[ ] NFS as backup storage, cc @roger-ryao
[ ] Scale-up CoreDNS

Check with conditions (WIP):

[ ]  Using NFS as backup storage to check if this issue is specific to S3, cc @roger-ryao

So far, after a total of 9 attempts, no failures have been observed.
I was not successful in changing the NFS backup server on the control node through the file at https://raw.githubusercontent.com/longhorn/longhorn/master/deploy/backupstores/nfs-backupstore.yaml.
I used my external NFS server as the backup target, but the server uses the IP directory nfs://<nfs_server_ip>:/opt/nfs.
This might be why I couldn't replicate the issue with NFS.
Let me try to see how I can configure my NFS server to connect using a domain name.
Perhaps this way, I can replicate the issue when the backup target is NFS.

After checking with @roger-ryao , we found that this issue is not reproducible when using NFS as backup storage.
The NFS list operation doesn't depend on CoreDNS because it verifies the local path directly.
https://github.com/longhorn/backupstore/blob/master/fsops/fsops.go#L113-L126
The S3 list operation checks the backup store object, which relies on the DNS resolution
https://github.com/longhorn/backupstore/blob/master/s3/s3.go#L114
This means this issue is specific to the cloud provider storage.

Check with conditions (WIP):

[ ]  Using NFS as backup storage to check if this issue is specific to S3, cc @roger-ryao
[ ]  Scale-up CoreDNS to check if this is a DNS resolution issue, @c3y1huang

After running it 20 times, I did not observe the volume becoming faulted when the backup target was the NFS server

I am able to reproduce this issue with v1.6.2 by scaling down CoreDNS during the node reboot, while the other 2 replicas are rebuilding.

Verified on v1.8.0-dev-20241201 20241205

longhorn v1.8.0-dev-20241201 https://github.com/longhorn/longhorn/commit/9e8a84bdc8b3cfc2e0cf53415ee2bc3f2d8753e2

Result Passed

[x] require/doc : Checked documentation in https://github.com/longhorn/website/pull/1011
[x] DR Volume Node Reboot During Initial Restoration & DR Volume Node Reboot During Incremental Restoration tested and passed.

issue9757_passed_report.tar.gz


Failed to pull image from nexus private registry

Failed to pull image ": rpc error: code = Unknown desc = unauthorized: authentication required
docker 17.03.2  nexus 3
rancher 2.1.3.
already add private registry in rancher. rancher pull failed. but docker pull directly on node is OK.

rancher 2.1.3.

@leochan007 Can you check if imagePullSecrets is in the yaml of your deployment, please?

@loganhz yes. i works. a workaround method : add this opt mannually. thx.


Modals 1-3

I added text and titles for #1-3... added video to #2 and will add images for #1 and #2 later.

Looks good


fix(android): rn-pager-view breaks view order causing gesture failures

Details

This PR fixes an issue that has been introduced in react-native-pager-view. The issue is that on android the JS based gesture system is broken on pages. This happens due to a view order issue on android, which can be fixed by making the child pages also positioned absolute.
The issue in the library has been reported here:

https://github.com/callstack/react-native-pager-view/issues/836

the patch can be removed once the library is updated and upgraded in expensify.
Fixed Issues

$ https://github.com/Expensify/App/issues/47911
PROPOSAL: https://github.com/Expensify/App/issues/47911#issuecomment-2307746398
Tests

[ ] Check that on android in Submit Expense > Scan all buttons at the bottom are perusable

Offline tests

same as tests
QA Steps

same as tests
PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/user-attachments/assets/a0344341-81ac-4d61-b948-1ebf85d57f47

Android: mWeb Chrome

As the issue is native android only, and the code fix only applies to the native android platform I deemed it to be unnecessary to explicitly record the other platforms than android.

iOS: Native

As the issue is native android only, and the code fix only applies to the native android platform I deemed it to be unnecessary to explicitly record the other platforms than android.

iOS: mWeb Safari

As the issue is native android only, and the code fix only applies to the native android platform I deemed it to be unnecessary to explicitly record the other platforms than android.

MacOS: Chrome / Safari

As the issue is native android only, and the code fix only applies to the native android platform I deemed it to be unnecessary to explicitly record the other platforms than android.

MacOS: Desktop

As the issue is native android only, and the code fix only applies to the native android platform I deemed it to be unnecessary to explicitly record the other platforms than android.

Closing as library upgrade was reverted


qtpass can't use qrencode

Describe the bug
Clicking the QR code icon on a password entry does nothing.
To Reproduce
Steps to reproduce the behavior:

Enable the Use qrencode option in preferences
Click the QR code icon on a password entry

Expected behavior
A QR code is displayed.
Screenshots

The QR code icon is the righthand one. Clicking it doesn't display anything.
Additional context
qtpass hardcodes the location of the qrencode executable.
Metadata

system: "x86_64-linux"
host os: Linux 4.19.84, NixOS, 19.09.1326.382f0951a9f (Loris)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3
channels(root): "nixos-19.09.1326.382f0951a9f"
channels(user): "nixpkgs-20.03pre199833.6b463388478"
nixpkgs: $HOME/.nix-defexpr/channels/nixpkgs

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

Fixed in:
442670f787ca8adceda7f8b0d6692024b4de2f70 -> unstable
65ebe52c81b611173e4928f87abe928f10555434 -> r19.09


macOS ColorSync profiles cause blocky backgrounds

VSCode Version: Code 1.11.2 (6eaebe3b9c70406d67c97779468c324a7a95db0e, 2017-04-13T07:56:42.517Z)
OS Version: Darwin x64 16.5.0
Extensions: the listing exceeds the lower minimum of browsers' URL characters limit

Steps to Reproduce:

open VSCode on macOS
open the Displays panel of System Preferences
try various display profiles with some code open, using a dark color theme. "Apple RGB" should cause the issue, for example

this is #12473


Unintended input when text editor gains focus

Is your issue REALLY a bug?

[X] My issue is indeed a bug!
[X] I am not crazy! I will not fill out this form just to ask a question or request a feature. Pinky promise.

Is there an existing issue for this?

[X] I have searched the existing issues.

Is this issue related to iced?

[X] My hardware is compatible and my graphics drivers are up-to-date.

What happened?
This is a bit of niche one. I use the Awesome tiling window manager on Linux. I have Super+j and Super+k bound to cycle back/forward through windows. When the focus reaches an Iced application with a text input a j or k is typed in the message box. This doesn't happen with any other applications on my system. I first observed the behaviour in the Halloy IRC client but it happens with the editor example too.
Steps to Reproduce

Run Awesome WM
Cycle through applications with Super+j until the Iced editor example is reached
Observe a j or k is typed.

Video of behaviour:
https://github.com/user-attachments/assets/a6e6b32e-0a2d-4ccb-a6cc-08afe7930d52
Environment
OS: Arch Linux, kernel 6.9.7
WM: Awesome
Display Server: X11
GPU: AMD Radeon RX 6700 XT
What is the expected behavior?
Expected behaviour is that when an iced application is focused via a keyboard shortcut no text is typed.
Version
master
Operating System
Linux
Do you have any log output?
No response

This is the case in several environments, including WindowMaker WM on FreeBSD: https://github.com/squidowl/halloy/issues/284


Use Resource files instead of too big byte arrays

Some tools are not good at treating such too long arrays.
e.g., Visual Studio takes long time to parse the code.

https://starbeamrainbowlabs.com/blog/article.php?article=posts/180-Embedding-Resources.html
Unfortunately, as gowasm2csharp doesn't generate csproj, we cannot adopt this way :-/
Let's split long arrays instead.


[Hue] Set scene directly with top level command

Extension
https://www.raycast.com/pindab0ter/hue
Description
Today, in order to set a scene, you have to run the 'Control Groups' command, then tap on a control group, and then tap on a scene. It would be great if you could program a scene to trigger directly with a keyboard shortcut or a alias - for example, set the bedroom to nightlight with ctr + cmd + l.
For example, by implementing an 'Add to favorites' action, users will then be able to trigger the scene with their keyboard using an easy to use shortcut.

Who will benefit from this feature?
Philips Hue and Raycast users who have a small number of scenes that are frequently used.
Anything else?
No response

This is a good idea and should be possible using the Action.CreateQuickLink component in combination with the deeplink scheme.on with the deeplink scheme. Would be something like raycast://extensions/pindab0ter/hue/setScene?launchContext=%7B%22sceneId%22%3A%22abc-234%22%7D
The recent Spotify Beta Extension has a good example:
https://github.com/raycast/extensions/blob/c7e094ac950b7294675419734f401a404d9e9e31/extensions/spotify-beta/src/quickActions.tsx#L56-L65
As a bonus this would allow controlling lights from other non-raycast apps by using those deeplinks.
Happy to play with this over the course of this weekend @pindab0ter

Love the idea! Great suggestion!
@robertvanhoesel would that allow for setting a keyboard shortcut?
You can work off of my draft PR #6006 if you feel like giving it a go!

@pindab0ter yes, the create quicklink action prefils the form for the Create Quick Link command that has been there for a while. You can then assign shortcuts, aliases, custom names etc.

I see, awesome! I look forward to what you come up with! Feel free to message me on Slack, too.


[BUG] lxml fails to build in Python-3.11.0a5

Describe the bug
I'm testing reportlab with latest python alpha 5; I use lxml. This built fine in 3.11.0a3, but fails in 3.11.0a5.
To Reproduce
Code to reproduce the behaviour:
. bin/activate
pip install cython #this works fine
pip install lxml fails
Expected behavior
I expected it to build as in the previous alpha 3; there was an alpha 4, but it was withdrawn so far as I can tell. If I build a wheel with 3.11.0a3 it will install in 3.11.0a5, but I think that is unsafe.
Environment :

OS:arch linux amd64
Python version 3.11.0a5
Cython version 0.29.27

lxml-311a5-install-failure.log
lxml-311a3-install-success.log

The error shown in the logs is a duplicate of https://github.com/cython/cython/issues/4581


Mistral Home Directory

Mistral's home directory is set to /home/mistral [1], as per the RDO package I suspect, but that directory does not exist. It should be set to an existing directory and doing so fixes a problem with Mistral ansible actions.
[1]
(undercloud) [stack@undercloud ceph-ansible]$ grep mistral /etc/passwd
mistral:x:980:977:Mistral Daemons:/home/mistral:/sbin/nologin
(undercloud) [stack@undercloud ceph-ansible]$

While running this playbook
https://github.com/ceph/ceph-ansible/blob/master/site.yml.sample#L21-L23
I get:
PLAY [mons,agents,osds,mdss,rgws,nfss,restapis,rbdmirrors,clients,iscsigws,mgrs] ***\
\
TASK [check for python2] *******************************************************\
fatal: [<IP_ADDRESS>]: FAILED! => {"failed": true, "msg": "Unable to create local directories(/home/mistral/.ansible/cp): [Errno 13] Permission denied: \\'/home/mistral\\'"}\
...ignoring\
fatal: []: FAILED! => {"failed": true, "msg": "Unable to create local directories(/home/mistral/.ansible/cp): [Errno 13] Permission denied: \\'/home/mistral\\'"}\
...ignoring\
fatal: [<IP_ADDRESS>]: FAILED! => {"failed": true, "msg": "Unable to create local directories(/home/mistral/.ansible/cp): [Errno 13] Permission denied: \\'/home/mistral\\'"}\
...ignoring\
\
TASK [install python2 for Debian based systems] **********

My playbook is being run the by mistral-user who shouldn't have a /home/mistral directory.
I orginally was getting this error:
Stderr: u'Traceback (most recent call last):
File "/usr/bin/ansible-playbook", line 43, in
import ansible.constants as C
File "/usr/lib/python2.7/site-packages/ansible/constants.py", line 161, in
DEFAULT_LOCAL_TMP         = get_config(p, DEFAULTS, \'local_tmp\',        \'ANSIBLE_LOCAL_TEMP\',      \'~/.ansible/tmp\', istmppath=True)
File "/usr/lib/python2.7/site-packages/ansible/constants.py", line 81, in get_config
makedirs_safe(value, 0o700)
File "/usr/lib/python2.7/site-packages/ansible/utils/path.py", line 70, in makedirs_safe
raise AnsibleError("Unable to create local directories(%s): %s" % (to_native(rpath), to_native(e)))
ansible.errors.AnsibleError: Unable to create local directories(/home/mistral/.ansible/tmp): [Errno 13] Permission denied: \'/home/mistral\'\
But I worked around it by adding "local_tmp=/tmp/.ansible/tmp" to /etc/ansible/ansible.cfg
and verified that /tmp/.ansible/tmp was creatd on my system after doing so.
However, there are parts of Ansible that whatever $HOME expands to. If I simply create a home directory that mistral can write to then suddenly I don't have this issue and my Mistral worfklow succeeds.
https://review.openstack.org/#/c/469644/8
E.g. It worked with the following:
(undercloud) [stack@undercloud tripleo-ceph-ansible]$ grep mistral /etc/passwd
mistral:x:980:977:Mistral Daemons:/tmp/mistral:/sbin/nologin
(undercloud) [stack@undercloud tripleo-ceph-ansible]$

Here's another idea
(undercloud) [stack@undercloud tripleo-ceph-ansible]$ echo $HOME; HOME=/tmp/foo; ansible all -i <IP_ADDRESS>, -u heat-admin -m ping ; HOME=/home/stack
/home/stack
<IP_ADDRESS> | SUCCESS => {
    "changed": false,
    "ping": "pong"
}
(undercloud) [stack@undercloud tripleo-ceph-ansible]$ ls -la /tmp/foo/
total 256
drwxrwxr-x.    3 stack stack     22 Jun  9 15:21 .
drwxrwxrwt. 5585 root  root  184320 Jun  9 15:21 ..
drwx------.    4 stack stack     27 Jun  9 15:21 .ansible
(undercloud) [stack@undercloud tripleo-ceph-ansible]$

Talked to d0ugal and rbrady suggestion:
Have the RDO package modified by submitting a change to the specfile in the distgit.
The following should be chantged:
https://github.com/rdo-packages/mistral-distgit/blob/rpm-master/openstack-mistral.spec#L281-L289
To make it more like:
https://github.com/rdo-packages/heat-distgit/blob/rpm-master/openstack-heat.spec#L324
Next step: connect this issue to and actual RDO request

flapper87 thinks this may be solved by a patch to the code introduced by  https://review.openstack.org/#/c/470021/ after it merges.
The patch would set $HOME temporarily for the execution of the playbook. The Ansible Environment might help: https://docs.ansible.com/ansible/playbooks_environment.html

I am going to wait for flaper87's change . Until then I have the following which doesn't seem to require any environmental changes:
https://github.com/fultonj/mistral-ansible-actions/blob/master/mistral_ansible_actions.py#L294
Aside from these:
https://github.com/fultonj/tripleo-ceph-ansible/blob/master/init.sh#L100-L104

Waiting on:
https://review.openstack.org/#/c/473585/
https://review.openstack.org/#/c/473587/
https://review.openstack.org/#/c/473586/

https://review.openstack.org/#/c/473585 merged.
waiting on:
https://review.openstack.org/#/c/473587/
https://review.openstack.org/#/c/473586/

Tested the following and they work. Waiting for them to merge:
https://review.openstack.org/#/c/473587/
https://review.openstack.org/#/c/473586/
https://review.openstack.org/#/c/474976/

These have merged


Ensure that the tests are run at least weekly

We make changes to this repo infrequently. So there can be long gaps between test runs. Add weekly tests on a Sunday to ensure that we notice in a timely manner if the tests break.

The fix for the failing tests is in https://github.com/alphagov/digitalmarketplace-utils/pull/609
This is a good idea and probably one we should add to other repos if it works. How will we know if a scheduled test fails?

That's the main problem - it only notifies the person who last modified .github/workflows/test.yml, which is not necessarily helpful.
Maybe we should add a step to notify Slack on failure?
In any case, this was just an experiment. It needs a fair bit more work, so I'll create a story on the tech board rather than continuing with it now.

@bjgill Sorry if I am missing something here, given these are unit tests, why is running them only after code changes not sufficient?

The problem this tries to solve is that we have an unpinned dependency - digitalmarketplace-developer-tools. This means that the tests can break without any code changes to this repo.

The problem this tries to solve is that we have an unpinned dependency - digitalmarketplace-developer-tools. This means that the tests could break and we wouldn't notice until we came to make an (unrelated) PR.

@bjgill Makes sense, do you want me to research how we can propagate failures to Slack?

Am not planning at continuing with this any time soon


Error in email mark down.

Laravel Version: 5.6.34
PHP Version: 7.2.9

Description:
Error when have another @compenent in @component('mall::message')
@component('mail::message')
    # Order Shipped

    Your order has been shipped!

    @component('mail::button', ['url' => '#'])
        View Order
    @endcomponent

    Thanks,<br>
    {{ config('app.name') }}
@endcomponent

Out put.

OK, I didn't read markdown note.


Fix yolo layer plugin loading

For more information on why this change is necessary see https://github.com/wang-xinyu/tensorrtx/issues/107
Please double check the change in the Makefile. I use CMake in my project and the necessary change is:
target_link_libraries(layerplugin nvinfer cudart)
So I hope the appended diff is the equivalent Makefile change.
After this change you can run the tensorrt engine with trtexec using the following command (change paths ofc):
./trtexec --loadEngine=/yolov4-triton-tensorrt/build/yolov4.engine --plugins=/yolov4-triton-tensorrt/build/liblayerplugin.so

This commit is not needed: Link plugin against nvinfer and cudart.  "libnvinfer.so" and "libcudart.so" will be included in the linking phase of "libyolo_layer.so".

Otherwise, thanks a lot for submitting this PR.


URL Encode commandline arguments for called script?

When using the --dir=DIR option, this enables me to call any script in that DIR.
Is there also a way to pass arguments to that script?
I tried with http://localhost:8080/script.sh%20argument but that resulted in "script not found"
I also tried with http://localhost:8080/script.sh?argument and http://localhost:8080/script.sh?arg=argument but $1 in the bash script I called remained empty.

Arguments are seen by script as environment variable QUERY_STRING per RFC3875.
This is part of CGI standard and while it's good to pass them this would limit ability to run scripts as  websocketd script arg arg.

Thanks! That answers my question!


build content docs

Status
Ready
Related Issues
fixes: link to the issue
Description
gitlab CI build for docs

force merge - change to file execute permission.


Tap on the top of the rear page for getting back leads app to a weird state.

If you swipe the front page down, everything works well,
but If you press the top of the rear page for back,
it's going to a weird state, and it lost its functionality.
(I've checked it in your /example app).

Thank you for reporting this issue. I will release a fix as soon as possible and let you know too.

Thanks!

Hey man,
any fix estimation on this issue?

Yes, Monday👍🏻

Thanks for your quick respone

Hi again. I am now testing the example application and I can't find any errors besides the wrong layout of the UI due to the misplacement of the widgets. Especially in reference to the issue you've reported, I am a bit confused because "pressing the top of the rear page for back" is not a functionality embedded in this library. You can go back either by pressing the back arrows or by sliding down a page.

Hmm, then how can I disable tapping there?

What I meant is by default, tapping there should not do anything. I just published a small update with an Example application that is easier to see and test. Can you try that as well?

Where did you publish the update?
Sure, I will check it.

It didn't fix,
I checked 1.0.5

I am kind of confused about this issue because when I press on the top of the rear page, nothing happens as it is not coded to do something. Can I trouble you for a screen recording?

Sliding a stack down is working perfectly, however, pressing on the behind stack is not normal behavior and should not be permitted.
Look at this video please,
the last touch has happened here which causes the bug:

It is happening in the latest version (1.0.5), on the /example project.
Let me know if it is confusing anymore.
Thanks!

Hello! Many apologies for the delay, I finally had some time to return my personal works. After upgrading my Flutter to the latest version, I saw the problem you were having and released a quick fix both on pub.dev and here. Take a look and I hope now it is alright🙂


[Bug]: Tunnel option gloms onto port causing issues

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
App
Expected behavior
I have a foreman script that opens a tunnel, assigned to my App, directing traffic to localhost on a port. The process also starts a basic web server on that port listening to localhost. When I run shopify app dev script on MacOS, assigning the tunnel-url parameter, it works fine. However, if I run this exact scripting on Linux, it fails.
I am testing by using Linux as my OS and have Puma setup such that my Rails App works when I start with foreman start -f Procfile.dev which opens the webserver, compiles assets and opens an NGrok tunnel. My MacOS machine runs the same setup. BUT, on MacOS I can use the yarn dev command too!
 "dev": "shopify app dev --tunnel-url=https://myapp.ngrok.io:3206",

So on my MacOS machine, both using foreman or yarn dev works!, and like magic, because my Linux machine is on the same wifi network, if I access the App on my laptop it too all works when MacOS started with yarn dev. So I am so close to glory.
However, if I start the tunnel on the Linux machine with yarn dev, my web server is blocked from running! I get this message from Puma!
/home/leo/.rbenv/versions/3
.2.2/lib/ruby/gems/3.2.0/gems/puma-6.3.0/lib/puma/binder.rb:334:in `initialize':
Address already in use - bind(2) for "<IP_ADDRESS>" port 3206 (Errno::EADDRINUSE)
I am not sure why the Linux setup has a problem that MacOS does not exhibit. This is my last blocker to getting Puma Dev style tunneled development (with ngrok) working. Can anyone help me to try and debug this issue with Linux and Puma?
The ONLY thing blocking Linux from working is the tunnel-url in the DEV scripting. Someone, on Linux, it is glomming onto the localhost at the port which then blocks the webserver from using localhost and the same port. WHY????
Actual behavior
Address already in use - bind(2) for "<IP_ADDRESS>" port 3206 (Errno::EADDRINUSE)
Verbose output
$ yarn dev
....
/home/leo/.rbenv/versions/3
.2.2/lib/ruby/gems/3.2.0/gems/puma-6.3.0/lib/puma/binder.rb:334:in `initialize':
Address already in use - bind(2) for "<IP_ADDRESS>" port 3206 (Errno::EADDRINUSE)

Reproduction steps

start app in MacOS with yarn dev, it all works
start same app in Linux with yarn dev, it fails to start the web service

Operating System
MacOS, Linux
Shopify CLI version (check your project's package.json if you're not sure)
3.52
Shell
ZSH
Node version (run node -v if you're not sure)
21.5
What language and version are you using in your application?
Ruy 3.2.2

Hi @resistorsoftware!
So the way the CLI works is that it either creates a tunnel to an internal port or expects to receive those values as flags.
Then it crates a proxy server listening to that port, the proxy redirects the traffic to your app and/or extensions.
So if you pass  --tunnel-url=https://myapp.ngrok.io:3206, the CLI will try to create a server that listens at port 3206. Because that's where external calls are going to be redirected to, so If there is something else there it won't work.
Per your comment:

I have a foreman script that opens a tunnel, assigned to my App, directing traffic to localhost on a port. The process also starts a basic web server on that port listening to localhost

If you are already starting a process in that port, then the CLI can't use it. So I'd say that linux behavior is correct and Mac shouldn't work?
Does this makes sense?
Can you try your linux flow without starting that extra process in that port?
I'm assuming that you are creating your ngrok tunnel to redirect to port 3206 right?

ngrok tunnel was tricky as they recently changed all their options but yes, I nailed that. For anyone that wants to know it, a Procfile.dev could be:
web: bin/rails s
js: yarn build --watch
tunnel: ngrok http --domain=myapp.ngrok.io 3206

The BIG killer that does not affect MacOS but affected Linux was me inadvertently, naively having a PORT=3206 in the shopify.web.toml file. Removed that and bingo, it worked. Why  felt the need to place a PORT in that file is probably due to not understanding the docs on this parameter and it's real use.

@isaacroldan I have many many Apps and I have not checked them all, but it is entirely possible that this is indeed the case, the only one that had a PORT set in the dot toml file. I suppose better documentation and an example of when, how and why one would use the PORT value could go a long way to ensuring no one else experiences this pain I did with the tunnels.


Remove setting http.route attribute in frontend

Changes
As per the OpenTelemetry HTTP Server semantic conventions, the http.route attribute is meant to be a low cardinality route template. The URI cannot substitute it.
This patch remove the setting of the http.route semantic attribute by the Instrumentation Middleware in the frontend service.
Trying to get a paramaterized template route in NextJS is incredibly difficult (take a look at https://github.com/getsentry/sentry-javascript/issues/5505 to see what it takes), so I did not replace it with anything. This seems to be fine since as per the semantic convention is the http.route attribute is "Conditionally Required: If and only if it's available"
Two notes:

Should we change SemanticAttributes.HTTP_TARGET to be the url? This seems to match the semantic conventions better.
Do we need a changelog entry for this?

Do I need to do anything else to get this merged in? Or is there some release cadence we need to follow here?

Do I need to do anything else to get this merged in? Or is there some release cadence we need to follow here?

Just update the branch and for future prs please use a personal fork. We can’t trigger branch updates on an organizational fork.
Should be good to go after that


Data structures.

Add functionality for arrays. Probably emulate assembly '.data' and '.txt' segments. More info/design needed.

Will be adding list functionality, and leaving it at that. This keeps things easier to understand from a programmer perspective, as well as a little easier to design the compiler. Alternative solutions are welcome, but lists are probably going to be where we keep it for a bit.


review jobs

some things to consider:

should what is now called jobs be called "job-templates" or something like that?
how do you deal with supplying commands/args/environments

should the template be defaults and fully overwritten?

e.g. if i say --env foo=bar does that mean ignore all default env vars or add foo=bar?

how to reference secrets

closing in favor of https://github.com/mlab-lattice/lattice/issues/208