RuntimeError: "addmm_impl_cpu_" not implemented for 'Half' on CPU

System Info
Running on CPU
CPU Details:
Architecture:            x86_64
CPU op-mode(s):        32-bit, 64-bit
Address sizes:         46 bits physical, 48 bits virtual
Byte Order:            Little Endian
CPU(s):                  12
On-line CPU(s) list:   0-11
Vendor ID:               GenuineIntel
Model name:            Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz
CPU family:          6
Model:               63
Thread(s) per core:  2
Core(s) per socket:  6
Socket(s):           1
Stepping:            2
CPU max MHz:         3800,0000
CPU min MHz:         1200,0000
OS Details:
Linux serv-4102 5.15.0-84-generic #93-Ubuntu SMP  x86_64 GNU/Linux
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.3 LTS
Release:        22.04
Information

[X] Docker
[ ] The CLI directly

Tasks

[X] An officially supported command
[ ] My own modifications

Reproduction
Command:
docker run --shm-size 1g -e HUGGING_FACE_HUB_TOKEN=$token -p 8080:80 -v $volume:/data ghcr.io/huggingface/text-generation-inference:1.1.0 --model-id $model --disable-custom-kernels
Stack Trace:
2023-10-05T11:59:09.465814Z  INFO text_generation_launcher: Args { model_id: "meta-llama/Llama-2-7b-chat-hf", revision: None, validation_workers: 2, sharded: None, num_shard: None, quantize: None, dtype: None, trust_remote_code: false, max_concurrent_requests: 128, max_best_of: 2, max_stop_sequences: 4, max_top_n_tokens: 5, max_input_length: 1024, max_total_tokens: 2048, waiting_served_ratio: 1.2, max_batch_prefill_tokens: 4096, max_batch_total_tokens: None, max_waiting_tokens: 20, hostname: "9eb8eef55da3", port: 80, shard_uds_path: "/tmp/text-generation-server", master_addr: "localhost", master_port: 29500, huggingface_hub_cache: Some("/data"), weights_cache_override: None, disable_custom_kernels: true, cuda_memory_fraction: 1.0, rope_scaling: None, rope_factor: None, json_output: false, otlp_endpoint: None, cors_allow_origin: [], watermark_gamma: None, watermark_delta: None, ngrok: false, ngrok_authtoken: None, ngrok_edge: None, env: false }
2023-10-05T11:59:09.465956Z  INFO download: text_generation_launcher: Starting download process.
2023-10-05T11:59:13.115693Z  INFO text_generation_launcher: Files are already present on the host. Skipping download.
2023-10-05T11:59:13.571361Z  INFO download: text_generation_launcher: Successfully downloaded weights.
2023-10-05T11:59:13.571733Z  INFO shard-manager: text_generation_launcher: Starting shard rank=0
2023-10-05T11:59:16.481529Z  WARN text_generation_launcher: We're not using custom kernels.
2023-10-05T11:59:16.486454Z  WARN text_generation_launcher: Could not import Flash Attention enabled models: CUDA is not available
2023-10-05T11:59:16.488869Z  WARN text_generation_launcher: Could not import Mistral model: CUDA is not available
2023-10-05T11:59:23.584416Z  INFO shard-manager: text_generation_launcher: Waiting for shard to be ready... rank=0
2023-10-05T11:59:33.595632Z  INFO shard-manager: text_generation_launcher: Waiting for shard to be ready... rank=0
2023-10-05T11:59:43.607386Z  INFO shard-manager: text_generation_launcher: Waiting for shard to be ready... rank=0
2023-10-05T11:59:53.618983Z  INFO shard-manager: text_generation_launcher: Waiting for shard to be ready... rank=0
2023-10-05T12:00:03.630826Z  INFO shard-manager: text_generation_launcher: Waiting for shard to be ready... rank=0
2023-10-05T12:00:13.642436Z  INFO shard-manager: text_generation_launcher: Waiting for shard to be ready... rank=0
2023-10-05T12:00:23.653955Z  INFO shard-manager: text_generation_launcher: Waiting for shard to be ready... rank=0
2023-10-05T12:00:33.665630Z  INFO shard-manager: text_generation_launcher: Waiting for shard to be ready... rank=0
2023-10-05T12:00:43.677224Z  INFO shard-manager: text_generation_launcher: Waiting for shard to be ready... rank=0
2023-10-05T12:00:53.689059Z  INFO shard-manager: text_generation_launcher: Waiting for shard to be ready... rank=0
2023-10-05T12:01:03.700559Z  INFO shard-manager: text_generation_launcher: Waiting for shard to be ready... rank=0
2023-10-05T12:01:13.712353Z  INFO shard-manager: text_generation_launcher: Waiting for shard to be ready... rank=0
2023-10-05T12:01:23.724068Z  INFO shard-manager: text_generation_launcher: Waiting for shard to be ready... rank=0
2023-10-05T12:01:26.554214Z  INFO text_generation_launcher: Server started at unix:///tmp/text-generation-server-0
2023-10-05T12:01:26.627999Z  INFO shard-manager: text_generation_launcher: Shard ready in<PHONE_NUMBER>16s rank=0
2023-10-05T12:01:26.707790Z  INFO text_generation_launcher: Starting Webserver
2023-10-05T12:01:27.536106Z  WARN text_generation_router: router/src/main.rs:349: --revision is not set
2023-10-05T12:01:27.536128Z  WARN text_generation_router: router/src/main.rs:350: We strongly advise to set it to a known supported commit.
2023-10-05T12:01:28.076175Z  INFO text_generation_router: router/src/main.rs:371: Serving revision 08751db2aca9bf2f7f80d2e516117a53d7450235 of model meta-llama/Llama-2-7b-chat-hf
2023-10-05T12:01:28.082136Z  INFO text_generation_router: router/src/main.rs:213: Warming up model
2023-10-05T12:01:28.190080Z ERROR text_generation_launcher: Method Warmup encountered an error.
Traceback (most recent call last):
File "/opt/conda/bin/text-generation-server", line 8, in
sys.exit(app())
File "/opt/conda/lib/python3.9/site-packages/typer/main.py", line 311, in call
return get_command(self)(*args, **kwargs)
File "/opt/conda/lib/python3.9/site-packages/click/core.py", line 1157, in call
return self.main(*args, **kwargs)
File "/opt/conda/lib/python3.9/site-packages/typer/core.py", line 778, in main
return _main(
File "/opt/conda/lib/python3.9/site-packages/typer/core.py", line 216, in _main
rv = self.invoke(ctx)
File "/opt/conda/lib/python3.9/site-packages/click/core.py", line 1688, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/opt/conda/lib/python3.9/site-packages/click/core.py", line 1434, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/opt/conda/lib/python3.9/site-packages/click/core.py", line 783, in invoke
return __callback(*args, **kwargs)
File "/opt/conda/lib/python3.9/site-packages/typer/main.py", line 683, in wrapper
return callback(**use_params)  # type: ignore
File "/opt/conda/lib/python3.9/site-packages/text_generation_server/cli.py", line 83, in serve
server.serve(
File "/opt/conda/lib/python3.9/site-packages/text_generation_server/server.py", line 207, in serve
asyncio.run(
File "/opt/conda/lib/python3.9/asyncio/runners.py", line 44, in run
return loop.run_until_complete(main)
File "/opt/conda/lib/python3.9/asyncio/base_events.py", line 634, in run_until_complete
self.run_forever()
File "/opt/conda/lib/python3.9/asyncio/base_events.py", line 601, in run_forever
self._run_once()
File "/opt/conda/lib/python3.9/asyncio/base_events.py", line 1905, in _run_once
handle._run()
File "/opt/conda/lib/python3.9/asyncio/events.py", line 80, in _run
self._context.run(self._callback, *self._args)
File "/opt/conda/lib/python3.9/site-packages/grpc_interceptor/server.py", line 159, in invoke_intercept_method
return await self.intercept(

File "/opt/conda/lib/python3.9/site-packages/text_generation_server/interceptor.py", line 21, in intercept
return await response
File "/opt/conda/lib/python3.9/site-packages/opentelemetry/instrumentation/grpc/_aio_server.py", line 82, in _unary_interceptor
raise error
File "/opt/conda/lib/python3.9/site-packages/opentelemetry/instrumentation/grpc/_aio_server.py", line 73, in _unary_interceptor
return await behavior(request_or_iterator, context)
File "/opt/conda/lib/python3.9/site-packages/text_generation_server/server.py", line 72, in Warmup
max_supported_total_tokens = self.model.warmup(batch)
File "/opt/conda/lib/python3.9/site-packages/text_generation_server/models/model.py", line 65, in warmup
self.generate_token(batch)
File "/opt/conda/lib/python3.9/contextlib.py", line 79, in inner
return func(*args, **kwds)
File "/opt/conda/lib/python3.9/site-packages/text_generation_server/models/causal_lm.py", line 568, in generate_token
logits, past = self.forward(
File "/opt/conda/lib/python3.9/site-packages/text_generation_server/models/causal_lm.py", line 558, in forward
outputs = self.model.forward(**kwargs)
File "/opt/conda/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py", line 820, in forward
outputs = self.model(
File "/opt/conda/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/opt/conda/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py", line 708, in forward
layer_outputs = decoder_layer(
File "/opt/conda/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/opt/conda/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py", line 424, in forward
hidden_states, self_attn_weights, present_key_value = self.self_attn(
File "/opt/conda/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/opt/conda/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py", line 321, in forward
query_states = self.q_proj(hidden_states)
File "/opt/conda/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in call_impl
return forward_call(*args, **kwargs)
File "/opt/conda/lib/python3.9/site-packages/torch/nn/modules/linear.py", line 114, in forward
return F.linear(input, self.weight, self.bias)
RuntimeError: "addmm_impl_cpu" not implemented for 'Half'

2023-10-05T12:01:28.190295Z ERROR warmup{max_input_length=1024 max_prefill_tokens=4096}:warmup: text_generation_client: router/client/src/lib.rs:33: Server error: "addmm_impl_cpu_" not implemented for 'Half'
Error: Warmup(Generation(""addmm_impl_cpu_" not implemented for 'Half'"))
2023-10-05T12:01:28.210989Z ERROR text_generation_launcher: Webserver Crashed
2023-10-05T12:01:28.211005Z  INFO text_generation_launcher: Shutting down shards
Error: WebserverFailed
2023-10-05T12:01:28.841520Z  INFO shard-manager: text_generation_launcher: Shard terminated rank=0
Expected behavior
Current Behavior:
ERROR warmup{max_input_length=1024 max_prefill_tokens=4096}:warmup: text_generation_client: router/client/src/lib.rs:33: Server error: "addmm_impl_cpu_" not implemented for 'Half'
Expected Behavior:
For the Container to launch.

Try --dtype bfloat16


shutdown api has been changed on mesos 0.24.1

Mesos 0.24.0 added experimental support for v1 Scheduler HTTP API.
and I cannot shutdown the framwork by using the following command:
curl -d "frameworkId=YOUR_FRAMEWORK_ID" -X POST http://YOUR_MESOS_URL:5050/master/shutdown

Now I use the following cmd to shutdown the framework
curl -X POST -H "Content-Type: application/json" http://YOUR_MESOS_URL:5050/api/v1/scheduler<EMAIL_ADDRESS>
Content of the teardown.json:
{
  "framework_id"    : {"value" : "framework id"},
  "type"            : "TEARDOWN"
}

This also works:
curl -d 'frameworkId=YOUR_FRAMEWORK_ID' -X POST http://YOUR_MESOS_URL:5050/master/teardown

@christobill maybe I got something wrong before-_-,I'll close this issue!

@christobill I found if I boot up the hdfs by using docker, I can not stop it ~~I'm confused by this
docker run -it --rm -v "$PWD"/hdfs-mesos-0.1.5:/hdfs-mesos-0.1.5 --net host --workdir /hdfs-mesos-0.1.5 mesos_jdk:0.24.1_1.7 bin/hdfs-mesos

mesos_jdk is a image I build for execute hdfs-mesos, Dockerfile as follow
FROM centos:7

RUN rpm -i http://repos.mesosphere.io/el/7/noarch/RPMS/mesosphere-el-repo-7-1.noarch.rpm && \
yum -y install mesos-0.24.1
RUN yum -y install java-1.7.0-openjdk
RUN yum -y install which

@christobill I found if I boot up the hdfs by using docker, I can not stop it ~~I'm confused by this
docker run -it --rm -v "$PWD"/hdfs-mesos-0.1.5:/hdfs-mesos-0.1.5 --net host --workdir /hdfs-mesos-0.1.5 mesos_jdk:0.24.1_1.7 bin/hdfs-mesos

mesos_jdk is a image I build for execute hdfs-mesos, Dockerfile as follow
FROM centos:7

RUN rpm -i http://repos.mesosphere.io/el/7/noarch/RPMS/mesosphere-el-repo-7-1.noarch.rpm && \
yum -y install mesos-0.24.1
RUN yum -y install java-1.7.0-openjdk
RUN yum -y install which

@asdfsx what I meant is: you are absolutely right, doc/README.md is not up-to-date.
You should reopen the issue.

README.md should be changed like this:

Shutdown the hdfs framework in Mesos: curl -d "frameworkId=YOUR_FRAMEWORK_ID" -X POST http://YOUR_MESOS_URL:5050/master/teardown (or curl -d "frameworkId=YOUR_FRAMEWORK_ID" -X POST http://YOUR_MESOS_URL:5050/master/shutdown for mesos<0.24.1)

README.md should be changed like this:

Shutdown the hdfs framework in Mesos: curl -d "frameworkId=YOUR_FRAMEWORK_ID" -X POST http://YOUR_MESOS_URL:5050/master/teardown (or curl -d "frameworkId=YOUR_FRAMEWORK_ID" -X POST http://YOUR_MESOS_URL:5050/master/shutdown for mesos<0.24.1)

README.md should be changed like this:
2 Shutdown the hdfs framework in Mesos: curl -d "frameworkId=YOUR_FRAMEWORK_ID" -X POST http://YOUR_MESOS_URL:5050/master/teardown (or curl -d "frameworkId=YOUR_FRAMEWORK_ID" -X POST http://YOUR_MESOS_URL:5050/master/shutdown for mesos<0.24.1)

@asdfsx concerning your docker issue.
Stop the docker container.
Get the framework id in mesos UI.
curl -d "frameworkId=YOUR_FRAMEWORK_ID" -X POST http://YOUR_MESOS_URL:5050/master/teardown (or curl -d "frameworkId=YOUR_FRAMEWORK_ID" -X POST http://YOUR_MESOS_URL:5050/master/shutdown for mesos<0.24.1)
With zkCli, rmr /hdfs-mesos
I am just quoting the doc (appart from the shutdown/teardown change)

I guess this depends on the situation. If you have succescfully started the frame work, you can use the old style to shutdown the framework. If you failed to start the framework.


Update dependencies

Updates all dependencies reported as outdated by running npm outdated:
$ npm outdated
Package                    Current  Wanted  Latest  Location
basic-auth                   1.1.0   1.1.0   2.0.0  express-prototype
cross-spawn                  5.1.0   5.1.0   6.0.5  express-prototype
dotenv                       4.0.0   4.0.0   6.0.0  express-prototype
express                     4.15.2  4.15.2  4.16.3  express-prototype
gulp-clean                   0.3.2   0.3.2   0.4.0  express-prototype
gulp-mocha                   4.3.1   4.3.1   6.0.0  express-prototype
gulp-sass                    3.1.0   3.1.0   4.0.1  express-prototype
marked                      0.3.19  0.3.19   0.4.0  express-prototype
notifications-node-client    3.5.0   3.5.0   4.1.0  express-prototype
readdir                     0.0.13  0.0.13   0.1.0  express-prototype
require-dir                  0.3.2   0.3.2   1.0.0  express-prototype
run-sequence                 1.2.2   1.2.2   2.2.1  express-prototype
standard                    10.0.3  10.0.3  11.0.1  express-prototype
sync-request                 4.1.0   4.1.0   6.0.0  express-prototype

(readdir has been removed as it was not being used)
Individual commits have details for how each change was tested.
https://trello.com/c/Vaizr1wg/1164-2-update-dependencies-in-prototype-kit

In your commits you mention that we support Node.js 8 and above, given that the data we have suggests lots of 6.x usage is there any reason why we'd not want to support 6.x and above?

The commit messages don't seem to require 8? They seem to drop support for older Node, but all older than 6

Not blocking, just to record, I get this output when installing with node 6.10.3:
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to<EMAIL_ADDRESS>as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.

><EMAIL_ADDRESS>install /Users/joelanman/projects/govuk-prototype-kit/node_modules/fsevents
> node install

[fsevents] Success: "/Users/joelanman/projects/govuk-prototype-kit/node_modules/fsevents/lib/binding/Release/node-v48-darwin-x64/fse.node" already installed
Pass --update-binary to reinstall or --build-from-source to recompile

><EMAIL_ADDRESS>install /Users/joelanman/projects/govuk-prototype-kit/node_modules/node-sass
> node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.9.2/darwin-x64-48_binding.node
Download complete  ⸩ ⠋ :
Binary saved to /Users/joelanman/projects/govuk-prototype-kit/node_modules/node-sass/vendor/darwin-x64-48/binding.node
Caching binary to /Users/joelanman/.npm/node-sass/4.9.2/darwin-x64-48_binding.node

><EMAIL_ADDRESS>postinstall /Users/joelanman/projects/govuk-prototype-kit/node_modules/node-sass
> node scripts/build.js

Binary found at /Users/joelanman/projects/govuk-prototype-kit/node_modules/node-sass/vendor/darwin-x64-48/binding.node
Testing binary
Binary is fine

><EMAIL_ADDRESS>postinstall /Users/joelanman/projects/govuk-prototype-kit/node_modules/nodemon
> node bin/postinstall || exit 0

><EMAIL_ADDRESS>postinstall /Users/joelanman/projects/govuk-prototype-kit/node_modules/nunjucks
> node postinstall-build.js src

npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

On node 8.9.4 - I think it's identical
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to<EMAIL_ADDRESS>as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.

><EMAIL_ADDRESS>install /Users/joelanman/projects/govuk-prototype-kit/node_modules/fsevents
> node install

[fsevents] Success: "/Users/joelanman/projects/govuk-prototype-kit/node_modules/fsevents/lib/binding/Release/node-v57-darwin-x64/fse.node" already installed
Pass --update-binary to reinstall or --build-from-source to recompile

><EMAIL_ADDRESS>install /Users/joelanman/projects/govuk-prototype-kit/node_modules/node-sass
> node scripts/install.js

Cached binary found at /Users/joelanman/.npm/node-sass/4.9.2/darwin-x64-57_binding.node

><EMAIL_ADDRESS>postinstall /Users/joelanman/projects/govuk-prototype-kit/node_modules/node-sass
> node scripts/build.js

Binary found at /Users/joelanman/projects/govuk-prototype-kit/node_modules/node-sass/vendor/darwin-x64-57/binding.node
Testing binary
Binary is fine

><EMAIL_ADDRESS>postinstall /Users/joelanman/projects/govuk-prototype-kit/node_modules/nodemon
> node bin/postinstall || exit 0

><EMAIL_ADDRESS>postinstall /Users/joelanman/projects/govuk-prototype-kit/node_modules/nunjucks
> node postinstall-build.js src

npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

I based my commit messages off of the fact that we say we require node 8.x.x in the install docs:
https://govuk-prototype-kit.herokuapp.com/docs/install/developer-install-instructions
https://govuk-prototype-kit.herokuapp.com/docs/install/requirements

Looks good thanks for this work!
Can we update Changelog and rebase?

Done 👍


Added links

Specifically, to the different subfields of computer science

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@Shermjj
Thank you for your contribution to the page! 👍 We're happy to accept these changes and look forward to future contributions.


Support for generating PMREM at runtime off of the main thread

In #338, we discussed the performance penalties incurred by runtime PMREM generation.
It is feasible to move most of this work off the main thread into a worker. This should be possible to do even without OffscreenCanvas support (although it would probably be notably slower to compute off of the GPU).
This work might tie in well with #37 , but we should take care to design it to support scenarios where GL rendering is still confined to the main thread.

This turned out to be a dead end.


Improve send screens UI

The send flow is overall good, but some components could use small design improvements especially in the address selection and amount selection screens
.

I have worked on the Transaction send flow UI improvements and have refined most of the screens to match the industry standard screens. this is how the new screens UI look now @ben-kaufman , clean and Modern
https://www.figma.com/design/m5eMFTKD391AiJAXaEzgxB/Bitcoin-Keeper?node-id=3328-11796&t=sgsqUfCjbA4O2pbF-1

Changes have been made now as per feedback
https://www.figma.com/design/m5eMFTKD391AiJAXaEzgxB/Bitcoin-Keeper?node-id=3328-11796&t=sgsqUfCjbA4O2pbF-1

Verified this issue on keeper app v 1.2.18(411)


feat: add adapter_type to telemetry

Description
Adds a new property to telemetry, the adapter_type.
After a bit of trial and error, it seems like the correct (i.e. runtime resolved) field comes from config.to_target_dict()["type"]. The more obvious config.get_metadata().adapter_type returns the static value from the configuration.

Closed in favor of https://github.com/fal-ai/fal/pull/743


Update CI testing, add nodejs 10 testing, update basic files

Hey,
This PR gives an error on Travis.
https://travis-ci.org/misanorot/ioBroker.viessmann?utm_source=email&utm_medium=notification
I am confused

restart the travis-ci build ... according to log travis had a problem to get the needed nodejs version ... so nothing to do with the adapter itself


[docs] Add GovX to Showcase, move Onepixel

[X] I have followed (at least) the PR section of the contributing guide.

sfr alexa ranking is wrong. Alternatively, you could use Similarweb.

sfrpresse.sfr.fr !== sfr.fr

Ah, good catch. I missed that Alexa redirected.


[FEATURE]: Meta title/description

Is there an existing issue for this?

[X] I have searched the existing issues

New feature
It appears that the site has no title/description. My tab for instance just says "koinos.io" I think it's just defaulting to the URL. We should have a proper title/description.
Anything else?
No response

https://nextjs.org/docs/messages/no-document-title


browsermob-proxy having issues with JAVA 9

In Java 9, there is an issue with browsermob proxy as it fails to collect the HTTP responses as HTTP archive object. So, basically when I do a proxy.new_har('some data') and after that, if I try to dump the data as a JSON object via json.dumps(proxy.har, ensure_ascii=false) it ends up giving me a python exception as "Nothing to decode". After much debugging, I cam out with the conclusion that the proxy is not collecting the HTTP archive data because of which it is failing in JAVA 9 version. After downgrading the JAVA version to 8 it resolved the issue. Can this issue be rectified for the upcoming JAVA versions?

@Corefinder89 We have a new fork of the BrowserMob proxy with support up to Java 11. Please feel free to give it a shot!
BrowserUp HTTP Proxy https://github.com/browserup/browserup-proxy

Thanks @ericbeland. Sure i will give it a try


全部中文简体，别中英混搭

Provide a description of the new feature / enhancement
全部中文简体，别中英混搭

due to our dev/ iteration speed, we are always slightly behind in translation.  If there are spots, please use localization/translation template to report. https://github.com/microsoft/PowerToys/issues/new?assignees=&labels=Issue-Bug%2CArea-Localization%2CIssue-Translation%2CTriage-Needed&template=translation_issue.yml
Screenshots are extremely helpful here


Hyperledger Besu re-deployment fails

Describe the bug
The BAF Hyperledger Besu deployment is not idempotent, it fails when running the deployment again without resetting.
To Reproduce
Steps to reproduce the behavior:

Deploy a hyperledger besu network successfully using BAF.
After all the nodes are up, redeploy using the same network.yaml
The deployment fails with the error (UPDATE required)

Expected behavior
The deployment should not fail. It should succeed even when there is nothing to change.

This is not fixed. Please check the demo pipelines. Redeployment failing with following error:
TASK [helm_component : create value file for supplychainvalidator1ibft] ********
[WARNING]: Unable to find '/jenkins/workspace/BAF_Demo_multi_besu-
VAHPN2FP7GGJMY3ZV4HIPANXNZ7UBA3OIX52A2VXHYHD2DRF3WDA/build/besu_genesis' in
expected paths (use -vvvvv to see paths)
fatal: [localhost]: FAILED! => {"changed": false, "msg": "AnsibleError: An unhandled exception occurred while templating '{{ lookup('file', '{{ network.config.genesis }}') }}'. Error was a <class 'ansible.errors.AnsibleError'>, original message: An unhandled exception occurred while running the lookup plugin 'file'. Error was a <class 'ansible.errors.AnsibleError'>, original message: could not locate file in lookup: /jenkins/workspace/BAF_Demo_multi_besu-VAHPN2FP7GGJMY3ZV4HIPANXNZ7UBA3OIX52A2VXHYHD2DRF3WDA/build/besu_genesis"}


Can't install using yarn or npm

I can't get this to install using either method on the README:
Install with yarn (v0.27.5) yarn add @serverless-chrome/lambda gives the error:
yarn add v0.27.5
[1/4] Resolving packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/@serverless-chrome%2flambda: User not found".

Install with npm (v5.3.0) npm install --save @serverless-chrome/lambda gives the error:
npm ERR! code E404
npm ERR! 404 Not Found: @serverless-chrome/lambda@latest

@boosh are you using a proxy or some 3rd party local NPM registry like SInopia? I was, and I fixed this issue by setting the registry to the default one:
npm config set registry https://registry.npmjs.org/

Thank you for the tip @tnolet!

@tnolet Yes, I was. I renamed my ~/.npmrc file and now I can install it. Thanks!


fix: the --registry flag is ignored when image:  exists in func.yaml

Fixes #1297:

if there is a mismatch in func.yaml between registry and image the latter will be updated with registry
if there is a mismatch between func.yaml registry and image comparing to flag value --registry both will be updated with the flag value
if --image was provided, use it and do NOT update even if there is a mismatch with the registry.

Ready for review.
/assign @lkingland

/retest

You have added a test for the case where registry differs in func.yaml from the value in the image name. Any chance you can add test cases for the remaining scenarios?

@lance sure 👍🏻

/unassign @lkingland
/assign @lance

@lance done, ready for review

/approve


Adds ability to calibrate temperature for BME680

Description:
Out of the box the BME680 runs too hot.   This change version bumps the bme680 package to allow for a temperature offset.
Further reading:

Looking at a reference thermometer, we can see that our temperature is indeed a few degrees to high. Does that mean the temperature sensor inside the BME680 is inaccurate?
Actually no, it very accurately measures the temperature exactly where it is located on the board. But there also is the issue: our board as most devices contains some heat sources (e.g., MCU, WiFi chip, display, …). This means the temperature on our board is actually higher than the ambient temperature. Since the absolute amount of water in the air is approximately constant, this also causes the relative humidity to be lower on our board than elsewhere in the room.
As BSEC cannot know in which kind of device the sensor is integrated, we have provide some information to the algorithm to enable it to compensate this offset. In the simplest case, we have to deal with an embedded device with a constant workload and approximately constant self-heating. In such a case, we can simply supply a temperature offset to BSEC which will be subtracted from the temperature and will be used to correct the humidity reading as well.

from the Integration Guide - Bosch Software Environmental Cluster (BSEC)
Related issue (if applicable): fixes #
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:

[X] The code change is tested and works locally.
[X] Local tests pass with tox. Your PR cannot be merged unless tests pass
[X] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[X] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[X] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Hi @ctborg,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Docs PR: https://github.com/home-assistant/home-assistant.io/pull/8004


Add support for CSS Variables autocomplete

Check for existing issues

[X] Completed

Describe the feature
As I wrote in the title. CSS variables have been around for a long time and it would be great to have support right in the box. VSCode has an extension that provides the right functionality and works quite well.
If applicable, add mockups / screenshots to help present your vision of the feature
No response

I don't mean to discredit this issue, but I believe that CSS variable autocomplete already exists in Zed. For me, with or without typing --, suggestions pop up.

Zed: v0.118.1 (Zed)
OS: macOS 12.6.6
Memory: 16 GiB
Architecture: x86_64

@CurbaiCode Of course, it works if you refer to a variable in the same file, but if you do it in another file, it no longer works.

Ohh, OK. Thank you for the clarification.


Only 72 dpi seems to work

I've tried specifying different dpis but so far I've only gotten images at 72dpi. Any ideas what might be happening?
Did this stop working? Any pointers on what the correct approach would be right now?
Thanks!

Same problem here, downloaded images are 72dpi only, no matter what defined in the -d parameter.
Any chance to get this fixed?
Thank you!

The Mapbox wmts service is another option for creating maps for printing in QGIS or ArcMap, but it does not currently support retina maps, so is limited to printing at around 72dpi, and is also only jpeg right now.

The Mapbox wmts service is another option for creating maps for printing in QGIS or ArcMap, but it does not currently support retina maps, so is limited to printing at around 72dpi, and is also only jpeg right now.


BC break for method call on union type

TypeScript Version:  2.1.0-dev.20160729
Code
interface A {
  focus: (force: boolean) => void
}
interface B {
  focus: () => void
}
let instance: A | B
instance.focus(true);

Expected behavior:
No compilation error at least at 2.1.0-dev.20160716
Actual behavior:
TS2349: Cannot invoke an expression whose type lacks a call signature.

Maybe similar case, also broken between 2.1.0-dev.20160716 and 2.1.0-dev.20160729:
interface List<T> {
    map<U>(mapper: (v: T, index: number) => U): List<U>
}
interface A {
    prop1: boolean
}
interface B extends A {
    prop2: number
}
type ListA = List<A>;
type ListB = List<B>;
let instance: List<A> | List<B>;
instance.map((v, index) => {
    return true;
})

@ahejlsberg I believe this is due to the less-aggressive subtype reduction -- thoughts?

@Strate I'm curious what the scenario is for having types like List<A> | List<B> when B is a subtype of A. You could equally well just write List<A> (and the issue would then go away). Similarly, you could just use type A instead of A | B in the first example.
@RyanCavanaugh Yes, this is caused by a change in #9407 to not perform subtype reduction in property accesses on objects of union types. Subtype reduction is horribly expensive on large union types and it is not clear we could ever make it perform acceptably. Also, subtype reduction only helps in those cases where we can reduce a union of function types down to a single function type.
The core issue really is that we are very conservative when it comes to call operations on a union type. We basically require all of the parameter types to be identical, with a small allowance matching omitted parameters to optional parameters.
The real fix here would be to find a better way to check calls on unions of function types. Subtype reduction isn't the solution because there are lots of cases where we have a union of function types that aren't subtypes of each other, but where there is a meaningful way to construct calls that would satisfy all of the signatures.
One possibility might be to intersect the types of parameters in corresponding positions. So, for a union of function signatures (() => T) | ((x: A) => U) | ((x: B, y: C) => V) we would produce a synthetic signature of type ((x: A & B, y: C) => T | U | V).

@ahejlsberg seems that your suggestion could solve this issue:
type a = string;
type b = number;
interface List<T> {
    map<U>(mapper: (item: T) => U): List<U>
}
let instance: List<a> | List<b>
instance.map(v => true)

call to map produces an error "TS2349: Cannot invoke an expression whose type lacks a call signature." and "TS7006: Parameter 'v' implicitly has an 'any' type.". Second one could be fixed by explicit add a|b type for v parameter, but first one fixable only by typecasting instance to List<a|b>

#10041 is a good example of how this can be problematic in the absence of a meaningless union type

@Strate Yes, but as I think about it more, the idea of intersecting the parameter types still wouldn't work for overloaded signatures (as it wouldn't be clear which signatures to match with other signatures).
Still curious whether this shows up in a real world scenario for you, and if so, what leads to the existence of union types where one constituent is a subtype of the other?

It seems that there is no difference between
interface A { prop1: boolean }
interface B extends A { prop2: boolean }

and
interface A { prop1: boolean }
interface B { prop1: boolean, prop2: boolean }

from structural type system view.
First case is just to reduce copy-paste props from A to B.
And there is definetely big difference between Array<A> | Array<B> and Array<A|B>  and, of course, Array<A>.

I had a similar break in my code:
type Rule = LocalRule | GlobalRule;
interface LocalRule { enforce: () => void; }
interface GlobalRule { enforce: (state: GlobalState) => void; }
declare rules: Rule [];
rules.forEach (rule => rule.enforce (state)); // used to work, not anymore

To be frank, the only reason I wrote it this way is because of my laziness, I didn't want to pattern match to a certain case as long as the unified signature would work as well.

@aleksey-bykov laziness was also smart in this case since pattern matching with LocalRule|GlobalRule also has a subtype reduction problem:
rules.forEach(rule => {
    if (isGlobalRule(rule)) {
        rule.enforce(state);
    }
    else {
        rule.enforce(); // ERROR: Property 'enforce' does not exist on type 'never'.
    }
});

@yortus the way i fixed is by adding a kind property to both cases that i used for discrimination, without such property i see how it can be a problem, good catch

I agree with @ahejlsberg s comment:

One possibility might be to intersect the types of parameters in corresponding positions.

Please also see my comment in 9104 (which unlike this ticket is "open"):
https://github.com/Microsoft/TypeScript/issues/9104#issuecomment-255952203


Mute flaky test SearchWeightedRoutingIT.testStrictWeightedRoutingWith…

…CustomString

Description
Mutes flaky test SearchWeightedRoutingIT.testStrictWeightedRoutingWithCustomString
As mentioned in this comment by @dreamer-89: https://github.com/opensearch-project/OpenSearch/issues/8279#issuecomment-1670005549
This test has failed 85 times between build number 20900 to 22120. Muting it till the issue is fixed.

(base) ➜  OpenSearch git:(main) ruby ~/Desktop/flaky-finder.rb --s 20900 --e 22120
Will crawl builds from 20900 to 22120
------------------
85 org.opensearch.search.SearchWeightedRoutingIT.testStrictWeightedRoutingWithCustomString (20928,20928,20928,20935,20938,20938,20948,20949,20949,20949,20950,20958,20958,20958,20990,20995,21001,21006,21122,21187,21219,21219,21219,21268,21268,21308,21314,21314,21314,21331,21347,21350,21366,21366,21435,21445,21447,21487,21507,21535,21539,21578,21590,21590,21592,21592,21592,21600,21617,21631,21631,21638,21647,21647,21679,21696,21696,21697,21726,21726,21726,21731,21731,21731,21751,21763,21767,21767,21772,21791,21794,21794,21798,21806,21843,21843,21855,21855,21949,22021,22043,22060,22089,22094,22094)

Related Issues
Related to #8030
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Gradle Check (Jenkins) Run Completed with:
* **RESULT:** FAILURE ❌

* **URL:** https://build.ci.opensearch.org/job/gradle-check/22170/

* **CommitID:** [8566578](https://github.com/opensearch-project/OpenSearch/commit/85665781699427da43c32d2eca81f7ac040791ee)
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure [a flaky test](https://github.com/opensearch-project/OpenSearch/blob/main/DEVELOPER_GUIDE.md#flaky-tests) unrelated to your change?

https://github.com/opensearch-project/OpenSearch/issues/9178


TypeError: Cannot read property 'length' of undefined

TypeScript Version:  2.9.0-dev.20180328
Code
import * as React from 'react';

const Test123 = () => <div/>;

function testComponent(props) {
    return <Test123 {...props}/>;
}

Expected behavior:
No errors
Actual behavior:
Exceptions:
TypeError: Cannot read property 'length' of undefined
    at Object.unescapeLeadingUnderscores (/Users/dmitriyb/projects/media-platform-client/node_modules/typescript/lib/typescript.js:12280:19)
    at checkJsxAttributesAssignableToTagNameAttributes (/Users/dmitriyb/projects/media-platform-client/node_modules/typescript/lib/typescript.js:40117:146)
    at checkJsxOpeningLikeElementOrOpeningFragment (/Users/dmitriyb/projects/media-platform-client/node_modules/typescript/lib/typescript.js:40052:17)
    at checkJsxSelfClosingElement (/Users/dmitriyb/projects/media-platform-client/node_modules/typescript/lib/typescript.js:39449:13)
    at checkExpressionWorker (/Users/dmitriyb/projects/media-platform-client/node_modules/typescript/lib/typescript.js:43637:28)
    at checkExpression (/Users/dmitriyb/projects/media-platform-client/node_modules/typescript/lib/typescript.js:43530:42)
    at checkExpressionCached (/Users/dmitriyb/projects/media-platform-client/node_modules/typescript/lib/typescript.js:43396:38)
    at getReturnTypeFromBody (/Users/dmitriyb/projects/media-platform-client/node_modules/typescript/lib/typescript.js:42348:24)
    at getReturnTypeOfSignature (/Users/dmitriyb/projects/media-platform-client/node_modules/typescript/lib/typescript.js:31762:28)
    at checkFunctionExpressionOrObjectLiteralMethodDeferred (/Users/dmitriyb/projects/media-platform-client/node_modules/typescript/lib/typescript.js:42632:21)

You're not giving props a type definition so it could be undefined and here the typeerror is coming from the spread operator because typescript can't be sure what you're passing in can be spread

@jaydh that's right, it anyway should not raise an exception on compile time. And it used to work prior to 2.8.0


No Dancing animation for avatar with 'low' quality details

Describe the bug
We dont have dance behavior for avaters with low quality settings.
To Reproduce
Steps to reproduce the behavior:

Go to settings
go to graphics section
select 'low' in character details
dance with 'v'

Expected behavior
Avatar should have dance behavior like all other such actions(Walk/run/crouch/dash)

Is this referring to spritesheet mode?


Pathing randomly fails after first search. Pathfinder doesn't reset closed nodes after search is complete.

Subsequent searches on the same grid/graph will fail, since "closed" nodes are left over from the previous search.
Here is a fixed version of the "astar" method that saves off, and restores the closed nodes flags, before the path is returned.
`
var astar = {
/**
* Perform an A* Search on a graph given a start and end node.
* @param {Graph} graph
* @param {GridNode} start
* @param {GridNode} end
* @param {Object} [options]
* @param {bool} [options.closest] Specifies whether to return the
path to the closest node if the target is unreachable.
* @param {Function} [options.heuristic] Heuristic function (see
*          astar.heuristics).
*/
search: function(graph, start, end, options) {
graph.cleanDirty();
options = options || {};
var heuristic = options.heuristic || astar.heuristics.manhattan,
closest = options.closest || false;
    var openHeap = getHeap(),
        closestNode = start; // set the start node to be the closest if required
    var closedList = [];
    start.h = heuristic(start, end);

    openHeap.push(start);

    while(openHeap.size() > 0) {

        // Grab the lowest f(x) to process next.  Heap keeps this sorted for us.
        var currentNode = openHeap.pop();

        // End case -- result has been found, return the traced path.
        if(currentNode === end) {
            while(closedList.length>0)closedList.pop().closed = false;
            return pathTo(currentNode);
        }

        // Normal case -- move currentNode from open to closed, process each of its neighbors.
        currentNode.closed = true;
        closedList.push(currentNode);

        // Find all neighbors for the current node.
        var neighbors = graph.neighbors(currentNode);

        for (var i = 0, il = neighbors.length; i < il; ++i) {
            var neighbor = neighbors[i];

            if (neighbor.closed || neighbor.isWall()) {
                // Not a valid node to process, skip to next neighbor.
                continue;
            }

            // The g score is the shortest distance from start to current node.
            // We need to check if the path we have arrived at this neighbor is the shortest one we have seen yet.
            var gScore = currentNode.g + neighbor.getCost(currentNode),
                beenVisited = neighbor.visited;

            if (!beenVisited || gScore < neighbor.g) {

                // Found an optimal (so far) path to this node.  Take score for node to see how good it is.
                neighbor.visited = true;
                neighbor.parent = currentNode;
                neighbor.h = neighbor.h || heuristic(neighbor, end);
                neighbor.g = gScore;
                neighbor.f = neighbor.g + neighbor.h;
                graph.markDirty(neighbor);
                if (closest) {
                    // If the neighbour is closer than the current closestNode or if it's equally close but has
                    // a cheaper path than the current closest node then it becomes the closest node
                    if (neighbor.h < closestNode.h || (neighbor.h === closestNode.h && neighbor.g < closestNode.g)) {
                        closestNode = neighbor;
                    }
                }

                if (!beenVisited) {
                    // Pushing to heap will put it in proper place based on the 'f' value.
                    openHeap.push(neighbor);
                }
                else {
                    // Already seen the node, but since it has been rescored we need to reorder it in the heap
                    openHeap.rescoreElement(neighbor);
                }
            }
        }
    }
    while(closedList.length>0)closedList.pop().closed = false;

    if (closest) {
        return pathTo(closestNode);
    }

    // No result was found - empty array signifies failure to find path.
    return [];
},
// See list of heuristics: http://theory.stanford.edu/~amitp/GameProgramming/Heuristics.html
heuristics: {
    manhattan: function(pos0, pos1) {
        var d1 = Math.abs(pos1.x - pos0.x);
        var d2 = Math.abs(pos1.y - pos0.y);
        return d1 + d2;
    },
    diagonal: function(pos0, pos1) {
        var D = 1;
        var D2 = Math.sqrt(2);
        var d1 = Math.abs(pos1.x - pos0.x);
        var d2 = Math.abs(pos1.y - pos0.y);
        return (D * (d1 + d2)) + ((D2 - (2 * D)) * Math.min(d1, d2));
    }
},
cleanNode:function(node){
    node.f = 0;
    node.g = 0;
    node.h = 0;
    node.visited = false;
    node.closed = false;
    node.parent = null;
}

};
`

Thank you, I was wondering WTF was going on.

This was very helpful.

I'm having this problem but I'm using a script tag with a link to the script. is there any way to reset the closed nodes outside the script?

Since no-one-else seems to have done it over the years, I've created a fork with this fix: https://github.com/tukkek/a-star.
The performance improvement from being able to re-use the graph is massive. I estimate it's on the order of 100-times-faster or more on a project with a very-large-graph but I haven't actually bench-marked it.
I have also created a pull-request, more out-of-respect for Brian than in any hope of it actually being merged: https://github.com/bgrins/javascript-astar/pull/81. ¯\_(ツ)_/¯
Thank you for sharing your fix @manthrax!


Unit tests

In this milestone, we implemented the following:

[ ] Added unit tests for all the methods in all the classes, the methods include:
💠 Book
💠Person
💠Student
💠Teacher
💠Classroom
💠Rental

Hello @MahmoudBakr23 👋🏼 ,
Thank you for taking out time to review and approve this PR. You are amazing 💯


Allow useRootNavigator as a config

I believe that allowing useRootNavigator as a config would benefit the component.
This would be useful if we want to show the modal on top of a bottom navigator bar for example.
I saw that on the code you have this:
 confirmed = await showModalBottomSheet(
          context: context,
          shape: modalStyle.shape,
          clipBehavior: modalStyle.clipBehavior ?? Clip.none,
          backgroundColor: modalStyle.backgroundColor,
          elevation: modalStyle.elevation,
          isDismissible: modalConfig.barrierDismissible,
          barrierColor: modalConfig.barrierColor,
          enableDrag: modalConfig.enableDrag,
          builder: (_) => modal,
        );

So maybe it is just an extra config for the useRootNavigator as a default false.
What do you think?

I released https://pub.dev/packages/flutter_awesome_select with fixed null safety.
Could you check that everything works for you?

Hi everyone,
I'm sorry to announce that I'm no longer maintaining the smart_select package. It's been a great project, but it's become too difficult to maintain.
In its place, I've released a new package called choice. The combination to smart_select and chips_choice with cleaner, more flexible, and composable API for creating inline or prompted choice widgets with single or multiple selection.
I hope you'll check out choice. I think you'll find it to be a great replacement for smart_select.
Thanks for your understanding.


feat: add my details in Community.md

Fixes #206
Added my details in Community.md file.

Hey @rootCircle, have you linked your gitHub and discord?

Yes, I did that on discord. Is there any way that I can verify those @Shruti3004?
Also, I rebased to the latest commit to fix the merge conflicts that were there.


Remove references to IRuntimeEnvironment

Huh?

Follow up to https://github.com/aspnet/PlatformAbstractions/issues/36

:shipit:

:shipit:


HADOOP-16728. Avoid removing all the channels from connectionInfo when borrowing from the pool

Please have a look at this bug. I added a test case to demonstrated the issue. Thanks

Any news on this one?

The problem seems to be addressed in https://issues.apache.org/jira/browse/HADOOP-15358, which has been released in Hadoop 3.3.0.


Quest SteamVR not finding tracking data

Quest up to date on <IP_ADDRESS>.626
SteamVR 1.6.10
ALVR server+client 2.4.0-alpha5
Server finds client no problem, launches SteamVR, SteamVR sees a device but "cannot detect position information for this headset".
Quest is in a guardian zone and tracking.

For Oculus Quest you can try JackD83's fork.
It works only with Quest, and it has several Quest specific improvements.


retire these bindings in favor of rusqlite?

Now that rusqlite has addressed the lifetime issues with query_map(), there's not much reason to maintain these bindings.
I'm inclined to give this project a once-over and raise issues there for anything that's novel here.
I made a note about the expose() method on one of their issues... it's a closed issue, though, so maybe I should look into that some more.
cc @jgallagher @PeterReid @dgilman @AndiDog @ericsink

In my use of these bindings, I prepare a bunch of statements when my application starts up and then execute them many times as it runs. This mean I have a struct that goes like:
struct DatabaseApi {
    conn: DatabaseConnection,
    select_whatever: PreparedStatement,
    select_something_else: PrepareStatement,
    insert_thing: PreparedStatement,
}

This is what motivated commit 934d78450d362d30fddecb4b7d3171e9ca92452c on this library -- before, with statements having a lifetime parameter that made them have to outlive conn, that would not compile. In rusqlite, they still have that lifetime parameter. I wonder if they have figured out a pattern which accomplishes what I was trying to do, or if users of it just always prepare statements just in time.

Hey, I created this thread before finding this issue.
But maybe you can join the discussion there: https://users.rust-lang.org/t/sqlite-libraries-potential-for-unification/8702

To address the two points above about things that were missing in rusqlite:

Connection::handle gives you access to the raw SQLite connection
Connection::prepare_cached does still return statements with a lifetime, but they will be returned to a Connection-local cache when they're dropped, and calling prepare_cached again with the same SQL statement will return that cached statement without round-tripping through SQLite again.

What's The Right Thing To Do with https://crates.io/crates/rust-sqlite ?


panic on creating torrent

During running create /Users/test/Downloads/GUI.Mac.M1.Tonutils.Proxy.dmg bbb command I received error:
▀  Scanning files... (0s)panic: runtime error: slice bounds out of range [52:51]

goroutine 1 [running]:
github.com/xssnick/tonutils-storage/storage.CreateTorrent.func1({0x1400020a587, 0x33}, {0x100ef8db0?, 0x14000074a90?}, {0x0?, 0x0?})
	/Users/xssnick/dev/ton/tonutils-storage/storage/create.go:62 +0x4dc
path/filepath.walk({0x1400020a587, 0x33}, {0x100ef8db0, 0x14000074a90}, 0x140001e6ec0)
	/usr/local/go/src/path/filepath/path.go:433 +0xd0
path/filepath.Walk({0x1400020a587, 0x33}, 0x140001e6ec0)
	/usr/local/go/src/path/filepath/path.go:520 +0x6c
github.com/xssnick/tonutils-storage/storage.CreateTorrent({0x1400020a587, 0x33}, {0x1400020a5bb, 0x3}, {0x100ef9798, 0x1400023ecc0}, {0x100ef9460, 0x14000226840})
	/Users/xssnick/dev/ton/tonutils-storage/storage/create.go:53 +0x270
main.create({0x1400020a587?, 0x3e?}, {0x1400020a5bb?, 0x1?})
	/Users/xssnick/dev/ton/tonutils-storage/cli/main.go:245 +0x4c
main.main()
	/Users/xssnick/dev/ton/tonutils-storage/cli/main.go:192 +0x12e0

v0.2.0 Released with support of creation from files, could you please try again?

Now separate files are added without errors. Information about the file from the local machine is visible on the VPS. But the file is not downloading. Directories are loaded normally.
In the "Completed" row, the value for files is false, for the directory - true.

Released v0.2.1, Included fix for this too, check please

If I create a torrent from a file like this create ./GUI.Mac.M1.Tonutils.Proxy.dmg aaa or like this create ton-torrent-mac-apple-silicon.dmg zzz111 it causes problems on the downloader side (using the official client).
FATAL ERROR: Invalid torrent header: Invalid torrent header: Invalid dir_name: Name can't start with '/'.

If I create a torrent from a file like this create ./GUI.Mac.M1.Tonutils.Proxy.dmg aaa or like this create ton-torrent-mac-apple-silicon.dmg zzz111 it causes problems on the downloader side (using the official client). FATAL ERROR: Invalid torrent header: Invalid torrent header: Invalid dir_name: Name can't start with '/'.

Fixed in v0.2.2

The server is unable to download a single file with the new version. However, the downloading of directories proceeds without issue. Official client can get the name of the file, but the download process for the file simply has not started. The file was added using the command create ton-torrent-mac-apple-silicon.dmg macsil.

The server is unable to download a single file with the new version. However, the downloading of directories proceeds without issue. Official client can get the name of the file, but the download process for the file simply has not started. The file was added using the command create ton-torrent-mac-apple-silicon.dmg macsil.

I changed behavior in v0.2.3, it will work between tonutils-storage nodes. But not sure about storage-daemon, I think it may not work with empty directory names, so single file torrents may be incompatible by design, I will reach them to raise this issue.
For now you can use single file torrents with tonutils-storage

Tested v0.2.3 with storage-daemon, works fine for me too.


gist:SchemaMetaData can have a formal definition

If I were to look for instances of gist:SchemaMetaData in use without using that URI I would write a query like:
select * where {
:schemametadata0 a gist:Content .
:spec0 a gist:Specification .
:spec0 gist:isExpressedIn|^gist:isAbout|gist:isRenderedOn :schemametadata0 .
:data0 gist:conformsTo :spec0 .
:data0 a gist:Content .
}

And in gisty english: Schema Meta Data is Content that expresses a Specification and some other Content conforms to that specification.
I think we can turn that into a formal definition, right?

That is an interesting stab at defining SchemaMetadata, and captures some important meaning. One subclass of SchemaMetadata is Column, as in a RDB table.  It's not obviously necessarily true that the column, middleName is a specification that some content conforms to.  Its a stretch to suppose that everythign we might conceive as SchemaMetaData would have to conform to this definition.  I see this class as being a bit like Intention, very abstract, not intended (so to speak) to be formally definable and used mostly as a topical grouping of classes that are similar in some intuitively graspable way.

It's not obviously necessarily true that the column, middleName is a specification that some content conforms to.

Sure it is. If you look at the DDL for a table definition you'll see a column is a specification for the kind of values it can take.

PROPOSAL: close this issue w/o doing anything.
Two main reasons.

I am not convinced that everything we think of as SchemaMetaData would conform to the proposed definition.  SchemaMetaData is a bit like Intention, very abstract, not intended to be formally definable and used mostly as a topical grouping of classes.
Even if it was, it is not clearly useful to have the definition.
As stated the definition cannot be expressed in OWL because it requires a rule that two variables are different from one another.


HTML Element with ID not Rendering Inside Editor

Im running into an issue when inserting the below html span element to the editor with an ID: "< span id='incInsert'>< /span>"
The value of the text editor is contained within React State and when console.logging state i can see the span element in there:

However, the span element doesnt exist when inspecting via chrome dev tools and thus in the DOM.
The reason why I need this element to exist in the DOM is because i need to use document.getElementById('incInsert') to insert HTML into the span element which is done later in my submit function.
TIA

Got something?
I'm wanting to do the same thing and I've tried it in every way I thought


Add Microsoft.VisualStudio.Component.VC.Redist.MSM for Visual Studio 2019 in Windows Server 2019

Tool information

Tool name: Microsoft.VisualStudio.Component.VC.Redist.MSM
Add
Desired version:
Approximate size:
If this is an add request:

Brief description of tool: Visual Studio Enterprise 2019 individual component "Redist MSM"
URL for tool's homepage: https://docs.microsoft.com/en-us/visualstudio/install/workload-component-id-vs-build-tools?view=vs-2019

Area for Triage: C/C++
Question, Bug, or Feature?: Feature
Virtual environments affected

[ ] macOS 10.15
[ ] Ubuntu 16.04 LTS
[ ] Ubuntu 18.04 LTS
[ ] Windows Server 2016 R2
[x] Windows Server 2019

Can this tool be installed during the build?
Currently, as a workaround, we install this component via the PowerShell, using the following command:
Start-Process "C:\Program Files (x86)\Microsoft Visual Studio\Installer\vs_installer.exe" -ArgumentList 'modify --installPath "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise" --quiet --add Microsoft.VisualStudio.Component.VC.Redist.MSM' -Wait -PassThru
It takes 10-15 minutes to install, that's why we would like to have it installed in advance to reduce the duration of every build.
Are you willing to submit a PR?
Kindly, add this component name Microsoft.VisualStudio.Component.VC.Redist.MSM into the VS 2019 installation script here https://github.com/actions/virtual-environments/blob/master/images/win/scripts/Installers/Windows2019/Install-VS2019.ps1 into $WorkLoads list. This should do it.

@allexzander sorry for the delay in looking at this. Is it still an issue for you?

@allexzander sorry for the delay in looking at this. Is it still an issue for you?

Hi @alepauly,
We are using a workaround by manually installing this component during the build process. It would be nice to have it added by default into a virtual OS image, so we would save the time spent for the installation for every build.

Hi @allexzander, we briefly looked into it and considering the size of the component and maintenance concerns, we won't be baking it into the image at this time.

@alepauly And how about now? In fact, the merge modules is a crucial component in many CI/CD builds where an MSI package depends on this type of VC runtime redistribution.

https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md claims that winndows-2019 image contains Microsoft.VisualStudio.Component.VC.Redist.MSM at least for the past two years.
Note that Microsoft.VisualStudio.Component.VC.Redist.MSM is missing from windows-2022 image, that is supposed to be fixed in https://github.com/actions/virtual-environments/issues/5143.


Link to OTel JS website_docs via submodule

This is an implementation of #661 similar to what #690 did for go

@dyladan, this PR might be superseded by the actions proposed in #720. If not, could you resolve the conflicts? Thanks!

Closing as this is superseded by the decision in #720


fix: adjust sequence number for app-id compatibility with palo alto fw

https://github.com/aporeto-inc/enforcerd/pull/1948

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "seq-num",
    "component": "trireme-lib",
    "pr-id": "1035",
    "commit-sha": "c7c5ab8b07bcd0277445091f3024be69e8a2e5f6",
    "pipeline": "release-3.14.0"
  },
  {
    "project": "seq-num",
    "component": "enforcerd",
    "pr-id": "1969",
    "commit-sha": "57da42e12150eebe916669336380b75c62904a6a",
    "pipeline": "release-3.14.0"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "seq-num",
    "component": "enforcerd",
    "pr-id": "1969",
    "commit-sha": "57da42e12150eebe916669336380b75c62904a6a",
    "pipeline": "release-3.14.0"
  },
  {
    "project": "seq-num",
    "component": "trireme-lib",
    "pr-id": "1035",
    "commit-sha": "ebaf65a9e97f2e5aff1d1ddcaef4198324fb47b8",
    "pipeline": "release-3.14.0"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "seq-num",
    "component": "enforcerd",
    "pr-id": "1969",
    "commit-sha": "57da42e12150eebe916669336380b75c62904a6a",
    "pipeline": "release-3.14.0"
  },
  {
    "project": "seq-num",
    "component": "trireme-lib",
    "pr-id": "1035",
    "commit-sha": "e21fc17e8357cc8c2797e82f657c6870ed4e40e8",
    "pipeline": "release-3.14.0"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "seq-num",
    "component": "enforcerd",
    "pr-id": "1969",
    "commit-sha": "57da42e12150eebe916669336380b75c62904a6a",
    "pipeline": "release-3.14.0"
  },
  {
    "project": "seq-num",
    "component": "trireme-lib",
    "pr-id": "1035",
    "commit-sha": "fe231c5edba615c077956bab825c2bfcb4004868",
    "pipeline": "release-3.14.0"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "seq-num",
    "component": "enforcerd",
    "pr-id": "1969",
    "commit-sha": "57da42e12150eebe916669336380b75c62904a6a",
    "pipeline": "release-3.14.0"
  },
  {
    "project": "seq-num",
    "component": "trireme-lib",
    "pr-id": "1035",
    "commit-sha": "11022ad9fa76a5a9f441a6c9287efb6f0ef1b850",
    "pipeline": "release-3.14.0"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "seq-num",
    "component": "enforcerd",
    "pr-id": "1969",
    "commit-sha": "57da42e12150eebe916669336380b75c62904a6a",
    "pipeline": "release-3.14.0"
  },
  {
    "project": "seq-num",
    "component": "trireme-lib",
    "pr-id": "1035",
    "commit-sha": "ed544c31376b6d169718a1692566b76ff9a55f5b",
    "pipeline": "release-3.14.0"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "seq-num",
    "component": "enforcerd",
    "pr-id": "1969",
    "commit-sha": "57da42e12150eebe916669336380b75c62904a6a",
    "pipeline": "release-3.14.0"
  },
  {
    "project": "seq-num",
    "component": "trireme-lib",
    "pr-id": "1035",
    "commit-sha": "ed544c31376b6d169718a1692566b76ff9a55f5b",
    "pipeline": "release-3.14.0"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "seq-num",
    "component": "enforcerd",
    "pr-id": "1969",
    "commit-sha": "f689cbb4589527b62d98e790f4270c6208f86db7",
    "pipeline": "release-3.14.0"
  },
  {
    "project": "seq-num",
    "component": "trireme-lib",
    "pr-id": "1035",
    "commit-sha": "ed544c31376b6d169718a1692566b76ff9a55f5b",
    "pipeline": "release-3.14.0"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "seq-num",
    "component": "enforcerd",
    "pr-id": "1969",
    "commit-sha": "926e87e201562555cb215f8f3df371c2a525f600",
    "pipeline": "release-3.14.0"
  },
  {
    "project": "seq-num",
    "component": "trireme-lib",
    "pr-id": "1035",
    "commit-sha": "8fd66b132c1dfcb5b3359b59ac8b14b250d7b555",
    "pipeline": "release-3.14.0"
  }
]

confirmed by @Rohit4793 @sibicramesh and @amitlimaye ... merging this now so that we can adjust the Gopkg.lock on the enforcer PR.


fixing a bug in the ios Setup guide

There was an error while validating job 901d3661-59ae-41c3-be01-527d69f9d092 Message:Error clonning repositoryDetails:System.ArgumentException: Error clonning repository ---> System.Exception: Error when trying to initialize shared repository ---> LibGit2Sharp.NotFoundException: Branch 386 not found. Available branches:
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.GetBranch(Repository repo, String name)
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.<>c__DisplayClass3e.b__3d()
at Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling.RetryPolicy.<>c__DisplayClass1.b__0()
at Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling.RetryPolicy.ExecuteAction[TResult](Func1 func)    at Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling.RetryPolicy.ExecuteAction(Action action)    at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.InitializeSharedRepository(String url, IDictionary2 branches, String sharedRepoPath)
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.VerifySharedRepository(String url, IDictionary2 branches, String tempPath)    --- End of inner exception stack trace ---    at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.VerifySharedRepository(String url, IDictionary2 branches, String tempPath)
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.CloneRepository(String url, IDictionary2 branches)    --- End of inner exception stack trace ---    at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.CloneRepository(String url, IDictionary2 branches)
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.CloneRepository()
at Microsoft.DPS.Services.LibGit2SharpSourceControlProvider.GetTreeAsync(String path, Boolean includeSubDirectories, String excludePath, IList1 extensionWhiteList)    at Microsoft.DPS.Commands.IdentifyDocumentsToPublish.ListSourceControlFilesCommand.Do(IDictionary2 context)
at Microsoft.LightweightJobEngine.Core.Language.JobWorkflow1.RunCommands(Guid jobId, IDictionary2 context, CancellationTokenSource cancelSignal)


Probable Security Issue

Hi @alexc-MSFT, there might be one possible security issue. I have reported the issue in the security centre 4 days ago. I think I have the solution that might fix this for now but wanted to discuss this. Can we connect somewhere?
Regards,
Sanket

@loflet I have contacted you via LinkedIn so will close this issue here.


[AIRFLOW-1118] Add evo.company to Airflow users

Dear Airflow maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title.

https://issues.apache.org/jira/browse/AIRFLOW-1118

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

This is just docs improvement

Codecov Report

Merging #2243 into master will increase coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2243      +/-   ##
==========================================
+ Coverage   68.73%   68.77%   +0.03%
==========================================
  Files         142      142
  Lines       10926    10926
==========================================
+ Hits         7510     7514       +4
+ Misses       3416     3412       -4

Impacted Files
Coverage Δ

airflow/jobs.py
73.28% <0%> (+0.4%)
:arrow_up:

Continue to review full report at Codecov.

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

Welcome to the community!


GetPC() always returns nullptr

As PC_FROM_UCONTEXT is never defined, GetPC() always returns nullptr: https://github.com/google/glog/blob/64827572c0612e6eb15ed324d8c4fa020a0c5a41/src/signalhandler.cc#L76-L86
Possible fix:

update https://github.com/google/glog/blob/64827572c0612e6eb15ed324d8c4fa020a0c5a41/CMakeLists.txt#L215-L233 by prefixing each entry with uc_mcontext./uc_mcontext-> (https://github.com/couchbase/gperftools/blob/846b775dfadb77901202ae7ddbac30ad1de7df01/m4/pc_from_ucontext.m4#L23-L43 seems to provide an up-to-date list of fields)
update try_compile () invocation. https://github.com/google/glog/blob/64827572c0612e6eb15ed324d8c4fa020a0c5a41/CMakeLists.txt#L251-L252 should say -D_GNU_SOURCE=1
set cache variable correctly (set (PC_FROM_UCONTEXT ${_PC_FIELD} CACHE STRING ""))
define the macro correctly (#cmakedefine PC_FROM_UCONTEXT ${PC_FROM_UCONTEXT})

Good catch, thanks! Could you please submit a PR with the corresponding changes?


Add working example of distributed tensorflow using estimator api kmeans

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):UNIX
TensorFlow installed from (source or binary):Source
TensorFlow version (use command below):1.5
Python version: 3.6
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:
Exact command to reproduce:

Describe the problem
I am using kmeans estimator for distributed tensorflow. I have a cluster of three machine and i have updated TF_CONFIG on all three machine. I am using hdfs to store model directory so that all machine can access to that folder, but when i ran python file from my master machine, gRPC server got created after that "PS server and Worker server waiting for response from master"  this message repeated after every 10 sec.
Source code / logs
import tensorflow as tf
import numpy as np
import pandas as pd
k = 5
n = 100
variables = 2
points = np.random.uniform(0, 1000, [n, variables])
input_fn=lambda: tf.train.limit_epochs(tf.convert_to_tensor(points, dtype=tf.float32), num_epochs=1)
kmeans=tf.contrib.factorization.KMeansClustering(num_clusters=k, use_mini_batch=False,model_dir="my_hdfs_path")
train_spec = tf.estimator.TrainSpec(input_fn=input_fn, max_steps=100)
eval_spec = tf.estimator.EvalSpec(input_fn=input_fn)
tf.estimator.train_and_evaluate(kmeans, train_spec, eval_spec)
list(kmeans.predict(input_fn=input_fn))
TF_CONFIG:
{ "cluster":{ "chief":[ "master:22220" ], "ps":[ "slave02:22220" ], "worker":[ "slave01:22220" ] }, "task":{  "type":"chief", "index":0, } }
Error message:
CreateSession still waiting for response from worker: /job:ps/replica:0/task:0
CreateSession still waiting for response from worker: /job:worker/replica:0/task:0

Interestingly enough I just created a question in SO about the serving input function requesting some example on how to actually do that.
I would be happy to contribute with an example once this question is resolved, although your question pretty much is about input when using the standard Estimator API :)

@martinwicke  what do you think?

@cy89 @ccolby please have a look at this issue

Nagging Assignee @bignamehyp: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @bignamehyp: It has been 67 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @bignamehyp: It has been 82 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @bignamehyp: It has been 112 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @bignamehyp: It has been 112 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @bignamehyp: It has been 127 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @bignamehyp: It has been 141 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @bignamehyp: It has been 157 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


Implement string interpolation

Python supports interpolation, via printf (%) and string.format() - Horrid to use stuff like "fish" + str(my_int) + "frog")
Either option would be fine, but I'd recommend taking a leaf out of Boo, which uses direct interpolation: "fish $(my_int) frog" (which is also similar to how Ruby does it too).

I would rather adapt that library instead of using it, so Godot can keep
the no dependency upon C++ standard libraries, using the template types in
Godot
On Wed, Jan 7, 2015 at 10:47 AM, Bil Bas<EMAIL_ADDRESS>wrote:

@okamstudio https://github.com/okamstudio I'm giving this a go using
https://github.com/cppformat/cppformat to implement python style
string.format() method and sprintf (format_string % args_array). Is that OK
to add to the project? I tried to work out how to leverage standard
sprintf(), but I couldn't see a way to use that with an arbitrary array of
different typed values.
—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/issues/1131#issuecomment-69023234.

You mean not using std::string at all? fmt::sprintf() and fmt::format() accepts int/float/c_str and I can get that from the Variants and outputs a std::string, but I can convert that into a String before returning them, can't I?
I don't think re-writing printf() and format() are within my willingness to waste time over, I'm afraid ;)

either that or use a C library
On Wed, Jan 7, 2015 at 11:06 AM, Juan Linietsky<EMAIL_ADDRESS>wrote:

I would rather adapt that library instead of using it, so Godot can keep
the no dependency upon C++ standard libraries, using the template types in
Godot
On Wed, Jan 7, 2015 at 10:47 AM, Bil Bas<EMAIL_ADDRESS>wrote:

@okamstudio https://github.com/okamstudio I'm giving this a go using
https://github.com/cppformat/cppformat to implement python style
string.format() method and sprintf (format_string % args_array). Is that
OK
to add to the project? I tried to work out how to leverage standard
sprintf(), but I couldn't see a way to use that with an arbitrary array
of
different typed values.
—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/issues/1131#issuecomment-69023234.

—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/issues/1131#issuecomment-69025468.

--
OkamStudio

The library looks way too complex for what is intended to do and, while the
functionality is desired, it is not worth it for having it as a dependency.
On Wed, Jan 7, 2015 at 11:13 AM, Okam Studio<EMAIL_ADDRESS>wrote:

either that or use a C library
On Wed, Jan 7, 2015 at 11:06 AM, Juan Linietsky<EMAIL_ADDRESS>wrote:

I would rather adapt that library instead of using it, so Godot can keep
the no dependency upon C++ standard libraries, using the template types
in
Godot
On Wed, Jan 7, 2015 at 10:47 AM, Bil Bas<EMAIL_ADDRESS>wrote:

@okamstudio https://github.com/okamstudio I'm giving this a go
using
https://github.com/cppformat/cppformat to implement python style
string.format() method and sprintf (format_string % args_array). Is
that
OK
to add to the project? I tried to work out how to leverage standard
sprintf(), but I couldn't see a way to use that with an arbitrary
array
of
different typed values.
—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/issues/1131#issuecomment-69023234.

—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/issues/1131#issuecomment-69025468.

--
OkamStudio
—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/issues/1131#issuecomment-69026341.

Fair enough - thanks for the responses. I'll maybe look at simpler things to implement then ;)

No worries, I'm sure it sounds strange, but keeping engine core small and
efficient is really difficult. Godot has a huge amount of functionality
that needs to be very restrained and to the point, otherwise the engine
binary starts growing easily. This happened with previous versions of the
engine and it was quite a problem. Due to this is that we do so much NIH
programming in the core instead of using other libraries, even the C++
standard library (which produces huge debug binaries due to the high
template complexity).
The situation is different in the editor, which is not as much size
constrained, adding libraries there is fine.
On Wed, Jan 7, 2015 at 11:21 AM, Bil Bas<EMAIL_ADDRESS>wrote:

Fair enough - thanks for the responses. I'll maybe look at simpler things
to implement then ;)
—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/issues/1131#issuecomment-69027417.

I'm not a fan of NIH in general, but I get your point about bloat (and I loved that I could just clone the repo and compile it on Linux with NO PAIN). I guess there are plenty of printf() sources that could be adapted to use your String class without a huge amount of effort (e.g. http://www.opensource.apple.com/source/shell_cmds/shell_cmds-170/printf/printf.c).
I might change my mind about doing that myself, but I suspect that my time might be better used in adding other things to GDScript (It felt a bit limiting when I tried doing things with it, since I'm used to Python/Boo level of functionality).

Allright! And yeah, gdscript is simpler than python mostly for performance
and simplicity, but if there are features missing that don't conflict with
those goals, I don't see why adding them should be a problem
On Jan 7, 2015 11:44 AM, "Bil Bas"<EMAIL_ADDRESS>wrote:

I'm not a fan of NIH in general, but I get your point about bloat (and I
loved that I could just clone the repo and compile it on Linux with NO
PAIN). I guess there are plenty of printf() sources that could be adapted
to use your String class without a huge amount of effort (e.g.
http://www.opensource.apple.com/source/shell_cmds/shell_cmds-170/printf/printf.c
).
I might change my mind about doing that myself, but I suspect that my time
might be better used in adding other things to GDScript (It felt a bit
limiting when I tried doing things with it, since I'm used to Python/Boo
level of functionality).
—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/issues/1131#issuecomment-69030497.

Mury please tone down, no one has done any harm here, what would the point
of making something open source if everyone was expected or forced to
contribute back to use it? Also, how would it be possible to make good
quality software if users could not express their needs? Please treat other
users and developers with more respect.

—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/issues/1131#issuecomment-69037536.

And reporting bugs and making suggestions and requests IS contribution to the project. Expecting the devs to jump when you ask for something is unreasonable though - either I'll do this or another contributor will or the devs will get around to it in a year or it won't happen.

sprintf seems to cover this OK (and particularly adds the ability to format numbers and strings nicely). Would be nice to have direct interpolation, as in Ruby/Boo, but I think this would require deeper changes to the interpreter.


Missing WSA Planefinding.dlls in MixedRealityToolkit-Unity

Planefinding.dlls missing for MixedRealityToolkit-Unity WSA builds.
https://github.com/Microsoft/MixedRealityToolkit-Unity/issues/629
https://github.com/Microsoft/MixedRealityToolkit-Unity/issues/769

Fixed in the Dev branch with commit Microsoft/MixedRealityToolkit-Unity@dc4375db8643632565fa21c4d21893d7f098a98d. Working on doing a full pass of DLL updates in master soon.


netbird-ui: 0.27.3 -> 0.27.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for netbird-ui is: Connect your devices into a single secure private WireGuard®-based mesh network with SSO/MFA and simple access controls
meta.homepage for netbird-ui is: https://netbird.io
meta.changelog for netbird-ui is: https://github.com/netbirdio/netbird/releases/tag/v0.27.4
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.27.4 with grep in /nix/store/98wp976dz1m16m45vv4vqmib88hnvp2d-netbird-0.27.4
found 0.27.4 in filename of file in /nix/store/98wp976dz1m16m45vv4vqmib88hnvp2d-netbird-0.27.4

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

netbird
netbird-ui

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/f856f53b908763a725ea0ccf2c84963367a7469f#netbird-ui

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

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

2 packages built:

netbird
netbird-ui

Maintainer pings
cc @misuzu for testing.

Result of nixpkgs-review pr 308042 run on aarch64-darwin 1

2 packages built:

netbird
netbird-ui


Reboot on takeover install

The current behaviour to poweroff during takeover installs is unexpected. This PR changes that behaviour to reboot instead.

This might be better addressed by something like #143 which I've been meaning to validate and include in a release.

From what I can tell #143 fixes another problem entirely, it's fixing some reboot/poweroff problem when running the install.sh script. This fix is not for when you run install.sh but after that first reboot and k3os is actually installed, i.e. after the first reboot it installs k3os and powers down instead of reboots another time to start the new system.

As discussed with @zimme in the rancher-users #k3os slack channel my current hold up with this is an as of yet not validated hunch that the current behavior is depended upon by the AWS/GCP packer builds. Working on validating this Soon ™

I've tested the AWS packer thing now and it seems to still work. Running packer build ./template.json from form the aws directory with a changed region ´eu-north-1` creates a packer build instance and terminates it after an AMI has been created and I can launch an instance from that.
I don't know if it's a problem that the installed k3os system probably boots during the packer build stage so the AMI is generateed from a running k3os instance?
In the case before this change I guess the installed k3os instance during the build stage is never started and the AMI is generated from a k3os system that has never been started.

So I just checked this again and it seems my suspicions were correct.
Looking at the output of kubectl get nodes -o wide on a freshly deployed instance from the AMI build via packer with this change I'm seeing the following
NAME                                           STATUS   ROLES    AGE   VERSION         INTERNAL-IP     EXTERNAL-IP   OS-IMAGE       KERNEL-VERSION      CONTAINER-RUNTIME
ip-172-31-2-104.eu-north-1.compute.internal    Ready    master   10h   v1.16.2-k3s.1   <IP_ADDRESS>    <none>        k3OS adfea69   4.15.0-66-generic   containerd://1.3.0+unknown
ip-172-31-13-221.eu-north-1.compute.internal   Ready    master   2s    v1.16.2-k3s.1   <IP_ADDRESS>   <none>        k3OS adfea69   4.15.0-66-generic   containerd://1.3.0+unknown
ip-172-31-13-221 [~]$

As you can see there is 2 nodes present, the one that's not ready is the master node that was configured during the first boot while building the AMI so we need to find a way to make the reboot on takeover install configurable in all stages of the takeover install or find another way of building an AMI.

Updated this to respect --poweroff. I'll update this post with some more context once I'm back, gotta run.

Fixed the check for k3os/system/poweroff and verified that it works on AWS.
I don't know if any other packer config needs updating too?

Is there any reason not to merge this and #143?

I would also like to see this merged.

Just a note on this. There might be updates to packer configs to add --poweroff needed as I haven't tested all packer configs.

Thank you. Working now.


Bug in example-forum, example-forms and example-movies: delete function does not work

Hi there,
in the example-forum, when trying to delete a post from my own, the following error message shows up: cannot convert undefined or null to object. Could you please check it? Thanks a lot in advance!

Update: I have checked it around. It seems that delete function does not work in all of the three examples mentioned above. However, I think a few weeks before, the delete function did work. Is it due to some update in the vulcanjs version? Could you please kindly fix it? Thank you so much in advance.

Hi,
any update on this issue?

Hi, I've managed to reproduce this issue. It may just be an UI issue, I don't know yet.

Closing because I don't have this issue on the latest "devel" branch.


Allow specification of target SHA for dynamic repositories

GitLink also supports target sha (a build might be running later and otherwise use a different commit to calculate the version). By default it should use the latest, otherwise it must use the specified commit SHA.

working on it.


benchmark.py doesn't work (on linux)

I've tried using bechmark.py and identified the following problems:

it tries to use an executable named rayx.exe that doesn't exist on linux
It cannot be called from the Scripts directory, instead you need to be in the repository root and call it as python Scripts/benchmark.py
path_to_input looks for a directory named "scripts" and not "Scripts" (how did this ever work for anyone? is windows case insensitive?)
what even is this output:

,Value
CPU model,x86_64
CPU cores,8
Total RAM,5.74GB
GPU model,No GPU found
Total GPU memory,N/A

It doesn't even show the time it took. (Should I run this within time?)

The instrumentor currently doesn't work at all on development and needs to be fixed first. Then we can fix the benchmark function for Linux.

TODO: decide to do benchmarking during runtime and remove json functionality

Benchmarking works now on Ubuntu

I got very interesing results:

Needs further testing to see whether the OS or the compiler makes such a difference.

@EnricoAhlers just fixed the aforementioned issues. Thanks!


feature: catnip v3 and API v8 support

As this makes some backwards-incompatible changes, this is a major version bump.
This is a WIP based off of https://github.com/discord/discord-api-docs/pull/2097.

An overview of changes

API v8 is the minimum required version. All the related v8 changes have been added, see the linked PR above.
Intents will actually warn properly if you're using them incorrectly now.
API version and intents are sanity-checked.
DM channels are no longer cached; they're fetched on-demand as needed.
ALL cache-related methods, and anything that touches them, return Rx operators instead of entities directly.
Member chunking is disabled by default.
Missing guild features added.

Q. Why does <this method> return an Rx operator, but <that method> returns an entity class?
A. This is due to how the Discord API works, and the points at which it does/not actually provide an entity.

APIv8 docs have been merged, so choo choo 🚂


Blocks are pushed in the interpreter now.

I am now pushing the new blocks from the interpreter and we don't need to update the server state in this convoluted way, anymore.
Pre-submit checklist:

Branch

[ ] Commit sequence broadly makes sense
[ ] Key commits have useful messages
[ ] Relevant tickets are mentioned in commit messages
[ ] Formatting, materialized Nix files, PNG optimization, etc. are updated

PR

[ ] Self-reviewed the diff
[ ] Useful pull request description
[ ] Reviewer requested

Pre-merge checklist:

[ ] Someone approved it
[ ] Commits have useful messages
[ ] Review clarifications made it into the code
[ ] History is moderately tidy; or going to squash-merge

Still has some compiler warnings


Should Client detect system clock not sync'ed?

Since client polling schedule is determined by earliest_completion_time returned by SAPI as an absolute ISO8601 time in UTC, correct timing depends on the correctness of user's system clock.
Should we try to detect too big of a discrepancy from the time returned by server (in HTTP headers) and local clock?

Resolution: when too big discrepancy detected, ignore earliest_completion_time and fallback to exponential back-off, starting at 1 second delay.

Closed in #249.


Summary Table on top of page

This is an awesome resource, thank you for putting it together. Is it possible to add a table to the top of the page with each state's most recent update?

I second this.
I have been working around this by adding this css to the page. Maybe a switch can be added to toggle between the two.
tr:not(:first-child) {display: none;}

@asielen I think this will work? been a bit since I messed with it:
tr:not(:first-child) td:not(:nth-child(0)){     display: none; }

My pull request has a modified python script to also generate a "compact" chart.

A 'last update' section - which state updated most recently, and how long ago, would be handy. Or a brief running list - a 'change log' of sorts...

I am -1 on this. I think it's an idea with some merit, but at this point I don't think we should add any more visual complexity to the page.

Agree with @fractionalhare, I don't think we want to make it visually any more complex at this time. We may revisit the UX at some point, but for now, the simplicity is a large part of the appeal.


Add curry sauce

This is some small fixes.
Grammar and spelling.
Adds °C conversions.
Makes the recipes more consistent with example.md and other recipes.


Extend ImageFolderDataset to support import of COCO detection data

Pull Request Template
Checklist

[x] Confirmed that run-checks all script has been executed*.
* with wgpu errors not related to this PR
[x] Made sure the book is up to date with changes in this PR.

Changes
COCO is a popular dataset which defines an own dataset format: https://cocodataset.org/#format-data
This commit introduces an ImageFolderDataset::new_coco_detection() function, which expects a path to the JSON annotations file in COCO format and a path where the actual images are stored.
Note, that while COCO also offers segmentation and pose estimation data, for now only the import of detection (bounding boxes) data is supported.
Testing
Apart from testing with actual COCO data, a small dataset containing three images and annotations in COCO format has been added to crates/burn-dataset/tests/data. Each image has a different amount of annotations, the test checks if the imported dataset contains the correct number of images and the expected number of annotations per image.

@laggui updated, I usually amend and force push to keep the history clean, hope that's OK for you.

I usually amend and force push to keep the history clean, hope that's OK for you.

Might mess up the github review UI for stuff that was already reviewed and untouched, but I don't have any issues with that. We squash & merge anyway so it will be reduced to a single commit 👍
Looks like the comment update was missed, otherwise it will be good to go!

sorry, C&P fail 🤦🏻♂

Thank you 🙏


Help needed running puzzle tests

Hi,
I wanted to have a look at puzzle but got the following error:

Puzzle is correctly installed.
Can you help me?
Thanks,
Bianca

Hi Bianca, glad you are testing!
The documentation is not really up to date, if you run puzzle --help you will see:
Usage: puzzle [OPTIONS] ROOT COMMAND [ARGS]...

  Puzzle: manage DNA variant resources.

Options:
  -p, --plugin [vcf|gemini]
  -v, --verbose
  --help                     Show this message and exit.

Commands:
  view  Visualize DNA variant resources.

so you need to use the command view to test it.
If you want to run on the test data do
puzzle tests/ view

Or you can point on another directory with your own files.
If you want to try with a gemini database do
puzzle --plugin gemini path/to/database.db view

Good luck!

:+1:


Add WORKFLOW_BACKEND_HOST to code-executor deployment

If retool workflows are enabled, code-executor deployments need to know which workflow backend to talk to. Before this update, users of the chart would have to inject this env var manually.
With this PR, I am proposing to add the (conditional) environment variable WORKFLOW_BACKEND_HOST to the code-executor deployment in the same way that it is being added in the other deployment manifests.

Hey @tomknig thanks for the PR. The code executor receives the workflow backend host dynamically for each request, so there is not a fixed workflow backend host that can be respected in environment variables. Will go ahead and close out this PR!


Checkbox Syntax Not Displaying In Releases Greater Than 3.6.1

🐛 Describe the bug
The fancy checkbox syntax displays properly on release 3.6.1 and lower.
With 3.7.0+, the checkboxes display the standard syntax.
Using conceallevel=2.  I also tried 0,1,3 and had the same problem.
3.6.1:

3.7:

Config
return {
  "epwalsh/obsidian.nvim",
  version = "3.7.0",  -- recommended, use latest release instead of latest commit
  lazy = true,
  ft = "markdown",
  -- Replace the above line with this if you only want to load obsidian.nvim for markdown files in your vault:
  -- event = {
  --   -- If you want to use the home shortcut '~' here you need to call 'vim.fn.expand'.
  --   -- E.g. "BufReadPre " .. vim.fn.expand "~" .. "/my-vault/**.md"
  --   "BufReadPre path/to/my-vault/**.md",
  --   "BufNewFile path/to/my-vault/**.md",
  -- },
  dependencies = {
    -- Required.
    "nvim-lua/plenary.nvim",

    -- see below for full list of optional dependencies 👇
  },
  opts = {
    workspaces = {
      {
        name = "REDACTED",
        path = "REDACTED",
      },
      {
        name = "REDACTED",
        path = "REDACTED",
      },

    -- Optional, configure additional syntax highlighting / extmarks.
    -- This requires you have `conceallevel` set to 1 or 2. See `:help conceallevel` for more details.
    ui = {
      enable = true,  -- set to false to disable all additional syntax features
      update_debounce = 200,  -- update delay after a text change (in milliseconds)
      -- Define how various check-boxes are displayed
      checkboxes = {
        -- NOTE: the 'char' value has to be a single character, and the highlight groups are defined below.
        [" "] = { char = "󰄱", hl_group = "ObsidianTodo" },
        ["x"] = { char = "", hl_group = "ObsidianDone" },
        [">"] = { char = "", hl_group = "ObsidianRightArrow" },
        ["~"] = { char = "󰰱", hl_group = "ObsidianTilde" },
        -- Replace the above with this if you don't have a patched font:
        -- [" "] = { char = "☐", hl_group = "ObsidianTodo" },
        -- ["x"] = { char = "✔", hl_group = "ObsidianDone" },

        -- You can also add more custom ones...
      },
      -- Use bullet marks for non-checkbox lists.
      bullets = { char = "•", hl_group = "ObsidianBullet" },
      external_link_icon = { char = "", hl_group = "ObsidianExtLinkIcon" },
      -- Replace the above with this if you don't have a patched font:
      -- external_link_icon = { char = "", hl_group = "ObsidianExtLinkIcon" },
      reference_text = { hl_group = "ObsidianRefText" },
      highlight_text = { hl_group = "ObsidianHighlightText" },
      tags = { hl_group = "ObsidianTag" },
      block_ids = { hl_group = "ObsidianBlockID" },
      hl_groups = {
        -- The options are passed directly to `vim.api.nvim_set_hl()`. See `:help nvim_set_hl`.
        ObsidianTodo = { bold = true, fg = "#f78c6c" },
        ObsidianDone = { bold = true, fg = "#89ddff" },
        ObsidianRightArrow = { bold = true, fg = "#f78c6c" },
        ObsidianTilde = { bold = true, fg = "#ff5370" },
        ObsidianBullet = { bold = true, fg = "#89ddff" },
        ObsidianRefText = { underline = true, fg = "#c792ea" },
        ObsidianExtLinkIcon = { fg = "#c792ea" },
        ObsidianTag = { italic = true, fg = "#89ddff" },
        ObsidianBlockID = { italic = true, fg = "#89ddff" },
        ObsidianHighlightText = { bg = "#75662e" },
      },
    },

    -- see below for full list of options 👇
  },
}

Environment
NVIM v0.9.5
Build type: Release
LuaJIT 2.1.1692716794

Obsidian.nvim v3.7.0 (6888c7620109684371ed9304df2ba68abc78d558)
Status:
   buffer directory: nil
   working directory: /home/erags/code/dotfiles/nvim/.config/nvim
Workspaces:
  ✓ active workspace: Workspace(name='REDACTED', path='REDACTED', root='REDACTED')
  ✗ inactive workspace: Workspace(name='REDACTED', path='REDACTED', root='REDACTED')
Dependencies:
   plenary.nvim: 08e301982b9a057110ede7a735dd1b5285eb341f
   nvim-cmp: 8f3c541407e691af6163e2447f3af1bd6e17f9a3
   telescope.nvim: d90956833d7c27e73c621a61f20b29fdb7122709
Integrations:
   picker: TelescopePicker()
   completion: enabled (nvim-cmp)
Tools:
   rg: ripgrep 13.0.0
Environment:
   operating system: Linux
Config:
   notes_subdir: nil%

I upgraded to 3.8.1 and no longer have this issue.


SkipNavContent is not working

It seems SkipNavContent is not working: on pressing tab right after loading a page or right after clicking on the navigation menu (to get focus there), SkipNavContent does not show up. I think it's expected to be used with SkipNavLink.

Do you have still an issue? It's seems like it's works fine on latest beta 2 version