backport: No container locks on docker ps

Problem
Our openshift-ci cluster was experiencing both long delays and lockups on docker ps. Investigation shown that, for the lockup case, all the instances of daemon.Container() (the API call producing the list of containers) are waiting for a lock for a particular container which was taken 2+ hours ago and never released. A long delay is also caused by waiting for the same lock, when some other container is performing a long operation (e.g. container creation, which includes selinux relabeling).
A typical waiting goroutine backtrace looks like this:
goroutine 145541 [semacquire, 153 minutes]:
sync.runtime_SemacquireMutex(0xc42031f7a4, 0x0)
        /opt/rh/go-toolset-1.10/root/usr/lib/go-toolset-1.10-golang/src/runtime/sema.go:71 +0x3d
sync.(*Mutex).Lock(0xc42031f7a0)
        /opt/rh/go-toolset-1.10/root/usr/lib/go-toolset-1.10-golang/src/sync/mutex.go:134 +0x108
github.com/docker/docker/daemon.(*Daemon).reducePsContainer(0xc420472200, 0xc42289d400, 0xc4242b6120, 0xc420b3d680, 0x0, 0x0, 0x0)
        /builddir/build/BUILD/docker-b2f74b220126bddbae585cfe2406498ced3ae065/_build/src/github.com/docker/docker/daemon/list.go:202 +0x46
github.com/docker/docker/daemon.(*Daemon).reduceContainers(0xc420472200, 0xc4247c60c0, 0xc420b3d680, 0xc420b3d690, 0x1, 0x424858, 0x40, 0xc4214ce598)
        /builddir/build/BUILD/docker-b2f74b220126bddbae585cfe2406498ced3ae065/_build/src/github.com/docker/docker/daemon/list.go:184 +0x12e
github.com/docker/docker/daemon.(*Daemon).Containers(0xc420472200, 0xc4247c60c0, 0x0, 0x0, 0x0, 0xed4d7ae6870956f6, 0x424858)
        /builddir/build/BUILD/docker-b2f74b220126bddbae585cfe2406498ced3ae065/_build/src/github.com/docker/docker/daemon/list.go:107 +0x54
......

Root cause
Alas, I was unable to find a place in the code which acquired but not released the lock, since there are way too many places like that in the code (and I'm still looking). Still, even if the bug will be found, docker ps can easily be stuck for a few minutes, since many container operations take this lock for this time.
A container being created got stuck on getdents(2) in the middle of selinux relabeling. This is most probably a volume on a networked block device (provided by GCE).
daemon.(*Daemon).containerStart() holds a per-container lock for the duration of the container creation.
Here's an except from dockerd goroutine dump:
goroutine 145539 [syscall, 138 minutes]:
syscall.Syscall(0xd9, 0x8a, 0xc423880000, 0x1000, 0xc4204f1200, 0xc4224c2c80, 0x640)
        /opt/rh/go-toolset-1.10/root/usr/lib/go-toolset-1.10-golang/src/syscall/asm_linux_amd64.s:18 +0x5
syscall.Getdents(0x8a, 0xc423880000, 0x1000, 0x1000, 0xc42576bc38, 0x18, 0xc42576bc30)
        /opt/rh/go-toolset-1.10/root/usr/lib/go-toolset-1.10-golang/src/syscall/zsyscall_linux_amd64.go:482 +0x5f
syscall.ReadDirent(0x8a, 0xc423880000, 0x1000, 0x1000, 0x15ccce0, 0x100000000000001, 0xc422a2dc00)
        /opt/rh/go-toolset-1.10/root/usr/lib/go-toolset-1.10-golang/src/syscall/syscall_linux.go:772 +0x49
internal/poll.(*FD).ReadDirent(0xc4219865a0, 0xc423880000, 0x1000, 0x1000, 0x0, 0x0, 0x0)
        /opt/rh/go-toolset-1.10/root/usr/lib/go-toolset-1.10-golang/src/internal/poll/fd_unix.go:404 +0xad
os.(*File).readdirnames(0xc42619ab40, 0xffffffffffffffff, 0x0, 0x0, 0xc42619ab40, 0x0, 0x0)
        /opt/rh/go-toolset-1.10/root/usr/lib/go-toolset-1.10-golang/src/os/dir_unix.go:67 +0x1bf
<...skipped....>
path/filepath.Walk(0xc4203fd400, 0x97, 0xc420ff4940, 0x0, 0xc42338c6d8)
        /opt/rh/go-toolset-1.10/root/usr/lib/go-toolset-1.10-golang/src/path/filepath/path.go:403 +0x106
github.com/docker/docker/vendor/github.com/opencontainers/runc/libcontainer/selinux.Chcon(0xc4203fd400, 0x97, 0xc421d6c510, 0x2f, 0x25aa601, 0x6e, 0x28)
        /builddir/build/BUILD/docker-b2f74b220126bddbae585cfe2406498ced3ae065/_build/src/github.com/docker/docker/vendor/github.com/opencontainers/runc/libcontainer/selinux/selinux.go:482 +0xc3
github.com/docker/docker/vendor/github.com/opencontainers/runc/libcontainer/label.Relabel(0xc4203fd400, 0x97, 0xc421d6c510, 0x2f, 0x0, 0x0, 0x0)
        /builddir/build/BUILD/docker-b2f74b220126bddbae585cfe2406498ced3ae065/_build/src/github.com/docker/docker/vendor/github.com/opencontainers/runc/libcontainer/label/label_selinux.go:146 +0x1fb
github.com/docker/docker/volume.(*MountPoint).Setup.func1(0xc42338c908, 0xc4227a3680, 0xc42576c8f8, 0xc421d6c510, 0x2f)
        /builddir/build/BUILD/docker-b2f74b220126bddbae585cfe2406498ced3ae065/_build/src/github.com/docker/docker/volume/volume.go:139 +0x1e0
github.com/docker/docker/volume.(*MountPoint).Setup(0xc4227a3680, 0xc421d6c510, 0x2f, 0x0, 0x0, 0xc4270424c0, 0xc4247ca790, 0x97, 0x0, 0x0)
        /builddir/build/BUILD/docker-b2f74b220126bddbae585cfe2406498ced3ae065/_build/src/github.com/docker/docker/volume/volume.go:187 +0x447
github.com/docker/docker/daemon.(*Daemon).setupMounts(0xc420472200, 0xc42289d400, 0x0, 0x0, 0x0, 0x0, 0x0)
        /builddir/build/BUILD/docker-b2f74b220126bddbae585cfe2406498ced3ae065/_build/src/github.com/docker/docker/daemon/volumes_unix.go:58 +0x3be
github.com/docker/docker/daemon.(*Daemon).createSpec(0xc420472200, 0xc42289d400, 0x0, 0x0, 0xc420472200)
        /builddir/build/BUILD/docker-b2f74b220126bddbae585cfe2406498ced3ae065/_build/src/github.com/docker/docker/daemon/oci_linux.go:703 +0xab2
github.com/docker/docker/daemon.(*Daemon).containerStart(0xc420472200, 0xc42289d400, 0x0, 0x0, 0x0, 0x0, 0x1, 0x0, 0x0)
        /builddir/build/BUILD/docker-b2f74b220126bddbae585cfe2406498ced3ae065/_build/src/github.com/docker/docker/daemon/start.go:149 +0x25d
github.com/docker/docker/daemon.(*Daemon).ContainerStart(0xc420472200, 0xc42565eb07, 0x40, 0x0, 0x0, 0x0, 0x0, 0x0, 0x424858, 0x10)
        /builddir/build/BUILD/docker-b2f74b220126bddbae585cfe2406498ced3ae065/_build/src/github.com/docker/docker/daemon/start.go:87 +0x195

Solution
It was not a great idea in the first place to take per-container locks for such frequently used and critical operation like docker ps. Thus here is a backport of upstream PR https://github.com/moby/moby/pull/31273 which removed the lock. It does not resolves the root cause (lock being held forever in case of I/O operation being stuck) but fixes the bad consequences (docker ps being stuck).
Backport details
This was not an easy backport. Most of the merge conflicts were caused by old codebase here, but there were some caused by commits in this repo missed from upstream. Every cherry-pick that resulted in conflicts has them documented in the commit message.
The main strategy was to skip porting most of the preceding PRs and resolve the merge conflicts manually.
Skipped PRs
These PRs were looked at carefully but not backported. The list is not complete, the order is random.

https://github.com/moby/moby/pull/30117
https://github.com/moby/moby/pull/29289
https://github.com/moby/moby/pull/31996
https://github.com/moby/moby/pull/32687
https://github.com/moby/moby/pull/30117
https://github.com/moby/moby/pull/27557
https://github.com/moby/moby/pull/33241
https://github.com/moby/moby/pull/33241
https://github.com/moby/moby/pull/32336
https://github.com/moby/moby/pull/29226
https://github.com/moby/moby/pull/29963
https://github.com/moby/moby/pull/29683

Ported PRs
These were analysed and deemed to be a necessary prerequisites for the PR being backported.

https://github.com/moby/moby/pull/30208 Remove sqlite dependency
https://github.com/moby/moby/pull/30753 remove Register return value
https://github.com/moby/moby/pull/29554 Use counter for tracking container states
https://github.com/moby/moby/pull/30618 Fix some data races
https://github.com/moby/moby/pull/31159 Don’t hold container lock for size calculation
https://github.com/moby/moby/pull/33456 Lock container while connecting to a new network
https://github.com/moby/moby/pull/31083 fix some typos from module contrib to man
https://github.com/moby/moby/pull/32821 Fix issue backporting mount spec to pre-1.13 obj
https://github.com/moby/moby/pull/33209 Add continue on error in mountspec backport

Finally:

https://github.com/moby/moby/pull/31273 No container locks on docker ps

That'd be nice to run CI overnight (at least to see the beast compiles)

@rhatdan PTAL

@kolyshkin Were you able to run and smoke test this locally? We can ask for a auto-test run for a scratch build of this run.

LGTM

Update: found a root cause, updated the description. This PR is still a valid workaround.
A solution would be to cancel container creation upon a timeout

A solution would be to cancel container creation upon a timeout

Which, of course, is also a workaround, just more targeted.

Minor updates to PR description.
A docker build with this PR was tested by QE team (they have some smoke tests under their belt), and also live-tested in a production environment (OC CI cluster doing search). The issue appears to be resolved, and no regressions were observed.
@mrunalp PTAL

LGTM

is it also backported to docker-1.13.1 (centos 7)?
I've installed v1.13.1-203 and I'm still facing this issue.

is it also backported to docker-1.13.1 (centos 7)?
I've installed v1.13.1-203 and I'm still facing this issue.


Advisory from Netsparker - Ponzu CMS - 0.9.4

Hello,
While testing the Netsparker web application security scanner we identified vulnerabilities in Ponzu CMS. Can you please advise whom shall we contact to disclose the vulnerability details so it can be fixed?
Please email me at<EMAIL_ADDRESS>for the technical details.
Looking forward to hearing from you.
Regards,
Daniel Bishtawi
Marketing Administrator | Netsparker Web Application Security Scanner

Emailed. Thank you!


Add a generic wrapper for forecasting classes.

Issue
This is a base class where raw stream of inputs x are transformed into a data stream x, y1,y2,...,yk where k is defined as a parameter to the number of steps to forecast and the training is done such as (x=x[t-1], y=x[t+k]) at moment t. Also training of the model is trivial to the user.
Changes proposed in this pull request:

A new base class for forecasting.

Checklist

[ ] Code complies with PEP-8 and is consistent with the framework.
[ ] Code is properly documented.
[ ] Tests are included for new functionality or updated accordingly.
[ ] Travis CI build passes with no errors.
[ ] Test Coverage is maintained (threshold is -0.2%).
[ ] Files changed (update, add, delete) are in the PR's scope (no extra files are included).

Thanks for the PR @mertozer94
Pinging @jmread to get feedback on this.
Note: codcov error is due to missing tests for the new code.

This looks promising!
In your comment above, I think you mean (x=x[t-1], y=x[t+k])? (To take into account k). Or you do mean (x=x[t-k:t-1], y=x[t]). Or a combination of these (there is one k or two?).

Thanks for the PR @mertozer94
Pinging @jmread to get feedback on this.
Note: codcov error is due to missing tests for the new code.

Thanks for the advice I will add some test cases as soon as possible. Also next time I will try to run locally 'codecov' but are there any other things that I should better check before pushing my commits? Like code coverage etc .

This looks promising!
In your comment above, I think you mean (x=x[t-1], y=x[t+k])? (To take into account k). Or you do mean (x=x[t-k:t-1], y=x[t]). Or a combination of these (there is one k or two?).

Thank you for the response. You are right, I meant (x=x[t-1], y=x[t+k]). I will modify it right now. But I am open for discussion on this subject.

This looks promising!
In your comment above, I think you mean (x=x[t-1], y=x[t+k])? (To take into account k). Or you do mean (x=x[t-k:t-1], y=x[t]). Or a combination of these (there is one k or two?).

Thank you for the response. You are right, I meant (x=x[t-1], y=x[t+k]). I will modify it right now. But I am open for discussion on this subject.

Actually, I think I have responded a bit quickly. What I had in my mind first was the training was done via (x=x[t-1], y=x[t]), and since I was thinking that forecasting was basically k times predicting the next value we could simply call predict function repeatedly k times. I now see that this is not possible.
I realize that I had in mind (x=x[t-k:t-1], y=x[t]). As I said, I am open for discussion on this one.

I realize that I had in mind (x=x[t-k:t-1], y=x[t]). As I said, I am open for discussion on this one.

I think the most generic option is (x=x[t-k:t-1], y=x[t::t+l]) to allow multi-step forecasting into the future since multi-output learning is also an integral part of scikit-multiflow (of course, l=1 would be a nice default). But maybe the t:t+l part could be an extension of the wrapper.

I realize that I had in mind (x=x[t-k:t-1], y=x[t]). As I said, I am open for discussion on this one.

I think the most generic option is (x=x[t-k:t-1], y=x[t::t+l]) to allow multi-step forecasting into the future since multi-output learning is also an integral part of scikit-multiflow (of course, l=1 would be a nice default). But maybe the t:t+l part could be an extension of the wrapper.

I agree that this is more generalized. But this means that, users needs to specify k and l before the training phase. Like you said, if they are not present, we can have some default values for them.

I agree that this is more generalized. But this means that, users needs to specify k and l before the training phase. Like you said, if they are not present, we can have some default values for them.

Yes, I believe that k=1 and l=1 will make good defaults.
There are numerous options that could be considered to extend this even further. For example, y=x[t+l] (a single, but long-range forecast). This has some relation to delayed labels. But this kind of flexibility could be added later. Even the simplest case with k=1,l=1 will open up many possibilities for the framework leveraging existing methods.

Hey @jmread, I have included changes. Although, for the unit test, I can only imagine to test it via it's sub classes. Do you have any recommendation on that?

Hey @jmread, I have included changes. Although, for the unit test, I can only imagine to test it via it's sub classes. Do you have any recommendation on that?

Other than testing the handling of different values for the parameters k, l, indeed most of the testing can be done with the actual methods employed for the forecasting.

Hey @jmread, I have included changes. Although, for the unit test, I can only imagine to test it via it's sub classes. Do you have any recommendation on that?

Other than testing the handling of different values for the parameters k, l, indeed most of the testing can be done with the actual methods employed for the forecasting.

I have added unit tests without creating a subclass.

Hello @jacobmontiel @jmread It's been a long time, but do you have any idea on how we can improve the code coverage ?

Hey @jmread, I have included changes. Although, for the unit test, I can only imagine to test it via it's sub classes. Do you have any recommendation on that?

Other than testing the handling of different values for the parameters k, l, indeed most of the testing can be done with the actual methods employed for the forecasting.

I have added unit tests without creating a subclass.

@mertozer94 Can you share a sample code for the forecasting model which can handle stream data in an online fashion and is compatible with other functions of multiflow, like DriftDetectors?

@mertozer94 I am unable to checkout this commit, throws out a "fatal:reference is not a tree" error while using the correct sha. Can someone help?


[contracts] Add integrity checks by pallet hook

The following integrity checks are added:

For MaxCodeLen and CallStack::len() values, as they should be consistent with runtime heap memory limits,
For MaxDebugBufferLen, as it should be large enough to hold debug output from a single contract
(not needed anymore since too large messages simply won't be put into the debug buffer)

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2257231

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2269986

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2270130

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2271548

CI fails on the integrity_check() which is what we want for the improperly configured pallet CallStack and MaxCodeLen. Should become green once the node runtime is updated.

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2272894

bot merge


Request: disableTouchControl() and enableTouchControl() methods

As mentioned in this issue, I think it would a pretty useful feature to disable user swiping controls, without "locking the swiper entirely."  Currently, .lockSwipes() seems to work by completely preventing all slide changes, even those triggered from the API using the .slideTo() method.  What would be useful is a method that would prevent the user from sliding, but still enable the developer to programmatically move slides in the swiper.  I feel like an API that mimics .disableKeyboardControl() and enableKeyboardControl() would fit in nicely with the available methods.

So I figured out that modifying the param onlyExternal like so:
s.params.onlyExternal = true; //or false, if you so desire
Since this is so simple, I think I'll make a PR implementing these methods for consistency, if you don't mind.

Thanks, closed by #1674


Update sensor

Update sensor to be able to use this configuration in configuration.yaml
sensor:

platform: elektro_network_tariff

Thank you for your help. I've tested component and it should work now. Please report if something is missing/not working!


Update rank scoring for it to always show FC when there are no misses and show SS when 100% accuracy

IMO it should say something like PERFECT or SS when it's perfect and it should always show FC when there are no misses as it it is still a full combo

naw


⚠ Bofrost.fr has degraded performance

In 163d9bb, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1253 ms

Resolved: Bofrost.fr performance has improved in a0d0b8c.


Refactor/accept spdx expressions

Description
Accept SDPX expressions for both satisfies arguments
Related Issue

Motivation and Context
The original package doesn't allow second to be a SPDX expression, only a list of simple licenses. Users may want to compare plain SDPX expressions instead
How Has This Been Tested?
Added new tests with Jest. Cases are included in test/cases.js
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[X] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[X] My code follows the code style of this project.
[X] My change requires a change to the documentation.
[X] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTING document.
[X] I have added tests to cover my changes.
[ ] All new and existing tests passed.

I'm fine with removing the second element as an array. This is not our use case and it would be as easy as passing a string with licenses separated by OR or AND. 🆒

@nanotower I have other functions in mind. Coming on the next PR

I'm fine with removing the second element as an array. This is not our use case and it would be as easy as passing a string with licenses separated by OR or AND. 🆒

@nanotower I have other functions in mind. Coming on the next PR

I've decided to do it in this PR.

@all-contributors please add @neodmy for code,doc,test

@all-contributors please add @nanotower for review

https://github.com/all-contributors please add @inigomarquinez  for review


fix a NPE with nested writeOnlyProperties with optional parent.

Issue #, if available:
Description of changes:
Change the removeProperty function to catch NullPointerException, as this implies the parent object was null when removing a nested property. This function is intended to take no action when the property to be removed was null, so it should take no action in this case as well.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Updated to use optional so we don't swallow any unexpected exceptions.


Traefik returns 504 during Kubernetes rollout

Do you want to request a feature or report a bug?

Bug

What did you do?
During high traffic peaks and a kubernetes rollout of an app, Traefik returns 504
I was able to reproduce this issue running load tests with k6
import { check } from 'k6';
import http from 'k6/http';

export default function() {
  let res = http.get('https://myapp.info/ping');
  check(res, {
    'is status 200': (r) => r.status === 200,
    'is status 504': (r) => r.status === 504,
  });
}

k6 run --vus 5 -d 80s k6.js

Execute
kubectl rollout deploy/my-app

The results I get running the load tests when
    ✗ is status 200
     ↳  97% — ✓ 474 / ✗ 12
    ✗ is status 504
     ↳  0% — ✓ 4 / ✗ 482

some requests unfortunately fail.

What did you expect to see?
I would expect to see all requests get 200.
What did you see instead?
Part of the requests return 504.
Output of traefik version: (What version of Traefik are you using?)
1.7.19

What is your environment & configuration (arguments, toml, provider, platform, ...)?
Kubernetes (kops) 1.16.10
Traefik deployed via official Helm chart version traefik-1.82.1
    # traefik.toml
    logLevel = "info"
    defaultEntryPoints = ["http", "httpn"]
    [entryPoints]
      [entryPoints.http]
      address = ":80"
      compress = true
      [entryPoints.httpn]
      address = ":8880"
      compress = true
      [entryPoints.prometheus]
      address = ":9100"
    [ping]
    entryPoint = "http"
    [kubernetes]
    ingressClass = "traefik-info"
      [kubernetes.ingressEndpoint]
      publishedService = "kube-system/reverse-proxy-traefik"
    [traefikLog]
      format = "json"
    [accessLog]
      format = "json"
    [accessLog.fields]
      defaultMode = "keep"
    [accessLog.fields.names]
    [accessLog.fields.headers]
      defaultMode = "keep"
    [accessLog.fields.headers.names]
    [metrics]
      [metrics.prometheus]
        entryPoint = "prometheus"

Important info to add. CNI running Cilum

Apologies here for the duplicated. I have found the issue already discussed in here https://github.com/containous/traefik/issues/4452#issuecomment-459931923
Closing but if anyone wants to add anything here, feel free ;-)


Fix: CapRover Dashboard App: Details of Workers disappear after few seconds

Description
Fix listing Caprover workers
Changes

Send both of the deployments, leader, and workers.
Call the 'getGrafanaUrl' on mount the component.

Related Issues

https://github.com/threefoldtech/tfgrid-sdk-ts/issues/3281

Screenshots/Videos
Screencast from 09-03-2024 05:27:14 PM.webm

Checklist

[ ] Tests included
[ ] Build pass
[ ] Documentation
[ ] Code format and docstrings
[ ] Screenshots/Video attached (needed for UI changes)

I was able to list and delete all workers fine, but on adding new one i got this error

This happened because the worker is listed instead of the master, which is wrong

Now listing works fine as it lists the leader not the worker, however, on adding another worker after deploying, I faced this error.

This issue isn't related to my PR, it could be another issue

Why is most of the code separated into different function and only used once, for example prepareForDeletion and finalizeDeletion. Is it because this's cleaner code somehow??

I deployed a cluster and added two workers successfully. Listing of workers is fine

However on shoe details, workers are not shown

@zaelgohary
Working well with me, please make sure that you have the latest code and do  yarn && make build
https://github.com/user-attachments/assets/21131a58-1886-4db6-b3ec-89e1c52046e8

Working well with me, please make sure that you have the latest code and do yarn && make build
Screencast.from.2024-09-24.15-13-48.mp4

Can you click on show details as the error appears once clicking it?

Workers are being showed as leaders in contracts page.

I deleted the caprover deployment but 1 network contract still exist after deletion. Happened more than once.

Workers are being showed as leaders in contracts page.

@zaelgohary In the contracts, all the cluster's workers carry the same name as the cluster (which is the leader name) so we can list them as part of the cluster

I deleted the caprover deployment but 1 network contract still exist after deletion. Happened more than once.

It's a known issue i think https://github.com/threefoldtech/tfgrid-sdk-ts/issues/3425

I deleted the caprover deployment but 1 network contract still exist after deletion. Happened more than once.

It's a known issue i think #3425

It's not. It was fixed in https://github.com/threefoldtech/tfgrid-sdk-ts/pull/3456 which was merged yesterday. Can you merge development to your branch?

The issue is already solved yeah, I just noticed that I have to build the client first

However, yeah one contract still exists and should be deleted!
https://github.com/threefoldtech/tfgrid-sdk-ts/issues/3473

I deployed a new instance & whenever I view its details I get the following error:

I also got the same error when deleting a worker.

I tried adding workers most of the times it passed, but it failed once. Deletion works fine


Updated for meteor 1.3 / 1.4 closes #71

Tested on Meteor <IP_ADDRESS> Would like to know if anyone out there can give it a shot on 1.3
Also this includes the fix for Modulus production directory (closed previous PR). We have been using this forked version in production since Meteor 1.2 and are getting ready to move from 1.3 to <IP_ADDRESS>
No error in the console:

Test email received:

Thanks! One problem is that this makes Sass non opt-in. I.e. the Npm.depends() in package.js creates a hard dependency on node-sass, which before was solved with weak: true for Chris Butler's node-sass Meteor package.
Is there a pro to rely on the node-sass npm package directly?


Simplify CMake

Simplify the CMakefile.txt to make it easier to maintain. Remove visual studio solution files as they are not necessary and hard to maintain properly.
I also converted the library to build as a static library. This is because the DLL being generated on windows was not exporting symbols properly. I can add proper support for shared vs static building in a later pull request.
I added compiler flags to Visual Studio builds to match the warnings as errors flags on non-VS builds.

Thanks Nicolas.
I've merged your changes which look just fine.
Howevr, I'm a complete novice with CMake so there's an element of trust there 😁😱🤞🙏.
And on that note, how do I get CMake to generate solution file that Visual Studio can compile and execute to examples.
I'm sure there are online examples re CMake in VS but I'm hoping you can provide a "quick and dirty" explanation that's specific to your modified CMakeLists.txt.  I've gotten as far as
option(CLIPPER2_UTILS "Build utilities" ON)
option(CLIPPER2_EXAMPLES "Build examples" ON)
option(CLIPPER2_TESTS "Build tests" ON)

but no further. Cheers.


Improve Arabic Localization: Spelling, Terminology, and Date Format Adjustments

The following changes were made:
Spelling Corrections:
    Fixed common spelling errors, such as:
        "أضافة" to "إضافة"
        "الغاء" to "إلغاء"
        "إختر" to "اختر"
        "يحتوى" to "يحتوي"
        "مساءاً" to "مساءً"
        "قيد الإنتظار" to "قيد الانتظار"

Terminology Standardization:
    Updated technical terms to use more common Arabic equivalents:
        "ميجا بايت" changed to "ميغابايت"
        "جيجا بايت" changed to "غيغابايت"
        "تيرا بايت" changed to "تيرابايت"
    Unified month and day names for consistency.

Date Format Adjustment:
    Changed the date format from "شهر/يوم/سنة" to "yy/mm/dd" to ensure consistency with a more standard international date format, making it easier to handle dates programmatically.

Improved Formatting:
    Standardized the use of Hamza in words, using "إ" where appropriate (e.g., "إظهار"، "إخفاء").
    Adjusted certain phrases for clarity, making the text more natural for native Arabic speakers.
    Consistent usage of certain UI terms like "إلغاء التحديد" instead of "قم بإلغاء التحديد".

1.2.2 has been published to NPM


lsp-dart vs flutter-tools

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Hi,
I am new to Flutter and Dart. Furthermore, I am looking for a Lightway IDE. Which one would you recommend to use:

flutter-tools.nvim or
lsp-dart

Thank you in advance,
Mic
Expected Behavior
Find the best ide
Steps To Reproduce
I searched the internet and can not find a comparison.
Environment
- OS:
- Flutter version:
- Is flutter in $PATH:
- neovim version:

Anything else?
No response

P.S. Is flutter-tools compatible with:

SpaceVim's  Dart/Flutter implementation
Normalnvim's  Dart/Flutter implementation

P.s. Does flutter-tools provide any code snippets?

Its been a month so im guessing you have figured it out by now, if you still need help react to this


raycast: 1.88.3 -> 1.88.4

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

There's already #368171 that upgrades to 1.88.4 and refactors the package and update script

@DontEatOreo Thanks, didn't notice that one. Was just going through and updating packages as I was migrating from homebrew module.

Apologies for approving in error 😅 Will teach me for doing it on my phone.


fixes footer scroll effect #150

fixes #150

fixes scroll effect of footer

Summary by CodeRabbit

Refactor

Simplified the structure of the Footer component for improved layout and positioning.
Removed unnecessary styles, enhancing the overall design and functionality.

doesn't looks good @Sawan-Kushwah


added dark mode

I added dark mode as asked, in all the  pages and also in the resposive feature.
Do review it,

@anushbhatia @ashuydv  There is one issue though. If you are at a page X, you change the theme to dark, then visit page Y, the theme switches back to X. However, it should remain the same.
Moreover, I would suggest to make the default theme as dark

@ashuydv
Feedback:

There is a small bug If you are on page X, you change the theme to dark, then visit page Y, the theme switches back to X. However, it should remain the same.
Moreover, I would suggest making the default theme as the system default.
The research page cards especially the buttons look awkward and need to be rectified
Experience Page lowermost cards (Mentorship) need to be fixed
The color of the scroll bar should be light and dark shades of purple for light and dark themes
Home Page: Medium and Kaggle Icons are faded

cc: @anushbhatia

I think this can be done in the next PR, cause this is enough for the first one. Rest he can enhancement one by one. what say @ashuydv @smaranjitghose

Yes, I'll be trying to make it common , I'll try to make a PR as soon as possible. I noted all the points

@ashuydv Raise a new Issue for the above points and split the work into 2-3 PRs.

okay,


firebase-admin it does not work

NOTE: now-dev It is available in the canary version of now cli
Steps to reproduce 🐛
git clone https://github.com/MAPESO/now-dev-bug-firebase
cd now-dev-bug-firebase
yarn install  # dependency installation
now dev # note the error output

This problem was ncc but it was resolved in this PR https://github.com/zeit/webpack-asset-relocator-loader/pull/12. Even though it now works in ncc the problem still persists innow and now dev
logs
Error: package.json does not exist at /private

Adding the text of the error message to make it easier for people to find...
(node:15004) UnhandledPromiseRejectionWarning: Error: package.json does not exist at /tmp/zeit-fun-0dde8aa1a33/user/api/src/package.json
    at Object.module.exports.exports.find (/tmp/zeit-fun-0dde8aa1a33/user/api/src/decks/index.ts:40129:15)
    at Object.<anonymous> (/tmp/zeit-fun-0dde8aa1a33/user/api/src/decks/index.ts:103259:12)
    at __webpack_require__ (/tmp/zeit-fun-0dde8aa1a33/user/api/src/decks/index.ts:22:30)
    at Object.<anonymous> (/tmp/zeit-fun-0dde8aa1a33/user/api/src/decks/index.ts:65647:12)
    at __webpack_require__ (/tmp/zeit-fun-0dde8aa1a33/user/api/src/decks/index.ts:22:30)
    at Object.module.exports.date.setLocales.MMMM (/tmp/zeit-fun-0dde8aa1a33/user/api/src/decks/index.ts:81670:27)
    at __webpack_require__ (/tmp/zeit-fun-0dde8aa1a33/user/api/src/decks/index.ts:22:30)
    at Object.module.exports.P (/tmp/zeit-fun-0dde8aa1a33/user/api/src/decks/index.ts:207731:14)
    at __webpack_require__ (/tmp/zeit-fun-0dde8aa1a33/user/api/src/decks/index.ts:22:30)
    at Object.module.exports.Object.defineProperty.value (/tmp/zeit-fun-0dde8aa1a33/user/api/src/decks/index.ts:172279:19)
(node:15004) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)

Is there any ETA on when this might get investigated/fixed?

Seems to be fixed as of 15.0.9-canary.1. @MAPESO is it also fixed for you?

Seems to be fixed as of 15.0.9-canary.1. @MAPESO is it also fixed for you?

@betsegaw could you show me an example 🙏

@betsegaw The problem still persists, the difference is that now it does not show any error now dev.

@betsegaw Did you manage to connect to firestore with now dev?

@MAPESO yes it did and I was able to get a reply from local queries just fine. Will try to put together a sample and send it your way. I am using it currently on a private repo so I can't link directly to my project but yeah, latest canary version seems to work for me.

Probably a couple of hours before I get the chance to send it though.

@MAPESO another thing you might check here is if node_modules/google-gax and node_modules/google-proto-files both exist.

@betsegaw

Seems to be fixed as of 15.0.9-canary.1.

I need more information 🙏

This is working for me in 15.1.0, although I don't know which version it was fixed in.
I'm getting these warnings/errors in the terminal, but they don't seem to cause any issues:
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/@firebase/database/dist" attempted to require "request" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/hash-stream-validation" attempted to require "fast-crc32c" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/retry-request" attempted to require "request" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/write-file-atomic" attempted to require "worker_threads" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/google-gax/build/src" attempted to require "@grpc/grpc-js" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/google-gax/build/src" attempted to require "@grpc/grpc-js" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/bytebuffer/dist" attempted to require "memcpy" but could not be resolved, assuming external.

If it's not important, is there a way to silence the message?

This is working for me in 15.1.0, although I don't know which version it was fixed in.
I'm getting these warnings/errors in the terminal, but they don't seem to cause any issues:
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/@firebase/database/dist" attempted to require "request" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/hash-stream-validation" attempted to require "fast-crc32c" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/retry-request" attempted to require "request" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/write-file-atomic" attempted to require "worker_threads" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/google-gax/build/src" attempted to require "@grpc/grpc-js" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/google-gax/build/src" attempted to require "@grpc/grpc-js" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/bytebuffer/dist" attempted to require "memcpy" but could not be resolved, assuming external.

If it's not important, is there a way to silence the message?

works with now dev or now ? I'm aware that in ncc it works

This is working for me in 15.1.0, although I don't know which version it was fixed in.
I'm getting these warnings/errors in the terminal, but they don't seem to cause any issues:
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/@firebase/database/dist" attempted to require "request" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/hash-stream-validation" attempted to require "fast-crc32c" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/retry-request" attempted to require "request" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/write-file-atomic" attempted to require "worker_threads" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/google-gax/build/src" attempted to require "@grpc/grpc-js" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/google-gax/build/src" attempted to require "@grpc/grpc-js" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/bytebuffer/dist" attempted to require "memcpy" but could not be resolved, assuming external.

If it's not important, is there a way to silence the message?

works with now dev or now ? I'm aware that in ncc it works

It's working for me with both now dev and now.

@danoc

This is working for me in 15.1.0, although I don't know which version it was fixed in.
I'm getting these warnings/errors in the terminal, but they don't seem to cause any issues:
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/@firebase/database/dist" attempted to require "request" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/hash-stream-validation" attempted to require "fast-crc32c" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/retry-request" attempted to require "request" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/write-file-atomic" attempted to require "worker_threads" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/google-gax/build/src" attempted to require "@grpc/grpc-js" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/google-gax/build/src" attempted to require "@grpc/grpc-js" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/bytebuffer/dist" attempted to require "memcpy" but could not be resolved, assuming external.

If it's not important, is there a way to silence the message?

Are you still seeing the messages? @danoc : )

@danoc The messages does not provides any value to the user. It would be a good idea to silence these messages

@danoc

This is working for me in 15.1.0, although I don't know which version it was fixed in.
I'm getting these warnings/errors in the terminal, but they don't seem to cause any issues:
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/@firebase/database/dist" attempted to require "request" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/hash-stream-validation" attempted to require "fast-crc32c" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/retry-request" attempted to require "request" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/write-file-atomic" attempted to require "worker_threads" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/google-gax/build/src" attempted to require "@grpc/grpc-js" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/google-gax/build/src" attempted to require "@grpc/grpc-js" but could not be resolved, assuming external.
ncc: Module directory "/private/var/folders/qs/rgfhf56n7pddh_nzcb6ljllh0000gp/T/co.zeit.now/dev/workPaths/sgkdk5vo/node_modules/bytebuffer/dist" attempted to require "memcpy" but could not be resolved, assuming external.

If it's not important, is there a way to silence the message?

Are you still seeing the messages? @danoc : )

Yes! Still seeing the messages. Although perhaps that's an issue for ncc, not now-cli.

Closing because it sounds like the original reported issue sounds like it was resolved.
As for the ncc warnings, the @now/node builder no longer uses ncc, but now uses node-file-trace.
If you are still experiencing any issues, please create a new issue 👍


[OTel SDKs] Automated performance test for OTel SDK to identify SDK performance, CPU and memory bottlenecks.

Automated performance test workflow for AWS OTel Java agent

Build automated performance test using benchmarking
performance test should be run weekly basis
should be able to identify CPU, memory bottlenecks as well as gives insights on API response time and SDK API bottlenecks

Is there anything unique to do here or can we implement this upstream? Even if we want to swap out the agent we publish, I think we should implement this upstream and reuse.

Submitted latency benchmark PR (upstream) - https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/1935

Submitted latency benchmark PR (upstream) - https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/1935


Feature/refactor paths

👋 Thanks for creating a pull request! 🚀 Checkout the storybook we created for it here.


Shift click in bank to eat/drink/equip

Is your feature request related to a problem? Please describe.
With the new eating, drinking & equipment while in the bank, you're required to right-click > eat/drink/equip. Being able to shift+click to perform these actions would be great.
https://secure.runescape.com/m=news/eating-in-the-bank?oldschool=1

Duplicate of #10572


Adding HubConnection State Enum (#2627)

Merging back to master

Let the bot handle it :)
https://github.com/aspnet/SignalR/pull/2643

I thought the bot was there just in case you forgot lol


review and testing codebase

Hi Liliana I try to run one of your python scripts and some dependencies were missing. I added a minimal pyproject.toml with dependencies that were missing, pandas and matplotlib I also removed some python command related to your jupyter notebook which we dont need.

Thanks Jose, tested the suggested changes and works nicely.


possible rust 1.80 build issues

hello i am unable to build this pkg from nixpkgs master branch right now.
i believe it is due to https://github.com/NixOS/nixpkgs/issues/332957
i attempted to confirm this myself, but had a couple issues working through building in general, with cargo wanting a 'wayland-client' to be available. this is likely just because i don't have my enviroment properly setup for building inlyne.
in other packages they suggest updating 'time' but i don't think that is the issue here.

It's possible that there could be issues as the last release looks like it's on an affected time version
❯ cargo tree -p time
time v0.3.29
├── deranged v0.3.8
├── itoa v1.0.9
└── time-core v0.1.2

which predates the PR to time fixing it (0.3.29 was released 7 months ago and the PR was merged 5 months ago), and I can confirm that I'm getting the expected error when trying to build the last inlyne release with a more recent toolchain
   Compiling enumflags2 v0.7.7
   Compiling gpu-descriptor v0.2.3
error[E0282]: type annotations needed for `Box<_>`
  --> /home/wintermute/.cargo/registry/src/index.crates.io-6f17d22bba15001f/time-0.3.29/src/format_description/parse/mod.rs:83:9
   |
83 |     let items = format_items
   |         ^^^^^
...
86 |     Ok(items.into())
   |              ---- type must be known at this point
   |
help: consider giving `items` an explicit type, where the placeholders `_` are specified
   |
83 |     let items: Box<_> = format_items
   |              ++++++++

   Compiling zvariant_derive v3.14.0
   Compiling darling v0.14.4

The main branch here is already updated to the latest time, although I won't be able to get a release out for likely a couple more weeks at least
As per the wayland-client issues that's an expected dep if the wayland feature is enabled which it is by default. There's are details on what dependencies are required in the Building from Souce section of the README

Eh on second thought we already have a branch for 0.4, so I can push out a patch release with an updated time version later today

A new release with an updated time version is now out which @r-ryantm will likely pick up and open a PR to nixpkgs soon to update to the latest version

Went ahead and opened a PR to nixpkgs NixOS/nixpkgs#338369

Closing this as it seems to be resolved


Added language support for PythOwO

Description

This pull request adds language support for PythOwO by virejdasani.
Checklist:

[x] I am associating a language with a new file extension.

[ ] The new extension is used in hundreds of repositories on GitHub.com

Search results for each extension:

https://github.com/search?utf8=✓&type=Code&ref=searchresults&q=extension%3A.pyowo

[x] I have included a real-world usage sample for all extensions added in this PR:

Sample source(s):

[URL to each sample source, if applicable]

Sample license(s):

[ ] I have included a change to the heuristics to distinguish my language from others using the same extension.

[x] I am adding a new language.

[ ] The extension of the new language is used in hundreds of repositories on GitHub.com.

Search results for each extension:

https://github.com/search?utf8=✓&type=Code&ref=searchresults&q=extension%3A.pyowo

[ ] I have included a real-world usage sample for all extensions added in this PR:

Sample source(s):

[URL to each sample source, if applicable]

Sample license(s):

[ ] I have included a syntax highlighting grammar: [URL to grammar repo]
[ ] I have updated the heuristics to distinguish my language from others using the same extension.

[ ] I am fixing a misclassified language

[ ] I have included a new sample for the misclassified language:

Sample source(s):

[URL to each sample source, if applicable]

Sample license(s):

[ ] I have included a change to the heuristics to distinguish my language from others using the same extension.

[ ] I am changing the source of a syntax highlighting grammar

Old: [URL to grammar repo]
New: [URL to grammar repo]

[ ] I am updating a grammar submodule

[ ] I am adding new or changing current functionality

[ ] I have added or updated the tests for the new or changed functionality.

[ ] I am changing the color associated with a language

[ ] I have obtained agreement from the wider language community on this color change.

[URL to public discussion]
[Optional: URL to official branding guidelines for the language]

I'm closing this PR as there are only 19 files with this extension on GitHub. This is a very very very long way from our documented usage requirements and highly unlikely to meet our usage requirements any time soon.


 I hope the code was good enough for this collection (my first pull request).
Thx @floriandd2ba

floriandd2ba<EMAIL_ADDRESS>writes:

Write programs that do one thing and do it well.

The question is what counts as one thing.
We have one 'cat' program, for example, instead
of different ones for each file extension.

Closing in favor of #39. Thank your for contributing @muxueqz, you are credited for the graphviz part of that filter.


Problem with mouse position

I'm having a problem which I've tried to solve in every way possible and I can't quite figure how.
I have a working code that is capable  of correctly identifying where the mouse is clicking and interact with imgui. This code is on dotnet core 3.1. The problem is that when I try to migrate to .net 5, the mouse suddenly starts capturing the wrong x and y.
The working code can be found here.  Simply changing the Shoelace project to .net 5, without changing anything else, causes the problem to appear. Changing all the projects to .net 5 won't work either.
I've tried changing the code to use the Sdl2Window.ScreenToClient() function, and it works if the imgui window is kept within the borders of the main window, but as soon as I change it into a viewport, it stops working again.
Any advice on how to star tackling this problem is of big help! As I've said, I've exhausted my ideas :/

After updating to the latest ImGui.NET version it seems to be working fine, so I'll close this (:


Replace os.path.join calls with "/".join for Windows

On Windows any paths that wind up containing "\n" will result in a broken path with a newline in the middle.
example:
C:\\apps\nuke\gizmos\...

Since Nuke already respects "/" as a separator on all OS's, this commit enforces this.

Even with the suggested update to the cpode, the toolkit doesn't launch for me on Nuke 13 / Windows 10
"File "C:/Users/Username/.nuke/NukeSurvivalToolkit/menu.py", line 18, in
import NST_helper
ValueError: source code string cannot contain null bytes"

This message appears when I open the program and then closes.
"C:/Users/USER/.nuke/init.py : error interpreting this plugin"
please help.

\n should never ever be part of a path.
If you want to ensure a path is correctly formed for your os use os.path.abspath
https://docs.python.org/3/library/os.path.html#os.path.abspath


Added configutation for fetching ErmrestDataUtils repo in travis.yml …

The PR fixes issue related to https://github.com/informatics-isi-edu/chaise/issues/665 and also changes the path in import script to use the local repo instead of using the npm version.

Once we merge this PR everyone needs to clone the ErmrestDataUrtils repo in the same directory where ermrestjs lies.
Considering that you're in ermrestjs directory
# Move to parent directory
$ cd ..

# Clone the ErmrestDatautils repo
$ git clone https://github.com/informatics-isi-edu/ErmrestDataUtils.git

# Install npm dependencies
$ npm install


ISPN-6089 Distributed Stream doesn't operate in parllel locally

Set the stream to parallel right away if a parallel stream was invoked
Set the stream parallel or sequential when retrieving

https://issues.jboss.org/browse/ISPN-6089

Pushed to both master and 8.1.x. Thanks


⚠ Bofrost.lu has degraded performance

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

HTTP code: 200
Response time: 1516 ms

Resolved: Bofrost.lu performance has improved in ce4456d after 16 minutes.


Availability of auto-suggestions not announced to screen readers

The ‘Where’ field displays a list of location suggestions as you type. The suggestions are keyboard accessible using the down arrow key, however the fact that there are auto-suggest options available is not announced to screen readers, so unless the user explores, they won’t know the options exist.
Recommendation
Announce to screen readers that location suggestions are available.
Option 1: Add hidden text as part of the  mentioning that suggestions will appear below the field.

  Where

    Suggestions will appear below the field as you type, use down arrow to navigate to the list

Option 2: Add an aria-live region to announce the availability of the options when the list of options is displayed. Insert the message into the aria-live region when auto-suggest results first appear.

  Location suggestions are available, use the down arrow key to navigate to the list

@kaylajheffernan Option 1 is totally in your control. The  is not part of react-autosuggest.
I had a quick look at the docs of aria-live, and it feels not mature yet.
Do you know how some of the well known sites (e.g. Google) solve this problem?
Also, this accessibility issue seems related. I'd appreciate your feedback on it.

Thanks @moroshko . We'll go with Option 1 then for now.
When I've played with Google & voice over it doesn't announce the auto-suggestions. I guess the difference is that you can enter free text, whereas we have structured data so we really need to be announcing to them the results are there.
Not sure about announcing the number of options in the dropdown. Would it interrupt them as they are typing and the number dynamically changes as matches change?

@kaylajheffernan Good point regarding announcing the number of suggestions. I wonder if there is an official guideline about this.
I'll close this issue for now since you have a workable solution.

I've done some research, because i have to write an accessible autocomplete in vanilla javascript for a client and found that the jQuery UI did this by using an status container:

No search results.

10 results are available, use up and down arrow keys to navigate.

But unfortunately I could not find any best practices guides around this and most of the autocompletes i could find did not announced the number of results.
Therefore right now i'm not using it.
P.S.:
But some screen readers announce the position of the item if the
s are wrapped inside of an ordered list, which i'm going for.

Is this still on the roadmap for future improvements?


Snake Game

Implemented Snake Game play including following features:
1- Smooth Gameplay
2- Snake Movement
3- Food Capturing and Dynamically creating new food
4- Collision detection and game ended
5- Score in console

Should I write complete bot function which gives input for both axis or only for X as discussed.
Here is the code only for X-axis
bot(){
  let bestWay =1;
  let i=1;

  // #1 first way moving in straight left or right {1,0}
  int steps = Math.abs(food.x - this.direction.x);
  // #2 then check if going in the opposite direction and then popping out from there is best way
  if(food.x > this.direction.x && (this.direction.x) + (100-food.x) < steps){
    steps = (this.direction.x) + (100-food.x);
    bestWay++;
  }

  if(food.x < this.direction.x && (100 - this.direction.x) + (food.x) < steps){
    steps = (100 - this.direction.x) + (food.x);
    bestWay++;
  }

  int sign=1;   // x-axis direction sign
  if(bestWay==1){
    if(food.x < this.direction) sign=-1;
    for(i=1;i<=steps;i++)
        console.log("{"+ sign + ", 0}"); //printing co-ordinates
  }
  else{
    if(food.x > this.direction) sign=-1;

    for(i=1;i<=steps;i++){
      console.log("{"+ sign + ", 0}");
      //change sign if it crossed the boundary
      if(food.x < this.direction && (this.direction.x + i) ==100) sign*=-1;
      if(food.x > this.direction && (this.direction.x - i) ==0) sign*=-1;
    }

  }

}

@vso42 please sent a different PR where we can discuss the solution. This PR belongs to somebody else's implementation for a different problem.
Also, we both the axes solutions are needed not just the X axis.

@ghostdsb Thanks for replying, actually I was not able to make a PR, it was asking to be a collaborator first.
I opened a new issue, under that I placed my code for the X-axis


File chooser: creating a new file

Is there a way to specify a file to be created and saved? Obviously clap::ValueHint::FilePath works great for existing files...

Well, you can just write the path manually in the box, but there's no easier way to do it at the moment. But I'm not sure what the best way would be to specify this.
There could be just an additional button on every file path field:

But that seems a bit confusing for a user.
I can't think of any way to specify this through clap. Maybe a settings option that's a Vec<String> where you can specify singular fields which save files and not read them?

Yeah I can't think of any way to specify it through clap, and I've just had a look. From clap's perspective there's no real difference between an input and output path. Short of asking/forking clap to add a ValueHint::NewFile
It's definitely possible with native_dialog_rs to choose a file, so at least that shouldn't be an issue.

So, probably the best course of action would be to add a setting that allows you to specify field purpose. I won't be able to work on this for a few days, but I will try to implement it later.

Sorry for the wait. I've thought about it more, and there are two ways (both kind of hacky) to specify it in clap:

Setting an alias of a field to some value would make it an "input file" field. There's a small chance someone could misspell a field when using the app as CLI and type it by mistake, but it seems unlikely.
Setting a value name to some value would make an "input file" field. This would change the help message displayed by clap.


Merge alisa_development branch with master

Merge branches with master.

Is this merge only merging already approved commits before? Any new change introduced?

This merge is only merging already approved commits.


Edit CSS files makes no effect

When I add a new file in the static folder (/public/css), the new file is not served on my server. For instance, I added a file test.css in /public/css, but it doesn't show up on the static file directory when I inspect element on my localhost page.
I even deleted the whole 'public' folder from the project directory and changed the static references in app.js. The page still contains the static files when I look up 'sources' in 'inspect element'.
My guesses is that the server has some access to the original files in 'public' folder and is not telling the webpage to load from the static folder in my computer.
Thanks for any advice.

When trying to access the content of /public from the web interface, you need to omit /public from the address.  For example if you create a test.css in /public/css , it will be accessible on localhost:8080 as localhost:8080/css/test.css


Using GLSL Version >= 3.0

Sorry I'm new to open inventor. I'm trying to implement a cap-clip-plane function in coin(the original SoClipPlane does not render the clip face) by using stencilbuffer just like threejs and I've already done it in OpenGL 4.6.  So, is there any chance I can do it in the coin? I try    to follow the doc but the shader chapter using glsl with "ftransform" and "gl_ModelViewMatrix". I greatly appreciate any help you can offer.

I can't help with this issue, but I guess freecad developers would love to see this implemented. Maybe there is a possibility to fund this. @luzpaz maybe you can help with getting the right people from freecad connected to this issue?

Maybe @wwmayer ? (sorry for the ping, but perhaps you can weigh-in ?)

Thanks for your reply, maybe I need to generate a clipped new shape before rendering instead of implementing it in rendering pipeline.

@SherSpidey I played with a capping algorithm some years ago. I ended up with this python code:
https://github.com/coin3d/pivy/blob/master/examples/utils/GlClipPlane.py
but I am not sure if this can help you.

Does this help?
https://glbook.gamedev.net/GLBOOK/glbook.gamedev.net/moglgp/advclip.html

@looooo wow, I can really look into it! thanks a lot!!!

@wwmayer Yes! Thanks for your reply~

glClipPlan in coin3d:
https://github.com/coin3d/coin/blob/81dcd9f649ea34be409acbcdacdb877b88f52225/src/elements/GL/SoGLClipPlaneElement.cpp#L142L143

Recently I decided to pick up it again by using pivy, and finally nailed it with the example code GlClipPlane.py! Big thanks to all of you~


Request to include TURBBO on BSSO foundry

The TURBBO project aims to provide tools that will allow you to work with ontologies to define behaviours, input data on the relationship between behaviours, run analyses, and visualise the results to provide robust answers to questions about how behaviours are related.
We currently have a set of ontologies available at https://github.com/fatibaba/turbbo that we wish to include in the BSSO foundry.
TURBBO is structured as three separate components upper.owl, behaviours.owl, and behaviour_properties.owl. These have been combined to form the turbbo.owl. At the moment, adding the turbbo.owl to the BSSO foundry should be sufficient.
PURL: https://purl.org/turbbo/turbbo.owl
Licence: CC BY 4.0
Homepage: https://github.com/fatibaba/turbbo
Contact: Fatima Maikore
Trackers: https://github.com/fatibaba/turbbo/issues
Domain: behavioural science
Thank you.

@fatibaba, thank you so much for your patience. We are working on this now!
I noticed that two potential issues with getting TURBBO to work with the visualisation tool:

the main file turbbo.owl uses imports to include the content from separate development files. This is of course a standard OWL design pattern, however, the library that loads content for the visualisation tool requires (at the moment) that the content be pre-merged. You should be able to programmatically create a merged production release file from the separate development OWL files using the ROBOT merge function. I actually just realised you do have a merged file in the repository. Can we make this the primary file?

The IDs you are using are specific to each file, that is, you are using https://purl.org/turbbo/bp, https://purl.org/turbbo/upper. For the visualisation tool for technical reasons it would be better if there was a single pattern for the IDs and then just the numeric part varied e.g. TURBBO_xxxxxx. I realise this can potentially be more difficult to manage on the tool side across multiple edit files, but perhaps if each file gets a different numeric range within the overall numeric space? Alternatively, we will have to register several different namespaces for the single ontology.

Please let me know what you think - thanks!

@jannahastings Thank you for working on this.
It is alright to use our merged file as the primary file.
Regarding the IDs for the files, we are actually restructuring the ontology at the moment. We want to make it one rather than three separate ontologies and so having the same base ID will make sense. The plan is to use https://purl.org/turbbo_xxx and I like your suggestion to use different numeric ranges to represent the different components of the ontology (we still want to maintain the idea of having separate components to enable independent reuse of those components).
I'll need some time to change the IDs but I'll let you know when it is done. I can see you have already linked the ontology to the BSSO foundry site, thank you for that.
Regards.

Hello @jannahastings,
We have made some updates to the ontology including changing the ID pattern, structure and name of the ontology. Instead of three ontologies, we now have one called RBBO (Relationships Between Behaviours Ontology). RBBO has three modules (formerly the three ontologies).
The main ontology file is now the RBBO.owl (where I have merged all three modules) and the PURL is https://purl.org/turbbo/RBBO.owl. Our new ID pattern is https://purl.org/turbbo/RBBO_xxxxxxx so I think it should be fine now for the visualisation tool.
I guess the PURL and the name of the ontology also needs updating on bssofoundry.org.
Thanks a lot :)

Hallo @fatibaba,
thank you for updating. We were wondering why you choose to store the ontology in Turtle? The visualization tool expects one of the common OWL/XML or RDF/XML formats. Could you provide the ontology in one of these formats?

Thank you for the supplied file. With that, RBBO ist now integrated in the visualization tool. Please take a look and let us know if you spot anything unexpected.

Hello @b-gehrke,
RBBO is looking good in the visualisation tool. Thanks for adding it.
I have a question, if I update our main ontology file so that it imports terms from different sources, will it cause any issues in the visualizer? Our ontology is structured such that we have three components and at the moment we have merged all three into one main OWL file but we want to change this. We want to use the OWL import feature instead to add the different ontology files into the main OWL file that is linked to the visualiser. This is just to make the maintenance easier for us but I worry it might break something in the visualization.


directive not working if draggable="true"

Is there a way to set draggable="true" and to use the v-draggable directive at the same time?

Currently the directive uses the attribute draggable and sets it to true.
So you don't need to set it yourself.

I want to react to the @dragend event because with that event I can pass specific data. The problem is only with the v-draggable directive I'am not able to pass the data.
I want to make something like this: @dragend="drag-end(node.name)"

if you will inspect the element that the v-draggable directive is on, you will see that the draggable attribute is already there.
So the dragend event should work for you.
If it doesn't please share a code so I could better help.

                                              {{ node.name }}

I need every node.name in the for loop but the dragend event in the v-draggable directive isn't in the loop

draggableValue can take an event of [onDragEnd](https://github.com/IsraelZablianov/draggable-vue-directive#ondragend) I suggest that you will make a draggableValue for each node with a different onDragEnd event.
something like:
    const filtered_nodes = [
        {
             node: node1 ,
             draggableValue: {
                  ...baseDraggableValue,
                  onDragEnd: () => {
                      console.log(node1.name);
                  }
             }
        }
    ]

in the template:

  {{ filtered_node.node.name }}

Thank you. I will try


[function2] Add port version 4.0.0

@gjasny thanks for this PR.
What issue does this PR fix? Please open an issue so others may replicate this problem.

What issue does this PR fix? Please open an issue so others may replicate this problem.

I opened issue #9318.
Thanks for reviewing!


Bug: Fix CI on Pull Request

CI is not triggering properly for updates to pull requests. We never updated nextjs repos with our fix for the other repos. Here is what we did to fix this for the android repo:

I'm working on this issue. I would like to learn CI/CD.


Implement a foreign key for subjects

We want to be able to nest subjects and build a hierarchical
relationship between them. This commit does that by adding a database
migration that adds a new column for parent_id and adds a FK
relationship to it.
This approach was discussed in https://github.com/rhmdnd/compserv/issues/84

migrations/000002_add_subject_parent_id.down.sql is supposed to be empty? otherwise looks good to me.

migrations/000002_add_subject_parent_id.down.sql is supposed to be empty? otherwise looks good to me.

No, that should revert the changes added in the corresponding up migration. I'll fix that up before we merge this, but I wanted get this proposal up to get feedback on the FK approach.

migrations/000002_add_subject_parent_id.down.sql is supposed to be empty? otherwise looks good to me.

I added a valid downgrade and test coverage exercising the downgrade.

I think it all looks good, wondering if we need to test the case where parent subject is removed after being referenced?

Yeah - I'll add a test for that today. Thanks for the review!


InfoWindow with 'undefined' title shows up on marker click

Hey,
since I've upgraded to the latest version of cordova-plugin-googlemaps, I have the following issue:
Even if I do not specify any title or text for the marker, the InfoWindow always shows up after clicking on a marker (I do not want to show the standard InfoWindow, but a custom HTML element). Am I missing something?
The content of the marker is undefined.

Could you show me your JS code please? Would like to see how you add the markers.

Confirmed. I will fix it today (there is already a PR for it)

Fixed in master


Update Backlog page

Remove done/won't do items

You can preview this change here:
Built with commit 5f147540a139e658795d597a484a732779ca22a3
https://deploy-preview-387--govuk-design-system-preview.netlify.com


Target collision fix

Adding a new status to the target gives the possibility to have an extra step in the target registration process.
The steps for the ambassador to register the target:

Fetching the identifiers in the NSP Service
Generating a new identifier based on the ones in use
Registering the target to the NSP service with the status as "disabled"
Fetching the identifiers in the NSP Service and checking if there is a collision
If there is: Back to step 2
If there is no: Updating the target status in the NSP service as "enabled"

The load-balancer will configure only the targets which are enabled, the other ones will be ignored or removed if they were existing in the LB.
Fix: #22

It seems fine to me reading your description. At first I wondered if the nsp could take this task. but then I realized that it is better the nsp do not include any state for this.


search: Tell user when there are "no results" because they used stop words.

Related but not quite the same as #7224.
We have 127 stop words, which includes some reasonably uncommon ones. So if you search for something like "what about", we'll return 0 results, since both what and about are stop words.
This makes Zulip search look broken, especially when you then test Zulip's search by sending a message "What about .." and then try searching for it.
Ideally we would just show a small message like "x, y, and z were excluded from the search" somewhere, or maybe strike through the stop words in the search bar.
Implementation-wise:

We'll need have the data for what the stop words are passed to the frontend, probably via direct addition to page_params in zerver/views.home.py
We should add a function in something like search_suggestion.js to check if the search terms overlap with stop words
We add some notice in the search UI (probably in a special error area at the bottom of the suggestions/typeahead dropdown widget?) with the text suggested above.

I don't think it'll be easy to get the postgres backend to report this.  But we could easily make the get_messages backend report this.  Agreed that this should just be an UI-layer check comparing the stopwords list to the set of search terms.

@zulipbot claim

@zulipbot abandon

@zulipbot claim

@zulipbot claim

Reopening, since this doesn't fix the problem if you include a stream name, is:starred, or similar in addition to the stop words. Currently, you get

I think the ideal behavior is:

We show this kind of message for stream narrows, topic narrows, PM narrows, and maybe a few more things like that. (I think we already have special text for starred messages and mentions.)
Basically things you can get to by clicking on stuff.
For anything else, we show the "No search results" type messaging from #11563.

@rishig Could you clarify what the desired behavior is?
Do you mean that we should have the text as follows (for example):
some common words were excluded from your query.
you were looking for: ~what~ ~about~ stop words
Nothing's been sent here yet!
Why not start the conversation?

I was suggesting that it should look exactly like

(so without "Nothings been sent here yet / why not start the conversation")


Missing refactoring files

Thanks @afitz0 & @efortuna for this episode of the Boring show. I enjoyed it.
It seems that you need to push the newly refactored classes :)

🤦🏻♂Classic case of a forgotten git add. Thanks for letting us know (and for watching)!! They should be pushed now.

yah exactly it happens 😃 .. that's why I prefer intellij 😸


[feature] Enable CodeQL scanning

Codecov Report

Merging #1 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #1   +/-   ##
=======================================
  Coverage   52.11%   52.11%
=======================================
  Files           5        5
  Lines         307      307
=======================================
  Hits          160      160
  Misses        135      135
  Partials       12       12

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 d2802ab...24911be. Read the comment docs.


[Gardening] Removed unused field web-address (W)

What's in this pull request?

Removed unused field web-address (W) in CODE_OWNERS.txt.
Resolved bug number: -

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

This field may be used in the future if someone elects to, there is no reason to remove it.

Ah, I thought it could be removed because #2119 also removed some unused fields. Could see adding a web-address be useful in the future, though!


Long posts not displayed fully

Lengthy text posts are truncated when viewed in slide
E.g the following post cuts off at “Wrestlemania 30 - Daniel Bryan v Batista v Randy Orton” rather than displaying the full post
https://www.reddit.com/r/SquaredCircle/comments/85398x/an_indepth_look_at_every_4_star_rated_match_at/

iPhone X iOS 11.3b6 if that makes any difference.
(Incidentally the same post correctly displays in full on Slide for Android).

Fixed for Alpha 5!


Control Flow narrows  X | undefined to never without checking arrow function

TypeScript: 3.1.3
function foo(cb) {
  cb()
}

let h: { a: 1 } | undefined = undefined // required to reproduce this bug
foo(() => h = {} as any)
if (h) {
  console.log(h.a) // <-- h is of type `never`
}

PlayGround
This happens when strictNullChecks is on.

Related #9998

This is a design limitation. See discussion in #9998.

Thanks for the info! As long as this is known, I'm happy about it. 🌷


netstandard 2

Bonjour du Quebec!
Quick question - can we expect netstandard 2 compliance with next release ? it would fix one warning my clients get out of this package and put of source of doubts (when problems arise) away...
Severity	Code	Description	Project	File	Line	Suppression State
Warning	NU1701	Package 'MvvmLightLibs 5.3.0' was restored using '.NETFramework,Version=v4.6.1' instead of the project target framework '.NETStandard,Version=v2.0'. This package may not be fully compatible with your project.	ToDoStudio	C:\Users\erikr\Source\Repos\TodoStudio\ToDoStudio\ToDoStudio\ToDoStudio.csproj	1

I second this, came searching for NETStandard 2.0 support since it's been released.

Hi, there is a preview package available, sew http://mvvmlight.net/std10.
Thanks
Laurent

Tried out the new package and things seem to work fine ! I didn't use the mvvmlight servicelocator pattern (using autofac) and so had no code changes.
Thanks !

Good to know, thanks for the feedback
Sent from my Windows 10 phone
From<EMAIL_ADDRESS>Sent: Thursday, October 26, 2017 8:19
To<EMAIL_ADDRESS>Cc: Laurent<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [lbugnion/mvvmlight] netstandard 2 (#2)
Tried out the new package and things seem to work fine ! I didn't use the mvvmlight servicelocator pattern (using autofac) and so had no code changes.
Thanks !
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/lbugnion/mvvmlight/issues/2#issuecomment-339663051, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEscWYtvvB5_fZHxX5_Ynrmc45LBPlvUks5swIbCgaJpZM4QEjhX.


Added travis ci support for modern node versions

Fixed

LGTM. @chaijs/type-detect team, anyone want to pass comment?

Ahh... for some reason lts/* didn't work. NVM docs say it should do: https://github.com/creationix/nvm#long-term-support. Not sure whats going on here 😞

So nvm 0.31.4 added LTS support (https://github.com/creationix/nvm/releases/tag/v0.31.3), travis is using 0.31.0. There's a PR on travis to update it to 0.31.4 here: https://github.com/travis-ci/travis-build/pull/821.

@keithamus : That PR was merged as it seems - does it fix the issue?

@davelosert @amilajack we need https://github.com/travis-ci/travis-build/pull/821/files to be merged, then this will work.

@keithamus Sorry - i saw the green lights on the bottom of that PR and thought it was merged - but it is still open. Nevermind then - we wait for it to be merged. :+1:
Besides that good work @amilajack :)

@davelosert @keithamus Yay, that PR was merged!
Let's get this party going! 😄

Its working now. Just need sign off from one of @davelosert @lucasfcosta @meeber

Do we want to align Node version numbers with base Chai? If so, then I'd recommend:

0.10 (which as noted will soon be phased out)
0.12
4
6

I'm not a fan of the node alias (replacement for stable which is now deprecated) for this type of project because the moment a new major version is released, our CI automatically stops testing the previous version even if it's still supported. I'm not a fan of lts/* because there are periods of time when there are two LTS versions being supported but that alias only brings in the latest one. It's my current feeling that we should explicitly list all the version numbers currently supported.

@meeber okay, some valid points there - but I also think we need aliases. For example, the Argon LTS release is a moving target, it started as 4.2.0and it's now 4.5.0. We could, I suppose, explicitly add 0.10 and 0.12. I think stable is worthwhile keeping, because it would be a nice assurance that new commits will run on the latest stable build. Perhaps we could do the following then @meeber:
node_js
 - 0.10 # to be removed 2016-10-01
 - 0.12 # to be removed 2016-12-31
 - lts/argon # to be removed 2018-04-01
 - lts/* # (never remove this)
 - stable # (never remove this)

The major version of a LTS release won't change, so lts/argon and 4 are equivalent. I believe the simpler numeric version is clearer, since (at least in my experience) people typically use the numeric version in normal discussion and use. I install "Node 4", I don't install "Node Argon". I ask a colleague if a language feature works in "Node 4", not in "Node Argon".
I don't have a problem including lts/* and node (stable is deprecated). However, I think the current numeric version should also be included, so that testing for a non-LTS version isn't automatically dropped the moment the next version is released. Typically there's a couple month period where the previous non-LTS version is still supported, as was the case with v5 after v6 was released.
By the way, I like having comments.
Counter-proposal:
node_js
 - 0.10 # to be removed 2016-10-01
 - 0.12 # to be removed 2016-12-31
 - 4 # to be removed 2018-04-01
 - 6 # to be removed 2019-04-01
 - lts/* # (never remove this)
 - stable # (never remove this)

Thoughts from others on this?

I think @meeber's point makes sense.
I'd like to keep important major versions (Argon) explicit.
Since lts and node are both moving targets in which we always want to have tests on, I'd keep them too.
IMO the latest suggestion by @meeber seems ideal: both explicit and complete.

Formalizing my thoughts, mostly for future reference:

If there was only ever a total of two versions actively supported, one LTS and one Current, at all times, then the lts/* and node aliases would alone be sufficient. The challenge comes from the planned overlaps that are built into the Node release schedule, causing there to periodically be two LTS or two Current versions actively supported at once. The only way to prevent an actively supported version from being prematurely dropped from automated testing during these periods of overlap is to manually list all actively supported versions. The aliases lts/* and node should still be included as safety nets, ensuring that there's still good (but not perfect) coverage if package maintainers fail to keep on top of manually updating the version list. (Need to verify that if the same version is listed twice, once numerically and once with an alias, it's only tested by Travis once.)

Whether or not to use numeric versions like 4 or aliased versions like lts/argon is merely preference. I prefer the former because I think it more accurately reflects how most people discuss and interact with different Node versions.

Including expiration date comments for each version in .travis.yml is good.

@lucasfcosta @keithamus I just found out that including a release's numeric version and aliased version will cause Travis to run the test suite twice for the same release. Not sure if this behavior is actually problematic in any meaningful way, but it's worth noting.

We've settled on this now, in other repos haven't we @meeber?
@amilajack do you feel happy to update this PR to something like this?

FYI @amilajack - I'm closing this one because I've rebased it to reflect our desired changes - in a new PR over at #96. Thanks for all your efforts here. Sorry it took so long to get this merged!


update doc of with-cte

What type of PR is this?

[ ] Enhancement
[ ] Displaying
[ ] Typo
[x] Doc Request

Which issue(s) this PR fixes:
issue #
https://github.com/matrixorigin/matrixone/issues/9780
What this PR does / why we need it:

限制说明可以按照 sql server 的文档也说明一下
Guidelines for defining and using recursive common table expressions
The following guidelines apply to defining a recursive common table expression:
The recursive CTE definition must contain at least two CTE query definitions, an anchor member and a recursive member. Multiple anchor members and recursive members can be defined; however, all anchor member query definitions must be put before the first recursive member definition. All CTE query definitions are anchor members unless they reference the CTE itself.
Anchor members must be combined by one of these set operators: UNION ALL, UNION, INTERSECT, or EXCEPT. UNION ALL is the only set operator allowed between the last anchor member and first recursive member, and when combining multiple recursive members.
The number of columns in the anchor and recursive members must be the same.
The data type of a column in the recursive member must be the same as the data type of the corresponding column in the anchor member.
The FROM clause of a recursive member must refer only one time to the CTE expression_name.
The following items aren't allowed in the CTE_query_definition of a recursive member:
SELECT DISTINCT
GROUP BY
PIVOT (When the database compatibility level is 110 or higher. See Breaking Changes to Database Engine Features in SQL Server 2016.)
HAVING
Scalar aggregation
TOP
LEFT, RIGHT, OUTER JOIN (INNER JOIN is allowed)
Subqueries

https://learn.microsoft.com/en-us/sql/t-sql/queries/with-common-table-expression-transact-sql?view=sql-server-ver16#guidelines-for-defining-and-using-recursive-common-table-expressions


ytmdesktop: Update to version 2.0.0, switch to nupkg

Since ytmdesktop got a major update from 1.x to 2.x with many changes would like to submit PR for review instead of simply update the version:

switch to nupkg;

update to version 2.0.0;

update license.

[x] I have read the Contributing Guide.

Thank you!
This was on my list of things to look at and get updated in the long list of package managers which can download YTM Desktop


Issue 20257 - Add wait(Pid, Duration) for windows

wait(Pid, Duration) allows to wait until the process terminates
or the timeout expires.
It's currently windows-only because a decent posix implementation
is quite difficult and this allows us to sort out the API beforehand.
CC @andralex as this introduces a new symbol

Good addition though unsure about more platform-specific functionality to Phobos.

Agreed, implementations for other platforms should be added in the future.

Would be good to ensure that it's possible to implement such things on top of Phobos functionality (i.e. using Pid.osHandle).

You mean a generic implementation for other platforms that doesn't depend on os-specific functions?

You mean a generic implementation for other platforms that doesn't depend on os-specific functions?

Not necessarily. I recall that there was some friction with doing some things which are partially doable with std.process. E.g., kill(Pid) would work perfectly fine for processes which are actually not children of the D program, however, there is no way to construct a Pid for an arbitrary process. I think we should try to avoid such situations when possible, and strive for interoperability between the D wrappers and the low-level C/OS API. In this case, that would be ensuring that this feature is implementable on top of std.process, which I think is the case thanks to Pid exposing osHandle.

There's not a portable option for Linux AFAIK. You need to use signals with another thread which can send the signal. I don't know if this is something we would want to implement in Phobos. I doubt there are going to be any advancements in Linux/Unix that allow for a wait with a timeout.
So if we add this, it will likely be permanently Windows-only. And I think that's fine, we should expose the OS functionality available for the OS you are using. For example, we have config options which are OS specific (though those are just ignored on other OSes).

Hm... I take it back (a bit), SIGALRM can be used without threads to implement this. So perhaps it is possible.

Hm... I take it back (a bit), SIGALRM can be used without threads to implement this. So perhaps it is possible.

Internet says SIGALRM is a bad idea due to race conditions.
BTW, this task is achievable in a cross-platform manner without any changes in Phobos by creating a pipe and passing one end to the process, and then using select or equivalent with a timeout on the other end to wait until the pipe is closed. (The pipe handle will be propagated to further child processes, which may or may not be what is needed.)

It highly depends on the child process. The process could close the pipe without exiting because it doesn't plan to do any output.
So I don't think it's portable for all situations.

Internet says SIGALRM is a bad idea due to race conditions.

Yeah, the more I look at it, the less nice it looks.

The process could close the pipe without exiting because it doesn't plan to do any output.

It doesn't have to be STDOUT_FILENO, can be an arbitrary handle. But, your point does still stand, the process technically could iterate over open fds and close them - I imagine some programs do that as part of daemonification.

Could also consider sigtimedwait, e.g. as proposed here

How about a control loop with Thread.sleep() ? This is actually what I occasionaly use when I have to do a non blocking wait on several Pid.

Busy waiting is inefficient because the parent keeps consuming resources and also imprecise because you wait way too long depending on your sleep duration.
I could kinda see it as an "if all else fails" solution but i don't think it's appropriate for phobos.

sigtimedwait probably isn't usable, that example doesn't seem to account for the possibility of waiting for a specific child, or in a thread.

I think the idea is that after every SIGCHLD, you check (as in tryWait) to see if it is the waited-on process which exited, or something else.

I would expect the SIGCHLD to immediately re-fire if you don't wait for the child that caused the signal. Is that not true?

Sorry, I don't know. You may be right.

Anybody got an idea how to fix LDC-Win32 on Azure?
.\unittest.exe
ERROR: Input redirection is not supported, exiting the process immediately.

@MoonlightSentinel Maybe it was a spurious failure? Maybe you can rebase this and see what the autotester has to say?

 I'll try a different test case (wait is problematic because Microsoft apparently changed the CLI interface between some versions ...)


Manjaro KDE не работает layout_changing_previous.sh

layout_changing_previous.sh
it doesn't work on manjaro, instead it inserts text from the buffer, maybe there are suggestions why this is so?

UPD, it turns out it works

UPD, it turns out it works

Please tell me how to make it work on Manzhdaro? My menu with key combinations does not see scripts