Please improve the writing style of Where clause

var q = new SelectQuery();
var table_a = q.From("table_a");
q.Select(table_a, "*");
q.WhereAnd(table_a, "id", ":id", 1);

Since the Where clause and the And conjunction are integrated, when we extend the function in the future, all method names will be prefixed with Where.

Integrate with #38 and proceed.


Investigate summerwind/actions-runner

The runner images are all manually constructed images. summerwind/actions-runner about as close to an official runner image as exists.

I don't think we will be able to use the image itself, especially if it's under a non-official owner like summerwind. But it did teach me about hooks which may come useful one day.
The exit hook would be nice if it had access to the job result so we can get rid of the log grepping hack.
We might also be able to simplify the idle reaper by giving it the runner id and actual startup time directly from .runner. That said, I don't want to give the runner context permissions to do that as it might get abused by untrusted jobs.
https://github.com/actions/actions-runner-controller/blob/8afef51c8bb4558746eb36fc3f0ad9fd921d0b13/runner/startup.sh#L123-L132


Stipulated Period??

The note mentions "AD FS would start deleting device objects from on-premises directory after a stipulated period". Could we just have the period defined right here? I haven't been able to determine how long we wait to be sure objects don't get deleted because of this ambiguous language.

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

ID: 2928e23e-3210-9e74-9cdb-1a19b703eac7
Version Independent ID: 44e303ca-e4bc-ba30-5aae-311aa9318278
Content: Controlled validation of hybrid Azure AD join - Azure AD
Content Source: articles/active-directory/devices/hybrid-azuread-join-control.md
Service: active-directory
Sub-service: devices
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@IntrepidBlazon Thanks for your feedback! We will investigate and update as appropriate.

hey @IntrepidBlazon we're looking into this issue and will try adding it if possible.
@IntrepidBlazon Please let us know if there are anymore questions within the scope of this git issue. If not, I will be closing out this git issue by end of day tomorrow. Please file a new git issue with a reference to this one if you have anymore concerns. Thanks

Hello @IntrepidBlazon
I will be adding the below information to clarify on what the stipulated period is. Please let me know if this answers your question,
ADFS will then start deleting device objects from on-premises directory after the stipulated period defined in the ADFS Device Registration's attribute "MaximumInactiveDays". ADFS Device Registration objects can be found using the powershell cmdlet here.

Thanks for the clarification!


Remove feature-flag code/checks for new org notifications functionality

That means, we should:

[ ] Remove the feature flag checker in order to show/hide the notifications panel.
[ ] Remove the feature flag (don't forget to remove it from production and staging).

@noguerol and @saleiva, when you decide.

IMO, we should open this right now.
El lun., 10 abr. 2017 a las 10:55, Javier Álvarez Medina (<
<EMAIL_ADDRESS>escribió:

@noguerol https://github.com/noguerol and @saleiva
https://github.com/saleiva, when you decide.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CartoDB/cartodb/issues/11947#issuecomment-292889286,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIENUZqPip6KQvyIW6u-OgvdpfYvsLYks5rue6QgaJpZM4M4frJ
.

Ey, you can open it to everybody just unchecking the "restricted" flag at superadmin. The tasks at this issue are just for code cleanup.

It is already opened yep, we want to remove the code, yes.

Changed title, sorry for the mixed up.

Although this is ready, I am holding because I found a couple of UI bugs during acceptance that I think should be fixed before opening this to the public: https://github.com/CartoDB/cartodb/issues/11957

Added in the TODO column due to the fact that it belongs to a current milestone.


Add warnings regarding the change of default value from <IP_ADDRESS> to <IP_ADDRESS> in installers

Description:
Add warnings regarding the change of default value from <IP_ADDRESS> to <IP_ADDRESS> in installers.
This logs a message when the value of the listen interface is set to <IP_ADDRESS> during installation, on Linux and Windows, in preparation of incoming changes to installer default values.

Maybe these messages should be moved to the end of the scripts, so that it is more noticeable and doesn't get lost in the output from the installation?

The messaging LGTM, thanks @atoulme! Would this apply to other deployment approaches (Ansible, Puppet,..) for the same warnings to be relayed or only the installer script?

The messaging LGTM, thanks @atoulme! Would this apply to other deployment approaches (Ansible, Puppet,..) for the same warnings to be relayed or only the installer script?

The other deployments methods (ansible, chef, etc) do not use these scripts.

For now, I have circumscribed the changes to default networking values to our installers and Chocolatey because they characterize VM installations and are primary target for our zero-config approach. We can expand to other installation methods next.


Update jira extension

Description
Custom Fields that are required didn't showed up as required in the extension,
From the issue report:

Some fields are recognized as mandatory, yet others are not. I investigate a little further and looks like the elements are not being mark as mandatory are the custom fields.

closes #12154
Screencast
Before

Now

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[ ] I checked that files in the assets folder are used by the extension itself
[ ] I checked that assets used by the README are placed outside of the metadata folder

Awesome 🚀


cainjector not creating/updating Secrets after root CA rotation

Describe the bug:
We observed a root CA certificate rotation in our AWS EKS cluster on January 3
"cert-manager/webhook: Root CA certificate is nearing expiry. Regenerating..."
"cert-manager/webhook: Detected root CA rotation - regenerating serving certificates"
"cert-manager/webhook: Updated cert-manager webhook TLS certificate" DNSNames=["cert-manager-webhook","cert-manager-webhook.cert-manager","cert-manager-webhook.cert-manager.svc"]
"cert-manager: Updated object" kind="validatingwebhookconfiguration" kind="validatingwebhookconfiguration" name="cert-manager-webhook"
"cert-manager: Updated object" kind="mutatingwebhookconfiguration" kind="mutatingwebhookconfiguration" name="cert-manager-webhook"

It seems to have "succeeded" in the sense that we have a new CA certificate:
$ kubectl -n cert-manager get secrets cert-manager-webhook-ca -o yaml \
| grep ca.crt | cut -d ":" -f2 \
| base64 -d \
| openssl x509 -noout -text

Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            <serial>
        Signature Algorithm: ecdsa-with-SHA384
        Issuer: CN=cert-manager-webhook-ca
        Validity
            Not Before: Jan 10 20:06:07 2024 GMT
            Not After : Jan  9 20:06:07 2025 GMT
        Subject: CN=cert-manager-webhook-ca
        Subject Public Key Info:
            Public Key Algorithm: id-ecPublicKey
                Public-Key: (384 bit)
                pub:
                    <pub>
                ASN1 OID: secp384r1
                NIST CURVE: P-384
        X509v3 extensions:
            X509v3 Key Usage: critical
                Digital Signature, Key Encipherment, Certificate Sign
            X509v3 Basic Constraints: critical
                CA:TRUE
            X509v3 Subject Key Identifier:
                <id>
    Signature Algorithm: ecdsa-with-SHA384
    Signature Value:
         <value>

However, we are seeing unexpected issues with the CA cert and related Secrets:

the CA cert has Common Name cert-manager-webhook-ca and no Key, Organization, or Issuer:

Common Name: cert-manager-webhook-ca
Subject Alternative Names:
Organization:
Organization Unit:
Locality:
State:
Country:
Valid From: January 10, 2024
Valid To: January 9, 2025
Serial Number: <serial>

Compare to our other environments with Common Name cert-manager.webhook.ca and expected 2048 bit Key, Organization and Issuer:
Common Name: cert-manager.webhook.ca
Subject Alternative Names:
Organization: cert-manager.system
Organization Unit:
Locality:
State:
Country:
Valid From: February 20, 2020
Valid To: February 18, 2025
Issuer: cert-manager.webhook.ca, cert-manager.system
Key Size: 2048 bit
Serial Number: <serial>

the cert-manager-webhook-tls Secret does not exist:

$ kubectl -n cert-manager get secrets | grep cert-manager-

cert-manager-cainjector-token-886rw            kubernetes.io/service-account-token   3      250d
cert-manager-token-2sfjx                       kubernetes.io/service-account-token   3      250d
cert-manager-webhook-ca                        Opaque                                3      90m
cert-manager-webhook-token-jxvx9               kubernetes.io/service-account-token   3      250d

the cert-manager-webhook-ca Secret is of type Opaque (expected kubernetes.io/tls)

$ kubectl -n cert-manager get secrets cert-manager-webhook-ca -o yaml

apiVersion: v1
data:
  ca.crt: <crt>
  tls.crt: <crt>
  tls.key: <key>
kind: Secret
metadata:
  annotations:
    cert-manager.io/allow-direct-injection: "true"
  creationTimestamp: "2024-01-10T20:06:07Z"
  name: cert-manager-webhook-ca
  namespace: cert-manager
  resourceVersion: "2642252831"
  uid: 4ec86c2f-3e41-49e9-9b38-dc25b42abaaa
type: Opaque

We are injecting CA data via Secret resource using this secret everywhere:
cert-manager.io/inject-ca-from-secret: cert-manager/cert-manager-webhook-ca

Impact
Since January 3, we've observed multiple cert and TLS-related errors:

AWS EKS control plane nodes unable to communicate with cert-manager:

http: TLS handshake error from <IP_ADDRESS>:37890: remote error: tls: bad certificate

The API server is unable to post to the certificates.cert-manager.io CustomResourceDefinition:

Post "[https://cert-manager-webhook.cert-manager.svc:443/convert?timeout=30s](https://cert-manager-webhook.cert-manager.svc/convert?timeout=30s)": tls: failed to verify certificate: x509: certificate signed by unknown authority (possibly because of "x509: ECDSA verification failure" while trying to verify candidate authority certificate "cert-manager-webhook-ca")

Expected behaviour:

The new CA certificate includes a key
The cert-manager-webhook-tls Secret is created by cainjector
The cert-manager-webhook-ca Secret is of type kubernetes.io/tls
The EKS control plane and API server are able to communicate successfully with cert-manager

Steps to reproduce the bug:
Unfortunately, we're not sure. Fortunately this issue is occurring in our pre-production cluster, but we haven't been able to reproduce anywhere else.
Anything else we need to know?:
We've tried deleting the webhooks, webhook deployment, and secret and re-deployed the helm chart, with no luck.
Environment details::

Kubernetes version: 1.25.16-eks-8cb36c9
Cloud-provider/provisioner: AWS EKS
cert-manager version: 1.12.3
Install method: helm template + helm upgrade
Issuer: letsencrypt-prod

/kind bug

We are experiencing this same issue across 4 clusters.
Kubernetes version: 1.29.0
Cloud-provider/provisioner: AKS (Azure)
cert-manager version: 1.14.4
Install method: Helm via Argo
Issuer: letsencrypt-prod
Note: We first experienced this issue on cert-manager 1.12.2, but we are currently using version 1.14.4. We were unable to fix this issue in the impacted clusters on either version.


Move 'forceLowerCase' to options - fixes #12

Addresses my issue regarding case sensitivity. This would simply add the flag to the options, defaulting to case-sensitive, which I would feel to be the most sensible value. If you disagree I'd be more than happy to change it back to default-lowercase if it meant getting this PR through. I plan to use this project quite heavily in a CLI for Buttercup.pw.

Nice, looks good to me 💯


format code

Pull Request Test Coverage Report for Build 3076
Details

19 of 20 (95.0%)  changed or added relevant lines in 6 files are covered.
26 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-0.6%) to 83.209%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

builtin/json.mbt
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

immut/sorted_map/map.mbt
2
83.05%

immut/array/tree.mbt
3
76.0%

builtin/bigint.mbt
6
87.71%

builtin/byte.mbt
15
36.67%

Totals

Change from base Build 3075:
-0.6%

Covered Lines:
3915

Relevant Lines:
4705

💛  - Coveralls


Cross Site Scripting vulnerability due to ${request.params.url} not being sanitized

https://github.com/GoogleChrome/rendertron/blob/8d70628c96ae72eff6eebb451d26fc9ed6b58b0e/src/main.js#L103
and
https://github.com/GoogleChrome/rendertron/blob/8d70628c96ae72eff6eebb451d26fc9ed6b58b0e/src/main.js#L127
PoC: https://render-tron.appspot.com/screenshot/<h1>xss%20here<%2Fh1>%3Fwidth%3D2335%26height%3D1297

Thanks for the report! This has been fixed now.

@samuelli Can you link to the fixing commit? Thanks!

#88 fixed this.


Update permissions endpoint to add support for returning permissions for all scope types for a given endpoint

Currently, when requesting for permissions, the client has to provide a value for the scopeType in the query parameter. If none is provided, the default DelegatedWork is provided. This means it is currently not possible for a client to retrieve all the scope types (DelegatedPersonal, DelegatedWork, Application) in one call.
https://github.com/microsoftgraph/microsoft-graph-devx-api/blob/fa0aca54e933b54f68f0259d26065e3974540fef/GraphWebApi/Controllers/PermissionsController.cs#L42-L46
We need to update the query parameter to not have a default value and add support for clients requiring retrieval of all the scope types for a given endpoint.

Related to #1337


Return the traced command's status, not 0

Replaces #281
Returns the exit status from the original command, not always 0. The trace and testrun commands now use 125 for an internal error.

@remram44 - thank you for this PR! definitely more complete than my patch.

@kaczmarj: I don't know if this is relevant to you, since this might be outside the scope of what neurodocker uses, but there is the same issue with reproduction: status 0 is returned if reprounzip succeeded, no matter what the experiment itself returned (status from the experiment is only printed out).


Fully automatic parallelization of entire JAX programs

In another issue, I wrote the following:

I dream of a compiler that is powerful enough to let users focus solely on the semantics of a program (what is to be computed), while the compiler figures out how to distribute the computation efficiently over a set of available resources (how it is to be computed). So no more pmap, xmap, shmap, pjit, pmean, etc. Just write your program as if it ran on a single device (i.e., specify its semantics), and let the compiler figure out the rest. As the shmap page says: Compiler, take the wheel!

Later, I came across a project that seeks to do just that:
Alpa: Automating Inter- and Intra-Operator Parallelism for Distributed Deep Learning (repo):

Alpa is built on top of a tensor computation framework Jax. Alpa can automatically parallelize jax functions and runs them on a distributed cluster. Alpa analyses the computational graph and generates a distributed execution plan tailored for the computational graph and target cluster. The generated execution plan can combine state-of-the-art distributed training techniques including data parallelism, operator parallelism, and pipeline parallelism.

Alpa provides a simple API alpa.parallelize and automatically generates the best execution plan by solving optimization problems. Therefore, you can efficiently scale your jax computation on a distributed cluster, without any expertise in distributed computing.

Alpa provides a transformation alpa.parallelize to parallelize a jax function. alpa.parallelize is similar to jax.jit. jax.jit compiles a jax function for a single device, while alpa.parallelize compiles a jax function for a distributed device cluster. You may know that jax has some built-in transformations for parallelization, such as pmap, pjit, and xmap. However, these transformations are not fully automatic, be cause they require users to manually specify the parallelization strategies such as parallelization axes and device mapping schemes. You also need to manually call communication primitives such as lax.pmean and lax.all_gather, which is nontrivial if you want to do advanced model parallelization. Unlike these transformations, alpa.parallelize can do all things automatically for you. alpa.parallelize finds the best parallelization strategy for the given jax function and does the code tranformation. You only need to write the code as if you are writing for a single device.

I was wondering if there's any interest in adopting/integrating a similar system into JAX itself. This could free the vast majority of JAX users from having to manually tune and restructure their programs to parallelize them efficiently for a particular situation and set of computational resources. It could greatly increase the ease and user-friendliness of distributed computing with JAX, resulting in more widespread adoption and popularity.
I'd love to hear your thoughts and comments.

pjit or jax.jit exactly does what you want :)
You write your program as if you are writing for a single device and the XLA GSPMD partitioner should take care of distribution your program and adding collectives for you! See https://jax.readthedocs.io/en/latest/notebooks/Distributed_arrays_and_automatic_parallelization.html
JAX also has integrated itself with the Alpa compiler wherein you can specify pjit.AUTO to in_shardings and out_shardings and that will invoke the auto-spmd (alpa) compiler pass. You can look at these tests: https://github.com/google/jax/blob/782d90dc8501e7148e1fd1dbd4757b4ca0b3ca4d/tests/pjit_test.py#L1261 to see how to use it.

@yashk2810 The Alpa docs say that pjit lacks some features that alpa.parallelize has ("Pipeline Parallelism" and "Automated"):

In summary, alpa.parallelize supports more parallelism techniques in a more automatic way.

Is this out of date?

Yes probably. JAX supports SPMD pipeline parallelism too. I don't know what automated means.

I would also love some guide on how to best use pipeline parallelism in jax. This is especially useful when working with GPUs without fast interconnect, as tensor parallelism (param sharding) is very slow in that case.

After communicating with the people at Alpa, they said that Jax does not welcome them to merge pipeline parallelism function in Alpa into the code of jaxlib. What is this?

Any news? It seems that only Alpa could be able to support pipeline parallelism. @Lime-Cakes

@hawkinsp Is pipeline parallelism possible with current jax version. There are a number of questions regarding this e.g. #17246.
To the best of my knowledge. Tensor parallelism works fine but pipeline parallelism does not.
The usual answer appears to be links to Praxis but there is no simple example if it is possible.


Added Inorder Preorder Postorder tree traversal in C++

@crveda Your PR has been merged successfully, Thank you for your contribution.
Give repo a star if it was useful.
Happy hacking.

@Zohaib-Sathio this repository is showing as excluded from hacktoberfest
Can you please check it once ?

There is a commitment — which is a compulsary requirement — for contributors & maintainers to follow a set of guidelines which is listed here.
This repository does not fall into the guidelines that were initially set by DigitalOcean. More specifically, this statement: "PR/MRs should be useful to maintainers. Repos that encourage simplistic PR/MRs (like adding a name or profile to a list or arbitrarily curating content) will be excluded from Hacktoberfest."
^ If you would like me to be even more specific - it's these 3 words: arbitrarily curating content
This repository was created for the sole purpose of allowing people to contribute pull requests (PRs) with no real purpose other than to be in the "minimum 4 pull requests (PRs)" window to be eligible for a T-Shirt from DigitalOcean.
This 1 week (7 days) of waiting time was implemented so that DigitalOcean can review more than 500K pull requests to ensure that each pull request (PR) meets the guidelines set. Lots of human moderators were chosen by DigitalOcean to take care of this.
If a particular repository was never reported to DigitalOcean where the sole purpose was to defeat the system - it's always — 50% to 75% — possible for your pull requests (PRs) to be flagged and have it not counted towards your contributions for Hacktoberfest 2022.
As always, humans are humans - and not robots. This means that it's sometimes possible for these pull requests (PRs) to slip through DigitalOcean's reviews and have your pull requests (PRs) counted towards your contributions for Hacktoberfest 2022.
Please be aware that if you made multiple repositories which were all excluded - it's better to be safe than sorry to say that it's always possible for DigitalOcean to blacklist your GitHub / GitLab account where any pull request (PR) made by other contributors to your repositories will not have their contributions counted towards Hacktoberfest 2022.
DigitalOcean is always looking to implement more safeguarding measures to prevent unfair advantage towards other people and every October in each year, those rules tend to expand.


sink(ticdc): Revert changes related to the conflict detector

