Fastlane is not working in M1

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
fastlane test is giving some ruby related issues.
Command executed

Tried installing via brew install fastlane , arch -x86_64 brew install fastlane, sudo gem install fastlane and sudo arch -x86_64 gem install fastlane
Complete output when running fastlane, including the stack trace and command used

fastlane test

 [✔] 🚀
[10:34:09]: ------------------------------
[10:34:09]: --- Step: default_platform ---
[10:34:09]: ------------------------------
[10:34:09]: Driving the lane 'android test' 🚀
[10:34:09]: ------------------
[10:34:09]: --- Step: test ---
[10:34:09]: ------------------
[10:34:09]: $ /Users/satan/Library/github/ToDo-App/android/gradlew test -p .
[10:34:14]: ▸ > Task :app:compileFlutterBuildDebug
[10:34:14]: ▸ > Task :app:packLibsflutterBuildDebug UP-TO-DATE
[10:34:14]: ▸ > Task :app:preBuild UP-TO-DATE
[10:34:14]: ▸ > Task :app:preDebugBuild UP-TO-DATE
[10:34:14]: ▸ > Task :flutter_secure_storage:preBuild UP-TO-DATE
[10:34:14]: ▸ > Task :flutter_secure_storage:preDebugBuild UP-TO-DATE
[10:34:14]: ▸ > Task :flutter_secure_storage:compileDebugAidl NO-SOURCE
[10:34:14]: ▸ > Task :fluttertoast:preBuild UP-TO-DATE
[10:34:14]: ▸ > Task :fluttertoast:preDebugBuild UP-TO-DATE
[10:34:14]: ▸ > Task :fluttertoast:compileDebugAidl NO-SOURCE
[10:34:14]: ▸ > Task :share_plus:preBuild UP-TO-DATE
[10:34:14]: ▸ > Task :share_plus:preDebugBuild UP-TO-DATE
[10:34:14]: ▸ > Task :share_plus:compileDebugAidl NO-SOURCE
[10:34:14]: ▸ > Task :shared_preferences_android:preBuild UP-TO-DATE
[10:34:14]: ▸ > Task :shared_preferences_android:preDebugBuild UP-TO-DATE
[10:34:14]: ▸ > Task :shared_preferences_android:compileDebugAidl NO-SOURCE
[10:34:14]: ▸ > Task :url_launcher_android:preBuild UP-TO-DATE
[10:34:14]: ▸ > Task :url_launcher_android:preDebugBuild UP-TO-DATE
[10:34:14]: ▸ > Task :url_launcher_android:compileDebugAidl NO-SOURCE
[10:34:14]: ▸ > Task :app:compileDebugAidl NO-SOURCE
[10:34:14]: ▸ > Task :flutter_secure_storage:packageDebugRenderscript NO-SOURCE
[10:34:14]: ▸ > Task :fluttertoast:packageDebugRenderscript NO-SOURCE
[10:34:14]: ▸ > Task :share_plus:packageDebugRenderscript NO-SOURCE
[10:34:14]: ▸ > Task :shared_preferences_android:packageDebugRenderscript NO-SOURCE
[10:34:14]: ▸ > Task :url_launcher_android:packageDebugRenderscript NO-SOURCE
[10:34:14]: ▸ > Task :app:compileDebugRenderscript NO-SOURCE
[10:34:14]: ▸ > Task :app:generateDebugBuildConfig UP-TO-DATE
[10:34:14]: ▸ > Task :flutter_secure_storage:writeDebugAarMetadata UP-TO-DATE
[10:34:14]: ▸ > Task :fluttertoast:writeDebugAarMetadata UP-TO-DATE
[10:34:14]: ▸ > Task :share_plus:writeDebugAarMetadata UP-TO-DATE
[10:34:14]: ▸ > Task :shared_preferences_android:writeDebugAarMetadata UP-TO-DATE
[10:34:14]: ▸ > Task :url_launcher_android:writeDebugAarMetadata UP-TO-DATE
[10:34:14]: ▸ > Task :app:checkDebugAarMetadata UP-TO-DATE
[10:34:14]: ▸ > Task :app:cleanMergeDebugAssets FAILED
[10:34:14]: ▸ FAILURE: Build failed with an exception.
[10:34:14]: ▸ * What went wrong:
[10:34:14]: ▸ Execution failed for task ':app:cleanMergeDebugAssets'.
[10:34:14]: ▸ > java.io.IOException: Unable to delete directory '/Users/satan/Library/github/ToDo-App/build/app/intermediates/incremental/mergeDebugAssets'
[10:34:14]: ▸ Failed to delete some children. This might happen because a process has files open or has its working directory set in the target directory.
[10:34:14]: ▸ - /Users/satan/Library/github/ToDo-App/build/app/intermediates/incremental/mergeDebugAssets/merger.xml
[10:34:14]: ▸ * Try:
[10:34:14]: ▸ > Run with --stacktrace option to get the stack trace.
[10:34:14]: ▸ > Run with --info or --debug option to get more log output.
[10:34:14]: ▸ > Run with --scan to get full insights.
[10:34:14]: ▸ * Get more help at https://help.gradle.org
[10:34:14]: ▸ Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
[10:34:14]: ▸ You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
[10:34:14]: ▸ See https://docs.gradle.org/7.4.2/userguide/command_line_interface.html#sec:command_line_warnings
[10:34:14]: ▸ BUILD FAILED in 5s
[10:34:14]: ▸ 10 actionable tasks: 2 executed, 8 up-to-date
+------------------+--------------+
|          Lane Context           |
+------------------+--------------+
| DEFAULT_PLATFORM | android      |
| PLATFORM_NAME    | android      |
| LANE_NAME        | android test |
+------------------+--------------+
[10:34:15]: Exit status of command '/Users/satan/Library/github/ToDo-App/android/gradlew test -p .' was 1 instead of 0.
> Task :app:compileFlutterBuildDebug
> Task :app:packLibsflutterBuildDebug UP-TO-DATE
> Task :app:preBuild UP-TO-DATE
> Task :app:preDebugBuild UP-TO-DATE
> Task :flutter_secure_storage:preBuild UP-TO-DATE
> Task :flutter_secure_storage:preDebugBuild UP-TO-DATE
> Task :flutter_secure_storage:compileDebugAidl NO-SOURCE
> Task :fluttertoast:preBuild UP-TO-DATE
> Task :fluttertoast:preDebugBuild UP-TO-DATE
> Task :fluttertoast:compileDebugAidl NO-SOURCE
> Task :share_plus:preBuild UP-TO-DATE
> Task :share_plus:preDebugBuild UP-TO-DATE
> Task :share_plus:compileDebugAidl NO-SOURCE
> Task :shared_preferences_android:preBuild UP-TO-DATE
> Task :shared_preferences_android:preDebugBuild UP-TO-DATE
> Task :shared_preferences_android:compileDebugAidl NO-SOURCE
> Task :url_launcher_android:preBuild UP-TO-DATE
> Task :url_launcher_android:preDebugBuild UP-TO-DATE
> Task :url_launcher_android:compileDebugAidl NO-SOURCE
> Task :app:compileDebugAidl NO-SOURCE
> Task :flutter_secure_storage:packageDebugRenderscript NO-SOURCE
> Task :fluttertoast:packageDebugRenderscript NO-SOURCE
> Task :share_plus:packageDebugRenderscript NO-SOURCE
> Task :shared_preferences_android:packageDebugRenderscript NO-SOURCE
> Task :url_launcher_android:packageDebugRenderscript NO-SOURCE
> Task :app:compileDebugRenderscript NO-SOURCE
> Task :app:generateDebugBuildConfig UP-TO-DATE
> Task :flutter_secure_storage:writeDebugAarMetadata UP-TO-DATE
> Task :fluttertoast:writeDebugAarMetadata UP-TO-DATE
> Task :share_plus:writeDebugAarMetadata UP-TO-DATE
> Task :shared_preferences_android:writeDebugAarMetadata UP-TO-DATE
> Task :url_launcher_android:writeDebugAarMetadata UP-TO-DATE
> Task :app:checkDebugAarMetadata UP-TO-DATE
> Task :app:cleanMergeDebugAssets FAILED
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:cleanMergeDebugAssets'.

java.io.IOException: Unable to delete directory '/Users/satan/Library/github/ToDo-App/build/app/intermediates/incremental/mergeDebugAssets'
Failed to delete some children. This might happen because a process has files open or has its working directory set in the target directory.
- /Users/satan/Library/github/ToDo-App/build/app/intermediates/incremental/mergeDebugAssets/merger.xml

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

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

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.4.2/userguide/command_line_interface.html#sec:command_line_warnings
BUILD FAILED in 5s
10 actionable tasks: 2 executed, 8 up-to-date
[10:34:15]: Permission denied @ rb_sysopen - ./fastlane/README.md
[10:34:15]: Couldn't save fastlane documentation at path '/Users/satan/Library/github/ToDo-App/android/fastlane/README.md', make sure you have write access to the containing directory.
[10:34:15]: Permission denied @ rb_sysopen - ./fastlane/report.xml
[10:34:15]: Couldn't save report.xml at path '/Users/satan/Library/github/ToDo-App/android/fastlane/report.xml', make sure you have write access to the containing directory.
+------+------------------+-------------+
|           fastlane summary            |
+------+------------------+-------------+
| Step | Action           | Time (in s) |
+------+------------------+-------------+
| 1    | default_platform | 0           |
| 💥   | test             | 5           |
+------+------------------+-------------+
[10:34:15]: fastlane finished with errors
Looking for related GitHub issues on fastlane/fastlane...
bundler: failed to load command: fastlane (/usr/local/bin/fastlane)
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/fastlane_core/lib/fastlane_core/ui/interface.rb:153:in `shell_error!': [!] Exit status of command '/Users/satan/Library/github/ToDo-App/android/gradlew test -p .' was 1 instead of 0. (FastlaneCore::Interface::FastlaneShellError)

Task :app:compileFlutterBuildDebug
Task :app:packLibsflutterBuildDebug UP-TO-DATE
Task :app:preBuild UP-TO-DATE
Task :app:preDebugBuild UP-TO-DATE
Task :flutter_secure_storage:preBuild UP-TO-DATE
Task :flutter_secure_storage:preDebugBuild UP-TO-DATE
Task :flutter_secure_storage:compileDebugAidl NO-SOURCE
Task :fluttertoast:preBuild UP-TO-DATE
Task :fluttertoast:preDebugBuild UP-TO-DATE
Task :fluttertoast:compileDebugAidl NO-SOURCE
Task :share_plus:preBuild UP-TO-DATE
Task :share_plus:preDebugBuild UP-TO-DATE
Task :share_plus:compileDebugAidl NO-SOURCE
Task :shared_preferences_android:preBuild UP-TO-DATE
Task :shared_preferences_android:preDebugBuild UP-TO-DATE
Task :shared_preferences_android:compileDebugAidl NO-SOURCE
Task :url_launcher_android:preBuild UP-TO-DATE
Task :url_launcher_android:preDebugBuild UP-TO-DATE
Task :url_launcher_android:compileDebugAidl NO-SOURCE
Task :app:compileDebugAidl NO-SOURCE
Task :flutter_secure_storage:packageDebugRenderscript NO-SOURCE
Task :fluttertoast:packageDebugRenderscript NO-SOURCE
Task :share_plus:packageDebugRenderscript NO-SOURCE
Task :shared_preferences_android:packageDebugRenderscript NO-SOURCE
Task :url_launcher_android:packageDebugRenderscript NO-SOURCE
Task :app:compileDebugRenderscript NO-SOURCE
Task :app:generateDebugBuildConfig UP-TO-DATE
Task :flutter_secure_storage:writeDebugAarMetadata UP-TO-DATE
Task :fluttertoast:writeDebugAarMetadata UP-TO-DATE
Task :share_plus:writeDebugAarMetadata UP-TO-DATE
Task :shared_preferences_android:writeDebugAarMetadata UP-TO-DATE
Task :url_launcher_android:writeDebugAarMetadata UP-TO-DATE
Task :app:checkDebugAarMetadata UP-TO-DATE
Task :app:cleanMergeDebugAssets FAILED

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:cleanMergeDebugAssets'.

java.io.IOException: Unable to delete directory '/Users/satan/Library/github/ToDo-App/build/app/intermediates/incremental/mergeDebugAssets'
Failed to delete some children. This might happen because a process has files open or has its working directory set in the target directory.
- /Users/satan/Library/github/ToDo-App/build/app/intermediates/incremental/mergeDebugAssets/merger.xml

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

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

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.4.2/userguide/command_line_interface.html#sec:command_line_warnings
BUILD FAILED in 5s
10 actionable tasks: 2 executed, 8 up-to-date
    from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in `method_missing'
    from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/fastlane/lib/fastlane/helper/sh_helper.rb:80:in `sh_control_output'
    from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/forwardable.rb:230:in `sh'
    from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/fastlane/lib/fastlane/helper/gradle_helper.rb:32:in `trigger'
    from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/fastlane/lib/fastlane/actions/gradle.rb:60:in `run'
    from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/fastlane/lib/fastlane/runner.rb:263:in `block (2 levels) in execute_action'
    from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/fastlane/lib/fastlane/actions/actions_helper.rb:69:in `execute_action'
    from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/fastlane/lib/fastlane/runner.rb:255:in `block in execute_action'
    from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/fastlane/lib/fastlane/runner.rb:229:in `chdir'
    from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/fastlane/lib/fastlane/runner.rb:229:in `execute_action'
    from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
    from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/fastlane/lib/fastlane/fast_file.rb:159:in `method_missing'
    from Fastfile:21:in `block (2 levels) in parsing_binding'
    from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/fastlane/lib/fastlane/lane.rb:33:in `call'
    from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
    from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/fastlane/lib/fastlane/runner.rb:45:in `chdir'
    from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/fastlane/lib/fastlane/runner.rb:45:in `execute'
    from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/fastlane/lib/fastlane/lane_manager.rb:47:in `cruise_lane'
    from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
    from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/fastlane/lib/fastlane/commands_generator.rb:110:in `block (2 levels) in run'
    from /Library/Ruby/Gems/2.6.0/gems/commander-4.6.0/lib/commander/command.rb:187:in `call'
    from /Library/Ruby/Gems/2.6.0/gems/commander-4.6.0/lib/commander/command.rb:157:in `run'
    from /Library/Ruby/Gems/2.6.0/gems/commander-4.6.0/lib/commander/runner.rb:444:in `run_active_command'
    from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:124:in `run!'
    from /Library/Ruby/Gems/2.6.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:in `run!'
    from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/fastlane/lib/fastlane/commands_generator.rb:354:in `run'
    from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/fastlane/lib/fastlane/commands_generator.rb:43:in `start'
    from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/fastlane/lib/fastlane/cli_tools_distributor.rb:123:in `take_off'
    from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.206.2/bin/fastlane:23:in `<top (required)>'
    from /usr/local/bin/fastlane:23:in `load'
    from /usr/local/bin/fastlane:23:in `<top (required)>'
    from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.11/lib/bundler/cli/exec.rb:58:in `load'
    from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.11/lib/bundler/cli/exec.rb:58:in `kernel_load'
    from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.11/lib/bundler/cli/exec.rb:23:in `run'
    from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.11/lib/bundler/cli.rb:483:in `exec'
    from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.11/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
    from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.11/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
    from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.11/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
    from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.11/lib/bundler/cli.rb:31:in `dispatch'
    from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.11/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
    from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.11/lib/bundler/cli.rb:25:in `start'
    from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.11/exe/bundle:48:in `block in <top (required)>'
    from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.11/lib/bundler/friendly_errors.rb:103:in `with_friendly_errors'
    from /Library/Ruby/Gems/2.6.0/gems/bundler-2.3.11/exe/bundle:36:in `<top (required)>'
    from /usr/local/bin/bundle:23:in `load'
    from /usr/local/bin/bundle:23:in `<main>' </pre>

Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
12.4

Ruby
2.6.8

Bundler?
false

Git
git version 2.32.1 (Apple Git-133)

Installation Source
/usr/local/bin/fastlane

Host
macOS 12.4 (21F79)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib

OpenSSL Version
LibreSSL 2.8.3

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
13.4.1

Swift Version
5.6.1

System Locale

Variable
Value

LANG
en_GB.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

default_platform(:android)

platform :android do
  desc "Runs all the tests"
  lane :test do
    gradle(task: "test")
  end

  desc "Submit a new Beta Build to Crashlytics Beta"
  lane :beta do
    gradle(task: "clean assembleRelease")
    crashlytics

    # sh "your_script.sh"
    # You can also use other beta testing services here
  end

  desc "Deploy a new version to the Google Play"
  lane :deploy do
    gradle(task: "clean assembleRelease")
    upload_to_play_store
  end
end

`./fastlane/Appfile`
json_key_file("") # Path to the json secret file - Follow https://docs.fastlane.tools/actions/supply/#setup to get one
package_name("com.listomania.listapp") # e.g. com.krausefx.app

fastlane gems

Gem
Version
Update-Status

fastlane
2.206.2
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.3.0

atomos
0.1.3

CFPropertyList
2.3.6

claide
1.1.0

colored2
3.1.2

nanaimo
0.3.0

rexml
3.2.5

xcodeproj
1.21.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.8.0

terminal-table
1.8.0

plist
3.6.0

public_suffix
4.0.6

addressable
2.8.0

multipart-post
2.0.0

word_wrap
1.0.0

optparse
0.1.1

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

artifactory
3.0.15

babosa
1.0.4

colored
1.2

highline
2.0.3

commander
4.6.0

excon
0.92.3

faraday-em_http
1.0.0

faraday-em_synchrony
1.0.0

faraday-excon
1.1.0

faraday-httpclient
1.0.1

faraday-multipart
1.0.4

faraday-net_http
1.0.1

faraday-net_http_persistent
1.2.0

faraday-patron
1.0.0

faraday-rack
1.0.0

faraday-retry
1.0.3

ruby2_keywords
0.0.5

faraday
1.10.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.5

faraday-cookie_jar
0.0.7

faraday_middleware
1.2.0

fastimage
2.2.6

gh_inspector
1.1.3

json
2.1.0

mini_magick
4.11.0

naturally
2.2.1

rubyzip
2.3.2

security
0.1.3

xcpretty-travis-formatter
1.0.1

dotenv
2.7.6

bundler
2.3.11

simctl
1.6.8

jwt
2.4.1

uber
0.1.0

declarative
0.0.20

trailblazer-option
0.1.2

representable
3.2.0

retriable
3.1.2

mini_mime
1.1.2

memoist
0.16.2

multi_json
1.15.0

os
1.1.4

signet
0.16.1

googleauth
1.1.3

httpclient
2.8.3

webrick
1.4.4

google-apis-core
0.6.0

google-apis-playcustomapp_v1
0.9.0

google-apis-androidpublisher_v3
0.22.0

google-cloud-env
1.6.0

google-cloud-errors
1.2.0

google-cloud-core
1.6.0

google-apis-iamcredentials_v1
0.12.0

google-apis-storage_v1
0.15.0

rake
12.3.3

digest-crc
0.6.4

google-cloud-storage
1.36.2

emoji_regex
3.2.3

jmespath
1.6.1

aws-partitions
1.600.0

aws-eventstream
1.2.0

aws-sigv4
1.5.0

aws-sdk-core
3.131.2

aws-sdk-kms
1.57.0

aws-sdk-s3
1.114.0

forwardable
1.2.0

logger
1.3.0

date
2.0.0

stringio
0.0.2

ipaddr
1.2.2

openssl
2.1.2

zlib
1.0.0

mutex_m
0.1.0

ostruct
0.1.0

strscan
1.0.0

io-console
0.4.7

fileutils
1.1.0

etc
1.0.1

libxml-ruby
3.2.1

psych
3.1.0

generated on: 2022-06-23

A really good post, very thankful and hopeful that you will write many more posts like this one.

I have exactly the same problem. Did anyone get a suggestion?


Update Composer dependencies (2024-09-23-00-18)

Visual regression test passed!
View the visual regression test report


Update development tool for docker image

Refactor docker information to use a published docker image:

Repository to build image

Build process

Docker Hub page

With this change, no need to build image locally for every user.
Besides that, it will give us option to use a standard image for all our test in CI instead of bootstrapping runner all time.

* [x]  make build - successful

* [x]  make run - successful

* [x]  make clean - refactored for new name - please validate!

Checked and worked fine. Also add deprecation warning for build command
$ make build
#docker build --no-cache -t avdteam/base:centos-7 .
echo ''; echo 'Deprecated command -- visit https://github.com/arista-netdevops-community/docker-avd-base to build image'; echo ''

Deprecated command -- visit https://github.com/arista-netdevops-community/docker-avd-base to build image

ansible-avd/development on  devel-use-dockerhub docker:(v19.03.8)
➜ make run
docker run --rm -it \
		-v /Users/xxx/.ssh:'/home/docker'/.ssh \
		-v /Users/xxx/.gitconfig:'/home/docker'/.gitconfig \
		-v /Users/tgrimonet/Projects/arista-ansible/ansible-avd/development/:/projects \
		-v /etc/hosts:/etc/hosts avdteam/base:centos-7
Agent pid 48
➜  /projects
➜  /projects
➜  /projects
➜  /projects
➜  /projects exit

ansible-avd/development on  devel-use-dockerhub docker:(v19.03.8)
➜ male clea
zsh: correct 'male' to 'make' [nyae]? %
ansible-avd/development on  devel-use-dockerhub docker:(v19.03.8)
➜ make clean
docker rmi avdteam/base:centos-7
Untagged: avdteam/base:centos-7
...

In Phase2 (another PR):

Remove docker Image
Update CI to use pre-configured image

reviewed and tested the latest updates!


Make dark mode optional

Original feature request on CW forum.

The light/dark mode switch in the trainer disappeared with one of the recent changes.

I had removed it temporarily because it's been buggy/broken for years and increases the cost of change. I'm planning to add it back after cleaning things up.

For some context, there was no theme (incomplete, light background), dark theme (default), inverted theme (buggy, enabled through light mode button), and light theme (?) for some reason and it was just a mess. Everything except dark theme seemed incomplete and overlapping.
When adding the theme switch back, I'll probably make it enable/disable dark theme (enabled by default, but also respects user's OS settings).

(enabled by default, but also respects user's OS settings).

As long as there is some option to override. I like the OSX dark menu bar, but have anything where I need to write text set to light. Terminals, Pycharm...
Thanks

Any updates?) Im looking light theme..

No, I'll close this issue when it's added back.

Deployed the new site wide theme switch. You can switch between dark/light using the moon/sun icon at the top.
I'm sure there's some things I overlooked and it's not the prettiest, but it should be usable. Please open issues if you find anything unreadable or if you have suggestions for improvements.

The code highlighting is poor in the light mode IMO. Using the dark mode, you can clearly see how different stuff is highlighted in purple (keywords), orange (function/class names and numbers), blue (methods), dark gray (comments), light gray (built-in function), and green (strings). With light mode, though, everything looks light-grayish with the original color mixed in a little:

I found a few other inconsistencies, or things that don't look very good IMO and could be improved. I wasn't sure whether to open a separate issue, and decided to list everything here.
The issue symbol is too bright compared to other symbols:

The shadows under cards are hard to see in dark mode, and look quite weird because of how they blend in with the background and the cards themselves:

Pressed drop-downs don't retain highlight in light mode (in both cases I clicked on the Progress button, and moved the cursor to the Status button):

The "ads via Carbon" message is illegible in light mode:

@FArekkusu Thanks!

I found a few other inconsistencies, or things that don't look very good IMO and could be improved. I wasn't sure whether to open a separate issue, and decided to list everything here.

Having separate issues are better since it's much easier to keep track.

The code highlighting is poor in the light mode IMO.

Yeah, the light mode have colors washed out. I'll try adjusting them to stand out little more.

The issue symbol is too bright compared to other symbols:

Codewars was/is using opacity a lot to adjust appearance and it was one of the pain points when adding light theme. This one has opacity: .75 to make it appear lighter on dark. I'll adjust both dark and light modes.

The shadows under cards are hard to see in dark mode, and look quite weird because of how they blend in with the background and the cards themselves

Yeah, the card was necessary to make the search result look decent in light mode. The original just listed the results on the background and that didn't work on light mode since it made the list of kata look unimportant when it's the main content.
I'll try adjusting the dark mode.

Pressed drop-downs don't retain highlight in light mode

Can you elaborate on this? Do you mean the background of "All" should match the background of "Approved"?

The "ads via Carbon" message is illegible in light mode:

I had overlooked this. It should be trivial to fix.

Can you elaborate on this? Do you mean the background of "All" should match the background of "Approved"?

Yes, to some extent. The drop-down button is black when the cursor is hovering over it, and it remains darkened after you click on it - the color isn't the same, but it's clear that the button is in focus. In light mode, on the other hand, the button goes back to the "default" white color.

Fixed "the issue symbol is too bright compared to other symbols" by changing the icon. The original was just too thin.
Fixed "Pressed drop-downs don't retain highlight in light mode".
Fixed illegible "ads via Carbon".
For syntax highlighting, I'll need some time to experiment. I'm considering to open source the theme so users can contribute.
For shadows in dark mode, I think the dark mode needs to be revamped. It currently has darker surfaces on top of a lighter background so it looks weird with the shadow.

I've just noticed that pre-processor direcrives in C/C++ are in purple which is hardly readable in dark mode (ealier it was gray, I believe). A similar thing could be happening in other languages too.

Please open new issues if you find anything else

I forgot that you asked to open separate issues yesterday, and listed new found problems together with the older ones :(
I'll open new ones if I notice anything else.


Try to use Pulsar 2.8.0-SNAPSHOT, requiring JDK11

I am trying to use Pulsar 2.8.0, but when I try to use it with the docker image it breaks with a JVM Core Dump
So I am exploring to use JDK11 with NB
in this case Fallout dies with:
2021-06-01 16:07:27,477 [FJP:927]             ERROR server-1             - [CMD-FAIL] Command completed with non-zero exit code 2: kubectl --namespace=mypulsar exec --container=nosqlbench nosqlbench-deployment-687dd4c7f6-28wg2 -- ash -o pipefail -c ' java -jar nb.jar run alias=produce_messages type=pulsar config=/fallout-library/config-txt/config.txt yaml=/fallout-library/pulsar-yaml/pulsar.yaml tags=phase:producer service_url=pulsar://pulsar-proxy:6650 web_url=http://pulsar-proxy:8080 async_api=true optype=msg-send threads=10 cycles=0..100000 host=dummy-cassandra --show-stacktraces -v --log-histograms /nosqlbench/produce_messages.hdr::5s --log-histostats /nosqlbench/produce_messages.csv::5s 2>&1 | tee /nosqlbench/produce_messages.log'
STDERR (last 2 lines):
ash: 0: Illegal option -o pipefail
command terminated with exit code 2

2021-06-01 16:07:31,377 [FJP:927]             ERROR server-1             - [CMD-FAIL] Command completed with non-zero exit code 2: kubectl --namespace=mypulsar exec --container=nosqlbench nosqlbench-deployment-687dd4c7f6-28wg2 -- ash -o pipefail -c ' java -jar nb.jar run alias=consume_messages type=pulsar config=/fallout-library/config-txt/config.txt yaml=/fallout-library/pulsar-yaml/pulsar.yaml tags=phase:consumer service_url=pulsar://pulsar-proxy:6650 web_url=http://pulsar-proxy:8080 optype=msg-consume cycles=0..100000 host=dummy-cassandra --show-stacktraces -v --log-histograms /nosqlbench/consume_messages.hdr::5s --log-histostats /nosqlbench/consume_messages.csv::5s 2>&1 | tee /nosqlbench/consume_messages.log'
STDERR (last 2 lines):
ash: 0: Illegal option -o pipefail
command terminated with exit code 2

2021-06-01 16:07:31,381 [clojure:254]         ERROR nofail               - History in jepsen-history.json contained 2 failures:
First failure: Operation{time=78763443371, process=produce_messages, module=nosqlbench, type=fail, mediaType="text/plain; charset=utf-8", value="nosqlbench failed"}
Last failure: Operation{time=82663184567, process=consume_messages, module=nosqlbench, type=fail, mediaType="text/plain; charset=utf-8", value="nosqlbench failed"}
2021-06-01 16:07:31,387 [clojure:254]         ERROR nofail               - Checker 'nofail' has failed the check.
2021-06-01 16:10:06,075 [ThreadedExecutor:34] ERROR generate_chart       - No HDR files found.

I have filed this issue upstream on Pulsar
https://github.com/apache/pulsar/issues/10798
This PR is only informative, it is not meant to be committed

I believe that we should not modify our Dockerfile here at NB.
Eventually someday we should move to jdk16, but we can wait for jdk17 as it will be LTS and it will be released on September

@jshook it looks like that with adoptopenjdk/openjdk15:alpine-slim the problem does not reproduce.
there should be some problem with Netty EPool Native and the libraries that are present in the openjdk-15 docker image.
The release of Pulsar 2.8.0 will be in a couple of weeks.
I wonder if we could  move to adoptopenjdk/openjdk15:alpine-slim when we move to Pulsar 2.8.0 client

As long as it works well after smoke testing, I think that is fine. It would be nice to get down the details on why this breaks, though.

@jshook it looks like that with adoptopenjdk/openjdk15:alpine-slim the problem does not reproduce.
there should be some problem with Netty EPool Native and the libraries that are present in the openjdk-15 docker image.
The release of Pulsar 2.8.0 will be in a couple of weeks.
I wonder if we could move to adoptopenjdk/openjdk15:alpine-slim when we move to Pulsar 2.8.0 client

It looks like there is someone who is willing top help in Netty project
https://github.com/netty/netty-tcnative/issues/649

@eolivelli Should we keep this open for now?

closing


feat: YARA-X dumper module

Dumping module for YARA-X. This module can be run by yr dump <binary-file> <options>, where options are not required and can be one of: --modules/-m=<module> and --output-format/-o=<format>.
Currently supported output formats are:

json
xml
toml
yaml
human-readable

Supported modules are all built-in modules that are retrieved in build.rs.
This module takes binary file and dumps parsed information to STDOUT. Modules used for parsing can be either selected and forced by using --modules/-m=<module>  option or if left empty it is automatically selected via validity_flag. This flag determines if module output is valid and therefore considered as successfully parsed. Validity flag is described in Module Developer's Guide.md. In terms of displayed output various formats are supported. User can specify also multiple modules used for parsing and output of all modules will be shown. Format can be selected via --output-format/-o=<format>. If left empty human-readable format is automatically selected. This format is basically valid YAML with additional colors and comments. This format also supports additional integer representation which can be selected by protobuf field descriptor and is also described in Module Developer's Guide.md.
Together with this I have also added parametrized tests for end2end testing and did a minor change in macho module, where dylib version was represented as an integer. It would make much more sense to have this as a string (last two digits represents patch version, previous two minor version and rest is major version number). cc @latonis
So far I have added validity flag into macho and lnk module.  Integer field representation descriptors were added only into macho module. I think module author should do both while developing the module so feel free to add it into other modules that produces output or change it in existing modules.

The API proposed for the yara-x-dump crate is not the most appropriate in my opinion, as it creates a dependency from the yara-x crate itself, because it needs the compiler and scanner for producing the module's output. It looks like the thought process was: I need to dump the information produced by a list of module names, let's create an API that does exactly that, put it as an independent crate, and call it from yara-cli.
The thought process should be quite the opposite: I need to dump the information produced by a list of module names, Which abstractions or building blocks do I need for implementing this into yara-cli?.
The must obvious abstraction to me is: given a &dyn MessageDyn containing the data and specification for a protobuf message, let's produce a text representation of it in one the supported formats. For the JSON format it's straightforward, as we already have the protobuf_json_mapping crate. For very basic YAML output we could simply use serde_yaml, but we want a human-friendly YAML output that can be controlled from the corresponding .proto files, so that's where the our crate should specialise on.
This is the right abstracion: a crate that is able to produce YAML output for &dyn MessageDyn messages produced by the protobuf crate, but allowing customization of the produced YAML via protobuf options. This has potential for a fully standalone crate that anyone can use in its own project!
The YAML protobuf customization options don't need to be in the yara.proto file (in the yara-x-proto crate). They could reside in some other yaml.proto file located in this independent crate, which would allow to implement it as a truly independent crate that doesn't depend on YARA-X at all, not even on the tiny yara-x-proto crate. But for now we could simply use the yara.proto file.
Regarding the protobuf customization options, the boolean hex_value is ok ([(yara.field_options).hex_value = true]), but I'm thinking on a more flexible mechanism, like [(yara.field_options).yaml_fmt = "x"]. Another format option could be "t" for a timestamp, and "f:SomeEnumType" for a fields that are a set of flags represented by a protobuf enum named SomeEnumType. Example:
enum MyFlags {
   Foo = 0x01;
   Bar
}

Let's go back to the drawing board...
The only thing we really need here is a crate (let's call it yara-x-proto-yaml) that does exactly one thing, take a &dyn MessageDyn and return a String with the message encoded in YAML format. Nothing else.
This crate doesn't need to produce JSON, or anything else, it's just a protobuf -> YAML converter. The two special features we need in this crate are:

Optional colors in the YAML output (no colors by default)
In your .proto files can use options for controlling some aspects of the YAML generation, like whether an integer should be rendered in hex, or whether a field is a timestamp that should be accompanied by a comment with the date and time in human readable format.

Let's go back to the drawing board...
The only thing we really need here is a crate (let's call it yara-x-proto-yaml) that does exactly one thing, take a &dyn MessageDyn and return a String with the message encoded in YAML format. Nothing else.
This crate doesn't need to produce JSON, or anything else, it's just a protobuf -> YAML converter. The two special features we need in this crate are:

Optional colors in the YAML output (no colors by default)
In your .proto files can use options for controlling some aspects of the YAML generation, like whether an integer should be rendered in hex, or whether a field is a timestamp that should be accompanied by a comment with the date and time in human readable format.

Once we have this, the remaining bits are very straightforward.

Thank you for suggestions. Basically I agree with everything.

This crate doesn't need to produce JSON, or anything else, it's just a protobuf -> YAML converter

I have removed all other forms of serialization and cleaned the crate to provide only protobuf -> YAML conversion

Optional colors in the YAML output (no colors by default)

This is implemented by yansi::Pait::disable() method that turns off all ANSI colors, it works for both YAML and JSON. I have also implemented colors for json using external library just for this it also pretty-formats the string so even with disabled colors the output is more readable.

In your .proto files can use options for controlling some aspects of the YAML generation, like whether an integer should be rendered in hex, or whether a field is a timestamp that should be accompanied by a comment with the date and time in human readable format.

I have done this as you suggested and used one unified (yara.field_options).yaml_fmt descriptor that takes string as an input. Right now I only look for "x" for hexadecimal and "t" for timestamp, this can be easily extended in the future. Hexadecimal value is used to replace the original integer one and timestamp is printed as a comment next to the integer version. In future I would like to also implement the flags, but at this point I need to figure out how to get an enum with specified name from the code itself, it looks like there is only a getter for fields.
In case you have any other notes/suggestions feel free to let me know.

This is much better now, but it still needs a bit polishing. I'm refactoring a few things to provide a mechanism for passing arbitrary data to any module by name, without having to use the trick of creating a dummy rule that imports that module. Once I have it we will be able to remove that part of the code and make it cleaner.
In the meanwhile I'll review other aspects of the code.

Take a look at this PR: https://github.com/VirusTotal/yara-x/pull/52
It introduces two new functions that allow invoking a module without having to create a dummy YARA rule. Basically you would to something like:
let elf_info = yara_x::mods::invoke_mod::<yara_x::mods::ELF>(data)?;
let lnk_info = yara_x::mods::invoke_mod::<yara_x::mods::Lnk>(data)?;

With that you will get the Rust structure corresponding to each module. There's another version that returns Box<&dyn MessageDyn>
let elf_info = yara_x::mods::invoke_mod_dyn::<yara_x::mods::ELF>(data)?;
let lnk_info = yara_x::mods::invoke_mod_dyn::<yara_x::mods::Lnk>(data)?;

Take a look at this PR: #52
It introduces two new functions that allow invoking a module without having to create a dummy YARA rule. Basically you would to something like:
let elf_info = yara_x::mods::invoke_mod::<yara_x::mods::ELF>(data)?;
let lnk_info = yara_x::mods::invoke_mod::<yara_x::mods::Lnk>(data)?;

With that you will get the Rust structure corresponding to each module. There's another version that returns Box<&dyn MessageDyn>
let elf_info = yara_x::mods::invoke_mod_dyn::<yara_x::mods::ELF>(data)?;
let lnk_info = yara_x::mods::invoke_mod_dyn::<yara_x::mods::Lnk>(data)?;

Thank you, I have just pushed the latest version which makes an use of this new API and should incorporate all of you suggestions.

Hi Victor, thank you for you review. I have addressed your issues and added all features into your template in #53. We can continue to discuss it there. Thank you!

Merged in #53


[Refactor][Framework] Extract scope/remote helper to avoid duplicated code in every plugin

What and why to refactor
Right now, in our plugins, we have to duplicate a lot of code to write scope/remote api
Describe the solution you'd like
We can extract scope/remote helper to reduce duplicated code

fixed already, please check related prs


Bug fix for a rare edge case

We're decrementing the off-target position by 1 (for reasons I don't understand), in all cases, in the map_int_to_coord function, only to compensate for it later by adding 2 instead of 1 (again in all cases) when we use its output in the map_coord_to_sequence function.
While both these in conjunction have the same effect as not decrementing at all, and incrementing by 1 instead of 2 later (which feels natural and is what the upcoming PR for these calculations in C++ will do), it does affect the very rare case (3 cases out of ~5M for ce11) where the off-target match is exactly at the start of the chromosome, in which case the map_int_to_coord function ends up reporting the chromosome that is before where the off-target actually lies, and subsequent code in the script throws away the off-target as invalid (because it determines that its not 23 BPs long after all).
There is no other place where the pos output of map_int_to_coord is used other than map_coord_to_sequence, so this has no side effects. I've run the script before/after on the sam file for ce11 and it produces exactly the same output, except for the 3 cases that it fixes.
While not a big deal practically, this PR will reduce the confusion around the -1 and +2, so I think it's worthwhile.

This look good.


Add option to set the nodePort mapping.

When choosing NodePort kind, the port exposed is randomized from a range. in some runtimes (Kind for example) you need to explicitly do port forwarding:
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
- role: control-plane
  # port forward 30080 on the host to 30080 on this node
  extraPortMappings:
  - containerPort: 30080
    hostPort: 30080
- role: worker

This is impossible if the nodePort cannot be predetermined.

@ydan287 are you referring to the opentelemetry-collector chart's ports section?
# Configuration for ports
ports:
  otlp:
    enabled: true
    containerPort: 4317
    servicePort: 4317
    hostPort: 4317
    protocol: TCP
  otlp-http:
    enabled: true
    containerPort: 4318
    servicePort: 4318
    hostPort: 4318
    protocol: TCP
  jaeger-compact:
    enabled: true
    containerPort: 6831
    servicePort: 6831
    hostPort: 6831
    protocol: UDP
  jaeger-thrift:
    enabled: true
    containerPort: 14268
    servicePort: 14268
    hostPort: 14268
    protocol: TCP
  jaeger-grpc:
    enabled: true
    containerPort: 14250
    servicePort: 14250
    hostPort: 14250
    protocol: TCP
  zipkin:
    enabled: true
    containerPort: 9411
    servicePort: 9411
    hostPort: 9411
    protocol: TCP
  metrics:
    # The metrics port is disabled by default. However you need to enable the port
    # in order to use the ServiceMonitor (serviceMonitor.enabled) or PodMonitor (podMonitor.enabled).
    enabled: false
    containerPort: 8888
    servicePort: 8888
    protocol: TCP

You would like to specify nodePort as well?

Yes, exactly. That should allow running the chart with Kind locally.


Remove maybe_upgrade_password_hash

Starting from 411c130ea63c3423d7ea71743095dfb446680da6 we accidentially
upgrading user's password to pbkdf.
Removing upgrade code.

+1


Performance

Currently Swift suffers some pretty serious performance issues with generics. After converting this library to not use Generics, I am seeing around a 30x increase in speed generating the standard MandelbrotSet. You might consider removing the generics until Swift is more mature.

Isn't this largely a Swift problem? I get that a performance tweaked version of this library might be nice, but a performance tweaked version of generics would be better.

So far as I see with my own Mandelbrot Set implementation (see MandelPlot in the playground), performance is okay with Swift 2.  Swift 2 still has issues with generics (you can't still do x is ProtocolType, for one thing) but in terms performance it's much better now.
I considered closing this issue but I'll leave it open to pick up any hint to improve performance -- without giving up generics.

Perhaps the issue here is that performance is not benchmarked.
A simple test case may be the minimally viable product to close this issue.


[SPARK-4945] [SQL] Add overwrite option support for SchemaRDD.saveAsParquetFile

/cc @rxin
More API questions.

Test build #25409 has started for   PR 3780 at commit 72c4a4b.

This patch merges cleanly.

Test build #25409 has finished for   PR 3780 at commit 72c4a4b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25409/
Test PASSed.

The changes lgtm. I left couple small comments. Do you mind fixing those?

@rxin what about the question of append, overwrite, error?  Do we want to expose all three for these types of interfaces?

For my understanding, insertInto works in the ways of create new, append or overwrite already, but it doesn't give user an option, which allow throwing exception when the file already existed. Probably that's why we  need the saveAsParquetFile, which in the semantic of create new if the file doesn't exist, or overwrite provided by this PR.
I can close this PR if you feel this change is worthless.

Test build #25860 has started for   PR 3780 at commit 8782fef.

This patch merges cleanly.

Or probably we can cleanup those APIs, kind of like:
trait Mode
object Append extends Mode
object Create extends Mode
object CreateOrOverwrite extends Mode
object CreateOrAppend extends Mode

def outputFile(path: String, format: FileFormat=defaultFormat, mode: Mode = CreateOrOverwrite)
def insertIntoFile(path: String, format: FileFormat) = outputFile(path, format, CreateOrOverwrite)
def toCsv(path: String, mode: Mode) = outputFile(path, CSV, mode)
def toParquet(path: String, mode: Mode) = outputFile(path, Parquet, mode)

Any ideas?

Test build #25860 has finished for   PR 3780 at commit 8782fef.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25860/
Test PASSed.

I kind of like a proposal like that, but we need to make it Java friendly as well.

OK, I will close this.


Graph compiler API interface

Opening this PR so we can discuss the GC API in one place

Moved the interface to the oneDNN project.


Extract jevt array misses as novalue

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If contributing rules or changes to rules, please make sure to also uncomment one of the following line:

/kind rule-update

/kind rule-create

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area rules

/area tests

/area proposals

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

fix(userspace/engine): properly handle field extraction over lists of containers when not all containers match the specified sub-properties

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please ask for approval from mstemm after the PR has been reviewed.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 4cee3e32a8b9449b756c20be6114da7bb74b21d3

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leodido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/milestone 0.28.0

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fntlnz, leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [fntlnz,leodido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fntlnz, leodido, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [fntlnz,leodido,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Made a few corrections on the doc.

Hi,
I was going through the docs on the website and I noticed a few errors. I hope you don't mind the corrections and maybe I can get to go through the rest of it, if you don't mind?

Thanks men!, this is the kind of help that I most appreciate


Save VBA flow information as users type

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

Action Performed:

Click on Get started in /workspace/<policyID>/card in New Expensify.
Input information into the fields.
Close the right pane without clicking on Save & Continue
Click on Get started again and verify that the information is lost.

More context in this thread and this issue
Expected Result:
A user should see the entered information when reopening the right pane.
Actual Result:
Users loose the information entered.
Workaround:
Retype everything!
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number:
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
View all open jobs on GitHub

@luacmartins Would you mind summarizing the approach here before we start? I'm curious about what the plan will be.

I was thinking of a similar approach we use for the draft comments. On a high level:

Create a new Onyx key draftReimbursementAccount where we will store all the draft data.
Create a updateDraftReimbursementAccount function that will:

Take a key-value pair as argument, e.g. updateDraftReimbursementAccount({routingNumber: '1234'})
Merge that key and value to the draftReimbursementAccount Onyx key

Update the onChangeText handlers of each input to also call a debounced version of updateDraftReimbursementAccount
Update the state in each step to take in the value stored in the new Onyx key as default, for example in BankAccountStep.js, update the state:

From routingNumber: props.achData.routingNumber || '',
To routingNumber: props.achData.routingNumber || props.draftReimbursementAccount.routingNumber || '',

We could also delete the related key-value pairs from the Onyx key once the user clicks Save & Continue

What are your thoughts?

So draftReimbursementAccount is going to collect all the data for the form fields as we enter it and we will just populate the state for each step when there is no achData values.
I think it works. My only concern would be it feel slike we are starting to have a lot of state to manage since we'll have:

draft state (used to populate the component and save changes)
server state in the achData (also used to populate the component)
component level state (to track local changes and submit new values)

Is there a reason why we should we decide to use the achData value first and only use the draft value if we don't have achData?
Future us convo: Feels like something we might want to incorporate on a per "form" basis for a more refined form component in the future so that the "draft" feature is opt-in instead of having to be set up. But not sure if that's an optimization we need to worry about now.

Hmmm... That's a good question. The reason that I can think of is if a user has data in the server, but for some reason wipes draftReimbursementAccount (e.g. logs out, resets browser data, etc) we wouldn't display accurate data.
I agree with your concern here and I'm also open to brainstorming other ideas.
As you mentioned, having a form component that keeps track of draft data, as well as input errors would be a great optimization in the future.

The reason that I can think of is if a user has data in the server, but for some reason wipes draftReimbursementAccount (e.g. logs out, resets browser data, etc) we wouldn't display accurate data.

I think you're saying that if a user:

has begun the flow and gone far enough to save some achData
then accidentally clears their local storage or signs out
we would end up with inaccurate data if we prioritized using the draft values over the achData values

But I think in that case we'd still default to using the achData values since the draft values are empty?
Thinking more on this though... it does seem possible that a user might do something like:

continue setting up an account that has achData set
the user decides to overwrite values with new ones instead
they then stop in the middle of the flow without saving any of that data to the server

If they restart the flow which values should they expect to see?

But I think in that case we'd still default to using the achData values since the draft values are empty?

Ah I see what you mean. So, we would do something like this?
routingNumber: props.draftReimbursementAccount.routingNumber || props.achData.routingNumber || ''
In that case, what I said before wouldn't be a problem.

If they restart the flow which values should they expect to see?

That's a really good point! We could argue either way. If the user intentionally stops the flow, they would expect to see achData. However, we could also argue that "stop in the middle of the flow" is similar to accidentally closing the right pane and, in that case, if they see achData they would have lost their edits, which is what we are trying to fix here.
@kevinksullivan for additional input in this scenario.

Yeah I think I mostly agree that the user would expect to see whatever they were editing before they got interrupted and not just whatever we managed to save in the server so in that case we'd do:

try to use the draft first if it exists
then use the values in achData if we have those

👍
But one caveat here is that once we've saved that data to the server... it doesn't feel like we'd need the "draft" anymore. Is there some point where we should ever clear those out?

Awesome! I'm on board with always showing the latest draft.

But one caveat here is that once we've saved that data to the server... it doesn't feel like we'd need the "draft" anymore. Is there some point where we should ever clear those out?

I think that would be step 5 from my original approach. We would clear those key/value pairs throughout the flow and finally delete the key when completing the last step.

We could also delete the related key-value pairs from the Onyx key once the user clicks Save & Continue

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @marcaaron in version: 1.0.96-1 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @francoisl in version: 1.0.97-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

Issue deployed to prod 7 days ago. Closing.


advice: ship the built binary along with the source code.

advice for  ship the built binary along with the source code.
so we can quickly test it without mannally  build it.
thanks

Next version will do it.


Test bug

Search terms you've used
This is a test bug
Describe the bug

To Reproduce
Steps to reproduce the behavior:

Given this data: …
Call this function …
See error

CodeSandbox

Expected behavior

Log output

Environment

$ npx envinfo --system --npmPackages --binaries --npmGlobalPackages --browsers

Additional context

test comment

@nicolasmondada Did the test succeed? Can we close this bug?


Log or throw exception if user tries to consume uncached request body twice

Describe your issue

https://github.com/javalin/javalin/commit/698f1a3a1750594eda975cf34f2858fcc602d4c5


Support ProxyCommand in SSH?

Do you plan to support ProxyCommand in SSH to allow jumping to the target server from a jump host?

Try in ~/.ssh/config and set new line ProxyCommand ssh -W %h:%p jumphost1. Do you think this can work? Source.

Try in ~/.ssh/config and set new line ProxyCommand ssh -W %h:%p jumphost1. Do you think this can work?

Sorry I don't totally follow. Does this mean this should work?
I have in my ssh/config
Host foo
  Hostname foo
  User marius
  ProxyCommand ssh -W %h:%p marius@bar

and ssh foo from the command line works, but it does not work if I add "Add new host SFTP" from Atom nd put "foo" as the hostname.
Any way to make this work at the moment? Thanks.


Client crash in custom modpack

https://paste.dimdev.org/ufapujamob.mccrash

Looks like this modpack is running an old version of the mod - if you can upgrade the mod to 1.0.3 that may well help with this issue.


Identify the boot loader

Whether it's BIOS, EFI, UEFI, Coreboot or Libreboot.

Do you have any thoughts on how do to this/documentation you can point me to?

A good place to start :+1:
http://sourceforge.net/projects/bootinfoscript/

Thanks!
It looks like this requires root privileges, but I'll look through it for data that can be accessed by a non-root user.

Great :)

sudo dmidecode -s bios-vendor
Not very reliable, but it should add a basic support to it.

Both of these methods require root privileges, so I'm hesitant to add them to screenfetch-c.
I'll continue looking for filesystem indicators/another way to get this information, but I'm not
sure it's possible under the current security context that screenfetch-c is expected to be run (non-root users).

Maybe just add a check, if it is a non root user, then simply don't display it.

That's do-able, but running screenfetch-c as root will cause additional problems (particularly with opening connections to X11 for graphical information). I also don't want to encourage people to run it as root regularly - there have been a fair share of fatal bugs in screenfetch-c and any one of them while running as a superuser could cause a crash.
I do like the idea of adding bootloader information to screenfetch-c, but unfortunately I don't think it's possible with current techniques without requiring users to trust it with heightened access. I'll leave this issue open for the time being in the event that another way of obtaining this information is found.

I see... Usually, it's the other way around. Haha

Yeah, it's more of an architecture problem than anything else.
I wrote screenfetch-c over 3 years ago as a way to teach myself C, and its structure leaves a lot to be desired. I've been planning a rewrite for a few months that'll modularize a large part of the detection system, but I haven't had time to work on it. When I get around to that, adding detections that specifically require root access should be more doable.

Ahhh ok :)


feat: Expose Translation react-i18next component

These changes export the react-i18next Translation component from the next-i18next module. I found this component the best match for introducing translations in the Page.getLayout function. The useTranslation hook is not allowed because the getLayout function is not top-level.
I also added test coverage for the Translation component by using it on the second page to render the header. It's tested by yarn test:e2e.

Thank you for a great package @isaachinman! I pushed a new commit, but it seems the codeclimate and node-multi-build checks are not running. It seems that this other PR also has the same issue https://github.com/isaachinman/next-i18next/pull/1593
Is there something wrong with the Circle CI integration?

Not sure @myrjola, but it appears something is indeed wrong for forked PRs. I've regenerated the CircleCI ssh key – do you mind trying again? Thanks!

Added the Translation export to the types.ts file.

Thanks @myrjola!


Code completion window too small on high resolution screens

Description of your problem
I have a new laptop with a resolution of 2560 x 1440 running the latest Windows10. However I have found that the code competion window in the spyder editor is too small.  This is indepdnent of the font size used in the editor. See enclosed image.

What steps will reproduce the problem?

Launch spyder in high res screen.
Import numpy as np
Type np. and hit tab to bring up code competion window in editor

What is the expected output? What do you see instead?
Output should be a bigger code competion window.
Please provide any additional information below
I migth be useful to have preference options to change the size of the code competion window.
Versions and main components
Spyder 3.2.3 on latest Windows 10

Spyder Version:
Python Version:
Qt Version:
PyQt Version:
Operating system:

Dependencies
Please go to the menu entry Help > Optional Dependencies (or
Help > Dependencies), press the button Copy to clipboard
and paste the contents below:
IPython >=4.0;<6.0:  5.5.0 (OK)
cython >=0.21     :  None (NOK)
jedi >=0.9.0      :  0.11.0 (OK)
nbconvert >=4.0   :  5.3.1 (OK)
numpy >=1.7       :  1.13.3 (OK)
pandas >=0.13.1   :  0.20.3 (OK)
pycodestyle >=2.3 :  2.3.1 (OK)
pyflakes >=0.5.0  :  1.6.0 (OK)
pygments >=2.0    :  2.2.0 (OK)
pylint >=0.25     :  1.7.4 (OK)
qtconsole >=4.2.0 :  4.3.1 (OK)
rope >=0.9.4      :  0.10.7 (OK)
sphinx >=0.6.6    :  1.6.4 (OK)
sympy >=0.7.3     :  1.1.1 (OK)

@dalthviz, please work on this one. The widget should have a minimal size and it should expand according to font size.

Just checking, @hsauro do you enabled the auto high DPI scaling?:

This is still a problem as the completion widget is not growing.
See:

This should be a simple fix, so I added it to 4.1

Note: https://forum.qt.io/topic/69978/scaling-widget-according-to-screen-scaling-ratio-in-os/12

I am also facing this problem. When I updated spyder from 3.3 to 4.0, the autocompletion window size is too small. It will not change when I change the font size. The high DPI setting will not solve this issue either.

The box itself is still a little small. Can you add an option to resize it using the mouse cursor? On my machine (Debian Bookworm, Spyder 5.4.2) not even the word "function" completely fits in the screen.

A drag resize option that remembers the size would fix these issues once and for all.


Localize WebManifest

In this way the description screenshots and shortcuts are translated too

Apparently this can be done by creating multiple webmanifest per lang like en.manifest.webmanifest then on the frontend choose one or another depending on $locale


ENOENT: no such file or directory...

When I drag and drop a file on to a folder to overwrite an old file, I get the following error:
ENOENT: no such file or directory, rename '' -> /path/to/folder/

What should occur:
When I drop the new file onto the folder, if the file exists I should be prompted to ask if I want to overwrite the old one.
Atom 1.3.2 on Mint 17.2

Does this happen for all files you are dropping and overwriting or only certain ones?
This is what I see when I try to reproduce it:

I created a folder named test with an empty file named test.json in that folder. I set the project folder as test. Created an empty file named test.json on the desktop (outside of project), then dragged the desktop file on top of the test folder. Below is the error:

@jersten thanks so much for the specific steps, will take a look :+1:

As an update; this bug is in 1.5 as well.


Prepare the new release

Codecov Report

Merging #47 (1530b73) into master (53180f2) will increase coverage by 0.52%.
The diff coverage is 99.04%.

@@            Coverage Diff             @@
##           master      #47      +/-   ##
==========================================
+ Coverage   93.19%   93.71%   +0.52%
==========================================
  Files          12       12
  Lines        1602     1703     +101
==========================================
+ Hits         1493     1596     +103
+ Misses        109      107       -2

Impacted Files
Coverage Δ

subaligner/logger.py
93.54% <83.33%> (+0.21%)
:arrow_up:

subaligner/network.py
93.69% <95.65%> (+0.03%)
:arrow_up:

subaligner/embedder.py
91.66% <100.00%> (+0.59%)
:arrow_up:

subaligner/hparam_tuner.py
100.00% <100.00%> (ø)

subaligner/hyperparameters.py
96.52% <100.00%> (+0.99%)
:arrow_up:

subaligner/media_helper.py
91.20% <100.00%> (+0.24%)
:arrow_up:

subaligner/predictor.py
90.75% <100.00%> (+0.07%)
:arrow_up:

subaligner/singleton.py
100.00% <100.00%> (ø)

subaligner/subtitle.py
95.86% <100.00%> (+0.32%)
:arrow_up:

subaligner/trainer.py
93.00% <100.00%> (+0.14%)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

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


Can an alternative alternatives set of animations be driven by a Pinch Gesture?

I know that RazzleDazzle basically works with logical time and therefore is inherently linear. This, when tied to the scroll gesture / contentOffset makes for a natural linear animated interaction.
However, as well as scrolling, I'm interested in letting the user 'zoom out' from that animated interaction so that they see, in effect, a 20,000ft view of the content they were just looking at. i.e. we want to tie animations to a change in zoomLevel as well.
I just want to confirm, that it's possible to attach, say, TWO (or any number for that matter!) of animators to a View's various different properties?
e.g.
x-scroll animates alpha — fades between 0 and 1
y-scroll animates size — scales object frame between 0 and 1

Yes, that should work perfectly! Just make sure you have one animator that animates based on the x-scroll, and a second animator that animates based on the y-scroll. And, use animations that won't conflict with each other, the same way you would if they were all controlled by a single animator (eg., only one scale animation per view).

I'd love to see how this turns out!


NEXT-33234 - feat: implement product-stream custom field entity select

This is a followup PR. #3024 included a bug. It only worked if the custom field name was equal to the entity name. I now noticed this and fixed it accordingly. Please see the second commit what I changed since #3024

Disclaimer: I tested this in my production project running on SW v<IP_ADDRESS>; I rebased these changes on the trunk branch and adjusted according to the changes I saw in the git history for each modified file since the last PR I made.
The only actual changes I did while rebasing from #3024 to trunk was changing v-model to v-model:value and v-model:ids.
I have no SW 6.5+ environment where I could test my changes.

1. Why is this change necessary?
We created a custom field with type entity on products. Currently when creating a new dynamic product stream you can select the custom field, but you need to enter the UUID value.
2. What does this change do, exactly?
This change implements the usage of sw-entity-single-select/sw-entity-multi-id-select fields in these cases, so we get a nice filterable dropdown.

Disclaimer: This patches an urgent need of a customer of us. This PR could be used as is, but this only patches the UX for CustomFieldTypes::ENTITY.
Many other CustomFieldTypes also require a similar patch which I won't provide. A clean solution would be to move the condition rendering for custom fields into an own component. Also the filter type should update when using specific custom field types, e.g. date.

3. Describe each step to reproduce the issue or behaviour.

Create a custom field:

type: Shopware\Core\System\CustomField\CustomFieldTypes::ENTITY ('entity').
config:

// use Shopware\Core\System\CustomField\CustomFieldTypes;

[
  'entity' => 'product', // or another entity with a name and some entries
  'componentName' => 'sw-entity-single-select',
  'customFieldType' => CustomFieldTypes::Entity,
  'customFieldPosition' => 10,
  'label' => [
      'en-GB' => 'Entity-Test',
      'de-DE' => 'Entity-Test',
  ],
],

Go to any product and assign a value to the Entity Test custom field. You need to know the UUID of that value for step 5.
Create a new dynamic product group
Select Entity-Test => equals or equalsAny
Now you need to enter the UUID of the entity we selected in step 2 to make the product show up in the preview.

With the change applied we now have a dropdown field where we can select the entity/entities instead of entering plain UUID(s).
4. Please link to the relevant issues (if any).
5. Checklist

[x] I have rebased my changes to remove merge conflicts
[ ] I have written tests and verified that they fail without my change
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

cc @King-of-Babylon

Hi @RafaelKr
Thank you for your contribution to our component. I already added some small feedback on that.
Could you please add some tests relevant to your changes?

Thanks for your contribution @RafaelKr . Your merge request has been merged. 🎉


permit plugins to be packages

This change makes this possible:
@@config/plugins
-watch/server
+watch

ls plugins/watch
index.js
html

Should we do this the way node_modules works and read a package.json for the main module name?

On Apr 26, 2015, at 12:40 PM, Matt Simerson<EMAIL_ADDRESS>wrote:
This change makes this possible:
@@config/plugins
-watch/server
+watch
ls plugins/watch
index.js
html
You can view, comment on, or merge this pull request online at:
https://github.com/baudehlo/Haraka/pull/943
Commit Summary
permit plugins to be packages
File Changes
M plugins.js (1)
Patch Links:
https://github.com/baudehlo/Haraka/pull/943.patch
https://github.com/baudehlo/Haraka/pull/943.diff
—
Reply to this email directly or view it on GitHub.

@baudehlo - yeah I think so.  But also shouldn't this also be looking in <haraka_install_dir>/node_modules/<plugin_name>/{index.js/package.json} instead of <haraka_install_dir>/plugins/<plugin_name>/{index.js/package.json}??
We ship a <haraka_install_dir>/package.json don't we, so if you put the plugins you want to install in that and do an npm install; the plugins are going to end up in <haraka_install_dir>/node_modules aren't they?   Or am I misunderstanding the purpose of that package.json?
I definitely think this a good improvement though.

Yeah that is stage two.

On Apr 26, 2015, at 3:15 PM, Steve Freegard<EMAIL_ADDRESS>wrote:
@baudehlo - yeah I think so. But also shouldn't this also be looking in <haraka_install_dir>/node_modules/<plugin_name>/{index.js/package.json} instead of <haraka_install_dir>/plugins/<plugin_name>/{index.js/package.json}??
We ship a <haraka_install_dir>/package.json don't we, so if you put the plugins you want to install in that and do an npm install; the plugins are going to end up in <haraka_install_dir>/node_modules aren't they? Or am I misunderstanding the purpose of that package.json?
I definitely think this a good improvement though.
—
Reply to this email directly or view it on GitHub.

I smell three different steps all leading in the same direction:

baby step: this PR, adding index.js support
one step: read and parse index/package.json and follow the main property.
big step: install plugins as npm packages

I think moving in that direction is certainly a good idea. We'd want a separate haraka-plugin-test harness that plugins in separate repos could import (at test time, perhaps, with a git submodule) and then run their tests under.
With a nice web admin panel, we wouldn't need to ship any plugins with Haraka. Install Haraka, configure an admin user, point at https://my.mail.com/admin/ and then click checkboxes for which plugins you want to use. Under the covers, clicking the checkboxes does a:
cd $haraka_install; npm install $package

With a web ui, every plugin gets a nice name, description, travis build test results icon, and versioning. There's a whole lotta fun that can be had down that road.

Agreed.

On Apr 26, 2015, at 3:28 PM, Matt Simerson<EMAIL_ADDRESS>wrote:
I smell three different steps all leading in the same direction:
baby step: this PR, adding index.js support
one step: read and parse index/package.json and follow the main property.
big step: install plugins as npm packages
—
Reply to this email directly or view it on GitHub.


limited busybox

Doing:
iex(32)> System.cmd("/bin/busybox", ["--list"])
{"ash\ncat\ncp\ndate\ndmesg\nfatattr\nhalt\ni2cdetect\ni2cdump\ni2cget\ni2cset\nid\nip\nipaddr\niplink\niproute\niprule\niptunnel\nkill\nkillall\nls\nlsmod\nmodprobe\nmount\nntpd\npoweroff\npwd\nreboot\nrm\nrmmod\nsh\nsha256sum\nudhcpc\nuevent\numount\nunzip\n", 0}

A much larger list of busybox commands are here.
How would I get these missing commands: ps, df, du, find, free, grep ?
I assume nerves is being minimalistic/secure, so this is not critical, but it's always nice to poke around, and knowing how to add/change the default busybox would be nice.

@cleesmith As this isn't QEMU-specific, this would probably be better directed at https://github.com/nerves-project/nerves or on the #nerves Slack channel.


nil from recover function could not be compared properly

The following program sample.go has an unexpected result:
package main

import "fmt"

func div(a, b int) (result int) {
	defer func() {
		r := recover()

		fmt.Printf("r = %#v\n", r)

		if r != nil {
			result = 0
		}
	}()

	return a / b
}

func main() {
	println(div(30, 2))

}

Expected result:
$ yaegi ./sample.go

r = <nil>
15

Got:
$ yaegi ./sample.go
r = <nil>
0

So the nil value r in the defer function is not real "nil" value?

Is it fixed? I still cannot get the correct result in the newest version.

Indeed, this bug is not fixed by the change in #633. Sorry for that, it's our mistake. We reopen the issue.


[macOS] point Xcode 13.4 to 13.4.1

Description
Announcement(issue-7127): Xcode 13.4 will be pointing to Xcode 13.4.1 and Xcode 13.4 removed.
Related issue:
https://github.com/actions/runner-images/issues/7127
Check list

[x] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

/azp run macos12


Having multi container Templates / Workflow Steps

Is this a BUG REPORT or FEATURE REQUEST?:
FEATURE REQUEST
What happened:
It seems that now each Workflow Step (template) can only have exactly one container. The resulting pod then also has only container. It would be benefical to be able to have multiple containers for each step, since Kubernetes support this (a Pod can have mutliple containers). This would allow us to have different containers talking to each other (inside one Pod).
What you expected to happen:
Instead of having only one "container" entry per template change it to "containers" and allow multiple images to be added.
Another idea would be to create templates inside templates to allow multiple containers to be in the same pod.
Anything else we need to know?:
I am new to the project, so maybe there is already something similiar out there and I was just not able to find it :-)
Thanks
Marcel

Can be solved using sidecars...

@rummens  can you provide more info regarding the sidecars silution ? many thanks !

@rummens can you provide more info regarding the sidecars silution ? many thanks !

You can find more details here, KFP runs Argo under the hood. So most Argo features are in KFP as well.
https://argoproj.github.io/argo/examples/#docker-in-docker-using-sidecars


 You should too.

Documentdetails
⚠ Dit gedeelte niet bewerken. Het is vereist om problemen te koppelen tussen docs.microsoft.com en GitHub.

ID: dbdbe4c8-400b-0f3f-2214-4233a05c1752
Version Independent ID: 4dafb9ad-de23-5d3c-130e-c1baa944ecb4
Content: Backlog best practices - VSTS & TFS
Content Source: docs/boards/backlogs/best-practices-product-backlog.md
Product: devops
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@jessehouwing  - Thank you for your feedback. Agreed. Will update the article.


Error on compiling: package org.nativescript.splashScreen does not exist

I've created my android project with NativeScript and I use splashscreen
I work on Windows 10 64bit
NativeScript 2.1.1
And I config splash screen like this instruction:
https://fitcom.co/2016/04/26/nativescript-splashscreen-hack/
but the error has occorred like this.
Have you guys a good solution to fix this error please?
D:\playground\nativescript\rodtu-alpha\platforms\android\src\main\java\com\tns\SplashScreen.java:8: error: package org.nativescript.splashScreen does not exist
import org.nativescript.splashScreen.R;
                                    ^
D:\playground\nativescript\rodtu-alpha\platforms\android\src\main\java\com\tns\SplashScreen.java:18: error: package R does not exist
           configSplash.setBackgroundColor(R.color.material_grey_900); //any color you want form colors.xml
                                            ^
D:\playground\nativescript\rodtu-alpha\platforms\android\src\main\java\com\tns\SplashScreen.java:27: error: package R does not exist
           configSplash.setLogoSplash(R.drawable.ns_logo); //or any other drawable
                                       ^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
3 errors
:compileF0F1DebugJavaWithJavac FAILED

The blog post is slightly outdated vs using the plugin follow the instructions in readme in the repo

Try this.It should work.
tns platform remove ios;
tns platform add ios;
tns run ios --emulator;

@leocaseiro they are using android also it is some old code i did a couple months back before creating this plugin


Issue With Password Input in case of Autofill

Bug, feature request, or proposal:
When using material input for password fields and user has enabled browser autofill for that website, the password field with auto-filled value doesn't appear properly i.e. the placeholder text which is suppose to float above the password field is actually shown over the filed value i.e. ******.
When user click anywhere on page the placeholder text floats on top and password field becomes normal so apparently some change detection issue.
What is the expected behavior?
The placeholder text for password fields should float even if the value of the field comes from browser autofill.

Duplicate #6837