Always missing one script :(

It seems no matter how up to date I am always missing one file you plan to release but didn't comment out, maybe you intended to leave it so people understand what is coming soon? For myself it makes me feel as-though my package is not complete.
The two files scheduled_tasks/get_crypto_transactions.py and scheduled_tasks/get_ipo_calendar.py are included in your .gitignore file. Causing issues when using scheduled_tasks.
I must comment out line 33, 105, 210, 211 inside tasks_to_run.py.
Typically I wouldn't have an issue with this but the discover page and all related get_ipo_calandar files seem to be included and/or have references to this missing file(s). I have removed the lines that caused errors but perhaps uploading this even if its less stable would be helpful.
files that are referencing get_ipo_calendar.py
static/javascript/discover/ipo.js
templates/discover/ipo_calendar.html
ViewStocks/views.py
templates/discover/short_interest.html
ViewStocks/urls.py
If you didnt mean to forget this file where are you pulling information from so I may recreate this myself?

Added them to the latest commit. After you run get_ipo_calendar.py, view it in /ipo_calendar. get_crypto_transactions.py currently only gets transactions from whalealert.io


Replace separate gateway endpoint with RDF-based protocol discovery

Resolves #24
This entirely removes the Gateway endpoint, replacing it with an RDF-based resource that can be used by clients to find the appropriate subscription API, based on the features and protocols supported by the client.
For example, the following RDF structure could replace the Gateway endpoint:
@prefix solid: <http://www.w3.org/ns/solid/terms#> .
@prefix notify: <http://www.w3.org/ns/solid/notifications#> .

<>
    a solid:StorageMetadata ;
    notify:hasWebSocketNotification <#websocketNotification> ;
    notify:hasWebHookNotification <#webhookNotification> ;
    notify:hasLinkedDataNotification <https://ldn.example/Metadata> .
<#websocketNotification>
    a notify:WebSocketSubscription2021 ;
    notify:endpoint <https://websocket.example/subscription> ;
    notify:features notify:state, notify:rate, notify:expiration .
<#webhookNotification>
    a notify:WebHookSubscription2021 ;
    notify:endpoint <https://webhook.example/subscription> ;
    notify:features notify:rate, notify:expiration, notify:webookAuth .

When is the RDF format to be decided?
For instance, rather than notify:hasWebSocketNotification, I wonder if we want notify:hasNotificationChannel [ a notify:WebSocket ] or similar.

The format is entirely open for discussion.
My initial thought was along the lines of notify:hasNotificationChannel, but I chose the protocol-specific properties purely from a performance consideration. If a client needs to follow links to many different remote resources, I worried that it would be too much of a burden on clients.
For instance, if the Storage Metadata resource contains the following:
<>
    a solid:StorageMetadata ;
    notify:hasNotificationChannel <https://foo.example/Metadata>, <https://bar.example/Metadata>, <https://baz.example/Metadata> .

A client would need to dereference all of the remote resources in order to determine which one is relevant. But the client may only be interested in WebSockets and those remote resources may be for WebHooks or LDN.
From an RDF data modeling perspective, I prefer the notify:hasNotificationChannel structure, but I don't really like that from an app development perspective.

A client would need to dereference all of the remote resources in order to determine which one is relevant.

True. To mitigate this, we should mandate certain information (such as typing) to be present in the shape.

To mitigate this, we should mandate certain information (such as typing) to be present in the shape.

I like that suggestion a lot. I will incorporate it into this PR

@RubenVerborgh what do you think of the use of rdf:value in structured bnodes such as:
<>
    a solid:StorageMetadata ;
    notify:hasNotificationChannel [
      a notify:WebSocketSubscription2021 ;
      rdf:value <https://foo.example/Metadata> ]
.

Or would you prefer an offset description like so:
<>
    a solid:StorageMetadata ;
    notify:hasNotificationChannel <https://foo.example/Metadata>
.
<https://foo.example/Metadata>
    a notify:WebSocketSubscription2021
.

I'm not a big fan to be honest, but I see the problem.
I wonder if we want something like notify:accessUrl "https://foo.example/Metadata" (the literal is deliberate). Would also enable authenticated URLs.

How about this: we start by keeping it simple.
IOW, all discovery metadata resides in the Storage metadata resource like this:
<>
    a solid:StorageMetadata ;
    notify:hasNotificationChannel <#websocketNotification>
.
<#websocketNotification>
    a notify:WebSocketSubscription2021 ;
    notify:endpoint <https://websocket.example/subscription> ;
    notify:features notify:state, notify:rate, notify:expiration
.

This could be wrapped in a bnode as in your example above, if desired, but there would be no defined support for externally-defined metadata. So <> notify:hasNotificationChannel <https://foo.example/Metadata> would not be explicitly described at all.

That's great, blank node definitely not needed.
I'd just refer to #30 so we don't use "endpoint" 🙂

Thanks, @RubenVerborgh. FWIW, I cringed every time I used endpoint here, but I wanted to avoid combining this change with #30. But yes, I really want to remove the use of "endpoint".

Allow me to advocate a change of perspective, which may or may not be relevant...
There are a couple of long-lived abstractions, one is that we prefer self-describing resources, so we tend to prefer the URI to match the target URL, or differ only in a fragment identifier. The other is essentially an OOP-inspired object or tree that is usually anonymous, i.e. the subject isn't really important at all, all important information is in property and object position. But neither of these are absolutes, and in an RDF, the subject is actually important, the subject is what we're talking about.
It seems to me, and I admit to not have looked very carefully, that what we're talking about here is the URI that should be subscribed to. Making it RDFy, it should be the subject, e.g.
<>
    a solid:StorageMetadata ;
    notify:hasNotificationChannel <https://websocket.example/subscription>
.
<https://websocket.example/subscription>
    a notify:WebSocketSubscription2021 ;
    notify:features notify:state, notify:rate, notify:expiration
.

In general, I'd like to see patterns like this more... I hope it fits. :-)

I agree on describing https://websocket.example/subscription , but then for it to be fully self-describing, it should be an RDF document and respond to GET, HEAD. Exposing its description in another resource is not what's generally considered as self-describing.

I agree on describing https://websocket.example/subscription , but then for it to be fully self-describing, it should be an RDF document and respond to GET, HEAD.

If it can do that, great.

Exposing its description in another resource is not what's generally considered as self-describing.

and if it can't, I wouldn't take a dogmatic approach to self-description, and still do it even though it wouldn't be self-describing. It would be a better knowledge graph, and when there's tension between self-description and knowledge graphs, then I would rather side with the knowledge graph, because, if you don't, what use is RDF?

I'm not aware of a strong reason as to why the subscription resource (endpoint) can't or shouldn't respond to GET, HEAD.
As per Solid Protocol #server-post-target-not-found :

When a POST method request targets a resource without an existing representation, the server MUST respond with the 404 status code.

Moreover, the request semantics of POST targeting a non-container (subscription resource) is currently undefined. (We have considerations/WIP on RDF Merge... as you know.)
Hence, I propose that the Notification Protocol has a requirement for GET, HEAD requests targeting a subscription resource in that the server MUST respond with 200 or 405. I suggest 200. The metadata as described in this PR should be available from the subscription resource in addition to the storage metadata resource.

I suggest additional considerations mostly for the record but preferably followed up in a separate issue/PR, if need be, and definitely not block this PR!

Use the storage resource instead of storage metadata resource to describe storage's notification channels. (Ultimately depends on issue 355.)

(I love and hate this idea.) Change the subscription resource from a non-container to a container. It will work with existing behaviour on POST to container in Solid Protocol. This will open up the possibility for a server to track/record subscription requests (as notifications) in and of itself. The immediate concern with subscription resource as a container is that if the description is to be readable (200 to GET, HEAD as mentioned above), then the container would reveal containment statements - a "feature" we definitely don't want as is. To get around this, essentially there needs to be a requirement that would, if at all, only allow the owner of the storage to have access to these subscription requests. Alternatively, a requirement that would allow servers to omit containment statements. On the other hand, if GET, HEAD to subscription resource is a 405, we don't have that problem.


Improvement - team selection

improvement suggestion for team selection:

choose per player (could include positon: defense & offense),
filter chosen players from player list  (4 players to pick, when you have chosen player 1, the chosen player is filtered out of the list of player 2-4, etc. etc.)

Axure sketch

Something like this perhaps

updated sketch, you can now:

go forward when you've already selected  a player without tapping that player again
record who made the goal

pending improvements:

button placement for goal registration


Remove support for IngressRoute and Routes

As decided in #106 I hereby remove this Helm Chart's support for IngressRoute and Route objects altogether.
We have decided that as these Ingress Controllers (Traefik and Openshift) also support standard Ingress objects nowadays, it is no longer necessary to support those CRDs in our Helm Chart.
Additionally to that, we have another, soon to be merged PR #121 which implements the possibility to render arbitrary Manifests together with this Chart.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped

@aeciopires Haven't you added the creation of Helm-Docs to Github Actions automatic CI/CD? I am asking because it's still noted here as a requirement to create a pull request. If so, could you please change this documentation, accordingly? Thanks

Hi @fibbs!
Thanks for your contributition.
The publishing of the helm chart is associated with the manually created tag. Using this approach, I can accumulate many PRs and publish all the changes together. That is why I did not add helm docs to the pipeline to avoid conflicts. I had a lot of problems with this last year.
So, during the process of publishing a new release, I evaluate all the changes from the PRs that I will publish, choose the appropriate version number and then publish them in one package...
The explanation for this is that last year I was very busy at work, so several PRs accumulated throughout the year and I published them all in one batch release.
Another reason is that some people who opened the PR were not responding quickly when I had free time (which is normal because everyone's schedule is asynchronous even depending on their interest and free time).

Hi @fibbs!
What do you think about using this PR to also remove the values and manifests related to Karpenter?
Looking at your PR and contribution of @sinux-l5d in #121, now it is flexible for anyone to add whatever manifest they want to the helm chart according to their needs without us having to worry about approving it for each release.
I think that the next release of chart is a break change with this values. I think that 7.0.0 version if the new release is more appropriated. Do you agree?

The publishing of the helm chart is associated with the manually created tag. Using this approach, I can accumulate many PRs and publish all the changes together. That is why I did not add helm docs to the pipeline to avoid conflicts. I had a lot of problems with this last year.
So, during the process of publishing a new release, I evaluate all the changes from the PRs that I will publish, choose the appropriate version number and then publish them in one package...
The explanation for this is that last year I was very busy at work, so several PRs accumulated throughout the year and I published them all in one batch release.

I was actually thinking about exactly the same: not raising versions at PRs anymore and to do that "centrally" by one, you or maybe some day me as well :-) So, we should change the documentation of how to contribute anyway and not mention the helm-docs creation nor the version updating, right?

I agree @fibbs. Can you adjust the documentation in this PR and remove any reference related to Karpenter in values and manifests?
Other point, can you change the READ.me.gotmpl file explaning the break change related to ingressRoute, Route and Karpenter because the new feature is implemented in #121?


Branch 142576906

Jenkins, test this please

Jenkins, test this please

Jenkins, test this please

@mrry fyi, I had to move saved_model deps from tf_cc_ops.cmake to tf_core_cpu.cmake to fix the windows cmake build. I added saved_model support to the C API in this set of changes, and it's closer to core anyway despite being under cc/.

Maybe tf.norm should use tf.norm(m, ord='fro') instead of tf.norm(m, order='fro') for consistency with numpy? @martinwicke

@aselle See the tf.norm comment above ^

I am ok with order instead of ord, because frankly, numpy's name there is worse. Incompatibility with keyword arguments is less pressing, since those basically will not cause as much confusion as positional argument mismatches (we do match them in some cases, like our change on axis).

@yaroslavvb fyi, it's being renamed to ord and should show up during the next sync.


fix Kafka flaky test

Trying to solve #103, I am very doubtful that KafakConsumer will not be consumed evenly from two partitions.

After four times CI checks(see: https://github.com/apache/incubator-pekko-projection/actions/runs/7831923269), this kind of test has been successfully passed, and we should be able to assume that this kind of flaky has been fixed.

@raboof Could you please do a code review? Thanks.

TBH I'm not convinced this change fixes the root cause of the instability: because of the assertion records.count(_.partition() == tp0.partition()) shouldBe 5 AFAICS it should be guaranteed that tp0TestCount would always be 5, so this change should not have an effect other than timing differences - or did I miss something?

The producer produces a total of 20 elements, and each partition has 10 evenly.
Then Sink consumes 10 elements from two partitions. There is no assertion that each partition consumes 5 evenly. If it is not consumed evenly, it will lead to problems with subsequent assertions, because partition 0 may consume 6 records in the previous step.
This PR does not force the assertion that Sink consumes evenly from all partitions. If Kafka Consumer is not balanced consume from partitions, I don't think this is the responsibility of this test or should be added a new test to assert.

Would you like to take a look? @raboof
This may not the best solution, but it does reduce flaky.


Conditional files / directories

This is a complement issue for #126. Sometimes I want to create a file only under certain condition.
I propose that the function generate_file() ignores the creation of file if its filename is empty. So, for example, I could template a filename like this :
/{% if cookiecutter.some_var %}{{ cookiecutter.another }}.txt{% endif %}

It seems this logic actually works for directories, but not for files.

I would love this. I hadn't found this ticket so posted it on SO: http://stackoverflow.com/questions/35005098/can-i-make-a-file-optional-based-on-a-variables-value-in-cookiecutter-json/35020626#35020626

Got a use case where I need a __main__.py if there's a console_script entry point in setup.py. Otherwise (pure lib) I don't need such file.

This can be done in post-generate hooks as seen in https://github.com/pydanny/cookiecutter-django/blob/master/hooks/post_gen_project.py#L163-L165. This makes this issue more an education issue then a technical solution. This is good because making logic work in directory/file names on Windows is impossible (and we support Windows).
Therefore, I believe this is better done as a recipe described in the advanced_usage.rst document.


[NPM] traffic break if pod IP is deallocated from previous pod

Is this an ISSUE or FEATURE REQUEST? (choose one):
ISSUE
Which release version?:
azure-npm:v1.1.0
Which component (CNI/IPAM/CNM/CNS):
NPM
Which Operating System (Linux/Windows):
Linux
For Linux: Include Distro and kernel version using "uname -a"
Linux aks-nodepool1-85368712-vmss000000 4.15.0-1071-azure #76-Ubuntu SMP Wed Feb 12 03:02:44 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Which Orchestrator and version (e.g. Kubernetes, Docker)
Kubernetes
What happened:
This test is typically Kubernetes networkpolicy e2e test
I have a server with 80 and 81 ports exposed outside,  and two egress policy applied on pods with label type=client .
two networkpolicies, one is to deny all ingress traffic to pods in namespace e2e, and the other one allows traffic from pods with app=client to pod app=server in namespace e2e
Before this test, we also have other network policy e2e tests just finished.
The client won't reach the server pod service
How to test:
kubectl run --rm -it --image busybox  -l app=client -n e2e client wget svc-access-server.e2e:80
What you expected to happen:
Background:
When delete a pod, gracefully by default, two pod delete event will be sent to the pod event watchers, like Azure NPM, and Kubelet, etc.
One event happens when the first attempt to delete the pod comes, kubelet will stop the container gracefully with SIGTERM by docker, as our server pod container cannot handle SIGTERM, docker will send SIGKILL to the container process after grace period, 30s. Thus, Kubelet get the containerdied notification, it talks to apiserver to delete the pod by force, which generate second pod delete event from apiserver.
As we have also other network policy e2e tests running in a sequence, chances are that the IP of server pod, say pod1, used in this test is deallocated from pod, say pod2, of a previous test.  pod1 and pod2 use the same pod labels.
When the pod1 creation event comes in the middle of the two pod deletion events, the ipset determined by the pod label will remove the ip address. Unfortunately, this cannot be recovered automatically. Also I apply the same scenarios in Calico, and the test passed.

Please feel free to reach out to me if my words is confusing.
How to reproduce it (as minimally and precisely as possible):
apiVersion: v1
kind: Pod
metadata:
  labels:
    app: server
  name: access-server
  namespace: e2e
spec:
  containers:
  - args:
    - python -m SimpleHTTPServer 80
    command:
    - sh
    - -c
    image: python:2.7.11-alpine
    name: pod-container-80
    ports:
    - containerPort: 80
      name: serve-80
      protocol: TCP
  - args:
    - python -m SimpleHTTPServer 81
    command:
    - sh
    - -c
    image: python:2.7.11-alpine
    name: pod-container-81
    ports:
    - containerPort: 81
      name: serve-81
      protocol: TCP

---
apiVersion: v1
kind: Service
metadata:
  name: svc-access-server
  namespace: e2e
spec:
  ports:
  - name: serve-80
    port: 80
    protocol: TCP
    targetPort: 80
  - name: serve-81
    port: 81
    protocol: TCP
    targetPort: 81
  selector:
    app: server
---

// network policy denies all ingress traffic to pods in namespace e2e by default
apiVersion: extensions/v1beta1
kind: NetworkPolicy
metadata:
  name: deny-all
  namespace: e2e
spec:
  podSelector: {}
  policyTypes:
  - Ingress

---
// network policy allows traffic from pods with `app=client` to pod `app=server` in namespace e2e
apiVersion: extensions/v1beta1
kind: NetworkPolicy
metadata:
  name: allow-from-client-pod-selector
  namespace: e2e
spec:
  ingress:
  - from:
    - podSelector:
        matchLabels:
          app: client
  podSelector:
    matchLabels:
      app: server
  policyTypes:
  - Ingress

Anything else we need to know:

hi @mainred , are you saying that

pod1 (update call -> to succeeded phase) triggers delete from ipset
pod2 (add call) triggers add to ipset
pod1 (delete call) triggers delete from ipset

so in the end, the ip doesn't exist in set because it's been added and deleted due to same labels and ip used?

hi @mainred , are you saying that

pod1 (update call -> to succeeded phase) triggers delete from ipset
pod2 (add call) triggers add to ipset
pod1 (delete call) triggers delete from ipset

so in the end, the ip doesn't exist in set because it's been added and deleted due to same labels and ip used?

Step 1 has a delete call actually, hope the following log is helpful. See first Line and second to last one.
May 15 06:44:05 aks-nodepool1-39481035-vmss000000 kubelet[3891]: I0515 06:44:05.515802    3891 kubelet.go:1904] SyncLoop (DELETE, "api"): "client_default(2a6ffd06-eff1-4254-b87d-d56bec2ed5fd)"
May 15 06:44:05 aks-nodepool1-39481035-vmss000000 kubelet[3891]: I0515 06:44:05.516096    3891 kuberuntime_container.go:581] Killing container "docker://a0ed9e382327ca09d82997b739034875290dcea831889af0545dcb53673e0dc7" with 30 second grace period
May 15 06:44:36 aks-nodepool1-39481035-vmss000000 kubelet[3891]: I0515 06:44:36.911537    3891 kubelet.go:1933] SyncLoop (PLEG): "client_default(2a6ffd06-eff1-4254-b87d-d56bec2ed5fd)", event: &pleg.PodLifecycleEvent{ID:"2a6ffd06-eff1-4254-b87d-d56bec2ed5fd", Type:"ContainerDied", Data:"a0ed9e382327ca09d82997b739034875290dcea831889af0545dcb53673e0dc7"}
May 15 06:44:36 aks-nodepool1-39481035-vmss000000 kubelet[3891]: I0515 06:44:36.911707    3891 kubelet.go:1933] SyncLoop (PLEG): "client_default(2a6ffd06-eff1-4254-b87d-d56bec2ed5fd)", event: &pleg.PodLifecycleEvent{ID:"2a6ffd06-eff1-4254-b87d-d56bec2ed5fd", Type:"ContainerDied", Data:"006a5c5f72c30ff70937d5f22364cb149d83dbab5522177f4f41c41bdd65e56e"}
May 15 06:44:36 aks-nodepool1-39481035-vmss000000 kubelet[3891]: E0515 06:44:36.949744    3891 remote_runtime.go:295] ContainerStatus "a0ed9e382327ca09d82997b739034875290dcea831889af0545dcb53673e0dc7" from runtime service failed: rpc error: code = Unknown desc = Error: No such container: a0ed9e382327ca09d82997b739034875290dcea831889af0545dcb53673e0dc7
May 15 06:44:37 aks-nodepool1-39481035-vmss000000 kubelet[3891]: I0515 06:44:37.086880    3891 reconciler.go:177] operationExecutor.UnmountVolume started for volume "default-token-gqt2n" (UniqueName: "kubernetes.io/secret/2a6ffd06-eff1-4254-b87d-d56bec2ed5fd-default-token-gqt2n") pod "2a6ffd06-eff1-4254-b87d-d56bec2ed5fd" (UID: "2a6ffd06-eff1-4254-b87d-d56bec2ed5fd")
May 15 06:44:37 aks-nodepool1-39481035-vmss000000 kubelet[3891]: I0515 06:44:37.105562    3891 operation_generator.go:860] UnmountVolume.TearDown succeeded for volume "kubernetes.io/secret/2a6ffd06-eff1-4254-b87d-d56bec2ed5fd-default-token-gqt2n" (OuterVolumeSpecName: "default-token-gqt2n") pod "2a6ffd06-eff1-4254-b87d-d56bec2ed5fd" (UID: "2a6ffd06-eff1-4254-b87d-d56bec2ed5fd"). InnerVolumeSpecName "default-token-gqt2n". PluginName "kubernetes.io/secret", VolumeGidValue ""
May 15 06:44:37 aks-nodepool1-39481035-vmss000000 kubelet[3891]: I0515 06:44:37.187129    3891 reconciler.go:297] Volume detached for volume "default-token-gqt2n" (UniqueName: "kubernetes.io/secret/2a6ffd06-eff1-4254-b87d-d56bec2ed5fd-default-token-gqt2n") on node "aks-nodepool1-39481035-vmss000000" DevicePath ""
May 15 06:44:40 aks-nodepool1-39481035-vmss000000 kubelet[3891]: I0515 06:44:40.297690    3891 kubelet.go:1904] SyncLoop (DELETE, "api"): "client_default(2a6ffd06-eff1-4254-b87d-d56bec2ed5fd)"
May 15 06:44:40 aks-nodepool1-39481035-vmss000000 kubelet[3891]: I0515 06:44:40.304962    3891 kubelet.go:1898] SyncLoop (REMOVE, "api"): "client_default(2a6ffd06-eff1-4254-b87d-d56bec2ed5fd)"


Use the shell less to avoid any shell metacharacter shenanigans

In general, shelling out is relatively error-prone given that one must remember to escape/quote shell metacharacters all the time, including spaces in filenames. For these curl and tar commands, there's no need to be using the shell in the first place, since no shell features are being used. So this switches them to use Open3.popen3 with an array argument instead (which shouldn't invoke the shell).
Also, the old code used %p for some shell escaping, even though String#inspect is not intended to be used for that purpose.
Since https://github.com/travis-ci/travis-ci/issues/5092 involves Cacher, I'm looking for possible bugs in Cacher.

@BanzaiMan Ping

Sorry for the delay. I like the idea, but there may be some issues.


Update Azure Getting Started tutorial (both scenario and provider)

To align with updating tutorials and other content to support the Azure native provider, we should update the Azure Getting Started tutorial in two ways:

Change the basic scenario to create a static website, which aligns with the AWS and Google Cloud versions.
Change the provider to the Azure native provider in all text and code blocks.

Issue fixed in #5351.


Discord does not work with Windows Focus Assist when installing through Scoop.

Bug Report
Package Name: discord
Current Behaviour
Installing Discord through scoop causes issues with Windows' Focus Assist.

It is not possible to set Discord as a priority app within Focus Assist, as it is not an option.
Also, notifications will appear under the header com.squirrel.Discord.Discord instead of Discord.

I'm unclear if whether or not this is the cause but, when Discord is installed through regular means a folder named "Discord" is created within "%LocalAppData%". When installed through scoop, this folder is not created.
It may also be caused by some registry keys not being set.
Expected Behaviour

When installing Discord through Scoop, it should be possible to assign it a priority within Windows Focus Assist.
Notifications within Focus Assist should properly show "Discord" as origin instead of "com.squirrel.Discord.Discord".

Additional context/output
It may help knowing I'm running an almost freshly installed Windows 10 OS on completely cleaned drives. External causes are unlikely.
I'd be happy to add additional information as requested.
System details
Windows version: 10 Home 21H2 Build 19044.1645
OS architecture: 64bit
PowerShell version:
Major  Minor  Build  Revision
-----  -----  -----  --------
5      1      19041  1645

Scoop Configuration
{
    "lastUpdate":  "2022-04-14T13:38:13.1157201+02:00",
    "SCOOP_REPO":  "https://github.com/ScoopInstaller/Scoop",
    "SCOOP_BRANCH":  "master"
}

I've never used Focus Assist, but does it not allow using user-provided app paths?
Regarding notifications, we extract the Squirrel package instead of running the Squirrel installer, so I'm afraid that display name cannot be changed.

@rashil2000
I'm unsure on whether that is or isn't the reason and Googling it does not really give me more insight.
My assumption is that something within the %LocalAppData% "Discord" folder, which is only created using the regular installer, is the cause.
Either way, neither is a large issue, so if the cause is not already know nor abundantly clear, it may not be worth the time. I definitely don't plan to do research into the inner workings of Windows Focus Assist either. I've made do with just using the installer instead. Just passing my findings along as potential bug and happy to supply additional information if needed.

Scoop's Discord actually has a bunch of other problems - https://github.com/ScoopInstaller/Extras/issues/8051 and https://github.com/ScoopInstaller/Extras/pull/8154 so even I'd personally recommend using its own installer for now.


Specifically, this seems to be triggered when the code contains a variable that does not exist -- rustc will try to make szggestions for names to use, which can trigger loading external crates, which might be what is happening here.

I think this issue belongs to https://github.com/rust-lang/miri-test-libstd. cargo test without Miri fails with same errors in that repository and all other libcore tests passed. It's caused by the miri-test-libstd-specific core_miri_test crate which is effectively another libcore.

Ah I see, thanks. I can't transfer issues there so I'll do that by hand.

Moved to https://github.com/rust-lang/miri-test-libstd/issues/4


The task provider for "composer" tasks unexpectedly provided a task of type "shell"

See https://github.com/microsoft/vscode/issues/97338 and https://github.com/microsoft/vscode/issues/96636

Update: Just ignore the output, the tasks works as expected.


useFetch doesn't use initialData

Describe the bug
I pass option initialData: [], but useFetch returns null.
To Reproduce
Steps to reproduce the behavior:

Create request
Pass request to useFetch and put { initialData: [] as any }
Run useFetch and see that data = null

Expected behavior
I expect that useFetch will pass initialData as data if request is loading.
Additional context
Request:
import client from "../../client";

type ResponseType = { id: number; name: string }[];

export default client.createRequest<ResponseType>()({
    endpoint: "/feeds",
    method: "GET",
});

useFetch:
const { data } = useFetch(
    feedsIndex.setQueryParams({ with_user_feed: withUserFeed ? "1" : "0" }),
    { initialData: [] as any },
);

console.log(data); // null

I got the idea of initialData. It sets not only data, but also other useFetch return data. So I need to use it in following way:
const { data } = useFetch(
    feedsIndex.setQueryParams({ with_user_feed: withUserFeed ? "1" : "0" }),
    { initialData: {
      data: []
    } },
);

console.log(data); // []

And now it works.

@jmas thanks for the issue! You're completely right, the "initialData" is misleading as there is more that can be inserted at initial render.
I will figure out a better approach maybe: initialResponse will work better 👍🏻

Hello, nice! I found that it lack of docs or examples about this option. The actual name confuse because React Query use initialData for storing data values.
initialResponse looks more convenient.
Thanks!


Make a consistent and strict usage of tslint/eslint across bot framework, samples and generators

Is your feature request related to a problem? Please describe.
The usage of linting tools and applied rules is not consistent across the bot framework, generators and samples. It would be helpful from code quality and coding experience perspectives to have one shared approach everywhere.
E.g., the echobot generator enforces using single quotes!
Describe the solution you'd like
Setup some share policy on using linting tools and default rules.
[enhancement]
Related #728

I think if we implement eslint everwhere, this will be a good start. (See #728)
We'll be applying typescript rules to typescript code, so there won't be a 100% match on the linter rules, but we'll at least be using the same tool and broadly the same set of rules.

We've now implemented eslint on the main botbuilder-js project, which incorporates the same ruleset that is applied to the samples.

Upon review of the samples work in progress, I believe this is done!


gh-1144 - changed LimitedSortedSet to LimitedSortedList

Codecov Report

Merging #1146 into develop will increase coverage by 0.06%.
The diff coverage is 56.66%.

@@              Coverage Diff              @@
##             develop    #1146      +/-   ##
=============================================
+ Coverage      65.05%   65.11%   +0.06%
- Complexity      1314     1343      +29
=============================================
  Files            623      623
  Lines          19334    19388      +54
  Branches        2420     2431      +11
=============================================
+ Hits           12577    12624      +47
- Misses          5752     5753       +1
- Partials        1005     1011       +6

Impacted Files
Coverage Δ
Complexity Δ

...chq/gaffer/commonutil/stream/GafferCollectors.java
73.91% <100%> (+10.95%)
4 <1> (ø)
:arrow_down:

...r/store/operation/handler/compare/SortHandler.java
86.66% <100%> (+31.11%)
0 <0> (ø)
:arrow_down:

...affer/commonutil/collection/LimitedSortedList.java
54.12% <54.12%> (ø)
36 <36> (?)

...k/gov/gchq/gaffer/operation/impl/compare/Sort.java
70.83% <66.66%> (-1.39%)
8 <2> (+2)

Continue to review full report at Codecov.

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


Fix an arithmetic overflow on 32-bit

The current test suite fails on 32-bit targets due to an arithmetic overflow,
but it was pretty easy to avoid!

Thanks!


Added 'How to test & run the project' section to description.md

Please, fix the issues and I will merge this PR.

I can't find any issues. Could you give me more details? Thank you!

Check the review.

Please, check the review here https://github.com/UNIZAR-30246-WebEngineering/lab1-git-race/pull/2/files/534226f51adec6cb951025122bb25c1c9f05a389

Sorry, the reviews were unfinished. Now they are visible.

Is it ok now?

Accepted.


Deployment not restoring. Stemcell not found

I'm restoring a BOSH that contains a single deployment with a single VM. The deployment's instance fails to start up, and when I run bosh cck on it the error is:
Task 13 | 04:57:17 | Applying problem resolutions: VM for 'my-little/4e4d8fb3-2cbc-419e-9fac-8ded0b486464 (0)' missing. (missing_vm 1): Recreate VM and wait for processes to start (00:00:00)
                   L Error: CPI error 'Bosh::Clouds::CloudError' with message 'Expected to find stemcell '{{5947a28b-063d-4239-725c-31582cde24dd}}'' in 'create_vm' CPI method

The ID does look the same as from the stemcells list:
$ bosh stemcells
Using environment '<IP_ADDRESS>' as client 'admin'

Name                                         Version  OS             CPI  CID
bosh-warden-boshlite-ubuntu-trusty-go_agent  3541.8*  ubuntu-trusty  -    5947a28b-063d-4239-725c-31582cde24dd

Is there something dodgy with the {{...}} around the stemcell ID? Or any other ideas why the deployment didn't restore ok?
Update: I deleted + redeployed the deployment and got a similar error. It was resolved by running bosh upload-stemcell --fix path/to/stemcell. Can you think why the stemcell records might not have been restored correctly?

@rkoster I'm using BUCC's BBR system - has it correctly restored stemcells for you; or did you need to bosh upload-stemcell --fix first?

That said, if you're just doing bucc down (which as far as I can see is just a bosh delete-env) then the stemcell should hang around in your IaaS, so a restore should just work... Strange.

Ok I think I understand more about what to expect from a BBR restore. I’ll close for now.

@henryaj it was a bosh-lite/bucc-lite so they were missing warden stemcells, which are ephemeral within the previously existing VM


[BUG] Observability / Metrics / Source No index to be selected

Describe the bug
There are no index to be selected at Otel Index selection box on (/app/observability-metrics)
The box appear empty
To Reproduce
Steps to reproduce the behavior:

Go to '/app/observability-metrics#/'
Click on 'Metrics source OpenTelemetry'
Click on Otel Index and on dropdown try to select any possible available index
The list is empty

Expected behavior
Was expected to appear a list of indexes that could be selected
OpenSearch Version
Opensearch 2.15.0
Dashboards Version
Opensearch Dashboard 2.15.0
Plugins
name               component                            version
mvp-masters-1      opensearch-alerting                  <IP_ADDRESS>
mvp-masters-1      opensearch-anomaly-detection         <IP_ADDRESS>
mvp-masters-1      opensearch-asynchronous-search       <IP_ADDRESS>
mvp-masters-1      opensearch-cross-cluster-replication <IP_ADDRESS>
mvp-masters-1      opensearch-custom-codecs             <IP_ADDRESS>
mvp-masters-1      opensearch-flow-framework            <IP_ADDRESS>
mvp-masters-1      opensearch-geospatial                <IP_ADDRESS>
mvp-masters-1      opensearch-index-management          <IP_ADDRESS>
mvp-masters-1      opensearch-job-scheduler             <IP_ADDRESS>
mvp-masters-1      opensearch-knn                       <IP_ADDRESS>
mvp-masters-1      opensearch-ml                        <IP_ADDRESS>
mvp-masters-1      opensearch-neural-search             <IP_ADDRESS>
mvp-masters-1      opensearch-notifications             <IP_ADDRESS>
mvp-masters-1      opensearch-notifications-core        <IP_ADDRESS>
mvp-masters-1      opensearch-observability             <IP_ADDRESS>
mvp-masters-1      opensearch-performance-analyzer      <IP_ADDRESS>
mvp-masters-1      opensearch-reports-scheduler         <IP_ADDRESS>
mvp-masters-1      opensearch-security                  <IP_ADDRESS>
mvp-masters-1      opensearch-security-analytics        <IP_ADDRESS>
mvp-masters-1      opensearch-skills                    <IP_ADDRESS>
mvp-masters-1      opensearch-sql                       <IP_ADDRESS>
mvp-masters-1      repository-s3                        2.15.0
mvp-nodes-0        opensearch-alerting                  <IP_ADDRESS>
mvp-nodes-0        opensearch-anomaly-detection         <IP_ADDRESS>
mvp-nodes-0        opensearch-asynchronous-search       <IP_ADDRESS>
mvp-nodes-0        opensearch-cross-cluster-replication <IP_ADDRESS>
mvp-nodes-0        opensearch-custom-codecs             <IP_ADDRESS>
mvp-nodes-0        opensearch-flow-framework            <IP_ADDRESS>
mvp-nodes-0        opensearch-geospatial                <IP_ADDRESS>
mvp-nodes-0        opensearch-index-management          <IP_ADDRESS>
mvp-nodes-0        opensearch-job-scheduler             <IP_ADDRESS>
mvp-nodes-0        opensearch-knn                       <IP_ADDRESS>
mvp-nodes-0        opensearch-ml                        <IP_ADDRESS>
mvp-nodes-0        opensearch-neural-search             <IP_ADDRESS>
mvp-nodes-0        opensearch-notifications             <IP_ADDRESS>
mvp-nodes-0        opensearch-notifications-core        <IP_ADDRESS>
mvp-nodes-0        opensearch-observability             <IP_ADDRESS>
mvp-nodes-0        opensearch-performance-analyzer      <IP_ADDRESS>
mvp-nodes-0        opensearch-reports-scheduler         <IP_ADDRESS>
mvp-nodes-0        opensearch-security                  <IP_ADDRESS>
mvp-nodes-0        opensearch-security-analytics        <IP_ADDRESS>
mvp-nodes-0        opensearch-skills                    <IP_ADDRESS>
mvp-nodes-0        opensearch-sql                       <IP_ADDRESS>
mvp-nodes-0        repository-s3                        2.15.0
mvp-nodes-2        opensearch-alerting                  <IP_ADDRESS>
mvp-nodes-2        opensearch-anomaly-detection         <IP_ADDRESS>
mvp-nodes-2        opensearch-asynchronous-search       <IP_ADDRESS>
mvp-nodes-2        opensearch-cross-cluster-replication <IP_ADDRESS>
mvp-nodes-2        opensearch-custom-codecs             <IP_ADDRESS>
mvp-nodes-2        opensearch-flow-framework            <IP_ADDRESS>
mvp-nodes-2        opensearch-geospatial                <IP_ADDRESS>
mvp-nodes-2        opensearch-index-management          <IP_ADDRESS>
mvp-nodes-2        opensearch-job-scheduler             <IP_ADDRESS>
mvp-nodes-2        opensearch-knn                       <IP_ADDRESS>
mvp-nodes-2        opensearch-ml                        <IP_ADDRESS>
mvp-nodes-2        opensearch-neural-search             <IP_ADDRESS>
mvp-nodes-2        opensearch-notifications             <IP_ADDRESS>
mvp-nodes-2        opensearch-notifications-core        <IP_ADDRESS>
mvp-nodes-2        opensearch-observability             <IP_ADDRESS>
mvp-nodes-2        opensearch-performance-analyzer      <IP_ADDRESS>
mvp-nodes-2        opensearch-reports-scheduler         <IP_ADDRESS>
mvp-nodes-2        opensearch-security                  <IP_ADDRESS>
mvp-nodes-2        opensearch-security-analytics        <IP_ADDRESS>
mvp-nodes-2        opensearch-skills                    <IP_ADDRESS>
mvp-nodes-2        opensearch-sql                       <IP_ADDRESS>
mvp-nodes-2        repository-s3                        2.15.0
mvp-coordinators-0 opensearch-alerting                  <IP_ADDRESS>
mvp-coordinators-0 opensearch-anomaly-detection         <IP_ADDRESS>
mvp-coordinators-0 opensearch-asynchronous-search       <IP_ADDRESS>
mvp-coordinators-0 opensearch-cross-cluster-replication <IP_ADDRESS>
mvp-coordinators-0 opensearch-custom-codecs             <IP_ADDRESS>
mvp-coordinators-0 opensearch-flow-framework            <IP_ADDRESS>
mvp-coordinators-0 opensearch-geospatial                <IP_ADDRESS>
mvp-coordinators-0 opensearch-index-management          <IP_ADDRESS>
mvp-coordinators-0 opensearch-job-scheduler             <IP_ADDRESS>
mvp-coordinators-0 opensearch-knn                       <IP_ADDRESS>
mvp-coordinators-0 opensearch-ml                        <IP_ADDRESS>
mvp-coordinators-0 opensearch-neural-search             <IP_ADDRESS>
mvp-coordinators-0 opensearch-notifications             <IP_ADDRESS>
mvp-coordinators-0 opensearch-notifications-core        <IP_ADDRESS>
mvp-coordinators-0 opensearch-observability             <IP_ADDRESS>
mvp-coordinators-0 opensearch-performance-analyzer      <IP_ADDRESS>
mvp-coordinators-0 opensearch-reports-scheduler         <IP_ADDRESS>
mvp-coordinators-0 opensearch-security                  <IP_ADDRESS>
mvp-coordinators-0 opensearch-security-analytics        <IP_ADDRESS>
mvp-coordinators-0 opensearch-skills                    <IP_ADDRESS>
mvp-coordinators-0 opensearch-sql                       <IP_ADDRESS>
mvp-coordinators-0 repository-s3                        2.15.0
mvp-masters-0      opensearch-alerting                  <IP_ADDRESS>
mvp-masters-0      opensearch-anomaly-detection         <IP_ADDRESS>
mvp-masters-0      opensearch-asynchronous-search       <IP_ADDRESS>
mvp-masters-0      opensearch-cross-cluster-replication <IP_ADDRESS>
mvp-masters-0      opensearch-custom-codecs             <IP_ADDRESS>
mvp-masters-0      opensearch-flow-framework            <IP_ADDRESS>
mvp-masters-0      opensearch-geospatial                <IP_ADDRESS>
mvp-masters-0      opensearch-index-management          <IP_ADDRESS>
mvp-masters-0      opensearch-job-scheduler             <IP_ADDRESS>
mvp-masters-0      opensearch-knn                       <IP_ADDRESS>
mvp-masters-0      opensearch-ml                        <IP_ADDRESS>
mvp-masters-0      opensearch-neural-search             <IP_ADDRESS>
mvp-masters-0      opensearch-notifications             <IP_ADDRESS>
mvp-masters-0      opensearch-notifications-core        <IP_ADDRESS>
mvp-masters-0      opensearch-observability             <IP_ADDRESS>
mvp-masters-0      opensearch-performance-analyzer      <IP_ADDRESS>
mvp-masters-0      opensearch-reports-scheduler         <IP_ADDRESS>
mvp-masters-0      opensearch-security                  <IP_ADDRESS>
mvp-masters-0      opensearch-security-analytics        <IP_ADDRESS>
mvp-masters-0      opensearch-skills                    <IP_ADDRESS>
mvp-masters-0      opensearch-sql                       <IP_ADDRESS>
mvp-masters-0      repository-s3                        2.15.0
mvp-coordinators-1 opensearch-alerting                  <IP_ADDRESS>
mvp-coordinators-1 opensearch-anomaly-detection         <IP_ADDRESS>
mvp-coordinators-1 opensearch-asynchronous-search       <IP_ADDRESS>
mvp-coordinators-1 opensearch-cross-cluster-replication <IP_ADDRESS>
mvp-coordinators-1 opensearch-custom-codecs             <IP_ADDRESS>
mvp-coordinators-1 opensearch-flow-framework            <IP_ADDRESS>
mvp-coordinators-1 opensearch-geospatial                <IP_ADDRESS>
mvp-coordinators-1 opensearch-index-management          <IP_ADDRESS>
mvp-coordinators-1 opensearch-job-scheduler             <IP_ADDRESS>
mvp-coordinators-1 opensearch-knn                       <IP_ADDRESS>
mvp-coordinators-1 opensearch-ml                        <IP_ADDRESS>
mvp-coordinators-1 opensearch-neural-search             <IP_ADDRESS>
mvp-coordinators-1 opensearch-notifications             <IP_ADDRESS>
mvp-coordinators-1 opensearch-notifications-core        <IP_ADDRESS>
mvp-coordinators-1 opensearch-observability             <IP_ADDRESS>
mvp-coordinators-1 opensearch-performance-analyzer      <IP_ADDRESS>
mvp-coordinators-1 opensearch-reports-scheduler         <IP_ADDRESS>
mvp-coordinators-1 opensearch-security                  <IP_ADDRESS>
mvp-coordinators-1 opensearch-security-analytics        <IP_ADDRESS>
mvp-coordinators-1 opensearch-skills                    <IP_ADDRESS>
mvp-coordinators-1 opensearch-sql                       <IP_ADDRESS>
mvp-coordinators-1 repository-s3                        2.15.0
mvp-nodes-1        opensearch-alerting                  <IP_ADDRESS>
mvp-nodes-1        opensearch-anomaly-detection         <IP_ADDRESS>
mvp-nodes-1        opensearch-asynchronous-search       <IP_ADDRESS>
mvp-nodes-1        opensearch-cross-cluster-replication <IP_ADDRESS>
mvp-nodes-1        opensearch-custom-codecs             <IP_ADDRESS>
mvp-nodes-1        opensearch-flow-framework            <IP_ADDRESS>
mvp-nodes-1        opensearch-geospatial                <IP_ADDRESS>
mvp-nodes-1        opensearch-index-management          <IP_ADDRESS>
mvp-nodes-1        opensearch-job-scheduler             <IP_ADDRESS>
mvp-nodes-1        opensearch-knn                       <IP_ADDRESS>
mvp-nodes-1        opensearch-ml                        <IP_ADDRESS>
mvp-nodes-1        opensearch-neural-search             <IP_ADDRESS>
mvp-nodes-1        opensearch-notifications             <IP_ADDRESS>
mvp-nodes-1        opensearch-notifications-core        <IP_ADDRESS>
mvp-nodes-1        opensearch-observability             <IP_ADDRESS>
mvp-nodes-1        opensearch-performance-analyzer      <IP_ADDRESS>
mvp-nodes-1        opensearch-reports-scheduler         <IP_ADDRESS>
mvp-nodes-1        opensearch-security                  <IP_ADDRESS>
mvp-nodes-1        opensearch-security-analytics        <IP_ADDRESS>
mvp-nodes-1        opensearch-skills                    <IP_ADDRESS>
mvp-nodes-1        opensearch-sql                       <IP_ADDRESS>
mvp-nodes-1        repository-s3                        2.15.0
Screenshots

Additional context
Prometheus metrics are also not appearing

@tsmjeu
These metrics visualizations are depended on the existence of Otel compliant metrics in Prometheus or local index in openSearch with a simple schema naming convention
See additional instructions for setting up otel collector with opensearch

[Catch All Triage - 1, 2]

the propose doesnt seems to work

@tsmjeu These metrics visualizations are depended on the existence of Otel compliant metrics in Prometheus or local index in openSearch with a simple schema naming convention
See additional instructions for setting up otel collector with opensearch

Doesn't seems to work with 2.15

Hi, I met the same issue, index exists but not displayed in the select box.
Digging the YANG-DB's answer, I understand that by convention only indexes respecting the pattern ss4o_metrics-- are displayed in the Observability Metrics page.
I just renamed the index as ss4o_metrics-otel-%{yyyy.MM.dd} and now the index is displayed :

But metrics are not displayed due to #2172 .


FINERACT-1541: Pentaho accounting reports converted to table format

Description
https://issues.apache.org/jira/browse/FINERACT-1541
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Write the commit message as per https://github.com/apache/fineract/#pull-requests

[x] Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.

[ ] Create/update unit or integration tests for verifying the changes made.

[x] Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.

[ ] Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/api-docs/apiLive.htm with details of any API changes

[ ] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the developer mailing list for guidance, if required.)

FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.

@galovics  The migration ran successfully with both mysql and posgres. So do we need to create separate changes for mysql and postgres ?

@sheminanto, rebase this PR

@vidakovic  could you please include this in 1.7

This  PR is raised again at https://github.com/apache/fineract/pull/2291  with rebase changes


Temporarily skip flutter build apk for native_assets tests.

Work around for https://github.com/flutter/flutter/issues/158560.

Actually looks like autosubmit merged this with a lot of failing builds.

Actually looks like autosubmit merged this with a lot of failing builds.

Yeah I wonder if this is a cocoon regression?

I filed https://github.com/flutter/flutter/issues/158892 to track


Wasi Tutorial Error: Invalid digit found in string

When following the tutorial here:
https://github.com/bytecodealliance/wasmtime/blob/master/docs/WASI-tutorial.md
An error is seen when attempting to run the demo.wasm example (created from demo.c) with filenames that are strings. Specifically the command:
target/debug/wasmtime --dir=. ~/wasmtime-wasi-tutorial/demo.wasm a.txt b.txt
warning: using --invoke with a function that takes arguments is experimental and may break in the future
Error: failed to run main module /home/jlbirch/wasmtime-wasi-tutorial/demo.wasm
Caused by:
invalid digit found in string
A backtrace is indicating that the error is thrown from wasmtime_cli::commands::run::RunCommand::invoke_export
where it seems there is an attempt to match against a LongLong argument type instead of a string.

I encounter the exactly same bug with the rust version code, with wasmtime 4.0.0 on windows 11:

use the rust code from the tutorial
make the function process to be pub, and #[no_mangle]
compile the project with cargo wasi build
echo hello world > test.txt
run the command and its return error:

> wasmtime --dir=. target\wasm32-wasi\debug\demo.wasm --invoke process test.txt somewhere.txt
warning: using `--invoke` with a function that takes arguments is experimental and may break in the future
Error: failed to run main module `target\wasm32-wasi\debug\demo.wasm`

Caused by:
    invalid digit found in string

and I checked out that what #858 has fixed is another bug, and its added a test for a digit param when invoking, but not for a string param, which is the bug I'm encountering now.

I find out another problem with the same bug on stackoverflow, just linking :-}


Add support for ignore_invalid_headers_in_responses in client::Builder

Is your feature request related to a problem? Please describe.
I am trying to fetch resource that located behind Imperva/Incapsula WAF.  As part it's client-classification process sometimes the WAF added cookies in the following format Set-Cookie: ___utmvaPRuXKscZ=dmo\x01OZPF; path=/; Max-Age=900; Secure; SameSite=None\r\n this cookie include the invalid \x01 in the middle. Currently I am not able to parse such responses with hyper-client,
Describe the solution you'd like
httparse has support in ignore_invalid_headers_in_response flags , I want to add the support to this flag in the same way that hyper support allow_obsolete_multiline_headers_in_responses .
Describe alternatives you've considered
N/A
Additional context
If it's sounds good I will start to work on PR

Just noticed that it's been added to httparse after the last release, so probably will need to wait for new httparse release

just found the   #2819 Draft  :)


chore(typeahead): Watermark text for Autocomplete

I believe the original ng-bootstrap supported showing autocomplete text (first matching result) as a watermark in the input.  Can this get implemented in ng2-bootstrap?

not sure I have seen what are talking about
so please provide a link to sample please :)

@ps2goat Do you mean the HTML property placeholder? You can bind to that with ng2 using square brackets if you want to make it dynamic.


Expose audio_channels to kinetics dataset

Allows the user to choose the number of audio channels returned from the decoder

Codecov Report

Merging #1559 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1559      +/-   ##
==========================================
+ Coverage   65.92%   65.93%   +<.01%
==========================================
  Files          90       90
  Lines        7073     7074       +1
  Branches     1076     1076
==========================================
+ Hits         4663     4664       +1
  Misses       2102     2102
  Partials      308      308

Impacted Files
Coverage Δ

torchvision/datasets/kinetics.py
37.5% <ø> (ø)
:arrow_up:

torchvision/datasets/video_utils.py
72.43% <100%> (+0.17%)
:arrow_up:

Continue to review full report at Codecov.

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


Istiod: refactor component startup

Describe the feature request
Right now Galley, Pilot, Injector, NodeAgent  are started from a main() that calls a
function in the pkg/ which creates gprc server, listens, in some cases handles MTLS,
adds monitoring and ctrlz ports, etc.
While this can be hacked to work for istiod, ideally for each component we would have a pair
of separate functions:
Init(grpcServer, httpMux, debugMux) - where the component will register its services and
handlers, without creating its own grpc server/listeners, and do any initialization is needed.
Start() - start serving.
Istiod will create a single gRPC server, as well as http and debug (ctrlz plus other debug endpoints), and init each component.
Galley and Pilot have some flexibility - the autoinjector is the worse so it would be first priority.
Additional startup options - like patching the webhooks for galley/injector - should not be part
of the new Init method, but exposed as Public methods that may be called as needed.
The startup will take care of creating certs if needed and all ordering of components ( so Pilot
Init is called after galley Init and Start are done, etc),
Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[ ] Docs
[x] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Additional context

@howardjohn

@costinm before we start creating tasks, can we have a kick-off for istiod and put together a rough roadmap and prioritize work? This is a big change and I think we need to take a step back and get on the same page.

It this slated for 1.4? There's only 3 days left till the freeze.

Is this slated for 1.4? There's only 3 days left till the freeze.

1.5 at the earliest


Different AVC low power encoding quality on free and non-free media drivers

Following the article https://github.com/Intel-Media-SDK/MediaSDK/wiki/Intel-media-stack-on-Ubuntu, let's compare AVC low power encoding outputs from free and non-free drivers:
wget https://fate-suite.libav.org/h264-conformance/AUD_MW_E.264
/usr/share/mfx/samples/sample_decode h264 -i AUD_MW_E.264 -o AUD_MW_E.yuv -i420

# free driver:
apt-get install intel-media-va-driver
/usr/share/mfx/samples/sample_encode h264   -w 176 -h 144 -f 30 -cqp -qpi 30 -qpp 30 -qpb 30 -qsv-ff    -i AUD_MW_E.yuv -o encoded_free_AUD_MW_E.264

# non-free driver:
apt-get install intel-media-va-driver-non-free
/usr/share/mfx/samples/sample_encode h264   -w 176 -h 144 -f 30 -cqp -qpi 30 -qpp 30 -qpb 30 -qsv-ff    -i AUD_MW_E.yuv -o encoded_nonfree_AUD_MW_E.264

sha1sum encoded*
2d4baa6a75e9ae5c7f1e57d4127cd8849360dc29  encoded_free_AUD_MW_E.264
52c1b787b16f51c7ba30eebb67deec8cf35a5354  encoded_nonfree_AUD_MW_E.264

Why free/non-free drivers output differs?
Above results obtained under Ubuntu 19.10 running on SKL.

That's likely media driver bug, but free/nonfree drivers return different caps and potentially mediasdk might do something different after reading caps. So, I suggest to investigate from mediasdk side.

On which platform did you find the issue?

SKL

Issue reproduced with latest media-driver master.
By driver dumps:
With free driver sets TU = 7 by default, instead of TU = 4 w/ non-free.
I found that with -DENABLE_NONFREE_KERNELS=OFF, also enables flag _FULL_OPEN_SOURCE.
This code is cause of issue:
#ifdef _FULL_OPEN_SOURCE
    if (!GFX_IS_PRODUCT(m_encodeCtx->pMediaCtx->platform, IGFX_ICELAKE_LP))
    {
        if (m_encodeCtx->targetUsage >= 1 && m_encodeCtx->targetUsage <= 2)
        {
            m_encodeCtx->targetUsage = 4;
        }
        else if (m_encodeCtx->targetUsage >= 3 &&m_encodeCtx->targetUsage <= 5)
        {
            m_encodeCtx->targetUsage = 7;
        }
    }
#endif

I checked with m_encodeCtx->targetUsage = 4; in second else if block. Files w/ free/non-free drivers are bitmatch.
So, problem is on driver side.

@AntonGrishin , thanks! Indeed. it doesn't make sense why VDENC in CQP mode behaves differently for free and non free build. Can you please submit issue against media driver?

Not reproduced with latest media-driver master.
52c1b787b16f51c7ba30eebb67deec8cf35a5354  encoded_free_AUD_MW_E.264
52c1b787b16f51c7ba30eebb67deec8cf35a5354  encoded_nonfree_AUD_MW_E.264

Hi @dvrogozh can we close this issue?


Create a new page to display hobbies.

I think we can scrap this as well since we're already incorporating multiple pages with Jinja which satisfies the requirement


Metadata and Datastore Storage Refactor

Here is my final PR of this internship (sadly). Let me know if there are any other tests you'd like to see me include.

It also seems that there are a lot of files to be reviewed, but I believe that's because Alvin couldn't work on his PR with his power outage.


[MLCChat] Separate function for generating sharding PrimFunc

The create_shard_func produces both the tir.PrimFunc that performs the sharding and a relax.Function wrapper that calls into it.  This separates out the two functions, such that the tir.PrimFunc can be generated without also generating the relax.Function wrapper.

Rebased onto mlc-serve-v0.2.0 to resolve conflict.


Icon request: GOV.BR

URL for the brand / site / app
https://www.gov.br/
Logo resources for the icon
https://pt.m.wikipedia.org/wiki/Ficheiro:Gov.br_logo.svg
Proof of the Aegis-compatible 2FA

Anything else?
When looking for how to activate 2FA on the access.gov.br website, we only found instructions on how to do this through the use of an application found in the Play Store, Gov.br, but when activating 2FA, within the account settings there is the option to additionally activate "Offline 2-Step Verification" by scanning a QR code via the OTP app.
In the third screenshot of the test, I put the translation of the text of the page from Portuguese to English.
Confirmation

[X] I have read and followed the issue guidelines & issue form.

Here you go!
https://github.com/aegis-icons/aegis-icons/blob/master/icons/1_Primary/GOV.BR.svg

:question: How to add icon(s) to Aegis?
:star: Support this project by giving a star! Just adding like to this comment is also appreciated.


Update manage-partners.md

Changed from Billing to settings

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/4643

@Kateyanne Please merge this PR. Thanks.


Actual WebView User Agent support for Android.

I have noticed that the current userAgent implementation for Android returns the device's user agent, not the WebView's user agent, as suggested in posts such as this on Stack Overflow.
Exposing the WebView's userAgent as webViewUserAgent will benefit many developers who want to use it in their Android implementation, i.e. append something to the preexisting user agent.
The only problem I have is that since userAgent on the iOS-side already returns the expected WebView user agent, the implementation of webViewUserAgent for iOS will merely return the same value as userAgent.

Forgot to update Readme, closing for now.

I understand that there hasn't been activity lately in regards to merging requests,
so if anybody is interested in these additions:
"dependencies": {
  "react-native-device-info": "git+https://github.com/Naoto-Ida/react-native-device-info.git#webview-ua"
}

Cheers.

Would be great if this PR is merged. 👍

I hope so too...

Any updates on this? I can fix the conflicts if there's any plans of merging this.

will merge, ping me when done with conflicts.

Actually the iOS userAgent returns the WebView user agent, instead of the default HTTP user agent like this:
<product-name>/<build-number> CFNetwork/548.0.3 Darwin/11.2.0

which is the opposite behavior for Android clients. For backwards compatibility, I suggest deprecate the existing DeviceInfo.getUserAgent() method and add

DeviceInfo.getWebViewUserAgent()
DeviceInfo.getHTTPUserAgent()

See also: #142

@Naoto-Ida what's the status on this PR?
@leethree comment seems like the good way to go if there is indeed an inconsistency.

Good idea!

The android WebView is already the real android webview useragent, since 6 months (in my understanding) https://github.com/rebeccahughes/react-native-device-info/commit/41d0ca9a88429bf7057661a1be878a772c72600b

@DracoBlue Yes I believe you can close this.


NIFI-1781: Updating UI to respect access controls outside of canvas

Updating UI according to permissions through out the application.
Shuffling provenance events, template, and cluster search REST APIs according to resources being authorized.
Moving template upload controls.
Removing username where appropriate.
Addressing issues when authorizing flow configuration actions.
Code clean up.

@mcgilman excellent - all looks good, as far as I can tell. This PR addresses several issues that existed in the application. I've pushed to master.


Make tags to use basespan

LGTM @pavolloffay. @yurishkuro is right about the missing test :-/

I will write something, do not merge  yet.
On 12 May 2017 17:36, "Ben Sigelman"<EMAIL_ADDRESS>wrote:

LGTM @pavolloffay https://github.com/pavolloffay. @yurishkuro
https://github.com/yurishkuro is right about the missing test :-/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/opentracing/opentracing-java/pull/139#issuecomment-301110583,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFW6-Jt_CwQMJKVbRlzGmTBeO1Q54Vmmks5r5HyTgaJpZM4NZWL0
.

Test is there


Command line tool for compiling templates

It would be cool if Ractive came with a CLI tool for precompiling templates.
I suggest a file format like:
-- template: name1

{{foo}} {{bar}}

-- template: name2

{{#stuff}}...{{/stuff}}

... basically, a series of Ractive templates separated by -- template and the desired name of the template (which would ultimately be registered as a partial).
The result of compiling the file would be a nodejs style module which exports an object with all of the (parsed) templates.
Another option for a file format would be to have one file per template, with the file name being the registered partial's name. This is how dust.js does it. I personally dislike this style, because 1) partials are often very short, which makes dedicating an entire file to it feel like a waste, and 2) it's nice to group related partials together.
I wrote this as a starting point.
#!/usr/bin/env node

var path = require('path'),
    fs = require('fs'),
    sys = require('util'),
    Ractive = require('ractive');

var parse = function (data) {
    var parts = data.split(/(?:^|[\r\n])-- template: (.*)/).slice(1);
    var template = "";
    for (var i = 0; i < parts.length; i+=2) {
        template += "module.exports.";
        template += parts[i];
        template += "=";
        template += JSON.stringify(Ractive.parse(parts[i+1]));
        template += ";";
    }
    sys.print(template);
};

process.stdin.resume();
process.stdin.setEncoding('utf8');

var buffer = '';
process.stdin.on('data', function(data) {
    buffer += data;
});

process.stdin.on('end', function() {
    parse(buffer);
});

You can cat templates/*.ractive | ractivec > parsed-templates.js, and in your application
partials = require('./parsed-templates.js')
new Ractive({..., template: partials[templatename], partials: partials, ...})

with browserify putting in the heavy lifting to make this work on client side.
Comments?

edge now has a bin included, so if you npm i -g ractive@edge, you can echo "
hello, {{name}}
" | ractive parse and get output suitable for pasting into new Ractive({ template: ... }). It should also handle expressions for csp. You can get a list of options by calling it with no command e.g. ractive.


What about validating user input and checking data for redundancy?

Hello Rick,
Thanks for this feedback, however I did not see this solution on stack overflow as suggested and I also noticed that a lot of people are coming up with the same question for Razor.
I also get the impression you believe stack overflow is extensive in it's solutions, while this is not a bad idea, I wouldn't go with you regarding upgraded technologies. I've practically been on stack overflow all day to no avail.
I hope you find some time to have a look at the problem soon. Thanks once again.

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

ID: 39b6d0f3-9bc7-d091-0d45-9fc1e2e7aac8
Version Independent ID: 20e7eb53-215b-09ab-205d-d20177221278
Content: Add validation to an ASP.NET Core Razor Page
Content Source: aspnetcore/tutorials/razor-pages/validation.md
Product: aspnet-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@code2expert What @Rick-Anderson  was saying is that you should post your question to StackOverflow. Devs will then respond to your scenario with ideas like using AJAX and web API to validate user input before submitting a form back to the server. We just don't have the staffing to describe every conceivable scenario that devs will wish to pursue.

Okay guardex, thanks for the feedback. I saw quite some feedback with AJAX though but I was trying to do the validation on the server side with the razor models really.

And I thought you could point me to an alternative to Remote Validation in Razor

I can't point you to a specific resource. I don't have anything bookmarked here. A few years ago, I did implement the approach that you're seeking to use (AJAX + web API to validate user input before POSTing a form), but that was with a .NET Framework (webforms) app, and I don't have saved links (or even the app).
Your best approach is to ask a new question on SO about it. I'm sure you'll get help there. You could also inquire on a support chat, such as Slack or Gitter. There are only a few doc authors here, and we're 🏃🏃🏃😅 on priority issues. Right now, we won't cover AJAX with web API for validating user input prior to form submission, but that's basically what you're probably looking to do.

I found a way around it in the model running a query against the database in the create.cshtml.cs and it works fine. Thanks


plan to support Update/Insert/Delete ?

Hi, I found the README file said that:
Only read operations are supported, such as SHOW and SELECT.
Is there any plan to support Update/Insert/Delete?
Thanks in advance.

A while ago, in #16, I added support for ExecContext and implemented methods of the Result interface. I only did this to support the USE statement. There are no tests for DML statements like INSERT, UPDATE and DELETE, so this statement in the README is correct. But you should try it, as it might not require any extra work.

@nineinchnick  it works! and it does not require any extra work. Thanks!

@nineinchnick  does it support transaction? I roughly walked thru the code and figure out this go-client is using TrinoDB REST API to implement the sql driver interface. So I think transaction is not supported due to the stateless in http's nature. But I am not 100% sure.

Transaction statements should work, but we don't have tests for this.


Fix ChatOllama model parameter

What?
Fix model parameter to ChatOllama constructor.
Why?
The model parameter name to ChatOllama was wrong, effectively pinning it to the default of "llama2" and preventing usage of other Ollama models.

@ptgoetz looks good!


Adding a predict CLI endpoint

In this PR, I've added a predict endpoint to nbaspa-model to run game-level predictions and save to the survival-prediction folder within each season.

Codecov Report

Merging #24 (3b81614) into develop (ea32ff0) will increase coverage by 0.37%.
The diff coverage is 96.55%.

@@             Coverage Diff             @@
##           develop      #24      +/-   ##
===========================================
+ Coverage    80.77%   81.14%   +0.37%
===========================================
  Files           49       49
  Lines         1919     1973      +54
===========================================
+ Hits          1550     1601      +51
- Misses         369      372       +3

Impacted Files
Coverage Δ

nbaspa/model/tasks/io.py
95.12% <90.47%> (-4.88%)
:arrow_down:

nbaspa/model/pipeline.py
100.00% <100.00%> (ø)

nbaspa/model/scripts/model.py
92.68% <100.00%> (+2.05%)
:arrow_up:

nbaspa/model/tasks/__init__.py
100.00% <100.00%> (ø)

nbaspa/model/tasks/tuning.py
94.80% <0.00%> (-1.30%)
:arrow_down:

Continue to review full report at Codecov.

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


Issue #000 fix: update course batch updater config.

Codecov Report

Merging #528 into course-batch-jobs will not change coverage.
The diff coverage is n/a.

@@                 Coverage Diff                  @@
##             course-batch-jobs     #528   +/-   ##
====================================================
  Coverage                32.28%   32.28%
  Complexity                1236     1236
====================================================
  Files                      170      170
  Lines                    15074    15074
  Branches                  2392     2392
====================================================
  Hits                      4866     4866
  Misses                    9471     9471
  Partials                   737      737

Continue to review full report at Codecov.

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


What is max length and valid characters for upload_to_testflight changelog?

Question Checklist

[X] Updated fastlane to the latest version
[X] I read the Contribution Guidelines
[X] I read docs.fastlane.tools
[X] I searched for existing GitHub issues

This refers to fastlane action upload_to_testflight changelog parameter.
I received the following error:
Could not set changelog: An attribute value has invalid text. - Text for whatsNew contains invalid characters/formats.
I cannot locate documentation on the maximum length and valid characters allowed.

✅ fastlane environment ✅
Stack

Key
Value

OS
10.15

Ruby
2.6.1

Bundler?
true

Git
git version 2.21.0 (Apple Git-122)

Installation Source
~/.rbenv/versions/2.6.1/bin/fastlane

Host
Mac OS X 10.15 (19A602)

Ruby Lib Dir
~/.rbenv/versions/2.6.1/lib

OpenSSL Version
OpenSSL 1.0.2r  26 Feb 2019

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
11.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
default_platform(:ios)

platform :ios do

  desc "iOS Fastlane for builds and release"

  before_all do
    setup_circle_ci
  end

  lane :adhoc do
    match(app_identifier: ["<REDACTED"], type: "adhoc", readonly: true)
    gym(
      scheme: "<REDACTED",
      export_method: "ad-hoc",
      configuration: "Adhoc"
    )
  end

  lane :release do
    match(app_identifier: ["<REDACTED"], type: "appstore", readonly: true)
    gym(scheme: "<REDACTED", export_method: "app-store")
    betweenValues = sh("head", "-n", "1", "../releaseinfo")
    puts betweenValues
    changelog = changelog_from_git_commits(between: "#{betweenValues}", merge_commit_filtering: "exclude_merges", date_format: "short")
    upload_to_testflight(changelog: changelog)
    newBuildNumber = increment_build_number(xcodeproj: "<REDACTED")
    commit_version_bump(
        xcodeproj:"<REDACTED",
        message:"[skip ci] <REDACTED>"
    )
    push_to_git_remote
  end

end

`./fastlane/Appfile`
app_identifier("<REDACTED") # The bundle identifier of your app
apple_id("<REDACTED") # Your Apple email address

itc_team_id("<REDACTED") # App Store Connect Team ID
team_id("<REDACTED") # Developer Portal Team ID

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.134.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.3.0

bundler
1.17.2

etc
1.0.1

forwardable
1.2.0

CFPropertyList
3.0.1

public_suffix
2.0.5

addressable
2.7.0

atomos
0.1.3

babosa
1.0.3

claide
1.0.3

colored
1.2

colored2
3.1.2

highline
1.7.10

commander-fastlane
4.4.6

declarative
0.0.10

declarative-option
0.1.0

digest-crc
0.4.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

dotenv
2.7.5

emoji_regex
1.0.1

excon
0.67.0

multipart-post
2.0.0

faraday
0.17.0

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday_middleware
0.13.1

fastimage
2.1.7

gh_inspector
1.1.3

jwt
2.1.0

memoist
0.16.0

multi_json
1.14.1

os
1.0.1

signet
0.12.0

googleauth
0.6.7

httpclient
2.8.3

mime-types-data
3.2019.1009

mime-types
3.3

uber
0.1.0

representable
3.0.4

retriable
3.1.2

google-api-client
0.23.9

google-cloud-env
1.2.1

google-cloud-core
1.3.1

google-cloud-storage
1.16.0

json
2.2.0

mini_magick
4.9.5

multi_xml
0.6.0

plist
3.5.0

rubyzip
1.3.0

security
0.1.3

naturally
2.2.0

simctl
1.6.6

slack-notifier
2.3.2

terminal-notifier
2.0.0

unicode-display_width
1.6.0

terminal-table
1.8.0

tty-screen
0.7.0

tty-cursor
0.7.0

tty-spinner
0.9.1

word_wrap
1.0.0

nanaimo
0.2.6

xcodeproj
1.12.0

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.0

generated on: 2019-10-28

Hello @aquacode 👋

I cannot locate documentation on the maximum length and valid characters allowed.

According to the documentation from App Store Connect Help, the limit is 4000 characters:

What’s New in this Version | A description of the changes in this version of the app such as new features, UI improvements, or bug fixes. Limited to 4000 characters.

I also had a look at our codebase:
https://github.com/fastlane/fastlane/blob/dce03348675149d986224d99e39e1fbd36bbcf3f/pilot/lib/pilot/build_manager.rb#L222-L231
The changelog is truncated when it is longer than 4000 characters.
Unfortunately I didn't find an info about valid characters allowed.

Thanks. This is the closest thing to documentation for that field that I was able to find as well:
https://help.apple.com/app-store-connect/#/devf29afbb74
Here I notice that for the Description field for releasing the app the following text:

A description of the app, detailing the features and functionality. Limited to 4000 characters. The description should be in plain text, with line breaks as needed. HTML format is not supported.

I suppose one can assume it is the same requirement for "What's New in this Version" but I'm not certain.
Also, I could not find any documentation on whether or not "What to Test" actually becomes "What's New in this Version" but it seems to be the case.

Only additional information I was able to find regarding this issue is that certain special characters (not documented) including HTML formatting is NOT allowed in the changelog string.


Feature: search? fuzzy search?

Any plans for a search or fuzzy search feature using fzf or ripgrep?
My use case is dumpster diving to find the right RFC and other RFCs that relate to it. Showing relationships between RFCs would be a killer feature, but it would start with a search capability.

Hi!
Thank you for opening this issue.
I did'nt think of this feature, but it should be easy enough to add it, by searching through the INDEX and the locally downloaded RFCs. I can add this feature in a day or two but PRs are also welcomed :smiley:


⚠ Bofrost.lu has degraded performance

In 778936f, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 823 ms

Resolved: Bofrost.lu performance has improved in 93267e7.


Added landscape.io badge and moved badges to the bottom

Not sure how to set up the shields.io stuff, abandoning this

Coverage remained the same at 75.81% when pulling 85df0c35f2e4c9743e14a758d15c52b44cf16450 on erikbern/badges into 03b6f774d4753e527fcdddce6eb43254f820c5ac on master.


[Bug Report] [Bug Report] component - popoper - Invalid first click

Element UI version
2.0.4
OS/Browsers version
win10 And the latest chrome version
Vue version
2.5.2
Reproduction Link
https://jsfiddle.net/mmx38qxw/
Steps to reproduce
http://element.eleme.io/2.0/#/en-US/component/popover
click the button "Click to activate"
What is Expected?
click once to open it as elementUI 1.4.9
What is actually happening?
click twice

Actual reproducible link: https://jsfiddle.net/mmx38qxw/1/

Duplicate of #8186


Crash using web sockets over https

Trying to combine ssl and websocket examples using VS2015 I've got a crash in SSLAdaptor::is_open() at the moment of opening the connection. After some examination I found out that SSLAdaptor::ssl_socket_ is nullptr. It happens in Connection::handle() when calling:
handler_->handle_upgrade(req, res, std::move(adaptor_));
and then adaptor_ is being accessed in lambda expression in Connection::do_read():
if (ret && adaptor_.is_open())
Is there any working example how to make websocket connection over https?
Thank you.

As a temporary workaround I have changed SSLAdaptor::ssl_socket_ from unique_ptr to to shared_ptr and defined move constructor for SSLAdaptor like this:
SSLAdaptor(SSLAdaptor&& other) : ssl_socket_(other.ssl_socket_)
{
}

So it works for me for now, but I have not examined all consequences yet.


Deleting GO records from dependent_xref table

Requirements

Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion;
Review the contributing guidelines for this repository; remember in particular:

do not modify code without testing for regression
provide simple unit tests to test the changes
if you change the schema you must patch the test databases as well, see Updating the schema
the PR must not fail unit testing

Description
An error is appearing when reaching the DataChecks step in the xref pipeline concerning some dangling references in the dependent_xref table. This is probably occurring because the GO import pipeline was run before the xref one, when the reverse is usually recommended.
When the GO import pipeline runs, it adds GO data into the db. When the xref pipeline is run after that, it deletes this GO data from the xref and object_xref tables, leaving the dependent_xref records unlinked. This fix deletes these dependent_xref records to prevent the existence of dangling references.
Use case
Deleting GO records from dependent_xref table to prevent dangling references DataCheck error.
Benefits
Xref pipeline mapping step starts with a fresh db that doesn't include unlinked references.
Possible Drawbacks
None.
Testing
Testing is already happening in DataChecks (foreign keys), which are succeeding after this fix.

Coverage decreased (-0.1%) to 82.242% when pulling ca4c854ac9cdf0f77b81d2b8f988c66c7a2fe50c on fix/xref_dangling_refs into f6c7ef20e845752ad52450e9b869dea5ad290ccf on master.

I am not sure why changes are appearing regarding spaces in the code, as the branch was created directly from master.

I am not sure why changes are appearing regarding spaces in the code, as the branch was created directly from master. Could be related to the text editor I used locally?

Might be a setting in your text editor that's trying to be helpful and reformatting the text without asking you

I am not sure why changes are appearing regarding spaces in the code, as the branch was created directly from master. Could be related to the text editor I used locally?

Might be a setting in your text editor that's trying to be helpful and reformatting the text without asking you

You're probably right! I reverted those changes to keep things consistent.


Add Are you working on it? section to the issue templates.

Is your feature request related to a problem? Please describe.
There is no option to know the issue reporter is working on the issue unless he commented on that.
Describe the solution you'd like
Add a section namedAre you working on it? to the issue templates.
Issue templates are located in .github directory

I'll do this


Implement the localStorage functionality to store the items added by a user

Append the to-do to the localStorage when a user adds a to-do ,on page load get the data from localStorage and display it to the page,

I can handle this one

Sure, go ahead!


Arm Support

I'd like to try to use skupper on edge devices like the Raspberry pi 4 or a Jetson Nano (What I'm using now)
skupper-docker-controller has an arm based image these 2 do not:
quay.io/interconnectedcloud/qdrouterd
quay.io/skupper/skupper-docker-proxy-controller
Where does the skupper-docker-proxy-controller image come from? What repo?

@dmc5179
The skupper-docker-controller is a rename of skupper-docker-proxy-controller that was part of PR #2. I missed updating the controller image name in the skupper init. I will make the update to fix that.
In the meantime, you can override the image via the "PROXY_CONTROLLER_IMAGE" env variable if you would like to try it.
I am not sure what the status is for having an arm based image for the qdrouterd, I will ask the qdr developers.
Thanks for checking out skupper-docker and appreciate your observations and feedbac.

It is now updated to use the skupper-docker-controller image...


Feature : Circuit Automation using AI Integration: Build Faster with a Prompt

Is your feature request related to a problem? Please describe
Designing complex circuits manually can be time-consuming and prone to human error. Students and engineers may struggle with selecting the right components, connecting them accurately, and achieving the desired functionality. This slows down the learning process and increases the difficulty of prototyping, especially for beginners. The absence of automation in circuit creation results in inefficiency, limiting experimentation and innovation.
Describe the solution you'd like
I would like to implement AI-powered Circuit Automation, where users can simply provide a text prompt describing the type of circuit they want to create, and the system automatically generates the basic structure of the circuit. The AI would intelligently select the right components, configure the connections, and generate a circuit based on the user's description. For example, if a user inputs "Create a basic RC low-pass filter," the AI will generate a functioning circuit with the necessary resistor and capacitor in the correct configuration.
Key Features:

Users enter natural language descriptions, and the system builds circuits accordingly.
AI suggestions for optimizing circuit design and improving efficiency.
Real-time editing after the circuit is generated, with the ability to tweak components as needed.

Describe alternatives you've considered

Manual Circuit Design: Users can continue designing circuits manually, which provides complete control but can be slow and tedious, especially for large or complex circuits.
Circuit Templates: Pre-built templates for common circuit types, which can help users get started but may not be flexible enough for custom designs.

Additional context
Technology Integration: This feature will require integrating an AI model capable of understanding circuit-related prompts and transforming them into logical circuit designs. We can explore using natural language processing (NLP) models in conjunction with circuit design databases.
Are you working on this?
No

@vedant-jain03 @subhamkumarr @tanmoysrt
Please review this.

This requires training a model with our circuit data structure, it will being additional complexity and infrastructure expenses. But if you want to build as a third party integration using circuitverse API, then feel free to do that.

@gitsofaryan thanks for the initiative though


PathTypeBased Servlet

Itrating all the child pages based on path type servlet extends SlingAllMethodsServlet

it has no conflicts... its working properly...


Don't keep module functions, and add to python path.

Pull Request Description
What issue does this change request address?
Closes #151
What are the significant changes in functionality due to this change request?

_module_methods in Function no longer keeps a link to the functions, which can be hard to serialize.
If the target file is not in the path, it probably needs to be, so add it.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass.
[ ] 5. If significant functionality is added, there must be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large tes.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added, the the analytic documentation must be updated/added.
[ ] 9. If any test used as a basis for documentation examples have been changed, the associated documentation must be reviewed and assured the text matches the example.

@PaulTalbot-INL Was this something we wanted to merge? Will merging this require RAVEN to be changed with the patch @joshua-cogliati-inl provided?

I don't think this requires RAVEN to be changed, but the changes Josh showed for RAVEN may be required to run HERON in parallel still.
I'm fine with merging this in, I'll do the review real quick.


[Issue_166] Add the ability to exclude Faces new TCK tests; exclude challenge #1935 tests

Resolves #166 against the 33.x branch
Upstream: #168

I just updated this to remove a cruft file.

yeah, my non-IDE text editor loves to use tabs in xml

Thanks @jamezp @jasondlee and @scottmarlow


🌙 Nightly CI with Mina Local Network

Description
We've successfully implemented a Proof of Concept (POC) workflow utilizing mina-local-network, paving the way for a significant enhancement in Pallad's test suites. The proposed feature involves the integration of workflows & (CI) that not only test against this deployed network within CI but also against public networks.
🎯 Goals

Enhance Pallad's test suites.
Implement workflows & CI that utilize mina-local-network.
Test against both the local network in CI and public networks.

🛠 Proposed Solution

Introduce environmental variables to the test suites for greater flexibility.
These variables should include configurable mnemonics, network URLs.
Eliminate hard-coded parameters currently present in our test suites to allow for more dynamic and adaptable testing environments.

🚀 Package Release via Nightly Workflows

Implement automated nightly workflows to release Pallad's packages to npmjs.
Ensure each nightly build passes all new and existing tests before release.
This automation enhances the frequency and reliability of package updates, providing users with the latest features and bug fixes.

💡 Expected Benefits

Enhanced test accuracy and coverage.
Increased flexibility and adaptability in testing different network environments.
Improved reliability and maintainability of Pallad's test suites.

A first attempt was made at this in PR https://github.com/palladians/pallad/pull/121. It is a simple task to extend this nightly workflow against the node provider but not yet possible to abstract over archive provider as it is specific to Mina Explorer's API and not agnostic yet.
To better enable a nightly CI the @palladxyz/mina-graphql package should be renamed & refactored to @palladxyz/mina-providers to have agnostic providers that can all satisfy a single wallet-provider interface to fetch account information, transaction information, and transaction submission APIs. This would make it easier to extend Pallad to using a local web-node like OpenMina or any Mina data provider.


region updateRender: the startLimited value has floating precision losted problem

Wavesurfer.js version(s):
3.0.0
Browser and operating system version(s):
chrome 76.0.3809, windows 10
Code needed to reproduce the issue:
updateRender() {
        const dur = this.wavesurfer.getDuration();
        const width = this.getWidth();

        var startLimited = this.start;
        var endLimited = this.end;
        if (startLimited < 0) {
            startLimited = 0;
            endLimited = endLimited - startLimited; //
        }
        if (endLimited > dur) {
            endLimited = dur;
            startLimited = dur - (endLimited - startLimited);
        }
...
    }

When endLimited > dur, after setting endLimited to dur, startLimited = dur - (endLimited - startLimited)  -> startLimited = dur - (dur - startLimited). I dont know why this is necessary. And this will cause floating precision losted.

@lisashen can you make a pull request with a fix?

@lisashen still an issue with v3.2.0?


edfapi dependency

I've slacked about this a couple of times, but despite what I previously thought, the Eyelink Developers Kit is required. There were some stray files that didn't get deleted when I thought I had uninstalled the Developers kit that lead to that misconception.
At this point, I've managed to install on the command line after manually downloading the .dmg file and converting that to a .pkg on macOS. I should be able to download the .dmg file once I figure out the right wget syntax, which can then be put into our workflow yml file for testing.

Is the link to downloading .dmg file publicly available? I'm asking because I remember having to register for the SR Research forum and wait for their confirmation before I can access any of those pages.

Is the link to downloading .dmg file publicly available? I'm asking because I remember having to register for the SR Research forum and wait for their confirmation before I can access any of those pages.

This is also mentioned in eyelinkio and eyelinkReader

No, it's not. But there's a way to pass usernames and passwords to wget (and a way to keep those hidden in Github actions).
So our users will still have to register and install, but for the purposes of CI testing, we can install it into the CI environment that way.

I actually wonder how that's handled in eyelinkio if there's any CI set up there, or if he just tests locally.

It looks like he just has linting setup for eyelinkio Github Actions.
I'm more than happy to go down this rabbit hole since I need more familiarity with Github Actions for my own work.

Handled for CI purposes by copying download link - for now, general users can just manually download so we don't have to worry about license distribution rules.


x/tools/gopls:

What version of Go are you using (go version)?

$ go version

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env

What did you do?

What did you expect to see?
What did you see instead?

Empty issue, closing.

@stamblerre - there appear to be a lot of empty gopls issues being created of late:
https://github.com/golang/go/issues?q=is%3Aissue+"DESCRIBE+THE+PROBLEM"+is%3Aclosed+label%3Agopls
I'm not even sure whether these are part-automated or simply the result of a user accidentally clicking "Create" on a pre-populated issue page?

Yep, these are my bad - we're trying to prompt users to file issues when gopls crashes / fails to initialize in VS Code Go. We're still iterating on how to improve these, but we've moved them to the vscode-go issue tracker now: https://github.com/golang/vscode-go/issues/304.


Nuke zips

This PR:

nukes all ZIPs from the repository
updates extension.json to use archives from GitHub
adds more sanity checks to check.py
one can now run python3 check.py foo to check only the foo extension and not all of them

Please pay special attention to extensions gerty jukebox usermanager where the hash had to be changed (meaning that the ZIP uploaded earlier was not the same as the generated ZIP by GitHub).

https://media.tenor.com/KtxkWfiztPwAAAAC/you-dropped-this-king-you-dropped-this-queen.gif


Issue: Select element border radius and color

VSCode Version: Code 1.12.1 (f6868fce3eeb16663840eb82123369dec6077a9b, 2017-05-04T21:18:32.269Z)
OS Version: Darwin x64 16.1.0

Honestly a super small issue from the looks of it.
Steps to Reproduce:

Set colors for (Color should have enough contrast between each other to be able to illustrate issue

    "workbench.colorCustomizations": {
        "focusBorder": "#a3a3a3",
        "dropdown.border": "#00FF00"
    }

Click on a dropdown then click off of it as such

You can see in the colors reference that the dropdown has border-radius: 0

On macos, it does not appear to be the case

The select did not change when I tried to set the  border-radius to 0 through the inspector.

@SidIcarus to be clear, you are describing the issue here that a select dropdown that has a border and also focus shows a little bit of UI glitch due to the border radius on it?

When a dropdown element on macOS gets focus, I am removing the border from the element to avoid this UX clash.


Display milliseconds for each request

I spend a lot of time developing a mobile application against an API, and most of the time my phone is going through mitmproxy.
It would be great if each request showed how milliseconds (or seconds, yikes!) it took each request to come back from the server, so that I could easily keep track of which API endpoints need some optimization attention.
e.g. instead of this:
POST https://p09-ckdatabase.icloud.com/api/client/user/quota
← 200 application/x-protobuf 78B 39.28kB/s
it would look something like this:
POST https://p09-ckdatabase.icloud.com/api/client/user/quota
← 200 application/x-protobuf 78B 39.28kB/s (237ms)
or this:
POST https://p09-ckdatabase.icloud.com/api/client/user/quota
← 200 application/x-protobuf 78B 39.28kB/s (1.32s)
or this:
POST https://p09-ckdatabase.icloud.com/api/client/user/quota
← 200 application/x-protobuf 78B 39.28kB/s (27.9s)
(i.e. three significant digits would be great)

Thanks for the suggestion @cellularmitosis and thanks for the incredibly quick PR, @gato. :smiley: I feel your pain - the web ui we're working on already features a way more detailed view on timing information:

Looking at mitmproxy, we should be careful that we don't clutter the UI with too much information. As it seems, @cortesi removed timing information in an earlier version (https://github.com/mitmproxy/mitmproxy/commit/a2643b52f909719d4e0fe97e17d3d30f43669341) precisely for this reason. Anyhow, I feel that the response time would be more useful than the rate, so maybe we should swap those two. Before we do that, we need to hear why @cortesi initially decided to display the rate only.
Cheers,
Max

Hi Max,
maybe a hotkey can switch between values or as @cortesi has suggested in (a2643b5) this value or more detailed info could be shown only in flowview and not in flowlist.
Just let me know.
Regards.
Marcelo
P.S. new ui looks really good ;)

Hey there,
I had a quick chat with @cortesi tonight. In short, I think we can pick up most points raised in this discussion here. :smiley:

Replace the download rate in the UI with the elapsed time between request.timestamp_start and response.timestamp_end. We then have size + elapsed time in the UI, the download rate could be directly derived.
Additionally, we probably want to provide full timing information in the FlowDetailsView (if someone picks this up, isolated PR please). I think copying the YYYY-MM-DD HH:MM:SS.FFF format would be wise, showing deltas is not strictly neccessary.

@gato, could you please adjust your PR to 1.? :-)
Cheers,
Max

Hi Max!

Done
about number 2 i can do it (obviously not today ;) ) your idea is to add a new urwid's tab (details) like the one in web interface with time information?
Regards.
Marcelo

Great!
Sent from my iPhone

On Mar 1, 2015, at 6:18 PM, Maximilian Hils<EMAIL_ADDRESS>wrote:
Hey there,
I had a quick chat with @cortesi tonight. In short, I think we can pick up most points raised in this discussion here.
Replace the download rate in the UI with the elapsed time between request.timestamp_start and response.timestamp_end. We then have size + elapsed time in the UI, the download rate could be directly derived.
Additionally, we probably want to provide full timing information in the FlowDetailsView (if someone picks this up, isolated PR please). I think copying the YYYY-MM-DD HH:MM:SS.FFF format would be wise, showing deltas is not strictly neccessary.
@gato, could you please adjust your PR to 1.? :-)
Cheers,
Max
—
Reply to this email directly or view it on GitHub.

Hi @mhils !
please discard the second part of my previous comment  I confused FlowDetailsView with FlowView. there is no need to add a tab just reorder some times and add the missing ones. expect a PR soon.
Regards.
Marcelo

Great, thanks. :+1: