Update sbt-pgp to 2.0.0

Updates com.jsuereth:sbt-pgp from 1.1.2 to 2.0.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.jsuereth", artifactId = "sbt-pgp" } ]

labels: semver-major

Codecov Report

Merging #1 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master     #1   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           2      2
  Lines          36     36
  Branches        1      1
=====================================
  Hits           36     36

Continue to review full report at Codecov.

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


grafana: 5.1.1 -> 5.1.2

new release, includes a bugfix for mysql and enables the anonymizeIP setting for google analytics.
Things done

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

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

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: grafana
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: grafana
Partial log (click to expand)
/nix/store/bv5zzv9y0ms25pzlzmf4x86izqmbb9x9-grafana-5.1.2/share/go/src/github.com/grafana/grafana/docker/blocks/graphite1/conf/usr/local/bin/manage.sh: interpreter directive changed from "/bin/bash" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/bash"
/nix/store/bv5zzv9y0ms25pzlzmf4x86izqmbb9x9-grafana-5.1.2/share/go/src/github.com/grafana/grafana/docker/blocks/smtp/bootstrap.sh: interpreter directive changed from "/bin/sh" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/sh"
/nix/store/bv5zzv9y0ms25pzlzmf4x86izqmbb9x9-grafana-5.1.2/share/go/src/github.com/grafana/grafana/docker/debtest/build.sh: interpreter directive changed from "/bin/bash" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/bash"
/nix/store/bv5zzv9y0ms25pzlzmf4x86izqmbb9x9-grafana-5.1.2/share/go/src/github.com/grafana/grafana/docker/buildcontainer/build.sh: interpreter directive changed from "/bin/bash" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/bash"
/nix/store/bv5zzv9y0ms25pzlzmf4x86izqmbb9x9-grafana-5.1.2/share/go/src/github.com/grafana/grafana/docker/buildcontainer/run_circle.sh: interpreter directive changed from "/bin/bash" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/bash"
/nix/store/bv5zzv9y0ms25pzlzmf4x86izqmbb9x9-grafana-5.1.2/share/go/src/github.com/grafana/grafana/docker/buildcontainer/build_circle.sh: interpreter directive changed from "/bin/bash" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/bash"
/nix/store/bv5zzv9y0ms25pzlzmf4x86izqmbb9x9-grafana-5.1.2/share/go/src/github.com/grafana/grafana/docker/create_docker_compose.sh: interpreter directive changed from "/bin/bash" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/bash"
/nix/store/gpy3r9ss5ngfkib8ylx7jzgahq7m0x5b-patch-shebangs.sh: line 22: warning: command substitution: ignored null byte in input
/nix/store/bv5zzv9y0ms25pzlzmf4x86izqmbb9x9-grafana-5.1.2/share/go/src/github.com/grafana/grafana/docs/publish.sh: interpreter directive changed from "/bin/bash" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/bash"
checking for references to /build in /nix/store/bv5zzv9y0ms25pzlzmf4x86izqmbb9x9-grafana-5.1.2...

@GrahamcOfBorg test grafana

Success on x86_64-linux (full log)
Attempted: tests.grafana
Partial log (click to expand)
machine: exit status 1
syncing
machine: running command: sync
machine: exit status 0
test script finished in 58.19s
cleaning up
killing machine (pid 593)
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: Could not remove ctl dir '/build/vde1.ctl': Directory not empty
/nix/store/05ivdka0xv1jxghb0858cf2hk0wwf0v3-vm-test-run-grafana

Success on aarch64-linux (full log)
Attempted: grafana
Partial log (click to expand)
/nix/store/fml43m077n2qa5vgaxjm8s0dkz0xsbd0-grafana-5.1.2/share/go/src/github.com/grafana/grafana/scripts/build/build_container.sh: interpreter directive changed from "/bin/bash" to "/nix/store/a4qslf0yfs44mhnbagarn232sjnckhy0-bash-4.4-p19/bin/bash"
/nix/store/fml43m077n2qa5vgaxjm8s0dkz0xsbd0-grafana-5.1.2/share/go/src/github.com/grafana/grafana/scripts/build/deploy.sh: interpreter directive changed from "/bin/bash" to "/nix/store/a4qslf0yfs44mhnbagarn232sjnckhy0-bash-4.4-p19/bin/bash"
/nix/store/fml43m077n2qa5vgaxjm8s0dkz0xsbd0-grafana-5.1.2/share/go/src/github.com/grafana/grafana/scripts/build/sign_packages.sh: interpreter directive changed from "/bin/bash" to "/nix/store/a4qslf0yfs44mhnbagarn232sjnckhy0-bash-4.4-p19/bin/bash"
/nix/store/fml43m077n2qa5vgaxjm8s0dkz0xsbd0-grafana-5.1.2/share/go/src/github.com/grafana/grafana/scripts/circle-test-backend.sh: interpreter directive changed from "/bin/bash" to "/nix/store/a4qslf0yfs44mhnbagarn232sjnckhy0-bash-4.4-p19/bin/bash"
/nix/store/fml43m077n2qa5vgaxjm8s0dkz0xsbd0-grafana-5.1.2/share/go/src/github.com/grafana/grafana/scripts/circle-test-frontend.sh: interpreter directive changed from "/bin/bash" to "/nix/store/a4qslf0yfs44mhnbagarn232sjnckhy0-bash-4.4-p19/bin/bash"
/nix/store/fml43m077n2qa5vgaxjm8s0dkz0xsbd0-grafana-5.1.2/share/go/src/github.com/grafana/grafana/scripts/import_many_dashboards.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/a4qslf0yfs44mhnbagarn232sjnckhy0-bash-4.4-p19/bin/bash"
/nix/store/fml43m077n2qa5vgaxjm8s0dkz0xsbd0-grafana-5.1.2/share/go/src/github.com/grafana/grafana/scripts/trigger_grafana_packer.sh: interpreter directive changed from "/bin/bash" to "/nix/store/a4qslf0yfs44mhnbagarn232sjnckhy0-bash-4.4-p19/bin/bash"
/nix/store/fml43m077n2qa5vgaxjm8s0dkz0xsbd0-grafana-5.1.2/share/go/src/github.com/grafana/grafana/scripts/trigger_windows_build.sh: interpreter directive changed from "/bin/bash" to "/nix/store/a4qslf0yfs44mhnbagarn232sjnckhy0-bash-4.4-p19/bin/bash"
checking for references to /build in /nix/store/fml43m077n2qa5vgaxjm8s0dkz0xsbd0-grafana-5.1.2...
/nix/store/5y8k4wayklcmwc6jb3jz2ijs7lbzjif8-grafana-5.1.2-bin

Success on aarch64-linux (full log)
Attempted: tests.grafana
Partial log (click to expand)
machine: exit status 1
syncing
machine: running command: sync
machine: exit status 0
test script finished in 21.23s
cleaning up
killing machine (pid 627)
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: Could not remove ctl dir '/build/vde1.ctl': Directory not empty
/nix/store/r68nhxq1af0dwngmgn8jn2r73x702iap-vm-test-run-grafana


Custom parameters/Row data in custom filter logic function

I wanted to know if there is an option to either pass custom parameters to the custom filter logic function or get the row data inside the function.
Expected Behavior
Pass custom parameters, to custom filter logic
Pass the rowData to the custom filter logic function
Current Behavior
Accepts only the column data and filter value

The logic function passes (value, filters) where the value is the value of the cell data being evaluated by the column and the filters are all of your filter options (array). That ought to be enough to create most custom filters. Is there something in particular you're looking to do?

Hey,
Thanks for the reply.
I'm trying to write a custom logic for a specific column based on the value of a different column. Ex : Lets say we have three columns A, B and C and when I want to filter C I want to have two different logic based on the value of A. So If I could the tableData or the rowData that would be great.
Thanks

You have access to the table and row data that you pass into the table, so you could try to manage it yourself and then call up those values in the custom filters.
Adding those options to custom filters for such a specific use case is unlikely to happen any time soon, as keeping state managed within the library is complex and a source of bugs at the moment, so I don't want to expand that out just yet.

I understand, I do have the table data as a whole but not sure how to get the row specific data during filtering, It would be really helpful if there any way to get that in the logic function. Sorry for the trouble


Svgs don't seem to be rendered correctly

I have this svg on the page.

when i download with that lib, the result is

it doesn't happen with images, anyone can help me with that?

@viniciushfr  did you find a solution to this problem? Im facing the same issue
my svg on page

downloaded file

Sorry for the delay in the response.Please check using the newest releases (v1) which has upgraded its dependencies (html2canvas and jspdf). Closing this but feel free to open another issue if the problem then continues.

Images are not rendering in PDF, in my case, I am trying to convert the canvas to PDF. All the text is fine but in place of images getting empty space.


Rename setters/getters/builders for Datastore classes to meet proto conventions

Coverage decreased (-0.1%) to 84.543% when pulling b7a5c2fa7c8efbe6c16e239f5f4faa3f919d5d58 on mziccard:datastore-rename into 513ca7034aca5395ab4e1b7a36899ffa56566af8 on GoogleCloudPlatform:master.

/cc @lesv

Coverage decreased (-0.08%) to 84.593% when pulling 5e999227129c22b9b6eddb86d4660355cb8bedd1 on mziccard:datastore-rename into 513ca7034aca5395ab4e1b7a36899ffa56566af8 on GoogleCloudPlatform:master.


Fix multi download start too many task and the empty files not use in next time download

1.fix that create too many empty files
2.try fix the multi download fails when task more than 100, now use the event to start a new task
I am a newbie here, it is my first-time to use Github. I am learning C# by myself, and not good at it. I try to add code fix my problem I post in Issues #92. Please forgive me if this brings you trouble.
I am sorry, this change has some bugs. If a task fails, it can't start a new task. If a task was canceled, I also can't start  a new one.

That's okay :)


Circlesclock v0.14

Support to display weather in a big form next to the clock and date

Neat, thanks!
If you get a change to add a remove option to Bangle.setUI (see Anton clock) then you could also make the transition from clock->launcher a lot quicker :)


Funtionality to Delete the uploaded image

Hi @thekavikumar , if you want i can add a feature to delete the uploaded image from the gallery.
Thanks

Hey @prateek-1606 , It is already added do check out the website https://gallery-37066.web.app/
If you like to change the UI design of it, you can proceed with that.
For now I'm closing this issue.

@thekavikumar i can't see any option to delete/remove uploaded image in the dashboard.

Oops bro it is not visible due to its color.
Please switch to light mode.


make travis tests great again

Travis fails to build with Python3.4. This PR is an attempt to fix it.

Coverage remained the same at 98.795% when pulling 2ac74f2373d601d9b3f12a706f0ae8f7cfb49a4c on py36 into de5ccf9d0b08b3f86e1c1876a7fd6c73461116e8 on master.

Coverage remained the same at 98.795% when pulling 25a1636c1374131ca620c4ff3d0493e63687064d on py36 into de5ccf9d0b08b3f86e1c1876a7fd6c73461116e8 on master.


onElementRender incorrect documentation

Looks like the onElementRender callback takes two parameters: the Form.IO instance and the element. Also, the documentation should state that the onElementRender handler must return the element to render (if it does not return anything, the form does not render).

Also, looks like npm test isn't set up in master and all the builds are failing.

This no longer applies to the current version of the renderer.


Ethernet crossover connection between 2 ESP32s3 w5500 (IDFGH-14091)

Could you say if it possible. I tried to set on both static IP and run PING on both sides. Currently, ping not working on both sides.
Thanks.

This is not an issue. Please use forum for asking questions next time. Anyway, what do you mean by "Ethernet crossover connection"? Do you mean bridging at L2? If so, here is example: https://github.com/espressif/esp-idf/tree/master/examples/network/bridge.

The idea is to connect two ESP32s3 directly without a router through Ethernet using two W5500 SPI modules.
Current status:

2 ESP with W5500 modules are connected
Used CrossOver cable
RJ45 Green and Yellow LEDs are ON on both sides.

On one side I use a basic ethernet example with some changes in code and receive that log:
I (8356) esp_netif_handlers: eth0 ip: <IP_ADDRESS>, mask: <IP_ADDRESS>, gw: <IP_ADDRESS>
I (8356) eth_example: Ethernet Got IP Address
I (8356) eth_example: ~~~~~~~~~~~
I (8356) eth_example: ETHIP:<IP_ADDRESS>
I (8366) eth_example: ETHMASK:<IP_ADDRESS>
I (8366) eth_example: ETHGW:<IP_ADDRESS>
I (8376) eth_example: ~~~~~~~~~~~
On the other hand, I use the same example with integrated ICMPecho to have a PING possibility. LOG:
I (2388) eth_example: Ethernet Link Up
I (2388) eth_example: Ethernet HW Addr 36:85:18:49:26:20
I (2388) esp_netif_handlers: eth ip: <IP_ADDRESS>, mask: <IP_ADDRESS>, gw: <IP_ADDRESS>
I (2388) eth_example: Ethernet Got IP Address
I (2398) eth_example: ~~~~~~~~~~~
I (2398) eth_example: ETHIP:<IP_ADDRESS>
I (2408) eth_example: ETHMASK:<IP_ADDRESS>
I (2408) eth_example: ETHGW:<IP_ADDRESS>
I (2418) eth_example: ~~~~~~~~~~~
I (4498) main_task: Returned from app_main()
esp> ping <IP_ADDRESS>
esp> From <IP_ADDRESS> icmp_seq=1 timeout
From <IP_ADDRESS> icmp_seq=2 timeout
Could somebody help me with that? Is it possible to communicate in such a way?


HADOOP-18602. Remove netty3 dependency

Change-Id: Ib9eb8a325364a60988b4b8dbb2fa7f6ee5a96f58
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[x] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 36s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m  0s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
30m 40s

trunk passed

+1 :green_heart:
compile
22m 56s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
20m 22s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
mvnsite
19m  1s

trunk passed

-1 :x:
javadoc
1m 20s
/branch-javadoc-root-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
root in trunk failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
7m 16s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
shadedclient
31m  8s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 32s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
28m 39s

the patch passed

+1 :green_heart:
compile
22m 31s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
22m 32s

the patch passed

+1 :green_heart:
compile
20m 26s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

-1 :x:
javac
20m 26s
/results-compile-javac-root-jdkPrivateBuild-1.8.0_352-8u352-ga-1~20.04-b08.txt
root-jdkPrivateBuild-1.8.0_352-8u352-ga-1~20.04-b08 with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08 generated 3 new + 2618 unchanged - 2 fixed = 2621 total (was 2620)

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
18m 54s

the patch passed

+1 :green_heart:
shellcheck
0m  0s

No new issues.

-1 :x:
javadoc
1m 12s
/patch-javadoc-root-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
root in the patch failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
7m 12s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
shadedclient
32m 37s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
862m 56s
/patch-unit-root.txt
root in the patch passed.

+1 :green_heart:
asflicense
1m 48s

The patch does not generate ASF License warnings.

1131m  0s

Reason
Tests

Failed junit tests
hadoop.hdfs.TestRollingUpgrade

hadoop.hdfs.server.balancer.TestBalancerService

hadoop.hdfs.TestLeaseRecovery2

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5323/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5323

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint shellcheck shelldocs

uname
Linux 0c066e2f0033 4.15.0-200-generic #211-Ubuntu SMP Thu Nov 24 18:16:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 9514b17ada24a60dd11b9931f38eff8283ac3248

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5323/1/testReport/

Max. process+thread count
3159 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-hdfs-project/hadoop-hdfs . U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5323/1/console

versions
git=2.25.1 maven=3.6.3 shellcheck=0.7.0

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m 29s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  3s

codespell was not available.

+0 :ok:
detsecrets
0m  3s

detect-secrets was not available.

+0 :ok:
xmllint
0m  3s

xmllint was not available.

+0 :ok:
shelldocs
0m  3s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 19s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
33m 43s

trunk passed

+1 :green_heart:
compile
25m 11s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
21m 43s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
mvnsite
20m  9s

trunk passed

-1 :x:
javadoc
1m 20s
/branch-javadoc-root-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
root in trunk failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
7m 22s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
shadedclient
34m 19s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 27s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
31m 16s

the patch passed

+1 :green_heart:
compile
24m 32s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
24m 32s

the patch passed

+1 :green_heart:
compile
21m 43s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

-1 :x:
javac
21m 43s
/results-compile-javac-root-jdkPrivateBuild-1.8.0_352-8u352-ga-1~20.04-b08.txt
root-jdkPrivateBuild-1.8.0_352-8u352-ga-1~20.04-b08 with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08 generated 3 new + 2618 unchanged - 2 fixed = 2621 total (was 2620)

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
19m 45s

the patch passed

+1 :green_heart:
shellcheck
0m  0s

No new issues.

-1 :x:
javadoc
1m  9s
/patch-javadoc-root-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
root in the patch failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
7m 22s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
shadedclient
34m 59s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
157m 45s
/patch-unit-root.txt
root in the patch failed.

-1 :x:
asflicense
1m 23s
/results-asflicense.txt
The patch generated 29 ASF License warnings.

446m 38s

Reason
Tests

Failed CTEST tests
test_test_libhdfs_threaded_hdfs_static

test_test_libhdfs_zerocopy_hdfs_static

test_test_native_mini_dfs

remote_block_reader

memcheck_remote_block_reader

sasl_digest_md5

memcheck_sasl_digest_md5

retry_policy

memcheck_retry_policy

rpc_engine

memcheck_rpc_engine

bad_datanode

memcheck_bad_datanode

node_exclusion

memcheck_node_exclusion

configuration

memcheck_configuration

hdfs_configuration

memcheck_hdfs_configuration

hdfspp_errors

memcheck_hdfspp_errors

hdfs_builder_test

memcheck_hdfs_builder_test

logging_test

memcheck_logging_test

hdfs_ioservice

memcheck_hdfs_ioservice

user_lock

memcheck_user_lock

hdfs_config_connect_bugs

memcheck_hdfs_config_connect_bugs

test_libhdfs_threaded_hdfspp_test_shim_static

test_hdfspp_mini_dfs_smoke_hdfspp_test_shim_static

libhdfs_mini_stress_valgrind_hdfspp_test_static

memcheck_libhdfs_mini_stress_valgrind_hdfspp_test_static

test_libhdfs_mini_stress_hdfspp_test_shim_static

test_hdfs_ext_hdfspp_test_shim_static

x_platform_utils_test

x_platform_syscall_test

x_platform_types_test

x_platform_dirent_test

x_platform_dirent_c_test

hdfs_tool_tests

Failed junit tests
hadoop.hdfs.nfs.TestMountd

hadoop.hdfs.server.namenode.TestAuditLogs

hadoop.hdfs.server.datanode.fsdataset.impl.TestLazyPersistReplicaRecovery

hadoop.hdfs.server.namenode.TestNameNodeRpcServerMethods

hadoop.hdfs.server.namenode.TestLargeDirectoryDelete

hadoop.hdfs.TestFileCreationEmpty

hadoop.hdfs.server.namenode.TestStripedINodeFile

