Add documentation for dot notation in arrays, objects, and embedded documents

Description
Closes #1310.

Readiness checklist

[ ] I added tests for new functionality or bugfixes.
[ ] I ran task all, and it passed.
[ ] I added/updated comments for both exported and unexported top-level declarations (functions, types, etc).
[ ] I checked comments rendering with task godocs.
[x] I ensured that the title is good enough for the changelog.
[x] (for maintainers only) I set Reviewers (@FerretDB/core), Assignee, Labels, Project and project's Sprint fields.
[x] I marked all done items in this checklist.

Waiting for the promised update


Automatic Closing Quotations after Space

Type: Bug
QM = quotation mark
I'm having this issue: inside parentheses, whenever I try to type a closing QM, VSCode automatically types two QM's. When I try to backspace one both. Only way to get around it is to use "delete". It would be helpful if it automatically types the closing QM when I type the opening QM, but instead, it only happens when I add space after typing the opening quotation mark. So I annoyingly get 3 QM's.
 Normally, the " autocompletion would not insert "" if you are already in a string. Here it is working correctly for me:
I am trying with the following C++ code snippet:
int main(void)
{
	int n;
	do {
		n = get_size("Size: ")
	}
}

Do you have any value configured for "editor.autoClosingQuotes"?
Does this reproduce in all files?
Did you by any chance install a different C++ grammar?
Does this reproduce when disabling all extensions?

https://user-images.githubusercontent.com/5047891/230135522-1fcef502-5ead-4054-9953-1164508d63bf.mp4

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Request: Pistol Twirl

Pistol Twirl is a (low-level) feat that enables the Pistolero as it allows him to Feint people at a distance. At the moment, the additional Feint support & effects only work on melee attacks. Any possibility this could be extended to range for Pistol Twirl ?👼
P.S.: love the module :)

Pistol Twirl was added, Need to use action for start after it feint and ranged attack will be trigger effect
In example Rogue trigger flat-footed with attack and damage(sneak attack was added)
0.0.30
https://github.com/reyzor1991/foundry-vtt-pf2e-action-support/assets/6688366/152fb089-4987-4693-a294-fcaaf3a96a6b

@Far2Casual If you want, you can post proposal to discord thread
https://discord.com/channels/880968862240239708/1131271396123742339

You are awesome ! Thanks !


Only show warning when overwrite existing preprocessor

Summary
from the original design of StyleSheet.setStyleAttributePreprocessor() in #11138, the overwriting warning shows when the existing preprocess is be overwritten.  the behavior changes from https://github.com/facebook/react-native/commit/33b385825c72. This PR revises the logic back to original design.
Changelog
[Internal] [Fixed] - Show warning only when overwriting existing preprocessor in StyleSheet.setStyleAttributePreprocessor()
Test Plan
Unit Test
 PASS  Libraries/StyleSheet/__tests__/StyleSheet-test.js
  setStyleAttributePreprocessor
    ✓ should not show warning when set preprocessor first time (2 ms)
    ✓ should show warning when overwrite the preprocessor (1 ms)

also rebase this one for ci fixes


feat(share/discovery): persist discovered peers

Closes #2208

[ ] Integrate option
[ ] Load peers into peer manager

I'm not convinced this is necessary outside of the context of saving peers for bootstrapper usage

I'm not convinced this is necessary outside of the context of saving peers for bootstrapper usage, as I have never seen issues finding peers very quickly once we join the network. In fact, until other errors are fixed, this will probably give the disadvantage that we save bad peers (which is why restarting helps so often)

Think of this in conjunction with Discard, which filters unhealthy peers


Make homepage #GE2015-specific

Close #15

After sleeping on this pull request, I realised this morning that it can't be good practice. Instead I think we should:

Create an app that contains the front-end static content.
Create a fork of the repository so that we can make that app GE2015-specific for our purposes while keeping the upstream system generic.

Since nobody else is using the code in anger yet, though, perhaps we can take this shortcut for now and refactor it after the general election?

I have forked: https://github.com/89up/candidate_questions

Thanks - I will shift this stuff over to the fork.


First swing at task prioritization

#456 suggests priorization to get features started sooner might be a plus. This is my first try, just naively split things into high and low priority and try to launch high priority work as soon as possible.
I see the work rearrange as expected in --emit-timing output. Oswald appears to benefit, apparently for Google Sans rushing to features is less important.
LINUX

Oswald reports gains
	$ cargo build --release && hyperfine --warmup 3 --runs 50 --prepare 'rm -rf build/' 'target/release/fontc --source ../OswaldFont/sources/Oswald.glyphs --emit-ir false'
	pri 		138.8 ms ±   9.0 ms
	main 		148.8 ms ±   8.5 ms

Google Sans isn't so clearly a win
	$ cargo build --release && hyperfine --warmup 3 --prepare 'rm -rf build/' 'target/release/fontc --source ../googlesans/source/GoogleSans/GoogleSans.designspace --emit-ir false'
	pri 		9.656 s ±  0.320 s
	main 		9.683 s ±  0.447 s

M1 MAC

Oswald reports more significant gains
       $ cargo build --release && hyperfine --warmup 10 --runs 100 --prepare 'rm -rf build/' 'target/release/fontc --source ../OswaldFont/sources/Oswald.glyphs --emit-ir false'
       pri     48.8 ms ±   3.8 ms
       main    62.7 ms ±   5.3 ms

Google Sans gains, thought not as significantly as Oswald
       $ cargo build --release && hyperfine --warmup 3 --prepare 'rm -rf build/' 'target/release/fontc --source ../googlesans/source/GoogleSans/GoogleSans.designspace --emit-ir false'
       pri     5.694 s ±  0.029 s
       main    5.821 s ±  0.085 s

On Mac, with this PR applied, timing suggests kerning and fea is just massively the long pole:

what's the status of this?

The timing graph makes it look like it WAI but hyperfine didn't seem to think there was an improvement and then I got distracted :)

Oswald is now so fast hyperfine says it cannot get useful measurements on an M1.


Update deps

Coverage remained the same at 81.503% when pulling 2383794a05f4736e1caf8d893a3280eebb827b97 on update-deps into 62c673ca0b9f919dbcfdb95155250973c99883bb on master.

Coverage remained the same at 81.503% when pulling 00bffef5cdb7b431865bdebcd87aa9bcafa6a48e on update-deps into 62c673ca0b9f919dbcfdb95155250973c99883bb on master.

Coverage remained the same at 81.503% when pulling ee43d2e607ddf078590f19b08f3307bdd0e83448 on update-deps into 62c673ca0b9f919dbcfdb95155250973c99883bb on master.

Coverage remained the same at 81.503% when pulling a24b8530b175e9ea273fbfaec4e57685a4cf4bb9 on update-deps into 62c673ca0b9f919dbcfdb95155250973c99883bb on master.

Coverage remained the same at 81.503% when pulling 430c686633a5c189b4ad7b59dabe8233a8da2d91 on update-deps into 62c673ca0b9f919dbcfdb95155250973c99883bb on master.

Coverage remained the same at 81.503% when pulling 8c2526c6f8c746c4f0c95f552df162761d8de46e on update-deps into 62c673ca0b9f919dbcfdb95155250973c99883bb on master.

Coverage remained the same at 81.503% when pulling d65b204b0e2303b084ca4c1bc518ff90b6fb9e0d on update-deps into 62c673ca0b9f919dbcfdb95155250973c99883bb on master.


scale.nice float rounding issue

Say you want a nice linear scale and ticks for your [5.83, 6.2] domain.
Due to float calculations .nice() sets the domain to:

d3.scaleLinear().domain([5.83, 6.2]).nice().domain()
[5.800000000000001, 6.2]

and .ticks() returns:

d3.scaleLinear().domain([5.83, 6.2]).nice().ticks()
[5.8500000000000005, 5.9, 5.95, 6.000000000000001, 6.050000000000001, 6.1000000000000005, 6.15, 6.2]

Now you are missing the first 5.8 tick.
I know this happens because of float calculations (0.05 * 116), what is the best way to deal with the situation? Should it be solved by d3 or by a user?
I ended up with rounding and resetting the domain with the help of d3.format, but looking for a more general solution.

Thanks for the report. I think we can fix this without too much trouble. This will affect both d3-array and d3-scale, since the core tick methods are in d3-array, but the implementation of linear.nice will be affected. Rather than tracking this in both places, let’s just use d3/d3-array#45.

Just a heads up that I can still reproduce this issue with the latest version of d3-array (1.2.0). I expected https://github.com/d3/d3-array/commit/04cf783bd715cae89303173d50a28fda38c24a9b would solve the problem.
Here are my dependencies:
└─┬<EMAIL_ADDRESS>  ├──<EMAIL_ADDRESS>  ├──<EMAIL_ADDRESS>  ├──<EMAIL_ADDRESS>  ├──<EMAIL_ADDRESS>  ├──<EMAIL_ADDRESS>  ├──<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>
> var d3Scale = require('d3-scale');
undefined
> d3Scale.scaleLinear().domain([5.83, 6.2]).nice().domain()
[ 5.800000000000001, 6.2 ]
> d3Scale.scaleLinear().domain([5.83, 6.2]).nice().ticks()
[ 5.85, 5.9, 5.95, 6, 6.05, 6.1, 6.15, 6.2 ]

No; linear scales still use d3.tickStep, not the new d3.tickIncrement, and so there’s no protection against rounding errors. See linear.js.
However, I don’t see any reason why we couldn’t update linear.nice to use d3.tickIncrement and thus guarantee exact behavior (within the limits of IEEE 754). So I’ll reopen and retitle this issue accordingly.


Problems with in the last update

Hello! I'm updated the dashdot to the last version (V.5.8.0) and now not start. its working in a Synology DSM 7.2.1.
the docker compose it's:

version: "3.9"
services:
dashdot:
container_name: dashdot
image: mauricenino/dashdot
mem_limit: 4g
cpu_shares: 768
security_opt:
- no-new-privileges:true
restart: on-failure:5
volumes:
- /:/mnt/host:ro
ports:
- 7512:3001
privileged: true
environment:
DASHDOT_ENABLE_CPU_TEMPS: true
DASHDOT_OVERRIDE_OS: Synology DSM
Appears this error in the log. Can you help me?
dashdot
date	stream	content
2024/01/21 08:50:13	stdout	$ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] [--require #0]  ...
2024/01/21 08:50:13	stdout
2024/01/21 08:50:13	stdout	Usage Error: Couldn't find a script named "start".
2024/01/21 08:36:38	stdout	$ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] [--require #0]  ...
2024/01/21 08:36:38	stdout
2024/01/21 08:36:38	stdout	Usage Error: Couldn't find a script named "start".
2024/01/21 08:34:21	stdout	$ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] [--require #0]  ...
2024/01/21 08:34:21	stdout
2024/01/21 08:34:21	stdout	Usage Error: Couldn't find a script named "start".

I have recreated the container again from "contanier manager in my synology" and it started fine, the problem is now solved. thank you


How to set the text characters shadow?

I can find the view shadow ,but can't find the text shadow

This is currently not supported.


add design.md

In contribute.md, the design.md is lost.

So i just find the removed design.md, and add it into ./docs/en/.

The design.md is deleted deliberately, I think you can refer to https://kubevela.io/#/en/concepts to fix #1194

ok, got it. May i ask why the design.md was deleted?

@hahchenchen  We have merged the design doc into the website docs.


Build issue for windows crate bindings

I am not able to build the bindings needed for my app using the 0.11 version of the windows crate.  I have built a minimal repro at: https://github.com/galenb-msft/minimal_repro.git
Doing a cargo build in this repo should reproduce the error.

@galenb-msft I have transferred the issue.
In future, please use https://github.com/microsoft/windows-rs for issues specific to the Windows crate and https://github.com/microsoft/win32metadata/ for issues specific to Win32 metadata.

When I build this repro I get the following error:
C:\git\minimal_repro>cargo build
   Compiling proc-macro2 v1.0.27
   Compiling unicode-xid v0.2.2
   Compiling syn v1.0.73
   Compiling windows_gen v0.11.0
   Compiling const-sha1 v0.2.0
   Compiling quote v1.0.9
   Compiling windows_macros v0.11.0
   Compiling windows v0.11.0
   Compiling windows_bindings v0.1.0 (C:\git\minimal_repro\lib\deployment\bindings)
   Compiling minimal_repro v1.0.0 (C:\git\minimal_repro\lib\deployment)
error: couldn't read lib\deployment\minimal_repro.rs: The system cannot find the file specified. (os error 2)

error: aborting due to previous error

error: could not compile `minimal_repro`

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed

This is unrelated to the Windows crate. It appears you have a configuration issue. Check your toml files. For more general Rust help, you may want to try https://stackoverflow.com/

After seeing that you could not repro what always repro'd for me to the only possibility of which I could think -- my compiler is out-of-date.  I updated my compiler and the issue went away.  Thanks for your help!


Can't import ip addresses as terraform resources

I created a fly.io app with the flyctl launch command, and it generated an app with a shared ipv4 ip address and an ipv6 address.
leejjon@leejjon-XPS:~/projects/node-sqlite-fly-tutorial/steps/02-docker$ flyctl apps list
NAME                                    OWNER           STATUS          PLATFORM        LATEST DEPLOY
fly-builder-quiet-snow-9145             personal        suspended       machines
leejjon-node-sqlite-fly-tutorial        personal        deployed        machines        2023-10-07T09:26:45Z

leejjon@leejjon-XPS-:~/projects/node-sqlite-fly-tutorial/steps/02-docker$ flyctl ip list
VERSION IP                      TYPE            REGION  CREATED AT
v6      2a09:8280:1::2d:7e61    public          global  2023-10-01T21:18:25Z
v4      <IP_ADDRESS>          public (shared)

I created a main.tf file that has definitions for the app and two ip addresses:
terraform {
  required_providers {
    fly = {
      source = "fly-apps/fly"
      version = "0.0.20"
    }
  }
}

provider "fly" {
  fly_api_token = var.token
  useinternaltunnel    = true
  internaltunnelorg    = "personal"
  internaltunnelregion = "ams"
}

resource "fly_app" "our-fly-app" {
  name = "leejjon-node-sqlite-fly-tutorial" #Replace this with your own app name
  org  = "personal"
}

resource "fly_ip" "ourIpv4" {
  app        = fly_app.our-fly-app.name
  type       = "v4"
  depends_on = [fly_app.our-fly-app]
}

resource "fly_ip" "ourIpv6" {
  app        = fly_app.our-fly-app.name
  type       = "v6"
  depends_on = [fly_app.our-fly-app]
}

I could import the app perfectly fine with the command:
terraform import fly_app.our-fly-app leejjon-node-sqlite-fly-tutorial
Now terraform nicely shows that my app exists.
leejjon@leejjon-XPS:~/projects/node-sqlite-fly-tutorial/steps/02-docker/terraform$ terraform show
# fly_app.our-fly-app:
resource "fly_app" "our-fly-app" {
    appurl = "https://2a09:8280:1::2d:7e61"
    id     = "leejjon-node-sqlite-fly-tutorial"
    name   = "leejjon-node-sqlite-fly-tutorial"
    org    = "personal"
    orgid  = "3KXm0g39B6X2ZT01Nkv4g83lV4hgYYXBp"
}

According to the docs you can do this command:
terraform import fly_ip.exampleIp <app_id>,<ip_address>
It doesn't seem to split the commas correctly:
leejjon@leejjon-XPS:~/projects/node-sqlite-fly-tutorial/steps/02-docker/terraform$ terraform import fly_ip.ourIpv4 "leejjon-node-sqlite-fly-tutorial,<IP_ADDRESS>"

fly_ip.ourIpv4: Importing from ID "leejjon-node-sqlite-fly-tutorial,<IP_ADDRESS>"...
fly_ip.ourIpv4: Import prepared!
  Prepared fly_ip for import
fly_ip.ourIpv4: Refreshing state... [id=leejjon-node-sqlite-fly-tutorial,<IP_ADDRESS>]
╷
│ Error: Could not find App
│
│ app
╵

I also tried it without the quotes.
But even if I leave out the ip address it gives the same error:
leejjon@leejjon-XPS:~/projects/node-sqlite-fly-tutorial/steps/02-docker/terraform$ terraform import fly_ip.ourIpv4 leejjon-node-sqlite-fly-tutorial

fly_ip.ourIpv4: Importing from ID "leejjon-node-sqlite-fly-tutorial"...
fly_ip.ourIpv4: Import prepared!
  Prepared fly_ip for import
fly_ip.ourIpv4: Refreshing state... [id=leejjon-node-sqlite-fly-tutorial]
╷
│ Error: Could not find App
│
│ app
╵

whoops, I just noticed there is a 0.0.23 version, and I'm getting a different error there.


Added https support for trunk serve.

This allows users to serve with https. To enable this, add path to the cert files as below in Trunk.toml. If it failed to read cert files, it will start in http as usual.
[serve]
crt = "./server.crt"
key = "./server.key"

Checklist

[x] Updated CHANGELOG.md describing pertinent changes.
[ ] Updated README.md with pertinent info (may not always apply).
[ ] Updated site content with pertinent info (may not always apply).
[x] Squash down commits to one or two logical commits which clearly describe the work you've done. If you don't, then Dodd will 🤓.

Hi, Is there anyway to try this before it gets merged at all?

Please add an example with HTTPS.

@simbleau Thankyou for reviewing. I made a sample here.
I checked in windows.
run sample as https

Create key and crt pair with openssl(without encrypt).
openssl req -x509 -new -keyout server.key -out server.crt -days 365
Place server.key and server.crt under the yew folder.
Add localhost as another domain in hosts file to prevents browsers from operating in trust mode.(Secure context WebAPI like showOpenFilePicker works with HTTP localhost,  when usually should only work with HTTPS.)
<IP_ADDRESS> server.my

windows

C:\Windows\System32\drivers\etc\hosts

linux

/etc/hosts

Run yew with merged trunk.
trunk serve
Access https://server.my:8080 with browser.
If it is operating successfully, opening file picker should work(this won't work when accessing http://server.my:8080 running with trunk before merge).

@peteringram0 Sorry for the late reply.
You can clone original trunk, create branch and easly build it.
git fetch origin pull/458/head:PR-458
git checkout PR-458
cargo build
After build, trunk binary will be generated at target/target/debug/trunk.exe(I checked in windows).
Use target/target/debug/trunk.exe with project you are using trunk with.

Is it possible to assist here?

Note that this development version can also be installed using:
cargo install --git https://github.com/murosuke/trunk --branch develop trunk

Note: I can not close the dev-server using Ctrl-C. Is the signal correctly handled? I an Using an M1 mac, Trunk config contains an active proxy section.
Also worth noting: I generated a self-signed certificate using a custom ca. That ca is part of my machines keychain. Chrome accepts the generated certificate perfectly. But: I had to set insecure = true in Trunk.tomls [[proxy]] section for communicating with my backend service (axum running in https locally using the came cert). Is Trunk using the systems CA store properly? I had not anticipated that this option would become necessary..

Also worth noting: I generated a self-signed certificate using a custom ca. That ca is part of my machines keychain. Chrome accepts the generated certificate perfectly. But: I had to set insecure = true in Trunk.tomls [[proxy]] section for communicating with my backend service

Self signed certificates are officially invalid, by definition, and need insecure acceptance, for sure.

I do believe this was part of trunk-ng. With the merge of trunk-ng into trunk as part of PR #623, that should be part of the next trunk release. If that's not the case, please let us know.


Tensorflow not Compatible with Python 3.7

Please go to Stack Overflow for help and support:
https://stackoverflow.com/questions/tagged/tensorflow
If you open a GitHub issue, here is our policy:

It must be a bug, a feature request, or a significant problem with documentation (for small docs fixes please send a PR instead).
The form below must be filled out.
It shouldn't be a TensorBoard issue. Those go here.

Here's why we have that policy: TensorFlow developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): N/A
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): OS 10.13.4
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): source (whole package)
TensorFlow version (use command below): 1.10.1
Python version: 3.7
Bazel version (if compiling from source): N/A
GCC/Compiler version (if compiling from source):

Apple LLVM version 9.1.0 (clang-9<IP_ADDRESS>)
Target: x86_64-apple-darwin17.5.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin

CUDA/cuDNN version: N/A

GPU model and memory: N/A

Exact command to reproduce:

run the following below:
import numpy as np
import tensorflow as tf
import tensorflow
from tensorflow import keras
from keras.models import Sequential
from keras.layers import Embedding
model = Sequential()
model.add(Embedding(5, 2, input_length=5))
You can collect some of this information using our environment capture script:
https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh
You can obtain the TensorFlow version with:
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"

Describe the problem
Describe the problem clearly here. Be sure to convey here why it's a bug in TensorFlow or a feature request.
So it appears Tensorflow doesn't play nicely with Python 3.7 - there is a source issue when I run ANY tensorflow or keras command using python 3.7 (but runs perfectly fine with earlier versions of python - reverted back and everything ran perfectly fine).
Here are all the relevant files with environment (it actually errors out when running in p3.7)
files using 3.7:
broken-old-tf_env.txt
broken-tf_env.txt
normal env:
old-tf_env.txt
tf_env.txt
Source code / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem.
Here is the trace error message - this exact message occurs when attempting to run ANY keras or tf command using python 3.7:
(for test case, honestly even the most simple lines will cause the break - try;
embeddings = tf.Variable(tf.random_uniform([vocabulary_size, embedding_size], -1.0, 1.0))
Or for keras:
model = Sequential()
model.add(Embedding(10000, 50, input_length=3334))
Error message:
UnboundLocalError                         Traceback (most recent call last)
 in ()
6 embedding_size = 100
7
----> 8 embeddings = tf.Variable(tf.random_uniform([vocabulary_size, embedding_size], -1.0, 1.0))
9 nce_weights = tf.Variable(tf.truncated_normal([vocabulary_size, embedding_size], stddev=1.0 / math.sqrt(embedding_size)))
10 nce_biases = tf.Variable(tf.zeros([vocabulary_size]))
~/.local/share/virtualenvs/embedded-feature-extraction-o8pNKOHv/lib/python3.7/site-packages/tensorflow/python/ops/random_ops.py in random_uniform(shape, minval, maxval, dtype, seed, name)
233   with ops.name_scope(name, "random_uniform", [shape, minval, maxval]) as name:
234     shape = _ShapeTensor(shape)
--> 235     minval = ops.convert_to_tensor(minval, dtype=dtype, name="min")
236     maxval = ops.convert_to_tensor(maxval, dtype=dtype, name="max")
237     seed1, seed2 = random_seed.get_seed(seed)
~/.local/share/virtualenvs/embedded-feature-extraction-o8pNKOHv/lib/python3.7/site-packages/tensorflow/python/framework/ops.py in convert_to_tensor(value, dtype, name, preferred_dtype)
996       name=name,
997       preferred_dtype=preferred_dtype,
--> 998       as_ref=False)
999
1000
~/.local/share/virtualenvs/embedded-feature-extraction-o8pNKOHv/lib/python3.7/site-packages/tensorflow/python/framework/ops.py in internal_convert_to_tensor(value, dtype, name, as_ref, preferred_dtype, ctx)
1092
1093     if ret is None:
-> 1094       ret = conversion_func(value, dtype=dtype, name=name, as_ref=as_ref)
1095
1096     if ret is NotImplemented:
~/.local/share/virtualenvs/embedded-feature-extraction-o8pNKOHv/lib/python3.7/site-packages/tensorflow/python/framework/constant_op.py in _constant_tensor_conversion_function(v, dtype, name, as_ref)
215                                          as_ref=False):
216   _ = as_ref
--> 217   return constant(v, dtype=dtype, name=name)
218
219
~/.local/share/virtualenvs/embedded-feature-extraction-o8pNKOHv/lib/python3.7/site-packages/tensorflow/python/framework/constant_op.py in constant(value, dtype, shape, name, verify_shape)
194   tensor_value.tensor.CopyFrom(
195       tensor_util.make_tensor_proto(
--> 196           value, dtype=dtype, shape=shape, verify_shape=verify_shape))
197   dtype_value = attr_value_pb2.AttrValue(type=tensor_value.tensor.dtype)
198   const_tensor = g.create_op(
~/.local/share/virtualenvs/embedded-feature-extraction-o8pNKOHv/lib/python3.7/site-packages/tensorflow/python/framework/tensor_util.py in make_tensor_proto(values, dtype, shape, verify_shape)
534     raise TypeError(
535         "Element type not supported in TensorProto: %s" % numpy_dtype.name)
--> 536   append_fn(tensor_proto, proto_values)
537
538   return tensor_proto
tensorflow/python/framework/fast_tensor_util.pyx in tensorflow.python.framework.fast_tensor_util.AppendFloat32ArrayToTensorProto()
~/.local/share/virtualenvs/embedded-feature-extraction-o8pNKOHv/lib/python3.7/site-packages/google/protobuf/internal/containers.py in append(failed resolving arguments)
249   def append(self, value):
250     """Appends an item to the list. Similar to list.append()."""
--> 251     self._values.append(self._type_checker.CheckValue(value))
252     if not self._message_listener.dirty:
253       self._message_listener.Modified()
UnboundLocalError: local variable 'self' referenced before assignment

@ivaylogb  -  Hi, currently Tensorflow tested build configurations with Python are 2.7, 3.3-3.6. We do not say that Tensorflow is not compatible with Python 3.7 but the above python versions are the tested ones. Thank you !

Closing this issue. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


Is it possible somehow to send LIMIT and OFFSET as parameters (not using paging) ?

Hi @c-martinez
I would like to be able to specify the LIMIT and OFFSET of the SPARQL inside the query, not automatically via the paging option, see e.g., : https://grlc.io/api-git/ILIAD-ocean-twin/api/#/test/get_Observations_test  (not working)
Is this possible somehow?
thanks

Hi @rapw3k,
Sorry for the delay in replying to your issue. I've had a quick look, and it appears it is not possible to do this. Basically, because having something like LIMIT ?top is invalid for SPARQL (limit should not be a SPARQL variable). Of course this would not be a problem once grlc rewrites ?_top to be a value, but because of the order in which grlc replaces variables, it runs into an issue.
@albertmeronyo  -- perhaps we should have another look at the query re-writing engine? This seems to be causing a couple of issues.

In principle I think this should be possible indeed. The real question here is on what time frame we could implement this (I know that both @albertmeronyo and I are a bit tied up with other work, but would welcome pull requests implementing these changes)

Haven't tested this, but I believe this should be possible since v1.3.9. I'm closing this issue, but please re-open it if it does not work.


Records missing from Sphinx results after updating

Hi all, having a issue that I haven't managed to make sense of for the last few hours - where records are missing from search results once they have been updated. I've been able to replicate it on a fresh Rails app, using the latest gems. Have also replicated this with a Rails 4 app. Here's the details:
thinking-sphinx - 3.1.3
ts-datetime-delta - 2.0.1
Rails - 3.2.21

The Animal Model:
# app/models/animal.rb
class Animal < ActiveRecord::Base
  attr_accessible :name
end

The Animal Index:
# app/indices/animal_index.rb
ThinkingSphinx::Index.define(:animal,
     with: :active_record,
          delta: ThinkingSphinx::Deltas::DatetimeDelta,
          delta_options: { threshold: 1.minute }
     ) do
     indexes name
     indexes id
end

After running rake ts:rebuild - I can Animal.search(1) (or any other ID) and results return fine.
But, when I update any of the records, from that point, they fail to return till I re-index
Here's an example from console:
Loading development environment (Rails 3.2.21)
1.9.3-p551 :001 > Animal.search 1
 => [#<Animal id: 1, name: "Cat", created_at: nil, updated_at: "2015-03-01 19:48:32">]
1.9.3-p551 :002 > Animal.find(1).update_attribute :name, 'Dog'
 => true
1.9.3-p551 :003 > Animal.search 1
 => []

In this example, I'd expect to still be able to search for the record by ID, even if the name had been changed. Are my expectations wrong or is there an issue here?
(By querying Sphinx by connecting via mysql, mysql -h <IP_ADDRESS> -uroot --port 9306 - I'm seeing the animal_core contain all records, and the animal_delta contain no records - which I'd expect as they have all been updated outside of the delta threshold that I have set. After making a change to one of the records, as shown in the example above - sphinx_deleted is showing as 1 for the record, and animal_delta remains empty. Should I be expecting to see the record there?)
Hoping you can help here!

With DateTime deltas, you still need a rake task to be run regularly (as often as your threshold) - that task is rake ts:in:delta.
If you want more immediate updates, then a queue-backed delta (Sidekiq, Resque, Delayed Job) is worth looking into, or real-time indices which avoid the need for deltas completely.

Thanks for the response Pat. I understand the need to delta index - the issue I'm seeing is that the second a record is updated, it no longer appears in search till the next time I index.
For example, say I have run a delta threshold of 30 minutes, and run a delta index every 5 minutes.
If I update a record, then it immediately disappears from the search results, till I next index.
This means, even if the delta indexing occurred every minute, it would still mean records are constantly disappearing from search results, for up to a minute at a time. Importantly, it only seems to be an issue for items that were updated at a time in the past, outside of the delta threshold.
Here's what sequence I'm seeing, using the same example of a 30minute delta threshold, with delta indexing occurring every 5 minutes:

I have a record that was updated 24 hours ago
I update this record - it immediately stops appearing in search results
At the time of the next delta index, the item reappears in search results
Now, as the records updated_at is now within its 30 minute threshold, it seems to now exist in the delta index, and thus further updates to the record do not cause it to drop out of search.

From what I'm seeing, it seems as though an item which was last updated 24 hours ago - does not appear within the delta index, and so when it gets updated - it's set as sphinx_deleted = 1 in core index. So when a search takes place, it is filtered out by Thinking Sphinx, as its marked as deleted. The difference is, once it's delta indexed - then it now also lives in the delta index (because it fell within the delta threshold), and so further updates will not cause it to drop out of search - that is, until the threshold time passes and it's no longer in the delta index and so the issue returns.
Should I not be expecting to be able to find a record by it's ID, even if it's been updated before the next delta index? If the record had it's name attribute changed for example, I understand that it'd need to be indexed for me to now search by its new name. But id, or other attributes that have not changed, should surely still yield the updated item in its result?
This issue appears to be new, as of Thinking Sphinx v3, as I believe I was not experiencing this on v2. Hope that clarifies the issue and thanks again for your time.

Ah, thanks for your patient understanding and detail James - I misunderstood the problem.
I've just pushed a fix for this - if you can give the master branch a spin and confirm it now works well for you, then I'll get a new gem release out.

That appears to work a treat! You rock Pat - thank you for being so prompt.
Looking forward to seeing it published =)

2.0.2 is now released :)

Thank you!


Add Section about Timeouts and Logging to docs

Waiting for #103 and #104

@jakubno added js example

Mergin so I can update the CodeGroupAutoload 🙏 🙏 🙏
Let's iterate on these in main


"Annotations" not a parameter

- What I did
Tried to create a service with a name using the API. The json struct had to be altered like the actual example:
"Name": "myname"

instead of
"Annotations": {
  "Name": "myname"
}

- How I did it
Posted the relevant json to /services/create
- How to verify it
Post to /services/create using the two forms and see that using "Annotations" will not work.
- Description for the changelog
The json struct when creating a service should not have the parameter "Annotations".
Signed-off-by: Eivin Giske Skaaren<EMAIL_ADDRESS>

Added some more fixes I found when working with /services

LGTM, thanks!
ping @vdemeester ptal

LGTM :cat:


Seismic Slam - Rumble Needs Update

The current rune for Seismic Slam - Rumble reads as follows:
"Expend all remaining Fury to cause the ground to shudder after the initial strike, damaging enemies in the area for 15% weapon damage for every point of Fury expended as Physical over 2 seconds."
The rune that is on the planner is the old rune.

You mean the tooltip text is outdated? I think the actual skill works correctly, as it has the Fury slider bar. I must've forgotten to update the tooltips (they're automatically generated so I don't usually look at them), fixing it now.


[core] Limit max parameter count to 255

Hey, I've noticed a huge method with 65k parameters (probably obfuscation?). Is that possible to prevent such cases?
Class p001a.p002a.p003a.C4687alockin (a.a.a.alockin)
public class C4687alockin {
    public static java.lang.String aa(java.lang.String str, java.lang.String str2, ...,  java.lang.String str65533) {
       return;
    }

APK: https://www.apkmonk.com/app/com.percent.royaldice/

LOL a really nice app.
I assume your question is just because Jadx requires a lot of time to load and display the class that contains this method?

@jpstotz
Yeah, and also because my AST parser crashes with OutOfMemoryError

@bagipro in theory it is possible to call such method using invoke-***/range instruction, but java spec limits method args count to 255. So in general case, we can replace these args with object array arg (Object[]). Also depending on the specific case we can remove unused args, or remove the whole method if it is empty.
I will try to implement a general solution.
And thanks for the sample :+1:

@skylot
Hey! Can you please look at this one? This issue occurs sometimes and ruins my codes :D

@bagipro can you share one more sample? Because in this case method don't used, so I just remove it. I wonder how will look an invoke of such method :)

@skylot
Sorry for the long response. It appeared that all affected APKs were the same. If I notice this issue, I will let you know.
Thanks for the fix!


Preferences uses non-Retina icon for Advanced tab

The Preferences panel uses a non-Retina icon for the Advanced tab. MacOS has a standard image for this. It looks like MacVim attempts to use this standard image, but fails and falls back to a custom non-Retina image included in the project.
I created a pull request that uses the macOS standard Advanced icon: https://github.com/macvim-dev/macvim/pull/528

merged, thanks.


Connect wq variable to POI

Connect POI to beach ID (s)

join POI polys with EPA RAD beach lines (that have the ID's we need)

Connect beach ID(s) to BEACON data
Deal with merging multiple wq data variables for beach lines that were combined into one POI

I put the data file in our shared data folder called "resultphyschem" along with the zip file that it came from. The GIS data to connect them to the beach POI's from Airsage is also in the data folder. I suggest a spatial join using the lat/lon of the WQP data and contains to start and see if that works. Nearest would probably work fine too.

Started a Python script to do this; still trying to understand these data better.

I just did this manually with a nearest join (max distance 500m) between the beacon data points and the POI shapefile in QGIS and then summarized the beacon data by POI by year. Script and data are in the folders now.

Now we need to run Erin's code through the rest of the process with her new WQ POI connect result


Error while cloning into mucache

Something went wrong while cloning, please check the invalid path.
Cloning into 'mucache'...
remote: Enumerating objects: 450, done.
remote: Counting objects: 100% (24/24), done.
remote: Compressing objects: 100% (15/15), done.
remote: Total 450 (delta 7), reused 23 (delta 6), pack-reused 426
Receiving objects: 100% (450/450), 27.75 MiB | 3.92 MiB/s, done.
Resolving deltas: 100% (83/83), done.
error: invalid path 'experiments/boutique/data/currency_conversion.json:Zone.Identifier'
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

It seems that it panics because Windows doesn’t support colons in the filename. As I don't have a Windows PC, I can't test it myself. Could you try downloading the repo zip directly?

Maybe the latest commit (that removes this and other such files) fixes the issue for you @deerlove-lxq ?

The issue is fixed! Thanks for solving my problem!
By the way, could you please share the paper's ppt for NSDI '24?


default interface/port

The applications listens by default on <IP_ADDRESS>. Is there a way to change it to <IP_ADDRESS>? I have the app installed on a remote VPS and i would like to be able to access through the internet.
Thanks a lot and sorry if this has been already referenced.

Hi @morxploit , thanks for trying Dojo out! For production use, I would suggest proxying Dojo through Nginx or better yet Nginx + Gunicorn. If you're still just exploring / playing with Dojo and aren't transmitting sensitive data, you can run Dojo on all interfaces using the developer server by executing:
python manage.py runserver <IP_ADDRESS>:80

Awesome, thanks for the quick answer @devGregA


Mark hodate value check confirmed

We mark all soft validations as confirmed upon import, this one was missed

Have you done a check that no other soft vals were misseed too?

@natdeanlewissoftwire very good point, there were a few, added them in now. Lettings looks correct. Thanks!


Update to pydantic 2.0

The recent pydantic 2.0 release made some backward-incompatible changes. I pinned it back to <2 for now. https://github.com/bluesky/tiled/pull/489/commits/2b0c80d33d834406f4220bd39b004c71c8397740

Closed by #669


drivers: ethernet: xlnx_gem: fixes for UltraScale operation

Fixes the issue of the transmit logic locking up whenever the driver is running on actual UltraScale+ hardware, where an additional set of RX/TX buffer descriptors can be specified via an additional set of RXQ base / TXQ base registers, whose primary purpose it seems to be to make DMA access 64-bit compatible (a high address word register also exists for each of the additional RXQ base / TXQ base registers). However, if at least the alternate TXQ base register is left in its power-on state and buffer DMA initialization is only performed identically to how it's being performed on the Zynq-7000, the GEM's TX path locks up when attempting to transmit a packet. Further info on the symptoms of this issue can now be found in the driver's buffer configuration function.
This fix solves the issue in the most simple way possible, by setting up an extra DMA area for the 2nd set of RXQ base / TXQ base registers. This DMA area effectively only consists of a single TX buffer descriptor, which will never indicate pending TX data to the controller, also, its control word contains the 'wrap' bit so that the 2nd TXQ base register will never point to anything else than this dummy TX buffer descriptor. However, placing this single descriptor in a new type of DMA area struct retains the option to expand the capabilities of the 2nd DMA area in case full 64-bit support might eventually be introduced for the UltraScale's A53 cores.
This commit also fixes the UltraScale+-specific issue hinted at in the dt-bindings commit: the driver performs a validity check in the form of an __ASSERT macro regarding the MDC clock divider. This check has so far been specific to whether the current system is based on the Zynq-7000 or the UltraScale+, with different maximum dividers for both SoC families. According to the most recent documentation, treating the two SoC families differently is not required when it comes to this particular validity check.
Another minor issue fixed is that https://github.com/zephyrproject-rtos/zephyr/pull/41918 apparently didn't automatically fix device config/data usage if the respective function was #ifdef'd. Therefore, compilation of eth_xlnx_gem_stats failed whenenver CONFIG_NET_STATISTICS_ETHERNET was set.
As a side effect of refactoring, register bits which so far were specified as full 32-bit hex words, now use the BIT(x) notation.
Also, status register clear write operations now use ~0 instead of 0xFFFFFFFF or 0 instead of 0x00000000 as value parameter.

Fixes the issue of the transmit logic locking up whenever the driver is running on actual UltraScale+ hardware, where an additional set of RX/TX buffer descriptors can be specified via an additional set of RXQ base / TXQ base registers [...]

Would you mind which issue you are referring to?  Is it 52019?

Hi @ibirnbaum,
Thank you for your detailed explanation.  Now I see what's going on.  I was gonna test it with my Zynq-7000 but I'm sure I can't.

If the UltraScale revision is detected, the 2nd TX queue is set up as a full-fledged TX queue, including making use of the corresponding 2nd set of interrupt enable/disable/status registers and handling them in the ISR. However, as observed by anyone running into this issue, the RX buffer descriptor queue is present only once, and is referred to by the original RXQBASE register which can be found in both the Zynq and the UltraScale revision of the controller.

It seems all the change is squashed into this commit, which doesn't help. :face_exhaling:
On to the commits.
It might help us to maintain the change if the commit "drivers: ethernet: xlnx_gem: fixes for UltraScale operation" is specific to the problem you described.  Would it be too much to ask splitting minor changes out to its own?

@yashi

On to the commits. It might help us to maintain the change if the commit "drivers: ethernet: xlnx_gem: fixes for UltraScale operation" is specific to the problem you described. Would it be too much to ask splitting minor changes out to its own?

Would you prefer those other minor changes as separate commits within this PR, or would you rather prefer a separate PR?

@ibirnbaum
In this PR should be OK.

@ibirnbaum
In this PR should be OK.

Hi @yashi, I've split up what was originally the single driver-related commit into individual ones for each topic addressed.

I'd say that "drivers: ethernet: xlnx_gem: generic refactoring" is not refactoring but non-functional cosmetic changes. Refactoring, at least to me, is more like structural change in the code.
BTW, I assume that the doc changes aren't relate to any patch in this series, right? If it does, it should move to the corresponding patch. But I'm assuming that you have added missing doc from the past changes.

I'll re-word the commit to avoid confusion.
At least the comment in the file's header regarding the DMA area placement should have been changed with #42036, but I missed that one. The added register bits in the header file are those where I wasn't sure initially if Zynq and UltraScale both have them. But as I'm now sure that both revisions of the controller have them, I've added them along the way, although they aren't used for anything yet. The comments in the "DMA fix for UltraScale+" commit all refer to the matter at hand.

@ibirnbaum, we don't push merge commit in a PR.  If you need, just rebase it.  Maintainers will merge it for you.

Rebase gone wrong as usual.


Add flag to toggle transaction & gas fees

Issue To Be Solved
Fees are optional in FVM, but this option isn't exposed to users of the emulator. This would be useful for developers who want to experiment with the emulator without worrying about fees.
Suggest A Solution
flow emulator start --disable-fees

or
flow emulator start --disable-tx-fees --disable-account-fees --disable-storage-fees

This has been implemented with --transaction-fees flag


Ironically, monosyllabic is not a recognized word

As you can see below, despite the word "monosyllabic" being used in the video, on the site itself, and in most dictionaries I can find, the translator does not recognize it as a word.

Came here to report this. +1 to "but why though?"


Create SQL Database for The Project

For this project, I'll use MySQL for the database to store the project's data. So I need to create the database first before writing any query inside the codebase
To-Do's

[x] Create MySQL Database
[x] Export the database into SQL file

Closed with 63dde9ab660d66a41f529803b60ab731cf3009a7


How to reset zoom?

Here's my reset function:
function reset() {
  var t = d3.zoomIdentity.translate(0,0).scale(1)
  chart_svg.call(zoomListener.transform, t)
}

But the resulting transform property applied to my chart is translate (-xxxxx,-xxx) scale (1).

That looks approximately correct, although the t you have defined is equivalent to d3.zoomIdentity, so you can more simply say:
selection.call(zoom.transform, d3.zoomIdentity);

As for why you are seeing a translate applied, I have no idea based on the snippet you posted. (What is zoomListener, for instance?) The only way I can investigate this issue is if you post a link to a running example, ideally on bl.ocks.org, that demonstrates the problem.

Hello, thanks for the quick response. Here is the running sample I have http://run.plnkr.co/plunks/hjiMeumJzL10TmWKkijV/

The problem is your code here:
if (!d3.event.transform.x) d3.event.transform.x = prev_zoom_x;
else prev_zoom_x = d3.event.transform.x;
if (!d3.event.transform.y) d3.event.transform.y = prev_zoom_y;
else prev_zoom_y = d3.event.transform.y;

I’m not sure why you are doing this, but when you reset to the identity transform, transform.x and transform.y will be zero, so you’ll use prev_zoom_x and prev_zoom_y rather than [0,0].

Please use Stack Overflow tag d3.js or the d3-js Google group to ask for further help debugging your code. If you are able to isolate an issue with D3 then I will investigate further, but I often don’t have time to debug general usage of D3. Thanks for your understanding.

Thanks a lot man.

does any one have reset function for d3 v2 zoom?


Unable to Load GuardOutput.tmTheme

Whenever I install or remove this package from ST3, I get the following error in a pop-up alert:

Error loading colour scheme Packages/Guard/GuardOutput.tmTheme: Unable to open Packages/Guard/GuardOutput.tmTheme

If you look closely you can see that the path to the theme is hardcoded to Packages/Guard/GuardOutput.tmTheme
Make sure the name of the folder under Packages/ is Guard, either by installing (copying the extracted github-zip to the Packages-Folder)  manually or fixing the path after installing via package manager

Yes, since I am using Package Manger, the plugin is in Installed Packages, not Packages.


ui: fix create network access in deploy vm wizard

Description
Fixes #9115
Types of changes

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

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

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

Screenshots (if appropriate):
For account with createNetwork access,

For account without createNetwork access,

How Has This Been Tested?

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

@blueorangutan ui

@weizhouapache a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: https://qa.cloudstack.cloud/simulator/pr/9117 (QA-JID-355)

tested in qa:


Replace single quotations with double quotations in code block in website

On the last two code blocks in the "How to Use" section on the website, replace the single quotations with double quotations. For example, change <a href='#' to <a href="#". This issue causes a bug in copying the code.

Hello. Hope you are doing fine. :)
I just happened to come across this issue. Can I work on it?

Hi @AgyeyaMishra go ahead!

Hey, can I work on this issue ?


FNF Start Menu Logo Y Axis issue (it is annoying as fuck)

Describe your bug here.
So, I changed the start menu logo on the engine ofc, and when I change the Y-Axis, It starts there, than it goes to the default offset.
--------Video for more context----------
https://github.com/JordanSantiagoYT/FNF-PsychEngine-NoBotplayLag/assets/145304742/2b922a27-40a0-4b27-a243-b377be11747d
Command Prompt/Terminal logs (if existing)
None
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
Yes, Start Menu Logo
If you use 1.12.0 or earlier, did you have Optimized Chart Loading turned on?
None

Fixed in https://github.com/JordanSantiagoYT/FNF-PsychEngine-NoBotplayLag/commit/4a95aac1a2d3b93d32e61846ee67b3deb7c48f9c!


Fixed Typo in README.md

Description of the changes:

Fixed Typo in README.md

How changes were validated:

No Validation

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: iamrajiv sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for your interest in the repo. Please avoid PR's that are purely formatting/typo changes to code which has not been modified otherwise. Also, the suggested edits in this PR are not correcting typos (the originals are all correct).

@grochocki sorry for the inconvenience and thanks for the guidance


change faulty script tags to ts

Description
Reason for this PR

Some script tags were not typescript, which is why components did not show up in code coverage

Changes in this PR

add missing lang ts tags and fix imports accordingly

Type of change (remove all that don't apply)

[X] Refactoring

Checklist: (remove all that don't apply)

[X] I have performed a self-review of my own code
[X] My changes generate no new linting warnings or console warnings

They actually still do not show up on the coverage report, as they do not contain any code.
Vue-router links are not instrumentalized by istanbul yet, it seems.


chore(sdk): Use ruff as the formatter

The formatting-related configuration file updates are:

.pre-commit-config.yaml
pyproject.toml

There are additional changes in:

.circleci/config.yml -- removed formatting checks from code-check and also disabled mypy because we don't pass it (not sure how it was working before)
.github/workflows/check-mocks-synced-with-yea-wandb.yml -- deleted because it only affects old unit tests, and I didn't want to update a whole other repository first...
tox.ini -- deleted some environments that aren't useful anymore
Makefile -- deleted references to deleted tox environments
tools/generate-tool.py -- updated to use ruff instead of black

Everything else is modifications by ruff format .

@timoffex what are we going to do with mypy? i think we should have this check.
should we do it in a follow up? i know that it works sometimes, since it fails files, could be that it didn't work when these files were merged or something, i don't think we should remove it completely

@timoffex what are we going to do with mypy? i think we should have this check. should we do it in a follow up? i know that it works sometimes, since it fails files, could be that it didn't work when these files were merged or something, i don't think we should remove it completely

I created a tracking issue to add it back: https://wandb.atlassian.net/browse/WB-18325
Realistically we'll just have it ignore a few files but run on everything else, and then gradually fix the files and remove the exceptions.


Changed ROOT_URL env to use HTTPS

Most OAUTH providers require an HTTPS URL for a callback.  The default Meteor OAUTH client uses the ROOL_URL to build the callback URL.

Thanks for the PR, looks good.


[update] Use context to define base path

It's a bit of a small thing, but I wanted to get additional thoughts on it. This PR sets webpack to use the context property to define the base path for entry points.
http://webpack.github.io/docs/configuration.html#context
It's arbitrary, so no worries on skipping this one.

that is way nicer. Thanks!

Yeah, I find necessary in some cases.


How to dump all databases

we can dump all the mysql databases using below CLI command:
mysqldump -u [username] –p[password] –all-database > [dump_file.sql]
But, how can we dump all databases using nodejs?

check the readme
https://github.com/bradzacher/mysqldump#usage


Cosmos EF Core component ignore emulator certificate

When using AddAzureCosmosDB the emulator certificate can be ignored as implemented with #1668
I try to use the EF Core version AddCosmosDbContext. With this it looks like this option to ignore the emulator certificate is not available.

cc @JamesNK

@JamesNK it looks like it doesn't use the right connection string - I'm getting errors.

That change is for preview 4. It isn't publicly released.
Are you using preview 3 or a nightly build?

Preview 3

@christiannagel I am getting the same. The only workaround I have found is when setting up my DB context is to do as the documentation says as so:
protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
{
    optionsBuilder.UseCosmos("AccountEndpoint = https://localhost:8081/;AccountKey=C2y6yDjf5/R+ob0N8A7Cgv30VRDJIWEHLM+4QDU5DE2nQ9nDuVTqobD4b8mGGyPMbIZnqyMsEcaGQy67XIw/Jw==", "cosmos",
        x => {
            x.HttpClientFactory(() => new HttpClient(new HttpClientHandler()
            {
                ServerCertificateCustomValidationCallback = HttpClientHandler.DangerousAcceptAnyServerCertificateValidator
            }));
            x.ConnectionMode(Microsoft.Azure.Cosmos.ConnectionMode.Gateway);
        });
}

Doing the above still gives me SSL errors, so in my Web project for my Aspire app I have had to:

ServicePointManager.ServerCertificateValidationCallback += (sender, certificate, chain, sslPolicyErrors) => true;

Obviously this is not ideal, but for testing it does allow me to at least make a connection to the Cosmos Emulator.

@JamesNK I missed updating one of the packages with this project. The IgnoreEmulatorCertificate option indeed is available with preview 3. However, it still throws with the same error.
@JamesLMiller - thanks for the workaround.
I'm not changing the DbContext as I'm usingt a NuGet package that's also used with Cosmos running in Azure: https://www.nuget.org/packages/CNinnovation.Codebreaker.Cosmos/, but managed to use your workaround with the DI container configuration ignoring the Cosmos component in the debug case:
#if DEBUG
            builder.Services.AddDbContext<IGamesRepository, GamesCosmosContext>(options =>
            {
                options.UseCosmos("AccountEndpoint = https://localhost:8081/;AccountKey=C2y6yDjf5/R+ob0N8A7Cgv30VRDJIWEHLM+4QDU5DE2nQ9nDuVTqobD4b8mGGyPMbIZnqyMsEcaGQy67XIw/Jw==", "codebreaker",
                 cosmosOptions => {
                    cosmosOptions.HttpClientFactory(() => new HttpClient(new HttpClientHandler()
                    {
                        ServerCertificateCustomValidationCallback = HttpClientHandler.DangerousAcceptAnyServerCertificateValidator
                    }));
                    cosmosOptions.ConnectionMode(ConnectionMode.Gateway);
                });
            });
#else
            builder.AddCosmosDbContext<GamesCosmosContext>("codebreaker", "codebreaker",
                configureDbContextOptions: static options =>
                {
                    options.UseQueryTrackingBehavior(QueryTrackingBehavior.NoTracking);
                });

            builder.Services.AddScoped<IGamesRepository, DataContextProxy<GamesCosmosContext>>();
#endif

Looking forward to updating this with preview 4.

I was using preview 3 and I had the same issue - but I tested the latest code from main using the playground and I didn't have any problems.
Also, seems the package used by preview 3 have the issue https://github.com/Azure/azure-cosmos-dotnet-v3/issues/4315. Now their latest non-preview release (which contains the fix) is the same one already being used by Aspire.
Just posting it here for correlation, since the issue experimented by you @christiannagel may be related to that, although already fixed by Aspire.

I'm going to close this as fixed with preview4. If the problem still exists in the preview4 builds, please re-open.

@JamesNK I missed updating one of the packages with this project. The IgnoreEmulatorCertificate option indeed is available with preview 3. However, it still throws with the same error.
@JamesLMiller - thanks for the workaround.
I'm not changing the DbContext as I'm usingt a NuGet package that's also used with Cosmos running in Azure: https://www.nuget.org/packages/CNinnovation.Codebreaker.Cosmos/, but managed to use your workaround with the DI container configuration ignoring the Cosmos component in the debug case:
#if DEBUG
            builder.Services.AddDbContext<IGamesRepository, GamesCosmosContext>(options =>
            {
                options.UseCosmos("AccountEndpoint = https://localhost:8081/;AccountKey=C2y6yDjf5/R+ob0N8A7Cgv30VRDJIWEHLM+4QDU5DE2nQ9nDuVTqobD4b8mGGyPMbIZnqyMsEcaGQy67XIw/Jw==", "codebreaker",
                 cosmosOptions => {
                    cosmosOptions.HttpClientFactory(() => new HttpClient(new HttpClientHandler()
                    {
                        ServerCertificateCustomValidationCallback = HttpClientHandler.DangerousAcceptAnyServerCertificateValidator
                    }));
                    cosmosOptions.ConnectionMode(ConnectionMode.Gateway);
                });
            });
#else
            builder.AddCosmosDbContext<GamesCosmosContext>("codebreaker", "codebreaker",
                configureDbContextOptions: static options =>
                {
                    options.UseQueryTrackingBehavior(QueryTrackingBehavior.NoTracking);
                });

            builder.Services.AddScoped<IGamesRepository, DataContextProxy<GamesCosmosContext>>();
#endif

Looking forward to updating this with preview 4.

One thing that I noted in some of my testing for my app, is that if I give the emulator time to fully start up (sometimes almost a whole minute) I will not get the SSL errors when connecting. If I don't give it time to connect, and try to use the my database context to call "EnsureCreated" I will still get the SSL issues.

I see similar problems with the cosmos emulator

@davidfowl are you seeing this on the main branch?

@christiannagel for preview 3 you will need to set the ignore flag for the certificate. But you still may see SSL errors. This is due to the time it takes for the emulator to start up. Even if the emulator output is saying it has started all the partitions it can still take some time for it to become responsive to some requests.
Try letting it run for about 40-60 seconds and see whether it starts being responsive. Could you let us know either way on this?

... if you are using preview 4 bits from main you don't need to set the ignore flag because the updated Cosmos client honours a setting on the connection string.

Reopening for now since this is still an active conversation and we just need to verify that it is actually working (if we wait long enough).

I've also seen SSL errors when the emulator is starting up.
However, the problem isn't caused by an invalid certificate. It's caused by the emulator returning a bad response as it starts. Ignoring invalid certificate won't fix it.

I've also seen SSL errors when the emulator is starting up.
However, the problem isn't caused by an invalid certificate. It's caused by the emulator returning a bad response as it starts. Ignoring invalid certificate won't fix it.

When waiting I do not get SSL errors. The other issue that I am noting is that I have no way (that I know of) beyond a GET request to check the status of the emulator. This seems like overkill.  With Aspire, I would assume the startup and connection would be handled when adding these components by my AppHost, and I just "use" them.
I can write retry logic if I have health status information about the emulator, to wait for startup to complete,  but I don't see anything in the docs about that. It is a little cumbersome to have to wait for 60 (sometimes more) seconds, to do local testing on cosmos changes. Its a first world problem I know, but just making a note of it.


Update config files (to "rotate in new ODIS signers") <-- (context from @codyborn on Slack)

This is an example ticket to demo Github Projects (please ignore).

adding a "PM"  label here so I can filter against this while backlog grooming

Closing this ticket, which was a demo for github project.


Hit testing for layouts

We're rendering bounding boxes around each glyph, it should be pretty easy to do hit testing using those.

Simply hit test was implemented https://github.com/kevinbarabash/math-ast/commit/5b52943a0ee9da5f0e4ba31e6e6978a0840390f4, but it treats each glyph as separate hit when in fact we'd like to be able to select a multi-digit number of negative number as a single item.

Selecting multi-digit numbers works now.


[W09H01] Add Comments for Test 2

Mac OS may throw IOException lazily if the directory does not exist. So if you have dealt with IOException on Mac, you still might encounter it. However, this JUnit test will not be executed in Artemis. So if you are sure that you have dealt with IOException, you can ignore this test. (for MacOS)

@BSLK11 I would for now use #203 as a solution. Let me know if #203 is still not a good solution 👍


[Enhancement] Make field non-public and provide accessors if needed.

Search before asking

[X] I had searched in the issues and found no similar issues.

Enhancement Request

located at:
eventmesh-connectors/eventmesh-connector-openfunction/src/main/java/org/apache/eventmesh/connector/openfunction/service/ConsumerService.java
Describe the solution you'd like

Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Hi, can you assign that to me?

@ErogluBaris OK! Welcome to the eventmesh community!

Hii Can i work on this issue..?

@AbhishekPSingh07 Welcome to the eventmesh community, you can start by submitting a pr.

Hi @Alonexc, can you assign it to me?

Hi, I'm new to open source and want to try to solve some simple problems. Can you assign this issue to me? I would appreciate it!


Request support for Cecofry 5500 connected

Log message
Logger: custom_components.tuya_local.config_flow
Source: custom_components/tuya_local/config_flow.py:483
integration: tuya_local (documentation, issues)
First occurred: 9:12:12 PM (4 occurrences)
Last logged: 9:24:13 PM

Device matches None with quality of 0%. DPS: {"updated_at":<PHONE_NUMBER>.1720564, "2": false, "3": "pizza", "5": "standby", "6": 180, "9": 10, "10": 10, "13": false}
Device matches None with quality of 0%. DPS: {"updated_at":<PHONE_NUMBER>.0235984, "2": false, "3": "pizza", "5": "standby", "6": 180, "9": 10, "10": 10, "13": false}
Device matches None with quality of 0%. DPS: {"updated_at":<PHONE_NUMBER>.9008543, "2": false, "3": "pizza", "5": "standby", "6": 180, "9": 10, "10": 10, "13": false}
Device matches None with quality of 0%. DPS: {"updated_at":<PHONE_NUMBER>.5533803, "2": false, "3": "pizza", "5": "standby", "6": 180, "9": 10, "10": 10, "13": false}

DPS information
"model": "Cecofry 5500 Connected",
    "name": "Cecofry 5500 Connected",
    "product_id": "xxwvfk9qrn56r4n6",
    "product_name": "Cecofry 5500 Connected",
    "sub": false,
    "time_zone": "+02:00",
    "update_time":<PHONE_NUMBER>,
    "uuid": "e52be3d9a47e3c6b"
  },
  "success": true,
  "t":<PHONE_NUMBER>125,
  "tid": "ef1169a0670211efb77736033862a1ba"

Product ID
xxwvfk9qrn56r4n6
Product Name
Cecofry 5500 Connected
Information about how the device functions
Airfryer
https://www.amazon.de/dp/B0BQ1QJJPH?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1

I'm not sure where you got the device info that you have included, but it does not contain any dps info. Maybe in the same location you can find more info that lists the dps with their names and numeric ids, as well as range and scale info for numeric ones, and list of possible values for enums such as "pizza" and "standby".

I'm not sure where you got the device info that you have included, but it does not contain any dps info. Maybe in the same location you can find more info that lists the dps with their names and numeric ids, as well as range and scale info for numeric ones, and list of possible values for enums such as "pizza" and "standby".

Oh sorry for my last post.
Here are the information from "query things data model":
{
"result": {
"model": "{"modelId":"000004f7hd","services":[{"actions":[],"code":"","description":"","events":[],"name":"默认服务","properties":[{"abilityId":1,"accessMode":"rw","code":"switch","description":"","extensions":{"iconName":"icon-dp_power2","attribute":"1152"},"name":"开关","typeSpec":{"type":"bool"}},{"abilityId":2,"accessMode":"rw","code":"start","description":"","extensions":{"iconName":"icon-dp_play","attribute":"1152"},"name":"启动","typeSpec":{"type":"bool"}},{"abilityId":3,"accessMode":"rw","code":"mode","description":"可增减枚举值，修改后需到App面板-编辑重新上传图标样式。","extensions":{"iconName":"icon-dp_mode","attribute":"1152"},"name":"烹饪模式","typeSpec":{"type":"enum","range":["pizza","fries","chicken","shrimp","fish","chicken_drumsticks","vegetables","desserts","none"]}},{"abilityId":5,"accessMode":"ro","code":"status","description":"待机 烹饪中 烹饪完成  锅抽出  步骤1完成 步骤2完成...","extensions":{"iconName":"icon-zhuangtai","attribute":"1152","trigger":"direct"},"name":"工作状态","typeSpec":{"type":"enum","range":["standby","cooking","done","door_open","1_done","2_done","3_done","4_done","5_done","6_done","7_done","8_done","9_done","10_done"]}},{"abilityId":6,"accessMode":"rw","code":"cook_temperature","description":"","extensions":{"iconName":"icon-dp_temp","attribute":"1152"},"name":"烹饪温度","typeSpec":{"type":"value","max":200,"min":80,"scale":0,"step":5,"unit":"℃"}},{"abilityId":9,"accessMode":"rw","code":"cook_time","description":"","extensions":{"iconName":"icon-dp_time3","attribute":"1152"},"name":"烹饪时间","typeSpec":{"type":"value","max":60,"min":1,"scale":0,"step":1,"unit":"min"}},{"abilityId":10,"accessMode":"ro","code":"remain_time","description":"","extensions":{"iconName":"icon-dp_time2","attribute":"1152"},"name":"剩余时间","typeSpec":{"type":"value","max":360,"min":0,"scale":0,"step":1,"unit":"min"}},{"abilityId":11,"accessMode":"rw","code":"multistep","description":"01  -- 当前步骤 /第二步 \n\n00  -- 步骤1 \n03   -- dp 点的个数 (时间，模式，温度) cookArgs 的长度\n03  -- dpId\n0004  -- dpValue\n03  -- dpId\n0004  -- dpValue\n03  -- dpId\n0004  -- dpValue\n00 -- 是否执行完成(00：未开始执行的  01：执行已完成  02：执行到一半跳过的)\n00 -- 步骤动作(等待加料(00) 下一步 (01))\n\n0100030300040300040300040000","extensions":{"iconName":"icon-dp_direction","attribute":"1152"},"name":"多步骤执行","typeSpec":{"type":"raw","maxlen":128}},{"abilityId":12,"accessMode":"ro","code":"fault","description":"","extensions":{"iconName":"icon-baojing","scope":"fault","attribute":"1152"},"name":"故障告警","typeSpec":{"type":"bitmap","label":["ntc_fault"],"maxlen":1}},{"abilityId":13,"accessMode":"rw","code":"pause","description":"","extensions":{"iconName":"icon-dp_pause","attribute":"1152"},"name":"暂停/继续","typeSpec":{"type":"bool"}},{"abilityId":22,"accessMode":"rw","code":"cloud_recipe_id","description":"无需云食谱功能则不用选择，根据实际需要选择使用；\n设备收到后回复即可","extensions":{"iconName":"icon-dp_cloud"},"name":"云食谱ID","typeSpec":{"type":"raw","maxlen":128}},{"abilityId":23,"accessMode":"rw","code":"cooking_history_id","description":"根据实际需要选择使用，设备主动上报食谱id，App生成一条烹饪记录","extensions":{"iconName":"icon-dp_cloud"},"name":"烹饪历史ID","typeSpec":{"type":"raw","maxlen":128}},{"abilityId":101,"accessMode":"ro","code":"device_version","description":"","name":"设备版本","typeSpec":{"type":"string","maxlen":255}}]}]}"
},
"success": true,
"t":<PHONE_NUMBER>104,
"tid": "27a07ea4677411ef88b02ac421ecbce6"
}

Under "Device Debugging" I got:
Code	Type	Values switch	Boolean	 "{true,false}" start	Boolean	 "{true,false}" mode	Enum	 {   "range": [     "shrimp",     "fish"   ] } cook_temperature	Integer	 {   "unit": "℃",   "min": 80,   "max": 200,   "scale": 0,   "step": 5 } cook_time	Integer	 {   "unit": "min",   "min": 1,   "max": 60,   "scale": 0,   "step": 1 } multistep	Raw	 {} pause	Boolean	 "{true,false}"

it works now. Thank you very much @make-all
Firstly I got problem with connecting. It showed always "unknown error".
After a while, I reinstall the add-on, connect it over app. And I can see and control everything


Explorer Patcher

Describe the bug
when installing Explorer Patcher, the "right" click on the start button does not generate the menu.  Installed latest version 22621.3880.66.6
To Reproduce
Steps to reproduce the behavior:

Go to 'right click start menu'
Click on 'right click start menu'
Scroll down to '....'
See error

Expected behavior
<does not generate menu
Screenshots

Additional context
Everything else appears to work with Explorer Patcher.

Hey there @Livealoha808
This is the WinUtil Repository. If you have an Issue with this application, I'd suggest making an Issue in the official ExplorerPatcher Repository.
/close

if i install Win11 without using microwin, Explorer Patcher installs fine with no issue.

/reopen
Maybe @CodingWonders knows something about this.

@Livealoha808, can you show the error with Explorer Patcher?

hmm thanks for responding, actually nothing to show..when I "Right" click on the start button, it should bring up the context menu, unfortunately, nothing happens.  No error message.  When i uninstall Explorer Patcher, then "right" click on the start button, brings back the context menu, so i know the file(s), shortcuts are there (appdata\local\microsoft\windows\winx)  all 3 groups 1-3 have the shortcuts...

Could you report the problem on the ExplorerPatcher repository?

Okay, thanks..just thought it had something to do with Microwin, since it does work using the same iso without using microwin.

We (atleast I) do not know the exact issue bc we are not experienced with errorhandling explorerpatcher. Meaning theyr support will be better at identifying the issue. If we know the exact issue and that it is because of microwin we may be able to "fix" it if it is an actual issue.
Explorerpatcher is known for its issues, one week you have some and others it works fine. On some devices it work fine on other not so great.


[stable/stolon] add stolon chart

Initial commit of stolon chart.

/assign @unguiculus

/assign @prydonius

/assign

/ok-to-test

As @unguiculus says, it looks like Stolon can work directly with Kubernetes. If you change the values.yaml to use that by default instead, I think it should pass the CI. Otherwise you'll have to provide additional manifests for the CI to provide it with the additional services. Check this document for additional guidance for the latter: https://github.com/kubernetes/charts/blob/master/test/README.md

@unguiculus @timstoop All issues/requested changes should be fixed.

@unguiculus @timstoop let me know if other changes are needed.

/lgtm


Add zziplib port

To facilitate support of VS2015 in all the different configurations,
a CMake-based build system based on the one found in
https://sourceforge.net/p/zziplib/patches/17/ is used.

Hi @traversaro, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Sweet! Thanks! 👍


Improve messaging around state of junction elements

See original issue on GitLab
In GitLab by [Gitlab user @cs-shadow] on Nov 12, 2019, 20:15
Summary
When you (in most cases, an unsuspecting new user) run bst show on a junction element, BuildStream will report its status as buildable. "buildable" quite literally means that it can be built. However, if you try to bst build it, BuildStream will tell you that junction elements can't be built.
As a BuildStream developer I understand why this happens. Nevertheless it's not obvious to new users. It's also not a great UX.
Steps to reproduce
Find a junction element. Run bst show and bst build on it.
What is the current bug behavior?
BuildStream tells user than an element is "buildable" but refuses to build it.
What is the expected correct behavior?
BuildStream either builds it, or doesn't say it's "buildable" while reporting its status.

In GitLab by [Gitlab user @cs-shadow] on Nov 12, 2019, 20:15
changed the description

In GitLab by [Gitlab user @cs-shadow] on Nov 12, 2019, 20:15
changed the description

In GitLab by [Gitlab user @cs-shadow] on Nov 12, 2019, 20:15
changed the description

In GitLab by [Gitlab user @cs-shadow] on Nov 12, 2019, 20:15
changed the description

In GitLab by [Gitlab user @cs-shadow] on Nov 12, 2019, 20:16
changed the description

In GitLab by [Gitlab user @cs-shadow] on Nov 12, 2019, 20:16
changed the description

In GitLab by [Gitlab user @tpollard] on Dec 10, 2019, 15:40
mentioned in merge request !1764

In GitLab by [Gitlab user @tpollard] on Dec 10, 2019, 15:40
mentioned in merge request !1764

In GitLab by [Gitlab user @tpollard] on Jan 9, 2020, 12:18
closed via merge request !1764

In GitLab by [Gitlab user @tpollard] on Jan 9, 2020, 12:18
closed via merge request !1764

In GitLab by [Gitlab user @tpollard] on Jan 9, 2020, 12:18
mentioned in commit 928d8e6b77daee3eb259d96681f4bce9dc512afd

In GitLab by [Gitlab user @tpollard] on Jan 9, 2020, 12:18
mentioned in commit 928d8e6b77daee3eb259d96681f4bce9dc512afd


Usercentrics Consent Management with Smart Data Protector

Test URLs:

Before:

homepage with video: https://main--adaptto-website--adaptto.hlx.live/2021/
talk with video: https://main--adaptto-website--adaptto.hlx.live/2021/schedule/image-optimization-at-the-edge
google maps: https://main--adaptto-website--adaptto.hlx.live/2023/venue
newsletter: https://main--adaptto-website--adaptto.hlx.live/2021/conference/newsletter
ticket shop: https://main--adaptto-website--adaptto.hlx.live/2023/sign-up/tickets

After:

homepage: https://feature-consent-management--adaptto-website--adaptto.hlx.live/2021/
talk with video: https://feature-consent-management--adaptto-website--adaptto.hlx.live/2021/schedule/image-optimization-at-the-edge
google maps: https://feature-consent-management--adaptto-website--adaptto.hlx.live/2023/venue
newsletter: https://feature-consent-management--adaptto-website--adaptto.hlx.live/2021/conference/newsletter
ticket shop: https://feature-consent-management--adaptto-website--adaptto.hlx.live/2023/sign-up/tickets

Superseded by https://github.com/adaptto/adaptto-website/pull/43


Adding splunk HEC support

I built the container and tested it in our environment and it works well 🙂

Hi @repeatedly could we get this PR merged?

Any update @repeatedly?

Need debian images and please add your name to README's maintainer section:
https://github.com/fluent/fluentd-kubernetes-daemonset#maintainers

@repeatedly done and done

sorry for the late. Merged!

No worries, thanks @repeatedly 🙂

a little more documentation would go a long way here.  ive been scratchin at this for a bit.  i see in -vv mode some contact being made (but not showing up in my indicies), but not sure what else is needed.  not sure what all switches i need to flip on for everything to be zen.  anyway, thx for making the effort to get something out at all :)

@cdaringe it might help to rule out fluentd for now and just test your HEC with curl: http://dev.splunk.com/view/event-collector/SP-CAAAE7F
Then find your message in your Splunk, work out the index etc.

Thanks. I meant to follow up. This plugin was doing great work, but splunk was tossing away the data due to an issue I'm still working out. Thanks for the feedback!


r128gain: 0.9.3 -> 1.0.1

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

cc @FRidh for mutagen update

I still need to note in the commit message that I've switched to fetching r128gain from GitHub so I can run the tests locally with the sandbox disabled.

It's https://github.com/beetbox/mediafile/issues/24. I'm backporting https://github.com/beetbox/mediafile/commit/b3343c4ee08d1251ae5e2344401a2f5892b4e868 to beets so it works with the new mutagen.

Fixed and rebased. mopidy-gmusic is unrelated as it also fails to build on master.
cc @aszlig @domenkozar @pjones for Beets patch

Hmm, I'm unable to replicate that.
$ realpath result
/nix/store/gmfi2f3415k9xjppgn7rly5zzk0xsm2j-cozy-0.6.7

$ nix-store -q --tree result | grep mutagen
+---/nix/store/10bdsywv56bmkrljv3wa65516813qp2s-python3.7-mutagen-1.43.0
|   +---/nix/store/10bdsywv56bmkrljv3wa65516813qp2s-python3.7-mutagen-1.43.0 [...]

This is what I get when I run it on KDE for the first time and import a few files (with duplicated lines removed):
$ result/bin/cozy

** (gst-plugin-scanner:11314): CRITICAL **: 23:37:25.344: Couldn't g_module_open libpython. Reason: /nix/store/g20g00saxyssz0ka1xcmcm31bfq6iq31-python3-3.7.6/lib/python3.7/config-3.7m-x86_64-linux-gnu/libpython3.7m.so: cannot open shared object file: No such file or directory

['/nix/store/gmfi2f3415k9xjppgn7rly5zzk0xsm2j-cozy-0.6.7/bin/.com.github.geigi.cozy-wrapped']
/nix/store/gmfi2f3415k9xjppgn7rly5zzk0xsm2j-cozy-0.6.7/bin/..com.github.geigi.cozy-wrapped-wrapped:60: PyGIDeprecationWarning: Since version 3.11, calling threads_init is no longer needed. See: https://wiki.gnome.org/PyGObject/Threading
  GObject.threads_init()
/nix/store/gmfi2f3415k9xjppgn7rly5zzk0xsm2j-cozy-0.6.7/bin/..com.github.geigi.cozy-wrapped-wrapped:71: DeprecationWarning: dist() and linux_distribution() functions are deprecated in Python 3.5
  log.info(platform.dist())
23:37:25 [MainThread  ] [main      ] [INFO ]  ('', '', '')
23:37:25 [MainThread  ] [main      ] [INFO ]  Starting up cozy 0.6.7
23:37:26 [MainThread  ] [ui        ] [INFO ]  Initialize main window
23:37:26 [Thread-2    ] [offline_ca] [INFO ]  Startet processing queue
23:37:26 [UpdateDataba] [importer  ] [INFO ]  Total import time: 0.0004296302795410156
23:37:26 [UpdateDataba] [offline_ca] [INFO ]  Startet processing queue

(.com.github.geigi.cozy-wrapped:11310): dconf-WARNING **: 23:37:49.711: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name ca.desrt.dconf was not provided by any .service files

23:37:52 [UpdateDataba] [importer  ] [INFO ]  Total import time: 3.0040740966796875e-05
23:37:52 [UpdateDataba] [offline_ca] [INFO ]  Startet processing queue
23:39:36 [UpdateDataba] [importer  ] [INFO ]  Total import time: 0.025415420532226562
23:39:36 [UpdateDataba] [offline_ca] [INFO ]  Startet processing queue
23:39:45 [UpdateDataba] [importer  ] [INFO ]  Total import time: 0.016440391540527344
23:39:46 [UpdateDataba] [offline_ca] [INFO ]  Startet processing queue
23:39:54 [MainThread  ] [player    ] [INFO ]  Closing.
23:39:59 [MainThread  ] [ui        ] [INFO ]  Closing.
23:39:59 [MainThread  ] [titlebar  ] [INFO ]  Closing.
23:39:59 [MainThread  ] [player    ] [INFO ]  Closing.
23:39:59 [MainThread  ] [db        ] [INFO ]  Closing.
23:39:59 [MainThread  ] [ui        ] [INFO ]  Closing app.
23:39:59 [MainThread  ] [ui        ] [INFO ]  App closed.

I can close it, reopen, and play a file with no issues.
I also tried erasing all data, running the pre-upgrade version (/nix/store/zhn0y1l8w4bjr4zjw7d2rjrga2a72qaq-cozy-0.6.7), and then running the post-upgrade version (seeing as it is database-related), but it worked all the same.

I also don't have a DE, so that may be contributing

hmm, cozy works fine on a different computer. No idea.


Unparseable json response for lines of code badge

Are you experiencing an issue with...

[x] shields.io
[ ] My own instance
[ ] badge-maker NPM package

:beetle: Description

The lines of code badge works before, however, since several days ago, it shows: unparseable json response.
Issue badge screenshot:

Live version:

:link: https://img.shields.io/tokei/lines/github/Hongbo-Miao/hongbomiao.com

Hello. This is happening because https://tokei.rs/b1/github/Hongbo-Miao/hongbomiao.com it is returning a non-JSON response
curl -H "Accept: application/json" "https://tokei.rs/b1/github/Hongbo-Miao/hongbomiao.com"

If I call another URL like
curl -H "Accept: application/json" "https://tokei.rs/b1/github/badges/shields"

that returns JSON as expected. This appears to be an issue with the tokei.rs service so can you raise an issue with them please.

Thanks @chris48s ! Created at https://github.com/XAMPPRocky/tokei/issues/794


[SPARK-27340][SS][TESTS][FOLLOW-UP] Rephrase API comments and simplify tests

What changes were proposed in this pull request?

Rephrase the API doc for Column.as
Simplify the UTs

Why are the changes needed?
Address comments in https://github.com/apache/spark/pull/28326
Does this PR introduce any user-facing change?
No
How was this patch tested?
New UT added.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/26662/
Test PASSed.

cc @cloud-fan @dongjoon-hyun @HeartSaVioR

Test build #121987 has started for PR 28390 at commit 6e98444.

Test build #121987 has finished for PR 28390 at commit 6e98444.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/121987/
Test PASSed.

Test build #122067 has started for PR 28390 at commit 1101d05.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/26742/
Test PASSed.

Test build #122067 has finished for PR 28390 at commit 1101d05.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/122067/
Test PASSed.

Test build #122098 has started for PR 28390 at commit d9baf7a.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/26772/
Test PASSed.

Test build #122098 has finished for PR 28390 at commit d9baf7a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/122098/
Test PASSed.

thanks, merging to master/3.0!

Thanks for the review.

Thank you all.


DB offloading - Create DB and schema

Create a new DB and create SQL for the schema.
Part of BI #81.

The add DB and create-osgp-offloading.sql worked fine
The correct DB structure was created.
The dbOffloading scripts worked fine on this DB


Better support for multithreaded debugging

Breakpoints on a per thread basis, better views of the current thread being debugged

Moved to https://prodbg.phoreplay.com/T50


Make creating (and adding to) tables via Iterators more flexible & intuitive

Currently Adding to and creating tables require RecordBatch iterator. To make this more intuitive we should support iterators of all types that are accepted by create_table() or add()

https://github.com/lancedb/lancedb/pull/430


add support for argument to x, to enable removing (not-current) directory

Workaround for #159
Does not work (PROMPT_COMMAND always adds $PWD again):
[user@there]$ z -x
Does work:
[user@here]$ z -x there

As I understand (see https://github.com/rupa/z/issues/208#issuecomment-335465026), the -x is already intended to be used with a regexp
$ z -x foo

meaning remove the current directory from the datafile, AND change to the directory matching foo. This is useful when z foo is changing to a directory you don't want to go anymore.

I have encountered this situation again, and z -x <previous-criteria> still does nothing for me
$ z -x foo
In fact, after running this many times ("until you land at target"), looks like it just keeps increasing the bad (current) directory's score. :(
[/base/foo/nested/wrong-foo]$ z -x foo
68         /base/foo
100        /base/foo/nested/wrong-foo
[/base/foo/nested/wrong-foo]$ z -x foo
68         /base/foo
101        /base/foo/nested/wrong-foo
[/base/foo/nested/wrong-foo]$ z -x foo
68         /base/foo
102        /base/foo/nested/wrong-foo
...

My work-around for this issue has been to cd to the directory I want gone, then use (_z -x; cd -) so that I'm no longer in the removed directory when my prompt command is run the next time.


Add Vaibhav-Gagneja to Before I Die

Issue Addressed
#188 Add Vaibhav-Gagneja to Before I Die

Proposed Changes and Benefits

Screenshots

Notes to Reviewers
@XanderRubio pls review

Checklist

[x] I have thoroughly read and understand The Contribution Guidelines.
[x] The title of this PR follows the keyword: brief description of change format, using one of the following keywords:

Feature - adds new or amends existing user-facing behavior.
Chore - changes that have no user-facing value, refactors, dependency bumps, etc.
Fix - bug fixes.
Docs - fixing typos and adding new content.

[x] I have listed my proposed changes and their benefits.
[x] I have linked the corresponding issue in the Issues section.

@VaibhavGagneja  Your pull request has been successfully merged!!! Congratulations .
Keep getting after it every day, raising back up from all the challenges you face to become a fashion and music influencer!
If you haven't already, please go ahead and star this repo and you are more than welcome to continually contribute to this project by assisting with our open issues, or adding your own new open issues, and additionally you can get an idea of ideas we have to continually grow this project further as technology and tech stack continually evolve by looking at the ROADMAP for the project. Have a great day, and thank you for taking the time to contribute,
Vaibhav! You can view your contribution now on the live link. Have a great rest of your day, and I will be sending you an invite to be a member of the Before I Die Code now.

@VaibhavGagneja Your pull request has been successfully merged!!! Congratulations .
Keep getting after it every day, raising back up from all the challenges you face to become a fashion and music influencer!
If you haven't already, please go ahead and star this repo and you are more than welcome to continually contribute to this project by assisting with our open issues, or adding your own new open issues, and additionally you can get an idea of ideas we have to continually grow this project further as technology and tech stack continually evolve by looking at the ROADMAP for the project. Have a great day, and thank you for taking the time to contribute,
Vaibhav! You can view your contribution now on the live link. Have a great rest of your day, and I will be sending you an invite to be a member of the Before I Die Code now.

@XanderRubio Thank you for kind words and accepting the merge :smiley: will surely look at the issues !!

@XanderRubio can you please add hacktoberfest accepted and hacktoberfest label to this pr


Consider make flax an optional dependency

It seems that the sole purpose of the flax dependency is to support conversion between haiku and flax, but flax's dependencies are considerably heavier  compared to the rest of haiku. I think it is a good idea to make flax an extra dependency, and avoid importing haiku.experimental.flax eagerly.

Thanks for letting us know! I'll take a look into whether we can do this for the next release.


Add variable for specific mise version during installation

Hello :wave: I would like to be able to install a specific version of mise with the official install script (https://mise.run/).
Is it possible to create an environment variable, for example MISE_VERSION that can be defined during installation here ?
Thanks in advance.

I'd accept a PR. I think we could either configure it via an env var or with curl https://mise.run | sh -s -- --version xxx
Here's an example of how to do it if anyone wants to contribute: https://github.com/crablang/crablang-site/blob/b4f3a38b30fad69902c188085c92566ef577e365/public/crabup-init.sh#L26

@jdx I made a PR, tell me if you want me to change something


Issue 372 - move tslint to eslint

Resolves #372
Changes:

add @typescript-eslint/eslint-plugin and @typescript-eslint/parser to enable linting of ts files
migrate tslint:recommended rules to plugin:@typescript-eslint/recommended
fix some issues for rules that don't work exactly as they did in tslint or where rules were previously ignored with @ts-ignore

Notes:

There are quite a few useful rules which i've disabled for consistency with the old tslint rules. I think it's worth analysing the disabled rules but i think this should be done in a separate issue once this is merged.
There's now 2 eslint config files (1 for js files and one for ts files). It might be useful to merge this to bring consistency of the codebase, but doing so in this PR would mean fixing a lot of linting issues, which again i think should be looked at as a separate issue.

Also, please make this PR to the dev branch instead of master to keep the master branch in sync with latest release :)
Thanks

All the changes look good, just one question to address about a change in tsconfig

Thanks, for your changes, that was pending for a while now :+1:


Modifications to arrays or repeated properties aren't observed

If a trait is changed by modifying the underlying data structure, the trait does not observe the change. Problem when swapping out project resources (ie proj.resources[2] = new_surf) or manipulating data (ie data.array[mask] = np.nan).

A good start would be upload(force=True)


DeepLink related

Hi,
I have @Destination with a Webview inside composable. I'm trying to open this Destination and passed received url to webview for showing webpage.
If i define a full/ exact path as deeplink for this destination then it can open it in webview e.g.
https://www.domain.com  <- works
https://www.domain.com/path/somepage.html  <- works
If let's say Deeplink is : https://www.domain.com
and i try : https://www.domain.com/page.html  <- doesn't work
Q: Is it possible to define Deeplink so that it can handle any path/pages from https://www.domain.com? can i use regex here?

I honestly don’t know. You should Google if that works for official compose navigation which gets used by this lib.
Whatever the deep link value we pass it to the official APIs, so the end result will be the same regardless of if you’re using this lib or official compose navigation 🙂
I’m closing as this is not an issue or question for this library.
Let me know if you find the solution! And thanks for choosing Compose Destinations!

thanks anyway

Sorry for not being helpful but since this is really not of this library I don’t know and I’d have to investigate myself just like you need to.
And I’m struggling with time 😅 I’m still interested if you find what you’re looking for so let me know 🙂

I looked for it before posting, still looking but so far no success. Will let know if I find something.
Cheers

got it working with :
composable(
route = "deeplinktest",
deepLinks = listOf(navDeepLink { uriPattern = "https://www.example.com/.*" })  // <---- notice .* after '/'
) {
......
}
OR with compose destinations
@Destination(
deepLinks = [
DeepLink(uriPattern = "https://www.example.com/.*")
]
)
in AndroidManifest.xml
<intent-filter>
                <action android:name="android.intent.action.VIEW"/>
                <category android:name="android.intent.category.DEFAULT"/>
                <category android:name="android.intent.category.BROWSABLE"/>
                <data android:scheme="https"
                    android:host="www.example.com" />
</intent-filter>

All of these work now
adb shell am start -d "https://www.example.com/" -a android.intent.action.VIEW
adb shell am start -d "https://www.example.com/blabla/" -a android.intent.action.VIEW
adb shell am start -d "https://www.example.com/test/hello.html" -a android.intent.action.VIEW
full url can be retrieved like this :
backStackEntry.arguments?.get("android-support-nav:controller:deepLinkIntent") as? Intent)?.data
OR
savedStateHandle.get("android-support-nav:controller:deepLinkIntent")?.data?.toString()

Great!
Thanks a lot for letting me know! Today I learnt, I didn’t know you could use regex?
glad you found the answer 🙂

if possible please add these findings to compose-destinations's wiki, hopefully helps someone

Look in fun buildPathRegex()(androidx/navigation/NavDeepLink.kt)

Today I learnt, I didn’t know you could use regex?

Look in fun buildPathRegex()(androidx/navigation/NavDeepLink.kt)


can not support mouse scroll event

Hello meslzy:
Thanks for your great work! It seems that the mouse forwarding didn't deal with mouse scroll event. I realy need it and can u support it :)

Ohh, i didn't need it when i created this library 😁.
But ill add the functionality now.


Add customisation point for replacing NSLocalizedString implementation

Hello 👋 We've used R.swift for years now in our project and I'm currently looking at migrating from 5.x to 7.x since we want to migrate our project to SPM in the near future.
In our project, we don't rely on the NSLocalizedString method for two reasons:

Our app uses a custom language selected by the user
We provide a more granular fallback on a per-phrase basis if the requested phrase is missing (i.e we only provide partial translations for es_MX and our implementation can look in es_419 or es if the phrase is missing)

This is something that we can't currently achieve with R.string(preferredLanguages: [ ... ])

In v5 of R.swift, we were able to use our custom implementation with the R.generated.swift code by providing an overload to NSLocalizedString(_:tableName:bundle:value:comment:) in the same module of the generated R.string struct. It wasn't great, but it did the job 😄
Looking into v7 however, it's not possible for us to use a similar trick because the resolution of a localized string has now moved into the RswiftResources module and therefor our overloaded implementation of NSLocalizedString(_:tableName:bundle:value:comment:) won't be called.
I've spent a bit of time trying to come up with various alternatives. I first started trying to just reimplement RswiftResources myself but this started getting complicated and I couldn't help but feel like I was having to write a lot of code that I didn't want to. It also meant that I had to update the generated code after running rswift:
$ sed -i '' '/import RswiftResources/d' "$SCRIPT_OUTPUT_FILE_0"
$ sed -i '' -E 's/RswiftResources\.(Image|String)Resource/\1Resource/g' "$SCRIPT_OUTPUT_FILE_0"

My fallback option is to just swizzle NSLocalizedString and replace the implementation with our own however this is my least favourite option for a lot of reasons 😄 I'm also not entirely sure if it's possible to achieve it without messing up other frameworks that call to NSLocalizedString (i.e UIKit internals).
Before going with swizzling, I have one last proposed idea that is this Pull Request. In this PR, i've added a public RswiftLocalizedString global property:
public var RswiftLocalizedString = Foundation.NSLocalizedString(_:tableName:bundle:value:comment:)

By default, it calls to Foundation's NSLocalizedString method , which is what 99.99% of users will want. But it provides me with a slightly nicer way to hook in and replace the implementation without swizzling at hopefully a very minimal cost in terms of maintenance within this project 🤞.
Please do let me know what you think though. I understand that this might need some more discussion but I opened a PR rather than an Issue to hopefully provide more context of what i'm trying to achieve. I guess that another option could be to make R.swift's preferredLanguages feature more powerful but my hunch is that it wouldn't be a simple challenge.
Thanks again for everything so far!

I guess that another option could be to make R.swift's preferredLanguages feature more powerful but my hunch is that it wouldn't be a simple challenge.

I'm going to have more of a look into this next week.

See: https://github.com/mac-cain13/R.swift/issues/843#issuecomment-1712923342