Running Commands and getting aggregations

Hi @babenkoivan
I have setup my laravel application following the readme and some solutions from the internet.
However, I am faced with a few issues.

I cannot run artisan commands like php artisan elastic:update-mapping "App\Models\ExampleModet" it says no elastic commands in the namespace and  I cannot find a fix for this

The reason I am trying to run the above is because I am trying to enable field data on one of my model fields and I have created a mapping to enable that as below
protected $mapping = [
'properties' => [
'price' => [
'type' => 'text',
'fielddata' => true
]
],
];
I am not sure if this is the right way to approach the mapping.

The 3rd issue is i would like to know how i can aggregate on multiple ranges i have written the aggregation query below
$builder = ExampleModel::boolSearch()
->aggregate('prices', ['range' => ['field' => 'price', 'ranges' => ["from" => "1", "to" => "20"]]])
->aggregate('prices', ['range' => ['field' => 'price', 'ranges' => ["from" => "21", "to" => "40"]]])

I hope make sense and you can provide some help

Hey @ta1nda, the elastic:update-mapping command and the mapping definition via properties belong to the old package , which is not maintained anymore. Please use elastic-migrations to configure an index mapping.
As for the aggregations, you need to give them different names, otherwise you override one with another, i.e.:
$builder = ExampleModel::boolSearch()
    ->aggregate('prices1', ['range' => ['field' => 'price', 'ranges' => ["from" => "1", "to" => "20"]]])
    ->aggregate('prices2', ['range' => ['field' => 'price', 'ranges' => ["from" => "21", "to" => "40"]]])


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.15.5",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d330f1d4f797b05c85eaa76ad1db114f7214bd61"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "d330f1d4f797b05c85eaa76ad1db114f7214bd61",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "staging: rtl8723bs: remove a third possible deadlock\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.5 by commit d330f1d4f797b05c85eaa76ad1db114f7214bd61. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1002343


Make Next cloneable?

Sometimes middleware needs to make requests multiple times e.g. retry middleware. However, Next::run consumes self, so we can make only one actual request per call.
Next has immutable references only, so it's possible to make it derive Clone/Copy. Would it be okay to make it cloneable/copyable?

I think so, that type of behavior would definitely be warranted. Want to open a PR for it?

@tirr-c this sounds very reasonable! If you have time a PR would indeed be great! :D

@fairingrey @yoshuawuyts Opened a PR!


Incorrect function.json generated for eventhubtrigger core runtime

Microsoft.NET.Sdk.Functions version: 1.0.6
Eventhub nuget package: Microsoft.Azure.WebJobs.Extensions.EventHubs
Repro steps

Create a function app
Use the following code to create a function

using Microsoft.Azure.WebJobs;
using Microsoft.Azure.WebJobs.Host;
using Microsoft.Azure.WebJobs.ServiceBus;

namespace FunctionApp15
{
    public static class Function1
    {
        [FunctionName("Function1")]
        public static void Run([EventHubTrigger(eventHubName: "<EventhubName>", Connection = "conn")]string myEventHubMessage, TraceWriter log)
        {
            log.Info($"C# Event Hub trigger function processed a message: {myEventHubMessage}");
        }
    }
}

Here is the generated function.json
"bindings": [
    {
      "type": "eventHubTrigger",
      "path": "<EventhubName>",   // path was renamed to eventHubName for core runtime
      "connection": "conn",
      "name": "myEventHubMessage"
    }
  ]

I am curious about how do you create eventhub trigger function from CLI. Could you help me because I find there only 4 templates without EventhubTrigger.

I have the same issue
Microsoft.Azure.WebJobs.ServiceBus 2.1.0
Microsoft.NET.Sdk.Functions 1.0.10
TargetFramework = net461

This is fixed.


Support for adding stacktracing for TDML files

Ideally, we would want the stacktrace of a failed daffodil parse to end up in the TDML file. There doesn't seem to be a clear place to put the stacktrace in the test case - does it make sense to include it as a separate text file? Is this defined in another schema that we would have to JAXBify?
This may not require information to be sent from server to client as previously thought as we do the JAXB work on the server side, but it would require us to capture the stacktrace and pass it to the JAXB code - currently, the JAXB code is currently only run before a parse, not after.

Ideally, we would want the stacktrace of a failed daffodil parse to end up in the TDML file

What do you see the use case of having a stack trace in a TDML file? Normally a TDML file defines the inputs (e.g. schema, parse data, unparse infoset) and expected outputs (parsed infoset or unparsed data). A stack trace is not normally thought of as an expected output, so doesn't feel like it belongs in a TDML file to me.

Our main use case for TDML is posting test cases (presumably ones that fail to parse) on the user list. It would make sense to be able to attach a stack trace to a test case so that someone can verify their stack trace against the "expected" one that is being reported.
I'm not actually sure where this idea originated from, but we've been floating it around for quite some time as a nice to have feature for our users list scenario. Maybe I was assuming that a stack trace could be considered an output for a test case? eg. If I wanted to capture a daffodil parse that I expect to fail and compare the expected/actual stack traces.
We are planning to look into an automated way of producing a zip archive containing all artifacts required to run all test cases in a TDML file, so maybe it will make more sense to include the stack trace as a separate artifacts?

To me, it feels like a separate artifact makes more sense. Including the actual output in a TDML file, whether it be a stack trace or an incorrect infoset, just adds more complication to an already complicated format. It's usually pretty straightforward to run a TDML file to reproduce the unexpected issue.
It also adds complication, for example, you would need to run your TDML test, capture the output, and then modify that same TDML file. There's a chance that modification might accidentally change the test (e.g. copy/paste to the wrong spot) and make it not reproducible.
If you really want it in the TDML file, maybe it could be added as a comment or as an annotation or something, but I'm not sure I would want it as something the TDML runner understands and uses in any way. Like, even if the TDML runner saw the same stack trace, it still wouldn't want to consider it as a test pass.

Is there currently no way to do a negative test case with the TDMLRunner?

Yes, you can do negative tests by expecting strings that should appear in diagnostics (see the <tdml:errors> tag). A failed compile/parse/unparse should create a diagnostic (e.g. Schema Definition Error, Parse Error, Unparse Error) which can be expected instead of an infoset or unparse data. But if you get a stack trace instead of one of those diagnostics, it usually means there is a bug in Daffodil, and there is no way in TDML to expect a stack trace because we never consider bugs expected behavior. Similarly, we don't have a way to expect an incorrect infoset, because that also is also considered a bug. TDML files have traditionally been used to describe and test what should happen, and not really describe what actually happened.

Do you have a barebones stub of what an annotation might look like?

It's usually something like:
<xs:annotation>
  <xs:appinfo source="someURI">
    Your content goes here
  </xs:appinfo>
</xs:annotation>

A failed compile/parse/unparse should create a diagnostic (e.g. Schema Definition Error, Parse Error, Unparse Error) which can be expected instead of an infoset or unparse data. But if you get a stack trace instead of one of those diagnostics, it usually means there is a bug in Daffodil, and there is no way in TDML to expect a stack trace because we never consider bugs expected behavior. Similarly, we don't have a way to expect an incorrect infoset, because that also is also considered a bug.

Okay, thanks. I think I see where I was misunderstanding.
The main driver for this feature is to provide a way for a user to verify that they are seeing the same issue as someone else that reported an issue. If the diagnostic(s) will provide a way to do that, we'll look to use those instead. If that's that case, it should be possible for us to get the diagnostic(s) from daffodil and serialize it into the TDML test case.


Just wanted to say thanks

I had been putting off building a tour for my app (https://www.lunajournal.app) and this library made is SO easy that I was done in about 20 minutes. Thank you so much for building this and sharing it with the world. I appreciate you!
PS. I know this isn't an issue, feel free to close, just wasnt sure how to best reach out to you!

I am very glad to hear that. Thank you!


PhpdocOrderByValueFixer - Allow sorting of throws annotations by value

This PR

[x] ajusts the PhpdocOrderByValueFixer to allow sorting of @throws annotations by value

I decided to bake it into 2.17

Thank you @localheinz.

Thank you, @keradus!


vue-markdown-v2 fork from vue-markdown

Hi,
I have forked this repo, the goal is to get updated modules dependencies (Mardown-it and plugins).
https://github.com/Akirami/vue-markdown-v2
Work with webpack V4, Babel 7 and latest vue.js or vue/cli.
Help is welcome.
@miaolz123
Thanks to your work, i only want to maintain dependencies and if you're inetersted, MP me.

Please check https://github.com/adapttive/vue-markdown/
master: current version (with few fixes)
next: updated dependencies and few features added.
Use:
npm install @adapttive/vue-markdown
https://www.npmjs.com/package/@adapttive/vue-markdown

Please check https://github.com/adapttive/vue-markdown/
master: current version (with few fixes)
next: updated dependencies and few features added.
Use:
npm install @adapttive/vue-markdown
https://www.npmjs.com/package/@adapttive/vue-markdown


Don't lint examples

I broke linting of examples in #1883 because they are now linted via CRA, and it has incompatible configuration with the ancient version of ESLint we’re using. Our lint setup is a mess right now, with rackt config being used which is not maintained anymore. For now, I’ll just disable linting of examples altogether to try to get Travis to pass. In the future we should pick a lint config and update ESLint to a modern version.

Yay passing!


HSEARCH-4315 Fix example captions in documentation

https://hibernate.atlassian.net/browse/HSEARCH-4315

Merged, thanks


Make it possible to display categories and pages at the same time. Fixes #4

You're right, thanks. I'll probably add some seperator between categories and pages and put the pages on the right.


Properties for the Goguen ledger

No Ada is forged/unforged

When a Tx is processed as "paying script fees only", no changes to the ChainState are made except the UTxO and fee pot (for-fees outputs moved to fee pot)

The general accounting property still holds when a transaction only pays fees

Shelley era transactions are always processed fully if they are processed at all

If a transaction adds outputs to the UTxO, all its Plutus scripts validate
If a Plutus script does not validate, the transaction cannot add outputs
If a transaction does not forge tokens, the Shelly accounting property holds, with Coin replaced by Value

all ada should be fungible with other ada

That depends a bit on the definition of Ada though. If Ada is any token with the PolicyID of Ada, that's only true if there is only one AssetID that's 'populated'. Ada could also mean a specific PolicyID and AssetID, in which case that's not a very strong property.

More :
Tx has a (unique?) redeemer for everything that needs a redeemer
Epoch boundary should not affect MAs

if a transaction is valid, it will remain valid if you increase the execution units
if a transaction contains at least one valid script, it must have at least one execution unit
txvaltag tx is true IFF all the scripts inside it validate within the given execution units
if txvaltag tx is false, then the delegation state and the update state are unchanged
if tx is a "shelley in goguen" transaction, the only difference between processing tx and processing toGoguenTx tx (ie converting it out of band) is that the transaction id on the created outputs is different.

Hashes of all data passed to scripts are included either in the UTxO or in the transaction. We say this in the spec, but it's not super obvious that this is actually true.

I'm going to close this now since we have the list of properties in the spec.


ADD ABA

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

[x] Filename in the lowercase format
[x] Image format: png
[x

] Image size: 256 by 256 px

Can you follow the guidelines ? https://developer.trustwallet.com/add_new_token_image#image-requirements

Can you follow the guidelines ? https://developer.trustwallet.com/add_new_token_image#image-requirements

who is the maintainer and do i need to close it because i don't know


_CShims: excise tgmath on Windows

While Windows does have tgmath support, it is difficult to use due to the conflicting definitions originating from clang and MSVC.  Excise this for the time being which allows us to build the full project on Windows.

@swift-ci please test


[Suggestion] Supply the server name when connecting to the server

The ServerData serverName seems to be set to null when clicking a button with action connectToServer. This causes some other mods to crash, as they expect a server name to be there, and use it to name folders (see https://github.com/Tropicraft/Tropicraft/blob/1.12.2/src/main/java/net/tropicraft/core/encyclopedia/TropicalBook.java#L92).
The fix for this would be one of:

Allow the serverName to be specified in the configuration
Supply a serverName that is the same as the server IP

Same issue with Journeymap
Details and Solution here.
https://github.com/TeamJM/journeymap/issues/149#issuecomment-565826418


story-123-tidyup-cleanup-wildcard

Done.

A new inspection was created.

The inspection completed: 17 new issues, 5 updated code elements


Method override completions

Suggestion

🔍 Search Terms

suggest / suggestion
IntelliSense
Snippet / snippets
Tooling
VS Code / vscode

⭐ Suggestion
For the code:
abstract class Base {
    abstract foo(param1: string, param2: boolean): Promise<void>;
}

class Sub extends Base {

}

I should be able to type f inside the body of Sub and get a suggestion for foo that fills in the entire signature of the method when accepted:
class Sub extends Base {
    foo(param1: string, param2: boolean): Promise<void> {
        | // cursor ends up here
    }
}

Right now, accepting the suggestion for foo only inserts the text foo. I have to fill out the entire body of the method myself, typically by copy and pasting from the base class

We should be able to use VS Code's snippet syntax for this style of completion. I originally proposed snippet style completions in #25207. It sounds like we have already have adopted a subset of VS Code's snippet string syntax
This would need to be an opt-in feature for editors and we would like need to add a user facing setting to disable these too

A general question I have about these snippet completions that may insert quite a bit of text is how we want to display them. Xcode has these kinds of method signature completions and it looks like they just truncate, which isn’t too bad:

It’s somewhat less clear how #40700 should display, for example, which is another use case I’m interested in exploring.

I think we can start by using the full method signature text as the label like Xcode does here and see how we like it. @mjbvz pointed out that the Editor > Suggest: Preview setting is particularly useful for longer snippet completions, and we may want to explore enabling it by default, at least for snippet-text completions.

I've wanted this one for so long and assumed it was already suggested, but didn't know what to search for. I'm surprised it only got added to the tracker last month — this would be such a huge usability enhancement for implementing abstract classes! It's honestly one of the only reasons why I sometimes miss working on Java projects 😜
Will this completion automatically propagate visibility modifiers? IE, if the superclass has public/protected, will the completion add the same visibility to the override? Also, will it add the override modifier if the user has the noImplicitOverride flag enabled? Both of those kinds of modifiers being included with these completions would be great.

Will this completion automatically propagate visibility modifiers? IE, if the superclass has public/protected, will the completion add the same visibility to the override? Also, will it add the override modifier if the user has the noImplicitOverride flag enabled? Both of those kinds of modifiers being included with these completions would be great.

I've been working on implementing this feature, and the override modifier is going to be added if noImplicitOverride is set (modulo possible bugs, of course 😅). About visibility modifiers, I think the suggested method should have them too, but I have yet to test that behavior.
Glad to hear feedback about this feature 😊


can the authenticator be run without running the installer?

Is it possible to run something like
AWS_ACCESS_KEY_ID="your_key"
AWS_SECRET_ACCESS_KEY="your_secret"
letsencrypt --agree-tos -a letsencrypt-s3front:auth
--letsencrypt-s3front:auth-s3-bucket the_bucket
-d the_domain
to run just the authenticator part and not the installer?
I can then use an http redirect from my web server to the auth file in s3.  This is useful for our situation where we have hundreds of domains behind one ELB, so we can avoid creating symlinks to --webroot directory

Yes you can!
Just run the CLI with the certonly command...
So something like:
AWS_ACCESS_KEY_ID="your_key" \
AWS_SECRET_ACCESS_KEY="your_secret" \
letsencrypt --agree-tos -a letsencrypt-s3front:auth \
--letsencrypt-s3front:auth-s3-bucket the_bucket \
-d the_domain certonly

@dlapiduz thx.  this is good.


Plugin doesn't work after pod restart

Hello,
I m using the latest version of this plugin trough the gocd helm chart, when I deploy the helm chart for the first time everything works fine but when I restart the pod (or the pod gets restarted by a helm update) I get the following error
2024-01-05 10:36:54,589  INFO [167@MessageListener for ServerPingListener] p.c.g.c.e.k.c.g.c.e.KubernetesPlugin:72 [plugin-cd.go.contrib.elasticagent.kubernetes] - Did not find any running kubernetes pods.
2024-01-05 10:37:54,579 ERROR [167@MessageListener for ServerPingListener] p.c.g.c.e.k.c.g.c.e.KubernetesPlugin:127 [plugin-cd.go.contrib.elasticagent.kubernetes] - Error occurred while trying to list kubernetes pods:
io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET at: https://<IP_ADDRESS>:443/api/v1/namespaces/gocd/pods. Message: Unauthorized. Received status: Status(apiVersion=v1, code=401, details=null, kind=Status, message=Unauthorized, metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=Unauthorized, status=Failure, additionalProperties={}).

Is this the expected behavior when running in a cluster? do I need to add extra configuration in order to avoid this? Thanks

It's not expected that if it works fine via the Helm chart the first time that it stops working thereafter with no other changes made on your side of things. I assume by "works fine", you mean can create new pods etc and then after the restart nothing works at all, it cannot create new pods etc?
There should be many more errors fro logs than that if it cannot create pods etc, I'd have thought.
Which Kubernetes version, Kubernetes type (EKS? GKE? a local single node deployment? etc?) and GoCD Helm chart version are you using?

Thanks for the reply.
By works fine I mean that it creates agents pods whenever I trigger the example pipeline in gocd, the pipeline completes and then the agent pod shuts down.
When I restart the gocd-server pod and trigger the example pipline in gocd nothing happens and I get the logs shown.
I m using EKS and the k8s version is 1.25, the chart version that I m using is the latest one: 2.5.1
This is the full logs that I get from the gocd-server pod, after that it repeats the same error
jvm 1    | 2024-01-05 10:36:54,589  INFO [167@MessageListener for ServerPingListener] p.c.g.c.e.k.c.g.c.e.KubernetesPlugin:72 [plugin-cd.go.contrib.elasticagent.kubernetes] - Did not find any running kubernetes pods.
jvm 1    | 2024-01-05 10:37:54,579 ERROR [167@MessageListener for ServerPingListener] p.c.g.c.e.k.c.g.c.e.KubernetesPlugin:127 [plugin-cd.go.contrib.elasticagent.kubernetes] - Error occurred while trying to list kubernetes pods:
jvm 1    | io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET at: https://<IP_ADDRESS>:443/api/v1/namespaces/gocd/pods. Message: Unauthorized. Received status: Status(apiVersion=v1, code=401, details=null, kind=Status, message=Unauthorized, metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=Unauthorized, status=Failure, additionalProperties={}).
jvm 1    |     at io.fabric8.kubernetes.client.KubernetesClientException.copyAsCause(KubernetesClientException.java:238)
jvm 1    |     at io.fabric8.kubernetes.client.dsl.internal.OperationSupport.waitForResult(OperationSupport.java:507)
jvm 1    |     at io.fabric8.kubernetes.client.dsl.internal.BaseOperation.list(BaseOperation.java:450)
jvm 1    |     at io.fabric8.kubernetes.client.dsl.internal.BaseOperation.list(BaseOperation.java:418)
jvm 1    |     at io.fabric8.kubernetes.client.dsl.internal.BaseOperation.list(BaseOperation.java:97)
jvm 1    |     at cd.go.contrib.elasticagent.KubernetesAgentInstances.refreshAll(KubernetesAgentInstances.java:156)
jvm 1    |     at cd.go.contrib.elasticagent.KubernetesPlugin.refreshInstancesForCluster(KubernetesPlugin.java:140)
jvm 1    |     at cd.go.contrib.elasticagent.KubernetesPlugin.refreshInstancesForAllClusters(KubernetesPlugin.java:122)
jvm 1    |     at cd.go.contrib.elasticagent.KubernetesPlugin.handle(KubernetesPlugin.java:90)
jvm 1    |     at com.thoughtworks.go.plugin.infra.DefaultPluginManager.lambda$submitTo$0(DefaultPluginManager.java:134)
jvm 1    |     at com.thoughtworks.go.plugin.infra.FelixGoPluginOSGiFramework.executeActionOnTheService(FelixGoPluginOSGiFramework.java:205)
jvm 1    |     at com.thoughtworks.go.plugin.infra.FelixGoPluginOSGiFramework.doOn(FelixGoPluginOSGiFramework.java:164)
jvm 1    |     at com.thoughtworks.go.plugin.infra.DefaultPluginManager.submitTo(DefaultPluginManager.java:131)
jvm 1    |     at com.thoughtworks.go.plugin.access.PluginRequestHelper.submitRequest(PluginRequestHelper.java:49)
jvm 1    |     at com.thoughtworks.go.plugin.access.elastic.v5.ElasticAgentExtensionV5.serverPing(ElasticAgentExtensionV5.java:152)
jvm 1    |     at com.thoughtworks.go.plugin.access.elastic.ElasticAgentExtension.serverPing(ElasticAgentExtension.java:63)
jvm 1    |     at com.thoughtworks.go.plugin.access.elastic.ElasticAgentPluginRegistry.serverPing(ElasticAgentPluginRegistry.java:51)
jvm 1    |     at com.thoughtworks.go.server.messaging.elasticagents.ServerPingListener.onMessage(ServerPingListener.java:31)
jvm 1    |     at com.thoughtworks.go.server.messaging.elasticagents.ServerPingListener.onMessage(ServerPingListener.java:21)
jvm 1    |     at com.thoughtworks.go.server.messaging.activemq.JMSMessageListenerAdapter.runImpl(JMSMessageListenerAdapter.java:83)
jvm 1    |     at com.thoughtworks.go.server.messaging.activemq.JMSMessageListenerAdapter.run(JMSMessageListenerAdapter.java:63)
jvm 1    |     at java.base/java.lang.Thread.run(Unknown Source)
jvm 1    | Caused by: io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET at: https://<IP_ADDRESS>:443/api/v1/namespaces/gocd/pods. Message: Unauthorized. Received status: Status(apiVersion=v1, code=401, details=null, kind=Status, message=Unauthorized, metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=Unauthorized, status=Failure, additionalProperties={}).
jvm 1    |     at io.fabric8.kubernetes.client.dsl.internal.OperationSupport.requestFailure(OperationSupport.java:660)
jvm 1    |     at io.fabric8.kubernetes.client.dsl.internal.OperationSupport.requestFailure(OperationSupport.java:640)
jvm 1    |     at io.fabric8.kubernetes.client.dsl.internal.OperationSupport.assertResponseCode(OperationSupport.java:589)
jvm 1    |     at io.fabric8.kubernetes.client.dsl.internal.OperationSupport.lambda$handleResponse$0(OperationSupport.java:549)
jvm 1    |     at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(Unknown Source)
jvm 1    |     at java.base/java.util.concurrent.CompletableFuture.postComplete(Unknown Source)
jvm 1    |     at java.base/java.util.concurrent.CompletableFuture.complete(Unknown Source)
jvm 1    |     at io.fabric8.kubernetes.client.http.StandardHttpClient.lambda$completeOrCancel$10(StandardHttpClient.java:140)
jvm 1    |     at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(Unknown Source)
jvm 1    |     at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(Unknown Source)
jvm 1    |     at java.base/java.util.concurrent.CompletableFuture.postComplete(Unknown Source)
jvm 1    |     at java.base/java.util.concurrent.CompletableFuture.complete(Unknown Source)
jvm 1    |     at io.fabric8.kubernetes.client.http.ByteArrayBodyHandler.onBodyDone(ByteArrayBodyHandler.java:52)
jvm 1    |     at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(Unknown Source)
jvm 1    |     at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(Unknown Source)
jvm 1    |     at java.base/java.util.concurrent.CompletableFuture.postComplete(Unknown Source)
jvm 1    |     at java.base/java.util.concurrent.CompletableFuture.complete(Unknown Source)
jvm 1    |     at io.fabric8.kubernetes.client.okhttp.OkHttpClientImpl$OkHttpAsyncBody.doConsume(OkHttpClientImpl.java:136)
jvm 1    |     at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
jvm 1    |     at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
jvm 1    |     ... 1 common frames omitted

It kind of looks like the service account token you're using somehow doesn't have the permissions for the namespace it's trying to look for agent pods within.

Are there any values from the chart that you override on installation (for the server, that is). Especially anything related to the storage mounts/volumes.

Did you go in and modify any of the values in Elastic Agents Configurations (either the main cluster profile, or the individual elastic agent profile?

How did you go about granting the right permissions for the service account? As noted in #328 there are a few ways to do this. I can't recall if 1.25 still is doing all the magic to allow this to work without k8s admin work, so anything you did here would be good to know.

Are there any weird changes being shown to the GoCD server config after the restart?
The Helm chart tries to bootstrap the server with an initial config that makes sense, however something may be being changed after the first run, or the restart is somehow removing some important config or not using the right service account token. You may be able to see these changes made to the server config from the Stage Details view for a build you are trying to run - when logged in as an admin look for these "Config Changed" links on the Stage history:

OK, I have confirmed that this is because of changes in the way "bound service account tokens" work in Kubernetes 1.24+. They are now bound to the pod lifecycle, rather than the service account itself so they used to basically last forever, but not do not.
What this means is that the "magic" the GoCD Helm chart does on first start to populate the service account token into the "cluster profile" populates your pod with an auto-mounted token bound to the pod. It only does this once. When the pod restarts, this token is invalidated by the Kubernetes API and is no longer valid. It may also not work for longer than 1 hour, since the plugin and GoCD cannot re-read the value.

Essentially, this makes the automation in the Helm chart deceptive as it won't work for long.
To fix this right now, you need to do something like mentioned in #328 to create a long-lived token, extract it from Kubernetes and then replace the value in your cluster profile with this.
Additionally, if you don't manually set the CA Certificate Data, you might experience a different bug I have fixed in this release included in the latest Helm chart version (2.5.2).
In any case, this needs a better fix as the Helm chart is currently misleading. Will move this issue there as the main problem is with the misleading behaviour of the Helm chart which makes you think you don't need to do anything with the service account tokens to keep it working, since on first install it will work for a while without the user doing anything.


Disable rlike integration tests

Signed-off-by: Andy Grove<EMAIL_ADDRESS>Disabling tests due to failures on Azure Databricks 7.3
Related to #3866

build


HTML report

Currently the summary is in the jupyter book. For the finalised product, we prefer to generate a HTML report.

The figure generation is more streamlined now! Check how to adapt to reports.

I decided this might not be the top priority for the paper. If we ever ship the tool used in this paper as software, this might be useful. Close for now.


PanelContainer applies its margin non-deterministically

Godot version
v3.4.1.stable.official [aa1b95889]
System information
Ubuntu 18.04
Issue description
The PanelContainer seems to apply its margin inconsistently. This can be annoying, because tiny code changes can lead to differently sized panels.
Steps to reproduce
I'm using a custom container, and for the purpose of the example I'm creating the GUI tree programmatically to make reproduction clear. Basically the tree is as follows:

The custom container is set to "full rect". It's layout logic is very simple: It places its Wrapper child so that it has a 50 px border on all sides. The CustomPanelContainer and ColorRect are also set to "full rect" anchors, so that they should fully cover the area defined by the wrapper.

Full implementation of `CustomContainer`
extends Container

func _ready():
    set_anchors_preset(PRESET_WIDE, true)

    create_subtree()

    # warning-ignore:return_value_discarded
    connect("sort_children", self, "_on_sort_children")

func _on_sort_children():
    print("Layout children")
    var available_size = self.rect_size
    for child in self.get_children():
        var size = available_size - Vector2(100, 100)
        var pos = Vector2(50, 50)
        fit_child_in_rect(child, Rect2(pos, size))

func create_subtree():
    # The 'wrapper' will be controlled by this container:
    var wrapper = Control.new()
    wrapper.name = "Wrapper"

    # The 'wrapper' in turn contains two children that are both set to 'full rect'
    var custom_panel_container = CustomPanelContainer.new()
    custom_panel_container.name = "CustomPanelContainer"
    custom_panel_container.set_anchors_preset(Control.PRESET_WIDE)
    wrapper.add_child(custom_panel_container)

    var color_rect = ColorRect.new()
    color_rect.name = "ColorRect"
    color_rect.set_anchors_preset(Control.PRESET_WIDE)
    color_rect.color = Color(1, 0, 0, 0.1)
    wrapper.add_child(color_rect)

    add_child(wrapper)

Things get really weird in the _ready function of the CustomPanelContainer:
extends PanelContainer
class_name CustomPanelContainer

func _ready():
    print("_ready PanelContainer")

    # The following two lines should clearly be a no-op but they aren't.
    if rect_position.x == 0:
        rect_position.x = 0

    print(self.margin_right)
    print(self.margin_bottom)

Obviously, setting the rect_position.x to zero if it already is zero should have no effect at all. However, it does! When running the example the output is:

The printed values show that the right and bottom margins have taken a value of 14, which is also visible from the transparent overlay of the color rect. Commenting out the two lines, i.e., not touching rect_position.x at all results in:

This time the right/bottom margins stay at 0, and the panel container behaves identical to the color rect.
This issues is very annoying in practice, because I'm often noticing that tiny code changes related to panel container result their size changing unexpectedly. For instance the underlying use case here was: My implementation of panel placement was working fine. Then I wanted to apply a transition effect, which touches rect_position.x. Because the tween now modulates the rect_position.x property the panel placement broke because the panels suddenly applied this undesired right/bottom margin.
Minimal reproduction project
ContainerUpdateBug1.zip
Or on GitHub

I just re-evaluated this issue under Godot 4.1 and it seems to behave correctly now (updated reproduction example).


Add subtask input plugin

Motivation for changes:
Be able to manipulate and filter entries before passing in to plugins like configure_series, or discover.
Detailed changes:

Creates a new input plugin which produces the resulting accepted entries from another task run.

Config usage if relevant (new plugin or updated schema):
tasks:
  task_a:
     mock:
      - title: blah
      accept_all: yes
  task_b:
    discover:
      what:
      - from_task: task_a
      from:
      - somewhere

To Do:

[x] Do we like the name 'subtask' best? What about 'from_task'? (going with from_task)
[x] Currently for logging the subtask name is parenttask>subtask is that good?
good enough for me.
[x] Should the 5 minute caching mechanism be enabled for subtask results?
Decided against this for now at least.
[ ] Is there an alternative way to disable the seen plugin, or some other solution to make that not necessary?
[x] Do we allow/require subtasks to be in a new root level 'subtasks' key? If not, is there a better way to prevent them from being executed by default from cli or daemon scheduling?
Skipping this for now. Can always be added later.
[x] Do we pass on the options of the parent task to the subtask? --inject is probably a very bad to pass on, but do we want/need other things passed on?
Let's not pass any options through right now. If we discover something that should be we can re-think.

I totally get the need for this, but this feels very hacky. I think ideally we want that ability to chain tasks to each other and that should be the direction, and not neccesarily introduce new hybrid solutions like this.

@liiight How do you mean chain tasks?

I sorta like this method. It doesn't really allow anything different than clearing then saving to an entry_list and using it somewhere else, but this way feels like it might be a bit easier. I've considered chaining tasks with something similar to run_task, but that passes entries along, but that doesn't help us in cases where we want to use the entries inside discover, or configure_series

@liiight How do you mean chain tasks?

I've tried putting something down only to get something almost similar to what you did, so NM :)

@liiight @paranoidi @cvium Any thoughts on the TODO checklist questions? I like this method, but want to get a little feedback on those points before merging it in.

@liiight @paranoidi Is from_task (ala from_deluge, from_transmission) a better name than subtask?

from_task is clearer for me

from_task is clearer for me

That's the way I'm leaning as well. I think it makes it more clear it's just an input. Especially if already familiar with from_deluge etc.

Wiki update: https://github.com/Flexget/wiki/commit/e336ec46fb5f099eef081e86d30c28835606fd5d

Does the flexget.com search database need to be updated when adding new plugins? I searched for "from_task" in the search bar on flexget.com "https://flexget.com/_search?q=from_task" but it comes up empty. I guessed the url and it took me to the page, so I know it DOES exist. I think there may have been a handful of other plugins that don't come up in a search, too. But I cannot remember which ones...

Does the flexget.com search database need to be updated when adding new plugins? I searched for "from_task" in the search bar on flexget.com "https://flexget.com/_search?q=from_task" but it comes up empty. I guessed the url and it took me to the page, so I know it DOES exist. I think there may have been a handful of other plugins that don't come up in a search, too. But I cannot remember which ones...

Seems like maybe the search index update was getting bypassed when syncing from the github repo (or something.) I've added a weekly cronjob to re-index, hopefully that keeps things working better.


Remove useless comma, which lead to bower install failed

The comma lead to bower install failed?

#25 #26 seems to be the same problem

Can we separate the filter-contains and comma fix commits into different PRs? Thanks! And yes..same issue. Sorry!

Yes, I have re-committed...
I think maybe not too many people need filter-contains, I can keep it in my branch

Change LGTM. Thanks!

I'll be doing some more Polymer issue triage today and will cut out a release of this as part of that.


Is it possible to use this with 'faster_whisper'

Is it possible to use this distilled model with https://github.com/guillaumekln/faster-whisper? I imagine 15-20x base

Closing as a repeat of #3! Feel free to follow along progress there!


⚠ Bofrost.fr has degraded performance

In 217421a, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1657 ms

Resolved: Bofrost.fr performance has improved in 48024be after 12 minutes.


Server.go file missing #7887

Notes for Reviewers
Updated server.go url and Remote Providers.
This PR fixes #7887
Signed commits

[X] Yes, I signed my commits.

🚀 Preview for commit ade0e0b5e9e609cade7a856c4411087bd6faa9ea at: https://6491c84c7dc74906e7807eec--meshery-docs-preview.netlify.app


InMemroyDatabase with InMemoryDatabaseRoot gets empty database each time

EF Core version: 2.2.6
I'm trying to write integration test of an API that have a shared instance of an InMemory database. Although I'm using an InMemoryDatabaseRoot, I always get a new empty database.
I'm using xunit and I have my CustomWebApplicationFactory as a fixture in a fixture collection to share it among the tests. Tests are decorated with the collection.
    public class CustomWebApplicationFactory<TStartup> : WebApplicationFactory<Startup>
    {
        private static readonly InMemoryDatabaseRoot databaseRoot = new InMemoryDatabaseRoot();

        protected override void ConfigureWebHost(IWebHostBuilder builder)
        {
            builder.ConfigureServices(services =>
            {
                // Create a new service provider.
                var serviceProvider = new ServiceCollection()
                    .AddEntityFrameworkInMemoryDatabase()
                    .BuildServiceProvider();

                // Add a database context (AppDbContext) using an in-memory database for testing.
                services.AddDbContext<MyContext>(opts => {
                    opts.UseInMemoryDatabase("InMemoryAppDb", databaseRoot);
                    opts.UseInternalServiceProvider(serviceProvider);
                });

                // Build the service provider.
                var sp = services.BuildServiceProvider();

                // Create a scope to obtain a reference to the database contexts.
                using (var scope = sp.CreateScope())
                {
                    var scopedServices = scope.ServiceProvider;
                    var appDb = scopedServices.GetRequiredService<MyContext>();
                    var logger = scopedServices.GetRequiredService<ILogger<CustomWebApplicationFactory<TStartup>>>();

                    // Ensure the database is created.
                    appDb.Database.EnsureCreated();

                    try
                    {
                        // Seed the database with some specific test data.
                        DatabaseSeeder.PopulateTestData(appDb);

                        logger.LogInformation("Database seeded");
                    }
                    catch (Exception ex)
                    {
                        logger.LogError(ex, "An error occurred seeding the database. " +
                                            "Error: {ex.Message}");
                    }
                }
            });
        }
    }

Now I have verified using the debugger that the InMemory context actually takes precedence over the context defined in the SUT API. Good there: database seeding gets called and runs fine.
For a variety of reasons, sometimes in the SUT I need to create a context "manually" - aka: new MyContext(options) - and I'm pulling the dbContextOptions<MyContext> that I pass to it from the DI. I verified again with the debugger that the options pulled have the InMemory provider, the database name and the InMemoryDatabaseRoot reference.
According to the here

All in-memory databases will be rooted in this object, allowing the application to control their lifetime. This is useful when sometimes the context instance is created explicitly with new while at other times it is resolved using dependency injection

this seems exactly my case but it is not working for me - the database I get is empty.
What am I getting wrong?
Thank you.

@EPinci Since CustomWebApplicationFactory<TStartup> each use of the class with a different TStartup will get its own static databaseRoot. Can you check that databaseRoot is the same instance in both places it is used?
If it's not that, then please post a small, runnable project/solution or complete code listing that demonstrates the behavior you are seeing.

EF Team Triage: Closing this issue as the requested additional details have not been provided and we have been unable to reproduce it.
BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.


Command for resending verification

Hey, i have a great idea for the bot. Add a command for resending the captcha link. It would be useful because some people do not look at their dms after joining servers.

Also while i am at it, is ot possible for the page not to be tagged as dangerous? It makes 9 out of each 50 people leave

Hey, i have a great idea for the bot. Add a command for resending the captcha link. It would be useful because some people do not look at their dms after joining servers.

Great idea, I will think about adding this.

Also while i am at it, is ot possible for the page not to be tagged as dangerous? It makes 3 out of each 100 people leave

It is possible, you must setup the https mode with an ssl certificate. You can generate some with Let's Encrypt.

Holy shit, i did not expect a response

You can google how to generate an SSL certificate with Let's Encrypt and you should find a way to do it, if not just message back.

I am adding these labels if anyone would be interested in opening a pull request,

Also while i am at it, is ot possible for the page not to be tagged as dangerous? It makes 3 out of each 100 people leave

it might be your domain tho, it might be flagged by google
run a test here
https://transparencyreport.google.com/safe-browsing/search?url=yourdomain.name

Good late afternoon.  :)


3D Terrain Effect in the Footer to replace the current illustration

Reference Video
Build it as a component

I want to work on this. Please assign it to me.

any updates?

@smaranjitghose what you mean by component here?

https://github.com/smaranjitghose/awesome-portfolio-websites/tree/reactjs/src/components create 3d wave here and import it directly to the footer in pages folder so that footer has less amount of code.

okay didn't notice there is reactjs branch as well

is your goal to replace this graphic with terrain one?

@smaranjitghose
demonstration from my side
https://user-images.githubusercontent.com/74287984/132100261-125fb5cd-8363-48eb-8dc0-f3efc0c3436a.mp4
I have created a terrain component.
For demonstration purpose I have imported it in a div inside footer.

The terrain component can be imported anywhere and will occupy 100% of parent container.
background of terrain is transparent so it will blend with background.
The bump is totally dependent on height map, different height maps will give different results.
only one dependency added ie THREE

If everything fine then tell me. I will raise PR

@Serjeel-Ranjan-911  i would like to know more about terrain geometry, throw more light on this and have more ideas

@Nzamuyejoram
The terrain is a 2d plane which is divided in a grid of 64 by 64. Now each point on this grid is given a vertical height based on a displacement map. Displacement map is just a black and white image which stores height information. The terrain is blue in colour due to the light projected on it.


Added Chrony NTP support

Starting with Ubuntu 18.04 (Bionic), chrony becomes the NTP default service. ntpd is not installed by default.
Also the latest Juju ntp charm (for Bionic) deploy chrony instead of ntpd (https://jujucharms.com/ntp/) so Contrail 5 deployment via Juju fails.
ntpd is progressively replaced by chrony also on the other linux distributions (like RHEL) because of the Autokey protocol that has serious security issues.
This is a generic check (not dependent by Linux dist) to support trigger the NTP check depending by the running NTP service.

Contrail/Tungsten Fabric does not accept GitHub pull requests. All changes should be submitted via the Gerrit code review tool. If you're not familiar with Gerrit, take a look at section 4 of https://github.com/tungstenfabric/docs/blob/master/Contributor/GettingStarted/getting-started-with-opencontrail-development.md for more info.
The key points are that you need to login to https://review.opencontrail.org with an Ubuntu One account in order to establish your SSH public key. You need to clone the repos from Gerrit rather than (or in addition to) GitHub (or manually add an additional remote to an existing repo rather than cloning if you prefer). And you need to install and use the "git review" extension to Git in order to push changes to Gerrit.


Remove examples for web components

We had some experiments rendering web components within the readme. As we don't further proceed this experiment we can remove the example directory for it.

Related to https://github.com/stateful/vscode-runme/issues/74

@sourishkrout this is ready for review, it updates all dependencies as well (except for @vscode/webview-ui-toolkit due to https://github.com/microsoft/vscode-webview-ui-toolkit/issues/432).


Quality of life improvements, part 1 (custom styles)

Don't show window until window.ready-to-show, this prevents the white flicker
Moved the daisy chain of scss imports into the root scss file.
Changed .js files to .jsx where applicable and added to build
Debounce saving prefs file to 200ms to prevent disk bombs when changing prefs like the slider (hundreds of writes per second, SSDs hate it)
Added a css option to provide a custom stylesheet. Fixes #57

I have more coming, just didn't want to overwhelm in a single PR

@pvrobays if you get a chance I'd love your eyes on this

Awesome! I'm very exited by reading the changes in the description @lacymorrow. I'll have a decent look tomorrow.

@lacymorrow It's merged!
The PR did make me think of a new feature: Themes.
That way the user can start from one of the different themes, and then continue to add his own custom css on top. I'll create an issue for it.

Thank you! I appreciate the quick turnaround here.
Themes are a great idea! Would be super welcome.


localhost:3000/null on IE

after login page of azure my app redirect to localhost:3000/null in internet explorer but working fine on other browsers. please help out

I think i am having similar issue, I have imported React polyfills for ie11 and stable, updated package.json to include the 'ie11' . I have also disabled protected mode on IE locally but the script is stopping at react-azure-adb2c code in chunk.js when trying to import modules.
Critical error was detected at line 1199, column 65 in https://localhost:5001/static/js/main.chunk.js.
SCRIPT1002: Syntax error


Remove APIRule v1alpha1 types and sync CRD documentation

Description

The version v1alpha1 of APIRule is deprecated and we want to remove it, before we release the module. Therefore we should delete. We should also delete all the old code that was used by conversion webhook.
Additionally when generating the APIRule CRD from the go types there is a mismatch of the generated documentation. The current documentation on the CRD were copied from the kyma-repository and should be considered the latest state. This means we have to adapt the go types, so the generation of the CRD won't display any changes.
ACs:

[ ] APIRule v1alpha1 is removed
[ ] APIRule type documentation is adapted
[ ] APIRule conversion webhook code is removed

Attachments

Kyma PR: https://github.com/kyma-project/kyma/pull/18152
API Gateway PR: https://github.com/kyma-project/api-gateway/pull/516


Old links, and overall deprecated "quick start"

Hi,
links are no longer valid in your doc. For example here:
https://github.com/zeganstyl/thelema-engine/wiki/Postprocessing-shaders
Links there lead to 404 error. Please update the links. Also can you please add some contact info to you? (mail, facebook)

@rafi0 Hello
Yes, I had to freeze the development of the engine and did not work on it for a while. I made the last commit in a hurry.
Soon, perhaps in a few months or sooner, I will update everything.
Now, I think, only tests can be actual, and even then not all.
Email<EMAIL_ADDRESS>


[Sandbox] Koordinator

Application contact emails
<EMAIL_ADDRESS><EMAIL_ADDRESS>Project Summary
A QoS-based scheduling system brings optimal layout and status to workloads such as microservices, web services, big data jobs, AI jobs, etc.
Project Description
Koordinator is a QoS based scheduling system for hybrid orchestration workloads on Kubernetes. Its goal is to improve the runtime efficiency and reliability of both latency sensitive workloads and batch jobs, simplify the complexity of resource-related configuration tuning, and increase pod deployment density to improve resource utilization.
Koordinator enhances the kubernetes user experiences in the workload management by providing the following:

Improved Resource Utilization: Koordinator is designed to optimize the utilization of cluster resources, ensuring that all nodes are used effectively and efficiently.
Enhanced Performance: By using advanced algorithms and techniques, Koordinator aims to improve the performance of Kubernetes clusters, reducing interference between containers and increasing the overall speed of the system.
Flexible Scheduling Policies: Koordinator provides a range of options for customizing scheduling policies, allowing administrators to fine-tune the behavior of the system to suit their specific needs.
Easy Integration: Koordinator is designed to be easy to integrate into existing Kubernetes clusters, allowing users to start using it quickly and with minimal hassle.

Org repo URL (provide if all repos under the org are in scope of the application)
https://github.com/koordinator-sh
Project repo URL in scope of application
https://github.com/koordinator-sh/koordinator
Additional repos in scope of the application
https://github.com/koordinator-sh/community
https://github.com/koordinator-sh/apis
https://github.com/koordinator-sh/koordetector
https://github.com/koordinator-sh/website
https://github.com/koordinator-sh/charts
Website URL
https://koordinator.sh/
Roadmap
https://github.com/koordinator-sh/community/blob/main/roadmap.md
Roadmap context
No response
Contributing Guide
https://github.com/koordinator-sh/koordinator/blob/main/CONTRIBUTING.md
Code of Conduct (CoC)
https://github.com/koordinator-sh/koordinator/blob/main/CODE_OF_CONDUCT.md
Adopters
https://github.com/koordinator-sh/koordinator/blob/main/ADOPTERS.md
Contributing or Sponsoring Org
Alibaba Cloud
Maintainers file
https://github.com/koordinator-sh/community/blob/main/MAINTAINERS.md
IP Policy

[X] If the project is accepted, I agree the project will follow the CNCF IP Policy

Trademark and accounts

[X] If the project is accepted, I agree to donate all project trademarks and accounts to the CNCF

Why CNCF?
The CNCF hosts a vibrant and diverse community of developers and organizations. Contributing to this ecosystem allows the Koordinator project to attract more contributors, leading to better and faster improvements. Furthermore, the CNCF is able to provide a vendor neutral home for the project, allowing for collaboration among various vendors, fostering the creation of a solution that delivers collective benefits to all stakeholders within the ecosystem.
Benefit to the Landscape
Koordinator provides a well-designed hybrid orchestration and SLO system for both serverless and batch workloads on Kubernetes. It facilitates users by optimize the utilization of their cluster resources, ensuring that all nodes are used effectively and efficiently. Simultaneously, it provides a range of options for customizing scheduling policies, allowing administrators to fine-tune the behavior of the system to suit their specific needs.
Cloud Native 'Fit'
The Koordinator best fits in under the "Scheduling and Orchestration" area of the landscape.
Cloud Native 'Integration'
The project should be installed and as a scheduler/operator in Kubernetes.
Cloud Native Overlap
There is no strong overlap with existing solutions that mainly focuses on hybrid orchestration scheduling and enhanced SLO management. Volcano, one of the CNCF projects, on the other hand, is mainly for those batch jobs scheduling and management.
Similar projects
Volcano may be, but they focus on different scheduling targets and areas.
Landscape
Yes, it's already in the "Scheduling & Orchestration".
Business Product or Service to Project separation
N/A
Project presentations
No response
Project champions
No response
Additional information
No response

@FillZpp  It'd be great if you could present Koordinator at a TAG Runtime meeting before the next TOC sandbox vote on Sept 12.
cc @raravena80 @helayoty @rajaskakodkar

@nikhita Sure, We are glad to do the presentation. Let's mark on calendar.

@FillZpp updated the TAG Runtime agenda with the presentation/discussion date.

hi @nikhita @amye , may I ask is there any progress on the TOC sandbox vote on Sept 12?

Hi @FillZpp, thanks for the follow up.
Not precluding the possibility that Koordinator can be a CNCF Sandbox project, there was a doubt with regards to how this project fits into the CNCF/K8s ecosystem.
The recommendation/consensus was (before voting for Koordinator as a CNCF Sandbox project) to reach out to (or communicate with) the following groups within the CNCF/K8s ecosystem to check if the project fits better into either the CNCF or the K8s ecosystem.

K8s SIG-Scheduling
K8s Batch Working Group
Batch System Initiative Working Group(TAG-Runtime)

Then come back with the outcome and proceed from there.
Feel free to reach out either here or on the CNCF slack if you have any other specific questions.
Thanks!

@raravena80 Is there any update? If you have any concerns, we can arrange an online meeting to discuss it.

Per my understanding on Koordinaor, its stack involves both scheduling and runtime, and even more. Shaping it as a sub-project of sig-scheduling does't quite reveal its accurate scope. My 2 cents is that a standalone sandbox project makes more sense to Koordinator.

@raravena80 to provide summarization in order for the project to move to the next steps (need-info or vote)

Based on the 'no concerns' from K8s SIG-Scheduling, as a next step before the Jan 23 sandbox application review, I'd like to request if there are any concerns from the following community members:

K8s Batch

@Huang-Wei
@endocrimes
@mwielgus
@soltysh
@swatisehgal

WG BSI

@stackedsax
@k82cn
@yangwwei

If there are aren't any before the meeting. I see no issues with the sandbox application and say that the project is ready for a vote.
Thanks!

That looks good to me :).
A sandbox seems better for Koordinator instead of sub-project of k8s sigs, as it includes several enhancement cross different components.

+1 from me too and I think the project is ready for a sandbox vote!

For k8s wg-batch, I'd suggest showing up to one of the first calls in Jan and discuss with the broader community there.

@FillZpp following up.  Were you able to connect with wg-batch? Thanks!

@FillZpp following up. Were you able to connect with wg-batch? Thanks!

@rajaskakodkar @amye I have introduced the project and discussed with wg-batch broader community yesterday. We have reached an agreement that Koordinator is ready for a sandbox vote.

/vote-sandbox

/check-vote

/check-vote

/check-vote

/check-vote

Heya @FillZpp!
Welcome aboard! We're very excited to get you onboarded as a CNCF sandbox project! Here's the link to your onboarding checklist: https://github.com/cncf/toc/issues/1302
That issue is where you can communicate any questions or concerns you might have. Please don't hesitate to reach out!

With the onboarding issue open at: https://github.com/cncf/toc/issues/1302
I'm going to go ahead and close this out. 👍
Thanks!


TransferWithAuthorization does not emit event

Having implemented EIP-712 signing and use of transferWithAuthorization instead of transfer, I was expecting the contract to emit an event. But I can't see any emitted on Etherscan or find any reference to it in the code.
Is it really true that it does not emit an event? @petejkim
If so can we please get that on the feature list for the next update.

My bad (I think). Seems to emit the same events as transfer.
For some reason they are not being picked up by our code so I'll need to debug further.

For anyone who might end up here in the future:
The event emitted after a transferWithAuthorization transaction  is AuthorizationUsed,
which has different (or missing) parameter names:
Instead of to, it uses 0.
Instead of from, it uses 1.


[TC_MC_3.6] Missing CurrentApp attribute in applicationlauncher cluster in TE7.5

Problem
CurrentApp attribute is not listed in the available attributes but is needed to run [TC-MC-3.6] Current App Verification, step 1.

Test Case
TE7.5 commit: b0af6ba42b6ce494748f18ecf3e054a400b8f45b
3.4.2. [TC-MC-3.6] Current App Verification
https://github.com/CHIP-Specifications/chip-test-plans/blob/TE_7_5_updates_IDM/src/cluster/media.adoc#tc-mc-3-6-current-app-verification
Logs

16-MacBook-Pro:chip-tool liam$ ./out/debug/chip-tool applicationlauncher read
[1642811926723] [99229:4621821] CHIP: [TOO] Missing attribute name
Usage:
./out/debug/chip-tool applicationlauncher read attribute-name [param1 param2 ...]
+-------------------------------------------------------------------------------------+
| Attributes:                                                                         |
+-------------------------------------------------------------------------------------+
| * application-launcher-list                                                         |
| * attribute-list                                                                    |
| * cluster-revision                                                                  |
+-------------------------------------------------------------------------------------+
[1642811926723] [99229:4621821] CHIP: [TOO] Run command failure: ../../commands/common/Commands.cpp:99: Error 0x0000002F

@lazarkov I saw you are working on the initial implementation of this cluster, could we enable this attribute and complete the remaining work if there is any

@yufengwangca yes there are 2 PRs that will resolve this:
https://github.com/project-chip/connectedhomeip/pull/14794
https://github.com/project-chip/connectedhomeip/pull/14841

Either one of them will, and probably both of them will be merged in the next 24h.

Resolved.


fix a typo

should be tf.zeros_initializer()

Using zeros_initializer without calling it actually works. See the logic at: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/ops/variable_scope.py#L781

Thank you again, sq! I tested TensorFlow 1.0 and current version, and check the codes.  In TF 1.0, using zeros_initializer won't work because the codes are different either, but zeros_initializer() has no problem. For consistency's sake with the Vafiables document, I still believe it would be a good thing to point out both circumstances works or use either.


Help requested: Fan Modes

Is there a way to set the fan modes from an automation in Home Assistant.
It's a little annoying that you not can change the fan modes from the main Climate interface, but you have to click the 3 dots top right (more information) to get to the Fan Modes.
Any help would be appreciated

You can use Climate: Set Fan Mode

By looking at Dev Tools -> States -> your AC entity, you can see the modes available per here:

Thanks, this helped me a lot.


How to add russia country

How to add  country iraq

Hi there,
Please refer to the following section
https://github.com/faisalthaheem/open-lpr#training-your-own-plate-detection-models
Thanks


dialer.DialContext undefined

New Ubuntu VM.  Followed instructions to get PWD running locally.
poldim@ubuntu:~/play-with-docker$ docker-compose up
WARNING: The Docker Engine you're using is running in swarm mode.

Compose does not use swarm mode to deploy services to multiple nodes in a swarm. All containers will be scheduled on the current node.

To deploy your application across the swarm, use `docker stack deploy`.

Creating haproxy ... done
Creating l2      ... done
Creating pwd     ... done
Attaching to pwd, haproxy, l2
haproxy    | [WARNING] 148/163845 (1) : config : missing timeouts for frontend 'http-in'.
haproxy    |    | While not properly invalid, you will certainly encounter various problems
haproxy    |    | with such a configuration. To fix this, please ensure that all following
haproxy    |    | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
haproxy    | [WARNING] 148/163845 (1) : config : missing timeouts for backend 'pwd'.
haproxy    |    | While not properly invalid, you will certainly encounter various problems
haproxy    |    | with such a configuration. To fix this, please ensure that all following
haproxy    |    | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
haproxy    | [WARNING] 148/163845 (1) : config : missing timeouts for backend 'l2'.
haproxy    |    | While not properly invalid, you will certainly encounter various problems
haproxy    |    | with such a configuration. To fix this, please ensure that all following
haproxy    |    | timeouts are set to a non-zero value: 'client', 'connect', 'server'.
haproxy    | [NOTICE] 148/163845 (1) : New worker #1 (6) forked
pwd        | # github.com/docker/go-connections/sockets
pwd        | ../../docker/go-connections/sockets/sockets.go:34:26: dialer.DialContext undefined (type proxy.Dialer has no field or method DialContext)
pwd        | ../../docker/go-connections/sockets/sockets_unix.go:24:28: undefined: context
l2         | # github.com/docker/go-connections/sockets
l2         | ../../../../docker/go-connections/sockets/sockets.go:34:26: dialer.DialContext undefined (type proxy.Dialer has no field or method DialContext)
l2         | ../../../../docker/go-connections/sockets/sockets_unix.go:24:28: undefined: context
l2 exited with code 2
pwd exited with code 2

did you run this? https://github.com/play-with-docker/play-with-docker#development
Seems like a problem with dependencies.

Yes, I'm not familiar with go so I had some trouble with dep ensure.  I
found the file and tried executing the command, but again, not
familiar with it.
poldim@ubuntu:~$ cd ./.go/src/github.com/play-with-docker/play-with-docker/
poldim@ubuntu:~/.go/src/github.com/play-with-docker/play-with-docker$ dep
ensure
/home/poldim/.go/src/github.com/play-with-docker/play-with-docker is not
within a known GOPATH/src
poldim@ubuntu:~/.go/src/github.com/play-with-docker/play-with-docker$
export GOPATH=$HOME/.go
poldim@ubuntu:~/.go/src/github.com/play-with-docker/play-with-docker$ dep
ensure
Warning: the following project(s) have [[constraint]] stanzas in Gopkg.toml:

  ✗  github.com/docker/distribution
  ✗  github.com/googollee/go-socket.io
  ✗  github.com/zbindenren/negroni-prometheus

However, these projects are not direct dependencies of the current project:
they are not imported in any .go files, nor are they in the 'required' list
in
Gopkg.toml. Dep only applies [[constraint]] rules to direct dependencies, so
these rules will have no effect.

Either import/require packages from these projects so that they become
direct
dependencies, or convert each [[constraint]] to an [[override]] to enforce
rules
on these projects, if they happen to be transitive dependencies.

On Wed, May 29, 2019 at 11:13 AM Marcos Nils<EMAIL_ADDRESS>wrote:

did you run this?
https://github.com/play-with-docker/play-with-docker#development
Seems like a problem with dependencies.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/play-with-docker/play-with-docker/issues/338?email_source=notifications&email_token=AEAWSUK6IYVYL2NSGUDDVULPX3BVVA5CNFSM4HQOWT6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWQGDBI#issuecomment-497049989,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEAWSULYD6VZWUK4ZUIJVKLPX3BVVANCNFSM4HQOWT6A
.

Yes, I'm not familiar with go so I had some trouble with dep ensure.  I
found the file and tried executing the command, but again, not
familiar with it.
poldim@ubuntu:~$ cd ./.go/src/github.com/play-with-docker/play-with-docker/
poldim@ubuntu:~/.go/src/github.com/play-with-docker/play-with-docker$ dep
ensure
/home/poldim/.go/src/github.com/play-with-docker/play-with-docker is not
within a known GOPATH/src
poldim@ubuntu:~/.go/src/github.com/play-with-docker/play-with-docker$
export GOPATH=$HOME/.go
poldim@ubuntu:~/.go/src/github.com/play-with-docker/play-with-docker$ dep
ensure
Warning: the following project(s) have [[constraint]] stanzas in Gopkg.toml:

  ✗  github.com/docker/distribution
  ✗  github.com/googollee/go-socket.io
  ✗  github.com/zbindenren/negroni-prometheus

However, these projects are not direct dependencies of the current project:
they are not imported in any .go files, nor are they in the 'required' list
in
Gopkg.toml. Dep only applies [[constraint]] rules to direct dependencies, so
these rules will have no effect.

Either import/require packages from these projects so that they become
direct
dependencies, or convert each [[constraint]] to an [[override]] to enforce
rules
on these projects, if they happen to be transitive dependencies.

I also tried following this guide, https://jmkhael.io/deploying-play-with-docker-com-on-my-machine/, but I'm guessing it's out of date.


Add GitHub link in footer section.

What would you like to share or ask?
I want to add a GitHub link in the footer section.

Additional information
No response

Go ahead.

@prnvtripathi Please review my PR.

@prnvtripathi Please close this issue so that it can be counted as a contribution in GSSOC


AAD acount support

Is it only the local accounts you can add to the Azure Stack Edge? What about Azure Active Directory accounts?

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

ID: 50be3d10-6d94-fef1-4d41-42cc72c73fe2
Version Independent ID: 13d1d322-01b5-05f7-5024-0ce4ab9d0fca
Content: Azure Data Box Edge manage users
Content Source: articles/databox-online/data-box-edge-manage-users.md
Service: databox
Sub-service: edge
GitHub Login: @alkohli
Microsoft Alias: alkohli

@KapilaMunaweera Thank you for your feedback! We will review and update this thread with relevant info.

@KapilaMunaweera No, the Azure Active directory accounts are not supported. Thanks !

#please-close


Compatibility with D3 4.0+?

Thank you for this awesome tool.
I ran into an issue using this for a chart I'm making using D3 4.0 code. In the browser I'm getting this error message: Uncaught TypeError: Cannot read property 'axis' of undefined, which points to line 43 in browser.js: d3.svg._axis = d3.svg.axis;.
The new API docs use axisTop, axisLeft, axisRight and axisBottom. Is there a workaround or does this tool strictly worth with D3 V3 code?

Thanks @chrisalcantara. Currently this is only tested against v3, but I plan to add support for v4 shortly

Looking forward to it 👍

Hey @chrisalcantara, do you have handy example code for what is failing here? I have a branch that should be working with most v4 changes but need to test on axes still

What exactly are you looking for? The line of the code that's giving me the error?

Was just looking for more test cases but I think it should be all sorted out. v1.3.0 is released on npm and passes all tests with v4 of d3. Please let me know if you continue to have issues!

Thanks so much!


voc parser

🐛 Bug
When running the starting codes for the VOC, runs into error at the parser step.
To Reproduce
Steps to reproduce the behavior:

Go to https://airctic.github.io/icedata/examples/voc_exp/
Click on '....'
Scroll down to '....'
See error

Expected behavior
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):
Mac
Additional context
Add any other context about the problem here.

fixed with #115


Spaces removed from :not statement

Hello,
I have been using gulp wrapper of this package and have noticed the whitespace is removed from :not statements.
Basically if i have css:
button {
    &:not(.gmap &){
        @include button();
    }
}

The compiled css becomes (notice the space removed from .gmap and button:
button:not(.gmapbutton){/* the mixin css */}

When using the following gulp process:
return gulp.src(cssPath + '/**/*.css')
        .pipe(groupMediaQueries())
        .pipe(cleanCss({
            compatibility: ie8,
            level: 2
        }))
        .pipe(gulp.dest(cssPath));

I dig into this issue. The space is removed here
https://github.com/jakubpawlowicz/clean-css/blob/f2c633791f6f81d66223fb26c1c6571b6c65430b/lib/optimizer/level-1/tidy-rules.js#L115
Adding stripped.push(character); will break https://github.com/jakubpawlowicz/clean-css/blob/f2c633791f6f81d66223fb26c1c6571b6c65430b/test/fixtures/issue-241.css#L1

To differentiate the case of :not(.c1, .c2){} that can be minimized to :not(.c1,.c2){} and :not(.c1 .c2){} that cannot be minimized, we could verify the presence of a ',' in the selector.

Can you put attribute rule inside not, e.g. :not(.c1[data-id="1,2,3"] .c2)? But in general it's good idea to go that way.

Well, the exact CSS4 spec for :not states that the :not() pseudo-class requires a comma-separated list of one or more selectors as its argument. The list must not contain another negation selector or a pseudo-element.
According to CSS 3, only simple selector are valid in the argument of :not() pseudo-class and <attribute-selector> is a valid <simple-selector>.
According to CSS 4 grammar, <attribute-selector> is a valid <selector-list>.
So, in theory, the case that you show is possible.

Did you differentiate a <selector-list> and a <complex-selector> in the selector parser ? I didn't find if clean-css has implemented a selector parser or not.
We may have a look at css-tree for the selector parsing part.

Thanks @abarre for having a closer look at it.
clean-css doesn't have a selector parser, just simple optimizer - see https://github.com/jakubpawlowicz/clean-css/blob/master/lib/optimizer/level-1/tidy-rules.js, as I haven't found a good reason to have it.

I have the same issue with
.container:not(#BorlabsCookieBox .container) {
    max-width: 1280px !important;
}

being minified to:
.container:not(#BorlabsCookieBox.container) {max-width: 1280px !important;}

Which is not the same selector. Any suggestions how to circumvent this?

Fixed in e651f24e60353726a589c25659095f0858572344

Fixed in e651f24e60353726a589c25659095f0858572344

I just ran into the same issue and a quick check on https://jakubpawlowicz.github.io/clean-css/ running v5.1.1. doesn't seem to have solved the issue.
e.g. the example code that @tobiasvielmetter provided still produces the same minified output.

Hmmm, you are right @lluerich. I have no idea how it slipped through the tests. Let's reopen it.

This time it is fine, please see @tobiasvielmetter example in test cases - https://github.com/jakubpawlowicz/clean-css/commit/64d8c27ed34eb0806c45f8002989bbbeaa32fc71#diff-893825b7389c9d5a4f8db929537b0649c75836c0cb03446de8fb1d2716e1ddffR273
Sorry for trouble with extra testing & reporting.


feat(components): badge support for icon-only

Closes #711

I think that we need to enlarge the icon size in size - expended. Note that when expended or condense is set the padding are being overriden (doesn't effect the look because of the aspect-ration)

will follow design (in the works) https://www.figma.com/file/r8OYLPmRmDqfLKt6KHdJDB/branch/eiSBjHTMsNrioTbA1Kohru/Vivid-UI-Kit---2.0?node-id=16381%3A76273


add resources for new contributors

you can add resources for new contributors here and help me by contributing to this repository :)

Hello @deniss-eh, I am interested in contributing to this.
Could I be assigned to this issue?

Please Merge my PR #10

@SalmaanShire365 ya sure 😃

@SalmaanShire365 @HPatel08 You can also contribute to my new repository where you can contribute by opening pull requests for DSA related programs. :)
https://github.com/deniss-eh/DSA-HACKTOBERFEST


Debugger stops working after slight changes

Type: Bug
Upon launching the debugger recognises all syntax and matches the colour scheme for the different parts of the code (e.g variables commands etc).
After doing even the slightest code change (e.g. just pressing enter) most of the code will end up white and with nonsense errors. I wouldn’t even be able to go to function through the option ‘Go to Declaration”
The only way to recover the colour scheme but not the functionality is to close and open visual studio code but again there is no proper functionality as code suggestion doesn’t work after doing changes.
I haven’t found a workaround as yet but the code executes correctly even with the reported issues.

I am using Python.
After submitting this bug I closed all tabs and closed vs code and reopened and now even after doing changes to the code the colour scheme is retained and also debugger is working fine.
That doesn't mean that issue was resolved but it is going to make it more difficult for me to replicate the issue in case more info is required.

This is likely an issue with the python extension, and you can file an issue on their repo. But first you can verify that with the "Start extension bisect" command


⚠ TiendaEnLinea has degraded performance

In b23f7d7, TiendaEnLinea (https://www.fahorro.com/) experienced degraded performance:

HTTP code: 200
Response time: 5911 ms

Resolved: TiendaEnLinea performance has improved in ad5bcad.


gentium: 6.001 -> 6.101

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/gentium/versions.
meta.description for gentium is: "A high-quality typeface family for Latin, Cyrillic, and Greek"
meta.homepage for gentium is: "https://software.sil.org/gentium/"
meta.changelog for gentium is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 6.101 with grep in /nix/store/vkrhwk0ifk9x2cx5mhlhqq2rw40rciym-gentium-6.101

found 6.101 in filename of file in /nix/store/vkrhwk0ifk9x2cx5mhlhqq2rw40rciym-gentium-6.101

Rebuild report (if merged into master) (click to expand)

6 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
3 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
gentium
hottext
sile

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vkrhwk0ifk9x2cx5mhlhqq2rw40rciym-gentium-6.101 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A gentium https://github.com/r-ryantm/nixpkgs/archive/48c3003616afc893806326aed5467902d64f7d23.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vkrhwk0ifk9x2cx5mhlhqq2rw40rciym-gentium-6.101
ls -la /nix/store/vkrhwk0ifk9x2cx5mhlhqq2rw40rciym-gentium-6.101/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package marked as broken and skipped:

hottext

1 package failed to build:

sile

1 package built:

gentium

Maintainer pings
cc @7c6f434c @rycee for testing.

sile seems to be a new but unrelated regression


Add tritoncache APIs

Main Changes:

General structure of new TRITONCACHE APIs and scaffolding from CLI to Core has added

tritoncache.cc was added with core-side TRITONCACHE API implementations
cache_manager.* and cache_entry.* have been added to encapsulate shared library communication
Some optimizations can definitely be made in the number of copies being done and lifetimes/ownership, open to a lot of feedback here

--response-cache-byte-size and corresponding C API has been deprecated in favor of --cache-config and --cache-dir. SetResponseCacheByteSize API will now call SetCacheConfig with specified size for now.
Some "band-aid" fixes have been made on the metrics/stats related to caching, but will be fixed more thoroughly in a follow-up PR
Response Cache unit test has been updated to use new Cache API via TritonCacheManager

Some (potential) follow-up PRs:

[ ] docs updates (response_cache.md, metrics.md, etc.)
[ ] (?) per-model caches, cache config specified in model config.pbtxt as suggested by Iman
[ ] remove copy from cache impl side by instead adding some callback/signal to hold onto a buffer until Triton has copied it to response output

may profile with nsys to see the specific impact here

TODO Items

[x] serialize/deserialize responses
[x] simple test that responses are cached correctly with example client
[x] Remove or update --response-cache-byte-size > 0 logic for enabling cache

this can be controlled by cache/cache_config

[x] pass cache_config to TritonCache
[x] pass cache_dir to TritonCache
[x] re-enable minimal unit test
[x] minimally fix cache stats for perf analyzer (follow up PR for thorough fixes)
[x] Check memory leaks
[x] check copyrights
[x] Update cache unit test (follow up test PR: #144)
[ ] Add API descriptions/docs (TBD on some copy/ownership changes)

[ ] Performance benchmarking

[ ] Optimize copies / remove unnecessary copies
[ ] Consider Exists API, may be tricky concurrency wise (exists when checking but not when looking up), or hurt performance (add concurrency around Exists + Insert/Lookup)
[ ] Nsight compare
[ ] Verify no C++17 related bottlenecks

[ ] Check stats/metrics (follow up metric PR)

[ ] Check L0_perf_analyzer_report
[x] Update cache miss stats through model rather than request due to request lifetime issues (released by backend before callback)

[ ] Update response_cache.md doc (follow up doc PR)

Corresponding server changes: https://github.com/triton-inference-server/server/pull/5119

@GuanLuo @Tabrizian let me know if you have any additional high-level feedback here. I will be merging into an rmccormick-cache-main side branch before final PR into main.
To try to keep the logical changes grouped and smaller, I will have follow-up PRs for:

protobuf config file (DLIS-4469)
copy optimization (DLIS-4471)
metrics cleanup (DLIS-4372)


#1226: Updated VTP steps numbers

I closing this PR in favor of other change: import message types from VTP library


Clearer colourmap / labels when showing task order in visualize

After a helpful suggestion from @TomAugspurger, I'm trying to examine the static task order of my DAG. This is harder than it should be just because

The current way of applying the colour map means sequential tasks have the most similar colours
There is no key to tell me which colour is first
I don't know of any other way to access this information
This definitely isn't colourblind-friendly (I'm not colourblind, but ~8% of men are)

My looks like this, which I'm finding hard to parse - for example I'm finding hard to tell if 30 occurs before 37.

Q's:

Is there another way for me to easily find out the static task order?
Can we add an (optional) key to help me differentiate?
Is there a html version of this graph that can tell me this info with a mouseover?

Thanks

Is there another way for me to easily find out the static task order?

dask.order.order will give you the ordering as a dictionary (I think0.
FYI, cmap="autumn", node_attr={"penwidth": "4"}) helps a bit with the coloring.

Is there a html version of this graph that can tell me this info with a mouseover?

I don't think so. That would be handy.

Is there a html version of this graph that can tell me this info with a mouseover?

This would be a good thing to do as part of #7301. A nicer, more web-friendly graph viz would also be great for #9053 .


ML2 TA feedback

Hi Folks,
Good job on the dashboard! This is really useful, everyone would enjoy a reasonably priced good wine.
I couldn't find a link to Heroku so I deducted marks for it, let me know if I missed it.
Few comments:

Add the pink(ish) background as your sketch if you can, it was nice.
add units for "price".
In addition to country, I'd like to be able to filter based on wine variety.

Cheers,
Afshin

Thanks for your comments. To address those comments, we will release the following change in Milestone4:

We stick to the white background, but we unify the color to red.
Add "80-100 points"
Add wine variety filter.

Thank you Afshin for your feedback. We appreciate all the suggestions and have been working on implementing them!
Just to add to Huan's response, we've also added dollar signs units for the price as you've suggested.


enhance accessibility by ensuring welcome screen Contrast meets required standards

Description
This PR is important to ensure napari maintains it's accessibility across all individuals and all platforms.
Here is my attempt to enhance the accessibility of the welcome screen on napari, and it was part of my work during the pydata global 2020 sprint session for napari
Type of change

[x] Bug-fix (non-breaking change which fixes an issue)

References
using https://webaim.org/resources/contrastchecker/ to see that the contrast passed minimum requirements for accessibility fix for issue #(1794)
How has this been tested?

[x] example: running a visual test on my mac and viewing the results on https://webaim.org/resources/contrastchecker/ was able to reach contrast ratio 5.03

[ ] example: someone should try it on windows

Final checklist:

[x] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works

@sofroniewn this looks good to me! Shall we merge?

Very nice @ddawsari!
I've cleaned this up a little more, and hopefully removed the need for the mac special case logic by using the primary color (which was an already lightened version of the color we were creating) and not changing the opacity which was a bit puzzling to have from last time.
Here's the current behaviour on my mac for our two themes.

For the "dark" theme the rgb values from a screenshot are [89, 99, 109] which leads to this accessibility profile

which passes for the "large text" case we're in now.
Maybe @GenevieveBuckley can take a quick look at this too, and then we can merge.
Thanks again @ddawsari for working on this during the sprint!!

I don't know how to switch to light mode, is this documented?

From the menubar, view then toggle theme.
We should add a line about that here https://napari.org/tutorials/fundamentals/viewer#changing-viewer-theme

Our documentation also doesn't have a search bar either, it seems.

Something to put on our feature for the website reorganization

I don't know how to switch to light mode, is this documented?

From the menubar, view then toggle theme.

Oops, didn't look carefully enough! Light mode on Windows looks good too.

We should add a line about that here napari.org/tutorials/fundamentals/viewer#changing-viewer-theme

Yes, this is a good idea.


chore: suppress warning log for tests

Problem
We currently log that websocket connection failures might be prominent during a node's lifecycle. This was added to inform users that this is normal, however the logs are being spammed for every node creation in our test suite & CI making the reports hard impossible to read & their size large.
Solution
Suppress the warning log only for test suites.
Notes

removes the additional hide flag that was introduced in https://github.com/waku-org/js-waku/pull/1733

removes the additional hide flag that was introduced in chore: add info message with expected WebSocket connection failures  #1733

why?

strange change slipped in

it is intended to be part of the same PR.
rationale is: we would only hide the info log for CI/testing (since it creates spam thus decreasing readability), and for all deployed applications the info log would show.  for any other case, i would assume we should log the warning.
Kept it for now to decrease diff, but not sure I see utility for it: 7e4bf303d82e1548efaf5095b5df6d0fb4e868ae
Please let me know if you think otherwise
cc @weboko who added this


How to enable gzip compression?

Closing. Please provide description next time. Below is probably the article you're looking for.
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/applications-sourcebundle.html


feat: Add epochs to existing orchestrator

Reverts the revert.
Original description
Adds epochs to the current Orchestrator. Splits the ProverState into epoch and block. Snapshots all inputs required for proving a block as early as possible, so we can keep updating trees without having to wait for older block proofs in the epoch.

Docs Preview
Hey there! 👋 You can check your preview at https://66f2c80dd1808a19acdfa03d--aztec-docs-dev.netlify.app

Closing in favor of new PR to unstuck CI


fixed typo of missing commas in json for example

Missing commas in the example for copy/pasters (like myself).

thanks for the correction @oaoleif


Daother 8066

Summary of Changes:
https://rcsbpdb.atlassian.net/browse/DAOTHER-xxxx

new file rcsb/app/file/uploadPartial.py at endpoint /file-v2/uploadPartial
new file rcsb/app/file/KvSqlite.py
updated rcsb/app/file/IoUtils.py, rcsb/app/file/main.py
testClientScript has new sliced upload, does not yet have concurrent sliced uploads
updated requirements.txt
have not built unit tests yet

Screenshot of Changes (or test)
(where applicable)
Checklist:

[ ] I followed the code style guidelines
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have tested the code / Added unit test(s)

FYI @j-s-135, I just merged the changes I made for DAOTHER-8067 into this branch and resolved the conflicts, so you'll probably want to pull the latest changes before committing anything new to avoid running into any new conflicts.

Hi @j-s-135, it looks like the publishing to PyPI still failed due to a new issue:
Removing intermediate container 59c770cba449
 ---> 1afc3ea5867f
Step 15/31 : COPY ./rcsb /app/rcsb
 ---> 49adc9271416
Step 16/31 : COPY ./deploy/gunicorn_conf.py /app/gunicorn_conf.py
 ---> bc285b6dfe8a
Step 17/31 : COPY ./deploy/launch.sh /app/launch.sh
 ---> 7dfd8bac66c8
Step 18/31 : RUN chmod +x /app/launch.sh
 ---> Running in e4818b767216
Removing intermediate container e4818b767216
 ---> b265a1ac35ed
Step 19/31 : COPY ./deploy/entryPoint.sh /app/entryPoint.sh
 ---> 939283b92196
Step 20/31 : RUN chmod +x /app/entryPoint.sh
 ---> Running in d2b7a1ab1146
Removing intermediate container d2b7a1ab1146
 ---> b76cd137790b
Step 21/31 : COPY ./rcsb/app/tests-file/data/example-data.cif    /app/rcsb/app/tests-file/data/example-data.cif
 ---> 466a9665f6b5
Step 22/31 : COPY ./rcsb/app/tests-file/data/testFile.dat /app/rcsb/app/tests-file/data/testFile.dat
COPY failed: file not found in build context or excluded by .dockerignore: stat rcsb/app/tests-file/data/testFile.dat: file does not exist
##[error]Bash exited with code '1'.
Finishing: Production build script

Can you have a look at this and see if you can re-open this ticket and push the needed fixes? Apparently it's having trouble copying/finding that file (rcsb/app/tests-file/data/testFile.dat). Unfortunately that test doesn't run until it gets published, so there isn't an easy way to troubleshoot this before merging. But hopefully it's a pretty obvious fix.
Also, just wanted to check if there was any code that should be added back in (but left commented out), so that we don't lose track of where it went? Or did you already keep all that code in here?


polygon tool: double-click too sensitive

One of the most used tools is probably the polygon drawer. However, there are some practical nuisances here IMO:

there is no way to "undo" the last vertex
there is no way to cancel the final closure
the time and distance for the double click rule are way too sensitive

(In effect, I often have to redo long polgons simply because LAREX thought the next vertex was the final one.)

I agree, the default values time / distance delta values for double clicks were a bit funky, I lowered them significantly and users are now able to set these values themselves starting with a0e6e69.


Confirm navigating away or refreshing

Expected Behavior
Pop up a dialog to confirm navigating away or refreshing the page to prevent losing unsaved jscad code.
Actual Behavior
No confirm dialog, jscad code is lost.
Steps to Reproduce the Problem

Open openjscad page
Work on model
Accidentally press F6 (highlights browser address bar)
Press F5
Browser refreshes, model is lost.

Specifications

Version: 1.9.0
Platform: Windows 10 / Chrome browser
Environment: Browser

We are at the mercy of the browsers. Each has a different set of ‘command’ keystrokes, behavior, etc. I’m not sure how much can prevented but we can try.

Let’s try adding this to V2 WEB UI.

@chingy1788 thanks.
Your suggestions have been integrated into V2 JSCAD via #687
Please keep those comments coming!


⚠ ClamAV has degraded performance

In 6532439, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 181 ms

Resolved: ClamAV performance has improved in 4b754c2.


Internal Server Error

Good evening, when I go to first log into the server using username: admin and password: password, I get an error saying 'Error 500 Internal Server Error'. I have a clean install of Python Version 3.8.9 as per the video and instructions.
Any help would be greatly appreciated.

@highhopes1 Is the error in the browser or the cmd console? I can't see the screenshot for some reason so can't help you much.

The issue is within the browser after the server starts and the login screen appears.

@highhopes1 You will have to look at the console errors and try to debug. There is most likely an error with your MainConfig.py, config.py or FTSConfig.yaml if you are using the .yaml file.
Also when running for the first time the FreeTAKServer.controllers.service will ask if you want to use the .yaml file. Type in No otherwise you will need to configure FTSConfig.yaml which I have not setup the app to do automatically.

Amazing  that worked thank you so much.


Allow IPv4 registrations to be disabled

This work extends my IPv6 patches in PR #321.  Once you can register IPv6 addresses, it may be advantageous to not register IPv4 addresses at all.  This patch allows you to do so, via the simple expedient of adding --ipv4=false to your registrator command line.

Same here re: rebase. Sorry!

Same answer re: rebase.  Sorry!

Sokay :)


upgrade dependecies

upgrade dependencies to:
markdown: ^7.1.1
flutter_markdown: ^0.6.18+2

Hey @gxsham can you please solve the merge conflicts before I merge the PR.


[FEATURE] Add support for Data Verfication activity in Automation.

Is your feature request related to a problem? Please describe.
Unable to deploy the Data Verification Activity as part of my Automation.
Describe the solution you'd like
Be able to deploy the Data Verification Activity as part of my Automation deployment routine.
Describe alternatives you've considered
Manually creating and updating the activity through Automation Studio UI, or writing myself REST API requests.
Additional context
Tested myself and found out that there is an REST endpoint which allows to READ/CREATE/MODIFY the Data Verification Activities. More details below.
Endpoint: /automation/v1/dataverifications/{id}
Supported Methods:  GET/POST/PATCH
Examples:
GET: /automation/v1/dataverifications/{dataVerificationDefinitionId}
Response:
{
    dataVerificationDefinitionId: 'dataVerificationDefinitionId',
    targetObjectId: 'dataExtensionObjectId',
    verificationType: 'IsEqualTo',
    value1: 0,
    value2: 0,
    shouldStopOnFailure: true,
    shouldEmailOnFailure: false,
    notificationEmailAddress: '',
    notificationEmailMessage: '',
    createdBy: userId
}

POST: /automation/v1/dataverifications/
Request:
{
  "destinationName": "Name",
  "deDestinationName": "DE Name",
  "targetObjectId": "DE Object ID",
  "deTotalRowCount": 0,
  "deFieldCount": 5,
  "deModifiedDate": "2022-04-06T15:54:14Z",
  "deModifiedByName": "Some User",
  "value1": 0,
  "conditionText1": "is",
  "conditionText2": "equal to",
  "notificationEmailAddress": "",
  "verificationType": "IsEqualTo",
  "shouldStopOnFailure": 1,
  "notificationEmailMessage": "",
  "shouldEmailOnFailure": 0
}

Response: Same as in GET Request
PATCH: /automation/v1/dataverifications/{dataVerificationDefinitionId}
Request:
{
  "dataVerificationDefinitionId": "dataVerificationDefinitionId",
  "targetObjectId": "dataExtensionObjectId",
  "verificationType": "IsEqualTo",
  "value1": 0,
  "value2": 0,
  "shouldStopOnFailure": true,
  "shouldEmailOnFailure": false,
  "notificationEmailAddress": "",
  "notificationEmailMessage": "",
  "createdBy": userId
}

Response: Same as in GET and POST

@JoernBerkefeld  - no generic GET collection exists for this, so would need building into automation directly, not as a separete type. We could just nest to json to avoid issues, but would need to be clever about caching etc. thoughts?

copying info in from other ticket:
https://help.salesforce.com/articleView?id=mc_as_automation_studio_activities_reference.htm&type=5

looks like a bigger task for 4.1?
I do find it interesting and I sure like the groundwork done by @bgacek


Apply fixes from StyleCI

This pull request applies code style fixes from an analysis carried out by StyleCI.

For more information, click here.

A new inspection was created.

The inspection completed: 2 Issues, 0 Patches


[UPGRADE] Migrate Updates from Internal Codebase

This PR:

Deprecates Leap.Unity.Pose for UnityEngine.Pose
Adds new Utils, QueryOperatorExtensions, and Infixes
Adds StringPathUtils.cs - A Utility for working with String Paths

This is part of the general compatibility movement for internal codebases.

Good catches; I'm not sure why I thought I couldn't do an Infix Extension Method earlier...


Remove draft versions 32 and 34 from README

https://github.com/lucas-clemente/quic-go/pull/3217 removed support for draft versions 32 and 34.

@googlebot I signed it!


zoom handler not work

hi
why _zoomConfig handler not work
onZoom = (data) =>console.info(zoom ${data});
const graphProps = {
...
zoomed: this.onZoom,
// or
// zoomConfig: this.onZoom,
};

Hello @MohandesaliRahnema thanks for reporting, but please use the issues template (feature/bug) so that we have a more contextualized overview on what exactly your problem or use case is. Thanks.
Regarding what you posted, there's no such method exposed in the official react-d3-graph API. Please submit a feature request if you would like to have that behavior.
Extra tip: currently that could be achieved with a monkey patch approach, but that's a quite ugly solution to put in place.


Issue in WinML Demo

Hi Team,
I got an issue as a screenshot as below.

Hi Team,
I got an issue as a screenshot as below.

Hello. I can think of two things: (1) the path is long. In the demo scripts, I ask that you copy the project to your C: drive root. and (2) Did reload the dependencies and the nuget packages?

@nitah-kelsy After I copy to the C: drive root. The problems solved. Thank you so much.