Failed to build app with entrypoint test_bundle.dart for iOS simulator

Steps to reproduce

Setup by following the documentation
Create the first example of the documentation
Run it with patrol test --verbose -d 52BFBA29-5537-4BF5-9DEE-34391B1265D2 -t integration_test/example_test.dart

Actual results
Failed to build app with entrypoint test_bundle.dart for iOS simulator (xcodebuild exited with code 65)
I got Error: xcodebuild exited with code 65. I thought it was related to my certificate but I don't have any error on Testflight.
When I tried to run it on a real device I got Error: Running on physical iOS devices is possible only in release mode.
Where can I choose to run my app in release mode in patrol conf?
EDIT: With the flag --release it runs in release mode and with this flag, I got the same error
Failed to build app with entrypoint test_bundle.dart for iOS device (xcodebuild exited with code 65).
Logs

Real device logs
Verbose mode enabled. More logs will be printed.
$ flutter --suppress-analytics --no-version-check pub deps --style=list
Received 1 test target(s)
Received test target: /Users/gwendalbazin/Documents/Kpler/mobile-app/kpler_app/integration_test/example_test.dart
Generated entrypoint /Users/gwendalbazin/Documents/Kpler/mobile-app/kpler_app/integration_test/test_bundle.dart with 1 bundled test(s)
$ flutter --no-version-check --suppress-analytics devices --machine
Received 1 device(s) to run on
Received device: Gwendal’s iPad
Received 9 --dart-define(s) (0 custom, 9 internal)
Received internal --dart-define: PATROL_WAIT=0
Received internal --dart-define: PATROL_APP_PACKAGE_NAME=com.kpler2022.mobile
Received internal --dart-define: PATROL_APP_BUNDLE_ID=com.kpler2022.mobile
Received internal --dart-define: PATROL_ANDROID_APP_NAME=kpler_app
Received internal --dart-define: PATROL_IOS_APP_NAME=kpler_app
Received internal --dart-define: INTEGRATION_TEST_SHOULD_REPORT_RESULTS_TO_NATIVE=false
Received internal --dart-define: PATROL_TEST_LABEL_ENABLED=true
Received internal --dart-define: PATROL_TEST_SERVER_PORT=8081
Received internal --dart-define: PATROL_APP_SERVER_PORT=8082
• Building app with entrypoint test_bundle.dart for iOS device (release)...
$ flutter build ios --no-version-check --suppress-analytics --config-only --no-codesign --release --target /Users/gwendalbazin/Documents/Kpler/mobile-app/kpler_app/integration_test/test_bundle.dart --dart-define PATROL_WAIT=0 --dart-define PATROL_APP_PACKAGE_NAME=com.kpler2022.mobile --dart-define PATROL_APP_BUNDLE_ID=com.kpler2022.mobile --dart-define PATROL_ANDROID_APP_NAME=kpler_app --dart-define PATROL_IOS_APP_NAME=kpler_app --dart-define INTEGRATION_TEST_SHOULD_REPORT_RESULTS_TO_NATIVE=false --dart-define PATROL_TEST_LABEL_ENABLED=true --dart-define PATROL_TEST_SERVER_PORT=8081 --dart-define PATROL_APP_SERVER_PORT=8082
	Warning: Building for device with codesigning disabled. You will have to manually codesign before deploying to device.
	Building com.kpler2022.mobile for device (ios-release)...
$ xcodebuild build-for-testing -workspace Runner.xcworkspace -scheme Runner -configuration Release -sdk iphoneos -destination generic/platform=iOS -quiet -derivedDataPath ../build/ios_integ OTHER_SWIFT_FLAGS=$(inherited) -D PATROL_ENABLED
	error: the following command failed with exit code 1 but produced no further output
	Run custom shell script 'Run Script'
	** TEST BUILD FAILED **

✗ Failed to build app with entrypoint test_bundle.dart for iOS device (xcodebuild exited with code 65) (8.3s)
Error: xcodebuild exited with code 65
#0      throwToolExit (package:patrol_cli/src/base/exceptions.dart:7:3)
#1      IOSTestBackend.build.<anonymous closure> (package:patrol_cli/src/ios/ios_test_backend.dart:136:9)
<asynchronous suspension>
#2      DisposeScope.run (package:dispose_scope/src/dispose_scope.dart:46:7)
<asynchronous suspension>
#3      IOSTestBackend.build (package:patrol_cli/src/ios/ios_test_backend.dart:76:5)
<asynchronous suspension>
#4      TestCommand._build (package:patrol_cli/src/commands/test.dart:265:7)
<asynchronous suspension>
#5      TestCommand.run (package:patrol_cli/src/commands/test.dart:199:5)
<asynchronous suspension>
#6      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#7      PatrolCommandRunner.runCommand (package:patrol_cli/src/runner/patrol_command_runner.dart:341:18)
<asynchronous suspension>
#8      PatrolCommandRunner.run (package:patrol_cli/src/runner/patrol_command_runner.dart:285:18)
<asynchronous suspension>
#9      patrolCommandRunner (package:patrol_cli/src/runner/patrol_command_runner.dart:70:20)
<asynchronous suspension>
#10     main (file:///Users/gwendalbazin/.pub-cache/hosted/pub.dev/patrol_cli-2.6.1/bin/main.dart:6:20)
<asynchronous suspension>

