Add title to fakenews extension?

Can you add '# Title: Fake News hosts' on line one? It makes it show up with the name rather than the URL for ublock origin.

This is a duplicate of Issue #744, which is closed (?!).

Sorry to resurrect this but the issue is still present as far as I can tell. I'm not sure why #744 was closed, looking at the comments and the fact no PR tagged that issue it seems that while a solution was identified it was never implemented?
I have added the Unified + Fakenews list to both uBlock Origin and AdGuard Home and neither show a title. The title column is blank on AdGuard Home while uBO shows the URL. Opening the list directly from both the GitHub and non-GitHub links shows that neither include any sort of title declaration, that I can see.

I don't bother to write a PR if an issue is flagged as closed @Ultrabenosaurus by OP or even Steve...
Steve @StevenBlack, let's follow up at https://github.com/StevenBlack/hosts/issues/744 because it has more details in the way we/I can implement this.
Cheers,
Nissar

@funilrys sorry for any confusion, I didn't mean to say "the issue is closed so why did no one do a PR?" but more "a solution was confirmed but no PR was created, so why is it closed?". I think it is reasonable to assume a closed issue does not need coding or a PR, but it seemed odd to me that #744 was closed despite the solution not being implemented.

Maybe OP did not understand how GitHub works ... People want everything instantly but forget that we aren't necessarily paid for what we do out here and that we mostly do what do out here in our side/free time...
Anyway @Ultrabenosaurus PR #1014  in pending. It's up to Steve @StevenBlack now :smile_cat:.
Have a good afternoon.
Cheers,
Nissar

This one can now be closed as #1014 was merged. @StevenBlack @Ultrabenosaurus

Closing.  Thanks everybody!


stage1/fly: clear FD_CLOEXEC only once

stage1-fly was previously toggling FD_CLOEXEC on RKT_LOCK_FD multiple
times:

setting it at first
clearing it before exec()
setting it again after exec()

This commit just clears it once, as exec() is the very last stage1 step
and we either exit-fail or never return after that.

LGTM. Looks like we use the same wrapper around exec in the other stage1, if you feel like fixing.

The story for other stage1 is a bit more complex and traces back to https://github.com/coreos/rkt/pull/628. In short, there may be other fork/exec involved for which we need FD_CLOEXEC. But I should re-check at some point, as that PR is quite old and the description in there doesn't completely match my current understanding.
/cc @jonboulle

@lucab maybe just file a follow up for that one?

After a second pass, the other stage1s looks fine as they are. I think I just misread one of the original comments, which left me wondering.


ModuleNotFoundError when running tests (trying to build 3.6 manually)

Here's my attempt at building Gensim 3.6.0 for Python 3.6. I just bumped the version number and got the updated SHA256 from PyPI.
Does something need to be updated elsewhere in the recipe?
git clone https://github.com/conda-forge/gensim-feedstock
cd gensim-feedstock

git apply <<'EOF'
diff --git a/feedstocks/gensim-feedstock/recipe/meta.yaml b/feedstocks/gensim-feedstock/recipe/meta.yaml
index 134fd61..7c1c694 100644
--- a/feedstocks/gensim-feedstock/recipe/meta.yaml
+++ b/feedstocks/gensim-feedstock/recipe/meta.yaml
@@ -1,6 +1,6 @@
 {% set name = "gensim" %}
-{% set version = "3.5.0" %}
-{% set sha256 = "78ed9b6ac35f104542f3bee0386d71ddf9432d74c153065d2ea9f6baf10e5b49" %}
+{% set version = "3.6.0" %}
+{% set sha256 = "24adaca52e8d821a2f5d5e6fe2e37cf321b1fafb505926ea79a7c2f019ce5b07" %}

 package:
   name: {{ name|lower }}
EOF

conda build --python=3.6 ./recipe

This gives the error:
ModuleNotFoundError: No module named 'gensim.models.word2vec_corpusfile'

Output from conda info:
     active environment : None
            shell level : 0
       user config file : /<redacted>/.condarc
 populated config files : /<redacted>/.condarc
          conda version : 4.5.0
    conda-build version : 3.0.31
         python version : 3.6.1.final.0
       base environment : /<redacted>/anaconda3  (read only)
           channel URLs : https://conda.anaconda.org/<redacted>/linux-64
                          https://conda.anaconda.org/<redacted>/noarch
                          https://conda.anaconda.org/conda-forge/linux-64
                          https://conda.anaconda.org/conda-forge/noarch
                          https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/free/linux-64
                          https://repo.anaconda.com/pkgs/free/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
                          https://repo.anaconda.com/pkgs/pro/linux-64
                          https://repo.anaconda.com/pkgs/pro/noarch
          package cache : /opt/app/anaconda3/pkgs
                          /<redacted>/.conda/pkgs
       envs directories : /<redacted>/.conda/envs
                          /<redacted>/anaconda3/envs
               platform : linux-64
             user-agent : conda/4.5.0 requests/2.18.4 CPython/3.6.1 Linux/3.10.0-514.26.2.el7.x86_64 rhel/7.3 glibc/2.17
                UID:GID : 51757:51714
             netrc file : None
           offline mode : False

Hello @gwerbin, current issue related with missing file in tarball on PyPI, this already fixed in https://github.com/RaRe-Technologies/gensim/pull/2194, but not released yet.
As workaround, you can use gensim==3.5.0 OR build tarball from current gensim develop branch & use it, instead of PyPI version (https://github.com/conda-forge/gensim-feedstock/files/2449277/gensim-3.6.0.tar.gz)


VSCodium cannot activate extension

Not sure if this is a VSCodium issue or an extension issue.
Problem
VSCodium cannot activate extension because it depends on an unknown ms-vscode.test-adapter-converter extension
What I tried
Install ms-vscode.test-adapter-converter fails with Unable to install extension 'ms-vscode.test-adapter-converter' as it is not compatible with VS Code '1.57.1'.
Description
From the ms-vscode.test-adapter-converter Marketplace page:

This is an extension that converts from the Test Explorer UI API into native VS Code testing. When using this, you will likely want to disable the test explorer UI components.

Yet ms-vscode.test-adapter-converter is not listed as a dependency in Test Explorer UI?
I am unable to downgrade VSCodium to 1.56 to see if it's just a version issue with the adapter-converter.

I'm having the same issue on vscode from today (it seems after updating to v1.57 though I have tried with v1.56 and it doesn't work there either). I am getting the following error:

Cannot activate the 'Test Explorer UI' extension because it depends on the 'Test Adapter Converter' extension, which is not loaded. Would you like to reload the window to load the extension?

After reloading, I get the same message again (and the test adapter converter is not loaded). This only appears when using WSL both on Ubuntu 18.04 and 20.04. If I don't connect to a remote WSL session, the test explorer UI loads as expected on the side bar.

It is also unusable with dev-containers at the moment.

Since these are issues with the Test Adapter Converter extension, here are the relevant issues in the repository for that extension:
microsoft/vscode-test-adapter-converter#6
microsoft/vscode-test-adapter-converter#5
I hope that Microsoft will fix these soon, otherwise I'll have to remove the extension dependency for now.

Yet ms-vscode.test-adapter-converter is not listed as a dependency in Test Explorer UI?

It is listed as an extensionDependency (because extension dependencies are handled differently than the regular dependencies)

The test-adapter-converter seems to activate - or attempt to and fail in my case - even with testExplorer.useNativeTesting explicitly set to false.
Is it possible to load dependencies conditionally?

Seems the problem got resolved (with the new vscode update?).

Can confirm. Resolved by upgrading to 1.58.1.

It's working here too on 1.58.1
Although, I noticed that the "Test Adapter Convert"  was updated to 0.0.13 an hour ago. Looking at the original error message, it might be related to the extension version rather than VSCode version?

@tyler36 The part of the issue that involves remotes looks to have indeed been a problem with the converter extension and was fixed here https://github.com/microsoft/vscode-test-adapter-converter/commit/5881ec1a44d0751fd3e0e9e61db8eadd84149e12

Can confirm, for me it works as well again (vscode 1.58.0 still but test adapter converter 0.0.13) on windows using WSL (Ubuntu 20.04)

Until there's a stable release of test-adapter-converter (or whatever system it morphs into), this type of issue will probably crop up again.
Probably should close ticket since OP, and several others, have confirmed it's no longer an issue.

FWIW, I installed test-adapter-converter from marketplace downloaded VSIX, so my current version ~is~ was still 0.0.10. Update to 0.0.12 (downloaded 8th July) also works. 0.0.15 (current version released yesterday) is incompatible with 1.58.1.


Use HAProxy from the beginning for Velum too.

This will help us with SSL termination on HAProxy side.

[x] Do not call to bin/init from two different containers, as they will setup the database the first time and run migrations afterwards. It's safer if only one container runs this while the others just raise the application server.

Depends on: https://github.com/kubic-project/velum/pull/387
Depends on: https://github.com/kubic-project/salt/pull/314

How to test: https://github.com/kubic-project/salt/pull/314#issuecomment-346907208

I didn't test the change, but it looks good to me. I've only one question: shouldn't we move all the velum pods definitions from public.yml to either private.yml or to a new .yml file? Originally public.yml has all the pods that are reusing the host network, but this is no longer needed now by velum; hence I would like to play safe and avoid to reuse the host network stack with it.

