Create version of the HTTP tracking client that supports 2.17

What and why?
Dart 2.17 will add two methods to HttpClient which we need to override. Currently, only developers using Flutter's beta channel will need this, but I'd rather stay ahead of it.
I'm keeping this on a release branch as a majority of users are going to be on Dart 2.16 until Flutter 2.12. for a while. Once Flutter 2.12 goes GA, we'll merge to master and likely close this release branch.
How?
Change version solving to put Dart 2.17 as the minimum version.
Review checklist

[ ] This pull request has appropriate unit and / or integration tests
[ ] This pull request references a Github or JIRA issue

Actually re-changed my mind.  The published pubspec already only supports up to Dart 2.16, so I'm going to have to push a new version anyway to support 2.17, and I prefer having the safety of the checks by not casting to dynamic.

Note for anyone that might be waiting on this -- The CI failures are due to this issue: https://github.com/flutter/flutter/issues/102330, but it's unlikely to be fixed as it appears to not be caused by the Flutter framework.
I'm actively looking for a solution which bypasses the iOS os.activity framework.


[unige] Add extractor for UniGE mediaserver

Before submitting a pull request make sure you have:

[x] Searched the bugtracker for similar pull requests
[x] Read adding new extractor tutorial
[x] Read youtube-dl coding conventions and adjusted the code to meet them
[x] Covered the code with tests (note that PRs without tests will be REJECTED)
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[ ] Improvement
[x] New extractor
[ ] New feature

Description of your pull request and other information
This enables to extract videos posted to the University of Geneva mediaserver, located at https://mediaserver.unige.ch. It supports:

Single courses/videos
Whole course "playlists" (accessible by clicking on the course's title)

Thanks and cheers !

Thanks for your work!
Before progressing this PR (and sorry for the slow response), I'd like to check that content is generally accessible outside the University. If not, it would be better to serve a local yt-dl fork for UniGe users.

Thanks for your reply !
It depends on the videos. Some of them are public, and others need authentication.
Cheers
On December 2, 2023 2:33:31 PM GMT+01:00, dirkf @.***> wrote:

Thanks for your work!
Before progressing this PR (and sorry for the slow response), I'd like to check that content is generally accessible outside the University. If not, it would be better to serve a local yt-dl fork for UniGe users.
--
Reply to this email directly or view it on GitHub:
https://github.com/ytdl-org/youtube-dl/pull/32596#issuecomment-1837150130
You are receiving this because you authored the thread.
Message ID: @.***>


add command 'julia-client:reset-workspace'

I found myself killing the process and running execute-all alot which is quite slow. This makes it pretty fast

Thanks for the patch! I'd like to be more clear on what specifically the issue is if possible.
Since there are keybindings for both kill and eval-all I would've expected that to be quite quick. I guess you're trying to replace this with the workspace() command to avoid Julia's boot time, and want there to be a command rather than typing it into the console?

yea thats right. For me it saved about 10s each restart on the project I was working on but I have a slow juliarc file so most people probably wouldn't gain that much. But it will always be faster since it allows Julia to reuse JITed code

I tried manually typing workspace() but I was doing it often enough that it got old real fast

Sorry to nitpick, this is coming along nicely though!


cpu usage not shown in Android Nougat 7.0

After upgrading from OmniRom 6.0.x to CopperHeadOS based on Android Nougat 7.1.1 only cpu frequency is shown. No values available for cpu load.

How about v2.0.0 ?


vapoursynth: add withPlugins interface

This PR patches vapoursynth to allow specifying the plugin directory in an environment variable. This allows for a withPlugins interface to create a vapoursynth environment with the specified plugins.
Motivation for this change
Currently, there is no nice way for using vapoursynth with plugins. A workaround exists (https://github.com/NixOS/nixpkgs/pull/58859#issuecomment-479397341), but has its drawbacks (e.g. temporary usage with nix run or nix-shell does not work, it does not support multiple environments with different plugins etc.).
Since there is no upstream support for specifying a plugin directory other than in the global configuration file, I added the ability to load plugins from the directory specified in VAPOURSYNTH_PLUGIN_PATH as a patch. This is probably not the best option for implementing this, but my other idea (resolving the plugin path relative to the shared library at runtime) would require copying (instead of symlinking) the vapoursynth shared library so the plugin path can be found relative to it. That seemed even worse, so I chose the former option.
An example plugin environment can be built from the following expression: vapoursynth.withPlugins [ vapoursynth-mvtools vapoursynth-editor ]
This includes vapoursynth-editor as a plugin (even though it isn’t), since that way the plugin path also gets added to the wrapper of vsedit.
This also adds the VAPOURSYNTH_PLUGIN_PATH environment variable to the mpv wrapper when vapoursynth support is enabled. Example:
wrapMpv
  (mpv-unwrapped.override {
    vapoursynthSupport = true;
    vapoursynth = vapoursynth.withPlugins [
      vapoursynth-mvtools
    ];
  })
  { }

I’m open for suggestions, as I acknowledge that this solution is somewhat of a hack.
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110365 run on x86_64-darwin 1

1 package failed to build and are new build failure:

vapoursynth-editor: log https://termbin.com/tmmb

2 packages built:

vapoursynth
vapoursynth-mvtools

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110365 run on x86_64-darwin 1

1 package failed to build and are new build failure:

vapoursynth-editor: log https://termbin.com/tmmb

2 packages built:

vapoursynth
vapoursynth-mvtools

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110365 run on x86_64-linux 1

3 packages built:

vapoursynth
vapoursynth-editor
vapoursynth-mvtools

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110365 run on x86_64-linux 1

3 packages built:

vapoursynth
vapoursynth-editor
vapoursynth-mvtools

Force pushed to rebase and to fix dependencies (propagatedBuildInputs) of plugins not being included in the python path.

Force pushed to rebase and to fix dependencies (propagatedBuildInputs) of plugins not being included in the python path.

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110365 run on x86_64-darwin 1

1 package failed to build and are new build failure:

vapoursynth-editor: log https://termbin.com/t454

1 package built:

vapoursynth

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110365 run on x86_64-darwin 1

1 package failed to build and are new build failure:

vapoursynth-editor: log https://termbin.com/t454

1 package built:

vapoursynth

Ok, I managed to simplify it a bit. I think symlinkJoin instead of buildEnv is more appropriate, because what we really want here are real directories of symlinked files. Here's an updated patch
commit cd7026359549cf0ee6efa7de256c52e31a80e3de
Author: Simon Bruder<EMAIL_ADDRESS>Date:   Thu Jan 21 15:53:58 2021 +0100

    vapoursynth: add withPlugins interface

    Since nixpkgs does not currently have an attribute set with plugins, the
    usage differes from python-style withPackages as it accepts a list
    instead of a function as a parameter.

    Using plugins in other programs that require vapoursynth (like `vsedit`)
    can be achieved by adding it to the plugin list (e.g.
    `vapoursynth.withPlugins [ vapoursynth-editor … ]`) or by passing the
    `VAPOURSYNTH_PLUGIN_PATH` variable.

diff --git a/pkgs/development/libraries/vapoursynth/default.nix b/pkgs/development/libraries/vapoursynth/default.nix
index 93f8d3c5ae5..6723868746d 100644
--- a/pkgs/development/libraries/vapoursynth/default.nix
+++ b/pkgs/development/libraries/vapoursynth/default.nix
@@ -1,4 +1,6 @@
-{ lib, stdenv, fetchFromGitHub, pkg-config, autoreconfHook, makeWrapper
+{ lib, stdenv, fetchFromGitHub, pkg-config, autoreconfHook
+, symlinkJoin, makeWrapper
+, vapoursynth
 , zimg, libass, python3, libiconv
 , ApplicationServices
 , ocrSupport ?  false, tesseract ? null
@@ -21,6 +23,10 @@ stdenv.mkDerivation rec {
     sha256 = "1krfdzc2x2vxv4nq9kiv1c09hgj525qn120ah91fw2ikq8ldvmx4";
   };

+  patches = [
+    ./plugin-path-environment-variable.patch
+  ];
+
   nativeBuildInputs = [ pkg-config autoreconfHook makeWrapper ];
   buildInputs = [
     zimg libass
@@ -42,6 +48,30 @@ stdenv.mkDerivation rec {
     # wrapper, what python3 version was used to build vapoursynth so
     # the right python3.sitePackages will be used there.
     inherit python3;
+
+    withPlugins = plugins:
+      let
+        pythonEnvironment = python3.buildEnv.override { extraLibs = plugins; };
+      in
+      symlinkJoin {
+        name = "${vapoursynth.name}-with-plugins";
+        paths = [ vapoursynth ] ++ plugins;
+        buildInputs = [ makeWrapper ];
+        postBuild = ''
+          for symlink in $out/bin/*; do
+            # remove the original symlink
+            original="$(realpath "$symlink")"
+            rm "$symlink"
+
+            makeWrapper "$original" "$symlink" \
+              --set VAPOURSYNTH_PLUGIN_PATH $out/lib/vapoursynth \
+              --prefix PYTHONPATH : ${pythonEnvironment}/${python3.sitePackages}
+          done
+        '';
+
+        # passthrus must be specified here, again
+        passthru = { inherit python3; };
+      };
   };

   postInstall = ''
@@ -54,7 +84,6 @@ stdenv.mkDerivation rec {
     homepage    = "http://www.vapoursynth.com/";
     license     = licenses.lgpl21;
     platforms   = platforms.x86_64;
-    maintainers = with maintainers; [ rnhmjoj tadeokondrak ];
+    maintainers = with maintainers; [ rnhmjoj sbruder tadeokondrak ];
   };
-
 }
diff --git a/pkgs/development/libraries/vapoursynth/plugin-path-environment-variable.patch b/pkgs/development/libraries/vapoursynth/plugin-path-environment-variable.patch
new file mode 100644
index<PHONE_NUMBER>0..80f98633d7f
--- /dev/null
+++ b/pkgs/development/libraries/vapoursynth/plugin-path-environment-variable.patch
@@ -0,0 +1,16 @@
+diff --git a/src/core/vscore.cpp b/src/core/vscore.cpp
+index 2d29844d..fd4cbea5 100644
+--- a/src/core/vscore.cpp
++++ b/src/core/vscore.cpp
+@@ -1351,6 +1351,11 @@ VSCore::VSCore(int threads) :
+     } // If neither exists, an empty string will do.
+ #endif
+
++    const char *pluginPath = getenv("VAPOURSYNTH_PLUGIN_PATH");
++    if (pluginPath) {
++        loadAllPluginsInPath((std::string)pluginPath, filter);
++    }
++
+     VSMap *settings = readSettings(configFile);
+     const char *error = vs_internal_vsapi.getError(settings);
+     if (error) {

Ok, I managed to simplify it a bit. I think symlinkJoin instead of buildEnv is more appropriate, because what we really want here are real directories of symlinked files. Here's an updated patch
commit cd7026359549cf0ee6efa7de256c52e31a80e3de
Author: Simon Bruder<EMAIL_ADDRESS>Date:   Thu Jan 21 15:53:58 2021 +0100

    vapoursynth: add withPlugins interface

    Since nixpkgs does not currently have an attribute set with plugins, the
    usage differes from python-style withPackages as it accepts a list
    instead of a function as a parameter.

    Using plugins in other programs that require vapoursynth (like `vsedit`)
    can be achieved by adding it to the plugin list (e.g.
    `vapoursynth.withPlugins [ vapoursynth-editor … ]`) or by passing the
    `VAPOURSYNTH_PLUGIN_PATH` variable.

diff --git a/pkgs/development/libraries/vapoursynth/default.nix b/pkgs/development/libraries/vapoursynth/default.nix
index 93f8d3c5ae5..6723868746d 100644
--- a/pkgs/development/libraries/vapoursynth/default.nix
+++ b/pkgs/development/libraries/vapoursynth/default.nix
@@ -1,4 +1,6 @@
-{ lib, stdenv, fetchFromGitHub, pkg-config, autoreconfHook, makeWrapper
+{ lib, stdenv, fetchFromGitHub, pkg-config, autoreconfHook
+, symlinkJoin, makeWrapper
+, vapoursynth
 , zimg, libass, python3, libiconv
 , ApplicationServices
 , ocrSupport ?  false, tesseract ? null
@@ -21,6 +23,10 @@ stdenv.mkDerivation rec {
     sha256 = "1krfdzc2x2vxv4nq9kiv1c09hgj525qn120ah91fw2ikq8ldvmx4";
   };

+  patches = [
+    ./plugin-path-environment-variable.patch
+  ];
+
   nativeBuildInputs = [ pkg-config autoreconfHook makeWrapper ];
   buildInputs = [
     zimg libass
@@ -42,6 +48,30 @@ stdenv.mkDerivation rec {
     # wrapper, what python3 version was used to build vapoursynth so
     # the right python3.sitePackages will be used there.
     inherit python3;
+
+    withPlugins = plugins:
+      let
+        pythonEnvironment = python3.buildEnv.override { extraLibs = plugins; };
+      in
+      symlinkJoin {
+        name = "${vapoursynth.name}-with-plugins";
+        paths = [ vapoursynth ] ++ plugins;
+        buildInputs = [ makeWrapper ];
+        postBuild = ''
+          for symlink in $out/bin/*; do
+            # remove the original symlink
+            original="$(realpath "$symlink")"
+            rm "$symlink"
+
+            makeWrapper "$original" "$symlink" \
+              --set VAPOURSYNTH_PLUGIN_PATH $out/lib/vapoursynth \
+              --prefix PYTHONPATH : ${pythonEnvironment}/${python3.sitePackages}
+          done
+        '';
+
+        # passthrus must be specified here, again
+        passthru = { inherit python3; };
+      };
   };

   postInstall = ''
@@ -54,7 +84,6 @@ stdenv.mkDerivation rec {
     homepage    = "http://www.vapoursynth.com/";
     license     = licenses.lgpl21;
     platforms   = platforms.x86_64;
-    maintainers = with maintainers; [ rnhmjoj tadeokondrak ];
+    maintainers = with maintainers; [ rnhmjoj sbruder tadeokondrak ];
   };
-
 }
diff --git a/pkgs/development/libraries/vapoursynth/plugin-path-environment-variable.patch b/pkgs/development/libraries/vapoursynth/plugin-path-environment-variable.patch
new file mode 100644
index<PHONE_NUMBER>0..80f98633d7f
--- /dev/null
+++ b/pkgs/development/libraries/vapoursynth/plugin-path-environment-variable.patch
@@ -0,0 +1,16 @@
+diff --git a/src/core/vscore.cpp b/src/core/vscore.cpp
+index 2d29844d..fd4cbea5 100644
+--- a/src/core/vscore.cpp
++++ b/src/core/vscore.cpp
+@@ -1351,6 +1351,11 @@ VSCore::VSCore(int threads) :
+     } // If neither exists, an empty string will do.
+ #endif
+
++    const char *pluginPath = getenv("VAPOURSYNTH_PLUGIN_PATH");
++    if (pluginPath) {
++        loadAllPluginsInPath((std::string)pluginPath, filter);
++    }
++
+     VSMap *settings = readSettings(configFile);
+     const char *error = vs_internal_vsapi.getError(settings);
+     if (error) {

I tested symlinkJoin, as before, with mpv and mvtools and everything looks good.

I tested symlinkJoin, as before, with mpv and mvtools and everything looks good.

Here's my attempt at this which I think is more reliable, because it modifies VapourSynth's shared library:
https://github.com/tadeokondrak/nixpkgs/commit/1f00195d337fc330469f8b54c5f3c64b5480b689
I also changed VSEdit to allow adding plugins without rebuilding:
https://github.com/tadeokondrak/nixpkgs/commit/d35511d82ab07cf1d5f22a62b76061c9cfc2e6f1

Here's my attempt at this which I think is more reliable, because it modifies VapourSynth's shared library:
https://github.com/tadeokondrak/nixpkgs/commit/1f00195d337fc330469f8b54c5f3c64b5480b689
I also changed VSEdit to allow adding plugins without rebuilding:
https://github.com/tadeokondrak/nixpkgs/commit/d35511d82ab07cf1d5f22a62b76061c9cfc2e6f1

Thanks @rnhmjoj for the suggestions. That looks cleaner than my workaround.
@tadeokondrak: Your attempt looks very nice, since it doesn’t rely on hacks (environment variables) like mine, thank you! It worked when I tried it with a basic setup in vsedit, however I didn’t yet have the time to test it with mpv or in more depth. Do you want to open a new PR for your implementation?

Thanks @rnhmjoj for the suggestions. That looks cleaner than my workaround.
@tadeokondrak: Your attempt looks very nice, since it doesn’t rely on hacks (environment variables) like mine, thank you! It worked when I tried it with a basic setup in vsedit, however I didn’t yet have the time to test it with mpv or in more depth. Do you want to open a new PR for your implementation?

Here's my attempt at this which I think is more reliable, because it modifies VapourSynth's shared library:

Indeed, but it's more complex: I don't think I can review this.
Anyway, since plugins path can be configured via SystemPluginDir, would it be possible to patch vapoursynth to load a custom generated vapoursynth.conf that points to $out? This would not require an environment variable or adding new code.

Here's my attempt at this which I think is more reliable, because it modifies VapourSynth's shared library:

Indeed, but it's more complex: I don't think I can review this.
Anyway, since plugins path can be configured via SystemPluginDir, would it be possible to patch vapoursynth to load a custom generated vapoursynth.conf that points to $out? This would not require an environment variable or adding new code.

I rebased onto master and incorporated @rnhmjoj’s suggestions.
I looked into @tadeokondrak’s attempt again. vspipe in the vapoursynth package isn’t wrapped, but when manually passing LD_LIBRARY_PATH, it works. With that, mpv and plain python scripts that import vapoursynth also work.
I agree that using a preload is complex, but given vapoursynth’s limited ability to load plugins from dynamic locations, it seems like any solution requires at least some new code.
It is relatively easy to patch vapoursynth to use a static configuration file in $out, but if I understand it correctly, that would require recompiling vapoursynth every time the plugins change. Since vapoursynth uses a hardcoded path to the configuration file (https://github.com/vapoursynth/vapoursynth/blob/d2f6cb0294e725605e8d86596172f3e638de7435/src/core/vscore.cpp#L1339-L1352), using that mechanism to load plugins from a configuration file outside of vapoursynth’s store path would also require adding quite a bit of new code (at least from my understanding, please correct me if I’m mistaken).

I rebased onto master and incorporated @rnhmjoj’s suggestions.

Thanks

it seems like any solution requires at least some new code.

Yes, I came to the same conclusion, unfortunately.

using that mechanism to load plugins from a configuration file outside
of vapoursynth’s store path would also require adding quite a bit of
new code (at least from my understanding, please correct me if I’m
mistaken).

No, you're right: mine wasn't a good idea afterwall :)
Both yours and @tadeokondrak's solutions look good to me, I don't have a
strong preference for either one.
On 05-02-21, Simon Bruder wrote:

I rebased onto master and incorporated @rnhmjoj’s suggestions.
I looked into @tadeokondrak’s attempt again. vspipe in the vapoursynth package isn’t wrapped, but when manually passing LD_LIBRARY_PATH, it works. With that, mpv and plain python scripts that import vapoursynth also work.
I agree that using a preload is complex, but given vapoursynth’s limited ability to load plugins from dynamic locations, it seems like any solution requires at least some new code.
It is relatively easy to patch vapoursynth to use a static configuration file in $out, but if I understand it correctly, that would require recompiling vapoursynth every time the plugins change. Since vapoursynth uses a hardcoded path to the configuration file (https://github.com/vapoursynth/vapoursynth/blob/d2f6cb0294e725605e8d86596172f3e638de7435/src/core/vscore.cpp#L1339-L1352), using that mechanism to load plugins from a configuration file outside of vapoursynth’s store path would also require adding quite a bit of new code (at least from my understanding, please correct me if I’m mistaken).
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/pull/110365#issuecomment-774302594

Sorry for the wrong pings/review requests, something went wrong while rebasing.

I swiched to @tadeokondrak’s approach, wrapped vspipe and added the needed makeWrapper options to mpv.
Also, to make propagatedBuildInputs work, I added a function that recursively gets the propagatedBuildInputs of all plugins and added the python environment as path to the environment. I’m not sure if this is the best way to do it.

I asked for feedback from someone else and they asked why the plugin loader doesn't directly use the path to the wrapper store directory. This is because that would be a circular dependency, but it made me think that we should at least link all the plugins to $out/lib/vapoursynth.
diff --git a/pkgs/development/libraries/vapoursynth/default.nix b/pkgs/development/libraries/vapoursynth/default.nix
index 2bc0d00b521..70fd297610a 100644
--- a/pkgs/development/libraries/vapoursynth/default.nix
+++ b/pkgs/development/libraries/vapoursynth/default.nix
@@ -1,5 +1,5 @@
 { lib, stdenv, fetchFromGitHub, pkg-config, autoreconfHook, makeWrapper
-, runCommandCC, runCommand, vapoursynth, writeText, patchelf
+, runCommandCC, runCommand, vapoursynth, writeText, patchelf, buildEnv
 , zimg, libass, python3, libiconv
 , ApplicationServices
 , ocrSupport ?  false, tesseract ? null
@@ -60,6 +60,12 @@ stdenv.mkDerivation rec {

       deepPlugins = plugins ++ (getRecursivePropagatedBuildInputs plugins);

+      pluginsEnv = buildEnv {
+        name = "vapoursynth-plugins-env";
+        pathsToLink = [ "/lib/vapoursynth" ];
+        paths = deepPlugins;
+      };
+
       pluginLoader = let
         source = writeText "vapoursynth-nix-plugins.c" ''
           void VSLoadPluginsNix(void (*load)(void *data, const char *path), void *data) {
@@ -102,6 +108,10 @@ stdenv.mkDerivation rec {
               --replace "${vapoursynth}" "$out"
       done

+      for binaryPlugin in ${pluginsEnv}/lib/vapoursynth/*; do
+          ln -s $binaryPlugin $out/''${binaryPlugin#"${pluginsEnv}/"}
+      done
+
       for pythonPlugin in ${pythonEnvironment}/${python3.sitePackages}/*; do
           ln -s $pythonPlugin $out/''${pythonPlugin#"${pythonEnvironment}/"}
       done

That seems like a good idea. I applied your patch.

I tested again today and everything seems in order. I would perhaps move the code to an external expression and do withPlugins = import ./plugins-interface.nix to keep the main package shorter.

Splitting the function into its own file is a good idea considering it amounts for more than half of the code. I rebased and incorporated this suggestion.

Looks good to me. @tadeokondrak?

Thanks for helping me with this PR and merging it!


zsh: Suggest --lib option as binary template now the default

r? @ehuss

r? @joshtriplett , to free assign log from ehuss

Thanks, I think Josh has been traveling.  I wouldn't put too much effort into updating the completions, since they are quite old and I intend to replace them soonish.
@bors r+

:pushpin: Commit c71bd2287ae3927df0ab9ced4e38546784fb6d36 has been approved by ehuss

:hourglass: Testing commit c71bd2287ae3927df0ab9ced4e38546784fb6d36 with merge 9634a3a4d41942d4129a9841cf7500c8436bfd23...

:sunny: Test successful - checks-travis, status-appveyor
Approved by: ehuss
Pushing 9634a3a4d41942d4129a9841cf7500c8436bfd23 to master...


w64devkit issue

hi there what i mean was
can i install pro tools  without to instal it on my system windows 10

please dont close my issue

i want a clean  drive instalation because i dont want cubase as a exe onnmy desktop pc

Please continue the discussion on #161.


nvm install gives permission denied

Operating system and version:
Ubuntu 21.04 64 bit
nvm debug output:

nvm --version: v0.38.0
$SHELL: /bin/bash
$SHLVL: 1
whoami: 'sauronnikko'
${HOME}: /home/sauronnikko
${NVM_DIR}: '${HOME}/.nvm'
${PATH}: ${HOME}/apps/google-cloud-sdk-340.0.0-linux-x86_64/google-cloud-sdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin
$PREFIX: ''
${NPM_CONFIG_PREFIX}: ''
$NVM_NODEJS_ORG_MIRROR: ''
$NVM_IOJS_ORG_MIRROR: ''
shell version: 'GNU bash, version 5.1.4(1)-release (x86_64-pc-linux-gnu)'
uname -a: 'Linux 5.11.0-17-generic #18-Ubuntu SMP Thu May 6 20:10:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux'
checksum binary: 'sha256sum'
OS version: Ubuntu 21.04
curl: /snap/bin/curl, curl 7.76.1 (x86_64-pc-linux-gnu) libcurl/7.76.1 OpenSSL/1.1.1f zlib/1.2.11 brotli/1.0.7 zstd/1.4.4 libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.2.0) libssh/0.9.3/openssl/zlib nghttp2/1.40.0 librtmp/2.3 libgsasl/1.8.1
wget: /usr/bin/wget, GNU Wget 1.21 built on linux-gnu.
git: /usr/bin/git, git version 2.30.2
grep: /usr/bin/grep (grep --color=auto), grep (GNU grep) 3.6
awk: /usr/bin/awk, awk: not an option: --version
sed: /usr/bin/sed, sed (GNU sed) 4.7
cut: /usr/bin/cut, cut (GNU coreutils) 8.32
basename: /usr/bin/basename, basename (GNU coreutils) 8.32
rm: /usr/bin/rm, rm (GNU coreutils) 8.32
mkdir: /usr/bin/mkdir, mkdir (GNU coreutils) 8.32
xargs: /usr/bin/xargs, xargs (GNU findutils) 4.8.0
nvm current: none
which node:
which iojs:
which npm:
npm config get prefix: Command 'npm' not found, but can be installed with:
sudo apt install npm
npm root -g: Command 'npm' not found, but can be installed with:
sudo apt install npm

nvm ls output:

            N/A
iojs -> N/A (default)
node -> stable (-> N/A) (default)
unstable -> N/A (default)
lts/* -> lts/fermium (-> N/A)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.17.1 (-> N/A)
lts/carbon -> v8.17.0 (-> N/A)
lts/dubnium -> v10.24.1 (-> N/A)
lts/erbium -> v12.22.1 (-> N/A)
lts/fermium -> v14.17.0 (-> N/A)

How did you install nvm?

ran curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash
What steps did you perform?
After installing nvm, I closed the terminal, then reopened it and ran nvm install 12.16.3
What happened?
Got this output:
Downloading and installing node v12.16.3...
Downloading https://nodejs.org/dist/v12.16.3/node-v12.16.3-linux-x64.tar.xz...
Warning: Failed to create the file
Warning: /home/sauronnikko/.nvm/.cache/bin/node-v12.16.3-linux-x64/node-v12.16.
Warning: 3-linux-x64.tar.xz: Permission denied
curl: (23) Failure writing output to destination

Binary download from https://nodejs.org/dist/v12.16.3/node-v12.16.3-linux-x64.tar.xz failed, trying source.
grep: /home/sauronnikko/.nvm/.cache/bin/node-v12.16.3-linux-x64/node-v12.16.3-linux-x64.tar.xz: No such file or directory
Provided file to checksum does not exist.
Binary download failed, trying source.
Downloading https://nodejs.org/dist/v12.16.3/node-v12.16.3.tar.xz...
Warning: Failed to create the file
Warning: /home/sauronnikko/.nvm/.cache/src/node-v12.16.3/node-v12.16.3.tar.xz:
Warning: Permission denied
curl: (23) Failure writing output to destination

Binary download from https://nodejs.org/dist/v12.16.3/node-v12.16.3.tar.xz failed, trying source.
grep: /home/sauronnikko/.nvm/.cache/src/node-v12.16.3/node-v12.16.3.tar.xz: No such file or directory
Provided file to checksum does not exist.

What did you expect to happen?
Expected Node version 12.16.3 to install
Is there anything in any of your profile files that modifies the PATH?

No

Warning: Failed to create the file
Warning: /home/sauronnikko/.nvm/.cache/src/node-v12.16.3/node-v12.16.3.tar.xz:
Warning: Permission denied
curl: (23) Failure writing output to destination

Do you have full ownership on $HOME?
If yes, then it might be the issue described in #2504, which is specific to snap's curl: https://bugs.launchpad.net/snapcraft/+bug/1928185

Given the presence of "snap" in your PATH, I'm going to assume that's what the issue is, and close it as a duplicate of #2504. Happy to reopen if that's not the case.


Lint Script

Adding a script in case the linting does not run on save

Closing this, superseded by #45


OSMC: ERROR: Can't find source for this kernel

`osmc@osmc:~$ rpi-source
*** gcc version check: OK
ERROR:
Can't find a source for this kernel
Help: https://github.com/notro/rpi-source/wiki
osmc@osmc:~$
`
I just installed the gcc and did the sudo wget https://raw.githubusercontent.com/notro/rpi-source/master/rpi-source -O /usr/bin/rpi-source && sudo chmod +x /usr/bin/rpi-source && /usr/bin/rpi-source -q --tag-update install thing.
It doesn't matter if I skip gcc nor I run --verbose it's always the same error. I'm using OSMC in my raspberry pi. How can I fix this?

rpi-source is for kernels installed with rpi-update.


Michinoku Shinrokuden, MediaCreatorUsername IRIDes, Images disappeared.

This issue may be the same problem as #801.  After the Yahoo image problem was fixed, some Michinoku Shinrokuden images (ID 891338 ~ 913881) are not appearing in the JDA site.

Thank you!


ShiftedFrameExtractor - There will be problem when Error.build is overridden

https://github.com/inf3rno/o3/issues/79

I will move this to the constructor and to the clone method before calling build and init. So in theory nothing will interfere with it.


Can this use partials as in html partials

I am tryign to find something like assemble for grunt that can insert html files where double braces occur in my build like this
{{header.html}} then in the build that will use the html in there.
Can this do that or is this for some other purpose. I tried to understand the Lodash object but it didnt seem to do this.
Thanks

Use Stack Overflow for support questions. This supports whatever the Lodash templating supports.

For some reason I cannot post in SO. Its so very annoying and there is noone you can talk to to ask why it isn't working its almost like trying to talk to google.
I already said that I didn't understand the Lodash documentation well it looks like it doesn't.
For those getting here and need help I can offer the lib 'gulp-file-include' that seems to do enough for me for now.
Let me close by saying that I am very grateful to your ever growing contribution to the OS world sindre.

Lodash doesn't support includes. You could read in the template file using fs.readFileSync and supply it as data, or better yet, use something that does support includes like https://github.com/sindresorhus/gulp-nunjucks ;)

Thank you.


Use with FFImageLoading

Hey James,
I was curious if you've ever used your plugin with FFImageLoading. I know FFImageLoading has a circle transformation, but I much prefer the way your plugin works with regard to drawing an image inside a circle as opposed to cropping the image to a circle. If not, do you have a suggestion of where I might start?

Since it is a customer render and theirs is a custom renderer you can't today unless you bring the source code into your app and inherit from their image type.
I am thinking of moving this to be all attached properties in the future though so we will see :)


connection timed out sending e-mail

Gogs crashed when sending confirmation email, using v0.6.1 @ 2015-3-26, MySQL, Git 1.9.1, Ubuntu 14.04.
Error log:
[asm_amd64.s:2232 goexit()] [E] Async sent email 0 succeed, not send emails<EMAIL_ADDRESS>info: UID: 1, send activate email to<EMAIL_ADDRESS>err: dial tcp <IP_ADDRESS>:587: connection timed out

Mail Configuration:
[mailer]
ENABLED = true
HOST = smtp.gmail.com:587
FROM =<EMAIL_ADDRESS>// using google for business
USER =<EMAIL_ADDRESS>PASSWD = ******

Thanks your report!
But have you tried to make sure the server actually can dial up <IP_ADDRESS>:587?

Close for now but open continuing discussion.


eth-typing: 2.0.0 -> 2.1.0 and eth-utils: 1.4.1 -> 1.7.0

Motivation for this change
Update eth-utils and eth-typing packages.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

nix-review builds on macos 10.13, only failing on electrum because of another of its dependencies failing.

@GrahamcOfBorg build eth-typing eth-utils

@GrahamcOfBorg build python3.pkgs.eth-typing python3.pkgs.eth-utils


Add OpenFX OCIO plugin framework and examples

This PR includes a working OCIOColorSpace OFX plugin and a lower-level framework to support other OCIO plugins fairly simply. Each plugin creates a transform and passes it to an OCIOProcessor base class which manages the rendering on multiple threads using an OCIO::PackedImageDesc. This currently only supports the CPU renderer but could be extended to support the GPU renderer. All bit-depths are supported.
A large component of this work is on the CMake side, since it uses the OpenFX Support Library (C++ wrapper) for interacting with the C API. I initially tried to build a static lib from that source and link it into plugins, but the plugins were not loaded by hosts. The issue could have certainly been on my end, so open to ideas there. The current approach treats the support library as additional source and compiles it directly with the plugin. The Resolve OFX example seems to use the same approach (by appearances at least), but i'll need to build it to confirm.
We can add more plugins in later PRs, and the overall UX of these will no doubt be tweaked as the UX working group iterates on implementation guidelines.
Resolve:

Natron:

Signed-off-by: Michael Dolan<EMAIL_ADDRESS>

Great work @michdolan, I tested that on Resolve macOS and it worked fine.
I'm not sure where you issues of having the support layer as a static lib comes from, here it loaded just fine with that setup. Maybe I missed something though, or it's a linker behaviour difference between platforms. On other note, I had to use a custom RPATH for the plugin pointing to the absolute installation library folder, for better or worse but it work when you copy the plugin to Resolve expected folder and install OCIO to a non standard location...
A bit curious about the GPU implementation, on Resolve at least, the OpenGL processing suite doesn't seems to be supported which probably means per frame upload / download of texture ? OpenCL / Metal / CUDA only seems officially supported. Also didn't really understood if that is a Resolve issue, but the multithreading seems quite disappointing.

@remia I think the OpenCL/CUDA/Metal support is specific to Resolve. I'm guessing they are maintaining their own version of: https://github.com/ofxa/openfx/blob/master/Support/Plugins/include/ofxsProcessing.H .
I agree on the multithreading performance. It's possible it could also be related to my choice of flags for the openfx interface.

I added the OpenFX Support Library source, modified to fix compiler errors and warnings for C++ 11, 14, and 17. I would like to contribute these changes back to openfx, but in the meantime I am proposing we house the modified code here, since it is BSD licensed, like OCIO. We could also add a OpenGL or DirectX render extension like Resolve did with the other GPU APIs...
@jmertic for license check to make sure this is ok for now.

New OCIODisplay node:

Updated OCIOColorSpace and added warning for scene/display color space conversion:

This work intended to propose solution for #1369

Added context override params like Nuke's "Context" tab. I took a slightly different approach and am creating a dedicated param per environment variable declared in the OCIO config "environment" section (vs. having a preset number of generic key/value pair params). Open to discussion as to whether this is the right approach. OFX handles this well in my tests of loading a different config in which the generated context params would differ due to different environment variables being declared (and thus dropping previously stored values). Tooltips provide a declared default (as pictured here).

Hmmm... interesting! I really like this approach, and it rewards declaring the "environment" value; however, I'd still like to be able to set (and persist) values and expressions for Context variables that might not exist in the config; or for configs that don't define an environment section.
For example, we have "Dynamic ColorSpace" and "Dynamic Display" nodes whose first two context (key, value) pairs are hard-coded with nuke tcl expressions to parse $SHOT and $SEQUENCE values from regex matching "input/filename" metadata. I'd like to assign / override those keys and values independently of the config. I don't know if Resolve has an equivalent concept (but I'd be really curious to find out).
Of course, maybe there are better places for overriding those context variables defaults than in this node's interface...
Can OFX nodes inherit arbitrary metadata from each other? Imagine an OCIO Context node for tracking and overriding the environment on a scope local to downstream nodes; and all other nodes can use the proposed node-level, dynamic per-config overrides.
(And the idea of OCIO-node metadata would extend nicely for things like tracking image state / encoding, which could inform the default modes of Grading and ExposureContrast nodes... all sorts of stuff. just a thought)
Thanks Michael, I can't tell you how awesome these OFX nodes are.

Thanks for the excellent feedback @zachlewis ! Here's the other approach we could do, more like what Nuke is doing. Good point on the use case you described. I agree that seems like it may be the better way to go.
As for externalizing the context overrides to its own node (and passing via metadata), I agree that would be very DAG/node graph friendly in terms of workflow. I'll do some investigation to see if openfx provides that level of interaction with the host application. I know it could be done in Nuke by writing a custom Op type, but I'm not sure how aware openfx plugins are of the surrounding graph implementation.

Added button to swap color spaces.
Also, I did more testing on the dynamic context variable interface (as discussed in UX WG meeting) and the persistence of the parameter values through config changes with different declared environment variables. In Resolve the values are preserved, but not in Natron, so it seems implementation dependent. As a solution I can add a hidden param to preserve all context variables and populate them as the dynamic params are available.

Context overrides are now preserved through config changes with the dynamic context param UX. A secret param serializes all context overrides when any context param is modified. I have tested this in Resolve and Natron and both re functioning.

The last thing I'm going to do in this PR is support preservation of choice param values even when not present in the config. This will result in an error on loading a scene with a different OCIO config as opposed to resetting params silently.

Thank you Michael -- preservation of choice param values even when not present in the config is exactly what I was hoping for. You're the best.

I found another issue.  When I use a config that has a different set of views for each display, I'm noticing that when I change the display, the view menu doesn't update with the appropriate new values.  It still has the old values.  Does it update correctly in the other hosts you tested in?

Thanks for the feedback @doug-walker ! I'll work on refinements over the next couple weeks.

When I use a config that has a different set of views for each display, I'm noticing that when I change the display, the view menu doesn't update with the appropriate new values. It still has the old values. Does it update correctly in the other hosts you tested in?

I just tested this again in Resolve, and the views do change per display. The change is triggered by the OFX plugin changedParam callback. Perhaps Flame is not emitting that?

Flame is definitely calling the changedParam callback because I'm getting the warning dialog box for the ColorSpace plug-in.  But I'll explore more why the menu is not being updated with the new values.  Thanks Michael!

@michdolan & @doug-walker . Looking at the comments that's tricky to see if the pull request is ready or not. So, what is the status of the pull request?

@hodoulp, I think Michael said he will be making another commit after his vacation.

I just pushed commits which respond to @doug-walker 's feedback, and also adds support for preserving (and warning about) missing color spaces, displays, and views. The missing values are added to the menus, with a "(missing)" label for hosts that support it (Resolve doesn't seem to), and the preserved values are restored when the correct OCIO config is loaded in a future session.

Other than responding to additional review comments, or fixing CI issues that may occur, this PR is complete. I plan to follow up with additional plugins and improvements in later PRs.

@jmertic EasyCLA is remaining at Expected - Waiting for status to be reported for this PR. Any idea as to what the issue might be? This PR did exist prior to the CLA switch. Thanks!

I'm going to close and reopen this PR to try and trigger the EasyCLA check.

/easycla

/easycla

/easycla

Note that I added info on OFX_PLUGIN_PATH to the OCIO docs, which should point to the OFX bundle, along with the shared OCIO lib being on PATH to use these. That's how I test the plugins on Windows.


HL2RP character customization ERROR for LUA

[ERROR] gamemodes/cwhl2rp/schema/derma/cl_character.lua:762: attempt to index field 'startButton' (a nil value)

Init - gamemodes/cwhl2rp/schema/derma/cl_character.lua:762
Create - lua/includes/extensions/client/panel/scriptedpanels.lua:153
3. RefreshPanelList - gamemodes/clockwork/framework/libraries/cl_character.lua:281
4. Callback - gamemodes/cwhl2rp/schema/derma/cl_character.lua:122
5. Callback - gamemodes/cwhl2rp/schema/derma/cl_character.lua:329
6. Func - gamemodes/cwhl2rp/schema/derma/cl_frame.lua:27
7. Run - lua/derma/derma_animation.lua:31
8. AThink - gamemodes/cwhl2rp/schema/derma/cl_frame.lua:81
9. unknown - gamemodes/cwhl2rp/schema/derma/cl_frame.lua:86

It seems like you tried to make an edit to the HL2 RP schema. This isn't recommended because errors like this can pop up. Try reinstalling fresh unedited copies of Clockwork and HL2 RP onto your server.


Upload key package before publishing identity updates

TL;DR
Implements parts of https://github.com/xmtp/xmtp-node-go/issues/399

Uses UploadKeyPackage instead of RegisterInstallation so we can deprecate the register installation endpoint
Uploads key package before publishing the identity updates for new installations. This ensures that any installation seen in an identity update must have a matching key package.
No longer checks the lifetime of key packages when verifying

AI Assisted Summary
What changed?

Removed expiration checks and set expiration to 0 in MLS validation service
Updated the client registration process to register identity before applying signature request
Renamed register_installation to upload_key_package in API client calls
Removed lifetime validity checks from key package verification

Merge activity

Aug 14, 5:32 PM PDT: @neekolas started a stack merge that includes this pull request via Graphite.


Support hopping event loops with EventLoopFuture

Motivation:
A somewhat common requirement when working with chains of futures
is needing to hop from one event loop to another. This is particularly
common when relying on the fact that EventLoopFuture will synchronize
with the event loop that created it: you often want to rely on that
implicit locking, rather than use Dispatch or Lock to achieve the
same effect.
While doing this hop requires relatively little code, it's not
necessarily totally apparent to new users how they would do it.
Additionally, the most naive implementation incurs the overhead of
allocations and reference counting in cases where it's not necessary
(e.g. when you have only one event loop, or when both work items are
being scheduled on the same event loop).
For this reason, we should have a nice concise way for a user to
request this behaviour and get a relatively performant implementation
of the behaviour.
Modifications:
Added EventLoopFuture.on(eventLoop:).
Changed AcceptHandler to use the new method rather than its (slower)
alternative.
Result:
Users will have an easier time working with EventLoopFutures.

Ok, renamed, and also updated and to use this function.

@Lukasa thanks! Shipped :)


Further details

Hi, will there be a paper for this or other documents describing all the changes made to the original SAM architecture?

@ziqi-jin
Also, I looked into the code and found the following in extend_sam/extend_sam.py.
def forward(self, img):
        x = self.img_adapter(img)
        points = None
        boxes = None
        masks = None

        sparse_embeddings, dense_embeddings = self.prompt_adapter(
            points=points,
            boxes=boxes,
            masks=masks,
        )

Does this mean that finetune-anything does not by default use any prompts? If so, would it be viable to implement automatic box generation for each class? And would it be beneficial to the algorithm performance


Need help with design

I'm unable to find solution any where hence posting here.
I want to make highlighted portion smooth, radius should be 120.
My design is combination of Elliptic Arc, Arc, and line. I want all to be seamless smooth.  I've used hard coded values for demonstration purposes.
code
var makerjs = require('makerjs');

function demo(startAngle, endAngle, radiusX, radiusY) {

  var example = new makerjs.models.EllipticArc(startAngle, endAngle, radiusX, radiusY);

  var arc = new makerjs.paths.Arc([35.00000002352587,-69.28203202838824], [20, -89], 120, false, false);

  var line1 = new makerjs.paths.Line([20,-89.00000002838823], [18.00000002352587,-109.28203202838823]);

  makerjs.model.addPath(example, arc, 'arc');
  makerjs.model.addPath(example, line1, 'line');

  var fillet = makerjs.chain.fillet(
     makerjs.model.findSingleChain(example),
     120
   );

//  var fillet1 = new makerjs.path.fillet(arc, line1, 20);

    this.models = {
     example: example,
      fillet: fillet
    };

}

demo.metaParameters = [
  { title: "startAngle", type: "range", min: 0, max: 90, value: 300 },
  { title: "endAngle", type: "range", min: 90, max: 360, value: 240 },
  { title: "radiusX", type: "range", min: 1, max: 50, value: 70 },
  { title: "radiusY", type: "range", min: 1, max: 50, value: 80 }
];

module.exports = demo;

Yup, facing same issue here as well ,
I also didn't find any way to do it

You may want to try your drawing as circles first, then distort it  to get it as elliptical.


US625210: Add FIPS support

https://internal.almoctane.com/ui/entity-navigation?p=131002/6001&entityType=work_item&id=625210

A developer build has not yet been created for this branch. Click here to go ahead and create the build...

I'll approve but I assume you're intending to close this without merging?

Yes, will not merge


xcb-proto dependency

It's in the apt-get code snipped at https://github.com/jaagr/polybar#dependencies but not in the list proper.

It's been added to the list


Cleans after images for sidecar windows images

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


Enhanced testing harness using BATS (resolves #10)

I expect this build to fail until #42 is merged.


go mod tidy to make nightly happy

to fix:
/home/runner/work/operator/operator/bin/ginkgo  --randomize-all --poll-progress-after=120s --poll-progress-interval=120s -timeout 14400s --no-color -nodes=1 tests/e2e
Failed to compile e2e:
go: updates to go.mod needed; to update it:
go mod tidy

Thanks. FYI, now that this is merged, I've just triggered a manual run of the Nightly Workflow: https://github.com/janus-idp/operator/actions/runs/8519266127

Thanks. FYI, now that this is merged, I've just triggered a manual run of the Nightly Workflow: janus-idp/operator/actions/runs/8519266127

🤔 Surprisingly, it does not seem to fix the nightly job: https://github.com/janus-idp/operator/actions/runs/8519266127/job/23332951137


Additional local storage tests

When calling to_json on LocalStorage transformations, I saw that it did not add the chosen array to the "array" field. I first thought it was a bug and wrote some tests to check but then realized this is by intention when no "array" was provided. Anyway, I think it's good to add the additional tests I wrote

I think, I just found one bug


Issues when transpiling typeScript into javaScript

Hello,
I am using vueuse/head in a vite-vue3 project where I mainly use composition API .
Everything works until I transpile the code into javascript.
The static website does not load properly and I get the following error:
Uncaught ReferenceError: can't access lexical declaration 'qg' before initialization.
The error appear when I hover the underlined word in the picture below:
https://tinypic.host/i/screenshot-from-2022-12-12-06-00-06.RfFfp
Code inside main.ts file:
import { createHead } from "@vueuse/head"

const app = createApp(App)
app.use(createHead())

Code inside the setup function inside component:
import { useHead } from "@vueuse/head";

useHead({
    title: 'title'
})

Am I doing anything wrong?
Thank you in advance,
Alepefe.

Hey @Alepefe
What you have looks correct. Would it be possible to provide a reproduction?

Hello @harlan-zw,
I found where the issue comes from.
The rollupOptions inside the vite.config.ts build params:
    build: {
      chunkSizeWarningLimit:1500,
      rollupOptions: {
        output: {
          manualChunks(id) {
            if (id.includes('node_modules')) {
              // return id.toString().split('node_modules/')[1].split('/')[0].toString();

              if(id.includes('@vue')){
                return 'vue'

              } else if(id.includes('echarts')) {
                return 'echarts'

              } else if(id.includes('elastic')) {
                return 'elastic'
              }

              return 'vendor'
            }
          }
        }
      },
      minify: 'esbuild',
    }

I'm guessing you mean useHead, can you share that code as well?

@harlan-zw
Yes, I meant in some components, I have to use the useHead() function inside onActivated lifecycle function in order to get the expected behavior.
setup(props: any){
    onActivated(()=> {
        useMeta({title: 'title'})
    })
}

instead of
setup(props: any){
useMeta({title: 'title'})
}
Browse history:
main page (first load) -> contact page (first load) -> main page (cached page so the contact page's meta remains here).
I still don't know why this happens but I suspect it is something related with  directives or .
I would not consider this a blocking issue as it does not hamper progress on my project.
However, this information might be helpful for you.
I will publish further news when I come back to the "meta management" part of my project.

@harlan-zw IS this still an issue? I was thinking about using this package in my Vue project?

Nuxt uses this library with no issues, I think it depends on your own configuration.


Middleware should render with URL parameters not just the path

Problem is at https://github.com/canjs/can-ssr/blob/master/lib/middleware.js#L27. We want to deparam all query parameters as well.

Ah, good catch.


Missing app.UseAuthentication()?

I must have done something differently because someone would have raised a concern before this, but I could not get _httpContextAccessor.HttpContext.User?.Claims?.FirstOrDefault(x => x.Type == ClaimTypes.NameIdentifier)?.Value; in CurrentUserAccessor to return a value. In fact, User.Claims was always empty.
I fixed the problem by adding app.UseAuthentication(); above app.UseMvc(); in Startup.cs, but I thought I'd mention this in case I did something wrong. How are others getting the claims to appear without this line?

Fixed.  Didn't notice as I wasn't using that!


Print test statistics one by one to a stream instead of generating a big string

Fixes #18
I also moved ICastable.java to the base package. Maybe we should have a "utilities" package.

I vote for a util package.
There's one test failure. Can you fix?

weird, on my machine the stylecheck passed...


Development hub

Context:
The development section in the documentation needs a face-lift. There are several incoming additions as well as changes to the existing guides and, at the moment, most of them are combined into a single page, making the "Development" section a bit unorganised and unwieldy.
Description of the Change:
This change will create a "Development guide" landing page under the "Development" section in the TOC, where the reader can be redirected to separate guides confined to sub-pages. The "Development" section will now have 4 different pages:
Development
-----------
Development guide
Building a plugins
Contributing templates
Release notes

and the "Development guide" will have 6 card-style links to the following sub-pages:
Installation
Software tests
Documentation
Submitting a pull request
Best practices
Architectural overview

"Best practices" and "Architectural overview" only have a title at the top and are otherwise empty.
This is the rendered "Development guide" page:

Benefits:
It will be much easier for a developer/contributor to find information regarding how to contribute to the PennyLane codebase and/or documentation. Everything is much more organised, making it clearer and cleaner than before.
Possible Drawbacks:
There are now two empty sub-pages ("Best practices" and "Architectural overview") that would need to be filled as soon as possible.
Related GitHub Issues:
N/A

Looks good to me! :100:  Thanks for addressing my comments :blush:


test: Add variable control test

Describe your proposed changes here.

[ ] CHANGELOG.md updated with a link to the PR (not the Issue)
[ ] Well-formatted commit messages
[ ] Rebased/mergeable
[ ] Tests pass
[ ] http/swagger.yml updated (if modified Go structs or API)
[ ] Documentation updated or issue created (provide link to issue/pr)
[ ] Signed CLA (if not already signed)

🤔 I'd love a little more context on this PR. Is there an issue it's attached to? Providing a snapshot of the functionality its testing could also be helpful in identifying what this test is testing


Patch Test platform config files

It seems that when using vstest.console or the IDE with 15.5.x, the QTAgent which is getting used to run test is getting picked from Common7\IDE\Extensions\TestPlatform. So patch config files for assembly probing.

cc @zooba


kind cluster setup

Adds k8s cluster deployment capabilities using kind clusters.

Once we're settled on the scripts I wonder if it's worth putting these scripts somewhere common repo which other repos can pull in?
But for now let's probably not do that.

With fixes for review comments, i have raised this PR - https://github.com/openebs/openebs-e2e/pull/20
Please take a look, @tiagolobocastro @rohan2794


added Turkish datasets and script

File names should be changed for consistency (see the email I sent about this). Once that's done, just open a new pull request.


Nested Lists?

I can't find any information on how I can target and style nested lists.
Sanity uses "a series of list item blocks with the same level and listItem properties will be grouped into a virtual one inside of this library." My rich text is inputted as follows

and is seen queried like this:
  "2": {
    "children": [{ }],
    "level": 1,
    "listItem": "number",
    "markDefs": [],
    "style": "normal",
    "_key": "2cc0186eb9d3",
    "_type": "block"
  },
  "3": {
    "children": [{ }],
    "level": 2,
    "listItem": "number",
    "markDefs": [],
    "style": "normal",
    "_key": "984f45cfba95",
    "_type": "block"
  },
  "4": {
    "children": [{ }],
    "level": 2,
    "listItem": "number",
    "markDefs": [],
    "style": "normal",
    "_key": "730d9b626b42",
    "_type": "block"
  }
}

But is rendered without grouping the level 2 items with the same indentation treatment?

export default function RichText({ variant = 'default', richText }) {

    let components = {
        list: {
            // Ex. 1: customizing common list types
            bullet: ({ children }) =>
{children}
,
            number: ({ children }) =>
{children}
,

            // Ex. 2: rendering custom lists
            checkmarks: ({ children }) =>
{children}
,
        },
        listItem: {
            number: ({ children }) => <Typography className='boo' paragraph={true} component='li' sx={{ color: 'red' }} >{children}</Typography>,
        },
    }

    return (
        <>
            {richText.map((block) => {
                return (
                    <PortableText
                        key={block._key}
                        value={block}
                        components={components}
                    />
                )
            })}
        </>
    )
};

How can we target the second level to style them properly? Am I misunderstanding how the grouping of levels should be operating?

To with the same doubt, got a solution?

Here is how I handled it. Keep in mind this only handles two levels since that was all I needed.
  const components: PortableTextComponents = {
    list: ({ value, children }) => {
      const { level, listItem } = value;

      if (listItem === 'bullet') {
        return
{children}
;
      }

      if (listItem === 'number') {
        if (level === 1) {
          return
{children}
;
        } else if (level === 2) {
          return
{children}
;
        }
      } else {
        // Handle other list types if needed
        return null;
      }
    }
}


Prevent popup from opening on mobile

Fixes #1308

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/319d720d6abbbc4fde2c4edc8879c7f80aff9917/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/319d720d6abbbc4fde2c4edc8879c7f80aff9917/

Thanks, @deronjohnson. LGTM.


ApyHub Document Readability (Independent Publisher)

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)
If this is your first time submitting to GitHub and you need some help, please sign up for this session.

[X] I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
[X] I attest that the connector works and I verified by deploying and testing all the operations.
[X] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
[X] I attest that I have added response schemas to my actions, unless the response schema is dynamic.
[X] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
[X] If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

[X] I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
[X] Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
[X] Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
[ ] If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

[[certify-connector]]

Hello @troystaylor,
The current version of the template is being deployed, we will take up this version, once the current version is deployed to all the stations. However, please note we have deployment freeze, the next deployment will start on 8th Jan 2024

Hello @troystaylor ,
I hope you are doing well.
Congratulations, the deployment of your connector and documentation page was already completed, We have a short survey on the connector certification process that we would like for you to complete. Your feedback is appreciated and will help us improve the program.
Thank you very much for working with us.


Allow any class in fixture YAML

When loading existing fixtures, it's possible to hit a ruby object class that is not allowed by the (new) Psych default of load_file meaning safe_load_file. In my particular case, I got an exception because my fixtures included a Time object.
This patch resolved the issue and allowed me to convert my fixtures successfully. Since we are only loading local fixture files exclusively, it should be fine to use Psych's unsafe load.
Here's the backtrace for the error I observed that was fixed by this patch:
psych-5.2.1/lib/psych/class_loader.rb:99:in `find': Tried to load unspecified class: Time (Psych::DisallowedClass)
        from psych-5.2.1/lib/psych/class_loader.rb:28:in `load'
        from psych-5.2.1/lib/psych/scalar_scanner.rb:115:in `parse_time'
        from psych-5.2.1/lib/psych/scalar_scanner.rb:59:in `tokenize'
        from psych-5.2.1/lib/psych/visitors/to_ruby.rb:65:in `deserialize'
        from psych-5.2.1/lib/psych/visitors/to_ruby.rb:129:in `visit_Psych_Nodes_Scalar'
        from psych-5.2.1/lib/psych/visitors/visitor.rb:30:in `visit'
        from psych-5.2.1/lib/psych/visitors/visitor.rb:6:in `accept'
        from psych-5.2.1/lib/psych/visitors/to_ruby.rb:35:in `accept'
        from psych-5.2.1/lib/psych/visitors/to_ruby.rb:346:in `block in revive_hash'
        from psych-5.2.1/lib/psych/visitors/to_ruby.rb:344:in `each'
        from psych-5.2.1/lib/psych/visitors/to_ruby.rb:344:in `each_slice'
        from psych-5.2.1/lib/psych/visitors/to_ruby.rb:344:in `revive_hash'
        from psych-5.2.1/lib/psych/visitors/to_ruby.rb:168:in `visit_Psych_Nodes_Mapping'
        from psych-5.2.1/lib/psych/visitors/visitor.rb:30:in `visit'
        from psych-5.2.1/lib/psych/visitors/visitor.rb:6:in `accept'
        from psych-5.2.1/lib/psych/visitors/to_ruby.rb:35:in `accept'
        from psych-5.2.1/lib/psych/visitors/to_ruby.rb:346:in `block in revive_hash'
        from psych-5.2.1/lib/psych/visitors/to_ruby.rb:344:in `each'
        from psych-5.2.1/lib/psych/visitors/to_ruby.rb:344:in `each_slice'
        from psych-5.2.1/lib/psych/visitors/to_ruby.rb:344:in `revive_hash'
        from psych-5.2.1/lib/psych/visitors/to_ruby.rb:168:in `visit_Psych_Nodes_Mapping'
        from psych-5.2.1/lib/psych/visitors/visitor.rb:30:in `visit'
        from psych-5.2.1/lib/psych/visitors/visitor.rb:6:in `accept'
        from psych-5.2.1/lib/psych/visitors/to_ruby.rb:35:in `accept'
        from psych-5.2.1/lib/psych/visitors/to_ruby.rb:319:in `visit_Psych_Nodes_Document'
        from psych-5.2.1/lib/psych/visitors/visitor.rb:30:in `visit'
        from psych-5.2.1/lib/psych/visitors/visitor.rb:6:in `accept'
        from psych-5.2.1/lib/psych/visitors/to_ruby.rb:35:in `accept'
        from psych-5.2.1/lib/psych.rb:336:in `safe_load'
        from psych-5.2.1/lib/psych.rb:371:in `load'
        from bootsnap-1.18.4/lib/bootsnap/compile_cache/yaml.rb:217:in `input_to_output'
        from bootsnap-1.18.4/lib/bootsnap/compile_cache/yaml.rb:232:in `fetch'
        from bootsnap-1.18.4/lib/bootsnap/compile_cache/yaml.rb:232:in `load_file'
        from oaken-0.7.0/lib/generators/oaken/convert/fixtures_generator.rb:78:in `block in parse'

Great point, thank you so much!


Builds py36, py37, py38

Builds and runs unit tests for python 3.6, python 3.7, python 3.8 with:

numpy 1.15 (py3.6, py 3.7)
numpy 1.16, 1.17, 1.18 with all

Temporarily removes unit tests on other repositories (CCPi-Astra, CCPi-Plugins, Tomophantom) whilst they are updated to the new python versions.

Thanks @gfardell and @paskino!  Having a built with py37+np1.15 would the most helpful since we're preparing the Savu3 release. Also if you could have a look into the build of CCPi-Reconstruction for the same configuration it'd be great.  cheers

@dkazanc my plan is to have everything (including CCPi-Reconstruction) built with these versions soon, hopefully it all goes smoothly :)


feat: hot-reloading of transform funcs

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#5  👈
#4
#3
#2
#1
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @blepabyte and the rest of your teammates on  Graphite

Merge activity

Jun 17, 4:38 AM EDT: Graphite rebased this pull request after merging its parent, because this pull request is set to merge when ready.


What is the purpose and how to use it?

[Enter feedback here]
Hi,
What is the purpose of this "tracking schema" and how to use it in Logic Apps? This article does not provide details on how to use a custom tracking.
Thanks.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d9aaf03d-d014-139d-62d1-d845e126469c
Version Independent ID: 12604c02-3faa-5d66-7ff2-582958e1dd33
Content: Custom tracking schemas for B2B messages - Azure Logic Apps
Content Source: articles/logic-apps/logic-apps-track-integration-account-custom-tracking-schema.md
Service: logic-apps
GitHub Login: @divyaswarnkar
Microsoft Alias: divswa

Thank you for your feedback! We will review and update as appropriate.

@divyaswarnkar Can you please provide insights on this.

As this thread has gone unanswered, I'm closing this thread for now.
#please-close


out of memory

hello,when I run the net,it always have this problem,"RuntimeError: CUDA out of memory",the memory of GPU is about 11171MiB,what happened?

it is ok when change batch size


Write the README.md

Currently, our README.md has only the title and some badges. We want to fill it with some information about the models we are implmenting such as Pix2Pix, UNIT, and TUNIT. I am thinkting that the structure of the README should be like pytorch-gan repository.
https://github.com/eriklindernoren/PyTorch-GAN
Please provide a good structure first such as the table of contents and outline. Everything can be filled in as we march through our goals.

hi can i be assigned this please

i have already started working on it.
i have started with the structure and i have written the the documentation for Pix2Pix and UNIT . i will write the documentation for TUNIT and make a pr when i close from work tonight

I apologize for any confusion, but this repository is designated for a university class project and will be evaluated for grading purposes. Regrettably, we are unable to accept assistance from individuals outside our designated team of 10 collaborators. Additionally, we will not be considering any pull requests from individuals who are not part of the same 10-member team. We appreciate your efforts and apologize for any misunderstanding this may have caused.


Add automatic code coverage reports to the CI

Enable codecov as other projects in open-telemetry did. This requires maintainer status.
References:

see https://github.com/open-telemetry/community/issues/1926
see https://docs.codecov.com/docs/quick-start

I don't have permssions to update codecov for this repo, an OTel organization owner is needed.

Requesting this should be a "Repository maintenance" issue in the community repository.


Correction path for icon cleartext

Icon image path is incorrect related to the location of the file

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: ufoloko sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Can we please get an accompanying issue that explains the problem, it looks fine to me in Dnn 9.3.2

Also just tried 9.4.0 nightly build and the clear icon shows. So I cannot see what the issue is supposed to be.

Given that no feedback has been received on this, and we are unable to recreate I am closing this PR for now.


interactive.history.output should focus on last cell in IW instead of first

It seems more likely that the user would want to navigate to the most recently run code.
Also, the selected cell isn't given focus, so it's not clear that it was selected if the first cell is out of the viewport.

already completed


fix(upgrade): replace instance manager count check with state check

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Problem:
Currently, the engine process can't be live migrated to a new longhorn instance manager, so there may be two IM at the same time. We have to improve our upgrade check for instance manager.
Ref: Troubleshooting: Some old instance manager pods are still running after upgrade
Solution:
Check whether new instance manager is running.
Related Issue:
https://github.com/harvester/harvester/issues/4879
Test plan:

Create a v1.2.1 Harvester cluster.
Create a VM.
Upgrade to v1.2-head with LH v1.5.3 (https://github.com/harvester/harvester/pull/5057).
Upgrade to this branch again. Instance manager check should pass without any error.

@mergify backport v1.2


Made Secant Search state-aware

added workspace to keep track of last gamma to warm start next time around. Please check

it is faster now for the opt experiment design

we should also add that the ls stops if gamma doesn't change anymore (eg when clipping)


Azure

Article is really good and knowledgeable. It cleared my few doubts. Thanks for sharing.
Ravi Kumar
https://www.mudrabank.com

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 2b83e320-c9a0-204c-dca5-b0ed60ce2470
Version Independent ID: 8862ff67-2c6e-cb8f-3f8c-2c1f51a37f68
Content: Migrate VMware VMs agentless Azure Migrate Server Migration - Azure Migrate
Content Source: articles/migrate/tutorial-migrate-vmware.md
Service: azure-migrate
GitHub Login: @rayne-wiselman
Microsoft Alias: raynew

@pantjee We really appreciate your feedback. Thanks to our document author @rayne-wiselman and team.

@pantjee Thanks again for your feedback. At this point it appears that there's no further edits or updates needed to the documentation. We will go ahead and close this issue, however if you have any further queries please tag us in your reply and will be happy to reopen the thread and continue the conversation. Thank you


🐛 More better Job cleaning

Summary
This PR makes the cleaning of Job objects more extensive. As reported in #1936 , in my testing it got the Job objects to the WEC but also received error messages in the ManifestWorkStatus.
Related issue(s)
This is intended to address #1936 but is not entirely satisfactory (yet).

/approve

Note that this will not fully solve the problem, see the end of https://github.com/kubestellar/kubestellar/issues/1936#issuecomment-2024471573 .


support filtering a VariantCollection according to an intervals list file

For some of our analyses it would be helpful to be able to filter a VariantCollection to only those variants that fall within the intended capture targets.
Example intervals list:
[odonnt02@minerva4 ~]$ head /sc/orga/projects/ngs/resources/captures/2.3/Human_All_Exon_V5.hg19.interval_list
@HD     VN:1.4  SO:unsorted
@SQ     SN:chrM LN:16571        UR:file:/gs01/projects/ngs/resources/gatk/2.3/ucsc.hg19.parmasked.fasta M5:d2ed829b8a1628d16cbeee88e88e39eb
@SQ     SN:chr1 LN:249250621    UR:file:/gs01/projects/ngs/resources/gatk/2.3/ucsc.hg19.parmasked.fasta M5:1b22b98cdeb4a9304cb5d48026a85128
@SQ     SN:chr2 LN:243199373    UR:file:/gs01/projects/ngs/resources/gatk/2.3/ucsc.hg19.parmasked.fasta M5:a0d9851da00400dec1098a9255ac712e
@SQ     SN:chr3 LN:198022430    UR:file:/gs01/projects/ngs/resources/gatk/2.3/ucsc.hg19.parmasked.fasta M5:641e4338fa8d52a5b781bd2a2c08d3c3
@SQ     SN:chr4 LN:191154276    UR:file:/gs01/projects/ngs/resources/gatk/2.3/ucsc.hg19.parmasked.fasta M5:23dccd106897542ad87d2765d28a19a1
@SQ     SN:chr5 LN:180915260    UR:file:/gs01/projects/ngs/resources/gatk/2.3/ucsc.hg19.parmasked.fasta M5:0740173db9ffd264d728f32784845cd7
@SQ     SN:chr6 LN:171115067    UR:file:/gs01/projects/ngs/resources/gatk/2.3/ucsc.hg19.parmasked.fasta M5:1d3a93a248d92a729ee764823acbbc6b
@SQ     SN:chr7 LN:159138663    UR:file:/gs01/projects/ngs/resources/gatk/2.3/ucsc.hg19.parmasked.fasta M5:618366e953d6aaad97dbe4777c29375e
@SQ     SN:chr8 LN:146364022    UR:file:/gs01/projects/ngs/resources/gatk/2.3/ucsc.hg19.parmasked.fasta M5:96f514a9929e410c6651697bded59aec

GATK also supports a few other formats (probably not needed here though): https://www.broadinstitute.org/gatk/guide/article?id=1319

I'm also thinking about the best way to filter variants by expression level (of either genes, transcripts, or allele-specific read count). Do you think these two use cases have enough in common to suggest a filtering API?

Maybe just a VariantCollection.filter function that takes a variant -> bool callable and returns a new VariantCollection?
Then could add a new module with filter implementations, including my and your examples.


Bug fixes for GUI and Websocket connections

Fix typo in nwm_gui Docker stack app_server service volume config
Fix bug with WebSocketInterface related to extending MaaSRequest class to ModelExecRequest
Bumping Python package deps and versions
Updating version of dmod.communication package required by GUI code

Am I missing it or are all the dependency bumps OWP software? No external dependencies actually changed?

This PR probably needs to be merged prior to final review of #130.

@mattw-nws, correct.  These are internal dependency relationships between the different namespace packages.  There is just a bit of a domino effect.
As a brief aside: the package architecture probably needs to be revisited to avoid the dependency complexity we are seeing right now, but that will have to be addressed later.


Add Func for compatibility with go 1.16 pkg/flag

Fixes #335

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


New User: drchrono

Name: drchrono
Homepage url: https://www.drchrono.com/
Brand Guidelines/Licensing: acceptable versions: https://www.drchrono.com/logos/ email<EMAIL_ADDRESS>for questions
Largest Logo: https://www.drchrono.com/site_media/img/public/logos/drchrono_logo_dark_1400x399.png
Other sizes: https://www.drchrono.com/logos/

Nice, wanna open a PR for it? Here's some examples


Way of the distant hand - flurry of arrows problem

When using the flurry of blows feature, only the first attack can be done with a bow, the other is a bare hands attack, even when i choose the ranged attack option.
Monk WOTDH bug.zip

If you reselect the bow attack after the first shoot of flurry of blows it seems to be working. For some reason you do a melee attack by default. I have the same issue on my game.

first bow attack:

after flurry:

indeed it selects the bonus unarmed attack by the default. not an issue.


Add Segoe UI and MDL2 font files

Add Segoe UI and MDL2 font files into new 'Segoe fonts' folder, add CSS to import these as custom fonts and add a note about it in the README #1

I added all the font files, but only imported Segoe MDL2 and Segoe UI (not its' weight variations)

This goes against the Windows guidelines for font redistribution.

Can I embed the fonts into a game, application or device I’m developing based on the document font embedding permissions?
No, document font embedding permissions relate to embedding fonts in documents only, not embedding fonts in games, apps and devices.

Yeah we know and have discussed this already. That's one reason why we're changing the font to bitmaps, the font is included on windows anyway.

@xPuls3 see here: https://github.com/binaryfunt/electron-seamless-titlebar-tutorial/issues/1

This PR has been superseded by #16. Now the tutorial is using PNG icons created by me, so there shouldn't be any licensing issues


Update logic-apps-using-sap-connector.md

typo

@ecfan
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Improve forward computation performance.

This PR provides an (about 2x) faster implementation of word/char features extraction, avoiding issue #38.
Please inspect carefully whether this affects NER performance.

Interestingly, behaviors are slightly different.
(It takes more time to get the final results.)
Before
epoch       iteration   elapsed_time  lr          main/loss   validation/main/loss  validation/main/fscore  validation_1/main/loss  validation_1/main/fscore
1           1405        3041.2        0.01        6.92158     3.50412               0.725659                3.14457                 0.699273
2           2809        6112.06       0.01        3.43053     2.20553               0.81893                 2.02065                 0.800766
3           4213        9160.82       0.01        2.47199     1.69712               0.846075                1.58031                 0.829867
4           5617        12246.6       0.01        1.94898     1.42359               0.860148                1.37471                 0.840401
5           7021        15304.9       0.01        1.67205     1.26166               0.870616                1.26547                 0.848158
6           8425        18356.6       0.01        1.50098     1.16698               0.876962                1.22118                 0.86252
7           9829        21424.7       0.01        1.37798     1.07084               0.890352                1.12946                 0.871096
8           11233       24555.7       0.01        1.2875      1.01308               0.890857                1.13451                 0.872355

PR
epoch       iteration   elapsed_time  lr          main/loss   validation/main/loss  validation/main/fscore  validation_1/main/loss  validation_1/main/fscore
1           1405        287.247       0.01        5.5681      3.01966               0.753705                2.77255                 0.728142
2           2809        561.063       0.01        2.19734     1.96602               0.834027                1.8872                  0.814538
3           4213        836.556       0.01        1.56393     1.57977               0.85443                 1.56826                 0.82799
4           5617        1108.09       0.01        1.26244     1.36628               0.871421                1.46327                 0.840275
5           7021        1379.08       0.01        1.07251     1.2227                0.883646                1.33345                 0.853317
6           8425        1650.95       0.01        0.937123    1.13244               0.887216                1.26569                 0.861128
7           9829        1920.81       0.01        0.831516    1.07397               0.888439                1.25119                 0.861957
8           11233       2189.48       0.01        0.750047    0.992743              0.894569                1.20669                 0.865789

In BiLSTM_CRF.create_init_state, h0 and c0 are initialized wrongly, where batch_size lower the scale of GlorotUniform.
It should be fixed like following.
def create_init_state(self, shape, scale=1.0):
    s = scale * np.sqrt(6. / shape[-1])
    h_0_data = self.xp.empty(shape, dtype=self.xp.float32)
    h_0_data[...] = self.xp.random.uniform(low=-s, high=s, size=shape)
    c_0_data = self.xp.empty(shape, dtype=self.xp.float32)
    c_0_data[...] = self.xp.random.uniform(low=-s, high=s, size=shape)
    h_0 = chainer.Variable(h_0_data)
    c_0 = chainer.Variable(c_0_data)
    return h_0, c_0

However, I personally doubt the effect of uniform initialization of h_0 and c_0.
I found that original Lample's implementation uses zero initialization for them.
https://github.com/glample/tagger/blob/1c9618889fb89500cc5e70c45c27859b89d44449/nn.py#L162
https://github.com/glample/tagger/blob/1c9618889fb89500cc5e70c45c27859b89d44449/utils.py#L49
So, now BiLSTM_CRF.create_init_state should be fixed like:
def create_init_state(self, shape):
    return None, None

Even after fixing initialization, I could not reproduce your result.
My PR may harm performance ...
Please investigate it before merging the PR.
I'm sorry to bother you.

I cherry-picked the commit in this PR and merged in #57.
So I close this PR. :bow:


Remove allowBackup from manifest

Otherwise you get this error if you disable allowBackup in the application manifest:
Error:Execution failed for task ':app:processMockDebugManifest'.
> Manifest merger failed : Attribute application@allowBackup value=(false) from AndroidManifest.xml:24:9-36
  	is also present at [com.cesarferreira.colorize:library:0.2.1] AndroidManifest.xml:11:18-44 value=(true).
  	Suggestion: add 'tools:replace="android:allowBackup"' to <application> element at AndroidManifest.xml:22:5-38:19 to override.

Thanks for the PR mate, just did a release for 0.2.2


Stuck on establishing connection (mlint)

Describe the bug
Extension stuck on MATLAB:Establishing Connection
To Reproduce
Steps to reproduce the behavior:

Start VSCode and this extension

Expected behavior
Should be able to use MATLAB functionalities.
Screenshots
If applicable, add screenshots to help explain your problem.
MATLAB is stuck on this screen -

Output -> MATLAB Language Server shows error in finding mlint executable
(18:34:32) matlabls: Launching MATLAB...
[Error - 6:34:32 PM] (18:34:32) matlabls - ERROR: Error finding mlint executable in C:\Program Files\MATLAB\R2023b\bin
[Error - 6:34:32 PM] (18:34:32) matlabls - ERROR: Error finding mlint executable in C:\Program Files\MATLAB\R2023b\bin

Useful Information

VS Code Version:
Version: 1.85.1 (user setup)
Commit: 0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2
Date: 2023-12-13T09:49:37.021Z
Electron: 25.9.7
ElectronBuildId: 25551756
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19044

MATLAB Version: 2023b

Extension Version: v1.1.5

Additional context
I searched for the mlint executable and found it in ..\bin\win64
Installed MATLAB is fully functional and works standalone.

Hi @Div12345, it appears that the primary issue here is that MATLAB is attempting to launch the New Desktop experience. Unfortunately, the VS Code extension currently does not work with MATLAB when the New Desktop is enabled. The only workaround at this time is to disable the New Desktop. We are actively working to resolve this issue, and plan to release that in a future update. (This is tracked by #24)
The issue with mlint is a separate known issue where the mlint executable cannot be found on Windows. This is also something we are working to resolve in an upcoming release of the extension. I have created #83 to track this. Once the New Desktop has been disabled, you should have access to linting when MATLAB is connected - this issue only exists when MATLAB is not connected.


Improving the documentation and the tutorial for running NAMD simulations

The github.io documentation is using jekyllnow.

see Tutorial


[Aqara/K100] add OTP and notification functions

Hi team.
Please refer STSE-2969 for the details.

Because the LockAlarm capability is so new, it's not included in the generated code in the lua libraries release artifact. It will work on the hub itself, because that talks to the cloud.
However, for the sake of getting the tests to pass, I'd recommend including a copy of the capability with this PR.

Based on local testing, some of the existing tests for the lock will also need to be updated to reflect the new functionality.

@greens , Do we need capability schema yaml file just like antiLockStatus.yaml on the same location? and do we need additional code work based on it?


Garbage collection dry run

I added a new syncGarbageCollection.dry option for helm chart and deployment. With this option activated it is irrelevant how syncGarbageCollection.enabled is set, the garbage collection will run in a trace mode. Only logs appear in the console but no resources are touched.
I created a Test for this behaviour in the style of the existing tests.
Fixes #1990

ci/circleci: e2e-testing — Your tests failed on CircleCI

Unfortunately I can’t run the e2e tests because I miss the app kind. Is that an alias?

@jan-schumacher kind is Kubernetes in Docker, it should also work with minikube.

Unfortunately I can’t run the e2e tests because I miss the app kind. Is that an alias?

@jan-schumacher You will be able to run them locally if you rebase on master (thanks to #2063 ) by running make e2e
Regardless, the current error is:
Error: render error in "flux/templates/deployment.yaml": template: flux/templates/deployment.yaml:194:24: executing "flux/templates/deployment.yaml" at <.Values.syncGarbageCollection.enabled>: enabled is not a method but has arguments
Exited with code 1

Unfortunately I can’t run the e2e tests because I miss the app kind. Is that an alias?

@jan-schumacher You will be able to run them locally if you rebase on master (thanks to #2063 ) by running make e2e
Regardless, the current error is:
Error: render error in "flux/templates/deployment.yaml": template: flux/templates/deployment.yaml:194:24: executing "flux/templates/deployment.yaml" at <.Values.syncGarbageCollection.enabled>: enabled is not a method but has arguments
Exited with code 1

@hiddeco
Does that come from the change of the equation?
{{- if .Values.syncGarbageCollection.enabled and not .Values.syncGarbageCollection.dry}}
- --sync-garbage-collection={{ .Values.syncGarbageCollection.enabled }}
{{- else if .Values.syncGarbageCollection.dry }}
- --sync-garbage-collection-dry={{ .Values.syncGarbageCollection.dry }}
{{- end }}

Should I rather do it like this?
{{- if .Values.syncGarbageCollection.enabled }}
{{- if not .Values.syncGarbageCollection.dry }}
- --sync-garbage-collection={{ .Values.syncGarbageCollection.enabled }}
{{- end }}
{{- else if .Values.syncGarbageCollection.dry }}
- --sync-garbage-collection-dry={{ .Values.syncGarbageCollection.dry }}
{{- end }}

@jan-schumacher please take a look at the Helm documentation about operators https://helm.sh/docs/chart_template_guide/#operators-are-functions

@jan-schumacher please take a look at the Helm documentation about operators https://helm.sh/docs/chart_template_guide/#operators-are-functions

I see, thanks mate ;)

@jan-schumacher this is shaping up well, can you smash your commits together into one?