See the logs above to learn what happened. Also consider running with --verbose. If the logs still aren't useful, then it's a bug - please report it.
Error: xcodebuild exited with code 65
#0      throwToolExit (package:patrol_cli/src/base/exceptions.dart:7:3)
#1      IOSTestBackend.build.<anonymous closure> (package:patrol_cli/src/ios/ios_test_backend.dart:136:9)
<asynchronous suspension>
#2      DisposeScope.run (package:dispose_scope/src/dispose_scope.dart:46:7)
<asynchronous suspension>
#3      IOSTestBackend.build (package:patrol_cli/src/ios/ios_test_backend.dart:76:5)
<asynchronous suspension>
#4      TestCommand._build (package:patrol_cli/src/commands/test.dart:265:7)
<asynchronous suspension>
#5      TestCommand.run (package:patrol_cli/src/commands/test.dart:199:5)
<asynchronous suspension>
#6      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#7      PatrolCommandRunner.runCommand (package:patrol_cli/src/runner/patrol_command_runner.dart:341:18)
<asynchronous suspension>
#8      PatrolCommandRunner.run (package:patrol_cli/src/runner/patrol_command_runner.dart:285:18)
<asynchronous suspension>
#9      patrolCommandRunner (package:patrol_cli/src/runner/patrol_command_runner.dart:70:20)
<asynchronous suspension>
#10     main (file:///Users/gwendalbazin/.pub-cache/hosted/pub.dev/patrol_cli-2.6.1/bin/main.dart:6:20)
<asynchronous suspension>

Simulator logs
Verbose mode enabled. More logs will be printed.
$ flutter --suppress-analytics --no-version-check pub deps --style=list
Received 1 test target(s)
Received test target: /Users/gwendalbazin/Documents/Kpler/mobile-app/kpler_app/integration_test/example_test.dart
Generated entrypoint /Users/gwendalbazin/Documents/Kpler/mobile-app/kpler_app/integration_test/test_bundle.dart with 1 bundled test(s)
$ flutter --no-version-check --suppress-analytics devices --machine
Received 1 device(s) to run on
Received device: iPhone SE (3rd generation)
Received 9 --dart-define(s) (0 custom, 9 internal)
Received internal --dart-define: PATROL_WAIT=0
Received internal --dart-define: PATROL_APP_PACKAGE_NAME=com.kpler2022.mobile
Received internal --dart-define: PATROL_APP_BUNDLE_ID=com.kpler2022.mobile
Received internal --dart-define: PATROL_ANDROID_APP_NAME=kpler_app
Received internal --dart-define: PATROL_IOS_APP_NAME=kpler_app
Received internal --dart-define: INTEGRATION_TEST_SHOULD_REPORT_RESULTS_TO_NATIVE=false
Received internal --dart-define: PATROL_TEST_LABEL_ENABLED=true
Received internal --dart-define: PATROL_TEST_SERVER_PORT=8081
Received internal --dart-define: PATROL_APP_SERVER_PORT=8082
• Building app with entrypoint test_bundle.dart for iOS simulator (debug)...
$ flutter build ios --no-version-check --suppress-analytics --config-only --no-codesign --debug --simulator --target /Users/gwendalbazin/Documents/Kpler/mobile-app/kpler_app/integration_test/test_bundle.dart --dart-define PATROL_WAIT=0 --dart-define PATROL_APP_PACKAGE_NAME=com.kpler2022.mobile --dart-define PATROL_APP_BUNDLE_ID=com.kpler2022.mobile --dart-define PATROL_ANDROID_APP_NAME=kpler_app --dart-define PATROL_IOS_APP_NAME=kpler_app --dart-define INTEGRATION_TEST_SHOULD_REPORT_RESULTS_TO_NATIVE=false --dart-define PATROL_TEST_LABEL_ENABLED=true --dart-define PATROL_TEST_SERVER_PORT=8081 --dart-define PATROL_APP_SERVER_PORT=8082
	Building com.kpler2022.mobile.dev for simulator (ios)...
$ xcodebuild build-for-testing -workspace Runner.xcworkspace -scheme Runner -configuration Debug -sdk iphonesimulator -destination generic/platform=iOS Simulator -quiet -derivedDataPath ../build/ios_integ OTHER_SWIFT_FLAGS=$(inherited) -D PATROL_ENABLED
	error: the following command failed with exit code 1 but produced no further output
	Run custom shell script 'Run Script'
	** TEST BUILD FAILED **

✗ Failed to build app with entrypoint test_bundle.dart for iOS simulator (xcodebuild exited with code 65) (9.3s)
Error: xcodebuild exited with code 65
#0      throwToolExit (package:patrol_cli/src/base/exceptions.dart:7:3)
#1      IOSTestBackend.build.<anonymous closure> (package:patrol_cli/src/ios/ios_test_backend.dart:136:9)
<asynchronous suspension>
#2      DisposeScope.run (package:dispose_scope/src/dispose_scope.dart:46:7)
<asynchronous suspension>
#3      IOSTestBackend.build (package:patrol_cli/src/ios/ios_test_backend.dart:76:5)
<asynchronous suspension>
#4      TestCommand._build (package:patrol_cli/src/commands/test.dart:265:7)
<asynchronous suspension>
#5      TestCommand.run (package:patrol_cli/src/commands/test.dart:199:5)
<asynchronous suspension>
#6      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#7      PatrolCommandRunner.runCommand (package:patrol_cli/src/runner/patrol_command_runner.dart:341:18)
<asynchronous suspension>
#8      PatrolCommandRunner.run (package:patrol_cli/src/runner/patrol_command_runner.dart:285:18)
<asynchronous suspension>
#9      patrolCommandRunner (package:patrol_cli/src/runner/patrol_command_runner.dart:70:20)
<asynchronous suspension>
#10     main (file:///Users/gwendalbazin/.pub-cache/hosted/pub.dev/patrol_cli-2.6.1/bin/main.dart:6:20)
<asynchronous suspension>

See the logs above to learn what happened. Also consider running with --verbose. If the logs still aren't useful, then it's a bug - please report it.
Error: xcodebuild exited with code 65
#0      throwToolExit (package:patrol_cli/src/base/exceptions.dart:7:3)
#1      IOSTestBackend.build.<anonymous closure> (package:patrol_cli/src/ios/ios_test_backend.dart:136:9)
<asynchronous suspension>
#2      DisposeScope.run (package:dispose_scope/src/dispose_scope.dart:46:7)
<asynchronous suspension>
#3      IOSTestBackend.build (package:patrol_cli/src/ios/ios_test_backend.dart:76:5)
<asynchronous suspension>
#4      TestCommand._build (package:patrol_cli/src/commands/test.dart:265:7)
<asynchronous suspension>
#5      TestCommand.run (package:patrol_cli/src/commands/test.dart:199:5)
<asynchronous suspension>
#6      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#7      PatrolCommandRunner.runCommand (package:patrol_cli/src/runner/patrol_command_runner.dart:341:18)
<asynchronous suspension>
#8      PatrolCommandRunner.run (package:patrol_cli/src/runner/patrol_command_runner.dart:285:18)
<asynchronous suspension>
#9      patrolCommandRunner (package:patrol_cli/src/runner/patrol_command_runner.dart:70:20)
<asynchronous suspension>
#10     main (file:///Users/gwendalbazin/.pub-cache/hosted/pub.dev/patrol_cli-2.6.1/bin/main.dart:6:20)
<asynchronous suspension>

Patrol version
patrol: ^3.4.0
Patrol Doctor output

Patrol Doctor output
Patrol doctor:
Patrol CLI version: 2.6.1
Android:
• Program adb found in /Users/gwendalbazin/Library/Android/sdk/platform-tools/adb
• Env var $ANDROID_HOME set to /Users/gwendalbazin/Library/Android/sdk
iOS / macOS:
• Program xcodebuild found in /usr/bin/xcodebuild
• Program ideviceinstaller found in /opt/homebrew/bin/ideviceinstaller

Flutter Doctor output

Flutter Doctor output

[✓] Flutter (Channel stable, 3.16.2, on macOS 14.2.1 23C71 darwin-arm64, locale en-FR)
    • Flutter version 3.16.2 on channel stable at /Users/gwendalbazin/fvm/versions/3.16.2
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 9e1c857886 (9 weeks ago), 2023-11-30 11:51:18 -0600
    • Engine revision cf7a9d0800
    • Dart version 3.2.2
    • DevTools version 2.28.3

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/gwendalbazin/Library/Android/sdk
    • Platform android-34, build-tools 33.0.0
    • ANDROID_HOME = /Users/gwendalbazin/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15C65
    • CocoaPods version 1.14.3

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

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

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

[✓] Connected device (4 available)
    • iPhone (mobile)                     • 00008110-000451C41152801E                • ios            • iOS 17.2.1 21C66
    • Gwendal’s iPad (mobile)             • fd46f10d8b64a947e2122abb145ccb115d134562 • ios            • iOS 17.2 21C62
    • iPhone SE (3rd generation) (mobile) • 52BFBA29-5537-4BF5-9DEE-34391B1265D2     • ios            • com.apple.CoreSimulator.SimRuntime.iOS-17-2 (simulator)
    • Chrome (web)                        • chrome                                   • web-javascript • Google Chrome 121.0.6167.85

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Hi @Bazni. This also looks like a setup issue to me so closing it for now. If you'll decide to describe the issue on discord channel, please take a look at #rules where you can find an instruction of how to provide a logs which will help us better understand the cause of the issue.


Docathon changes

PR Summary:
Added some docstrings and other small fixes
PR Checklist

[ ] Includes appropriate unit test(s)
[x] Appropriate docstring(s) are added/updated
[x] Code is (approximately) PEP8 compliant
[ ] Issue(s) raised/addressed?

Looking like you need to adopt black 😁

I have been going back and forth on it for a year or two now (which inevitably means I'll go all-in sometime soon, on a whim)


Dwarf: add support for static members

change CU lang from C89 to C_plus_plus

ungroup gc, non-gc and thread statics in debuginfo

Example:
Sample:
using System;
using System.Collections.Generic;
using System.Runtime.CompilerServices;
using System.Threading;
using System.Threading.Tasks;

enum TestEnum
{
    A,
    B,
    C,
    D
}

struct TestStruct
{
    public static TestStruct t = new TestStruct();
    public int Int;
    public float Float;
    public object Object;
}

class TestClass
{
    public static int StaticInt = 10;
    public static Object[] StaticArr = new Object[10];

    public string String;
    public TestClass Object;
    public TestStruct Struct;

    public TestClass(string Name)
    {
        String = Name;
        Object = this;
        Struct.Int = 10;
        Struct.Float = 5.0F;
        Struct.Object = "123";
    }
}

class TestClass1
{
    public static int StaticInt = 20;
}

class Program
{
    static int Main()
    {
        TestClass t = new TestClass("Test");
        TestClass1 t1 = new TestClass1();
        TestEnum e = TestEnum.B;
        TestStruct s = TestStruct.t;
        s.Int = (int)e;
        int v = TestClass.StaticInt;
        int v1 = TestClass1.StaticInt;
        int[] arr = new int[] {1, 2, 3, 4};
        int[,] arr2 = new int[,] {{1, 2}, {3, 4}};

        Console.WriteLine("Test " + t.String);

        return 0;
    }
}

Result:
$ gdb -q /media/kbaladurin/data/dotnet/forked/corert/tests/src/Simple/BasicThreading/bin/Debug/x64/native/BasicThreadingReading symbols from /media/kbaladurin/data/dotnet/forked/corert/tests/src/Simple/BasicThreading/bin/Debug/x64/native/BasicThreading...done.
(gdb) b BasicThreading.cs:65
Breakpoint 1 at 0x5f8daf: file /media/kbaladurin/data/dotnet/forked/corert/tests/src/Simple/BasicThreading/BasicThreading.cs, line 65.
(gdb) r
Starting program: /media/kbaladurin/data/dotnet/forked/corert/tests/src/Simple/BasicThreading/bin/Debug/x64/native/BasicThreading
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffd9be1700 (LWP 28767)]

