istioctl does not read multiple sections from an input YAML file

destination: productpage.default.svc.cluster.local
precedence: 1
route:
- tags:
    version: v1
  weight: 100
---
destination: reviews.default.svc.cluster.local
precedence: 1
route:
- tags:
    version: v1
  weight: 100
---
destination: ratings.default.svc.cluster.local
precedence: 1
route:
- tags:
    version: v1
  weight: 100
---
destination: details.default.svc.cluster.local
precedence: 1
route:
- tags:
    version: v1
  weight: 100

When the above input is submitted via a file, only the first one gets processed while the remaining are rejected.

The reason is that we do not expect metadata (name, namespace) in the content. Would including the name inside help:
name: my-destination
namespace: default
kind: destination
spec: ...

Assigning to @esnible

If we include:
        name: my-destination
        namespace: default
        kind: destination
        spec: ...

then what happens with the corresponding istioctl command args? Can the user provide the values in either place or is the command to set multiple rules a different command in istioctl, e.g., istioctl multi-create -f multi-rules.yaml?

I don't think that is the issue. It seems that go-yaml doesn't support parsing multiple documents

From https://godoc.org/gopkg.in/yaml.v2#Unmarshal

Unmarshal decodes the first document found within the in byte slice and assigns decoded values into the out value.

It looks like Kubernetes manually splits up the input file(s) into seperate YAML documents (see https://github.com/kubernetes/client-go/blob/release-2.0/pkg/util/yaml/decoder.go#L94 https://github.com/kubernetes/client-go/blob/release-2.0/pkg/util/yaml/decoder.go#L143.

Thanks for the implementation suggestion @ayj .  Question.  Both istio/manager and kubernetes/client-go are Apache licensed.  If we decide to go this way, do we need a clean room reimplementation of splitYAMLDocument() or would it be expected to copy the 30 lines?
@frankbu @rshriram Two separate questions.  First What CLI argument format is going to be beautiful and expected by users.  First what YAML file format is going to be beautiful.
Regarding the CLI argument format, I think a user would not want to specify the type and name.  kubectl create doesn't need them.  It is much easier to put the type and name in the YaML or to infer it.  I propose getting rid of both arguments.
Regarding the file format, we could go with ayj's suggestion with a decoder splitter or just use a YaML array.  We can put the name and type in the YaML format for rules.  I don't have a mental model of what our users would expect.  What does the team think?

There is no special yaml format. Our rules spec is the yaml format with the
addition of the type and name. Basically, each document has
type:
name:
spec:
..route/destination policy
istioctl create/update -f yaml
needs fixing
istioctl get type
lists all rules of a type , (just name and type, similar to kubectl get svc
) or with -o yaml dumps content.
istioctl get type name
dumps the rule in yaml
istioctl delete -f yaml
deletes rules based on types and names found in the yaml file. There is no
need to parse the spec.  Similar to kubectl delete svc foo
On Thu, Mar 2, 2017 at 9:18 AM Ed Snible<EMAIL_ADDRESS>wrote:

Thanks for the implementation suggestion @ayj https://github.com/ayj .
Question. Both istio/manager and kubernetes/client-go are Apache licensed.
If we decide to go this way, do we need a clean room reimplementation of
splitYAMLDocument() or would it be expected to copy the 30 lines?
@frankbu https://github.com/frankbu @rshriram
https://github.com/rshriram Two separate questions. First What CLI
argument format is going to be beautiful and expected by users. First what
YAML file format is going to be beautiful.
Regarding the CLI argument format, I think a user would not want to
specify the type and name. kubectl create doesn't need them. It is much
easier to put the type and name in the YaML or to infer it. I propose
getting rid of both arguments.
Regarding the file format, we could go with ayj's suggestion with a
decoder splitter or just use a YaML array. We can put the name and type in
the YaML format for rules. I don't have a mental model of what our users
would expect. What does the team think?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/manager/issues/213#issuecomment-283664777, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AH0qd-1zJBFmgCgjoVYeZup3nFjhpGloks5rhs-rgaJpZM4MMrUY
.

--
~shriram

So back to my question above. If we add the type and name to the yaml (and allow multiple rules per yaml) for istioctl create -f rules.yaml, do we also (optionally) still allow istioctl create type name rule-spec.yaml?

@shriram Can you break this down for me?  We have “route-rule”, “ingress-rule.  Both types use cfg.proto’s RouteRule (!!!), defined at istio/api/proxy/v1/config/cfg.proto:104-133.
We have no specification for an array of RouteRule.  @ajy suggested breaking them as kubectl does, which is nice although a clean-room reimplementation of the split may take time and I’ll need a partner.  I am just looking for confirmation before I begin.
@frankb has a good question.  I don’t think we should allow both CLI argument styles because it will be hard for beginners to tell if they are looking at a “with name and type yaml” or a “without name and type yaml”.  Furthermore I think an improvement would be to have istioctl delete [name] [--type type] which would simplify use if the name only matches a single rule.

We should not allow "istioctl create type name rule-spec.yaml".
Let's stick with the delete format I described earlier which is what k8s
does as well (the format you propose has some ambiguity - one can have same
names with different types).
We only allow route-rule and destination. Ingress-rule is not be allowed.
Kuat has already taken care of that I think.
We are not using array of route rules or destination policies. It's
multiple documents in one yaml (k8s style - multiple services in one yaml).
Each document has exactly one Spec.
This is the part that needs fixing (split input yaml into multiple yamls
and make multiple TPR commands).
On Thu, Mar 2, 2017 at 11:18 AM Ed Snible<EMAIL_ADDRESS>wrote:

@shriram https://github.com/shriram Can you break this down for me? We
have “route-rule”, “ingress-rule. Both types use cfg.proto’s RouteRule
(!!!), defined at istio/api/proxy/v1/config/cfg.proto:104-133.
We have no specification for an array of RouteRule. @ajy
https://github.com/ajy suggested breaking them as kubectl does, which
is nice although a clean-room reimplementation of the split may take time
and I’ll need a partner. I am just looking for confirmation before I begin.
@frankb https://github.com/frankb has a good question. I don’t think we
should allow both CLI argument styles because it will be hard for beginners
to tell if they are looking at a “with name and type yaml” or a “without
name and type yaml”. Furthermore I think an improvement would be to have istioctl
delete [name] [--type type] which would simplify use if the name only
matches a single rule.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/manager/issues/213#issuecomment-283699749, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AH0qd-KpNBqe49pX-lGbrMa6F17uE5oSks5rhuvOgaJpZM4MMrUY
.

--
~shriram

@rshriram @ayj Are you proposing the implementation of splitting be copied from https://github.com/kubernetes/client-go/blob/release-2.0/pkg/util/yaml/decoder.go#L143 or that we do a reimplementation of it?

For starters you could use the YAML decoder as is by importing the "client-go/pkt/util/yaml" package. The "yaml" package itself doesn't have any other kubernetes golang dependencies though it does require adding the "client-go" repo, but we're doing that already.

Right, let's just reuse the code. I think we shouldn't spend too much time on making istioctl feature-compatible with kubectl, since istioctl is a temporary solution. Let's get the basic functionality to an acceptable level (to support multi-platform set-up), and push for better integration with kubectl.

Wrong person — I'm @shriram, not the person you're trying to reach
(@rshriram). Please take me off this. Thanks.

Done, sorry about that.


hide rescind testimony button

Summary
#1234
Remove the "Request to Rescind" text.
Prior to this PR, it currently shows up whenever you view your own testimony, which is 1) when you view a bill you've added testimony to, 2) when you view your own profile, and 3) when you click 'edit profile' and view the list of your testimonies.

Checklist

[x] On the frontend, I've made my strings translate-able.
[x] If I've added shared components, I've added a storybook story.
[x] I've made pages responsive and look good on mobile.

Screenshots
On Bill Page

On View Profile

On Edit Profile

Known issues
No known issues
Steps to test/reproduce
For each feature or bug fix, create a step by step list for how a reviewer can test it out. E.g.:

for each step, make sure "Request to rescind" option is not visible

Navigate to a bill that has one's own testimony
Navigate to View Profile
Naviate to Edit Profile -> Testimonies tab

gracias!


user_first_name added to bills list

Hey thanks for doing this, it worked! But would just like to make sure going forward that we not merge into master until another group member reviews the code.


Rename<EMAIL_ADDRESS>to<EMAIL_ADDRESS>

Also changes password from spree123 to test123
Will need #22 merged for tests to pass

:+1:


tests: kernel: usage: Relax timing requirements for RISCV

Test was previously relaxed for RISCV machine timer. I have a platform where it fails on RISCV requiring further relaxation. Relaxing precision for RISCV architecture.

Test was previously relaxed for RISCV machine timer. I have a platform where it fails on RISCV requiring further relaxation. Relaxing precision for RISCV architecture.

Why not relaxing that only for the platform?


Really Python 2/3 compatible, corrected computation error in this regard. Update example with small file

thank you!


upload seem to not work properly

I tried to do upload of image, to smugmug.
I created the api key. I defined the permission properly.
in the demo app, I can authenticate, get information of user, album etc... (with some mint code modification in the demo)
I cannot do any upload
for both, I use the same framework : Oauth1Swift
for upload, I tried postImage() method, and tried to build a modified version of that code.
for upload, I use the information visible here : http://api.smugmug.com/services/api/?method=upload
without the signature calculation fix proposed in another thread, I obtain a "invalid signature" error.
with the signature calculation fix ( compared to the website :
http://oauth.googlecode.com/svn/code/javascript/example/signature.html)
I obtain another error when uploading : System Error 5.
which is something like invalid album
I tried several possibilities :
smugmug API 1.3, API 2.0
Upload using POST, mutlipart, like the code of the sample app does.
Upload using HTTP PUT (I modified the code, to set the body with the image and content-type to image/jpeg)
Upload using HTTP POST (same as above)
I always get the same error. System Error 5.
I think (but I cannot be sure) that there is something not compatible with the framework, and smugmug upload.
could anyone do a test on google account (on my side, it does not work also) or smugmug ?

your error is something like that
http://dgrin.com/showthread.php?t=233736
try to see upload log in smugmug account (maybe Tools -> Account Settings -> Stats -> Uploads -> Details) for more information
sorry I have no time to code a test, maybe just test with a provided project

I wil check. thanks
anyway, I found that in the httprequest code, when there is a body and a content-type, the non oauth parameters were not added.
after fixing that, it works.
I will d a fork soon, and place my code in it, in order to let you see what I did. may be I did it wrong
thanks


Alignment

Currently Runic destroys alignment because it is very stringent about spacing, for example
a  = 1
ab = 2

will be replaced with
a = 1
ab = 2

Doing this is of course a valid option (and what e.g. gofmt does).
The current rule is a single space around operators, but I wonder if relaxing it to at least a single space around operators would satisfy the "human need" to prettify things with alignment would be a good option. I think this would work in all situations where you typically align things.

What about comments? For example:
a  = 1.0 # important float
ab = 2   # fine as integer

Yea same would apply there -- at least one soace before comment.

Perhaps  #41 could be enough to solve this. I think that "useful" alignment is pretty rare but in cases where it is useful you can format it on your own instead. (The example in the OP is IMO a case of aligntment that isn't useful).
It seems very tricky to try to detect existing alignment in the code.


Home page 403 Forbidden

Challenge Name

Issue Description

When I go to freecodecamp home/index page I get:
403 Forbidden
nginx/1.4.6 (Ubuntu)
Browser Information

Browser Name, Version: 47.0
Operating System: firefox
Mobile, Desktop, or Tablet:

Your Code

Screenshot

problem resolved itself


ENH: Support rechunk with some unknown dims

Expands the rechunking methods to support rechunking arrays
with some unknown dimensions, along known dimensions.
Closes https://github.com/dask/dask/issues/2236

I have a TODO in there for updating the plan_rechunk code. The current code happens to already "work" since our block sizes are always NaN, so AFACT, the block_size_limit is always using DEFAULT_BLOCK_SIZE_LIMIT. If I understand correctly, this isn't optimal, but it's the best we can do with unknown dimensions.

Rather than complicate all subroutines to support unknown dims, perhaps it's easier to modify the callers?

My latest commit tries to do that. To summarize the changes

I extracted some of the logic from intersect_chunks into a new helper _old_to_new
All of the new NaN handling is in the _old_to_new function.
We call the (unchanged) _intersect_1d and _breakpoints functions on the known dimensions
We enhance the known output with the necessary lists of slices to handle the unknown dimensions.

I'm worried I've missed some edge cases, since I still don't quite understand the _intersect_1d and _breakpoints methods. But the rechunk tests still pass, so that's something.

Ah my apologies, I didn't catch the extra five in there.
On Wed, Apr 26, 2017 at 8:46 AM, Tom Augspurger<EMAIL_ADDRESS>wrote:

@TomAugspurger commented on this pull request.
In dask/array/tests/test_rechunk.py
https://github.com/dask/dask/pull/2251#discussion_r113441265:

+def assert_chunks_match(left, right):

for x, y in zip(left, right):

   if np.isnan(x).any():

       assert np.isnan(x).all()

   else:

       assert x == y

+def test_rechunk_unknown_raises():

dd = pytest.importorskip('dask.dataframe')

x = dd.from_array(da.ones(shape=(10, 10), chunks=(5, 5))).values
with pytest.raises(ValueError):

   x.rechunk((None, (5, 5, 5)))

Thin this case, the ValueError comes from the 1-dimension chunks not
adding up (10 -> 15). I do have tests ensuring that None works as a dummy
for "unchanged", though I see now that I don't have a test like x.rechunk(((nan,
nan), (5, 5))), which should work, and x.rechunk(((nan,), (5, 5))), which
should fail. I'll add them now.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/pull/2251#discussion_r113441265, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AASszPGtJO4vLLpZuTK2EVBQn-SFHG18ks5rzzyggaJpZM4NGNg_
.

d7eaa90 should exclude unknown dimensions from any size calculations. I think that's our desired behavior, since we don't allow rechunking along the unknown dimension.

d7eaa90 should exclude unknown dimensions from any size calculations. I think that's our desired behavior, since we don't allow rechunking along the unknown dimension.

I don't think so, since intermediate results will include the unknown dimensions and their size therefore depends on the size of those dimensions.

I don't think so, since intermediate results will include the unknown dimensions and their size therefore depends on the size of those dimensions.

I see... Can we do any better than that while planning the rechunking, if we don't know the size of a chunk along an unknown dimension?

I see... Can we do any better than that while planning the rechunking, if we don't know the size of a chunk along an unknown dimension?

I don't think so. One radical solution would be to never create intermediates in the rechunking plan, another would be to disable the size limitation.

I don't think so. One radical solution would be to never create intermediates in the rechunking plan, another would be to disable the size limitation.

@mrocklin do you have a preference between these two? I'm leaning towards not having any intermediates, since what's the point of a block size limit parameter, if you can't actually respect it?

Not having any intermediates seems fine to me.
On Thu, Apr 27, 2017 at 8:32 AM, Tom Augspurger<EMAIL_ADDRESS>wrote:

I don't think so. One radical solution would be to never create
intermediates in the rechunking plan, another would be to disable the size
limitation.
@mrocklin https://github.com/mrocklin do you have a preference between
these two? I'm leaning towards not having any intermediates, since what's
the point of a block size limit parameter, if you can't actually respect it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/pull/2251#issuecomment-297699980, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AASszN5DiB4AuvwOsU4hbiHw9cF8pAwaks5r0IrOgaJpZM4NGNg_
.

@mrocklin all green. I think this is ready.

@pitrou any further concerns on this?
I will probably not go through the logic changes here personally.

OK to merge this?

Good on my end :)

@pitrou are you ok with this?


How to set multi accept content types

I use AFNetworking with swift
In my project, i hope AFNetworking can accept different kind of Content-Types
Here is my code:
  let manager = AFHTTPRequestOperationManager()

 // 1. use an array
 // let acceptTypes = ["text/plain", "text/html", "application/json", "audio/wav", "application/octet-stream"]
 // let headerSet = NSSet(array: acceptTypes)

 // 2. use objects
 let headerSet = NSSet(objects: "text/plain, text/html, application/json, audio/wav, application/octest-stream")

 manager.responseSerializer.acceptableContentTypes = headerSet
 //manager.Get(...)

both wrong!
I searched stackoverflow but still cannot find a solution.
who can tell me how to do that?

I am also facing this type of issue


Automate releasing of official packages

Close #1333
Review commit by commit.

Did a shallow pass only today, will take a proper look tomorrow.

Btw. have you also looked at https://github.com/changesets/action ? It does the PR opening and potentially NPM package releasing. I'm sorry for not giving the link sooner, but it just now came to my mind that I saw this thing being mentioned in the changeset docs...
I am fine with our own implementation though...

No worries, I knew about it :slightly_smiling_face: I decided against it mainly because it's just a CI action and I wanted a solution you can run locally as well. I could have used some of the code though...

I'd love to see this in action though. Maybe we could do a test release?

I'd leave it for v0.10. I don't really want to mess up the official API3 registry with random versions.


Multiple tag on same image with latest strategies will in loop update image

Hi,
I use Google Container Registry for hosting my docker images. When I tag my docker image with SHA1 tag and latest tag, argocd-image-updater found two tag for latest strategy image.
So it first updates the pod image with the tag SHA1 .... then it updates with the latest tag...
This operation is executed in a loop
To Reproduce
Steps to reproduce the behavior:
# Build with two tag
docker build -t eu.gcr.io/<gcp-project-id>/<image-name>:07bfd2596 -t eu.gcr.io/<gcp-project-id>/<image-name>:latest .

# Push image with two tag
docker push eu.gcr.io/<gcp-project-id>/<image-name>:07bfd2596
docker push eu.gcr.io/<gcp-project-id>/<image-name>:latest

Application YAM
apiVersion: argoproj.io/v1alpha1
...
    annotations:
    argocd-image-updater.argoproj.io/image-list: my_alias=eu.gcr.io/<gcp-project-id>/<image-name>
    argocd-image-updater.argoproj.io/my_alias.update-strategy: latest
....

Expected behavior
I think argocd-image-updater should be based on image digest for determine the really latest image.
Version
argocd-image-updater:0.8
Workaround
I use ignore_tags for explicitly ignoring latest tag
apiVersion: argoproj.io/v1alpha1
...
    annotations:
    argocd-image-updater.argoproj.io/image-list: my_alias=eu.gcr.io/<gcp-project-id>/<image-name>
    argocd-image-updater.argoproj.io/my_alias.update-strategy: latest
    argocd-image-updater.argoproj.io/my_alias.ignore-tags: latest
....

Logs
time="2021-01-27T16:51:24Z" level=debug msg="Cache hit for eu.gcr.io/<gcp-project-id>/<image-name>:07bfd2596"
time="2021-01-27T16:51:24Z" level=debug msg="Cache hit for eu.gcr.io/<gcp-project-id>/<image-name>:latest"
time="2021-01-27T16:51:24Z" level=debug msg="found 2 from 2 tags eligible for consideration" image="eu.gcr.io/<gcp-project-id>/<image-name>:07bfd2596"

I agree, this is an annoying behaviour and should be considered a bug.
Unfortunately, the manifests of the container images specify only the creation date - which in this case is the same for both tags, since they're aliases. With the latest update-strategy, it's always a good idea to make more restrictions on which images should be looked at for the update.
I think your suggestion using the image digest is pretty good, but we do not have information about the digest of the live image, because I think it's only available in the status of a particular application's workload (e.g. Deployment).
Let me think about a possible implementation for a while. I'm happy for additional ideas, too.

I agree, this is an annoying behaviour and should be considered a bug.
Unfortunately, the manifests of the container images specify only the creation date - which in this case is the same for both tags, since they're aliases. With the latest update-strategy, it's always a good idea to make more restrictions on which images should be looked at for the update.
I think your suggestion using the image digest is pretty good, but we do not have information about the digest of the live image, because I think it's only available in the status of a particular application's workload (e.g. Deployment).
Let me think about a possible implementation for a while. I'm happy for additional ideas, too.

Maybe argocd-image-updater can create a memory-map with {image-digest: ["label-1", "label-2"]}, and after selecting the latest image-digest, take the label in a consistent way (first/last after sorting).
My 2 cents.


add retry for describe-parameters.

The describe-parameters call would silently ignore failures. This commit will fix the issue by adding a retry when we bump into a ThrottlingException.

We have three instances each with 16 agents running knapsack build, on average around 7-9 of the agents will fail to retrieve the parameters because of this issue.


Inquiry: Intention of Timestamp structure

In pkg/volunteer/volunteer.go the Timestamp collected is being cast to a string
https://github.com/kubernetes-incubator/spartakus/blob/633430c4022c62dc1046682c7f3d3976eb783c60/pkg/volunteer/volunteer.go#L123
This is similarly defined in the schema pkg/database/bigquery.schema.json:
https://github.com/kubernetes-incubator/spartakus/blob/633430c4022c62dc1046682c7f3d3976eb783c60/pkg/database/bigquery.schema.json#L7-L11
As the service is primarily defined  to utilize BigQuery as a datastore it seems odd to utilize a string versus a TIMESTAMP (or even an INTEGER since BigQuery stores this as int64).
Was the use of String an intentional design decision?  What are the ramifications of changing this to a field of type Timestamp?

It was not intentional.  We can probably do it compatibly - add a new
field, have the server prefer the new field, and IFF the old field is
needed, parse it back to a timestamp?
On Wed, Nov 1, 2017 at 5:54 PM, redbeard<EMAIL_ADDRESS>wrote:

In pkg/volunteer/volunteer.go the Timestamp collected is being cast to a
string
https://github.com/kubernetes-incubator/spartakus/blob/
633430c4022c62dc1046682c7f3d3976eb783c60/pkg/volunteer/volunteer.go#L123
This is similarly defined in the schema pkg/database/bigquery.schema.json:
https://github.com/kubernetes-incubator/spartakus/blob/
633430c4022c62dc1046682c7f3d3976eb783c60/pkg/database/
bigquery.schema.json#L7-L11
As the service is primarily defined to utilize BigQuery as a datastore it
seems odd to utilize a string versus a TIMESTAMP (or even an INTEGER
since BigQuery stores this as int64).
Was the use of String an intentional design decision? What are the
ramifications of changing this to a field of type Timestamp?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/spartakus/issues/29, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFVgVBCXSGWQvn5N_AMvmsvsaFObDCwIks5syRLegaJpZM4QPBmw
.

That should likely work.  I first started exploring this a few weeks ago and took some notes on the BigQuery process.  I hadn't considered the process of just migrating to a new field though (which really is probably the correct answer).

@thockin this has been quite a while.  if i was to submit a PR to add the new field, would that work for you?


Proofs shouldn't include the Merkle root or the value being proven, as this is part of the statement being proven, not the proof

A Merkle proof is a proof for the statement "a key x has value y for the tree with root z". It doesn't make sense for the statement being proven to be a part of the proof, because the prover could always generate a valid proof if they get to pick the statement. Furthermore, the verifier may already know what the statement being proven is, so including it as part of the proof may be redundant. At minimum, they should already know what the root of the tree is.

See: https://github.com/lazyledger/smt/pull/5/files#r460376202

Also, independent from including leaf and root, it is unclear what the current Namespace Merkle Tree Proofs are supposed to prove:
https://github.com/lazyledger/lazyledger-specs/blob/master/specs/data_structures.md#namespace-merkle-tree-proofs
Do they correspond to a single leaf inclusion proof? (seems like it as there is a single index/key of a leaf).
My understanding is that we need to kind of proofs:

whole namespace proofs
single leaf proofs

Both can be implemented as range proofs.


Added the option to add more than one node (requires new config file)

You can now have multiple nodes, please configure them in the config file:
   local: {         devices: {             "warmtewinner": {                 ip: "<IP_ADDRESS>",                 eui64: "f105:00ff:0000:0001"             },             "plug_2": {                 ip: "<IP_ADDRESS>",                 eui64: "f105:00ff:0000:0002"             }         }     },

Allright, updated :)


docs: update enforcement page

that's weird, the netlify preview was not triggered! the only time we need this it's not triggered 🤔

Merged. Let's improve later if need be.


Improve tests

First commit created a lot of changes because of indentation. You can check the second one separately.


Clean up net.peer.{ip,port,name} attribute handling

Let's follow up on https://github.com/bufbuild/connect-opentelemetry-go/pull/37#issuecomment-1358073237. We shouldn't use the net.peer.ip attribute at all, and servers and clients should both emit net.peer.name and net.peer.port by default. This is high cardinality, but matches the OTel specification.
As @joshcarp notes on #37, the AttributeFilter option introduced in #41 lets handlers strip the client port and IP from metrics to reduce cardinality. This seems likely to be a common request, so we should export an option like WithLowerCardinality that does this automatically.

I think we should aim for defaults that avoid high cardinality metrics (without configuring AttributeFilter or specifying an option).
https://opentelemetry.io/docs/reference/specification/metrics/semantic_conventions/rpc-metrics/ has some more details on this, in particular:

To avoid high cardinality, implementations should prefer the most stable of net.peer.name or net.sock.peer.addr, depending on expected deployment profile. For many cloud applications, this is likely net.peer.name as names can be recycled even across re-instantiation of a server with a different ip.

For connect implementations, are we getting this value from the Host header?

For connect implementations, are we getting this value from the Host header?

For connect implementations the peer.Addr() is used to populate net.peer.ip(net.peer.name in #50) and net.peer.port
I would lean towards leaving out the high cardinality attributes by default, because most people are going to set it up without any options and this will lead to the least headache.
Either way the current implementation is the most correct,
I've got two commits on #50
4184c0b that replaces net.peer.ip for net.peer.name, and
3a10d2c that adds a WithLowerServerCardinality option

For now, I think we ought to follow the specification by default rather than inventing our own default behavior. In places where the spec is bad (like the cardinality problem we're discussing here), we should push users to make noise on the otel spec and hope we can fix the spec before this library hits 1.0.
In cases where we know the spec is bad (like this one), we should also ship a hopefully-temporary escape hatch. Hopefully we'll be able to delete these escape hatches before we release a 1.0 of this library.

Closed by #50


Refactor the Maven setup

With this the aot testsuite is running but, as expected, it fails.

Beautiful - this is way better (I wanted to merge the test infrastructure into a common test suite, but hadn't gotten that far yet).


For In-valid combination of Data no error show under View Companies(Agent panel)

Description of the bug
If we enter a valid company name(which is already in database and invalid account name which is not in database then after clicked on  search button the result of valid company sorted , no error show.
Steps to reproduce the behavior:

Go to 'https://www.pulseptt.com/agent.html'
Login with valid credential:- 1. User name: john  2. Password: 12345678
Navigate to Company Management.
Navigate to view Company list.
Enter company name:- infotech pvt. ltd (which is exist in database)
Enter Company Account Name:- Fdsaser  (which doesn't exist in database)
Click on Search Button.
See error.

Expected behavior
A error must show and Result shouldn't sorted in table.
Screenshots

Desktop
-OS: Windows 10
Browser :Version 100.0.4896.60 (Official Build) (64-bit)
Version [0.1.1]

This issue is still same.


test profile: miso_index failure

Description of the bug
MISO_INDEX runs and appears to create an output file "/index/genes.gff" (according to command.log), but the pipeline breaks with the below error.
Upon checking the work directory, there is only the log files; no ".gff".
Command used and terminal output
nextflow -c nextflow.config run nf-core/rnasplice -r dev -
profile test --outdir 's3://mdibl-jhfuqua/'

Aug-22 14:15:28.171 [Task monitor] ERROR nextflow.processor.TaskProcessor - Error executing process > 'NFCORE_RNASPLIC
E:RNASPLICE:VISUALISE_MISO:MISO_INDEX'

Caused by:
  Missing output file(s) `index` expected by process `NFCORE_RNASPLICE:RNASPLICE:VISUALISE_MISO:MISO_INDEX`

Command executed:

  index_gff --index genes_chrX_genes.gff3 index

  cat <<-END_VERSIONS > versions.yml
  "NFCORE_RNASPLICE:RNASPLICE:VISUALISE_MISO:MISO_INDEX":
      python: $(python --version | sed "s/Python //g")
      misopy: $(python -c "import pkg_resources; print(pkg_resources.get_distribution('misopy').version)")
  END_VERSIONS

Command exit status:
  0

Command output:
  (empty)

Relevant files
nextflow.log
command-2.log
System information
No response

Hi @heathfuqua
To replicate your issue I need to know if you made any chance to the nextflow.config file (I saw you passed it trough the -c option). In case you used a custom nextflow.config file please share it with me so I'll be able to replicate your configuration for the run.
Thank you

Great thank you.
Have you specified any specific containerization method (docker, conda, singularity) for the execution?

Could you try with '-profile test,docker' ?

Got the same error.

Hi, again. I just wanted to add that in the referenced work directory not only is there no .gff3 file, there is no /index, either. I'm not sure if this might help narrow down the possibilities, but thought I should mention it.

Jumping in here (I'm Heath's supervisor).  I found what seems to be the problem.  The MISO_INDEX process, defined in the local module "miso_index.nf" includes the directive "scratch false". After a bit of comparisons between various other modules, this seemed to be one difference, so seemed worth trying, so I deleted it.  With that deletion, the pipeline was able to find the output directory "index" and move it to the working directory and the process is now moving forward
As Heath noted above, we are running this using awsbatch as the executor, so perhaps this is specific to that.

The new error in MISO_SETTINGS appears to be a problem with the ext.args setting, which is specifying the two prefixes, --bam_prefix and --miso_prefix.
In each case, they are being set to a concatenation of two things- first my local directory where I am launching the nextflow process from, and second, the star_salmon subdirectory of the Publish directory.  I haven't found yet where this setting is being created, but it's identical for each of the two prefixes

Hi @heathfuqua @jhgraber
Thank you both for pointing out the issues.
Similar problems were highlighted in the issue #74 and #75 and we are still working on those to find a proper solution.
Keep you updated

Hello again.  I did work with this a bit further today.  You may already know this, but just in case, I have identified where the problem lies with sashimi_plot.  It's directly an issue of misopy, in that the miso_data files hard code the local path to the "pickle" files.  As far as I can tell, it's in the files that are found in "miso_data/[sampleID]/batch-genes/". (It's also in the batch-logs files, but I doubt that affects downstream steps.).
A typical line in the batch-genes files (named batch-0_genes.txt, batch-1_genes.txt, ...) looks like this:
ENSG00000102054 /tmp/nxf.XXXXLWuex4/index/chrX/ENSG00000102054.pickle
I don't see any obvious fixes in the command-line options to miso that would disable the use of the absolute path, however, I think that you might be able to get around it by globally deleting the prefixes of the form "/tmp/nxf.XXXXLWuex4/" from all of these files, so that it was instead looking for a relative path that started in index in the current directory.  That is how the pipeline currently places the index in the working machine on AWS (once I disabled the scratch option)

We have now submitted a PR #91 to the dev branch we believe will have fixed this issue and the related issue #89 . Essentially, we have created a script to change the absolute paths in the MISO data files to a relative path. Big thanks to @jhgraber for pointing us in the right direction. This also means we no longer have to use the scratch directory or copy the files into the working directory. Please could those interested test the PR code on their systems, both local and through your HPC/AWS environments would be great to make sure we catch all edge-cases. Notifying @dkoppstein as well as this may fix the issues opened by you previously.

We tried it again using the AWS execution engine, and unfortunately, it's still not working.  The specific error that stopped the process came in VISUALISE_MISO:MISO_SASHIMI, however when I went back into the process, it was clear that VISUALISE_MISO:MISO_RUN had also failed to execute properly.
I spent a little time reading through the .command.run files as well as some of the others, and my best guess so far is that it's an issue with the channels.  For example, the index directory is not being created as a directory, but is instead just a file.  When I compare the .command.run files from different runs, when MISO_RUN previously ran correctly, the channel was leading to an S3 download statement:
downloads+=("nxf_s3_download s3://mdibl-nextflow-work/jhgraber/rnasplice/3a/46a2e1dba62bc98c2b662b360ecf18/index index")
In contrast, int the run that just failed, the equivalent set up was for a symbolic link (which would definitely not work in the AWS environment):
ln -s /mdibl-nextflow-work/jhfuqua/rna_splice_test/ae/2e9df2bb10ce05289025b6c51be3ab/index index
That seems to indicate to me an issue with the channel being connected from MISO_INDEX to MISO_RUN and MISO_SASHIMI.
One more issue though, as well- the exact error that came out was this:
IOError: [Errno 2] could not open alignment file ./ERR204916_sorted.bam: No such file or directory`, size: 1580 (max: 255)
Which seems to indicate that the bam files should be provided to MISO_SASHIMI module, but as far as I can tell from looking at the VISUALIZE_MISO subworkflow, the bam channel isn't being connected into MISO_SASHIMI.
I hope this is helpful.

That's disappointing. Could you provide the logs for us to inspect, either on here or direct message on the Slack channel if they contain any private information. Could I also confirm you are running the PR code? For example, you mention that the MISO_SASHIMI module requires a bam channel, but if you look at the PR code for that module and sub workflow you can see we added a ch_bam_bai channel. See #91 code for subworkflows/local/visualise_miso.nf and modules/local/miso_sashimi.nf

Ok. I didn't notice that the PR hadn't yet been accepted to the Dev branch, so my last run didn't reflect the changes in that PR. Will clone the PR and run that.

Good news. After running the latest PR, the pipeline completed without errors.
Thanks for your help.

That’s great news, I will leave the issue open until @jhgraber reports back as well.

All good here- My comments above were with regard to Heath's run of the data. He has confirmed both that it ran without errors and also that it produced MISO output.  That's great news.  Thanks for getting it updated so quickly!


PoC Mobile app

For now using Ionic's https://CapacitorJS.com
Still to do:

[ ] Make links to attachments work
[ ] Initial space index?

Implemented, not live yet.


Fix bug with StreamProcessor::stream_lock

antecedent/patchwork's StreamProcessor contains bug explained here https://github.com/antecedent/patchwork/issues/27

Hi @aleksandrlat , you should fix the code to make it pass the tests in order to make it "mergeable", or fix the tests if you think that they're incorrect.
Kind regards and thank you for your time and effort :) .

Hi again @aleksandrlat , it seems that the broken tests are broken because an external case, I'll review it in a couple of days.
Sorry for the inconvenience.

Hello @castarco
How is it going? Can I help you with problem identification? Because I see problem is not in my changes.

Can this be fixed/merged? I just ran into this bug as well...

@devartbvba You could fork the project, and apply the fix yourself :) That's what I've done.

@aleksandrlat sorry for the delay, could you please rebase/update the PR to check if the tests are passing?

@aleksandrlat are you still willing to work on this? Thank you!


Gradle tests Liberty, Payara, Helidon [WIP]

Gradle:
Removes Tomee and Wildfly and Quarkus until properly implemented in Starter.
Adds tests for Helidon, Payara and Liberty.

All Liberty tests are failing for me now due to ports already in use...
[ERROR   ] CWWKO0221E: TCP Channel defaultHttpEndpoint initialization did not succeed.  The socket bind did not succeed for host localhost and port 9081.  The port might already be in use.  Exception Message:

[ERROR   ] CWWKO0221E: TCP Channel defaultHttpEndpoint-ssl initialization did not succeed.  The socket bind did not succeed for host localhost and port 9444.  The port might already be in use.  Exception

[ERROR   ] CWWKO0221E: TCP Channel defaultHttpEndpoint initialization did not succeed.  The socket bind did not succeed for host localhost and port 9080.  The port might already be in use.  Exception Message: Address already in use

[ERROR   ] CWWKO0221E: TCP Channel defaultHttpEndpoint-ssl initialization did not succeed.  The socket bind did not succeed for host localhost and port 9443.  The port might already be in use.  Exception Message: Address already in use

Not sure what brought that in. Apparently port shift for service-b does not work?

The problem is Liberty + Gradle.  Ctrl+C simply does not terminate it. Servers keep running in the background, occupying ports :-(

JWT on Liberty fails when built and ran with Gradle:

[AUDIT   ] CWWKF0011I: The defaultServer server is ready to run a smarter planet. The defaultServer server started in 7.795 seconds.
[ERROR   ] CWWKS5524E: The MicroProfile JWT feature encountered an error while creating a JWT by using the [jwtUserConsumer] configuration and the token included in the request. CWWKS6031E: The JSON Web Token (JWT) consumer [jwtUserConsumer] cannot process the token string. CWWKS6022E: The issuer [https://server.example.com] of the provided JSON web token (JWT) is not listed as a trusted issuer in the [jwtUserConsumer] JWT configuration. The trusted issuers are [${jwt.issuer}].

Definitley ${jwt.issuer} looks suspicious...

@Emily-Jiang  I tried
ext  {
    liberty.server.var.'default.http.port' = '9081'
    liberty.server.var.'project.name' = projectName
    liberty.server.var.'app.context.root' = '/'
    liberty.server.var.'jwt.issuer' = 'https://server.example.com'
}

and it didn't help to propagate it to  https://github.com/eclipse/microprofile-starter/blob/master/src/main/resources/files/liberty/server.xml.tpl#L28 and my Liberty x Gradle support kinda ends here :-)  I would like you to take a look and help, if you may.

@Karm for the ctl+c issue, can you issue gradlew libertyStop to stop the server?

@Emily-Jiang I tried
ext  {
    liberty.server.var.'default.http.port' = '9081'
    liberty.server.var.'project.name' = projectName
    liberty.server.var.'app.context.root' = '/'
    liberty.server.var.'jwt.issuer' = 'https://server.example.com'
}

and it didn't help to propagate it to https://github.com/eclipse/microprofile-starter/blob/master/src/main/resources/files/liberty/server.xml.tpl#L28 and my Liberty x Gradle support kinda ends here :-) I would like you to take a look and help, if you may.

I tried and it does work.

https://github.com/eclipse/microprofile-starter/pull/429 is to fix service-b

@Emily-Jiang  Any idea how to stop Liberty so as  org.gradle.launcher.daemon.bootstrap.GradleDaemon process stops too?
The test suite has to forcibly kill those processes now.
How do you do it locally?  (it's reproducible locally without TS too)

Do you mean that you could not do gradlew libertyStop?

It looks ./gradlew libertyStop did it.
Let the tests run...

@Emily-Jiang Any idea how to stop Liberty so as org.gradle.launcher.daemon.bootstrap.GradleDaemon process stops too?
The test suite has to forcibly kill those processes now.
How do you do it locally? (it's reproducible locally without TS too)

I talked with the Open Liberty team who owns the gradle plugin and confirmed this is a known issue. The current workaround is to use gradlew libertyStop or killing the process manually.


Taiwan data hasn't been updated in 9 ays

Describe the bug
Taiwan's COVID data hasn't been updated since 4/15.
Link to microCOVID scenario
If applicable, please copy-paste the URL to the scenario that you modeled on the calculator, so we can easily reproduce it.

To Reproduce
Steps to reproduce the behavior:

Go to Step 1
Select Taiwan
See last updated 4/15/2022

Expected behavior
See last updated 4/24/2022 or at least something more recent than 4/15
Is this a regression?
Probably
Additional context / screenshots

I've also noticed this for my region (California). It looks like automatic prevalence updates stopped on 4/16 (search PRs with is:pr label:auto-prevalence-update), so every region should be affected by this.

Presumably fixed by https://github.com/microCOVID/microCOVID/pull/1450.  Please file separate issues if you see any continuing issues.


Plaing Button inside list item produces callstack overflow

Describe the bug
Placing Button inside list item makes Avalonia code go infinite recursion. Sometimes, tweaking some Button properties (e.g., Content) is needed to trigger this - I failed to find any correlation, why sometimes things do work.
Both ItemsControl and ListBox give the same result; I didn't check other item containers.
To Reproduce
Minimal XAML code I've came up with, that always fail when used inside empty VS 2022 Avalonia project:
<ItemsControl>
	<ItemsControl.Items>Foo</ItemsControl.Items>
	<ItemsControl.DataTemplates>
		<DataTemplate>
			<Button>Bar</Button>
		</DataTemplate>
	</ItemsControl.DataTemplates>
</ItemsControl>

Expected behavior
No stack overflow.
Screenshots
No need.
Desktop

OS: Windows 10
Version 0.10.12; installing 0.10.13 (latest pre-release from NuGet) doesn't change anything

Additional context
I've made an excerpt from "Avalonia Diagnostics" output window, after viewer process crash. Running my own built program leads to crash with a similar stack trace.

You are using DataTemplate without specifying data type, and put it in DataTemplates. Button will also read same DataTemplates collection to get a template for its own content (Bar). What will create a button inside of a button...inside of a button...
You need to either specify DataType, or use ItemTemplate. ItemTemplate will be used strictly in the items presenter.

Argh. Coming from WPF land, still doing silly mistakes... Sorry, and thank you for the answer very much!

It was restricted with https://github.com/AvaloniaUI/Avalonia/pull/8221 and not allowed anymore.


Multiple IP adresses: no ASN so no proper balancing

When connecting from mobile devices mirrorbits 'sees' two external IP's for the device, and is unable to select an ASN. The result is that the client does not receive a download at optimal speed.
For example: http://up.kibje.com/20150803/Screenshot_2015-08-03-17-27-09.png
I have IP's <IP_ADDRESS> (ASN8608) and <IP_ADDRESS> (ASN15169)
For mobile the first address almost always corresponds to the location-defining IP of the client. In my case when I am on WLAN I get the proxy of my location, when I am not on WLAN I get the proxy address of my mobile phone provider.
The second IP address is caused by mobile browser optimization services (eg Google / Akamai / Apple) which most phone manufacturers are using on their OS's these days. They can also be caused by webpage filtering software but that is less common.
In my opinion the first address should always be selected if two or more addresses are available.

In the current implementation, the X-Forwarded-For header is expected to contain only one IP address. How were you able to get two?

In my opinion the first address should always be selected if two or more addresses are available.

The first is the "real" user's location but since we need to feed the proxy instead, shouldn't we use the last one? In case of a browser optimization services then it's probably best to use the first, since binary files will probably not go through the proxy.

I'll leave that design choice op to you, but picking either is likely better than none.


[SDK][INFINITY-1032] Add VolumePathCannotBeEmpty validator

@NotEmpty does not detect blank string

@NotBlank works
We should also have @Pattern


Macro error with actix-web plugin (could not find proc_macro2 in `proc_macro_error)

I'm trying to generate swagger spec using https://paperclip.waffles.space/actix-plugin.html example, but I get the following error:
   --> /home/s/.cargo/registry/src/github.com-1ecc6299db9ec823/paperclip-macros-0.3.0/src/actix.rs:400:66
    |
400 |     fn quote_option(value: Option<&String>) -> proc_macro_error::proc_macro2::TokenStream {
    |                                                                  ^^^^^^^^^^^ could not find `proc_macro2` in `proc_macro_error`

I can show my code, but it is very close to the example.

Commit https://github.com/wafflespeanut/paperclip/commit/addcf7a9abef3627f9e1cf236559f573d2f6c88d should fix this. I'll close this after releasing another minor version.

Minor version has been released.

Thanks!


Update ramsey/uuid from 3 to 4 to avoid conflicts with Laravel 7

Poblem
When requiring the cloudcreativity/laravel-json-api (2.0.0-beta.1) from a fresh installation of Laravel 7 I'm getting the next error:
Problem 1
    - Installation request for cloudcreativity/laravel-json-api 2.0.0-beta.1 -> satisfiable by cloudcreativity/laravel-json-api[v2.0.0-beta.1].
    - Conclusion: remove ramsey/uuid 4.0.1
    - Conclusion: don't install ramsey/uuid 4.0.1
    - cloudcreativity/laravel-json-api v2.0.0-beta.1 requires ramsey/uuid ^3.0 -> satisfiable by ramsey/uuid[3.0.0, 3.0.0-alpha1, 3.0.0-alpha2, 3.0.0-alpha3, 3.0.0-beta1, 3.0.1, 3.1.0, 3.2.0, 3.3.0, 3.4.0, 3.4.1, 3.5.0, 3.5.1, 3.5.2, 3.6.0, 3.6.1, 3.7.0, 3.7.1, 3.7.2, 3.7.3, 3.8.0, 3.9.0, 3.9.1, 3.9.2, 3.9.3, 3.x-dev].
    - Can only install one of: ramsey/uuid[3.7.0, 4.0.1].
    - Can only install one of: ramsey/uuid[3.7.1, 4.0.1].
    - Can only install one of: ramsey/uuid[3.7.2, 4.0.1].
    - Can only install one of: ramsey/uuid[3.7.3, 4.0.1].
    - Can only install one of: ramsey/uuid[3.8.0, 4.0.1].
    - Can only install one of: ramsey/uuid[3.9.0, 4.0.1].
    - Can only install one of: ramsey/uuid[3.9.1, 4.0.1].
    - Can only install one of: ramsey/uuid[3.9.2, 4.0.1].
    - Can only install one of: ramsey/uuid[3.9.3, 4.0.1].
    - Can only install one of: ramsey/uuid[3.x-dev, 4.0.1].
    - Can only install one of: ramsey/uuid[3.0.0, 4.0.1].
    - Can only install one of: ramsey/uuid[3.0.0-alpha1, 4.0.1].
    - Can only install one of: ramsey/uuid[3.0.0-alpha2, 4.0.1].
    - Can only install one of: ramsey/uuid[3.0.0-alpha3, 4.0.1].
    - Can only install one of: ramsey/uuid[3.0.0-beta1, 4.0.1].
    - Can only install one of: ramsey/uuid[3.0.1, 4.0.1].
    - Can only install one of: ramsey/uuid[3.1.0, 4.0.1].
    - Can only install one of: ramsey/uuid[3.2.0, 4.0.1].
    - Can only install one of: ramsey/uuid[3.3.0, 4.0.1].
    - Can only install one of: ramsey/uuid[3.4.0, 4.0.1].
    - Can only install one of: ramsey/uuid[3.4.1, 4.0.1].
    - Can only install one of: ramsey/uuid[3.5.0, 4.0.1].
    - Can only install one of: ramsey/uuid[3.5.1, 4.0.1].
    - Can only install one of: ramsey/uuid[3.5.2, 4.0.1].
    - Can only install one of: ramsey/uuid[3.6.0, 4.0.1].
    - Can only install one of: ramsey/uuid[3.6.1, 4.0.1].
    - Installation request for ramsey/uuid (locked at 4.0.1) -> satisfiable by ramsey/uuid[4.0.1].

Installation failed, reverting ./composer.json to its original content.

Solution
I upgraded the ramsey/uuid from 3 to 4, and now it's working on a fresh install of Laravel 7

Hi! Thanks for submitting this as I wasn't aware that Laravel had changed the UUID version. I'm not going to merge this PR as I'd prefer the UUID dependency to be ^3.0|^4.0 seeing as this package does actually work with v3 of the UUID package.
I thought it would just be easier for me to make that change myself, rather than merge this PR. It will  be in the next release (which is 2.0.0-beta.2).


Add test for LeanRestartFile mapping

This is the test for #357 . It passes in the sense that
just retest spec/mappings_spec.lua

returns 0, and I can manage to fail it too.
But it's mostly a dummy test, checking the key mapping is set, but I don't really know how to check if it can restart file.
So, feel free to close without merging.
Also, I can't pass all existing tests locally, some of them are failing without modifications, the log file is attached.
just-test.log

Thanks! Yeah writing a test for the actual restart functionality is a bit trickier, though should still be doable, it's been on my list of "known missing tests". No harm merging this I suppose.

Also, I can't pass all existing tests locally, some of them are failing without modifications, the log file is attached.

Are you on nightly? There's some flakiness in the tests which seems to only manifest on nightly. If you run the suite a few times, does it pass any of them?

Not really, I'm on nvim v 0.10.20.


Enhance slide panel to hide off screen content when closed

Issue Description
Set hidden styles on the slide panel to prevent tab focus from component off of the screen.
Issue Type

[ ] New Feature
[x] Enhancement
[ ] Bug
[ ] Other

Expected Behavior
When the value for isOpen is set to false, the content inside the slide panel should not be focusable, so hidden styles should be applied to the whole panel.

Duplicate issue: https://github.com/cerner/terra-core/issues/1192

Resolved in #1228


StandardShadow doesn't work on older Android versions

Hey @thunderbiscuit, I'm Bhuvan Ade. A UI/UX Designer Can I please work on this issue?

Hi @BhuvanAde. You are more than welcome to investigate, but I do think that it's a rather technical issue related to the Compose compiler and compatibility with older Android APIs. If you are an UI/UX designer, I'm not sure this issue is the perfect fit for you. I also didn't put any extra comment there, so I do wonder if maybe you thought it was something else than what the bug actually is. Let me know if you want more explanations.

@thunderbiscuit Please let me know if there are any issues related to UI/UX. I would love to do that!

At the moment there isn't much, as I'm sort of repositioning the project towards cleaning up some technical debt and preparing for the 1.0 release. You can keep an eye on the issues I tagged for the 1.0 milestone here. There isn't much, but hopefully we add a few as bug reports come in!
If you'd like to try the latest version in the Play Store and play around with it, you can also open up issues on the repo with small UI issues and suggestions (for example I'm not sure how the app looks on very small screens or very large ones, so if you have access to that you could share screenshots of UI breaks if there are any).

standardShadow is an extension function that is based on advancedShadow modifier right?

I am not able to figure out the expected and actual behavior ( I am on Android 11). Here is what I can see from Cancel button that seems to use standardShadow


🐛 Bug Report: TechDocsDocument should be in common package

📜 Description
https://github.com/backstage/backstage/blob/master/plugins/techdocs-node/src/techdocsTypes.ts#L23 is now in node plugin and not usable in the frontend
👍 Expected behavior
TechDocsDocument should be moved to techdocs-common plugin
👎 Actual Behavior with Screenshots
Cannot import TechDocsDocument in app as it is node plugin
👟 Reproduction steps
Try to use TechDocsDocument in app
📃 Provide the context for the Bug.
No response
🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

did you consider using TechDocsEntityMetadata in react?

Well, it's not the same thing. When doing customization of search results, you need the type that extends IndexableDocument to access the fields. Just like CatalogEntityDocument.

There is no techdocs-common plugin. A fast fix would be to dulicate the code of TechDocsDocument inside techdocs-react plugin

Or just make it properly and create techdocs-common plugin and deprecate the TechDocsDocument from the node plugin

I am wondering if there is any reason of why there is not yet present a techdocs-common plugin

@drodil Are you up for this?

Not stale


Add authentication attributes on resource password grant type

Backport of: https://github.com/apereo/cas/pull/5524

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


Server tests for context images for 2D tasks

Related to https://github.com/openvinotoolkit/cvat/pull/3122
Motivation and context

How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[ ] I have updated the license header for each file (see an example below)

# Copyright (C) 2021 Intel Corporation
#
# SPDX-License-Identifier: MIT

Why these tests are here? I don't see relations with dataset_manager functionality.

Moved to engine/tests.


API docs: replace @example with @source + inlined code

Here is an example from the staged site: NgStyle.
Contributes to https://github.com/dart-lang/site-webdev/issues/338
Note that @example directives that referred to .ts code have been written as {@disabled-source ...} entries. These will be converted to proper @source entries in a follow-up commit.
cc @kwalrath @matanlurey @thso @kevmoo

@chalin to be clear: do you want this merged or no?
Please update the title if this is just  work-in-progress (WIP)

@kevmoo: This is ready for review and merge, though I now see that Travis is reporting errors, so I'll look into that. But I recall Kathy telling me that there were some issues with Travis?

i'll attempt a merge now

I see that master has the same errors as this PR, so as I mentioned before, it is ready for review and merge.

Should we be using labels like "State: merged internally" (or maybe a new one, "State: merged" for stuff that's already visible externally)?

What do you mean "visible"?
I just use those for tracking as-yet synced pull requests.
If they exist on closed PR, I'm not concerned...
On Thu, Feb 9, 2017 at 10:51 AM, Kathy Walrath<EMAIL_ADDRESS>wrote:

Should we be using labels like "State: merged internally" (or maybe a new
one, "State: merged" for stuff that's already visible externally)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/angular2/pull/270#issuecomment-278736103,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABCirMnXa_8Jimn8i0IxhDg-9Dazz4cks5ra2AagaJpZM4L7Q9p
.

Somebody looking at these PRs might think that they weren't merged. But they were. So I thought it might be nice to have a label saying what the merge state is.
We already have (but didn't use for this PR) a label (State: merged internally) for stuff that's merged in our internal repo but perhaps not yet merged to the GitHub repo. I was also wondering whether we wanted a label for stuff that had made it to the external repo, although I suspect we might forget to update it.

ferhatb closed this in 99a8816 6 days ago

This is the key thing, I think. We could always go through and clean-up the labels and add the "really merged to github" -- if one were to think that was important :smile:


90 make poster from website page

@caffiendcode Can you check this branch out and have a poke around to:

see that nothing is broken - I've messed with how individual film pages are constructed - mostly adding css classes but a a bit of re-arranging. I've also removed br tags as we can apply space with css - and other files have been tweaked as part of that task.
Upcoming films should now fit an A4 page if printing from the browser. (old films probably look naff if you try this)

If you're happy, please merge.
If you haven't reviewed by Tuesday 10th Jan. I'll probably merge this and we can then worry about bugs later!

Goona merge this so we can use it and worry about broken stuff later!


Calculating information content from different datasets

Hello,
I have been using pyHPO to calculate the similarity scores between patients within a dataset using their clinical phenotype lists as HPOSets. ie - HPOSet1.similarity(HPOSet2)
However, I am worried my analyses may be skewed because pyHPO calculates the information contents used in the scoring algorithms based on  the "kind" parameter - OMIM, orpha, decipher, or gene. I am wondering if there is any way to create a "custom kind" of sorts so that my patients' similarity scores are calculated using information contents derived from my dataset of choice instead of these publicly available ones?
Any feedback would be greatly appreciated. Thanks!

Hi,
At the moment PyHPO does not support custom information_content values. But that would be a good feature to add, doesn't seem too difficult.
In the meantime, you could write your own Similarity method (see the example here: https://centogene.github.io/pyhpo/similarity.html).
Alternatively, you could take a hacky approach and overwrite one of the existing information_content in every term. So, you could do something like this:
from pyhpo import Ontology
_ = Ontology()
for term in Ontology:
    term.information_content.decipher = my_ic_calculating_function(term)

...
HPOSet1.similarity(HPOSet2, kind='decipher')

Dear @icooperstein,
We have now released v3.1.2 for PyHPO, which allows adding custom information content to each HPO term. Thanks for the feature suggestion.
You can check here for a brief documentation:
https://centogene.github.io/pyhpo/hpoterm.html#set-custom
I hope PyHPO continues to be useful for your research.


Get-ChildItem autocompletion stops to work when -r is used

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
Type Get-ChildItem C:\ (or gci C:\, or ls C:\) and press Tab. You'll get some autocompletion.
Type Get-ChildItem -Recurse C:\ (or gci -Recurse C:\, or ls -Recurse C:\) and press Tab. You'll get some autocompletion.
Type Get-ChildItem -r C:\ (or gci -r C:\, or ls -r C:\) and press Tab. You won't get any autocompletion.
(But that's very low-priority thing.)
Expected behavior
PS> # Press Tab key after typing '\' instead of Enter:
PS> gci -r C:\

PS> # I expect to get something like:
PS> gci -r 'C:\$Recycle.Bin\'

Actual behavior
PS> # Press Tab key after typing '\' instead of Enter:
PS> gci -r C:\

PS> # I actually get nothing more than:
PS> gci -r C:\

Error details
No response
Environment data
PS> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.1.4
PSEdition                      Core
GitCommitId                    7.1.4
OS                             Microsoft Windows 10.0.19043
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
No response

FWIW, if you use -s instead of -r you get proper tab completion

The Working Group has reviewed this issue.  In the case of -r, and why it binds to -recurse instead of -ReadOnly, we are investigating a possible bug in Tab completion.

I suppose, that binding -r to -ReadOnly is intentional and useful. (PowerShell's ls -R should work similarly to classic ls -R, as well as rm -r should work similarly to classic rm -R. Full compatibility is impossible, but compatibility in basic things is useful.)

Alias for Recurse is "s" and it is not clear why -r works as -Recurse.
I tried some switch parameters in other cmdlets and not found such weird behaviour.

This is an interesting one as PowerShell not only allows you to be lazy with parameter aliases, it also allows you to be lazy in a number of different ways too, some that only make sense when you understand how the engine will decide what to run.
Also this particular cmdlet changes how it can work depending on what provider you are working with, so you'll get different results in FileSystem vs Registry for example.
One may think, and unfortunately would be wrong that if calling Get-ChildItem -r when in a filesystem provider would then look alphabetically, as that's a logical view.
This would mean that the parameter called would be ReadOnly not Recurse.
However whilst PowerShell has Parameter Positioning (which actually isn't enforced on Recurse), and could have been why Recurse come up as the intended parameter, I think that because Recurse is a base parameter of Get-ChildItem, it will always be preferential to any additional parameters that are added by the provider it is working with, like ReadOnly in the FileSystem Provider and that's because that is how the author of the cmdlet designed it. Therefore @theJasonHelmick I don't think that this is an issue for Tab Completion at all as I strongly believe that this is working entirely as designed.

When you run Get-ChildItem -r it will interpret it as the Recurse switch parameter. However, if you use the tab autocompetition it suggests $true and $false.

If you then run Get-ChildItem -r $true or Get-ChildItem -r $false you get no results, even if Get-ChildItem -Recurse or Get-ChildItem -r would typically return something.
If you navigate to a file which is ReadOnly (In my situation I ran Get-ChildItem C:\Windows -Recurse | where isReadOnly -eq true and found "C:\Windows\Globalization\ICU\icudtl.dat" was a read only file) and run Get-ChildItem -Readonly I get the file return. However, if I run Get-Childitem -r $true and Get-Childitem -r $false I still get no results.
Unfortunately that's as far as I could get but hope it helps!

This only happens in the FileSystem Provider and not in say the Registry provider in my limited testing

@kilasuit - Makes perfect sense and thank you!


Initial work for PRPL

Render contentOnly templates
Fetch only the content of the page from client

@andreban I plan to merge and keep working on another PR.


Osb Domain Creation fails because of connection problems

I'm using Oracle <IP_ADDRESS> Enterprise and OracleSOASuite <IP_ADDRESS>
After succesfully executing RCU, OSB domain creation fails with following error:
createDomain.py called with the following inputs:
INFO: sys.argv[0] = /u01/oracle/dockertools/createDomain.py
INFO: sys.argv[1] = -oh
INFO: sys.argv[2] = /u01/oracle
INFO: sys.argv[3] = -jh
INFO: sys.argv[4] = /usr/java/default
INFO: sys.argv[5] = -parent
INFO: sys.argv[6] = /u01/oracle/user_projects/domains
INFO: sys.argv[7] = -name
INFO: sys.argv[8] = soainfra
INFO: sys.argv[9] = -password
INFO: sys.argv[10] = start123
INFO: sys.argv[11] = -rcuDb
INFO: sys.argv[12] = oracleDb:1521/soapdb
INFO: sys.argv[13] = -rcuPrefix
INFO: sys.argv[14] = OSB01
INFO: sys.argv[15] = -rcuSchemaPwd
INFO: sys.argv[16] = start123
INFO: sys.argv[17] = -domainType
INFO: sys.argv[18] = osb
INFO: Creating Node Managers...
INFO: Creating Admin server...
INFO: Creating OSB cluster...
INFO: OSB Servers created.....
INFO: Writing base domain...
INFO: Base domain created at /u01/oracle/user_projects/domains/soainfra
INFO: Extending domain at /u01/oracle/user_projects/domains/soainfra
INFO: Applying JRF templates...
INFO: Applying OSB templates...
INFO: Extension Templates added
INFO: Configuring the Service Table DataSource...
INFO: Getting Database Defaults...
Error: getDatabaseDefaults() failed. Do dumpStack() to see details.
Error: runCmd() failed. Do dumpStack() to see details.
Problem invoking WLST - Traceback (innermost last):
File "/u01/oracle/dockertools/createDomain.py", line 483, in ?
File "/u01/oracle/dockertools/createDomain.py", line 118, in createDomain
File "/u01/oracle/dockertools/createDomain.py", line 312, in extendOsbDomain
File "/u01/oracle/dockertools/createDomain.py", line 237, in configureJDBCTemplates
File "/tmp/WLSTOfflineIni4641236230965879151.py", line 263, in getDatabaseDefaults
File "/tmp/WLSTOfflineIni4641236230965879151.py", line 19, in command
Failed to build JDBC Connection object:
at com.oracle.cie.domain.script.jython.CommandExceptionHandler.handleException(CommandExceptionHandler.java:69)
at com.oracle.cie.domain.script.jython.WLScriptContext.handleException(WLScriptContext.java:2983)
at com.oracle.cie.domain.script.jython.WLScriptContext.runCmd(WLScriptContext.java:735)
at sun.reflect.GeneratedMethodAccessor155.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
com.oracle.cie.domain.script.jython.WLSTException: com.oracle.cie.domain.script.jython.WLSTException: Got exception when auto configuring the schema component(s) with data obtained from shadow table:
Failed to build JDBC Connection object:
ERROR: Domain Configuration failed. Please check the logs
This is the corresponding Database log:
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for Linux: Version <IP_ADDRESS>.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version <IP_ADDRESS>.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version <IP_ADDRESS>.0 - Production
Time: 16-APR-2019 10:05:25
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12606
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=host)(PORT=port))
2019-04-16T10:05:25.682722+00:00
SOAPDB(3):WARNING: inbound connection timed out (ORA-3136)
It seems to be an issue with the Database connection (maybe authentication?)
The Database is visible in the Docker Network and can be pinged from the OracleSuit container.
My setenv.sh file:
#!/bin/sh
export DC_USERHOME=/home/comdev/tobi/docker
export DC_REGISTRY_SOA=localhost
export DC_REGISTRY_DB=localhost
exportComposeEnv() {
export DC_HOSTNAME=localhost
export DC_ORCL_PORT=1521
export DC_ORCL_OEM_PORT=5500
export DC_ORCL_SID=soadb
export DC_ORCL_PDB=soapdb
export DC_ORCL_SYSPWD=start123
export DC_ORCL_HOST=oracleDb
export DC_ORCL_DBDATA=${DC_USERHOME}/dbdata
export DC_ADMIN_PWD=start123
export DC_RCU_SCHPWD=start123
export DC_RCU_SOAPFX=SOA01
export DC_RCU_BPMPFX=BPM01
export DC_RCU_OSBPFX=OSB01
export DC_DDIR_SOA=${DC_USERHOME}/soadomain
export DC_DDIR_BPM=${DC_USERHOME}/bpmdomain
export DC_DDIR_OSB=${DC_USERHOME}/osbdomain
export DC_SOA_VERSION=<IP_ADDRESS>
}
#===============================================
createDirs() {
mkdir -p ${DC_ORCL_DBDATA} ${DC_DDIR_SOA} ${DC_DDIR_BPM} ${DC_DDIR_OSB}
chmod 777 ${DC_ORCL_DBDATA} ${DC_DDIR_SOA} ${DC_DDIR_BPM} ${DC_DDIR_OSB}
}
#===============================================
#== MAIN starts here
#===============================================

echo "INFO: Setting up SOA Docker Environment..."
exportComposeEnv
createDirs
#echo "INFO: Environment variables"
#env | grep -e "DC_" | sort
My Database docker-compose service:
soadb:
image: oracle/database:<IP_ADDRESS>-ee
ports:
  - "${DC_ORCL_PORT}:1521"
  - "${DC_ORCL_OEM_PORT}:5500"
environment:
  - ORACLE_SID=${DC_ORCL_SID}
  - ORACLE_PDB=${DC_ORCL_PDB}
  - ORACLE_PWD=${DC_ORCL_SYSPWD}
container_name: soadb
volumes:
  - ${DC_ORCL_DBDATA}:/opt/oracle/oradata
networks:
  default:
    aliases:
      - oracleDb

My Oracle Suite Docker-compose service:
osbas:
image: ${DC_REGISTRY_SOA}/oracle/soasuite:${DC_SOA_VERSION}
container_name: osbas
command: /bin/bash -c "sleep 5s; /u01/oracle/dockertools/createDomainAndStart.sh"
env_file:
- ../setenv.sh
ports:
- "7001:7001"
#entrypoint: tail -f /dev/null
environment:
- DOMAIN_TYPE=osb
- ADMIN_HOST=${DC_HOSTNAME}
- ADMIN_PASSWORD=${DC_ADMIN_PWD}
- CONNECTION_STRING=${DC_ORCL_HOST}:${DC_ORCL_PORT}/${DC_ORCL_PDB}
- DB_PASSWORD=${DC_ORCL_SYSPWD}
- DB_SCHEMA_PASSWORD=${DC_RCU_SCHPWD}
- RCUPREFIX=${DC_RCU_OSBPFX}
- MANAGED_SERVER=osb_server1
volumes:
- ${DC_DDIR_OSB}:/u01/oracle/user_projects
I'm also able to connect to the DB from Oracle Suite container using sqlplus:
/sqlplus sys/start123@//oracleDb:1521/soadb as sysdba
So maybe something is wrong how the configureJDBCTemplates(self,db,dbPrefix,dbPassword) within the createDomain.py script is setting up the DB connection
Any help would be really appreciated.

Based on database error seen in this issue "SOAPDB(3):WARNING: inbound connection timed out (ORA-3136)", I'm suspecting there could be some memory issue/space issue.
Reference : https://www.stechies.com/oracle-sql-warning-inbound-connection-timed-out-ora3136/
"It is always possible that if the DB system is undersized as regards memory, and is using a lot of SWAP, then this might affect the way that the system is able to respond do the TCP comms layer, but that would be
unusual I think.
The fact that it is an INBOUND timeout might point to a sluggish system, but it might be some other factor (e.g. looping Java processes hogging the system in some way)."
Can you pls check the machine details where your DB container is running?

Exaclty same issue here, not being able to use Oracle SOA Suite image because of this error.

I have the same problem!

Hi folks.
In my case, the problems were with the OracleDB container. Because of unknown reasons, every time I got the error above, I got the error below too:
***********************************************************************

Fatal NI connect error 12170.

  VERSION INFORMATION:
    TNS for Linux: Version <IP_ADDRESS>.0 - Production
    Oracle Bequeath NT Protocol Adapter for Linux: Version <IP_ADDRESS>.0 - Production
    TCP/IP NT Protocol Adapter for Linux: Version <IP_ADDRESS>.0 - Production
  Time: 18-JUN-2019 01:05:41
  Tracing not turned on.
  Tns error struct:
    ns main err code: 12535

TNS-12535: TNS:operation timed out
    ns secondary err code: 12606
    nt main err code: 0
    nt secondary err code: 0
    nt OS err code: 0
  Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=<IP_ADDRESS>)(PORT=52032))
2019-06-18T01:05:41.707988+00:00
SOAPDB(3):WARNING: inbound connection timed out (ORA-3136)

How I solve it
I logged in the db container (oracle/database:<IP_ADDRESS>-ee) and add this line SQLNET.INBOUND_CONNECT_TIMEOUT=300 int the file located at /opt/oracle/product/<IP_ADDRESS>/dbhome_1/network/admin/sqlnet.ora.
No restart is required.
After that no more errors and the things goes up!

The solution suggested is acceptable. If required perform "lsnrctl reload" to get the changes effective.

I get the same error only when docker container runs inside my Kubernetes cluster.
On local machine (macOS) directly with docker it does not appear.
On Kubernetes it happens around the fifth connect which then gets timed out.
But your suggestions fix the error, but not really the loooong "almost timeout" of the connection.

My case is the database internally ready for use. Is oracle try to reverse dns lookup the client?

Testing things aroud, do not want to change SQL_NET, it feels like a band aid, after mout /dev/urandom in the container as /dev/random, viola, it starts working.
Different behavior in windows and linux gave me a hint.  Most of time it worked on windows machine, but it failed almost all the time on linux server. What is the difference? randomness is one of them.


New version: ArviZ v0.5.21

Registering package: ArviZ
Repository: https://github.com/arviz-devs/ArviZ.jl
Created by: @sethaxen
Version: v0.5.21
Commit: d9b74e0245414c0ce2eb984caea04c181a6fe343
Reviewed by: @sethaxen
Reference: https://github.com/arviz-devs/ArviZ.jl/commit/d9b74e0245414c0ce2eb984caea04c181a6fe343#commitcomment-73170810
Description: Exploratory analysis of Bayesian models with ArviZ in Julia

block

[noblock]


blog.brackets.io is down

The brackets.io site works normally however, originally reported here: https://github.com/adobe/brackets/issues/13341#issuecomment-319749183

Fixed


add environment variables to readme

In regards to the open issue.
Figured this would be nice to have documented :)

@tyler-mastery, thanks so much for your contribution.


what about the erj liveries?

https://github.com/kolos26/GEOFS-LiverySelector/issues/79

Sorry, I forgot them. Added now.


returning is not supported by mysql

Package version
9.1.1
Describe the bug
I saw the following 2 codes here,
https://github.com/adonisjs/auth/blob/016cc8c6a27109597d86c37caa81a5cf793f529a/modules/access_tokens_guard/token_providers/db.ts#L175-L176
https://github.com/adonisjs/auth/blob/016cc8c6a27109597d86c37caa81a5cf793f529a/modules/session_guard/token_providers/db.ts#L145-L146
It is noticed that the method/function returning('id') is used there, which is not supported for MySQL by knex itself ^1. I know this is for returning an "identifier", but in the previous version (for Adonis v5), there was no identifier and it worked fine.
Is there a fix for this?
Reproduction repo
No response

Hey, it this a MySQL 5.7 related issue? Because we have tests running for MySQL 8 and everything seems to be fine.

The version of MySQL I'm using (more precisely, I'm using MariaDB).
mysql  Ver 15.1 Distrib 10.6.16-MariaDB, for debian-linux-gnu (x86_64) using  EditLine wrapper

And I tried the RETURNING query myself and it worked. Honestly, I don't know which part isn't supported, but I've seen documentation and issues related to Knex regarding this matter (as per footnotes).

I am not able to reproduce it. I will recommend creating a failing test in this repo and then I can look into pushing a fix.

I found the issue, @thetutlage! It's because I used UUID (char(36)) on the access_auth_tokens table. I switched it to bigint and it's working fine now. Hopefully UUID will be supported here.

Can I reopen the issue here and rename the title to "UUID support in foreign keys"?


submit not working

Everything was working all right today and suddenly I started getting this:
Submit 1186 A Haskell GHC 8.6.3
Not logged. Try to login
Login lmno...
Succeed!!
Submit 1186 A Haskell GHC 8.6.3
Not logged in

And it exits
I was already logged in, and even if I log in again (which goes fine), I get the same when submitting.
Codeforces Tool (cf) v0.8.2
Thank you!

Came here to report this, exactly the same thing happening to me on v0.8.2 and even switch users to see if it was a problem with my account, but submit is not working (parse works just fine).
Thanks.

I think the issue is with codeforces, the URL that cf-tool is trying to reach is down: https://codeforces.com/contest/478/submit.

Submission seems to be working all right again, so yes, it was a codeforces issue. Thanks!
Note this: I've been getting that "Oops! Probably Codeforces can't be reached right now or your internet connection is broken" message lately in random Codeforces URLs, even the main page, but reloading once or twice usually fixes it, maybe that can help to overcome this issue... hopefully, we'll stop getting that message from codeforces and that would be it :)


Fix all flake8 issues

This fixes all outstanding flake8 issues that popped up after https://github.com/pytorch/vision/pull/4384 (https://github.com/pytorch/vision/pull/4384#issuecomment-933474723)
Most of it is just removing unused imports. I stayed conservative (i.e. keep the import with a # noqa) when I wasn't sure.
It also ignores the line-too-long errors from flake8: those are taken care of by black now anyway, but there can be minor conflicts in the case e.g. of https://github.com/pytorch/vision/blob/main/torchvision/models/detection/ssdlite.py#L21:L21, so we just keep flake8 quite and trust black in those cases.

The test_frozenbatchnorm2d_eps errors are unrelated and are tracked in https://github.com/pytorch/vision/issues/4506


Attachment form change revisions are not staged correctly [?]

Describe the Bug:
Attachments with the update operation are not changed from pending to staged when navigating away from the attachments form (they do move to staged if you click the "submit" button on the attachments form). Not sure what effect this might have.
A possible cause might be that the attachment "form" (it's an upload button and a table, not an actual ) is made up of multiple form changes, one per attachment.
Probability (how likely the bug is to happen, scored from 1-5): 4
(For example, probability of 5 is something like "it happens to all users every time they log in."
Probability of 1 "only happens to certain users when a really specific and unlikely path is followed.")
Effect (how bad the bug is when it does happen, scored from 1-5): ?
(For example, effect of 5 is "the entire app crashes and makes it unusable for all users" or "the bug causes the wrong data to be saved, with critical information (e.g. payment) being affected."
Effect of 1 is "It makes some styling look a little bit weird.")
Steps to reproduce the behaviour:

create a project with an attachment
create a revision and add an attachment
psql into the db and see that there are 3 attachment form change records, one that's committed, and two that are pending (the new one and the copy of the previously committed one)
navigate away from the attachment form in the app
psql into the db again and see that one of the attachment form changes is still pending

Screenshots:
Additional information:

OS: [e.g. iOS]
Browser: [e.g. chrome, safari]
Version: [e.g. 22]
Additional context

Is this somehow similar to this issue? https://app.zenhub.com/workspaces/climate-action-secretariat-60ca4121764d710011481ca2/issues/gh/bcgov/cas-cif/1759

Maybe? @JoshLarouche and I discovered the staging problem while pairing on 1759, but I think 1759 is more about conditionally showing things (Josh, correct me if I'm wrong here)

I think this MAY be different? I'm not sure as the staging started to work on my end which is when I got confused and thought the 1759 bug wasn't showing for me. I did see the issue when I was pairing with @BCerki but I would need to look into it more to see if I can even reproduce the issue again before being certain if it is similar or related to 1759 or not.


Documentation on how to override sanitizeHtmlOptions

Firstly thanks, this library is a great library!
I have tried a few method to override the sanitizeHtmlOptions object and failed. Can you provide some documentation on how to override those?

@CalvinTp the configs here depend on the original library, there is not much things to do.
Could you share a bit more about what you have done? I may give you another suggestion.


Image pull logs total / downloaded instead of downloaded / total GBs

Environment
Device and OS: System76 Darter Pro, Pop!_OS 22.04 LTS
App version: v0.25.0-rc2
Kubernetes distro being used: k3d
Other
Steps to reproduce

zarf.yaml
kind: ZarfPackageConfig
metadata:
  name: demo
  description: "demo"
  architecture: amd64

components:
  - name: so-many-images
    description: "This think can fit so many images"
    required: true

    images:
      - "registry1.dso.mil/ironbank/big-bang/base:2.0.0"
      - "registry1.dso.mil/ironbank/opensource/istio/pilot:1.16.1"
      - "registry1.dso.mil/ironbank/opensource/istio/proxyv2:1.16.1"
      - "registry1.dso.mil/ironbank/opensource/istio/install-cni:1.16.1"
      - "registry1.dso.mil/ironbank/tetrate/istio/istioctl:1.15.1-tetratefips-v1"
      - "registry1.dso.mil/ironbank/tetrate/istio/proxyv2:1.15.1-tetratefips-v1"
      - "registry1.dso.mil/ironbank/tetrate/istio/pilot:1.15.1-tetratefips-v1"
      - "registry1.dso.mil/ironbank/tetrate/istio/install-cni:1.15.1-tetratefips-v1"
      - "registry1.dso.mil/ironbank/opensource/istio/operator:1.16.1"
      - "registry1.dso.mil/ironbank/tetrate/istio/operator:1.15.1-tetratefips-v1"
      - "registry1.dso.mil/ironbank/opensource/ingress-nginx/kube-webhook-certgen:v1.3.0"
      - "registry1.dso.mil/ironbank/opensource/jaegertracing/all-in-one:1.39.0"
      - "registry1.dso.mil/ironbank/opensource/jaegertracing/jaeger-operator:1.39.0"
      - "registry1.dso.mil/ironbank/opensource/kiali/kiali-operator:v1.60.0"
      - "registry1.dso.mil/ironbank/opensource/kiali/kiali:v1.60.0"
      - "registry1.dso.mil/ironbank/bigbang/cluster-auditor/opa-exporter:v0.0.7"
      - "registry1.dso.mil/ironbank/opensource/kubernetes/kubectl:v1.25.3"
      - "registry1.dso.mil/ironbank/opensource/openpolicyagent/gatekeeper:v3.10.0"
      - "registry1.dso.mil/ironbank/elastic/elasticsearch/elasticsearch:8.5.2"
      - "registry1.dso.mil/ironbank/elastic/kibana/kibana:8.5.2"
      - "registry1.dso.mil/ironbank/elastic/eck-operator/eck-operator:2.5.0"
      - "registry1.dso.mil/ironbank/opensource/fluent/fluent-bit:2.0.6"
      - "registry1.dso.mil/ironbank/big-bang/grafana/grafana-plugins:9.3.2"
      - "registry1.dso.mil/ironbank/kiwigrid/k8s-sidecar:1.21.0"
      - "registry1.dso.mil/ironbank/opensource/kubernetes/kube-state-metrics:v2.7.0"
      - "registry1.dso.mil/ironbank/opensource/prometheus-operator/prometheus-config-reloader:v0.61.1"
      - "registry1.dso.mil/ironbank/opensource/prometheus-operator/prometheus-operator:v0.61.1"
      - "registry1.dso.mil/ironbank/opensource/prometheus/alertmanager:v0.24.0"
      - "registry1.dso.mil/ironbank/opensource/prometheus/node-exporter:v1.5.0"
      - "registry1.dso.mil/ironbank/opensource/prometheus/prometheus:v2.40.5"
      - "registry1.dso.mil/ironbank/twistlock/console/console:22.06.197"
      - "registry1.dso.mil/ironbank/twistlock/defender/defender:22.06.197"
      - "registry1.dso.mil/ironbank/opensource/kubernetes-sigs/metrics-server:v0.6.2"
      - "registry1.dso.mil/ironbank/neuvector/neuvector/controller:5.0.2"
      - "registry1.dso.mil/ironbank/neuvector/neuvector/enforcer:5.0.2"
      - "registry1.dso.mil/ironbank/neuvector/neuvector/manager:5.0.2"
      - "registry1.dso.mil/ironbank/neuvector/neuvector/scanner:latest"
      - "registry1.dso.mil/ironbank/opensource/bitnami/elasticsearch-exporter:1.5.0-debian-11-r17"

Create the Zarf package defined abovezarf package create --confirm

Expected result
In the Pulling x images (y GBs of z GBs) message y should be the number of GBs pulled so far, z should be the total number of GBs
Actual Result
In the Pulling x images (y GBs of z GBs) message y is the total number of GBs, z the number of GBs pulled so far
Visual Proof (screenshots, videos, text, etc)

Severity/Priority
Low
Additional Context

Hi, I'm new to this project and would love to contribute. Can I be assigned to this issue?

Sure @Mihai22125!  Here are our contributing guidelines if you haven't seen them yet:
https://github.com/defenseunicorns/zarf/blob/main/CONTRIBUTING.md
The biggest thing is to make sure you GPG sign your commits (num 3 in developer workflow) (otherwise we will need to close/reopen the PR to re-sign - we would maintain your authorship though)
And here is the likely relevant code as well for this:
https://github.com/defenseunicorns/zarf/blob/main/src/pkg/utils/bytes.go#L85

Missed that @nik-don had already opened a PR sorry about that @Mihai22125


added autofetch arg for get func

A simple idea for implementing auto-fetch with qri.get()

Awesome, yea that approach is much better.


UnixPB: change conditions to include Ubuntu versions greater and equal to 20

ref https://github.com/AdoptOpenJDK/openjdk-infrastructure/issues/2143
The tasks https://github.com/AdoptOpenJDK/openjdk-infrastructure/blob/a4d8543253f2cf3edbe9b606b809a3ad5fd6beab/ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/Common/tasks/Ubuntu.yml#L84 and https://github.com/AdoptOpenJDK/openjdk-infrastructure/blob/a4d8543253f2cf3edbe9b606b809a3ad5fd6beab/ansible/playbooks/AdoptOpenJDK_Unix_Playbook/roles/NTP_TIME/tasks/main.yml#L5 fail on ubuntu versions 20.04 and 21.04, and so need to be skipped on these versions

Hmmm elsewhere we are now using e.g. ansible_distribution_major_version|int >= 10 - Haroon have you verified that this change works on 21.04 and doesn't produce any deprecation warnings with that syntax?
I'm less sure about the lack of VPC run on the basis of the above so I've kicked off https://ci.adoptopenjdk.net/view/Tooling/job/VagrantPlaybookCheck/1141/

Ive verified that the tasks do get skipped without a deprecation warning. I used ansible 2.10.5

Good point - though I restarted your VPC run, as test was specified, without build :-) https://ci.adoptopenjdk.net/view/Tooling/job/VagrantPlaybookCheck/1142/

I'm tempted to suggest ignoring test if buid isn't set ... Keeps catching me out (Doesn't help that RUN_BUILD and RUN_TEST aren't next to each other in the parameter list)

@Haroon-Khel VPC is all good!

I'm tempted to suggest ignoring test if buid isn't set ... Keeps catching me out (Doesn't help that RUN_BUILD and RUN_TEST aren't next to each other in the parameter list)

I'll fix both of those

Given both @Haroon-Khel and @sxa are both away for the next 1-2 week(s), I'm going to squash and merge this so I can get to adding Ubuntu 21.04 to VPC.


Fix the implementation of Http2DependencyTree

Fix #2268
Changed log

Leaving Node alone and using Http2DependencyTree namespace instead

We defined the Node is shadow which the node->t is nullptr.
We will create the shadow node if the parent node is not existed and the exclusive is true. And remove it if children and queue is empty.
The shadow nodes could become a real nodes if the real stream coming. And we set the node->t to the real stream.

@masaori335 @maskit @SolidWallOfCode  Thanks for reviewing. Can you please review again ?

@masaori335 Updated!

That's correct ! I'll fix it.

This wouldn't fix / address any of the ASAN issues I'm seeing does it?

Status on this? It's having merge conflicts now :-). Also, this is a candidate for 7.x ? If so, 7.1.1 or 7.1.2 ? Or 7.2.0 ?

This needs some changes. And I think this doesn't block release of 7.1.1, so this is a candidate for 7.1.2 or 7.2.0.

[approve ci]

[approve ci Linux]

[approve ci]

[approve ci Linux]

@scw00 There is a conflict on the PR, can you please resolve it so we can merge it in.

@bryancall Fixed the conflict!

@masaori335 Can you please approve again! I'll merge it.

Question: Do we want this for 7.1.2, or wait for either 7.2.0 or 8.0.0, whichever comes first ? This does not cherry-pick cleanly to 7.1.x branch, so if we need it there, we will need a new PR.

It'd be great if 7.1.2 has this. I'll create a PR.


update ckeditor when prop changes

this PR updates ckeditor when props change. now it wasn't working if editor was visible and content prop changed.

That is really useful and needed.

Any news ?

This is now merged and made live in version 1.1.0. You can get the latest version from NPM.
Thanks for the PR @themre

pushed a PR related to this one: https://github.com/codeslayer1/react-ckeditor/pull/58


Make AbstractIterator package-private

We use AbtractIterator in order to ensure the NoSuchElementExceptions on empty.next() call are homogenous along all Iterator impls throughout Javaslang and to reduce code duplication.
We should keep the number of types as simple as possible. There is no need to share our impl with the users.

Someone (I dont remember exactly) asked for public visibility

you (I think) :)
Currently we use AbstractIterator only in the javaslang.collection package. Iterator itself is used almost everywhere but it is instantiated by using the factory methods. I think it could be made package private. Let users write Iterators how they are used to write them!

you (I think) :)

NO!!! :smile:

Currently we use AbstractIterator only in the javaslang.collection package. Iterator itself is used almost everywhere but it is instantiated by using the factory methods. I think it could be made package private. Let users write Iterators how they are used to write them!

I agree with you

@ruslansennov


Assets command really needs to tell me what circular dependency it is finding

I keep getting:
Creating new bundle configuration...
Error: A circular dependency is detected for target 'widgets'.

But the problem is it doesn't actually tell me which one, even in debug mode it doesn't seem to.

showing which one exactly is quite hard because it may be over a long list of dependencies which then depend back on the first element. Not sure if it really helps if we implement a search strategy here to improve the error message. When seeing this messages you could normally go through the list of dependencies of 'widgets' and check if any of them depend back on 'widgets'.

@cebe Probably such functionality when YII_DEBUG is true may be interesting.

Issue resolved by commit 378937f


Deweb

Django didn't able to build multiply filter in template. (when multiply filter worked, site is slowly working.


0.12: transformer.js syntax error: Unexpected token ,

I'm getting this syntax error after upgrading to 0.12.
/Users/Shared/project/node_modules/react-native/packager/transformer.js:32
	filename,
			^
SyntaxError: Unexpected token ,
	at exports.runInThisContext (vm.js:53:16)
	at Module._compile (module.js:411:25)
	at Object.Module._extensions..js (module.js:446:10)
	at Module.load (module.js:353:32)
	at Function.Module._load (module.js:308:12)
	at Module.require (module.js:363:17)
	at require (module.js:382:17)
	at process.<anonymous> (/Users/Shared/project/node_modules/react-native/node_modules/worker-farm/lib/child/index.js:45:34)
	at emitTwo (events.js:87:13)
	at process.emit (events.js:169:7)

Very weird. It's stumbling over es6 object literals, which I'm also using myself in the project code. Seems like some babel configuration is not updated properly somewhere

Can you share your code?

Can you provide a few lines around where this happens (/Users/Shared/project/node_modules/react-native/packager/transformer.js:32)?

I think it's resolved. It was probably related to some non up to date contextual libraries such as nvm. I went back to the basic setup instructions, upgraded everything and I was set

Closing this out ^


Discuss the possibility of upgrading Kura to Java 8

The next release of Kura will be using Java 8, so we can use Java 8 in Rhiot bits dedicated  as well.


make error

cc ${wl}-flat_namespace ${wl}-undefined ${wl}suppress -o .libs/env.so -bundle  php5/.libs/php_env.o .libs/env.o
duplicate symbol _env_globals in:
php5/.libs/php_env.o
.libs/env.o
ld: 1 duplicate symbol for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [env.la] Error 1
PHP 5.6.21 (cli) (built: May 13 2016 17:51:57) (DEBUG GCOV)
Copyright (c) 1997-2016 The PHP Group
Zend Engine v2.6.0, Copyright (c) 1998-2016 Zend Technologies
with Xdebug v2.4.0, Copyright (c) 2002-2016, by Derick Rethans
Darwin 15.5.0 Darwin Kernel Version 15.5.0: Tue Apr 19 18:36:36 PDT 2016; root:xnu-3248.50.21~8/RELEASE_X86_64 x86_64

I tried the NTS version of php 5.6.21, still got the same error. Attach the build log. Thanks.
build.log.txt


Remove specific code for testing Symfony 6

Q
A

Type
task

BC Break
no

Fixed issues

Summary

There is no need for this since it has been released and it will install Symfony 6 using highest dependencies.

Thanks @franmomu!


Set up AppVeyor build with CI Nuget package feed

I will only build the netstandard branch, and publish nuget packages from there.

Done: https://ci.appveyor.com/project/dazinator/rhino-licensing/build/artifacts


Updated gas_price on networks.json for sentinel chain

With the old gas price for sentinel chain restake was not working anymore. I put 0.1udvpn and it works fine

Thank you!


[ISSUE #4191] Do some code optimization.[StreamPushRequest]

Fixes #4191.
Motivation
Explain the content here.
Explain why you want to make the changes and what problem you're trying to solve.
Modifications
Describe the modifications you've done.
Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

@mxsm @Alonexc Please review


feat: add typing effect when streaming texts

Replaced by: https://github.com/casibase/casibase/pull/762


arm-eabi-nm: not found (but I can find arm-none-eabi-nm)

When I started checkStackUsage.py on Ubuntu 22.04, I get :
/bin/sh: 1: arm-eabi-nm: not found
/bin/sh: 1: arm-eabi-objdump: not found

The package binutils-arm-none-eabi contains arm-none-eabi-nm and arm-none-eabi-objdump but I can't find arm-eabi-nm nor arm-eabi-objdump.
By doing this, I don't have the messages above :
diff --git a/checkStackUsage.py b/checkStackUsage.py
index 4c66e6a..7581963 100755
--- a/checkStackUsage.py
+++ b/checkStackUsage.py
@@ -214,8 +214,8 @@ def ParseCmdLineArgs(cross_prefix: str) -> Tuple[
             stackUsagePattern = Matcher(
                 r'^.*save.*%sp, (-([0-9]{2}|[3-9])[0-9]{2}), %sp')
         elif arm.search(binarySignature):
-            objdump = 'arm-eabi-objdump'
-            nm = 'arm-eabi-nm'
+            objdump = 'arm-none-eabi-objdump'
+            nm = 'arm-none-eabi-nm'
             functionNamePattern = Matcher(r'^(\S+) <([a-zA-Z0-9_]+?)>:')
             callPattern = Matcher(r'^.*bl\s+\S+\s+<([a-zA-Z0-9_]+)>')
             stackUsagePattern = Matcher(

Is my modification relevant ?

Well, the difference between the two toolchains is that one targets embedded systems with no OS (bare metal, hence no application binary interface - there are no applications in a monolithic embedded image!)
This is what the main README refers to when it says: "...Adding additional platforms is very easy - just tell the script what objdump flavor to use..."

Sorry to bother you but what I still don't understand is where can arm-eabi-nm (or arm-eabi-gcc or other tools) be found ?
On ARM website, I can find arm-none-eabi and arm-none-linux-gnueabihf but I can't find arm-eabi. My search on internet has been unsuccessful.
Thank you

No problem, Jonathan. When I wrote the script - "back in the day :-)" - I believe I was using the Linaro tools. But one can also build the cross-compilers on his own - it's not so hard.
Do keep in mind though, that the script can be used with any target - targeting bare metal or OS-specific code (i.e.  without or with an application binary interface) - as long as you can provide the patterns to match the stack reservations in the disassembly of your code.