hadoop.hdfs.TestAclsEndToEnd

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5323/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5323

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint shellcheck shelldocs

uname
Linux 17a6a4158af3 4.15.0-200-generic #211-Ubuntu SMP Thu Nov 24 18:16:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 9514b17ada24a60dd11b9931f38eff8283ac3248

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

CTEST
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5323/2/artifact/out/patch-root-ctest.txt

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5323/2/testReport/

Max. process+thread count
1785 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-hdfs-project/hadoop-hdfs . U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5323/2/console

versions
git=2.25.1 maven=3.6.3 shellcheck=0.7.0

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 53s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
xmllint
0m  1s

xmllint was not available.

+0 :ok:
shelldocs
0m  1s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 51s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
33m 39s

trunk passed

+1 :green_heart:
compile
25m  5s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
21m 41s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
mvnsite
20m 26s

trunk passed

-1 :x:
javadoc
1m 19s
/branch-javadoc-root-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
root in trunk failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
7m 40s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
shadedclient
34m 35s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 27s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
31m 17s

the patch passed

+1 :green_heart:
compile
24m 38s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
24m 38s

the patch passed

+1 :green_heart:
compile
21m 44s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

-1 :x:
javac
21m 44s
/results-compile-javac-root-jdkPrivateBuild-1.8.0_352-8u352-ga-1~20.04-b08.txt
root-jdkPrivateBuild-1.8.0_352-8u352-ga-1~20.04-b08 with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08 generated 3 new + 2617 unchanged - 2 fixed = 2620 total (was 2619)

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
19m 55s

the patch passed

+1 :green_heart:
shellcheck
0m  0s

No new issues.

-1 :x:
javadoc
1m  9s
/patch-javadoc-root-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
root in the patch failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
7m 21s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
shadedclient
35m  6s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
709m 30s
/patch-unit-root.txt
root in the patch failed.

+1 :green_heart:
asflicense
1m  6s

The patch does not generate ASF License warnings.

997m 25s

Reason
Tests

Failed junit tests
hadoop.hdfs.TestLeaseRecovery2

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5323/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5323

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint shellcheck shelldocs

uname
Linux a52def5b14f6 4.15.0-200-generic #211-Ubuntu SMP Thu Nov 24 18:16:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 9514b17ada24a60dd11b9931f38eff8283ac3248

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5323/3/testReport/

Max. process+thread count
2517 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-hdfs-project/hadoop-hdfs . U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5323/3/console

versions
git=2.25.1 maven=3.6.3 shellcheck=0.7.0

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

This message was automatically generated.

Thanks @tomicooler for working on this.
Patch LGTM, committed to trunk.

what about branch 3.3?

Hi @steveloughran, HADOOP-15327 was not backported to branch-3.3 so mapreduce still uses netty3 in that branch.

thanks. looks like a useful but big backport


Added addition function

Dr. Seth please add my addition function

I have now added doctests to the add_something function


[12.1 testnet] protocol version of masternodelist

I have checked debug log and found the protocol version of a node is 70201.
But 'masternode list'  shows protocol version of the node as 70202.
macos sierra, Dash Core version v<IP_ADDRESS>-1eb399c (64-bit)
2016-10-03 17:13:33 receive version message: /Dash Core:0.12.1/: version 70201, us=xxx, , peer=12, peeraddr=aa.48.185.55:19999

  "e62ebae735969f203c91a4b48e5b8c8e22332abbda5f5c756dc18751ecf35047-0": "  ENABLED 70202 yTCez9XVLgi3v1TmSNfrTjAmGwe875f7wv<PHONE_NUMBER><PHONE_NUMBER>514814  79721 aa.48.185.55:19999",
  "f6e282fb3bab4ccfcc53e1fa029613225791b5ad3d81bede9810f0ce7d6af7a1-1": "  ENABLED 70202 yio3QxN6uHjpbgyYQ9erpqMdDEhqb7yCAq<PHONE_NUMBER><PHONE_NUMBER>237062  77965 aa.48.185.55:19999",
  "5e681bca84fcbec216c7f43434bee90f7008c6c623f620e206057d7285f48326-0": "  ENABLED 70202 yXRE5LbE5shk85vdnBnA8bKNcQds7HSJuL<PHONE_NUMBER><PHONE_NUMBER>513811  79713 aa.48.185.55:19999",
  "07f1fc88a1b1e6a6bf0ffa744d270d9f13224bb1ef7c245014d30bdf649e12d2-0": "  ENABLED 70202 yb7zPDqVVVrFEx2tvKYduo35ojfEvEYuNV<PHONE_NUMBER><PHONE_NUMBER>504423  79651 aa.48.185.55:19999",

*edited : ip is masked

Also note that the IP address is obviously invalid here.  I'm surprised we aren't validating those before considering an MN to be enabled, or accepting a peer connection.

@tgflynnI have changed the ip. aa is actually 45 and xxx is my ip.

@chaeplin Ah, OK, thanks for clarifying that.

masternodelist itself is fine and works as it should. The reason for results you see is that you node is a "real" one and all other nodes in masternodelist are nodes of an attacker who is reusing your IP. That's a known issue, but thanks for reporting anyway :)

thanks


docker exec should cleanup its orphaned processes when it exits

Some background on this is at:

https://github.com/docker/docker/issues/9098
https://github.com/docker/libcontainer/issues/286
https://github.com/docker/libcontainer/pull/290

TLDR: docker exec process when exits can leave behind orphaned/unwanted processes, this patch put all processes belongs to a single docker exec session into its own subcgroup and removes them when the main process finishes. This will not affect processes spawned in the container and/or other exec sessions.

nice - can you please add a sentence or two to this effect into the run.md - that way anyone that is curious how and why this happens will have something to refer to
I'm interested to see how (or if) users will want to start new daemon processes using docker exec

I think this should have a flag to control the behavior. While I somewhat agree with the idea in this change, I do not think it that unreasonable for some more complex applications & systems to use docker exec for lauching long running commands inside a container. Perhaps as part of some nightly maintenance scripts, to kick off a background task.

@phemmer @SvenDowideit in that case, would it make more sense to run each long-running process in a different docker exec -d session instead of having short-lived script launching multiple long-running daemon ?
The purpose of the patch is to prevent that exact situation as ideally an exec session should not leave orphaned process inside the PID namespace when it finishes.

@dqminh I think that libcontainer was bumped and now you can rebase against master.

yes, I guess docker attach $(docker exec -dit ...) makes sense, compared to docker exec -it nohup stuff - does it work that way?
yes, I realised talking to some people last night, that you might have a long running upgrade / transform task you might start with docke exec, and having it reaped due to network failure to the Docker client may make them cry too.
no-easy-answer

I'd document what the PR does now, as it seems like a useful addition as is.

yes, I realised talking to some people last night, that you might have a long running upgrade / transform task you might start with docke exec, and having it reaped due to network failure to the Docker client may make them cry too.

ah no, it currently doesnt behave like that. The behavior of how docker exec client affects the remote exec session on the server when the client exits is currently undefined.
Starting a long running exec session with docker exec -d will work as is ( i.e, the remote exec process will not be killed if the client is killed ). This patch only affects cleanup of docker exec processes when the main process exits. For example:
# before this patch
> docker exec -it my-precious sh
/ # sleep 1000 &
/ # exit
# now there's a dangling `sleep 1000` process inside the parent container after main `sh` process exits and user has to clean it up manually

# after this patch
> docker exec -it my-precious sh
/ # sleep 1000 &
/ # exit
# main `sh` process and its `sleep 1000` child process will be stopped.

@SvenDowideit i will add some docs to cli and the HTTP api to document the new behavior for this patch.

Actually i think it probably makes more sense to have the cgroup setup as an optional part. Some of our users do want to launch background processes from an interactive exec session and dont want them to be shut down automatically.
I will close this and open again when it's ready.

@dqminh Is there followup on this PR?


Enable deployment of exhibitions from local source

This addresses ticket #7822 https://issues.dp.la/issues/7822

I tested this locally by deploying a local branch of the exhibitions app, and it seems to be working as expected.

I'm :+1:, but maybe have @markbreedlove take a look too before we merge?

@AudreyAltman, just fixed something in https://github.com/dpla/automation/commit/3d9eb56688e1677c8b83996c9e1763a4c0a63a47 related to my last comment, and related to the rsync error that you reported to me before.

I'm :+1: if @markbreedlove's good on this. Shall we merge?

I'm fine with merging it.  @AudreyAltman, would you like to squash it first?

:squash:ed and ready to :merge: @markbreedlove or @anarchivist


error while looking for metadata directory when using livy

Hello everybody,
I connected to my remote spark cluster from RStudio desctop via livy. The connection works well, but when I try to read a parquet file from hdfs the livy server outputs the following error:
"error while looking for metadata directory"
On client side I see "Value sparklyrRetVar_36" does not exist in the R console.
Using the spark-shell on a cluster node there are no such problems. Are there additional configurations necessary?

@hecking sounds like you need to specify spark.sql.warehouse.dir either when Livy launches as a service or as a config in spark_connect?
Reference: https://issues.apache.org/jira/browse/SPARK-15034

I specified the warehouse  directory. Meanwhile I also figured out that without configuration the value of spark.sql.warehouse.dir depends on the folder from which livy was started. I made sure that the warehouse paths exists. In the server logs I can see that livy points to the correct directory.
spark_session(sc) %>% invoke("conf") %>% invoke("get", "spark.sql.warehouse.dir") also gives the expected outcome.
However, the problem still remains.


Main

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

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

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

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

:tada: This PR is included in version 3.1.0-alpha.9 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Crash on Android 10