Thread 1 "BasicThreading" hit Breakpoint 1, BasicThreading_Program__Main () at /media/kbaladurin/data/dotnet/forked/corert/tests/src/Simple/BasicThreading/BasicThreading.cs:65
65	        Console.WriteLine("Test " + t.String);
(gdb) i locals
e = {value__ = 1}
s = {Int = 1, Float = 0, Object = @0x0, static t = {Int = 0, Float = 0, Object = @0x0, static t = <same as static member of an already seen type>}}
arr = @0x7fffd9bf6e38: {<S_P_CoreLib_System_Array> = {<Object> = {m_pEEType = 15175624}, _numComponents = 4}, m_NumComponents = 4, m_Data = 0x7fffd9bf6e48}
t = @0x7fffd9bf6d10: {<Object> = {m_pEEType = 14798528}, String = @0xda8c40, Object = @0x7fffd9bf6d10, Struct = {Int = 10, Float = 5, Object = @0xd886e0, static t = {Int = 0, Float = 0, Object = @0x0,
      static t = <same as static member of an already seen type>}}, static StaticInt = 10, static StaticArr = @0x7fffd9bf6da8}
t1 = @0x7fffd9bf6d40: {<Object> = {m_pEEType = 14799024}, static StaticInt = 20}
v = 10
v1 = 20
arr2 = @0x7fffd9bf6e60: {<S_P_CoreLib_System_Array> = {<Object> = {m_pEEType = 15204472}, _numComponents = 4}, m_NumComponents = 4, m_Bounds = {2, 2}, m_Data = 0x7fffd9bf6e80}
(gdb) p t.StaticInt
$1 = 10
(gdb) p t1.StaticInt
$2 = 20
(gdb) p t.StaticArr
$3 = (__Array<Object> &) @0x7fffd9bf6da8: {<S_P_CoreLib_System_Array> = {<Object> = {m_pEEType = 15170384}, _numComponents = 10}, m_NumComponents = 10, m_Data = 0x7fffd9bf6db8}

PTAL @sandreenko @davidwrighton

@tijoytom I think maybe you can review it better.


component for canvas

What do you think about this component?

Its like something between native and https://github.com/lavrton/react-konva
Would be interesting to see something between this and react-konva that bridges the ctx methods to react components, but its another library itself that can take any ctx. That way it would work with this


[dependencies] cargo update

Motivation
Dependabot has been falling behind on update-able crates.   Bumping safe to update crates and updating the total number of prs dependabot can open.
Have you read the [Contributing Guidelines on pull requests]
Yes
Test Plan
Standard build/test
Related PRs
none

Notice that mime-guess doesn't get a duplicate, one already existed, but maybe could have converged?
mime_guess 2.0.3 (1.8.8)
mime_guess: 1.8.7 -> 1.8.8
mime_guess: 2.0.1 -> 1.8.8

@sausagee @metajack r+ please.   Thinking of bumping dependabot total open prs to 15 now -- make sure we don't miss updates in the future?

@bors-libra r+

:pushpin: Commit d4a045c has been approved by metajack

Note you can just write r? @metajack to ask for a review, and review-assign-bot will assign that person.

any objections to the 15 max on prs?

:hourglass: Testing commit d4a045c9d07dbbea77f58523405d49cf2b9734fa with merge 5f669c02ab2739043d1442ffdeb47c60c60e7b25...

any objections to the 15 max on prs?

None here.

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: metajack
Pushing 5f669c02ab2739043d1442ffdeb47c60c60e7b25 to master...


fix: temporarily disable flaky peg_outs_support_rbf

This was added recently by https://github.com/fedimint/fedimint/pull/2967
It fails like 5-10% of time. Will disable until a proper fix.

@elsirion FYI


Redirect on permission denied

When a call is made that returns an authentication error, the frontend should redirect to the login page.

Also check whether the global error handler receives a 404 redirect to login.

Newly introduced functionality will redirect to the login page in case a call to our backend fails with a 401
The redirct includes the URL to the previously visited page if and only if it was not already the login page. Hopefully this fits your needs

Apparently, the current mechanism in place is not as reliable as originally expected.


Remove need for cross-env

Hoping this works 🤞
Using CI to do some Windows testing.
Current implementation relies on #2608 but can easily be based on master

Is there a benefit to removing cross-env? Or is it just a "one less dependency" thing?

I’m still thinking about whether or not this is a good idea. The main improvement here is simplification for windows users which is the whole reason we need to use cross-env. After thinking about this though it may still prove useful.

After thinking about this more I'm gonna table it for now. I may re-open it in the future if it makes sense to do so.


Warnings when install the package

Steps to reproduce:

init a project
add as deps
like this:

{
  "name": "aaaa",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "dependencies": {
    "@tokenscript/token-negotiator": "2.7.1"
  },
  "author": "",
  "license": "ISC"
}

Got lots of warning in the console, maybe we can improv

e this by upgrading the deps.

cc @nicktaras @micwallace

Thanks @futantan.
We're currently removing WCv1 this should remove many of these warnings. With any that remain I'll create a Jira ticket for us to remove them in the next release after this up and coming major version release.

@futantan
From version 3.0.0 many of these warnings will be removed.
The WC warning is still present where we are using a lib that works for both 1 and 2 as a solution to support TKN.
I'll close this issue and address the WCv1/2 in a following release.


Tab titles display

Problem
In smaller devices the tab titles are displayed in two rows which causes the tab row to increase its height
Solution
Consider either dynamic font sizes for the titles, alternative shorter titles or simply displaying an icon instead of text
Additional context

Code of Conduct

[X] I agree to follow this project's Code of Conduct and Contributing Guidelines

@PSchmiedmayer which of the suggestions do you prefer?

I'll think about it in more detail but for now I am fine with the two lines if it happens in some edge cases on smaller screens. BP is a generally well used abbreviation for blood pressure which we could use.
I am not a huge fan of showing icons in the top segmented bar. I would rather try to find strings that are shorter. On the other hand it will be challenging so we will have two lines for multiple different locales in the future.
I can see icons only as an option for the bottom bar, especially if it's size increases with two or more lines.

The problem could arise in particular because many of the users are older and have activated larger fonts. To save space in the bottom bar, we could consider reducing "Heart Health" to "Health". As the app focuses exclusively on heart issues, this would be consistent - similar to "Medication", which is also not called "Heart Medication". This could at least partially alleviate the problem. We have to keep in mind, an entry will still be added to both the top (Symptoms) and bottom (Devices) bar. In the first step, I would then shorten Blood Pressure to BP and, if desired, also omit the Heart from Health. Would that be in your favour, @PSchmiedmayer ?

Sounds good to me! Fine with just naming it health.
I think the devices tab might move into the account settings in the top bar. We might do the same thing for iOS as well.


Users should be able to see upgrade notifications, etc., in the diagnostics view

Ambassador checks in periodically to see if upgrades are available. The diag service should show this information, rather than having it just be in the logs.

FIxed in... oh dear... 0.18.2. That was awhile ago.


General questions about using hubpress for a developer blog

What are good examples of github io developer blogs created with hubpress?
What are good examples of syntax highlighting code blocks?
Is there a way to fold / unfold larger blocks of code, e.g. show only the first n lines of a 500 line code snippet?
Is there a way for readers to subscribe to a hubpress based blog running on github io? With RSS?
Are there any tools to create / render on the fly simple diagrams and/or graphs / bar charts via ascii markup instead of messing around with actual images, i.e. complete blog article in one text file, rather than text file + image file(s)? For example, something like [1] or [2] fed by markdown text?
Thanks.
[1] http://jtblin.github.io/angular-chart.js/
[2] http://knsv.github.io/mermaid/

All good topics for the Users Guide.
I'm not a developer, but I write plenty of detailed blog posts with code
samples embedded: http://jaredmorgs.github.io
Take a look at the blog post on Javadocs I wrote: it has plenty of embedded
samples and you can view them in the blog source to see how they were
written. You can also check the Asciidoctor Users Guide for some great
examples of how to use code syntax blocks.
On wrapping code samples, I couldn't find anything obvious in the
Asciidoctor docs, but I know that in the Asciidoctor Users Guide they have
show/hide blocks. I've put a tweet out to the Asciidoctor team to see if
they can help us with that.
RSS support depends on whether @anthonny has implemented RSS in the themes.
I believe at one point he had to turn them off because they were broken.
There are ways of making text based diagrams which are transformed when
published by Asciidoctor. See
http://asciidoctor.org/docs/asciidoctor-diagram. These use PlantUML,
Graphviz, ditaa, or Shaape syntax.
Anthonny would need to add the extensions into HubPress for them to work.
On Sun, Apr 26, 2015, 07:34 Simon Hardy-Francis<EMAIL_ADDRESS>wrote:

What are good examples of github io developer blogs created with hubpress?
What are good examples of syntax highlighting code blocks?
Is there a way to fold / unfold larger blocks of code, e.g. show only the
first n lines of a 500 line code snippet?
Is there a way for readers to subscribe to a hubpress based blog running
on github io? With RSS?
Are there any tools to create / render on the fly simple diagrams and/or
graphs / bar charts via ascii markup instead of messing around with actual
images, i.e. complete blog article in one text file, rather than text file

image file(s)? For example, something like [1] or [2] fed by markdown
text?

Thanks.
[1] http://jtblin.github.io/angular-chart.js/
[2] http://knsv.github.io/mermaid/
—
Reply to this email directly or view it on GitHub
https://github.com/HubPress/hubpress.io/issues/199.

+1
I wonder mow to configure mermaid

Just doing a bit of issue maintenance (as you can see, it's well overdue on this repo 😞).
This was a general question, so I'm closing it off for now.


good news! it removes the adblock-block screen! bad news! it removes the entire video itself.

Script version
5.6
Describe the bug
video plays for roughly five seconds, before the script removes the entire video screen while the audio plays, and only reverses when the entire page is refreshed, and even then it still keeps on doing it.
Expected behavior
video plays while also blocking ads.
Screenshots
N/A
Desktop (please complete the following information):
Opera GX on windows 10
Additional context
also removes the autoplay, miniplayer and theater mode buttons.

OS: Windows 10
Browser: Firefox
Tamper Monkey Version: 5.1.1
Adblock Thing Version: 5.6
I'm getting the same thing.

fixed in PR : #4756, Lets hope the maintainers push the code changes


Publish an examlple playbook for deploying AWX on K3s

Looking over this repo, first off this looks like great content and very useful for someone like myself who does not know a lot about k3s/k8s to deploy AWX on. I was wondering though you say make changes to these config files in your instructions, which made me wonder, what about creating a jinja template instead and use ansible to create these configuration files and deploy them to k3s or at least to a repo that then something like argo could use?

@djdanielsson sounds awesome

@djdanielsson @kmf
Thank you for your ideas.
Yes, this has been considered in the past and is of course technically possible. I also know it is very helpful for users.
In fact, I have automated all deployments, including K3s, AWX, EDA Server, and Galaxy NG with Ansible for testing my guide itself in my home lab for each updates.
The concern with automating deployment with Ansible is that the build procedure becomes a black box. I want my guide to not only provide instructions to make it as easy as possible for users to get a working AWX, but also provide a role as a hands-on guide to getting started with Kubernetes, like Kubernetes 101 labs. Since knowledges and skills to use Kubernetes is a necessary part of using recent AWX.
For this reason, I am not actively accustomed to publishing the guide as a playbook, as I want to work through it, step by step, so that users know what they are doing. It may be feasible to at least provide a playbook version as sub-content, rather than replacing the guide entirely.
Any thought?

I for one fully agree with the idea of having a guide one can follow step-by-step to learn how to install k3s, etc., and I've been grateful for the effort presented.

I am not actively accustomed to publishing the guide as a playbook, as I want to work through it, step by step,

Maybe tasks in a playbook could be numbered to correspond with similarly numbered steps in the documentation. That way people reading could see how to implement in a play, and conversely, people following the playbook could refer to the numbered guide sections/steps.

I can see and understand about this being a guide to help learn and agree that if you just provide a black box that isn't as helpful. I think jpmens idea of linking the current documentation to the code could help explain everything but provide an automated solution at the same time. As for you being "just a community member" these are all open source applications, this is exactly the type of thing community members do, do not feel like you need to have some sort of position or title to be able to contribute, help others, or create solutions. The only difference between you and someone who works on the AWX team is they are getting payed to do it. I am not sure if you keep up with the AWX office hours or not but they even brought up how they were going to add some testing to try and catch some potential issues that they currently do not check for that can happen when using local storage due to how many people use your guide.

@jpmens @djdanielsson
Thanks for the input and ideas. Tying the guide to the code is indeed a good idea. I will consider if there is a room to implement something.
(Of course, I understand that this does not necessarily have to be done by me, and community members other than myself can do this in a separate repository 😃 Contributions and PRs are always welcome!)

you said you already had some code that did this, if you publish what you have already, I could try and help improve/expand it. I can try and build something from scratch but it will take longer.

Hmm, the playbooks that I already have is for testing manual procedures in my guides. So the playbooks contains following tasks:

Finding shell commands in the markdown file and extract it using regexp
Invoke extracted shell commands to imitate users' input

At this time I don't intend to make these playbooks public, because its purpose is different (testing guides v.s. deploying AWX) and it is inappropriate for deploying AWX, and several community members have already published a sort of "wrapper" for my repository.

https://github.com/antuelle78/awx-install-on-k3s
https://github.com/PC-Admin/awx-ansible
https://github.com/robertpriedl/awxOnK3s

Some community members have published some playbooks or roles differently than my guide. I don't know if these are all of that.

https://github.com/antuelle78/deploy-awx-k3s-ubuntu
https://github.com/zigford/awx-operator-k3s-vagrant
https://github.com/SOSETH/awx
https://github.com/daljitdokal/raspberry-pi-ubuntu-server-k3s-awx-ansible-automated-setup

I had embedded hidden comments that indicate code blocks in my guides, e.g.: https://github.com/kurokobo/awx-on-k3s/blame/main/README.md#L177
In fact, my (private) playbooks uses these hidden comments to extract commands from markdown files, to imitate manual procedure.
However, it is not appropriate to use this embedded comment for deployment purposes, since the mkdir command, for example, should use the ansible.builtin.file module.

I'm still fairly new to kubernetes, I was going to post a new thread but honestly, I think this probably belongs here, i know it isn't a playbook, but since i don't remember seeing a flavor specified in this thread I didn't want to make a playbook out of it.  I'm using almalinux, and installing this to get AWX up and running requires a few extra steps.  I will leave updating the readme up to a current contributor, you are more than welcome to take credit for my suggestions if that stuff matters to you.  I don't know if this applies to other flavors, but from a fresh almalinux install, it does. Some of the steps i am going to post are already in the current readme.  I used chatgpt 40 to help me research the steps but I can confirm they work.
install from repo to keep updated easily
sudo tee /etc/yum.repos.d/kubernetes.repo <<EOF
[kubernetes]
name=Kubernetes
baseurl=https://pkgs.k8s.io/core:/stable:/v1.28/rpm/
enabled=1
gpgcheck=1
gpgkey=https://pkgs.k8s.io/core:/stable:/v1.28/rpm/repodata/repomd.xml.key
exclude=kubelet kubeadm kubectl cri-tools kubernetes-cni
EOF
sudo dnf install -y kubelet kubeadm kubectl --disableexcludes=kubernetes
sudo systemctl enable --now kubelet
Make sure firewall is updated
https://docs.k3s.io/installation/requirements?os=rhel#operating-systems
Check and make sure ~/.kube/config exists, else follow...
mkdir -p ~/.kube
sudo cp /etc/rancher/k3s/k3s.yaml ~/.kube/config
sudo chown $(id -u):$(id -g) ~/.kube/config
install k3s
from repo https://github.com/kurokobo/awx-on-k3s
curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION=v1.29.4+k3s1 sh -s - --write-kubeconfig-mode 644
install operator.  update version to latest version
cd ~
git clone https://github.com/kurokobo/awx-on-k3s.git
cd awx-on-k3s
git checkout 2.17.0
kubectl apply -k operator

@davidmacdonald80
Hi, you are probably being misled by ChatGPT. I don't see the need to install kubelet, kubeadm and kubectl before installing K3s, since they are bundled with K3s. Also creating ~/.kube/config is also not necessary as long as you use kubectl bundled with K3s.


Feature/old scene cleanup

Ready for review.
This removes the old microsplat stuff and the obsolete scenes/code that are no longer maintained and used. It should have no effects on full-feature-2, but if I accidentally removed something that is in use, you'd see errors and breakage.

One more thing, if testing this you need to go to scene/loadingscene, delete the loadingscene1 stuff, and rename the 2 and 3 stuff to 1 and 2 respectively. This is because the loadingscene1 files used to be for ff1, which is now gone, moving the numbers down for everything after it.

Another idea on water level. Maybe we can place a script on the top level "Water" container that goes through all the meshes and selects the highest water level.


fix(rebuild): Rebuilding lib

:tada: This PR is included in version 3.4.1 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


snapshot_load_compiled_code does not verify snapshot size

While jerry_exec_snapshot does receive (a param #2) the length of the snapshot buffer, it does not pass it to snapshot_load_compiled_code, which is prone to unsupported snapshot contents (i.e.: corrupt file, snapshot generated by different jerry version etc.).
This has been observed in practice, crashing TizenRT platform (offset being ~20MB, with largest snapshot included smaller than 5kB).

The version number is checked by Jerry, but no other attempt is made to validate the snapshot. This is intentional, since many environment guarantees a valid snapshot data, and extra checks would be a considerable performance overhead.
Perhaps the simplest solution would be adding some CRC check to your platform. At some point we could think about adding a validating system to jerry utils, but that is a considerable work. You need to validate each byte code operation one by-one, all stack operation one-by-one, all arguments one-by-one. I saw the validating system of action script before, and that is a huge project.

Would it be possible to have such mechanism only for debug build? It would be easier to catch some errors. Additionally since snapshot format depends on compile flags, maybe it would be good to verify such things? Simple few ints comparison.

It does not depend on compile flags anymore. That was a bad idea.
What are you trying to do exactly?

Erm, what do you mean by anymore?
Last I tried I had snapshot generated by host jerry (with 16 bit compressed
pointers, due to jerry heap used).
On arm target, where I used system allocator, the build scripts silently
force 32bit compressed pointers that happen to be stored in a snapshot.
I guess I do not have to tell what the results were..
On Wed, May 17, 2017 at 1:50 PM, Zoltan Herczeg<EMAIL_ADDRESS>wrote:

It does not depend on compile flags anymore. That was a bad idea.
What are you trying to do exactly?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jerryscript-project/jerryscript/issues/1741#issuecomment-302066614,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJFfnPKEodhmKJyxVTLuMTw5c7mVrIFtks5r6t8AgaJpZM4NAKTM
.

I thought you were talking about the debugger byte codes. Yes, compressed pointer size affects snapshots. We could add a configuration word besides version to check such features. Is that ok for you?

TLDR; yes, we need snapshot compatibility validation.
CPTRS are both int the snapshot file, and their length depends on compile
flags.
Proper solution would be to decouple the snapshot format (device
independent would be really great) from in-memory format (this one can be
whatever).
In the lack of such solution we'd like to be able to at least detect such
mismatches when accessing (loading) compiled snapshot.
TIA
Tomasz Wozniak
On Wed, May 17, 2017 at 3:07 PM, Zoltan Herczeg<EMAIL_ADDRESS>wrote:

I thought you were talking about the debugger byte codes. Yes, compressed
pointer size affects snapshots. We could add a configuration word besides
version to check such features. Is that ok for you?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jerryscript-project/jerryscript/issues/1741#issuecomment-302084334,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJFfnCKV69D1F12sZSbzA4nB7fyIC5d7ks5r6vEcgaJpZM4NAKTM
.


RL backtest pipeline on 5-min data

Description

Motivation and Context

How Has This Been Tested?

[ ] Pass the test by running: pytest qlib/tests/test_all_pipeline.py under upper directory of qlib.
[ ] If you are adding a new feature, test on your own test scripts.

Screenshots of Test Results (if appropriate):

Pipeline test:
Your own tests:

Types of changes

[ ] Fix bugs
[ ] Add new feature
[ ] Update documentation

Please fix the CI error


Support older browsers

Followup to #66  to add support for older browsers (https://caniuse.com/#feat=arrow-functions)

Template literals as well, if supporting IE11: https://caniuse.com/#feat=template-literals
Would be great to have analytics stats on this. I know on our websites we typically drop support for browsers that are at or below 2%-3% market share (just to save on dev resources).

Related to #66
Site renders fine with:

Microsoft Edge 80.0.xyz/Windows 10

Filters:

"Zip Code": works
"City, State": works
"Use my location": does not work
"Use my location": option disappears after one clicks on it
"State": works
"By Accepted Items": works

Tested with Microsoft Edge 80.0.xyz/Windows 10

Keep in mind that IE and older Edge will be overrepped in healthcare. I have seen Win95 in hospitals when there as a patient, even in tech-centric Seattle.

Putting the same caveat as @r-pop - Healthcare workers will be on more archaic systems. However, as long as they can go to to the site and fill out the form their main use case will be handled.

Here are the browser stats. I was noticing some patterns changing (for example desktop usage going up) so please access GA for the latest stats:
Chrome version stats:

Safari stats (what is 604???):

Firefox stats:

Edge stats:

IE stats:

So the only common browsers that look weird to me are:

Safari 604
Edge 18

I'm not familiar with either of those browsers. Are they modern?

@r-pop that may be true (I actually expect that too), interestingly enough the analytics doesn't reflect that. It's possible that there are factors skewing it away from what we expect! In fact, this could be a hint that there are deeper issues, e.g.

Maybe they're encountering fatal JS errors which are preventing Google Analytics from loading, skewing the stats.
Maybe they have security software that is filtering it out (unlikely, but feasible, as some may have interstitial proxies, would require that they intercept SSL connections and install root CA certificate on browsers, which some corps do but usually they don't MiTM their own browsers)

I'm leaning toward #1; do you have server logs that you can check? Go oldschool and run something likw AwStats which can analyze server logs to determine more accurately the amount of old browsers your seeing, in case the newfangled arrow functions and module expressions are causing JS to terminate early, resulting in failed analytics (note that the <noscript> will still fail to fire since that can only happen if JS is actually disabled).


add ping v4 & traceroute v4 (ICMP) utilities

traceroute relies on ICMP, and not UDP.

Rebase, but switched back to draft, as I need to get the proper source IP address to emit the ICMP echo request, and not the default.

On PTO til next week, will update the branch as soon as I get back.

Looking at last PR, patch 4 should be squashed in patch 3, since it is the introduction of ttl field in ip_local_mbuf_data that triggers this compilation issue.


How to infer 6000x4000 images?

I tried to use Retinexformer model to infer one  6000x4000 image but got Out Of Memory (A100 40G). Could you share how to do 6000x4000 image inference? (maybe need crop?)

Hi, thanks for your interests,
My suggestion is:
(i) Use a GPU with 48G memory to execute our code to infer 6k x 4k images.
or
(ii) You can modify this part of code to split the image into three part:

你好，我的显卡是24g的3090，好奇这种分割为n part的方式即等同于下采样吗

可以这么理解，但又并不完全是，这种拆分方式能让最后平凑的图片没有明显的明暗边界，语义上更为连续


Improve ProductTitle Accessibility

Background
I've been working on a Jest/RTL accessibility test suite for FastStore's UI components. This issue isn't a bug in the sense that the component is "broken" -- it just doesn't meet the WCAG standards.
Describe the bug
The <p> tag on line 60 of the ProductTitle component currently contains both a <div> and a <ul> as children/descendants; this is not semantically correct.
        {(refNumber || ratingValue) && (
          <p data-fs-product-title-addendum>
            {ratingValue && <Rating value={ratingValue} />}
            {refNumber && (
              <>
                {refTag} {refNumber}
              </>
            )}
          </p>
        )}

Possible Solution
The <p> tag on line 60 needs to be changed to a <div>.
Additional context
To see the error, you can check out my tests PR branch in the demoHearst repo and run the following command in the console:
yarn test-jest src/components/molecules/producttitle

If you'd like to print the component's DOM tree in the console, you can pull down the RTL-test-examples branch, and then use the screen.debug() command in the ProductTitle test:

The DOM looks like this (note that I cut on the bottom of the DOM tree because the screenshot was so long):

Hi @hahnwhitney, thanks for reporting this issue in such detail, it's really helpful ✨
We created an internal task and will fix it soon.

Done! 💯


Exposure a p2p interface to classes implementing orbit-db-store

This proposal is a system that allows stores to create custom p2p channels to other peers connected to the same store.
Below is a hypothetical model. Note all p2p traffic is over IPFS pubsub
Definitions:

Asking peer: The peer initializing the connection
Responding peer: The peer responding to the initiation.
The network: Cloud of peers all interconnected focusing on the
Broadcast channel: Single pubsub channel representing the data store.
Application specific API: Interface that is diagrammed by higher level code implementing orbit-db-store

Asking peer joins store broadcast channel. (Example: Asking peer is just starting up and gets connected to the network)
Responding peer broadcasts a small message to all the other peers containing information regarding what diagrams/protocol it supports. Including Public key for encryption, if needed, and a forwarding pubsub channel ID (a channel where asking peers can send messages directly to the responding peer, derived from the peerId). The forwarding channel isn't designed to be a back and forth between a responding peer and an asking peer.  Only a temporary channel for negotiating a direct peer-to-peer connection.
Asking peer sends an establishment request to the forwarding channel, containing the necessary information to determine a direct p2p channel ID.
In the newly created pubsub channel, protocol handshakes are done, encryption is established, exchange of supported p2p application specific API calls, Secondary application specific handshakes completed. The rest of the process is diagrammed by the application specific API.

What does this accomplish
By exposing a some type of peer to peer API to store types. Stores can implement custom authentication methods, and side channel-non essential actions not using the oplog.
The following is possible.

Secondary level authentication via oauth2 or other abstract non-cryptographically verifiable authentication. Ultimately tying into the normal orbit-db access controller.
Running store specific queries through other peers in the network (Future project: Store Sharding)

Further discussion and comments is appreciated.

@vaultec81 can you make this a PR and designate it SCP-002?