[boost-regex] Build error

Host Environment

OS:  Windows
Compiler: VS2019

To Reproduce
Steps to reproduce the behavior:
`./vcpkg install boost:x64-windows
Failure logs
Installing 1/120 boost-regex:x64-windows...
Building boost-regex[core]:x64-windows...
-- Using cached boostorg-regex-boost-1.79.0.tar.gz.
-- Cleaning sources at E:/vcpkg/buildtrees/boost-regex/src/ost-1.79.0-42753a2328.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source E:/vcpkg/downloads/boostorg-regex-boost-1.79.0.tar.gz
-- Using source at E:/vcpkg/buildtrees/boost-regex/src/ost-1.79.0-42753a2328.clean
-- Including E:/vcpkg/ports/boost-regex/b2-options.cmake
-- Found external ninja('1.10.2').
-- Getting CMake variables for x64-windows
-- Configuring x64-windows
-- Building x64-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:129 (message):
Command failed: E:/vcpkg/downloads/tools/cmake-3.24.0-windows/cmake-3.24.0-windows-i386/bin/cmake.exe --build . --config Debug --target install -- -v -j17
Working Directory: E:/vcpkg/buildtrees/boost-regex/x64-windows-dbg
See logs for more information:
E:\vcpkg\buildtrees\boost-regex\install-x64-windows-dbg-out.log
Call Stack (most recent call first):
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
installed/x64-windows/share/boost-build/boost-modular-build.cmake:136 (vcpkg_cmake_install)
ports/boost-regex/portfile.cmake:12 (boost_modular_build)
scripts/ports.cmake:147 (include)

Cut and paste the appropriate build messages from the console output.
Attach every failure log file mentioned in the console output.

Additional context
install-x64-windows-dbg-out.log
Add any other context about the problem here, such as what you have already tried to resolve the issue.

vcpkg version：2022.08.15 Release

You should probably try the current master head and try again. They updated boost from 1.79 to 1.80 on August 24th.

-- Using cached boostorg-regex-boost-1.79.0.tar.gz.

Now the version of boost is 1.8.0, please update vcpkg by command git pull and .\bootstrap-vcpkg.bat, then rebuild boost-regex.

Duplicated of https://github.com/microsoft/vcpkg/issues/24473

Duplicated of #24473

I doubt it, my vcpkg is up-to-date, I 've tried version 1.78, 1.19 and 1.80 and non of them worked.
I finally find that my company's anti-virus software killed b2.exe and jamxxx.exe generated by boost, as I turn it off it worked immediately. @Matc2018 hope it helps.

I tried your method but still failed.

You should probably download the current master head and try again. They updated boost from 1.79 to 1.80 on August 24th.

At first I used the current master head version of master, after failure I tried the latest release version and still got the same error.

Duplicated of #24473

I doubt it, my vcpkg is up-to-date, I 've tried version 1.78, 1.19 and 1.80 and non of them worked. I finally find that my company's anti-virus software killed b2.exe and jamxxx.exe generated by boost, as I turn it off it worked immediately. @Matc2018 hope it helps.

I followed your method and still failed.

Could you double check if D:\project\vcpkg\buildtrees\boost-regex\x64-windows-dbg\boost\standalone\msvc\19858a0c092d6daed3b7579665d68f18\msvc-setup.nup exist?
Did you install anti-virus software on your machine? Anti-virus software may remove these files, if you have anti-virus software, please close it and rebuild boost-regex with new vcpkg.

Could you double check if D:\project\vcpkg\buildtrees\boost-regex\x64-windows-dbg\boost\standalone\msvc\19858a0c092d6daed3b7579665d68f18\msvc-setup.nup exist? Did you install anti-virus software on your machine? Anti-virus software may remove these files, if you have anti-virus software, please close it and rebuild boost-regex with new vcpkg.

Thanks，I'll check and try it later.

I installed a new system environment using vmware, and the compilation passed without problems. So it's a problem with my local machine environment. It's probably related to antivirus software. Thanks again for help @Danielmelody @LilyWangLL .


⚠ ClamAV has degraded performance

In 93c156d, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 85 ms

Resolved: ClamAV performance has improved in 1e9e7be.


Double loader application when using configuration & require loader directive in same app.

My feeling is that something like this should not result in a webpack compilation error which seems to occur because the loader is applied twice, or that there should be someway to do this, such that it doesn't result in an error.
//a.js
  require('json!./foo.json')
//b.js
  require('./foo.json')

//webpack.config.js
  module.exports {
    //..
    modules : {
      loaders: [
        { test: /\.json$/, loader: "json" }
      ]
    }
  };

This has come up in our application because we still run unit tests for the moment vis-a-vis requireJS, but would like to transition new modules to commonJS syntax (no overloaded requires).
I had hoped that making the loader.test a function would allow me to do something like this:
ƒ(filename) {
  return /\.json$/.test(filename) && (! /^json\!/.test(filename))
}

But the filename argument does not include the loader directive.

Just don't use the inline require syntax for these loaders. It makes no sense to use it for loaders that can be matched to an extension. Always use the configuration for these loaders.
If you still want to use the inline require syntax, i. e. if you want to apply other loaders than in configuration, prefix a !: i. e. require('!raw!./foo.json') gives you the raw file content instead of a json object. (! prefix override the configured loaders)
Use inline require syntax for loaders that add behavior to the module: i. e. require('bundle!./foo.json') loads the module on demand in addition to returning a json object.
But you would never use the json-loader in a require. It's a loader that is always bound to the extension. Same with babel-loader, coffee-loader, html-loader, etc. Everything that has a special extension.

Thanks I guess for the moment i am trying to find a way to keep requireJS plugin syntax compat while shifting away from it in newer code.  Maybe I should rethink my approach


Add Lava Server Software

Lava is an opensource Forge + Paper implementation with our own optimizations.
Project URL: https://github.com/LavaPowered/Lava

Thanks :-)
The changes will be visible, when I restart the backend the next time.


chore: netlify-cli package install-size analysis

TL;DR
Too many big-size binary npm package in dependencies list, so netlify-cli's install size is very huge.

 That's why netlify user complained about this issue. https://github.com/netlify/cli/issues/494 [Huge increase in install size]. The core issue is netlify-cli rely on some binary npm package which size is too big. For example, @netlify/routing-local-proxy ->  . This binary file size is more than ~50mb. Replace lodash with lodash/fp or lodash.xx is not useful for reduce package install-size, beacuse it's only ~1.3mb.
Alternative solution
Rewriten netlify-cli in golang, I think these binary netlify private package is also writen in golang, and then pack it as npm package, distribute it via npmjs.org. So netlify user only need install a single platform-specific golang binary file.  I know this is  impossiable, rewriten is a huge work and stop the cli iteration.
So how about developer experience ? sorry, nobody cares.
cc @erezrokah @ehmicky

Hi @iChenLei,
Thanks for reporting this issue.
Netlify CLI has lots of features and therefore lots of dependencies. I do agree though that we should strive for a smaller package size. I also agree that 330MB is a lot.
However, the developer experience is mostly only impacted by how long it takes to run npm install netlify-cli, which is rather minor IMHO.
Also, this is not an easy fix. As your correctly pointed out with the long table, the total installation size does not come so much from specific dependencies than from the number of dependencies we use. However, most of those dependencies are providing Netlify CLI with essential features.
One potential action item i could see would be to make @netlify/plugin-edge-handlers optional, which is something we've been discussing.
Happy to hear what @erezrokah also thinks about this. :thinking:

Thanks for reply, @netlify/plugin-edge-handlers | @netlify/routing-local-proxy | @netlify/zip-it-and-ship-it | @netlify/build ,  I'm curious why these package install-size is so huge. It looks like same with esbuild(writen in golang, and compile different platform-specific binary artifacts ?).

Anyway, I'm just making a fuss .  Skip it , and continue your great work for netlify-cli. Thanks

I just need to deploy a small static site (a few kB). If would be nice to have some lite version of netlify-cli for netlify API calls like init, deploy, etc. (i.e. without dev server and others).

Switching to https://gitlab.com/lepovirta/netlify-deployer made the deploys by CI significantly faster for me.

@ehmicky Like I mentioned in #494, this is NOT only an issue of package size.
It's a fundamental security issue: you make all of the people who install your package trust 1300+ packages!

https://npm.anvaka.com/#/view/2d/netlify-cli

The security chain attacks are real, and the only solution is to reduce the packages you depend on. If you do that, then size and install time will also improve.
Also, the disk churn is serious with each netlify-cli release:
C:\Users\xmr\Desktop>npm i -g netlify-cli
npm WARN deprecated<EMAIL_ADDRESS>flatten is deprecated in favor of utility frameworks such as lodash.
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>This package has been deprecated and is no longer maintained. Please use @rollup/plugin-inject.
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future

changed 1374 packages, and audited 1375 packages in 25s

108 packages are looking for funding
  run `npm fund` for details

16 vulnerabilities (9 moderate, 7 high)

And that's with npm 8.x.
Size is one important factor. Disk churn another. Security is the most important, though.

Thanks for the additional context @XhmikosR.
I agree the security aspect is more important than the package size.
We've recently dropped oclif from the codebase which helped and are also in the process of converting the codebase to ES Modules so we can upgrade our dependencies to latest versions.
As for the npm audit results - unfortunately they are not very helpful as they contain too much noise. It's hard to know which of the reported vulnerabilities are actually exploitable in the context of the CLI.
There's more about that here and here.
We use a shrinkwrap file, which means once we publish the CLI  you'd always get the same dependencies when you install it using npm (with yarn you should use your own lock file).
That pins the dependencies users get when installing the CLI, so they don't implicitly get minor/patch updates due to semver ranges.
We also highly encourage submitting any security issue you find by following our policy.

I've submitted a few PRs the last couple weeks reducing the deps etc. I've pinpointed the root cause for the biggest size increase in netlify-cli. It comes from multiple typescript versions. See https://github.com/netlify/zip-it-and-ship-it/pull/951 for more info.
This affects quite a few packages that depend on @netlify/zip-it-and-ship-it.

So, with the above zip-it-and-ship-it change I get these results for netlify-cli:
Before: 240 MB (251.943.583 bytes)
After:  188 MB (197.329.508 bytes)
1351 -> 1328 packages

I'm sure we can get this even more down.


feat: [IDP]: Added docs on My Tasks Card

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6745645bf6d3edca9939f743--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://67457011ea29bbe890f89201--harness-developer.netlify.app


MTEB STS performance and using as feature extraction model

Hi, very interesting approach, and impressive results.

Would be interesting to see their performance v/s existing models with similar model size.
Thanks

Hi @dhruv-anand-aintech, thanks for following our work and thanks for your suggestion. We will test the STS performance on MTEB later.

congrats!


Add interactive mode

sel interactive (browsername) should launch a browser and a IPython REPl with driver bound to that browser.

Done


Trailblazer

Building the new UI

Added the trailblazer screen

Added the settings screen

Connect to the tracking services

remove the extra services for sos

remove extra issues for found in the

@Balleng-2 Lets not merge this branch in. Instead what I am doing is that I have used it as a base branch to compile the Android changes and set up proper structures in the project using design patterns like MVVM and strict SOLID principles. I would like to separate the trailblazer app into a different module before going forward with the project.


wip: wasi build routing

test if wasi build option does not interfere with current emsdk CI

initial work is able to run postgres server as wasi with plpgsql support ( dyn lib is statically linked )  and initdb ( dict_snowball is statically linked )


Incompatible version of PHP has been declared in composer.json

This issue causes a sequence of issues in which printed stack trace can't practically help all users to resolve the problem that is hidden behind the incompatible version of PHP with current Laravel version. However, .travis.yml representing right dependencies so that Travis passes all tests without any issue. Again, the fact is behind the composer.json
To be more clear take look at following echoed stack trace:
> composer install
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for intervention/image 2.5.1 -> satisfiable by intervention/image[2.5.1].
    - intervention/image 2.5.1 requires ext-fileinfo * -> the requested PHP extension fileinfo is missing from your system.
  Problem 2
    - Installation request for laravel/framework v8.5.0 -> satisfiable by laravel/framework[v8.5.0].
    - laravel/framework v8.5.0 requires php ^7.3 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 3
    - Installation request for laravel/legacy-factories v1.0.4 -> satisfiable by laravel/legacy-factories[v1.0.4].
    - laravel/legacy-factories v1.0.4 requires php ^7.3 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 4
    - Installation request for laravel/telescope v4.0.0 -> satisfiable by laravel/telescope[v4.0.0].
    - laravel/telescope v4.0.0 requires php ^7.3 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 5
    - Installation request for league/flysystem 1.1.3 -> satisfiable by league/flysystem[1.1.3].
    - league/flysystem 1.1.3 requires ext-fileinfo * -> the requested PHP extension fileinfo is missing from your system.
  Problem 6
    - Installation request for league/mime-type-detection 1.4.0 -> satisfiable by league/mime-type-detection[1.4.0].
    - league/mime-type-detection 1.4.0 requires ext-fileinfo * -> the requested PHP extension fileinfo is missing from your system.
  Problem 7
    - Installation request for ocramius/package-versions 1.9.0 -> satisfiable by ocramius/package-versions[1.9.0].
    - ocramius/package-versions 1.9.0 requires php ^7.4.0 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 8
    - Installation request for phpoffice/phpspreadsheet 1.14.1 -> satisfiable by phpoffice/phpspreadsheet[1.14.1].
    - phpoffice/phpspreadsheet 1.14.1 requires ext-fileinfo * -> the requested PHP extension fileinfo is missing from your system.
  Problem 9
    - Installation request for spatie/image-optimizer 1.2.1 -> satisfiable by spatie/image-optimizer[1.2.1].
    - spatie/image-optimizer 1.2.1 requires ext-fileinfo * -> the requested PHP extension fileinfo is missing from your system.
  Problem 10
    - Installation request for spatie/laravel-medialibrary 8.7.1 -> satisfiable by spatie/laravel-medialibrary[8.7.1].
    - spatie/laravel-medialibrary 8.7.1 requires ext-fileinfo * -> the requested PHP extension fileinfo is missing from your system.
  Problem 11
    - Installation request for spatie/laravel-query-builder 2.8.3 -> satisfiable by spatie/laravel-query-builder[2.8.3].
    - spatie/laravel-query-builder 2.8.3 requires php ^7.3 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 12
    - Installation request for mockery/mockery 1.4.2 -> satisfiable by mockery/mockery[1.4.2].
    - mockery/mockery 1.4.2 requires php ^7.3 || ^8.0 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 13
    - Installation request for nunomaduro/collision v5.0.2 -> satisfiable by nunomaduro/collision[v5.0.2].
    - nunomaduro/collision v5.0.2 requires php ^7.3 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 14
    - Installation request for phpunit/php-code-coverage 9.1.11 -> satisfiable by phpunit/php-code-coverage[9.1.11].
    - phpunit/php-code-coverage 9.1.11 requires php >=7.3 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 15
    - Installation request for phpunit/php-file-iterator 3.0.4 -> satisfiable by phpunit/php-file-iterator[3.0.4].
    - phpunit/php-file-iterator 3.0.4 requires php ^7.3 || ^8.0 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 16
    - Installation request for phpunit/php-invoker 3.1.0 -> satisfiable by phpunit/php-invoker[3.1.0].
    - phpunit/php-invoker 3.1.0 requires php ^7.3 || ^8.0 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 17
    - Installation request for phpunit/php-text-template 2.0.2 -> satisfiable by phpunit/php-text-template[2.0.2].
    - phpunit/php-text-template 2.0.2 requires php ^7.3 || ^8.0 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 18
    - Installation request for phpunit/php-timer 5.0.1 -> satisfiable by phpunit/php-timer[5.0.1].
    - phpunit/php-timer 5.0.1 requires php ^7.3 || ^8.0 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 19
    - Installation request for phpunit/phpunit 9.3.10 -> satisfiable by phpunit/phpunit[9.3.10].
    - phpunit/phpunit 9.3.10 requires php >=7.3 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 20
    - Installation request for sebastian/cli-parser 1.0.0 -> satisfiable by sebastian/cli-parser[1.0.0].
    - sebastian/cli-parser 1.0.0 requires php ^7.3 || ^8.0 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 21
    - Installation request for sebastian/code-unit 1.0.5 -> satisfiable by sebastian/code-unit[1.0.5].
    - sebastian/code-unit 1.0.5 requires php ^7.3 || ^8.0 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 22
    - Installation request for sebastian/code-unit-reverse-lookup 2.0.2 -> satisfiable by sebastian/code-unit-reverse-lookup[2.0.2].
    - sebastian/code-unit-reverse-lookup 2.0.2 requires php ^7.3 || ^8.0 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 23
    - Installation request for sebastian/comparator 4.0.3 -> satisfiable by sebastian/comparator[4.0.3].
    - sebastian/comparator 4.0.3 requires php ^7.3 || ^8.0 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 24
    - Installation request for sebastian/complexity 2.0.0 -> satisfiable by sebastian/complexity[2.0.0].
    - sebastian/complexity 2.0.0 requires php ^7.3 || ^8.0 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 25
    - Installation request for sebastian/diff 4.0.2 -> satisfiable by sebastian/diff[4.0.2].
    - sebastian/diff 4.0.2 requires php ^7.3 || ^8.0 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 26
    - Installation request for sebastian/environment 5.1.2 -> satisfiable by sebastian/environment[5.1.2].
    - sebastian/environment 5.1.2 requires php ^7.3 || ^8.0 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 27
    - Installation request for sebastian/exporter 4.0.2 -> satisfiable by sebastian/exporter[4.0.2].
    - sebastian/exporter 4.0.2 requires php ^7.3 || ^8.0 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 28
    - Installation request for sebastian/global-state 5.0.0 -> satisfiable by sebastian/global-state[5.0.0].
    - sebastian/global-state 5.0.0 requires php ^7.3 || ^8.0 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 29
    - Installation request for sebastian/lines-of-code 1.0.0 -> satisfiable by sebastian/lines-of-code[1.0.0].
    - sebastian/lines-of-code 1.0.0 requires php ^7.3 || ^8.0 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 30
    - Installation request for sebastian/object-enumerator 4.0.2 -> satisfiable by sebastian/object-enumerator[4.0.2].
    - sebastian/object-enumerator 4.0.2 requires php ^7.3 || ^8.0 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 31
    - Installation request for sebastian/object-reflector 2.0.2 -> satisfiable by sebastian/object-reflector[2.0.2].
    - sebastian/object-reflector 2.0.2 requires php ^7.3 || ^8.0 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 32
    - Installation request for sebastian/recursion-context 4.0.2 -> satisfiable by sebastian/recursion-context[4.0.2].
    - sebastian/recursion-context 4.0.2 requires php ^7.3 || ^8.0 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 33
    - Installation request for sebastian/resource-operations 3.0.2 -> satisfiable by sebastian/resource-operations[3.0.2].
    - sebastian/resource-operations 3.0.2 requires php ^7.3 || ^8.0 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 34
    - Installation request for sebastian/type 2.2.1 -> satisfiable by sebastian/type[2.2.1].
    - sebastian/type 2.2.1 requires php ^7.3 || ^8.0 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 35
    - Installation request for sebastian/version 3.0.1 -> satisfiable by sebastian/version[3.0.1].
    - sebastian/version 3.0.1 requires php ^7.3 || ^8.0 -> your PHP version (7.2.17) does not satisfy that requirement.
  Problem 36
    - laravel/framework v8.5.0 requires php ^7.3 -> your PHP version (7.2.17) does not satisfy that requirement.
    - laravel/dusk v6.6.0 requires illuminate/console ^6.0|^7.0|^8.0 -> satisfiable by laravel/framework[v8.5.0].
    - Installation request for laravel/dusk v6.6.0 -> satisfiable by laravel/dusk[v6.6.0].

  To enable extensions, verify that they are enabled in your .ini files:
    - PATH/TO/php.ini
  You can also run `php --ini` inside terminal to see which files are used by PHP in CLI mode.

As you can see it looks like a bunch of long history of migrating from Laravel 7.x to 8.x, however, the istruction is stright and easy to follow where is elaborated in Official Upgrade Instruction.
I'll make a PR ASAP.

After the merge (#227), the current composer.json represents the right dependencies as expected on Official Laravel Instruction.


alloca.h: No such file or directory

Compiling with MinGW produces the error:
alloca.h: No such file or directory
chipmunk.h:32 reads:
#ifdef _WIN32
	// For alloca().
	#include <malloc.h>
#else
	#include <alloca.h>
#endif

But it should read:
#if defined(WIN32) || defined(__WIN32) || defined(__WIN32__)
	// For alloca().
	#include <malloc.h>
#else
	#include <alloca.h>
#endif

I didn't submit a pull request since the change is small.

I can confirm this using MSYS 2 and Mingw-w64.

This is still broken.  Can I take this issue?

Using VS2015 on Windows 10 64bit I fixed this issue with:
#ifdef _WIN32 || _WIN64

Can confirm this happens with mingw-64 on Windows 10 too.
WIN32 should be _WIN32.


Can't Create MeanJS - Build failed

node version : v10.5.0
npm version : 6.1.0
yo version : 2.0.3
generator-meanjs version : 0.4.5
Error: some g++ build warning and 2 NPM error
$ npm install
make: Leaving directory '/mnt/LEARNSS/mean-stack-for-web-developers/codesnippets/node_modules/node-sass/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/mnt/LEARNSS/mean-stack-for-web-developers/codesnippets/node_modules/node-gyp/lib/build.js:258:23)
gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:237:12)
gyp ERR! System Linux 4.17.2-1-ARCH
gyp ERR! command "/usr/bin/node" "/mnt/LEARNSS/mean-stack-for-web-developers/codesnippets/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /mnt/LEARNSS/mean-stack-for-web-developers/codesnippets/node_modules/node-sass
gyp ERR! node -v v10.5.0
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
Build failed with error code: 1
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/terabyte/.npm/_logs/2018-07-03T04_36_26_473Z-debug.log

same problem for me also.

npm rebuild node-sass

@Root-Control still it is not installing

What are your current nodejs version?

1.- Make sure you are using the latest lts version (no latest with all features)
2.- don't use yeoman, its failing with meanjs scaffolding
3.- Download the last meanjs version in github repository
4.- Run again npm install

10.6.0
On Tue, 10 Jul 2018, 22:06 Root-Control<EMAIL_ADDRESS>wrote:

What are your current nodejs version?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/meanjs/mean/issues/1980#issuecomment-403887235, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AbEloRRDe6g4aVIQVNPAYo5oQGr9WCdeks5uFNf5gaJpZM4VASSS
.

Build failed even when download the repo (not yoman)... same error
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>postinstall: node scripts/build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:

it working fine on my computer.
Node version 8.9.4
npm version 6.1.0
Please try aplying before "npm cache clean --force"
Then if still failing try to download dependencies with yarn

well i figured out, i read it somewhere and they said that MEAN-JS is not compatible with node 10x because it depends on node-sass and node-sass is not compatible with node 10x atleast in Arch Linux


improve performance

@dahernan talked about a way to make this way quicker (using radix trees) -- Let's do it.

@ole108 How are you getting on with this?

@matryer  Sorry Mat but I got a bit stuck with it.
I tried first to take httptreemux (it already has got many of the nice things we want and the original from Julien Schmidt doesn't got) and cut code from there and paste it into way. Unfortunately it was quite impossible to make ends meet.
Then I forked httptreemux instead and tried to refactor it until the interface would match. But I got stuck there, too.
A month ago I started a new job and consequently don't have got much time for it now.
I suppose one would have to only look at code from other routers but shouldn't try to copy much.
I really hoped it would be much easier.

No problem Ole - it's just an interesting side problem. No real pressure to get it done.
Thanks anyway
Mat

On 18 Sep 2017, at 09:12, Ole Bulbuk<EMAIL_ADDRESS>wrote:
@matryer Sorry Mat but I got a bit stuck with it.
I tried first to take httptreemux (it already has got many of the nice things we want and the original from Julien Schmidt doesn't got) and cut code from there and paste it into way. Unfortunately it was quite impossible to make ends meet.
Then I forked httptreemux instead and tried to refactor it until the interface would match. But I got stuck there, too.
A month ago I started a new job and consequently don't have got much time for it now.
I suppose one would have to only look at code from other routers but shouldn't try to copy much.
I really hoped it would be much easier.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks for your comment.
Router performance isn’t considered an important metric in the wider
context of where it is used in real world applications, so we don’t give it
much time or attention. There is an idea to use a tree to lookup the routes
which would be faster but it’s more of an intellectual exercise rather than
an important priority.
Mat
On Sun, 14 Oct 2018 at 13:26, Alex<EMAIL_ADDRESS>wrote:

Sorry for resurrecting an old issue, but does anyone have a benchmark of
the current state of the router? How bad/good is the performance right now?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/matryer/way/issues/1#issuecomment-429622266, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAGNG-l1oUYGghMRu1QYB_qKyZR0Ruizks5uky1ogaJpZM4KPO5P
.

Yes, I totally understand that routing performance isn't the most time consuming part in APIs. I was mainly asking since you brought it up in this issue. I'm new to Go, but it would be an interesting project for me to maybe work on. I'm not 100% sure on how to benchmark routers though, so I'd have no reference point to compare my results to. :)
Also, thanks for the quick response.

Well if you fancy having a look, the idea is to build a version of this that uses a radix tree for lookups. And benchmark it to see what difference it makes. Purely academic exercise though :)

@matryer Ye, I'm already kinda done. :)
I started with this project as a base, but pretty much ended up rewriting everything. Still working on it, but so far the performance is pretty good. The only thing that appears to lower the performance is when assigning parameters to the context.
Unfortunately I don't think it would be a good idea to merge my code with this project since it's so different. I mean, it looks just like your router from a user's perspective, but the router's code is almost fully replaced with my own.
I might post it on github someday if anyone is interested.

@matryer @awulkan IMHO this is the only way.
As long as the API stays the same and the new code isn't too complex it should be fine.
I once tried to solve this issue with smaller changes but it didn't add up...

I'll post this in case you don't know yet

is someone still working on improve performance?

pinging for visibility. Is there still interest in adding a radix tree implementation to way?

@matryer ? Any interest?


Ambiguous error on Aliasing

What you expect:
Given I was using 38/50 deploys, I am able to create new deployments and alias them. I would expect that I could alias this specific deployment.
What was happening:
The alias scaling settings were set to min 1 max 10 on both zones. So when I try to alias: 38 + 20 = 58 and it throws the error.
Suggested solution
The repsonse doesn't explain the issue and it looks like there is an error in the CLI.
A better explanation of the error and/or the inclusion of the deployments you are trying to reserve would clear thing up.

As of Now 2.0, there are no instances anymore. In turn, this problem will not pop up again! 🙏


How to fix number of instances for one of the ensemble's models when using Model Analyzer?

Hello,
I'm using Model Analyzer for an ensemble that consists of 2 models: dali and ViT.
I would like to fix the parameter instance_group = 1 for dali, so that Model Analyzer does not go through the number of instances for this model.
The ViT model must remain unchanged and the parameters must be searched completely for it.
Are there ways to do this?
Thank you.

Unfortunately Model Analyzer does not currently support what you are asking for via quick search, and I can't think of any workarounds. It is possible in brute-force search, but that isn't supported for multi-model. There is a way to globally limit the instance count, but that would limit all models.
There are plans to make quick search much more configurable, but that won't be ready for a bit.


Update installation instructions to fix compilation in el9 machines

I think this can be merged as it's a pretty light change. Will do so soon unless anyone objects


v5.0.b1: Setting the output (AKSampler) to the AKManager causes a crash on iOS 14 devices when started.

We have updated the app to make use of v5.0.b1 to make it compilable on XCode 12, after some minor required changes we got it compilable (ex. AudoKit -> AKManager and required initializers).
But we do run into some issues,  for instance on iOS 14 Devices build from Xcode 11 and 12, we get the following issue when we assign AKSampler as output for the AKManager.output and start the AKManager with the following console crash details as result:
2020-07-06 13:35:18.590866+0200 X[45490:655818]  HALB_IOBufferManager_Client::GetIOBuffer: the stream index is out of range
2020-07-06 13:35:18.591072+0200 X[45490:655818]  HALB_IOBufferManager_Client::GetIOBuffer: the stream index is out of range
2020-07-06 13:35:18.602009+0200 X[45490:655818] [aqme] 255: AQDefaultDevice (1): output stream 0: null buffer
2020-07-06 13:35:18.602404+0200 X[45490:655818] [aqme] 1778: EXCEPTION thrown (-50): error != 0
2020-07-06 13:35:27.485964+0200 X[45490:655338] Initialize: Mach message timeout. Apparently deadlocked. Aborting now.
CoreSimulator 725.10 - Device: iPhone 11 Pro Max (X) - Runtime: iOS 14.0 (X) - DeviceType: iPhone 11 Pro Max

And on devices lower than iOS 14.0 the AKSampler.stop seems not to work at all. sounds are played, but can't be stopped.
I have tested it on a clean project and the output issue is still present, so it doesn't seem implementation related.
Thanks in advance.

Could you by any chance use the latest code off of the v5-develop branch? There is work happening on v5 every day and as beta software I can't support debugging off of a specific beta version. Thank you for try v5 however, and I would love to know if the probably persists in the latest versions of the tools and the beta operating systems.

Thank you for your response, @aure
I've used the develop branch of version 5 as you suggested via the guide. link

Downloading the repository
Dragging in the .xcodeproj into the app xcode project
Adding the Audiokit.frameworks to Frameworks of the target.

I succeeded to build it and I have the following findings:

The crash no longer appears on iOS 14 when the AKSampler is set as AKManager.output!
The issue of AKSampler stop is still present and causes the sound to never stop playing. AKSampler.stop(noteNumber:)

I did make sure that the playing MIDINoteNumber is the same as the one that is getting stopped.

exportAsynchronously is removed from AVAudioFile, I searched a little bit and it could be that we can use AVAssetExportSession to replace it with?

The most recent changes to AKSampler have come from @eljeff but perhaps when I merged them into v5 something went wrong. @ryanfrancesconi removed AKAudioFile which was getting unwieldy and instead we have a suite of tools inside the top level /Audio Files/ folder in the AudioKit xcodeproj, perhaps something in there like AKConverter can help?

Re: aksampler start/stop ... what are your envelope settings?
If you could print out:
.attackDuration
.holdDuration
.decayDuration
.sustainLevel
.releaseHoldDuration
.releaseDuration
That might answer some questions
I can't comment much on AK5 tho - I've barely used it.

@impmaarten You can use AKConverter to export to different formats.

@eljeff
attackDuration: 0.0
holdDuration: 0.0
decayDuration: 0.0
sustainLevel: 1.0
releaseHoldDuration: 0.0
releaseDuration: 0.8

We didn't set any of these values, besides the releaseDuration
Start playing of a note
play(noteNumber:velocity:)
Stop playing of a note
stop(noteNumber:))

Cool thanks - was just checking that your holds werent set. When I start playing with AK5 I'll see how aksampler behaves.

Noobie here on using cocoapods. How do I get at a pod of AudioKit that fixes: Failed to build module 'AudioKit' from its module interface; the compiler that produced it, 'Apple Swift version 5.2.4 (swiftlang-1<IP_ADDRESS> clang-1<IP_ADDRESS>)', may have used features that aren't supported by this compiler, 'Apple Swift version 5.3 (swiftlang-1<IP_ADDRESS> clang-1<IP_ADDRESS>)'?
Do I need to build from source and learn to link in prerelease pods?

@Francois-Laberge-Bose Easiest would be for you to use our beta 5.0.b1 pod. Instructions are here:
https://github.com/AudioKit/Specs

@megastep Forgot to respond. Thanks, the instructions were easy and it worked. Much appreciated


Fix for usage of the new csproj with targetFramework #2450

Hi it's a quick fix of the problem with dotnet pack on the new csproj when using template with type project.
It should fix #2450
The issue with TargetFrameworks is still there for now. But it's a bigger rework as for now we only return one outputpath where we should return multiple one.

thanks!


An error is reported in vite build

Describe the bug / 问题描述
vite版本：4.2
node版本16.16
运行yarn build时，
报错信息：[commonjs--resolver] Invalid pattern "/[name]-[hash].js" for "output.entryFileNames", patterns can be neither absolute nor relative paths. If you want your files to be stored in a subdirectory, write its name without a leading slash like this: subdirectory/pattern.
file<EMAIL_ADDRESS>error during build:
RollupError: Invalid pattern "/[name]-[hash].js" for "output.entryFileNames", patterns can be neither absolute nor relative paths. If you want your files to be stored in a subdirectory, write its name without a leading slash like this: subdirectory/pattern.
at error (file:///Users/Documents/project/insightarch-fe/node_modules/rollup/dist/es/shared/node-entry.js:2287:30)
at renderNamePattern (file:///Users/Documents/project/insightarch-fe/node_modules/rollup/dist/es/shared/node-entry.js:15665:16)
at Chunk.getPreliminaryFileName (file:///Users/Documents/project/insightarch-fe/node_modules/rollup/dist/es/shared/node-entry.js:15965:24)
at reserveEntryChunksInBundle (file:///Users/Documents/project/insightarch-fe/node_modules/rollup/dist/es/shared/node-entry.js:17695:19)
at renderChunks (file:///Users/Documents/project/insightarch-fe/node_modules/rollup/dist/es/shared/node-entry.js:17681:5)
at Bundle.generate (file:///Users/Documents/project/insightarch-fe/node_modules/rollup/dist/es/shared/node-entry.js:17922:19)
at async file:///Users/Documents/project/insightarch-fe/node_modules/rollup/dist/es/shared/node-entry.js:26785:27
at async catchUnfinishedHookActions (file:///Users/Documents/project/insightarch-fe/node_modules/rollup/dist/es/shared/node-entry.js:25910:16)
at async serialBundleWorkerEntry (file:///Users/Documents/project/insightarch-fe/node_modules/vite/dist/node/chunks/dep-41cf5ffd.js:42533:61)
Reproduction link / 重现链接
No response
Steps to Reproduce the Bug or Issue / 重现步骤
No response
G6 Version / G6 版本
🆕 5.x
Operating System / 操作系统
macOS
Browser / 浏览器
Chrome
Additional context / 补充说明
No response

https://g6-next.antv.antgroup.com/manual/further-reading/bundle


Article download doesn't work / ZIP file is incomplete

Hi @StudioMercury
when I download an article from the plugin I get an incomplete zip file. I can't unzip it (error message: "End-of-central-directory signature not found.  Either this file is not a zipfile, or it constitutes one disk of a multi-part archive.  In the latter case the central directory and zipfile comment will be found on the last disk(s) of this archive.") nor upload it to DPS (error message: "The content is unavailable because there was an error while unzipping the article. [IN024]" ).
The problem seems to be somewhat related to #2
Thanks a lot for sharing your plugin and helping us out with this issue!

@ju21,
We have some follow up questions:
1.) Are you using the default template?
2.) Can you please send us the .zip file that's downloaded?
Thank you,
Studio Mercury

Dear Studio Mercury Team,
attached you can find the requested .zip file. (GitHub digital-publishing-tools-for-wordpress issue #24)
Thank you and have a nice day!
Jonathan Ulrich

Am 27.10.2015 um 17:20 schrieb Studio Mercury<EMAIL_ADDRESS>@ju21 https://github.com/ju21,
We have some follow up questions:
1.) Are you using the default template?
2.) Can you please send us the .zip file that's downloaded?
Thank you,
Studio Mercury
—
Reply to this email directly or view it on GitHub https://github.com/StudioMercury/digital-publishing-tools-for-wordpress/issues/24#issuecomment-151556693.

Hi @StudioMercury
thanks for your reply.
1.) we are not using the default template but the issue occurs also when selecting it
2.) I sent you a mail with the corresponding .zip file
Thanks again and all the best!

@ju21,
The file didn't come through.
Would you be able to send the file to our e-mail address<EMAIL_ADDRESS>Thank you.

@StudioMercury FYI: I used the GitHub mail reply first and now sent it again to<EMAIL_ADDRESS>Thanks!

@ju21, we're not getting your e-mail with the file.
Would you mind putting it on Dropbox or WeTransfer and emailing us a link?
Thank you.

@StudioMercury I just sent you the dropbox link to<EMAIL_ADDRESS>... thanks!

@ju21,
please also send to<EMAIL_ADDRESS>we’re unfortunately not seeing any e-mails from you to our hello email account.
You can also paste in the link here, we’ll remove it from this thread.
thank you

On Oct 27, 2015, at 3:25 PM, ju21<EMAIL_ADDRESS>wrote:
@StudioMercury https://github.com/StudioMercury I just sent you the dropbox link to<EMAIL_ADDRESS><EMAIL_ADDRESS>... thanks!
—
Reply to this email directly or view it on GitHub https://github.com/StudioMercury/digital-publishing-tools-for-wordpress/issues/24#issuecomment-151617123.

@StudioMercury just sent it to<EMAIL_ADDRESS>just to make sure here are the links again:
with our template:
https://www.dropbox.com/s/rwdn28hmvu2bhfe/huehnersuppe-mit-gemuese-und-gabelspaghetti_article.zip?dl=0
and with the standard article template:
https://www.dropbox.com/s/9ifxvoxwk1anz4v/huehnersuppe-mit-gemuese-und-gabelspaghetti_article_template.zip?dl=0

Thank you @ju21
We got your e-mail.

We just released an update 2.0.10 with an improvement to the packaging of the article. We updated the way the template. If you look inside the article.php file you'll see we're looking for full paths (or relative paths to the server now). This is part of a larger goal to allow any template (or theme) to be used for creating an article. Relative paths are no longer relative to the article. You can manually specify relative paths in the filter (dpsfa_bundle_article). It's been committed to github but will be available via wordpress's plugin portal within the hour.

@ju21 We've released an update to the plugin that resolves a number of issues. Problems zipping an article file should be resolved in this update. Any warnings from PHP at the time of bundling were corrupting the zip, we've suppressed these and zipping article files is improved.


nested parameters keys have to be integer like?

Given this set of params, works as I'd expect:
 "service_assignment"=>
  {"0"=>
    {"id"=>"5",
     "service_id"=>"1",
     "assignment_date"=>"2015-04-28 00:00:00",
     "taken"=>"1"},
   "1"=>
    {"id"=>"",
     "service_id"=>"2",
     "assignment_date"=>"2015-04-28",
     "taken"=>"0"}

params.permit(:service_assignment => [:id, :service_id])
=> {"service_assignment"=>
  {"0"=>{"id"=>"5", "service_id"=>"1"},
   "1"=>{"id"=>"", "service_id"=>"2"}}}

This does not:
 "service_assignment"=>
  {"0-a"=>
    {"id"=>"5",
     "service_id"=>"1",
     "assignment_date"=>"2015-04-28 00:00:00",
     "taken"=>"1"},
   "1-a"=>
    {"id"=>"",
     "service_id"=>"2",
     "assignment_date"=>"2015-04-28",
     "taken"=>"0"}

params.permit(:service_assignment => [:id, :service_id])
Unpermitted parameters: 0-a, 1-a, 2-a, 3-a, 4-a, 5-a, 6-a, 7-a, 8-a, 9-a, 10-a, 11-a, 12-a, 13-a, 14-a, 15-a, 16-a, 17-a, 18-a, 19-a, 20-a, 21-a, 22-a, 23-a, 24-a, 25-a, 26-a, 27-a
Unpermitted parameters: utf8, authenticity_token, commit
=> {"service_assignment"=>{}}

Yes. This is the rails convention. If you don't want to use it you would have to permit the keys by yourself.


Show correct error message if sending a mail failed

The backend sends a message in the response if sending a an email failed for some reason. This message should be used to fill the snackbar showing the failure.
#1970 can be used to cause an error and the backend sends an appropriate message.

I would advise to expand the clients error-map.service with a new ErrorMap for backend errors in order to solve this.

By the way: @rrenkert
Is this issue about saving new email addresses, or is it about actually sending emails?
If it is the latter, please add some example(s) for how to trigger the sending of an email from the client, so that the corresponding backend action can at least be inferred.
The verbose error-text would also be appreciated.
Aimlessly digging around in the backend code to find out which error needs to be caught, does not seem like a sensible use of anyone's time.

These messages don't look so nice, let me update them first

Updated in https://github.com/OpenSlides/openslides-backend/pull/1618. Keep in mind that once https://github.com/OpenSlides/openslides-backend/pull/1502 is merged, the backend will be able to translate these errors by itself, so you don't want to put took much work into translating these, if that's also part of this issue.

the backend will be able to translate these errors by itself, so you don't want to put took much work into translating these, if that's also part of this issue.

Sounds like the http.service and the error-map.service will have to be rewritten in the future to somehow recognise pre-translated error messages.


insight web gui and apache

Hi
Could somebody explain who to use apache2 in replace of nginx? On a lot of services i'm using apache2 and move to nginx is not possible.

resolved


Upgrade to Ethers.js v6

FYI @vplasencia

Can I pick this issue and upgrade it to<EMAIL_ADDRESS>with necessary changes?

Hey @neel-ds! Yes, sure. Do you want me to assign you this issue?

Hey @vplasencia
Yes! I would like to contribute. Please assign it to me, and I will ensure that my contributions align with the project's contribution guidelines.

Hey @neel-ds. Done ✅
Thank you so much. Let us know if you have questions or need any help.

Hey @neel-ds. Done ✅
Thank you so much. Let us know if you have questions or need any help.

Hello! I have upgraded the package and changed methods or imports accordingly. But I am stuck with some response type issues in Bandada Interface file from contracts. I will try to solve it ASAP. If there is anything I will send request on Discord.

Hey @neel-ds
Great. Thank you for the update. Feel free to always ask questions.

Hello @neel-ds. How's going with the upgrade? I'm going to work on #355 and I'll potentially need the Ethers V6. Let me know if you need help!

Hello @neel-ds. How's going with the upgrade? I'm going to work on #355 and I'll potentially need the Ethers V6. Let me know if you need help!

I am stuck with errors in contracts. I solved the typechain-types issue by changing hardhat config. I tried upgrading @nomiclabs/hardhat-ethers and @typechain/ethers-v6 to latest but build fails. As ethers v6 doesn't support utils package

Hello @neel-ds, any news on this PR? Do you need any further help? Please, let us know! :)

Thanks for reaching out @0xjei, I will try to finish it asap. Connect back to you on discord.

Hello @0xjei,
I have upgraded the ethers package to v6. I did the needful but can't resolve build issue. I would appreciate your help here to review the work and provide any feedback to resolve issue. Pushed the commits in my branch. Please check out dm on Discord for more details.

Hello @0xjei,
I have upgraded the ethers package to v6. I did the needful but can't resolve build issue. I would appreciate your help here to review the work and provide any feedback to resolve issue. Pushed the commits in my branch. Please check out dm on Discord for more details.

Thank you! I will have a look now.


Possible injector-memoryleak

I've encountered a possible memoryleak with angular/cdk and angular/core. I figured this was the spot to post this issue since it has to do with the overlay, componentportal and portalinjector.
Reproduction
https://github.com/kbarendrecht/injector-loop-repro
*I tried stackblitz first, but it seems like it's not possible to use ivy there yet.
Structure

AppComponent attaches a PanelComponent to a cdk/overlay and injects HelloWorldComponent.

PanelComponent tries to render HelloWorldComponent inside a ngComponentOutlet.

Steps to reproduce:
Step 1: Run ng serve and open the browser console
Step 2: Uncomment the p tag with ngModel binding
Step 3: Observe the PanelComponent.createInjector() being triggered continuously
Expected Behavior
What behavior were you expecting to see?
The component being rendered.
Actual Behavior
What behavior did you actually see?
The component wasn't rendered.
Environment

Angular:
"@angular/animations": "~9.0.2",
"@angular/common": "~9.0.2",
"@angular/compiler": "~9.0.2",
"@angular/core": "~9.0.2",
"@angular/forms": "~9.0.2",
"@angular/platform-browser": "~9.0.2",
"@angular/platform-browser-dynamic": "~9.0.2",
"@angular/router": "~9.0.2",
CDK/Material:
"@angular/cdk": "^9.0.1",
Browser(s):
Brave - Version 1.3.115 Chromium: 80.0.3987.87 (Official Build) (64-bit)
Operating System (e.g. Windows, macOS, Ubuntu):
Windows 10 Pro 1909 - 18363.657

The problem is that you have a call to createInjector inside the view (*ngComponentOutlet="component, injector: createInjector()"). This means that any time Angular runs change detection, createInjector will run and will return a new injector which will be passed to the injector property.


[FEATURE REQ] Auto upgrade emitter version when emitter is published

Library name
Azure.Core
Please describe the feature.
Similar to how we update Packages.Data.Props each time we publish a new version of autorest.csharp we should update this file https://github.com/Azure/azure-sdk-for-net/blob/main/eng/csharp-emitter-package.json when we publish a new version of @azure-tools/cadl-csharp npm package.

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Storage:0.5844188,Azure.Core:0.080494545,Data Lake Storage Gen2:0.02907884'

@archerzz I think this was already done can you confirm / close if that is the case?

@m-nash That's true. Closing.


Forward Policy - require package

https://github.com/attachmentgenie/attachmentgenie-ufw/blob/master/manifests/init.pp#L48-53
Should this require Package['ufw']?
Otherwise I get an error on the first run:
Error: /Stage[main]/Ufw/File_line[forward policy]: Could not evaluate: No such file or directory @ rb_sysopen - /etc/default/ufw

:+1:


Fix typo

This is the wrong place, Erlang.mk packages will be removed at some point in the future, and this was copied automatically from the repository.


Removing all instances of artifact

Please complete the following checklist:

[x] I have read the contribution guidelines.

[x] I have documented all public-facing changes in the changelog.

[ ] This pull request includes code, documentation, or other content derived from external source(s). If this is the case, ensure the external source's license is compatible with scikit-bio's license. Include the license in the licenses directory and add a comment in the code giving proper attribution. Ensure any other requirements set forth by the license and/or author are satisfied.

It is your responsibility to disclose code, documentation, or other content derived from external source(s). If you have questions about whether something can be included in the project or how to give proper attribution, include those questions in your pull request and a reviewer will assist you.

[x] This pull request does not include code, documentation, or other content derived from external source(s).

Note: This document may also be helpful to see some of the things code reviewers will be verifying when reviewing your pull request.
I realized that there could be some use cases that would wrongly call qiime2 imports and attempt to create qiime2 artifacts.  All such instances have been removed.

Go for it :)
On Tue, Mar 26, 2024 at 12:29 PM Qiyun Zhu @.***> wrote:

@.**** approved this pull request.
Looks good to me. Shall we merge?
—
Reply to this email directly, view it on GitHub
https://github.com/scikit-bio/scikit-bio/pull/1995#pullrequestreview-1961047950,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA75VXMAITO3K53F6SSEAATY2GO7BAVCNFSM6AAAAABFH62HXWVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTSNRRGA2DOOJVGA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Use full Scala 3 version in crossTarget

Fixes #6415

Added the following test:
scalaVersion := "3.0.0-RC2-bin-20210328-cca5f8f-NIGHTLY"
name := "foo"
version := "1.0.0"

> compile
$ exists target/scala-3.0.0-RC2-bin-20210328-cca5f8f-NIGHTLY/classes/Foo$.class
> package
$ exists target/scala-3.0.0-RC2-bin-20210328-cca5f8f-NIGHTLY/foo_3.0.0-RC2-1.0.0.jar

@smarter Is it what you expect?

That looks fine yes.


test(e2e): refactor assertions to create, insert and validate data

Closes: #5713
Refactors:

Unify AssertCreateTestData,AssertCreateTestDataWithDatabaseName,AssertCreateTestDataInTablespace
Unify insertRecordIntoTable,insertRecordIntoTableWithDatabaseName
Unify AssertDataExpectedCount,AssertDataExpectedCountWithDatabaseName
Remove ExecCommandWithPsqlClient given that we previously removed the psqlCLient
Remove RunQueryFromPod, which is not needed anymore since now we can connect directly using port-forwarding
Convert ExecCommand usages that were connecting locally to run a query to instead use ExecQueryInInstancePod
Convert EventuallyExecCommand usages that were connecting locally to run a query to instead use EventuallyExecQueryInInstancePod
Add RunExecOverForward which allows running queries that don't return any rows via port-forwarding

Fixes:

Client should close the connection when it is done. This improves timings on switchover/failover because we rely on smartShutdown by default

E2E fixes:

Drain with PDB disabled: actually wait for the Cluster to be back
Replica Mode: synchronize secret value in the Replica Cluster before connecting
Configuration update: simplify pg_ident assertion

/test d=push tl=4


not listening not supported

im on windows 10 home 21h2 19044.1889
rdpwrap used to work for me before but today i tryed it and its not working

RDPConf screenshot, please!

I am facing the same problem. Here is the screenshot of my RDPConf.

im on windows 10 home 21h2 19044.1889
rdpwrap used to work for me before but today i tryed it and its not working

https://github.com/stascorp/rdpwrap/issues/1881#issuecomment-1157218547


Release v55.2.0<PHONE_NUMBER> 2

[ ] The purpose of this PR is explained in this or a referenced issue.
[ ] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.
[ ] MIT license headers are included in each file.

Fixes https://github.com/Azure/sdk-release-request/issues/1650
Fixes https://github.com/Azure/sdk-release-request/issues/1624
Fixes https://github.com/Azure/sdk-release-request/issues/1660
Fixes https://github.com/Azure/sdk-release-request/issues/1654
Fixes https://github.com/Azure/sdk-release-request/issues/1645


TaskPool should contain a spmc queue and more features

Currently, the std::sync::taskpool::TaskPool have fixed number of threads and does not support reject execution policy. It is simple but I think it could have more features.
In Java, the java.util.concurrent.ThreadPoolExecutor, when calling execute on the pool:

If the number of current working threads is less than CoreThreadNum, then it will spawn a new thread and execute the task;

If the number of current working threads is greater or equal to CoreThreadNum, but smaller than MaximumThreadNum:

if the queue is not full, then just put the task into the queue
if the queue is full, then spawn a new thread and execute a task

If the number of current working threads is equal to MaximumThreadNum, and the queue is full, then it will reject the task according to the RejectExecutionHandler.

Currently implementation of TaskPool uses the channel in std::sync::mpsc, which result in every working threads have to lock the mutex for getting the real tasks. If we have a "spmc" channel, which means that the Receiver could be shared across multiple threads, the TaskPool could be more efficient.

spmc primitives would quite generally be very useful. I've found myself maintaining a Vec<mpsc::Sender<T>> for callback mechanisms more than once.

It's not very hard to implement a spmc queue since mpsc and spsc queues are already exists. I hope this could be included into the std crate.

Because the sync module has already been stabilized, changes to it need to go through the RFC process, and so, threads like this belong over there: https://github.com/rust-lang/rfcs/issues/
Thanks!

@steveklabnik. I am pretty sure, this is the RFCs repo…

Uuuuuugh, sorry :(

This has since been removed from libstd, so closing.


Allow customization of metrics

This is a proof of concept for allowing applications to manage the labels applied to metrics. The application I work on (written in Go) incorporates two related but distinct CometBFT networks. Thus each node runs two CometBFT nodes within the same process. Due to how CometBFT initializes metrics, I am forced to use a different namespace for metrics for each node, which leads to unpleasantly awkward queries in Grafana.
The change I propose:

Modifies the PrometheusMetrics methods so that they do not apply labels immediately.
Adds helper With methods so that change (1) is not a burden.
Exposes metrics struct types (some are currently internal).

As a result:

Applications can add their own labels that are applied to all metrics.
My application can register the metrics once with the default namespace, instead of being forced to register with different namespaces to avoid a panic. See the example in node/metrics_test.go.
I can use more natural queries.

Here's a comparison of a query before and after:
// Returns multiple different metric names due to the wildcard
{__name__=~"cometbft_.*_consensus_num_txs"}

// All results have the same name, with different label sets (like a normal query)
cometbft_consensus_num_txs

@ebuchman :wave:


[Bug Report] Truth of Forest buff

Describe the bug
miner gets Truth of Forest buff when switching class
botanist gets the wrong buff too

That's the whole point of the feature, to give you the opposite jobs buff so you have both up.


Bundle / minify the search app

Currently, the search app exists as individual component files in assets/js/components. For more efficient delivery to the browser, we should bundle + minify this application into a single file.

Done: https://github.com/CollectionBuilder/collectionbuilder-sa_draft/pull/70


Error while server-rendering - Network request failed with status 403

I've narrowed down the issue, but still don't have a solution.
Our setup involves Cloudflare DNS (https://www.example.com) -> Heroku (https://example.herokuapp.com)
Visiting the Heroku instance directly (after modifying ROOT_URL environment variable and the graphQLendpointURL property in METEOR_SETTINGS to point to the respective heroku urls) works fine. However, visiting https://www.example.com yields the following server-side errors. There are no client errors. I suspect this might be related to CORS.
Thoughts on a workaround? This issue is slowing down website loads considerably.
2018-12-13T07:33:23.878267+00:00 app[web.1]: Error while server-rendering. date: Thu Dec 13 2018 07:33:23 GMT+0000 (UTC) url: /sample-selection
2018-12-13T07:33:23.878813+00:00 app[web.1]: { Error: Network error: Network request failed with status 403 - "Forbidden"
2018-12-13T07:33:23.878817+00:00 app[web.1]:     at new ApolloError (/app/.meteor/heroku_build/app/programs/server/npm/node_modules/apollo-client/apollo.umd.js:1981:28)
2018-12-13T07:33:23.878819+00:00 app[web.1]:     at /app/.meteor/heroku_build/app/programs/server/npm/node_modules/apollo-client/apollo.umd.js:3091:41
2018-12-13T07:33:23.878821+00:00 app[web.1]:     at /app/.meteor/heroku_build/app/programs/server/npm/node_modules/apollo-client/apollo.umd.js:3583:25
2018-12-13T07:33:23.878824+00:00 app[web.1]:     at Array.forEach (<anonymous>)
2018-12-13T07:33:23.878826+00:00 app[web.1]:     at /app/.meteor/heroku_build/app/programs/server/npm/node_modules/apollo-client/apollo.umd.js:3580:27
2018-12-13T07:33:23.878828+00:00 app[web.1]:     at Array.forEach (<anonymous>)
2018-12-13T07:33:23.878831+00:00 app[web.1]:     at QueryManager.broadcastQueries (/app/.meteor/heroku_build/app/programs/server/npm/node_modules/apollo-client/apollo.umd.js:3577:42)
2018-12-13T07:33:23.878832+00:00 app[web.1]:     at /app/.meteor/heroku_build/app/programs/server/npm/node_modules/apollo-client/apollo.umd.js:3047:31
2018-12-13T07:33:23.878835+00:00 app[web.1]:     at /app/.meteor/heroku_build/app/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40
2018-12-13T07:33:23.878837+00:00 app[web.1]:  => awaited here:
2018-12-13T07:33:23.878840+00:00 app[web.1]:     at Function.Promise.await (/app/.meteor/heroku_build/app/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)
2018-12-13T07:33:23.878842+00:00 app[web.1]:     at Object.preRender (packages/vulcan:routing/lib/server/routing.jsx:62:14)
2018-12-13T07:33:23.878844+00:00 app[web.1]:     at generateSSRData (packages/vulcan:routing/lib/server/router.jsx:53:15)
2018-12-13T07:33:23.878845+00:00 app[web.1]:     at sendSSRHtml (packages/vulcan:routing/lib/server/router.jsx:86:45)
2018-12-13T07:33:23.878847+00:00 app[web.1]:     at match (packages/vulcan:routing/lib/server/router.jsx:149:11)
2018-12-13T07:33:23.878849+00:00 app[web.1]:     at /app/.meteor/heroku_build/app/programs/server/npm/node_modules/react-router/lib/match.js:67:5
2018-12-13T07:33:23.878850+00:00 app[web.1]:     at /app/.meteor/heroku_build/app/programs/server/npm/node_modules/react-router/lib/createTransitionManager.js:108:11
2018-12-13T07:33:23.878852+00:00 app[web.1]:     at done (/app/.meteor/heroku_build/app/programs/server/npm/node_modules/react-router/lib/AsyncUtils.js:79:19)
2018-12-13T07:33:23.878854+00:00 app[web.1]:     at /app/.meteor/heroku_build/app/programs/server/npm/node_modules/react-router/lib/AsyncUtils.js:85:7
2018-12-13T07:33:23.878856+00:00 app[web.1]:     at getComponentsForRoute (/app/.meteor/heroku_build/app/programs/server/npm/node_modules/react-router/lib/getComponents.js:11:5)
2018-12-13T07:33:23.878858+00:00 app[web.1]:     at /app/.meteor/heroku_build/app/programs/server/npm/node_modules/react-router/lib/getComponents.js:35:5
2018-12-13T07:33:23.878859+00:00 app[web.1]:     at /app/.meteor/heroku_build/app/programs/server/npm/node_modules/react-router/lib/AsyncUtils.js:84:5
2018-12-13T07:33:23.878861+00:00 app[web.1]:     at Array.forEach (<anonymous>)
2018-12-13T07:33:23.878863+00:00 app[web.1]:     at mapAsync (/app/.meteor/heroku_build/app/programs/server/npm/node_modules/react-router/lib/AsyncUtils.js:83:9)
2018-12-13T07:33:23.878865+00:00 app[web.1]:     at getComponents (/app/.meteor/heroku_build/app/programs/server/npm/node_modules/react-router/lib/getComponents.js:34:28)
2018-12-13T07:33:23.878867+00:00 app[web.1]:     at finishEnterHooks (/app/.meteor/heroku_build/app/programs/server/npm/node_modules/react-router/lib/createTransitionManager.js:102:35)
2018-12-13T07:33:23.878868+00:00 app[web.1]:     at runTransitionHooks (/app/.meteor/heroku_build/app/programs/server/npm/node_modules/react-router/lib/TransitionUtils.js:79:7)
2018-12-13T07:33:23.878870+00:00 app[web.1]:     at runEnterHooks (/app/.meteor/heroku_build/app/programs/server/npm/node_modules/react-router/lib/TransitionUtils.js:112:12)
2018-12-13T07:33:23.878872+00:00 app[web.1]:     at /app/.meteor/heroku_build/app/programs/server/npm/node_modules/react-router/lib/createTransitionManager.js:95:7
2018-12-13T07:33:23.878874+00:00 app[web.1]:     at runTransitionHooks (/app/.meteor/heroku_build/app/programs/server/npm/node_modules/react-router/lib/TransitionUtils.js:79:7)
2018-12-13T07:33:23.878876+00:00 app[web.1]:     at runChangeHooks (/app/.meteor/heroku_build/app/programs/server/npm/node_modules/react-router/lib/TransitionUtils.js:136:12)
2018-12-13T07:33:23.878877+00:00 app[web.1]:     at finishMatch (/app/.meteor/heroku_build/app/programs/server/npm/node_modules/react-router/lib/createTransitionManager.js:92:5)
2018-12-13T07:33:23.878879+00:00 app[web.1]:   graphQLErrors: [],
2018-12-13T07:33:23.878881+00:00 app[web.1]:   networkError:
2018-12-13T07:33:23.878883+00:00 app[web.1]:    { Error: Network request failed with status 403 - "Forbidden"
2018-12-13T07:33:23.878885+00:00 app[web.1]:     at /app/.meteor/heroku_build/app/programs/server/npm/node_modules/apollo-client/apollo.umd.js:730:45
2018-12-13T07:33:23.878887+00:00 app[web.1]:     at /app/.meteor/heroku_build/app/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40
2018-12-13T07:33:23.878906+00:00 app[web.1]:      response:
2018-12-13T07:33:23.878909+00:00 app[web.1]:       Body {
2018-12-13T07:33:23.878912+00:00 app[web.1]:         url: 'https://www.example.com/graphql',
2018-12-13T07:33:23.878914+00:00 app[web.1]:         status: 403,
2018-12-13T07:33:23.878916+00:00 app[web.1]:         statusText: 'Forbidden',
2018-12-13T07:33:23.878918+00:00 app[web.1]:         headers: [Object],
2018-12-13T07:33:23.878919+00:00 app[web.1]:         ok: false,
2018-12-13T07:33:23.878921+00:00 app[web.1]:         body: [Object],
2018-12-13T07:33:23.878923+00:00 app[web.1]:         bodyUsed: false,
2018-12-13T07:33:23.878925+00:00 app[web.1]:         size: 0,
2018-12-13T07:33:23.878926+00:00 app[web.1]:         timeout: 0,
2018-12-13T07:33:23.878928+00:00 app[web.1]:         _raw: [],
2018-12-13T07:33:23.878929+00:00 app[web.1]:         _abort: false } },
2018-12-13T07:33:23.878938+00:00 app[web.1]:   message: 'Network error: Network request failed with status 403 - "Forbidden"',
2018-12-13T07:33:23.878940+00:00 app[web.1]:   extraInfo: undefined,
2018-12-13T07:33:23.878942+00:00 app[web.1]:   queryErrors: [ [Circular] ] }

Figured it out! Turns out it was an SSL issue! Isolated by running through all the CF setup steps on a test app, but it would have been nice to have a more helpful error message.

I think I just ran into the same issue actually. I was getting 403 errors for all internal GraphQL requests (those going from Meteor to the GraphQL endpoint during SSR). To fix it I did the following:

Put CloudFlare in "DNS-only" mode (i.e. disable every CloudFlare feature, basically).
Set forceSSL to true in mup.js
Use this technique for redirecting www to non-www.

If you found a way to make it work with all CloudFlare features enabled though I'd be very interested.
And yeah the error messages are not very helpful… hopefully this issue goes away altogether with Apollo 2, since there shouldn't be a separate request anymore.

Yep, I meant to post an update. I also had to put Cloudflare into "DNS-only" mode, which was quite sad.

Let's keep this open until we either find the "real" fix with full Cloudflare features; or we update to Apollo 2 then.

@SachaG was just thinking about this... what's special about SSR in CDN mode? IIRC, queries without SSR were going through just fine.

With the current version of Apollo, when the server needs to access your API data for the SSR process, it makes a query to the GraphQL endpoint with a new request. My understanding is that maybe Cloudflare messes up the process at that point.
In Apollo 2, if I'm not mistaken there is no need to make an actual request anymore, the endpoint can be queries in the same process.
My understanding of all this is pretty fuzzy though so I might be wrong.

Thanks for the clarification! So are you currently using that schema link in the Apollo 2 branch?


Remove version: eat-pray-ai.yutu version 0.9.0

This version is older than what has been set in max-versions-to-keep by the publisher.
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/eat-pray-ai/yutu/releases/download/v0.9.0/yutu-windows-amd64.exe
OK
(Automated message - build 911)

Hi @OpenWaygate,
This manifest has the highest version number for this package. Is it available from another location? (This might be in error if the version is switching from semantic to string, or string to semantic.)
(Automated response - build 886.)

@stephengillie A newer version(0.9.1) has already been merged https://github.com/microsoft/winget-pkgs/pull/160773 , so this version can be removed safely.


Fix hamburger icon for mobile #36

Docusaurus 2 is built under Infima style framework so this is the way it looks on mobile. What I can do is to overwrite its style to make the change, but it may break its original setting. I have tested it on Firefox, Chrom, and Safari. Please let me know if you find other issues.
@Rodric Please let me know when docs.nimbella.com gets replaced so I can change the references link to point the docs site.

Thanks Sam.

Thanks Sam.


[Docs] Update required property indicator

Having spent so long staring at the docs :dizzy_face:, the optional/required indicator in front of the every prop description began to bother me (especially since most components don't even have required props), so I had a quick stab at visually simplifying it.
Before:

After:

The message also pluralises. (CircularProgress has multiple required props to save you looking for an example to test against. :smile:)
Another possibility is to have the asterisk against the property name, rather than the description.
@alitaheri @newoga @oliviertassinari ?

@mbrookes I agree, the required and optional words are an eyesore where they currently are. :+1:
I like the idea of putting the * by property name (or would be curious to see it that way). Also, maybe we can try styling it red.

Here's with the * by the property name:

I'd had to switch he font to Roboto, as otherwise it doesn't get that slight superscript, and looks wrong.

Last experiment, complimentary to the current PR:

Using strikethrough on the name of deprecated props, so the description can be less "shouty" than the current "DEPRECATED".

I don't think we can easily change the text color for required props, because it's markdown.

Oh, right. I forgot that was how it's rendered.
Either way, I think I like the * on the property name and I like the crossed out property name for deprecated. :+1:

@mbrookes Nice work :+1: :+1: You solved it very neatly :grin:
But the asterisk on prop name makes them unaligned, I liked it better when it was on the description.... Or at least, how about it having a very small column? or instead, it being placed after the name instead of before.

I don't think we can easily change the text color for required props, because it's markdown.

No, markdown supports inline html. you can just wrap the asterisk inside a <span> and give it any style you wish :grin:

What about

using the asterisk after the property name
using strikethrough on the name of deprecated props
removing the bold on Required and Deprecated`
removing the wording optional
?

