Not able to run the flux successfully

Hello All,
While following the steps, i am getting the below error on the flux and not able to run any workload using the flux:
ts=2019-04-29T04:06:36.714622818Z caller=images.go:28 component=sync-loop msg="no automated workloads"
ts=2019-04-29T04:06:43.293711087Z caller=loop.go:103 component=sync-loop event=refreshed url=git@github.com:xxxxxxx/xxxxxx branch=master HEAD=c38943df8dde8b4ffda98a050e6f643ec712ccc3
ts=2019-04-29T04:06:43.528694435Z caller=main.go:199 type="internal kubernetes error" err="couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
ts=2019-04-29T04:06:43.528789635Z caller=loop.go:210 component=sync-loop err="collating resources in cluster for sync: not found"
ts=2019-04-29T04:06:43.531861734Z caller=loop.go:90 component=sync-loop err="collating resources in cluster for sync: not found"
ts=2019-04-29T04:11:36.714944593Z caller=images.go:18 component=sync-loop msg="polling images"
ts=2019-04-29T04:11:36.818370548Z caller=main.go:199 type="internal kubernetes error" err="couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
ts=2019-04-29T04:11:44.168625836Z caller=loop.go:210 component=sync-loop err="collating resources in cluster for sync: not found"
ts=2019-04-29T04:11:44.171171938Z caller=loop.go:90 component=sync-loop err="collating resources in cluster for sync: not found"
ts=2019-04-29T04:11:44.172498339Z caller=loop.go:103 component=sync-loop event=refreshed url=git@github.com:xxxxxx/xxxxxxxx branch=master HEAD=c38943df8dde8b4ffda98a050e6f643ec712ccc3
ts=2019-04-29T04:16:36.825719462Z caller=images.go:18 component=sync-loop msg="polling images"
ts=2019-04-29T04:16:36.939251772Z caller=main.go:199 type="internal kubernetes error" err="couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
ts=2019-04-29T04:16:45.041430658Z caller=loop.go:210 component=sync-loop err="collating resources in cluster for sync: not found"
ts=2019-04-29T04:16:45.04355066Z caller=loop.go:90 component=sync-loop err="collating resources in cluster for sync: not found"```

Any help will be appreciated.

The same problem with:

GKE, kubernetes v. 1.12.7-gke.10, clean, just deployed cluster
helm v2.12.3
flux 1.12.1, chart v0.9.2

Logs from flux pod:
ts=2019-04-30T15:14:14.388856059Z caller=main.go:192 version=1.12.1
ts=2019-04-30T15:14:14.414804737Z caller=main.go:346 component=cluster identity=/etc/fluxd/ssh/identity
ts=2019-04-30T15:14:14.414853262Z caller=main.go:347 component=cluster identity.pub="ssh-rsa ..."
ts=2019-04-30T15:14:14.414886312Z caller=main.go:348 component=cluster host=https://<IP_ADDRESS>:443 version=kubernetes-v1.12.7-gke.10
ts=2019-04-30T15:14:14.414944773Z caller=main.go:360 component=cluster kubectl=/usr/local/bin/kubectl
ts=2019-04-30T15:14:14.416181456Z caller=main.go:371 component=cluster ping=true
ts=2019-04-30T15:14:14.424369715Z caller=main.go:504<EMAIL_ADDRESS>user="Weave Flux"<EMAIL_ADDRESS>signing-key= sync-tag=flux-sync notes-ref=flux set-author=false
ts=2019-04-30T15:14:14.424441003Z caller=main.go:561 upstream="no upstream URL given"
ts=2019-04-30T15:14:14.425109781Z caller=main.go:582 addr=:3030
ts=2019-04-30T15:14:14.425400867Z caller=loop.go:90 component=sync-loop err="git repo not ready: git repo has not been cloned yet"
ts=2019-04-30T15:14:14.42543519Z caller=images.go:18 component=sync-loop msg="polling images"
ts=2019-04-30T15:14:14.425447813Z caller=images.go:28 component=sync-loop msg="no automated workloads"
ts=2019-04-30T15:14:14.99186012Z caller=checkpoint.go:24 component=checkpoint msg="up to date" latest=1.12.1
ts=2019-04-30T15:14:15.699468879Z caller=warming.go:198 component=warmer info="refreshing image" image=docker.io/weaveworks/helm-operator tag_count=15 to_update=15 of_which_refresh=0 of_which_missing=15
ts=2019-04-30T15:14:16.520717253Z caller=warming.go:206 component=warmer updated=docker.io/weaveworks/helm-operator successful=15 attempted=15
ts=2019-04-30T15:14:16.521310683Z caller=images.go:18 component=sync-loop msg="polling images"
ts=2019-04-30T15:14:16.521344059Z caller=images.go:28 component=sync-loop msg="no automated workloads"
ts=2019-04-30T15:14:17.300027383Z caller=warming.go:198 component=warmer info="refreshing image" image=memcached tag_count=68 to_update=68 of_which_refresh=0 of_which_missing=68
ts=2019-04-30T15:14:19.367301081Z caller=loop.go:103 component=sync-loop event=refreshed<EMAIL_ADDRESS>branch=master HEAD=29c7067c2a2ec05ffc663e2e040a6984518bf4a3
ts=2019-04-30T15:14:19.632424736Z caller=warming.go:206 component=warmer updated=memcached successful=68 attempted=68
ts=2019-04-30T15:14:19.721616109Z caller=main.go:206 type="internal kubernetes error" ts=2019-04-30T15:14:19.721627185Z caller=memcache.go:199 err="couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
ts=2019-04-30T15:14:19.723726274Z caller=main.go:206 type="internal kubernetes error" ts=2019-04-30T15:14:19.723736762Z caller=memcache.go:111 err="couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
ts=2019-04-30T15:14:19.741070634Z caller=loop.go:90 component=sync-loop err="collating resources in cluster for sync: unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
ts=2019-04-30T15:14:19.74116762Z caller=images.go:18 component=sync-loop msg="polling images"
ts=2019-04-30T15:14:19.81937953Z caller=images.go:28 component=sync-loop msg="no automated workloads"
ts=2019-04-30T15:14:21.022331691Z caller=warming.go:198 component=warmer info="refreshing image" image=docker.io/weaveworks/flux tag_count=29 to_update=29 of_which_refresh=0 of_which_missing=29
ts=2019-04-30T15:14:22.406835225Z caller=warming.go:206 component=warmer updated=docker.io/weaveworks/flux successful=29 attempted=29
ts=2019-04-30T15:14:22.407079934Z caller=images.go:18 component=sync-loop msg="polling images"
ts=2019-04-30T15:14:22.491887236Z caller=images.go:28 component=sync-loop msg="no automated workloads"
ts=2019-04-30T15:14:22.816378428Z caller=warming.go:198 component=warmer info="refreshing image" image=gcr.io/stackdriver-agents/stackdriver-logging-agent tag_count=43 to_update=43 of_which_refresh=0 of_which_missing=43
ts=2019-04-30T15:14:23.990321458Z caller=warming.go:206 component=warmer updated=gcr.io/stackdriver-agents/stackdriver-logging-agent successful=43 attempted=43
ts=2019-04-30T15:14:23.990709606Z caller=images.go:18 component=sync-loop msg="polling images"
ts=2019-04-30T15:14:24.071599116Z caller=images.go:28 component=sync-loop msg="no automated workloads"
ts=2019-04-30T15:14:24.466000245Z caller=warming.go:198 component=warmer info="refreshing image" image=gcr.io/kubernetes-helm/tiller tag_count=69 to_update=69 of_which_refresh=0 of_which_missing=69
ts=2019-04-30T15:14:25.848811677Z caller=warming.go:206 component=warmer updated=gcr.io/kubernetes-helm/tiller successful=69 attempted=69
ts=2019-04-30T15:14:25.849972253Z caller=images.go:18 component=sync-loop msg="polling images"
ts=2019-04-30T15:14:25.924965686Z caller=images.go:28 component=sync-loop msg="no automated workloads"
ts=2019-04-30T15:14:49.48935677Z caller=loop.go:103 component=sync-loop event=refreshed<EMAIL_ADDRESS>branch=master HEAD=29c7067c2a2ec05ffc663e2e040a6984518bf4a3
ts=2019-04-30T15:14:49.817122766Z caller=main.go:206 type="internal kubernetes error" ts=2019-04-30T15:14:49.817139134Z caller=memcache.go:111 err="couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
ts=2019-04-30T15:14:49.836981413Z caller=loop.go:90 component=sync-loop err="collating resources in cluster for sync: unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
ts=2019-04-30T15:15:20.25409899Z caller=main.go:206 type="internal kubernetes error" ts=2019-04-30T15:15:20.254113633Z caller=memcache.go:199 err="couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
ts=2019-04-30T15:15:20.25589743Z caller=main.go:206 type="internal kubernetes error" ts=2019-04-30T15:15:20.255907374Z caller=memcache.go:111 err="couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
ts=2019-04-30T15:15:20.274468081Z caller=loop.go:90 component=sync-loop err="collating resources in cluster for sync: unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
ts=2019-04-30T15:15:20.276593296Z caller=loop.go:103 component=sync-loop event=refreshed<EMAIL_ADDRESS>branch=master HEAD=29c7067c2a2ec05ffc663e2e040a6984518bf4a3
ts=2019-04-30T15:15:25.925306668Z caller=images.go:18 component=sync-loop msg="polling images"
ts=2019-04-30T15:15:26.006435102Z caller=images.go:28 component=sync-loop msg="no automated workloads"
ts=2019-04-30T15:15:51.06012156Z caller=main.go:206 type="internal kubernetes error" ts=2019-04-30T15:15:51.06013407Z caller=memcache.go:111 err="couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
ts=2019-04-30T15:15:51.078705207Z caller=loop.go:90 component=sync-loop err="collating resources in cluster for sync: unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
ts=2019-04-30T15:15:51.08636588Z caller=loop.go:103 component=sync-loop event=refreshed<EMAIL_ADDRESS>branch=master HEAD=29c7067c2a2ec05ffc663e2e040a6984518bf4a3
ts=2019-04-30T15:16:21.752093002Z caller=main.go:206 type="internal kubernetes error" ts=2019-04-30T15:16:21.752106478Z caller=memcache.go:111 err="couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
ts=2019-04-30T15:16:21.768521245Z caller=loop.go:90 component=sync-loop err="collating resources in cluster for sync: unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
ts=2019-04-30T15:16:21.770565476Z caller=loop.go:103 component=sync-loop event=refreshed<EMAIL_ADDRESS>branch=master HEAD=29c7067c2a2ec05ffc663e2e040a6984518bf4a3
ts=2019-04-30T15:16:26.006781485Z caller=images.go:18 component=sync-loop msg="polling images"
ts=2019-04-30T15:16:26.089713607Z caller=images.go:28 component=sync-loop msg="no automated workloads"
ts=2019-04-30T15:16:52.873453573Z caller=main.go:206 type="internal kubernetes error" ts=2019-04-30T15:16:52.873468656Z caller=memcache.go:111 err="couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
ts=2019-04-30T15:16:52.890825119Z caller=loop.go:90 component=sync-loop err="collating resources in cluster for sync: unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
ts=2019-04-30T15:16:52.893905855Z caller=loop.go:103 component=sync-loop event=refreshed<EMAIL_ADDRESS>branch=master HEAD=29c7067c2a2ec05ffc663e2e040a6984518bf4a3
ts=2019-04-30T15:17:23.504796994Z caller=main.go:206 type="internal kubernetes error" ts=2019-04-30T15:17:23.504810062Z caller=memcache.go:111 err="couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
ts=2019-04-30T15:17:23.520032947Z caller=loop.go:90 component=sync-loop err="collating resources in cluster for sync: unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
ts=2019-04-30T15:17:23.522067982Z caller=loop.go:103 component=sync-loop event=refreshed<EMAIL_ADDRESS>branch=master HEAD=29c7067c2a2ec05ffc663e2e040a6984518bf4a3
ts=2019-04-30T15:17:26.090019339Z caller=images.go:18 component=sync-loop msg="polling images"
ts=2019-04-30T15:17:26.171956062Z caller=images.go:28 component=sync-loop msg="no automated workloads"

Thanks both of you for your reports, we will be looking into this asap.
@hamid2013 can you share some details about your environment?

This seems a bit similar to: #1951
As the two error messages in logs from @lkosz are:
caller=main.go:206 type="internal kubernetes error" ts=2019-04-30T15:16:52.873468656Z caller=memcache.go:111 err="couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
caller=loop.go:90 component=sync-loop err="collating resources in cluster for sync: unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server is currently unable to handle the request"

This is similar to #1951 (which is fixed in Flux1.12.1). However, in this case Flux is not silencing the error (the server is currently unable to handle the request when trying to get the resources for metrics.k8s.io/v1beta1) since it's legitimate.
After a quick search ( see https://github.com/kubernetes-incubator/metrics-server/issues/157  , https://github.com/DirectXMan12/k8s-prometheus-adapter/issues/66 and for instance ), this seems to be a misconfiguration of the metrics addon (or something else leveraging the metrics API) in your clusters.
To fix this, Flux could potentially avoid getting the resources for *metrics.k8s.io/* (I have never used metrics, but I don't think it makes any sense to sync  them with Flux) but for now I think it's best if you try to address the metrics API problem in your clusters.
Since this has come up before, it would help us to understand how this happened . @hamid2013 @lkosz could you answer the following questions?

@hamid2013 what kubernetes version are you using and how did you deploy it?
@hamid2013  @lkosz Could you show me the output of kubectl get --raw /apis/metrics.k8s.io/v1beta1 (I would expect something like server is currently unable to handle the request as an output)
@hamid2013  @lkosz Are you knowingly using the metrics API? Did you modify the metrics API configuration in any way? Are you running the prometheus adapter or similar?

And one more hint.
There was another bug related to GKE: #1855 which also mentioned couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
And there was a hint that it might depend on timing (e.g. deploying both the GKE cluster and flux within a single terraform run): https://github.com/weaveworks/flux/issues/1855#issuecomment-476103797


polymer serve returns undefined in output URL for element template

Install next releases of both the CLI and polyserve
run polymer init element in a new directory
Run polyserve
polymer serve

Expected result:
The CLI return accurate output, similar to polyserve.
Actual result:
(see reusable components: url)
fschott-macbookpro:temp fschott$ polyserve -p 1945
Files in this directory are available under the following URLs
    applications: http://<IP_ADDRESS>:1945
    reusable components: http://<IP_ADDRESS>:1945/components/temp-element/

fschott-macbookpro:temp fschott$ polymer serve -p 1945
info:    Files in this directory are available under the following URLs
      applications: http://<IP_ADDRESS>:1945
      reusable components: http://<IP_ADDRESS>:1945/components/undefined/

Same issue here.
It occurs on WSL(ubuntu), but works fine on MacOS...
Both $ polymer serve and $ polyserve would get this issue.

polymer version

$ polymer --version
1.9.11

OS info

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.2 LTS
Release:        18.04
Codename:       bionic


Removing duplicate ssh-keygen line for Github AE docs

Why:
There is currently a duplicated line in the documentation for generated an SSH key for Github AE user. This PR removes the duplicate command.
Closes: https://github.com/github/docs/issues/26967

What's being changed (if available, include any code snippets, screenshots, or gifs):
Step 2 of the Generating a new SSH key on the Github AE docs contains a duplicate command, this PR removes that duplicate. The original and current version of that step can be found in the issue linked above.

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

@valxntine Thank you for opening a PR and linking it to your issue! ✨
Welcome to the community! I'll get this triaged for review! :zap:
In the meantime, if you'd like to find other ways to contribute, check out our help wanted section to find open issues you can work on. 👍


capture a piece of JSON/XML as a literal

An important case in GeoSPARQL is to capture fragments of the input XML (GML) or JSON (GeoJSON) as literals with custom datatypes: geo:gmlLiteral, geo:geoJSONLiteral.
This happens when converting eg GML, CityGML; and JSON-FG, CityJSON to RDF.
I think this is easy with RML, but I just want to be sure. Is it possible to add test cases for it?
I faced that problem recently, so I wrote some issues for different tools:

https://github.com/w3c/json-ld-syntax/issues/425
https://github.com/SPARQL-Anything/sparql.anything/issues/452
https://github.com/semantalytics/xsparql/issues/38

However, I'm a bit puzzled how it looks exactly if we want to add a test case for it. Do you have an example of input and expected RDF output? The referenced issues give only a faulty output as an example.

@VladimirAlexiev could you help us to define this test-case?

Sorry forvthe delay @DylanVanAssche and @dachafra , I'll do this

Sorry for the delay @DylanVanAssche and @dachafra , I'll do this


Can you provide the GPT2 example?

Would you be able to provide the gpt2 example for p-tuning v2?

@Xiao9905

@PoodleWang Hi,
We do not implement p-tuning v2 for GPT-style models in this work. However, you can refer to Prefix-Tuning's implementation, which is for GPT models on generation tasks only.


URL's from Redis To Go don't work due to "too many colons in address"

A conventional Redis-To-Go URL doesn't work.
2017-02-26T20:54:23.538797721Z","@version":"1","level":"debug","message":"Trying to connect to mongodb://user:password@hidden.mlab.com:12345/janus","type":"Janus"}
2017-02-26T20:54:25.293989182Z {"@timestamp":"2017-02-26T20:54:25.293716857Z","@version":"1","level":"debug","message":"Connected to mongodb","type":"Janus"}
2017-02-26T20:54:25.294027164Z {"@timestamp":"2017-02-26T20:54:25.293791179Z","@version":"1","level":"debug","message":"Trying to connect to redis pool: redis://user:password@hidden.redistogo.com:12345","type":"Janus"}
2017-02-26T20:54:25.294033972Z {"@timestamp":"2017-02-26T20:54:25.293817677Z","@version":"1","level":"fatal","message":"Couldn't connect to the redis pool: dial tcp: too many colons in address redis://user:password@hidden.redistogo.com:12345","type":"Janus"}

Janus version: quay.io/hellofresh/janus:1.7.4

Thank you for reporting that, the problem was that we were using the Dial method from the redigo library, we changed to use DialURL so it should work properly now.

Confirmed here that this is fixed in 1.7.4-rc.6. Thanks!


Method for changing order number

Is there currently a method for changing/resetting the initial order number.
I have a client who wants orders to start at a specific number.

The order number is just the id of the order record, which is an auto increment field.
So the easiest way is I think to just do a manual SQL query against the database:
ALTER TABLE CommunityStoreOrders AUTO_INCREMENT = 1234;


[testing] return joinhandles and add store preserve support in cluster

A follow up of https://github.com/MystenLabs/narwhal/pull/487 , is doing the following:

Making the code return JoinHandles from all the parts that we spawn new tasks
Because of the above we are now able to properly shutdown all the running parts of the primary when we stop a node and properly close the database (automatically closed once all references are dropped)
Refactoring the Cluster struct to allow us preserve storage when node is restarted. That will allow us to test our network under different assumptions

Note: Interestingly enough the test now passes when we preserve the storage - the restarted node manages to perform the causal completion successfully, catch up the other nodes and make progress to the same commit round.

Closing as this has been merged  which already contains the above changes


Custom html snippet for flash message

@Pralish can we add the following to the spec?

expose the newly created api_resource in the snippet context. So we can do the following:

Thanks for filling out the form #{ api_resource.properties[:first_name] }. We will get back to you soon!


fatal error: 'objc/runtime.h' file not found

Hey @progrium 👋
Thank you so much for macdriver, you have no idea how excited I am about this 🙌
I feel a bit silly not even being able to get going on the largetype example, but I get:
# github.com/progrium/macdriver/objc
../../../../go/pkg/mod/github.com/progrium/macdriver@v0.0.1/objc/class.go:10:10: fatal error: 'objc/runtime.h' file not found
#include <objc/runtime.h>
         ^~~~~~~~~~~~~~~~
1 error generated.

When I try to go run *.go with main.go containing the example's contents.
I've set up with the usual go mod init ... and go mod download.

I'm sure it's just something dead simple that I'm missing 😅

Ah, I might be missing some pre-req steps. Quick question, how did you install go? What version of OS X? Do you have Xcode Command Line Tools installed?

I have go1.15.6 darwin/amd64 installed from nixpkgs on macOS 11.1
I don't have the Xcode Command Line Tools installed as the utilities provided in that package are present in my environment via nixpkgs too :)
Is there something specific in that package that's needed for those headers?

The headers.

I think I saw them under an SDK directory, googling "apple headers sdk nix" I found there is maybe a nix package called "apple-sdk" and this looks similar but I'm no nix expert! Hope that's helpful, pls share what you find

Is there something specific in that package that's needed for those headers?

The headers.

That made me chuckle, haha.
Great, thank you for the help on this! It was indeed just headers/libraries missing from my system.
For anyone coming across this with a conventional set-up, I believe you need to install the Xcode Command Line Tools (as @progrium suggests above).
If you're like me and you're running Nix, the following shell.nix will give you a build environment (and of course this is enough to go off to build a package):
with import <nixpkgs> {};
stdenv.mkDerivation rec {
  name = "example";
  env = buildEnv { name = name; paths = buildInputs; };

  buildInputs = [
    go
    clang

    darwin.apple_sdk.frameworks.AppKit
    darwin.apple_sdk.frameworks.Cocoa
    darwin.apple_sdk.frameworks.CoreFoundation
    darwin.apple_sdk.frameworks.WebKit
  ];

  CPATH = "${darwin.Libsystem}/include";
  NIX_LDFLAGS = "-framework AppKit -framework Cocoa -framework CoreFoundation -framework WebKit";
}

Then something like nix-shell --pure --command "go run *.go Nix\!" works 🎉
Thanks again @progrium - I can't wait to get started building stuff with this 🙇


Integrate Chart.js - Matrix Client

Purpose
In order to be able to provide visualization of respective metrics collected e.g. CPU, Memory, and Disk Consumption we have decided to use Chart.js
First we need to integrate this library into our project utilizing npm
Expected Behavior
we should have the ability to create visual charts outlining metric consumption over a given period of time using the Chart.js library.

This work has been completed on 30/chartjs-integration' and is ready to be merged into develop`.


Web API conventions return type

When we use ProducesResponseType we can specify the return type of the action "Model", how to specify the return type while using Web API conventions?
Thanks.

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

ID: 9d14d206-7998-2031-d1d7-f8c8dbecf54a
Version Independent ID: 3071c40e-f08b-555e-4fe7-dc3828f5828e
Content: Use web API conventions
Content Source: aspnetcore/web-api/advanced/conventions.md
Product: aspnet-core
Technology: aspnetcore-webapi
GitHub Login: @pranavkm
Microsoft Alias: scaddie

Thank you for contacting us. Due to a lack of activity on this discussion issue we're closing it in an effort to keep our backlog clean. If you believe there is a concern related to the ASP.NET Core which hasn't been addressed, please file a new issue.

You didn't provide any solution nor any suggestion before closing the issue!


batch requests when filtering on interfaces

solution provided by @Tom-Hubrecht https://github.com/Solvik/netbox-agent/pull/297
walrus operator is available starting from Python 3.8

python 3.8 is already eol though, maybe the requirements should be updated ?

@Tom-Hubrecht yes you're right, but netbox-agent suport python 3.7 too and it won't work anymore :)

@Tom-Hubrecht
You're right, Python 3.7 and Python 3.8 are EOD, for now the codebase is compatible with those versions.
The change that I've made to your proposal will allow us to maintain that level of compatibility.


A few JSONErrors

I get the following error when pulling data using the instruments function:
Data: JSONError "Error in $.instruments[0].halted: failed to parse field halted: expected String, encountered Boolean"

Changing line 55 of Rates.hs from using Maybe String to Maybe Bool seems to do the trick.
But then I get:
Data: JSONError "Error in $.instruments[0].interestRate: failed to parse field interestRate: mempty"

Where changing line 56 of Rates.hs from using Maybe Decimal to Maybe Object makes it work again:
...instrumentInterestRate = Just (fromList [("USD",Object (fromList [("bid",Number 0.0),("ask",Number 4.0e-3)])),("EUR",Object (fromList [("bid",Number 0.0),("ask",Number 4.0e-3)]))])...

Although I don't know enough about Aeson (or Haskell for that matter) to know if using Maybe Object is the correct approach.
I'll submit a pull request.

Fixed with #3.

Fixed with #3.


Keyboard accessibly and ARIA

Hi
I notice that the pagination on the results page is not keyboard accessible. Also it would be great if you added ARIA attributes to make it more accessible.
Thanks
Cheers
Decrepidos

Thanks. I'll look into this for the next release.

Note: This has been fixed in Pull Request #39.


Weird DDC error with a simple Angular2 application

 (master) $ bazel build :dashboard_layout_demo
WARNING: Sandboxed execution is not supported on your system and thus hermeticity of actions cannot be guaranteed. See http://bazel.io/docs/bazel-user-manual.html#sandboxing for more information. You can turn off this warning via --ignore_unsupported_sandboxing.
INFO: Found 1 target...
ERROR: /home/zoechi/dart/bwu_ng_mdl/BUILD:31:1: Compiling with dart2js //:dashboard_layout_demo failed: process-wrapper failed: error executing command /home/zoechi/.cache/bazel/_bazel_zoechi/3e443aaa6a6cf1824cc4980f306f0a94/execroot/bwu_ng_mdl/_bin/process-wrapper -1 5 - - external/io_bazel_rules_dart/dart/build_rules/tools/dart2js_helper.sh ... (remaining 8 argument(s) skipped).
bazel-out/local-fastbuild/bin/dashboard_layout_demo.build/lib/demo/dashboard_layout/dashboard_layout_demo_app_component.dart:2:1:
Error: Library not found 'package:angular2_components/angular2_components.dart'.
import 'package:angular2_components/angular2_components.dart'
    show materialInputDirectives;

bazel-out/local-fastbuild/bin/dashboard_layout_demo.build/lib/demo/dashboard_layout/dashboard_layout_demo_app_component.dart:3:10:
Hint: Library 'package:angular2_components/angular2_components.dart' doesn't export a 'materialInputDirectives' declaration.
Try removing 'materialInputDirectives' from the 'show' clause.
    show materialInputDirectives;
         ^^^^^^^^^^^^^^^^^^^^^^^
bazel-out/local-fastbuild/bin/dashboard_layout_demo.build/lib/src/layout/drawer_button/drawer_button_component.dart:5:10:
Hint: Library 'package:angular2_components/angular2_components.dart' doesn't export a 'GlyphComponent' declaration.
Try removing 'GlyphComponent' from the 'show' clause.
    show GlyphComponent;
         ^^^^^^^^^^^^^^
bazel-out/local-fastbuild/bin/dashboard_layout_demo.build/lib/src/layout/navigation_link/navigation_link_component.dart:5:10:
Hint: Library 'package:angular2_components/angular2_components.dart' doesn't export a 'GlyphComponent' declaration.
Try removing 'GlyphComponent' from the 'show' clause.
    show GlyphComponent;
         ^^^^^^^^^^^^^^
bazel-out/local-fastbuild/bin/dashboard_layout_demo.build/web/dashboard_layout_demo.dart:
Warning:
****************************************************************
* WARNING: dart:mirrors support in dart2js is experimental,
*          and not recommended.
*          This implementation of mirrors is incomplete,
*          and often greatly increases the size of the generated
*          JavaScript code.
*
* Your app imports dart:mirrors via:
*   dashboard_layout_demo.dart => package:angular2 => dart:mirrors
*
* You can disable this message by using the --enable-experimental-mirrors
* command-line flag.
*
* To learn what to do next, please visit:
*    http://dartlang.org/dart2js-reflection
****************************************************************

bazel-out/local-fastbuild/bin/dashboard_layout_demo.build/lib/demo/dashboard_layout/dashboard_layout_demo_app_component.dart:28:7:
Error: Not a compile-time constant.
      materialInputDirectives
      ^^^^^^^^^^^^^^^^^^^^^^^
bazel-out/local-fastbuild/bin/dashboard_layout_demo.build/lib/demo/dashboard_layout/dashboard_layout_demo_app_component.dart:28:7:
Error: Not a compile-time constant.
      materialInputDirectives
      ^^^^^^^^^^^^^^^^^^^^^^^
bazel-out/local-fastbuild/bin/dashboard_layout_demo.build/lib/src/layout/drawer_button/drawer_button_component.dart:10:39:
Error: Not a compile-time constant.
    directives: const <dynamic>[NgIf, GlyphComponent],
                                      ^^^^^^^^^^^^^^
bazel-out/local-fastbuild/bin/dashboard_layout_demo.build/lib/src/layout/drawer_button/drawer_button_component.dart:10:39:
Error: Not a compile-time constant.
    directives: const <dynamic>[NgIf, GlyphComponent],
                                      ^^^^^^^^^^^^^^
bazel-out/local-fastbuild/bin/dashboard_layout_demo.build/lib/src/layout/navigation_link/navigation_link_component.dart:13:7:
Error: Not a compile-time constant.
      GlyphComponent,
      ^^^^^^^^^^^^^^
bazel-out/local-fastbuild/bin/dashboard_layout_demo.build/lib/src/layout/navigation_link/navigation_link_component.dart:13:7:
Error: Not a compile-time constant.
      GlyphComponent,
      ^^^^^^^^^^^^^^
bazel-out/local-fastbuild/bin/dashboard_layout_demo.build/lib/demo/dashboard_layout/dashboard_layout_demo_app_component.dart:28:7:
Error: Not a compile-time constant.
      materialInputDirectives
      ^^^^^^^^^^^^^^^^^^^^^^^
bazel-out/local-fastbuild/bin/dashboard_layout_demo.build/lib/demo/dashboard_layout/dashboard_layout_demo_app_component.dart:28:7:
Error: Not a compile-time constant.
      materialInputDirectives
      ^^^^^^^^^^^^^^^^^^^^^^^
bazel-out/local-fastbuild/bin/dashboard_layout_demo.build/lib/src/layout/drawer_button/drawer_button_component.dart:10:39:
Error: Not a compile-time constant.
    directives: const <dynamic>[NgIf, GlyphComponent],
                                      ^^^^^^^^^^^^^^
bazel-out/local-fastbuild/bin/dashboard_layout_demo.build/lib/src/layout/drawer_button/drawer_button_component.dart:10:39:
Error: Not a compile-time constant.
    directives: const <dynamic>[NgIf, GlyphComponent],
                                      ^^^^^^^^^^^^^^
bazel-out/local-fastbuild/bin/dashboard_layout_demo.build/lib/src/layout/navigation_link/navigation_link_component.dart:13:7:
Error: Not a compile-time constant.
      GlyphComponent,
      ^^^^^^^^^^^^^^
bazel-out/local-fastbuild/bin/dashboard_layout_demo.build/lib/src/layout/navigation_link/navigation_link_component.dart:13:7:
Error: Not a compile-time constant.
      GlyphComponent,
      ^^^^^^^^^^^^^^
Hint: 3 warning(s) suppressed in package:bwu_ng_mdl.
Hint: 4 hint(s) suppressed in package:angular2.
Error: Compilation failed.
Target //:dashboard_layout_demo failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 9.392s, Critical Path: 8.76s

pub build output
 (master) $ pub build
Loading source assets...
Loading angular2/transform/codegen, sass, test/pub_serve and dart_to_js_script_rewriter transformers...
Loading angular2 and angular2/transform/reflection_remover transformers... (4.8s)
Building bwu_ng_mdl... (14.0s)
[Info from Dart2JS]:
Compiling bwu_ng_mdl|web/dashboard_layout_demo.dart...
[Warning from Dart2JS]:
web/dashboard_layout_demo.dart:1:139:
Library 'package:angular2/platform/browser_static.dart' doesn't export a 'initReflector' declaration.
Try removing 'initReflector' from the 'show' clause.
import 'dashboard_layout_demo.template.dart' as ngStaticInit;import 'package:angular2/platform/browser_static.dart' show bootstrapStatic, initReflector;import 'dashboard_layout_demo.template.dart' as ngStaticInit;
                                                                                ^^^^^^^^^^^^^
[Warning from Dart2JS on bwu_ng_mdl|web/dashboard_layout_demo.dart]:
packages/angular2_components/src/utils/color/color.dart:102:3:
The class 'Color' overrides 'operator==', but not 'get hashCode'.
  bool operator ==(other) => other is Color && other.rgbString == rgbString;
  ^^^^^^^^^^^^^^^^^^^^^^^
[Dart2JS on bwu_ng_mdl|web/dashboard_layout_demo.dart]:
View the dumped .info.json file at https://dart-lang.github.io/dump-info-visualizer
[Info from Dart2JS]:
Took 0:00:16.182980 to compile bwu_ng_mdl|web/dashboard_layout_demo.dart.
Built 1419 files to "build".

The The class 'Color' overrides 'operator==', but not 'get hashCode'. error is already fixed in angular2_components in master AFAIK.
Dart VM version: 1.21.0-edge.d62e41fcea8fee5aa69f0875eb4f151abfdcc74e (Mon Oct 31 09:15:30 2016) on "linux_x64"

Hi, I'm not sure if this is DDC related? The message says "Warning from Dart2JS" and the bazel build also seems to be using dart2js "WARNING: dart:mirrors support in dart2js is experimental"? Where is DDC being invoked?

I think this is probably a build/bazelify issue so moving to that repo

This issue was moved to dart-lang/bazel#69


pip upgrade not updating beziers version as required in the requirements.txt

Describe the issue
I have been getting fontbakery errors for outline checks and saw that despite upgrading fontbakery to 0.8.10 the beziers version remained at 0.4.0. I have to manually upgrade (via pip) beziers to make the outline checks work again.
To Reproduce

Have a pre 0.8.10 version of fontbakery installed in a Python3.7 virtual environment.
Run pip install --upgrade fontbakery which runs through package upgrades.
Run fontbakery check-universal -F <.ttf file> on a . TTF file
Runs into errors during outline checks:

 >> com.google.fonts/check/outline_alignment_miss
    Are there any misaligned on-curve points?
    with /Users/UT-development/Documents/UniversalThirst/01_UT_types/UT_Meursault/ut-chelt/fonts/Desktop-TrueType/Meursault-Regular.ttf

      Rationale:

      This check heuristically looks for on-curve points which are close to,
      but do not sit on, significant boundary coordinates. For example, a point
      which has a Y-coordinate of 1 or -1 might be a misplaced baseline point.
      As well as the baseline, here we also check for points near the x-height
      (but only for lowercase Latin letters), cap-height, ascender and
      descender Y coordinates.

      Not all such misaligned curve points are a mistake, and sometimes the
      design may call for points in locations near the boundaries. As this
      check is liable to generate significant numbers of false positives, it
      will pass if there are more than 100 reported misalignments.

    ERROR The condition <FontBakeryCondition:outlines_dict>
          had an error: AttributeError: '_TTGlyphGlyf' object has no attribute
          '_glyph'
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/fontbakery/checkrunner.py",
          line 228, in _evaluate_condition
          return None, condition(**args)
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/fontbakery/callable.py", line
          110, in call
          return self.__wrapped__(*args, **kwds)
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/fontbakery/profiles/outline.py
          ", line 25, in outlines_dict
          for codepoint, glyphname in cmap.items()}
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/fontbakery/profiles/outline.py
          ", line 25, in <dictcomp>
          for codepoint, glyphname in cmap.items()}
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/beziers/path/init.py", line
          126, in fromFonttoolsGlyph
          _glyph = font.getGlyphSet()[glyphname]._glyph

    Result: ERROR

 >> com.google.fonts/check/outline_short_segments
    Are any segments inordinately short?
    with /Users/UT-development/Documents/UniversalThirst/01_UT_types/UT_Meursault/ut-chelt/fonts/Desktop-TrueType/Meursault-Regular.ttf

      Rationale:

      This check looks for outline segments which seem particularly short (less
      than 0.6% of the overall path length).

      This check is not run for variable fonts, as they may legitimately have
      short segments. As this check is liable to generate significant numbers
      of false positives, it will pass if there are more than 100 reported
      short segments.

    ERROR The condition <FontBakeryCondition:outlines_dict>
          had an error: AttributeError: '_TTGlyphGlyf' object has no attribute
          '_glyph'
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/fontbakery/checkrunner.py",
          line 228, in _evaluate_condition
          return None, condition(**args)
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/fontbakery/callable.py", line
          110, in call
          return self.__wrapped__(*args, **kwds)
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/fontbakery/profiles/outline.py
          ", line 25, in outlines_dict
          for codepoint, glyphname in cmap.items()}
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/fontbakery/profiles/outline.py
          ", line 25, in <dictcomp>
          for codepoint, glyphname in cmap.items()}
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/beziers/path/init.py", line
          126, in fromFonttoolsGlyph
          _glyph = font.getGlyphSet()[glyphname]._glyph

    Result: ERROR

 >> com.google.fonts/check/outline_colinear_vectors
    Do any segments have colinear vectors?
    with /Users/UT-development/Documents/UniversalThirst/01_UT_types/UT_Meursault/ut-chelt/fonts/Desktop-TrueType/Meursault-Regular.ttf

      Rationale:

      This check looks for consecutive line segments which have the same angle.
      This normally happens if an outline point has been added by accident.

      This check is not run for variable fonts, as they may legitimately have
      colinear vectors.

    ERROR The condition <FontBakeryCondition:outlines_dict>
          had an error: AttributeError: '_TTGlyphGlyf' object has no attribute
          '_glyph'
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/fontbakery/checkrunner.py",
          line 228, in _evaluate_condition
          return None, condition(**args)
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/fontbakery/callable.py", line
          110, in call
          return self.__wrapped__(*args, **kwds)
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/fontbakery/profiles/outline.py
          ", line 25, in outlines_dict
          for codepoint, glyphname in cmap.items()}
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/fontbakery/profiles/outline.py
          ", line 25, in <dictcomp>
          for codepoint, glyphname in cmap.items()}
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/beziers/path/init.py", line
          126, in fromFonttoolsGlyph
          _glyph = font.getGlyphSet()[glyphname]._glyph

    Result: ERROR

 >> com.google.fonts/check/outline_jaggy_segments
    Do outlines contain any jaggy segments?
    with /Users/UT-development/Documents/UniversalThirst/01_UT_types/UT_Meursault/ut-chelt/fonts/Desktop-TrueType/Meursault-Regular.ttf

      Rationale:

      This check heuristically detects outline segments which form a
      particularly small angle, indicative of an outline error. This may cause
      false positives in cases such as extreme ink traps, so should be regarded
      as advisory and backed up by manual inspection.

    ERROR The condition <FontBakeryCondition:outlines_dict>
          had an error: AttributeError: '_TTGlyphGlyf' object has no attribute
          '_glyph'
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/fontbakery/checkrunner.py",
          line 228, in _evaluate_condition
          return None, condition(**args)
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/fontbakery/callable.py", line
          110, in call
          return self.__wrapped__(*args, **kwds)
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/fontbakery/profiles/outline.py
          ", line 25, in outlines_dict
          for codepoint, glyphname in cmap.items()}
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/fontbakery/profiles/outline.py
          ", line 25, in <dictcomp>
          for codepoint, glyphname in cmap.items()}
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/beziers/path/init.py", line
          126, in fromFonttoolsGlyph
          _glyph = font.getGlyphSet()[glyphname]._glyph

    Result: ERROR

 >> com.google.fonts/check/outline_semi_vertical
    Do outlines contain any semi-vertical or semi-horizontal lines?
    with /Users/UT-development/Documents/UniversalThirst/01_UT_types/UT_Meursault/ut-chelt/fonts/Desktop-TrueType/Meursault-Regular.ttf

      Rationale:

      This check detects line segments which are nearly, but not quite, exactly
      horizontal or vertical. Sometimes such lines are created by design, but
      often they are indicative of a design error.

      This check is disabled for italic styles, which often contain
      nearly-upright lines.

    ERROR The condition <FontBakeryCondition:outlines_dict>
          had an error: AttributeError: '_TTGlyphGlyf' object has no attribute
          '_glyph'
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/fontbakery/checkrunner.py",
          line 228, in _evaluate_condition
          return None, condition(**args)
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/fontbakery/callable.py", line
          110, in call
          return self.__wrapped__(*args, **kwds)
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/fontbakery/profiles/outline.py
          ", line 25, in outlines_dict
          for codepoint, glyphname in cmap.items()}
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/fontbakery/profiles/outline.py
          ", line 25, in <dictcomp>
          for codepoint, glyphname in cmap.items()}
          ↳ File "/Users/UT-development/Documents/_Programming/testing_environme
          nts/FMake32/lib/python3.7/site-packages/beziers/path/init.py", line
          126, in fromFonttoolsGlyph
          _glyph = font.getGlyphSet()[glyphname]._glyph

    Result: ERROR

Suggested behavior
The upgrade is not effecting the beziers package. Version remains at 0.4.0 instead of bumping up to 0.5.0.
Additional context
I'm running fontbakery in a virtual environment under Python 3.7

I’m running into this as well. So, @kalapi, it works once you do upgrade the beziers package to 0.5.0?

@arrowtype yes, fixes it. You can pip install --upgrade beziers inside the virtual environment.

Awesome, thank you for the quick and helpful reply!


[TOPI, CUDA] Bug fix properly bind gpu threads to injective op

We had an interesting error report on the discussion forum, where reshape op is fused into convolution. In picture, it looks like this. Nodes in red are fused by NNVM. This fusion happens without the recent change I made in #1548.

The error occurred for cuda target because reshape op, which is an injective op,  is not bound gpu threads when fused with convolution. The output of tvm.lower(...) is below.
lower function  fuse_reshape_broadcast_mul_conv2d_broadcast_add_1
// attr [tensor] storage_scope = "global"
allocate tensor[float32 * 1 * 16 * 1 * 1]
produce tensor {
  for (ax1, 0, 16) {
    tensor[ax1] = input0[ax1]
  }
}
produce tensor {
  // attr [iter_var(blockIdx.z, , blockIdx.z)] thread_extent = 1
  // attr [compute] storage_scope = "local"
  allocate compute[float32 * 2 * 4 * 1 * 1 * 1 * 1]
  // attr [pad_temp.shared] storage_scope = "shared"
  allocate pad_temp.shared[float32 * 1 * 8 * 1 * 56]
  // attr [input2.shared] storage_scope = "shared"
  allocate input2.shared[float32 * 32 * 8 * 1 * 1]
  // attr [iter_var(blockIdx.y, , blockIdx.y)] thread_extent = 56
  // attr [iter_var(blockIdx.x, , blockIdx.x)] thread_extent = 2
  // attr [iter_var(threadIdx.y, Range(min=0, extent=28), threadIdx.y)] thread_extent = 28
  // attr [iter_var(threadIdx.x, Range(min=0, extent=8), threadIdx.x)] thread_extent = 8
  produce compute {
    compute[0] = 0.000000f
    compute[4] = 0.000000f
    compute[1] = 0.000000f
    compute[5] = 0.000000f
    compute[2] = 0.000000f
    compute[6] = 0.000000f
    compute[3] = 0.000000f
    compute[7] = 0.000000f
    for (rx.ry.fused.rc.outer.fused, 0, 18) {
      produce pad_temp.shared {
        for (ax3.outer, 0, 2) {
          pad_temp.shared[((threadIdx.y + (threadIdx.x*56)) + (ax3.outer*28))] = tvm_if_then_else((((((1 - ((rx.ry.fused.rc.outer.fused % 9)/3)) <= blockIdx.y) && (blockIdx.y < (57 - ((rx.ry.fused.rc.outer.fused % 9)/3)))) && (((1 - (ax3.outer*28)) - ((rx.ry.fused.rc.outer.fused % 9) % 3)) <= threadIdx.y)) && (threadIdx.y < ((57 - (ax3.outer*28)) - ((rx.ry.fused.rc.outer.fused % 9) % 3)))), input1[((((((((blockIdx.y*56) + threadIdx.y) + (threadIdx.x*3136)) + ((rx.ry.fused.rc.outer.fused/9)*25088)) + (((rx.ry.fused.rc.outer.fused % 9)/3)*56)) + ((rx.ry.fused.rc.outer.fused % 9) % 3)) + (ax3.outer*28)) + -57)], 0.000000f)
        }
      }
      produce input2.shared {
        for (ax0.outer, 0, 2) {
          if (likely((threadIdx.y < (32 - (ax0.outer*28))))) {
            if (likely(((blockIdx.x*32) < ((16 - (ax0.outer*28)) - threadIdx.y)))) {
              input2.shared[(((threadIdx.y*8) + threadIdx.x) + (ax0.outer*224))] = input2[((((((((blockIdx.x*32) + threadIdx.y)*16) + threadIdx.x) + ((rx.ry.fused.rc.outer.fused/9)*8))*9) + (rx.ry.fused.rc.outer.fused % 9)) + (ax0.outer*4032))]
            }
          }
        }
      }
...

I replaced the use of tag.is_broadcast with tag.is_injective to make sure injective ops as well as broadcast ops are inlined correctly. But I'm not quite sure if this is a valid change, so please review @tqchen @Laurawly @merrymercy . If this looks good, then I should replace other uses of tag.is_broadcast() within other backends.
I added a simplified test case which fails without this PR.

This seems to be the problem of the fusor, as currently we do not encourage fusing of injective op into conv2d

ok, close it for now.
But to change fusor, we need to realize conv + batchnorm and broadcast_mul before the final elemwise_add. I think the logic becomes very tricky.

The fusor's logic should enforce broadcast_mul not being fused into conv2d+bn, because broadcast_mul should be marked as injective(due to it is being fused into reshape)

The difficulty seems to be that broadcast_mul is a sibling node of conv + bn, so it cannot 'see' conv + bn node during the initial partitioning stage. But they are both assigned FuseRule::kFuseToMaster to elemwise_add at the bottom, so they are fused during the last grouping stage.

We should be able to check the fused type of the group, which is injective instead of elemwise

ok, my plan is as follows:

During the initial partition step, if injective op is followed by broadcast op, mark broadcast op's op pattern to be injective
During the last grouping step, check for input nodes op patterns. If one of them is kOutEWiseFusable and the other is kInjective, ignore the  kOutEWiseFusable node and fuse only kInjective node.


Intellisense Fault - (window.open) funtion in HTML/JavaScript

 <button id="pkc1" class="dlink" onclick=open("https://en.wikipedia.org/wiki/Titanic_(1997_film)","_blank","width=450,height=500,left=1000,top=200");>
Titanic [1997]
</button>

<button id="pkc2" class="dlink" onclick=open("https://www.facebook.com","_blank","width=450,height=500,left=1000,top=200");>
Kesari [2020]
</button>

These are the two button where I used javascript function to open this link in new custom size window.
The code I witten is working properly as I want .
BUT,
Problem Tab in VS code shows that it has some error as in screenshot.
If I will follow the instruction as VS code display then code will break custom function never will open , i.e value will not pass to the function.
Note : - According to AI, these errors were fixed when I used closing parenthesis just after opening parenthesis but the fact is that it breaks my custom function.
Thanks for this outstanding app, wish you will made VS code even better for us.

onclick=open("https://www.facebook.com","_blank","width=450,height=500,left=1000,top=200");>
Kesari [2020]
</button> is not valid.
The HTML spec forbids double quote characters in unquotesd values:
https://www.w3.org/TR/2012/WD-html-markup-20120329/syntax.html#attr-value-unquoted
I suggest to put quotes around the value:
onclick='open("https://www.facebook.com","_blank","width=450,height=500,left=1000,top=200");'>Kesari [2020]


Change disk_space_warning_threshold from 5.0 to 0.05

fixed in https://github.com/apache/iotdb/pull/7909


modImplementation failure

the modImplementations in readme.md don't work in projects, but jitpack did like so:
modImplementation 'com.github.NucleoidMC.DisguiseLib:disguiselib-fabric:1.0.3'
Although, since 1.0.4 (and in future releases) jitpack fails compilation with an older version of java, so this workaround no longer works, and the readme modImplementation also seems to fail.

You should just use nucleoid's maven. The library is there, so not sure why it failed https://maven.nucleoid.xyz/xyz/nucleoid/disguiselib-fabric/1.0.4/

If you don't need forge / common version, nucleoid maven is the way to go as Patbox mentioned.
I can implement a fix for jitpack though (I think TheEpicBlock mentioned it).


Use ansible_host from inventory to replace k8s API IP address

Description
In some use-cases the ['ansible_default_ipv4']['address'] does not point to the correct interface, this PR aims to fix that by using the ansible_host IP address from the inventory.
Type of change

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

How Has This Been Tested?
Ran my playbook and observe that the first host among masters is being replaced in the kubeconfig file.

Yeah that make sense. lgtm


Make state && city text entry only appear if they do not select CoderDojo

Business Case
We added state & city text fields. However, these are unnecessary when they have selected a Dojo since we know where the Dojo is.
Task

[ ] Only show State && City text fields under the same rules as the please describe field when they select CodeClub etc. IE they do not show up if you select a Dojo.

And 90% of the time they do select a Dojo.

[ ] (TBC) Currently is we select Dojo we put int the Dojo ID. If it's easy to can we put the state/city in automatically from the Dojo information rather than be blank? If it's easy it would be a nice addition for browsing this information in the admin panel. If not that's ok.

For the CoderDojo "autofill" ones
From the API we can use place into the town/city field. If there's no even half decent guess for county/state in the API then just leave it blank in the platform.


trouble using dlib/dnn.h

dlib 19.7 installed. using visual studio 2015. cuda 8.0 installed. visual studio is set up to build cuda 8.0 programs. I've added dlib/all/source.cpp to my project.
I successfully built and ran the 3D point cloud app.
However, this program
#include <dlib/dnn.h>
int main()
{
	exit(0);
}

generates the following error messages
1>------ Build started: Project: dlib-test, Configuration: Debug x64 ------
1>  baz.cpp
1>e:\src\dlib-19.7\dlib\dnn\core.h(254): error C2995: 'alwaysbool<unknown-type>::type dlib::impl::backward_requires_forward_output(layer_type &,SUBNET &)': function template has already been defined
1>  e:\src\dlib-19.7\dlib\dnn\core.h(239): note: see declaration of 'dlib::impl::backward_requires_forward_output'
1>e:\src\dlib-19.7\dlib\dnn\core.h(290): error C2995: 'alwaysbool2<unknown-type>::type dlib::impl::has_inplace_backward(layer_type &,SUBNET &)': function template has already been defined
1>  e:\src\dlib-19.7\dlib\dnn\core.h(275): note: see declaration of 'dlib::impl::has_inplace_backward'
1>e:\src\dlib-19.7\dlib\dnn\core.h(350): error C2995: 'unknown-type dlib::impl::call_layer_backward(layer_type &,const dlib::tensor &,const dlib::tensor &,SUBNET &,dlib::tensor &)': function template has already been defined
1>  e:\src\dlib-19.7\dlib\dnn\core.h(329): note: see declaration of 'dlib::impl::call_layer_backward'
1>e:\src\dlib-19.7\dlib\dnn\core.h(410): error C2995: 'unknown-type dlib::impl::call_layer_forward(layer_type &,const SUBNET &,dlib::tensor &)': function template has already been defined
1>  e:\src\dlib-19.7\dlib\dnn\core.h(378): note: see declaration of 'dlib::impl::call_layer_forward'
1>e:\src\dlib-19.7\dlib\dnn\core.h(422): error C2995: 'unknown-type dlib::impl::call_layer_forward(layer_type &,const SUBNET &,dlib::resizable_tensor &)': function template has already been defined
1>  e:\src\dlib-19.7\dlib\dnn\core.h(393): note: see declaration of 'dlib::impl::call_layer_forward'
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

The dnn example programs don't build either, but let's see if fixing the above also fixes the other issues.

To make it clear, my include path is effectively "e:\src\dlib-19.7" . I wasn't expecting the code meta to reformat the error message; sorry about that.

You probably have an older version of visual studio 2015.  see http://dlib.net/faq.html#WhycantIusetheDNNmodulewithVisualStudio.

Indeed I did. Updated to update 3 and things compile now. I didn't think the FAQ would address a compile issue, so didn't check it. I now have read the FAQ fully. Do you have a recommended compiler for Windows 10 that works with all of the machine learning code in dlib?

Clang or GCC will work fine.  Really any C++11 compiler.

OK, thanks. I am used to the VS2015 IDE, so won't change until I actually have to. Closing.

You can use clang with visual studio’s IDE.

clang_c2 installed. After working around the IUnknown error by adding the following to source.cpp
#if defined(c2) &&  clang_major == 3 && clang_minor == 8
//To avoid compile error
//C:\Program Files (x86)\Windows Kits\8.1\Include\um\combaseapi.h(229,21): error : unknown type name 'IUnknown'
//          static_cast<IUnknown*>(*pp);    // make sure everyone derives from IUnknown
struct IUnknown;
#endif
I now crash in the clang compiler with the following error message
1>  'union __m128 __cdecl _mm_cvtepi32_ps(union __m128i)': Intrinsic not yet implemented:
1>    %4 = call <4 x float> @llvm.x86.sse2.cvtdq2ps(<4 x i32> %3)
1>E:\src\dlib-test\dlib-test\source.cpp : fatal error C1001: An internal error has occurred in the compiler.
1>  (compiler file 'llvm-bridge.cpp', line 5757)
1>   To work around this problem, try simplifying or changing the program near the locations listed above.
Since I don't actually need clang at the moment, I'm going to assume the above problem will eventually be fixed.

How did you install clang?  I've used the version here
http://prereleases.llvm.org/win-snapshots/LLVM-5.0.0-r306282-win64.exe and
it worked well.

See also the discussion here https://github.com/davisking/dlib/pull/772

I installed clang using the Visual Studio 2015 installer.
I also installed clang using your link above, and using the LLVM-vs2014 platform toolset, I was able to build successfully.
There are a lot of warning messages though. What's your recommendation about them?

Don't worry about them.  I honestly haven't looked at them though.  I don't use visual studio very much anymore.  I do have regular unit tests run against visual studio.  But it's not a very good C++ compiler.  One of it's many problems is the absurd warnings it gives out.  I often disable them in the code, but I haven't gone through and dealt with them in a while.  As a few examples, visual studio will give warnings saying that some parts of the standard C++ library are deprecated and that you should use functions that only exist on windows.    There are also a lot of warnings about internal imitations of visual studio or even about bug fixes in their compiler.
If you use a normal version of GCC or clang you shouldn't see any warnings.  But for visual studio you might see some.

The warning messages were from my using the Visual Studio IDE with the clang 5.0 C++ front end, not the Microsoft C++ compiler.  Here's one of them. (I'm ignoring the ones from source.cpp since I'll only see them once.)
1>------ Build started: Project: dlib-test, Configuration: Debug x64 ------
1>clang-cl.exe : warning : argument unused during compilation: '/ZI' [-Wunused-command-line-argument]
1>clang-cl.exe : warning : argument unused during compilation: '/Gm' [-Wunused-command-line-argument]
1>  In file included from baz.cpp:62:
1>  In file included from ....\dlib-19.7\dlib/dnn.h:12:
1>  In file included from ....\dlib-19.7\dlib/dnn/tensor.h:8:
1>  In file included from ....\dlib-19.7\dlib/image_keypoint/../matrix.h:6:
1>  In file included from ....\dlib-19.7\dlib/array2d/../geometry/../matrix/matrix.h:9:
1>  In file included from ....\dlib-19.7\dlib/vectorstream/../serialize.h:158:
1>....\dlib-19.7\dlib/map/../interfaces/enumerable.h(48,24): warning : function definition with pure-specifier is a Microsoft extension [-Wmicrosoft-pure-definition]
1>          inline virtual ~enumerable(
1>                         ^
1>  ....\dlib-19.7\dlib/sequence/sequence_kernel_2.h(61,13):  note: in instantiation of member function 'dlib::enumerabledlib::lbfgs_search_strategy::data_helper::~enumerable' requested here
1>              sequence_kernel_2 (
1>              ^
1>  ....\dlib-19.7\dlib/matrix/../optimization/optimization_search_strategies.h(157,18):  note: in instantiation of member function 'dlib::sequence_kernel_2<dlib::lbfgs_search_strategy::data_helper, dlib::memory_manager_stateless_kernel_1 >::sequence_kernel_2' requested here
1>          explicit lbfgs_search_strategy(unsigned long max_size_) : max_size(max_size_), been_used(false)
1>                   ^
There are eight of the above from including dnn.h (all pure function warnings.) The other warning message is
1>  In file included from baz.cpp:62:
1>  In file included from ....\dlib-19.7\dlib/dnn.h:12:
1>  In file included from ....\dlib-19.7\dlib/dnn/tensor.h:8:
1>  In file included from ....\dlib-19.7\dlib/image_keypoint/../matrix.h:6:
1>  In file included from ....\dlib-19.7\dlib/array2d/../geometry/../matrix/matrix.h:9:
1>  In file included from ....\dlib-19.7\dlib/vectorstream/../serialize.h:162:
1>  In file included from ....\dlib-19.7\dlib/dnn/../byte_orderer.h:7:
1>....\dlib-19.7\dlib/byte_orderer/byte_orderer_kernel_1.h(139,13): warning : unused typedef 'DAHSL2_139' [-Wunused-local-typedef]
1>              DLIB_ASSERT_HAS_STANDARD_LAYOUT(T);
1>              ^
1>  ....\dlib-19.7\dlib/map/../assert.h(191,38):  note: expanded from macro 'DLIB_ASSERT_HAS_STANDARD_LAYOUT'
1>      DLIB_NO_WARN_UNUSED typedef char BOOST_JOIN(DAHSL2_,LINE)[sizeof(BOOST_JOIN(DAHSL_,LINE))];
1>                                       ^
1>  ....\dlib-19.7\dlib/map/../assert.h(24,28):  note: expanded from macro 'BOOST_JOIN'
1>  #define BOOST_JOIN( X, Y ) BOOST_DO_JOIN( X, Y )
1>                             ^
1>  ....\dlib-19.7\dlib/map/../assert.h(25,31):  note: expanded from macro 'BOOST_DO_JOIN'
1>  #define BOOST_DO_JOIN( X, Y ) BOOST_DO_JOIN2(X,Y)
1>                                ^
1>  ....\dlib-19.7\dlib/map/../assert.h(26,32):  note: expanded from macro 'BOOST_DO_JOIN2'
1>  #define BOOST_DO_JOIN2( X, Y ) X##Y
1>                                 ^
1>  (66,1):  note: expanded from here
1>  DAHSL2_139
1>  ^
1>  9 warnings generated.
1>  dlib-test.vcxproj -> E:\src\dlib-test\x64\Debug\dlib-test.exe
1>  dlib-test.vcxproj -> E:\src\dlib-test\x64\Debug\dlib-test.pdb (Full PDB)
1>  copy "C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\bin\cudart*.dll" "E:\src\dlib-test\x64\Debug"
1>  C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\bin\cudart32_80.dll
1>  C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\bin\cudart64_80.dll
1>          2 file(s) copied.
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

They seem fine.  Although if you want to figure out how to avoid those warnings and submit a pull request with them that would be cool :)

Okay, thanks for your help. I'll put fixing the warnings on my to-do list.

In the Visual Studio IDE, Configuration Properties>C/C++>Command Line, add the following in the Additional Options section to remove nearly all of the warnings:
-Wno-microsoft-pure-definition -Wno-deprecated-declarations -Wno-unused-local-typedef -Wno-exceptions -Wno-unused-command-line-argument
The no-exceptions one might be a little problematical, but I'll leave that to you. I'm aware this is a band-aid, but I'm fine with my local fix to the minor issue.

Thanks for reporting back.  I'll see about improving the warnings in this configuration.

Changing stuff to support clang in VS2015 with no error messages might be a moot issue. See https://stackoverflow.com/questions/38432211/how-do-i-use-other-c-compilers-with-cuda-on-windows ; I can't use clang and compile my own CUDA code, and I don't know how to change the toolset to use for different parts of a project (and don't really want to.) So I'm just going to have to hope I don't run into the limitations of VS2015, or hope Microsoft fixes VS2017. At the moment, I am OK (dnn.h builds with no issues now after updating VS2015 per your comment.) I assume you'll know when VS2017 starts working well again!

Yeah, lack of CUDA support in clang is a bummer.  VC2015 is mostly alright.


Add Markdown preprocessor

Enables selecting fenced code blocks from Markdown text based on selector expressions, as described in the K tutorial:
https://github.com/runtimeverification/k/tree/master/k-distribution/k-tutorial/1_basic/08_literate_programming

Measurements on evm-semantics (time in ms).

File name
md processing
Outer parsing

abi.md
0
5

asm.md
0
2

buf.md
0
0

data.md
0
0

driver.md
0
5

edsl.md
0
0

evm-imp-specs.md
0
1

evm-node.md
0
2

evm-types.md
0
4

evm.md
1
16

foundry.md
1
6

gas.md
0
3

hashed-locations.md
0
0

issues.md
0
0

json-rpc.md
0
1

network.md
0
0

optimizations.md
0
1

schedule.md
0
3

serialization.md
0
7

state-utils.md
0
3

word.md
0
4


Move sota.env from /usr/lib to /etc

The current way for the user to replace the default aktualizr
environment configuration is by copying the original aktualizr.service
to /etc/systemd/system and changing EnvironmentFile to point to a
different file, which is not user friendly.
Change the default environment path from /usr/lib/sota/sota.env to
/etc/sota/sota.env to allow user changes during runtime.
Signed-off-by: Ricardo Salveti<EMAIL_ADDRESS>

I'm a bit worried by this, because it conflicts with our (unstated) goal of moving toward a Stateless system (in the systemd sense of the word).
The intention is that users can put their own settings in /etc, and use those to override our default settings in /usr.  In an ideal world we would have a clean split between:

/etc For local administrator changes (this would often be completely empty)
/var For data files generated by applications (erasing this would be a 'factory reset')
/usr Is read-only application data, managed by the software update system

I think your use-case is reasonable, and we should support it.  Would an alternative be to copy aktualizr.service to /etc, then add modify the config directly using Environment=FOO=bar or by editing the command line directly?
Can you describe a bit more about what you are aiming to change?

I'm a bit worried by this, because it conflicts with our (unstated) goal of moving toward a Stateless system (in the systemd sense of the word).

That's fine, good to know there is also a push to support stateless systems, as then I can also be aligned with that from our side.

I think your use-case is reasonable, and we should support it. Would an alternative be to copy aktualizr.service to /etc, then add modify the config directly using Environment=FOO=bar or by editing the command line directly?

My only issue with duplicating the service file itself is that it can also easily create update issues over time (in case another part of that file gets changed in a newer rev). I guess one possible solution could be having a default environment as we have today, but change the service file to also consume an environment file in /etc if available, something like:
[Service]
RestartSec=10
Restart=always
EnvironmentFile=/usr/lib/sota/sota.env
EnvironmentFile=-/etc/sota/sota.env
ExecStart=/usr/bin/aktualizr $AKTUALIZR_CMDLINE_PARAMETERS

That would make aktualizr work after a factory reset and would also allow the user to change the startup options if required/wanted.
Coming back to the use case itself, our main use case is just playing with aktualizr log level in order to facilitate debugging (but other options could also be set by the user if required/wanted).
Would this work for you?

That is a great solution! I wasn't aware of the '-' prefix on EnvironmentFile, but it is exactly what we want.
I've been stopping the aktualizr service and running it from the console to up the log level, so this will help me too.
If you are debugging the client/server communication, then I recently wrote up some notes for how to dump the ssl session keys so that wireshark can decrypt the traffic: https://github.com/advancedtelematic/aktualizr/blob/master/docs/debugging-tips.adoc#dumping-ssl-encrypted-traffic  These are a bit sparse at the moment, because they are partly there to remind me how to do it.
Thank you!

Is this sufficiently fixed by https://github.com/advancedtelematic/meta-updater/pull/283 to be satisfactorily resolved?

Is this sufficiently fixed by #283 to be satisfactorily resolved?

@patrickvacek yes, thanks for the fix and sorry for the delay, travels after ELC.

If you are debugging the client/server communication, then I recently wrote up some notes for how to dump the ssl session keys so that wireshark can decrypt the traffic: https://github.com/advancedtelematic/aktualizr/blob/master/docs/debugging-tips.adoc#dumping-ssl-encrypted-traffic These are a bit sparse at the moment, because they are partly there to remind me how to do it.

Awesome, thanks for the notes!


NYC Interfering with subprocess signal handling

Expected Behavior
nyc should run tests the same as when the tests are run without NYC
Observed Behavior
nyc, when running mocha unit tests, appears to be doing something with subprocesses spawned with child_process.spawn. Specifically, I have a unit under test that manages subprocesses. These subprocess can be killed. First the default SIGTERM is tried, but if the process does not exit, a SIGKILL is tried a second later. This test passes when run by mocha, but fails when run with nyc and mocha. A reduced test case follows:
Bonus Points! Code (or Repository) that Reproduces Issue
A full gist with code and package.json at: https://gist.github.com/9d663a5fc7076777289c6b4bd3ef53b2
const {spawn} = require('child_process')
const assert = require('assert')
describe('nyc doing weird stuff...', () => {
  it('should be able to force kill if it times out', (done) => {
    let s = `
    process.on('SIGTERM', function() { console.log('ignore!') })
    setInterval(function() {
      console.log('wtf')
    }, 40)
    `
    const args = ['-e', s.trim()]
    const scr = spawn('node', args)
    scr.stdout.setEncoding('utf8')
    scr.stderr.setEncoding('utf8')
    scr.stdout.on('data', (d) => {
      console.log(d)
    })
    scr.stderr.on('data', (d) => {
      console.log(d)
    })
    let gotStopped = false
    let forceKillTimeout
    function stop(cb) {
      scr.on('exit', (exitCode, signal) => {
        clearTimeout(forceKillTimeout)
        cb(null, 'script killed in response to signal : ' + signal)
      })
      forceKillTimeout = setTimeout(() => scr.kill('SIGKILL'), 1000)
      scr.kill()
    }
    setTimeout(() => {
      stop((err, status) => {
        if (err) return done(err)
        console.log(status)
        assert(status.indexOf('SIGKILL') > -1)
        done()
      })
    }, 150)
  })
})

With just mocha:
$: mocha reducedTest.js
  nyc doing weird stuff...
wtf

ignore!

wtf

wtf
...

script killed in response to signal : SIGKILL
    ✓ should be able to force kill if it times out (1172ms)

  1 passing (1s)

With nyc
$: nyc mocha reducedTest.js
  nyc doing weird stuff...
script killed in response to signal : SIGTERM
    1) should be able to force kill if it times out

  0 passing (176ms)
  1 failing

  1) nyc doing weird stuff... should be able to force kill if it times out:

      Uncaught AssertionError: false == true
      + expected - actual

      -false
      +true

      at stop (reducedTest.js:6:1253)
      at ChildProcess.scr.on (reducedTest.js:6:702)
      at Process.ChildProcess._handle.onexit (internal/child_process.js:204:12)

----------------|----------|----------|----------|----------|----------------|
File            |  % Stmts | % Branch |  % Funcs |  % Lines |Uncovered Lines |
----------------|----------|----------|----------|----------|----------------|
All files       |    81.48 |       50 |    66.67 |       88 |                |
 reducedTest.js |    81.48 |       50 |    66.67 |       88 |       16,19,36 |
----------------|----------|----------|----------|----------|----------------|

Note that no logs are seen from the subprocess in the nyc output even though we wait 150 mills before killing the process.
Forensic Information
Observed in MacOs El Capitan
Output text here: https://gist.github.com/2bbde16e2bcb80e567e6fb1a44f4948d

For kicks, I also run this in linux (under a docker image with node 6.90 and ubuntu 14.04) and had the same issue :(

@addisonj to be able to output coverage information prior to exiting, it's necessary for nyc to override signal-handling. The library https://github.com/tapjs/signal-exit is used to facilitate this.
Unfortunately, nyc would be unable to both collect coverage information from your spawned processes, and not override the signal handlers -- the project signal-exit attempts to be clever however, about maintaining a stack of listeners and firing them appropriately, If you wouldn't mind opening an issue on signal-exit maybe we can figure out a workaround for your tests.

So, interestingly, this works perfectly fine if instead of invoking the script with node -e the script is written to a file and then run, updated snippet:
const {spawn} = require('child_process')
const assert = require('assert')
const fs = require('fs')
describe('nyc doing weird stuff...', () => {
  it('should be able to force kill if it times out', (done) => {
    let s = `
    process.on('SIGTERM', function() { console.log('ignore!') })
    setInterval(function() {
      console.log('wtf')
    }, 40)
    `
    fs.writeFileSync('script.js', s)
    const args = ['script.js']
    const scr = spawn('node', args)
    scr.stdout.setEncoding('utf8')
    scr.stderr.setEncoding('utf8')
    scr.stdout.on('data', (d) => {
      console.log(d)
    })
    scr.stderr.on('data', (d) => {
      console.log(d)
    })
    let gotStopped = false
    let forceKillTimeout
    function stop(cb) {
      scr.on('exit', (exitCode, signal) => {
        clearTimeout(forceKillTimeout)
        cb(null, 'script killed in response to signal : ' + signal)
      })
      forceKillTimeout = setTimeout(() => scr.kill('SIGKILL'), 1000)
      scr.kill()
    }
    setTimeout(() => {
      stop((err, status) => {
        if (err) return done(err)
        console.log(status)
        assert(status.indexOf('SIGKILL') > -1)
        done()
      })
    }, 150)
  })
})

@bcoe this appears to have less to do with signal handling directly and more that with node -e the spawn-wrap doesn't seem to function as expected. Perhaps what node shim spawn-wrap is using does not properly handle the input, mainly, its not running the script to evaluate. That would explain no output from the subprocess as well as immediately dying to a SIGTERM where no handler was installed
@isaacs might be able to confirm if this is a possibility with spawn-wrap?

@addisonj was about to say, it sounds like we should probably carve out an exception in spawn-wrap for -e ... seems reasonable to avoid

👍  I have a workaround I can use for now, fun little diversion in the wonderful hacks to make test coverage work :) Thanks for the great tool!

This is kind of weird, because -e invocations are already explicitly passed through by spawn-wrap's shim.
Here's a test verifying that: https://gist.github.com/isaacs/9b05a4010304bdacd01fd8400fd74d94
Here's where it detects the -e: https://github.com/tapjs/spawn-wrap/blob/master/shim.js#L53
And here's where it says "no main, no wrap": https://github.com/tapjs/spawn-wrap/blob/master/shim.js#L88-L93
So... I'm not sure why the SIGTERM is not getting ignored.

Note that this test also passes when I run with tap --cov test/exec-flag.js or nyc node test/exec-flag.js

@addisonj @isaacs I'll keep this open until I have some time to look that's not just me poking through issues at 11PM -- sounds like a legitimate bug we should address, if we're already attempting to carve out an exception for -e.

A relevant difference in our scripts seems to be that mine is doing process.execPath, and yours is doing 'node'.
The plot thickens!

I believe this comes down to a shortcoming in foreground-child.  The shim is doing its best to re-exec the child as its foreground process, but unless fg gets a bit smarter (and probably slower), it can't reliably know which ones are being caught and ignored by the child process.
What's actually happening is that the parent is killed with SIGTERM, parent (thinking the SIGTERM to be fatal) passes the SIGTERM to the child with its last breath, then kills itself with SIGTERM.  At this point, the child (not killed by the passed-along SIGTERM) keeps on trucking, which is itself rather odd, because I'd think that it should get a fatal SIGHUP (since its parent process has exited).  But it doesn't appear to get a SIGHUP at all.
This works when passing a full path to node, because it doesn't have to do path resolution.  A possible solution would be for spawn-wrap's index.js file to not only not munge 'node' -e calls, but in fact, fully resolve them to the next node executable in the PATH after the spawn-wrap shim.

Since this issue is open, it also conflicts with puppeteer. Here's the issue I reported with them https://github.com/GoogleChrome/puppeteer/issues/763.
And the repo to reproduce the issue https://github.com/thetutlage/puppeteer-tests.
I tried digging into the codebase, and realized foreground-child is where things are getting messy.

@thetutlage If I had to guess, I'd bet the underlying issue is with the spawn-wrap module which is used to hook into exit signals (it might be worth creating an issue here as well).
Would love help digging into this further if you're so inclined 👍

The culprit is almost certainly foreground-child.
Because node does not have support for calling exec without a fork, the best we can do is run the new process with shared stdio, exit with the same status code and signal if the child process exits, and proxy any signals that come to the parent.
This approach has limitations.  Since SIGKILL and SIGSTOP cannot be caught, they can't be proxied either.  On windows, a few other signals also can't be caught and ignored, such as SIGTERM.
Without adding support for exec-without-fork, either in node core or via a binary addon, there's no other way to do the kinds of things that spawn-wrap (and thus, nyc) need to do in a consistent way.

Ah, in the issue referenced with GoogleChrome/puppeteer#763, it seems like the issue is just istanbul as such, since they are relying on consistent toString() output from functions.  If those functions are munged, their code will definitely change.  Maybe istanbul could transform functions such that toString was preserved?  I don't know.

@addisonj there have been quite a few changes to spawn-wrap since this issue was originally open, and it sounds like you've figured out work arounds. Mind if I close this out?
@thetutlage it sounds like there are issues specifically related to puppeteer  and should have its own issue. If I understand properly puppeteer injects code into a browser context, and is using the toString() on a function to perform magic?
It feels like we'd probably need to coordinate a fix or workaround between the two projects.

@bcoe Great that u guys are in favor of coordinating and getting a fix out.
Also, I agree that they run the code in browser context and ideally it nyc may have nothing to do with that and same goes for puppeteer since they have a generic library to automate browser tasks.
But I am 100% sure that going forward, lots of testing engine implementations will be written in puppeteer and this issue will arise again.
I am happy to help in any way I can. Maybe creating appropriate issues with enough context, or digging into some code ( may need some guidance for that )
Thanks again 😄


kontena/lb sticky session / backend affinity

My app is a classic symfony2 web app. I'm testing scaling.
I noticed that haproxy is not configured neither to use ip-based backend affinity nor sticky session.
Is there a way to fix that?

You can change this behaviour via KONTENA_LB_BALANCE env variable. For ip based affinity value should be source.
These env variables are documented here: http://www.kontena.io/docs/using-kontena/loadbalancer .


Rename FactBaseBuilder

The name of the FactBaseBuilder class isn't the clearest and doesn't really give a good sense of why it is needed or how it is used.
The goal of a FactBaseBuilder object is to take a list of clingo Symbol objects and to extract facts from this list by unifying against the registered Predicate sub-classes. While the extracted facts (i.e., the instances of the Predicate sub-classes) are indeed returned in a FactBase object, however this is bit besides the point of the core functionality of what FactBaseBuilder is doing. For example, it could have been returned in a standard python list, but it happens that a FactBase is more useful for subsequent querying.
So need to think of some better names; PredicateUnifier or FactUnifier or maybe just Unifier. FactGenerator? Or SymbolPredicateUnifier?

Renamed to SymbolPredicateUnifier but also refactored and simplified the API a little so that in most cases you don't need to use it.


crash at >>

#[derive(Copy, Clone)]
pub struct StdCounter<T: Zero + Add<T, Output = T> + Sub<T, Output = T>> {
    pub value: T
}

error is
thread '<main>' panicked at 'called `Result::unwrap()` on an `Err` value: IllFormedSpan(Span { lo: BytePos(190), hi: BytePos(189), expn_id: ExpnId(4294967295) })', ../src/libcore/result.rs:734

Pretty sure this is due to a libsyntax error (https://github.com/rust-lang/rust/issues/28158), but in case it isn't lets track it here too.

I get the a similar IllFormedSpan error on this snippet, which compiles fine with rustc itself. Does that mean it's not a libsyntax error?
fn main() {
    match () {_ => () }
}

Similarly inserting a space between the { and the _ fixes it.

@ben0x539 No, we use more spans than rustc and (more importantly) use them in more interesting ways.

And another example (from liballoc):
fn homura<T: Deref<Target=i32>>(_: T) { }

Should be fixed by https://github.com/rust-lang/rust/pull/28291


Building export templates (release & release_debug) X11 failed (core/rid.h)

Impossible to compile export templates  for X11
scons platform=x11 ->  works
but:
scons platform=x11 tools=no target=release_debug bits=64 -> failed
scons platform=x11 tools=no target=release bits=64 -> failed
scons platform=x11 tools=no target=release bits=64
scons: Reading SConscript files ...
i586-mingw32msvc-gcc (GCC) 4.2.1-sjlj (mingw32-2)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

i686-w64-mingw32-gcc (GCC) 4.8.2
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Enabling ALSA
Enabling PulseAudio
scons: done reading SConscript files.
scons: Building targets ...
g++ -o platform/x11/godot_x11.x11.opt.64.o -c -O3 -ffast-math -DNDEBUG -DFREETYPE_ENABLED -DENABLE_DEPRECATED -DOPENGL_ENABLED -DALSA_ENABLED -DJOYDEV_ENABLED -DPULSEAUDIO_ENABLED -DX11_ENABLED -DUNIX_ENABLED -DGLES2_ENABLED -DGLES_OVER_GL -DGDSCRIPT_ENABLED -DMINIZIP_ENABLED -DXML_ENABLED -DGLAD_ENABLED -DGLES_OVER_GL -D_REENTRANT -Icore -Icore/math -Itools -Idrivers -I. -Iplatform/x11 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/alsa -Iplatform/x11 platform/x11/godot_x11.cpp
In file included from core/ref_ptr.h:37:0,
                 from core/variant.h:50,
                 from core/object.h:33,
                 from core/os/input.h:32,
                 from platform/x11/os_x11.h:33,
                 from platform/x11/godot_x11.cpp:30:
core/rid.h: In member function 'bool RID_OwnerBase::_is_owner(RID&) const':
core/rid.h:118:22: error: 'class RID' has no member named '_owner'
   return this==p_rid._owner;
                      ^
core/rid.h: In member function 'void RID_OwnerBase::_remove_owner(RID&)':
core/rid.h:124:16: error: 'class RID' has no member named '_owner'
   return p_rid._owner=NULL;
                ^
In file included from /usr/include/string.h:32:0,
                 from core/os/copymem.h:40,
                 from core/os/input_event.h:34,
                 from core/variant.h:47,
                 from core/object.h:33,
                 from core/os/input.h:32,
                 from platform/x11/os_x11.h:33,
                 from platform/x11/godot_x11.cpp:30:
core/rid.h:124:23: error: return-statement with a value, in function returning 'void' [-fpermissive]
   return p_rid._owner=NULL;
                       ^
scons: *** [platform/x11/godot_x11.x11.opt.64.o] Error 1
scons: building terminated because of errors.

scons platform=x11 tools=no target=release_debug bits=64
scons: Reading SConscript files ...
i586-mingw32msvc-gcc (GCC) 4.2.1-sjlj (mingw32-2)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

i686-w64-mingw32-gcc (GCC) 4.8.2
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Enabling ALSA
Enabling PulseAudio
scons: done reading SConscript files.
scons: Building targets ...
g++ -o scene/3d/gi_probe.x11.opt.debug.64.o -c -O2 -ffast-math -DDEBUG_ENABLED -DFREETYPE_ENABLED -DENABLE_DEPRECATED -DOPENGL_ENABLED -DALSA_ENABLED -DJOYDEV_ENABLED -DPULSEAUDIO_ENABLED -DX11_ENABLED -DUNIX_ENABLED -DGLES2_ENABLED -DGLES_OVER_GL -DGDSCRIPT_ENABLED -DMINIZIP_ENABLED -DXML_ENABLED -DGLAD_ENABLED -DGLES_OVER_GL -D_REENTRANT -Icore -Icore/math -Itools -Idrivers -I. -Iplatform/x11 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/alsa -Iscene/3d scene/3d/gi_probe.cpp
scene/3d/gi_probe.cpp: In member function 'void GIProbe::_create_debug_mesh(GIProbe::Baker*)':
scene/3d/gi_probe.cpp:1317:18: error: 'class SceneTree' has no member named 'get_edited_scene_root'
  if (get_tree()->get_edited_scene_root()==this){
                  ^
scons: *** [scene/3d/gi_probe.x11.opt.debug.64.o] Error 1
scons: building terminated because of errors.

We're typically at a stage where, with no indication of what version you tried to compile, this report is not as useful as it should be.

Version given in version.py
short_name = "godot"
name = "Godot Engine"
major = 3
minor = 0
status = "alpha"

obsolete, closing


[DRAFT] feat(github): add code for listing/reviewing/getting PRs on Github

Description
Adding functionality to List, Review and Get info on Github PRs.
Pending adding functionality to get PR diffs(right now it's not returned). Will mark as ready once finishing that.
Server Details

Server: github
Changes to: tools

Motivation and Context
Thought of adding functionality to review and list PRs on private/public repos on Github.
How Has This Been Tested?
Verified manually via Claude Desktop.
Breaking Changes
None.
Types of changes

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

Checklist

[x] I have read the MCP Protocol Documentation
[x] My changes follows MCP security best practices
[x] I have updated the server's README accordingly
[x] I have tested this with an LLM client
[x] My code follows the repository's style guidelines
[x] New and existing tests pass locally
[x] I have added appropriate error handling
[x] I have documented all environment variables and configuration options

Additional context
n/a

Thanks! Converting this to a draft to make its status clear. Please mark as "ready for review" when you'd like us to take a look!


[TAG]<EMAIL_ADDRESS>

[TAG]<EMAIL_ADDRESS>version bump only.

includes: #41

Need to break out tag to different branch and merge due to recent main branch commits.


Drop openstack-ironic-staging-drivers from ironic-condutor

https://issues.redhat.com/browse/OSPRH-5427 drops the openstack-ironic-staging-drivers from OSP-18 and package is removed from downstream dlrn builds, leading to failure in building ironic conductor container image.
Dropping this package from tcib fixes the issue.
Closes: https://issues.redhat.com/browse/OSPCIX-218

/lgtm


Fail to build on MacBook Pro 14 with M1 Pro

| Camera Model                       | D455 |
| Firmware Version                   | (Open RealSense Viewer --> Click info) |
| Operating System & Version |  MacOS  Monterey|
| Platform                                 | MacBook Pro 14 (2021)  |
| SDK Version                            | librealsense-2.49.0 |
| Language                            |  {C/C#/labview/nodejs/opencv/pcl/python/unity }                          |
| Segment			|  Robot |
Issue Description
Hello,
I am following the steps from https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_osx.md to build the SDK on my MacBook Pro. I have done some tweaks according to https://www.yuque.com/docs/share/e97e0cca-7532-424b-b3ca-b69906651779 and added the following
set(CMAKE_THREAD_LIBS_INIT "-lpthread")
set(CMAKE_HAVE_THREADS_LIBRARY 1)
set(CMAKE_USE_WIN32_THREADS_INIT 0)
set(CMAKE_USE_PTHREADS_INIT 1)
set(THREADS_PREFER_PTHREAD_FLAG ON)

in CMakeLists.txt above the build folder. This is the error message I am getting
[ 48%] Linking CXX shared library librealsense2.dylib
ld: library not found for -latomic
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [librealsense<IP_ADDRESS>.dylib] Error 1
make[1]: *** [CMakeFiles/realsense2.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
HEAD is now at 2f33be817 RELEASE-NOTES: synced
[ 48%] No update step for 'libcurl'
[ 49%] No patch step for 'libcurl'
[ 49%] Performing configure step for 'libcurl'
-- The C compiler identification is AppleClang <IP_ADDRESS>00029
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc - broken
CMake Error at /opt/homebrew/Cellar/cmake/3.22.0/share/cmake/Modules/CMakeTestCCompiler.cmake:69 (message):
  The C compiler

    "/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: /Users/du/development_local/intel_realsense/librealsense-2.49.0/build/libcurl/src/libcurl-build/CMakeFiles/CMakeTmp

    Run Build Command(s):/usr/bin/make -f Makefile cmTC_783be/fast && /Applications/Xcode.app/Contents/Developer/usr/bin/make  -f CMakeFiles/cmTC_783be.dir/build.make CMakeFiles/cmTC_783be.dir/build
    Building C object CMakeFiles/cmTC_783be.dir/testCCompiler.c.o
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc   -pedantic -g -D_DEFAULT_SOURCE   -mfpu=neon -mfloat-abi=hard -ftree-vectorize -latomic -pthread  -arch arm64 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.0.sdk -MD -MT CMakeFiles/cmTC_783be.dir/testCCompiler.c.o -MF CMakeFiles/cmTC_783be.dir/testCCompiler.c.o.d -o CMakeFiles/cmTC_783be.dir/testCCompiler.c.o -c /Users/du/development_local/intel_realsense/librealsense-2.49.0/build/libcurl/src/libcurl-build/CMakeFiles/CMakeTmp/testCCompiler.c
    clang: warning: -latomic: 'linker' input unused [-Wunused-command-line-argument]
    clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
    clang: warning: argument unused during compilation: '-mfloat-abi=hard' [-Wunused-command-line-argument]
    Linking C executable cmTC_783be
    /opt/homebrew/Cellar/cmake/3.22.0/bin/cmake -E cmake_link_script CMakeFiles/cmTC_783be.dir/link.txt --verbose=1
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc    -pedantic -g -D_DEFAULT_SOURCE   -mfpu=neon -mfloat-abi=hard -ftree-vectorize -latomic -pthread  -arch arm64 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.0.sdk -Wl,-search_paths_first -Wl,-headerpad_max_install_names CMakeFiles/cmTC_783be.dir/testCCompiler.c.o -o cmTC_783be
    ld: library not found for -latomic
    clang: error: linker command failed with exit code 1 (use -v to see invocation)
    make[4]: *** [cmTC_783be] Error 1
    make[3]: *** [cmTC_783be/fast] Error 2

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:48 (project)

-- Configuring incomplete, errors occurred!
See also "/Users/du/development_local/intel_realsense/librealsense-2.49.0/build/libcurl/src/libcurl-build/CMakeFiles/CMakeOutput.log".
See also "/Users/du/development_local/intel_realsense/librealsense-2.49.0/build/libcurl/src/libcurl-build/CMakeFiles/CMakeError.log".
make[2]: *** [libcurl/src/libcurl-stamp/libcurl-configure] Error 1
make[1]: *** [CMakeFiles/libcurl.dir/all] Error 2
make: *** [all] Error 2

Hi @gy2256  Building the RealSense SDK on a modern Mac with an Apple Silicon M1 processor is possible but can be more complicated than a build for the older Intel-based models.  the case https://github.com/IntelRealSense/librealsense/issues/8090 is an excellent hub for finding solutions to M1 build problems.
I note though that you are using the new MacOS Monterey.  USB device problems in general (not just with RealSense cameras) have been reported on Monterey on both Intel and M1 based computers, whereas RealSense worked with earlier MacOS versions such as Catalina and Big Sur.  This is discussed in https://github.com/IntelRealSense/librealsense/issues/9916
However, you are not experiencing errors typically related to the Monterey SUB problem such as failed to claim usb interface and so it is more likely to be a build-related problem.  When debugging, a good rule is to start the investigation at the first error, as subsequent errors may be resulting from a cascade of problems caused by the first error and so disappear once the initial error is solved.
Regarding the initial error ld: library not found for -latomic ... clang: error: linker command failed with exit code 1 (use -v to see invocation): a RealSense M1 user in https://github.com/IntelRealSense/librealsense/issues/8090#issuecomment-829339582 experienced this.
It looks as though that user, who subsequently achieved a successful build, may have followed the advice given to them to another user to build using the alternative instruction guide in the link below.
https://dev.intelrealsense.com/docs/macos-installation-for-intel-realsense-sdk

Thanks for the reply. I realize that should not use make -j8 to build the project. Instead, I need to use Xcode to build the project. I use the following command before building it in Xcode.
cmake .. -DBUILD_PYTHON_BINDINGS:bool=true -DFORCE_LIBUVC=true -DFORCE_RSUSB_BACKEND=true -DBUILD_NETWORK_DEVICE=ON -DBUILD_EXAMPLES=true -DBUILD_WITH_OPENMP=false -DHWM_OVER_XU=false -G Xcode -DOPENSSL_ROOT_DIR=/opt/homebrew/opt/openssl -DOPENSSL_LIBRARIES=/opt/homebrew/opt/openssl/lib

Excellent news that you found a solution, @gy2256 - thanks very much for the update and for sharing your method!

Hi, I do not have much experience with CMake and M1 is there easy way to fix this? (I checked other issues but nothing was close or I missed them)
-- Found PythonInterp: /opt/homebrew/bin/python3.9 (found version "3.9.9")
-- Found PythonLibs<EMAIL_ADDRESS>-- Performing Test HAS_FLTO
-- Performing Test HAS_FLTO - Failed
-- Performing Test HAS_FLTO_THIN
-- Performing Test HAS_FLTO_THIN - Failed
-- Found Python: /opt/homebrew/Frameworks/Python.framework/Versions/3.9/bin/python3.9 (found version "3.9.9") found components: Interpreter Development Development.Module Development.Embed
CMake Error at /opt/homebrew/Cellar/cmake/3.22.0/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
Could NOT find Threads (missing: Threads_FOUND)
Call Stack (most recent call first):
/opt/homebrew/Cellar/cmake/3.22.0/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE)
/opt/homebrew/Cellar/cmake/3.22.0/share/cmake/Modules/FindThreads.cmake:238 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
examples/measure/CMakeLists.txt:9 (find_package)
-- Configuring incomplete, errors occurred!

Hi @Obrepal  Which MacOS version are you using (for example, Catalina, Big Sur or Monterey)

Hi @Obrepal Which MacOS version are you using (for example, Catalina, Big Sur or Monterey)

I am using Monterey (downloaded it yesterday, with Big sur I had the same problem and thought that might help)
Also I have the newest Xcode Version 13.1 (13A1030d)
I downloaded the repo with this command:
git clone https://github.com/IntelRealSense/librealsense
and here the whole error output
build % cmake .. -DBUILD_EXAMPLES=true -DBUILD_WITH_OPENMP=false -DHWM_OVER_XU=false -- Checking internet connection... -- Internet connection identified -- Info: REALSENSE_VERSION_STRING=2.50.0 -- Setting Unix configurations -- using RS2_USE_LIBUVC_BACKEND CMake Error at /opt/homebrew/Cellar/cmake/3.22.0/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230 (message):   Could NOT find Threads (missing: Threads_FOUND) Call Stack (most recent call first):   /opt/homebrew/Cellar/cmake/3.22.0/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE)   /opt/homebrew/Cellar/cmake/3.22.0/share/cmake/Modules/FindThreads.cmake:238 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)   examples/measure/CMakeLists.txt:9 (find_package)
I don't want to make it too long so I attached two files mentioned after cmake ..
CMakeError.log
CMakeOutput.log

Thanks very much @Obrepal for the information.  If you also had the same problem with Big Sur then your issue likely isn't related to the USB problems that have been experienced by upgraders to Monterey, as discussed in https://github.com/IntelRealSense/librealsense/issues/9916

So I should make  a new issue?

@Obrepal  Yes, please post a new issue using the green New Issue button on the front page of this forum at the link below and include your original message from https://github.com/IntelRealSense/librealsense/issues/9999#issuecomment-988188997
https://github.com/IntelRealSense/librealsense/issues/


hello, may you share me with the cdiscount dataset to reproduce your work?

Thanks a lot!

Hello. I don't have the dataset, I deleted it when the competition ended.


feat: Button component

BREAKING CHANGE: Button Component receives new props

button design
button has icon included
IconButton as separated component
transitions added
icon cleanup
tailwind config extended

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket: