daemon: Define CILIUM_ACCESS-LOG and CILIUM_ACCESS-LABELS env vars

Fixes: https://github.com/cilium/cilium/issues/3751
Signed-off-by: Romain Lenglet<EMAIL_ADDRESS>

test-me-please

@rlenglet I think this will need back porting. Adding the necessary label.

Sure. I guess the real question is do you think the other commit and this one needs to be back ported. If not then we are good

@aanm Good point about - vs _. I'll fix the names of environment variables.
But unfortunately the special logic in viper to lookup the environment variables is only called from viper.Get, and it doesn't set flag variables automatically from env variables. So if we replace viper.Get* calls with flag variables like I did, the env variable is ignored unless we explicitly call viper.BindEnv.

I think calling viper.BindEnv is better anyway, since it documents explicitly which env variables are supported.

@manalibhutiyani neither commit needs backporting. Thanks!

test-me-please

test-me-please

@rlenglet We have [0] which should pick all of the flags, doesn't that work?
[0]
	viper.AutomaticEnv()           // read in environment variables that match

@aanm The problem is that this works only when we call viper.Get* directly. Calling viper.AutomaticEnv() doesn't set the variables of declared flags. Makes me doubt the usefulness of viper.AutomaticEnv() altogether.

@rlenglet yep, you are right, accordingly with the docs:
AutomaticEnv is a powerful helper especially when combined with SetEnvPrefix. When called, Viper will check for an environment variable any time a viper.Get request is made. It will apply the following rules. It will check for a environment variable with a name matching the key uppercased and prefixed with the EnvPrefix if set.

@rlenglet The requirement of the Fixes tag is unrelated to our current decision to backport or not. If the faulty commit ever gets subject to be backported it needs to be clear what dependencies it has. Please add a fixes tag to the commit message.

Green build: https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/2438/

test-me-please

Sorry, didn't see that the CI is still ongoing, removing read-to-merge label again

I just wanted to have a 2nd green build...

@rlenglet Are you sure using '-' in env variable names is a good idea? Typically it is avoided, IMO.

@jrajahalme That's how viper matches flag names to env variable names. Apparently we've been relying on those names, so we can't change them anymore.

On Apr 16, 2018, at 2:10 PM, Romain Lenglet<EMAIL_ADDRESS>wrote:
@jrajahalme https://github.com/jrajahalme That's how viper matches flag names to env variable names. Apparently we've been relying on those names, so we can't change them anymore.

IMO it would be better to double-check the need to keep using those names. Viper examples do not use underscores and the docs refer to the ability to set up a formatter/filter to translate underscores to dashes. If we absolutely must keep them, we should deprecate them now and somehow support both spellings and hopefully get rid of the env variables with dashes in some future.
The problem with dashes is that I have not yet been able to figure out how to set an environment variable with a dash in it’s name. Indeed, according to https://unix.stackexchange.com/questions/23659/can-shell-variable-include-character/23714#23714 https://unix.stackexchange.com/questions/23659/can-shell-variable-include-character/23714#23714 it is not even possible. So I wonder how can we be depending on those old names?
Jarno

The problem with dashes is that I have not yet been able to figure out how to set an environment variable with a dash in it’s name. Indeed, according to https://unix.stackexchange.com/questions/23659/can-shell-variable-include-character/23714#23714 https://unix.stackexchange.com/questions/23659/can-shell-variable-include-character/23714#23714 it is not even possible. So I wonder how can we be depending on those old names?

Wow, so viper is literally broken for the majority of flags using AutomaticEnv(). I agree with Jarno. No point in guaranteeing this compatibility.

Removing the call to viper.AutomaticEnv().

test-me-please

3rd green build: https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/2458/


chore: Bump Karpenter Version

Fixes #N/A
Description

Bump to include these two PRs:
https://github.com/kubernetes-sigs/karpenter/pull/1141
https://github.com/kubernetes-sigs/karpenter/pull/1148

How was this change tested?

/karpenter snapshot

Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

13 of 13 (100.0%)  changed or added relevant lines in 5 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.07%) to 82.243%

Files with Coverage Reduction
New Missed Lines
%

pkg/providers/amifamily/ami.go
1
90.32%

Totals

Change from base Build<PHONE_NUMBER>:
-0.07%

Covered Lines:
5331

Relevant Lines:
6482

💛  - Coveralls


The modal window with images appears two times.

Hi everybody,
could you help me to figure out why the modal window with images gallery appears two times on the page?
I call my JS function ones to generate a lightbox gallery:
function initLightboxForImages(elemId) {     document.querySelectorAll(elemId + ' a.detail_img').forEach(el => el.addEventListener('click', (e) => {         e.preventDefault();         const lightbox = new Lightbox(el);         lightbox.show();     })); }
The images on the page (see attached file)
When there is one image for showing, the modal window appears one time.
When there are more than one picture, the modal window appears two times.

I click on image from the other modal window, which appeared before. Maybe some collision with other modal window?
Thank you!

I just did in the wrong way.
Here is the right way:
function initLightboxForImages(elemId) {     const lightbox = new Lightbox();     document.querySelectorAll(elemId + ' a.detail_img').forEach(el => el.addEventListener('click', Lightbox.initialize)); }


Add REQUIRES: distributed to runtime_discoverable_attrs_distributed.swift

The test is using the distributed capabilities, but it is not marked as such. If someone is not building with the distributed features enabled, the test will fail for them.

@swift-ci please test


Version update on microsoft/setup-msbuild not detected from 1.0.2 to 1.1.3

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
github-actions
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
Workflow file with multiple steps, where one of them is to setup MS Build:
    steps:
    - name: Setup MSBuild
      uses<EMAIL_ADDRESS>
dependabot.yml content
version: 2

registries:

  nuget-org:
    type: nuget-feed
    url: https://api.nuget.org/v3/index.json

  github-packages:
    type: nuget-feed
    url: xxxxxxxxxxxxxxx
    token: ${{secrets.xxxxxxxxxxx}}

updates:

  - package-ecosystem: "nuget"
    directory: "/"
    registries: "*"
    schedule:
      interval: "daily"

  - package-ecosystem: "github-actions"
    directory: "/"
    schedule:
      interval: "daily"

Updated dependency
microsoft/setup-msbuild from version 1.0.2 to 1.1.3
What you expected to see, versus what you actually saw
Dependabot has over the last months created a lot of updates for all other GitHub Action steps, but we noticed that the package for setting up MSBuild was never updated.
Dependabot update log shows that it finds that 1.0.2 is used, and that there are no updates:
updater | INFO <job_485702128> Checking if microsoft/setup-msbuild 1.0.2 needs updating
  proxy | 2022/10/18 05:20:31 [016] GET https://github.com:443/microsoft/setup-msbuild.git/info/refs?service=git-upload-pack
  proxy | 2022/10/18 05:20:31 [016] * authenticating git server request (host: github.com)
  proxy | 2022/10/18 05:20:31 [016] 200 https://github.com:443/microsoft/setup-msbuild.git/info/refs?service=git-upload-pack
updater | INFO <job_485702128> Latest version is c26a08ba26249b81327e26f6ef381897b6a8754d
updater | INFO <job_485702128> No update needed for microsoft/setup-msbuild 1.0.2

When manually getting the content of the GET request, the result indeed shows that there are newer packages, and that version 1.1.3 is the newest:
001e# service=git-upload-pack
000001560b44c6745b7e81956596964100aadb92d667c497 HEAD multi_ack thin-pack side-band side-band-64k ofs-delta shallow deepen-since deepen-not deepen-relative no-progress include-tag multi_ack_detailed allow-tip-sha1-in-want allow-reachable-sha1-in-want no-done symref=HEAD:refs/heads/master filter object-format=sha1 agent=git/github-gcaaf1c4b6630
005b0fc2502ca49f277016260bdd89c70e0c16a7cf4e refs/heads/dependabot/npm_and_yarn/ajv-6.12.6
006db7835cef05cc81bdb8c67ea14346cdcd7c89fd81 refs/heads/dependabot/npm_and_yarn/json-schema-and-jsprim-0.4.0
005b1d97ad85a9755ff291da008c63fe2b08238535e5 refs/heads/dependabot/npm_and_yarn/tmpl-1.0.5
003c6a8fedefe94395d1c2193b87c6d83224d6e87569 refs/heads/dev
003f0b44c6745b7e81956596964100aadb92d667c497 refs/heads/master
003ffc16ae6170877cd889e5d735ea9d41c2362078b2 refs/heads/v1.0.0
003f8dc49dbd173d2e84b142c0b65eef06ad36ccc82c refs/heads/v1.0.1
003fc26a08ba26249b81327e26f6ef381897b6a8754d refs/heads/v1.0.2
003f9546707e6b8f513d3a2af998e51e3b995c9fbe81 refs/heads/v1.0.3
003fab534842b4bdf384b8aaf93765dc6f721d9f5fab refs/heads/v1.1.0
003fb381dbabab030b2d16c2c87be6e0fdfadb75628a refs/heads/v1.1.1
003fd6496d378fd258c01b23231ffff1e73808f126e7 refs/heads/v1.1.2
003f34cfbaee7f672c76950673338facd8a73f637506 refs/heads/v1.1.3
003e2008f912f56e61277eefaac6d1888b750582aa16 refs/pull/1/head
003f93e160075a116879b0927816549540701146b3e5 refs/pull/11/head
003fc4f3bee2c44d35fbdd918d508c6bca44132fad82 refs/pull/12/head
003fc9ef9479351644e79a048f53964bbd9d357ead05 refs/pull/14/head
003f9c9a1a34a4c6a9f36400e23e479b9c33ec98a4bb refs/pull/15/head
003ff05df80b32f8b835cfbd3b002f3bb3f59f9a4d43 refs/pull/16/head
003f341cfb53e30b7748ba6bfdf007e641462556042a refs/pull/17/head
003f0d4f73260bc92ffdfd6052dd962cc5ccb954575b refs/pull/19/head
003f06c9a7f31c273c6a22e43aa4e92c2a185a4d9dee refs/pull/21/head
003fe82103acef14ac8c7dd76d6997a4ba7cfda1bcfc refs/pull/22/head
004028d2c305055d6141bd15ff04523719117a574a48 refs/pull/22/merge
003f0b5643901b0999aee1e981a4ae1c8bbf7e90484d refs/pull/23/head
003fa0858ffef3d2e5dd0a5d785f4875c4b6285add75 refs/pull/25/head
003fcbeaa72a9f112eb29acac0430556277b10e00a49 refs/pull/31/head
003f4813f144a2145028fee526004a6b6aac0c2d80a5 refs/pull/37/head
003f1c5a706e2695e453c6919dd43f598dbd445b73d6 refs/pull/39/head
003ff00648bcdcfd5713fb8347b4f927ad51fbafc8c7 refs/pull/40/head
003f7626c90a395f6403e9bf21ea09cd14ef7f000931 refs/pull/46/head
003fbabd7930ed54e6f5cb5f9ee592b6031216cb4255 refs/pull/51/head
003f9afe006fef5dd1c8b6ab1eae71caec99bb2f7e5c refs/pull/52/head
003f047d9a067883f2e2ea6cd9a08bbc2b2d6bbeddb5 refs/pull/53/head
003f455ec54ae7025c970e5fc4dc9a14283e7298883f refs/pull/56/head
003f412f2703681bd1e2107f511ab857c92252afb803 refs/pull/57/head
003e43cd4ebaecd8cd9bf7c95fc18edbdba1252d7482 refs/pull/6/head
003f9546707e6b8f513d3a2af998e51e3b995c9fbe81 refs/pull/60/head
003f2cbcfcb79598175f7aebe742012225f5a8657d31 refs/pull/61/head
003f1d97ad85a9755ff291da008c63fe2b08238535e5 refs/pull/62/head
00402667aad3e9773cef990d798a6286b44fd72b17f4 refs/pull/62/merge
003f84e0d709b2c782782b075c1f5a7173b76b6115b2 refs/pull/65/head
003f281b95dea87d381cd268f481dc51b7ef5da8fa04 refs/pull/66/head
0040cd91c225762ecb1e922c2b7474c80b35be65019c refs/pull/66/merge
003fce3de01b52669a228622f9e280b9f068c7cf4163 refs/pull/68/head
003f0fc2502ca49f277016260bdd89c70e0c16a7cf4e refs/pull/75/head
00402f7844feb6aa4bf20998c09b4b94ba3b261d970a refs/pull/75/merge
003f7a1ab92e6cf81d5a6b4797ad4c4dd0cfcb428e80 refs/pull/87/head
003f50f8578df565ecf193e9bbbf6acd76c66b34d92e refs/pull/89/head
003e70efaa8b2d06055da6239191f0ae35144119b4c5 refs/pull/9/head
003fd6496d378fd258c01b23231ffff1e73808f126e7 refs/pull/90/head
003fb7835cef05cc81bdb8c67ea14346cdcd7c89fd81 refs/pull/91/head
00408199e0cbd1e75594a89361cf458ee38b093fa95a refs/pull/91/merge
003f71b0754fb20d8beb7590e2cd1a91a12bbda4324f refs/pull/92/head
003f34cfbaee7f672c76950673338facd8a73f637506 refs/pull/94/head
003a127f7c3fc66419bb77fc6703c497db0e1e3e8c74 refs/tags/v1
003d34cfbaee7f672c76950673338facd8a73f637506 refs/tags/v1^{}
003e8dc49dbd173d2e84b142c0b65eef06ad36ccc82c refs/tags/v1.0.1
003ec26a08ba26249b81327e26f6ef381897b6a8754d refs/tags/v1.0.2
003e9546707e6b8f513d3a2af998e51e3b995c9fbe81 refs/tags/v1.0.3
003c4ec49e314e52344e4b6e3aba15a3c519f7129419 refs/tags/v1.1
003f34cfbaee7f672c76950673338facd8a73f637506 refs/tags/v1.1^{}
003ed6496d378fd258c01b23231ffff1e73808f126e7 refs/tags/v1.1.2
003e905a7b699b34b9b34158ec6b839167581ce1db62 refs/tags/v1.1.3
004134cfbaee7f672c76950673338facd8a73f637506 refs/tags/v1.1.3^{}
0000

Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response

Thanks for the report, I can reproduce it, let me see why this is.

This action pushes a branch with the same name for every tag, so understandably confuses dependabot 😅, I'll open a PR to fix this now.

This action pushes a branch with the same name for every tag, so understandably confuses dependabot 😅, I'll open a PR to fix this now.

I noticed that, and wondered if the equally named branches could have anything to do with this 😇
Thanks, @deivid-rodriguez, for both confirming the issue and working on a fix! 🚀

No worries! #5918 should hopefully do the trick :)

Just to confirm, in case anyone stumbles onto this case in the future:
The fix definitely did the trick, and dependabot opened new pull requests the day after this change was released 😀👍


about d4xx_to_mavlink_3D.py and mavros

hi, I want to use mavros to connect fcu and missing planner,
firstly, I run
roslaunch mavros apm.launch fcu_url:=/dev/ttyACM0:57600<EMAIL_ADDRESS>and It,s work,
secondly,I run
./d4xx_to_mavlink_3D.py --debug_enable 1
the connect between FCU and Missing Planner is disconnect.
if I close the second step, the connection will established at the same time.
how could I implement both functions at the same time.
any adivice. thanks


Unable to setup temurin with gitea actions runner

Description:

- name: Setup JDK
  uses: actions/setup-java@v4
  with:
    distribution: 'temurin'
    java-version: '17'

This is using the Gitea actions runner, so I'm unsure if this is exclusives to this setup.
Task version:
4
Platform:

[x] Ubuntu
[ ] macOS
[ ] Windows

Runner type:

[ ] Hosted
[x] Self-hosted

Repro steps:
- name: Setup JDK
  uses: actions/setup-java@v4
  with:
    distribution: 'temurin'
    java-version: '17'

Expected behavior:
JDK to find temurin jdk 17
Actual behavior:
No distributions found

looks like this was due to unicode quotes being pasted when I copied the with block


Sizeof of buffer or pointer?

void SI7021::_command(byte * cmd, byte * buf ) {
_writeReg(cmd, sizeof cmd);
_readReg(buf, sizeof buf);
}
I does not understand the sizeof  of buf , it seems that you ask size of a pointer and not buffer length,
is this correct ?
i think that the correct function should be _command(byte * cmd,int cmdlen, byte * buf ,int buflen);

This is now fixed with this update.


Adding QueryParameter support in BigQuery

Also, adding DATE, TIME, and DATETIME support for legacy SQL types.
Fixes #1411

Coverage increased (+0.006%) to 83.518% when pulling 6271268f486e545f6a490713a09412fb3aeea675 on garrettjonesgoogle:master into b24ec1af5f616b6f412d6ba172b45169d45ffdeb on GoogleCloudPlatform:master.

Coverage increased (+0.006%) to 83.518% when pulling 38451c226dd8e4173c0dae1b4d75e4166549990c on garrettjonesgoogle:master into b24ec1af5f616b6f412d6ba172b45169d45ffdeb on GoogleCloudPlatform:master.

I decided to add the missing types TIME/DATE/DATETIME into LegacySQLTypeName to resolve #1388 .

Coverage increased (+0.008%) to 83.52% when pulling 0173f63ed5266f7dade9794908fbea12ce896b39 on garrettjonesgoogle:master into b24ec1af5f616b6f412d6ba172b45169d45ffdeb on GoogleCloudPlatform:master.

I decided to add the missing types TIME/DATE/DATETIME into LegacySQLTypeName to resolve #1388

Update PR description?

Description updated.

Review comments addressed - PTAL

Coverage increased (+0.05%) to 83.559% when pulling 179132bfc3a4fd9a98e7eb70a2aab0742a6b8a3e on garrettjonesgoogle:master into b24ec1af5f616b6f412d6ba172b45169d45ffdeb on GoogleCloudPlatform:master.


Some improvements

How do you feel about these changes?

added to package.xml - the "when" conditions
added the description to readme (using the F5 -> reload window workflow to develop the extension)

closed because it contains unrelated commits


Mkirk/debug

[x] I agree to follow the project's code of conduct.
[x] I added an entry to CHANGES.md if knowledge of this change could be valuable to users.

Based on #53, so review that first.
I'm not actually sure if we should do this. Or if we should maybe go even farther and have "WktFloat: Display  + FromStr + Default" as well. Since we're bumping API anyway, thought it might be a good time to sneak it in.
It's not clear to me how useful the crate would be for numeric types that didn't implement all of these things.

bors r=frewsxcv

bors r=frewsxcv


Bump version to 9.6.0

Bring version up to date

OK, I think it's good to go now

@valadas @donker we want to merge this back into develop now, right?

@valadas @donker we want to merge this back into develop now, right?

Yes. But I am not confident enough I'll do that without breaking something ...

Hmm, I was not involved in this one here, usually we only only want to merge stuff into master from a release branch. I don't think it would be a huge issue to merge this into develop, but in a few days when we do merge the release/9.6.1 into both master and develop, we will get 9.6.1 on both. My only concert is the issue template, I worked some automation (more coming up when I get some time) and we will need to try to avoid manual edits in the version list section. I am relying on the present of a line with "alpha" and a line with "latest supported release" to automate on 3 events:

Add the rc as soon as a release branch is created
Remove the rc and update the latest as soon as we publish a non-rc version
Maybe or maybe not automate for the future/xx branches (this changes less often)

Oh, nevermind my comments here, I am late on notifications and this was already done...


use_argsfile_at_link to use response file for a large number of objects.

Reworked #41 after rebasing on top of up-to-date upstream prelude.

tested with 9k modules.


Chapter 14  Improving Accessibility - useActionState is not available in React

Uppon importing useActionState like so:
import { useActionState } from 'react';
The following error appears:
Module '"react"' has no exported member 'useActionState'.ts(2305)
When searching on Google, the official React Documentation actually says that the useActionState is still an experimental feature in their Canary channel.
I assume this means that when using the stable version of React, this Hook is not available yet and can therefore not be used.
If I am completely wrong on this topic, please explain me what I am doing wrong! I'm not doing this course because I am so good at this all already ;)

I am not able to reproduce, can you share more about what you're seeing? Can you restart your TypeScript server?

@dtknepper - Ran into something similar, @leerob 's suggestion to restart the Typescript server solved it on my end
The following steps may be helpful

Copy final-example's package.json
Run pnpm i to install latest dependencies
Restart Typescript server using cmd + shift + p and select TypeScript: Restart TS Server

After the TypeScript server restarts, ideally useActionState is defined

I have updated all my dependancies, and I still get this error. I was however able to still continue with this project by using useFormState from the react-dom dependancy.
@braxtonb I see in you screenshot that you actually use the Canary release of React and not the general release. That's why you do not get this error.

What are we supposed to do to get this working? Without the useActionState hook the entire tutorial grinds to a halt at chapter 14.

@leerob honestly, I think it's quite weird to depend on a canary release for a tutorial that is made for beginners. Especially since there is never a mention of using this version as the NPM command to start the project is using the latest stable release and not the canary version. The command to start this tutorial is: npx create-next-app@latest nextjs-dashboard --example "https://github.com/vercel/next-learn/tree/main/dashboard/starter-example" --use-pnpm On top of that using a canary version which is most likely still quite buggy for a beginner tutorial is not the smartest thing in my humble newcomer opinion.
@bwarman the easiest thing to do, is to use useFormState instead of the useActionState and change the import from react to react-dom. This will give almost the same behaviour.

I just encountered this error myself.
I'm coming from a jQuery / old-school JS background and the zoo of dependencies, versions, and related errors is making it really hard for me to feel good about trying Next in any real capacity.
I think it's best to keep the tutorial as stable as possible rather than bleeding edge.

@bwarman have you already restarted your TS server or the steps mentioned above?

the NPM command to start the project is using the latest stable release and not the canary version.

This is the npx command, which is a separate project (create-next-app is a CLI tool), which pulls the code for the specific example codebase as an argument.
If you would prefer to use useFormState, you can reference this PR and use the codebase at deca7c7.

hey there i faced the same issue with the useActionState and couldn't find out how do i resolve it
if there's any resolution regarding the error please let me know I'm looking forward to complete this whole course

@Sahil4883
https://github.com/vercel/next-learn/issues/775#issuecomment-2226848274
You can try useFormState to solve it

@bwarman have you already restarted your TS server or the steps mentioned above?

the NPM command to start the project is using the latest stable release and not the canary version.

This is the npx command, which is a separate project (create-next-app is a CLI tool), which pulls the code for the specific example codebase as an argument.
If you would prefer to use useFormState, you can reference this PR and use the codebase at deca7c7.

or you could just make the tutorial work? you realized if you just clone the repo and run npm install it has dependecies errors and cant even build?

@bwarman have you already restarted your TS server or the steps mentioned above?

the NPM command to start the project is using the latest stable release and not the canary version.

This is the npx command, which is a separate project (create-next-app is a CLI tool), which pulls the code for the specific example codebase as an argument.
If you would prefer to use useFormState, you can reference this PR and use the codebase at deca7c7.

Do you realized that if someon clones the repo

@bwarman have you already restarted your TS server or the steps mentioned above?

the NPM command to start the project is using the latest stable release and not the canary version.

This is the npx command, which is a separate project (create-next-app is a CLI tool), which pulls the code for the specific example codebase as an argument.
If you would prefer to use useFormState, you can reference this PR and use the codebase at deca7c7.

sounds like excuse to me. npm run install fails on a fresh clone of the repo. thats what it is.

This worked for me: npm i<EMAIL_ADDRESS>npm install --legacy-peer-deps next@rc react@rc react-dom@rc

Thanks man.

React 19 (and types) are now stable: https://github.com/vercel/next-learn/pull/946


Add Support for File Uploads

Small file uploads as base64 will be great to add to the panel.

It was planned originally but was not asked from the community.
Closing for now.


Feature Request: Add Auto-Update feature for an Insiders edition for Terminal

Summary of the new feature/enhancement
I would like to see an Insiders edition made that updates daily like VSCode. Otherwise a model similar to MS Edge and VS Code extensions:  Monthly: stable, beta: weekly, and alpha: daily.
 If not updating from the Store (preferably it wouldn't matter), being able to get changes from either clicking "Update" (manual update) or automatically updating (configurable in settings) would be highly desired. ConEmu has this feature and it's great but I'd prefer Windows Terminal.
Proposed technical implementation details (optional)
ConEmu has it going directly to the github release page. This would probably be best for Windows Terminal as well.  We don't have a stable yet but alpha can be auto-built binaries created daily at midnight EST or whatever time the Console team feels is appropriate. Beta would be auto-built binaries made weekly. These auto-built binaries would have a summary listing all PRs (which you could click on and examine yourself if desired) that were made since the last binary. An auto-delete feature would need to be in place for daily binaries to prevent the list from getting too long. Basically once a new binary was built, the previous one would be deleted (with some checks ensuring the build was successful and can be run and logic checking if no PRs were made that day, then don't create a new build).
A clear and concise description of what you want to happen.
In the About dialog or in the new settings UI that's getting built, provide an option to update with a "Check for updates" option. A setting for automatically checking and installing updates if available.

To provide incentive: https://github.com/microsoft/terminal/issues/279#issuecomment-439179675

In our team's ideal world, you would all be running the latest console bits everywhere everytime we make a change. But that's just not how it is today.

You can do this for Terminal unlike Console.

To add to this a bit, an MVP for public nightly builds could use the new auto-updated for sideloaded apps feature. You basically just stick your .appx (and dependencies) at a URL somewhere, and stuff that URL into the appxmanifest.

msix will work with this as well. Also  App Installer won't be available on the earliest builds of Win 10 and Terminal is support all versions that go back to Anniversary Update (and Win 7/8.1 from what I've seen in recent PRs from external contributors).

@zadjii-msft any estimate on when this can be looked at?

@WSLUser anybody can look at this, not just Microsoft staff. Open source! Wouldn't you rather they be working on advancing the terminal instead of screwing around with auto updates, just so they can create an entirely new stream of complaints? Someone in the community should take ownership of this.

Yes and this would help with testing all the flux. I’m not much of a C programmer or I’d take a crack at it.  I agree anybody could look at this. Just want to be sure it isn’t one of those issues that slips through the cracks.

There is just about 0% chance this happens before 1.0. There's currently 128 open issues that we've marked for 1.0, and I'm sure there's plenty more that we haven't tracked properly yet. At the moment we're focusing on flushing out and polishing the terminal experience it is. Building and maintaining an auto-updater would detract from that work, and unfortunately none of us have any experience doing that, so it'll take extra long to make sure we research the options and deploy the correct one.
Now, if the community wanted to hop on and lend their expertise, that would certainly be appreciated.

Couple things here. Our target for v1.0 is distribution primarily via the store. The store provides both "automatic updating" and gated flight rings for insiders to join. I know it's not ideal for a subset of the population, but we've made this choice to focus our engineering efforts.
We'll re-evaluate this in the future. For now, I'm going to close this one out.
Thanks everything.

So currently, the biggest hurdle is getting CD from Azure Pipelines.  Understanding how there are many other competing priorities that take precedent is understandable. Half of this challenge is simply in getting updates to the Release page more frequently. Once that's done, somebody could come in and do the other half of the work to have it do a check against the Release page and if the commits don't match, download and update the existing installation. All you guys need to do is set up CD so that it produces an msix that is then posted to the Release page of this repo. Then configure it to do it automatically every few days and clean up the previous version if possible. If not, then it can be dealt with later. I don't think the setting up of the deployment on an interval should take too much time and effort within Azure Pipelines. Can you guys look at that at least?


Add: feature that will create new readme file for each play at the time of creating play

Description
Added a new file in the plop-templates which will define the heading of the readme of each play
Fixes #(47)
Type of change
Added Feature
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
yarn create-play by creating a sample play (Deleted it afterwards)
Checklist:

[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Tapas sir i've made the changes which you gave me


Lightweight architecture decision records

Summary
We need a way to record decisions (and the conversations around those
decisions) in a durable, discoverable format. Architecture Decision
Records (ADRs) are a way to record "significant" decisions made about
the technical architecture of our service, as well as the context around
those decisions, any alternatives that were considered or explored, and
the pros/cons that might be worth remembering.
We don't want to introduce a lot of complexity, so it seems beneficial
to keep this process very lightweight. In that vein, we will look at the
Lightweight Architecture Decision, as discussed here:
https://www.thoughtworks.com/radar/techniques/lightweight-architecture-decision-records
http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions
This does not involve an undue burden of detailed documentation, but
recommends preserving, concisely, the context of the problem, the
decision taken, the alternatives considered, and the consequences of the
chosen solution.

Done @frankieroberto 👍

Is the "ADR tool" this one...?
https://github.com/npryce/adr-tools
Are we really going to write these using vim or nano, which seems to be the helpful thing it does?

@TheDoubleK yep, that's the adr-tools I used. Definitely don't need to use it. It's probably easier to just make a copy of the 0000 template and rename it. adr-tools doesn't seem to add much value as a cli tool, IMO.

Damn these failing tests though.  I had a weird one on my PR too - different from this though, some issue with coveralls.


Night vale weather

Re-add "And now to hallo with the weather"
use youtube API
part=snippet
maxResults=50
playlistId=PL5bFd9WyHshXpZK-VPpH8UPXx6wCOIaQW
Remember to use nextPageToken as pageToken to get further pages of playlist
We only need snippet.title and snippet.resourceId.videoId but I don't know if we can only request that

fields = items(snippet/title,snippet/resourceId/videoId)

https://github.com/joshcoales/Hallo/pull/123


Improve port usage for tinylicious and unit test

TCP hangs on to a port after it close for a period of time to avoid message being delivered after.
If we make a lot of HTTP request, that create a lot of TCP connection.  The unit test is an example.
Also within tinylicious, even though that it is monolithic, it is still a bundling of multiple microservices. So call to historian is still done thru HTTP request even though they are the same process.
To avoid port exhaustion, set the HTTP connection to keep alive so that it can be reused, instead of closing and creating a new one.
The change set those flag globally for the unit test and tinylicious.  We might want to consider making this more targeted and configurable in the future.
Related to issue #5098
Note: I am able to run the mocha e2e test with --parallel --jobs 2 now.  Not enabling it because there are still instability.

/azp run Build - client packages


Using loop-inversion to optimizes translation overhead for while loops

Prerequisite: #620
Before:

After:

There are still some issues that need to be fixed.
Updates: the tests are still blowing up

Closing since IVT is in main now


Camera Input Change Required in Zoom

ℹ Computer information

PowerToys version: Pre-release 0.22
PowerToy Utility: VideoConference
Running PowerToys as Admin: Yes
Windows build number: 18363.1016

📝 Provide detailed reproduction steps (if any)

Install Prerelease
Open Zoom and create a new meeting
Attempt to use the Win + N or Win + Shift + O hotkey. Camera does not change
Change the camera input on bottom left of Zoom tool bar to "PowerToys VideoConference" and repeat Step 3 to get an expected result.

✔ Expected result
Camera turns on or off
❌ Actual result
No change to the camera. Overlay image says "Camera not in use" even if your camera is on in the meeting.
📷 Screenshots

@Checkmate363

Attempt to use the Win + N or Win + Shift + O hotkey. Camera does not change

The camera is not expected to change. You have to manually choose the PowerToys camera.
Can you please clarify if after changing the camera in Zoom is still not muting when pressing one of the muting shortcut?

I was unaware that I had to change the camera; that's why I was asking and am now wondering if it can be added to the documentation.
Once I changed the camera to "PowerToys VideoConference" it did turn on and off, as expected, when I used the keyboard shortcuts.

@Checkmate363
we are tracking in https://github.com/microsoft/PowerToys/issues/6444 the documentation issue.
Closing this since seems resolved.
Thanks.


Re-consider recommendation of rdkafka (prefer kafkajs)

My IBM Garage team prefer kafkajs (https://kafka.js.org) to rdkafka. The developer user experience is better with kafkajs, because of its pedigree, and it seems to have more maintenance activity. It also is more portable. kafkajs looks to have surpassed node-rdkafka in terms of npm downloads (although that metric is an imperfect metric of project value!).
Counter-arguments:

When we discussed it,  @jgorzins pointed out that kafkajs is not yet listed on https://cwiki.apache.org/confluence/display/KAFKA/Clients#Clients-Node.js
Incumbency: rdkafka is still widely and strongly recommended on IBM resources. It's clearly still widely used, even if momentum is in the process of shifting.

Backing up this suggestion. We also use Kafka.js

We should loop back with the messaging teams within Red Hat and IBM to see if their opinions have changed.  I'll have to dig out the contacts to that we can do that.
@cescoffier as the RH reactive lead I think you have some good insight as to what we should be considering as well. Can you add your comments ?

There are a few features that should be supported:

Auto and Manual offset commit (with a clear definition of the auto-commit as it may not work with async processing - see https://quarkus.io/blog/kafka-commit-strategies/)
Java-compliant partitioning
Avro support
Compression support (GZIP but also Snappy)
JSON object support
tombstone support (null value)
Rebalance hooks (and how can we commit eagerly during a rebalance)
Shutdown hook
Possibility to introduce a data store on reception to implement idempotence and exactly-once delivery
Kafka transaction support

KafkaJS developer here. Glad to hear that you're having positive experiences with KafkaJS, @holly-cummins!
@cescoffier: In regards to your list of features that you'd need in order to feel comfortable recommending KafkaJS, here are my notes. Most of these are supported, some with caveats, and a few I don't really understand and would like some clarification on.

Auto and Manual offset commit

Both are supported in KafkaJS.

Java-compliant partitioning

The default partitioner that we ship with is not Java compatible, but we do ship a JavaCompatiblePartitioner that can be used: https://kafka.js.org/docs/producing#default-partitioners
In some future major version, we'll probably change the default to be the JavaCompatible one.

Avro support (with both the Confluent and Apicurio registry)

We consider this to be outside of the scope of the client. We do provide a library for integrating with the Confluent schema registry, with support for not just Avro, but also Protobuf and JSON Schema: https://github.com/kafkajs/confluent-schema-registry/

Compression support (GZIP but also Snappy)

We support gzip, Snappy, lz4 and zstandard. https://kafka.js.org/docs/producing#a-name-compression-a-compression

JSON object support

This one I don't really understand what it means. Maybe you can expand on it?
If you pass in an object into producer.send, it will be serialized using JSON.stringify(), which will call the objects toJSON method. When you consume the message, you can toss that into JSON.parse to get back the deserialized object.

tombstone support (null value)

Kind of the same thing here. We do support tombstones in the sense that you can send a null value, and when we consume a null value, that is not passed to the userland code. Is that what you mean by support, or is there something else?

Rebalance hooks (and how can we commit eagerly during a rebalance)

This one we don't really support today.

Shutdown hook

Can you re-phrase this one in terms of what you want to achieve? We don't base our API around hooks in general, in contrast to how librdkafka does it.

Possibility to introduce a data store on reception to implement idempotence and exactly-once delivery

The interceptor pattern that's used in the Java client, which I guess is how you'd think of implementing this, is not how we design KafkaJS. In my mind, this is a higher-level concern that's easily implemented on top of the client. Conceptually it's as simple as:
const createPersistingMessageHandler = (eachMessageFn) => async ({ message, topic, partition, offset, ...rest }) => {
  // check persistence to see if message has already been processed or whatever other logic you want
  // then delegate back to user handler if the message should be processed
  return eachMessageFn({ message, topic, partition, offset, ...rest })
}

const eachMessage = createPersistingMessageHandler(async ({ message }) => {
  await processMessage(message)
})

await consumer.run({ eachMessage })

Maybe there are some specific requirements here that make it difficult to implement this with KafkaJS, and if so, I'd love to hear what those are, but conceptually this isn't something that we think belongs inside the client itself, and at least as of our current thinking, it doesn't require any special APIs that aren't available.

Kafka transaction support

This is supported, but it needs some love. There are some open bugs here, but since none of us core maintainers have had a need for EoS, we haven't had a chance to really devote time to investigate and sort those issues out. I would love it if some community member with a vested interest in this would take it upon themselves to make this 100% solid.

Thanks @Nevon for this very detailed reply. First, I'm not a Node developer, so when I listed the feature, I didn't check which ones were and were not implemented in the various libraries.
It looks to me that kafka.js checks all the boxes (more on the rebalance later)

JSON object support

It's exactly what you mentioned. It should encode the object into JSON and allows reading the data as JSON. It's natural in the node world, let's say it's less natural in other languages.

 Basically, the ability to implement a graceful shutdown and avoid record loss and reduce the likeliness of duplicates.

Rebalance listeners

About the rebalance listeners, which is more or less the only missing feature. When a rebalance happens (new consumer, or departure), Kafka will rebalance. Involved consumers will be notified that some of the partitions they are assigned to may not be theirs anymore and some new partitions would need to be handled. Hooks allow, typically in the first case, to commit pending records. You can't commit the record just after processing, as you may send too many commits which would be slow. So, you need to batches. Without that ability, we can see duplicates (it's all good, as Kafka apps generally support that), as the already processed records (uncommitted) may be handled by another consumer. Also, if you are not notified, you may end up committing offset on a partition not assigned to you anymore. I don't know how the client would react to this (just a failure maybe?).

 Basically, the ability to implement a graceful shutdown and avoid record loss and reduce the likeliness of duplicates.

Ah, I see. This is supported. consumer.disconnect will wait for ongoing work to finish before shutting down. Same for producer.disconnect, which will wait for any in-flight requests before disconnecting.

About the rebalance listeners

Right. I'd have to look into exactly what our semantics are on this, but in general the way the client becomes aware of this is that it gets an error response to the heartbeat request. In the client, we then skip any remaining messages and rejoin the group (which gives us new assignments). KafkaJS has two different interfaces towards the user, one where the user passes in a function that is applied to each message (named eachMessage) - in this interface we essentially just stop calling the user-provided function with the remainder of the messages. In the eachBatch interface we hand the user a batch of messages from a partition. This allows for more complex use-cases, but also delegates more responsibility to the user. In this case the user has the ability to heartbeat themselves, which allows them to become aware of rebalances, and it's also up to them to decide when they want to commit offsets.

@Nevon hi,
About SASL Support

OAUTH Bearer
SASL_PLAIN
SASL_SCRAM-SHA512
SASL_SCRAM-SHA256

I saw the code here https://github.com/tulios/kafkajs/tree/master/src/broker/saslAuthenticator
Question: all those SASL approaches are production-ready?

Yes, they are all tested and are used in production.

Closed by https://github.com/nodeshift/nodejs-reference-architecture/pull/72

For anyone stumbling here.
Not sure this changes anything, but worth knowing about: https://github.com/tulios/kafkajs/issues/1303


Remove covid 19 tags

Most businesses are no longer affected by Covid-19 any more than they are by the flu or any other seasonal diseases. As a result Covid-19 related  tags are considered deprecated by the larger OSM community. This PR removes all related content  and the supporting translation entries, in English, connected to the tag.

Thanks, this makes sense.
It would be nice to also remove the localizations for other languages too. Would you be up for that? Or I can do it later too.


Client error message

It currently always says X is not installed:
check-npm-versions.js:28 Uncaught Error<EMAIL_ADDRESS>not installed.
This may be misleading, in the case that you have installed with npm i, but the client doesn't see it. Consider:

meteor add apollo
npm i --save apollo-client: error on client
add import { meteorClientConfig } from 'meteor/apollo'; to client file: error on client (is this a bug? the file that defines meteorClientConfig imports from apollo-client)
add import { ApolloClient } from 'apollo-client'; to client file: error goes away

Perhaps could say X is either not installed or has not been imported on the client

is this still an issue?

This seems to be like this package should only run on the server to report the issue.

Yes, for future reference, checking npm versions should be done on the server even if the npm module code is needed on the server.


Lowercase the all caps “green”

What type of PR is this? (check all applicable)

[x] ♻ Refactor
[ ] ✨ Feature
[ ] 🐛 Bug Fix
[ ] 👷 Optimization
[ ] 📝 Documentation Update
[ ] 🔖 Release
[ ] 🚩 Other

Description

Switch from “GREEN” to “green”.
Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Remarks, notes, or any future suggestions?
Testing if this GitHub workflow is doing well and switching from “GREEN” to “green”.
Added to documentation?

[ ] 📜 readme
[ ] 📜 contributing.md
[ ] 📓 docs
[ ] 📕 storybook
[x] 🙅 no documentation needed

This thing worked.


Makefile: Add a pattern rule for oci-* commands

Make it easy to (re)build a single command without building all of them.  Using main.go as the only prerequisite cuts some corners, but prerequisites for this are hard ;).  With this commit, you can touch main.go to force a rebuild.  If that ends up being too awkward, we can make these .PHONY targets.
This is the current first commit in #5, to see if nibbling away at that PR one commit at a time makes review any easier.

If that ends up being too awkward, we can make these .PHONY targets.

yes please, split them into individual targes and then have "tools" to build them all

On Thu, Sep 22, 2016 at 09:40:40AM -0700, Antonio Murdaca wrote:

If that ends up being too awkward, we can make these .PHONY targets.

yes please, split them into individual targes and then have "tools"
to build them all

As is stood in 0179710, this PR already split them into individual
(pattern) targets and had the ‘tools’ target build them all.  What it
did not do was complete dependency checking (which is tricky with Go)
to only rebuild when necessary.  I've pushed 0179710 → 689ee3e with a
new commit that adds .PHONY to always rebuild.  That rebuilds too
often, but it errs on the side of rebuilding while 0179710 errs on the
side of not-rebuilding.

On Thu, Sep 22, 2016 at 10:50:54AM -0700, Vincent Batts wrote:

.PHONY:
tools \

$(TOOLS) \

that is somewhat redundant

We need $(TOOLS) so we rebuild them every time.  You could remove
‘tools’ if you wanted, but there is no ‘tools’ file on the disk, so I
think keeping it in .PHONY is appropriate.

On Thu, Sep 22, 2016 at 10:56:01AM -0700, Vincent Batts wrote:

+$(TOOLS): oci-%:
Here the oci-% is looking for dependencies of the target that have
the oci-% pattern. Is that intended?

This is a static pattern rule (linked from the the 689ee3e92 commit
message).  It is saying “for all the targets in $(TOOLS) use the
‘oci-%: ’ pattern rule”.  It has no dependencies (entries after the
second colon).

would almost seem like to get the Makefile dependency usefulness, we could have something like
GO_DEPS = $(shell go list -f '{{range .Deps}}{{printf "%s" .}}{{end}}' $(1))
GO_SOURCE_FILES = $(shell go list -f '{{range .GoFiles}}{{printf "%s" .}}{{end}}' $(1))

oci-%: $(call GO_SOURCE_FILES,$(call GO_DEPS,./cmd/oci-%))
        go build ./cmd/$@

or similar

On Thu, Sep 22, 2016 at 11:27:41AM -0700, Vincent Batts wrote:

would almost seem like to get the Makefile dependency usefulness, we could have something like
GO_DEPS = $(shell go list -f '{{range .Deps}}{{printf "%s" .}}{{end}}' $(1))
GO_SOURCE_FILES = $(shell go list -f '{{range .GoFiles}}{{printf "%s" .}}{{end}}' $(1))

oci-%: $(call GO_SOURCE_FILES,$(call GO_DEPS,./cmd/oci-%))

Having an accurate list of dependencies would be awesome, but the
.GoFiles line seems to print the filename and not the full path to the
file.  I'm happy to add this sort of checking if you know the proper
incantation to get the full path.
On the other hand, ‘go build’ (as we call it without -a) only rebuilds
packages that are out of date, so I'm fine leaving this PR at
689ee3e924, calling ‘go build’ every time, and having it bail out
if/when dependent packages are up to date.

yes. go build is nicer.

On Thu, Sep 22, 2016 at 11:48:06AM -0700, Vincent Batts wrote:

yes. go build is nicer.

So we're both happy with this PR as it stands with 689ee3e9?  Or is
there anything else I can do to help move this along?

please rebase

Rebased around #9 with 689ee3e → 2d06368.

LGTM

welp https://travis-ci.org/opencontainers/image-tools/builds/165582442

On Thu, Oct 06, 2016 at 09:35:21AM -0700, Vincent Batts wrote:

welp https://travis-ci.org/opencontainers/image-tools/builds/165582442

Is that lint timeout reproducible?  I'd just kick it again.

funky. that did the trick.


BOM clarification

C6 and C7 are actually on top of the PCB.

For the Rev.4 I moved these capacitors to the other side.  I forgot to update the BOM as well. Is now fixed.

Excellent, thanks.


Pod to pod connectivity in between nodes (microk8s)

Hello,
I am trying to build a k8s cluster of two nodes using microk8s where a MQTT broker is located on one node (exposing a service for a TCP connection on port 1883) and another pod on another node that is supposed to connect to this broker. Everything is working fine when the 2 pods are on the same node but I cannot manage to make the TCP connection when the 2 pods are on 2 different nodes (see screenshots below).
After a few back and forth I realized that the issue was the pod connectivity in between nodes. For example if I shell exec inside pod-74b4db7697-4znf5 (on node reamtlrnd03 - <IP_ADDRESS>)  I can:

PING the host (<IP_ADDRESS>)
PING the other node (<IP_ADDRESS>)
PING another pod on the same node

container-registry             registry-5f697bb7df-s76r4                                ●             1/1                                  1 Running              <IP_ADDRESS>                 reamtlrnd04              37m
kube-system                    calico-kube-controllers-7959b65c6-4c8jc                  ●             1/1                                  1 Running              <IP_ADDRESS>                 reamtlrnd04              18m
kube-system                    calico-node-qnlcg                                        ●             1/1                                  1 Running              <IP_ADDRESS>              reamtlrnd03              18m
kube-system                    calico-node-x2kwn                                        ●             1/1                                  1 Running              <IP_ADDRESS>              reamtlrnd04              18m
kube-system                    coredns-64c6478b6c-swqmx                                 ●             1/1                                  0 Running              <IP_ADDRESS>                 reamtlrnd04              6m36s
kube-system                    hostpath-provisioner-7764447d7c-p6tn4                    ●             1/1                                  2 Running              <IP_ADDRESS>                 reamtlrnd04              37m
production                     pod-controller-68fcbbfff-qxsdc                           ●             1/1                                  1 Running              <IP_ADDRESS>                 reamtlrnd04              26m
production                     pod-74b4db7697-4znf5                                     ●             1/1                                  1 Running              <IP_ADDRESS>                reamtlrnd03              26m

So the issue is that one pod on one node cannot connect to a pod on another node.
I started fiving in Calico's documentation and I tried to run calicoctl node status, which gives me:
Calico process is running.

The BGP backend process (BIRD) is not running.

So there is indeed an issue. According to the doc I checked that I could make TCP connection on port 179 using iperf and configured NetworkManager but the BGP backend process is still not running.
I also tried to specify the network interface using IP_AUTODETECTION_METHOD=eno1. But still no luck.
I also disabled the firewall but something is still wrong. Would you mind checking up the logs of calicoctl node diags for my two nodes?
Thanks.
diag-03.tar.gz
diag-04.tar.gz

The issue was actually coming from some microk8s misconfiguration on my side. Closing.

The issue was actually coming from some microk8s misconfiguration on my side. Closing.

@maximehyh I seem to have the exact same problem. What was your solution?

@nc-kab some things that were unrelated to Calico, see https://github.com/canonical/microk8s/issues/3043
I basically had to purge my installation and rename my hosts to some proper Linux hostnames .

That's interesting.
What is a "proper" linux hostname?
I think my hostnames complies with this https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-subdomain-names
My nodes are called k8s-master-1, k8s-node-1, k8s-node-2 etc.


First

Related Issue or bug

Info about Issue or bug

Fixes:
#[11]
#[31]
Describe the changes you've made
UI of the webpage where quizes are viewed have been changed to make it look cleaner. Image on the left side disappears on mobile devices and table has been made responsive.
UI of create quiz has been enhanced similarly.
HomePage has been changed slightly to enable smooth scrolling on clicking on "read more"

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
A clear and concise description of it.
Checklist:

[ ] Have you checked there aren't other open Pull Requests for the same update/change?
[ ] My submission doesn't break any existing feature.
[ ] My code follows the style guidelines of this project.
[ ] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] New and existing unit tests pass locally with my changes.
[ ] Any dependent changes have been merged and published in downstream modules.

Screenshots

Original
Updated

original screenshot
updated screenshot

@Kritinp Good work! UI looks great can you make it responsive too

@Kritinp Good work! UI looks great can you make it responsive too

Thanks!
Do you mean responsive with respect to the size of the window or something else?

@Kritinp Good work! UI looks great can you make it responsive too

Thanks! Do you mean responsive with respect to the size of the window or something else?

You can see that main content is overlapping with navbar right.. that one

@Kritinp any updates??

@Kritinp When will you complete this? it's more than 5 days

@Kritinp When will you complete this? it's more than 5 days

Will finish it tonight

@Kritinp When will you complete this? it's more than 5 days

I have updated the pull request. Please let me know if any changes are to be made.


refactor(ffe-account-selector-react): New dependencies

BREAKING CHANGE:
This package relied on ffe-checkbox-react which has been merged into ffe-form-react.
As a result, you need to update your dependencies to use this version. Replace the dependency on ffe-checkbox-react with ffe-form-react.
Make sure you're at least on version 4.3.0 of ffe-form-react.
No further action should be required to update this version.

This is going to fail untill #530 is merget and published

Coverage remained the same at 81.179% when pulling 24367a6bfd2e1ff8c2f3a3493229aaf551d6760e on ivarni:492-update-account-selector-deps into<PHONE_NUMBER>bde6d0787253f9c65ee3052cdbc4c2 on SpareBank1:develop.


Remove unused assets & partials

Deleting the following

patch: Remove redudant search partials
Remove old search template
Remove sticky header handling logic
Remove unused partials for resinSSH/resinSync commands

Please make sure to read the CONTRIBUTING document before opening the PR for relevant information on contributing to the documentation. Thanks!

@balena-ci rebase

@balena-ci I self-certify!


Rename "Market" to "Vendor"

Intel Quartus and Xilinx Vivado both use the namespace as "vendor" when a legoHDL "market" is synonymous. However, markets can be a special repository that hold the metadata for available blocks to install or download for integration or development.
Changing the name to "Vendor" will keep consistency with these terms and help users stick to already established conventions.

Solution merged from 'market-to-vendor' branch.


Possible to fix missing textures on Steam Deck/AMD with this tool?

Hello, thank you for this wonderful tool. It works quite well, though I did notice a few cases where characters talk on top of each other with high frame rate enabled, and a bit of UI issues playing in 1280x800 with the aspect ratio and UI fix.
Please close this issue if it isn’t within scope but I wondered, since you seem to be the only person capable of patching this game, is it possible to add a fix for missing textures (like part of Shiva’s forehead that is completely missing) on Steam Deck and AMD cards? As far as I’m aware this is an engine-level issue that affects anyone besides Nvidia users.
I uploaded a save file that showcases the issue here. https://github.com/ValveSoftware/Proton/issues/306#issuecomment-2134361277

I'm not sure I'd be able to address a vendor-specific issue like that. Also save data for this game is tied to your account and not transferrable, so I can't even boot up your save to have a look.
I definitely do want to try and further address some of the issues with the UI and the dynamic framerate but it'll take time.


Turn ShortcutListing and MarkdownIntroduction of text editor into ove…

…rridable components by retrieving them from component registry.
Fix #4812!

Closing because MarkdownIntroduction.jsx indeed can be shadowed, even it is not in src/.
<EMAIL_ADDRESS>


Fix TaskRunning: Handle Running state specifically and set startedAt.

 /|_||_\`.__
(   _    _ _\
=`-(_)--(_)-'  Awesome!


Execution failed for task ':baronha_react-native-multiple-image-picker:compileDebugKotlin'

I also got the same error like issue 44 .I downgraded the version to ver11 but still no success

"@baronha/react-native-multiple-image-picker": "^0.4.8",
"react-native": "0.66.0",

Please check the new version ( The current version is ver.1.0.0 )!

I have this exact same issue with react-native: 0.73.2 and @baronha/react-native-multiple-image-picker": "^1.1.6"

I this issue too
"@baronha/react-native-multiple-image-picker": "^1.1.6",
"react-native": "0.73.2",


Feature/performance

This PR continues on the work of PR #11 (fixes #7), and adds a significant performance increase, whereby it mostly fixes #9. I say mostly, because I think there might still be room for improvement, if we manage to utilize precompiled javascript, instead of having to create a number of ScriptEngines. However, I think this provides for a good start, and a flexible base to build upon if we feel the need to add different transpiling strategies.
Seeing as this builds on #11, it would suffice to merge only this PR, but for the time being, I'll leave both open, so as not to loose any comments.

@milpol, these last commits address all the remaining issues from #11.


When text scaling is applied, text is not getting resized in Length Converter pane

When text scaling is applied, text is not getting resized in Length Converter pane
Repro steps:
1.Launch the calculator application from start menu.
2.Navigate to  menu navigation button present in left corner if the app and invoke it.
3.Now select the length option under Converter pane and invoke it.
4.Length Converter page, select “kilometers” as the unit type in the input field and input “5”  and navigate to the Output values now observe the "about equals to values" text size in Textscaling 200%. mode.
Actual Results
In Length converter pane "About equals text" and "Displayed value" text is not enlarged after applying 200 % textscaling.
Expected Results
Text size should be increased when Text scaling is applied
User Impact
Users with low vision will face difficulty if the text is not getting increased.

This is your friendly Microsoft Issue Bot. I created this issue automatically as requested by a team member.

I think that is because BodyTextBlockStyle has a fixed font size.

Hmm, even when specifying a font style like this, the font should scale with the system. I suspect that IsTextScaleFactorEnabled might be set to false somewhere inappropriately (it is intended to be used for non-text, like icons).

Many of the TextBlocks in question are located in this xaml file.
https://github.com/gsfreema/calculator/blob/master/src/Calculator/Views/SupplementaryResults.xaml
They currently have IsTextScaleFactorEnabled set to false, but the history for that goes back before the initial transition to GitHub.  It does appear that setting them to true causes the text to scale, but it is unclear as to why they were set to false to begin with.

Sometimes, you want to set IsTextScaleFactorEnabled to false (e.g., when text is sufficiently large already, having it scale can cause severe layout issues). I am not sure why it is set on so many TextBlocks, but we should selectively remove that property from TextBlocks that we want to scale.


feat: Add German Nvidia store

Description
Fixes #84
Add the Nvidia.de store, using the in-and-ru-store API to check stock.

If i try this version I always get a success, cause of the following errors: 504 gateway time-out, 503 service temporarily unavailable and another error which i cant reproduce at the moment

Interesting. This API is what Nvidia's de-de site actually uses for its own stock check, so it's as reliable as the site itself.
(Notably, the calls from the Nvidia store page are also timing out, so it's currently unable to check its own stock on any items.)
Either way, I'll add failure states for 500 status codes when I get home.

I just got another error instead of an API result, but the API seems way more stable now. 5 minutes ago I had only failures:
Exception(s) were found for route(s):
0: Response code 429 mapped as failure.

Seems like its not working right, I've modified the .ts with your latest .ts

Have you pulled from main? The file it's complaining about was just added a couple of hours ago.

For me this new version is working 100%, zero false positives since running it

While this is (finally) working, a better implementation is happening in #162, so I'll close this PR.


Unit Test code needs updated

Hi there,
I'm working through creating ADO tasks and this guide has been a great resource; however, it appears there were some recent updates to the azure-pipelines-task-lib/mock-test package that should be reflected in this article to allow a smooth creation and testing of the task.
I started running into issues in the Unit test your task scripts. It looks like the run() function was deprecated and replaced with runAsync() inside the azure-pipelines-task-lib/mock-test package. A link below to the commit in the package from September 19th, 2023 to back this up (hope links are okay to send).
If you want to review the commit manually it's found at microsoft/azure-pipelines-task-lib/node/mock-test.ts, commit: cea7412512a6980646350854731833f289553b5b.
https://github.com/microsoft/azure-pipelines-task-lib/commit/cea7412512a6980646350854731833f289553b5b
I don't like to bring up issues without attempting a solution. It's easy enough to call the runAsync() function, but then the success tests were failing since the logging of the stdout happened before the runAsync() finished. So my (jr. dev) suggestion is to attach a callback to the runAsync() function:
    it('should succeed with simple inputs', function(done: Mocha.Done) {
        this.timeout(1000);

        let tp: string = path.join(__dirname, 'success.js');
        let tr: ttm.MockTestRunner = new ttm.MockTestRunner(tp);

        // tr.run(); //current, old function.
        tr.runAsync().then(() => {
            console.log(tr.succeeded);
            assert.equal(tr.succeeded, true, 'should have succeeded');
            assert.equal(tr.warningIssues.length, 0, "should have no warnings");
            assert.equal(tr.errorIssues.length, 0, "should have no errors");
            console.log(tr.stdout);
            assert.equal(tr.stdout.indexOf('Hello human') >= 0, true, "should display Hello human");
            done();
        }).catch((error) => {
            done(error); // Ensure the test case fails if there's an error
        });
    });

That small change got it working locally for me. I know this isn't a huge issue for experienced javascript developers, but it stumped me for a bit and I'm sure it could be of help to someone else.
Thanks!

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

ID: 44581f4a-93df-7507-3844-eadedf9a6cc4
Version Independent ID: 33c7bcf0-1512-975f-5ef8-9f2a192a84ad
Content: Add a build or release task in an extension - Azure DevOps
Content Source: docs/extend/develop/add-build-task.md
Service: azure-devops
Sub-service: azure-devops-ecosystem
GitHub Login: @chcomley
Microsoft Alias: chcomley

@benjamin-morris-91, thanks so much for this detailed issue. I've added your workaround to the article, which will be published in the next day or so. Thanks for helping others be successful!


Update installed JDKs to match current boot JDK requirements

Checklist

[x] commit message has one of the standard prefixes
[x] playbook changes run through VPC or QPC (if you have access): https://ci.adoptium.net/view/Tooling/job/VagrantPlaybookCheck/1666/

Draft pending VPC checks and verification that the build uses the installed JDK20 but approvals welcome in the meantime.

This is going to require a bit more work because it's trying to pull JDK20 from api.adoptopenjdk.net which does redirect to adoptium, so I'm going to stick this in draft for now until it can be progressed.

On hold until we come up with something sane to do for Linux on s390x and arm32

@sxa Needs a rebase

VPC: https://ci.adoptium.net/view/Tooling/job/VagrantPlaybookCheck/1845/

GPG signature verification is failing with this change so some extra remediation will be required for that.

AIX and Linux (including riscv64 tested separately as it has different paths through the playbooks) are working properly now. Windows still undergoing testing...

Windows now looking good: https://ci.adoptium.net/job/VagrantPlaybookCheck/1855/

CentOS6 and Solaris also now clean (Both have special paths in this particular role at present.

And thanks for handling all those linter changes. :)

Merging so that it's ready for the JDK22 dry run pipelines later this week.

Rebuild of linux images happening under https://ci.adoptium.net/job/centos7_docker_image_updater/471


First time running

Anyone knows what could be the reason for the following when i start the bot:
arbitrader_1  | 2019-03-30 12:02:06.009  WARN 1 --- [           main] s.c.a.AnnotationConfigApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'tradingService': Invocation of init method failed; nested exception is org.knowm.xchange.exceptions.ExchangeException: java.net.UnknownHostException: api.kraken.com
arbitrader_1  | 2019-03-30 12:02:06.032 ERROR 1 --- [           main] o.s.boot.SpringApplication               : Application run failed

arbitrader_1

I filled correct my kraken keys.

That means your computer can’t look up api.kraken.com due to a DNS error. That is the same address I am using for Kraken so I think your configuration is probably correct.
Try going to https://api.kraken.com in your browser or with something like curl and see if that works.

Thank you ! This fixed my problem.

Hello,
There are new kraken fees.
I think you should update the project.
Thanks for your efforts !
Regards,
Todor

On 31 Mar 2019, at 1:20, Peter Keeler<EMAIL_ADDRESS>wrote:
That means your computer can’t look up api.kraken.com due to a DNS error. That is the same address I am using for Kraken so I think your configuration is probably correct.
Try going to https://api.kraken.com https://api.kraken.com/ in your browser or with something like curl and see if that works.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/scionaltera/arbitrader/issues/54#issuecomment-478297856, or mute the thread https://github.com/notifications/unsubscribe-auth/AKoOdNVVlIzboCOeG6qwO2Gqp5ckBfmAks5vb_E0gaJpZM4cTtDJ.

Hello,
I meant liquid/quone not kraken sorry.
Regards,
Todor

On 31 Mar 2019, at 1:20, Peter Keeler<EMAIL_ADDRESS>wrote:
That means your computer can’t look up api.kraken.com due to a DNS error. That is the same address I am using for Kraken so I think your configuration is probably correct.
Try going to https://api.kraken.com https://api.kraken.com/ in your browser or with something like curl and see if that works.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/scionaltera/arbitrader/issues/54#issuecomment-478297856, or mute the thread https://github.com/notifications/unsubscribe-auth/AKoOdNVVlIzboCOeG6qwO2Gqp5ckBfmAks5vb_E0gaJpZM4cTtDJ.

XChange does not yet support querying Liquid/Quoine for trading fees dynamically so it will fall back to what you have configured in your application.yaml. It looks like the correct setting would be 0.001 now instead of 0.002.

Updated application.example.yaml with the new fee in #55 .

Hello,
Thank you.
Now i see other crash:
arbitrader_1  | 2019-04-02 07:54:43.826  INFO 1 --- [   scheduling-1] c.r.arbitrader.service.TradingService    : ***** ENTRY *****
arbitrader_1  | 2019-04-02 07:54:45.797  INFO 1 --- [   scheduling-1] c.r.arbitrader.service.TradingService    : Updated account balances: Quoine $66.56 + Kraken $46.16 = $112.72
arbitrader_1  | 2019-04-02 07:54:45.947  INFO 1 --- [   scheduling-1] c.r.arbitrader.service.TradingService    : Entry spread: 0.01119732
arbitrader_1  | 2019-04-02 07:54:46.097  INFO 1 --- [   scheduling-1] c.r.arbitrader.service.TradingService    : Exit spread target: -0.00100268
arbitrader_1  | 2019-04-02 07:54:46.244  INFO 1 --- [   scheduling-1] c.r.arbitrader.service.TradingService    : Long entry: Quoine XRP/USD 30.42750647 @ 0.32865 (0.00000 slip) = $10.0000000013655
arbitrader_1  | 2019-04-02 07:54:46.395  INFO 1 --- [   scheduling-1] c.r.arbitrader.service.TradingService    : Short entry: Kraken XRP/USD 30.09057262 @ 0.33234000 (-0.00001000 slip) = $10.0003009045308000
arbitrader_1  | 2019-04-02 07:54:46.912 ERROR 1 --- [   scheduling-1] o.s.s.s.TaskUtils$LoggingErrorHandler    : Unexpected error occurred in scheduled task.
arbitrader_1  |
arbitrader_1  | org.knowm.xchange.exceptions.ExchangeException: {"message":"Please go to our Trading site (dashboard_url) to review Terms, Conditions and Trading Rules before continuing."}
arbitrader_1  |  at org.knowm.xchange.quoine.service.QuoineBaseService.handleHttpError(QuoineBaseService.java:51)
Seems like i must confirm something but i can not find anything to confirm.
Also i think that bot is placing long order at liquid.
Do you have more information about this bug ?
If you prefer i can create an issue at your webpage ?
Regards,
Todor

On 2 Apr 2019, at 7:55, Peter Keeler<EMAIL_ADDRESS>wrote:
Updated application.example.yaml with the new fee in #55 https://github.com/scionaltera/arbitrader/pull/55 .
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/scionaltera/arbitrader/issues/54#issuecomment-478844197, or mute the thread https://github.com/notifications/unsubscribe-auth/AKoOdFOv-h1hGgmY4nA7YcyZJHuZ2iZwks5vcuK_gaJpZM4cTtDJ.

https://app.liquid.com/update-terms https://app.liquid.com/update-terms
This fixed the problem i think.
Sorry for the spam…..
Regards,
Todor

On 2 Apr 2019, at 11:04, Todor Neshev<EMAIL_ADDRESS>wrote:
Hello,
Thank you.
Now i see other crash:
arbitrader_1  | 2019-04-02 07:54:43.826  INFO 1 --- [   scheduling-1] c.r.arbitrader.service.TradingService    : ***** ENTRY *****
arbitrader_1  | 2019-04-02 07:54:45.797  INFO 1 --- [   scheduling-1] c.r.arbitrader.service.TradingService    : Updated account balances: Quoine $66.56 + Kraken $46.16 = $112.72
arbitrader_1  | 2019-04-02 07:54:45.947  INFO 1 --- [   scheduling-1] c.r.arbitrader.service.TradingService    : Entry spread: 0.01119732
arbitrader_1  | 2019-04-02 07:54:46.097  INFO 1 --- [   scheduling-1] c.r.arbitrader.service.TradingService    : Exit spread target: -0.00100268
arbitrader_1  | 2019-04-02 07:54:46.244  INFO 1 --- [   scheduling-1] c.r.arbitrader.service.TradingService    : Long entry: Quoine XRP/USD 30.42750647 @ 0.32865 (0.00000 slip) = $10.0000000013655
arbitrader_1  | 2019-04-02 07:54:46.395  INFO 1 --- [   scheduling-1] c.r.arbitrader.service.TradingService    : Short entry: Kraken XRP/USD 30.09057262 @ 0.33234000 (-0.00001000 slip) = $10.0003009045308000
arbitrader_1  | 2019-04-02 07:54:46.912 ERROR 1 --- [   scheduling-1] o.s.s.s.TaskUtils$LoggingErrorHandler    : Unexpected error occurred in scheduled task.
arbitrader_1  |
arbitrader_1  | org.knowm.xchange.exceptions.ExchangeException: {"message":"Please go to our Trading site (dashboard_url) to review Terms, Conditions and Trading Rules before continuing."}
arbitrader_1  |  at org.knowm.xchange.quoine.service.QuoineBaseService.handleHttpError(QuoineBaseService.java:51)
Seems like i must confirm something but i can not find anything to confirm.
Also i think that bot is placing long order at liquid.
Do you have more information about this bug ?
If you prefer i can create an issue at your webpage ?
Regards,
Todor

On 2 Apr 2019, at 7:55, Peter Keeler<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
Updated application.example.yaml with the new fee in #55 https://github.com/scionaltera/arbitrader/pull/55 .
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/scionaltera/arbitrader/issues/54#issuecomment-478844197, or mute the thread https://github.com/notifications/unsubscribe-auth/AKoOdFOv-h1hGgmY4nA7YcyZJHuZ2iZwks5vcuK_gaJpZM4cTtDJ.

Hello,
I’ve updated to latest git version.
I had crash.
Attaching screen.log file.
Regards,
Todor Neshev

Attaching screen.log file.

I don't see the attachment anywhere?

screen.log
Here is the log file. Sorry

Sorry sending again….

On 8 Apr 2019, at 17:18, Peter Keeler<EMAIL_ADDRESS>wrote:
Attaching screen.log file.
I don't see the attachment anywhere?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/scionaltera/arbitrader/issues/54#issuecomment-480850864, or mute the thread https://github.com/notifications/unsubscribe-auth/AKoOdMyfUHfIseM-V9rng_tZxYC7QRf6ks5ve0-kgaJpZM4cTtDJ.

That is a bug that I'm working on in my current pull request #59 . I am hoping to be able to merge it tonight.


Auto-Shutdown Doesn't Detect Connections

Even though the auto-shutdown works on the original Satisfactory server stack that it was built for, it seems there are some changes needed to properly detect connections going into the Docker server. There was an initial attempt at this but that doesn't seem to be working and needs to be addressed.

This may have been fixed in 0d24b62. It turned out there were seemingly two issues:

The ec2-user did not have permission to run netstat against the container. I think I could have joined up some permissions to address this but in this case there's no harm in running the auto-shutdown script as root, so that's how this problem was fixed.
The command itself that was being run wouldn't return just a count of connections. This was updated with some better grep filtering and then using wc -l to count the number of lines returned.

The auto-shutdown now seems to be maintaining the server while players are active, but when players aren't active it seems that there are sometimes still connections reported briefly. I'm leaving this issue open as I continue to investigate, this might be pings from clients that are open but not actively in-game.


Change to more aesthetic math rendering 💅🏼

Feature details
FlamingPy uses this Xanadu Sphinx theme on our readthedocs pages, but the math rendering is not pleasant to read since it results in pixelated equations, see this QEC explainer for example. This happens because the equations are rendered as a png. I would propose to change this to the way StrawberryFields and PennyLane do it, see this paragraph on tensor observables.
Implementation
PennyLane and StrawberryFields already use the proposed method. I guess it's relatively easy to change the general Xanadu theme accordingly.
How important would you say this feature is?
2: Somewhat important. Needed this quarter.
Additional information
No response

Hey @soosub! This is a bit confusing, since PL and SF both use this general theme as well. Maybe they do something different in their conf.py configuration files?

Alright, I'll have a look and keep you posted @josh146

Found it! Apparently we had both sphinx.ext.imgmath and sphinx.ext.mathjax in the extensions of the  conf.py file. Removing sphinx.ext.imgmath did the trick 👌🏼
Thanks @josh146!


Automatic calculation of layer sizes

🚀 Feature
Calculate number of layer inputs (especially linear layers) automatically, without having to resort to manual calculation or print
Motivation
I have a model that receives multiple images as inputs. Each input goes through some number of convolution/pool layers, each with potentially different kernel sizes/stride/etc. All of these are hyperparameters that are being tuned
The output from those layers gets flattened, merged, and passed into a linear layer
The problem here is that during init, the linear layer needs to know how many input connections it needs. I cant hard code this value because hyperparameter tuning means I wont know ahead of time what the size of each image will be post-convolution/pool. I cant resort to using print to check the size, because the size will change between each tuning run. print is fine if you're dealing with a fixed architecture, but doesnt cut it when tuning parameters that end up changing the architecture
I was working on a personal project recently where I had to calculate and combine all the output sizes and it ended up being about 100 lines in total: https://github.com/sho-87/webcam-eye-tracker/blob/master/Models.py#L299-L397
Am I just doing this slowly/inefficiently? Is there a saner way to do this without all the hand calculation? This is a relatively simple case without tuning things like stride. I expect it to get more complicated in those situations.
If this is the best we have currently, then consider this a feature request for automatic calculation of those sizes, because this feels quite excessive in terms of boilerplate. I would essentially like to just replace line 391 in my code with something like self.fc1 = nn.Linear(None, config["dense_nodes"]), and have the None replaced for me
As a side note, we can set self.example_input_array to log the graph to tensorboard, so arent these layer sizes already stored somewhere in a lightning module? Maybe we can use that, or a similar idea, to avoid hand calculating everything?

It seems to me that you are asking for automatic shape inference. If so, maybe torchlayers is exactly what you are looking for as they seem to be doing auto shape inference.

It seems to me that you are asking for automatic shape inference. If so, maybe torchlayers is exactly what you are looking for as they seem to be doing auto shape inference.


RenderToString does not support ref type teleport

Version
3.0.4
Reproduction link
https://codesandbox.io/s/naughty-wind-fufkn
Steps to reproduce
ref type tereport
https://github.com/vuejs/vue-next/blob/master/packages/runtime-core/__tests__/components/Teleport.spec.ts#L38-L54
teleport SSR test
https://github.com/vuejs/vue-next/blob/master/packages/server-renderer/__tests__/ssrTeleport.spec.ts#L59-L73
When ref type report is used, it is not reflected in ctx
const ctx: SSRContext = {}
const html = await renderToString(
  createApp({
    setup() {
      const svg = ref()
      const circle = ref()

      return {
        svg,
        circle
      }
    },
    template: `
      <svg ref="svg"></svg>
      <teleport :to="svg" v-if="svg">
        <circle ref="circle"></circle>
      </teleport>
    `
  }),
  ctx
)
console.log(html) // <!--[--><svg></svg><!----><!--]-->
console.log(ctx) // return {}

What is expected?
The same result as with id
What is actually happening?
No teleport object in context

IMO:

With ref target, teleports can find the target in current component scope, so it's rendered to string directly.

With id target, teleports cannot determine where the target is during SSR, so it's extracted to the context.

With ref target, teleports can find the target in current component scope, so it's rendered to string directly.

@meteorlxy
If so, I would like to get results that include circle in the renderToString.

My previous comment was wrong.
If we remove the v-if="svg", the bug might be more clear.

I understand your kind answer, but I still have some questions.

Based on the result code of renderToString using id or ref, Does not the server-side rendering code expose the teleport template?
If made source using ref and v-if (Like an example link), where would the reference be kept and processed after mounted?

The to has to be present at the moment the component renders, so as explained, using an unitialized ref won't work. In general, it's better to have the teleport target outside of the component where teleport is used: https://v3.vuejs.org/api/built-in-components.html#teleport. Because of this you cannot use the ref="svgRef" attribute for teleports. You can still use a dynamic selector


Configuration for DynamoDB Hadoop in 0.5.4

Is there a dynamo equivalent for the hadoop format files for the HadoopFactory configurations in 0.5.4?
http://s3.thinkaurelius.com/docs/titan/0.5.4/hadoop-config-ref.html
We're trying to export a list of specific edges from a production Titan 0.5.4 environment and migrate them to a 1.0.0 env

I suggest you use the procedure listed in @dkuppitz openflights project to migrate 0.5.4 data to 1.0.0;.


Run action on error

It would be useful if shire could run an action when an error occurs. This could simply run a shell script or could post to a Discord webhook.

Not sure whether it should be a discord webhook, a regular one, or something that supports either

or yea could be a shell script, not sure what the permission implications of that would be

Thats what I was just thinking about- I presume the best way to get error details into a shell script would be arguments?


VM extension TeamServicesAgentLinux fails with "Incorrect VSTS account credentials"

Agent Version and Platform
Version of your agent?
2.165.0 (Hosted V2017)
OS of the machine running the agent?
CIS Red Hat Enterprise Linux 7 Benchmark L1
Publisher: center-for-internet-security-inc
SKU: cis-rhel7-l1
Offer: cis-rhel-7-v2-2-0-l1
Azure DevOps Type and Version
dev.azure.com (formerly visualstudio.com) or on-premises TFS/Azure DevOps Server?
dev.azure.com
If dev.azure.com, what is your organization name?
https://dev.azure.com/cbsp-selfservice-arie
What's not working?
I'm installing the "TeamServicesAgentLinux" extension using an ARM template on a Linux VM which sits behind a proxy server.
I have modified the ARM template for Linux ("TeamServicesAgentLinux") and changed it to only target one VM. The template is valid. I'm using cbsp-selfservice-arie (the organization name) for "vstsAccountName". The team project specified exists and contains the deployment group to which I try to add the Linux VM. The PAT is valid and has the correct permissions (Deployment Groups - Read & manage).
The provisioning fails with the following error:
2020-02-26T08:01:03.1975291Z ##[debug]Exception:
2020-02-26T08:01:03.2000176Z ##[debug]Microsoft.PowerShell.Commands.WriteErrorException: DevOps agent extension installation failed. Template deployment returned the following errors: '8:01:01 AM - Resource Microsoft.Compute/virtualMachines/extensions 'arie01evm01/TeamServicesAgentLinux' failed with message '{
2020-02-26T08:01:03.2013639Z ##[debug]  "status": "Failed",
2020-02-26T08:01:03.2023748Z ##[debug]  "error": {
2020-02-26T08:01:03.2033381Z ##[debug]    "code": "ResourceDeploymentFailure",
2020-02-26T08:01:03.2043024Z ##[debug]    "message": "The resource operation completed with terminal provisioning state 'Failed'.",
2020-02-26T08:01:03.2052842Z ##[debug]    "details": [
2020-02-26T08:01:03.2056638Z ##[debug]      {
2020-02-26T08:01:03.2067335Z ##[debug]        "code": "VMExtensionProvisioningError",
2020-02-26T08:01:03.2079078Z ##[debug]        "message": "VM has reported a failure when processing extension 'TeamServicesAgentLinux'. Error message: \"Incorrect VSTS account credentials\"\r\n\r\nMore information on troubleshooting is available at https://aka.ms/vmextensionlinuxtroubleshoot "
2020-02-26T08:01:03.2088746Z ##[debug]      }
2020-02-26T08:01:03.2099550Z ##[debug]    ]
2020-02-26T08:01:03.2109735Z ##[debug]  }
2020-02-26T08:01:03.2121397Z ##[debug]}' 8:01:01 AM - VM has reported a failure when processing extension 'TeamServicesAgentLinux'. Error message: "Incorrect VSTS account credentials"

When viewing the detailed status (0.status file on the Linux VM itself), I see the following error:
[
    {
        "code": "ComponentStatus/Pre-Validation Checks/succeeded",
        "level": "Info",
        "displayStatus": "Provisioning succeeded",
        "message": "Successfully validated dependecies"
    },
    {
        "code": "ComponentStatus/Read config settings/failed/53",
        "level": "Error",
        "displayStatus": "Provisioning failed",
        "message": "AzureDevOpsOrganizationUrl should be specified"
    }
]

The extension.log file on the Linux VM itself reads the following:
2020/02/26 08:00:46 [Microsoft.VisualStudio.Services.TeamServicesAgentLinux-<IP_ADDRESS>] sequence number is 0
2020/02/26 08:00:46 [Microsoft.VisualStudio.Services.TeamServicesAgentLinux-<IP_ADDRESS>] setting file path is/var/lib/waagent/Microsoft.VisualStudio.Services.TeamServicesAgentLinux-<IP_ADDRESS>/config/0.settings
2020/02/26 08:00:46 [Microsoft.VisualStudio.Services.TeamServicesAgentLinux-<IP_ADDRESS>] Config decoded correctly.
2020/02/26 08:00:46 [Microsoft.VisualStudio.Services.TeamServicesAgentLinux-<IP_ADDRESS>] JSON config read successfully
2020/02/26 08:00:46 [Microsoft.VisualStudio.Services.TeamServicesAgentLinux-<IP_ADDRESS>] Check systemd process exit code : 0
2020/02/26 08:00:46 [Microsoft.VisualStudio.Services.TeamServicesAgentLinux-<IP_ADDRESS>] stdout : /usr/bin/systemctl
2020/02/26 08:00:46
2020/02/26 08:00:46 [Microsoft.VisualStudio.Services.TeamServicesAgentLinux-<IP_ADDRESS>] srderr :
2020/02/26 08:00:46 [Microsoft.VisualStudio.Services.TeamServicesAgentLinux-<IP_ADDRESS>] systemd is installed on the machine.
2020/02/26 08:00:46 ERROR:[Microsoft.VisualStudio.Services.TeamServicesAgentLinux-<IP_ADDRESS>] AzureDevOpsOrganizationUrl should be specified
2020/02/26 08:00:46 [Microsoft.VisualStudio.Services.TeamServicesAgentLinux-<IP_ADDRESS>] Setting handler status, code and message as 'error', '53' and 'Incorrect VSTS account credentials' respectively
2020/02/26 08:00:46 [Microsoft.VisualStudio.Services.TeamServicesAgentLinux-<IP_ADDRESS>] Change log file to /var/log/azure/Microsoft.VisualStudio.Services.TeamServicesAgentLinux/CommandExecution.log

The 0.settings file on the Linux VM itself reads the following:
{
    "runtimeSettings": [
        {
            "handlerSettings": {
                "protectedSettings": "",
                "publicSettings": {
                    "DeploymentGroup": "arie01",
                    "AgentName": "arie01evm01",
                    "TeamProject": "SelfService",
                    "VstsAccountName": "https://dev.azure.com/cbsp-selfservice-arie",
                    "Tags": [
                        "arie01"
                    ]
                },
                "protectedSettingsCertThumbprint": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
            }
        }
    ]
}

The HandlerStatus file on the Linux VM itself reads the following:
{
    "status": "NotReady",
    "code": 1009,
    "name": "Microsoft.VisualStudio.Services.TeamServicesAgentLinux",
    "version": "<IP_ADDRESS>",
    "extensions": [],
    "message": "[ExtensionOperationError] Non-zero exit code: 53, /var/lib/waagent/Microsoft.VisualStudio.Services.TeamServicesAgentLinux-<IP_ADDRESS>/AzureRM.py -enable\n[stdout]\n2020/02/26 08:00:46 ERROR:[Microsoft.VisualStudio.Services.TeamServicesAgentLinux-<IP_ADDRESS>] Error occured during Read config settings. AzureDevOpsOrganizationUrl should be specified\n\n\n[stderr]\n"
}

When adding the deployment agent via unattended config directly on the Linux VM itself, the deployment succeeds when I make use of the proxy server with cURL (to download the agent) and config.sh (for installing and configuring the deployment agent). I have to use the full organization name (https://dev.azure.com/cbsp-selfservice-arie) for this method, just like what is shown in the 0.settings file.
This leads me to believe that the error message itself is wrong and that the real error is caused by the proxy server not being used, as it's the only difference which I see? Is my deduction correct and if so, how can we solve this issue?

@bishal-pdmsft @pulkitaggarwl - Is this some thing that either of your teams handles?

Yes @jtpetty our team owns this vm extension. We will look into this.

Hi @atyourservers, it looks like the is an issue in the VstsAccountName you are passing in the ARMtemplate. It should be VSTSAccountName.
The error log AzureDevOpsOrganizationUrl should be specified is correct. The other log Setting handler status, code and message as 'error', '53' and 'Incorrect VSTS account credentials' respectively you are seeing in extension.log is the extension status returned back to VM because of which the below log is added to 0.status file.
{         "code": "ComponentStatus/Read config settings/failed/53",         "level": "Error",         "displayStatus": "Provisioning failed",         "message": "AzureDevOpsOrganizationUrl should be specified"     }

Hi @atyourservers, it looks like the is an issue in the VstsAccountName you are passing in the ARMtemplate. It should be VSTSAccountName.
The error log AzureDevOpsOrganizationUrl should be specified is correct. The other log Setting handler status, code and message as 'error', '53' and 'Incorrect VSTS account credentials' respectively you are seeing in extension.log is the extension status returned back to VM because of which the below log is added to 0.status file.
{ "code": "ComponentStatus/Read config settings/failed/53", "level": "Error", "displayStatus": "Provisioning failed", "message": "AzureDevOpsOrganizationUrl should be specified" }

Are you talking about the field VSTSAccountName in the ARM template? That's already written that specific way; see line 66 of my full ARM template, which I quoted below:
{
    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
    "contentVersion": "<IP_ADDRESS>",
    "parameters": {
        "vmName": {
            "type": "string",
            "metadata": {
                "description": "The name of the VM on which the deployment agent will be installed."
            }
        },
        "location": {
            "type": "string",
            "metadata": {
                "description": "The location of the VM."
            }
        },
        "vstsAccountName": {
            "type": "string",
            "metadata": {
                "description": "The name of the Azure DevOps organization."
            }
        },
        "teamProject": {
            "type": "string",
            "metadata": {
                "description": "The name of the project that has the deployment group defined within it."
            }
        },
        "deploymentGroup": {
            "type": "string",
            "metadata": {
                "description": "The name of the deployment group for the agent to join."
            }
        },
        "agentName": {
            "type": "string",
            "metadata": {
                "description": "The agent name for the VM."
            }
        },
        "tags": {
            "type": "array",
            "metadata": {
                "description": "A comma-separated list of tags that will be set on the agent. Tags are not case sensitive and each must be no more than 256 characters."
            }
        },
        "patToken": {
            "type": "securestring",
            "metadata": {
                "description": "The Personal Access Token that will be used to authenticate against Azure Pipelines to download and configure the agent."
            }
        }
    },
    "resources": [
        {
            "type": "Microsoft.Compute/virtualMachines/extensions",
            "name": "[concat(parameters('vmName'), '/TeamServicesAgentLinux')]",
            "apiVersion": "2019-07-01",
            "location": "[parameters('location')]",
            "properties": {
                "publisher": "Microsoft.VisualStudio.Services",
                "type": "TeamServicesAgentLinux",
                "typeHandlerVersion": "1.0",
                "autoUpgradeMinorVersion": true,
                "settings": {
                    "VSTSAccountName": "[parameters('vstsAccountName')]",
                    "TeamProject": "[parameters('teamProject')]",
                    "DeploymentGroup": "[parameters('deploymentGroup')]",
                    "AgentName": "[parameters('agentName')]",
                    "Tags": "[parameters('tags')]"
                },
                "protectedSettings": {
                    "PATToken": "[parameters('patToken')]"
                }
            }
        }
    ]
}

Do you have an update on this please @bishal-pdMSFT?

@atyourservers Anurag's observation was based on the 0.settings file content you pasted earlier
{
    "runtimeSettings": [
        {
            "handlerSettings": {
                "protectedSettings": "",
                "publicSettings": {
                    "DeploymentGroup": "arie01",
                    "AgentName": "arie01evm01",
                    "TeamProject": "SelfService",
                    "VstsAccountName": "https://dev.azure.com/cbsp-selfservice-arie",
                    "Tags": [
                        "arie01"
                    ]
                },
                "protectedSettingsCertThumbprint": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
            }
        }
    ]
}

Notice the setting named VstsAccountName. This can cause problem as extension reads this file to get all settings. Though it is really interesting that somehow settings specified in ARM templates are getting altered.
Is this a VM on which this extension was never installed? If no, can you try this template on VM where this template was not installed previously.
cc @tejasd1990

@atyourservers Anurag's observation was based on the 0.settings file content you pasted earlier
{
    "runtimeSettings": [
        {
            "handlerSettings": {
                "protectedSettings": "",
                "publicSettings": {
                    "DeploymentGroup": "arie01",
                    "AgentName": "arie01evm01",
                    "TeamProject": "SelfService",
                    "VstsAccountName": "https://dev.azure.com/cbsp-selfservice-arie",
                    "Tags": [
                        "arie01"
                    ]
                },
                "protectedSettingsCertThumbprint": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
            }
        }
    ]
}

Notice the setting named VstsAccountName. This can cause problem as extension reads this file to get all settings. Though it is really interesting that somehow settings specified in ARM templates are getting altered.
Is this a VM on which this extension was never installed? If no, can you try this template on VM where this template was not installed previously.
cc @tejasd1990

This was on a new Linux VM.

@bishal-pdMSFT @tejasd1990 any update on this issue?

Hi @atyourservers , apologies for the response delay. You should use AzureDevOpsOrganizationUrl instead of VSTSAccountName. We will update the documentation for this.


Linking Text Doesn't Work..

Linking text won't work for the newer version of Ren'Py ( Ren'Py 8.1.0)!
Any help would really be appreciated! :)

Had to do some modifications to my script to get it to work in Ren'Py 8.1.0 and also to keep support for lower versions of Ren'Py 8.0.3 and below I have made the following changes to my script
Hope this might help you
            # Add in the focus areas.

            try:
                for hyperlink, hx, hy, hw, hh in layout.hyperlinks:

                    h_x, h_y = layout.unscale_pair(hx + layout.xoffset, hy + layout.yoffset)
                    h_w, h_h = layout.unscale_pair(hw, hh)

                    rv.add_focus(self, hyperlink, h_x, h_y, h_w, h_h)

            except:
                for hyperlink, hx, hy, hw, hh, valid_st in layout.hyperlinks:

                    if st >= valid_st or not self.slow:

                        h_x, h_y = layout.unscale_pair(hx + layout.xoffset, hy + layout.yoffset)
                        h_w, h_h = layout.unscale_pair(hw, hh)

                        rv.add_focus(self, hyperlink, h_x, h_y, h_w, h_h)

Also trying to fix the click twice to proceed after a line ends and what I have come up with so far seems to solve the issue for me.
self.call_slow_done has changed to self.slow_done in Ren'Py 8.1.0
            # Figure out if we need to redraw or call slow_done.
            if self.slow and not self.always_effect and not redraw is None:
                renpy.display.render.redraw(self, max(redraw, 0))

            elif self.always_effect:
                renpy.display.render.redraw(self, 0)

            if self.slow and redraw is None:
                try:
                    self.slow = False
                    self.call_slow_done(st)
                    renpy.game.interface.timeout(0)
                except:
                    self.slow = False
                    self.slow_done()
                    renpy.game.interface.timeout(0)

It works! Thank you so much! :D