CORS policy

Hi,
I was using the m3u8 links in the README.md to play test feeds during development only. It was working until a few days ago. Now I get the following error in both Chrome and Firefox:
Access to fetch at 'https://1b1ecb7efeb2.us-east-1.playback.live-video.net/api/video/v1/us-east-1.533826271312.channel.3NcFegvmOax6.m3u8?player_version=1.0.0' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

It seems that something on the server side changed https://stackoverflow.com/questions/52412511/cors-and-request-headers-errors-on-live-streaming-using-videojs
Could CORS be allowed again please?
It's very handy to be able to connect to a always on feed, it simplifies development & testing.
Thank you.

Hey @cabello, I don't recognize that playback URL - it doesn't appear to be in our README.md based on a quick search. Is this perhaps a playback URL that you generated?
I checked our test streams, and they all appear to be working correctly with the appropriate CORS headers.

Hi @tonyjin
Thank you for the quick reply, you are correct that was a custom stream that I created, my bad. Sorry!
The videos in the README look fine 🙇


Translate Ripple code into Lydown code

Usage: lydown translate 01-choro
The above command will translate the entire subdirectory, leaving the role files in place and creating new lydown files in the same directory
Translation code will reside in lib/lydown/translation/ripple
Parsing using custom treetop rules
Look for macros in _work.yml, _movement.yml files
Parse relative command to determine octave of first note.
Ignore curly brackets
Parse and translate note events: note head, duration, expressions
Parse key signature and translate chromatic note names into diatonic ones
Parse and translate duration macros
Look for lyrics files and as them to output under a =lyrics section

Works pretty good for the moment. In the future I'd like to use this feature to translate the entire music repository. For this we'll need:

Feature parity with Ripple, especially regarding layout, and score/part specific code.
Translation of figures (the syntax is very similar). Not sure if standalone figure syntax is already implemented in lydown.
Putting named macros into work/movement files.

Closing for now. May reopen again in the future if any concrete work pops up.


Git authentication

Trying to publish while the repo url contains username will still ask me for username.
Leaving empty or filling in the username and password will result in authentication fail by remote server.
Example,
repo url<EMAIL_ADDRESS>username:  or FilipDz
password: ******
output:
remote: Invalid username or password. If you log in via a third party service you must ensure you have an account password set in your account profile.
fatal: Authentication failed for<EMAIL_ADDRESS>

Duplicate of #1138


NIFI-9504 Upgrade Logback from 1.2.8 to 1.2.9

Description of PR
NIFI-9504 Upgrades Logback from 1.2.8 to 1.2.9 in order to address potential vulnerabilities associated with non-standard logging configurations as described in CVE-2021-42550.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[X] Has your PR been rebased against the latest commit within the target branch (typically main)?

[X] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Push additional commit upgrading Log4j 2 from 2.16.0 to 2.17.0 for NIFI-9505.

Thanks for your contribution @exceptionfactory, 👍 will merge


error codes; error handling

Note that this does not catch all our errors, however it tells the user to report the bug so effectively we should get to 100% nice errors via reports.


Coredump after  to_binary() => to_term() roundtrip

I am able to reproduce a core dump with the simple roundtrip() function below (see https://github.com/evnu/rustler_core_dump). The function takes a term, encodes it into a binary, reencodes into a term and returns that term wrapped with a 1 within a tuple.
#[macro_use]
extern crate rustler;

use rustler::{NifEncoder, NifEnv, NifResult, NifTerm};

rustler_export_nifs! {
    "Elixir.RustlerCoreDump",
    [
        ("roundtrip", 1, roundtrip),
    ],
    None
}

fn roundtrip<'a>(env: NifEnv<'a>, args: &[NifTerm<'a>]) -> NifResult<NifTerm<'a>> {
    let original: NifTerm = args[0].decode()?;
    let binary = original.to_binary();
    let roundtripped: NifTerm = binary.to_term(env);
    Ok((1, roundtripped).encode(env))
}

When I use the following Elixir implementation to load the nif, running test results in a core dump.
defmodule RustlerCoreDump do
  use Rustler, otp_app: :rustler_core_dump, crate: "rustler_core_dump"

  def roundtrip(term), do: throw(:nif_not_loaded)

  def test do
    reference = make_ref()
    IO.inspect(reference)
    {1, reference} = roundtrip(reference)
    IO.inspect(reference)
  end
end

Note that inspecting the resulting reference assigned after roundtrip seems to be crucial: I need to either IO.inspect(reference) or match with {1, ^reference} = roundtrip(reference) to reproduce this.
Running the Example
 mix run -e RustlerCoreDump.test
==> rustler
Compiling 1 file (.yrl)
Compiling 1 file (.xrl)
Compiling 2 files (.erl)
Compiling 6 files (.ex)
Generated rustler app
==> rustler_core_dump
Compiling NIF crate :rustler_core_dump (native/rustler_core_dump)...
    Finished release [optimized] target(s) in 0.0 secs
Compiling 1 file (.ex)
Generated rustler_core_dump app
#Reference<0.3640706538.2123366403.78090>
[1]    7004 segmentation fault (core dumped)  mix run -e RustlerCoreDump.test

Version Information
rust:
rustc -V
rustc 1.26.0 (a77568041 2018-05-07)

Elixir:
elixirc -v
Erlang/OTP 20 [erts-9.3] [source] [64-bit] [smp:4:4] [ds:4:4:10] [async-threads:10] [hipe] [kernel-poll:false]

Elixir 1.6.4 (compiled with OTP 20)

mix.lock:
%{
  "rustler": {:git, "https://github.com/hansihe/rustler", "00bcc871cdacc70af35ed29daeb9e3f37cd3a1f4", [sparse: "rustler_mix"]},
}

I added some debugging output:
fn roundtrip<'a>(env: NifEnv<'a>, args: &[NifTerm<'a>]) -> NifResult<NifTerm<'a>> {
    let original: NifTerm = args[0].decode()?;
    eprintln!("{:?}", original);
    let binary = original.to_binary();
    let roundtripped: NifTerm = binary.to_term(env);
    eprintln!("{:?}", roundtripped);
    Ok((1, roundtripped).encode(env))
}

Resulting run:
mix run -e RustlerCoreDump.test
Compiling NIF crate :rustler_core_dump (native/rustler_core_dump)...
   Compiling rustler_core_dump v0.1.0 (file:///home/mo/tools/rustler_core_dump/native/rustler_core_dump)
    Finished dev [unoptimized + debuginfo] target(s) in 0.47 secs
#Reference<0.441875240.1587806209.52051>
#Ref<0.441875240.1587806209.52051>
<cp/header:0x0000000000000000>

A similar bug was fixed with OTP
20.3.7:

OTP-15080    Application(s): erts
          Fixed bug in enif_binary_to_term which could cause
          memory corruption for immediate terms (atoms, small
          integers, pids, ports, empty lists).

I can still trigger the segfault with the example above.

@evnu Could you test it again on latest master?

ah, you beat me to it @hansihe

The example does not segfault any more, thank you! I needed to adapt the conversion into a Term as to_binary() now returns an OwnedBinary:
    let roundtripped: Term = binary.release(env).to_term(env);

Note that the resulting roundtripped does not equal the value put into the NIF:
    eprintln!("{:?}", original == roundtripped); #=> false

Converting it within Elixir with :erlang.binary_to_term/1 produces the original value again, though. I guess I would need to use env::binary_to_term() to convert back into the original term.


Fixed documentation issues in access dataone and editing

See issue #66

Excellent, thanks @jeanetteclark! I took a quick look and it all looks good. I did make one minor comment. Would you mind making that change, re-pushing the commit back to your fork and I'll merge it?

@amoeba I wrote boolean because it was in the style of other variable definitions in the package (there are a lot of boolean's in there). Should I change them all?

Ah, of course I wrote them that way. No, we can keep this PR straight to the point.

Thanks for the changes!
I saw you removed the @export from sysmeta_to_other_entity. You probably saw the Deprecated call inside it. I did that because I renamed the function but it's not nice for your users to just rename functions between package versions. So I left the old function name as is but replaced its body with a Deprecated call. Given that it's been a while since I deprecated it, I bet no one would even call it anymore so I'm just going to remove it entirely. Not a big deal either way.


Attempt to fix the operator rename problem

See #40 — this doesn't do quite what we want, as we're stuck on operator from April.  Go modules doesn't like operator versions >1, but that's actually irrelevant anyway since credsgen is now in quarks-secrets.


🏃 Getting started

This is an issue reserved for the TU Delft Student Software Project '23
The goal for the first 3 weeks of the project is to familiarise yourselves with CounteractualExplanations.jl and Julia more generally. To help you get started, we have put together a set of smaller tasks/issues.

[ ] #103
[ ] #119
[ ] #124

Optionally, you could also look at

[ ] #114

These issues have subtasks. Try to complete as many of those as you can.

I've added #124. It's a very simple one, but should help you familiarise yourselves with the package architecture.


Enhance: About us page

I would like to change the ui/ux of the about us section.

I would also like to reduce the unwanted space between the navbar and the heading of the home page.
So, please assign this issue to me under GSSOC'23.
Thanking you.

Is this issue assigned to anyone? I am interested in this.


Job Explorer options

What is the significance of the below Explorer Job entries.  There are entries for 1, 2, 3, 4 and 5 but I couldn't find what they related to or if they are even valid for 1.13.x.
Should these be changed to the material names for 1.13.x (assuming it is for the first five blocks in game)? Or are these something else that should be explained better in the jobConfig.yml file?

Read the comments in the example job.
https://github.com/Zrips/Jobs/blob/master/src/main/resources/jobConfig.yml#L438

Thanks - it must have been removed with all the editing I did unintentionally. Note there is a typo in the comments (Change "ho" to "who")

In fact, I do not even know what this Explore job is doing. This plugin was written by Zrips and I have been back for half a month to help her, but I did not know much about what was doing.
I think this Explore job is doing it to count the chunks in that particular world. Or something similar.

understood and appreciate you helping out :-)
The way I was trying to use this one is every player would autojoin the Explorer job as a means to earn some money/points/exp while they get around the world and basically explore.  Then when they are ready to settle on a location, they would then join the job(s) that pay for the work they are doing while still holding onto the explorer job.  Everyone will always be exploring the worlds.
So if we go with the theory this is all chunk vistit based, then if the player enters into a chunk the first time, they get the payout listed but not paid again for this chunk.  Every new chunk a player enters, they would get the payout, but not paid again for that chunk.  This would work well for all players if there was an option for saying "All" players.  What we would not want to do is list 10,000 entries for the number of players a server has.  That would be silly and very time consuming.
It would require new parameters in the config to support something like the above where we could select all players, players in a job, players in a certain permission group and then something about the chunks.  What do you think?
`Explore:
AllPlayers:
NewChunk:
income: 2.5
points: 2.5
experience: 2.5
VisitedChunk:
income: 0
points: 0
experience: .01
Group:
Default:
NewChunk:
income: 2.5
points: 2.5
experience: 2.5
VisitedChunk:
income: 0
points: 0
experience: .01
Job:
Miner:
NewChunk:
income: 2.5
points: 2.5
experience: 2.5
VisitedChunk:
income: 0
points: 0
experience: .01'

Hmmm.. This could be solved, but not simple. This VisitedChunk may cause problems, such as server lag, crash, freezing. Because chunk is not good for servers.

agreed, perhaps using coordinates then?  Something like traveling total distance of x and or z from joined world coordinates since we should have where they are when they enter the game.  Then each day (24h) it would reset for the next day.
X-Z:
Use: (values: X, Z or Both)
x: 500
z: 500
So it would be like if I joined today at 9:00AM and travelled 500 blocks North or South, I'd get paid.  If I traveled 500 blocks East or West, I'd get paid.  If I traveled both X & Z distance, I'd get paid.  But that would be it for the day.  Similar to taking a quest. It's a one time payment for that day.

For this feature, the Advanced Achievements plugin is perfect.

Thanks for the referral.  I didn't notice anything about exploring or Jobs support.  Is this a resource you have used or know someone that did what I was looking for?

Yes, that's what you want. Only with a different name. By doing this: "Distance-by-foot" or something similar.


Documentation Work

Documentation work for Matrix Transpose and Matrix Inverse.

Hey @mr-kadyan,
Assigned.
Issue completion deadline - 22nd Oct 8:00:00 am IST
NOTE - In case the issue completion deadline is not met, the issue will be assigned to a new participant


Refactor tests to common parent folder to better code sharing

Fixes #1578
Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

Given the recent commit, I suspect this instance was missed: https://github.com/elyra-ai/elyra/pull/2160/files#r717812729


[Bug]: Paddle Sandbox testing from localhost

What happened?
I am integrating with a sandbox account. I use @paddle/paddle-js from NPM. I initiate Paddle with environment 'sandbox' and a client token generated in the sandbox account. I then initiate the overlay checkout, which triggered the following failing HTTP request:
POST https://checkout-service.paddle.com/transaction-checkout
Which returned with a 403 and the following payload:
{"errors":[{"status":403,"code":"unauthorized","details":"Failed to retrieve JWT"}]}

I am testing from a local IP address (192.168..), I don't use localhost because I also test on other devices that are in the same network. I also noticed a CSP error, but I assumed that would be because my local dev server doesn't have HTTPS, so I created a Firefox profile for testing that disableds CSP.
These are the requests that are made after initiating the checkout:

Steps to reproduce
See above.
What did you expect to happen?
The overlay checkout should open.
How are you integrating?
I use the NPM package @paddle/paddle-js
Logs
No response

Hi @bergwerf,
Thank you for reaching out to us.
Looking at the URL and the screenshot, it appears that you are trying to access production env with the token from sandbox.
Maybe there is some misconfiguration while setting the environment to sandbox.
Can you please share the code you are using to initialize paddle so that we can help your further.
Thank you.

Hi @bergwerf,
Thank you for sharing the snippet.
I tried to run it using the latest version (and some older versions of this package) and I was not able to replicate the issue. The checkout is opening for me.
Can you please share a reproducible example to help debug the problem.
Thank you.

@vijayasingam-paddle Can you share your email address?

@vijayasingam-paddle I created a reproducible example that includes IDs from my Sandbox account. If you send me your email address I can send the example to you.

Hi @bergwerf,
Thank you.
Please send it to<EMAIL_ADDRESS>Ensure that you have removed all tokens and ids.
Thank you,

@vijayasingam-paddle Without token IDs the code is pretty much just the above, so I can share it here as well.
index.html
<!DOCTYPE html>

  <title>Embedded Sketcher</title>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">

Paddle Checkout

  <button id="button">Checkout!</button>

main.ts
// npx esbuild --bundle main.ts > main.js

import { initializePaddle } from '@paddle/paddle-js'

const access_token = 'test_xxx'
const customer_id = 'ctm_xxx'
const price_id = 'pri_xxx'

async function checkout() {
  const paddle = await initializePaddle({
    environment: 'sandbox',
    token: access_token
  })
  if (paddle) {
    paddle.Checkout.open({
      settings: {
        displayMode: 'overlay',
        theme: 'light'
      },
      customer: {
        id: customer_id
      },
      items: [
        {
          quantity: 1,
          priceId: price_id
        }
      ]
    })
  }
}

document.querySelector('#button')!.addEventListener('click', checkout)

To build the TypeScript file, install @paddle/paddle-js, install esbuild, and run npx esbuild --bundle main.ts > main.js. I serve the file from localhost. The same problem appears when I click the button:

I am happy to share my access token and other IDs with the development team, since they are only associated with my sandbox account (so no actually sensitive information is there).

Hi @bergwerf,
This is interesting.
I ran the same code and i was able to launch a checkout 😅
The code I used to test is here
Can you please check this repo to see if there are any differences?
Additionally, please check if this function Paddle.Environment.get() is returning sandbox once paddle is initialized.
Thank you.

The repository worked for me, but I had to set a value for the Default payment link (I am not yet sure what this is used for). However there was an instructive error somewhere that pointed me in this direction. In my other code I made an error somewhere that caused the environment constant I passed to it to be undefined, and thus it ended up in 'production'. By the way Paddle.Environment.get is not in the TypeScript definition.
Anyway, it turns out this was my error and the library works fine. Thanks for the support!

Hi @bergwerf,
I am happy that you were able to make it work.
The function Paddle.Environment.get is not part of the typescript definition nor our documentation because it is an internal function used for debugging and doesn't have any functional usage.
Please feel free to reach out to us if you need any other help.

We have been struggling with the same issue on Vue/Nuxt.

Paddle instance can be initiated (client-side only)
Environment is set to sandbox
The sandbox checkout service issues a 403 "Failed to retrieve JWT"

Reproduced here:
https://github.com/saddam-azad/nuxt-paddle/blob/master/app.vue

Hi @saddam-azad,
Thank you for sharing an example.
I tried to run the code after replacing token and priceId and I was able to launch a checkout without any error.
Please let us know if you are still facing any issues.  Maybe there is some misconfiguration similar to Herman's problem?
Thank you.

Solved the problem. I was using production products and prices wrongly assuming that setting the environment to sandbox allowed testing locally.
Just wanted to document my steps to help future users.

For local testing and staging environments, users have to create another account in https://sandbox-vendors.paddle.com and duplicate the products and prices in the Catalog.

The Default payment link in Checkout > Checkout Settings must be set to your local development environment (e.g. https://localhost:3000/pay)

I wish the documentation around sandbox testing was better.

Solved the problem. I was using production products and prices wrongly assuming that setting the environment to sandbox allowed testing locally.
Just wanted to document my steps to help future users.
1. For local testing and staging environments, users have to create another account in https://sandbox-vendors.paddle.com and duplicate the products and prices in the Catalog.

2. The `Default payment link` in Checkout > Checkout Settings must be set to your local development environment (e.g. `https://localhost:3000/pay`)

I wish the documentation around sandbox testing was better.

Thanks for this. However, the sandbox does not seem to accept localhost or any IP address (i.e. I tried <IP_ADDRESS>). I can always map a local domain in my /etc/hosts but this process needs to be simpler IMO.

Hi @talonx,
I am sorry that you are running into this issue.
Can you please share some details on where you are trying to set the value as localhost or <IP_ADDRESS>?
Is it for the default payment link? If yes, please try http://<IP_ADDRESS> or http://localhost:3000.
Additionally, in sandbox, you can launch checkout from any domain and it doesn't have to exactly match the value provided in the default payment link. So you can configure your staging URL as default payment link and test it on your local machine.
Please let us know if this solves your issue.
Thank you.


Allow compile query

This PR adds the ability to compile query via CLI. It extends compile sub-command. Implementation of #3015.
Currently, it lacks support of (1) keeping context values like counters and states, and (2) styles of target content - result of query which we render.
To resolve (1) I tried to rebuild the Locator from the frames of the first compilation, but results were incorrect. I also tried to keep Locator from the entire build of the document. This attempt was also unsuccessful.
I could solve issue (2) by abusing Tracer, but looking for a cleaner solution.
To see those experiments, look at this branch.
List of unsolved problems:

[ ] Preserve context values
[ ] Keep styles
[ ] Decide which sub-command will implement this functionality - compile vs query

I think the intent of #3015 was something else. Basically just to compile a document and at the same time run a query on the same document, rather than compiling the output of the query, as implemented here. Did you have a specific use case for that in mind?
cc: @ntjess

@laurmaedje I misunderstood that issue, so I've created a new one that describes my use case.

I think there are a lot of challenges to properly support something like this.

Correctly keeping contextual things is not possible at the moment, but might become easier in the future, due to other things I'm working on
Keeping styles is also impossible at the moment
The CLI interface. The --element-number interface feels a bit weird to me.

Can you elaborate more on the use case? I understood that it's for extracting compilations of specific equations or something like that? I can see how that can be useful (as it can work with calculations etc. correctly as opposed to just extracting the equation syntax), but it's also quite specific.


WSL1 Support

Could WSL1 support be continued? And strong recommendations to use WSL2 be furloughed? Filesystem performance and Linux Kernel compatibility aren't as important as being able to run something. I have a cloud VM that doesn't support virtualization.
A pipe dream would be to push WSL1 to zsh and work to remove all GPL licensed software. And maybe some day paragon can remedy the filesystem performance issues.

Feel free to close after reading if this is a duplicate or within scope / the current road map

We have no immediate plans to stop supporting WSL1.


Add Prettier and Eslint Checks as GitHub PR Merge Workflows

Reason/Context
Please try answering few of those questions

Why we need this improvement?
Currently, we do not have prettier under this project. Due to which, the codebase is improperly formatted.

How will this change help?
This change would allow us to manage the lint and format changes during PRs.

What is the motivation?
Most of the open-source projects I have seen or contributed so far uses these plugins and further have a GitHub action to check for such error during the PR workflow.

Description
Please try answering few of those questions

What changes have to be introduced?
The following scripts needs to be included:

    "lint:check": "eslint \"**/*.{ts,tsx}\" --max-warnings=0",
    "lint:fix": "eslint \"**/*.{ts,tsx}\" --fix",
    "format:fix": "prettier --write \"**/*.{ts,tsx,json,scss,css}\"",
    "format:check": "prettier --check \"**/*.{ts,tsx,json,scss,css}\"",

Further, a GitHub action needs to be added to check the PR files, if they fail or pass in the lint and format check.
Continuous-Integration:

    name: Performs linting and formatting
    runs-on: ubuntu-latest
    steps:
      - name: Checkout the Repository
        uses: actions/checkout@v3

      - name: Install Dependencies
        run: npm install

      - name: Run linting check
        run: npm run lint:check

      - name: Check formatting
        run: npm run format:check

Will this be a breaking change?
Yes

How could it be implemented/designed?
This could be implemented by adding the above npm scripts, and .yml files.

The above codes are for representation purpose only. Actual code may vary while implementing.

@derberg @mcturco @akshatnema @magicmatatjahu
Please take a look at this issue. This is a crucial change and would help in automating the lint and formatting of the code base.

@magicmatatjahu If possible I would love to work on this issue .

@anshgoyalevil I have tried to fix the issue here is the PR https://github.com/asyncapi/website/pull/1666
hope this solves the issue feel free to suggest any chages
Thank You

https://github.com/asyncapi/website/pull/1666

#1666

@SumantxD @anshgoyalevil IMHO, I will not prefer to have Prettier configured in the codebase as a part of script. Yes, I agree that we sometimes come across the cases where contributor uses the Prettier or any code formatter to format the code in any style. But I prefers to have no code-formatter configured inside the code and everyone should follow the normal Javascript and Typescript formatter of the VS code.
Regarding the eslint configuration, yeah please add it to the scripts inside package.json but don't configure it as a part of any hook or workflow for the repository. It's nice to be implemented in the way if someone wants to run the eslint at their own wish.
These are just my opinions, no final calls at all. I will recommend to take views from @derberg and @magicmatatjahu also regarding this. And @SumantxD, please make sure that you should first see whether the issue has been acknowledged by one of the maintainers of the repository before creating PR for the issue.

@akshatnema

I will not prefer to have Prettier configured in the codebase as a part of script. Yes, I agree that we sometimes come across the cases where contributor uses the Prettier or any code formatter to format the code in any style. But I prefers to have no code-formatter configured inside the code and everyone should follow the normal Javascript and Typescript formatter of the VS code.

Thanks for the views regarding Prettier Configuration. I too agree with those points. Some open-source projects are using it as a mandate, so I am a bit confused if it is necessary.

Regarding the eslint configuration, yeah please add it to the scripts inside package.json but don't configure it as a part of any hook or workflow for the repository. It's nice to be implemented in the way if someone wants to run the eslint at their own wish.

According to me, the reason for adding eslint to workflow was to enforce the contributor to follow some standard coding rules, which not only maintains the integrity of the project, but also ensures that code is readable.
For example: eslint enforces to validate the prop-types, which is a good thing, and currently in our codebase, none of the props are being validated.
Upon adding eslint to workflow, the developers would have to add such things (like, prop-types in this example) for their PR to be merged, else the workflows would fail.

I made the plugin according to the issue https://github.com/asyncapi/community/issues/238 with the following extensions:

sonarjs
security
react
jest/mocha (depending on which test framework is used in the repo)

If that's appropriate, we can take it as a base and add more extensions according to more specific use case.
Package Link: https://www.npmjs.com/package/@anshgoyalevil/eslint-config

@anshgoyalevil can you please open a new fresh issue for discussion about using https://www.npmjs.com/package/@anshgoyalevil/eslint-config in website? and vscode config to define how it should behave by default for users?

why? what effects can prettier have on eslint?


WIP: RFC: Add upstream version url regexp's to allow upto date checks...

In order to automate the checking of our component versions against their upstream sources,
add 'uscan' formatted URL regexps to items that have a 'version:' key to allow scripts to determine
both our current version, and how to find the latest upstream version.
[This is RFC/WIP - some of the regexp's need work, and there are some features I'd like to add
but I'd like some review and thoughts if this is a sane approach.
And, if anybody fancies helping me out with perl regexp wrangling, such as to skip all 'alpha' etc. releases,
that would be great. yes, I'm looking towards folks like @jodh-intel @marcov @raravena80 ;-) ]
Signed-off-by: Graham Whaley<EMAIL_ADDRESS>

@jodh-intel - I don't see the 'branch out of date' warning? I do see the (shiny new) 'This pull request is still a work in progress' item from github, which is a new feature - you can mark PRs as WIP on github itself when you open them.
But, sure, I'll update branches before dropping the WIPs. I need to go fix and improve some bits before that happens though.

Weird - nor do I now :confused:

Updated, rebased, pushed. Ready for review now. /cc @jodh-intel @chavafg @GabyCT
For reference, here is the current output using the related pending checkversions PR:
 Num:                                     Item          Current Ver         Upstream Ver
PASSES:
   0:    assets.hypervisor.nemu-ovmf.uscan-url                  0.6                  0.6
   1:           externals.kubernetes.uscan-url            1.13.3-00               1.13.3

FAILURES:
   0:  assets.hypervisor.firecracker.uscan-url               0.12.0               0.14.0
   1:         assets.hypervisor.nemu.uscan-url           2018-11-29           2018-12-17
   2:         assets.hypervisor.qemu.uscan-url                 2.11                3.1.0
   3:                  assets.kernel.uscan-url              4.14.67             4.14.101
   4:         externals.gometalinter.uscan-url                2.0.5                3.0.0
   5:            externals.openshift.uscan-url               3.10.0               3.11.0
   6:                 externals.runc.uscan-url            1.0.0-rc5            1.0.0-rc6
   7:               languages.golang.uscan-url               1.10.4               1.11.5
   8:                      specs.oci.uscan-url            1.0.0-rc5                1.0.1

PASSES: 2
FAILS: 9

/test

wow, that broke the CI. I'll check that tomorrow!

Yep - our YAML linter kicked in on this one :)
versions.yaml
  63:81     error    line too long (84 > 80 characters)  (line-length)
  75:81     error    line too long (100 > 80 characters)  (line-length)
  81:81     error    line too long (86 > 80 characters)  (line-length)
  87:81     error    line too long (83 > 80 characters)  (line-length)
  101:81    error    line too long (101 > 80 characters)  (line-length)
  151:81    error    line too long (101 > 80 characters)  (line-length)
  202:81    error    line too long (92 > 80 characters)  (line-length)
  208:81    error    line too long (89 > 80 characters)  (line-length)
  210:81    error    line too long (90 > 80 characters)  (line-length)
  218:81    error    line too long (85 > 80 characters)  (line-length)
  227:81    error    line too long (86 > 80 characters)  (line-length)
  253:81    error    line too long (94 > 80 characters)  (line-length)

doh, do what! I didn't even know we had one ;-)
Hmm, so, if I have an URL that is >80 chars... how do I format that to fix it? Do I have to start injecting \s into the URLs??? bleh....

Yep, we got one :)

https://github.com/kata-containers/tests/blob/master/.ci/static-checks.sh#L323

As to a fix, you might need to specify a custom config for yamllint (which uses YAML format for its config file - cute! ;)

Grumble - OK, I had a look at the yamllint options - I had a stab at enabling 'long lines that cannot be broken', but, my URL/regexps have a ' ' in the middle of them, so that didn't seem to work.
I then reworked them using the yaml > and then >- to wrap the url/regexps over multiple lines, and now the version checker seems not to work, so I have to go debug that (I presume the strings are getting mangled a touch)..... I'll keep beating it with the yaml-stick.

This prolly won't help with the line length issue, but strings in yaml don't need to be quoted so I'd strip off the quotes for all the uscan-url lines.

well, I know what the difference is, now I just have to figure out if I can find a fix. I have some ideas. Fundamentally, splitting the string into an >- extension changes what is extracted!
With the original single line I get:
$ yq r versions.yaml specs.oci.uscan-url
https://github.com/opencontainers/runtime-spec/tags .*/v?(\d\S+)\.tar\.gz

With the multi-line (quoted or not) I get:
$ yq r versions.yaml specs.oci.uscan-url
"https://github.com/opencontainers/runtime-spec/tags .*/v?(\\d\\S+)\\.tar\\.gz"

the difference being the expansion (or is that reduction) of the \\s into \s. Looks like maybe some explicit string quoting that happens for multi lines. maybe I can drop the \\s in that case - let me check..

/test
repushed - let's try again..

/test
Oh YAML YAML - quote of the day for me.... YAML is crazy.
Try again - with some more mangling to wrap some long lines etc.

/test
ooooh, just the one CI fail, but now too old for me to individually retrigger - let's fire them all then...

All green. Merging...


Cra13649/update 4.1.2

Performed the following tasks:
-- fetch tags from upstream and push tags
git checkout main
git remote add upstream https://github.com/martinus/unordered_dense
git fetch --tags upstream
git push --tags
-- branch off of runtimecore and merge tag v4.1.2
git checkout runtimecore
git checkout -b cra13649/update-4.1.2
git push origin cra13649/update-4.1.2
git merge v4.1.2

Is the intent to merge this into the runtimecore branch, or into main first and then cherry-pick over to runtimecore? It looks like in the list of steps you branched off of runtimecore, but the merge target is main

Intent is to merge into runtimecore.  Fixed merge target to merge into that branch.

I think the conanfile_rtc.py also needs to be updated with this new version number


Refactor agent 4 pipeline dbus impl

When the out parameter type is set to "s" (which means a string type value), it should not be a NULL value. This patch fixes such a case in the DBus callback implementation for the pipeline.
Signed-off-by: Wook Song<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. 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://ci.nnstreamer.ai/.


Update outdated test in "Identity provider Google in develop section [UI] "

Describe the Issue:
"Identity provider Google in develop section [UI] " test outdated and should update according to the latest changes
Test description
Scenario:
Identity provider google
Sub scenarios:
Create identity provider Google
List Identity provider
Remove identity provider
Update identity provider google general settings
Update identity provider google Advanced settings
Update identity provider google Attribute settings
Update identity provider google Outbound provisioning settings
Update identity provider google Authentication settings
Update identity provider google Just-in-Time provisioning settings

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Fail the github work flow if the tests couldn't run

Description:
Ran the WebSocket load test and it has failed at the "pre_run.sh" being unable to copy a jar file to the Jmeter/lib/ext folder. After that, the tests haven't run. But the GitHub workflow says it has successfully run.

Currently we simply apply the pod and stream the results from Kubernetes.  Not sure how to get this done but we need to change our approach for this. We'll research on this and get back to you.


Use type annotations in code

Decide on where to use type annotations
and to use which type checke

[x] include type annotations in code
[x] run type checker in travis

Done


Set DRb conn pool to [] after closing connections

After forking and closing open DRb pooled connections set the pool to []
to prevent other calls calling conn.close on already closed
connection.  This prevents the following:
[NoMethodError]: undefined method `close' for nil:NilClass
Did you mean?  clone
/opt/rh/rh-ruby23/root/usr/share/ruby/drb/drb.rb:1258:in `close'
/opt/rh/rh-ruby23/root/usr/share/ruby/drb/drb.rb:1237:in `block in open'
/opt/rh/rh-ruby23/root/usr/share/ruby/sync.rb:234:in `block in sync_synchronize'
/opt/rh/rh-ruby23/root/usr/share/ruby/sync.rb:231:in `handle_interrupt'
/opt/rh/rh-ruby23/root/usr/share/ruby/sync.rb:231:in `sync_synchronize'
/opt/rh/rh-ruby23/root/usr/share/ruby/drb/drb.rb:1235:in `open'
/opt/rh/rh-ruby23/root/usr/share/ruby/drb/drb.rb:1141:in `block in method_missing'
/opt/rh/rh-ruby23/root/usr/share/ruby/drb/drb.rb:1160:in `with_friend'
/opt/rh/rh-ruby23/root/usr/share/ruby/drb/drb.rb:1140:in `method_missing'
lib/gems/pending/VMwareWebService/MiqVimBroker.rb:419:in `getMiqVim'

After a successful call DRbConn.open pops a connection off the pool and closes it, https://github.com/ruby/ruby/blob/v2_3_7/lib/drb/drb.rb#L1237
And #close doesn't check if @protocol is nil before calling @protocol.close, https://github.com/ruby/ruby/blob/v2_3_7/lib/drb/drb.rb#L1258
~~https://bugzilla.redhat.com/show_bug.cgi?id=1562401~~
https://bugzilla.redhat.com/show_bug.cgi?id=1566198

/cc @jrafanie

And #close doesn't check if @protocol is nil before calling @protocol.close

😅 🤦♂

Fine backport details:
$ git log -1
commit edcb7c5d3a0527d59d4b763bd6321a069e1c4360
Author: Joe Rafaniello<EMAIL_ADDRESS>Date:   Mon Apr 9 16:36:15 2018 -0400

    Merge pull request #17267 from agrare/bz_1562401_empty_pool_after_fork

    Set DRb conn pool to [] after closing connections
    (cherry picked from commit 142129eddf87212b71b60222d3dc41b2ed2e6e65)

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1566256

Hello, i have this issue. i added the line to miq_worker.rb. ive to do something additional, because the problem still present when i try to do an smart state analysis.

Hey @dfmanguia what version are you using?

Hello again, im using Version <IP_ADDRESS>.20180501195858_35dc609 note that im using CLOUDFROMS FROM redhat. what do you think about it?

@dfmanguia From a quick glance, that version should have that fix already so you shouldn't have needed to do that.  Are you sure it's that version and the line didn't already exist there?  It's probably a different source of the error.  Can you contact Red Hat support with the logs showing the backtrace for the error?

Well, actually i updated cf and the version is <IP_ADDRESS>, yes the code is by default there.  yesterday i was outdate so thats why the  line wasnt there.  But the problem still there.

@dfmanguia did you stop all processes before updating?  We fork processes so if the parent evm_server process isn't restarted, any new workers that are restarted will not pick up any code changes provided by an update.

@dfmanguia is it the same backtraces or just the same exception?
:+1: to opening a support case and uploading logs.

I got this from logs... What do you think. I restarted the server and nothing

If it is repeatedly happening on vms and not hosts I'd bet it is not the same issue as this.  This was extremely rare and hard to reproduce on a live appliance.

@dfmanguia Yeah, I suggest you open a support ticket and possibly remove the screenshot containing hostnames, etc. I hid the comment but it's still there.  There's no private comment in public github.

is any process to add scvmm as provider to cloudforms, maybe im missing something?, i can see the hosts and the vms, but i want scanstate this vm and got this problem?
ive antoher providers rhev and vmware, everything work except for this provider scvmm

Im working in this, and in the logs appear this.
[----] I, [2018-06-22T09:12:09.842417 #21991:b2b114]  INFO -- : Q-task_id([job_dispatcher]) MIQ(ManageIQ::Providers::Microsoft::InfraManager::Vm.connect_to_ems): Connecting to [host(directly):] for VM:[vmname]
[----] E, [2018-06-22T09:12:09.843098 #21991:b2b114] ERROR -- : Q-task_id([job_dispatcher]) MIQ(ManageIQ::Providers::Microsoft::InfraManager::Vm.connect_to_ems): Connection to [host(directly):] failed for VM:[vmname] with error [no Hostname defined] after [0.000738802] seconds
[----] E, [2018-06-22T09:12:09.845441 #21991:b2b114] ERROR -- : Q-task_id([job_dispatcher]) MIQ(ManageIQ::Providers::Microsoft::InfraManager::Vm#perform_metadata_scan): undefined method close' for nil:NilClass Did you mean?  clone [----] E, [2018-06-22T09:12:09.845925 #21991:b2b114] ERROR -- : Q-task_id([job_dispatcher]) MIQ(MiqServer#scan_metadata) undefined method close' for nil:NilClass
Did you mean?  clone
seem like no Hostname defined] where ive to configure this?

@dfmanguia this PR is not the place to discuss as this is not related to your issue and is cluttering the history, please open a support case with red hat support or at least open a separate GitHub issue for the problem you're having.


Create small dummy server to local tests on client side

To test the connection, response processing and the some minor features, create a dummy server with some static response

Merged into client


[Validation][Requested Changes] Update Warning, Error, Success banner placements and content to consistent

Problem Statement
Currently on the validation results page, our error, warning, and success banners all display inconsistently. Some do not have titles, others are placed below the tables versus above, and elements around each are not consistently positioned above/below the banner.
Resources
Florences mural of research: https://app.mural.co/t/primedatainput6410/m/primedatainput6410/1666190212832/25f971cebb2d289837352dc406cb379ce362068c?sender=ua604735c5cf1162b042a4310
Acceptance Criteria

[ ] All three banners display in the same position: below the file name label and above the tables
[ ] All three banners have a title and description

Column 3 on the mural has a lot of info on this :D


Add a finer-grained view for placer latency metrics

This is a small tweak to the placer latency stats. If we have a cluster of values
around the 1-2s mark, then having a single relatively broad bucket that captures
the (1s, 10s] range will obscure that. In particular, typical Prometheus quartile
estimates may be distorted by this bucket size.
We should probably do something better here - either let the end-user inject their distributions, or perhaps generate a log-linear spread across likely values with far more intervals.

LGTM, but minor concern regarding adding too many buckets.

Agreed; advice from statisticians wrt bucket counts versus from the prom guys is in conflict. All we can tell from quantiles is "the nth percentile lies in this bucket", though. We probably need a better scheme to let us tune these across the board.


Output of "Start with debug" is disabled or not working

I can't see output of console while running through this button, like GD.Print() stuff and etc which outputs to console.
*old way is to run Listen(1) and Run with attach (2) run configurations which allows to run game with debugging without Godot buttons.
Running old way:

Running with new button:

Using Godot 3.2.1 (Mono), Godot Support 2020.1.3, Rider 2020.1 EAP 7 on Arch Linux

Restarted Godot fully, now it's working, it opens another terminal window with output (GD.print and etc from game) of debugger.
#10 Works so far

So is it now intended behaviour that when debugging a new terminal window opens with the game output? This is not very usable as, as soon as the game closes the output is lost.

@hhyyrylainen please add a new issue and mention this one. Thanks!


port of read clipper unit tests

:+1: Merge once tests pass

hmm

Coverage increased (+0.26%) to 70.7% when pulling 75f78bc9e79bd7fb812d54f89a84998d913af787 on ak_readClipperUnitTests into 002aa43baefb0bc4c1bdf6ba9e55ab5b6f0b0b78 on master.


I have added two more news

issue #871
I have added two more news

what is the problem? can you plz tell me I have done the specified task.

update your codebase with current code and please create a new pr because page UI is updated

good work! but make sure to always add a screenshot

sure

update your codebase with current code and please create a new pr because page UI is updated

here is a request . Since I'm a newbie I did not get the above sentence
I mean in what way you want me to update my codebase

update your codebase with current code and please create a new pr because page UI is updated

here is a request . Since I'm a newbie I did not get the above sentence I mean in what way you want me to update my codebase

pull new changes

please fetch and merge the changes and conflicts will be resolved

please update codebase and also add a screenshot


net: tcp: Zero Window Probes are not supported/handled properly

TCP receive window handling implementation was discussed in https://github.com/zephyrproject-rtos/zephyr/issues/3440.
The initial implementation proposed to perform receive window handling on the level of IP stack (i.e. by exposing via native API): https://github.com/zephyrproject-rtos/zephyr/pull/81 . But there was resistance to it, so instead a generic hooks were added on the level on native API (so its behavior didn't change), and the actual receive window handling was implemented on the level of BSD Sockets shim: https://github.com/zephyrproject-rtos/zephyr/pull/1002 .
There were 2 requirements for this initial implementation:

Make sure that receive window handling is performed at all, so non-toy TCP communication can happen.
Disallow bypassing receive window checks as means of a DoS influence (see e.g. https://github.com/zephyrproject-rtos/zephyr/pull/81#discussion_r116311205).

@rlubos: FYI

Disallow bypassing receive window checks as means of a DoS influence (see e.g. #81 (comment)).

So, the intended behavior of achieving this was: if a peer sends us more data than we advertised with our receive window, we just NET_DROP that entire packet. (The idea being: we asked not to send us too much data. If the peer still sends us too much data, that can be only for bad motives, and we'll resist attempts to pull us into packet amplification.)
However, that completely overlooked the concept of Zero Window Probes: if we communicated a window=0 to the peer, and don't communicate anything else for a while, the TCP allows peer to proactively send us "Zero Window Probe", and we expected to reply to it - by sending ACK, where we either confirm that window is still 0, or well, that it's no longer.
"Zero Window Probe" is actually a fully normal TCP packet (segment). Per TCP 793 3.7 page 42:

The sending TCP must be prepared to accept from the user and send at
least one octet of new data even if the send window is zero.

However, in real world, IP stacks add some constraints on ZWPs. For example, Linux appears to send exactly one octet in them.

With this info, we now have a bugreport which shows (by the means of Wireshark capture) that the actual behavior is not as described above: https://github.com/zephyrproject-rtos/zephyr/issues/7818
After receiving ZWP (which is again, just a normal TCP segment, just sent to a peer with window=0), Zephyr instead of silently dropping it, sends an ACK, with an updated ack sequence, which Wireshark notes as "TCP ACKed unseen segment". That apparently quite confuses the peer, that it stops further ZWPs and the TCP communication stalls.
That was speculative part of explaining the behavior based on external symptoms, next step is to confirm this behavior by the code review.

Related RFC: https://tools.ietf.org/html/rfc1122#page-92

After the last comment, I switched to the practical part of trying to reproduce Zero Window Probes issues, logged here: https://github.com/zephyrproject-rtos/zephyr/issues/7818#issuecomment-391767369

Cross-posting from https://github.com/zephyrproject-rtos/zephyr/issues/7818#issuecomment-391891083 :
As a final test, I'm applying following test changes:
--- a/samples/net/sockets/big_http_download/src/big_http_download.c
+++ b/samples/net/sockets/big_http_download/src/big_http_download.c
@@ -29,7 +29,7 @@

 /* This URL is parsed in-place, so buffer must be non-const. */
 static char download_url[] =
-    "http://archive.ubuntu.com/ubuntu/dists/xenial/main/installer-amd64/current/images/hd-media/vmlinuz";
+    "http://microsoft.com/";
 /* Quick testing. */
 /*    "http://google.com/foo";*/

diff --git a/subsys/net/ip/tcp.c b/subsys/net/ip/tcp.c
index fec12c550..c39205875 100644
--- a/subsys/net/ip/tcp.c
+++ b/subsys/net/ip/tcp.c
@@ -274,7 +274,7 @@ struct net_tcp *net_tcp_alloc(struct net_context *context)
 	tcp_context[i].context = context;

 	tcp_context[i].send_seq = tcp_init_isn();
-	tcp_context[i].recv_wnd = min(NET_TCP_MAX_WIN, NET_TCP_BUF_MAX_LEN);
+	tcp_context[i].recv_wnd = 40; //min(NET_TCP_MAX_WIN, NET_TCP_BUF_MAX_LEN);
 	tcp_context[i].send_mss = NET_TCP_DEFAULT_MSS;

 	tcp_context[i].accept_cb = NULL;
diff --git a/subsys/net/lib/sockets/sockets.c b/subsys/net/lib/sockets/sockets.c
index 5bcd771f5..5f672245e 100644
--- a/subsys/net/lib/sockets/sockets.c
+++ b/subsys/net/lib/sockets/sockets.c
@@ -443,7 +443,7 @@ static inline ssize_t zsock_recv_stream(struct net_context *ctx,
 	} while (recv_len == 0);

 	if (!(flags & ZSOCK_MSG_PEEK)) {
-		net_context_update_recv_wnd(ctx, recv_len);
+//		net_context_update_recv_wnd(ctx, recv_len);
 	}

 	return recv_len;

With it, I get the following console output:
***** Booting Zephyr OS v1.11.0-1619-g5b20350a7 *****
[net/app] [INF] net_app_init: Initializing network
[net/app] [INF] setup_dhcpv4: Running dhcpv4 client...
Preparing HTTP GET request for http://microsoft.com:80/
addrinfo @0x401040: ai_family=2, ai_socktype=1, ai_protocol=6, sa_family=2, sin_port=5000
sock = 4199520
[net/tcp] [ERR] _tcp_established: Context 0x00401460: overflow of recv window (0 vs 1), pkt dropped
[net/tcp] [ERR] _tcp_established: Context 0x00401460: overflow of recv window (0 vs 1), pkt dropped

in full accordance with the analysis described in https://github.com/zephyrproject-rtos/zephyr/issues/7876.
So, that's the only stable and reproducible issue on our side that I see, and which needs to be fixed. (The next issue on our side is "TCP handling is poor", but unfortunately one can't submit a few lines patch and have that fixed).

Yes, I think we can close this one.


find_package macro breaks CMake policy propagation

Describe the bug
The vcpkg.cmake toolchain file defines a  find_package macro in order to inject extra behaviours.
This macro changes the active CMake policies as seen by called Find modules and Config files
...from the state of policies when find_package is called (late, project configuration)
...to the state of policies which was active when the macro is defined (early, toolchain initialization).
This change can break configuration in particular for projects which apply a low minimum CMake version.
The key difficulty is the fact that the interaction is not obvious. It may be a rare case, but this makes it even more puzzling when it happens.
Exampe
From #28929:

Install gdal with libkml support.
Build libosmium. Simplified:

CMakeLists.txt:  cmake_minimum_required(VERSION 2.8.12) # :classical_building:
CMakeLists.txt:  project(libosmium)

vcpkg.cmake: macro(find_package) # CMP0057 OLD :bomb:

CMakeLists.txt: find_package(GDAL REQUIRED)

gdal/vcpkg-cmake-wrapper.cmake: cmake_policy(SET CMP0057 NEW) # :fire_engine:
gdal/vcpkg-cmake-wrapper.cmake: find_dependency(LibKML) # CMP0057 NEW :innocent:

vcpkg.cmake: _find_package(LibKML) # in macro, CMP0057 OLD :zap:

gdal/FindLibKML.cmake: if(comp IN_LIST LibKML_FIND_COMPONENTS) # :boom:

CMake Error at /mnt/vcpkg-ci/installed/x64-linux/share/gdal/packages/FindLibKML.cmake:61 (if):
  if given arguments:

    "DOM" "IN_LIST" "LibKML_FIND_COMPONENTS"

  Unknown arguments specified

Alternative solutions for the given example

global: Fix vcpkg.cmake
I don't know if this can be done for the macro.

gdal: Fix the FindModule.cmake
Adding cmake_policy(SET CMP0057 NEW) to FindLibKML.cmake` will fix the problem for all users.
It may be possible to upstream the change. But the problem is specific to vcpkg's macro in combination with particular downstreams, so upstream might be unwilling to accept a patch.

libosmium: Bump cmake_minimum_required
Using cmake_minimum_required(VERSION 2.8.12...3.25) will enable new policies as possible since CMake 3.12 and is compatible with CMake older than 3.12, so it may be possible to upstream the change. However, new policies may come with extra side effects, positive and negative, so it is not without risk.
The fix has to be applied to every affected port.

libosmium: Configure with -DCMAKE_POLICY_DEFAULT_CMP0057=NEW
No patching, just portfile changes.
The fix has to be applied to every affected port.

(In this particular example, no. 2 is a good choice because we need to carry a patch for this module anyways.)

just push the policy stack run vcpkg.cmake with highest policy possible, pop the policy stack?

cc @BillyONeal

Still valid.

@BillyONeal Any news?

Not stale.

Not stale.


MGMT-16272: Allow the controller to delete NodeModulesConfigs

Make the OwnerReferencesPermissionEnforcement admission plugin happy.
/cc @yevgeny-shnaidman

/lgtm

/cherry-pick release-2.0


Embedding Layer's mask operation with LSTM Layer Gives Wrong Results When Using a GPU

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 18.04.3
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: No
TensorFlow installed from (source or binary): source
TensorFlow version (use command below): 2.0 GPU version
Python version: 3.x
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with: 1. TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)" 2. TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"
Describe the current behavior
When using a GPU, the mask operation of the embedding layer (with LSTM layer) gives wrong result. With mask_zero = True, anytime there is an input of 0 in one of the time steps, the output should be same as the previous time step's output. Which is what it does with a CPU. However, using a GPU, it just gives a zero output (which is not the expected behavior).
Describe the expected behavior
With mask_zero = True, anytime there is an input of 0 in one of the time steps, the output should be same as the previous time step's output.
Code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate the problem.
########################################
import tensorflow as tf
tf.random.set_seed(0)
inputs = tf.keras.layers.Input(shape=(None,), dtype='int32')
x = tf.keras.layers.Embedding(input_dim=10, output_dim=3, mask_zero=True)(inputs)
outputs = tf.keras.layers.LSTM(2, return_sequences=True)(x)
model = tf.keras.Model(inputs, outputs)
padded_inputs = tf.constant([[1,3,0,0]])
print(model(padded_inputs))
It prints the following:
tf.Tensor(
[[[0.00727878 0.00290126]
[0.00217528 0.00565582]
[0.         0.        ]
[0.         0.        ]]]
instead of
tf.Tensor(
[[[0.00727878 0.00290126]
[0.00217528 0.00565582]
[0.00217528 0.00565582]
[0.00217528 0.00565582]]] (which is what it is supposed to print).
Note that when only using a CPU, it gives the correct result.
########################################
Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

Issue is replicating with Tf 2.0.0-gpu on colab. Please take a look at the gist. Thanks!

Just wanted to check if and when will this be resolved in the future? Thanks alot for listening!

Sorry for the late reply, this might take some time on my end.
Also I think even the numerical result is different here, those different value actually belong to masked timesteps which will be auto ignored by keras. Are you somehow using those values?

@gtg162y,
This issue is fixed in Tf==2.1.
Please  find the gist here .
Please close the issue if it was already resolved for you. Thanks!

I think this issue is not fixed yet, the gist was run on a CPU env, which doesn't reproduce the issue.

Was able to reproduce the issue with Tf 2.1 GPU.
Please find the gist here. Thanks!

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?

I am able to reproduce the issue with [Tf nightly] (2.4.0-dev20200809)(https://colab.research.google.com/gist/Saduf2019/c466f8f21b07450a8438d89e352cc248/untitled346.ipynb) GPU.
Please find the gist here. Thanks!

@amitp-ai
This issue has been fixed in tf-nightly and tf 2.5, please refer tot he gist here, can you please upgrade your tf and move this issue to closed status.


Make .encode(ENCODING) more robust

Using python 3.7.9 and import html and from puz import (Puzzle, DefaultClueNumbering, BLACKSQUARE)
I'm converting files from the web into PUZ format with puzpy. The files contain html entities which I'm unescaping with html.escape.
So, for example:
— --> \u2014
’ --> \u2019

This causes:
UnicodeEncodeError: 'latin-1' codec can't encode character '\u2014' in position 28: ordinal not in range(256)
In puz.py, replacing every instance of
.encode(ENCODING)
with
.encode(ENCODING, 'replace')
solves the problem.

Thanks for the report! Do you have a sample file you could link or attach that reproduces the issue?
thanks!

Thanks for the report! Do you have a sample file you could link or attach that reproduces the issue?
thanks!

This is fixed in master now: you can override the encoding policy for the module like so:
import puz
puz.ENCODING_ERRORS = 'replace'
...


reentrant prepare for closing

Make prepare_for_closing reentrant by making it return an Option<EnvClosingEvent> rather than panicking when called multiple times.

The panic in this function can never be triggered in normal usage, it is not possible to call prepare_for_closing on a dropped environment as it is the latest environment dropped that will remove the entry from the HashMap and therefore no other environment can be used to call prepare_for_closing on it again.


Fix infinite loop for deeply nested pytrees

I have a rather big dataclass to describe a robot model, that includes a graph of links and a list of joints. Each node of the graph references the parent link and all the child links. Each joint object references its parent and child links.
When I try to copy_and_mutate any of these objects, maybe due to all this nesting, an infinite loop occurs. I suspect that the existing logic tries to unfreeze all the leafs of the pytree, but the high interconnection and the properties of mutable Python types lead to a never ending unfreezing process.
This PR addresses this edge case by storing the list of IDs of objects already unfreezed. It solves my problem, and it should not add any noticeable performance degradation.
cc @brentyi

Makes sense, thanks!
Happy to merge this, I just want to make sure I fully understand the exact underlying issue first. A concise example would be helpful if you have the time, if not I'm happy to look into this myself. (would also help with unit testing etc)
Cycle detection indeed sounds useful but it's unclear to me whether this should be handled gracefully (as the PR currently does) or if an error should be thrown. From the JAX documentation:

Pytrees are tree-like, rather than DAG-like or graph-like, in that we handle them assuming referential transparency and that they can’t contain reference cycles.

Makes sense, thanks!
Happy to merge this, I just want to make sure I fully understand the exact underlying issue first. A concise example would be helpful if you have the time, if not I'm happy to look into this myself. (would also help with unit testing etc)
Cycle detection indeed sounds useful but it's unclear to me whether this should be handled gracefully (as the PR currently does) or if an error should be thrown. From the JAX documentation:

Pytrees are tree-like, rather than DAG-like or graph-like, in that we handle them assuming referential transparency and that they can’t contain reference cycles.

I had a deeper check on my code, and I think I found a possible culprit in a relatively simpler case that does not involve any closed-loop kinematics.
It is related to what I wrote in the beginning about the links that form the nodes of a kinematic graph: each link has a reference to its parent and also contains a list of its children.
In other words:
@pytree_dataclass
class Link:
    parent: "Link"
    children: List["Link"]

When the dataclass is accessed recursively with the existing logic, an infinite loop occurs with the following order:

starting from an object of the Link class
its parent is unfrozen
first element of children is unfrozen

the parent of the first child is unfrozen, but it is the same object of 1), therefore this process loops forever

So yes, although the structure seems a tree, this backward reference with parent makes it no longer acyclic.

Thanks! Yeah, if the parent points to the child and the child points to the parent that sounds like a cycle.
Is the parent pointer strictly necessary? Perhaps you could track this relationship externally, eg maintain something like parent_link_from_child_link: Dict[Link, Link] = {shoulder: base, elbow: shoulder, wrist: elbow}, etc.
I have some ideas for other solutions but none of them seem particularly appealing. With a proper immutable object it should be impossible to have link.child.parent point back to the original link, since either the link object or the child object needs to be created first and the first one that's created can't point to the one that doesn't exist yet. (apologies for the word salad)
To work around that, my guess is you're doing something that looks like this?
from __future__ import annotations

from typing import List, Optional

import jax_dataclasses as jdc

@jdc.pytree_dataclass
class Link:
    parent: Optional[Link]
    children: List[Link]

shoulder_link = Link(parent=None, children=[])
base_link = Link(
    parent=None,
    children=[
        shoulder_link,
    ],
)

with jdc.copy_and_mutate(base_link, validate=False) as base_link:
    # Try to update the parent pointers. This creates a cycle and will fail.
    base_link.children[0].parent = base_link

Thanks! Yeah, if the parent points to the child and the child points to the parent that sounds like a cycle.
Is the parent pointer strictly necessary? Perhaps you could track this relationship externally, eg maintain something like parent_link_from_child_link: Dict[Link, Link] = {shoulder: base, elbow: shoulder, wrist: elbow}, etc.

Thanks for the feedback! I checked the entire codebase (it's a medium-sized project that I'll release soon, it's not yet open), and I use the parent link information in multiple places. As often happens in software, the problem is not absolute, and workarounds like what you proposed can be implemented.

To work around that, my guess is you're doing something that looks like this?
[...]

Yes, this is a possible MWE of the problem that is fixed by this PR.
So far I vendored jax_dataclasses to speed up prototyping, but now I wanted to push the fix upstream. At this point, let me know if you think this patch could be a value added (regardless to my specific problem). If not, I'll either try to remove the parent attribute, or keep temporarily the vendored fork for another while.

For the record, the infinite loop occurring in my application was caused by a static dataclass, therefore the recently added https://github.com/brentyi/jax_dataclasses/commit/b81803ab3cb03f6424b936cc6aaca7cc52d3a18d in main solves my specific problem. In any case, I still think that the logic of this PR could be useful in edge cases like those described here above when the object with cycles is a (non-static) pytree.

Really helpful to know, thanks @diegoferigo!
And apologies for dragging my feet a bit with this PR; has been a bit of a mess of a week. :smiling_face_with_tear:
I've been running some experiments with inserting cycles into pytrees and it doesn't seem like a good idea. For example, on my machine this gives me a segfault:
import jax
from jax import numpy as jnp

x = [jnp.zeros(3), jnp.ones(3)]

# OK.
print(jax.tree_map(lambda array: array * 2, x))

# Create a cycle. Segfault!
x.append(x)
print(jax.tree_map(lambda array: array * 2, x))

So I'm thinking eventually we should actually throw an error if a cycle is detected. Gave this some thought and doing it efficiently while considering all the edge cases is actually nontrivial, so will save for the future. In the meantime just avoiding the infinite loop is helpful; thanks again for the PR!

Really helpful to know, thanks @diegoferigo!
And apologies for dragging my feet a bit with this PR; has been a bit of a mess of a week. smiling_face_with_tear

Thank you @brentyi! And thanks for creating this package, I love dataclasses and being able to use them also in JAX has been very helpful. Particularly, the validation of the treedef with the context manager helped me preventing many subtle bugs that would have been painful to find.

I've been running some experiments with inserting cycles into pytrees and it doesn't seem like a good idea. For example, on my machine this gives me a segfault:
[...]
So I'm thinking eventually we should actually throw an error if a cycle is detected. Gave this some thought and doing it efficiently while considering all the edge cases is actually nontrivial, so will save for the future. In the meantime just avoiding the infinite loop is helpful; thanks again for the PR!

Yeah, the error occurs in the JAX side because this limitation is over there. At least now the error does not affect jax_dataclasses, that should not really mind about cycles. Less maintenance burden ;)
I still have to try the last tweaks you added in this PR, but as I already wrote, in my case the problem was originated by a static field.

Super glad it's been useful; I definitely also prefer the context manager over the standard .replace() syntax. Especially for compatibility with type checkers, autocomplete, etc. :slightly_smiling_face:


FSM for panel update logic

This is correctly working in v0.0.5.
I could have broken this during refactor by not translating the code over correctly.
I consider this completed, and will spin up new bugs.


Cannot find find_url function in GrafanaApi class in api.py module

Describe the bug
A clear and concise description of what the bug is.
I see this
AttributeError: type object 'GrafanaApi' has no attribute 'from_url'
To Reproduce
Steps to reproduce the behavior:

Install latest grafana-client using pip install grafana-client==2.3.0

Run with valid key

from grafana_client import GrafanaApi

# Use Grafana API token.
grafana = GrafanaApi.from_url(
    url="https://grafana.example.org/grafana",
    auth="eyJrIjoiWHg...dGJpZCI6MX0=",
)

Expected behavior
I see the method in the repo code but not in my site packages when I do pip install.
Expecting this to run error free.
Versions

Grafana: [ 8.5.2]
grafana-client: [ 2.3.0]
Authentication:  [Token]

Additional context
Add any other context about the problem here.

My bad. On checking further, it seems that the from_url is to be released in 2.4.0.
I will close this and follow instructions here https://pypi.org/project/grafana-client/

Dear Achin,
you are right, grafana-client==2.4.0 is around the corner. In the meanwhile, you can install the development version of the package into your sandbox by using pip install --upgrade git+https://github.com/panodata/grafana-client.
With kind regards,
Andreas.

Dear Achin,
grafana-client==3.0.0 has been released. With this release, you will be able to use the new factory methods GrafanaApi.from_url() and GrafanaApi.from_env().
With kind regards,
Andreas.


Add scraper for Virginia County Level Hospitalizations & Death Data

Original issue https://github.com/covidatlas/coronadatascraper/issues/884, transferred here on Thursday Apr 23, 2020 at 02:02 GMT

Location name
All County/City, Virginia, USA
Source URL
http://www.vdh.virginia.gov/content/uploads/sites/182/2020/03/VDH-COVID-19-PublicUseDataset-Cases.csv
Notes/comments
Released each morning by 10:00 am eastern

(Transferred comment)
From Virginia Department of Health:
UPDATE: 4/23/20 - In addition to today's counts, this data set now includes historical data of cumulative counts by date
VDH COVID-19-PublicUseDataset-Cases


fix: avoids getting and setting doc preferences when creating new

Description
Fixes #5739 #5747
fix: only call getPreferences & setPreferences if preferencesKey exists

[x] I have read and understand the CONTRIBUTING.md document in this repository.

Type of change

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

Checklist:

[x] Existing test suite passes locally with my changes

Both issues fixed 🎉  thank you 🙏


duplicate tests

Seems like we have 3 tests that do the same things but differ only on trigger

Daily runs tests once daily
nodejs runs tests on pull requests and commits to master
on demand runs tests ... well, ... on demand

There are slight differences, like do we update codecov? do we notify slack? what node versions do we cover 14.x or 14?
I think these should all be the same workflow file with a collection of triggers ... like we have in app-smoke-test.yml

I think we can consolidate these and maintain the Slack notification and Codecov upload behaviors by inspecting the event_name (i.e. push, pull_request, schedule) when deciding to run those steps.
PR: https://github.com/adobe/aio-e2e-tests/pull/75


7.2.0-preview9: & arguments no longer remove quotes

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
Have a program that just prints out it's args:
using System;
using System.Linq;

namespace ConsoleApp29
{
    internal class Program
    {
        static void Main(string[] args)
        {
            Console.WriteLine("Arguments:");
            args.ToList().ForEach(arg => Console.WriteLine(arg));
        }
    }
}

Invoke the program with & and pass some params.
Expected behavior
& ".\ConsoleApp29.exe" @("a", '"a"')

Arguments:
a
a

Actual behavior
& ".\ConsoleApp29.exe" @("a", '"a"')

Arguments:
a
"a"

Error details
The "" are no longer stripped from the argument in 7.2.0-preview9, while in 7.1.3 they are stripped.

Environment data
$psversiontable

Name                           Value
----                           -----
PSVersion                      7.2.0-preview.9
PSEdition                      Core
GitCommitId                    7.2.0-preview.9
OS                             Microsoft Windows 10.0.19043
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
No response

We also see this in our repository, when executing this line:
https://github.com/microsoft/testfx/blob/a5fc7c9c91d5de10fe3824d86872d31f847a682d/scripts/Build.ps1#L225

This is due to the experimental feature PSNativeCommandArgumentParsing.  As a workaround, you can disable the feature or control it with this variable:
$oldMode = $PSNativeCommandArgumentPassing
try {
    $PSNativeCommandArgumentPassing = 'Legacy'
    InvokeExeHere
} finally {
    $PSNativeCommandArgumentPassing = $oldMode
}

Thanks Patrick.
Or probably just rely on variable scoping to reset it for us:
& {
    $PSNativeCommandArgumentPassing = 'Legacy'
    InvokeExeHere
}

Thanks @nohwnd, @SeeminglyScience.

Just as an FYI this should be the desired behaviour as it is escaping the values correctly. It will allow you to do my.exe '{"foo": "bar"}' without you having to manually escape the double quotes yourself.


RPM Repo(Chapter 6): Permission denied

Fail when import Remi GPG key. Because You forgot add : "become: true". I just made a PR.

If this is  a Linux  machine try chmod +x "file name "

If you're encountering a "Permission denied" error in an RPM repository (Chapter 6), follow these steps:

Check user permissions, use a user with elevated privileges.
Verify and adjust file/directory permissions using chmod.
Ensure correct ownership using chown.
Check SELinux or AppArmor logs and configurations.
Confirm sufficient disk space.
Double-check command accuracy.
Review repository configuration.
Examine system logs for error messages.
Confirm firewall/security group settings.
Temporarily use elevated privileges as a workaround.

Thank you, I really appreciate it.


where is the key?

I am only a layman. i don,t know where the key is,
from the following parts. if the key is there？
$ cat /home/blc/liufeia/key
Warning: pasting the following URL into your browser exposes the OTP secret to Google:
https://www.google.com/chart?chs=200x200&chld=M|0&cht=qr&chl=otpa
Your new secret key is: 7QOJCMH2YGT
Your verification code for code 1 is 0942
Your emergency scratch codes are:
38106
appreciate

This 11 character string looks like an incomplete base32 string. 11 base32 characters is the encoding of 55 bits, and most base32 decodes would ignore the 11th character and decode this as 6 bytes. It doesn't look like a complete base64 string, because mime decoders would treat that 11th character "T" the same as they would Q or R or S.


bump/1.160.0

Release v1.160.0 of AWS Solutions Constructs

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: de100a7c7bde9e665f5e62f92a77199dc4d688e3
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: de100a7c7bde9e665f5e62f92a77199dc4d688e3
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Fixing capitalization

I suspect QueryEnum on the simple-options docs should be QueryMsg, here's a quick docs pull for it.

Applied changes in another comment. Thanks!


error in useing different video name

when i use your video demo , it works well
but if i use different video name ,(i also remember to change the .josn file name) , it gives me this error.
(car_video is the video name).
if i rename my video to cam_04 it works .
Fusing layers...  Model Summary: 213 layers, 7020913 parameters, 0 gradients Adding AutoShape...  Traceback (most recent call last):   File "run.py", line 48, in <module>     main(args, config)   File "run.py", line 30, in main     pipeline.run()   File "/content/main/modules/__init__.py", line 34, in run     self.cam_config.cam[cam_name], KeyError: 'car_video'

You need to modify the video name in cam_configs.yaml as well

Thank you , it's work .


Unstable connection leads to lost some locations that are not sent to the Archipelago Server

I am now using the new version of the lib.
I can close this issue


Enable-PnPResponsiveUI error

Hi,
I have error when i use Enable-PnPResponsiveUI in SP16
Enable-PnPResponsiveUI : La méthode « GetFileByServerRelativePath » n’existe pas.
At line:1 char:1

Enable-PnPResponsiveUI

  + CategoryInfo          : WriteError: (:) [Enable-PnPResponsiveUI], ServerException
  + FullyQualifiedErrorId : EXCEPTION,SharePointPnP.PowerShell.Commands.Branding.EnableResponsiveUI

any help plz

Hi @maouinati,
I have to ask you some questions to be sure to understand :

From which repo/solution did you deploy the Responsive Solution (PnP-Tools or PnP-Sites-Core) ?
Because you have a SP2016 version, did you download the good PowerShell in accordance with your version ? (you have 3 PowerShell package)

Note : in accordance with your issue,some dependancies seem to be missing or thePowerShell solution is not the good one.

Hi @Laul0
1.I deploy from repo "PnP-Tools-master\Solutions\SharePoint.UI.Responsive".
2. for the powershell, I chose the good one.
thank you for your help

Hi @maouinati,
I just tried with the latest version of cmdlet PowerShell and I can't reproduce your issue.
Your issue still true ? Did you try the latest version of PowerShell cmdlet ?


RuntimeError: Unconvertible NCCL type

Hello Colleagues,
I just try to use FEDformer to run some LSTP tasks, and I directly use your default configurations in the run.py.
--------------------First Question (Multi-GPU usage)------------------------
But the RuntimeError shows Unconvertible NCCL type when the model uses the nn.DataParallel to parallelize. Have you ever encountered such issues when conducting experiments before? Thanks for your possible suggestions and help.
By the way, I use the Pytorch Version 1.5 and previously have used the Autoformer to conduct the same tasks but didn't receive similar errors from Pytorch. The difference between those is using the Frontier Transform (parser's default is to use Frontier) to decompose the time series.
In your codes implementing the Frontier module in the layers/FrontierCorrelation.py, the param modes seems to control the Frontier based configs, I don't know whether some ops between the modes and the length of the sequence denoted as seq_len will affect the training. However, I have modified the value of modes to less than seq_len to satisfy the index = index[:modes] line in your codes, but the errors still exist.
--------------------Second Question (Complex Multiplication)--------------------
I try to directly update the Pytorch to v1.9 and now I can use multiple GPUs to train. So the first question may be solved by updating due to incompatibility. However, I find another problem occurs in the complex multiplication op (see the attached figure) and the errors show einsum() the number of subscripts in the equation (3) does not match the number of dimensions (4) for operand 1 and no ellipsis was given (see the attached figure). It's noted that this time I entirely use your raw codes and the problems also exist, so maybe some issues indeed need to be solved.
You can directly email<EMAIL_ADDRESS>and look forward to your reply!
In your paper, you said this model could outperform Autoformer and Transformer-based variants by almost 20%, so I would like to kindly ask about some issues and hope I can use this in my research later on.
Best
Attached figures:

shows the Pytorch backend uses the nn.DataParallel to run on multiple GPUs.

if the comm.py means communications among processes, there may be some errors in this part. But the Autoformer doesn't have this issue, so maybe it's because of the Frontier part? But this may be also a compatibility issue, so if you think it's worth discussing we can solve this issue by discussing in the email since you also just open-sourced the codes days before. It can benefit the entire community maybe.

complex multiplication issue

try to upgrade to PyTorch 1.9.0 at least, I am not sure about this NCCL type error.....

Do you know the second question: the einsum issue? I think this is not the NCCL type error. After upgrading to 1.8, the NCCL type issue has been solved.

check my reply， i said upgrade to torch 1.9.0 at least not 1.8………
发自我的iPhone

在 2022年7月10日，03:07，Taochun Sun @.***> 写道：

Do you know the second question: the einsum issue? I think this is not the NCCL type error. After upgrading to 1.8, the NCCL type issue has been solved.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.

Do you know the second question: the einsum issue? I think this is not the NCCL type error. After upgrading to 1.8, the NCCL type issue has been solved.

hi~你解决了einsum这个问题了吗？ 我用的源码出现了一模一样的错误RuntimeError: einsum(): the number of subscripts in the equation (3) does not match the number of dimensions (4) for operand 1 and no ellipsis was given。太困惑了，能跟你讨论一下吗？求赐教

Do you know the second question: the einsum issue? I think this is not the NCCL type error. After upgrading to 1.8, the NCCL type issue has been solved.

hi~你解决了einsum这个问题了吗？ 我用的源码出现了一模一样的错误RuntimeError: einsum(): the number of subscripts in the equation (3) does not match the number of dimensions (4) for operand 1 and no ellipsis was given。太困惑了，能跟你讨论一下吗？求赐教

check my reply， i said upgrade to torch 1.9.0 at least not 1.8……… 发自我的iPhone
…
在 2022年7月10日，03:07，Taochun Sun @.***> 写道：  Do you know the second question: the einsum issue? I think this is not the NCCL type error. After upgrading to 1.8, the NCCL type issue has been solved. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you modified the open/close state.

Hello Colleagues, my torch version is 1.9.0, but this error will be reported when using multi gpu, as shown in the attached picture. I would like to ask the author if you have tried to run multiple Gpus, or do you have any suggestions to solve it? thank you for your kind reply.

Hello Colleagues, my torch version is 1.9.0, but this error will be reported when using multi gpu, as shown in the attached picture. I would like to ask the author if you have tried to run multiple Gpus, or do you have any suggestions to solve it? thank you for your kind reply.

You don't need to run a multi-GPU setting here. we never use that in all of
our experiments, the speed is reasonably fast. I would rewrite the project
using Pytorch lightning if I want to use multiple GPUs in the future. A lot
of things could go wrong with a hand-implemented one.
On Wed, Nov 30, 2022 at 3:55 PM Hsuxiang @.***> wrote:

[image: image]
https://user-images.githubusercontent.com/77951517/204738710-28e0301f-6334-49d5-bbde-8ddeb499b3f9.png
Hello Colleagues, my torch version is 1.9.0, but this error will be
reported when using multi gpu, as shown in the attached picture. I would
like to ask the author if you have tried to run multiple Gpus, or do you
have any suggestions to solve it? thank you for your kind reply.
—
Reply to this email directly, view it on GitHub
https://github.com/MAZiqing/FEDformer/issues/10#issuecomment-1331766154,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB3JGO6W5JA2F2TYB6WPTPLWK4B5PANCNFSM52JCUYTQ
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


fix: usage of events with type never

Found an error and created an issue. This fixes #101 :)

Published as<EMAIL_ADDRESS>Thanks a lot @cstrnt!


clear error messages and secure warnings

Recommendation to improve SSL error comprehension.  Comment recommends seeing https://adrifelt.github.io/sslinterstitial-chi.pdf.  Consider adding a management function that users can't click through errors to MOF.

Added to MOF:
22. Enable/disable user's ability to acknowledge/accept risks associated with security warnings


[Website] The Layer5 Cloud extension should have a "5" mark, not Meshery logo

Current State of the Meshery.io site
On the extensions page, the Layer5 Cloud extension should have a "5" logo, not Meshery logo

Desired State of the Meshery.io site
The "5" mark can be found at https://layer5.io/company/brand.

Contributor Guides and Handbook
The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

📚 See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

hi. would like to take a look at this if possible.

@leecalcote would like to work on it

@dsawwork, 🎉 Thanks for stepping up!
@rahulrana701 Thanks for asking... we assign tasks chronologically to ensure fairness. Don't worry, more opportunities are on the way! 👍😊

Hi @Ashparshp. when setting up the server for meshery on windows (git bash) I get compilation errors. I think I have the prerequisites but there might be a mismatch in the gcc versions. Any idea on how to go about it?


IA-1552: account id in urls

The idea is to add account_id param everywhere in the dashboard in order to debug, share easily links
Self proof reading checklist

[ ] Did I use eslint and black formatters
[ ] Is my code clear enough and well documented
[ ] Are my typescript files well typed
[ ] Did I add translations
[ ] My migrations file are included
[ ] Are there enough tests

Changes

refactor o protectedRoute, main index and App
adding accountId in routes, plugin routes, sidebar menu, redirections
fix tests for new urls

How to test
Unfortunately you have to pass a bit everywhere.
Notes
This is working also for anonymous plugins page like embedded calendar

@cypress

@cypress

@cypress

${siteBaseUrl}/dashboard/orgunits/detail/orgUnitId/${orgUnit.id}/tab/history/accountId/1
Wouldn't it be more stable and future proof to have the accountId at the start ? Like this ?
${siteBaseUrl}/dashboard/accountId/1/orgunits/detail/orgUnitId/${orgUnit.id}/tab/history
would seems less prone to future conflict for me and less chance to mix it with deep linking.
Also wonder if it would be nice to have the account name instead
${siteBaseUrl}/dashboard/account/pbf_rca/orgunits/detail/orgUnitId/${orgUnit.id}/tab/history

Also concerning putting it in front, I'm not certain but from my understanding of ReactRouter, if you  put it in front you could just wrap all the current in a parent  component.
I'm seeing they are doing it like this for nesting in their documentation.
<Router>
    <Route path="/" component={App}>
      <Route path="about" component={About} />
      <Route path="inbox" component={Inbox}>
        <Route path="messages/:id" component={Message} />
      </Route>
    </Route>
  </Router>

https://github.com/remix-run/react-router/blob/v3.2.6/docs/guides/RouteConfiguration.md

According to our discussion, accound id should be present at the beginning of the url.
We have to update tests and fix @quang-le issues

I added retries to the cypress tests. the tests will take even more time this way, but it will prevent some flaky tests from failing so it should be an overall win


omitNeedlessWords: Fix self-type-stripping regression

Fix-up for #27602. Turns out self-type-stripping always operates on a type without prefixes rather than never. Neither of these behaviors are really what we'd want (see the inconsistent test cases), but we'll live with it! The new hack is simpler than the old hack, at least.
rdar://problem/56334797

@swift-ci Please smoke test

@swift-ci Please test source compatibility


Updated broken promise

It's already past his first day as President, and he still has not done this.

👍


⚠ Samsung has degraded performance

In fd234f1, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2187 ms

Resolved: Samsung performance has improved in 84a8ea8.


changes in redme.md

-> add some line

I the readme is good enough and I don't expect this kind of PRs, invalid.


Testing lcm results against analytical solution

I implement a test against the analytical solution from Iskhakov et al (2017). The analytical solution was created in the lcm-dev repo.

I created datasets that contain the analytical solution. As discussed with @timmens I skipped the pre-commit hooks for file size as the files are larger than what is currently allowed (approx. 1.8Mb each file).
Also, note that the tests still fail for the initial retired state.

Try to use
def consumption_constraint(consumption, wealth):
    return wealth >= consumption > 0

instead of
def next_wealth_constraint_no_borrowing(next_wealth, labor_income):
    return next_wealth >= labor_income


[FEATURE] User Agent header is overwritten for Azure SDK clients

Is your feature request related to a problem? Please describe.

Azure SDK clients have a standardized User Agent string format prescribed in the Azure SDK guidelines. The Azure OpenAI client created in InternalAzureOpenAiHelper and InternalGitHubModelHelper overwrites the User Agent header which results in loss of valuable details like JDK version, library version and platform details.
Describe the solution you'd like

Use the application_id instead to include the langchain4j information in the User Agent header. This will appear at the beginning of the User Agent header string in the following format.
[<application_id> ]{azsdk-<sdk_language>-<package_name>/<package_version> }+<platform_info>
Additional context
Here's a PR to the proposed solution

@langchain4j I work with @srnagar at Microsoft, he's on the SDK team and we discussed this internally, so once the review is good I'm all for merging this to replace my existing code.


add additional programing languages that surround image

[x]  add typescript
[x]  add postgres
[x]  add node

completed


[request-pull] fix CourrierInternationalBridge

The following changes since commit ad534444fa621963005b617f22699416621c553a:
Merge pull request #407 from sysadminstory/leboncoin-toute-la-france (2016-09-24 19:24:16 +0200)
are available in the git repository at:
https://framagit.org/peetah/rss-bridge fixIndividualBridges
for you to fetch changes up to 3dcdaa1595a80ff78222e622a544d469af51acc5:
[CourrierInternationalBridge] fix content parsing (2016-09-26 00:50:26 +0200)

Pierre Mazière (1):
[CourrierInternationalBridge] fix content parsing
bridges/CourrierInternationalBridge.php | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)

Merged.
Related commits:

3dcdaa1595a80ff78222e622a544d469af51acc5 - [CourrierInternationalBridge] fix content parsing - by @pmaziere


⚠ Bofrost.es has degraded performance

In fa8bd65, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1547 ms

Resolved: Bofrost.es performance has improved in 13bc45a after 7 minutes.


Update pidhandler.py

Fixing Bash syntax error in pid checking script.

qq: on which OS you are seeing this error?

Debian 9. The  AWK command should read '{}' as the output format.

Ok. SGTM.
I am not a linux expert, maybe @nlu90 @huijunw can confirm and approve.


Feature request about windows system tray

Is your feature request related to a problem? Please describe.
When I click on the software icon in the system tray, it does not open directly but displays an open option for me to open after clicking, which is not in line with the operating habits.
Describe the solution you'd like
I hope that when the software is closed and shrunk in the system tray, the left mouse button double-click or click to open it, and the right mouse button is the display option. This is more in line with operating habits.
Describe alternatives you've considered
No response
Additional context
No response

Added in 4eb9e8fe80e985105f322683ba33017e17e85352
Will be released in v1.8.0 in 1 or 2 weeks


[refactor] Merge Commits

cc https://github.com/codecov/codecov.io/pull/213

Read more at https://github.com/codecov/support/wiki/Merge-Commits

Closing due to age


Business Central: Error 'The type or method 'Open' cannot be used for 'Extension' development'

I am trying to create a report to read csv file data and import it into a Business Central table.
When I a method 'Open' which is a method of 'File Management' codeunit, I am getting this error:
The type or method 'Open' cannot be used for 'Extension' development
Can anybody help me find out the code to import data into a table from a file using AL code.

Hi! Have you used the search functionality on this repository to find similar issues such as https://github.com/Microsoft/AL/issues/4721 ?

Duplicate of #4721


Update eclipse-php to v4.5

There is no longer a 32-bit version offered so that section was removed. The depends-on was added and the app was changed to match the other upgraded eclipse casks.

Thank you for the contribution. It was merged directly as b28adbc53652032691c4cc995853a5ddab490d41 to keep commit history cleaner. Your contribution is still credited to you.


See it in action video is corrupt

The video located under the heading "See it in action" at:
https://tenderowl.com/work/frog/
does not work in Firefox. (It does seem to work in Chromium and Chromium-based browsers.)
Firefox reports it as corrupt. (Mozilla Firefox 97.0.1 on ArchLinux.)

Moved the video to Youtube :)


NathanWalker/ui router

add ui-router

@NathanWalker - Are you intending to deviate away from the parent seeds router implementation?
That's going to make upstream changes a p.i.t.a.

Thanks @Jimmysh I'll take a look in more detail shortly.
@d3viant0ne This will go on the ui-router branch only.

@Jimmysh Looks like you still have this targeting master though. If you close this, then reopen, you can change the target branch to ui-router for the PR.


[BEAM-1385] Add license header to website Jenkins job descriptions

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[x] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[x] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[x] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[x] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

Changes Unknown when pulling 838ef04da912091db6f83be2fe48a9a3525e8279 on kennknowles:groovy-RAT into ** on apache:master**.

Because this unbreaks the build, I am going to merge before review.

R: @davorbonaci

(or any committer, since we are now switching which side of the Earth is in daylight :-)

LGTM.
Thanks @kennknowles; much appreciated. FYI @jasonkuster.

@peihe created #1911 to fix too, looks like this got in before his.


zsh: fzf-completion: use noshwordsplit local option

This also fixes the completion causing a bell / flickering in case
"shwordsplit" was not set, because then the function would return false.

This is nice, thanks!


Ship Bulloak as a Release

Currently, Bulloak is shipped under the tag category. It would be great to see it shipped as a Software Release.

yeah, makes sense, will do as soon as I can

Hey @smol-ninja ! Just released the latest version. Let me know if everything works well, if not, feel free to reopen this issue.

Great. Thank you very much @alexfertel.


Added error handling for 404 and 500 status codes

Shows an custom error page (instead of the default).
If a 500 internal server error is encountered, IMSS is emailed with
the traceback.

@epelz @dwang159 @mendoncakeegan @rpinkerton sorry for the spam lol

Okay, this should be ready to merge

lgtm

Live.