I didn't test the change, but it looks good to me. I've only one question: shouldn't we move all the velum pods definitions from public.yml to either private.yml or to a new .yml file? Originally public.yml has all the pods that are reusing the host network, but this is no longer needed now by velum; hence I would like to play safe and avoid to reuse the host network stack with it.

I agree, I think we should explore this, but I'd do this in a separate PR.

@flavio - yep - I've been thinking the same and started with this PR - https://github.com/kubic-project/caasp-container-manifests/pull/135 - that gets the package into a place where new yaml files will work in our dev env, without needing a new c-c-m package built :)

Force merging the 3 PRs in together.


python3Packages.pydeconz: 83 -> 84

Motivation for this change
Update to latest upstream release 84
Change log: https://github.com/Kane610/deconz/releases/tag/v84
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@ofBorg build home-assistant

Cherry-picked into home-assistant.


NestedScrollView instantaneous jump when body starts to scroll

import 'package:flutter/material.dart';

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  static const String _title = 'Flutter Code Sample';

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      title: _title,
      home: MyStatelessWidget(),
    );
  }
}

class MyStatelessWidget extends StatelessWidget {
  const MyStatelessWidget({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    final List<String> _tabs = <String>['Tab 1', 'Tab 2'];
    return DefaultTabController(
      length: _tabs.length, // This is the number of tabs.
      child: Scaffold(
        body: NestedScrollView(
          headerSliverBuilder: (BuildContext context, bool innerBoxIsScrolled) {
            return <Widget>[
              SliverToBoxAdapter(
                child: SizedBox(
                  height: 250,
                ),
              ),
              SliverOverlapAbsorber(
                handle: NestedScrollView.sliverOverlapAbsorberHandleFor(context),
                sliver: SliverAppBar(
                  title: const Text('Books'),
                  pinned: true,
                  expandedHeight: 150.0,
                  forceElevated: innerBoxIsScrolled,
                  bottom: TabBar(
                    tabs: _tabs.map((String name) => Tab(text: name)).toList(),
                  ),
                ),
              ),
            ];
          },
          body: TabBarView(
            children: _tabs.map((String name) {
              return SafeArea(
                top: false,
                bottom: false,
                child: Builder(
                  builder: (BuildContext context) {
                    return CustomScrollView(
                      key: PageStorageKey<String>(name),
                      slivers: <Widget>[
                        SliverOverlapInjector(
                          handle: NestedScrollView.sliverOverlapAbsorberHandleFor(context),
                        ),
                        SliverPadding(
                          padding: const EdgeInsets.all(8.0),
                          sliver: SliverFixedExtentList(
                            itemExtent: 48.0,
                            delegate: SliverChildBuilderDelegate(
                              (BuildContext context, int index) {
                                return ListTile(
                                  title: Text('Item $index'),
                                );
                              },
                              childCount: 30,
                            ),
                          ),
                        ),
                      ],
                    );
                  },
                ),
              );
            }).toList(),
          ),
        ),
      ),
    );
  }
}

NestedScrollView shows weird behaviour when some sliver(SliverToBoxAdapter in this case) is above SliverOverlapAbsorber .
When body starts to scroll slightly, its scroll speed gets faster and scrolls further than expected.
I was able to reproduce this behaviour in several devices.
Above is a reproducible code.
Hope I didn't violate any community rules, since this is my first issuing. Thanks!

Hi @MinseokKang003
Can you please provide your flutter doctor -V and screen recording of the behavior
SliverToBoxAdapter pops if Iscroll the body,
Thank you

flutter doctor -v
[√] Flutter (Channel stable, 2.2.1, on Microsoft Windows [Version 10.0.18363.1500], locale ko-KR)
    • Flutter version 2.2.1 at D:\app\flutter
    • Framework revision 02c026b03c (12 days ago), 2021-05-27 12:24:44 -0700
    • Engine revision 0fdb562ac8
    • Dart version 2.13.1

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at D:\app\android-sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_SDK_ROOT = D:\app\android-sdk
    • Java binary at: D:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Android Studio (version 4.1.0)
    • Android Studio at D:\Program Files\Android\Android Studio
    • 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 1.8.0_242-release-1644-b01)

[√] Connected device (3 available)
    • SM G965N (mobile) • 211171a60b057ece • android-arm64  • Android 10 (API 29)
    • Chrome (web)      • chrome           • web-javascript • Google Chrome 91.0.4472.77
    • Edge (web)        • edge             • web-javascript • Microsoft Edge 91.0.864.41

• No issues

https://user-images.githubusercontent.com/74072689/121171410-71345400-c891-11eb-9d5c-5548d79fff38.mp4
NestedScrollView's body starts to scroll a little bit more than I expected. I'm not sure if this is an expected behavior.
Also found out this is irrelevant to SliverOverlapObsorber and SliverOverlapInjector.
Thanks!
@TahaTesser

Hi @MinseokKang003
Thanks for the video, the issue is more clear now.
Yes, I can see the same behavior, in fact, my testing body scrolls too much even I scroll slightly to snap top,  Tested on Samsung device
https://user-images.githubusercontent.com/48603081/121333190-40036480-c921-11eb-8ab8-032beb8458ed.mp4
On Oneplus 8, the body scrolls even faster and unexpected
https://user-images.githubusercontent.com/48603081/121343467-629a7b00-c92b-11eb-96b6-0c47e98ae214.mp4

stable
master

❌
❌

Check flutter doctor -v outputs for each channel below

flutter doctor -v
[✓] Flutter (Channel stable, 2.2.1, on Microsoft Windows [Version 10.0.19043.1052], locale en-US)
    • Flutter version 2.2.1 at C:\Users\Taha\Code\flutter_stable
    • Framework revision 02c026b03c (13 days ago), 2021-05-27 12:24:44 -0700
    • Engine revision 0fdb562ac8
    • Dart version 2.13.1

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at C:\Users\Taha\Code\SDK
    • Platform android-30, build-tools 30.0.3
    • ANDROID_SDK_ROOT = C:\Users\Taha\Code\SDK
    • Java binary at: C:\Users\Taha\Code\openjdk\bin\java.exe
    • Java version OpenJDK Runtime Environment (build 1.8.0-262-b10)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[✓] Visual Studio - develop for Windows (Visual Studio Community 2019 16.10.0)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
    • Visual Studio Community 2019 version 16.10.31321.278
    • Windows 10 SDK version 10.0.19041.0

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/windows#android-setup for detailed instructions).

[✓] IntelliJ IDEA Community Edition (version 2021.1)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2021.1.1
    • Flutter plugin version 57.0.5
    • Dart plugin version 211.7233

[✓] VS Code (version 1.56.2)
    • VS Code at C:\Users\Taha\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.23.0

[✓] Connected device (4 available)
    • sdk gphone x86 (mobile) • emulator-5554 • android-x86    • Android 11 (API 30) (emulator)
    • Windows (desktop)       • windows       • windows-x64    • Microsoft Windows [Version 10.0.19043.1052]
    • Chrome (web)            • chrome        • web-javascript • Google Chrome 91.0.4472.77
    • Edge (web)              • edge          • web-javascript • Microsoft Edge 91.0.864.41

! Doctor found issues in 1 category.

[✓] Flutter (Channel master, 2.3.0-17.0.pre.275, on Microsoft Windows [Version 10.0.19043.1052], locale en-US)
    • Flutter version 2.3.0-17.0.pre.275 at C:\Users\Taha\Code\flutter_master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 1694188e21 (5 hours ago), 2021-06-09 02:29:02 -0400
    • Engine revision 132669b021
    • Dart version 2.14.0 (build 2.14.0-189.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at C:\Users\Taha\Code\SDK
    • Platform android-30, build-tools 30.0.3
    • ANDROID_SDK_ROOT = C:\Users\Taha\Code\SDK
    • Java binary at: C:\Users\Taha\Code\android-studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6842174)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[✓] Visual Studio - develop for Windows (Visual Studio Community 2019 16.10.0)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
    • Visual Studio Community 2019 version 16.10.31321.278
    • Windows 10 SDK version 10.0.19041.0

[✓] Android Studio (version 4.2.0)
    • Android Studio at C:\Users\Taha\Code\android-studio
    • 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.8+10-b944.6842174)

[✓] IntelliJ IDEA Community Edition (version 2021.1)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2021.1.1
    • Flutter plugin version 57.0.5
    • Dart plugin version 211.7233

[✓] VS Code (version 1.56.2)
    • VS Code at C:\Users\Taha\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.23.0

[✓] Connected device (5 available)
    • sdk gphone x86 (mobile) • emulator-5554 • android-x86     • Android 11 (API 30) (emulator)
    • Windows (desktop)       • windows       • windows-x64     • Microsoft Windows [Version 10.0.19043.1052]
    • Windows (UWP) (desktop) • winuwp        • windows-uwp-x64 •
    • Chrome (web)            • chrome        • web-javascript  • Google Chrome 91.0.4472.77
    • Edge (web)              • edge          • web-javascript  • Microsoft Edge 91.0.864.41

• No issues found!

✅ : No Issue ❌: Issue reproduce
Can you please confirm this is the issue?
Thank you

Yes, I confirm that is the issue. Thanks for checking out.

Hi @MinseokKang003
To confirm it's just not Android tried on iOS, same results, framework issue. Although it is worse on Oneplus 8, it could that it has a 90hz display?

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

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  static const String _title = 'Flutter Code Sample';

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      title: _title,
      home: MyStatelessWidget(),
    );
  }
}

class MyStatelessWidget extends StatelessWidget {
  const MyStatelessWidget({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    final List<String> _tabs = <String>['Tab 1', 'Tab 2'];
    return DefaultTabController(
      length: _tabs.length, // This is the number of tabs.
      child: Scaffold(
        body: NestedScrollView(
          headerSliverBuilder: (BuildContext context, bool innerBoxIsScrolled) {
            return <Widget>[
              SliverToBoxAdapter(
                child: SizedBox(
                  height: 250,
                ),
              ),
              SliverOverlapAbsorber(
                handle: NestedScrollView.sliverOverlapAbsorberHandleFor(context),
                sliver: SliverAppBar(
                  title: const Text('Books'),
                  pinned: true,
                  expandedHeight: 150.0,
                  forceElevated: innerBoxIsScrolled,
                  bottom: TabBar(
                    tabs: _tabs.map((String name) => Tab(text: name)).toList(),
                  ),
                ),
              ),
            ];
          },
          body: TabBarView(
            children: _tabs.map((String name) {
              return SafeArea(
                top: false,
                bottom: false,
                child: Builder(
                  builder: (BuildContext context) {
                    return CustomScrollView(
                      key: PageStorageKey<String>(name),
                      slivers: <Widget>[
                        SliverOverlapInjector(
                          handle: NestedScrollView.sliverOverlapAbsorberHandleFor(context),
                        ),
                        SliverPadding(
                          padding: const EdgeInsets.all(8.0),
                          sliver: SliverFixedExtentList(
                            itemExtent: 48.0,
                            delegate: SliverChildBuilderDelegate(
                              (BuildContext context, int index) {
                                return ListTile(
                                  title: Text('Item $index'),
                                );
                              },
                              childCount: 30,
                            ),
                          ),
                        ),
                      ],
                    );
                  },
                ),
              );
            }).toList(),
          ),
        ),
      ),
    );
  }
}

iOS
https://user-images.githubusercontent.com/48603081/121481559-ec525300-c9d4-11eb-9142-9eae2fb92218.mov
Android
https://github.com/flutter/flutter/issues/84128#issuecomment-857605545

flutter doctor -v
[✓] Flutter (Channel stable, 2.2.1, on macOS 11.4 20F71 darwin-x64, locale
    en-GB)
    • Flutter version 2.2.1 at /Users/tahatesser/Code/flutter_stable
    • Framework revision 02c026b03c (2 weeks ago), 2021-05-27 12:24:44 -0700
    • Engine revision 0fdb562ac8
    • Dart version 2.13.1

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Volumes/Extreme/SDK
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Volumes/Extreme/SDK
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Volumes/Extreme/Xcode-beta.app/Contents/Developer
    • Xcode 13.0, Build version 13A5154h
    • CocoaPods version 1.10.1

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

[✓] Android Studio (version 4.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.8+10-b944.6916264)

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

[✓] Connected device (3 available)
    • Taha’s iPhone (mobile) • 00008020-001059882212002E • ios            • iOS
      15.0
    • macOS (desktop)        • macos                     • darwin-x64     •
      macOS 11.4 20F71 darwin-x64
    • Chrome (web)           • chrome                    • web-javascript •
      Google Chrome 91.0.4472.77

• No issues found!

cc: @Piinks


Relic icon improvements

Time to get new icons for some relics, and also paint all those that won't have non-boots.
List of relics which will have new non-boot icons below:

Red Gi should be a... red gi, with cut sleeves. - Done.
Dark Gi... same. - Done.
Cattail should be a cattail. - Done.
Wrestler's Cloak - Done.
Necklace of Skulls - Done.
Killian Engine Alpha - Done.
School Backpack - Done.
Mixed Paint Bucket - Done. Ugly, VERY ugly, but done.

And list of relics which needs some painting or changes:

Green Leotard - Done.
Broken Tusk - Done.
Red Beret - Done.
Wild Herbs Ointment - Done.
Lotus Statue - Color of a lotus, one boot - Done.
Red Cyclone Teachings - Red and Yellow - Done
Special Ops Insignia - Done
Rainbow Brush - Done

And done.


Project selection prompt

Is your feature request related to a problem? Please describe.
Currently when running e.g. "daytona code" or "daytona ssh" without arguments and instead using the prompting wizard - once you pick a workspace, the first project gets automatically selected. There should instead be another "SELECT A PROJECT" prompt for multi-project workspaces.
Doing this will make using the command line arguments not a requirement for selecting a non-primary project of a workspace.
Additional context
The project selection opens only for workspaces with more than one project. It should have the same Charm.sh design as the workspace selection prompt.

/attempt #111

@neo773  We accept your request, thank you! We are available for any questions


Cannot open the same book more than once

When this is attempted, the card for the first open goes blank.
This is very similar to some other issues...
Of course, there is the serious question of whether this should be permitted at all!

v0.9.0-rc.2 build 29a2450. If user tries to open the same book twice, the message pops up "Book is already open"


Add PCI Compliant Repeat Billing and Cardholder Information storage for ...

From Netbilling documentation:
This feature enables you to perform a future repeat-billing or up-sell for the same consumer within the same gateway account, rather than storing and specifying the card number and billing address again. Simply check
"Enable PCI Compliant Repeat Billing, Up-selling and Cross-selling" in Step 6 of the Credit Cards setup page. When the feature is enabled, you would send "CS:123456789012" as the card_number, where<PHONE_NUMBER>12 is
the trans_id of the original transaction.
Per above, netbilling.rb has been modified to accept a string ("123456789012") in lieu of a credit_card for submission.
Furthermore, Netbilling Direct Mode also supports submission of billing information to PCI compliant storage without performing any credit gateway operations with the 'Quasi' (tran_type 'Q') mode. This is implemented in the 'store' method.

This looks good to me. @Shopify/payments ?

:+1:

@wvanbergen remote tests pass OK? If so, :+1: from me.

Code looks fine - haven't personally run the tests though

@cshepherd Any way you get get us credentials so we can run the remote tests?

Remote tests appear to work fine using the default remote test credential account ID '104901072025'.. I've no access to any other credentials that aren't in production, or that are in test mode. If necessary, I can inquire about getting another set of credentials for testing.


Navigator chart should always be shown

I think this will be a case of increasing the min width of the window.

The navigator appears on widths >992px, perhaps that as the new minimum? Or a nice, round, 1000?

FYI, since BitFlux 1.1.0 - assuming you're still using Less - you should be able to achieve this be overriding the relevant variables:
@phone-landscape-nav-display: @show;
@phone-portrait-nav-display: @show;
@tablet-landscape-nav-display: @show;
@tablet-portrait-nav-display: @show;

#213 will update the version of BitFlux, after which we can do this issue. @bjedrzejewski I'll assign this to you, when #213 is closed you can unassign this case again.


Notebook layout issue when collapsing and moving cells

Steps to Reproduce:

Fold a cell with a nested code + output
Move cell above another section
:bug: When cell is moved, it is expanded and layout issues appear

Happened to see this issue when glancing though -- may have just filed a duplicate https://github.com/microsoft/vscode/issues/104120

Already fixed via https://github.com/microsoft/vscode/commit/408ad5d67dcc050ec13b2e02cd9a6735a3bbd3d4


List with factory (xml fragment) doesn't have re-use capabilities

I am using a normal List control with factory on items nothing fancy.
The issue is that if you check in network tab it calls this "CustomListItem.fragment.xml" for each cell.
So it doesn't re-use the cell but creates new one each time.
On this page I could find how the dev team is using aggregate binding with factory but I think what they do is not consistent. First they use XML views and in the controller they create js controls. I want to be consistent and use xml for all view related coding.
In iOS and Android they have something like a re-use id so that it will not be fetched each time.
Overview.view.xml
			<List id="masterList" mode="SingleSelectMaster"
			growing="true" items="{path: '/', factory: '.createListItems'}" growingScrollToLoad="true" >
			</List>

Overview.controller.js
		createListItems: function(sId, oContext){
			if(oContext.getObject().Group != null){
			//individual
			return new sap.ui.xmlfragment(sId, "example.view.fragments.GroupListItem", this);
			}else{
			return new sap.ui.xmlfragment(sId, "example.view.fragments.CustomListItem", this);
			}
		}

CustomListItem.fragment.xml
//just customlistitem with controls
GroupListItem.fragment.xml
//just customlistitem with controls

Hi kyakubi,
Thank you for your message.
Can you also share some more information whether the fragment request in the debugger network has the status 200 or status 340?
Usually the browser should handle the caching of the files or the server should be configured to handle the file requests and use the cached file.
It would also be nice if you could provide us a working example where the issue can be reproduced.
Thanks and regards,
Jay Barbhaiya

i use this workaround to solve this problem
instantiate fragment
this.groupListItemFragment = new sap.ui.xmlfragment("example.view.fragments.GroupListItem", this);

and then use it
createListItems: function(sId, oContext) {
    return this.groupListItemFragment.clone(sId)
}

Since there is no response from the author for more than 4 weeks I'm closing the ticket.


[BUG] Range is not shown correctly when set from end of year to beginning of next year

Hi,
I noticed an issue while using the range function. When the range begins in one year and ends in another year, the connection between those years (months) is not shown correctly.
Please have a look at the provided screenshot. This can easily be reproduced on the demo page.
In this case December should be selected as well, as the range ends in January.

Thanks!
Best regards,
Fabian

The bug should be fixed in the latest version.


Appstudio update test-component-pac-ions

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-ions-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
13 seconds
appstudio-init

✅ Succeeded
13 seconds
clone-repository

✅ Succeeded
16 seconds
appstudio-configure-build

✅ Succeeded
16 seconds
sast-snyk-check

✅ Succeeded
47 seconds
build-container

✅ Succeeded
24 seconds
deprecated-base-image-check

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
15 seconds
clair-scan

✅ Succeeded
24 seconds
sanity-inspect-image

✅ Succeeded
27 seconds
sbom-json-check

✅ Succeeded
13 seconds
sanity-label-check

✅ Succeeded
12 seconds
sanity-optional-label-check

✅ Succeeded
8 seconds
show-summary


chore: In gnoNativeService, support using the remote Gnokey Mobile service

PR https://github.com/gnolang/gnokey-mobile/pull/2 creates the Gnokey Mobile service. This PR updates GnoNativeService with the option to use the remote Gnokey Mobile service as needed (for example, to sign a transaction).

In BridgeConfig and service.Config, add the config flag UseGnokeyMobile.
In initService, if UseGnokeyMobile then set gnokeyMobileClient to a gRPC client connected to the remote Gnokey Mobile service. Set client to a gnoclient without a Keybase (because the purpose is to use Keybase in the remote Gnokey Mobile service).
In gnoNativeService, add getClient which returns the correct gnoclient.Client. If not useGnokeyMobile then simply return s.client . If useGnokeyMobile then it's possible that Gnokey Mobile has been changed to use a different gno.land remote, so we must call the Gnokey Mobile method GetRemote . If this is different from our local s.remote then reconfigure the RPCClient of the gnoclient and save the new s.remote. Change QueryAccount, Query, Render and QEval to call getClient and then proceed as normal. This means that if an app is using Gno Native Kit with UseGnokeyMobile, then the app can send these queries directly to the gno.land remote node, but we must make sure that it is the correct remote.
In GetRemote and ListKeyInfo, if useGnokeyMobile then we directly use the Gnokey Mobile service.
In Call, if useGnokeyMobile then use the local MakeCallTx to make the transaction. Use the SignTx API of the remote Gnokey Mobile service to sign the transaction. Then use the local BroadcastTxCommit to broadcast the signed transaction and get the streaming result.

The above changes allow an app to configure its Gno Native Kit to use a gRPC client with the Gnokey Mobile service. But we still need the Gnokey Mobile app to start the Gnokey Mobile gRPC server. The following changes allow the Gnokey Mobile app to set start_gnokey_mobile_service in the configuration for its GnoNativeProvider.

In the Go Bridge, add StartGnokeyMobileService. See the description comment. Add this method to the TypeScript GoBridgeInterface and to the Java and Swift GnonativeModule.
In the TypeScript Config, add a flag start_gnokey_mobile_service. Check this flag in the GnoNativeApi initClient and call startGnokeyMobileService().

A possible fix for the bug demonstrated in the PR is https://github.com/gnolang/gno/pull/2685, so I set this PR to Draft. If that PR is merged, then we can close this PR.


Row Data copied from excel is malformed from Clipboard

MacOS and 7.1.2
Steps to reproduce
Create a new blank Excel (16.47) Sheet and add data to 3 rows in a column:

Copy to the rows.
behavior
(Get-Clipboard)[0].length

Returns 6

Should return length of string 5.

There is a blank char (ASCII 13 Carriage Return) added to the end of the string. This causes text operators like -join to misbehave. Data copied from Google sheets does not have this issue and this is also not an issue for Powershell 7.1.2 on Windows.
Environment data

The problem is that when Get-Clipboard splits the text on the clipboard into individual lines (as it does, except if -Raw is passed), it only recognizes LF-only newlines as newlines, and retains the CR in Windows-style CRLF as part of the lines.
The problem is here:
https://github.com/PowerShell/PowerShell/blob/11a5d940c4f797be2b6f61c1bf619ccd3a667ce4/src/Microsoft.PowerShell.Commands.Management/commands/management/GetClipboardCommand.cs#L71-L72
That is, instead of exhibiting the usual platform-agnostic newline treatment - recognizing CR-only, LF-only, and CRLF interchangeably - only the platform-native newline sequence is recognized.
Seemingly, Excel uses CRLF newlines even on macOS, which causes the problem.
A simpler way to reproduce the problem on macOS:
PS> sh -c 'printf ''line 1\r\nline 2\r\n'' | pbcopy'; (Get-Clipboard) -replace "`r", '\r'
line 1\r
line 2\r

Also note the empty line at the end, which represent an extra, empty output string, which points to an unrelated secondary problem that isn't platform-specific and is also present in Windows PowerShell - see #14810


Fixed mispositioned "players waiting to play" label in arena modes

Before:

After:

looks good to me, i honestly haven't seen that label in so long i forgot it existed. ty for PRing :)


tests: ringbuffer: avoid unaligned mem access

Casting the rb_data character array to a u32_t can result
in an unaligned u32_t * pointer being passed to
ring_buf_item_put(), since rb_data is only byte-aligned.
Our Altera Max10 CPU build is not configured to detect
unaligned memory access and throw an exception, it is
instead rounding down the memory address
of the data pointer to the nearest 4-byte value, causing
the wrong data to be copied into the ring buffer.
It appears that in the C standard this is considered
Undefined Behavior so the approach this patch takes is
to fix the test, by ensuring that rb_data is aligned to
u32_t.
Fixes: #14869
Signed-off-by: Andrew Boie<EMAIL_ADDRESS>

verified that the tests/lib/ringbuffer test cases are passed with the latest commit 9926f94


💡[FEATURE]: Genetic Algorithm for Credit Risk Modeling

Is your feature request related to a problem? Please describe.
demonstrates the application of a Genetic Algorithm (GA) to optimize a logistic regression model for credit risk prediction. The goal is to find the best hyperparameters for the logistic regression model to improve its accuracy in predicting whether a customer will default on a loan.
Describe the solution you'd like
Initialization: Creates an initial population of potential solutions.
Evaluation: Evaluates each individual in the population using a fitness function (accuracy in this case).
Selection: Selects the best-performing individuals (parents) for reproduction.
Crossover: Combines the parameters of selected parents to create offspring.
Mutation: Introduces random variations to some offspring to maintain genetic diversity.
Iteration: Repeats the process for a specified number of generations to find the best parameters
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

pls @Akshat111111 assign it me I'm Gssoc'24 Contributor


Scheme is not http error using rust-lang.org example

Attempting to use the example results in:

[dependencies]
reqwest = {version = "0.11.14", features = ["rustls", "blocking", "json", "cookies"], default-features = false }
tokio = { version = "1.21.2", features = ["full"] }

use color_eyre::Result;

#[tokio::main]
async fn main() -> Result<()> {
    let body = reqwest::get("https://www.rust-lang.org")
        .await?
        .text()
        .await?;

    println!("body = {body:?}");
    Ok(())
}

The feature is not rustls, but rustls-tls. While some optional dependencies create implicit features, the proper ones to use are list on  docs.rs/reqwest.


Error status for DNS errors

Setting DNS lookup error for connects
Print an error if more than one last error is set.

@bmiklautz @mfleisz @nfedera @MartinHaimberger Anyone time to review/merge this one?


Make ScopeIdsFixture compatible with Gradle 4.0+

By using the legacy task declaration syntax.

@bot-gradle test RFN

OK, I've already triggered ReadyForNightly build for you.


Remove Protobuf dependency

Coverage Report
Affected SDKs

FirebasePerformance-iOS-FirebasePerformance.framework
SDK overall coverage changed from 75.93% (1decaec)  to 92.33% (9bbcc00)  by +16.41%.
Filename
Base (1decaec)
Head (9bbcc00)
Diff

Test Logs

Base (1decaecc): https://github.com/firebase/firebase-ios-sdk/actions/runs/1113012935
Head (9bbcc00c): https://github.com/firebase/firebase-ios-sdk/actions/runs/1113358400

Tremendous increase in our code coverage just because of deleting these lines of code. Another feather in hat because of this change.


SSDS Should Error Out When Given A Nonexistent File/Folder To Upload

When attempting to upload a file that does not exist, ssds does not error out (but it should, I think), instead it looks to the user as if the upload succeeded...


Capture urls that isn't working properly

As of now, we can't figure out which URL:s are not working. E.g. don't respond to query or returns bogus data etc.
We need to be able to discover this in the update cycles.

I'd say this is somewhat solved, so I'll close the issue for now:
Can be seen in the log of the blockchain-monitor charm, and can be tested by running the db_util.py json validation.


Serverless Component V2

TBC

How's the progress on this going?

How's the progress on this going? Since it does not conform to the new v2 system it is kind of in a broken state. Cannot feed any inputs into it.

@m4tta As you can still is still in progress. I'll actually close this draft PR and reopen once I add more details.


cannot create net-attach-def resource when one of namespace failed to create/update

[ ] checked https://foundation-model-stack.github.io/multi-nic-cni/user_guide/troubleshooting/.
[ ] titled with the bug issue (if applicable).
[ ] provided corresponding information regarding the troubleshooting guidelines (CR list/detail, multi-nic cni controller and/or daemon status/log).

Describe the bug
A clear and concise description of what the bug is.
When any of namespace is in terminating state which causing an error to create/update net-attach-def in that namespace, multi-nic-cni may not be able to continue updating net-attach-def for the other newly-created namespace due to that error.
https://github.com/foundation-model-stack/multi-nic-cni/blob/fba59cff7b7c320fcd12c712209303f0caa7f4ca/plugin/net_attach_def.go#L120-L131
To Reproduce
Steps to reproduce the behavior:
1.
2.
3.
4.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.

manager container of controller and multi-nicd DS status:
multinicnetwork CR:
hostinterface list/CR:
cidr CR (multiNICIPAM: true):
ippools CR (multiNICIPAM: true):
log of manager container:
log of failed multi-nicd pod:

Environment (please complete the following information):

platform: [e.g. self-managed k8s, self-managed OpenShift, EKS, IKS, AKS]
node profile:
operator version :
cluster scale (number of nodes, pods, interfaces):

Additional context
Add any other context about the problem here.

handled by https://github.com/foundation-model-stack/multi-nic-cni/pull/114


Fix small command typo uninstall_sparrow.sh

Fix small command typo

Thanks for reviewing everything. If I was better with git, I would do more than one file at a time, but not confident with doing that yet. Thank you for your time.

Understood. No pressure, I don't mind either way, appreciate your efforts.
On Tue, Nov 26, 2024 at 2:55 PM secp512k2 @.***> wrote:

Thanks for reviewing everything. If I was better with git, I would do more
than one file at a time, but not confident with doing that yet. Thank you
for your time.
—
Reply to this email directly, view it on GitHub
https://github.com/ArmanTheParman/Parmanode/pull/81#issuecomment-2499600331,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASQCCX3MSPUFPVYZ7DNFIH32CPWJPAVCNFSM6AAAAABSO2F6BKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJZGYYDAMZTGE
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


Agent scheduler removal part 1

Taking the first steps outlined in the staging plan here:
https://github.com/microsoft/FluidFramework/pull/5716#issuecomment-816015051

/azp run repo-policy-check

/azp run Build - client packages


clarify whether null is a valid element

Java’s Stream supports it
most concurrent data structures do not support it

Given that there is no provision in the spec prohibiting the use of null, I think the current status is that it is prohibited. @reactive-streams/contributors Thoughts?

I believe it is currently not prohibited to use null as element. TCK wise we never check for values, other than ' the same element' in one or two tests with multiple subscribers. So this clarification, if decided to allow null (I'm for allowing) needs no tck updates. Though we could add a test that signals null into a subscriber then.

For implementors those nulls will be hellish, most of the concurrent queues dislike it.

I don't see why it needs to be specified. The only method this could impact is onNext.  Some (hopefully most) publishers will promise never to call onNext(null) because it would make no sense, and some (hopefully most) subscribers would treat them as indications that there is nothing-there,  and either skip them or treat them as errors.

@DougLea I suspect the problematic case will be the combination of null-publishing-publisher with non-null-receiving-subscriber.
In any case, it is completely possible to use a null-token to transport null safely in a CLQ for example.

yes. but those null-tokens will be custom per library?

or you mean that the users of a CLQ just do it internally

@drewhk I mean that since it is the CLQ of the Subscriber, any such handling is purely local.

that means in Akka, that the mailbox will have to support nulls after the Envelope removal. In this case the problem is that the underlying concurrency abstraction is not streams specific, and might not support nulls. I am not saying that this is necessarily a problem, it might be specific to Akka, but let's give it a bit thought before declaring nulls valid.

Ah forget it, I am too tired to think, no problem there.

To clarify: Banning nulls is a great policy because it avoids unsolvable issues about how to interpret them:  In most concurrent settings, sending "nothing" makes no sense, so it is usually banned, which also simplifies APIs. But if nulls are allowed to be sent here, it ought to be legal for any receiving stage (including relays) to skip them. (Thus they never enter queues etc.)

I'm all for banning null from onNext, would be great to get more opinions from @reactive-streams/contributors on this topic :)

In RxJava we have allowed it and use a NULL_SENTINEL whenever we are going via a queue. I don't have strong opinion either direction on allowing or banning it, just sharing that we did end up making the effort to support it, and we have had users over time who wanted the support (and have filed bugs when we didn't).

FWIW, future-streams supports nulls (without any special treatment); I have no reason to disallow them.
If a user doesn't realize nulls are disallowed and tries using them, maybe the spec should require immediate runtime failure on calling onNext(null). Otherwise the resulting error may be hard to understand for someone who isn't familiar with the implementation used. CLQ.add(null) throws a NullPointerException, but in theory an implementation could rely on the prohibition of nulls in a way that makes sending nulls a race condition or some other undefined, hard to debug behavior.
@DougLea why are you suggesting subscribers skip nulls? In most cases I would expect an error instead of silently ignoring input. If I write a Processor that maps elements, and it happens to be implemented using CLQ inside my streams library (not manually by me as a user), and it encounters a null, then I would want it to signal an error, not silently drop input.

@danarmak I just sent you 42 empty TCP packets as an answer.
Again, the main problem here is that there is no single right way to process nulls, so users who care about quality won't use them. (The in-progress j.u.c SubmissionPublisher does not allow them to be sent.) But that's not necessarily a reason to ban them outright.

@DougLea certainly, sometimes it's permissible or even expected to drop certain messages. But unless the subscriber understands the semantics of null stream elements, it shouldn't drop them. Just like a j.u.Collection may not support nulls, but then calling add(null) should throw a NullPointerException, and not 'drop' the element and return successfully.
Also, "empty" elements are often represented by something other than null (e.g. ByteString.empty), so the logic of what to drop needs to be explicitly added to the stream. IOW, I wouldn't want to rely on implicitly dropping nulls unless the spec outright requires it.
I think we should do one of:

Require implementations to support nulls. This is hard for some of them, so we don't want to.
Forbid implementations to support nulls, and require calls to onNext(null) results in an error (cancelling the subscription). This has the benefit of consistency, failing early, and making it obvious what caused the error. Every implementation has to remember to add a trivial check to onNext, and users who want to use nulls (because they naturally appear in their model) need to replace them with some other value.
Allow implementations to do whatever they want, as long as they document it, just as different collections may or may not support nulls.

Do you think some other option involving dropping is better?

My attitude is colored by a long history of dealing with this. I'd prefer to ban the use of null to mean anything other than "there is nothing here". But I settle for doing this only in components that I develop, and let people adapt to it  using sentinels etc if they need to. Which amounts to your option (3).

The problem here (that I see) is that if onNext-ing null is OK to be silently dropped, it needs to be specced so that demand counting doesn't go awry.
I'm fine with either A) Explicitly mandate that null is fine to send or B) Explicitly mandate that null yields an NPE from onSubscribe(null), onNext(null) or onError(null).
@reactive-streams/contributors Thoughts? :)

I vote for forbidding null.

I don't have a strong opinion on this so I'm fine either way. Existing stream libraries supporting nulls will have to start throwing an NPE when bridging into Reactive Streams if we go that route, but I'm fine with that.

onSubscribe(null) has nowhere to go (can't throw, can't call null.onError). For the other methods, I think the cost of enforcing non-nullness is greater than using null-sentinels. The former need to be put on every subscriber frontend at every stage (increasing method bytecode length as well), whereas the latter need to be put in front and back of helper data structures (i.e., queues) only.
Generally, the issue I see with forced onError based error reporting (since the 7 API methods mustn't throw) is that Subscribers need to be defensively serializing because rule violations happening on any thread has to be reported spec conformant.

@akarnokd Indeed, the behavior of Publisher.subscribe(null) should be outlined in the spec. Given that it is on the "outside" of the interactions (i.e. the first interaction) I'd think an IAE or NPE would be permissible. @reactive-streams/contributors, thoughts?

@viktorklang Same answer as onNext(null) (also for onSubscribe(null), onError(null)): Either say that behavior is undefined and implementation-dependent (thus allowing exceptions), or mandate that they cannot be null (thus requiring exceptions). Either approach conveys the message that reliable programs do not use nulls as sentinels.

@DougLea having a ban on null would be nicely symmetric for subscribe, onSubscribe, onNext and onError.

@reactive-streams/contributors Should we add a Rule requiring all signals to throw an NPE or (IAE?) if null is passed as a parameter?
Ie. illegal:
subscribe(null)
onSubscribe(null)
onNext(null)
onError(null)
(We should then update the TCK accordingly)

I'll open a PR that can be voted upon.


[Hub Generated] Review request for Microsoft.Batch to add version stable/2023-11-01

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

 Click here to see the details of Step 1
Breaking changes review (Diagram Step 1)
If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

 Click here to see the details of Step 2
ARM API changes review (Diagram Step 2)

If this PR is in purview of ARM review then automation will add the ARMReview label.
If you want to force ARM review, add the label yourself.
Proceed according to the diagram at the top of this comment.

 Click here to see the diagram footnotes
Diagram footnotes
[1] ARM review queue (for merge queues, see [4])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4] public repo merge queue, private repo merge queue (for ARM review queue, [1])
If you need further help with anything, see Getting help section below.

Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[x] New API version. (If API spec is not defined in TypeSpec, the PR should have been generated using OpenAPI Hub).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix swagger quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the Diagram Step 2, "ARM API changes Review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.

Getting help

For general PR approval workflow, see the diagram at the top of this comment.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

      "additionalProperties": {

https://armwiki.azurewebsites.net/api_contracts/guidelines/openapi.html#oapi032-only-use-additionalproperties-when-the-object-properties-are-dynamic-unknown-or-user-defined
fyi..

Refers to: specification/batch/resource-manager/Microsoft.Batch/stable/2023-11-01/BatchManagement.json:4287 in c392596. [](commit_id = c3925965b069dc7af9f9f03bbde4213a70386f04, deletion_comment = False)

    "writeAcceleratorEnabled": {

ARM recommends enums over booleans for future proof APIs.
Standard guidance is: replace boolean/switch properties with a more meaningful enum whenever possible.
A boolean will forever have two valid values (true or false). A string enum type is always preferred. Also, properties should always provide better values just than True and False. For example two switches "isTypeA" and "isTypeB" should be replaced with one enum "type": [A, B, DefaultType]. Enums are always a more flexible and future proof option because they allow additional values to be added in the future in a non-breaking way, e.g. [Enabled, Disabled, Suspended, Deallocated].

Refers to: specification/batch/resource-manager/Microsoft.Batch/stable/2023-11-01/BatchManagement.json:5501 in c392596. [](commit_id = c3925965b069dc7af9f9f03bbde4213a70386f04, deletion_comment = False)

      "type": "boolean",

https://github.com/Azure/azure-openapi-validator/blob/main/docs/enum-instead-of-boolean.md
applies in all places

Refers to: specification/batch/resource-manager/Microsoft.Batch/stable/2023-11-01/BatchManagement.json:6405 in c392596. [](commit_id = c3925965b069dc7af9f9f03bbde4213a70386f04, deletion_comment = False)

"ManagedDisk": {

https://github.com/Azure/azure-openapi-validator/blob/main/docs/schema-description-or-title.md
Missing title or description

Refers to: specification/batch/resource-manager/Microsoft.Batch/stable/2023-11-01/BatchManagement.json:6375 in c392596. [](commit_id = c3925965b069dc7af9f9f03bbde4213a70386f04, deletion_comment = False)

/pr RequestMerge


Use timeouts instead of relying on runtime.GoSched

ping @LK4D4 @aaronlehmann

LGTM

@LK4D4 Updated... hoped nobody would notice that :)

LGTM


It doesn't work

Hey. The plugin just doesn't work.
Before using the plugin I got at least source mapping to the built file of a dependency.
Now I just get nothing.
import babel from 'rollup-plugin-babel';
import commonjs from 'rollup-plugin-commonjs';
import resolve from 'rollup-plugin-node-resolve';
import sourcemaps from 'rollup-plugin-sourcemaps';

import pkg from './package.json';

export default {
  input: 'src/index.js',
  output: [
    {
      file: pkg.main,
      format: 'cjs',
      sourcemap: true,
      compact: true,
      exports: 'named'
    },
    {
      file: pkg.module,
      format: 'es',
      sourcemap: true,
      compact: true,
      exports: 'named'
    }
  ],
  plugins: [
    babel({
      babelrc: false,
      exclude: '../../node_modules/**',
      presets: [
        ['@babel/env', {
          exclude: ['transform-regenerator']
        }]
      ],
      plugins: [
        '@babel/proposal-class-properties'
      ]
    }),
    commonjs(),
    resolve(),
    sourcemaps()
  ]
};

Without this plugin:

With this plugin:

I would expect to get source mapping to document-canvas-vanilla/src instead.

This plugin implements a custom load hook as described here. Perhaps the Babel plugin is interfering? Looks like Babel already has this capability built in by using the inputSourceMap, have you tried that?

Ah, interesting that Babel has this built-in.
Anyway, you pointed me to a misconfiguration of Babel. Actually document-canvas-vanilla/src should be excluded in Babel. If I exclude this, everything works fine.


Test error: test OKs code that does not compile

From #1785 , that example does not compile:
Too few positionals passed; expected 1 argument but got 0
  in block <unit> at callable-containers.p6 line 3

But the chunk does:
ok 8 - doc/Language/containers.pod6 chunk 8 starts with “my &c = ->” compiles

FYI, the code mentioned here no longer exists on that page. Can you post the specific problematic code here, or point to a github URL (with line numbers) that shows the code?

Note that your message above appears to be a run time error; the code isn't executed if at all possible, only compiled.

The code is in the issue; I changed that so it's no longer on the page. And you are right, it's a runtime error, so it's best to just close it.


bunBuild with error handling

Current dependencies on/for this PR:

main

PR #3   👈

This comment was auto-generated by Graphite.


Attaching file

The file component upload works on this editor? How I can use it?
Thanks!

Did you read and try this, and if yes, where exactly did it not work:
https://github.com/manogi/nova-tiptap#links-and-linksettings-and-filesettings


Is there any plan to support drupal 8?

I also help with the Drupal snippets for sublimetext which has also prompted this question but also in general a move towards making an general repo for Drupal snippets. This can be tracked here: https://github.com/robballou/drupal-snippets/issues/1

While I personally support any effort to standardize and outsource the snippet management across IDEs so we can just compile the vendor specific formats with gulp or something I'm not against creating snippets that you find useful in the mean time for a starting point.
At question would be supporting each snippet vocabulary independently because I assume you move between D7 and D8 development as much as i do and changing it by had would be a pain.
Would we prefer to do drupal version detection on the files for snippet loading (via adding d7/d8 grammar class or somesuch) or supporting all snippets simultaneously?
Also which type of snippets are most useful?

Added some experimental code (to another branch) above that detects the Drupal version and updates the scope. Check it out! Maybe that'll help with doing different snippets.


How to resolve dependencies based on type?

If I have two classes:
class Foo (
    contructor(@inject("IValidator") private validator: IValidator<Foo>) {}
)

class Bar (
    contructor(@inject("IValidator") private validator: IValidator<Bar>) {}
)

Can I have two separate instances of validator in this situation? Could I have a BarValidator class and a FooValidator class?

Typescript interfaces are not objects like classes are. Trying to bind a value to a interface will cause a "Interface" only refers to a type, but is being used as a value here error.
That's why we can't use @inject(IValidator), and instead we need to use @inject("IValidator") (as string).
Unfortunately, due to this limitation, the only solution is to register two distinct types on the container so you can resolve them later on.
container.register<IValidator<Foo>>("IValidator<Foo>", { useValue: validatorFooInstance });
container.register<IValidator<Bar>>("IValidator<Bar>", { useValue: validatorBarInstance });

Thanks!


typo error corrected in HowItWork component

#36 corrected typo error in How it works component from excess to access
@rishipurwar1

#36 corrected typo error in How it works component from excess to access
@rishipurwar1

merged your pr.
Thanks for your contribution.


Visualization question

Awesome work !!! I want to ask that is there any specific reason to seperate the "pruned & reused later" and "pruned & reused in the next layer" token ? As shown below:

This shows that if a token is to be reused, it is likely it will be reused immediately after it's pruned. This is intuitive, because when a token is not used for consecutive several layers, its feature would be far from what the current layer's features represent and thus becomes unusable.

Thanks for your reply. I also want to ask that in the left figure, how is the ratio of tokens calculated ? Does the three columns sum to the token prune ratio in that layer ? For example, in the fourth layer, the three columns sum to approximately 0.45, so the prune ratio of tokens in the fourth layer is 0.45 ?

Hi, the first two columns add up to the pruning ratio of that layer. So fo the 4th layer, the pruning ratio is about 0.3.
The third column is a subset of the second column. Note that for layer 11, since all later layers = the next layer, column 2 equals column 3.

@kaikai23 Thanks for your reply


[intern] GIF Recorder Rectangle Selection Overlay UI

Summary of the Pull Request
Drag and drop to draw rectangle in area below toolbar, can resize/move. Lock selection in place when record button is clicked. Selection is cleared when stop button is clicked. (added ResizableRectangle class from online tutorial)
Edit:
ResizableRectangle Credit to: https://github.com/kareemsulthan07/ResizableRectangleSample
YouTube video series (9 parts): https://www.youtube.com/watch?v=a8IsZFUIzQo

We've moved over to WPF to allow transparent background and to use ScreenToGif backend


Update Dockerfile with latest MarkupSafe

There was an error when building the docker image. Solution: Upgrade to the latest MarkupSafe (at this time 1.1.1). See the below error:
  File "/tmp/pip-install-rrl3_k3v/MarkupSafe/setup.py", line 6, in <module>
    from setuptools import setup, Extension, Feature
ImportError: cannot import name 'Feature'
----------------------------------------

Thanks for providing the fix! I also hit this issue


New terms, issue #1176

New terms from issue #1176
Calling make all in following error that needs to be resolved:
MANCHESTER PARSE ERROR the expression 'specimen and (is_specified_output_of some 'collecting specimen from organism') and ('derives from' some trachea)' at row 70, column 8 in table "src/ontology/templates/biobank-specimens.tsv" cannot be parsed: encountered unknown 'trachea'

So far so good.

Please use the UBERON "replacement" terms from this comment: https://github.com/obi-ontology/obi/issues/1176#issuecomment-689071343 When that's done, I'll update the UBERON imports to fix the parse error.

Please remove 'aspiration specimen collection' from the table. It's not a type of specimen, so we'll put it somewhere else.

Thanks. I'll take care of the next step.
It would have been better not to commit the deletion of biobank-specimens.owl. I'll rebuild it.

I updated the imports and made some changes to the table.
Please use Protege to add 'aspiration specimen collection' to src/ontology/obi-edit.owl.
There are still some problems to fix for the aspirate stuff.

@apmody there are a bunch of changes to biobank-specimens.tsv that are making it difficult to see what's changed. Is there a reason quotes were added to the definition source field? Since these are TSVs, not CSVs, I don't think we need to enclose these in quotes.
Side note, there's also some trailing space on some of those values (e.g. "Chris Stoeckert, NCI BBRB ")

I'm pretty sure that I ran make sort and it added these quotes (because the fields contain commas).

Do we want to keep them or should I clean that up?

I think it's right now, and will be stable going forward.

@apmody please disregard the review, I will update the definitions. Thanks!

After updating the definitions, I re-ran make sort and it removed those quotes. I think that should be fine going forward?


Zicond gcc/binutils/qemu support status

Hello, I am wondering where I can find the update to date zicond patches for gcc/binutils/qemu. I found some links in this page below:
https://docs.google.com/spreadsheets/d/10uWgib-DFQ40WfaoWY9l521s3-Pn4Pp3hH0BgnSk8qY/edit?pli=1#gid=1983095369
but not sure is it up to date, could someone make some comments if there are updated patches.
As I can observe, these patches are not yet in upstream projects.
Thanks

I also wonder about the GCC version supporting zicond extension for RISC-V. There is also a patch mentioned in that link but I cannot find a way to compile for zicond by supplying the mentioned flags -march=rv64gc_zicond or -march=rv64gc_xventanacondops.
Could anyone help me too?


Configure logging

Where do our logs go, what do other freeCodeCamp project do? Can and if so, are we happy to re-use this?
/cc @freeCodeCamp/open-api

Thanks!
Is Datadog giving us a good deal, the lack of data retention over 24 hours in the free tier sounds like a blocker. As Opbeat has been acquired by Elastic thats a dead end.
The Elastic offerings sound interesting. I have seen quite a high operational load on keeping and ELK stack performing at scale, which makes me a little wary of using it in a small team. However
if we get enough AWS credits to run the Elastic products for free it would definitely be an interesting option to explore!
How far are you in exploring running a self hosted ELK? Shall we set up a call this week and catch up?

I am planning to re-route the beta instance logs to a small EC2 instance on AWS as a spike with the elastic stack. I am unsure when I will get that ready though. It will need some changes on the beta itself.
But yeah I am up for a call around Thursday if you would like to catch up. Will send you an invite.

We've had our meeting and decided to use Cloudwatch for now. What remains to do for this issue is to improve log messages by adding the API GW ID
Lambda see https://docs.aws.amazon.com/lambda/latest/dg/nodejs-prog-model-logging.html
Interesting trick to be able to track which API GW request caused a Lambda log message https://aws.amazon.com/blogs/compute/techniques-and-tools-for-better-serverless-api-logging-with-amazon-api-gateway-and-aws-lambda/
API gw see https://docs.aws.amazon.com/apigateway/latest/developerguide/set-up-logging.html
Usage: https://docs.aws.amazon.com/lambda/latest/dg/monitoring-functions-logs.html


debug test failures under linux

Fixes all but one of the remaining test failures under linux.  I'm still working on the last one, but it doesn't appear to be a correctness issue.  The test can safely be commented out locally until I get a real fix in.

Thanks, Dan!


kernel: Deprecate sys_clock_us_per_tick variable.

On some architectures tick time cannot be expressed as integer
number of microseconds, introducing error in calculations using
sys_clock_us_per_tick variable.
This commit deprecates the sys_clock_us_per_tick variable and
replaces its usage by more precise calculations based on
sys_clock_hw_cycles_per_sec and sys_clock_ticks_per_sec.

Codecov Report

Merging #9026 into master will increase coverage by 0.1%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master    #9026     +/-   ##
=========================================
+ Coverage   52.32%   52.43%   +0.1%
=========================================
  Files         197      192      -5
  Lines       24797    24166    -631
  Branches     5158     5040    -118
=========================================
- Hits        12975    12671    -304
+ Misses       9742     9472    -270
+ Partials     2080     2023     -57

Impacted Files
Coverage Δ

drivers/timer/native_posix_timer.c
86.11% <100%> (ø)
:arrow_up:

subsys/net/ip/net_context.c
63.93% <0%> (-3.28%)
:arrow_down:

subsys/net/ip/net_stats.h
62.79% <0%> (-3.05%)
:arrow_down:

subsys/net/ip/net_if.c
62.02% <0%> (-1.31%)
:arrow_down:

subsys/net/ip/net_pkt.c
60.16% <0%> (-1.25%)
:arrow_down:

subsys/net/buf.c
56.65% <0%> (-1.24%)
:arrow_down:

subsys/net/ip/net_core.c
70% <0%> (-0.68%)
:arrow_down:

include/net/net_pkt.h
84.21% <0%> (-0.41%)
:arrow_down:

subsys/net/ip/net_tc.c
91.3% <0%> (-0.37%)
:arrow_down:

drivers/ethernet/eth_native_posix.c

... and 6 more

Continue to review full report at Codecov.

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


IOS sonoma

Hello! I recently updated my mac, and now I can see that the spaces is not updating every time I switch it. What do I do ?

Have you updated yabai to v6?

I have, and restarted the system, but still does not work


No known languages found for specification English.

Hey,
I am trying to build one of our projects but it fails with the following exception:
  ⨯ No known languages found for specification English.  stackTrace=
                                                           NoSuchLanguageError: No known languages found for specification English.
                                                               at Function.bySpec (/Users/dmey/workspace/drive/node_modules/dmg-license/lib/Language.js:35:19)
                                                               at Object.indexByLanguage (/Users/dmey/workspace/drive/node_modules/dmg-license/lib/Language.js:81:41)
                                                               at labelCache (/Users/dmey/workspace/drive/node_modules/dmg-license/lib/assembleLicenses.js:92:35)
                                                               at Object.assembleLicenses [as default] (/Users/dmey/workspace/drive/node_modules/dmg-license/lib/assembleLicenses.js:117:23)
                                                               at dmgLicensePlist (/Users/dmey/workspace/drive/node_modules/dmg-license/lib/index.js:27:78)
                                                               at dmgLicense (/Users/dmey/workspace/drive/node_modules/dmg-license/lib/index.js:21:62)
                                                               at dmgLicenseFromJSON (/Users/dmey/workspace/drive/node_modules/dmg-license/lib/index.js:37:18)
                                                               at addLicenseToDmg (/Users/dmey/workspace/drive/node_modules/dmg-builder/src/dmgLicense.ts:57:9)

The exact same configuration is working on my workmates device.
What is the exact problem in this case?
Thanks and best regards,
Dominic

Instead of English, you need to use an IETF language tag like en-US or a numeric Classic Mac OS region code like 0. There's a list of which language tags and region codes are supported.
Please reopen this issue if you're still having trouble.

Looks like everything's working now, so I'll go ahead and close this. Glad I could help!


Not working in Jest 25.4.0 version

It's working after recent Jest updates. I get the following error:
TypeError: runtime.unstable_shouldLoadAsEsm is not a function
        at jasmine2 (node_modules/@jest/core/node_modules/jest-jasmine2/build/index.js:210:23)
        at node_modules/@jest-runner/electron/node_modules/jest-runner/build/runTest.js:385:24

same here

Different line numbers, but same error:
    TypeError: runtime.unstable_shouldLoadAsEsm is not a function
        at jasmine2 (/node_modules/@jest/core/node_modules/jest-jasmine2/build/index.js:188:25)
        at /node_modules/@jest-runner/electron/node_modules/jest-runner/build/runTest.js:385:24
        at Generator.next (<anonymous>)
        at asyncGeneratorStep (/node_modules/@jest-runner/electron/node_modules/jest-runner/build/runTest.js:161:24)
        at _next (/node_modules/@jest-runner/electron/node_modules/jest-runner/build/runTest.js:181:9)

      at jasmine2 (node_modules/@jest/core/node_modules/jest-jasmine2/build/index.js:188:25)
      at Server.emit (node_modules/event-pubsub/es5.js:74:21)
      at Server.gotData (node_modules/node-ipc/dao/socketServer.js:194:14)

My temporary fix is to patch / replace const esm = runtime.unstable_shouldLoadAsEsm(testPath); with const esm = false; in node_modules/jest-jasmine2/build/index.js(which could be a subfolder ofnode_modules/@jest/core/`, depending on your local NPM/Yarn setup.
Source code references:
https://github.com/facebook/jest/blob/7a7710d2c9cdc7da97a3674c36f1ca46f7068f78/packages/jest-jasmine2/src/index.ts#L159
https://github.com/facebook/jest/blob/7a7710d2c9cdc7da97a3674c36f1ca46f7068f78/packages/jest-jasmine2/src/index.ts#L180

There are many ways to implement the aforementioned patch, but as this is a temporary measure, FYI I simply wrote a quick postinstall script in my package.json to patch jest-electron-runner until it is upgraded to the latest Jest 25.4.x:
"patchElectronJestRunner2": "node scripts/replace-in-file.js<EMAIL_ADDRESS>'const esm = runtime.unstable_shouldLoadAsEsm' 'const esm = false; // runtime.unstable_shouldLoadAsEsm'",

...where scripts/replace-in-file.js is:
const path = require('path');
const fs = require('fs');
const args = process.argv.slice(2);
const filePath = path.join(process.cwd(), args[0]);
let fileStr = fs.readFileSync(filePath, { encoding: "utf8" });
const regex = new RegExp(args[1], "g");
fileStr = fileStr.replace(regex, args[2]);
fs.writeFileSync(filePath, fileStr, { encoding: "utf8" });

Quick and dirty :)

I founded a way to fix this:
Yarn: https://classic.yarnpkg.com/en/docs/selective-version-resolutions/
Npm: https://github.com/rogeriochaves/npm-force-resolutions
In your package.json, add:
  "resolutions": {
    "@jest-runner/electron/jest-haste-map": "^25.4.0",
    "@jest-runner/electron/jest-mock": "^25.4.0",
    "@jest-runner/electron/jest-runner": "^25.4.0",
    "@jest-runner/electron/jest-runtime": "^25.4.0",
    "@jest-runner/electron/jest-util": "^25.4.0"
  }

And run yarn install.
This even fixes the console error #54

Pipeline: https://dev.azure.com/ai-scanlation/ai.scanlation/_build/results?buildId=969&view=logs&j=12f1170f-54f2-53f3-20dd-22fc7dff55f9&t=bd05475d-acb5-5619-3ccb-c46842dbc997&l=34
It's a temporary way until jest-electron-runner is updated.

https://github.com/facebook-atom/jest-electron-runner/pull/62 should have fixed it! sorry about the breakage

published<EMAIL_ADDRESS>


Added support for package prerequisite

Summary
Some plugins require certain Python packages to be installed. This changes added a decorator to support that, similar to the original @requires decorator.
Type
New feature

self-merging to unblock @praetorian-rad


"characteristic was supplied illegal value" errors

Started getting these errors today out of the blue:
[16/09/2022, 2:43:24 pm] [homebridge-panasonic-ac-platform] This plugin generated a warning from the characteristic 'Cooling Threshold Temperature': characteristic was supplied illegal value: number 10 exceeded minimum of 16. See https://homebridge.io/w/JtMGR for more info.
[16/09/2022, 2:43:24 pm] [homebridge-panasonic-ac-platform] This plugin generated a warning from the characteristic 'Heating Threshold Temperature': characteristic was supplied illegal value: number 0 exceeded minimum of 1. See https://homebridge.io/w/JtMGR for more info.
Tried manually setting the minimum temperature to 0 via the plugin settings but that didn't work.

I think you have a "extra heater" in your device,
from config.schema.json;
      "minHeatingTemperature": {         "title": "Minimum heating temperature (override)",         "description": "The default heating temperature range is 16-30°C. Some Panasonic ACs have an additional heating mode for the range of 8-15°C. If you own such a model, you can use this setting to adjust the minimum value. Leave it empty or undefined to use the default value.",         "type": "integer",         "placeholder": "16"

@johnsonwalker, did you restart Homebridge after adjusting the configuration? That would be required for the changes to take effect.

hi, I'm new in this community. I want to ask for a secondary account with Panasonic comfort cloud. when I'm trying to create the second account is not letting me, because I'm putting the same Device id. can someone help me with what to do, please?

For the first time to connect I have used 2 on remote.
For sub accounts I have used 3 on remote.
So my workflow for sub-account is;

open app
new ID with different E-mail
5 sec WiFi button (on remote)
3 “set” (on remote)
enter password
Put in message for main-account “text”

After this the main-account must accept the request

Thanks Jurgen I will give it a try
On 13 Nov 2022 at 20:01 +0100, JurgenLB @.***>, wrote:

For the first time to connect I have used 2 on remote.
For sub accounts I have used 3 on remote.
So my workflow for sub-account is;
• open app
• new ID with different E-mail
• 5 sec WiFi button (on remote)
• 3 “set” (on remote)
• enter password
• Put in message for main-account “text”
After this the main-account must accept the request
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

hi, I'm new in this community. I want to ask for a secondary account with Panasonic comfort cloud. when I'm trying to create the second account is not letting me, because I'm putting the same Device id. can someone help me with what to do, please? and another thing on the temps is saying "[Homebridge Panasonic AC Platform] Temperature state is not available

Hi! Please create a new issue for this rather than inserting a different problem statement into an existing topic.


Generate ESM functions for Netlify

Netlify currently transpiles serverless functions with ESM syntax down to CJS, which is causing problems such as https://github.com/sveltejs/kit/issues/6462.
We've started to address that in https://github.com/netlify/zip-it-and-ship-it/pull/1198, which emits ESM files for functions with a .mjs extension.  This is done with a per-function configuration file introduced in https://github.com/netlify/zip-it-and-ship-it/pull/1030.
With that in place, this PR has the following changes:

The conditional logic that decided whether to create CJS or ESM functions was removed, and it now generates ESM only
The generated function files use the .mjs extension
There's an additional file generated for each function, containing the configuration property mentioned above

We're in the final stages of rolling out this functionality to all customers, but wanted to get the PR in front of you sooner rather than later to gather any feedback and improve the experience for SvelteKit users as soon as possible.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

Is it necessary to use the .mjs extension if a user has "type": "module" in their package.json? (which all SvelteKit users will have)

For now, yes. We'll gradually roll out ESM support for .js files, but using .mjs allows you to opt-in to this behaviour straight away.

To clarify, would it be okay if we merge this PR and roll it out to our users now or do we need to wait for something on your side still?

We need to update our CLI with this change, which we'll do today. I'll keep this thread updated and let you know once it's good to merge.

Does this work properly if somebody has manually set their bundler to esbuild?

Does this work properly if somebody has manually set their bundler to esbuild?

Yes, esbuild will respect these settings.

Awesome!! Thank you so much!


Copies of snapshots have the same IP address

LXD assigns the same IP address to containers in the following sequence of events:
lxc launch trusty something #"trusty" is 73500357e4d4
lxc snapshot something whatever
lxc copy something/whatever clone1
lxc copy something/whatever clone2
lxc start clone1
lxc start clone2
lxc list
What happens:
clone1 and clone2 report having the same (ipv4) address.
What should happen:
clone1 and clone2 have different (ipv4) addresses.

This is caused by a missing reset of the volatile keys on copy.


Npm run start is very slow

It used to be pretty fast, but it takes almost 2 minutes to start the development server.
Am I the only one experiencing this ?

Alright, apparently this is because of my the web browser i use


The same layer version is specified for v1.0.2 and v1.0.3 in github releases

Description
The layer version is not updated in the v1.0.3 release note. I assume the latest version is 4:
https://github.com/SumoLogic/sumologic-lambda-extensions/releases/tag/v1.0.3

https://github.com/SumoLogic/sumologic-lambda-extensions/releases/tag/v1.0.2

Yes version is 4


UI Bug - UI Elements disappear When Cancel is clicked on New Unit Test

Open a transformation with a unit test applied. You can see the UI elements for input data etc. Click New Unit Test and then Cancel on the popup dialog. The UI elements for the original unit test disappear although the unit test is still applied to the transformation.
Click Switch and reselecting the Unit Test will obviously bring back the UI elements even thought the unit test was actually still attached

Nice catch, thanks Harris!


[WIP] Factor out common fields from enum variants

Work in progress. This will soon™ close #6129.
Still to be done:

[x] Update code that created the old enum
[ ] Update usage of the old enum
Mostly done. Still have to deal with rest patterns .. and converting literal values in patterns into match guard/nested if where required.
[ ] Support record fields in the enums
[ ] Support generic enums
[ ] Maybe prompt user for the name of the enum (and the struct fields if using enums with tuple fields)? Or just make users use the already available renaming feature.
[ ] Deal with attributes. Probably just copy derives.

Closing due to inactivity, feel free to get back to this at any time!


Feat/hermes wasm ap is

Description
Thanks for contributing to the project!
Please fill out this template to help us review your changes.
Related Issue(s)
List the issue numbers related to this pull request.

e.g., Closes #123, Resolves #456  Fixes #367

Description of Changes
Provide a clear and concise description of what the pull request changes.
Breaking Changes
Describe any breaking changes and the impact.
Screenshots
If applicable, add screenshots to help explain your changes.
Related Pull Requests
If applicable, list any related pull requests.

e.g., #123, #456

Please confirm the following checks

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream module

all this already done in these PRs:
https://github.com/input-output-hk/hermes/pull/72
https://github.com/input-output-hk/hermes/pull/58