kernel: add option to enable timerlat tracing

This is a first stab at adding an option to enable timerlat tracing which is useful for debugging latency spikes in otherwise well tuned systems. I'm not sure if it works - I never before worked with options in overlays. Rebuilding the kernel takes ca. 3 hours on my system, so I'm hesitant to test right now.
nixos-rebuild dry-build at least doesn't complain..
Is there a way to just build the kernel config and not the resulting kernel? Then I could check wether the option is applied correctly to the kernel config..

Thanks for writing this!
Unfortunately it fails to build for me, full logs here:
https://gist.github.com/magnetophon/05215c10c5651ec0307793a35f4880dd

I think I have seen these kind of errors before
https://gist.github.com/magnetophon/05215c10c5651ec0307793a35f4880dd#file-gistfile1-txt-L16820
It might be a gcc thing. Which version do you use to compile the kernel?

@fps How do I find out the gcc version that is used?

Good question. I'm still trying to figure out adding this option at all. For me toggling musnix.kernel.timerlat makes no difference at all and doesn't force a kernel rebuild. Something is very wrong, either in this PR or on my system ;)

Closing as #149 would have been necessary to make this work.


Download Progress Bar for Large Files

I would like to request a feature for the uv package: a download progress bar for large files during installation. This would enhance the user experience by providing visual feedback on the download status, especially when installing sizable packages like torch using the command uv pip install torch.

I'm open to something like this but we need it to work with highly concurrent downloads.

This is a duplicate of https://github.com/astral-sh/uv/issues/1209


What do you think of Pandoctools

What do you think of Pandoctools: profile manager of text processing pipelines (uses Pandoc filters and any text CLI filters)?

This looks interesting -- it looks like a nice tool! The reproducibility problem is a big and important one. It's good to see this being addressed.

Thanks for response! Today I've learned about your Panzer. And it seems that you tried to solve alike problem that I did (but differently). So I was interested in your opinion.

I see. I didn't mind to dig into command line arguments at all so I went another way. I was irritated by copy-pasting terminal commands, adjusting names and like. So it's not a reproducibility that inspired me. I also needed extra level of abstraction. But I've chosen the one that is the easiest to understand it's workings and to tune in a moment.
Reproducibility came next. But I don't really track versions - O simply hope that they won't break anything. And simply add used Pandoc and text filers to dependencies of python module.

You even have preflight and postflight options: this functionaliy together with filters themselves is what I initially wanted to put into some kind of profiles. So this ended with bash scripts that define everything.
But in your case it's metadata section that controls panzer app.

Markdown+HTML as PDF, MS Word and others killer
@msprev See the dream description.


[Release-1.0]: Add Comments Support

I believe most of the logic for this will be done on the client through firebase, but the two things we need to setup for this are:

[x] Setup comments collection
[x] Setup proper Firestore rules

Pretty sure this is good to go, but we should do a bit more verification on this


[feature](doris compose) Add no-detach mode && use java 17 image

Add no-detach mode, will can inspect container output error;
Use java 17 image;

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Update meeting-policies-participants-and-guests.md

Link for QnA is broken. Updated with current link.

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

File
Status
Preview URL
Details

:x:Error

Details

[Error: RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://aka.ms/SiteHelp and include the error report for our team to troubleshoot

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

Docs Build status updates of commit d8f5981:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Teams/meeting-policies-participants-and-guests.md
:warning:Warning

Details

Teams/meeting-policies-participants-and-guests.md

Line 119, Column 141: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-US/microsoftteams/meeting-policies-participants-and-guests?WT.mc_id=TeamsAdminCenterCSH' contains locale code 'en-US'. For localizability, remove 'en-US' from links to most Microsoft sites.

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

We appreciate any feedback that improves the content in the Microsoft docs but we haven't had any response from you so we are going to close this issue.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


pushNamedAndRemoveUntil breaks the chain and can not return data

I have PageA that pushNamed PageB then pushNamed PageC
PageA -> PageB -> PageC
Then in PageC I have a button that allows me to  use pushNamedAndRemoveUntil to bring up PageD and remove previous pages until PageA, so now it becomes like this:
PageA -> PageD
What Im expecting is when I pop PageD with some data, PageA should be able to catch the returned data, so I can do something with it, but it doesn't seems like the case.
in PageA, I have some code like this:
Navigator.pushNamed(context, routeName, arguments: arguments).then((results) {
      // Not executed at all.
}

But if I pop back from PageB to PageA, the above code will definitely be executed.
I would like to know why it doesn't work with pushNamedAndRemoveUntil  and how can I workaround it. Thanks

[✓] Flutter (Channel stable, 1.22.5, on Mac OS X 10.15.7 19H2 darwin-x64, locale en-NZ)
    • Flutter version 1.22.5 at /Users/pengfeihuang/fvm/versions/stable
    • Framework revision<PHONE_NUMBER> (4 weeks ago), 2020-12-10 11:54:40 -0800
    • Engine revision ae90085a84
    • Dart version 2.10.4

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/pengfeihuang/Library/Android/sdk
    • Platform android-30, build-tools 29.0.2
    • ANDROID_HOME = /Users/pengfeihuang/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

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

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin installed
    • Dart plugin version 201.9317
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

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

[✓] Connected device (2 available)
    • SM J415GN (mobile)                  • ebf5e4ce                             • android-arm • Android 8.1.0 (API 27)
    • iPhone SE (2nd generation) (mobile) • 01768AA3-066A-483C-BAED-91EDC3E50665 • ios         • com.apple.CoreSimulator.SimRuntime.iOS-14-0 (simulator)

• No issues found!

Hi @PandaGeek1024
Can you please provide a minimal complete reproducible code sample?
Thank you

Hi @PandaGeek1024
Can you please provide a minimal complete reproducible code sample?
Thank you

As requested
import 'package:flutter/material.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      routes: {
        PageA.routeName: (context) => PageA(),
        PageB.routeName: (context) => PageB(),
        PageC.routeName: (context) => PageC(),
        PageD.routeName: (context) => PageD(),
      },
      title: 'Flutter Demo',
      initialRoute: PageA.routeName,
    );
  }
}

class PageA extends StatefulWidget {
  static const routeName = '/PageA';
  @override
  _PageAState createState() => _PageAState();
}

class _PageAState extends State<PageA> {

  @override
  Widget build(BuildContext context) {

    return Scaffold(
      appBar: AppBar(
        title: Text('PageA'),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            RaisedButton(child: Text('To PageB'), onPressed: () async{
              Navigator.pushNamed(context, PageB.routeName).then((value) {
                print('Got result'); //Never gets called when back from pageD
              });
            })
          ],
        ),
      ),
    );
  }
}

class PageB extends StatelessWidget {
  static const routeName = '/PageB';
  @override
  Widget build(BuildContext context) {
      return Scaffold(
        appBar: AppBar(title: Text('PageB'),),
        body: Center(
          child: Column(
            mainAxisAlignment: MainAxisAlignment.center,
            children: <Widget>[
              RaisedButton(child: Text('To PageC'), onPressed: (){
                Navigator.pushNamed(context, PageC.routeName);
              })
            ],
          ),
        ),
      );
  }
}

class PageC extends StatelessWidget {
  static const routeName = '/PageC';
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: Text('PageC'),),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            RaisedButton(child: Text('To PageD'), onPressed: (){
              Navigator.pushNamedAndRemoveUntil(context, PageD.routeName, ModalRoute.withName(PageA.routeName));
            })
          ],
        ),
      ),
    );
  }
}

class PageD extends StatelessWidget {
  static const routeName = '/PageD';
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: Text('PageD'),),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            RaisedButton(child: Text('Pop'), onPressed: (){
              Navigator.pop(context, 'Result');
            })
          ],
        ),
      ),
    );
  }
}

As requested
import 'package:flutter/material.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      routes: {
        PageA.routeName: (context) => PageA(),
        PageB.routeName: (context) => PageB(),
        PageC.routeName: (context) => PageC(),
        PageD.routeName: (context) => PageD(),
      },
      title: 'Flutter Demo',
      initialRoute: PageA.routeName,
    );
  }
}

class PageA extends StatefulWidget {
  static const routeName = '/PageA';
  @override
  _PageAState createState() => _PageAState();
}

class _PageAState extends State<PageA> {

  @override
  Widget build(BuildContext context) {

    return Scaffold(
      appBar: AppBar(
        title: Text('PageA'),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            RaisedButton(child: Text('To PageB'), onPressed: () async{
              Navigator.pushNamed(context, PageB.routeName).then((value) {
                print('Got result'); //Never gets called when back from pageD
              });
            })
          ],
        ),
      ),
    );
  }
}

class PageB extends StatelessWidget {
  static const routeName = '/PageB';
  @override
  Widget build(BuildContext context) {
      return Scaffold(
        appBar: AppBar(title: Text('PageB'),),
        body: Center(
          child: Column(
            mainAxisAlignment: MainAxisAlignment.center,
            children: <Widget>[
              RaisedButton(child: Text('To PageC'), onPressed: (){
                Navigator.pushNamed(context, PageC.routeName);
              })
            ],
          ),
        ),
      );
  }
}

class PageC extends StatelessWidget {
  static const routeName = '/PageC';
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: Text('PageC'),),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            RaisedButton(child: Text('To PageD'), onPressed: (){
              Navigator.pushNamedAndRemoveUntil(context, PageD.routeName, ModalRoute.withName(PageA.routeName));
            })
          ],
        ),
      ),
    );
  }
}

class PageD extends StatelessWidget {
  static const routeName = '/PageD';
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: Text('PageD'),),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            RaisedButton(child: Text('Pop'), onPressed: (){
              Navigator.pop(context, 'Result');
            })
          ],
        ),
      ),
    );
  }
}

I was able to reproduce the issue.

flutter doctor -v
[✓] Flutter (Channel stable, 1.22.5, on Mac OS X 10.15.7 19H2 darwin-x64, locale en)
    • Flutter version 1.22.5 at /Users/pedromassango/Code/flutter_stable
    • Framework revision<PHONE_NUMBER> (5 weeks ago), 2020-12-10 11:54:40 -0800
    • Engine revision ae90085a84
    • Dart version 2.10.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/pedromassango/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

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

[!] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] IntelliJ IDEA Community Edition (version 2020.3.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin installed
    • Dart plugin version 203.6912

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

[✓] Connected device (2 available)
    • Redmi 5 Plus (mobile)      • 0258ff700005  • android-arm64 • Android 8.1.0 (API 27)
    • sdk gphone x86 64 (mobile) • emulator-5554 • android-x64   • Android 11 (API 30) (emulator)

! Doctor found issues in 1 category.

I was able to reproduce the issue.

flutter doctor -v
[✓] Flutter (Channel stable, 1.22.5, on Mac OS X 10.15.7 19H2 darwin-x64, locale en)
    • Flutter version 1.22.5 at /Users/pedromassango/Code/flutter_stable
    • Framework revision<PHONE_NUMBER> (5 weeks ago), 2020-12-10 11:54:40 -0800
    • Engine revision ae90085a84
    • Dart version 2.10.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/pedromassango/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

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

[!] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] IntelliJ IDEA Community Edition (version 2020.3.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin installed
    • Dart plugin version 203.6912

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

[✓] Connected device (2 available)
    • Redmi 5 Plus (mobile)      • 0258ff700005  • android-arm64 • Android 8.1.0 (API 27)
    • sdk gphone x86 64 (mobile) • emulator-5554 • android-x64   • Android 11 (API 30) (emulator)

! Doctor found issues in 1 category.

Any update? Im pending on this to deliver my work. Any help will be appreciated.

Any update? Im pending on this to deliver my work. Any help will be appreciated.

Since thenis never called,If BuildContext is referenced in then, it will cause memory leak,I guess it is because Future is strongly referenced by static properties in the VM.

Reproduces on stable 3.3 and master 3.7. Popped result is not returned.

code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      routes: {
        PageA.routeName: (context) => const PageA(),
        PageB.routeName: (context) => const PageB(),
        PageC.routeName: (context) => const PageC(),
        PageD.routeName: (context) => const PageD(),
      },
      title: 'Flutter Demo',
      initialRoute: PageA.routeName,
    );
  }
}

class PageA extends StatefulWidget {
  static const routeName = '/PageA';

  const PageA({super.key});
  @override
  _PageAState createState() => _PageAState();
}

class _PageAState extends State<PageA> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text('PageA'),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            ElevatedButton(
                child: const Text('To PageB'),
                onPressed: () async {
                  Navigator.pushNamed(context, PageB.routeName).then((value) {
                    print(
                        'Got result'); //Never gets called when back from pageD
                  });
                })
          ],
        ),
      ),
    );
  }
}

class PageB extends StatelessWidget {
  static const routeName = '/PageB';

  const PageB({super.key});
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text('PageB'),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            ElevatedButton(
                child: const Text('To PageC'),
                onPressed: () {
                  Navigator.pushNamed(context, PageC.routeName);
                })
          ],
        ),
      ),
    );
  }
}

class PageC extends StatelessWidget {
  static const routeName = '/PageC';

  const PageC({super.key});
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text('PageC'),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            ElevatedButton(
                child: const Text('To PageD'),
                onPressed: () {
                  Navigator.pushNamedAndRemoveUntil(context, PageD.routeName,
                      ModalRoute.withName(PageA.routeName));
                })
          ],
        ),
      ),
    );
  }
}

class PageD extends StatelessWidget {
  static const routeName = '/PageD';

  const PageD({super.key});
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text('PageD'),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            ElevatedButton(
                child: const Text('Pop'),
                onPressed: () {
                  Navigator.pop(context, 'Result');
                })
          ],
        ),
      ),
    );
  }
}

flutter doctor -v (mac)
[✓] Flutter (Channel master, 3.7.0-13.0.pre.131, on macOS 13.1 22C65 darwin-arm64, locale en-IN)
    • Flutter version 3.7.0-13.0.pre.131 on channel master at /Users/mahesh/Development/flutter_master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 0196e6050b (2 days ago), 2022-12-31 11:10:23 -0500
    • Engine revision 932591ec04
    • Dart version 3.0.0 (build 3.0.0-76.0.dev)
    • DevTools version 2.20.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 33.0.0-rc4)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0-rc4
    • ANDROID_HOME = /Users/mahesh/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 14.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14A400
    • CocoaPods version 1.11.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)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 61.2.4
    • Dart plugin version 212.5080.8

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

[✓] Connected device (3 available)
    • iPhone 12 Pro (mobile) • 026D5789-9E78-4AD5-B1B2-3F8D4E7F65E4 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-5 (simulator)
    • macOS (desktop)        • macos                                • darwin-arm64   • macOS 13.1 22C65 darwin-arm64
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome 108.0.5359.124

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[✓] Flutter (Channel stable, 3.3.9, on macOS 12.6 21G115 darwin-arm, locale en-IN)
    • Flutter version 3.3.9 on channel stable at /Users/mahesh/Development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision b8f7f1f986 (24 hours ago), 2022-11-23 06:43:51 +0900
    • Engine revision 8f2221fbef
    • Dart version 2.18.5
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc4)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0-rc4
    • ANDROID_HOME = /Users/mahesh/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 14.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14A400
    • CocoaPods version 1.11.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)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 61.2.4
    • Dart plugin version 212.5080.8

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

[✓] Connected device (3 available)
    • iPhone 12 Pro (mobile) • 026D5789-9E78-4AD5-B1B2-3F8D4E7F65E4 • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-14-5 (simulator)
    • macOS (desktop)        • macos                                • darwin-arm64   • macOS 12.6 21G115 darwin-arm
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome 107.0.5304.110

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

cc: @chunhtai


Required php version

Thank you @uzairwp for this MR.
Could you please add a short description and check the failing unit tests?
Thank you again!

This PR was closed because it has been inactive.


infoWindow content is not updating

	mapReadyHandler(evt){
		evt.object.infoWindowTemplate = `
			<FlexboxLayout flexDirection="column" style="width: 200; height: 200; background-color: blue;">
				<Label text="{{userData.addr}}" style="flex-shrink: 0; color: red;" />
			</FlexboxLayout>
		`;
	}

Hi, I have the above code. Whenever I click on each marker at the first time. The userData.addr shows correctly. However, when I further update the userData.addr to other value. The content in the info windows is not updated anymore even though I close and reopen the same info window (by clicking on the marker again).
How can I achieve into window content update? Thanks in advance.

See my similar issue: https://github.com/dapriett/nativescript-google-maps-sdk/issues/372

@dlcole This is the fastest reply I ever get in github issue.   Thanks   haha


Document periodic maintenance tasks (Stack snapshot update, cache clear)

In #435 we update to lts-7.9.
Is there a rule for how often we want to do this? For example, lts-7.15 is out now.
Or is it just "we update whenever someone feels like it"?
Let's see when a few versions were released since 7.9:

2016-11-14
2016-11-22
2016-11-28
2016-12-04
2016-12-12
2016-12-18
2017-01-08

Okay, so that means (normally) weekly. I don't think we particularly want to update every week. So, do we want to adopt some sort of thing like "let's update every month", or do we want it to be looser, like "we'll update if something is broken, otherwise we won't"?

Any snapshot update generates additional downloads and compilation to the users, so I always avoided updating too frequently.

Minor number updates usually require small downloads and some additional compilation, but they are generally safe. I guess they are supposed to only add new packages and make non-breaking updates to the existing packages (changes to the patch number).

Major number updates require a lot of downloads and compilation, in some cases forcing download of a new GCC. Most of the time they reduce the number of available package.

I believe we can periodically update minor numbers, to allow more packages and also receive some non-breaking updates, but the major number bumps should be decided in a by-case basis.
We may also need to clear and rebuild the Travis-CI cache from time to time because of the updates, to check that everything builds from nothing - as expected - and to reduce the cache size, that keeps increasing as we build multiple snapshots. Usually I only do that when we change .travis.yml.

I believe we can periodically update minor numbers, to allow more packages and also receive some non-breaking updates, but the major number bumps should be decided in a by-case basis.

Makes sense. How often do you think minor updates should be done? A month? Two months? Longer? Is there even a need for a set schedule?

We may also need to clear and rebuild the Travis-CI cache from time to time because of the updates, to check that everything builds from nothing - as expected - and to reduce the cache size, that keeps increasing as we build multiple snapshots.

Hmm... seems like it would be good to have these maintenance tasks written down somewhere so that we can be reminded of them (and/or any future maintainers)

Is there even a need for a set schedule?

For minor updates, anytime someone feels it is too old seems good enough IMHO.This way is is up the one opening the PR if it is a week or a few months. :)

Hmm... seems like it would be good to have these maintenance tasks written down somewhere so that we can be reminded of them (and/or any future maintainers)

If the cache gets too big, it will probably timeout when updating or downloading it, so rebuild times will get bigger. We'll probably notice that, so I'm not too worried about it for now.
That said, I may be useful for new maintainers as you pointed out.

depending on what model we decide for #416, keeping up to date with x-common may also be a task to be documented. I would document that, but since it's non-Haskell code I didn't want to inflict my code upon others. Anyway, I just run the script when I feel like it, no particular set schedule, just when I feel like things may be getting out of date

to reduce the cache size,

let's see. Current cache size, 2202.35MB, I do not know when it was last cleared.

After rebuild, which was triggered by me https://travis-ci.org/exercism/haskell/builds/357633588, cache size 921.02MB

issue title: rename x-common to problem-specifications

So basically this is about documentation that is useful for maintainers.
Consider also talking about the merging strategy, which, in brief, is:

If the PR contains only one change and therefore is suitable to become one commit:

Slight preference for Squash and Merge. Create a Merge Commit is acceptable only if the PR was submitted as one commit.
Only if Squash and Merge is going to be used, Update from Master is acceptable. (Since Update from Master causes the "submitted as one commit" to be false, this should follow logically from the above)

If the PR contains multiple changes and therefore must remain as separate commits:

Only Create a Merge Commit makes sense. Squash and Merge loses individual commits. Rebase and Merge makes the link to the PR only available when viewing the individual commits via web, which is too inconvenient.
Update from Master is unusable in this situation. Ask the submitter to rebase on master, or possibly do it yourself if the submitter left the "Allow edits from maintainers" box checked.


Incompatible with Terraform 0.7.3

The module does not work with the variable handling changes introduced in Terraform 0.7.3. In the Terraform change log it sounds like variables and outputs can't use the same name anymore. When I run a terraform plan for this module with 0.7.3 it asks for the values of var.prefer_hvm and var.prever_pv.

Had a look at this, appears to be a JSON key issue hashicorp/terraform#5140 (that will be fixed in 0.7.4)

Running Terraform v0.7.4-dev built from HEAD this morning, and I still have this issue:

Error loading Terraform: module virttype: required variable prefer_pv not set

I think I have just fixed it in #3 . Thanks everyone!


[Bug] Unable to create new Spring Boot application with the latest version of NX

Plugin Name
@nxrocks/nx-spring-boot
Nx Report

 NX   Report complete - copy this into the issue template

Node           : 20.18.0
OS             : linux-x64
Native Target  : x86_64-linux
bun            : 1.1.30

nx             : 20.0.0
@nx/js         : 20.0.0
@nx/eslint     : 20.0.0
@nx/workspace  : 20.0.0
@nx/angular    : 20.0.0
@nx/devkit     : 20.0.0
@nx/vite       : 20.0.0
@nx/web        : 20.0.0
@nx/webpack    : 20.0.0
typescript     : 5.6.3
---------------------------------------
Community plugins:
@analogjs/content             : 1.8.2
@analogjs/platform            : 1.8.2
@analogjs/router              : 1.8.2
@analogjs/vite-plugin-angular : 1.8.2
@nxrocks/nx-spring-boot       : 10.2.6

### Expected Behaviour

Create a project using `nx g @nxrocks/nx-spring-boot:project`.

### Actual Behaviour

```~/Workspace/Work/Bedrock git:[main] bunx nx g @nxrocks/nx-spring-boot:project test --verbose

 NX  Generating @nxrocks/nx-spring-boot:project

✔ What kind of project are you generating? · application
✔ Which build system would you like to use? · maven-project
✔ Which packaging would you like to use? · jar
✔ Which version of Java would you like to use? · 22
✔ Which language would you like to use? · java
✔ What groupId would you like to use? · com.test
✔ What artifactId would you like to use? · test
✔ What package name would you like to use? · com.test.api

 NX   Cannot read properties of undefined (reading 'replace')

TypeError: Cannot read properties of undefined (reading 'replace')
    at removeWindowsDriveLetter (/home/user/Workspace/Work/Bedrock/node_modules/nx/src/utils/path.js:9:27)
    at normalizePath (/home/user/Workspace/Work/Bedrock/node_modules/nx/src/utils/path.js:16:12)
    at determineProjectNameAndRootOptions (/home/user/Workspace/Work/Bedrock/node_modules/@nx/devkit/src/generators/project-name-and-root-utils.js:10:58)
    at normalizeOptions (/home/user/Workspace/Work/Bedrock/node_modules/@nxrocks/nx-spring-boot/src/generators/project/lib/normalize-options.js:6:144)
    at projectGenerator (/home/user/Workspace/Work/Bedrock/node_modules/@nxrocks/nx-spring-boot/src/generators/project/generator.js:9:64)
    at /home/user/Workspace/Work/Bedrock/node_modules/nx/src/command-line/generate/generate.js:238:32
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async handleErrors (/home/user/Workspace/Work/Bedrock/node_modules/nx/src/utils/handle-errors.js:9:24)
    at async Object.handler (/home/user/Workspace/Work/Bedrock/node_modules/nx/src/command-line/generate/command-object.js:14:22)

### Steps to reproduce the behaviour

1. Create new nx workspace with "none" preset
2. Install @nxrocks/nx-spring-boot
3. Try and create a spring boot application

It seems like the directory is null when logging out the options in normalize-options.js

Hi @Divaaaaaan
Thanks for reporting this, I'll have a look and provide an update soonish.
Stay tuned!

@tinesoft Just an update, seems like things are not playing well together when I edited the file :sweat_smile: so will wait for the update rather before continuing.

Having a look at the Nx plugin registry, it supports the Nx version between 16 and 18. When will the plugin be updated accordingly?

Hi @Divaaaaaan.
"In Nx 20, generating projects will no longer derive the name and root"
So the correct way to create projects now is:
nx g @nxrocks/nx-spring-boot:project testapp --directory testapp
This same change affects both Spring Boot and Flutter projects in Nx 20.

Hi @Divaaaaaan.
"In Nx 20, generating projects will no longer derive the name and root"
So the correct way to create projects now is: nx g @nxrocks/nx-spring-boot:project testapp --directory apps/testapp  This same change affects both Spring Boot and Flutter projects in Nx 20.

I seem to have this exact same problem here, I do not seem to understand how to do the fix you suggested on my end.

@lordvins226 thank you very much, it works for me. you save my time.

i got the some problem and try to fix but it not work.
how to fix this problem ?

lordvins226, hello! Thank you very much for providing a workaround! :heartbeat:

i got the some problem and try to fix but it not work.
how to fix this problem ?

correct command: npx nx g @nxrocks/nx-spring-boot:project ecom-backend --directory apps/ecom-backend


WIP Feature/issue 606 send multiple RPCS

WIP
Fixes #606
This PR is not ready for review.
Risk
This PR makes minor API changes.
Testing Plan
[Describe how you plan to unit test the changes in this PR]
Summary
[Summary of PR changes]
Tasks Remaining:

[ ] Finish Async method
[ ] Finish synchronous method
[ ] Unit tests
[ ] Tests against head unit

CLA

[X] I have signed the CLA

Codecov Report

Merging #685 into develop will decrease coverage by 0.08%.
The diff coverage is 2.77%.

@@             Coverage Diff              @@
##             develop    #685      +/-   ##
============================================
- Coverage      41.29%   41.2%   -0.09%
  Complexity      2643    2643
============================================
  Files            360     361       +1
  Lines          15705   15741      +36
  Branches        1656    1659       +3
============================================
+ Hits            6485    6486       +1
- Misses          8936    8971      +35
  Partials         284     284

Impacted Files
Coverage Δ
Complexity Δ

...ink/proxy/rpc/listeners/OnRPCResponseListener.java
62.5% <ø> (ø)
2 <0> (ø)
:arrow_down:

...proxy/rpc/listeners/OnMultipleRequestListener.java
0% <0%> (ø)
0 <0> (?)

...n/java/com/smartdevicelink/proxy/SdlProxyBase.java
5.44% <5.26%> (-0.01%)
6 <0> (ø)

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 41b0d7d...71a22c8. Read the comment docs.


Optionally support profiles in credentials for cicd in multiple accounts

I am using a multi-account structure for my environments, and would like to be able to pass in an (optional) profile name so that I can use a simpler pattern in getting the aws credentials to this action.

I will close this, as using the AWS_PROFILE env variable solved my problem, apologies.


Dialogs should get focus by default

The mwc-dialog component will only move initial focus onto the dialog when the dialogInitialFocus attribute is set on a slotted element.  If not set, focus remains on the element that opened the dialog and must be moved to the dialog manually.  This creates inaccessibility for assistive technology and is a WCAG failure.
I would recommend a change such that initial focus has a default inside the dialog when the attribute is not set, such as the least destructive action button or the heading text using tabindex="-1".  There's no reason for a lazy implementation to be less accessible.

Thanks for the bug report! Adding to our backlog

@asyncLiz maybe this is the behavior the  getInitialFocusEl function at mwc-dialog-base.ts is doing? it seem that the focusable element should is supposed to be dialogInitialFocus would be good to change to .mdc-dialog ?

Obsolete with M3's dialog


Format URL to show clickable 'website' button instead of whole url

This could be handled it three ways:

Frontend should scan for 'http' in data and then replace content with 'website' word. Drawback - if some data would have two websites, every would be treated same way
Frontend could get some specific formatting, e.g. besides data, backend could also serve format, or data type. It could be sth like that {data:{name: point1, website: {type: hyperlink, value: www...}}} or sth like makrdown {data:{name: point1, website: (website)[www...]}
Frontend can serve only one webpage and it has reserved keyword for value 'www' or 'website'.

Choose one or suggest another approach.

@kacper-cyra will take this issue


bug(zero-bin): Inconsistent async failures on block batches

When proving batches of blocks (size 10), I got several issues with output as follows:
Error: Failed to send proof

Stack backtrace:
   0: anyhow::error::<impl anyhow::Error>::msg
   1: <futures_util::future::future::flatten::Flatten<Fut,<Fut as core::future::future::Future>::Output> as core::future::future::Future>::poll
   2: <futures_util::future::future::Then<Fut1,Fut2,F> as core::future::future::Future>::poll
   3: <S as futures_core::stream::TryStream>::try_poll_next
   4: <futures_util::stream::try_stream::try_collect::TryCollect<St,C> as core::future::future::Future>::poll
   5: prover::ProverInput::prove::{{closure}}
   6: leader::client::client_main::{{closure}}
   7: leader::main::{{closure}}
   8: tokio::runtime::park::CachedParkThread::block_on
   9: tokio::runtime::context::runtime::enter_runtime
  10: tokio::runtime::runtime::Runtime::block_on
  11: leader::main
  12: std::sys_common::backtrace::__rust_begin_short_backtrace
  13: std::rt::lang_start::{{closure}}
  14: std::rt::lang_start_internal
  15: main
  16: <unknown>
  17: __libc_start_main
  18: _start

The errors are inconsistent between runs, but we should add some strengthening mechanism (with possibly some retry-upon-error kind of behavior), to prevent this.
I've been running as follows:
for n in {20175010..20180000..10}
do
    ./prove_rpc.sh $n $((n+9)) endpoint native true 1000 1000 test_only
done

(note that these block ranges are past Cancun upgrade, they have been ran against fix/native_cancun branch)

Fixed with increasing the ulimit: ulimit -n 4096

Seems there are still some sporadic issues with even ulimit -n 16384.
Ran with for n in {20175180..20180000..10}; do time ./prove_rpc.sh $n $((n+9)) rpc_url native true 1000 1000 test_only; done

Maybe this is a bit of an aside, but I'll bet that the error:
Error: Failed to send proof

is probably an anyhow Result and that only the most recent context is getting printed and not the other contexts that are added as it calls down the stack. Probably with the rest of the contexts it might have given more of a hint that we were running out of file descriptors.

I will look into this in more depth soon

Fixed with https://github.com/0xPolygonZero/zk_evm/pull/369


Update aws-java-sdk-dynamodb to 1.12.450

Updates com.amazonaws:aws-java-sdk-dynamodb from 1.11.1034 to 1.12.450.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "aws-java-sdk-dynamodb" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.amazonaws", artifactId = "aws-java-sdk-dynamodb" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #430.


[FEATURE] Support more flexible pattern for auto-follow

Is your feature request related to a problem?
In documentation there is information that pattern parameter for auto-follow currently only supports wildcard matching. We have issue when we need to replicate all but a few indices.
For example, we don't want to replicate indices starting with ..
What solution would you like?
It could be more flexible pattern or additional optional parameter in auto-follow configuration to exclude some indices.

Duplicate of https://github.com/opensearch-project/cross-cluster-replication/issues/265

This will be a very nice to have feature. We have also same use-case.


chore: removing fsevents dependency

SUMMARY

In a prior PR, I moved this from an Optional Dependency to a Dependency, along with several other package changes, to get CI to start working again. Since this isn't used directly by superset (as far as I can see) I figured it's worth yanking it entirely now to see if CI still passes.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN

🤞 CI
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

By the way, i think having fsevents as a normal dep isn't the right thing to do, as it breaks non mac environments. I think removing the dep altogether should be fine

Ugh... what a troublesome package! Merging this for now.


Can you upload multi-part form data?

Does pyresttest allow tests on the submission of multi-part form data? Specifically, sending some values and an image file. This is how I send the request via cURL:
curl -X POST -F "data1=value1" -F "data2=value2" -F<EMAIL_ADDRESS>"http://localhost:5000/endpoint"

Hi, thank you for reaching out with your question.  PyRestTest doesn't have any explicit support for multipart form data, but it is possible to construct one manually and specify it as the post body.
This is similar to constructing a manual form request: https://github.com/svanoort/pyresttest/tree/master/examples/dummyapp-posting-forms.yaml
There's a standing enhancement request for greater support of form data and other custom request bodies, in https://github.com/svanoort/pyresttest/issues/115.
I'll go ahead and convert this to a proposed enhancement to tackle in the next couple releases.

Ok, looking forward to see this implemented. In case anyone is interested in testing multi-part form data, here's what I did:
Create a file with the multipart-form data. For example:
`--------------------------4935875673ad6222
Content-Disposition: form-data; name="username"
george
--------------------------4935875673ad6222
Content-Disposition: form-data; name="file"; filename="image.jpg"
Content-Type: image/jpeg
Content-Transfer-Encoding: base64
/9j/4AAQSkZJRgABAQAAAQABAAD/2wBDA
--------------------------4935875673ad6222--
Set the appropriate headers and load the data into the body of the request.- test:

group: "Group test"
name: "Test name"
url: "/endpoint"
method: "POST"
headers: {'Content-Type': 'multipart/form-data; boundary=------------------------4935875673ad6222'}
body: {'file':'formdata.txt'}
expected_status: [200]`

Clue - https://automatthias.wordpress.com/2013/04/07/http-put-with-multipartform-data-using-pycurl/

I'm trying to test multipart/form-data using pyresttest using the above way but I'm getting
'unicodeescape' codec can't decode bytes in position 156-157: truncated \UXXXXXXXX escape error.


Explicitly export createServerRenderContext

This adds createServerRenderContext to the main exports file, allowing it to be accessed exactly as it is in the v4 docs website.

Thanks!

no problem.

Don't people will be able to try out server rendering without a new release btw.

out of interest, do you have a release schedule or do you know when the next one (with this fix) in it will be?
i'm not too worried, i'll use npm link until it's out...

you can require it with react-router/createServerContext before the new release.

unfortunately I don't think the above solution (changing the `require)  is enough.
Using tag 4.0.0-2 : I get ReferenceError: location is not defined
Using branch v4 : no errors
this is my middleware to render the app on the server.
import React from 'react';
import { renderToString } from 'react-dom/server';
import { ServerRouter/* , createServerRenderContext */ } from 'react-router';
import createServerRenderContext from 'react-router/createServerRenderContext';

import { makeRoutes } from '../../app/routes';

const createMarkup = (req, context) => renderToString(
  <ServerRouter location={req.url} context={context} >
    {makeRoutes()}
  </ServerRouter>
);

const setRouterContext = (req, res, next) => {
  const context = createServerRenderContext();
  const markup = createMarkup(req, context);
  const result = context.getResult();
  if (result.redirect) {
    res.redirect(301, result.redirect.pathname + result.redirect.search);
  } else {
    res.status(result.missed ? 404 : 200);
    res.routerContext = (result.missed) ? createMarkup(req, context) : markup;
    next();
  }
};

export default setRouterContext;

as I say, v4 branch works so no bugs to fix. Just thought you'd want to know if it affects when to release the next update.


Refactor old cc pkg upload API

Refactor old chaincode package upload API according to the new design doc.
Signed-off-by: xichen1<EMAIL_ADDRESS>

The original API implementation requires the user to upload a zipped chaincode file, then the backend will package the the cc file using peer command line.
According to our new API design, now we need the user to package the cc package by themselves and upload the cc package directly. Therefore adjust the current implementation to allow the requirement.
The PR also updated the cc Django model, the current db columns include uuid, package_id, name, label, version, creator, language, description and create_ts.

One issue still exists is it's impossible to get cc version from the metadata.json file (it doesn't contain the version info).
Do we update the version in the backend automatically? (if a duplicate cc package id is received we increase the version?)

Need to simplify the extraction and verification steps. Only need to extract metadata.json file and check and store its information. It can be done using the library tarfile:
    with tarfile.open(tar_file_path, "r:gz") as tar:
        try:
            # Retrieve the member information for the specified file
            member = tar.getmember("metadata.json")
            # Extract the file
            tar.extract(member, path=output_path)
        except KeyError:
            print(f"File '{file_name}' not found in the archive.")

One issue still exists is it's impossible to get cc version from the metadata.json file (it doesn't contain the version info).
Do we update the version in the backend automatically? (if a duplicate cc package id is received we increase the version?)
Update: It seems cc name and version can only be created in Approve step (to create a new running instance), which needs to be confirmed.

Confirmed: cc names and versions are decided at Approve step. They are tied with the cc and one channel specified at Approve step.


[local-cli] Add support for custom log reporter cli option for local server

Motivation (required)
In Expo tools such as XDE, exp we listen listen to stdout from the packager process and print it in our own buffer. In the case of XDE, an electron app, our log pane is DOM-based, and before printing each log chunk we need to remove special tty characters and sometimes parse it to get information that we need (eg: progress bar). By using a custom reporter, we can take the raw events and pass them along in a format that is easy to consume by XDE and exp. This same motivation applies to create-react-native-app, where we currently don't show a progress bar in the terminal, but we can with this change.
Test Plan (required)
Create LogReporter.js in the root of a project with the CLI changes included in this PR.
class LogReporter {
  update(event) {
    console.log(JSON.stringify(event));
  }
}

module.exports = LogReporter;

Now, run react-native start --customLogReporterPath=LogReporter.js -- all of the raw events will be output as JSON (while the logs that do not go through the reporter, such as the "banner", will remain as-is).
Future considerations that don't prevent this from shipping

Should we add this option to bundle and unbundle? I don't have a need for this within the context of Expo but it likely makes sense for consistency.
Speaking of consistency, naming style for CLI arguments is inconsistent between bundle and start -- bundle uses kebab-case and start mostly uses camelCase (exception is resetCache/reset-cache where both are provided, I followed this example for customLogReporterPath/custom-log-reporter-path). Should add the option to use kebab-case for all start options and deprecate the camelCase alternative?
Are the raw log events likely to change significantly? If so, any changes to these should probably be documented as breaking changes in the release notes in the future.

Thanks for the PR. We may want to add a comment here noting that changes to events could be considered breaking changes, that way anyone touching that file will have to report the breaking change to us and it will be noted in the release notes.
Regarding casing, it looks like both kebab-case and camelCase are accepted for all start flags, even though resetCache is the only one to make a note of it. At least I don't see any special casing for resetCache. If this turns out to be the case for bundle as well, then I would say the best way to address this would be to pick one case to document in the CLI help output for both start and bundle, and silently support the other case as well. I don't see any harm in supporting both.

@hramos - any info on what failed?

@brentvatne looks like some trouble rebasing unto our internal codebase. Giving it another try.


Make Tenant Id a first class Wolverine citizen

Multi-tenancy is coming up a lot, and it'd be nice to see tenancy reflected in monitoring and tracing

Tasks

[ ] Envelope.TenantId
[ ] above prop is mapped end to end w/ EnvelopeSerializer
[ ] TenantId should be propagated to responses and/or cascading messages.
[ ] Copied to envelopes when routed
[ ] Written in all Otel activity tracing
[ ] Written as header in metrics tracking
[ ] Some way to propagate via policy from message body???
[ ] Some way to propagate "X-tenant-id" from HTTP request???
[ ] Overwrite Envelope.TenantId from DeliveryOptions ???
[ ] Dedicated ITenantedMessage interface for messages?
[ ] Dedicated [TenantId] attribute?

Closed by https://github.com/JasperFx/wolverine/commit/b5684a8e94aed8bd7c6492fba9f5d4dc322e7d3c


portfolio: Filled order quad text sizing

existing tix for numeric values for portfolio.
Also whole table row in filled orders needs to be 11px.
Market title needs to be 12px.

@matt-bullock please review and close if this looks correct

outcome should be medium in weight (500)

@phoebemirman comment on this issue.

@matt-bullock double check this is correct and close if it is

closing


RHOAIENG-1669 - Modified the Request Size for Manager

The issue resolved by this Pull Request:
Resolves RHOAIENG-1669
Description of your changes:
Leveraging Vertical Pod Autoscaling recommender , I got values suggested for the request size to be a bit more when I had a single DSPA deployed along with DSPO.
I took the safe route of taking the minimum suggested values to modify the request size for manager by the Jira Reporter instead as it is recommended to leverage Vertical Pod Autoscaling for atleast a week before considering the suggested values.

Testing instructions

Deploy DSPO
Deploy DSPA and see if the sample pipeline works as it should.

Checklist

[X] The commits are squashed in a cohesive manner and have meaningful messages.
[X] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[X] The developer has manually tested the changes and verified that the changes work

/lgtm
/approve


How to only fine-tune the image encoder?

When I want to feed only the parameters of the image encoder (self.model.encode_image.parameters()) into the optimizer, it shows that "AttributeError: 'function' object has no attribute 'parameters'". It's ok for "self.model.parameters()".
Anyone knows how to solve this problem?

man,cause that's a function not A module,try with the "self.model.visual"

man,cause that's a function not A module,try with the "self.model.visual"

It's been resolved in the same way, thank you.

man,cause that's a function not A module,try with the "self.model.visual"
It has been solved in the same way, thank you.

When I want to feed only the parameters of the image encoder (self.model.encode_image.parameters()) into the optimizer, it shows that "AttributeError: 'function' object has no attribute 'parameters'". It's ok for "self.model.parameters()".
Anyone knows how to solve this problem?

I met the same question,bro. Could u please help me about the solution you took


Replace existing data into a rendered template that already exist and has been called once

Hello, I'm using handlebars into my edit forms, each page has different edit forms therefore I have created different php files for each page. The structure of my html code is that I have a div (with id edit_content) and inside that div i have my script (The script where the handlebars will use to compile and print it). On the same page I made my function of the handlebars that will collect the data from a json request and put them into the edit form. I'm using the .append function to append my compiled template into the edit_content div. Now when you click on a row for the first time it loads fine the edit form with the data of the clicked row. Then when you click on any next row it will show the edit form but with the values of the first clicked row. The problem I know is because i'm using .append, I tried to clean the contents of the edit_content div but it also removes the script tag with the template that i want to render. How I can replace the data of the previews clicked row with the new data that are coming from the ajax? Thank you

Ok i found the solution, basically i'm checking if the first's div class is equal to box, that means the edit form has been printed, so then next, i'm using remove function to remove the div with the class box and whatever contains.

Ok i found the solution, basically i'm checking if the first's div class is equal to box, that means the edit form has been printed, so then next, i'm using remove function to remove the div with the class box and whatever contains.


ModuleNotFoundError: No module named 'netbox_ipcalculator'

ModuleNotFoundError: No module named 'netbox_ipcalculator'
Following the instructions but get this error. Last issue is closed without solution
This file /opt/netbox/local_requirements.txt is not present at my installation. Only base_requirements.txt so i put the line netbox-ipcalculator in there, maybe false.

Ok, found.
Put netbox-ipcalculator in requirements.txt not in base_requirements.txt

and better: create a file named local_requirements.txt (if not already existing)
it can be so easy with a hint in readme


CameraTools to BDArmory (Continued) development team

As advised in KSP-CKAN/CKAN-meta#1236
Heads-up to @jrodrigv, @Nerfclasher

Looks good, merging


feat(dotfiles): add ability to run apply dotfiles as root

In my template (basic-env), dotfiles are also applied to root.
I like doing this because whenever switching to a root shell for more than one command (e.g installing packages, etc), my shell is consistent with my user.
I have added a root parameter to the module which will apply the dotfiles using sudo.

module "dotfiles" {
  source = "git::https://github.com/phorcys420/coder-modules.git//dotfiles?ref=dotfiles-root"
  agent_id = coder_agent.dev.id
  root = true
}

Hmm. Can you run bun fmt and bun lint to fix the formatting issues?

Yes, sorry, I'm not used to formatting every commit yet.

it seems like the CI has more formatting/linting rules than my local branch does, e75b62f was all good on my end (bun fmt and bun lint both exited without modifying anything or erroring yet the CI still fails)

lol, looks like i messed up, let me do some cleaning up.

sorry for all the noise, now this should be good.

I didn't mean to close, i'm starting off of a clean slate, which is probably what triggered it to close.

hey @mafredri, while writing this PR, I realized that the script running the dotfiles is named "personalize", do you want me to rename it to "dotfiles" in this PR even though it's not really it's scope, or should I open another PR ? to fix it
resource "coder_script" "personalize" {
  agent_id = var.agent_id
  script = templatefile("${path.module}/run.sh", {
    DOTFILES_URI : local.dotfiles_uri,
  })
  display_name = "Dotfiles"
  icon         = "/icon/dotfiles.svg"
  run_on_start = true
}

sorry for all the noise, but given that terraform modules can only be loaded via an URL, I have to push debug commits and then force-push to clean my branch.
here is an example of what you can do with this PR :
module "dotfiles" {
  source = "git::https://github.com/phorcys420/coder-modules.git//dotfiles?ref=dotfiles-root"
  agent_id = coder_agent.dev.id
  #dotfiles_uri = "<defined by template admin>"
}

module "dotfiles-root" {
  source = "git::https://github.com/phorcys420/coder-modules.git//dotfiles?ref=dotfiles-root"
  agent_id = coder_agent.dev.id
  user = "root"
  dotfiles_uri = module.dotfiles.dotfiles_uri # "<defined by template admin>" if uncommented, or the value the end user provided in template settings
}

I have tested all the following scenarios and they are working :

single module without dotfiles_uri defined

asks the user on template creation
applies dotfiles to the default user (coder)

single module with dotfiles_uri defined

doesn't ask the user on template creation
applies dotfiles to the default user (coder)

single module without dotfiles_uri defined with user = "root"

asks the user on template creation
applies dotfiles to the root user

