Future directions

Basic plan: @OliverBalfour and @simonmaris will do some short-term cleanup

Update the build system and docs if necessary
Include fixes from forks and PR's
Fix the most critical bugs
Push out a new release

We're still figuring out:

Where will this repo go long term? Hopefully we transfer it to the obsidian-community GitHub org (as long as the community-plugins.json is updated too)
Who will maintain the repo long term? We're thinking a small group sharing responsibility

Patches I've just added:

Relative image path support (not yet sure if this is a full fix, but it doesn't break anything)
Release CI workflow

Dev instructions are in development.md

Use ESBuild instead of Rollup

Patches worth reviewing:

[ ] https://github.com/obsidian-community/obsidian-pandoc/compare/master...PeteMichaud:obsidian-pandoc:master?expand=1 (adds a mode to increment filenames instead of overwriting them)
[ ] https://github.com/OliverBalfour/obsidian-pandoc/compare/master...phillipjohnston:obsidian-pandoc:master?expand=1 (fixes admonitions and some types of embeds)
[ ] https://github.com/OliverBalfour/obsidian-pandoc/compare/master...ryuzee:obsidian-pandoc:master?expand=1 (relative path resolution for output file and CLI args - I think there's a more general way to do this?)
[ ] https://github.com/frogkind/obsidian-pandoc/commit/4a751c90eed338fc4c5b0776049128862fde4e84 (fixes SVG export with non-ASCII characters)
Alternative relative image path fixes:

[ ] https://github.com/dirkroorda/obsidian-pandoc/commit/b053a7c45939760bd74819a382632537275ff441
[ ] https://github.com/JDMcE/obsidian-pandoc/commit/4eb7e643a66541d8fc70f707225e781103e12c23

[ ] https://github.com/OliverBalfour/obsidian-pandoc/compare/master...BumbrT:obsidian-html-export:master?expand=1 (big refactor, something to do with div's and an export all feature? unsure if we want to merge, but maybe there's useful edits here to cherry pick)

I can see the issues are stacking up and also that this is a really valuable and critical obsidian plugin.
Are you open to adding more maintainers?
Maybe we could add a new issue called something like "Call for Maintainers" with a few questions to help people introduce themselves and establish their credibility and then give it a week or two, and add a few folk in that have a bunch of likes?
Just an idea. Would be good to have more maintainers on this project.


Need explain:

Hi,
I have three question:

What is easiest way to get my ethernet port IP address?

If  i have a friend in another county and i want let him to control on my Arduino throw the Internet, What i have to do?

In line 4 the port is 3030 how to make it a universal port for my Arduino ?

var five = require("johnny-five");
var EtherPort = require("etherport");
var board = new five.Board({
port: new EtherPort(3030)
});
Thank you.

What is easiest way to get my ethernet port IP address?

In your terminal:
$ ifconfig

If i have a friend in another county and i want let him to control on my Arduino throw the Internet, What i have to do?

I suggest using a websocket to your node.js program.

In line 4 the port is 3030 how to make it a universal port for my Arduino ?

That comes from this line:
https://github.com/firmata/arduino/blob/master/examples/StandardFirmataEthernet/StandardFirmataEthernet.ino#L110

Thanks for your answers,
$ ifconfig  ?? you mean $ ipconfig but i think this to get my computer ip address not  ethernet port IP address!
In my node.js program, how etherport connect to my remote Arduino using only  port (3030) and without Arduino IP address? i think i miss something!!

@tarek360 I meant ifconfig to get your computer's IP address. The instructions for getting the ethernet port IP are in this project's readme under Setup: steps 4-8


Updating a Basic Authentication credential invalidates the password

When updating a Basic Authentication credential, the password digest previously created at insertion time is re-hashed, destroying the original password.
This lines are causing the problem: https://github.com/Mashape/kong/blob/master/kong/plugins/basic-auth/daos.lua#L4-L7
Basically we should not re-encrypt the password if the password hasn't changed at all on an update operation.

Closed when #729 will be merged.


Remove Origin debug log

Summary
This removes the debug logging that was added in #1520 and #1521 as the Origin receipt was confirmed.
Changes

Removes Origin log from /v1/auth/nonce

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.06%) to 93.068%

Files with Coverage Reduction
New Missed Lines
%

src/domain/account/account.repository.ts
2
88.96%

Totals

Change from base Build<PHONE_NUMBER>:
0.06%

Covered Lines:
7042

Relevant Lines:
7293

💛  - Coveralls


Laravel 11 events are not auto discovered outside app folder

Laravel Version
^11.9
PHP Version
8.3.9
Database Driver & Version

Description
Reproduction repo url: https://github.com/xizprodev/laravel-with-events.
Description: Laravel does not allow "Listeners" to be discovered automatically if they are not in the app folder.
https://github.com/xizprodev/laravel-with-events/blob/master/app/Listeners/SendPodcastNotification.php - auto discovered (in the app folder)
https://github.com/xizprodev/laravel-with-events/tree/master/custom-namespace/FolderName/Listeners - is not auto discovered
Following documentation: https://laravel.com/docs/11.x/events#dispatching-events.
https://github.com/xizprodev/laravel-with-events/blob/master/bootstrap/app.php - has the ->withEvents with required folder path.
I think this is a bug because it is not specified in the docs that only the app folder will be scanned.
"If you plan to store your listeners in a different directory or within multiple directories, you may instruct Laravel to scan those directories using the withEvents method in your application's bootstrap/app.php file:"
Steps To Reproduce
git clone git@github.com:xizprodev/laravel-with-events.git
php artisan event:list
only App\Events\PodcastProcessed appear.

Found a fix: https://github.com/laravel/framework/pull/52976
Ok, so i find the problem.
The method DiscoverEvents::classFromFile return Custom-namespace\FolderName\Listeners\CustomListenerName instead of CustomNamespace\FolderName\Listeners\CustomListenerName
So my folder structure is like:
app
bootstrap
...
modules
modules-core
And the issue is with naming. But I think these folders should work. It's more of a preference.


CDaR and CVaR's portfolio_performance() not working with manually set weights

Describe the bug
CDaR and CVaR uses cp solver in the portfolio_performanace to get the value of cdar and cvar. But they they do not work with manually set weights.
ecdar = EfficientCDaR(mu, historical_returns)
ecdar.set_weights(input_weights)
ret, cdar = ecdar.portfolio_performance(verbose=False)
# cdar is un-changed for different weights.

ecvar = EfficientCDaR(mu, historical_returns)
ecvarset_weights(input_weights)
ret, cvar = ecvar.portfolio_performance(verbose=False)
# error due to None retuls from cvar.value.

Operating system, python version, PyPortfolioOpt version
Linux, Python 3.10.4, PyPortfolioOpt 1.5.2

Good point: the reason why this happens is that the calculation of CDaR/CVaR introduce auxiliary parameters (self._alpha, self._z below. I don't see a clean way to calculate these for a given set of input weights via set_weights, so I might just have to override the parent method and raise a NotImplementedError
    def portfolio_performance(self, verbose=False):
        mu = objective_functions.portfolio_return(
            self.weights, self.expected_returns, negative=False
        )

        cdar = self._alpha + 1.0 / (len(self.returns) * (1 - self._beta)) * cp.sum(
            self._z
        )
        cdar_val = cdar.value

ok. Thanks, Martin.


[apply-login-partner-changes] - admin login, put a button login just below password

Describe the bug
In the admin login, page cannot be scrolled down, so please add button to Login

fixed @robert-dm

tested locally, couldn't merge code, Login button is not showing up.

I can't figure out where is problem you talk about /admin ?
because it is scrollable and admin login button exist in all screen sizes @robert-dm

Ok if it is scrollable we can close it, thanks.


Fix #356

Tick the checkbox if you understand [x]:

[x] I have read and understand the pull request rules.

Description
Fixes #356
Added a more graceful disconnect when removing an agent to ensure socket.io is not in a "stuck" state where it attempts to keep an open connection to a deleted agent as well as a re-trigger of sendAgentList to ensure the UI has a quick update on agent deletion.
Type of change

Bug fix (non-breaking change which fixes an issue)

Checklist

[x] My code follows the style guidelines of this project
[x] I ran ESLint and other linters for modified files
[x] I have performed a self-review of my own code and tested it
[x] I have commented my code, particularly in hard-to-understand areas
(including JSDoc for methods)
[x] My changes generate no new warnings

I see https://github.com/louislam/dockge/actions/runs/11011056962/job/30574312169?pr=617#logs failing.
I did not change anything in the files it mentions so I don't know what happened exactly.

I see louislam/dockge/actions/runs/11011056962/job/30574312169?pr=617#logs failing.
I did not change anything in the files it mentions so I don't know what happened exactly.
If someone else wants to fix that CI fail be my guest. I am fixing the issue I had with dockge spamming my DNS server with queries to no longer existing services.

I assume that you are using Windows and your editor has formatted the file with CRLF.
npm run fmt should fix it. (if not https://stackoverflow.com/questions/27810758/how-to-replace-crlf-with-lf-in-a-single-file)

Thanks @Jayllyz
Oddly enough nothing
domi > dockge >  (fix-for-#356) >  20.11.0 > 13:58 > npm run fmt

><EMAIL_ADDRESS>fmt
> eslint "**/*.{ts,vue}" --fix

/domi/projects/dockge/backend/log.ts
    6:14  warning  Identifier 'CONSOLE_STYLE_Reset' is not in camel case         camelcase
    7:14  warning  Identifier 'CONSOLE_STYLE_Bright' is not in camel case        camelcase
    8:14  warning  Identifier 'CONSOLE_STYLE_Dim' is not in camel case           camelcase
    9:14  warning  Identifier 'CONSOLE_STYLE_Underscore' is not in camel case    camelcase
   10:14  warning  Identifier 'CONSOLE_STYLE_Blink' is not in camel case         camelcase
   11:14  warning  Identifier 'CONSOLE_STYLE_Reverse' is not in camel case       camelcase
   12:14  warning  Identifier 'CONSOLE_STYLE_Hidden' is not in camel case        camelcase
   14:14  warning  Identifier 'CONSOLE_STYLE_FgBlack' is not in camel case       camelcase
   15:14  warning  Identifier 'CONSOLE_STYLE_FgRed' is not in camel case         camelcase
   16:14  warning  Identifier 'CONSOLE_STYLE_FgGreen' is not in camel case       camelcase
   17:14  warning  Identifier 'CONSOLE_STYLE_FgYellow' is not in camel case      camelcase
   18:14  warning  Identifier 'CONSOLE_STYLE_FgBlue' is not in camel case        camelcase
   19:14  warning  Identifier 'CONSOLE_STYLE_FgMagenta' is not in camel case     camelcase
   20:14  warning  Identifier 'CONSOLE_STYLE_FgCyan' is not in camel case        camelcase
   21:14  warning  Identifier 'CONSOLE_STYLE_FgWhite' is not in camel case       camelcase
   22:14  warning  Identifier 'CONSOLE_STYLE_FgGray' is not in camel case        camelcase
   23:14  warning  Identifier 'CONSOLE_STYLE_FgOrange' is not in camel case      camelcase
   24:14  warning  Identifier 'CONSOLE_STYLE_FgLightGreen' is not in camel case  camelcase
   25:14  warning  Identifier 'CONSOLE_STYLE_FgLightBlue' is not in camel case   camelcase
   26:14  warning  Identifier 'CONSOLE_STYLE_FgViolet' is not in camel case      camelcase
   27:14  warning  Identifier 'CONSOLE_STYLE_FgBrown' is not in camel case       camelcase
   28:14  warning  Identifier 'CONSOLE_STYLE_FgPink' is not in camel case        camelcase
   30:14  warning  Identifier 'CONSOLE_STYLE_BgBlack' is not in camel case       camelcase
   31:14  warning  Identifier 'CONSOLE_STYLE_BgRed' is not in camel case         camelcase
   32:14  warning  Identifier 'CONSOLE_STYLE_BgGreen' is not in camel case       camelcase
   33:14  warning  Identifier 'CONSOLE_STYLE_BgYellow' is not in camel case      camelcase
   34:14  warning  Identifier 'CONSOLE_STYLE_BgBlue' is not in camel case        camelcase
   35:14  warning  Identifier 'CONSOLE_STYLE_BgMagenta' is not in camel case     camelcase
   36:14  warning  Identifier 'CONSOLE_STYLE_BgCyan' is not in camel case        camelcase
   37:14  warning  Identifier 'CONSOLE_STYLE_BgWhite' is not in camel case       camelcase
   38:14  warning  Identifier 'CONSOLE_STYLE_BgGray' is not in camel case        camelcase
   41:5   warning  Identifier 'CONSOLE_STYLE_FgCyan' is not in camel case        camelcase
   42:5   warning  Identifier 'CONSOLE_STYLE_FgGreen' is not in camel case       camelcase
   43:5   warning  Identifier 'CONSOLE_STYLE_FgLightGreen' is not in camel case  camelcase
   44:5   warning  Identifier 'CONSOLE_STYLE_FgBlue' is not in camel case        camelcase
   45:5   warning  Identifier 'CONSOLE_STYLE_FgLightBlue' is not in camel case   camelcase
   46:5   warning  Identifier 'CONSOLE_STYLE_FgMagenta' is not in camel case     camelcase
   47:5   warning  Identifier 'CONSOLE_STYLE_FgOrange' is not in camel case      camelcase
   48:5   warning  Identifier 'CONSOLE_STYLE_FgViolet' is not in camel case      camelcase
   49:5   warning  Identifier 'CONSOLE_STYLE_FgBrown' is not in camel case       camelcase
   50:5   warning  Identifier 'CONSOLE_STYLE_FgPink' is not in camel case        camelcase
   54:13  warning  Identifier 'CONSOLE_STYLE_FgCyan' is not in camel case        camelcase
   55:13  warning  Identifier 'CONSOLE_STYLE_FgYellow' is not in camel case      camelcase
   56:14  warning  Identifier 'CONSOLE_STYLE_FgRed' is not in camel case         camelcase
   57:14  warning  Identifier 'CONSOLE_STYLE_FgGray' is not in camel case        camelcase
  127:24  warning  Identifier 'CONSOLE_STYLE_FgCyan' is not in camel case        camelcase
  127:53  warning  Identifier 'CONSOLE_STYLE_Reset' is not in camel case         camelcase
  128:57  warning  Identifier 'CONSOLE_STYLE_Reset' is not in camel case         camelcase
  129:54  warning  Identifier 'CONSOLE_STYLE_Reset' is not in camel case         camelcase
  138:27  warning  Identifier 'CONSOLE_STYLE_FgRed' is not in camel case         camelcase
  138:55  warning  Identifier 'CONSOLE_STYLE_Reset' is not in camel case         camelcase
  145:28  warning  Identifier 'CONSOLE_STYLE_FgGray' is not in camel case        camelcase
  145:57  warning  Identifier 'CONSOLE_STYLE_Reset' is not in camel case         camelcase
  148:31  warning  Identifier 'CONSOLE_STYLE_FgGray' is not in camel case        camelcase
  148:60  warning  Identifier 'CONSOLE_STYLE_Reset' is not in camel case         camelcase

/domi/projects/dockge/backend/socket-handlers/main-socket-handler.ts
  7:28  warning  'twoFaRateLimiter' is defined but never used  no-unused-vars
  7:28  warning  'twoFaRateLimiter' is defined but never used  @typescript-eslint/no-unused-vars

/domi/projects/dockge/backend/stack.ts
  15:5  warning  'PROGRESS_TERMINAL_ROWS' is defined but never used  no-unused-vars
  15:5  warning  'PROGRESS_TERMINAL_ROWS' is defined but never used  @typescript-eslint/no-unused-vars

/domi/projects/dockge/backend/util-server.ts
  3:10  warning  'randomBytes' is defined but never used  no-unused-vars
  3:10  warning  'randomBytes' is defined but never used  @typescript-eslint/no-unused-vars

/domi/projects/dockge/frontend/src/components/Terminal.vue
  21:9  warning  Prop 'name' requires default value to be set         vue/require-default-prop
  26:9  warning  Prop 'endpoint' requires default value to be set     vue/require-default-prop
  32:9  warning  Prop 'stackName' requires default value to be set    vue/require-default-prop
  37:9  warning  Prop 'serviceName' requires default value to be set  vue/require-default-prop

/domi/projects/dockge/frontend/src/pages/Compose.vue
   66:28  warning  Variable 'url' is already declared in the upper scope       vue/no-template-shadow
  101:60  warning  Variable 'endpoint' is already declared in the upper scope  vue/no-template-shadow

/domi/projects/dockge/frontend/src/pages/DashboardHome.vue
  43:38  warning  Variable 'agent' is already declared in the upper scope  vue/no-template-shadow

✖ 68 problems (0 errors, 68 warnings)

domi > dockge >  (fix-for-#356) >  20.11.0 > 13:58 > git add .
domi > dockge >  (fix-for-#356) >  20.11.0 > 13:59 > git commit -m "Fix New Lines"
On branch fix-for-#356
Your branch is up to date with 'origin/fix-for-#356'.

nothing to commit, working tree clean

This is confusing me as my previous commit didn't even touch these files.


Usersnap Feedback - Clicked profile image icon and selected profile. Says "loading user data" [...]

Sender<EMAIL_ADDRESS>Comment: Clicked profile image icon and selected profile. Says "loading user data" but nothing happens.
Console:
user:1 GET https://api.participedia.xyz/user 401 ()
Open #17 in Usersnap Dashboard

Download original image
Browser: Chrome 57 (macOS Sierra)
Referer: https://participedia.xyz/profile
Screen size: 1280 x 800 Browser size: 999 x 676
Powered by usersnap.com

This issue was moved to participedia/usersnaps#17


Unbreak xine-lib and dvdstyler

Motivation for this change
xine-lib is currently broken on master since the latest libcaca bump. And it will also break with ffmpeg 5.x which is currently on staging.
This reuses patches from Arch for both problems.
dvdstyler is broken on master and on 21.11 because it crashes on startup because of a symbols conflict between GTK2 and GTK3. It works only with wxGTK30 without GTK2.
It was also missing wrapping for Gnome apps.
(I will later backport the second commit)
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review run on x86_64-linux 1

6 packages built:

dvdstyler
eaglemode
quodlibet-xine
quodlibet-xine-full
xine-lib
xine-ui

Why does it fail in ARM Linux?

It is xine-ui failing, not xine-lib.
And it's failing on Hydra since it was bumped from 0.99.12 to 0.99.13

Ok then.

We would need this change to fix xine-ui on aarch64.
I'll see if someone already made a patch of that, or add it in our tree.

@ofborg build xine-ui


Chat - Add loading component to messages

Task:
We need a loading indicator to let our Users know they warp is communicating and trying to send the message
Indicator needs designed

[ ] Indicator should appear next to the any message attempted to be sent
[ ] Indicator should persist until Warp has successfully delivered the message to the recipient

For p2p (or direct messaging), using RayGun::message_status should work fine in letting one know if a message has been sent or not. A message that isnt sent would generally be in the queue.
Do note that this isnt exactly applicable for group chat at this time, but would change in the near future.


[DNM] copr: support count

@shenli @coocood @qiuyesuifeng PTAL

Coverage increased (+0.1%) to 81.768% when pulling 1e1321a8b3c63f9d06e2777a83823349e696bd01 on busyjay/support-count into 2fc3f29d77e76cadf83cd0afae5b986ac5960b7e on master.

Coverage increased (+0.1%) to 81.749% when pulling eb6190b0ab2f46f5658b13af2ddaacff7cbe5ddc on busyjay/support-count into 2fc3f29d77e76cadf83cd0afae5b986ac5960b7e on master.

LGTM

LGTM


GitHub pages documentation is not accessible

http://ciena-frost.github.io/ember-frost-modal

Look's like the gh-pages branch is empty, and the last commit removed everything but didn't add the new files that should've been created

Manually pushed the latest version on the gh-pages branch and the demo is back up. Will hav to keep an eye on this for the next PR.

Looks like a PR broke the demo page again

Due to failed build during publish of gh-pages
https://travis-ci.org/ciena-frost/ember-frost-modal/jobs/269655099#L2327

this addon doesnt use ember-css-modules...hmm


[sail] Build error

Package: sail[bmp,core,gif,high-priority,jpeg,png,tiff]:x64-windows -> 0.9.0-rc3#2
Host Environment

Host: x64-windows
Compiler: MSVC 19.36.32535.0
vcpkg-tool version: 2023-06-22-f19f3d9939100085fe2f7e41502d60b08e2083b6
vcpkg-scripts version: 228987a6f 2023-07-05 (5 hours ago)

To Reproduce
vcpkg install
Failure logs
-- Using cached HappySeaFox-sail-v0.9.0-rc3.tar.gz.
-- Cleaning sources at C:/_development_/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/src/v0.9.0-rc3-d33782e697.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/_development_/graphicsEngine/3rd_party/vcpkg/downloads/HappySeaFox-sail-v0.9.0-rc3.tar.gz
-- Applying patch avif.patch
-- Applying patch webp.patch
-- Using source at C:/_development_/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/src/v0.9.0-rc3-d33782e697.clean
-- Found external ninja('1.11.0').
-- Configuring x64-windows
-- Building x64-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
    Command failed: C:/CMake/bin/cmake.exe --build . --config Debug --target install -- -v -j13
    Working Directory: C:/_development_/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/x64-windows-dbg
    See logs for more information:
      C:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\install-x64-windows-dbg-out.log

Call Stack (most recent call first):
  C:/_development_/graphicsEngine/build/vcpkg_installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
  C:/_development_/graphicsEngine/build/vcpkg_installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
  buildtrees/versioning_/versions/sail/0c604af0721281506a77f887d07abca30fe350c3/portfile.cmake:33 (vcpkg_cmake_install)
  scripts/ports.cmake:147 (include)

C:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\install-x64-windows-dbg-out.log
[1/100] C:\PROGRA~1\MIB055~1\2022\COMMUN~1\VC\Tools\MSVC\1436~1.325\bin\Hostx64\x64\cl.exe   -DSAIL_BUILD -DSAIL_COLORED_OUTPUT=1 -Dsail_common_EXPORTS -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\include -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common /nologo /DWIN32 /D_WINDOWS /W4 /utf-8 /MP  /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1  -std:c11 /YcC:/_development_/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/x64-windows-dbg/src/libsail-common/CMakeFiles/sail-common.dir/cmake_pch.h /FpC:/_development_/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/x64-windows-dbg/src/libsail-common/CMakeFiles/sail-common.dir/./cmake_pch.c.pch /FIC:/_development_/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/x64-windows-dbg/src/libsail-common/CMakeFiles/sail-common.dir/cmake_pch.h /showIncludes /Fosrc\libsail-common\CMakeFiles\sail-common.dir\cmake_pch.c.obj /Fdsrc\libsail-common\CMakeFiles\sail-common.dir\ /FS -c C:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\src\libsail-common\CMakeFiles\sail-common.dir\cmake_pch.c
FAILED: src/libsail-common/CMakeFiles/sail-common.dir/cmake_pch.c.obj
C:\PROGRA~1\MIB055~1\2022\COMMUN~1\VC\Tools\MSVC\1436~1.325\bin\Hostx64\x64\cl.exe   -DSAIL_BUILD -DSAIL_COLORED_OUTPUT=1 -Dsail_common_EXPORTS -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\include -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common /nologo /DWIN32 /D_WINDOWS /W4 /utf-8 /MP  /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1  -std:c11 /YcC:/_development_/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/x64-windows-dbg/src/libsail-common/CMakeFiles/sail-common.dir/cmake_pch.h /FpC:/_development_/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/x64-windows-dbg/src/libsail-common/CMakeFiles/sail-common.dir/./cmake_pch.c.pch /FIC:/_development_/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/x64-windows-dbg/src/libsail-common/CMakeFiles/sail-common.dir/cmake_pch.h /showIncludes /Fosrc\libsail-common\CMakeFiles\sail-common.dir\cmake_pch.c.obj /Fdsrc\libsail-common\CMakeFiles\sail-common.dir\ /FS -c C:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\src\libsail-common\CMakeFiles\sail-common.dir\cmake_pch.c
C:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\src\libsail-common\CMakeFiles\sail-common.dir\cmake_pch.c : fatal error C1083: Cannot open compiler intermediate file: 'c:\_development_\graphicsengine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\src\libsail-common\cmakefiles\sail-common.dir\cmake_pch.c.pch': No such file or directory
[2/100] C:\PROGRA~1\MIB055~1\2022\COMMUN~1\VC\Tools\MSVC\1436~1.325\bin\Hostx64\x64\cl.exe   -DSAIL_BUILD -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\include -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\sail-codecs\common\bmp\..\.. /nologo /DWIN32 /D_WINDOWS /W4 /utf-8 /MP  /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1  -std:c11 /showIncludes /Fosrc\sail-codecs\bmp\CMakeFiles\sail-codec-bmp.dir\bmp.c.obj /Fdsrc\sail-codecs\bmp\CMakeFiles\sail-codec-bmp.dir\ /FS -c C:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\sail-codecs\bmp\bmp.c
[3/100] C:\PROGRA~1\MIB055~1\2022\COMMUN~1\VC\Tools\MSVC\1436~1.325\bin\Hostx64\x64\cl.exe   -DSAIL_BUILD -DSAIL_HAVE_JPEG_ICCP -DSAIL_HAVE_JPEG_JCS_EXT -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\include -IC:\_development_\graphicsEngine\build\vcpkg_installed\x64-windows\include -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common /nologo /DWIN32 /D_WINDOWS /W4 /utf-8 /MP  /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1  -std:c11 /showIncludes /Fosrc\sail-codecs\jpeg\CMakeFiles\sail-codec-jpeg.dir\io_src.c.obj /Fdsrc\sail-codecs\jpeg\CMakeFiles\sail-codec-jpeg.dir\ /FS -c C:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\sail-codecs\jpeg\io_src.c
[4/100] C:\PROGRA~1\MIB055~1\2022\COMMUN~1\VC\Tools\MSVC\1436~1.325\bin\Hostx64\x64\cl.exe   -DSAIL_BUILD -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\include -IC:\_development_\graphicsEngine\build\vcpkg_installed\x64-windows\include -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common /nologo /DWIN32 /D_WINDOWS /W4 /utf-8 /MP  /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1  -std:c11 /showIncludes /Fosrc\sail-codecs\gif\CMakeFiles\sail-codec-gif.dir\io.c.obj /Fdsrc\sail-codecs\gif\CMakeFiles\sail-codec-gif.dir\ /FS -c C:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\sail-codecs\gif\io.c
[5/100] C:\PROGRA~1\MIB055~1\2022\COMMUN~1\VC\Tools\MSVC\1436~1.325\bin\Hostx64\x64\cl.exe   -DSAIL_BUILD -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\include -IC:\_development_\graphicsEngine\build\vcpkg_installed\x64-windows\include -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common /nologo /DWIN32 /D_WINDOWS /W4 /utf-8 /MP  /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1  -std:c11 /showIncludes /Fosrc\sail-codecs\gif\CMakeFiles\sail-codec-gif.dir\helpers.c.obj /Fdsrc\sail-codecs\gif\CMakeFiles\sail-codec-gif.dir\ /FS -c C:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\sail-codecs\gif\helpers.c
[6/100] C:\PROGRA~1\MIB055~1\2022\COMMUN~1\VC\Tools\MSVC\1436~1.325\bin\Hostx64\x64\cl.exe   -DSAIL_BUILD -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\include -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\sail-codecs\common\bmp\..\.. -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common /nologo /DWIN32 /D_WINDOWS /W4 /utf-8 /MP  /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1  -std:c11 /showIncludes /Fosrc\sail-codecs\common\bmp\CMakeFiles\bmp-common.dir\helpers.c.obj /Fdsrc\sail-codecs\common\bmp\CMakeFiles\bmp-common.dir\ /FS -c C:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\sail-codecs\common\bmp\helpers.c
[7/100] C:\PROGRA~1\MIB055~1\2022\COMMUN~1\VC\Tools\MSVC\1436~1.325\bin\Hostx64\x64\cl.exe   -DSAIL_BUILD -DSAIL_HAVE_JPEG_ICCP -DSAIL_HAVE_JPEG_JCS_EXT -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\include -IC:\_development_\graphicsEngine\build\vcpkg_installed\x64-windows\include -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common /nologo /DWIN32 /D_WINDOWS /W4 /utf-8 /MP  /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1  -std:c11 /showIncludes /Fosrc\sail-codecs\jpeg\CMakeFiles\sail-codec-jpeg.dir\jpeg.c.obj /Fdsrc\sail-codecs\jpeg\CMakeFiles\sail-codec-jpeg.dir\ /FS -c C:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\sail-codecs\jpeg\jpeg.c
C:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\sail-codecs\jpeg\helpers.h(43): warning C4324: 'jpeg_private_my_error_context': structure was padded due to alignment specifier
[8/100] C:\PROGRA~1\MIB055~1\2022\COMMUN~1\VC\Tools\MSVC\1436~1.325\bin\Hostx64\x64\cl.exe   -DSAIL_BUILD -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\include -IC:\_development_\graphicsEngine\build\vcpkg_installed\x64-windows\include -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common /nologo /DWIN32 /D_WINDOWS /W4 /utf-8 /MP  /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1  -std:c11 /showIncludes /Fosrc\sail-codecs\gif\CMakeFiles\sail-codec-gif.dir\gif.c.obj /Fdsrc\sail-codecs\gif\CMakeFiles\sail-codec-gif.dir\ /FS -c C:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\sail-codecs\gif\gif.c
[9/100] C:\PROGRA~1\MIB055~1\2022\COMMUN~1\VC\Tools\MSVC\1436~1.325\bin\Hostx64\x64\cl.exe   -DSAIL_BUILD -DSAIL_HAVE_JPEG_ICCP -DSAIL_HAVE_JPEG_JCS_EXT -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\include -IC:\_development_\graphicsEngine\build\vcpkg_installed\x64-windows\include -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common /nologo /DWIN32 /D_WINDOWS /W4 /utf-8 /MP  /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1  -std:c11 /showIncludes /Fosrc\sail-codecs\jpeg\CMakeFiles\sail-codec-jpeg.dir\io_dest.c.obj /Fdsrc\sail-codecs\jpeg\CMakeFiles\sail-codec-jpeg.dir\ /FS -c C:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\sail-codecs\jpeg\io_dest.c
[10/100] C:\PROGRA~1\MIB055~1\2022\COMMUN~1\VC\Tools\MSVC\1436~1.325\bin\Hostx64\x64\cl.exe   -DSAIL_BUILD -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\include -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\sail-codecs\common\bmp\..\.. -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common /nologo /DWIN32 /D_WINDOWS /W4 /utf-8 /MP  /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1  -std:c11 /showIncludes /Fosrc\sail-codecs\common\bmp\CMakeFiles\bmp-common.dir\bmp.c.obj /Fdsrc\sail-codecs\common\bmp\CMakeFiles\bmp-common.dir\ /FS -c C:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\sail-codecs\common\bmp\bmp.c
[11/100] C:\PROGRA~1\MIB055~1\2022\COMMUN~1\VC\Tools\MSVC\1436~1.325\bin\Hostx64\x64\cl.exe   -DSAIL_BUILD -DSAIL_HAVE_JPEG_ICCP -DSAIL_HAVE_JPEG_JCS_EXT -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\include -IC:\_development_\graphicsEngine\build\vcpkg_installed\x64-windows\include -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common /nologo /DWIN32 /D_WINDOWS /W4 /utf-8 /MP  /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1  -std:c11 /showIncludes /Fosrc\sail-codecs\jpeg\CMakeFiles\sail-codec-jpeg.dir\helpers.c.obj /Fdsrc\sail-codecs\jpeg\CMakeFiles\sail-codec-jpeg.dir\ /FS -c C:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\sail-codecs\jpeg\helpers.c
C:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\sail-codecs\jpeg\helpers.h(43): warning C4324: 'jpeg_private_my_error_context': structure was padded due to alignment specifier
[12/100] C:\PROGRA~1\MIB055~1\2022\COMMUN~1\VC\Tools\MSVC\1436~1.325\bin\Hostx64\x64\cl.exe   -DSAIL_BUILD -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\include -IC:\_development_\graphicsEngine\build\vcpkg_installed\x64-windows\include -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common /nologo /DWIN32 /D_WINDOWS /W4 /utf-8 /MP  /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1  -std:c11 /showIncludes /Fosrc\sail-codecs\png\CMakeFiles\sail-codec-png.dir\helpers.c.obj /Fdsrc\sail-codecs\png\CMakeFiles\sail-codec-png.dir\ /FS -c C:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\sail-codecs\png\helpers.c
[13/100] C:\PROGRA~1\MIB055~1\2022\COMMUN~1\VC\Tools\MSVC\1436~1.325\bin\Hostx64\x64\cl.exe   -DSAIL_BUILD -Dsail_manip_EXPORTS -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\include -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-manip -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common /nologo /DWIN32 /D_WINDOWS /W4 /utf-8 /MP  /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1  -std:c11 /YcC:/_development_/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/x64-windows-dbg/src/libsail-manip/CMakeFiles/sail-manip.dir/cmake_pch.h /FpC:/_development_/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/x64-windows-dbg/src/libsail-manip/CMakeFiles/sail-manip.dir/./cmake_pch.c.pch /FIC:/_development_/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/x64-windows-dbg/src/libsail-manip/CMakeFiles/sail-manip.dir/cmake_pch.h /showIncludes /Fosrc\libsail-manip\CMakeFiles\sail-manip.dir\cmake_pch.c.obj /Fdsrc\libsail-manip\CMakeFiles\sail-manip.dir\ /FS -c C:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\src\libsail-manip\CMakeFiles\sail-manip.dir\cmake_pch.c
FAILED: src/libsail-manip/CMakeFiles/sail-manip.dir/cmake_pch.c.obj
C:\PROGRA~1\MIB055~1\2022\COMMUN~1\VC\Tools\MSVC\1436~1.325\bin\Hostx64\x64\cl.exe   -DSAIL_BUILD -Dsail_manip_EXPORTS -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\include -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-manip -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common /nologo /DWIN32 /D_WINDOWS /W4 /utf-8 /MP  /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1  -std:c11 /YcC:/_development_/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/x64-windows-dbg/src/libsail-manip/CMakeFiles/sail-manip.dir/cmake_pch.h /FpC:/_development_/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/x64-windows-dbg/src/libsail-manip/CMakeFiles/sail-manip.dir/./cmake_pch.c.pch /FIC:/_development_/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/x64-windows-dbg/src/libsail-manip/CMakeFiles/sail-manip.dir/cmake_pch.h /showIncludes /Fosrc\libsail-manip\CMakeFiles\sail-manip.dir\cmake_pch.c.obj /Fdsrc\libsail-manip\CMakeFiles\sail-manip.dir\ /FS -c C:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\src\libsail-manip\CMakeFiles\sail-manip.dir\cmake_pch.c
C:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\src\libsail-manip\CMakeFiles\sail-manip.dir\cmake_pch.c : fatal error C1083: Cannot open compiler intermediate file: 'c:\_development_\graphicsengine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\src\libsail-manip\cmakefiles\sail-manip.dir\cmake_pch.c.pch': No such file or directory
ninja: build stopped: subcommand failed.

Additional context
vcpkg.json
{
  "builtin-baseline": "228987a6fdbd56739a16d47eacf6e79d71a47973",
  "dependencies": [
    {
      "name": "sail",
      "version>=": "0.9.0-rc3#1"
    },
    {
      "name": "freetype",
      "version>=": "2.12.1#3"
    },
    {
      "name": "tbb",
      "version>=": "2021.8.0"
    },
    {
      "name": "glm",
      "version>=": "<IP_ADDRESS>#2"
    },
    {
      "name": "spdlog",
      "version>=": "1.11.0"
    },
    {
      "name": "entt",
      "version>=": "3.11.1"
    },
    {
      "name": "taskflow",
      "version>=": "3.5.0"
    },
    {
      "name": "asio",
      "version>=": "1.24.0#1"
    },
    {
      "name": "glfw3",
      "version>=": "3.3.8#2"
    },
    {
      "name": "gtest",
      "version>=": "1.13.0"
    }
  ]
}

@jimli570, Thanks for posting this issue, please not use spaces or special characters in the project path:
C:\_development_\graphicsEngine\3rd_party\vcpkg

please change to
C:\development\graphicsEngine\3rd_party\vcpkg

try again.

_  doesn't cause problems.

@jimli570, I can't reproduce your error locally.
Stored binaries in 1 destinations in 736 ms.
Elapsed time to handle tbb:x86-windows: 34 s
Total install time: 6.8 min
asio provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(asio CONFIG REQUIRED)
    target_link_libraries(main PRIVATE asio::asio)

entt provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(EnTT CONFIG REQUIRED)
    target_link_libraries(main PRIVATE EnTT::EnTT)

freetype is compatible with built-in CMake targets:

    find_package(Freetype REQUIRED)
    target_link_libraries(main PRIVATE Freetype::Freetype) # since CMake 3.10

glfw3 provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(glfw3 CONFIG REQUIRED)
    target_link_libraries(main PRIVATE glfw)

glm provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(glm CONFIG REQUIRED)
    target_link_libraries(main PRIVATE glm::glm)

The package gtest is compatible with built-in CMake targets:

    enable_testing()

    find_package(GTest CONFIG REQUIRED)
    target_link_libraries(main PRIVATE GTest::gtest GTest::gtest_main GTest::gmock GTest::gmock_main)

    add_test(AllTestsInMain main)

The package sail provides CMake targets:

C libraries:

    find_package(Sail CONFIG REQUIRED)
    target_link_libraries(main PRIVATE SAIL::sail)

C++ bindings:

    find_package(SailC++ CONFIG REQUIRED)
    target_link_libraries(main PRIVATE SAIL::sail-c++)

The package spdlog provides CMake targets:

    find_package(spdlog CONFIG REQUIRED)
    target_link_libraries(main PRIVATE spdlog::spdlog)

    # Or use the header-only version
    find_package(spdlog CONFIG REQUIRED)
    target_link_libraries(main PRIVATE spdlog::spdlog_header_only)

taskflow provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(Taskflow CONFIG REQUIRED)
    target_link_libraries(main PRIVATE Taskflow::Taskflow)

tbb provides CMake targets:

    # this is heuristically generated, and may not be correct
    find_package(TBB CONFIG REQUIRED)
    target_link_libraries(main PRIVATE TBB::tbb TBB::tbbmalloc TBB::tbbmalloc_proxy)

Failures:
C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\src\libsail-common\CMakeFiles\sail-common.dir\cmake_pch.c : fatal error C1083: Cannot open compiler intermediate file: 'c:_development_\graphicsengine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\src\libsail-common\cmakefiles\sail-common.dir\cmake_pch.c.pch': No such file or directory
Hi @jimli570, I can't repro this issue locally, could you help confirm if cmake_pch.c.pch generated successfully in your local machine? BTW, _ doesn't cause the failures.

Open x64 Native Tools command
pushd C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg
Execute

C:\PROGRA~1\MIB055~1\2022\COMMUN~1\VC\Tools\MSVC\1436~1.325\bin\Hostx64\x64\cl.exe   -DSAIL_BUILD -DSAIL_COLORED_OUTPUT=1 -Dsail_common_EXPORTS -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\include -IC:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common /nologo /DWIN32 /D_WINDOWS /W4 /utf-8 /MP  /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1  -std:c11 /YcC:/_development_/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/x64-windows-dbg/src/libsail-common/CMakeFiles/sail-common.dir/cmake_pch.h /FpC:/_development_/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/x64-windows-dbg/src/libsail-common/CMakeFiles/sail-common.dir/./cmake_pch.c.pch /FIC:/_development_/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/x64-windows-dbg/src/libsail-common/CMakeFiles/sail-common.dir/cmake_pch.h /showIncludes /Fosrc\libsail-common\CMakeFiles\sail-common.dir\cmake_pch.c.obj /Fdsrc\libsail-common\CMakeFiles\sail-common.dir\ /FS -c C:\_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\src\libsail-common\CMakeFiles\sail-common.dir\cmake_pch.c

Check if c:_development_\graphicsengine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\src\libsail-common\cmakefiles\sail-common.dir\cmake_pch.c.pch generated.

Thank you for your replies!
I did try your suggestions @JonLiu1993 , it gave no difference.
@PhoebeHui  c:_development_\graphicsengine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\src\libsail-common\cmakefiles\sail-common.dir\cmake_pch.c.pch  is generated in the buildstep already. but i did also try remove the file, and then follow your steps, and it generates the file (it do exist when I check), but with the following output:

cl.exe   -DSAIL_BUILD -DSAIL_COLORED_OUTPUT=1 -Dsail_common_EXPORTS -IC:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\include -IC:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common /nologo /DWIN32 /D_WINDOWS /W4 /utf-8 /MP  /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1  -std:c11 /YcC:/development/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/x64-windows-dbg/src/libsail-common/CMakeFiles/sail-common.dir/cmake_pch.h /FpC:/development/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/x64-windows-dbg/src/libsail-common/CMakeFiles/sail-common.dir/./cmake_pch.c.pch /FIC:/development/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/x64-windows-dbg/src/libsail-common/CMakeFiles/sail-common.dir/cmake_pch.h /showIncludes /Fosrc\libsail-common\CMakeFiles\sail-common.dir\cmake_pch.c.obj /Fdsrc\libsail-common\CMakeFiles\sail-common.dir\ /FS -c C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\src\libsail-common\CMakeFiles\sail-common.dir\cmake_pch.c
cmake_pch.c
Note: including file: C:/development/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/x64-windows-dbg/src/libsail-common/CMakeFiles/sail-common.dir/cmake_pch.h
Note: including file:  C:/development/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/src/v0.9.0-rc3-d33782e697.clean/src/libsail-common/sail-common.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\include\config.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\common.h
Note: including file:    C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\error.h
Note: including file:     C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\compiler_specifics.h
Note: including file:    C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\export.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\common_serialize.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\compression_level.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\hash_map.h
Note: including file:    C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.33.31629\include\stdbool.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\hash_map_p.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\iccp.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\image.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\io_common.h
Note: including file:    C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt\stddef.h
Note: including file:     C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt\corecrt.h
Note: including file:      C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.33.31629\include\vcruntime.h
Note: including file:       C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.33.31629\include\sal.h
Note: including file:        C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.33.31629\include\concurrencysal.h
Note: including file:       C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.33.31629\include\vadefs.h
Note: including file:    C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.33.31629\include\stdint.h
Note: including file:    C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt\stdio.h
Note: including file:     C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt\corecrt_wstdio.h
Note: including file:      C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt\corecrt_stdio_config.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\linked_list_node.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\load_features.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\load_options.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\log.h
Note: including file:    C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.33.31629\include\stdarg.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\memory.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\meta_data.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\meta_data_node.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\palette.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\pixel.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\resolution.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\save_features.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\save_options.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\source_image.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\string_node.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\utils.h
Note: including file:    C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt\wchar.h
Note: including file:     C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt\corecrt_memcpy_s.h
Note: including file:      C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt\errno.h
Note: including file:      C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.33.31629\include\vcruntime_string.h
Note: including file:     C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt\corecrt_wconio.h
Note: including file:     C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt\corecrt_wctype.h
Note: including file:     C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt\corecrt_wdirect.h
Note: including file:     C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt\corecrt_wio.h
Note: including file:      C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt\corecrt_share.h
Note: including file:     C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt\corecrt_wprocess.h
Note: including file:     C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt\corecrt_wstdlib.h
Note: including file:     C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt\corecrt_wstring.h
Note: including file:     C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt\corecrt_wtime.h
Note: including file:     C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt\sys/stat.h
Note: including file:      C:\Program Files (x86)\Windows Kits\10\include\10.0.22621.0\ucrt\sys/types.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\variant.h
Note: including file:   C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\src\v0.9.0-rc3-d33782e697.clean\src\libsail-common\variant_node.h
C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\src\libsail-common\CMakeFiles\sail-common.dir\cmake_pch.c : fatal error C1083: Cannot open compiler intermediate file: 'c:_development_\graphicsengine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\src\libsail-common\cmakefiles\sail-common.dir\cmake_pch.c.pch': No such file or directory

Any other suggestions I should look into?

Note: including file: C:/development/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/src/v0.9.0-rc3-d33782e697.clean/src/libsail-common/sail-common.h
Note: including file: C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\include\config.h

How did the path change here?

Note: including file: C:/development/graphicsEngine/3rd_party/vcpkg/buildtrees/sail/src/v0.9.0-rc3-d33782e697.clean/src/libsail-common/sail-common.h
Note: including file: C:_development_\graphicsEngine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\include\config.h

How did the path change here?

Good spot, I was wonder for a second too. Until I noticed github apperently did want transcript that as italic formating, here on github

I fixed the format in above comments, sorry for that! please let us know if the file generated correctly in your machine.

@jimli570, Try disabling precompiled headers. Project settings / C/C++ / Precompiled Headers.
Precompiled Headers: Not Using Precompiled Headers

Why is this taggad as a question btw?

Because according to the error log, it doesn't look like a port bug, and I can successfully install sail locally using the same environment, so I think this is a question related to compilation.

@jimli570, Try disabling precompiled headers. Project settings / C/C++ / Precompiled Headers.
Precompiled Headers: Not Using Precompiled Headers

Not sure how to test this? I am not using visual studio

@jimli570, Please open the VS you are using

Create a C++ project
Then click the project on the top toolbar, select the bottom property of the pop-up menu
open it, and click "Precompiled Header" in the C/C++ rot on the left.
Could you take a screenshot to see what you have set? There are three options: Create (/YC), Use (/Yu) and Not Using Precompiled Headers. If you choose Not Using Precompiled Headers, you can disable precompiled header files.

@PhoebeHui c:development\graphicsengine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\src\libsail-common\cmakefiles\sail-common.dir\cmake_pch.c.pch is generated in the buildstep already. but i did also try remove the file, and then follow your steps, and it generates the file (it do exist when I check), but with the following output:

It's strange, that means the cmake_pch.c.pch generated correctly, but failed to find during build. May be related to multi-thread build? I still can't repro this issue locally.
Failures:
fatal error C1083: Cannot open compiler intermediate file: 'c:\_development_\graphicsengine\3rd_party\vcpkg\buildtrees\sail\x64-windows-dbg\src\libsail-common\cmakefiles\sail-common.dir\cmake_pch.c.pch': No such file or directory

@jimli570,have you solved the problems now? could you please setting VCPKG_CONCURRENCY=1 as an environment variable and try again? I suspect this caused by multi-thread build.

@JonLiu1993 dit try setting that value through CMAKE, did not help.
@PhoebeHui Not solved it, did try your idea also, but not to any help.
Have everything up & running on my stationary, so now when I had access to It I have compared paths, versions and all with my enviroment on my laptop (that is where I do not get it running), but looks the same to me.

Permission issue? Or a parallel build issue? Try to find the same issue on upstream.


Investigate using Globus Auth with AWS API Gateway

As a Developer, we are considering making Garden serverless using AWS API Gateway, based on our experiences with the DLHub Service. First, we need to investigate how Globus Auth works with API Gateway, and how achievable that is
Assumptions:

I know how to use AWS API Gateway
I know how to use Globus Auth
Ben Galewsky has done this before, and could provide some guidance
I could create a simple demo/flow/proof of concept if desired

Acceptance Criteria
Given I have presented my findings to the team (in the form of a simple demo and/or 1-3 slides, whichever I find most communicative), we can all determine:

What's easy about using Globus Auth with API Gateway
What are painpoints or potential points of failure with using Globus Auth with API Gateway
Whether or not we need to pursue other solutions

Good q! We had assigned this to @ericblau, and I didn’t want to add too much to his plate — @ericblau what’s your capacity like for adding a little end to end demo like Ben G mentioned?

We could also, of course, assign to someone else

I've already been working on one.  Interestingly, the process for Oauth2 authorizers appears to be different for HTTP APIs vs REST APIs (in the Amazon taxonomy).  Would you like me to present on both, or is it already known which path Garden might be most interested in?

Turns out the "simple" integrated oauth for the confusingly named AWS HTTP APIs doesn't help us, as Globus Auth only has JWTs for the id_token, not the access token.  So we will need to use a lambda authorizer in either case, which means that, at least for purposes of Globus Auth authentication, it doesn't matter if the gateway is an HTTP or a REST API.

Gotcha, thanks for investigating Eric! Definitely confusing

Do we want to make this end with just suggestions, or could it result is some useful code? A running gateway in AWS with some simple REST endpoint that just says "hello world" to an authenticated user.

Just updated the acceptance criteria

Gist for the client for the demo
Demo is up and running in Globus AWS (I don't think I have access to GlobusLabs AWS).  It is using Hello World example REST api code from Amazon, and a custom Globus Auth lambda authorizer that I wrote, based on some example code from @BenGalewsky

The Authorizer itself can be found at https://github.com/globusonline/GlobusAuthExampleLambdaAuthorizer


Fix tests to use t *testing.T instead of tt *testing.T

Overview
fix test to use t *testing.T instead of tt *testing.T
Description
Addresses https://github.com/TBD54566975/ssi-service/issues/634
How Has This Been Tested?

[ ] Test A (e.g. Test A - New test that does ... run in ...)
[ ] Test B

Checklist
Before submitting this PR, please make sure:

[ ] I have read the CONTRIBUTING document.
[ ] My code is consistent with the rest of the project
[ ] I have tagged the relevant reviewers and/or interested parties
[ ] I have updated the READMEs and other documentation of affected packages

References
Please list relevant documentation (e.g. tech specs, articles, follow up or related work) relevant to this change, and note if the documentation has been updated.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (11e9266) 25.51% compared to head (cb7d150) 25.51%.
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #717   +/-   ##
=======================================
  Coverage   25.51%   25.51%
=======================================
  Files          56       56
  Lines        6309     6309
=======================================
  Hits         1610     1610
  Misses       4421     4421
  Partials      278      278

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Contract tests

We should try to improve the contract test coverage to 95%+. This is a good metric we can track. Our contract coverage is ~40% right now.

Closing in favor of #163


fix the problem that some config in profiles.default may not take effect

What problem does this PR solve?
Issue Number: close #5574
Problem Summary: The config item in profiles.default may not take effect because some service initialized before load profiles.default value from config file.
What is changed and how it works?
Change the initialization order of some services: BackgroundPool, BlockableBackgroundPool and GlobalStoragePool
Check List
Tests

[ ] Unit test
[ ] Integration test
[x] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/merge

/run-all-tests

/merge

/hold

/unhold

/rebuild

/rebuild

/rebuild

/merge

/merge


make this change to make sure relativePath won't become undefined

make this change to make sure relativePath won't become undefined

The code change is to pass E2E test for routerlicious
The pull request break the e2e test for routerlicious: https://github.com/microsoft/FluidFramework/commit/3455abf46cba386c8c4ca629768fe44e5fff60f1#diff-709854e39c4ae051761dcc30a70c61d4628b2737d2ac307f277d58ffe259bf0e
It seems that odsp and routerlicious have different url format which caused relativePath variable be null for routerlicious url.
The code change for this pull request is to make sure relativePath passing to resolverHelper won't be undefined.


Cannot re-export name that is not defined in the module.

Short description of the problem:
I just created a new project in Ionic 2 typescript and sidemenu as template
Everytime I run ionic serve I receive this not blocking error:

ERROR in [default] /.../scaffold-ionic/node_modules/angular2/src/facade/promise.d.ts:1:9
Cannot re-export name that is not defined in the module.

Steps to reproduce:

ionic start scaffold-ionic sidemenu --v2 --ts
ionic serve

Here the complete flow
∆ Compiling and bundling with Webpack...
√ Using your webpack.config.js file
∆ Compiling Sass to CSS
√ Matching patterns: app/theme/app.+(ios|md|wp).scss
∆ Copying fonts
√ Matching patterns: node_modules/ionic-angular/fonts/**/*.+(ttf|woff|woff2)
∆ Copying HTML
√ Matching patterns: app/**/*.html
√ HTML copied to www/build
√ Sass compilation complete
√ Fonts copied to www/build/fonts
Hash: 4d8afbdec4626d5a657f
Version: webpack 1.12.11
Time: 5935ms
Asset     Size  Chunks             Chunk Names
app.bundle.js  2.73 MB       0  [emitted]  main
[0] multi main 64 bytes {0} [built]
+ 363 hidden modules
ERROR in [default] /.../scaffold-ionic/node_modules/angular2/src/facade/promise.d.ts:1:9
Cannot re-export name that is not defined in the module.
√ Webpack complete
∆ Starting dev server.
√ Running live reload server: http://localhost:35729
√ Running dev server:  http://localhost:8100
√ Watching: 0=www/build//*.html, 1=www/build//.js, 2=www/build/**/.css
Ionic server commands, enter:
restart or r to restart the client app from the root
goto or g and a url to have the app navigate to the given url
consolelogs or c to enable/disable console log output
serverlogs or s to enable/disable server log output
quit or q to shutdown the server and exit
ionic $

Thanks for opening this issue with us! As this issue has more to do with our CLI than the actual framework I will be moving this issue over to that repo. Please feel free to continue the conversation there! Thanks again!

This issue was moved to driftyco/ionic-cli#849


【论文复现】Deep Image Prior 复现源码及文档规范提交

你好，已经按照邮件要求，把 Deep Image Prior 复现源码及文档规范后提交至此仓库，请查阅。
from：玻尔兹曼之脑的团队
<EMAIL_ADDRESS>

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


multi gpu on lanenet-lane-detection model

您好！我根据您的代码将lanenet-lane-detection模型改为了多GPU版本。但是在训练中发现，val的loss与train时的loss不匹配（val的loss是train时的100~1000倍）。分割的精度train一直在增加，但是val的精度始终超不过0.01。请问这种情况您有遇到过么？代码和您的几乎一样的格式，train与val也是同时进行的。 @cardwing @yujincheng08

这是我train时的代码：
#!/usr/bin/env python3
# -*- coding: utf-8 -*-
# @Time    : 18-5-18 下午7:31
# @Author  : Luo Yao
# @Site    : http://icode.baidu.com/repos/baidu/personal-code/Luoyao
# @File    : train_lanenet.py
# @IDE: PyCharm Community Edition
"""
训练lanenet模型
"""
import argparse
import os
import os.path as ops
import time
import glog as log
import numpy as np
import tensorflow as tf
import sys
sys.path.append(os.path.dirname(os.path.dirname(__file__)))
from config import global_config
from instances_model.lanenet_model import lanenet_merge_model
from data_provider import lanenet_data_processor
CFG = global_config.cfg
def init_args():
    """
    :return:
    """
    parser = argparse.ArgumentParser()
    parser.add_argument('--dataset_dir', type=str, help='The training dataset dir path')
    parser.add_argument('--net', type=str, help='Which base net work to use', default='vgg')
    parser.add_argument('--weights_path', type=str, help='The pretrained weights path')
    return parser.parse_args()
def average_gradients(tower_grads):
    """Calculate the average gradient for each shared variable across all towers.
    Note that this function provides a synchronization point across all towers.
    Args:
      tower_grads: List of lists of (gradient, variable) tuples. The outer list
        is over individual gradients. The inner list is over the gradient
        calculation for each tower.
    Returns:
       List of pairs of (gradient, variable) where the gradient has been averaged
       across all towers.
    """
    average_grads = []
    for grad_and_vars in zip(*tower_grads):
        # Note that each grad_and_vars looks like the following:
        #   ((grad0_gpu0, var0_gpu0), ... , (grad0_gpuN, var0_gpuN))
        grads = []
        for g, _ in grad_and_vars:
            # Add 0 dimension to the gradients to represent the tower.
            expanded_g = tf.expand_dims(g, 0)
            # Append on a 'tower' dimension which we will average over below.
            grads.append(expanded_g)
        # Average over the 'tower' dimension.
        grad = tf.concat(grads, 0)
        grad = tf.reduce_mean(grad, 0)
        # Keep in mind that the Variables are redundant because they are shared
        # across towers. So .. we will just return the first tower's pointer to
        # the Variable.
        v = grad_and_vars[0][1]
        grad_and_var = (grad, v)
        average_grads.append(grad_and_var)
    return average_grads
def forward(batch_queue, net, scope, optimizer=None):
    img_batch, label_instance_batch, label_existence_batch = batch_queue.dequeue()
    compute_ret = net.compute_loss(input_tensor=img_batch, instance_label=label_instance_batch, name='lanenet_model')
    total_loss = compute_ret['total_loss']
    instance_loss = compute_ret['discriminative_loss']
    binary_seg_loss = compute_ret['binary_seg_loss']
    instance_var = compute_ret['loss_var']
    instance_dist = compute_ret['loss_dist']
    accuracy = compute_ret['accuracy']
    accuracy_back = compute_ret['accuracy_back']
    tf.get_variable_scope().reuse_variables()
    if optimizer is not None:
        grads = optimizer.compute_gradients(total_loss)
    else:
        grads = None
    return total_loss, instance_loss, binary_seg_loss, instance_var, instance_dist, accuracy, accuracy_back, grads
def train_net(dataset_dir, weights_path=None, net_flag='vgg'):
    train_dataset_file = ops.join(dataset_dir, 'train_gt_instances.txt')
    val_dataset_file = ops.join(dataset_dir, 'val_gt.txt')
    assert ops.exists(train_dataset_file)
    phase = tf.placeholder(dtype=tf.string, shape=None, name='net_phase')
    train_dataset = lanenet_data_processor.DataSet(train_dataset_file, use_flip=True, use_lighting=True)
    val_dataset = lanenet_data_processor.DataSet(val_dataset_file)
    net = lanenet_merge_model.LaneNet(net_flag=net_flag, phase=phase)
    tower_grads = []
    global_step = tf.Variable(0, trainable=False)
    if CFG.TRAIN.WARMUP:
        rate = CFG.TRAIN.LEARNING_RATE ** (1.0 / CFG.TRAIN.WARMUP_EPOCH)
    else:
        rate = CFG.TRAIN.LEARNING_RATE
    # lr = tf.Variable(rate, trainable=False)
    learning_rate = tf.train.polynomial_decay(rate, global_step,
                                              CFG.TRAIN.EPOCHS, end_learning_rate=0.00001, power=0.9)
    optimizer = tf.train.MomentumOptimizer(learning_rate=learning_rate, momentum=0.9)
    img, label_instance, label_existence = train_dataset.next_batch(CFG.TRAIN.BATCH_SIZE)
    batch_queue = tf.contrib.slim.prefetch_queue.prefetch_queue(
        [img, label_instance, label_existence], capacity=2 * CFG.TRAIN.GPU_NUM, num_threads=CFG.TRAIN.CPU_NUM)
    val_img, val_label_instance, val_label_existence = val_dataset.next_batch(CFG.TRAIN.VAL_BATCH_SIZE)
    val_batch_queue = tf.contrib.slim.prefetch_queue.prefetch_queue(
        [val_img, val_label_instance, val_label_existence], capacity=2 * CFG.TRAIN.GPU_NUM,
        num_threads=CFG.TRAIN.CPU_NUM)
    with tf.variable_scope(tf.get_variable_scope()):
        for i in range(CFG.TRAIN.GPU_NUM):
            with tf.device('/gpu:%d' % i):
                with tf.name_scope('tower_%d' % i) as scope:
                    total_loss, instance_loss, binary_seg_loss, instance_var, instance_dist, accuracy, accuracy_back, \
                        grad = forward(batch_queue, net, scope, optimizer)
                    tower_grads.append(grad)
                with tf.name_scope('test_%d' % i) as scope:
                    val_op_total_loss, val_op_instance_loss, val_op_binary_seg_loss, val_instance_var, val_instance_dist, val_op_accuracy, \
                        val_op_accuracy_back, _ = forward(val_batch_queue, net, scope)
    grads = average_gradients(tower_grads)
    train_op = optimizer.apply_gradients(grads, global_step=global_step)
    train_cost_time_mean = []
    train_instance_loss_mean = []
    train_existence_loss_mean = []
    train_accuracy_mean = []
    train_accuracy_back_mean = []
    for vv in tf.trainable_variables():
        print('All trainable_variables:', vv)
    saver = tf.train.Saver()
    model_save_dir = 'model/culane_lanenet/culane_scnn'
    if not ops.exists(model_save_dir):
        os.makedirs(model_save_dir)
    train_start_time = time.strftime('%Y-%m-%d-%H-%M-%S', time.localtime(time.time()))
    model_name = 'culane_lanenet_{:s}_{:s}.ckpt'.format(net_flag, str(train_start_time))
    model_save_path = ops.join(model_save_dir, model_name)
    sess_config = tf.ConfigProto(device_count={'GPU': CFG.TRAIN.GPU_NUM}, allow_soft_placement=True)
    sess_config.gpu_options.per_process_gpu_memory_fraction = CFG.TRAIN.GPU_MEMORY_FRACTION
    sess_config.gpu_options.allow_growth = CFG.TRAIN.TF_ALLOW_GROWTH
    sess_config.gpu_options.allocator_type = 'BFC'
    with tf.Session(config=sess_config) as sess:
        with sess.as_default():
            if weights_path is None:
                log.info('Training from scratch')
                init = tf.global_variables_initializer()
                sess.run(init)
            else:
                log.info('Restore model from last model checkpoint {:s}'.format(weights_path))
                saver.restore(sess=sess, save_path=weights_path)
                sess.run(tf.assign(global_step, 0))
            # 加载预训练参数
            if net_flag == 'vgg' and weights_path is None:
                pretrained_weights = np.load(
                    './data/vgg16.npy',
                    encoding='latin1').item()
                for vv in tf.trainable_variables():
                    weights = vv.name.split('/')
                    if len(weights) >= 3 and weights[-3] in pretrained_weights:
                        try:
                            weights_key = weights[-3]
                            weights = pretrained_weights[weights_key][0]
                            _op = tf.assign(vv, weights)
                            sess.run(_op)
                        except Exception as e:
                            continue
        tf.train.start_queue_runners(sess=sess)
        for epoch in range(CFG.TRAIN.EPOCHS):
            t_start = time.time()
            # if CFG.TRAIN.WARMUP and epoch < CFG.TRAIN.WARMUP_EPOCH:
            #     rate = rate ** (epoch + 1)
            #     sess.run(tf.assign(lr, rate))
            _, c, train_accuracy, train_accuracy_back, train_instance_loss, train_binary_seg_loss, train_instance_var, train_instance_dist, train_learning_rate, train_global_step = \
                sess.run([train_op, total_loss, accuracy, accuracy_back, instance_loss, binary_seg_loss, instance_var, instance_dist, learning_rate, global_step],
                         feed_dict={phase: 'train'})
            cost_time = time.time() - t_start
            train_cost_time_mean.append(cost_time)
            train_instance_loss_mean.append(train_instance_loss)
            train_existence_loss_mean.append(train_binary_seg_loss)
            train_accuracy_mean.append(train_accuracy)
            train_accuracy_back_mean.append(train_accuracy_back)
            if epoch % CFG.TRAIN.DISPLAY_STEP == 0:
                print(
                    'Epoch: {:d}({:d}) loss_instance= {:6f} ({:6f}) instance_var={:6f} instance_dist={:6f} loss_segmentation= {:6f} ({:6f}) lr={} accuracy= {:6f} ({:6f}) '
                    'accuracy_back= {:6f} ({:6f}) mean_time= {:5f}s '.format(epoch + 1, train_global_step, train_instance_loss,
                                                                             np.mean(train_instance_loss_mean),
                                                                             train_instance_var, train_instance_dist,
                                                                             train_binary_seg_loss,
                                                                             np.mean(train_existence_loss_mean),
                                                                             train_learning_rate,
                                                                             train_accuracy,
                                                                             np.mean(train_accuracy_mean),
                                                                             train_accuracy_back,
                                                                             np.mean(train_accuracy_back_mean),
                                                                             np.mean(train_cost_time_mean)))
            if epoch % 500 == 0:
                del train_cost_time_mean[:]
                del train_instance_loss_mean[:]
                del train_existence_loss_mean[:]
                del train_accuracy_mean[:]
                del train_accuracy_back_mean[:]
            if epoch % 1000 == 0:
                saver.save(sess=sess, save_path=model_save_path, global_step=epoch)
            if epoch % 10000 != 0 or epoch == 0:
                continue
            val_cost_time_mean = []
            val_instance_loss_mean = []
            val_existence_loss_mean = []
            val_accuracy_mean = []
            val_accuracy_back_mean = []
            for epoch_val in range(int(len(val_dataset) / CFG.TRAIN.VAL_BATCH_SIZE / CFG.TRAIN.GPU_NUM)):
                t_start_val = time.time()
                c_val, val_accuracy, val_accuracy_back, val_instance_loss, val_existence_loss = \
                    sess.run(
                        [val_op_total_loss, val_op_accuracy, val_op_accuracy_back,
                         val_op_instance_loss, val_op_binary_seg_loss],
                        feed_dict={phase: 'test'})
                cost_time_val = time.time() - t_start_val
                val_cost_time_mean.append(cost_time_val)
                val_instance_loss_mean.append(val_instance_loss)
                val_existence_loss_mean.append(val_existence_loss)
                val_accuracy_mean.append(val_accuracy)
                val_accuracy_back_mean.append(val_accuracy_back)
                if epoch_val % 1 == 0:
                    print('Epoch_Val: {:d} loss_ins= {:6f} ({:6f}) '
                          'loss_ext= {:6f} ({:6f}) accuracy= {:6f} ({:6f}) accuracy_back= {:6f} ({:6f}) '
                          'mean_time= {:5f}s '.
                          format(epoch_val + 1, val_instance_loss, np.mean(val_instance_loss_mean), val_existence_loss,
                                 np.mean(val_existence_loss_mean), val_accuracy, np.mean(val_accuracy_mean),
                                 val_accuracy_back, np.mean(val_accuracy_back_mean),
                                 np.mean(val_cost_time_mean)))
            del val_cost_time_mean[:]
            del val_instance_loss_mean[:]
            del val_existence_loss_mean[:]
            del val_accuracy_mean[:]
            del val_accuracy_back_mean[:]
if __name__ == '__main__':
    # init args
    args = init_args()
    # train lanenet
    train_net(args.dataset_dir, args.weights_path, net_flag=args.net)

You can try our code and check if the problem disappears.

@Yc174
您好，请问你在TuSimple上test后，有没有写脚本计算accuracy， fp，fn 呢？目前我也在学习LaneNet，可否加微信指教一下， tommytang930


Use ddev start -y so doesn't stop in prebuild

In ddev v1.17, when it detects a "new" ddev version, it will ask if it can do a poweroff.
We obviously don't want that in prebuild.
So set DDEV_NONINTERACTIVE.

oh! so that is what has been happening with prebuilds tests...

Thank you @rfay


Creepers shake

The creepers shake around when falling, making them nearly impossible to hit.

Should be fixed on 1.17


Authentication failure in safari browser(version- 13.3) and ios mobile devices (version 13.4.1))

Library

<EMAIL_ADDRESS>
Framework
React v16
Description
It is a single-tenant application. The incoming user is authenticated using msal.js. If the user exists in AD, they can access our application.
Security
Is this issue security related?  NO
Regression
Did this behavior work before?  NO
Configuration
const authContext = new UserAgentApplication({
auth: {
clientId: clientId,
authority: https://login.microsoftonline.com/${tenantId},
postLogoutRedirectUri: window.location.origin,
redirectUri: window.location.origin
},
cache: {
cacheLocation: "localStorage",
storeAuthStateInCookie: true
}
});
Reproduction steps
When the code is executed in Safari browser(version 13.1), acquireTokenSilent throws the following error:
ClientAuthError: URL navigated to is https://login.microsoftonline.com//oauth2/v2.0/authorize?response_type=token&scope=openid%20profile%20User.Read&client_id=<client_id>&redirect_uri=<redirect_uri>&state=&nonce=<  ### >&client_info=1&x-client-SKU=MSAL.JS&x-client-Ver=1.3.0&client-request-id=<request_id>&prompt=none&response_mode=fragment, Token renewal operation failed due to timeout.
Expected behavior
The user should be authenticated successfully in safari browser as well.
Browsers
This is a browser specific behaviour. The authentication call fails only in Safari (version 13.1) and mobile iOS devices (version- 13.4.1). It works perfectly in all other browsers.

@divya2603 Unfortunately due to Safari blocking third party cookies, acquireTokenSilent is expected not to work. As a workaround you can either enable third party cookies or call acquireTokenRedirect or acquireTokenPopup. You can read more about this issue here
Additionally, we have a new version of msal, known as<EMAIL_ADDRESS>or msal-browser, which is currently in Public Preview that implements the Auth Code flow which solves this problem by using refresh tokens instead of acquiring tokens using a hidden iframe. You can read more about how this solves the problem here

Closing as this is expected behavior in msal 1.x. Let us know if you have any further questions. Thanks!


Update expressroute-howto-linkvnet-arm.md

Converted important point to a Note

Hi @shchauh, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@ganesr - Please review this proposed change in the public repo.
@shchauh - Thanks for the update - would you be able to update this to use the correct markdown style?
> [AZURE.NOTE] To complete this tutorial...

@tysonn change looks good. We can sign off once the style is fixed. I couldn't fix the files. Once Shailendra fixes it I will sign off.

Contributor made update in another PR.


Check classification result in "make test"

Make tests/test.sh check the result. As the test itself is written in shell, just use shell ways to check it - instead of actually parsing the XML.
The classification check also assumes that the classification results are sorted by descending probabilities, i.e. that the result with highest probability is listed first.
Fixes #3.

@seuretm This needs to be updated when you upload a model with changed class names, unless fraktur remains fraktur.


RC car example with OpenCV UI

A new example is needed that allows controlling the robot as an RC car with OpenCV UI.
It should provide functionality, similar to the rc.py example but also display a real-time image from the robot camera.

Try this https://github.com/RecognitionDesigns/Vector_Object_Prediction_Recollection?fbclid=IwAR15nHwgUijuc6cCMhTV2Dg6T-6LsXLDvZMX592L8ldNteUGpF0bZlCLN-M

Vector to Vector recognition :
https://github.com/RecognitionDesigns/Vector-to-Vector-recognition

https://github.com/RecognitionDesigns/Rock-Paper-Scissors-Vector-Game

The links are not directly related to the RC car example.
They are more appropriate for #35 or a more general approach for object recognition using CNNs.
The links don't seem very useful though. These are very basic experiments, the models, weights, or data sets do not seem to be shared.


Misc updates after rename

The crate has been renamed to ftdi-embedded-hal. Update all the links
and examples to use the new name and location.
Signed-off-by: Sergey Matyukevich<EMAIL_ADDRESS>

Links in CHANGELOG.md need to change as well, other than that looks good.
Edit: I see the git tags were not preserved, is the intent to start over from v0.1.0 or continue from the ftd2xx-embedded-hal version?

I am fine with pushing existing tags and going further from 0.9.2 unless this approach breaks something on crates.io.

Links in CHANGELOG.md need to change as well, other than that looks good.
Edit: I see the git tags were not preserved, is the intent to start over from v0.1.0 or continue from the ftd2xx-embedded-hal version?

I am fine with pushing existing tags and going further from 0.9.2 unless this approach breaks something on crates.io.

Sounds good to me.
This wont break crates.io as far as I know.  The stm32-rs repository does abnormal version jumps all the time.

I mean possible crates.io breakage due to new name, not new version. But lets see how it goes. If it is not smooth enough, we can start over from v0.1.0 adding links to your previous releases.

I mean possible crates.io breakage due to new name, not new version. But lets see how it goes. If it is not smooth enough, we can start over from v0.1.0 adding links to your previous releases.

Changing the name is not possible crates.io, a new crate will have to be published under this name.
Since adding support for libftdi will result in a breaking change anyway I think a name change is fine.


fix: try out proposed fix for #3245

Ah, we need at least a congruence theorem to descend into the condition, but we don't want to descend into the branches. Trying again.


[BUG] Unable to use the generate addon script to create RKE config yaml for K3s csi and cloud provider

Describe the bug

According to document, we use generate addon config script to install cloud provider and csi driver on Rancher K3s cluster

cloud provider: https://docs.harvesterhci.io/next/rancher/cloud-provider
csi driver: https://docs.harvesterhci.io/next/rancher/csi-driver

Create csi driver and cloud provider both display the same error:
Extracting ca.crt from secret...error: resource name may not be empty
CSI driver
When we use the csi driver Generate addon configuration to create RKE config, it display error
Extracting ca.crt from secret...error: resource name may not be empty

davidtclin@localhost:~/Documents/Harvester/tools/csi_driver> ./generate_addon.sh k3s-1244-csi default
Creating target directory to hold files in ./tmp/kube...done
Creating a service account in default namespace: k3s-1244-csi
serviceaccount/k3s-1244-csi created

Creating a rolebinding in default namespace: k3s-1244-csi
rolebinding.rbac.authorization.k8s.io/k3s-1244-csi created

Getting secret of service account k3s-1244-csi on default
Secret name:

Extracting ca.crt from secret...error: resource name may not be empty

Cloud provider
When we use the cloud provider Generate addon configuration to create RKE config, it display error
Extracting ca.crt from secret...error: resource name may not be empty

davidtclin@localhost:~/Documents/Harvester/tools/cloud_provider> ./generate_addon.sh k3s-1244-ccm default
Creating target directory to hold files in ./tmp/kube...done
Creating a service account in default namespace: k3s-1244-ccm
W1014 16:39:21.902226    5887 helpers.go:535] --dry-run is deprecated and can be replaced with --dry-run=client.
serviceaccount/k3s-1244-ccm created

Creating a role in default namespace: harvester-cloud-provider
role.rbac.authorization.k8s.io/harvester-cloud-provider created

Creating a rolebinding in default namespace: k3s-1244-ccm
W1014 16:39:23.971389    5971 helpers.go:535] --dry-run is deprecated and can be replaced with --dry-run=client.
rolebinding.rbac.authorization.k8s.io/k3s-1244-ccm created

Getting secret of service account k3s-1244-ccm on default
Secret name:

Extracting ca.crt from secret...error: resource name may not be empty

To Reproduce
Steps to reproduce the behavior:
CSI driver

Create a K3s cluster, select v1.24.4+k3s1
Add the following user data

password: 123456
chpasswd: { expire: False }
ssh_pwauth: True

Create K3s cluster
Download the Generate addon configuration for csi driver
ssh to harvester node 1
Execute cat /etc/rancher/rke2/rke2.yaml
change the server value from https://<IP_ADDRESS>:6443 to your node1 IP
Copy the kubeconfig and add into your local ~/.kube/config file
Generate K3s kubeconfig by running generate addon script
 ./deploy/generate_addon.sh <k3s cluster name> <namespace>
e.g ./generate_addon.sh k3s-csi-cluster default

Cloud provider

Create a K3s cluster, select v1.24.4+k3s1
Click the Edit yaml button
Set disable-cloud-provider: true to disable default k3s cloud provider.
Add cloud-provider=external to use harvester cloud provider.
Create K3s cluster
Download the Generate addon configuration for cloud provider
Download Harvester kubeconfig and add into your local ~/.kube/config file
Generate K3s kubeconfig by running generate addon script
 ./deploy/generate_addon.sh <k3s cluster name> <namespace>
e.g ./generate_addon.sh k3s-focal-cloud-provider default

Expected behavior

Can create RKE config for creating cloud provider and csi driver RKE config yaml as stated in document
Support bundle

supportbundle_21db8038-6f50-4d91-a5b1-5b1e42de44d3_2022-10-14T08-51-46Z.zip
K3s service log
k3s_service.log
Environment

Harvester ISO version: master-0a9538a1-head (10/14)
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): 1 node Harvester on local kvm machine
Rancher version: v2.6.9-rc4

Additional context
Add any other context about the problem here.
harv1014:~ # kubectl get sa k3s-1244-ccm default -o yaml
apiVersion: v1
items:
- apiVersion: v1
  kind: ServiceAccount
  metadata:
    annotations:
      kubectl.kubernetes.io/last-applied-configuration: |
        {"apiVersion":"v1","kind":"ServiceAccount","metadata":{"annotations":{},"creationTimestamp":null,"name":"k3s-1244-ccm","namespace":"default"}}
    creationTimestamp: "2022-10-14T08:39:23Z"
    name: k3s-1244-ccm
    namespace: default
    resourceVersion: "44677"
    uid: 6df8c379-a1ed-45c0-a768-e5cb20afc0f5
- apiVersion: v1
  kind: ServiceAccount
  metadata:
    creationTimestamp: "2022-10-14T07:55:32Z"
    name: default
    namespace: default
    resourceVersion: "517"
    uid: 003463c2-6e7b-43d4-88ec-9f7d86c4570a
kind: List
metadata:
  resourceVersion: ""

Verified fixed on the latest cloud provider and csi driver generate script on Harvester v1.1.0-rc3 with Rancher v2.6.9-rc6. Close this issue.
Result
Use the latest generate addon script of the following:
We can correctly generate the related RKE config and proceed to install Harvester cloud provider and csi driver on K3s cluster

cloud provider addon
csi driver addon

Then we can successfully install Harvester csi driver 0.1.14 on K3s cluster

But failed to install Harvester cloud provider 0.1.13 on K3s cluster
We will track this issue on https://github.com/harvester/harvester/issues/2998

Test Information

Test Environment: 1 node Harvester local kvm machine
Harvester version: v1.1.0-rc3
Rancher version: v2.6.9-rc6

Verify Steps
CSI driver

Create a K3s cluster, select v1.24.4+k3s1
Add the following user data

password: 123456
chpasswd: { expire: False }
ssh_pwauth: True

Create K3s cluster
Download the Generate addon configuration for csi driver
ssh to harvester node 1
Execute cat /etc/rancher/rke2/rke2.yaml
change the server value from https://<IP_ADDRESS>:6443 to your node1 IP
Copy the kubeconfig and add into your local ~/.kube/config file
Generate K3s kubeconfig by running generate addon script
 ./deploy/generate_addon.sh <k3s cluster name> <namespace>
Copy the generated RKE2 config
ssh to the K3s cluster VM
Add the generated yaml content to /var/lib/rancher/rke2/etc/config-files/cloud-provider-config

root@k3s-csi-v1244-pool1-7898ed01-wgpzk:/var/lib/rancher/rke2/etc/config-files# pwd
/var/lib/rancher/rke2/etc/config-files
root@k3s-csi-v1244-pool1-7898ed01-wgpzk:/var/lib/rancher/rke2/etc/config-files# ls
cloud-provider-config

Access K3s cluster
Go to Apps -> Chart
Search Harvester csi driver
Use the default cloud config file path during installation

18 . Finish the installation

Cloud provider

Create a K3s cluster, select v1.24.4+k3s1
Click the Edit yaml button
Set disable-cloud-provider: true to disable default k3s cloud provider.
Add cloud-provider=external to use harvester cloud provider.
Create K3s cluster
Download the Generate addon configuration for cloud provider
Execute cat /etc/rancher/rke2/rke2.yaml
change the server value from https://<IP_ADDRESS>:6443 to your node1 IP
Copy the kubeconfig and add into your local ~/.kube/config file
Generate K3s kubeconfig by running generate addon script
 ./deploy/generate_addon.sh <k3s cluster name> <namespace>
Copy the generated RKE2 config
ssh to the K3s cluster VM
Add the generated yaml content to /etc/kubernetes/cloud-config
Access K3s cluster
Go to Apps -> Chart
Search Harvester cloud provider
Use the default cloud config file path during installation

18 . Finish the installation


BUG: pip install -e . dinged for not using hashes, but it can't

Describe the bug
My project (https://deps.dev/pypi/coverage) gets a warning about pinned dependencies:
Warn: pipCommand not pinned by hash: .github/workflows/coverage.yml:114

The line in question is:
python -m pip install -e .

I think scorecard is looking for the --require-hashes option, but it's not allowed with -e.  This is what happens when I try:
+ python -m pip install --require-hashes -e .
Obtaining file:///home/runner/work/coveragepy/coveragepy
ERROR: The editable requirement file:///home/runner/work/coveragepy/coveragepy cannot be installed when requiring hashes, because there is no single file to hash.

Thanks for the report.  So I think the fix is for scorecard to verify that no -e local/path is used in the command. Is that correct?
-e also seems to accept a remote URL as input, which is harder to verify.
Do you think ignoring -e local/path is enough?

Definitely ignoring -e local/path will help.  Why not also allow a URL?

I don't know how the URL works. Does pip fetch the URL and search for a requirement.txt? Or does it simply take the URL as being the source code? Is the source code guaranteed to be immutable (which is the property we're looking for)?

The local file path or the URL are the same: they are a place to get an installable directory of files.
A difference is that the URL could include a SHA that would make it immutable.  So perhaps the rule should be a local file path, or a URL with a SHA?

This seems to be the best docs: https://pip.pypa.io/en/stable/topics/vcs-support/
Some syntaxes to support (shell quoting may or may not be needed):
pip install "MyProject @ git+https://git.example.com/MyProject.git@da39a3ee5e6b4b0d3255bfef95601890afd80709"
pip install "MyProject[extra1,extra2]@git+https://git.example.com/MyProject.git@da39a3ee5e6b4b0d3255bfef95601890afd80709"
pip install git+https://git.example.com/MyProject.git@da39a3ee5e6b4b0d3255bfef95601890afd80709#egg=MyProject
pip install<EMAIL_ADDRESS>
Are shortened hashes OK?
pip install git+https://git.example.com/MyProject.git@da39a3ee5e#egg=MyProject

Maybe the simplest solution is to match against @[a-fA-F0-9]{40} and forget the rest of the syntax possibilities?

Sure, that couldn't hurt.  Ping me on the change, I would like to understand better how this code works.

Actually if you want to take a shot at it, feel free to try it out. Code to change is https://github.com/ossf/scorecard/blob/main/checks/raw/shell_download_validate.go#L469
You can add tests in https://github.com/ossf/scorecard/blob/main/checks/raw/pinned_dependencies_test.go#L550, https://github.com/ossf/scorecard/blob/main/checks/raw/pinned_dependencies_test.go#L710 https://github.com/ossf/scorecard/blob/main/checks/raw/pinned_dependencies_test.go#L813
https://github.com/ossf/scorecard/blob/main/checks/raw/pinned_dependencies_test.go#L855
https://github.com/ossf/scorecard/blob/main/checks/raw/pinned_dependencies_test.go#L935
https://github.com/ossf/scorecard/blob/main/checks/raw/pinned_dependencies_test.go#L983

Thanks, but I've never written Go, so you should not wait for a pull request from me... :)


Add Raku support

Hi there,
What is the status of Raku support in highlight.js package?
Is it planned?
Raku is a mature production ready language and would love to see this library support it.

+1 for Perl 6 support.

Is anyone volunteering to write the syntax for it and maintain it?  That's all we need to get the ball rolling now that languages are simply external repos.

The core team doesn't have a plan for ongoing development of new syntaxes (typically it's all we can do to keep up with support, issues, PRs, etc) - building support for new languages is all up to the larger community.  If you'd really like to see this language, perhaps you know a developer who'd be willing to put in the time to develop and maintain a grammar for it?
If someone steps up to the plate it'd be great to have a Perl 6 grammar! :-)

Rather than leave these issues open to languish forever (as we have in the past) we're going to start closing them (to clean up the issues list).
I've moved this request to the wish list:
https://github.com/highlightjs/highlight.js/wiki/Grammar-Requests

I'm willing to start the ball rolling.
I've put in a separate request for a repo.

finanalys: not sure if joshgoebel will see this as he has marked it closed


feat: New Module avm/ptn/deployment-script/import-image-to-acr

Description
Adds a pattern module to deploy a container image to an Azure Container Registry. The max text shows an example on how to use it with a private Container Registry.
Pipeline Reference

Pipeline

Type of Change

[x] Update to CI Environment or utilities (Non-module affecting changes)
[x] Azure Verified Module updates:

[ ] Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
[ ] Breaking changes and I have bumped the MAJOR version in version.json.
[x] Update to documentation

Checklist

[x] I'm sure there are no other open Pull Requests for the same update/change
[x] I have run Set-AVMModule locally to generate the supporting module files.
[x] My corresponding pipelines / checks run clean and green without any errors or warnings

Do we have an idea when the team will be fixed by adding the repo?

Do we have an idea when the team will be fixed by adding the repo?

@ReneHezser, to clarify, to proceed with this PR, 2 things need to happen:

The GH teams you created need to be added to their respective parents, as per SNFR20. This is a 2-way handshake that needs to be initiated by the module owner (you in this case). Once you initiated the assignment of these 2 teams to their parents, I'll approve them on the parent teams' side.
The module's record needs to be onboarded to the MAR manifest. We have a pending PR; I hope the MAR team will approve it soon (in the coming days).

Hi @matebarabas
Finally, I could add the parent groups. There were some issues that prevented saving before ¯\(ツ)/¯

The GH teams you created need to be added to their respective parents, as per SNFR20. This is a 2-way handshake that needs to be initiated by the module owner (you in this case). Once you initiated the assignment of these 2 teams to their parents, I'll approve them on the parent teams' side.

This is now done (my part).

@eriqua are we still waiting for external changes, or can this PR be merged now?

@eriqua are we still waiting for external changes, or can this PR be merged now?

@eriqua, there were 2 dependencies:

I confirmed the MCR manifest publication, here
René confirmed the GH team assignments, here

I think this should be good to go now.

@eriqua are we still waiting for external changes, or can this PR be merged now?

@eriqua, there were 2 dependencies:

I confirmed the MCR manifest publication, here
René confirmed the GH team assignments, here

I think this should be good to go now.

@ReneHezser @matebarabas I've resolved my comments and removed labels which are not applicable anymore.
The module part still needs review though and it's free to be assigned

Hey @AlexanderSehr. Thanks for the great review. I've changed a lot (e.g. leveraging the existing deployment-script modul).

Hey @ReneHezser,
just finished the re-review. I added a few more comments and resolved most others. 'Most' because a few are yet to be addressed. Beware that GitHub likes to 'hide' them when to many entries hit the PR's history. You then have to expand the history manually so see everything again.

Hey @ReneHezser, aside the inline script which I still dread (but won't block) the PR looks good to me. Once the workflow works (there seems to be some issue) I'm happy to approve 💪
Thanks. I'd go for the script, if it would work. But I spent too much time troubleshooting and think for now I won't touch it anymore.
The test is driving me crazy now, as the pipeline fails, but all my test-deployments work 🙄

The pipeline is green 🥳