Buildx runners are not reused

Buildx runners are hanging unused after execution finishes. There should be cleanup of them on the final part of the execution.

Im not sure what do you mean by "hanging unused".  Can you explain it a bit more?

[opc@oracle ~]$ docker container ls
CONTAINER ID   IMAGE                           COMMAND                  CREATED              STATUS              PORTS                                                                                NAMES
e043e467abdd   moby/buildkit:buildx-stable-1   "buildkitd"              About a minute ago   Up About a minute                                                                                buildx_buildkit_festive_sanderson0
0239fbce7b4e   moby/buildkit:buildx-stable-1   "buildkitd"              10 minutes ago       Up 10 minutes                                                                                buildx_buildkit_pensive_boyd0
2a975179381f   moby/buildkit:buildx-stable-1   "buildkitd"              14 minutes ago       Up 14 minutes                                                                                buildx_buildkit_ecstatic_edison0
812c03b6bf8f   moby/buildkit:buildx-stable-1   "buildkitd"              20 minutes ago       Up 20 minutes                                                                                buildx_buildkit_busy_volhard0
08f4f8d89b92   moby/buildkit:buildx-stable-1   "buildkitd"              24 minutes ago       Up 24 minutes                                                                                buildx_buildkit_great_swirles0
fc92a115007c   moby/buildkit:buildx-stable-1   "buildkitd"              29 minutes ago       Up 29 minutes                                                                                buildx_buildkit_unruffled_almeida0
df01615319d8   moby/buildkit:buildx-stable-1   "buildkitd"              2 hours ago          Up 2 hours                                                                                buildx_buildkit_cranky_mclaren0
9c7be84aa8fe   fb1d84dcf0bb                    "/bin/drone-server"      2 hours ago          Up 2 hours          <IP_ADDRESS>:8002->80/tcp, :::8002->80/tcp, <IP_ADDRESS>:9002->443/tcp, :::9002->443/tcp                   drone_server_1
3b5509f217a0   c7496fe41b92                    "/bin/drone-runner-d…"   2 hours ago          Up 2 hours          <IP_ADDRESS>:3000->3000/tcp, :::3000->3000/tcp                                                        drone_runner_1

I have only single runner and single server. I enabled only one project, and it is running only one pipeline with drone-docker-buildx. Every new run creates new buildkit container that is neither removed nor used again.

Im confused, it looks like you use moby/buildkit:buildx-stable-1 which is a completely different image that is not related to this repo.

That's the repo: https://github.com/Shanduur/ddgo
Here is my Drone instance: http://<IP_ADDRESS>:8002/Shanduur/ddgo
As you can see in the .dorne.yml, I am using correct image:
kind: pipeline
type: docker
name: build

platform:
  os: linux
  arch: arm64

steps:
- name: publish
  image: thegeeklab/drone-docker-buildx
  privileged: true
  volumes:
  - name: docker
    path: /var/run/docker.sock
  settings:
    platforms:
      - linux/arm64
      - linux/amd64
    repo: shanduur/ddgo
    tags: [ "${DRONE_COMMIT_SHA:0:7}", "latest" ]
    username:
      from_secret: docker_username
    password:
      from_secret: docker_password

volumes:
- name: docker
  host:
    path: /var/run/docker.sock

moby/buildx is how the docker builds multiarch images, you are creating runner in this function (docker.go:55-65) and executed here (impl.go:164)

Got it, thanks for the link to your drone config. I guess the issue is that you expose your hosts docker socket to the container https://github.com/Shanduur/ddgo/blob/main/.drone.yml#L13-L15.
That's not required and result in "bypassing" dind and the moby/buildkit build container is created on your host instead inside the plugin container. The main concept of Drone it to keep pipeline steps isolated. Is there a reason why you pass the docker socket to the step?

@xoxys it's due to the fact, that I can't manage to get it to work otherwise:
latest: Pulling from thegeeklab/drone-docker-buildx
Digest: sha256:14405f6c4134a3adc8bbaca63289d923d244c37301aee771573ef1e2261303e7
Status: Image is up to date for thegeeklab/drone-docker-buildx:latest
+ /usr/local/bin/dockerd --data-root /var/lib/docker --host=unix:///var/run/docker.sock
Detected registry credentials
+ /usr/local/bin/docker version
Client:
 Version:           20.10.13
 API version:       1.41
 Go version:        go1.16.15
 Git commit:        a224086
 Built:             Thu Mar 10 14:04:23 2022
 OS/Arch:           linux/arm64
 Context:           default
 Experimental:      true
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
time="2022-03-17T08:38:59Z" level=error msg="execution failed: exit status 1"

Because privileged mode is still required and you have disabled it now in your config as well.


Make SLA calculation of a Finding Group use the most severe finding

When using finding groups within a test, the SLA calculation for groups passes the entire group to the SLA calculation for a single finding. There is an expected mismatch there. This PR takes the most severe finding I the group and passes that finding the SLA calculation function so that the group has the fastest approaching SLA.

@Maffooch Looks like there's something deprecated in our Helm Lint GH Action setup :-(

Yes, Helm chart unit testing has bee pretty broken for a few months now :/ I change it slightly each release in hopes of finding the right fix, but no dice.
This error happens because the target branch is not dev, and the problematic helm test runs and (expectedly) fails :/


Incorrect caret position and text output

Windows Terminal version (or Windows build number)
Microsoft Windows 10.0.19042, Terminal 1.7.1033.0
Other Software
No response
Steps to reproduce

Start new Windows Terminal instance from windows taskbar (it runs in the C:\Windows\System32 folder). The window must not be maximized.
Type: ls
Press and hold: a key

Expected Behavior
The terminal show a long line with a characters after a list of files.
Actual Behavior
After a few a characters the carret position jumps a few lines above and output the remaining characters there.

This behavior is not 100% reproducible. I guess it is related to window position somehow. I can reproduce this bug 1 or 2 times from 10 runs.
When it broke that way and I maximize window and then return it to old size, then type clear the bug fixes and not appear in than instance of terminal anymore.
However, if I not maximize/return the window size back and just type clear the bug is reproduced again in that instance.
Maybe it is related to some unitialized variable?
This bug is not new. The first time I've noticed it was around 20H2 Windows Update.

Thanks for the report! This is actually already being tracked by another issue on our repo - please refer to #6546 for more discussion.
/dup #6546
If you've got an absolutely consistent repro, I'd appreciate it in that thread 😄


Release Version 2.2.0

This is a component issue for 2.2.0.
Coming from opensearch-build#2271. Please follow the following checklist.
Please refer to the DATES in that post.
How to use this issue

This Component Release Issue
This issue captures the state of the OpenSearch release, on component/plugin level; its assignee is responsible for driving the release. Please contact them or @mention them on this issue for help.
Any release related work can be linked to this issue or added as comments to create visiblity into the release status.
Release Steps
There are several steps to the release process; these steps are completed as the whole component release and components that are behind present risk to the release. The component owner resolves the tasks in this issue and communicate with the overall release owner to make sure each component are moving along as expected.
Steps have completion dates for coordinating efforts between the components of a release; components can start as soon as they are ready far in advance of a future release. The most current set of dates is on the overall release issue linked at the top of this issue.
The Overall Release Issue
Linked at the top of this issue, the overall release issue captures the state of the entire OpenSearch release including references to this issue, the release owner which is the assignee is responsible for communicating the release status broadly.  Please contact them or @mention them on that issue for help.
What should I do if my plugin isn't making any changes?
If including changes in this release, increment the version on 2.0 branch to 2.2.0 for Min/Core, and <IP_ADDRESS> for components. Otherwise, keep the version number unchanged for both.

Preparation

[x] Assign this issue to a release owner.
[ ] Finalize scope and feature set and update the Public Roadmap.
[ ] All the tasks in this issue have been reviewed by the release owner.
[ ] Create, update, triage and label all features and issues targeted for this release with v2.2.0.
[ ] Cut 2.2 branch
[ ] Bump 2.x to version 2.3.0 and update BWC versions
[ ] Update BWC version in main 3.0.0

CI/CD

[ ] All code changes for 2.2.0 are complete.
[ ] Ensure working and passing CI.
[ ] Check that this repo is included in the distribution manifest.

Pre-Release

[ ] Update to the 2.2.0 release branch in the distribution manifest.
[ ] Increment the version on the parent branch to the next development iteration.
[ ] Gather, review and publish release notes following the rules and back port it to the release branch.git-release-notes may be used to generate release notes from your commit history.
[ ] Confirm that all changes for 2.2.0 have been merged.
[ ] Add this repo to the manifest for the next developer iteration.

Release Testing

[ ] Find/fix bugs using latest tarball and docker image provided in parent release issue and update the release notes if necessary.
[ ] Code Complete: Test within the distribution, ensuring integration, backwards compatibility, and performance tests pass.
[ ] Sanity Testing: Sanity testing and fixing of critical issues found.
[ ] File issues for all intermittent test failures.

Release

[ ] Complete documentation.
[ ] Verify all issued labeled for this release are closed or labelled for the next release.

Post Release

[ ] Prepare for an eventual security fix development iteration by incrementing the version on the release branch to the next eventual patch version.
[ ] Add this repo to the manifest of the next eventual security patch version.
[ ] Suggest improvements to this template.
[ ] Conduct a retrospective, and publish its results.

Tracking changes for v2.2.0: https://github.com/opensearch-project/cross-cluster-replication/issues/468

@peterzhuamazon Please update the above the issue to the public road map. I don't have the required permissions.

Plugin build blocked on https://github.com/opensearch-project/OpenSearch/issues/4062
@peterzhuamazon Please help in prioritising the above fix to proceed with the release activities.

@peterzhuamazon - Are plugin pre-release artifacts published on this link https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/2.2.0
FYI, 2.1.0 release artifacts are present for download.
Seeing errors while running integration tests with security plugin - refer to : https://github.com/opensearch-project/cross-cluster-replication/pull/469
cc: @prudhvigodithi

Hey @saikaranam-amazon I see with 2.2.0 the distribution build did not pass with security plugin still, hence you are not able to access the zip.
https://build.ci.opensearch.org/job/distribution-build-opensearch/5855/
The build link you shared https://build.ci.opensearch.org/job/distribution-build-opensearch/5850/ just built OpenSearch and no other components
https://build.ci.opensearch.org/job/distribution-build-opensearch/5850/parameters/
Thank you
@peterzhuamazon @bbarani

Thanks @prudhvigodithi I will wait for the security plugin artifacts to be available in the repo before proceeding further.

@prudhvigodithi I see that security plugin has pushed the fix for 2.2: https://github.com/opensearch-project/security/pull/1988
Can we trigger the build with correct params to publish the artifacts?

I see that 5861 is in progress: https://build.ci.opensearch.org/job/distribution-build-opensearch/5861/

Sanity test - 2.2.0
curl -u 'admin:admin' -k "https://localhost:9200/_cat/nodes?v"
ip         heap.percent ram.percent cpu load_1m load_5m load_15m node.role node.roles                                        cluster_manager name
<IP_ADDRESS>           42          64  14    1.30    0.44     0.14 dimr      cluster_manager,data,ingest,remote_cluster_client *               opensearch-leader1
~~~~ 2.2.0 % curl -u 'admin:admin' -k "https://localhost:9201/_cat/nodes?v"
ip         heap.percent ram.percent cpu load_1m load_5m load_15m node.role node.roles                                        cluster_manager name
<IP_ADDRESS>           27          64  13    1.19    0.43     0.14 dimr      cluster_manager,data,ingest,remote_cluster_client *               opensearch-follower1
~~~~ 2.2.0 % curl -u 'admin:admin' -k -X PUT "https://localhost:9201/_cluster/settings?pretty" -H 'Content-Type: application/json' -d'
  {
    "persistent": {
      "cluster": {
        "remote": {
          "remote-cluster": {
            "seeds": [
              "<IP_ADDRESS>:9300"
            ],
            "transport.ping_schedule": "30s"
          }
        }
      }
        }
}
'
{
  "acknowledged" : true,
  "persistent" : {
    "cluster" : {
      "remote" : {
        "remote-cluster" : {
          "seeds" : [
            "<IP_ADDRESS>:9300"
          ],
          "transport" : {
            "ping_schedule" : "30s"
          }
        }
      }
    }
  },
  "transient" : { }
}
~~~~ 2.2.0 % curl -k -u 'admin:admin' -X PUT "https://localhost:9200/remote-index?pretty" -H 'Content-Type: application/json' -d'
  {
    "settings": {
      "index": {
        "number_of_shards": 1,
        "number_of_replicas": 0
      }
    }
  }
  '
{
  "acknowledged" : true,
  "shards_acknowledged" : true,
  "index" : "remote-index"
}
~~~~ 2.2.0 % curl -k -u 'admin:admin' -X PUT "https://localhost:9201/_plugins/_replication/remote-index/_start?pretty" -H 'Content-Type: application/json' -d'
{
  "leader_alias": "remote-cluster",
  "leader_index": "remote-index",
  "use_roles": {
    "leader_cluster_role": "all_access",
    "follower_cluster_role": "all_access"
  }
}
'
{
  "acknowledged" : true
}
~~~~ 2.2.0 % curl -k -u 'admin:admin' "https://localhost:9200/_cat/indices?v"
health status index                        uuid                   pri rep docs.count docs.deleted store.size pri.store.size
green  open   remote-index                 EMjg4-EZQ5qUZJ5nWpSGAg   1   0          0            0       208b           208b
yellow open   security-auditlog-2022.08.09 jEXjBM4NRpS3_KHtAk9iTQ   1   1          6            0      113kb          113kb
green  open   .opendistro_security         UwQv6Rw8SUqZKPBMzlcONQ   1   0         10            0     68.4kb         68.4kb
~~~~ 2.2.0 % curl -k -u 'admin:admin' "https://localhost:9201/_cat/indices?v"
health status index                        uuid                   pri rep docs.count docs.deleted store.size pri.store.size
green  open   remote-index                 I5Zd_SjGSlunz-y8DRAisw   1   0          0            0       208b           208b
yellow open   security-auditlog-2022.08.09 p1H9yCU8QeeYB7d3K38a7w   1   1          4            0     58.4kb         58.4kb
green  open   .opendistro_security         CUMdnpYkSTGR3s3HZ3gWXQ   1   0         10            0     68.4kb         68.4kb
~~~~ 2.2.0 % curl -k -u 'admin:admin' "https://localhost:9201/_plugins/_replication/remote-index/_status?pretty"
{
  "status" : "SYNCING",
  "reason" : "User initiated",
  "leader_alias" : "remote-cluster",
  "leader_index" : "remote-index",
  "follower_index" : "remote-index",
  "syncing_details" : {
    "leader_checkpoint" : -1,
    "follower_checkpoint" : -1,
    "seq_no" : 0
  }
}
~~~~ 2.2.0 % curl -k -u 'admin:admin' -X POST "https://localhost:9200/remote-index/_doc/?pretty" -H 'Content-Type: application/json' -d'
  {
      "user" : "kimchy",
      "post_date" : "2009-11-15T14:12:12",
      "message" : "trying out Elasticsearch5"
  }
  '
{
  "_index" : "remote-index",
  "_id" : "W6wcgYIB7vTqbEKoX_br",
  "_version" : 1,
  "result" : "created",
  "_shards" : {
    "total" : 1,
    "successful" : 1,
    "failed" : 0
  },
  "_seq_no" : 0,
  "_primary_term" : 1
}
~~~~ 2.2.0 % curl -k -u 'admin:admin' "https://localhost:9201/_plugins/_replication/remote-index/_status?pretty"
{
  "status" : "SYNCING",
  "reason" : "User initiated",
  "leader_alias" : "remote-cluster",
  "leader_index" : "remote-index",
  "follower_index" : "remote-index",
  "syncing_details" : {
    "leader_checkpoint" : 0,
    "follower_checkpoint" : 0,
    "seq_no" : 1
  }
}
~~~~ 2.2.0 % curl -k -u 'admin:admin' "https://localhost:9200/_plugins/_replication/leader_stats?pretty"
{
  "num_replicated_indices" : 1,
  "operations_read" : 1,
  "translog_size_bytes" : 245,
  "operations_read_lucene" : 0,
  "operations_read_translog" : 1,
  "total_read_time_lucene_millis" : 0,
  "total_read_time_translog_millis" : 2,
  "bytes_read" : 197,
  "index_stats" : {
    "remote-index" : {
      "operations_read" : 1,
      "translog_size_bytes" : 245,
      "operations_read_lucene" : 0,
      "operations_read_translog" : 1,
      "total_read_time_lucene_millis" : 0,
      "total_read_time_translog_millis" : 2,
      "bytes_read" : 197
    }
  }
}%                                                                                ~~~~ 2.2.0 % curl -k -u 'admin:admin' "https://localhost:9201/_plugins/_replication/follower_stats?pretty"
{
  "num_syncing_indices" : 1,
  "num_bootstrapping_indices" : 0,
  "num_paused_indices" : 0,
  "num_failed_indices" : 0,
  "num_shard_tasks" : 1,
  "num_index_tasks" : 1,
  "operations_written" : 1,
  "operations_read" : 1,
  "failed_read_requests" : 0,
  "throttled_read_requests" : 0,
  "failed_write_requests" : 0,
  "throttled_write_requests" : 0,
  "follower_checkpoint" : -1,
  "leader_checkpoint" : 0,
  "total_write_time_millis" : 76,
  "index_stats" : {
    "remote-index" : {
      "operations_written" : 1,
      "operations_read" : 1,
      "failed_read_requests" : 0,
      "throttled_read_requests" : 0,
      "failed_write_requests" : 0,
      "throttled_write_requests" : 0,
      "follower_checkpoint" : -1,
      "leader_checkpoint" : 0,
      "total_write_time_millis" : 76
    }
  }
}%                                                                                ~~~~ 2.2.0 % curl -k -u 'admin:admin' -X POST "https://localhost:9201/_plugins/_replication/remote-index/_pause?pretty" -H 'Content-Type: application/json' -d '{}'
{
  "acknowledged" : true
}
~~~~ 2.2.0 % curl -k -u 'admin:admin' "https://localhost:9201/_plugins/_replication/remote-index/_status?pretty"
{
  "status" : "PAUSED",
  "reason" : "User initiated",
  "leader_alias" : "remote-cluster",
  "leader_index" : "remote-index",
  "follower_index" : "remote-index"
}
~~~~ 2.2.0 % curl -k -u 'admin:admin' -X POST "https://localhost:9201/_plugins/_replication/remote-index/_resume?pretty" -H 'Content-Type: application/json' -d '{}'
{
  "acknowledged" : true
}
~~~~ 2.2.0 % curl -k -u 'admin:admin' "https://localhost:9201/_plugins/_replication/remote-index/_status?pretty"
{
  "status" : "SYNCING",
  "reason" : "User initiated",
  "leader_alias" : "remote-cluster",
  "leader_index" : "remote-index",
  "follower_index" : "remote-index",
  "syncing_details" : {
    "leader_checkpoint" : 0,
    "follower_checkpoint" : 0,
    "seq_no" : 1
  }
}
~~~~ 2.2.0 % curl -k -u 'admin:admin' -X POST "https://localhost:9200/remote-index/_doc/?pretty" -H 'Content-Type: application/json' -d'
  {
      "user" : "kimchy2",
      "post_date" : "2009-11-15T14:12:12",
      "message" : "trying out Elasticsearch5"
  }
  '
{
  "_index" : "remote-index",
  "_id" : "Y6wdgYIB7vTqbEKoZvZa",
  "_version" : 1,
  "result" : "created",
  "_shards" : {
    "total" : 1,
    "successful" : 1,
    "failed" : 0
  },
  "_seq_no" : 1,
  "_primary_term" : 1
}
~~~~ 2.2.0 % curl -k -u 'admin:admin' "https://localhost:9201/_plugins/_replication/remote-index/_status?pretty"
{
  "status" : "SYNCING",
  "reason" : "User initiated",
  "leader_alias" : "remote-cluster",
  "leader_index" : "remote-index",
  "follower_index" : "remote-index",
  "syncing_details" : {
    "leader_checkpoint" : 1,
    "follower_checkpoint" : 0,
    "seq_no" : 1
  }
}
~~~~ 2.2.0 % curl -k -u 'admin:admin' -X POST "https://localhost:9201/_plugins/_replication/remote-index/_stop?pretty" -H 'Content-Type: application/json' -d '{}'
{
  "acknowledged" : true
}
~~~~ 2.2.0 % curl -k -u 'admin:admin' "https://localhost:9201/_plugins/_replication/remote-index/_status?pretty"
{
  "status" : "REPLICATION NOT IN PROGRESS"
}
~~~~ 2.2.0 % curl -k -u 'admin:admin' -X POST "https://localhost:9201/remote-index/_doc/?pretty" -H 'Content-Type: application/json' -d'
  {
      "user" : "kimchy3",
      "post_date" : "2009-11-15T14:12:12",
      "message" : "trying out Elasticsearch5"
  }
  '
{
  "_index" : "remote-index",
  "_id" : "DFodgYIB7YU7FRdRw-zy",
  "_version" : 1,
  "result" : "created",
  "_shards" : {
    "total" : 1,
    "successful" : 1,
    "failed" : 0
  },
  "_seq_no" : 2,
  "_primary_term" : 4
}

curl -k -u 'admin:admin' "https://localhost:9200?pretty"
{
  "name" : "opensearch-leader1",
  "cluster_name" : "opensearch-leader",
  "cluster_uuid" : "WHIiLqJZQDiGqaL4IBiwzw",
  "version" : {
    "distribution" : "opensearch",
    "number" : "2.2.0",
    "build_type" : "tar",
    "build_hash" : "b1017fa3b9a1c781d4f34ecee411e0cdf930a515",
    "build_date" : "2022-08-09T02:28:05.169390805Z",
    "build_snapshot" : false,
    "lucene_version" : "9.3.0",
    "minimum_wire_compatibility_version" : "7.10.0",
    "minimum_index_compatibility_version" : "7.0.0"
  },
  "tagline" : "The OpenSearch Project: https://opensearch.org/"
}

curl -k -u 'admin:admin' "https://localhost:9201?pretty"
{
  "name" : "opensearch-follower1",
  "cluster_name" : "opensearch-follower",
  "cluster_uuid" : "dJbbkleuR22S4fQhPLZ_xw",
  "version" : {
    "distribution" : "opensearch",
    "number" : "2.2.0",
    "build_type" : "tar",
    "build_hash" : "b1017fa3b9a1c781d4f34ecee411e0cdf930a515",
    "build_date" : "2022-08-09T02:28:05.169390805Z",
    "build_snapshot" : false,
    "lucene_version" : "9.3.0",
    "minimum_wire_compatibility_version" : "7.10.0",
    "minimum_index_compatibility_version" : "7.0.0"
  },
  "tagline" : "The OpenSearch Project: https://opensearch.org/"
}

We will complete the tasks after dependent plugin changes are merged to 2.x branch: security-2.x

common-utils is tracking 2.2.0 and 2.3.0-SNAPSHOT are not yet available.
Could not determine the dependencies of task ':thirdPartyAudit'.
> Could not resolve all files for configuration ':runtimeClasspath'.
   > Could not resolve org.opensearch:common-utils:<IP_ADDRESS>-SNAPSHOT.
     Required by:
         project :
      > Could not resolve org.opensearch:common-utils:<IP_ADDRESS>-SNAPSHOT.
         > Could not get resource 'https://plugins.gradle.org/m2/org/opensearch/common-utils/<IP_ADDRESS>-SNAPSHOT/common-utils-<IP_ADDRESS>-SNAPSHOT.pom'.
            > Could not GET 'https://repo.gradle.org/artifactory/jcenter/org/opensearch/common-utils/<IP_ADDRESS>-SNAPSHOT/common-utils-<IP_ADDRESS>-SNAPSHOT.pom'. Received status code 409 from server: Conflict
      > Could not resolve org.opensearch:common-utils:<IP_ADDRESS>-SNAPSHOT.
         > Unable to load Maven meta-data from https://d1nvenhzbhpy0q.cloudfront.net/snapshots/lucene/org/opensearch/common-utils/<IP_ADDRESS>-SNAPSHOT/maven-metadata.xml.
            > Could not GET 'https://d1nvenhzbhpy0q.cloudfront.net/snapshots/lucene/org/opensearch/common-utils/<IP_ADDRESS>-SNAPSHOT/maven-metadata.xml'. Received status code 403 from server: Forbidden

other tasks can be unblocked after updating common-utils.


Afterware should follow same rules as middleware

After loading both a middleware and afterware layer to the same path, I noticed that OPTIONS requests were not being fed through the middleware layer, but were being processed by the afterware layer. Since the afterware layer was dependent upon setup in the middleware, this caused errors which required a patch by checking against the request method in the afterware.
The rules for determining the processing of a request should be identical for middleware and afterware.

Hello, thanks for the report. Sounds like a bug to me.
I'm not able to reproduce this though, for example the following test case passes:
func TestOptionsMiddleware(t *testing.T) {
	kami.Reset()
	ok := false
	kami.Use("/hello/", func(ctx context.Context, w http.ResponseWriter, r *http.Request) context.Context {
		return context.WithValue(ctx, "hello", "world")
	})
	kami.Options("/hello/", func(ctx context.Context, w http.ResponseWriter, r *http.Request) {})
	kami.After("/hello/", func(ctx context.Context, w http.ResponseWriter, r *http.Request) context.Context {
		if ctx.Value("hello").(string) == "world" {
			ok = true
		}
		return ctx
	})

	expectResponseCode(t, "OPTIONS", "/hello/", http.StatusOK)
	if !ok {
		t.Error("middleware did not run")
	}
}

If you could provide a failing test case it would help in debugging.

Thanks for the reply. I tried recreating the conditions but it all seemed OK this time around... I'm sure you know how it is.
My best guess is that I might've forgotten the trailing / on middleware, but remembered it on the afterware layer.
If it crops up again, I'll pin it down and create a new issue with detailed information.
Btw, thanks for a great project ✌


change in index.css

Description

...
...
...

Related issue(s)

@nikhil-3112 no changes have been proposed in this PR. please make sure to first open an Issue if you think some changes need to be made.

@nikhil-3112 no changes have been proposed in this PR. please make sure to first open an Issue if you think some changes need to be made.

@KhudaDad414 @koukama
I opened the issue and tried finding some files that need to be modify but I was not able to do with my forked repository. Even not able to make changes and submit a pull request. Do i need any permission , if there is kindly allow me.
Thank you.

Hi @nikhil-3112 I think @koukama already submitted a PR https://github.com/asyncapi/studio/pull/1025
You can pick other issues, by commenting that you want to work on them. Regarding your issue, you don't need any permission from us to contribute in your own Fork.


Update MaxTestedVersion to >= Windows 11

There isn't an SDK for Windows 11 yet but we have tested the app on Windows 11 so set the MaxTestedVersion = 22200 so we get the latest behavior. We can remove/undo this when the SDK is available.

@jevansaks shouldn't this be 22000 instead of 22200?

You're right, but it's also ok because 22000 is the smallest number we could have that works but anything higher is technically ok too.


[BUG 4.0.3] When open 2 consecutive notifications I get a console error

When my code call 2 times to notificate something I get this error:
Uncaught TypeError: Cannot read property 'style' of null   at /bower_components/notific8/dist/notific8.js:110
To fix, need to add this on the two setTimeout functions:
notification = document.getElementById(notificationId);
if (!notification)
        return;

Which browser does this occur in? Also, are you queuing the notifications?

And are there any other frameworks being used?

Linux Chrome, AngularJS, but I think the error is not related to the browser or the framework, it is the way I use notifications. Try these steps in sequence (remove any notification and notific something 2 times):
notific8('remove');
notific8('test', {theme: 'ruby', sticky: true});
notific8('remove');
notific8('test2', {life: 4000});

I will try those out. Those extra details just help with making sure I emulate the environment that the errors occurred in correctly :)
Question, though: why call remove after each one? There isn't really a need to do that since they will remove themselves when they finish. If it's a matter of making sure they're in sequence instead of stacked along the edge, they can set them to queue (config before you call any notifications) instead and set the life to make sure there is only one visible at a time.

Hmm nice to hear about queues!
Today a lot of pages can create a notification and some of them are sticky error messages. Sometimes two or more messages are called and I only check to maintain the last error message on screen, so it will eventually call the remove code and create a notification.

I definitely need to look into the bug that you found but it sounds like you should look into the queuing functionality. They even work with sticky notifications (you can mix and match sticky and not sticky as well).
However, you just gave me an idea for a new feature to have the ability to name a notification and have the ability to rip it from the queue by name (that would probably need to be required for this functionality). From the sounds of what you said about possibly creating two or more messages and only keeping the last in the queue, that might be a useful feature to help with that functionality.

@willsteinmetz It is nice to see you making theses changes, thx!
But the fact is that when you set those timeouts for 1ms and 5ms ( https://github.com/willsteinmetz/notific8/blob/develop/dist/notific8.js#L106 - https://github.com/willsteinmetz/notific8/blob/develop/dist/notific8.js#L118 ) and get the element notification = document.getElementById(notificationId); it can be null depending on what happened between 1ms and 5ms, so you should check if the element is null like you did here: https://github.com/willsteinmetz/notific8/blob/develop/dist/notific8.js#L169
It is a problem HARD to reproduce because it depends on the clock of your machine, but on mine i7-3770 @ 3.4GHz x 4 I am getting this error Uncaught TypeError: Cannot read property 'style' of null or Uncaught TypeError: Cannot read property className of null when I call those in sequence:
notific8('remove');
notific8('test', {theme: 'ruby', sticky: true});
notific8('remove');
notific8('test2', {life: 1000});
notific8('remove');
notific8('test3', {theme: 'ruby', sticky: true});
notific8('remove');
notific8('test4', {life: 4000});

And I am not using queues, so queue is FALSE

I'm definitely going to look into that problem. I get that it's there. I'm suggesting that queues might be worthwhile for what you're trying to accomplish as well. Either way, I am going to fix that bug.

@Tudumanu I just pushed up the fix in version 4.0.4. It should be available now on Bower and NPM.

THX!!!

@Tudumanu I'm working on issue #72 now. That might be of interest to you as well.


update readme

Can we add what version of material-ui is required ... looking in the package.json is annoying :P

styled-components is also a peer dependency, right?

Changes pushed! thx for the review!

Travis automatic deployment:
https://pr18--safereactcomponents.review.gnosisdev.com


[Question] about the fair swapiness

Hello there, I've been looking into the nice script within this repo when something struck me as a bit weird.
The swapiness is set to 100 which as far as I know is the maximum value available.
However, the comment state "swap at a fair rate" which seems weird.
I feel like I'm missing a piece of the puzzle here and would appreciate to be enlightened on how this value was chosen 😄

As far as I understood it:
Android doesn't (unless your OEM is dumb) use real swap, but ZRam only, which is swap-in-ram but compressed, and the compression is not expensive in sense of CPU time.

both can be used iirc, it is even called zswap

Can be used yes, but in practice I only saw xiaomi doing iy

Samsung started advertising swap as extended ram too

On my laptop I use either Zram or Zswap (this currently), with a swappiness value of 200 (kernel 5.10+). It's better to swap early and little because that can be done fast, compared to swapping late and swapping a lot.

Samsung started advertising swap as extended ram too

Samsung uses ZRAM writeback for their "RAM Plus" (RAM extension) feature.


Unable to install SyMPC on raspberry pi 4b

Question
Describe your question in ONE SENTENCE.
I am unable to install SyMPC on my raspberry pi 4b that I'm using for research even though I've successfully installed the dependancies.
Further Information
Describe your question in greater length here.
I followed the install instructions and was able to successfully install PySyft, PyTorch, Torchvision, and the dependancies for SyMPC, but I get an install error when trying to run pip install .
I also tried running "pip install -e ." per the solution for issue #265 , but it still did not work for me and it gave me the same error message.
Screenshots
If applicable, add screenshots to help explain your question.
System Information

OS: Ubuntu
OS Version: 21.04
Language Version: Python 3.9.5
Package Manager Version: APT

Additional Context
Add any other context about the problem here.
I am trying to install this on a raspberry pi4 and I'm not sure if SyMPC can install/run on an ARM architecture.

I was able to solve the install issue, but now when I i try to import Session from sympc.session, I get the following error:

OSError                                   Traceback (most recent call last)
/tmp/ipykernel_2327/3063307635.py in
4 import torch
5
----> 6 from sympc.session import Session
7 from sympc.session import SessionManager
8 from sympc.tensor import MPCTensor
/usr/lib/python3.9/importlib/_bootstrap.py in find_and_load(name, import)
/usr/lib/python3.9/importlib/_bootstrap.py in find_and_load_unlocked(name, import)
/usr/lib/python3.9/importlib/_bootstrap.py in _load_unlocked(spec)
/usr/lib/python3.9/importlib/_bootstrap.py in _load_backward_compatible(spec)
/usr/local/lib/python3.9/dist-packages/wrapt/importer.py in load_module(self, fullname)
154
155     def load_module(self, fullname):
--> 156         module = self.loader.load_module(fullname)
157         notify_module_loaded(module)
158
/usr/local/lib/python3.9/dist-packages/sympc/init.py in
9 from pkg_resources import get_distribution
10
---> 11 from . import api  # noqa: 401
12 from . import approximations  # noqa: 401
13 from . import config  # noqa: 401
/usr/local/lib/python3.9/dist-packages/sympc/api.py in
21 import sympc
22
---> 23 from . import protocol  # noqa: 401
24 from . import session  # noqa: 401
25 from . import store  # noqa: 401
/usr/local/lib/python3.9/dist-packages/sympc/protocol/init.py in
4 from .aby3 import ABY3
5 from .falcon import Falcon
----> 6 from .fss import FSS
7 from .protocol import Protocol
8
/usr/local/lib/python3.9/dist-packages/sympc/protocol/fss/init.py in
1 """FSS Protocol."""
2
----> 3 from .fss import FSS
4
5 all = ["FSS"]
/usr/local/lib/python3.9/dist-packages/sympc/protocol/fss/fss.py in
16 # third party
17 import numpy as np
---> 18 import sycret
19 import torch as th
20 import torchcsprng as csprng  # type: ignore
/usr/local/lib/python3.9/dist-packages/sycret-0.1.3-py3.9.egg/sycret/init.py in
----> 1 from sycret.fss import EqFactory  # noqa: 401
2 from sycret.fss import LeFactory  # noqa: 401
/usr/local/lib/python3.9/dist-packages/sycret-0.1.3-py3.9.egg/sycret/fss.py in
2 import numpy as np
3
----> 4 from .sycret import lib
5 from .utils import _as_i64_array
6 from .utils import _as_u8_array
/usr/local/lib/python3.9/dist-packages/sycret-0.1.3-py3.9.egg/sycret/sycret/init.py in
4 from .ffi import ffi
5
----> 6 lib = ffi.dlopen(os.path.join(os.path.dirname(file), 'native.so'), 4098)
7 del os
OSError: cannot load library '/usr/local/lib/python3.9/dist-packages/sycret-0.1.3-py3.9.egg/sycret/sycret/native.so': /usr/local/lib/python3.9/dist-packages/sycret-0.1.3-py3.9.egg/sycret/sycret/native.so: cannot open shared object file: No such file or directory

Could you install the dependencies and check in the root folder by
pip install -r requirements.dev.txt

hi @rasswanth-s . thanks for the quick reply.
during the install process, i successfully installed the dependencies by running "pip install -r requirements.dev.txt". when I look in the directory listed in error message, the "/usr/local/lib/python3.9/dist-packages/sycret-0.1.3-py3.9.egg/sycret/sycret/" directory is there, but the "native.so" file is not.
is there somewhere else I should be looking?

After installing the dependencies , you are getting the same error?

@rasswanth-s, sorry, I misread you're original post. I had previously run just requirements.txt.
I have now run "pip install -r requirements.dev.txt" and it looks like it successfully installed those new dependencies, but i am still getting the same error when trying to import Session from sympc.session.
OSError: cannot load library '/usr/local/lib/python3.9/dist-packages/sycret-0.1.3-py3.9.egg/sycret/sycret/native.so': /usr/local/lib/python3.9/dist-packages/sycret-0.1.3-py3.9.egg/sycret/sycret/native.so: cannot open shared object file: No such file or directory

@tholop  , @arturomf94  could you take a look at this error?

Yes - I'm trying to replicate a build with Raspberry Pi 4 atm. Will get back to you as soon as I've got more info.

thanks for the help. on a separate install on my VM with x86 architecture, i have the native.so file. would a possible solution be to manually move the native.so file to the directory on the raspberry pi?

The problem evidently comes from sycret. My best guess (maybe @tholop can confirm) is that we need to re-build sycret with Maturin for this architecture? In order to do that, I've installed Maturin and tried to run it, with something like this:
cd ~ && git clone https://github.com/OpenMined/sycret.git
cd sycret
wget -c https://github.com/PyO3/maturin/releases/download/v0.11.2/maturin-aarch64-unknown-linux-musl.tar.gz
tar xvzf maturin-aarch64-unknown-linux-musl.tar.gz
python3 -m venv venv && source venv/bin/activate
./maturin develop -b cffi --release

If you want to replicate this you'll need to install Rust.
However, I'm getting errors in the compilation. I'm still trying to figure out how (if possible) they can be solved.

Cross-compilation might help, so if the compilation doesn't work on the RPi I'll try to do that.

@stevenjgore - Unfortunately, I think it won't be possible to install/use SyMPC on a Raspberry Pi at the moment. The reason for this is that, even if we try to compile sycret on the Raspberry Pi, the problem is that one of the crates used, aesni, uses "special Intel instructions to run AES faster on the CPU" (as pointed out by @tholop).
We will try to make this an optional dependency. We've created this issue for that.

@stevenjgore - sycret now has successful builds for aarch architectures, so you should have no problem with runnning this on a RPi now. I'll close this, but if you have any questions or comments, don't hesitate to reach out! :+1:


Add ability to query derived data

Add ability to query derived variables (eg. subdomains derived from domains) in the graph explorer.

This should be handled either in the mapping or client side.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

AWS CodeBuild CI Report

CodeBuild project: DDKIntegrationTestsD8472609-5SCHWjldmWcf
Commit ID: 38aa670ee3f5d906f136e21cf2ae71045cdec7ca
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Diff Inline View is not showing removed code

Type: Bug

Open a file that is stored in source control.
Remove some text from it.
In the "Source Control" menu, select the file to open the diff and see the changes.
Toggle between Split View and Inline View. Split View shows the deleted text, while Inline View does not. The minimap scrollbar shows red though, indicating it sees the removed code.

FYI this has appeared for me now in latest release.
The bug does not appear immediately on vscode application launch. Have not noticed any specific action triggering it, but will keep an eye out.
Version: 1.83.1 (user setup)
Commit: f1b07bd25dfad64b0167beb15359ae573aecd2cc
Date: 2023-10-10T23:48:05.904Z
Electron: 25.8.4
ElectronBuildId: 24154031
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19044

It looks like something with the view zones is off. The alignment viewzones are missing in the first screenshot.

Somewhere in the middle of coding VS Code suddenly decides to do this. Closing and reopening VS Code fixes is temporarily until this happens again. That's my current unsophisticated observation. (v1.83.1)

https://stackoverflow.com/questions/77324073/vscode-is-hiding-removed-lines-from-diffs
I've been having this issue too. if you move the diff view or split the view the "new" view shows things correctly.

Do you have any settings enabled that could cause this? This is certainly a bug, but so far I didn't manage to reproduce

I have this issue in the latest vscode version

Happens for me invariably. Here is my version info and settings.json
Version: 1.83.1 (Universal)
Commit: f1b07bd25dfad64b0167beb15359ae573aecd2cc
Date: 2023-10-10T23:46:55.789Z (1 wk ago)
Electron: 25.8.4
ElectronBuildId: 24154031
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 22.6.0
{
  "window.autoDetectColorScheme": true,
  "workbench.sideBar.location": "right",
  "[typescriptreact]": {
    "editor.defaultFormatter": "esbenp.prettier-vscode"
  },
  "[javascript]": {
    "editor.defaultFormatter": "esbenp.prettier-vscode"
  },
  "editor.tabSize": 2,
  "[html]": {
    "editor.defaultFormatter": "vscode.html-language-features"
  },
  "editor.lineNumbers": "relative",
  "editor.fontFamily": "SF Mono,Menlo,monospace",
  "editor.fontLigatures": true,
  "workbench.preferredLightColorTheme": "Default Light+ Experimental",
  "workbench.preferredDarkColorTheme": "Default Dark+ Experimental",
  "git.confirmSync": false,
  "[python]": {
    "editor.formatOnType": true
  },
  "thunder-client.previewFeatures": true,
  "thunder-client.responseLimit": 5,
  "ruby.rubocop.onSave": false,
  "[json]": {
    "editor.defaultFormatter": "esbenp.prettier-vscode"
  },
  "[typescript]": {
    "editor.defaultFormatter": "esbenp.prettier-vscode"
  },
  "terminal.integrated.fontSize": 17,
  "ruby.useBundler": true, //run non-lint commands with bundle exec
  "ruby.useLanguageServer": true, // use the internal language server (see below)
  "ruby.lint": {
    "rubocop": {
      "useBundler": true // enable rubocop via bundler
    }
  },
  "ruby.format": "rubocop",
  "workbench.colorTheme": "Alabaster",
  "editor.formatOnSaveMode": "modificationsIfAvailable",
  "editor.formatOnSave": true,
  "editor.fontSize": 17
}

toggling the Diff Editor: Render Side By Side setting on and off worked for me

toggling the Diff Editor: Render Side By Side setting on and off worked for me

Doesn't work for me.

Another quick fix/workaround is to run > Developer: Reload Window from the Command Pallete:

Can you check/share the dev tool logs when this happens?
Can you also share both sides of the diff where this happens?
I'm using the diff editor daily and so far I didn't see this yet.

Same just happened for me. In my case it asked if i want to increase the diff time processing (was processing 2 big files), apart from that i haven't done anything unusual.
Reloading the window solved for me

This issue has been a huge problem for me for over a month. Developer: Reload Window solved all my problems. Thanks!

I faced this issue and updated to 1.84.2 (user setup). After restart, the issue is not present, but that could be temporary until the issue returns again (as per previous comments here). I'm not able to forcefully reproduce the issue by doing things like switching diff views, staging, unstaging, staging selected ranges etc.
It's interesting to note that the first occurrence of this issue happened when I staged a file. Usually the diff in the working tree disappears fully, but this time only the added diff (green) disappeared, where as the deleted diff (red) still remained. I thought that was odd, and checked the diff in the index, and it only contained the added diff (green).
I checked git diff on Terminal and everything is alright there, so I'm thinking this might be a corruption of the VS Code's internal diff cache or something, which could explain why Reload Window or restart of VS Code fixes this temporarily.
PS: When I first noticed it, I incorrectly thought this is some kind of a new feature which hides unnecessary deleted lines 😂 (for example if the line has no deleted chars, only added ones) and went around digging in Settings to turn it off. Apparently, it's a bug and regression.

@hediet is there a way for one of us to get a dump of the VS Code app diff engine/module/whatever when this happens again? Maybe you can inspect it to see what's going on. 🙂
Logs could be an alternative too. Maybe the diff engine is hitting some errors and silently bypassing them.

Just ran into this after doing a lot of work in a single session (i.e. the problem did not immediately start occurring). Developer: Reload Window was an effective workaround for me as well. Before this occurred, I had been doing an abundant amount of mass find/replace (non-regex, non-case-sensitive, non-whole-word, non-preserve-case), that had cumulatively dirtied >800 files in my working directory. In the course of doing this, I had invoked the diff editor many dozens (if not hundreds) of times from within the session before this misbehavior occurred.
This misbehavior was not isolated to a specific file or find result; once it began occurring, the misbehavior continued with each file/location in my find results list.
Version: 1.84.2 (user setup)
Commit: 1a5daa3a0231a0fbba4f14db7ec463cf99d7768e
Date: 2023-11-09T10:51:52.184Z
Electron: 25.9.2
ElectronBuildId: 24603566
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621

@hediet this is most consistently happening to me when I'm viewing worktree diff, then staging it in the sidebar. It happens randomly, but I noticed this is what I was usually doing just before it does.
I have to Reload Window each time it happens to fix the issue, until it re-occurs sometime later.

@hediet Time-correlated renderer.log entries when this issue re-occurred just a bit ago... hope this provides a hint at what might be going on.
2023-11-22 13:38:00.272 [error] Cannot read properties of undefined (reading 'endLineNumberExclusive'): TypeError: Cannot read properties of undefined (reading 'endLineNumberExclusive')
    at E.intersectsStrict (vscode-file://vscode-app/c:/Users/me/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:96:10545)
    at D (vscode-file://vscode-app/c:/Users/me/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:681:45393)
    at vscode-file://vscode-app/c:/Users/me/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:681:47301
    at w (vscode-file://vscode-app/c:/Users/me/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:85:8256)
    at vscode-file://vscode-app/c:/Users/me/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:681:47296
2023-11-22 13:38:45.797 [error] Cannot read properties of undefined (reading 'endLineNumberExclusive'): TypeError: Cannot read properties of undefined (reading 'endLineNumberExclusive')
    at E.intersectsStrict (vscode-file://vscode-app/c:/Users/me/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:96:10545)
    at D (vscode-file://vscode-app/c:/Users/me/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:681:45393)
    at vscode-file://vscode-app/c:/Users/me/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:681:47301
    at w (vscode-file://vscode-app/c:/Users/me/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:85:8256)
    at vscode-file://vscode-app/c:/Users/me/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:681:47296
2023-11-22 13:38:56.498 [error] Cannot read properties of undefined (reading 'endLineNumberExclusive'): TypeError: Cannot read properties of undefined (reading 'endLineNumberExclusive')
    at E.intersectsStrict (vscode-file://vscode-app/c:/Users/me/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:96:10545)
    at D (vscode-file://vscode-app/c:/Users/me/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:681:45393)
    at vscode-file://vscode-app/c:/Users/me/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:681:47301
    at w (vscode-file://vscode-app/c:/Users/me/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:85:8256)
    at vscode-file://vscode-app/c:/Users/me/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:681:47296
2023-11-22 13:40:04.384 [error] Cannot read properties of undefined (reading 'endLineNumberExclusive'): TypeError: Cannot read properties of undefined (reading 'endLineNumberExclusive')
    at E.intersectsStrict (vscode-file://vscode-app/c:/Users/me/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:96:10545)
    at D (vscode-file://vscode-app/c:/Users/me/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:681:45393)
    at vscode-file://vscode-app/c:/Users/me/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:681:47301
    at w (vscode-file://vscode-app/c:/Users/me/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:85:8256)
    at vscode-file://vscode-app/c:/Users/me/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:681:47296

This actually might be a duplicate of https://github.com/microsoft/vscode/issues/198516 which I already fixed.

Closing as duplicate of https://github.com/microsoft/vscode/issues/198516.

Another example - again missing deleted line decorations in split view:

And inline view doesn't show anything:

This happened after "Staging Selected Ranges".
Reloading the window fixes it temporarily:

This issue is most certainly not resolved. I've had this problem for several months but it was always "fixed" by closing and restarting Code. As of today it's happening about every five files or so. Developer: Reload Window is an effective workaround only when the problem happens infrequently; but when I'm trying to review hundreds of files to push a bug fix into production, it's not an effective workaround. The issue that this issue "duplicates" doesn't mean anything to me.
It's definitely a cross-browser issue. I'm using Ubuntu and at least two of the people reporting the bug in this thread are using Windows.
Can someone give me a status on this that I can explain easily to my boss? Thanks.
Version: 1.85.1
Commit: 0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2
Date: 2023-12-13T09:47:11.635Z
Electron: 25.9.7
ElectronBuildId: 25551756
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.4.0-169-generic snap


Add lex models

Beta builds fail due to https://github.com/rusoto/rusoto/issues/877 .  This is okay to merge!


Package installation fails on a new blank UWP app

Here is the error from the output window:
System.Reflection.Emit.ILGeneration 4.0.1 provides a compile-time reference assembly for System.Reflection.Emit.ILGeneration on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-arm-aot.
One or more packages are incompatible with UAP,Version=v10.0 (win10-arm-aot).
System.Reflection.Emit.ILGeneration 4.0.1 provides a compile-time reference assembly for System.Reflection.Emit.ILGeneration on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-x64-aot.
One or more packages are incompatible with UAP,Version=v10.0 (win10-x64-aot).
System.Reflection.Emit.ILGeneration 4.0.1 provides a compile-time reference assembly for System.Reflection.Emit.ILGeneration on UAP,Version=v10.0, but there is no run-time assembly compatible with win10-x86-aot.
One or more packages are incompatible with UAP,Version=v10.0 (win10-x86-aot).
Package restore failed for 'App1'.
Package restore failed. Rolling back package changes for 'App1'.

Thank you for reporting the issue. This will be taken care of as soon as possible.
Could you install version <IP_ADDRESS> for now.
Thanks,
Linvi

I wanted to issue a fix by tonight but it is getting late here.
The problem is with nuget only, no code needs to be changed.
So you will have to wait tomorrow evening.
In the meantime please do use the version 1.0.
Sorry for the inconvenience.

I have just released version <IP_ADDRESS> which is just a new nuget package with the same binary but this time it should work with your W10 project.
Thank you.


unique / custom / one-off default runner

intended implmentation is doing this with the args thing, with just using the whole command as an arg

closed by commit https://github.com/anna-singleton/runfast/commit/104f5204bb47f7fde62142759542ce97a751b034


Agent embeddings templates

Need templates for agent embeddings for giving better initial context to the agent. The templates could be created around different goals, constraints, agent types etc.

Do you have an example of an agent embedding template?  How would these be formed and introduced into the application?

Knowledge embeddings are now live on local and Cloud. Please check it out, it should solve your usecase. Closing this issue


How to use with named formatting?

Hello and thanks for having this package. I wonder how to use the context editor with Named Formatting
I checked examples/basic but couldn't find any example for named formatting usage. I'd tried to change title as
<h2>{{ $t("title", { number: 3 }) }}</h2>

and the related translation to
<i18n>
{
  "en": {
    "title": "Dummy title {number}",
    "headline": "",
    "intro": "",
    "text": ""
  }
}
</i18n>

however it did not worked for some reason. Instead I received this screen below with Dummy title {number} as hardcoded:

I also added my translation to Translation Center

Hey @kaangokdemir, the InContext-Editor is currently only displaying the translation from Phrase. Placeholder values are being currently being ignored. It would definitely be great to actually show the placeholder values in the translation but we have no looked further into this yet.


glz::expected implicitly convertible to std::expected

For use cases where you already have std::expected and would like the user facing code to use the standard library would it be beneficial to make glz::expected implicitly convertible to std::expected?
example
#include <expected>
#include <glaze/glaze.hpp>

std::expected<double, int> value = glz::expected<double, int>{};

or  use std expected when it is available, something like

#ifdef __cpp_lib_expected
namespace glz {
template<typename expected_t, typename unexpected_t>
using expected<expected_t, unexpected_t> = std::expected<expected_t, unexpected_t>;

template<typename unexpected_t>
using unexpected<unexpected_t> = std::unexpected<unexpected_t>;
}
#else
// internal impl
#endif

I know it is configurable whether glz::expected should throw or abort, not sure how that would best integrate with this.
Maybe third option to use std::expected explicitly but not sure it is a good idea.
What is the best way around this matter?

I think using std::expected when it is available is preferable, Ill go ahead and make that change later today.

Addressed in #235. glz::expected is just an alias to std::expected if it is available.


Change messaging about SCM support

[x] Don't say we support Gitlab
[x] Update zapiers
[ ] Test manually

@dtuite it's finally all good!


VR: fix site-2-site VPN if split connections is enabled

Description
This PR fixes the issue that s2s vpn cannot be applied if split-connections is enabled
the issue is because count is a build-in method in python3 , len should be used instead.
>>> aa=[]
>>> aa.count
<built-in method count of list object at 0x76e292158b40>
>>> len(aa)
0

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI
[ ] test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

How did you try to break this feature and the system with this change?

@blueorangutan package

@weizhouapache a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

@blueorangutan test

@DaanHoogland a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests

[SF] Trillian test result (tid-11870)
Environment: kvm-ol8 (x2), Advanced Networking with Mgmt server ol8
Total time taken: 46086 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr10067-t11870-kvm-ol8.zip
Smoke tests completed. 131 look OK, 2 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_04_extract_Iso
Failure
16.15
test_iso.py

test_01_secure_vm_migration
Error
134.45
test_vm_life_cycle.py

test_01_secure_vm_migration
Error
134.45
test_vm_life_cycle.py

@blueorangutan package

@andrijapanicsb a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 11888

@blueorangutan test

@andrijapanicsb a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests

[SF] Trillian Build Failed (tid-11972)

[SF] Trillian Build Failed (tid-11973)

tested in lab env, both active and passive versions get created

@blueorangutan test

@weizhouapache a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests

[SF] Trillian test result (tid-11988)
Environment: kvm-ol8 (x2), Advanced Networking with Mgmt server ol8
Total time taken: 45112 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr10067-t11988-kvm-ol8.zip
Smoke tests completed. 133 look OK, 0 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

[SF] Trillian test result (tid-11995)
Environment: kvm-ol8 (x2), Advanced Networking with Mgmt server ol8
Total time taken: 45948 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr10067-t11995-kvm-ol8.zip
Smoke tests completed. 132 look OK, 1 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_01_secure_vm_migration
Error
134.40
test_vm_life_cycle.py

test_01_secure_vm_migration
Error
134.41
test_vm_life_cycle.py


Security

Hi there,
Thanks for the great tutorial.
What are the considerations around security? Helm - Tiller - Ingress
Would really appreciate your advise in this respect - especially when considering production use in Azure.

Anyone wondering about the same thing - have a look at: https://docs.microsoft.com/en-us/azure/aks/kubernetes-helm

Hi @Leon-Africa - thank you for sharing this link! Sorry I didn't respond earlier! And I'm really glad this was helpful.
Hopefully Helm 3 (see https://helm.sh/blog/helm-3-preview-pt2/) will also start to improve some of the security posture in running Helm as the Tiller is being completely removed.


Integrate upgraded bitcoin controller into vault

Closed by merging PR: https://github.com/getsafle/safle-vault/pull/270


⚠ Bofrost.at has degraded performance

In aba1745, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1929 ms

Resolved: Bofrost.at performance has improved in d32e69e after 7 minutes.


Enable config.strictDepsByDefault = true by default

strictDeps helps keeping cleaner PATHs for cross-compiled packages. But it's also useful to have for native builds: it helps writing nix derivations that have better chance of working when cross-compiled later.
 Or more precise depsBuildBuild & co. finer grained equivalents.
https://github.com/NixOS/nixpkgs/blob/cd88f8613f3d8cd5a985c624cd3cf14459ddbed9/pkgs/stdenv/generic/make-derivation.nix#L127-L128

libxml2 seems to break with config.strictDepsByDefault = true. Adding python in nativeBuildInputs fixes the issue.
I am not really confident to propose this as a patch as I don't understand why this exists: pythonSupport ? enableShared && stdenv.buildPlatform == stdenv.hostPlatform.

libxml2 seems to break with config.strictDepsByDefault = true. Adding python in nativeBuildInputs fixes the issue. I am not really confident to propose this as a patch as I don't understand why this exists: pythonSupport ? enableShared && stdenv.buildPlatform == stdenv.hostPlatform (in pkgs/development/libraries/libxml2/default.nix).

python is probably being disabled because cross-compilation enables strictDeps and so breaks the python detection
i'll fix it

There seems to be a similar issue to libxml2 with libxslt.
I am building a aarch64-linux NixOS system from master using config.strictDepsByDefault = true. I will update the following list with the files in which I had to add strictDeps = false; to get a working system:

[ ] pkgs/development/libraries/libxml2/default.nix
[ ] pkgs/development/libraries/libxslt/default.nix
[ ] pkgs/os-specific/linux/kmod/default.nix

libxml2, libxslt: https://github.com/NixOS/nixpkgs/pull/194941

perlPackages.{Po4a,AlienLibxml2},kmod,liblouis https://github.com/NixOS/nixpkgs/pull/218503

Ward because I need to learn this.

Since nobody mentioned this before, we should only do this for Nixpkgs, not third-parties, at least not without a proper warning first. Otherwise we break package builds for thousands of users.

What are third parties exactly? Are (for example) users of .override, .overrideAttrs and overlays = [] considered to be third-parties? I wonder if nixpkgs even provides a way to distinguish internal from external users.
I had an impression that external users are expected to pin to a particular revision of nixpkgs to get a reasonable build result. Otherwise users have to constantly adapt to internal changes like gcc updates, parameter additions and removals, package removal/deprecation and .nix file moves. Largest breakages are usually covered by release notes.

Overlays make this a bit tricky because it's how Nixpkgs defines its packages internally, but third-parties can also provide overlays. So I think it's fine to treat overlays as Nixpkgs code.
But other than that, anything using the resulting import <nixpkgs> {} value instead of going through overlays should be considered third-party code. And it's possible to implement code that can distinguish that (it'll have to touch the core of Nixpkgs though).

I had an impression that external users are expected to pin to a particular revision of nixpkgs to get a reasonable build result. Otherwise users have to constantly adapt to internal changes like gcc updates, parameter additions and removals, package removal/deprecation and .nix file moves. Largest breakages are usually covered by release notes.

While we don't yet have a clear guideline on API stability guarantees, my take on it is that we should guarantee stability for the code that we control. This includes all the Nix code in Nixpkgs, including e.g. the passthru attributes of packages. We are responsible for that code and should take care to not break it.
But this doesn't include the contents of the packages: If upstream of a package happens to break for all users, we aren't responsible for that, it's upstream that should get the complaints. We can still include a note on that in the release notes as a courtesy, but it's not required.

Is extra-cmake-modules affected by strictDeps = true?

note that cmake effectively puts buildInputs in the search path and before PATH when strictDeps is true and should probably get fixed before strictDeps becomes the default. one attempt to fix this is here https://github.com/NixOS/nixpkgs/pull/318226 but it is still a WIP.


Incorrect hash length for netntlmv2 captured hash

Hello Kevin,
I've obtained several NetNTLM v2 hashes using your tool but hashcat is throwing an error with the hash length (type 5600: NetNTLMv2)
Hashfile 'netntlmv2.lst' on line 1 (-- redacted ---): Salt-length exception
The same error for all hashes.
Checking the format against the hashcat examples I've accomplished an inusual length of 32 characters for the captured hash.
Any idea or hint?
Thanks in advance!

SMB or HTTP? I'm guessing the challenge is missing? There is something that can cause that with the packet sniffer on the SMB side that I have not been able to track down.

Hi Kevin,
SMB and the challenge is present in the logfile:
[+] [2020-09-17T07:51:35] SMB(445) negotiation request detected from <IP_ADDRESS>:51243 [+] [2020-09-17T07:51:36] SMB(445) NTLM challenge F91F2FCA9466DCC4 sent to <IP_ADDRESS>:51243 [+] [2020-09-17T07:51:36] SMB(445) NTLMv2 captured for DOMAIN\username from <IP_ADDRESS>(COMPUTERNAME):51243: [redacted]
The attacker's machine is a "Windows Server 2012 R2 Standard" and the tool was launched with admin privs. I can send you a captured hash if need be.
In the other hand using Inveigh-Zero in the same scenario it works like a charm.
Thanks for your support!

Hi,
Ugh, I'm guessing you don't see F91F2FCA9466DCC4 listed in the full hash output? If so, I think I see the bug. I combined the SMB and HTTP NTLM code but it looks like it's only checking the HTTP session table to grab the challenge.
Since it is indeed seeing the challenge in this case, you should be able to just paste it in right after DOMAIN:. I'll get it fixed this weekend. Thanks!

Hi Kevin,
As you said, using the challenge from the logfile the problem has gone. I should have thought about it before!
Thanks for your support and such great tool!


Shuffle some test initialization code to allow running under xdist.

I was trying to get my tests to run under xdist in my factory_boy branch, and I wound up having to make these changes for the child process to initialize properly. That branch isn't ready for a PR yet, so I thought I may as well submit these separately.

Turns out this is actually fiendishly difficult to do correctly. My first version worked fine for me, but failed under Travis.
In the end, I think I found a solution that doesn't feel entirely hack-ish.

Excellent! I'm not sure about the import of setup_olympia.py as a django installed app, it's really hackish, and pretty sure it won't work anymore once we upgrade do django 1.7 and its not app loading code. Why don't we simply import this file in the conftest.py instead of the previously imported manage.py?

r+wc

I added comments, and also a couple of lines in conftest.py to also add prefixes to cache keys, just in case we do end up needing to switch back to using an actual memcache server.

One more comment and we're good to go, thanks!
r+wc


Abuse protection failed when using Azure Function

Describe the bug
I'm trying to use Web PubSub in combination with a C# Function App in Azure. When I sent a custom event to the Function App, the abuse protection fails with status code 401.
If I run the Function locally, use ngrok, and change the event handler to the ngrok URL, everything works fine.
To Reproduce
I've created a Function App called serverlessponies1805. In the trace logging, I see the following message:
Registered Web PubSub negotiate Endpoint = https://serverlessponies1805.azurewebsites.net/runtime/webhooks/webpubsub

I used that URL to set up my event handler.
I then connect succesfully to the Web PubSub service from a client application and send a custom event.
The live trace now shows the following error:
Event Name = AbuseProtectionResponseInvalidStatusCode
Message = Abuse protection failed: 401

What am I missing here?

Have you include the function keys when setup the event hander? See snapshot below to get the registered key from Function App. Including the key, the event handler url should be like https://{function-app}.azurewebsites.net/runtime/webhooks/webpubsub?Code={webpubsub_extension_key}

There's a known issue when authenticated enabled will always return 401. If the function key is not the reason for you case, can you share more information in your scenario? Share a sample is better.

Thanks! Works perfect now that I use the function key. Has this been documented somewhere already? I couldn't find any docs/samples on hosting a Web PubSub function app in Azure.

Sorry that after a few rounds of document refactor, I missed to add it anywhere. Basically it should be mentioned in both Azure Function side similar to this and our documents side. I'll put it in near future. Thanks for the feedbacks!

Hey @JialinXin, it would be really nice to update documentation. I've just spent 2h debugging until I found this.

@anzax , Thanks for adding comments. I'm working on this. BTW, to help improve the noticing entry, would you share some insights about which doc are you use to work with? I'll add some link to it to help navigation.

@JialinXin, I was using this sources of documentation:

https://docs.microsoft.com/en-us/azure/azure-web-pubsub/quickstart-serverless?tabs=javascript
https://github.com/Azure/azure-webpubsub/blob/main/docs/getting-started/work-with-azure-function/js-work-with-azure-function.md
https://azure.github.io/azure-webpubsub/references/functions-bindings

I got it working locally with ngrok but it didn't work when I deployed function app as I didn't know there is a need to specify security code in the webhook url. Moreover, Azure Web PubSub service was returning 500 on an attempt to connect to websockets so it was hard to figure out what was wrong.

For short, I'm updating the sample related to event-handler settings for some further introduction. Besides, we need to add a few more in Azure Docs. Keep the issue open until we finished.


[6.0 🍒][Explicit Module Builds] Remove dead/incorrect code for handling header inputs of binary module dependencies

Explanation: As of https://github.com/swiftlang/swift/pull/72067, we serialize (bridging) .h inputs directly into binary .swiftmodule files, because their clients may not be able to use the binary module's corresponding .pch files due to a compilation context mismatch. The clients of such binary modules then consume the serialized .h files directly, and compile them, implicitly, using explicit module dependencies collected during scan of such header files. This change removes leftover code that relied on a prior, incorrect, assumption that we pass on binary dependencies' PCH inputs to their clients.
Scope: This affects Explicit Module Builds where source client being compiled depends on a binary-only .swiftmodule dependency which was built with a bridging header.
Risk: Low. This change only deletes a code-path that previously was extremely likely to lead to a compilation error downstream.
Issue/Radar: rdar://131261765
Original PR: https://github.com/swiftlang/swift-driver/pull/1653
Reviewed By: @cachemeifyoucan

@swift-ci test


Implementation of sending data using a modem SIM7600 and Wiznet W5500.

Help me please! I have a need to send data via MQTT using a modem SIM7600 and Wiznet W5500, but I have a problem how can I choose the network interface to send using the MQTT API.
By default, data should be transmitted via Wiznet W5500, when the connection is interrupted I want to switch to data transmission via modem SIM7600.

Closing due to inactivity and age


setup.py: Separate description for tools and runtime

Another non-code fix.
I am not sure if the runtime is not included in tools package. Looks like it is packed as data, but not probably not installed as something to be imported from Python code. I am also not sure why runtime is packed for PyPI if it is only usable by generated Go code.

You are mostly right. runtime is packed for PyPI because I wanted an to let an easy way for people to install Grumpy. As Python is needed anyway, distribution using PyPI seemed as a nice idea. Also because I wanted not to mess with the Golang distribution tools.
grumpy-tools can transpile Python -> Go code
grumpy-runtime have the native modules that the transpilled ones need.

This runtime might need some explanation for the users of Python, but for now I couldn't think of anything better. Are there any chance to update PyPI packages?


Linux wheels: manylinux2014 tracking issue

The manylinux1 images are starting show their age and therefore make the maintenance of the Linux wheels quite troublesome. OpenCV 3.4.10 and 4.3.0 cannot be built on manylinux1 images due to too old glibc:
/io/opencv/modules/core/src/parallel.cpp:943:56: error: ‘CPU_COUNT’ was not declared in this scope

         unsigned cpu_count_cpu_set = CPU_COUNT(&cpu_set);

In practice this means that the manylinux1 (CentOS 5) needs to be updated to manylinux2010 (CentOS 6) or manylinux2014 (CentOS 7). Considering that the CentOS 6 will be deprecated later this year it's better move straight to manylinux2014. The manylinux2014 tag support is not yet fully rolled out (https://github.com/pypa/manylinux/issues/338). However, there are only some minor issues remaining and they will get solved likely during the next few months.
This upgrade will most likely have positive effects to the OpenCV performance (see: https://github.com/skvark/opencv-python/issues/287). Additionally, external dependencies, such as Qt, can be updated to more recent versions.
What needs to be done:

[x] Prepare new custom Dockerfiles which extend from manylinux2014 similarly to the current manylinux1 Dockerfiles

[x] Install Qt 5 (preferably via package manager, currently Qt 4.8.7 is built from sources)
[x] Check if Cmake is present. If not, it could be probably set as a Python dependency similarly to numpy
[x] Check if custom OpenSSL build is needed
[x] Build latest FFmpeg from sources
[ ] Check if other often requested 3rd party dependencies can be enabled easily by installing them via package manager (must check license terms) Edit: this needs more work, needs to be done later when first working versions of the new wheels have been released
[x] Clean up other stuff from the Dockerfiles

[x] Check setup.py custom rules and patches

[x] Enable IPP if possible
[x] Remove other custom rules which are not needed
[x] Check if OpenEXR patch is still needed

The manylinux2014 tag support is not yet fully rolled out

It looks like as of this comment, the rollout has been completed.

Thanks for the info. I'll update the Docker images and will run some tests.

The current status is that Linux builds have an issue with Qt5. I get this on Ubuntu 20.04 when trying to run very simple script with imshow:
Found metadata in lib /home/username/test/lib/python3.8/site-packages/cv2/qt/plugins/platforms/libqxcb.so, metadata=
{
    "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3",
    "MetaData": {
        "Keys": [
            "xcb"
        ]
    },
    "className": "QXcbIntegrationPlugin",
    "debug": false,
    "version": 329991
}

Got keys from plugin meta data ("xcb")
QFactoryLoader::QFactoryLoader() checking directory path "/usr/bin/platforms" ...
loaded library "/home/username/test/lib/python3.8/site-packages/cv2/qt/plugins/platforms/libqxcb.so"
[New Thread 0x7fffbb3b0700 (LWP 5905)]

Thread 1 "python" received signal SIGSEGV, Segmentation fault.
0x00007fffbe3abe05 in _xcb_in_expect_reply () from /home/username/test/lib/python3.8/site-packages/cv2/qt/plugins/platforms/../../../../opencv_python.libs/libxcb-65da195c.so.1.1.0

The Qt xcb plugin crashes on _xcb_in_expect_reply() method.

If someone would like to test the manylinux2014 wheels they can be downloaded by following this guide: https://github.com/skvark/opencv-python/releases/tag/34

Hi, any updates? looking forward to 4.3 :)

I'll have to compile Qt5 probably manually to get rid of that error but haven't had the time to do it yet.

Regarding manual build, have u look at C++ package managers?
this one is actively contributed https://github.com/microsoft/vcpkg

BTW, I built opencv4.3 on ubuntu 20.04 and it works fine.
What's the issue, or it is only related to CentOS ?

Yeah, locally built OpenCV will work of course just fine but that's not what this repository is trying to do. Manylinux wheels must be built on very specific systems to make them compatible with different Linux distributions (https://www.python.org/dev/peps/pep-0513/). The problem is not in package managers but in binary level compatibility across different distributions.
The OpenCV builds related to this issue work just fine, only a subset of the methods related to displaying GUI windows is broken. As we can see above, Qt5 segfaults when it tries to use the bundled xcb plugin which has been included from the CentOS Qt5 build.
Additionally, building for example Qt5 manually is not a problem, it just takes time when it's done for the first time. After that it can be used from the Docker images without any build overhead.

@skvark In case any of these resources are helpful:

Building Qt5 from Git
A Dockerfile for Qt5 on CentOS 7

Another interesting thing I found: PyQt5 builds manylinux2014 wheels already.

The source is listed here: https://riverbankcomputing.com/software/pyqt/download5 but at first glance I don't see any kind of Docker build environment for making the wheels. Maybe they don't release that.
Perhaps for a project as important as OpenCV, they would consider answering a question: https://riverbankcomputing.com/support/pyqt

I guess we don't need pyqt5 but instead we need native Qt5 with cmake and header files.
I will try to build Qt5 and opencv with this docker

I guess we don't need pyqt5 but instead we need native Qt5 with cmake and header files.

Right, I just assumed that if PyQt5 managed to build a manylinux2014 wheel, as part of that they must have figured out how to built Qt5 on a CentOS 7 image.

Oh, I see

I'm pretty sure that building Qt5 on the manylinux image is quite straightforward process (same as Qt4 in current images, probably mostly copy pasting from there). After that the next thing is to get OpenCV built against it and testing the resulting wheels in other systems. Again, the main issue is that all those things take multiple evenings (or weekends) of my time. Anyone can of course do that as this is a open source project, it does not have to be me. The Dockerfiles are in the docker directory in case someone is interested in contributing. Copying the Qt4 example from master branch Dockerfiles to manylinux2014 branch Dockerfiles and modifying it for Qt5 is a good starting point. https://doc.qt.io/qt-5/build-sources.html#linux-x11

@skvark Would you consider setting up something like GitHub Sponsors for people who would like to say thank you for your work?

@johnthagen I'll have a look at it. There are some complicated things related to Finnish taxation system which I need to check before even applying for example to Github Sponsors.

I couldn't get the latest Qt5 work with OpenCV (cv2 import hanged forever in 64 bit builds and segfaulted in 32-bit builds) so downgrading back to Qt4 which hopefully solves the issue for now. I will test the builds this week. macOS has also some build failures which need to be solved.

Linux builds are now ok. Fixing macOS issues now.

Homebrew apparently fixed itself so the release builds can be now made. 3.4.10 is now in progress, 4.3.0 will come after they are done.


Azure Web Pubsub Samples Issue

Section : link

Reason:  when I create a group and add user to it,  always get an error that user id not found. When I create a group and add connection to it,  always get an error that connection id doesn't exist . some detials are as follows:

@jongio for notification.

It is not a issue, so close it.


Link to covenant redirects to the Gardens page

When I click to view the covenant before signing. It tries to open https://gardens-rinkeby.1hive.org/#/covenant, but then redirects to https://gardens-rinkeby.1hive.org/#/home
It also does not open in a new tab but rather refreshes the current page I am on.

Closed by https://github.com/1Hive/honey-pot/pull/498
Thanks for reporting @CurlyBracketEffect !


docs: Change structure of document

Description

Related Issue: Fixes #62
Changes

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

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

Checklist

[ ] I have performed a self-review of my own code.
[ ] My code is commented, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] New and existing unit tests pass locally with my changes.
[ ] Any dependent changes have been merged and published in downstream modules.

Further Comments

Our team is currently in the process of reviewing the document. Once the review is complete, significant changes to the structure are likely.
I will incorporate your comments after this task is finished. Thank you.

Continue to #67


OrchestrationTemplate refactoring

The major goal is to move OrchestrationTemplate subclasses to provider repositories, together with some other refactoring/enhancement around OrchestrationTemplate. The work includes aspects such as:

Move CloudFormation, Hot, Azure, Vnfd Template to provider repositories. VCloud Template is already in its provider repository
Update the provider refresher code to create/update orchestration template with the new type.
Enhance Amazon and Openstack OrchestrationTemplate class to handle both JSON and YAML format
Move factories and fixtures for various template types to corresponding repositories.
Move/Refactor service dialog generation tool to create deployment options in a more generic way.
Migrate DB orchestration template records from old type to new ones.
Update classic UI references to any above changes
Cleaning up manageiq repository for obsoleted files.

This issue tracks all PRs around the refactoring
ManageIQ/manageiq-providers-amazon

Move template class here ~~https://github.com/ManageIQ/manageiq-providers-amazon/pull/286~~
Fix refresher ~~https://github.com/ManageIQ/manageiq-providers-amazon/pull/295~~
Supports YAML https://github.com/ManageIQ/manageiq-providers-amazon/pull/298

ManageIQ/manageiq-providers-openstack

Move template class here ~~https://github.com/ManageIQ/manageiq-providers-openstack/pull/76~~
Fix refresher, add JSON support, move spec fixtures etc https://github.com/ManageIQ/manageiq-providers-openstack/pull/93

ManageIQ/manageiq-providers-azure

Move template class here ~~https://github.com/ManageIQ/manageiq-providers-azure/pull/111~~
Fix refresher ~~https://github.com/ManageIQ/manageiq-providers-amazon/pull/121~~

ManageIQ/schema

Migration https://github.com/ManageIQ/manageiq-schema/pull/55

ManageIQ/manageiq

Add (move) OrchestrationTemplateServiceDialog https://github.com/ManageIQ/manageiq/pull/15982
Cleaning up #15964

ManageIQ/manageiq-ui-classic

Fix references https://github.com/ManageIQ/manageiq-ui-classic/pull/2133

cc @gmcculloug

@bzwei Anything outstanding here?  Otherwise we can close this issue.


Compilation on an ARMv7A Machine

What steps will reproduce the problem?
1.../configure --build=x86 --target=armv7a-none-linux-gnueabi
--host=arm-none-linux-gnueabi --program-prefix=arm-none-linux-gnueabi-
--with-static --prefix=/people/pradeepb/test
2.make install

What is the expected output? What do you see instead?
I did not expect to see any warnings about the machine type. However, i see
os.h:160:4: warning: #warning "Unsupported CPU type: Unable to force cache
flushes."

What version of the product are you using? On what operating system?
1_0_7; Linux/Ubuntu

Please provide any additional information below.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 9 Sep 2014 at 1:37

Fixed


feat(bfdr): cigarettes smoked

Summary
Natality already has smoking implemented, so this was just a matter of adding tests and IJE methods

The changes look good, just needs a rebase to resolve conflicts


interactive=True has no effect with default drawer output ('text')

What is the expected enhancement?
I think we either convert the text output to an image and make it pop out, or we clearly document that interactive only works when output is 'latex' or 'mpl'. Not the default 'text'

So the interactive flag is documented as opening the visualization in a new window. That really wasn't an option with text. Did you have a way in mind for doing it? I can update the docstring though. When I wrote the docstring for the circuit_drawer() the text drawer didn't exist.

Updating the docstring (maybe a 'warning' that interactive doesn't work with this output arg?) sounds good. I originally thought converting the text output with a bounding box to an image and showing that, but that's probably too crazy.


Prototype Updates - Everything before CFR

Title of ticket: Prototype Updates - Everything before CFR
Description
Completed all small missing UI elements before Call for Records
Dependencies
Are there any dependencies?
DOD

[x] Update template editor screen to look like rich text editor - R

[x] Add modal - navigating away from request before saving - R

[x] Add toast - successfully save/sent - R

[x] Templates - is there an additional file or form requested/clarification before file can be opened - R

[x] View Request History

[x] View Documents Provided for Personal Requests

[x] Adoption Details - Additional Details

[x] Update Prototype

Some things have been updated in sketch but not the prototype as there will be additional changes to come in the upcoming sprint which will change how these function in the prototype.


Cpu limiter in normal instalation without docker

This should be already possible by using cgroups cpulimit or nice. See https://scoutapm.com/blog/restricting-process-cpu-usage-using-nice-cpulimit-and-cgroups for details. This should be then included in your server start command. Cpulimit ist not advised, since it will hard limit and why would you force a server to idle, when a process could use some of the resources.


[MRTK3] Updated HandMenu & NearMenu prefabs to use CanvasBackplate.mat in the  StandardAssets package

Overview
HandMenu & NearMenu prefabs were using CanvasBackplate.mat from the MRGT package which was not updated to Linear color space. Assigned CanvasBackplate.mat from the StandardAssets package.
(Pin button was already using the correct material)
We are going to need to document this difference + update MRGT one to avoid confusion.
Changes

Fixes: #11008

Before & After

The near menu prefabs still have issues, but I'll open another issue and fix those myself.


javaType as Long does not work with latest version but works with 0.4.x

"type": "integer",
"javaType": "Long"
This correctly creates Long object in 0.4.x. However it does not work with the latest version. If I want some objects as Integer and come as Long then this does not work with latest version.

Hi
There were a lot of changes between 0.4.x and current version including breaking changes.
javaType has been separated into existingJavaType and javaType, see #828.
Please use existingJavaType when referring existing java types, eg:
"type": "integer",
"existingJavaType": "Long"


0.1.0 release

This is the final branch for the 0.1.0 release.
I'll be fixing one or two bugs here, improving code quality, then writing a blog article after the release is live.
No new features are being considered for this release. I'm expecting to release either tonight or early tomorrow.

I've confirmed tests work on x86-64/GNU and Aarch64/GNU. Our CI is overwhelmed unfortunately, so I'll open an issue for that.


create IT for DataFlagEncoder & SpatialRuleLookup

See the discussion: https://github.com/graphhopper/graphhopper/pull/966#issuecomment-285901672

Yes this is very important. We should definitely do this.


MTRC is returning plain objects, not react components

Hey, thanks for the really cool library! I'm trying to integrate this into my app, but am hitting an issue and I'm not sure what's causing it.
When I run a markdown string through MRTC, I'm getting back a list of objects that are not react components. Basically, this is all I have so far:
const MTRC = require('markdown-to-react-components')
MTRC.configure({})

const md = "# Header text"
const components = MTRC(md)

console.log(components.tree)

...however, the .tree I'm getting back is an array of 'plain' objects, not React components.
"{
  "type": "p",
  "key": "1",
  "ref": null,
  "props": {
    "children": [
      "Header text",
    ]
  },
  "_owner": null,
  "_store": {}
}"

When I run the example from this repo, the objects returned from MTRC are react components (eg, with the $$typeof key and everything else).
The only thing I can think that might be relevant is that I'm using React 15, while this library is using React 0.14. It probably has something to with this.
Any tips or pointers for getting around this?

@CodyReichert This seems weird, but this repo just got DEPRECATED in favor of: https://github.com/cerebral/marksy. Could you try that out? :-)


GH#220 - Softmax Utils Function

Closes #220
For review: @BruceYanghy, @XiaoYangLiu-FinRL

this branch has conflicts with master.
could  you pls describe the reason why using the softmax you have written?