[Docs] Integration with ThirdEye:  generate and load sample data script doesn't work

https://docs.pinot.apache.org/integrations/thirdeye#prepare-your-data-optional
Creating segment for complexWebsite in /tmp/pinotGenerator/complexWebsiteSegment
Error: "-tableName" is not a valid option

I've made some changes to bin/generator.sh file and it was executed successfully, but I'm not sure about the final result.
echo "Creating segment for ${TEMPLATE_NAME} in ${SEGMENT_DIR}"
${ADMIN_PATH} CreateSegment \
-format csv \
-tableConfigFile "${TEMPLATE_BASEDIR}/${TEMPLATE_NAME}_config.json" \
-schemaFile "${TEMPLATE_BASEDIR}/${TEMPLATE_NAME}_schema.json" \
-dataDir "${DATA_DIR}" \
-outDir "${SEGMENT_DIR}" || exit 1

Thanks, Oleg. Looks like I missed a change in the CreateSegment command params. Your fix is correct. PR here: #5415


hg-crecord: switch to same revision, but fetched properly using fetchhg

I was previously just fetching the bitbucket-generated tarball of this revision, but
this was vulnerable to breakage when bitbucket made micro-changes to the tarball
generation, causing the file hash to change. This should make mercurial-full buildable
again.

fetchFromBitbucket could also be used, it fixes the tarballs so the hash shouldn't change.

@jgillich is this preferred over fetchhg?

@risicle fetchhg will uselessly download the complete history of the project and then just use the specified revision. This isn't necessary as there are tarballs available. fetchFromBitbucket should do the hash on the actual content of the files using fetchzip.

Yes of course - fixed now.

Thanks for the quick fix! Travis is also green, so let's merge this. :beers:

@fpletz Hmm - did you merge the wrong changeset in? the version that went in seems to have been the fetchhg one

Don't worry about this - it looks like I screwed up anyway and the hg-crecord package can possibly be removed entirely...


Increase branch coverage

Master build is failin since branch coverage is wanting, this Tries to fix that.
closes #92

Decided to revert on the decision to remove onadata oauth, i think there would need for a team discussion if its something that should still remain in the codebase even though IMO its not currently used.


v1-bump/1.160.0

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 61d483184f041006d99b7fed665c7a65a4d9011e
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: a211c3e9a4d55074adab1dfd0147e2241af6b280
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


[BUG] This statement is always true!

https://github.com/kevthehermit/RATDecoders/blob/39c28645c35c03aa3f12ccd60158b98668d004a3/StandAlone/NanoCore.py#L180
Probably should be if str(entry.name) == "RC_DATA" or str(entry.name) == "RCData":

Yeah, nice find. Indeed, this is not how the "or" operator works in Python (or in any programming language to be honest), this is interpreted as (str(entry.name) == "RC_DATA") or ("RCData") (due to the operator precedence rules). :smile:
I have submitted a merge request to fix this.

Thanks, I actually found some time this week to work on converting this to a library with python3 compatibility. Have fixed this in that branch. - https://github.com/kevthehermit/RATDecoders/tree/library


Ability to fetch “the latest” set of experiments

Following up with the discussions in https://github.com/openrlbenchmark/openrlbenchmark/pull/13#issuecomment-1538160595, this issue seeks to discuss ways we can fetch "the latest" set of experiments for plotting.
Currently, we can log experiments with wandb tags, which can help us filter experiments. However, different tags might be applied to different experiments. For example, our ppo_atari.py might be tagged with v1.0.0 while dqn_atari.py might be tagged with v1.0.1-pr-203. There is no automatic way to get the latest tags which are v1.0.0 and v1.0.1-pr-203.

I think one possible solution is to add an openrlbenchmark.yaml configuration file to the code repositories that natively support openrlbenchmark (e.g. cleanrl). This file can store the latest tag information or the order of the tags, guiding our code to select the latest experiments. This way, new tag information only needs to be added in the configuration file of each branch that runs new experiments, and running experiments in a new branch before it is merged won't affect the openrlbenchmark results. We might also be able to use GitHub Actions to automatically modify the openrlbenchmark.yaml configuration file.
For code repositories that don't natively support openrlbenchmark, we can still manually add the latest tag.


Investigate: Puma Rack tests failing on 3.2.0-preview2

On the new 3.2.0-preview2 version, all rack test suites involving puma are failing with the following errors:
  1) Error:
RackAutoInstrumentationTest#test_middlewares_record_metrics:
ArgumentError: wrong number of arguments (given 2, expected 1; required keyword: tag)
    /home/runner/work/newrelic-ruby-agent/newrelic-ruby-agent/test/multiverse/suites/rack/example_app.rb:84:in `initialize'
    /home/runner/work/newrelic-ruby-agent/newrelic-ruby-agent/lib/new_relic/agent/instrumentation/middleware_proxy.rb:32:in `new'
    /home/runner/work/newrelic-ruby-agent/newrelic-ruby-agent/lib/new_relic/agent/instrumentation/middleware_proxy.rb:32:in `new'
    /opt/hostedtoolcache/Ruby/3.2.0-preview2/x64/lib/ruby/gems/3.2.0+2/gems/rack-1.6.13/lib/rack/builder.rb:86:in `block in use'
    /opt/hostedtoolcache/Ruby/3.2.0-preview2/x64/lib/ruby/gems/3.2.0+2/gems/rack-1.6.13/lib/rack/builder.rb:147:in `block in to_app'
    /opt/hostedtoolcache/Ruby/3.2.0-preview2/x64/lib/ruby/gems/3.2.0+2/gems/rack-1.6.13/lib/rack/builder.rb:147:in `each'
    /opt/hostedtoolcache/Ruby/3.2.0-preview2/x64/lib/ruby/gems/3.2.0+2/gems/rack-1.6.13/lib/rack/builder.rb:147:in `inject'
    /opt/hostedtoolcache/Ruby/3.2.0-preview2/x64/lib/ruby/gems/3.2.0+2/gems/rack-1.6.13/lib/rack/builder.rb:147:in `to_app'
    /home/runner/work/newrelic-ruby-agent/newrelic-ruby-agent/lib/new_relic/agent/instrumentation/rack/prepend.rb:24:in `block in to_app'
    /home/runner/work/newrelic-ruby-agent/newrelic-ruby-agent/lib/new_relic/agent/instrumentation/rack/instrumentation.rb:44:in `with_deferred_dependency_detection'
    /home/runner/work/newrelic-ruby-agent/newrelic-ruby-agent/lib/new_relic/agent/instrumentation/rack/prepend.rb:24:in `to_app'
    /opt/hostedtoolcache/Ruby/3.2.0-preview2/x64/lib/ruby/gems/3.2.0+2/gems/rack-1.6.13/lib/rack/builder.rb:59:in `app'
    /home/runner/work/newrelic-ruby-agent/newrelic-ruby-agent/test/multiverse/suites/rack/rack_auto_instrumentation_test.rb:28:in `app'
    /opt/hostedtoolcache/Ruby/3.2.0-preview2/x64/lib/ruby/gems/3.2.0+2/gems/rack-test-2.0.2/lib/rack/test/methods.rb:45:in `build_rack_test_session'
    /opt/hostedtoolcache/Ruby/3.2.0-preview2/x64/lib/ruby/gems/3.2.0+2/gems/rack-test-2.0.2/lib/rack/test/methods.rb:33:in `rack_test_session'
    /opt/hostedtoolcache/Ruby/3.2.0-preview2/x64/lib/ruby/gems/3.2.0+2/gems/rack-test-2.0.2/lib/rack/test/methods.rb:52:in `current_session'
    /opt/hostedtoolcache/Ruby/3.2.0-preview2/x64/lib/ruby/3.2.0+2/forwardable.rb:234:in `get'
    /home/runner/work/newrelic-ruby-agent/newrelic-ruby-agent/test/multiverse/suites/rack/rack_auto_instrumentation_test.rb:91:in `test_middlewares_record_metrics'

  2) Error:
RackAutoInstrumentationTest#test_body_is_preserved:
ArgumentError: wrong number of arguments (given 2, expected 1; required keyword: tag)
....

  3) Error:
RackAutoInstrumentationTest#test_non_agent_middlewares_do_not_record_metrics_if_disabled_by_config:
ArgumentError: wrong number of arguments (given 2, expected 1; required keyword: tag)
....

  4) Error:
RackAutoInstrumentationTest#test_middlewares_record_queue_time:
ArgumentError: wrong number of arguments (given 2, expected 1; required keyword: tag)
...

  5) Error:
RackAutoInstrumentationTest#test_middleware_gets_used:
ArgumentError: wrong number of arguments (given 2, expected 1; required keyword: tag)
....

  6) Error:
RackAutoInstrumentationTest#test_header_is_preserved:
ArgumentError: wrong number of arguments (given 2, expected 1; required keyword: tag)
....

  7) Error:
RackAutoInstrumentationTest#test_middleware_that_returns_early_records_middleware_rollup_metric:
ArgumentError: wrong number of arguments (given 2, expected 1; required keyword: tag)
....

  8) Error:
RackAutoInstrumentationTest#test_middleware_created_with_args_works:
ArgumentError: wrong number of arguments (given 2, expected 1; required keyword: tag)
....

  9) Error:
RackAutoInstrumentationTest#test_status_code_is_preserved:
ArgumentError: wrong number of arguments (given 2, expected 1; required keyword: tag)
...

 10) Error:
RackAutoInstrumentationTest#test_middleware_that_returns_early_middleware_all_has_correct_call_times:
ArgumentError: wrong number of arguments (given 2, expected 1; required keyword: tag)
...

 11) Error:
RackAutoInstrumentationTest#test_middleware_created_with_kwargs_works:
ArgumentError: wrong number of arguments (given 2, expected 1; required keyword: tag)
....

3.2 went stable a few months after this issue was created and we've been sailing smoothly with it being used for our Puma CI tests for quite awhile now. Closing as resolved.
There is another issue this year with the 3.3 preview release. That issue was traced to Puma's fork of Rack, which we have addressed with a PR (merged now) submitted to the Puma repo.
For 3.3, we're now simply waiting on a new Puma release to re-enable 3.3 based tests. That waiting is being tracked with https://github.com/newrelic/newrelic-ruby-agent/issues/2042


pohka

I'd like to have my profile on ghuser.io, thanks!

here you go :) https://ghuser.io/pohka
In case you're wondering why it is empty, this is because we don't display repos without stars, because we think that if you don't star your own project, that means you're not proud of it (yet).  See #22


Add tests for incorrect tax calculations in JPY

I want to merge this change because adding tests for incorrect tax calculations in JPY

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-5444 Invalid price calculation for orders in JPY.


Retain offset in BoundingBox::contract and expand

This is a breaking change to those methods but I expected those to behave like this so much that I think it's a bug.

This is a really 'sneaky' breaking change and would be frustrating to debug. I think there should simply be some new methods added to work this way and javadocs added explaining the difference rather than breaking here.


Change "Override Execution Context" button to "Record" button on nodes

Pull Request Description

Close #9164

Fix appearance of Record/Record Once icon in top menu
Change icon for overriding execution context to record icon
Unconditionally show per-node record icon if it is set
Remove the ability to override the execution context to disabled
Fix the icon for nodes with an overridden execution context always being the Enso icon

Important Notes
None
Screenshot

Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[x] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

@farmaazon you mentioned you might have wanted to take a look at this

I guess it also fixes #7976?

probably, yeah. tests haven't been added in this PR though, maybe that could be split out into another task?

anyone know what's going on with the tests? https://github.com/enso-org/enso/actions/runs/8094866300/job/22120440156?pr=9188#step:8:466
  INFO ide_ci::program::command: npm⚠ ⎯⎯⎯⎯⎯⎯ Failed Suites 8 ⎯⎯⎯⎯⎯⎯⎯
 INFO ide_ci::program::command: npmℹ
 INFO ide_ci::program::command: npm⚠
 INFO ide_ci::program::command: npm⚠  FAIL  src/composables/__tests__/selection.test.ts [ src/composables/__tests__/selection.test.ts ]
 INFO ide_ci::program::command: npm⚠  FAIL  src/providers/__tests__/widgetRegistry.test.ts [ src/providers/__tests__/widgetRegistry.test.ts ]
 INFO ide_ci::program::command: npm⚠  FAIL  src/components/ComponentBrowser/__tests__/input.test.ts [ src/components/ComponentBrowser/__tests__/input.test.ts ]
 INFO ide_ci::program::command: npm⚠  FAIL  src/components/GraphEditor/__tests__/dragging.test.ts [ src/components/GraphEditor/__tests__/dragging.test.ts ]
 INFO ide_ci::program::command: npm⚠  FAIL  src/stores/graph/__tests__/graphDatabase.test.ts [ src/stores/graph/__tests__/graphDatabase.test.ts ]
 INFO ide_ci::program::command: npm⚠  FAIL  src/composables/selection.ts [ src/composables/selection.ts ]
 INFO ide_ci::program::command: npm⚠  FAIL  src/components/GraphEditor/collapsing.ts [ src/components/GraphEditor/collapsing.ts ]
 INFO ide_ci::program::command: npm⚠  FAIL  src/util/ast/node.ts [ src/util/ast/node.ts ]
 INFO ide_ci::program::command: npm⚠ TypeError: Cannot read properties of undefined (reading '__wbindgen_add_to_stack_pointer')
 INFO ide_ci::program::command: npm⚠  ❯ Module.parse rust-ffi/pkg/rust_ffi.js:156:14
 INFO ide_ci::program::command: npm⚠     154|         return v2;
 INFO ide_ci::program::command: npm⚠     155|     } finally {
 INFO ide_ci::program::command: npm⚠     156|         wasm.__wbindgen_add_to_stack_pointer(16);
 INFO ide_ci::program::command: npm⚠        |              ^
 INFO ide_ci::program::command: npm⚠     157|     }
 INFO ide_ci::program::command: npm⚠     158| }
 INFO ide_ci::program::command: npm⚠  ❯ parseEnso shared/ast/parse.ts:65:16
 INFO ide_ci::program::command: npm⚠  ❯ parseBlockWithSpans shared/ast/parse.ts:541:16
 INFO ide_ci::program::command: npm���  ❯ parseBlock shared/ast/parse.ts:521:10
 INFO ide_ci::program::command: npm⚠  ❯ Module.parse shared/ast/parse.ts:527:15
 INFO ide_ci::program::command: npm⚠  ❯ new Pattern src/util/ast/match.ts:12:21
 INFO ide_ci::program::command: npm⚠  ❯ Function.parse src/util/ast/match.ts:21:12
 INFO ide_ci::program::command: npm⚠  ❯ src/util/ast/prefixes.ts:22:76
 INFO ide_ci::program::command: npm⚠  ❯ Function.FromLines src/util/ast/prefixes.ts:22:39

 GitHub**Change "Override Execution Context" button to "Record" button on nodes · enso-org/enso@3f03d53**Hybrid visual and textual functional programming. Contribute to enso-org/enso development by creating an account on GitHub.

Missing initializeFFI call in test file. Unfortunately, we need to add it in every test file using parser.

man, whatever happened here?

oh i guess i messed up the merge...

✅ QA passed

[x] Fix appearance of Record/Record Once icon in top menu
[x] Make the icons be consistent with the new icons for live/design mode in https://github.com/enso-org/enso/pull/9133

i.e. grey circle for off, red circle for on

[x] Unconditionally show per-node record icon if it is set
[x] Remove the ability to override the execution context to disabled
[x] Fix the icon for nodes with an overridden execution context always being the Enso icon


__non_webpack_require__ incompatible with experiments.outputModule + devtool: 'eval-source-map'

Bug report
What is the current behavior?
When using experiments.outputModule = true in combination with __non_webpack_require__ and devtool: 'eval-source-map' (or any other of the eval-based devtools), then you get Error: Cannot use 'import.meta' outside a module when trying to run the bundled file. This is because import.meta is accessed in the code that is passed as a string to eval, which does not have access to import.meta.
If the current behavior is a bug, please provide the steps to reproduce.
Full minimal sample project: https://stackblitz.com/edit/github-qjzdxl?file=webpack.config.cjs&view=editor
Run npm install && npm run build && npm run start to get the error.
Important files:

package.json which specifies type: "module"
webpack.config.cjs:  const path = require('path');

  module.exports = {
    entry: './src/index.js',
    devtool: 'eval-source-map',
    output: {
      filename: 'main.js',
      path: path.resolve(__dirname, 'dist'),
    },
    experiments: {
      outputModule: true,
    },
    optimization: {
      minimize: false,
    },
  };

src/index.js:  __non_webpack_require__('path');
  console.log('it worked');

What is the expected behavior?
Webpack should use a different mechanism to access import.meta when using an eval-based devtool that avoids accessing import.meta inside of strings passed to eval. Running the compiled file should print it worked to the console.
Other relevant information:
webpack version: 5.89.0
Node.js version: 18.18.0
Operating System: Linux
Additional tools: None

Yeah, not sure how we can solve it, because we need import.meta.url for https://nodejs.org/api/module.html#modulecreaterequirefilename, I want to say it is a limitation, why do not use createRequire in code?

I am unable to use createRequire, because I'd need import.meta.url for it:
Input:
const path = require('path');

module.exports = {
  entry: './src/index.js',
  devtool: 'eval-source-map',
  target: 'node18',
  externalsPresets: { node: true },
  output: {
    filename: 'main.js',
    path: path.resolve(__dirname, 'dist'),
  },
  experiments: {
    outputModule: true,
  },
  optimization: {
    minimize: false,
  },
};

import * as module from 'node:module';

const customRequire = module.createRequire(import.meta.url);
customRequire('something');

Output:
/*
 * ATTENTION: An "eval-source-map" devtool has been used.
 * This devtool is neither made for production nor for readable output files.
 * It uses "eval()" calls to create a separate source file with attached SourceMaps in the browser devtools.
 * If you are trying to read the output file, select a different devtool (https://webpack.js.org/configuration/devtool/)
 * or disable the default devtool with "devtool: false".
 * If you are looking for production-ready output files, see mode: "production" (https://webpack.js.org/configuration/mode/).
 */
import { createRequire as __WEBPACK_EXTERNAL_createRequire } from "module";
/******/ var __webpack_modules__ = ({

/***/ 590:
/***/ (() => {

eval("\n;// CONCATENATED MODULE: external \"node:module\"\nconst external_node_module_namespaceObject = __WEBPACK_EXTERNAL_createRequire(import.meta.url)(\"node:module\");\n;// CONCATENATED MODULE: ./src/index.js\n\n\nconst customRequire = external_node_module_namespaceObject.createRequire(\"file:///home/projects/github-qjzdxl/src/index.js\");\ncustomRequire('something');\n//# sourceURL=[module]\n//# sourceMappingURL=data:application/json;charset=utf-8;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiNTkwLmpzIiwibWFwcGluZ3MiOiI7O0FBQUEsTUFBTSxvQ0FBNEIsb0U7O0FDQUk7O0FBRXRDLHNCQUFzQixrREFBb0IsQ0FBQyxrREFBZTtBQUMxRCIsInNvdXJjZXMiOlsid2VicGFjazovL2dldHRpbmctc3RhcnRlZC11c2luZy1hLWNvbmZpZ3VyYXRpb24vZXh0ZXJuYWwgbm9kZS1jb21tb25qcyBcIm5vZGU6bW9kdWxlXCI/YTRiNSIsIndlYnBhY2s6Ly9nZXR0aW5nLXN0YXJ0ZWQtdXNpbmctYS1jb25maWd1cmF0aW9uLy4vc3JjL2luZGV4LmpzPzg4YjciXSwic291cmNlc0NvbnRlbnQiOlsiY29uc3QgX19XRUJQQUNLX05BTUVTUEFDRV9PQkpFQ1RfXyA9IF9fV0VCUEFDS19FWFRFUk5BTF9jcmVhdGVSZXF1aXJlKGltcG9ydC5tZXRhLnVybCkoXCJub2RlOm1vZHVsZVwiKTsiLCJpbXBvcnQgKiBhcyBtb2R1bGUgZnJvbSAnbm9kZTptb2R1bGUnO1xuXG5jb25zdCBjdXN0b21SZXF1aXJlID0gbW9kdWxlLmNyZWF0ZVJlcXVpcmUoaW1wb3J0Lm1ldGEudXJsKTtcbmN1c3RvbVJlcXVpcmUoJ3NvbWV0aGluZycpO1xuIl0sIm5hbWVzIjpbXSwic291cmNlUm9vdCI6IiJ9\n//# sourceURL=webpack-internal:///590\n");

/***/ })

/******/ });
/************************************************************************/
/******/
/******/ // startup
/******/ // Load entry module and return exports
/******/ // This entry module can't be inlined because the eval-source-map devtool is used.
/******/ var __webpack_exports__ = {};
/******/ __webpack_modules__[590]();
/******/

As you can see, this still leads to import.meta.url being used inside of eval.

I see...

bump

... that said setting devtool: false doesn't fix the import.

You can use __non_webpack_require__ for loading node.js modules for the web env...


Update npm from 7.6.1 to 7.7.4

v7.7.4 (2021-03-24)
BUG FIXES
200bee74b #2951 fix(config): accept explicit production=false (@wraithgar)
7b45e9df6 #2950 warn if using workspaces config options in npm config (@ruyadorno)
v7.7.3 (2021-03-24)
BUG FIXES
c76f04ac2 #2925 fix(set-script): add completion (@yash-singh1)
0379eab69 #2929 fix(install): ignore auditLevel (@wraithgar)
98efadeb4 #2923 fix(audit-level): add info audit level (@wraithgar)
e8d2adcf4 #2945 config should not error when workspaces are configured (@nlf)
aba2bc623 #2944 fix(progress): re-add progress bar to reify (@wraithgar)
877b4ed29 #2946 fix(flatOptions): re-add _auth (@wraithgar)
v7.7.2 (2021-03-24)
BUG FIXES
a4df2b98d #2942 Restore --dev flag, unify --omit flatteners (@isaacs)
DEPENDENCIES
2cbfaac0e<EMAIL_ADDRESS>#83 Do not parse urls for gitlab (@nlf)
v7.7.0 (2021-03-23)
FEATURES
33c4189f9 #2864 add npm run-script workspaces support (@ruyadorno)
e1b3b318f #2886 add npm exec workspaces support (@ruyadorno)
41facf643 #2859 expanded "Did you mean?" suggestions for missing cmds and scripts (@wraithgar)
BUG FIXES
8cce4282f #2865 npm publish: handle case where multiple config list is present (@kenrick95)
6598bfe86 mark deprecated configs (@isaacs)
8a38afe77 #2881 docs(package-json): document default main behavior (@klausbayrhammer)
93a061d73 #2917 add action items to npm run error output (@wraithgar)
DOCUMENTATION
ad65bd910 #2860 fix link in configuring-npm (@varmakarthik12)
b419bfb02 #2876 fix test-coverage command in contributing guide (@chowkapow)
DEPENDENCIES
7b5606b93<EMAIL_ADDRESS>#254 Honor explicit prefix when saving dependencies (@jameschensmith)
#255 Never save to bundleDependencies when saving a peer or peerOptional dependency. (@isaacs)
f76e7c21f<EMAIL_ADDRESS>increases tarball compression level
4928512bc<EMAIL_ADDRESS>fix handling prereleases/ANY ranges in subset
1924eb457<EMAIL_ADDRESS>fix removing undescored-prefixed package.json properties in npm version
916623056<EMAIL_ADDRESS>fix expanding windows-style environment variables
a8d0751e4<EMAIL_ADDRESS>fix running packages with a single executable binary with npm exec
af7eaac50<EMAIL_ADDRESS>f52c51db1<EMAIL_ADDRESS>v7.7.0 (2021-03-23)
FEATURES
33c4189f9 #2864 add npm run-script workspaces support (@ruyadorno)
e1b3b318f #2886 add npm exec workspaces support (@ruyadorno)
41facf643 #2859 expanded "Did you mean?" suggestions for missing cmds and scripts (@wraithgar)
BUG FIXES
8cce4282f #2865 npm publish: handle case where multiple config list is present (@kenrick95)
6598bfe86 mark deprecated configs (@isaacs)
8a38afe77 #2881 docs(package-json): document default main behavior (@klausbayrhammer)
93a061d73 #2917 add action items to npm run error output (@wraithgar)
DOCUMENTATION
ad65bd910 #2860 fix link in configuring-npm (@varmakarthik12)
b419bfb02 #2876 fix test-coverage command in contributing guide (@chowkapow)
DEPENDENCIES
7b5606b93<EMAIL_ADDRESS>
#254 Honor explicit prefix when saving dependencies (@jameschensmith)
#255 Never save to bundleDependencies when saving a peer or peerOptional dependency. (@isaacs)
f76e7c21f<EMAIL_ADDRESS>increases tarball compression level
4928512bc<EMAIL_ADDRESS>fix handling prereleases/ANY ranges in subset
1924eb457<EMAIL_ADDRESS>fix removing undescored-prefixed package.json properties in npm version
916623056<EMAIL_ADDRESS>fix expanding windows-style environment variables
a8d0751e4<EMAIL_ADDRESS>fix running packages with a single executable binary with npm exec
af7eaac50<EMAIL_ADDRESS>f52c51db1<EMAIL_ADDRESS>
v7.6.3 (2021-03-11)
DOCUMENTATION
8c44e999b #2855 Correct "npm COMMAND help" to "npm help COMMAND" (@dwardu)
DEPENDENCIES
57ed390d6<EMAIL_ADDRESS>Respect link deps when calculating peerDep sets
v7.6.2 (2021-03-09)
BUG FIXES
e0a3a5218 #2831 Fix cb() never called in search with --json option (@fraqe)
85a8694dd #2795 fix(npm.output): make output go through npm.output (@wraithgar)
9fe0df5b5 #2821 fix(usage): clean up usage declarations (@wraithgar)
DEPENDENCIES
7f470b5c2<EMAIL_ADDRESS>fix(install): Do not revert a file: dep to version on bare name re-install
e9b7fc275<EMAIL_ADDRESS>fix(diff): Gracefully handle packages with prepare script
c7314aa62<EMAIL_ADDRESS>864f48d43<EMAIL_ADDRESS>

I think there's a regression in npm, raised here https://github.com/npm/cli/issues/2939

Thanks for reaching out @feelepxyz. We shipped npm 7.7.1 to 7.7.4 today that should contain the appropriate fix, please let us know if you still have any problem!

@ruyadorno thanks! Looks like specs are green 🎉


chore(package.json): clear up intermidiate build artifact after build

⚠ Targeting master ⚠

[x] Non-breaking change

Description:
This PR makes force clear intermediate build artifact es6 used for internal doc / umd package building only, to no longer included in actual
Related issue (if exists):
#2177

I'm feeling bulid script might need to be simplified (and remove some of confusions if anyone read scripts).. but that's other story later.

Coverage remained the same at 97.674% when pulling 077cc2e6fa26f6a9540e317340048d533844e56a on kwonoj:fix-es6-build into dc06e017d1cf7f1336cc38a4ab81033a057a6794 on ReactiveX:master.

Updated PR corrects my error.

Seems good, but I want @blesh to confirm as well.

@jayphelps I agree.

Coverage remained the same at 97.674% when pulling 3a598841bddc503df82094fcf85fb02e27977414 on kwonoj:fix-es6-build into dc06e017d1cf7f1336cc38a4ab81033a057a6794 on ReactiveX:master.

LGTM


fix(*): main field in package.json to reference index.js correctly

Description
By adding main in the projects package.json, nx will use the proper reference in final package, while looking at src when developing.
I noticed the warning come up when I was trying various build things, so I figured I should fix this.
I also added a repository reference as seen here. I looked at a polkadot package for the format. I saw lib grading tool dock marks for not having it. Probably something we should add in other repos as well.
Breaking Changes
None
JIRA Link
DA-547
Checklist

[ ] Updated the Readme.md (if required) ?

:tada: This PR is included in version<EMAIL_ADDRESS>:tada:
The release is available on:

npm package (@latest dist-tag) :package::rocket:
GitHub release :package::rocket:

:tada: This PR is included in version<EMAIL_ADDRESS>:tada:
The release is available on:

npm package (@latest dist-tag) :package::rocket:
GitHub release :package::rocket:

:tada: This PR is included in version<EMAIL_ADDRESS>:tada:
The release is available on:

npm package (@latest dist-tag) :package::rocket:
GitHub release :package::rocket:

:tada: This PR is included in version<EMAIL_ADDRESS>:tada:
The release is available on:

npm package (@latest dist-tag) :package::rocket:
GitHub release :package::rocket:

:tada: This PR is included in version<EMAIL_ADDRESS>:tada:
The release is available on:

npm package (@latest dist-tag) :package::rocket:
GitHub release :package::rocket:


Ability To Instant Print Selected Mathches

It would be great if the user could Instant Print only the matches that they select, which would prevent having to Instant Print all the matches for that round each time.

Resolved in 7715d8a


depend just on cats-core, not on all of cats

this allows including atto in the Scala 2.12 community build

Oh, cool. Thanks!

@SethTisue do you need to build from a tag, or is this good as-is?

we don't need a tag, we're tracking the series/0.5.x branch


[devcenter] Add devcenter 2022-11-11-preview

@am-lim please update command model in this PR as well


UT failure: HistoryMetricsServiceSpec

UT HistoryMetricsServiceSpec will fail:
[info] HistoryMetricsServiceSpec:
[info] SingleValueMetricsStore
[info] - should retain metrics and expire old value *** FAILED ***
[info]   5 did not equal 3 (HistoryMetricsServiceSpec.scala:68)
[info] MinMaxMetricsStore
[info] - should retain min and max metrics data and expire old value
[info] HistogramMetricsStore
[info] - should retain corse-grain history and fine-grain recent data
[info] MeterMetricsStore
[info] - should retain corse-grain history and fine-grain recent data
[info] CounterMetricsStore
[info] - should retain corse-grain history and fine-grain recent data
[info] HistoryMetricsService
[info] - should retain lastest metrics data and allow user to query metrics by path

Not sure whether this is valid anymore. The latest CI is good.
https://travis-ci.org/intel-hadoop/gearpump/builds/70478622


Config file doesn't validate Maven versions.

Package manage/ecosystem
java:maven
What you expected to see, versus what you actually saw
When I use a correct version requirement string in Maven, I expect my comfig.yml file to be validated, however instead I get the following error (both as an issue in a repo and using the config validator online):
The property '#/update_configs/0/ignored_updates/0/version_requirement' is an invalid version requirement for a java:maven ignore condition

If I were to remove the version_requirement line from that section of the config file, it works fine. Below is an example of the ignored_updates section of a config file I'm testing.
ignored_updates:
  - match:
      dependency_name: "org.springframework:spring-core"
      version_requirement: "[4.0.0.RELEASE,)"

In this example, all updates greater than Spring 3 should be ignored.
One workaround to please the config validator is to remove the comma, but looking at the source code, I think Dependabot Core would treat that as an "equals" constraint as opposed to a "range" constraint".
I've taken a look at the requirement.rb file for the Maven part of the Dependabot core and tested the functions. The core handles version ranges as expected; it's just the config validator that is throwing issues. I tried to look at its code, but I couldn't find it. I am happy to take a look at this issue some more if someone can point me in the right direction.

@eager Thank you for your PR. Hopefully that fixes it. I have tried using the Gem format for the past couple months, but seem to get intermittent success. It could well be user error when using Gem format, but I haven't been able to fully observe if it's functioning properly.

I can confirm that even after including the following code segment in the ignored_updates section of the config.yml file, I still get dependency updates for the packages:
- match:
    dependency_name: "swagger.annotations.version"
    version_requirement: ">= 1.5.9" # Requires Java 8


Persist Job remains in JobWorker even after cancel.

Alluxio Version:
What version of Alluxio are you using? 2.2.0-SNAPSHOT, but reproducible in 2.1.1 and 2.0.x
Describe the bug
A clear and concise description of what the bug is.
PersistJob cancellation doesn't get processed properly.
To Reproduce
Steps to reproduce the behavior (as minimally and precisely as possible)
With AsyncThrough writeType

Write a large number of files as AsyncThrough
Before all of them gets persisted, rm them all.
Wait for a long time.
Run jobservice report

You will see that there are a large number of jobs still stuck under CREATED/RUNNING.
Expected behavior
A clear and concise description of what you expected to happen.
0 jobs under CREATED or RUNNING
Urgency
Describe the impact and urgency of the bug.
Additional context
Add any other context about the problem here.
There is no report in 2.0 to see the bug clearly but the bug is nonetheless still there.

@bradyoo  is this still an open issue?

It's not in 2.1. I should actually resolve it.


Is the Android App ever going to be published in Chinese App Stores?

The majority of Chinese users cannot access the Google Play store not only because it is blocked by the Great Chinese Firewall, but because many domestic phones just do not have the Google framework installed. Thus, using a VPN and installing the Google Playstore won't work.
I can install it without any hassles on my Pocophone EU edition, but when I use my Chinese Xiaomi phone I cannot find the app anywhere. I had to export the APK manually and transfer it to the Xiaomi phone.
Would it be possible to add it to the major App stores such as Xiaomi GetApps and Huawei's app store as well? There are several altermative app stores in China, I know it is a drag. But when thinking of the features, the Chinese people definitely are in need of software like yours. Besides that, it is a huge userbase.

+1 for this, but I'd prefer more general access to a raw apk file!
The Android client being a plain APK on APKMirror was the only reason I was still entertaining Keybase. Starting with 6.4.0 it 's only a bundle now, and I don't quite care to mess around with sideloading that for updates.
I use a OnePlus 6 with LineageOS 21 and no Google Apps. The few apps I can't get off F-Droid I sideload, and Keybase was one of those apps until it looks to be apk bundles-only now.

I'm not sure which Chinese App Store this is, but I sideload my watch's apk from here and wouldn't mind getting Keybase from there like that!


cache_kernel.cu does not compile using pip install -e . on source code

Neither in docker (with the suggested docker), nor on my own environment, I get to compilte the cache_kernel.cu.
NCVV = 11.8, also using the PyTorch 2.0.1 CUDA 11.8 package.
At first, it didn't install at all because of the myproject.toml pointing towards a pytorch in pip that is not cuda enabled.
After removing the toml file, I ran into these errors:
vllm\csrc\cache_kernels.cu(41): error: expression must be a pointer to a complete object type
vllm\csrc\cache_kernels.cu(42): error: expression must be a pointer to a complete object type
vllm\csrc\cache_kernels.cu(96): error: expression must have a constant value
vllm\csrc\cache_kernels.cu(96): note #2689-D: the value of variable "num_layers"
(86): here cannot be used as a constant
vllm\csrc\cache_kernels.cu(97): error: expression must have a constant value
vllm\csrc\cache_kernels.cu(97): note #2689-D: the value of variable "num_layers"
(86): here cannot be used as a constant

Hello, have you solved it?

I am having this same issue -- just trying to bump the discussion to see if a solution was arrived upon.  Getting the same num_layers "not constant value" errors described by OP.

I am having this same issue, have anyone solved it?

Closing this because the build system has changed dramatically since this was opened


Feature request: better UI to handle combinatorial explosion of variants

I'm a fan of the variants feature, but in one of my projects, its use is starting to get unwieldy, since the number of available variants suffers from combinatorial explosion.
In this project, I currently have 9 different options I'd like to control using the variants feature -- indeed,  there were additional options that I've considering adding at some point, but had to weight that against the increase in variant count, and eventually decided not to add them. While many of these options are binary choices, some have a larger number of choices, compounding the problem. Concretely, using all 9 options works out to almost 5,000 possible variants, and scrolling through them to find the desired one is quite time-consuming.
Recently I cut this down to the 5 most used options, but it still works out to almost 300 possible variants, which is easier to scroll through (but still not ideal) and forces me to run CMake manually when I need to use the other options. Sorting options from least to most commonly modified in the YAML file last helps a bit, so that often the choice is in the first few screenfuls, but is not a proper solution to the problem.
The root of the issue, in my opinion, is the UI choice of a scrollable list containing the cartesian product of all variants. I'd like to propose a different design that handles combinatorial explosion much better: when the user tries to select a variant, a dialog pops up containing combo boxes for each available option -- this works well with the current paradigm of a number of choices per option. Later, this could be extended to use check boxes for binary choice options, and even text fields for open-ended options.
I understand that, for some users, the existing UI works fine and they may dislike the proposed one. Thus, I suggest that the choice of UI should be a setting, and the existing UI might be the default choice to avoid disrupting current workflows.

PLEASE do this. The drop-down is un-usable after just a few variants are added.

This would be awesome. I find myself having the same issue described above.


AVRO-2837: DecimalConversion handling of scale and precision

Improve the handling to check precision and not error if scale
of value is less
Make sure you have checked all steps below.
Jira

[x] My PR addresses the following Avro Jira issues and references them in the PR title.

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

TestDecimalConversion file added with tests of the success and expected error states
Commits

[x] My commits all reference Jira issues in their subject lines. In addition, my commits follow the guidelines from "How to write a good git commit message":

Documentation

[x] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain Javadoc that explain what it does

Hello! Thanks for noticing these issues. Avro is definitely doing something wrong today, with precisions that don't match the logical type.
However, there's something wrong with your logic here: if the logical type is precision 5 and scale 2, it would happily accept a new BigDecimal("9123") (precision 4 and scale 0). I tried to exhaustively list the cases in AVRO-2837, and there's a decision to be made about how this should be fixed! Can you take a look?

Thanks for the feedback @RyanSkraba . I've made some updates and commented on AVRO-2837

LGTM Thanks for all the thought you put into this, and the thorough tests!
This now conflicts with master because of the last commit :/ My apologies! If you rebase this on master or remove the last commit, I can merge this!

Thanks. Just rebased onto master


rgba without leading zero

This PR fixes #205.

The rgbare RegEx accepts 0 or 1 0 character in the alpha field.
The alpha field is then normalized so it always outputs 0.##, so as far as the rest of the library is concerned, the output of parseColor remains unchanged (for example rgba(123,123,123,0.4)).

thanks for the fix @jtanadi 👍

@imsky glad to have helped. Thanks for merging!


Certify ORDS 3.0.4

http://www.oracle.com/technetwork/developer-tools/rest-data-services/downloads/ords-bugsfixed-304-2895222.html
@fuzziebrain please tag to any other ticket that ORDS 3.0.3 may have raised.

We may need a better solution if these scripts change with each release.
See #112


Fixed search results disappearing off screen

Results that don't fit within the screen width would continue off the screen, however using width instead of minWidth for the TouchableHighlight style will show an ellipsis when running out of room. This is more user friendly.

Thank you for your PR @oliveroneill!


adduser: gecos group doesn't exist

Hello , Im following
http://docs.couchdb.org/en/master/install/unix.html
When i hit this command :+1:
adduser --system
--shell /bin/bash
--group --gecos
"CouchDB Administrator" couchdb
This is the error :+1:
adduser : le groupe « --gecos » n'existe pas
in english :+1:
gecos group doesnt exist,
im bloqued please help

I cant create the couchdb user, please help, geco group doesnt exist, why did you add --geco ?

@nicolas15000 Looks like your adduser command has a different syntax.
For GNU adduser, --system --group will create a group with the same name and ID as the system user.
Which OS are you on?

On Ubuntu bionic (18.04):
root@67bec2d34961:/# adduser --system --group foo
Adding system user `foo' (UID 102) ...
Adding new group `foo' (GID 103) ...
Adding new user `foo' (UID 102) with group `foo' ...
Creating home directory `/home/foo' ...

Hello, finally, its is because when you install couchdb from the ubuntu installation graphic app, it puts it inside a readonly directory called snap, then you cant change anything

@nicolas15000 Thanks for the info. As mentioned, the snap is outdated and unsupported, we've unpublished it from the snapcraft store.

Hi, I'm experiencing the same behaviour described above, but on Fedora 31. Runnig the command sudo adduser --system --home /usr/local/var/lib/couchdb --no-create-home --shell /bin/bash --group --gecos "CouchDB Administrator" couchdb
Returns "group --gecos does not exists"
Any ideias?

Hi, I'm experiencing the same behaviour described above, but on Fedora 31. Runnig the command sudo adduser --system --home /usr/local/var/lib/couchdb --no-create-home --shell /bin/bash --group --gecos "CouchDB Administrator" couchdb
Returns "group --gecos does not exists"
Any ideias?
The same issue is getting for me as well...


Is there any way to log the IP address of the client?

It is a very good and useful development server. I'm using it for everything, but sometimes, while debugging, I need to see the IP address in its console logs.
Does this sound useful for somebody else?
Thank you.

Duplicate of #184, pull request submitted in #187


import error - cant not worked in nuxt3

I got a error when use import * as Tone  from 'tone'
error_info:
Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension. (Use node --trace-warnings ...to show where the warning was created)
only  npm run dev got the error。it can workd when  npm run build ,amazing
my code link:https://stackblitz.com/edit/github-cmudtt?file=app.vue
the issue also report in nuxt3: https://github.com/nuxt/nuxt.js/issues/13976
can help me how to fix this,thank you

Hi @wohui. The issue you are getting from sandbox, is that because tone > standardized-audio-context is not a valid ESM package (using ESM syntax but neither using type: 'module' or .mjs extension).
Therefore we need to transpile it:
export default defineNuxtConfig({
  build: {
    transpile: ['tone', 'standardized-audio-context'],
  },
});

Sandbox: https://stackblitz.com/edit/github-cmudtt-nvzmdw?file=nuxt.config.ts

@pi0 hi pi0 very thank you ！ can you tell me how to find out it is caused by this library

Hi @wohui, sorry for the inconvenience. I'm the author of standardized-audio-context. I planned to update the way the package is published since "type": "module" became a thing but I don't know yet how that should be done to support all the different use cases. There are some frameworks/tools which only support the new way but there are others which still require the old format. 🤷
standardized-audio-context is for example already published as an ESM package but it doesn't have the "type": "module" property yet which might be the reason why that's not picked up by some bundlers.

Hi @chrisguttandin I would suggest to start compatibility by renaming .jsto .mjs when using esm syntax and type: module is not possible. Feel free to create an issue and ping me would be happy to help on packaging support.

I had the same issue with contentful-management and after I added it to transpile array I faced a new error which I'm not sure how to resolve. I'm not sure what to do next ?
ncaught SyntaxError: The requested module '/_nuxt/node_modules/lodash.isplainobject/index.js?v=c1b556fd' does not provide an export named 'default' (at index.es-modules.js?v=c1b556fd:4:8)

I had the same issue with contentful-management and after I added it to transpile array I faced a new error which I'm not sure how to resolve. I'm not sure what to do next ?
ncaught SyntaxError: The requested module '/_nuxt/node_modules/lodash.isplainobject/index.js?v=c1b556fd' does not provide an export named 'default' (at index.es-modules.js?v=c1b556fd:4:8)


Movie path is wrong after calling RadarrAPIv3.add_movie

Movie path should be {root_dir}/{movie_title} instead of {root_dir}{movie_title} (notice the slash). I don't think that my Radarr is improperly setup, but maybe most people have the trailing slash included in their root dir. An easy fix would be to use os.path.join. This can easily be patched by just explicitly stating the root dir when calling the function though.
Also, using Radarr's "Movie Folder Format" setting (advanced option under Settings -> Media Management) would be ideal, but I'm not sure that Radarr's API could facilitate that.

Upon further investigation it appears that the /config/naming endpoint would be useful to get the movie folder format setting.

Thanks for logging this, the quick fix is like you say to just use os.path, however I would like to use the naming config as you found later on. However i'm trying to figure out how to convert the naming params into a path as the params available in the UI dont match the API, i may need to add some conversion to the correct value.

I'll look into this if I find some time as well.

I did some testing and its possible to just use rootFolderPath then Radarr will name the folder appropriately.


Add integration test for workspace saved objects client wrapper

Description

Fix permission validate for addToWorkspaces and deleteByWorkspace in client wrapper
Add integration tests for workspace saved object client wrapper

Issues Resolved

Screenshot

Testing the changes

Check List

[ ] All tests pass

[ ] yarn test:jest
[ ] yarn test:jest_integration
[ ] yarn test:ftr

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[ ] Update CHANGELOG.md
[ ] Commits are signed per the DCO using --signoff

Codecov Report

Merging #206 (b7f0d10) into workspace (29ccc20) will increase coverage by 24.70%.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           workspace     #206       +/-   ##
==============================================
+ Coverage      30.42%   55.12%   +24.70%
==============================================
  Files           2199     1191     -1008
  Lines          45154    24053    -21101
  Branches        7023     4029     -2994
==============================================
- Hits           13737    13259      -478
+ Misses         30810    10139    -20671
- Partials         607      655       +48

Flag
Coverage Δ

Linux_1
?

Linux_2
55.12% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 2222 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Road required icon missing for some parks.

Similar to the issue with the service buildings, it's also missing for some parks, even after  your update.

Yet another small update (1.4.2) has been made to fix this bug.


Review Editorial Looker Studio dashboard

The Data Studio Editorial dashboard has been rebuilt using Looker Studio and linked to the wellcomecollection [default] GA4 Property by Duga Digital. https://lookerstudio.google.com/u/0/reporting/8b09ce41-5256-42ee-846f-f6661f5f91fd/page/93HO
Before Duga move on to other work, I am going to be checking that all functionality has been replicated where possible. Any comments will be forwarded to @jennpb to pass on to Duga Digital.

Here are changes for Duga Analytics:
Create a calculated field landing pageviews / pageviews for page 1
Create calculated field exits / pageviews for top of page 7, filtered by editorial (without /stories) and include in table.
Add calculated field exits / pageviews as metric to table on page 11

@dannybirchall Can we delete page 10 of the dashboard? It looks like it was supposed to help with analysis of specific stories but I could add this after Duga Digital have finished doing their work.

Create calculated field exits / pageviews for top of page 7, filtered by editorial (without /stories) and include in table.

@taceybadgerbrook Do you mean filtered by /articles?

@jennpb Yes. The filter is called, "editorial (without /stories)" but what it does is filter for those page urls that contain /articles.

I've sent those changes to Duga Digital, cc'd Tacey in email.


What if users don't have Julia aliased to julia on their systems?

https://docs.julialang.org/en/v1/manual/environment-variables/#JULIA_BINDIR

https://docs.julialang.org/en/v1/manual/embedding/

https://docs.julialang.org/en/v1/manual/command-line-options/

Base.julia_cmd()


Allow [ ] (array notation) in query string

Hit this when trying to parse URIs :)

URIs are not allowed to contain square brackets (see rfc 3986).
See also e.g. https://stackoverflow.com/questions/40568/are-square-brackets-permitted-in-urls


Fix casper when used with -c

Changes the working directory to the location of the config file so all
relative paths relative to the config file will work properly.

Coverage decreased (-0.6%) to 84.95% when pulling 5790ec524f7c41a3f799fbf3d0857ca9d1d67c73 on fixrelpaths into 969397173e5c672e98a6ec5ab8415640662d114d on master.

Coverage decreased (-0.5%) to 85.062% when pulling eb6d659ef21677d557166110a11cfe108b124e18 on fixrelpaths into 969397173e5c672e98a6ec5ab8415640662d114d on master.

What about the coverage decrease?

Coverage decreased (-0.1%) to 85.432% when pulling 462d324ff7a717575c1d814743740afe873f89c4 on fixrelpaths into 969397173e5c672e98a6ec5ab8415640662d114d on master.


Use RxBinding

how to use rxbinding ? does u2020 build it in?

Using in DebugView, more eventually...


alternative implementations of flooding_correction()

description
I have examined some alternative implementations of the flooding_correction() method.
The motivation of this method, as best as I can tell, is to ensure there are no "windows" (geology reference that arise by chance of not being in the path of any water parcels, but would be flooded due to "water runs downhill" in a real-world situation.
At present, the method implementation uses a few other helping methods to build neighbor-stage arrays and updates the stage at the center cell with the maximum stage of its neighbors. At face value, this seems reasonable to me.

The current implementation is pretty convoluted and difficult to follow. I believe that my implementation below (with _flag set instead to max reimplements the same thing as is currently implemented, but is simpler. This needs to be verified by a consistency check between two runs, or simultaneous computations through a run.
The original matlab implementation actually does something subtly different. Due to the order of looping through the neighbors used in this implementation, the stage value updated is not the maximum of the neighbors, but rather the last cell in iteration that is wet and has a stage higher than the center dry cell. This iteration follows an E --> clockwise iteration. I have implemented (I think) the original matlab version below, when the _flag is set to legacy.

Prelim tests
I have run a set of simulations with a) the current implementation, and b) my implementation of the matlab version.

old
new

errored

and if I'm being honest, they all kinda don't look excellent, and I can't really discern any qualitative difference.
As a result, I've decided not to make any change to the flooding_correction in #133.
def flooding_correction(self):
        """Flood dry cells along the shore if necessary.

        Check the neighbors of all dry cells. If any dry cells have wet
        neighbors, check that their stage is not higher than the bed elevation
        of the center cell.
        If it is, flood the dry cell.
        """
        _msg = 'Computing flooding correction'
        self.log_info(_msg, verbosity=2)

        pad_wet_mask = np.copy(np.pad(self.wet_mask, 1, 'edge'))
        pad_stage = np.copy(np.pad(self.stage, 1, 'edge'))

        _ord = np.array([5, 8, 7, 6, 3, 0, 1, 2])
        for i in np.arange(self.L):
            for j in np.arange(self.W):
                if self.wet_mask[i, j] == 0: # locate dry nodes

                    # slice the padded array neighbors
                    wm_nbrs = pad_wet_mask[
                        i - 1 + 1:i + 2 + 1, j - 1 + 1:j + 2 + 1]
                    stage_nbrs = pad_stage[
                        i - 1 + 1:i + 2 + 1, j - 1 + 1:j + 2 + 1]

                    wm_nbrs_flat = wm_nbrs.ravel()
                    stage_nbrs_flat = stage_nbrs.ravel()

                    _flag = 'legacy'
                    if _flag == 'max':
                        wm_nbrs_flat[4] = 0

                        wm_nbrs_stage_flat = stage_nbrs_flat[wm_nbrs_flat]
                        if wm_nbrs_stage_flat.size > 0:
                            max_wm_nbrs_stage = np.max(wm_nbrs_stage_flat)

                            if max_wm_nbrs_stage > self.eta[i, j]:
                                self.stage[i, j] = max_wm_nbrs_stage
                    else:
                        wm_nbrs_ord = wm_nbrs_flat[_ord]
                        stage_nbrs_ord = stage_nbrs_flat[_ord]
                        stage_above_eta = (stage_nbrs_ord > self.eta[i, j])
                        both_conds = np.logical_and(wm_nbrs_ord, stage_above_eta)
                        if np.any(both_conds):
                            idx = np.where(both_conds)[0][-1]
                            self.stage[i, j] = stage_nbrs_ord[idx]

also of not in this regard, is that the wet_mask is calculated before water iteration in the matlab implementation.
so, add near the top of water iteration:
self.wet_mask = self.depth >= self.dry_depth


Hi,
what environment is expected for executing "make all"?
-Cygwin?
-msys2?
-WSL?
greetings
Carsten

hi Carsten
this is being tested only on Linux (mostly tested on ubuntu machines) due to vagrant compatibility in these other env.

@knabben already addressed the question. Closing for now.
See Also: https://github.com/kubernetes-sigs/sig-windows-dev-tools/issues/203

/close


Switch pg storage management away from psql

This moves storage_up and storage_down for the Postgres adapter to use an Ecto/Postgrex connection, rather than relying on psql.
This closes #854.

This has taken an embarrassing amount of time for such small code changes, and I'm still getting timeout errors that I don't understand.

@GeorgeTaveras1231 Thanks for the suggestions, I've updated run_query to destructure the error, much better.

No problem @sorentwo, glad to help
btw, I don't know if this should be done as part of this same PR, but we should not forget about the mysql dependency here.

I've made some changes to use Task.Supervisor.async_nolink with Task.yield, which works well aside from random timeouts. With ericmj/postgrex#128 being merged I think this will have to be reworked again though.

The connection is now closed after the query is run, which prevents a timeout for back-to-back invocations of the storage_up or storage_down.

@josevalim This has been updated with the db_connection changes, some cleanup, and squashed into a single commit. CI seems to be having s3 errors, so I'm not sure of the build status now.

Ok, everything is passing now. This is ready to go from my end.


Fix number of MXH coeffs in tequila2imas

Fixes #768
@mgyoo86 please test

@orso82 See, this is what happens if I just start pushing changes and don't test them first...
@mgyoo86 Sorry, try again. And by the way, anytime you do slicing, you want to use @view or @views to avoid allocations. For example:
A = rand(3,3)
B = zeros(3)
B .= A[:, 2] # allocates new vector of length 3, then broadcasts it
B .= @view(A[:,2]) # does not allocate, just a view of the original matrix
@views B .= A[:, 3] .+ A[1, :] # again, no allocations

@bclyons12 Thank you for the quick fix, it now works!
Also, I appreciate the great tips on using @view :)
Julia's allocations under the hood are still too magical thing for me  😭
BTW, this might be one of good use cases of the forked repo, where the GitHub actions run tests for my pushed commits on remote (not harshing my laptop), after which I can open the PR safely.

@bclyons12
Before closing this PR, I have a question about the dim2 for the flux-coordinate (profiles_2d[1])
What is the meaning of the following definitnion of dim2?
eq2d.grid.dim2 = vcat([0.0, 0.0, 0.0, 0.0, 0.0], fill(1.0, (MXH_modes,)), fill(-1.0, (MXH_modes,)))

If there is no specific meaning, can we just set dim2 as the index, like the following?
eq2d.grid.dim2 = collect(Float64, 1:length(MXH_modes))

The reason why I ask this follows.
In the following PR for the IMAS repo, I implemented new plot recipes, of which 3D plot recipe (contour, surface, ...) uses dim1 and dim2 as x and y axes.
https://github.com/ProjectTorreyPines/IMAS.jl/pull/216
The problem is that I need x and y data sorted in ascending order to use recipes of contour or heatmap.
The new recipes work well with the (R,Z) coordinate, but will not work for the flux-coordinate as the dim2 is not defined in sorted ascending order.

In this case, eq2d.psi is storing not the flux, but the MXH coefficients of each flux surface. eq2d.grid.dim1 is the normalized rho_toroidal, labeling each flux surface. eq2d.grid.dim2 is supposed to represent the "mode type". The first 5 values are (R0, Z0, epsilon, kappa, c0). Those get "mode type" 0. Then the next MXH_mode values correspond to cosine terms and all get positive 1. The last MXH_mode values correspond to sine terms and get negative 1.
@orso, perhaps we should do
eq2d.grid.dim2 = vcat([0.0, 0.0, 0.0, 0.0, 0.0], 1:MXH_modes, .-(1:MXH_modes))?

@bclyons12 I like your proposal! Since it carries more information and possibly allows skipping of modes.


remove bbknn_full_unscaled

This PR both a) removes bbknn_full_unscaled (which I will move to a PR to re-add) and b) adds test args to a bunch of long-running batch integration methods.
Submission type

[ ] This submission adds a new dataset
[ ] This submission adds a new method
[ ] This submission adds a new metric
[ ] This submission adds a new task
[ ] This submission adds a new Docker image
[X] This submission fixes a bug (link to related issue: fixes #432 )
[ ] This submission adds a new feature not listed above

Testing

[X] This submission was written on a forked copy of SingleCellOpenProblems
[ ] GitHub Actions "Run Benchmark" tests are passing on this base branch of this pull request (include link to passed test: )
[X] If this pull request is not ready for review (including passing the "Run Benchmark" tests), I will open this PR as a draft (click on the down arrow next to the "Create Pull Request" button)

Submission guidelines

[X] This submission follows the guidelines in our Contributing document
[X] I have checked to ensure there aren't other open Pull Requests for the same update/change

PR review checklist
This PR will be evaluated on the basis of the following checks:

[X] The task addresses a valid open problem in single-cell analysis
[X] The latest version of master is merged and tested
[X] The methods/metrics are imported to __init__.py and were tested in the pipeline
[X] Method and metric decorators are annotated with paper title, year, author, code version, and date
[ ] The README gives an outline of the methods, metrics and datasets in the folder
[ ] The README provides a satisfactory task explanation (for new tasks)
[X] The sample test data is appropriate to test implementation of all methods and metrics (for new tasks)

Hey @scottgigante-immunai! What's the issue with bbknn_full_unscaled?

Thanks... just saw the link in the PR above as well... a bit hidden amongst all of the boxes that could be ticked ^^.

Yes, happy for this to be merged. In the end, the main repo needs to work all the time.

Yes, happy for this to be merged. In the end, the main repo needs to work all the time.

Thanks!


Update to 1.18.2

This goes without saying, but I am going to make it here just for my own sanity. We need to update to 1.18.2.

It's sad, because it currently only half-works on 1.18.2, and crashes most of the time. This is definitely a good idea.

This is fixed now


After submitting a vote, the proposal disappeared from dashboard

Not sure what caused this one.. when I submitted a vote, the proposal was then not visible.

May have been bad timing. Need to confirm its a bug.


Change the language name to plrustu

The PostgreSQL uses the convention of suffixing the name with a "u" to indicate an untrusted language. This adds that convention and opens the possibility of adding "trusted" plrust in the future.

We've long since moved past this being the correct approach.  When we get postgrestd working on MacOS I think then we can take a look at making a proper distinction between trusted and untrusted.  Until then, having that knowledge compiled into the plrust binary is good enough.


Safari Bug - tiled images outside of viewport

Hi,
I'm having an issue that seems to affect only Safari (using 10.1.1) and I think Edge too, but I've not tested as thoroughly on Edge yet.
 This is working great on Chrome and Firefox. Last I tested on IE11 it was okay too.
On Safari however, when zooming in and out, images will disappear and reappear. As far as I can tell if the image would be entirely in the viewport/canvas, it displays, the moment it hits the edge of the canvas, either by panning or by zooming, it seems to disappear entirely.
What should happen is it should just be clipped by the viewport.
I've stripped down our working site to the bare minimum to demonstrate the problem here:
http://files.onedarnleyroad.com/safari.html
Try in Safari, then in Chrome and see the difference.  Use the input range to change zoom
Full source code of that link is here, aside from the CDN links and refs to placehold.it, it should work as is:
<!DOCTYPE html>

<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, user-scalable=no, initial-scale=1.0, maximum-scale=1">
<title>Example</title>

		<input type="range"
			id="carouselZoomControls"
			min="1"
			max="100"
			value="50"
			step="1"
			aria-valuemin="1"
			aria-valuemax="100"
			aria-valuenow="50">
		<output  class='visually-hidden' for="carouselZoomControls" id="carouselZoomControlsAmount">50</output>

Looks like this is related to https://github.com/openseadragon/openseadragon/issues/1211 . What do yuo think @iangilman ?

Agreed... I believe it's the same issue. @nathanedwards are your original images PNG, by any chance? We think this happens when there's some reason for transparency checking. Take a look at #1211 for more discussion.

@nathanedwards Okay, I think I've fixed it... please try #1222.

@iangilman That's fixed it! many thanks

Excellent... thank you for confirming, and reporting in the first place :)


Incorrect time

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://timertomato.com/'
See error incorrect time
Try adjusting by selecting the settings icon/gear icon.
Again produces incorrect timer time on the main page

Expected behavior
Expect the timer to display time as per the setting.
Screenshots

Desktop (please complete the following information):

Browser [chrome]
Version 128.0.6613.121 (Official Build) (arm64)]

I can fix it if the maintainer is busy with other stuff(life).
Please point me where I should look at in code.
HTH:)


Setup stuck in prompt loop

With the setup.exe, if it finds a previous installed version it will ask if it should track that version and then that everything in the folder that contains the version will be deleted, then it will start over if i confirm both. Eventually got it to installed by pressing no and on "exit setup" no again.
After install the current version was tracked as by "nvm current" but nvm list would return "No installations recognized".

Please see the following:

Uninstall Existing Node Installation Before Installing NVM4W
Why do I Need to Uninstall Node.js Before Installing NVM for Windows?

After install the current version was tracked as by "nvm current" but nvm list would return "No installations recognized".

nvm current just runs node -v. Windows does this by running the first node.exe it finds in the PATH. In your case, I suspect the old installation wasn't actually uninstalled, so you're still seeing the original installation. When you run nvm ls, it scans the NVM root directory for installations. Since your original installation didn't actually get moved, this directory would be empty. That's why it says there aren't any installations.


PL [3.1.23] Parse PDF file to text, transform to mobile friendly PDF or model

Parse PDF file to text, transform to mobile friendly PDF or model.
SPIKE ? Figure out how to do this with eLeaflet to get mobile friendly leaflet format into mobile app
LEARNINGS:
Without AI, It's not possible transform leaflet PDFs and achieve the same UX as with paper leaflet. There are two possible solutions:
use some structured data format instead of PDF (or maybe PDF accessibility tags could be helpful)
create mobile friendly PDFs editorially
There is no library for Vapor for parsing PDFs.
For every product backlog item:

rule
description
status

Task description
add at least short description about the task
✅

Acceptance criteria
clear description (bullet points) what is output of the task (output of team refinement)
✅

team engagement
one person/pair/team (list names in case of more than 1 person)
1+

task reviewed by at least 1 peer
acceptance criteria passing
X

ruler
description
status

branch created
- branch with correct type (feature/bugfix/...) - branch name contains JIRA reference
X

tests
- tested manually - unit tests implemented if applicable (team agreement) - integration/E2E tests for finished feature if applicable (team agreement)
X - -

sdlc
if the task covers acceptance criteria from requirement add test case(s) to SIT documentation -technical documentation updated (DCS) if applicable (team agreement
- -

coding standards
static analysis (linter, sonarQ) passing
X

development practices
commits contain reasonable message - logging enhanced - monitoring updated - analytics added/updated
X - - -

pull request
- 2 approvals required - build passing - PR contains description (+ screenshot or gif if applicable) - PR always rebased on master - delete remote branch after merge
X X X X X

Irrelevant

Irrelevant


chore: use docker image to test library generation scripts

This PR changes .github/workflows/verify-generation-config.yaml to use the docker image created in https://github.com/googleapis/sdk-platform-java/pull/2493 instead of directly calling the scripts from the host.

Testing in progress
https://github.com/googleapis/google-cloud-java/actions/runs/8033790367/job/21944638790?pr=10435

Test was OK


ZeroShotAgent does not support multi-input tool Calculator.

I am trying to follow quick start guide for using agents from https://python.langchain.com/en/latest/getting_started/getting_started.html#agents-dynamically-call-chains-based-on-user-input while following steps I am seeing error
ZeroShotAgent does not support multi-input tool Calculator.

I am using langchain==0.0.152 and python version Python 3.8.10
Python code I executed
from langchain.agents import load_tools
from langchain.agents import initialize_agent
from langchain.agents import AgentType

llm = OpenAI(temperature=0)
tools = load_tools(["serpapi", "llm-math"], llm=llm)
agent = initialize_agent(tools, llm, agent=AgentType.ZERO_SHOT_REACT_DESCRIPTION, verbose=True)

The Error I am seeing
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
/tmp/ipykernel_1917316/1048650410.py in <module>
      1 llm = OpenAI(temperature=0)
      2 tools = load_tools(["serpapi", "llm-math"], llm=llm)
----> 3 agent = initialize_agent(tools, llm, agent=AgentType.ZERO_SHOT_REACT_DESCRIPTION, verbose=True)

~/Code/langchainApp/venv/lib/python3.8/site-packages/langchain/agents/initialize.py in initialize_agent(tools, llm, agent, callback_manager, agent_path, agent_kwargs, **kwargs)
     50         agent_cls = AGENT_TO_CLASS[agent]
     51         agent_kwargs = agent_kwargs or {}
---> 52         agent_obj = agent_cls.from_llm_and_tools(
     53             llm, tools, callback_manager=callback_manager, **agent_kwargs
     54         )

~/Code/langchainApp/venv/lib/python3.8/site-packages/langchain/agents/mrkl/base.py in from_llm_and_tools(cls, llm, tools, callback_manager, output_parser, prefix, suffix, format_instructions, input_variables, **kwargs)
     99     ) -> Agent:
    100         """Construct an agent from an LLM and tools."""
--> 101         cls._validate_tools(tools)
    102         prompt = cls.create_prompt(
    103             tools,

~/Code/langchainApp/venv/lib/python3.8/site-packages/langchain/agents/mrkl/base.py in _validate_tools(cls, tools)
    123     @classmethod
    124     def _validate_tools(cls, tools: Sequence[BaseTool]) -> None:
--> 125         super()._validate_tools(tools)
    126         for tool in tools:
    127             if tool.description is None:

~/Code/langchainApp/venv/lib/python3.8/site-packages/langchain/agents/agent.py in _validate_tools(cls, tools)
    457         for tool in tools:
    458             if not tool.is_single_input:
--> 459                 raise ValueError(
    460                     f"{cls.__name__} does not support multi-input tool {tool.name}."
    461                 )

ValueError: ZeroShotAgent does not support multi-input tool Calculator.

Let me know if more information is needed or if this is expected behavior then documentation changes are needed.

+1
Same issue here

Not sure why that is not allowed - its not like LLM's can't generate the input lol. I just overwrote the from_llm_and_tools method to not validate the tools.

I created a PR https://github.com/hwchase17/langchain/pull/3803 that removes the restrictive checking of multi-input in the Agent base class. Will need reviewers to +1 and merge.

langchain   0.0.153 can handle this error.

you bet.

I meet this problem again with newest version.

Any update on this? I cannot use tools.

I face the same issue now.
Name: langchain
Version: 0.0.308
Summary: Building applications with LLMs through composability
Home-page: https://github.com/langchain-ai/langchain
Author:
Author-email:
License: MIT
Location: /Users/cgm_mbf_lemery_mac/miniconda3/envs/torch/lib/python3.10/site-packages
Requires: aiohttp, anyio, async-timeout, dataclasses-json, jsonpatch, langsmith, numpy, pydantic, PyYAML, requests, SQLAlchemy, tenacity
Required-by: langchain-experimental, langflow, langfuse
`from typing import Optional, Type
from langchain.chains.conversation.memory import ConversationBufferWindowMemory
import random
from langchain.callbacks.manager import (
AsyncCallbackManagerForToolRun,
CallbackManagerForToolRun,
)
Set up the turbo LLM
turbo_llm = ChatOpenAI(
temperature=0,
model_name='gpt-3.5-turbo'
)
email = 'XXXXXXX'
url = "https://XXXXXXX.atlassian.net/rest/api/3/issue"
class CustomJiraToolIssueStory(BaseTool):
"""
Custom Jira Tool for creating tickets in Jira.
"""
name = "CustomJiraPost"
description = "Useful to create tickets in Jira"
def _run(
    self,
    tool_input: str,
    url: str,
    email: str,
    run_manager: Optional[AsyncCallbackManagerForToolRun] = None
) -> str:

    """Use the tool."""

    url = url

    auth = HTTPBasicAuth(email, api_token_jira)

    headers = {
      "Accept": "application/json",
      "Content-Type": "application/json"
    }

    payload = tool_input

    response = requests.request(
       "POST",
       url,
       data=payload,
       headers=headers,
       auth=auth
    )

    return json.dumps(json.loads(response.text), sort_keys=True, indent=4, separators=(",", ": "))

async def _arun(
    self,
    tool_input: str,
    url: str,
    email: str,
    run_manager: Optional[AsyncCallbackManagerForToolRun] = None,
) -> str:
    """Use the tool asynchronously."""
    raise NotImplementedError("custom_search does not support async")

Jira = CustomJiraToolIssueStory()
tools = [Jira]`


Readme file revisions

A few edits for clarity

@googlebot I signed it!

Closing this pull request as the 2021 program is over.


Portable internet for CoM

I might have some contacts with AT&T and Verizon, let me check.

AT&T contact fell through. Where do we stand on this? I will ask at CoM this Sunday about their bandwidth.

No update from me. I can make it a priority for this week. Chris, you
mentioned you were checking our Verizon? I will find two other alternatives
for consideration.
On Tue, Aug 9, 2016 at 8:32 AM, Chris Mathews<EMAIL_ADDRESS>wrote:

AT&T contact fell through. Where do we stand on this? I will ask at CoM
this Sunday about their bandwidth.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/CityCampNC/issues/105#issuecomment-238538537,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB3Ie1pv6x6-KOyg30M-B7RGKwyITUTqks5qeHNjgaJpZM4I0zIr
.

I have a contact and he is going to price it for us. Stan<EMAIL_ADDRESS>-<PHONE_NUMBER>

CoM uses TWC for their internet. So there are actually three seperate netwowrks available to wireless access. Cable but I think we're probably good. cableWIFI, TWCWIFI and CoM-Guest.   Need to check I will encourage people to bring a MiFi for heavy lifting.

I have a lead here. Met someone at Verge NC last night: TourTech connected<EMAIL_ADDRESS>contact shannon at<PHONE_NUMBER> x 102 - she seemed interested and could entertain an in-kind sponsorship. We need to move fast on this (to potentially get logo's on marketing material), can someone contact her today?

Calling now.
On Aug 31, 2016 8:18 AM, "Jason Hibbets"<EMAIL_ADDRESS>wrote:

I have a lead here. Met someone at Verge NC last night: TourTech
connected<EMAIL_ADDRESS>contact shannon at<PHONE_NUMBER> x 102 -
she seemed interested and could entertain an in-kind sponsorship. We need
to move fast on this (to potentially get logo's on marketing material), can
someone contact her today?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/CityCampNC/issues/105#issuecomment-243746185,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOGta9ugsok8li9Sp3hjOlho8DYwZ25ks5qlXDsgaJpZM4I0zIr
.

So is this issue closed? What's left here?
On Wed, Aug 31, 2016 at 8:22 AM, Chris Mathews<EMAIL_ADDRESS>wrote:

Calling now.
On Aug 31, 2016 8:18 AM, "Jason Hibbets"<EMAIL_ADDRESS>wrote:

I have a lead here. Met someone at Verge NC last night: TourTech
connected<EMAIL_ADDRESS>contact shannon at<PHONE_NUMBER> x 102

she seemed interested and could entertain an in-kind sponsorship. We need
to move fast on this (to potentially get logo's on marketing material),
can
someone contact her today?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<https://github.com/codeforraleigh/CityCampNC/issues/105#issuecomment-
243746185>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AAOGta9ugsok8li9Sp3hjOlho8DYwZ25ks5qlXDsgaJpZM4I0zIr>
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/codeforraleigh/CityCampNC/issues/105#issuecomment-243747096,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB3Ie3UqI3kOW5GZf3a_3MbgD8Xp1Jggks5qlXH4gaJpZM4I0zIr
.


fix: eliminate the serialize-javascript vulnerability warning

By switching to a fork of copy-webpack-plugin v5, so that we can
circumvent the issue in a non-semver-breaking way.
Fixes #5782
What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Docs
[ ] Underlying tools
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

Other information:

So maybe it would be better to do the Update and Migration?
https://github.com/webpack-contrib/copy-webpack-plugin/blob/master/CHANGELOG.md#-breaking-changes

I strongly do not recommend do it

Why?
You're afraid that doing this quick fix will mean people won't work on properly updating / migrating?

@peteruithoven We can do it in copy-webpack-plugin, it is not hard, I just ask why it is hard to update, but if it is require more time I can do patch release right now

@evilebottnawi it's hard to update because Vue CLI allows users to tap into the copy-webpack-plugin configuration (I don't know how many would do this but there will surely be some). So updating it would break their apps.
I do plan to update it in the next major, but that would take another 2 to 3 months before being stable.
So the fork is used as a temporary fix to prevent the audit warning from scaring newcomers away.
It would certainly be better if a release can be made in the upstream package to address this issue.
I'll close this PR then.

@sodatea let's do security release

Done https://github.com/webpack-contrib/copy-webpack-plugin/releases/tag/v5.1.2

@evilebottnawi Thanks!

Thanks! :)


LIF Neuron not working as expected

Describe the bug
LIF neurons not working as expected
Application: Brain Simulator, Neuron Engine,
Module/Network: (if your network, please attach XML file)
To Reproduce
Steps to reproduce the behavior:

Create always firing neuron
connect to LIF neuron with weight 1
Not irregular firing of LIF neuron (A)
Similar problem with axon delay (B)

Expected behavior
Screenshots

Desktop (please complete the following information):

OS:
Version [v0.9a]

Add any other context about the problem here.

I doubt whether it is the root cause of what shows here: I replayed the scenario as described, with no extra neurons in the network except the described trio. Even at engine speed 10 I saw hardly any deviation from desired functionality (A and B fire 1 cycle after i). What I did observe is that i, A and B sometimes missed a single pulse, but in a non-related matter: if i skipped, A and B did not.
I believe the basic firing behavior of both types is correct, but the root cause is somewhere in how the engine deals with hundreds or thousands of neurons firing.


[C++] Implement row range read API for IPC file (and Feather)

The objective would be able to read a range of rows from the middle of a file. It's not as easy as it might sound since all the record batch metadata must be examined to determine the start and end point of the row range
Reporter: Wes McKinney / @wesm
Note: This issue was originally created as ARROW-8391. Please see the migration documentation for further details.

Hello - just wondering if anyone is still thinking about this? We have a data platform where this would be extremely useful.
Looking at the Footer structure, the block information is already in there as a list. Since this structure needs to be read anyway, is it sufficient to e.g. add a recordOffset property to the Block, only meaningful for record batches? A simple solution like this would allow paginated retrieval and processing of moderately large datasets I would think, at least up to a few million batches. Compared to scanning through the batches one by one from cloud storage it would be a big win.
In terms of adding to the language APIs, in our case we are already working at the FB / batch level because we need non-blocking data streams, so just having it in the file format would be enough for us. My guess is that adding it to the language APIs would make it more generally useful though.
For the pre-built index discussed above, I'd think this is only needed if (a) the number of batches is very large, and (b) the arrangement of batches is very asymmetrical (e.g. lots of big batches followed by lots of small batches) and (c) the file is read a lot more often than it is written. Perhaps this index structure could be added later, and fall back to either bisecting the list of blocks or generating an index at read time. Depends I guess, how much extra effort is needed.
We have a very crude solution for now - use a constant batch size and write that value to the custom metadata in the footer for datasets created by our platform. This is really all the functionality we need, the only problem is it's not portable.


Enhance Add Link dialog to include list of page headers and also match server Add Link dialog

All merged here: https://github.com/jgraph/drawio/issues/1266


bug: "failed to download bfg" error on Windows

Version

0.16.0
v0.17.1701356806

Describe the bug
On Windows, Cody shows this error message:

Failed to download bfg from URL https://github.com/sourcegraph/bfg/releases/download/v5.2.6637/bfg-windows-arm64.zip: AxiosError: Request failed with status code 404

Expected behavior
No error message
Additional context
No response

cc @philipp-spiess @valerybugakov

Thank you for reporting! This error is happening since we don't build bfg for Windows ARM (yet?). Any idea @SuperAuguste how to support this?
I tried building it like this
❯ rustup target install aarch64-pc-windows-msvc
❯ cargo zigbuild --target=aarch64-pc-windows-msvc --profile=release-without-debug

but it failed with errors about GNU compiler
...
warning<EMAIL_ADDRESS>GNU compiler is not supported for this target

I tried using cargo build instead but that seems to require that we build the binary on a Windows computer
  running: "lib.exe" "-....
  error occurred: Failed to find tool. Is `lib.exe` installed?

I'm installing clang on my windows computer right now to see if I can cargo build the aarch64 target...

This line here indicates it failed to start the binary.
█ CodyEngine: failed to initialize Error: spawn EBUSY

I only built the binary but wasn't able to test it on arm64-windows. For now, I think it's best to stick with saying that Windows arm64 is not supported. I think we can support it eventually but it requires engineering time to setup the build so that we test it in CI and automate releases for it.
We should still improve error handling so that it either silently doesn't work or we notify the user that Windows arm64 is not supported. However, before doing that, we may want to wait a bit to see how many users hit on this error. The JetBrains plugin and Neovim don't work on windows-arm64 either because we don't build an agent binary for it. We don't have any special handling to inform users about this case and it hasn't been reported as an issue IIRC.


CSGOFloat Market Checker extension always switching to first page of the skin

Hi, I'm using CSGOFloat Market Checker chrome extension. When I enter market url with specific page (start=x&count=y) it loads correct page and after ~2 second switches to the first page of the skin (sometimes it doesn't load correct page at all).
For example:
https://steamcommunity.com/market/listings/730/AK-47 | Slate (Field-Tested)?start=100&count=100
Same thing when I refresh the page.
Is there any chance that you could fix that?

I think you might wanna open an issue over at https://github.com/csgofloat/extension

Moved to extension issues, thanks
https://github.com/csgofloat/extension/issues/159#issue-1812225207


New socket implementation doesnt recognize listening UDP ports

Here's an example of my test that was working before upgrading to testinfra 1.12.0.
@pytest.mark.parametrize('ossec_service', [
    dict(host="<IP_ADDRESS>", proto="tcp", port=22, listening=True),
    dict(host="<IP_ADDRESS>", proto="udp", port=1514, listening=True),
    dict(host="<IP_ADDRESS>", proto="tcp", port=1515, listening=False),
])
def test_listening_ports(host, ossec_service):
    Ensure the OSSEC-related services are listening on the
    socket = "{proto}://{host}:{port}".format(**ossec_service)
    with host.sudo():
        assert host.socket(socket).is_listening == ossec_service['listening']

Specifically getting a fail on dict(host="<IP_ADDRESS>", proto="udp", port=1514, listening=True) now. Here is the relevant ss and lsof output:
sdrop@mon-staging:~$ sudo lsof -iUDP -n
COMMAND    PID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
dhclient   674   root    5u  IPv4  10425      0t0  UDP *:bootpc
dhclient   674   root   20u  IPv4  10405      0t0  UDP *:15006
dhclient   674   root   21u  IPv6  10406      0t0  UDP *:45681
ossec-rem 1174 ossecr    4u  IPv4  11482      0t0  UDP *:1514
ntpd      3133    ntp   16u  IPv4  18769      0t0  UDP *:ntp
ntpd      3133    ntp   17u  IPv6  18770      0t0  UDP *:ntp
ntpd      3133    ntp   18u  IPv4  18776      0t0  UDP <IP_ADDRESS>:ntp
ntpd      3133    ntp   19u  IPv4  18777      0t0  UDP <IP_ADDRESS>:ntp

sdrop@mon-staging:~$ ss --numeric --listening --udp
State       Recv-Q Send-Q                    Local Address:Port                      Peer Address:Port
UNCONN      0      0                                     *:15006                                *:*
UNCONN      0      0                                     *:1514                                 *:*
UNCONN      0      0                                     *:68                                   *:*
UNCONN      0      0                          <IP_ADDRESS>:123                                  *:*
UNCONN      0      0                             <IP_ADDRESS>:123                                  *:*
UNCONN      0      0                                     *:123                                  *:*
UNCONN      0      0                                    :::45681                               :::*
UNCONN      0      0                                    :::123                                 :::*

It appears that the socket module only looks for the status of LISTEN or ESTAB  but doesn't recognize UNCONN as a listening status.

Thank you for reporting!
This should be fixed in (just released) 1.13.0


Export vanilla describe, so that it doesn't have to be added to added to tests/.jshintrc manually

I want to use Mocha's plain jane "describe" to group expectations for a particular method, but when using ember-cli-mocha, I encounter a jshint failing test because "'describe' is not defined".
Even though jshint complains, describe behaves as one would expect when using it in mocha test files.
Looks to me like all that needs be done is to add it here:
https://github.com/switchfly/ember-cli-mocha/blob/master/index.js#L56
Pretty understandable that it would have gotten missed, as everything listed is specifically added or overridden by ember-mocha.
Thanks for all your excellent work.

You should be able to import describe from the mocha stub module, which ember-mocha also exports. For example: https://github.com/switchfly/ember-cli-mocha/blob/master/blueprints/acceptance-test/files/tests/acceptance/name-test.js#L3

Great. Thanks for the example!


Add support of date time pattern for string representation of date an…

The problem is that calls like #{date.past ... } and others with date converts date and time based on default toString with no way to customize it.
The PR adds corresponding methods which allow to specify date/time pattern

Awesome. This pr reminds me to add Java 8 time support instead of the old Java Date.


Move important UTxO state transition functions to the top-level and test them

This work is intended to allow future modifications to the UTxO state transition function (i.e. collateral) to be tested in isolation, at the unit level.
My changes are primarily to the nested function "applyTx". I have tried to keep my changes minimal:

Use more verbose variable names in that function to make the purpose of each variable clear.
More clearly delineate between transaction outputs that are unspent and transaction outputs "we know about" but may possibly be spent.
Make some effort to separate the ideas of "knowledge of a UTxO" from "ownership of a UTxO" to make testing easier.
Extract out the core state transition function from the existing "do lots" "applyTx" function and move it to the top-level.
Move other useful functions to the top-level for the same reason.
Test important functions in wallet model spec.
Re-implement hasKnownInput/hasKnownOutput to make their implementations a little more clear and symmetric.

Comments
These changes make testing collateral much easier, we can just test the "applyTxToUTxO" function at the unit level, and adjust existing model tests as necessary.
Issue Number
ADP-1092

bors r+

bors retry

bors retry


Azure Load Balance- Regional or Global

I see that this page has a chart that has reclassified the Azure Load Balancer as Global not Regional. It was listed as Regional before.  Why has this changed?  Traffic Manager and Front Door would be the Global items while Traffic Manager and Load Balancer as Regional.
Cheers,
Jeff Smalley MCT
Chicagoville

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

ID: 936c85d9-c953-2def-c399-77cbda32b24d
Version Independent ID: 9173c834-2c40-9169-b13b-6273759a2c8a
Content: Overview of Azure load-balancing options - Azure Application Architecture Guide
Content Source: docs/guide/technology-choices/load-balancing-overview.md
Service: architecture-center
Sub-service: guide
GitHub Login: @doodlemania2
Microsoft Alias: pnp

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 377614

@JeffSmalley Thank you for reaching out. You may refer to : https://docs.microsoft.com/en-us/azure/load-balancer/cross-region-overview . This might explain why it is marked as "Global". However, I will reconfirm the same at the earliest.

@JeffSmalley Thank you for reaching out. You may refer to : https://docs.microsoft.com/en-us/azure/load-balancer/cross-region-overview . This might explain why it is marked as "Global". However, I will reconfirm the same at the earliest.

@JeffSmalley Following up to understand whether my previous comment helps and works out for the mentioned problem statement. Also I have confirmed that the document I shared is the latest one and it explains why it is marked as "Global".

It appears this has been addressed.  Please re-open with additional details if help is still needed.


Create CODE_OF_CONDUCT.md

Codecov Report

Merging #23 (c7a9d89) into master (b62f4db) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #23   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           41        41
  Lines          840       840
  Branches        89        89
=========================================
  Hits           840       840

Continue to review full report at Codecov.

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


Named arguments

What is wrong?
The parser and ast support python-style named arguments, but the names aren't checked in the rest of the compiler.
def f(x: u256, y: u256) -> u256:
  return x - y

def g() -> u256:
  return self.f(y=10, a=5)  # same as f(10, 5), so x = 10, y = 5

Furthermore, functions can be called without specifying argument names, which can be a source of bugs.
def _update(balance0: u256, balance1: u256, reserve0: u256, reserve1: u256):
   ...
self._update(token0.balanceOf(self.address), self.reserve0, token1.balanceOf(self.address), self.reserve1)

How can it be fixed
I think we should require argument names, and require that arguments always be provided in the correct order. I also think we should use : instead of =. Eg self.transfer(from: me, to: you)
We could consider adopting swift's syntax and semantics here https://docs.swift.org/swift-book/LanguageGuide/Functions.html
In swift, function parameters have labels (which default to the parameter name). Labels must be included when calling the function, and arguments must be provided in the correct order. In cases where labels aren't warranted, they can be disabled for a given parameter.
Default case:
def transfer(sender: address, recipient: address):
  ...
self.transfer(sender: me, recipient: you)

Specify different label names, so calls are convenient but the function body can use long names (which can change without breaking the calling code):
def transfer(from sender_addr: address, to recipient_addr: address):
  ...
self.transfer(from: me, to: you)

Disable labels:
def max(_ val1: u256, _ val2: u256):
  ...
self.max(x, y) # instead of self.max(val1: x, val2: y)

note that some args can have labels while others don't
def new_account(_ addr: address, balance: u256 = 0):
  ...
new_account(sender)
new_account(sender, balance: 100)

I like this. It makes things alot easier to read.
For something like this
send_1_dai(my_friend)

it's pretty clear what the parameter is, but for something like this
MyContract::create2(42, 26)

I would need to look at the docs, which is annoying.
MyContract::create2(value: 42, seed: 26)

is much easier to read.
The separation of internal and external names is quite important for this, as things often need to be more verbose on the inside.
def send_double_their_dai(to to_addr: address):
  to_balance: u256 = dai_contract.balanceOf(to_addr)
  send_many_dai(to: to_addr, amount: to_balance * 2)

I think for simpler functions, this might be overkill, but it's all small price to pay in the grand scheme of things

I'm also on board with switching to : instead of using =.

If you have something like this
def transfer(from sender_addr: address, to recipient_addr: address):
  ...

Wouldn't it be reasonable to not require the labels if the variable name matches the argument name. E.g if I use from and to for the variable names I could write the call as:
self.transfer(from, to)

On a more general note, I can see how the change aims to improve safety at the cost of convenience. I'm not 100 % sold if we should adopt it but I'm generally open to the idea.

Wouldn't it be reasonable to not require the labels if the variable name matches the argument name.

Yeah, totally. That's how I've implemented required named args in struct and event constructors (inspired by rust, of course):

(named args were required for struct constructors; I extended that to events)

Yes, I'm on board as long as we continue to not require named arguments if the parameter names already match the argument name :+1:

Yeah, I completely agree.


use http-shutdown

This should make sure that keep-alive connections don't prevent toor from working.

LGTM


Create an alias to open up sublime project

stp commands works in following way:

If the current directory is a part of a Git repo and if there is a .sublime-project file among its ancestor directories, the command opens up that sublime project.
If the current directory is a part of a Git repo but there isn't a .sublime-project file among its ancestor directories, the command opens up the root of the repo.
If the current directory is not a part of a Git repo, the command opens up the current directory.

Hey there -- I really appreciate the contribution.
Cheers,
Robby


Adding option to sort columns using F3 key in SlickGrid.

Issue: #20779
While this PR does not make the column headers keyboard accessible, we are providing users an alternative keyboard shortcut to access the column header sort options.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 11 (0.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.01%) to 37.409%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/base/browser/ui/table/table.ts
0
11
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/sql/base/browser/ui/table/table.ts
1
0.37%

Totals

Change from base Build<PHONE_NUMBER>:
-0.01%

Covered Lines:
14135

Relevant Lines:
34737

💛  - Coveralls


Fix GPU value not showing properly

This Pull Request just increases FASTFETCH_STRBUF_DEFAULT_ALLOC from 64 to 128.
It also adds ctags & cscope files to .gitignore.

Not merging this as this doesn't fix the issue but just making it more unlikely to appear while doubling ram usage


Update http4s-client, http4s-core, ... to 0.23.7

Updates

org.http4s:http4s-client
org.http4s:http4s-core
org.http4s:http4s-dsl

from 0.23.6 to 0.23.7.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s" } ]

labels: library-update, early-semver-minor, semver-spec-patch, commit-count:1

Superseded by #337.


Fix code scanning alert - Insecure randomness

Tracking issue for:

[ ] https://github.com/vrm-piyush/Encryption-Decryption/security/code-scanning/1

Use getRandomValues() to get random charset values