single module with dotfiles_uri defined with `user = "root"

doesn't ask the user on template creation
applies dotfiles to the root user

module without dotfiles_uri defined + module with dotfiles_uri = module.dotfiles.dotfiles_uri

asks the user on template creation once and uses the same URI when applying both times
applies dotfiles to the default user (coder)

module with dotfiles_uri = "<defined by template admin>" + module with dotfiles_uri = module.dotfiles.dotfiles_uri

doesn't ask the user at all
applies dotfiles to the default user (coder)

@mafredri I would like your input on these things.

main.tf
variable "dotfiles_uri" {
  type        = string
  description = "The URL to a dotfiles repository. (optional)"

  default = null
}

locals {
  dotfiles_uri = var.dotfiles_uri != null ? var.dotfiles_uri : data.coder_parameter.dotfiles_uri[0].value
  user         = var.user != null ? var.user : ""
}

currently, var.user's default is null and I use a ternary operator to send an empty string ("") if it's null because templatefile() doesn't take null arguments.
I think this is ugly, but while I could set var.user's default to an empty string (""), I think it doesn't make sense that the default is not null if nothing was passed.

run.sh
if [ -n "$${DOTFILES_URI// }" ]; then
  if [ -z "$DOTFILES_USER" ]; then
    DOTFILES_USER="$USER"
  fi
fi

In this section, I use [ -z "$DOTFILES_USER" ] when I could theoretically use [ "$${DOTFILES_USER// }" ] to be more coherent, but I only got it working in my shell and never in the script and ran out of nerve, is it fine if it stays like this ?
Furthemore, I think that the following can look quite confusing :
if [ -n "$${DOTFILES_URI// }" ]; then
  if [ "$${DOTFILES_USER// }" ]; then
    DOTFILES_USER="$USER"
  fi
fi

Currently, var.user's default is null and I use a ternary operator to send an empty string ("") to templatefile() if it's null because templatefile() doesn't take null arguments. I think this is ugly, but while I could set var.user's default to an empty string (""), I think it doesn't make sense that the default is not null if nothing was passed.

Hmm, defaulting to the empty string should be fine, I don't think null conveys any additional information in this instance. However, perhaps this is a problem for this implementation.
Ultimately, for this to work as expected, we would need the output dotfiles_uri from module A to always be a non-empty string. Otherwise module B can't determine whether or not it has been defined.
Maybe we need to scrap the idea? 😔

In this section, I use [ -z "$DOTFILES_USER" ] when I could theoretically use [ "$${DOTFILES_USER// }" ] to be more coherent, but I only got it working in my shell and never in the script and ran out of nerve, is it fine if it stays like this ? Furthemore, I think that the following can look quite confusing :

My recommendation would be to clean up the input in Terraform and keep the shell script simple(r).
  script = templatefile("${path.module}/run.sh", {
    DOTFILES_URI : trimspace(local.dotfiles_uri),
    DOTFILES_USER : trimspace(local.user)
  })

This way, we don't need ${...// }.
if [ -n "$DOTFILES_URI" ]; then
  if [ -z "$DOTFILES_USER" ]; then
    DOTFILES_USER="$USER"
  fi
  # ...

Ultimately, for this to work as expected, we would need the output dotfiles_uri from module A to always be a non-empty string. Otherwise module B can't determine whether or not it has been defined.

I don't see the issue, because this scenario where an empty string is returned from module A only happens if the end user didn't provide any dotfiles URI or if we set dotfiles_uri = "", therefore we don't have to apply anything in module B either.
Could you elaborate a bit ? I really don't see how this can cause an issue.

f var.dotfiles_uri == null, then module A's output.dotfiles_uri value will be the coder_parameter's value.

And this can empty as dotfiles are the optional user can leave the coder_aparmeter empty.

f var.dotfiles_uri == null, then module A's output.dotfiles_uri value will be the coder_parameter's value.

And this can empty as dotfiles are the optional user can leave the coder_aparmeter empty.

yes but then nothing is done with the other module either, it will not error just not do anything.

hey all, i see this is becoming stale, have you got the time to take a look @mafredri ?

hey!
sorry for letting this PR become stale, I went ahead and applied the changes you suggested.

@phorcys420 can you rebase it?

hey @matifali, just resolved the merge conflict, there was an error in the docs where the variable name was default_dotfiles_repo instead of default_dotfiles_uri so I corrected that.
Also, does it make sense that there is a dotfiles_default_uri output? I don't see how this could be useful.
output "dotfiles_default_uri" {
  description = "Dotfiles Default URI"
  value       = var.default_dotfiles_uri
}

Another thing, could you review the README.md to see if it makes sense to you?
I think the section about default dotfiles URI might be better somewhere else, but I don't really know.

@phorcys420 having an output doesn't do any harm but could be helpful for some users, so I did not remove it. I agree that to doesn't add much value as its not anything computed but a direct output from an input.
Let's remove that.

@matifali do you want me to remove it in this PR?

@phorcys420 We can do it in a separate PR and keep the changes related in this PR.
The new PR can fix the typo and remove output.

@matifali so should I apply the change you suggested?
since you said you want to do it in another PR?

#225 does that but we need to wait for someone to approve that :D

oh okay, but I already fixed the typo in this branch @matifali, do you want me to unfix it to keep the changes related to the PR? 😄

@phorcys420 Yes, its better to do ina separate PR.

I have tested the module again after all the changes and I can confirm that it still works as expected.

@phorcys420 Could you rebase it again. :D

@phorcys420 Could you rebase it again. :D

will do!


"X takes 1 positional argument but 2 were given" in command line but not in Spyder

Issue Report Checklist

[x ] Searched the issues page for similar reports
[ x] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[x ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[x ] Tried basic troubleshooting (if a bug/error)

[ ] Restarted Spyder
[ ] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[x ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
I have a script where I'm opening a websocket connection to stream Bitcoin price data from Bybit, and the script runs as expected when I run it in Spyder. However, when I try to run it in cmd or powershell, I get "X takes 1 positional argument but 2 were given" errors, and I can't figure out why. The methods in my websocket class that are giving the errors all include the "self" parameter where they're defined, e.g.:
def _on_open(self):
'''Log WS open.'''
self.logger.debug('WebSocket opened.')
self.opened = True
What steps reproduce the problem?

Run the script in cmd or powershell instead of within Spyder.

What is the expected output? What do you see instead?
I'm currently running a test script that opens the websocket connection, waits five seconds, then closes it again. When I run it in Spyder, I see:
2021-10-03 16:26:13 - Bybit_WS - INFO - Initializing WebSocket.
2021-10-03 16:26:14 - Bybit_WS - INFO - Subscription to trade.BTCUSD successful.
2021-10-03 16:26:19 - Bybit_WS - INFO - WebSocket closed.
but when I run it in, e.g., cmd, I see:
2021-10-03 16:51:11 - Bybit_WS - INFO - Initializing WebSocket.
2021-10-03 16:51:12 - websocket - ERROR - error from callback <bound method MyWebSocket._on_open of <Bybit_WS.MyWebSocket object at 0x000001D0FFD89790>>: _on_open() takes 1 positional argument but 2 were given
2021-10-03 16:51:12 - websocket - ERROR - error from callback <bound method MyWebSocket._on_message of <Bybit_WS.MyWebSocket object at 0x000001D0FFD89790>>: _on_message() takes 2 positional arguments but 3 were given
2021-10-03 16:51:13 - websocket - ERROR - error from callback <bound method MyWebSocket._on_message of <Bybit_WS.MyWebSocket object at 0x000001D0FFD89790>>: _on_message() takes 2 positional arguments but 3 were given
2021-10-03 16:51:15 - websocket - ERROR - error from callback <bound method MyWebSocket._on_message of <Bybit_WS.MyWebSocket object at 0x000001D0FFD89790>>: _on_close() takes 1 positional argument but 2 were given
Versions

Spyder version: 5.05
Python version: 3.8.8
Qt version: 5.9.7
PyQt version: 5.9.2
Operating System name/version: Windows 10

Hey @sebastiang42, thanks for reporting. We need a simple and reproducible code example from you so we can test and debug this problem in our side. Otherwise it won't be possible to help you, sorry.

Hi again,
After digging even deeper, I finally found a clue that resolved the problem. I'm not exactly sure why, but rolling back my websocket-client package from version 0.58.0 to 0.57.0 fixed the problem.


FBP in silx

This PR adds a Filtered Back-Projection (FBP) utility in silx.
For now, the only backend is OpenCL. The GPU version uses textures (image2d_t). There is a CPU version without textures.
The Backprojection kernel is adapted from PyHST2 with Alessandro's permission.

I still have one issue:
======================================================================
ERROR: test_fbp (silx.opencl.test.test_backprojection.TestFBP)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/users/kieffer/workspace-400/silx/build/lib.linux-x86_64-2.7/silx/opencl/test/test_backprojection.py", line 140, in test_fbp
    t, res = self.measure()
  File "/users/kieffer/workspace-400/silx/build/lib.linux-x86_64-2.7/silx/opencl/test/test_backprojection.py", line 117, in measure
    result = self.fbp.filtered_backprojection(self.sino)
  File "/users/kieffer/workspace-400/silx/build/lib.linux-x86_64-2.7/silx/opencl/backprojection.py", line 426, in filtered_backprojection
    self.filter_projections(sino)
  File "/users/kieffer/workspace-400/silx/build/lib.linux-x86_64-2.7/silx/opencl/backprojection.py", line 389, in filter_projections
    self.num_projs
  File "/usr/lib/python2.7/dist-packages/pyopencl/__init__.py", line 515, in kernel_call
    global_offset, wait_for, g_times_l=g_times_l)
TypeError: No registered converter was able to produce a C++ rvalue of type unsigned long from this Python object of type numpy.int32

----------------------------------------------------------------------
Ran 1 test in 0.203s

LGTM
The support of gpyfft is left for later (dependency on clfft & debian9)


Painted Dimensional Transciever Rendering Error

Issue Description:
Painted dimensional transcievers render the transport field in front of the block geometry when active.  Installing Optifine actually fixes this, which is not a sentence I ever expected to type.
Affected Versions (Do not use "latest"):

EnderIO: 1.10.2-3.1.179
EnderCore: 1.10.2-<IP_ADDRESS>-beta
Minecraft: 1.10.2
Forge: 1.10.2-<IP_ADDRESS>2-universal

Transciever painted as Quark Bucket Storage

The order and location in which TESRs are rendered is determined by vanilla/and or Forge code, we do not have any say in it.

I doubt Mojang can be convinced that this represents a bug, I guess the solution is to install Optifine.

I had a look at the code, I'm quite sure we can blame Forge---vanilla doesn't have transparent TESRs at all.
So here's what happens:

The game draws all solid blocks.
The game renders all solid TESRs.
The game renders all translucent blocks.
The game renders all translucent TESRs.

That means a TESR can either render behind all translucent blocks, or in front of them... :(

If I'm understanding that correctly, it is a minor bug in Forge, then.  3 and 4 should render the other way around, no?

It's a bit hard to wrap my brain around it, so I may be wrong: All translucent things should render ordered by distance from the camera. For solid pixels the GPU can track the distance from the camera per pixel, so painting something solid behind some pixels they came from something else will just do nothing. But for translucent things that won't work, as those have to be painted in the correct order for it to look right.

Since our last modpack update, Optifine no longer solves this issue.  Apparently I had a bad config that was subtly glitching the display of all EnderIO blocks in a way that accidentally worked around this specific problem with TESRs.  Looking through my backups in search of the exact version numbers and config.


Adds release notes generation script

This will be used in the new release process to generate draft release
notes that a person edits before clicking publish.
Notably, this correctly annotates co-authors, which is a common practice
in func-e, but easy to miss.
Ex. (nevermind the 'aster' as I'm hacking this to show pending notes)
$ .github/workflows/release_notes.sh master

func-e aster supports X and Y and notably fixes Z
TODO: classify the below into up to 4 major headings and the rest as bulleted items in minor changes
The published release notes should only include the summary statement in this section.
ee700a1 Converts e2e to new Makefile (#356) Adrian Cole, Co-authored-by: Dhi Aurrahman<EMAIL_ADDRESS>83e7c30 updates last known Envoy to 1.19.1 (#355) Adrian Cole,
f975609 Aligns make to func-e color scheme (#354) Adrian Cole,
551840f Scaffold a new Makefile (#353) Adrian Cole,
877a72e Removes bingo for go run (#350) Adrian Cole, Co-authored-by: Takeshi Yoneda<EMAIL_ADDRESS>12a74b1 Adds vanity downloads (#351) Adrian Cole,
0f313c8 Pares down code to work around flake (#349) Adrian Cole,
e74c0b7 Removes test utilities for built-ins (#347) Adrian Cole,
41c2742 Cleans up tests (#348) Adrian Cole,
17375b4 Updates to Go 1.17 (#346) Adrian Cole,
6ae5d48 Corrects manifest path Adrian Cole,
a9ccc4d fixes auth Adrian Cole,
a4bc290 Fixes glitches in package update script (#344) Adrian Cole,
X packages
Don't forget to cite who was involved and why
func-e Y
Minor changes
TODO: don't add trivial things like fixing spaces or non-concerns like build glitches

Z is now fixed thanks to Yogi Bear

Thank you
func-e aster was possible thanks to the following contributors:
Adrian Cole
Dhi Aurrahman
Takeshi Yoneda

e2e tests are failing on centos for an unrelated reason

I'll watch to see if the action glitches are persistent as maybe we get lucky


Link details on merge/replace

This link is very useful for showing different behaviour on merge/patch:
https://github.com/stolostron/governance-policy-framework/blob/main/doc/configuration-policy/README.md#merge-patch
we could link this together with our documentation

will be also documented here https://access.redhat.com/solutions/6316451 and review if being added to further docs

will be covered in a blog which is being worked https://github.com/ch-stark/argocdpoliciesblog/blob/main/blog.md


chore(lib): release<EMAIL_ADDRESS>

What?
This PR updates the lib version for release.

Indeed those were my thoughts. But maybe it's fine to have different versions.

@demetriusfeijoo let me close it, from the history it seems fine as well, so i will only open the PR for CLI.

okidoki @BibiSebi. 🙏
I found a thread about which path we should choose and it was about releasing only the package that had the change, indeed. 🙌


Route sandbox requests via client proxy by using API cache

Route sandbox requests via client proxy by using API cache.
This is a prerequisite for resuming snapshots.

:sparkles: Description by Callstackai
This PR routes sandbox requests via a client proxy using an API cache, which is a prerequisite for resuming snapshots. It introduces a new NodeInfo struct and modifies various parts of the orchestrator to utilize this new structure.

Diagrams of code changes
sequenceDiagram
    participant Client
    participant Nginx
    participant DNS Server
    participant Node
    participant Sandbox

    Note over Client,Sandbox: New DNS Resolution Flow

    Client->>Nginx: Request to sandbox-id-xxx
    Nginx->>DNS Server: Resolve sandbox-id
    DNS Server->>DNS Server: Lookup sandbox IP mapping
    DNS Server-->>Nginx: Return Node IP address

    alt IP Found
        Nginx->>Node: Forward request to Node:3003
        Node->>Sandbox: Handle request
        Sandbox-->>Client: Response
    else IP Not Found
        Nginx-->>Client: Return 404
    end

Files Changed

FileSummary
packages/api/MakefileAdded environment variables for template bucket name and environment.
packages/api/internal/cache/instance/instance.goAdded a new field to InstanceInfo to hold node information.
packages/api/internal/node/node.goDefined a new struct NodeInfo to hold node details.
packages/api/internal/orchestrator/cache.goUpdated node references to use the new NodeInfo struct.
packages/api/internal/orchestrator/client.goModified the node parameter type in connectToNode to use NodeInfo.
packages/api/internal/orchestrator/create_instance.goUpdated logging and node deletion logic to use NodeInfo.
packages/api/internal/orchestrator/list_instances.goChanged the parameter type in getInstances to accept NodeInfo.
packages/api/internal/orchestrator/node.goUpdated the Node struct to include NodeInfo.
packages/api/internal/orchestrator/orchestrator.goInitialized a DNS server and added it to the Orchestrator struct.
packages/api/main.goUpdated error logging to use log instead of fmt.
packages/nomad/proxies/client.confAdded DNS resolution configuration.
packages/orchestrator/cmd/mock-sandbox/mock.goUpdated DNS server start parameters.
packages/orchestrator/internal/sandbox/sandbox.goUpdated imports to include the new DNS package.
packages/orchestrator/internal/server/main.goUpdated DNS server start parameters.
packages/shared/pkg/dns/server.goModified the DNS server start function to accept a port parameter.

This PR includes files in programming languages that we currently do not support. We have not reviewed files with the extensions .conf. See list of supported languages.

This is already merged in dev


Feature Request: Shortcut for Search

a quick shortcut to open up Search, like shift+s or whatever else you think is suitable would be a good addition for the app I think.

I will add it to Alt + S.
Thanks for the idea.


ADD A FULLY WORKING PROJECT


Don't clear player.userid upon unlinking

Approved by @Zarel in https://github.com/Zarel/Pokemon-Showdown/pull/5456#discussion_r312765366 and needed for #5456.

Wait, nothing else needs to happen for this change? Are you sure?

I don't think so?
What else do you think needs to happen?

I suppose there isn't; I'm just surprised there isn't.


add in-toto governance review

fixes #733

@TheFoxAtWork @dims @dzolotusky ready for your approval.

Thanks, just updated!

Thanks, all, merging per @TheFoxAtWork


[BUG]

Describe the bug
There are 2 managers in a team, although the singleowner setting is active.

Details
Please provide the following details about your server set-up:
airplane latest
betterteams latest

This issue is being closed for inactivity. If you are still having problems feel free to open a new issue linking this one, make sure you answer any questions asked in the new issue.


Support TypeScript composite/reference projects

This should replace the --workspaces option.
https://blogs.msdn.microsoft.com/typescript/2018/07/30/announcing-typescript-3-0/#project-references
https://github.com/RyanCavanaugh/project-references-demo

Implemented here: https://github.com/beemojs/beemo/pull/40


Switch to latest edtt

This will switch to use the most recent version of EDTTool.
Also this will also implement referencing 'main' branch, as will be configured default on EDTTool repo

I think commit "edtt: make sure the refactored LLCP is correctly selected" should go into a separate PR to separate concerns.

I agree, re. 8b62442654fbce487f2936e97f086a4308c7551d - this is already on its way into main through other channels, but I wanted to make this Draft PR 'self-contained'

Updated edtt reference in west.yml and rebased.


MODORG-19 "Account number" must be unique for organization

https://issues.folio.org/browse/MODORG-19


Unstable AVD?

Hi there,
I've been testing with the AVD module and noticed that it does not seem to repeat it's tasks reliably:

sometimes it cannot boot the emulator
sometimes the emulator seems to crash after a couple of tasks

Is there are known issues about the repeatability/stability of this module?
fyi: Before, I tried to implement everything with the "Virtual Device Testing for Android" Module instread of executing it via Gradle Modules (connectedFlavor1DebugAndroidTest) which worked great but I had to stop as I needed to execute 3 modules with 2 flavors each but the modul only works for one combination, see: https://github.com/bitrise-steplib/steps-virtual-device-testing-for-android/issues/16
------------------------------------------------ LOGS ---------------------------------------------

Error

+------------------------------------------------------------------------------+

| (0) AVD: Prepare device                                                      |
+------------------------------------------------------------------------------+
| id: avd-manager                                                              |
| version: 0.9.2                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: go                                                                  |
| time: 2018-08-17T13:32:26Z                                                   |
+------------------------------------------------------------------------------+
|                                                                              |
INFO[13:32:26] sudo "apt-get" "update"
Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [107 kB]
Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease
Get:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Get:4 https://download.docker.com/linux/ubuntu xenial InRelease [65.8 kB]
Get:5 https://packages.cloud.google.com/apt cloud-sdk-xenial InRelease [6,372 B]
Hit:6 https://dl.yarnpkg.com/debian stable InRelease
Get:7 https://deb.nodesource.com/node_8.x xenial InRelease [4,646 B]
Get:8 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
Hit:9 https://packagecloud.io/github/git-lfs/ubuntu xenial InRelease
Get:10 https://packages.cloud.google.com/apt cloud-sdk-xenial/main amd64 Packages [45.3 kB]
Get:11 http://security.ubuntu.com/ubuntu xenial-security/universe Sources [88.1 kB]
Get:12 https://packages.cloud.google.com/apt cloud-sdk-xenial/main i386 Packages [45.1 kB]
Get:13 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages [688 kB]
Get:14 https://deb.nodesource.com/node_8.x xenial/main amd64 Packages [1,009 B]
Get:15 https://deb.nodesource.com/node_8.x xenial/main i386 Packages [1,001 B]
Get:16 http://archive.ubuntu.com/ubuntu xenial-updates/universe Sources [275 kB]
Get:17 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages [601 kB]
Get:18 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages [465 kB]
Get:19 http://security.ubuntu.com/ubuntu xenial-security/universe i386 Packages [393 kB]
Get:20 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [1,073 kB]
Get:21 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 Packages [3,748 B]
Get:22 http://security.ubuntu.com/ubuntu xenial-security/multiverse i386 Packages [3,936 B]
Get:23 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages [975 kB]
Get:24 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [876 kB]
Get:25 http://archive.ubuntu.com/ubuntu xenial-updates/universe i386 Packages [796 kB]
Get:26 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 Packages [18.8 kB]
Get:27 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse i386 Packages [17.6 kB]
Fetched 6,765 kB in 2s (2,261 kB/s)
Reading package lists...
INFO[13:32:34] Start installing (golang) with apt-get
INFO[13:32:34]  * [OK] Step dependency (go) installed, available.
Configs:
- Version: 26
- Resolution: 240x426
- Density: 120
- Orientation: portrait
- Tag: google_apis
- ABI: x86
- Profile: Nexus 5X
- ID: emulator
- CustomCommandFlags: -no-window -no-audio -debug-init
- Overwrite: true
- CustomConfig:
disk.dataPartition.size=1024M
hw.camera.back=emulated
hw.camera.front=emulated
hw.keyboard=yes
hw.gpu.enabled=true
hw.gpu.mode=swiftshader
hw.ramSize=1536
runtime.network.latency=none
runtime.network.speed=full
showDeviceFrame=no
skin.dynamic=yes
skin.path=_no_skin
skin.path.backup=_no_skin
vm.heapSize=384
Ensure sdk packages: [tools platform-tools system-images;android-26;google_apis;x86]
- Done
Create AVD
- Done
Start emulator
Failed to boot emulator device within 300 seconds.
|                                                                              |
+---+---------------------------------------------------------------+----------+
| x | AVD: Prepare device (exit code: 1)                            | 419 sec  |
+---+---------------------------------------------------------------+----------+
| Issue tracker: https://github.com/bitrise-steplib/steps-avd-manager/issues   |
| Source: https://github.com/bitrise-steplib/steps-avd-manager                 |
+---+---------------------------------------------------------------+----------+

Error

Starting 25 tests on emulator(AVD) - 8.0.0
****ServiceTest > testStopNonConnectedService[emulator(AVD) - 8.0.0] FAILED
	java.lang.NullPointerException: Attempt to read from field 'android.os.MessageQueue android.os.Looper.mQueue' on a null object reference
	at android.os.Handler.<init>(Handler.java:232)
Tests on emulator(AVD) - 8.0.0 failed: Instrumentation run failed due to 'Process crashed.'

Hi @hb0,
Thank you for reporting the issue! We are trying to find a solution that would work without reducing the functionality of the AVD Manager step, but it proves to be more complicated than expected. It appears there is a workaround though. Could you do the following and start a new build?

Setting Verbose Mode in the Customize section of the AVD Manager step to false
Downgrading the AVD Manager step to version 0.9.1

Hi @tamasbazs , thanks for the reply!

Setting Verbose Mode in the Customize section of the AVD Manager step to false
fyi: There is "true, false, false" to choose from. 2nd "false" was already selected.

---------- (1) Downgraded AVD Manager module to 0.9.1 ---------------
Gradle Build successful, next step would be "waiting for Android Device" but the build fails without error message / before it get's to the "waiting for" module. (I can try to reproduce this it helpful)
BUILD SUCCESSFUL in 3m 6s
260 actionable tasks: 260 executed

Collecting gradle caches...
 Generate dependencies map...

----------- (2) Downgraded "Wait for emulator" module to 1.0.3" --------
This time it ran through:

both with only one module and two flavors
and also with 3 modules and two flavors (my initial setup)

+---+---------------------------------------------------------------+----------+
| ✓ | AVD: Prepare device                                           | 91 sec   |
+---+---------------------------------------------------------------+----------+
| Update available: 0.9.1 -> 0.9.2                                             |
+---+---------------------------------------------------------------+----------+
| ✓ | activate-ssh-key                                              | 18 sec   |
+---+---------------------------------------------------------------+----------+
| ✓ | git-clone                                                     | 9.00 sec |
+---+---------------------------------------------------------------+----------+
| ✓ | cache-pull                                                    | 55 sec   |
+---+---------------------------------------------------------------+----------+
| ✓ | install-missing-android-tools                                 | 62 sec   |
+---+---------------------------------------------------------------+----------+
| ✓ | Gradle: Build                                                 | 205 sec  |
+---+---------------------------------------------------------------+----------+
| ✓ |<EMAIL_ADDRESS>                             | 12 sec   |
+---+---------------------------------------------------------------+----------+
| Update available: 1.0.3 -> 1.0.4                                             |
+---+---------------------------------------------------------------+----------+
| ✓ | Gradle: non Flaky androidTests                                | 214 sec  |
+---+---------------------------------------------------------------+----------+
| ! | Gradle: Flaky AndroidTests too (skippable) (exit code: 1)     | 155 sec  |
+---+---------------------------------------------------------------+----------+
| Issue tracker: https://github.com/bitrise-io/steps-gradle-runner/issues      |
| Source: https://github.com/bitrise-io/steps-gradle-runner                    |
+---+---------------------------------------------------------------+----------+
| ✓ | Gradle: Unit Tests                                                   | 252 sec  |
+---+---------------------------------------------------------------+----------+
| ✓ | cache-push                                                    | 38 sec   |
+---+---------------------------------------------------------------+----------+
| ✓ | slack                                                         | 3.36 sec |
+---+---------------------------------------------------------------+----------+```

-------------- (0) before I received your suggestion my last try resulted in -----------------
The build didn't stop after running through / skipping all steps but just ran on (at least it seemed like this), had to abort it manually. If helpful, I can try to reproduce this.
+------------------------------------------------------------------------------+

| (6) wait-for-android-emulator                                                |
+------------------------------------------------------------------------------+
| id: wait-for-android-emulator                                                |
| version: 1.0.4                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: go                                                                  |
| time: 2018-08-23T06:41:42Z                                                   |
+------------------------------------------------------------------------------+
|                                                                              |
INFO[06:41:42] Start installing (golang) with apt-get
INFO[06:41:42]  * [OK] Step dependency (go) installed, available.
Configs:
- emulatorSerial: emulator-[REDACTED]4
- bootTimeout: 300
- AndroidHome: /opt/android-sdk-linux
Waiting for emulator boot
> Checking if device booted...
Running command timed out, retry...
> Checking if device booted...
Failed to check emulator boot status, error: * daemon not running; starting now at tcp:5037
* daemon started successfully
error: device still connecting - exit status 1
|                                                                              |
+---+---------------------------------------------------------------+----------+
| x | wait-for-android-emulator (exit code: 1)                      | 30 sec   |

Still working, I've selected this as default workflow now and will report back if it fails.
So from my end this can be closed, you probably have a own ticket for the underlying issue.
Thanks alot for the workaround!
One off-topic question, maybe someone has a clue:
One of our location update based tests on Android only works on the Pixel 2 emulator.
Unfortunately, the AVD Manager does not offer pixel 2 as device. Is there a specific reason for this or will it be added eventually with an AVD update?

Hey @hb0 !
Thanks for the feedback. The ticket is already in our internal issue tracker.
Is pixel 2 is one of the locally available android emulators?

@trapacska Yes, Pixel 2 is available on our local AVD.

So this is something Bitrise is going to do (eventually) if I understand you correctly?
If not, I meant that I cannot choose a "pixel 2" profile in the AVD Manager step, see screenshot:

OH! I got it now. All right, let me look around.

Anyhow I try to update latest SDK, still pixel 2 is not listed in the list I got with this command:
$ANDROID_HOME/tools/bin/avdmanager list
If you run the command, do you see pixel 2 in the list?

Well, I can't execute avdmanager via command line because it seems not to be compatible with JAVA 10.0.2. In order to execute it I used the following flag (suggested here: https://stackoverflow.com/a/51644855/5815054):
export JAVA_OPTS='-XX:+IgnoreUnrecognizedVMOptions --add-modules java.se.ee'
The output is now:
Parsing ****
Available Android Virtual Devices:
    Name: Nexus_5X_API_26
  Device: Nexus 5X (Google)
    Path: /home/user/.android/avd/Nexus_5X_API_26.avd
  Target: Google Play (Google Inc.)
          Based on: Android 8.0 (Oreo) Tag/ABI: google_apis_playstore/x86
    Skin: nexus_5x
  Sdcard: 100M
---------
    Name: Nexus_5X_API_28
  Device: Nexus 5X (Google)
    Path: /home/user/.android/avd/Nexus_5X_API_28.avd
  Target: Google Play (Google Inc.)
          Based on: Android API 28 Tag/ABI: google_apis_playstore/x86
    Skin: nexus_5x
  Sdcard: 100M

The following Android Virtual Devices could not be loaded:
    Name: Pixel_2_API_28
    Path: /home/user/.android/avd/Pixel_2_API_28.avd
   Error: Google pixel_2 no longer exists as a device
Available devices definitions:
id: 0 or "tv_1080p"
    Name: Android TV (1080p)
    OEM : Google
    Tag : android-tv
---------
... and others, but no more pixel 2 entry.

My very wild guess would be that Pixel 2 is only available under JAVA 10 ?
Or are you gues using JAVA 10, too?

To be honest - I can't tell. But I created a stackoverflow question, maybe others have the same problem.
https://stackoverflow.com/questions/52329359/pixel-2-emulator-virtual-device-not-in-avd-manager-device-list


can't use ostringstream to output xtensor in unittest in vs2017?

hi, I want to writing some tests in unit test, in vs2017, but it report c2131 error when I try to ouput xtensor by ostringstream:
error C2131: expression did not evaluate to a constant
from file xvariant_impl.hpp.
here is code:
#include "stdafx.h"
#include "CppUnitTest.h"

#include "xtensor/xarray.hpp"
#include "xtensor/xio.hpp"
#include "xtensor/xview.hpp"
#include "xtensor/xnpy.hpp"
#include "xtensor/xnoalias.hpp"
#include "xtensor/xtensor.hpp"
#include "xtensor/xtensor_forward.hpp"
#include "xtensor/xindex_view.hpp"
#include "xtensor/xsort.hpp"
#include <iostream>
#include <sstream>

using namespace Microsoft::VisualStudio::CppUnitTestFramework;

namespace xtensor_ut
{
	TEST_CLASS(UnitTest1)
	{
	public:

		TEST_METHOD(TM_reshape)
		{
			xt::xtensor<int, 2> x = { {1, 2}, { 3, 4 } };
			std::stringstream oss;
			oss << x;

		}
	};
}

Closing as a duplicate of #1152. This is a compiler bug on VS2017.
The VS team claim they fixed it in the next release (they release vs2017 every few weeks fixing some bugs and adding new ones).