Request for New Branch: German Translation

The German translation team has initiated work on translating the book. Our updates reside on the 'german-translation' branch in my forked repository.
We request that a new branch, 'german-translation', be created in the base repository. This dedicated branch will facilitate our work and allow us to contribute directly to it.
After the new branch is in place, please change the target of this pull request to 'german-translation'. Then proceed with the merge.
Does this approach work for you? :)

I support this idea and it is what the other translations are leaning towards, but I am checking with my technical folks about potential benefits/challenges of each approach…let me revert to you shortly, but take this as tentative support and you can go ahead if you feel blocked.
Best,
Glen
Infinite diversity in infinite combinations. (he/him/his)
https://www.radicalxchange.org/
From: Erich @.>
Sent: Tuesday, June 6, 2023 3:53 AM
To: pluralitybook/plurality @.>
Cc: pluralitybook @.>; Mention @.>
Subject: Re: [pluralitybook/plurality] Request for New Branch: German Translation (PR #6)
Thank you so much for setting up the branch for us, Glen @.*** https://github.com/pluralitybook ). Upon further deliberation, we'd actually like to propose an alternative approach for managing the German translation project.
While the initial idea of maintaining a separate branch for the German translation within the existing repository https://github.com/pluralitybook/plurality  could work, it presents the challenge of requiring you to review every commit and merge to that branch. Considering that the translation project is primarily managed by a separate team, this arrangement is not necessarily the most efficient.
To streamline the process, we suggest that we create a separate repository specifically for the German translation, still housed under this account https://github.com/pluralitybook . This approach might offer several benefits:

Autonomy: With @XQTStrategy https://github.com/XQTStrategy  and myself having permissions to review and merge commits/PRs in the new repository, the German team can independently manage the translation work without impacting the flow of the original book's development.
Legitimacy and Accessibility: Keeping the German translation under this account will ensure the project's legitimacy and increase its accessibility. Users interested in the German version will easily find the project associated with the original source, strengthening the connection and the credibility of our work.
Project Management: Separate repositories enable cleaner project history and management, reducing confusion for all contributors involved.

This is just a suggestion, and we are completely open to your preferences or any other ideas you might have. Our ultimate goal is to facilitate an effective and efficient workflow that benefits all parties involved and serves the community of contributors and readers interested in our work.
So thank you for the consideration -- please feel free to share your thoughts and any other potential solutions you might have in mind. :-)
—
Reply to this email directly, view it on GitHub https://github.com/pluralitybook/plurality/pull/6#issuecomment-1578117553 , or unsubscribe https://github.com/notifications/unsubscribe-auth/A3BRRPQLTHNOZ3Y5AHJXXL3XJ3OVTANCNFSM6AAAAAAYQGOIN4 .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/A3BRRPUH6HRO2AVDATOLUODXJ3OVTA5CNFSM6AAAAAAYQGOIN6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS6CAU3C.gif Message ID: @.*** @.***> >

I confirmed with the technical team that this makes sense.  It will allow the repo to manage its own governance, which I think is desirable.  We can still create linkages with the governance for the root, but independence as a baseline is a better starting point I think.
From: @.*** @.>
Sent: Tuesday, June 13, 2023 3:32 PM
To: 'pluralitybook/plurality' @.>; 'pluralitybook/plurality' @.>
Cc: 'Mention' @.>
Subject: RE: [pluralitybook/plurality] Request for New Branch: German Translation (PR #6)
I support this idea and it is what the other translations are leaning towards, but I am checking with my technical folks about potential benefits/challenges of each approach…let me revert to you shortly, but take this as tentative support and you can go ahead if you feel blocked.
Best,
Glen
Infinite diversity in infinite combinations. (he/him/his)
https://www.radicalxchange.org/
From: Erich @.*** @.> >
Sent: Tuesday, June 6, 2023 3:53 AM
To: pluralitybook/plurality @. @.> >
Cc: pluralitybook @. @.> >; Mention @. @.***> >
Subject: Re: [pluralitybook/plurality] Request for New Branch: German Translation (PR #6)
Thank you so much for setting up the branch for us, Glen @.*** https://github.com/pluralitybook ). Upon further deliberation, we'd actually like to propose an alternative approach for managing the German translation project.
While the initial idea of maintaining a separate branch for the German translation within the existing repository https://github.com/pluralitybook/plurality  could work, it presents the challenge of requiring you to review every commit and merge to that branch. Considering that the translation project is primarily managed by a separate team, this arrangement is not necessarily the most efficient.
To streamline the process, we suggest that we create a separate repository specifically for the German translation, still housed under this account https://github.com/pluralitybook . This approach might offer several benefits:

Autonomy: With @XQTStrategy https://github.com/XQTStrategy  and myself having permissions to review and merge commits/PRs in the new repository, the German team can independently manage the translation work without impacting the flow of the original book's development.
Legitimacy and Accessibility: Keeping the German translation under this account will ensure the project's legitimacy and increase its accessibility. Users interested in the German version will easily find the project associated with the original source, strengthening the connection and the credibility of our work.
Project Management: Separate repositories enable cleaner project history and management, reducing confusion for all contributors involved.

This is just a suggestion, and we are completely open to your preferences or any other ideas you might have. Our ultimate goal is to facilitate an effective and efficient workflow that benefits all parties involved and serves the community of contributors and readers interested in our work.
So thank you for the consideration -- please feel free to share your thoughts and any other potential solutions you might have in mind. :-)
—
Reply to this email directly, view it on GitHub https://github.com/pluralitybook/plurality/pull/6#issuecomment-1578117553 , or unsubscribe https://github.com/notifications/unsubscribe-auth/A3BRRPQLTHNOZ3Y5AHJXXL3XJ3OVTANCNFSM6AAAAAAYQGOIN4 .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/A3BRRPUH6HRO2AVDATOLUODXJ3OVTA5CNFSM6AAAAAAYQGOIN6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS6CAU3C.gif Message ID: @.*** @.***> >

hey folks,
Chiming in from the Traditional Mandarin side, I was going to propose another solution and saw this thread. If there is a desire to standardize the way new translations get created and synced with the website, I thought perhaps sharing here could be useful to get some feedback:
Given the long-term plan to progressively decentralize, would it perhaps make more sense to allow different languages to self-initiate a translation by forking a new repository?
To solve for Legitimacy and Accessibility, perhaps we can create an "official translations" section under ReadME.md in the original repo that lists each repository for people to access.
If the way translations are submitted is standardized in the same format, perhaps the website can pull directly from GitHub as well to optimize the workflow even more as new chapters get added and translated
Curious about what you guys think!
Best,
Jacky

I agree with this analysis and we will proceed.  Thank you Jacky!
From: Jacky @.>
Sent: Friday, June 16, 2023 1:59 PM
To: pluralitybook/plurality @.>
Cc: pluralitybook @.>; Mention @.>
Subject: Re: [pluralitybook/plurality] Request for New Branch: German Translation (PR #6)
hey folks,
Chiming in from the Traditional Mandarin side, I was going to propose another solution and saw this thread. If there is a desire to standardize the way new translations get created and synced with the website, I thought perhaps sharing here could be useful to get some feedback:
Given the long-term plan to progressively decentralize, would it perhaps make more sense to allow different languages to self-initiate a translation by forking a new repository?
To solve for Legitimacy and Accessibility, perhaps we can create an "official translations" section under ReadME.md in the original repo that lists each repository for people to access.
If the way translations are submitted is standardized in the same format, perhaps the website can pull directly from GitHub as well to optimize the workflow even more as new chapters get added and translated
Curious about what you guys think!
Best,
Jacky
—
Reply to this email directly, view it on GitHub https://github.com/pluralitybook/plurality/pull/6#issuecomment-1595052649 , or unsubscribe https://github.com/notifications/unsubscribe-auth/A3BRRPRSK6SGQZCJEJAQCMTXLSNGHANCNFSM6AAAAAAYQGOIN4 .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/A3BRRPVHYC7H7SYOAOBLA5TXLSNGHA5CNFSM6AAAAAAYQGOIN6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS7CKJGS.gif Message ID: @.*** @.***> >

Sure I can do that!
From: Erich @.>
Sent: Friday, June 16, 2023 1:40 PM
To: pluralitybook/plurality @.>
Cc: pluralitybook @.>; Mention @.>
Subject: Re: [pluralitybook/plurality] Request for New Branch: German Translation (PR #6)
Thanks for the flexibility and confirming with the technical team, Glen. Would you mind setting up the German repository with @pluralitybook https://github.com/pluralitybook 's account and adding @XQTStrategy https://github.com/XQTStrategy  and my Github account as managers?
Perhaps calling the repository german-translation?
Let us know if we can assist with anything in the set up.
—
Reply to this email directly, view it on GitHub https://github.com/pluralitybook/plurality/pull/6#issuecomment-1595028134 , or unsubscribe https://github.com/notifications/unsubscribe-auth/A3BRRPRSOUNNI3G5L7EMGOLXLSK7BANCNFSM6AAAAAAYQGOIN4 .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/A3BRRPUNGSZO3CP2A4R5673XLSK7BA5CNFSM6AAAAAAYQGOIN6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS7CIZKM.gif Message ID: @.*** @.***> >

Desired repo name?  Perhaps the name you intend in German?  What is that?
From: Erich @.>
Sent: Friday, June 16, 2023 1:40 PM
To: pluralitybook/plurality @.>
Cc: pluralitybook @.>; Mention @.>
Subject: Re: [pluralitybook/plurality] Request for New Branch: German Translation (PR #6)
Thanks for the flexibility and confirming with the technical team, Glen. Would you mind setting up the German repository with @pluralitybook https://github.com/pluralitybook 's account and adding @XQTStrategy https://github.com/XQTStrategy  and my Github account as managers?
Perhaps calling the repository german-translation?
Let us know if we can assist with anything in the set up.
—
Reply to this email directly, view it on GitHub https://github.com/pluralitybook/plurality/pull/6#issuecomment-1595028134 , or unsubscribe https://github.com/notifications/unsubscribe-auth/A3BRRPRSOUNNI3G5L7EMGOLXLSK7BANCNFSM6AAAAAAYQGOIN4 .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/A3BRRPUNGSZO3CP2A4R5673XLSK7BA5CNFSM6AAAAAAYQGOIN6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS7CIZKM.gif Message ID: @.*** @.***> >


Configure a bot that closes stale issues/PRs

What do we think about having a bot that automatically marks/closes stale issues?

@andersy005 might know about this?


Release v1.3.1

Release v1.3.1 (v1.3.0 was used for an earlier version of the final product in case we do not have time to finish all the features).
This will be kept as draft until all features have been merged in.

Codecov Report
Base: 77.55% // Head: 77.55% // No change to project coverage :thumbsup:

Coverage data is based on head (92238ee) compared to base (ff26502).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #113   +/-   ##
=========================================
  Coverage     77.55%   77.55%
  Complexity      745      745
=========================================
  Files           111      111
  Lines          2245     2245
  Branches        265      265
=========================================
  Hits           1741     1741
  Misses          408      408
  Partials         96       96

Impacted Files
Coverage Δ

src/main/java/seedu/address/MainApp.java
0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


userdb to use dtfClient API

The userdb module will be changed to use the dtfClient API.

Forgot to close. Fixed: https://github.com/jakev/dtfmods-core/commit/f5df0b99dcc2fc992102f32b249b5372d72cb66c


[python] Update Parameterization to pull outputs regardless of input

[python] Update Parameterization to pull outputs regardless of input
Today parameterization will skip prompts if the input is not parameterizable. Instead, update to paramterize outputs even if the input is not parameterizable.
Typescript sdk already does something similar.
Testplan
Run with HF Remote Inference models

removed an unintended ipynb


SCSS compiling issue in Foundation sites v6.5.0rc

I got a Warning when compile SCSS.
WARNING: null was passed to rem-calc(), which is not a number.
on line 78 of node_modules/foundation-sites/scss/util/_unit.scss, in function -zf-to-rem
from line 47 of node_modules/foundation-sites/scss/util/_unit.scss, in function rem-calc
from line 84 of node_modules/foundation-sites/scss/xy-grid/_cell.scss, in function if
from line 84 of node_modules/foundation-sites/scss/xy-grid/_cell.scss, in mixin -xy-cell-properties
from line 174 of node_modules/foundation-sites/scss/xy-grid/_cell.scss, in mixin xy-cell-static
from line 276 of node_modules/foundation-sites/scss/xy-grid/_classes.scss, in mixin xy-vertical-grid-classes
from line 471 of node_modules/foundation-sites/scss/xy-grid/_classes.scss, in mixin foundation-xy-grid-classes
from line 20 of src/scss/helper/_main.scss
from line 2 of src/scss/style-rtl.scss
WARNING: null was passed to rem-calc(), which is not a number.
on line 78 of node_modules/foundation-sites/scss/util/_unit.scss, in function -zf-to-rem
from line 47 of node_modules/foundation-sites/scss/util/_unit.scss, in function rem-calc
from line 84 of node_modules/foundation-sites/scss/xy-grid/_cell.scss, in function if
from line 84 of node_modules/foundation-sites/scss/xy-grid/_cell.scss, in mixin -xy-cell-properties
from line 174 of node_modules/foundation-sites/scss/xy-grid/_cell.scss, in mixin xy-cell-static
from line 276 of node_modules/foundation-sites/scss/xy-grid/_classes.scss, in mixin xy-vertical-grid-classes
from line 471 of node_modules/foundation-sites/scss/xy-grid/_classes.scss, in mixin foundation-xy-grid-classes
from line 20 of src/scss/helper/_main.scss
from line 2 of src/scss/style.scss
This is my breakpoint:
$breakpoints: (
small: 0,
medium: 551px,
large: 801px,
xlarge: 1261px,
xxlarge: 1441px,
xxxlarge: 1681px,
);
$print-breakpoint: large;
$breakpoint-classes: (small medium large xlarge xxlarge xxxlarge);
I see someone get same issue in https://foundation.zurb.com/forum/posts/58327-foundation-cli-sites-update-to-650rc1-issue
Thanks

Getting the same error:
WARNING: null was passed to rem-calc(), which is not a number.
Backtrace:
        node_modules/foundation-sites/scss/util/_unit.scss:78, in function `-zf-to-rem`
        node_modules/foundation-sites/scss/util/_unit.scss:47, in function `rem-calc`
        node_modules/foundation-sites/scss/xy-grid/_cell.scss:84, in function `if`
        node_modules/foundation-sites/scss/xy-grid/_cell.scss:84, in mixin `-xy-cell-properties`
        node_modules/foundation-sites/scss/xy-grid/_cell.scss:174, in mixin `xy-cell-static`
        node_modules/foundation-sites/scss/xy-grid/_classes.scss:276, in mixin `xy-vertical-grid-classes`
        node_modules/foundation-sites/scss/xy-grid/_classes.scss:471, in mixin `foundation-xy-grid-classes`
        src/assets/scss/app.scss:9

I've dived a little bit into it and found that the error happens here (https://github.com/zurb/foundation-sites/blob/v6.4.3/scss/xy-grid/_classes.scss#L276), because $-zf-size is null, and in an older version of foundation small was passed here. But i can not find out wherer $-zf-size gets defined.

These are just warnings, compilation should still work.

cc @ncoden I guess this is the fallback of the mediaquery

These are just warnings, Foundation should compile fine. But this should be resolved anyway. I'll take a look at this.
@anvucodespot @marvinhuebner Does this SCSS compilation break after these errors ? Otherwise is there any issue when your site is running ?

@anvucodespot For your next issue, please follow the template

@ncoden compilation does not break, it's only a warning.

Hi, I appreciate this is only a warning, but I've duplicated some investigating time and also got as far as seeing that $-zf-size is null in _classes.scss, but couldn't get past that.
Compilation doesn't fail, but I'd like to understand what's wrong, and if it's something I should address in our code? Another issue (https://github.com/zurb/foundation-sites/issues/10015) alludes to the definition of custom breakpoints, but that's not something we're doing.
Happy to troubleshoot if you can give me a nudge in the right direction.

I'm working on this. There is some issues with the way we handle $-zf-size and its default value. So I guess you have nothing to do, the problem is only on our side. I`ll let you know about a possible fix.

@ncoden I'm sorry, I will follow the template in next time. The SCSS compilation is not break after compiling.
Thankyou.

#11361 fixes it for me, thanks for the speedy response!

Can confirm #11361 fixed the problem here.


Fixes #58: corrected 'reps' to 'trials' to fix fts_dmd_lds demo

Renames "reps" in the 3rd cell of fts_dmd_lds demo to "trials" for the demo to work.

Fixes #58

@sameerashahh please edit your pull request to match the guidelines in CONTRIBUTING.md https://github.com/DynaDojo/dynadojo/blob/main/CONTRIBUTING.md#pull-request-checklist


Updated GH-161

Fixes PEP8 issues and updates examples_output info
There may be a better way to do this with github, but I'm not aware of it :)

@phobologic thanks for doing this! Extremely useful. :+1: :+1:  (Sorry I didn't get back to it over the holidays).

No worries, thanks for the PR!


Add in support for setting default texture resolution

Currently if one is running on a browser with a devicePixelRatio > 1 and one is not using retina prefix values, then the textures will be displayed larger than expected. To provide more flexibility, it would be helpful to support the ability to allow for a default texture resolution to use.
An example usage, which I am doing, is opting to treat everything as native resolution (eg. set Application resolution to 1, not devicePixelRatio).
I've actually written about it here, along with a solution I am currently using.
http://www.html5gamedevs.com/topic/43636-texture-loading-and-non-integer-devicepixelratio

do you load all your texture through a loader? maybe we can add something in metadata object that can be passed to it :) I use it for pixi-spine loading.
https://github.com/pixijs/pixi-spine/blob/master/examples/change_atlas_extension.md
https://github.com/pixijs/pixi-spine/blob/master/src/loaders.ts#L75
We can do pass-through of certain parameters in the texture loader the same way. right now its very stupid: https://github.com/pixijs/pixi.js/blob/dev/packages/loaders/src/TextureLoader.js#L18

Yes, I do all my loading through the loader.
I couldn't find anything indicating the actual arguments for loader add. I also thus far haven't found what calls Texture from (so I can understand the process better).
I have seen this in the Pixi-spine code you referenced.
                loader.add(name, url, imageOptions, (resource: PIXI.LoaderResource) => {
                  if (!resource.error) {
                    callback(resource.texture.baseTexture);
                  } else {
                    callback(null);
                  }
                });

Which presumably indicates that loader.add can take options.
What is the expected format of this? I've tried
loader.add('sprite', 'sprite.png', { resolution: 2 });
loader.add('sprite', 'sprite.png', { metadata: { resolution: 2 }});

And a few other variants which include putting it into imageMetadata. But have not seen it make any noticeable changes. I also put in some debug console.log into pixi.js, and I don't even see my values surface within BaseTexture, Texture, or Spritesheet.
One aspect which is confusing is that the code references at some point, the concept of imageMetadata and also then references a meta.scale. So it seems like inconsistency (I can't get it to work right now by trying to feed in values). I guess the point of this comment, is it is slightly convoluted how this is being handled.
From my testing, any object I use as the 3rd argument to loader.add does not seem to make it into BaseTexture, Texture, and Spritesheet. The loaders (TextureLoader and SpritesheetLoader) do see the meta.
The other comment I would cite is if the solution stems from adding options to the calling argument, this seems more error prone to the end user. Because one needs to do this for every asset of BitmapText, Spritesheet, and Texture that is loaded.
The ideal solution should uniformly apply resolution to BaseTexture, BitmapText, Spritesheet, and Texture. Right now the most "common" way is through getResolutionOfUrl. A weakness of this approach would be if someone passed in an actual image versus a URL, it would not be covered.
One last note here. I did try and override
PIXI.settings.RESOLUTION = window.devicePixelRatio;

And it did not help either.
I'm still going through the code and experimenting.

loader.add('sprite', 'sprite.png', { metadata: { resolution: 2 }});

then you'll get resource.metadata inside the loader middleware, and you can pass it somehow to Texture.fromLoader , then maybe we need to modify fromLoadermethod itself to pass it further.
Btw, premultiplyAlpha is one more param that i'd like to see there :)

Eventually one can get the values in that way. However, it requires a changed to the loaders. So I suppose perhaps what you are trying to say is just make custom loaders? And if this is the case, why not just wire it up so real meta can pass through.
I don't think I'm necessarily an outlier in wanting to do resolution = 1. Even this individual was sort of querying about the same
https://github.com/pixijs/pixi.js/issues/6029
I'm happy to implement if needed. IMHO, slightly cleaner to require less code entry. Just let me know which way you prefer and I'll put that method in a branch for you to review.
Another thing to factor, which I mentioned was if you don't pass in a url but actual data. Both getResolutionOfUrl and whatever we do here won't catch it.
Another thing I notice BTW, unfortunately values of width/height are also not correct once one goes down this route. For example, if I get width from the sprite, the value requires resolution scaling.
The BaseTexture itself has the proper realWidth, realHeight but that is for the overall texture.
Typically one would expect the proper unit values returned. For example, if I have a resolution !=1 it implies "points".  If == 1, then it would be equivalent to "pixels".
I'm currently working on some layout code, so I may have some more observations soon

I think that issue is related to baseTexture.setResolution , need some time to remember what did i write there.

I plan on looking at this further this weekend. I'll probably do a couple of versions and show you.  Now that I have my foundational code working, I have a bit better understanding of my needs as well as the things I misunderstood about what pixijs is doing. I'm still getting used to pixijs so my mental model of how it works changes daily.

I'm still getting used to pixijs so my mental model of how it works changes daily.

I'm familar with code of several renderers with different architecture, I know that feeling :)


Orthographic camera and particles

Dear Greg,
I have come across another bottleneck, which is the following:
I have noticed that the simulator only works in orthographic mode and that works fine for me except for the weather I use with Unistorm - The particles are not visible this way.
So if I switch the perspective mode I am able to see the weather but then I am not able to move the cars around.
So my question is:
Is there a way to make the cars and the application work in perspective mode and if not do you know how I can make the particles work in orthographic mode?
Thanks in advance!

hey Justin, you should be able to convert to perspective mode with a little work to confirm that the 2d physics and screen UI are aligned.
Alternatively, if you stay in orthographic mode you could render your 3d scene (particles, etc) to a second camera with a render texture assigned, and then use that render texture in a RawImage component in the UI as a background.
Unity RenderTexture
Unity UI RawImage

Awesome! Thanks for the quick response!
I was thinking of trying that so it's great that you are confirming that possibility, I will look into that!
Now let's say I do want to switch to perspective which you say is possible, what do you exactly mean with aligning the 2D physics and screen UI.
Could you give me some hints where to exactly look at or what I would have to change or focus on?
Your help is much appreciated, thanks again Greg!

In Unity, 2d physics runs in the x/y plane at z=0. You can move 2d bodies in z for organisation but by default the physics doesn't take any notice of it. The screenspace overlay UI is rendered after everything else in the scene and will be drawn over the top of everything and not be affected by any camera position or rotation.
The current setup in the app is to use rays/positions from the screen to check for physics hits for dragging items. This is simplified a bit because the screenspace UI and the physics are aligned. If you change to a perspective camera and don't want to change the hit detection calculations (screen -> 2d physics) then you will probably want to make sure you don't move the camera. If you do move the camera then you'll need to map the screen touches to the camera, and then a ray into the world to find its position at z=0 which is where the 2d physics is based so you can detect hits.
You could also consider using 2 cameras: one for your 3d content which is rendered first, and a second one for the 2d content which is set to not clear the background first so it renders over the top.


Update QIR Runtime to use QubitIdType

This updates the QIR Runtime to use a consistent type for qubit ids, typedef intptr_t QubitIdType;. All APIs that correspond to the QIR spec continue to use opaque pointer type QUBIT* and then immediately cast to QubitIdType for use internally. Of note, the Qubit Manager uses negative values for special meaning when tracking qubits in use, so the unsigned uintptr_t is not compatible.
This is part 1 of the change. The update of the native simulator and corresponding C# types from unsigned to intptr_t will be part of a separate change.

/azp run

Done reviewing. Thanks.


Create uvmx.txt

@musanchaj The first verification stage is complete: the official domain for  Universidad Veracruzana is www.uv.mx, to the best of my knowledge. This is just an informational note. The pull request is still under review. The review may take some more time. I greatly appreciate your patience. Here is the proof of domain ownership: https://www.uv.mx/nutri-xal/cuerpo-directivo-2/

@musanchaj Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


Image Thumbnail not being updated while re-capturing

While Re-capturing Image, Thumbnail is not being updated right away, but if we go previous or next and come back to the same item, it does!
@MJ1998

This is due to the file location being the same, the answer component does not change and hence the UI does not update the thumbnail!
Current solution to this would be to remove the previous answer and add a new one. These APIs are available in the current master branch of datacapture library which will be available in the next release!


[stable/redis-ha] use master group name not used in haproxy tcp-check…

… (#17868)
Signed-off-by: Clément Schockaert<EMAIL_ADDRESS>Which issue this PR fixes

fixes #17868

Special notes for your reviewer:
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/ok-to-test

@zaneclaes seems good to me

We are running into another issue, since we are using this chart in multiples release and we want to be more flexible, we need to be able to tpl against the masterGroupName or at least use something like :
{{- define "redis-ha.masterGroupName" -}}
{{- if .Values.redis.masterGroupName -}}
{{ .Values.redis.masterGroupName }} # or even use tpl here ?
{{- else -}}
{{ .Release.Name }}-mymaster
{{- end -}}
{{- end -}}

is it ok to you to push a change like that?

We are running into another issue, since we are using this chart in multiples release and we want to be more flexible, we need to be able to tpl against the masterGroupName or at least use something like :
{{- define "redis-ha.masterGroupName" -}}
{{- if .Values.redis.masterGroupName -}}
{{ .Values.redis.masterGroupName }} # or even use tpl here ?
{{- else -}}
{{ .Release.Name }}-mymaster
{{- end -}}
{{- end -}}

is it ok to you to push a change like that?

@cschockaert  Your current changes in the PR look good and very necessary. However, just so I'm sure I understand what you're asking above, you want to add a tpl function in the case the masterGroupName is not defined? If so, I think this is okay. @DandyDeveloper any thoughts on this?

@cschockaert @ssalaues This looks like a good change, but I want to play devils advocate to understand the justification of the group name change.
Would the more appropriate thing for multiple releases, be to use --set in the helm install command? This is what I do.

@DandyDeveloper you are right, after all i think that emptying master name should just be prohibed.
Well all we need here is the capability of templating the master group name, i would suggest a change like that every where we need master group name:
{{ tpl .Values.redis.masterGroupName $ }}
or somehting in helpers like that:
{{- define "redis-ha.masterGroupName" -}}
{{- $masterGroupName := tpl ( .Values.redis.masterGroupName | default "mymaster") $ -}}
{{- $validMasterGroupName := regexMatch "^[A-Za-z0-9_-]+$" $masterGroupName -}}
{{- if $validMasterGroupName -}}
{{ $masterGroupName | lower }}
{{- else -}}
{{ required "A valid .Values.redis.masterGroupName entry is required (matching ^[A-Za-z0-9_-]+$)" ""}}
{{- end -}}
{{- end -}}

masterGroupName will be check against a regexp
(Note: master name should not include special characters or spaces.
The valid charset is A-z 0-9 and the three characters ".-_".)
empty masterGroupName will be mymaster
masterGroupName can be templated inside values.yaml

To be clear why we need that tpl feature, its because we got a lot of redis-ha chart installed in our preemptible instance, and under certains circumstances sentinel of another redis-ha release joined together and leading to uncomprehensible situation where we got many redis at prior unknown of each other (differents redis-ha charts) working (so not well working) together

@cschockaert I actually agree that a validation template function would be ideal. That's a great suggestion to prevent people scratching their heads why their instances are not running.

under certains circumstances sentinel of another redis-ha release joined together

This is strange behaviour... Are you using namespaces for the different releases? I am not sure how this can happen when the announce addresses are explicit to the release name. Considering that we explicitly use the IP for those announce addresses as well, I am not sure how this kind of behavior happens.

We are using differents namespace for redis-ha and fullnameOverride.
for example with fullname override = product-api-redis-ha
so we can have theses svc in namespace one:
product-api-redis-ha
product-api-redis-ha-announce-0
product-api-redis-ha-announce-1
product-api-redis-ha-announce-2
product-api-redis-ha-haproxy

and the same one in another namespace.
I saw in config that we resolve ip against fullname but we dont prefix any namespace in dns
ex :
{{ template "redis-ha.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local
product-api-redis-ha.namespacea.svc.cluster.local
but without adding {{ .Release.Namespace }}.svc.cluster.local, kubedns will normally resolve in current namespace.
Another thing i saw is that our mixed releases are not mixed with the same fullnameOverride. it's totally random..

/retest

We are using differents namespace for redis-ha and fullnameOverride.
for example with fullname override = product-api-redis-ha
...
I saw in config that we resolve ip against fullname but we dont prefix any namespace in dns
ex :
{{ template "redis-ha.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local
product-api-redis-ha.namespacea.svc.cluster.local
but without adding {{ .Release.Namespace }}.svc.cluster.local, kubedns will normally resolve in current namespace.
Another thing i saw is that our mixed releases are not mixed with the same fullnameOverride. it's totally random..

So I understand that you are using essentially the same service names in your various namespaces, but the point of the namespace is exactly for this reason. There should be no reason that I can see why your redis quorum in namespace-a can attach to another redis in namespace-b since (exactly as you said) without adding the  {{ .Release.Namespace }}.svc.cluster.local it will always resolve within the same namespace therefore preventing the redis/sentinels joining across namespaces. So the question is, why are your redis instances attaching across namespaces?

Well, i don't know how it happened, since i use isolation with differents group name it did not happen again.
But we are using istio and preemtible instance.
There is a lot of crashloopbackoff coz of istio slowing down startup of pods.
Perhaps one pod got rescheduled with another IP and the old IP was used by another redis/sentinel instance, leading to other sentinel monitoring this pod by ip allow him to join the redis cluster.
I mean, since redis.conf and sentinel.conf is populated by IP and not dns, this can happen

We have a situation too (caused by slow startup and K8S killing pod) where for example a cluster of 3 instance, we got
redis-0 slave and replica of redis-2
redis-1 slave and replica of redis-0
redis-2 master
this happened after a rollingupdate restarting redis-2 then 1 then 0
perhaps due to a race condition in config-init choosing index 0 as master, and a sentinel quorum relecting a new master.
i have to investiguate about that too...

@ssalaues @DandyDeveloper seems to me that all is resolved around master name customization, can we merge it?
thanks :)

Hello, just updated this MR, @ssalaues @DandyDeveloper

@ssalaues @DandyDeveloper someone here?

@ssalaues Simply because you've been so heavily involved in the discussion. Can you approve this if it looks good to you?
If you want me to get involved, let me know and I'll weigh in on the discussion. I don't want to LGTM @cschockaert just incase Salim has some thoughts.

Nice, just updated this MR to get rid of conflict (chart version)

/lgtm


Usage -> IAM credentials, have 2nd step copy + pasteable

Making the commands at the 2nd step of Usage -> IAM credentials without change useable in the local environment
Inspiration is from https://cloud.google.com/solutions/using-jenkins-for-distributed-builds-on-compute-engine - maybe something else is missing?

My adaptions do still not work, will create another PR later, when everything works fine.


Change log to output full error object.

Problem: See #181.
Solution: Use serialize-error to include stack traces
Testing: ?

Adding a throw Error(/*...*/) in packages/coinstac-ui/app/render/log.js reveals this works:


Refactor tinkerbell hardware 4

Depends on: #1340
As part of the Tinkerbell provider end-user workflow we generate files for registration in the Tinkerbell stack and management clusters.
This PR introduces a CSV Reader that can supply Machine instances to Translate() so they can be written out in other formats such as capt hardware yaml or Tinkerbell hardware json.

/hold


Unable to fetch on ubuntu 20.04 (Version GLIBC_2.27 not found)

Description
Ubuntu upgraded to version 20.04 breaks git fetch and pull support inside Atom
Steps to Reproduce
Install or upgrade to Ubuntu 20.04
Launch atom
Right click on Fetch
Pull  => Error messages

Here is the error message:
/snap/atom/248/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-http: /snap/core/current/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.27' not found (required by /usr/lib/x86_64-linux-gnu/libssh.so.4)
/snap/atom/248/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-http: /snap/core/current/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /usr/lib/x86_64-linux-gnu/libssh.so.4)
/snap/atom/248/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-http: /snap/core/current/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1)
/snap/atom/248/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-http: /snap/core/current/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.27' not found (required by /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2)
/snap/atom/248/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-http: /snap/core/current/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2)
/snap/atom/248/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-http: /snap/core/current/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/x86_64-linux-gnu/liblber-2.4.so.2)
/snap/atom/248/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-http: /snap/core/current/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /usr/lib/x86_64-linux-gnu/libgnutls.so.30)
/snap/atom/248/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-http: /snap/core/current/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.26' not found (required by /usr/lib/x86_64-linux-gnu/libp11-kit.so.0)
/snap/atom/248/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-http: /snap/core/current/lib/x86_64-linux-gnu/libcrypt.so.1: version `XCRYPT_2.0' not found (required by /usr/lib/x86_64-linux-gnu/libkrb5.so.26)
/snap/atom/248/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-http: /snap/core/current/lib/x86_64-linux-gnu/libcrypt.so.1: version `XCRYPT_2.0' not found (required by /usr/lib/x86_64-linux-gnu/libroken.so.18)
/snap/atom/248/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-http: /snap/core/current/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /usr/lib/x86_64-linux-gnu/libsqlite3.so.0)
/snap/atom/248/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-http: /snap/core/current/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /usr/lib/x86_64-linux-gnu/libsqlite3.so.0)

Versions
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04 LTS
Release:	20.04
Codename:	focal
$ ldd --version
ldd (Ubuntu GLIBC 2.31-0ubuntu9) 2.31
Atom version is 1.45.0 installed from snap

Workaround:
export LOCAL_GIT_DIRECTORY=/usr


[Bot-Ai-QnA] Add QnAMakerRecognizer class

Fixes #
Description

Specific Changes

Testing

@fran893 - I already applied the requested changes.

@fran893 - I already applied the requested changes.


return defaultValue for null and undefined

treat null and undefined as missing
apply same behaviour as in https://github.com/zemirco/json2csv/blob/2ea1c3c3c1259725a8b43458ef788ef30ef6d0a8/lib/JSON2CSVBase.js#L94-L106

Current behaviour:
const fields = [{ label: 'ID', value: 'id' }];
const transformer = new Transform({ fields });

Converts only undefined to defaultValue (see getProp)
const fields = [{ label: 'ID', value: (row) => row['id'] }];
const transformer = new Transform({ fields });

Converts null and undefined to defaultValue (see here)

I'll leave it to @juanjoDiaz to comment, since it might be that way for a reason. Otherwise the code looks fine.

Hi all,
The reason for it to be like this is that undefined means that the field was empty while null means that the value null was there. For example, null is a valid JSON value while undefined is not.
I've seen endless discussion about whether null and undefined should be considered the same or only undefined should be considered as missing property and null to indicate that the property was set but was just empty.
I don't think that we will solve that here 😅
In any case, this breaks the API since we don't know if our users are currently that actually expect to get the null back.
So I don't think that we should merge it.
I'd be happy to add a new property useDefaultValueOnNull given that the PR adds the necessary tests and documentation. Also, if we add such property we probably want to do better caching to avoid the extra boolean check on every field of every object potentially affecting performance.
Al alternative is to use a transform to convert nulls into undefineds.

Hi @juanjoDiaz I agree with you that introducing an additional option (useDefaultValueOnNull) makes sense. I'll free some time for it during next week hopefully.

The reason for it to be like this is that undefined means that the field was empty while null means that the value null was there.

This makes sense but it is actually inconsistent. As described when using a function as fieldInfo value the behaviour is different to using the column key as fieldInfo value. So I guess this should then also be unified? That would still be some kind of breaking change but could be merged into the upcoming v6.x version, right?

Al alternative is to use a transform to convert nulls into undefineds.

Imo the better way is to introduce useDefaultValueOnNull as converting null to undefined using a transfer requires us to hook into the object transformer.

Also, if we add such property we probably want to do better caching to avoid the extra boolean check

I'm not 100% sure I get what you mean by caching. Maybe registering different converters with null/undefined check and one with undefined only?


Fixup dracut conf (whitespaces and rd.driver.pre)

dracut warns about these, as one cannot combine this setting with others due as += is string concatenation.
rd.driver.pre is the kernel argument, but force_drivers is the dracut config (presumably)

Part of  #36


Add hide-zammy-darkness plugin

Overview
This PR adds a new plugin called hide-zammy-darkness to the plugin hub. It allows the user to hide the Zamorak Godwars Dungeon darkness overlay. This plugin was inspired by a previous OSBuddy plugin I used to use.
Legality
I referenced the rules: https://secure.runescape.com/m=news/third-party-client-guidelines?oldschool=1 and I do not believe my plugin infringes any of the game rules.

I don't think we'll want to accept this as you're meant to use Saradomin's light to dispel the darkness in zammy godwars. I'm aware other plugins hide darkness in other areas (such as around the Ver Sinhaza bank), but the darkness there does not impact gameplay the same way it would in godwars dungeon.


Assignee search doesn't find users

[ this was pasted from my clipboard from the VS Code Issue Reporter as it claimed there was too much info to post ]
Issue Type: Bug
I am trying to enter an issue in Jira.  Everything goes smoothly until I have to assign it to somebody.  First of all there isn't a "assign to me" option.  There should be.
But moreso, I click in the field and am prompted to type to search.  So I enter my own userid.  It says Loading and doesn't find me and just says Type to search again.  Assignee is required so I can't complete the issue.
Extension version: 2.1.4
VS Code version: Code 1.39.2 (6ab598523be7a800d7f3eb4d92d7ab9a66069390, 2019-10-15T15:33:40.634Z)
OS version: Linux x64 5.2.15-200.fc30.x86_64

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz (8 x 2350)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwareoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: disabled_softwareskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: unavailable_offviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
31.33GB (3.24GB free)

Process Argv
--unity-launch

Screen Reader
no

VM
0%

/needsMoreInfo Unclear what entering an issue into Jira has to do with a possible VSCode bug. If related to an extension, maybe report on the extension's support site.

As I prefixed the issue with, I tried to file this within VS Code and claimed there was too much info to post and directed me to here with a clipboard to paste into the issue.

I still don't understand how Jira fits into the picture.
Talking of pictures - can you post screenshots?

Jira is the VS Code plutin I was trying to report the issue about, using the VS Code "Help: Report Issue" feature, when it told me it couldn't post the report and instead copied it to my clipboard and opened this github issue for me to paste into.
Clearly VS Code did the wrong thing here and opened an issue against itself instead of the plugin that I was trying to report the issue against.

Clearly VS Code did the wrong thing here and opened an issue against itself instead of the plugin that I was trying to report the issue against.

Agreed. Assuming the specific plugin/extension you tried to report the issue on uses a repository other than GitHub, this problem with the VS Code issue reporter is already logged as #73515

Let's continue tracking in #73515


2FA QR code on profile should be blurred out by default to prevent accidental sharing

Is your feature request related to a problem?
It's easy to accidentally share your 2FA QR code by taking a screenshot of your member settings page. Perhaps any sensitive information should be hidden by default so that it won't be accidentally shared.
Describe the solution you'd like.
I think the 2FA QR code on members' member settings should be blurred out by default, which can be toggled via a button, switch, or some other input.
Describe alternatives you've considered.

Moving sensitive member information into a sub-page - it likely requires more work.
Adding a callout or something onto the profile page informing users that there is sensitive information on their member settings page which should not be shared with anyone.

Other
No response

reverted this again, no need to blur, the code is regenerated every time you open the settings and only actually used if verified, after that the code is never shown again


feat: add routing to GW option for sast

[X] Ready for review
[X] Linked to Jira ticket - https://snyksec.atlassian.net/browse/PUL2-801

What does this PR do?
Adding logic to route to gateway instead of the deeproxy service
Where should the reviewer start?
src/utils/httpUtils.ts
How should this be manually tested?
You can run the tests
Any background context you want to provide?
For a temporary stage where some Deeproxy changes only deployed to FedRAMP we add this logic to use the new Deeproxy arch' in the FedRAMP clusters.
When the changes are deployed to all the clusters we can use this new logic as default logic.
Screenshots
Additional questions

:tada: This PR is included in version 4.22.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


bug in android on ActivityIndicator!!

when init the ActivityIndicator  's animating atrribute to be false , it will never be show if you rerender it .
here is source code
import React, { Component } from 'react';
import {
  AppRegistry,
  StyleSheet,
  Text,
  ActivityIndicator,
  View
} from 'react-native';

export default class AwesomeProject extends Component {

constructor(){
      super()
        this.state = {
             isloading:false,
        }
    }

  render() {
    return (

      <View style={{flex:1}}>
          <Text  onPress={()=>{
            this.setState({isloading:!this.state.isloading })
          }}>
          click-isloading</Text>
          <ActivityIndicator  animating={this.state.isloading}/>
        </View>

    );
  }
}

AppRegistry.registerComponent('AwesomeProject', () => AwesomeProject);

android 6.1 ,reactnative 0.39 ，the latest version

By default the ActivityIndicator hides when it is stopped. See "hidesWhenStopped": https://facebook.github.io/react-native/docs/activityindicator.html#hideswhenstopped

yeah,but when i setstate animating :true it is still hide . if you initial false  it is always be false @johnryan

I have met similar bugs. Interesting is that this rnplay works.
you can work around it by saying {this.state.isloading && <ActivityIndicator/>}

I have same problem. Any solution?

@knapeto have you tried what I suggested?

great!!! ,thank you ,but why?

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with Canny! Check out its new home: https://react-native.canny.io/feature-requests/p/bug-in-android-on-activityindicator

I met the same problem on android device, but iphone not.
@vonovak your method is perfect.


docs: List the bug raised in case of using GitHub Desktop.

Add the recommendation in docs for not using GitHub Desktop client for
zulip code as it has a bug of keeping the symlinks disabled and ignoring
any configuration done to re-enable it resulting into failure to identify
the received symlinks leading to failing test cases in the zulip development
environment.
For reference I had submitted an issue at GitHub-Desktop at that time here

Merged as 87f7a578e6efab7594bd73ca6205c0a35c02fde5, thanks @AsociTon!  Please resubmit the upstream bug report to GitHub and post the issue number here so I can track that issue.

The issue number is #7083 .

@AsociTon https://github.com/desktop/desktop/issues/7083 has already been closed by upstream, so you will need to open a new issue following their policies.

OK, great, I'm following that issue so we should be able to track progress towards it being fixed.


Can kserve support multi-model deployment?

Can kserve support multi-model deployment like seldon-core?

For example deploy two models with two isvcs. The output of the first isvc will be passed to the second isvc.

@SeibertronSS  this is going to be supported with inference graph https://github.com/kserve/kserve/pull/1910

Thank you very much!


How to uninstall Debian Linux?

Example URL(s)
https://developers.cloudflare.com/warp-client/get-started/linux/
Actual Behavior
No
Expected Behavior
No
Additional information
The DPKG program will run automatically at every startup and cannot find the installation location

sudo apt remove cloudflare-warp

Based on the comment above, it looks like this issue appears is be resolved. I'm going to close it now, but feel free to open a new issue or ask any questions.


camerad: get embedded statistics and data by embedding in pixel data

follow up of https://github.com/commaai/openpilot/pull/24299
0 - frame id: 1638
0 - temp 0 (top): 40.15
0 - temp 1 (bottom): 39.44
1 - frame id: 1638
1 - temp 0 (top): 40.30
1 - temp 1 (bottom): 40.15
2 - frame id: 1639
2 - temp 0 (top): 40.71
2 - temp 1 (bottom): 40.57

( logMonoTime =<PHONE_NUMBER>619,
  roadCameraState = (
    frameId = 429,
    encodeId = 0,
    timestampEof =<PHONE_NUMBER>777,
    frameLength = 0,
    integLines = 221,
    globalGainDEPRECATED = 0,
    frameType = unknown,
    timestampSof =<PHONE_NUMBER>641,
    transform = [1, 0, 0, 0, 1, 0, 0, 0, 1],
    lensPos = 0,
    lensSag = 0,
    lensErr = 0,
    lensTruePos = 0,
    gain = 0.8,
    recoverState = 0,
    highConversionGain = false,
    measuredGreyFraction = 0.23046875,
    targetGreyFraction = 0.22790544,
    processingTime = 0.019059086,
    temperaturesC = [41, 40.151516],
    frameIdSensor = 431 ),
  valid = true )

Good to merge after running in the testing closet for a bit.

This CI failure real? Can we merge this?

I believe there were some issues found in the testing closet too.


split screen 1

testing on android, version 7.0, LG G6
When i open STAN in the split screen mode, it reloads every time i change the size of the split screen.
example: i was in an exercise on STAN, i changed size of the split screen, STAN showed the splash screen/ a white screen or a grey screen. after that i was back on the home screen and my exercise was closed. (see screenshots attached)

the same happened, as i wanted to drag the STAN app from split screen back to full screen. after grey loading screen it went back to home screen, exercise closed.

tested on Samsung Galaxy S6, android version 7.0
When i open STAN in the split screen mode, it only reloads when i drag the app back to full screen.


Living Wage link doesn't work

Hello! The link on index.html to living-wage.code4sa.org doesn't work. I get a 404 from github with that url. The calculator sounds like a cool project!

This has been fixed, thanks for letting us know.
We're building up a story around that link, so keep a watch on our blog.

Very cool! Looking forward to seeing it. :)


Temporarily disable ARMv7 builds

Description
Temporarily disable ARMv7 builds
This PR temporarily disables ARMv7 builds.  These builds seem to be braking based on a recent dependency change.  We'll address the broken dependency, but as an interim solution I recommend disabling the build.
Mitigates: #12258
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Comments

Note: I noticed a similar issue earlier in the day with another build locally.  I'm wondering if we might see more of these after caches expire.  It would be great if others could test local builds.

I can't reproduce this locally. Could be dirty build / ccache?

Please don't merge this, revert the commit that introduced the regression. Somebody changed dmlc_core

Please use this fix instead: https://github.com/apache/incubator-mxnet/pull/12264

@anirudh2290 @marcoabreu @nswamy @sandeep-krishnamurthy Please help merging this PR ASAP when you have time! Thanks!


[Doc]Updated load_data.py

Reference Issues/PRs
Fixes #484
What does this implement/fix? Explain your changes.
Added required docstrings.
Does your contribution introduce a new dependency? If yes, which one?
No
PR checklist

[ ] I've added myself to the list of contributors.
[x] Optionally, I've updated sktime's CODEOWNERS to receive notifications about future changes to these files.
[x] I've added unit tests and made sure they pass locally.
[x] I've added the docstrings to the file.
[x] I've updated the existing file.

Hi @Afzal-Ind, sorry for the delay, we had some CI issues, but they're all fixed now. So the PR should be good to go once all tests pass!

sorry for the delay, we had some CI issues, but they're all fixed now.

Alright then... I'm looking for new PR.

Thanks again @Afzal-Ind


really return on context done

Hi, Axel
I noticed that the comment for the function doesn't match its operation.
So, I fixed the function to work as described in the comment.

Alternatively, if that doesn't work for some reason, another possibility that might work is spawning a goroutine that waits for the context to be done and then either calls l.SetDeadline(time.Now()) or just closes it.
I think ideally there should be a test case for this, just to reproduce it and make sure the fix actually fixes it.

seems like a hack

I agree. My first implementation was dirty - did it in the night to get fast result in my task.
I tested approach with (*net.ListenConfig).Listen
It does not work as may expect - it does not finish l.Accept waiting on context.Done.
So I made new version inspired by this answer https://stackoverflow.com/a/66755998
Check if it suitable for you, or let me know how can I improve this PR

Yes, it seems this is golang/go#10527. Hm.
I don't think this is quite correct. If you call this with a context that never gets cancelled and then the Accept call fails for a different reason (e.g. the network goes down), this will leak a goroutine. Also, in general, a select with a default clause is a red flag. In this case, you don't need the quit channel, as you can use errors.Is(err, net.ErrClosed) to distinguish the case where the listener was closed.
I think the steps needed are

Use ctx, cancel := context.WithCancel(ctx); defer cancel() to get a child context that definitely gets cancelled eventually. Do that after the defer wg.Done(), so the cancellation happens before we wait on the WaitGroup. i.e. move the WaitGroup stuff to the very top of the function.
Put the goroutine that does the closing into the same WaitGroup. We want to guarantee that the listener is closed before returning. This is also why it's important to defer wg.Done() before the defer cancel().

Here are fixes you requested

Here commits with changes after review.
As for code quality, my philosophy is that if project works better after patch, then everything goes ok

Thanks again.


fields/parking: Add options to harmonize centerline tagging

~This PR is for next week when the voting was officially concluded.~ — Update: The proposal was accepted. All related documentation is updated and the manual data migration is on it's way.

Following the successful proposal https://wiki.openstreetmap.org/wiki/Proposed_features/street_parking_revision#Summary:_What_is_proposed,_changed_and_deprecated? those keys are suggested for separately mapped parking areas.

Regarding separately mapped parking areas,
parking=on_kerb, parking=half_on_kerb and parking=shoulder are proposed beside the existing parking=street_side and parking=lane to clearly distinguish different parking positions.

Since this field has autoSuggestions and customValues off they are listed all, even if not very common.

FYI @SupaplexOSM

@tyrasd I updated the PR description since the proposal was accepted. I don't see anything holding this back now, right?


Implementation of qFlex parser and additional gates

Summary
This Pull Request enhances Quac with the integration of a parser for qFlex circuits and the addition of two important gates: Hz (PhasedXPow) and FSim (Fermionic Simulation), which are used widely in qFlex circuits. The newly incorporated parser enables loading circuits directly from a qFlex txt files. An example of such a file can be found here.
Moreover, we also introduced a test set for the new parser.
Example
Here's a quick guide on how to use the newly implemented parser:
julia> using Quac

julia> temp_file_path = tempname() # Prepare a temporary file with test data
"/tmp/jl_iLiLiVet4v"

julia> open(temp_file_path, "w") do io
           write(io,
           """
           53
           0 hz_1_2 5
           0 x_1_2 6
           1 rz(0.7743385483953005) 6
           2 fsim(0.483109325847836, 0.16101107882693258) 24 34
           """)
       end
104

julia> sites = Set([5,6,14,15,16,17,24,25,26,27,28,32,33,34,35,36,37,38,39,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,61,62,63,64,65,66,67,72,73,74,75,76,83,84,85,94,6,16,15,25,17,27,24,34,26,36,28,38,33,43,35,45,37,47,39,49,42,52,44,54,46,56,48,58,51,61,53,63,55,65,57,67,62,72,64,74,66,76,73,83,75,85,84,94,6,16,15,25,17,27,24,34,26,36,28,38,33,43,35,45,37,47,39,49,42,52,44,54,46,56,48,58,51,61,53,63,55,65,57,67,62,72,64,74,66,76,73,83,75,85,84,94,6,16,15,25,17,27,24,34,26,36,28,38,33,43,35,45,37,47,39,49,42,52,44,54,46,56,48,58,51,61,53,63,55,65,57,67,62,72,64,74,66,76,73,83,75,85,84,94,5,6,14,15,16,17,24,25,26,27,28,32,33,34,35,36,37,38,39,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,61,62,63,64,65,66,67,72,73,74,75,76,83,84,85,94,5,15,14,24,16,26,25,35,27,37,32,42,34,44,36,46,38,48,41,51,43,53,45,55,47,57,52,62,54,64,56,66,63,73,65,75,74,84,5,15,14,24,16,26,25,35,27,37,32,42,34,44,36,46,38,48,41,51,43,53,45,55,47,57,52,62,54,64,56,66,63,73,65,75,74,84,5,15,14,24,16,26,25,35,27,37,32,42,34,44,36,46,38,48,41,51,43,53,45,55,47,57,52,62,54,64,56,66,63,73,65,75,74,84,5,6,14,15,16,17,24,25,26,27,28,32,33,34,35,36,37,38,39,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,61,62,63,64,65,66,67,72,73,74,75,76,83,84,85,94,5,6,14,15,16,17,25,26,27,28,32,33,34,35,36,37,38,39,41,42,43,44,45,46,47,48,50,51,52,53,54,55,56,57,61,62,63,64,65,66,72,73,74,75,83,84,5,6,14,15,16,17,25,26,27,28,32,33,34,35,36,37,38,39,41,42,43,44,45,46,47,48,50,51,52,53,54,55,56,57,61,62,63,64,65,66,72,73,74,75,83,84,5,6,14,15,16,17,25,26,27,28,32,33,34,35,36,37,38,39,41,42,43,44,45,46,47,48,50,51,52,53,54,55,56,57,61,62,63,64,65,66,72,73,74,75,83,84,5,6,14,15,16,17,24,25,26,27,28,32,33,34,35,36,37,38,39,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,61,62,63,64,65,66,67,72,73,74,75,76,83,84,85,94,15,16,24,25,26,27,33,34,35,36,37,38,42,43,44,45,46,47,48,49,51,52,53,54,55,56,57,58,62,63,64,65,66,67,73,74,75,76,84,85,15,16,24,25,26,27,33,34,35,36,37,38,42,43,44,45,46,47,48,49,51,52,53,54,55,56,57,58,62,63,64,65,66,67,73,74,75,76,84,85,15,16,24,25,26,27,33,34,35,36,37,38,42,43,44,45,46,47,48,49,51,52,53,54,55,56,57,58,62,63,64,65,66,67,73,74,75,76,84,85,5,6,14,15,16,17,24,25,26,27,28,32,33,34,35,36,37,38,39,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,61,62,63,64,65,66,67,72,73,74,75,76,83,84,85,94,5,6,14,15,16,17,25,26,27,28,32,33,34,35,36,37,38,39,41,42,43,44,45,46,47,48,50,51,52,53,54,55,56,57,61,62,63,64,65,66,72,73,74,75,83,84,5,6,14,15,16,17,25,26,27,28,32,33,34,35,36,37,38,39,41,42,43,44,45,46,47,48,50,51,52,53,54,55,56,57,61,62,63,64,65,66,72,73,74,75,83,84,5,6,14,15,16,17,25,26,27,28,32,33,34,35,36,37,38,39,41,42,43,44,45,46,47,48,50,51,52,53,54,55,56,57,61,62,63,64,65,66,72,73,74,75,83,84,5,6,14,15,16,17,24,25,26,27,28,32,33,34,35,36,37,38,39,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,61,62,63,64,65,66,67,72,73,74,75,76,83,84,85,94,15,16,24,25,26,27,33,34,35,36,37,38,42,43,44,45,46,47,48,49,51,52,53,54,55,56,57,58,62,63,64,65,66,67,73,74,75,76,84,85,15,16,24,25,26,27,33,34,35,36,37,38,42,43,44,45,46,47,48,49,51,52,53,54,55,56,57,58,62,63,64,65,66,67,73,74,75,76,84,85,15,16,24,25,26,27,33,34,35,36,37,38,42,43,44,45,46,47,48,49,51,52,53,54,55,56,57,58,62,63,64,65,66,67,73,74,75,76,84,85,5,6,14,15,16,17,24,25,26,27,28,32,33,34,35,36,37,38,39,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,61,62,63,64,65,66,67,72,73,74,75,76,83,84,85,94,6,16,15,25,17,27,24,34,26,36,28,38,33,43,35,45,37,47,39,49,42,52,44,54,46,56,48,58,51,61,53,63,55,65,57,67,62,72,64,74,66,76,73,83,75,85,84,94,6,16,15,25,17,27,24,34,26,36,28,38,33,43,35,45,37,47,39,49,42,52,44,54,46,56,48,58,51,61,53,63,55,65,57,67,62,72,64,74,66,76,73,83,75,85,84,94,6,16,15,25,17,27,24,34,26,36,28,38,33,43,35,45,37,47,39,49,42,52,44,54,46,56,48,58,51,61,53,63,55,65,57,67,62,72,64,74,66,76,73,83,75,85,84,94,5,6,14,15,16,17,24,25,26,27,28,32,33,34,35,36,37,38,39,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,61,62,63,64,65,66,67,72,73,74,75,76,83,84,85,94,5,15,14,24,16,26,25,35,27,37,32,42,34,44,36,46,38,48,41,51,43,53,45,55,47,57,52,62,54,64,56,66,63,73,65,75,74,84,5,15,14,24,16,26,25,35,27,37,32,42,34,44,36,46,38,48,41,51,43,53,45,55,47,57,52,62,54,64,56,66,63,73,65,75,74,84,5,15,14,24,16,26,25,35,27,37,32,42,34,44,36,46,38,48,41,51,43,53,45,55,47,57,52,62,54,64,56,66,63,73,65,75,74,84,5,6,14,15,16,17,24,25,26,27,28,32,33,34,35,36,37,38,39,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,61,62,63,64,65,66,67,72,73,74,75,76,83,84,85,94,6,16,15,25,17,27,24,34,26,36,28,38,33,43,35,45,37,47,39,49,42,52,44,54,46,56,48,58,51,61,53,63,55,65,57,67,62,72,64,74,66,76,73,83,75,85,84,94,6,16,15,25,17,27,24,34,26,36,28,38,33,43,35,45,37,47,39,49,42,52,44,54,46,56,48,58,51,61,53,63,55,65,57,67,62,72,64,74,66,76,73,83,75,85,84,94,6,16,15,25,17,27,24,34,26,36,28,38,33,43,35,45,37,47,39,49,42,52,44,54,46,56,48,58,51,61,53,63,55,65,57,67,62,72,64,74,66,76,73,83,75,85,84,94,5,6,14,15,16,17,24,25,26,27,28,32,33,34,35,36,37,38,39,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,61,62,63,64,65,66,67,72,73,74,75,76,83,84,85,94,5,15,14,24,16,26,25,35,27,37,32,42,34,44,36,46,38,48,41,51,43,53,45,55,47,57,52,62,54,64,56,66,63,73,65,75,74,84,5,15,14,24,16,26,25,35,27,37,32,42,34,44,36,46,38,48,41,51,43,53,45,55,47,57,52,62,54,64,56,66,63,73,65,75,74,84,5,15,14,24,16,26,25,35,27,37,32,42,34,44,36,46,38,48,41,51,43,53,45,55,47,57,52,62,54,64,56,66,63,73,65,75,74,84,5,6,14,15,16,17,24,25,26,27,28,32,33,34,35,36,37,38,39,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,61,62,63,64,65,66,67,72,73,74,75,76,83,84,85,94])
Set{Int64} with 53 elements: ...

julia> # Parse the circuit from the file
        circ = parse_qflex_circuit(temp_file_path; sites=sites)

julia> print(circ)
Circuit(#lanes=53, #gates=5)

I'm not going to merge the parser yet because I want to think more about how to integrate other QASM formats too (@HerManNav already worked on this), but this code comes handy so I'will leave the branch untouched.
However, the Hz and FSim can be merged already. @jofrevalles Could you decouple that code from here and do another PR?

However, the Hz and FSim can be merged already. @jofrevalles Could you decouple that code from here and do another PR?

Sure! Done in the PR #33

This functionality has been merged into bsc-quantic/QuacIO.jl.


Remove L -> M MTU update release note

The process of manually setting MTU values in neutron when performing a
Liberty to Mitaka upgrade is no longer valid now that OpenStack-Ansible
has automated the process. That work was pulled into the project by
35d069492eb1fcaa388d3167f89d7ffc00e1975e but the release note was
missed. This commit removes the release note now that manual
intervention is no longer required.
Connected https://github.com/rcbops/u-suk-dev/issues/529

:eyes: Preview

👍

:+1:


Fix <InputText /> types

Types for <InputText /> weren't set correctly 😓

:tada: This PR is included in version 2.7.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Automatic IP Blocking

There are a large number of requests, apparently from spammers, attempting to gain access to the server.  While these requests are being blocked and are essentially harmless, the IP addresses involved should be automatically blacklisted after x number of declined attempts.

One way would be to parse the log file to extract the IPs and block them if they reach some request limit.

That would require a cron job.  In most cases, as far as I know, a cron job wouldn't be able to stop them immediately.
I was thinking about logging IP's and login failures in the database, and then after so many failure attempts they are blocked for a certain amount of time.  After being blocked xx times, they go on a black list from which they can not be removed without contacting you.
You may also want an email each time one of these actions occur.
And perhaps we should also implement the Google Captcha?

I was assuming that you would implement Captcha for the registration process. Note that spammers sometimes have people working low wage to solve captchas on forums. Since after the users get in, they can spam away. Annoying.

Yes, both for registration and login.  And of course we'd be able to access the blacklist from the back-end admin site.

We now have IP blacklisting (currently for Russia and China, but IPs can be added via the admin portal).  We now have Google Captcha on Signup and Login.  Last but not least, we have the random question & answer on signup.
Unless anyone objects, I'm going to go ahead and close this issue.

I think leave the login working, but disable user creation for these semi-blacklisted countries. Basically, they try to make a bunch of users, and we don't wanna deal with these. However, I have made some users manually for some people, and they should be able to login from Russia and China.


completion: support promises

This fixes #278
I had to rework the helper to support async tests since promises defer things to the next tick, and since I have to use nextTick as to not swallow any fatal errors and just never report them.
A promise polyfill is included as a **dev-**dependency and is used during the tests.

@LinusU this looks solid, I'll look a bit closer tonight when I'm not at work.

LGTM :+1: Thanks, @LinusU!

No problems, happy to help!

@LinusU your work is published to yargs' next release candidate, give it a shot:
npm install yargs@next
Assuming we don't run into any issues, I'll promote the release tomorrow.

Super! Thanks \o/


use request id from server

Had to use useEffect to call navigate() in order to circumvent React useState hook's asynchronous nature. Attempting to solve with async/await and Promises did not resolve the failure to update requestId before the call to navigate.


Test SONAR_TOKEN_AS

:tada: This PR is included in version 3.11.0-next.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Ice web

Now every time I startup the ice web repulse is glitched out and it responds, even tho repulse disabled is crossed. I usually fix it with turning “disable repulse” off and on again.
Could you please fix this

Its problem of both wallpaper and the application.
Use this attached zip. I have disabled the click in JavaScript.
In Wallpaper engine, click on Open from a file -> select the index.html.
I will re-write this wallpaper later or next month.
Ice Web No Click.zip

@SharpShadowFTW  did you tried the attached wallpaper ?

Yes I did and it worked exactly as I wanted to
Thanks
SharpShadow
Op do 13 sep. 2018 om 13:44 schreef Vikas Kapadiya<EMAIL_ADDRESS>

@SharpShadowFTW https://github.com/SharpShadowFTW did you tried the
attached wallpaper ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/vikas5914/Ice-web/issues/2#issuecomment-420978166,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ao_SIwbYD7HtzGazTZvxeha3jp8OwW65ks5uakUvgaJpZM4WhoxH
.


Add min price line to price history chart

The average price line is solid (as previously), and the new minimum price line is dashed.
Previously, the price line would be red or green depending on if the price had gone down or up in the last two days. This changes it so that each line are either red or green depending on if the average or minimum price has gone up or down from the start of the graph to the end of the graph.
Also makes the minimum for the chart dynamic to show a better range for items with a higher price floor:

.deploy


Add support for specifying package dependencies

It would be nice if there was a way to specify package dependencies.
For example, a .NET app could depend on postgresql-server package. And when the rpm gets installed, the dependencies get installed as well.
Can framework-dependent .NET apps be packaged?
If so, this can be used to add a dependency like: dotnet-runtime-6.0.
cc @xoofx

Can framework-dependent .NET apps be packaged?

So, currently, nope. The focus was to provide a way to easily publish x-plat app including Windows that doesn't have any package manager at the level of what deb/rpm are providing, so hence why it is supporting only single file app and it is specifying the RID (RuntimeIdentifier) when compiling the app.
As you mention, the problem is that framework dependent apps could only work for e.g debian or rpm, so that limits the usability - but definitely fine for such platforms.

It would be nice if there was a way to specify package dependencies.

That case should be possible for deb/rpm packages without much changing the way dotnet-releaser is working. Let me check.

It would be nice if there was a way to specify package dependencies.

This should be fixed by commit 00e9cbe and part of 0.1.10+
A package dependency can be added to the configuration file like this:
[[deb.depends]]
name = "your-runtime-dependency"

For creating apps with .NET framework dependency, I will postpone it for now. Let's see if there are more demands for such a scenario.

Thank you!

For creating apps with .NET framework dependency, I will postpone it for now. Let's see if there are more demands for such a scenario.

The main benefit is that you don't need to rebuild your app for .NET patch releases.
I wouldn't mind taking a shot at it.

The main benefit is that you don't need to rebuild your app for .NET patch releases.

Yeah, I understand the use case, when you are ok that it requires to install a .NET runtime machine wide, but it's a deal breaker for anyone outside the .NET ecosystem. One reason why Go has been so popular for writing apps. One reason why I made this project, to allow to more easily target multiple platforms without having a dependency to a .NET runtime.

I wouldn't mind taking a shot at it.

Yep, PR welcome if you want to push for such an option.
The case of "creating a cross platform framework dependent" via dotnet publish alone might require some tweaks around in the current code base, as you would not have anymore the concept of RID, and the code currently is assuming that it is setup.
Hope it will not complicate to much existing code path but you will see...


samples_num_alt_1 not exists in the elastic search index

I used v0.1 version of load_dataset_to_es to load the VCF into Elastic Search. seqr expects a filed "samples_num_alt_1" which doesn't exist in the index schema while I tried to add a dataset into seqr via web interface. But I couldn't find this specific filed in the _mapping/variant. I do see sample_id_num_alt, e.g. S00001_CIDR_num_alt. I have the most updated codes on hail-elasticsearch-pipelines. Could you point me out what I might miss? Thanks!

We have upgraded seqr to use the latest version of the pipeline output, which requires you to use the flags --use-nested-objects-for-vep --use-nested-objects-for-genotypes when initially running the pipeline

Thanks, @hanars . I must hear those two parameters before, but couldn't figure out where they were. Now I re-run the scripts and see I can make it work to the end. Just curious if this meta data is always expected? and if so,  why it is optional? Sorry that I am asking this kind of question without going through much details into the codes.

It is always expected, and its optional because these scripts are old and badly maintained, and we are in the process of completely rewriting them

Yes, it is working now. @hanars, thanks for your time and heads up as well. I will close this ticket now.


Make use of Flux.Optimise.AbstractOptimiser

Use Flux' abstract optimizer type instead of the Union.
By doing so, users can also use their own custom Flux optimizer.

Unrelated failure.


Fix office room layout

Fix some layout bugs

Spacing between users.
Modal meeting title.
Rooms disposition

Fix: 75


Fix redhat import failure

This fixes #398.
This PR is mainly comprises of following two commits.

requests_with_5xx_retry: Retry on 5xx errors
Introduced and used a helper function for retries on 5xx errors. This is
important and some servers like bugzilla.redhat.com return 502 Proxy Error
which was the cause of #398
A ticket has been raised in RedHat here https://redhat.service-now.com/help?id=rh_ticket&table=sc_req_item&sys_id=278239541b1ba010477e43fccd4bcb4a
Here is the response from<EMAIL_ADDRESS>
Yes, just back off a bit and retry when this happens. It's been a long-term issue and we're working on a way to address it but it will still take time. There's also a time-out on individual queries - if you're hitting that sometimes on other requests then you'll need to optimise them or break them up into smaller ones

Not all RHSA errata have a CVRF document
This is mentioned in the NOTE of "2.1 List all CVRFs" of
https://access.redhat.com/documentation/en-us/red_hat_security_data_api/1.0/html/red_hat_security_data_api/cvrf
Such a case would lead to a crash before this commit.
Eg: https://access.redhat.com/hydra/rest/securitydata/cvrf/RHSA-2005:835.json
No cvrfdoc would be found in the statement
value = rhsa_data["cvrfdoc"]["aggregate_severity"]

@sbs2001 Perhaps we would be able to revert back after redhat fixes the problem on their side. Until then, this is what we got.


ms-photos:viewer?fileName uri scheme not working

Win 10 Home 1903 18362.836
Microsoft Photos 2020.19111.24110.0
Running ms-photos:viewer?fileName=c:\users\userName\Pictures\image.jpg opens the photos app but doesnt show the photo. It seems the fileName parameter is ignored. App is opened in some "collections" setion.
Is there any uri scheme for opening video from web (http://.../video.mp4)?

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

ID: ae2608d3-38b8-2404-d138-1ba17772e72c
Version Independent ID: 535d38b3-3174-fc77-ec58-7b5732ba803c
Content: Launch the default app for a URI - UWP applications
Content Source: windows-apps-src/launch-resume/launch-default-app.md
Product: uwp
Technology: processes-and-threading
GitHub Login: @lastnameholiu
Microsoft Alias: alholiu

Thanks for filing this issue @jozefchutka. Could you submit this to our Microsoft Q&A platform? The community of Microsoft experts and engineers over there could have a better answer to your issue. Though, if you suspect this to be a product bug, you could file this through Microsoft Support. A support engineer will look at the repro and see whether the issue is a Microsoft product bug, or something else. If it's a bug with a Microsoft product then the ticket will be free of charge.
If you receive assistance via any support resource, and you believe that information would help us improve the docs, then please come back and let us know.

Hi @lastnameholiu , I tired posting the same on Q&A however after submission it showed WAF v2 has determined your request exceeded the normal web request and has blocked your request.
I do not know if this is product bug or not, resolve the attribute on your side.
Free of charge? Yes, thanks for letting me submit bug on your software free of charge.
At this point, I believe I did enough to report the bug in MS software. If you need please resubmit into any other system you like.

If any new actionable items arise, let us know either through a new Issue or directly on this thread. In the meantime, I'll be closing this Issue. Thanks once again for submitting your feedback.

Three years later and the docs are either still wrong or the scheme still doesn't work?

It seems like it. It says 10/21/2022 on the site, so I presume it's not meant to be outdated. But it just doesn't work as described.

4 years later，it's always error

@hkhmsft closed this issue in 2020. Noone in Microsoft is interested or looking into it. You might want to create a new one.


Detect null values in schemas

In src/mongo/services/schemaService.ts:
private functions setSchemaForDocument and setSchemaForDocumentProperty both
make decisions based on the type of the passed value/document
being an object.
Unfortunately, in javascript,
typeof null === 'object'

As a result, if a property or an array value has a value of null,
setSchemaForDocument will throw an error when calling Object.keys(document)

@PrashanthCorp, @nturinski can one of you handle this?
@jimmcnulty41 Can you provide a set of repro steps we can add to our test cases?  Thx.

Reproduction Steps:

Create a new mongoDB collection (e.g. 'cubits')
execute the following query:

db.cubits.insert({
  blah: "cubits",
  blahBlah: [
    null,
    "cubits",
    null,
    "cubits",
    null
  ]
})

Start typing a find query in a mongo scrapbook (in the following, the pipe character represents the cursor position)

db.cubits.find({
  |
})

Trigger auto-complete/intellisense (using ctrl+space)

Expected:
Intellisense provides options based on the property names found in the documents
Observed:

Error appears in debug console (see below)
No intellisense options are provided

[Error - 1:31:35 PM] (node:61942) UnhandledPromiseRejectionWarning: TypeError: Cannot convert undefined or null to object
    at Function.keys (<anonymous>)
    at SchemaService.setSchemaForDocument (/Users/jim/.vscode/extensions/ms-azuretools.vscode-cosmosdb-0.10.2/dist/mongo-languageServer.bundle.js:37:17322)
    at SchemaService.setSchemaForDocumentProperty (/Users/jim/.vscode/extensions/ms-azuretools.vscode-cosmosdb-0.10.2/dist/mongo-languageServer.bundle.js:37:17664)
    at SchemaService.setSchemaForDocument (/Users/jim/.vscode/extensions/ms-azuretools.vscode-cosmosdb-0.10.2/dist/mongo-languageServer.bundle.js:37:17365)
    at module.exports.1224.t.SchemaService._resolveQueryCollectionSchema.Promise.readNext.r (/Users/jim/.vscode/extensions/ms-azuretools.vscode-cosmosdb-0.10.2/dist/mongo-languageServer.bundle.js:37:16840)
    at module.exports.1224.t.SchemaService.readNext.e.length.t.hasNext.then.o (/Users/jim/.vscode/extensions/ms-azuretools.vscode-cosmosdb-0.10.2/dist/mongo-languageServer.bundle.js:37:29461)
    at process._tickCallback (internal/process/next_tick.js:68:7)
[Error - 1:31:35 PM] (node:61942) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
[Error - 1:31:35 PM] (node:61942) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

ping @PrashanthCorp, @nturinski

Bump

I'll look into it today.

Updated, moving 'getMongoDocumentType' into separate function

bump?

The build seems to have failed, but azure devops can't find the build. I'll look into this later today.

These changes look good to me.  Because so much time has elapsed, I'll have to merge this without the build passing, but I don't think the failure was ever related to these changes to begin with.
Thanks for your patience in this PR, @jimmcnulty41 and we appreciate your contribution! 👍


No alert when a client connects to wifi and then disconnects before the next interval

No alert when a client connects to wifi and then disconnects before the next interval - I will never know that someone connected and then left.

@iptvcld This behavior is expected since the app polls based on the interval set by the CHECK_INTERVAL parameter. You can reduce the interval time to make the polling closer to real-time, but unfortunately, there is no real-time webhook available for immediate notifications when a client connects.

@ZSamuels28 Hmm ok thanks, I have pfsense as my router and have even tried looking something for that to notify me as soon as a new device gets a IP. But nothing really good I can find. Arpwatch is not the best. Then I geared towards UniFi as I am using that for my switches and AP but seems like with UniFi it will always a pooling effect instead of an instant trigger based on an action.

If I adjust the interval to 5 seconds, what do you think the impacts that can cause for the UniFi controller
Also is there a way to report on disconnected devices (offline) new devices? So that way if a device did come online between the interval and then disconnected from the network, that device still should be in the not action section in UniFi. And it would be neat for this package to be able to report on those as well

Changing the check interval from 60 to 5 seconds means your UniFi controller will handle 12 times more requests, but I'm not sure if it will have any impact on performance—it depends on your hardware and network. You would want to keep an eye on it and see if there is any impact. Perhaps putting a question into the Unifi community and see what they say as well about this.
As for disconnected devices, I'd need to check if there is an API that captures all devices including those that aren't connected.

Grabbing the new disconnected devices would be neat as then it would capture those events that connect and drop before the next interval even if it’s set at 5 mins. The notification can read a new device was discovered but is offline now. And being the home lab user, I can investigate to see what that device was.

@iptvcld so I did some tested and found that this will pull all clients within a certain amount of time. The endpoint stat_allusers pulls all clients connected within a certain timeframe, for example, here is an instance that pulls clients connected within the last 24 hours.
I would need to add a parameter to instead use stat_allusers(CHECK_INTERVAL) instead of list_clients. The issue with this is that stat_allusers interval is only by hours, so I would need to pull all clients from the last hour, then filter on them for the last CHECK_INTERVAL seconds. Let me know your thoughts.
`<?php
require_once(DIR . '/Unifi-API-client/Client.php');
require_once(DIR . '/Unifi-API-client/config.php');
function createUnifiClient($controlleruser, $controllerpassword, $controllerurl, $site_id) {
$unifiClient = new UniFi_API\Client($controlleruser, $controllerpassword, $controllerurl, $site_id);
$loginResult = $unifiClient->login();
if (!$loginResult) {
throw new Exception('Failed to log in to UniFi Controller');
}
return $unifiClient;
}
function getAllClients($unifiClient) {
// Fetch clients that were online within the last 24 hours
$clients = $unifiClient->stat_allusers(24);
if ($clients === false) {
throw new Exception('Failed to retrieve users from the UniFi Controller.');
}
return $clients;
}
try {
$unifiClient = createUnifiClient($controlleruser, $controllerpassword, $controllerurl, $site_id);
$all_clients = getAllClients($unifiClient);
if (empty($all_clients)) {
    echo "No client devices found within the last 24 hours.\n";
} else {
    echo "All client devices within the last 24 hours:\n";
    foreach ($all_clients as $client) {
        echo json_encode($client, JSON_PRETTY_PRINT) . "\n";
    }
}

$unifiClient->logout();

} catch (Exception $e) {
echo "An error occurred: " . $e->getMessage() . "\n";
}
?>`

Thanks for your time on this, I am actually up at this moment trying to find something that will work as well!
From what you have explained it seems to make sense, let’s say my check interval is ever 5 mins. So your new check would also check in the last hour if there was someone connected and in the offline state which is great and then on my next interval I would get a telegram or something that will alert me saying mac, etc was online within the last hour.
Is there a way to get telegram alerts by the way for all this? Thanks again.

I would think to do something like, if the interval is 5 minutes, check all clients and then check clients in the last hour and filter by first seen (or maybe last seen, I'd need to think through this) <= 5 mins. Then take any new MAC addresses from there as well.
I would add this as a parameter and then it would be added to the app to notify via telegram or the other services.

Thank you!! Excited to try it out!!


Feature proposal: export(), import() and deepCompare()

This PR introduces two new concepts that we find essential and that we have implemented in our fork:
export()
After we save a model to MongoDB, we like to put a copy of it into other databases, caches and queues. By calling DocumentManager::export(), a plain associative array is returned.
import()
When we load a model from a cache, we might start with an associative array that was originally created with the above mentioned export() function. By calling DocumentManager::import(), a plain associative array is converted into the exact state that the models were in before we called export().
deepCompare()
When we load an item from an "alternate" source such as a database or a cache, we like to sometimes do a comparison against what is in the cache to determine if the the copy of the data was accurate. The "deepCompare()" function makes this possible.

@blockjon nice! I had something similar on my list which at least partially resembles what you've done here so I hope we'll come to an agreement :)
My idea was to extract ChangeSetCalculator from UnitOfWork to a separate class and let it have 2 methods:

calculate($document) (this probably will have UnitOfWork as well)
getActualData($document)

and my number 2 seems to be your export(). I wanted to do so to make our UnitOfWork a friendlier place, eventually allow rolling own calculator which getActualData would work in more efficient way than reflections and apparently could fit your use case here as well. Reason I'm leaning towards having this utility in UoW instead of in DocumentManager is not cluttering public API and not adding methods that are not in an interface there.
Thoughts? :)

@malarzm It has come to my attention that we would also really want an option to not only export() to an array, but to also subsequently call some kind of import() which would re-build our Models into that exact same state. Can you please comment on this?

As for the location the DocumentManager is the public place where callers can invoke and things are fairly easy to understand. UnitOfWork is the black magic of the ODM and I've tried to avoid that where possible because things get very confusing very quickly in there.

subsequently call some kind of import() which would re-build our Models into that exact same state.

This is exactly what Hydrators are for :) You can get to them, again, from UnitOfWork - this method is getting or creating documents (which you could utilize if document to be imported is not managed) or in case it would be this else block will show you how to create document using Hydrators - later you could probably merge newly created document.

UnitOfWork is the black magic of the ODM

Sadly this is true hence my intention of breaking it up a little :)


Bonobo

Geez, I didn't pay attention to this PR - sorry.  You can provide a reference for where this address came from?  I need to verify each entry that goes into this list.   Thanks.


Allow for unlabeled charts along side labeled charts

Hello, first of all, thanks for making this repository available since the original one is outdated. A minor issue with the labeling is that they are enforced in every chart, which make it difficult for a page to have both labeled and unlabeled charts. It would be a good idea to check for the options if the labels tag is available or not before going to the process. I've made the changes in a local repository, I am going to create a pull request if you think it should be added.
Thanks,
Yousef Altaher

Any PR is welcome

Can you please show me before/after examples or screenshots? Thanks for the PR

Of course, here is before/after image from a page that implemented the file

s


Bumping AWS provider version to ~> 3.0.0

what

Bumping our AWS provider to version 3
Bumping terraform-aws-vpc version to latest in examples

why

Allows us to take advantage of some newer Terraform features when deploying EKS
We need this to be in line with terraform-aws-eks-node-group, which will provide us with the ability to specify custom launch templates via aws_eks_node_group (for custom EC2 tagging)

references
https://github.com/aws/containers-roadmap/issues/585

/test all

We're going to include this work in a different PR so I'm going to close for now.


Unable to compile docs due to error

I am trying to compile docs to resolve an issue with routing tree webtool.
make compile crashed trying to do git reset inside alertmanager/release-0.19 folder
Part of crash log
error: Sparse checkout leaves no entry on working directory
fatal: Could not reset index file to revision 'HEAD'.

Captain! We’ve been hit!

RuntimeError: Running command 'cd /mnt/d/IdeaProjects/docs/tmp/repo_docs/alertmanager/release-0.19 && git reset --hard --quiet && git clean --force' failed

When I go to folder alertmanager/release-0.19 it is empty.
Manually invoking git reset --hard --quite gives the error as in above.
Other folders have docs folder inside and I can successfully do git reset on them.
UPD:
Problem appears on Windows 11 and maybe reproducible on Windows 10
I repeat all the steps on ubuntu without any issues

@Evreke How did you manage to build it on Ubuntu, mine is failing. I believe the cause is that alert manager release-0.19 directory seems to be empty.

@KirubelT I just followed instructions

I meet this the same matter, and you how to reolve it?