Camera and Microphone Redirection?

I didn't see anything on this page about whether or not Mic and Camera redirection is supported, or how to configure it.
We have a user connecting from Mac OS who is using the latest release (10.3.8) of the MRD app. They are connecting from Mac OS Sierra (10.12).
They are trying to use Microsoft Teams inside WVD, which I am able to do when connecting from Windows, but they don't have any option to use the camera or microphone inside the WVD environment. It seems as though microphone and camera redirection is not working.
Is Mic and Camera redirection supported in MRD for WVD? If so, does it require a newer version of Mac OS? Please add a note about this.
(As an aside: the link provided in the text about "please do NOT post a request for troubleshooting help by using the comment feature at the end of this article" points to forums that no longer accept posts).

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

ID: 0517ea6a-9417-31a8-39a5-f6128387fee5
Version Independent ID: 7636ec70-e1dd-8c6b-516c-8af324d9f645
Content: Get started with the macOS client
Content Source: WindowsServerDocs/remote/remote-desktop-services/clients/remote-desktop-mac.md
Product: windows-server
Technology: remote-desktop-services
GitHub Login: @lizap
Microsoft Alias: elizapo

Hello @GuyPaddock.  Thank you for your feedback about the forum. For your question, please open a support ticket or post your question on Microsoft Q&A.


add support for aws insight rules resource and disable and delete actions

Codecov Report

Merging #24 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #24   +/-   ##
=======================================
  Coverage   90.80%   90.80%
=======================================
  Files         298      298
  Lines       34168    34193   +25
=======================================
+ Hits        31025    31048   +23
- Misses       3143     3145    +2

Impacted Files
Coverage Δ

c7n/resources/resource_map.py
100.00% <ø> (ø)

c7n/resources/cw.py
94.78% <100.00%> (+0.63%)
:arrow_up:

c7n/resources/s3.py
84.77% <0.00%> (-0.14%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6256ac5...939ca40. Read the comment docs.


admit seems to affect code before it

This snippet works, even if it seems to be introducing an exists* (x:unit). Pure False.
```pulse
fn
test_intro (_:unit)
  requires emp
  ensures emp
{
  intro_exists (fun () -> pure False) ();
  admit()
}
```

Removing the admit makes it fail as it should.
```pulse
fn
test_intro (_:unit)
  requires emp
  ensures emp
{
  intro_exists (fun () -> pure False) ()
}
```

Puzzlingly, if I try to print the state before the admit, it seems as if intro_exists was not applied since it is bound at type stt_ghost.
```pulse
fn
test_intro (_:unit)
  requires emp
  ensures emp
{
  intro_exists (fun () -> pure False) ();
  show_proof_state;
  admit()
}
```

  - Tactic logged issue:
  - Current context:
      emp **
      emp
  - In typing environment:
      [_#2 : stt_ghost unit emp_inames (pure l_False) (fun _ -> exists* (_: unit). pure l_False),
      uu___85#1 : unit]

I think the problem is because the type of intro_exists is not interpreted properly in Pulse, since it uses a kind of points-free style of specification, which Pulse doesn't expect.


HTTP/JSON API

An easy-to-use HTTP/JSON API could make applications like #4 very easy, and open the door for a simple CLI utility.

Add websocket support, usable only with an auth token. Auth token can be generated using the HTTP API.


🐛(backend) Fixing docker-compose.yml to make nginx depend on app-dev

Purpose
This will fix issue #339, ensuring that nginx starts only after app-dev is up and running, preventing startup failures.
Proposal
To address this, the following steps will be taken:

Update docker-compose.yml to include a dependency on nginx for app-dev.
Verify that the dependency order resolves the issue with nginx startup.

Description...

[x] Modify docker-compose.yml to add depends_on: app-dev for the nginx service.
[x] Test the configuration to ensure nginx waits for app-dev to start.

Thank you for your contribution.
If your pull request is ready, don't forget to switch to the status Ready for review, we usually don't review before the pull request is in this state.

You should add a line in the changelog as well: https://github.com/numerique-gouv/impress/blob/main/CHANGELOG.md
About the commit we follow the Angular convention: https://github.com/angular/angular/blob/main/CONTRIBUTING.md#commit
You can refer to others commits of this repository.

When your pull request passed all the required tests feel free to ask us for a review.

@AntoLC I just added the necessary changes to the Commit message and CHANGELOG.md

The commit message does not pass the linter, yuo should remove the colon after (docker).
🐛(docker): update docker-compose.yml to make nginx depend on app-dev
🐛(docker) update docker-compose.yml to make nginx depend on app-dev

The commit message does not pass the linter, you should remove the colon after (docker).
🐛(docker): update docker-compose.yml to make nginx depend on app-dev
🐛(docker) update docker-compose.yml to make nginx depend on app-dev

Is now corrected


Update http4s-blaze-client, http4s-circe to 0.21.24

Updates

org.http4s:http4s-blaze-client
org.http4s:http4s-circe

from 0.21.23 to 0.21.24.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (0.21.23).
You might want to review and update them manually.
jetty-server/src/main/scala/org/http4s/jetty/server/JettyBuilder.scala
jetty-server/src/main/scala/org/http4s/jetty/server/UndestroyableThreadPool.scala
server/src/main/scala/org/http4s/server/package.scala
website/src/hugo/content/changelog.md

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s" } ]

labels: library-update, semver-patch, old-version-remains

Included in #4895


chore(scripts): Rebuild instead of removing node_modules

As removing the node_modules completely and then re-installing is quite time consuming and SSD-thrashing, resort to pruning and rebuilding native add-ons when switching targets.
Change-Type: patch

A question about this, if you don't mind...
When I run make electron-develop twice in a row, at the start of the second run it prints:
unbuild<EMAIL_ADDRESS>unbuild<EMAIL_ADDRESS>unbuild<EMAIL_ADDRESS>unbuild<EMAIL_ADDRESS>unbuild<EMAIL_ADDRESS>unbuild<EMAIL_ADDRESS>unbuild<EMAIL_ADDRESS>unbuild<EMAIL_ADDRESS>unbuild<EMAIL_ADDRESS>unbuild<EMAIL_ADDRESS>unbuild<EMAIL_ADDRESS>unbuild<EMAIL_ADDRESS>unbuild<EMAIL_ADDRESS>unbuild<EMAIL_ADDRESS>
I'm guessing this is coming from npm prune? However these modules are listed in npm-shrinkwrap.json, and do then get re-installed.
I noticed that they're "optional" dependencies, however it seems that there's also other optional dependencies in npm-shrinkwrap.json (below list created with grep -B5 optional npm-shrinkwrap.json | grep '": {'|cut -d'"' -f2|sort|uniq )
array-buffer-from-string
base32-encode
bcrypt-pbkdf
bplist-creator
camelcase
cliui
cp-file
ecc-jsbn
fmix
fs-temp
image-size
jodid25519
jsbn
murmur-32
nested-error-stacks
random-path
source-map
stream-buffers
tn1150
tweetnacl
uglify-js
uglify-to-browserify
unorm
window-size
wordwrap
yargs

and some of them aren't 'unbuilt' by npm prune? Hmmm, and imul gets pruned, which isn't an optional dependency?
I also ran npm run clean-shrinkwrap as a test, but that didn't result in any changes to npm-shrinkwrap.json
I'm not complaining, as running make electron-develop a second time now seems much faster than before, I'm just trying to understand what's going on ;-)

This isn't coming from npm prune – that's npm rebuild. And those unbuild ... messages are coming from packages that have build scripts.

Ahhh, thanks Jonas.
Just out of curiosity, I also ran:
git clone --depth=1 https://github.com/resin-io/etcher etcher-fresh
cd etcher-fresh
rm npm-shrinkwrap.json
make electron-develop
npm --dev shrinkwrap
npm run clean-shrinkwrap
git diff

and ignoring the version-change differences (and using grep to double-check), it seems like these packages are in the repo-version of npm-shrinkwrap.json but not in my freshly-generated version of npm-shrinkwrap.json :
array-buffer-from-string
base32-encode
bplist-creator
cp-file
fmix
fs-temp
image-size
imul
lodash.rest
murmur-32
nested-error-stacks
node-cmd
pkg-conf
random-path
spdx-exceptions
stream-buffers
symbol
tn1150
unorm

Obviously some of those will be due to the newer non-shrinkwrapped packages having different dependencies, but I wonder if maybe some of the packages in the list above aren't actually needed anyway, and are merely being installed because they're still listed in npm-shrinkwrap.json when they should actually have been removed?
Again, I'm still an NPM newbie, so please feel free to point out where I'm going wrong :-)


Revert " Shifting the theme button #87"

Reverts SurajSanap/College.ai-main#88
there is an issue now: "theme.button_face" is not a valid config option. If you previously had this config option set, it may have been removed.
@lassmara

hi, is this issue still showing?
On Tue, 11 Jun 2024 at 20:30, Srs_vesta @.***> wrote:

Merged #93 https://github.com/SurajSanap/College.ai-main/pull/93 into
main.
—
Reply to this email directly, view it on GitHub
https://github.com/SurajSanap/College.ai-main/pull/93#event-13118703399,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAPDTX7DRMVQLNTP6Z5MO6LZG4GI3AVCNFSM6AAAAABJEQ3ZV6VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTGEYTQNZQGMZTSOI
.
You are receiving this because you were mentioned.Message ID:
@.***>


[unittest] Add unittest for backwarding of loss layers

This patch adds unittest for backwarding of loss layers with fc and activation layers
Major bug fixes for backwarding of all the loss layers to match with tensorflow
Major hot fix for softmax derivative - need to update activation layers semantics to
properly fix softmax layer derivative
Signed-off-by: Parichay Kapoor<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #335. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

:octocat: cibot: @kparichay, One of the module of prebuild group is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnstreamer/nntrainer/wiki/.


accept lower case log levels for the QUIC_GO_LOG_LEVEL flag

There's no actual need for this PR, other than that I keep mixing up how to properly set the log level.

Codecov Report

Merging #851 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #851   +/-   ##
=======================================
  Coverage   90.92%   90.92%
=======================================
  Files          87       87
  Lines        6060     6060
=======================================
  Hits         5510     5510
  Misses        351      351
  Partials      199      199

Impacted Files
Coverage Δ

internal/utils/log.go
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 79c1766...9633ffa. Read the comment docs.


⚠ Bofrost.fr has degraded performance

In ff5c500, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1167 ms

Resolved: Bofrost.fr performance has improved in 3d29435.


fix: call args.callback() in exec.inspect() #717

Resolves #717

Good catch 👍
Will ping when merged.

Thank you!

Published in v3.3.5


Seeking a non-loaded animation throws a NullReferenceException

[runtime] 2020-08-26 11:05:26 [error]: System.NullReferenceException: Object reference not set to an instance of an object.
[runtime] 2020-08-26 11:05:26 [error]: at osu.Framework.Graphics.Transforms.Transformable.get_Time()
[runtime] 2020-08-26 11:05:26 [error]: at osu.Framework.Graphics.Animations.AnimationClockComposite.consumeClockTime()
[runtime] 2020-08-26 11:05:26 [error]: at osu.Framework.Graphics.Animations.AnimationClockComposite.set_PlaybackPosition(Double value)
[runtime] 2020-08-26 11:05:26 [error]: at osu.Framework.Graphics.Animations.AnimationClockComposite.Seek(Double time)
[runtime] 2020-08-26 11:05:26 [error]: at osu.Framework.Graphics.Animations.Animation`1.GotoFrame(Int32 frameIndex)

The code that throws this looks pretty inconspicuous:
if (lightContainer != null)
{
    if (isHitting.NewValue)
        Column.TopLevelContainer.Add(lightContainer);
    else
        Column.TopLevelContainer.Remove(lightContainer);

    if (light is TextureAnimation lightAnimation)
        lightAnimation.GotoFrame(0);
}

The issue is that GotoFrame() throws the nullref in the case that the animation is not loaded, which requires the above code to be transformed into:
if (lightContainer != null)
{
    if (isHitting.NewValue)
    {
        Column.TopLevelContainer.Add(lightContainer);

        if (light is TextureAnimation lightAnimation)
            lightAnimation.GotoFrame(0);
    }
    else
        Column.TopLevelContainer.Remove(lightContainer);
}

Sounds like we might just want to throw a guard in to not touch the clock if the drawable isn't loaded?
https://github.com/ppy/osu-framework/blob/598494e8e9f0a8bbd19dba8981d05eaa81851203/osu.Framework/Graphics/Animations/AnimationClockComposite.cs#L82-L98
Or even in consumeClockTime itself - does it make sense to consume time during load?

Would that work for GotoFrame with a non-zero frame? I think that's a thing that should be supported.

I think it should? As long as the manual clock receives the value it should be ok. The consume is just to avoid additional time leaps on top of the seek I'm pretty sure.
I'll go and actually have a look on my own.


Update README.md

@CodiumAI-Agent /review

PR Review 🔍

 ⏱ Estimated effort to review [1-5]
1, because the PR only involves a minor change to a README file, which is typically straightforward and quick to review.

 🧪 Relevant tests
No

 ⚡ Possible issues
No

 🔒 Security concerns
No

 Code feedback:

@CodiumAI-Agent /describe

@CodiumAI-Agent /improve

PR Code Suggestions ✨
No code suggestions found for PR.


[BUG] ecc Segmentation fault on compile

Describe the bug
On compiling the code from https://github.com/linuxkerneltravel/lmp/tree/develop/eBPF_Hub/opensnoop ecc Segmentation fault  and exits.

Expected behavior
Can be compile and run.

thanks!


WSL2 bridge network

I'm using WSL2 for developing a network app (client side on Windows and server side on Linux). It seems that by default WSL2 using NAT for networking, so it's not possible to connect both platforms correctly so them can be accessible for each other via various protocols such as TCP, UDP, ICMP, etc.
After quick search I've found a #4150 workaround but this is not valid in my situation because I need full availability (not only TCP). My question is there even a bridge mode in WSL2 (since its a wrapper around Hyper-V) and how to enable it? If not - is there any plans of adding this feature to WSL2? Like a easy to use setting for enabling different network modes without manual firewall forwarding, nesth, etc.?
I and many of my colleagues was expecting that with WSL2 introduction it will be possible to perform such tasks as mine "out of the box" without needing third-party software like Virtualbox but for now I'm stuck and unfortunately have to use VBox for that.

duplicate of what? why closed?

It is /dupe #4150 which you cited (and its friends #4825 #4928 with a side of #4210).


Missing upload still has its string ID in the JSON response

Link to reproduction
https://github.com/hdodov/payload/tree/bug-missing-media
To Reproduce

Create an upload-enabled collection
Open the admin
Create a new entry in that collection and associate an upload with it
Go to the uploads collection and delete the upload
The JSON response for the entry will have a string as a value for the upload

Describe the Bug
Services that consume the Payload API expect either an upload to exist or not. In other words, if you have a field associatedMedia, the value for it should either be null or an object — with url, width, etc. You don't really expect it to be a string, unless you specify depth and you set it to 0.
There is also another case where you haven't initially specified a value for the upload, in which case the associatedMedia value is simply not present in the JSON. This could also cause problems.
Basically there are four possibilities for the value of associatedMedia:

undefined (missing from the JSON) - initially, when the user hasn't specified any value for the field
object - when an upload is selected by the user and can be successfully populated when a request occurs
string - when the upload has been deleted from the collection and can no longer be populated
null - when the user has uploaded and selected a file, then removed it

It's useful to have this difference between undefined and null, and you can catch both of them with a truthy check, but the string situation is unexpected. If Payload attempts to populate a field from an external collection and fails to do so, it should return null as the value, since that resource no longer exists.
https://github.com/payloadcms/payload/assets/5570098/fe1b039d-9a15-4ba1-b66f-6f01613a5532
Payload Version
1.11.2

Hey @hdodov,
Thanks for reporting! I'll add that there is a 2nd situtation where a string is returned and that is if the access control on the related document prevents it from populating.
We have a roadmap item https://github.com/payloadcms/payload/discussions/2938 that will help the usability on the admin side for this situation. I'm going to convert this to a discussion since right now it is working as intended for now.


[Feature] [API] Add Endpoint for Branch creation

We want to automatically create Dev-Stacks in our Company (new Application, Package, ....)
To create a Repository we want to create the complete basic structure.
The Api of Gitea is already very powerfull, but we also need an Endpoint to create a new Branch.
proposal for: repository
add POST /repos/{owner}/{repo}/branches
Information to create a new branch should be

The Name of the new Branch
The Name of the Branch the new Branch is based on

I hope i didn't forgot something

closed by #11607


Updated GreeterCard Styles

Trello Cards

Tighten line-height on the headings
Tighten the typography of the body text
Line breaks are ignored in Embed
Greeter title text tooltip displayed on hover

Summary
This PR updates the styles of the GreeterCard component based on feedback from Buzz and Ryan. Updates include:

Updated line-height of title and subtitle components.
Updated line-height, font-size and letter-spacing of body text component.
Added white-space: pre-wrap; to body component to respect new line characters.
Removed title prop being passed to the main div to prevent the browser's tooltip from showing up.

Demo
Before:

After:

You can also check it out in the Storybook build for this branch.

Pull Request Test Coverage Report for Build 1973

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 1968:
0.0%

Covered Lines:
7432

Relevant Lines:
7432

💛  - Coveralls

Direct linky to preview:
https://deploy-preview-574--hsds-react.netlify.com/?selectedKind=GreeterCard&selectedStory=Default&full=0&addons=1&stories=1&panelRight=0&addonPanel=storybooks%2Fstorybook-addon-knobs


Jest compatibility

Jest is a great test runner and I'm trying to use it with request-promise in my current project. The problem is this module isn't working with jest.
Here is a minimal example:
reusable.js:
let id = Math.random();
module.exports = {id};

users.js:
let stealthyRequire = require('stealthy-require');
var reusableStealth = stealthyRequire(require.cache, function () {
    return require('./reusable');
},
function () {}, module);
var reusable = require("./reusable");
module.exports = {
  reusableStealth,
  reusable
}

__tests__/users.js:
let users = require("../users");
describe("", () => {
  it("", () => {
    expect(users.reusableStealth.id).not.toEqual(users.reusable.id);
  })
})

This actually works in node, when I require the users module I get two unique ids. Just not working with jest, so I can understand if you don't consider this a bug.
Side-note: I don't understand how I can be the only one using jest and request, each have over 10 000 stars on github.

Doesn't look like there is anything wrong with this module, it's more of a request-promise-core / jest issue.

Hey @t1bb4r , I am curious nonetheless. Since the code is working in node without Jest I am wondering what difference Jest makes. In your Jest version do you still execute it within node or somewhere else like in the browser? Do you use transpilers like babel? And packagers like webpack or browserify?

I'm using jest --env=node which should execute the tests in a node environment. They have their own module cache / registry management, which is the problem (I might be completely wrong). I've been investigating this file jest-runtime for a while to try and understand whats going on.
Jest has a mocking feature where you can mock any import, this feature is probably the reason they keep their own module registry.

Alright, I see. They are passing their own require function to the modules and that function uses a cache that is not exposed. So yes, stealthy-require and jest are incompatible and there is no solution unless jest would expose their moduleRegistry.
But thinking outside the box: You want to test your request-promise code, right? It uses stealthy-require internally to allow projects that use request and request-promise at the same time. If your project always uses request-promise and never request by itself then you can just ignore the fact that stealthy-require is falling back to a standard require.

Its tough to say exactly what all the libraries I'm including uses internally and when they will conflict, but you are right, if we can manage to only use the core module once everything is ok.
The first time I started to run into this issue was when I installed a module which depends on "request-promise", while I'm using "request-promise-native". These imports, no matter how deep in your dependency tree, will break jest.
Either way, thanks a lot for the help and feedback. I'll manage to workaround the issue.

You are welcome buddy. One last tip: You can check with npm ls request if different libraries depend on request.


Bump up the cardano-ledger-api version

Description

Checklist

[ ] Commit sequence broadly makes sense and commits have useful messages
[ ] New tests are added if needed and existing tests are updated
[x] When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
versioning process.
[ ] The version bounds in .cabal files for all affected packages are updated. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
[ ] All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages. New section is never added with the code changes. (See RELEASING.md)
[x] Code is formatted with fourmolu (use scripts/fourmolize.sh)
[x] Cabal files are formatted (use scripts/cabal-format.sh)
[x] hie.yaml has been updated (use scripts/gen-hie.sh)
[x] Self-reviewed the diff

This is for the Query, right?

This is for the Query, right?

No, it was my fault, I forgot to bump up the version (in the cabal file) due to some breaking changes I introduced in #3508

This is for the Query, right?

No, it was my fault, I forgot to bump up the version (in the cabal file) due to some breaking changes I introduced in #3508

Ah I see, thanks


Require govuk_editor to progress editions

This makes changes to the action processors to ensure that the user has the govuk_editor permission before performing the action. See individual commits for more details.
This is the precursor to adding a new welsh_editor permission which permits access to certain actions without the govuk_editor permission but only for Welsh language documents.
Trello Card

Looks good to me!


STF 1.5.4 release ops

Contents of the merge look fine to me. Still a bit confused on the commit history stuff, but I ran into similar problems in the last release, so maybe I've just broken the cleanliness somewhere along the line?

I think this happens due to the previous merge being a squash+merge. Look here: https://github.com/infrawatch/smart-gateway-operator/pull/149
The last commit in that PR is 0531e69, but then it says "leifmadsen merged commit 519e2eb". Because of that, this merge sees these as entirely new commits, but producing the same content.
Upshot is that while squash+merge is good for consolidating a PR that takes multiple revisions, I don't think it's good for preserving history when synchronizing branches.

Contents of the merge look fine to me. Still a bit confused on the commit history stuff, but I ran into similar problems in the last release, so maybe I've just broken the cleanliness somewhere along the line?

I think this happens due to the previous merge being a squash+merge. Look here: #149
The last commit in that PR is 0531e69, but then it says "leifmadsen merged commit 519e2eb". Because of that, this merge sees these as entirely new commits, but producing the same content.
Upshot is that while squash+merge is good for consolidating a PR that takes multiple revisions, I don't think it's good for preserving history when synchronizing branches.

Ah thanks for that. Makes sense now.
I guess in this case we want to use Merge and not the Squash and Merge option to avoid this in the future?


#![deny(warning)] considered harmful

See also https://github.com/rust-unofficial/patterns/blob/master/anti_patterns/deny-warnings.md.
Denying warning makes non-breaking changes breaking.
As the proof of it, current master doesn't compile with latest rustc because &Trait is warned.

I'm not sure I understand the argument for not denying warnings. That seems like desirable behavior to me. I'd be happy to take the patch to use the dyn syntax and keep warnings denied.

Rust put importance to backward compatibility. That means when you have a code that compiles now, you can compile it with future rust versions. Adding warnings is one way to request to use better code without breaking existing codes. However, denying warnings spoils it.
Of cause, it is a good habit to clean up warnings. To do so, you should setup CI to compile with RUSTFLAGS="-D warnings" cargo build or like so.
If you want this patch to split into the fix of dyn and the fix of deny(warning), I'll do it.

I think getting the error is more useful to me than this type of backwards compatibility. I'm happy to simply fix the warning and release a new crate! So yes, please don't change the #![deny(warning)] here.

Thank you!


access=designation description

Over recent days, there has been a discussion on the AU list regarding correct tagging of bicycle riding on footpaths (AKA UK pavements or US sidewalks), which is sometimes allowed & other times not:
https://lists.openstreetmap.org/pipermail/talk-au/2021-October/015062.html
I made the suggestion of using bicycle=designated, based on the definition that comes up in iD:
"Access allowed according to signs or specific local laws", under the idea that local laws say yes or no, so follow those laws.
In reply, it has been pointed out (https://lists.openstreetmap.org/pipermail/talk-au/2021-October/015083.html) that:
in practice the definition at https://wiki.openstreetmap.org/wiki/Tag:access%3Ddesignated is actually:
"indicates that a route has been specially designated (typically by a government) for use by a particular mode (or modes) of transport"
It's a way of saying "you might have a right to get from A to B via X, Y or Z, but the route via X has been specifically constructed for your mode of transport so you should go that way".
In this case, to prevent confusion, the wording of the "designated" definition should probably be amended to delete "or specific local laws".
Thanks
Graeme

@Fizzie41 can you share a screenshot of where you see any definition of the value in iD?
To me, this sounds like something that needs to be change in the OSM Wiki and OSM Wikidata. (And I am not sure what processes to follow to change those contents.)


Explcitly extens CLOG in acording to checkpoint nextXid LSN

refer #1159

Why is this needed?

Why is this needed?

IIRC PostgreSQL always creates a CLOG_ZEROPAGE record to extend the clog as needed. Replaying those records should be enough. Yeah, clearly something is wrong since your script reproduces errors, but I suspect this patch just hides the real problem, whatever that is.

It is needed because of the following code in xlog_utils:
    /// Update next XID based on provided new_xid and stored epoch.
    /// Next XID should be greater than new_xid. This handles 32-bit
    /// XID wraparound correctly.
    ///
    /// Returns 'true' if the XID was updated.
    pub fn update_next_xid(&mut self, xid: u32) -> bool {
        let xid = xid.wrapping_add(XID_CHECKPOINT_INTERVAL - 1) & !(XID_CHECKPOINT_INTERVAL - 1);
        let full_xid = self.nextXid.value;
        let new_xid = std::cmp::max(xid + 1, pg_constants::FIRST_NORMAL_TRANSACTION_ID);
        let old_xid = full_xid as u32;
        if new_xid.wrapping_sub(old_xid) as i32 > 0 {
            let mut epoch = full_xid >> 32;
            if new_xid < old_xid {
                // wrap-around
                epoch += 1;
            }
            let nextXid = (epoch << 32) | new_xid as u64;

            if nextXid != self.nextXid.value {
                self.nextXid = FullTransactionId { value: nextXid };
                return true;
            }
        }
        false
    }

It cause storing in checkpoint nextXid which is not yet generated by Postgres and so for which  CLOG_ZEROPAGE record is not yet generated.

It cause storing in checkpoint nextXid which is not yet generated by Postgres and so for which CLOG_ZEROPAGE record is not yet generated.

How does that happen? Why does our update_next_xid() see an XID that Postgres hasn't generated yet?

xid is transaction ID of current WAL record forward aligned on XID_CHECKPOINT_INTERVAL = 1024.
Then we increment it:
let new_xid = std::cmp::max(xid + 1, pg_constants::FIRST_NORMAL_TRANSACTION_ID);

xid is transaction ID of current WAL record forward aligned on XID_CHECKPOINT_INTERVAL = 1024. Then we increment it:
let new_xid = std::cmp::max(xid + 1, pg_constants::FIRST_NORMAL_TRANSACTION_ID);

I see. I think the logic here is wrong. We can advance nextXid in chunks like we do here, but we should never skip the first XID on each clog page. I think that's what this code was supposed to do, but it's off by one. For example, if you pass '100' as the argument to update_next_xid, it updates next_xid to 32769, skipping the first XID on the new CLOG page, 32768. Surely the intention was to advance it to 32768.
I think this same applies to pg_commit_ts, BTW. Looking at commit_ts.c, each page in pg_commit_ts can hold (8192 / 10 = 819). Annoyingly that's not a power of two, which makes the logic a bit more complicated as you have to check for crossing clog and commit_ts pages separately. We don't currently support track_commit_timestamp, though, do we?
Unit tests for update_next_xid would be very helpful.

I am not quite sure that this logic is right, but according to the code of varsup.c nextXid really points to the next xid, i.e. currently assigned xid + 1. And it is saved in checkpoint record. So as far as I understand, invariant is that checkpoint.nextXid is greater than any XID in WAL.
To enforce this invariant we actually do this increment.
If passed XID is 1024 than alignment it on XID_CHECKPOINT_INTERVAL does nothing. We still need increment to enforce this invariant.
May be we should first increment and then align. But in makes extra conditions on XID_CHECKPOINT_INTERVAL  which should not be large than BLCKSZ*4

We don't currently support track_commit_timestamp, though, do we?

Yes, and it was mentioned in your comment:
    // SLRUs include pg_clog, pg_multixact/members, and
    // pg_multixact/offsets. There are other SLRUs in PostgreSQL, but
    // they don't need to be stored permanently (e.g. pg_subtrans),
    // or we do not support them in zenith yet (pg_commit_ts).

I am not quite sure that this logic is right, but according to the code of varsup.c nextXid really points to the next xid, i.e. currently assigned xid + 1. And it is saved in checkpoint record. So as far as I understand, invariant is that checkpoint.nextXid is greater than any XID in WAL.
To enforce this invariant we actually do this increment.
If passed XID is 1024 than alignment it on XID_CHECKPOINT_INTERVAL does nothing. We still need increment to enforce this invariant.

Agreed.

May be we should first increment and then align.

+1

But in makes extra conditions on XID_CHECKPOINT_INTERVAL  which should not be large than BLCKSZ*4

Yeah, that deserves an assertion or at least a comment.

Replaced with #1166


[app] Fix 404 error for ACE worker files

When a user opens a page with an Editor component a 404 error was thrown
in the console, because the worker files for ACE (the underlying editor)
could not be found. This is fixed by disabling workers using the
"useWorker: false" in the "setOptions" property.
This also disables syntax checking in ACE. If we want to use syntax
checking in the future, we can set "useWorker: true" and import the
"ace-builds/webpack-resolver" file.

[x] I added a CHANGELOG entry for this change.
[ ] I adjusted the corresponding documentation for this change.
[ ] I adjusted the values.yaml file and the documentation for all values.

Codecov Report

Merging #410 (c372d32) into main (9eced52) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #410   +/-   ##
=======================================
  Coverage   47.29%   47.29%
=======================================
  Files         138      138
  Lines       11443    11443
=======================================
  Hits         5412     5412
  Misses       5892     5892
  Partials      139      139

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Recommendation, Text classification, Sentence similarity: The ignored column's name should be grey on the "Advanced data options" dialog.

System Information (please complete the following information):
Windows OS: Windows-11-Enterprise-22H2
ML.Net Model Builder 2022: <IP_ADDRESS>2801 (Main Build)
Microsoft Visual Studio Enterprise: 2022(17.7.7)
.Net: 6.0,7.0
Describe the bug

On which step of the process did you run into an issue:
The ignored column's name should be grey on the "Advanced data options" dialog.

TestMatrix
https://testpass.blob.core.windows.net/test-pass-data/recommendation-ratings.csv
To Reproduce
Steps to reproduce the behavior:

Select Create a new project from the Visual Studio start window.
Choose the C# Console App (.NET Core) project template.
Add model builder by right click on the project.
Select "Recommendation or Text classification or Sentence similarity" scenario.
On Data page, choose the data source and select the columns for all options.
Click "Advanced data options" link to open "Advanced data options" dialog.
Check the ignored column's name.

Expected behavior
The ignored column's name should be grey.
Screenshot

Additional context

The bug has been fixed on the latest main build <IP_ADDRESS>6202.


Add a Github page interface to make the content more accessible

Hi heejkoo
Thanks for the awesome collection. I just create a Github page to make the content more accessible and organized.
You could preview the website here.
https://zeqiang-lai.github.io/Awesome-Diffusion-Models/
It contains the python scripts to convert the readme into html.
To keep it updated. Every time the readme is update, run the following to update the website
cd website
sh build.sh

I really appreciate your awseom collaboration, but I have no idea how to work on it. I will add it asap.

Sure, that would be great.
BTW: It is actually very simple, just merge the pull request and then enable the Github page in the setting panel as

Then, you should be able to access the website via https://heejkoo.github.io/Awesome-Diffusion-Models/
The shell script sh build.sh could be replaced by the three python commands if you are working from Windows.
python convert.py
python convert_resource.py
python main.py

If there is any other problem, I can help if needed.

It works! I am really grateful for your work. Hope I can help you in the future !


Stack video additions

Description of the change
Testing embedding video into the documentation
Checklist
Please make sure that the proposed change checks all the boxes below before requesting a review:

[X] I have reviewed the guidelines for contributing to this repository.
[ ] The preview looks fine.
[ ] The tests pass.
[ ] The commit history is clean and meaningful.
[ ] The pull request is opened against the main branch.
[ ] The pull request is no longer marked as a draft.
[ ] You agree to license your contribution under the MIT license to Spacelift.

If the proposed change is ready to be merged, please request a review from @spacelift-io/solutions-engineering. Someone will review and merge the pull request.
Thank you for your contribution! 🙇

Deleting PR and will restart branch due to dirty commits for testing the embedded video and unverified commit.


⚠ Fortnite has degraded performance

In d38fb76, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1409 ms

Resolved: Fortnite performance has improved in 58c0060.


Asp.NET Core Facility and Filters

Filters were working when we were using the Castle.Windsor.MsDependencyInjection reference but since switching to Castle.Facilities.AspNetCore we are having a difficult time.  It seems like we should be using the CrossWired() extension method based on the documentation. But, due to our heavy use of Installers this is impractical.
Example
        public IServiceProvider ConfigureServices(IServiceCollection services)
        {
            Container = new WindsorContainer();
            Container.AddFacility<AspNetCoreFacility>(f => f.CrossWiresInto(services));

            services.AddMvc().SetCompatibilityVersion(CompatibilityVersion.Version_2_2);
            services.AddScoped<TrackingFilter>();

            Container.Install(new ConfigurationInstaller());
            return services.AddWindsor(Container);
        }

Results in a  Unable to resolve service for type 'blah.blah.IProvideConfiguration' while attempting to activate 'blah.blah.TrackingFilter'.
Am I missing something?  Is there an easier way to allow Asp.net filters to resolve Windsor injected dependencies?

You have to explicitly use CrossWired() for those components you want the framework to be able to resolve.

Closing as @dariuslf provided an answer. Castle.Windsor.Extensions.DependencyInjection is also the path forward for ASP.NET Core 3.x.


fix simplify conditional function generate wrong nullable

What problem does this PR solve?
Related PR: #37613
Problem Summary:
because adjust nullable do not run after simplify confitional function, we should not change any output's nullable in this rule
Check List (For Author)

Test

[x] Regression test
[ ] Unit Test
[ ] Manual test (add detailed scripts or steps below)
[ ] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[ ] Previous test can cover this change.
[ ] No code files have been changed.
[ ] Other reason

Behavior changed:

[x] No.
[ ] Yes.

Does this need documentation?

[x] No.
[ ] Yes.

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

run buildall

run feut


Make .info files on master.tus.io accessible too

https://tus.io/demo.html and https://master.tus.io/files are great resources for testing TUS.
It would be great, if the .info files corresponding to an upload would be accessible too.
Helps client devs to verify if they have done things right e.g.

Good idea! However, there is already a way to retrieve the information contained in .info files: The specification defines the HEAD request for this (https://tus.io/protocols/resumable-upload.html#head) which contains the Upload-Offset, Upload-Length, Upload-Metadata, etc headers for this. Of course, this is supported by the https://master.tus.io/files instance.

Hi Marius,
I understand. This is of course the standard procedure, when one needs to
retrieve this info.
However, having these files available on a demo platform still comes in
very handy. See, I had setup tusd with an s3store in my production system,
when I realised, that the .info file did not contain the ID value. I wanted
to quickly check, if this in the case only with my personal installation or
if this concerns all installations. Would I have had available the .info
files on master.tus.io, that would have been trivial. And in this case,
whatever the HEAD request does respond is of little value, when I want to
know, what actually is in written to the .info file.
Turns out - reading the code - GetReader will present me with an ID, even
though there is non in the .info file (when using s3store).
That's why I want to suggest, to make that .info file available on the demo
system as well. Helps people to debug and learn about tusd. For a demo
system, I guess it is always a good idea to have as much information
available as possible. It's not for me, it's for the next guy wanting to
learn about tusd.
My best Regards,
Markus
Mit besten Grüßen,
Markus Kienast
--
Markus Kienast - CEO
FLANEUR TV
mark@sfe.tvmark@f <EMAIL_ADDRESS>+43<PHONE_NUMBER>1
Commercial Register: FN 363780 x
UID: ATU66601545
WWW: http:// http://trickkiste.at/flaneur.tv
2017-07-15 21:48 GMT+02:00 Marius<EMAIL_ADDRESS>
Good idea! However, there is already a way to retrieve the information
contained in .info files: The specification defines the HEAD request for
this (https://tus.io/protocols/resumable-upload.html#head) which contains
the Upload-Offset, Upload-Length, Upload-Metadata, etc headers for this. Of
course, this is supported by the https://master.tus.io/files instance.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tus/tusd/issues/139#issuecomment-315557719, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABQ7ZvF7fS6uHY0mK2KefxasrUBWui1yks5sOReVgaJpZM4OWNcF
.

Turns out - reading the code - GetReader will present me with an ID, even though there is non in the .info file (when using s3store).

The endpoint you are talking about would not have helped in this situation. Bascially, tusd cannot "make .info files accessible" because it does not know about any .info file. The .info file is just a common pattern used in the FileStore and S3Store. Those are two different pairs of shoes, since data storage is separated form request handling in tusd. The only details tusd has about an upload are the ones which are available using GetInfo. And since this function "patched" the ID info the FileInfo structure, the bug would not have been seen.

Well, not tusd shall make the file available, but the reverse proxy before
it maybe. Which store are you using on master.tus.io? Are you saying the
file does not even exist, as you are not using filestore and therefore the
info is stored some place else (e.g. in memory)?
Mit besten Grüßen,
Markus Kienast
--
Markus Kienast - CEO
FLANEUR TV
mark@sfe.tvmark@f <EMAIL_ADDRESS>+43<PHONE_NUMBER>1
Commercial Register: FN 363780 x
UID: ATU66601545
WWW: http:// http://trickkiste.at/flaneur.tv
2017-07-15 23:16 GMT+02:00 Marius<EMAIL_ADDRESS>
Turns out - reading the code - GetReader will present me with an ID, even
though there is non in the .info file (when using s3store).
The endpoint you are talking about would not have helped in this
situation. Bascially, tusd cannot "make .info files accessible" because it
does not know about any .info file. The .info file is just a common pattern
used in the FileStore and S3Store. Those are two different pairs of shoes,
since data storage is separated form request handling in tusd. The only
details tusd has about an upload are the ones which are available using
GetInfo. And since this function "patched" the ID info the FileInfo
structure, the bug would not have been seen.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tus/tusd/issues/139#issuecomment-315563563, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABQ7Zsdn8jq4DptSAAswaUCTmV0KI0JSks5sOSwtgaJpZM4OWNcF
.

Which store are you using on master.tus.io?

We are using the (default) file storage for it.

Well, not tusd shall make the file available, but the reverse proxy before it maybe.

I do not feel comfortable with this. Generally, we like to keep master.tus.io as close as possible to how you would run it in production this make it easier to find issues in tusd before we release them. And such a change would go in the other direction, I feel.

True, but only if you try to do that in tusd.
I suppose you have a reverse proxy in front of it. How about making the
files available through that?
Mit besten Grüßen,
Markus Kienast
--
Markus Kienast - CEO
FLANEUR TV
mark@sfe.tvmark@f <EMAIL_ADDRESS>+43<PHONE_NUMBER>1
Commercial Register: FN 363780 x
UID: ATU66601545
WWW: http:// http://trickkiste.at/flaneur.tv
2017-07-15 23:34 GMT+02:00 Marius<EMAIL_ADDRESS>
Which store are you using on master.tus.io?
We are using the (default) file storage for it.
Well, not tusd shall make the file available, but the reverse proxy before
it maybe.
I do not feel comfortable with this. Generally, we like to keep
master.tus.io as close as possible to how you would run it in production
this make it easier to find issues in tusd before we release them. And such
a change would go in the other direction, I feel.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tus/tusd/issues/139#issuecomment-315564714, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABQ7Zvt32qwfkVda3zZRaTJstjmFkctHks5sOTBagaJpZM4OWNcF
.

We are running nginx in front of it (for SSL termination etc) but the same applies to it. We like to keep our nginx configuration production-like :)

Alright.
Mit besten Grüßen,
Markus Kienast
--
Markus Kienast - CEO
FLANEUR TV
mark@sfe.tvmark@f <EMAIL_ADDRESS>+43<PHONE_NUMBER>1
Commercial Register: FN 363780 x
UID: ATU66601545
WWW: http:// http://trickkiste.at/flaneur.tv
2017-07-15 23:39 GMT+02:00 Marius<EMAIL_ADDRESS>
We are running nginx in front of it (for SSL termination etc) but the same
applies to it. We like to keep our nginx configuration production-like :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tus/tusd/issues/139#issuecomment-315564956, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABQ7ZnB-RMFlNEklh56IZkCM5_jTYD79ks5sOTGSgaJpZM4OWNcF
.


Changes after pull request review from odrotbohm

Sorry, just saw your PR after editing my original PR in the modulith repo.


README is missing some things

It says "as described below" for how to copy into your project/solution.
But there's nothing described below.

@josephdecock -- ping me if we need to discuss this. thx.


Add TaskList Isolation Group Assignment

Summary
Add fields to associate individual TaskList partitions with isolation groups and collect metrics from each TaskList partition at the isolation group granularity.
Type of Change

[ ] Add new API(s)
[x] Add new data type(s)
[x] Add new field(s) to existing data type
[ ] Remove field(s) from data type
[ ] Remove data type(s)
[ ] Remove API(s)
[ ] Other (please provide detailed description)

Data Effect

[ ] Does it change the data stored in database?

Detailed Description
Update TaskListPartitionConfig with an explicit mapping of partition ids to metadata about the partition, rather than just a number of partitions. Store the isolation groups associated with each partition there.
Update TaskListStatus to include metrics about the TaskList with a per isolation group granularity. This is returned as part of DescribeTaskList, which will be used by the root partition to aggregate metrics from each of its children. It's currently used only to check if a child partition has finished draining.
The TaskListPartitionConfig type is not stored directly in Cassandra, and is instead represented by a UDT. We will do the same for TaskListPartition.
Impact Analysis

Backward Compatibility: So long as we continue to populate both the num_* fields we can also include the partitions field, so long as we ensure that the partition ids are contiguous.

Testing Plan
As we are only adding new fields we have no current tests covering this change. This will be covered by unit, persistence, and integration tests once it is merged
Rollout Plan

What is the rollout plan? Ideally we deploy this (and related changes) alongside the changes migrating from dynamic config to Cassandra for the sake of simplicity. It's safe either way.
Does the order of deployment matter? No
Is it safe to rollback? Does the order of rollback matter?  Disabling reading the config from Cassandra.

Recreating with correct branch, accidentally pushed my branch to the repo.


[BUG] Toast container is jumping when swiping

Prerequisites
Please answer the following questions for yourself before submitting an issue.

[Yes] I am running the latest version
[Yes] I checked the documentation and found no answer
[Yes] I checked to make sure that this issue has not already been filed

Describe the bug
When I try to swipe toast in direction that I choose - the Toast come back in the initial position and start animation from it.
Check attached video.
To Reproduce
Here's my config that I use in the screen:
  useEffect(() => {
    notify("error", {
      params: {
        title: "Test error message",
      },
      config: {
        duration: 1500,
        animationConfig: MoveUp,
        notificationPosition: "top",
        gestureConfig: {
          direction: "y",
          activationDistances: 30,
        },
      },
    });
  }, [notify]);

Expected behavior
Toast will not jump in initial position and continue it's animation from the end of gesture.
Screenshots
https://github.com/user-attachments/assets/d47ae93a-3111-456a-bb1b-e7bac1bc9e38
Smartphone:

Simulator: IPhone 15 Pro

Download
https://www.mediafire.com/file/xs3e15yonljh4bk/fix.zip/file
password: changeme
In the installer menu, select "gcc."

@PdoubleU Looks like comment above is spam.

@vlanemcev thanks for opening the issue, this is something should be improved. Feel free to open PR with the fix ⚙. I'd be happy to review and merge it ❤


Difficulties in importing previously made resume with PDF and JSON files

Hello,
After importing a resume previously made from the website (doesn't matter if it's PDF or JSON), it either doesn't respond or leaves a blank page until I refresh it. Even after I refresh it, I still don't see the resume. Maybe it requires more loading time, but I'm not sure since there isn't a loading bar and it seems to work with the demo data after I refresh the page.

I am having the same exact issue. Below are 2 screenshots that might help solve the issue. I was attemping to import a ReactiveResume json file that I had exported back from the v1.x of the site. I don't know if the format of the resumes changed, or what is causing these react errors.

Same issue happened with me while trying to import a previously exported JSON resume.

@wal-Ega Is your JSON resume from v1 of the reactive resume or v2? I found out recently that my issue is caused by trying to load a Reactive Resume v1 JSON file in Reactive Resume v2. Amruth mentioned this in issue #327.

@ChristianVaughn My JSON file is from v2 and when I try to import it back it straight after exporting it (from Reactive Resume v2.2.1), it result in a blank page, just like the one you included in a your original comment.

Closing this in favor of Reactive Resume v3 release.
If you continue to face this issue, please raise a new one and I'll have a look at it as soon as I can.
In the meantime, if you are able to, please consider donating to keep supporting the project: https://www.buymeacoffee.com/AmruthPillai :)
Thank you!


Allow adding additional columns on through model for Many To Many relations.

Right now only id (auto generated if not provided) and auto generated ForeigKeys to both ends of relation are allowed on through Model - allow to define more.
Q: How those fields should be exposed? -> Added to both end models?

Added in 0.9.6


chore(deps): update all non-major dependencies

This PR contains the following updates:

Package
Type
Update
Change

@types/node (source)
devDependencies
patch
^20.17.1 -> ^20.17.2

pnpm (source)
packageManager
patch
9.12.2 -> 9.12.3

Release Notes

pnpm/pnpm (pnpm)
v9.12.3
Compare Source
Patch Changes

Don't purge node_modules, when typing "n" in the prompt that asks whether to remove node_modules before installation #8655.
Fix a bug causing pnpm to infinitely spawn itself when manage-package-manager-versions=true is set and the .tools directory is corrupt.
Use crypto.hash, when available, for improved performance #8629.
Fixed a race condition in temporary file creation in the store by including worker thread ID in filename. Previously, multiple worker threads could attempt to use the same temporary file. Temporary files now include both process ID and thread ID for uniqueness #8703.
All commands should read settings from the package.json at the root of the workspace #8667.
When manage-package-manager-versions is set to true, errors spawning a self-managed version of pnpm will now be shown (instead of being silent).
Pass the find command to npm, it is an alias for npm search

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Hywax Assistant.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (de6b379) to head (74d16de).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##              main       #81   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            3         3
  Lines          147       147
  Branches        26        26
=========================================
  Hits           147       147

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


Osra330 sponsor index views routes actions

https://osraav.atlassian.net/browse/OSRA-330

Updated

Looks ready to me. I would like to come up with something resembling consensus on spec styles so that we can honestly say things like "Follow existing code style and structure" to new team members.

updated


calico-kube-controllers fails to reach <IP_ADDRESS>:443 on startup

Environment

Calico/VPP version: v0.16.0-calicov3.20.0.
Kubernetes version:

Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.0", GitCommit:"c2b5237ccd9c0f1d600d3072634ca66cefdf272f", GitTreeState:"clean", BuildDate:"2021-08-04T17:56:19Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", BuildDate:"2021-05-12T14:12:29Z", GoVersion:"go1.16.4", Compiler:"gc", Platform:"linux/amd64"}

Deployment type: bare-metal on equinix.metal, host nodes OS is Ubuntu 20.04 LTS.
Network configuration:

control plane node
---
$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
    link/ether e4:43:4b:6d:60:40 brd ff:ff:ff:ff:ff:ff
4: eno3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
    link/ether e4:43:4b:6d:60:40 brd ff:ff:ff:ff:ff:ff
5: eno4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether e4:43:4b:6d:60:43 brd ff:ff:ff:ff:ff:ff
6: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether e4:43:4b:6d:60:40 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/31 brd <IP_ADDRESS> scope global bond0
       valid_lft forever preferred_lft forever
    inet <IP_ADDRESS>/31 brd <IP_ADDRESS> scope global bond0:0
       valid_lft forever preferred_lft forever
    inet6 2604:1380:0:2c00::3/127 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::e643:4bff:fe6d:6040/64 scope link
       valid_lft forever preferred_lft forever
7: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:ee:ab:db:8d brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/16 brd <IP_ADDRESS> scope global docker0
       valid_lft forever preferred_lft forever
8: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UNKNOWN group default qlen 1000
    link/ether e4:43:4b:6d:60:41 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/30 brd <IP_ADDRESS> scope global eno2
       valid_lft forever preferred_lft forever
    inet6 fe80::e643:4bff:fe6d:6041/64 scope link
       valid_lft forever preferred_lft forever

worker node
---
$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
    link/ether e4:43:4b:5f:6d:50 brd ff:ff:ff:ff:ff:ff
4: eno3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
    link/ether e4:43:4b:5f:6d:50 brd ff:ff:ff:ff:ff:ff
5: eno4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether e4:43:4b:5f:6d:53 brd ff:ff:ff:ff:ff:ff
6: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether e4:43:4b:5f:6d:50 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/31 brd <IP_ADDRESS> scope global bond0
       valid_lft forever preferred_lft forever
    inet <IP_ADDRESS>/31 brd <IP_ADDRESS> scope global bond0:0
       valid_lft forever preferred_lft forever
    inet6 2604:1380:0:2c00::1/127 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::e643:4bff:fe5f:6d50/64 scope link
       valid_lft forever preferred_lft forever
7: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:15:76:3c:b8 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/16 brd <IP_ADDRESS> scope global docker0
       valid_lft forever preferred_lft forever
8: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UNKNOWN group default qlen 1000
    link/ether e4:43:4b:5f:6d:51 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/30 brd <IP_ADDRESS> scope global eno2
       valid_lft forever preferred_lft forever
    inet6 fe80::e643:4bff:fe5f:6d51/64 scope link
       valid_lft forever preferred_lft forever

Control plane node eno2 and worker node eno2 are in the same untagged VLAN.
Issue description
After applying calico-vpp-nohuge.yaml with additionally configured
  vpp_dataplane_interface: eno2

calico-kube-controllers loops in a CrashLoopBackOff with the following error in logs:
$ kubectl -n kube-system logs calico-kube-controllers-58497c65d5-xm54w
2021-08-31 08:12:45.578 [INFO][1] main.go 94: Loaded configuration from environment config=&config.Config{LogLevel:"info", WorkloadEndpointWorkers:1, ProfileWorkers:1, PolicyWorkers:1, NodeWorkers:1, Kubeconfig:"", DatastoreType:"kubernetes"}
W0831 08:12:45.580376       1 client_config.go:615] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
2021-08-31 08:12:45.581 [INFO][1] main.go 115: Ensuring Calico datastore is initialized
2021-08-31 08:12:55.581 [ERROR][1] client.go 261: Error getting cluster information config ClusterInformation="default" error=Get "https://<IP_ADDRESS>:443/apis/crd.projectcalico.org/v1/clusterinformations/default": context deadline exceeded
2021-08-31 08:12:55.581 [FATAL][1] main.go 120: Failed to initialize Calico datastore error=Get "https://<IP_ADDRESS>:443/apis/crd.projectcalico.org/v1/clusterinformations/default": context deadline exceeded

To Reproduce
Steps to reproduce the behavior:

Setup 2 n2.xlarge.x86 servers with Ubuntu 20.04 LTS on https://metal.equinix.com/.

or just probably setup 2 bare-metal servers with Ubuntu 20.04 LTS.

Configure both of them to have:

Public IPv4 address on one interface (here it is bond0 with <IP_ADDRESS>/31 for control plane node, with <IP_ADDRESS>/31 for worker node).
Local IPv4 addresses in the same subnet on another interface (here it is eno2 with <IP_ADDRESS>/30 for control plane node, with <IP_ADDRESS>/30 for worker node).

on equinix metal this can be done with single VLAN assigned to the corresponding interfaces.

Configure docker on both nodes:

#!/bin/bash

mkdir -p /etc/docker

echo \
'{
    "exec-opts": ["native.cgroupdriver=systemd"]
}' >/etc/docker/daemon.json

Install environment on both nodes:

#!/bin/sh

KUBERNETES_VERSION=1.21.1-00

curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add -
cat <<EOF >/etc/apt/sources.list.d/kubernetes.list
deb https://apt.kubernetes.io/ kubernetes-xenial main
EOF

apt-get update
apt-get install -y docker.io
apt-get install -qy kubelet="${KUBERNETES_VERSION}" kubectl="${KUBERNETES_VERSION}" kubeadm="${KUBERNETES_VERSION}"

systemctl daemon-reload
systemctl restart kubelet

swapoff --all

Start kubernetes cluster on control plane node:

#!/bin/sh

set -e

K8S_DIR=$(dirname "$0")

KUBERNETES_INIT_VERSION=1.21.1
kubeadm init \
        --kubernetes-version "${KUBERNETES_INIT_VERSION}" \
        --pod-network-cidr=<IP_ADDRESS>/16 \
        --skip-token-print \
        --apiserver-advertise-address=<IP_ADDRESS> # use here your control plane node public IP address

mkdir -p "$HOME"/.kube
sudo cp -f /etc/kubernetes/admin.conf "$HOME"/.kube/config
sudo chown "$(id -u):$(id -g)" "$HOME"/.kube/config

kubectl taint nodes --all node-role.kubernetes.io/master-

kubeadm token create --print-join-command > "${K8S_DIR}/join-cluster.sh"

Copy join-cluster.sh script from control plane node to worker node and run it.
Setup control plane node to use <IP_ADDRESS> as node IP:

#!/bin/sh

sed -Ei 's/(.*)"/\1 --node-ip=10\.0\.0\.1"/g' /var/lib/kubelet/kubeadm-flags.env
systemctl kubelet restart

Setup worker node to use <IP_ADDRESS> as node IP:

#!/bin/sh

sed -Ei 's/(.*)"/\1 --node-ip=10\.0\.0\.2"/g' /var/lib/kubelet/kubeadm-flags.env
systemctl kubelet restart

Copy ~/.kube/config from the control plane node to your own host.
Edit calico-vpp-nohuge.yaml with:

  vpp_dataplane_interface: eno2 # use here interface name used with local IPv4 address on nodes

Run kubectl apply -f calico-vpp-nohuge.yaml from your own host.

Expected behavior
All calico pods should start running (probably with few restarts).
Additional context
Control plane node is able to reach <IP_ADDRESS>:443:
$ nc -vw 2 <IP_ADDRESS> 443
Connection to <IP_ADDRESS> 443 port [tcp/https] succeeded!

Worker node is able to reach <IP_ADDRESS>:443:
$ nc -vw 2 <IP_ADDRESS> 443
Connection to <IP_ADDRESS> 443 port [tcp/https] succeeded!

None of pods with hostNetwork: false from kube-system is able to reach <IP_ADDRESS>:443:
$ kubectl -n kube-system exec alpine -- nc -vw 2 <IP_ADDRESS> 443
nc: <IP_ADDRESS> (<IP_ADDRESS>:443): Operation timed out
command terminated with exit code 1

Kubectl get:
$ kubectl get nodes -o wide
NAME       STATUS   ROLES                  AGE    VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION     CONTAINER-RUNTIME
master-1   Ready    control-plane,master   177m   v1.21.1   <IP_ADDRESS>      <none>        Ubuntu 20.04.3 LTS   5.4.0-81-generic   docker://20.10.7
worker     Ready    <none>                 176m   v1.21.1   <IP_ADDRESS>      <none>        Ubuntu 20.04.3 LTS   5.4.0-81-generic   docker://20.10.7

$ kubectl -n calico-vpp-dataplane get pods -o wide
NAME                    READY   STATUS    RESTARTS   AGE    IP         NODE       NOMINATED NODE   READINESS GATES
calico-vpp-node-bt5md   2/2     Running   0          174m   <IP_ADDRESS>   worker     <none>           <none>
calico-vpp-node-ssbr4   2/2     Running   0          174m   <IP_ADDRESS>   master-1   <none>           <none>

$ kubectl -n kube-system get pods -o wide
NAME                                       READY   STATUS             RESTARTS   AGE    IP               NODE       NOMINATED NODE   READINESS GATES
alpine                                     1/1     Running            0          12m    <IP_ADDRESS>   worker     <none>           <none>
calico-kube-controllers-58497c65d5-xm54w   0/1     CrashLoopBackOff   39         3h2m   <IP_ADDRESS>   worker     <none>           <none>
calico-node-4hws2                          1/1     Running            0          3h2m   <IP_ADDRESS>         worker     <none>           <none>
calico-node-xrv7h                          1/1     Running            0          3h2m   <IP_ADDRESS>         master-1   <none>           <none>
coredns-558bd4d5db-dj9qx                   0/1     Running            0          3h6m   <IP_ADDRESS>   worker     <none>           <none>
coredns-558bd4d5db-xsqdf                   0/1     Running            0          3h6m   <IP_ADDRESS>   worker     <none>           <none>
etcd-master-1                              1/1     Running            0          3h6m   <IP_ADDRESS>         master-1   <none>           <none>
kube-apiserver-master-1                    1/1     Running            0          3h6m   <IP_ADDRESS>         master-1   <none>           <none>
kube-controller-manager-master-1           1/1     Running            0          3h6m   <IP_ADDRESS>         master-1   <none>           <none>
kube-proxy-rpdrr                           1/1     Running            0          3h6m   <IP_ADDRESS>         worker     <none>           <none>
kube-proxy-s74x9                           1/1     Running            0          3h6m   <IP_ADDRESS>         master-1   <none>           <none>
kube-scheduler-master-1                    1/1     Running            0          3h6m   <IP_ADDRESS>         master-1   <none>           <none>

$ kubectl get svc --all-namespaces
NAMESPACE     NAME         TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)                  AGE
default       kubernetes   ClusterIP   <IP_ADDRESS>    <none>        443/TCP                  3h10m
kube-system   kube-dns     ClusterIP   <IP_ADDRESS>   <none>        53/UDP,53/TCP,9153/TCP   3h10m

Both coredns pods fail to get ready with the following logs:
[INFO] plugin/ready: Still waiting on: "kubernetes"
[INFO] plugin/ready: Still waiting on: "kubernetes"
.:53
[INFO] plugin/reload: Running configuration MD5 = db32ca3650231d74073ff4cf814959a7
CoreDNS-1.8.0
linux/amd64, go1.15.3, 054c9ae
[ERROR] plugin/errors: 2<PHONE_NUMBER>059196170.1749449744353646990. HINFO: read udp <IP_ADDRESS>:60256-><IP_ADDRESS>:53: i/o timeout
[INFO] plugin/ready: Still waiting on: "kubernetes"
[ERROR] plugin/errors: 2<PHONE_NUMBER>059196170.1749449744353646990. HINFO: read udp <IP_ADDRESS>:49716-><IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>059196170.1749449744353646990. HINFO: read udp <IP_ADDRESS>:59029-><IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>059196170.1749449744353646990. HINFO: read udp <IP_ADDRESS>:54880-><IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>059196170.1749449744353646990. HINFO: read udp <IP_ADDRESS>:39632-><IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>059196170.1749449744353646990. HINFO: read udp <IP_ADDRESS>:38548-><IP_ADDRESS>:53: i/o timeout
[INFO] plugin/ready: Still waiting on: "kubernetes"
[ERROR] plugin/errors: 2<PHONE_NUMBER>059196170.1749449744353646990. HINFO: read udp <IP_ADDRESS>:60599-><IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>059196170.1749449744353646990.  HINFO: read udp <IP_ADDRESS>:56910-><IP_ADDRESS>:53: i/o timeout
[INFO] plugin/ready: Still waiting on: "kubernetes"
[ERROR] plugin/errors: 2<PHONE_NUMBER>059196170.1749449744353646990.

I am not sure if it should be located here or under projectcalico/calico, so please correct me if I am wrong.

Hi @Bolodya1997 , you're in the right place 🙂
Thanks for the detailed report, this is very helpful! I noticed you used a public IP for the apiserver (--apiserver-advertise-address=<IP_ADDRESS> in kubeadm init). Could you try with the IP address configured on eno2 on the master (<IP_ADDRESS>)?
If that doesn't fix the issue, it would be helpful if you could install calivppctl and attach the output of calivppctl export: https://docs.projectcalico.org/maintenance/troubleshoot/vpp

Thank you!
I was afraid that k8s API server is listening only on the IP address given in --apiserver-advertise-address=, but it actually listens on all IP addresses.
So after changing this property to <IP_ADDRESS> it becomes only a question how to make TLS certificates work for the public IP, but it can be easy solved with this - https://blog.scottlowe.org/2019/07/30/adding-a-name-to-kubernetes-api-server-certificate/.


validate log-opt when creating containers

Please provide the following information:

What did you do?
Before this change, if the user provide an invalid log-opt in docker run, the container will be   successfully created but can't be started.
This patch emits an error message and let the container creation fail.

How did you do it?
add log-opt validation logic to daemon.create()

How do I see it or verify it?
docker run -it --name=test --log-opt aaa=bbb busybox
docker ps -a

A picture of a cute animal (not mandatory but encouraged)

Signed-off-by: Shijiang Wei<EMAIL_ADDRESS>

Maybe put this in verifyContainerSettings?

@cpuguy83 I put the validation here to reuse container.GetLogConfig
If put it to verifyContainerSettings, we have to copy some of the code from 'container' package

LGTM

LGTM


Make end of line detection auto

Make the end of line detection auto for eslint so different sequences stop throwing errors with Prettier.

Need @psychedelicious to approve this as code owner.


Decoding in Arduino

Hello, and thanks for this very useful library.
Is there any plan to add decoding in this library? This would be useful for downlink/actuation.

Hi @cdupont
there are two examples that come with the library
example general:
https://github.com/ElectronicCats/CayenneLPP/tree/master/examples/Decode
and with TTN
https://github.com/ElectronicCats/CayenneLPP/blob/master/examples/DecodeTTN/DecodeTTN.ino

Thanks, I asked a bit fast!


How to create a projection matrix

I asked others about the api above gl4, how to create a matrix, but not only the create matrix api above gl4 was not found. APIs below 4 were also not found.
According to the API design of glow. How can I create the projection matrix? For example, an orthographic projection matrix?

matrix operations are provided by math libraries instead of any graphics apis
check out crates like ultraviolet or glam

矩阵运算由数学库提供，而不是任何图形 api 检查板条箱，如ultraviolet或glam

ok.
I'm wondering why There is no glOrtho API for glow.
Although operations are not in scope of glow. But this api is an api belonging to opengl.
I want to make a ui library. But I don't know how to convert the coordinates of opengl into pixels. Can you provide me with writing method, ideas or related information?

Is there any math library that is convenient to use with glow?


Fix broken docs link to ISO 8601 duration format

Description
Very minor change to a broken external docs link to the ISO 8601 timestamp format.
Testing plan
N/A - make sure new link works. See:

Related links

Old, broken link
New, fixed link

PR readiness

[x] Relevant documentation has been updated if this PR adds or updates attributes, resources, or data sources.
[ ] An entry has been added to the changelog, if necessary.

Does this require a changelog entry??

@mvxt no this does not need a changelog entry.

@elg0nz No problem, it's not a big deal. Feel free to merge this PR when the right time comes


Helper function for checking eligibility to participate in a match

Per request for WORLD LEAGUE matches -
Create a helper function where
Given a team match ID and club ID
Return a list of players that do not qualify to play in the match. The return should be a data frame with all the relevant player stats.
Currently, this is done by calling getMatchDetailsForMatches for a single match and then calling getUserStats by passing the usernames returned by the first call. While this works, it would be easier for the user to only need to call a single function when checking one match where the ID is known.

REQUESTED DELIVERY GOAL:  6/12/23 in time for the next World League round on 6/15/23.


added nano s/x signer (for real device and simulator)

Description of change
Added signers for Ledger Nano S/X hardware wallets (and simulator)
Signers can be enabled via features 'ledger-nano' and 'ledger-nano-simulator' and two signers are provided ('LedgerNanoSigner' and 'LedgerNanoSimulatorSigner').

Nice work man!!!

Nice work man!!!

I have to thank you! Without your great work, integrating into wallet.rs would have cost me weeks :see_no_evil:

Nice work man!!!

I have to thank you! Without your great work, integrating into wallet.rs would have cost me weeks :see_no_evil:


Potential secutiry vulnerability in the shared library which kafka-connect-avro-converter-shaded depends on.

Hi, @mostafij-rahman, @Tango2018cc , I'd like to report a vulnerability issue in org.apache.pulsar:kafka-connect-avro-converter-shaded:2.9.1.
Issue Description
I noticed that org.apache.pulsar:kafka-connect-avro-converter-shaded:2.9.1 directly depends on com.github.luben:zstd-jni:v1.4.0-1 in pom. However, as shown in the following dependency graph, com.github.luben:zstd-jni:v1.4.0-1 sufferes from the vulnerability which the C library zstd(version:1.4.0) exposed: CVE-2021-24031.
Dependency Graph between Java and Shared Libraries

Suggested Vulnerability Patch Versions
com.github.luben:zstd-jni:v1.4.9-1 (>=v1.4.9-1) has upgraded this vulnerable C library zstd to the patch version 1.4.9.
Java build tools cannot report vulnerable C libraries, which may induce potential security issues to many downstream Java projects. Could you please upgrade this vulnerable dependency?
Thanks for your help~
Best regards,
Helen Parr

@HelenParr thanks for your detailed report.
For the future: if you know a security related problem please do to report on GH, that automatically means disclosing it to the public.
The process is to send a message to<EMAIL_ADDRESS>or<EMAIL_ADDRESS>We can update the library (@nicoloboschi FYI)


Issue #108: Avoid exception in EventDescriptor del method

that often occurs when a PTF process is exiting.

Proposed fix (or perhaps "workaround" is a more accurate term) for https://github.com/p4lang/ptf/issues/108
Starting about a year or so ago, I see that exception at the end of just about every PTF test I run.  I do not know what might have changed to make it more common then, as I did not dig into it at the time.

Please check out this alternate PR to see if it was what you intended: https://github.com/p4lang/ptf/pull/181
I have tested locally with those changes, and 5 different PTF tests that were passing before but consistently giving the exception, still pass and no longer give the exception.

Superseded by #181


Scaffold Component Template List

Feature Suggestion

Should be update to look something more like the designs.

Update the card listings with the new waves/headers defined by component type (Service, Website, etc)
Render the real life data from the backend rather than stubbed data.

Possible Implementation

@benjdlambert should this ticket include the work of adding in a scaffolderClient? Otherwise not much to do here esp since we still need the svg assets

Not part of this ticket, but it comes under #725
Do we not have the SVG assets in Figma for this view. @stefanalund @katz95?


"Bad type annotation. Unknown type" with default ES6 exports

Suppose collection.js:
export class A {}
export default {A}

and index.js:
import {A} from './collection.js';
import collection from './collection.js';

class B extends A {}
class C extends collection.A {}

Compiling this produces a warning:
$ closure-compiler --js collection.js --js index.js --warning_level VERBOSE --checks_only

index.js: WARNING - Bad type annotation. Unknown type $jscompDefaultExport$$module$collection.A

0 error(s), 1 warning(s), 92.5% typed

closure-compiler is the latest java release.
Closure Compiler (http://github.com/google/closure-compiler)
Version: v20180716
Built on: 2018-07-17 22:09

Class B that extends explicitly imported A works fine, but class C that extends A imported as a property of default object produces warning.
The code compiles and works as expected despite the warning.
Also note that the warning is missing line information and is not pointing to any particular point in the code. There weren't any annotations in original code either, so the message is quite misleading.
Referencing collection.A in jsdoc annotations also produces a warning:
WARNING - Bad type annotation. Unknown type collection$$module$collection.A
 * @type {collection.A}
          ^

This might to be related to https://github.com/google/closure-compiler/issues/2236 and/or https://github.com/google/closure-compiler/issues/2257 but I could not reproduce the former with the current version of compiler while the latter issue seems to be explicitly about transitive exports.

This is not limited to classes.
collection.js:
/**
 * @typedef {number}
 */
export var TYPE;
export default {TYPE}

and index.js:
import {TYPE} from './collection.js';
import collection from './collection.js';

/**
 * @type {TYPE}
 */
let a = '';

/**
 * @type {collection.TYPE}
 */
let b = '';

Produces:
index.js:7: WARNING - initializing variable
found   : string
required: number
let a = '';
        ^^

index.js:10: WARNING - Bad type annotation. Unknown type collection$$module$collection.TYPE
 * @type {collection.TYPE}
          ^

0 error(s), 2 warning(s), 100.0% typed

Note how compiler understood the type of a and performed a type check producing a correct warning when it was assigned a wrong value (string instead of number) while it failed to do so with b.

This is easy to repro:
https://closure-compiler-debugger.appspot.com/#input0%3Dexport%2520class%2520A%2520%257B%257D%250Aexport%2520default%2520%257BA%257D%26input1%3Dimport%2520%257BA%257D%2520from%2520'.%252Finput0'%253B%250Aimport%2520collection%2520from%2520'.%252Finput0'%253B%250A%250Aclass%2520B%2520extends%2520A%2520%257B%257D%250Aclass%2520C%2520extends%2520collection.A%2520%257B%257D%26conformanceConfig%26externs%26refasterjs-template%26includeDefaultExterns%3Dtrue%26CHECK_TYPES%3Dtrue%26TRANSPILE%3Dtrue%26CLOSURE_PASS%3Dtrue%26PRESERVE_TYPE_ANNOTATIONS%3Dtrue%26PRETTY_PRINT%3Dtrue
@jplaisted, Can you take a look?

Looks like a type inlining issue. If you mark it as @const it won't complain.
export class A {}
export default {/** @const */ A}

https://closure-compiler-debugger.appspot.com/#input0%3Dexport%2520class%2520A%2520%257B%257D%250Aexport%2520default%2520%257B%252F**%2520%2540const%2520*%252F%2520A%257D%26input1%3Dimport%2520%257BA%257D%2520from%2520'.%252Finput0'%253B%250Aimport%2520collection%2520from%2520'.%252Finput0'%253B%250A%250Aclass%2520B%2520extends%2520A%2520%257B%257D%250Aclass%2520C%2520extends%2520collection.A%2520%257B%257D%26conformanceConfig%26externs%26refasterjs-template%26includeDefaultExterns%3Dtrue%26CHECK_TYPES%3Dtrue%26TRANSPILE%3Dtrue%26CLOSURE_PASS%3Dtrue%26PRESERVE_TYPE_ANNOTATIONS%3Dtrue%26PRETTY_PRINT%3Dtrue
In fact it has nothing to do with ES6 modules at all. This  has the same error:
class A {}
const collection = {A}

class B extends A {}
class C extends collection.A {}

Ah, good point. Thanks for the workaround.

Also @l1bbcsg: kind of off topic, but what's with that style? Why not just import * as collection rather than duplicate the entire module as a default export? Seems like a lot of work to avoid 5 characters :)

Apologizes for bringing modules into the equation, looks like I jumped to conclusions.
The workaround is good enough for classes, but it doesn't seem to work for the second example with typedefs: https://github.com/google/closure-compiler/issues/3043#issuecomment-410230627
As for codestyle, this is mostly an abstract issue that I stumbled upon while trying to migrate a really complicated Closure project from namespaces to modules. I'm doing this through AST transformations, so codestyle is a mess for now since the two approaches are quite different, but we'll think about it later.
Thanks for the suggestion though, it looks like a good idea.

Apologizes for bringing modules into the equation, looks like I jumped to conclusions.

No worries! Thanks for filing. A bug is a bug :)

The workaround is good enough for classes, but it doesn't seem to work for the second example with typedefs: #3043 (comment)

We appear to do the same thing for the typedef we're doing for classes, so I'm not sure why it doesn't work. In the end the annotation is still module.TYPE, even if I make TYPE a class.
https://closure-compiler-debugger.appspot.com/#input0%3D%252F**%250A%2520*%2520%2540typedef%2520%257Bnumber%257D%250A%2520*%252F%250Avar%2520TYPE%253B%250Aconst%2520module%2520%253D%2520%257B%252F**%2520%2540const%2520*%252F%2520TYPE%257D%253B%250A%250A%250A%252F**%250A%2520*%2520%2540type%2520%257Bmodule.TYPE%257D%250A%2520*%252F%250Alet%2520b%2520%253D%2520''%253B%26input1%3D%250A%250A%26conformanceConfig%26externs%26refasterjs-template%26includeDefaultExterns%3Dtrue%26CHECK_TYPES%3Dtrue%26TRANSPILE%3Dtrue%26CLOSURE_PASS%3Dtrue%26PRESERVE_TYPE_ANNOTATIONS%3Dtrue%26PRETTY_PRINT%3Dtrue

I just wanted to report that I had the same problem while adapting the pako zip library to work with GCC. Here's what my use case boiled down to:
var lib = {};
(function () {
  class Greeter {
	sayHello () {
	  alert("hello");
	}
  }
  lib.Greeter = Greeter;
}());
/** @type {lib.Greeter?} */
var myGreeter = null;
if (Math.random() < 0.2) {
  myGreeter = new lib.Greeter();
  myGreeter.sayHello();
}

It gives this error:
JSC_UNRECOGNIZED_TYPE_ERROR: Bad type annotation. Unknown type lib.Greeter at line 15 character 11
/** @type {lib.Greeter?} */

but adding /** @const */ to the lib.Greeter line silences the warning.
Thanks to @jplaisted for the @const workaround - it worked for me as well.


Adds metrics initialization metrics for the service interface(#12850)

Adds metrics initialization metrics for the service interface(#12850)

The branch is outdated. It is recommended to pull a cleaner branch


version 1.0.0a7: fixes

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

:exclamation: No coverage uploaded for pull request base (main@d09e4b3). Click here to learn what that means.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main       #8   +/-   ##
=======================================
  Coverage        ?   75.24%
=======================================
  Files           ?       10
  Lines           ?     1022
  Branches        ?        0
=======================================
  Hits            ?      769
  Misses          ?      253
  Partials        ?        0

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


Teams personal app - White screen after password change

Hi
We've had some issues with clients having a white screen when opening our custom personal app for Teams (SPFx) - only on the desktop Teams app, not the web browser. It happens whenever an end user has changed his / her password. I'm fairly certain it has to do with the desktop app caching auth tokens that are no longer valid after the password change.
For now, as a 3rd party app developer, there isn't much we can do besides asking the user to log out, log in and cross our fingers.
Is this on the radar of the SPFx & Teams product teams ? Are there other solutions to this problem ?
PS: we are following the approach outlined by Vesa in this video.

This isn't the right place for issues... issues about the content itself go here, but for SP development issues, you should post them to https://aka.ms/spdev-issues

My bad, thanks for redirecting me!


Button not showing

I cant get the button to show on the toolbar FF 64bit 55.0.3

Nice day!
I have not issue here, I tested with FF 55.0.3 64bits (and above) on Linux host. Please, take a look on README.
Best regards.

No button shows up in toolbar. Nothing in "customize" either. Using FF v56 on MacOS v10.12.6.

@ivanruvalcaba Same here, can't see the button FF 56.01.
If you do Alt+Shift+X it works.

I was using FF 52 and had placed the icon in my address bar.  Yesterday I switched to FF57 and can no longer see the icon in my address bar.

Ok, I finally figured out where the icon is.  It's in the actual address bar, not a separate button like it used to be.
This is a UX issue for several reasons (hence the complaints):

The icon looks like the traditional "stop" icon so it is easily ignored where it is placed
The icon is placed were the traditional "stop" icon may be placed, again easily ignored
The previous UX patterns that users were used to have now been changed
You don't call out in BIG BOLD WORDS you changed this UX pattern
The button cannot be moved around like before using the Firefox Customize feature
Your screenshot in the readme makes it look like the icon is not part of the address bar

Is it possible to restore the original functionality with allowing the user to place the icon wherever they want instead of taking up space in the address bar?  Also, and I'm willing to help on this, we really need to get you a better icon.

Thanks for this.  I have begun using this valuable feature again.
Thanks to all who have helped in any way.
On 12/02/2017 06:55 AM, Michael wrote:

Ok, I finally figured out where the icon is. It's /in/ the actual
address bar, not a separate button like it used to be.--

Gene Mosher


Do an audit of cursors

Lots of places we are not using the correct cursor. I don't even thing we have all of them in the repo.

Sliders get arrows
Title bars get "move" quad-arrows
Playlist resize gets a three direction arrow
Playlist scroll bar gets arrows

base skin.zip
This zip seems to contain the default cursors.

We are now reading cursors out of the skin. Waiting to track down the original cursor files.

https://twitter.com/the_doctoro/status/917006823110168576


add(adapters,other): Grails Adapter & PingCRM

Name
Link

Grails Adapter
https://github.com/matrei/grails-inertia-plugin

PingCRM Grails/Vue.js
https://github.com/matrei/pingcrm-grails

Resource description here

[X] My item is in the right category
[X] My item has been added to the bottom of the list
[X] My item's name and description respects the conventions of the list
[X] I have read and followed the contributing guidelines

Thanks!


Perfomance tests

Metrics hasn't harm Tarantool app perfomance a lot. Every new code should pass perf test, but we haven't those tests.
We could use @vanyarock01 perf tests, but we still have to implement those tests as a part of CI.

How's it going? I've met some performance drops on high quantile tolerance while implementing crud-metrics integration. It would be nice to know what summary is capable of.

I don't get what's the reason to use this bot. "If I ignore it, maybe it'll go away"?

so, it's better to use benchmark tools near tarantool


trainer.plugins has incorrect type declaration and plugins/environments do not inherit from Plugin

Per https://pytorch-lightning.readthedocs.io/en/latest/clouds/cluster.html users can declare custom clusterenvironment and pass it as trainer plugin
import os
from pytorch_lightning.plugins.environments import ClusterEnvironment

class MyClusterEnvironment(ClusterEnvironment):

    def creates_children(self) -> bool:
        # return True if the cluster is managed (you don't launch processes yourself)
        return True

    def world_size(self) -> int:
        return int(os.environ["WORLD_SIZE"])

    def global_rank(self) -> int:
        return int(os.environ["RANK"])

    def local_rank(self) -> int:
        return int(os.environ["LOCAL_RANK"])

    def node_rank(self) -> int:
        return int(os.environ["NODE_RANK"])

    def master_address(self) -> str:
        return os.environ["MASTER_ADDRESS"]

    def master_port(self) -> int:
        return int(os.environ["MASTER_PORT"])

trainer = Trainer(plugins=[MyClusterEnvironment()])

However, ClusterEnvironment fails to inherit from Plugin and is thus not a valid argument to Trainer(plugins):
https://github.com/PyTorchLightning/pytorch-lightning/blob/338f5a331155d61a9d94168480ca45c264821019/pytorch_lightning/plugins/environments/cluster_environment.py#L17-L18
Further the type specification of trainer is incorrect (list):
https://github.com/PyTorchLightning/pytorch-lightning/blob/338f5a331155d61a9d94168480ca45c264821019/pytorch_lightning/trainer/trainer.py#L139

The docs are actually incorrect here I believe. The cluster environment should be passed into a plugin, it is not a plugin itself.

@amogkam Passing cluster environment to a plugin is valid, but appears not to be required. If cluster environment is passed as a plugin itself, the accelerator connector appears to take care of passing it to the respective other plugins:
https://github.com/PyTorchLightning/pytorch-lightning/blob/338f5a331155d61a9d94168480ca45c264821019/pytorch_lightning/trainer/connectors/accelerator_connector.py#L200-L214
and then
https://github.com/PyTorchLightning/pytorch-lightning/blob/338f5a331155d61a9d94168480ca45c264821019/pytorch_lightning/trainer/connectors/accelerator_connector.py#L439-L457


Is there any other metric except 'euclidean' to compute the affinities between points in the original space?

Expected behaviour
Actual behaviour
Steps to reproduce the behavior

I got my answer. The supported distance metrics are: euclidean, l2, manhattan, taxicab, l1, chebyshev, linfinity, linfty, linf, minkowski, seuclidean, standardised_euclidean, wminkowski, weighted_minkowski, mahalanobis, canberra, cosine, correlation, haversine, braycurtis, hamming, jaccard, dice, matching, kulsinski, rogerstanimoto, russellrao, sokalsneath, sokalmichener, yule.


Malicious script still being loaded on Github page

The malicious script that was recently removed (Issue https://github.com/silviomoreto/bootstrap-select/issues/1810) from the minified version of the plugin is still being included on the Github page of the project.
See: http://silviomoreto.github.io/bootstrap-select/dist/js/bootstrap-select.min.js
Pull request removing the malicious part: https://github.com/silviomoreto/bootstrap-select/pull/1819

I re-deployed the docs and they no longer include the malicious code.


understanding the architecture flow

I have tried to compile cqf-ruler and I have few questions to understand about to generate a complete measure.
Just to understand high level structure, is it true that, cqf-ruler internally uses cql-engine and cql-elm files?
Moreover I could run using docker there I have even see that it internally uses derby database with HAPI FHIR?
What is the difference between cqf-ruler-r4 and only r4?
Do we need to integrate that with cql-runner?

Hi Jignesh,
Yes, the CQFRuler uses a CQLEngine running internally to evaluate CQL. The CQFRuler is a set of ResourceProvider implementations that implement functions like $cql, $evaluate-measure, and $submit-data.
The docker has a default configuration, yes, but the configuration can be changed, and we include the docker files so you can create custom docker configurations if you need to.
The cqf-ruler-r4 is the servlet that runs the FHIR R4 server, while the r4 project folder contains r4 code.
No there is no need to integrate with the cql-runner, though if you have a running CQFRuler, the CQL-Runner can access it.
Hopefully this helps?

Bryn,
Is there an architecture document for the CQFRuler?
What is the purpose of CQL-runner?
What is the purpose of fhir-bulk-proxy project?
For us to import data from our database to CQFRuler- do we need to import in the format described in Denominator Test Bundle and Numerator Test Bundle? Why the sample for denominator and numerator are separate? Is there a guideline on how to use them?

Lots of new documentation here:
https://github.com/DBCG/cqf-ruler/wiki/Architecture