Do the tests ever fail?

Description
For some reasons, I can't get the test to fail. I added the following line:
diff --git a/definitions/npm/knex_v0.12.x/test_knex-v0.12.js b/definitions/npm/knex_v0.12.x/test_knex-v0.12.js
index efe9b50..0a203d1 100644
--- a/definitions/npm/knex_v0.12.x/test_knex-v0.12.js
+++ b/definitions/npm/knex_v0.12.x/test_knex-v0.12.js
@@ -42,6 +42,8 @@ knex('bar').del();
 // $ExpectError
 knex.from();

+knex.iCertainlyDontExistButIWontFail('blaaaa');
+
 knex.destroy();

 /**

As the function iCertainlyDontExistButIWontFail doesn't exist in the Knex definition, I was expecting the tests to fail where I ran the script run_def_tests.sh but it reported that all the tests passed.
» ./run_def_tests.sh
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

up to date in 0.788s

><EMAIL_ADDRESS>test /path/to/dir/flowtype/flow-typed/definitions
> eslint npm/**/test*

/path/to/dir/flowtype/flow-typed/definitions/npm/backbone_v1.x.x/test_backbone-v1.x.x.js
  15:14  warning  Unexpected use of weak type "any"       flowtype/no-weak-types
  17:14  warning  Unexpected use of weak type "any"       flowtype/no-weak-types
  19:22  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types
  49:29  warning  Unexpected use of weak type "any"       flowtype/no-weak-types
  52:23  warning  Unexpected use of weak type "any"       flowtype/no-weak-types
  54:17  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types
  55:16  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/blacklist_v1.x.x/test_blacklist_v1.x.x.js
  4:33  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
  5:37  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/bluebird_v3.x.x/test_bluebird_v3.x.x.js
   99:37  warning  Unexpected use of weak type "Object"    flowtype/no-weak-types
  121:47  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/bunyan_v1.x.x/test_bunyan_v1.x.x.js
  17:20  warning  Unexpected use of weak type "any"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/camelcase-keys_v3.x.x/test_camelcase-keys_v3.x.x.js
  3:15  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/commander_v2.x.x/test_commander_v2.x.x.js
  37:30  warning  Unexpected use of weak type "any"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/express_v4.x.x/test_express_v4.x.x.js
  71:23  warning  Unexpected use of weak type "any"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/fuzzaldrin_v2.x.x/test_fuzzaldrin_v2.js
  6:10  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/inquirer_v2.x.x/test_rx_observable_array_v2.x.x.js
  41:17  warning  Unexpected use of weak type "any"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/inquirer_v2.x.x/test_rx_observable_create_v2.x.x.js
  9:9  warning  Unexpected use of weak type "any"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/isomorphic-fetch_v2.x.x/test_isomorphic-fetch_v2.js
  7:25  warning  Unexpected use of weak type "any"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/koa-bunyan-logger_v2.x.x/test_koa_bunyan_logger_v2.x.x.js
  19:20  warning  Unexpected use of weak type "any"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/map-obj_v1.x.x/test_map-obj_v1.x.x.js
  3:18  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
  3:79  warning  Unexpected use of weak type "any"     flowtype/no-weak-types
  3:92  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/mocha_v2.4.x/test_mocha_v2.4.x_hooks.js
   8:16  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types
  19:20  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types
  31:15  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types
  42:19  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/mocha_v2.4.x/test_mocha_v2.4.x_it.js
   8:20  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types
  26:25  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types
  46:25  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/mocha_v3.1.x/test_mocha_v3.1.x_hooks.js
   8:16  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types
  19:20  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types
  31:15  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types
  42:19  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/mocha_v3.1.x/test_mocha_v3.1.x_it.js
   9:20  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types
  25:25  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types
  43:25  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/morgan_v1.x.x/test_morgan.js
  29:58  warning  Unexpected use of weak type "any"  flowtype/no-weak-types
  29:68  warning  Unexpected use of weak type "any"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/node-fetch_v1.x.x/test_node-fetch_v1.js
  7:26  warning  Unexpected use of weak type "any"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/normalizr_v2.x.x/test_normalizr-v2.js
  4:40  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
  5:42  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
  8:25  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/object-assign_v4.x.x/test_object-assign_v4.x.x.js
  5:16  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
  6:16  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/papaparse_v4.x.x/test_papaparse_v4.x.x.js
  28:17  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
  31:25  warning  Unexpected use of weak type "any"     flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/primus_v5.x.x/test_primus-v5.js
  9:63  warning  Unexpected use of weak type "any"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/primus_v6.x.x/test_primus-v6.js
  9:63  warning  Unexpected use of weak type "any"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/prismic.io_v3.x.x/test_prismic.io_v3.x.x.js
   44:37  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
   49:44  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
   53:44  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
   55:72  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
   56:59  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
   71:27  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
   74:43  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
  103:29  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
  140:35  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
  148:43  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
  157:37  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
  164:28  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
  165:34  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
  166:45  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
  302:29  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/react-dnd_v2.x.x/test_react-dnd-v2.js
  72:26  warning  Unexpected use of weak type "any"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/react-select_v1.x.x/test_react-select_v1.x.x.js
   7:31  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
  10:31  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
  11:30  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
  12:33  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
  13:32  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
  19:32  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
  20:31  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
  63:21  warning  Unexpected use of weak type "any"     flowtype/no-weak-types
  67:26  warning  Unexpected use of weak type "any"     flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/redux-devtools-extension_v2.x.x/test_redux-devtools-extension_v2.x.x.js
  69:21  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types
  70:26  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/redux-form_v5.x.x/test_redux-form_v5.js
  19:25  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types
  20:20  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types
  21:21  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types
  33:32  warning  Unexpected use of weak type "any"       flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/rxjs_v5.0.x/test_rxjs.js
  145:56  warning  Unexpected use of weak type "any"  flowtype/no-weak-types
  146:52  warning  Unexpected use of weak type "any"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/sinon_v2.x.x/test_sinon_v2.x.x.js
    4:19  warning  Unexpected use of weak type "Function"  flowtype/no-weak-types
    6:20  warning  Unexpected use of weak type "any"       flowtype/no-weak-types
   57:22  warning  Unexpected use of weak type "any"       flowtype/no-weak-types
   58:18  warning  Unexpected use of weak type "any"       flowtype/no-weak-types
  166:16  warning  Unexpected use of weak type "any"       flowtype/no-weak-types
  175:16  warning  Unexpected use of weak type "any"       flowtype/no-weak-types
  185:16  warning  Unexpected use of weak type "any"       flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/twit_v2.x.x/test_twit_v2.x.x.js
  16:30  warning  Unexpected use of weak type "any"  flowtype/no-weak-types
  17:29  warning  Unexpected use of weak type "any"  flowtype/no-weak-types

/path/to/dir/flowtype/flow-typed/definitions/npm/underscore_v1.x.x/test_underscore-v1.js
  171:20  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types
  172:13  warning  Unexpected use of weak type "Object"  flowtype/no-weak-types

✖ 93 problems (0 errors, 93 warnings)

npm WARN prepublish-on-install As of npm@5, `prepublish` scripts are deprecated.
npm WARN prepublish-on-install Use `prepare` for build steps and `prepublishOnly` for upload-only.
npm WARN prepublish-on-install See the deprecation note in `npm help scripts` for more information.

><EMAIL_ADDRESS>prepublish /path/to/dir/flowtype/flow-typed/cli
> mkdirp dist && npm run test

><EMAIL_ADDRESS>test /path/to/dir/flowtype/flow-typed/cli
> npm run clean && npm run build && npm run test-quick

><EMAIL_ADDRESS>clean /path/to/dir/flowtype/flow-typed/cli
> rimraf dist

><EMAIL_ADDRESS>build /path/to/dir/flowtype/flow-typed/cli
> mkdirp dist && babel ./src --out-dir=./dist

src/cli.js -> dist/cli.js
src/commands/__tests__/install-test.js -> dist/commands/__tests__/install-test.js
src/commands/__tests__/search-test.js -> dist/commands/__tests__/search-test.js
src/commands/create-stub.js -> dist/commands/create-stub.js
src/commands/install.js -> dist/commands/install.js
src/commands/runTests.js -> dist/commands/runTests.js
src/commands/search.js -> dist/commands/search.js
src/commands/update-cache.js -> dist/commands/update-cache.js
src/commands/update.js -> dist/commands/update.js
src/commands/validateDefs.js -> dist/commands/validateDefs.js
src/commands/version.js -> dist/commands/version.js
src/lib/TEST_UTILS.js -> dist/lib/TEST_UTILS.js
src/lib/__mocks__/node.js -> dist/lib/__mocks__/node.js
src/lib/__tests__/cacheRepoUtils-test.js -> dist/lib/__tests__/cacheRepoUtils-test.js
src/lib/__tests__/codeSign-test.js -> dist/lib/__tests__/codeSign-test.js
src/lib/__tests__/flowVersion-test.js -> dist/lib/__tests__/flowVersion-test.js
src/lib/__tests__/libDefs-test.js -> dist/lib/__tests__/libDefs-test.js
src/lib/__tests__/semver-test.js -> dist/lib/__tests__/semver-test.js
src/lib/cacheRepoUtils.js -> dist/lib/cacheRepoUtils.js
src/lib/codeSign.js -> dist/lib/codeSign.js
src/lib/fileUtils.js -> dist/lib/fileUtils.js
src/lib/flowProjectUtils.js -> dist/lib/flowProjectUtils.js
src/lib/flowVersion.js -> dist/lib/flowVersion.js
src/lib/git.js -> dist/lib/git.js
src/lib/github.js -> dist/lib/github.js
src/lib/isInFlowTypedRepo.js -> dist/lib/isInFlowTypedRepo.js
src/lib/libDefs.js -> dist/lib/libDefs.js
src/lib/node.js -> dist/lib/node.js
src/lib/npm/__tests__/npmLibDefs-test.js -> dist/lib/npm/__tests__/npmLibDefs-test.js
src/lib/npm/npmLibDefs.js -> dist/lib/npm/npmLibDefs.js
src/lib/npm/npmProjectUtils.js -> dist/lib/npm/npmProjectUtils.js
src/lib/semver.js -> dist/lib/semver.js
src/lib/stubUtils.js -> dist/lib/stubUtils.js
src/lib/validationErrors.js -> dist/lib/validationErrors.js

><EMAIL_ADDRESS>test-quick /path/to/dir/flowtype/flow-typed/cli
> jest && npm run lint

 PASS  src/lib/npm/__tests__/npmLibDefs-test.js
 PASS  src/commands/__tests__/install-test.js
 PASS  src/lib/__tests__/libDefs-test.js
 PASS  src/commands/__tests__/search-test.js
 PASS  src/lib/__tests__/cacheRepoUtils-test.js
 PASS  src/lib/__tests__/flowVersion-test.js
 PASS  src/lib/__tests__/codeSign-test.js
 PASS  src/lib/__tests__/semver-test.js

Test Suites: 8 passed, 8 total
Tests:       94 passed, 94 total
Snapshots:   0 total
Time:        4.057s
Ran all test suites.

><EMAIL_ADDRESS>lint /path/to/dir/flowtype/flow-typed/cli
> eslint .

up to date in 19.137s
All libdefs are named and structured correctly. (Found 317)
Running definition tests in /path/to/dir/flowtype/flow-typed/definitions/npm...

Fetching all Flow binaries...

All tests passed!

Am I missing something?
Environment information

Operation system: Mac OS 10.12.6
Flow version: 0.51.1

Looks like you're using the wrong command to run tests, try flow-typed run-tests knex.

Thanks replying!
However, no luck there too :(
» flow-typed run-tests knex
Running definition tests in /path/to/dir/flowtype/flow-typed/definitions/npm...

Fetching all Flow binaries...

All tests passed!

Just to confirm:

this command has to be run from the root of this repository (the flow-typed repository)
the flow-typed binary is the one that can be installed through npm

?

Weird, seems the path in the output is just random nonsense, whereas it should be a real path. Here's my output when I run it from the project's root:
➜ flow-typed run-tests knex
Running definition tests in /Users/me/workspace/flow-typed/definitions/npm...

Fetching all Flow binaries...
Finished fetching Flow binaries.

Testing knex_v0.12.x/flow_v0.38.x- (flow-v0.38.0)...
Testing knex_v0.12.x/flow_v0.38.x- (flow-v0.39.0)...
Testing knex_v0.12.x/flow_v0.38.x- (flow-v0.40.0)...
Testing knex_v0.12.x/flow_v0.38.x- (flow-v0.41.0)...
Testing knex_v0.12.x/flow_v0.38.x- (flow-v0.42.0)...

I'm not sure where /path/to/dir/flowtype is coming from... Try updating your global version of flow-typed to the latest release: npm update -g flow-typed.

Weird, seems the path in the output is just random nonsense, whereas it should be a real path.

My bad here. A real path is actually output, I just replaced it before posting my messages. I should have mentioned that, sorry.

Try updating your global version of flow-typed to the latest release: npm update -g flow-typed.

I did and I still get the same output :(
» flow-typed run-tests knex
Running definition tests in /Users/stouf/Development/flowtype/flow-typed/definitions/npm...

Fetching all Flow binaries...

All tests passed!

(I only replaced my username on my computer this time).
Compared to your output, it seems that I don't get the Finished fetching Flow binaries. message after Fetching all Flow binaries..., so maybe it silently fails? I'll try to debug the test launcher to see if I can find anything.

My bad here. A real path is actually output, I just replaced it before posting my messages. I should have mentioned that, sorry.

You know, I should have caught that, I did the same. 😛
Honestly I'm not totally sure what's going on, if I run it via flow-typed, it works as expected, but running node dist/cli.js run-tests from within flow-typed/src gives the same results. I'll do some debugging on that end to see what's going on.

so maybe it silently fails?

I could confirm it. For some reasons, the releases property doesn't exist there and the script I got from npm install -g flow-typed silently failed there.
Here is how that code looks like:
return regeneratorRuntime.awrap(new Promise(function (res, rej) {
  GH_CLIENT.releases.listReleases({
    owner: 'facebook',
    repo: 'flow',
    page: page++,
    per_page: QUERY_PAGE_SIZE
  }, function (err, result) {
    if (err) {
      rej(err);
    } else {
      res(result);
    }
  });
}));

If I get rid of the return statement, I get the following output:
» flow-typed run-tests knex
Running definition tests in /Users/stouf/Development/flowtype/flow-typed/definitions/npm...

Fetching all Flow binaries...
(node:75703) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: Cannot read property 'listReleases' of undefined
(node:75703) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

All tests passed!

The GH_CLIENT object seems to be initialized with the following lines:
console.log('Fetching all Flow binaries...');
IS_WINDOWS = _node.os.type() === 'Windows_NT';
FLOW_BIN_VERSION_ORDER = [];
GH_CLIENT = (0, _github.gitHubClient)();
QUERY_PAGE_SIZE = 100;
OS_ARCH_FILTER_RE = new RegExp(BIN_PLATFORM);
_context3.next = 8;
return regeneratorRuntime.awrap(_node.fs.exists(BIN_DIR));

Here are the properties of the GH_CLIENT object during runtime:
'config',
'debug',
'Promise',
'routes',
'acceptUrls',
'constants',
'requestHeaders',
'responseHeaders',
'authorization',
'getAuthorizationApi',
'activity',
'getActivityApi',
'gists',
'getGistsApi',
'gitdata',
'getGitdataApi',
'integrations',
'getIntegrationsApi',
'issues',
'getIssuesApi',
'migrations',
'getMigrationsApi',
'misc',
'getMiscApi',
'orgs',
'getOrgsApi',
'projects',
'getProjectsApi',
'pullRequests',
'getPullrequestsApi',
'reactions',
'getReactionsApi',
'repos',
'getReposApi',
'search',
'getSearchApi',
'users',
'getUsersApi',
'enterprise',
'getEnterpriseApi'

I looked a little deeper into that object and the only functions I could find that seem to be related to releases are:

GH_CLIENT.repos.getReleases()
GH_CLIENT.repos.getRelease()
GH_CLIENT.repos.getLatestRelease()
GH_CLIENT.repos.getReleaseByTag()
GH_CLIENT.repos.createRelease()
GH_CLIENT.repos.editRelease()
GH_CLIENT.repos.deleteRelease()

Maybe the code I got from npm install -g flow-typed got badly packaged or something?
(I'll try to dig deeper into it later, I have to leave my computer now)

@GAntoine Sorry, I missed your message while I was typing mine.

Do try running this from flow-typed/src: npm run build && node dist/cli.js run-tests knex

I guess you meant from flow-typed/cli since the dist folder gets created in it?
I removed flow-typed/cli/dist folder before running the commands you gave me and the output is unfortunately the same :(
Also, the observations I made in my previous comment applied there too.

I'm out of time tonight, but I'll spend some time looking into this tomorrow. Could also just be that the github API is having issues at the moment, what with the downtime they suffered yesterday.
Thanks for digging into this so deeply! Keep updating this issue if you find anything else.

+1, I am also unable to run tests from the CLI. FWIW, with a globally installed command line tool for running tests seems like it'd be easy for bugs to be introduced, since there's no guarantee that the CLI tool is the same version as your repo. Maybe the documentation should instead point users who are working on changes to the flow-typed repo to instead run node dist/cli.js [command]?

Update time: Looks like this commit upgraded the github dependency from ^0.2.4 to ^9.2.0, which most likely introduced breaking changes.
@davidswinegar Once this is taken care of, I'll spend some time moving CONTRIBUTING.md over to the wiki, and updating it accordingly (although if people want to help, I'd be really appreciated!)

@davidswinegar Totally agree with that 👍
@GAntoine Thanks a lot for spending time on it and sending a pull request for it :)


Can I place PIPX_BIN_DIR inside PIPX_HOME?

I would like to place PIPX_BIN_DIR inside PIPX_HOME. I.e.:
PIPX_BIN_DIR=$HOME/pipx/bin
PIPX_HOME=$HOME/pipx

Is this OK or can this cause trouble at some stage?

FWIW that’s exactly what I do and I haven’t noticed any problems.

Short answer: It will probably be fine, but it's not recommended.
PIPX_HOME is used by pipx for internal operations, so there's a non-zero danger that in the future your sub-directory could conflict with something that pipx does.  Right now I don't think there would be any conflict however, and it should be ok.

Thanks for the info. I will try to go with that scheme.
I think it could be worth considering to set PIPX_BIN_DIR by default to PIPX_HOME if PIPX_HOME is set...

I am using this set up now for a little while and it seems to work for me too. I close the issue for now.


Initial Website v1

needs registration, Date change and more content

The [https://github.com/naher94/portfolio/blob/gh-pages/mail/contact_me.php](PHP contact form) won't work.

got rid of contact form and some other resources


DOWNSTREAM: : ETCD-696: Add rev bumping to force-new-cluster

force-new-cluster seems to have similar watch cache issues as the ordinary snapshot restore. This PR introduces the already existing utl logic as a separate package into the server-side code.
This will only introduce a revbump flag, but under the hood implement both rev bumping and compaction markers.
Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.

/lgtm

/override ci/prow/configmap-scale


chore: enable allowing merge commits

this setting being off prevents merging alpha to main

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[feature request] Add ability to evaluate Source in a particular js Realm

Thank you for graaljs. It's really great!
I was thinking that it would be handy if there was API functionality to easily evaluate code in a particular js Realm, similar to https://github.com/graalvm/graaljs/blob/201226f93083c9262014e0c7ccfee3ddcf46e9c1/docs/user/JavaScriptCompatibility.md#loadwithnewglobalsource-arguments but via the Java API and a Source object. This would allow loading code without polluting the default Realm's global object, while caching the code across Contexts using the same Engine. As I understand it, loadWithNewGlobal will not cache code across Contexts because it takes a string.
We could potentially expose something like one of the following APIs, from lowest to highest level of abstraction:

expose a java realm representation and java analogues to the v8 realm builtins for creating/switching/disposing/etc. realms for a given context
have a CPS/handler-style function one could call with an anonymous function that would create a temporary child realm, switch to that realm, invoke the provided function (where a user could do whatever they want in this temporary realm, like evaluate Source), capture this temporary realm's global object, switch back to the initial realm, dispose the temporary realm, and return the captured temporary realm's global object. This approach would mean that no java representation of "realm" needs to be exposed to users.
expose a java analogue of loadWithNewGlobal that takes a Source object to eval, performing some logic like (2) internally

Without such a feature, I am currently enabling the experimental v8 Realm builtin, and performing something like the following on the javascript side:
function loadLibrary(libraryName) {
  const realmId = Realm.create();
  const globalObj = Realm.global(realmId);
  // we need to introduce a new scope in the prototype chain so that we can
  // communicate the library's name to Java, because the code in the string
  // passed to `Realm.eval` does not have access to `libraryName` from the
  // current lexical scope.
  const libNameScope = Object.new();
  libNameScope.__proto__ = this;
  libNameScope._libraryName = libraryName;
  globalObj.__proto__ = libNameScope;
  try {
    Realm.eval(realmId, 'Packages.com.foo.loadLibrary()');
  } finally {
    Realm.dispose(realmId);
    globalObj.__proto__ = this; // remove libNameScope from the prototype chain
  }
  return globalObj;
}

and the following on the Java side:
public static void loadLibrary() {
  Context c = Context.getCurrent();
  String libraryName = context.getBindings("js").getMember("_libraryName").asString();
  Source s = buildCacheableSource(libraryName);
  context.eval(s)
}

Does a feature like this seem like something you think would fit in graaljs?
Thanks again!
Brian

Hi,
providing something similar to loadWithNewGlobal (which is only available in the deprecated Nashorn compatibility mode) by default (or at least behind a flag) sounds reasonable on the long run.
We provide a Realm builtin similar to v8's d8 shell behind the js.v8-realm-builtin flag. Realm.create() could help you implement what you want to achieve then, but this is not something you should use in production code.
Best,
Christian

Hi all,
This workaround I've been using (Realm.create, then Realm.eval that uses interop to call a java function to load the library) apparently creates a new Context each time it's called. This is problematic because I end up running into https://github.com/oracle/graal/issues/631.

Is this current behavior (Realm creation creating a new Context) intentional?
Would it be possible for this requested feature be able to execute code in multiple realms without creating more than a single Context? (From what I understand, this would mean something like: change the toplevel binding scope for the current Context while executing code in a specified realm)

Unfortunately I think I am a little stuck at the moment without the ability to load code into separate realms and share values created across these loads. I am using realms because I need to be able to load different Sources without everything polluting a single shared global namespace.
Thanks for your help,
Brian

@wirthi @eleinadani in the shorter term, maybe I could try changing the Realm impl to only use a single Context (i.e. without trying to add more first-class Realm support)? What do you think?

Hi @bts the current semantics of Realm.create() is intentional, as we try to be compatible with what v8 does. Sharing the same (internal) context might work in your case, but could potentially break our v8 compatibility mode, so I am afraid this is not a solution that we can merge. Tc39 is currently working on a new spec proposal called Realms, which provides a new mechanism to execute JS code with a new global (https://tc39.es/proposal-realms/ and https://github.com/tc39/proposal-realms). This is currently at stage2, but we are following the discussion and we will implement the specification once it reaches stage3.

Hi @eleinadani. Great -- thank you! I will stay tuned in!

I am closing this ticket. We will support this feature as part of the Realms proposal, once that hits stage 4 of the ECMAScript process.


Update config.yml

Fixes #
Describe the changes you have made in this PR -
Screenshots of the changes (If any) -
Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

Coverage remained the same at 82.034% when pulling 53a7d74f6a0c187f9591531e747ae6140747d4bb on Mbiakop1:patch-1 into d7083d6ca6f5f89ed534ee5990277ce2f62df929 on CircuitVerse:master.


Inform people that this is deprecated

When do you will add text that this project is deprecated?

 I m using this repo in in a very important project

@Syfele It seems dead. We also use it on our main web project and decided to remove it. Still figuring out a good way on how to.


Feature request: 2D line plot

Hi,
I have looked at the documentation/code and I don't think a 2D line plot is supported in Vaex.  I would like to plot 100M rows of data from a hdf5 column to create an interactive plot in Jupyter.  I would prefer bqplot to matplotlib if possible.

Hi,
thanks for showing interest. What do you mean by a 2d line plots. Can you be more specific? Would it be 100M different lines? And can you give me an example where this is useful, I'm curious what you have in mind?
cheers,
Maarten

Hi Maarten,
Thanks for the quick response. I would like to plot long time histories of data.  A typical hdf5 file would have 100 columns and 100 million rows. I would like to plot maybe 2 or 3 of these columns ( different colour lines for each column)  against  time on the x-axis. The equivalent plot type In matplotlib would be similar to  the plt.plot(x, y, linestyle='-') . I would also like to create virtual channels with the data (statistics, sum, mean, rolling mean etc etc) .   I have been down sampling the data to plot it in jupyter  but it would be nice for the user to be able to zoom into the data interactively. Because the data set cannot fit into memory, I thought maybe Vaex or Dask/Datashader/Holoviews technology could be a good solution. Would Vaex be suitable for this type of application?
Doug

Hi Doug,
ok, I think I now understand what you want. Is the sampling regular? If not, I assume you have a column containing the time, if that is the case, you could do sth like this:
ds.plot1d('t', what='mean(amount)')

If it is regularly sampled, I need to think about it, but I have some ideas.
cheers,
Maarten

Hi Maarten,
Yes, I have 1 column for time. All other columns are the other data channels that would be plotted against time.  The time samples are not alway regular.
I tried the code below but it didn't give an output.
import vaex as vx

dataset = vx.datasets.helmi_de_zeeuw.fetch()

dataset.plot1d("x", what='mean(y)')

I have created a Jupyter notebook to better explain what I would like Vaex to do.  I can't attach notebooks to Github issues so I will email it to you.   I would be interested in what you think and whether or not it would be worth implementing in Vaex.
Thanks, Doug

Yes, feel free to send me by email. Try adding the following magic:
%matplotlib inline

Or try adding show=True to the plot1d command.

Maarten,
I have done it!  Thanks very much for your help.  I love the power of expressions in Vaex.
For reference,
I used this code in the BQplot brush interval callback:
    # expression to find time range (index),  Where 'a' is list of min + max of selected range
    tExpression = "abs(" + str((a[0] + a[1])/2) + " - index) < " + str((a[1]-a[0])/2)

    # Save a data selection method
    price_dataVX.select(tExpression, name='xpos')

    # Create mean of binned data
    t = price_dataVX.mean("index", binby="index", selection = 'xpos', shape=samplePoints, limits=[a[0],a[1]])
    data = price_dataVX.mean(symbol2, binby="index", selection = 'xpos', shape=samplePoints, limits=[a[0],a[1]])

Cheers,
Doug

Hi Doug,
thanks for sharing this and your enthousiasm, glad you like using vaex!
cheers,
Maarten


Change IntOrString field types from string to object

IntOrString is better represented as object in python (and I can argue in most of the other languages too). That way we won't have any type check on it which is not ideal but it is better than consider it as string because both serialization and deserialization would be wrong that way.
fixes #18
(It is not a 100% fix but I think it is close enough to fix that issue. Only missing thing for IntOrString is typecheck which is not a big deal, if it is at all, in python but could be an issue in other languages).

LGTM 👍


The location of cue

After installing cue, where can I find the location of cue in my computer?

In mac OS or linux operating system, can you tell me the location in all possible scenarios, including:
binary install; from source(through go). I want to know whether the user has installed cue, so they can use cue fmt in the command line.

can you tell me the location in all possible scenarios

Generally speaking, no.

I want to know whether the user has installed cue

The which tool can tell you this. Many languages have a similar helper in their stdlib. You can also try running cue help and catch what happens.

so they can use cue fmt in the command line

It will have to be somewhere in their PATH. That should make things easier for you


Running piped SQL file that drops and adds a table produces different results on subsequent runs

Repo: corona-virus
Branch: case_details_virological_dot_org
This SQL: https://drive.google.com/open?id=1nZJyvSfZspMnIixZtmW3uRM0xYT7dloW
When run twice on the same working set produces no diff and the this diff summary:
Timothys-MacBook-Pro:corona-virus timsehn$ dolt diff --summary
diff --dolt a/case_details b/case_details
--- a/case_details @ ugcofv63pv8mqvq40h0esr4p7qm010qo
+++ b/case_details @ p11dee7ecl08h9g8ml3jrpnnqj48o5mm
48,601 Rows Unmodified (98.42%)
0 Rows Added (0.00%)
779 Rows Deleted (1.58%)
0 Rows Modified (0.00%)
0 Cells Modified (0.00%)
(49,380 Entries vs 48,601 Entries)

It seems to deterministically delete all rows for the Hubei sheet source key with ID above 20463.

Reproduced this with latest build. Not sure what's happening yet, but have some ideas.


Azure DevOps Artifacts Nuget Feed Badge, run [nuget myget chocolatey resharper]

@calebcartwright marked #4182 as a good first issue so I decided to give it a shot.
With this shield, you can get the same kind of shield that you get from the existing nuget shield, but this one uses Azure Artifacts as a back end instead of nuget.org. The azure artifacts shield requires more information than the traditional nuget shield.
An example shield path would be /azure-devops/vpre/dotnet/RX.Net/RxNet/System.Interactive.
Azure Artifacts feeds support multiple views. You can specify a specific view as an optional parameter in the shield path right before the package name. For example, /azure-devops/vpre/dotnet/RX.Net/RxNet/release/System.Interactive
I felt that the way that the nuget shield is currently implemented is kind wonky with the withTenant and withFeed options. I didn't think that approach would scale to multiple different kinds of nuget feeds. So I factored the fetch logic into a separate "nuget-v3-helpers" file. This way, different nuget package feeds (nuget.org, myget, azure devops artifacts, github package registry, sleet, etc) could share the core nuget feed search logic while each one can have it's own custom route configuration to generate the base nuget feed URL.
I did modify the package fetch logic a bit. I was hitting an issue where the package query returned more than one package. For example, searching for Some.Package will return Some.Package and Some.Package.MoreDetails. So I modified the logic to explicitly check package name. I also added a getLatestVersion helper function that explicitly sorts by decending semver + does the prerelease filtering.
I'm creating a draft pull request because I still need to go back and update the existing nuget and myget shields to use this new approach. But I wanted feedback that I was on the right path before doing that work.

Warnings

:warning:
This PR modified service code for azure-devops but not its test code. That's okay so long as it's refactoring existing code.

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @devhawk!

  Generated by :no_entry_sign: dangerJS against 08cc766c8a5fc9fa83918a498cd156fe4f273118

Hi @devhawk thanks for the PR!
I still think there's a need to investigate whether the Azure DevOps REST APIs for Artifacts (like this) can be leveraged directly, allowing Shields to provide AzDO Artifact badges for all package types (not just nuget) with a single implementation.
The other thing we have to keep in mind both with AzDO and other providers is support of private projects/feeds/etc. Shields already supports providing various AzDO badges for content from private team projects (test results, code coverage, and build/release status), and we'd naturally want to be able to do the same for artifact-related badges.

This way, different nuget package feeds (nuget.org, myget, azure devops artifacts, github package registry, sleet, etc) could share the core nuget feed search logic while each one can have it's own custom route configuration to generate the base nuget feed URL

I'm not familiar with sleet, but there are some relevant service/platform specific contexts to keep in mind. For example, we've actually already got an implementation for GitHub Package Registry (like #4184) that supports badges for all package types, and handles the authentication, token pooling for rate limiting mitigation, support for private artifacts, etc. that are associated with GitHub. It does so via the native GitHub v4 APIs.
I'm also not sure I follow what you had in mind regarding sharing the core nuget feed search logic, could you elaborate? The core code dealing directly with nuget feeds is already pretty well encapsulated and reused IMO, so the various service classes that are dealing directly with nuget feeds are really lightweight (mostly just example listings that display on the front end)
https://github.com/badges/shields/blob/master/services/nuget/nuget.service.js
https://github.com/badges/shields/blob/master/services/myget/myget.service.js
https://github.com/badges/shields/blob/master/services/chocolatey/chocolatey.service.js
https://github.com/badges/shields/blob/master/services/resharper/resharper.service.js

I took a cursory look at the azure artifact REST api using insomnia - that approach should would work. Probably need to use the Get packages endpoint because Get Pacakge needs the package to be specified by GUID ID which doesn't seem to be easily discoverable (it's buried in a huge pile of JSON on the azure artifacts package web page).

I took a cursory look at the azure artifact REST api using insomnia - that approach should would work. Probably need to use the Get packages endpoint because Get Pacakge needs the package to be specified by GUID ID which doesn't seem to be easily discoverable (it's buried in a huge pile of JSON on the azure artifacts package web page).

Nice! And yeah if there's an API available that allows Shields to accept more user-friendly params that's always worthwhile 👍

What I meant by sharing the core nuget feed search logic was that - at least for the nuget/myget v3 services - I didn't think the nuget query logic was well factored. Because there is a single base NugetVersionService used for both nuget and myget, there's a bunch of switching logic in buildRoute that feels like it should be in sub classes rather than in the base class.
If you look at this PR, you'll see that I factored the fetch logic out so that it could be shared by multiple different nuget based shields. Each shield would be responsible for it's own route, using the route information to construct a nuget base URL which it then passes to the fetch logic.
Clearly, the REST/universal approach is the right choice for this service. And the other nuget feeds all seem to have a simple custom base URL except for myget so I wouldn't think it would be worth refactoring the pure nuget feed approach.

Sleet is a static nuget feed generator. Like Jeckyll or Gatsby but for nuget feeds.

What I meant by sharing the core nuget feed search logic was that - at least for the nuget/myget v3 services - I didn't think the nuget query logic was well factored. Because there is a single base NugetVersionService used for both nuget and myget, there's a bunch of switching logic in buildRoute that feels like it should be in sub classes rather than in the base class.

Thanks for elaborating. I've not worked with any of the nuget-related Shields code myself, but I believe that encapsulation and generalization was done deliberately to make it really simple to provide the range of package-related badges for any additional platforms/services that we'd have to integrate with at the feed level (it's not just for nuget.org/myget). That's exposed via the service family generator functions and helps avoid a lot of the duplicative code in the various service classes that was repeated in each of the service classes, for each of the platforms previously.
We're always open to improvements though so if you feel it could be better and are willing, feel free to open a new PR and we'll be happy to take a look and discuss!

Hey @devhawk, I wrote what's there, and while I have opinions on things 😃 I am by no means attached to the way this is written now.
A point where Caleb and I agree is that helper functions + composition are often clearer ways of decomposing services, preferable to complicated inheritance hierarchies. It seems like you're largely on the same page with us there.
I'm happy for you to take a shot at revisiting and refactoring these, especially if there are ways to make things work better by breaking out some helper functions. Moving some of the feed URL generation responsibilities to the service class seems fine. We probably don't want to repeat a bunch of code, but it's also possible to replace the create... functions with a small amount of boilerplate that delegates to a "build route" function or a feed URL generation function that uses the withTenant and withFeed abstractions. Also, if these don't make sense at all let's toss 'em out the window, and replace with an abstraction that better fits the way we think this rather large family of services will grow going forward.
For what it's worth, I have never used any of these services, so my rewrite came largely from the existing implementations – plus one of the services had just migrated from v2 to v3. It was not with any deep understanding of NuGet or what might be possible or desirable. They've been pretty stable since then but that's not signal that they're factored correctly, as much as signal that they have good tests. It's our service model rewrite (#963) which prompted that.
By all means, if you are interested in continuing to work on, or refactor these, we'd both welcome you to do that. 😀

A point where Caleb and I agree is that helper functions + composition are often clearer ways of decomposing services, preferable to complicated inheritance hierarchies. It seems like you're largely on the same page with us there.

That's a much better explanation of what I was trying to say! Thanks @paulmelnikow.
My primary interest is in getting an azure artifacts shield. Not sure when I will have time again to work on it - today was kind of a fluke - but when I do I'll also take a stab at reworking the nuget shields - the v3 ones anyway since it's only the myget shield that requires anything more complex then a custom hard-coded base url


Implement support for Cassandra

Implement an extension to JPA-Unit which supports all the JPA-Unit tools with Cassandra.
The idea is to be able to use JPA providers, which support NoSQL databases, thus to be able to reuse (to a certain extent) existing code and test implementation when switching between different data base types or when using different types of data bases (polyglot persistence) in one project.
Cassandra seems to be supported by following JPA provider:

EclipseLink
DataNucleus
Hibernate OGM (Experimental)
Kundera

Issue encountered with hibernate OGM OGM-1324

Issue encountered with Datanucleus as well. See datanucleus/datanucleus-cassandra#32 for detail.

Kundera and EclipseLink enforce additional code level dependencies making re-usage of so far used test data model impossible.

test data models are project specific now


OLS-448: Bump project deps

Description
Bump project deps
Type of change

[x] Bump-up dependent library

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.78%. Comparing base (4f81c36) to head (01321b4).
Report is 18 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #781      +/-   ##
==========================================
+ Coverage   94.67%   94.78%   +0.10%
==========================================
  Files          53       55       +2
  Lines        1935     2012      +77
==========================================
+ Hits         1832     1907      +75
- Misses        103      105       +2

see 5 files with indirect coverage changes

/lgtm

/approve

/retest

/retest


chore: 统一 playground 代码风格

👀 PR includes

✨ Feature

[ ] New feature

🎨 Enhance

[ ] Code style optimization
[ ] Refactoring
[ ] Change the UI
[ ] Improve the performance
[ ] Type optimization

🐛 Bugfix

[x] Solve the issue and close #0

🔧 Chore

[ ] Test case
[ ] Docs / demos update
[ ] CI / workflow
[ ] Release version
[x] Other ()

📝 Description
在写视频demo 的时候，发现的一些小问题

fix: 修复启动demo时，只填入 dataCfg 报错问题

chore: 统一 playground 代码风格

fix: 修复 eslint 报错

fix: 这个下钻样式已经不使用了，统一到 s2-share 了

fix: playground 不需要导出类型声明文件

🖼 Screenshot

Before
After

❌
✅

🔗 Related issue link

🔍 Self-Check before the merge

[ ] Add or update relevant docs.
[ ] Add or update relevant demos.
[ ] Add or update test case.
[ ] Add or update relevant TypeScript definitions.

:tada: This PR is included in version @antv/s2-react-v1.28.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Set no shallow clone for tenacity

As noted in https://github.com/rtfd/readthedocs.org/issues/5031, I'm asking to disable shallow clone for tenacity.
We're using reno to maintain our release notes and shallow clone breaks it.
Thanks!

Done


Correct SHA-512 hash for CGAL-4.11.1 package.

Current port for CGAL-4.11.1 contains a wrong SHA-512 hash. Package cannot pass verification.

my bad for not looking at #2962 😝


game crashes after loading cheat dll

Describe the bug
if im new i will ned to learn even how to inject it on manual map or something with extreme injector
To Reproduce
Steps to reproduce the behavior:
using extreme injector manual map
Expected behavior
open menu in main lobby
Screenshots
injected succesfully but closing game
Additional context
Add any other context about the problem here.

use CS2 Injector from UC
https://www.unknowncheats.me/forum/counter-strike-2-a/606455-cs2-injector.html
Extreme tends to cause issues.

#67


Gown Detail View Component

Nobody was assigned this component

Too broad, @mdrisco4 - much of your work already covered this I think. I'll review before making more tickets.


Continue to clean up the long tail of the archive

🚀 Deployed on https://66564c6a7c2666a252518d33--alexwlchan.netlify.app


Migrate to 1KGP reference panel for testing

Addresses issue #10

Reorganized input json directory structure, with templates at /inputs/templates, value jsons at /inputs/values, and default builds in /inputs/build. Build paths have been cleaned up to be more intuitive.
Removes ref_panel_v1x from the set of test data
Fresh run of the 1000 Genomes reference panel, ref_panel_1kg. This was generated using a new workflow by running GATKSVPipelineBatch using the Cromwell config option --final-workflow-outputs-dir to copy outputs to a permanent location, and then feeding the metadata to a new script at scripts/inputs/create_test_batch.py to generate input values at inputs/values/ref_panel_1kg.json.
Updated readme to reflect changes, including a new section: "Generating a reference panel"
Renamed wdl_test dir to carrot

Thanks for the thorough review, @epiercehoffman !

I think it would be nice to have a smaller test batch for when we are testing changes to GatherSampleEvidence - I usually use test_small for this, but here you'd have to run all 156 samples or manually edit a JSON

I agree it would be nice to have a smaller cohort. IMO, it's a bit cluttering and adds maintenance to have two separate cohorts, especially if one can only be run partway through the pipeline. I think eventually we'll want to consider running on a couple of chromosomes (say 21 and Y), but that will require some updates to the wdls and likely some bug fixes in places.

I think it would be beneficial to be able to generate test JSONs for a 2-batch cohort matching the contents of the Terra workspace, both to test multi-batch steps and to match the Terra workspace more closely. I'm not totally sure how best to implement that - it could work as a separate test_batch with its own values JSON, but there will be duplicated information across the 1-batch and 2-batch JSONs in that case

Yes we should have something for the 2-batch testing and Terra workspace. I think that would have to be defined as a separate test batch, even if some of the data are the same. Might be good to open an issue for this.

The inputs/ directory gets nested so deeply which is a little cumbersome to work with. I'm not certain what to change though

I think it's an improvement to have everything in an inputs directory - the old organization was a bit confusing IMO. I don't know what to do about nesting but I feel like everything is organized in a more logical way now.

Nesting the Terra cohort mode JSONs under ref_panel_1kg doesn't fully make sense since the Terra workspace uses 2 batches so it is a superset of the ref panel samples. If a 2-batch test set were to be added, it would fit better under there

Yes when we add a 2-batch test, we can also generate a workspace for that. Not sure if we have a 1-batch workspace currently? But this way one can create the workspace for single-batch at least without needing access to our workspaces.


chore(main): release 1.1.1

:robot: I have created a release beep boop
1.1.1 (2024-05-24)
Bug Fixes

add new mrburns version url (ef74f14)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/emberist/mrburns/releases/tag/v1.1.1 :sunflower:


Update cloud-management-gateway-faq.md

Summarize the change in the pull request title
Describe your change, specifically why you think it's needed.
Fixes #Issue_Number (if necessary)

@RobYork : Thanks for your contribution! The author, @aczechowski, has been notified to review your proposed change.

#sign-off

@RobYork - I can't verify the link. I'm going to merge this PR (as it seems like the link should work), but you will need to check the live article and verify that the new link works.
thanks.


React adapter states not functioning as intended

Describe the bug
I've only tested this on Phantom wallet, but if you switch between wallets more than 2 times you are greeted with an error and no state updates for the publicKey on the useWallet hook.
To Reproduce

Use react wallet adapter like shown in example
use the multi button to connect wallet
in phantom switch the active wallet to a different wallet
in phantom switch the active wallet back to the original or a different wallet again

Expected behavior
wallet adapter doesn't break and updates the current actively selected wallets states like intended.
Screenshots

Desktop (please complete the following information):

OS: Windows 11 22h2
Browser Firefox Developer Edition
Version 109.0b7 (64-bit)

Additional context
Add any other context about the problem here.

Nevermind...? I went to bed, woke up today and now its not an issue??


Support for configuring non-ascii characters to be invalid

Please describe the feature that you are requesting

It seems to me that email servers / SMTP servers often (normally?) do not support non-ascii characters in local part or domain, even in countries where it is common with non-ascii characters in names (such as æ, ø, å in Norway).
It would be really nice with a feature for configuring non-ascii characters not to be valid.
E. g<EMAIL_ADDRESS>should fail.
Additional context

Hi @frodeto, thanks for opening this issue! Somewhat related to #149, but this seems like a good enhancement that would be straightforward to implement. I'm going to try and get this added in the next week.

This feature is now available in v1.6.0! Example:
EmailValidator validator = JMail.strictValidator().requireAscii();

validator.isValid("jørn@test.com"); // returns false


1805 missing rate limit creates ddos potential

🗣 Description
Imported express-rate-limit to backend/src/api/app.ts  to limit how many times a user authorization request is accepted per 10 minute window. I set a rate limit of 100 calls per 10 minute window per IP address for the '/matomo' and '/pe' endpoints.
💭 Motivation and context
CodeQL flagged flagged as a high severity vulnerability, in the GitHub security tab under Code Scanning. I applied a generous limit to mitigate any negative side effects this change might cause for IPs associated with a proxy/load-balancing server.
🧪 Testing
I tested to ensure that the limiter only blocked requests once the limit was reached. I did this by setting the limit to 1 request per 10 minute window then I called the /matomo endpoint 2 times. The first request returned a status 200 and the second request returned a status 429 (Too Many Requests). I then changed the limit back to 100 per 10 minutes, called the /matomo endpoint a third time, and confirmed that the response headers displayed the correct RateLimit-Limit and Retry-After.
📷 Screenshots (if appropriate)
Testing that rate limit rejects calls after being reached.

Testing that rate limit displays correctly in response headers.

✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.

[x] Changes are limited to a single goal - eschew scope creep!

[x] All relevant type-of-change labels have been added.

[x] I have read the CONTRIBUTING document.

[x] These code changes follow cisagov code standards.

✅ Pre-merge checklist

[ ] Revert dependencies to default branches.
[ ] Finalize version.

✅ Post-merge checklist

[ ] Create a release.

https://www.serverless.com/plugins/serverless-api-gateway-throttling

As discussed, let's 1) keep this code in but with a comment explaining it only works locally and 2) set up serverless api gateway throttling https://www.serverless.com/plugins/serverless-api-gateway-throttling

Closing this since rate limits will be implemented through AWS.

Oh — I thought the last time we discussed we decided that we can merge
this, provided there’s a comment added that the rate limits would apply
only when running the app locally / not using AWS lambda?
Ashwin
On Fri, Apr 21, 2023 at 2:09 PM Matthew @.***> wrote:

Closed #1806 https://github.com/cisagov/crossfeed/pull/1806.
—
Reply to this email directly, view it on GitHub
https://github.com/cisagov/crossfeed/pull/1806#event-9069977129, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAM4MX254SLQB2HHL6XFMOLXCLEMPANCNFSM6AAAAAAW4LGZAA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
--
Ashwin Ramaswami


Require types to be contextually canonical in AbstractionPatterns

Because violations of this might have made an AbstractionPattern incorrectly show up as abstract, it's possible that this will cause an ABI change.  However, I haven't been able to find any examples where it does, and certainly there's no way we can promise to maintain the old behavior, especially since it's not done consistently.

@swift-ci Please test


Hot reload edge cases should be better documented

Users are often surprised when a hot reload will not update certain parts of their Dart code. We should do an update of https://docs.flutter.dev/tools/hot-reload to better describe the limitations and edge cases of hot reload.

Example: an anonymous closure reachable from main was not re-compiled after a hot reload, the workaround was moving the closure to a top level function: https://github.com/flutter/flutter/issues/54395

Referring to the below issue

#62962

We should guide users that are building applications with multiple modules about how to correctly setup their projects so that hot reload/restart are working as expected. The user in the above issue was not aware that placing multiple modules inside the lib/ directory would prevent hot reload/restart from working


Simplified kong config

removed need for the user configure the LFH host IP
removed hosts clause from the kong matching on each transaction
removed http from the kong config, since that port isn't open anyway

opening a new PR on a new branch with only the changes I need on that branch.


Ackermann Steering Plugin

Summary
This adds an Ackermann Steering Plugin based on the differential drive plugin.
The plugin accepts a linear velocity (x) and a rotational velocity (z) the same as the differential drive plugin and sets the vehicle drive and steering joints to achieve the requested inputs.  The plugin and integration tests are largely based on the differential drive plugin.
Items to consider:
SpeedLimiter.cc and SpeedLimiter.hh are identical copies from the diff_drive plugin
Odometry is not as accurate as a pure diff_drive robot.  I had to open the integration tests limit up from 1cm to 25cm when comparing odometry to ground truth in the integration tests.  I tried various ground friction coefficients and using the wheel
slip plugin, but I did not achieve 1cm accuracy for the odometry.
There is a lot of commonality between the differential and Ackermann plugins.  It might make sense to merge them at some point in the future when the Ackermann plugin has aged a bit and is stable (to minimize risk to the heavily used diff drive plugin).
I was not able to generate a coverage report.
Test it
The plugin can be tested using examples/worlds/ackermann_steering.sdf
Checklist

[x] Signed all commits for DCO
[x] Added tests
[x] Added example world and/or tutorial
[x] Updated documentation (as needed)
[NA] Updated migration guide (as needed)
[x] codecheck passed (See contributing)
[x] All tests passed (See test coverage)
[?] While waiting for a review on your PR, please help review

@osrf-jenkins retest this please

Remember to sign all your commits.   I would have expected github to handle signoffs.  I have made a couple of attempts to resolve it, but my googling has not found a successful way to resolve it.
I believe I have addressed the issues from the two reviews.

I would have expected github to handle signoffs.

Yeah unfortunately GitHub doesn't make it easy to sign commits from the web UI. We've been manually adding the signature for those cases.
One way of solving this would be by adding the signature locally while rebasing and then force-pushing. If this is too much trouble, we can manually accept the DCO check since all other commits are properly signed.

One way of solving this would be by adding the signature locally while rebasing and then force-pushing. If this is too much trouble, we can manually accept the DCO check since all other commits are properly signed.

If you could, please manually accept the DCO check.
Adding the signature locally/rebasing/force-pushing was one of the approaches I tried a couple of different ways, but it didn't work for me in this case.


add graphcool (or any) authentication

Is there any plan to add an example with graphcool authentication (or any authentication) to show/hide routes/data for logged in users?
I think it'd be quite handy to see the 'done properly' way of doing this.

I'm working on authentication this week. It'll handle OAuth and updating a local Redux store too. Will keep you posted.

👍

FYI for related threads - see https://github.com/reactql/kit/issues/59#issuecomment-323509731 for an update on adding auth.

See https://github.com/reactql/kit/issues/38#issuecomment-325102058 for an update

Video explainer on YT -> https://youtu.be/s1p4R4rzWUs
I'll go ahead and close this now, but will update the thread once I've also added social logins.

Passport.js has been integrated, with a Facebook example ->
https://github.com/reactql/examples/tree/master/auth
Video commentary to follow later.


Poc of interface guiding user to physical device instructions

Codecov Report
Base: 92.50% // Head: 83.46% // Decreases project coverage by -9.04% :warning:

Coverage data is based on head (d7cca13) compared to base (85fcc1b).
Patch coverage: 42.15% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop      #76      +/-   ##
===========================================
- Coverage    92.50%   83.46%   -9.05%
===========================================
  Files           27       31       +4
  Lines          961     1137     +176
===========================================
+ Hits           889      949      +60
- Misses          72      188     +116

Impacted Files
Coverage Δ

src/ragger/backend/__init__.py
37.50% <0.00%> (-12.50%)
:arrow_down:

src/ragger/gui/interface.py
29.41% <29.41%> (ø)

src/ragger/gui/process.py
35.21% <35.21%> (ø)

src/ragger/backend/physical_backend.py
67.44% <67.44%> (ø)

src/ragger/backend/ledgercomm.py
100.00% <100.00%> (+7.24%)
:arrow_up:

src/ragger/backend/ledgerwallet.py
94.64% <100.00%> (+5.60%)
:arrow_up:

src/ragger/gui/__init__.py
100.00% <100.00%> (ø)

src/ragger/logger.py
88.23% <100.00%> (+0.73%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Cilium 1.12.2 CNI daemonset pods failing

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Hi All,
We are trying to deploy Cilium CNI helm chart using terraform on EKS cluster, we are planning to use a dedicated subnet to deploy the pods and below are the params which we are using to deploy the same :
ipam:
  mode: eni
cni:
  chainingMode: aws-cni
  configMap: cni-configuration
  customConf: true
enableIPv4Masquerade: false
endpointRoutes:
  enabled: true
eni:
  enabled: true
  subnetTagsFilter: Identifier=eks-pods
tunnel: disabled
hubble:
  relay:
    enabled: true
  ui:
    enabled: true

We have created a configMap,  to use subnet-tags and enabled customConf to use the same. With this method, we are observing an issue where the Cilium daemonset pods are failing with below errors :
Startup probe failed: Get "http://<IP_ADDRESS>:9879/healthz": dial tcp <IP_ADDRESS>:9879: connect: connection refused
When we observe the pod logs, we could see the below message :
msg="Waiting for IPs to become available in CRD-backed allocation pool" available=0 helpMessage="Check if cilium-operator pod is running and does not have any warnings or error messages."
Cilium operator is running fine and could see that it is able to get the subnets, but it has some warnings as below :
level=warning msg="Instance not found! Please delete corresponding ciliumnode if instance has already been deleted."
Have seen few other issue, mentioning this error but heard this issue has been resolved post v1.11.. So could you please let us know how to debug the same and know the issue. Deployment is getting successful, if we dont use "subnetTagFilter", the pods are not complaining but the pods are not getting deployed to expected subnet.
Cilium Version
1.12.2
Kernel Version
5.4.209-116.367.amzn2.x86_64
Kubernetes Version
1.22
Sysdump
No response
Relevant log output
No response
Anything else?
No response
Code of Conduct

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

Hi Team,
Can someone let me know if this is expected or is it some kind of bug (or) how to debug this further.
Thanks and Regards,
Sandeep.

@joestringer FYI..

@Sandy7894 did you try to delete the CiliumNode as the warning message from the cilium operator mentions?

@Sandy7894 Could you try with the latest version of Cilium? There may have been some improvements to this area in newer versions.


413 Request Entity Too Large with mirror-registry 2.0.3

When pushing big images to quay installed by mirror-registry 2.0.3 I'm getting this error
413 Request Entity Too Large

Note that this is working with mirror-registry 1.3.5. I will try also other versions.
EDIT: it is working also with 1.3.10

Hey @apodhrad, What is the size of the size of the image? Are you able to share it so we can try to recreate?

@apodhrad We tried to reproduce this issue as you mentioned, but when pushing image with large layer size "9.4GB", can't reproduce this issue, is it possible to share the image to confirm.
[centos@ip-10-0-1-4 ~]$ ./mirror-registry --version

   __   __
  /  \ /  \     ______   _    _     __   __   __
 / /\ / /\ \   /  __  \ | |  | |   /  \  \ \ / /
/ /  / /  \ \  | |  | | | |  | |  / /\ \  \   /
\ \  \ \  / /  | |__| | | |__| | / ____ \  | |
 \ \/ \ \/ /   \_  ___/  \____/ /_/    \_\ |_|
  \__/ \__/      \ \__
                  \___\ by Red Hat
 Build, Store, and Distribute your Containers

mirror-registry version v2.0.3

[centos@ip-10-0-1-4 ~]$ podman push quayomr.qe.devcluster.openshift.com:8443/quay/test123 --tls-verify=false --creds quay:***
Getting image source signatures
Copying blob 2653d992f4ef done   |
Copying blob 637a3c7a75fa [===>----------------------------------] 1.1GiB / 9.4GiB | 260.1 MiB/s

[centos@ip-10-0-1-4 ~]$ podman push quayomr.qe.devcluster.openshift.com:8443/quay/test123 --tls-verify=false --creds quay:***
Getting image source signatures
Copying blob 2653d992f4ef done   |
Copying blob 637a3c7a75fa done   |
Copying config 76e8b2c5c2 done   |
Writing manifest to image destination

Hi @LiZhang19817 I hit exactly the same error.
Unfortunately, today with a fresh install I was not able reproduce it :(

@apodhrad Is it possible to share your test image then we can see if it's the same issue.


ci: add build-wheel job

Description
I added a CI job build-wheel, that runs on each pull request.
The job will build the frontend bundle using webpack and then build a python wheel.
The wheel will be renamed from the default name rdmo-{version}-py3-none-any.whl (e.g. rdmo-2.0.2-py3-none-any.whl) to rdmo-{version}-pr{pr-number}-py3-none-any.whl (e.g. rdmo-2.0.2-pr-802-py3-none-any.whl). This enables developers to install the wheel locally or on their test servers and then test the changes of a PR. The renaming makes it easier to tell the difference between wheels from different PRs.
Is the renaming reasonable or should it I remove this step?
Also I chose master as the target branch for this PR, because dev-2.0.2 was already merged and 2.1.0 is behind master.
Related issue: #802
Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[x] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Checklist

[x] I have read the contributor guide.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

coverage: 80.917%. remained the same
when pulling c6ef0b58595075f98eef1296836f43fd6594fec0 on afuetterer:802-build-wheel-in-ci
into a54867e9604bf7ed604ff45ce219bbc33f5ff21e on rdmorganiser:master.

Example wheel for this PR (812): https://github.com/rdmorganiser/rdmo/suites/17875312643/artifacts/1026211993

Does this work for you, @MyPyDavid? Can you try to install the wheel from the uploaded artifact?

Not directly, the filename needs to follow a certain pattern.

Wheel files typically follow the pattern {distribution}-{version}(-{build tag})?-{python tag}-{abi tag}-{platform tag}.whl.
Here's an example of a valid wheel filename: example_pkg-0.0.1-py3-none-any.whl.

I cant really find an easy explanation for this.

eg.  https://peps.python.org/pep-0425/

Maybe just keep a simple filename of that format?

Sure, that is the default. I thought, if multiple PRs are in the works at the same time, you might want to differentiate between the wheels of the PR.
Do you prefer rdmo-2.0.2-py3-none-any.whl?
Then I will remove the renaming step.

yes, thanks, then it has to just be locally differentiated between PRs.
Is there not something possible with versioning of rdmo or setting a tag when building the wheel?
so that pip show rdmo shows another version than just the release

I don't understand.
You need all the wheels in PRs to the dev-2.1.0 have this name:
rdmo-2.1.0-py3-none-any.whl, correct?
Then you need to differentiate between them by another layer? What would that layer be?
The version, in this case, is 2.1.0 for all wheels.
What you mean by tag?
These are the options for build:
https://pypa-build.readthedocs.io/en/latest/index.html#python--m-build-options
You can pass options to setuptools.build, I guess. But I don't understand what you need here.
If the same is fine for you, I will just remove the rename step and you could do the differentiating manually on your system?

Rename wheel to valid wheel name, keep none and any.
Maybe change version to rdmo version + Dev(pr-number).

@MyPyDavid: I changed the renaming to create a valid wheel filename.
What do you think of rdmo-{version}dev{pr-number}-py3-none-any.whl
e.g. rdmo-2.1.0dev812-py3-none-any.whl
where dev81 stands for PR #812.

nice!
Here are some infos for downloading artifacts via the CLI, https://github.com/actions/upload-artifact/issues/89.
I would include a download via shell script in my rdmo-app for this for example.
We could add it to rdmo-docs-en eventually, to include it in dev setup docs as a pre-release or feature-preview set up right?

Excellent. Can you try to install the wheel from https://github.com/rdmorganiser/rdmo/suites/18249482442/artifacts/1054627559?

yes, I could install it and it runs!
eg. pip install rdmo-2.0.2dev812-py3-none-any.whl'[allauth]'

Waht about a + sign: https://packaging.python.org/en/latest/specifications/version-specifiers/#local-version-identifiers?

Where do you want the +?
Please give me the desired wheel name and I will adapt the rename step.

Sorry, my suggestion would be rdmo-2.0.2+pr812-py3-none-any.whl which I guess is conformal with the local version identifiers in the linked document. They are however designed to be used for downstream packages, like a distro specific version of e.g. requests or so. I am not super sure if it is ok to use it for this purpose here.

Local version identifiers SHOULD NOT be used when publishing upstream projects to a public index server, but MAY be used to identify private builds created directly from the project source. Local version identifiers SHOULD be used by downstream projects when releasing a version that is API compatible with the version of the upstream project identified by the public version identifier, but contains additional changes (such as bug fixes). As the Python Package Index is intended solely for indexing and hosting upstream projects, it MUST NOT allow the use of local version identifiers.

I would also be ok with just the public version.

ok after reading this:

While they may be useful for continuous integration purposes, publishing developmental releases of pre-releases to general purpose public index servers is strongly discouraged, as it makes the version identifier difficult to parse for human readers. If such a release needs to be published, it is substantially clearer to instead create a new pre-release by incrementing the numeric component.

Developmental releases of post-releases are also strongly discouraged, but they may be appropriate for projects which use the post-release notation for full maintenance releases which may include code changes.

I think dev<pr> is much better. We can merge here (I guess).

Does the name work for you @MyPyDavid? Then I would merge the PR after your approval.


"Proof of Twitter" unavailable

Wrong URL of "Proof of Twitter" links (here and in pm repos) or twit was removed by the author.

d.o.n.e.

i did close it, without mentioning why.
the twit-handle changed therefor-
is a new "Proof of Twitter" needed for any purpose?

double
https://github.com/goerli/testnet/issues/70


Merge RadioTunes and JazzRadio into one connector

There is no reason to keep multiple connectors for identical websites.

Makes sense :+1:

I found no information about owners of these websites.


refactor(transformer): move parsing pragmas into TS transform

#6138
#6137  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite


Missing file, static path

Hi there, first off, nice demo and code.
But in the preprocess_kaggle_data.py file your loading in vocab.txt and this is not on kaggle nor in your repository.

nvm wasn't looking

My bad - thanks for pointing this out.
This should fix it: https://github.com/altosaar/food2vec/commit/971f560cf3739ef454105fa10ebdf69d130c4877


feat: Leverage Helidon shut down hooks so that the Block Node shuts down in a clean state

AS A BN Developer
I WANT TO Add shut down hooks to Helidon
SO THAT the Block Node server exits cleanly and leaves the Blocks in a completed state.

I did some investigation into this. With the OOTB shut down hooks provided with Helidon and grpc.io we were not able to override the necessary methods. With the PBJ Helidon plugin, we may be able to override these hooks in the future once that integration work is complete

@mattp-swirldslabs  is this issue fixed by this recently merged PR?
https://github.com/hashgraph/hedera-block-node/pull/362

No, this issue is not related to #362


feat: add ratingComment & otherLinks

As discussed in slack

Sorry for the force-push, but the typo was stupid and since it's just a feature branch that noone has had the chance to pull yet, I figured it's nicer to the history (I know I could also have squashed the PR, but it would also just make this review weirder that it'd have to be ^^)


Why are elements alphabetized on key while iterating?

Let's say I have the json from the example readme:
  nlohmann::json all = {
  {"pi", 3.141},
  {"happy", true},
  {"name", "Niels"},
  {"nothing", nullptr},
  {"answer", {
    {"everything", 42}
  }},
  {"list", {1, 0, 2}},
  {"object", {
    {"currency", "USD"},
    {"value", 42.99}
  }}
};

I will iterate over it the following way:
  for (nlohmann::json::iterator it = all.begin(); it != all.end(); ++it) {
    std::cout << it.key() << std::endl;
  }

I would expect this:
pi
happy
name
nothing
answer
list
object

Instead, I get:
answer
happy
list
name
nothing
object
pi

Why is this the default?  Can it be turned off?

They are ordered by key, because they are internally stored in a container of type std::map<std::string, nlohmann::json> which by default uses std::less<std::string> as order. This default can be overridden by setting a different template parameter ObjectType. To be able to compile the code, this type has to conform to the AssociativeContainer concept.
I know there may be situations where it would be convenient to rely on a certain order of JSON object's elements, it would at the same time be non-compliant, because JSON defines objects as unordered list of values.


cannot drag columns

Describe the bug

I can drag columns in previous versions, but not now.
I'm not sure if you have this problem

Desktop (please complete the following information):

OS: win10
Version obsidian 0.15.9

Additional context
looking forward to your reply, thanks.

Hi @wuzhen97
Its disabled by default until fix https://github.com/RafaelGB/obsidian-db-folder/issues/239
You can enable it on the global settings > developer section


[TVMC] Separate model loading from model compilation in TVMC.

This PR moves the load component from compile_module to drive_compile to make it cleaner for python scripting. It prevents "double dipping" the load in frontends more than once.
The flow is now

mod, params = tvmc.load("whatever") #from frontends.py
lib, etc = tvmc.compile(mod, params) #from compiler.py

See PR #7698 for import details.
TVMC behavior from command line won't change, as this only effects compile_module directly from python.

@comaniac @mdw-octoml @leandron @jwfromm

I'm fine with this change. Leave on others.

Thanks @CircleSpin, @comaniac, and @leandron. This is now merged.


Donate Form PayPal Link on Mobile

On /donate/#gf_3 in small mobile browsers the PayPal link overlaps the "Submit" button due to their respective positions:

I've changed this on live to prevent it but it doesn't look great. @ageeroms please can Affinity Bridge take a look at this?

Hi Rob, I've assigned to @altrugon. We'll follow up when we've had a chance to take a look.

Thank you!

I have replicated my previous solution on branch issue-556-paypal_link_overlap
, please QA and merge into the code if everything looks good.
I have also closed ticket 463 because it's really outdated now, the branch associated with that ticket should be deleted.

Thanks very much. @robmyers there's a fix from Alberto, which should be applied.

Tested, merged and deployed. It will show up soon.
Thank you!


Broken in latest

JMX is connecting, but the metrics are not spitting any output. Switching back to 0.3.1 resolves this issue. There's no log output to stdout, so I can't give much more info here.

I dunno, this works in some environments but not others, I'll keep investigating.


Trillium install error, mkdir /share/trillium access denied

I just started with a fresh HAOS setup. When starting the Trillium addon, the following error is logged:
No USER_UID specified, leaving 1000
No USER_GID specified, leaving 1000
node:internal/fs/utils:347
    throw err;
    ^
Error: EACCES: permission denied, mkdir '/share/trillium'
    at Object.mkdirSync (node:fs:1382:3)
    at getTriliumDataDir (/usr/src/app/src/services/data_dir.js:41:16)
    at Object.<anonymous> (/usr/src/app/src/services/data_dir.js:62:26)
    at Module._compile (node:internal/modules/cjs/loader:1191:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1245:10)
    at Module.load (node:internal/modules/cjs/loader:1069:32)
    at Function.Module._load (node:internal/modules/cjs/loader:904:12)
    at Module.require (node:internal/modules/cjs/loader:1093:19)
    at require (node:internal/modules/cjs/helpers:108:18)
    at Object.<anonymous> (/usr/src/app/src/services/log.js:4:17) {
  errno: -13,
  syscall: 'mkdir',
  code: 'EACCES',
  path: '/share/trillium'
}

Thank you for creating these addons.

That is why the documentation says to make the directory yourself. Did that not work?
https://github.com/jdeath/homeassistant-addons/tree/main/trillium#installation

I did create the folder, but the error remained.
Probably the issue has got something to do with the uid. I will retry soon.

I had to "chmod 2777 /share/trillium" to get it to work.

2777 or 777? I added to documentation.
Perhaps in the future, I will convert it to use the new addons_config/ directory instead of share.

I tried 777 first, but it didn't work. 2777 did the trick.


Add files via upload

Update to 3D STEP file to include 5-way switch and a rough design of the 2.9inch e-paper according to Waveshare's datasheet on the module.

Please can SQFMI review the STEP file and confirm the 5-way switch and e-paper module are sufficient to merge into master?

Amazing! Thanks @chunkysteveo 😃


Not consistent C++ code highlighting

VSCode Version:
Version 1.5.2
Commit 66f37fd2a99eb9d628dd374d81d78835b410c39b
Date 2016-09-12T13:22:54.636Z
Shell 0.37.6
Renderer 49.0.2623.75
Node 5.10.0
OS Version:
4.4.0-38-generic #57~14.04.1-Ubuntu SMP Tue Sep 6 17:20:43 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Steps to Reproduce:
See the slightly different code highlighting for the 2 identical code blocks:
1.

Reading your description it seems that the issue originates from an extension and not VS Code itself. Thereby I will close this issue and kindly ask you to report this issue against the extension repository.
Most extensions are on GitHub as well so it should be easy to file it against the extension. If you open an extension on the market place, click on the Support link to find out more.

Thanks again for your feedback!

You are correct, it is Microsoft C/C++ extension from Microsoft. I will open an issue there.
Thanks,
Pedro


Syntax Error: Unexpected token

I have the following issue: creation of nameofmycoin errored: Error encoding arguments: SyntaxError: Unexpected token ' in JSON at position 11. Is there a way to fix it?

I get this error in remix when I wrap variable in '' instead of "". I'm guessing it's similar to that.


Explicit converters for Arrays

convert() method for recursive conversion of array objects. Example:
obj = ...        # JObject, storing reference to byte[][]
arr = convert(Array{Array{jbyte, 1}, 1}, obj)  # Julia's Array{Array{jbyte, 1}, 1} with the same data

See this comment for one of the possible use cases for this converter.

This looks OK. I'd like to think this over a little bit, particularly in relation to #13 . I'll merge in a day or two.

Could you also add some tests please?

Added some tests.

This looks OK. I'd like to think this over a little bit, particularly in relation to #13 . I'll merge in a day or two.

Don't hurry up - these conversions aren't easy to design well, so better to think more now and break less in the future.

Have you come to any decisions regarding such conversions? Now when I'm back to Sparta.jl, it becomes a kind of blocker for me, so some sort of vision would be very helpful.

I think the changes in this PR are required, irrespective of what we do about #13

Hmm, did you meant to merge it instead of closing?

Duh.. That button!
This needs rebasing... Will get to it once I'm back at a computer.

No problem, I've rebased it onto latest master. I see tests for Julia 0.5 are failing, but I guess it's not a problem at the moment.

Just a kindly reminder about this PR :)

Thanks for the reminder... I've been on the road constantly.


Create Message Monitoring research plan

Context
ReportStream is investigating what information is desired and necessary, from and external usage perspective. Research must be done in order to identify the use cases, data types, methods, and frequency of which our external users would like to gain and use information. This research plan aims to document the specifics of how we're going to conduct research (primary and secondary) and be the repository for notes and findings from individual sources.
Links

Research plan document

Acceptance Criteria

[x] Outline questions specific to each audience and method of asking
[x] Outline structure for note-taking/ capturing re-mined content
[ ] Gain approval from design lead

reviewed, looks good to me! approved @jsutantio


OSX version - zsh: segmentation fault

Beside that the Windows and Ubuntu Version produces black frames.
OSX Version quits with zsh: segmentation fault
After nihui did such a good job in the older versions.
nihui/cain-ncnn-vulkan. seems to be broken : (

un a system with 2 gpu and linux this cain version works.
so I think it is just a problem with GPU IDs

Same for me

you need to jump into the same directory when you call it at commend line:
cd {App folder}


Update to the upcoming WITs

Update the WITs to follow the upcoming package format. This will not be able to land until https://github.com/bytecodealliance/wit-bindgen/pull/580 and https://github.com/bytecodealliance/wasmtime/pull/6390 land and possible a new version for wit-bindgen and wasmtime.
I used the package name spin:reactor for the entire WIT package. Happy to change it

I'm not sure what the package name should be. My first impression was fermyon/spin (much like the GitHub repo). Reactor feels much more like a world name rather than a package name.

My first impression was fermyon/spin (much like the GitHub repo). Reactor feels much more like a world name rather than a package name.

Sounds good. Changed it to fermyon:spin

I believe the upcoming June wasmtime-10 release will include the new WIT syntax changes.

Going to close this in favor of #1594. Thanks!


Release/v4.4 about camera and the SDcard

How to use esp32S3 camera example to save pictures for computer to SD card recognition

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.3 out of 21 committers have signed the CLA.:white_check_mark: dobairoland:white_check_mark: suda-morris:white_check_mark: sio13:x: L-KAYA:x: ESP-YJM:x: freakyxue:x: mahavirj:x: Charlotudy:x: igrr:x: jack0c:x: JiaLWang:x: Isl2017:x: skywxFang:x: ESP-Marius:x: xiongweichao:x: wmy-espressif:x: kostaond:x: krzychb:x: alisitsyn:x: Icarus113:x: KonstantinKondrashovYou have signed the CLA already but the status is still pending? Let us recheck it.

@13149036365 Thanks for your contribution, checked you raised one issue https://github.com/espressif/esp-idf/issues/8585, please help provide more details there, will close this PR and let us check in https://github.com/espressif/esp-idf/issues/8585. Thanks.


Change space creator_id to owner_id

There has been confusion about permissions for spaces deriving from the use of 'creator_id' and a comment was made that owner_id would be a better label and more consistent, we could add an 'author' miniUser to capture the original creator as well but allow ownership transfer of a space eventually as well.

see also: Dataset and the distinction between author (MiniUser) and creators. The dataset might be attributable to multiple creators.
Authors (This is creator in the research sense, not the computing sense.)
vs.
Original Uploader (Clowder user)
vs.
Owner/Admin who currently manages the dataset and controls access


Does Flight support namespaced controller?

Im using Flight because it looks simple & easy to use. But then i need to use namespaced controller. Is this possible with Flight? Also, Flight use statical method of controller. Is it possible to use class with non-statical method?
Thanks :)
Javas

@javasworks simple solution:
Flight::route('login', [new Namespace\AuthController(), 'index']);

Why don't you support this way @mikecao
Flight::route('/aaa', ['\\my\\aaa','bbb']);

and this way
Flight::route('/bbb', '\\my\\aaa::bbb');

    $str = '\\my\\aaa';
    $obj = new $str;
    $obj->bbb(); // It's work.

$str = '\\my\\aaa::bbb';
call_user_func_array($str, []); // It's work too.

Fixed in commit ec24d786026de89bc4852d6f33de6b42fb0a5b98.


documentation link correcting to S

adding  for better documentation

This doesn't look correct

Okay. I was trying to link up the entire word in the documentation


Dashing support

This PR brings the current feature set of ros2_dotnet forward to be compatible with ROS2 dashing.
High level Changes:

Updated a couple RCL API updates
Rebased all UWP-specific fixes in other repos onto their dashing versions
The IDL/message generation system changed significantly in Dashing. Ported ros2_dotnet to use the new system, using rosidl_generator_python and rosidl_generator_cpp as models for best practices.

This change intentionally avoids adding any new functionality to ros2_dotnet as part of this update. Notably there is still no support for actions/services, nested types, sequence types, etc. There is also not full support for Unicode strings (new in Dashing as far as I can tell) nor BoundedString constant values.

Note for @esteve  -- this branch is based on top of my Crystal PR. Once Crystal goes through, I'll rebase this (if necessary) and mark it ready for review.

@theseankelly thanks! What do you think of skipping Crystal and going straight to Dashing? Would that make sense?

@esteve same difference for me, and makes sense from a support perspective. Either way I did the work incrementally so there's always the option to branch or tag the crystal commit later on. I'll mark this commit ready for review then.

I'm encountering an issue during testing today. Not sure what's different today, but to be safe I'm closing this PR until I've gotten to the bottom of it.

All clear -- it was a network issue on my end. Original changes stand.

FYI I'm working on getting the custom UWP changes in the various ros2 repos integrated into master & backported to dashing.
rcutils is complete, so I've updated the repos file. No need for the custom dashing-windows branch any longer.

Hey @esteve -- have you had a chance to look at this? I don't want to rush the code review, but I do hope to keep iterating on top of dashing and would rather not overload this PR. Perhaps you could create a dashing branch containing this PR for future PRs to target?

@theseankelly sorry for the slow response, and thanks for the patience

@esteve no worries, thanks for taking a look!


Create a Basic Bash Script for System Monitoring by Akitha Wijesinghe

Introduces system_monitor.sh to capture and log CPU, memory, and disk usage stats. Includes detailed setup instructions in the README.md.

Hi,
Thank you for your fantastic contribution to the Codeku Cloud and DevOps micro tasks! We truly appreciate your effort. However, we regret to inform you that this particular task cannot be approved due to a few errors. But don’t worry—this is just the beginning! There will be plenty of opportunities in the future, and we’re confident that you’ll succeed next time.
We encourage you to keep trying, and we wish you the very best of luck!
Warm regards,
Team CoDeKu


Node will be discovered twice if two NICs are connected to control network

When I test with a node connected 2 NICs to control network, I found the same nodes can be discovered twice. This should not be a correct behavior. A better solution is that after first discovery of compute node, we should mark all the other NICs and avoid a second discovery.

@pengz1 this should be happening when we parse the lshw catalog. It's possible this is a bug introduced with some refactoring made to the catalog processing job (https://github.com/RackHD/on-tasks/blob/master/lib/jobs/linux-catalog.js#L94, https://github.com/RackHD/on-tasks/blob/master/lib/utils/job-utils/command-parser.js#L547). It's also possible we have a parsing error with the lshw catalog, as has happened before when we introduced new SKUs. What machine are you testing this on?
CC @VulpesArtificem

@benbp , I found this issue on Dell C6320.


Add restore for CC databases / tables

Closes #8483.

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/2c894d55364e2470b00749f6e1814c47e3287750/
Edited pages:

cockroachcloud/backups-page.md
cockroachcloud/console-access-management.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/2c894d55364e2470b00749f6e1814c47e3287750/
Edited pages:

cockroachcloud/backups-page.md
cockroachcloud/console-access-management.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/00d6baa031841db6f2810cdb037e16c19ebda13e/
Edited pages:

cockroachcloud/backups-page.md
cockroachcloud/console-access-management.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/00d6baa031841db6f2810cdb037e16c19ebda13e/
Edited pages:

cockroachcloud/backups-page.md
cockroachcloud/console-access-management.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/781e2edc8dd870f953dcdda1f79aa9c008beb2b5/
Edited pages:

cockroachcloud/backups-page.md
cockroachcloud/console-access-management.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/781e2edc8dd870f953dcdda1f79aa9c008beb2b5/
Edited pages:

cockroachcloud/backups-page.md
cockroachcloud/console-access-management.md

@mwang1026 moving this to docs review but please feel free to take another look

@mwang1026 moving this to docs review but please feel free to take another look

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/b2b41e703dca7569c0dc8f99fafbd5e73eac2a5a/
Edited pages:

cockroachcloud/backups-page.md
cockroachcloud/console-access-management.md
v20.2/restore.md
v21.1/restore.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/b2b41e703dca7569c0dc8f99fafbd5e73eac2a5a/
Edited pages:

cockroachcloud/backups-page.md
cockroachcloud/console-access-management.md
v20.2/restore.md
v21.1/restore.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/78be76af0fd4d10f1e75f3d828a4d1f13636c510/
Edited pages:

cockroachcloud/backups-page.md
cockroachcloud/console-access-management.md
v20.2/restore.md
v21.1/restore.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/78be76af0fd4d10f1e75f3d828a4d1f13636c510/
Edited pages:

cockroachcloud/backups-page.md
cockroachcloud/console-access-management.md
v20.2/restore.md
v21.1/restore.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/feedde0fb6e528675d554827bc60935b33b1a839/
Edited pages:

cockroachcloud/backups-page.md
cockroachcloud/console-access-management.md
v20.2/restore.md
v21.1/restore.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/feedde0fb6e528675d554827bc60935b33b1a839/
Edited pages:

cockroachcloud/backups-page.md
cockroachcloud/console-access-management.md
v20.2/restore.md
v21.1/restore.md


Update the  README.md file to describe the  repo.

Added default read.me

Wondering if you missed pushing all you changes or was this a test PR?


Justified nav and sticky footer examples are broken

See http://v4-alpha.getbootstrap.com/examples/justified-nav/ and http://v4-alpha.getbootstrap.com/examples/sticky-footer-navbar/.
Source: https://news.ycombinator.com/item?id=10086756

Ah, here it is! And I pinged @mdo this morning on Slack.

Footers are fixed, justified is a dupe of #17723.


Latest operation always gets undone when right clicking to fly, even if confirmed via unselecting it.

https://github.com/blackears/cyclopsLevelBuilder/assets/23440295/2cf9c5b7-07b2-43e2-9109-9fb957d3a551
This is really unintuitive because when I move a block I immediately want to start flying around to see if I like this placement.

A fix for this has been checked into the latest development branch.

Thanks king!


runtime: "unexpected signal during runtime execution" during bgscavenge on plan9-386-0intro

From plan9-386-0intro (https://build.golang.org/log/a94f5d80b1a5d38ecdf8b02bed7bfb305f569118), a cmd/vet test failure that appears to have nothing to do with cmd/vet:
--- FAIL: TestVet (1.94s)
    --- FAIL: TestVet/assign (0.43s)
        vet_test.go:162: error check failed:
            assign.go:18: missing error "self-assignment of x to x"
            assign.go:20: missing error "self-assignment of s.x to s.x"
            assign.go:22: missing error "self-assignment of s.l.0. to s.l.0."
            Unmatched Errors:
            fatal error: unexpected signal during runtime execution
            [signal sys: trap: fault write code=0x0 addr=0x0 pc=0xa960]
            goroutine 4 [running]:
            runtime.throw(0x96394d, 0x2a)
            	/tmp/workdir-gnot/go/src/runtime/panic.go:1106 +0x63 fp=0x11429f44 sp=0x11429f30 pc=0x2e783
            runtime.sigpanic()
            	/tmp/workdir-gnot/go/src/runtime/os_plan9.go:79 +0x333 fp=0x11429f78 sp=0x11429f44 pc=0x2b033
            runtime.newobject(0x92d1a0, 0x0)
            	/tmp/workdir-gnot/go/src/runtime/malloc.go:1153 fp=0x11429f7c sp=0x11429f78 pc=0xa960
            runtime.bgscavenge(0x1143c000)
            	/tmp/workdir-gnot/go/src/runtime/mgcscavenge.go:211 +0x5b fp=0x11429fe8 sp=0x11429f7c pc=0x1d83b
            runtime.goexit()
            	/tmp/workdir-gnot/go/src/runtime/asm_386.s:1337 +0x1 fp=0x11429fec sp=0x11429fe8 pc=0x573f1
            created by runtime.gcenable
            	/tmp/workdir-gnot/go/src/runtime/mgc.go:215 +0x6a
            goroutine 1 [chan receive, locked to thread]:
            runtime.gopark(0x96ee48, 0x1143c030, 0x1143170e, 0x2)
            	/tmp/workdir-gnot/go/src/runtime/proc.go:304 +0xd8
            runtime.chanrecv(0x1143c000, 0x0, 0x11400001, 0x1515a)
            	/tmp/workdir-gnot/go/src/runtime/chan.go:563 +0x275
            runtime.chanrecv1(0x1143c000, 0x0)
            	/tmp/workdir-gnot/go/src/runtime/chan.go:433 +0x1c
            runtime.gcenable()
            	/tmp/workdir-gnot/go/src/runtime/mgc.go:216 +0x7e
            runtime.main()
            	/tmp/workdir-gnot/go/src/runtime/proc.go:166 +0x183
            runtime.goexit()
            	/tmp/workdir-gnot/go/src/runtime/asm_386.s:1337 +0x1
FAIL
FAIL	cmd/vet	34.760s

CC @aclements @mknyszek @0intro @fhs

This is very odd. It's failing very, very early in the runtime (right when the background scavenger is spinning up) trying to allocate a timer. And the problem seems to be that newobject has a nil type parameter? I'm not even sure how that can happen.

The type parameter passed to newobject is 0x92d1a0.  The 0x0 is the result parameter.  The addr=0x0 printed at the start of the backtrace is meaningless, as this is not a fault signal, it is a trap signal.  The trap signal does not set the address field (sigcode1) on Plan 9.
But that said I have no idea why the binary would get a trap signal.  I don't know enough about Plan 9 to know what might cause that.  If this happened only once I'm inclined to ignore it.


feat: Add checkbox to enable/disable scroll sync on markdown editor

This PR adds an experimental feature to be able to scroll the Markdown editor and the Markdown preview containers independently, and adding the functionality to synchronize the scroll position from the editor to the preview based on the position of the Markdown component.

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