Create values-schema mechanism to update values to conform to schema changes

User story
As a developer making breaking changes to the values-schema, I want to have a mechanism that will copy the corresponding values to their new locations.
Problem
We break the schema when:

We move properties around (more frequent)
We delete props (more frequent)
We change property type (less frequent)

otomi-core should have a mechanism that migrates values to conform to the new spec.
Proposed solution
A schema will get a version (semver, patches are additions, minors are breaking changes) and a changes property holding information about breaking changes:

The new location (if changed) by mapping old to new
The list of deleted props
The new type (if changed) by giving a go template for transformation (see schema change below):

Note: the schema version has NO relationship with otomi-core's version.
Workflow:
Every time a developer changes the schema which includes these changes as DOD, the otomi migrate-values command should be performed that will massage the values to migrate to the new structure.
Schema change:
Sample part:
version: 0.23.7
changes:
  locations:
    charts.bla.someProp: someNewRootProp.someProp
  deletions:
    - charts.bla.someOtherProp
  mutations:
    # image tag went from semver to glob
    charts.bla.image.tag: 'printf "v%s"'

Tasks:
core:

[ ] Enrich values-schema.yaml

[x] changes property
[ ] a lint function to ensure that making a breaking change will be checked before commit

[x] otomi migrate-values-rev to show all history from previous versions from version control.
[ ] Create otomi migrate-values script that migrates otomi-values forward based on changes defined, and sets latest version in values.

[x] Connect otomi-tasks to bin/migrate-values.sh and bin/otomi migrates-values
[x] Load otomi-values file as json with fileName as argument to start modification per file
[ ] Create a mechanism that will be able to pin an otomi-values repository to a certain version so the modification can take place

[x] getNewVersion() mock
[ ] getNewVersion()
[x] getOldVersion() mock
[ ] getOldVersion()

[ ] otomi-values modification

[x] displacements ()
[ ] deletions ()
[ ] mutations ()

[ ] CLI functionality

api:

[ ] Add extra call to tools server just before deploy: migrate-values

Definition Of Done

[ ] Tasks are done
[ ] (Unit) Tests are added to code
[ ] Refactoring:

[ ] Rewire exported functions
[ ] Type safety for typescript

[ ] (Architecture) Design Record(s) have been added as adr/*.md and appended to list in adr/_index.md
[ ] Specs and demo files have been updated to reflect code changes
[ ] Documentation has been updated (docs/lifecycle-management/versioning)
[ ] Functionality, code, and/or documentation has been peer reviewed
[ ] Relevant team members have been notified

Copied from unassigned issues to link it with pull request for changes in otomi-core.

A schema will get a version (semver, patches are additions, minors are breaking changes)

Let's just refer to SemVer 2.0.0 then for clarity? https://semver.org

thanks for all the hard work and congrats with the lessons learned, but this darling will be closed in favor of our simplifying efforts ;)

Reopening as we need this to migrate values forward automatically.

Parking this once more as this seems more complex seen the different files involved, and knowing we don't have much need for it yet.

I have some new insights. I think we maybe should reconsider how we will approach this problem.
I was reading Designing Data-Intensive Applications, and the problem domain is "schema evolution".
Schema evolution has solutions in other serialisation/encoding formats. Thrift/Protobuf's solution is described like so:
As you can see from the examples, an encoded record is just the concatenation of its encoded fields.
Each field is identified by its tag number (the numbers 1 , 2 , 3 in the sample schemas) and
annotated with a datatype (e.g., string or integer). If a field value is not set, it is simply
omitted from the encoded record. From this you can see that field tags are critical to the meaning
of the encoded data. You can change the name of a field in the schema, since the encoded data never
refers to field names, but you cannot change a field’s tag, since that would make all existing
encoded data invalid. You can add new fields to the schema, provided that you give each field a new tag number. If old
code (which doesn’t know about the new tag numbers you added) tries to read data written by new
code, including a new field with a tag number it doesn’t recognize, it can simply ignore that field.
The datatype annotation allows the parser to determine how many bytes it needs to skip. This
maintains forward compatibility: old code can read records that were written by new code.

What about backward compatibility? As long as each field has a unique tag number, new code can
always read old data, because the tag numbers still have the same meaning. The only detail is that
if you add a new field, you cannot make it required. If you were to add a field and make it
required, that check would fail if new code read data written by old code, because the old code will
not have written the new field that you added. Therefore, to maintain backward compatibility, everyof the schema must be optional or have a default value. Removing a field is just like adding a field, with backward and forward compatibility concerns
reversed. That means you can only remove a field that is optional (a required field can never be
removed), and you can never use the same tag number again (because you may still have data written
somewhere that includes the old tag number, and that field must be ignored by new code).

Datatypes and schema evolution

What about changing the datatype of a field? That may be possible check the documentation for
details but there is a risk that values will lose precision or get truncated. For example, say you
change a 32-bit integer into a 64-bit integer. New code can easily read data written by old code,
because the parser can fill in any missing bits with zeros. However, if old code reads data written
by new code, the old code is still using a 32-bit variable to hold the value. If the decoded 64-bit
value won’t fit in 32 bits, it will be truncated.

A curious detail of Protocol Buffers is that it does not have a list or array datatype, but instead has a repeated marker for fields (which is a third option alongside required and optional ). As you can see in Figure 4-4 , the encoding of a repeated field is just what it says on
the tin: the same field tag simply appears multiple times in the record. This has the nice effect
that it’s okay to change an optional (single-valued) field into a repeated (multi-valued) field.
New code reading old data sees a list with zero or one elements (depending on whether the field was
present); old code reading new data sees only the last element of the list. Thrift has a dedicated list datatype, which is parameterized with the datatype of the list
elements. This does not allow the same evolution from single-valued to multi-valued as Protocol
Buffers does, but it has the advantage of supporting nested lists.

Ie., keys can be referenced with tags and their meaning does not depend on their "nest" in the schema.
The Apache Avro and Parquet have also rethought schema evolution but are specific to their problem domains.
Draw your own conclusions, but it seems kinda hacky to move properties around by nest to retain their meaning.

since we are only evolving forward I have no problem with our chosen approach...this is about automating a version to a newer one and never having to know what was the state before

Can you do this after the KinD delivery @svatwork

To be honest, I don't think this story is realistic and I hope we can have a chat whether this will really solve a problem.

why wouldn't it be? I observe that we create, delete and move props, and transform values. Can we not cover those use cases in the approach we designed?


Prepare for release v1.13.17

Prepare for release v1.13.17
Summary of Changes
Minor Changes:

Improved background resynchronization of nodes. Before all nodes were being updated at the same time, now we spread updates over time to average out CPU usage. (Backport PR #32885, Upstream PR #32577, @marseel)
Introduce CLI commands to troubleshoot connectivity issues to the etcd kvstore and clustermesh control plane (Backport PR #32573, Upstream PR #32336, @giorio94)
ipsec: Improve CPU usage of cilum-agent in large clusters (Backport PR #32884, Upstream PR #32588, @marseel)

Bugfixes:

.github/workflows: fix digests file creation (Backport PR #32887, Upstream PR #32860, @aanm)
[v1.13] iptables: Do not install NOTRACK rules if IPv4NativeRoutingCIDR is nil (cilium/cilium#32652, @pippolo84)
cni: Reserve local ports for DNS proxy even if IPv6 is disabled (Backport PR #32786, Upstream PR #32725, @gandro)
Fixes accidentally ignoring the preflight.nodeSelector Helm value. (Backport PR #32696, Upstream PR #32548, @squeed)
ipsec: Safely delete Xfrm state (Backport PR #32705, Upstream PR #32450, @jschwinger233)
Remove deprecated hubble.ui.securityContext.enabled from hubble-ui deployment template (Backport PR #32887, Upstream PR #32338, @stelucz)

CI Changes:

ci: Filter supported versions of EKS (Backport PR #32887, Upstream PR #32304, @marseel)
ci: Filter supported versions of GKE (Backport PR #32696, Upstream PR #32302, @marseel)
ci: l4lb: Don't hang on gathering logs forever (Backport PR #32963, Upstream PR #32947, @joestringer)
ci: l4lb: gather more infos about docker-in-docker issues (Backport PR #32696, Upstream PR #32570, @mhofstetter)
ci: l4lb: restart docker-in-docker container on failure (Backport PR #32696, Upstream PR #32600, @mhofstetter)
ci: update unsupported ci-aks k8s version from 1.26 to 1.27 (cilium/cilium#32502, @mhofstetter)
eks: Don't use spot instances (Backport PR #32696, Upstream PR #32553, @michi-covalent)
GCP OIDC instead of SA creds. (Backport PR #32709, Upstream PR #30809, @viktor-kurchenko)
gha: correctly trigger integration tests via ariane commands (cilium/cilium#32843, @giorio94)
Modify GitHub Actions Workflows to echo the inputs they are given when triggered by a workflow_dispatch event. (Backport PR #32504, Upstream PR #31424, @learnitall)
Use GH_RUNNER_EXTRA_POWER for CI image workflow (Backport PR #32504, Upstream PR #32402, @michi-covalent)
workflows: ignore "No egress gateway found" drops (Backport PR #32696, Upstream PR #32564, @jibi)
workflows: Remove stale CodeQL workflow (Backport PR #32696, Upstream PR #32084, @pchaigno)

Misc Changes:

(v1.13) Bump golang.org/x/net (cilium/cilium#32791, @ferozsalam)
background-sync: fix bootstrap issue and edge-case with 1 node (Backport PR #32885, Upstream PR #32630, @marseel)
bump cni plugins to v1.5.0 (Backport PR #32696, Upstream PR #32629, @antonipp)
Bump timeout of lint-build-commits.yaml (Backport PR #32786, Upstream PR #32746, @YutaroHayakawa)
chore(deps): update all github action dependencies (v1.13) (cilium/cilium#32499, @renovate[bot])
chore(deps): update all github action dependencies (v1.13) (cilium/cilium#32742, @renovate[bot])
chore(deps): update all github action dependencies (v1.13) (cilium/cilium#32845, @renovate[bot])
chore(deps): update cilium/little-vm-helper action to v0.0.18 (v1.13) (cilium/cilium#32582, @renovate[bot])
chore(deps): update dependency cilium/hubble to v0.13.5 (v1.13) (cilium/cilium#32950, @cilium-renovate[bot])
chore(deps): update docker.io/library/golang:1.21.10 docker digest to 16438a8 (v1.13) (cilium/cilium#32740, @renovate[bot])
chore(deps): update docker.io/library/ubuntu:22.04 docker digest to 19478ce (v1.13) (cilium/cilium#32926, @renovate[bot])
chore(deps): update docker.io/library/ubuntu:22.04 docker digest to a6d2b38 (v1.13) (cilium/cilium#32376, @renovate[bot])
chore(deps): update github/codeql-action action to v3.25.5 (v1.13) (cilium/cilium#32516, @renovate[bot])
chore(deps): update go to v1.21.11 (v1.13) (cilium/cilium#32896, @renovate[bot])
chore(deps): update google/cloud-sdk docker tag to v479 (v1.13) (cilium/cilium#32927, @renovate[bot])
chore(deps): update hubble cli to v0.13.4 (v1.13) (cilium/cilium#32837, @renovate[bot])
chore(deps): update kindest/node docker tag to v1.26.15 (v1.13) (cilium/cilium#32583, @renovate[bot])
chore(deps): update stable lvh-images (v1.13) (patch) (cilium/cilium#32844, @renovate[bot])
contrib: Remove CHARTS_PATH dependency (Backport PR #32696, Upstream PR #32328, @joestringer)
Docs: add note about AKS kube-apiserver entity (Backport PR #32696, Upstream PR #32464, @darox)
Miscellaneous improvements to the clustermesh troubleshooting guide (Backport PR #32573, Upstream PR #32552, @giorio94)
Remove release scripts (Backport PR #32963, Upstream PR #32938, @aanm)

Other Changes:

[v1.13] bugtool: Avoid sensitive data in envoy config dump (cilium/cilium#32966, @sayboras)
[v1.13] envoy: Bump envoy version to v1.28.4 (cilium/cilium#32911, @sayboras)
[v1.13] images: update cilium-{runtime,builder} (cilium/cilium#32449, @michi-covalent)
envoy: Update envoy 1.27.x to 1.28.3 (cilium/cilium#32540, @sayboras)
install: Update image digests for v1.13.16 (cilium/cilium#32547, @nebril)

⚠⚠⚠ i used a modified version of start-release.sh because i could not create a project for v1.13.18 due to https://github.blog/changelog/2024-05-23-sunset-notice-projects-classic/.
as a result, https://github.com/cilium/cilium/blob/bf9a1ae1b2d2b2c9cca329d7aa96aa4858032a61/.github/maintainers-little-helper.yaml#L1 is still pointing to v1.13.17 project.

@julianwiedmann Can you give it another quick look, please?


Remove seed blocks for structurally invalid transactions + reformat

This PR removes seed blocks that after additional testing have been deemed unnecessary as they only contain structurally invalid transactions.
Removing unneeded seed blocks serves to optimize initial parsing by removing unnecessary work.
Revised seed block list to 390000 passes all checkpoints to 390000.
Resolves https://github.com/OmniLayer/omnicore/issues/329.

Did you try a test parse by any chance? :)

Did you try a test parse by any chance? :)

I did indeed... (a --startclean with the new seedblock list, passed all checkpoints) - did I miss something?

Haha, no, this was not where I was going. Just wanted to make sure! :)


Implementing additional Query-level retry logic

This retry logic was originally proposed by @ivanprado.
I've refactored the source code moving most part of the logic to the QueryError exception.
I've also introduced the sub-batches retry.

[ ] Revert Python 3.5 removal
[ ] Skip test cases when incompatible with Python 3.5
[ ] Experiment with standalone method for single queries with additional retry support

I talked to @ejulio today. Another option proposed by him is turning the request method into an async generator instead of returning a list of responses. The code would retry only failed responses. We would promptly yield successful ones.
Another modification that could take place is receiving a flag enabling or disabling the additional retry logic for Query-level errors.

@ivanprado @kmike @ejulio
There you are, guys. I've just refactored the source code to use a max retries integer argument for Query-level errors.
Let me know if it looks good to you and I could proceed to documentation.

@ejulio @ivanprado @kmike
Review season is open again guys!
I've added some comments and fixed lastest feedback.
Let me know if there's something pending.
I believe the PR is ready to be merged.

@victor-torres I'll give another review now, but I think before merging it would be a good idea to do a run as the litmus test. I'll suggest you a URLs dataset.

Since we've moved the concern with tenacity.RetryError to another issue, are you ready to approve this PR, @ivanprado?

are you ready to approve this PR, @ivanprado?

From the code perspective, yes, the PR is ready. Great work! :+1: Only this comment from my side remains to be addressed: https://github.com/scrapinghub/scrapinghub-autoextract/pull/7#discussion_r455707736
I'll wait until seeing the results for tests you will run for the final green light to the PR.

Thanks @victor-torres for the implementation, and @ivanprado + @ejulio for the reviews and suggestions!

Thank you for all the time invested in reviewing this code, @kmike, @ivanprado, and @ejulio! 🚀


Peer review

Data analysis review checklist
Reviewer:
Conflict of interest

[✓] As the reviewer I confirm that I have no conflicts of interest for me to review this work.

Code of Conduct

[✓] I confirm that I read and will adhere to the MDS code of conduct.

General checks

[✓] Repository: Is the source code for this data analysis available? Is the repository well organized and easy to navigate?
[✓] License: Does the repository contain a plain-text LICENSE file with the contents of an OSI approved software license?

Documentation

[✓] Installation instructions: Is there a clearly stated list of dependencies?
There is a list of dependencies, but under a section called “Running the project locally
” instead of an individual section named “Dependencies”
[✓] Example usage: Do the authors include examples of how to use the software to reproduce the data analysis?
[✓] Functionality documentation: Is the core functionality of the data analysis software documented to a satisfactory level?
[✓] Community guidelines: Are there clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support

Code quality

[✓] Readability: Are scripts, functions, objects, etc., well named? Is it relatively easy to understand the code?
[✓] Style guidelines: Does the code adhere to well known language style guides?
[✓] Modularity: Is the code suitably abstracted into scripts and functions?
[✓] Tests: Are there automated tests or manual steps described so that the function of the software can be verified? Are they of sufficient quality to ensure software robustness?

Reproducibility

[✓] Data: Is the raw data archived somewhere? Is it accessible?
[✓] Computational methods: Is all the source code required for the data analysis available?
[✓] Conditions: Is there a record of the necessary conditions (software dependencies) needed to reproduce the analysis? Does there exist an easy way to obtain the computational environment needed to reproduce the analysis?
[✓] Automation: Can someone other than the authors easily reproduce the entire data analysis?

Analysis report

[✓] Authors: Does the report include a list of authors with their affiliations?
[✓] What is the question: Do the authors clearly state the research question being asked?
[✓] Importance: Do the authors clearly state the importance for this research question?
[✓] Background: Do the authors provide sufficient background information so that readers can understand the report?
[✘] Methods: Do the authors clearly describe and justify the methodology used in the data analysis? Do the authors communicate any assumptions or limitations of their methodologies?
[✓] Results: Do the authors clearly communicate their findings through writing, tables and figures?
[✓] Conclusions: Are the conclusions presented by the authors correct?
[✓] References: Do all archival references that should have a DOI list one (e.g., papers, datasets, software)?
[✓] Writing quality: Is the writing of good quality, concise, engaging?

Estimated hours spent reviewing: ~1.5
Review Comments:
Please provide more detailed feedback here on what was done particularly well, and what could be improved. It is especially important to elaborate on items that you were not able to check off in the list above.

The report can be run reproducibly with commands provided in README.

The confusion matrix does not match with the text below. For example, the matrix only seems to provide the results predicted by the model as FP and FN are all 0 which is almost impossible while in the text below, it is said that “[the model] predicted not fire correctly in 25 cases, predicted fire correctly in 32 cases and predicted incorrectly in only 3 cases. ”. Therefore, I would doubt that something went wrong with the code which creates the confusion matrix (which does not have a chunk name).

The r chunk “entries-by-class” and the confusion matrix is not saved out by previous steps so it is still produced by code. Therefore, save out these tables or png files instead of still producing by code. This will likely reduce some of the time for “make all” to run.

Maybe using “COPY” in dockerfile to put files that are required for the report instead of using volumes because it looks a little messy for the Rstudio container which also contains Dockerfile, Contributing, etc. These files are not required for producing the report in the container.

The limitations seem not to be included in the conclusion or in the report after discussing the results.

Attribution
This was derived from the JOSE review checklist and the ROpenSci review checklist.

if the text above does not render correctly, please view this on:
https://docs.google.com/document/d/1VHSGKmrRRjxKUHFsHU71t34IBLMV98AaVtokeCh-iWY/edit?usp=sharing

Concerning the following bullet point:

Maybe using “COPY” in dockerfile to put files that are required for the report instead of using volumes because it looks a little messy for the Rstudio container which also contains Dockerfile, Contributing, etc. These files are not required for producing the report in the container.

I think that it is better to mount the whole volume, because if changes are made to the project inside of the container, they are also persisted on the local machine this way. If we would just COPY them, then the changes would be gone after closing the container if we didn't push them to a remote repository.

We create the issues #171 #172 and #173 out of this peer review. These will be adressed accordingly. As we now have separate issues we will close this issue now. Thank you for your peer review 👍


refactor(styles): separate concerns from styles and tokens

diffrentiate harmless style tokens from styles that affect the application (side-effects)
this describes the updated interface and the scope of this PR
https://github.com/Vonage/vivid-3/blob/bf36987ea9a95e0a9ce9f55e8c89a3efa2289fd7/libs/components/README.md#L33-L65

That's an issue as now we never apply styles (including color-scheme) on root
Fixed color-scheme to not propagate to the viewport background if set on the  (253565@main)


Bluetooth audio not working correctly

When playing anything from the browser, using a bluetooth connected speaker, the sound is very choppy to the extent that it is unusable.
Setup:
Raspberry Pi 4B with 4GB of RAM
FydeOS 11.4
Chromium: Version 86.0.4240.260  (32 bitar)
Plattform: 134<IP_ADDRESS> (Release Build v11.4 - sp2) stable-channel rpi4-fydeos
Kanal: beta-channel
Firmwareversion:
ARC aktiverat: true
ARC: 6104653
Med företagsregistrering: false
Utvecklarläge: true
Keyboard and touchpad from Trust connected via wireless transmitter.
Screen connected to HDMI1 port in 1080p
FydeOS running off a Samsung 64GB memory stick
To Reproduce
Steps to reproduce the behavior:
0. Connect the bluetooth speaker using settings in FydeOS

Go to youtube.com
Click on any video
Start playing
Listen to the sound from the bluetooth speaker. It is horrible and any dialogue can not be understood.

Expected behaviour
Bluetooth audio should be as clear as audio through the jack.
Additional context
Lowering the resoultion on the video has no effect
Using the audio-player to play a file on the computer has the same effect
Using a audio-player from the Linux-environment (Penguin) has the same effect

https://github.com/openfans-community-offical/Debian-Pi-Aarch64/blob/master/README.md#3-164-bluetooth-audio-connection-lost
In this project they got the same problem；
they used this way to fix it：
“3-16.4 Bluetooth Audio connection lost
Reason:
Pi's Bluetooth has compatibility issues with certain hardware between alsa and pulseaudio.
Solution:
Disable Bluealsa Service, just use pulseaudio for bluetooth audio. Run the command below and reboot:
systemctl mask  bluealsa.service
Note： Here U must use "mask" for unactive bluealsa.service, mustn't use "disable" !!”
Can we do in the same way？

I'm going to put some stress on this. It doesn't appear that the latest version of Chromium has any issues with bluetooth, but for some reason we do. What could be the issue?

Chromium OS does not have the best Bluetooth support, this is an inconvenient fact. For the original issue about "choppy", we could also reproduce this while high-res youtube video playback. Reducing the resolution or just playing a static audio file on a local drive sounds better. This is unfortunately due to the performance constrain of the Pi.
We will look into continuously optimising Bluetooth performance but I sense this is a long shot. For immediate resolution, it's best to connect audio via HDMI or a 3.5mm jack.

I play netflix and youtube on manjaro arm with bluetooth sound bar without choppy playback so i disagree that it is the constraints of the raspberry pi specifically.  perhaps a newer version of chromium os is needed?  If there is one.

fixed, try r92-r2 release


Add a LICENSE file

Because the skeleton is using the MIT License, we should add the LICENSE
file. It will prevent translators to release the language extension
without a LICENSE file (MIT or not, they will be able to change that
file accoring to their choosen license). This will be explained in the
future L10n documentation.

Good idea. :+1:

I'm worried that people will forget to change my name in the copyright... we should make a special note of this in the documentation.

Good point! Noted.


outbound.send_email doesn't like \r\n

Change \n to \r\n at example http://haraka.github.io/manual/Outbound.html
var contents = [
    "From: " + from,
    "To: " + to,
    "MIME-Version: 1.0",
    "Content-type: text/plain; charset=us-ascii",
    "Subject: Some subject here",
    "",
    "Some email body here",
    ""].join("\r\n");

Received email is empty:
Received: (Haraka outbound); Fri, 01 Aug 2014 16:23:52 +0300
Message-Id: <5E068B74-AB49-4602-B1F9-0A8DA1B76983@zeus>
Date: Fri, 01 Aug 2014 16:23:52 +0300

This should be fixed by #817


Frame rate drops (outside UnrealEditor Window)

I am trying to increase the frame rate of server.
I usually edit the town and launch Carla from UnrealEditor itself.
My issue is that, frame rate of the server drops to 3-5 fps when I am outside Unreal Editor Window.
For example, when I run manual_control.py and check the frame rate of server (it is 3fps). But, when I switch back to UnrealEditor the frame rate increases to 40fps.
Is there any settings for this? Or any other way to have high fps?
Outside UnrealEditor window

Inside UnrealEditor window

Yes there is! :)
Inside the Unreal Editor click on 'Edit' in the top bar, then under 'General' go to 'Performance' and deactivate the flag 'Use Less CPU when in Background'. Your fps should then not change when working outside of the Unreal Editor.


Slack invite link expired

I clicked on the link to join the slack but it expired.

We're not really using the Slack so I'm going to close this one


Feat: Moved axios instance into Configuration and using it as single source of truth

Summary
Feature: User can now give its own axios instance to be used. If none is given, global one is used. This allows additional configurations such as using axios interceptors, etc.
Chore: This also consolidates Configuration as the single source of truth for the axios instance.
Type of Change
Please mark the relevant option(s) for your pull request:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Code refactoring (improving code quality without changing its behavior)
[ ] Documentation update (adding or updating documentation related to the project)

Checklist
Please ensure that your pull request meets the following criteria:

[x] I have read the Contributing Guide
[x] My code follows the project's coding style and best practices
[x] My code is appropriately commented and includes relevant documentation
[ ] I have added tests to cover my changes
[ ] All new and existing tests pass
[x] I have updated the documentation, if necessary

Thanks for your contribution @AlexDochioiu! @Vardominator Could you handle the versioning aspect of this PR (changeset)?


Disable clinic upload in old CLI.

Tell users to update because the Upload Server requires authentication
now.

I'm not sure this is useful.
What's the current response of the 2.x line with the new server?

With old CLI, you get:

which is not actionable to someone who doesn't know that these updates have happened.

I think we should just issue a deprecate warning for clinic < 3 once we release.


AuthenticateResult.Fail(failreason) fails to propagate failreason through the stack

I am writing my own authentication middleware and upon returning AuthenticateResult.Fail("fail reason") in HandleAuthenticateAsync() I am expecting this to result in a challenge and somehow use this information during the challenge.
the "fail reason" string gets lost at some point when I would like to be able to see it passed to HandleForbiddenAsync or HandleAuthenticateAsync during the challenge. I've narrowed it down to perhaps having some properties passed in the challenge result from the result of authentication. At https://github.com/aspnet/Mvc/blob/c7a46e4caf0d1f25dd5f8bcd385af50b34b0f5dd/src/Microsoft.AspNetCore.Mvc.Core/Authorization/AuthorizeFilter.cs#L118 I wonder if the challenge result shouldn't be authenticated with properties derived from the authentication step at
https://github.com/aspnet/Mvc/blob/c7a46e4caf0d1f25dd5f8bcd385af50b34b0f5dd/src/Microsoft.AspNetCore.Mvc.Core/Authorization/AuthorizeFilter.cs#L92
it seems that this would resolve the issue I'm seeing as the rest of the stack seems to properly pass along this informationg to HandleForbiddenAsync and HandleAuthenticateAsync.

/cc @HaoK

Also I would like to be able to select between different deny behaviors in my middleware (Unauthorized vs Forbidden), it seems that upon executing the challenge the behavior that is passed is always Automatic, and this always leads to HandleUnauthorizedAsync. According to https://github.com/aspnet/Security/blob/5cd236c1b069cebecf53dbe6380e39933986eb47/src/Microsoft.AspNetCore.Authentication/AuthenticationHandler.cs#L317 the Principal should be null. But there is no way to create a ticket with a null principal since the property setter is private.

You shouldn't be setting the ticket directly, but you can call AuthenticateResult.Fail to return a result with a null ticket in your HandleAuthenticateAsync() method.
To change the behavior of Authorize, you should be able to IAsyncAuthorizationFilter and implement OnAuthorizationAsync however you like I believe.

For your original question of how to flow the failure message out of Authenticate, that's not something we are doing today, as its mostly an internal error for the handler (logging/debugging remote auth errors mostly).  As you mention you could certainly flow your error information in the AuthenticationProperties that is returned by your Auth middleware, and then pass it along in your call to challenge.

I haven't been able to trigger Forbidden, if the ticket is null, then the behavior becomes UnAuthorized.

Yep, that is the behavior for Automatic that comes from the AuthenticationHandler base class.  You can always implement an Auth middleware without using that base class too.

@HaoK is this still relevant?

Nope, challenge behavior was removed in preview 2, so Challenge/ForbidResult give you full control now

OK, closing this then since it doesn't seem to relevant for the future.


PromQL  resets()  counting wrong changes

What did you do? I tried to find number of times a counter has went down using resets
What did you expect to see? I expect that it should return number of times counter has went down
What did you see instead? Under which circumstances? It is wrongly counting.
Example :
188 -> 248  = From 188 to 248, The value has increased, But not decreased, But still it is counting as one change.
Environment: Linux

System information:
insert output of uname -srm here

Prometheus version:
insert output of prometheus --version here 2.19.2

Alertmanager version:
insert output of alertmanager --version here (if relevant to the issue)

Prometheus configuration file:

insert configuration here

Alertmanager configuration file:

insert configuration here (if relevant to the issue)

Logs:

insert Prometheus and Alertmanager logs relevant to the issue here

Can you share the exact input that is going into resets?

I'm running into this problem as well. For the some_query, this is my resets graph that causes rate queries to return invalid results.
resets(some_query[5m])

Looking at only some_query I see the following increasing values, no decreases:

The following is the raw data. As you can see, there is nothing decreasing:
{"status":"success","data":{"resultType":"matrix","result":[{"metric":{ "secret": "stuff" },"values":[[1599239976.031,"72371"],[1599239976.032,"72371"],[1599240006.031,"78369"],[1599240006.032,"78369"],[1599240036.031,"85360"],[1599240066.031,"90303"],[1599240066.032,"90303"],[1599240096.031,"95269"],[1599240096.032,"95269"],[1599240126.031,"103291"],[1599240126.032,"103291"],[1599240156.031,"109188"],[1599240156.032,"109188"],[1599240186.031,"115143"],[1599240186.032,"115143"],[1599240216.031,"120988"],[1599240216.032,"120988"],[1599240246.032,"123920"]]}]}}

Build info:

Version | 2.19.2
-- | --
c448ada63d83002e9c1d2c9f84e09f55a61f0ff7
HEAD
root@dd72efe1549d
20200626-09:02:20
go1.14.4

@akshayvijapur any updates? Maybe, you can send a range query for that particular query via HTTP request and mention the response for better understanding.

I am closing this due to lack of feedback.


Customize the location of ".vscode" directory

I found that VSCode will automatically create the $HOME/.vscode directory to store user data and extensions. I wonder if there is a way to customize the path of these files with environment variables, such as $VIMRC for vim and $ZDOTDIR for zsh. Currently I only see one related solution, and it does not support macOS.

I don't see any issue, why your related solution should not work on mac? However, it does not work in portable mode.
See related issue #32933

Hey! Thank you for your comment. Let me elaborate on my problem. I checked #32933 and found it cannot fix my problem. Yet I can launch VS code in the terminal with options --extensions-dir and --user-data-dir to specify directories. But I don't know whether there is a way in macOS to pass these options every time VS code launches even not from the terminal. If you have solutions, I would appreciate it a lot.
I find many applications like to create dot folder in $HOME, e.g. .conda, .vim, .jupyter. Some of them did this because they need a location with write permission to store data and configurations. And most of them provide useful environment variables to help user customize their preferable location. In this issue, I would like to store user data in $XDG_CONFIG_DIR/vscode so that I can manage all my configurations with ease. I know that I can create a symlink to the .vscode directory, but I prefer a tidy home directory.

If you are talking about launching it via macOS UI, you can take a look here.
If you want to open it via CLI with those arguments, you can add an alias in your .zshrc.
But such specific questions should be asked on StackOverflow, where the (VSCode) community will be happy to help.
@isidorn is passing (some) arguments via environmental variables to VSCode something we want to pursue? Or can we close this issue?

Arguments can be passed via environment variables. but (user-data-dir) is not a valid env variable format.
There are no plans to support these, hence closing.


Minor fixes involving IndexErrors

I noticed that when there are no tasks present, certain functions in application.py and base_list_box.py could crash the application. This pull requests fixes the issues by checking the lists' lengths are greater than 0.

Looks good now. Can you squash your work into one commit, then I think it will be ready for merge.

The commits have been squashed.

Thanks for your work!


refactoring code with List Comprehension

refactoring code with List Comprehension which is more pythonic, concise and efficient;how do think this change which has practical value？
static_idx=[i for i in range(1000)]
dynamic_idx=[i for i in range(1000)]
code='''
idx = []
for (s, d) in zip(static_idx, dynamic_idx):
    if d is not None:
        idx.append(d)
    elif isinstance(s, tuple):
        idx.append(slice(s[0], s[1], s[2]))
    else:
        idx.append(s)
'''
total_time_1 = min(
    timeit.repeat(code, globals={**globals(), **locals()},
                  repeat=1, number=1000))
pythonic_code='''
idx = [d if d is not None else slice(s[0], s[1], s[2]) if isinstance(s, tuple) else s for (s, d) in zip(static_idx, dynamic_idx)]
'''
total_time_2 = min(
    timeit.repeat(pythonic_code,
                  globals={**globals(), **locals()},
                  repeat=1, number=1000))
print("total time: ", total_time_2, total_time_1, total_time_1 / total_time_2)

output:
0.05620845900000049 0.08211149999999989 1.4608388392216762

Hi - thanks for looking into this. Improving JAX trace times is a great goal! That said, at first blush, I'm not convinced that microbenchmarks at this level are the best way to approach reducing JAX's overhead. Yes it's a ~30% improvement in runtime, but that improvement amounts to ~30µs per run when parsing 1000 static and 1000 dynamic indices, which I suspect is far more than are ever parsed in practice. If we assume the savings is linear in the number of parsed indices, then I expect the typical savings for a real use-case would be perhaps tens of nanoseconds for a typical gather operation. That's not zero, but I don't think it's something worth dwelling on in the overall computational cost of executing a JAX program.
Now I may be wrong... it would be interesting to see a line profiler output of a typical JAX computation, and see which operations are contributing the most. If _merge_static_and_dynamic_indices is high in that, then this may be a good change to consider.

Closing as stale.


gifsicle pre-build test failed

Output:
Response code 404 (Not Found)
gifsicle pre-build test failed
compiling from source
Error: Command failed: C:\WINDOWS\system32\cmd.exe /s /c "autoreconf -ivf"

fixed 0.5.1

Still have this issue
#18 224.9 Output: #18 224.9 ⚠ spawn /workspace/node_modules/gifsicle/vendor/gifsicle ENOENT #18 224.9   ⚠ gifsicle pre-build test failed #18 224.9   ℹ compiling from source #18 224.9   ✖ Error: Command failed: /bin/sh -c autoreconf -ivf #18 224.9 /bin/sh: autoreconf: not found


feat(constants): update model constants

Description

Add new models Mistral Nemo and Codestral Mamba
Add aliases to models constant to be deserialized seemlessly from the versioned forme (e.g.: "mistral-large-2407")
The commonly named Mistral Large 2 is now constants::Model::MistralLargeLatest when the old one is Model::MistralLarge

Checklist

[ ] I updated the tests accordingly. Or I don't need to.

The addition of an enum variant can actualy break match blocks if they don't have a default match arm.
Ok I'll update the tests.

Thank you! I'll merge this one and release it for a start.


[SPARK-48941][PYTHON][ML] Replace RDD read / write API invocation with Dataframe read / write API

What changes were proposed in this pull request?

PysparkML: Replace RDD read / write API invocation with Dataframe read / write API
Why are the changes needed?

Follow-up of https://github.com/apache/spark/pull/47341
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Unit test.
Was this patch authored or co-authored using generative AI tooling?

No.

Merged to master.


How to retrieve XML file or package using JSforce?

How to retrieve XML file or package using JSforce?
I want to input as Json format like this:
var metadata = [{
fullName: 'TestObject1__c',
label: 'Test Object 1',
pluralLabel: 'Test Object 1',
nameField: {
type: 'Text',
label: 'Test Object Name'
},
deploymentStatus: 'Deployed',
sharingModel: 'ReadWrite'
}, {
fullName: 'TestObject2__c',
label: 'Test Object 2',
pluralLabel: 'Test Object 2',
nameField: {
type: 'AutoNumber',
label: 'Test Object #'
},
deploymentStatus: 'InDevelopment',
sharingModel: 'Private'
}];
and output as XML format or package, any idea?

If you want to work on package and deploy features you should use the metadata tools provided by jsforce.
https://github.com/jsforce/jsforce-metadata-tools

triaging old issues...
checkout :https://jsforce.github.io/document/#retrieve-deploy-metadata-file-based-
https://github.com/jsforce/jsforce/blob/af8a10e84557d95e20a62dae37e9dbf1e4d50fa8/src/api/metadata.ts#L320


Upgrade service parent to 3

LGTM.

GOAWAY issue might be due to the heavy header or high load at the moment to the server, then increasing the throughput capacity like adding thread pool number might be a way to go. @ligangty, @sswguo

GOAWAY issue might be due to the heavy header or high load at the moment to the server, then increasing the throughput capacity like adding thread pool number might be a way to go. @ligangty, @sswguo

Yeah, we can mock the POST request locally with the example high load to see if the server side has the GOAWAY issue.


Use compactMap instead of flatMap

In Swift 4.1 there is this kind of information:

'flatMap' is deprecated: Please use compactMap(_:) for the case where closure returns an optional value.

Thank you for help👍


Exclude files and folder from dist

Described here https://redd.it/2jzp6k

Thanks for merging.
Anyway, may I ask. Are you guys has plan to implement it for another repo under slimphp org?

@feryardiant if you see any other repo that would benefit from this, send a PR.

Got it :+1:


proposal: x/exp/slices: add ContainsFunc

During the design of the slices package ContainsFunc function was dropped at the time of discussion (https://github.com/golang/go/discussions/47203#discussioncomment-1006027). Briefly, the discussion was about the signature of the function and how often it is used.
I suggest finally making ContainsFunc, since we have Contains, so it will be consistent to have ContainsFunc as well. Also, it's just convenient to have such a function. Talking about the signature, for me, it's reasonable to make it the same as for IndexFunc: ContainsFunc[E comparable](s []E, f func(E) bool) bool
Note:
I've created a PR for this change because I'm new here and didn't know that such change needs a proposal. In case you are curious  – here it is: https://github.com/golang/exp/pull/39

This operation is very common. It also often goes by the name Any. Yes, ContainsFunc matches the pattern in the package, but Any is delightfully concise.
It'd be nice to also be really nice to have the dual, All. Yes, like any dual, it is easy to implement All in terms of Any, but given the frequency of use, it's worth having the clarity of a separate function.

This proposal has been added to the active column of the proposals project
and will now be reviewed at the weekly proposal review meetings.
— rsc for the proposal review group

It sounds like the main justification would be that we have Index and Contains (which wraps Index), and we have IndexFunc but not ContainsFunc. So adding ContainsFunc would complete the set.
@bradfitz reports that in the Tailscale source tree there are four implementations of ContainsFunc, only one generic. So that argues for adding ContainsFunc.
I am sympathetic to @josharian's comment about Any, but we already call it ContainsFunc elsewhere in the standard library, so we should probably keep that name here.

<tangent>
As a tangent regarding "any", if we did want to add a function called Any in Go, I think it would be nice if we could make it return (T, ok) rather than just a bool, so that you can actually extract the thing that matches the predicate. Perhaps it would be
func Any[T any](x []T, f func(T)bool) (T, bool)

or perhaps it would be
func Any[T, U any](x []T, f func(T)(U, bool)) (U, bool)

The latter is most analogous to what Common Lisp calls 'some'.
Writing out those type signatures, I notice the collision between 'Any' and 'any', which have very different meanings. That makes me think maybe the function should have a different name. Maybe Some.
If anyone (someone?) wants to push further on this, feel free to file a separate proposal issue.
</tangent>

I'd like to push a little bit to consider using Any and All, since they are such nice, succinct names. And if we use ContainsFunc, it's not at all clear what to call All.
I'd call the (T, ok) flavor of this  First, since that also makes it clear which element gets returned in case multiple match. (Last might also be desirable.)

Personally, I would like to see these signatures:
func Any[T any](x []T, f func(T)bool) (bool)
func All[T any](x []T, f func(T)bool) (bool)

It's pretty convenient to use Any in if conditions and switch cases, which would be less convenient if it would return something more than a single bool value.
First and Last functions look good to me, can implement them as well.

I appreciate the elegance of Any and All, but we have the analogy already set up: Index is to Contains as IndexFunc is to ___. The answer is clearly ContainsFunc. We should use the name people already familiar with the other APIs will expect if we're going to do this.
(In strings and bytes, we also have IndexAny and ContainsAny, which is something else entirely.)

Based on the discussion above, this proposal seems like a likely accept.
— rsc for the proposal review group

No change in consensus, so accepted. 🎉
This issue now tracks the work of implementing the proposal.
— rsc for the proposal review group

This work was completed by https://go.dev/cl/417374.


[ZEPPELIN-704] Display elapse time for long running paragraph

What is this PR for?
For long running paragraph, it is hard to know how long it has already been running. We should either have the elapsed time displayed
What type of PR is it?
[Bug Fix ]
Todos
What is the Jira issue?
ZEPPELIN-704 (https://issues.apache.org/jira/browse/ZEPPELIN-704)
How should this be tested?
-Open a note.
-Run a paragraph , It should show you the elapsed time.
Screenshots (if appropriate)

Questions:

Does the licenses files need update?No
Is there breaking changes for older versions?No
Does this needs documentation?No

Thanks @sagarkulkarni3592 for very useful feature.
It works nicely with 'default' looknfeel. However, 'simple' looknfeel it displays elapsed time above the progress bar on left side. like

Could this be displayed below the progress bar on the right side in 'simple' looknfeel? the same position that "Took XX seconds" message placed.

@Leemoonsoo Thank you for your suggestion.
I have done the necessary changes to make it appear on the same position that "Took XX seconds" message placed.

@sagarkulkarni3592 Thanks for taking care.
I tried the last commit and i can see text is displayed on the right corner in 'simple' looknfeel.
However, "Took xx seconds" and "xx seconds elapsed" are still displayed in the different place. Could you make it display at exactly the same place where "Took xx seconds" positioned?

@Leemoonsoo Thanks for the suggestion.
Sorry for the delay. I have done the necessary changes.

Had to change property of Simple.css top: -9px from -13px as it was appearing on the loading blue line.
Is this good?

Text floats outside paragraph

Even after merging the pull request for ZEPPELIN , it was showing "Took xx seconds. Last updated by undefined at time XXX".
Fixed this to "Took xx seconds. Last updated by anonymous at time XXX".

@prabhjyotsingh Thank u for the suggestion about text float.
I have made the necessary changes. Is this ok?

If there is difference in timezone for client and zeppelin server then UI shows a wrong value.

@prabhjyotsingh Thank you for the bug. Fixed this using standard ISO time format. Tested with different time zones.

Checkout the time zones.

This also changes the time format (customizable in code) at statement "last updated by xx at ".

Added moment.js : Now, took xx seconds text will show as per moment.js documentattion. Same is the case for elapsed time.

I would prefer keeping the elapsed wording, otherwise it doesn't give indications that it is for the running process.

@corneadoug Thank you for the suggestion.
For a long running process, say running for more than hour, it will show something like "3601 seconds elapsed". The number in seconds does not look good. What will be your suggestion on this?

@sagarkulkarni3592 if you follow moment.js documentation
You can use fromNow(true) to remove the ago

@corneadoug So, it will be "a few seconds elapsed" or "2 minutes elapsed". It this good?

@sagarkulkarni3592 "Started 2 minutes ago" looks more gracious :)

@corneadoug Latest commit have both the changes you suggested. :)

@prabhjyotsingh corrected the test cases. :)

Tested, works well. LGTM!

Tested, Merging if there is no more discussions

Merging as it includes HOTFIX for failing Integration Tests

@sagarkulkarni3592 could you please assign a JIRA issue to yourself?


Update Runnable

Whole lotta miscellaneous clean-up in here. I tried to keep the commit naming accurate to maintain a sense of what's changed.

Still a couple things to review/change, and will add back in all the unite tests, but opening this PR so an approval isn't the bottleneck.


[Bug] Android TV screen flickering

Platform
Android tv
...
Screenshots/Videos
If applicable, add screenshots/videos to help explain your problem.

Try this version
com.redphx.betterxc_0.3-3.apk.zip

Your device's H.264 encoder is buggy. Nothing I can do about that.


Deme should store ancestor indexes rather than the hash map

Currently, a Deme stores HashMap<String, usize> to map ancestors to ancestor indexes in the Graph.
This is not great:

The Strings are now stored 2x.  Once in the required ancestors field and again in the hashmap.
It is not great to require hashing to find an ancestor when zipping along the ancestor names + a vector of IDs should suffice.

We should:

Deprecate Deme::ancestor_map
Replace it with Deme::ancestor_indexes (marked as "no serialize")

Closed by #352


Is anyone working on Draggable Lanes?

I see that there seems to be some preparation for draggable lanes, but not yet implemented?

Oh, looking forward to it, thank you！

Check out this storybook for intended behaviour: http://rcdexta.me/react-trello/?selectedKind=Drag-n-Drop&selectedStory=Basic&full=0&down=0&left=1&panelRight=0
Usage code here: https://github.com/rcdexta/react-trello/blob/master/stories/DragDrop.story.js
Added two handlers specific to lane drop. Pull the latest release to see changes in effect.

Thanks very much! But sometimes drag failure?

@changyu72 Could you give more details? Are we talking lane or card dnd?

When dragging lane, over other lane through a state similar to the drag of card down, the dragged lane  go to the first, and then  can not drag anything.

@changyu72 Thanks for pointing that out. The latest release patch should fix that

thanks!


Use host-scanner deployment from an external source

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

No. It's an improvement

Describe the solution you'd like.

KS will use an external source for the host scanner deployment. I suggest the host scanner repository. This way we:

Can define a host-scanner image version (in the external source) to improve stability.
Don't need to update the deployment file for every host-scanner version update.
Related discussion: https://github.com/kubescape/kubescape/pull/877#discussion_r1002930409

Describe alternatives you've considered.

The current way is a good alternative but it has some downsides as I described.

Not sure about this one.
Host sensor isn't differ than any other external package.
Just like any other package which requires rebuilding for each version upgrade - so the host sensor.

Sounds like there's no action here, so closing this issue.  Please re-open if it's still relevant.


TM support with reserved private IP address space

[
Hi Team,
As per FAQ section, reserved private IP ranges are not supported as endpoint in traffic manager. Link
But currently portal is accepting this range of IP as endpoint and in few cases TM can configure like an internal traffic manager as well. Means to distribute traffic to different regions over private virtual network. So currently in the documentation it is not clear that, is it allowed to do such configuration or not.
As per FAQ, if private IP range is not allowed then, portal should not allow to configure endpoint with those range.
OR if TM is allowed to configure for distributing traffic over private network , then highly appreciated to mention that in FAQ section.
]

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

ID: d9522edc-ac04-6c89-e061-59fa788e28ed
Version Independent ID: 4cafaeee-5b0a-7f50-7c71-a8c3abf4e881
Content: Azure Traffic Manager - FAQs
Content Source: articles/traffic-manager/traffic-manager-FAQs.md
Service: traffic-manager
GitHub Login: @duongau
Microsoft Alias: duau

@cloud4free  Thank you for your feedback . We will investigate and update the thread further.

@cloud4free , could you please clarify if you are referring to External endpoints?

Yes, you are right. I was referring to  External endpoints.


[REQUEST] Ease tracking of faulty GTFS rows

Is your feature request related to a problem? Please describe.
It is sometime difficult to track down faulty GTFS entities with the information given in the notice description.
Describe the solution you'd like
Improve said description, add element to improve tracking of faulty GTFS entitie
Additional context
External contribution, question 2: https://github.com/MobilityData/gtfs-validator/issues/390

On hold until https://github.com/MobilityData/gtfs-validator/issues/482  is implemented

Per comment: https://github.com/MobilityData/gtfs-validator/issues/482#issuecomment-725721591. Will resume work on this PR.


2.535 Error InterruptibleStdioStream.cpp:61: Got EOF on stdin; closing

Hello dear zopanix/docker_factorio_server team
First of all, thank you for your great work, I successfully installed your factorio docker on my unraid server.
Everything is going great, it's also publicly available on Steam
So far so good
I always get an error in the log file
2.535 Error InterruptibleStdioStream.cpp:61: Got EOF on stdin; closing
Unfortunately, I'm a total beginner and unfortunately I can't classify the danger that this error entails.
Can it be that this mod installations are hindered
What do I have to do to get rid of this error
Thanks in advance for your efforts

https://forums.factorio.com/viewtopic.php?p=207753#p207753

Thanks for the quick reply and the information, I'm a total beginner and unfortunately I don't understand it. It would be very nice if you could briefly explain that to me.

Yes, Docker closes stdin. Since you can't read closed stdin<<
what is stdin???
what do you need it for???
is this now a problem for me as a user???
does this affect the functionality of the factorio server???
what can i do to solve the problem???

Thanks in advance for all your efforts


implement manual payout from API (#2634)

Implements request from #2634.
API action: manualpayout
Required arguments: api_key, pin

I remember why this wasn't added ... someone could easily use this system to lock-out users by supplying a wrong PIN multiple times. PINs are only required when already logged in not for any API calls. And I am hestinant to remove it completely for the sake for this API to work without the potential to break accounts.
Thoughts?

No problems

I feel obligated to mention that this should absolutely be put behind a config setting and opt-in; there are more than a few ways this can and likely will be abused.

By the way. requiring PIN prevent untrusted admins (who not have access to DB) to execute that request against id specified in request.

I think the lockout can't be removed. That would allow for easy brute-force attacks. Keep trying until the PIN works. Now the attacker has the PIN of a user. Seems not like a good idea.
In the end I don't think this is at all a good idea. It may add a benefit but it surely doesn't help in regards of security. Closing this and the opened issue.


10.0.19041.4239 printer redirection is not working

Hi
Already updated RDP ini to version from  issue 2529.
But unable to redirect printers over RDP. Only embedded (Microsoft PDF, FAX, etc.) are showing.
Please advise.

But unable to redirect printers over RDP

Solution in https://github.com/stascorp/rdpwrap/issues/504

It is not solving problem. Could you provide me steps to follow to solve the issue

Please, ask in official Telegram chat https://t.me/rdpwrap


Installing the binary

Sorry for asking such a retarded question.
Howto install the comiled binary? can I simply copy the binary or does it need any libraries?

Basically what you get as a result of building is all you need. But sometimes you will need some dynamic libraries to be copied into the same folder of executable file, so it will be portable.
So there is no "installing", but simple copy wherever you like and run this executable file as CLI.

ok thanks! thats what I did


[5.7.0] "commitOnReturn" and "rollbackOnReturn" properties are not set to pool properties

"commitOnReturn" and "rollbackOnReturn" properties are not set to pool properties when initializing the DB connection.
Therefore committing will not be happened after the query executed. This causes to WSO2 Identity Server to permanently hold the "Access Share" level locks.

Fixed


Drop support for Python 3.6

Summary
This is in keeping with the supported set of Aer and other Qiskit
components, with the exception of Terra, which has a slightly wider
band of support.  Python 3.6 was first released at the end of 2016, and
goes end-of-life at the end of 2021.

Details and comments
Fix #37.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Fwiw, aer still supports python 3.6 everything in the metapackage still does until terra 0.19.0 is released, we just reduced the level of testing for aer on 3.6 to reduce the ci load. But as dynamics is a downstream project of Qiskit and hasn't had a release yet being only >=3.7 is fine.


Skillmap: Hint is not accurate in "Planets"

Describe the bug
Skillmap: Hint is not accurate in "Planets"
Steps to reproduce the behavior
1.Navigate to https://arcade.makecode.com/skillmap
2.Planets------>START
3.Click step 7
Expect behavior
The hint should be as below:

Actual behavior
Hint is not accurate in "Planets". Last step has finished that drag get value at over the gray image in projectile from side block. So the hint should be modified.

Additional context
1.OS: Win10(rs6)

Thanks for the feedback!  We've actually removed the Planet level in the new release, since it's a third implementation of something already taught with enemies and fuel.

Thanks for the feedback!  We've actually removed the Planet level in the new release, since it's a third implementation of something already taught with enemies and fuel.


remove lint unused_doc_comment

To Reproduce
Steps to reproduce the behavior:
1. cargo make all

Describe the bug
warning: lint unused_doc_comment has been renamed to unused_doc_comments
  --> env/src/lib.rs:11:5
   |
11 |     error_chain!{}
   |     ^^^^^^^^^^^^^^
   |
   = note: #[warn(renamed_and_removed_lints)] on by default
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
  --> env/src/lib.rs:11:5
   |
11 |     error_chain!{}
   |     ^^^^^^^^^^^^^^
   |
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
  --> env/src/lib.rs:11:5
   |
11 |     error_chain!{}
   |     ^^^^^^^^^^^^^^
   |
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
  --> env/src/lib.rs:11:5
   |
11 |     error_chain!{}
   |     ^^^^^^^^^^^^^^
   |
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

   Compiling syntex_syntax v0.58.1
   Compiling env_logger v0.5.10
   Compiling ethereum-types-serialize v0.2.1
   Compiling chrono v0.4.2
   Compiling ethbloom v0.5.0
   Compiling diamond-drops-cli v0.1.0-a (file:///Users/tim.siwula/Desktop/diamond_drops/cli)
warning: lint unused_doc_comment has been renamed to unused_doc_comments
  --> cli/src/lib.rs:16:5
   |
16 |     error_chain! { }
   |     ^^^^^^^^^^^^^^^^
   |
   = note: #[warn(renamed_and_removed_lints)] on by default
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
  --> cli/src/lib.rs:16:5
   |
16 |     error_chain! { }
   |     ^^^^^^^^^^^^^^^^
   |
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
  --> cli/src/lib.rs:16:5
   |
16 |     error_chain! { }
   |     ^^^^^^^^^^^^^^^^
   |
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
  --> cli/src/lib.rs:16:5
   |
16 |     error_chain! { }
   |     ^^^^^^^^^^^^^^^^
   |
   = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
 --> cli/src/modules/mod.rs:7:5
  |
7 |     error_chain! { }
  |     ^^^^^^^^^^^^^^^^
  |
  = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
 --> cli/src/modules/mod.rs:7:5
  |
7 |     error_chain! { }
  |     ^^^^^^^^^^^^^^^^
  |
  = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
 --> cli/src/modules/mod.rs:7:5
  |
7 |     error_chain! { }
  |     ^^^^^^^^^^^^^^^^
  |
  = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
 --> cli/src/modules/mod.rs:7:5
  |
7 |     error_chain! { }
  |     ^^^^^^^^^^^^^^^^
  |
  = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

   Compiling mml v0.1.41
   Compiling diamond-drops-node v0.1.0-a (file:///Users/tim.siwula/Desktop/diamond_drops/node)
warning: lint unused_doc_comment has been renamed to unused_doc_comments
 --> node/src/modules/errors.rs:1:1
  |
1 | error_chain!{}
  | ^^^^^^^^^^^^^^
  |
  = note: #[warn(renamed_and_removed_lints)] on by default
  = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
 --> node/src/modules/errors.rs:1:1
  |
1 | error_chain!{}
  | ^^^^^^^^^^^^^^
  |
  = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
 --> node/src/modules/errors.rs:1:1
  |
1 | error_chain!{}
  | ^^^^^^^^^^^^^^
  |
  = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

warning: lint unused_doc_comment has been renamed to unused_doc_comments
 --> node/src/modules/errors.rs:1:1
  |
1 | error_chain!{}
  | ^^^^^^^^^^^^^^
........

Hmm, this looks like an issue with the error-chain crate. Will cross post this there. https://github.com/rust-lang-nursery/error-chain/issues/245

So we can add to #90 in all crates at the top of lib.rs an #[allow!(renamed_and_removed_lints)] and leave a comment with a link to this issue until a better solution is found.

Referencing https://github.com/Drops-of-Diamond/diamond_drops/pull/90#issuecomment-393713386.


ERROR OCCURED: The Web site address "/sites/bigdata/telephoneandutilities" is already in use.

Fixed.


Open to pull requests?

I will start accepting contributions after the next update (still figuring a few things out). Stick around!


[SPARK-26697][CORE] Log local & remote block sizes.

What changes were proposed in this pull request?
To help debugging failed or slow tasks, its really useful to know the
size of the blocks getting fetched.  Though that is available at the
debug level, debug logs aren't on in general -- but there is already an
info level log line that this augments a little.
How was this patch tested?
Ran very basic local-cluster mode app, looked at logs.  Example line:
INFO ShuffleBlockFetcherIterator: Getting 2 (194.0 B) non-empty blocks including 1 (97.0 B) local blocks and 1 (97.0 B) remote blocks

Full suite via jenkins.

(A few months late to the party here)
Thanks for working on this!  I'm currently debugging some FetchFailed issues and this extra verbosity is helpful 💯


Fix flaky test "should expose two endpoints on localhost"

What type of PR is this:
/kind tests
What does this PR do / why we need it:
This PR adds a random-ports flag to odo dev, that calls the port-forward library with a destination port set to zero, this way a port is automatically chosen by the system atomically.
func net.Listen(network string, address string) (net.Listener, error)
[net.Listen on pkg.go.dev]()

Listen announces on the local network address.

The network must be "tcp", "tcp4", "tcp6", "unix" or "unixpacket".
[...]
If the port in the address parameter is empty or "0", as in "<IP_ADDRESS>:" or "[::1]:0", a port number is automatically chosen.
[...]

Which issue(s) this PR fixes:

Fixes #5603
PR acceptance criteria:

[ ] Unit test

[ ] Integration test

[ ] Documentation

How to test changes / Special notes to the reviewer:

IBM tests passed 6x in a row

Nice way of fixing the issue 👍🏿 I saw that this test in tests/interactive/cmd_dev_test.go was not updated to use the new random-ports flag: should run alizer to download devfile successfully even with -v flag
Is that on purpose?

No, good catch. I've added it

@rm3l I force pushed the commit to rerun the tests, as the OpenShift platform were not stable. Feel free to lgtm again :)

@rm3l I force pushed the commit to rerun the tests, as the OpenShift platform were not stable. Feel free to lgtm again :)

/lgtm

/lgtm from test perspective

/lgtm
4ab204d was a minor change.


Update pillow>=10.0

Codecov Report
Patch and project coverage have no change.

Comparison is base (f99b5fb) 100.00% compared to head (fd6b918) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #320   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          321       321
  Lines        10032     10032
  Branches       967       967
=========================================
  Hits         10032     10032

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


SkeletonIK3D "play IK" doesn't stay in played state when selecting other nodes

Godot version
4.1-beta2_mono_win64
System information
Windows 11
Issue description
I expect that I can play an IK and move the target around to see how the bones behave.
However when I click the button "play IK" when SkeletonIK3D is selected, and then click on the target to move it, the IK doesn't play anymore.
I'm not sure if this is the normal behavior or not. But I saw in videos that in 4.0 when Skeleton node was in charge of IKs it'd work in real time.
Steps to reproduce
N/A
Minimal reproduction project
N/A

Looks like a duplicate of https://github.com/godotengine/godot/issues/72945

Indeed, my apologies. Worst part is I searched and found that thread but saw 4.0-rc1 and thought it was too early for SkeletonIK3D to be implemented.

SkeletonIK3D "play IK" doesn't stay in played state when selecting other nodes,


minor miss spell on readme

Hello my friend
I found a minor miss spell on README.md
https://github.com/ximtech/jasypt-encrypt-plugin/blob/b02908bba5d387f26b52f8c0321b80e5205c5336/README.md?plain=1#L42
This is supposed to be
apply plugin: io.github.jasypt.encrypt.JasyptPlugin

thank you for nice and neat plugin, this saves my hours of work.

Fixed. Thank you!


[red-knot] Track root cause of why a type is inferred as Unknown

Summary
This PR adds detailed information to our type inference so we can track exactly why a symbol has been inferred as Unknown. This allows us to restore the unresolved-import red-knot lint to the level of accuracy it had prior to https://github.com/astral-sh/ruff/commit/a9847af6e89c593dcb49023b5e88ba7f4a84a61a, because we can now distinguish between Unknown types that were caused by unresolved imports and other kinds of Unknown types. The approach is similar to the one mypy uses.
Test Plan
There are three ways in which this PR is tested:

The assertion in the benchmark is changed: six spurious "Unresolved import" diagnostics go away, meaning the number of diagnostics drops from 34 to 28. The only remaining "unresolved import" diagnostic is emitted on this line, which is because we don't understand * imports yet, and Iterable is defined in the typeshed stub for collections.abc here.
A test is added to red_knot_python_semantic/src/types/infer.rs asserting that from imports with invalid syntax result in Unknown types.
A test is added to red_knot_workspace/src/lint.rs asserting that a project structure (where the foo module does not exist) like this only triggers an "unresolved import" diagnostic in a.py, and not in b.py:

/src/a.py: import foo as foo
/src/b.py: from a import foo

How does this new type work when unifying or intersecting types? Do we keep all different variants?

Good question. Currently yes, you could end up with a union such as int | Unknown(UnknownTypeKind::UnresolvedImport) | Unknown(UnknownTypeKind::TypeError).
I suppose we should flatten them into a single Unknown member. But then the question becomes: what kind of Unknown should it be? Maybe UnknownTypeKind::SecondOrder, since it results from the union of two Unknown elements?

I would love to wait with this PR to get @carljm opinion. I feel uncertain about the type's definition because there are no "obvious" definitions for unification and intersection (unless we make it a bit set, at least for unification).
It's further unclear if we still need to distinguish between the two types, now that the check for unresolved imports moves into the type checker.
I had a quick look at pyright and from what i understand is that it uses Unknown for unresolved imports but it only has a single Unknown type.
https://github.com/microsoft/pyright/blob/52a47010b9db2ad6801b4b35d987cb9f4c923c18/packages/pyright-internal/src/analyzer/typeEvaluator.ts#L18629-L18676

I would love to wait with this PR to get @carljm opinion. I feel uncertain about the type's definition because there are no "obvious" definitions for unification and intersection

Agreed, I'm definitely not going to merge until we've heard Carl's thoughts here! There's no rush on this.

I feel uncertain about the type's definition because there are no "obvious" definitions for unification and intersection (unless we make it a bit set, at least for unification).

FWIW, I think simplifying unions is inevitably going to become more complex than what we currently have, whether we go with this PR or not, because of the fact that we will want to simplify Literal[True] | Literal[False] to Instance(builtins.bool), and similarly for other sealed types such as enums.

It's further unclear if we still need to distinguish between the two types, now that the check for unresolved imports moves into the type checker.

Hmm, yeah, not sure. I'll try to pull out some of the improvements here into a separate PR that doesn't introduce the new UnknownTypeKind enum, so that we can evaluate in isolation exactly whether it improves anything for us right now.

I'm open to the idea that we may need to do this eventually, but there are complexity and efficiency disadvantages to smuggling additional context through the type system this way, so I'd rather not do it until it's really clear exactly why we need it. And I don't think that's currently clear, given that the issue with the unresolved-imports check in main branch that this PR fixes is also easily fixable with a much smaller change: https://github.com/astral-sh/ruff/pull/13007
I don't think we should ever need this for the sake of deciding whether or not to emit a diagnostic. Unknown may result from a type error, but I don't think it's existence should ever be a type error.
I would be interested in knowing more about precisely how mypy uses this extra information about the origin of Any.

I don't think we should ever need this for the sake of deciding whether or not to emit a diagnostic. Unknown may result from a type error, but I don't think its existence should ever create a type error. The fact that main branch currently treats an import of any Unknown typed value as an error is IMO not correct, and is fixed by the change linked above.

Thanks, I think this is correct; treating Unknown as a type error goes against the spirit of gradual typing. We need to catch the error before we transform the Unbound into Unknown. My mistake.

I still think there's a good chance that we'll need something like this eventually, but I agree that with the fixes in #13055, there are few immediate benefits to this right now. Thanks both!

Much of it seems to be used for precise diagnostics when strict mode is enabled.

Yeah, that makes sense. I agree, we'll probably need something like this for the same reason, when we want to have an Any-forbidding strict mode and emit useful diagnostics for it.


Refactor get_key

I had this diff laying around, finally took the time to split it up into several
commits. Thoughts and feedback are much appreciated.

Hey @mptre, nice work! To me, the code reads better this way. Looks good to merge!


generate prompt on the server

Don´t generate the prompt on the client as this can lead to people exploiting your API with unwanted prompts.

Yes, I also wanted to mention this.

I find, by the fact that this is a showcase example, that has gotten a lot of attention and is being forked/cloned for personal projects by many people learning Next.js, this security issue has to be fixed.

I find, by the fact that this is a showcase example, that has gotten a lot of attention and is being forked/cloned for personal projects by many people learning Next.js, this security issue has to be fixed.

Yes. But I also think they put a token limit in their code which is a 200 limit... so i don't think it's terrible but I personally consider it a security flaw because it's very loose.
Even if they pass the boilerplate input of chatGPT in the back-end, the user could still by-pass it like sql injection haha.
like, if the chatGPT input right now is: "Generate a twitter bio that is short bluh bluh bluh based on this bio:
$userBio".
User can say: "Full-Stack Web Developer". And also calculate this complex math formula for me [or whatever thing the bad user wants to do with the chatGPT]

Though generally you want to make it harder for the hacker but whatever.


Multi package workers

Pull Request Test Coverage Report for Build 667804516

7 of 9 (77.78%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.3%) to 78.986%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/react-api/src/hooks/useViewportFeatures.js
0
2
0.0%

Totals

Change from base Build 667601916:
-0.3%

Covered Lines:
569

Relevant Lines:
685

💛  - Coveralls


[Icon]  Peertube

What service is this for?
federated video social network
What are their domain names?
peertube.tv
peertube.social
diode.zone
tilvids.com
Do you have a link to a SVG of their logo?
https://simpleicons.org/icons/peertube.svg

Added, thanks!


fix(#2162): accordion padding for right and left icon position

Before (the change)
Accordion padding is not correct:

The correct one should be like this:

After (the change)
The padding is fixed, the padding when icon position is right, also being fixed. This PR is to upgrade the version of our package @abgov/design-tokens
Make sure that you've checked the boxes below before you submit the PR

[x] I have read and followed the setup steps
[ ] I have created necessary unit tests
[x] I have tested the functionality in both React and Angular.

Steps needed to test

:tada: This PR is included in version 1.17.0-alpha.119 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 5.0.0-alpha.12 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.0.0-alpha.9 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Question] How to make full page screenshot?

Nothing native in the lib to offer that atm, but it's a nice feature to have..  Let me have a play around.


Upgrade to Payload 2.11.2

Test are passing and it seems to work. I'm not a nodejs expert ...
Maybe you would want it to use an earlier version of PayloadCMS 2.x.x ?

I inserted the content of the dist/ folder into an payload instance I'm configuring (2.11.2) and it's working.

Does not seem to play well with nested docs plugin. There is a validation issue. The error goes away when I disable this plugin ...
[15:10:57] ERROR (payload): ValidationError: The following field is invalid: parent     at beforeChange (/Users/olivier/Documents/src/payload-test/logica-cms-2/node_modules/payload/src/fields/hooks/beforeChange/index.ts:60:11)     at processTicksAndRejections (node:internal/process/task_queues:95:5)     at async updateByID (/Users/olivier/Documents/src/payload-test/logica-cms-2/node_modules/payload/src/collections/operations/updateByID.ts:234:18)     at async updateByIDHandler (/Users/olivier/Documents/src/payload-test/logica-cms-2/node_modules/payload/src/collections/requestHandlers/updateByID.ts:36:17)

Does not work with a relationship inside a row inside an array

I also noticed that a nested query (to filter access to a document) didn't work when the foreign key was an ObjectId instead of a string ...
{ 'place.within.id': { equals: '65a6724b7...' } }


TypeScript Library - Surface Tint + Elevations

It seems that the typescript library doesn't account for the md.sys.color.surface-tint-color token which should default to the primary color.
In addition, is there a POV on how elevations should be handled?
I think at present it would require manually compositing the surface color + primary color (possibly to be replaced the aforementioned surface tint color) with opacity at a given elevation per the specification.  Implemented as a custom color today?
Is there an example of how to use HCT to accomplish this to get the tonal variations for the elevations?
Thank you in advance!  The library and concepts are awesome!

Checking the flutter source, led me to: https://api.flutter.dev/flutter/dart-ui/Color/alphaBlend.html as the actual mechanism for tinting, and the specifics of which color and opacity seem to be covered in the Material design guidelines

To answer the elevation question, we're moving away from blending a base color + a surface tint color to fully providing roles for surface colors (e.g. surface-2, surface-1, surface, surface+1, etc.). That'll be coming this year.

surface-tint color is removed in favor of surface-tint

@wojtek-viirtue I'm figuring you've probably got a solution worked out by now, but here's my function for generating tailwind classes for the surface elevation tints until the official implementation is released. Not sure if it's 100% accurate, but it looks reasonably well in my project. You'd probably want to remove some stuff if you're not using tailwind in your project, but hope it helps!
const mapSurfaceTints = (
  surfaceColor: number,
  primaryColor: number,
  schemeName: string
) => {
  const tints = [0.05, 0.08, 0.11, 0.12, 0.14];

  return tints.reduce((colors, tint, index) => {
    colors[`surface-${index + 1}-${schemeName}`] = hexFromArgb(
      Blend.cam16Ucs(surfaceColor, primaryColor, tint)
    );

    return colors;
  }, {} as { [key: string]: string });
};

use:
mapSurfaceTints(
  theme.schemes.light.surface,
  theme.schemes.light.primary,
  "light"
)

output:
{
  'surface-1-light': '#eff4ec',
  'surface-2-light': '#e8efe5',
  'surface-3-light': '#e1e9df',
  'surface-4-light': '#dfe8dd',
  'surface-5-light': '#dae4d9'
}

Just want to call out surfaces are about to change. This will be reflected in the library soon.
The material theme builder figma plugin just updated to show the new roles (it uses material color utilities internally)

@pennzht I think this can be closed, yes?

@guidezpl Sorry but so is this available in the Typescript library already? I can't find anywhere in the implementation.

https://github.com/material-foundation/material-color-utilities/blob/main/typescript/dynamiccolor/material_dynamic_colors.ts#L145-L236 are all the explicit surface colors per the M3 guidelines.

I see. My issue was that they're missing from the Scheme returned by themeFromSourceColor/themeFromImage.
Seems this is only available on dynamic color schemes. I don't think this should necessarily be the case?

Agreed yeah, those theme functions should be updated

So it's probably not on the roadmap yet to update them right? If anyone wants to use the correct surface colors they should use dynamic colors for now

But where's the surface-container-highest and something others? They're not included in the TS library (at least not the release).

But where's the surface-container-highest and something others? They're not included in the TS library (at least not the release).

They are in the dynamic schemes part only. You can create them with for example, SchemeTonalSpot, SchemeNeutral, etc...
Something like this:
import {
  argbFromHex,
  hexFromArgb,
  Hct,
  SchemeContent,
  MaterialDynamicColors,
} from "@material/material-color-utilities";

const mainColor = "#3f51b5";

const isDark = false;
const contrastLevel = 0.3;
const argb = argbFromHex(mainColor);
const source = Hct.fromInt(argb);
const dynamicScheme = new SchemeContent(source, isDark, contrastLevel);

const surfaceContainerHighest = hexFromArgb(MaterialDynamicColors["surfaceContainerHighest"].getArgb(dynamicScheme));

But where's the surface-container-highest and something others? They're not included in the TS library (at least not the release).

They are there, as @gpkc said, but using anything that calls the Scheme class won't return an object with them (i.e. themeFromImage(), themeFromSourceColor(), etc).  Admittedly I'm new to Typescript, so please forgive any unnecessary work I'm about to suggest.  Also, if there's a better way, I'm all ears!
If you add a couple blocks of code to two files here, you can get these to deliver in the Scheme object.
scheme.js
First up is adding these to the bottom of the getters for the Scheme class:
    get surfaceDim() {
        return this.props.surfaceDim;
    }
    get surfaceBright() {
        return this.props.surfaceBright;
    }
    get surfaceContainerLowest() {
        return this.props.surfaceContainerLowest;
    }
    get surfaceContainerLow() {
        return this.props.surfaceContainerLow;
    }
    get surfaceContainer() {
        return this.props.surfaceContainer;
    }
    get surfaceContainerHigh() {
        return this.props.surfaceContainerHigh;
    }
    get surfaceContainerHighest() {
        return this.props.surfaceContainerHighest;
    }
    get surfaceTint() {
        return this.props.surfaceTint;
    }
    get primaryFixed() {
        return this.props.primaryFixed;
    }
    get primaryFixedDim() {
        return this.props.primaryFixedDim;
    }
    get onPrimaryFixed() {
        return this.props.onPrimaryFixed;
    }
    get onPrimaryFixedVariant() {
        return this.props.onPrimaryFixedVariant;
    }
    get secondaryFixed() {
        return this.props.secondaryFixed;
    }
    get secondaryFixedDim() {
        return this.props.secondaryFixedDim;
    }
    get onSecondaryFixed() {
        return this.props.onSecondaryFixed;
    }
    get onSecondaryFixedVariant() {
        return this.props.onSecondaryFixedVariant;
    }
    get tertiaryFixed() {
        return this.props.tertiaryFixed;
    }
    get tertiaryFixedDim() {
        return this.props.tertiaryFixedDim;
    }
    get onTertiaryFixed() {
        return this.props.onTertiaryFixed;
    }
    get onTertiaryFixedVariant() {
        return this.props.onTertiaryFixedVariant;
    }

Next, adding this to lightFromCorePalette:
            surfaceDim: core.n1.tone(87),
            surfaceBright: core.n1.tone(98),
            surfaceContainerLowest: core.n1.tone(100),
            surfaceContainerLow: core.n1.tone(96),
            surfaceContainer: core.n1.tone(94),
            surfaceContainerHigh: core.n1.tone(92),
            surfaceContainerHighest: core.n1.tone(90),
            surfaceTint: core.a1.tone(40),
            primaryFixed: core.a1.tone(90),
            primaryFixedDim: core.a1.tone(80),
            onPrimaryFixed: core.a1.tone(10),
            onPrimaryFixedVariant: core.a1.tone(30),
            secondaryFixed: core.a2.tone(90),
            secondaryFixedDim: core.a2.tone(80),
            onSecondaryFixed: core.a2.tone(10),
            onSecondaryFixedVariant: core.a2.tone(30),
            tertiaryFixed: core.a3.tone(90),
            tertiaryFixedDim: core.a3.tone(80),
            onTertiaryFixed: core.a3.tone(10),
            onTertiaryFixedVariant: core.a3.tone(30)

Last up for this file is adding this to the darkFromCorePalette:
            surfaceDim: core.n1.tone(6),
            surfaceBright: core.n1.tone(24),
            surfaceContainerLowest: core.n1.tone(4),
            surfaceContainerLow: core.n1.tone(10),
            surfaceContainer: core.n1.tone(12),
            surfaceContainerHigh: core.n1.tone(17),
            surfaceContainerHighest: core.n1.tone(22),
            surfaceTint: core.a1.tone(80),
            primaryFixed: core.a1.tone(90),
            primaryFixedDim: core.a1.tone(80),
            onPrimaryFixed: core.a1.tone(10),
            onPrimaryFixedVariant: core.a1.tone(30),
            secondaryFixed: core.a2.tone(90),
            secondaryFixedDim: core.a2.tone(80),
            onSecondaryFixed: core.a2.tone(10),
            onSecondaryFixedVariant: core.a2.tone(30),
            tertiaryFixed: core.a3.tone(90),
            tertiaryFixedDim: core.a3.tone(80),
            onTertiaryFixed: core.a3.tone(10),
            onTertiaryFixedVariant: core.a3.tone(30)

scheme.d.ts
Add this to the Scheme class:
    get surfaceDim(): number;
    get surfaceBright(): number;
    get surfaceContainerLowest(): number;
    get surfaceContainerLow(): number;
    get surfaceContainer(): number;
    get surfaceContainerHigh(): number;
    get surfaceContainerHighest(): number;
    get surfaceTint(): number;
    get primaryFixed(): number;
    get primaryFixedDim(): number;
    get onPrimaryFixed(): number;
    get onPrimaryFixedVariant(): number;
    get secondaryFixed(): number;
    get secondaryFixedDim(): number;
    get onSecondaryFixed(): number;
    get onSecondaryFixedVariant(): number;
    get tertiaryFixed(): number;
    get tertiaryFixedDim(): number;
    get onTertiaryFixed(): number;
    get onTertiaryFixedVariant(): number;

Lastly, add this to darkFromCorePalette:
        surfaceDim: number;
        surfaceBright: number;
        surfaceContainerLowest: number;
        surfaceContainerLow: number;
        surfaceContainer: number;
        surfaceContainerHigh: number;
        surfaceContainerHighest: number;
        surfaceTint: number;
        primaryFixed: number;
        primaryFixedDim: number;
        onPrimaryFixed: number;
        onPrimaryFixedVariant: number;
        secondaryFixed: number;
        secondaryFixedDim: number;
        onSecondaryFixed: number;
        onSecondaryFixedVariant: number;
        tertiaryFixed: number;
        tertiaryFixedDim: number;
        onTertiaryFixed: number;
        onTertiaryFixedVariant: number;

Now the Theme Utilities will pull a Scheme object that includes all of the Material Palette (at least the ones listed on m3.material.io).
Bonus Round
While futzing with this, I noticed the values for lightFromCorePalette's background and surface and darkFromCorePalette's background, surface, and onErrorContainer are off in scheme.js, so I corrected them for my build, but wanted to leave them here in case it's helpful.  Again, using m3.material.io for reference.  If the differences are intentional please let me know.
NOTE: These blocks also have been reordered with the new additions to group things the way it was originally.

I see that now.  The issue I'm having there is that I can't get it to generate the same color palette.  I used @gpkc code above, and it results in a much more muted palette vs the Theme Utils.  That's why I went the Scheme route for now.  I'm gonna need to circle back to that before going live.

I see that now. The issue I'm having there is that I can't get it to generate the same color palette. I used @gpkc code above, and it results in a much more muted palette vs the Theme Utils. That's why I went the Scheme route for now. I'm gonna need to circle back to that before going live.

Have you tried all of the possible schemes? SchemeTonalSpot, SchemeVibrant, SchemeExpressive etc


Fixes #1888

Fixes #1888, Adding a ref will allow you to access the checkbox through the header component.

Can't we use some properties to acheive the same goal?
(https://facebook.github.io/react/docs/more-about-refs.html)

Refs are a great way to send a message to a particular child instance in a way that would be inconvenient to do via streaming Reactive props and state

@penkar I'm closing this PR. I don't think that we should encourage people to use imperative API by adding ref.


feat: users/guimatheus92/v0.5.0

I have added a couple of features and improved the documentation.
What I have added:

Plugin will not open until user has opened a project on SH3D, that way we can prevent errors and streamlining the user workflow:

User can now choose betwen HIGH and LOW quality before exporting his images:

TheTitle key-value from .yaml file can now be filled by user in SH3D in the description field in user project. That way, everytime a new file is generated, the data will be there saved in his project:

SH3D:

YAML:
  - type: state-icon
    entity: switch.kitchen_4
    title: Light Kitchen
    style:
      top: 70.37%
      left: 65.07%
      border-radius: 50%
      text-align: center
      background-color: rgba(255, 255, 255, 0.3)
    tap_action:
      action: toggle

Since I am using Windows, the Makefile didn't work for me. So I created a PowerShell file following the same logic (great solution btw) that do the same work.

For Windows only: I wasn't able to download the SweetHome3D .jar file using this method, so I have commented that line. For now, I suggest to download manually and place under a folder called dl

@shmuelzon I don't if is possible to Pull Request my tag and my release as well, I wasn't able to do that. Or, if I should drag the file in here manually.

Thank you for the pull request!
Would it be possible to split each feature/change to a separate pull request?
That way it'll show up properly in the change log.
Thanks!

Thank you for the pull request!
Would it be possible to split each feature/change to a separate pull request?
That way it'll show up properly in the change log.
Thanks!

Sure, I will take some time do undo all I did and create a PR for each but I will do. There a couple of comments there that I don't know how to solve, so I might open an issue to ask help/ideas so I can implement.


Reader: shuffle inside every row group

Allow shuffle inside every single row group in reader.
Also use a shuffle seed to generate reproducible shuffle results across: single row shuffle, row groups shuffle in ventilator and sharding.

Attach some benchmark result using synthetic dataset with PyTorch:

Experiment setup: BatchedDataLoader + make_batch_reader(), batch_size=50000, shuffle_buffer_size=1000000, thread_pool, 10 workers.
Datasets from 100M rows to 1.6B rows are tested.
Compare throughput of shuffle in dataloader and shuffle in reader .

Using shuffle in reader is expected to generate higher throughput since multiple workers are shuffling in parallel.
fyi @selitvin


your private key (usually a .pem file) is not correct

Bug Report
Current Behavior
as I want to do things independently from the context. from what I read I thought this should work:
module.exports = (robot: Application) => {
const server = robot.route();
server.get(
    "/:installationId",
    async (req, res) => {
      const octokit = await robot.auth((req as any).params.installationId);
      const appInfo = octokit.apps.getAuthenticated();
      res.json(appInfo);
    }
  );
}

instead I get:
22:29:49.492Z ERROR probot: Your private key (usually a .pem file) is not correct. Go to https://github.com/settings/apps/YOUR_APP and generate a new PEM file. If you're deploying to Now, visit https://probot.github.io/docs/deployment/#now.
  HttpError: A JSON web token could not be decoded

i initialized using create-probot-app and my private key got automatically inlined into the .env
robot.on() seems to work flawlessly.

Does the issue persist, when you download a new .pem file from https://github.com/settings/apps/<YOUR_APP> and replace the old one in /secrets?

Couldn't tell. I moved away from probot, but will come back when the octokit upgrades are done to give it another spin.