fix: fix broken permissions

Fix broken import path
Rename DefaultPermissionSet to SimplePermissionSet
Fix example app

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


detected as trojan

windows defender detect it  as Trojan: Win32/Fethar.B!cl when i lauch it. worked great until now, probably because of last update.

Cant' reproduce - https://virustotal.com/pl/file/714915fd039b08cfdf43070c3f8ccce6107cc2ea30e87ebe694344fe0857ddbc/analysis/1465508528/

Check if ASF.exe binary from https://github.com/JustArchi/ArchiSteamFarm/releases/tag/<IP_ADDRESS> works for you, as I can't reproduce the issue. If it does, I'll release it as next stable release.

it works thanks

Sigh... I think I'll need to start looking elsewhere as ILRepack is more troublesome than expected, thanks.


SamlResponse signature SHA256-RSA validation fails with unexpected signature length

Steps to produce:

IDP metadata contains two IDP X509 certificates with different RSA key lengths 2048 vs. 3072 bits because certificate transition is about to happen in future. Signature algorithm is SHA256-RSA.
Use onelogin.saml2.idp.x509certMulti property to configure both certificates.
Process SAML login redirect using com.onelogin.saml2.Auth.processResponse()
Authentication response validation fails while comparing XML signature using the 3072 bit key. The error stack trace contains the message:
Signature length not correct: got 256 but was expecting 384
Second X.509 certificate is never checked against received XML signature.

Expected behaviour:

Signature validation should continue past the first signature verification failure using 3072 bit key.
Second IDP X.509 certificate validation should succeed with 2048 bit key.

Wrong signature length exception is an expected condition due to transitioning to longer RSA key length.
Full stacktrace:
com.onelogin.saml2.util.Util - Error executing validateSignNode: Signature length not correct: got 256 but was expecting 384
org.apache.xml.security.signature.XMLSignatureException: Signature length not correct: got 256 but was expecting 384
	at org.apache.xml.security.algorithms.implementations.SignatureBaseRSA.engineVerify(SignatureBaseRSA.java:92)
	at org.apache.xml.security.algorithms.SignatureAlgorithm.verify(SignatureAlgorithm.java:301)
	at org.apache.xml.security.signature.XMLSignature.checkSignatureValue(XMLSignature.java:760)
	at org.apache.xml.security.signature.XMLSignature.checkSignatureValue(XMLSignature.java:697)
	at com.onelogin.saml2.util.Util.validateSignNode(Util.java:1010)
	at com.onelogin.saml2.util.Util.validateSign(Util.java:931)
	at com.onelogin.saml2.authn.SamlResponse.isValid(SamlResponse.java:301)
	at com.onelogin.saml2.Auth.processResponse(Auth.java:640)
	at com.onelogin.saml2.Auth.processResponse(Auth.java:673)

Thanks for reporting that, do you have a PR to solve this?

@kherrala Do you use Dynamic Settings to configure your SAMLSettings? if so, when configuring IDP_X509CERTMULTI_PROPERTY_KEY you need this line of code to put your certs into it:
```
// OneLogin uses onelogin.saml2.idp.x509certMulti.(index) to lookup the additional IdP certificates.
samlData.put(IDP_X509CERTMULTI_PROPERTY_KEY + "." + (i - 1), idpCerts.get(i));
Then your second cert could be looked up.

@sunkaiqin Thank you and sorry for the false alarm! I am using dynamic properties and it seems I was just concatenating certs using the comma-separator because that is how all other list-valued properties work.
Somehow I was distracted by the stack trace printed by Util.validateSignNode() exception handler. Maybe only the expected
org.apache.xml.security.signature.XMLSignatureException validation failure should be caught and logged without stack trace?


.NET SDK Not Listed on Docs

I have spent some time trying to get generators to build classes to work with your OpenAPI spec, and learning they are far from perfect.
Would you please list https://github.com/blockfrost/blockfrost-dotnet on your official docs, so others can avoid messing around with tools they don't need?
Thank you!

 Thanks for letting us know it's missing and sorry for the inconvenience this have caused you.

No worries, thanks for the quick reply!


SampleGen: generate comments on fields of request objects

Configuration:

- parameters:
  - defaults:
    ...
  - attributes:
    - parameter: some_parameter
      description: "some comments on the parameter"
    - parameter: another_parameter
      description: "this comment goes to sample function documentation"
      sample_argument_name: other_param

Comments on resource name entities are not supported, since they are currently inlined. We can fix this when we start working on generating inline parameters.
Also correctly generates default lines in Ruby.

PTAL @googleapis/samplegen

@vchudnov-g PTAL


Crash in the title interface

Seems to be random
Sorry, I can only provide logs
Crash_2022_12_10_17-6-40.txt
Crash_2022_12_12_0-9-58.txt
Crash_2022_12_13_11-33-31.txt

That error should be fixed in the upcoming build as I think it was due to CoInitialize which I use for IShellItem2 to retrieve other mods dll information either way I've placed a failsafe around it.
It might be a Discord issue which can randomly crash IC at startup then it is fine. I reported an issue with discord over 2yrs ago so if it is on discords end it won't ever get fixed! Fun fact: if you have the menu loaded as overlay discord injects into that instead of the game.


powerplatform-vscode Localization hand-back [CTAS - RunID=20240822-174718-dfm31bbc93]

Translation handback check-in (PR Created by automation).

https://github.com/microsoft/powerplatform-vscode/pull/1035/files


Dotnet template

The first time I used Fulma was by adding it to an existing Fable project. As I had no prior knowledge of Node.js or Webpack, I couldn't understand why nothing worked when I simply added Fulma to the client project and added Bulma to the package.json. After a long trial and error process, I imported the Bulma file to the project and told Webpack to use loaders for the sass file, then everything was in place.
It would be nice to have a simple template with everything Node related configured so everyone can use it out of the box without having to delete unneeded stuff from existing projects.

A template, has been created under the SAFE-Stack, I will close this issue as the template should fix your problem :)

That template has no loaders for sass, also it loads the Bulma from a CDN instead of bundling it. The problem is still there, having to reconfigure everything when using the extensions.
Not really a issue, but that template also has stuff for the server when sometimes just the client is needed.

I finally took the time to create the template. You can find the documentation here


O cannot change my password

Subject: O cannot change my password
Description:
Try to change the password
Results:
O don’t receive the email to change my password
Backend version: develop-64e6cf65
Frontend version: develop-6d22ac7f
User Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 16_0 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) CriOS/115.0.5790.130 Mobile/15E148 Safari/604.1
Page: https://couchers.org/password-reset
User:

#4058


SharedLibraryException handling

SharedLibraryException handling per https://github.com/CppMicroServices/rfcs/pull/9

Thanks for your thorough reviews, Jeff and Mike!
If there aren't any additional feedback by tomorrow (Friday 4/24) afternoon, I'll merge the changes into development by EOD Friday!


readme

Please, fix the readme description.
You write: "ArrayList subtitles = SRTReader.getSubtitlesFromFile(path, keepNewLinesEscaped);"
correct "ArrayList subtitles = SRTParser.getSubtitlesFromFile(path, keepNewLinesEscaped);"

@SaaStudio I am gonna write a better README file, and will be soon adding some more instructions in my website.


[Table]  Create & Save views

Internal issue 167
Is this an extension to an existing component, pattern, or a brand new asset?
This is an EDS item.
What is the rationale for this contribution.
In certain situations, a user may need to make use of the same resource table for a number of different purposes, which would benefit from different configurations of things like sorting, columns and filters.
This contribution covers the ability to save a particular configuration as a 'view' and later change between saved views.
Detail the intended behavior

The default table gains a dropdown to the left of the toolbar.

This dropdown is by default 'default view', when a user makes changes to the tables configuration, this changes to 'unsaved view'

Once a custom view is created through changing table settings. The user can open the settings (disregard incorrect icon usage - should be from settings gear) overflow and choose to 'save view'
Image:

This will prompt a small dialog to provide a name and description to the custom view and if it should be the view selected by default when the table first loads.
Image:

Completing this form will save the view as something selectable in the aforementioned dropdown.
Image:

Also in the dropdown of view selection: default view, any saved views and a 'manage views' action.
image:

The manage views action will pop a modal with a simple table of views that can be edited (name/description/default?) or deleted.
Image: Not provided.

Adding some clarifications on behavior after discussion with @bjornalm today:

When should the “Save new view” should be available?

When a users current configuration of the table is different from the last selection made in the view picker. Eg: making any configuration changes from the 'default' setup of the table in a fresh instance, and after they select 'view X/Y/Z' and then make a change. In other words, the only time it isn't available is when they haven't changed any of the things that form the view (filters, sorts etc) from what we loaded in for them.
Note: I spotted now looking at the contributed designs that this is missing, but whenever the 'save new view' option is available based on the above, there should also be an action to 'save changes'. Which would update the currently selected view to be whatever the current state of the table is, instead of creating a new one with the current state.

How is the “edit view” stuff expected to work?

In reference to the edit action from the saved views dialog. In this case, it opens the dialog that is triggered when a new view is saved (basically just with its name as an input), so the user can rename the view itself. Editing of the actual content of the view will happen using the note above - select view from dropdown, make changes, click save changes.

Moving to sprint 53 since @bjornalm is out this week.

Imagine the following scenario:
A table initially has 10 columns without any width specified but with hasResize active. Upon the initial rendering the 10 columns are rendered by the browser and the width of each column gets measured and each column thereafter gets an internal width property which also is applied using CSS. At this stage, the table "knows" about the width of each visible column and that is needed for the column resize to work. However, the column prop has not changed and still does not specify any widths for the columns.
Now, a new column X is added (appended to the columns prop and ordering prop) and it has a specified width of 500px. The table will try to make room for the new column by shrinking the other columns. The table will not shrink any columns below the specified MIN_WIDTH and if there is not enough horizontal space the table will grow wider to fit the new column. In this case the initial columns are shrunk into MIN_WIDTH but the table still has to grow wider to fit column X. Now, yet a new column Y is added and it also has a specified width of 500px. The initial 10 columns stay at MIN_WIDTH and column X will shrink to MIN_WIDTH to make room for column Y.
At this point there is a potential conflict. The columns prop specifies that the first 10 columns don't have a width and that X and Y both have a width of '500px', but the table has resized the x column to MIN_WIDTH. If the user saves the view, the current columns prop will be used, and when this view is later loaded into a table it will render the first 10 columns (that still don't have a width defined) using MIN_WIDTH and let both X and Y be 500px as specified. Hence, the view that was rendered during save will differ from the loaded one.
Possible remedies:
a) The table will never shrink columns that have a predefined width, only columns with an undefined width, when new ones are added (or toggled for visibility).
b) The table will never shrink any existing columns when new ones are added (or toggled for visibility) and the table always grows in width.
c) trigger the onColumnResize when the table automatically resizes the table columns as part of the add/remove column operation so that the application will have the latest version of the column widths when a view is saved.
d) We refresh the column props somehow (by force triggering the onColumnResize) before a view save

@tay1orjones @davidicus Is there a decision on what parts of the view that should/needs to be saved?
Some properties like view.filters, view.table.sort and view.table.ordering seem obvious. The columns prop also needs to be considered since they contain the column widths. But then there are properties like  view.table.filteredData that could potentially be the complete dataset...

Imagine the following scenario:
A table initially has 10 columns without any width specified but with hasResize active. Upon the initial rendering the 10 columns are rendered by the browser and the width of each column gets measured and each column thereafter gets an internal width property which also is applied using CSS. At this stage, the table "knows" about the width of each visible column and that is needed for the column resize to work. However, the column prop has not changed and still does not specify any widths for the columns.
Now, a new column X is added (appended to the columns prop and ordering prop) and it has a specified width of 500px. The table will try to make room for the new column by shrinking the other columns. The table will not shrink any columns below the specified MIN_WIDTH and if there is not enough horizontal space the table will grow wider to fit the new column. In this case the initial columns are shrunk into MIN_WIDTH but the table still has to grow wider to fit column X. Now, yet a new column Y is added and it also has a specified width of 500px. The initial 10 columns stay at MIN_WIDTH and column X will shrink to MIN_WIDTH to make room for column Y.
At this point there is a potential conflict. The columns prop specifies that the first 10 columns don't have a width and that X and Y both have a width of '500px', but the table has resized the x column to MIN_WIDTH. If the user saves the view, the current columns prop will be used, and when this view is later loaded into a table it will render the first 10 columns (that still don't have a width defined) using MIN_WIDTH and let both X and Y be 500px as specified. Hence, the view that was rendered during save will differ from the loaded one.
Possible remedies:
a) The table will never shrink columns that have a predefined width, only columns with an undefined width, when new ones are added (or toggled for visibility).
b) The table will never shrink any existing columns when new ones are added (or toggled for visibility) and the table always grows in width.
c) trigger the onColumnResize when the table automatically resizes the table columns as part of the add/remove column operation so that the application will have the latest version of the column widths when a view is saved.
d) We refresh the column props somehow (by force triggering the onColumnResize) before a view save

I would think that a is the best option. If a column has a specified width I think we should try to respect that. Any column that does not have a specified width can be shrunk down to the min width but those that are specified will make the table grow to accommodate if there is not enough room.

@tay1orjones @davidicus Is there a decision on what parts of the view that should/needs to be saved?
Some properties like view.filters, view.table.sort and view.table.ordering seem obvious. The columns prop also needs to be considered since they contain the column widths. But then there are properties like view.table.filteredData that could potentially be the complete dataset...

@lukefirth @dianatran18 is there any guidance on this from the product teams? The easy answer would be to store whatever props need to be saved in order to get the same view loaded that is separate from the data. This would think this excludes the filteredData prop since that is a result of the applied filters. Plus that data may have changed since they saved and would like the same "view" to be applied to the updated data set.

@tay1orjones @davidicus Is there a decision on what parts of the view that should/needs to be saved?
Some properties like view.filters, view.table.sort and view.table.ordering seem obvious. The columns prop also needs to be considered since they contain the column widths. But then there are properties like view.table.filteredData that could potentially be the complete dataset...

@lukefirth @dianatran18 is there any guidance on this from the product teams? The easy answer would be to store whatever props need to be saved in order to get the same view loaded that is separate from the data. This would excludes the filteredData prop since that is a result of the applied filters. Plus that data may have changed since they saved and would like the same "view" to be applied to the updated data set.

Perhaps we can export everything and let the app decide what they want to use. In our Storybook example we can use filters, ordering, activeBar and search and ignore the rest.

@tay1orjones @davidicus Is there a decision on what parts of the view that should/needs to be saved?
Some properties like view.filters, view.table.sort and view.table.ordering seem obvious. The columns prop also needs to be considered since they contain the column widths. But then there are properties like view.table.filteredData that could potentially be the complete dataset...

@lukefirth @dianatran18 is there any guidance on this from the product teams? The easy answer would be to store whatever props need to be saved in order to get the same view loaded that is separate from the data. This would excludes the filteredData prop since that is a result of the applied filters. Plus that data may have changed since they saved and would like the same "view" to be applied to the updated data set.

I'll let @lukefirth answer for the product team requirements, but from my perspective I would agree with you David, and I would save whatever needs to be saved in order to achieve the same view I had just customized.

:tada: This issue has been resolved in version 2.118.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add Benchmarks for Singleton

Wanted to see what each method costs to try to determine the best one to use in specific situations.
Build the project in Release and run the Console application selecting the Benchmark to run.
 Surprisingly though Locking and Better locking allocate more (perhaps because of the lockpad initialization?). LazyOfT performed the best in both mean time and allocations and should be the recommended method of locking - supporting the conclusions in your course.

Thanks, that's good to hear!
Do you want to put your results in a README.md in the Singleton folder and then I'll merge this in? Give yourself credit, of course.

Of course! Thank you for the feedback. I am glad you found the results as interesting as I did.
I have added a README to the Singleton folder as part of this pull request. If you would prefer I can make it a separate PR. Please review the content of the README and feel free to make any changes you deem necessary.
I do not deserve any credit, the Benchmarks were adapted from your unit tests.


https://tox-rebrand.herokuapp.com

Hi SkyzohKey,
nice site, but not complete yet. Web-App, Downloads, About, Blog are empty pages.
Please set up an web version of your TOX client.
Did the project will be continued?
If it stucks in money. please contact me ;)
BR

Hello @r4de ! Thanks for the great words. I want to finish that website so we can maybe get it to replace the actual tox.chat one. The WebApp is coming when toxcore supports WebSockets/WebRTC. in the meantime, I may create a bridge between WebRTC/TCP so it works without core supporting it, but I feel it's a bit hackish.
You can contact me at<EMAIL_ADDRESS>🤘🔥


AI navmap overlay

It's not super pretty atm so open to suggestions.

LIDAR going to be reserved for a science item.
Don't merge without https://github.com/space-wizards/space-station-14/pull/32477 or else it looks bad.
:cl:

tweak: Replaced AI static with a different background.

brilliant idea

This looks awesome. It is currently hard to tell the difference between walls and open space, perhaps you could draw diagonal lines inside the wall blocks? Like the station maps do it. Also, how does the green/orange color scheme look when compared to the AI eye? I'm curious to see how it would look with other colors, such as blue/yellow or blue/purple.
Another thing to note...  Perhaps the old static could stay to indicate where there is no floor?

You could use the navmap wall sprite that the station map uses
also slight static for the background

You could use the navmap wall sprite that the station map uses

It's not a sprite and it also doesn't look good blown up.

Also any chance we'll get the AI Eye to appear over the overlay too?

It's not a sprite and it also doesn't look good blown up.

something similiar then? The walls just feel empty and are hard to tll apart from the floor

Seems significantly more readable to me if the walls and doors are filled

Yeah I might go with that, it's similar to what I did for shuttle control of a lower alpha fill. If we gave it some kind of vcr texture backing it might look good too.

Will this include seeing dots for crew with coordinates on? Or is that out of scope?

Out of scope.
I wanted this to share navmap code a bit but it's a bit too hard to do as it bakes some stuff in so we might need to do something about that if we ever added more than crew monitoring to it.

make it look like you're walking on the station map overlay

AI should have an action to swap between camera and overlay sight even for camera'd areas so you can simplify looking for things

I spent some time floating around Fland, and I think it gets a bit visually weird that the Empty Squares don't have a left and top border when adjacent to visible tiles. Especially in situations where full-black Space tiles are around them, like this spot in Containment. I think it would be easier to parse what I am looking at if the green contour always went all the way around

(A much more subjective thing, but I also really liked the Static effect in general, so even though I see the clear advantages to this change,  I'm wondering if there was a way to faintly incorporate the static into this system, somewhere? Maybe either the walls OR the floor (but not both, for visual distinction) could have a mild version of it? (or perhaps Space tiles)

I'm wondering if there was a way to faintly incorporate the static into this system, somewhere?

Maybe it could come back later if mechanics like processing power are added. Or maybe it could replace the navmap overlay if power goes out?

Interesting, do you think AI should still be allowed to interface with powered machines even when there are no cams?
It would make sense that a ai would need not see a machine hardwired to the station to use it, and a lack of vision would still be debilitating.
Lots of gameplay implications

Or maybe it could replace the navmap overlay if power goes out?

this seems like the way to go, imo

this seems like the way to go, imo

The point of having a navmap overlay is that AI is not utterly useless when theres no power, as I believe cameras will stop providing vision when unpowered
Giving it a navmap that only exists when powered and also making unpowered cams give no vision is a terrible idea with how often power goes out

How about this. Static should be applied to space tiles out of camera view (or simply anything that is not on the AI's grid). This way the AI will have 4 different types of "objects" it will be able to recognize even beyond it's cameras view:

Dark green tiles for any type of floors
Bright green tiles for any type of walls (i think linear hatching like in default navmap will look good too and also add some consistency with it)
Whatever-it-is for any type of airlocks
Static for anything that is not a part of the station (because AI doesn't have any information about it)

This will be enough for the AI players to not get lost and understand what they are looking at.  Because it was really hard for me to understand that these are space tiles (especially the bottom one, that looks more like a bug)


me_messages: Sender-name cleanup.

This PR removes remaining references to a class (.sender_name-in-status) that was eliminated as part of #25997.
It also aligns the info-overlay example for me-messages to use the .sender_name class, along with the status-message class, so that the example always remains in concord with live code. (In the screenshots below, you can see the extra space after Iago's name is no longer present because of how usernames are now run inline with the me-message text.)
Screenshots and screen captures:

Before
After

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

Merged, thanks @karlstolley!


Automate deployment to TEST

Acceptance criteria: On the initiation of the Action, new images in TOOLS are picked up and deployed to TEST, where they are confirmed by manually accessing the TEST url.

Warren will look into this, Kunal's off sick

As per previous discussions with @warrenchristian1telus this is on HOLD at the moment as the TEST env was being used by active users.

@kkapoor-fresh all testing should now be in production. @allanhaggett can you please confirm that all users are out of test, and that we're ready to bring it down to implement CI/CD deployments?

@kkapoor-fresh blocked on triple checking that they are no longer using the test env "in production"

We have checked with the appropriate people and are clear to proceed with this after 16:30 PST today

@warrenchristian1telus @will-freshworks @freshjwarren which means as per dicussion we can go back to working on CI/CD pipeline -automation to Moodle TEST, right?@allanhaggett


Fixes #1428 Converts command arguments to environment variables and back again (merge to master)

This change allows environment variables to be passing into marathon so they do not show up in ps.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

xref #4644

Fixed in https://github.com/mesosphere/marathon/commit/85a32314d6c60d620c1fa2cc8d5660b23190cf47


Fix support for skipping Go tracers

During some refactoring for multi-process support we had broken the debug option BEYLA_SKIP_GO_SPECIFIC_TRACERS, which can come in handy when debugging issues with Go instrumentation. For example, we may fail to parse something or work with older Go version that is unsupported.
This fixes the support for the option and adds an integration test so we don't accidentally break it again.

Codecov Report
Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (e2c0c51) 78.26% compared to head (1c21a19) 65.89%.
Report is 1 commits behind head on main.

Files
Patch %
Lines

pkg/internal/discover/attacher.go
40.00%
1 Missing and 2 partials :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #451       +/-   ##
===========================================
- Coverage   78.26%   65.89%   -12.38%
===========================================
  Files          61       58        -3
  Lines        5028     4937       -91
===========================================
- Hits         3935     3253      -682
- Misses        882     1418      +536
- Partials      211      266       +55

Flag
Coverage Δ

integration-test
65.89% <40.00%> (+0.14%)
:arrow_up:

unittests
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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

I'd also backport the issue to release-1.0.

I'd also backport the issue to release-1.0.

Sounds good!


global: preparation for beta release

Moves cli.py to __main__.py and cmd.py to cli.py to follow
naming conventions.

Adds PyPy to testing matrix on Travis CI.

Signed-off-by: Jiri Kuncar<EMAIL_ADDRESS>--
closes #86

I see that Travis CI passed for this PR, but the status here seems stalled... Going to restart the Travis CI job, at the price of eating our Travis quota...


fix panic & provide msg

Overview
This PR fixes Kubescape panicking for image scanning when using output formats other than pretty printer and JSON (which are the only ones supported).
Previous behavior:
kubescape scan image nginx --format junit

Behavior with this PR:
kubescape scan image nginx --format junit

@Daniel-GrunbergerCA How is the object nil?

@Daniel-GrunbergerCA How is the object nil?

Since it's not a configuration scanning

We should have this logic handled differently...
Also, we should support SARIF and JUNIT (similar to grype)

I will sarif support. I don't see grype has junit
Regarding the logic, how do you think we should handle?

Handling logic:

Dont create an instance of a printer if it is not supported
Consider having an indication of what is being scanned

Regarding the formats, It look like  they don't support junit.

I have put a validate function for the format. I did leave the nil check though, since it's better to have it IMO.
Also, since I don't want to break the ActionPrint interface, printers which support both image and configuration scanning, they decide what to print according to the report data. I think it makes sense especially since we can have both image and configuration scanning results for the same scan


Error trying to build for AVX2 on CPU

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

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): source
TensorFlow version: 2.0.0
Python version: 3.6.4
Installed using virtualenv? pip? conda?: pip
Bazel version (if compiling from source): 0.26.1
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: 10/7
GPU model and memory: NVIDIA GeForce MX150

Describe the problem
I am trying to build tensorflow with AVX2 instructions for my CPU to increase speeds, but bazel keeps failing when loading tensorflow
Provide the exact sequence of commands / steps that you executed before running into the problem

Cloned the tensorflow source from github and checked out the r2.0 branch.
Ran python ./configure.py
Proceded through steps, selecting no for all other builds and set the bazel config option to /arch:AVC2
Ran bazel build --config=opt //tensorflow/tools/pip_package:build_pip_package

Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
The error text is attached here:
error.txt

@ajidevelop ,
Hello i see error Stderr: /usr/bin/bash: patch: command not found in log ,can you install patch in your PATH?Thanks!

This seemed to fix the issue, but the only thing I'm confused about is why the build_pip_package command seem to target 16000+ packages

Closing this issue since it's resolved.
Feel free to reopen if still have problems. Thanks!


Identifiers validation failed for dataset Computarización de las colectas del estado de Morelos depositadas en el Herbario HUMO de la Universidad Autónoma del Estado de Morelos

Identifier validation failed for the dataset Computarización de las colectas del estado de Morelos depositadas en el Herbario HUMO de la Universidad Autónoma del Estado de Morelos:

Crawler attempt: 285
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 6021
Cause: GBIF IDs hit maximum allowed - 50%, duplicates - 100%, total records count 6019, absent records count 6019
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3073107/step

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Computarización de las colectas del estado de Morelos depositadas en el Herbario HUMO de la Universidad Autónoma del Estado de Morelos : https://doi.org/10.15468/b1oury.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Computarización de las colectas del estado de Morelos depositadas en el Herbario HUMO de la Universidad Autónoma del Estado de Morelos:

Crawler attempt: 288
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 6021
Cause: GBIF IDs hit maximum allowed - 50%, duplicates - 100%, total records count 6019, absent records count 6019
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3093977/step

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Computarización de las colectas del estado de Morelos depositadas en el Herbario HUMO de la Universidad Autónoma del Estado de Morelos : https://doi.org/10.15468/b1oury.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.


Update Vpn Package Family Name to note required field and add helpful remark

Update vpnpluginprofile_vpnpluginpackagefamilyname.md to note that this field is required to for a VpnPlugInProfile to be valid.
Also, add a remark that helps developers get a valid value if they are creating a profile from the plug-in.

@PoeTheMonk : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@irinvoso and @msatranjr , could you take a look at these changes?


Move service & client idl into a dedicated repo

New repo created https://github.com/uber/cadence-idl


it would be nice to add inspect element

by hovering in elements in editor

duplicate of #149

If you're still looking for an alternative VS Code extension: Five Server is able to jump to a section of a preview when you double-click or edit a section of your code. It can also highlight the code you are working on in your browser, update your files instantly while typing on your keyboard, and navigate your live preview automatically to the current editing file.

Only downside is that there's no Workspace Multi-root support yet.


unable to create provisioning profile using spaceship::Launcher

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
i use spaceship as library, and i found that it is  unable to create provisioning profile using spaceship::Launcher , and it would report "Please login using Spaceship::Portal.login('user', 'password') (RuntimeError)"
Command executed
save the following code  as spacetest.rb
require 'fastlane'
require 'spaceship'

USERNAME = 'YOUR_APPLE_ID'
PASSWORD = 'YOUR_PASSWORD'

def test()

  bundle_id = 'YOUR_BUNDLE_ID'       #a registered bundle_id

  client = Spaceship::Launcher.new( USERNAME, PASSWORD )
  client.select_team

  cert = client.certificate.production.all.first
  if cert == nil
      puts("#{__callee__} apple  no certification for bundle_id: #{bundle_id} ")
      return
  end

  profile = client.provisioning_profile.ad_hoc.create!(
                      bundle_id: bundle_id , certificate: cert, name: "dev12")

  puts profile

end

if $PROGRAM_NAME == __FILE__
  test
end

Complete output when running fastlane, including the stack trace and command used
Traceback (most recent call last):
	5: from ./spacetest.rb:35:in `<main>'
	4: from ./spacetest.rb:25:in `test'
	3: from /home/xxxx/.rvm/gems/ruby-2.6.3/gems/fastlane-2.135.2/spaceship/lib/spaceship/portal/provisioning_profile.rb:264:in `create!'
	2: from /home/xxxx/.rvm/gems/ruby-2.6.3/gems/fastlane-2.135.2/spaceship/lib/spaceship/portal/app.rb:111:in `find'
	1: from /home/xxxx/.rvm/gems/ruby-2.6.3/gems/fastlane-2.135.2/spaceship/lib/spaceship/portal/app.rb:85:in `all'
/home/xxxx/.rvm/gems/ruby-2.6.3/gems/fastlane-2.135.2/spaceship/lib/spaceship/portal/portal_base.rb:11:in `client': Please login using `Spaceship::Portal.login('user', 'password')` (RuntimeError)

   N/A

Environment
Stack

Key
Value

OS
debian_based buster/sid

Ruby
2.6.3

Bundler?
true

Git
git version 2.17.1

Installation Source
~/.rvm/gems/ruby-2.6.3/bin/fastlane

Host
Ubuntu 18.04.3 LTS debian_based buster/sid (4.15.0-67-generic)

Ruby Lib Dir
~/.rvm/rubies/ruby-2.6.3/lib

OpenSSL Version
OpenSSL 1.1.1  11 Sep 2018

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

System Locale

Variable
Value

LANG
zh_CN.UTF-8
✅

LC_ALL
zh_CN.UTF-8
✅

LANGUAGE

fastlane files:
No Fastfile found
No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.135.2
✅ Up-To-Date

credentials_manager
1.0.0
✅ Up-To-Date

spaceship
1.0.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.3.0

executable-hooks
1.6.0

bundler-unload
1.0.2

rubygems-bundler
1.4.5

bundler
2.0.2

rake
13.0.1

CFPropertyList
3.0.1

public_suffix
2.0.5

addressable
2.7.0

ast
2.4.0

atomos
0.1.3

babosa
1.0.2

claide
1.0.3

coderay
1.1.2

colored
1.2

colored2
3.1.2

highline
1.7.10

commander
4.4.6

commander-fastlane
4.4.6

concurrent-ruby
1.1.5

safe_yaml
1.0.5

crack
0.4.3

dotenv
2.7.5

emoji_regex
1.0.1

excon
0.68.0

multipart-post
2.0.0

faraday
0.17.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday_middleware
0.13.1

fastimage
2.1.7

gh_inspector
1.1.3

jwt
2.1.0

memoist
0.16.1

multi_json
1.14.1

os
1.0.1

signet
0.12.0

googleauth
0.6.7

httpclient
2.8.3

mime-types-data
3.2019.1009

mime-types
3.3

declarative
0.0.10

declarative-option
0.1.0

uber
0.1.0

representable
3.0.4

retriable
3.1.2

google-api-client
0.23.9

digest-crc
0.4.1

google-cloud-env
1.3.0

google-cloud-core
1.4.1

google-cloud-storage
1.16.0

json
2.2.0

mini_magick
4.9.5

multi_xml
0.6.0

plist
3.5.0

rubyzip
1.3.0

security
0.1.3

naturally
2.2.0

simctl
1.6.6

slack-notifier
2.3.2

terminal-notifier
2.0.0

unicode-display_width
1.6.0

terminal-table
1.8.0

tty-screen
0.7.0

tty-cursor
0.7.0

tty-spinner
0.9.1

word_wrap
1.0.0

nanaimo
0.2.6

xcodeproj
1.13.0

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.0

credentials_manager
1.0.0

tzinfo
2.0.0

et-orbi
1.2.2

raabro
1.1.6

fugit
1.3.3

hashdiff
1.0.0

jaro_winkler
1.5.4

kgio
2.11.2

method_source
0.9.2

minitest
5.13.0

minitest-around
0.5.0

minitest-focus
1.1.2

mustermann
1.0.3

oj
3.9.2

ox
2.11.0

parallel
1.19.0

parser
<IP_ADDRESS>

pry
0.12.2

rack
2.0.7

rack-cors
1.0.6

rack-protection
2.0.7

rack-test
1.1.0

rainbow
3.0.0

raindrops
0.19.0

ruby-progressbar
1.10.1

rubocop
0.76.0

rubocop-performance
1.5.1

rufus-scheduler
3.6.0

semantic_logger
4.6.0

shotgun
0.9.2

tilt
2.0.10

sinatra
2.0.7

sinatra-logger
0.3.2

unicorn
5.5.1

vcr
5.0.0

webmock
3.7.6

generated on: 2019-11-15

cc @max-ott

@littlewhitetwo could you please try what the error message tells you? Spaceship::Portal.login('user', 'password') I'm not aware that Spaceship::Launcher works anymore.

@littlewhitetwo Could you still try using Spaceship::Portal to see if it works there?

@max-ott
of course it works. so, is Spaceship::Launcher   deprecated ?

@littlewhitetwo @max-ott I actually had no idea that Spaceship::Launcher was a thing 🤔 I would probably suggest switching to Spaceship::Portal and Spaceship::Tunes if possible 😇 Spaceship::Launcher is really old and probably will get deprecated soon

@joshdholtz  thanks a lot.


Documentation

Start writing a documentation webpage for PCU. Includes a huge rewrite of all function and class documentation so we can automatically generate an API reference.

This PR creates proper documentation for the functionality in point-cloud-utils. It also implements a few small quality of life improvements. In particular:

Full documentation website with code examples, figures, description of functionality, API reference, and recipes
Complete overhaul of docstrings
Small fixes and tweaks:

earth_movers_distance is a function you can just call which is the common case (I still want to implement a sparse C++ version of this)
morton code operations take unsigned inputs (this was a bug)
Update the main README


add test to prevent addition of k8s.io/kubernetes as dep

Importing k8s.io/kubernetes as library is not supported and creates significant maintenance burden: any update can break anytime. We spent a very significant amount of energy removing the deps and we should ensure it is not coming back.
We need a check to scan go.mod pre-merge and fail if that dep is pulled - directly or indirectly.

these PRs will remove the dep: #734 #746


Update App Store description

Removed english line, added iCloud as a feature

Ups. Pressed the wrong button ;)


Change deploy.yml to update dependencies

QA merge test went well

Gonna recheck the merge

QA merge went well again


Revive ability to snapshot() the CertificateCredentials so they can be used on remote agents

As detailed in https://issues.jenkins.io/browse/JENKINS-70101 I've hit a problem using certificate-based user authentication in http-request-plugin (noticed as part of my work on https://issues.jenkins.io/browse/JENKINS-70000 in https://github.com/jenkinsci/http-request-plugin/pull/120 but also reproduced with latest 1.16 release of that plugin).
After a week of reproductions and tracing across different plugins, the root of the problem crystallized as the use of SecretBytes in UploadedKeyStoreSource and effective lack of special snapshot() support. As a consequence, serialized copies of the key store used the same SecretBytes as on the Jenkins Controller, but being on a different JVM in the remote agent case, they used a different instance of the static KEY field with its own secret field. Although the SecretBytes are diligently copied (took a lot of effort to confirm that as seen in sibling branch https://github.com/jimklimov/credentials-plugin/tree/JENKINS-70101-trace), they are unreadable on the remote agent.
During investigation I found that credentials-plugin did have an implementation for the Certificate Credentials Snapshot Taker, but it was removed by https://github.com/jenkinsci/credentials-plugin/commit/40d0b5cc53c265b601ffaa4469310fad390a80fb as part of deprecation of FileOnMasterKeyStoreSource subclass. Also an earlier history of the plugin involved the Secret class which effectively stores a base64 string and only encodes/decodes it on demand -- this was superseded by SecretBytes but some handling for conversion from older versions remained. This code proved to be a good starting point for fixing the problem, although not without some further work:

originally it consulted isSnapshotSource (forced true for UploadedKeyStoreSource subclass) and just returned the original credential if so;
even with that check disabled, the snapshot used SecretBytes for the copied key store and suffered the same fate - not usable on agent.

This PR adds tests (failing at first to confirm the problem), makes use of older codebases and new verified fixes:

UploadedKeyStoreSource.isSnapshotSource() depends on Channel.current() == null (so for remoting-related snapshots it is false and shortcuts to return this are not taken)
CertificateCredentialsSnapshotTaker was revived as a separate source file and standalone class, similar to existing UsernamePasswordCredentialsSnapshotTaker
UploadedKeyStoreSource was modified to handle again a Secret uploadedKeyStore field (and provide data from it if SecretBytes uploadedKeyStoreBytes are currently null). As part of that, transient and final modifiers on these fields had to go.
CertificateCredentialsSnapshotTaker was modified to create the new UploadedKeyStoreSource instance with Secret version rather than SecretBytes (as CredentialsSnapshotTaker docs stipulate, "all the details are captured within the credential")

Thanks to @mawinter69 and @slide for bright ideas and pointers, and general sympathy as I woed on the chat :)
Separately note that this PR adds tests using a separate JVM for the build agent to reproduce the problem. This code may be worth exporting into some JenkinsAgentRule if someone is up for it.

[x] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
[x] Ensure that the pull request title represents the desired changelog entry
[x] Please describe what you did
[x] Link to relevant issues in GitHub or Jira
[x] Link to relevant pull requests, esp. upstream and downstream changes
[x] Ensure you have provided tests - that demonstrates feature works or fixes the issue

NOTE: I'll post commits in several phases, so CI has its chance to fail with the tests and show the original problem in logs.

Problem exposed in build logs, e.g. in https://github.com/jenkinsci/credentials-plugin/pull/391/checks?check_run_id=9617279731 :
[2022-11-21T14:02:34.841Z] Querying HTTPS with cert...
[2022-11-21T14:02:34.841Z] [Pipeline] httpRequest
[2022-11-21T14:02:34.841Z] HttpMethod: GET
[2022-11-21T14:02:34.841Z] URL: https://github.xcom/api/v3
[2022-11-21T14:02:34.841Z] Content-Type: application/x-www-form-urlencoded; charset=ISO-8859-1
[2022-11-21T14:02:34.841Z] Using authentication: myCert
[2022-11-21T14:02:34.841Z] [Pipeline] }
[2022-11-21T14:02:34.841Z] [Pipeline] // node
[2022-11-21T14:02:34.841Z] [Pipeline] End of Pipeline
[2022-11-21T14:02:34.841Z] javax.crypto.BadPaddingException: Given final block not properly padded. Such issues can arise if a bad key is used during decryption.
[2022-11-21T14:02:34.841Z] 	at java.base/com.sun.crypto.provider.CipherCore.unpad(CipherCore.java:975)
[2022-11-21T14:02:34.841Z] 	at java.base/com.sun.crypto.provider.CipherCore.fillOutputBuffer(CipherCore.java:1056)
[2022-11-21T14:02:34.841Z] 	at java.base/com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:853)
[2022-11-21T14:02:34.841Z] 	at java.base/com.sun.crypto.provider.AESCipher.engineDoFinal(AESCipher.java:446)
[2022-11-21T14:02:34.841Z] 	at java.base/javax.crypto.Cipher.doFinal(Cipher.java:2202)
[2022-11-21T14:02:34.841Z] 	at com.cloudbees.plugins.credentials.SecretBytes.getPlainData(SecretBytes.java:140)
[2022-11-21T14:02:34.841Z] Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to worker
[2022-11-21T14:02:34.841Z] 		at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1784)
[2022-11-21T14:02:34.841Z] 		at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356)
[2022-11-21T14:02:34.841Z] 		at hudson.remoting.Channel.call(Channel.java:1000)
[2022-11-21T14:02:34.841Z] 		at jenkins.plugins.http_request.HttpRequestStep$Execution.run(HttpRequestStep.java:404)
[2022-11-21T14:02:34.841Z] 		at jenkins.plugins.http_request.HttpRequestStep$Execution.run(HttpRequestStep.java:383)
[2022-11-21T14:02:34.841Z] 		at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
[2022-11-21T14:02:34.841Z] 		at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
[2022-11-21T14:02:34.841Z] Caused: java.lang.Error
[2022-11-21T14:02:34.841Z] 	at com.cloudbees.plugins.credentials.SecretBytes.getPlainData(SecretBytes.java:142)
[2022-11-21T14:02:34.841Z] 	at com.cloudbees.plugins.credentials.SecretBytes.getPlainData(SecretBytes.java:233)
Output truncated.

Will post the fix commits now :)

Tests fixed. Now posting the final touch, to make them quieter. This passes - and good to merge (on my side) :)

@jenkinsci/core-security-review Should probably review this.

Yep. In particular, I wonder if it is okay to leave it like this (possibly storing keystore data "plaintext" in a Secret which still needs a password to read, vs. SecretBytes all the time).
I have a further effort to force conversion from Secret to SecretBytes on first read, if we are in context where Channel is not null and JenkinsJVM indicates running not on a controller. It complicates things a bit, does not seem to break anything, and I have no idea if it actually takes effect (never saw the logs it is supposed to emit in my local branch - not as MVN log, not as pipeline log, not as agent log...) and also there is some indefinite timeframe where the Secret is used by the class instance before the first read. Probably someone with debug privileges can un-private the field to read it, but that's a pretty contrived attack and probably SecretBytes are not much safer in that situation.

https://github.com/orgs/jenkinsci/teams/core-security-review Gentle bump :)

Hey @jimklimov, we've noticed the issue. We'll try to review it if/when time permits.

Thanks for the diligently annotated response :)
Regarding FileCredentialsImpl - I did not use it so maybe the issue is there, just unnoticed. Probably multi-agent tests like those I proposed here can be used to check if it works or is similarly broken.

Just in case for future readers, this is a different class (and plugin) from FileOnMasterKeyStoreSource deprecated by SECURITY-1322 fixes ;)

Regarding "correctness" of the fix: it seems that

The Secret is easier to read and clone, since it effectively carries the plaintext data as a Base64 String value which can be encoded/decoded for serialization to disk or some such - and the KEY is only used there. Copying it across the remoting boundary is just about copying the (plaintext) string field of the class instance, I guess.
On the other hand, SecretBytes stores an array of bytes with encoded data and salt, and relies on its KEY (static so shared by all instances in one JVM - and with remoting there are two JVMs). When a SecretBytes instance is cloned on the same (controller) JVM, the copy is decodable. When it passes the remoting boundary, the actual byte arrays are diligently copied, but the key in that JVM can not decipher it. And there are no provisions to set the KEY in the remote agents (it is generated for a runtime of JVM, not the master.key or some such) - it could be a different way to solve the issue, with a trade-off depending on how much we trust our remote agents.
I agree that the Secret is potentially less secure since the plaintext content is easy to access by debugger and API. In case of certificate key store (bytes serialized into a string and back) it is IMHO less of a problem, since a separate password is needed to read the store (and pedantically, same or other password for each private key... not sure if current code allows different passwords here, just did not dig in that direction).

According to my tracing, the referenced code of http_request runs on the controller, as the class is initialized for the step, and so the original credential and its snapshot are readable there. By the time it gets to the actual httpExecute and specifically credentials.getKeyStore() in https://github.com/jenkinsci/http-request-plugin/blob/master/src/main/java/jenkins/plugins/http_request/auth/CertificateAuthentication.java#L34 - that part of code runs on the agent and fails to decipher the exact replica of original SecretBytes in that remote JVM with its different key, but succeeds to make use of Secret.
As I mentioned above, in another branch (and draft PR #393 for review convenience) I have additional tracing and a commit https://github.com/jenkinsci/credentials-plugin/pull/393/commits/537d44dc7e57be326ba5481f8501edb856512f73 to convert from Secret to SecretBytes upon first read in remote JVM. Pedantically it should be safer and seems to not hurt (test-wise), but I think it is sort of moot given that some percentage of the time that data is "less protected" anyway, and for keystores needs a password to read anyway. Still, may be worth adding for additional peace of mind, especially if some use-cases would be not about short-lived storage of this data (with http-request-plugin, it lives as long as each separate step is being processed: snapshot'ed in preparation of the context, handles request/response, and then discarded).
I have no strong opinion about reverting the older change (from Secret to SecretBytes), but still would be reluctant to do so:

in general case, SecretBytes do seem safer vs. memory-poking
current solution is around for a few years and maybe something somewhere (maybe in someone's internal JSLs) relies on code and fields being as they are. I've seen pipelines fiddling with field visibility via reflection here and there, to just get their job done, albeit quickly and dirtily, so while this is not something we want to bother "supporting", got no good reason for breaking that either :)

Finally, regarding the idea to effectively redefine http-request-plugin::CertificateAuthentication so we would extract needed credential fields - it does sound viable. However on one hand it would be more work (compared to me having the solution I need with this PR, and another PR there https://github.com/jenkinsci/http-request-plugin/pull/120 for better support of trusted CAs), and so something to reimplement and retest for no apparent gain. Also not sure if it is more/less safe for the credential payload that we are trying to protect; potentially the getters used now might deny privy access to certain agents (e.g. in a paranoid subclass), and getting info earlier would forfeit such security. On another, the root cause of my stumble there was that snapshotting in this plugin happened to be dysfunctional if remoting got involved. So a different implementation there would be a workaround, and potential other broken use-cases would need to do similar or invent their new wheel. Although the referenced docs are a bit ambiguous: "if you need to send a credential - use snapshot()" (here this one is broken so needs a fix proposed by this PR) "...but better avoid sending it at all" (your proposal).
So it likely makes sense to log an RFE issue in http-request-plugin to rearchitect this part, but I was not on a crusade to make all of the world better - got dayjob tasks to tend to, so have to be satisfied by getting it working and leave refactoring to others :) But since the root-cause was broken snapshot() ability here, well... it is a bug that should be fixed anyway. Work with that plugin just led me to the discovery :)

The Secret is easier to read and clone, since it effectively carries the plaintext data as a Base64 String value which can be encoded/decoded for serialization to disk or some such - and the KEY is only used there. Copying it across the remoting boundary is just about copying the (plaintext) string field of the class instance, I guess.

Ah, yeah I did not realize that Secret's in-memory form is just the plaintext, whereas SecretBytes.value holds the ciphertext (this comment seems wrong looking at getPlaintextData and getEncryptedData()). I guess that does mean that https://github.com/jenkinsci/credentials-plugin/pull/64 is what originally broke the ability to use these credentials remotely. Another fix could be to make SecretBytes hold the unencrypted value in memory, comparable to Secret, which I think would prevent us from needing to add all of the snapshot-related code back, and it would allow other credentials types that use SecretBytes to work on agents without special snapshot support.

At least that's an option to keep in mind. If it bites someone else. This use-case issue took 3? years to be noticed intently enough...

A memory-dump snapshot of those is not immediately readable, unlike a Secret, which probably is the point of this class.

This comment and the reply make me think that the main goals were code deduplication and to avoid the need to Base64-encode raw byte[] secrets that may not be text when storing them in a Secret. I do not think that it was intended to offer security improvements over Secret, and I do not think that it does.

Ok, I'll trust your judgement on this then - you're the security team and know more context overall :)
Now, what about this-here PR? To me and my tasks it brings "immediate relief" for an issue at hand; you seem to be in favor of deeper design changes... Can this one be merged as proposed and the rest iterated separately? :)

Now, what about this-here PR? To me and my tasks it brings "immediate relief" for an issue at hand; you seem to be in favor of deeper design changes..

From my perspective, this general goal of this PR and the approach seem fine. My personal opinion is that https://github.com/jenkinsci/credentials-plugin/pull/391#issuecomment-1341628264 might be simpler and help us avoid related issues in the long run, but that's just my opinion.
I am not an active maintainer of this plugin, so I'll request a review and see if anyone who is responsible for it wants to review it (sorry, I should have done this after my initial review). I have not reviewed the implementation carefully, but generally speaking the tests look more complicated than I would expect. I don't think we want to take on dependencies on http_request or job-dsl, even in test scope. I don't think it makes sense to test the behavior of withCredentials here, and I don't think we want a credentials-binding dependency either. I think you could probably use a @TestExtension MasterToSlaveCallable (or a basic Step if you must use Pipeline) to drastically simplify the tests.
In case you did not already know, you can always download a build of the plugin with your PR from the "Incremental" GitHub check to use while you wait for a maintainer. The latest build as of the time of writing this comment can be found here: https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/credentials/1235.v3213f694ca_1c/.

Anyway, since I am trying to be helpful and not just nitpicky (😄), take a look at https://github.com/jenkinsci/credentials-plugin/compare/master...dwnusbaum:credentials-plugin:JENKINS-70101 to see what a fix that changes SecretBytes to use unencrypted data in memory looks like. Whether maintainers would prefer that type of fix or yours, I do not know.
That said, my test in that branch is minimal and reproduces the javax.crypto.BadPaddingException: Given final block not properly padded. Such issues can arise if a bad key is used during decryption issue described in JENKINS-70101 without the fix, and passes with the fix.


NetOffice samples and tutorials

Are there supposed to be samples here?
Original question: https://github.com/netoffice/Samples/issues/1

NetOffice code samples existing in the @NetOfficeFw repositories at three places:

This repository
Examples in NetOffice repository
Tutorials in NetOffice repository

PS1: Not all samples are kept up to date.
PS2: This is a test if we can cross reference issues from the https://github.com/netoffice/Samples/ repository.

@elthombre and @DanJBower I hope this will answer your question from https://github.com/netoffice/Samples/issues/1


Oauth 2 base rebased

#448 is the PR where these changes were reviewed.
This is an updated PR on a fresh branch to confirm that the changes from #467 were correctly rebased into the branch 'oauth-2-base'.
In the event that the rebase subtly went wrong, I want to be able to go back to the state of #448 and try again.

@cdolfi review on this PR would just be making sure that the page reorg looks correctly represented here.


Update requirements

cc @mcarans @turnerm

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.458%

Totals

Change from base Build<PHONE_NUMBER>3:
0.0%

Covered Lines:
1753

Relevant Lines:
1896

💛  - Coveralls


Multiple types for PolicyDocument?

      "type": [
        "object",
        "string"
      ],

This seems a bit clunky. It would be hard for tools like CDK to help provide a better developer experience because many static typed languages don't support this type of input. Personally I would go with just an Object or (better yet) convince the IAM team to create an official PolicyDocument type that can be re-used. Also, calling it an "object" means it is arbitrary json and I DO NOT LIKE that. What are valid keys? what are valid values? what is even real anymore?
https://github.com/aws-cloudformation/aws-cloudformation-resource-providers-codeartifact/blob/master/aws-codeartifact-domain/aws-codeartifact-domain.json#L41-L44

We have since changed this to object. What is the value of adding validation of permissions policies if the the service will handle misformed policies?

If you were reading the docs for CodeArtifact and saw this, would you know what that json was supposed to look like?

We have some examples available here that demonstrate how to add the policy doc:
https://github.com/aws-cloudformation/aws-cloudformation-resource-providers-codeartifact/tree/main/sample-templates/json

if I were reading this then it would definitely be clear, maybe we can add this to the "description" text?


Creator not found occured when user FullName is null

This PR is related to bug #602 .

Can one of the admins verify this patch?


Add support for tox 3

Also closes #5

Choosing to ignore travis build failures on 3.7dev, will care when 3.7 lands for real

Can we have a new release for this fix?

CC @kbalonek ^

Thanks! :)

Happy to help, and glad people are actually using it!


[NEW] Gitlab Component Kit

[x] I have read the Contributing Guide - https://github.com/RocketChat/Rocket.Chat/blob/develop/.github/CONTRIBUTING.md#contributing-to-rocketchat doc
[x] I have signed the CLA - https://cla-assistant.io/RocketChat/Rocket.Chat
[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works (if applicable)
[x] I have added necessary documentation (if applicable)
[x] Any dependent changes have been merged and published in downstream modules

Issues
Mentioned in the issue #72
Proposed changes (including videos or screenshots)

New Reusable Gitlab Components Kit

Data fetching method in cms (can be re-used when switching from strapi) to provide a better experience for community builders. All data fetching for  the gitalb kit for a repository will be done by a a single gitlabKit() function.

Introduce Single <Gitlab ... > tag which can be used to fetch different components of the kit depending on props/parameters. <Gitlab type={'members'} gitlabData={props.gitlabData} />

Introduce single gitlabKitData(project_id ,[..needs]) function which can fetch relevant data based on the components we wish to use on a particular page.

New Gitlab Merge Request Component

New Gitlab Project Members Component

New Gitlab Project Overview Component

New Gitlab Project Issues Component

Introduce Documentation for Gitlab Component Kit

https://user-images.githubusercontent.com/70485812/160279357-55a1f115-c0d0-43f8-9945-805f5785ec90.mp4

New Gitlab Page to showcase the components kit which can be accessed at /gitlab

https://user-images.githubusercontent.com/70485812/160279209-f9ec5e14-772c-4920-b4d8-ec20dab7d50c.mp4

@Sing-Li I have added all the necessary to the Gitlab Components Kit , added documentation and have also created a page to showcase the component. Let me if know if there are any changes 😅


Newer versions do not export scripts (no Scripts folder)

I was using an older version of the tool (which is no longer available) that actually exported scripts into a Scripts folder. Now when I use the newest version with the GUI , no Scripts folder is created and no scripts are exported. Why?

Maybe you test it on different game and this game uses Il2Cpp?

I double checked script export. Yes, it is a little bit tricky now. Script export work in 2 cases:

You drop whole folder with game files
You drop single/multiple game files and Managed folder (all at once)
I know that it isn't convenient and I was going to improve this behavior in special big update but I didn't manage to finish it so now I don't know when will do it.

Alright thanks for the info. I'll try it out.

I double checked script export. Yes, it is a little bit tricky now. Script export work in 2 cases:

You drop whole folder with game files
You drop single/multiple game files and Managed folder (all at once)
I know that it isn't convenient and I was going to improve this behavior in special big update but I didn't manage to finish it so now I don't know when will do it.

As a related question, will script recompilation support be expanded on in the future? Right now external tools such as dnSpy are required to properly decompile script files in a more complete manner.

@JillCrungus no, just because such tools as dnSpy exist. Those tools will do its work much better even though it requires extra step from user.

@JillCrungus no, just because such tools as dnSpy exist. Those tools will do its work much better even though it requires extra step from user.

That's fair enough, thanks.


V6 how to use it with arduino ?

Littlevgl is amazing - I have started recently with v5.3
Now littlevgl V6 is out - how to use it with arduino ?
Just replace scr directory with latest version ? Any recommendation ?
Thank you

@luc-github I would recommend waiting - @Pablo2048 is working on updating the project already.

@embeddedt @luc-github  thank you - let me know if I can help in anything ^_^

Ok, I'm almost done. The only thing that remains are font files with #include "lvgl/lvgl.h" - I'm unable to force Arduino to compile this so far (Arduino Builder is unable to locate the lvgl subdirectory). When I change #include "lvgl/lvgl.h" to #include "lvgl.h" it compiles ok...

@Pablo2048 I've updated the built-in fonts to use relative path to lvgl.h

Great - thanks. So I use current master instead of Release. Is this ok? If all my testing went ok, I will do release new version of the library until end of this week.

So I use current master instead of Release Is this ok?

Yes. We continuously add small fixes to master.

Library updated with the new core. I'm not doing an release for now, because it's not based on actual LVGL release - I'm using master...

Thank you so much ^_^
So lv_arduino release will be when 6.1 is released, I am right ?
Is there a way to automate the creation process when a lvgl release will happen,  without the example part of course, because this one need human action if API change

Yes. We have two options:

wait for next lvgl 6.x release (I'm preferring this solution)
release v2.0.0 with Master branch from lvgl and then v2.0.1 after new lvgl 6.x release

I'm searching for a way to do some automation, but my github-fu seems to be too weak :-( so if anybody can give me a hand...

about automation I would be happy to help - I think the idea would be:
Once you have a script that automate the task :

you can use travis and the
- if [ -n "$TRAVIS_TAG" ]; then something when tag set; fi feature to launch this script (I use it on one project to generate binary when doing a release
)
and then use this feature also to push your commit to lv_arduino repository and/or  any other repository using thisfor example :
https://gist.github.com/Maumagnaguagno/84a9807ed71d233e5d3f

The master branch is always kept stable -  I would suggest releasing now.

@Pablo2048 Maybe I missed the explanation but why can we have an Arduino release for v6.0?

@kisvegabor Arduino Library manager work only with Releases so without doing an lv_arduino release, users have to install the library manually.
@luc-github Thank You - I'm new to travis so I need some time to get familiar with it
@embeddedt Ok, if there is need, I'll do an release for version 2.0.0

Release v 2.0.0 done...

thank you ^_^

Awesome! :slightly_smiling_face:


Prerender error

How to fix?

These are dependent on Sanity as a CMS. I'll add documentation on this soon.
Once you have signed up for Sanity, you have to set the environment variables (see .env.example), the schemas for Sanity are included in the code base, so you should be able to just use those to get up and running. You can access your Sanity Studio running locally on http://localhost:3000/studio.
Let me know if you need any further help with this.


Cannot compile as std++14 in Xcode

When using this in a project which is c++14 code I get the following error:
In file included from /usr/local/include/opentracing/propagation.h:5:
In file included from /usr/local/include/opentracing/util.h:13:
/usr/local/include/opentracing/expected/expected.hpp:829:19: error: no matching member function for call to 'construct_error'
contained.construct_error( error.value() );
^~~~~
/usr/local/include/opentracing/expected/expected.hpp:1206:16: note: in instantiation of function template specialization 'opentracing::expected<void, std::__1::error_code>::expectedstd::exception_ptr' requested here
return make_unexpected_from_current_exception();
^
/usr/local/include/opentracing/expected/expected.hpp:157:10: note: candidate function not viable: no known conversion from 'const std::exception_ptr' to 'const error_type' (aka 'const std::__1::error_code') for 1st argument
void construct_error( error_type const & e )
^
/usr/local/include/opentracing/expected/expected.hpp:162:10: note: candidate function not viable: no known conversion from 'const std::exception_ptr' to 'error_type' (aka 'std::__1::error_code') for 1st argument
void construct_error( error_type && e )
^
1 error generated.
Apple LLVM version 8.1.0 (clang-802.0.42)
Target: x86_64-apple-darwin16.7.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

Could you attach the smallest file you can that reproduces the problem?

This is the simplest I can make it.
#include <opentracing/tracer.h>
int main()
{
return 0;
}
Compiled with:
clang++ -isystem /usr/local/include  -g   -std=gnu++14 -o main.cpp.o -c main.cpp

This doesn't look well formed to me:
auto make_expected_from_call( F f,
nsel_REQUIRES( ! std::is_same<typename std::result_of<F()>::type, void>::value )
) -> expected< typename std::result_of<F()>::type >
{
try
{
return make_expected( f() );
}
catch (...)
{
return make_unexpected_from_current_exception();
}
}
make_expected must return a expected<T, std::error_code>
make_unexpected_from_current_exception has to return expected<T, std::exception_ptr>
That is how I understand it. I can only assume that prior to 14 it was casting the exception_ptr to an error_code some how?

From looking at https://github.com/ned14/Boost.Expected/blob/master/include/boost/expected/expected.hpp
they seem to have solved it by specialising make_expected for the error type exception_ptr.


Use github actions to deploy docs

Currently, we're using some Condé processes that are being deprecated internally, since this documentation is an upload to an S3 bucket, porting this is pretty easy 😄

@gmedina I think in order to merge this we need to add some AWS secrets to the github actions environment. You have this, ya?


JSX SyntaxError breaks this plugin

I've set it up in my test project according to the Usage section and when I try a reference error as in the example, it works correctly. However, if I for example remove random closing tag in JSX, things break:

If you look at the second image, the weird part is
GET https://localhost:3000/babel/parser/lib/index.js 404 (Not Found) which is requested from "node_modules/react-error-overlay". this breaks things. If I create similar SyntaxError in a create-react-app test app, this doesn't happen and a proper Failed to compile error appears in the overlay. Any ideas?

@mnlj this problem may because of terminal color character
use /(\u001b\[\d*m)/g can replace color character

Thanks for the update @tungpin, feel free to submit a PR to fix this problem.

Looks like it is fixed, feel free to reopen.


Add build info to README.

#286

@timmylicheng you may need to close and reopen PR to trigger the CI again.

Merged. Thanks for contributing this, @timmylicheng!


Removed  and  as per the TODO's

some files has #include <iostream> and using namespace std; which were marked to be removed, this branch does the same.

Thank you, merging this after a quick check if we have forgotten "std::" other places in these files.


factor: Fix "resource:work" pointing to store

Description of changes
The necessary changes to io.pathnames absolute-path did not end up in the final factor image. Build a local boot image and bootstrap factor twice to make it contain all build modifications.
Fixes #212254
For quick verification, run:
M\ string absolute-path see

which prints the definition of absolute-path. It must contain a case for resource:work pointing to /var/lib/factor.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2252

@ofborg build factor-lang

Please rebase

merged as https://github.com/NixOS/nixpkgs/commit/5cd9b4264517ffba734556969d9d25ebeea55310 through some hickup at github

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/factor-language-factor-lang-on-nixos/37246/4


Delete manifests/j/JanDeDobbeleer/OhMyPosh/7.59.6 directory

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.2 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@wingetbot run


Is it possible to extent the qr code to fill the canvas

I have a responsive design, the size of the canvas where I want to show the QR code can vary. How to I make the QR code the same size as the canvas.
I've tried setting the width and height to:

auto: Error: The provided double value is non-finite.
0: Error: The canvas is too small
10000: QR code is now to big for the canvas
Not at all: Generates at default size

Has anybody another suggestion?

A solution that worked for me was generating a fixed size canvas, i.e. 300x300, and applying CSS scaling to it, which dynamically updates to fill it in w/ the parent node.
https://developer.mozilla.org/en-US/docs/Web/CSS/transform-function/scale

A solution that worked for me was generating a fixed size canvas, i.e. 300x300, and applying CSS scaling to it, which dynamically updates to fill it in w/ the parent node.
https://developer.mozilla.org/en-US/docs/Web/CSS/transform-function/scale

Hey @jzombie do you have a codesandbox for the solution you mentioned? I couldn't make it work


Convert closures to arrow functions

[x] Changes have been thoroughly tested to not break existing functionality.

This PR converts traditional closures to arrow functions, resulting in cleaner and consistent code style throughout Filament code base.
Used tool:

Rector 0.17.3 (with ClosureToArrowFunctionRector rule) for refactoring
Laravel Pint 1.10.6 for formatting

Each change was verified manually before being applied.

i think the readability is not as good

i think the readability is not as good

Most closures in code base are already written using arrow functions, even in documentation. This PR converts remaining traditional closures to make coding style consistent.
For readability, I don't think it's a big issue because we spend most time working without custom code, not the packages.

This PR converts remaining traditional closures to make coding style consistent.

using arrow function is just convenience

For readability, I don't think it's a big issue because we spend most time working without custom code, not the packages.

you are not wrong, but there are times code dive helps to understand how it works in the package to build own app/suggest features/bug fix etc.

For readability, I don't think it's a big issue because we spend most time working without custom code, not the packages.

Speak for yourself, I have to read it and maintain it 😅 I wrote full closures in these places for readability, so the lines aren't too long
Sorry, but not gonna merge this one


lxd/logging: Handle projects in log expiry

Closes #6910
Signed-off-by: Stéphane Graber<EMAIL_ADDRESS>

Testsuite passed


fix(timer-controller): Fixing bug for browsers

:tada: This PR is included in version 7.1.7 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


Defining explicit default_security_list expects to define display_name

When defining explicitly a default_security_list in a VCN (to have the absolute control of the entries on it with the JSON config), it is expecting a display_name, not defined in the variables.tf of the orchestrator:
Error:

Error: Unsupported attribute
│
│   on networking.tf line 42, in locals:
│   42:               display_name   = vcn_value.default_security_list.display_name
│     ├────────────────
│     │ vcn_value.default_security_list is object with 6 attributes
│
│ This object does not have an attribute named "display_name".
╵

orchestrator variables.tf:

default_security_list = optional(object({
          compartment_id  = optional(string),
          compartment_key = optional(string),
          defined_tags    = optional(map(string)),
          freeform_tags   = optional(map(string)),
          ingress_rules = optional(list(object({

fix with:

        default_security_list = optional(object({
          compartment_id  = optional(string),
          compartment_key = optional(string),
          defined_tags    = optional(map(string)),
          freeform_tags   = optional(map(string)),
          **_display_name    = optional(string),_**

Added the workaround. However this needs to be translated to the networking core module team as it is not taking the default security list display name desired.


squidExtLogFormat: typo

Hi!
looks like a little typo?
ref. https://forum.opnsense.org/index.php?topic=26593.msg130828#msg130828
thanks!

@kulikov-a thanks!


updated blobs

updated  blobs

re run not allowed

and dont do force push

Oh sorry sir didn't know that


OSX Installer: /usr/local/bin does not allow read or execute for anyone except owner

OS: OSX 10.11.1
bits: 64
route: mac installer
error: unable to execute any of the elm binaries after installation completes successfully
This was a rather clean OSX install and I did not yet have a /usr/local/bin directory.  The installer created it, however the installer did not give read or execute access to anyone except the owner.  A simple chmod 755 on /usr/local/bin fixed the issue.

Is this still happening with the current version of Elm?

I'd feel uncomfortable running chmod on peoples stuff. I suspect people set it different ways for different reasons. I'd want to get some consensus on elm-dev or on the Elm slack channel before making a change like this. Don't know enough to be confident what's the right thing!


When running the command to connect to exchange online it fails

Reference: https://learn.microsoft.com/powershell/exchange/connect-exo-powershell-managed-identity#step-3-store-the-user-assigned-managed-identity-in-a-variable
Connect-ExchangeOnline -ManagedIdentity -**Organization** **<YourDomain>**.onmicrosoft.com -ManagedIdentityAccountId <UserAssignedManagedIdentityClientIdValue>

I added the respective values but it seems the Organization value is not good and returning:
Failed to acquire managed identity token:
System.Net.Http.HttpRequestException: A socket operation was attempted to an unreachable network. (<IP_ADDRESS>:80)
 ---> System.Net.Sockets.SocketException (10051): A socket operation was attempted to an unreachable network.
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
   at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|281_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(QueueItem queueItem)
   at System.Threading.Tasks.TaskCompletionSourceWithCancellation`1.WaitWithCancellationAsync(CancellationToken cancellationToken)
   at System.Net.Http.HttpConnectionPool.HttpConnectionWaiter`1.WaitForConnectionAsync(Boolean async, CancellationToken requestCancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
   at Microsoft.Exchange.Management.AdminApiProvider.Authentication.ManagedIdentityTokenProvider.GetAccessTokenAsync(String claims, String cmdletId)
OperationStopped: A socket operation was attempted to an unreachable network. (<IP_ADDRESS>:80)

Connect-ExchangeOnline -ManagedIdentity -Organization .onmicrosoft.com -ManagedIdentityAccountId
I added the respective values but it seems the Organization value is not good and returning:
Failed to acquire managed identity token:
System.Net.Http.HttpRequestException: A socket operation was attempted to an unreachable network. (<IP_ADDRESS>:80)
---> System.Net.Sockets.SocketException (10051): A socket operation was attempted to an unreachable network.
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
at System.Net.Sockets.Socket.g__WaitForConnectWithCancellation|281_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(QueueItem queueItem)
at System.Threading.Tasks.TaskCompletionSourceWithCancellation1.WaitWithCancellationAsync(CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.HttpConnectionWaiter1.WaitForConnectionAsync(Boolean async, CancellationToken requestCancellationToken)
at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpClient.g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
at Microsoft.Exchange.Management.AdminApiProvider.Authentication.ManagedIdentityTokenProvider.GetAccessTokenAsync(String claims, String cmdletId)
OperationStopped: A socket operation was attempted to an unreachable network. (<IP_ADDRESS>:80)

@speerbux, verify that you're using the latest version of the module (v3.3.0) if you aren't already. After that, you should open a support ticket.

@speerbux Hope this comment is helpful for you. Considering the nature of the issue, as advised, please open a service ticket in your tenant and follow with them for the resolution. You can contact Microsoft support via the need help section on the admin center. We proceed to close it as here we are limited to documentation fixes and improvements only.
We will be very happy if you can share the outcome or resolution with us if you see documentation update is required. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

thank you @chrisda  and @yogkumgit


Incorrect result for divide by zero

In ScalaFiddle, a divide by zero operation returns 0 when the numerator and denominator are both integers.
https://scalafiddle.io/sf/QHrybLv/1

This is due to JS semantics and how some things are not checked by Scala.js due to performance reasons. http://www.scala-js.org/doc/semantics.html