libgbinder: 1.1.25 -> 1.1.26

Description of changes

libgbinder version increased from 1.1.25 to 1.1.26
libgbinder needed to be updated for Waydroid with the android 11 based image to work on my machine.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Hm, my waydroid install got fixed by latest unstable, without this update, but applying it also didn't seem to break anything, so I'm inclined to approve.
Is there any reason that this isn't to latest version 1.1.27?

It seems that waydroid's other dependencies were updated in unstable, your most likely right that those fixed it and not this. I was just running a custom overlay with updated dependencies and decided to contribute the applicable package that wasn't updated in nixpkgs.
I wasn't aware that 1.1.27 was released when I made this patch, the changelog doesn't seem like there were any breaking changes from 1.1.26 however so it should be safe to update the package and merge that version.


Build error on go1.10

Error message :
github.com/RadhiFadlillah/shiori/assets
assets\assets.go:197:16: too many arguments in call to FS.Mkdir
	have ("golang.org/x/net/context".Context, string, number)
	want (string, os.FileMode)
assets\assets.go:202:16: too many arguments in call to FS.Mkdir
	have ("golang.org/x/net/context".Context, string, number)
	want (string, os.FileMode)
assets\assets.go:207:16: too many arguments in call to FS.Mkdir
	have ("golang.org/x/net/context".Context, string, number)
	want (string, os.FileMode)
assets\assets.go:212:16: too many arguments in call to FS.Mkdir
	have ("golang.org/x/net/context".Context, string, number)
	want (string, os.FileMode)
assets\assets.go:233:22: too many arguments in call to FS.OpenFile
	have ("golang.org/x/net/context".Context, string, int, number)
	want (string, int, os.FileMode)
assets\assets.go:259:22: too many arguments in call to FS.OpenFile
	have ("golang.org/x/net/context".Context, string, int, number)
	want (string, int, os.FileMode)
assets\assets.go:285:22: too many arguments in call to FS.OpenFile
	have ("golang.org/x/net/context".Context, string, int, number)
	want (string, int, os.FileMode)
assets\assets.go:311:22: too many arguments in call to FS.OpenFile
	have ("golang.org/x/net/context".Context, string, int, number)
	want (string, int, os.FileMode)
assets\assets.go:337:22: too many arguments in call to FS.OpenFile
	have ("golang.org/x/net/context".Context, string, int, number)
	want (string, int, os.FileMode)
assets\assets.go:363:22: too many arguments in call to FS.OpenFile
	have ("golang.org/x/net/context".Context, string, int, number)
	want (string, int, os.FileMode)
assets\assets.go:363:22: too many errors
Error: process exited with code 2.

@ding you need to update your copy of x/net/webdav. go get -u golang.org/x/net/webdav
though vendoring of deps may be required


NPM?

Hi,
This looks awesome and I'm interested in using the tool in a site I'm building for my group but I'm not sure as to the easiest way to get started with it. Can you uploaded this (and visibility-polygon-js) to npm? If not, what would the easiest way to implement this be?

Hi, I have never used npm before. I don't think npm would make things easier. To use this library, you just need to copy three javascript files to wherever you are hosting the webpage. The three files are: "battle-map-explorer.js", and the two files in the "external" directory. Take a look at "example-map.html" for an example. To modify/run example-map.html, just download all the files from this project to some directory on your computer. Let me know if you have any questions.


Suggestion - Show MC inventory in the OI GUI and allow dumping items from MC inventory to OI

as per title

Sorry for replying so late. Ill try to work on this soon

No problem, better later than never!


Add support for custom Setting provider implementations

In simple words: we want the ADFS configuration to be editable in the admin, and this feature facilitates this.
Long read:
While looking at the code, I noticed a nice separation of ProviderConfig and Settings, where the former makes use of the instance/sentinel of the latter. The Settings are populated from the Django Settings - all very reasonable.
However, ADFS will be only one of many backends we support, so we want to be able to enable/disable it at runtime and make it possible to configure against Azure or on-premise without having to redeploy. This essentially means that environment variables are out of the question, and we're probabling going to leverage django-solo to store the config.
By implementing our own SoloSettings class, which exposes the same attributes as the Django-settings based on, this should be a drop-in replacement, that gives no extra maintenance burden to django-auth-adfs. This PR only facilitates us to specify our own Settings implementation.
Changes:

Added a Django setting to specify which Settings class to use
Default is the one that was currently used
Added tests + modified existing tests
Added documentation

I'm not against this, but the implementation has a few things that need improvement.

The settings class is a separate setting. This can just as well be another entry in AUTH_ADFS. Else documenting this setting will become very confusing. (entry in AUTH_ADFS vs. top level setting). You can document it, but people don't read manuals in detail.

The class setting should be a string, not a class object. That way it matches with how Django does it throughout their code. But most importantly, allowing a class is very susceptible for circular imports. If your class needs a django setting you end up with this:  Class's module => Django settings module => Settings file => Class's module.

Thanks for the feedback, I'll get both points sorted out.
One thing I'm not a fan of in general is that the module level singleton
forces settings evaluation at start up time, but I guess it still works.
I liked the different top level settings because it decouples nicely, but
it's definitely a pain to document properly.
On Fri, 8 Mar 2019, 20:27 Joris Beckers<EMAIL_ADDRESS>wrote:

I'm not against this, but the implementation has a few things that need
improvement.

The settings class is a separate setting. This can just as well be
another entry in AUTH_ADFS. Else documenting this setting will become
very confusing. (entry in AUTH_ADFS vs. top level setting). You can
document it, but people don't read manuals in detail.
2.
The class setting should be a string, not a class object. That way it
matches with how Django does it throughout their code. But most
importantly, allowing a class is very susceptible for circular imports. If
your class needs a django setting you end up with this: Class's module =>
Django settings module => Settings file => Class's module.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jobec/django-auth-adfs/pull/74#issuecomment-471046997,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFQ01n-LwAL4eaOnKXCn_IcKOMqvieLyks5vUrmPgaJpZM4bhMSf
.

Ideas for easier loading of settings/ADFS properties are always welcome.
One important thing is that the settings must be loaded from the ADFS server once (besides being refreshed every so often) because the backend class is being instantiated on every authentication request.

Yeah, it's a typical 'hard' problem for 3rd party apps. It definitely
warrants its own PR
On Fri, 8 Mar 2019, 20:38 Joris Beckers<EMAIL_ADDRESS>wrote:

Ideas for easier loading of settings/ADFS properties are always welcome.
One important thing is that the settings must be loaded from the ADFS
server once (besides being refreshed every so often) because the backend
class is being instantiated on every authentication request.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jobec/django-auth-adfs/pull/74#issuecomment-471050667,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFQ01vpdjXBxFyGEyhaKVfuIWnAAeF3nks5vUrxGgaJpZM4bhMSf
.

@jobec I've processed the feedback:

no more extra setting, it's added to AUTH_ADFS and the documentation has been updated to reflect that.
Only strings are supported now. It's indeed easy to mess yourself up with circular imports, so probably best to take away the gun to shoot yourself in the foot with.

One important thing is that the settings must be loaded from the ADFS server once (besides being refreshed every so often) because the backend class is being instantiated on every authentication request.

Shouldn't be a problem for this library, and I see you have a test for it. This also mostly seems to concern ProviderConfig via the load_config hook, which is untouched and configured through the settings object, so it's the problem of the one (read: me) implementing a custom Settings class.

@jobec up for re-review :-)


Permission denied on accessing host directory in docker in Centos

Hi,
I have faced this problem, when I mount a host directory to a container:
docker run -it -v /home/share:/home/share centos /bin/bash
and then in container:
cd /home/share
ls
ls: cannot open directory .: Permission denied
But I tried it on  ubuntu system, it works well.
Docker option SELinux are both enabled.
What is the difference between the two system? Can someone give comments?
Thanks
Brs,

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

Can you give the output of id -Z and ls -ldZ /home/share?

@cyphar , the output:
The host：
[root@centos-minion share]# id -Z
unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
[root@centos-minion share]# ls -ldZ /home/share
drwxr-xr-x. root root unconfined_u:object_r:home_root_t:s0 /home/share
The container：
[root@4ccce73bed9d share]# id -Z
id: --context (-Z) works only on an SELinux-enabled kernel
[root@4ccce73bed9d share]# ls -ldZ /home/share
drwxr-xr-x. root root unconfined_u:object_r:home_root_t:s0 /home/share
Thanks!

I think maybe I known the reason now.
The difference is the SELinux.
My ubuntu system disabled the  SELinux. (getenforce = Disabled)
So the docker actually didn't enable the SELinux, so user in the container can access the mounted directory from host.
Thanks !

Yes, this is because of SELinux.
You need to relabel the host path to allow the docker container access.
If you are using Docker 1.7 you can do this by doing either -v /home/share:/home/share:z or -v /home/share:/home/share:Z depending on if you want it to be shared or private.
Closing since this is a non-issue.


configure gh actions to update version

blocked on gh actions be available, though.

i think this is probably a lot of configuration for something that we already have as part of the release process (which is not automated). closing for now.


#BUG#Kata runtime was not connected with network namespace

Description

Steps to reproduce the issue:
1.Using CRI-O 1.11.7 with kata untrusted pod on CentOS7;
2.CNI conf:
{
"cniVersion": "0.3.0",
"name": "kubenet",
"type": "bridge",
"bridge": "cbr0",
"mtu": 1400,
"addIf": "eth0",
"isGateway": true,
"ipMasq": false,
"hairpinMode": false,
"ipam": {
"type": "host-local",
"subnet": "<IP_ADDRESS>/24",
"gateway": "<IP_ADDRESS>",
"routes": [
{ "dst": "<IP_ADDRESS>/0" }
]
}
}
{
"cniVersion": "0.3.0",
"name": "kubenet-loopback",
"type": "loopback"
}
3.The Pod bridge cbr0 was arranged corrected IP address and network is flat.
Describe the results you received:
But kata Pod was found no eth0 and there is no kata_tap in it's network namespace.
Describe the results you expected:
I thought there maybe one step missing, I found no relevant error log in journalctl -u crio.service. The same ENV I tried with CRI-Containerd and It's ok.
Many thanks.
Sincerely yours
Additional information you deem important (e.g. issue happens only occasionally):
Output of crio --version:
1.11.7
(paste your output here)

Additional environment details (AWS, VirtualBox, physical, etc.):

@sboeuf @chavafg PTAL

Can you share your crio.conf?
Also check if you have manage_network_ns_lifecycle set to true in it. Thanks!

Can you share your crio.conf?
Also check if you have manage_network_ns_lifecycle set to true in it. Thanks!

Thank you very much!! problem was solved. Cause I did's see any conf describe from /kubernetes-sigs/cri-o/docs, I didn't know there is a extra configuration when using kata. This manage_network_ns_lifecycle only appears at kata's wiki.
Thank you again!

Closing this, feel free to enhance docs if we need to :)


Introduce critical alert panel in grafana dashboard

Some examples:

[ ] Node/Component failure (compactor/meta/CN/frontend node count drop to 0)
[ ] Recovery rate (recovery triggered too frequently)
[ ] Barrier latency (gap between desired barrier latency and actual barrier latency remains large)
[ ] Foreground error rate (object store/meta store/streaming/batch/user SQL/RPC/... error rates go up and last for long)
[ ] Background error rate (compaction/vacuum error rates go up and last for long)
[ ] Capacity issues (disk/network bandwidth/object store QPS/compaction lags)
[ ] Version/Epoch gap (gaps in committed/safe/pinned epoch, current/checkpoint/safepoint/pinned version)
[ ] Stale SST Count (stale SSTs are not cleaned in time)

error rates go up and last for long

Is this a fixed threshold or do we use a moving average? What is the definition of "long"? Is it 5 minutes, 30 mins, 1 hour? Does this depend on the specific error type/error source?

#9031


Scheduling Rollup Jobs via Apex

I am attempting to write an Apex class that will be run when we refresh our Sandboxes. The class will be responsible for scheduling all of our Apex jobs in the Sandbox (to mimic Production). We have many Declarative roll-up jobs which we would like to schedule in our Sandbox. However, I can't seem to find the names of the schedulable Apex Classes.
Can you provide insight on how we can schedule DLRS jobs to run via Apex? The jobs that get created when you schedule a DLRS record via the GUI must be running a schedulable Apex class. It would help tremendously if we could reference these in our code

Sure that would be dlrs.RollupJob (just one of these) and then dlrs.RollupCalculateJobSchedulable  (however this is not global so you cannot access it). Does the sandbox copy not bring the schedules over?


Version updates (including safety fix)

Fixes build failure due to aiohttp dependency being flagged by safety. Take the opportunity to generally update versions of dependencies.

@masonproffitt has verified updated dependencies should be OK


PAB Simulator "forgets" utxos after an extended amount of time

Summary
I ran my PAB Simulator for 15+ minutes and noticed that the simulated chain index utxo query at my script address returns empty even though there are utxos at that address.
Steps to reproduce the behavior

Start the PAB Simulator with default config.
Pay to some script.
Leave the PAB Simulator running for at least 15-20 minutes (maybe machine-dependent, not sure).
Run the smart contract that logs utxos at the script address:

utxo <- utxosTxOutTxAt myScriptAddress
logInfo @String $ show utxo
Actual Result
The query above returns an empty Map while 'Plutus.PAB.Simulator.currentBalances' returns the correct amount at the script address.
Expected Result
The query should return the utxo with the payment to 'myScriptAddress'.
Describe the approach you would take to fix this
No response
System info
Ubuntu 20.04, plutus-apps commit eba0a570f72502ac650e642011171bfdcca60e89 (December 16).

Can you please retest with the current master?

Retested with the current master. Yep, it is working as expected now. Thanks! I am closing the issue.


HBASE-26117 RIT counts should be configured when cluster is balancing

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

+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.

_ master Compile Tests _

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

+1 :green_heart:
mvninstall
3m 55s
master passed

+1 :green_heart:
compile
4m  4s
master passed

+1 :green_heart:
checkstyle
1m 29s
master passed

+1 :green_heart:
spotbugs
2m 49s
master passed

_ Patch Compile Tests _

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

+1 :green_heart:
mvninstall
3m 44s
the patch passed

+1 :green_heart:
compile
3m 55s
the patch passed

+1 :green_heart:
javac
3m 55s
the patch passed

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

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

+1 :green_heart:
hadoopcheck
18m 24s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1 3.3.0.

+1 :green_heart:
spotbugs
3m  7s
the patch passed

_ Other Tests _

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

52m 27s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3524/1/artifact/yetus-general-check/output/Dockerfile

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile

uname
Linux 65b5d42b91ac 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
dev-support/hbase-personality.sh

git revision
master / 51ed95c0cb

Default Java
AdoptOpenJDK-1.8.0_282-b08

Max. process+thread count
96 (vs. ulimit of 30000)

modules
C: hbase-common hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3524/1/console

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 16s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

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

+1 :green_heart:
mvninstall
3m 51s
master passed

+1 :green_heart:
compile
1m 26s
master passed

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

+1 :green_heart:
javadoc
1m  2s
master passed

_ Patch Compile Tests _

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

+1 :green_heart:
mvninstall
3m 41s
the patch passed

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

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

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

+1 :green_heart:
javadoc
0m 59s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 40s
hbase-common in the patch passed.

+1 :green_heart:
unit
152m 16s
hbase-server in the patch passed.

187m  1s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3524/1/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux b74814a23fb4 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 51ed95c0cb

Default Java
AdoptOpenJDK-1.8.0_282-b08

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3524/1/testReport/

Max. process+thread count
4463 (vs. ulimit of 30000)

modules
C: hbase-common hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3524/1/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

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

+1 :green_heart:
mvninstall
5m  0s
master passed

+1 :green_heart:
compile
1m 44s
master passed

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

+1 :green_heart:
javadoc
1m  8s
master passed

_ Patch Compile Tests _

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

+1 :green_heart:
mvninstall
4m 51s
the patch passed

+1 :green_heart:
compile
1m 45s
the patch passed

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

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

+1 :green_heart:
javadoc
1m  4s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
2m 11s
hbase-common in the patch passed.

+1 :green_heart:
unit
202m 46s
hbase-server in the patch passed.

241m 59s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3524/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 7455e250046c 4.15.0-147-generic #151-Ubuntu SMP Fri Jun 18 19:21:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 51ed95c0cb

Default Java
AdoptOpenJDK-11.0.10+9

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3524/1/testReport/

Max. process+thread count
3329 (vs. ulimit of 30000)

modules
C: hbase-common hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3524/1/console

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

This is hard coded in the past? Oh no.
And maybe it should be a percentage instead of a fixed value? Consider you have 10 regions, maybe 5 is too large but if you have 100k regions, 5 is too small?
WDYT?

This is hard coded in the past? Oh no.
And maybe it should be a percentage instead of a fixed value? Consider you have 10 regions, maybe 5 is too large but if you have 100k regions, 5 is too small?
WDYT?
Thanks，
It’s should be configured！The percentage is complicated for business side I think。

@Apache9
Thanks，
It’s should be configured！The percentage is complicated for business side I think。

Checking the code again, I think here, the hard coded 5 is just for printing logs, not for the actual balancing work.
Could you please confirm this again?
        List<RegionStateNode> toPrint = regionsInTransition;
        int max = 5;
        boolean truncated = false;
        if (regionsInTransition.size() > max) {
          toPrint = regionsInTransition.subList(0, max);
          truncated = true;
        }

        if (!request.isIgnoreRegionsInTransition() || metaInTransition) {
          LOG.info("Not running balancer (ignoreRIT=false" + ", metaRIT=" + metaInTransition +
            ") because " + regionsInTransition.size() + " region(s) in transition: " + toPrint
            + (truncated? "(truncated list)": ""));
          return responseBuilder.build();
        }

The code is like this, we never use the toPrint list in other places.
Thanks.


Fix client template

The client.mustache template is out of date - there have been numerous changes to the upstream repository since this file was forked. This PR brings in the latest changes, and reapplies MX customizations.
I went through the git history and found that this fork was committed on 12/13/2021.
Then I found the common ancestor in openapi-generator. client.mustache as of the date of the fork can be seen here.

I took the latest version of client.mustache and brought back these customizations, resulting in this PR.
For confirmation, I ran the openapi code generator, pointed my code to my local copy, and was able to compile my program successfully.
Fixes #47

@brettmortensen Can you bring this to the attention of the team? Thanks!

Duplicate of #49


receive: fix deadlock on interrupt in routerOnly mode

Hi,
Changes
Currently, the receive component blocks indefinitely in router mode when the Thanos process is interrupted because of unclosed channel.
Verification

start the receive component in router mode
send SIGINT
verify that before the change the process does not exit
verify that after fix process does exit

How to reproduce it
Start the thanos receive component in router mode with the --receive.hashrings-file flag and hit ctrl + c
# Create empty hashring file
$ cat /tmp/test.json
[{}]

$ ./thanos receive --label 'tenant="test"' --receive.hashrings-file=/tmp/test.json
level=info ts=2022-05-07T15:25:40.124359Z caller=receive.go:118 component=receive mode=RouterOnly msg="running receive"
level=info ts=2022-05-07T15:25:40.124404Z caller=options.go:27 component=receive protocol=HTTP msg="disabled TLS, key and cert must be set to enable"
level=info ts=2022-05-07T15:25:40.124493Z caller=receive.go:649 component=receive msg="default tenant data dir already present, not attempting to migrate storage"
level=info ts=2022-05-07T15:25:40.125746Z caller=receive.go:282 component=receive msg="starting receiver"
level=info ts=2022-05-07T15:25:40.1259Z caller=intrumentation.go:75 component=receive msg="changing probe status" status=healthy
level=info ts=2022-05-07T15:25:40.125954Z caller=http.go:73 component=receive service=http/server component=receive msg="listening for requests and metrics" address=<IP_ADDRESS>:10902
level=info ts=2022-05-07T15:25:40.125983Z caller=options.go:27 component=receive protocol=gRPC msg="disabled TLS, key and cert must be set to enable"
level=info ts=2022-05-07T15:25:40.126018Z caller=handler.go:223 component=receive component=receive-handler msg="Start listening for connections" address=<IP_ADDRESS>:19291
level=info ts=2022-05-07T15:25:40.125898Z caller=receive.go:415 component=receive msg="the hashring initialized with config watcher."
level=info ts=2022-05-07T15:25:40.126251Z caller=tls_config.go:195 component=receive service=http/server component=receive msg="TLS is disabled." http2=false
level=info ts=2022-05-07T15:25:40.126442Z caller=handler.go:250 component=receive component=receive-handler msg="Serving plain HTTP" address=<IP_ADDRESS>:19291
level=warn ts=2022-05-07T15:25:40.126404Z caller=intrumentation.go:67 component=receive msg="changing probe status" status=not-ready reason="hashring has changed; server is not ready to receive web requests"
level=info ts=2022-05-07T15:25:40.126554Z caller=receive.go:465 component=receive msg="hashring has changed; server is not ready to receive web requests"
level=info ts=2022-05-07T15:25:40.126574Z caller=receive.go:472 component=receive msg="server has reloaded, ready to start accepting requests"
level=info ts=2022-05-07T15:25:40.126592Z caller=intrumentation.go:56 component=receive msg="changing probe status" status=ready
level=info ts=2022-05-07T15:25:40.127062Z caller=receive.go:369 component=receive msg="listening for StoreAPI and WritableStoreAPI gRPC" address=<IP_ADDRESS>:10901
level=info ts=2022-05-07T15:25:40.127172Z caller=grpc.go:131 component=receive service=gRPC/server component=receive msg="listening for serving gRPC" address=<IP_ADDRESS>:10901
^Clevel=info ts=2022-05-07T15:25:44.542766Z caller=main.go:169 msg="caught signal. Exiting." signal=interrupt
level=warn ts=2022-05-07T15:25:44.542825Z caller=intrumentation.go:67 component=receive msg="changing probe status" status=not-ready reason=null
level=info ts=2022-05-07T15:25:44.542847Z caller=http.go:84 component=receive service=http/server component=receive msg="internal server is shutting down" err=null
level=info ts=2022-05-07T15:25:44.544218Z caller=http.go:103 component=receive service=http/server component=receive msg="internal server is shutdown gracefully" err=null
level=info ts=2022-05-07T15:25:44.544276Z caller=intrumentation.go:81 component=receive msg="changing probe status" status=not-healthy reason=null```

It'd be nice to have a CHANGELOG entry for this. It'd be great if you can add that!

@onprem Thanks for the review, I'm happy as it's my first contribution !

Thanks!


Enabling or disabling nightmode does not appy unless you manually reload page.

In GitLab by @julien1205 on May 2, 2023, 05:09
The DW system option to enable or disable nightmode should force a reload, since it's needed to be applied.

In GitLab by @Asacolips on Sep 21, 2023, 20:26
mentioned in commit 18f4e386025909af42a72798552869d947eb8738


[GetTest] Bump Mockito version constraints

Currently, get_test has set the version constraints for Mockito to ">=3.0.0 <4.0.0". Version 4.1.0 added Fake classes, which we currently depend on, so we're currently unable to use get_test in our project.
Can the version constraints please be updated to (ideally) support the latest Mockito version rather than being a whole major release behind.

:+1:

Fix on get 3.12.1


Deprecate $(H: name) value syntax

Workaround
Write (: name Str "value") or $(> name) "value" instead.
Timeline

Warning in v0.1.6.
Removal in v0.2.0.

https://github.com/fildesh/fildesh/commit/61e0e5feab2c40ca67987aecfeeb59a17c84d802


separator was not removed

Thank you for the script, it was easy to use. However I just try it out and it seem the separators in the .txt still present, there is no error logs pop up in the terminal so I don't know what cause this. On the other note, what is the flag button do?

I think I forgot to put the separators remover in the script. Wait a moment, I will fix this

The remove separator should be added in latest commit

thanks, it works now


Allow Pydantic V2+

For this, I followed this Pydantic Migration Guide and it showed me a quick and easy way to temporarily (though probably not best practice) to allow me and others to use pydantic 2+ with semantic router.
It passes all tests so I assume it would work well while we wait for a more official pydantic v2 migration.
Lmk what you all think.

This wouldn't necessarily close https://github.com/aurelio-labs/semantic-router/issues/77 but is related to it.
Also, for some reason the pytests passed but it couldn't upload it to codecov. I've never used that service so I have no idea how to fix that, but keep that in mind.

Thanks @kdcokenny we will take a look at both pydantic compatibility with v1 and v2, and codecov issue

@kdcokenny tests seem to be passing, but I'm seeing ValidationError when trying to run myself


Too Many errors when adding ignore pattern

See the errors:
I want to ignore missing semicolon, I success to ignore it but it is still counted as error.

Sublime linter settings:
"ignore_match": [
"Missing semicolon",
".debugger.",
".functions within.",
"._is better._in dot.*"
]

+1

This is an error message from the linter. You're suppressing the errors in SL, but you should change the configuration for the linter itself instead so it ignores these cases.


spi init fail in esp32 (IDFGH-9168)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v5.1-dev-1006-g02605f1a31
Operating System used.
Windows
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
PowerShell
Development Kit.
esp32-wroow
Power Supply used.
USB
What is the expected behavior?
spi init
What is the actual behavior?
spi init fail
Steps to reproduce.
spi_bus_config_t buscfg;
  buscfg.miso_io_num = GPIO_NUM_12;
  buscfg.mosi_io_num = GPIO_NUM_13;
  buscfg.sclk_io_num = GPIO_NUM_14;
  buscfg.quadwp_io_num = -1;
  buscfg.quadhd_io_num = -1;
  buscfg.max_transfer_sz = 64;

  // Initialize the SPI bus
  esp_err_t ret = spi_bus_initialize(SPI2_HOST, &buscfg, SPI_DMA_CH_AUTO);
  ESP_ERROR_CHECK(ret);

  spi_device_interface_config_t devcfg;
  devcfg.clock_speed_hz = SPI_MASTER_FREQ_10M; // Clock out at 10 MHz,
  devcfg.mode = 0;    // SPI mode 0
  devcfg.cs_ena_pretrans = 0;
  devcfg.spics_io_num = -1;
  devcfg.queue_size = 7;

  ret = spi_bus_add_device(SPI2_HOST, &devcfg, &spi);
  ESP_ERROR_CHECK(ret);

Debug Logs.
E (372) spi_hal: spi_hal_cal_clock_conf(94): When work in full-duplex mode at frequency > 0.0MHz, device cannot read correct data.
Try to use IOMUX pins to increase the frequency limit, or use the half duplex mode.
Please note the SPI master can only work at divisors of 80MHz, and the driver always tries to find the closest frequency to your configuration.
Specify ``SPI_DEVICE_NO_DUMMY`` to ignore this checking. Then you can output data at higher speed, or read data at your own risk.
E (422) spi_master: spi_bus_add_device(372): assigned clock speed not supported
ESP_ERROR_CHECK failed: esp_err_t 0x106 (ESP_ERR_NOT_SUPPORTED) at 0x400d6851

### More Information.

_No response_

E (373) spi: spi_bus_initialize(766): intr flag not allowed
ESP_ERROR_CHECK failed: esp_err_t 0x102 (ESP_ERR_INVALID_ARG) at 0x400d5c23

with
PS E:\workload\esp\esp-idf> git describe --tags
v5.1-dev-2926-g3df87a91a3

spi_bus_config_t buscfg;

I think this is where introduced the issue. buscfg is not initiated with proper "default" values. You can do that in this way:
spi_bus_config_t buscfg = {};

spi_bus_config_t buscfg;

I think this is where introduced the issue. buscfg is not initiated with proper "default" values. You can do that in this way:
spi_bus_config_t buscfg = {};

yes, it work, thanks


[Feature] [EDT-1472] Add options to control start/stop/end characters

This PR
PR Guidelines

[X] I have read the contribution and PR guidelines

Related tickets

EDT-1472

Screenshots

Engine is ready but waiting for release on the dart barcode lib before creating PR

Jeroen asks to align the SDK methods with the copy that is used: allowLightMarginToggle allowStartStopCharactersToggle
Also the setters should be renamed accordingly

That means that for every terminology for every barcode type we need to add more booleans :/


az aks create: No registered resource provider found for location 'eastus' and API version '2015-11-01-preview' for type 'applicationGateways'.

az feedback auto-generates most of the information requested below, as of CLI version

Describe the bug
No registered resource provider found for location 'eastus' and API version '2015-11-01-preview' for type 'applicationGateways'. The supported api-versions are '2014-12-01-preview, 2015-05-01-preview, 2015-06-15, 2016-03-30, 2016-06-01, 2016-07-01, 2016-08-01, 2016-09-01, 2016-10-01, 2016-11-01, 2016-12-01, 2017-03-01, 2017-04-01, 2017-06-01, 2017-08-01, 2017-09-01, 2017-10-01, 2017-11-01, 2018-01-01, 2018-02-01, 2018-03-01, 2018-04-01, 2018-05-01, 2018-06-01, 2018-07-01, 2018-08-01, 2018-10-01, 2018-11-01, 2018-12-01, 2019-02-01, 2019-04-01, 2019-06-01, 2019-07-01, 2019-08-01, 2019-09-01, 2019-11-01'. The supported locations are 'westus, eastus, northeurope, westeurope, eastasia, southeastasia, northcentralus, southcentralus, centralus, eastus2, japaneast, japanwest, brazilsouth, australiaeast, australiasoutheast, centralindia, southindia, westindia, canadacentral, canadaeast, westcentralus, westus2, ukwest, uksouth, koreacentral, koreasouth, francecentral, australiacentral, southafricanorth, uaenorth, switzerlandnorth, germanywestcentral, norwayeast'.
To Reproduce
az aks create -g $ResourceGroup         --name $ClusterName
-k $AksVersion         --location $Location
--node-count 2         --generate-ssh-keys
--enable-addons monitoring         --workspace-resource-id $WorkSpaceIdUrl
--network-plugin azure         --network-policy azure
--service-cidr <IP_ADDRESS>/16         --dns-service-ip <IP_ADDRESS>
--docker-bridge-address <IP_ADDRESS>/16         --vnet-subnet-id $SubnetId
--service-principal $ServicePrincipal.appId         --client-secret $ServicePrincipal.password
--no-wait
Expected behavior
A cluster to be created
Environment summary
Install Method: apt-get
CLI version (az --version) /
azure-cli                          2.1.0
command-modules-nspkg              2.0.3
core                               2.1.0
nspkg                              3.0.4
telemetry                          1.0.4
Extensions:
azure-firewall                     0.3.0
Python location '/opt/az/bin/python3'
Extensions directory '/home/carlos/.azure/cliextensions'
Python (Linux) 3.6.5 (default, Feb 14 2020, 05:22:53)
[GCC 7.4.0]
OS version #32~~18.04.1-Ubuntu
Shell Type  bash or PowerShell
PowerShell Version
PSVersion                      6.2.4
PSEdition                      Core
GitCommitId                    6.2.4
OS                             Linux 5.3.0-40-generic #32~18.04.1-Ubuntu SMP Mon Feb 3 14:05:59 UTC 2020
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0
Additional context
It used to work, the only think that i can remember that changed was updating some powershell modules (AZ)
Get-Module Az: Script     3.5.0      Az
If I do az network application-gateway list --debug it works, and I get this
...
urllib3.connectionpool : Starting new HTTPS connection (1): management.azure.com:443
urllib3.connectionpool : https://management.azure.com:443 "GET /subscriptions/930c11b0-5e6d-458f-b9e3-f3dda0734110/providers/Microsoft.Network/applicationGateways?api-version=2019-11-01
...

aks

I found the issue. It is my mistake
I was getting $WorkSpaceIdUrl from az group deployment ..... --query .... and the query sometimes brings the app gateway uri (depending on how the deployment happened). Since this was in a pipeline I could not really see that value
I am not sure if you want to close the issue as "user has no clue what it is doing :)" or if you can improve the error message in case you have more users that have no clue what they are doing :)
It is ok to close this.


Use build-in tools with local LLMs models

"It seems we encountered an unexpected error while trying to use the tool. This was the error: 'OPENAI_API_KEY'"
I got this message while trying to use tools. Can you please let me know how to switch into local LLM models.

1: Ensure ollama is installed and running, and is version 0.1.27 or higher:
`
ps aux | grep ollama

ollama      1810 55.4  2.5 291658704 1663360 ?   Ssl  12:56  81:16 /usr/local/bin/ollama serve

ollama -v

ollama version is 0.1.27
`

2: Get the ollama model name
`
ollama list

NAME                         	ID          	SIZE  	MODIFIED
mistral:7b-instruct-v0.2-q8_0	3f321fd2a1c3	7.7 GB	5 days ago
`

3: At top of your python code, before the crewai imports:
os.environ['OPENAI_API_BASE'] = 'http://localhost:11434/v1' os.environ['OPENAI_MODEL_NAME'] = 'mistral:7b-instruct-v0.2-q8_0' os.environ['OPENAI_API_KEY'] = 'NA'
This should work on crewai 0.19

1: Ensure ollama is installed and running, and is version 0.1.27 or higher:
ps aux | grep ollama
ollama      1810 55.4  2.5 291658704 1663360 ?   Ssl  12:56  81:16 /usr/local/bin/ollama serve

ollama -v
ollama version is 0.1.27

2: Get the ollama model name
ollama list
NAME                         	ID          	SIZE  	MODIFIED
mistral:7b-instruct-v0.2-q8_0	3f321fd2a1c3	7.7 GB	5 days ago

3: At top of your python code, before the crewai imports:
os.environ['OPENAI_API_BASE'] = 'http://localhost:11434/v1'
os.environ['OPENAI_MODEL_NAME'] = 'mistral:7b-instruct-v0.2-q8_0'
os.environ['OPENAI_API_KEY'] = 'NA'

This should work on crewai 0.19

Using the latest versions of crewai and crewai-tools.
running ollama run llama2 (llama2:latest)
running the following code

import os
from crewai import Agent, Task, Crew, Process
from crewai_tools import SerperDevTool
from langchain_community.llms import Ollama

# Load environment variables
from dotenv import load_dotenv
load_dotenv()

# You can choose to use a local model through Ollama for example. See https://docs.crewai.com/how-to/LLM-Connections/ for more information.
os.environ["OPENAI_API_BASE"] = 'http://localhost:11434/v1'
os.environ["OPENAI_MODEL_NAME"] ='llama2:latest'  # Adjust based on available model
os.environ["OPENAI_API_KEY"] ='sk-111111111111111111111111111111111111111111111111'
llama2 = Ollama(model="llama2")

search_tool = SerperDevTool()

# Define your agents with roles and goals
researcher = Agent(
  role='Senior Research Analyst',
  goal='Uncover cutting-edge developments in AI and data science',
  backstory="""You work at a leading tech think tank.
  Your expertise lies in identifying emerging trends.
  You have a knack for dissecting complex data and presenting actionable insights.""",
  verbose=True,
  allow_delegation=False,
  tools=[search_tool],
  llm=llama2
)
writer = Agent(
  role='Tech Content Strategist',
  goal='Craft compelling content on tech advancements',
  backstory="""You are a renowned Content Strategist, known for your insightful and engaging articles.
  You transform complex concepts into compelling narratives.""",
  verbose=True,
  allow_delegation=True,
  llm=llama2
)

# Create tasks for your agents
task1 = Task(
  description="""Conduct a comprehensive analysis of the latest advancements in AI in 2024.
  Identify key trends, breakthrough technologies, and potential industry impacts.""",
  expected_output="Full analysis report in bullet points",
  agent=researcher
)

task2 = Task(
  description="""Using the insights provided, develop an engaging blog
  post that highlights the most significant AI advancements.
  Your post should be informative yet accessible, catering to a tech-savvy audience.
  Make it sound cool, avoid complex words so it doesn't sound like AI.""",
  expected_output="Full blog post of at least 4 paragraphs",
  agent=writer
)

# Instantiate your crew with a sequential process
crew = Crew(
  agents=[researcher, writer],
  tasks=[task1, task2],
  verbose=2, # You can set it to 1 or 2 to different logging levels
)

# Get your crew to work!
result = crew.kickoff()

print("######################")
print(result)

I get
(.venv) me@my-mbp-2 crewai_tests % python [crewai_test.py](http://crewai_test.py/)
 [DEBUG]: == Working Agent: Senior Research Analyst
 [INFO]: == Starting Task: Conduct a comprehensive analysis of the latest advancements in AI in 2024.
  Identify key trends, breakthrough technologies, and potential industry impacts.

> Entering new CrewAgentExecutor chain...
Thought: I understand the task at hand and will use the available tools to conduct a comprehensive analysis of the latest advancements in AI in 2024.

Action: Search the internet for "AI trends 2024"
Action Input: {"query": "AI trends 2024"}

Action 'Search the internet for "AI trends 2024"' don't exist, these are the only available Actions: Search the internet: Search the internet(search_query: 'string') - A tool that can be used to semantic search a query from a txt's content.

Thought: I understand the task at hand and will use the available tools to conduct a comprehensive analysis of the latest advancements in AI in 2024.

Action: Search the internet for "AI trends 2024"
Action Input: {"query": "AI trends 2024"}

Action 'Search the internet for "AI trends 2024"' don't exist, these are the only available Actions: Search the internet: Search the internet(search_query: 'string') - A tool that can be used to semantic search a query from a txt's content.

When using local models you must set OPENAI_API_KEY=NA

@lhermoso I haven't seen this:

When using local models you must set OPENAI_API_KEY=NA

Documented anywhere, nor have I been able to find this in the code anywhere. Can you explain where you found this and how you knew to do this?
For context, doing this has not improved my situation of running locally either..

@lhermoso
Ah, the Ollama integration section is what I needed, as I'm using Ollama.
Thanks for bringing this part of the docs to my attention :)

We also need better docs, sorry about that, it's on our radas


Incorrect parsing of badly formatted lattice with 8 entries

As reported at libAtoms/ExtXYZ.jl#12, this file contains a typo in the Lattice and should give an error:
[essswb@mnf144 ExtXYZ]$ cat test.xyz
8
Lattice="5.44 0.0 0.0 0.0 5.44 0.0 0.0 0.05.44" Properties=species:S:1:pos:R:3 Time=0.0
Si        0.00000000      0.00000000      0.00000000
Si        1.36000000      1.36000000      1.36000000
Si        2.72000000      2.72000000      0.00000000
Si        4.08000000      4.08000000      1.36000000
Si        2.72000000      0.00000000      2.72000000
Si        4.08000000      1.36000000      4.08000000
Si        0.00000000      2.72000000      2.72000000
Si        1.36000000      4.08000000      4.08000000

However, it is read successfully but gives a strange cell:
[essswb@mnf144 ExtXYZ]$ python3
Python 3.7.4 (default, Mar 26 2020, 11:57:44)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import extxyz
>>> extxyz.read("test.xyz")
Atoms(symbols='Si8', pbc=True, cell=[[5.44, 0.0, 0.0], [0.0, 5.44, 0.0], [0.0, 0.05, 0.44]])

For this to be the case there must be an error in the parser, or even in the grammar.

This appears to be a bug in the grammar - the quoted whitespace-separated-float element is a Repeat(Regex..., mi=1)), which allows for a repeat without any whitespace, so it parses 0.050.44 as 0.050 followed by .44, I suspect.  These are separated by a wordbreak regex \b. A List(,, delimiter=' ') doesn't seem to work.  What does work for parsing is Sequence(Repeat(Regex(re_float+'\s'), mi=0), Regex(re_float))), but that breaks the C and python tree walking code, in different ways, because there's one additional depth nesting of container tree nodes.


Bible Reading Schedule - Chronological Reading

The Bible schedule in jwpub is awesome! Love the different ones in 12/18/24/36 months.
Could you consider adding the chronological Bible reading? It would be awesome since it allows us to read in the order in which the events occurred.
I'm attaching a pdf with such schedule.
2014-12 Read-Chronological.pdf

Hi @benny-danny
I'm glad you find the project helpful :-)
Now, I have always wanted to make a truly chronological schedule, but due to lack of resources had to exclude those in favor of a pseudo-chronological order (based on time of completion).
As to your attached schedule, did you make it yourself? How precise/correct is it? Do you have it in another format (Excel, CSV, etc.)?
Also, it may need some adjustments? For instance, JW Library doesn't handle parts of verses - "1Chron. 20:1b-3" will need modification. And some days may be "larger" than others - or have you already checked that?

Hi @erykjj
Thanks again for your fast reply.
Regarding your questions, I can answer a few:

As to your attached schedule, did you make it yourself?
No, used from an app made by a brother (used a few years ago) https://play.google.com/store/apps/details?id=com.mres.schedule&pcampaignid=web_share

How precise/correct is it?
Can’t saw for sure, but I’ve used it 2 times about 10 years ago for reading it cover to cover and “looks” precise to me. For example, the “Good News According To…” looks pretty close to that schedule and the one in the appendix A7 from the New World translation

Do you have it in another format (Excel, CSV, etc.)?
No, but if you want I can copy and paste it to a different format. Just let me know what you need.

Also, it may need some adjustments? For instance, JW Library doesn't handle parts of verses - "1Chron. 20:1b-3" will need modification.
Yes, I understand that, but that shouldn’t be an issue for “the reader” since sometimes publications also have 1b or 1a, and they show the complete verse. It’s up to the reader to “divide” the verse.

And some days may be "larger" than others - or have you already checked that?
I’ve followed that schedule 2 times in the past (and also my mom as well). I think it’s well divided for a 12 months schedule, but probably there are days that are a bit “larger” than the other… can’t tell for sure.

Let me know if you need anything else.

Well, how do you feel about taking this into your hands and preparing it for me? To start with, I would need a CSV (or Excel if that's easier) with the scriptures for each day (I don't need the dates, just each day on a separate line). Once I have that, I will do an automatic check for completeness and balance. Then we'll go from there.

Well, how do you feel about taking this into your hands and preparing it for me? To start with, I would need a CSV (or Excel if that's easier) with the scriptures for each day (I don't need the dates, just each day on a separate line). Once I have that, I will do an automatic check for completeness and balance. Then we'll go from there.

Hi! See if this works.
Chronolog Reading.xlsx

Please see your invite to another repo


i18n(fr): update backend/supabase.mdx

Description (required)
Adds changes from #9541 to the French translation of guides/backend/supabase.mdx

Related issues & labels (optional)

Suggested label: i18n

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

fr
guides/backend/supabase.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Add column showing exact escape sequence for each row

This would include the % and hex ASCII value needed to escape each character.

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

ID: 4e990c1d-5b08-0b80-6851-68bd737f9c7b
Version Independent ID: f898e9ad-99e7-5584-4b7e-a808d3f63728
Content: Special Characters to Escape - Visual Studio
Content Source: docs/msbuild/special-characters-to-escape.md
Product: visual-studio-windows
Technology: msbuild
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

@BruceForstall Thanks, Bruce. I believe this is by design, as the main intent is to tell which characters need escaping, vs. providing the list of % and ASCII values. If you would like to open a PR with these improvements, though, I will make sure it gets reviewed. Thanks!


Add support for latest Minecraft version

Mod gives an error when loading in fabric that it doesn't support this version of the game when running in fabric loader 0.16.4 on Minecraft 1.21.1. Also, does this mod turn your camera when you're driving a boat and straif?

i cannot reproduce a crash with and without fabric api on mc 1.21.1, loader 0.16.5, so if you have a crash log i'd like if you could share that...for your second question, it will apply to player passengers in boats but not the driver.


feat(precondition-header): add new precondition-header spectral-style rule

PR summary
This commit introduces the new spectral-style
'precondition-header' rule. This rule checks operations
with 412 response defined, to make sure it supports
conditional header.
Signed-off-by: Norbert Biczo<EMAIL_ADDRESS>PR Checklist
General checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)
[x] Dependencies have been updated as needed
[x] .secrets.baseline updated as needed?

Checklist for adding a new validation rule:

[x] Added new validation rule definition (packages/ruleset/src/rules/*.js, index.js)
[x] If necessary, added new validation rule implementation (packages/ruleset/src/functions/*.js, updated index.js)
[x] Added new rule to default configuration (packages/ruleset/src/ibm-oas.js)
[x] Added tests for new rule (packages/ruleset/test/*.test.js)
[x] Added docs for new rule (docs/ibm-cloud-rules.md)

Checklist for removing an old validation rule:

[ ] Removed old rule implementation (packages/validator/src/plugins/validation/*.js)
[ ] Removed or adjusted testcases (packages/validator/test)
[ ] Updated default configuration to deprecate old rule (packages/validator/src/.defaultsForValidator.js)
[ ] Removed docs of old rule (docs/ibm-legacy-rules.md)

@padamstx First off, thanks for the docs improvements! :)
Originally I started to implement this check in the response-status-codes rule, but that only has a warning severity while this one (from my understanding) should yield an error. Anyway, I'm open for any changes, let's discuss.

Originally I started to implement this check in the response-status-codes rule, but that only has warning severity while this one (from my understanding) should yield an error.

Yeah, that's true.  But to be honest, I don't know that it makes THAT much of a difference whether it's an error or warning.   Yes, it would mean that a violation of this guideline (if implemented as part of response-status-codes) would NOT cause a "bad result" when running the generator if it returns a warning instead of an error.  But users could modify the severity of the response-status-codes rule if it was that important.
My opinion (fwiw) is that the benefit of combining it all in response-status-codes slightly outweighs the negative of making it a warning.   @hudlow what's your take on this?

This may not be a popular opinion, but I do not like big rules with generic categories of problems. In some cases (like pagination style) the benefits may be really significant (because of the implementation and performance efficiencies of doing various heuristics once for an operation versus every time), but in my view, this is a very neatly scoped rule, and response-status-codes may actually merit being broken up.
I generally don't like the idea of increasing the friction for a user to turn off rules in a granular way (often because of some legacy compatibility considerations for their API).
But maybe I'm missing something that would make having hundreds of rules versus dozens (the direction I'm proposing we go) burdensome for us or for our users?
In any case, it seems like we should try to establish some sort of general policy for making this decision rather than it being arbitrary per enforcement point.

I'm inclined to agree with @hudlow on that point, I think I've seen the benefit of more granular customization for users even though it's more files to maintain. More files can mean some easier maintenance of individual bits of code though. And more rules doesn't mean more clutter from the users perspective, they just see the rules that pop up in their output and decide if they want to turn them off or not.
So for this rule, I think we can leave it as its own, configurable rule.

:tada: This PR is included in version 0.38.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 0.89.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


[Feature Request][Kernel] Add utility APIs to get the file status and physical data schema from the scan state

Feature request
Which Delta project/connector is this regarding?

[ ] Spark
[ ] Standalone
[ ] Flink
[ ] Kernel
[ ] Other (fill in here)

Overview
Followup from PR.
Basically, we need utility APIs to get the physical data schema (schema of the Parquet table) from the scan state.  Otherwise, the connector needs to know the details of the scan state and extract it. In the future for any changes in the scan state contents, the connector code may need to be updated.
Currently, the physical data schema is the same for all scan files in a query. There is also a discussion of can the schema change per-file.
Motivation

Further details

Willingness to contribute
The Delta Lake Community encourages new feature contributions. Would you or another member of your organization be willing to contribute an implementation of this feature?

[ ] Yes. I can contribute this feature independently.
[ ] Yes. I would be willing to contribute this feature with guidance from the Delta Lake community.
[ ] No. I cannot contribute this feature at this time.

Currently the utility methods are private in InternalScanUtils. We need to make them public.


Support for cyclical graphs

If A->B and B->A, one of these needs to be the start point when evaluating the graph. But what does the input port of the start node get when it has an edge from the output port of the not yet run node?
One option is to define a "default_value" on one of the input ports and the graph can be "snipped" there...
Work on this in progress here: https://github.com/ModECI/MDF/tree/cyclic_graphs

Potential extension for cyclical graphs: add parameter cycle_default_value - the default value only to use when it's in a cycle, not standalone.

@pgleeson in addition to this:
snippet from src/modeci_mdf/execution_engine.py
def init(self, node: Node, verbose: Optional[bool] = False):
self.verbose = verbose
self.node = node
self.evaluable_inputs = {}
self.evaluable_parameters = OrderedDict()
self.evaluable_functions = OrderedDict()
    self.evaluable_outputs = {}

Can using OrderedDict()  be the reason for the existing constraint?

Not really. It's basically that one of the nodes in a cycle (e.g. A->B->C->A) needs to be flagged as "this is the one to start evaluating the nodes at". We will do this by stating that an input node has a default value, and that this can be used to start the evaluation, e.g. if A has a default value, you don't have the problem that you first need to evaluate the output of C, but before that the output of B, but before that A...


Put core subroutines into modules

@pazathoth do you think we can pull this through and avoid the array temporaries altogether?

@pazathoth do you think we can pull this through and avoid the array temporaries altogether?

It should be straightforward, you just have to use field etc. in all “client” codes. If something doesn't work, it's likely a bug hidden by the lack of an interface.


Add Retry system.

Allow retry on CI fails and when check to the mergeable state.
Closes #5
cc @shaikatz

@shaikatz You can try the docker image of this PR with the tag feature_retry
For now, I'm thinking of adding more options for the new retry.

docker: Error response from daemon: manifest for testcafe/testcafe:feature_retry not found.

Using the feature for few days looks like it work as expected, I can also propose some more modifications to the flow but for now maybe we can merge this PR?

I will try to move on that tonight.

@shaikatz I have change the way to configure the retry:
    --retry                      Merge retry configuration.                                              (default "false")
    --retry.interval             Time between retry.                                                     (default "1m0s")
    --retry.number               Number of retry before failed.                                          (default "0")
    --retry.on-mergeable         Retry on PR mergeable state (GitHub information).                       (default "false")
    --retry.on-statuses          Retry on GitHub checks (aka statuses).                                  (default "false")

Now you must define --retry.on-mergeable=true and/or --retry.on-statuses=true.


Add a Gitter chat badge to README.md

criteo/biggraphite now has a Chat Room on Gitter
@unbrice has just created a chat room. You can visit it here: https://gitter.im/criteo/biggraphite.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

This change is

Coverage remained the same at 93.408% when pulling bb2d233a1ca58733cc4ded8f05de6756c9cd38d2 on gitter-badger:gitter-badge into c7d6b03fe329a38b519ed97e5df62d89b4e690a1 on criteo:master.

Review status: 0 of 1 files reviewed at latest revision, 1 unresolved discussion.

README.md, line 8 [r1] (raw file):

============

[![Join the chat at https://gitter.im/criteo/biggraphite](https://badges.gitter.im/criteo/biggraphite.svg)](https://gitter.im/criteo/biggraphite?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)

Maybe  rebase on https://reviewable.io/reviews/criteo/biggraphite/28#- and put that in "contact" ?

Comments from Reviewable

Previously, coveralls wrote…
>
> [![Coverage Status](https://coveralls.io/builds/6432501/badge)](https://coveralls.io/builds/6432501)
>
> Coverage remained the same at 93.408% when pulling **bb2d233a1ca58733cc4ded8f05de6756c9cd38d2 on gitter-badger:gitter-badge** into **c7d6b03fe329a38b519ed97e5df62d89b4e690a1 on criteo:master**.
>

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable


config(engine): imitate adjust DM source config

What problem does this PR solve?

Issue Number: close #5535
ref #5504
What is changed and how it works?
convert between and call existing functions.
Check List
Tests

Integration test

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
 `None`.

/check-issue-triage-complete

Codecov Report

Merging #5550 (3514ca6) into master (e62fbea) will decrease coverage by 0.1408%.
The diff coverage is 72.3163%.

Flag
Coverage Δ

cdc
61.4967% <ø> (+0.0102%)
:arrow_up:

dm
51.9786% <72.3163%> (+0.0123%)
:arrow_up:

engine
?

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #5550        +/-   ##
================================================
- Coverage   56.3160%   56.1751%   -0.1409%
================================================
  Files           675        530       -145
  Lines         78594      69828      -8766
================================================
- Hits          44261      39226      -5035
+ Misses        30143      26864      -3279
+ Partials       4190       3738       -452

/merge

conversion
/run-dm-integration-test

/merge


MGDOBR-928: Display cloud provider/region information of a Bridge

JIRA:  https://issues.redhat.com/browse/MGDOBR-928
Steps to test it (on chrome):

Open the drawer of smart event instance details.
It will display the Cloud Provider and Cloud Region information of the instance.
Also try to create a new Instance and check the drawer for the same.
If the providers are not available then it will display Cloud Provider and Cloud Region  as "Not available".

@ppadti any updates on my comment ^ ?

Yes, Its done.


Add Input to Array Table Throws error

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Reproduction link
Steps to reproduce

Add Array Table to form
Add Column to the table
Try to add input field in the column

What is expected?
To work
What is actually happening?
react-dom.development.js:10331 Uncaught DOMException: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
at removeChild (https://unpkg.com/react-dom/umd/react-dom.development.js:10331:20)
at unmountHostComponents (https://unpkg.com/react-dom/umd/react-dom.development.js:21326:11)
at commitDeletion (https://unpkg.com/react-dom/umd/react-dom.development.js:21377:7)
at commitMutationEffects (https://unpkg.com/react-dom/umd/react-dom.development.js:23437:13)
at HTMLUnknownElement.callCallback (https://unpkg.com/react-dom/umd/react-dom.development.js:3942:16)
at Object.invokeGuardedCallbackDev (https://unpkg.com/react-dom/umd/react-dom.development.js:3991:18)
at invokeGuardedCallback (https://unpkg.com/react-dom/umd/react-dom.development.js:4053:33)
at commitRootImpl (https://unpkg.com/react-dom/umd/react-dom.development.js:23151:11)
at unstable_runWithPriority (https://unpkg.com/react/umd/react.development.js:2764:14)
at runWithPriority$1 (https://unpkg.com/react-dom/umd/react-dom.development.js:11306:12)
removeChild @ react-dom.development.js:10331
unmountHostComponents @ react-dom.development.js:21326
commitDeletion @ react-dom.development.js:21377
commitMutationEffects @ react-dom.development.js:23437
callCallback @ react-dom.development.js:3942
invokeGuardedCallbackDev @ react-dom.development.js:3991
invokeGuardedCallback @ react-dom.development.js:4053
commitRootImpl @ react-dom.development.js:23151
unstable_runWithPriority @ react.development.js:2764
runWithPriority$1 @ react-dom.development.js:11306
commitRoot @ react-dom.development.js:23020
performSyncWorkOnRoot @ react-dom.development.js:22359
(anonymous) @ react-dom.development.js:11357
unstable_runWithPriority @ react.development.js:2764
runWithPriority$1 @ react-dom.development.js:11306
flushSyncCallbackQueueImpl @ react-dom.development.js:11352
flushSyncCallbackQueue @ react-dom.development.js:11339
scheduleUpdateOnFiber @ react-dom.development.js:21923
dispatchAction @ react-dom.development.js:16169
(anonymous) @ useForceUpdate.js:34
(anonymous) @ useForceUpdate.js:38
(anonymous) @ useObserver.js:41
Tracker.track._scheduler @ tracker.js:36
(anonymous) @ reaction.js:193
<EMAIL_ADDRESS>@ array.js:40
executePendingReactions @ reaction.js:191
batchEnd @ reaction.js:159
(anonymous) @ action.js:8
boundary @ internals.js:88
(anonymous) @ internals.js:102
(anonymous) @ useDragDropEffect.ts:143
../../packages/core/src/models/Workbench.ts.Workbench.eachWorkspace @ Workbench.ts:97
(anonymous) @ useDragDropEffect.ts:119
(anonymous) @ event.ts:168
../../packages/shared/src/subscribable.ts.Subscribable.dispatch @ subscribable.ts:32
../../packages/shared/src/event.ts.EventDriver.dispatch @ event.ts:38
DragDropDriver._this.onMouseUp @ DragDropDriver.ts:51
Show 7 more frames
react_devtools_backend.js:2540 The above error occurred in one of your React components:
at<EMAIL_ADDRESS>(http://<IP_ADDRESS>:3000/playground.c9fc3182c87f8617f8c0.bundle.js:62713:23)
at td
at BodyCell (http://<IP_ADDRESS>:3000/playground.c9fc3182c87f8617f8c0.bundle.js:141957:108)
at zy (https://unpkg.com/antd/dist/antd-with-locales.min.js:23:703806)
at tr
at Zy (https://unpkg.com/antd/dist/antd-with-locales.min.js:23:708373)
at tbody
at tb (https://unpkg.com/antd/dist/antd-with-locales.min.js:23:711019)
at table
at div
at div
at https://unpkg.com/antd/dist/antd-with-locales.min.js:23:720916
at div
at t (https://unpkg.com/antd/dist/antd-with-locales.min.js:23:30118)
at jb (https://unpkg.com/antd/dist/antd-with-locales.min.js:23:721049)
at div
at div
at a (https://unpkg.com/antd/dist/antd-with-locales.min.js:23:549359)
at div
at K2 (https://unpkg.com/antd/dist/antd-with-locales.min.js:23:762794)
at ArrayBase (http://<IP_ADDRESS>:3000/playground.c9fc3182c87f8617f8c0.bundle.js:62708:80)
at div
at wrappedComponent (http://<IP_ADDRESS>:3000/playground.c9fc3182c87f8617f8c0.bundle.js:76647:78)
at div
at div
at div
at div
at BaseItem (http://<IP_ADDRESS>:3000/playground.c9fc3182c87f8617f8c0.bundle.js:65177:23)
at http://<IP_ADDRESS>:3000/playground.c9fc3182c87f8617f8c0.bundle.js:76644:78
at http://<IP_ADDRESS>:3000/playground.c9fc3182c87f8617f8c0.bundle.js:76644:78
at ArrayField (http://<IP_ADDRESS>:3000/playground.c9fc3182c87f8617f8c0.bundle.js:75234:70)
at wrappedComponent (http://<IP_ADDRESS>:3000/playground.c9fc3182c87f8617f8c0.bundle.js:76647:78)
at wrappedComponent (http://<IP_ADDRESS>:3000/playground.c9fc3182c87f8617f8c0.bundle.js:76647:78)
at form
at div
at FormLayout (http://<IP_ADDRESS>:3000/playground.c9fc3182c87f8617f8c0.bundle.js:65438:22)
at http://<IP_ADDRESS>:3000/playground.c9fc3182c87f8617f8c0.bundle.js:76275:27
at FormProvider (http://<IP_ADDRESS>:3000/playground.c9fc3182c87f8617f8c0.bundle.js:75335:89)
at Form (http://<IP_ADDRESS>:3000/playground.c9fc3182c87f8617f8c0.bundle.js:65984:19)
at wrappedComponent (http://<IP_ADDRESS>:3000/playground.c9fc3182c87f8617f8c0.bundle.js:76647:78)
at wrappedComponent (http://<IP_ADDRESS>:3000/playground.c9fc3182c87f8617f8c0.bundle.js:76647:78)
at div
at wrappedComponent (http://<IP_ADDRESS>:3000/playground.c9fc3182c87f8617f8c0.bundle.js:76647:78)
at div
at Viewport (http://<IP_ADDRESS>:3000/playground.c9fc3182c87f8617f8c0.bundle.js:130260:26)
at wrappedComponent (http://<IP_ADDRESS>:3000/playground.c9fc3182c87f8617f8c0.bundle.js:76647:78)
at div
at PCSimulator (http://<IP_ADDRESS>:3000/playground.c9fc3182c87f8617f8c0.bundle.js:133994:26)
at wrappedComponent (http://<IP_ADDRESS>:3000/playground.c9fc3182c87f8617f8c0.bundle.js:76647:78)
at div
at ../../packages/react/src/panels/WorkspacePanel.tsx.exports.WorkspacePanel.Item

Package

The issus is fixed by https://github.com/alibaba/designable/commit/65f08411cac17393eb6520191a035adcd52ef0a9, but not release yet, you can simply copy source and make your own ReactionsSetter.


.gitignore vendor/**

I'm a little unclear on what's going on here. First, we actually have files under vendor/ in the repo. I'm not sure how that works with having that under gitignore. Second, we've moved all of the other go projects away from using vendor. Shouldn't we do the same here, and once that's done, we won't need to gitignore it either, since we won't be creating the directory locally.

Yeah I think we will want to resolve the issue with using vendor in CI before doing this. And additionally, I agree with Scott, we don't want to add it to gitignore, we'd rather just delete it entirely


SQLSTATE=PAERR SQLCODE=8012 Need to call conn() to allocate connection on DbConn first

Describe the bug
When a bunch (north of 5000) queries have run inside the job, the job appears to run out of memory and refuses to create new connections until restarted. Temporary storage of the job also keeps increasing throughout the day. I can only suspect a memory leak.
To Reproduce
Steps to reproduce the behavior:
I have a back-end server implemented with Express.js that runs the entire day and is restarted at night. Normally it works fine, but a couple of days a month, everybody in the company uses the tool it powers at the same time, and it  can receive 10 hits per second. During those busy days, it looks like the job eventually runs out of temporary storage. This appears to be caused by the statements (or the connections?) allocating memory and never deallocating? If this is caused by poor coding from my side, I would like to apologize for wasting your time, I usually stick to RPGLE :-).
I have also included a function that uses idb-pconnector, as there the problem seems to be much worse. This could provide useful clues when figuring out what happens I guess.
const { dbconn, dbstmt, NUMERIC, CHAR, IN, NULL, SQL_ATTR_DBC_SYS_NAMING, SQL_TRUE } = require('idb-connector');
const { DBPool, Statement } = require('idb-pconnector');
const config = require('./config.json');
const pool = new DBPool({
  url: '*LOCAL',
});

async function executeStatement(sqlStatement, bindParams, skipFetch = false, skipSetLibList = false) {
  const connection = new dbconn();
  connection.conn('*LOCAL');

  if (!skipSetLibList) await setLibraryList(connection, config.db2LibList);

  const statement = new dbstmt(connection);

  return new Promise((resolve, reject) => {
    try {
      statement.exec('SET PATH = *LIBL', (out, error) => {
        if (error) {
          reject(error);
          return;
        }
        if (bindParams === null) {
          statement.exec(sqlStatement, (out, error) => {
            if (error) {
              reject(error);
              return;
            }
            resolve(out);
            statement.close();
            connection.disconn();
            connection.close();
          });
        } else {
          let bindings = [];

          for (var i in bindParams) {
            switch (typeof bindParams[i]) {
              case 'number':
                bindings.push([bindParams[i], IN, NUMERIC]);
                break;
              case 'string':
                bindings.push([bindParams[i], IN, CHAR]);
                break;
              case 'object':
                if (bindParams[i] === null) bindings.push([null, IN, NULL]);
                else bindings.push([bindParams[i], IN, CHAR]);
                break;
            }
          }

          statement.prepare(sqlStatement, (error) => {
            if (error) {
              reject(error);
              return;
            }
            statement.bindParameters(bindings, (error) => {
              if (error) {
                reject(error);
                return;
              }
              statement.execute((out, error) => {
                if (error) {
                  reject(error);
                  return;
                }
                if (!skipFetch) {
                  statement.fetchAll((out, error) => {
                    if (error) {
                      reject(error);
                      return;
                    }
                    resolve(out);
                    statement.close();
                    connection.disconn();
                    connection.close();
                  });
                } else {
                  resolve(out);
                  statement.close();
                  connection.disconn();
                  connection.close();
                }
              });
            });
          });
        }
      });
    } catch (error) {
      reject(error);
    }
  });
}

async function setLibraryList(conn, list) {
  await setConnAttr(conn, SQL_ATTR_DBC_SYS_NAMING, SQL_TRUE);

  return new Promise((resolve, reject) => {
    try {
      let changeLibStmt = new dbstmt(conn),
        qcmdexc = 'CALL QSYS2.QCMDEXC(?)',
        // you can set multiple libs
        changeLibParam = `CHGLIBL LIBL(${list.join(' ')})`;

      changeLibStmt.prepare(qcmdexc, (error) => {
        if (error) {
          reject(error);
          return;
        }
        changeLibStmt.bindParam([[changeLibParam, IN, CHAR]], (error) => {
          if (error) {
            reject(error);
            return;
          }
          changeLibStmt.execute((out, error) => {
            if (error) {
              reject(error);
              return;
            }
            changeLibStmt.close();
            resolve(out);
          });
        });
      });
    } catch (error) {
      reject(error);
    }
  });
}

async function setConnAttr(conn, attribute, value) {
  return new Promise((resolve, reject) => {
    try {
      resolve(conn.setConnAttr(attribute, value));
    } catch (error) {
      reject(error);
    }
  });
}

async function executeStatementConnectorP(sqlStatement, bindParams, skipFetch = false, skipSetLibList = false) {
  const conn = pool.attach();
  if (!skipSetLibList) await conn.connection.setLibraryList(config.db2LibList);

  var results;

  let statement = new Statement(conn.connection);
  statement.stmt.asNumber(true);
  await statement.exec('SET PATH = *LIBL'); //TIMESTAMP_ISO8601 UDF in SYSACCPGM

  if (bindParams === null) {
    results = await statement.exec(sqlStatement);
  } else {
    await statement.prepare(sqlStatement);

    let bindings = [];

    for (var i in bindParams) {
      switch (typeof bindParams[i]) {
        case 'number':
          bindings.push([bindParams[i], IN, NUMERIC]);
          break;
        case 'string':
          bindings.push([bindParams[i], IN, CHAR]);
          break;
        case 'object':
          if (bindParams[i] === null) bindings.push([null, IN, NULL]);
          else bindings.push([bindParams[i], IN, CHAR]);
          break;
      }
    }

    await statement.bindParam(bindings);
    await statement.execute();
    if (!skipFetch) results = await statement.fetchAll();
  }

  await statement.close();

  pool.detach(conn);

  return results;
}

async function getStories() {
  const sSql = `
    SELECT
      rTrim(JIRAISSUE)                                      "jiraIssue",
      rTrim(JIRAISSUEID)                                    "jiraIssueId",
      rTrim(JIRAASSIGNEEUSER)                               "jiraAssigneeUser",
      JIRAISSUEDESCRIPTION                                  "jiraIssueDescription",
      JIRAISSUESYSTEM                                       "jiraIssueSystem",
      rTrim(JIRAISSUEVERSION)                               "jiraIssueVersion",
      DEPLOYINSTRUCTIONS                                    "deployInstructions",
      rTrim(DEPLOYINSTRUCTIONSRESPONSIBLE)                  "deployInstructionsResponsible",
      rTrim(DEPLOYINSTRUCTIONSRESPONSIBLEBACKUP)            "deployInstructionsResponsibleBackup",
      DEPLOYINSTRUCTIONSDONE                                "deployInstructionsDone",
      STATUS                                                "status",
      TIMESTAMP_ISO8601(timestamp(UPDATEDATE, UPDATETIME))  "updateTimestamp",
      rTrim(UPDATEUSER)                                     "updateUser"
      FROM sysjse
      order by JIRAISSUEID`;

  const resultSet = await executeStatement(sSql);
  //const resultSet = await executeStatementConnectorP(sSql);

  return resultSet;
}

for (let step = 0; step < 1000; step++) {
  getStories()
    .then((a) => {
      console.log(step + ' OK ');
    })
    .catch((e) => {
      console.error(step + ' ERROR ' + e);
    });
}

//enter to exit
process.stdin.setRawMode(true);
process.stdin.resume();
process.stdin.on('data', process.exit.bind(process, 0));

When ran using idb-connector [await executeStatement(sSql)]:

When ran using idb-pconnector [await executeStatementConnectorP(sSql)]:

My implementation with pconnector uses about 30% more temp storage after completing 1000 statements and runs slightly slower.
When a node job reaches 1200 - 1400 MB of temp storage, it tends to crash on our machine.
Is this caused by poor coding on my side, or is this some sort of memory leak?
Expected behavior
All memory cleaned up after completing a query.
Screenshots
See above.

Node.js version: v12.18.4
idb-connector version: +--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| --<EMAIL_ADDRESS>deduped --<EMAIL_ADDRESS>`--<EMAIL_ADDRESS>deduped
IBM i version: 4 7

Thank you for your time 👍

Revisiting this, I notice I didn't make very clear when "SQLSTATE=PAERR SQLCODE=8012" occurs. When the temp storage reaches 1200 - 1400 MB, usually the job becomes unresponsive, but other times when a query (usually 'SET PATH = *LIBL'") is executed on the first statement after new dbconn() "SQLSTATE=PAERR SQLCODE=8012" occurs. After that point, every query will fail with this error until the job is restarted.

Revisiting this, I notice I didn't make very clear when "SQLSTATE=PAERR SQLCODE=8012" occurs. When the temp storage reaches 1200 - 1400 MB, usually the job becomes unresponsive, but other times when a query (usually 'SET PATH = *LIBL'") is executed on the first statement after new dbconn() "SQLSTATE=PAERR SQLCODE=8012" occurs. After that point, every query will fail with this error until the job is restarted.


No module named 'yt_dlp' ????

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm asking a question and not reporting a bug or requesting a feature
[X] I've looked through the README
[X] I've verified that I'm running yt-dlp version 2023.06.22 (update instructions) or later (specify commit)
[X] I've searched known issues and the bugtracker for similar questions including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Please make sure the question is worded well enough to be understood
I copied and pasted the "Extract audio" snippet under the Embedding examples in the README into a python file, but when I try to run it I keep getting "ModuleNotFoundError: No module named 'yt_dlp'" from the very first line in the snippet (import yt_dlp).
I am on Windows and installed yt-dlp using Chocolatey, but it still says the module can't be found. I also tried restarting in case that would make a difference somehow.
I feel like I am missing something obvious here so I apologize if this is a very stupid question (I'm not really a Python person).
Anyone know how I could be screwing this up?
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>[812cdfa06] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.19045-SP0 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: ffmpeg 6.0-essentials_build-www.gyan.dev (setts), ffprobe 6.0-essentials_build-www.gyan.dev
[debug] Optional libraries: Cryptodome-3.18.0, brotli-1.0.9, certifi-2023.05.07, mutagen-1.46.0, sqlite3-2.6.0, websockets-11.0.3
[debug] Proxy map: {}
[debug] Loaded 1851 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Available version<EMAIL_ADDRESS>Current version<EMAIL_ADDRESS>Current Build Hash: 37e7ffe204309357cfd1388b0e2c782a30e293ddd0f2761a9a8f6afa185b3566
yt-dlp is up to date<EMAIL_ADDRESS>

I am on Windows and installed yt-dlp using Chocolatey

You obviously cannot use the executable as a library! Install using pip of the python you are running

Are you really wanting to embed yt-dlp? Otherwise, just use the command line interface. To extract audio, run yt-dlp URL --extract-audio

I am on Windows and installed yt-dlp using Chocolatey

You obviously cannot use the executable as a library! Install using pip of the python you are running

Ah!! Thank you! I didn't realize that the various installation options resulted in different things - I knew I was missing something obvious!
Got it working now, yea!!


API Enable DataList::sort to support composite field names

4.0 replacement pull request for https://github.com/silverstripe/silverstripe-framework/pull/4611
Pulling to 4.0 means we can remove DataList::getRelation, and modify the method signature on DataQuery::applyRelation. :)

ta!


bug: splitRatio property inside FlutterDeckSlide.split template

Description
I've got a problem using the splitRatio property inside the  FlutterDeckSlide.split template
Steps To Reproduce
Create a FlutterDeckSlide.split template like this:
@override
FlutterDeckSlide build(BuildContext context) {
  return FlutterDeckSlide.split(
    splitRatio: SplitSlideRatio(left: 1,right: 2), // <- this line here
    leftBuilder: (context) {
      return Text('LEFT section');
    },
    rightBuilder: (context) {
      return Text('RIGHT section');
    },
  );
}

Expected Behavior
I expect the property to be recognized and it is possible to create a class of type SplitSlideRatio in which to customize the width of the two columns but I get an error back telling me that:

The method 'SplitSlideRatio' isn't defined for the type 'FlutterWindowManagementSlide'. Try correcting the name to the name of an existing method, or defining a method named 'SplitSlideRatio'.
Type: InvalidType

Additional Info
Tested with:

flutter_deck version 0.5.0 and 0.6.0
Flutter (Channel stable, 3.13.7, on Fedora Linux 38 (KDE Plasma) 6.5.6-200.fc38.x86_64, locale it_IT.UTF-8)
VS Code (version 1.83.1)

Good one! I will take care of it, thanks.

It will be fixed with flutter_deck v0.6.1. Releasing in a minute or two.