HBASE-26088 Fix thread leaks in conn#getBufferedMutator(tableName) method call

@saintstack @anoopsjohn @apurtell This PR is just for branch-2. The behavior is different in master branch. In master brach, there is only AsyncConnection and I don't see it creating a new ThreadPoolExecutor but still studying master code base. Please review.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 43s
branch-2 passed

+1 :green_heart:
compile
0m 26s
branch-2 passed

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

+1 :green_heart:
javadoc
0m 27s
branch-2 passed

_ Patch Compile Tests _

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

+1 :green_heart:
compile
0m 27s
the patch passed

+1 :green_heart:
javac
0m 27s
the patch passed

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

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

_ Other Tests _

+1 :green_heart:
unit
2m 22s
hbase-client in the patch passed.

25m 12s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / cabf0dc51d

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

Max. process+thread count
346 (vs. ulimit of 12500)

modules
C: hbase-client U: hbase-client

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 19s
branch-2 passed

+1 :green_heart:
compile
0m 31s
branch-2 passed

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

+1 :green_heart:
javadoc
0m 30s
branch-2 passed

_ Patch Compile Tests _

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

+1 :green_heart:
compile
0m 30s
the patch passed

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

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

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

_ Other Tests _

+1 :green_heart:
unit
2m 42s
hbase-client in the patch passed.

29m 11s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux d9a81630bbf8 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / cabf0dc51d

Default Java
AdoptOpenJDK-11.0.10+9

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

Max. process+thread count
292 (vs. ulimit of 12500)

modules
C: hbase-client U: hbase-client

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 41s
branch-2 passed

+1 :green_heart:
compile
1m 22s
branch-2 passed

+1 :green_heart:
checkstyle
0m 49s
branch-2 passed

+1 :green_heart:
spotbugs
1m 41s
branch-2 passed

_ Patch Compile Tests _

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

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

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

+1 :green_heart:
checkstyle
0m 41s
the patch passed

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

+1 :green_heart:
hadoopcheck
14m 36s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
1m 38s
the patch passed

_ Other Tests _

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

42m 52s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile

uname
Linux b3d2c31b3cad 4.15.0-142-generic #146-Ubuntu SMP Tue Apr 13 01:11:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / cabf0dc51d

Default Java
AdoptOpenJDK-1.8.0_282-b08

Max. process+thread count
86 (vs. ulimit of 12500)

modules
C: hbase-client U: hbase-client

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

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 59s
branch-2 passed

+1 :green_heart:
compile
0m 33s
branch-2 passed

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

+1 :green_heart:
javadoc
0m 28s
branch-2 passed

_ Patch Compile Tests _

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

+1 :green_heart:
compile
0m 32s
the patch passed

+1 :green_heart:
javac
0m 32s
the patch passed

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

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

_ Other Tests _

+1 :green_heart:
unit
2m 50s
hbase-client in the patch passed.

29m  0s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux f46173bf6ac8 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / cabf0dc51d

Default Java
AdoptOpenJDK-11.0.10+9

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

Max. process+thread count
298 (vs. ulimit of 12500)

modules
C: hbase-client U: hbase-client

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m  5s
Docker mode activated.

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 47s
branch-2 passed

+1 :green_heart:
compile
0m 32s
branch-2 passed

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

+1 :green_heart:
javadoc
0m 30s
branch-2 passed

_ Patch Compile Tests _

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

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

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

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

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

_ Other Tests _

+1 :green_heart:
unit
2m 56s
hbase-client in the patch passed.

31m 13s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 88ca43cee7ff 4.15.0-142-generic #146-Ubuntu SMP Tue Apr 13 01:11:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / cabf0dc51d

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

Max. process+thread count
236 (vs. ulimit of 12500)

modules
C: hbase-client U: hbase-client

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

Just a nit.
This issue is not there in branch-1 anyways right?
So for all branch-2 branches, we are sticking with the existing behaviour to have the compatibility and correcting the Javadoc. Pls mark this issue accordingly and we can address master branch (3.x also?) in another task. There we can even change to use the current javadoc way of using Connection's pool (If bug is there still)

branch-1 seems no such issue, because there's no this flag cleanupPoolOnClose, so the pool no matter created by default or provided by applications will be shutdown

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 19s
branch-2 passed

+1 :green_heart:
compile
0m 31s
branch-2 passed

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

+1 :green_heart:
javadoc
0m 30s
branch-2 passed

_ Patch Compile Tests _

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

+1 :green_heart:
compile
0m 31s
the patch passed

+1 :green_heart:
javac
0m 31s
the patch passed

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

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

_ Other Tests _

+1 :green_heart:
unit
2m 49s
hbase-client in the patch passed.

28m 54s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / cabf0dc51d

Default Java
AdoptOpenJDK-11.0.10+9

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

Max. process+thread count
302 (vs. ulimit of 12500)

modules
C: hbase-client U: hbase-client

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

_ Prechecks _

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

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

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

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 26s
branch-2 passed

+1 :green_heart:
compile
1m  3s
branch-2 passed

+1 :green_heart:
checkstyle
0m 33s
branch-2 passed

+1 :green_heart:
spotbugs
1m  6s
branch-2 passed

_ Patch Compile Tests _

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

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

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

+1 :green_heart:
checkstyle
0m 32s
the patch passed

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

+1 :green_heart:
hadoopcheck
11m 44s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
1m 25s
the patch passed

_ Other Tests _

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

32m 39s

Subsystem
Report/Notes

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

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

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti checkstyle compile

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

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / cabf0dc51d

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

modules
C: hbase-client U: hbase-client

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

versions
git=2.17.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

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

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

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
5m 12s
branch-2 passed

+1 :green_heart:
compile
0m 38s
branch-2 passed

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

+1 :green_heart:
javadoc
0m 31s
branch-2 passed

_ Patch Compile Tests _

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

+1 :green_heart:
compile
0m 33s
the patch passed

+1 :green_heart:
javac
0m 33s
the patch passed

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

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

_ Other Tests _

+1 :green_heart:
unit
3m  1s
hbase-client in the patch passed.

32m 53s

Subsystem
Report/Notes

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

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

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux f51b88b7ae3c 4.15.0-142-generic #146-Ubuntu SMP Tue Apr 13 01:11:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / cabf0dc51d

Default Java
AdoptOpenJDK-1.8.0_282-b08

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

Max. process+thread count
233 (vs. ulimit of 12500)

modules
C: hbase-client U: hbase-client

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

versions
git=2.17.1 maven=3.6.3

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

This message was automatically generated.


Version without goal

Currently, when a goal is reached, the game is cleared and the game is over, but a version that does not end the game needs to be added.
Consider rendering for large numbers as well

If specifying a very large number , the game is virtually never over.


Documentation lesson to use markdown instead of Rst

The transformation is not yet fully finished and tested
Still to do:

index.rst -> md to be done / found out if it works
labeling math equations
more testing
But I still suggest to merge these changes so that exercise leaders can see that we will use (at least mainly) markdown for the sphinx exercise and not rst.
I will still work on the to-dos before second week of the workshop.

What do you think?

Please merge if you think it is ready and let's iterate then, so that exercise leaders (if they now check the exercises) get to see markdown instead of rst. (On phone only for the moment so cannot (dare not) merge myself 😅)

Can somebody resolve the suggestions? It is not clear to me whether they have been applied or not.


[HELP]  Use module path

Hi everyone,
I'd like to use this plugin in combination with module path in webpack, I mean use import Test from "components/Test";  instead of  import Test from "./src/components/Test";.
It is a expo project and  I configured webpack to load the module from  the ./src directory
const createExpoWebpackConfigAsync = require("@expo/webpack-config"); const path = require("path"); module.exports = async function (env, argv) {     const config = await createExpoWebpackConfigAsync(env, argv);     config.resolve.modules = [path.resolve("./src"), "node_modules"];     return config; };
It works but the eslint show me the error:  "Cannot find module  "components/Test" or its corresponding type declaration'
I added into the eslint configuration ( in my package.json) the webpack resolver
"settings": {             "import/resolver": {                 "webpack": "./webpack.config.js"             }         }
But it doesn't work, what should I do ?

Do you have the webpack resolver installed, as well?

Yes,  i have this package
"eslint-import-resolver-webpack": "^0.13.2"

Can you try providing an absolute path to your webpack config, just in case?
You’ll also still want the node resolver in your settings, after webpack.

Oh wait - your webpack config is async. That won’t ever work, because eslint requires everything to work sync.

Isn't there a possible solution then?

The only one i know of would be making a separate, sync webpack config , that shares code with the async one, that handles the aliases - and use that for eslint.

Due to  I am using expo I have to use createExpoWebpackConfigAsync  ( https://docs.expo.dev/guides/customizing-webpack/#example).
This function returns a config object ... maybe I can explore this object and copy the necessary properties and paste it into the eslint config but I don't know which properties are.
Do you know which properties are?

I’m afraid i don’t. It might be useful to file an issue for expo to provide a sync webpack config for use by eslint.


feat: step definitions related to the feature file

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


errored out with list of local files

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2016.06.25. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x ] I've verified and I assure that I'm running youtube-dl 2016.06.25

Before submitting an issue make sure you have:

[x ] At least skimmed through README and most notably FAQ and BUGS sections
[x ] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add -v flag to your command line you run youtube-dl with, copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
$ youtube-dl -v <your command line>
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'http://www.youtube.com/watch?v=BaW_jenozKcj']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2016.06.25
[debug] Python version 2.7.11 - Windows-2003Server-5.2.3790-SP2
[debug] exe versions: ffmpeg N-75573-g1d0487f, ffprobe N-75573-g1d0487f, rtmpdump 2.4
[debug] Proxy map: {}
...
<end of log>

[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['-F', 'http://www.nationallibertyalliance.org/common-law', '-v']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2016.06.25
[debug] Python version 3.4.4 - Windows-7-6.1.7600-SP0
[debug] exe versions: none
[debug] Proxy map: {}
[generic] common-law: Requesting header
WARNING: Falling back on generic information extractor.
[generic] common-law: Downloading webpage
Traceback (most recent call last):
File "main.py", line 19, in
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpdy42tioh\build\youtube_dl_init_.py", line 420, in main
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpdy42tioh\build\youtube_dl_init_.py", line 410, in _real_main
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpdy42tioh\build\youtube_dl\YoutubeDL.py", line 1740, in download
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpdy42tioh\build\youtube_dl\YoutubeDL.py", line 676, in extract_info
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpdy42tioh\build\youtube_dl\extractor\common.py", line 343, in extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpdy42tioh\build\youtube_dl\extractor\generic.py", line 1412, in _real_extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpdy42tioh\build\youtube_dl\extractor\common.py", line 390, in _request_webpage
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpdy42tioh\build\youtube_dl\YoutubeDL.py", line 1950, in urlopen
File "C:\Python\Python34\lib\urllib\request.py", line 470, in open
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpdy42tioh\build\youtube_dl\utils.py", line 842, in http_response
File "C:\Python\Python34\lib\gzip.py", line 360, in read
File "C:\Python\Python34\lib\gzip.py", line 449, in _read
File "C:\Python\Python34\lib\gzip.py", line 482, in _read_eof
File "C:\Python\Python34\lib\gzip.py", line 286, in _read_exact
EOFError: Compressed file ended before the end-of-stream marker was reached
If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: https://www.youtube.com/watch?v=BaW_jenozKc
Single video: https://youtu.be/BaW_jenozKc
Playlist: https://www.youtube.com/playlist?list=PL4lCao7KL_QFVb7Iudeipvc2BCavECqzc

Description of your issue, suggested solution and other information
Explanation of your issue in arbitrary form goes here. Please make sure the description is worded well enough to be understood. Provide as much context and examples as possible.
If work on your issue required an account credentials please provide them or explain how one can obtain them.
Wanted to see what files could be recognized from the provided URL knowing it would use the [generic] extractor, hoped I could pull the mp3s.  Did not expect it to error out with a list of local files.  After running the command, noted neither C:/User/dst nor C:\Python does not exist. FYI.  Have C++ 2010 redistributable installed.

Looks like network problems. Could you try more times?

Tried several more times.  Same response.  I can point youtube-dl at any youtube URL and it works.  I don't have a network problem anywhere else, just this particular site using this command.  Could the site block this request if it sees youtube-dl?

Could the site block this request if it sees youtube-dl?

I don't think so as the same command runs fine here.


How to install?

I'm starting out with Astro, but I can't seem to parse the docs as how to install this integration.

Install it with npm, yarn, etc. E.g. npm install astro-loader-obsidian --save

Alright, thanks.


portal connection render for DOM elements

Is your feature request related to a problem? Please describe.
Improvement : Performance leak
use case: Table (a lot of cells that use tooltip)
When we use original <table> <tr> (default browser behaviour) element we should use portal otherwise it will overflowed

portal property create DOM element for each float element

Describe the solution you'd like
How it can be improved ? for example: create portal connection to Float only if element show, or create just one portal that can be connect for each Float
Describe alternatives you've considered
^_

hey @ycs77 do you have any idea how it would be optimised ?

Hi @d90375, sorry I have no current plans to resolve this issue.
I created this package to float the Headless UI component quickly, and non-invasive to the Headless UI, just supported floating the basic usage for the Headless UI example. This change will increase the complexity of this package.  So if you want to use the tooltip, I suggest using Tippy.js.


vagrant: add kubeconfig files to support KUBECONFIG path and vagrant-…

…{single,multi} clusters

@aaronlevy ping.

How will you be using this / can we add some documentation on how we expect these to be used?
We currently document creating these via kubectl config set-foo commands: https://github.com/coreos/coreos-kubernetes/blob/master/Documentation/kubernetes-on-vagrant-single.md#configure-kubectl
This change seems useful, but may be worth describing how they can be used vs using the commands to modify existing config.

@aaronlevy docs added. also i have both the clusters named "vagrant" to be consistent with the kubectl config set-* instructions- the assumption is people will be using one or the other?

I actually get annoyed with the name being "vagrant" for both single/multi-node configs because I often find myself switching between. In the case of the custom KUBECONFIG path, it doesn't matter because there is only one user/cluster/context per file.
I'd like to see it change to something like "vagrant-multi" in the case of updating existing kubeconfig, so the settings don't stomp on eachother. But that can be left to a different PR

I agree w/ aaron regarding differentiation of multi- and single-node kubeconfigs. Please do that in this PR.

@colhom Were you able to make the requested changes?

@bcwaldon changes made

Made some comments RE consistency. Also once the changes are made, just sanity check that you are able to switch between contexts as expected and have it work for single/multi node clusters:
kubectl config use-context vagrant-single; kubectl get nodes
kubectl config use-context vagrant-multi; kubectl get nodes
KUBECONFIG=path/to/single kubectl get nodes
KUBECONFIG=path/to/multi kubectl get nodes

rebased/squashed. tested KUBECONFIG and kubectl approaches, everything checks out.

lgtm


Infinite Scroll Issue

The resultList is null for the infinite scroll example when the Next function gets called, can be replicated by loading up the InfiniteScroll.sln, searching "a", and scrolling down

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

ID: f8cde97a-8763-52e1-104c-8415f554c698
Version Independent ID: 2d93d797-a7e4-6e61-10d7-202d77501924
Content: C# tutorial on search results pagination - Azure Search
Content Source: articles/search/tutorial-csharp-paging.md
Service: search
GitHub Login: @PeterTurcan
Microsoft Alias: v-pettur

Hi @MHarrison22, thanks for the feedback! We are currently investigating and will update you shortly.

Also I'm seeing a similar issue with the typeahead solution, let me know and I can open an additional ticket

Upon further review we feel your feedback would be best received by the doc author to determine if an update to the current doc is necessary, or to create a new doc if they align with the feedback.

Hi @MHarrison22
I wrote the tutorial. Can you give me a few more details - a screenshot of the error/exact steps to replicate/expect behavior? The hotel data set is for demo purposes only, and is small (50), so will run to the end in a few scrolls of infinite scrolling, so perhaps the issue is "by design" but happy to investigate if you have found an issue.

Hey @PeterTurcan , thanks for reaching out, for example, looking at this solution:
https://github.com/Azure-Samples/azure-search-dotnet-samples/tree/master/create-first-app/3-add-typeahead
Once I run the app from VS 2019 Professional I'm seeing this front end error inside of a chrome incognito window:

@MHarrison22
OK, got it. Are you able to verify the apps work as expected if you use Microsoft Edge?

Same issue in Edge as well it looks like:

@MHarrison22
I am finding an issue with SessionState.  If this is enabled, TempData works in the MVC code, but if it is not enabled TempData is not persisted, so the app fails. I am not savvy enough with this setting yet to be sure of how to be certain it is set. Not sure either if this is the issue you are seeing!

Hmm, what steps did you take to enable SessionState?

@PeterTurcan @MHarrison22
TempData not being persisted is a known issue in .NET Core 2.2 MVC apps. It is caused by an incorrect order of method calls in Startup.cs . This is a template issue; the tutorial does not touch Startup.cs .
The fix is to edit the Configure(..., ...) method in Startup.cs : move app.UseCookiePolicy() below app.UseMvc(...) .
More detailed instructions can be found here: https://stackoverflow.com/questions/41734039/tempdata-null-in-asp-net-core
By the way, .NET Core 3.0 MVC template uses a different (method) structure, which avoids the problem altogether.

@MHarrison22 - thanks for finding the issue
@MichelSchols - thanks for pointing out the fix
I will suggest the tutorial is updated with a note mentioning the known issue, and pointing to the article suggested above, and then that this issue is marked as Closed.

Peter

@MHarrison22  I modified all of the Startup.cs files to use the reordered methods and then noted the change in the readme file.  Please let me know if you find other issues.
All of the samples work for me although for the infinite scrolling sample, I found that a simple F5 was not enough. Instead, I had to select the program name instead of IIS Express to run it.  No one else has reported that issue so for now, I'll assume it's not a problem.

I'm going to mark this as closed but feel free to reopen if you think I missed something
#please-close


Understand the output of Securify when analyzing runtime bin

Hello, I am writing to ask a quick question regarding how to interpret the output of Security.
For instance when executing the following command and getting the output:
➜  securify git:(master) java -jar build/libs/securify.jar -fh src/test/resources/solidity/transaction-reordering.bin.hex
  Attempt to decompile the contract with methods...
  Success. Inlining methods...
  Propagating constants...
  Verifying patterns...

So what does that mean? Where can I find the corresponding results, something like whether this is vulnerable towards reentracy attack, towards TOD attack (violation or not).
I tried to append the --json option to the command but nothing happens.
Also, I tried to run a run-time EVM bytecode on my local machine and got the following output::
➜  securify git:(master) java -jar build/libs/securify.jar -fh /opt/wangshua/work/evm_analyzer_folder/evm_analyzer_1/scripts/contract_bins/0x068abd01efff87943c6853abff3d20edfa9f9a18.bin
  Attempt to decompile the contract with methods...
  Failed to decompile methods. Attempt to decompile the contract without identifying methods...
  Propagating constants...
  Verifying patterns...

Somehow the "function" is not recognized. Is it still OK to use Securify, for such cases? Thanks!

Hi @ireneGP ,
thanks a lot for your question. This was unclear indeed. Please use:
java -jar build/libs/securify.jar -fh src/test/resources/solidity/transaction-reordering.bin.hex --livestatusfile /tmp/result.json

We also modified the usage message to clarify this.
Please let us know if it shouldn't work for you.

@ritzdorf Thank you so much for your prompt reply! I appreciate it very much.
Just one followup question to understand the json output. So basically I got the following output by analyzing my contract (a local EVM runtime bytecode):
{
  "decompiled": true,
  "securifyErrors": {
    "errors": []
  },
  "finished": true,
  "patternResults": {
    "DAO": {
      "completed": true,
      "hasViolations": false,
      "hasWarnings": false,
      "hasSafe": false,
      "hasConflicts": false,
      "violations": [],
      "warnings": [],
      "safe": [],
      "conflicts": []
    },
    "DAOConstantGas": {
      "completed": true,
      "hasViolations": true,
      "hasWarnings": false,
      "hasSafe": false,
      "hasConflicts": false,
      "violations": [
        354,
        866,
        831,
        777
      ],
      "warnings": [],
      "safe": [],
      "conflicts": []
    },
    "LockedEther": {
      "completed": true,
      "hasViolations": false,
      "hasWarnings": false,
      "hasSafe": true,
      "hasConflicts": false,
      "violations": [],
      "warnings": [],
      "safe": [
        1
      ],
      "conflicts": []
    },
    "MissingInputValidation": {
      "completed": true,
      "error": "not supported",
      "hasViolations": false,
      "hasWarnings": false,
      "hasSafe": false,
      "hasConflicts": false,
      "violations": [],
      "warnings": [],
      "safe": [],
      "conflicts": []
    },
    "RepeatedCall": {
      "completed": true,
      "hasViolations": false,
      "hasWarnings": false,
      "hasSafe": false,
      "hasConflicts": false,
      "violations": [],
      "warnings": [],
      "safe": [],
      "conflicts": []
    },
    "TODAmount": {
      "completed": true,
      "hasViolations": true,
      "hasWarnings": true,
      "hasSafe": false,
      "hasConflicts": false,
      "violations": [
        866,
        831
      ],
      "warnings": [
        354,
        777
      ],
      "safe": [],
      "conflicts": []
    },
    "TODReceiver": {
      "completed": true,
      "hasViolations": true,
      "hasWarnings": true,
      "hasSafe": false,
      "hasConflicts": false,
      "violations": [
        866,
        831
      ],
      "warnings": [
        354,
        777
      ],
      "safe": [],
      "conflicts": []
    },
    "UnhandledException": {
      "completed": true,
      "hasViolations": true,
      "hasWarnings": false,
      "hasSafe": false,
      "hasConflicts": false,
      "violations": [
        354,
        866,
        831,
        777
      ],
      "warnings": [],
      "safe": [],
      "conflicts": []
    },
    "UnrestrictedEtherFlow": {
      "completed": true,
      "hasViolations": false,
      "hasWarnings": true,
      "hasSafe": true,
      "hasConflicts": false,
      "violations": [],
      "warnings": [
        354,
        777
      ],
      "safe": [
        866,
        831
      ],
      "conflicts": []
    },
    "UnrestrictedWrite": {
      "completed": true,
      "hasViolations": true,
      "hasWarnings": true,
      "hasSafe": true,
      "hasConflicts": false,
      "violations": [
        251,
        365,
        374,
        454,
        464,
        473,
        523,
        532,
        615,
        669,
        698
      ],
      "warnings": [
        788,
        797
      ],
      "safe": [
        104,
        115,
        202,
        411,
        871,
        836
      ],
      "conflicts": []
    }
  }
}

My questions are:

what does it mean for "errors": [] in the "securifyErrors"? Does it mean this contract is safe?
Note that I found that DAOConstantGas and TODAmount  has some "violations"..

Where are the "bad randomness/dependence on system properties" issue and "reentrancy issue"?

Thanks a lot! I look forward to hearing from you!

"errors" will report internal securify errors, e.g. failed decompilation. Obviously we try to minimize those. Let us know if you encounter some of those.
You can add --descriptions to get more information, e.g. the patterns DAO and DAOConstantGas check for reentrancy-related issues.

@ritzdorf  Thank you! Then may I ask what about the dependence on timestamp or other system properties? I somehow got the impression that Securify would also capture that.

@ireneGP We are working on such patterns. And will release them once they are stable enough. You can try out some initial version under https://securify.ch

@ritzdorf  Thank you! One followup question on the "violation patterns" vs. "warning patterns". How should I interpret this? In case I encountered a "warning pattern", can I interpret it as "vulnerable" or so?

@ireneGP violation implies that the security property is violated, while warning indicates that it may be a false positive. For full details on that you can see Fig 2 in the tech report: https://files.sri.inf.ethz.ch/website/papers/ccs18-securify.pdf

@ptsankov  Thank you for the clarification. I am still a bit confused about the vulnerability pattern here, say, can Securify pinpoint DoS with (Unexpected) revert style vulnerability? I don't think the Handled Exception (HE) is what I am looking for here. Thanks!


[Bug] perl ssl test failed against centos 9 operating system

Cloudberry Database version
PostgreSQL 14.4 (Cloudberry Database 1.5.5+dev.65.g1481bf3e build 78672 commit:1481bf3e) (HashData Lightning 1.5.5+dev.65.g1481bf3e build 78672 commit:1481bf3e) on
x86_64-pc-linux-gnu, compiled by gcc (GCC) 11.4.1 20231218 (Red Hat 11.4.1-3), 64-bit compiled on Jul  2 2024 04:10:38
What happened
c/src/test/ssl/../../..' PG_REGRESS='/code/cbdb_src/src/test/ssl/../../../src/test/regress/pg_regress' /usr/bin/prove -I ../../../src/test/perl/ -I .  t/*.pl
t/001_ssltests.pl .. 6/110 # Looks like your test exited with 29 just after 7.
t/001_ssltests.pl .. Dubious, test returned 29 (wstat 7424, 0x1d00)
Failed 103/110 subtests
t/002_scram.pl ..... Dubious, test returned 29 (wstat 7424, 0x1d00)
No subtests run
Test Summary Report
t/001_ssltests.pl (Wstat: 7424 Tests: 7 Failed: 0)
Non-zero exit status: 29
Parse errors: Bad plan.  You planned 110 tests but ran 7.
t/002_scram.pl   (Wstat: 7424 Tests: 0 Failed: 0)
Non-zero exit status: 29
Parse errors: No plan found in TAP output
Files=2, Tests=7, 20 wallclock secs ( 0.02 usr  0.00 sys +  1.41 cusr  0.55 csys =  1.98 CPU)
Result: FAIL
make: *** [Makefile:196: installcheck] Error 1
What you think should happen instead
No response
How to reproduce
start and logon to <IP_ADDRESS>
su - gpadmin
gpstart
cd /code/cbdb_src/src/test/ssl
make installcheck
Operating System
centos9
Anything else
No response
Are you willing to submit PR?

[ ] Yes, I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct.

Hi Max,
There is incompatible change about security socket layer in CentOS 9, which cause ssl test failure.  Will talk to you later about it in our tomorrow meeting.

Hi @wenchaozhang-123,  from triage meeting,  Max mentioned you resolved similar issue before.  Would you please take a look at it?
We have reproducible environment <IP_ADDRESS> for diagnosis.

The issue is gone,  closing this issue.

As discussed with wenchao,  It appears PR #637 did not successfully disable this test,  reopen it for tracking.


RS(256, 384, 512) - no supports for these?

Does it support RS(256, 384, 512)? It seems it doesn't. Are you going to add this capacity soon?

These identifiers are RFC7518 identifiers for RSASSA-PKCS1-v1_5 using SHA-(256, 384, 512). The SHA2 hashes are implemented, and the DH/RSA implementation progress is tracked in #106.

Maybe you know what can I use instead of this library for RSA for now?

OpenSSL, probably.


Use ps -A when looking for PID of injected process.

On another PC, adb shell ps was showing nothing except for ps itself, which is same as default behavior on desktop ps.

Presumably this is device-specific because that's where ps runs, rather than PC specific?
Do you know if this parameter is supported on all relevant android/device versions? If it's unsupported on Android 4.0 or similar that's not important. Is there a risk that we run ps -A and just get an error from an unknown parameter?

I was actually using the same device on 2 different PCs (different distro versions), so its probably because of different adb versions. The software on the phone was exactly the same each time.
ps is an old standard tool, so Im fairly certain that parameter is widely supported too...

That seems strange :disappointed:.
I think in desktop ps, the parameter is lowercase -a for all processes, but looking at the source for android's custom ps the -A parameter has been around for a long time, so this should be safe to change.

FYI surprising nobody I found a case where ps will just print an error message about a bad PID if you pass -A as a parameter. Upon investigation it seems like the ps binary is provided by toolbox which doesn't support the param and not toybox which does, even though it's Android 7.0 which should be using toybox.
I think the solution is just to try both variants and hope one of them produces some results. Then when we find an android install that doesn't work with either version we can just add another variant.


[InterfaceGen] Print private/internal properties

All properties which contribute to the storage of a type should be
printed, and their names should be hidden from interfaces. Print them
with '_' as their name, and teach the parser to recognize these special
patterns when parsing interface files.
Partially resolves rdar://43810647

What’s the plan for properties that have internal types?

"Not covered by this PR" :-) I haven't passed along to Harlan the thing you told me about value witnesses, that if a struct has private types in its fields IRGen just gives up and always uses value witnesses. (Yes? No?)

Yes that is correct. We still need to know the size and alignment of the type though. I think the best solution for this and the class vtable layout issues is to include any referenced internal types in the interface output.

Do we want to rename them/their properties to avoid exposing private implementation details?

We'll have to for fileprivate types anyway, so we might as well everywhere.

I've added a test to make sure the layout doesn't change if the type is declared in this file, in another module, or in an interface file.

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 00d8908455a5759b21330f1e67a99396d35dfb02

Build failed
Swift Test Linux Platform
Git Sha - 00d8908455a5759b21330f1e67a99396d35dfb02

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 31b9b4bf6df93c301fe2a7c5d5f97738cc07dc9a

Build failed
Swift Test Linux Platform
Git Sha - 31b9b4bf6df93c301fe2a7c5d5f97738cc07dc9a

:boat:


✨ Create a new node context menu example.

Someone opened a discussion asking how to do node context menus, I thought it would make a handy little example. There's a sandbox link in the discussion if we decide we don't want something more permanent :)

💯


Another question: In WAS ND there are multiple app servers

Good afternoon, Dennis.
Dennis, could you tell us please, if we have WAS Network Deployment with 5 application servers (5 JVMs), server1, sererv2, etc. Of course, the .cfg file contains configuration for all 5 JVMS. We need to create a report ONLY for one JVM, let's say for server3. How can we do that? Not only that, Dennis if we need to compare server3 from one environment with server3 from a different environment, what steps do we need to take.
Thanks a lot, in advance.

Two compare entities from two cells, you need to run ConfigDump.py against each cell.  You would need to have ConfigReport.py pull in both .cfg files into the reporting either by placing them both in the same directory and running ConfigReport.py from that directory or by specifying them in the ConfigurationDumpFiles property.
To compare one server (you can compare one but it really is just a report of the configuration at that point), specify the following properties.
ReportList=MyReport
MyReport:ReportType=Server
MyReport:Title=My Report
MyReport:Clusters:1=
MyReport:Servers:1=MyCellName::MyServerName
MyReport:FileName=MyReport
To add in another server from another cell add the following properties.
MyReport:Servers:2=MyOtherCellName::MyOtherServerName
You can have any number of servers specified just make sure the ID is unique.  The IDs in the sample above are 1 & 2.

Thanks a lot, Dennis for your quick reply. The name of the Application server we'd like to create a report on is CAPSServer. This is what we tried in ConfigReport.properties
CAPSServer:ReportType=Server
CAPSServer:Title=CAPS Servers
CAPSServer:Clusters:1=
CAPSServer:Servers:1=CAPSCell::CAPSServer
CAPSServer:ReportList=All
#CAPSServer:ReportOnlyMismatched=All
it worked like a charm, it created a server report only for CAPSServer. But  when we try to produce a report for CAPSServer's Resources we used these properties
CAPSServer:ReportType=Server
CAPSServer:Title=CAPS Servers
CAPSServer:Clusters:1=
CAPSServer:Servers:1=CAPSCell::CAPSServer
CAPSServer:ReportList=Resources
CAPSServer:FileName=CAPS_Servers
#CAPSServer:ReportOnlyMismatched=All
The CAPS_Server report came out empty and Resources report contain 4 more application server that we're trying to eliminate. What would you suggest, Dennis.
Thanks a million once again.

The ReportList property within a report definition is not documented and not used the way you think it is.  It is for limiting the tables created in an HTML report for debugging and development purposes.  I need to change the name and remove it from the samples to avoid confusion.
If you are looking to run the built in Resources report, either don't specify the ReportList at all or specify ReportList=Resources.
If you are trying to create a custom resources report, it is similar syntax but REPORT_NAME:Type needs to be the resource type you want to compare (e.g. DataSource).  Also the selection syntax is a bit different as well.
Here is a sample I have in ConfigReport.properties
EJBTimerDataSource:ReportType=DataSource
EJBTimerDataSource:Title=EJB Timer DataSource
EJBTimerDataSource:Scope:1=Node
EJBTimerDataSource:Resources:1=.::.::DefaultEJBTimerDataSource
EJBTimerDataSource:FileName=EJBTimerDataSource
Note, unlike Server reports, a scope has to be specified and the ID ("1" in the sample above) needs to match.  A server does not have resources.  A resource may be scoped (only visible to) to a server, however.  This is how the configuration repository is structured.

Please reopen issue if you have additional questions.

Dennis, sorry for the late response, but thank you so much and have a great day!


Lightning Gateway backupability

Do we have a common seed for all the clients in the gateway and can we export it/recover from it? If not we should.

dev call: @joschisan reports that every client different seeds. Also, we use 64 bytes which can't be represented as BIP39 seed words.

sounds related: https://github.com/fedimint/fedimint/issues/4170

Also related to https://github.com/fedimint/fedimint/issues/2652. These 3 could probably be one issue.

Working this rn with @m1sterc001guy , moving to bip39 mnemonic and reusing all dpc's fanciness in the fedimint-client with a manual migration: gateway operator moves their ecash out, leaves the federation, rejoins with the automatically created new client derived from the mnemonic

If you do a manual migration you can also move all dbs into one via prefixes.

If you do a manual migration you can also move all client dbs into one via prefixes.

Yep, had the same idea, this is the plan.


Looking for contributors

Looking for maintainers/contributors to take over the project.
Unfortunately I have too many other commitments at the moment and am no longer actively doing objc development. So sadly I don't have the time to give Classy the time and attention it deserves.

Hey
We are interested in taking over this project since we did some pull requests to it in the past and our company http://wire.com is using it extensively for our iOS project.
The only question for us is how much time did it took in the past for you to maintain the project?
With kind regards, Mike on behalf of Wire's iOS team

Hi @mikeger nice to hear from you. Hard to put a figure on time spent maintaining in past, I guess there was a lot of upfront time getting the base featureset working. Since then I've been doing very little iOS work so haven't spent alot of time on it.
 At the other end of spectrum adding the most commonly requested features and fixing bugs would probably not be a huge commitment.
If you would like discuss in more detail the podspec file has my email address in it.
thanks!

@mikeger @cloudkite what's the scoop on handing off maintainer for Classy? I am interested in helping as a co-maintainer if you'd like. I've been hacking on Classy for a while now - I have some experimental features added in my fork (https://github.com/keithnorm/Classy) like the ability to call custom color functions so you can do things like:
  UIButton.cancel-button {
      title-color[state: normal]: $green
      title-color[state: highlighted]: darken($green, 0.20)
  }

Aside from features, I would be most interested in helping with bug fixes and managing issues, as well as helping to improve and promote the website and documentation. I strongly believe that Classy should be the standard for theming iOS apps and I don't want to see the project wither on the vine.

@keithnorm awesome :) have added you to the ClassyKit org

@cloudkite I too would be sad to see Classy disappear. When I joined my current team and was tasked with building an iOS SDK, I started pulling my hair out - mainly because I had no idea how one would build an SDK and allow 3rd party apps using it to control the look and feel of the final product (it's just not doable with iOS GUI builder). I was jealous of XML templates Android devs could do, then I discovered Classy. Now the Android devs are jealous, and I can keep the rest of my hair. I've successfully built an SDK that's much easier to style than Android and have gotten good feedback from client developers playing with the beta version. If Classy becomes unmaintained or worse yet, incompatible with future versions of XCode, I now risk building a dud for my company. For that reason, I'd love to help out with Classy where I can, but given my other project commitments (RapydScript, etc.) and work, the time I can contribute would be limited by that. However, I'm pretty comfortable with Swift, if that's where you decide to take the project.
p.s. @keithnorm I like the state idea you mention, can't wait to play with it.
p.p.s. I noticed that classy.as is now down. This was how I used to learn Classy documentation. Could you copy the documentation from it into the project or the README, because currently the README only gives a couple examples and suggests going to the website for the rest.
Thanks

@atsepkov awesome, good to hear you've found Classy to be valuable as well! The classy.as domain may have expired but you can still access the site through the github pages url at http://classykit.github.io/Classy/

Hey, I'm porting to IOS soon. I guess its a bit like Classy: https://github.com/eonist/Element Its in swift though. I hope its not inappropriate to mention my project here?

@eonist Looks pretty good. How soon will iOS port be available? I like Classy but it's currently my only Obj-C dependency and with project potentially deprecated, it's hard to continue using it. I would prefer to have all my libraries be in Swift for consistency.

Element was built with IOS in mind. I'm planing to set a side 2 weeks for the IOS port. Then it's the matter of start date which is not set yet. Still working on a few finishing touches of Element for OSX.


feat: uniform kcl cli

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[x] Y

re #https://github.com/kcl-lang/kpm/issues/289

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[x] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[x] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[ ] Other

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 38.209%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
128

Relevant Lines:
335

💛  - Coveralls


Typos in the README

In the example for My.Json.Module:
@behaviour Joken.Json
should be
@behaviour Joken.Codec
and in the config example, there should be a comma after :joken
so it should be
config :joken,
secret_key: "test"

Thanks, I think I got them all.


Semantic versioning system and changelogs for devs

Sometimes there's a substantial production update on the queue, and I have to save notes on what to do during that update if there's any reason why I can't get it done immediately. This creates additional mental baggage, and whenever we have multiple devs again it's sure to be a communication issue.
I propose a system like this:

Use a semantic versioning system of the form A.B (or A.B.C), where:

A is the major version. Updating this indicates an overall big change to CoralNet, usually including major user-visible changes such that it makes sense to mention the version bump in a blog post. For example, we announced CoralNet 1.0 (or 1.0.0) when we introduced the Deploy API and EfficientNet extractor, alongside major internal changes done in that round (AWS Batch / Python 3). Possible reasons for a version 2.0(.0) would include an expanded API, multiple labels per point, some form of orthomosaic support, semantic segmentation, etc.

B is the minor version. Updating this indicates that a CoralNet environment (production/staging or development) needs to do something other than git pull and manage.py collectstatic to update to that point of the repo. For example, updating a package version, running DB migrations, or specifying new settings. In general, this could be advanced once per pull request which involves such steps for updating, but there may be exceptions. For example, one minor version for back-to-back related PRs, or multiple minor versions for a single PR with a tricky installation (like PR #387).

C is the patch version. This indicates any update that doesn't meet the criteria for A or B, but is still worth marking as a version for one reason or another. For example, a security update which should be pushed to production quickly. Patch versions can be used as often or as scarcely as we see fit; we may frequently have smaller PRs which don't have any version bump at all.

Maintain Git tags to mark versions. A new tag should be added on the appropriate commit whenever a PR intends to bump the version. Note that tags can be pushed and fetched along with everything else in the repo.

Maintain a changelog file (perhaps in Markdown format) listing version notes, latest version at the top. At minimum, this should include update-instructions for major and minor versions (e.g. "New migrations in vision_backend"). Brief description of the changes in functionality are also good to have.

With this, the mental model for updating an environment is: identify the version you're on and the version you want to update to, and follow the instructions in the changelog to update through those versions. No need to dig through the individual PRs/commit details.
Note that the versioning system for pluggable apps tends to be different; in particular, the criteria for B is often considered worthy of a major version. However, I think the system I've laid out above is better optimized for CoralNet.
Tasks:

[x] Document this semantic versioning system in our docs.

[x] Add a changelog file.

[x] Tags and changelog entries to add right away:

1.0 corresponding to (roughly) when we announced CoralNet 1.0.

1.1 before PR #459, indicating where production is currently sitting.

1.2 after PR #459.

1.3 after PR #462.

[x] Our "1.1" GitHub milestone could be split up into 1.1 and 1.x (since 1.1 encompassed a decent amount of activity).

Done: merged PR #465, added tags, and modified milestones.


permission denied

Checklist for submitting an issue to KickThemOut:

[x ] I have carefully read the README file and haven't managed to resolve my issue.
[x ] I have searched the issues of this repo and believe that this is not a duplicate.
[x ] I am running the latest version of KickThemOut.

OS name & version: android termux
Python version: python3
Scapy version:
Nmap version: 7.7
Link of Gist:

$ tsudo python3 kickthemout.py
ERROR: Requirements have not been satisfied properly. Please look at the README file for configuration instructions.
If you still cannot resolve this error, please submit an issue here:
https://github.com/k4m4/kickthemout/issues
Details: [Errno 13] Permission denied: '/data/data/com.termux/files/usr/bin/sh'
$
can someone help me with this issue. my. Im usin rooted samsung galaxy note 5 with permissive selinux.  <br/ >

Description:  permission denied

I have the same problem


getNamesOfClassesImplementing fails if the interface is in different package.

Using 1.9.7
Assuming:

package a;
interface A {}

package b;
public class C extends A {}

And calling it with:
 new FastClasspathScanner("b").scan().getNamesOfClassesImplementing("a.A")

I would expect "b.C" to still be returned but it is not. A workaround is new FastClasspathScanner("b", "a"), but that feels clunky.
Basically I feel like the interface itself should not have to be in the list of packages scanned. I haven't looked at implementation details, so there may be a good reason for it.

I tried to reproduce this:
https://github.com/lukehutch/fast-classpath-scanner/compare/master...triggerNZ:outside-interface-example?expand=1
It definitely fails in my example, but I want to introduce a pure java test case, rather than submitting my scala example.
Unfortunately, I could not it to fail. Will explore further...

Hmm. As stated in README.md (in the Constructor section), this is supposed to succeed -- if a class inside a whitelisted package refers to another class that is outside a whitelisted package (e.g. as a superclass, or for an implemented interface), then the referenced class is returned in the list of all classes (or superclasses, or implemented interfaces), just as you requested. If it doesn't work this way, it may indicate a bug of some sort.
Unfortunately I know nothing of the details of how Scala might compile its classes differently than Java, and I wouldn't even know how to exactly reproduce your testcase, so I don't think I can help debug this effectively. However, try calling .verbose() before .scan(), and compare the output for minimalistic Java and Scala testcases -- this should hopefully give you enough info to figure out what's going on.
Please keep me posted. I definitely want to support Scala with FastClasspathScanner, but you may be the first person to have tried this.

@lukehutch cool, I will investigate further.

I'm pretty sure legal won't get on your case for posting a minimal testcase into a bugreport ;-)
You can probably debug this much faster than I could, since I have close to zero experience with Scala, but let me know if you need assistance.
Please paste the results here of running FastClasspathScanner with .verbose() then .scan() for what you think should be exactly equivalent testcases in Java and Scala -- that should help figure out what's going wrong.

Update: I have added scala compilation support for tests and have a breaking test. Verbose output seems what we would expect:
FastClasspathScanner: Found Class-Path entry in jar:file:/Users/tin/dev/fast-classpath-scanner/target/surefire/surefirebooter1624711121499741185.jar!/META-INF/MANIFEST.MF: file:/Users/tin/.m2/repository/org/apache/maven/surefire/surefire-booter/2.12.4/surefire-booter-2.12.4.jar file:/Users/tin/.m2/repository/org/apache/maven/surefire/surefire-api/2.12.4/surefire-api-2.12.4.jar file:/Users/tin/dev/fast-classpath-scanner/target/test-classes/ file:/Users/tin/dev/fast-classpath-scanner/target/classes/ file:/Users/tin/.m2/repository/junit/junit/4.12/junit-4.12.jar file:/Users/tin/.m2/repository/org/hamcrest/hamcrest-core/1.3/hamcrest-core-1.3.jar file:/Users/tin/.m2/repository/org/assertj/assertj-core/3.1.0/assertj-core-3.1.0.jar file:/Users/tin/.m2/repository/org/scala-lang/scala-library/2.11.4/scala-library-2.11.4.jar
FastClasspathScanner: Found classpath element: /Users/tin/.m2/repository/org/apache/maven/surefire/surefire-booter/2.12.4/surefire-booter-2.12.4.jar
FastClasspathScanner: Found classpath element: /Users/tin/.m2/repository/org/apache/maven/surefire/surefire-api/2.12.4/surefire-api-2.12.4.jar
FastClasspathScanner: Found classpath element: /Users/tin/dev/fast-classpath-scanner/target/test-classes
FastClasspathScanner: Found classpath element: /Users/tin/dev/fast-classpath-scanner/target/classes
FastClasspathScanner: Found classpath element: /Users/tin/.m2/repository/junit/junit/4.12/junit-4.12.jar
FastClasspathScanner: Found classpath element: /Users/tin/.m2/repository/org/hamcrest/hamcrest-core/1.3/hamcrest-core-1.3.jar
FastClasspathScanner: Found classpath element: /Users/tin/.m2/repository/org/assertj/assertj-core/3.1.0/assertj-core-3.1.0.jar
FastClasspathScanner: Found classpath element: /Users/tin/.m2/repository/org/scala-lang/scala-library/2.11.4/scala-library-2.11.4.jar
FastClasspathScanner: Found classpath element: /Users/tin/dev/fast-classpath-scanner/target/surefire/surefirebooter1624711121499741185.jar
FastClasspathScanner: *** Starting scan ***
FastClasspathScanner: Classpath elements: [/Users/tin/.m2/repository/org/apache/maven/surefire/surefire-booter/2.12.4/surefire-booter-2.12.4.jar, /Users/tin/.m2/repository/org/apache/maven/surefire/surefire-api/2.12.4/surefire-api-2.12.4.jar, /Users/tin/dev/fast-classpath-scanner/target/test-classes, /Users/tin/dev/fast-classpath-scanner/target/classes, /Users/tin/.m2/repository/junit/junit/4.12/junit-4.12.jar, /Users/tin/.m2/repository/org/hamcrest/hamcrest-core/1.3/hamcrest-core-1.3.jar, /Users/tin/.m2/repository/org/assertj/assertj-core/3.1.0/assertj-core-3.1.0.jar, /Users/tin/.m2/repository/org/scala-lang/scala-library/2.11.4/scala-library-2.11.4.jar, /Users/tin/dev/fast-classpath-scanner/target/surefire/surefirebooter1624711121499741185.jar]
FastClasspathScanner: Whitelisted paths:  [io/github/lukehutch/fastclasspathscanner/]
FastClasspathScanner: Blacklisted paths:  []
FastClasspathScanner: => Scanning classpath element: /Users/tin/.m2/repository/org/apache/maven/surefire/surefire-booter/2.12.4/surefire-booter-2.12.4.jar
FastClasspathScanner: Scanning jarfile: /Users/tin/.m2/repository/org/apache/maven/surefire/surefire-booter/2.12.4/surefire-booter-2.12.4.jar
FastClasspathScanner: Scanned jarfile /Users/tin/.m2/repository/org/apache/maven/surefire/surefire-booter/2.12.4/surefire-booter-2.12.4.jar in 0 msec
FastClasspathScanner: => Scanning classpath element: /Users/tin/.m2/repository/org/apache/maven/surefire/surefire-api/2.12.4/surefire-api-2.12.4.jar
FastClasspathScanner: Scanning jarfile: /Users/tin/.m2/repository/org/apache/maven/surefire/surefire-api/2.12.4/surefire-api-2.12.4.jar
FastClasspathScanner: Scanned jarfile /Users/tin/.m2/repository/org/apache/maven/surefire/surefire-api/2.12.4/surefire-api-2.12.4.jar in 0 msec
FastClasspathScanner: => Scanning classpath element: /Users/tin/dev/fast-classpath-scanner/target/test-classes
FastClasspathScanner: Scanning path: /
FastClasspathScanner: Scanning path: io/
FastClasspathScanner: Scanning path: io/github/
FastClasspathScanner: Scanning path: io/github/lukehutch/
FastClasspathScanner: Scanning path: io/github/lukehutch/fastclasspathscanner/
FastClasspathScanner: Reached whitelisted path: io/github/lukehutch/fastclasspathscanner/
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/F$.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/F.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/FastClasspathScannerTest$1.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/FastClasspathScannerTest$2.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/FastClasspathScannerTest$3.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/FastClasspathScannerTest$4.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/FastClasspathScannerTest.class in 1 msec
FastClasspathScanner: Scanning path: io/github/lukehutch/fastclasspathscanner/metaannotation/
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/metaannotation/A.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/metaannotation/B.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/metaannotation/C.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/metaannotation/D.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/metaannotation/E.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/metaannotation/F.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/metaannotation/G.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/metaannotation/H.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/metaannotation/I.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/metaannotation/J.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/metaannotation/K.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/metaannotation/L.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/metaannotation/M.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/metaannotation/MetaAnnotationTest.class in 0 msec
FastClasspathScanner: Scanning path: io/github/lukehutch/fastclasspathscanner/outside/
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/outside/Outside.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/ScalaBugTest.class in 1 msec
FastClasspathScanner: Scanning path: io/github/lukehutch/fastclasspathscanner/whitelisted/
FastClasspathScanner: Scanning path: io/github/lukehutch/fastclasspathscanner/whitelisted/blacklisted/
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/whitelisted/blacklisted/Blacklisted.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/whitelisted/Cls.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/whitelisted/ClsSub.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/whitelisted/ClsSubSub.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/whitelisted/Iface.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/whitelisted/IfaceSub.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/whitelisted/IfaceSubSub.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/whitelisted/Impl1.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/whitelisted/Impl1Sub.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/whitelisted/Impl1SubSub.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/whitelisted/Impl2.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/whitelisted/Impl2Sub.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/whitelisted/Impl2SubSub.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/whitelisted/ImplementsOutside.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/whitelisted/StaticField.class in 0 msec
FastClasspathScanner: Scanning path: outside/
FastClasspathScanner: Scanning path: someothersillypackage/
FastClasspathScanner: => Scanning classpath element: /Users/tin/dev/fast-classpath-scanner/target/classes
FastClasspathScanner: Scanning path: /
FastClasspathScanner: Scanning path: io/
FastClasspathScanner: Scanning path: io/github/
FastClasspathScanner: Scanning path: io/github/lukehutch/
FastClasspathScanner: Scanning path: io/github/lukehutch/fastclasspathscanner/
FastClasspathScanner: Reached whitelisted path: io/github/lukehutch/fastclasspathscanner/
FastClasspathScanner: Scanning path: io/github/lukehutch/fastclasspathscanner/classgraph/
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/classgraph/ClassfileBinaryParser.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/classgraph/ClassGraphBuilder$1.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/classgraph/ClassGraphBuilder$10.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/classgraph/ClassGraphBuilder$11.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/classgraph/ClassGraphBuilder$2.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/classgraph/ClassGraphBuilder$3.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/classgraph/ClassGraphBuilder$4.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/classgraph/ClassGraphBuilder$5.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/classgraph/ClassGraphBuilder$6.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/classgraph/ClassGraphBuilder$7.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/classgraph/ClassGraphBuilder$8.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/classgraph/ClassGraphBuilder$9.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/classgraph/ClassGraphBuilder.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/classgraph/ClassInfo.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/classgraph/DAGNode.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/FastClasspathScanner$1.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/FastClasspathScanner$10.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/FastClasspathScanner$2.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/FastClasspathScanner$3.class in 1 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/FastClasspathScanner$4.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/FastClasspathScanner$5.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/FastClasspathScanner$6.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/FastClasspathScanner$7.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/FastClasspathScanner$8.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/FastClasspathScanner$9.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/FastClasspathScanner$ClassMatcher.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/FastClasspathScanner.class in 1 msec
FastClasspathScanner: Scanning path: io/github/lukehutch/fastclasspathscanner/matchprocessor/
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/matchprocessor/ClassAnnotationMatchProcessor.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/matchprocessor/FileMatchContentsProcessor.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/matchprocessor/FileMatchProcessor.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/matchprocessor/InterfaceMatchProcessor.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/matchprocessor/StaticFinalFieldMatchProcessor.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/matchprocessor/SubclassMatchProcessor.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/matchprocessor/SubinterfaceMatchProcessor.class in 0 msec
FastClasspathScanner: Scanning path: io/github/lukehutch/fastclasspathscanner/scanner/
FastClasspathScanner: Scanning path: io/github/lukehutch/fastclasspathscanner/scanner/classloaderhandler/
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/scanner/classloaderhandler/ClassLoaderHandler.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/scanner/classloaderhandler/JBossClassLoaderHandler.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/scanner/classloaderhandler/URLClassLoaderHandler.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/scanner/classloaderhandler/WeblogicClassLoaderHandler.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/scanner/ClasspathFinder.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/scanner/RecursiveScanner$FilePathMatcher.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/scanner/RecursiveScanner$FilePathTester.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/scanner/RecursiveScanner.class in 0 msec
FastClasspathScanner: Scanning path: io/github/lukehutch/fastclasspathscanner/utils/
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/utils/HashClassfileContents$1.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/utils/HashClassfileContents.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/utils/LazyMap$1.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/utils/LazyMap$2.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/utils/LazyMap.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/utils/Log.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/utils/MultiSet.class in 0 msec
FastClasspathScanner: Scanned file io/github/lukehutch/fastclasspathscanner/utils/Utils.class in 0 msec
FastClasspathScanner: Scanning path: META-INF/
FastClasspathScanner: => Scanning classpath element: /Users/tin/.m2/repository/junit/junit/4.12/junit-4.12.jar
FastClasspathScanner: Scanning jarfile: /Users/tin/.m2/repository/junit/junit/4.12/junit-4.12.jar
FastClasspathScanner: Scanned jarfile /Users/tin/.m2/repository/junit/junit/4.12/junit-4.12.jar in 0 msec
FastClasspathScanner: => Scanning classpath element: /Users/tin/.m2/repository/org/hamcrest/hamcrest-core/1.3/hamcrest-core-1.3.jar
FastClasspathScanner: Scanning jarfile: /Users/tin/.m2/repository/org/hamcrest/hamcrest-core/1.3/hamcrest-core-1.3.jar
FastClasspathScanner: Scanned jarfile /Users/tin/.m2/repository/org/hamcrest/hamcrest-core/1.3/hamcrest-core-1.3.jar in 0 msec
FastClasspathScanner: => Scanning classpath element: /Users/tin/.m2/repository/org/assertj/assertj-core/3.1.0/assertj-core-3.1.0.jar
FastClasspathScanner: Scanning jarfile: /Users/tin/.m2/repository/org/assertj/assertj-core/3.1.0/assertj-core-3.1.0.jar
FastClasspathScanner: Scanned jarfile /Users/tin/.m2/repository/org/assertj/assertj-core/3.1.0/assertj-core-3.1.0.jar in 0 msec
FastClasspathScanner: => Scanning classpath element: /Users/tin/.m2/repository/org/scala-lang/scala-library/2.11.4/scala-library-2.11.4.jar
FastClasspathScanner: Scanning jarfile: /Users/tin/.m2/repository/org/scala-lang/scala-library/2.11.4/scala-library-2.11.4.jar
FastClasspathScanner: Scanned jarfile /Users/tin/.m2/repository/org/scala-lang/scala-library/2.11.4/scala-library-2.11.4.jar in 3 msec
FastClasspathScanner: => Scanning classpath element: /Users/tin/dev/fast-classpath-scanner/target/surefire/surefirebooter1624711121499741185.jar
FastClasspathScanner: Scanning jarfile: /Users/tin/dev/fast-classpath-scanner/target/surefire/surefirebooter1624711121499741185.jar
FastClasspathScanner: Scanned jarfile /Users/tin/dev/fast-classpath-scanner/target/surefire/surefirebooter1624711121499741185.jar in 0 msec
FastClasspathScanner: *** Time taken by .scan(): 21 ms ***

So it appears that the issue is on ClassGraphBuilder.java:266. At this point interfaceNameToInterfaceNode, doesn't contain the outside trait. I don't really understand why/how it works for the java case

Yes, I'm looking at this right now. I discovered that Scala does some funky stuff when it compiles code. The F$ class is a "companion class", and contains the interfaces (but not annotations). F contains annotations but not interfaces. (There's also a class generated in other cases, not this one, "MyTrait$class" based on trait "MyTrait", to hold the static methods for the trait.
I'm currently writing code to merge F, F$ and F$class into a single entry in the class graph.

Thanks for reporting this, it should be fixed now, but can you please test it with your setup?

(Just released v1.9.8 to Maven with these fixes, in case it's easier for you to test it that way.)

@lukehutch thank you so much for fixing that so promptly. My dependency on 1.9.8 isn't resolving yet though.  Is there a resolver i have to set up?

You may need to manually rebuild your Maven Central index -- the release is definitely up: https://github.com/lukehutch/fast-classpath-scanner/releases
Failing that, it would be great if you could just do a "git clone" and copy the FastClasspathScanner project into your project's source directory to test it.

Will reopen this until it's tested and confirmed working!

Hi @triggerNZ, did you get the 0.9.8 dependency resolved? Would love to know if I can close this bug -- thanks!

Hi @lukehutch, sorry it has taken me this long to reply - it has been a busy week. There is an error in the class merging code. If you run mvn test in my fork you can see the errors. I haven't had time to investigate further

@triggerNZ thanks for taking another look. You're right, your test generated a lot of warnings. I fixed these in the latest checkin, and your test now passes, so I'll close this bug and release 0.9.9. Thank you again for your help getting Scala up and working (so far, at least :-) ).


Extend and simplify installation instructions

Comments from @ledigchr by email:
The installation page is currently a bit less clear. Perhaps it would be good to provide an example of how to build mirtk without understanding cmake?
E.g. cmake ..; make -j 8; worked for me on Linux.
A user might not know how to run the cmake gui? On my Mac there is no command line command ‘cmake’, here I need to download cmake and run it from the applications.

Thanks @ledigchr for the comments. I also think the installation instructions could be less cluttered. For example, the dependencies table could be on a separate page. And there could be sections for each OS and common build tool, i.e., Linux + GNU Make, Linux + Ninja, OS X + GNU Make, OS X + Ninja, OS X + Xcode, (and Windows + Visual Studio) with a brief summary of the steps usually needed. Only when this doesn’t work out, a more generic, lengthy description can be looked up.
What is also missing, to build all modules without GUI, the cmake command would be:
cmake -D BUILD_ALL_MODULES=ON $MIRTK_SOURCE_DIR

Also, for OS X change default installation directory to /Users/<user>/Applications/MIRTK to avoid difficulties for unexperienced users. This directory can further be viewed easily in the Finder.


fix(utils): fix proxyWithHistory behavibor with nested objects

Related Issues
Test to reproduce issue #516.
And, a fix.

Let's wait for #528, which might provide a better option.

Let's wait for #528, which might provide a better option.

On second thought, deepClone can be more efficient, because it only happens for undo/redo. (The other method I had in mind is to do copy on saveHistory.)


pallet_nfts Missing force_ methods, publicdo_

Is there an existing issue?

[X] I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

[X] This is not a support question.

Motivation
There are a few methods that are currently not implemented in pallet_nfts. These are force_transfer, force_lock_item_transfer and force_unlock_item_transfer.
The functionality these methods would provide are very useful when designing game mechanics around pallet_nfts.
As a workaround, do_transfer is public and can be used as a DIY "force_transfer", but it is unclear whether the do_* methods are intended to be part of the public api as for in this case, the ItemDetailsfields are private and unusable. The do_lock/unlock_item_transfer methods are private so no DIY approach is possible, which also leads me to question whether  it's sensible to use do_*.
Request
IMO there's value in keeping do_* methods public as they offer a great amount of flexibility. if this seems sensible, then the remaining do methods (I've only checked do_lock/unlock_item_transfer) should be public and the types exposed in the with_details callback should have public fields.
Otherwise, I think providing the extra force_* methods as described above would be really handy.
Solution
No response
Are you willing to help with this request?
Yes!

do_* functions are meant to be private. But we can probably add more public force functions, or @jsidorenko?

I'm not against adding more force functions.
Some do_ functions are public since we use them in traits and I don't think we can make them private. So, to make the pallet more flexible, we could make all the do_ methods public, and/or wrap them with the traits.
Btw, as for item transfer, you can simply call the transfer() on the Transfer trait that pallet implements, and there is no need to touch the do_transfer

P. S. Transfer::transfer() doesn't support the callback that could be useful in some cases. So, having the do_ methods public could allow the implementation of more sophisticated use cases where the public traits methods won't be enough.

If some of the do_ methods have to be public, maybe it makes more sense to treat them as a feature and make them and their callback struct fields public.
I suspect this will be a much quicker path to providing the flexibility described above compare to creating new force methods. It also clears up the question of "is it correct to build around do_ methods".
The force methods could then possibly be introduced later if/when they're required for ease-of-use (as technically everything can be achieved with do_?)

@kianenigma Would appreciate your input here


Only initialize JANSI when native services are enabled

JANSI is being initialized, even though native services have been disabled by the system property. This has been introduced by #17440.
As an additional problem, the nativeBaseDir has not been set in this case, which caused jansi to be initialized in the current working directory.
This PR fixes both problems:

Do not initialize JANSI when native integrations are disabled.
Always set the native base dir.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test QFL

OK, I've already triggered QuickFeedbackLinux build for you.

@bot-gradle test and merge

OK, I've already triggered a build for you.


Fix paths generation for container sas

Fixes
Issue #208
Description
This is to fix malformed paths generated by Azure Storage instance created with SAS which includes container name already

[x] I've made sure that this PR is raised against the develop branch.
[x] I have included unit/integration tests validating this fix.
[x] I have updated markdown documentation where required.

I've done additional work to fix build issues with depricated build properties. Let me know if I should remove it in favour of #199 PR which solution looks more clean
@aloneguid I hope that package is still under maintenance and you accept contributions - I am really looking forward for that fix to go in

@aloneguid This seems to still cause an issue as of today within the library. It looks like the emulator isn't using the devstoreaccount1 account when generating the key.


Add Zero Trust Option for Storage Accounts / CMK

Overview/Summary
This change incorporates updates to the baseline deployment to add an option in the Storage section of the UI for Zero Trust which then allows for an additional Key Vault to be deployed.  Keys created for each storage account and Customer Managed Keys configured for each storage account.
This PR fixes/adds/changes/removes

Adjusted UI definition for custom names - prefix regex set for 1-6 chars but validation mesg said 1-90.
Adds check box for Zero Trust in Custom UI Storage section
Code includes logic to handle and deploy additional key vault, keys and associates with existing identity and storage accounts.

Breaking Changes

N/A

Testing Evidence
Tested deployment in lab environment with multiple scenarios and successfully deployed each time to include the changes added with the option flag set.
As part of this Pull Request I have

[X] Read the Contribution Guide and ensured this PR is compliant with the guide
[X] Ensured the resource API versions in .bicep file/s I am adding/editing are using the latest API version possible
[X] Checked for duplicate Pull Requests
[X] Associated it with relevant GitHub Issues
[X] (AVD LZA Team Only) Associated it with relevant ADO Items
[X] Ensured my code/branch is up-to-date with the latest changes in the main branch
[X] Performed testing and provided evidence.
[X] Updated relevant and associated documentation (e.g. Contribution Guide, Module READMEs, Docs etc.)

@JCoreMS Hey Jonathan, reviewing PR:
Can we change the naming  of:
line 427: Default: kv-sec to Default: kv-st
line 428: param ztKvStrPrefixCustomName string = 'kv-str' to param ztKvStPrefixCustomName string = 'kv-st'
lines 617 to 623: varStrgKvName to varStgKvName (and additional naming updates)
If this code is also for ZT, should we use the exiting ZT identy or if creating new one whould we rename the previous ZT arctifacts to VMS instead of ZT?
rename workload/bicep/modules/zeroTrust/.bicep/StorageCmkConfig.bicep to workload/bicep/modules/zeroTrust/.bicep/storageCmkConfig.bicep. Also this new module should follow the same template as the others (mostly comments and headers), pleae clean up commented sections if they are not needed.
Above will require the param/var name to be updated across all templates

@danycontre updates made per request.

New PR submitted with the same feature.


v3-beta7: Better error messages when Cordova is not installed

What version of the CLI are you using? Output of ionic --version
3.0.0-beta7
Short description of the problem:
Calling ionic cordova platform outputs a non-descript error when Cordova is not installed:
> ionic cordova platform
[ERROR] Command not found: cordova

What behavior are you expecting?
Calling a cordova sub-command on a project when Cordova is not installed should output this error message but also point the user in the right direction to install Cordova on his machine.

Hi! In the next beta release you should see this:

Along with a super helpful, huge error message during preinstall of the plugin:

Thank you! 🎉


Fix slowdown on init with device_map="auto"

What does this PR do?
https://github.com/huggingface/accelerate/pull/2857 introduced using gc.collect() as part of the clear_device_cache. This is very slow to do and increases the time to load models exponentially when using device_map="auto" (e.g. llama-3-8B went from 6.663s to 37.535s).
This PR adds a garbage_collection flag which is False by default.
Fixes https://github.com/huggingface/accelerate/issues/2911
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[x] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
[ ] Did you write any new necessary tests?

Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@SunMarc

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Update transports.py

Under p3k, this code throws NameError (because of the unicode() function)
This fix should be valid under both python2 and python3

Thanks!


add SLO url to metadata generation

1st step for SLO

@SilviaAmAm You were right,  # pragma: no cover worked like a charm for the whole class


Bengali OCR

When we got a better OCR for Bengali language?

See #212.

Langdata/tessdata  issues should be reportoed at relevant part of project (https://github.com/tesseract-ocr/tessdata/issues or https://github.com/tesseract-ocr/langdata/issues)
Issue tracker should be use for reporting issues and not for asking questions.


Implement if let expressions and associated fixes

Why?
As we don't have any form of destructuring, getting values out of enums is impossible. This hinders our progress in developing the standard library and basic demos -- primarily SwaySwap.
What?
This PR implements if let for enums, although not to complete parity with Rust's pattern matching. Some general fixes around generic types/enums/etc., are included in this PR as well.
List O' Changes

Previously, return statements inside of if expressions were not being type checked correctly. This PR fixes that.
Enum monomorphization was not implemented at all, this PR implements that.
Help text has been reintroduced to type errors.
Implements if let expressions, which compare an enum's tag and conditionally pull out its contents into a variable.

Allow type annotations for enum instantiations, i.e. let x = Result::Ok::<u64, bool>(5u64)

Remaining work

Generic impl blocks and trait interactions are still not there. This PR was big enough as is, so that'll be coming later.
Arbitrary pattern destructuring is not implemented. This version of if let only allows for destructuring the top-level enum. This is okay: if let Result::Ok(val) = foo { .. }, this is not okay: if let Result::Ok(Option::Some(Enum::Variant(x, y, Struct { field, .. } ) ) ) = foo { .. }

closes #817
closes #624

Yikes, are we going to get Forc.lock conflicts like crazy from now on, or is this temporary?

Yikes, are we going to get Forc.lock conflicts like crazy from now on, or is this temporary?

All of the Forc.tomls and Forc.lock files for the E2E tests were updated in #876 and shouldn't need to be updated in a PR like this (except for the new ones of course!). Conflicts in lock files should be no more common than conflicts related to changing version numbers in Forc.toml.
I think this is a unique case where the conflicts are potentially related to generating and committing lock files between #825 landing and #876 landing. I probably should have done #876 as a part of #825 to avoid this happening, but that PR was already massive enough! I would probably address this via a rebase onto master, but I know many prefer to avoid rebase and everyone has their own git wrangling strats :)

Do not merged until 0.6.1 is released https://github.com/FuelLabs/sway/pull/921


Change tab_bar backgroundcolor

Hi im new on rubymotion, this is my 3rd day i started directly with promotion because you did a great job!
Sorry for my bad english im from France...
So my problem is described in the title i would like to customize my tab bar but i have no idea how to find it... so i have i tab_bar like this one:
open_tab_bar(FirstScreen.new(nav_bar: true), SecondScreen, ...)
And in my declared screens i have:
def on init    set_tab_bar_item title: "first", item: "my-icon" end
How can i access the options availible in the UI Documentation?
Thanks a lot !

Hey @bmoby! Welcome to ProMotion, glad it's been useful.
You'll need to change the UIAppearance of all tab bars. Check #341 for an example of how to do that.

I'm going to close this issue since it's been open for a long time. Let us know if you need any more help!


Bubbletree crashes bcbio

Bit strange, I’ve run bubbletree via bcbio (updated today) on 8+ samples from a cohort without error.
Using the same installation, one of the samples kicks up an R error:
5 0.08823529 0.06496308      75 1.1485669384
6 0.10847154 0.06133024      68 1.2260297256
Error in if (uc.cov > 0.5 & uc.hds < 1/6 & cfg$high.ploidy) { :
  missing value where TRUE/FALSE needed
Calls: btpredict -> btpredict -> getPloidyAdj -> getPloidyAdj
In addition: Warning message:
In limma::weighted.median(lrr, seg.size, na.rm = TRUE) :
  All weights are zero
Execution halted
' returned non-zero exit status 1

I put the contents of the respective /heterogeneity/PID/bubble directory here:
https://www.dropbox.com/sh/5r40ns1fodwafzn/AAA1iq7GUL6PZMPRPGoMJkiXa?dl=0
Not urgent, but might need to be addressed for robustness

Thanks, this looks stale and hasn't been any action-- I think this is probably a non-problem now.


Create VISION.md

Use as reference this:
https://github.com/projen/projen/blob/main/VISION.md

it's done.


coreos-cloudinit: v1.6.0 build fails for arm64

v1.5.1 built OK, v1.6.0 fails.  I haven't had time yet to look at it.
github.com/coreos/coreos-cloudinit/Godeps/_workspace/src/github.com/sigma/vmw-guestinfo/bridge
In file included from ../include/message.h:47:0,
             from ../gopath/src/github.com/coreos/coreos-cloudinit/Godeps/_workspace/src/github.com/sigma/vmw-guestinfo/bridge/bridge.go:6:
../include/vm_basic_types.h:437:9: error: unknown type name 'uintptr_t'
 typedef uintptr_t VA;

That sounds like https://github.com/coreos/coreos-cloudinit/commit/13dc11abf32520f79c2cab949d7e68df407c1c37.


Add support form mutation

Follows up https://github.com/opencollective/opencollective-frontend/pull/7235

@flickz We would prefer to handle this directly from the Frontend side, similar to https://github.com/opencollective/foundation-website/blob/master/api/contact.js

@flickz let's move to frontend handling as discussed in https://github.com/opencollective/opencollective-api/pull/6945#issuecomment-989599612