"Runner quit unexpectedly" when trying to run on iOS simulator

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

Run flutter run

Actual results

Logs
The logs for flutter run -v are too large so I pasted them on this link https://rentry.co/maikerios
Flutter Doctor output

Doctor output
[flutter] flutter doctor -v
[!] Flutter (Channel stable, 3.13.8, on macOS 14.0 23A344 darwin-arm64, locale en-US)
    • Flutter version 3.13.8 on channel stable at /Users/mudassirchapra/.puro/envs/main/flutter
    ! Warning: `flutter` on your path resolves to /Users/mudassirchapra/development/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/mudassirchapra/.puro/envs/main/flutter. Consider adding /Users/mudassirchapra/.puro/envs/main/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/mudassirchapra/development/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/mudassirchapra/.puro/envs/main/flutter. Consider adding /Users/mudassirchapra/.puro/envs/main/flutter/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 6c4930c4ac (21 hours ago), 2023-10-18 10:57:55 -0500
    • Engine revision 767d8c75e8
    • Dart version 3.1.4
    • DevTools version 2.25.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/mudassirchapra/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

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

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

[✓] Android Studio (version 2022.3)
    • 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 17.0.6+0-17.0.6b829.9-10027231)

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

[✓] Connected device (3 available)
    • iPhone 15 Pro Max (mobile) • 27EF2784-5553-4169-ABB4-5EB05010FC75 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-17-0 (simulator)
    • macOS (desktop)            • macos                                • darwin-arm64   • macOS 14.0 23A344 darwin-arm64
    • Chrome (web)               • chrome                               • web-javascript • Google Chrome 118.0.5993.70
    ! Error: Browsing on the local area network for Mudassir's iPad (2). Ensure the device is unlocked and attached with a cable or associated with the same local area network as this Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code -27)

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

Hi @muddi900 . Thanks for filing this. Does this only happen when running flutter run?
Can you try running from XCode to see if this reproduces there as well?
Also, how ofter do you get this error?
And on what simulator iOS version does this occur?

@dam-ease It occurs with xcode build as well.

Thanks for checking this and responding.
From the logs you shared, I see the error might be occurring at:

Error: Browsing on the local area network for Mudassir's iPad (2). Ensure the device is unlocked and attached with a cable or associated with the same local area network as this Mac.
The device must be opted into Developer Mode to connect wirelessly. (code -27)

Can you try disconnecting the device and running specifically on the simulator with flutter run -v -d 27EF2784-5553-4169-ABB4-5EB05010FC75?
I'm unable to reproduce this on my end but it'll be helpful if you could also try with a native iOS project to see if this reproduces with that as well.

I removed the physical device and ran flutter run -v -d 809229CB-CE2C-4C18-990F-C788583A6448. I got a new error this time.
[  +68 ms] Failed to build iOS app
[   +1 ms] Error (Xcode): Failed to launch AssetCatalogSimulatorAgent via CoreSimulator spawn
           /Users/mudassirchapra/src/maiker/ios/Pods/DKPhotoGallery/DKPhotoGallery/Resource/Resources/Images.xcassets

[   +2 ms] Could not build the application for the simulator.
[        ] Error launching application on iPhone 15 Pro.
[   +2 ms] "flutter run" took 222,408ms.
[   +2 ms]
           #0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
           #1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:760:9)
           <asynchronous suspension>
           #2      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1297:27)
           <asynchronous suspension>
           #3      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #4      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
           <asynchronous suspension>
           #5      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:339:9)
           <asynchronous suspension>
           #6      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #7      FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:285:5)
           <asynchronous suspension>
           #8      run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:115:9)
           <asynchronous suspension>
           #9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #10     main (package:flutter_tools/executable.dart:90:3)
           <asynchronous suspension>

[  +29 ms] Running 1 shutdown hook
[  +32 ms] Shutdown hooks complete
[   +1 ms] exiting with code 1

Flutter Doctor
[✓] Flutter (Channel stable, 3.13.8, on macOS 14.0 23A344 darwin-arm64, locale en-US)
    • Flutter version 3.13.8 on channel stable at /Users/mudassirchapra/.puro/envs/main/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 6c4930c4ac (3 days ago), 2023-10-18 10:57:55 -0500
    • Engine revision 767d8c75e8
    • Dart version 3.1.4
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/mudassirchapra/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

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

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

[✓] Android Studio (version 2022.3)
    • 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 17.0.6+0-17.0.6b829.9-10027231)

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

[✓] Connected device (3 available)
    • iPhone 15 Pro (mobile) • 809229CB-CE2C-4C18-990F-C788583A6448 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-17-0 (simulator)
    • macOS (desktop)        • macos                                • darwin-arm64   • macOS 14.0 23A344 darwin-arm64
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome 118.0.5993.88

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

The method I am using to capture the verbose out of run is not working. If the full output is needed, I'll run it again.

The error log made me think there was pod issue, so I ran pod install again. Tried to run the app again and I am still getting the 'runner quit unexpectedly' error. I managed to capture the verbose output correctly
maiker-flutter-run.txt
I press the Report button and copy the data
maiker-report.txt

Hi @muddi900. Thanks for providing these. I see a similar issue https://github.com/flutter/flutter/issues/135208 and was mentioned here https://github.com/flutter/flutter/issues/135442#issue-1911923527 and per the later issue has been fixed. Are you able to check this on the master channel to see if this issue still persists?

I try to check on the master channel, but I need it to work on the stable, since I want it to be published soon.

So I tried the master branch
Flutter Doctor
[flutter] flutter doctor -v
[!] Flutter (Channel [user-branch], 3.16.0-15.0.pre.72, on macOS 14.0 23A344 darwin-arm64, locale en-US)
    ! Flutter version 3.16.0-15.0.pre.72 on channel [user-branch] at /Users/mudassirchapra/.puro/envs/master_env/flutter
      Currently on an unknown channel. Run `flutter channel` to switch to an official channel.
      If that doesn't fix the issue, reinstall Flutter by following instructions at https://flutter.dev/docs/get-started/install.
    ! Warning: `flutter` on your path resolves to /Users/mudassirchapra/.puro/envs/main/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/mudassirchapra/.puro/envs/master_env/flutter. Consider adding /Users/mudassirchapra/.puro/envs/master_env/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/mudassirchapra/.puro/envs/main/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/mudassirchapra/.puro/envs/master_env/flutter. Consider adding /Users/mudassirchapra/.puro/envs/master_env/flutter/bin to the front of your path.
    ! Upstream repository unknown source is not a standard remote.
      Set environment variable "FLUTTER_GIT_URL" to unknown source to dismiss this error.
    • Framework revision dc78bf669d (9 minutes ago), 2023-10-24 02:56:50 -0400
    • Engine revision 2a8471f188
    • Dart version 3.3.0 (build 3.3.0-53.0.dev)
    • DevTools version 2.28.1
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/mudassirchapra/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

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

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

[✓] Android Studio (version 2022.3)
    • 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 17.0.6+0-17.0.6b829.9-10027231)

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

[✓] Connected device (3 available)
    • iPhone 15 Pro (mobile) • 809229CB-CE2C-4C18-990F-C788583A6448 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-17-0 (simulator)
    • macOS (desktop)        • macos                                • darwin-arm64   • macOS 14.0 23A344 darwin-arm64
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome 118.0.5993.88

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

Got the same issue. Here's the verbose output:
maiker-flutter-run.txt
And the report text from the crash dialog.
maiker-report.txt

Hi @muddi900. Thanks for your response and patience.
Looking through the crash report, it seems like an issue with Dart
0   Flutter                       	       0x11b342fe8 dart::kernel::Reader::ReadLineStartsData(long) + 80
1   Flutter                       	       0x11b5a08f4 dart::kernel::KernelReaderHelper::GetLineStartsFor(long) + 408
2   Flutter                       	       0x11b3470ec dart::kernel::KernelLoader::LoadEntireProgram(dart::kernel::Program*, bool) + 1032
3   Flutter                       	       0x11b62cdb4 dart::LoadLibrary(dart::Thread*, dart::ExternalTypedData const&) + 64
4   Flutter                       	       0x11b62cc50 Dart_LoadLibraryFromKernel + 352
5   Flutter                       	       0x11b2a73d0 flutter::DartIsolate::LoadKernel(std::_LIBCPP_ABI_NAMESPACE::shared_ptr<fml::Mapping const> const&, bool) + 200
6   Flutter                       	       0x11b2a74fc flutter::DartIsolate::PrepareForRunningFromKernel(std::_LIBCPP_ABI_NAMESPACE::shared_ptr<fml::Mapping const> const&, bool, bool) + 236
7   Flutter                       	       0x11b2afe2c flutter::KernelIsolateConfiguration::DoPrepareIsolate(flutter::DartIsolate&) + 116

Can you try creating a new Flutter project and running the Flutter simple project to see if this occurs with it as well?
Also, could you try running the app on another iOS version so we could label it appropriately?

Thank you!

The simple project works:
maiker-flutter-run-test.txt

I was making a mistake in my real project. I was not passing the --dart-define-from-file that is required to run the app.
I still had the same issue, but this time, I got an error message:
[ +236 ms] Launching a Dart Developer Service (DDS) instance at http://<IP_ADDRESS>:0, connecting to VM service at http://<IP_ADDRESS>:51004/rhCFqhH9n00=/.
[ +187 ms] Warning: Failed to start DDS: Failed to start Dart Development Service
[        ] Fail to connect to service protocol: http://<IP_ADDRESS>:51004/rhCFqhH9n00=/: DartDevelopmentServiceException: Failed to start Dart Development Service
[        ] Error connecting to the service protocol: failed to connect to http://<IP_ADDRESS>:51004/rhCFqhH9n00=/
[   +5 ms] "flutter run" took 705,751ms.
[  +23 ms]
           #0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
           #1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:760:9)
           <asynchronous suspension>
           #2      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1297:27)
           <asynchronous suspension>
           #3      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #4      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
           <asynchronous suspension>
           #5      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:339:9)
           <asynchronous suspension>
           #6      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #7      FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:285:5)
           <asynchronous suspension>
           #8      run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:115:9)
           <asynchronous suspension>
           #9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #10     main (package:flutter_tools/executable.dart:90:3)
           <asynchronous suspension>

Thanks for your response. Seeing that the crash doesn't occur with the sample Flutter project.
We would need a minimal complete reproducible code sample that doesn’t include 3rd party plugins or complex production code for this issue to be workable.
This issue could also be caused by one of your plugins, so you can probably start your investigation from there.
Thank you

I tried running on iOS 16.4 emulator and got the same error.
[✓] Connected device (3 available)
    • iPhone 14 Pro (mobile) • CECC9192-6301-4991-B148-75144438B0CC • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-4 (simulator)
    • macOS (desktop)        • macos                                • darwin-arm64   • macOS 14.0 23A344 darwin-arm64
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome 118.0.5993.88

I am guessing the issue is a package. How do I figure out which one?

There was an issue with the google_mobile_ads package. A value in Info.plist was incorrect, and the error was not handled by the package, which caused a SIGABRT. I will file the issue with the appropriate repo. @dam-ease Thank you for your support. I am closing the issue.

Can you tell me how you solved it? i have the same  error and using google_mobile_ads dependency.
Error : "Runner quit unexpectedly" when trying to run on iOS simulator

The app id in the Info.plist was incorrect.
On Sun, Oct 29, 2023, 12:19 AM Kashif Asghar @.***>
wrote:

There was an issue with the google_mobile_ads package. A value in
Info.plist was incorrect, and the error was not handled by the package,
which caused a SIGABRT. I will file the issue with the appropriate repo.
@dam-ease https://github.com/dam-ease Thank you for your support. I am
closing the issue.
Can you tell me how you solved it? i have the same error and using
google_mobile_ads dependency.
Error : "Runner quit unexpectedly" when trying to run on iOS simulator
—
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/136889#issuecomment-1783902148,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI2VVZQ2ZVL2RUNTNQ5RKH3YBVLFDAVCNFSM6AAAAAA6HGI6LCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBTHEYDEMJUHA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


Concurrency issue: crash on changing instrument

The problem is as follows:

change instrument
the DSP invokes FilePool::triggerGarbageCollection on the old files
some of these files are still streaming, their memory block is freed and they write invalid memory
crash with report.txt.gz

very easily reproduced with a timer that changes loaded instrument every tick
stress.patch.gz
It's difficult to find a quick fix to this one, it's more than tempting to revert the loader to pre-0.5.0.

I'll have time tonight to look into this. I think the "nice" behavior in this case would actually be to keep the file and the voice streaming on instrument change to avoid sound cutoffs, but it probably will not be a simple machinery to implement.


Add default support for scrolling with the mouse wheel.

Also changes the scrollback() function so that the amount to scroll
can be configured as a fraction of the screen height.
This fixes #103.

Hi, I'm a long time dvtm user. Just wanted to note that this patch seems to be working properly and I'm very happy with the feature, although I don't know about the implementation details. Thank you @ccrusius !

I have also tried this patch and it seems to work very well. Thanks a lot @ccrusius !

Shameless plug for a4 https://a4term.com which is a rewrite of dvtm and implements configurable scrolling with the mouse wheel by default. You can specify a number of lines to scroll (with an integer) or a percentage of a screen (with a decimal number). You can scroll whichever window the mouse is hovering over, not just the selected window. You can also use the mouse for additional configurable actions by clicking on a tag in the status bar, the layout symbol, and more. End of shameless plug.


Merge pull request #1 from bvaughn/master

update
Thanks for contributing to react-virtualized!
Before submitting a pull request, please complete the following checklist:

[ ] The existing test suites (npm test) all pass
[ ] For any new features or bug fixes, both positive and negative test cases have been added
[ ] For any new features, documentation has been added
[ ] For any documentation changes, the text has been proofread and is clear to both experienced users and beginners.
[ ] Format your code with prettier (npm run prettier).
[ ] Run the Flow typechecks (npm run typecheck).

Here is a short checklist of additional things to keep in mind before submitting:

Please make sure your pull request description makes it very clear what you're trying to accomplish. If it's a bug fix, please also provide a failing test case (if possible). In either case, please add additional unit test coverage for your changes. :)
Be sure you have notifications setup so that you'll see my code review responses. (I may ask you to make some adjustments before merging.)

Codecov Report

Merging #1406 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #1406   +/-   ##
======================================
  Coverage    90.4%   90.4%
======================================
  Files          59      59
  Lines        1740    1740
======================================
  Hits         1573    1573
  Misses        167     167

Continue to review full report at Codecov.

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

Codecov Report

Merging #1406 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #1406   +/-   ##
======================================
  Coverage    90.4%   90.4%
======================================
  Files          59      59
  Lines        1740    1740
======================================
  Hits         1573    1573
  Misses        167     167

Continue to review full report at Codecov.

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


Viewdeo: new bidder code alias for gamoshi

Type of change

[X] Feature

Description of change
Added viewdeos as a new bidder code alias for gamoshi.
Thanks.

released with PBJS 2.1


Fix Bytes.bitAt to respect byte order

Closes #39. bitAt now checks byte order before locating the desired
bit.

Thanks for the PR!


Why i can't install this library?

Environment
"react-native": "0.64.2"
node js: v16.9.1
Description
Failed to install this library.

Reproducible Demo
Execute:  npm install @react-native-community/image-editor --save as mentioned on the docs

@mppperez for now i install it using --force

I tried --force. The installation runs globally but I still get errors when running the program saying "unable to resolve module @react-native-community/image-editor"

fix: https://github.com/callstack/react-native-image-editor/pull/125
also will be release soon


introducing Azure IoT Edge Solution dev-container

Thanks for opening! Is there a reason you're introducing a separate library-scripts/docker-in-docker-debian.sh rather than referencing the one included in the repo?


How to manually type the vtables?

My case is (simplified and abstracted) as follows... The source code likely declares a base class and 2 derived classes in the following manner:
class Base {
    virtual ~Base() {};
    virtual void impl(/* args */) = 0;
};

class FirstChild: public Base {
    virtual ~FirstChild() {};
    virtual void impl(/* args */) {
        this->func(/* args */);
    }
    virtual void func(/* args */) { ... }

    /* fields */
};
class SecondChild: public Base {
    virtual ~SecondChild() {};
    virtual void impl(/* args */) {
        this->func(/* args */);
    }
    virtual void another() { ... }
    virtual void func(/* args */) { ... }

    /* fields */
};

The vtables are (I trimmed the RTTI because it's unavailable):
-----------------------------------------------------------------------------------
0x0:  Base::~Base;
0x4:  nullptr; // pure virtual function with no implementation
-----------------------------------------------------------------------------------
0x0:  FirstChild::~FirstChild;
0x4:  FirstChild::impl; // derived class introduces the implementation
0x8:  FirstChild::func;
-----------------------------------------------------------------------------------
0x0:  SecondChild::~SecondChild;
0x4:  SecondChild::impl; // derived class introduces the implementation
0x8:  SecondChild::another;
0x10: SecondChild::func;
-----------------------------------------------------------------------------------

Next... I've got a struct Holder that contains a pointer to some instance of the derived class. Like, it is sometimes assigned a FirstChild's address and sometimes it's the SecondChild's.
Now the questions...

I wanted to type the field as Base*. Then Base would be
struct Base {
    BaseVtable* vtable;
};

The question is... what's BaseVtable then? I guess, it should look like this:
struct BaseVtable {
    ??? dtor;
    ??? impl;
};

...but I don't know what types to use for the entries. I could use void*, but that erases the info about the arguments => theoretically Ghidra might show
(**(code**)holder->instance->vtable->impl)();

instead of
(**(code**)holder->instance->vtable->impl)(holder->instance, /* args */);

The latter is definitely better => how to type the entries?

Even if we manage to propagate the types into the BaseVtable, what are supposed to do with the derived vtbales?
struct FirstChild {
    FirstChildVtable* vtable;
    /* fields */
};

... and then
struct FirstChildVtable {
    ??? dtor;
    ??? impl;
    ??? func;
}

Assuming we don't use void* for the entries, it looks like there is just no way to type that... Because we can no longer do this:
void FirstChild_impl(FirstChild* this, /* args */);

We are forced to do
void FirstChild_impl(Base* this, /* args */);

... but that doesn't work, because the BaseVtable doesn't have the entry for FirstChild::func
Maybe I'm just confused and I must use void* for the functions, tell me if that's so, please.

have you tried using a union of vftables and then manually selecting the vftable type based on the target?  that seems to be what you are trying to go for here?

You might also want to take a look at #516 which deals with the general topic of vtables. Maybe you can find some inspiration over there.


Only 5 pins appear on iPhone 12 pro max, even if pinLength is 6

I am using pinView for otp in one of my application, On simulator of iphone12 Pro Max it just shows five pin TexField instead of 6.

anyupdate on this?

i have fixed issue by just changing hight of the SVPinview, which you added in view, earlier it was, 65 not i changed to 60 and it worked


Increase a value of PCIE_ECAP_ID_END macro.

PCIE_ECAP_ID_END is defined as  0x29
https://github.com/ARM-software/bsa-acs/blob/726b990213b17fe466b9c53d751c0f5c11c16c60/test_pool/pcie/operating_system/test_os_p009.c#L28
However according to "PCI Code and ID Assignment Specification Revision 1.11" values up to 0x2C are allowed.

Hi @semihalf-bernacki-grzegorz,
Thanks for raising the issue, we will check at our side.
Regards,
ACS team

Hi @semihalf-bernacki-grzegorz,
This issue has been fixed as part of the PR: https://github.com/ARM-software/bsa-acs/pull/60
Regards,
Gowtham,
ACS Team


LibWeb: Ensure requests modules is not empty before indexing into it

Fixes: #2676
Regression from 5af613aa657ebc03b93891c955f4ee62eaef7e53

Also, check https://donorbox.org/ladybird

Now with a regression test, I am somewhat suspicious that there is a spec issue for this though 🤔


Build fails when Web Worker dynamically imports module also dynamically imported by the main thread

Describe the bug
I have created a Web Worker with type: module that dynamically imports a module shared with the main thread. In dev mode this works as expected, but when building I get (full logs below)
rendering chunks (2)...The emitted file "assets/logger.c9021ab8.js" overwrites a previously emitted file of the same name.
[vite:build-import-analysis] Cannot read property 'importedCss' of undefined

Reproduction
git clone https://github.com/esturcke/web-worker-dynamic-import-error
cd web-worker-dynamic-import-error
yarn && yarn build

System Info
System:
    OS: macOS 12.5.1
    CPU: (10) x64 Apple M1 Pro
    Memory: 33.20 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 14.19.1 - ~/Library/Caches/fnm_multishells/39357_1662750145123/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 6.14.16 - ~/Library/Caches/fnm_multishells/39357_1662750145123/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 105.0.5195.102
    Chrome Canary: 107.0.5290.0
    Edge: 105.0.1343.33
    Firefox Developer Edition: 105.0
    Safari: 15.6.1
    Safari Technology Preview: 16.0
  npmPackages:
    vite: ^3.1.0 => 3.1.0

Used Package Manager
yarn
Logs

Click to expand!
❯ yarn build --debug
yarn run v1.22.19
$ tsc && vite build --debug
  vite:config bundled config file loaded in 85.98ms +0ms
  vite:esbuild init tsconfck (root: /Users/esturcke/work/web-worker-dynamic-import-error) +0ms
  vite:esbuild init tsconfck (root: /Users/esturcke/work/web-worker-dynamic-import-error) +1ms
  vite:esbuild init tsconfck (root: /Users/esturcke/work/web-worker-dynamic-import-error) +1ms
  vite:esbuild init tsconfck (root: /Users/esturcke/work/web-worker-dynamic-import-error) +0ms
  vite:esbuild init tsconfck end +1ms
  vite:esbuild init tsconfck end +0ms
  vite:esbuild init tsconfck end +0ms
  vite:esbuild init tsconfck end +0ms
  vite:config using resolved config: {
  vite:config   worker: {
  vite:config     format: 'es',
  vite:config     plugins: [
  vite:config       'vite:build-metadata',
  vite:config       'vite:pre-alias',
  vite:config       'alias',
  vite:config       'vite:modulepreload-polyfill',
  vite:config       'vite:resolve',
  vite:config       'vite:html-inline-proxy',
  vite:config       'vite:css',
  vite:config       'vite:esbuild',
  vite:config       'vite:json',
  vite:config       'vite:wasm-helper',
  vite:config       'vite:worker',
  vite:config       'vite:asset',
  vite:config       'vite:wasm-fallback',
  vite:config       'vite:define',
  vite:config       'vite:css-post',
  vite:config       'vite:build-html',
  vite:config       'vite:worker-import-meta-url',
  vite:config       'vite:force-systemjs-wrap-complete',
  vite:config       'vite:watch-package-data',
  vite:config       'commonjs',
  vite:config       'vite:data-uri',
  vite:config       'vite:asset-import-meta-url',
  vite:config       'vite:dynamic-import-vars',
  vite:config       'vite:import-glob',
  vite:config       'vite:build-import-analysis',
  vite:config       'vite:esbuild-transpile',
  vite:config       'vite:terser',
  vite:config       'vite:reporter',
  vite:config       'vite:load-fallback'
  vite:config     ],
  vite:config     rollupOptions: {},
  vite:config     getSortedPlugins: [Function: getSortedPlugins],
  vite:config     getSortedPluginHooks: [Function: getSortedPluginHooks]
  vite:config   },
  vite:config   optimizeDeps: {
  vite:config     disabled: 'build',
  vite:config     force: undefined,
  vite:config     esbuildOptions: { preserveSymlinks: undefined }
  vite:config   },
  vite:config   build: {
  vite:config     target: [ 'es2020', 'edge88', 'firefox78', 'chrome87', 'safari13' ],
  vite:config     polyfillModulePreload: true,
  vite:config     outDir: 'dist',
  vite:config     assetsDir: 'assets',
  vite:config     assetsInlineLimit: 4096,
  vite:config     cssCodeSplit: true,
  vite:config     cssTarget: [ 'es2020', 'edge88', 'firefox78', 'chrome87', 'safari13' ],
  vite:config     sourcemap: false,
  vite:config     rollupOptions: {},
  vite:config     minify: 'esbuild',
  vite:config     terserOptions: {},
  vite:config     write: true,
  vite:config     emptyOutDir: null,
  vite:config     manifest: false,
  vite:config     lib: false,
  vite:config     ssr: false,
  vite:config     ssrManifest: false,
  vite:config     reportCompressedSize: true,
  vite:config     chunkSizeWarningLimit: 500,
  vite:config     watch: null,
  vite:config     commonjsOptions: { include: [Array], extensions: [Array] },
  vite:config     dynamicImportVarsOptions: { warnOnError: true, exclude: [Array] }
  vite:config   },
  vite:config   configFile: '/Users/esturcke/work/web-worker-dynamic-import-error/vite.config.ts',
  vite:config   configFileDependencies: [
  vite:config     '/Users/esturcke/work/web-worker-dynamic-import-error/vite.config.ts'
  vite:config   ],
  vite:config   inlineConfig: {
  vite:config     root: undefined,
  vite:config     base: undefined,
  vite:config     mode: undefined,
  vite:config     configFile: undefined,
  vite:config     logLevel: undefined,
  vite:config     clearScreen: undefined,
  vite:config     optimizeDeps: { force: undefined },
  vite:config     build: {}
  vite:config   },
  vite:config   root: '/Users/esturcke/work/web-worker-dynamic-import-error',
  vite:config   base: '/',
  vite:config   resolve: { alias: [ [Object], [Object] ] },
  vite:config   publicDir: '/Users/esturcke/work/web-worker-dynamic-import-error/public',
  vite:config   cacheDir: '/Users/esturcke/work/web-worker-dynamic-import-error/node_modules/.vite',
  vite:config   command: 'build',
  vite:config   mode: 'production',
  vite:config   ssr: {
  vite:config     format: 'esm',
  vite:config     target: 'node',
  vite:config     optimizeDeps: { disabled: true, esbuildOptions: [Object] }
  vite:config   },
  vite:config   isWorker: false,
  vite:config   mainConfig: null,
  vite:config   isProduction: true,
  vite:config   plugins: [
  vite:config     'vite:build-metadata',
  vite:config     'vite:pre-alias',
  vite:config     'alias',
  vite:config     'vite:modulepreload-polyfill',
  vite:config     'vite:resolve',
  vite:config     'vite:html-inline-proxy',
  vite:config     'vite:css',
  vite:config     'vite:esbuild',
  vite:config     'vite:json',
  vite:config     'vite:wasm-helper',
  vite:config     'vite:worker',
  vite:config     'vite:asset',
  vite:config     'vite:wasm-fallback',
  vite:config     'vite:define',
  vite:config     'vite:css-post',
  vite:config     'vite:build-html',
  vite:config     'vite:worker-import-meta-url',
  vite:config     'vite:force-systemjs-wrap-complete',
  vite:config     'vite:watch-package-data',
  vite:config     'commonjs',
  vite:config     'vite:data-uri',
  vite:config     'vite:asset-import-meta-url',
  vite:config     'vite:dynamic-import-vars',
  vite:config     'vite:import-glob',
  vite:config     'vite:build-import-analysis',
  vite:config     'vite:esbuild-transpile',
  vite:config     'vite:terser',
  vite:config     'vite:reporter',
  vite:config     'vite:load-fallback'
  vite:config   ],
  vite:config   server: {
  vite:config     preTransformRequests: true,
  vite:config     middlewareMode: false,
  vite:config     fs: { strict: true, allow: [Array], deny: [Array] }
  vite:config   },
  vite:config   preview: {
  vite:config     port: undefined,
  vite:config     strictPort: undefined,
  vite:config     host: undefined,
  vite:config     https: undefined,
  vite:config     open: undefined,
  vite:config     proxy: undefined,
  vite:config     cors: undefined,
  vite:config     headers: undefined
  vite:config   },
  vite:config   env: { BASE_URL: '/', MODE: 'production', DEV: false, PROD: true },
  vite:config   assetsInclude: [Function: assetsInclude],
  vite:config   logger: {
  vite:config     hasWarned: false,
  vite:config     info: [Function: info],
  vite:config     warn: [Function: warn],
  vite:config     warnOnce: [Function: warnOnce],
  vite:config     error: [Function: error],
  vite:config     clearScreen: [Function: clearScreen],
  vite:config     hasErrorLogged: [Function: hasErrorLogged]
  vite:config   },
  vite:config   packageCache: Map(0) { set: [Function (anonymous)] },
  vite:config   createResolver: [Function: createResolver],
  vite:config   appType: 'spa',
  vite:config   experimental: { importGlobRestoreExtension: false, hmrPartialAccept: false },
  vite:config   getSortedPlugins: [Function: getSortedPlugins],
  vite:config   getSortedPluginHooks: [Function: getSortedPluginHooks]
  vite:config } +13ms
vite v3.1.0 building for production...
✓ 2 modules transformed.
✓ 8 modules transformed.
rendering chunks (2)...The emitted file "assets/logger.c9021ab8.js" overwrites a previously emitted file of the same name.
[vite:build-import-analysis] Cannot read property 'importedCss' of undefined
error during build:
TypeError: Cannot read property 'importedCss' of undefined
    at addDeps (file:///Users/esturcke/work/web-worker-dynamic-import-error/node_modules/vite/dist/node/chunks/dep-665b0112.js:43002:60)
    at Object.generateBundle (file:///Users/esturcke/work/web-worker-dynamic-import-error/node_modules/vite/dist/node/chunks/dep-665b0112.js:43024:33)
    at file:///Users/esturcke/work/web-worker-dynamic-import-error/node_modules/rollup/dist/es/shared/rollup.js:22710:40
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

For a workaround, add a module that re-exports everything from logger.ts and use it instead in worker.
// logger2.ts
export * from './logger'

// worker.ts
onmessage = e => {
    import("./logger2").then(({ log }: any) => log(`worker: ${e.data}`)) // use logger2
}

export {}

Thanks @sapphi-red, this looks like a nice workaround for direct imports. Unfortunately I ran into this while porting a project from Webpack to Vite and there are multiple dynamic imports brought in indirectly several levels deep. I'm not sure how feasible it will be to fork the entire call chain.

Also struggling with this. In my case I'm not sure how to apply the workaround. My worker is a tiny wrapper around a class:
import { MyClass } from './MyClass'
import { expose } from 'comlink'
expose(MyClass)

Inside MyClass I make a dynamic import to a JS module, and since that is an implementation detail of MyClass, and not something I do directly in the worker, I'm not sure how to apply the workaround.
@esturcke It sounds similar to your case. Could you shed any light on your approach?

Interestingly, when using worker that requires the vite react plugin both the main app & the worker i don't get any of these errors and just see that all the dependencies have been bundled twice. Once for the use inside the worker and once in the main thread.
This is the same result when using the workaround of reexporting the module suggested by @sapphi-red.
Even though this works, it increases the bundle size considerably in my case because both react and a large lib i.e. @react-pdf/renderer is getting bundled twice.

I'm having this issue, too, and I think the problem in my case is similar to @jedrichards's, and the culprit is Comlink.
Because Comlink is a node module, not a user module, @sapphi-red's trick of re-exporting it here doesn't work (at least didn't work in my test).  Although, with how Vite's advanced, the error message is different:
RollupError: [vite:worker-import-meta-url] Invalid value "iife" for option "output.format" - UMD and IIFE output formats are not supported for code-splitting builds.

My worker is {type: module} and I'm using the new Worker construct:
new Worker(new URL('$workers/db.ts', import.meta.url), {
    type: 'module',
  }),


TS is slow when parsing elixir files.

When i open a elixir file i get TS took 356ms to parse document, will be disabled for current file.
It happens with small or larger file.
is this because i'm on a m1 mac?

@connorlay Thanks for confirming! I know you already optimised the queries for performance, so not sure how much more we can do. If you have any ideas feel free to open an issue on nvim-treesitter.


May I ask if it is possible to deploy to the server?

Hello, may I encapsulate UniTalker into a Python project, deploy it to a server, and provide services for the Unreal Engine project to drive digital human mouth shapes? Sorry, my question may be more basic as I am a beginner. Thank you

Hello, may I encapsulate UniTalker into a Python project, deploy it to a server, and provide services for the Unreal Engine project to drive digital human mouth shapes? Sorry, my question may be more basic as I am a beginner. Thank you

Yes, our team have tried this and it needs some engineering knowledeges.


SEO: 500 errors on commenting system

@michellekondou 500 is fairly unhelpful error, but it's easy to see something's up with textile again:
http://alistapart.com/comments/horizdropdowns/

The problem was with code in the comments, javascript sanitizing, I corrected this http://alistapart.com/comments/horizdropdowns/ and this http://alistapart.com/comments/dynatext/ (found in webmaster tools)


Multi-line comment being stripped from generated code

Describe the bug
We create some popular developer tools (Quokka.js, Wallaby.js).
Our tools rely on code comments being correctly in code emitted by SWC.
It appears that SWC sometimes (not always) removes multi-line comment from generated code.
Input code
a() /* IMPORTANT_DO_NOT_REMOVE */ ;

Config
{
  "jsc": {
    "parser": {
      "syntax": "typescript",
      "tsx": false,
      "decorators": false,
      "dynamicImport": false
    }
  },
  "sourceMaps": true
}

Playground link
https://play.swc.rs/?version=1.2.144&code=H4sIAAAAAAAAA0vU0FTQ11Lw9A3wDwpx9AuJd%2FGP9%2FMPiQ9y9fUPc1XQ0lewBgAeBNe1IwAAAA%3D%3D&config=H4sIAAAAAAAAA0WMTQrEIAxG75K1286id5hDBCctFv9IUhgR714tlu7C915ehUMsrBUyshCPS0pU%2FMMKZAOKZZcVTNf6tKEXagYUeScdiiyd%2BZSEJjUQXHRbGSWbQmYSeRHG3T9m66GQfucYKmjJdAc%2F0N7G%2FHPynaLySe0Cj9ke9LUAAAA%3D
Expected behavior
Generated code should be:
a() /* IMPORTANT_DO_NOT_REMOVE */ ;

Actual behavior
Generated code is:
a();

Version
<EMAIL_ADDRESS>Additional context
No response

👋 I'm wallaby / quokka daily user.
We really don't have good defined behavior around comment. https://github.com/swc-project/swc/issues/2964 is one of the examples. There is internal consideration to revisit whole comment, but also it doesn't aim to fix specific issues around comment.
How much is this a blocker for you? Is there any workaround you can apply?

👋 I'm wallaby / quokka daily user.

That's awesome :)

One of Quokka/Wallaby key features is Live Comments, which gives users a mechanism to always log a value when Wallaby/Quokka runs their code.
We've been recommending people use swc over babel or TypeScript (see our blog post) because of the massive performance benefits. And we're also using swc in our own projects.
There's no real work around for us on this issue. It seems to work most of the time, but not always.
I wouldn't say it's a blocker for us per se but it'll definitely affect our customers and perhaps make them choose babel instead of swc when running their tests if they find it particularly painful.


How can I contact you?

Hi Ayush,
I would like to contact you in regards to a coding project that I am working on. Seems like you have a similar experience. Can you share your email ID where we can discuss further.
Thanks

It's @.*** @.***>
On Sun, 12 Nov, 2023, 12:07 PM Aamir Bader Shah, @.***>
wrote:

[image: Boxbe] https://www.boxbe.com/overview This message is eligible
for Automatic Cleanup! @.***) Add cleanup rule
https://www.boxbe.com/popup?url=https%3A%2F%2Fwww.boxbe.com%2Fcleanup%3Fkey%3DiBF44rvbhkI6lB1iyQqZkJVZ5O2qjgQBnqY5drol0Cc%253D%26token%3DSm1KaxUBwXguse6b3IzwZTiq%252B3XepeObvmwpY9HyqMzxAz5V7CqZN%252BXu77Lj7sjo2lJqJqOLicsyfv%252BwIj8bNg74M6TVPArt3InfcGE8q44gM8kMxB%252BnhxWu7OPvXt976DaDnq1OadLk74Nu3OCqSA%253D%253D&tc_serial=59632133130&tc_rand=732580558&utm_source=stf&utm_medium=email&utm_campaign=ANNO_CLEANUP_ADD&utm_content=001&
| More info
http://blog.boxbe.com/general/boxbe-automatic-cleanup?tc_serial=59632133130&tc_rand=732580558&utm_source=stf&utm_medium=email&utm_campaign=ANNO_CLEANUP_ADD&utm_content=001&
Hi Ayush,
I would like to contact you in regards to a coding project that I am
working on. Seems like you have a similar experience. Can you share your
email ID where we can discuss further.
Thanks
—
Reply to this email directly, view it on GitHub
https://github.com/AYUSH-ISHAN/Type-Based_Heirarchial_MARL_SC2/issues/4,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASRXSOOKZELUOP7KJUL3CTTYEBTRFAVCNFSM6AAAAAA7HZK6G6VHI2DSMVQWIX3LMV43ASLTON2WKOZRHE4DSMRVHAZDSMY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hi Ayush, I am unable to read your email. Could you send me an email on<EMAIL_ADDRESS>please


The Application is not responding after running it.

Hi,
Thank you for the amazing work. However, I encountered an issue while running the application. After importing a video, nothing happens. For instance, I imported the demo video and tried asking a question, but there was no response.
Could you please provide or release a tutorial document explaining how to use the software effectively?
Thank you!

Thanks for your attention!
We think the different versions of gradio might cause this problem. And we will fix this bug this weekend.


Reader option

I've found myself doing that a lot:
class Foo
  extend Dry::Configurable

  setting :something

  def self.something
    config.something
  end
end

WDYT about this:
class Foo
  extend Dry::Configurable

  setting :something, reader: true
end

What behavior for reader should be for this example?
class Foo
 extend Dry::Configurable

 setting :database, reader: true do
   setting :dsn, 'sqlite:memory'
 end
end

I'm not sure it would be necessary on nested settings as a reader on the root setting would make the child settings available as i.e. database.dsn

Not sure about this as it introduces different behaviour based on the level of nesting, plus you could just use Forwardable and delegators to do the same

@AMHOL wdym?

@AMHOL's probably talking about what happens with something like this, for example?
setting :foo do
  setting :bar, reader: true
end

Nesting shouldn't be supported as it makes no sense :)

@solnic I'm not sure the option should be supported though, the way the library works it can't be implemented on the root level without also being implemented at the nested level, and I'm not sure whether a library for configuration should support an option to expand the interface of an object. With Forwardable I meant something like:
class App
  extend Dry::Configurable

  class << self
    extend Forwardable
    def_delegator :config, :database
  end

  # Pass a block for nested configuration (works to any depth)
  setting :database do
    # Can pass a default value
    setting :dsn, 'sqlite:memory'
  end
  # Defaults to nil if no default value is given
  setting :adapter
end

App.database
=> #<struct dsn="sqlite:memory">

@AMHOL I think we can close this one


chore: CIP94 Privacy Requirements

Yeah I wonder if we could add some potential strategies here or other
technologies that could help. Encrypted data would be extra cool and useful
On Mon, Mar 8, 2021 at 4:05 PM Spencer T Brody<EMAIL_ADDRESS>wrote:

@stbrody commented on this pull request.
In CIPs/CIP-94/CIP-94.md
https://github.com/ceramicnetwork/CIP/pull/96#discussion_r589712275:

@@ -107,7 +107,12 @@ The NFT DID derives most of its security properties from the blockchain which th

Privacy Requirements
-See § 10. Privacy Considerations in did-core.
+Blockchains provide an immutable audit trail of all previous owners of an NFT. The caip10-link Ceramic document similarly provides an audit trail for which DID the specified blockchain account has pointed to over time. These audit trails are completely public.

+Since NFTs are tradable, resources that an NFT has access to should not be seen as having been granted to one individual. Instead access granted to an NFT DID becomes more fluid.

+Another important aspect to consider is that if data is encrypted to an NFT DID the data will only really be encrypted to the public key of the controller-did. This means that when the NFT gets a new owner this new owner won't get access to data that was previously encrypted to the NFT DID. Furthermore, the old owner will still be able to decrypt the data if they have access to it.
That's a bummer. I guess there's really no way around it though
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/ceramicnetwork/CIP/pull/96#pullrequestreview-606662513,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHZQESR43MLHU5A74IVQGLTCUUZZANCNFSM4YZ74LSQ
.

--
Michael Sena
908-285-6653
LinkedIn http://linkedin.com/in/msena


autoscale button for features/waveforms views

To make [99% of?] the data fill the viewable area.

can use p = np.percentile(self.view.visual.features, 95)
requires #402

The more I sort, the more I realize how critical this is. Basically, there is still a 30-second gap between making one decision and being in a position to make another, just like with KV - the difference is, it doesn't feel so bad now because it's all spent with me zooming out, finding the waveform, zooming in on it, ctrl+clicking to pick some features - i.e. because I'm doing something active rather than just sitting and waiting. But it is still a major time sink.

Yes we will try to do this this week @nippoo
Le dimanche 4 octobre 2015, nsteinme<EMAIL_ADDRESS>a écrit :

The more I sort, the more I realize how critical this is. Basically, there
is still a 30-second gap between making one decision and being in a
position to make another, just like with KV - the difference is, it doesn't
feel so bad now because it's all spent with me zooming out, finding the
waveform, zooming in on it, ctrl+clicking to pick some features - i.e.
because I'm doing something active rather than just sitting and waiting.
But it is still a major time sink.
—
Reply to this email directly or view it on GitHub
https://github.com/kwikteam/phy/issues/401#issuecomment-145349246.

There should not be a button for this: the view should automatically zoom in, which will also remove a lot of complexity in the code due to saving the manually-set scaling factor.

Yeah, good, let me be more clear about what I'm hoping will happen. Upon assigning the current "best unsorted" to some cluster_group, then: whether by hotkey or automatically, either fine for me, you go from this:
[waveform view of where the last best unsorted used to be]

to this: [waveform view of where the new one is, with same zoom/scaling parameters?]

and from this [feature view of old features]

to this [feature view of new features, keeping time as the x-axis if it was before, or else picking two large features for "best unsorted"]

When you go from one "closest match" to another, nothing should change in either view.
Of course it will also help if this one is also fixed: https://github.com/kwikteam/phy/issues/617
There is another problem this will generate - at least when you have to zoom in and out all the time, you do keep track of where on the probe you are currently looking. This is relevant, important information. The coolest and nicest solution might be if it did a really quick google-maps style animation of zooming out to show the whole probe then zooming in to the new spot. A simpler workaround could be opening a second waveform view (is this possible?) that the user keeps zoomed out so they see both the zoomed and un-zoomed view at once. A third option would be some kind of labeling of the waveform view with geometrical coordinates.

wow you're a tough user to satisfy ;)
How urgent is all of this? I'm currently doing a significant refactoring of the code, and I could tackle some of this at the same time, but it won't be ready until after SfN. Otherwise we can try to hack something quicker, but we'll have to rework the implementation on the new version.

Can we say 0.3? If it's not ready before SfN that's fine. I understand the
refactoring is important, no worries. And don't worry, I am mostly very
satisfied, these are just some loose ends. Thanks!
On Sun, Oct 4, 2015 at 3:10 PM, Cyrille Rossant<EMAIL_ADDRESS>wrote:

wow you're a tough user to satisfy ;)
How urgent is all of this? I'm currently doing a significant refactoring
of the code, and I could tackle some of this at the same time, but it won't
be ready until after SfN. Otherwise we can try to hack something quicker,
but we'll have to rework the implementation on the new version.
—
Reply to this email directly or view it on GitHub
https://github.com/kwikteam/phy/issues/401#issuecomment-145353002.

Oh yeah, sure, actually I've put the "Pre-SfN" milestone but it'll probably have to be relabelled ;)
Pierre and Olivier have also requested this feature for template matching, which is understandable given the size of their probes...

No, this is definitely definitely high-priority (at least most of it). It annoys me even when I'm trying to look through a dataset quickly, never mind sorting a whole one by hand...!
Related to issue #94.


parser failing on valid query with parameters?

Some test code:
final List<Token> tokens = scan(meQuery);
 final Parser parser = Parser(tokens);

 if (parser.errors.isNotEmpty) {
   // Handle errors...
   print(parser.errors.toString());
 }

 // Parse the GraphQL document using recursive descent
 final DocumentContext doc = parser.parseDocument();

 expect(doc.definitions, isNotNull);
 expect(doc.definitions, isNotEmpty);

Fails with this query:

query customerMemberAttributes(\$memberId: Int!){
  customerByCustomerId(customerId: 7) {
    customerMemberAttributesByCustomerId {
      nodes {
        customerMemberAttributeId
        memberAttributesByCustomerMemberAttributeId(condition: {memberId: $memberId}) {
          nodes {
            memberAttributeId
          }
        }
      }
    }
  }
}

but not this query:
query customerMemberAttributes(\$memberId: Int!){
  customerByCustomerId(customerId: 7) {
    customerMemberAttributesByCustomerId {
      nodes {
        customerMemberAttributeId
        memberAttributesByCustomerMemberAttributeId(condition: {memberId: 7}) {
          nodes {
            memberAttributeId
          }
        }
      }
    }
  }
}

I believe these queries are valid and both should work.

Please format the second query (can't read it).

Sorry about the formatting - fixed.

Okay, I need more information. The word "fails"/"failing" really doesn't me a clue as to what is happening.

I notice backslashes in front of your $. Is there a specific reason for this?
Are you getting an error message, etc. when parsing the second query? If so, please paste its contents, as well as the associated source span.
What are you expecting to happen here? What is actually happening?

To the get the span:
for (var e in errors) {
  // Do whatever other printing is necessary...
  print(e.message);
  print(e.span.highlight());
}

Sorry about the backslashes - needed to escape the "$".
The first query is what is actually failing with these errors:
  ╷
1 │ query customerMemberAttributes($memberId: Int!){   customerByCustomerId(customerId: 7) {     customerMemberAttributesByCustomerId {       nodes {         customerMemberAttributeId         memberAttributesByCustomerMemberAttributeId(condition: {memberId: $memberId}) {           nodes {             memberAttributeId           }         }       }     }   } }
  │                                                                                ^
  ╵
Unterminated object literal.
  ╷
1 │ query customerMemberAttributes($memberId: Int!){   customerByCustomerId(customerId: 7) {     customerMemberAttributesByCustomerId {       nodes {         customerMemberAttributeId         memberAttributesByCustomerMemberAttributeId(condition: {memberId: $memberId}) {           nodes {             memberAttributeId           }         }       }     }   } }
  │                                                                                ^
  ╵
Missing ")" in argument list.
  ╷
1 │ query customerMemberAttributes($memberId: Int!){   customerByCustomerId(customerId: 7) {     customerMemberAttributesByCustomerId {       nodes {         customerMemberAttributeId         memberAttributesByCustomerMemberAttributeId(condition: {memberId: $memberId}) {           nodes {             memberAttributeId           }         }       }     }   } }
  │                                                                                ^
  ╵
Missing "}" after selection set.
  ╷
1 │ query customerMemberAttributes($memberId: Int!){   customerByCustomerId(customerId: 7) {     customerMemberAttributesByCustomerId {       nodes {         customerMemberAttributeId         memberAttributesByCustomerMemberAttributeId(condition: {memberId: $memberId}) {           nodes {             memberAttributeId           }         }       }     }   } }
  │                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  ╵
Missing "}" after selection set.
  ╷
1 │ query customerMemberAttributes($memberId: Int!){   customerByCustomerId(customerId: 7) {     customerMemberAttributesByCustomerId {       nodes {         customerMemberAttributeId         memberAttributesByCustomerMemberAttributeId(condition: {memberId: $memberId}) {           nodes {             memberAttributeId           }         }       }     }   } }
  │                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  ╵
Missing "}" after selection set.
  ╷
1 │ query customerMemberAttributes($memberId: Int!){   customerByCustomerId(customerId: 7) {     customerMemberAttributesByCustomerId {       nodes {         customerMemberAttributeId         memberAttributesByCustomerMemberAttributeId(condition: {memberId: $memberId}) {           nodes {             memberAttributeId           }         }       }     }   } }
  │                                                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  ╵
Missing selection set in fragment definition.
  ╷
1 │ query customerMemberAttributes($memberId: Int!){   customerByCustomerId(customerId: 7) {     customerMemberAttributesByCustomerId {       nodes {         customerMemberAttributeId         memberAttributesByCustomerMemberAttributeId(condition: {memberId: $memberId}) {           nodes {             memberAttributeId           }         }       }     }   } }
  │       ^^^^^^^^^^^^^^^^^^^^^^^^
  ╵

The definitions should not be empty (I believe).
I am trying to get the "operation name" (which is the definition.name) for the query. The second query returns the name and the first does not. I actually need to pass the variable into the query in the code so hard coding the memberId is a no go.
As a note I am digging into a flutter GraphQL library issue and have run it down to this library which is used by them.

Ah, I see.
So, peering back into the spec (the original parser is from 2016), it looks like Variable nodes can now be considered Value nodes: https://graphql.github.io/graphql-spec/June2018/#Value
However, ObjectFieldContext only takes scalar values:
https://github.com/angel-dart/graphql/blob/master/graphql_parser/lib/src/language/ast/misc_value.dart#L65
The fix necessary will be to be to ultimately allow object fields to take ValueOrVariable instead of just Value. This will be a much bigger change than it might seem.
The steps necessary to prevent this change from breaking all of the other GraphQL packages are:

Add a T computeValue(Map<String, dynamic> variables) to ValueContext.

This should default to returning ValueContext.value.
Add logic for resolving variable names in object fields from the variables argument.
Throw an error if the plain getter ObjectValueContext.value is called when any field contains a variable.

Modify graphql_server to call computeValueinstead of just gettingvalue`.

A fix for this is rolling in branch 1.2.0: https://github.com/angel-dart/graphql/tree/1.2.0
Working on getting this release out ASAP. I aim to fix all outstanding bugs in this package.

Will go ahead and close this, as it's been solved (though it has not been released yet).


add type generation

This is the result: https://github.com/webpack/webpack/blob/types/generate/types.d.ts

What kind of change does this PR introduce?
typing generation from source

Did you add tests for your changes?
yes, against the config test suite
need to be added to tsconfig.json to test the typings agains all webpack configs in our test suite. But this doesn't work yet.

Does this PR introduce a breaking change?
yes, types are exposed

What needs to be documented once your changes are merged?
@types/webpack is no longer needed starting with webpack 5.

Open TODOs

[x] Move tooling into separate repo
[x] Test types against test suite

[x] Make tests pass

[x] any arguments should be optional too
[x] readonly flags (e. g. for hooks)
[x] methods instead of properties with functions
[x] inline anonymous namespaces in other namespaces
[x] emit only types needed (emit when getCode is called)
[x] remove internal namespace (add all non typeof properties in namespace to usedNames)
[ ] emit function instead of interface for functions

It's worth testing against DT too https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/webpack/test/index.ts

Some @types/* packages such as devServer are contributing to webpack types. To not break the world this change needs to keep naming consistent with previous @types/webpack types.
Luckily it's easy to test all of those types by replacing @types/webpack with this branch in DT and run the tests there.

Some @types/* packages such as devServer are contributing to webpack types. To not break the world this change needs to keep naming consistent with previous @types/webpack types.
Luckily it's easy to test all of those types by replacing @types/webpack with this branch in DT and run the tests there.

I did my best to ensure that it is compatible with at least Configuration from DefinitelyTyped. I tried to test this inside of webpack but seems like typescript doesn't allow to argument the module you are inside of. At least I was not able to do that.

[string, ...string] is incorrect. ... is onitted


Document diff problems with TCP/UDP ports

"Fixes" #99.
@sh0rez are there other places where this should documented, too?

I'll move into known-issues.md.

PHAL.


Update run_reference_analysis.sh

"hg clone" repository is not available replaced with "git clone"

mercurial is need for "hg clone". But it can be also replaced with "git clone"


Rewrite application in Python

This PR is open to move the rewrite of LambentLight done in Python into the master branch.
See #43 for more information.
If you think that something needs to be modified, feel free to leave a comment.

I'm going to merge this PR and keep working on master.
If you are interested on the old version, check the pre-rewrite branch,


gotty does not work properly under firefox 64.0

What version of GoTTY are you using (gotty --version)?
gotty version 1.0.1
What operating system and browser are you using?
Mac os 10.14.1
Firfox 64.0
What did you do?
set the '--once' option, just like:
gotty --address <IP_ADDRESS> --port 9091 --w --once  docker exec -it b4598916268f sh
What did you expect to see?
Gotty Can be work normally at firefox 64.0
What did you see instead?
everything works fine under Chrome

but can't work under Firefox 64.0

I guess it is caused by the code below， but I don't know how to fix it

When file a new feature proposal

Hello,
we're experiencing the same behavior under Firefox 64. Chrome, Edge and Safari work fine.

It is --once and/or --max-connections 1 flags that broke the gotty in Firefox for us. For some reason Firefox establishes two connections to gotty:
2019/02/08 13:54:26 read tcp <IP_ADDRESS>:40332-><IP_ADDRESS>:43213: use of closed network connection
2019/02/08 13:54:26 Connection closed: <IP_ADDRESS>:43213, connections: 1/5
2019/02/08 13:54:36 New client connected: <IP_ADDRESS>:54234
2019/02/08 13:54:36 Command is running for client <IP_ADDRESS>:54234 with PID 4421 (args="bash -l"), connections: 2/5

After removing --once and bumping --max-connections it works when opened directly in Firefox, but is still broken when loaded in iframe.

Hi there,
Is there updates?  This problem also occurs in Firefox 65 66...

https://github.com/DaoCloud/gotty/commit/1e03cc863be22003635c4a61b7b9f2b5b8df4cf7
After I update hterm to v1.84, it works!


Exception removing multiple elements from ordered embeddable collection

running additional tests to check latest Reactive collection persister logic from the @OrderColumn #581 changes.  Ran into an issue removing more than 1 element during a flush().
See: OrderedEmbeddableCollectionTest
Exception: 	[Exception 0] io.vertx.core.impl.NoStackTraceThrowable: The number of parameters to execute should be consistent with the expected number of parameters = [2] but the actual number is [3].
[Exception 1] io.vertx.core.VertxException: Transaction already completed
Appears that the Object[] array of param values is returning an Object[3] instead of Object[2] for the second deleted element in the new abstract persister: https://github.com/hibernate/hibernate-reactive/blob/fe9dfbaa07e4b71fe85e949a45ac23c91c26709b/hibernate-reactive-core/src/main/java/org/hibernate/reactive/persister/collection/impl/ReactiveAbstractCollectionPersister.java#L237

Might be worth getting the test working on Hibernate ORM core, just to be able to step through and see what happens there.

In ORM's deleteRows  the int offset = 1; never changes.
In Reactive, we're passing the offset into the deleteRowsParamValues( entry, index+1, id, session ) call, which is based on an incremented index value.  Seems we're wrongly combining the concepts of i, index, loc and offset in ORM.
The i value appears to provide update and insert methods to know which collection entry is being operated on, so it shouldn't be tied to/used in the delete process.

Yup, it looks like the logic is just wrongly-ported-over.

I think just changing the index+1" to 1 reflects the ORM logic

Great!

Good catch!
@blafond assigned this to you as it seems you have already a fix

Thanks, @blafond


Without istio-system services in the Sidecar resource, you lose metrics

Hey,
I consider this behaviour a little unexpected, but if you're using Sidecar to control egress, without appending istio-system services, eg:
    - istio-system/zipkin.istio-system.svc.cluster.local
    - istio-system/jaeger-agent.istio-system.svc.cluster.local
    - istio-system/istio-telemetry.istio-system.svc.cluster.local
    - istio-system/istio-policy.istio-system.svc.cluster.local

You lose metrics.
Personally I'd expect this to just work, istio should probably transparently clusters which are just required for things to be functional.
this graph shows where we didn't have istio-system egress routes in our app sidecar:

round(sum(irate(istio_requests_total{destination_service="app.forecourt-service.svc.cluster.local"}[1m])) by (source_app, response_code), 0.001)

As an added comment, it wasn't easy to spot.  We'd actually just mistakenly not used the fqdn, for example:

@costinm @rshriram @mandarjog @louiscryan what are our thoughts on defaulting access to istio-system resources?  is this the sort of thing that should be automatic (always allow traffic to the gloabl tracing service and istio-telemetry)?
Or is this primarily a docs issue (that we should emphasize)?

for ux, i vote for make it default

Yeah from a UX perspective why would anyone ever do tracing.enabled=true and then not want connectivity to tracing services?

Duplicate of this: https://github.com/istio/istio/issues/12237

Closing in favor of https://github.com/istio/istio/issues/12237


Project Status

@crhym3 Just wanted to see what your plans are for this repo moving forward. @raphael's suggested changes all seem great.

Hey @derekperkins I'm not sure how but I missed all notifications from @raphael's issues. Or maybe github never sent me those.
In any case, thanks so much for pinging me. I'll check out all @raphael's suggestion. The plan is to make this more robust and better :) so, all suggestions are welcome.

Awesome! This is a pretty cool extension.


OSError: libcurand.so.10: cannot open shared object file: No such file or directory

I'm running the container "dustynv/ros:noetic-pytorch-l4t-r32.5.0" (and I also tried the previous one) as I want to use ros-noetic together with pytorch on a Jetson AGX.
However, when I try to import PyTorch, I get the following error:
Status: Downloaded newer image for dustynv/ros:noetic-pytorch-l4t-r32.5.0
sourcing   /opt/ros/noetic/setup.bash
ROS_ROOT   /opt/ros/noetic/share/ros
ROS_DISTRO noetic
root@e22d0ae5ddbc:/# python
Python 3.6.9 (default, Oct  8 2020, 12:12:24)
[GCC 8.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import torch
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.6/dist-packages/torch/__init__.py", line 188, in <module>
    _load_global_deps()
  File "/usr/local/lib/python3.6/dist-packages/torch/__init__.py", line 141, in _load_global_deps
    ctypes.CDLL(lib_path, mode=ctypes.RTLD_GLOBAL)
  File "/usr/lib/python3.6/ctypes/__init__.py", line 348, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: libcurand.so.10: cannot open shared object file: No such file or directory
>>>

Any idea what I could be missing or how to fix this?

Edit:
Reading the README, I found that one needs to change the default runtime to nvidia if one wants to use pytorch, as seen here:
https://github.com/dusty-nv/jetson-containers#docker-default-runtime


show hits on specific pages

hi i used code to get page url in page name field now i want to show hits on that page, what code i can use to show hits o page? as url are variables and all are passed through same php file so i want a code which match url with the url in mysql database and show total visits of that url
regards

issue resolved but when i am opening same page again and again, it is increasing counter i want to show only unique visits, what to do?


socks 6

Adding Socks 0.6 support with deadlines.
@czechboy0, it might be a good idea to include timeval in Socks. Have to import SocksCore still. But this seems to be working. Let me know if I'm doing it right.

Wait, how is deadline for never defined? This cant take negative values, but isn't never defined as -1? If so, never needs to be 0. That's what's defined as wait forever in the sockets API.
Other than that it looks good, but do test it out first :)

I made some updates to how Stream works in a different branch. Going to merge this so I can update.
I'll make sure not to send negative values. :)


Add new assertions

[ ] assertButton
[ ] assertButtonIsPresent/NotPresent (both to use assertButton)
[ ] contains/doesNotContain
[ ] assertCount
[ ] assertMissingText
[ ] assertSelectHasValueByLabel
[ ] assertInputHasValueByAutoId

Feel free to remove/add more

These look good to me.  One pattern I've seen is using refute instead of assertNot, so I would change assertButtonIsNotPresent to refuteButtonIsPresent.

I find the former easier to comprehend at first glance. For some reason the refuteButtonIsPresent confuses my brain D:


Implement some llvm.x86.sse2.* intrinsics and add tests

Continuation of https://github.com/rust-lang/miri/pull/2989 with SSE2 intrinsics.
Thankfully, a significant amount of SSE2 functions use simd_* intrinsics, which are already implemented in Miri.

@rutsbot author

@rustbot author

@rustbot ready

All right, looking great overall! Please squash into <4 commits, then we can land this. :)

Ready!

Remainder to myself:

Implement bin_op_f32/bin_op_f64 with generics to reduce code duplication.
Figure out a widening conversion helper function to implement avg and mulh without host integer arithmetic.

I will work on that once this lands in the main Rust repo because I expect to add helpers to rustc_middle.

Thanks. :)
@bors r+

I will work on that once this lands in the main Rust repo because I expect to add helpers to rustc_middle.

I expect it will be rustc_const_eval, but it will be on the rustc side either way.

:pushpin: Commit<PHONE_NUMBER>080deb7fe4cb8b15b9e39e0b37da21 has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit<PHONE_NUMBER>080deb7fe4cb8b15b9e39e0b37da21 with merge 0143f1fc3005d82341acb1d80a178964928da482...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 0143f1fc3005d82341acb1d80a178964928da482 to master...

@eduardosm his is synced into rustc now.


doc: type spec

Summary by CodeRabbit

New Features

Enhanced type specifications for functions in the Yex.ArrayPrelim, Yex.Map, Yex.Text, Yex.XmlElement, and Yex.XmlFragment modules, improving clarity and type safety.
Added practical usage examples in the documentation for several functions in the Yex.Map module.
Introduced new data structures in the Yex.XmlTextPrelim module, allowing for more complex data representation.

Documentation

Updated documentation to include type specifications and examples for various functions, aiding user understanding and implementation.

These changes improve the usability and safety of the modules without altering existing functionalities.

coverage: 79.923% (-0.3%) from 80.233%
when pulling 96febb07179039355421cd354f41aa2b13cb7901 on typespec
into b1c1a0078f009731e03a216a79427d2c39c0b845 on main.


App crash in updateLocation method

Hello,
I found that the App crash when the number of my beacons is 4 in updateLocation() method inside the IndoorPositioning class
No interface method sort(Ljava/util/Comparator;)V in class Ljava/util/List; or its super classes (declaration of 'java.util.List' appears in /system/framework/core-libart.jar)
1 -

2 -

3 -

Here is the 4 beacons from usableBeacons ArrayList :
1 -

2 -

3 -

4 -

PS: I am working with the dev branch
'implementation 'com.github.neXenio:BLE-Indoor-Positioning:dev-SNAPSHOT'

After searching a little bit i found that it's not recommended to use ArrayList#sort if the app targeting Api Level > 25.
Instead we should use Collections.sort(list, comparator).
Implementation Note:
This implementation defers to the List.sort(Comparator) method using the specified list and a null comparator. Do not call this method from List.sort() since that can lead to infinite recursion. Apps targeting APIs <= 25 observe backwards compatibility behavior where this method was implemented on top of List.toArray(), ListIterator.next() and ListIterator.set(Object).

check this and this.
I sent a PR to fix this bug.

I find it strange that we didn't ran into this issue, as we're also targeting API level 26 and have > 3 beacons in range all the time. Anyway, glad you figured out that using Collections.sort(list, comparator) fixed this issue for you.


Path-dependent types turn into type projections

I'm still struggling with getting TypeTag to work. Now the problem is that it is path-dependent on the universe.
Simplified example: Let's say that I have these types:
class Outer {
  class Inner
}

Then
  println(dbg_code"""
              val x = new Outer
              val y: x.Inner = ???""")

prints
code"""{
  val x_0 = new test.Outer();
  val y_1 = ((scala.Predef.???): (test.Outer)#Inner);
  ()
}"""

where x.inner turned into Outer#Inner.
This is a problem in Emma, because after some code fragment runs through Squid, I'm getting errors such as
found   : scala.reflect.api.JavaUniverse#TypeTag[String]
 required: reflect.runtime.universe.TypeTag[String]

Sorry, I should have pointed you to this Squid feature list from the start. There is expressly no support for path-dependent types in Squid.
I am wondering why you need to embed type tags in the DSL code fragments, though. What is the use case?

Ugh... that's a bit annoying.
Note that ClassTag should be problematic. As for TypeTag, it's actually problematic because scala.reflect.runtime.universe is not a module but a simple val, defined as:
lazy val universe: api.JavaUniverse = new runtime.JavaUniverse

One workaround would be to define your own module universe as:
object universe extends runtime.JavaUniverse

...though that would not help if you want to use definitions you can't change such as the Spark ones.
Maybe then, it would be sufficient to declare an implicit conversion from scala.reflect.api.JavaUniverse#TypeTag[T] to reflect.runtime.universe.TypeTag[T], implemented as a cast?

I made a typo in the message above: class tags are not problematic; they embed well. For example:
scala> import squid.TestDSL.Predef._
import squid.TestDSL.Predef._

scala> code"scala.reflect.classTag[String]"
res0: squid.TestDSL.ClosedCode[scala.reflect.ClassTag[String]] = code"scala.reflect.`package`.classTag[java.lang.String](scala.reflect.ClassTag.apply[java.lang.String](_root_.scala.Predef.classOf[String]))"


many fixes, separated by commits

How_To/ in images links wasn't work online, I replaced it by how_to/
Added IBL texture tool link
reorder some parts in a more logical way to me, and also remove the twice part about Sandbox generate .env button

There are a few build issues, mainly because you changes all How_To to how_to. These refer to the directory the .md file is located at, and not the URL. Also, the How_To url are being correctly forwarded to their new location, but how_to URLs simply fail with 404.
The image URLs are the only ones that are served from the how_to URL, because this is the actual name of the directory in the public library.

wooops ok! i fix this

should be fine now, right?

Was it intentional that the png you submitted is empty? Any reason to actually show it in the docs?

not intentionnal at all 😱 but I don't understand, on my fork we clearly see the image https://github.com/Vinc3r/BabylonJS-Documentation/blob/master/public/img/how_to/Environment/ibl-texture-tool.png

I really doesn't understand what happens here... here the image from imgur: https://i.imgur.com/1hP3BjT.png
do you want me to delete this file, and try later?
(sorry about all these issues...)

I have to admit that it is odd.

The commit seems to be deleting the file?

i've update my PR so as to get rid of this image, we will see this later 🙃


AttributeError: 'ModleWithLoss' object has no attribute 's_det'

I am very interested in this work, I would like to reproduce it, but can you help me, I can run test.py file, but when I want to train yes, run train.py file will report an error, prompt as follows:
yesyes
/opt/conda/conda-bld/pytorch_1565272279342/work/aten/src/ATen/native/IndexingUtils.h:20: UserWarning: indexing with dtype torch.uint8 is now deprecated, please use a dtype torch.bool instead.
/opt/conda/conda-bld/pytorch_1565272279342/work/aten/src/ATen/native/IndexingUtils.h:20: UserWarning: indexing with dtype torch.uint8 is now deprecated, please use a dtype torch.bool instead.
/opt/conda/conda-bld/pytorch_1565272279342/work/aten/src/ATen/native/IndexingUtils.h:20: UserWarning: indexing with dtype torch.uint8 is now deprecated, please use a dtype torch.bool instead.
/opt/conda/conda-bld/pytorch_1565272279342/work/aten/src/ATen/native/IndexingUtils.h:20: UserWarning: indexing with dtype torch.uint8 is now deprecated, please use a dtype torch.bool instead.
Traceback (most recent call last):
File "train.py", line 133, in
main(opt)
File "train.py", line 92, in main
log_dict_train, _ = trainer.train(epoch, train_loader)
File "/home/buu/Yan/DEFT/src/lib/trainer.py", line 486, in train
return self.run_epoch("train", epoch, data_loader)
File "/home/buu/Yan/DEFT/src/lib/trainer.py", line 246, in run_epoch
output, loss, loss_stats = model_with_loss(batch)
File "/home/buu/anaconda3/envs/DEFT/lib/python3.6/site-packages/torch/nn/modules/module.py", line 547, in call
result = self.forward(*input, **kwargs)
File "/home/buu/Yan/DEFT/src/lib/trainer.py", line 192, in forward
loss_stats["tot"] = torch.exp(-self.s_det)  * loss_stats["tot"] + torch.exp(-self.s_id) * loss_matching + (self.s_det + self.s_id)
File "/home/buu/anaconda3/envs/DEFT/lib/python3.6/site-packages/torch/nn/modules/module.py", line 591, in getattr
type(self).name, name))
AttributeError: 'ModleWithLoss' object has no attribute 's_det'

hello. Have you solved it? l want to know how you address this problem.

hello. Have you solved it? l want to know how you solve this problem.

Not yet, and have you solved it

你好。你解决了吗？我想知道你是如何解决这个问题的。

File "DEFT/src/lib/trainer.py", line 149
class ModleWithLoss(torch.nn.Module):
def init(self, model, loss):
super(ModleWithLoss, self).init()
self.model = model
self.loss = loss
self.s_det = nn.Parameter(torch.ones(1))
self.s_id = nn.Parameter(torch.ones(1))


Selendroid and Gradle

Hi,
I am trying to run Selendroid Acceptance tests from a gradle project in Intellij on a MacOS.
Even if I setup the android home (I can do echo $ANDROID_HOME and the output is correct), I get "Environment variable 'ANDROID_HOME' was not found!".
Is there anything I can setup or pass directly to Selendroid when I run tests so that the ANDROID_HOME get set?
Thanks

This seems to be a gradle IntelliJ configuration issue. Add the ANDROID_HOME variable there and it should work.

Can you tell me exactly where I could add the ANDROID_HOME in Intellij?

http://lmgtfy.com/?q=how+to+set+environment+variable+in+intellij

Thanks for googling that for me.
There is no Environment setting in the run/debug configuration in gradle.

I solved the problem, maybe can be of any help to someone.
 A groovy run configuration gives you the chance to setup an Environment Variable and in this way you can pass the ANDROID_HOME required by Selendroid. This solved the problem.


permissions parameter in didHide()

Hi,
Can you please add permissions: [SPPermission] as a parameter to the didHide() method?
When there's only one permission we ask for on a VC, it's easy to know which permission request the user dismissed and react accordingly... however, when there's multiple permissions we may be asking for and the user dismisses the request, it'd be nice to know which permission(s) were ignored.
Thanks!

Good idea! I am add it today)

Great, thanks!

I am add it in 5.2.4, please, update. I can't simple return array of permission, but I returned ids of permissions. Need init SPPermission with it id. You can see readme for more details.
And thanks for cool idea!

Cool - I'll take a look!


duplicated screenshots?

Hey there guys, i'm trying to create a POC of a visual diff tool and i'm having an issue where i get duplicated screenshots every time i run my test...
I get what appears to be a default screenshot and the one i named, so for example with this run:
const Differencify = require('differencify');
const differencify = new Differencify({
    debug: true,
    imageSnapshotPath: './evidence'
});

const hideElement = () => {
    document.querySelector('.small-spots__container').style.display = "none";
};

const snap = async () => {
    await differencify.launchBrowser();

    const target = differencify.init({ chain: false });
    const page = await target.newPage();

    await page.setViewport({ width: 1360, height: 768 });
    await page.goto('https://www.gog.com');
    await page.addStyleTag({ path: './src/freeze.css' }); // Freezing animations and transitions
    await page.evaluate(hideElement); // hiding dynamic elements to avoid false-positives
    await page.waitFor('.js-background-0'); // waiting for big image to continue

    const image = await page.screenshot({
        type: 'jpeg',
        path: './evidence/frontpage_big_spot.jpg'
    });

    await target.toMatchSnapshot(image);

    await page.close();
    await differencify.cleanup();
};

snap();

This runs fine, the problem is that i get two screenshots here instead of one...
frontpage_big_spot.jpg
test 1.snap.png
The first one is the intended one as you can see in line path: './evidence/frontpage_big_spot.jpg'
The second one i have no idea where is it coming from, also it's the wrong format?
How can i avoid this? I can't find any info in other issues or in the docs.
Thanks and regards.

Hi @jbures,
The problem is that you are trying to name your screenshot image file in a wrong way, instead, you should use Differencify provided options to that for you.
Based on testoption you can provide a testName which is basically your screenshot name.
So I would re-write your script like this:
const snap = async () => {
    await differencify.launchBrowser();

    const target = differencify.init({
      chain: false,
      testName: frontpage_big_spot,
    });
    const page = await target.newPage();

    await page.setViewport({ width: 1360, height: 768 });
    await page.goto('https://www.gog.com');
    await page.addStyleTag({ path: './src/freeze.css' }); // Freezing animations and transitions
    await page.evaluate(hideElement); // hiding dynamic elements to avoid false-positives
    await page.waitFor('.js-background-0'); // waiting for big image to continue

    const image = await page.screenshot({
        type: 'jpeg',
    });

    await target.toMatchSnapshot(image);

    await page.close();
    await differencify.cleanup();
};

snap();

The reason behind that is, if you try to take randon screenshots, Differencify wouldn't know where to find them to compare against new screenshots.

Hi @NimaSoroush, i kinda figured out this could be the reason... but it doesn't work for me because i need to document a whole flow in one test and having screenshots with different names makes it easier to know which step we are in... rather than just having 1, 2 ,3 on the name.
So anywan, thanks for the help!

Hi @jbures , Have you tried something like this
https://github.com/NimaSoroush/differencify/blob/61142708e7fa54bdceee7d4aab1f038cddcfc607/src/integration.tests/integration.test.js#L200

I'm having the exact use case as @jbures's. if I use the differencify as mentioned in "Multiple toMatchSnapshot on chained object" section, my screenshot will be named like, test 1.snap.png, test 1 2.snap.png,  test 1 2 3.snap.png  and go on. Is it possible to provide names for the screenshot individually instead of one per differencify instance (during init)?


Detect migrating batch size

should fix #7348

Does a batch size of 100 work by default for sqlite?

@zeripath it works for me but not @mrsdizzie

I left comment on #7348 about the size

Codecov Report

Merging #7353 into master will decrease coverage by <.01%.
The diff coverage is 14.75%.

@@            Coverage Diff             @@
##           master    #7353      +/-   ##
==========================================
- Coverage   41.24%   41.24%   -0.01%
==========================================
  Files         467      467
  Lines       63291    63332      +41
==========================================
+ Hits        26107    26119      +12
- Misses      33769    33796      +27
- Partials     3415     3417       +2

Impacted Files
Coverage Δ

models/models.go
58.02% <100%> (+0.52%)
:arrow_up:

modules/migrations/gitea.go
8.59% <26.66%> (+0.81%)
:arrow_up:

modules/migrations/migrate.go
19.2% <4.65%> (-1.58%)
:arrow_down:

modules/process/manager.go
76.81% <0%> (-4.35%)
:arrow_down:

routers/repo/view.go
43.25% <0%> (+1.01%)
:arrow_up:

models/unit.go
67.56% <0%> (+5.4%)
:arrow_up:

Continue to review full report at Codecov.

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

This looks good thanks! Was able to migrate all Gitea with Sqlite

I guess this needs to be 1.9

Yes should be in 1.9 since the batch processing is


C28229: Escaping URL that must not be shown as link

Hello, @pfletcher ,
Localization team has reported source content issue that causes localized version to have broken/different format compared to en-us version.
"Escaping URL that must not be shown as link"
Please review and merge the proposed file change to fix to target versions. If you make related fix in another PR  then share your PR number so we can confirm and close this PR.
Many thanks in advance.

Thank you, @v-maudel!

Thanks to you @scottaddie .