Using custom TLS certificates with ArgoCD

/question
I am trying to deploy Argo CD on OpenShift,  my OpenShift router is patched to use my TLS certs (letsenctypt). When I try to use the same certificates with argocd via secret in the Operator CR, it does not pick it up.
apiVersion: argoproj.io/v1alpha1
kind: ArgoCD
metadata:
  name: example-argocd
  labels: {}
  namespace: argocd
spec:
  dex:
    image: quay.io/redhat-cop/dex
    version: v2.22.0-openshift
    openShiftOAuth: true
  rbac:
    defaultPolicy: 'role:readonly'
    policy: |
      g, system:cluster-admins, role:admin
    scopes: '[groups]'
  server:
    route:
      enabled: true
  tls:
    ca:
      secretName: my-dev-ca

Anything I am missing here?

We are using the following:
  tls:     initialCerts:       example.com: |         -----BEGIN CERTIFICATE-----         Mx ..

Is there any update on this at all? As an alternative to using re-encrypt on our route, it would simplify things if we could just use passthrough on the route and have ArgoCD use our cert that we are generating with Cert-Manager instead of the self-signed cert that the operator is generating.

I am specifying the cert that we are generating in the CR like this:
tls:     ca:       secretName: argocd-devops-cert
But even after deleting the CR and allowing the entire instance to rebuild all resources, I still see that it is using the self signed cert.

I'll take a look into this.

I've setting up to do some manual testing for this, but this is where my implementation's at:
apiVersion: argoproj.io/v1alpha1
kind: ArgoCD
metadata:
  name: example-argocd
  labels: {}
  namespace: argocd
spec:
  server:
    host: test.example.com
  tls:
    ca:
      secretName: my-dev-ca

It looks up the secret named my-dev-ca, and if there's a ca.crt key in the Data, then it uses it with the spec.server.host to generate the key into the argocd-tls-certs-cm configmap.
If this sounds ok, I might change that secretName to be a LocalObject called secret so you'd do:
  tls:
    ca:
      secret:
        name: my-dev-ca

Maybe I'm misunderstanding the thought behind the original purpose of that value. Currently the operator is generating a self-signed certificate and storing it in a secret named -tls. In our case, our chosen name is argocd-devops, so our secret that it is generating by default looks like this:
apiVersion: v1
metadata:
  namespace: argocd-devops
  name: argocd-devops-tls
  labels:
    app.kubernetes.io/name: argocd-devops-tls
    app.kubernetes.io/part-of: argocd
    argocd.argoproj.io/instance: argocd-devops
data:
  tls.crt: >-  LS0tLS1CRUdJTiBDRVJU...
  tls.key: >-  LS0tLS1CRUdJTiBSU0Eg...
type: kubernetes.io/tls

We use CertManager in our cluster to interface with our Venafi server to issue certificates with our enterprise CA. We are generating a certificate secret using that and it is being created in the same namespace as a secret named argocd-devops-cert. It looks like this:
apiVersion: v1
metadata:
  name: argocd-devops-cert
  namespace: argocd-devops
  annotations:
    cert-manager.io/certificate-name: argocd-devops-cert
    cert-manager.io/issuer-kind: ClusterIssuer
    cert-manager.io/issuer-name: venafi
data:
  ca.crt: ''
  tls.crt: >- LS0tLS1CRUdJTiBDR...
  tls.key: >- LS0tLS1CRUdJTiBSU...
type: kubernetes.io/tls

My hope was that by adding that secret name to the CR, the operator would use this certificate and key for argocd-server container instead of the argocd-tls self-signed certificate, therefore avoiding the security warning from browsers when hitting the ArgoCD console due to the untrusted self-signed cert.

@jdziedzic the tls.ca.secretName is not actually doing anything (it doesn't get used in reconciliation)
My interpretation is that it's within the ca key, which implies that it's defining a CA Certificate?
It feels like there are perhaps two different issues? one for the CA issue, and another for your use case?

@bigkevmcd I am re-reading the initial post again and I guess I misunderstood what they were trying to achieve. I can open a new issue.

@jdziedzic Upon rereading it, I come to a different view, and I think it's the the same thing, I suspect that it's confused by the use of the previously unused field ca.
Most of the work I've done here is reusable, I'll come up with something that works, probably outside of that key, along the lines you're describing there.

Hi @bigkevmcd,
I upgraded the operator to .14 and I do see the ca.crt in the secret now, which is great. However, when I switch the route to re-encrypt with the annotations for the cert-utils operator to modify the route, the operator is constantly overriding the changes to the route that cert-utils is making. Any idea why this is happening?
Spec:
route:
      annotations:
        cert-utils-operator.redhat-cop.io/certs-from-secret: "argocd-devops-cert"
        cert-utils-operator.redhat-cop.io/destinationCA-from-secret: "argocd-devops-ca"
      enabled: true
      path: /
      tls:
        termination: reencrypt
        insecureEdgeTerminationPolicy: Redirect
      wildcardPolicy: None

Error in operator logs:
{"level":"error","ts":1603738968.2680197,"logger":"controller-runtime.controller","msg":"Reconciler error","controller":"argocd-controller","request":"argocd-devops/argocd-devops","error":"Operation cannot be fulfilled on routes.route.openshift.io "argocd-devops-server": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/home/john/go/pkg/mod/github.com/go-logr/zapr@v0.1.1/zapr.go:128\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/home/john/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.0/pkg/internal/controller/controller.go:258\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/home/john/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.0/pkg/internal/controller/controller.go:232\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker\n\t/home/john/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.0/pkg/internal/controller/controller.go:211\nk8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1\n\t/home/john/go/pkg/mod/k8s.io/apimachinery@v0.18.3/pkg/util/wait/wait.go:155\nk8s.io/apimachinery/pkg/util/wait.BackoffUntil\n\t/home/john/go/pkg/mod/k8s.io/apimachinery@v0.18.3/pkg/util/wait/wait.go:156\nk8s.io/apimachinery/pkg/util/wait.JitterUntil\n\t/home/john/go/pkg/mod/k8s.io/apimachinery@v0.18.3/pkg/util/wait/wait.go:133\nk8s.io/apimachinery/pkg/util/wait.Until\n\t/home/john/go/pkg/mod/k8s.io/apimachinery@v0.18.3/pkg/util/wait/wait.go:90"}

@jdziedzic I'll take a look and see
Let me see if I understand what you're doing, you've got a TLS secret argocd-devops-cert and a CA in argocd-devops-ca you're configuring these in the operator, and it's writing them out correctly to the argocd secrets,  but the route is being rewritten by the operator, and it's causing issues with cert-utils?

@jdziedzic How are you applying those annotations? manually?
The operator applies annotations from the server route configuration, something like this should work:
apiVersion: argoproj.io/v1alpha1
kind: ArgoCD
metadata:
  name: example-argocd
  labels:
    example: ingress
spec:
  server:
    route:
      annotations:
        cert-utils-operator.redhat-cop.io/certs-from-secret: "argocd-devops-cert"
        cert-utils-operator.redhat-cop.io/destinationCA-from-secret: "argocd-devops-ca"

@bigkevmcd, yes, I am including the annotations in the ArgoCD spec, I just only included the relevant part of the yaml. When I go to the route in the OpenShift Console, I can see the page constantly flashing between the certificate boxes being populated and then blank. That message above is from the ArgoCD operator logs and appears each time it resets the certificates back to null (which is about every second). It appears that the ArogCD operator is creating the route as expected with the correct annotations, but when the cert-utils operator sees those annotations on the route and attempts to populate the certificate information on the route, the ArgoCD operator is seeing this route as changed and attempting to set it back to the spec state.
Removing additional configurations from the spec, our ArgoCD resource looks like this:
apiVersion: argoproj.io/v1alpha1
kind: ArgoCD
metadata:
  namespace: argocd-devops
  name: argocd-devops
spec:

    host: 'argocd-devops.apps.{{ $root.Values.cluster }}.openshift.cignacloud.com'
    insecure: false
    route:
      annotations:
        cert-utils-operator.redhat-cop.io/certs-from-secret: "argocd-devops-cert"
        cert-utils-operator.redhat-cop.io/destinationCA-from-secret: "argocd-devops-ca"
      enabled: true
      path: /
      tls:
        termination: reencrypt
        insecureEdgeTerminationPolicy: Redirect
      wildcardPolicy: None

What we are trying to achieve here is having the server present a certificate to the browser that matches the route name so we don't get a security warning. argocd-devops-cert is a cert we are generating using cert-manager and argocd-devops-ca is created by the ArgoCD operator and contains the ca.crt from the self-signed certificate that the operator is generating. We are using a rennecrypt route to present our custom certificate to the browser, and then trusting the self-signed CA on the backend.

@jdziedzic thanks for the update, I'll do some digging and see what we can do

Thanks @bigkevmcd!
I am not sure if this alternative would be any easier to implement, but it would almost be more ideal to just be able to tell the operator to use the certificate we are generating with cert-manager instead of having to do re-encrypt. This way the server side would just present the custom cert and I could use passthrough on the route avoiding the need for the annotations and route modification all together.

Hi @bigkevmcd @jdziedzic
I got this working by using a certificate generated by cert-manager (storing the certificate in the already existing secret argocd-tls) and setting the spec.route.termination to passthrough in the ArgoCD definition.
Unfortunately, the documentation of the operator is missing those use cases IMHO.

Hi @bigkevmcd @jdziedzic
I got this working by using a certificate generated by cert-manager (storing the certificate in the already existing secret argocd-tls) and setting the spec.route.termination to passthrough in the ArgoCD definition.
Unfortunately, the documentation of the operator is missing those use cases IMHO.


Pull request for libqglviewer-qt4-dev

For travis-ci/travis-ci#4414.
Ran tests and found no setuid bits.
See https://travis-ci.org/travis-ci/apt-whitelist-checker/builds/72058101

Sorry, but this test will have to be re-run. Will open a new one later.


Add unix socket for introspection for privileged containers

This adds a separate socket for providing introspection to containers.
It is automatically added to all privileged containers as well as the
current copy of the docker client binary for use with the socket.
The socket will be placed in /run/docker.sock.  All linux
systems/images should have a symlink from /var/run to /run.
The introspection socket does not include the swarm/1.12 endpoints as
these require advanced authentication for use.  The consumers will get a
404 if they try to access a swarm endpoint.
Signed-off-by: Michael Crosby<EMAIL_ADDRESS>

I like it :+1: cc @justincormack

Overall LGTM
Wondering if this should be --privileged or another flag. Although I guess they're interchangeable: if you have access to docker you can easily become privileged, and if you're privileged you can get access to the docker socket anyway.
/cc @diogomonica

@aluzzardi ya, it should be another flag as well, waiting for @justincormack to remind me of the good flag name that he thought of, but for testing right now we can add this with privileged containers as it fits the number 1 use case.

earlier discussion https://github.com/docker/docker/pull/9135 and https://github.com/docker/docker/pull/9135#issuecomment-67427605 😇

@crosbymichael what changed? :)

Overall, I'm a bit confused; is this PR for introspection or for controlling docker? For introspection, I'd expect a container to be able to obtain information about itself (published ports on the host, labels, ...?)
For controlling docker, this makes sense, but various discussions in the past lead to a conclusion that we should not do this without fine-grained control over what access the container gets. For example, there's many use-cases of containers that only need access to docker events, without the need to be able to control docker. Currently those bind-mount the docker socket (which is obviously insecure), some things from the top of my head;

being able to listen to a (filtered) set of docker events (specific type of events, or only events for specific containers / services), and (related) being able to inspect the source of that event
getting access to docker stats (filtered?)

If we decide on providing full access by default, changing that to a limited set may be complicated in future. I'd far more like a limited introspection API to start with, and opening up more features when needed.
I really don't like connecting this to --privileged, I think --privileged in general was a bad decision (I think @jpetazzo even mentioned he wanted to call it --insecure at first); we discourage people to use --privileged because it's adding way too much privileges; adding more features to it only seems to encourage people to use it (because it's convenient).
Just my 0.02c.
TL;DR; I really like having an introspection API as a feature, but in this form, I don't see it as an improvement over what we currently have

Won't this break anyone starting docker daemon in a container?

@justincormack what was the flag name that you were thinking about for this feature ?

@crosbymichael I forget, its annoying me...
The janky failure looks real, read only rootfs.
@cpuguy83 comment is an issue I think - either we should put the introspection socket on a different path (ugh) or make it optional.

when we figureout a good flag name i'll just remove this from --privileged

For the flag name, given it's just a socket to the daemon and not specifically introspection per se, why not call it as such?
Something like --daemon-socket /path/to/socket (or something along those lines).

I'd prefer a flag that lets us extend this feature in the future:
--cap-add DOCKER_PRIVILEGED_DAEMON
--docker-cap-add PRIVILEGED_DAEMON
--security-opt docker:privileged-daemon

@ibuildthecloud have you seen this?  Do you have any comments/concerns?

Lets close this until we have a better idea on what people expect and want


Checkout Laptop Data in NerfStudio for Instant-ngp model

Works fine but it need more GPU .
While rendering it shows an issue which is a issue of NerfStudio here


Fixes: #1200 'requirements.txt for testing dependency'

PTAL @ezyang @fmassa

Codecov Report

Merging #1275 into master will increase coverage by 0.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1275      +/-   ##
==========================================
+ Coverage   65.52%   65.59%   +0.06%
==========================================
  Files          74       74
  Lines        5784     5784
  Branches      884      884
==========================================
+ Hits         3790     3794       +4
+ Misses       1727     1725       -2
+ Partials      267      265       -2

Impacted Files
Coverage Δ

torchvision/transforms/transforms.py
80.94% <0%> (ø)
:arrow_up:

torchvision/transforms/functional.py
71.38% <0%> (+1.15%)
:arrow_up:

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 c6e41b5...d142c17. Read the comment docs.

requirements.txt doesn't imply anything for setup.py interaction, e.g. https://stackoverflow.com/questions/43658870/requirements-txt-vs-setup-py
But if you're afraid of people getting confused, you can always move the file to test.
This is kind of a much larger list than I expected though; also, I don't think we want the version pin on PyTorch.

@ezyang okay then should I remove the version for all the dependencies? also which dependencies should we keep?

I'm not too familiar with torchvision's deps, @fmassa will have to answer that question :)

Now I am only left with these modules.

numpy
requests
Pillow
apex
av
lmdb
mock

should I finalize changes with these modules now? or should I add any from pycocotools,
scipy, torch, chartio.


Should this doc be updated for new Microsoft 365 app instead of Office 365?

Re: https://learn.microsoft.com/en-us/windows/client-management/add-an-azure-ad-tenant-and-azure-ad-subscription
I'm performing the steps under Register your free Azure Active Directory subscription
When I login to https://portal.office.com/, it looks absolutely nothing like the pictures on this page.
The instructions say to "Admin tools icon."  There is nothing on the page with the text "admin" on it anywhere.
The title on the pictures on the pages in the task say "Office 365" in the left corner.  The real page has "Microsoft 365" in the corner and there is this banner at the top of the page:
The Office app is becoming the new Microsoft 365 app, your home to find, create, and share your content and ideas.
[Learn more](https://aka.ms/microsoft-365-faq)

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

ID: 418463ae-ff0c-6ea2-9994-172206fd433e
Version Independent ID: 418463ae-ff0c-6ea2-9994-172206fd433e
Content: Add an Azure AD tenant and Azure AD subscription - Windows Client Management
Content Source: windows/client-management/add-an-azure-ad-tenant-and-azure-ad-subscription.md
Product: windows-client
Technology: itpro-manage
GitHub Login: @vinaypamnani-msft
Microsoft Alias: vinpa

Hi @barbj, this article is outdated and I've been working on some clean up (expecting the changes to be published by next week). If you're looking to create an Azure AD tenant, these articles should help:

https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/active-directory-whatis
https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/active-directory-access-create-new-tenant

I have an Azure tenant.  I've created an OIDC OP in the tenant and I am trying my best to figure out how to create a SAML IdP.  My next step is perhaps it requires a paid AD add-on and I was trying now to figure out how to add that to my free account that I created a long time ago.  Not making much headway.

@vinaypamnani-msft  BTW: thank you for the quick response.
Background: I write a SAML service provider and I frequently have customers that ask me questions about how to change settings in their AD IdP.  I was hoping to get some more knowledge so that I could answer their questions.

@barbj I'm afraid I don't have any experience with SAML IdP, but I assume you've already looked at https://learn.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-fed-saml-idp and https://learn.microsoft.com/en-us/azure/active-directory/manage-apps/add-application-portal-setup-sso so perhaps posting in the Azure-Docs repo or opening a support ticket might help.


hostApiBranch Review

hostAPiBranch completed, all relevant hostApi cards finished and ready for Sprint Review tomorrow.

Good job! very thorough testing

Looks great, implementation is very well done.

Branch Merged. Branch deleted.

Branch merged!


added OCM Useful links

Added Useful links in OCM page

I have read the CLA Document and I hereby sign the CLA


Create kadikoyanadolulisesi.txt

@onderbayraktar I am sorry, the official domain of the school is kadikoyanadolulisesi.meb.k12.tr, and you ask to add a domain kadikoyanadolulisesi.k12.tr.
If you were correct, please provide us with a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

@onderbayraktar I am sorry, the official domain of the school is kadikoyanadolulisesi.meb.k12.tr, and you ask to add a domain kadikoyanadolulisesi.k12.tr.
If you were correct, please provide us with a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

@onderbayraktar You might miss my previous comment. Please react.

@onderbayraktar You might miss my previous comment. Please react.

The official email domain for the students is "kadikoyanadolulisesi.k12.tr".
I will ask the administration of the school for a paper in English as a
proof.
I will post the paper whenever I receive it.
Thanks for your attention.
Best regards.
On Mon, Jan 11, 2021, 12:03 Philip Torchinsky<EMAIL_ADDRESS>wrote:

@onderbayraktar https://github.com/onderbayraktar I am sorry, the
official domain of the school is kadikoyanadolulisesi.meb.k12.tr, and you
ask to add a domain kadikoyanadolulisesi.k12.tr.
If you were correct, please provide us with a proof, which shows that the
school recognizes the domain you are submitting as an official email domain
for the students.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/10352#issuecomment-757759226, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACSOTHDTPOVWLQ4VLK2LQ63SZK5GBANCNFSM4VQLY2XA
.

The official email domain for the students is "kadikoyanadolulisesi.k12.tr".
I will ask the administration of the school for a paper in English as a
proof.
I will post the paper whenever I receive it.
Thanks for your attention.
Best regards.
On Mon, Jan 11, 2021, 12:03 Philip Torchinsky<EMAIL_ADDRESS>wrote:

@onderbayraktar https://github.com/onderbayraktar I am sorry, the
official domain of the school is kadikoyanadolulisesi.meb.k12.tr, and you
ask to add a domain kadikoyanadolulisesi.k12.tr.
If you were correct, please provide us with a proof, which shows that the
school recognizes the domain you are submitting as an official email domain
for the students.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/10352#issuecomment-757759226, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACSOTHDTPOVWLQ4VLK2LQ63SZK5GBANCNFSM4VQLY2XA
.

@onderbayraktar Thank you!

@onderbayraktar Thank you!

@onderbayraktar I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for your understanding!


Appsettings keys are not present

There is a table showing which values to set to which keys in an appsettings.json file, but they seem to be documentation placeholders that should have been replaced with actual key names.

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

ID: 520b9821-ecef-20af-a601-ea36c4297d88
Version Independent ID: da9c8ac9-4d7a-4b40-56a2-a4bfe7083567
Content: Secure a hosted ASP.NET Core Blazor WebAssembly app with Azure Active Directory B2C
Content Source: aspnetcore/blazor/security/webassembly/hosted-with-azure-active-directory-b2c.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @guardrex
Microsoft Alias: riande

Hi @mrpmorris ... That's not really workable because some config values are made up of multiple placeholder values from the CLI command that creates the app and at least in one case for the client ID there are two of them, which need to be distinguished for the Client and Server apps in hosted WASM scenarios.
Adopting my approach, the placeholders can be constants across both the CLI command and the values in the files shown. This was the best way I could think of to do this in a consistent, simple way and avoid confusion about what value goes where ...... and by adding the actual example files with fake values SxS with the placeholder files.
Only a few devs over the years opened an issue with a broken app that turned out to be a mistake in getting the values in the right spots. They were usually suffering from simple 😈 where they did things like ...

Stuck the client ID for the Server app into the Client app's config, or vice versa.
Completely avoided placing a key-value pair in the configuration because they just missed it for some reason or thought it was optional config.
Didn't faithfully copy something (e.g., a client ID, a scope, a sign-up/sign-in policy name) from the Azure portal into their CLI command and/or app config.

... i.e., they just simply weren't following the guidance.
Thanks for the suggestion, but I'm going to stick with what we have given that only about a half-dozen devs have opened issues in this vein out of thousands of devs who have used these articles over the last five years. I continue to monitor the situation for devs writing in saying that they're confused by something, but such issues are very rare with this group of articles.


Add classes for complex metadata attributes

Coordinate with #1133 and #1137
Description of issue or feature request:
For consistent use of OOP we should provide classes for all complex metadata fields
and not only for the outer metadata signature wrapper and the inner signed metadata.
This would make the used metadata format more explicit and might have a positive effect on metadata schema validation (see discussion in #1130).
Current behavior:
Mixed use of classes and dictionaries for TUF metadata
Expected behavior:
Provide classes for all complex metadata fields, i.e. 'signatures' (in
Metadata) 'meta'/'targets' (in Timestamp, Snapshot, Targets), 'delegations'
(in Targets), 'keys'/'roles' (in not yet existent Delegation), ...

Created twice due to GitHub glitch. Closing in favour of #1139


Question: efficient implementation of mmseqs easy-rbh for large datasets

Hi,
I want to run "mmseqs easy-rbh" on all pairs of a large dataset of genomes (let's say 100 genomes, so 10,000 pairs). I tested on 1 pairs and it took 27 seconds to run.
I thought to use the modules instead of the easy workflow to make it faster - what I did is:
mmseqs createdb <protein_fasta1>
mmseqs createdb <protein_fasta2>
mmseqs rbh <protein_fasta1_db> <protein_fasta2_db> alnOffsettedDB tmpDir
mmseqs convertalis <protein_fasta1_db> <protein_fasta2_db> alnOffsettedDB output_m8
The advantage of this is that I do only once the "createdb" operations for all genomes. And indeed, the rbh+convertalis commands took 17 seconds to run, which is faster than 27 seconds, and very significant when multiplied by 10,000 genome pairs.
But the problem is that the outputs are different - the output of "easy-rbh" had 100 more pairs than the output of my implementation.
Can you please help me fix my implementation? or explain how to use the easy-rbh but with pre-computed databases?
thanks

Is this with the latest release? We had a few changes a while ago that are only officially part as of release 15
Maybe the issue is already fixed. I don't see anything immediately wrong.
Could you post the full command line output of both calls?

Hi,
thanks for the quick response!
I use the latest mmseqs package (15.6f452).
I attach my:

my 2 fasta files
the script easy_rbh.py which simply runs "easy-rbh", its command line output and the m8 output file (which contains 590 pairs).
the script my_rbh.py which runs mmseqs createdb+rbh+convertails, its command line output and the m8 output file (which contains 489 pairs).

easy_rbh.log
easy_rbh.m8.txt
easy_rbh.py.txt
my_rbh.log
my_rbh.m8.txt
my_rbh.py.txt

Thanks a lot for the response!
about the -s parameter - is it possible to calculate it according to the desired identity_percent cutoff?
Let's say I want to get all results with identity_percent > 40%, is there a way to calculate the required value for "-s" parameter?
(The reason I ask this is that I would like to set this parameter in my pipeline in a dynamic way according to a user-defined identity_percent cutoff)
Thanks again


ResourceNotFoundError: gazebo_ros. Cannot run the first tutorial

Tutorial No.: 1
ROS: Kinetic
Gazebo: 7
Ubuntu: 16.04
System Platform: X64

Expected Behavior
Gazebo simulation window should pop up with the drone centered in middle.
Current Behavior
Error on terminal :
ResourceNotFound: gazebo_ros
Failure Logs
roslaunch px4 mavros_posix_sitl.launch
... logging to /home/atmadeep/.ros/log/ff7c2de2-ac81-11e9-915b-3497f6e05201/roslaunch-osiris-21857.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
Traceback (most recent call last):
File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/init.py", line 306, in main
p.start()
File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/parent.py", line 268, in start
self._start_infrastructure()
File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/parent.py", line 217, in _start_infrastructure
self._load_config()
File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/parent.py", line 132, in _load_config
roslaunch_strs=self.roslaunch_strs, verbose=self.verbose)
File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/config.py", line 451, in load_config_default
loader.load(f, config, verbose=verbose)
File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/xmlloader.py", line 749, in load
self._load_launch(launch, ros_config, is_core=core, filename=filename, argv=argv, verbose=verbose)
File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/xmlloader.py", line 721, in _load_launch
self._recurse_load(ros_config, launch.childNodes, self.root_context, None, is_core, verbose)
File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/xmlloader.py", line 685, in _recurse_load
val = self._include_tag(tag, context, ros_config, default_machine, is_core, verbose)
File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/xmlloader.py", line 95, in call
return f(*args, **kwds)
File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/xmlloader.py", line 627, in _include_tag
default_machine, is_core, verbose)
File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/xmlloader.py", line 685, in _recurse_load
val = self._include_tag(tag, context, ros_config, default_machine, is_core, verbose)
File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/xmlloader.py", line 95, in call
return f(*args, **kwds)
File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/xmlloader.py", line 589, in _include_tag
inc_filename = self.resolve_args(tag.attributes['file'].value, context)
File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/xmlloader.py", line 183, in resolve_args
return substitution_args.resolve_args(args, context=context.resolve_dict, resolve_anon=self.resolve_anon)
File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/substitution_args.py", line 370, in resolve_args
resolved = _resolve_args(resolved, context, resolve_anon, commands)
File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/substitution_args.py", line 383, in _resolve_args
resolved = commands[command](resolved, a, args, context)
File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/substitution_args.py", line 151, in _find
source_path_to_packages=source_path_to_packages)
File "/opt/ros/kinetic/lib/python2.7/dist-packages/roslaunch/substitution_args.py", line 197, in _find_executable
full_path = _get_executable_path(rp.get_path(args[0]), path)
File "/usr/lib/python2.7/dist-packages/rospkg/rospack.py", line 203, in get_path
raise ResourceNotFound(name, ros_paths=self._ros_paths)
ResourceNotFound: gazebo_ros
ROS path [0]=/opt/ros/kinetic/share/ros
ROS path [1]=/opt/ros/kinetic/share
ROS path [2]=/home/atmadeep/catkin_ws/src/Firmware
ROS path [3]=/home/atmadeep/catkin_ws/src/Firmware/Tools/sitl_gazebo

try gazebo in terminal，see if gazebo7 run correctly. If not ,fix it.

I will close this issue for now as discussion has stalled. Re-open if needed.

I will close this issue for now as discussion has stalled. Re-open if needed.
I have the same question. I think my gazebo is correct.


Fix outputs when enabled=false. Change Security Group rules from inline to resources

what

Fix outputs when enabled=false
Change Security Group rules from inline to resources

why

Fix outputs when enabled=false: coalesce will throw error when both parameters are empty
Change Security Group rules from inline to resources: output the Security Group name, ID and ARN to allow adding other rules to the SG (which is not possible with the inline SG rules, and not possible to mix inline rules with resource-based rules)

related

Closes #24

/test all


Can u update this?

Crash after pick case, crash after use key on case

Crash after pick case, crash after use key on case too

MF wont update it GAY FAG


Feature/translations

Pull Request Test Coverage Report for Build 759537020

3 of 5 (60.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.004%) to 75.668%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

InvenTree/part/templatetags/inventree_extras.py
3
5
60.0%

Totals

Change from base Build 758033300:
-0.004%

Covered Lines:
13528

Relevant Lines:
17878

💛  - Coveralls


FancyZone Windows Snap Behind Top Mounted Windows Task Bar [Since Version 0.19.0]

Environment
Windows build number: 10.0.18363.900
PowerToys version: 0.19.0
PowerToy module for which you are reporting the bug (if applicable): FancyZones
Monitor(s): 2 side-by-side 4K monitors (one set to display scaling 100% and the other to 125%)

Steps to reproduce

Set Windows taskbar location to Top
Snap a window to a FancyZone (2 priority grid zones in my case)

Expected behavior
The window should snap to the full-height of the FancyZone below  the task bar
Actual behavior

The window snaps behind the task bar (as shown with the green arrows)
The window leaves a gap underneath each window (as shown with the red arrows), which exposes the desktop background underneath

Screenshots

@JPStrydom
is a template zoneset or a custom one?

@JPStrydom
is a template zoneset or a custom one?

I'm experiencing it in are the template zones. I've tested Priority Grid (2) and Column (2).

@JPStrydom
as a temporary workaround, open the FZ editor and apply the template again.

Looks like the Zones are saved in exact pixels and have nog notice of the taskbar

@JPStrydom
as a temporary workaround, open the FZ editor and apply the template again.

Hi @enricogior ,
I've tried this a few times but it did not help. Even tried other templates and restarted PowerToys a few times, but the issue persisted. Any other ideas?

Looks like the Zones are saved in exact pixels and have nog notice of the taskbar

@Jay-o-Way That would be strange because the issue wasn't present on 0.18.X

Same is happening to me after the update. It ignores the task bar when the windows are applied. But FZ editor leaves out the taskbar while editing as expected.
-It works after re-applying the same config. One more issue that I see is that the pane numbers seem be repeated while dragging as if there are two sets of config active at the same time. I cant take a screenshot of it.
This is captured on phone.

Same is happening to me after the update. It ignores the task bar when the windows are applied. But FZ editor leaves out the taskbar while editing as expected.
-It works after re-applying the same config. One more issue that I see is that the pane numbers seem be repeated while dragging as if there are two sets of config active at the same time. I cant take a screenshot of it.
This is captured on phone.

@vijaybritto
I haven't been able to fix the issue by re-applying the same template zones - perhaps I'm missing something?
Also, I get the same bleeding through issue on my FZ when hovering. Mine is due to me having two virtual desktops with different FZs layouts on each - this makes the zones bleed through and shows the FZs from both desktops. Perhaps this is what's happening to you?

@JPStrydom I have a 2 monitor setup. It worked for me the second time I reapplied on the target monitor

@vijaybritto do you have multiple virtual desktops?

@JPStrydom no. I'm not running any sort virtualization now.

@vijaybritto that's strange, I wonder where your zone bleed through is coming from...

For me (taskbar on the left, custom zones) I don't think reapplying zones works (I will check again); disabling and re-enabling FancyZones doesn't work; but restarting PowerToys does - until the next time my monitor configuration changes (my two main monitors are televisions on displayport-to-hdmi cables and when they turn completely off, Windows thinks they're disconnected - irrelevant to this issue except for explaining why I know the issue returns when the monitor configuration changes).
As mentioned, previous version didn't do this.

Thanks for the fix folks! Looking forward to seeing it 😄

This seems to have been fixed in 0.19.1 that was just released? It is working on mine with the taskbar on top like any sane person should be doing.  😜

Nop, 19.1 didn't fix the issue in my case. When applying a layout, new or existing, windows snap behind the taskbar at top and leaves a blank space as if the taskbar were at the bottom. When defining the zones of a new layout with the taskbar at the top though, it does layout the zone lines correctly considering the taskbar at the top, but once the new layout is saved and applied, the snapping of the windows keep with the wrong behavior.

@MCrank
the fix will be available in 0.20.
For now, just reapplying the template will solve the problem until next time you move the taskbar again.

@MCrank
the fix will be available in 0.20.
For now, just reapplying the template will solve the problem until next time you move the taskbar again.

Re-Applying did not work for me.  Installing the update must have jarred something and made mine work for now.  I'll test it again later when I don't have 100 Windows open.

@MCrank
the fix will be available in 0.20.
For now, just reapplying the template will solve the problem until next time you move the taskbar again.

Thank you, but Just to feedback, re-applying does not work for me either. I even try with a different template and a new layout, and still thinks the taskbar is at bottom when the layout is applied. On drawing/designing a new template, it seems to recognize the new area with the taskbar on top, but once one applies the template, the empty space of the bottom taskbar comes back.

Based on the behavior with the taskbar on the left, I don't think it's specifically assuming the taskbar is at the bottom...I think It's accurately determining how much space is available, but then when the monitor arrangement or taskbar position changes, it mistakenly anchors that space to the top left corner.
Looking forward to 0.20, at any rate.

I wonder if it's possible to make custom layouts automatically resize when you use auto-hide taskbar, just like with template layouts.

I still have an issue simular like this.

The bug is now fixed in 0.19.2

@zuldero
what you posted is not related to this bug, the custom layout shown in your screenshot is not drawn below the task bar.
Open a new issue.
Thanks.

ok sorry than i have miss missunderstood something. I was thinking it is the same issue because with the update the bug has changed. but it is bad for a new issue. maybe it is my fault. Thx for the great work on this tool. it works perfect. (exept fort thet one costum layout)
sry for my english....

The issue with left-side reappears. See https://github.com/microsoft/PowerToys/issues/11180 for details.

The bug is back again after update to v0.59.1. For me:

Reapplying the template doesn't fix.
Turning FancyZones off then on does fix.

The bug is back again after update to v0.59.1. For me:

Please open a new issue attaching a bug report to help us investigate it.

Still reproing on the latest build (v0.68.0). And no, opening the editor and choosing different layouts doesn't fix it.

@enricogior I realize the this was a bug, but I would actually really like to have this as a feature.
Would go really great with a transparent taskbar.
Is there anyway that I could make my FancyZones do that on Win11?


Immutables should be cached even for storeByValue

Manik:
WIth regards to the additional work required to deserialize every time an entry is read, I wonder if the deserialized object could be cached internally and a reference returned.  Now I know this impacts referential integrity when a POJO can be mutated and changes leaked to concurrent threads, but perhaps this can be optimised so that known immutable types (e.g., Strings) can be cached and not deserialized each time?  Taking this concept further, perhaps providing an @Immutable annotation for users to annotate custom POJO values, to allow for this caching of deserialization?

(Terracotta Team)
We have two issues with the addImmutableClass functionality.  Firstly we believe that Yannis' first instincts on https://github.com/jsr107/jsr107spec/issues/9 we correct in that an @Immutable annotation makes more sense and feels more natural than addImmutableClass does.  Although a complete list of immutable types is probably quite extensive I do not see this as a problem - most common usage patterns can be covered with a very small number of immutable platform classes.  What is more, providing an Immutable annotation encourages frameworks such as Hibernate that may utilize 107 to apply the annotation in the relevant places within their code.
Greg: Agree. I suspect he went this way because it was less work. We could have an @CacheImmutable annotation. Or perhaps we want both because Annotations are an optional feature so immutable classes should be registrable without annotations. I prefer the term registerImmutableClass.
The other issue we have with this functionality regards exactly what the meaning is here.  Does declaring a class to be immutable mean that just that class is immutable, or does it mean that class and the entire object graph reachable from it is immutable? We believe the intent is that the latter is true, since the former would require implementations to walk the entire graph checking whether every referenced instance is of a declared immutable type before it can know whether the entire graph is immutable. Assuming that it's the later then we feel it should be explicitly stated as such.  If not then we strongly object since this would put a very large burden on implementors and greatly reduce the power of the feature.
I have updated the Javadoc to the existing add clarify that it is the latter. The Javadoc reads:
"Where a class is declared immutable and it contains references to other classes, the whole object graph will be treated as immutable. "

On the first issue (using annotation). Part of the problem here is that, as I understand annotations, this can not be applied to Classes not owned by the application owner (built in or 3rd party classes).
Given that there are thousands of builltin classes which could be used as keys and or values, asking implementers to "know" whether these are immutable is too big a task.
I am happy renaming the method to whatever the EG prefers (e.g. registerImmutableClass)
On the second issue I'm missing something. The intent of the registration is to declare intent - from javadoc "There is no guarantee or requirement that the class declared as immutable actually is such"
Thus it is perfectly valid for an application to declare java.util.Date as immutable (for use in a key for example) even though it is in fact mutable - the application writer declares the intent that code will not mutate dates placed in the cache.
So, to me it seems obvious that if a class (say java.util.Map) is declared immutable, there is no need to take into account the object graph - it is a statement that keys or values of type Map can be treated as immutable.
I don't understand why there is a concern that the implementation needs to check anything - as I see it the declaration is taken as fact, the implementation needs to do no checking. Maybe I am missing something.

It seems the main purpose of having a set of immutableClasses is to enable an optimization for caches that are configured as storeByValue.
But... It sounds like the concern isn't really if the class is really immutable or not - it's just that you want a way to mark certain classes as being safe to store as references?
Perhaps
@cacheAsReference and a set of registerCacheAsReferenceClasses or something along those lines?
(Or perhaps there is a better name) - since it sounds like a developer could sometimes want to have certain classes that aren't truly immutable.

I'm never a good one for naming but it does seem like you need both an annotation for developer controlled classes and an API to register 3rd party classes.

As I tried to say above, I believe annotations can not be used for builtin or 3rd party classes.
If that is true, then we require an API way of declaring immutable classes.
Since we must have that, annotations are not needed - user classes can also be declared using the API.

Correct, it is just a question of convenience. Is it worth the extra work for the implementations to provide the simpler syntax for end users by having an annotation.

On the subject of the annotation/feature naming I can see the argument for @NotMutated or @CacheAsReference instead of @Immutable - to me there are two questions here though:

I'm generally of the opinion that these annotations should describe properties of the annotated class, and not be directives imposed on the implementation.  @NotMutated for example describes a property of that classes instances that an implementation can choose to take advantage of (or not).  @CacheAsReference is more strongly worded and implies a directive to the Cache implementation that instances of this class must be cached as references (and not copied) - implying that it is an error for the implementation to not obey the directive - which isn't the intention of the feature as I understand it.
Should we be encouraging users to make use of this annotation for classes that are mutable but not currently mutated?  To me this feels like a major source of future Heisenbugs.  By wording the annotation in a stronger way (@Immutable) that declares something very explicit about the class (and well understood by most Java developers) encourages users to not apply the annotation too loosely and leave potential traps for future devs.  This is especially true if this annotation is being applied in frameworks - where adding it to a mutable class is almost certainly a bug.

Yannis,
The second issue regarding the immutability of the class instances versus the entire graph was more a matter of pedantry than anything else.  We simply wanted what we assumed was the implied behavior to be explicitly documented so that implementors could not become confused or implement the feature in ways that would function dramatically differently for the user purely because the API had not been explicit enough.

I'm torn on the subject of annotations versus methods.  Annotations seem to me to be the most natural way to implement this feature - but it does make configuration difficult in certain situations.

No access to the source

for the JDK this can be handled internally (impl can hardcode common immutable types) - 90%+ of the common usage will be of a very small number of immutable types.
for 3rd Party code (e.g. frameworks) these should add the annotations themselves

User overrides of 3rd-party (JDK or other) mutability decisions.  For example Yannis' suggestion of declaring Date to be immutable in some cases - this would seem to be risky (especially given the current CacheManager scoping of this registration).

Situation 1 would seemed to be a transient problem - once the javax.cache standard is released frameworks which rely on caching would (should?) start to implement these annotations in their own code.  I'm not sure we should add methods to solve a transient problem such as this.
Situation 2 seems to be a slight anti-pattern - it seems to risk triggering future Heisenbugs?  Is this a common enough use-case that it should be covered in the spec - or should we instead allow implementors to expose an equivalent method themselves if necessary?

My issue is that while annotations may be more natural to some, they are not possible for 3rd part classes.
This leads to 2 means for an application to declare immutable classes.
For users who find annotations more natural, they will need to mix and match - programmatic approach for some objects (3rd party) and annotations for others. This seems somewhat inconsistent.
I don't think we can put the onus on implementers of Cache to provide immutability declarations for the entire JDK let alone 3rd party classes. As for implementers of 3rd party libraries, we can hope that they would provide javax.cache annotations but no more than that.
Incidentally, my suggestion for Date did not suggest attempting to subclass Date. It was simply a statement that many (most?) usages of Date use it as a immutable so a user who wanted to store Date elements allowing the implementation to take advantage of "immutable" optimizations could do so. If later someone were to make use of the mutability of Date and hit "strange" behavior that would be a case of RTFM.
All that said, if I continue to be the only voice that is resisting the annotation approach I am OK with conceding to the majority.

We seem to be forgetting that annotations are an optional feature which means that there will be perfectly valid implementations that do not support them.
So we have to keep the registration approach anyway for that reason plus the reason that Yannis mentioned.
Also, presumably implementers will also offer a way of doing this in the config.
But I think we do need some clarification in the Javadoc on what is meant by Immutable.

Just to be clear, an @Immutable annotation (or whatever it is called) would in no way be related to the annotations used for aspect based caching. Support for @Immutable would be added in whatever code decides to store an object by reference or by value. You wouldn't need a container (CDI, Spring, etc) for @Immutable to work, the 'isImmutable(Class)' logic would just look in both the set of registered immutable classes and look for the @Immutable annotation.

I guess because values use generics we would not need to check for @Immutable on each put. We could determine this at cache startup.
I think @Immutable is kind of a bad name for this.
What we really mean is that if you have a value in transformed form and you also have a ready copy on the Java heap it is ok to return the one on the heap. Any mutations that might have happened to it (remember it might not actually be immutable) are ok for the cache to ignore. So it is an optimisation hint.
So we really mean @AllowUseOfHeapCopyIfAny
On 15/11/2011, at 2:27 PM, edalquist wrote:

Just to be clear, an @Immutable annotation (or whatever it is called) would in no way be related to the annotations used for aspect based caching. Support for @Immutable would be added in whatever code decides to store an object by reference or by value. You wouldn't need a container (CDI, Spring, etc) for @Immutable to work, the 'isImmutable(Class)' logic would just look in both the set of registered immutable classes and look for the @Immutable annotation.

Reply to this email directly or view it on GitHub:
https://github.com/jsr107/jsr107spec/issues/9#issuecomment-2745191

Regards
Greg Luck
web: http://gregluck.com
skype: gregrluck
yahoo: gregrluck
mobile: +61 408 061 622

I guess because values use generics we would not need to check for @immutable on each put. We could determine this at cache startup.

That would depend on whether the @Immutable annotation is inherited or not.  Making it inherited would make the enforcement easier since as you point out if the generic type of the cache is immutable then all valid put-able types must be immutable too.  Although this is simpler to enforce, I'm not sure it's correct.  Immutability is not an inherited quality - a class that is immutable can easily be subclassed and become a mutable class instead.  In my opinion it doesn't make sense from a user point of view to make the @Immutable annotation inherited.

To Greg's comment, I think we would need to do the check on put since the whole point is to enforce type safety which generics does not do (you can lie to generics mechanism). But I assume the check is cheap - we need to get the Class anyway for using the method form of checking...
To clarify any confusion this discussion of annotations is completely orthogonal to CDI/Spring annotations - not an optional feature.
Note that the whole concept is optional to implementers - immutability is just a hint to an implimentation that it can perform certain optimizations if it so chooses.
To expedite the decision process I will withdraw my resistance to annotations. Given Chris' clarification I vote for

Annotation & method
@Immutable
Not inherited (method & annotation)

Anyone have a magic wand that can make inactive JSR's re-opened and completed? In doing a bit of digging, I noticed that JSR-305 had an @Immutable annotation that it was defining. (Google is shipping a JSR-305 package that contains this annotation as part of their guava library in the ).
( Google-code JSR-305 or from the Original JCIP annotation
Alas, JSR-305 appears to be dead. :(
Because there isn't an existing annotation to lean on, defining an @Immutable that could be used in the context of caching is fine. Providing libraries a way to annotate things and then have those classes optimized in how they are stored in cache I believe is a very useful feature.

Thanks for doing the research.
What if we end up defining javax.cache.Immutable and someone else defines java.util.Immutable? Won't that be confusing?
What about @CacheEntryImmutable?
On 19/11/2011, at 7:17 PM, Ryan Gardner wrote:

Anyone have a magic wand that can make inactive JSR's re-opened and completed? In doing a bit of digging, I noticed that JSR-305 had an @Immutable annotation that it was defining. (Google is shipping a JSR-305 package that contains this annotation as part of their guava library in the ).
( Google-code JSR-305 or from the Original JCIP annotation
Alas, JSR-305 appears to be dead. :(
Because there isn't an existing annotation to lean on, defining an @Immutable that could be used in the context of caching is fine. Providing libraries a way to annotate things and then have those classes optimized in how they are stored in cache I believe is a very useful feature.

Reply to this email directly or view it on GitHub:
https://github.com/jsr107/jsr107spec/issues/9#issuecomment-2802315

Regards
Greg Luck
web: http://gregluck.com
skype: gregrluck
yahoo: gregrluck
mobile: +61 408 061 622

Personally I'm reluctant to change our naming based on a JSR that's currently Inactive - (the slight hypocrisy of this statement is not lost on me ;) ).  Furthermore if JSR-305 was to be re-invigorated and it did end up standardizing an {{@Immutable}} annotation then implementations would probably want to optimize in response to it's presence too.  In that case any sensible JSR-107 implementation would never require a user to apply both annotations to the same type.  In essence if both annotations were present on the class path at the same time then the {{javax.cache.Immutable}} annotation would be effectively deprecated.

Brian Goetz defines Immutable as:
/**

Immutable

The class to which this annotation is applied is immutable. This means that
its state cannot be seen to change by callers. Of necessity this means that
all public fields are final, and that all public final reference fields refer
to other immutable objects, and that methods do not publish references to any
internal state which is mutable by implementation even if not by design.
Immutable objects may still have internal mutable state for purposes of
performance optimization; some state variables may be lazily computed, so
long as they are computed from immutable state and that callers cannot tell
the difference.

Immutable objects are inherently thread-safe; they may be passed between
threads or published without synchronization.
*/

This makes perfect sense to me - a truly immutable object. But we mean something different - that we are allowed to return a reference to a heap object because we are allowed to assume that no threads mutated any part of it's object graph. Not because it really is immutable but because the programmer has identified that we are allowed to take the shortcut.
Looking at all the names suggested I like either of:
@NotMutated
@AllowUseOfHeapCopyIfAny
Having said that if someone does define a true @Immutable we can follow Chris' suggestion and treat those the same way.

Why not @CacheByReference?
From Greg's description this has little to do with true immutability and more to do with marking classes that should be stored by reference even if the cache is configured to store things by value. @Immutable is just one subset of @CacheByReference in that case.

The objection to @CacheByReference was that it's worded as a directive, but this is intended as a performance optimization marker.  A spec compliant cache is entitled to ignore these annotations and still copy everything - at least thats my understanding.

How about @CacheableByReference then? That is worded as a marker and not a directive.

@CacheableByReference works for me.

Had a vote on email group and we agree to kill this


Making FlashIAP object SingletonPtr

Any object left lingering in the source code with static initializer will get pulled in even if not being used.
That's why FlashIAP object should be wrapped in SingeltonPtr envelope.
This will save about 660 B of ROM and 40 B of RAM for applications who do have mbed-clount-client library but are not using it.

@teetak01 Please review and test.

This is in the update domain, @evedon  and @bremoran  - please review.

Looks good to me.

@JanneKiiskila I was told the correct place to open a PR is different, so closing this.

Here is the PR at correct repo https://github.com/ARMmbed/update-client-hub/pull/325


Document all environment variables used

While fixing issue #9 , I realized that I don't think there is a good place where all the environment variables that are used are documented. Most of them are in Vault, but there are some testing related ones that as far as I'm aware only exist in @oohwooh and I's pycharm run configurations. I think it should be safe to put all the env var names here, although I won't start documenting them until I get the OK from someone else in case there's some potential issue I don't see.

I can't think of any potential issues from documentation, nothing anybody couldn't learn from just analyzing the code. There are probably a bunch of outdated things that are now useless from the run configurations though

This issue can probably be closed since #27 lol


Docker build failed with filemanager plugin

Branch: master
Command:
docker build --build-arg     plugins=filemanager     github.com/abiosoft/caddy-docker.git

Output:
Sending build context to Docker daemon  99.84kB
Step 1/22 : FROM abiosoft/caddy:builder as builder
 ---><PHONE_NUMBER>a8
Step 2/22 : ARG version="0.11.2"
 ---> Using cache
 ---> 4576b6b00f92
Step 3/22 : ARG plugins="git,cors,realip,expires,cache"
 ---> Using cache
 ---> aa68a2dcfc1d
Step 4/22 : RUN go get -v github.com/abiosoft/parent
 ---> Running in 194d735e48f4
github.com/abiosoft/parent (download)
github.com/abiosoft/parent
 ---> 36094bf21327
Removing intermediate container 194d735e48f4
Step 5/22 : RUN VERSION=${version} PLUGINS=${plugins} /bin/sh /usr/bin/builder.sh
 ---> Running in 74355520ccbc
Cloning into '/go/src/github.com/mholt/caddy'...
Note: checking out '8ab447e6159ce2c47ccc853cf20ac2b5515c54e9'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

Switched to a new branch 'v0.11.2'
github.com/abiosoft/caddyplug (download)
github.com/abiosoft/errs (download)
github.com/fatih/color (download)
Fetching https://golang.org/x/sys/unix?go-get=1
Parsing meta tags from https://golang.org/x/sys/unix?go-get=1 (status code 200)
get "golang.org/x/sys/unix": found meta tag get.metaImport{Prefix:"golang.org/x/sys", VCS:"git", RepoRoot:"https://go.googlesource.com/sys"} at https://golang.org/x/sys/unix?go-get=1
get "golang.org/x/sys/unix": verifying non-authoritative meta tag
Fetching https://golang.org/x/sys?go-get=1
Parsing meta tags from https://golang.org/x/sys?go-get=1 (status code 200)
golang.org/x/sys (download)
github.com/abiosoft/errs
github.com/fatih/color/vendor/github.com/mattn/go-isatty
github.com/abiosoft/caddyplug/internal
golang.org/x/sys/unix
github.com/fatih/color/vendor/github.com/mattn/go-colorable
github.com/fatih/color
github.com/abiosoft/caddyplug/caddyplug
fetching missing dependencies: caddy, dnsproviders, hook.pluginloader
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/net/internal/iana
github.com/mholt/caddy/vendor/github.com/klauspost/cpuid
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/crypto/pbkdf2
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/crypto/ed25519/internal/edwards25519
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/text/transform
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/sys/unix
github.com/mholt/caddy/vendor/github.com/flynn/go-shlex
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/gopkg.in/square/go-jose.v2/json
github.com/mholt/caddy/vendor/github.com/xenolf/lego/acme
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/crypto/ocsp
github.com/mholt/caddy/vendor/github.com/google/uuid
github.com/mholt/caddy/vendor/github.com/xenolf/lego/log
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/gopkg.in/square/go-jose.v2/cipher
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/text/unicode/bidi
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/text/unicode/norm
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/net/bpf
github.com/mholt/caddy/vendor/github.com/xenolf/lego/platform/wait
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/net/internal/socket
github.com/mholt/caddy/vendor/github.com/xenolf/lego/acme/api/internal/sender
github.com/mholt/caddy/vendor/github.com/xenolf/lego/challenge
github.com/mholt/caddy/vendor/golang.org/x/crypto/ocsp
github.com/mholt/caddy/vendor/github.com/xenolf/lego/certcrypto
github.com/mholt/caddy/telemetry
github.com/mholt/caddy/vendor/github.com/xenolf/lego/acme/api/internal/nonces
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/crypto/ed25519
github.com/mholt/caddy/caddyfile
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/text/secure/bidirule
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/net/ipv4
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/net/ipv6
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/gopkg.in/square/go-jose.v2
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/net/idna
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/github.com/miekg/dns
github.com/mholt/caddy/vendor/github.com/xenolf/lego/acme/api/internal/secure
github.com/mholt/caddy/vendor/github.com/xenolf/lego/acme/api
github.com/mholt/caddy/vendor/github.com/xenolf/lego/certificate
github.com/mholt/caddy/vendor/github.com/xenolf/lego/challenge/tlsalpn01
github.com/mholt/caddy/vendor/github.com/xenolf/lego/challenge/http01
github.com/mholt/caddy/vendor/github.com/xenolf/lego/registration
github.com/mholt/caddy/vendor/github.com/xenolf/lego/challenge/dns01
github.com/mholt/caddy/vendor/github.com/xenolf/lego/challenge/resolver
github.com/mholt/caddy/vendor/github.com/xenolf/lego/lego
github.com/mholt/caddy/vendor/github.com/mholt/certmagic
github.com/mholt/caddy
Cloning into '/root/lib/caddy/gopath/src/github.com/caddyserver/dnsproviders'...
github.com/abiosoft/caddyplug (download)
github.com/abiosoft/caddyplug/internal
github.com/abiosoft/caddyplug
done fetching depedencies.

plugin not found
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/net/internal/iana
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/crypto/pbkdf2
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/text/transform
github.com/mholt/caddy/vendor/github.com/klauspost/cpuid
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/crypto/ed25519/internal/edwards25519
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/sys/unix
github.com/mholt/caddy/vendor/github.com/flynn/go-shlex
github.com/mholt/caddy/vendor/github.com/xenolf/lego/acme
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/gopkg.in/square/go-jose.v2/cipher
github.com/mholt/caddy/vendor/github.com/xenolf/lego/log
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/gopkg.in/square/go-jose.v2/json
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/text/unicode/bidi
github.com/mholt/caddy/vendor/github.com/google/uuid
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/crypto/ocsp
github.com/mholt/caddy/vendor/github.com/xenolf/lego/acme/api/internal/sender
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/net/bpf
github.com/mholt/caddy/vendor/github.com/xenolf/lego/challenge
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/net/internal/socket
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/text/unicode/norm
github.com/mholt/caddy/vendor/github.com/xenolf/lego/platform/wait
github.com/mholt/caddy/vendor/golang.org/x/crypto/ocsp
github.com/mholt/caddy/vendor/github.com/xenolf/lego/acme/api/internal/nonces
github.com/mholt/caddy/vendor/github.com/xenolf/lego/certcrypto
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/crypto/ed25519
github.com/mholt/caddy/telemetry
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/net/ipv6
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/net/ipv4
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/text/secure/bidirule
github.com/mholt/caddy/caddyfile
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/gopkg.in/square/go-jose.v2
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/github.com/miekg/dns
github.com/mholt/caddy/vendor/github.com/xenolf/lego/vendor/golang.org/x/net/idna
github.com/mholt/caddy/vendor/github.com/xenolf/lego/acme/api/internal/secure
github.com/mholt/caddy/vendor/github.com/xenolf/lego/acme/api
github.com/mholt/caddy/vendor/github.com/xenolf/lego/certificate
github.com/mholt/caddy/vendor/github.com/xenolf/lego/challenge/tlsalpn01
github.com/mholt/caddy/vendor/github.com/xenolf/lego/registration
github.com/mholt/caddy/vendor/github.com/xenolf/lego/challenge/http01
github.com/mholt/caddy/vendor/github.com/xenolf/lego/challenge/dns01
github.com/mholt/caddy/vendor/github.com/xenolf/lego/challenge/resolver
github.com/mholt/caddy/vendor/github.com/xenolf/lego/lego
github.com/mholt/caddy/vendor/github.com/mholt/certmagic
github.com/mholt/caddy
plugin not found
Cloning into '/go/src/github.com/caddyserver/builds'...
caddymain/run.go:39:2:
../caddyhttp/filemanager.go:2:10: invalid import path: ""
2019/02/04 02:44:31 exit status 1
exit status 1
The command '/bin/sh -c VERSION=${version} PLUGINS=${plugins} /bin/sh /usr/bin/builder.sh' returned a non-zero code: 1

It has been renamed to filebrowser. https://github.com/mholt/caddy/pull/2417


incorrect OG URLs

In the source for https://matthewrocklin.com/engineering/stability-bias/, I see:
<meta property="og:url" content="https://matthewrocklin.com/engineering/stability-bias.html" />

But https://matthewrocklin.com/engineering/stability-bias.html 404s. (The user experience result for me is that I can't use Instapaper with this blog.)
A possible clue: Coiled's developer blog (e.g. https://blog.coiled.io/blog/coiled-from-prefect/) has the same user experience problem for me, but for a slightly different reason. That blog has no OpenGraph config, but the canonical link is wrong:
<link rel="canonical" href="https://blog.coiled.io/blog/coiled-from-prefect.html" />

I think that this is fixed.  BTW, all posts changed their addresses, without redirects.  My apologies.

Can confirm Instapaper works for me now.

Thanks!


Inspector lags when editing theme

Godot version
v3.4.beta6.official [3e2bb415a]
System information
Windows 11, GLES3
Issue description

Accessing styles from the theme editor seems fine though.
Steps to reproduce
Create a new theme, import all theme elements, try to edit it in the Inspector.
Minimal reproduction project
No response

CC @pycbouh

It should be snappier with https://github.com/godotengine/godot/pull/53397, but what you show in the gif is just inspector updating a big resource, and that’s pretty slow in general.

@pycbouh In 3.3 and before, such lag doesn't occur (or too trivial to notice). I wonder what changed since then.


Set Retry-After-Header for serviceAction

1. Why is this change necessary?
If a shout is set in maintenance, HTTP-Code 503 will be send. But there is missing a Retry-After. This results unwanted errors f.e. in Google Search Console.
https://webmasters.googleblog.com/2011/01/how-to-deal-with-planned-site-downtime.html
2. What does this change do, exactly?
Adding Header Retry-After: 1800 (seconds)
3. Describe each step to reproduce the issue or behaviour.

Register Shop in "Google Search Console"
Wait some days until google indexed some pages
Set Shop in maintenance-mode for 1 hour
after a few days "Search Console" reports errors while indexing links, causing 503 errors with no "Retry-After-Header"

4. Please link to the relevant issues (if any).
5. Which documentation changes (if any) need to be made because of this PR?
6. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-21359
Please use this issue to track the state of your pull request.

Hi @tinect, thank you for your contribution! 🎉
And sorry it took so long, we try to do better! 💙


Added functionality to toggle rendering of URLs as clickable hyperlinks

Addresses the feature-request #27632

@RohithKumbharkar,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

@RohithKumbharkar, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, Microsoft Pull Request Bot

@RohithKumbharkar   thank you for your contribution :heart:.
There are already two PRs targeting links that came in a few days ago for #27632

#28160
and #28281

I will go through them in the order they came in, and see if there is overlap/parity across the 3 PRs.

@RohithKumbharkar Thank you for your contribution. I have just merged the first PR that came in and added a toggle for link detection, #28160 .
I have presented in today's standup and we have found that adding a toggle in the View menu for this option is a bit too much. The editor has very many toggles and we cannot fit all of them in the View menu, even if they are related to rendering, e.h. codeLens, roundedSelection, hideCursorInOverviewRuler, etc.

No biggie 👌 I'm game 😎 I'll just have to invade this repo with more & more PRs 😈
Thanks @alexandrudima even I hated the idea of having a menu item 😱 but left it just in case

:+1: Looking forward to more PRs ! :heart:


fix(brigade-project): allow disabling vcs sidecar

This represents the chart fix originally in https://github.com/Azure/brigade/pull/715
TODO

[x] bump chart version (patch), make build index and update.  (A few concurrent chart changes in PR form so holding off on this.)

When you get a change, we should merge this, as the CLI functionality has also been merged - https://github.com/Azure/brigade/pull/715
Thanks!


Add Github Actions for Linting, Testing, Building, and Releasing.

To trigger a release.
git tag v?.?.?
git push origin v?.?.?

Looks good 👌


Swift/support

This change is

Reviewed 34 of 34 files at r1, 1 of 1 files at r2.
Review status: all files reviewed at latest revision, 3 unresolved discussions.

byuSuite/Classes/FeatureManager/Feature.swift, line 46 at r1 (raw file):

        self.limitToGroGroup = dict["GroGroup"] as? String
        self.loginRequired = dict["LoginRequired"] as? Bool ?? false
        self.iconName = dict["Icon_iOS"] as! String

Remove iOS

byuSuite/Classes/FeatureManager/PopularView.swift, line 17 at r2 (raw file):

private let POPULAR_VIEW_WIDTH: CGFloat = 105
private let POPULAR_VIEW_HEIGHT: CGFloat = 135
private let IMAGE_SIZE: CGFloat = 96.0

Remove decimal

byuSuite/Classes/FeatureManager/PopularView.swift, line 46 at r2 (raw file):

        //Set up width and height of the view
        self.addConstraint(NSLayoutConstraint(item: self, attr1: .width, constant: POPULAR_VIEW_WIDTH))

addConstraints

Comments from Reviewable

Reviewed 3 of 3 files at r3.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Add Unique ID to be able to remove sensor from recorder

If you try to go to "Settings" of sensor.random_joke, you will see this message:
This entity ('sensor.random_joke') does not have a unique ID, therefore its settings cannot be managed from the UI. See the [documentation](https://www.home-assistant.io/faq/unique_id) for more detail.

Also, this code will not work
recorder:
  ...
  exclude:
    entities:
      - sensor.random_joke

I think that it is same issue. So DB is bloated with jokes. I don't think it is common use-case, when you need history of jokes. Most people will see random joke only just now.
Can you add Unique ID  to sensor.random_joke

It started to work after some time. Don't know why.


Verbs hang fix

Replaces the sync wrappers for device to device operations in verbs_util, with a call to the async function with a callback function. Resolves Issue #11725
As mentioned in the issue:
I think the problem rises because the Sync deviceToDevice operation blocks the thread, preventing the earlier Async Device to Device operation from finishing- which, for some reason, blocks the later operation.
I've tested this fix in origin/r1.3 since origin/master is currently broken.
2nd commit only removes the unused functions from verbs_utils. It is not required for validity.
@junshi15 , @shamoya , @byronyi , can you please go over this?

Can one of the admins verify this patch?

Thanks for the fix. Is there any reason you did not get rid of CopyCPUTensorToGPUSync in verbs_util.h?

CopyCPUTensorToGPUSync is still being used by RdmaRemoteRendezvous here
I am still studying it, so I avoided changing this call. But if my understanding of the bug was correct it is definitely a risk.

Nice work!
I think I am using the same sync wrappers (yes all of us are lazy) in my GDR patch. I might as well take a closer look on this before someone raises another issue :)

@yanivbl6 CopyCPUTensorToGPUSync can be an issue if not fixed. Can we fix the one in RdmaRemoteRendezvous as well? thanks.

Sure, I am on it.

I only have access to two boxes with fairly old OS (RHEL6.5) and CUDA 7.5, which limited me to TF1.1. I modify the patch to fit TF1.1, but got the following error during benchmark test.
error message: Cannot parse tensor from proto
Not sure if this is due to my adaptation or it is a problem with this patch.
@shamoya , @bkovalev can you test this patch on TF1.2 or 1.3, if you have access to newer OS/CUDA. Thanks.

Very good work @yanivbl6 , patch looks good.
Plz just update when u finish checking this patch on TF1.2 and TF1.3.

I ran successful tf_cnn_benchmarks with r1.3 ( 4 hosts (worker + ps), 8X4 GPUs, Imagenet data, Resnet-50 model).

Hi @poxvoculi @junshi15,
Can we merge this ?
And when it's merged to master, can we cherry-pick it to r1.3 (since master verbs code is broken) ?
Ido

@poxvoculi What's the policy for patching a branch? Given the fix for verbs on master will take time, it will be useful to patch TF 1.3 (and maybe 1.2).

Jenkins, test this please

We're not making anymore changes to v1.3. This will appear in TF 1.4, though.

Thanks @jhseu
The problem is that the verbs code is broken in master for now due to this issue.
We are working on a fix for, which may require some time.
For now, people who want to work with the RDMA Verbs need to patch r1.3 manually with this commit.
It's not so crazy, but less comfortabale.
I thought v1.3.0 is already out, so cherry-picking this to r1.3 doesn't mean a lot.
or are you updating the v1.3 binary version with r1.3 from time to time ?


Text composables: Android Basics with Compose

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-compose-text-composables?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-compose-unit-1-pathway-3%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-compose-text-composables#6
In which task and step of the codelab can this issue be found?
7.6
Describe the problem
space needed after = sign
from
GreetingText(message = "Happy Birthday Sam!", from ="From Emma")

to
GreetingText(message = "Happy Birthday Sam!", from = "From Emma")

Steps to reproduce?

Go to...
Click on...
See error...

Versions
Android Studio version:
API version of the emulator:
Additional information
Include screenshots if they would be useful in clarifying the problem.

Hi @alghe-global
Thank you for pointing this out.
It has been corrected and will be republished in the near future with the fix.
Hope you are enjoying the course.
Regards.


[feature request] numbered notes

Would it be possible to number the note circles like this? I don't know how many people are using SIFTrain on BlueStacks, but it would be very helpful for people who are using it to get used to the keyboard layout and playing with all fingers. I'm sorry if I'm asking for something difficult. Thank you very much.

while it is not 'hard' to just add the numbers, I don't see a real need for that, if you've ever played mania, IIDX or any other rhythm games with a similar behavior (falling notes) they usually don't have any visual aid other than the layout itself, also.. I noticed you are using an old version of the app, have you updated from the store as of late? Or you're using a local build?

Oh, sorry, it's just because I keep thinking of this app purely as a training tool for SIF for people who want to get better and not a separate game.
This is how the app looks like on BlueStacks, even though I grabbed the newest one from Google Play store via evozi. It also has the Rin icon and Rin loading screen, and no "hint sounds" in the settings. I'm using the same version on my tablet and it's updated.


ReferenceMany mapped by nested property of EmbedMany collection fails to be merged with ObjectManager

How about this for an edge case.
I'm not sure the inheritance is relevant but I want to paint an honest picture of my structure for the avoidance of doubt.
/** @MappedSuperclass */
abstract class Base {
        /** @ReferenceMany(targetDocument="B", mappedBy="cs.d" cascade="all") */
        private $bs = [];
}

/** @Document */
class A extends Base {
        /** @Id */
        private $id;
}

/** @Document */
class B {
        /** @Id */
        private $id;

        /** @EmbedMany(targetDocument="C") */
        private $cs = [];
}

/** @EmbeddedDocument */
class C {
        /** @ReferenceOne(
            inversedBy="bs",
            discriminatorMap={"f":"Foo", "b":"Bar"},
            discriminatorField="t"
        ) */
        private $d;
}

This structure works fine except in the following scenario:

An instance of A is fetched fetched from the ObjectManager.
ObjectManager is cleared.
A is merged back into the ObjectManager.

In this scenario the following error occurs:

Undefined index: cs.d

mongodb-odm/lib/Doctrine/ODM/MongoDB/UnitOfWork.php:1955
mongodb-odm/lib/Doctrine/ODM/MongoDB/UnitOfWork.php:2140
mongodb-odm/lib/Doctrine/ODM/MongoDB/UnitOfWork.php:1963
mongodb-odm/lib/Doctrine/ODM/MongoDB/UnitOfWork.php:1775
mongodb-odm/lib/Doctrine/ODM/MongoDB/DocumentManager.php:467

Note the discriminator classes are defined elsewhere and probably entirely irrelevant.

That's....interesting to say the least. I'll take a look later this week, but this looks like it needs some debugging to figure out. Thanks for the report!

Not sure if it helps, but simple=true is deprecated
https://github.com/Nilz11/mongodb-odm/blob/master/docs/en/reference/annotations-reference.rst#referencemany

simple - deprecated (use storeAs: id)

For the record, I haven't forgotten this issue, just had a few days off and unfortunately caught a nasty bug. I will debug this before the end of the week.

Cool, thanks for the update @alcaeus and get well soon 👍

@Bilge Either I'm missing something, or there is something else involved. I tried reproducing your bug with the following test case: https://github.com/alcaeus/mongodb-odm/blob/gh-1597/tests/Doctrine/ODM/MongoDB/Tests/Functional/Ticket/GH1597Test.php. Did I reproduce your scenario properly? Because it isn't failing over here...

I have the same problem.
My solution was to implement a field in the ReferenceMany class,  $notSaved, and assign the value 'true'.
English is not my mother tongue; please excuse any errors on my part.

@alcaeus That doesn't look the same as the code I posted at all. The discriminator belongs to the field of C, not the base class. Furthermore, the field of C does not point to a target document. Maybe you think these are still equivalent, and maybe they are, I don't know.
Also I technically never call clear(); the clear happens implicitly between two dependent test cases. That is, one test depends on another, and PHPUnit clears down between the two tests. I believe calling clear() effectively emulates the same scenario in a single test case, though.

@bilge I changed the test to account for the missing clear and the discriminator, and it still passes. Since you apparently have a failing test, please post it here (or send it to me privately if you don't want to share it in an open setting). Thanks.

Closing since I can't reproduce it and for lack of feedback. @Bilge if you could produce a failing test case, feel free to reopen this issue. @chefemaster if you manage to reproduce this error in a minimal script, it would be much appreciated as well.


Move timestamp handling into misc/

It's in head table now, but also used by FFTM.

Done already.


Net::HTTP's return code has to be int

test this please

test this please

test this please

test this please


Error message: Invalid audio name found: "1.wav". Only numeric values are allowed.

I met this error when using Individual utterances + matching transcript, would you please let me know what are the expected file name?
In this case, shall I use one transcript file for all the .wav files. Or shall I use a separate transcript file for each .wav?

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

ID: 7e6fc39a-3260-dd83-f0e9-9d2b123d0970
Version Independent ID: ad59b5b5-fefa-5c01-751e-f83b74373d31
Content: How to prepare data for Custom Voice - Speech Service - Azure Cognitive Services
Content Source: articles/cognitive-services/Speech-Service/how-to-custom-voice-prepare-data.md
Service: cognitive-services
Sub-service: speech-service
GitHub Login: @erhopf
Microsoft Alias: erhopf

@wwlpublish Thanks for the question! We're investigating this and will get back to you shortly.

@wwlpublish Yes you can use one transcript file, Below is an example.

@wwlpublish We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

sorry I still meet the same problem'Only numeric values are allowed'. I don't know what kinds of data text file should I upload, I have tried to transfer my data (Chinese characters) into UTF-8-BOM, but it is still go wrong.

I had the same problems and then I realized that the extension of file ( .wav ) should not be declared either
if your structure would be like so:
---dataset.zip
--------- 00001.wav
--------- 00002.wav
Then your trans.txt file should be something like:
00001 [tab] this is the subtitle of
00002 [tab] this is the other subtitle of


TextInput bg colour not being applied

Describe the bug
The background color (defined in theme reference as colors.input.bg) is being ignored by the TextInput.tsx component. Apparently, this can be fixed by including the property in the list of default styles like so:

After running the test, a snapshot refresh was required, which showed the new property being applied correctly.
Note: As this is a public repo, please be careful not to include details or screenshots from unreleased GitHub products or features. In most cases, a good bug report should be able to describe the new component without including business logic or feature details, but if you must discuss context relating to an unreleased feature, please open an issue in the private Design Systems repo and link to it here.
To Reproduce
Steps to reproduce the behavior:

Include the <TextInput /> component somewhere
Check the background colour of the span wrapper
The bg colour is not set

Expected behavior
Since there's a property in theme reference that exposes the bg property for this component, it should be used.
Screenshots
I find it difficult to showcase this issue using screenshots :P
Desktop (please complete the following information):

OS: Windows 10
Browser: Google Chrome
Version: 25

Smartphone (please complete the following information):
Not applicable
Additional context
This is not really a very big issue, and it's a one liner fix. But apparently I don't have enough disk space to make a PR myself! I'm sorry x.x
Thanks!

Should be fixed by https://github.com/primer/react/pull/1661


[SPARK-6252] [mllib] Added getLambda to Scala NaiveBayes

Note: not relevant for Python API since it only has a static train method

Test build #28445 has started for   PR 4969 at commit 63eff48.

This patch merges cleanly.

Test build #28445 has finished for   PR 4969 at commit 63eff48.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/28445/
Test PASSed.

Test build #28557 has started for   PR 4969 at commit a471d90.

This patch merges cleanly.

LGTM of course

Test build #28557 has finished for   PR 4969 at commit a471d90.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/28557/
Test PASSed.

Merged into master. Thanks!


DistanceSensor does not work reliably (or at all)  on Pi Zero

(Possibly a dupe of #644 but this is over all distances)
Operating system: Latest Raspbian Stretch Lite
Pi model: Pi Zero 1.3
GPIO Zero version: e.g. 1.4.1
Pin factory used: e.g. RPiGPIO
from gpiozero import DistanceSensor
from time import sleep

ds = DistanceSensor(15,14)

while True:
    print(ds.distance)
    sleep(0.1)

The results when starting with no obstacle then placing one at about 5 cm for sensor and moving back and forwards are:
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
0.5
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0
0.0

In contrast, using the same set-up with the hcsr04sensor library gives good results (but note that I'm  using 3 samples to give faster results  and thus sacrificing accuracy (default is 11)).
from hcsr04sensor import sensor
from time import sleep

d = sensor.Measurement(14,15)
while True:
    print(d.raw_distance(sample_size=3))
    sleep(0.1)

244.04195069250022
242.5322103902967
242.654953504297
242.58130763589685
242.56494188736346
243.25230332576507
5.60936030981303
8.285160195019246
17.126755840173118
5.9694067775472
7.446415582683964
8.526554985886474
8.83750420802053
10.28178151609055
11.034605948625632
11.910173495161

I notice this issue is closed, does that mean it's fixed?
I've upgraded to v1.5 but the issue remains

What Pi model are you on? Zero?
Which Python version?
Can you confirm the GPIO Zero version you're using is v1.5 by running this in the same environment you're running your code (to make sure it's not e.g. installed for Python 2 when you're using 3)
Also we now recommend using the pigpio pin factory, especially on Pi 1/Zero as noted here: https://gpiozero.readthedocs.io/en/stable/api_input.html#distancesensor-hc-sr04
$ sudo pigpiod
$ export GPIOZERO_PIN_FACTORY=pigpio
$ python3 distance.py

See if you get better results and let us know.

I am on Pi Zero, and v1.5 is conformed:
`>>> from pkg_resources import require

require('gpiozero')
[gpiozero 1.5.0 (/usr/local/lib/python3.5/dist-packages), colorzero 1.1 (/usr/local/lib/python3.5/dist-packages)]
require('gpiozero')[0].version
'1.5.0'`
and I have export GPIOZERO_PIN_FACTORY=pigpio.
The reading is between 50~60 regardless of the actual distance.
But if I enable remote GPIO and run the code on windows(also python3 and gpiozero v1.5), the reading is constantly 100.

Similar issue but with RaspPI 3 B+, see #770


Research Facial Recognition Solutions

Take a look at OpenCV documentation, walk-thought tutorial, and possibly other solutions (packages or libraries)

npm:
opencv4nodejs
face-recognition
face-detection
smile-face-detector

face-recognition is depreciated.


Is there any doc about gorm V2?

Your Question
Is there any doc about gorm V2?
Expected answer
Is there any doc about gorm V2?

https://github.com/go-gorm/gorm/wiki
https://v2.gorm.io/docs/


errorfilter doesn't seem to work

.net 4.5
Windows 2008 R2 Datacentre

my webconfig setting:
 <errorFilter>
      <test>
        <and>
          <greater binding="HttpStatusCode" value="400" type="Int32" />
          <lesser binding="HttpStatusCode" value="500" type="Int32" />
        </and>
      </test>
 </errorFilter>

I don't want 400 Bad Requests to be emailed but they are.  I've even rebooted the server.
Any ideas?

Originally reported on Google Code with ID 369
Reported by<EMAIL_ADDRESS>on 2014-08-26 15:05:16

You want test for greater than 399 to include filtering of 400. Following should fix it:
 <errorFilter>
      <test>
        <and>
          <greater binding="HttpStatusCode" value="399" type="Int32" />
          <lesser binding="HttpStatusCode" value="500" type="Int32" />
        </and>
      </test>
 </errorFilter>


RESTAdapter supports loadSaveResponse flag that causes the record to be loaded from the response the server returns on a save().

Fixes issue #275.

Sorry to reopen this but I believe I'm seeing the original problem again but on embedded records?
Should this fix also cause the update the dirty properties of embedded records from server response data?
In my current build (E 2.3.0 and ED 2.3.3) things are as expected for the parent/top level record.


ZED support

Hi @dusty-nv :)
I suggest you add this optional volume in the README of the ZED Package:
-v ${HOME}/zed_docker_ai/:/usr/local/zed/resources/
this allows you to not download and optimize the AI models used in the container each it's started.
You could also add this volume to not be obliged to download the camera calibration at each run (mostly if the host is not connected to the internet):
-v /usr/local/zed/settings/:/usr/local/zed/settings/

The SDK path is fixed, but you can change the bond folder on the host:
-v <whatever_you_want>:/usr/local/zed/resources/
-v <whatever_you_want>:/usr/local/zed/settings/

OK gotcha, thanks Walter.  BTW ya'll have new JetPack out to build ZED SDK for ;)
https://forums.developer.nvidia.com/t/jetpack-5-1-2-l4t-35-4-1-is-now-live/262030


Patch plugin for 2022.3

Fixes #244
Fixes #254
Fixes #256
Fixes #258
Fixes #260
Fixes #261
Fixes #262
Fixes #264
For anyone who is looking for a pre-built version right now:
JetBrains-Discord-Integration-1.10.0+6.zip
There are some known issues with kipc, so if you get any errors that resemble #252, go to Help > Edit Custom VM Options... and add the following line:
-Dcom.almightyalpaca.jetbrains.plugins.discord.plugin.rpc.connection=rpc

nice

nice

When compiling I get an exception:
An exception occurred applying plugin request [id: 'com.palantir.git-version', version: '0.15.0']
> Failed to apply plugin 'com.palantir.git-version'.
   > Cannot find '.git' directory

Is there a solution to this?

How soon this will be available live and updated plugin will be in store? Do we need the attention of the repository owner for the merge to be completed?

@AlexZeDim not sure when the owner will see this pr. For now, I would go to dnbln's fork, compile it, and then manually install it to the IDE.

@dnbln This fix, is not working for EAP versions of Intellij IDEA. I try, and only works for 2022.3 Versions. Any way to EAP versions?

@dnbln This fix, is not working for EAP versions of Intellij IDEA (2022.3.1 RC). I try, and only works for 2022.3 Versions. Any way to EAP versions?

@arsenelupin0 Fixed in a8c1d548ebacc598ae5dbeaa5c8964c4a898209b

All good and fine, BUT: The plugin crashes when I change projects

@NotJansel Huh... that's weird. Do you have a stack trace of when that happens? I cannot reproduce that

Sure, I'll send one when I get home

strange. I can't seem to reproduce it anymore...

update: I seem to get a different error sometimes, heres the stacktrace:
	at com.intellij.openapi.diagnostic.Logger.error(Logger.java:202)
	at com.almightyalpaca.jetbrains.plugins.discord.plugin.rpc.connection.DiscordIpcConnection.onError(DiscordIpcConnection.kt:128)
	at com.almightyalpaca.jetbrains.plugins.discord.plugin.rpc.connection.DiscordIpcConnection.access$onError(DiscordIpcConnection.kt:39)
	at com.almightyalpaca.jetbrains.plugins.discord.plugin.rpc.connection.DiscordIpcConnection$ipcClient$1$1.invokeSuspend$onError(DiscordIpcConnection.kt:47)
	at com.almightyalpaca.jetbrains.plugins.discord.plugin.rpc.connection.DiscordIpcConnection$ipcClient$1$1.access$invokeSuspend$onError(DiscordIpcConnection.kt)
	at com.almightyalpaca.jetbrains.plugins.discord.plugin.rpc.connection.DiscordIpcConnection$ipcClient$1$1$2.invoke(DiscordIpcConnection.kt:47)
	at com.almightyalpaca.jetbrains.plugins.discord.plugin.rpc.connection.DiscordIpcConnection$ipcClient$1$1$2.invoke(DiscordIpcConnection.kt:47)
	at com.almightyalpaca.jetbrains.plugins.discord.plugin.rpc.connection.DiscordIpcConnection$ipcClient$1$1$invokeSuspend$$inlined$onEvent$4$1.invokeSuspend(KDiscordIPC.kt:103)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
	at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.kt:42)
	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:95)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)

That looks like #252, more or less

Does this also fix the integration for rider?

Does this also fix the integration for rider?

It fixes the integration for each IDEA based IDE, so yeah, Rider will be working.