Domestic Scan fails with 'EC Key not found'

When scanning a domestic QR code freshly generated through the NHS App, the QR code is not validated as expected.
Steps to repro:

Log in to the NHS App
Navigate to 'Get you NHS COVID Pass'
Choose 'Continue'
Choose 'Event Trials'
Scan the resulting QR code using this app

Expected: That _qrDecoderService.ValidateQrCode(result.Text) (QRScannerViewModel line 125) would return true.
Observed: The return value is false.
The following is present in the log:
[ZXing.Net.Mobile] Barcode Found
[0:] Logged ERROR:
[0:] {
[0:]    Severity: ERROR:
[0:]    AdditionalInfo: Error[QrECValidatorService] ValidateQrCodeForCertificate:
[0:] }
[0:] With exception [Exception]: EC Key not found
[0:]   at NHSCovidPassVerifier.Services.Repositories.QrECValidatorService.ValidateQrCodeForDomesticCertificate (System.Byte[] digest, System.Byte[] signature, System.String header) [0x000b0] in C:\dev\covid-pass-verifier\NHSCovidPassVerifier\Services\Repositories\QrECValidatorService.cs:41

Device: Galaxy Note 20 ultra 5G running Android 11
Additional Information: At first glance, the QR data looks somewhat valid - the Key corresponds to one returned by the certificates endpoint, and the payload looks ok. So I guess it's a bug somewhere in how the sig is validated.
The root cause of the issue is that on line 99 of QrECValidatorService.cs we retrieve the list of keys from secure storage - however this is empty. This means the key is never going to be found, which means the sig will never be verified. I'm guessing the keys haven't been downloaded!

Resolved: The URL for the JWK service needs to be present in Configuration/appsettings.json
Suggestion: Update the documentation outlinging configuration keys required for the app to function correctly.
Suggestion: If the key list is empty, and the user hits 'Check a 2D Barcode' on the main page, we should show a spinner whilst we perform an initial download of the keys. If this fails, the user should be informed and returned to the main page.
Happy to to a PR for either of these...?


Add Compliance check: preventLandingSensitiveCommits

How the Check Works
Provide a clear definition based on the spreadsheet
Pending Tasks
You can find more details in the contributing guide

[ ] 1. Define a Good Implementation Example

[ ] Read the documentation (guidelines, best practices...)
[ ] Brainstorm how to implement this check (logic, alerts, tasks, validations, edge cases...).
[ ] Achieve an agreement on the implementation details before starting to work on this.

[ ] 2. Update Check Record Example

[ ] Update the compliance_checks row with the following fields: how_to_url, implementation_status, implementation_type and implementation_details_reference
[ ] Check the migration scripts using npm run db:migrate and npm run db:rollback
[ ] Update the database schema by running npm run db:generate-schema

[ ] 3. Implement the Business Logic Validator Example and Check Example

[ ] Add the specific validator in src/checks/validators/index.js
[ ] Add the check logic in src/checks/complianceChecks
[ ] Ensure that the check is in scope for the organization (use isCheckApplicableToProjectCategory)
[ ] Ensure that the severity value is well calculated (use getSeverityFromPriorityGroup)
[ ] Add the alert row in the compliance_checks_alerts table when is needed.
[ ] Add the task row in the compliance_checks_tasks table when is needed.
[ ] Add the result row in the compliance_checks_results table.

[ ] 4. Ensure It Works as Expected

[ ] Add new unit tests for the validator check.
[ ] Add new integration test cases for this check.
[ ] Verify that all tests are passing.
[ ] Run the command check run --name {check_code_name} and verify the changes in the database. Update the seed script if needed (npm run db:seed)

[ ] 5. Update the website Example

[ ] Review the current content it in https://openjs-security-program-standards.netlify.app/details/{check_code_name}
[ ] Create a PR in https://github.com/secure-dashboards/openjs-security-program-standards to include how we calculate this check and include additional information on the mitigation if needed.

Similar to https://github.com/OpenPathfinder/visionBoard/issues/67#issuecomment-2543265159, but in this case we will focus on this criteria:
Organization-Level Validation

secret_scanning_push_protection_enabled_for_new_repositories = true

Repository-Level Validation

secret_scanning_push_protection_status = enabled
secret_scanning_validity_checks_status = enabled


Transfer maintenance rights to The Foreman

[x] Transfer GitHub repo
[x] Transfer Rubygems release rights

Hi @sandfoxme, I can help with the repo transfer. I'm sending you a org invite, once you've accepted you should be able to transfer the repo to the "theforeman" namespace. I can restore admin privs for you and @lzap after that.

Could you also add<EMAIL_ADDRESS>as an author on the respective rubygems please?

done

Thanks! I've added you and @lzap to repo with admin rights, and added @lzap to the rubygem.


fix(Request): Make wsgi.input wrapper more robust

Fix two bugs with the wsgi.input wrapper that is used to normalize
behavior between wsgiref and production-class web servers:

Do not hang when reading with a size < Content-Length but the
stream has already been consumed.
If Content-Length is invalid or missing, assume no content and
still wrap the stream, rather than sometimes wrapping and sometimes
not.

Also, improve the tests to more cleanly shut down the wsgiref server
between tests so that the above can be tested in a more modular
fashion.

LGTM, @kgriffs

I'll merge if you rebase. ;-)

@fxfitz Thanks, rebased.


add print and online ISBNs to CounterBook

CounterBook should be able to track print and online ISBN (delimited reports only have "ISBN" field but SUSHI distinguishes them)

Fixed in 25dac6a51d24bcb1bf4ee8b3d5ef32b2b17e4a6f


[Discussion] Why does the button to post a comment in the comment pane say "Save"?

This is a minor thing. Unless I'm mistaken, the comment pane works like a "chatroom". However, the first time I try to use it, I am very confused about how it works. The "save" button gives me a feeling that I am saving a note or some important info, not sharing thoughts with others. I would suggest using "Comment" or "Post" instead.

The button now says "comment" instead of "save":


Prepare for OpenShift AI 2.13.0 RC1 regression testing

OpenShift AI 2.13.0 RC1 is available for Regression Testing.

This is attempt to launch the smoke test for RHOAI 2.13.0 RC1 in the OpenShift CI cluster just to make sure there isn't any functional issue.
/test rhoai-light kserve vllm_cpt_single_model_gating_light

CI Job is successful.

thanks Charan, good to merge.
Please, when sharing the test link, give the URL to the report index, or anything more relevant to the PR

I merge this PR, so that I can put mine on top of it.


Improve script

closes https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/10041

@dstrome Hello David, I see the script has an author defined, do we need their approval here? Thank you

@dstrome
PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


Fix lib_strings_str_util_test on Windows

Can one of the admins verify this patch?

@tensorflow-jenkins test this please.

@tensorflow-jenkins test this please.


Drop down

Reasons for making this change
[Please describe them here]
If this is related to existing tickets, include links to them as well.
Checklist

[ ] I'm updating documentation

[ ] I've checked the rendering of the Markdown text I've added

[ ] I'm adding or updating code

[ ] I've added and/or updated tests
[ ] I've updated docs if needed
[ ] I've run npm run cs-format on my branch to conform my code to prettier coding style

[ ] I'm adding a new feature

[ ] I've updated the playground with an example use of the feature

I'm closing this PR as it seems to be a mistake, but let me know @Ashwithabg if otherwise.


polygon winding direction

The current spoly in pgsphere is allowed to be clockwise or counter clockwise and the "inside" is the smaller side of the boundary.
In the IVOA community, where postgresql+phsphere is used inn many places, the DALI standard specifies polygon as always counter clockwise with the "inside" on the left (https://www.ivoa.net/documents/DALI/20170517/REC-DALI-1.1.html#tth_sEc3.3.7). The reasons for that choice were well justified by use cases identified by the authors (me and others); I will add that material or a link in a subsequent post on this issue if needed.
The issue is that the pgsphere behaviour trips many implementers up because it is subtle and basic tests/trials work fine and the discrepancy show sup after they'd ingested a lot of data. I don't know what the solution is for this, but I'd like to start a discussion on this issue and try to find one that works. Basically, your users are often implementing IVOA standards and I think we both want that to be as easy and straightforward as possible.

On Tue, Jul 20, 2021 at 8:47 PM Patrick Dowler @.***>
wrote:

The current spoly in pgsphere is allowed to be clockwise or counter
clockwise and the "inside" is the smaller side of the boundary.
In the IVOA community, where postgresql+phsphere is used inn many places,
the DALI standard specifies polygon as always counter clockwise with the
"inside" on the left (
https://www.ivoa.net/documents/DALI/20170517/REC-DALI-1.1.html#tth_sEc3.3.7).
The reasons for that choice were well justified by use cases identified by
the authors (me and others); I will add that material or a link in a
subsequent post on this issue if needed.
The issue is that the pgsphere behaviour trips many implementers up
because it is subtle and basic tests/trials work fine and the discrepancy
show sup after they'd ingested a lot of data. I don't know what the
solution is for this, but I'd like to start a discussion on this issue and
try to find one that works. Basically, your users are often implementing
IVOA standards and I think we both want that to be as easy and
straightforward as possible.

I agreу with that issue, so what is your suggestions ? One straightforward
solution is to have DALI compatible polygon  'vopoly' and let user use it.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/postgrespro/pgsphere/issues/2, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQURYQJFBGMTZMHDRNEKMLTYWZEBANCNFSM5AWITJKQ
.

--
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

Sorry for taking so long to reply - it has been a busy few months.
Yes, I think a 'vopoly' type with compatible behaviour would be a good way to go; users could decide if they require the different behaviour/semantics and chose beteen spoly and vospoly.
On the implementation side, because 'vopoly' has a specified winding direction, it can be larger than half the sphere; there are some use cases for having a value that means and behaves (in queries) like "all sky".

A final thing (probably just to keep in mind but not necessarily implement): we will be publishing a new draft of DALI that supports a couple of new constructs:

multipolygon is a set of disjoint simple (vopoly) polygons (needed to describe some kinds of observation footprints)
shape is a polymorphic type that is sometimes needed when combining data from multiple missions
In both of these cases, I have been able to implement these effectively with a combination of existing functionality so I don't think pgsphere needs to support them, but if it turned out these were more generally interesting and effected some implementation decisions then we could think about them.

On Wed, Nov 08, 2023 at 01:05:33AM -0800, Christoph Berg wrote:

Does this need a new type? We could say that from some release,
polygons are all left-winding, and fix all the operators to follow
that convention. We'd supply a conversion function what would
convert all right-winding polygons to left-winding ones that users
could call as part of the upgrade.

Hm.  I'd say that's at least a really dangerous thing to do if it
will silently turn small right-winding polygons into almost full-sky
left-winding polygons.  It is not hard to imagine the resulting
symptoms: A query that before was fast and returned a few rows then
is slow and returns huge result sets.  And that's the best scenario
because it'll be easy to notice something is wrong.
With sufficient warning, we might still want to pull it off.  We could
hope that pgsphere adopters are the kind of people that read release
notes, in particular if we make this a major version.  But I can't
say I'd not wish there was a better solution.
Perhaps we can put in a magic automatic migration, i.e., see if a
polygon is of the old, smaller-than-2-pi kind and turn it
left-winding behind the scenes, perhaps even transparently on-disk?

I agree that magic conversion to the specified winding direction would be undesirable as it wouldn't allow for larger than half the sphere vopoly and would probably hide bugs in s/w that generates small polygons incorrectly.
A migration mechanism for existing content would be a nice thing for operators. I would envision that as part of an alter table statement that changed the datatype of a column from spoly to vopoly. Then people chose it and in that context there would be nothing ambiguous or surprising about converting values to left-winding.

I am taking note of this issue, as suggested by @msdemlei when discussing possible ESDC contributions to pgsphere at ADASS 2023.

Perhaps we can put in a magic automatic migration, i.e., see if a polygon is of the old, smaller-than-2-pi kind and turn it left-winding behind the scenes, perhaps even transparently on-disk?

spoly is a varlena type so there is room in there to stuff in extra flags. That can help make upgrading not rewrite all right-winding polygons.
But an automatic on-the-fly upgrade doesn't help with application bugs - if the app continues to put in right-winding polygons and still expects them to be "small", the database will start interpreting them as "big", and the problems are as hard to find as before.
Even a new type won't prevent this problem, if people swap in new columns with a new type, but using the old name and syntax, old apps will happily write correct or incorrect data as they like.
There will have to be a flag day where the database and all apps get switched over. (And if a new type doesn't help, we might just try to keep using the old one with better semantics.)
Related problem: scircle with radius > π/2.

Definitely, polygons should be oriented on the sphere, otherwise there will be some inconsistency in defining polygons. I like the idea to add a hint to spoly. By default, all the polygon data will be interpreted as it is now. We may add an optional parameter to spoly constructor. This parameter will define the input polygon data orientation: left, right or undefined orientation. By default, the undefined orientation will be used (the current behaviour). We may also introduce a new function vopoly which will interpret input data as left oriented polygons.


remove using SIGSEGV, SIGBUS, SIGILL from engine/esma_template

I see we have a lot of duplicate code:
if (str_3_cmp(p, 'F', 'P', 'E')) {
	eti.ch_data = SIGFPE;
	state = st_trans_semicolon;
	break;
}

if (str_3_cmp(p, 'H', 'U', 'P')) {
	eti.ch_data = SIGHUP;
	state = st_trans_semicolon;
	break;
}

Each signal in POSIX has a code other than zero. It seems to me that we can do in each case only by setting the signal number, and do all the other actions after leaving the switch. Then each case statement wil be like:
if () {
	eti.ch_data = SIG1;
}
...
if () {
	eti.ch_data = SIGN;
}

break;

After the operator, we may well be able to determine the error by the variable eti.ch_data.


Batch Edit stuck when changing permissions

Go to dashboard
Select 2 files
Click Edit Selected
Click Permissions
Change the permissions (e.g. from public to private)
Click Save Changes
The system gets stuck and the permissions are not updated

Test case https://scm.dlt.psu.edu/issues/3726

This is what is reported in the logs
2015-04-03 14:34:26 -0400 (22938) Completed 500 Internal Server Error in 273ms
2015-04-03 14:34:26 -0400 (22938)
NoMethodError - undefined method `permit' for nil:NilClass:
  hydra-editor (1.0.2) app/forms/hydra_editor/form.rb:57:in `sanitize_params'
  hydra-editor (1.0.2) app/forms/hydra_editor/form.rb:49:in `model_attributes'
  sufia (6.0.0) app/controllers/concerns/sufia/batch_edits_controller_behavior.rb:87:in `generic_file_params'
  sufia (6.0.0) app/controllers/concerns/sufia/batch_edits_controller_behavior.rb:50:in `update_document'
  hydra-batch-edit (1.1.1) app/controllers/concerns/hydra/batch_edit_behavior.rb:39:in `block in update'
  hydra-batch-edit (1.1.1) app/controllers/concerns/hydra/batch_edit_behavior.rb:37:in `update'
  sufia (6.0.0) app/controllers/concerns/sufia/batch_edits_controller_behavior.rb:58:in `update'

The culprit seems to be this line in Sufia: https://github.com/projecthydra/sufia/blob/master/app/controllers/concerns/sufia/batch_edits_controller_behavior.rb#L87
The code to validate the attributes only accounts for fields passed when updating the "Descriptions" tab but not the case where the user edits the "Permissions" tab.
Then editing the permissions tab there is no params[:generic_file] and the code blows up in Hydra Editor (https://github.com/projecthydra/hydra-editor/blob/master/app/forms/hydra_editor/form.rb#L63) since there is no permit method in nil.

The change is the check in generic_file_params to make sure we don't pass nil to model_attributes
    def generic_file_params
      file_params = params[:generic_file] || ActionController::Parameters.new()
      Forms::BatchEditForm.model_attributes(file_params)
    end


github action repo compliance

I was wondering if there is any github action ready to be use to check for repository compliance? That would be helpful to deploy on both Canonical and Ubuntu organization, to know in adjust repository settings when they are needed and have some continuous check.

The first time you'll try to run anything on the hosted runners, if anything is misconfigured you'll get a failed "setup runner" step. An extra action would be redundant I guess.
If I may add my wish, it would be to have a tool, that goes and checks the repo and its configuration for compliance.

@jdkandersson is this issue still relevant?


p2p and rpc: a few misc fixes

Log to a file in lightchain_shell
Rename Peer.stop_and_wait_until_finished() to stop()
lightchain.py, lightchain_shell.py and rpc/server.py now connect to ropsten by default
peer.py no longer takes a db/mainnet arg as it no longer handles sync

I guess you mean docs for rpc/server.py? I'll add them tomorrow

:shipit: when ready.


Command verification failed with add-sig with 2+ signers

This regression is possibly related to #943, or it might be because pact add-sig is now outputting a json instead of a yaml, not exactly sure.
With the following file test.yaml:
code: |-
  (+ 1 1)
publicMeta:
  chainId: "0"
  sender: k:c8b4eac774c5ccdfdba1a5ed659f32a50b97ea5342b420469fa960e4f300e0c7
  gasLimit: 5000
  gasPrice: 0.00000001
  ttl: 28800
networkId: "testnet04"
signers:
  - public: c8b4eac774c5ccdfdba1a5ed659f32a50b97ea5342b420469fa960e4f300e0c7
  - public: 11dce1759df5d684dd559cbd17d45ef3038563700a3e57cf57fff93f8e5c3b21
    caps:
      - name: coin.GAS
        args: []
type: exec

The following commands work fine in pact v4.1.1 to sign it with two keys:
pact -u test.yaml > unsigned.json
cat unsigned.json | pact add-sig key1.yaml > signed1
cat unsigned.json | pact add-sig key2.yaml > signed2
pact combine-sigs signed1 signed2

In pact v4.2.0, the second line, pact add-sig key1.yaml returns:
Command verification failed!
Invalid command: Number of sig(s) does not match number of signer(s)

The same error is thrown with cat unsigned.json | pact add-sig key1.yaml key2.yaml (which also worked fine in v4.1.1).

Currently we're facing the same issue in pact 4.2.0. Is there a way to install back pact 4.1.1?

You can install old versions by downloading from https://github.com/kadena-io/pact/releases

Closed by #981


Suggestion: better graphics for multiple result sets in the results pane

Azure Data Studio Version:
1.14.1
Steps to Reproduce:
Execute multiple queries in a single batch, look for visual queues, missing borders, spacing, mismatched scroll bars, other legibility issues in the output window

Unfortunately replacing the grid is more of an investigation at the moment and not a priority.


Prepare rancher-external-ip-webhook chart for 2.7.0

rancher-external-ip-webhookchart needs to be updated the charts for 2.7 by

File a PR removing the doNotRelease flag form the package.yaml; in this PR, you will also want to make any changes that need to be made to update the chart to the version you intend to release in 2.7. For example, for a charts like rancher-aks-operator / rancher-gke-operator / rancher-eks-operator, you will need to create a new branch in upstream for Rancher 2.7, cut the first release for that chart, and introduce those changes in to the package.yaml as well before removing the doNotRelease flag

To make your chart available for 2.7, almost every chart will also have to modify the Rancher Version annotations that scope it to 2.6, i.e. https://github.com/rancher/charts/blob/2e058e93ee01f2980e4750148842dd7f04262b38/charts/fleet-agent/100.0.5%2Bup0.3.11/Chart.yaml#L8

Once the PR is merged, ensure that the brand new chart is smoke tested by QA/dev

To validate

Deploy v2.7.0-rc3 on k8s v1.21 (can be done via AWS cluster)
Install External IP Webhook into the local cluster

Apps -> Charts -> Search External IP Webhook
Leave configuration options empty

Verify chart versions are
    rancher-external-ip-webhook:     101.0.0+up1.0.1

Moving this out from test because we need to remove from 2.7.

To validate

On 2.6.8 - verify this chart is available on the local cluster.
on 2.7-head, verify this chart doesn't show up.

I validated this card on both v2.7-head and v2.6.8 and seeing below observations:

On v2.7-head -- I am seeing the app "External IP Webhook" on my local cluster
On v2.7-head ->Local cluster->Apps-> "External IP Webhook" : I did not see a version with rancher-external-ip-webhook: 101.0.0+up1.0.1

Installed Versions:
a. RANCHER_CHART_VERSION=2.7.0-rc3
b. RANCHER_IMAGE_TAG=v2.7-head
c. RKE VERSION= v1.4.0-rc3

On v2.6.8 -- I am NOT seeing the "External IP Webhook" on my local cluster

Installed Versions:
a. RANCHER_CHART_VERSION=2.6.8
b. RANCHER_IMAGE_TAG=v2.6.8
c. RKE_VERSION=v1.3.13

I revalidated the ticket on v2.7.0-rc3 and I did not see the app "External IP Webhook".
I am closing this ticket.


Baseline more features

Thoroughly re-baseline the set of features that are not accepted by older compilers and therefore cannot appear unguarded in .swiftinterface files. The only features which require guards at this point were introduced in late Spring 2024.

@swift-ci please test

Awesome!

@swift-ci please smoke test

@swift-ci please smoke test


pilot: fix treating spontaneous request as ACK

Fixes https://github.com/istio/istio/issues/51612
What is happening here is we get a request from Envoy without Nonce set. We end up setting Acked="". Then, istioctl ps sees sent=some-nonce, acked="" and thinks it is STALE; its not.
Instead, we should not reset the Acked var when its not a real ACK.
This PR fixes this issue and adds a test case.
I am fairly sure this fixes https://github.com/istio/istio/issues/51165 as well, not but 100%
Easy manual reproducer is to apply a Gateway to an otherwise empty cluster, then remove it. 45s later the listener will drain and RDS will start reporting as stale

In response to a cherrypick label: #52278 failed to apply on top of branch "release-1.22":
Applying: pilot: fix treating spontaneous request as ACK
Using index info to reconstruct a base tree...
M	pilot/pkg/xds/delta.go
M	pilot/pkg/xds/delta_test.go
Falling back to patching base and 3-way merge...
Auto-merging pilot/pkg/xds/delta_test.go
Auto-merging pilot/pkg/xds/delta.go
CONFLICT (content): Merge conflict in pilot/pkg/xds/delta.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 pilot: fix treating spontaneous request as ACK
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to a cherrypick label: new issue created for failed cherrypick: #52298

In response to a cherrypick label: new pull request created: #52299


YJAF Access Renewal

Use this issue template if you do not feel comfortable raising a PR with the required changes to files in the terraform/ directory.
Please supply all the requested information, so that your request can be processed as quickly as possible.
Which MoJ repository/s are you requesting access to (e.g. money-to-prisoners)?
yjaf-assets
yjaf-auth
yjaf-bands
yjaf-bed-unlock
yjaf-case
yjaf-cmm
yjaf-conversions
yjaf-dal
yjaf-datateam
yjaf-documents
yjaf-gateway
yjaf-gateway-proxy
yjaf-mule-hub-connector
yjaf-placements
yjaf-refdata
yjaf-returns
yjaf-sentences
yjaf-serious-incidents
yjaf-transfers
yjaf-transitions
yjaf-ui
yjaf-views
yjaf-workflow
yjaf-yp
yjsm-hub
yjsm-hubadmin
yjsm-hub-svc
yjaf-mule-miss-processor
What is the GitHub username of the person who needs access?
ttipler
What is their full name?
Thomas Tipler
What is their email address?
<EMAIL_ADDRESS>What company/organisation do they belong to (e.g. "Department for Education")?
NEC (YJAF)
What level of access should they have?

[ ] Read
[ ] Triage
[ ] Write
[ ] Maintain
[x] Admin

Why is this access being requested?
Currently devops - requesting access to be granted & extended to "review date" below
Which MoJ team/person is responsible for this request? This must be a ".justice.gov.uk" or ".digital.justice.gov.uk" email address.
This should be an email address<EMAIL_ADDRESS>Team email addresses are preferred, rather than individual email addresses, to make it easier to follow-up at a later date.
<EMAIL_ADDRESS>Review date
Date after which this collaborator's access should be reviewed. This should be a date in the format: 2021-01-15, no more than one year into the future from today.
01/09/2024

Awaiting approval from Business Owner


Update README for lazy.nvim package manager

lazy.nvim seems to be the state-of-the-art package manager for neovim nowadays, even the Packer maintainer uses it, so it would be nice if you include an installation example for lazy (although this is trivial, it makes it easier for unexperienced users).

Sure, I'll add a small example. Thanks for your feedback!


Model Persistence

Allow users to save and load their custom-built models for later use.

@wkambale assign this to me


Added linear search in python

Have you read the Contributing Guidelines on Pull Requests?
(Write your answer here.)
Description
Added linear search in python
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
#313
(Write your answer here.)

Thanks for correcting the link in README.md :)


Delete ETAS code

ETAS is going away as of alma launch and won't come back. We can remove all the etas code.

some methods reference "etas", some reference "hathi"

On catalog.princeton.edu there are 5 works that are listed under the location online$etas

https://catalog.princeton.edu/catalog/9948595283506421
https://catalog.princeton.edu/catalog/9911897463506421
https://catalog.princeton.edu/catalog/9910009553506421
https://catalog.princeton.edu/catalog/9910407913506421
https://catalog.princeton.edu/catalog/995642993506421


Port EF6 Data Annotations tests

We want to know whether any semantics of data annotations has changed.

@AndriySvyryd Poaching this.

Assigning back to @AndriySvyryd since he has some additional tests.


Remove StdRng, switching ThreadRng to ChaChaRng.

This strategy was described in https://github.com/rust-lang/rfcs/pulls/722.
Thoughts, @nagisa?

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

LGTM +1


External load balancer for the Listener

In the document you use an internal load balancer, which makes sense as the IP should be in the same subnet as the VMs,
However, in the load balancer section type, you mention "External: Allows applications to connect to the availability group through a public Internet connection." If this is the case, Should I use the public static IP address when configuring the client access point in the cluster?
I am guessing that by "external" you mean public, because in the Portal the only options are Internal and Public as shown in the attached image

Can you provide more detail on how to set the listener when using a Public load balancer?

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

ID: 09504e18-c72f-07ee-3ef8-dc9ed44562ca
Version Independent ID: 8058bb4f-2321-ddf2-9930-0cc767b68a62
Content: Configure availability group listeners & load balancer (Azure portal) - SQL Server on Azure VM
Content Source: articles/azure-sql/virtual-machines/windows/availability-group-load-balancer-portal-configure.md
Service: virtual-machines-sql
GitHub Login: @MikeRayMSFT
Microsoft Alias: mikeray

@danvalero
Thanks for your Question! We are checking on this and will get back on this.

@danvalero Apologies for the delay in response and all the inconvenience caused because of the issue.
You should do the following:

Choose type as public and SKU as Basic/Standard(depending on their VM ip sku) while creating LB. if basic, the vms should be part of same availability set. This will create a public ip address for the LB and add it to LB front end configurations.

While creating client access point, they can choose any ip address. Anyways, We will reconfigure it in the powershell script with the LB ip address.
-When they run the powershell script for linking cluster resource probe port with LB probe port, it will reconfigure the client access point ip address to load balancer ip address.

You can create DNS name for load balancer public ip address and start using it.

Others are pretty much same as mentioned in the original doc.
Please also take a look at the document explaining how to setup external LB in detail:

Hi @danvalero , to add on to the responded provided by @psmanhas , you can associate the private IP address with the public ILB when you configure the cluster probe

Thanks!
Masha from the SQL Docs team

@danvalero Hope the provided information is helpful.
We will now close this issue. If there are further questions regarding this, please tag me in a comment. I will reopen it and we will continue the discussion.
Thanks


[bin/grav newuser] Password visible in command history

I quickly searched for this issue on GitHub, but couldn't find anything. I am new to grav development, so if I've overlooked something, just let me know.
bin/grav prompts for a password when used with the newuser parameter to add a new user as suggested in the Administration Panel Introduction. This, however, results in the password being visible in the command history of your shell. I have huge security concerns regarding this.
When prompting for a password, input should not be displayed. (Like sudo does, for instance.)
Any thoughts on this?

Is it really shown in the command history?  It's a PHP command that is running and all you would see is bin/grav newuser in your history.

@rhukster You might be right. I'm not sure if it would be possible to capture that somehow. Maybe not, but i think it already is an issue to see the password as plaintext in your current session.

I just requested for pulling my fix for this, as I don't see any reasons for not changing this behaviour. Maybe there are any?

I'm ok with this if you add some logic to repeat your password and then check the two entries are valid and match.. nothing worse than typing a hidden password field once, with a typo, and then not being able to login because you didn't type what you thought.
Thanks.

Agreed, will do so.


Nvenc Encoding can't be started

it occurs on alpha-v1.0.2

Note

I think it will be fixed on next version.

vcruntime140_1d.dll
ucrtbased.dll & more

this error solved but live is still not working.

get gpu information
[How to check if the system has AMD or NVIDIA](https://stackoverflow.com/questions/49348026/how-to-check-if-the-system-has-amd-or-nvidia-in-c)

dotnet build action resolve


update readme with information about CSS files

This PR updates the readme with information about CSS files, following the implementation of #142.

@vadekh Can you give this a once-over and see if everything is clear, or whether more information needs to be added? Thanks!


Jess Archer

I'd like to add Jess Archer to the list

https://github.com/sponsors/jessarcher

@jessarcher, can you please comment on this issue to give consent to be added to the Sponsor Open Source Dev platform?
Thank you!

Thank you @zuzana-kunckova!
I give consent :)

Hey! Sorry I missed the notifications. I'm on it! :)

👍🏼 done!

Thanks so much! 🥰


[add] happy 404 template

hope its of some value!
ps: more 404 page template coming in

that's a very creative 404 page. will surely use for the site.
Thanks for the the wonderful repository @Diptenusarkar


Use Mergin webhooks

Currently we poll Mergin in regular intervals to see if there are any changes to the project. Optionally there should be a way to listen to Mergin webhooks in case there are new data pushed to the project.

Do webhooks already exist in Mergin that I can connect into?

Do webhooks already exist in Mergin that I can connect into?

Not yet - there has not been that much interest from users so far...


Updates AppStore Review URL

In this PR we're updating the AppStore review URL.
We got reports that this wasn't working anymore in Simplenote. I managed to repro on Simplenote, but not on WPiOS.
Reference here, third answer!
Needs review: @sendhil
Thanks in advance!

I think this is ok, but you could also try something like this for Simplenote @jleandroperez  - https://github.com/wordpress-mobile/WordPress-iOS/pull/4774

:shipit:

Thanks for the tip @sendhil!!


Feature: bwlimit option on rsync processes

Hi,
this is more of a proposal for a feature. During snapshots of dir based containers, as expected rsync tries its best to occupy all the IO resources which can be a trouble. Now that snapshots are consistent due to the "initial rsync->freeze->second rsync->unfreeze" i believe rsync can safely run with --bwlimit if set- for example with "lxc config set XXXXX". creating a cgroup for rsync with limited blkio doesn't work smoothly + blkio.weight tend to work only for CFQ io elevator- same is for ionice. So the best place to control this is as a parameter of rsync. What do you think?
Cheers,
Atanas

@nakatadim from the manpage, it says taht bwlimit applies to the socket, which implies it will only ever be used when transferring over a socket (as in, over the network), not when merely copying files on the local disk.

hey, just made a test with local file copy with rsync- the file is 512M zeroed. Looks like bwlimit works on local fs too:
root@atanasdimitrov-ThinkPad-E550:/home/atanasdimitrov# time rsync -av **--bwlimit=10000** testfile testfile2
sending incremental file list
testfile

sent 537,002,103 bytes  received 35 bytes  10,228,612.15 bytes/sec
total size is 536,870,912  speedup is 1.00

**real	0m52.671s**
user	0m2.696s
sys	0m2.812s
root@atanasdimitrov-ThinkPad-E550:/home/atanasdimitrov# rm -f testfile2
root@atanasdimitrov-ThinkPad-E550:/home/atanasdimitrov# sync && echo 3 > /proc/sys/vm/drop_caches
root@atanasdimitrov-ThinkPad-E550:/home/atanasdimitrov# time rsync -av **--bwlimit=50000** testfile testfile2
sending incremental file list
testfile

sent 537,002,103 bytes  received 35 bytes  46,695,838.09 bytes/sec
total size is 536,870,912  speedup is 1.00

**real	0m10.711s**
user	0m2.452s
sys	0m2.692s

Interesting. We can probably add a new "storage.dir_rsync_bwlimit" option to use in such cases.

Sounds nice
On Dec 2, 2016 8:53 PM, "Stéphane Graber"<EMAIL_ADDRESS>wrote:

Interesting. We can probably add a new "storage.dir_rsync_bwlimit" option
to use in such cases.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lxc/lxd/issues/2678#issuecomment-264532518, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AEyY6MqPjlwXff10myGYHI3ZZaXpYTmxks5rEGk8gaJpZM4LCqt8
.


Dictionary versions with just a Git Commit SHA produce a confusing error message

F´ Version
3.1.0

Affected Component
Ref Application

Problem Description
GDS suggests upgrading when builds from a Git checkout - without tags - produce a dictionary with just a commit SHA as version, like this:
<dictionary topology="Ref" framework_version="7cb9feed0" project_version="7cb9feed0">

[ERROR] Dictionary version  is not in supported range: 0.0.0-9.9.9. Please upgrade fprime-gds.

How to Reproduce

Build the Ref app from an F´ checkout that doesn't have Git Tags in the local history
Run fprime-gds as documented in the Install guide

I have a longer-form description of the problem and how I encountered it in this blog post.
Expected Behaviour
Suggested solutions:

An error about version format instead of version range, possibly suggesting that release tags are missing
Run with a warning instead of an error when the version number can't be evaluated
Fix fprime-util so it doesn't produce invalid versions

I have it too! I thought it was due to my wobbly personal setup at the moment. 😅

I have it too! I thought it was due to my wobbly personal setup at the moment. 😅

Thanks for the "me, too!" comment. I was worried I might be reporting something only I encountered because I did something unexpected. There's a bunch of reasons people might not end up with tags in their local checkout, though.

I was just looking through the project to get a better sense of whether I could write a fix for this. Looks like there's a comment that defines the expected behavior as ignoring version strings that are not formatted with major.minor.patch.
https://github.com/fprime-community/fprime-gds/blob/48efee990481e3c152c1b0fb5a50821a07a1ca55/src/fprime_gds/common/loaders/xml_loader.py#L120-L121

I just had this happen to me, good thing I had seen this issue here before!
Yes it looks we're catching that there's an issue with the value of the version, but not really handling it (https://github.com/fprime-community/fprime-gds/blob/bbae3d6275b18706dc757a965fce8a1a4214adfd/src/fprime_gds/common/loaders/xml_loader.py#L128-L129). dict_version becomes the empty tuple, which raises the DictionaryException. We should instead detect that we're in this special case, and probably just raise a warning.
I'll get to it when I have time, but feel free to open a PR if you want to!

Moved to: https://github.com/nasa/fprime/issues/223


add binary translator key to uplink

About the PR
for 4 tc lets you hear and talk on the binary channel
obviously talking instantly outs youself as a traitor so only do it if you have a voicemask or are big troll
Why / Balance
exists in tg so why not
bit cheaper since there is no ai not as useful
Technical details
no
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes
no
Changelog
:cl:

add: The Syndicate has cracked the binary radio channel's encryption and is offering keys for 4 TC.

Still not a huge fan of one traitor getting caught with this and the HoS suddenly having access to binary but I guess that’s kind of inevitable

in ss13 and nyano rd and ce respectively have it iirc, could be added in the future so its not as wacky
also maybe a cool thing would be uplink keys get destroyed if you try to unscrew them so fill your headset with common keys and head of sus has to choose between his headset and having binary


After install jupyter extensions, it shows duplicate "Run Cell"

Environment data

VS Code version: 1.30.0
Extension version: 2018.12.1
OS and version: Windows 10 1803(17134.471)
Python version: Python 3.7.1(in env),  Anaconda 5.3.1
Type of virtual environment used: conda env
Relevant/affected Python packages and their versions: Jupyter 4.4.0

Expected behaviour

Jupyter kernel should use the interpreter of the chosen env.(Solved by install jupyter in env)
When I install Jupyter extension, the original "Run Cell" shoule be hided

Actual behaviour

The Python Interactive window shows which use the base env so that cannot find the module I use.(Solved by install jupyter in env)
Above the code "#%%", it shows "Run Cell | Run All Cells | Run cell"

Steps to reproduce:

Use the right interpreter of env by ctrl+shift+p
Write some code and add "#%%" above
Press F5/Ctrl+F5, it works
Click Run Cell, it uses the base env so that I get "No module"

@panda361 Did you happen to have @DonJayamanne's Jupyter extension installed? One of the "Run cell" links likely comes from the Jupyter extension...

We should put up a warning that Don's extension is no longer supported and not compatible with ours. We need to come up with wording.

Let's add this into my old Jupyter extension.


Merge various fixes

Current coverage is 83.78%

Merging #64 into master will increase coverage by +0.23% as of 2cc6cf6

@@            master     #64   diff @@
======================================
  Files            6       6
  Stmts          839     845     +6
  Branches         0       0
  Methods          0       0
======================================
+ Hit            701     708     +7
  Partial          0       0
+ Missed         138     137     -1

Review entire Coverage Diff as of 2cc6cf6

Powered by Codecov. Updated on successful CI builds.


Fixed Navbar & Footer

I want to

Improve Navbar style
fix animation in top box
improve style of search bar.
improve footer.
remove unnecessary youtube links.

Assign me under JWOC 2024,if approve.

@Surajit0573 any prgress?

@Priyanshi662 working on it, will PR before end of the day.


Triggering a cancellation token may not cancel a running query based on timing

When an async cancellation token is triggered, a running query is expected to be cancelled at the server; this apparently works fine when the token is triggered during ExecuteReaderAsync, or during ReadAsync.
However, if the token happens to be triggered while no SqlClient code is in progress (e.g. ReadAsync), the next time ReadAsync is called, it would simply return a cancelled Task immediately, without cancelling the query at the server. This means that there's a race condition - depending on when the token triggering happens, the query may be cancelled (if ReadAsync happens to be in progress) or it may not.
In Npgsql, we handled this race conditions by cancelling the (running) server query from ReadAsync, even when it's called with an already-cancelled token. This is being discussed in https://github.com/DapperLib/Dapper/pull/1590#issuecomment-739732477, where Dapper may be working around this issue by registering a callback to call SqlCommand.Cancel when the token is triggered - this should IMHO not be necessary.
An alternative strategy would be to continue monitoring the cancellation token originally passed to ExecuteReaderAsync - even after ExecuteReaderAsync itself has already completed. This would have the advantage of allowing immediate cancellation at the server at any point, and not only when ReadAsync is called.
For a bit more context, I wrote a small blog post on ADO.NET and cancellation.

In other words, I'm saying it may make sense to modify that check, and to immediately call SqlCommand.s_cancelIgnoreFailure if ReadAsync is invoked with a cancelled token.

I will look into that.

I agree that there shouldn't be any promise or expectation of immediate cancellation or similar; since cancellation communicates with the server, there will of course be a delay before it takes effect.

Regarding this, what happens in driver is that even though cancellation occurs > attention is sent > response is received > but driver continues to process row with large data till the end of row for 90+ seconds. There's definitely no server side delay, our test proves that. That's why there's no guarantee in the driver, that cancellation token will terminate "ReadAsync" from processing and return back control.

That's why there's no guarantee in the driver, that cancellation token will terminate "ReadAsync" from processing and return back control.

@cheenamalhotra sure. Once again, it makes perfect sense for cancellation not to be immediate. But what should be guaranteed, is that the attention (cancellation?) is actually sent by SqlClient to SQL Server - and that's not currently the case (because of the race condition described above). What happens after the attention is sent - i.e. how long before the query actually is cancelled at the server, and how many additional rows are delivered to SqlClient before the query terminates - those are all unrelated questions where there are no expected guarantees.
To summarize, this issue is about making sure that SqlClient always sends a cancellation to SQL Server when a cancellation token is triggered.

I was hoping I could rely on SqlDataReader.ReadAsync() sending the attention to the server, but it looks like I have to manually keep track of SqlCommand and call SqlCommand.Cancel() prior to disposing any reader until this bug is fixed. Thanks for the guidance!

I'm seeing this cause a wait for the entire result set inside SqlDataReader.Dispose. Instead of cancelling after the first row, this code waits for the full query (a billion rows in this case):
using Microsoft.Data.SqlClient; // 5.0.0. Same with System.Data.SqlClient on .NET Framework 4.8 too.
using System.Threading;
using System.Threading.Tasks;

public static class Program
{
    public static async Task Main()
    {
        const string longRunningQuery = @"
with TenRows as (select Value from (values (1), (2), (3), (4), (5), (6), (7), (8), (9), (10)) as TenRows (Value)),
    ThousandRows as (select A.Value as A, B.Value as B, C.Value as C from TenRows as A, TenRows as B, TenRows as C)
select *
from ThousandRows as A, ThousandRows as B, ThousandRows as C;";

        var connectionString = new SqlConnectionStringBuilder
        {
            DataSource = "(local)",
            IntegratedSecurity = true,
            TrustServerCertificate = true,
        }.ToString();

        using (var source = new CancellationTokenSource())
        using (var connection = new SqlConnection(connectionString))
        {
            await connection.OpenAsync(source.Token);

            using (var command = new SqlCommand(longRunningQuery, connection))
            using (var reader = await command.ExecuteReaderAsync(source.Token))
            {
                while (await reader.ReadAsync(source.Token))
                {
                    source.Cancel();
                }
            } // If you pause the debugger, it highlights this line
        }
    }
}

In practice, I find it blocking on SNIReadSyncOverAsync:

Can the fix be backported to .NET Framework's System.Data.SqlClient?

@jnm2 S.D.SqlClient is in servicing mode and is not accepting any fixes but security ones.


minimum and maximum length of username and password

Added four new settings used in SignupForm:
USERENA_USERNAME_MIN_LENGTH (default value: 5)
USERENA_USERNAME_MAX_LENGTH (default value: 30)
USERENA_PASSWORD_MIN_LENGTH (default value: 5)
USERENA_PASSWORD_MAX_LENGTH (default value: 30)

... and updated documentation for settings.

Nice addition to userena. However, changing the default to 5 will make a lot of current userena users scratch their heads why suddenly people can't signup with < 6 characters. It would be better to change the default value to 1 to keep al current userena install oblivious to this extra addition.

You are completely right about min length, I didn't think about that. I've also added checking that max username length is not higher than 30.


Rewrite hardcoded "magic"

Currently, there are a few items in the driver that use hardcoded register values, or other "magic" looking numbers that are meaningless or cryptic to someone not intimately familiar with the device's datasheet.

this is as complete as can be - any stragglers are due to poor/no documentation in the datasheet


Fabric Version missing on curseforge

Describe the Bug
Some good modpacks like Create Astral uses fabric and create. But for curseforge users, your flywheel fabric version isnt available on curseforge.
Reproduction Steps

...
Expected Result
Add the fabric version to curseforge.
Screenshots and Videos
No response
Crash Report or Log
No response
Operating System

What is your GPU?

Mod Version
0.6.8.a
Minecraft Version
1.18.2
Loader Version
Fabric *
Other Mods
No response
Additional Context
No response

Its not needed on curseforge create fabric bundles fabric in itself and so does forge now too


Support setting metrics-proxy heap size

It's currently hardcoded to 256 Mb, and some users have reported running out.

After #30927 this should not be necessary. We prefer to not expose to many adjuster buttons for our internal services that are currently not exposed.


Brand package should be optional

This is actually an upstream bug. Will keep open for a bit--we could workaround it by adding none of the above: False but I don't think that should be required.


Update dependencies

Failed on Node 15, but Node 15 always fails "Error: Cannot find module 'node:events'".

What package is using the prefix? events works fine in every node version.

Arborist.
https://github.com/jslicense/licensee.js/actions/runs/10676215091/job/29589437503?pr=95#step:9:16

@ljharb, any objection to my releasing this semver-minor?

ah, looks like it's minipass, which indeed has engines of >= 16.
so yes, i'd say it's a semver-major, and you can confirm it by running npx ls-engines in CI prior to this change.

This PR is no longer bumping Arborist. Yet we get the failure.
@ljharb, any objection to my merging this #95, adding a commit to bump Arborist to latest 7.x.y, and releasing semver-major?

Sure, but let's proactively bump engines.node to ^18.12 || ^20.9 || >= 22.7, just to reduce the likelihood of another semver major. I'd also recommend adding ls-engines to CI :-)

Thanks for your effort here, @jayvdb.


Currency with multiple symbols won't adjust cursor properly

Hi!
I've noticed that using currencies that contain more than one symbol (such as BRL - R$) this component will not adjust the caret correctly.
Reproducing:

Open your codepen https://codepen.io/konstantin-lukas/pen/oNWzwOP
Add "currency: 'BRL'" to the options
Clear the text field
Start typing numbers

You'll see that the caret will be at this position:

FIXED
Thank you for reporting!

Thank you for this awesome lib!
Saved the backend dev a lot of time :D


I am getting an Error man

hey,
I am getting an error man. can u please help me out man

try installing node bro
On Tue, Sep 25, 2018 at 6:59 AM joel john<EMAIL_ADDRESS>wrote:

[image: screenshot from 2018-09-25 19-24-37]
https://user-images.githubusercontent.com/22270858/46018988-bcfe3980-c0f8-11e8-85b5-0b9a2d00f883.png
hey,
I am getting an error man. can u please help me out man
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/codingphasedotcom/Starter-Kit-2018/issues/7, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AfAsDj5ZDtd7wURQ3Zd4v4hTtQ68GPBHks5uejaugaJpZM4W4sO9
.


Tray doesn't redraw when app quits

Hi,
I made a short screencast to demonstrate the issue:

I quited stardict app and the tray icon disappeared, leaving a gap in the tray. You can see the right modules actually shifted to the right, which indicates the width of the tray should be updated correctly, while the gap and other parts of the tray remained unchanged, which doesn't go as expected. After I restarted stardict, its icon showed up as normal.
Here's my settings related to the tray:
tray-position = right
tray-padding = 5
tray-maxsize = 24
; tray-transparent = false
; tray-background = #2ABBFF
tray-detach = false

This also affects Redshift's tray icon. However only when using "Quit" from its context menu. Manually killing Redshift works fine.
With udiskie's tray icon both ways work fine while the auto hide function of udiskie's tray icon has the same issue.

Seems like it affects any time a tray icon disappears. Kind of a bummer as it covers my power menu... ¯_(ツ)_/¯


Estimating recombination rates between two populations

Hi there!
I would be interested in estimating the recombination rates between two populations of the same species. I would have the reference genome for the species and the fastq/BAM files for both sites.
Could I use rhometa to get an estimate of intra and inter-population recombination rates? If so, how?
Thanks in advance,
Fernando

Hi Fernando, one approach might be to run rhometa three times, once on each of the individual populations and once on the combined dataset. Before you do that on real data I think it would be wise to evaluate the strategy on a simulated dataset that is as close as possible to your real dataset in characteristics so that you can understand whether the method can produce the expected results even in the ideal setting of a simulation. If it works reasonably well on the simulation then it might be informative on real data, but if it doesn't work on simulated data then it seems very unlikely to produce meaningful results on a real dataset. Among other things I suggest you pay attention to the amount of data / number of reads from each population that are included in analysis.


FieldUUID

Django doesn't like it when you have more than one autofield on a model so I refactored FieldUUID into a seperate class.

Coverage increased (+0.2%) to 61.846% when pulling 6f5ab41b8ef48194911ad43e0d9e1c70ea77f98f on sethdenner:field-uuid into 117ff2dcb133596dcf902100238378217f5defbe on Knotis:master.


Change the template name for the orchestrator

This wouldn't actually make it to the cluster as we oc process
before we tell the cluster to deploy anything, but we should still
fix it anyway

Closing this as it's not really relevant given that #46 exists.


uncss fails due to CDN paths

https://github.com/addyosmani/grunt-uncss/issues/51 <- this should be reopened, issue is still occuring on 0.5.2

If this is an issue, it's an an upstream issue.

Any chance of identifying where upstream so it can be addressed ?

Upstream means uncss itself.


fix(deps): update transitive minimist dependency to 1.2.6

Addresses https://github.com/advisories/GHSA-xvch-5gv4-984h.

Suggestion: Do not use fix, because this is IMO not a user facing change. The customer needs to update their sub-dependencies (or better said their lock file) manually

Right, good call. I've rewritten the commit message to build(deps): update transitive minimist dependency to 1.2.6, in line with what Dependabot uses. 👍


JARVIS stopped replying to messages after September 28th!

No deployments around that time-frame; Need to find the root cause..

Can you verify if the token hasn't expired?

@HectorRoblesWolf That was it! It's working now.


Pop up an error after creating a web app with 63-characters name

Repro Step:

Right click one subscription and select 'Create New Web App'.
Create a web app with 63-characters name like 'abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz12345678901'.
Verify that whether this web app can be created successfully or not.

Expect:
The web app can be created successfully.
Actual:
Pop up an error.
Attachment:

Looks like this was fixed at some point. The validation prevents you from creating a web app with 63 characters:


Steps to build and download a private Python lambda layer as a local .zip or .tar file?

Question
How can I build a local version of the arn:aws:lambda:<region>:901920570463:layer:aws-otel-python-<architecture>-ver-1-19-0:1 for private use?
My organization requires that source code for all lambda layers be hosted locally (either in S3 or an artifact repository), so I would like to download this specific version of the python lambda auto-instrumentation + collector layer as a .zip or .tar file.
What I've Tried

Cloned this repo via git clone --recurse-submodules https://github.com/aws-observability/aws-otel-lambda.git and Running  ./build.sh in the /python directory. This created a layer.zip file, but testing this causes my lambda function to fail.
Followed the Manual Steps for Private Lambda Layers found in this documentation that is mentioned here. The bash run.sh -n <LAYER_NAME_HERE> -b true created a .zip file, but using this causes my lambda function to crash as well.
Followed the steps from Issue #299 to download the ARN layer via curl, but I am running into Security Token issues and am unable to finish the download.

Apologies if this question has already been asked/documented elsewhere, but I have found the documentation and links to be confusing, so I would appreciate if someone could give me specific steps and links for accomplishing this download.
Ideally, I would like to use the ARN arn:aws:lambda:<region>:901920570463:layer:aws-otel-python-<architecture>-ver-1-19-0:1 specifically, as this is what I have used to test successfully in our lower environments, though if there is another similar solution, please let me know.

Apologies for this question, I was able to achieve the result I was looking for with an aws cli command.


Support for Laravel 6

Duplicate of this, but better implemented: https://github.com/felixkiss/uniquewith-validator/pull/111

Original pull updated


Backend to add "Link" as question type in survey

@KillerX Looks good 👍 the cancelButtonText can be optional though, as we discussed

You can take a look at https://github.com/bcc-code/bcc-media-platform/pull/1061
It's still in draft as I had to jump over to the other urgent things and have done 0 testing, but let me know if you see some issues.

@sifferhans the UX test survey should have this type of question now.


Allow CORS and CORP Headers, Enabling SharedArrayBuffer

I've updated the livereload to allow for setting Cross-Origin-Embedder-Policy to "cross-origin", so it will work with other sites that require-corp, and same-site headers. Allowing you to use SharedArrayBuffer in modern browser versions.
Example using SIRV with this pull, livereload then needs modification to work correctly.
Explaining the need: Blog Regarding SharedArrayBuffer
Necessity/Purpose: So that you can work locally with @ffmpeg/ffmpeg which relies on SharedArrayBuffer

Without modification, livereload is being blocked:

After modification and proper headers:

Functionality returns and WS is connecting, reloads properly.

I can, give me a bit.
I'll take a look when I'm off.
Just a note, this should be considered different than standard CORS, it's the Cross Origin Resource Policy. Which was introduced to handle SPECTRE CPU vulnerabilities.
CORS is a bit tougher because there are a bunch variations on ways to configure them, based on source/origins, ect.

  livereload config
    ✓ should remove default exts when provided new exts
    ✓ should incldue default exts when provided extraExts
    ✓ extraExts must override exts if both are given
    ✓ should support filesToReload
    ✓ should support CORP headers

  livereload headers
    ✓ should set the correct CORP headers (61ms)

Let me know if I can assist with the CORS side. Looks like a different approach than mine was taken with the "defaultHeaders" variable, not much different, could be adapted easily.

I looked over both CORS requested PRs. I implemented what they wanted and the tests.
You can define { cors: true } or { cors: 'domain.name' } and the headers will respond.
  livereload config
    ✓ should remove default exts when provided new exts
    ✓ should incldue default exts when provided extraExts
    ✓ extraExts must override exts if both are given
    ✓ should support filesToReload
    ✓ should support CORP headers
    ✓ should support default CORS headers
    ✓ should support a specific CORS headers

  livereload headers
    ✓ should receive the correct CORP headers (66ms)
    ✓ should receive the correct default CORS headers
    ✓ should receive the correct sepecfic CORS headers

@napcs Setting both CORS and CORP settings, I've verified they both working appropriately.

@napcs This is the final change.  It's a speed optimization.
By moving the if conditions to the higher level function, they'll only need to evaluated once, at time of createServer being called. Moving them out of requestHandler means they don't need to evaluation on every single request to the JS file.

@a904guy holy smokes this is incredible. I'll look later this week. Thanks so much for the work here.

Just curious if there's anything blocking this PR?  I'm interested in using node-livereload with CORS, and might be able to help if needed.


Can drag and drop vsix with wrong platform to Extensions viewlet and it gets installed

Testing #133868
Client: Mac x64
Container: Linux x64
Extensions allowed me to drop an Alpine ARM64 VSIX downloaded from https://marketplace.visualstudio.com/items?itemName=chrmarti.test-platform-specific-extensions and it was installed.

Related to #134080

/duplicate


ERROR    - Did not find any init-build-env script

I'm getting the following when I try to run this example:
I cloned the repo, then ran kas build eu-terminal-distro.yml
Appreciate any pointers what I might be doing wrong.
2021-10-04 11:55:45 - INFO     - /scratch/oe/eu-terminal-distro/layers/meta-toradex-demos$ git rev-parse --verify -q origin/dunfell-5.x.y
2021-10-04 11:55:45 - INFO     - f99619b2135ff939b6370be8116d66a10bc84836
2021-10-04 11:55:45 - INFO     - /scratch/oe/eu-terminal-distro/layers/meta-toradex-demos$ git checkout -q f99619b2135ff939b6370be8116d66a10bc84836 -B dunfell-5.x.y
2021-10-04 11:55:45 - INFO     - /scratch/oe/eu-terminal-distro/layers/meta-toradex-distro$ git status -s
2021-10-04 11:55:45 - INFO     - /scratch/oe/eu-terminal-distro/layers/meta-toradex-distro$ git rev-parse --verify -q origin/dunfell-5.x.y
2021-10-04 11:55:45 - INFO     - 9f52ce166e8e3c10fa0935f55b3f403085f64fa2
2021-10-04 11:55:45 - INFO     - /scratch/oe/eu-terminal-distro/layers/meta-toradex-distro$ git checkout -q 9f52ce166e8e3c10fa0935f55b3f403085f64fa2 -B dunfell-5.x.y
2021-10-04 11:55:45 - ERROR    - Did not find any init-build-env script

I never tried kas, as it runs on my host PC and can mess up things easily. I always used kas-container to run kas in a well-defined container.
When kas sets up the Yocto build environment, it runs oe-init-build-env to set the environment variables correctly. This script is located in layers/openembedded-core/oe-init-build-env. I saw the error message when I didn't include openembedded-core in the project configuration file.


 is already possible.

 is already possible.
https://www.polymer-project.org/1.0/docs/devguide/data-binding.html#compound-bindings
Originally posted by @ebidel in https://github.com/Polymer/polymer/issues/3512#issuecomment-197558260

Thanks @ebidel for your guidance. But still few style properties are not binding as expected. Kindly share your inputs.
https://plnkr.co/edit/RvKX1EwOysUEdwbt?open=lib%2Fscript.js

Hi @ssthil ... When I look at your sample, it appears that all of the values you're binding are showing up correctly on both Chrome and Safari, unless I'm missing something. You're not actually using backgroundColor at the moment, and note that for camel-case properties, like "backgroundColor", if you want to initialize them from attributes as you're doing, you'll need to specify the attribute name using dash-case ("background-color: yellow"). Here's a plunker with that added:
https://plnkr.co/edit/G87PWInjrhK31SSn?open=lib%2Fscript.js
(Correction: after updating I noticed you're using "font-weight," but using a number. You probably want font-size here.)
Note that this is a really old version of Polymer. For ongoing Polymer work we recommend using Polymer 3, which takes advantage of native support for web components standards in all evergreen browsers including Chrome, Firefox, Safari, and Edge.
Here's a version of this in Polymer 3:
https://stackblitz.com/edit/bhbseg
Note that in Polymer 3, you have to explicitly declare any properties you want to initialize from attributes.
For new projects, we'd recommend LitElement.

@arthurevans Oh my God!, I don't have words to express my thanks to you. It's really detailed and helped 100%. Since I am new into Polymer side but quite interesting that the community has a super cool person like you 👍🙂 Thank you once again.


docs: adds info with step size/independent scale

It was not clear from the existing docs how to set individual chart size when using an independent scale with faceted charts and an unequal number of observations.
This adds one more chart example to user_guide/customization.rst to show how to vary the size using alt.Step to achieve this.

Thanks @daylinmorgan ! I agree that this example could be clearer. I changed your suggestion to use the same data as earlier in the same section and cleaned up the page a bit. Will merge when tests are passing

Perfect!


Remove stale add-ons when building

Change assembleZapAddOn to remove stale add-ons, to ensure ZAP loads
the add-on built.

Build failed?

Yes, but it's unrelated to these changes, the tutorial tests fail sometimes (restarted the failing job).

All passing now.

I haven't looked too much into the selenium tests, but is there a reason why they fail sometimes? Is there a way we can make those more reliable? I know @psiinon did a ton of work getting those up, so I think it would be cool if we could make those trustworthy. Right now they don't really provide me value because if they fail I can't trust taht something is actually wrong.


Consider Opus FEC and PLC

A good way to experiment is:
gst-launch filesrc location=foo.wav ! wavparse ! audioresample ! \
  opusenc inband-fec=1 packet-loss-percentage=10 ! \
  identity drop-probability=0.1 ! \
  opusdec use-inband-fec=1 plc=1 ! \
  autoaudiosink

plc=1 definitely improves things, while package-loss-percentage > 0 just seems to make things worse, so this should be researched.
Also, see https://bugzilla.gnome.org/show_bug.cgi?id=744338. Before opusdec gains a way of knowing the actual maximum packet duration, the constant 120ms latency added by use-inband-fec=1 would make it inappropriate for RTC.

@sdroege

@sdroege , you might have some input.

I'm not sure about signaling for in-band opus FEC. But fine for non-interoperable usage.
This draft is being discussed by IETF at the moment. https://tools.ietf.org/html/draft-ietf-payload-flexible-fec-scheme-00

I'm not sure about signaling for in-band opus FEC.
FEC's presence is signaled by Opus headers, so it's naturally interoperable; i.e. if you start sending Opus in-band FEC while your decoder doesn't have use-inband-fec=0, nothing will break, and vice versa.

plc=1 is also not an interop risk.
The maximum packet duration corresponds to SDP's maxptime according to Oliver Crête, so this is already standardized.

Anyway, I'd appreciate if somebody else will try, e.g.:
gst-launch-1.0 filesrc location=/Users/ilyak/music.wav ! wavparse ! audioresample ! opusenc inband-fec=1 bitrate-type=0 bitrate=64000 packet-loss-percentage=25 ! identity drop-probability=0.2 ! opusdec use-inband-fec=1 plc=1 ! autoaudiosink

and let me know if it's just me.

Without drop-probability > 0, setting inband-fec=1 results in slightly lower quality, which is expected since some of the bitrate is being wasted on FEC. This brings me to assume FEC is indeed being added.
With drop-probability > 0, I've tried setting packet-loss-percentage slightly higher than the drop probability (e.g. 20 --> 25). I'd assume coding theory stuff would make sure to add just enough FEC to counter the drops, but what I'm hearing is not clearly better. In fact, plc=1 seems to be what's making a difference. With plc=0, it's really bad.

Ideas, anyone?

OK, actually read the source.

plc=1 actually affects GstAudioDecoder and makes it send an empty buffer for GAP events (which identity drop-probability=... generates). For Opus to trigger PLC, it simply needs a NULL buffer, which plc=1 results in eventually.
Without those GAP buffers, FEC reconstruction would not be triggered either. Therefore use-inband-fec=1 plc=0 is meaningless.
Furthermore, FEC reconstruction seems broken — see https://bugzilla.gnome.org/show_bug.cgi?id=753148


#810: added warning message to setup

fixes #810
added warning message to setup explaining that a new shell needs to be started to use IDEasy:
$ unset -f ide
$ rm /d/projects/_ide/bin/ide
$ ide help
bash: /d/projects/_ide/bin/ide: No such file or directory
$ source setup
Setting up IDEasy in /d/projects/_ide
Configuring IDEasy in /c/Users/hohwille/.bashrc.
Configuring IDEasy in /c/Users/hohwille/.zshrc.
ATTENTION: IDEasy has been setup for your shells but you need to start a new shell to make it work.
Only if you invoked this setup script by sourcing it, you are able to run 'ide' and 'icd' commands without starting a new shell.
$ ide help
__       ___ ___  ___
\ \     |_ _|   \| __|__ _ ____ _
 > >     | || |) | _|/ _` (_-< || |
/_/ ___ |___|___/|___\__,_/__/\_, |
   |___|                       |__/

Current version of IDE is 2024.12.001-beta-SNAPSHOT
...

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
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 67.417%

Totals

Change from base Build<PHONE_NUMBER>7:
0.0%

Covered Lines:
6511

Relevant Lines:
9316

💛  - Coveralls


Fix CSP bug with "Open in new window" button (#382)

Hi,
This is a pull request to fix #382 issue opened yesterday. My solution works fine.
I tried to install the npm dependencies with npm i, but it didn't work, so I couldn't rebuild the script.   Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
244 timing reifyNode:node_modules/uuid Completed in 1227ms
245 timing reifyNode:node_modules/qs Completed in 1227ms
246 warn deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
247 timing reifyNode:node_modules/request Completed in 1237ms
248 timing metavuln:cache:get:security-advisory:jsprim:QRwmQiuv2v1qSgbUQnnOq/BCmkS2/L/UCMZqttFxXCKmhngjXz/Emg8LJqaGEEX8q+I+K+Nu9HfxA4IDuytApA== Completed in 33ms
249 timing reifyNode:node_modules/asynckit Completed in 1232ms
250 timing reifyNode:node_modules/har-schema Completed in 1245ms
251 timing reifyNode:node_modules/minimist Completed in 1247ms
252 timing reifyNode:node_modules/source-map Completed in 1277ms
253 timing reifyNode:node_modules/readable-stream Completed in 1291ms
254 http fetch GET 200 https://registry.npmjs.org/jsprim 121ms (cache revalidated)
255 timing metavuln:packument:jsprim Completed in 122ms
256 timing metavuln:load:security-advisory:jsprim:uVcBWD+ZqHJKVkSGOfO4yK+HybE/AV72re+WaiTN0a2jxKtVzp8MsDQW6mQ0NhRBKqqxq93dEUVYTqaY6Vbrlw== Completed in 0ms
257 timing metavuln:calculate:security-advisory:jsprim:uVcBWD+ZqHJKVkSGOfO4yK+HybE/AV72re+WaiTN0a2jxKtVzp8MsDQW6mQ0NhRBKqqxq93dEUVYTqaY6Vbrlw== Completed in 122ms
258 timing reifyNode:node_modules/tar Completed in 1358ms
259 timing metavuln:cache:get:security-advisory:meow:qMGSqDOPwBYOuSDi8UxYBvIWKNbskU0xZuNoRfLxyZkJyqN9VQIiZVdFgUXVBJO6KmJn12ycEpMrEdlH2bYikg== Completed in 30ms
260 timing reifyNode:node_modules/json-schema Completed in 1403ms
261 timing reifyNode:node_modules/uglify-js Completed in 1436ms
262 http fetch GET 200 https://registry.npmjs.org/meow 138ms (cache revalidated)
263 timing metavuln:packument:meow Completed in 139ms
264 timing metavuln:load:security-advisory:meow:FKtGPIHE0cWJrTOi1H996Hvqnj28iATHiQozLL7kOyZM+hBcKTbQkvTcxBhdBUKOwk1FocLiNFl3tMgMuyKb0g== Completed in 2ms
265 timing metavuln:calculate:security-advisory:meow:FKtGPIHE0cWJrTOi1H996Hvqnj28iATHiQozLL7kOyZM+hBcKTbQkvTcxBhdBUKOwk1FocLiNFl3tMgMuyKb0g== Completed in 141ms
266 timing metavuln:cache:get:security-advisory:strip-ansi:VNH7BZLDPXeb+XyBHjziFezTzkb3wUEeYZF30Shwpq+9ErFf3ja9WpDN5+1N0ZmzJRrF78Jsd1Rv6URhv1/2cQ== Completed in 22ms
267 timing reifyNode:node_modules/sshpk Completed in 1515ms
268 timing reifyNode:node_modules/yargs Completed in 1545ms
269 http fetch GET 200 https://registry.npmjs.org/strip-ansi 107ms (cache revalidated)
270 timing metavuln:packument:strip-ansi Completed in 107ms
271 timing metavuln:load:security-advisory:strip-ansi:gipfqiXURkkimm8+IyoEer5YC1ntqyorXe7xXSHfbxT4Q2N0cl4sjpCXLBfNQSZpCf2C6BCCpq61JXzBTOWL+g== Completed in 1ms
272 timing metavuln:calculate:security-advisory:strip-ansi:gipfqiXURkkimm8+IyoEer5YC1ntqyorXe7xXSHfbxT4Q2N0cl4sjpCXLBfNQSZpCf2C6BCCpq61JXzBTOWL+g== Completed in 108ms
273 timing metavuln:cache:get:security-advisory:http-signature:upm1syltaQQk+WBKtPw6YsBaxj+CsFA5RzQpT8BTsGTeKtaQDFI39vz+ktDswUws3m15VM18TZja0+/1k69g7Q== Completed in 7ms
274 timing reifyNode:node_modules/semver Completed in 1594ms
275 timing reifyNode:node_modules/nan Completed in 1593ms
276 timing reifyNode:node_modules/uri-js Completed in 1598ms
277 http fetch GET 200 https://registry.npmjs.org/http-signature 85ms (cache revalidated)
278 timing metavuln:packument:http-signature Completed in 86ms
279 timing metavuln:load:security-advisory:http-signature:QRwmQiuv2v1qSgbUQnnOq/BCmkS2/L/UCMZqttFxXCKmhngjXz/Emg8LJqaGEEX8q+I+K+Nu9HfxA4IDuytApA== Completed in 0ms
280 timing metavuln:calculate:security-advisory:http-signature:QRwmQiuv2v1qSgbUQnnOq/BCmkS2/L/UCMZqttFxXCKmhngjXz/Emg8LJqaGEEX8q+I+K+Nu9HfxA4IDuytApA== Completed in 86ms
281 timing metavuln:cache:get:security-advisory:node-sass:uH53mY8GsVlyO5ECOvnd0tGFHSF5rf4A0hXfdx0QYFkWZNsx6GD2sSbXyvWHcfEt70IsiW35PDXoFZ28lJlbjA== Completed in 14ms
282 timing metavuln:load:security-advisory:node-sass:qMGSqDOPwBYOuSDi8UxYBvIWKNbskU0xZuNoRfLxyZkJyqN9VQIiZVdFgUXVBJO6KmJn12ycEpMrEdlH2bYikg== Completed in 1ms
283 timing metavuln:calculate:security-advisory:node-sass:qMGSqDOPwBYOuSDi8UxYBvIWKNbskU0xZuNoRfLxyZkJyqN9VQIiZVdFgUXVBJO6KmJn12ycEpMrEdlH2bYikg== Completed in 15ms
284 timing metavuln:cache:get:security-advisory:cliui:7d3FZGcI3zHMZwOEJ7z64Yya3CeS8V9Yp1mUPqnkRhYfe1AhvBDG2H8PbANiJB6NNtMXuaGQGEmGWKyUIVPg3w== Completed in 14ms
285 timing metavuln:cache:get:security-advisory:string-width:z8iR7PVusZCDbQbpBbfUOlp4nWW5lica+XU9Ck0Wj4d793LOue6orGcnetE+RgMcvOtyfG+VyOfSi0Yzr3ZiWw== Completed in 15ms
286 timing metavuln:cache:get:security-advisory:wrap-ansi:GHlqgCTSc3dwtjMoQl6niHwnwCGUim0UjGppBrfJQzwA3E5oOFtnX/Dq+IC4H0kqX6j5CocvPBNIsu8VJbeufA== Completed in 14ms
287 http fetch GET 200 https://registry.npmjs.org/string-width 78ms (cache revalidated)
288 timing metavuln:packument:string-width Completed in 78ms
289 timing metavuln:load:security-advisory:string-width:VNH7BZLDPXeb+XyBHjziFezTzkb3wUEeYZF30Shwpq+9ErFf3ja9WpDN5+1N0ZmzJRrF78Jsd1Rv6URhv1/2cQ== Completed in 0ms
290 timing metavuln:calculate:security-advisory:string-width:VNH7BZLDPXeb+XyBHjziFezTzkb3wUEeYZF30Shwpq+9ErFf3ja9WpDN5+1N0ZmzJRrF78Jsd1Rv6URhv1/2cQ== Completed in 78ms
291 http fetch GET 200 https://registry.npmjs.org/cliui 79ms (cache revalidated)
292 timing metavuln:packument:cliui Completed in 79ms
293 timing metavuln:load:security-advisory:cliui:VNH7BZLDPXeb+XyBHjziFezTzkb3wUEeYZF30Shwpq+9ErFf3ja9WpDN5+1N0ZmzJRrF78Jsd1Rv6URhv1/2cQ== Completed in 0ms
294 timing metavuln:calculate:security-advisory:cliui:VNH7BZLDPXeb+XyBHjziFezTzkb3wUEeYZF30Shwpq+9ErFf3ja9WpDN5+1N0ZmzJRrF78Jsd1Rv6URhv1/2cQ== Completed in 80ms
295 http fetch GET 200 https://registry.npmjs.org/wrap-ansi 87ms (cache revalidated)
296 timing metavuln:packument:wrap-ansi Completed in 87ms
297 timing metavuln:load:security-advisory:wrap-ansi:VNH7BZLDPXeb+XyBHjziFezTzkb3wUEeYZF30Shwpq+9ErFf3ja9WpDN5+1N0ZmzJRrF78Jsd1Rv6URhv1/2cQ== Completed in 0ms
298 timing metavuln:calculate:security-advisory:wrap-ansi:VNH7BZLDPXeb+XyBHjziFezTzkb3wUEeYZF30Shwpq+9ErFf3ja9WpDN5+1N0ZmzJRrF78Jsd1Rv6URhv1/2cQ== Completed in 87ms
299 timing metavuln:cache:get:security-advisory:cliui:2gbc6+LrUTrmS9/1of6t2ConpwkXUvhGLxrWKb9OKsYXzelT/nvJ8pLGFowk0Q0AAL7vm/IAl6mjO77yfQ1FlA== Completed in 14ms
300 timing metavuln:load:security-advisory:cliui:z8iR7PVusZCDbQbpBbfUOlp4nWW5lica+XU9Ck0Wj4d793LOue6orGcnetE+RgMcvOtyfG+VyOfSi0Yzr3ZiWw== Completed in 0ms
301 timing metavuln:calculate:security-advisory:cliui:z8iR7PVusZCDbQbpBbfUOlp4nWW5lica+XU9Ck0Wj4d793LOue6orGcnetE+RgMcvOtyfG+VyOfSi0Yzr3ZiWw== Completed in 14ms
302 timing metavuln:cache:get:security-advisory:wrap-ansi:bBNGWPaeIczlySXOiHEe7fItDCJRl0j7uIYLEUVtmxvynJ8Jub47NupYgKQyGIiFZF6n3QExmGhvEjwo4bV+Hw== Completed in 11ms
303 timing metavuln:load:security-advisory:wrap-ansi:z8iR7PVusZCDbQbpBbfUOlp4nWW5lica+XU9Ck0Wj4d793LOue6orGcnetE+RgMcvOtyfG+VyOfSi0Yzr3ZiWw== Completed in 0ms
304 timing metavuln:calculate:security-advisory:wrap-ansi:z8iR7PVusZCDbQbpBbfUOlp4nWW5lica+XU9Ck0Wj4d793LOue6orGcnetE+RgMcvOtyfG+VyOfSi0Yzr3ZiWw== Completed in 11ms
305 timing metavuln:cache:get:security-advisory:yargs:BOa2Al3idP5OlOreEdnVQi68smAzGPOhWohGdtS8trVu5DacMa8X/tmqHH8v0P7xOBCZgrfoFATVy/B3qs1pTg== Completed in 11ms
306 timing reifyNode:node_modules/ajv Completed in 1799ms
307 timing reifyNode:node_modules/resolve Completed in 1820ms
308 http fetch GET 200 https://registry.npmjs.org/yargs 59ms (cache revalidated)
309 timing metavuln:packument:yargs Completed in 63ms
310 timing metavuln:load:security-advisory:yargs:z8iR7PVusZCDbQbpBbfUOlp4nWW5lica+XU9Ck0Wj4d793LOue6orGcnetE+RgMcvOtyfG+VyOfSi0Yzr3ZiWw== Completed in 1ms
311 timing metavuln:calculate:security-advisory:yargs:z8iR7PVusZCDbQbpBbfUOlp4nWW5lica+XU9Ck0Wj4d793LOue6orGcnetE+RgMcvOtyfG+VyOfSi0Yzr3ZiWw== Completed in 64ms
312 timing metavuln:cache:get:security-advisory:yargs:sEQW/iRTpyQRNB6hQsxF7xOlMLlyV4sqa2brC9oz1fcV33UocNP/jtG9oNUHw7v4JTvcrzNRdQEGFoHvXqJiXA== Completed in 6ms
313 timing metavuln:load:security-advisory:yargs:7d3FZGcI3zHMZwOEJ7z64Yya3CeS8V9Yp1mUPqnkRhYfe1AhvBDG2H8PbANiJB6NNtMXuaGQGEmGWKyUIVPg3w== Completed in 2ms
314 timing metavuln:calculate:security-advisory:yargs:7d3FZGcI3zHMZwOEJ7z64Yya3CeS8V9Yp1mUPqnkRhYfe1AhvBDG2H8PbANiJB6NNtMXuaGQGEmGWKyUIVPg3w== Completed in 8ms
315 timing metavuln:cache:get:security-advisory:cliui:YvvwN3bPbpjXv4F1ffT9cm5JB9+i7WRwRf1M+p+fSCpbKcM/RmEuIXTOH4OS9E3TQgOYTBM0HKslgem1lsj+nQ== Completed in 7ms
316 timing metavuln:load:security-advisory:cliui:GHlqgCTSc3dwtjMoQl6niHwnwCGUim0UjGppBrfJQzwA3E5oOFtnX/Dq+IC4H0kqX6j5CocvPBNIsu8VJbeufA== Completed in 0ms
317 timing metavuln:calculate:security-advisory:cliui:GHlqgCTSc3dwtjMoQl6niHwnwCGUim0UjGppBrfJQzwA3E5oOFtnX/Dq+IC4H0kqX6j5CocvPBNIsu8VJbeufA== Completed in 7ms
318 timing metavuln:cache:get:security-advisory:sass-graph:WGDfqJQle4+MNYWJAHB20SsHCiX9BtonJh4RGPjt1Djci4Ezm7GGT9wTFx4VkrpRtCNcenc39T2oo+YnW42TJw== Completed in 4ms
319 http fetch GET 200 https://registry.npmjs.org/sass-graph 66ms (cache revalidated)
320 timing metavuln:packument:sass-graph Completed in 67ms
321 timing metavuln:load:security-advisory:sass-graph:BOa2Al3idP5OlOreEdnVQi68smAzGPOhWohGdtS8trVu5DacMa8X/tmqHH8v0P7xOBCZgrfoFATVy/B3qs1pTg== Completed in 0ms
322 timing metavuln:calculate:security-advisory:sass-graph:BOa2Al3idP5OlOreEdnVQi68smAzGPOhWohGdtS8trVu5DacMa8X/tmqHH8v0P7xOBCZgrfoFATVy/B3qs1pTg== Completed in 67ms
323 timing metavuln:cache:get:security-advisory:node-sass:sKa4m2v9CoUt2NE/HFdn2iHPGTVRUKpbo4oLNnOVBTLyHGQ/KmGqhFuwUlvkR/owQNQEXwZFOGQt5TNCCkoHWw== Completed in 6ms
324 timing metavuln:load:security-advisory:node-sass:WGDfqJQle4+MNYWJAHB20SsHCiX9BtonJh4RGPjt1Djci4Ezm7GGT9wTFx4VkrpRtCNcenc39T2oo+YnW42TJw== Completed in 1ms
325 timing metavuln:calculate:security-advisory:node-sass:WGDfqJQle4+MNYWJAHB20SsHCiX9BtonJh4RGPjt1Djci4Ezm7GGT9wTFx4VkrpRtCNcenc39T2oo+YnW42TJw== Completed in 7ms
326 timing auditReport:init Completed in 1197ms
327 timing reify:audit Completed in 1943ms
328 timing reifyNode:node_modules/node-gyp Completed in 1961ms
329 timing reifyNode:node_modules/prettier Completed in 2297ms
330 timing reifyNode:node_modules/node-sass Completed in 2419ms
331 timing reifyNode:node_modules/lodash Completed in 2967ms
332 timing reify:unpack Completed in 2975ms
333 timing reify:unretire Completed in 1ms
334 timing build:queue Completed in 10ms
335 timing build:link:node_modules/node-sass Completed in 35ms
336 timing build:link:node_modules/mkdirp Completed in 37ms
337 timing build:link:node_modules/node-gyp Completed in 35ms
338 timing build:link:node_modules/sass-graph Completed in 34ms
339 timing build:link:node_modules/nopt Completed in 35ms
340 timing build:link:node_modules/uuid Completed in 33ms
341 timing build:link:node_modules/rimraf Completed in 34ms
342 timing build:link:node_modules/which Completed in 31ms
343 timing build:link:node_modules/normalize-package-data/node_modules/semver Completed in 31ms
344 timing build:link:node_modules/sshpk Completed in 34ms
345 timing build:link:node_modules/tar/node_modules/mkdirp Completed in 31ms
346 timing build:link:node_modules/strip-indent Completed in 33ms
347 timing build:link:node_modules/uglify-js Completed in 33ms
348 timing build:link:node_modules/semver Completed in 34ms
349 timing build:link:node_modules/prettier Completed in 35ms
350 timing build:link Completed in 38ms
351 info run<EMAIL_ADDRESS>install node_modules/node-sass node scripts/install.js
352 info run<EMAIL_ADDRESS>install { code: 0, signal: null }
353 timing build:run:install:node_modules/node-sass Completed in 677ms
354 timing build:run:install Completed in 677ms
355 info run<EMAIL_ADDRESS>postinstall node_modules/node-sass node scripts/build.js
356 info run<EMAIL_ADDRESS>postinstall { code: 1, signal: null }
357 timing reify:rollback:createSparse Completed in 455ms
358 timing reify:rollback:retireShallow Completed in 1ms
359 timing command:install Completed in 5209ms
360 verbose stack Error: command failed
360 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\@npmcli\promise-spawn\index.js:64:27)
360 verbose stack     at ChildProcess.emit (node:events:390:28)
360 verbose stack     at maybeClose (node:internal/child_process:1064:16)
360 verbose stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
361 verbose pkgid<EMAIL_ADDRESS>362 verbose cwd C:\xampp\htdocs\kint
363 verbose Windows_NT 10.0.19044
364 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "i"
365 verbose node v16.13.2
366 verbose npm  v8.1.2
367 error code 1
368 error path C:\xampp\htdocs\kint\node_modules\node-sass
369 error command failed
370 error command C:\WINDOWS\system32\cmd.exe /d /s /c node scripts/build.js
371 error Building: C:\Program Files\nodejs\node.exe C:\xampp\htdocs\kint\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
372 error gyp info it worked if it ends with ok
372 error gyp verb cli [
372 error gyp verb cli   'C:\\Program Files\\nodejs\\node.exe',
372 error gyp verb cli   'C:\\xampp\\htdocs\\kint\\node_modules\\node-gyp\\bin\\node-gyp.js',
372 error gyp verb cli   'rebuild',
372 error gyp verb cli   '--verbose',
372 error gyp verb cli   '--libsass_ext=',
372 error gyp verb cli   '--libsass_cflags=',
372 error gyp verb cli   '--libsass_ldflags=',
372 error gyp verb cli   '--libsass_library='
372 error gyp verb cli ]
372 error gyp info using<EMAIL_ADDRESS>372 error gyp info using<EMAIL_ADDRESS>| win32 | x64
372 error gyp verb command rebuild []
372 error gyp verb command clean []
372 error gyp verb clean removing "build" directory
372 error gyp verb command configure []
372 error gyp verb find Python Python is not set from command line or npm configuration
372 error gyp verb find Python Python is not set from environment variable PYTHON
372 error gyp verb find Python checking if "python3" can be used
372 error gyp verb find Python - executing "python3" to get executable path
372 error gyp verb find Python - "python3" is not in PATH or produced an error
372 error gyp verb find Python checking if "python" can be used
372 error gyp verb find Python - executing "python" to get executable path
372 error gyp verb find Python - "python" is not in PATH or produced an error
372 error gyp verb find Python checking if "python2" can be used
372 error gyp verb find Python - executing "python2" to get executable path
372 error gyp verb find Python - "python2" is not in PATH or produced an error
372 error gyp verb find Python checking if Python is C:\Python37\python.exe
372 error gyp verb find Python - executing "C:\Python37\python.exe" to get version
372 error gyp verb find Python - "C:\Python37\python.exe" could not be run
372 error gyp verb find Python checking if Python is C:\Python27\python.exe
372 error gyp verb find Python - executing "C:\Python27\python.exe" to get version
372 error gyp verb find Python - "C:\Python27\python.exe" could not be run
372 error gyp verb find Python checking if the py launcher can be used to find Python
372 error gyp verb find Python - executing "py.exe" to get Python executable path
372 error gyp verb find Python - "py.exe" is not in PATH or produced an error
372 error gyp ERR! find Python
372 error gyp ERR! find Python Python is not set from command line or npm configuration
372 error gyp ERR! find Python Python is not set from environment variable PYTHON
372 error gyp ERR! find Python checking if "python3" can be used
372 error gyp ERR! find Python - "python3" is not in PATH or produced an error
372 error gyp ERR! find Python checking if "python" can be used
372 error gyp ERR! find Python - "python" is not in PATH or produced an error
372 error gyp ERR! find Python checking if "python2" can be used
372 error gyp ERR! find Python - "python2" is not in PATH or produced an error
372 error gyp ERR! find Python checking if Python is C:\Python37\python.exe
372 error gyp ERR! find Python - "C:\Python37\python.exe" could not be run
372 error gyp ERR! find Python checking if Python is C:\Python27\python.exe
372 error gyp ERR! find Python - "C:\Python27\python.exe" could not be run
372 error gyp ERR! find Python checking if the py launcher can be used to find Python
372 error gyp ERR! find Python - "py.exe" is not in PATH or produced an error
372 error gyp ERR! find Python
372 error gyp ERR! find Python **********************************************************
372 error gyp ERR! find Python You need to install the latest version of Python.
372 error gyp ERR! find Python Node-gyp should be able to find and use Python. If not,
372 error gyp ERR! find Python you can try one of the following options:
372 error gyp ERR! find Python - Use the switch --python="C:\Path\To\python.exe"
372 error gyp ERR! find Python   (accepted by both node-gyp and npm)
372 error gyp ERR! find Python - Set the environment variable PYTHON
372 error gyp ERR! find Python - Set the npm configuration variable python:
372 error gyp ERR! find Python   npm config set python "C:\Path\To\python.exe"
372 error gyp ERR! find Python For more information consult the documentation at:
372 error gyp ERR! find Python https://github.com/nodejs/node-gyp#installation
372 error gyp ERR! find Python **********************************************************
372 error gyp ERR! find Python
372 error gyp ERR! configure error
372 error gyp ERR! stack Error: Could not find any Python installation to use
372 error gyp ERR! stack     at PythonFinder.fail (C:\xampp\htdocs\kint\node_modules\node-gyp\lib\find-python.js:302:47)
372 error gyp ERR! stack     at PythonFinder.runChecks (C:\xampp\htdocs\kint\node_modules\node-gyp\lib\find-python.js:136:21)
372 error gyp ERR! stack     at PythonFinder.<anonymous> (C:\xampp\htdocs\kint\node_modules\node-gyp\lib\find-python.js:200:18)
372 error gyp ERR! stack     at PythonFinder.execFileCallback (C:\xampp\htdocs\kint\node_modules\node-gyp\lib\find-python.js:266:16)
372 error gyp ERR! stack     at exithandler (node:child_process:404:5)
372 error gyp ERR! stack     at ChildProcess.errorhandler (node:child_process:416:5)
372 error gyp ERR! stack     at ChildProcess.emit (node:events:390:28)
372 error gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:288:12)
372 error gyp ERR! stack     at onErrorNT (node:internal/child_process:477:16)
372 error gyp ERR! stack     at processTicksAndRejections (node:internal/process/task_queues:83:21)
372 error gyp ERR! System Windows_NT 10.0.19044
372 error gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\xampp\\htdocs\\kint\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
372 error gyp ERR! cwd C:\xampp\htdocs\kint\node_modules\node-sass
372 error gyp ERR! node -v v16.13.2
372 error gyp ERR! node-gyp -v v7.1.2
372 error gyp ERR! not ok
372 error Build failed with error code: 1
373 verbose exit 1

Regards.

Hi @BrokenSourceCode I was going to post this on the issue but it ended up late.

The browser removes the nonce attribute from the script tag before any of the code is run (Obviously to prevent malicious actors deducing the nonce) so there doesn't appear to be any way to get it dynamically.
We could additionally add the nonce in another attribute and pass it to the new window from there, but that means any page with a rich dump in it now has an easily accessible CSP nonce... That's a security risk I really don't want to deal with.
Unless you can think of another way to do this I'm afraid I'm going to have to simply disable that feature when a nonce is present.

After I wrote this I realized I could probably add a meta tag to the html to overwrite the CSP and allow all, but I haven't gotten it working yet.
Since this PR essentially presents a security issue on any page with a kint dump I don't think this is going to work. (You could access the nonce through clever CSS selector abuse for instance)
I'll be working on it more tonight but here's the diff of my WIP in case you want to take a deeper crack at it in the next few hours:
--- a/resources/js/rich.js
+++ b/resources/js/rich.js
@@ -159,6 +159,8 @@ if (typeof window.kintRich === 'undefined') {
                             ')' +
                             kintRich.mktag('/title') +
                             kintRich.mktag('meta charset="utf-8"') +
+                            // kintRich.mktag('meta http-equiv="Content-Security-Policy" content="script-src * \'unsafe-inline\' \'unsafe-eval\' ; style-src * \'unsafe-inline\'"') +
+                            kintRich.mktag('meta http-equiv="Content-Security-Policy" content="default-src * \'unsafe-inline\' \'unsafe-eval\' data: ; script-src * \'unsafe-inline\' \'unsafe-eval\' ; style-src * \'unsafe-inline\'"') +
                             document.getElementsByClassName('kint-rich-script')[0].outerHTML +
                             document.getElementsByClassName('kint-rich-style')[0].outerHTML +
                             kintRich.mktag('/head') +

PS: try npm ci though you might need a newer version of npm, I know a lot of systems use a really old one by default

Edit: Wait I'm an idiot, I didn't know you could access the nonce through script... Your solution is probably best then, I'll add a fixup commit and merge later on unless I see a new problem

Yes, my solution is working. You can't access the attribute (element.getAttribute('nonce')), but there is a property (element.nonce) especially for our case.
See https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/nonce.

PS: try npm ci though you might need a newer version of npm, I know a lot of systems use a really old one by default

I'll will try this now!

Looking at the input style changes I noticed that the microtime plugin's inline style changes work just fine, so long as the JS it comes from has a nonce... In other words if we applied the width:100% through JS instead of as a string attribute we wouldn't need to change the CSS.
That said I'll just give it a proper class and add that to the CSS so it's a moot point...
Do you know if there's any detriment to an incorrect nonce if there's no CSP header? I imagine not but it might be better to leave the attribute out than have one with an empty string in some edge cases

Looking at the input style changes I noticed that the microtime plugin's inline style changes work just fine, so long as the JS it comes from has a nonce... In other words if we applied the width:100% through JS instead of as a string attribute we wouldn't need to change the CSS.
That said I'll just give it a proper class and add that to the CSS so it's a moot point...

Yes, I think that's better and cleaner than my quick fix in this PR!
// Bad, we should add a rule for a class.
'input{width:100%;}' +

Do you know if there's any detriment to an incorrect nonce if there's no CSP header? I imagine not but it might be better to leave the attribute out than have one with an empty string in some edge cases

I just tried this piece of code without any  Content-Security-Policy header, and the alert works perfectly (no error/warning in the web console). Does this answer your question?
<script nonce="foo">
	alert('ok');
</script>

still the same issue with npm ci

Looking at the log:

You need to install the latest version of Python.

Looks like node-sass depends on python for some reason (Which is weird since it's a C library of something originally written in ruby called from JS...)
I'll add that to the contrib notes

Oh okay, I didn't know that we need python for node-sass, maybe because Kint uses an old version. Currently there is version 7, and Kint uses 5. I'll try this

Yeah I didn't know either. I'm not particularly cutting edge on the JS front, and it doesn't really matter for endusers since we only have dev dependencies. If the newer version doesn't depend on python please tell me, I'd rather upgrade it and get rid of the dependency than have to add it to contributing.md
I merged it btw, even if an empty nonce does break in some edge cases it's still less broken than now so I'll take the win

The new version doesn't depend on python. Take a look at this PR.


RocketPlayer.GiveItem Exception

InvalidCastException: Cannot cast from source type to destination type. - SDG.Unturned.PlayerInvento
ry.onVestUpdated (UInt16 id)
SDG.Unturned.PlayerClothing.tellClothing (CSteamID steamID, UInt16 newShirt, Byte newShirtQuality, S
ystem.Byte[] newShirtState, UInt16 newPants, Byte newPantsQuality, System.Byte[] newPantsState, UInt
16 newHat, Byte newHatQuality, System.Byte[] newHatState, UInt16 newBackpack, Byte newBackpackQualit
y, System.Byte[] newBackpackState, UInt16 newVest, Byte newVestQuality, System.Byte[] newVestState,
UInt16 newMask, Byte newMaskQuality, System.Byte[] newMaskState, UInt16 newGlasses, Byte newGlassesQ
uality, System.Byte[] newGlassesState, Int32 newVisualShirt, Int32 newVisualPants, Int32 newVisualHa
t, Int32 newVisualBackpack, Int32 newVisualVest, Int32 newVisualMask, Int32 newVisualGlasses, Boolea
n newVisual)
System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.B
inder binder, System.Object[] parameters, System.Globalization.CultureInfo culture)
Rethrow as TargetInvocationException: Exception has been thrown by the target of an invocation.
System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.B
inder binder, System.Object[] parameters, System.Globalization.CultureInfo culture)
System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters)
SDG.Unturned.SteamChannel.receive (CSteamID steamID, System.Byte[] packet, Int32 offset, Int32 size)
SDG.Unturned.SteamChannel.send (ESteamCall mode, ESteamPacket type, Int32 size, System.Byte[] packet
)
SDG.Unturned.SteamChannel.send (System.String name, ESteamCall mode, ESteamPacket type, System.Objec
t[] arguments)
SDG.Unturned.PlayerClothing.askClothing (CSteamID steamID)
System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.B
inder binder, System.Object[] parameters, System.Globalization.CultureInfo culture)
Rethrow as TargetInvocationException: Exception has been thrown by the target of an invocation.
System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.B
inder binder, System.Object[] parameters, System.Globalization.CultureInfo culture)
System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters)
SDG.Unturned.SteamChannel.receive (CSteamID steamID, System.Byte[] packet, Int32 offset, Int32 size)
SDG.Unturned.Steam.receive (CSteamID steamID, System.Byte[] packet, Int32 offset, Int32 size, Int32
channel)
SDG.Unturned.Steam.listenServer (Int32 channel)
SDG.Unturned.Steam.listen ()
SDG.Unturned.Steam.Update ()

I think this might be related with the latest patch and the new improvement:

Improved clothing to track state allowing night vision to save whether it was on or off.


Gallery, Shrine, Dark theme: quantity selector doesn't match theme of Shrine

Open gallery, turn on Dark Mode, open shrine, select an item, and then open the Quantity selector:

Also, Pesto:

This is a duplicate of https://github.com/flutter/flutter/issues/5572
The underlying problem is non-trivial, see the comments for #5572

Thanks for de-duping :)


Improve Travis CI config

Add deployment of a package to PYPI for tagged commits running after all tests
Introduce testing against PYPY
Add pip packages caching
Print list of installed packages in case of failure

@benjaminp please note to encrypt your password via travis encrypt command and put it into .travis.yml.
When the new version is ready to publishing, create and push a new tag with that version. Travis CI will run tests as usual, but also, after success, it will publish the package to PYPI..

Thank you!

@benjaminp Please don't forget to replace YOUR_ENCRYPTED_PYPI_PASSWORD_HERE placeholder in Travis CI config :)