Math ops lowering and runtime issue

What happened?
MLIR is here.
Compilation failed after iree-convert-to-llvm pass.

error: failed to legalize operation 'math.acos' that was explicitly marked illegal

I added theses changes and it compiled, but having runtime issue.

iree/runtime/src/iree/hal/local/executable_plugin_manager.c:570: NOT_FOUND; missing 1 required executable imports: [acosf]; while invoking native function hal.executable.create; while calling import;
[ 1]   native hal.executable.create:0 -
[ 0] bytecode module.__init:268 model.mlir:4:10; creating VM context; creating run context

I'm not sure if the changes I made is right though.
Steps to reproduce your issue

git clone https://github.com/nod-ai/SHARK-TestSuite.git
cd SHARK-TestSuite/iree_tests/onnx/node/generated/test_acos
iree-compile model.mlir --iree-hal-target-backends=llvm-cpu -o model.vmfb
iree-run-module --module=model.vmfb --device=local-sync --flagfile=test_data_flags.txt

What component(s) does this issue relate to?
No response
Version information
No response
Additional context
No response

@pashu123 please take a look at it. My guess is that we need a polynomial approximation for math.acos. Because not all the systems have libc/libm. I could be wrong, please help take a deeper look.

@hanhanW After reading the issue https://github.com/iree-org/iree/issues/4717, I think libm is not the right way to go, and you're right. I created a small Python script to emulate https://stackoverflow.com/questions/28969184/is-there-an-accurate-approximation-of-the-acos-function (for testing) https://gist.github.com/pashu123/26c0c4e45b11634538a1637c115717fb and the results are  ```
Actual: 2.1682027434402467, Approximation: 2.1682027434402467
Actual: 1.9551931012905357, Approximation: 1.9551931012905357
Actual: 1.8234765819369754, Approximation: 1.8234765819369751
Actual: 1.5707963267948966, Approximation: 1.5707963267948966
Actual: 1.318116071652818, Approximation: 1.318116071652818
Actual: 1.1863995522992576, Approximation: 1.1863995522992574
Actual: 0.9733899101495465, Approximation: 0.9733899101495465

Thanks @pashu123 , what a quick fix! Please remember to send your LLVM commit out for review, thanks!

@pashu123 Thanks for your fix! Yes I got acos onnx tests working, but got a result mismatch for an asin test. Though the tests are imported from onnx by using iree-import-onnx, the expected result might not be correct. Could you check it out?

[FAILED] result[0]: element at index 7 (1.101) does not match the expected (1.10125); expected that the view is equal to contents of a view of 3x4x5xf32
expected:
3x4x5xf32=[[0.580944 0.796895 0.64696 0.57625 0.437476][0.702194 0.452914 1.10125 1.30039 0.39352][0.913628 0.557298 0.604128 1.18261 0.0710959][0.0872399 0.0202198 0.983821 0.891726 1.05523]][[1.36363 0.925894 0.479662 0.895512 0.118552][0.694395 0.143849 1.23658 0.549016 0.427571][0.267743 0.885503 0.473664 0.604601 0.0187909][0.665733 0.658708 0.664841 1.23379 0.750248]][[0.36774 0.452296 0.772086 0.0602619 0.729862][0.735068 0.211966 0.129286 0.320908 0.372248][0.606745 0.454042 1.41816 0.102223 0.210426][0.162017 0.711682 0.256081 0.485116 0.246927]]
actual:
3x4x5xf32=[[0.580944 0.796895 0.64696 0.57625 0.437476][0.702194 0.452914 1.101 1.29203 0.39352][0.913626 0.557298 0.604128 1.18135 0.0710959][0.0872399 0.0202198 0.983808 0.891725 1.05514]][[1.34451 0.925892 0.479662 0.895511 0.118552][0.694395 0.143849 1.2334 0.549016 0.427571][0.267743 0.885503 0.473664 0.604601 0.0187909][0.665733 0.658708 0.664841 1.23074 0.750248]][[0.36774 0.452296 0.772086 0.0602619 0.729862][0.735068 0.211966 0.129286 0.320908 0.372248][0.606745 0.454042 1.38255 0.102223 0.210426][0.162017 0.711682 0.256081 0.485116 0.246927]]

Also, is there any chance to add support for acosh, asinh, atanh, cosh, sinh? Thanks!

@pashu123 Thanks for your fix! Yes I got acos onnx tests working, but got a result mismatch for an asin test. Though the tests are imported from onnx by using iree-import-onnx, the expected result might not be correct. Could you check it out?

[FAILED] result[0]: element at index 7 (1.101) does not match the expected (1.10125); expected that the view is equal to contents of a view of 3x4x5xf32
expected:
3x4x5xf32=[[0.580944 0.796895 0.64696 0.57625 0.437476][0.702194 0.452914 1.10125 1.30039 0.39352][0.913628 0.557298 0.604128 1.18261 0.0710959][0.0872399 0.0202198 0.983821 0.891726 1.05523]][[1.36363 0.925894 0.479662 0.895512 0.118552][0.694395 0.143849 1.23658 0.549016 0.427571][0.267743 0.885503 0.473664 0.604601 0.0187909][0.665733 0.658708 0.664841 1.23379 0.750248]][[0.36774 0.452296 0.772086 0.0602619 0.729862][0.735068 0.211966 0.129286 0.320908 0.372248][0.606745 0.454042 1.41816 0.102223 0.210426][0.162017 0.711682 0.256081 0.485116 0.246927]]
actual:
3x4x5xf32=[[0.580944 0.796895 0.64696 0.57625 0.437476][0.702194 0.452914 1.101 1.29203 0.39352][0.913626 0.557298 0.604128 1.18135 0.0710959][0.0872399 0.0202198 0.983808 0.891725 1.05514]][[1.34451 0.925892 0.479662 0.895511 0.118552][0.694395 0.143849 1.2334 0.549016 0.427571][0.267743 0.885503 0.473664 0.604601 0.0187909][0.665733 0.658708 0.664841 1.23074 0.750248]][[0.36774 0.452296 0.772086 0.0602619 0.729862][0.735068 0.211966 0.129286 0.320908 0.372248][0.606745 0.454042 1.38255 0.102223 0.210426][0.162017 0.711682 0.256081 0.485116 0.246927]]

Also, is there any chance to add support for acosh, asinh, atanh, cosh, sinh? Thanks!

atanh is already there. cosh and sinh are also there. So, they might just work.

@jinchen62 For these kinds of tests, i.e., polynomial approximations, you should keep a threshold. It won't match the entire precision. 1.101 and 1.10125 are close, given that it's an approximation.

For SHARK test suite we had set it to https://github.com/nod-ai/SHARK/blob/cf2513e7b19960628ea44d44626fca5b23887c15/tank/model_utils.py#L346

@pashu123 I got the following kind of error for acosh, asinh, atanh, cosh, sinh.

error: failed to legalize operation 'math.atanh' that was explicitly marked illegal

Could you point me out where the supports of atanh, cosh and sinh are?

@pashu123 I got the following kind of error for acosh, asinh, atanh, cosh, sinh.

error: failed to legalize operation 'math.atanh' that was explicitly marked illegal

Could you point me out where the supports of atanh, cosh and sinh are?

You will find it here: https://github.com/pashu123/llvm-project/blob/0be25e06c6773c34c8d592f07d30a767003f28b1/mlir/lib/Dialect/Math/Transforms/PolynomialApproximation.cpp#L1656

@pashu123 I got the following kind of error for acosh, asinh, atanh, cosh, sinh.

error: failed to legalize operation 'math.atanh' that was explicitly marked illegal

Could you point me out where the supports of atanh, cosh and sinh are?

You will find it here: https://github.com/pashu123/llvm-project/blob/0be25e06c6773c34c8d592f07d30a767003f28b1/mlir/lib/Dialect/Math/Transforms/PolynomialApproximation.cpp#L1656

You are right. I was confused between cosh and cos. So, the implementation for acosh, asinh.. is not present.

@jinchen62 So, the lowering of sinh would be  1/2 * (math.exp(x) – math.exp(-x)), cosh would be 1/2 * (math.exp(x) + math.exp(-x)) and tanh = sinh/cosh. For acosh would be  math.log(x + math.sqrt(x**2 - 1)). We have an example for polynomial approximation for acos and asin; adding these would be straightforward. We can keep this a starter task if someone is willing.

Also, which models are they coming from? I have only seen cos and sin from LLAMA's rotary embedding.

@jinchen62 For these kinds of tests, i.e., polynomial approximations, you should keep a threshold. It won't match the entire precision. 1.101 and 1.10125 are close, given that it's an approximation.

FYI, tolerances can be changed using the --expected_f32_threshold=0.0001f flag, source: https://github.com/iree-org/iree/blob/9f5e356d0d7c7f62995413f03f1b42f2adac942e/runtime/src/iree/tooling/comparison.cc#L21-L26, added to either individual test cases like https://github.com/nod-ai/SHARK-TestSuite/blob/main/iree_tests/onnx/node/generated/test_acos/test_data_flags.txt (for all backends, CPU/GPU/etc.) or to configs for all tests on one backend: https://github.com/iree-org/iree/blob/9f5e356d0d7c7f62995413f03f1b42f2adac942e/build_tools/pkgci/external_test_suite/onnx_cpu_llvm_sync.json#L6-L8
We haven't had enough test cases with tolerance issues for either style to get much mileage... I'm leaning towards adding the tolerances upstream in SHARK-TestSuite for the test cases we know will often use polynomial approximations (asin, acos, etc.)

@pashu123 Thanks for your help! Could you land your llvm patch?

@pashu123 Thanks for your help! Could you land your llvm patch?

Sure, I will raise the PR today.

Changed the lowering of acosh, asinh, atanh, cosh, sinh.

Changed the lowering of acosh, asinh, atanh, cosh, sinh.

@ jinchen62 I suggest you add these as a part of the polynomial approximation pass since many frontends may take advantage of that. Since you've added this as a part of ONNX to TORCH lowering, this will not benefit TORCH frontend.

@pashu123 Please review https://github.com/llvm/llvm-project/pull/90718

Please keep issues open until fixes have fully landed (https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue on the PR that fixes the issue helps automate that)

https://github.com/iree-org/iree/pull/17324 was merged with test failures (newly passing tests need XFAIL lists updated) so it was reverted in https://github.com/iree-org/iree/pull/17324. You may also want to update tolerances as discussed.

https://github.com/iree-org/iree/pull/17395 is landed, closing the issue.


dotnet pack arguments Extensions

As of now, we have the following options to create a Nuget package via dotnet pack command

In case if want some additional resource files to be part of Nuget package that configuration must be added via .csproj file, an example (its only sample):
<ItemGroup >
    <None Include="MyFiles\*">
      <PackagePath>Content\MyFiles</PackagePath>
      <pack>true</pack>
    </None>
 </ItemGroup >

Is there any possibility to instruct dotnet pack command to include custom files or directories via the arguments instead of explicitly configuring or instructing via .csproj file?
Example:
1. dotnet pack --include-custom-files= "FirstFile.txt, SecondFile.txt, etc.."
2. dotnet pack --include-custom-directory="D:\Test\SomeadditonalFiles"

So that we can have the flexibility to add custom resource files or directories to the Nuget package without explicitly adding the resource files configs in .csproj.

Wrong repository
I requested in https://github.com/dotnet/sdk


Upgrade jemalloc, fix mem-profiling build

What have you changed? (mandatory)
This upgrades jemallocator to the latest published version, changes the code to use the stable allocator API, makes the mem-profiling build compile, and updates the codebase to continue working with libfuzzer.
This is part of upgrading to Rust 2018. I've pulled out only the jemalloc changes to try to land them alone, make sure everything continues to work.
Things to note:

This upgrades to the latest published jemallocator, away from @BusyJay's fork. I suspect that the fixes in BusyJay's fork are incorporated into the latest jemallocator, but don't know for sure.

jemalloc is used on all Unixes, and nowhere else.

jemalloc is configured to not prefix its symbols, such that on supported platforms it replaces libc malloc, letting RocksDB and Rust share the same allocator. This works on Linux, but notably not macOS.

jemallocator is always a dependency now, even if it's not used, where before it was only a dependency when the mem-profiling feature is on. Presumably that means it has to build correctly even on Windows, which I suspect it will.

The global allocator is set within the tikv library, so all the bins, tests, and benches that link to it should use jemalloc. The component tests, because they don't link to tikv, don't use jemalloc.

What are the type of the changes? (mandatory)

Improvement (non-breaking change which is an improvement to an existing feature)
Bug fix (non-breaking change which fixes an issue)

How has this PR been tested? (mandatory)
I ran the unit tests, clippy and rustfmt. I made sure that libfuzzer and honggfuzz continue to work.
Does this PR affect documentation (docs) update? (mandatory)
No.
Does this PR affect tidb-ansible update? (mandatory)
No.
Refer to a related PR or issue link (optional)
Full Rust 2018 upgrade PR: https://github.com/tikv/tikv/pull/3952

/rebuild

/rebuild

/rebuild

/rebuild

@BusyJay @siddontang thanks for updating this with merges.
@siddontang what's the next step in the process here? Seems like the build is good. Do I need to get another 'LGTM'? Should I merge myself or let someone else merge?


fvm releases should be in decending order

This has been solved on the latest version of FVM 0.0.5. Please look through the readme as there has been a lot of changes


Cleaning up "features"

Right now we have:

std/no_std
wee_alloc/qimalloc/stdalloc
one feature for each optional EEI: debug, experimental, bignum, eth2 (these would be merged into master once stable)

This is spawning this build hell as seen in #56.
Perhaps bignum could go under experimental. With time as these features mature, they wouldn't need to be conditionally enabled.
Maybe debug doesn't even need to be a feature, just made available. Idea by @jakelang to only enable the debug module when compiling in debug mode. Extending on that: how about making them macros which are compiled to nop in release mode?

We don't necessarily need to make them macros, but this is a nice idea because we can completely remove the code at compile-time rather than have calls to stub functions.

We've already remove the "bignum" feature and created #63 to track the "debug" feature.
It seems we'll end up with:

std/not_std
(option to use other allocators)
"experimental" and "eth2" features

I think this is more manageable now.


Set global data attribute for the whole dataset

If all the graphs in the dataset share some global attribute, assuming it as global_edge_index, how can we set it along with train_dataset/test_dataset only once, and put it into the DataLoader?

You can simply set/load your data as additional attribute of your dataset, e.g.:
dataset.edge_index = torch.tensor([...])

You can then pass this attribute to your data by using, e.g., custom transforms.

You can simply set/load your data as additional attribute of your dataset, e.g.:
dataset.edge_index = torch.tensor([...])

You can then pass this attribute to your data by using, e.g., custom transforms.

Could you please write a mini example about how to do this without saving duplicated edge_index?

MyTransform(object):
    def __init__(self, edge_index):
        self.edge_index = edge_index
    def __call__(self, data):
        data.edge_index = edge_index
        return edge_index

transform = MyTransform(dataset.edge_index)
dataset.transform = transform

should do the trick

Is this measure different than simply saving edge_index in each data? In both ways, data looks like the same way, Data(edge_index=[2, 29990], x=[5023, 3], y=[1]).

Well, by using transforms the data is not copied.

I see. Thanks.

Well, by using transforms the data is not copied.

Do you know why it is still consumed the higher time?
Batch(batch=[160736], edge_index=[2, 959680], x=[160736, 3], y=[32]) (edge_index is obtained by transform method)
Batch(batch=[160736], x=[160736, 3], y=[32]) (no edge_index, but I used a variable global_edge_index, and send this to the device so don't need to send it to device at each iteration)

Sure. The edge_index still gets created for each batch individually. If you do not want this, set drop_last=True in the DataLoader and create a batched edge_index on your own, e.g.:
edge_indices = []
cum_num_nodes = 0
for _ in range(batch_size):
    edge_indices.append(edge_index + cum_num_nodes)
    cum_num_nodes += num_nodes
edge_index = torch.cat(edge_indices, dim=1)

Sure. The edge_index still gets created for each batch individually. If you do not want this, set drop_last=True in the DataLoader and create a batched edge_index on your own, e.g.:
edge_indices = []
cum_num_nodes = 0
for _ in range(batch_size):
    edge_indices.append(edge_index + cum_num_nodes)
    cum_num_nodes += num_nodes
edge_index = torch.cat(edge_indices, dim=1)

I see. This is what I exactly have done on my work, i.e.., create a batched edge_index and drop the last incomplete batch. Thank you all the same.


failsafe_mode don't work when k8s return 409

What happened?
failsafe_mode don't work when k8s return 409
How can we reproduce it (as minimally and precisely as possible)?
I‘m not sure, maybe k8s is overload
What did you expect to happen?
failsafe_mode could work when k8s return 409
Patroni/PostgreSQL/DCS version

Patroni version: 3.1.0
PostgreSQL version:
DCS (and its version):  k8s

Patroni configuration file
ttl: 30
loop_wait: 10
retry_timeout: 10
failsafe_mode: true

patronictl show-config
no need

Patroni log files
2024-02-18 07:15:35,544 INFO: no action. I am (node0), the leader with the lock
2024-02-18 07:15:41,360 INFO: Lock owner: node0; I am node0
2024-02-18 07:15:46,373 ERROR: Request to server https://<IP_ADDRESS>:443 failed: ReadTimeoutError("HTTPSConnectionPool(host='<IP_ADDRESS>', port=443): Read timed out. (read timeout=4.999478869140148)",)
2024-02-18 07:15:49,314 ERROR: Request to server https://<IP_ADDRESS>:443 failed: ReadTimeoutError("HTTPSConnectionPool(host='<IP_ADDRESS>', port=443): Read timed out. (read timeout=2.045989267528057)",)
2024-02-18 07:15:51,369 ERROR: Request to server https://<IP_ADDRESS>:443 failed: ReadTimeoutError("HTTPSConnectionPool(host='<IP_ADDRESS>', port=443): Read timed out. (read timeout=1.631961651146412)",)
2024-02-18 07:15:51,369 ERROR: Error communicating with DCS
2024-02-18 07:15:51,377 INFO: Got response from node1 http://<IP_ADDRESS>:8009/patroni: Accepted
2024-02-18 07:15:51,471 INFO: continue to run as a leader because failsafe mode is enabled and all members are accessible
2024-02-18 07:15:51,473 WARNING: Loop time exceeded, rescheduling immediately.
2024-02-18 07:15:51,474 INFO: Lock owner: node0; I am node0
2024-02-18 07:15:56,485 ERROR: Request to server https://<IP_ADDRESS>:443 failed: ReadTimeoutError("HTTPSConnectionPool(host='<IP_ADDRESS>', port=443): Read timed out. (read timeout=4.989643476903439)",)
2024-02-18 07:15:59,227 ERROR: Request to server https://<IP_ADDRESS>:443 failed: ReadTimeoutError("HTTPSConnectionPool(host='<IP_ADDRESS>', port=443): Read timed out. (read timeout=2.2473123595118523)",)
2024-02-18 07:15:59,876 WARNING: Concurrent update of node-leader
2024-02-18 07:16:00,998 ERROR: failed to update leader lock
2024-02-18 07:16:00,998 INFO: Demoting self (immediate-nolock)
2024-02-18 07:16:03,956 INFO: demoted self because failed to update leader lock in DCS

PostgreSQL log files
no need

Have you tried to use GitHub issue search?

[X] Yes

Anything else we need to know?
No response

409 is a concurrent update.
That is, K8s API is up and running and someone else updated the leader object.
failsafe_mode can't help with it.

@ChenChangAo make sure you use the latest Patroni version, there have been some fixes in this are

https://github.com/patroni/patroni/pull/3174
This PR might help with this issue.


fix: Modify label sync global node path

What type of PR is this?
/kind bug

What does this PR do?

Modify label sync global node path: .Labels.—>Spec.Labels
Which issue(s) does this PR fix?

Fixes #
Special notes for your reviewer:

@OrangeBao
Does this PR introduce a user-facing change?

NONE

https://github.com/kosmos-io/kosmos/pull/591 solved the problem, https://github.com/kosmos-io/kosmos/pull/589 is no longer needed, so it is closed.


Update README.md

@Rick-Anderson,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

Hi @Rick-Anderson,
The 'cache priming' is no longer supported @SteveSandersonMS§ closed an issue the other day saying it should not be referenced in the docs.
https://github.com/aspnet/JavaScriptServices/issues/858
Thanks,
Sandeep

@initialspark  removed cache priming - how is the rest of my changes?

@Rick-Anderson I am not the person who reviews these changes to allow them to be merged. It was just something i came across in a previous issue around the cache priming feature.


Kubernetes integration broken by small typo

The following code doesn't work because the annotation is supposed to be flame.pawelmalak/name and not flame.pawelmalak/.name.
https://github.com/fdarveau/flame/blob/32324ed6967743250460a44a0e5407579b5805d3/controllers/apps/docker/useKubernetes.js#L63

Thanks for the bug report and the solution.
Since I don't have a Kubernetes setup to test on, could you pull tes ghcr.io/fdarveau/flame:fix_kubernetes_annotation and confirm the fix is working?
I will complete #27 once you confirm to push the fix to the latest tag.


Feature: Modifying Tech Stacks in ReadMe

We can add a link to Documentation of Each Tech Stack in ReadMe.md
Basic Markdown design
![name](link)
Further we Can add EJS to the tech stack as it is the templating engine which is used.

@SurajPratap10 may you assign this issue to me under GSSOC'23

assigned @PranavSikarwal 📌


APPS-924 revert change that removes logging limit

I approved the dxScala PR, so you should be able to merge it and use the new snapshot.


permissions - gitblit plugin

Description

GitHub repo: https://github.com/jenkinsci/gitblit-plugin
Hosting request: https://issues.jenkins-ci.org/browse/HOSTING-603
Commiter andreasmandel
Submitter checklist for changing permissions

Always

[x] Add link to plugin/component Git repository in description above

For a newly hosted plugin only

[x] Add link to resolved HOSTING issue in description above

For a new permissions file only

[x] Make sure the file is created in permissions/ directory
[x] artifactId (pom.xml) is used for name (permissions YAML file).
[x] groupId / artifactId (pom.xml) are correctly represented in path (permissions YAML file)
[x] Check that the file is named plugin-${artifactId}.yml for plugins

When adding new uploaders (this includes newly created permissions files)

[x] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[x] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[x] All newly added users have logged in to Artifactory at least once

Build failed; the context from the latest run is:
Expand to view
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Build)
[Pipeline] tool
Unpacking https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.5.4/apache-maven-3.5.4-bin.zip to /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/mvn on ubuntu-jenkinsinfrabb90c0
[Pipeline] tool
Installing /home/jenkins/tools/hudson.model.JDK/jdk8/jdk.sh
[jdk8] $ tar xzf /home/jenkins/tools/hudson.model.JDK/jdk8/jdk.sh
[Pipeline] sh
+ /home/jenkins/tools/hudson.tasks.Maven_MavenInstallation/mvn/bin/mvn -U clean verify
[INFO] Scanning for projects...
Downloading from repo.jenkins-ci.org: https://repo.jenkins-ci.org/public/org/jenkins-ci/jenkins/1.36/jenkins-1.36.pom
[WARNING] Failed to create parent directories for tracking file /home/jenkins/.m2/repository/org/jenkins-ci/jenkins/1.36/jenkins-1.36.pom.lastUpdated
Downloading from central: https://repo.maven.apache.org/maven2/org/jenkins-ci/jenkins/1.36/jenkins-1.36.pom
[WARNING] Failed to create parent directories for tracking file /home/jenkins/.m2/repository/org/jenkins-ci/jenkins/1.36/jenkins-1.36.pom.lastUpdated
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for io.jenkins.infra:repository-permissions-updater:1.0-SNAPSHOT: Could not transfer artifact org.jenkins-ci:jenkins:pom:1.36 from/to repo.jenkins-ci.org (https://repo.jenkins-ci.org/public/): /home/jenkins/.m2/repository/org/jenkins-ci/jenkins/1.36/jenkins-1.36.pom.part.lock (No such file or directory) and 'parent.relativePath' points at wrong local POM @ line 3, column 13
 @
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project io.jenkins.infra:repository-permissions-updater:1.0-SNAPSHOT (/home/jenkins/workspace/tory-permissions-updater_PR-1036/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for io.jenkins.infra:repository-permissions-updater:1.0-SNAPSHOT: Could not transfer artifact org.jenkins-ci:jenkins:pom:1.36 from/to repo.jenkins-ci.org (https://repo.jenkins-ci.org/public/): /home/jenkins/.m2/repository/org/jenkins-ci/jenkins/1.36/jenkins-1.36.pom.part.lock (No such file or directory) and 'parent.relativePath' points at wrong local POM @ line 3, column 13 -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Archive)
[Pipeline] archiveArtifacts
Archiving artifacts
[Pipeline] archiveArtifacts
Archiving artifacts
‘json/*.json’ doesn’t match anything: even ‘json’ doesn’t exist
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Terminated

GitHub has been notified of this commit’s build result

ERROR: No artifacts found that match the file pattern "json/*.json". Configuration error?
Finished: FAILURE

Powered by the Comment Logger

LGTM


Wrong parameters multiClientMiddleware

This is happening when you try to use more than one client.
I have tried everything (How to structure the config for multiple clients).
using version ^4.0.0
//My current config
import axios from 'axios';
const clients = {
    ['default']: {
        client: axios.create({
            baseURL: 'http://foo/',
            responseType: 'json',
        }),
        options: {
            interceptors: {
                request: [
                    (store, config) => {
                        return config
                    }
                ]
            }
        }
    },
    ['bar']: {
        client: axios.create({
            baseURL: '/bar',
            responseType: 'json',
        }),
        options: {
            interceptors: {
                request: [
                    (store, config) => {
                        return config
                    }
                ],
                response: [
                    (store, response) => {
                        return response
                    }
                ]
            }
        }
    }
}

export default clients;

Any comment on this?

@AthanasiosKoumpouras
Sorry, I don't understand the purpose of this PR, can you please explain in more detail?
Thanks.


[Documentation] Add docs for surfacers

Add examples and more information about how to use different types of surfacers in the online docs. It's unclear how to send data to Stackdriver for example.

Thanks for filing this, @icco (Hello, by the way :)). I am working on the documentation for Stackdriver as this has come up quite a few times recently.
In the meantime, the smallest config for stackdriver looks like the following:
surfacer {
  type: STACKDRIVER
}

You can have multiple surfacers, for example, to add both, prometheus and stackdriver surfacer:
surfacer {
  type: PROMETHEUS
}

surfacer {
  type: STACKDRIVER
}

More config options:
https://github.com/google/cloudprober/blob/master/surfacers/stackdriver/proto/config.proto
https://github.com/google/cloudprober/blob/master/surfacers/prometheus/proto/config.proto

👋 ! neat, thanks! Talking a bit about how wonderful cloudprober is in a book for https://newline.co so just want to make sure that if I send folks here they have all of the docs they need to be successful.

That's great. Thanks Nat! :)
Added some initial documentation on surfacers:
https://cloudprober.org/surfacers/overview/
https://cloudprober.org/surfacers/stackdriver/
I'll add some examples as well.

Added examples here: https://github.com/google/cloudprober/tree/master/examples/surfacers (commit: https://github.com/google/cloudprober/commit/4be46a994f2ba47b4f71a227f3db47297ce275c3).

Closing the bug now. I'll look forward to reading your book, @icco :)


logrotate config files will be overwritten every hour

RancherOS Version: (ros os version)
v1.5.1
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
All
The logrotate service runs every hour by cron service, you can check its service label.
https://github.com/rancher/os/blob/master/os-config.tpl.yml#L249-L256
    logrotate:
      image: {{.OS_REPO}}/os-logrotate:{{.VERSION}}{{.SUFFIX}}
      command: /usr/sbin/logrotate -v /etc/logrotate.conf
      labels:
        io.rancher.os.createonly: "true"
        io.rancher.os.scope: system
        io.rancher.os.before: system-cron
        cron.schedule: "@hourly"

The logrotate has en entrypoint script, https://github.com/rancher/os/blob/master/images/02-logrotate/usr/bin/entrypoint.sh:
#!/bin/bash

cp /usr/share/logrotate/logrotate.d/* /etc/logrotate.d

exec /usr/bin/ros entrypoint "$@"

If the /etc/logrotate.d/docker file is modified, it will be overwritten each time, as the /usr/share/logrotate/logrotate.d/docker file is in the logrotate container.

Tested with rancher/os:v1.5.2-rc1 from May 27
This version of logrotate config files will not be overwritten every hour.
Verified fixed.


RedisConnectionException when using Amazon ElastiCache

We encountered an issue when using Redisson to connect our application running on Ubuntu to Amazon ElastiCache for Redis.
When performing any operation Redisson throws a RedisConnectionException: Unable to connect xxxx.cache.amazonaws.com/10.xxx.xxx.xxx:6379. However, after installing the redis-tools package (using apt-get) the issue goes away and everything works correctly.
Does Redisson requires the redis-cli binary or the redis-tools package? Did anyone had a similar issue?

ElastiCache support added in https://github.com/mrniko/redisson/pull/244


Add double click and double click + drag gestures to SelectionArea

Adds double click to select a word.
Adds double click + drag to select word by word.
https://user-images.githubusercontent.com/948037/234363577-941c36bc-ac42-4b7f-84aa-26b106c9ff05.mov
Partially fixes #104552
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is [test-exempt].
[x] All existing and new tests are passing.

Looks like the failing tests are because getPositionForOffset returns a different value on web vs other platforms.
  Offset textOffsetToPosition(RenderParagraph paragraph, int offset) {
    const Rect caret = Rect.fromLTWH(0.0, 0.0, 2.0, 20.0);
    final Offset localOffset = paragraph.getOffsetForCaret(TextPosition(offset: offset), caret);
    return paragraph.localToGlobal(localOffset);
  }

  test('getWordBoundary control test failing', () {
    final RenderParagraph paragraph = RenderParagraph(
      const TextSpan(text: 'How are you?'),
      textDirection: TextDirection.ltr,
    );
    layout(paragraph);

    final Offset target4 = textOffsetToPosition(paragraph, 4);
    final TextPosition position4 = paragraph.getPositionForOffset(target4);
    final TextRange range4 = paragraph.getWordBoundary(position4);
    expect(range4.textInside('How are you?'), equals('are'));
  });

This fails with --platform=chrome

Thanks for opening that issue!

This is ready for another review. I'm still running into the issue where the scrollable synthesizes an event for the opposite edge sometimes losing the origin word boundary, but this happens a lot less if we track the synthesized event https://github.com/flutter/flutter/pull/124817/commits/9239d36bd00188235c5a8a4105c2b563061b41b5.


kured cordon node before checking if just 1 up

If a reboot is required, kured will cordon the node before it obtains the concurrency lock.
ie. if you currently just have a single control-plane running due to some other problem, and the auto updater kicks in marking the node reboot-required kured will gladly cordon the last control-plane and leave the cluster in a state where nothing happens.

waiting for someone to take a look

Hi @davhdavh, I'm not seeing what your report in the way the code is implemented. We do set a "prefer do not schedule" taint, if configured, immediately upon detecting that a reboot is required, but we don't actually cordon/drain until the lock is acquired. Ref:

https://github.com/kubereboot/kured/blob/1.14.2/cmd/kured/main.go#L778-L782

Which version of kured are you using?

1.14.1
This is what happens:
kubectl describe node xxx

Logs from kured:

So it is getting the lock (because there is only 1 master, so nothing else could be holding it), but it cannot complete the reboot, so it gets stuck in situation where the cluster just dies.

Hi @davhdavh,
the log already shows the reason for the behaviour. There are PDBs in your cluster which prevent pods from being evicted. Kured only makes sense when the cluster can be rebooted automatically. This is not the case, as every drain - automated through kured or manual via kubectl - will fail. This is nothing kured can handle.


Smoothen the Scrolling between sections

While clicking on the navbar make sure that their is a smooth transition from one section to another instead of directly jumping to one

Please I would like to work on this issue.

Please I would like to work on this issue.

Sure!


docker compose is auto sufficient

CI should be able to "install" on machine will only Docker And Compose installed
take a look a Docker Compose.yml v3
use healthcheck or custom entrypoint to insert manifmaker user to database
git clone repo if not present

voc


Authenticate on CI

Checklist

[x] I have read the Contributor Guide
[x] I have read and agree to the Code of Conduct
[x] I have added a description of my changes and why I'd like them included in the section below

Description of Changes
Use GitHub API token to avoid hitting rate limit on CI.
The CI build shows it working, tada
Related Issues
Closes #25

Thanks Sonia!


R2Dtool annotate error

Hello, excited to use the R2Dtool. I am having trouble with the annotate function. I am running on a linux server, and compiled on rust 1.76.0
Command used:
r2d annotate --gtf Homo_sapiens.GRCh38.113.gtf --input r2_bed_m6a.bed > test.bed
Output error:
thread 'main' panicked at src/annotate.rs:185:47:
called Result::unwrap() on an Err value: ParseIntError { kind: InvalidDigit }
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
I am able to reproduce this error on my macbook and while using the test data.

I should note, the "splice_sites_map.txt" file output is produced.

Hi, can you please share a sample of the input data being used?

Here is the bed file I was using.
I have been able to use the deprecated Rscripts and have found that the outputs work fine with the remaining tools. Seems to just be an issue with the rust built annotate function.
r2_bed_m6a.txt


Uplift chatgpt-api version

Sydney is back :)

Sweet! Are you still working on this? it's marked as a draft

Sweet! Are you still working on this? it's marked as a draft
Yes, currently, the message tree for bingai and sydney is mangled. I fixed for Sydney, and will work on bingai tmr!

Thank you!

@danny-avila Can you check?

I merged this, but this issue had been happening even before that: currently, I'm trying to debug the latest changes to the master branch as chatgpt is not retaining conversations. I'm not very familiar with how the conversation handling has evolved since I first designed it, so I may limit backend changes until there's a proper test env.
Rolling back the node-chatgpt-api version didn't fix the issue. Luckily, my search branch is fully functional, and I may end up using it as the main branch and manually walking back the latest commits made to master.

Did my comb-through, I did identify the api update may have been part of the issue but unsure, had a lot more housekeeping to do.
@HyunggyuJang would you mind trying again off the latest master branch? you can test the latest api using the alias i installed
"chatgpt-latest": "npm<EMAIL_ADDRESS>
so you'll need to change
const { BingAIClient } = (await import('@waylaidwanderer/chatgpt-api'));
and sydney to await import('chatgpt-latest')
Thank you!

Did my comb-through, I did identify the api update may have been part of the issue but unsure, had a lot more housekeeping to do.
@HyunggyuJang would you mind trying again off the latest master branch? you can test the latest api using the alias i installed
"chatgpt-latest": "npm<EMAIL_ADDRESS>
so you'll need to change
const { BingAIClient } = (await import('@waylaidwanderer/chatgpt-api'));
and sydney to await import('chatgpt-latest')
Thank you!

Got it! Will work on that.

Thank you! last thing, work off 'working-branch' since master is giving me issues. it's difficult to debug because it may be due to auto merging

@HyunggyuJang as far as testing goes, you can just focus on reproducing your changes for bing/sydney with the alias package, and then i can go from there!

FYI I reproduced your changes with some minor tweaks and got this working alongside the old chatgpt-api version as still debugging changes there


[breaking change] Discontinue deprecated core library APIs, part II

The following Dart core library APIs, which are all currently deprecated, are now being fully removed.
This is the continuation of previous discontinuation work tracked in https://github.com/dart-lang/sdk/issues/34233
Phase II, scheduled for Dart 3.0
The following APIs are planned to be removed in 3.0, as some breakage is to be expected.
API changes which we believe are minimally breaking
dart:core

[x] onError argument to int.parse, double.parse, num.parse:
CL: https://dart-review.googlesource.com/c/sdk/+/259042
[x] proxy constant:
CL: https://dart-review.googlesource.com/c/sdk/+/258004
[x] Provisional class and associated constant:
CL: https://dart-review.googlesource.com/c/sdk/+/258004
[x] List constructor (use List.Filled):
CL: https://dart-review.googlesource.com/c/sdk/+/258920
[x] BidirectionalIterator class:
CL: https://dart-review.googlesource.com/c/sdk/+/276741
[x] Deprecated.expires getter on Deprecated. Use Deprecated.message instead.
[x] Errors:

[x] AbstractClassInstantiationError class (no longer relevant in dart:core libraries. dart:mirrors may still throw it and now has it's own definition of it):
CL: https://dart-review.googlesource.com/c/sdk/+/274383
[x] CastError class (use TypeError):
https://dart-review.googlesource.com/c/sdk/+/259041
[x] FallThroughError class (Unused since Dart 2.0):
https://dart-review.googlesource.com/c/sdk/+/261860,
CL: https://dart-review.googlesource.com/c/sdk/+/259041
[x] NoSuchMethodError default constructor (use the named constructor NoSuchMethod.withInvocation):
CL: https://dart-review.googlesource.com/c/sdk/+/271082
[x] CyclicInitializationError (will never be thrown from code with sound null safety):
https://dart-review.git.corp.google.com/c/sdk/+/275120
[x] NullThrownError (will never be thrown from code with sound null safety):
https://dart-review.googlesource.com/c/sdk/+/275840

dart:async

[x] DeferredLibrary class (use the deferred as import syntax):
CL: https://dart-review.git.corp.google.com/c/sdk/+/268460

dart:developer

[x] MAX_USER_TAGS in UserTag:
CL: https://dart-review.git.corp.google.com/c/sdk/+/268340

dart:mirrors
None.
dart:html

[x] document.registerElement & registerElement2:
https://github.com/dart-lang/sdk/issues/49536,
CL 📝: https://dart-review.git.corp.google.com/c/sdk/+/268461

API changes which may be more breaking
These are postponed, and not planned for inclusion in Dart 3.
### dart:core

[ ] IntegerDivisionByZeroException exception (use UnsupportedError ):
~~https://github.com/dart-lang/sdk/issues/30743~~
[ ] Errors:

### dart:async

[ ] runZoned arg on onError:
CL: https://dart-review.googlesource.com/c/sdk/+/248002

Our dependency is still there, but probably can easily be refactored by updating the dart2js patch files without changing the compiler directly
/cc @rakudrama

If we want to ship dart migrate in Dart 3.0, is it ok if that tool does not understand these removed APIs?
For example, if someone installs Dart 3.0, and uses that Dart's dart migrate to try to migrate code which refers to CastError, is it ok if dart migrate fails in some way? Crashes or something like that on the unresolved element.

@mit-mit https://github.com/dart-lang/sdk/commit/efb509c114dcaf54d0a011f717b48893d71ec9c3 should address the dependency from dart2js, I think the constructor is now ready to be removed.

If we want to ship dart migrate in Dart 3.0, is it ok if that tool does not understand these removed APIs?

@srawlins I think that is OK. If a developer wants support for migrating away from discontinued APIs, they can use the 2.19 SDK.

@sigmundch @kevmoo is the comment above about the dart:html change accurate (i.e. we're removing that in 2.19)?

@mit-mit, can you clarify which comment are you referring to?
We landed changes to mark the APIs deprecated in late July. Those haven't been released yet in the stable channel, so it will first get broad visibility with the 2.19 stable release. Given that, we wont be removing it entirely in 2.19, but the release that follows.

@sigmundch I was looking at an older, stale version, sorry.

Given that, we wont be removing it entirely in 2.19, but the release that follows.
sgtm, we'll track that as a 3.0 removal then

AbstractClassInstantiationError class (no longer relevant)

The class may be irrelevant when running normal Dart code, but not when using mirrors:
https://github.com/dart-lang/sdk/blob/636232628bfb9f8aa1d8b16656d647c8c3cc2205/tests/lib/mirrors/instantiate_abstract_class_test.dart#L40-L44
Should classMirror.newInstance(decl.constructorName, args) start throwing a different type of exception, or should we move AbstractClassInstantiationError to dart:mirrors as per https://dart-review.googlesource.com/c/sdk/+/259041/16/sdk/lib/mirrors/mirrors.dart ? @mit-mit

The class may be irrelevant when running normal Dart code, but not when using mirrors:

The text was unclear. It's no longer relevant in the dart:core libraries. But, yes mirrors can still throw it, and now have their own definition of it: https://dart-review.googlesource.com/c/sdk/+/259041/16/sdk/lib/mirrors/mirrors.dart

@mit-mit Can Are you expecting there will be tracking issues for the removal of CyclicInitializationError and NullThrownError. Is there already discussion happening somewhere?

All done, closing

hey @mit-mit you forgot MapEntry in your list which cannot be extends anymore (it breaks ClojureDart btw).

Making MapEntry a final class will, like all other now-final classes in the platform libraries, only affect code when it migrates to Dart 3.0.
It's not, technically, considered breaking, even though it prevents some uses from being continued. The existing code, running at language version 2.19, will keep working until support for pre-3.0 code is removed, which is unlikely to be soon.
 Allow me to share my viewpoint:
As a library creator, supporting all major Dart version updates is crucial to prevent the library from becoming obsolete.
What occurred to libraries that failed to transition from Dart 1 to 2.X?
The final class example is an excellent illustration. Introducing final class in Dart standard libraries disrupts all code dependent on those classes when transitioning to Dart 3, generating unplanned work for library authors.
When I examine the decision to make MapEntry a final class, it appears to be final for the sake of precaution rather than necessity.
Please don't misunderstand me; I adore Dart and the team behind it, and I will always be thankful for the impact it had on my life when I chose it for ClojureDart.
I would simply prefer minimal Breaking Changes.
Thanks for all your work 🙇


Add description to project.json

/cc @Eilon

@kichalla Could you take this in as well, while you're merging the other PRs?

Thanks @hishamco. Merge conflicts with the recent changes happening on project.jsons across the board. More are expected in the next few weeks so closing this. We'll do the necessary changes at a later time.


Fix: Unzip the right file

@dwmkerr Lets wait for the pipeline to pass before merging. :P

Yeah I didn't realise you'd only just pushed, running locally and have applied the same fix 😄

I've just updated CircleCI to build forked PRs, you can push a commit again and that should trigger a rebuilt. You might need to update the tests file to update the version of terraform it checks for, that'll trigger a rebuild

I made the edits in browser :P
Looks like no pipeline is running. Did you run out of credits?

I think if you make an edit now it'll build - I just updated the circleci config to allow builds from pull requests (before that it would only build branches in the repo itself). Try updating the version numbers in tests.sh to trigger a built

At least I can see the test is working locally:

Fixed in #11, released as v0.3.1

The image name dwmkerr/terraform-ci does not work for local testing.
Also added that as a parameter

👍


Ensure v6.4 compatibility

Summary
In the previous implementation in the function simrupt_init(), we utilize a function call "class_create()" to create a class structure for the kernel module. This function is explicitly called with "class_create(THIS_MODULE, DEV_NAME)", which will cause a compiling error. The reason is the function "class_create()" only allows a single arguments, but two are used here. That's why the corresponding change is made to make sure the basic compiling process is error-free.
Compiler version
gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0

Can you check the kernel compatibility? For Linux v5.15, I encountered the following:
/home/jserv.linux/simrupt/simrupt.c: In function ‘simrupt_init’:
/home/jserv.linux/simrupt/simrupt.c:341:42: error: macro "class_create" requires 2 arguments, but only 1 given
  341 |     simrupt_class = class_create(DEV_NAME);
      |                                          ^
In file included from ./include/linux/device.h:31,
                 from ./include/linux/cdev.h:8,
                 from /home/jserv.linux/simrupt/simrupt.c:3:
./include/linux/device/class.h:273: note: macro "class_create" defined here
  273 | #define class_create(owner, name)               \
      |
/home/jserv.linux/simrupt/simrupt.c:341:21: error: ‘class_create’ undeclared (first use in this function); did you mean ‘vfs_create’?
  341 |     simrupt_class = class_create(DEV_NAME);
      |                     ^~~~~~~~~~~~
      |                     vfs_create

Can you check the kernel compatibility? For Linux v5.15, I encountered the following:
/home/jserv.linux/simrupt/simrupt.c: In function ‘simrupt_init’:
/home/jserv.linux/simrupt/simrupt.c:341:42: error: macro "class_create" requires 2 arguments, but only 1 given
  341 |     simrupt_class = class_create(DEV_NAME);
      |                                          ^
In file included from ./include/linux/device.h:31,
                 from ./include/linux/cdev.h:8,
                 from /home/jserv.linux/simrupt/simrupt.c:3:
./include/linux/device/class.h:273: note: macro "class_create" defined here
  273 | #define class_create(owner, name)               \
      |
/home/jserv.linux/simrupt/simrupt.c:341:21: error: ‘class_create’ undeclared (first use in this function); did you mean ‘vfs_create’?
  341 |     simrupt_class = class_create(DEV_NAME);
      |                     ^~~~~~~~~~~~
      |                     vfs_create

I'm using Linux v6.5.0-26-generic in my computer , I'll refactor the implementation and send it up later.
$ uname -r
6.5.0-26-generic

Thank @vax-r for contributing!


Support ACTION_IGNORE_BATTERY_OPTIMIZATION_SETTINGS for Reliable Location Tracking

Is your feature request related to a problem? Please describe.
On Android devices, battery optimization settings can interrupt or restrict background location tracking. This leads to inconsistent behavior when accurate and continuous location updates are required.
Describe the solution you'd like
We request the addition of support for the ACTION_IGNORE_BATTERY_OPTIMIZATION_SETTINGS intent in the Capacitor background geolocation plugin. This would enable developers to prompt users to exempt the app from battery optimizations.
Describe alternatives you've considered
There are no reliable workarounds to bypass Android’s battery optimization restrictions without user intervention.
Additional context
Adding this support will allow developers to ensure consistent and uninterrupted background location tracking on Android devices.

ACTION_REQUEST_IGNORE_BATTERY_OPTIMIZATIONS is even more direct then ACTION_IGNORE_BATTERY_OPTIMIZATION_SETTINGS.
I have tried to avoid adding Android or iOS specific features to this plugin, but I agree that this one is pretty important. Unfortunately it depends on the <uses-permission-sdk-23 android:name="android.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS" /> permission, even if the app never uses this feature. Could that be an impediment to Play Store review?


Commissioning with Google Home fails at the end with "device not found"

Turns out the reason is we don't (yet) support the RevokeComm command on the admin cluster.
My next branch has an impl that fixes the issue. To be merged soon, hopefully.

Fixed by https://github.com/project-chip/rs-matter/pull/137


Switch to github actions

As per RFC-123, which specified that we would switch from Jenkins to Github Actions for our gems.
This PR needs to be merged first, as it removes unused code that is not compatible with ruby 3.0 (it would be possible to make it compatible but since it's unused we've decided to remove instead). After this github actions PR is merged, we can then release the code removal change to test the release process :-)
Also, before this PR is merged someone with access will need to:

remove branch protection; and
add the github secret

Trello

Changes here look good. It looks like this will need a rebase once https://github.com/alphagov/govuk_message_queue_consumer/pull/73 is merged as the commit hashes are different.
Before this is merged I'm hoping to get another TLC PR in. I'll try have it raised later today once https://github.com/alphagov/govuk_message_queue_consumer/pull/73 is merged (so I can rebase off it)


Update Using Private Data in Fabric tutorial

Type of change

Documentation update

Description
Update Using Private Data in Fabric tutorial.

closing due to cherry-pick issue.

@btl5037 I am trying to cherry-pick changes back to 2.2 from approved PR on master, let me know if this is not correct. Thanks.

Need to re-work cherry-pick.


Google group for KaTeX?

I actually have a question, rather than an issue, but couldn't find anywhere to ask my question. Hence the   Google group suggestion. :-)
I'll ask my question here anyway and hope it's not annoying.
I'm looking for 2 signals:

When a particular math expression has finished processing.
When all the math on a page has finished processing.

Thank you!
Regards,
Murray

Sounds like everything was resolved here – let me know if not and I'll reopen.


[0.7] Error Daemon

Please describe your issue in full below. Include what products are affected, as well as what version(s) you are running. Please also include information about your system, such as uname -a and php -v and docker info if applicable.
If you're just making a suggestion, be descriptive, and link to any issues that might be releated as well.
You can delete from this line up.

Panel or Daemon:
Daemon
Version of Panel/Daemon:
5.0
Server's OS:
Linux Ubuntu latest
Your Computer's OS & Browser:
Windows 10

Add Details Below:
getting the following error:
04:04:32.039Z  INFO wings: + ------------------------------------ +
04:04:32.042Z  INFO wings: | Running Pterodactyl Daemon v0.5.0-beta.1    |
04:04:32.043Z  INFO wings: |        https://pterodactyl.io        |
04:04:32.043Z  INFO wings: |  Copyright 2015 - 2017 Dane Everitt  |
04:04:32.043Z  INFO wings: + ------------------------------------ +
04:04:32.043Z  INFO wings: Loading modules, this could take a few seconds.
04:04:32.543Z  INFO wings: Modules loaded, starting Pterodactyl Daemon...
04:04:32.618Z  INFO wings: Configuring user p.dactyl (id: 999) as the owner of all server files.
04:04:32.625Z  INFO wings: Contacting panel to retrieve a list of currrent Eggs available to the node.
04:04:32.627Z  INFO wings: Checking container networking environment...
04:04:32.640Z  INFO wings: Found network interface for daemon: pterodactyl_nw
04:04:32.640Z  INFO wings: Configuring timezone file location...
04:04:32.640Z  INFO wings: Checking pterodactyl0 interface and setting configuration values.
04:04:32.641Z  INFO wings: Checking gateway for pterodactyl0
04:04:32.654Z  INFO wings: Gateway detected as <IP_ADDRESS> for pterodactyl0.
04:04:32.672Z  INFO wings: Checking current files aganist panel response.
04:04:32.675Z  INFO wings: Attempting to load servers and initialize daemon...
04:04:32.698Z FATAL wings: A fatal error caused the daemon to abort the startup. (additional={})
Error: No service type was passed to the server configuration, unable to select a service.
at Server.initContainer.err (/srv/daemon/src/controllers/server.js:86:29)
at docker.Docker (/srv/daemon/src/controllers/server.js:116:24)
at Object.inspect [as callback] (/srv/daemon/src/controllers/docker.js:90:24)
at /srv/daemon/node_modules/dockerode/lib/container.js:72:12
at Modem.buildPayload (/srv/daemon/node_modules/docker-modem/lib/modem.js:270:7)
at IncomingMessage. (/srv/daemon/node_modules/docker-modem/lib/modem.js:229:14)
at emitNone (events.js:91:20)
at IncomingMessage.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:974:12)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
04:04:32.698Z ERROR wings: You should forcibly quit this process (CTRL+C) and attempt to fix the issue.

Whatever server is throwing that error has an invalid configuration file. I've added a change to show the server UUID in the error, but this isn't a bug.

Turns out this is actually a bug... my bad.


[question] Clarification to the existance of webpack.server.js

Can you provide a bit of context around why the webpack.server.js is needed?

Webpack Hot Module Reloading (webpack.server-watch.js) and 2) requiring ES2015/ES7 and non-JS files with Webpack-loaders (Babel and CSS etc).

So these are both for development workflow and wouldn't be used in production, correct?

No, Webpack HMR in point 1 is development only.
Bundling and transforming via Webpack-loaders also happens for the production build. Node doesn't understand require("...css") for example, so building the production build is a must.

Ah, that makes more sense. Thanks for the answers. Much appreciated.


dns/unbound-plus: add DoT support

Finally there's DNS over TLS :)

See https://github.com/opnsense/plugins/issues/1778 for more details :)

@mimugmail @fichtner I know we talked about this some time ago, but maybe we should consider pulling the plugin into core for 20.7,  if more functionality is added it might confuse users more where to find it.

I'll have a look, does this need to come from OPNsense Certificate store?
@AdSchellevis when I started with the code we agreed to start with plugin and there was already Unbound namespace used by statistics page. I have no idea how to migrate to core but I'm the last person against it.

@mimugmail ok, I'll take care of it, the first step shouldn't be a big deal

Merged, thanks!

I use blockerdns.com and nextdns.io
but the forward-addr are not accepted in the field "DNS over TLS Servers".
what don't I see?
My custom options in Unbound look like this:
tls-cert bundle: "/etc/ssl/cert.pem" forward-zone: name: "." forward-addr<EMAIL_ADDRESS>forward-addr<EMAIL_ADDRESS>forward-addr<EMAIL_ADDRESS>forward-addr<EMAIL_ADDRESS>forward-ssl-upstream: yes

the devil is in the details... we build it up step by step


Support mapping random ports

Allow the ability to map to random ports.

+1

+1 here as well.  We have a specific use case for spinning up many ephemeral containers for students in classes mapping to randomly chosen ports

We need to implement something like Kubernetes NodePort. Just randomly pick a port on individual nodes won't work for services like Rancher load balancer which has to listen on the same random port on multiple hosts.
The feature should work as follows: We allow the user to specify on a per-environment basis a range of service ports. Rancher will then assign ports out of the range for mapping service ports.

This sounds a great solution that gives us the best of both worlds.  Looking forward to seeing it implemented...

+1  looking forward to see this implemented..shipyard for now.

+1

+1 We're would really love this for integration with Consul, where services are discovered and registered using the host ip and randomly assigned port.

:+1: to both Consul and random port

@sangeethah

Port range is defined on per environment (project) basis. New API field is introduced for the project:

servicesPortRange (string, optional, default value "49153-65535", CRU permissions)

If service has a port defined under "ports" parameter as "80" or "80/tcp" (with no public port specified), public port will get automatically assigned to the port from environment.servicesPortRange

Port gets assigned to the service on its creation, and the assignment gets removed after service is removed. Once disassociated, the port can be used by other services.

Random port can't have duplicates among other ports generated in random manner.
We don't validate random port against public ports specified by the user explicitly. The assumption is that the servicesPortRange is reserved for random allocation, and user shouldn't specify ports from this range when creates service/standalone instance.
We should test port release by 1) specify smaller port range, say 2 ports. 2) Add 2 services. 3) Remove one of the services. Make sure the port can be released.

Tested with Build from master.
We have support for mapping random ports when public port is not provided in port maps for services.
Issues found when testing this feature is tracked in different issues.

:+1:
When will this be available in the released container images? It does not seem to work in the current v0.56.1 release.

@kolos this was in0.56; please open a separate issue with details about what you think isn't working.

lol, it actually seem to work now when I tested once again, not sure what happened before!


[Issue-324] [WIP] Data loading performance optimization

Code modification done:

Enabled prefetch - code modifications done to make prefetch work according to new code
Moved mdkey processing code to a different thread
Moved copying of file from local to hdfs as soon as file is completed writing

As this branch has been detached after making code open sort...raised another PR for it
https://github.com/HuaweiBigData/carbondata/pull/444


[BUG][IOS] Write not work

PROBLEM
Hi, I installed the plugin but on ios doesn't want to know how to work writing on ble, I can read but not write.
On android instead everything works properly.
I use a ESP32-Dev-Module with ble.
CODES
//First of all, after connecting to the device,
//I read the writing and notification characteristics
//and save them in the appropriate variables

void readCharacteristic(Service service) async {
  await service.characteristics().then((List<Characteristic> res) {
    res.forEach((item) {
      if (item.isWritableWithResponse) {
        singleService = service;
        characteristicWritable = item;
      }
      if (item.isNotifiable) {
        characteristicNotifiable = item;
      }
    });
  });
}

//With this i read the parameter from Esp32-Dev-Module
_read() async {
    device.monitorCharacteristic(singleService.uuid, characteristicNotifiable.uuid).listen((res) {
      setState(() {
        print(utf8.decode(res.value.toList()).toString());
        value = utf8.decode(res.value.toList()).toString();
      });
    });
}

//With this i send A or B for turn on or turn off led
write(int val) async {
    return await characteristicWritable.write(Uint8List.fromList([val]), false);
}

CONSOLE LOG
[CoreBluetooth] API MISUSE: <CBCentralManager: 0x2827fae80> has no restore identifier but the delegate implements the centralManager:willRestoreState: method. Restoring will not be supported
[CoreBluetooth] WARNING: Characteristic <CBCharacteristic: 0x281642580, UUID = 6E400002-B5A3-F393-E0A9-E50E24DCCA9E, properties = 0x8, value = (null), notifying = NO> does not specify the “Write Without Response” property - ignoring response-less write

FLUTTER DOCTOR [MAC]
[✓] Flutter (Channel stable, v1.17.5, on Mac OS X 10.15.5 19F101, locale it)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
[✓] Android Studio (version 4.0)
[✓] VS Code (version 1.46.1)
[✓] Connected device (1 available)
• No issues found!

FLUTTER DOCTOR [WINDOWS]
[√] Flutter (Channel stable, v1.17.5, on Microsoft Windows [Versione 10.0.19041.329], locale it-IT)

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
[√] Android Studio (version 4.0)
[√] VS Code (version 1.46.1)
[√] Connected device (1 available)

• No issues found!

DEVICES TESTED

Oneplus 5T (ANDROID 10) -> Work
Iphone 6 (12.4.6) -> Not Work
Iphone XS (13.5.1) -> Not Work

Hi!
You're checking if it's writeableWithResponse:
    if (item.isWritableWithResponse) {
        singleService = service;
        characteristicWritable = item;
      }

but writing without one:
return await characteristicWritable.write(Uint8List.fromList([val]), false);

Flip the boolean at the end of the line to true.

Hi @mikolak , thank you so much for your quick response, I tested and it works correctly 💪🏽.
But I have a question, why does it still work on android leaving the variable to false?

To be honest I have no idea. 😉
Write with response is the default on Android, so perhaps it falls back to it?
@dariuszseweryn perhaps you know?

Never tried using write that was not supported by a characteristic. Android may use the default or because of some bug in implementation may send a write without response anyway. Or there may be a misshandling in the library itself which did correctly set "no response"?


Load currency exchange rate

Load currency exchange rate
Designs and Mockups
Acceptance Criteria:

[ ] Requirement

@pdpinch there is a difference between the current currency rate and the saved values on micromasters RC.

AFN (Current: 89, but saved is 90.5)
XOF (Current: 611, but save is 612)
INR (Current: 77.61, but saved is 77.52)
etc

So, instead of fetching from the model, I think we should keep fetching through the exchange rate API as in micromasters.
@rhysyngsun what do you suggest?

@umarmughal824 there's a task in MicroMasters that does that. I'd thought we'd brought it over but if we haven't that would need to be done.


[Back-port branch-1]: HBASE-24112 [RSGroup] Support renaming rsgroup

This pr is for branch-1.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 40s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
prototool
0m  1s
prototool was not available.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 4 new or modified test files.

_ branch-1 Compile Tests _

+0 :ok:
mvndep
1m 23s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
7m 29s
branch-1 passed

+1 :green_heart:
compile
1m 28s
branch-1 passed with JDK v1.8.0_242

+1 :green_heart:
compile
1m 39s
branch-1 passed with JDK v1.7.0_252

+1 :green_heart:
checkstyle
4m 40s
branch-1 passed

+1 :green_heart:
shadedjars
3m  4s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  4s
branch-1 passed with JDK v1.8.0_242

+1 :green_heart:
javadoc
1m 15s
branch-1 passed with JDK v1.7.0_252

+0 :ok:
spotbugs
2m 50s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
6m  1s
branch-1 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 58s
the patch passed

+1 :green_heart:
compile
1m 30s
the patch passed with JDK v1.8.0_242

+1 :green_heart:
cc
1m 30s
the patch passed

+1 :green_heart:
javac
1m 30s
the patch passed

+1 :green_heart:
compile
1m 41s
the patch passed with JDK v1.7.0_252

+1 :green_heart:
cc
1m 41s
the patch passed

+1 :green_heart:
javac
1m 41s
the patch passed

-1 :x:
checkstyle
0m 19s
hbase-rsgroup: The patch generated 1 new + 11 unchanged - 0 fixed = 12 total (was 11)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedjars
3m 38s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
6m  1s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
hbaseprotoc
2m 10s
the patch passed

+1 :green_heart:
javadoc
1m  7s
the patch passed with JDK v1.8.0_242

+1 :green_heart:
javadoc
1m 28s
the patch passed with JDK v1.7.0_252

+1 :green_heart:
findbugs
7m 38s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 34s
hbase-protocol in the patch passed.

+1 :green_heart:
unit
131m 41s
hbase-server in the patch passed.

+1 :green_heart:
unit
13m  1s
hbase-rsgroup in the patch passed.

+1 :green_heart:
asflicense
1m 16s
The patch does not generate ASF License warnings.

212m 37s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1467/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1467

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile cc hbaseprotoc prototool

uname
Linux 27b1cda845b5 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1467/out/precommit/personality/provided.sh

git revision
branch-1 / 4b94f2e

Default Java
1.7.0_252

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:1.8.0_242 /usr/lib/jvm/zulu-7-amd64:1.7.0_252

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1467/1/artifact/out/diff-checkstyle-hbase-rsgroup.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1467/1/testReport/

Max. process+thread count
4383 (vs. ulimit of 10000)

modules
C: hbase-protocol hbase-server hbase-rsgroup U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1467/1/console

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
8m 10s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+0 :ok:
prototool
0m  0s
prototool was not available.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 4 new or modified test files.

_ branch-1 Compile Tests _

+0 :ok:
mvndep
1m 25s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
7m 43s
branch-1 passed

+1 :green_heart:
compile
1m 29s
branch-1 passed with JDK v1.8.0_242

+1 :green_heart:
compile
1m 39s
branch-1 passed with JDK v1.7.0_252

+1 :green_heart:
checkstyle
4m 43s
branch-1 passed

+1 :green_heart:
shadedjars
3m  1s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  3s
branch-1 passed with JDK v1.8.0_242

+1 :green_heart:
javadoc
1m 14s
branch-1 passed with JDK v1.7.0_252

+0 :ok:
spotbugs
2m 45s
Used deprecated FindBugs config; considering switching to SpotBugs.

-1 :x:
findbugs
2m 42s
hbase-server in branch-1 has 1 extant findbugs warnings.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 18s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m  7s
the patch passed

+1 :green_heart:
compile
1m 26s
the patch passed with JDK v1.8.0_242

+1 :green_heart:
cc
1m 26s
the patch passed

+1 :green_heart:
javac
1m 26s
the patch passed

+1 :green_heart:
compile
1m 34s
the patch passed with JDK v1.7.0_252

+1 :green_heart:
cc
1m 34s
the patch passed

+1 :green_heart:
javac
1m 34s
the patch passed

+1 :green_heart:
checkstyle
4m 18s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedjars
2m 49s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
4m 50s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2.

+1 :green_heart:
hbaseprotoc
1m 46s
the patch passed

+1 :green_heart:
javadoc
0m 57s
the patch passed with JDK v1.8.0_242

+1 :green_heart:
javadoc
1m 14s
the patch passed with JDK v1.7.0_252

+1 :green_heart:
findbugs
6m 10s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 28s
hbase-protocol in the patch passed.

+1 :green_heart:
unit
128m 43s
hbase-server in the patch passed.

+1 :green_heart:
unit
12m 19s
hbase-rsgroup in the patch passed.

+1 :green_heart:
asflicense
1m 25s
The patch does not generate ASF License warnings.

210m 46s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1467/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1467

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile cc hbaseprotoc prototool

uname
Linux 3b5f6cb925af 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1467/out/precommit/personality/provided.sh

git revision
branch-1 / 7b12709

Default Java
1.7.0_252

Multi-JDK versions
/usr/lib/jvm/zulu-8-amd64:1.8.0_242 /usr/lib/jvm/zulu-7-amd64:1.7.0_252

findbugs
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1467/2/artifact/out/branch-findbugs-hbase-server-warnings.html

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1467/2/testReport/

Max. process+thread count
4181 (vs. ulimit of 10000)

modules
C: hbase-protocol hbase-server hbase-rsgroup U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1467/2/console

versions
git=1.9.1 maven=3.0.5 findbugs=3.0.1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

The findbug warning is not related to this branch, let's commit first.


Making it 100X faster

Could you suggest how it can be made much faster?

You could change CAPTURE_DELAY to 0: https://github.com/mrcoles/full-page-screen-capture-chrome-extension/blob/master/page.js#L2
The delay exists because a number of things happen during scroll that if captured immediately might end up with unintended results in the final capture.


Enable Bitcode

Bitcode is enabled by default in Xcode 7, and the Xcode 7.0 release notes say that

Apps that include incorrectly-built bitcode in frameworks and libraries are rejected by the App Store. If you are a provider of framework and library products for iOS, watchOS, and tvOS platforms, your products must include full bitcode content. The Xcode 7 build system defaults include enabling the Enable Bitcode build setting, but standard Debug or Release builds do not include the full bitcode content in the built framework and library products.

With this release note it is quite clear that at some point in the future Apple will start to enforce the use of Bitcode, so it might be a good idea to adopt Bitcode while it's still optional instead of waiting until I am forced to do so.
Main problem: Third party libraries need to support Bitcode, too.

The Apple docs say that Bitcode is part of the "App Thinning" concept. The document mentions that Bitcode is already mandatory for watchOS and tvOS.

Cf. this SO answer.

The previous 4 comments are wrong - those commits all reference the wrong issue in their commit comment. The correct issue to reference would have been #323.


Code Not Running

Namespace name "Passenger" couldn't be found. I went in to Project settings and copied the settings under Passenger mover not working. Still won't run, help!

hey i just downloaded the project and tried it out, seems to be working on my end - can you provide more details? perhaps what version of unity you are using?

the version above is what I've tested it on

I didn't download the protect just copied the assets so that may be the issue, thanks!

yeah you have to be careful with the way you work with unity, it needs to build correctly - closing the issue for now!


Add Solution of LeetCode problem 206

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
It will provide the optimized solution for the problem 206
Use Case
It will provide the optimized solution for the problem 206
Benefits
No response
Add ScreenShots
No response
Priority
Medium
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@Saksham2k3s complete task otherwise I will close it.


Salt (Next) Legacy theme

EOS: Legacy theme tested and released to Salt (Next) Figma library

Due to unforeseen theme tasks (tokens for #3325 , #3535, #3310 ) I haven't been able to start this task within the current sprint. However, I have been able to give it some thought and I know how the issue can be resolved. It's a sizeable piece of work, but it should be achievable within 1-2 sprints including QA testing.

@pseys to rescope to separate pieces of work (and create relevant new issues) + identify which will be completed in this sprint.

Rescoping into 3 parts:

Create variables library containing Salt-current foundation colours published locally
Create variables library containing Salt-current palette tokens published locally
Add Mode options to Characteristics variables
-- Salt Legacy light
-- Salt Legacy dark
-- Salt Next

The proposed approach to enable Salt legacy theme within the Salt Next variables library is as follows:

Map legacy color palette to variables and publish to Salt team only
Map legacy palette level tokens to variables using the legacy color palette variables and publish to Salt team only
Connect legacy palette variables to characteristics within the Salt Next Styles Library

The last task will come with conditions:

The characteristic variables will need modes applied; Salt Next and Salt Legacy (TBC)
Each characteristic variable mode will need to be mapped to a different set of palette variables – the Salt Next characteristics are already aligned to Accent / Mode in the styles library. Salt Legacy will need to map to a 'Mode' only switch, either in the same file or from a different library (TBC)
When creating a new design, components will default to Salt Next, but designers will have the ability to toggle to Salt Legacy if they wish, however, they will have to set mode separately


Build in mechanism to state files to reclaim space

HDF5 doesn't (yet) reclaim space from deleted nodes. Therefore, in principle TreantFiles will slowly grow if enough universe definitions / selections are added/replaced. We need to assess how big a problem this is, and what the best solution is for "cleaning" state files that have this potential for bloat.

This isn't appropriate for Treants or Groups, since they don't require adding and deleting tables. Advise moving this to MDSynthesis since that's where the problem appears. Also, it seems that in the upcoming release of the HDF5 library, there should be a mechanism for reclaiming space from deleted nodes.


feat: transaction screen

Closes #38

When the transaction fee is too low, it doesn't show the amount. It should show 0.000000001. Example txId: 0x755fecd0059b835efbcd0e647590c38f87b95ca062ec978f28a085042c05e3a9

Also, it's possible to show how much has been sent or received in any transaction is possible to cross the InputCoins with the Output of type Change. Ex. txId: 0x18617ccc580478214175c4daba11903df93a66a94aada773e80411ed06b6ade7


Ecr docker v2

Switch to using tags rather than registries to distinguish between images.

Looks like you kept on working from your local branch, instead of creating a new branch off of master?


Error during deployment with current git and v211

Hi,
today I tried to deploy CF with the current manifest. After configuring the manifest
./generate_deployment_manifest vsphere cf-stub.yml > cf-deployment.yml

And starting the deploy with bosh deploy, I always get:
 Started preparing configuration > Binding configuration. Failed: Error filling in template `agent_ctl.sh.erb' for `uaa_z1/0' (line 31: undefined method `tr' for ["uaa", {}]:Array) (00:00:01)

Error 100: Error filling in template `agent_ctl.sh.erb' for `uaa_z1/0' (line 31: undefined method `tr' for ["uaa", {}]:Array)

Which seems to be a problem according to the diego part: https://github.com/cloudfoundry-incubator/diego-release/issues/60
Question is, how do I overcome this error?

Hi @jhiemer:
If you are deploying cf-release v211, you should also check out the v211 tag of the cf-release repo to generate the manifests:
$ # from cf-release directory
$ git fetch origin
$ git co v211
$ bosh upload release releases/cf-211.yml
$ ./generate_deployment_manifest vsphere cf-stub.yml > cf-deployment.yml
$ bosh -d cf-deployment.yml deploy

Yes, thanks forgot that. My bad. :-(

Glad to help!


RISON Operation

Is your feature request related to a problem? Please describe.
No problem, just a popular new library
Describe the solution you'd like
Add Rison encide/decode operations
https://observablehq.com/@nyurik/rison-online-decoder-encoder
https://github.com/Nanonid/rison/tree/master/js

RISON is now supported.

Well, almost. RISON Decode operation is broken. The "decode option" dropdown contains 3 undefined options, and makes it unusable. Replacing l.31 type: "editableOption", with type: "option", should do the trick.


'charmap' codec can't decode

Hi All,
while starting to use organize I will setup my rules before execute it on productive files.
Therefore I started to set up a easy config file:
rules:
  - folders: ~/tmp_doc-test
    subfolders: false
    filters:
      - extension: pdf
      - filecontent: "Entgeltbescheinigung"
    actions:
      - echo: "Found PDF!"
      - copy: "~/tmp_doc-test/sortiert/Lohnzettel/"

And execute it as usual:
organize run

For some files i face Following issues:
  File BWG.pdf:
    - (FileContent) ERROR! 'charmap' codec can't decode byte 0x9d in position 9796: character maps to <undefined>

I tried to resolve this issue but i have no Idea about the reason.
First of all I was thinking that's because the files charset is of type binary:
file -i BWG.pdf
BWG.pdf: application/pdf; charset=binary

But I have also other PDF files with charset binary
So I'm completely out of ideas.
Someone of you has any idea?

organize uses textract under the hood. So you might check the output of:
textract file.pdf

You can also try installing another parser which is supported by textract:
pip install pdftotext

Please try again with the latest version, which supports exiftool by default. Should be good now!


Hot reload and hot restart is not update app after changes in code

The hot reload and hot restart is not update app after change in my code. After exec flutter run, I make change in a simple text line and press R in windows terminal (power shell). The log in console report the change in code but nothing happens in my app. I need stop the process and start again to see my app changed with my new code.
`import 'package:flutter/material.dart';
void main() {
runApp(const MyApp());
}
class MyApp extends StatelessWidget {
const MyApp({super.key});
@override
Widget build(BuildContext context) {
return MaterialApp(
title: 'Flutter Demo',
theme: ThemeData(
colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
useMaterial3: true,
),
home: const MyHomePage(title: 'Flutter Demo Home Pagex'),
);
}
}
class MyHomePage extends StatefulWidget {
const MyHomePage({super.key, required this.title});
final String title;
@override
State createState() => _MyHomePageState();
}
class _MyHomePageState extends State {
int _counter = 0;
void _incrementCounter() {
setState(() {
_counter++;
});
}
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(
backgroundColor: Theme.of(context).colorScheme.inversePrimary,
title: Text(widget.title),
),
body: Center(
child: Column(
mainAxisAlignment: MainAxisAlignment.center,
children: [
const Text(
'You have pushed the button this many times:',
),
Text(
'$_counter',
style: Theme.of(context).textTheme.headlineMedium,
),
],
),
),
floatingActionButton: FloatingActionButton(
onPressed: _incrementCounter,
tooltip: 'Increment',
child: const Icon(Icons.add),
), // This trailing comma makes auto-formatting nicer for build methods.
);
}
}
`
`PS C:\Users\Ivaldo\test> flutter run
Connected devices:
Windows (desktop) • windows • windows-x64    • Microsoft Windows [versÆo 10.0.22631.3374]
Chrome (web)      • chrome  • web-javascript • Google Chrome 123.0.6312.88
Edge (web)        • edge    • web-javascript • Microsoft Edge 123.0.2420.81
[1]: Windows (windows)
[2]: Chrome (chrome)
[3]: Edge (edge)
Please choose one (or "q" to quit): 1
Launching lib\main.dart on Windows in debug mode...
Building Windows application...                                     9,3s
✓  Built build\windows\x64\runner\Debug\test.exe.
Syncing files to device Windows...                                  79ms
Flutter run key commands.
r Hot reload. 🔥🔥🔥
R Hot restart.
h List all available interactive commands.
d Detach (terminate "flutter run" but leave application running).
c Clear the screen
q Quit (terminate the application on the device).
A Dart VM Service on Windows is available at: http://<IP_ADDRESS>:55380/rFQV_6GCLCg=/
The Flutter DevTools debugger and profiler on Windows is available at:
http://<IP_ADDRESS>:9106?uri=http://<IP_ADDRESS>:55380/rFQV_6GCLCg=/
Performing hot reload...
Reloaded 0 libraries in 132ms (compile: 13 ms, reload: 0 ms, reassemble: 48 ms).
Performing hot restart...
Restarted application in 284ms.
Performing hot restart...
Restarted application in 310ms.
Performing hot reload...
Reloaded 0 libraries in 110ms (compile: 8 ms, reload: 0 ms, reassemble: 57 ms).
Deseja finalizar o arquivo em lotes (S/N)? s
PS C:\Users\Ivaldo\test> flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.19.5, on Microsoft Windows [versÆo 10.0.22631.3374], locale pt-BR)
[✓] Windows Version (Installed version of Windows is version 10 or higher)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✓] Chrome - develop for the web
[✓] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.9.5)
[✓] Android Studio (version 2023.2)
[✓] VS Code (version 1.88.0)
[✓] Connected device (3 available)
[✓] Network resources
`

i have a same issue  for this

@ivaldo
What IDE are you using (VSCode or AS) ?
If you run your app directly through command line (outside of IDE) and then try to hot restart, does it work ?

This is my environment
C:\Windows\System32>flutter doctor -v
[√] Flutter (Channel stable, 3.19.5, on Microsoft Windows [versÆo 10.0.22631.3374], locale pt-BR)
    • Flutter version 3.19.5 on channel stable at C:\Users\Ivaldo\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 300451adae (8 days ago), 2024-03-27 21:54:07 -0500
    • Engine revision e76c956498
    • Dart version 3.3.3
    • DevTools version 2.31.1

[√] Windows Version (Installed version of Windows is version 10 or higher)

[√] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at C:\Users\Ivaldo\AppData\Local\Android\sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: C:\Program Files\Android\Android Studio\jbr\bin\java
    • Java version OpenJDK Runtime Environment (build 17.0.9+0--11185874)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.9.5)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
    • Visual Studio Community 2022 version 17.9.34723.18
    • Windows 10 SDK version 10.0.22621.0

[√] Android Studio (version 2023.2)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.9+0--11185874)

[√] VS Code (version 1.88.0)
    • VS Code at C:\Users\Ivaldo\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension can be installed from:
       https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [versÆo 10.0.22631.3374]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 123.0.6312.88
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 123.0.2420.81

[√] Network resources
    • All expected network resources are available.

• No issues found!

darshankawar commented 3 hours ago
Hello, first of all, thank you very much for noticing my issue. I'm not using IDEs. Just a text editor and the Windows CMD.

I have the impression that ADB.exe is locking my folder c:\users\ivaldo\apptest. When trying to rename the folder, Windows says it's in use. When I end the ADB.exe process in Task Manager, I can rename the folder.
ADB version
'''
C:\Users\Ivaldo\AppData\Local\Android\Sdk\platform-tools>adb.exe --version
Android Debug Bridge version 1.0.41
Version 35.0.1-11580240
Installed as C:\Users\Ivaldo\AppData\Local\Android\Sdk\platform-tools\adb.exe
Running on Windows 10.0.22631
'''

my folder c:\users\ivaldo\apptest

Can you try on different path / location / drive and check if you still get same locking behavior ?


[FancyZones] Allow Windows Snap to process Win + arrow if there isn't a layout applied

When a desktop doesn't have a layout, Win + arrow should default to Windows Snap.
Related to https://github.com/microsoft/PowerToys/issues/192

Related to #7841

Also, consider https://github.com/microsoft/PowerToys/issues/8530#issuecomment-742738751

I don't get why it's necessary to have "Move windows based on their position" checked for it to work.
That kill native windows feature like Win + Up to maximize window. 🤷

Fixed with 0.29, released today.  https://github.com/microsoft/PowerToys/releases/tag/v0.29.0


update perl to 5.22

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Selectors are suggested to take a <two spaces>#<one space>[<expression>] form.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

hello @jakirkham, I believe everything is correct now, could you review this PR for me ?
also ping @tomkinsc and @bgruening, I guess.

Looks good to me! Thanks a lot @rvalieris!

@jakirkham can you please merge this? Thanks a lot and happy new year!

Thanks for the upgrade. Happy New Year.


fix: checking for updates

The GitHub CLI slightly altered how it checks extensions for upgrades. The new way will still log that the extension is up-to-date, but will always log "✓ Would have upgraded extension" when the --dry-run flag is enabled.
See https://github.com/cli/cli/commit/88cae9f5be67989be191cd4a1fe043ddbeafe629
All we need is to slightly alter the message text we're checking for in order to get this working again.

Fixes https://github.com/HaywardMorihara/gh-tidy/issues/44

I get it's not ideal, but short of copying some of the logic from gh to check the latest sha from GitHub I think it works well.


Integrate in the Open MCT visualizer the ground contact forces

Moved from https://github.com/dic-iit/element_software-engineering/issues/59 on August 25 2021.
The idea is to read the ground contact forces from both ports /wholeBodyDynamics/left_leg/cartesianEndEffectorWrench:o and /wholeBodyDynamics/right_leg/cartesianEndEffectorWrench:o and plot them in the OpenMCT web based visualizer.
These two ports and their handling are added to the framework implemented in https://github.com/ami-iit/element_software-engineering/issues/50 and https://github.com/ami-iit/element_software-engineering/issues/64.

Here's an illustration of the force z component of the left leg while the robot was falling or walking:
https://user-images.githubusercontent.com/6848872/132584815-be9459cd-1d1b-4d1f-bcda-04bd5d7effb6.mp4
https://user-images.githubusercontent.com/6848872/132584917-fcc2a8da-7465-4463-8985-4daefe9b4dda.mp4

CC @traversaro


Return SuggestedCorrection for PossibleIncorrectComparisonWithNull

In order to use auto-fixing in VS-Code or via the -Fix switch, it would be nice and technically possible to let the PSPossibleIncorrectComparisonWithNull calculate a correction that could be used for that. I already have a prototype that works
cc @PrzemyslawKlys

Thank you!


🐛 BUG: Inconsistency between dev and prod service bindings

What version of Wrangler are you using?
2.2.1
What operating system are you using?
Mac
Describe the Bug
Using the following pattern, copied verbatim from the docs at https://developers.cloudflare.com/workers/platform/bindings/about-service-bindings/:
    const authResponse = await env.auth.fetch(request.clone());

    if (authResponse.status !== 200) {
      return authResponse;
    }

In production If the request method is POST/PUT/PATCH/DELETE, the cloned request will be cancelled if the response body is not read.  This leads to e.g. browser XHR requests hanging indefinitely with no error message (making it very difficult to debug).
Using wrangler dev --local however works without reading the response. I believe it's accessing the live service binding based on '@opencragmap/ocm-boundary:dev: ▲ [WARNING] This worker is bound to live services: auth (ocm-auth)
'
Not sure where the bug is here - maybe the docs just need updating, but there's definitely inconsistency between dev and prod.

FWIW turns out the response cannot be returned directly if it's been read. If authentication fails and the response has been read, a  TypeError is thrown:  "Body has already been used. It can only be used once. Use tee() first if you need to read it twice."
Final solution working on dev and prod is:
    const response = await env.auth.fetch(request.clone())
    const authJson = await response.json() // Response must be read, otherwise non-simple requests (PUT etc) will fail
    if (response.status !== 200) {
      // A new response must be constructed to avoid a "Body has already been used" error
      return Response.json(authJson, {
        ... response
      })
    }

Thanks for bringing this up! @mrbbot looks like a difference in behavior between miniflare and the runtime? Would like to hear your thoughts on this.

I'm trying to replicate this issue with a toy example on workers.dev at the moment but I can't so far - no difference between request methods found at all.

@willtemperley can you see if this discrepancy still exists in wrangler dev --experimental-local

I've replicated the issue in a toy example: https://github.com/willtemperley/wrangler-issue-2170
In this example the script fails if the PUT request body is read after it has been cloned (worker0). The logs show the request to mock-auth is being cancelled.
What's strange is this is not exactly the same issue I had in prod. In that case the request to the auth service binding failed with the same error if I didn't read the auth response (for non-GET requests). I wasn't able to replicate that here.
@JacobMGEvans I can't seem to get the service binding to bind in --experimental-local

This should be fixed in wrangler@3, which uses the open source workerd for local mode emulation.


Cannot rename a variable if it is declared in "for each in"

Screencast_20240713_002117.webm
Cannot rename a variable if it is declared in "for each in", but if you rename variable inside the brackets, then it works.

Good find! Thanks. I'll investigate.

Fixed in apache/royale-compiler@6679e22713dacaf9ddcb4fb1fdc8517a78b82006
This fix will be included in a version of vscode-as3mxml after the next Apache Royale version is released.


Release Radar Request

Open Source Project name
moviez
What is your project?
It is a simple site that shows movies and going to work on it much more and created the release just right now.
Version
1.0
Date
December 3 2021
Description of changes
Initial Release
GitHub Repo
https://github.com/codewithpom/moviez
Website
http://moviez-nu.vercel.app/
Link to changelog
https://github.com/codewithpom/moviez/releases/tag/v1.0
Social media
not yet
Anything else to add?
No response

Thanks for submitting your project. We had a lot of projects submitted for the December 2021 Release Radar and we couldn't include them all. Please submit your project again for consideration when you have another major version release and we'd love to consider your project.


Python3.9

When will you migrate to python3.9?

Hello, python 3.9 support has been added in v1.7

Do we say somewhere that we don't support 3.9, or only show support up to 3.8?
I thought I changed everywhere but I assume from this question I didn't.


feat: :sparkles: Add Bitbucket config

@jdoiro3 @felipe-nardon Is it possible to use bitbucket repositories without this plugin? If not, can we get this change merged in somehow?

I have the same issue, I would like to use it for our Bitbucket repositories as well. Can we merged the changes in a smaller release or is there another way without this plugin? Thanks

As a temporary fix in your installation you can probably add these lines in /usr/local/bin/sparse_clone.sh before else:
elif [[ -n  "$BitbucketAcessToken" ]]; then
    url_to_use="${protocol}://x-token-auth:$BitbucketAcessToken@$url_rest"


Attach meta-data to a file? Is this possible?

Hi guys,
first of all: thanks for this great package. So far it has been awesome to hook up to my project. 👍
Now I need to add some meta-data to an image. In my useCase an admin can add avatar-images to users, so I need a place to store WHICH user the admin is uploading the image for. I'd love to do something like $set: { meta: { imageType: 'AVATAR', userId: 'someUserId', .... } }.
Is this possible to do? What is the best place to do this?

I think I found the answer: https://github.com/jalik/jalik-ufs/issues/69. Closed!

@thebarty I am glad you found it. Maybe it is not obvious in the doc.

Yeah - adding a hint to the docs would make it easier for future users 👍


first render

Which OS ?
android
Version
Which versions are you using:

react-native-swiper v1.5.13
react-native v0.55.3

I  have large list. When navigate render slowly. this task 35 not help. Because first render called !. Have 100 page in first render 100 page. And etc

I have same this issues. I have about 7 pages, each page have list data. In first render, it very long about 8 seconds. I think it have issue when render UI.

@navata use InteractionManager or use react-native-swiper-flatlist. I chose option 2

@navata no. Lagre list only use with flatlist


classification heartbeat check

scheduled job to check classifications are being received within a window period and alert via email / honeybadger if not

i've added a config file for this. i plan to test on staging once this PR goes through.


[BD-46] feat: add component generator command

Add a script for generating new components
JIRA:

PAR-617
PAR-610

Thanks for the pull request, @viktorrusakov! I've created OSPR-6355 to keep track of it in JIRA, where we prioritize reviews. Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.

@viktorrusakov 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket: