Update podman to 3.3.1

Tool name
podman
Tool license
Apache
Add or update?

[ ] Add
[X] Update

Desired version
3.3.1 https://github.com/containers/podman/releases/tag/v3.3.1
Approximate size
No response
Brief description of tool
Please update podman to v3.3.1 to resolve a bug in v3.2.3 which causes backwards-compatibility issues for users pulling images from Docker image storage.
https://github.com/containers/podman/issues/10998
https://github.com/redhat-actions/push-to-registry/issues/42
URL for tool's homepage
No response
Provide a basic test case to validate the tool's functionality.
No response
Virtual environments affected

[ ] Ubuntu 16.04
[ ] Ubuntu 18.04
[X] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11
[ ] Windows Server 2016
[ ] Windows Server 2019
[ ] Windows Server 2022

Can this tool be installed during the build?
No response
Tool installation time in runtime
No response
Are you willing to submit a PR?
No response

Hello @tetchel,
Currently, we install podman according to the podman documentation for Ubuntu, however the latest available version in the repository is 3.2.3, it seems there is some discrepancy between GitHub podman versioning and Ubuntu's repository.
We will investigate the issue.

@lsm5, Hey, Lokesh
We use download.opensuse.org/ [current version in the repo is 3.2.3] repo to install podman buildah skopeo  in the container.sh script as the recommendation from https://podman.io/getting-started/installation help.  As a packer maintainer could you update package version to 3.3.1 and help us and your college @tetchel to fix the issue?
Package: podman
Maintainer: Lokesh Mandvekar<EMAIL_ADDRESS>
Buildah, Podman and Skopeo ONLY from EITHER the Kubic repo OR the official Ubuntu repos. Mixing and matching may lead to unpredictable situations including installation conflicts.

@al-cheb I'll update the kubic package. Btw, any chance you could switch to Ubuntu 21.04? That would have podman and buildah in the default repos itself.

@al-cheb I'll update the kubic package. Btw, any chance you could switch to Ubuntu 21.04? That would have podman and buildah in the default repos itself.

err, never mind, I do recall sometime back you mentioned you'd only switch from one LTS to another.

Just sent podman v3.3.1 update to Kubic, give it maybe an hour to complete. https://build.opensuse.org/package/show/devel:kubic:libcontainers:stable/podman . Let me know if any other packages need changes.

@lsm5, Many thanks for the help. I will generate a test image build and let you know.

@tetchel , We are planning to start a new image rollout next week.
jobs:
  build:
    name: Build
    runs-on: ubuntu-latest
    steps:
      - name: update podman
        run: |
          source /etc/os-release
          REPO_URL="https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable"
          sudo sh -c "echo 'deb ${REPO_URL}/x${NAME}_${VERSION_ID}/ /' > /etc/apt/sources.list.d/devel:kubic:libcontainers:stable.list"
          wget -qnv https://download.opensuse.org/repositories/devel:kubic:libcontainers:stable/x${NAME}_${VERSION_ID}/Release.key -O Release.key
          sudo apt-key add Release.key
          sudo apt-get update -qq
          sudo apt-get -qq -y install podman buildah skopeo
      - run: podman -v

The Ubuntu Server 20.04 with podman 3.3.1  have been deployed.


cmd/compile: improve code generation for math.Abs

From the thread,
"Pure Go math.Abs outperforms assembly version"
https://groups.google.com/forum/#!topic/golang-dev/nP5mWvwAXZo
It was noted that the code generation for
func Abs(x float64) float64 {
        return Float64frombits(Float64bits(x) &^ (1 << 63))
}

is not ideal:
@randall77 wrote:
Current assembly:

	MOVQ   $(1<<63), BX
	MOVQ   BX, X0 // movsd $(-0.0), x0
	MOVSD  x+0(FP), X1
	ANDNPD X1, X0
	MOVSD  X0, ret+8(FP)
	RET

Generated by the compiler from Russ' example:

	0x0000 00000 (abs.go:5)	SUBQ	$16, SP
	0x0004 00004 (abs.go:5)	XORPS	X0, X0
	0x0007 00007 (abs.go:6)	MOVSD	"".x+24(FP), X0
	0x000d 00013 (abs.go:6)	MOVSD	X0, math.f·2(SP)
	0x0012 00018 (abs.go:6)	LEAQ	math.f·2(SP), BX
	0x0016 00022 (abs.go:6)	MOVQ	(BX), BX
	0x0019 00025 (abs.go:6)	MOVQ	$9223372036854775807, BP
	0x0023 00035 (abs.go:6)	ANDQ	BP, BX
	0x0026 00038 (abs.go:6)	MOVQ	BX, math.b·2+8(SP)
	0x002b 00043 (abs.go:6)	XORPS	X0, X0
	0x002e 00046 (abs.go:6)	LEAQ	math.b·2+8(SP), BX
	0x0033 00051 (abs.go:6)	MOVSD	(BX), X0
	0x0037 00055 (abs.go:6)	MOVSD	X0, "".~r1+32(FP)
	0x003d 00061 (abs.go:6)	ADDQ	$16, SP
	0x0041 00065 (abs.go:6)	RET

...

SSA:
	0x0000 00000 (abs.go:5)	SUBQ	$16, SP
	0x0004 00004 (abs.go:5)	MOVQ	$0, "".~r1+32(FP)
	0x000d 00013 (abs.go:5)	MOVSD	"".x+16(SP), X0
	0x0013 00019 (abs.go:6)	MOVSD	X0, math.f·2(SP)
	0x0018 00024 (abs.go:6)	MOVQ	math.f·2(SP), AX
	0x001c 00028 (abs.go:6)	MOVQ	$9223372036854775807, CX
	0x0026 00038 (abs.go:6)	ANDQ	CX, AX
	0x0029 00041 (abs.go:6)	MOVQ	AX, math.b·2+8(SP)
	0x002e 00046 (abs.go:6)	MOVSD	math.b·2+8(SP), X0
	0x0034 00052 (abs.go:6)	MOVSD	X0, "".~r1+32(FP)
	0x003a 00058 (abs.go:6)	ADDQ	$16, SP
	0x003e 00062 (abs.go:6)	RET

better hand-written code:
	MOVQ   x+0(FP), AX
	SHLQ   $1, AX
	SHRQ   $1, AX
	MOVQ   AX, ret+8(FP)
	RET

This is bug about improving it.

Mostly the problem is about getting rid of the stores.
Step 1 would be an SSA rule that recognizes that a store followed by a load from the same address can short-circuit the store and use the store's argument directly instead of the load.
Step 2 would be to recognize that stores to auto variables that are never read again can be dropped.
Step 3 is to replace the and with two shifts.

Fixed by https://golang.org/cl/19485.

Turns out CL 19485 is not enough, see discussion on the CL.

@randall77, not sure whether you're continuing your intrinsification crusade, but maybe the popular funcs at least in math are candidates.
(Reminded after seeing @mundaym's https://go-review.googlesource.com/27827 and the TODO in https://golang.org/src/math/abs.go?s=278:305#L2:
    12	func Abs(x float64) float64 {
    13		// TODO: once golang.org/issue/13095 is fixed, change this to:
    14		// return Float64frombits(Float64bits(x) &^ (1 << 63))
    15		// But for now, this generates better code and can also be inlined:
    16		if x < 0 {
    17			return -x
    18		}
    19		if x == 0 {
    20			return 0 // return correctly abs(-0)
    21		}
    22		return x
    23	}

I think I will continue intrinsification to sync/atomic, but probably stop there.  It feels wrong to intrinsify something that's easily writeable in Go.  And I still have hope for doing this more generically.


Make Runtime api same as kubernetes/pkg/kubelet/api.RuntimeService

And also use k8s util ExitError as wrapper for exitCode.
This PR will help make support multiple runtime easier.
Signed-off-by: Crazykev<EMAIL_ADDRESS>

This change is

LGTM


FFmpeg exited with code 1 as no temp folder was created by default.

I downloaded the repo and after running the app, whenever I paste any link and click on the button the link appears in the list and it keeps loading.
I then learnt that the error was that there wasn't any temp folder created. After I created the folder myself, it ran smoothly. Is this a problem?
Debug: internal, implementation, error
Error: Uncaught error: ffmpeg exited with code 1: /home/arunvv53999/myimages/ytdl-webserver-master/public/temp/Train - Hey, Soul Sister.mp3: No such file or directory

Closed by #23.


[Question]: Does it support using kuberay to run a super large model with multiple pods

Your current environment
Does it support using kuberay to run a super large model with multiple pods ?
Model Input Dumps
No response
🐛 Describe the bug
This is a Question!
Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

duplicate https://github.com/vllm-project/vllm/issues/8402


Tags - Background report changes to Tags page after clicking Custom tag name in RHP

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.41-2
Reproducible in staging?: Y
Reproducible in production?: N/A Unable to check
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause - Internal Team
Action Performed:
Precondition:

User is logged in to two devices
Workspace has tags

Go to staging.new.expensify.com
[Device A] Go to workspace chat
[Device A] Click + > Submit expense > Manual
[Device A] Proceed to confirmation page and click Tag
[Device B] Go to workspace settings > Tags
[Device B] Disable all tags
[Device A] Click Edit tags
[Device A] Click Settings > Custom tag name

Expected Result:
The report in the background will remain after clicking Custom tag name
Actual Result:
The report in the background changes to Tags page after clicking Custom tag name
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/user-attachments/assets/ffdcd5fd-95ab-47fb-a28b-89238ffd7c5c
View all open jobs on GitHub

Looks pretty NAB to me

Proposal
Please re-state the problem that we are trying to solve in this issue.
Tags - Background report changes to Tags page after clicking Custom tag name in RHP
What is the root cause of that problem?
We're not passing the backTo param when navigating to the Custom tag name page
https://github.com/Expensify/App/blob/3047c1baa21f47825f5c1ffd652184341dd22256/src/pages/workspace/tags/WorkspaceTagsSettingsPage.tsx#L85
https://github.com/Expensify/App/blob/3047c1baa21f47825f5c1ffd652184341dd22256/src/ROUTES.ts#L847-L850
And same when navigating to the Settings page
https://github.com/Expensify/App/blob/3047c1baa21f47825f5c1ffd652184341dd22256/src/pages/workspace/tags/WorkspaceTagsPage.tsx#L174-L176
https://github.com/Expensify/App/blob/3047c1baa21f47825f5c1ffd652184341dd22256/src/ROUTES.ts#L843-L846
What changes do you think we should make in order to solve the problem?
We can add the backTo param inside the getRoute function and pass the backTo param by using route.params.backTo
WORKSPACE_TAGS_SETTINGS: {
    route: 'settings/workspaces/:policyID/tags/settings',
    getRoute: (policyID: string, backTo?: string) => getUrlWithBackToParam(`settings/workspaces/${policyID}/tags/settings` as const, backTo),
},
WORKSPACE_EDIT_TAGS: {
    route: 'settings/workspaces/:policyID/tags/:orderWeight/edit',
    getRoute: (policyID: string, orderWeight: number, backTo?: string) => getUrlWithBackToParam(`settings/workspaces/${policyID}/tags/${orderWeight}/edit` as const, backTo),
},

WorkspaceTagsPage.tsx when navigating to Settings page
const backTo = route.params.backTo;
const navigateToTagsSettings = () => {
    Navigation.navigate(ROUTES.WORKSPACE_TAGS_SETTINGS.getRoute(policyID, backTo));
};

// ...types for route.params
[SCREENS.WORKSPACE.TAGS]: {
    policyID: string;
    backTo?: Routes;
};

And same for WorkspaceTagsSettingsPage when navigating to Custom tag name page
<MenuItemWithTopDescription
    title={policyTagLists[0]?.name}
    description={translate(`workspace.tags.customTagName`)}
    onPress={() => Navigation.navigate(ROUTES.WORKSPACE_EDIT_TAGS.getRoute(policyID, policyTagLists[0].orderWeight, backTo))}
    shouldShowRightIcon
/>

Result
https://github.com/user-attachments/assets/ace8973c-9aed-4812-93d5-a3b78291568b
What alternative solutions did you explore? (Optional)

What does NAB mean? I assume this is internal? @stitesExpensify

@Christinadobrzyn NAB stands for Not a blocker

Proposal
Please re-state the problem that we are trying to solve in this issue.
The report in the background changes to Tags page after clicking Custom tag name
What is the root cause of that problem?

We have logic to push a new full screen navigator to the stacks if the RHN is in FULL_SCREEN_TO_RHP_MAPPING list:

https://github.com/Expensify/App/blob/d18766580c7e35e439ff933f3097366e36c6ceca/src/libs/Navigation/linkingConfig/getAdaptedStateFromPath.ts#L146-L153

When we click on "Custom tag name", the custom tag name screen is in FULL_SCREEN_TO_RHP_MAPPING:

https://github.com/Expensify/App/blob/d18766580c7e35e439ff933f3097366e36c6ceca/src/libs/Navigation/linkingConfig/FULL_SCREEN_TO_RHP_MAPPING.ts#L134
hence we push a new full screen navigator to stacks.
What changes do you think we should make in order to solve the problem?

In general, we should add a backTo param to the route when we click "Custom tag name". With this, in:

https://github.com/Expensify/App/blob/d18766580c7e35e439ff933f3097366e36c6ceca/src/libs/Navigation/linkingConfig/getAdaptedStateFromPath.ts#L112
logic:
https://github.com/Expensify/App/blob/d18766580c7e35e439ff933f3097366e36c6ceca/src/libs/Navigation/linkingConfig/getAdaptedStateFromPath.ts#L113-L114
is called instead of pushing a new full screen navigator to stacks:
https://github.com/Expensify/App/blob/d18766580c7e35e439ff933f3097366e36c6ceca/src/libs/Navigation/linkingConfig/getAdaptedStateFromPath.ts#L146-L147

In detail:

First, update the getRoute function so that it can receive the additional backTo param:

https://github.com/Expensify/App/blob/d18766580c7e35e439ff933f3097366e36c6ceca/src/ROUTES.ts#L843-L850

Then, update:

https://github.com/Expensify/App/blob/d18766580c7e35e439ff933f3097366e36c6ceca/src/pages/workspace/tags/WorkspaceTagsPage.tsx#L175
    const navigateToTagsSettings = () => {
        Navigation.navigate(ROUTES.WORKSPACE_TAGS_SETTINGS.getRoute(policyID, Navigation.getActiveRoute()));
    };

and:
https://github.com/Expensify/App/blob/d18766580c7e35e439ff933f3097366e36c6ceca/src/pages/workspace/tags/WorkspaceTagsSettingsPage.tsx#L85
                        onPress={() => Navigation.navigate(ROUTES.WORKSPACE_EDIT_TAGS.getRoute(policyID, policyTagLists[0].orderWeight, Navigation.getActiveRoute()))}

It will add new backTo param to the route when we click "Custom tag name"
What alternative solutions did you explore? (Optional)

Ah thanks @NJ-2020! That makes sense. Given that, I think this can be external so adding the label.

@paultsimura can you check out the proposals when you have a moment? TY!

Thanks @paultsimura! Note for Melvin - we're reviewing proposals.

Doubling bounty because we are fixing 2 extra bugs

Just an update for melvin that we're working on the PRs

PR in the works! https://github.com/Expensify/App/pull/50416

@paultsimura Do we need a regression for this?
Payouts due:

[ ] Contributor: $500 @twilight2294 (feel free to send a request to NewDot)
[ ] Reviewer: $500 @paultsimura (Upwork offer - https://www.upwork.com/nx/wm/offer/104272735)

Ah thanks for letting me know @twilight2294 - can you please accept the offer here

Regression test - https://github.com/Expensify/Expensify/issues/441268
Paid out based on payment summary - https://github.com/Expensify/App/issues/49883#issuecomment-2451158106
But I just checked and there was discussion after the PR went to production- is there a regression that we need to track for this? @twilight2294 @paultsimura

hi @paultsimura thank you for the additional information. I think it sounds fair to keep the payment as is.
Closing this as complete!


Docs: Add ArangoSearch as top-level chapter in Manual and AQL docs

See https://github.com/arangodb/planning/issues/2607

Warning: This wasn't committed by me, looks like a git artifact again https://github.com/arangodb/arangodb/pull/5702/files#diff-bbe3f2321d83bde05f19e8604299c4ee

@Simran-B Sensible idea. As long as users find the word "ArangoSearch" in the main categories it would be fine for me.


Patch 1

Description
This adds validation and documentation that the name and endpoint fields cannot be used alongside offer_url.
Fixes:
fixes https://github.com/juju/terraform-provider-juju/issues/449

I seem to have broken it trying to squash


Duplicate input fields with id search-query in 404 page DOM

The 404 page features two input fields with id search-query. While the page is still functional, this causes HTML validators to fail.
Can be reproduced on the demo site: https://academic-demo.netlify.com/404

Did you already have any ideas on how to fix this? I'd be happy to take a stab.

Feel free to investigate and submit a PR. The easiest solution is perhaps to convert the instances in the templates along with the corresponding JS/CSS to refer to a CSS class name instead of ID, as long as it doesn't break anything...

I took a look, seems like switching to class-based selectors for this might end up making search a bit more brittle: there is code that relies on the id selector for setting focus and, while that can be addressed, it would complicate things a bit.
An alternative that seems to work is to just remove the id from the searchbox in the 404 page since, as far as I could tell, none of the logic for triggering search from that page seems to depend on the id itself.
Will send a PR shortly.


Added instrum resp for calcSpec, lots of feautres, fixed rho bug

Added instrum resp functionality
Added averaging functionality
Fixed bugs for normalized poloidal flux rho
Added (E,p,R,z) slice functionality when computing calcSpec

Added also extra functionality to automatically load bulk plasma profiles from TRANSP

Added also extra saving functionality


fix: close after error

can you add a unit test?
Il giorno sab 27 ott 2018 alle 20:54 Robert Nagy<EMAIL_ADDRESS>ha scritto:

You can view, comment on, or merge this pull request online at:
https://github.com/mcollina/sonic-boom/pull/15
Commit Summary

fix: close after error

File Changes

M index.js
https://github.com/mcollina/sonic-boom/pull/15/files#diff-0 (9)

Patch Links:

https://github.com/mcollina/sonic-boom/pull/15.patch
https://github.com/mcollina/sonic-boom/pull/15.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mcollina/sonic-boom/pull/15, or mute the thread
https://github.com/notifications/unsubscribe-auth/AADL49GJCaH5qDTSzTgqsWR9_RM75ArIks5upKvagaJpZM4X9lme
.

It should not be emitted with reopen. It should be emitted after everything is flushed.

Closing for low activity, feel free to reopen.


Python2.7 Legacy Branch Thorough Test

The legacy dev branch needs to be thoroughly tested.
Every single button needs to be clicked!
This includes testing all scanners, API stuff, and various reports.
Record any issues you come across.

Test Completed. Here's my report: https://docs.google.com/document/d/1ipoB6oRT3DOE9smgSsFzgOmlcouinKGhr2URaqwXkBU/edit?usp=sharing


Add CSS variable transformer for sd

#56

Hey @douglaszaltron,
I somehow figured this would be part of a formatter?
Why do you favor a transformer?
It has the benefit of flexibility but would need to be applied in correct order. Also did you test it with nested tokens. We must make sure to avoid issues where the referenced token is already transformed to a css value (this could be done using the original values I think).
Somehow it feels more fitting for me to have this done in the formatter, I guess in this function. But I am open to being convinced that transformers are better.

Hey @douglaszaltron,
I somehow figured this would be part of a formatter? Why do you favor a transformer?
It has the benefit of flexibility but would need to be applied in correct order. Also did you test it with nested tokens. We must make sure to avoid issues where the referenced token is already transformed to a css value (this could be done using the original values I think).
Somehow it feels more fitting for me to have this done in the formatter, I guess in this function. But I am open to being convinced that transformers are better.

At first, I thought about creating it as a formater, but as a transformer, I can apply the value modification for both JavaScript/* and JSON/*. It would extend more easily. I did realize about the order issue, that the value mutations need to be done beforehand.
transforms: [
    "name/cti/kebab",
    "shadow/css",
    "fontFamily/css",
    "font/css",
    "variables/css",
],

@lukasoppermann I made the adjustments, take a look.

Looks great, I'll have to test it and will merge it afterwards.


[1.16] Update pack.mcmeta

To prevent the the data/resource pack as being highlighted with red.

I assumed you closed this since it doesn't affect anything?


Added Responsiveness

Description
Added over all responsiveness to the website.
Fixes #94
Type of change

[x] Added Responsiveness
[x] fixed the position of Scroll to Top btn for easy access in smaller screens

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

Attachments
https://user-images.githubusercontent.com/69809086/126741990-91ccc37d-42fb-461a-af7c-8cb6122143d6.mp4

@souravseal99  add any ss or video clips ...to show responsiveness

@souravseal99  add any ss or video clips ...to show responsiveness

Sure @Ayan-thecodeking, updating it shortly with a video file.

@souravseal99  add any ss or video clips ...to show responsiveness

Sure @Ayan-thecodeking, updating it shortly with a video file.

good work @souravseal99 ....hope u will contribute more
thank you:)

hey @souravseal99 have u added responsiveness in other pages ???

hey @souravseal99 have u added responsiveness in other pages ???

Really sorry, I thought there was only the home page.
Please give a moment, I will push the rest of the changes very soon.

hey @souravseal99 have u added responsiveness in other pages ???

Really sorry, I thought there was only the home page.
Please give a moment, I will push the rest of the changes very soon.

yup update it

hey @souravseal99 have u added responsiveness in other pages ???

Really sorry, I thought there was only the home page.
Please give a moment, I will push the rest of the changes very soon.

yup update it

Added Responsiveness to contact us page

The events page was already responsive, so I left that as it was.
The index.html file was causing a merge conflict, I accepted the incoming changes and resolved it.

hey @souravseal99 ..please resolve the merge conflicts and make a PR ....

@souravseal99 plz update that

hey @souravseal99 ..please resolve the merge conflicts and make a PR ....

@souravseal99 plz update that

yes @Ayan-thecodeking , updated it. Please let me know, if it seems good to you.

hey @souravseal99 ..please resolve the merge conflicts and make a PR ....

should I make a new PR ?

hey @souravseal99 ..please resolve the merge conflicts and make a PR ....

should I make a new PR ?

Ya sure @souravseal99

hey @souravseal99 ..please resolve the merge conflicts and make a PR....

@souravseal99 plz update that

hey @Ayan-thecodeking, While resolving the merge conflicts, I found out that the main branch has a bug in the hamburger menu.
As I had to sync my code with the main branch, my working branch i.e. responsiveness, now also synced that bug from there.
For now I am only committing the changes required for the responsiveness and later on we can create a different issue regarding that.

hey @souravseal99 ..please resolve the merge conflicts and make a PR ....

should I make a new PR ?

Ya sure @souravseal99

Ok sure @Ayan-thecodeking , making a new PR shortly.

hey @souravseal99 ..please resolve the merge conflicts and make a PR ....

should I make a new PR ?

Ya sure @souravseal99

Ok sure @Ayan-thecodeking , making a new PR shortly.

just made the PR @Ayan-thecodeking, please let me know if you want me to make any further changes.


DEVELOPERS: Get rid of "print" functions and use right logging

Issue for future developers.
Logging using "print" function is not good. We should use special modules for logging.
Try to use only standard Python libraries to prevent enlarging of the requirements.txt.
Python standart logging library: https://docs.python.org/3/library/logging.html

Everything but the interactive print() statements have been converted to logging.  Of course logging could be better organized and used but this is a good start.


Docs: Change "handbook" to "reference"

Follow-up to https://github.com/Semmle/ql/pull/3178.
Whilst all the QL handbook articles are staying the same, they are now in a "QL language reference" category and the handbook itself doesn't exist anymore. The URLs remain unchanged for now, so I've only updated the link text.

This LGTM 💚. One remaining place this will need to be updated is: https://help.semmle.com/QL/ql-reference-topics.html. I don't think there's anywhere else.

Thanks! I have a list of outstanding changes in https://github.com/github/semmle-docs/issues/53.


Installing a domain instead of a local Ip with APSTA (IDFGH-9833)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
I am implementing the first major project on the esp32-s3 board, and switched from the arduino ide to esp-idf vs code, which seemed to me a more correct, more functional, albeit complex solution.
I ran into a problem:
It took the implementation of connecting the board to Wi-Fi and creating an access point so that the board could communicate with itself over a local network and, if there was a WiFi connection, discover additional features and functionality in the work of the original project.
I successfully coped with this task and implemented WebSocket and the server API via tls protocol on different secure ports, which also works, but the code requires improvements, but for now I put it aside.
Now my main problem is
It was necessary to make a domain for the address of the board in Wi Fi and AP, for which I used the esp_netif_set_hostname(net if, "esp") function - and this works fine for WiFi, while SoftAP only works on the static ip address <IP_ADDRESS>. There was an idea to do redirection using the DNS settings on the board, but not I was able to find the proper information in the documentation and other sites with the help of how it is possible to implement.
Please help with solving this problem, because it is very important in two modes to have the same domain to communicate with the board's web.

@drozdoff-dev Could you please describe you problem with mdns?

and it no longer works from a mobile device (

Are you trying to access the webserver using mdns name from your mobile phone? I think the mDNS would work seamlessly only on iPhones, on Android phones you'd have to install some application or service, e.g. Service-Browser or similar.


Provisioning using a bastion does not work on a restricted shell

Provisioning using a bastion requires access to the mkdir command because of this.
However, sometime the sysadmins who set up the bastion allowed only access to the ssh command, so that we can jump to the destination host.
It would be great if this provider could work without trying to store the SSH public keys of the destination host on the bastion.

Hey @mcanevet, thank you for the report. Would the assumption be that the bastion has the known hosts file preconfigured?

Unfortunately no. I still have the message saying that the authenticity of the host can't be established before first login to remote host.

The only thing I can think of, is the following:

a new setting ansible_ssh_settings.bastion_insecure_no_strict_host_key_checking, default false; if true, StrictHostKeyChecking no is added for ssh connections to the bastion
a new setting ansible_ssh_settings.insecure_no_strict_host_key_checking, default false; if true, StrictHostKeyChecking no is added for ssh connection to target host; when going via bastion host, bastion should auto accept the target host key, in this case, bastion would not attempt executing any key scan related commands commands at all

Additionally, having ansible_ssh_settings.bastion_user_known_hosts_file and ansible_ssh_settings.user_known_hosts_file wouldn't hurt either. This way, the administrator could potentially provide a bastion host with known hosts file populated.

@radekg I think your solutions would work fine.

Hi @mcanevet, I'm about to merge https://github.com/radekg/terraform-provisioner-ansible/pull/94 which contains the code required for the above workflow.
The example sshagent-local-with-bastion is the closest reflecting the described setup. To validate that the insecure_... settings do what they supposed to, cd into thhat example directory and run:
terraform apply -var "ami_id=${TERRAFORM_PROVISIONER_ANSIBLE_AMI_ID}"         -var "region=${R_REGION}" -var "aws_admin_profile=${R_NAME}" -var "vpc_cidr_block=${R_VPC_CIDR_BLOCK}" -var "infrastructure_name=${R_NAME}-local" -var "insecure_no_strict_host_key_checking=true"

Because it takes more than 30 seconds for the SSH to become available on the target, you will need a file like this one: https://github.com/radekg/terraform-provisioner-ansible/pull/94/files#diff-170acbfffb52268849488843675447d2R1.
It seems that the usual SSH options for timeout and retries are not respected, what matters is the timeout and retries from the config file.
Of course, you'll need to set the environment up, as described in Getting started.

Resolved with
https://github.com/radekg/terraform-provisioner-ansible/pull/94.


Abandonware?

Is this project still alive?

It is! I've just been very busy with other projects. If you've got the time and interest, I'm looking for a collaborator on this one.

I’m going to chcek it out. Will reply here in a few days.
Thanks for swift info!


Set up Action Mailbox; use it to create log entries via email reply

This change (which got successfully deployed via this change: https://github.com/davidrunger/david_runger/pull/2745 ) appears to be associated with a significant increase in memory usage:

The output of bundle exec derailed bundle:mem (ref: https://github.com/schneems/derailed_benchmarks ) suggests that high memory usage by action_mailbox and/or its dependencies might be to blame:

See https://github.com/mikel/mail/issues/ 1342 for discussion of this high memory usage and https://github.com/mikel/mail/pull/ 1343 for a possible solution.

(The problem seems to be more with the mail/parsers/address_lists_parser dependency of action_mailbox/engine, rather than action_mailbox/engine itself.)

I've merged https://github.com/davidrunger/david_runger/pull/2754 as a bandaid/"fix" for this problem. I'm bummed that I've had to go from 2 server processes down to just 1 because of this issue of excessive memory usage by mail/parsers/address_lists_parser, which I think that I'm barely even actually using (maybe not at all?).


Added static framework build settings presets

Added static framework build settings presets: the lack of SKIP_INSTALL: 'YES' was resulting in invalid archives when archiving. See https://github.com/yonaskolb/XcodeGen/pull/358 and https://stackoverflow.com/a/26563115/3203441 for further references

Also may solve https://github.com/yonaskolb/XcodeGen/issues/813


Changed the stub method to resolvesArg

The proper way to use an identity function as a stub for a promise in sinon.js is to use resolvesArg(0). Because of this the tokens attribute was set to an anonymous function instead of the expected value.
And the funny thing is the test was passing because it was only checking the length attribute to be one, which would also be true for an anonymous function.

I'm currently working on a psf-slp-indexer interface contract related bug. The PR for that is incoming.


Adjust regular expression to avoid look behind expression for Safari compatibility

Resolves #9

Thanks @mamaddox ! Whats the release process like for this project? When will we see a tagged release with this fix in it?

Thanks @mamaddox ! Whats the release process like for this project? When will we see a tagged release with this fix in it?

Hey, also interested when it will get published. @zetagame @mamaddox

@StefanSelfTaught and @m4olivei Sorry for the delay! We're still sorting out the release process. We should be getting a new version out today or sometime this week.

@StefanSelfTaught and @m4olivei The release just went out today 🎉


Module appears on Starfinder worlds

As seen in the image, the HeroLab Online PF2e Import Tool module appears on worlds with the Starfinder system installed. None of the documentation shows that HLO Starfinder characters are supported (which I would absolutely love to have), so I'm assuming this is simply not restricted to PF2 worlds.
If this is a feature you are looking at adding, I would love to assist.

Thanks for the heads up!  Just a small display bug. I have no plans to support Starfinder at this time.
Pushed a fix for this


[PDI-18453] Enhance SQLite database input to correctly return BLOB field

Removes restrictions that forces an SQLite BLOB field to only be returned to PDI as a String.   NOTE: This change is dependent on PDI-18456.

:white_check_mark: Build finished in 14m 33s
Build command:
mvn clean verify -B -e -Daudit -amd -pl core

:ok_hand: All tests passed!
Tests run: 4709, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message

:white_check_mark: Build finished in 16m 55s
Build command:
mvn clean verify -B -e -Daudit -amd -pl core

:ok_hand: All tests passed!
Tests run: 4714, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message

:white_check_mark: Build finished in 23m 6s
Build command:
mvn clean verify -B -e -Daudit -amd -pl core

:ok_hand: All tests passed!
Tests run: 4715, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message

:white_check_mark: Build finished in 20m 58s
Build command:
mvn clean verify -B -e -Daudit -amd -pl core

:ok_hand: All tests passed!
Tests run: 4718, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message

:white_check_mark: Build finished in 16m 4s
Build command:
mvn clean verify -B -e -Daudit -amd -pl core

:ok_hand: All tests passed!
Tests run: 4727, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message

assertArrayEquals( new String[] { "sqlite-jdbc-3.7.2.jar" }, nativeMeta.getUsedLibraries() );
--> Shouldn't we change the test to the changed version by PR 7039?

@mkambol can you please reivew the PR

This is taken care of in PDI-18456.
On Monday, November 18, 2019, 10:43:33 AM EST, Jens Bleuel<EMAIL_ADDRESS>wrote:
assertArrayEquals( new String[] { "sqlite-jdbc-3.7.2.jar" }, nativeMeta.getUsedLibraries() );
--> Shouldn't we change the test to the changed version by PR 7039?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Please keep in mind for this to work completely, PDI-18456 must also be applied.  This one is where the JDBC driver is updated.
On Monday, November 18, 2019, 11:13:29 AM EST, Ramaiz Mansoor<EMAIL_ADDRESS>wrote:
@mkambol can you please reivew the PR
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Sorry @cgrimm01 -  just merged 7039, which introduced the conflict.  Can you resolve?

Can you give me a hint on what I need to do with this?  This is the first time I have tried to submit.a change for Pentaho.
Thanks!
On Monday, November 18, 2019, 11:42:34 AM EST, Matt Campbell<EMAIL_ADDRESS>wrote:

Sorry @cgrimm01 - just merged 7039, which introduced the conflict. Can you resolve?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

I don't have write access, so please let me know how I can resolve.

I believe this is now correct.

I think I managed to resolve the conflict. Please verify.
On Monday, November 18, 2019, 11:50:54 AM EST, Clifford Grimm<EMAIL_ADDRESS>wrote:
Can you give me a hint on what I need to do with this?  This is the first time I have tried to submit.a change for Pentaho.
Thanks!
On Monday, November 18, 2019, 11:42:34 AM EST, Matt Campbell<EMAIL_ADDRESS>wrote:

Sorry @cgrimm01 - just merged 7039, which introduced the conflict. Can you resolve?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

I believe this has been correctly resolved.

@cgrimm01 -  that works :) .   I typically squash commits locally and force push when I make changes to a PR just to make sure it goes in as a single commit, but I can squash on merge.

:white_check_mark: Build finished in 17m 6s
Build command:
mvn clean verify -B -e -Daudit -amd -pl \
core,plugins/connections/ui,plugins/file-open-save-new/core,ui

:ok_hand: All tests passed!
Tests run: 4727, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message


[DOCS] fix tvm.build API doc layout.

Why
The newline in the pydoc breaks the layout of parameter inputs in API tvm.build,  as shown below,

How
Just remove the newline.
Thanks for contributing to TVM!   Please refer to guideline https://tvm.apache.org/docs/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers by @ them in the pull request thread.

@tqchen

Thanks for the fix @kuizhiqing, this is now merged 😸


SAML 2.0 based authorization

I want to use a SAML 2.0 based identity provider for my portal. According to the document, I need to create an application to configure settings with the identity provider by Azure AD or AD FS.
Can I use the other external SAML 2.0 based identity provider(not Azure AD ,not AD FS).
For example, the company's own authorization system(SAML 2.0 based)

Thank you for reaching out. You can use SAML 2.0 compliant identity providers in addition to Azure AD and AD FS examples.


Support for Flutter Web Apps Built with "--wasm" Flag?

This might be a naive question but is it possible to build a flutter web app that leverages the new "--wasm" compilation mode and is still able to leverage an internal package that utilizes a wasm module generated through the flutter_rust_bridge_codegen build-web command?

I have not tried it personally, since it seems the flutter wasm requires browser to support WasmGC which is quite new and not many browser users have those browsers installed. However, since frb has migrated to the new js interop packages, theoretically it should work. Feel free to have a try and ping me if it does not work!

It is producing this error with the version 2.1.0 and the base template code

Seems like https://github.com/fzyzcjy/flutter_rust_bridge/blob/9e5c6e54723700e8436bc76016173e0391befa8e/frb_dart/lib/src/dart_opaque/_web.dart#L1 is not migrated (indeed it seems to be the only one remaining? https://github.com/search?q=repo%3Afzyzcjy%2Fflutter_rust_bridge js_util&type=code)
Feel free to PR to migrate it to dart:js_interop which is usually trivial, or alternatively I will work on it later (but may not be very soon, since flutter wasm is quite experimental and only works in a small portion of browsers)

To be handled in https://github.com/fzyzcjy/flutter_rust_bridge/issues/2237 (hopefully within a week)


[Improve][Flink] Optimization of  Kafka Source Busy Problem

Purpose of this pull request

link #8358

subtask : Kafka optimization

Does this PR introduce any user-facing change?

How was this patch tested?

Check list

[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist
Add ci label in label-scope-conf
Add e2e testcase in seatunnel-e2e
Update connector plugin_config

[ ] Update the release-note.

This PR will not be merged for the time being as the change will have too much impact. We are waiting for the best solution to be discussed.


Add support for #[derive(Debug, serde::Serialize, serde::Deserialize)] to SharedStruct

Expanding on https://github.com/chinedufn/swift-bridge/pull/198
Let me know if this is heading toward the right direction, I can add more tests later.

Looks like the right direction

I added a few tests, let me know if I missed anything.

@wooden-worm are you still working on this PR? I could really use this feature, and I'd be happy to help move this forward.

I've added a few tests, not sure what else this needs in order to merge?

@wooden-worm thanks for the quick reply.
@chinedufn are there any other required changes before this can be merged?

I'll take a look over the weekend.

I am in dire need to be able to have #[derive(Debug, Default, Clone)] on shared structs. also I am wondering how to make them vectorizable aka allow me to return a Vec<T> of them


Migrate meshery.io to google tag manager

Description
This PR fixes #
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

@ayushthe1, hopefully, we can finish this one off this week. @Udit-takkar, perhaps, you can do so...


scripts/tidb.json: remove tso_async_wait from the grafana panel

tso_async_wait is misleading, so it's better to remove it from the grafana.
http://<IP_ADDRESS>:34125/d/000000011/test-cluster-tidb?orgId=1
The rule is now
type!~"tso|tso_async_wait"

About the change, !~ means

Select labels that do not regex-match the provided string.

https://prometheus.io/docs/prometheus/latest/querying/basics/

PTAL @jackysp

LGTM


Security Notice from Github Bootstrap.Less

Wanted to post an issue since I didn't see one here. Via GitHub

Known moderate severity security vulnerability detected in Bootstrap.Less >= 3.0.0, < 3.4.1 defined in packages.config.
packages.config update suggested: Bootstrap.Less ~> 3.4.1.

Fixed in 8f2a4ac where I upgraded to 3.4.1 of both bootstrap and bootstrap.less , I was too lazy to create an issue.


IoT Hub - X509CA support

Migrating these changes: 1253
to a new API version.
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

@mtuchkov,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@anuchandy The error that linter shows are applicable to the first class ARM resources. LIke, 'Top level properties should be one of name, type, id, location, properties, tags, plan, sku, etag, managedBy, identity'. The certificates are iothub's subordinate reource. The warnings are not applicable also, for instance on PUT we accept the Certificate as a PEM or CER files, but on GET we give back a normalized JSON representation of the certificate with Subject, Expiry, etc.
Moreover, these PR was already approved two months back. See 1253 Pull Request

@mtuchkov my understanding is this operations group which represents operations on the certificates is already deployed but it is not exposed through swagger, so no SDK exposes these functionalities.
In order to comply with the new process we have, I would start with feed back from ARM and their sign off. Added the tag "WaitForARMFeedBack".

Hi @anuchandy,
@andrew-buckley is working on SDK for this feature and it is already done and is waiting for swagger to be merged in to publish the SDK.

@mtuchkov thanks.
@ravbhatnagar could you please sign-off from ARM side?, this is the first time operation group Certificates is going to be exposed (though it is already deployed) via SDKs. 'Certificatesis child resource of ARM resourceIotHub`

@mtuchkov looks like there is another PR opened with similar changes https://github.com/Azure/azure-rest-api-specs/pull/1487..
Could you take a look at linter error and warnings.. https://travis-ci.org/Azure/azure-rest-api-specs/jobs/261929893

@anuchandy another PR was for previous version of API. it is not needed to change the old version as long as we have shipped a new version meanwhile.
Linter errors and warnings are not applicable to us. It requires to add fields like location and properties, but this is a child resource, we do not have these properties on child resource.
other warnings about PUT and GET data contract, it asks to make them identical. But they cannot be the same, User uploads certificate and we return them only certificate properties, but not the cert itself.

@ravbhatnagar Please take a look

@ravbhatnagar
I know we've chatted about this with the group are we good to go from your side?

@salameer - as discussed over email, we don't want SDKs/docs to be generated for this. SO I would say, lets hold off on merging this.

@ravbhatnagar what's left to merge this change?

SDK is OK with merging if Gaurav gives the Greenlight from ARM

@mtuchkov I know that you guys are waiting for the service to go live before the changes get merged in, what's the status here?

@mtuchkov any status updates?

I have email confirmation from Shankar that the service has been deployed, I think we're unlbokced on Merging :)

@mtuchkov seems fix is deployed.. could you update the certificateDescription to reflect the fix?

@mastermanu should I close this PR given that you have a new PR with same features?

This PR is not relevant any more, closing this.


Flatpak version crash after pin enter

   ~  flatpak run com.quexten.Goldwarden                                                                                 ✔
F: X11 socket /tmp/.X11-unix/X0 does not exist in filesystem, trying to use abstract socket instead.
starting goldwarden daemon /app/bin/goldwarden
running locked status daemon
[INF] [23:35] [Goldwarden > Keyring] >>> Creating new memguard keyring
[WRN] [23:35] [Goldwarden > Agent] >>> Config is not locked. SET A PIN!!
[INF] [23:35] [Goldwarden > Agent] >>> Agent listening on /home/kweezy/.var/app/com.quexten.Goldwarden/data/goldwarden.sock...
[INF] [23:35] [Goldwarden > SSH] >>> SSH Agent listening on /home/kweezy/.var/app/com.quexten.Goldwarden/data/ssh-auth-sock
[WRN] [23:35] [Goldwarden > Agent] >>> Could not monitor idle: org.freedesktop.DBus.Error.ServiceUnknown
listening for pinentry /app/bin/goldwarden
Running in flatpak, registering with background portal for autostart.
[INF] [23:35] [Goldwarden > Agent] >>> Received pinentry registration request
[INF] [23:35] [Goldwarden > Agent] >>> Pinentry registration success: true
create authenticated connection
[INF] [23:35] [Goldwarden > Agent] >>> Verified: true
[INF] [23:36] [Goldwarden > Pinentry] >>> Asking for pin |Pin Change|Enter your desired pin|
[INF] [23:36] [Goldwarden > Agent] >>> Received getPassword request
zsh: terminated  flatpak run com.quexten.Goldwarden
   ~ 

Hmm, what's your distro, desktop-environment and do you use wayland or xorg?

Manjaro KDE, xorg. The bug disappeared after a reboot, so i am closing issue


[Old Settings] Warn the user on Windows < 1903 that next version won'…

…t be supported
Summary of the Pull Request
What is this about:
0.35 is the last PowerToys release that will support Windows 1803 and 1809.
Add a warning in the old settings to alert the users they will not be able to install future releases.
Note: we might have to change the wording since it will still be possible to install patch release 0.35.x, but not 0.36.0 or greater.
What is include in the PR:
How does someone test / validate:
Quality Checklist

[x] Linked issue: #10302
[ ] Communication: I've discussed this with core contributors in the issue.
[ ] Tests: Added/updated and all pass
[ ] Installer: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Docs: Added/ updated
[ ] Binaries: Any new files are added to WXS / YML

[x] No new binaries
[ ] YML for signing for new binaries
[ ] WXS for installer for new binaries

Contributor License Agreement (CLA)
A CLA must be signed. If not, go over here and sign the CLA.

/azp run


fix: wheel scroll bug

Coverage decreased (-0.01%) to 71.123% when pulling 7cc7436f6049b50fd35d7b1bf23a4cd74aef824b on edison-hm:dev into 28f379aa6132a773482c037f0f04c499f085da98 on ZhonganTechENG:dev.


Shifter: Make optional the use of Segment scale compensation

Talk from forum: http://forum.mgear-framework.com/t/how-to-prevent-shear-on-joints/3252/3

https://user-images.githubusercontent.com/1050212/210682371-e11d8027-0104-46a5-8a6e-62c01cd77ecf.mp4

Reopening ticket:
The current implementation is not working correctly with non uniform scale and also is breaking global scale

https://user-images.githubusercontent.com/1050212/212822910-71608c34-1766-4ba2-8ac4-e4c69fa380fe.mp4


Implementing LUD-12 comments on payRequest in LNURLP Lightning Address flow (sending and receiving)

Related to #230
This PR enhances SN on the receiving end to support comments when someone sends to a<EMAIL_ADDRESS>lightning address.
It also enhances the withdraw to lightning address flow from SN to allow comments to be included, if the lightning address provider supports them.
Sample wallet history UI:

Looks like the right approach to me. Nice work!

Cool, thanks for taking a look! I'd like to implement the "wallet" side of LUD-12 on SN, too, so withdrawing to a lightning address allows you to specify a comment, if the recipient supports it. Full circle! :)

Great work! I'll probably deploy this weekend's merges monday

All good. It took me awhile to get in the habit of deleting the functions when signatures change. It was only after subtle bugs started appearing where I was using old versions of functions unknowingly


there is  no  active source manage system program .

VSCode Version: Code 1.19.0 (816be6780ca8bd0ab80314e11478c48c70d09383, 2017-12-14T12:06:43.492Z)
OS Version: Windows_NT x64 10.0.16299
Extensions:

Extension
Author (truncated)
Version

ng-template
Ang
0.1.7

npm-intellisense
chr
1.3.0

path-intellisense
chr
1.4.2

ng-zorro-vscode
cip
1.1.3

vscode-eslint
dba
1.4.3

tslint
eg2
1.0.24

vscode-npm-script
eg2
0.3.3

vsc-material-theme
Equ
1.1.2

vue-snippets
hol
0.1.5

beautify
Hoo
1.1.1

vscode-npm-dependency
how
1.1.4

webpack
jer
2.0.2

Go
luk
0.6.69

font-awesome-codes-html
med
0.0.7

vscode-language-babel
mgm
0.0.10

Angular-BeastCode
Mik
5.1.8

vscode-extension-auto-import
Nuc
1.4.1

material-icon-theme
PKi
3.1.0

LiveServer
rit
3.0.0

px-to-rem
sai
1.2.3

vscode-i18n-tag-schema
sko
2.2.0

(1 theme extensions excluded)

Steps to Reproduce:

there is  no  active source manage system program .

i had setted the git path

Reproduces without extensions: Yes/No

Actually I find  the git can work  when i use use the command pannel (crtl + shift + p),   but  only in the source manage pannel display  not work ,

This is being tracked in #40243


Feature Request: 'canonical' headSetting

In addition to the title, favicon, and lang, I would find it handy to be able to specify a canonical URL in the page config.
This could be beneficial for other SSG sites optimized for search engines (see How to specify a canonical with rel="canonical" and other methods.
I currently implement this in my HeadDefault.vue as below, but it seems to closely match the pattern in the latest onRender{Client|Html} code, and may have broader appeal beyond my specific use case, so if you think it would be beneficial, please let me know and I'll submit a PR. Curious also why it appears that description was removed in the latest code, as I also configure description on page-by-page basis.
e.g.
const canonical = getHeadSetting('canonical', pageContext)

const canonicalTag = !canonical ? '' : escapeInject`<link rel="canonical" href="${canonical}" />`

Replaces my specific implementation:
<template class="h-100">
  <meta charset="UTF-8" />
  <link rel="apple-touch-icon" sizes="120x120" href="/favicons/apple-touch-icon.png">
  <link rel="icon" type="image/png" sizes="32x32" href="/favicons/favicon-32x32.png">
  <link rel="icon" type="image/png" sizes="16x16" href="/favicons/favicon-16x16.png">
  <link v-if="canonical" rel="canonical" :href="canonical">
  <link rel="manifest" href="/favicons/site.webmanifest">
  <link rel="shortcut icon" type="image/x-icon" href="/favicons/favicon.ico">
  <meta name="msapplication-TileColor" content="#da532c">
  <meta name="msapplication-config" content="/favicons/browserconfig.xml">
  <meta name="theme-color" content="#ffffff">
  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
</template>

Hi @TimJohns I agree with everything you wrote. I think we removed description too quickly as we wanted to refactor/simplify things and we underestimated the need for setting a page-specific description that would be updated on client-side navigation.
So yes, please feel free to create one or several PRs (re-)introducting the following settings:

description
canonicalUrl

Looking forward to it :pray:
@brillout FYI feel free to push back as it would be nice to align vike-react afterwards

Actually let me back-pedal a bit. So the reason why we removed description is because:

You can now do it through Head as you know
There is no need to update the description on client-side navigation as a human user wouldn't really care about that description, which is more designed for robots, which are not using client-side navigation.

Argument 2. holds as well for canonicalUrl. It doesn't hold though for the favicon and the title of the page, which a human user expects to be updated on client-side navigation. That's why we kept these two settings, and only these two.
So I'm changing my mind here: we'd rather not (re-)introduce the description and canonicalUrl settings. I apologize if you started working on it.
However, I'd love to see the basic example extended with canonical URLs, similarly to your snippets. Would you be up for creating a PR for the examples? Thanks a lot :pray:

Thanks for the conversation @TimJohns @AurelienLourot.
Yes, that's the reason I only kept title, favicon, and lang: these are the only three  tags I'm aware of that need to be updated upon client-side navigation.
Although I'm realizing that setting a global default description that is being overriden by only some pages is a use case that currently doesn't have a good DX. The issue is that Head is all-or-nothing: there is no way to tell "only override the description while keeping all other  tags". I'm not sure what we can/should do about this 🤔
@4350pChris WDYT? 👀

I would argue that some crawlers are using client-side navigation, like @crawlee/puppeteer.
Even Google has a Javascript SEO thingy.
I'm confident in saying that most crawlers are just plain HTML parsers, but I can see a path where it begatively impacts SEO in some way too.

Not to complicate the matter, but one additional consideration worth noting is that while description (and title) is typically human-defined by the developer, a reasonable default 'canonicalUrl' could probably be determined at build time, and may be more appropriately provided programmatically, perhaps in coordination with a plugin that also generates a corresponding sitemap.xml.
In my case, I provided explicit canonicalUrl values in the various pages' +config.h.ts files, but only because my site is small and it seemed easy to do so, and it matched the patterns I saw for the other Head values - there may be a more appropriate mechanism.
In any case, I will see if I can create an example as a basis for reasoning about it, and go from there, and we certainly have my specific actual use case to inform some discussion as well.
Also, thanks for the work on Vike and vike-vue; I am finding it quite useful and I appreciate it.

That (generating canonicalUrl programmatically) seems like I would make a particularly relevant example; I will see what I can come up with there.

Keeping this issue open as @brillout and I had a talk earlier today. We're thinking of (re-)introducing more settings like description for a reason other than crawlers using client-side navigation. Right now the DX is quite convoluted if a user wants to:

define a Head component at the root of their project, and
override only parts of that component for certain pages.

Having more fine-grained settings would alleviate that. On top of that, we'd like some settings to be more "semantic", e.g.:

title would not only set <title> but also og:title
description would not only set <meta name="description" but also og:descrption

Just to give my two cents here - is this really something to implement ourselves? I've been using https://unhead.unjs.io for some time now and really like it, so I wouldn't like to ditch that for vike's implementation. So we should definitely keep it open for users to use their own library / implementation here. On top of that - how would you generally see incorporating that library and focus only on making it work smoothly together?

I'll put it here because it is related, even if it is a new feature:
One other attribute related to lang that should have the same treatment is dir - for documents in specific languages the direction should be set for the whole document.

@pdanpdan :+1: Makes sense and it's on the radar as well.

Another possible use case - I'm currently using <teleport> to add image metadata structured data to , at run-time on the client, using the approach described in the accepted answer to this stack overflow article. That approach is itself a workaround to

    </>
  )
}

I guess we can do the same for vike-vue? Does Vue has something like React's dangerouslySetInnerHTML?

I am happy to contribute

Yes, contribution welcome! If you're up for it, you could contribute replicating the vike-react/Head component for vike-vue. Although note that, while it's all-in-all fairly straighforward (also because I think I've paved a fairly clear path), it isn't completely trivial to implement.

Vue has the v-html directive and Render Functions that have the capability of injecting html.
Here's what I am currently doing (directly within +Head.vue for a subset of pages, without the teleport I mentioned earlier - I keep changing my mind on which approach is cleaner...).
Security Note: I have not thoroughly analyzed this code for the possibility of injection attacks using carefully crafted imgSrc and copyrightNotice values, but neither imgSrc nor copyrightNotice are user-provided in our use case (and they have been validated and sanitized server-side).
<template class="h-100">
  <link rel="apple-touch-icon" sizes="120x120" href="/favicons/apple-touch-icon.png">
  <link rel="icon" type="image/png" sizes="32x32" href="/favicons/favicon-32x32.png">
  <link rel="icon" type="image/png" sizes="16x16" href="/favicons/favicon-16x16.png">
  <title>{{title}}</title>
  <meta v-if="description" name="description" :content="description">
  <link v-if="canonicalUrl" rel="canonical" :href="canonicalUrl">
  <link rel="manifest" href="/favicons/site.webmanifest">
  <link rel="shortcut icon" type="image/x-icon" href="/favicons/favicon.ico">
  <meta name="msapplication-TileColor" content="#da532c">
  <meta name="msapplication-config" content="/favicons/browserconfig.xml">
  <meta name="theme-color" content="#ffffff">
  <meta name="viewport" content="width=device-width, initial-scale=1.0" />

  <template v-for="photo in photos">
    <ImageObjectJSONLD :contentUrl="photo.imgSrc" :copyrightNotice="photo.copyrightNotice"/>
  </template>

  <link rel="preconnect" href="https://identitytoolkit.googleapis.com">
  <link rel="preconnect" href="https://maps.gstatic.com">
  <link rel="preconnect" href="https://accounts.google.com">
  <link rel="preconnect" href="https://maps.googleapis.com">
  <link rel="preconnect" href="https://lh3.googleusercontent.com">
  <link rel="preconnect" href="https://api.epicroadtripplanner.com">
</template>

I did some experimentation earlier this week and really want to double-down on what @4350pChris said here about ensuring things like https://unhead.unjs.io integrate smoothly.

Just to give my two cents here - is this really something to implement ourselves? I've been using https://unhead.unjs.io for some time now and really like it, so I wouldn't like to ditch that for vike's implementation. So we should definitely keep it open for users to use their own library / implementation here. On top of that - how would you generally see incorporating that library and focus only on making it work smoothly together?

Chris, I'm not sure if you got that working cleanly, but I tried some fairly complex workarounds because https://unhead.unjs.io's state is reset between the rendering of of the page content and the head content, and ultimately took a step back to try again another day. This may just be learning curve on my part, but I figured I'd share some details in case it's relevant to this issue thread.
Specifically, it seems like the natural place to install unhead is the onCreateApp hook, but that didn't work for me out-of-the-box because onCreateApp is called twice for each pre-rendered page in my configuration. I believe this is first for the Page itself, and then again separately for the Head. In any case the unHead state is reset in this setup. I tried creating a distinct unHead cache and storing it in the PageContext, but I ran into some complexity trying to get that right, and ultimately backed off to something I understood a little better.
I'm in fact still working to understand better how all of this interacts, particularly in my hybrid configuration (vs. a pure SPA or SSR app), but I thought I would post that observation in case it's helpful or on anyone else's mind on this topic as well. I've currently gone back to a tightly-coupled custom +Head.vue that "knows" what components I might have used in my +Page.vue based on the data. That is, I currently have a little bit of duplicated code in +Head.vue and +Page.vue that looks through the data returneduseData, and constructs ImageObject JSON-LD script tags in the head and the corresponding photo components within the page itself. That works fine in my specific use case, and is something I understand, but even just playing around with unHead briefly, it definitely seems clean and intuitive, and I especially very much like the loose coupling between the head and the specific Components on any given page, so hope I either just missed something simple, or we can find a way to accommodate it going forward.

Yes, having a unhead integration is very much on the radar. Can you publish a working example of using Vike and unhead without vike-vue (Vike boilerplate with manual Vue integration: npm install vike@latest)? I'll translate that in a vike-vue-unhead extension for you to use with your vike-vue app.

Sounds good - here's the diff, and I'll create an actual GitHub repo for the files as soon as I get back to work (probably Monday). No rush on my behalf, though, and thanks as always - grateful for Vike and these integrations!
diff --git a/package.json b/package.json
index af4227a..83afd2c 100644
--- a/package.json
+++ b/package.json
@@ -11,6 +11,8 @@
     "@types/compression": "^1.7.5",
     "@types/express": "^4.17.21",
     "@types/node": "^20.10.4",
+    "@unhead/ssr": "1.9.16",
+    "@unhead/vue": "1.9.16",
     "@vitejs/plugin-vue": "^5.0.0",
     "@vue/compiler-sfc": "^3.3.10",
     "@vue/server-renderer": "^3.3.10",
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index 37612fe..5912823 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -10,5 +10,26 @@

diff --git a/renderer/+onRenderHtml.ts b/renderer/+onRenderHtml.ts
index 68ddd23..361c4c7 100644
--- a/renderer/+onRenderHtml.ts
+++ b/renderer/+onRenderHtml.ts
@@ -7,6 +7,8 @@ import { escapeInject, dangerouslySkipEscape } from 'vike/server'
 import { createVueApp } from './createVueApp'
 import logoUrl from './logo.svg'
 import type { OnRenderHtmlAsync } from 'vike/types'
+import { renderSSRHead } from '@unhead/ssr'
+import { getActiveHead } from 'unhead'
 import { getPageTitle } from './getPageTitle'

 const onRenderHtml: OnRenderHtmlAsync = async (pageContext): ReturnType<OnRenderHtmlAsync> => {
@@ -15,24 +17,66 @@ const onRenderHtml: OnRenderHtmlAsync = async (pageContext): ReturnType<OnRender
   if (!pageContext.Page) throw new Error('My render() hook expects pageContext.Page to be defined')

   const app = createVueApp(pageContext)
+
+  const head = getActiveHead();
+  if (!head) throw new Error('No active unhead head. Ensure you have installed unhead by calling createHead and app.use(head).')
+
+  /**
+   * title and desc are now site-wide defaults, and are overwritten by any page-specific or
+   * layout-specific updates to useHead({}).
+   *
+   * @see<EMAIL_ADDRESS>+   *
+   * Note that the order we render in is important. Only the most recent
+   * <title> and <meta name="description"> will be used, so we intentionally
+   * do this head.push prior to calling renderToString().
+   *
+   * @see https://unhead.unjs.io/usage/guides/handling-duplicates#deduping-logic
+   *
+   */
+  const title = getPageTitle(pageContext)
+  const desc = pageContext.data?.description || pageContext.config.description || 'Demo of using Vike';
+
+  head.push({
+    htmlAttrs: {
+      lang: "en"
+    },
+    link: [
+      {
+        href: logoUrl,
+        rel: "icon"
+      }
+    ],
+    title,
+    meta: [
+      {
+        name: 'charset',
+        content: 'UTF-8'
+      },
+      {
+        name: 'viewport',
+        content: 'width=device-width, initial-scale=1.0'
+      },
+      {
+        name: 'description',
+        content: desc,
+      }
+    ],
+  });

   const appHtml = await renderToString(app)

-  // https://vike.dev/head
-  const title = getPageTitle(pageContext)
-  const desc = pageContext.data?.description || pageContext.config.description || 'Demo of using Vike'
+  const { headTags, bodyTags, bodyTagsOpen, htmlAttrs, bodyAttrs } = await renderSSRHead(head)

   const documentHtml = escapeInject`<!DOCTYPE html>
-
+

-        <meta charset="UTF-8" />
-        <link rel="icon" href="${logoUrl}" />
-        <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-        <meta name="description" content="${desc}" />
-        <title>${title}</title>
+        ${dangerouslySkipEscape(headTags)}

-
+
+        ${dangerouslySkipEscape(bodyTagsOpen)}

${dangerouslySkipEscape(appHtml)}

+        ${dangerouslySkipEscape(bodyTags)}

     `

diff --git a/renderer/createVueApp.ts b/renderer/createVueApp.ts
index c8a73b1..fd620cf 100644
--- a/renderer/createVueApp.ts
+++ b/renderer/createVueApp.ts
@@ -6,6 +6,7 @@ import { setData } from './useData'
 import Layout from './Layout.vue'
 import type { PageContext } from 'vike/types'
 import { objectAssign } from './utils'
+import { createHead } from '@unhead/vue'

 function createVueApp(pageContext: PageContext) {
   const pageContextRef = shallowRef(pageContext)
@@ -17,6 +18,10 @@ function createVueApp(pageContext: PageContext) {
   setPageContext(app, pageContextRef)
   setData(app, dataRef)

+  const head = createHead()
+  app.use(head)
+
+
   // app.changePage() is called upon navigation, see +onRenderClient.ts
   objectAssign(app, {
     changePage: (pageContext: PageContext) => {

@TimJohns Thank you! Let me finish my current priorities and I'll then take a stab at it (sometime around next week). In the meantime, feel free to try to create vike-vue-unhead by having a look at the source code of vike-vue-query, vike-vue-pinia, and vike-vue.

Done.

https://vike.dev/head-tags
https://vike.dev/useConfig

Closing, but let me know if you believe something's missing. We are looking forward to gather feedback about the newly introduced head tag management improvements.

As for vike-vue-unhead I can take a stab at it a little later. Contribution very much welcome if I get delayed.

As for vike-vue-unhead I can take a stab at it a little later. Contribution very much welcome if I get delayed.

I'm deprioritizing this. I created https://github.com/vikejs/vike-vue/issues/183 to track progress. Contribution welcome.

Curious: with the latest improvements to head management, is there a rationale for using vue-unhead?

I'd be curious to know this. This would also increase the priority to work on #183 .

Thanks - I've updated to the latest and everything is working great for me, and I'll try unhead again with vikeVue when I get back.
I don't know that I'd recommend prioritizing a specific integration, but there may be a change to the way the create app hooks are called in vikeVue that would allow unhead to be used if someone does have a preference. As for why someone might have a preference to use unhead, one reason that was relevant to me is that it has a set of handy schema.org integrations. I only needed image and rolled my own component, so I am definitely not blocked by this. I suspect others may just prefer unhead for familiarity coming from other ecosystems and frameworks, but unhead was new to me, so that's hypothetical on my part.

it has a set of handy schema.org integrations

Indeed, that's neat. I'm thinking maybe we create a Vike extension vike-opengraph that is based on https://vike.dev/head-tags#custom-settings.

I suspect others may just prefer unhead for familiarity coming from other ecosystems and frameworks

Yes it's an argument, although long-term it isn't as big of an argument if we manage to pull off a better DX than vue-unhead.

is this really something to implement ourselves? I've been using https://unhead.unjs.io/ for some time now and really like it

@4350pChris Indeed, for vike-vue using vue-unhead could have been a strategy. But in the React ecosystem I ain't aware of any library as good and as complete as vue-unhead.
Also, for simple use cases, I think (but I'm happy to be shown wrong) that our DX is simpler.
For advanced use cases, let's see if we can manage a better DX than vue-unhead. Speaking of which, do you see a missing use case from https://vike.dev/head-tags? Utilities for https://schema.org is on the radar.


Compatibility Test

Currently, ANT's compatibility test code is used in our research group internally.
The compatibility test's rule is to check if the target board is compatible with ANT and ready to run ANT APIs.
The test code should be released via this github repository.
We will upload the test code and status README file.

As I added compatibility test to this repository (#226), I close this issue.


Prepare for 0.11 link variants

We are currently linking to book and docs for the latest crates.io version and for master.
For the upcoming 0.11 release, we should probably leave the documentation for 0.10 in place for some time.
Affected files

generate.sh - docs need to be built for 0.10, 0.11 and master
src/config.toml - needs to store array instead of single tag
src/templates/doc.html - needs to loop over the array of doc targets

New links
We currently link to

https://book.amethyst.rs/stable/ and
https://docs-src.amethyst.rs/stable/amethyst/

Given that we'll have two stable releases then, I suggest to use /0.10 and /0.11, while redirecting to /0.11 for /stable.

Heya! Quick comment on this:
The website is not built by this script anymore, but instead by a build server that listens to github webhooks. I'll transfer it to the org asap, so that we can have that discussion over there.


make edge-impulse-config.json a hidden .edge-impulse-config.json file

might be nicer aesthetically if edge-impulse-config.json is a ~/.edge-impulse-config.json file

seconded!

not really tricky the code if it find the config in home should just move it to a hidden folder...  else just read from the hidden folder...

Ahh yeah, fair enough – definitely an edge case so probably no need to support aside from a printed warning, but a straightforward move would mess with anyone who also uses symlinks for their dotfiles ala mackup

Took a crack at a barebones approach that should hopefully allow people to convert the edge impulse config file into a dotfile without affecting others in this small PR

thanks @codeanpeace , I will review and see about pushing this upstream.


figma.enum cannot map to decimal numbers

Hello! I have an issue with the figma.enum when passing decimal numbers in the value. All the decimal numbers below will show 0 in Figma design. Is there any workarounds?
figma.connect(
  Component,
  'https://...',
  {
    props: {
      value: figma.enum('value', {
        '100%': 1,
        '75%': 0.75,
        '50%': 0.5,
        '25%': 0.25,
        '0%': 0,
      }),
    },
    example: (props) => <Component {...props} />,
  },
);

Code Connect CLI version: 1.0.4
Operating system: macos

Hi @stacysun-cb! Thanks for the message. We'll be adding support for this in an upcoming version.

This is now supported as part of the 1.0.6 release.


Honor installed package locale during winget upgrade --all

When I run winget upgrade --all the Windows Package Manager should try to honor the locale for the installed package.

Ahh, if you compare the urls from the Manifest and the one you found you can see the urls we use are from a archive
https://download-installer.cdn.mozilla.net/pub/firefox/releases/
Also i think i know of your issue, you want en-US, however your computer locale is something we do not inside of the manifest.
@denelon this is tiny annoyance i've noticed, i keep installing en-US however nb-NO keeps getting installed.
Originally posted by @OfficialEsco in https://github.com/microsoft/winget-pkgs/issues/65824#issuecomment-1183355282

I recently saw a report associated with Adobe.
The manifest contains the multi-language version of Adobe Reader, but when a user runs upgrade, the multi-language version is installed.

Same issue here, we have Adobe Reader EN version, so can't use winget as it will upgrade wit MUI package and kill our initial settings set using MST file. Thanks for those working on it.

[Policy] Command-Upgrade


Editing change recommendations

This allows editing the change recommendations. The line numbers are fixed, though.

Successfully tested.


StorageAPI agnostic from datastore

What would you like to have changed?
Currently the Storage interface makes many references to store items in a file system. Consider reducing the coupling to the file system.

What
Why
Workaround

In the Storage and Locker interfaces, the methods take key strings that are in the format of a filesystem path
This could make it difficult for different storage implementations to look up certificates. In the past, the Storage interface used the host as the way to reference a certificate/private key, why the switch away from this?
parse out the host from the key

In the Storage interface, List takes in a prefix and recursive
Consider removing the recursive options since it exists only for keys that are in filesystems
hacks to make this work  outside of filesystems

In the Storage interface, the Stat method returns a KeyInfo which has Size and IsTerminal
these are hard to compute for non-filesystem storage mechanisms
these don't appear to be used anywhere, so can always return 0 and false.

Why is this feature a useful, necessary, and/or important addition to this project?
Allows for non-file based storage implementations (eg: MySQL).

These are good questions/requests, thanks for the issue @dschwar.
The Storage interface is designed to work well with any key-value store, which includes a MySQL database and any other kind of database.

In the Storage and Locker interfaces, the methods take key strings that are in the format of a filesystem path. This could make it difficult for different storage implementations to look up certificates. In the past, the Storage interface used the host as the way to reference a certificate/private key, why the switch away from this?

The Storage interface is now used for more than just certificates and keys. If we didn't encode a structure into object keys, we'd have to create methods for every new kind of object we wanted to access/query from storage.

In the Storage interface, List takes in a prefix and recursive. Consider removing the recursive options since it exists only for keys that are in filesystems

Recursive is simply a traversal of the structure encoded in a key, it doesn't require traversing a file system. If there are keys "a/b/c" and "a/b/d" and we wanted to list "a" or "a/b", then it's simply a matter of returning the two keys, which in this case have that prefix (looking at whole parts of the "path" separated by /).

In the Storage interface, the Stat method returns a KeyInfo which has Size and IsTerminal | these are hard to compute for non-filesystem storage mechanisms. these don't appear to be used anywhere, so can always return 0 and false.

Hm, you seem to be right, that these are not used anywhere, at least within CertMagic. Caddy doesn't appear to use them either. This is worth looking into.

hacks to make this work outside of filesystems

Are there specific difficulties you are having? You refer to MySQL, but what's the actual problem?

The Storage interface is now used for more than just certificates and keys. If we didn't encode a structure into object keys, we'd have to create methods for every new kind of object we wanted to access/query from storage.

Have you considered making the types of objects stored in the datastore more concrete and then the implementation can decide how to store/retrieve the key based on the type desired? This would allow the implementor to decide whether to use prefixes or different tables.

Recursive is simply a traversal of the structure encoded in a key, it doesn't require traversing a file system. If there are keys "a/b/c" and "a/b/d" and we wanted to list "a" or "a/b", then it's simply a matter of returning the two keys, which in this case have that prefix (looking at whole parts of the "path" separated by /).

I don't feel like this is trivial to implement in a database.

Have you considered making the types of objects stored in the datastore more concrete and then the implementation can decide how to store/retrieve the key based on the type desired?

Yes, that is what Caddy used to do, and it was extremely difficult to work with.
I'm sorry if it appears difficult or confusing, but I don't think there's much we can helpfully do to simplify things at this point -- and there are already other implementations using the existing interface, and it works quite well, all it needs is some key-value store (and database tables can make good key-value stores).


apps sc: alert when no metrics are received from sc/wc

What this PR does / why we need it:
Adds alerts when no metrics are received from sc/wc cluster.
Which issue this PR fixes: fixes #799
Public facing documentation PR (if applicable)

Special notes for reviewer:
The query prometheus_tsdb_head_series{tenant!="",tenant!="default-tenant"} did not work for the alert. As it retained the latest value after metrics stopped coming in. However prometheus_tsdb_head_series{job="kube-prometheus-stack-prometheus"} went absent when no metrics came in.
Add a screenshot or an example to illustrate the proposed solution:
Checklist:

[x] Added relevant notes to WIP-CHANGELOG.md
[x] Proper commit message prefix on all commits
[ ] Updated the public facing documentation
Is this changeset backwards compatible for existing clusters? Applying:

[x] is completely transparent, will not impact the workload in any way.
[ ] requires running a migration script.
[ ] will create noticeable cluster degradation.
E.g. logs or metrics are not being collected or Kubernetes API server
will not be responding while upgrading.
[ ] requires draining and/or replacing nodes.
[ ] will change any APIs.
E.g. removes or changes any CK8S config options or Kubernetes APIs.
[ ] will break the cluster.
I.e. full cluster migration is required.

Chart checklist (pick exactly one):

[ ] I upgraded no Chart.
[x] I upgraded a Chart and determined that no migration steps are needed.
[ ] I upgraded a Chart and added migration steps.

Pipeline config (if applicable)
If you change some config options (e.g. add/rename variable or change the default value) you may need to update the config used by the pipeline in pipeline/config.

I had a lot of merge conflicts but i think it looks okay now. Please have a extra check :slightly_smiling_face:


Add support for STM32F4DISCOVERY Discovery kit and fix support for STM32F407XG

This PR fixes support for the STM32F407XG SoC and support for the STM32F4DISCOVERY Discovery kit board.
Documentation for the STM32F4DISCOVERY Discovery kit board is added based on the Nucleo F411RE format.

@erwango ok, But should I leave all the STM32F4DISCOVERY naming in the doc ? and only reference stm32f4_disco in the zephyr related text ?

Indeed, let it as is in doc.

Hi @fallrisk, It was dropped in the board renaming...

I'll rebase this PR once #126 is merged.

#126 is now merged


111

Vue version
11
Link to minimal reproduction
11
Steps to reproduce
1
What is expected?
11
What is actually happening?
1
System Info
No response
Any additional comments?
No response

Vue version
11
Link to minimal reproduction
11
Steps to reproduce
1
What is expected?
11
What is actually happening?
1
System Info
No response
Any additional comments?
No response


megasync: fix build with glibc 2.30

Motivation for this change
Fixes #81387
Things done

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

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

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

I didn't search hard enough first:

alternate fix: #80850
version update including another alternate fix: #81117 (upstream PR: https://github.com/meganz/MEGAsync/pull/313)

Resolved by #81117
Thank you @thefloweringash nevertheless.


crash with 1-float attribute vertex stream

forum thread : https://forum.babylonjs.com/t/bgfx-babylon-native-bug-when-using-float-vertex-buffer-shader-attribute/36158
Vertex stream with 1 float stream crashes BN (in shader creation as it looks) whereas using a vec2 instead works fine.

This does not crash on Windows FYI, but we reproed on another project on Android. (did not had a chance to test on IOS) but just to let you know it might be platform specific.

At least investigate what the problem is.

The problem seems to be related to a bug when glslang parsers an "AssignmentMultiplicationVectorByFloat" operation. The problem is not related to the usage of a float buffer itself, but to the instruction where the UV vec2 gets multiplied by a float.
Replacing the shader code with the code below make the code work and also uses a float vertex buffer:
BABYLON.Effect.ShadersStore["customVertexShader"]= "\r\n"+
		"precision highp float;\r\n"+

    	"// Attributes\r\n"+
    	"attribute vec3 position;\r\n"+
    	"attribute vec2 uv;\r\n"+
        "attribute float side;\r\n"+

    	"// Uniforms\r\n"+
    	"uniform mat4 worldViewProjection;\r\n"+

    	"// Varying\r\n"+
    	"varying vec2 vUV;\r\n"+

    	"void main(void) {\r\n"+
    	"    gl_Position = worldViewProjection * vec4(position, 1.0);\r\n"+

    	"    vec2 sidev = vec2(side, side);\r\n"+
        "    vUV = uv * sidev;\r\n"+
    	"}\r\n";

This bug seems to be related to glslang, maybe updating to a more recent version might fix it.

After updating glslang and SPIRV-Cross this issue was fixed. PR #1285


Dragging marines is too slow

If you are not injured and wearing light armor, you should be able to carry marines pretty easily. This ain't the case, and instead takes forever
Subscract efficiency if you're in the water

Tried using rollerbeds?

Actually I got baited by pixel movement
RMC dragging with light armor is faster than CM dragging with light armor
https://github.com/RMC-14/RMC-14/assets/122584947/6756df5a-0644-451f-8ead-731d425a543d


build: hotfix for release 0.31.0

Signed-off-by: Federico Di Pierro<EMAIL_ADDRESS>
What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If contributing rules or changes to rules, please make sure to also uncomment one of the following line:

/kind rule-update

/kind rule-create

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area rules

/area tests

/area proposals

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: FedeDP
To complete the pull request process, please assign jonahjon after the PR has been reviewed.
You can assign the PR to them by writing /assign @jonahjon in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

.circleci/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

.circleci/OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 32c6269175c2efd0b8a59cd8647a7eaa670c55ba

/milestone 0.31.0

@leogr: The provided milestone is not valid for this repository. Milestones in this repository: [0.32.0, 1.0.0]
Use /milestone clear to clear the milestone.

In response to this:

/milestone 0.31.0

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@FedeDP thank you :pray:
For the records: this PR tries to fix the issue we are having in the CI with the release pipeline :point_down:
https://app.circleci.com/pipelines/github/falcosecurity/falco/2056/workflows/86c23e3b-6bf8-4127-b984-2b571190f16f/jobs/18820

/hold

New changes are detected. LGTM label has been removed.

LGTM label has been added.  Git tree hash: c92b358dcbf7d994c48ffbf5627e4697a213f8ab

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, jasondellaluce, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

.circleci/OWNERS [jasondellaluce,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Closing and reopening to trigger the CI
/close

/reopen

@leogr: Reopened this PR.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


jB silentMode not working!

silentMode = true seems not having effect on any function.

Fixed with @ee72574059cde20bb0cf8430bb1aa8c7c48c1cf1


[eBPF] fix trace id

Phenomenon and reproduction steps
(Describe the phenomenon and scenario of the bug)
Root cause and solution
(Describe the cause of the bug and corresponding solution)
Impactions
(Visible changes after this fix)
Test method
(Test method to ensure the bug is fixed)
Affected branch(es)

main

Checklist

[ ] Dependencies update required
[ ] Common bug (similar problem in other repo)

f657087 异常
7563bb9 正常


Update mmctl-cli-tool.rst

Update for: https://github.com/mattermost/mattermost-server/pull/14561 and new command updates for https://mattermost.atlassian.net/browse/MM-25662.

@mgdelacroix: Do you have any additional content around "The way that the local mode operates on and specific requirements as running the CLI from the server folder must be documented, both externally and internally (within the CLI generated docs) if possible." I seem to recall there was some but now I can't find it.

@mgdelacroix: Do you have any additional content around "The way that the local mode operates on and specific requirements as running the CLI from the server folder must be documented, both externally and internally (within the CLI generated docs) if possible." I seem to recall there was some but now I can't find it.

The content we have is the local mode proposal, which describes how the feature works and the communication mechanisms that it uses.


Paper Submission to HICSS

Ava : Introduction on VR for training in health care , nursing and education
Brennan & Morgan : Implementation ; describe how the simulation works and objective framework
Professor Akram : Summary and proof read

Here are a few papers I've found thus far:
0177.pdf
0013.pdf

Final paper
2023-VRSNT.pdf


#831 : added optional text on placeholders

It says "Add link to "Sources" as well." In the issue.
Where do we expect this to link to? The documentation or the admin section?
@jesperweber @emilras

Tooltip added to api key label

I really like solution for this.
Now that we have the option we could maybe add it to the other fields as well?
Enterspeed endpoint - The value should be https://api.enterspeed.com
Media domain - Enter a custom domain (can include a path as well) if you want to use another domain than the Umbraco domain for your media files.
Preview API Key - Create a separate source in the Enterspeed app and provide the API key here.
What do you think?

I agree. Will get to it :)

@jesperweber Updated :)


Docker Error: Cannot find module 'libsql' - SQLite Adapater

Link to reproduction
No response
Payload Version
3.0.0-beta.73
Node Version
v18.20.2
Next.js Version
15.0.0-canary.53
Describe the Bug
I encountered an issue when trying to run a Dockerized Payload application using SQLite. The problem manifests differently on local machines and cloud platforms like Digital Ocean. Previously discussed here: https://github.com/payloadcms/payload/pull/7490#issuecomment-2269757066
Local Docker Environment:
Error: Cannot find module 'libsql'
Digital Ocean:
Error: Error relocating /app/node_modules/.pnpm/@libsql+linux-x64-musl<EMAIL_ADDRESS>fcntl64: symbol not found

This seems to be related to the issue discussed here: https://github.com/tursodatabase/libsql-client-ts/issues/112
Attempted Solutions:

Adding RUN pnpm i @libsql/linux-x64-musl to the Dockerfile did not resolve the issue.
I found that adding COPY --from=builder /app/node_modules ./node_modules to the Dockerfile's runner stage resolved the issue. However, this copies the entire node_modules directory, which is not ideal for image size optimization.

Additional Information:

I attempted to copy only the @libsql directory, but this did not work. I didn't have time to determine the exact minimum set of packages needed.
It appears that the Next.js standalone build is not including all necessary SQLite dependencies.

Reproduction Steps
Use Dockerfile below with a libsql:/ connection strin
FROM node:18-alpine AS base

FROM base AS deps
RUN apk add --no-cache libc6-compat
WORKDIR /app
COPY package.json pnpm-lock.yaml ./
RUN corepack enable pnpm && pnpm i --frozen-lockfile

FROM base AS builder
WORKDIR /app
COPY --from=deps /app/node_modules ./node_modules
COPY . .
ENV NEXT_TELEMETRY_DISABLED 1
RUN corepack enable pnpm && pnpm run build

FROM base AS runner
WORKDIR /app
ENV NODE_ENV production
ENV NEXT_TELEMETRY_DISABLED 1
RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 nextjs
COPY --from=builder /app/public ./public
RUN mkdir .next
RUN chown nextjs:nodejs .next
COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static
USER nextjs
EXPOSE 3000
ENV PORT 3000
CMD ["node", "server.js"]

Adapters and Plugins
db-sqlite

Hey @ainsleyclark can you share the Dockerfile you're using?

Hey, sure can it's below.
I've commented out the line that makes it work COPY --from=builder /app/node_modules ./node_modules
# From https://github.com/vercel/next.js/blob/canary/examples/with-docker/Dockerfile

FROM node:18-alpine AS base

# Install dependencies only when needed
FROM base AS deps
# Check https://github.com/nodejs/docker-node/tree/b4117f9333da4138b03a546ec926ef50a31506c3#nodealpine to understand why libc6-compat might be needed.
RUN apk add --no-cache libc6-compat
WORKDIR /app

# Install dependencies based on the preferred package manager
COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* ./
RUN corepack enable pnpm && pnpm i

# Rebuild the source code only when needed
FROM base AS builder
WORKDIR /app
COPY --from=deps /app/node_modules ./node_modules
COPY . .

# Next.js collects completely anonymous telemetry data about general usage.
# Learn more here: https://nextjs.org/telemetry
# Uncomment the following line in case you want to disable telemetry during the build.
ENV NEXT_TELEMETRY_DISABLED 1

RUN corepack enable pnpm && pnpm run build

# Production image, copy all the files and run next
FROM base AS runner
WORKDIR /app

ENV NODE_ENV production
# Uncomment the following line in case you want to disable telemetry during runtime.
ENV NEXT_TELEMETRY_DISABLED 1

RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 nextjs

COPY --from=builder /app/public ./public

# Temp - SQL Lite
# COPY --from=builder /app/node_modules ./node_modules

# Set the correct permission for prerender cache
RUN mkdir .next
RUN chown nextjs:nodejs .next

# Automatically leverage output traces to reduce image size
# https://nextjs.org/docs/advanced-features/output-file-tracing
COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static

USER nextjs

EXPOSE 3000

ENV PORT 3000

# server.js is created by next build from the standalone output
# https://nextjs.org/docs/pages/api-reference/next-config-js/output
CMD HOSTNAME="<IP_ADDRESS>" node server.js

Discord chat in Turso:
https://discord.com/channels/933071162680958986/1270099510202335233
I haven't tested this tho.

This is not only happening in docker, I tried starting a new project running:
npx<EMAIL_ADDRESS>
And when I ran pnpm dev I got the same error on my browser when trying to access the admin.
But after a couple of tries of running pnpm i and then pnpm dev, it worked, specifically after restarting vscode, which to me makes no sense, but I'm just sharing my experience in case it's useful.

I'm running Node v20.17.0 on an M1 Mac.

I'm running on this issue, this is my dockerfile:
# Base image with Node.js
FROM node:22-alpine AS base

# Install dependencies
FROM base AS deps
RUN apk add --no-cache libc6-compat
WORKDIR /app

# Copy package manager files and install dependencies
COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* ./
RUN \
    if [ -f pnpm-lock.yaml ]; then \
    corepack enable pnpm && pnpm i --frozen-lockfile; \
    else \
    echo "Lockfile not found." && exit 1; \
    fi

# Build the Next.js application
FROM base AS builder
WORKDIR /app
COPY --from=deps /app/node_modules ./node_modules
COPY . .
ENV NEXT_TELEMETRY_DISABLED=1
RUN \
    if [ -f pnpm-lock.yaml ]; then \
    corepack enable pnpm && pnpm run build; \
    else \
    echo "Lockfile not found." && exit 1; \
    fi

# Final stage: Set up the runtime environment
FROM base AS runner
WORKDIR /app
ENV NODE_ENV=production
ENV NEXT_TELEMETRY_DISABLED=1

# Create and set the application user
RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 nextjs

# Copy the built files from the builder stage
COPY --from=builder /app/public ./public
# Change ownership of the public directory to the application user
RUN chown -R nextjs:nodejs ./public

# Setup directories and permissions for runtime
RUN mkdir .next
RUN chown nextjs:nodejs .next
COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static

# Switch to non-root user
USER nextjs

# Expose the port the app runs on
EXPOSE 3000
ENV HOSTNAME=<IP_ADDRESS>

# Command to run the application
CMD ["node", "server.js"]

And once I added
    "libsql": "^0.4.6",
    "@libsql/client": "^0.14.0",

I get the following error when running the docker container:
 ⨯ [Error: Cannot find module '@libsql/linux-arm64-musl'
Require stack:
-<EMAIL_ADDRESS>{
  code: 'MODULE_NOT_FOUND',
  requireStack: [Array]
}

It's running on a Mac M3 but i get similar error on the x86 server on hetzner

It is important to install the @libsql/client package into your own project. For anyone experiencing this issue, please check and make sure that your have this as a dependency in your package.json.
If this doesn't resolve your issue, you can tag me and we will look into it more.