oclint - How can I define FL_OCLINT_EXCLUDE_REGEX value in a .env file

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
How can I define FL_OCLINT_EXCLUDE_REGEX value in a .env file? If try to use FL_OCLINT_EXCLUDE_REGEX=/src/ then I get type mismatch: String given.
Complete output when running fastlane, including the stack trace and command used
DEBUG [2017-08-23 09:00:27.49]: Checking if there are any plugins that should be loaded...
INFO [2017-08-23 09:00:27.60]: gem 'spaceship' is already installed
INFO [2017-08-23 09:00:27.61]: -------------------------------------------------
INFO [2017-08-23 09:00:27.61]: --- Step: Verifying required fastlane version ---
INFO [2017-08-23 09:00:27.61]: -------------------------------------------------
INFO [2017-08-23 09:00:27.61]: Your fastlane version 2.54.0 matches the minimum requirement of 2.50.0  ✅
INFO [2017-08-23 09:00:27.61]: ------------------------------
INFO [2017-08-23 09:00:27.61]: --- Step: default_platform ---
INFO [2017-08-23 09:00:27.61]: ------------------------------
INFO [2017-08-23 09:00:27.62]: Driving the lane 'ios run_analyzer' 🚀
INFO [2017-08-23 09:00:27.62]: Lane run_analyzer started.
INFO [2017-08-23 09:00:27.62]: --------------------
INFO [2017-08-23 09:00:27.62]: --- Step: oclint ---
INFO [2017-08-23 09:00:27.62]: --------------------
DEBUG [2017-08-23 09:00:27.62]: Taking value for 'compile_commands' from environment variable 'FL_OCLINT_COMPILE_COMMANDS'
DEBUG [2017-08-23 09:00:27.62]: Taking value for 'compile_commands' from environment variable 'FL_OCLINT_COMPILE_COMMANDS'
DEBUG [2017-08-23 09:00:27.62]: Taking value for 'select_regex' from environment variable 'FL_OCLINT_SELECT_REGEX'
DEBUG [2017-08-23 09:00:27.62]: Taking value for 'select_regex' from environment variable 'FL_OCLINT_SELECT_REGEX'
DEBUG [2017-08-23 09:00:27.62]: Taking value for 'exclude_regex' from environment variable 'FL_OCLINT_EXCLUDE_REGEX'
INFO [2017-08-23 09:00:33.95]: Lane run_analyzer failed to complete.
WARN [2017-08-23 09:00:33.95]: Lane Context:
INFO [2017-08-23 09:00:33.95]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios run_analyzer"}
ERROR [2017-08-23 09:00:33.95]: type mismatch: String given
INFO [2017-08-23 09:00:33.96]: Successfully generated documentation at path '/Users/user/projects/ios/project/MyProject/fastlane/README.md'

+------+------------------------------+-------------+
|                 fastlane summary                  |
+------+------------------------------+-------------+
| Step | Action                       | Time (in s) |
+------+------------------------------+-------------+
| 1    | Verifying required fastlane  | 0           |
|      | version                      |             |
| 2    | default_platform             | 0           |
| 💥   | oclint                       | 0           |
+------+------------------------------+-------------+

ERROR [2017-08-23 09:00:33.96]: fastlane finished with errors

Looking for related GitHub issues on fastlane/fastlane...
Search query: type mismatch: String given

URL: https://api.github.com/search/issues?q=type%20mismatch:%20String%20given+repo:fastlane/fastlane
➡  oclint - How can I define `FL_OCLINT_SELECT_REGEX` value in a `.env` file
    https://github.com/fastlane/fastlane/issues/10069 [closed] 6 💬
    6 hours ago

🔗  You can ⌘ + double-click on links to open them directly in your browser.
bundler: failed to load command: fastlane (/Users/user/.gem/bin/fastlane)
TypeError: [!] type mismatch: String given
  /Users/user/3party/fastlane/fastlane/lib/fastlane/actions/oclint.rb:48:in `=~'
  /Users/user/3party/fastlane/fastlane/lib/fastlane/actions/oclint.rb:48:in `!~'
  /Users/user/3party/fastlane/fastlane/lib/fastlane/actions/oclint.rb:48:in `block in run'
  /Users/user/3party/fastlane/fastlane/lib/fastlane/actions/oclint.rb:44:in `select!'
  /Users/user/3party/fastlane/fastlane/lib/fastlane/actions/oclint.rb:44:in `run'
  /Users/user/3party/fastlane/fastlane/lib/fastlane/runner.rb:252:in `block (2 levels) in execute_action'
  /Users/user/3party/fastlane/fastlane/lib/fastlane/actions/actions_helper.rb:50:in `execute_action'
  /Users/user/3party/fastlane/fastlane/lib/fastlane/runner.rb:230:in `block in execute_action'
  /Users/user/3party/fastlane/fastlane/lib/fastlane/runner.rb:226:in `chdir'
  /Users/user/3party/fastlane/fastlane/lib/fastlane/runner.rb:226:in `execute_action'
  /Users/user/3party/fastlane/fastlane/lib/fastlane/runner.rb:148:in `trigger_action_by_name'
  /Users/user/3party/fastlane/fastlane/lib/fastlane/fast_file.rb:146:in `method_missing'
  Fastfile:140:in `block (2 levels) in parsing_binding'
  /Users/user/3party/fastlane/fastlane/lib/fastlane/lane.rb:33:in `call'
  /Users/user/3party/fastlane/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
  /Users/user/3party/fastlane/fastlane/lib/fastlane/runner.rb:45:in `chdir'
  /Users/user/3party/fastlane/fastlane/lib/fastlane/runner.rb:45:in `execute'
  /Users/user/3party/fastlane/fastlane/lib/fastlane/lane_manager.rb:52:in `cruise_lane'
  /Users/user/3party/fastlane/fastlane/lib/fastlane/command_line_handler.rb:30:in `handle'
  /Users/user/3party/fastlane/fastlane/lib/fastlane/commands_generator.rb:104:in `block (2 levels) in run'
  /Users/user/.gem/gems/commander-fastlane-4.4.5/lib/commander/command.rb:178:in `call'
  /Users/user/.gem/gems/commander-fastlane-4.4.5/lib/commander/command.rb:153:in `run'
  /Users/user/.gem/gems/commander-fastlane-4.4.5/lib/commander/runner.rb:476:in `run_active_command'
  /Users/user/3party/fastlane/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:64:in `run!'
  /Users/user/.gem/gems/commander-fastlane-4.4.5/lib/commander/delegates.rb:15:in `run!'
  /Users/user/3party/fastlane/fastlane/lib/fastlane/commands_generator.rb:303:in `run'
  /Users/user/3party/fastlane/fastlane/lib/fastlane/commands_generator.rb:42:in `start'
  /Users/user/3party/fastlane/fastlane/lib/fastlane/cli_tools_distributor.rb:66:in `take_off'
  /Users/user/3party/fastlane/bin/fastlane:20:in `<top (required)>'
  /Users/user/.gem/bin/fastlane:23:in `load'
  /Users/user/.gem/bin/fastlane:23:in `<top (required)>'

Fixed with ba9ce3734ab106773c8d817dca38b9d207eafbe3

Fixed with ba9ce3734ab106773c8d817dca38b9d207eafbe3.


Add PolygonAssociatedAddress and FantomAssociatedAddress

same principle as EthereumAssociatedAddress
see Design of the card in Figma
https://github.com/TalaoDAO/wallet-tools/blob/main/test/CredentialOffer2/FantomAssociatedAddress.jsonld
https://github.com/TalaoDAO/wallet-tools/blob/main/test/CredentialOffer2/PolygonAssociatedAddress.jsonld
updatre create account and update  account to intagrate those new credntials

Size: L


Add the ability to synchronous destructors

This is different from using finally, since promise chains will generally resolve in the next tick. Imagine for example that we want to clean up an event listener, then it would be very unfortunate if an event occurs in-between the fork finalizing and the finally hook being run.

A preview package of this pull request has been released to NPM with the tag at-exit.
You can try it out by running the following command:
$ npm install effection@at-exit

or by updating your package.json to:
{
  "effection": "at-exit"
}

Once the branch associated with this tag is deleted (usually once the PR is merged or closed), it will no longer be available. However, it currently references<EMAIL_ADDRESS>which will be available to install forever.

  Generated by :no_entry_sign: dangerJS against 8c15e6800b952c0992b04cc4dea1998f32d9a28c

Pulled this out from #49, since this is really an isolated change. I think even with the changes we've talked about re fork/join we will need to have something like this.

A preview package of this pull request has been released to NPM with the tag at-exit.
You can try it out by running the following command:
$ npm install effection@at-exit

or by updating your package.json to:
{
  "effection": "at-exit"
}

Once the branch associated with this tag is deleted (usually once the PR is merged or closed), it will no longer be available. However, it currently references<EMAIL_ADDRESS>which will be available to install forever.

  Generated by :no_entry_sign: dangerJS against 5831372d584aa66b91018620679db9b69e33e13f

A preview package of this pull request has been released to NPM with the tag at-exit.
You can try it out by running the following command:
$ npm install effection@at-exit

or by updating your package.json to:
{
  "effection": "at-exit"
}

Once the branch associated with this tag is deleted (usually once the PR is merged or closed), it will no longer be available. However, it currently references<EMAIL_ADDRESS>which will be available to install forever.

  Generated by :no_entry_sign: dangerJS against 4e9faca8193a9a782347060717a709d8606dd84e


[PostgreSQL] Missing ; in DROP TABLE comment

In the DDL tab:
-- DROP TABLE my_table

Should be:
-- DROP TABLE my_table;

Maybe present in other object type.

Thanks!


Maintainer

Not sure who I need to get in touch with, but I have some free time and would like to start helping out as best I can with maintaining this, if that help is still needed.

Can you send me an email? Thanks!


Addition to "Other Resources"

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you for your contribution.  At this time we have decided not to merge your pull request.  We welcome future pull requests from you.
Reason:

We won't accept a PR that only adds links to the More Information or References section.

Please reference how to work on guide articles when submitting new PRs for guide updates.
Happy Coding!


Error: Getting current working directory failed, path = '' (OS Error: Interrupted system call, errno = 4)

Steps to Reproduce

upgraded to MacOS Big Sur:
System Version: macOS 11.0.1 (20B29)
Kernel Version: Darwin 20.1.0
running any unit test that flutter project already had before updating laptop OS version

did try to clean flutter pub cache with flutter pub cache repair, and also by deleting said cache folder from laptop and then running flutter pub get again on project and running tests.... still failed
Expected results:
unit test to run successfully at all times
(In Catalina OS version, same test(s) run without fail)
Actual results:
at random runs the test fails
Verbose Log
[  +28 ms] test 0: awaiting initial result for pid 20741
00:04 +0: loading /Users/me/dev-env/app/packages/collector/test/collector_test.dart                [ +810 ms] test 0: process with pid 20741 connected to test harness
[   +1 ms] test 0: awaiting test result for pid 20741
00:04 +0 -1: loading /Users/me/dev-env/app/packages/collector/test/collector_test.dart [E]
  Failed to load "/Users/me/dev-env/app/packages/collector/test/collector_test.dart": Getting current working directory failed, path = '' (OS Error: Interrupted system call, errno = 4)
  dart:io-patch/directory_patch.dart 64:5                                                                                _uriBaseClosure
  dart:core-patch/uri_patch.dart 21:41                                                                                Uri.base
  package:path/src/style.dart 42:14                                                                                Style._getPlatformStyle
  package:path/src/style.dart 33:33                                                                                Style.platform
  package:path/src/style.dart                                                                                Style.platform
  package:flutter_test/src/_goldens_io.dart 71:52                                                                         LocalFileComparator._getPath
  package:flutter_test/src/_goldens_io.dart 75:34                                                                         LocalFileComparator._getBasedir
  package:flutter_test/src/_goldens_io.dart 67:17                                                                         new LocalFileComparator
  /var/folders/rz/dt7c_sjs3hv2hk3pxz9qf2f80000gn/T/flutter_tools.xUGs3h/flutter_test_listener.9FVTCU/listener.dart 42:24  main.<fn>
  package:test_api/src/remote_listener.dart 68:27                                                                         RemoteListener.start.<fn>.<fn>.<fn>
  package:test_api/src/remote_listener.dart 65:25                                                                         RemoteListener.start.<fn>.<fn>.<fn>
  dart:async/zone.dart 1186:13                                                                                _rootRun
  dart:async/zone.dart 1090:19                                                                                _CustomZone.run
  dart:async/zone.dart 1626:10                                                                                _runZoned
  dart:async/zone.dart 1614:12                                                                                runZonedGuarded
  package:test_api/src/remote_listener.dart 65:9                                                                          RemoteListener.start.<fn>.<fn>
  dart:async/zone.dart 1186:13                                                                                _rootRun
  dart:async/zone.dart 1090:19                                                                                _CustomZone.run
  dart:async/zone.dart 1626:10                                                                                _runZoned
  dart:async/zone.dart 1546:10                                                                                runZoned
  package:test_api/src/backend/stack_trace_formatter.dart 42:7                                                            StackTraceFormatter.asCurrent
  package:test_api/src/remote_listener.dart 64:29                                                                         RemoteListener.start.<fn>
  dart:async/zone.dart 1186:13                                                                                _rootRun
  dart:async/zone.dart 1090:19                                                                                _CustomZone.run
  dart:async/zone.dart 1626:10                                                                                _runZoned
  dart:async/zone.dart 1546:10                                                                                runZoned
  package:test_api/src/suite_channel_manager.dart 35:7                                                                    SuiteChannelManager.asCurrent
  package:test_api/src/remote_listener.dart 63:27                                                                         RemoteListener.start
  /var/folders/rz/dt7c_sjs3hv2hk3pxz9qf2f80000gn/T/flutter_tools.xUGs3h/flutter_test_listener.9FVTCU/listener.dart 15:25  serializeSuite
  /var/folders/rz/dt7c_sjs3hv2hk3pxz9qf2f80000gn/T/flutter_tools.xUGs3h/flutter_test_listener.9FVTCU/listener.dart 40:36  main
  dart:ui/hooks.dart 136:25                                                                                _runMainZoned.<fn>.<fn>
  dart:async/zone.dart 1186:13                                                                                _rootRun
  dart:async/zone.dart 1090:19                                                                                _CustomZone.run
  dart:async/zone.dart 1626:10                                                                                _runZoned
  dart:async/zone.dart 1614:12                                                                                runZonedGuarded
  dart:ui/hooks.dart 132:5                                                                                _runMainZoned.<fn>
  dart:isolate-patch/isolate_patch.dart 283:19                                                                            _delayEntrypointInvocation.<fn>
  dart:isolate-patch/isolate_patch.dart 184:12                                                                            _RawReceivePortImpl._handleMessage

 Run `flutter analyze`

no issues
  Run `flutter doctor -v`

[✓] Flutter (Channel stable, 1.22.4, on macOS 11.0.1 20B29 darwin-x64, locale en-FI)
• Flutter version 1.22.4 at /Users/me/dev-env/flutter
• Framework revision 1aafb3a8b9 (7 days ago), 2020-11-13 09:59:28 -0800
• Engine revision 2c956a31c0
• Dart version 2.10.4
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at /Users/me/Library/Android/sdk
• Platform android-30, build-tools 29.0.2
• ANDROID_HOME = /Users/me/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
• 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.8.4
[✓] Android Studio (version 3.5)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 43.0.1
• Dart plugin version 191.8593
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
[✓] VS Code (version 1.51.1)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.16.0
[!] Connected device
! No devices available
! Doctor found issues in 1 category.

+1

Experiencing the same issue.
Л flutter doctor -v
[✓] Flutter (Channel stable, 1.22.4, on macOS 11.0.1 20B29 darwin-x64, locale
    en-GB)
    • Flutter version 1.22.4 at /Users/adam/Development/flutter
    • Framework revision 1aafb3a8b9 (10 days ago), 2020-11-13 09:59:28 -0800
    • Engine revision 2c956a31c0
    • Dart version 2.10.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/adam/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Users/adam/Library/Application
      Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.6953283/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)
    • 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.9.3

[!] Android Studio (version 4.1)
    • Android Studio at /Users/adam/Library/Application
      Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.6953283/Android
      Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.49.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.12.2

[!] Connected device
    ! No devices available

! Doctor found issues in 2 categories.

@jonahwilliams any ideas on what is causing this? or even when there might be a fix?

https://github.com/dart-lang/sdk/issues/44214
different error code / number, but coming from same class / line number.

\cc @devoncarew another current working directory failed issue.  Should these cases be moved to dart-lang/sdk for investigation?

The fix for that sdk issue landed (https://github.com/dart-lang/sdk/commit/ce272daae8a881a5199fc749a4643d36b4fa6fc4), but w/o digging into it I would guess that that specific problem only existing on dev releases of the sdk and not for flutter stable.

I was using 1.22.4 stable flutter and error persisted with unit tests
Had to actually downgrade back to Catalina to resume working environment, so any updates on this issue would be much appriciated

I also run into this issue when running tests with Flutter 1.22.4, but I'm still on macOS Catalina..
So what's the real issue here?

Same error for me on Big Sur
flutter doctor -v
[✓] Flutter (Channel stable, 1.22.4, on macOS 11.0.1 20B29 darwin-x64, locale it-IT)
• Flutter version 1.22.4 at /Users/danilo/DevEnvironments/flutter
• Framework revision 1aafb3a8b9 (3 weeks ago), 2020-11-13 09:59:28 -0800
• Engine revision 2c956a31c0
• Dart version 2.10.4
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at /Users/danilo/Library/Android/sdk
• Platform android-29, build-tools 29.0.2
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
• 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
[✓] Android Studio (version 4.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin installed
• Dart plugin version 201.9245
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
[✓] VS Code (version 1.48.1)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.13.2
[!] Connected device
! No devices available
! Doctor found issues in 1 category.

Am having the same on Big Sur with Flutter stable.Spend quite sometime playing with different parameters. I found out that if I run flutter test --no-test-assets it has a higher chance of passing (around 1/3 passes now). However this is not a sustainable solution. Really hope this gets fixed soon.

The fix for that sdk issue landed (dart-lang/sdk@ce272da), but w/o digging into it I would guess that that specific problem only existing on dev releases of the sdk and not for flutter stable.

@devoncarew This is reported on 1.22.4 stable.  Can we move this to dart for investigation?

@jmagman I'm really not the right person to dig into this. Perhaps @a-siva, as this might be a dart:io issue on Bug Sur?

Sorry @devoncarew, I totally missed that your comment was replying to a comment about a different issue.

Hi! Was solving this moved somewhere else or is someone still looking into this issue?
any link to dart:io issue if this is being fixed in that project?

Big Sur, has new APIs that prevent Little Snitch from working the same way. The new APIs don’t permit Little Snitch to inspect or block any OS level processes. Additionally, the new rules in macOS 11 even hobble VPNs so that Apple apps will simply bypass them.

https://sneak.berlin/20201112/your-computer-isnt-yours/
any ideas if that "new APIs don’t permit.... inspect or block any OS level processes" is the cause here? is that just some tin foil hat stuff?

I just ran flutter test 20 times on Big Sur machine and it passed every time.  This was a new machine and not migrated from Catalina (it's an M1).
I filed https://github.com/dart-lang/sdk/issues/44509 so the dart team can take a look.

Closed?

I faced the same issue, when I migrated to Big Sur. Now I have Big Sur 11.2, but the issue with tests running is still reproducible.
I managed to find temporary workaround for it: to run command with concurrency parameter set to 1 (by default it is 10):
flutter test --concurrency 1

In 95% of runs, error does not appear, but in rest 10% - it does.
I suppose, error is somehow related to filesystem access or some access race condition. And I do not rely on my temporary solution, because it decrease running time (because only 1 job is used).
I believe the issue will be investigated and fixed asap.

@ihorvitruk Can you update https://github.com/dart-lang/sdk/issues/44509 with your findings so the dart team can see it?

I am facing this issue randomly in mac os big sur

Is the only way to reproduce this problem is running an existing flutter project unit test after upgrading to Mac OS Big Sur ?

I can reproduce this almost every time with Anti-Virus enabled. Disable it and everything works.

See this

with latest release of 11.3 macOS version, issue seems to have been fixed.
Might also be that Microsoft silently fixed something in MS ATP
Anyways, works for me. No OS Error anymore in test runs.


PowerToys Awake standalone Tray Icon reports incorrrect time

Microsoft PowerToys version
0.84.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
Awake
Steps to reproduce

Validate that Awake is turned off in the PowerToys settings.
Open a terminal and navigate to the PowerToys install directory.
Input the following command:
.\PowerToys.Awake.exe --display-on true --time-limit 1800

✔ Expected Behavior
I expect this to only keep the display and computer awake for 30 minutes. The tray icon should also reflect this when hovered.
This was the behavior prior to updating to v0.84.0.
❌ Actual Behavior
The tray icon for awake now says "[Indefinite]" when hovering over it.
However, it does appear to terminate after the specified time. So this is seemingly just a bug with the tray icon display logic.

Other Software
No response

I'm experiencing the same issue.

I'm starting to believe that this isn't just an issue with the tray display. I've seen the icon well after the specified duration and my screen has remained on. It seems inconsistent, but I'm happy to run through any troubleshooting steps if needed.

Can reproduce this - thanks for the feedback. Investigating.

Found the issue. Should be covered in #34717. The app wrongly initialized with --use-parent-pid.

Closing this because this is covered by #34148 as the icon behaviors are not expected.


Minor Touch-ups + consistent naming

Can you please hold off the name of type changes like name of PreloginHandler casing. I want to get the login handler and dealing with merge conflicts is for these name changes can be avoided till some more code goes in.
I am ok with comment changes and removal of async keyword

Can you please hold off the name of type changes like name of PreloginHandler casing. I want to get the login handler and dealing with merge conflicts is for these name changes can be avoided till some more code goes in. I am ok with comment changes and removal of async keyword

Sure, I can park it for later

@cheenamalhotra  according to https://learn.microsoft.com/en-us/openspecs/sql_server_protocols/ms-sstds/75e62f67-f057-4d46-82b3-6920fe0ebada prelogin is a keyword. So it should continue to be Prelogin instead of PreLogin

It looks like we have some PreLogin terms in use as well.. I'm fine with either way, as long as it's consistent and Visual Studio can accept the spelling :P


test add test simplify comparison predicate

What problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Add test simplify comparison predicate
Release note
None
Check List (For Author)

Test

[x] Regression test
[ ] Unit Test
[ ] Manual test (add detailed scripts or steps below)
[ ] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[ ] Previous test can cover this change.
[ ] No code files have been changed.
[ ] Other reason

Behavior changed:

[ ] No.
[ ] Yes.

Does this need documentation?

[ ] No.
[ ] Yes.

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

when comparison with date like type still has bug,  need fix them first

run buildall

run buildall


eval() vs freeze_model(True)

Environment info

adapter-transformers version: 3.0.0
Platform: ubuntu 20.04
Python version: 3.7
PyTorch version (GPU?): 1.11.0+cu113

Description
I tried to perform evaluation on dev set after training of each epoch. Before training, I set
optimizer.zero_grad(), model.train_adapter(adapter_i) and model.set_active_adapters(adapter_i),
and switch to eval mode after training (before evaluation on dev set):
model.freeze_model(True) and model.set_active_adapters(adapter_i).
I found that if I change model.freeze_model(True) to model.eval(), the result will be very different after the complete training process. I am aware that model.eval() will leave parameters of adapters as requires_grad=True. But I set optimizer.zero_grad() before training every time, based on my understanding, these two commands (model.freeze_model(True) or model.eval()) should not cause different gradient computations during training of next epoch. Therefore I am confused why these two commands (set during evaluation on dev set) cause different results?

Hey,
the command model.freeze_model(True) does freeze the weights of the model. Hence, the weights are not adapted during training. But for evaluation where you don't update the parameters, this does not make a difference. The model.eval() command deactivates the Dropout modules of the model, such that a forwardpass of one input always produces the same output. Since the Dropout randomly drops some of the nodes this is not the case for models with active Dropout.  This explains the different results: model.eval() deactivates Dropout, while model.freeze_model(True) does not.
I hope this clarifies things.

@hSterz Thanks!


Resetting Project Data doesn't Remove Session Report Data

I wanted to clear all my previous log data from testing so I had fresh interface for testing more features – so I assumed Settings > Project > Reset Project Data > and click the big red button would do this?
This successfully cleared everything in Exceptions, Log Messages, Features etc
But still showing all my previous session information under Reports > Sessions
It seemed to clear the old content when I then next sent a exception as only 1 item appeared in list
BUT if you then do Reset Project Data again ALL the previous data comes back to Report > Sessions !!!

Thanks for reporting this issue, I've been able to verify it as well and we'll get this fixed shortly.

Related issue
After doing Settings > Project > Reset Project Data  for a project - you can still see a count of stacks / events in My Projects - but if you have "reset project data" then I assume this should now show 0 / 0

Thanks for letting us know about this. I was able to reproduce in a test. We also committed a fix last night but haven't deployed it for this issue.

This has been fixed and deployed


New rule proposal: unnecessary-newline-at-start-of-file

Hi,
I think it could be interesting for ruff to also check for unnecessary newlines at the start of files, a parallel (sort of) to to W292 https://docs.astral.sh/ruff/rules/missing-newline-at-end-of-file/
The idea being, ruff would prevent a file to start with a new line. Currently, ruff is perfectly fine with it.
For example, this works even with all rules selected:

from marshaling import AppSettings

class Settings(AppSettings):
    CI_VERSION: str
    ENVIRONMENT_NAME: str
    SYSTEM_JWT_KEY: str

settings = Settings()

Thanks for the suggestion. Have you considered using ruff format? It removes the line automatically for you (and inserts the trailing new line)

So, I recon it's bordeline, but also use ruff to check on files types (like behave files) that don't quite work ruff format unfortunately

I'm sorry but I don't follow what you're trying to say here. Can you expand on what do you mean by "don't quite work ruff format"? Are you using any other filetypes which contains Python source code?

I'm going to close this for now as we're trying to be very conservative in adding new formatting-only lint rules now that we have ruff format, since maintaining compatibility between ruff format and style rules is tricky.


No activity, no DFU mode

Hi,
Thank you for this project! I followed your directions and got my package of 5 quickly from JLCPCB.
However, it's not entering DFU mode.  Any troubleshooting I can do? Measure voltage(s) somewhere on the board?   Same results with all of them...
$ dfu-util -a 0 -s 0x08000000 -D aioc-fw-1.2.0.bin
dfu-util 0.11

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Match vendor ID from file: 1209
Match product ID from file: 7388
dfu-util: No DFU capable USB device available

@klinquist Do you have any of those extra boards ? Can you spare one?

That's the wrong pins that are shorted. Needs to be the outer most pins. See the silkscreen on the back.
Also, you should try adding sudo before the dfu command.

ah-ha!  Thank you @skuep , got all 4 flashed - now waiting for the 3.5mm and 2.5mm jacks to be delivered from Adafruit.
@desaiamogh Not currently, but I just followed skuep's directions and had 5 of them in my hand in about 5 days for $65 USD!

Nice! 😎 Thanks a bunch for the pull request. Much appreciated!
PS: of you order ten of them, they are even cheaper per piece 😁


Roundtripping in pipelines

I was thinking about what happens when one uses a pipeline with input format text/html and output format text/html.
I think when the pipeline internally uses other input / output formats (e.g. turtle) then it will fail in the last step because the last step has informat=turtle, outformat=text/html which is not supported.
It should work when every single pipeline step has informat=outformat=text/html . But this means conversion in every single pipeline step which has a bad performance.
e-Internationalization generates during conversion from original format to NIF an additional NIF document that stores the original input document in turtle. This file needs to be kept during the pipeline execution. At the end of the pipeline, the enrichment information is merged with the original input document in turtle to perform the conversion back to the original format.
@ghsnd do you have a solution on how to store the input document in turtle?

I think this is indeed a good idea to improve performance. So to summarize: if the input/output format is text/html, then the pipeline service should:

Convert to NIF, and keep the additional original input doc;
Perform the steps in the pipeline using NIF, "overriding" the original specified input/output parameters in each step;
Take the ouput of the last step (NIF) and convert it to HTML using the stored original input doc.

Can e-Internationalization be used out of the box to perform the conversions and get the original input doc in NIF?

@ghsnd do you have a solution on how to store the input document in turtle?

I think it is not that hard to store the input document, be it in a temporary file or using hibernate...

I have a first implementation ready, merged to the main branch.
Right now the skeleton file is kept in memory until the pipeline is completed (which works fine). Depending on the input it can grow rather large, but I can write it to a temporary file in stead and / or apply compression.


Test type isn't updating

Description
I am using     "cypress-xray-plugin": "7.1.0",       "cypress": "^13.15.2",
and i have added
        jira: {
         fields: {
           labels: config.env.JIRA_FIELDS_LABELS,
           testType: config.env.JIRA_FIELDS_TEST_TYPE,
         },
         projectKey: config.env.JIRA_PROJECT_KEY,
         url: config.env.JIRA_URL,
       },

in my cypress config
and also added  JIRA_FIELDS_LABELS, and JIRA_FIELDS_TEST_TYPE in env
but it is not updating the test type or adding labels to the test
(the test Is precreated and I am tagging the issue key in bdd scenario in .feature files)
it is creating testexecutions and linking to the precerated tests but not updating the test type
Cypress version
13.15.2
Plugin version
7.1.0
Jira/Xray type
Cloud
Configuration
import { defineConfig } from 'cypress';
import createBundler from '@bahmutov/cypress-esbuild-preprocessor';
import { addCucumberPreprocessorPlugin } from '@badeball/cypress-cucumber-preprocessor';
const createEsbuildPlugin =
  require('@badeball/cypress-cucumber-preprocessor/esbuild').createEsbuildPlugin;
import { configureXrayPlugin, syncFeatureFile } from 'cypress-xray-plugin';
import fix from 'cypress-on-fix';

export default defineConfig({
  e2e: {
    async setupNodeEvents(on, config) {
      const fixedOn = fix(on);
      await addCucumberPreprocessorPlugin(fixedOn, config);
      await configureXrayPlugin(fixedOn, config, {
        cucumber: {
          featureFileExtension: '.feature',
          downloadFeatures: true,
        },
        jira: {
          fields: {
            labels: config.env.JIRA_FIELDS_LABELS,
            testType: config.env.JIRA_FIELDS_TEST_TYPE,
          },
          projectKey: config.env.JIRA_PROJECT_KEY,
          url: config.env.JIRA_URL,
        },
      });
      fixedOn('file:preprocessor', async (file) => {
        await syncFeatureFile(file);
        const cucumberPlugin = createBundler({
          plugins: [createEsbuildPlugin(config)],
        });
        return cucumberPlugin(file);
      });
      return config;
    },
    specPattern: 'e2e/**/*.feature',
    supportFile: 'support/e2e.ts',
    env: {
      tags: '@automated',
      localePath: '../packages/common/contexts/localization/locales/en.json',
    },
  },
  chromeWebSecurity: false,
});

Acknowledgements

[X] I have made sure not to include any sensitive data in screenshots or obfuscated all occurrences.
[X] I have made sure not to include any sensitive data in descriptions or replaced all values with placeholders.
[X] I have made sure not to include any sensitive data in code snippets or replaced all values with placeholders.

Hey @PranavHiraniAI,
thanks for the issue. I'm not yet entirely sure what you're trying to do, so here are two suggestions.

If you want to configure test execution data such as labels, you'll need to use the testExecutionIssue setting:
      await configureXrayPlugin(fixedOn, config, {
        // ...
        jira: {
          testExecutionIssue: {
            fields: {
              labels: config.env.JIRA_FIELDS_LABELS // must be an array of strings
            }
          },
        // ...
        },
      });

These will then be added to the test execution issue.
You can customize any field there that is present in your test execution issues (assignee, ...).

If you want to add labels to your test issues, you'll need to stick to Xray's Cucumber documentation and add them to your scenarios inside the feature files. Xray will then add them to your test issues on feature file import (i.e. syncFeatureFile).
The plugin does not add them to your tests automatically, neither does it update the test type. You will need to change the test type in Xray on your own.

I see.

If not labeled it is fine

The example tagged @automated you've provided should be labelled on feature file upload according to Xray: The tags used in the scenario/scenario outline are also added as labels.
If this is not the case you might want to file a bug with Xray :thinking: Unless it's because you're importing test results of type Cucumber to tests that are not of type Cucumber. That might also be an issue.

so the Test Type of test issues related to that scenarios should be updated to Automated

To be honest, allowing the plugin to change test types would open a huge can of worms:

The plugin currently does not modify test issues. It only modifies or creates test execution issues. It was able to create and update test issues in the past, but that lead to a lot of confusion, complicated configurations and other issues, e.g.:

#83
#84
#100

The configurability would be complicated, as it would need to support different test types for Cypress and/or Cucumber tests.
Changing test types can be an extremely destructive action if the test type provided in the plugin is not of the same category like the ones currently configured, deleting all steps/test definitions. Not a good idea from a perspective of the principle of least surprise.

In my opinion it's too difficult for me to provide a one-fits-all solution that will make all users happy. Therefore, I suggest you implement your use case "manually" with a custom hook:
export default defineConfig({
  e2e: {
    async setupNodeEvents(on, config) {
      const fixedOn = fix(on);
      await addCucumberPreprocessorPlugin(fixedOn, config);
      // New hook:
      // 1. Identify all tests we want to update
      // 2. Update all test types using the Xray API
      fixedOn("after:run", async (results) => {
          if ("status" in results) {
            // Return early if Cypress failed to run.
            return;
          }
          // Identify all relevant test issues whose test types we want to update.
          const issueKeys = new Set<string>();
          const projectKey = "CYP";
          // Matches as follows:
          // "CYP-123 CYP-456 hello test"
          // [ "CYP-123", "CYP-456" ]
          const titleRegex = new RegExp(`(${projectKey}-\\d+)`, "g");
          for (const run of results.runs) {
            for (const test of run.tests) {
              if (shouldUpdateTestType(run, test)) {
                const testKeys = test.title.join(" ").match(titleRegex);
                if (testKeys) {
                  testKeys.forEach((key) => issueKeys.add(key));
                }
              }
            }
          }
          await updateTestTypes("Automated", ...issueKeys);
        }
      );
      // Make sure to add the plugin afterwards such that the plugin's hooks run after
      // the one that updates the test types.
      await configureXrayPlugin(fixedOn, config, { /* ... */ });
      fixedOn('file:preprocessor', async (file) => { /* ... */ });
      return config;
    },
    specPattern: 'e2e/**/*.feature',
    supportFile: 'support/e2e.ts',
    env: {
      tags: '@automated',
      localePath: '../packages/common/contexts/localization/locales/en.json',
    },
  },
  chromeWebSecurity: false,
});

/**
 * Returns whether the specified test should be included in the tests to update.
 *
 * @param run the Cypress run
 * @param test the test included in the Cypress run
 * @returns `true` if it should be updated, `false` otherwise
 */
function shouldUpdateTestType(run: CypressCommandLine.RunResult, test: CypressCommandLine.TestResult) {
  const projectKey = "CYP";
  // Custom logic, e.g. only update test types of tests in normal Cypress specs:
  return run.spec.fileExtension.endsWith(".js") && test.title.join(" ").includes(projectKey);
}

/**
 * Sets the test type of all provided issues to the specified one if needed.
 *
 * @param testType the target test type
 * @param issueKeys the issues whose test type should be updated
 */
async function updateTestTypes(testType: string, ...issueKeys: string[]) {
  // 1. Authenticate to Xray Cloud API
  //    - https://docs.getxray.app/display/XRAYCLOUD/Authentication+-+REST+v2
  // 2. Update test type for each identified test issue
  //    - https://us.xray.cloud.getxray.app/doc/graphql/updatetesttype.doc.html
  const authenticationResponse = await fetch("https://xray.cloud.getxray.app/api/v2/authenticate", {
    method: "POST",
    headers: { ["content-type"]: "application/json" },
    body: JSON.stringify({
      client_id: ...,
      client_secret: ...,
    }),
  });
  const token = await authenticationResponse.json();
  const issues = await getTestIssues(token, ...issueKeys);
  for (const issue of issues) {
    // Skip tests whose test type has been updated already.
    if (issue.testType.name === testType) {
      continue;
    }
    const response = await fetch("https://xray.cloud.getxray.app/api/v2/graphql", {
      method: "POST",
      headers: { authorization: `Bearer ${token}`, ["content-type"]: "application/json" },
      body: JSON.stringify({
        query: `
          mutation {
            updateTestType(issueId: "${issue.issueId}", testType: { name: "${testType}" }) {
              testType {
                name
              }
              jira (fields: ["key"])
            }
          }
        `,
        variables: {},
      }),
    });
    // The response will looke like this:
    // {
    //   data: {
    //     updateTestType: {
    //       testType: { name: "Automated Steps" },
    //       jira: { key: "CYP-1139" },
    //     },
    //   },
    // };
    const json = await response.json();
    console.log(`Updated test type: ${json.data.updateTestType.jira.key} - ${json.data.updateTestType.testType.name}`);
  }
}

/**
 * Returns test issue data for the specified issue keys.
 *
 * @param issueKeys the issue keys
 * @returns the corresponding issue issue data
 */
async function getTestIssues(token: string, ...issueKeys: string[]) {
  const issues: { issueId: string; testType: { name: string } }[] = [];
  // GraphQL limit ist 100 by default.
  const limit = 100;
  for (let i = 0; i < issueKeys.length; i += limit) {
    const jql = `issue in (${issueKeys.slice(i, i + limit).join(",")})`;
    const query = `
      {
        getTests(limit: ${limit}, jql: "${jql}") {
          results {
            issueId
            testType {
              name
            }
          }
        }
      }
    `;
    const response = await fetch("https://xray.cloud.getxray.app/api/v2/graphql", {
      method: "POST",
      headers: { authorization: `Bearer ${token}`, ["content-type"]: "application/json" },
      body: JSON.stringify({ query: query, variables: {} }),
    });
    // The response will look like this:
    // {
    //   "data": {
    //     "getTests": {
    //       "results": [
    //         {
    //           "issueId": "13747",
    //           "testType": {
    //             "name": "Manual"
    //           }
    //         }
    //       ]
    //     }
    //   }
    // }
    const json = await response.json();
    for (const result of json.data.getTests.results) {
      issues.push(result);
    }
  }
  return issues;
}

@csvtuda thankyou for your response and providing the apis for updating test types manually
The issue has been solved but the only thing pinning to me is that,
Why the customization features like this got removed in recent versions?
Because I see there is great customizations available in older versions,
that is missing in latest ones and removed even from the documentation.
Isn't it better to give high level of customization to the users so they can configure it like they want.
JUST A SUGGESTION.

Thanks for the feedback! I agree that especially the documentation should probably be available in a version-specific fashion. It's something I have never really managed to thoroughly investigate.

Why the customization features like this got removed in recent versions?

It basically boils down to me not being able to adequately model Xray's behaviour in the plugin. Consider the removed jira.createTestIssues option, for example. It allowed the creation of new test issues for tests without issue keys in their title. Pretty cool. But the issues created that way are identified and compared by their summary in Xray when uploading results. You're uploading results after you've renamed the test case in Cypress? You'll get a new test issue in Jira. The Jira board owner decided to add a QA:  prefix to all test issues? You'll get a lot of new test case issues without the prefix unless you rename all test cases in Cypress.
Obviously this can be prevented by adding issue keys to the Cypress test titles for the plugin to find. Or by setting jira.createTestIssues to false, right? No, unfortunately not. The Cucumber feature file upload does not care about that. It's even worse because Xray tries to match scenarios to existing test issues as follows:

If Test key is not present in the file, system tries to find the Test having: the same source and original relative path of .feature (e.g. "[project_lambda]core/sample_addition.feature) [...]

So if you rename your feature file or any of the directories it's contained in, you'll often end up with new test cases on feature file upload. Even if the plugin is explicitly told not to do that. Moreover, if you've tagged all Gherkin scenarios with issue keys, the upload can still create new issues if the tagging scheme is modified in Xray (i.e. scenario and precondition prefixes).
It is basically impossible for the plugin to prevent issues from being created, because Xray does a lot of things behind the scenes. So why keep such an option that will only confuse users (see linked issues above) and is a pain in the butt for me to maintain?
That's why I decided that the plugin should always consider Xray as the single source of truth for the time being. No more test issue updating (the feature file upload is an exception to this and has blown up the plugin's complexity over time, unfortunately). The plugin is only allowed to create or modify test execution issues. It's basically become a reporter.

@csvtuda Thanks again for understandable clarification and being helpful.


[Branch Friendly] Can't build a new VM cluster using friendly branch code

Tried to bring up a VM cluster using the code in branch friendly and it fails with the following issues. Looks like some un-tested code got merged into the friendly branch.
Recipe Compile Error in /var/chef/cache/cookbooks/bach_spark/attributes/default.rb

08:55:04  30>> default.bach_spark.environment.SPARK_LOCAL_IP = node.bcpc.floating.ip

This change which got pulled into the {{friendly}} branch is causing the code to break.

'git blame' indicates that's from Amit's 'spark_enhance' changes.
<EMAIL_ADDRESS>" data-digest="From<EMAIL_ADDRESS>" style="">
From<EMAIL_ADDRESS>Subject: Re: [bloomberg/chef-bach] [Branch Friendly] Can't build a new VM cluster using friendly branch code (#507)
This change which got pulled into the {{friendly}} branch is causing the code to break.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub

Cluster build is successful using friendly branch after fixing the issue with the spark related components.


Unattended upgrade of postgres broke the uptime check

The server's unattended upgrades updated postgres (server and client). This caused an uptime check to fail. I'm assuming that either:

The update / restart occurred mid-request, causing the 500
The update / restart occurred mid-sync, causing the 500
The update / restart borked up the connection pool
The update / restart caused a prolonged (> 1min) downtime of the database

Try to figure out what happened and how a user 500 can be avoided in the future.
Relevant log entry (notice how a WRITE failed exactly 5 mins after the connection was terminated):
Jun 02 06:25:20 bloggulus bloggulus[850]: 2021/06/02 06:25:20 FATAL: terminating connection due to administrator command (SQLSTATE 57P01)
Jun 02 06:30:20 bloggulus bloggulus[850]: 2021/06/02 06:30:20 write failed: write tcp <IP_ADDRESS>:46586-><IP_ADDRESS>:5432: write: broken pipe

Still broken with Hikari?


Web Alert events

Analytics tracking for web alerts.

:rocket: PR was released in v4.22.0 :rocket:


Support for Django templating language

Is there any chance this can happen? I like the old version of hyde, and I'd be eager to upgrade except that I don't want to give up my Django templates.

@palewire,
Definitely a possibility - the design supports multiple templates. However, I am curious as to why you like Django over Jinja for static websites.

Kind of lame reason: I have a well developed Django base template I am required to deploy across a variety of sites (i.e. latimes.com). I might be ignorant of some easy fix, but it feels a lot easier for me to drop the Django base templates into Hyde, inherit and run in the site-specific templates than have to maintain a separate version of the base template with Jinja friendly block tags

Thats a good reason actually. Having django template support for this version of hyde is a definite possibility - perhaps for 0.9 version. Not sure about the time line though.

Okay. It's not a big hurry, but I probably won't upgrade to 1.0 without that feature. If there's some way I can contribute, please let me know.
Another argument along the same lines is that Django support might help you win converts among people with preexisting Django database-driven sites. If they can use their preexisting templates, there is less distance for them to travel.

Agreed. It is one of primary reasons why the new version of hyde was designed with template abstraction.
That said, I still think Jinja2 is better even for dynamic websites. I am not sure how involved your templates are... porting the template to jinja2 may not be that time consuming if your django templates do not contain too much logic:

http://jinja.pocoo.org/docs/switching/
https://github.com/mitsuhiko/jinja2/blob/master/ext/djangojinja2.py
https://github.com/mitsuhiko/jinja2/tree/master/ext/django2jinja
http://lethain.com/replacing-django-s-template-language-with-jinja2/


Inline all the things! 🎨

#92 introduced quite a serious performance regression by refactoring inlinable code in to a helper function which was only usable from inlined code, but not itself inlinable. The first commit corrects this.
Upon further inspection, I noticed a pattern - that all internal functions seemed to only be @usableFromInline and not @inlinable, whereas their public siblings were all @inlinable. Inlining is critical for exactly this kind of code - lazy wrappers and collections and so on, and especially when they are generic. For instance, how is the client's instance of the compiler supposed to be able to optimise Chain, when the implementation of offsetForward is hidden from it?

Additionally, I would strongly recommend setting up a benchmark suite, so that small refactorings don't cause huge performance regressions in future. I have some concerns about adding swift-algorithms as a dependency for my performance-sensitive project, and a benchmark suite which ensures at least stable baseline performance would help convince me that it's safe to rely on this project.

@swift-ci please test

Thanks for chasing these down, @karwa! Agreed that this is a better default, and that we do eventually want a wait to keep benchmarks for this package.


Please make openrc-shutdown broadcasts optional

There's usually no need to broadcast to other users if you are on a single user machine. However, there's a problem regarding OpenRC: since the shutdown command can only be issued as root, users that run the command with sudo or su or via elogind receive the broadcast anyway (and this makes computers beep / notifications pop with sound). This can be annoying for those who want computers to be especially quiet. I request a --no-wall option to disable broadcasts altogether.

Hi,
If you dont use the beep sound for other purposes, there is a way to disable it in general:
https://wiki.archlinux.org/index.php/PC_speaker

Actually, disabling the PC speaker does nothing in itself, since the desktop environment can still pick up and alert for that broadcast.


Validate cloudprovider credentials

What would you like to be added:
Add validation for cloudprovider secret
Why is this needed:
Currently, when uploading secrets via the UI, all secret fields are required and validated. However, when creating those credentials via the cloudprovider secret, there is no validation. This results in errors such as:
Flow "Shoot cluster reconciliation" encountered task errors: [task "Waiting until shoot infrastructure has been reconciled" failed: failed to create infrastructure: retry failed with context deadline exceeded, last error: extension encountered error during reconciliation: Error reconciling infrastructure: secret shoot--xxxx--xxxx/cloudprovider doesn't have a subscription ID] Operation will be retried.

g/g does not know anything about cloud provider credentials.
Isn't it kind of similar to https://github.com/gardener/gardener-extension-provider-aws/issues/40, https://github.com/gardener/gardener-extension-provider-azure/issues/42, etc.?
Shall we close this issue in favor of those?

Ah yes, it would make more sense in the extension repo!
The two issues you referenced would be great for fixing a secret without all the fields in place but don't address validating a cloudprovider secret when it is created. The error in this issue was is caused by a customer not including their Azure subscription ID into their secret (secret shoot--xxxx--xxxx/cloudprovider doesn't have a subscription ID)
Should I move this issue to the Azure extension repo? And also create similar issues for the other providers?

Whatever you prefer more, either updating/extending the scope of the existing issues or creating new issues. But yes, they should definitely be moved to the various provider extension repos, g/g cannot help, i.e., this issue here should be closed.

closing in favor of the issue in the azure extension: https://github.com/gardener/gardener-extension-provider-azure/issues/81


Please Answer in #245

Is there an existing issue for this?

[X] I have searched the existing issues

🐛 Describe the bug
Dynamic pagination cannot be accessed on user-defined layout pattern #245
✔ Expected behavior
.
👣 Steps to Reproduce
.
💻 Platform

[ ] Bukkit
[ ] Sponge
[X] Other

⭐ Versions
1.19.4
✍ Additional context
.

Its not completed..


Add a link about the LogMonitor buttons

Following https://github.com/gaearon/redux-devtools/issues/196#issuecomment-187945400.
Looking forward to your comments.

@gaearon, bump?

Whoops, never mind the bump, have noticed it’s not just my PR waiting.


QueryBuilder: support ranking.features.featurename

Removes traceLevel, explainLevel and explainlevel aliases
Adds

model.{filter,locale}
ranking.{rerankCount,matching}
grouping.{defaultMaxGroups,defaultMaxHits,globalMaxGroups,defaultPrecisionFactor}
presentation.summary
trace.{level,explainLevel,profileDepth,query}
dispatch.topKProbability
hitcountestimate
weakAnd.replace
wand.hits

Replaces presentation.format with presentation.format.tensors
Query builder now has all parameters documented in https://docs.vespa.ai/en/reference/query-api-reference.html except:

noCache and streaming.{userid,groupname,selection,priority,maxbucketspervisitor}: supported by query builder but are not documented (on that page)
select: Seems like there are 2 types of select and at least 1 of them is covered by yql?

Allows user defined key-values under ranking.features (Fixes #24475)

select: Seems like there are 2 types of select and at least 1 of them is covered by yql?

yes. See https://github.com/vespa-engine/documentation/pull/2383 - the select parameter is there, but not something we want to promote, so good to not have it in the query builder
the streaming. parameters are documented in https://docs.vespa.ai/en/streaming-search.html for the same reason - we do not want these in the querybuilder either.
so everything looks right now, except the missing noCache - will look into

Added noCache to https://github.com/vespa-engine/documentation/pull/2383, too


OCM-7315 | feat: describe client support for configurable registries

https://issues.redhat.com/browse/OCM-7315

/approve

/approve


Fix need to rebuild col_id_to_predicates when true predicates encountered

Proposed changes
Issue Number: close #xxx
relate pr: #25366
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


add "Bill Scanlon's Data Criteria" to NC Datapalooza Future Eventbrite Messaging

Meeting with Bill on Wednesday. Thanks @zachambrose

@natalienoel1 completing in mktg draft, followed by signed off on filling in gaps and additional input from @wildca01t


Unable to create lock in backend with simultaneous backups from different hosts?

Output of restic version
restic 0.9.3 compiled with go1.11.1 on linux/amd64
What should restic do differently? Which functionality do you think we should add?
If lock is required but cannot be acquired because another host/pid has the lock, restic should have an option to wait and retry until either the lock can be acquired or some timeout expires or retry count is exceeded.
What are you trying to do?
Trying to use https://github.com/ixc/restic-pg-dump on multiple hosts with the same (default) cron schedule (0 */4 * * *).
Sometimes, depending on the specific timing (how long it takes to do a database dump, how long it takes one host or the other to send data to S3), it seems I get an error like this:
Fatal: unable to create lock in backend: repository is already locked exclusively by PID 283 on 24e1b7101987 by root (UID 0, GID 0)

Did restic help you or made you happy in any way?
Yes! It's amazing to find a feature rich and active open source project offering encrypted incremental and network efficient backups that is easy to use.
In particular, the ability to thin the repository to N latest, daily, weekly, etc. with deduplication is exactly what I needed. Thanks!

Hm, thanks for the report. In my opinion, that's a shortcoming of the scripts in the docker container that you're using. There are two types of locks in a repository: exclusive (used for prune and forget), and non-exclusive (all other operations). There may be more than one non-exclusive lock (so multiple instances of restic can save their data simultaneously) but at most one exclusive lock. When an exclusive lock exists, no other locks must exist in parallel, even non-exclusive locks are forbidden.
In practice, this means that you can run restic backup from several different hosts and use the same repo, but when prune is running, no backups can be made until it finishes.
In general, running restic forget after each restic backup operation is okay, but running prune (via restic forget --prune) will block the repo. That's what you're experiencing.
I suggest you think about what you schedule is: If you have a daily backup for several machines, run prune only once per week (or so) while no other machines make backups.
This is not an issue in restic, so I'm closing this issue for now. Please feel free to add further comments. Thanks!

@fd0 thanks for clarifying the way restic works. However, I still think this feature request is valid. If I am attempting a backup, but some other scheduled process/server (or interactive manually triggered process) is doing forget --prune at the same time, it will fail with an error.
Even if that only happens once a week, instead of 50% of the time every 4 hours, it's still a missed backup. And I expect that the longer I delay in doing a prune, or the bigger the backup size, the longer the prune will take, and the more servers are backing up to or the more people who are using the same repository, will increase the chance that backups will fail during that window.
I still believe that restic should (and could without too much difficulty) expose an option to retry (up to a retry limit or timeout) when it is unable to acquire a lock, before failing with an error. For example, --retry 10 (10 times) or -- retry 5m (keep retrying for 5 minutes).
The only alternative I can see is for everyone attempting to schedule backups and wanting reliable backups is to re-implement their own retry logic on failure to acquire a lock, which seems like something everyone scheduling backups would need to do (repetitive).
Even if I were to do as you suggest, it's not necessarily within my control to ensure that every developer who deploys this to any/every server will not configure an overlapping schedule. And it's a pain to have to run not only a scheduled task on every server, but also run one "master" scheduled task to run prune on a non-overlapping schedule.
I think that significantly increases the setup complexity required to get backups up and running using an image like this. It's no longer just a one liner docker run ... to get scheduled automated backups.

Hmmm, I disagree; I think that is feature creep, and complexity that restic doesn't need to incur. The bug is in the script that is running it at the wrong time, and retries are trivial in scripts/wrapping programs anyway.

Hmmm, I disagree; I think that is feature creep, and complexity that restic doesn't need to incur. The bug is in the script that is running it at the wrong time, and retries are trivial in scripts/wrapping programs anyway.

I disagree. :)
IMHO feature creep is to add features which are rarely needed. Having some retry mechanic probably is useful for most people. Do you expect all of them to script something on their own? What about people who aren't able to do that? Keep in mind that not everyone is a programmer.
I've wrote a small wrapper script for restic to handle everything on my Unix servers. But while I do backups on Windows aswell my batch script skills are close to non existant, hence there is no retry logic for my backups on Windows. If a backup is missed because prune or check haven't finished it'll be executed on the next run 24 hours later.
I'm aware that there are issues/features which are more important than this one, but think this a valid RFE and the issue should atleast be reopened to keep track of it.

Any chance we can reopen this? Backups can also fail unexpectedly when a user is running an unscheduled forget --prune. Surely not all usage of restic is carefully scheduled and scripted by programmers?

A "wait" option would definitely be beneficial, at the very least restic could return a > 1 return code when the repository is exclusively locked for sake of (easier) scripting purposes.
My scenario is similar to what is described in posts above; I run a backup + forget every hour and perform a prune once a week. This prune takes well over an hour and therefore results in scheduled backups failing.
Right now, I catch this by checking the return code of restic, and 'grepping' for "exclusively locked" - when that is the case, I back-off for 5 minutes and try again. This would be easier if restic would return something else than 1 (which it already returns for all other errors), but it would most definately be even more convenient if restic where able to just wait itself.
Alternatively, would it be possible to not require an exclusive lock when performing a prune?
I'm not privy to the internals, but I'm imagining that 'forget' marks the datasets as no longer in use; shouldn't prune be able to remove the marked datasets without requiring an exclusive lock in the first place?

Just as an additional data point, it's just taken me a few hours to update https://github.com/ixc/restic-pg-dump to retry when it encounters exclusive locks (actually when it encounters any error, which might not be appropriate). And my first attempts were buggy and I didn't realise I ended up with many overlapping/waiting restic scripts (triggered by cron). And I had to put this retry handling code around basically every call to restic (backup, check, forget, prune).
In searching restic issues on GitHub it appears that there have been quite a few similar reports in the past about issues when backing up from multiple hosts. I can't imagine that scenario is that uncommon, so I still really think it's a valid request for restic to implement it's own wait/retry option.
If the goal is reliable backups, and multiple hosts is a supported use case, then I think this is really essential to save users from implementing this time consuming and error prone task themselves, over and over again.

I'm +1 to adding a --wait option - this would be very useful in github.com/heptio/velero.

restic should IMO automatically resolve locks created by the same node, when the pid does not exist anymore.


Support Python 3.13 in pyfluent repos

Need to support Python 3.13 in CI

[ ] pyfluent
[ ] pyfluent-visualization
[x] pyansys-units
[ ] pyfluent-parametric (maintenance mode)

https://github.com/ansys/pyansys-units/pull/309

https://github.com/ansys/pyfluent-visualization/pull/462


ESP32 via UDP: Failed status on line 48: 1. Aborting.

Issue template

Hardware description: ESP32
RTOS: FreeRTOS
Installation type: micro-ROS component for ESP-IDF
Version: foxy

Steps to reproduce the issue
Install ESP-IDF and create a first project, as written here:
sudo pacman -S --needed gcc git make flex bison gperf python-pip cmake ninja ccache dfu-util libusb
mkdir -p ~/esp
cd ~/esp
git clone --recursive https://github.com/espressif/esp-idf.git
cd ~/esp/esp-idf
./install.sh esp32
. $HOME/esp/esp-idf/export.sh
cd ~/esp
cp -r $IDF_PATH/examples/get-started/hello_world .
cd ~/esp/hello_world
idf.py set-target esp32
idf.py build
idf.py -p /dev/ttyUSB0 flash

At this point with idf.py -p /dev/ttyUSB0 monitor I can correctly see the "Hello world!" output being generated by the ESP32.
Moving on, install the micro-ROS component for ESP-IDF and run the int32_publisher example, as written here:
. $IDF_PATH/export.sh
pip3 install catkin_pkg lark-parser empy colcon-common-extensions
cd ~/esp/hello_world
mkdir components
cd ~/esp/hello_world/components
git clone -b foxy https://github.com/micro-ROS/micro_ros_espidf_component.git
cd ~/esp/hello_world/components/micro_ros_espidf_component/examples/int32_publisher
idf.py set-target esp32
idf.py menuconfig
# set WiFi credentials, and agent's port (8888) and IP address (same as local machine: <IP_ADDRESS>)
idf.py build
idf.py -p /dev/ttyUSB0 flash

Run a micro-ROS Agent on a new terminal:
docker run -it --rm --net=host microros/micro-ros-agent:foxy udp4 --port 8888 -v6

Monitor the ESP32:
 idf.py -p /dev/ttyUSB0 monitor

Expected behavior
I should be able to see the ESP32 publishing messages on a new topic.
Actual behavior
The ESP32 does not publish any message, and no new topic is created.
From the terminal monitoring the ESP32 I see that it successfully connects to the WiFi network, but then the error Failed status on line 48: 1. Aborting. appears, referring to this line.
The output of the micro-ROS Agent is the following:
➜  ~ docker run -it --rm --net=host microros/micro-ros-agent:foxy udp4 --port 8888 -v6
[1632387100.513237] info     | UDPv4AgentLinux.cpp | init                     | running...             | port: 8888
[1632387100.513442] info     | Root.cpp            | set_verbose_level        | logger setup           | verbose_level: 6

Which are the IP address of the ESP32 and the IP address of your machine?

IP address of the ESP32: <IP_ADDRESS>
IP address of my machine: <IP_ADDRESS>

It seems that your ESP32 and the agent have no network communication. Because ESP32 packets are not reaching your machine.
Can you check that with another network example?
Also, can you hardcode the agent address here?

I tried other examples and every time it fails (aborting on the same line).
I tried hardcoding the agent address with RCCHECK(rmw_uros_options_set_udp_address("<IP_ADDRESS>", CONFIG_MICRO_ROS_AGENT_PORT, rmw_options)); and it still fails (aborting on the same line).
Moreover, I tested branch release/v4.3 of the ESP-IDF (instead of main), and once again the result is the same.

I meant another networking example like opening a UDP port in the computer and sending data from the ESP... I guess that there is a network connectivity problem in your setup.

Oh I got it, finally.
I started digging into the low-level stuff but it was simply due to my firewall rules, don't know why I didn't think about that before...
Hope this will save some time to anyone facing the same problem in future: just update your firewall rules.
And, of course, thank you for the support and for your work on micro-ROS!

@leonardogargani Were you running it on windows? Can you provide more details on what kind of rules have you updated?

@leonardogargani Were you running it on windows? Can you provide more details on what kind of rules have you updated?

Assuming you're asking about the micro-ROS Agent, I was running it as a docker container from a Linux machine.
Look at the way I was launching it:
docker run -it --rm --net=host microros/micro-ros-agent:foxy udp4 --port 8888 -v6

The solution was simply opening port 8888 for UDP traffic... pretty obvious, but I wasn't thinking about it at that moment.

Yes I was asking about the agent. Unfortunately this solution does not work for me in Windows, but works on Linux straight away. Have you adjusted any settings in Linux or gateway? Or just used that line you just wrote and it started working?

After having added the firewall rule (port 8888 open for UDP traffic), it started working correctly without any other adjustment.
I have no experience with Windows, but if I were you I would make sure that both Windows Firewall and any installed antivirus allow the communication above.


feat(ComboBox): add invalid and invalidText props

Closes IBM/carbon-components-react#1161
Added props in a ComboBox component to let users validate the selected value.
Changelog
New

invalid prop in a comboBox component
invalidText prop in a comboBox component

Looks great to me, thanks for doing this! 🎉

Looks great to me, thanks for doing this! 🎉

No, no, thank you guys for your work!
Using this in our project is absolutely amazing!
Greetings from IBM in Poland! :smiley:


[Bug]: Documentation for SDK-React is completely missing (404)

Telegram Application
Other
Describe the Bug
https://docs.telegram-mini-apps.com/packages/telegram-apps-sdk-react
To Reproduce
Steps to reproduce the behavior:

Go to https://docs.telegram-mini-apps.com/packages/telegram-apps-sdk-react
Verify 404

Expected Behavior
Steps to reproduce the behavior:

Go to https://docs.telegram-mini-apps.com/packages/telegram-apps-sdk-react
View documentation for using v2

https://docs.telegram-mini-apps.com/packages/telegram-apps-sdk-react/1-x


AWS Amplify not generating proper graphql input depth

Which Category is your question related to?
AWS Amplify code generation
What AWS Services are you utilizing?
AWS Amplify API
Provide additional details e.g. code snippets
I am new to both graphql & AWS Amplify, so please forgive any ignorance :)
I have a graphql schema like this:
    type Location @model @auth(rules: [{allow: owner}]){
      street: String
      city: String
      state: String
      zip: String
    }

    type Trip @model @auth(rules: [{allow: owner}]){
      id: String!
      ...
      location: Location
    }

I'm trying to create both the location and the trip at the same time with a mutation request like this:
    mutation {
      createTrip(input: {
          id: "someIdentifier",
          location: {
            street: "somewhere"
          }
      }) {
          id
          location {
            street
          }
      }
    }

But I'm getting an error like this:
    {
      "data": null,
      "errors": [
        {
          "path": null,
          "locations": [
            {
              "line": 2,
              "column": 21,
              "sourceName": null
            }
          ],
          "message": "Validation error of type WrongType: argument 'input' with value '...' contains a field not in 'CreateTripInput': 'location' @ 'createTrip'"
        }
      ]
    }

Checking the generated schema.graphql file, I see that there is indeed no location object on the input model:
    input CreateTripInput {
      id: String!
      ...
    }

How can I have amplify generate the proper input schema so that I can create both the Trip and the location objects at the same time?
Other notes

Manually updating the generated code in /amplify/backend/api/myApi/build/schema.graphql is not successful.
Manually updating the schema in the dashboard works with:

input CreateTripInput {
         ...
	location: CreateLocationInput
}

@dperconti In your schema, I see that both Trip and Location have model directive. I don't see @connection directive connecting the Trip with Location. You may have to update your schema connecting to connect your models if you want them to be in 2 separate tables and want the ability to query Trip based on Location. Using 2 separate table you won't be able to create both Trip and Location in a single mutation
    type Location @model @auth(rules: [{allow: owner}]){
      street: String
      city: String
      state: String
      zip: String
      trips: Trip @connection(name:"TripLocation")
    }

    type Trip @model @auth(rules: [{allow: owner}]){
      id: String!
      location: Location @connection(name:"TripLocation")
    }

If the Location data is very specific to a trip and you don't want to create a separate table, then get rid of @model directive from your Location type. Doing so would allow you to create Location as a part of same mutation
    type Location {
      street: String
      city: String
      state: String
      zip: String

    }

    type Trip @model @auth(rules: [{allow: owner}]){
      id: String!
      location: Location
    }

Perfect - the later recommendation was exactly what I needed. Do you recommend any resources that I can read up on to learn more about the different directive and their respective usages? Thank you again.

@dperconti we have the directives documented in https://aws-amplify.github.io/docs/cli/graphql#directives


Current ledger-go seems incompatible with linux

https://github.com/Zondax/ledger-go/issues/19

This is related to #7 as well.

Closed due to https://github.com/Zondax/ledger-go/issues/19 closure


Critical issue with mergeFeaturesByPrevalence

Unexpected and potentially critical behavior with mergeFeaturesByPrevalence.
Let's first prepare example data.
library(mia)
data(GlobalPatterns, package="mia")
tse <- GlobalPatterns
tse <- transformAssay(tse, assay.type="counts", method="relabundance")

Here we merge features by prevalence, and return the result at the family level.
nrow(mergeFeaturesByPrevalence(tse, rank="Family", assay.type="relabundance", detection  = 0.5/100, prevalence  = 20/100))
#> 35

Here we merge features first by Family level grouping, then by prevalence.
altExp(tse, "Family") <- mergeFeaturesByRank(tse, rank="Family")
nrow(mergeFeaturesByPrevalence(altExp(tse, "Family"), assay.type="relabundance", detection  = 0.5/100, prevalence  = 20/100))
#>2

Same happens when we treat Family as a group, rather thank rank:
altExp(tse, "Family2") <- mergeFeatures(tse, f="Family")
nrow(mergeFeaturesByPrevalence(altExp(tse, "Family2"), assay.type="relabundance", detection  = 0.5/100, prevalence  = 20/100))
#>2

Interestingly, checking the prevalences manually yields even different numbers.. :-D
sum(rowMeans(assay(altExp(tse, "Family"), "relabundance") > 0.5/100) > 0.2)
#>26

sum(rowMeans(assay(altExp(tse, "Family2"), "relabundance") > 0.5/100) > 0.2)
#>19

All these approaches should be safely expected to yield the same result, I think. Failing to do so may lead to critical bugs in analyses.
Perhaps the reason is obvious but at first this seems very confusing.
To be investigated and fixed as a top priority.

I suggest that @ake123 checks and @TuomasBorman can review?

Good to first diagnose the issue and discuss the solution.
In both cases, the low-level features should be aggregated to the higher level (here, Family) before agglomerating the rare groups. This is one possible source for the behavior.

Also some additional unit tests will be warranted here.

Not sure where the NAs come fromsince the assay itself does not seem to have any NAs:

sum(is.na(assay(tse, "relabundance")))
0

Usually good strategy is to calculate manually what is needed and then see where the differences are in each deviating case.

Here are the cases that the numbers fluctuate
First case is when the user includes na.rm = TRUE for mergeFeaturesByRank or na.rm=FALSE for mergeFeaturesByPrevalence
nrow(mergeFeaturesByPrevalence(tse, rank="Family", assay.type="relabundance", detection  = 0.5/100, prevalence  = 20/100,na.rm=FALSE))
[1] 27

altExp(tse, "Family") <- mergeFeaturesByRank(tse, rank="Family",na.rm = TRUE)
> sum(rowMeans(assay(altExp(tse, "Family"), "relabundance") > 0.5/100) > 0.2)
[1] 19

altExp(tse, "Family2") <- mergeFeatures(tse, f="Family",na.rm = FALSE)
>
> sum(rowMeans(assay(altExp(tse, "Family2"), "relabundance") > 0.5/100) > 0.2)
[1] 19

Second case
Also when removing NA from empty.fields in  mergeFeaturesByRank with signature = c(x = "SummarizedExperiment")
empty.fields = c(NA, "", " ", "\t", "-", "_")

This is a critical high-importance issue to sort out. I suggest that @TuomasBorman will prioritize to review this one with Jeba asap.

I agree that the default should be no agglomeration. Otherwise this can lead to confusing results.
Agreed.

Yet another observation.
The order of rows is returned differently in mergeFeatures (Family2) and mergeFeaturesByRank (Family3), although the data is otherwise the same:
Here, rownames do not match but the same rownames are in both:
> all(rownames(altExp(tse, "Family2")) == rownames(altExp(tse, "Family3")))
[1] FALSE
> all(rownames(altExp(tse, "Family2")) %in% rownames(altExp(tse, "Family3")))
[1] TRUE
> all(rownames(altExp(tse, "Family3")) %in% rownames(altExp(tse, "Family2")))
[1] TRUE

Also the assay values match when we make sure the rows are in the same order:
> all(assay(altExp(tse, "Family2")) == assay(altExp(tse, "Family3")))
[1] FALSE

> all(assay(altExp(tse, "Family2")[o,]) == assay(altExp(tse, "Family3")[o,]))
[1] TRUE

The
Results from mergeFeatures  are in alphabetical order:
all(rownames(altExp(tse, "Family2"))== sort(rownames(altExp(tse, "Family2"))))
TRUE

The results from mergeFeaturesByRank are in the same order than in the original rowData, when the NA group is removed:
 all(rownames(altExp(tse, "Family3"))== unique(rowData(tse)$Family)[-1])
[1] TRUE

It would be beneficial to harmonize the sorting logic.
The additional thing to discuss:

Shall we order alphabetically or respect the rowData order? The latter would feel more natural but it might have some issues when onRankOnly=FALSE, for instance. On the other hand we do not have clear examples of any real issues with that, it could be possible to just use the rowData order for these cases and later reconsider this shall needs arise.
Shall we review if some other functions have similar sorting issues? I tend to think that it would be good to check on the same go, to maintain internal logic.

Up

if i gather correctly, there are about 4 indications on the changes to be made.

[ ] The default value of rank in mergeFeaturesByRank should be NULL
[ ] Add na.rm parameter to mergeFeatures
[ ] Change the default to onRankOnly=TRUE in mergeFeaturesByRank
[ ]  Respect the rowData order

Yes, and then if you can also check other functions if they have similar sorting issues

This was fixed


Remove #![custom_attribute]

No longer needed by the looks of it!

@alexcrichton: no appropriate reviewer found, use r? to override

@bors: r+

:pushpin: Commit cd3b87dc7ee79d33e6bad054ef1d4d54b00bcea1 has been approved by alexcrichton

:hourglass: Testing commit cd3b87dc7ee79d33e6bad054ef1d4d54b00bcea1 with merge 8a9b980a8402fde4c7dec14050ec75d742cc1acb...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 8a9b980a8402fde4c7dec14050ec75d742cc1acb to master...


I have a question about Visual Concept Sliders!

Hi! I'm trying to train a slider to remove the background from an image and replace it with white.
But the visual slider didn't work as I expected. I changed Lr and rank but didn't get the desired result. The result is not stable compared to the text slider.
On the right is a green screen Lora that I previously created using the copier Lora technique. What would I need to modify to get a similar result with the visual concept slider? (https://note.com/kohya_ss/n/nb258da07236f)

Below is the image pair I prepared.

Very interesting - I see text slider works decent compared to visual slider here. So my hunch is:

You could use prompts for visual sliders (same prompts you used for visual sliders). Especially - for positive "" and for neutral "white background"
maybe you can try overfitting the slider (large training steps)

This is completely different suggestion to sliders. You could also look into foreground-background segmentation with diffusion models. I believe there are works that show these segmentations using linear probes on top of intermediate activations. If you haven't explored this direction, it could be something to look into

Raising Lr to 0.001 and changing rank to 1 seems to work somewhat.

However, it still seems like the duplicator lora works a little better.

Awesome, so that's definitely better than the last one. What is the start_noise you are using for generation? You could try out values - 600, 650, 700, 750, 800, 850, 900. I'm guessing this could help too

closing the issue. Please feel free to reopen if issues persist. Thanks!


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/1103 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target.git

Docs Build status updates of commit 207e545:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: RepositoryUnauthorizedWithSourceCommit] Git data access to 'https://github.com/opstest2/docs-archive-test-source' (branch: Release_Archive_main_2022-05-31-04-09-33) is not authorized.. It looks like this might be the first time user: v-alji submitted a pull request to this repo. Before user can run builds in a pull request, he/she can enable 'v-alji' GitHub account in Docs by visiting Docs Portal (https://ops.microsoft.com). After enabling his/her account (v-alji), close and then reopen this pull request to start another build.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


How to add a metric to parse from HELM output in wandb_writer.py?

Before Asking 在提问之前

[X] I have read the README carefully. 我已经仔细阅读了 README 上的操作指引。

[X] I have pulled the latest code of main branch to run again and the problem still existed. 我已经拉取了主分支上最新的代码，重新运行之后，问题仍不能解决。

Search before asking 先搜索，再提问

[X] I have searched the Data-Juicer issues and found no similar questions. 我已经在 issue列表 中搜索但是没有发现类似的问题。

Question
I want to add a metric named Denoised inference time (s) to track the efficiency of my model in tools/evaluator/recorder/wandb_writer.py, so I changed the config file mymodel_example.yaml as follows:
project: ee_tune_eval
base_url: https://wandb.ai/liukui/EE-TUNE-EVAL
evals:
  - eval_type: helm
    model_name: llama2_ee
    source: helm
    helm_output_dir: /data3/lk/data-juicer/helm_output
    helm_suite_name: ee_test-llama2_ee
    token_per_iteration: <tokens per iteration in billions>
    benchmarks:
      - name: summarization_cnndm
        metrics:
          - ROUGE-2
          - Denoised inference time (s)
      - name: summarization_xsum
        metrics:
          - ROUGE-2
      - name: narrative_qa
        metrics:
          - F1
      - name: mmlu
        metrics:
          - EM

However, I got an error:
parsing summarization_cnndm.json
  parsing dataset_name: cnn-dm, sampling_min_length: 50, sampling_max_length: 150, doc_max_length: 512
Fail to parse summarization_cnndm: 'value'

I then checked the summarization_cnndm.json in HELM output dir, and there indeed isn't a value for Denoised inference time (s).
What modifications should I make to parse Denoised inference time (s) from the HELM output?
I would greatly appreciate your help and look forward to your prompt response.
Additional 额外信息
No response

Please refer to link


need solution

why it's not allowing me to deployment my repo into github.io?

Hi @yazzer22 ,
Request you to paste your folder structure and tell us on how to reproduce this issue. That'll make us understand what's going wrong at your end.


Running mtag example?

Hi,
What is the suggested way to run the mtag example code? It appears that multiple switch definitions aren't supported by p4app, and the VM provided in the most recent tutorials only supports P4-16 programs. The only remaining option seems to be to install the relevant dependencies via the instructions in the SIGCOMM_2015 tutorial, and go from there. Am I missing something, or is this an accurate outlook?
Thanks.
Edit: I see elsewhere that this isn't a full example.

TL;DR: yes, I would recommend installing bmv2 and p4c from source.
In more detail:

I haven't confirmed this recently, but the mtag code should run out of
the box by using p4c-bm-ss (passing the --p4-14 flag) to produce a JSON
configuration for bmv2, and then running that either natively or via
Mininet.

p4c and bmv2 can be installed on most Unix-like environments.

I wouldn't go back to the SIGCOMM 2015 tutorial -- just follow the
instructions in p4lang/behavioral-model and p4lang/p4c.

p4app does support multiple switches but yes, each switch currently needs
to run the same program.

-N
On Sun, Feb 11, 2018 at 7:47 AM, Alana Marzoev<EMAIL_ADDRESS>wrote:

Hi,
What is the suggested way to run the mtag example code? It appears that
multiple switch definitions aren't supported by p4app, and the VM provided
in the most recent tutorials only supports P4-16 programs. The only
remaining option seems to be to install the relevant dependencies via the
instructions in the SIGCOMM_2015 tutorial, and go from there. Am I missing
something, or is this an accurate outlook?
Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/p4lang/p4-spec/issues/579, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABwi0qIkCMSX6NjcDWPx_uxusE5XoYzsks5tTuFggaJpZM4SBU8S
.

(Closing this issue now as it doesn't relate to the language specification.)

Thank you!


multigpu training

how can I train using multigpu? when I tried to use multigpu code is not supported and only use 1 gpu training.

Since we just trained on one GPU the multi-GPU training is not implemented yet for this project.