rkt: implement new image fetching behavior.

Implement fetching behavior as explained in the below tables (see https://github.com/coreos/rkt/issues/1196#issuecomment-127983674).
For fetch/run/prepare.

--no-remote
--force-remote
behavior
description

1
0
store
Just check the store

0
1
remote
Do remote download (handling caching logic for http(s):// and docker://)

0
0
store then remote
Default Behavior. Does store and if it doesn't return an image calls remote

behavior details related to provided image:

behavior
image
detailed behavior

store
file://
just use the file.

store
http(s)://
Search in the store remote table if the URL is available and use the saved BlobKey.

store
docker://
Search in the store remote table if the URL is available and use the saved BlobKey.

store
image name
Check store using GetACI(name, labels), if found use that image.

remote
file://
just use the file.

remote
http(s)://
Search in the store remote table if the URL is available. If it's available and the saved Cache-Control maxage > 0 determine if the image should be downloaded. If  it's not expired use the saved BlobKey. Otherwise download (sending if available the saved ETag). If download returns a 304 Not Modified use the saved BlobKey.

remote
docker://
Fetch using docker2aci.

remote
image name
Do discovery. If discovery is successful use the discovered URL doing the above remote http(s):// image case.

Remote behavior doesn't mean that the image will always be downloaded. For
http(s):// images ETag and Cache-Control max-age are handled.
If someone really wants to bypass remote caching logic a future option
(something like --no-cache) should be implemented.
What's missing is an additional caching check for docker:// images. This will
mimic the caching done for http(s):// URLs and will avoid downloading an image
on remote behavior if a cached image is considered good.  This will come in a
later patch.
This fetch behavior integrates with kubernetes in kubernets imagePullPolicy in this way:
Always: rkt fetch --force-remote image
IfNotPresent: rkt fetch image
Never: do not run rkt fetch image
Then the container can be prepared running rkt prepare --no-remote

@yifan-gu From the previous discussion I renamed --{no|force}-fetch to --{no|force}-remote to avoid confusion with the rkt fetch command, since rkt fetch fetches something but this can be in the local store or remote.
For this same reason, rkt fetch now has both the options like /run/prepare` behavior is the same.

@sgotti Thanks for the PR :) Nice work! LGTM overall excepts for some nits.
FWIW, in kubernetes currently, the image fetching logic is managed by the image puller which requires the container runtime to implement IsImagePresent() and PullImage() interface.
The PullImage() interface's behavior here is --force-remote.
This is mainly due to that we need to make it compatible with docker's interface. But maybe we can optimize for rkt later.

@yifan-gu Thanks for your review! Updated.

FWIW, in kubernetes currently, the image fetching logic is managed by the image puller which requires the container runtime to implement IsImagePresent() and PullImage() interface.
The PullImage() interface's behavior here is --force-remote.
This is mainly due to that we need to make it compatible with docker's interface. But maybe we can optimize for rkt later.

Ok. So that commit message part can be misleading. Should I remove it?

Sorry for dropping this.
This behaviour as described (here and https://github.com/coreos/rkt/issues/1196#issuecomment-127983674) looks great to me.
The one thing that comes up is around file:///. I've always resisted the idea of caching/indexing it in the past, but as things like https://github.com/coreos/rkt/issues/1350 show, it's not necessarily the most intuitive UX, I wonder if there's some room for improvement there.
Thanks @sgotti!!

@steveeJ mind providing another pair of eyes on this?

@jonboulle thanks!

The one thing that comes up is around file:///. I've always resisted the idea of caching/indexing it in the past, but as things like #1350 show, it's not necessarily the most intuitive UX, I wonder if there's some room for improvement there.

Sure. I'll try to give it a thought (I think it can be a future patch).

I came across the same thought as Jon while reading the code. Scheme file should not prevent caching. It would be nice if the image had a hash that could be compared to a stored image quickly, but this could be topic for another issue.
This was my first glimpse at the store code yet LGTM overall

@steveeJ @jonboulle file:// is interesting and can have an impact on the option names. I can think to implement it something like this:

behavior
image
detailed behavior

store
file://
a) compare the on disk file absolute path and size (are they enough?) with cached info from the storez or b) calculate the on disk file sha512 and search for an existing sha512 in the store (slow as it needs to read/uncompress the file but reliabe.

remote
file://
just use the file.

But doing this will clash with the remote name. For example an user should use --force-remote to force the use of the on disk file.

Another option will be to call them on the store side: --no-remote -> --store-only and --force-remote -> --no-store.
Thoughts?

I don't understand how --{force,}remote would semantically work with file://, so my feedback here is limited.
About the change detection: the filesize is not a reliable indicator as you mentioned, the hash of the file is. I'm still wondering why the ACI doesn't carry its digest or a timestamp at a known location where it can be read efficiently without hashing the file on every run. Especially with the stage1 this would make a huge difference since it's used on every run.

@steveeJ well, arguably neither of those are particularly reliable either as they could both trivially be faked. But for this use case we should probably just pick a heuristic and run with it since it is really a convenience behaviour. IMHO path + size + timestamp would be pretty safe, and then we could fall back to hash in the pathological case...

I want to target this for 0.9.0.

I don't understand how --{force-,}remote would semantically work with file://, so my feedback here is limited.

@steveeJ @jonboulle What I was trying to do is to match the file:// images with the two behaviors: store and remote. My doubt is that remote is a strange name for a local file. So I was asking what we can do to make the naming less confusing. For example, with my proposed behaviors (https://github.com/coreos/rkt/pull/1353#issuecomment-138684934) for file:// the store behavior will use a cached file in the store and remote will instead import the local file in the store. A user that wants to bypass the store should do something like rkt fetch --force-remote /path/to/file that IMHO looks confusing.
One solution will be to change the remote wording to something else or alternatively change the options to --no-remote -> --store-only , --force-remote -> --no-store to remove the remote word from the options. The above command will become rkt fetch --no-store /path/to/file
@jonboulle
Would you prefer that I add the file:// caching in this PR (will probably need a db schema migration for adding the related fileinfo fields) or in another PR on top of this?

I'm in favor of the --no-remote -> --store-only , --force-remote -> --no-store suggestion. I feel like it's a little less ambiguous about what's going to happen.

@jonboulle
Would you prefer that I add the file:// caching in this PR (will probably need a db schema migration for adding the related fileinfo fields) or in another PR on top of this?

sorry for the delay - happy for this to land in a follow up I think.

@sgotti A bunch of nits, but overall, this looks awesome.

My doubt is that remote is a strange name for a local file. So I was asking what we can do to make the naming less confusing. For example, with my proposed behaviors (https://github.com/coreos/rkt/pull/1353#issuecomment-138684934) for file:// the store behavior will use a cached file in the store and remote will instead import the local file in the store. A user that wants to bypass the store should do something like rkt fetch --force-remote /path/to/file that IMHO looks confusing.
One solution will be to change the remote wording to something else or alternatively change the options to --no-remote -> --store-only , --force-remote -> --no-store to remove the remote word from the options. The above command will become rkt fetch --no-store /path/to/file

I am kind of on the fence about this, personally I don't care that much about the "awkwardness" of --remote file:///.... Other opinions? @yifan-gu @philips @robszumski @iaguis @alban

+1 for the --no-remote -> --store-only , --force-remote -> --no-store.

Looks awesome to me!

I like --store-only and --no-store

Thank you all for the review. I forgot to say that I have updated the PR.

LGTM
Great work!

@sgotti Thanks for the work!

Forgot to mention: can someone kindly come up with something for the docs explaining this behaviour? :-)
One of those tables would fit in nicely.


What I studied today

Studying the MST basic concepts (practice using mobx-state-tree)

Good job!


The code in useage has something wrong

It is here.
b = drop_block(a, training)
when I use it to test,it cannot run.After I changed it as     b = drop_block(a, training=True)
The code could run.

Maybe the problem was caused by the tensorflow version, I'm using tensorflow 1.12.0 and the code is working fine on my computer.
I wrote an example in Google Colab, you can check it out from here: https://colab.research.google.com/drive/18eOcpTLH4xXpa4B75I62JJSgM49CxkGF

Maybe the problem is the tensorflow's version.My tensorflow's version is 1.2.1.
Thanks.


update doc block for static analyzer fix

if you use static analyzer like larastan with kavenegar will give you an error like this
Method App\Notifications\VerifySMSNotification::toKavenegar() should
         return Illuminate\Notifications\Messages\MailMessage but returns
         Kavenegar\Laravel\Message\KavenegarMessage.

@hosseinRezaei188 please review and merge this PR
thanks

Thank you for your PR.


Updated typings and tests for Navigation 1.1.0

Updated typings and tests to match the new version 1.1.0 of the Navigation Router
(I moved the tests inside a module, causing the diff to show the whole file has changed.)

@grahammendick thanks mate!

Thanks :smile:


Remove "Call for submissions" from news

The Call for submissions is closed and we need a replacement "news". I shamelessly copy/pasted from last year.

Approving in spite of the duplicate : so you can merge yourself after fixing

Yep.

Is this really how the review flag system is supposed to work?

That's how GH designed it.


clr-daypicker as a standalone calendar component

Summary
It would be nice to have daypicker as a standalone calendar component to use outside of the input components.
Currently, this component can't be used separately from the Date Picker due to service injections: No provider for ViewManagerService!
Motivation
To have ability show calendar in plain view, like it's in google calendar.
Does this change impact existing behaviors? If so how?
No, it shouldn't.
If this change introduces a new behavior, is this behavior accessible?
I think there is no new behavior, but the existing functionality is still sufficient.
Use case
Use it as a simple calendar to navigates through dates.
Examples

Workarounds
It seems there is no workaround to use it outside of the Date Picker at the moment.

Totally support that! Since there’s no time range selection component in Clarity, more flexibility with calendar parts would help.

@mathisscott Would we be building a generic calendar for Core as part of Datepicker?

@gnomeontherun
Yes. It would make sense for that to be a reusable component inside the datepicker drop down.

The feature request here has been captured into our list and we’re going to take it into consideration as we develop Clarity Core capabilities. In an effort to clean up our backlog and focus our attention, I’m going to close this as captured in our feature requests. Please follow our development and releases to see when we release relevant components to make this possible. Future feature requests can be made in our GitHub Discussions.


sh make.sh

I changed cur_dir path, but when i run sh make.sh (win64) Terminal display:
ValueError: path '/data/data2/a2jformer/camera_ready/dab_deformable_detr/ops/src/vision.cpp' cannot be absolute，
How can i solve this problem, Thanks

Thank you very much for your interest. I have never encountered your problem. In order to prevent conflicts, I deleted some compiled files in the folder, you can download and try again. In addition, I have not tested whether the code can be run under the Windows system. You can try to use Linux system. If it doesn't work, can you send me the compilation result and the code running platform? Thanks.

Thanks for your quick response, I will try it . Note: I noticed that you are a student at Huazhong University of Science and Technology, and I am currently studying in Wuhan, expressing my respect for your research！Thanks again

That's great! Maybe we can discuss together offline hhh~

When running program  sh make.sh , an error is reported
RuntimeError: Error compiling objects for extension


[SPARK-36674][SQL] Support ILIKE - case insensitive LIKE

What changes were proposed in this pull request?
In the PR, I propose to support a case-insensitive variant of the like expression - ilike. In this way, Spark's users can match strings to single pattern in the case-insensitive manner. For example:
spark-sql> create table ilike_ex(subject varchar(20));
spark-sql> insert into ilike_ex values
         > ('John  Dddoe'),
         > ('Joe   Doe'),
         > ('John_down'),
         > ('Joe down'),
         > (null);
spark-sql> select *
         >     from ilike_ex
         >     where subject ilike '%j%h%do%'
         >     order by 1;
John  Dddoe
John_down

The syntax of ilike is similar to like:
str ILIKE pattern[ ESCAPE escape]

Implementation details
ilike is implemented as a runtime replaceable expression to Like(Lower(left), Lower(right), escapeChar). Such replacement is acceptable because ilike/like recognise only _ and % as special characters but not special character classes.
Note: The PR aims to support ilike in SQL only. Others APIs can be updated separately on demand.
Why are the changes needed?

To improve user experience with Spark SQL. No need to use lower(col_name) in where clauses.
To make migration from other popular DMBSs to Spark SQL easier. DBMSs below support ilike in SQL:

Snowflake
Redshift
PostgreSQL
ClickHouse
Vertica
Impala

Does this PR introduce any user-facing change?
No, it doesn't. The PR extends existing APIs.
How was this patch tested?

By running of expression examples via:

$ build/sbt "sql/test:testOnly org.apache.spark.sql.expressions.ExpressionInfoSuite"

Added new test:

$ build/sbt "test:testOnly *.RegexpExpressionsSuite"

Via existing test suites:

$ build/sbt "sql/testOnly org.apache.spark.sql.SQLQueryTestSuite -- -z regexp-functions.sql"
$ build/sbt "test:testOnly *SQLKeywordSuite"
$ build/sbt "sql/testOnly *ExpressionsSchemaSuite"

Test build #143023 has started for PR 33919 at commit abe94f4.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47525/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47525/

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

Test build #143023 has finished for PR 33919 at commit abe94f4.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
abstract class LikeBase(left: Expression, right: Expression, escapeChar: Char)
case class Like(left: Expression, right: Expression, escapeChar: Char)

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

Test build #143026 has started for PR 33919 at commit f075720.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47528/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47528/

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

Test build #143026 has finished for PR 33919 at commit f075720.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
sealed abstract class LikeBase extends StringRegexExpression
case class Like(left: Expression, right: Expression, escapeChar: Char) extends LikeBase

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

Test build #143044 has started for PR 33919 at commit 8b895bc.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47547/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47547/

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

Test build #143048 has started for PR 33919 at commit fa78dbd.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47551/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47551/

Test build #143044 has finished for PR 33919 at commit 8b895bc.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class ILike(left: Expression, right: Expression, escapeChar: Char) extends LikeBase

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

Test build #143048 has finished for PR 33919 at commit fa78dbd.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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

Test build #143051 has started for PR 33919 at commit bd887d8.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47554/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47554/

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

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47559/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47559/

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

Test build #143051 has finished for PR 33919 at commit bd887d8.

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

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

Test build #143056 has finished for PR 33919 at commit 86abe1c.

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

Test build #143085 has started for PR 33919 at commit ae8af6c.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47587/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47587/

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

Test build #143089 has started for PR 33919 at commit 81c4eca.

Test build #143090 has started for PR 33919 at commit 8bf5b4f.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47591/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47591/

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

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47592/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47592/

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

Test build #143085 has finished for PR 33919 at commit ae8af6c.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class Like(left: Expression, right: Expression, escapeChar: Char)
case class ILike(

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

Test build #143089 has finished for PR 33919 at commit 81c4eca.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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

Test build #143090 has finished for PR 33919 at commit 8bf5b4f.

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

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

thanks, merging to master!


Grammar correction on front page

The message at the top of http://www.oldweather.org/ should read:
New site! Visit Old Weather: Whaling for ships' logs from whaling ships in the Arctic.

And the message on http://whaling.oldweather.org/#/ should read:
Check out other Old Weather projects!

wrong repo


How to compile libcurl work with grid proxies in RHEL

@bbockelm Please add your steps here.

AFAIK we also need cjson from CMSSW

So, libcurl includes code for multiple SSL backends.  By default on RHEL6 and 7, the libcurl backend is set to NSS which has no support for grid proxies (but there are workarounds).
What we do for CMSSW is compile libcurl with the OpenSSL backend, which has much better handling with certificates.
That said, it seems safe to assume that there's no control over the backend, particularly if we want to integrate with standard infrastructures instead of being inside the CMS ghetto.  Hence, we want the workaround!
Here's the best overview I'm aware of:
https://wiki.nikhef.nl/grid/Funny_Curly_things
For the CLI, you want to do something like this:
curl -s -S --cert ./rfcproxy --key ./rfcproxy --cacert ./rfcproxy --capath ./dir https://<IP_ADDRESS>:4433

That is, specify the proxy file as the X509 cert, X509 key, and the X509 ca cert file.  By providing this as the X509 CA cert in addition to the normal /etc/grid-security/certificates, it'll include the usercert in the proxy chain sent over TLS and cmsweb can utilize it.
I assume that each of the command line flags correspond to a separate option in the python & C API.
HTH


Shree: Watch technauto.com

Shree requests the watch of the watch_keyword technauto\.com. See the MS search here and the Stack Exchange search here.

technauto\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

!!/approve


How can I show github link url in cardview of list?

@SuSandiWai this is not possible.
You can either provide custom definition files for all the libs you use and include the repo link in the general description.
Or you just use the Libs object and it's API to build your own view showing the used libraries


Build errors when updating to 0.5

Use of undeclared identifier 'QMServicesManager'
Also I cannot revert back to 0.4.6.

Had to update import statements
Before
#import "QMServices.h"
After
#import <QMServices/QMServicesManager.h>
#import <QMServices/QMServices.h>


Safe and Blocked Lists

We need a way to grant end-users the ability to add messages sent to them to the safe or blocked sender lists. It looks like users used to be able to do that until October 21 or so.

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

ID: 417169b2-983d-314d-94fe-32cec2f5fc40
Version Independent ID: 620070c2-6311-a1fe-890d-a447a0994beb
Content: Safe sender and blocked sender lists in Exchange Online - Office 365
Content Source: microsoft-365/security/office-365-security/safe-sender-and-blocked-sender-lists-faq.md
Service: o365-seccomp
GitHub Login: @MSFTTracyP
Microsoft Alias: tracyp

@awsceris - Thank you for submitting feedback.
I think the best way forward is if you can open a service ticket in your tenant so this can get resolved ASAP. Based on outcome, let me know if it is something that can be called out in the docs.
If you don't mind please keep us posted here on the resolution so we can get this information you are discovering back into the docs.


The generated projection method is missing

Hi. Please let me open the issue.
I tried to generate code from GraphQL schema.
However, in some cases, the generated projection method is missing.
I use plugin - v4.2.0.
The below is the GraphQL schema and the generated code (projection) .
The generated code is code that is missing a method.

schema.graphql

type Query {
    shows(titleFilter: String!): [Show]
}

type Show {
    title: String!
    list1: [List1!]
    list2: [List2!]
}

interface List1 {
    id: String!
}

type List1A implements List1 {
    id: String!
    name: String!
    option: Option!
}

type List1B implements List1 {
    id: String!
    name: String!
    option: Option!
}

type List1C implements List1 {
    id: String!
    name: String!
    option: Option!
}

interface List2 {
    id: String!
}

type List2A implements List2 {
    id: String!
    name: String!
    option: Option!
}

type List2B implements List2 {
    id: String!
    name: String!
    option: Option!
}

type List2C implements List2 {
    id: String!
    name: String!
    option: Option!
}

type Option {
    name: String!
    memo: String!
}

ShowsList2List2BProjection.kt

package com.example.dgs.demo.generated.client

import com.netflix.graphql.dgs.client.codegen.BaseSubProjectionNode
import kotlin.String

public class ShowsList2List2BProjection(
  parent: ShowsList2Projection,
  root: ShowsProjectionRoot
) : BaseSubProjectionNode<ShowsList2Projection, ShowsProjectionRoot>(parent, root) {
  init {
    fields["__typename"] = null
  }

  public fun name(): ShowsList2List2BProjection {
    fields["name"] = null
    return this
  }

  public override fun toString(): String {
    val builder = StringBuilder()
    builder.append("... on List2B {")
    fields.forEach { k, v ->
        builder.append(" ").append(k)
        if(v != null) {
            builder.append(" ").append(v.toString())
        }
    }
    builder.append("}")

    return builder.toString()
  }
}

I think the following method should also be included.
public fun option(): ShowsList2List2BOptionProjection {
  val projection = ShowsList2List2BOptionProjection(this, root)
  fields["option"] = projection
  return projection
}

I don't know the cause for sure, but if I reduce the number of types that implement interface in GraphQL schema, this problem doesn't seem to occur.

Can you try with the latest release? We did fix an issue related to this.

Thank you to fix it. I tried by using latest version (v4.4.1).
It seems that issue was resolved.
By the way, is this bugfix related to https://github.com/Netflix/dgs-codegen/pull/79 ? I just want to know PR related to this issue.

Yes, that is the PR that fixes the problem.


Fixup minor typo in Readme

This PR just fixes up a minor type in the readme
aotolabel → autolabel

Thanks for the correction!


Suricata: Unable to edit action of a single rule when using a policy

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I have searched the existing issues and I am convinced that mine is new.

Describe the bug
With 21.1 it seems to be impossible to override the alert action of a single alert in Suricata at Services > Intrusion Detection > Administration > Rules when there is a policy that overrides the alert action of the ruleset containing the rule. You can set the action from "Drop" to "Alert" and hit "Save" followed by "Apply", but the setting never gets applied (or overwritten by the policy again?). The the action is still "Drop" and the traffic is actually dropped.
The issue is also mentioned here: https://forum.opnsense.org/index.php?topic=21212.0
To Reproduce
Steps to reproduce the behavior:

Create a policy to set the rule actions of a ruleset from "Alert" to "Drop"
Edit a rule that is included in the overwritten ruleset (https://opnsense.example.com/ui/ids#rules)
Set action to "Alert"
Hit save and apply
Override is not applied

Expected behavior
The override gets applied after hitting apply.
Environment
OPNsense 21.1-amd64

We should move the separate rules to the policy as well to fix this properly. The problem is that it removes the manual rules from the config if their the same as default, which doesn't work if a policy matches on the same case too. A quick temporary fix would be to not try to remove the rule after change, but as with all these manual adjustments it has a high risk of blowing up your config.xml.
Adding the sids to the policies and removing the actions on separate rules is likely the cleanest fix, I don't mind preparing a small fix to keep the current behaviour in between.
The downside of the proper fix is manual adjustments will vanish from the current rule page.
Already thought about this while working on the policies, but tried to limit the scope a bit and made sure the local adjustments are still being processed properly (highest priority), which doesn't help if we don't store them...

@AdSchellevis
please can you explain why @ashceryth  case can be workarouned (at least on my test VM) by changing status (enabled\disabled) first? so if default state of rule is "enabled and drop", matched policy action: Alert and GUI won't let me change the action then i can disable it first (rules goes to manual), change action to drop (default) and reanable (rule stays in manual policy)?

I hope now I understand and will not ask a stupid question
@AdSchellevis
please explain, do you think that saving such rules (with the default parameters, but overlapping the matched policy) will inflate the config more than saving the rules with the current rule-based management approach? (imho there should still be less of them than current "modified" rules on rule-based configs)
and could you consider adding a some "Reset rule" button in "Rule detail" modal to completely reset the rule parameters (delete from config.xml and assign matched policies)?:
sometimes it can be hard to remember why a rule got into "manual" policy — a change in status or action. and this would make it possible to return the rule to the matching policy for the cases described above (default parameters, but overlapping the matched policy)
thanks!

@kulikov-a the problem with the current single rule entries is that a single entry of about 7 bytes (the sid) is encapsulated in a container which is much larger. when moving them to the policies you would logically define a single policy and select multiple sids in it, which consumes way less space (and is easier to validate).
To some degree I expect complaints if we move the selection out of this window, which is also why I was a bit cautious to add the sids (plus a migration) in the first place, but in reality I don't think there's much choice here.

@AdSchellevis  thanks!
just trying to get a better understanding of how rules and policy processing works. just tell me if I bore you)
what if the "manual" field is added to the configuration in the "policies" section. and if the user touches the rule (it doesn't matter: changing its parameter from the default settings or vice versa by turning them back), then the user intentionally wants to remove this rule from under the policies and you we can put the rule's sid in this field? then at the time of creating the cache db a "manual" policy can be assigned to these sid's. will it inflate the config less?

@kulikov-a no problem, my original idea just ran into issues due to the Javascript in the browser rending way too slow.  https://github.com/opnsense/core/commit/a2a21829fae11a1ad6d738cbd2c1639687ee6f53 commit makes sure you can still use the custom rule based overrides, do you own maintenance and warn if there are many defined.

Thanks!! already trying to test


this.getCompilerApi().getCommand() do not return the current command

With your last commit all of the compile.js files in different projects do not run any longer.
Problem is this code:
   let command = this.getCompilerApi().getCommand();
  command.addListener("made", this.__onMade, this);

In the old version command was the actual used command derived from qx.tool.cli.commands.Command.
In the new version it's qx.tool.cli.Cli not the current command. So adding listeners will not work.
Any idea how to solve this?

None of the event based compile.js are working any longer

Question is if we should revert the last commit or if @johnspackman can provide a quick fix?

hmm, I havn't looked at the code but I suspect that this is an issue because compile.js is now loaded before a command is determined.  Where can I see this - is this apiviewer?

This example is package browser. Apiviewer has the same problem.
And you are right - load is called before command is ready.
IMHO we need a second call during the command creating phase


magic spell

please accept my request for hakcober fest its cpp  hackrrank problem

@mrigankabrahma Please give the problem statement in description.


DevEx: IFD caching investigation

All components in the cardano-node stack (plutus, ledger, consensus, the node itself etc) are expressed within the haskell.nix Haskell build infrastructure.
haskell.nix stretches the limits of what Nix itself provides, and so relies heavily on the input-from-derivation technique (IFD).
The IFD technique, while crucial for implementing the features necessary for haskell.nix, has an unfortunate property of causing un-cacheable builds on each developer's machine, each time a significant change in dependencies happens.
Sometimes these un-cacheable builds are massive.
This sometimes makes the developer experience very sluggish.
We have avenues of investigation into the key deficiency of IFD -- the lack of caching.

Closing this. If this is still relevant please reopen.


Fix crash for method cacheKeyForURL: when url is nil

New Pull Request Checklist

[x] I have read and understood the CONTRIBUTING guide

[x] I have read the Documentation

[x] I have searched for a similar pull request in the project and found none

[x] I have updated this branch with the latest master to avoid conflicts (via merge from master or rebase)

[x] I have added the required tests to prove the fix/feature I am adding

[x] I have updated the documentation (if necesarry)

[x] I have run the tests and they pass

[x] I have run the lint and it passes (pod lib lint)

This merge request fixes / reffers to the following issues: ...
Pull Request Description
In method cacheKeyForURL, when the url was nil, the app crashed. So I added a safe check on it.

@NSKevin thanks for this. I adapted a bit your fix. Since we have places where we use that key as a dictionary key, I preferred to return an empty string rather than nil when the url was nil. 1bf62d4


Remove empty test file

influxql/select_test.go is the right test file. cmd/influxd/run/select_test.go is not useful.

@li-ang Thanks. This file was added when I was trying to move tests out of server_test.go into logical groups. However, that was going to cause a lot of merge conflicts later so I reverted. It looks like one of the files never got deleted.
I'll merge on green. :+1:

Done ! @benbjohnson


Unable to resolve Raylib-cs dep using Rider IDE

I tried to install it through the dotnet cli but it says that no version <IP_ADDRESS> of Raylib-cs matches net6.0:
Chess-Challenge.csproj: [NU1100] Unable to resolve 'Raylib-cs (>= <IP_ADDRESS>)' for 'net6.0'.

Try install it from nuget

It was a permission problem with NuGet, I had to delete NuGet.Config and restart Rider.


Can I disable name-analyzed.sgf gernerating?

Sometime I only want to save json instead of analyzed.sgf, can I only save json files that would save some time?

We get JSON information while analyzing SGF, so even if we do not save analyzed.sgf, we cannot save any time.
And I'm sorry to tell you that I have no plan to add the option saving only JSON file.

I understand.


Build fails on React-Native 0.56

Build fails on a fresh install of React Native 0.56 with react-native-static-server. Seems like resources are missing.
:react-native-static-server:preBuild UP-TO-DATE
:react-native-static-server:preReleaseBuild UP-TO-DATE
:react-native-static-server:checkReleaseManifest
:react-native-static-server:preDebugAndroidTestBuild UP-TO-DATE
:react-native-static-server:preDebugBuild UP-TO-DATE
:react-native-static-server:preDebugUnitTestBuild UP-TO-DATE
:react-native-static-server:preReleaseUnitTestBuild UP-TO-DATE
:react-native-static-server:prepareAndroidArchLifecycleRuntime100Library
:react-native-static-server:prepareComAndroidSupportAnimatedVectorDrawable2610Library
:react-native-static-server:prepareComAndroidSupportAppcompatV72610Library
:react-native-static-server:prepareComAndroidSupportSupportCompat2610Library
:react-native-static-server:prepareComAndroidSupportSupportCoreUi2610Library
:react-native-static-server:prepareComAndroidSupportSupportCoreUtils2610Library
:react-native-static-server:prepareComAndroidSupportSupportFragment2610Library
:react-native-static-server:prepareComAndroidSupportSupportMediaCompat2610Library
:react-native-static-server:prepareComAndroidSupportSupportV42610Library
:react-native-static-server:prepareComAndroidSupportSupportVectorDrawable2610Library
:react-native-static-server:prepareComFacebookFbuiTextlayoutbuilderTextlayoutbuilder100Library
:react-native-static-server:prepareComFacebookFrescoDrawee190Library
:react-native-static-server:prepareComFacebookFrescoFbcore190Library
:react-native-static-server:prepareComFacebookFrescoFresco190Library
:react-native-static-server:prepareComFacebookFrescoImagepipeline190Library
:react-native-static-server:prepareComFacebookFrescoImagepipelineBase190Library
:react-native-static-server:prepareComFacebookFrescoImagepipelineOkhttp3190Library
:react-native-static-server:prepareComFacebookReactReactNative0560Library
:react-native-static-server:prepareComFacebookSoloaderSoloader030Library
:react-native-static-server:prepareOrgWebkitAndroidJscR174650Library
:react-native-static-server:prepareReleaseDependencies
:react-native-static-server:compileReleaseAidl
:react-native-static-server:compileReleaseNdk NO-SOURCE
:react-native-static-server:compileLint
:react-native-static-server:copyReleaseLint NO-SOURCE
:react-native-static-server:compileReleaseRenderscript
:react-native-static-server:generateReleaseBuildConfig
:react-native-static-server:generateReleaseResValues
:react-native-static-server:generateReleaseResources
:react-native-static-server:mergeReleaseResources
:react-native-static-server:processReleaseManifest
:react-native-static-server:processReleaseResources
/home/pvl/workspace/repo/htone/htone/node_modules/react-native-static-server/android/build/intermediates/res/merged/release/values-v24/values-v24.xml:3: AAPT: Error retrieving parent for item: No resource found that matches the given name 'android:TextAppearance.Material.Widget.Button.Borderless.Colored'.

/home/pvl/workspace/repo/htone/htone/node_modules/react-native-static-server/android/build/intermediates/res/merged/release/values-v24/values-v24.xml:4: AAPT: Error retrieving parent for item: No resource found that matches the given name 'android:TextAppearance.Material.Widget.Button.Colored'.

/home/pvl/workspace/repo/htone/htone/node_modules/react-native-static-server/android/build/intermediates/res/merged/release/values-v26/values-v26.xml:15:21-54: AAPT: No resource found that matches the given name: attr 'android:keyboardNavigationCluster'.

/home/pvl/workspace/repo/htone/htone/node_modules/react-native-static-server/android/build/intermediates/res/merged/release/values-v24/values-v24.xml:3: error: Error retrieving parent for item: No resource found that matches the given name 'android:TextAppearance.Material.Widget.Button.Borderless.Colored'.

/home/pvl/workspace/repo/htone/htone/node_modules/react-native-static-server/android/build/intermediates/res/merged/release/values-v24/values-v24.xml:4: error: Error retrieving parent for item: No resource found that matches the given name 'android:TextAppearance.Material.Widget.Button.Colored'.

/home/pvl/workspace/repo/htone/htone/node_modules/react-native-static-server/android/build/intermediates/res/merged/release/values-v26/values-v26.xml:15: error: Error: No resource found that matches the given name: attr 'android:keyboardNavigationCluster'.

:react-native-static-server:processReleaseResources FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-static-server:processReleaseResources'.
> com.android.ide.common.process.ProcessException: Failed to execute aapt

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

same error. any solutions ?

Odd, I'll try running the react native git update script on it

Updated to RN 0.58


redirect to /401 when the admin-ui user is not allowed to use the cluster

redirect to /401, if the user has no cluster privilege, but not if the console query fails with 401

Codecov Report

Merging #432 into master will decrease coverage by 0.03%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master     #432      +/-   ##
==========================================
- Coverage   38.38%   38.35%   -0.04%
==========================================
  Files          20       20
  Lines        1662     1666       +4
==========================================
+ Hits          638      639       +1
- Misses       1024     1027       +3

Impacted Files
Coverage Δ

app/scripts/controllers/common.js
17.3% <ø> (ø)
:arrow_up:

app/scripts/controllers/console.js
3.01% <0%> (ø)
:arrow_up:

app/scripts/app.js
8.1% <0%> (-0.08%)
:arrow_down:

app/scripts/services/sql.js
83.14% <50%> (-1.74%)
:arrow_down:

Continue to review full report at Codecov.

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


Introduce theme-specific CSS bundles.

This introduces two separate CSS bundles, which are created automatically by Hexo, share almost 100% of their code, and are able to be selected by individual doc deployments by use of the css_bundle variable.  At a higher level, that variable will be automatically set through the apollo-hexo-config[0] and meteor-hexo-config[1] config packages, so no changes by the individual deployments will be necessary.
This builds on the work done in the Apollo/Meteor theme merge[2], and eliminates a local ./assets/theme-colors.less which was still present in each Apollo docs deployment.
In additional to being a maintenance burden in the event that we wanted to change that file, it was also the source of problems with link colors exhibited in the test theme used on the Netlify previews on this hexo-theme-meteor repository.
This eliminates the need for that file (though keeps it there in case the need arises for a deployment-specific color override.
[0] https://github.com/apollographql/apollo-hexo-config
[1] https://github.com/meteor/meteor-hexo-config
[2] https://github.com/meteor/hexo-theme-meteor/pull/51
cc @stubailo tl;dr fyi, red link colors fixed. was unnoticed bug-ish. :tada:.


Ensure clusterName can be used from global.kubernetes.clusterName

Proposed changes
Fixes #184
Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist
Put an x in the boxes that apply.

[x] I have read the CONTRIBUTING doc
[x] I have read the CLA
[x] I have added necessary documentation (if appropriate)
[x] Any dependent changes have been merged and published in downstream modules

Do you happen to know the next release cycle with this change?


superset dashboard published will return the true or false by the chart id

A clear and concise description of what the bug is.
How to reproduce the bug

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected results
what you expected to happen.
Actual results
what actually happens.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
(please complete the following information):

browser type and version:
superset version: superset version
python version: python --version
node.js version: node -v
any feature flags active:

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[ ] I have reproduced the issue with at least the latest released version of superset.
[ ] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

please fill out the complete issue template to report an issue 🙏 close for now.


Flaky pending saves vcs test

Pull Request Description

Ensure force all pending saves does not fail.
Important Notes

Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[x] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.

Did a few re-runs today. It seems it does not trigger the issue anymore


[$1000] mWeb - mWeb - Keyboard opens automatically after going back from attachment

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to any chat
Send any image as attachment.
Click on image to view it.
Click back arrow to go back to chat.
Keyboard opens automatically

Expected Result:
Keyboard should not open automatically.
Actual Result:
Keyboard opens automatically
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[x] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number:
Reproducible in staging?:
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/3e9013bf-46d3-4c7e-b446-aff005c11b68
https://github.com/Expensify/App/assets/93399543/2cc62c3f-47d1-4f98-acae-76f67995ce25
Expensify/Expensify Issue URL:
Issue reported by: @Talha345
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1690147484102679
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~011c973cf5ceb3c3f7
Upwork Job ID:<PHONE_NUMBER>311867904
Last Price Increase: 2023-07-24

Was able to repro.

@stephanieelliott @fedirjh
Refocusing on main composer opens the keyboard. I think this is an expected behavior

@stephanieelliott @fedirjh
Refocusing on main composer opens the keyboard. I think this is an expected behavior

Nope, as we had the same issue on native platforms previously and we disabled it.This is not the expected behaviour.Only when the user taps the composer, only then the keyboard should open.

I think composer autofocus issues on mWeb can be handled in https://github.com/Expensify/App/issues/23382.

@situchan It looks like they are separate bugs, However, for this issue, I think this is the expected behavior. cc @stephanieelliott, looking at this comment, it seems like this is the expected, Focusing the input will open the keyboard on non-native platforms.
https://github.com/Expensify/App/blob/64e719e04c1a9712ba74633eb20d93690250f907/src/pages/home/report/ReportActionCompose.js#L269-L271

If you read the comment,it is mentioned that this same issue existed on native platforms and was solved using this code.If we are fixing it on native platforms,why not on mWeb?

This feels like expected behavior to me too... I don't know enough about the RN variable to be certain though. @fedirjh based on the above, do you still agree this is not a bug?

This feels like expected behavior to me too... I don't know enough about the RN variable to be certain though. @fedirjh based on the above, do you still agree this is not a bug?

@stephanieelliott Think from the perspective of a user using the platform.
They open a chat and scroll through it and every time they open an image attachment to preview it and close it,the keyboard pops up.Feels like buggy behavior to me at least.

I agree with @fedirjh, it feels like polish if anything. Taking Help Wanted off this one and adding it to the tracking issue.

Not overdue, just removed the Daily label since this is on hold

Still on hold.

Closing this as I don't think it is a priority. It is linked to the master tracking issue for composer component polish (which has also been deprioritized), so we may reopen it when we decide to focus on that issue.


Removed incomplete sentence

A possible artefact from a previous change in documentation perhaps?

Please make all pull requests on the dev branch.
Don't commit build files
Try to get all tests to pass.

🙏🏻


how to limit hive query history records

When you get the Hive query history, all records for a user are found and placed in memory. If a user has a particularly large number of records, the memory can be particularly high. How do I limit the number of history records returned to memory, such as 20 records

Are you sure about this?
The query history should have a limit 50 per default:
Request URL: http://demo.gethue.com/notebook/api/get_history?doc_type=hive&limit=50&page=1&doc_text=&is_notification_manager=false&_=1559319046886

But I have a question, when there are only 10 historical records, hue memory consumes 80MB, and when there are 10,000 records, there is 200 MB of memory, which looks like the more history, the higher the memory footprint, what is the reason of this?

I would recommend to profile Hue to be exactly sure of what is happening, e.g. SQL query generated
http://gethue.com/get-a-mode-to-allow-easy-profiling-of-requests/

I found out the reason, when I commented out the three lines, the memory no longer grew. I use Hue 3.11.0, How do I change the code here?

I add this parameter when query history and the problem resolved.

Hue 3.11 is extremely old, would recommend to use 4.5 instead.
In master the default is not to includd trashed history: https://github.com/cloudera/hue/blob/master/desktop/core/src/desktop/models.py#L989


Fixes issue of not being able to submit on no filing company.

*Issue:*https://github.com/bcgov/entity/issues/
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the namex license (Apache 2.0).

/gcbrun

Temporary Url for review: https://bcregistry-btr-dev--pr-178-tiewv0mp.web.app


Is it functional?

The readme says nothing about whether this project is functional or not. If I use this in Godot now, will the callbacks, spectating, etc. work? If not, what are the steps that need to be taken to get to that state?

So basically, all the callbacks are managed by the module, but the only callbacks you don't need to write are the begin_game and the free_buffer callbacks as they are already writen in the module. As for the functions, the spectating and so on, it should already be handled by the GGPO lib, so they should work anyway.
Also for the point of your question, I actually planned to make a github page explaining in details how the module should be installed and used. But I'm also counting on you (the GGPO and Godot community) to test the module and help me make the github page a thing. Because yeah I may know some things about that, but I'm not an expert on GGPO though.

Ah, I see. That helps a lot. I was planning on creating tutorials anyway, if I could figure it all out, so that works. I feel a lot better about sinking some time into this now.
It might be a good idea to call that out in the readme, possibly with a TODO list for things to fill out in the how-to.

And also, I saw you made a fork of this project. So if there is something you wanna fix or improve, don't hesitate to do so on your fork, then do a pull request on mine.


Add an append_without_duplicates function

Append operations will add duplicate values by default.  The Delta Lake documentation contains examples showing how to append without adding and duplicates.
Here's the code snippet they use:
deltaTable.alias("logs").merge(
    newDedupedLogs.alias("newDedupedLogs"),
    "logs.uniqueId = newDedupedLogs.uniqueId") \
  .whenNotMatchedInsertAll() \
  .execute()

It'd be nice to wrap this in a helper method so users can access this functionality with a single line of code.

Hi @MrPowers I can take this issue. Please assign it to me. Thanks.

@souvik-databricks - awesome, assigned it to you!

@MrPowers I think we can close the issue now that the PR is merged.


Not a valid origin for the client:  has not been whitelisted for client ID

I'm trying to get this source working:
https://github.com/google/google-api-javascript-client/blob/master/samples/authSample.html
error message: Not a valid origin for the client: http://localhost:5500 has not been whitelisted for client ID
in my devtools console
window.location.origin : "http://localhost:5500"
I have set the whitelist through the API Key and entered it as suggested by @orichcasperkevin (issue #301) and I have cleared the cache, but I'm seeing this same issue.
One thing that confuses me is the message refers directly to the client ID, but whitelist input is done through the API Key. The Oauth consent form deals with Authorized Domains and not Whitelists. It will not allow localhost entries; it requires a top private domain.
Looking for suggestsions.

I was able to get past this issue. I'm not certain how and I've been tinkering with several items, but it may have been a result of completing a field I had left empty in the "edit app" link on the oauth content screen. I have a new issue (403 error) but I think that is not a result of this problem. Closing.

.

I added that I encountered this problem problem caused by the top-level domain.


how can i pass ArrayList in materialDialog single choice list?

BTW this repository is a really greate job!!
thx !

There should be no problem with using .items(Collection) for that.

thanx for the quickly reply !
in the documentation it didn't mention.


fix Unit convertor.

In unit convertor , while clicking on any option other than length, the top part is showing length for all option.

Here, I clicked on volume, it still showing length while it should show volume.

I would like to work.

Go ahead
Deadline 14 March,2021 (11:59 PM IST)


Deprecate global Homebrew.args.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew tests with your changes locally?

Finished the implementation started by @SeekingMeaning in https://github.com/Homebrew/brew/pull/8204.
Closes https://github.com/Homebrew/brew/pull/8204.

For some reason this PR (and my old one) doesn't work with https://github.com/Homebrew/homebrew-livecheck/commit/aafb126ada9c0625929aa4406532021a83ca8a4b

Thanks @reitermarkus ❤


Document API stability

Below is a screenshot of the table that documents stability:

After this is merged, I will close https://github.com/zephyrproject-rtos/zephyr/projects/15

API meeting:
@nashif mentions that an additional column with "Version changed"
@nashif also mentions that we should include updating the table in the release checklist
@pabigot: we should document the deprecation release in the code, alongside the __deprecated.

@nashif @mbolivar-nordic added a "Version modified" column

@nashif @mbolivar-nordic added a "Version modified" column

Is there a process for making sure this is updated for each release? If not I still believe this will go stale immediately.

@nashif @mbolivar-nordic added a "Version modified" column

Is there a process for making sure this is updated for each release? If not I still believe this will go stale immediately.

I've added it to the checklist template.


contribution Himanshi Rana

PULL REQUEST TEMPLATE
👨💻 What did you do ?

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title and description of the PR is clear and explains the approach.
[x] I have read the contribution guideline properly and following the criteria.

you are not following the contribution criteria of this repository.

if you are not interested in rules,
you can close this PR

if you are not interested in rules, you can close this PR

sir can you please confirm which rule i haven't followed?

sir i have star your reposita

done:)

be professional.
this might look little mistakes.
but rules are rules.


components/cer.js: Briana Morrison now at UVA

Briana Morrison is moving to the University of Virginia August 2021.

Thanks Kevin!


Namespace Filter

Resolves #2819
Signed-off-by: Julian Castrence<EMAIL_ADDRESS>Type of change

New feature
Improvement (improvement to code, performance, etc)

Description

Namespace filter flag allows the user to produce only ledger differences of a given namespace. Compatible with existing flags.
Since it is now possible to compare two different snapshots and find no differences due to the namespace flag being active, output files with no relevant differences (empty files) will not be generated, and if no output files are generated the output directory will not be generated.

There is some discussion about not merging this one... rather just leave the utility very simple and always collect all differences since that is what will be required when troubleshooting.

As @denyeart mentioned, we've decided to drop this feature to keep the tool simple. This PR will be closed.


Minimum TLS version on storage account created is Version 1.0

When this solution is deployed to Azure, the minimum TLS version on the storage account created is Version 1.0. Best practice is to use TLS 1.2, and is the default on newly-created Azure storage accounts. Is there a reason why TLS 1.0 is the minimum version for this solution? Is there risk to updating to TLS 1.2?

@jbailey-limgeomatics - There is no risk in updating to TLS 1.2 and solution will work fine.

@balas77
Do you know when the TLS version included in this deployment template will be updated from 1.0 to 1.2?


ArgumentCaptor for a suspended function parameter

How can I capture suspended function arguments?
Suppose I have a function:
class DatabaseRepository {
...
    suspend fun getPosts(success: (List<Post>) -> Result,
                         error: suspend () -> Result) : Result
...
}

And I would like to verify it with an Argument Captor.
val argumentCaptorParam1 = argumentCaptor<(List<Post>) -> Result>()
verify(databaseRepositoryInstance).getPosts(argumentCaptorParam1.capture(), ...

How can I write the argument captor for param2? (error: suspend () -> Result)
As suspend isn't part of the type, there doesn't seem to be a way to capture suspended function arguments at the present.

@bkach suspenddoes not have to be part of the type, because the compiler and Mockito-core takes care of this for us.
The code below should theoretically work (requires mockito-core 2.23 at least if you're using kotlin 1.3)?
@Test
fun captureSuspendFunctionArgument() = runBlocking {
    /* Given */
    val m = SomeClass()
    val captor1 = argumentCaptor<(List<Post>) -> Result>()
    val captor2 = argumentCaptor<suspend () -> Result>()

    /* When */
    val result = m.getPosts(argumentCaptorParam1.capture(), captor2.capture())

    /* Then */
    ... Do what ever with argumentCaptors ...
}


[Numpy] Added operator logaddexp; added support for zero-size tensor in BinaryBroadcastBackwardUseIn

Description

Added np.logaddexp and its docs for future rendering. Scalar calculation is supported.

Fixed zero-size tensor error in BinaryBroadcastBackwardUseIn (GPU version).

Checklist
Essentials

[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

Added np.logaddexp and its docs for future rendering. Scalar calculation is supported.
Fixed zero-size tensor error in BinaryBroadcastBackwardUseIn (GPU version).

Comments

The previous error case description: when one operand is non-zero-size (eg. shape of (1, 3)) and the other is zero-size (eg. shape of (2, 0, 3)), the backward calculation on GPU will raise a floating point error.

@xidulu could you resolve conflicts?

@szha Conflicts solved (for now)


chrome dead net game

just a quick game

it seems like you submitted an empty file, please review your PR.

i am adding other files  in a second

4 files


Cannot connect to https://cloud.zilliz.com

Basically the SDK cannot connect to collections on https://cloud.zilliz.com. It says auth check failure, please check username and password are correct.
public const string Host = "in01-XXXXXXXXX.aws-us-west-2.vectordb.zillizcloud.com";
public const int Port = 19543;

connect.UseHttps = true;

Exception Details
Grpc.Core.RpcException: Status(StatusCode="Unknown", Detail="auth check failure, please check username and password are correct")
   at Grpc.Net.Client.Internal.HttpClientCallInvoker.BlockingUnaryCall[TRequest,TResponse](Method`2 method, String host, CallOptions options, TRequest request)
   at Grpc.Core.Interceptors.InterceptingCallInvoker.<BlockingUnaryCall>b__3_0[TRequest,TResponse](TRequest req, ClientInterceptorContext`2 ctx)
   at Grpc.Core.ClientBase.ClientBaseConfiguration.ClientBaseConfigurationInterceptor.BlockingUnaryCall[TRequest,TResponse](TRequest request, ClientInterceptorContext`2 context, BlockingUnaryCallContinuation`2 continuation)
   at Grpc.Core.Interceptors.InterceptingCallInvoker.BlockingUnaryCall[TRequest,TResponse](Method`2 method, String host, CallOptions options, TRequest request)
   at Milvus.Proto.Milvus.MilvusService.MilvusServiceClient.Query(QueryRequest request, CallOptions options) in /Users/hieu/sources/repos/milvus-sdk-csharp/src/IO.Milvus/obj/Debug/net7.0/MilvusGrpc.cs:line 2030
   at IO.Milvus.Client.AbstractMilvusGrpcClient.Query(QueryParam requestParam, Nullable`1 callOptions) in /Users/hieu/sources/repos/milvus-sdk-csharp/src/IO.Milvus/Client/AbstractMilvusGrpcClient.cs:line 1337

seems that the verification failed.
You will need to offer username/password.
Did the c# client support username/password

I have found the reason. In short, the current sdk does not work with a remote Milvus server at all. It only works locally to some extend.
I made a PR to fix it and other issues: https://github.com/milvus-io/milvus-sdk-csharp/pull/9


Filter events by labels

Resolves #16458
This is the smallest change I could see to add support for this feature.  I think some refactoring of getEvents() would make it easier to unit test, but I wanted to try this first.
Feedback appreciated

I like this, +1

Moved to code review. @dnephin don't forget that this change is going to require also documentation.

Ok, moved the nested functions out, and added docs.  My docs commit includes some cleanup of end-of-line whitespace (which was done automatically by my git commit hooks). I hope that's alright.

At least, I'm assuming that whitespace is all intentional! ping @moxiegirl

I'm pretty sure the whitespace doesn't do anything, I'll wait for confirmation from @moxiegirl

checking with a make...

@moxiegirl my change isn't related to cpuset or deprecating anything, not sure what you mean.
The docs changes were just cleanup done by my automated git hooks to remove end-of-line whitespace.

@dnephin ugh...I was reading the green lines.  And I'll file an issue for the other stuff because it was missed.

@cpuguy83 ok, I've cleaned up the assertions, and moved a lot of the filtering logic out of  the api handler and into the daemon package.
I'm not sure what you'll think of the EventFilter type. The only way I can see around that (and the GetEventFilter method on daemon), would be a significant change to the data stored by Event.Log. Instead of only storing an ID, it would need to store an object which exposes a way to normalize id/name, and to extract labels (basically store the container or image struct).  I think that would be the way I'd design it.  I'd rather avoid that large change for now, and do it as a follow up (if you think that's the way to go).

Ok, I realized there is another issue with the lookup of labels. If the container or image is removed before the API call to events (with a filter on label), and there is a since=... param, you actually miss events.  The call to lookup labels fails (because the thing is already removed), so it doesn't match the filter.
This is probably an isolated edge case.  Do you think it necessitates the changes to events I was suggesting above?

Applied 's/EventFilter/Filter/g' and changed Int64ValueOrZero to use `Int64ValueOrZero

I don't like passing in daemon.GetLabels, but I can't think of a better way at the moment.
So, LGTM.

LGTM

can you squash the commits please

Once squashed, LGTM ;-)

squashed to two commits (one for code one for docs)

Moving to docs review

Fixed the docs mistake (and sorted filter list)

@dnephin oops, just added one more comment inline: https://github.com/docker/docker/pull/16530#discussion_r41064013.
Also, I think we need a mention in https://github.com/docker/docker/blob/master/docs/reference/api/docker_remote_api.md#v121-api-changes
Hm, looks like the man page doesn't actually mention which filters are available; https://github.com/docker/docker/blob/master/man/docker-events.1.md. Would be nice to add it there, but since it's not there currently, I'll leave that up to you :+1:

Fixed s/GetFilter/GetEventFilter, and added to the api changes doc

Updated filter examples in command line reference for events

Thanks! docs LGTM

LGTM

Thanks @dnephin!


Is this module ready for AOT?

I've made few tests but I  got errors.
did someone succeed?

Please provide at least the rollup configuration, the import mode of the library and the errors you get. Thank you.

Ok, I have found the mistake. Angular 2 has again changed the compilation options for the destination src folder. I'll update and publish a new release. Thanks for the feedback.

I did not even answer and you already fixed it :)
I will try again in the next few days and I'll leave a feedback in case of errors.
Thanks!

Hi,
I have released the new version, which fixes the AoT compilation. See here for more information.
There are however still many problems with the AoT compilation. Follow this thread for example.
Greetings


User Favorites Do Not Appear & Overwritten

Like BFColorPicker, this clean new implementation also suffers a bug where user favorites (the favorite color palette at the bottom) are not loaded when the picker is displayed. These favorites are shared across applications. If you then add favorites through the picker, the user's favorite colors are replaced with the newly-created list (that is, a list of 10 colors is immediately reset to a list with the only first color you add via the picker). Because the list is "empty" when presented, then overwritten when changed, this leads to data loss.
Steps to recreate:

Launch another application and create or observe favorite colors in the color picker panel.
Launch your picker demo app.
Note the empty favorites.
Drag a new color into the favorites.
Switch back to other app and observe reset favorites with new color only.
Quit your demo app and relaunch.
Observe once again the most recent favorites are empty.

After spending some time investigating BFColorPicker, I was unable to determine the cause. I have a theory transferring the panel's contents disconnects something that wasn't considered. I welcome a discussion. :-)

Thank you! Fixed in 75d4f5d764c32e370bde56283e40259ae98ecb6f.


Better Description for Failed Nodes in Advanced Menu

Is your feature request related to a problem? Please describe.
Under Failed Nodes, the descriptive text currently reads:

Manage nodes that are dead and/or marked as failed with the controller

While this text is certainly accurate when entering the General Actions menu via the Advanced actions button, I believe it should be changed on the Advanced menu for specific devices (which one enters by clicking or tapping the ADVANCED button).
I suggest this because while I now understand that this is where to remove a battery powered device even though it will say sleeping indefinitely (as opposed to dead or failed), there are many search results from people not understanding this, and that confusion may be easy to solve.
Describe the solution you'd like
If the text can be different between the menus, I suggest something like:

Remove this failed node (if it is marked dead or sleeping)

for the individual device menu, with no change to the general actions menu.
Describe alternatives you've considered
My first draft was as follows:

Remove nodes that are not working

However, that was before I realized the same description was used in two different places including one which would never remove a sleeping device.
Additional context
While it is speculation on my part, I believe this is what globe-earther was suggesting in https://github.com/zwave-js/zwave-js-ui/issues/2651
Note also that https://zwave-js.github.io/zwave-js-ui/#/usage/nodes-management mentions Remove Failed Node when discussing Replace Failed Node, but I couldn't find any prior information on the former.  While it is feasible that should be reported and addressed separately, this change could help with that deficit as well.

Removing or replacing failed nodes will work on sleeping nodes too, this is correct. We need to be careful though not to indicate that this is meant to be used as the primary way to remove or replace sleeping nodes.
Remove failed node is only meant to remove devices that cannot be removed by excluding, because the device no longer exists or is truly dead (hardware failure), or the device was factory reset without the controller/Z-Wave JS noticing. This is true for both mains-powered and sleeping devices.
Replace failed node is meant to do the same thing, but by giving the node ID to another new device. This is sometimes "abused" by users who want to reuse the node IDs.
What contributes to the confusion IMO is the "check failed" function. We should probably just remove it from the UI. It simply checks if the device is marked as failed in the controller memory, but this isn't necessary for removal. Z-Wave JS will test if a device is reachable. Only if it isn't, the device can even be removed this way.


FileIO byte functions don't work.

This is because of how to write the bytes, which ends up being incorrect.

Along with this, all write and append functions return None instead of a (), this is now fixed.


Not possible to enter combination symbols on input

When trying to solve a puzzle, if a word contains the letter ä it's not possible input this value via keyboard.
On the keyboard you have to first hit ¨ and then a and they are combined into ä. I suspect the input maybe listens for key events and not input events?

@icc Yup. If I remember correctly, that was necessary to make it work properly on Android or iOS. But I'll check.

Aha, I see. Maybe I'll try to look into it later then

@icc Is it urgent? I'd have a look this weekend. Might spare you to look at the partially ugly code that grew and grew due to constantly changing requests (and no time/budget for refactoring).

@icc Hmm, maybe we should both have a look. I don't have a ¨ key to combine with an a (because German has an ä) on the keyboard, but I just tried ´ and e for é and ^ and o for ô and that works nicely both in the grid and the input fields.

@otacke Not that urgent. If you change to Norweigan Bokmål for KB language you can get ¨ on what is the ]} key on ANSI. I think what is special compared to ´ is it actually outputs ¨ and then it goes back to correct it when hitting a next.

@icc Okay, this is a weird one. I'm at https://h5p.org/content-types/crossword (Linux, latest Chrome), changed the keyboard to Bokmål, and I can get a Ä with the two-key combination. Both, in the grid and in the input fields. What OS/browser are you on?
I also glanced at the code (for a grid cell). I definitely had to work around some issues on Android and older browsers, but I don't see a comment why I didn't go for the InputEvent in the first place (except, maybe, "Android [...] doesn't check maxlength on input" - but that comment doesn't tell me what I meant with that ... "Bad former Ollie!"). Maybe I should give the InputEvent another try. But you would need to be my tester, because I cannot reproduce this.

@icc I have quickly changed the behavior to use the InputEvent for the grid. I'll have to re-test this on all kinds of devices, but could you please check whether this fixes the problem on your end? If yes, then I assume only for the grid but not for the input fields? Aaand if yes, then I'll try to replace the KeyEvent that I used for changing the input field behavior - and I'll re-test everything on all kinds of devices ...

@icc Oh, I should have mentioned https://github.com/otacke/h5p-crossword/tree/inputevent-for-grid

@icc I think I know what the issue is and why it works for me but not for you. Crossword is assuming that each character represents one unicode code point. The ä could be one single unicode code point (U+00E4 for ä) which is fine for Crossword, but it could also be a be a composite of two unicode code points (U+0061 for a and U+0308 for ◌̈) and this would most likely throw off the symbol detection. Since ä is a common symbol in Germany, the locale settings here might result in U+00E4 being used whereas your locale setting might report it as U+0308U+0061.
Even if the change to InputEvent in my separate branch fixes the detection, I am pretty sure that there are more places in the code that implicitly assume that each character represents one unicode code point. I guess that comparing the given answers with the expected solutions would also fail.
I'd love to fix this, because it would also affect languages that rely on composite characters, but unfortunately, I currently don't have the time to investigate what's necessary to deal with those properly and to check what parts of the code need to be updated (given that the issue is composite characters) :-/

Hi, I have created a crossword game in Chinese Language, and I face the similar problem. However,  I am able to key in the answer with my Samsung handphone. But I am not able to key in any Chinese Character with laptop and iPhone. I will paste the link of the game as well as the answers here.
https://story2021.h5p.com/content/1291639853518537889
Answer:
1 琳琅满目
3 长他人志气灭自己威风
7 意兴阑珊
8 发愣
2 警察队长
4 掩人耳目
5 咖喱火气面包
6身不由己
7 兴致勃勃
Sorry I don't really know anything about code, I don't understand why I can key in with my Samsung phone but not my laptop too , but I really like this game, hope the problem can be solved :)

@Hweyping It's working on your Samsung phone but not on other platforms because different devices use different ways of "sending" a symbols that consist of multiple "subsymbols" to the application that's running in the browser.
This content type was contract work that I created as a contractor for a company and they did not require support for non-latin based languages (or languages that require multiple keystrokes for one symbol). Their requirements were met. I can only implement more features if my time allows, and currently it does not.


Fix docstring early_stop_callback arguments

What does this PR do?
As discussed in https://github.com/PyTorchLightning/pytorch-lightning/issues/3291#issuecomment-697217439, the PR fixes documentation for the Trainer's early_stop_callback argument. Before this PR the default argument was set to None. Now it is set to False. Moreover, the PR fixes grammatical error for the None value.
Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together? Otherwise, we ask you to create a separate PR for every change.
[x] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

Hello @JackCaster! Thanks for updating this PR.

In the file pytorch_lightning/trainer/__init__.py:

Line 1098:1: W391 blank line at end of file


Clarify behaviour and interplay of --run-types, --tests, --doc, --all-targets, etc.

Came here in trying to find out how to run overall coverage, aka doc, unit and perhaps more tests combined.
Initially I found this comment in #13 which says:

tarpaulin now has a new --run-type flag where you can get coverage for just your tests (default), just doc-tests or both!

I'm not sure how to get this working. Perhaps things changed in the four years since. #850 is tightly related but the below differs, and I didn't want to comment in an old, closed issue.
I am working with:
$ cargo tarpaulin --version
cargo-tarpaulin version: 0.25.2

and have a sample project:
$ cargo new --lib tarpaulin-test
     Created library `tarpaulin-test` package
$ tree tarpaulin-test
tarpaulin-test
├── Cargo.toml
└── src
    └── lib.rs

with the lib.rs as:
pub fn one() {
    println!("one");
}

/// # Examples
/// ```
/// use tarpaulin_test::two;
/// two();
/// ```
pub fn two() {
    println!("two");
}

mod tests {
    use super::*;

    #[test]
    fn test_one() {
        one();
    }
}

and Cargo.toml:
[package]
name = "tarpaulin-test"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]

Now, cargo tarpaulin --doc reports 50%, cargo tarpaulin --tests reports 50% as well, and lastly cargo tarpaulin --doc --tests gives 100% coverage. Great, works! But how does --run-type AllTargets work? Its behaviour isn't clear to me:

cargo tarpaulin --run-types doctests tests only doctests, which is fine. Reports 50% coverage.
cargo tarpaulin --run-types tests tests only unit tests, also fine. Gives 50% coverage.
cargo tarpaulin --run-types AllTargets, contrary to the above cargo tarpaulin --doc --tests, exercises only the unit, not the doc test, giving 50% as well, which is unexpected.

Run the above examples with --out html to see the coverage "flip around" between the one unit and the one doc test.
Another thing of note is how the help output is written, where it says:
$ cargo tarpaulin --help | grep -- '--doc'
        --doc                      Test only this library's documentation

but also, for example:
$ cargo tarpaulin --help | grep -- '--examples'
        --examples                 Test all examples

As far as I understand one could run cargo tarpaulin --tests --doc --examples to run all three and combine results. However, only for the --doc option does it say only, which I guess is misleading?
Lastly, either a hint that these options combine (which ones exactly then? --tests, --doc, --examples, ... --benches I guess? Did I miss anything?) would be helpful, and/or a flag for running everything combined (is this was --run-types AllTargets is designed for)?
I can offer looking into clearing this up in a PR, but the --run-types arg I'm not clear on yet. It seems related to other, 'single' flags:
https://github.com/xd009642/tarpaulin/blob/8c876b1cba411bbada710335f051e5f968b158bb/src/cargo.rs#L535-L544
In fact, passing just --all-targets errors out, which is quite unexpected behaviour on the CLI (passing a single flag shouldn't error out, as it can't contradict anything; maybe ignore if tarpaulin already passes it to cargo test?):
$ cargo tarpaulin --all-targets
Jun 12 18:55:24.481  INFO cargo_tarpaulin::config: Creating config
Jun 12 18:55:24.487  INFO cargo_tarpaulin: Running Tarpaulin
Jun 12 18:55:24.487  INFO cargo_tarpaulin: Building project
Jun 12 18:55:24.487  INFO cargo_tarpaulin::cargo: Cleaning project
error: the argument '--all-targets' cannot be used multiple times

Usage: cargo test [OPTIONS] [TESTNAME] [-- [args]...]

For more information, try '--help'.
Jun 12 18:55:24.496 ERROR cargo_tarpaulin: Cargo failed to run! Error: cargo run failed
Error: "Cargo failed to run! Error: cargo run failed"

The help output doesn't warn of this potential behaviour:
$ cargo tarpaulin --help | grep -C3 -- '--all-targets'
FLAGS:
        --all                      Alias for --workspace (deprecated)
        --all-features             Build all available features
        --all-targets              Test all targets
        --avoid-cfg-tarpaulin      Remove --cfg=tarpaulin from the RUSTFLAG
        --benches                  Test all benches
        --bins                     Test all binaries

Thanks for putting together this crate, it works really well! Just at this point I reckon the docs can be tad clearer.

So tarpaulin actually matches cargo tests behaviour in regards to this - which meant I had to look it up because my help text for it is also taken verbatim from cargo test. From https://doc.rust-lang.org/cargo/commands/cargo-test.html
--all-targets
    Test all targets. This is equivalent to specifying --lib --bins --tests --benches --examples.

Allowing --doc --examples to be args is where tarpaulin differs - probably because I felt at the time it made sense for these to be additive.
The error with all-targets is likely due to over-enthusiastically passing flags into cargo test when building the test binaries.
Hopefully this clears up some of the initial questions or provides some clarity. Tomorrow I'll try to find some time to go over in more detail and actually address the issues in the docs and make --all-targets work. Though I probably won't add doc tests to it because doc test coverage does rely on nightly features

Thanks for the fast reply! The help for cargo test actually doesn't contain that bit on my system, so no wonder I wasn't able to find that info:
$ cargo test --help | grep -C2 -- '--all-targets'
      --benches                 Test all benches
      --offline                 Run without accessing the network
      --all-targets             Test all targets
      --config <KEY=VALUE>      Override a configuration value
      --doc                     Test only this library's documentation

so that would've helped clear up the confusion. Perhaps a version mismatch (I have v1.69.0).
It's helpful to see that tarpaulin mirrors that, thanks. I agree about being pragmatic in the --doc case (have it be additive).

Yeah so the help for cargo test doesn't include it, it's only in the cargo book hosted online. Maybe worth raising an issue on rust-lang/cargo  if you feel the CLI help text could stand to be improved. I'm adding (excluding doctests) to my own help text to clear up the ambiguity.
I've also tracked down the issue with --all-targets so a PR to fix that should be landing today or tomorrow and a new release before the end of the week!


Include limitations in the document

Oh, the limitations of tensor inference method:
https://nzy1997.github.io/TensorQEC.jl/dev/generated/inference/


completion suggestions inside comments

I think completion suggestions should not be offered inside comments.

Ah great point. Thank you for report!! I will work on this when I get home


Retrieve the InjectTemplateListener from the service manager.

This makes it possible to use your own InjectTemplateListener.

@akrabat merged into develop at zendframework/zf2@d98b64250a081f6c9407b6d2bb67e39de25aec45, thanks!

@akrabat merged into develop at zendframework/zf2@d98b64250a081f6c9407b6d2bb67e39de25aec45, thanks!


path to script root

Instructions talk about setting a public path. But my config is saying script root. What's a script root vs public?

+1

+1
This seems like a promising library, but the instructions on how to configure the plugin are confusing.

+1

+1


Why my lines of code are 0?

Are you experiencing an issue with...
shields.io
🐞 Description
Hi! I added lines of code badge to my README.md, but I have no lines
I noticed a problem in my repo https://github.com/KartoshkaPy/Sweet-Coin-Market
I know that it's using Tokei
I installed Tokei locally and everything works correctly

Is it really bug?
This badge also don't works in my other repos
For example https://github.com/qBasket-File-Sharing-Platform/Cloud-Service
But I didn't change anything
Everything worked before, but now it doesn’t
I thought I was wrong somewhere, but any badges have 0 lines

🔗 Link to the badge
https://img.shields.io/tokei/lines/github.com/KartoshkaPy/Sweet-Coin-Market?style=for-the-badge
💡 Possible Solution
No response

Presumably due to https://github.com/XAMPPRocky/tokei/issues/804

The problem was fixed.


Fix spelling typo.

Just a small spelling typo in a README

The build check is failing, but I'd venture a guess that your change didn't cause that and it was already broken. Thanks for the change.


fail to gracefully shutdown java dubbo app

To whom it may concern:
According to  the link, https://cn.dubbo.apache.org/zh-cn/overview/mannual/java-sdk/advanced-features-and-usage/others/graceful-shutdown/,  adjusting  wait parameter,   can ensure the jar app to wait until the running tasks  complete normally, after receiving the TERM (sent by the command of kill PID ).    The reality is IT IS NOT WORKING as expected.     Even I increase the wait value to VERY VERY large, the running tasks still  FAIL  to  complete normally.   This bug has been verified on the version of 3.2.0-beta.4,  and should apply to other dubbo 3 version, even dubbo 2.      pls help, many thanks

What's the actual behavior?

false


Error! Unable to parse option value "bt470bg"

Bug description
This is the error I get with a simple auto-editor filename.mp4 command
What's your platform?
Python Version: 3.12.1 64-bit
Platform: Windows 11 amd64
FFmpeg Version: N-110322-g0c25da5a28-g1440bf15e2+1
FFmpeg Path: C:\Users\fred\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.12_qbz5n2kfra8p0\LocalCache\local-packages\Python312\site-packages\ae_ffmpeg\Windows\ffmpeg.exe
Auto-Editor Version: 23w51a

What command did you use
auto-editor filename.mp4

What properties does your input video have?
.\Short1.mp4:

video:

track 0:

codec: h264
fps: 25
resolution: 1920x1080
aspect ratio: 16:9
pixel aspect ratio: 1
duration: 69.44
pix fmt: yuv420p
color range: tv
color space: smpte170m
color primaries: bt709
color transfer: bt470bg
timebase: 1/12800
bitrate: 4996338
lang: und

audio:

track 0:

codec: aac
samplerate: 48000
channels: 1
duration: 69.354
bitrate: 179993
lang: und

container:

duration: 69.44
bitrate: 5182477

.\Short1.mp4:

video:

track 0:

codec: h264
fps: 25
resolution: 1920x1080
aspect ratio: 16:9
pixel aspect ratio: 1
duration: 69.44
pix fmt: yuv420p
color range: tv
color space: smpte170m
color primaries: bt709
color transfer: bt470bg
timebase: 1/12800
bitrate: 4996338
lang: und

audio:

track 0:

codec: aac
samplerate: 48000
channels: 1
duration: 69.354
bitrate: 179993
lang: und

container:

duration: 69.44
bitrate: 5182477

Comments
I tried with another ffmpeg (--ffmpeg-location) but same error.
with --show-ffmpeg-output :
[NULL @ 00000170a7a4ad80] [Eval @ 00000023a5ffe218] Undefined constant or missing '(' in 'bt470bg'
[NULL @ 00000170a7a4ad80] Unable to parse option value "bt470bg"
[NULL @ 00000170a7a4ad80] Error setting option color_trc to value bt470bg.
[vost#0:0/copy @ 00000170a7a4aa80] Error setting up codec context options.
Thank you!

I've found a workaround that helped me:
Add --extras "-color_primaries bt470bg -color_trc gamma28 -colorspace bt470bg" to to the auto-editor command

Thank you, it works !

No problem. I still think its an issue worth leaving open and investigating though because it shouldn't happen in the first place


Remove unused file and correct explorer view

Codecov Report

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

@@            Coverage Diff             @@
##           master      #20      +/-   ##
==========================================
+ Coverage   68.51%   70.62%   +2.11%
==========================================
  Files          20       19       -1
  Lines         848      817      -31
  Branches      132      129       -3
==========================================
- Hits          581      577       -4
+ Misses        267      240      -27

Continue to review full report at Codecov.

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


This seems to be an existing issue: https://github.com/openthread/ot-br-posix/issues/2133
@morningboata I wonder if this has been fixed or not?
Regarding this one, @yf-fan-org you may try getting the properties you're interested in (this should work) instead of getting all properties.

#2133 is not fixed. Added a comment in it.

This seems to be an existing issue: #2133
@morningboata I wonder if this has been fixed or not?
Regarding this one, @yf-fan-org you may try getting the properties you're interested in (this should work) instead of getting all properties.

Thank you very much, mainly because I need to be able to get all the properties when initializing so that I can read the data in the cache next time, is there any way I can make get all work? Is there any way to make get all work? It's too much trouble for me to read them one by one.

I've tried to turn on attribute configurations that may not be turned on, but I still get the same error, all attributes should be supported at this time @superwhd

I was trying to fix the issue by abandoning the opened container on error but otbr-agent crashed after handling the message. The client also failed to receive the response:
    for (auto &p : mGetPropertyHandlers.at(interfaceName))
    {
        DBusMessageIter subIter, dictEntryIter;

        VerifyOrExit(dbus_message_iter_open_container(&iter, DBUS_TYPE_ARRAY,
                                                      "{" DBUS_TYPE_STRING_AS_STRING DBUS_TYPE_VARIANT_AS_STRING "}",
                                                      &subIter),
                     error = OT_ERROR_FAILED);
        VerifyOrExit(dbus_message_iter_open_container(&subIter, DBUS_TYPE_DICT_ENTRY, nullptr, &dictEntryIter),
                     error = OT_ERROR_FAILED);
        VerifyOrExit(DBusMessageEncode(&dictEntryIter, p.first) == OTBR_ERROR_NONE, error = OT_ERROR_FAILED);

->        if (p.second(dictEntryIter) != OT_ERROR_NONE) {
->           dbus_message_iter_abandon_container_if_open(&subIter, &dictEntryIter);
->           dbus_message_iter_abandon_container_if_open(&iter, &subIter);
->           continue;
        }

        VerifyOrExit(dbus_message_iter_close_container(&subIter, &dictEntryIter), error = OT_ERROR_FAILED);
        VerifyOrExit(dbus_message_iter_close_container(&iter, &subIter));
    }

Wow! I come in the issues section for the same thing. But it seems that many issues exists.

I would like to use DBUS API as this is a standard inter-process communication mechanism to control the Thread network
I wanted to explore the available methods using standard utilities like busctl as there is no documentation about the DBUS API except the code (https://github.com/openthread/ot-br-posix/blob/main/src/dbus/server/introspect.xml)  (or more generally all the files in this folder)

# busctl --system --verbose introspect io.openthread.BorderRouter.wpan0 /io/openthread/BorderRouter/wpan0
Failed to get all properties on interface io.openthread.BorderRouter: Input/output error

Logs of otbr-agent:
Sep  3 11:02:05 otbr-agent[23172]: [INFO]-DBUS----: Handling method org.freedesktop.DBus.Introspectable.Introspect
Sep  3 11:02:05 otbr-agent[23172]: [INFO]-DBUS----: Handling method org.freedesktop.DBus.Properties.GetAll
Sep  3 11:02:05 otbr-agent[23172]: [ERR ]-UTILS---: Replied to org.freedesktop.DBus.Properties.GetAll with result io.openthread.Error.NotImplemented

What is the status of this issue or related issues ?
What is the status of the DBUS-API ?

Is it something that is going to be upgraded in the future ? (documentation, fix) ?
Or is it something with very low priority ?

What is the status of the DBUS-API ?

D-BUS API will be continuously maintained but the priorities of the methods may vary, depending on the use cases.
So far the introspect.xml is the most comprehensive documentation in the repo. I wonder what kind of documentation would you suggest?

What is the status of the DBUS-API ?

D-BUS API will be continuously maintained but the priorities of the methods may vary, depending on the use cases.
So far the introspect.xml is the most comprehensive documentation in the repo. I wonder what kind of documentation would you suggest?

I was thinking about something like this directly in openthread website:
https://w1.fi/wpa_supplicant/devel/dbus.html
So that everybody know there is a DBUS API and how to use.
But in any cases, it will be (maybe) the same informations as introspect.xml, eventually with some dbus-send examples.


Switch to using #![no_std] with alloc.

We shouldn't need the std crate for this library to function. Therefore we should add the #![no_std] attribute to the crate and import the alloc crate before too many other data-structures are implemented.

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Fail to reproduce the codellama baseline with the code base

Hello, thanks for sharing the great work!
But we tried to reproduce the codellama-13b-pal results on GSM-Hard dataset, with the following script:
set -ex

MODEL_NAME_OR_PATH="LOCAL CODELLAMA-13B MODEL WEIGHTS"

# DATA_LIST = ['math', 'gsm8k', 'gsm-hard', 'svamp', 'tabmwp', 'asdiv', 'mawps']

DATA_NAME="gsm-hard"

SPLIT="test"
PROMPT_TYPE="pal"
NUM_TEST_SAMPLE=-1

CUDA_VISIBLE_DEVICES=0 TOKENIZERS_PARALLELISM=false \
python -um infer.inference \
--model_name_or_path ${MODEL_NAME_OR_PATH} \
--data_name ${DATA_NAME} \
--split ${SPLIT} \
--prompt_type ${PROMPT_TYPE} \
--num_test_sample ${NUM_TEST_SAMPLE} \
--seed 0 \
--temperature 0 \
--n_sampling 1 \
--top_p 1 \
--start 0 \
--end -1 \

The output results are as follows:
Num samples: 1319
Num scores: 1319
Timeout samples: 10
Empty samples: 293
Mean score: [0.1]

Time use: 7540.60s
Time use: 125:40

It shows the result is 0.1, which has large gaps with the reported one. Would you please share the baseline script on CodeLLaMA with PAL strategy? Thanks a lot.

Maybe check if the environment is consistent with the requirements.txt ~


Remove NO_ALPHA flag insertion in ColorPicker4::build

ColorEditFlags::NO_ALPHA is used in ColorPicker4::build function, so there is no way to edit alpha value.
It was probably copied from ColorPicker3::build and should be removed.

Ahh I briefly confused the ColorEdit with the ColorPicker! ColorPicker4 which is the "inline color swatch" widget, and it indeed is permanently missing the alpha without this fix:

Looks good, shall merge once all the CI bits are happy! Thanks!


Remove frontend filtering when clustered

When in cluster zoom level, filter by severity, accuracy and date only in backend to send as little data to client as possible.

Reverted because there was a problem where clicking a cluster did not zoom in.