My clients who are using android 10, are facing the following issue:
java.lang.IllegalArgumentException:
  at On.onWrite (PG:27)
  at android.print.PdfConverter$1.onPageFinished (PdfConverter.java:71)
  at e6.b (PG:2)
  at on.handleMessage (PG:63)
  at android.os.Handler.dispatchMessage (Handler.java:107)
  at android.os.Looper.loop (Looper.java:237)
  at android.app.ActivityThread.main (ActivityThread.java:7770)
  at java.lang.reflect.Method.invoke (Native Method)
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:493)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1047)

After seeing this trace, the first thing came to my mind that maybe the user did not allow storage permission. I double checked with them and found out that the storage permission was enabled. However, when the app is trying to generate PDF, it crashes.
Any ideas? Thank you

Hi, just realise i'm also facing similar issue regarding Permission. But, it's kinda random though. sometimes the crash happened sometimes not.

@SaruwatariSagittario do you face this issue in android 10 also?

Yes.
Scratching head for days cause of the crash. I already put the permission protocol using react-native-permissions before generating pdf, still Crashes on Android 10

It's not about permission.. I have tried granting the permission manually from settings but still crashes.
https://github.com/christopherdro/react-native-html-to-pdf/blob/4bc1a3d249ede0329d4de3aaa72bd3b6db7d2ef1/android/src/main/java/android/print/PdfConverter.java#L71
this is the line where it crashes.

Yeah I also got logcat report saying it stopped working on that particular line. Do your issue happen intermittently or always happened.

Yeah I also got logcat report saying it stopped working on that particular line. Do your issue happen intermittently or always happened.

for me it happens every time 😕

Same issue, but I cannot find some way to work around

i changed sdk to sdk 29, and added this line:
PermissionsAndroid.request(PermissionsAndroid.PERMISSIONS.WRITE_EXTERNAL_STORAGE);
to index.

for me the solution was, save the pdf file in an existing directory.. Seems like if we dont specify the directory, the lib cant save the file.
NOTE: I asked for directory permission but still faced the issue. Specifying an existing directory solved my problem.

hi, any update about this issue??

Has anybody got a solution yet?

After searching through github repo fork network graph, I found this fork works fine: https://github.com/jdaoliveira/react-native-html-to-pdf
For anybody who's suffering the android 10 upgrade, you can uninstall version 0.8.0 and try npm install https://github.com/jdaoliveira/react-native-html-to-pdf.git


clj-djl should not dependend on  org.slf4j/slf4j-simple

https://github.com/kimim/clj-djl/blob/e29352ed873accde8d7f5ec2dc5a8075b02b335b/project.clj#L8
It should depend on the api, if not everybody using it inherits the dependency, which is bad practice

Thanks. I fixed in the latest commit.


Investigate original names in source maps with source-map-support >= 0.5.8.

See https://github.com/scala-js/scala-js/pull/3663#issuecomment-495140160.

Potentially related: https://github.com/evanw/node-source-map-support/pull/253

Potentially related: https://github.com/evanw/node-source-map-support/pull/253


genquery2_sql.hpp uses std::vector but does not #include <vector>

std::vector is referenced here:
https://github.com/irods/irods_api_plugin_genquery2/blob/f600cdf88133dfe50114d9db3e7249fc51e12efb/parser/include/irods/genquery2_sql.hpp#L19
but <vector> is not #included.
This causes an error during compilation against libstdc++.

Looks identical to me:
https://github.com/irods/irods_api_plugin_genquery2/blob/402c276a6c020e8ed0fdbe9658ec2d2bc78d8f2f/parser/include/irods/genquery2_sql.hpp#L19

Let's add the checkboxes and cherry-pick the change.


Autoplay does not work after hide / show

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Swiper Version: 4.5.0

Platform/Target and Browser Versions: OSX / iOS, Android, Chrome, Safari

Live Link or JSFiddle/Codepen or website with isssue: https://codepen.io/NeptuneG/pen/eYOpEEM

What you did

Hide <div> including an autoplay swiper then show a modal.
Close the modal and show the hidden <div> include the swiper then call swiper.update() .

I tried the workaround mentioned in Issue #2073, but still simply not work.

Expected Behavior

The swiper is rendered and continue autoplay from the slide shown before hiding the <div> .

Actual Behavior

The swiper was rendered but autoplay stopped.

You may have a try like this to fix it,
      $(function () {
         $('#modalTrigger').click(function () {
             swiper.autoplay.stop();
             toggleModal();
         });
         $('#modalReturnBtn').click(function () {
             toggleModal();
             swiper.autoplay.start();
             swiper.update();
         });
     });

@saltb0rn It seems to work! Thanks.


Nav menu builder

we need to create navigation builder and add it e.g. to settings tab

user should be able to build menu with pages / post titles / post categories / or his own links

Hello, It is a good start, but let us have the basic functionality out of this. Add, delete, reorder and multi-layer.
This path should be a route alias. So for example we create a page called Contacts, then refer to it when building the navigation. The path can be also something the user type manually like external link or html anchor.
Thanks

@mahnouman I think this issue might be closed now


Improve script.

I'm using this with the new experience on JIRA and hit a few issues. I'm just sending one PR since it's a small project, but I can split them up if it's too confusing. Hope you find it useful.

Optional Docker Compose file added.
Added jiraLoginUsername for JIRA Cloud users that log in with Atlassian ID
but have a different username in the instance.
Added notifyUsers option to silence emails when syncing time.
Defaults to TRUE, so behavior is not changed.

Hiya, first of all, thanks for contributing :) I am happy to merge this, unfortunately, the unit tests are failing and there are some code style issues (see Scrutinizer).
If you fix them, this can be merged.

Ah, I configured PhpStorm for Zend, but there wasn't an .editorconfig, so I wasn't sure of the actual style in use :) I'll fix the boolean case later today when I run the script again and try to get the tests passing. I assume I have to update them to be aware of the new parameters/properties.

I think it should be all good now :)

Yay! Merged and thanks :)


Why does StreamingDataset.state_dict() have to be told how many samples have been yielded?

My question is, why does StreamingDataset.state_dict() have to be told how many samples have been yielded? https://github.com/mosaicml/streaming/blob/0fc72665e9c20e1c53d036d09592b7335ae8ae9a/streaming/base/dataset.py#L771
The pattern of the StreamingDataloader keeping track of num_samples and providing this to the dataset to get the state dict works for most use cases, but things get much more complicated if you have downstream functions like rejection sampling and bin packing that make it harder to keep track of how many samples were yielded from the dataset.
So, I just wonder if there's any reason why the StreamingDataset itself can't keep track of how many samples it has yielded? It seems that would enable a simpler state saving and loading interface.
Thanks in advance for any help!

Most dataloaders implement some form of prefetching on samples. Accordingly, streaming can't track the number of samples processed, as it may have yielded samples which have not actually been processed when checkpointing occurs. Unfortunately, this means you must pass in sample count during a call to state_dict.

Thanks for the explanation! Makes sense to me.


How to use Tensorflowlite SDK with iOS 8

Hello @petewarden ,
I want to support tensorlowlite to my existing project which is having iOS 8 min target. But I am getting error while including it using pod targeted OS version does not support use of thread local variables in __ZNK6tflite13eigen_support12_GLOBAL__N_122EigenThreadPoolWrapper15CurrentThreadIdEv for architecture
Can anyone help me how to fix this issue?
Any help is appreciable.
Thanks

@miaout17 : Can you please help me to achieve this?

We do not officially support iOS 8, but you could try building your own TensorFlowLiteC framework with minimum OS version as 8.0.

In tensorflow/lite/experimental/ios/ios.bzl, change the TFL_MINIMUM_OS_VERSION to 8.0.
In tensorflow/lite/experimental/ios/BUILD:

Comment out the gpu:metal_delegate.h from the header list.
Comment out the "Metal" line from the TensorFlowLiteC target.
Comment out the gpu:metal_delegate dependency from the tensorflow_lite_c target.

Once you've done all of this, try building the TensorFlowLiteC_framework target with the following command:
bazel build -c opt --config=ios_fat //tensorflow/lite/experimental/ios:TensorFlowLiteC_framework

You could then try using this framework following this guide.
Let me know if this works for you.

@yyoon
Thanks for your support. I will check and get back to you on this.

It has been 15 days with no activity and the awaiting response label was assigned. Is this still an issue?

It has been 30 days with no activity and the awaiting response label was assigned. Is this still an issue?

We are closing this issue for now due to lack of activity. Please comment if this is still an issue for you. Thanks!


For the Actions Sync  ,we need to add db logs msgs describing the live process

We should be able to add to db logs  of what's happening in the current proccess .
My initial idea for this logs pattern is

starting to get workflows
starting to get all runs and jobs for workflow "workflow name"
inserted x number of runs and x of jobs
starting to get all runs and jobs for workflow "workflow name" .....

starting to get all GitHub Actions workflows for repo (repo)
starting to get all GitHub Actions jobs for workflow (name)
starting to get all GitHub Actions runs for job (name)
inserted x runs and y jobs
....


Fixed missing Artwork in WebService

Add Clearlogo,ClearArt,Disc & CharacterArt..
This Art missing in WebService

Thanks for the PR. There is however no more need as I've already adjusted the code with a more generic approach to fix it. New version available asap.


Update docker image used by slim version of the action

Fixes #4494

Update the docker image referenced in the slim metadata file to use the same version as the main version of the action.
Proposed Changes

Uses the updated super-linter/super-linter repo
Bumps the slim image version to 5.2.0 to align with the full-fat version of the action

Readiness Checklist
Author/Contributor

[ ] If documentation is needed for this change, has that been included in this pull request (N/A)

Reviewing Maintainer

[ ] Label as breaking if this is a large fundamental change
[ ] Label as either automation, bug, documentation, enhancement, infrastructure, or performance

Would it also be worth having a mechanism to either

Keep the two versions aligned automatically?
Detect when the two versions diverge?

@grahame-student Yes, that would be really helpful. I would lean towards automation to keep the versions in sync.


Pip install not working

Super excited about this project. I love duckdb and tying it in with dbt is a great idea. I tried pip installing this package per the readme but a version on Pypi couldn't be found. Has it been published to Pypi yet?

Hey Andrew, thanks so much for the note! So I haven't made it available yet b/c there isn't a released version of duckdb that this works with yet-- you have to do a build from source against duckdb/master and you would also need these two PRs (which should hopefully be merged in soon!)
https://github.com/cwida/duckdb/pull/1044
https://github.com/cwida/duckdb/pull/1037
...once those are in and a new release of duckdb is cut, I will publish this to Pypi and update the docs to that effect.

Thanks for the context! Want me to leave this open until that happens? or close this provided your context?

I'm hoping it won't be that long till the next release, so let's leave it open for now. Thanks again!

Fixed now; pip install dbt-duckdb does the right thing.


Deploy Builds v0.8.0

Changes

Deploy v0.8.0 of the build controller
Update default version in preparation of the release.

/kind feature
Submitter Checklist

[ ] Includes tests if functionality changed/was added
[ ] Includes docs if changes are user-facing
[x] Set a kind label on this PR
[x] Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.
Release Notes
Update build controller deployment to v0.8.0.

/assign @SaschaSchwarze0

/cc @sbose78 @qu1queee

/approve
Self-approving


Even more minor typos fixed

f76768d - fixed minor typos on some Upgrade cards.
d521ca7 - updated the text to exactly match the card (1 [Hit]/[Critical Hit]/[Focus] instead of 1 [Hit], [Critical Hit], or [Focus]).

Thanks a lot!


Collect email addresses of petition sponsors

I think we're ~80% here with this.  I think we could leverage the Sponsor and has_many :sponsors association more than we are.

Yeah, this feels better, nice work @otlaitil!

Looks like we need a rebase against master (perhaps wait for #23) and then we can merge once green.

@h-lame yep, I will do that. Is it ok if I squash all the commits in this branch to a single one before merging?


What does seeders do?

Seems like it's a newly added feature.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/25730416-what-does-seeders-do?utm_campaign=plugin&utm_content=tracker%2F73887&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F73887&utm_medium=issues&utm_source=github).

It is not only new, it is not released yet :)
Like the name says, they provide the ability to seed your database. Or more specific, everything that is related to data manipulation and not part of the data definition is part of a Seeder.
There are two types of seeds that are going to be introduced. VC Seeder and static Seeder.
The release will also provide documentation for all of this.

If you want to have more informations right now, you can also read the describing comment of the seederInterface:
https://github.com/db-migrate/node-db-migrate/blob/master/lib/interface/seederInterface.js#L1-L36

Sounds like a data transformer layer. That's powerful. Considering one can easily manipulate production schema on a fly without necessarily rolling out a new deployment.
Well explained. Thanks

That is the plan yes.
One of the hairiest use cases would also be for example:
Renaming, moving or duplicating a Column
It isn't a big deal normaly, but not if you want to keep your zero downtime deployment, you need to take the detour. Creating a new column in the first step, copy over the data of the column in the second step, set the new application live and if it is live, running and working deleting the old column.

In Cassandra, you can't rename a table or column family. Seeders could be helpful here.
I'm writing a driver for Cassandra. You can have a look here.
I intentionally did not implement the renameTable spec because of this limitation. Happy to get a first hand update on Seeders.

@charyorde I guess renaming in this case would need to copy the whole table?
In this case your decision wasn't wrong, but this brings some topics up that are planned for zero downtime friendliness. If you handle zero downtime on a database you have a similar problem. You will need the old table and the new table on a renaming action. May be this is something to also consider when thinking about this.

That's the sort of solution proposed as at here

Well copying files seems not to be a good option to do this. Renaming is by nature an action that is not very zero downtime friendly. Especially if there is nothing like aliasing tables.
What I currently think of is: When we copy a table, this is not a seeding operation, but a migration operation. Even so it does write data one to another table, seeding is ment to be everything that is not data definition. And copying is kind of both in this example, but still it initial operation is data definition and copying a table without duplicating it together with the data in it is an uncomplete operation.

Doing that in production without a downtime is possible in layers of database clustering (for RDMS) and masterless architectures in Cassandra.
Based on your explanation, it's obvious that Seeders and Migrators have to be non-mutually exclusive to get this to work. Can Seeders intereact with migration functions at the moment?

The final draft for seeders defines seeders to be not linked, but act in the same way as everything else in a migration.
This means, a migration can call seeders up to a defined point like everything else.
I think an example is more clear:
var seed;

exports.setup = ( options, _seed ) => {
  seed = _seed;
};

exports.up = ( db ) => {
  db.renameColumn( 'test', 'from', 'to' )
  .then( () => seed.up( '20xxxxxxx-seeduptothisseed') );
};

exports.down = ( db ) => {
  seed.down( '20xxxxxxx-seeddowntothisseed')
  .then( () =>  db.renameColumn( 'test', 'from', 'to' ) );
};

To add, at the moment seeders are not implemented like the final draft describes them. Currently I write the test suite for the seeders btw., also right now at the moment.
And to add: Some migration tasks may execute seeder like behavior without wanting them to actually execute a seeder. Copying a table is a perfect example for this. The reverse of copyTable, would be dropTable and thus only one direction needs to execute a seed. A seed itself would be for operations that you want to reverse at some point. To give a really simple example: Like changing all values of a spefic column and multiply them with 10.

About the layer database clustering:
Yes that is a possible way, but possibly this is something out of the scope for db-migrate. A perfect zero downtime deployment is an automatic one without any human interaction. While I want to allow this zero downtime friendliness it is hard to cover everything and also not generally wanted to just cover everything, but give a good, useful and powerful toolset with it that makes such a task as easy as possible.

Best thing would be obviously to never rename anything :p
However zero downtime is something for the future and that will be definitely something that will need its time to mature.

I just took a look if I already have published any docs about the seeders. And I haven't published anything yet. That is a good thing though, as it would just confuses users to think to be able to use this stuff already, which is not the case.
Also as additional information: The first 4 seeder operations will be insert, remove, update and lookup. Examples of how those will look are also not yet in the docs, except for the new docs, you can take a look here if you want to:
https://docs-0-10.dbmigrate.wizardtales.com/API/Seeder

I checked out the comment here:  https://github.com/db-migrate/node-db-migrate/blob/master/lib/interface/seederInterface.js#L1-L36
The first sentence says "The seeder interface provides the ability to handle all operations, that are not DDL specific and thus not a migration."
While I agree that inserting data is different than changing a schema, data insertion is very much dependent on the schema and therefore should therefore be considered a first class migration just like DDL, just one you want to execute optionally depending on environment.  Otherwise you end up in a situation where you constantly have to re-write your seed data migrations if you introduce "real" DDL migrations that break the insert statements.  That's a BIG smell if I've ever seen one.  The whole purpose of a migration is that you write them once and don't edit them again in the future.

First of all I do appreciate your engagement here :)
I understand your point, but that is also not how it is going to work. There will be two types of seeders. Seeders like the traditional ones you know, that are executed whenever you feel the need to and those that will work similar to migrations. B/c they will be in fact versioned and are tightly integrated with migrations. Means you are able to call such seeds from migrations and the other way around.
Unfortunately I'm currently not at home, which makes it not possible to go any further into detail, but I will look on sunday evening when I am back, into answering questions more thoroughly.

@jonathan-fulton So to start with the whole migration and seeder topic, lets start with the following part for today:
Migrations
A migration should be capable of transferring a data object from one state to another. May this be a table, a traditional column or some document storage.
Seeds
A seed should be capable of manipulating data, e.g. transforming data, inserting data, deleting data. A seed is thus dependent of a migration that successfully created an agreed state of the data object to be manipulated.
Static Seeds
The very first implementation are static seeds, those are that kind of seeds that are more or less just a replacement for sql files. The only thing that would give them an advantage over sql files is if migrations are written for a prototype and the project later on decides to use another database. In this case the seeds are most likely guaranteed to be compatible, exceptions may excist when moving from sql to nosql.
Version controlled seeds
The second implementation are the version controlled seeds, those work exactly the same that migrations do, but they do offer different toolsets.
They can be rolled back and they do not execute again if they have been already, just like migrations.
Integration of seeders and migrations
As from the definition already stated, a seed is always dependent from its migrations. That creates two kind of different relations between

migrations and version controlled seeders
migrations and static seeders

Static seeders have a one sided relation to migrations, as they just depend on them. A static seeder can, but does not need to, define a migration up to which all migrations already need to be executed in order to execute the seed.
Version controlled seeders do have a two sided relation and a one sided relation. Version controlled seeders can define a state they depend on just like the static does.
The other relation is a bit different:
The two sided relation is on the seeder side also the defined state which the seed does depend on. A two sided relation is not invoked by the default logic, it gets invoked through the migrations. Thus the migration calls the "up and down" functions and not db-migrate in this case. A migration does also refer to a seed up to which all seeds shall be executed.
That means a one sided relation is just the seeders depending on a migration state and the two sided relation is also the migrations depending of some execution state of seeders.
I will continue with everything I have left out right now, but this is already a good start to give an idea where the whole thing runs. If you have opinions on this already, don't stop and go ahead and let me know ;)

@wzrdtales Thanks for the detailed response!  Very helpful.  Apologies if the above seemed harsh at all.  node-db-migrate was so close to being perfect for me.  Still an amazing tool that I'm taking advantage of though so thanks very much!

@jonathan-fulton No worries, no offense were taken. Discussions, ideas, prs, feature requests and any other kind of contributions are always welcome :)

I think that seeding is released now considering the version is 0.10.0-beta.20?
@wzrdtales can you please advise how to create a seed template & link it to a migration?

@staff0rd Much of it was done already, I decided to post pone it to a later release however anyway. From 0.9.x to 0.10.x a lot has changed. If not everything has changed, while still kept as backwards compatible as possible. I have decided this b/c 0.10.x should finally leave the "beta" stage, it is since a while actually stable, but without proper docs and some missing tests it is not ready for release yet. Those are the things that are being worked on and after the 0.10.x release I want to switch to monthly releases instead of the current release target, to get new stuff faster in again.
I have done quite some work at the docs I need to finalize (I hope I finally get to it this weekend). As you might noticed I try to be as responsive as possible and as fast as possible, but I don't always have the time to actually work on db-migrate, b/c I'm also involved in multiple other projects and also my work is eating much of my time though, if you want to help you're more as welcome though ;)

Where can documentation on seeders are supposed to work and how to use them be found? The documentation at https://db-migrate.readthedocs.io/en/latest/Getting Started/usage/#seeder-introduction is very lacking.
The current state of this project (beta versions being pushed to NPM, links to a GH tag would have made more sense for dev/beta releases) and the lack of published documentation is causing me to considering throwing away a few days of work and switching to a simpler migrator that isn't trying to be everything. Some of us just want to be able to run up/down, create/delete tables and add/remove records without a bunch of hoop jumping.

Since the insert method is deprecated I'm using the normal runSql, still, I'm curious about how to use seeders, but I guess we have to wait,
Again, thank you for your work :)

@wzrdtales Just a friendly ping on when we could expect proper documentation to be released :)

+1 on the documentation

+1 on the documentation

+1 documentation

👍 ❌ 💯  on documentation :)
also, can seeders, like migrations be .sql ? if so, how does it associate between them

Is there any documentation on how to do a versioned seeder? the read tho docs only mentions them in passing.

Hey all,
sry for the delay, the thing about seeders is that they were planned to be introduced but then postponed. The docs have yet not been updated. However, there are some news on that topic, I will give you all an update to this topic by this week (put it literally on my schedule).

@wzrdtales you have the update? 😄

@BorntraegerMarc yes :) But needed a bit more time though.
So for the Seeders, to go into a bit of detail:
They have been postponed to actually push the release of the 0.10.x version further, which helped but the last two years I got very tight on time as I got very heavily involved in other projects, so stuff really stretched way beyond what I wanted it to stretch. This is the reason why this is open for so long actually, the good news are, that in recent projects I do incorporate db-migrate again which includes doing work on it to improve it. Part of this was for example pushing out the cockroachdb driver and also part of this was starting work on the seeders again.
Here I will make a decision now, I will end the beta track for 0.10.x as of now. I will push out a non beta version over the next weeks (currently my schedule is even more tight as I also prepare for dockercon), which I could have done even earlier than now. The only reason for not releasing 0.10.x was actually me not being satisfied yet with the state of the docs and tests. But actually 0.10.x is far from being a beta, it works and does its job quite stable, so not so much beta anymore. So releasing finally the 0.10.x means repolishing a few last things, taking out the way too big changelog (from 0.9.x to 0.10.x db-migrate basically has been revised and to a certain extend rewritten in many if not all parts) and cleaning up the docs.
So the interesting part for you guys starts here, some version >0.10.x will introduce the first version of seeders and subsequent versions will introduce additional toolings to seeders. With seeders introduced db-migrate will step out of the 0.x.x tree and release the first major release 1.0.0. A goal for me ending the beta is actually enable new features to be introduced in normal releases quite quickly and I hope to see a motivated community contributing :).
The goals for the next time remain the same however:

Have a clear separation between data definition and data manipulation*
A focus zero downtime enablement
3 step migrations**
Seeder
Seeder toolings
More support functions/toolings for community drivers

To the points marked with stars:

Separating data manipulation and data defintion does not only make the code base more clean and understandable, but is also supporting to have a logical separation between those two, which is absolutely necessary to successfully implement true zero downtime
** 3 step migrations are an exclusive feature towards zero downtime, they will enable to migrate non-deterministic changes, like renaming and will be quite exclusive to the programatic access as it provides information to the application and also plans to incorporate orms to control changes for those. There will be a cli too, but this will be just for manual operation and not really useful though.

Thats it and a call out at that point, if anyone here feels that he wants to help on any on that points, wants to add some goals and help working on these, please feel free to reach out or just directly contribute. You're all more than welcome to help evolving db-migrate to suit modern needs of massively scalable and production critical systems in a continous deplyoment environment.

Sounds great! but the question remains: What do seeders actually do? 😉
nah, I'm just kidding! I think it has been great seeing this library evolve over the years and now moving to a final 1.0 release 🎉 I love it!!! I will help out in whatever way possible 😃

can anyone provide an example or API documentation of the functions of the seeders ?

Please don't close it 😄 Official documentation has still not been provided

Just added the stale bot, you should see my inbox though :joy: , working through to see what really can be closed and what not.

it seems released. but where is the documentations? how to use cli to create template file and how to use it?

I suppose we have to investigate the code. 😄

What is the current status of this? I'm happy to write some docs if someone can explain to me roughly how to use it...

I'm wondering about this feature too. I'm using Postgraphile to build my app, and often find myself loading the same data in for testing or production. E.g.:
select<EMAIL_ADDRESS>'client1', 'password', 'client');
select<EMAIL_ADDRESS>'client2', 'password', 'client');
select<EMAIL_ADDRESS>'writer1', 'password', 'writer');
select<EMAIL_ADDRESS>'writer2', 'password', 'writer');

insert into app.order(owner_id, title, description) values(
  (select id from app.user where username = 'client1'),
  'client1 open order',
  'Description of order'
);

Can I use seeders to automate loading these queries when NODE_ENV=develop? If so, even knowing how to do that would be helpful.
Thanks.

How about seeder document ?

Hey folks!  Why do we need seeders if one can use runSql to manipulate data? What's the profit?

Where is this feature documented? There's the interface docs, but they don't actually tell you how to use them. Has there been any movement on this at all or has everyone just switched over to using sequelize for migrations?

i would like to add another request for actual documentation around this feature, but since people have asking about this for several years now, i'm not too hopeful.

i would like to add another request for actual documentation around this feature, but since people have asking about this for several years now, i'm not too hopeful.

there is a reason closed issues are closed. and its really not hard to find the current one https://github.com/db-migrate/node-db-migrate/issues/687
If you really need this feature right now, then help the project and contribute. There are efforts running, but seeders done right, in the sense of db-migrate being a tool that promises zero downtime operations, will take more effort than just executing an insert call. My time is scarce running multiple businesses and while I seek to continue developing this library, it happens in batches where I get some free time. So really, the best anyone can do in btw. any open source project, is trying to help themself. Which is your duty anyways if you're consuming open source software.

there is a reason closed issues are closed. and its really not hard to find the current one https://github.com/db-migrate/node-db-migrate/issues/687
If you really need this feature right now, then help the project and contribute. There are efforts running, but seeders done right, in the sense of db-migrate being a tool that promises zero downtime operations, will take more effort than just executing an insert call. My time is scarce running multiple businesses and while I seek to continue developing this library, it happens in batches where I get some free time. So really, the best anyone can do in btw. any open source project, is trying to help themself. Which is your duty anyways if you're consuming open source software.


UI actions are only available on root isolate

I would want to know how can i open UI in new isolate - not root? if it is possible, please give some examples or  solution.thank you

@ershat-dl
Your question is better suited for StackOverflow. Please see https://flutter.dev/community for resources.
Closing from here since this repo is for tracking bugs and feature requests.


Use Data.Hash from contrib?

I.e., https://github.com/idris-lang/Idris-dev/blob/master/libs/contrib/Data/Hash.idr

Sounds like a good idea. I would gladly accept a patch :)


EXC_BAD_ACCESS KERN_INVALID_ADDRESS at 0x00000000

I running my app on iPhone 6 Plus. But i have an issue with AFNetworking as image below.

Any suggestions how I can determine the cause?
Thanks.

Duplicate of #2507


phpdoc_order should be configurable

The phpdoc_order fixer specifies:

param annotations come first, then throws annotations, then return annotations.

However, this is very opinionated and other projects may wish to configure a different order.

How about opening a PR?

That's an interesting idea. Do you have any other interesting ideas?

We are community driven project. If you want to have a feature it would be great to help project introducing it. That's it.

Are you suggesting I should not request a feature I am not prepared to code myself?

@Bilge
What I am suggesting is this: If you are using an open source library and want a feature, but do not want to contribute it yourself, maybe try being a nice person. It helps in a lot of situations. 👍

When was I not being a nice person?

I would like @throws after @returns, it reminds me of when I was dev.ing in Java.
So please, anyone go for it :+1:
That being said, I think if someone ask for a feature from a community, one should not be surprised if someone from that community asks about opening a PR. You can always so "no" for whatever reason (which you don't have to provide).

Everyone, calm down a bit ;)
All suggestions, requests and bug reports are more than welcome.
At the same point, we cannot make everything in house. Best option (but not the only one) to make the request happen is to help with it, if it is not possible by any reason then the requests end up in big backlog, from which requests are chosen by priority, amount of how many people are requesting same thing and finally willing of community to work on it. Your request is valid, question for help from your side as well. Just keep in mind that without it it's not on top of that backlog yet ;)

I've seen enough.

Closing as duplicate of #1602


Upgrade sqlite to 3.26.0 to fix security vulnerability and add window functions

Like https://github.com/litehelpers/Cordova-sqlite-storage/issues/837, which just landed a couple days ago. Many details on the security vulnerability are in the links in that issue.

Here's a workaround until a newer sqlite is included as part of react-native-sqlite-storage:

Turns out that sqlite is included in ios:

https://github.com/yapstudios/YapDatabase/wiki/SQLite-version-(bundled-with-OS)

But you can bundle your own sqlite3 dylib that shadows the ios system dylib, e.g. using CocoaPods:

https://github.com/stephencelis/SQLite.swift/blob/master/Documentation/Index.md#requiring-a-specific-version-of-sqlite
https://github.com/clemensg/sqlite3pod
e.g. pod 'sqlite3', '~> 3.27.1'

@jdanbrown how do you fix this on Android? Any Ideas

@herlarb Nope, no idea, haven't tried android.

The iOS library does not include SQLite binaries. It uses SQLite that is available on the iOS.

how do you fix this on Android? Any Ideas

I recommend rebuilding NDK (*.so) libraries from https://github.com/brodybits/Android-sqlite-ext-native-driver and copying them into src/android-native/libs. The default master branch contains FTS5, R-Tree, REGEXP, and non-standard BASE64 functions; the sqlite-storage-native-driver branch branch does not contain these features.

The iOS library does not include SQLite binaries. It uses SQLite that is available on the iOS.

Yeah, I didn't realize that at first, but did learn it in the course of figuring out my workaround above.
Another twist (cc @aidanw re #321):
After I followed my workaround I started seeing crashes in places I had not seen before, and the new crashes didn't make much sense to me (EXC_BAD_ACCESS from within the sqlite sql parser—see backtrace screenshot below), so I gave up on the nonstandard sqlite lib (3.27.1 via sqlite3pod) and rolled back to using the built-in ios sqlite lib (3.24.0).
If I were to dive into fixing it I'd start by tweaking sqlite3pod's sqlite build flags to enable some of the ones that increase safety (e.g. SQLITE_THREADSAFE=1—see the sqlite compile flags docs). It looks maybe possible to figure out which sqlite build flags were used for the ios built-in lib—a good first step might just be to match those—and also cordova-sqlite-storage's build flags could be another good reference.

@andpor Sounds like a wontfix since this is an issue with the built-in ios sqlite lib? Going ahead and closing.

@jdanbrown if you use custom sqlite lib, I would recommend you remove all references to libSQLite.a that you see in master/src/ios/SQLite.xcodeproj/project.pbxproj.
I think it is desired to rebuild NDK library objects for Android, as I described in https://github.com/andpor/react-native-sqlite-storage/issues/310#issuecomment-469357373.

I think it is desired to rebuild NDK library objects for Android, as I described in #310 (comment).

Ah, +1, reopening.

So I attempted to build the binaries using latest NDK. armeabi is no longer supported and had some compilation warnings about implicit pointer casts which make me a little uncomfortable. Awaiting some updates from @brodybits on this topic before I proceed.

@jdanbrown - can you try new-native-sqlite-libs branch - I uploaded new native libs. Let me know how it works for you.

My apologies for the delay. The trick for me was to use android-ndk version 16b (I think) to keep the old armeabi support. (I did already make a note on the Android-sqlite-ext-native-driver project.)

@jdanbrown - can you try new-native-sqlite-libs branch - I uploaded new native libs. Let me know how it works for you.

I don't have an android build to test against. Maybe @herlarb or @brodybits can try it out?

I am actually working on a new update based on a recent version of cordova-sqlite-storage. I hope to have it ready within the next few days or so. I am using create-react-native-module so that it should "just work" with normal automatic installation.

I just posted the following project that uses SQLite 3.26.0 to support the transaction-based SQLite functionality on Android and iOS: https://github.com/brodybits/react-native-sqlite-plugin-legacy-support
It is based on a very recent release of cordova-sqlite-storage, working on Android and iOS only. The automatic installation should "just work" using Yarn. Note that it does not include some features such as Promise API, pre-populated databases, or ATTACH/DETACH API.
I would like to leave it as an open question whether or not it makes sense to integrate my new work more closely with this project. If not, I will look into supporting Cordova and React Native from almost the same code base moving forward. In any case I would like to express my gratitude to @andpor and others for the work in implementing and supporting this project over the past several years.

Hey @brodybits and @andpor this may be more or less related, but we have been using this lib on ios for a while and made use of SQLite's JSON1 extension (json_object, json_group_array, ...), which has work out of box on iOS. Now we are porting the app to Android and realized that the old version of SQLite provided by Android does not include the json extension.
Reading this thread I believe you have updated SQLite on the new-native-sqlite-libs branch, but that will probably not change anything about the JSON extension, will it?
I am considering using https://github.com/requery/sqlite-android which has it built in and seems to be a drop-in replacement for android.database.sqlite.SQLiteDatabase.
A little pointer in the right direction would be highly appreciated.

@AndreasKlein I am not actively supporting this project, I made https://github.com/xpbrew/react-native-sqlite-plugin-legacy-support to support SQLite updates on React Native. I raised https://github.com/xpbrew/react-native-sqlite-plugin-legacy-support/issues/1 to support JSON1 on that project. I hope to do this in the near future.

@AndreasKlein I tried to update android version to use https://github.com/requery/sqlite-android. I think it looks awesome! As I understood they already support built native libraries packaged to AAR format.
But I couldn't even be able just to build / compile android project using Android Studio. So not sure how to test modifications.
If anyone with better native experience could try to use sqlite-android?
They provide fresh sqlite version with Android wrappers.


Add support for symbols in palette for QOL

This PR adds an option to show symbols on the palette, just like how numbers are currently used. It's a small QOL upgrade since sometimes it can be hard to realize what color the symbol means since some shades are pretty similar.

I made a custom font that maps characters to the symbols. Right now, only the 34 symbols from the palette are mapped because that's all I had access to, but I could add more if needed.
The font also includes the kanji style that Clueless can generate mapped to hiragana characters. They're not implemented since pxls doesn't generate templates with those, but I left them in just in case someone wants to use them via a userscript or something similar.

I just realized vscode auto-formatted on save and index.handlebars and style.css make the PR 1.4k in changes just because of that :laughing:


Add ability to add Prefix for Wind presets

Would it be possible to add the ability to the Wind preset docs pages to add a prefix?
We use the tailwind prefix option, and it's quite tedious now to copypaste the preset, and then manually add the prefix. It would be nice if this could be added automatically.

Hi,
For now, we don't think it. But, I made some changes in mergeProps option of ptOptions. I think you can use output class string and then add prefix to each class part. https://github.com/primefaces/primevue/issues/4707#issuecomment-1914607040
const addPrefix = (classes) => {
     return classes?.spit(' ').map((c) => ....).join(' '); // you can update this block according to your needs.
}

const customMergeProps = (globalPTProps = {}, selfPTProps = {}, datasets) => {
   /*
    * - mergeProps from Vue package
    */
   const mergedProps = Vue.mergeProps(globalPTProps, selfPTProps, datasets);
   const newClassesWithPrefix = addPrefix(mergedProps?.class);

    mergedProps.class = newClassesWithPrefix;

    return mergedProps;
}

Best Regards,


Need Configuration suggestion

Hello,
Looking to encode below four simulcast avc layers.
90p@6 fps
180p@12 fps
350p@24 fps
720p@30 fps
Currently i am trying with 4 temporal layers but seems fps difference must be in power of 2.
Is there any way to achieve by configuration? Or need to modify code at PrepareEncodeFrame in encoder_ext.cpp to achieve desire frame rate?
Thanks,
Parag

Currently it is not allowed to encode with non-dyadic temporal settings, either by configuration or by simply modifying the code.

huili2 Thanks for quick reply,
I don't care about temporal layer. I saw that bitratecontroler do skip frame for that layer when bw  overshoot.  Can we use same logic to control desire fps per special layer?

The logic works, but it has not been implemented yet. Anyway bitrate control is more important in many cases.

If no update, will close this days afterwards.

I believes FPS does play critical role when it comes to rendering. And
could be good feature to add in upcoming release. Do you see any
possibilities?
Can I convert this ticket in to feature request? Else feel free to close it.
Thanks,
Parag Patel
On Mar 13, 2017 6:31 PM, "huili2"<EMAIL_ADDRESS>wrote:

If no update, will close this days afterwards.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cisco/openh264/issues/2667#issuecomment-286055972,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA15esuY7jgPMR1jQBkvIlbGaZT6HMZDks5rlQz3gaJpZM4MQeA-
.

I turned label to be "enhancement" to see if anybody is willing to contribute on this :)


add qsirecon --recon-only option to documentation

The flag --recon-only should be included in the reconstruction.rst documentation. I'm not sure where in that file would be the best place, but if someone wants to point to a good place to include it, I can take a stab and put in a PR.

Thanks for opening an issue on this! The documentation is in docs/reconstruction.rst, a PR would be greatly appreciated.  Please also add yourself to .zenodo.json

that should be fixed with #628


[cocoon] Broken builds navigate to builders, not the broken build

description
I've noticed that when clicking on broken builds in cocoon it will frequently jump to the builders website instead of displaying the popup that will allow you to navigate to the actual error.
workaround
I found that resizing the web browser window will sometimes allow you to get the popup behavior if you are getting the "navigate to builders" behavior.
screenshot

Another clue is that the "navigate to builders" behavior is the one you should get when clicking on a columns header.  The erroneous "navigate to builders" may only happen on failures that are in the first couple of rows of a column.

This looks like https://github.com/flutter/flutter/issues/145849, but one row further down than usual.


Image insertion dialog does not work properly

There is an issue with inserting images. After adding an image URL, you can insert the image by pressing Enter or Return. However, the blue button does not work.

Thank you for the report and for the PR! I pushed a fix for it, the automation should pick it up to a new release in a few minutes.


RiMajol

https://vimeo.com/690286853

Just keep in mind that all the respository have similar functions. Thanks.


go.dev: search can show "zero results" on an exact package match

What did you do?
I typed a full package url into the search box at go.dev, hoping to go to a particular package:

What did you expect to see?
I expected to either go directly to that package, or for that package to be a link in the search results.
What did you see instead?

/cc @julieqiu

@hunterloftis I wasn't able to reproduce that bug - visiting https://pkg.go.dev/search?q=github.com%2Fhunterloftis%2Fstorj%2Frelay redirects me to https://pkg.go.dev/github.com/hunterloftis/storj/relay?tab=doc.
Would you mind verifying if we are looking at the same URL?

It looks like the first version of this package was only indexed a few hours ago.
https://index.golang.org/index?since=2020-02-07T00:00:00.000000Z
https://pkg.go.dev/github.com/hunterloftis/storj/relay?tab=versions
So it's likely that when this was first searched, we didn't have it.

Thanks for trying to reproduce! I guess the search system index is a little
behind the actual archive.
It’s not a big deal but I wouldn’t be surprised if others run into the same
issue as they are publishing packages and trying to verify them on go.dev.
On Fri, Feb 7, 2020 at 2:03 PM findleyr<EMAIL_ADDRESS>wrote:

It looks like the first version of this package was only indexed a few
hours ago.
https://index.golang.org/index?since=2020-02-07T00:00:00.000000Z
https://pkg.go.dev/github.com/hunterloftis/storj/relay?tab=versions
So it's likely that when this was first searched, we didn't have it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/37111?email_source=notifications&email_token=AACY7VMHF3URXHEWA5T23N3RBWWAJA5CNFSM4KRQZV32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELEF56I#issuecomment-583556857,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACY7VPHW72GMFZ2QPSBCU3RBWWAJANCNFSM4KRQZV3Q
.

--

from mobile

Closing this issue as a duplicate of #37026.


Migrate UserLoggedIn Activity Alerts to Alert Policies

Hello,
according to the documentation Activity Alerts are deprecated. They should be migrated to Alert Policies. How can Office 365 E3 tenants convert activities that are missing in Alert Policies from Activity Alerts? E. g. UserLoggedIn activity exists in Activity Alerts but doesn't exist in Alert Policies.
1st and 2nd level Support doesn't have a solution beside buying a higher/additional license to be able to use Alert Policies in Cloud App Security panel. They can't help much more than this as that feature is supported by the Azure support team which can't be contacted as an Office 365 admin without buying a support plan.
Related to this:

https://office365.uservoice.com/forums/289138-office-365-security-compliance/suggestions/34347670-activity-alerts-deprecating-but-new-alert-polici

Thank you for your help!

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

ID: 9f2879ba-e58e-cd47-f488-10d153c31418
Version Independent ID: 391a2c05-d63d-e84e-7c7d-80c3b3518419
Content: Alert policies in the security and compliance centers - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/alert-policies.md
Service: o365-seccomp
GitHub Login: @markjjo
Microsoft Alias: markjjo

@GiantCrocodile As I'm sure you know,  in the UI, you can create custom alert policies only for the activities in the Activities Is dropdown list. You might try using the New-ProtectionAlert cmdlet; see Example 1.
As you point out in the link to the Office Voice, this feedback has been provided to the engineering team.

@markjjo I will check out that cmdlet. Thank you for this information!
Is it correct that when Activitiy Alerts are removed, the Activity Alerts created via the button in the Audit Log Search page are still working and that the Activity Alerts of the Cloud App Security panel are independent from the deprecated ones or are all of these policies with the same name being based on the deprecated feature?

@ Apologies, this is confusing. IMO, the "New alert policy" button on the audit log search page should have been removed a long time ago. This button does not create alert policies (New-ProtectionAlert). It lets you create an activity alert (New-ActivityAlert), which are being deprecated as you cited. I imagine existing activity alerts alerts will continue to work until they don't, but at some point you probably won't be able to create new ones.
I'm not very familiar with Cloud App Security alerts. But I'm pretty sure they are not the same as activity alerts. CAS alerts are triggered by CAS policies. And you can view CAS alerts on the Alerts page center. But these aren't activity alerts, they are CAS alerts triggered by CAS policies. See https://docs.microsoft.com/en-us/microsoft-365/compliance/alert-policies?view=o365-worldwide#viewing-cloud-app-security-alerts

Thanks for the great details @markjjo! This helped with better understanding the other information from the ongoing service request. When we find a feasible solution, I will post it here for other people with the same requirement. Right now, Cloud App Security isn't working as expected so I can't say more at the moment.

Microsoft provided a solution for which you need an extra license as it's a standalone product: Activity Policies of Cloud App Security. It works.


Error after login.

The app does'nt work since some cookbook updates.
The code must be corrected to remove some unused values.
I have make the changes and all is fine now and i can commit them now if you want.

Not sure if this is the error I'm seeing since there was no info, but I am getting the following...
Categories could not be loaded.  Make sure the Cookbook plugin is installed on this Nextcloud Instance!
Category load failed: Exception: FormatException: Unexpected character (at character 1)

Yes this is the issue.
This is due to the links hardcoded in the app about API. The dev include the API v1 but it is not used by the cookbook nextcloud pluggin.
I have made all the changes and compiled the new app ans all is working again.

Wouldn't you fork, make changes in your fork, then make a pull request into this one?

@airbat If you have some code to share please create a PR i will gladly look at what you have changed.

Hi @airbat can you still reproduce this issue with the app version 0.7.9 and the cookbook version 0.10.2 on your nextxloud?
There have been a lot of changes regarding the api recently.
If you are still facing the issue you could try the current develop branch?
Lastly please publish a log or the patch you've made. If you need assistance in how to achieve this just ask and I'll help.
Otherwise I'll close this issue with the next release.

My Nextcloud instance has Cookbook version 0.10.2 on it, the latest version, and your app still gives the same errors as it has for a while.
Categories could not be loaded. Make sure the Cookbook plugin is installed on this Nextcloud Instance!
Category load failed: Exception: FormatException: Unexpected character (at character 1) < ! DOCTYPE HTML >

Ok closing this as no further issues are found/reproducible.
If this still occurs on the latest app and cookbook version please open a new issue.


You shoud start a vanilla Isaac Sim and open your custom USD file.

          You shoud start a vanilla Isaac Sim and open your custom USD file.

Then you will need to add Rigid Body API to each link of the object, and add Collision Body API to each collision mesh of each link.
Originally posted by @ChengshuLi in https://github.com/StanfordVL/OmniGibson/issues/973#issuecomment-2411985188

Thank you for your reply.
When we add Rigid Body API to the object in a vanilla isaac sim, the steps as below:
1 open one_leg.usd file
2. select  the object
3. add -->Physics -->Rigid Body with Colliders Preset
4. save the .usd file
as show the video
2024年10月15日 屏幕视频 19时07分52秒.webm
Then we can generate real collision effect in isaac sim, as show below:
2024年10月15日 屏幕视频 19时19分54秒.webm
Then we load it  in omnigibson, the object becomes transparent, but the effect can be seen in the UI by displaying the physical collision, as shown in the video below:
Screencast from 2024年10月14日 15时38分28秒.webm

Now I don't know if there is a problem adding the rigid body api in isaac sim or a problem loading the .usd in omnigibson or if there is a problem with the original .usd file that ultimately leads to incorrect results.
You can verify the result if you can, the original .usd file is here: https://github.com/clvrai/furniture-bench/tree/main/furniture_bench/assets/furniture/mesh/square_table
I hope to get your reply and guidance, thanks again~

Hello.
I found that in the .usd file saved after adding the rigid collision api to an object in isaac sim, the visual ->Purposes for each mesh is default; as show the bellow image:

But when loaded in omnigibson, this property changes to guide, so that only the collision lines are visible, not the meshes. as show the bellow image:

So, did omnigibson do something to the .usd file that caused the property to change?
What should I do to keep the original properties?
Hope to get your reply and answer, thanks again.


prompts edit + cerbathon category

Messed with the JS for the Cerbathon a bit to add the Cerbathon prompts, fingers crossed that doesn't break anything. Maybe double check on that though.
Aside from that, added a few prompts and clarified one of them.

Suggestions added! Looks good to me so far


Separating files.

Find out, how to organize all files.

Files separeted with a5abf7b4ef2d10d1bfec30638cb95104082f5b7c, closing this for now.


polish docs

polish docs

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.evanljp seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Compile error for double colon

I was writing a proc macro using the syn library and had the following code:
structstruck::strike! {
    struct ItemDefine {
        semantic_token: keywords::semantic,
                                ^---- errors here
        ident: Ident,
        semantic_fields: struct {
            brace_token: token::Brace,
                              ^---- errors here
            fields: Vec<SemanticField>,
        }
    }
}

In the output I see:

structstruck error: Colon in top level of type expression. Did you forget a comma somewhere?

This should be valid I was able to do this in my structs before nesting them.
PS. I am getting around this by using type Brace = token::Brace, but it makes things harder to read.

Uff, dumb mistake on my part when trying to fix #4. Can you verify that your code works with structstruck 0.4.1?

I was playing around in my local machine so I don't have the code anymore, but from the test case in the commit  the fix looks good.