[CH-432]fixed nullable mismatch in coalesce

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
Fixes: https://github.com/Kyligence/ClickHouse/issues/432
pass the schema into coalesce
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
unit tests
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)
test by CH[[440]]

native pr is https://github.com/Kyligence/ClickHouse/pull/440


The sample command "az monitor diagnostic-settings create" is throwing multiple errors.

[Enter feedback here]
The sample command "az monitor diagnostic-settings create" is throwing multiple errors.
Please refer the attached image for all the errors and the final working one highlighted in red box.

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

ID: e65b6971-ea56-5e85-b199-d357fbc97580
Version Independent ID: 219058ac-5460-a33f-bec1-810f40cd2be7
Content: Monitor data by using Azure Diagnostic settings - Azure Cosmos DB
Content Source: articles/cosmos-db/monitor-resource-logs.md
Service: cosmos-db
GitHub Login: @seesharprun
Microsoft Alias: sidandrews

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

@tonytomyatmicrosoft
Thank you for bringing this to our attention.
I've delegated this to content author @seesharprun, who will review it and offer their insightful opinions.

@seesharprun
Could you please review add comments on this, update as appropriate.

@tonytomyatmicrosoft, if you drop the categoryGroup: null from the JSON, it should work. This article will be updated soon.


cmd/go: go test usage regression, inconsistency

Discussion on CL 14826, but I am creating an issue so it isn't forgotten for Go 1.6, one way or the other.
In short, these four commands have always worked:
go test -test.short math
go test -short math
go test math -test.short
go test math -short

Now the last does not.

I just ran across a similar (perhaps exactly the same) issue. It applies to test flags that
take an argument. The go test command treats flag arguments as if they were package
names.
This no longer works (note: all our code uses Gustavo's gocheck package
which adds its own flags to the test):
go test -gocheck.f MyTest

Instead, one is required to write:
go test -gocheck.f=MyTest

or
go test . -gocheck.f MyTest

Comment from @rsc in https://golang.org/cl/14826:

There are two fundamental problems that make the design here tricky.
The first is that I tried to avoid required alternation of flags and arguments, based on bad experience with the pedantry of Mercurial, where you have to remember to write things like "hg -V log -l2" and not "hg log -V -l2". I think that turned out well in general, but the other commands established a precedent of flags before the package arguments, and we had to also allow unrecognized flags to pass to the test binary after the package list. Following the last version of gotest, we sniffed the beginning of the flags after the package list to apply the same conversions as before the package list. Otherwise it is difficult to explain why only the 4th of these is disallowed:

go test -test.short math
go test -short math
go test math -test.short
go test math -short

It can be explained of course, but the explanation is something users don't typically care about, the same way Mercurial users don't want to play Simon says trying to figure out "hg -V log -l2".
The second problem is that the package list is optional. If it gets overloaded as a signal changing the meaning of command-line flag parsing, then now flags and the presence of the package list are conflated in ways they were not before, which leads to more confusion.
As a demonstration, this CL broke "go test -unrecognizedflag x". That used to mean test the current directory with "-unrecognizedflag x" passed to the test. Now the command is rejected. (Roger Peppe pointed this out on #13583 over the weekend.) This CL also changed the meaning of "go test -unrecognizedflag=1 arg1 arg2". Before, the test processing stopped before the first unrecognized flag (as documented), so that "-unrecognizedflag=1 arg1 arg2" would be passed to the test as its arguments. Now, -unrecognizedflag=1 is taken and given to the test but arg1 arg2 are used as the package list! While there may be ambiguity in the 1-line usage message, it can't explain that. The parsing is actually more muddled now than it was before the CL. The new comments claim that this is for "backwards compatibility with a poor design", but it's not backwards compatible and even harder to explain than before.

The counter-proposal is this. Put in a flag -args that consumes the remainder of the command line, to be passed verbatim to the test. (This is by loose analogy with gdb --args, although there it includes the name of the binary to run, and here it does not.)

Then to test glog's -v flag you can do either of:

go test .../glog -args -v
cd glog; go test -args -v

Similarly, if you want to run a test with non-flag arguments passed on the command line (impossible both before and after this CL), you can do that with -args:

go test -args X Y Z

I'll send a CL for this and try to make sure the docs are clear.

So, is -args the same thing as --, spelled differently? I recall people asking for -- previously but it being shot down.

What I objected to with -- in the past was the idea that you'd put more flags after it. The long-established definition of -- is that it stops flag processing, even (especially!) when what comes next look like more flags. There's also a compatibility issue. From the beginning, -- has been passed through to the underlying binary, so that it had the same meaning in the underlying test binary command line as it did in the go test command line. There may well be tests that expect that.
The same compatibility issue could arise with -args, but -args is not a long-established convention being given a different meaning, so it's less likely that a test already expects it and also less problematic to give it the meaning we need.

I'm fine with -args but even with your description it sounds too similar to -- to be worth breaking convention. I'd use the mechanism that's more familiar (--) rather than invent something new.

FWIW, Rob and I discussed -- just now, and he started out on your side but
when I made the same point I just made to you, he agreed it doesn't make
sense to use -- for this.
The important point is that go test is kind of weird: the command line is
serving both as arguments to 'go test' but then, usually, in a rewritten
form also as arguments to the test binary itself. We've worked pretty hard
(and, I would argue, successfully) so that users don't think about that:
they see a single thing, even though underneath there are two different
programs implementing that thing. It would be strange for --, which means
"the rest of the command-line is not flags" to mean that only for 1/2 of
the pieces.

I'll just register that I'm really not keen on -args.
The moment people use either -args or -- they have
to be aware of the split in the flag parsing between
top level command and test binary, and -- has
a long history as the way to stop dash-prefixed arguments
from being interpreted by the top level command.
Thus AFAICS (this was certainly true for me) once someone
realises that the flags are being interpreted by the top
level go command, they'll reach for the usual tool (--)
and be surprised when it doesn't work.
To me, "--" does not mean "the rest of the command line is not
flags", but "the rest of the command line is not interpreted as
flags by the top level command".
Consider, for example:
 sh -c 'echo $*' -n a b c

vs
 sh -c 'echo $*' -- -n a b c

The "-n" argument is still a flag, even though it's after the "--".
I'd argue that the go tool case is similar.
The compatibility issue is unfortunate though, and probably the clincher
in favour of -args.

A more common place you'd see -- is in something like ls -l -- -n as an
alternative to ls -l ./-n.
The sh example is at the very least convoluted. I can't think of any other
examples where -- means "the rest of the command line is not interpreted as
flags by the top-level command". Most people don't know sh -c CMD takes
additional arguments at all, and what it does with them is inconsistent,
and sh -c is explicitly about reexecution in a direct way that I would
argue 'go test' is not.
Also, fun on my Mac:
$ sh -c 'echo $*' -- -n a b c
-n a b c
$ sh -c '/bin/echo $*' -- -n a b c
a b c$
$

Again maybe not the best example. :-)
Also, for the record, the way git uses -- (to separate one kind of non-flag
argument from another) is non-standard too.


Some toString methods to help with debugging

@dblevins Can you rebase this please so that we can trigger the github action builder for it?


Text output feature

Hi,
Is there any possibility that Netron outputs the NN description text for the user?
Similar to CAFFE's prototxt format, with the layer details &  dependency (input layer name) shown in Netron's block.
For example:
INPUT {
  output_size: {3, 224, 224}
}
Layer0 {
   Type: CONV2D
   Input_name: INPUT
   kernel: (64,3,3,3)
   stride: 1
   output_size: (64,222,222)
}

Layer1 {
   Type: CONV2D
   Input_name: Layer0
   kernel: (64,64,3,3)
   stride: 1
   output_size: (64,220,220)
}

...

Thank you.

@ycchung0516 can you explain what specific problem you are trying to solve, why you need this feature? What would a mockup look like?

@lutzroeder I am working on the AI accelerator hardware design for parallel multi-DNN execution.
To determine the hardware architecture, I want to profile and analyze different domains' DNN workloads in the early design stage.
Also, at the compile time, I can convert these DNN description files to generate the instructions/configs to operate the AI accelerator.
The DNN description file can be a text file that includes all the information in the Netron GUI block. With these description files, I can build the DAG for the analysis with the inputs' and outputs' names.
The mockup is referenced from SqueezeNet in the repo:
The format can be changed for your convenience, I used CAFFE's prototxt format here for the example.
CONV block example

Layer {
    NODE_PROPERTIES {
        type: Conv
   }
    ATTRIBUTES {
       kernel_shape: 3, 3
       pads: 0, 0, 0, 0
       strides: 2, 2
   }
    INPUTS {
          X:  data_0
         W: conv1_w_0
         B: conv1_b_0
    }
    OUTPUTS {
        Y: conv1_1
   }
}

How would this work, copy and paste the description for each node manually? Can this be done more efficiently via a CLI Python script using the actual Caffe framework? Is the challenge more that in Caffe the nodes don't show identifiers or a location index?

CAFFE doesn't support other kinds of frameworks like Netron.
I am sorry that the expression is not clear.
Netron draws the block diagram of DNN with each layer's information, it must generate the information with the defined data structure before drawing.
Can Netron add a feature to output this information of each block (layer) as a text file? The CAFFE format above is an example for you to look at.

@ycchung0516 Netron is not a framework. Caffe is a framework. You can use Caffe to open Caffe models, process them or output text information about the model. Why would it help to copy random text in a random format from a tool like Netron. For example, below is "text" and it's a better compact representation. A representation that makes sense for Caffe likely does not work for other formats like ONNX and would not be efficient to render in a large graph.


Add notes about the salesforce-maven-plugin to the Salesforce extension docs

Hold merging - I probably need to tweak code block because I don't see the camel-version property replacement happening locally.


chore(dev): add yarnupgrade workflow

Add YarnUpgrade workflow to run the yarn upgrade from github action. This will reduce the invividual PRs created from dependabot.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hi @mreferre
I am installing this GH action for easier daily maintenance.

By running this workflow, the following PRs opened by dependabot should be closed automatically.


[SPARK-17711] [test-hadoop2.2] Fix hadoop2.2 compilation error

What changes were proposed in this pull request?
Fix hadoop2.2 compilation error.
How was this patch tested?
Existing tests.
cc @tdas @zsxwing

Test build #67146 has started for PR 15537 at commit fd0b076.

LGTM pending tests

Test build #67146 has finished for PR 15537 at commit fd0b076.

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

Merged build finished. Test PASSed.

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

Thanks! Merging to master and 2.0.


Add observations auto-configuration

Adds auto-configuration of the observation aspects of the listener and template.
Points of interest

I refactored the template and listeners to use immutable constructors for some key pieces to simplify them as well as make them auto-configuration friendly (eg. the auto-config will/not pass in the observation registry when user has disabled the obeservations property).

Resolves #147

We did an internal code review by walking through the code. Looks good @onobc. Merged upstream.


StreamingProtocols/StreamingIntegrationTest.PostAndProcessStreamedRequestBodyPartially is flaky

The test StreamingProtocols/StreamingIntegrationTest.PostAndProcessStreamedRequestBodyPartially in //test/extensions/filters/http/ext_proc:streaming_integration_test seems to be flaky.
An example: https://dev.azure.com/cncf/envoy/_build/results?buildId=149245&view=logs&j=767be981-567e-57d8-68c3-2140ede0a0bd&t=67a76341-37f4-5b49-db38-acbb8a59af82&l=4490
[ RUN      ] StreamingProtocols/StreamingIntegrationTest.PostAndProcessStreamedRequestBodyPartially/IPv4_EnvoyGrpc_WithDeferredProcessing
test/extensions/filters/http/ext_proc/streaming_integration_test.cc:351: Failure
Value of: client_response_->headers()
Expected: http status is "200"
  Actual: 24-byte object <B0-CC E8-01 00-00 00-00 A8-D1 E8-01 00-00 00-00 20-D2 E8-01 00-00 00-00> (of type Envoy::Http::ResponseHeaderMap), which has status code 500
Stack trace:
  0x1d9e288: testing::internal::HandleExceptionsInMethodIfSupported<>()
  0x1d9e128: testing::Test::Run()
  0x1d9f278: testing::TestInfo::Run()
... Google Test internal frames ...

@yanjunxiang-google can you PTAL?

Thanks for reporting the issue. Yes, there is a bug in this test.
Please check https://github.com/envoyproxy/envoy/pull/29628 for the root cause and fix.

@yanjunxiang-google is this fixed and should be closed out?

Yes, this issue is fixed. Let's close it.

/closed


Create new Cancer Biomarkers summary widget and detail view for evidence page

We are adding Cancer Biomarkers as a new evidence source for the upcoming release (21.09). We need to create a table to display the data.

The current schema is in a mature state and no changes are expected:
root
 |-- biomarkerName: string (nullable = true)
 |-- biomarkers: struct (nullable = true)
 |    |-- geneExpression: array (nullable = true)
 |    |    |-- element: struct (containsNull = true)
 |    |    |    |-- id: string (nullable = true)
 |    |    |    |-- name: string (nullable = true)
 |    |-- variant: array (nullable = true)
 |    |    |-- element: struct (containsNull = true)
 |    |    |    |-- functionalConsequenceId: string (nullable = true)
 |    |    |    |-- id: string (nullable = true)
 |    |    |    |-- name: string (nullable = true)
 |-- confidence: string (nullable = true)
 |-- datasourceId: string (nullable = true)
 |-- datatypeId: string (nullable = true)
 |-- diseaseFromSource: string (nullable = true)
 |-- diseaseFromSourceMappedId: string (nullable = true)
 |-- drugFromSource: string (nullable = true)
 |-- drugId: string (nullable = true)
 |-- drugResponse: string (nullable = true)
 |-- literature: array (nullable = true)
 |    |-- element: string (containsNull = true)
 |-- targetFromSourceId: string (nullable = true)
 |-- urls: array (nullable = true)
 |    |-- element: struct (containsNull = true)
 |    |    |-- niceName: string (nullable = true)
 |    |    |-- url: string (nullable = true)

Evidence strings can be found here: gs://otar000-evidence_input/CancerBiomarkers/json, although they are not yet exposed in the GraphQL API.
The data at the moment has a bug that prevents it from passing validation (see #1705), but it shouldn't be a blocker to scope how data should look like.
The data represents how tumour alterations can modulate drug response. We have different scenarios:

1. An example where biomarker describes a single variant (and we have variantId)
{
    "datasourceId": "cancer_genome_interpreter",
    "datatypeId": "affected_pathway",
    "drugFromSource": "ERK inhibitors",
    "drugResponse": "GO_0042493",
    "targetFromSourceId": "BRAF",
    "diseaseFromSource": "Head and neck squamous cell carcinoma",
    "diseaseFromSourceMappedId": "EFO_0000181",
    "confidence": "Case report",
    "biomarkerName": "BRAF (G469A)",
    "urls": [
        {
            "niceName": "American Society of Clinical Oncology Annual Meeting 2017",
            "url": "https://meetinglibrary.asco.org/browse-meetings/2017%20ASCO%20Annual%20Meeting"
        }
    ],
    "biomarkers": {
        "variant": [
            {
                "name": "BRAF:G469A",
                "id": "7_140481402_C_G",
                "functionalConsequenceId": "SO_0001777"
            }
        ]
    }
}

2. An example where biomarker describes multiple variants
{
    "datasourceId": "cancer_genome_interpreter",
    "datatypeId": "affected_pathway",
    "drugFromSource": "Pd1 Ab Inhibitors",
    "targetFromSourceId": "KRAS",
    "diseaseFromSource": "Lung adenocarcinoma",
    "diseaseFromSourceMappedId": "EFO_0000571",
    "confidence": "Early trials",
    "biomarkerName": "STK11 oncogenic mutation + KRAS oncogenic mutation",
    "urls": [
        {
            "niceName": "American Society of Clinical Oncology Annual Meeting 2017",
            "url": "https://meetinglibrary.asco.org/browse-meetings/2017%20ASCO%20Annual%20Meeting"
        }
    ],
    "biomarkers": {
        "variant": [
            {
                "name": "KRAS",
                "functionalConsequenceId": "SO_0001777"
            },
            {
                "name": "STK11",
                "functionalConsequenceId": "SO_0001777"
            }
        ]
    }
}

3. An example where biomarker consists of a change in expression
{
    "datasourceId": "cancer_genome_interpreter",
    "datatypeId": "affected_pathway",
    "drugFromSource": "Ado-trastuzumab Emtansine",
    "drugResponse": "GO_0042493",
    "targetFromSourceId": "ERBB2",
    "diseaseFromSource": "Breast adenocarcinoma",
    "diseaseFromSourceMappedId": "EFO_0000304",
    "confidence": "FDA guidelines",
    "biomarkerName": "ERBB2 overexpression",
    "urls": [
        {
            "niceName": "Food and Drug Administration guidelines",
            "url": "https://www.fda.gov/RegulatoryInformation/Guidances/default.htm"
        }
    ],
    "biomarkers": {
        "geneExpression": [
            {
                "name": "ERBB2:over",
                "id": "GO_0010628"
            }
        ]
    }
}

4. An example where biomarker describes a variant and a change in expression
{
    "datasourceId": "cancer_genome_interpreter",
    "datatypeId": "affected_pathway",
    "drugFromSource": "Trastuzumab",
    "drugId": "CHEMBL1201585",
    "targetFromSourceId": "ANXA1",
    "diseaseFromSource": "Breast adenocarcinoma",
    "diseaseFromSourceMappedId": "EFO_0000304",
    "confidence": "Early trials",
    "biomarkerName": "ARID1A amplification + ANXA1 overexpression",
    "literature": [
        "27172896"
    ],
    "biomarkers": {
        "variant": [
            {
                "name": "ARID1A:amp",
                "functionalConsequenceId": "SO_0001563"
            }
        ],
        "geneExpression": [
            {
                "name": "ANXA1:over",
                "id": "GO_0010628"
            }
        ]
    }
}

Things to bear in mind:

No evidence strings have biomarkerName set to null.
There are cases where drugResponse is null - this will be fixed as soon as EFO creates new terms for certain drug responses. This is no longer the case, as we are displaying the raw string until we are happy with how EFO treats drug responses.
No evidence strings have drugFromSource set to null.
drugFromSource can be mapped sometimes to a CHEMBL drug (drugId)
biomarkers.variant.functionalConsequenceId is a SO ID that needs to be resolved. We want to show the label and build the respective link.
Similarly, biomarkers.geneExpression.id is a GO ID that needs to be resolved. We want to show the label and build the respective link.
Most of the evidence is supported by a PubMed ID, sometimes the reference is built into urls displaying. Note that we might have cases where both fields are present (biomarkerName='ERBB2 overexpression')

Based on the analyses above by @ireneisdoomed, I have created a sample API query and draft design specification for a new Cancer Biomarkers section on the evidence page.
Please note that both are subject to further change and iteration.
Query
query targetInfo {
  target(ensemblId: "ENSG00000157764") {
    id
    approvedSymbol
    evidences(efoIds:["EFO_0000181"], datasourceIds:["cancer_biomarkers"]){
      rows{
        disease{
          id
          name
        }
        diseaseFromSource
        biomarkerName
        biomarkers{
          geneExpression{
            id
            name
          }
          variant{
            functionalConsequenceId
            id
            name
          }
        }
        drugFromSource
        drugId
        drugResponse
        confidence
        literature
        urls {
          niceName
          url
        }
      }
    }
  }
}

Summary widget

[ ] Display the number of rows returned by the API query.

Detail view

[ ] Create a data table section based on the following design specification

[ ] For the section description, display the following text.

Expert-curated genomic biomarkers of drug sensitivity, resistance, and toxicity for drugs targeting GENE with an experimental or approved indication of DISEASE. Source: Cancer Genome Interpreter.

[ ] Show the "Affected pathway" datatype chip in the top right-hand corner

[ ] Add the ability to search the table by the "Disease", "Biomarker", "Reported drug", and "Source" columns

[ ] Add the "Show more rows" functionality

[ ] In the "Disease" column, display the disease.name value and link to the relevant disease profile page using the disease.id value. Also, display the diseaseFromSource in a tooltip.

[ ] In the "Biomarker" column, display the biomarkerName value and on-click, open the drawer component. Iterate through the biomarkers object and construct up to two unordered lists — one list called "Variant" with the biomarkers.variant.name and biomarkers.variant.id (if available); the other list called "Gene expression" with the biomarkers.geneExpression.name. It is important to note that there are associations with only one gene expression, one variant, multiple variants, and both gene expression and variant information — see @ireneisdoomed analyses above for examples. And also note that in further iterations, this data will be expanded and the SO and GO terms will be resolvable entities.

[ ] In the "Reported drug" column, display the drugFromSource value and if drugId is not null, link to the drug profile page using the drugId value — otherwise, just display the drugFromSource value.

[ ] In the "Source" column, display the confidence value

[ ] In the "Literature" column, use both the literature and urls arrays and display the PubMed IDs and url.niceName values in the drawer component and link to Europe PMC. Note: if the drawer component is flexible enough to show the citation/abstract and other URLs, we can use that functionality — otherwise, we can just show a list of the IDs and url.NiceName values.

@mirandaio I've updated the design specification above — it should be good to go! 👍

Thank you @mirandaio for your work!
Some things I've noted:

There are special characters in the name of the data source in the facet. Could we change that to Cancer Biomarkers?

I don't know if it is intended, but the order of the columns are changed. Could we put the Drug response column immediately after Reported drug?

There are biomarkers which cannot be referenced with a Pubmed ID, hence lacking any type of link out on the FE. For this cases an url is also returned in the API (urls.niceName and urls.url) instead. (link)

@andrewhercules, do you think it would be a good idea to collapse the Source and Literature columns similarly as we do in the target safety widget in such a way that:

references where literature != null display the literature widget
references where literature == null link out to the url returned in urls.url?

The biomarker name can be very long and look ugly in the table. ABL1 is the most extreme case, with about 70 mutations. (link)

@andrewhercules , what is the best way to go about this? Is it possible to collapse the name and adding ..., e.g.? Please note that the second most promiscuous case is found on NOTCH1 (152 characters), which doesn't look bad (link):

@mirandaio based on the feedback from @ireneisdoomed above, can we please do the following?

[ ] Change the order of the columns and move the "Drug response" column left so that it is after the "Reported drug" column

[ ] In the "Biomarker" column, truncate the text to show the first 100 characters and then show ellipsis and on-hover, show the full text

[ ] Update the "Source" column to use the drawer component and iterate through the urls array and show a list of each urls.niceName and link with the urls.url value

[ ] Update the association page facets — see #1736

@ireneisdoomed @andrewhercules I have addressed the feedback. Let me know if it's ready to merge. Thanks!

Thanks @mirandaio — looks great! 👍
@ireneisdoomed we had to adjust how we handle the urls and for now, we are showing in the Source column. This allows us to handle situations where there's both a publication and a trial ID or external link (e.g. ALK and lymphoma)

Niceeee

Thank you both!
@andrewhercules To me it looks great now. The distinction of the origin of the data is clearer like this.
@mirandaio, I don't know if it is due to this specific PR, but it seems that something has been changed on the widgets drawer. I don't think it was like this on Friday. Do you see the same behaviour? (link)

Ticket closed as work completed, merged into main, and released in 21.11


controls: update to LaxarJS 1.0.0 style controls

Use the new, separated controls.

Implemented on master (v3.0.0)
Breaking Change
The widget was updated to be compatible to LaxarJS 1.0.0, which introduces several incompatibilities to prior LaxarJS versions itself. Hence it is required that an application using this widget in version 3.0.0 updates the following libraries at least to the given versions in its bower.json:
 "laxar": "LaxarJS/laxar#^1.0.0-alpha.14",
 "laxar-patterns": "LaxarJS/laxar-patterns#^1.0.0-alpha.3",
 "laxar-uikit": "LaxarJS/laxar-uikit#^1.0.0-alpha.7",


Docker jobs not running when pulling from self-hosted registry

I am running mesos 0.21.1, marathon 0.7.6 and chronos 2.3.0. I've submitted a docker job using the following JSON
{
  "name": "hello",
  "schedule": "R/2015-01-16T11:00:00Z/PT5M",
  "container": {
    "type": "DOCKER",
    "image": "myregistry:5000/myimage"
  },
  "cpus": 0.2,
  "mem": 32.0,
  "command": "echo this is a test"
}

The docker image, myimage is hosted in a private, self-hosted docker registry. The server for the registry is at myregistry on port 5000.
The job shows up in the Chronos UI, and the "schedule" section in the UI updates the time every 5 minutes, however, the # success and error are 0. The mesos UI doesn't show any tasks for this job either. When I tail /var/log/messages (this is installed on CentOS6), I don't see any errors.

FWIW -- I just restarted chronos, and it successfully ran the docker job.

I had an issue much like this.  However, mine was that I got a timeout on the task setup from Mesos.  Well if it is a new chronos job it may need to download the Docker image.  This takes longer than the time set for task set-up in Mesos and thus failed.  The second run of the job then worked.
It would be nice if mesos had a different timeout for loading Docker images...

@rayjohnson it has see --executor_registration_timeout here

hi @mindscratch, yes the property to change would be executor registration timeout. This problem is related to any tasks running docker in marathon or chronos. Did changing that timeout resolve your issue?

@elingg I've been focusing on Marathon the last couple of months, I believe I'll be looking at using Chronos again soon. If I do, I'll post my observations. Thanks.

In the meantime can we close this?
It seems it's a configuration issue with mesos more than anything, perhaps
we could add a note in the documentation about this and raise the mesos
default.
On Thu, Apr 9, 2015 at 2:08 AM, Craig Wickesser<EMAIL_ADDRESS>wrote:

@elingg https://github.com/elingg I've been focusing on Marathon the
last couple of months, I believe I'll be looking at using Chronos again
soon. If I do, I'll post my observations. Thanks.
—
Reply to this email directly or view it on GitHub
https://github.com/mesos/chronos/issues/340#issuecomment-91165808.

I think that sounds reasonable. I probably won't get a chance to test this for a few weeks.


Cleanup unused overloaded methods

I noticed that our production code always instantiates FeedRetriever with a non-null CurlHandle.
Changed the argument to a reference to make this obvious (and updated tests to make tehm use FeedRetriever in the same way as the production code).
Extended these changes to external APIs and other places where we use a CurlHandle.
Additionally I noticed that my C++ Vim plugin started highlighting unused header includes.
I've removed those unnecessary header includes in the files I had open for this PR.
If preferred, I can take out those changes and apply them in a separate PR.
-> I ran into some issues so will move these changes into a separate PR

coverage: 59.866% (+0.1%) from 59.767%
when pulling f6b2dfff95128c0affef115f85d2aaccfe8c4718 on dennisschagt:feedretriever-easyhandle
into ffc9e3d14da753f4889930517892e64ab1c89ade on newsboat:master.


PR template doesn't work

Describe the bug
The PR template you placed simply doesn't work.
To Reproduce
Just try to create a PR using any branch with some changes.
Expected behavior
The PR template you placed shows up.
Additional context
None

closed via #218


Export function

Would be very nice if there would be an export function in html or bbcode and preferably per show and total. That would be very exciting, especially for forum users. Thanks for a check

I'd probably need an example of what you want, and I assume you are talking about from the Rounds details screen, or Shows?

[table] [tr] 	[th]Level Name[/th] 	[th]Played[/th] 	[th]Qualified[/th] 	[th]Gold[/th] 	[th]Silver[/th] 	[th]Bronze[/th] 	[th]Kudos[/th] 	[th]Avg Kudos[/th] 	[th]Avg Duration[/th] [/tr] [tr] 	[td]Fruit Chute[/td] 	[td]30[/td] 	[td]29[/td] 	[td]6[/td] 	[td]11[/td] 	[td]7[/td] 	[td]3405[/td] 	[td]113[/td] 	[td]0:43[/td] [/tr] [tr] 	[td]See Saw[/td] 	[td]30[/td] 	[td]30[/td] 	[td]9[/td] 	[td]15[/td] 	[td]6[/td] 	[td]3065[/td] 	[td]102[/td] 	[td]2:16[/td] [/tr] [/table]
Something like that is my guess. That way you can take the values and paste them into an Excel document and sort them around and stuff.

Hello, yes as a .csv it works, that's right. But if you want to export the whole thing for a website or forum then you first have to convert the .csv into html and copy everything out and insert a header.
The export should of course use the filters, so I want to export a session then it only exports this. But that works with .csv and should also be possible with html export, right?
Actually this html output would be the right one, yes. Simply export directly if possible.
[table] [tr] [th] Level Name [/ th] [th] Played [/ th] [th] Qualified [/ th] [th] Gold [/ th] [th] Silver [/ th] [th] Bronze [/ th] [th] Kudos [/ th] [th] Avg Kudos [/ th] [th] Avg Duration [/ th] [/ tr] [tr] [td] Fruit Chute [/ td] [td] 30 [/ td] [td] 29 [/ td] [td] 6 [/ td] [td] 11 [/ td] [td] 7 [/ td] [td] 3405 [/ td] [td] 113 [ / td] [td] 0:43 [/ td] [/ tr] [tr] [td] See Saw [/ td] [td] 30 [/ td] [td] 30 [/ td] [td] 9 [ / td] [td] 15 [/ td] [td] 6 [/ td] [td] 3065 [/ td] [td] 102 [/ td] [td] 2:16 [/ td] [/ tr] [ / table]

Ok I have added Html and BBCode options to the right click menu on the grids, which will export to your clipboard.
Can be found in v1.63

wow super many thanks, it works wonderfully. Would it be possible to include the title line as well? So Level Name, Played, Qualified ...

It should already include the header, unless you are talking about something else?

Also table yes, unfortunately not as BBCode.


bug: markdown is not rendered in transcript user message

Version
main
Describe the bug
Users can't encapsulate markdown with triple backticks (```) anymore in chat
see video
https://github.com/sourcegraph/cody/assets/51868853/2f7c3eb4-1909-43a2-84c2-e917533a739a
Expected behavior
in chat users should be able to encapsulate their code in markdown using triple backticks
Additional context
No response

The bug is that the markdown is not rendered when the user's message is displayed in the transcript.
Will look into it now

also filed in #3496

@sqs any updates to the fix?

Based on new design direction to make user transcript less rich, more notebook style


Updated to include 'unreleased' and 'bugfix'

Added in unreleased section plus bugfix section. Wrote in the bugfix to #52 in pull request #55

Duplicate with pull request 55


New feature to pull recorded images / video

Hi,
I'm working on a flow to grab a still image on an alarm and store on my PI4 for easy verification. I'm sure it would be possible to get this from the DVR directly based on timestamp, camera channel etc. I don't have any good info on the API and its probably beyond my skills.
Do you have any plans for something like this ?

Hi
Yes you van do it using the picture node, but better asking on nodered forum, as i’m very busy with another of my nodes and i cannot currently halp you!

Sorry I didn't explain very well.
I mean to grab an image from the "past" based on a timestamp, not a live image. Also video clips would be great ;-)

Hi,
Ok, understood.
No, currently is not possible. Maybe you can achieve that by using the XML Node and pass the needed data to it. You should search for what to pass, in the use-ip website forum or in the ipcamtalk website forum.


sqlean flags lower() as non-deterministic

Running sqlean version 3.45.0 on macOS I get this error:
Parse error near line 120: non-deterministic functions prohibited in generated columns
      domain       VARCHAR(24) GENERATED ALWAYS AS (lower(substr(email, instr(em
                                      error here ---^

The DDL for the table is:
create table email
(
   email_id     INTEGER
      primary key autoincrement,
   source       CHAR(1), -- A=Account,C=Contact
   source_email VARCHAR(48),
   is_valid     CHAR(1),
   email        VARCHAR(48),
   domain       VARCHAR(24) GENERATED ALWAYS AS (lower(substr(email, instr(email, '@') + 1)))
);

I am assuming that lower(), substr(), and instr() are all deterministic, right?
This DDL works in sqlite3 v3.37.0.

Sure! Fixed in 0.21.9.

Wow, talk about service!  Thanks.
P.S. I have another one for you, slightly harder I expect.  Issue pending.


Documentation site is down

Summary of problem or feature request

Documentation Site is Down!
Code snippet of problem
System details

Operating System: Mac OS
PHP Version: 7.0
Laravel Version: 5.2
Laravel-Datatables Version: 6.29.3

The docs is available on github via this repo https://github.com/yajra/laravel-datatables-docs.

Not much on adding as a service on there.

#2135


nitrocli: init at 0.9.0

Description of changes
Add nitrocli package:
"nitrocli is a program that provides a command line interface for interaction with Nitrokey Pro, Nitrokey Storage, and Librem Key devices."
https://github.com/d-e-s-o/nitrocli
Packages are available for:
Arch Linux: nitrocli
Debian: nitrocli (since Debian Buster)
Gentoo Linux: app-crypt/nitrocli ebuild
Ubuntu: nitrocli (since Ubuntu 19.04)
Nixpks already contains a module for Nitrokey devices and the "official" Nitrokey GUI.
The Nitrokey site links to the CLI tool here:
https://www.nitrokey.com/news/2017/nitrokey-app-library-and-cli
This package currently only supports the Linux platform, but it may be possible to package it to support Darwin too with some work.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

I've tested the tools work well, both using nix build and by adding my nixpkgs fork as an additional channel on my nixos system. nitrocli is a really great package and I hope we can get it into nixpkgs.
I haven't reviewed any packages yet, sorry. I'd like to be more involved in the project in the future.

Hi @RaitoBezarius @panicgh and @frogamic
Would any of you be interested in reviewing/co-maintaining a nitrocli package. I found you all in PRs for other nitrokey related packages so I thought you might be the right people to ask.
Thanks

Hi there, sorry, I don't own any of those Nitrokey devices.

@tarnacious I could help co-maintain, however I only have nitrokey 3 devices to test with.


doesn't compatible

this mod can't use with entity model feature mod, when i run the game it freeze at loading

Please elaborate!

Which resource-pack are you using? (not facing this issue with Fresh Animations)
Please send the log and crash report.
Have you tried testing with only this mod, EMF and the rp?


neovim: fix plugin loading order

fixes https://github.com/NixOS/nixpkgs/issues/188167
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

thank you very much that's very helpful. It looks good. I will have a better look at it later today and merge if I can't find any issue

I didn't look into the details, but I confirm that with latest nixpkgs some plugins (in my case vimtex) didn't work. This PR fixes the issue.
I suspect that this PR will fix #187465 too

the test fails without the fix so all good. I will add a comment about why we need to set the rtp in a follow up PR.


Transactions help

This is kind of a knex question, but since I'm using objection and the transaction.start wrapper has slightly different syntax than knex.transaction, I figured it's better to ask here. I'm trying to do this as the docs, but it seems like I'm dropping transactions occasionally and then my knex pool fills up and connections start to time out when they can't get a connection.
let trx;

return Promise.try(() => {
  return transaction.start();
}).then(trxObj => {
  trx = trxObj;
  // do a bunch of stuff with transactoin here
  return Foo.bindTransaction(trx). //..
}).then(() => {
  // more stuff with transaction
  return Bar.bindTransaction(trx) // ...
}).then(() => {
  // transaction queries complete
  return trx.commit();
}).then(() => {
  // no more transaction needed
  return Baz.query(). // ...
}).catch(() => {
  return trx.rollback();
})

I also have some methods inside of the above transactions that look like this:
class Foo extends Model {
  static aMethod (trx) { // trx passed in from outer method call.
    return Promise.try(() => {
      return Foo.bindTransaction(trx).query() // ...
    });
  }
}

and these will get called from the first chain, like
Foo.aMethod(trx);

Is there a better way to do this? For instance, should I be using a new transaction.start() call in every method that is part of a transaction, and let the database figure out the hierarchy? If I did that, would the outer transaction get rolled back if any inner transactions fail?
Also, is there any better way to debug transactions to see which calls are causing the transactions to hang (i.e., are not calling commit or rollback)? I think I've got both commit and rollback exactly once for every call to transaction.start, but maybe I'm missing something else.
Thanks.

@elhigu Is the knex master and could probably answer this question better.
You shouldn't start multiple transactions if a single transaction is what you need. I cannot see anything wrong with your code that would cause leaked transactions.

@anyong It would be helpful if you could provide complete example which breaks your transactions. I don't see much wrong in your code example which you have sent so far...
How are you passing knex connection to transaction.start()? In objection examples one passes some model, which is bound to knex connection as a parameter to start() method.
here is example from objection docs:
objection.transaction.start(Person).then(function (transaction) {
  trx = transaction;
  return Person
    .bindTransaction(trx)
    .query()
    .insert({firstName: 'Jennifer', lastName: 'Lawrence'});
...

@anyong Did you solve this problem? Can I close this issue?


A little question about the gating mechanism

Hi,
I just have a little question for the final line state = gate2([state, new_state, gate]). I am wondering whether new_state here is new_states? Thanks.

Happy Chinese New year,
Qiming

But there is a error when I use new_states to replace new_state.
The error is located on line 176.

It is called ValueError: Input 0 is incompatible with layer repeat_to_ctx: expected ndim=2, found ndim=3.

What I am doing is I fix the gate2 function as the following.

And then I remove the new_state in order to keep the ndim as same as repeat_toctx.
The program can run now.
My question is for gating mechanism, I see in the gate1, you use sigmoid and in the gate2 you design a new function xyg[2]*xyg[0] + (1-xyg[2])*xyg[1]. Can you explain a little bit to make it more clear? Thanks a lot!

Hello, it would be difficult to say without checking the older version. The state tensor might have different number of dimensions with would explain the error. I think what you did should work, just make sure to follow shape annotations at the end of the lines to correctly gate the right dimension. Hope that helps.

This issue has been solved by that following issue.
https://github.com/nuric/deeplogic/issues/14


Abstract current AccessRoleProvider and implement as RbAclAccessRoles…

…Provider for use with WebAC.
Addresses FCREPO-1716

Resolved with: https://github.com/fcrepo4/fcrepo-module-auth-rbacl/commit/9e284e64cc982c9cea2e1fb116c9f736001fc429


beta user service refactor typo

There's a typo in "or password":

Also, it may be good to disable the "Login" button here with the text "loading..."/"logging in..." after the login button is clicked.
Looking much better though!

yes, that was identified, thanks
On Mon, Mar 19, 2018 at 2:46 PM, nconrad<EMAIL_ADDRESS>wrote:

There's a typo in "or password":
[image: image]
https://user-images.githubusercontent.com/1194246/37615323-01aaa37a-2b7b-11e8-880a-e2f5dd7b8860.png
Also, it may be good to disable the "Login" button here with the text
"loading..."/"logging in..." after the login button is clicked.
Looking much better though!
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/PATRIC3/patric3_website/issues/1922, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AMuN2C4IaxfQpxw-FWL_43C9L8vva1xIks5tf_0fgaJpZM4SwtA9
.

--
Josh Sherman
https://web-jam.com
https://www.linkedin.com/in/joshuavsherman/
540-494-8035


Respect unread message status from "mark as unread" in webapp

In zulip/zulip#2676, we are implementing a "mark message as unread" option.
When a message is marked as unread in the webapp, we should make sure it appears as unread in the mobile app as well.

(The server side of the feature was merged a few months ago as https://github.com/zulip/zulip/pull/21252 , after the API feedback we got from Wesley's #4790. The web/desktop client side is still pending, or at least the client UI for actually marking things unread is still pending, but having the server side means the API is committed and makes it possible to merge client implementations.)


Broken reference to default JUnit runner in Please 16.20.0-beta.16

As of Please 16.20.0-beta.16, //_please:junit_runner no longer exists, presumably because of https://github.com/thought-machine/please/pull/2429 - I'm guessing the default value of JunitRunner should now be //tools/junit_runner.

Fixed by #11 - thanks, @Tatskaari 🙂


Migration crashes creating a function on Postgres

Hi Prisma Team! Prisma Migrate just crashed. I used the following SQL migration. It was created with createOnly flag and later added:
--
-- RLS Helpers
--
CREATE OR REPLACE FUNCTION current_user_id() RETURNS string
    LANGUAGE sql STABLE
    AS $$
    SELECT current_setting('userId')::string;
$$;

In addition I am using a custom schema and user to create/connect to the database, so I have:
DATABASE_URL=postgresql://MYUSER:MYPASS@localhost:5432/MYDB?schema=MYSCHEMA
SHADOW_DATABASE_URL=postgresql://postgres:pgpass@localhost:5432/MYDB?schema=MYSCHEMA

I can see that the tables are created into my schema, but also into public schema.
Command
migrate dev
Versions

Name
Version

Platform
darwin

Node
v16.16.0

Prisma CLI
3.14.0

Engine
2b0c12756921c891fec4f68d9444e18c7d5d4a6a

Error
Error: Error in migration engine.
Reason: [libs/sql-schema-describer/src/postgres.rs:1039:28] no entry found for key

Please create an issue with your `schema.prisma` at
https://github.com/prisma/prisma/issues/new

Hey, can you try again with 4.5.0? We think this could be fixed already. Thanks!

@kevinmamaqi Just tested your SQL locally with Prisma v4.6.1 and it throws an error near string.
You can try to change it to text or uuid.
- CREATE OR REPLACE FUNCTION current_user_id() RETURNS string
+ CREATE OR REPLACE FUNCTION current_user_id() RETURNS uuid
    LANGUAGE sql STABLE
    AS $$
-     SELECT current_setting('userId')::string;
+     SELECT current_setting('userId')::uuid;
$$;


Check the ActionCable connection on stimuluate

Feature
Description
Raise and exception if stimuluate is called before the ActionCable connection is open and ready.
Checklist

[x] My code follows the style guidelines of this project
[x] Checks (StandardRB & Prettier-Standard) are passing

This is a really good step in the right direction.

Can we also merge #86 alongside this? It probably needs to be rebased, but conceptually this is valid and viable.
What happens if stimulate is triggered by a declared reflex? I guess the error will raise but there's no opportunity to capture it.

👆🏻 2. was also my first thought?

I'm not sure how I feel about #86 after revisiting it. I now consider it to be a concern that should be managed by users of the library. But, we can and should provide documentation to help users understand how to best work with the socket connection in their controllers. Here's an example:

export default class extends ApplicationController {
  connect () {
    super.connect()
    this.doStuff()
  }

  doStuff () {
    if (!this.isActionCableConnectionOpen())
      return setTimeout(this.doStuff.bind(this), 10)
    this.stimulate('ExampleReflex#do_stuff')
  }
}

This is already a problem today. The primary difference is that users don't currently get a helpful error message. I expect that in the future we may be able to implicitly check the connection status on stimulate and retry until the connection is ready, but we'll need to be thoughtful about this. Also, I see that feature as landing as a separate feature in a new PR.

I hope you revisit your revisitation! I believe that having the option to use style cascading (as nature intended) to hide or change UI items that aren't currently available is useful and powerful. Having to write a bunch of event handlers to do the same thing is just boilerplate.

I'm excited to help you flesh this out going forward. It's surprising to me that it hasn't been the source of more issues. I know that my Snake demo - aside from being thoroughly silly - frequently doesn't work if you don't wait a few seconds for WS to upgrade the connection.

You talked me into it :)


[IO] Replace Diff with fork version

No BC breaks this time.
This will provide an upgrade path to producing diff's with linenumbers.
closes https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/2993

Thank you @SpacePossum.


UDP publishing using docker

Which version are you using?
v0.0.0
Which operating system are you using?

OS

[ ] Linux
[x] Windows
[ ] macOS

Architecture

[ ] amd64
[ ] arm64
[ ] arm7
[ ] arm6

Describe the issue
Description
For an application, I want to publish an UDP stream to the server. Once published I want to open it with vlc or ffplay. Using TCP, it works, but with UDP, it won't.
I start the server with
docker run --rm -it -e RTSP_PROTOCOLS=udp -p 8554:8554 aler9/rtsp-simple-server
I publish a stream with ffmpeg
./ffmpeg -i testVideo.mp4  -rtsp_transport udp -f rtsp rtsp://localhost:8554/mystream
I get the following error
2021/02/23 10:23:43 [I] [1/0/0] [client <IP_ADDRESS>:59268] connected (plain) 2021/02/23 10:23:43 [I] [1/1/0] [client <IP_ADDRESS>:59268] is publishing to path 'mystream', 1 track with udp 2021/02/23 10:23:53 [I] [1/1/0] [client <IP_ADDRESS>:59268] ERR: no UDP packets received recently (maybe there's a firewall/NAT in between) 2021/02/23 10:23:53 [I] [0/0/0] [client <IP_ADDRESS>:59268] disconnected
From Wireshark I can see "destination unreachable (port unreachable)" packets
Starting the server with this command line get ffmpeg to block
docker run --rm -it --network=host aler9/rtsp-simple-server
ffmpeg :
 ./ffmpeg -re -stream_loop -1 -i testVideo.mp4 -f rtsp rtsp://localhost:8554/mystream
errors:
Could not write header for output file #0 (incorrect codec parameters ?): Immediate exit requested Error initializing output stream 0:0 --
Everything works fine using the windows precompiled binaries, so I assume it's a network problem.
Did you attach a network dump?
no

Hi,
I've encountered similar issue on Linux Docker (I can not use host network mode in my scenario) but I've manged to overcome it by disabling userland proxy in docker daemon. It can be done in Linux by adding to docker daemon config file and restarting daemon:
/etc/docker/daemon.json
{
"userland-proxy": false
}
With this docker daemon option host networking is not required, exposing udp ports is sufficient.
Although docker on Windows requires this option to allow localhost connections to be forwarded so this probably can not be used in your scenario. I think this may explain also why UDP connection to docker on Windows is not working as expected.

Unfortunately RTSP with UDP requires a direct connection between client and server - i'm working to add support for another protocol (SRT) that doesn't require it.


[Suggestion] Allow multiple markers

First of all, Thanks MChristopher, I really appretiate the work that's gone in to making this wonderful program, I however have several friends who live sort of close to me but JUST out of reach from the default "7" radius, However, increasing it dramatically increases the update time so it's a bit pointless when none of us go very far to find pokemon.
My idea would be to allow multiple map markers at set radius' (E.g. I'd have one near my house with a radius of 2, and one near my friends' houses with a radius of 2 each)
If this is possible I'd really like to see it implemented however if you have no time to do something like this yourself, that's fine, it's more of an ease of use thing anyway.
Thanks again for all the work you've put into this already and I look forward to see what the future brings :)

I could see this working if they allowed multiple accounts, and then on the sign-in screen you can associate markers/ location points with login accounts. So that you can use one account for your house, and one for your friends.

This would be actually nice if you can use multiple logins to put markers in several places, right now using 3 windows of the same program and then restarting just resets all of the accounts to the last one used, even the long/lat is the same.


Using it on Node-Red call service.

Hi guys, im attempting to use it with Node-Red as well.
HA automations is 100% fine, but on NR is kinda confusing.

No matter wich types of options I configure, I get this error msg.
I dont know if the JSON is correctly formatted, since NR example is like this.

This is the "example" JSON NR supplies, I only removed the URL and changed the entity.
Same error as well

The problem here is that image_entity expects a list but is given a string, which it then interprets as a list (each character as an item). This is why it says "c" (first letter in "camera.garagem") is not an entity.
I have no experience with Node Red but since it takes json, I think it should look like this:
"image_entity": ["camera.garagem"]

it worked!
thanks!!


Blank screen on step 4

I got to step 4 of the Friendly Eats Codelab, and served my app on localhost, but just got a blank grey screen.
I viewed the source and the code is there, but the "add mock data" button is not visible. It also has no event listeners other than load and storage.
When I ran the firebase serve command in the CLI, it seemed to hang partway through the process.
Also getting a "Failed to load resource" error on the Google auth API (I enabled Google Authentication in Step 3).

Just deployed my app to the Firebase server and got the following error:

Failed to load resource: the server responded with a status of 400 ()
FriendlyEats.js:38
code: "auth/operation-not-allowed"
message: "The given sign-in provider is disabled for this Firebase project. Enable it in the Firebase console, under the sign-in method tab of the Auth section."
proto: Error

But I have enabled authentication in the Firebase console.

Have you enabled all of the providers?  I think the important ones here are Google, Email, and Anonymous:

I don't think the instructions mention that you should enable Anonymous. I will do that, thank you.

I also missed out some crucial steps in the bit where it says "follow the instructions to set up your Firebase app" and takes you to a different screen (it would help if these were integrated into the Codelab).

Hi @vogelbeere . Did you solve that issue? I have the same problem and i can´t understand what´s happening.

Hi @vogelbeere . Did you solve that issue? I have the same problem and i can´t understand what´s happening.

I cannot remember but I think I did by following what was suggested.

Seeing the same issue
Followed all the instructions up to "Run Local Server".
on launching- http://localhost:5000
I see a screen with the following
You're seeing any restaurant located anywhere with any price sorted by rating
and not "add mock data" screen.
Am I missing something?
I have Anonymous  enabled. In the console for the index.html page I see  this error:
Uncaught Error in snapshot listener: FirebaseError: Missing or insufficient permissions
Should I be adding some other permissions?


Use own (webman) middleware interface

Allows to extend own Request/Response classes and use them in middleware.

Not actual anymore


Python SDK create_dataset is actually creating dataset in BQ

Expected Behavior
"Dataset" that was meant on the sdk is a collection of features selected by the user. While this term is also used in BigQuery, the SDK should not create a dataset whenever this function is called, rather just create a view in the feast dataset.
Current Behavior
It creates a new BigQuery Dataset.
Steps to reproduce
Use the quickstart:
feature_set = FeatureSet(entity="ride",
  features=["ride.log_trip_duration",
     "ride.distance_haversine",
     "ride.distance_dummy_manhattan",
     "ride.direction",
     "ride.month",
     "ride.day_of_month",
     "ride.hour",
     "ride.day_of_week",
     "ride.vi_1",
     "ride.vi_2",
     "ride.sf_n",
     "ride.sf_y"])
dataset_info = fs.create_dataset(feature_set, "2016-06-01", "2016-08-01")
dataset = fs.download_dataset_to_df(dataset_info, staging_location=STAGING_LOCATION)

dataset.head()

Specifications

Version: latest
Platform: as per suggested by install guide
Subsystem: as per suggested by install guide

Possible Solution

Fix create_dataset to create view in feast dataset instead
Write down dataset definition
Change to create_view?

Hey @budi. This issue is a bit confusing.
The idea of a dataset to the client should be a materialization of a feature set. Basically a collection of rows for specific columns (features). We should not care what happens in BQ in terms of naming (bq table vs dataset).
In this case I think it is important that we create a table as a snapshot of the data (not a BQ dataset) in order to make the dataset immutable. A view would not provide that. In the event that the user wants to have new data, they should create a new dataset using the same features and time range query.


Fixed ready event name for IE < 9 +  Fixed issue with 'interactive' document.readyState

I fixed wrong event name for IE < 9 which was added in this pr https://github.com/ofirdagan/cross-domain-local-storage/pull/27
Very sorry, my mistake.
Also
document.addEventListener('DOMContentLoaded') doesn't call handler if it was bound while 'interactive' document.readyState. So i changed 'DOMContentLoaded' event to 'readystatechange' with state filter.

released 2.0.5 :)

Thanks

@ofirdagan could you please also update npm and bower versions?

updated both at 2.0.5


Readme is incorrect or unclear about how to get metadata

Description of getting Width/Height from a JPEG are listed as:

MetaData
You can currently retrieve a JPEGs width and height. This only decodes the JPEGs header information and is very fast.
int width = jpegTransformer.getWidth();
int height = jpegTransformer.getHeight();

These methods exist on the  jpegkit.Jpeg class, not the jpegkit.JpegTransformer.  I'm not sure if that's an oversight in the intended implementation of JpegTransformer, or if the readme should be describing how to get metadata from a Jpeg object.
Edit: I just realized that there are other bits that seem to refer to the wrong class:

jpegTransformer.crop(cropRect);

JpegTransformer class has cropWithOffsets(...) and cropWithRegion(...) methods.  Jpeg class has the crop(Rect) method.

Thanks @joshuafarray we will look into this!


Handling logoutRedirect in a window opened with Office.Dialog API

Core Library
MSAL.js v2 (@azure/msal-browser)
Core Library Version
2.16.1
Wrapper Library
Not Applicable
Wrapper Library Version
none
Description
I have an auth flow implemented with the help of Office.Dialog API (this is a bit of a followup on a different issue I used to have). Everything works fine but I'm having trouble getting the logout flow to work as expected.
I'll start by describing what I expect the process to look like:

the user clicks on the "logout" button in the add-in
a separate window is opened using the Office.Dialog API (which I assume is required in order for this to work with the desktop Excel)
some back-and-forth messaging happens between the add-in (host) and the dialog in order to ensure proper communication channels have been established (and the dialog initialization did not fail)
when the add-in receives info the dialog is ready to proceed, it sends a message to the dialog indicating the logout flow should begin
the dialog, in response to that message, begins the logout flow using the logoutRedirect() method
the user is taken through the steps on login.microsoftonline.com
afterwards, the user is redirected back to the initial logout page in the dialog, which sends a message back to the host add-in that the flow finished successfully

However this does not happen as the flow triggered with logoutRedirect() stops at the following screen:

I see that the postLogoutRedirectUri is loaded in an iframe on that page, which would be enough to complete the flow but it seems not to have access to the Office APIs (Office.initialize method is not called). Even if it did, I'm not entirely sure it would recognize the host add-in as the recipient of the Office.context.ui.messageParent(). Without that I'm not entirely sure how to communicate back to the add-in that the logout succeeded 🤔
Since the success message is never triggered the add-in is unaware that the flow is finished. Moreover, if the user decides to close the dialog manually the add-in is informed that the window closed prematurely (thanks to the magic of Office.Dialog API – gotta love the error codes ❤ ) and shows a notification to the user asking them to retry the process.
I tried working around this issue using event API but to no avail – the add-in does not receive any events so I assume this doesn't work across windows? 🤔
Any suggestions on how to proceed would be most welcome 😅
MSAL Configuration
{
  "auth": {
    "authority": "https://login.microsoftonline.com/e4...",
    "clientId": "77...",
    "redirectUri": "https://localhost:3000/login.html",
    "postLogoutRedirectUri": "https://localhost:3000/login.html?logout"
  },
  "cache": {
    "cacheLocation": "localStorage"
  }
}

Relevant Code Snippets
const response = await msalInstance.handleRedirectPromise();

if (response) {
  // dispatchToHost – that wraps `Office.context.ui.messageParent()`
  // authLogoutSuccess – prepares the proper message to indicate a successfull logout
  dispatchToHost(authLogoutSuccess());
} else {
  await msalInstance.logoutRedirect({
    account: accountInfo,
  });
}

Identity Provider
Azure AD / MSA
Source
External (Customer)

Hi @kdmadej , could you please confirm that the postLogoutUri ("https://localhost:3000/login.html?logout") is registered as a replyUrl in your app registration? Thanks.
Here's our documentation on logout, please ensure that your configuration is correct and see if anything there can help fix your issue.
https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-browser/docs/logout.md

Yup, it is:

I even set it as a front-channel logout URL although I think that's redundant as I don't want to sign the user out across all apps.
I tried providing the postLogoutUri both on the config as well as the logout request just to be sure but both yield the same result. The final step is not redirecting back to it but instead it is loaded as an iframe in the dialog window.

@kdmadej can you try changing the URL to http:// instead of https:// and seeing if that changes anything. Usually redirect URIs have to use https://, but localhost is an exception to this rule.

The same result – stays on the "close all browser windows" screen and loads the redirect url in an iframe.

@kdmadej could you send me a Fiddler or network trace of this flow so I can see what's going on between the app and server? You can find my work e-mail on my GitHub profile so you can send it privately.


Enable jck-runtime-api-signaturetest and jck-runtime-api-javax_naming-spi on AIX

Add cmd to associate XVFB with one display on aix for jck test only
Enable jck-runtime-api-signaturetest and jck-runtime-api-javax_naming-spi on AIX

Signed-off-by: lanxia<EMAIL_ADDRESS>

Waiting for XVFB to be installed on all aix machines

The xvfb prereq on AIX machines is also applicable to openjdk tests (jdk_awt and jdk_swing, etc), we should likely open an issue at openjdk-infrastructure, so that we can re-enable those tests on more than just x86 machines (see: https://github.com/AdoptOpenJDK/openjdk-tests/blob/master/openjdk/playlist.xml#L139).

Internal aix machines are updated. PR is ready for review.

Change looks good @llxia , we will need to verify that Adopt & OpenJ9 machines have xvfb installed before merging this, correct?

This PR only applies for jck tests on AIX. Since we only run jck tests internally atm, we do not need to wait for Adopt & OpenJ9 machines to have xvfb installed.

I needed to view the whole file to see it, thanks!
Will merge now, and we can tidy up the setting of xvfb to encompass more types of tests later.


refactor!: convert library to ESM

Current state

@commitlint/lint is able to load the preset through @commitlint/load thanks to https://github.com/conventional-changelog/commitlint/pull/3776
@commitlint/cli is not able to load the preset because @commitlint/resolve-extends does not support ESM
"blocked by" https://github.com/conventional-changelog/commitlint/issues/3705
related: https://github.com/conventional-changelog/commitlint/issues/3768

Error log
$ npm run test:commitlint

><EMAIL_ADDRESS>test:commitlint
> commitlint --from HEAD~1 --to HEAD --verbose

/home/sherlox/workspace/INSURGENT_LAB/commitlint-config/node_modules/@commitlint/cli/lib/cli.js:123
        throw err;
        ^

Error [ERR_REQUIRE_ESM]: require() of ES Module /home/sherlox/workspace/INSURGENT_LAB/commitlint-config/index.js from<EMAIL_ADDRESS>not supported.
Instead change the require of /home/sherlox/workspace/INSURGENT_LAB/commitlint-config/index.js in<EMAIL_ADDRESS>to a dynamic import() which is available in all CommonJS modules.
    at /home/sherlox/workspace/INSURGENT_LAB/commitlint-config/node_modules/@commitlint/resolve-extends/lib/index.js:48:19
    at Array.reduce (<anonymous>)
    at loadExtends (/home/sherlox/workspace/INSURGENT_LAB/commitlint-config/node_modules/@commitlint/resolve-extends/lib/index.js:45:16)
    at resolveExtends (/home/sherlox/workspace/INSURGENT_LAB/commitlint-config/node_modules/@commitlint/resolve-extends/lib/index.js:25:22)
    at load (/home/sherlox/workspace/INSURGENT_LAB/commitlint-config/node_modules/@commitlint/load/lib/load.js:42:52)
    at async main (/home/sherlox/workspace/INSURGENT_LAB/commitlint-config/node_modules/@commitlint/cli/lib/cli.js:189:20) {
  code: 'ERR_REQUIRE_ESM'
}

Node.js v20.9.0

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


less confusing messages for toHaveBeenCalledWith

I've run into this a couple of times where the failure message for toHaveBeenCalledWith looks like you've passed in an array of arrays, when really it's just printing out the array of arguments arrays, so I fixed it to make it a bit more obvious what the heck was going on

+1 for clearer messages.
I just got the following beauty:
Expected spy actionSpy to have been called with [ [ { type : 'enter', from : 'green', to : 'orange' } ] ] but was called with [ [ { type : 'enter', from : 'green', to : 'orange' } ] ]
A bit confusing, right?
I know how this happened though, I passed the expected payload object within an array to the toHaveBeenCalledWith method.


feat: Introduce multiple value headers

The PR addresses https://github.com/coreruleset/go-ftw/issues/332

There is a lot of whitespace change in this PR. Is that intended?

@huberts90 Please revert the changes to white space. I'll wait with the review until then.

ping @huberts90

Ok, thanks for letting us know.


Better test assertion.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @angoenka

Unrelated failure in apache_beam.transforms.userstate_test.StatefulDoFnOnDirectRunnerTest.test_dynamic_timer_clear_then_set_timer

Run Python PreCommit

I think this broke postcommits cc: @TheNeuralBit
E         apache_beam.runners.dataflow.dataflow_runner.DataflowRuntimeException: Dataflow pipeline failed. State: FAILED, Error:
E         Traceback (most recent call last):
E           File "apache_beam/runners/common.py", line 1404, in apache_beam.runners.common.DoFnRunner.process
E           File "apache_beam/runners/common.py", line 624, in apache_beam.runners.common.SimpleInvoker.invoke_process
E           File "/home/jenkins/jenkins-slave/workspace/beam_PostCommit_Python38/src/sdks/python/apache_beam/io/gcp/bigquery_json_it_test.py", line 103, in process
E             self.assertEqual(country_expected, country_actual)
E           File "/usr/local/lib/python3.8/unittest/case.py", line 911, in assertEqual
E             assertion_func = self._getAssertEqualityFunc(first, second)
E           File "/usr/local/lib/python3.8/unittest/case.py", line 892, in _getAssertEqualityFunc
E             asserter = self._type_equality_funcs.get(type(first))
E         AttributeError: 'CompareJson' object has no attribute '_type_equality_funcs'
E
E         During handling of the above exception, another exception occurred:
E
E         Traceback (most recent call last):
E           File "/usr/local/lib/python3.8/site-packages/dataflow_worker/batchworker.py", line 646, in do_work
E             work_executor.execute()
E           File "/usr/local/lib/python3.8/site-packages/dataflow_worker/executor.py", line 208, in execute
E             op.start()
E           File "dataflow_worker/native_operations.py", line 38, in dataflow_worker.native_operations.NativeReadOperation.start
E           File "dataflow_worker/native_operations.py", line 39, in dataflow_worker.native_operations.NativeReadOperation.start
E           File "dataflow_worker/native_operations.py", line 44, in dataflow_worker.native_operations.NativeReadOperation.start
E           File "dataflow_worker/native_operations.py", line 54, in dataflow_worker.native_operations.NativeReadOperation.start
E           File "apache_beam/runners/worker/operations.py", line 514, in apache_beam.runners.worker.operations.Operation.output
E           File "apache_beam/runners/worker/operations.py", line 226, in apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive
E           File "apache_beam/runners/worker/operations.py", line 893, in apache_beam.runners.worker.operations.DoOperation.process
E           File "apache_beam/runners/worker/operations.py", line 894, in apache_beam.runners.worker.operations.DoOperation.process
E           File "apache_beam/runners/common.py", line 1406, in apache_beam.runners.common.DoFnRunner.process
E           File "apache_beam/runners/common.py", line 1478, in apache_beam.runners.common.DoFnRunner._reraise_augmented
E           File "apache_beam/runners/common.py", line 1404, in apache_beam.runners.common.DoFnRunner.process
E           File "apache_beam/runners/common.py", line 623, in apache_beam.runners.common.SimpleInvoker.invoke_process
E           File "apache_beam/runners/common.py", line 1585, in apache_beam.runners.common._OutputProcessor.process_outputs
E           File "apache_beam/runners/worker/operations.py", line 226, in apache_beam.runners.worker.operations.SingletonElementConsumerSet.receive
E           File "apache_beam/runners/worker/operations.py", line 893, in apache_beam.runners.worker.operations.DoOperation.process
E           File "apache_beam/runners/worker/operations.py", line 894, in apache_beam.runners.worker.operations.DoOperation.process
E           File "apache_beam/runners/common.py", line 1406, in apache_beam.runners.common.DoFnRunner.process
E           File "apache_beam/runners/common.py", line 1494, in apache_beam.runners.common.DoFnRunner._reraise_augmented
E           File "apache_beam/runners/common.py", line 1404, in apache_beam.runners.common.DoFnRunner.process
E           File "apache_beam/runners/common.py", line 624, in apache_beam.runners.common.SimpleInvoker.invoke_process
E           File "/home/jenkins/jenkins-slave/workspace/beam_PostCommit_Python38/src/sdks/python/apache_beam/io/gcp/bigquery_json_it_test.py", line 103, in process
E             self.assertEqual(country_expected, country_actual)
E           File "/usr/local/lib/python3.8/unittest/case.py", line 911, in assertEqual
E             assertion_func = self._getAssertEqualityFunc(first, second)
E           File "/usr/local/lib/python3.8/unittest/case.py", line 892, in _getAssertEqualityFunc
E             asserter = self._type_equality_funcs.get(type(first))
E         AttributeError: 'CompareJson' object has no attribute '_type_equality_funcs' [while running 'Validate rows']

apache_beam/runners/dataflow/dataflow_runner.py:1672: DataflowRuntimeException


in script ./Room.py:54 invalid syntax (simple.py, line 54)

Problem Description
A clear and concise description of what the bug is.
Steps to reproduce the behavior:
mitmdump -s Room.py
it shows:
in script ./Room.py:54 invalid syntax (simple.py, line 54)
System Information
Mitmproxy: 7.0.0
Python:    3.9.6
OpenSSL:   OpenSSL 1.1.1k  25 Mar 2021
Platform:  Windows-10-10.0.19041-SP0

What is Room.py?


hls error 4 on replay attempt

Browser: any browser I've tried so far
OS: any I've tried so far
Clappr Version: 0.4.2 / latest, regression in this aspect from 0.4.1
Steps to reproduce:

go to http://clappr.io/demo/#dmFyIHBsYXllckVsZW1lbnQgPSBkb2N1bWVudC5nZXRFbGVtZW50QnlJZCgicGxheWVyLXdyYXBwZXIiKTsKCnZhciBwbGF5ZXIgPSBuZXcgQ2xhcHByLlBsYXllcih7CiAgc291cmNlOiAnaHR0cHM6Ly90ZXN0LXN0cmVhbXMubXV4LmRldi94MzZ4aHp6L3gzNnhoenoubTN1OCcsCiAgcG9zdGVyOiAnaHR0cDovL2NsYXBwci5pby9wb3N0ZXIucG5nJywKICBtdXRlOiB0cnVlLAogIGhlaWdodDogMzYwLAogIHdpZHRoOiA2NDAKfSk7CgpwbGF5ZXIuYXR0YWNoVG8ocGxheWVyRWxlbWVudCk7Cg==
play until end
after poster appears try to play again
player hangs, depending on devices shows hls error 4

Expected: replay should work
Did you try to reproduce this issue at http://cdn.clappr.io/
Yes, see above.

Exactly the same case as my issue here: https://github.com/clappr/clappr/issues/1982. So, it seems I'm no the only one.

I'm having the same issue, too.

I could reproduce the issue, i proposed a fix in Clappr core.

@blacktrash is your issue fixed with Clappr 0.4.3 ?

@blacktrash is your issue fixed with Clappr 0.4.3 ?

@kslimani, yes indeed, it is. As can be verified in the demo as well.
Sorry for not getting back earlier. Closing.

@kslimani, yes indeed, it is. As can be verified in the demo as well.
Sorry for not getting back earlier. Closing.


Publication Dates Showing on Pages

It seems that dates should only show on blog posts, not Pages. Many page dates are either irrelevant or false (like the search page).

Fair point. I will consider making it optional in settings or potentially using the last updated date vs the publish date, if that's possible.

Next update will change pages to "last modified". I will consider making that optional in the future.
Starting to get concerned I'm adding too many settings to the plugin though! :-)

Going to convert this to a discussion so others can weigh in...


ROX-11894: Skip unauthorized error messages when fetching image signatures

Description
When an issue occurs during authentication with a registry, i.e. the wrong credentials are used, the error returned by the call FetchSignaturesForReference will be of the type registry.HttpStatusCode.
Previously, we only expected either a transport.Error or a error.Wrap which contained a url.Error and subsequently a registry.HttpStatusCode error.
This led to additional logs being printed within central logs when credentials were used that didn't fit for a registry. Those logs are false, as they are not indicating an actual error within the signature fetching, as it will
not stop the enriching of the image.
Now, instead of casting the errors, we use errors.As. This way, we can skip unwrapping errors manually, which was the issue beforehand of not casting the plain registry.HttpStatusCode error.
Testing Performed

see added unit tests.
Manual tests:

Use a any registry of your liking (quay.io/docker.io/demo.harbor.io).
Create a private repository, if you do not already have one.
Create an image integration for the registry but with wrong credentials.
Deploy a pod, observe that no unauthorized log messages are printed.

Current dependencies on/for this PR:

master

PR #2589   👈

This comment was auto-generated by Graphite.

/retest


Proper secrets mount in generated pipelines

Hi there,
Seems the Vault credentials have been missing when running errand from generated pipelines. We haven't tested it unfortunately, as we still don't have the CF pipeline working, which should happen soon. In the meantime @dennisjbell could you confirm that these Vault environment variables are indeed required?
Then, we've added the GENESIS_SECRETS_MOUNT env var, so that genesis invocations in pipeline task get their genesis.secrets_mount forced to the correct value.
Please note that this code is not tested yet, thus the Draft PR. I'll update here when it is.
Best,
Benjamin

Canceling this PR in favor of #508.


Add tests with the internal kotlin compiler framework

Currently, tests don't work on CI because of a strange error. We will fix it in the future versions


modalBottomSheet does not respond to keyboard

If I put a text widget on a modelBottomSheet, then when the keyboard comes up it covers the bottom sheet. In other words, the contents do not push up along with the keyboard.
I have only tested this on iOS.

Closing this as dup of https://github.com/flutter/flutter/issues/18564.


Optimized Team Cards using CSS Grid for mobile View.

The cards used to overlap and misalign on smaller screen sizes, I fixed it by setting them into a grid . Also fixed the navbar for mobile view.
Github pages Preview: https://kishorbalgi.github.io/sushiksha-first-contributions/

hey looks great! only problem now appears to be that the cards are closer to the nav bar in teams. looks to be a padding issue. would be great if you could fix that as well.


Setup github actions for CI

Currently (from the old times) building is done by Travis. If we should change it should also remove travis build file and badge.

Closed in favor of #76


WAL-664: Feature/xstate onboarding

Add xstate to the wallet, so we can start using state machines to handle flows in the wallet
Move Onboarding screen classes to functional components
Add test support

updated login and onboarding machine to wait for login to complete, without blocking individual redux actions that can also be called from elsewhere. Main solution is to split the setting the active user from the login success. The last one now also sets a login time. So we are fully logged in case there is an active user and there is a login time. We could not move the active user to the end, as that user is needed for other actions and binding contacts/vcs to the user.


[MenuItem] Menu overwrites theme styles for MenuItem

Problem Description

MenuItem doesn't respect the selectedTextColor defined in a theme. It looks like it is being overwritten here:
https://github.com/callemall/material-ui/blob/7177973d84bcd1a792f720588fd5df45ff965d58/src/Menu/Menu.js#L534
Versions

Material-UI: v0.15.0-alpha.2
React: 0.14.8
Browser: Chrome

I'd like to see this resolved as well.

@bschnelle Please don't just +1 issues - it spams the maintainers. Use reactions for that instead.
If you would like to see this fixed, the best bet it to submit a PR to fix it.

We have been porting the component on the v1-beta branch. We reimplemented it from the ground-up. While we haven't tested it, I think that the issue is most likely fixed on that branch. Hence, I'm closing it.
Still, we will accept PR fixes until v1-beta takes over the master branch.


Added federated OIDC JWT support.

In response to issue #671, I took a pass at adding in capability of using OIDC JWTs. Completed the CLA.

Thank you for your contribution to Go-AutoRest! We will triage and review it as soon as we can.
As part of submitting, please make sure you can make the following assertions:

[x] I've tested my changes, adding unit tests if applicable.
[ ] N/A - No new files I've added Apache 2.0 Headers to the top of any new source files.

Friendly ping if a reviewer or maintainer can take a look at this.

Yeah, I don't see any strong reason that the JWT would need to be exported in this instance. I updated the PR to make it internal.

Anything still blocking this? I opened up two downstream issues where I would love to implement workload identities as soon as this is merged.

There's an open question about how to handle the JWT expiring.  @karlschriek how is your app handling this?

We use this for "Azure Workload Identities" on Kubernetes. Essentially we annotate a Pod's ServiceAccount, and that leads to the following vars being injected into the Pod, as follows (note the token expiry annotation).
apiVersion: v1
kind: ServiceAccount
metadata:
  name: external-dns
  namespace: external-dns
  labels:
    azure.workload.identity/use: 'true'
  annotations:
    azure.workload.identity/client-id: bbbbbbbb-xxx-yyyyy-mmmm-rrrrrrrrrr
    azure.workload.identity/service-account-token-expiration: '86400' # expiry after one day
    azure.workload.identity/tenant-id: yyyyyyy-xxx-zzzz-xxxx-rrrrrrrrrrrrr

Starting a Pod with the above service account results in the following ENV vars being mounted.
AZURE_AUTHORITY_HOST: https://login.microsoftonline.com/
AZURE_CLIENT_ID: bbbbbbbb-xxx-yyyyy-mmmm-rrrrrrrrrr
AZURE_FEDERATED_TOKEN_FILE: /var/run/secrets/azure/tokens/azure-identity-token
AZURE_TENANT_ID: yyyyyyy-xxx-zzzz-xxxx-rrrrrrrrrrrrr

In addition, a JWT token is mounted at the file location /var/run/secrets/azure/tokens/azure-identity-token.
My understanding is that after 86400 seconds the token at that location will be refreshed, i.e. the contents of the file is replaced (I cannot 100% confirm this, but that is what I assume happens). I noticed that the adal module has token refresh callbacks, though it isn't clear to me how they work. Am I to take from the comments above that these cannot be used to automatically refresh the token? I our case "refreshing" the token in-memory would simply mean reading it from the same location on disk again.

By far the most convenient on client side would be to be able to pass for example adal.NewServicePrincipalTokenFromFederatedToken(*oauthConfig, awiClientId, jwtDateTime, expirySeconds, env.ResourceManagerEndpoint) instead have adal just look up the token again after expirySeconds has passed. Is there any feasible way to imlement this?

Since the JWT has it's own expiry, there isn't a way to get refresh tokens using the JWT. Rather we are wrapping around this call to get a new JWT and then a new Azure access token when needed. Getting the JWT will be highly dependent on the Identity Provider in use.


support npm shrinkwrap files, condense npm styles

"Condense NPM styles"? What do you mean?

@Alhadis : This block:
{ .npm-icon;             .medium-red; }

was repeated two times extraneously-- this commit also removes the duplication.


Garbage collect old CertificateRequests and Orders

It looks like old CertificateRequests and Order are retained forever. We have old completed ones floating around from weekly renewals going back 100 days to when cert-manager was installed. Will they eventually be garbage collected? Is there some configuration property we need to set? Is this functionality available in a newer version of cert-manager?
Environment details (remove if not applicable):

Kubernetes version: 1.18
Cloud-provider/provisioner: AWS
cert-manager version: 1.2.0
Install method: kubectl apply

/kind feature

Hi @rittneje,
CertificateRequest garbage collection can be controlled with the spec.revisionHistoryLimit option on Certificates. Most users have success with setting this value to 1. This will garbage collect both CertificateRequests as well as Orders.
This field was introduced in cert-manager v1.3
/close

@JoshVanL How about Certificates that are created automatically when using the Ingress annotation then? I did a quick search for relevant cert-manager annotations and I found no way to set revisionHistoryLimit there.


graphcool init only write package.json if none exists

Fixes #354

Anything else I can do to get this over the line?


Cloud SDK install: run install.sh outside the unzipped directory

We are hitting https://github.com/GoogleCloudPlatform/google-cloud-eclipse/issues/3157, which is not a usual situation. I think the situation happens when the Cloud SDK team rolls back a release, which makes installing the SDK effectively become a downgrading operation. Note
Welcome to the Google Cloud SDK!

Your current Cloud SDK version is: 205.0.0
Installing components from version: 204.0.0

The failure can be avoided if we run install.sh or install.bat outside the unzipped SDK root. Right now, we are intentionally running install.sh inside the SDK root.
The same cure to #651 should work, I believe. (Note #651 was when installing the Java component and upgrading the SDK. We didn't fix it for initially running the install script.)

Yall hacker think yall getting away with this ..stealing my apps. Changing things ..


ci: add master core install for lint/test/dev

@cbornet integration tests seem to be failing for unrelated reason - let me know if it's due to a change in core!

Hi, @efriis , thank you for taking care of this upgrade and spotting the test failure. It was indeed related to a randomness-induced flakiness, which is addressed in https://github.com/langchain-ai/langchain-datastax/pull/15. That should be merged momentarily - and this PR, once rebased, will certainly pass.
Thank you!

@efriis #15 has been merged. Can you rebase the PR ?

I should have been able to do it myself as one side was pure code and the other was pure dependencies. Could please @cbornet  or @efriis take a look?

oops thanks for merging!


[Campaign] Ensure Github workflow runs on docker image used by Production Distribution Build

Hi All,
This is coming from the campaign here:

https://github.com/opensearch-project/opensearch-build/issues/3966

Overview
We would like your CI check (specifically plugin build) in GitHub Repo to run on top of the Build Docker Images from production distribution pipeline.
This is to ensure every plugin repo will use the exact docker images we used in Jenkins build, to check their PRs and run tests before merging the code, so that issues can be detected earlier, and environment can be identical across teams.
Solutions
The Build Team has created a simple script to dynamically retrieve the current docker image name/tag, so everyone can easily pull the images for their CI checks.
We have a trial run of the above with k-NN team. The script retrieves the docker image dynamically, save output, and use it as the docker image to pull for the upcoming run:

https://github.com/opensearch-project/k-NN/pull/1099

Note that GitHub Actions only support LINUX docker container at the time of this writing, so we will add Windows containers later on as well as macOS.
Implementation Notes
We would like you to review above PR and implement similar changes. Note on line 33 of the above k-NN PR, -u and -p parameters needs to assign values accordingly.

OpenSearch Plugin:

          CI_IMAGE_VERSION=`opensearch-build/docker/ci/get-ci-images.sh -p centos7 -u opensearch -t build | head -1`

OpenSearch-Dashboards Plugin:

          CI_IMAGE_VERSION=`opensearch-build/docker/ci/get-ci-images.sh -p rockylinux8 -u opensearch-dashboards -t build | head -1`

Note that in the above k-NN PR, despite it being OpenSearch plugin, it still uses rockylinux8, as we initially plan to upgrade to rockylinux. We have since revert back to centos7 to support older versions of systems running k-NN lib. As a result, all OpenSearch plugins still uses centos7 for the time being, and all OpenSearch-Dashboards plugins can go to rockylinux8.
Completion Date
The above should be implemented by Nov. 1, 2023 (2023-11-01) by Plugin Owners to their repository.
And backport the changes to 2.x branch after merging in main branch.
Contacts
Please contact @peterzhuamazon for any questions on this campaign.
cc: @bbarani
Thanks.

[Triage] Hi @peterzhuamazon, thank you for filing this issue. At this time, the Security repos do not have enough context around the purpose of this change... It seems like this is adding responsibility to the Security repo without context for the change. Could you provide a case for this change and why we should address it on such an aggressive time scale (11/1)?
Thank you.

Hi @scrawfor99 I will work with you on this soon.
Thanks.

We have a new approach established here.
Please see this sample workflow file from Alerting for example:
https://github.com/opensearch-project/alerting/blob/main/.github/workflows/multi-node-test-workflow.yml
Thanks.

Hi @peterzhuamazon, thanks for following up. Looking at the workflow you shared, it seems like the idea is to just use the docker image to make things more standardized? Have there been issues around this area?
I am not against the change, just want to make sure we (security) have the context for the root of the change.

Hi @peterzhuamazon, just following up. Are you still pursuing this campaign? If not, we will close this issue. Thank you.

Hi @peterzhuamazon, thanks for following up. Looking at the workflow you shared, it seems like the idea is to just use the docker image to make things more standardized? Have there been issues around this area?
I am not against the change, just want to make sure we (security) have the context for the root of the change.

Yes @scrawfor99 this is for standardizing the github run env to be the same as on Jenkins during prod release build.

Due to the complexity of the workflows, we need to work with security team to understand the process before onboarding the docker images.

Hi @peterzhuamazon, just checking in if there was anything you needed from the Security repos at this time. Thanks

@reta to follow-up.

@peterzhuamazon This recommendation creates a circular dependency between security and OpenSearch-build repos please publish a GitHub action that can be consumed instead of a file [1]

[1] https://github.com/opensearch-project/opensearch-build/issues/4296


RHEL 7.4: Too many setuid bits removed

When running against RHEL 7.4 beta, these files have their setuid bits removed:

/usr/bin/su
/usr/sbin/netreport
/usr/libexec/openssh/ssh-keysign

This definitely breaks su. I don't know about the other files and if they should have setuid, but I suspect so.
I'll open a PR to add these files to the whitelist for RHEL 7.
As a workaround, add the files to the os_security_suid_sgid_whitelist var.
EDIT: I can't actually figure out how to apply the workaround - neither putting it into a group var nor in the playbook vars works... - I also don't know why it's acting as if os_security_suid_sgid_remove_from_unknown is set to true.
I am running ansibe <IP_ADDRESS>, installed the role by doing git clone https://github.com/dev-sec/ansible-os-hardening.git dev-sec.os-hardening in /etc/ansible/roles, and this is my playbook:
- hosts: '*'
  roles:
    - dev-sec.os-hardening

Hey @duk3luk3, you're right about the su-binary, this should be fixed. Do you want to create a PR for this?
As for ssh-keysign: According to this mailinglist-entry, the binary is only used for host-based authentication, which should never be used (we also disable it in ssh-hardening). That's why it is in the blacklist.
as for netreport:
 netreport tells the network management scripts to send a SIGIO signal to the process which called netreport when any network interface status changes occur.

So removing thew SGID from that binary is OK in my opinion.

fixed by https://github.com/dev-sec/ansible-os-hardening/pull/199


KNN interpolation

Hi
I want to use the KNN to interpolate the incomplete data matrix (one row represents a sample) which is not normalized.   If I normalized the incomplete data matrix  before KNN (only consider not NaN values), and then use the KNN to interpolate the values (which is NaN). I do not know whether I still need normalized the complete matrix.

You won't need to normalize it.


google-cloud-logging errors - uninitialized constant Google::Cloud::Logging::VERSION

google-cloud-logging 0.21.1
Google::Cloud::Logging::VERSION is passed as the value for app_version but it is not loaded by "google/cloud/logging"
https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/master/google-cloud-logging/lib/google/cloud/logging/service.rb#L74
irb(main):001:0> require "google/cloud/logging"
=> true
irb(main):002:0> logging = Google::Cloud::Logging.new
=> #<Google::Cloud::Logging::Project:0x007fe93cae35f8 @service=Google::Cloud::Logging::Service(...)>
irb(main):003:0> logging.sinks
NameError: uninitialized constant Google::Cloud::Logging::VERSION
	from /Users/remily/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/google-cloud-logging-0.21.1/lib/google/cloud/logging/service.rb:74:in `sinks'
	from /Users/remily/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/google-cloud-logging-0.21.1/lib/google/cloud/logging/service.rb:158:in `block in list_sinks'
	from /Users/remily/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/google-cloud-logging-0.21.1/lib/google/cloud/logging/service.rb:279:in `execute'
	from /Users/remily/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/google-cloud-logging-0.21.1/lib/google/cloud/logging/service.rb:157:in `list_sinks'
	from /Users/remily/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/google-cloud-logging-0.21.1/lib/google/cloud/logging/project.rb:498:in `sinks'
	from (irb):5
	from /Users/remily/.rbenv/versions/2.3.1/bin/irb:11:in `<top (required)>'
	from /Users/remily/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/cli/exec.rb:63:in `load'
	from /Users/remily/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/cli/exec.rb:63:in `kernel_load'
	from /Users/remily/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/cli/exec.rb:24:in `run'
	from /Users/remily/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/cli.rb:304:in `exec'
	from /Users/remily/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
	from /Users/remily/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
	from /Users/remily/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch'
	from /Users/remily/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start'
	from /Users/remily/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/cli.rb:11:in `start'
	from /Users/remily/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/exe/bundle:27:in `block in <top (required)>'
	from /Users/remily/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/friendly_errors.rb:98:in `with_friendly_errors'
	from /Users/remily/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/exe/bundle:19:in `<top (required)>'
	from /Users/remily/.rbenv/versions/2.3.1/bin/bundle:23:in `load'
	from /Users/remily/.rbenv/versions/2.3.1/bin/bundle:23:in `<main>'

I've reproduced this by loading the gem without use of a Gemfile and Bundler. Every other service requires the version file, but Logging does not. The reason we haven't seen this previously is because Bundler will load the gemspec, which also loads the version file.

Stackdriver Logging 0.21.2 is released with this fix. Thanks for being so diligent in examining these gems @remi!
https://github.com/GoogleCloudPlatform/google-cloud-ruby/releases/tag/google-cloud-logging%2Fv0.21.2
https://rubygems.org/gems/google-cloud-logging/versions/0.21.2


Oracle Implement Daily, Weekly, Monthly Graphs

What would you like to be added:
As part of UI/UX update for the oracles page. We would need the following:

Implementation of Daily, Weekly, Monthly Graphs (Awaiting https://github.com/DeFiCh/whale/pull/836)

/triage accepted
/area ui-ux oracles

Awaiting #853 instead


XD-3449a Introduce Task Exec Repository

This is just the interface that will be used by Task developers.  The impl will follow soon.

Closing for the moment.


[BUG] How to run on Ubuntu?

How to run on Ubuntu?

download
cd into folder
sh install.sh
. ./activate
cd taco-blockchain-gui
sh install-gui.sh
npm run electron &
???
Profit


Fail2ban fails to start after restarting container

It looks like fail2ban doesn't shutdown properly and after a container restart there's still a fail2ban.sock file left in /var/run/fail2ban/ directory.

Hi @arcaine2, I think I already faced this problem.
A check in start-mailserver.shmay solve the issue.
Could you provide a patch for that?

I'm new to that (on github) so please check if haven't mess up anything but this should do.

Should be fixed by #404