…ad skew issue (#10376) (#10778)"
This reverts commit 2c55c0e8ccd09ef1f84e8c1ea0c0be5fc09f829f.

What problem does this PR solve?

Issue Number: close #10341
What is changed and how it works?
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
Please refer to [Release Notes Language Style Guide](https://pingcap.github.io/tidb-dev-guide/contribute-to-tidb/release-notes-style-guide.html) to write a quality release note.

If you don't think this PR needs a release note then fill it with `None`.

/retest


Travis Support

Problem
Test results are only available if a library consumer runs them.
Solution
Add Travis CI support to performed automated testing.

LGTM


Lab 8 failed testcase 9_12

Description:
My code produces the wrong order of events in the output. From the debugging output which shows the events in the PQ after "3.939 10 done serving by 1" is polled, It appears that this is because the Event "4.590 14 done serving by self-check 4" is polled before Event "4.590 15 serves by self-check 4". When the Event "4.590 15 serves by self-check 4" is polled, it is updated and converted to "3.353 17 serves by self-check 3". Can I check if there is a way to ensure that the selfCheckout Service attempts are updated and polled first before the other Events?
Screenshots
Screenshots (if any)

Hi there, how does your event comparator prioritise events? Whether it's a human server or self-checkout should not matter because the events should have been ordered based on earliest time and smallest customer number already

My event comparator compares the time for each Event, and if they are the same, I compare the associated customerID.

Hm, one possible bug I can think of is that you are not retrieving the most updated server between events since there's some backtracking going on from "4.590 15 serves by self-check 4" to "3.353 17 serves by self-check 3".

Hi I encountered this issue to. I'm not sure if its the same problem as yours but for mine, I realised that the time that is printed is not the same as the time within my Served event used to compare events in the comparator. I fixed it by using a dummy event that does not print to update the Served event time to the correct time so that the comparator compares the correct timings. Hope this helps.

I solved it by creating an Event method to get a string defining the type of event. This breaks the tell don't ask principle but gets the job done. The next step is to have your comparator check the type of event and give precedence accordingly.

Make sure your time comparator is correct and your server is at the most updated state every time you process it

I am assuming that the debugging output that your printed is the PQ list. You might want to check the PQ after line 66.
Assuming your time comparator is right, you might also want to make sure that your event is being created at the right moment.
i.e. Even if your Event time is earlier, there's no point if the Event wasn't created at that point in the first place.


[WIP] Migration of the diff logic from operator-registry + setting of defaultChannel fix

Description
This PR is a Work In Progress and serves the purpose of presenting the suggestion of changes towards the diff logic. Previously present in the opeator-registry project, the diff logic was suggested to be moved to oc-mirror together with the changes proposed by @joehuizenga - of setting a defaultChannel by adding a priority property to a channel.
Relevant discussions:

https://github.com/openshift/oc-mirror/issues/453
https://github.com/operator-framework/operator-registry/pull/969

Fixes #453
This PR comes in parallel with changes to operator-registry. In order to test the migrated diff logic, operator-registry dependency must be set to this one: https://github.com/joehuizenga/operator-registry/pull/1 and vendor has to be updated
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] This change requires a documentation update (?)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Test Configuration:

Firmware version:
Hardware:
Toolchain:
SDK:

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

As agreed, the diff logic should be moved to this repository and this PR presents a suggestion for such a migration.
Some questions that arose:

the pkg structure - migrating the diff logic I suggested action and diff - is that okay?
there are some changes that would have to made in the operator registry as well - since the diff parts of code are now here, some variables (schemas) are refernced from another project and therefore have to be public. Additionally, since the diff logic is getting out of operator-registry, does it also mean that opm diff command should be removed?
To follow other parts of code I used klog for logging - check out the verbosity and if it matches how it's supposed to work
Sorting by name is being done when there is no information about channel priority found. Right now we are sorting by comparing channel names as strings if the priority comparison fails. I am afraid that this way of comparison can not always produce the results we are expecting. For example if a channelName is v1.10 it will be sorted as smaller than v1.9 if we compare it with strings and not with any versioning package comparisons. This thought may be invalid though, cause I am not sure if the channels names can even go up to having two digits as the “minor” version. I’m not sure how the versioning works here. Can channel names also be something like stable and so on here? If so, that can also give us inaccurate results if we sort it like that. What do you think? The initial thought we had with @joehuizenga was to error it out in that case.

I'm looking forward for other comments as well. I'm new to both of these projects so there may be some concepts i haven't fully understood while preparing this PR and I'd appreciate feedback
@dinhxuanvu @joehuizenga @joelanford

/ok-to-test

I haven't had the time to review this PR in a depth but from the initial review, it looks promising. A quick question here is that do you have plan to hook this code up into oc-mirror code as well or this PR is strictly for the code migration?

As agreed, the diff logic should be moved to this repository and this PR presents a suggestion for such a migration.
Some questions that arose:

the pkg structure - migrating the diff logic I suggested action and diff - is that okay?

Overall this looks good to me. Just a thought on the package structure. I am not sure that action makes as much sense in the context of oc-mirror since diff is not a top-level oc-mirror action. To keep the migration simple and keep the boundary between the high-level and low-level diff logic that existed in operator-registry, it might make more sense if the diff package was moved under the operator package (this is where libraries related to low-level catalog processing are located for oc-mirror) and the files in the action package were moved directly under the operator package for (possible) later restructuring. WDYT @pawicao-ibm?

Thank you very much for your replies!
As for your refactoring suggestions @jpower432 it couldn't be done exactly like that since with that we were getting into circular imports between pkg/v1alpha2 and pkg/operator, having the high-level diff logic directly in the pkg/operator. Therefore for now I added the high-level diff logic into pkg/operator/diff package and the diff includers and diff generators files into pkg/operator/diff/include. It certainly makes more sense than having a pkg/action package here. Nevertheless I am not sure if a name include is the right one here, I didn't really know how to name it, so further feedback would be really appreciated

Thank you very much for your replies!
As for your refactoring suggestions @jpower432 it couldn't be done exactly like that since with that we were getting into circular imports between pkg/v1alpha2 and pkg/operator, having the high-level diff logic directly in the pkg/operator. Therefore for now I added the high-level diff logic into pkg/operator/diff package and the diff includers and diff generators files into pkg/operator/diff/include. It certainly makes more sense than having a pkg/action package here. Nevertheless I am not sure if a name include is the right one here, I didn't really know how to name it, so further feedback would be really appreciated

@pawicao-ibm I think that name is probably fine for now IMO. I see where the circular import came from since this PR is adding the DiffIncludeConfig type that oc-mirror is doing conversions for in v1alpha2. I think what you ended up doing actually makes more sense.

@dinhxuanvu @deejross I just wanted to point out that oc-mirror does not use all of the functionality that the diff logic provides (specifically diffing two models), and it may have to be trimmed down to ensure there is no unused code. Not sure if the preference would be to have that trimmed down in this PR or a subsequent PR. Thoughts?

Personally, I prefer to remove unneeded code when possible. My first reaction is to make a separate PR unless there are very minor changes required to this one in order to accomplish, but I'll leave that for you to decide.

@dinhxuanvu @deejross I just wanted to point out that oc-mirror does not use all of the functionality that the diff logic provides (specifically diffing two models), and it may have to be trimmed down to ensure there is no unused code. Not sure if the preference would be to have that trimmed down in this PR or a subsequent PR. Thoughts?

My original proposal was to relocate the diff code and so revamp/refactor it as it is quite bloated and was written a bit hastily without a lot of thoughts for code sanity. As Jenn already said, there are a few of features that are not needed. I'm on board with asking for some code revamp as a part of this PR if possible. However, we can make this task as a progressive process as things can be changed over a series of PRs instead just one. Just my 2 cents.

Thanks for the feedback. I agree that capturing this requirement in a separate issue will do to limit the changes since I don't think the refactor will be particularly minor.

there are some changes that would have to made in the operator registry as well - since the diff parts of code are now here, some variables (schemas) are refernced from another project and therefore have to be public. Additionally, since the diff logic is getting out of operator-registry, does it also mean that opm diff command should be removed?

@dinhxuanvu I know we had some discussion on opm diff remove or deprecate,  I thought the direction was to deprecate which would mean that operator-registry now includes code from oc-mirror until opm diff gets removed.  Is this the direction we want to go?

Sorting by name is being done when there is no information about channel priority found. Right now we are sorting by comparing channel names as strings if the priority comparison fails

I am ok erroring out here

Thanks for the feedback. I agree that capturing this requirement in a separate issue will do to limit the changes since I don't think the refactor will be particularly minor.

agree, new issue to remove unused seems like a good path forward

Therefore for now I added the high-level diff logic into pkg/operator/diff package and the diff includers and diff generators files into pkg/operator/diff/include

diff/include. first thought , it seems strange but struggling with a better name internal? common?   No strong opinion here

Following the suggestion from @joehuizenga , diff/include package was renamed to diff/internal.
Also following the suggestions https://github.com/operator-framework/operator-registry/pull/1006 the operator-registry PRs were separated into two. That means that in order to test oc-mirror, a dependency to operator-registry must be set to a version of the project which includes both of the changes. It can be for example this temporary branch: https://github.com/pawicao-ibm/operator-registry/tree/oc-mirror-testing
A really important matter here that remains is the way all of that will be merged - these changes seem to be dependent on each other so changes in operator-registry and here would have to be synced if it comes to merging.
The work here seems to be ready other than that, I will remove the WIP tag in that case

@jpower432 we are moving forward with both of the operator-registry PRs. One of them is merged already, the other should be merged soon.
Is this one here okay to be approved afterwards or there are any changes that you would like us to make?

Both PRs on registry have been merged. Feel free to pin to the latest commit on registry repo until a new version is released.

@jpower432 @deejross the operator-registry dependency is now set at the latest commit. Eveything in this PR should be now easily testable. Waiting for review/inputs from your side

@jchunkins @jpower432 thank you very much for your feedback. It has been addressed, please check

@jpower432 I think that when I was re-requesting review earlier on, somehow @deejross was removed from the reviewers list and I'm not able to alter that
In any case, final feedback addressed, ready for final approval

/retest

@deejross @jpower432 The PR looks good for me. I would like to ask if you two can do a round of review and give it a lgtm. Then, I can approve it. Thanks.

/lgtm

@deejross @jpower432 @dinhxuanvu
Two minor changes were necessary:

update the operator-registry reference to an actual release (used v1.26.1)
improve the error message and logging when we can't actually set the default channel.

After these changes things /lgtm

/lgtm

Hi team,
Hillay from the IGC PS,
In the past I had no problems mirroring a specific operator version from a channel that was not the daft channel.
Since using the oc-mirror v4.11 binary it would auto-re-direct me to the dafulat channel and won't mirror (output errors) due to me asking for a package version that is not in the "default channel" set up by the catalog and operator maintainers as I understood.
With the advice of a developer from the team (former role) I tried using the oc-mirror v4.12 binary and still had errors (similar but different).
How can I best work to advance this feature/bug in the cli?
Attaching my errors and the same imageSetConfig.yaml used in both tries in different oc-mirror binaries.
imageSet:
apiVersion: mirror.openshift.io/v1alpha2
kind: ImageSetConfiguration
archiveSize: 50
mirror:
operators:

catalog: registry.redhat.io/redhat/redhat-operator-index:v4.10
packages:

name: advanced-cluster-management
channels:

name: release-2.4
minVersion: '2.4.9'
maxVersion: '2.4.9'


Use CSS nesting in the annotationLayer

/botio test

/botio-linux preview

@calixteman I've addressed your comments in a separate commit, mind re-reviewing that part?


Disallow setting priority for sync events to keep state consistent.

Ever since switching to using ocaml-language-server internally we've been getting reports that it's been reporting spurious errors, complaining about malformed identifiers that don't match what's actually in the code (for instance, if the line in question says Option.to_list we would get an error that Option.to_listto_list is not defined).
The root cause of this error is that if we were editing in the middle of a long operation (such as outlining or error detection) we could queue up handful of incremental tells with a priority of Infinity, then the file is saved, which calls refreshImmediate, which enqueues a single full tell at priority 0.  That one would go through first and apply the full file changes, and then the lower priority tells that had been sent before the file was saved are applied, causing Merlin to think that the text had been duplicated.

Nice. Thanks for tracking this down.


Fix node with no text using the text method from a custom node

When you have a paragraph with no text, ProseMirror saves it like this:
'content' => [
    [
        'type' => 'paragraph',
        // there's no 'text' key here
    ],
],

Combine that, with a custom node that has a text() method, and the paragraph would use the custom node's text.
This is because the loop on lines 51-56 goes through all the nodes and $renderClass will always be the last registered class, even when a different class matched.
I had a hard time trying to write a test that covers break-ing out of the loop, so instead, adding another ->matching() check also fixes it.

Hey, I also encountered this error. You need to add the break; in the loop too. Otherwise only the last registered Nodes custom text function will be used. You can test this by adding two nodes with custom text.
        $json = [
            'type' => 'doc',
            'content' => [
                [
                    'type' => 'user',
                ],
            ],
        ];
        $html = '
Foobar
';
        $renderer = new Renderer;
        $renderer->addNodes([Custom\User::class, Custom\Div::class]);
        $this->assertEquals($html, $renderer->render($json));

You're right. I'll rework this and resubmit. I imagine there might also be some issues with the other loops. (ie. the closing tag loop, and both mark loops)

I think the problem is that the $renderClass is used outside of the loop. Since this is the only example of that, I don't think the other loops cause problems. (And the $renderClass in the first (mark) loop is overwritten by the $renderclass in the second loop).
Although adding  break;s still seems reasonable, to prevent looping unnecessarily over the renderClasses after a match has already been found.


[BUG] ToC doesn't display correct active header when clicked

For example, this occurs when clicking "Overview of Hugo and PaperMod"

Likely related to the fixed navbar. Specifically, when you click the ToC heading, the website scrolls such that the content is visible and not covered by the fixed navbar. But it seems that the ToC calculates the active element using what's under the fixed navbar.

https://afeld.github.io/bootstrap-toc/#customization

Similarly, clicking a footnote doesn't scroll to the right spot (i.e., scrolls such that the footnote is covered by the navbar).
Consider a non-fixed navbar.


How to use pretrained_model parameter in scANVI

I want to use scANVI with label transfer. I noticed that it has parameter pretrained_model and I was wondering it this can be used to reduce time of running.
I would like to use it in the following way. Please let me know if this is the intended use:
I have reference dataset - I want to train scVI on this data and use it as pretrained_model.
I have a query that does not have annotation. So If I understand correctly  I should then provide to scANVI the pretrained model + concatenated adata (ref+query, this time with labels).
When I do predict can I use just query data?
Must I register each dataset separately to scVI?  E.g. one for loading model (ref only, including cells I will not use for label transfer), one for compiling model/scANVI (ref - only cells with annotation + query),  and one for prediction?
Do I still need to run train on scANVI if I give it pretrained model as input?

Sorry for the delay. Scanvi by default is created from a pretrained scvi model (that is pretrained on labelled and unlabelled data). The intention of this argument is to allow you to train an SCVI class model of both sets of cells and then build the scanvi classification mechanisms on top of that.

Closing for now, but please let me know if you have any trouble with this argument.


Feat: Adds xypad and an example for it

Adds XY pad view

Supports disabling
Supports light/dark themes

Adds an example for the new view

One odd behavior is that the xypad element and thumb CSS classes don't change the border properties I want it to on dark theme.. Maybe someone could check if I'm missing something there? Other properties like background-color change correctly, but the border-color has no effect.

One odd behavior is that the xypad element and thumb CSS classes don't change the border properties I want it to on dark theme.. Maybe someone could check if I'm missing something there? Other properties like background-color change correctly, but the border-color has no effect.

It looks like you've set a border colour for it in rust code. This will override any css styling on the element.

It looks like you've set a border colour for it in rust code. This will override any css styling on the element.

Ahh, fixed that and updated the image above with the new theme, thanks!

I totally missed this merge!
Thanks, @bboettcher3 and @geom3trik!


EventGrid: Fix remaining swagger correctness issues

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[X] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
Already deployed.

When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
ASAP

If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[X] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@lirenhe, can you please help merge this change and provide an ETA For that?
I am not sure what is next step as I don't see any issue related to my change other than breaking change which is not sure how to resolve given this is what Swagger Correctness team asked us to do. My understanding this should be handled by reviewer to approve this change. Please let me know if I am missing something.


VC code freezed when typing complicated regexp

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: vscode.dev
OS Version: up-to-date mac, up-to-date chrome

I initially put it as a comment to another issue, but I see that it wasn't noticed, so I'm opening a new bug report.
Steps to Reproduce:

go to vscode.dev in the browser
create new file and paste content of https://raw.githubusercontent.com/prisma/database-schema-examples/main/mysql/magento/schema.sql
press CTRL+F or CMD+F, enable regexp search.
search for CREATE TABLE([^;]|[\n])*([^;]|[\n]);
change regex to CREATE TABLE([^;]|[\n])*`([^;]|[\n]); by adding a` between * and (
Chrome tab freezes

/duplicate of #30874

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Update Exoscale Terraform module to v5.0.0

Checklist

[x] The PR has a meaningful title. It will be used to auto-generate the
changelog.
The PR has a meaningful description that sums up the change. It will be
linked in the changelog.
[x] PR contains a single logical change (to build a better changelog).
[x] Update the documentation.
[x] Categorize the PR by adding one of the labels:
bug, enhancement, documentation, change, breaking, dependency
as they show up in the changelog.

Note that the instructions have been spot-checked (yq commands and similar), but I haven't done a full migration with them yet.

Tested the migration successfully on APPUiO Cloud Exoscale and updated the how-to with the things I noticed during the test.


Scope module Installation to only the function where it is used

Powershell-yaml is only needed for the 'Get-AllPkgProperties' function which right now is only used for local dev scenarios.
So scoping module installation to the function where it is used.

/check-enforcer override

While I'm fine with this change I'm curious what prompted it. Were we seeing failures in our pipelines? If so I'd still like to understand what those are because we are likely to hit them in other places.

Yes there was another failure while trying to install powershell-yaml


📦 NEW: Conditional logging option

Yesterday I was going through my project and saw I would quickly have to upgrade my Heroku Postgres add-on as the table was filled with log items 😱
So, based on #28 , I've made this PR to make LogItem creation optional.
How it works:
Add a new COOKIE_CONSENT_LOG_ENABLED setting to False (default is True) and then new log items will not be created. It won't show in the admin too.
The table will still be there though! I didn't know if that's desirable and since I'm still not comfortable toying around migrations, I leave the decision up to @bmihelac. I wasn't really sure what would happen to existing projects if the migration was conditional and making the whole model class conditional meant there would be a new migration for every time the user toggled that setting.
Another option I considered would be to move LogItem to an app of its own and then each new log item would be created with… signals? Not a big fan of signals: they make it hard to keep track of what's changing what. Also, that meant every user would have to manually add a new app in INSTALLED_APPS for keep using log items. Figured the project didn't need this extra friction.
Hope you like it so I can use the updated version on my project! 😄

Thanks for the pull request @MrCordeiro. Everything looks great. I agree with your decision not to skip creating models based on settings or moving LogItem to another app.

@bmihelac please push this new change to PyPi


Add Replicate demo and API

Hi @zRzRzRzRzRzRzR,
Great work on CogVideoX!
This pull request makes it possible to run CogVideoX on Replicate (https://replicate.com/chenxwh/cogvideox-t2v, https://replicate.com/chenxwh/cogvideox-i2v). Also we'd like to transfer the demo pages to THUDM so you can make modifications easily, and happy to help maintain/integrate the upcoming changes and improving the demo :)

@zRzRzRzRzRzRzR thanks for the suggestion, I have made the corresponding modifications :)


fix: flatten nested arrays in parseAbiParameters

Description
Hopefully fix https://github.com/wevm/abitype/issues/231
Additional Information
Introduce a DeepFlatten and use it in ParseAbiParameters instead of assuming that Filter<Mapped, never> has always only one element.
NOTE: I had to update parseAbiParameters to return abiParameters as unknown as ParseAbiParameters<TParams> for the compiler to be happy but waiting for feedback.
Before submitting this issue, please make sure you do the following.

[x ] Read the contributing guide
[x ] Added documentation related to the changes made.
[ ] Added or updated tests (and snapshots) related to the changes made.

PR-Codex overview
This PR enhances the parseAbiParameters function in abitype package to support parsing nested tuple structures.
Detailed summary

Added DeepFlatten type to flatten nested tuple structures
Updated parseAbiParameters to handle nested tuple structures
Improved type inference for parsed ABI parameters

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Can you add a test based on #231? You can use the provided playground as the base for the test. That way if there is a unforseen regression that test catches it.

Sure! I noticed the type tests are failing. I need to fix that as well when I find time. Any help/guidance is welcomed

@xenoliss since depth flatten returns a arraylist now you need to check if it's length is 0 instead of checking if the list member is undefined which was the previous implementation so that it shows as never for the parameters.
Something like this should work. But feel free to take any other approach
? Filter<Mapped, never> extends readonly [...infer Content]
  ? Content['length'] extends 0
    ? never
    : DeepFlatten<Content>
  : never
: never

Hey thank you @Raiden1411, I added your fix and it seems to work fine. I also added the playground test. Let me know how that looks to you.

I added the changeset @Raiden1411


Authentication Services

Question/Comment on Identity Management RFQ
Name and affiliation
Brian Funk - NCI, Inc - Agile BPA Manager
Section of RFQ documents
Attachment 1 PWS, Section 4.0 Requirements
“Contractor will work with agency partners and 18F Identity Management team to build integration (using Security Assertion Markup Language (SAML) or other appropriate technology) between agency web properties and 18F identity management products.”
Question/Comment
Will “build integration” include building authentication services including directory services that support LDAP/RADIUS or social media authentication including Facebook or Google Authentication?

Currently, the integrations involve SAML. We do not plan to support LDAP/RADIUS. That may change as the product develops.


Context on how to use partition key when use add Vertex Gremlin command

Context on how to use partition key when use adding Vertex using Gremlin. I am having trouble figuring out how to do this . Can someone throw some pointers in this regard.

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

ID: 0374b015-1139-9df8-6c96-a8657a088748
Version Independent ID: 2e18d44d-de3c-eee5-7932-0a5a967e9b17
Content: Azure Cosmos DB Gremlin support
Content Source: articles/cosmos-db/gremlin-support.md
Service: cosmos-db
GitHub Login: @LuisBosquez
Microsoft Alias: lbosq

g.addV('<vertex_label>').property('id','').property('/','')

@arunmenon : The syntax is g.addV('<vertex_label>').property('id','').property('','')
The leading "/" is not needed.
The partition key is not a meta property for vertices. If you are using an unlimited graph, we need to know the partition key while creating a vertex to determine its logical/physical placement.


Exposure not supported for color stream on D435i?

Hello,
I've recently switched from a D435 to a D435i and have noticed that manually setting exposure on the color stream is no longer supported on the D435i. That is, the following function call returns false on the D435i:
my_color_stream.supports(RS2_OPTION_EXPOSURE)
and
my_color_stream.supports(RS2_OPTION_ENABLE_AUTOEXPOSURE)
The same code works fine when using the D435 and even with IR streams on the D435i. Is this a potential bug or a limitation of the device?
Thank you,
Mike

Required Info

Camera Model
D435i

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu 16.04

Kernel Version (Linux Only)
4.15.0

Platform
PC

SDK Version
2.17.1

Language
C++

Segment
Robotics

Hello @mkaspr,
Thank you for your inquiry.  A couple questions:
This issue may be OS specific, would you be able to try your code on a Windows 10 system?
Also, have you updated your firmware to latest?
https://downloadcenter.intel.com/download/28481/Latest-Firmware-for-Intel-RealSense-D400-Product-Family?product=128255
Linux Device Firmware Update Tool:
https://www.intel.com/content/dam/support/us/en/documents/emerging-technologies/intel-realsense-technology/Linux-RealSense-D400-DFU-Guide.pdf
Also try using the latest LibRealSense Release:
https://github.com/IntelRealSense/librealsense

Please try this on Windows 10 with updated FW + LibRealSense Binaries
Also try updated FW + LibRealsense Binaries on Linux Ubuntu 16.04 as well.

Update this ticket with your results and we can proceed from there.
Thank you!

Hello
Is the issue still seen on your side?
Under Win10, with RealSense Viewer(2.19.0) and FW<IP_ADDRESS>, I don't see the issue on manual exposure control on RGB camera of D435i.
Thanks


ZEPPELIN-3974. Reorganize zeppelin integration test

What is this PR for?
I create a new module zeppelin-interpreter-integration which contains all the interpreter related integration test. The reason I didn't put it into zeppelin-integration is that zeppelin-integration module's selenium dependency has transitive guava dependency which conflicts with that of zeppelin zengine.
What type of PR is it?
[Refactoring]
Todos

[ ] - Task

What is the Jira issue?

https://jira.apache.org/jira/browse/ZEPPELIN-3974

How should this be tested?

CI pass

Screenshots (if appropriate)
Questions:

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

LGTM!


Running the example phantom recon

I think the example for phantom recons needs some improvement. @cncastillo please can you cross-check that this is the right way to do it.
If I understood it correctly, there are two options that work as it is now, firstly I could activate the Project.toml of GIRFReco.jl by using julia --project=/path/to/GIRFReco.jl joss_example.jl (but that's not in the description), or I could have all the required dependencies installed into my main environment (which is active if I run it as described in the readme).
I think both are not optimal because you want the example to have a similar setup to when someone is using your package, but self-contained and with minimal effort to get it running. The first method activates the wrong environment, and the second requires the user to manually install packages they might not want/need into their main environment. I suggest setting up an environment which you ship with the joss_example.jl, i.e. in the examples folder you run ] activate ., and then add all the dependencies for the example and add the Project.toml to the git repo. The instructions then need to be adjusted to say cd .../examples/, then ] and activate, instantiate, then julia --project=. joss_example.jl.

@felixhorger yes, we only ever tested this from inside the GIRFReco environment, and didn't adjust the example after package-ization during the JOSS pre-review. I will adjust.

There are multiple ways of distributing the examples.
Option 1: Use the same environment as docs
In general, the documentation should have its own Project.toml. So to run the example it would be like this
julia --project=docs/ docs/lit/examples/joss_demo.jl

This is similar to what the CI does to generate the docs with GitHub actions. But really it should just work if I download it and run it.
Option 2: Use literate to generate a Julia file that installs everything for you
In literate you can add special comments #jl (code that will be present only in the generated Julia file), #md (code that will only be in the generated docs), and #nb (for jupyter notebooks). So you can install the packages for the user in a temporary environment.
# This is text that will be present in the docs explaining the code
#jl using Pkg; Pkg.activate(; temp = true); Pkg.add("Package1"); Pkg.add("Package2")
using Package1, Pacakge2
im = recon(data)
p = plot_image(im)
#md savefig(p, "../assets/results.html") # hide
#jl display(p)
#md # ```@raw html
#md # <object type="text/html" data="../../assets/results.html"></object>
#md # ```

The link to the generated files can be added programmatically, see this as an example.
Option 3: Using Manifest.toml and Project.toml to set an environment for an specific example
If you really want a specific example to have a self-contained and reproducible environment you could add a Project.toml and Manifest.toml to docs/lit/examples/ (I think the Manifest.toml is enough). If you cd to that folder and open julia
(@v1.9) pkg> activate .
(@v1.9) pkg> instantiate
julia> include("joss_demo.jl")

But not sure how it will play with Literate if that environment is different from the one in docs (I would make my life easier and use the same environment).
Option 4: Use Pluto for self-contained environments
Another option is putting the example as a Pluto.jl notebook, this could be the best for reproducibility and ease of use because it contains its own Project.toml and Manifest.toml, can also be run as a normal Julia file and exported as plain HTML.
nb_path = "..."
s = Pluto.ServerSession();
nb = Pluto.SessionActions.open(s, nb_path; run_async=false)
html_contents = Pluto.generate_html(nb; binder_url_js="undefined")
open("test_pluto.html", "w") do io
    write(io, html_contents)
end

or opened like a notebook
using Pluto
Pluto.run() #Opens a tab in your browser that you could use to open the notebook

There could be more ways that I haven't thought but that is the jist of it.

@nbwuzhe this is the issue I mentioned in today's meeting

#9 will be addressed here as well

#16

We have elected to pursue Option 1 for reducing the dependencies and also to streamline the running of the examples. This will achieve the target of a significantly more lightweight GIRFReco.jl. We will make this change and close this issue once completed.

We have implemented Option 1 into #4, and so are closing this.


Add Custom Categories

As a user, I would like to create new custom categories, edit their names later, and delete entire categories to enhance the customization of my experience.
Acceptance Criteria:

To add a new category, the user will tap the "plus" icon in the top right-hand corner of the Categories screen. This will take them into the add keyboard flow. New categories will be added to the bottom of the categories list, and should appear on the home screen.
If a user closes the keyboard without saving, they should receive the discard edits alert.
- To edit a custom category name, the user will navigate to the category detail screen and tap the pencil icon. This will take them into the edit keyboard flow.
If a user closes the keyboard without saving any changes, they should receive the discard edits alert.
If a user does not make any changes and closes the keyboard, no alert should be given.
To delete an entire category, a user should navigate to the custom category detail screen and tap the trash can icon in the top right-hand corner. This will delete the entire category and all of its custom phrases in both the Categories setting screen and the home screen.
A user should receive the "are you sure you want to delete?" alert when tapping the delete category button.

Test Note:
Custom Category labels will be in english only for this ticket.
Design:
https://www.figma.com/file/mNrwUygVhTmuWnKNHHkenR/Vocable-New?node-id=1%3A1344

Implemented on PR391


New Feature to include other Covariance Types for Estimating GMMS

Adding the functionality to include other covariance matrices, i.e., full, 'tied,' 'diag,' & 'spherical.'
using the Scikit-Learn GMM

https://github.com/felipemaiapolo/infoselect/commit/1781661e61407d2f038f469fc6cdaae9ea908740
https://github.com/felipemaiapolo/infoselect/commit/ea828663e9ea09a0bcb6c9aeeec0e18499b48773


Update failed with "Error: CTAP2_ERR_OPERATION_DENIED (0x27)"

Hi,
update under Windows 10 (1809 17763.864) failed with this error code.

Another question: What is meant by the abbreviation "WIP"?

Update: I got it running by using the provided commandline tools on another computer. The desktop application still shows this error code.

@emsix why close it?
The function is not OK and solokeys must fix it.

If you're still seeing this issue, can you see if it is still persisting with the 3.0.1. firmware release?

@emsix why close it?
The function is not OK and solokeys must fix it.

I am not sure if it's an not OK function. I had issues after I played to much with a tool calles "Zadiag" to instal different USB drivers. After I could restore the state from before, I was able to update severals Solokeys with "Solo Desktop".


add TypeScript typings

Docs were taken literally from the readme.

These types are outdated. If types are desired, I suggest copy-pasting them from DefinitelyTyped. https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/inflation/index.d.ts


Remove unused dependencies

Types of Changes
Prerequisites
Please make sure you can check the following two boxes:

[x] I have read the CONTRIBUTING document
[x] My code follows the code style of this project

Contribution Type
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue, please reference the issue id)
[ ] New feature (non-breaking change which adds functionality, make sure to open an associated issue first)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] My change requires a change to the documentation
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[x] All new and existing tests passed

Description
Closes #247
Furthermore, I sorted package.json using npx sort-package-json package.json command.
Upgraded memoize-one version to 5.1.0, which natively supports Typescript.
Upgraded jest-puppeteer-docker version to 1.4.2 and updated snapshots accordingly.

Landed in main via cherry-pick.


Support run_as user when downloading files

Describe the Bug
When users specify a run_as user when using a supporting when using the download_files plan function or CLI subcommand we should ensure the file is downloaded as the privileged user, not as the connecting user. This allows users to download files that are owned by the run_as user or otherwise not accessible by the connecting user.

My use case is retrieving OpenSCAP scanning results. We are not allowed to SSH as the root user, so we login with a service account, then sudo to root to run the scans (this is setup very simply using ssh.run-as in our inventory).
I would then like to obtain the scan results using download_file, however the logged-in-user doesn't have access to the root user's home directory (who ran the scan).
The workaround right now is that we have an intermediate step where we copy the scan results to a world-readable directory like /tmp and then obtain them with our SSH user (not ideal, but workable).

Solution
Basically the reverse process of uploading files:

Copy the existing file to the tmpdir/some_random_numbers_and_letters/myfile
Chown to the connecting user
SCP to Bolt controller
Cleanup the temporary instance of the file

Most important is to make sure the file is minimally accessible at each stage, and the intermediary files always get cleaned up.


[#155,#235,#108] Make HTTP API a Protected Resource, Add support of Confidential Client, User Mapping

Summary
The primary goal of this PR is to allow the HTTP API to receive access tokens on all of the iRODS HTTP API endpoints. We do this while moving away from the currently used HTTP API tokens in OAuth related authorization. A major reason for moving towards OAuth tokens is for better integration with existing providers, as well as improved compliance to desired token properties (e.g. token expiration, revocation).
As part of this implementation, confidential clients and user mapping needed to be implemented. The implementation of confidential clients should allow for the HTTP API to contact the OpenID Provider's introspection endpoint, among other benefits. Additionally, the alternate user mapping system allows for further flexibility on how to map tokens to iRODS users.

OAuth Protected Resource #155
This allows access to the HTTP API endpoints by passing an access token as a Bearer token, as is specified in the OAuth specification: https://www.rfc-editor.org/rfc/rfc6749.html#section-7.1
Taking directly from the example provided in the above link, you would just need to send the access token as bearer:
GET /resource/1 HTTP/1.1
     Host: example.com
     Authorization: Bearer mF_9.B5f-4.1JqM

By sending a valid Bearer token, you should have access to the iRODS HTTP API endpoints. It should be noted that access will only be permitted in the following conditions:

The access token provided is valid.
The token can be matched to an iRODS user.

Confidential Client Support #235
If you define client_secret in your configuration, this will run the HTTP API as a confidential client. This should allow for access to protected endpoints on the provider, such as the introspection endpoint, among other benefits.
When running as a confidential client, all requests to the OpenID Provider, aside from well-known endpoint, will send a Bearer token in the Authorization header with the provided client_id and client_secret, as described in the OAuth 2.0 specification: https://www.rfc-editor.org/rfc/rfc6749.html#section-2.3.1
User Mapping #108
Without a mapping mechanism of access tokens to iRODS users, the HTTP API would not be able to function. By specifying the iRODS user, as well as the desired mapping attributes to search for. An example of a mapping can be found below:
"openid_connect": {
  "user_attribute_mapping": {
    "rodsBob": {
      "email"<EMAIL_ADDRESS>      "sub": "a.very.real.sub",
      "phone_number": "56709"
    },
    "rodsAlice": {
      "email"<EMAIL_ADDRESS>      "sub": "a.different.sub"
    }
  }
}

It should be noted that each iRODS user does not require the same number of attributes. Each of the given attributes must match completely in order for the token to be mapped to a user.
When running as a Protected Resource, these mappings will be matched with the response given from the OpenID Provider's introspection endpoint. An example of what may be in an introspection endpoint's response is as follows:
 {
      "active": true,
      "client_id": "l238j323ds-23ij4",
      "username": "jdoe",
      "scope": "read write dolphin",
      "sub": "Z5O3upPC88QrAjx00dis",
      "aud": "https://protected.example.net/resource",
      "iss": "https://server.example.com/",
      "exp":<PHONE_NUMBER>,
      "iat":<PHONE_NUMBER>,
      "extension_field": "twenty-seven"
 }

The previous example was taken from the OAuth 2.0 Token Introspection specification, which can be found at the following link: https://www.rfc-editor.org/rfc/rfc7662.html#section-2.2
Otherwise, they will match against the OpenID Provider's ID Token, given in response to a token endpoint request. An example of what may be in an ID Token is as follows:
{
   "iss": "https://server.example.com",
   "sub": "24400320",
   "aud": "s6BhdRkqt3",
   "nonce": "n-0S6_WzA2Mj",
   "exp":<PHONE_NUMBER>,
   "iat":<PHONE_NUMBER>,
   "auth_time":<PHONE_NUMBER>,
   "acr": "urn:mace:incommon:iap:silver"
}

The previous example was taken from the OpenID Connect Core 1.0 specification, which can be found in the following link: https://openid.net/specs/openid-connect-core-1_0.html#IDToken

Response to: https://github.com/irods/irods_client_http_api/pull/252#discussion_r1501131318
Not for logging. OAuth spec allows you to auth either in the header (preferred) or the body. Some OpenID Providers may not appreciate finding a spare client_id in the body after finding it in the header.

Response to: https://github.com/irods/irods_client_http_api/pull/252#discussion_r1501132405
is_oidc_running_as_client() is oidc_stanza_exists plus run_as_protected_resource. If we run as a protected resource, we don't run as a client, which is most of the auth endpoint.

Rebased onto main. Still need to test.

In client mode, all test pass.
In protected_resource mode, we get 9 tests failing:
...
FAILED test_auth_endpoint.py::test_oidc_resource_owner_password_credentials_login[bob-bob-200] - assert 400 == 200
FAILED test_auth_endpoint.py::test_oidc_resource_owner_password_credentials_login[--401] - assert 400 == 401
FAILED test_auth_endpoint.py::test_oidc_resource_owner_password_credentials_login[aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa-bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb-401]
FAILED test_auth_endpoint.py::test_oidc_authorization_code_login - AssertionError: assert 405 == 200
FAILED test_auth_endpoint.py::test_oidc_authorization_code_non_irods_user - AssertionError: assert 405 == 200
FAILED test_auth_endpoint.py::test_get_oidc_errors[placeholder-bad_code-400] - assert 405 == 400
FAILED test_auth_endpoint.py::test_get_oidc_errors[-bad_code-400] - assert 405 == 400
FAILED test_auth_endpoint.py::test_get_oidc_errors[placeholder--400] - assert 405 == 400
FAILED test_auth_endpoint.py::test_get_oidc_errors[aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa-bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb-400]
...

I would say these failures are expected, since we effectively disable the 'client' related items, and the tests are not made to handle this case yet. Not sure if these are the HTTP codes we want to return, though.

I agree. Those tests seem specific to client mode and that's ok.
Consider adding new tests which target the protected_resource mode.
You can add options to the config.py file to ease some of the automation.

is there also a place to 'skip' tests in certain modes?     not sure the approach vs doubling up lines of code...

Consider adding new tests which target the protected_resource mode.

I'll try and cook up a test, hoping I don't have to make another client.

is there also a place to 'skip' tests in certain modes? not sure the approach vs doubling up lines of code...

We can skip the tests, which I'm considering. If the test code for the modes varies a good bit, will likely make a new function to test the new mode.

If the test code for the modes varies a good bit, will likely make a new function to test the new mode.

that feels correct.

Consider adding new tests which target the protected_resource mode.

I'll try and cook up a test, hoping I don't have to make another client.

Will likely need either a mini http server, or an OIDC client library to make a python test.
This is due to the part where the OpenID Provider returns a response to the 'redirect_uri', which we have to listen for.

is there also a place to 'skip' tests in certain modes? not sure the approach vs doubling up lines of code...

We can skip the tests, which I'm considering. If the test code for the modes varies a good bit, will likely make a new function to test the new mode.

Skipped the tests that were failing.

Got it. Think about the simplest path forward to a 0.3.0 release and we'll discuss that tomorrow.

All tests passed. Manual testing shows in client mode, access tokens are treated like iRODS bearer tokens (effectively rejected). In protected resource mode, access tokens that are expired error out. If the access token is not expired, but the token does not map to a user, it errors out.  Otherwise, it proceeds to do as requested, acting as the mapped user.
TLDR, scripted tests passed, and manual tests seem good too.

most excellent - thank you.

Please resolve the remaining comments and squash to taste if everything is working as expected.

Squashed.

please order the '108, 155, 235' in the commit messages.

I was too slow. No problem.

hooray - let's do it.

Pounded.

Please close any issues mentioned.


Migrate the Deployments and Daemonset manifests to apps/v1

What does this PR do?
extensions/v1beta1 is deprecated for daemonsets and will be removed in 1.16.
This PR moves the Deamonset and Deployment manifests to apps/v1 and add the required selector when necessary.
That includes mostly the doc but also the e2e tests.
From: https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.15.md

DaemonSet, Deployment, and ReplicaSet resources will no longer be served from extensions/v1beta1, apps/v1beta1, or apps/v1beta2 in v1.16. Migrate to the apps/v1 API, available since v1.9. Existing persisted data can be retrieved via the apps/v1 API.

Motivation
Have an example up-to-date of the deployment.
Additional Notes
This is available since k8s 1.9 and I doubt a lot of people are still running k8s < 1.9, so it's quite backward compatible.

Note: there are many commits in here to make it easier to revert things if you want the PR broken down (for example moving the tests changes around).
But if you're all good and ready to merge, feel free to use the squash merge button! ;)

Hey @hkaj!
Thanks for the review and good catch!
I updated the Daemonset you pointed out. Let me know if you want me to do other changes.

thanks again @aerostitch :)


How to send location details every 30 minute using flutter

I want to perform a task in which my app send location details in every 30 minute to the server.I want to do this using flutter. This process would continue even after if App is in close state.
I tried some code,but i didn't find any flutter plugin for background service.I search on google about this,then i got that i have to write native code for both android and ios platform that is the main problem.I can write code for android only not for ios.
Please guide me how to overcome this problem.
thankyou,

Thank you for using Flutter!
Please check out our documentation first:

https://flutter.dev/
https://api.flutter.dev/

If you can't find the answer there, please consider asking a question on the Stack Overflow Web site:

https://stackoverflow.com/questions/tagged/flutter?sort=frequent

Unfortunately, we're not able to provide support via GitHub. GitHub issues are for tracking defects in the product.


Fix Sprite's getColor() behavior

As described in issue 6862 getColor() returns a vertex's modified color instead of the color variable stored in the Sprite.
Even if the reason for the current implementation is to keep sync when the user modifies the vertices' colors directly, current getColor() implementation only takes C1 into account.
Thanks to @tommyettinger, @mgsx-dev, @Frosty-J & @MobiDevelop for helping me understand key concepts

This was changed on aa0d30e2dadbe36d4b549aca3c99c3725333815c.
Pinging @NathanSweet


updated validator versions, added versions to README

I changed versions of validators to ''latest" in package.json and added version to README.template so that actual version is included in the report.
Version of JSON-Schema-Test-Suite is update to latest.
Ran the benchmark on node 0.12

I've merged it, please let me know if there is any issue. Thanks

looks good. I was thinking at one point, that maybe we could schedule a nightly run on the benchmarks somehow?

I was thinking about travis too actually. It can publish the results to somewhere...

Or to GitHub pages like here: http://www.steveklabnik.com/automatically_update_github_pages_with_travis_example/


csv-to-csvw improvements

This is a placholder issue to hold the improvements we want to make to the csv-to-csvw github workflow:

[ ] Ensure that when a CSV gets deleted from the repository, the CSV-W also gets deleted from the out folder + gh-pages branch.

[x] Ensure we're looking for .json files instead of the non-standard .csv.json (@GDonRanasinghe to check)

[ ] make sure that any validation-errors.json files are picked up and archived as artifacts

[ ] When updating a CSV file's content, the inspect command output txt file is appended to when it should be wiped and replaced each time.

[ ] Run the inspect command on code-list outputs as well as cubes which are built.

[ ] Order outputs alphabetically in the index.html output.

[ ] Create a new ticket to implement this workflow as a github action so a user can write their own workflow and don't have to fork the repo.

@robons You are correct on the .json vs .csv.json - I will update accordingly.

The new ticket for publishing the csv-to-csvw workflow is at: https://app.zenhub.com/workspaces/features-squad-61b72275ac896c0010a1b00b/issues/gss-cogs/csv-to-csvw/2


Should only load nvm when needed, not every time.


Improvement/form doc

Update form documentation

I'm not sure why my account wasn't set up properly when I made the first two commit, but that's still me...

Closes #742


19 digit convert double - character problem

NEST/Elasticsearch.Net version:
NEST 7.4
Elasticsearch version:
7.3
Description of the problem including expected versus actual behavior:
return json string:
buckets":[{"key":3515753798950990007,"doc_count":3}]
after Json Serializer key:3.51575379895099E+18
code in AggregateFormatter.GetKeyedBucket ReadDouble
The code is on line 773 of "AggregateFormatter.cs"

Thanks for opening @shz701. Please could you provide a more complete example of what you're doing? It looks like your issue is related to floating point rounding from<PHONE_NUMBER>950990007 to 3.51575379895099E+18<PHONE_NUMBER>950990000), but some more detail will help

yes ,thank you

Reopening as this is an issue.
@shz701, Please could you provide a more complete example of what you're doing? It looks like you might be running a terms aggregation on a double field?

I have an id field that's a 19-digit number


Generating documentation throws error

Stefans-MacBook-Air-2:google-api-nodejs-client Stefan$ npm run generate-docs

><EMAIL_ADDRESS>generate-docs /Users/Stefan/Projects/google-api-nodejs-client
> jsdoc -c jsdoc-conf.json ./README.md

/Users/Stefan/Projects/google-api-nodejs-client/node_modules/jsdoc/lib/jsdoc/tutorial/resolver.js:80
        names = Object.keys(meta);
                       ^
TypeError: Object.keys called on non-object
    at Function.keys (native)
    at addTutorialConf (/Users/Stefan/Projects/google-api-nodejs-client/node_modules/jsdoc/lib/jsdoc/tutorial/resolver.js:80:24)
    at addTutorialConf (/Users/Stefan/Projects/google-api-nodejs-client/node_modules/jsdoc/lib/jsdoc/tutorial/resolver.js:82:13)
    at /Users/Stefan/Projects/google-api-nodejs-client/node_modules/jsdoc/lib/jsdoc/tutorial/resolver.js:141:21
    at Array.forEach (native)
    at Object.exports.load (/Users/Stefan/Projects/google-api-nodejs-client/node_modules/jsdoc/lib/jsdoc/tutorial/resolver.js:115:11)
    at Object.module.exports.cli.resolveTutorials (/Users/Stefan/Projects/google-api-nodejs-client/node_modules/jsdoc/cli.js:410:18)
    at Object.module.exports.cli.processParseResults (/Users/Stefan/Projects/google-api-nodejs-client/node_modules/jsdoc/cli.js:393:13)
    at module.exports.cli.main (/Users/Stefan/Projects/google-api-nodejs-client/node_modules/jsdoc/cli.js:236:14)
    at Object.module.exports.cli.runCommand (/Users/Stefan/Projects/google-api-nodejs-client/node_modules/jsdoc/cli.js:192:5)

npm ERR! Darwin 14.0.0
npm ERR! argv "node" "/usr/local/bin/npm" "run" "generate-docs"
npm ERR! node v0.10.32
npm ERR! npm  v2.1.6
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>generate-docs: `jsdoc -c jsdoc-conf.json ./README.md`
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>generate-docs script.
npm ERR! This is most likely a problem with the googleapis package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     jsdoc -c jsdoc-conf.json ./README.md
npm ERR! You can get their info via:
npm ERR!     npm owner ls googleapis
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/Stefan/Projects/google-api-nodejs-client/npm-debug.log

Any ideas? :)

This file causes jsdoc to throw. Perhaps it does not expect to see a JSON...? Perhaps we could change it to Markdown file or plain JS.

I just tried several attempts at forcing jsdoc to ignore the json file, to no avail. It seems that jsdoc completely ignores the exclusion rules. In fact, it seems it also ignores the includePattern - were it not, a json file would never have made its way into the parsing phase.
I will consider opening a bug/PR at jsdoc repo (maybe later today or during weekend, unless someone beats me to it!).

This should be fixed now.  Please make sure to npm install before running the command.  Thanks!

Fixed by #522


Diagnostic message remove single quotes when it displays the message in the terminal

Description:
I experienced this issue while using openAPI validator plugin. In openAPI we have messages with single quotes for specialized parameters in the compiler diagnostic message. After making the diagnostic it displays without a single quote, Could you please let me know is there a reason for this?
given message

"Missing OpenAPI contract parameter '%s' in the counterpart Ballerina service resource (method: '%s', path: '%s')"

expected message

"ERROR [service.bal:(4:1,19:2)] Missing OpenAPI contract parameter 'q' in the counterpart Ballerina service resource (method: 'get', path: '/weather')"

displayed message

"ERROR [service.bal:(4:1,19:2)] Missing OpenAPI contract parameter q in the counterpart Ballerina service resource (method: get, path: /weather)"

Affected Versions:
SwanLake beta6 RC1
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

This issue was resolved after adding double quotes to the string template.
"Missing OpenAPI contract parameter ''%s'' in the counterpart Ballerina service resource (method: ''%s'', path: ''%s'')

Some templating examples: https://github.com/ballerina-platform/ballerina-lang/blob/master/compiler/ballerina-lang/src/main/resources/compiler.properties


Ms-identity-node prototype

Proof of concept for node.js token validation library and sample, showing JWT tokens can be validated with JOSE.

Closing. POC to remain on branch.


Poorly handled errors when deserializing related_sample_identity

The commit 7a4c511 restricts the accepted representation identifiers to RepresentationIdentifier::PL_CDR_BE and RepresentationIdentifier::PL_CDR_LE in related_sample_identity of inline_qos.rs by using pl_cdr_rep_id_to_speedy_d. This makes the function to return an error for example when the representation identifier is RepresentationIdentifier::CDR_LE. The function is called by Reader::handle_data_msg, and the error is disregarded by calling Result::ok, replacing it with None.
This for example breaks the ros2_service_client example in jhelovuo/ros2-client, as the responses have RepresentationIdentifier::CDR_LE but require a related_sample_identity, and the above error is not printed.

The use of pl_cdr_rep_id_to_speedy_d should be checked also elsewhere as closing the server in ros2_service_client or the client in ros2_service_server example cause similar errors for status_info. Also, someone should make sure representation identifiers are used correctly and for example commit b478b8cb36bb84aab48d36cdfa06e30fa1eeffac does not cause invalid deserializations when CDR_LE etc. are accepted.
In addition, in the ros2_service_client example, restarting the client causes subsequent responses to arrive in 10+ sequence number delay (probably unrelated).

Endianness conversion between Serde and Speedy seems legit.


Update dbt_utils package to reference dbt labs and not fishtown analytics

With the rebranding, the Fishtown github org that was hosting the dbt utils package is now called dbt-labs

Created #17

Update done and release 0.3.0 issued.


Nested data on api response are coming as null

Link to the code that reproduces this issue
https://github.com/vercel/next.js/tree/canary/examples/reproduction-template
To Reproduce
I have a graphql server.
I am using @apollo/experimental-nextjs-app-support/rsc for registering my apollo client on server and @apollo/client.
Now, I am loading an array of objects from my graphql server.
The data is like this
users = [{id:"", name:"", doctor:{bio:"", speciality:""}}]
I am loading this data on a server component. Now the issue is on my client components and my console I am getting this,
users = [{id:"", name:"", doctor:null}]
I don't know why this happening. For testing if I convert the data into string using JSON.stringify and then console it I can even see my doctor object inside my user object.
What can be the issue?
This is the code that I am using on my sever component for get the user from apollo client,
  const { data:DoctorsDataForSlider }:{
    data:DoctorsForHomePageQuery | undefined
  } = await getClient().query({ query: DoctorsForHomePageDocument , variables:doctorQueryVariables});

As you can see in the screenshot. The first data is showing doctor where I used json.stringify and on the second data doctor is null where I used the parsed data.

Current vs. Expected behavior
Nested object on api response set as null.
I should get my full API response data.
Verify canary release

[X] I verified that the issue exists in the latest Next.js canary release

Provide environment information
Platform: Macos
Package Manager:  pnpm
Nodejs:v18.16.0
Nextjs:13.4.19

Which area(s) are affected? (Select all that apply)
App Router, CLI (create-next-app), Data fetching (gS(S)P, getInitialProps)
Additional context
No response

on my registerApolloClient I was using cache as a result it was not loading my updated server data. I just used fetchOptions: { cache: "no-store" }. which resolved my issue.


Add method cumulated_score

Description
Add method  conformal predictions based on cumulated score
Fixes #69
Type of change
Please remove options that are irrelevant.

New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Tests are added in the test_classification.py module
Checklist:

[x] I have read the contributing guidelines
[x] I have updated the HISTORY.rst and AUTHORS.rst files
[x] Linting passes successfully : make lint
[x] Typing passes successfully : make type-check
[x] Unit tests pass successfully : make tests
[x] Coverage is 100% : make coverage
[x] Documentation builds successfully : make doc

Good job ! Comme discuté ce matin, il y a pas mal de modifications à faire afin de prendre en compte l'ordre décroissant des scores dans les classes.

Codecov Report

Merging #93 (9da45ec) into dev (3db34f5) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##               dev       #93   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           11        11
  Lines          828       851   +23
  Branches        56        61    +5
=========================================
+ Hits           828       851   +23

Impacted Files
Coverage Δ

mapie/classification.py
100.00% <100.00%> (ø)

mapie/tests/test_classification.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3db34f5...9da45ec. Read the comment docs.


Fix/add ratelimit headers and default locale

Codecov Report

Merging #73 into master will decrease coverage by 1.65%.
The diff coverage is 25.45%.

@@             Coverage Diff              @@
##             master      #73      +/-   ##
============================================
- Coverage     82.93%   81.27%   -1.66%
- Complexity      279      281       +2
============================================
  Files            44       45       +1
  Lines          1090     1127      +37
  Branches         64       66       +2
============================================
+ Hits            904      916      +12
- Misses          154      179      +25
  Partials         32       32

Impacted Files
Coverage Δ
Complexity Δ

...om/contentful/java/cma/model/CMAHttpException.java
0% <0%> (ø)
0 <0> (?)

...tentful/java/cma/interceptor/ErrorInterceptor.java
66.66% <50%> (+47.61%)
2 <0> (ø)
:arrow_down:

...ain/java/com/contentful/java/cma/ModuleSpaces.java
88.88% <61.11%> (-11.12%)
13 <1> (+1)

...n/java/com/contentful/java/cma/model/CMASpace.java
71.42% <66.66%> (-1.3%)
6 <1> (+1)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9dde7b7...587c4c8. Read the comment docs.

Only comments regarding exceptions are missing, everything else 👌


Generated prettier-ignore comments do nothing

Which project does this relate to?
Router
Describe the bug
By default, the router generator will add prettier-ignore-start and prettier-ignore-end comments to the generated file (functionality added in #1157):
https://github.com/TanStack/router/blob/2c4ff9162cca457fa00ee326367fbe258f212a95/packages/router-generator/src/config.ts#L24
https://github.com/TanStack/router/blob/2c4ff9162cca457fa00ee326367fbe258f212a95/packages/router-generator/src/config.ts#L32
However, these comments are not actually supported by prettier - the start/end range comments are only supported in Markdown right now - prettier/prettier#5287
Your Example Website or App
https://prettier.io/playground/#N4Igxg9gdgLgprEAuEBbAhjATgSwB4AUAOlAASkCMANKQAw30nn2UNVN1uUkCUJJAegBUpAA5Y4MGDjhYAtDgDmUCBLkBnGOiwxSQgSQzZ8xMq06cOLapbMtrvQSPGTpshctVw5CACZ6BECoQCFFpaHVkUG0sCAB3AAVtBEiUdAAbOPQAT0jggCMsdDAAa0kAZXRUOAAZHCg4ZAAzDPU4AqLSitFi+sVkbABXdpA21BwBrGHguDxRWRxq2AyAFVkobRlUlvS24PU+9LgARUGIeGbWkYArdTxyw5Ozi6QdvZAAR2e4BNjRVJA6HUcgacF8YKCIGw6Bw6T6AGEIKgMMhAel0pCDlBFEcAIJSXD5QbwBKyOoNS67EYACxgqHSAHVqTh4OoemA4OUUiycAA3FnZVFgdR5EC84YASSg4Ng5TAuDCuOl5Rg2SOlPe4ggbQZRVEqJcbSwvMawXqRpgv3QihRryuwR6WCNqNV83U8pwYUh4nqMAZOF8MGpyAAHPQQBIvjgJFabegNSMtPl-YHg0gAEzBQZtFbofLbe0gOCofJg8G+GrobGDa1wABiqiM0mxqPQxIgIAAvp2gA
Steps to Reproduce the Bug or Issue

Take any generated TSR route tree file and run it through prettier
Notice prettier still formats the entire file

Expected behavior
The presence of the non-functional prettier-ignore comments is confusing. They should just be removed from the default configuration since there is no way to get prettier to ignore a whole file through comment directives (prettier/prettier#3634).
Screenshots or Videos
No response
Platform

OS: macOS
Browser: N/A

Additional context
No response

For the time being, on some versions of prettier, this seems to be working. In general, you should ignore the generated file from your formatted and linter.
Prettier: https://prettier.io/docs/en/ignore.html#ignoring-files
Eslint: https://eslint.org/docs/latest/use/configure/ignore
We should call this out in the docs.

As far as I'm aware the prettier-ignore-start/end comments were never supported for any language except markdown (prettier/prettier#5287). Is there any actual evidence of it working? From what I can tell, router-generator's output conforms perfectly to the prettier default style when quotes and semis are configured the same, so that might be leading to the impression that it works?

I must be mistaken then 🤔.

What would you suggest as the best option here outside of updating the documentation?
I'm thinking of possibly updating the head comment of the generated output file, telling the user to ignore the generated file from their linter and/or formatted.
Whatever path forward, we'd definitely want to avoid having to update the user's prettierignore file as it relies upon us knowing the location of root dir (which can be different based on people's setups). Plus, this kind of change would lead to people wanting the same changes to accommodate others like eslint, biome, and others.

Yeah, I agree that calling this out in the docs and updating the head comment is probably the best way forward - I don't think there's much automation that can/should be done (at least, until prettier gets around adding a @noformat directive or something).
But whatever happens, I think the currently inserted comments should be removed, since it misleads people (such as me) into thinking they're supposed to do something.

FYI @thomasballinger thought you'd be interested in knowing about this find.


support nextcloud 14

as 14.0.0beta3 is already released and the final release will follow in the end of august

The final relase for nextcloud 14 is planned for august 29th

duplicate #186


KAFKA-10639: ConfigProvider for environment variables

More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@ewencp, @tombentley could you review, please?
I believe this env variable config provider was implemented hundreds of times, should be one here in kafka codebase. (not to mention that it would be automatically on classpath :) )

Thx the info


Can not Build apk correctly

Hi，I could not get the newest changed apk every time run 'flutter build apk'.
But， it will generate correctly unless  deleting the build directory before building.
Below is my computer environment：

Hi @ShengjieGeng
How are you verifying that the .apk didn’t changed?
Can you run (making sure you have an existing apk in the build folder) flutter build apk -v and provide the output?
Thank you

Hi @ShengjieGeng
How are you verifying that the .apk didn’t changed?
Can you run (making sure you have an existing apk in the build folder) flutter build apk -v and provide the output?
Thank you

Hi，
AndroidStudio  analyzes the apk to check the versionName, and found that it is the old verionName.
I just run 'flutter build apk -v', which generated the newest apk correctly.
thank you very much.
PS:
Normally, I will click Android Studio's menu bar:  build->flutter->build apk

Hi @ShengjieGeng
Just to make sure, did you solved the issue?

Hi @ShengjieGeng
Did you solved the issue?

Yes,absolutely.

Hi @ShengjieGeng
Given your last message I feel safe to close this issue, if you disagree please write in the comments and I will reopen it.
Thank you