@alitaheri:

But the asterisk on prop name makes them unaligned [...] how about [...] it being placed after the name instead of before.

Yes, that was where I tried it first, but it looked "wrong", however that was before I realised the problem was the font, not the position. I've put it back after the name now.

Latest:

Asterisk to right of prop name, colored. And the footnote is styled for size.

@mbrookes It's lovely :heart_eyes: :heart_eyes:. Thanks a lot :+1: :+1:

Yeah, I really like it! Required properties are easier to spot and the description is shorter.
@mbrookes Nice job :+1:.

One last thing - should we make the deprecated props read (sort of opposite the required props green, or is the strikethrough enough?

or is the strikethrough enough

I think changing the color is visual clutter in a way. lets Kip It Simple :grin:

I agree, I think this is really good as is. :+1:
Nice work @mbrookes!

JSX & inline styles per @oliviertassinari.

@mbrookes Thanks.
Then. I think we can merge it :100:.

Uh-oh, something's gone wrong!

Fixed and squashed.

@mbrookes :tada:


tests: fix shrink_osd scenario

the wrong image version was used to run shrink_osd playbook.
in stable-3.1 we should use a luminous image, not nautilus which doesn't
have ceph-disk binary anymore.
Signed-off-by: Guillaume Abrioux<EMAIL_ADDRESS>

jenkins test luminous-centos-non_container-shrink_osd

jenkins test luminous-centos-container-shrink_osd


Cross-Certificates for Kernel Mode Code Signing: Add expiration date of cross-certificates

There are also open questions:

Do Microsoft plan to issue new cross-certificates to CA before old one expires?
What will happen after software vendor will sign file after given certificate expires and timestamp counter signature will contain signed time after expiration of KM certificate? It seems signtool do not verifies expiration of additional certificate provided by switch /ac.

Do Microsoft plan to issue new cross-certificates to CA before old one expires?

No. This has been communicated to the driver community for over a year.

What will happen after software vendor will sign file after given certificate expires and timestamp counter signature will contain signed time after expiration of KM certificate? It seems signtool do not verifies expiration of additional certificate provided by switch /ac.

The timestamp proves that the certificate used for signing was valid at the time of signing, and so the signature is not considered expired. You need to use the /kp option with signtool verify for it to check the chains supplied by /ac. Note that given today's date, these signatures are not valid for driver signing, but are valid for /IntegrityCheck signing of user mode binaries.

Thanks for the PR!


fix frozen dict dataclass error encountered in google colab notebooks

This should fix errors encountered in the following issue:
https://github.com/google/nerfies/issues/24

@googlebot I signed it
On Sun, Aug 29, 2021 at 8:59 PM google-cla[bot] @.***>
wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project (if not, look below for help).
Before we can look at your pull request, you'll need to sign a Contributor
License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot
I signed it! and we'll verify it.
What to do if you already signed the CLA Individual signers

It's possible we don't have your GitHub username or you're using a
different email address on your commit. Check your existing CLA data
https://cla.developers.google.com/clas and verify that your email is
set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.

Corporate signers

Your company has a Point of Contact who decides which employees are
authorized to participate. Ask your POC to be added to the group of
authorized contributors. If you don't know who your Point of Contact is,
direct the Google project maintainer to go/cla#troubleshoot (Public
version https://opensource.google/docs/cla/#troubleshoot).
The email used to register you as an authorized contributor must be
the email used for the Git commit. Check your existing CLA data
https://cla.developers.google.com/clas and verify that your email is
set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
The email used to register you as an authorized contributor must
also be attached to your GitHub account
https://github.com/settings/emails.

ℹ Googlers: Go here
https://goto.google.com/prinfo/https%3A%2F%2Fgithub.com%2Fgoogle%2Fnerfies%2Fpull%2F29
for more info.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google/nerfies/pull/29#issuecomment-907995371, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AARIELVPVPTHJTJBXFYJDGTT7L6ZNANCNFSM5DBAIYZA
.


wrong position of window line when setting width = 'fill' unless setting placement.horizontal = 'center'

example config:
require('incline').setup {
        window = {
            width = 'fill',
            placement = {
                vertical = 'bottom',
            },
            margin = {
                horizontal = {
                    left = 0,
                    right = 0,
                },
            },
            padding = {
                left = 0,
                right = 0,
            },
        },
    }

when there are two windows, the window line for the window that is focused is left shifted (my focus is on the right window):

however, adding placement,horizontal = 'center' solves the issue. I guess the inner logic doesn't handle the width = fill case with placement.horizontal

Thanks for reporting! Can you test the latest commit and let me know if that fixes your issue?


BP-2667 setup:di:compile fails on PHP 7.4 due to newer PHP syntax used

The module still claims to be compatible with PHP 7.4. but it is not. The syntax private QuoteAddressFactory|BaseQuoteAddressFactory $quoteAddressFactory; in file Service/Applepay/Add.php is not working on 7.4, and thus setup:di:compile will terminate with a fatal error.
Ideally, you would check for such an issue in your CI pipeline. If you need help to improve the CI pipeline, let me know. Happy to support you.

@shochdoerfer ,
Thank you for mentioning this issue. We'll look into it and discuss it within the team.
We appreciate the help, If we need additional help regarding the CI pipeline we'll let you know.

@Buckaroo-Rene any news on this?

@jellesiderius ,
There has been some progress on this issue. A fix has been merged into our development branch.
Unfortunately it is not available yet in a new release. When I know more about a release date I'll let you know.
https://github.com/buckaroo-it/Magento2/pull/760/commits

@Buckaroo-Rene Great, thank you!

Released in v1.46.0


simpleTextUndefined

The youtube scraper was working perfectly fine before and using the maxRetryCount logic worked fine as well. But now, the addition of simpleText makes it work not at all. Could you please revert it?

You can install old version instead with npm install<EMAIL_ADDRESS>Can you reproduce it consistently? Is there any specific keyword of search? That will be helpful for me to fix this.

Okay i found what causes this, turns out not all video have published date for some reason..!
image
a12c5a358dc7cf69629c8bd81c07301c53fd79cf should fixed it. Published the update to npm (v1.0.9)
Thank you for reporting this bug! If the issue still persists, feel free to open it again :)


Replace OS title bar with custom one

One notable thing we can't yet do is give a warning that closing the editor window will discard unsaved changes. We could do that if we made our own exit button instead of using the OS one.

To be robust against other methods of exiting such as from the taskbar, we should modify the Application class left over from imgui-node-editor.


Coordinator: Allow dropping all segments.

Removes the coordinator sanity check that prevents it from dropping all
segments. It's useful to get rid of this, since the behavior is
unintuitive for dev/testing clusters where users might regularly want
to drop all their data to get back to a clean slate.
But the sanity check was there for a reason: to prevent a race condition
where the coordinator might drop all segments if it ran before the
first metadata store poll finished. This patch addresses that concern
differently, by allowing methods in MetadataSegmentManager to return
null if a poll has not happened yet, and canceling coordinator runs
in that case.
This patch also makes the "dataSources" reference in
SQLMetadataSegmentManager volatile. I'm not sure why it wasn't volatile
before, but it seems necessary to me: it's not final, and it's dereferenced
from multiple threads without synchronization.

I think this PR should had a Design Review tag. Such PRs shouldn't be merged 10 hours after opening.

The design with SQLMetadataSegmentManager enforcing leadership changes on its callers doesn't feel right to me. It forces all callers to handle this situation, while it doesn't feel that they should. For example, REST endpoints in MetadataResource shouldn't be responsible for this, rather, the user is responsible for querying the right Coordinator (the current leader).
I think that upon losing leadership Coordinator should just stop polling database, but still offering the last view of the segments.

@gianm this issue blocks my progress in #7306, I need to know in which direction to resolve conflicts. Please answer the last question.

@leventov, sorry, what question do you mean? Is it whether or not we should stop polling the DB after losing leadership? (https://github.com/apache/incubator-druid/pull/7447#issuecomment-482249849)
I can only think of one benefit of nullifying the metadata segment cache when losing leadership: it means that next time we gain leadership, we're guaranteed that the segment cache we use is at least as new as the gain of leadership. If we might use an old one, there's a potential for a new leader to use an older view of segments than the old leader. It could be extreme: maybe the new leader, for some reason, hasn't been able to poll for hours or even days, leading to surprising behavior as the cluster 'rolls back' to an earlier state.
This could be mitigated through some code that explicitly makes sure the currently-cached segment metadata is at least as new as the leadership gain, though. I think if you decide it's best to stop nullifying the cache, it'd be good to also add this safety mechanism.


[Feature] Ability to watch a remote branch: auto deploy when the remote branch has new commits

@hiteshjoshi this can be a potential duplicate of https://github.com/appsmithorg/appsmith/issues/11522, should we close this as more context is present in the other ticket?

Closing this as possible duplicate of https://github.com/appsmithorg/appsmith/issues/11522


Optimization Step loading bar instead of spinner

Change the loading animation from a spinner to a loading bar. A spinner should only be used for short loading times, and when uploading large datasets, the load time can be very long.

I agree! We should do the same for grooming and analysis.


Investigate why DisposeAsync is being called early before the operation complete.

When we access the IAsyncEnumerable directly to loop through items, DisposeAsync is being called before the operation is complete and when MoveNextAsync is called next, calls are failing due to the connection and reader being disposed of.

@MaddyDev - is this still something that needs investigation?

@MaddyDev - is this still something that needs investigation?

yep, have sent an email to @fabiocav regarding this.


add icons to docs and generated tables

Type of PR

[ ] BUG
[ ] FEAT
[ ] MAINT
[X] DOC

Is your Pull Request linked to an existing Issue or Pull Request?

No
Give a brief description for the solution you have provided

This PR does 2 things:

Adds icons for each backend to the docs
Adds links from comparison library tables to the function documentation

For 2, this has required some renaming of cl base functions to remove e.g. LevenshteinAtThresholdsComparisonBase -> LevenshteinAtThresholdsBase to more easily generate base function string from the end user functions (levenshtein_at_thresholds in this case). Plus I think this makes it more consistent with cll and ctl libraries. DateDiff... has been changed to Datediff... for similar reasons.
PR Checklist

[x] Added documentation for changes
[ ] Added feature to example notebooks at tutorials in splink_demos (if appropriate)
[ ] Added tests (if appropriate)
[ ] Made changes based off the latest version of Splink
[ ] Run the linter

Apologies, this is actually ready to review now.  I have now added a comparison functions table to comparison_composition_library just to reassure users that the functions are available across all backends


ModuleNotFoundError: No module named 'mysql'

Context
I'm trying to use MySQL Connector/Python with Zappa but keep getting ModuleNotFoundError: No module named 'mysql' after deploying. Everything works fine locally, the error only occurs on Lambda.
I'm installing mysql-connector-python from source URL:
pip install https://dev.mysql.com/get/Downloads/Connector-Python/mysql-connector-python-2.1.7.tar.gz
I also tried uninstalling mysql-connector-python and instead installed mysql-connector-python-rf via pip install mysql-connector-python-rf. I get the exact same issue, ModuleNotFoundError: No module named 'mysql' on Lambda (again, it works perfectly locally).
I am running Zappa from a virtual environment and am using Python 3.6.
I thought that the issue might be related to https://github.com/Miserlou/Zappa/issues/319, so I tried to create a wheel from the Platform Independent ZIP archive (from MySQL's download page). But every time I tried to do python setup.py sdist bdist_wheel I got error: invalid command 'bdist_wheel'. Spent a fair amount of time trying to get that to work before giving up.
Update: Interestingly enough, I tried using "use_precompiled_packages": false and no longer got ModuleNotFoundError: No module named 'mysql'. However, I then ended up getting:
Traceback (most recent call last):
  File "/var/task/handler.py", line 509, in lambda_handler
  return LambdaHandler.lambda_handler(event, context)
  File "/var/task/handler.py", line 237, in lambda_handler
  handler = cls()
  File "/var/task/handler.py", line 129, in __init__
  self.app_module = importlib.import_module(self.settings.APP_MODULE)
  File "/var/lang/lib/python3.6/importlib/__init__.py", line 126, in import_module
  return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 978, in _gcd_import
  File "<frozen importlib._bootstrap>", line 961, in _find_and_load
  File "<frozen importlib._bootstrap>", line 950, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 655, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 205, in _call_with_frames_removed
  File "/var/task/application.py", line 6, in <module>
  from PIL import Image
  File "/var/task/PIL/Image.py", line 58, in <module>
  from . import _imaging as core
ImportError: cannot import name '_imaging'

MySQL isn't built for Python3.6 yet. There is a related issue on the lambda-packages project.

Even when this issue is old:
Today I had the same issue using virtual Anaconda environment with Python 3.6 and mysql-connector-python 2.0.4 (this version was installed automatically by Anaconda)
I had the same error message:
ModuleNotFoundError: No module named 'mysql'
Installation of mysql-connector-python version 8.0.16 in Anaconda solved the problem.
Nevertheless, I couldn't use Python 3.7 because there where problems with the ssl package that is needed for mysql-connector-python.


Forward SSH passphrase requests to the user

If you use an SSH key with a passphrase, it's not possible to use the context menu options in pass-winmenu to synchronise your password repository. Because pass-winmenu launches Git without a shell, Git has no way to request your SSH passphrase, causing it to ignore any passphrase-protected keys, which means it won't be able to connect to the remote repository.
This will probably involve starting an SSH agent and requesting it to load an SSH key, as well as providing it with a passphrase.

https://git-scm.com/docs/gitcredentials

I've used both versions in my commit (and message) above in conjunction with native-git. I haven't done much experimenting with builtin so far.

Thanks for the PR. I'll test it to see see how it works, but it seems like a good idea to support GIT_SSH regardless.

Implemented in the pre-release.


Add date format option to defaults

Currently only affects the updated at field for PRs and issues.
Hoping to get feedback on this idea and help contribute to documentation or schema update as required.
Closes #67
Summary
How did you test this change?
This config will use a simple yyyy-mm-dd format with a larger column layout. Not entirely sure why its 12 width and not 10, maybe there is some padding by default.
defaults:
  layout:
    prs:
      updatedAt:
        width: 12
        grow: true
  dateFormat: "2006-01-02"

The special value of RELATIVE, or no value at all, will keep the existing relative dates.
defaults:
  dateFormat: "RELATIVE"

Images/Videos
None

Looks simple enough. nit Can we have the value be lower case relative?

Looks simple enough. nit Can we have the value be lower case relative? Also, what about the time? HH:MM I think that since this is written in Go, we should just follow Go's time.Format: go.dev/src/time/format.go and instruct users that's the format we expect

Correct, it is using the go time format, so adding some sort of docs link would probably be helpful.
By lower case relative do you mean compare to relative or make it case insensitive by allowing any form of Relative?

Yeah lowercase relative is my preference. We do have a docs site that you can add to. It's a kind of hugo site.

Yeah lowercase relative is my preference. We do have a docs site that you can add to. It's a kind of hugo site.

Gotcha, on it. Do you by chance have any tips on getting hugo to run locally. I did some research and have used hugo before but can't seem to get it working.

Can you please attach a screenshot of how this looks with a custom date?

Can you please attach a screenshot of how this looks with a custom date?

Added


[Discussion] Typing a command group should print its help text by default

It would be great if typing a command group (e.g. az component, az network) would print out the same text that you get when appending the -h flag. This would make the already well-documented nature of the CLI feel a little easier to navigate. For example, typing az network does in fact print out the list of acceptable commands, but it's a pretty long list, with no help descriptions, and so you really have to add -h to make that text usable.
I've always felt like help flags were mostly used for commands (to indicate that you don't want to execute it), and not command groups, and many CLIs special-case "executing" a command group by printing out its pretty-printed help text. For example, if you run docker network (or any other group/sub group), you get the full help text, that is analogous to what you'd get by running az network -h. It's a subtle difference, but saving a few keystrokes can go a long way when using a CLI a lot :)
This behavior would seem conceptually similar to the fact that simply typing az (which is the "root" command group) outputs the print-printed help text for the top-level command groups.

@lostintangent : Thanks for your input. This is something that team has gone back and forth on a bit and decided to stick with a minimalistic approach on a missing value case and providing a detailed help when the user asks for it (by doing -h or --help). This is something we have been looking for feedback from our customers as they use it to see if things are intuitive.
I have marked this as discussion and will talk to the team about this.
//cc @johanste

Same as #574

I could be convinced to treat "executing" the command group more like commands than failure/missing command. I assume that this would also mean that the return code for the "group command" would indicate success/0 (today, you'll get a failure/2 return code with the assumption that you made a mistake rather than asked for help)

@johanste That would be awesome :)

@johanste Any updates on this discussion?

Cleaning u old issues, reopen if this is still active.


Add support for AMEX CVC on the front of the card

Fixes #13

Adds the CVC to the front of the card if the type is amex, and doesn't flip to the back. See screenshots from the test.

Cool, thanks! :smile:

Published as 0.11.0 :+1: