Move bundling to Rollup

So far, the main file was written like this (since https://github.com/edenspiekermann/a11y-dialog/commit/074109c292e2054342baa8e69b5bd548bbce6118 and https://github.com/edenspiekermann/a11y-dialog/commit/577df3389c124d9b7598f5e5f0ea45fdea53ae8b):
;(function (global) {
  var A11yDialog = function () {}

  // More code here …

  if (typeof module !== 'undefined' && typeof module.exports !== 'undefined') {
    module.exports = A11yDialog
  } else if (typeof define === 'function' && define.amd) {
    define('A11yDialog', [], function () {
      return A11yDialog
    })
  } else if (typeof global === 'object') {
    global.A11yDialog = A11yDialog
  }
})(typeof global !== 'undefined' ? global : window)

This pull-request introduces Rollup for bundling and uses the umd format to support both browser and Node environments. As a result, I removed the aforementioned boilerplate from the main file and let Rollup do its thing. Tests pass, and it seems possible to execute the resulting bundle with Node without an error so I assume everything is okay?
Benefits of moving to rollup:

It makes using https://github.com/HugoGiraudel/focusable-selectors possible (see #134)
It simplifies some logic around building/copying
It simplifies adding the version in the banner of the minified file

Rollup is small and great, close to de-facto standard tooling for libraries, and gives you a platform to evolve your bundling/transpiling/etc. if you need to. So that’s probably a good idea. :)
I haven’t reviewed the changes in detail, but two thoughts:

Changing your file structure (moving the minified file, making the /a11y-dialog.js not be an importable IIFE but more like a module) might break the way some users use the library. I’m not sure how big of a risk that is. I was thinking about users loading the library from a CDN like unpkg.com, but it seems that unpkg.com will tend to redirect users to a URL with an explicit package version, e.g. if I visit:

https://unpkg.com/browse/a11y-dialog/ (using a final slash shows a file directory)
I get redirected to:
<EMAIL_ADDRESS>So I might end up using this URL:
<EMAIL_ADDRESS>And moving that file in, say, 5.6.0 should not break that usage.
Still, it might be worth treating this as an API change and bump the version to 6.0.0, to be on the safe side.

Would it make sense to offer a minified ESM build? Ideally you could have output files like:

/dist/a11y-dialog.d.ts
/dist/a11y-dialog.esm.js
/dist/a11y-dialog.esm.min.js
/dist/a11y-dialog.umd.js
/dist/a11y-dialog.umd.min.js

This might be useful for tools and environments such as the browser+CDN, Snowpack/Skypack, and maybe Deno?
One downside is that /dist/a11y-dialog.esm.js would be virtually the same as /a11y-dialog.js at this time (but not if you end up importing focusable-selectors later on, and roll that in your ESM bundle).

@fvsch Thank you so much for taking the time to offer your review, I really appreciate it.

I didn’t really plan on bumping to v6, but maybe that makes sense to be on the safe side as you said. I’ll think about it.
I must say I don‘t know so much about bundling flavours. What would be esm? Is it a format Rollup can compile to?

I added an ESM version in 17e41ee. I tried it as well and it seems to work fine, which is cool. I wonder how it’s going to work when I finalize #134 though.

2. I must say I don‘t know so much about bundling flavours. What would be esm? Is it a format Rollup can compile to?

ESM = ECMAScript 2015 Modules. I think the “correct” name is “JavaScript Modules”, but they were first defined in the ECMAScript 2015 spec and they’re commonly called “ES Modules” — abbreviated to “ESM”.
Technically, with this PR the /a11y-dialog.js file is an ES Module, and Rollup parses that syntax and converts it to UMD (per your configuration). Side note: Rollup works with ESM syntax by default, if you want it to understand CommonJS syntax (module.exports and require())  you have to use a Rollup plugin.
Adding ESM builds in dist should be as simple as duplicating the UMD build config and using output.format: 'es'. For example:
import { terser } from 'rollup-plugin-terser'
import pkg from './package.json'

const banner = () => `/*! a11y-dialog ${pkg.version} — © Edenspiekermann */`

export default {
  input: 'a11y-dialog.js',
  output: [
    // Main file
    {
      file: 'dist/a11y-dialog.js',
      format: 'umd',
      name: 'A11yDialog',
      exports: 'default',
    },
    {
      file: 'dist/a11y-dialog.esm.js',
      format: 'es',
      name: 'A11yDialog',
      exports: 'default',
    },
    // Minified version
    {
      file: 'dist/a11y-dialog.min.js',
      format: 'umd',
      name: 'A11yDialog',
      exports: 'default',
      plugins: [terser()],
      banner,
    },
    {
      file: 'dist/a11y-dialog.esm.min.js',
      format: 'es',
      name: 'A11yDialog',
      exports: 'default',
      plugins: [terser()],
      banner,
    },
    // Copy of the main file for example and tests
    {
      file: 'example/a11y-dialog.js',
      format: 'umd',
      name: 'A11yDialog',
      exports: 'default',
    },
  ],
}

You can probably have a shared output config that looks like this, to reduce duplication a bit:
const outputBase = {
  name: 'A11yDialog',
  exports: 'default',
  banner: () => `/*! a11y-dialog ${pkg.version} — © Edenspiekermann */`,
}

and have the different outputs reuse it:
[
  // Main file
  { ...outputBase, file: 'dist/a11y-dialog.js', format: 'umd' },
  { ...outputBase, file: 'dist/a11y-dialog.esm.js', format: 'es' },
  // Minified version
  { ...outputBase, file: 'dist/a11y-dialog.min.js', format: 'umd', plugins: [terser()] },
  { ...outputBase, file: 'dist/a11y-dialog.esm.min.js', format: 'es', plugins: [terser()] },
  // Copy of the main file for example and tests
  { ...outputBase, file: 'example/a11y-dialog.js', format: 'umd' },
]


Known fix for CVE-2022-43680

Are you going to integrate the known fix for CVE-2022-43680 (High - 7.5)?

https://nvd.nist.gov/vuln/detail/CVE-2022-43680
https://security-tracker.debian.org/tracker/CVE-2022-43680

More details by Docker Hub here: https://dso.docker.com/images/python/digests/sha256%3Ad29fc682d30b314f41d5bb9e19ffe0b8fa128b836146a0a5b19dd60e96d1c19b?vtab=high
I read your FAQ entry about CVEs, but wondering if this fix will be integrated soon.

Python will get rebuilt eventually
There wasn't a fix available in Debian as of https://github.com/docker-library/python/pull/766, but it seems to have been added since. If their update to libexpat 2.5.0 on the 25th coincided with security updates to previous supported versions then we missed it by a day for Python 3.11 and a week for the other variants
Background:

Tags in the [official-images] library file[s] are only built through an update to that library file [–like if the Dockerfile is updated–] or as a result of its base image being updated (ie, an image FROM debian:buster would be rebuilt when debian:buster is built).
-https://github.com/docker-library/official-images/tree/2f086314307c04e1de77f0a515f20671e60d40bb#library-definition-files

Official Images FAQ:

Though not every CVE is removed from the images, we take CVEs seriously and try to ensure that images contain the most up-to-date packages available within a reasonable time frame
- https://github.com/docker-library/faq/tree/0ad5fd60288109c875a54a37f6581b2deaa836db#why-does-my-security-scanner-show-that-an-image-has-cves

Since our build system makes heavy use of Docker build cache, just rebuilding the all of the Dockerfiles won't cause any change. So we rely on periodic base image updates.

We strive to publish updated images at least monthly for Debian. We also rebuild earlier if there is a critical security need. Many Official Images are maintained by the community or their respective upstream projects, like Ubuntu, Alpine, and Oracle Linux, and are subject to their own maintenance schedule.
- from the same FAQ link

Because you mentioned 3.11, just would like to mention that in my case I'm with 3.9 and 3.10.

I believe this has been addressed


map.getZoom() has old value during GridLayer.createTile() when changing zoom levels

During the execution of GridLayer.createTile(), the zoom level is correct in coords.z, but is still wrong in map.getZoom().
Although this may seem like a minor inconvenience, this can have unintended side effects when using functions like map.project().
How to reproduce
Open debug/map/grid.html and insert a console.log(this._map.getZoom()); statement right at the beginning of createTile (or use this Gist here: https://gist.github.com/bb-generation/51c2f55a7b184c0e8d8d)
Then open the file and start zooming. You will see that it will output the old zoom level in the console, while the tiles will show the correct ones (because the actual drawing uses coords.z).
git-bisect
A short git-bisect revealed the first commit with this bug is bbf32ebfcdb0d24d187dbb54eecbea367fd7b72d
Tested Browsers

Chrome 40.0.2214.111 m (64-bit)
Firefox 35.0.1

This is by design. During zoom animation, new tiles are being loaded for the target zoom level. Because the animation is done with CSS transitions, the current zoom level is still returned by map.getZoom(). And in general code should not assume that tiles will be loaded only for the zoom level currently returned by map.getZoom() -- overzooming and retina tiles also contradict that assumption.

Hi, recently, I also meet this problem, and it took a few days to find the problem. Now, I want to use the map method 'latLngToLayerPoint' in 'createTile' method, but the zoom level is old, how can I use the newest zoom level in 'latLngToLayerPoint' method? @bb-generation @jfirebaugh


Duplicate entry files with a multi-page build

Version
5.0.0-rc.1
Reproduction link
github.com
Environment info
Environment Info:

  System:
    OS: Linux 5.10 Ubuntu 20.04.2 LTS (Focal Fossa)
    CPU: (12) x64 Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
  Binaries:
    Node: 16.13.1 - /nix/store/80n94fmsmjxyw1rvyf5zglb911raj2lg-nodejs-16.13.1/bin/node
    Yarn: Not Found
    npm: 8.1.2 - /nix/store/80n94fmsmjxyw1rvyf5zglb911raj2lg-nodejs-16.13.1/bin/npm
  Browsers:
    Chrome: Not Found
    Firefox: 93.0
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.2.1
    @vue/babel-helper-vue-transform-on:  1.0.2
    @vue/babel-plugin-jsx:  1.1.1
    @vue/babel-plugin-transform-vue-jsx:  1.2.1
    @vue/babel-preset-app:  5.0.0-rc.1
    @vue/babel-preset-jsx:  1.2.4
    @vue/babel-sugar-composition-api-inject-h:  1.2.1
    @vue/babel-sugar-composition-api-render-instance:  1.2.4
    @vue/babel-sugar-functional-vue:  1.2.2
    @vue/babel-sugar-inject-h:  1.2.2
    @vue/babel-sugar-v-model:  1.2.3
    @vue/babel-sugar-v-on:  1.2.3
    @vue/cli-overlay:  5.0.0-rc.1
    @vue/cli-plugin-babel: ~5.0.0-rc.1 => 5.0.0-rc.1
    @vue/cli-plugin-eslint: ~5.0.0-rc.1 => 5.0.0-rc.1
    @vue/cli-plugin-router:  5.0.0-rc.1
    @vue/cli-plugin-typescript: ~5.0.0-rc.1 => 5.0.0-rc.1
    @vue/cli-plugin-unit-jest: ~5.0.0-rc.1 => 5.0.0-rc.1
    @vue/cli-plugin-vuex:  5.0.0-rc.1
    @vue/cli-service: ~5.0.0-rc.1 => 5.0.0-rc.1
    @vue/cli-shared-utils:  5.0.0-rc.1
    @vue/compiler-core:  3.2.26
    @vue/compiler-dom:  3.2.26
    @vue/compiler-sfc:  3.2.26
    @vue/compiler-ssr:  3.2.26
    @vue/component-compiler-utils:  3.3.0
    @vue/eslint-config-typescript: ^9.1.0 => 9.1.0
    @vue/reactivity:  3.2.26
    @vue/reactivity-transform:  3.2.26
    @vue/runtime-core:  3.2.26
    @vue/runtime-dom:  3.2.26
    @vue/server-renderer:  3.2.26
    @vue/shared:  3.2.26
    @vue/test-utils: ^2.0.0-0 => 2.0.0-rc.17
    @vue/vue3-jest: ^27.0.0-alpha.1 => 27.0.0-alpha.4
    @vue/web-component-wrapper:  1.3.0
    eslint-plugin-vue: ^8.0.3 => 8.2.0
    jest-serializer-vue:  2.0.2
    typescript: ~4.1.5 => 4.1.6
    vue: ^3.2.13 => 3.2.26
    vue-eslint-parser:  8.0.1
    vue-hot-reload-api:  2.3.4
    vue-loader:  16.8.3 (15.9.8)
    vue-style-loader:  4.1.3
    vue-template-es2015-compiler:  1.9.1
  npmGlobalPackages:
    @vue/cli: 5.0.0-rc.1

Steps to reproduce
Run a build with npm run build
What is expected?
The build does not create duplicate entry files for each page in a multi-page build.
What is actually happening?
Each page has a new generated entry file, despite sharing the same source for the entry before the build.

When creating a multi-page build, a javascript entry file is generated for each page, even if the pages use the same source entry file. Is there a way to prevent this from happening? On sites with a large number of pages, this will cause a huge number of duplicate files that the browser cannot cache between pages.
Vue-Cli version: 5.0.0-rc.1
vue config:
const { defineConfig } = require('@vue/cli-service')
module.exports = defineConfig({
  transpileDependencies: true,
  pages: {
    index: {
      entry: 'src/main.ts',
      template: 'public/index.html',
      filename: 'index.html',
    },
    test: {
      entry: 'src/main.ts',
      template: 'public/test.html',
      filename: 'test.html',
    },
  }
})

index.09ed7944.js and test.ad5688ab.js have identical content besides a sourceMapping comment.

I was actually able to solve this by using the webpack-chain customization point.
I moved my pages object out into its own variable, created a couple of helper functions to determine the unique entry points and created a mapping from the original page names to their deduplicated entry point. Then, using the chainWebpack function of the vue-cli config, I added new entry points for each deduplicated entry point. I iterated over each html-webpack-plugin that was added by the pages option, modifying the chunks array to use the deduplicated entry instead of the unique entry. Finally, I removed the unique entry points from the config, since they were not used any longer.
Full code can be found in this gist: https://gist.github.com/WhiteAbeLincoln/f6842dcca3d08fe0aead127fe452a533
Result:

Notice how we no longer have duplicate js files for each html page.


Added Model Entry Points

Implemented Model Entry Points to create Model objects within the template and initialise them through entry points.
Added the SPM model which can be initialised through the model entry points.
A wrapper method to load a model object called models("modelname/authorname") is added.
Example -
To load the SPM model, after installing the pybamm_cookiecutter project, it can be accessed by calling, pybamm_cookiecutter.Model("SPM"). This would return an initialised model object of the SPM model.
Added two basic tests for model entry points.

Nice to see this progressing! Good to prototype this in pybamm-cookiecutter but once it works well we should move the entry point logic to PyBaMM itself to match the ParameterValues entry points, for example users should be able to do pybamm.Model("author/name")

Tweaked some things to unify both the entry points for parameter_sets and models, I noticed pybamm.parameter_sets is a singleton instance for loading parameter_sets, so I made some changes to make it a doubleton instance to accommodate Model Entry Points and Parameter Sets Entry Points in the same file, as in through the same entry point, just two different instances. I tested the logic and it seems to be working, if you create a third instance through the entry point it will just return you the object of the second instance(the most recent instance that was created).

You can load a Model by calling the pybamm_cookiecutter.Model('SPM') method, and load a parameter_set by doing pybamm_cookiecutter.parameter_sets["Chen2020"] the same way we do it in PyBaMM.

I think this looks good to me and we have two approvals too, so I propose that we merge this so that we can start moving these files to the template. It's likely we'll revisit this code many times anyway, so once we are done, we can follow @valentinsulzer's suggestion in https://github.com/pybamm-team/pybamm-cookiecutter/pull/23#issuecomment-2218443815 to add the same things to the PyBaMM repository


Fix Clock time getter in complex objects docs

The time getter is trying to accessing this.minutes, but it's missing this.!
get time() {
	return `${this.hour}:${minute}`
}

Thanks for noticing!

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add support to disconnect from cluster using workspace overview

What would you like to be added:
Add support for disconnecting from a cluster using the workspace overview
Why is this needed:
The new workspace overview makes it easy to see which clusters you are connected to. In order to disconnect, you have to first click on the cluster, then right click on the icon to select Disconnect. This would be much easier if the ⋮ menu on the workspace overview included Disconnect as an option.
Environment you are Lens application on:

Kubernetes distribution: EKS
Desktop OS: OSX

Thanks, this is something we missed, but we will address this as part of our cluster/overview revamping in 5.0


Citing the AQUAS Pipeline

Hello,
I used the AQUAS TF Chip-seq peak calling pipeline for a work that I will be submitting very soon and I can't find which DOI to officially cite in the paper? Which DOI  is the best to associate with the pipeline?
-Michael

Please cite the GitHub URL and this paper
http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3431496/


[Pump.io] Timeline shouldn't show messages, which I'm not subscribed to

Sometimes I notice that my Pump.io timeline has messages from unknown users. I figured out that these messages were connected with messages by users, whom I'm following, but I couldn't figure out how.
Recent ticket #274  made me understand that AndStatus takes from Pump.io timeline not only "items" of the Timeline, but also "notes", which these items are Replies to (they are embedded into the Replies - items of a Timeline)
Correct behavior would be to download such related messages (optionally!) , but mark them explicitly as "not subscribed" during parsing. So such messages will not appear in the Home Timeline, but will be present in Everything Timeline and in a Conversation view.

That can be happening because some of your contacts is sharing these motes. Try to sharing them, if I'm right you couldn't.

@moshpirit

That can be happening because some of your contacts is sharing these motes.
I don't really understand @yvolk's post, but yes, 99% probability that what he's seeing is shared messages by people he follows, from people he does not. That's normal, and the client just needs to show it properly.

Try to sharing them, if I'm right you couldn't.
No, you can share whatever you see, the author doesn't matter.

Done: message, to which subscribed message is a reply, is explicitly marked as not subscribed.

The fix is available since v.29.00. Currently in the Open Beta Testing Channel: https://play.google.com/apps/testing/org.andstatus.app


Import of nuxt is slow - 3 seconds for import -> speed it up somehow

What problem does this feature solve?
It is pretty critical for serverless setups on lambda and so on.
https://nuxtjs.org/api/nuxt-render/
console.time('test')
const { Nuxt } = require('nuxt-edge')
console.timeEnd('test')

test: 2847.106ms

Its way too much to be 3sec for cold start
I tried to look why it take so long and 99% of time is spent on in nuxt-edge\dist\nuxt.js at the import section for that 50 imports section ..
There should be just a render function that dont have all that 50+ imports and other things that not really needed for rendering and used for building/debugging/etc
Nuxt 1 have like 0.5-1 second less import time, but still way too much, but nuxt-edge made it even worse

This feature request is available on Nuxt community (#c7483)

Hi @aldarund
Actually, when the app is built, it's better to use nuxt-start, until the package is published for 2.0, you can require it like so:
console.time('test')
const { Nuxt } = require('nuxt-edge/dist/nuxt-start')
console.timeEnd('test')

test: 208.735ms

When released, you will do:
const { Nuxt } = require('nuxt-start')

I'll keep it open until Nuxt 2.0 is out.

It does not provide Builder.
import { Nuxt, Builder } from 'nuxt-edge/dist/nuxt-start'

It's normal since it's only runtime of Nuxt.js, no webpack, no babel, only Core, Modules and Renderer.

I summarized some time-consuming libs in Nuxt:
console.time('Time-consuming dependencies')
require('webpack')
require('webpack-bundle-analyzer');
require('uglifyjs-webpack-plugin');
require('@vue/component-compiler-utils')
require('html-minifier')
require('html-webpack-plugin')
console.timeEnd('Time-consuming dependencies')

console.time('Nuxt Core                  ')
require('nuxt-edge')
console.timeEnd('Nuxt Core                  ')

Majority of them have major release between Nuxt 1 and Nuxt-edge.
And the importing is more like a warming step, all imported modules will be cached, so I think it's reasonable to have this funcitonality.
@Atinux @pi0, do you think it's necessary to make them dynamic or lazy require in Nuxt, for example: require webpack inside Builder constructor or some where else inside function scope ?

Which of those Time-consuming dependencies does nux-start require?
Because preloading them makes it go from 119.124ms to 68.404ms
I guess they have shared dependencies on some smaller packages?

For me importing nuxt-start-edge takes 380-400ms
consola - 60ms
vue-server-renderer - 50ms
fs-extra - 52ms
serve-static - 40ms
esm - 46ms

Seems like we will have to load consola asynchronously 🤷♀


[CHORE] cleanup cache and exception on make test

moved the invalidate_forever task to proper location and use create_permanent_task. and there was a Task never awaited Exception when running tests

Codecov Report

Merging #1899 (45c8dbc) into main (e50a7fb) will decrease coverage by 7.80%.
The diff coverage is 0.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main    #1899      +/-   ##
==========================================
- Coverage   56.79%   48.99%   -7.80%
==========================================
  Files          49       49
  Lines        7490     7490
==========================================
- Hits         4254     3670     -584
- Misses       3236     3820     +584

Files Changed
Coverage Δ

lnbits/app.py
42.40% <0.00%> (ø)

... and 17 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Azure Key Vault Feature Request for Key Vault with managed HSM

Dummy ticket

@jiasli this request is for Key Vault with managed HSM.

move to later sprint due to previous priority change. working on it now.

12328

move to later Sprint, managed HSM control plane will be ready around April.

move all MSHM related feature to backlog. current status is CLI feature ready for features with Swagger, but not released due to service not public yet. Public preview maybe around June/July timeline, but not locked down yet. Will close the issue when service public and CLI feature merged/released.

PR for Ignite has been merged. Closing this one.


pyvinecopulib 0.6.5 :snowflake:

pyvinecopulib 0.6.5 :snowflake:
Destination channel: Snowflake
Links

PKG-4852
dev_url (pypi): https://github.com/vinecopulib/pyvinecopulib/tree/v0.6.5
conda-forge: feedstock not found on conda-forge
pypi: https://pypi.org/project/pyvinecopulib/0.6.5
pypi inspector: https://inspector.pypi.io/project/pyvinecopulib/0.6.5

Explanation of changes:

new feedstock
recipe from grayskull
patch build dependencies out of runtime dependencies
upstream PR: https://github.com/vinecopulib/pyvinecopulib/pull/131

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_13fn4tcc92/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:22: patch_must_be_in_build: patch must be in build when source/patches is set.
===== Final Report: =====
1 Error and 0 Warnings were found

Hi, maintainer of the pyvinecopulib package here :) I have pushed a PR to properly unvendor boost and eigen: it's on the main branch already and it will make its way to PyPI once the CI completes. Might I suggest to use this latest version ?
Note that the build now needs the path for the boost and eigen installs as environment variables, respectively  Boost_INCLUDE_DIR and EIGEN3_INCLUDE_DIR.
Typically, on Ubuntu, one can use:
sudo apt install libeigen3-dev libboost-all-dev
export Boost_INCLUDE_DIR=/usr/include
export EIGEN3_INCLUDE_DIR=/usr/include/eigen3

I don't know conda that well, but I expect that one should use the boost feedstock and eigen feedstock ?
I'm going to try asap.

@lorepirri I've submitted a PR to conda forge for an updated recipe.

Hi, I have not unvendored wdm or vinecopulib because (a) we are authors for those libraries, and (b) they are far less useful without their python interface :)

Another reason which makes it hard to unvendor vinecopulib: we extract the doctstrings (docstr.hpp) from the C++ headers using pybind11's mkdoc. So it is important that the version of vinecopulib and that of pyvinecopulib are properly synced.

LGTM. Though a couple things to consider: They just updated to 0.6.6 last week. We may want to cap the numpy version <2 to help migration (not required though).

@ryanskeith I was too quick merging it, apologies.
The update to 0.6.6 is mostly to un-vendor eigen and boost, and a couple of changes in src/main.cpp and src/docstr.hpp. See https://github.com/vinecopulib/pyvinecopulib/compare/v0.6.5...v0.6.6
In the next version I'll add the upper bound to numpy, thanks!


[riverpod_lint] prerelease custom_lint version

Describe the bug
The lastest riverpod_lint (2.3. 9) has a new version from Feb 4 with custom_lint dependency bumped
but the prerelease of riverpod_lint (3.0.0-dev.4) doesn't have this change with the last version from Nov 27
To Reproduce
Install the prerelease of riverpod_lint
Install any other dependency that need custom_lint ^0.6.2
Example:
dev_dependencies:
  flutter_test:
    sdk: flutter

  custom_lint: 0.6.2
  riverpod_lint: 3.0.0-dev.4
  nilts: 0.12.1   #  <== For example

Resolving dependencies...
Because nilts 0.12.1 depends on custom_lint_builder ^0.6.0 and riverpod_lint 3.0.0-dev.4 depends on custom_lint_builder ^0.5.2, nilts 0.12.1 is incompatible with riverpod_lint
  3.0.0-dev.4.

Temporarily bypass the problem
dev_dependencies:
  flutter_test:
    sdk: flutter

  custom_lint: 0.6.2
  riverpod_lint: 3.0.0-dev.4
  nilts: 0.12.1

dependency_overrides:
  custom_lint_builder: 0.6.0
  custom_lint_core: 0.6.0

It will come in due time. I don't want to make a new prerelease quite yet


Chakra install enhancements

build and install with pip install from local source or directly from github
use pyproject.toml to describe the project attibutes and dependecies in a declarative way
install dependencies when installing the package
upgrade to protobuf 4.x
build proto file with setuptools-grpc instead of protoc; this removes the need of installing protobuf-compiler
fix imports from internal modules to be able to be called from anywhere, not only from the cloned repo root.
et_generator: add comm_size attribute to one_comm_send/recv_node

Thanks for enabling this feature, @danmih-ixia. Can you fix the merge conflict. I will also try this out and add more comments if any.

Hello, I met below error while building the code. Could you check this please?
python3 -m chakra.et_generator.et_generator\
    --num_npus 64\
    --num_dims 1

Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/Users/a./anaconda3/lib/python3.11/site-packages/chakra/et_generator/et_generator.py", line 6, in
from chakra.et_def.et_def_pb2 import (
ImportError: cannot import name 'BOOL' from 'chakra.et_def.et_def_pb2' (/Users/a./anaconda3/lib/python3.11/site-packages/chakra/et_def/et_def_pb2.py)

I also figured out that et_generator works without Taekyung's two commits(a2b45c10fed84bae0515e706b74063dcf99d57d0, c236cfaeeff459cd508fb266b6e0e2b63dd44e87) in the middle.

@danmih-ixia , there is a failing build test. Could you please check?

Fixed the failing build test.


add note on how to get leptos_axum::ResponseOptions

lol I am unable to use GitHub properly until I drink some more coffee, apparently. Ignore the comment above, which was supposed to be a commit message -- I should've just use the GitHub editor to add this commit, but instead seem to have added it to your branch in a way that doesn't appear in the PR?
Thanks for your work on these concrete docs improvements. Much appreciated.


Support for more ZCL clusters (TZ-91)

I am interested to a Multistate Input, an Analog Input and a Power Configuration cluster, but these aren't supported yet.
Would be really cool if you could also implement this. (It is related to #6 but I don't know if I should reopen this issue or create a new one for a “cluster request”)

@JanUmbach It is better to create a new one issue for your new ZCL clusters support. We will consider to add those clusters in the next round release

@JanUmbach Just for curiosity, do you have any specific Zigbee devices that you need to those three clusters

@JanUmbach We will support power configure cluster and release this week. But for the rest of two are not mandatory for the base device, so we will put into the future plan but not this time. For details, you can refer to CSA document to check this list : 16-02867-021-PRO_BDB-ZigBee-3.0-Cluster-List.xlsx.


Add instead of Replace

It would be nice to add Administrators instead of replacing the existing set.

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

ID: c0c28c15-f0be-d732-4d9e-cf5df5e64e8b
Version Independent ID: 17eba45f-d200-e656-42b9-e1a512931eea
Content: Policy CSP - RestrictedGroups
Content Source: windows/client-management/mdm/policy-csp-restrictedgroups.md
Product: w10
GitHub Login: @MariciaAlforque
Microsoft Alias: maricia

The idea behind a restricted group is to enforce membership to only those in the list. This enforces the removal of a group member that was added in through any other method in order to, in part, satisfy compliance needs.
Hope this helps

While I see your point, it doesn't help our use case in particular. In our use case we are using Intune as our MDM and we want to adjust the local admins on a small subset of computers. During Autopilot enrollment, the user is added as Local Admin (we like this). But we also want to add another user (the IT Admin who works at that office building). When we use this to set another user it clobbers the existing user which we don't want. The workaround I see for this would be to create a separate policy for every workstation, but that adds more overhead than we'd like to spend on this task.

To my understanding, supporting a scenario like that is not the intent of this policy. Personal opinion: I would take a serious look at the wisdom of having users be admins.

I agree that having users as Admins isn't always Best Practice. But it's not a best fit for everybody and for our company it works best having them as Local Admins and we're not ready to make the change.
But since that's not the intent of this policy I'll just go ahead and close this.


Fix/responsiveness ipad view

PR
This PR resolves the issue 80

It fixes responsiveness issues on Ipad view( about-content section and the funder images).

Done @BatoolMM


Fix or Remove "bulk_pull_blocks"

The bootstrap request "bulk_pull_blocks" currently only sends a subset of blocks ("info") rather than a complete set;  Additionally, it is paginated in a way that requires sorting (min, max).
Currently nothing uses this primitive and so we could remove it, or, alternatively we could fix it.
In favor of fixing it:

It is very fast

In favor of removing it

It requires blocks to be sorted by hash value
After pulling in all blocks, the whole chain must be assembled and each frontier must be validated with the rest of the network

This ticket is a place to collect comments on how this should proceed.

Let's remove it.
Any calls to this should return empty set with the current semantics.
In a future release when we need a new slot we remove "bulk_pull_blocks" and replace it the new thing.


⚠ SceneTime has degraded performance

In 8af1a0b, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 3774 ms

Resolved: SceneTime performance has improved in ad53565 after 6 minutes.


Feature: log transformation progress

background
I have dump about 200G size.
So it takes a lot to process such file
proposal

write log to console every 30s or 1m progress in form like:

 processed <bytes_count> of <total_dump_bytes_count>

add cli option for log output format. formats: json (like now), and text for human readable logs

Hi!

Because nxs-data-anonymizer is used input data as stream (except a case when specified a real path to sql dump) it only can operate with processed count of bytes.

In commit faf540c0 was added requested feature. To adjust a behavior of logging progress new config options was added. See this in Readme for details.
For example, this config:
progress:
  rhythm: 2s
  humanize: true

will print into log info with count of read bytes every 2 seconds in human-readable format (i.e. 10MB instead 10485760).

Added cli option -l/--log-format to select desired log format (json and plan values are available, json by default).
In conjunction with first feature you may see something like this in your log:

[2023-08-30T10:17:27+00:00] INFO: program started
[2023-08-30T10:17:29+00:00] INFO: anonymization progress (read bytes: 6.989MB)
[2023-08-30T10:17:31+00:00] INFO: anonymization progress (read bytes: 14.09MB)
...
[2023-08-30T10:18:39+00:00] INFO: anonymization progress (read bytes: 322.8MB)
[2023-08-30T10:18:41+00:00] DEBUG: derived routine done (exit code: 0)
[2023-08-30T10:18:41+00:00] INFO: anonymization progress (read bytes: 372.4MB)
[2023-08-30T10:18:41+00:00] INFO: anonymizer routine done
[2023-08-30T10:18:41+00:00] DEBUG: freeing context
[2023-08-30T10:18:41+00:00] INFO: program terminating (exit code: 0)

Please check commit 8df5a702 (with both changes). It would be better to realize a new version with those features after your feedback.


DCR - Add Partition Key to CosmosDB (proposed for v4.2.0)

Goal
Enable the CosmosDB Provider to support developer defined Partitions. This is needed for 2 reasons:

Part of the maturity & credibility story around using CosmosDB. Developers expect access to the Partition keys.
Support (potentially) large bots.

Compatability
Any solution must have defaults that are back-compatable with v4.0.X bots. This means any new functionality needs to be either additive, a new switch of some time, or fully back-compat.
Proposal
Allow developers, on each request, to participate in the data flow and specify a partition key.
To accomplish this, the following DB related operations in CosmosDBStorage need to be updates:

DeleteAsync (C#), Delete (JS)
ReadAsync (C#), Read (JS)
WriteAsync (C#), Write(JS)

The proposal is to add a new class, PartitionedDocumentStoreItem, alongside DocumentStoreItem. To help insure compatability, this class would NOT be created using inheritence, and would instead simply be a new POCO/POJO.
private class DocumentStoreItem
{
    [JsonProperty("partitionKey")]
    public string PartitionKey { get; set; }
    [JsonProperty("id")]
    public string Id { get; set; }
    [JsonProperty("realId")]
    public string ReadlId { get; internal set; }
    [JsonProperty("document")]
    public JObject Document { get; set; }
    [JsonProperty("_etag")]
    public string ETag { get; set; }
}

interface DocumentStoreItem {
   partitionKey: string;
   id: string;
   realId: string;
   document: any;
}

DB Initialization
A new "usePartitions" flag is added to the CosmosDbStorageOptions POCO/POJO. If set, the database is initialized as having the partition key in the document collection set to the PartitionKey path.
var documentCollection = new DocumentCollection
{
    Id = _collectionId,
};
documentCollection.PartitionKey.Paths.Add("/partitionKey");

let docCollection = client.createCollection(
    databaseLink,
    { id: collectionId },
    (err2: any, collectionLink: any) => {
        if (err2) { return reject(err2); }
        resolve(collectionLink._self);
    });
docCollection.PartitionKey.Paths.Add("/partitionKey");

Developer Participation
Developers inherit from CosmosDBStore and override the GetPartitionKey method. This is called on every read/write, and allows the developer to specify an arbitrary string.
public overridable string GetPartitionKey(TurnContext context)
{
    return "someKey";
}

I'm starting to work on the C# implementation, but I'm still new to C#, so anybody can feel free to take it if this becomes a priority. Just a note: the Node implementation uses the new @azure/cosmos, replacing the deprecated documentdb. The equivalent on the .NET side is Azure Cosmos DB .NET SDK V3, which is still in prerelease.

Quick update: The C# Cosmos SDK doesn't currently support non-partitioned databases at all, which breaks backwards compatibility. They're supposed to be releasing an update that allows for this "soon," but it has stalled progress on the C# port. See https://github.com/Azure/azure-cosmos-dotnet-v3/issues/5

As an update: We've got PRs in both the C# and JS repos for this fix:
JS [860] (https://github.com/Microsoft/botbuilder-js/pull/860)
C# [1537] (https://github.com/Microsoft/botbuilder-dotnet/pull/1537)

Done in both C# and JS. Closing.


UDP communication fails with STM32H743zi Nucleo and Zephyr

Hi,
I'm trying to get the int32_publisher example working on the H7 over Zephyr. The serial example works great.

Hardware description: Nucleo STM32H743Zi .  I do not see the board on nmap or my router page. Nor I'm able to ping

Additional information

The Serial example works great.
I do not get the board up in the udp example. Is there a way as to what is going on the H7 when the board is running(a uart console maybe)
(edit) I made sure the hardware works by loading a test software from STM32 that a host can ping.

Which are the assigned IP addresses of your board and PC where the agent is running?

Board is at <IP_ADDRESS>
PC is at <IP_ADDRESS>
Note that the board does not appear to be at the network at all .. if I do an nmap.

In that case, you need to configure the UDP4 transport to connect with the <IP_ADDRESS>, because the agent will be listening there:
ros2 run micro_ros_setup configure_firmware.sh int32_publisher -t udp -i <IP_ADDRESS> -p 8888

I'm having no luck.
The issue is that the board does not seem to get on the network at all. I'm unable to see the board get on the network.
Has anyone got a board with an H7 with UDP working?

Still having no luck with this setup.
The issue seems to be
 Failed status on line 122: 1. Aborting
which is the below line in main.c(I have some debug code, so the line no. may not match the current git for int32_publisher)
RCCHECK(rclc_support_init(&support, 0, NULL, &allocator));
When I debug, via Jlink/openocd, the hang up is here:
 bool received = wait_session_status(session, create_session_buffer, ucdr_buffer_length(&ub), (size_t) retries);
under:

Things I have tried:

I do start the agent first.. which seems to be a requirement.

I have tested Zephyr only code (samples/net/sockets/echo and samples/net/dhcpv4_client). Both work well.

Update:
Was not able to debug much today. For some reason I was unable to set a breakpoint at that location, which is weird.
With v6

With this agent output, we can say that your client is not connecting to the agent at all. Please check the network as I have mentioned previously.

Any update on this?

Yes, I'm was able to get ahead a little bit. There appears to be some issue with the Socket file descriptors at startup. Once I get an example(int32_publisher) in a working state, I'll update here.

Hello.. thanks for waiting.
PR: https://github.com/micro-ROS/zephyr_apps/pull/53
I've got this working some time back and have a PR.

Before building make sure the agent IP(the PC you are running the agent on) is listed in microros_extensions/microros_transport.h
static zephyr_transport_params_t default_params = {.ip = "<IP_ADDRESS>", .port = "8888"};
Microros can also do auto-discovery of an agent, but I've gone the static route.

Start the Agent:
docker run -it --rm --net=host  microros/micro-ros-agent:humble udp4 --port 8888  -v6

Build and load the firmware on the STM3274zi nucleo board.
On the uart console:

Connection to agent is shown below:

Start a ros2 instance
docker run -it --rm --net host -v /dev/shm:/dev/shm arm64v8/ros:humble

Echo the publisher topic
ros2 topic echo /zephyr_int32_publisher
Data will now be streaming in.

Cool, I'm closing and merging your PR


Language != locale

(Firstly, thanks for the great tool!)
I realise the list of languages you're using is from those supported by iTunes Connect (https://github.com/KrauseFx/snapshot/issues/45) but those codes are not valid ones to pass to AppleLanguages and AppleLocale.
The examples from the documentation are "de" for AppleLanguages and "fr_FR" for AppleLocale. Snapshot is using "de-DE" and "fr-FR" respectively.
Maybe for languages you could strip the second part if it's identical (so "de-DE" becomes "de", but we keep ones like "pt-BR"). And for locale, simply convert the dash to underscore.
Another issue is that you have "cmn-Hans" and "cmn-Hant" in your list but I believe AppleLanguages expects "zh-Hans" and "zh-Hant".
Cheers,
Nick

Hello everybody.
I experienced the same problem. Changing "de-DE" to "de" and "fr-FR" to "fr", made the app show the string in the expected way.
I had also to do the change for Chinese (cmd vs zh).
I hope you're going to find a solution to this issue.
Thanks a lot!

Hey, sorry for not replying earlier on this issue.
So all I have to change is to pass the locale on the instruments command, which is generated by removing the second part, but only if the first and second parts are the same?
Have you tried this?

PR #131 resolves this for us, but it needs added to the documentation so people know it exists, what it is for, and how to use it

I´m facing a similar problem, even i i just set the language code as for example : 'it'
i´m not able to get the localized string for that language
I´m using the NSLocalizedString
As a note: this only happens with snapshot, if i pass a launch param from xcode like : -AppleLanguages (it) or if i change the language in the simulator or device, NSLocalizedString returns the correct value

I just released snapshot 1.0, please follow the migration guide.
Since the underlying snapshot was completely rewritten, I'm closing this issue now. Feel free to submit a new issue if you're experiencing an issue :+1:


sensors unavailable

I must be doing something wrong but i can see the messages arrive when i listen with MQTT but the sensors remain unavailable.
Message 107 received on go-eController/*/isv at 09:48:

Added a / in front of the prefix and it seems to work


New package: RareWares.LAME version 3.100.1

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Is there a linked Issue? Resolves https://github.com/microsoft/winget-pkgs/issues/153522

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@microsoft-github-policy-service agree

Apologies for the two force pushes, I found some minor issues I wanted to touch up. 😄

Automatic Validation ended with:

Executable C:\Users\validator\AppData\Local\Microsoft\WinGet\Packages\RareWares.LAME__DefaultSource\lame.exe returned exit code: 1
Executable C:\Users\validator\AppData\Local\Microsoft\WinGet\Links\lame.exe returned exit code: 1
Executable C:\Users\Validator\AppData\Local\Microsoft\WinGet\Packages\RareWares.LAME__DefaultSource\lame.exe returned exit code: 1
Executable C:\Users\Validator\AppData\Local\Microsoft\WinGet\Links\lame.exe returned exit code: 1

(Automated response - build 880.)

Apologies for the two force pushes, I found some minor issues I wanted to touch up. 😄

No worries. It's pretty much just robots pushing these PRs around. I like to think of this space as similar to a laundromat, and nobody mentions if you stop and restart your dryer a couple of times.

Verify:


Scroll state is not retained

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

Go to 'Home'
Click on 'Open pdf'
Scroll down to 'any page'
Rotate the screen
See error which is the scroll state is not retained and scrolling to the initial state

Expected behavior
While rotating the screen if the user scrolled down from first page to any other page expected to retain the page on rotation event.
Smartphone (please complete the following information):

Device: Samsung s10 Lite
OS: Android

Hi, Thank you for using this library. Above issue has been fixed in latest version.
https://github.com/afreakyelf/Pdf-Viewer/releases/tag/v2.0.1


chore: convert devMode to standard spec format using metadataTransd…

Awesome project, just have a try.
fix: https://github.com/alibaba/lowcode-engine/issues/283

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

there are 3 metadataTransducers ahead of the builtin one which registered in ComponentMeta, so it not the perfect location to compact devMode, see below:

I suggest registering a brand new metadataTransducer which has high level like 2, not the default 100. pseudo code: registerMetadataTransducer(compact, 2), so the subsequent metadataTransducers could use the compatible devMode value.
refs:

https://github.com/alibaba/lowcode-engine/blob/develop/packages/editor-skeleton/src/register-defaults.ts
https://github.com/alibaba/lowcode-engine/blob/develop/packages/designer/src/component-meta.ts

and plz set the target branch to develop other than main.
see: https://github.com/alibaba/lowcode-engine/tree/main#-participation

Should I convert all the devMode of component-meta fixtures to uppercase? They are causing type errors in tests.

Should I convert all the devMode of component-meta fixtures to uppercase? They are causing type errors in tests.

Actually it would not throw error while running tests, so it called compatible way to solve this issue.
But it's better to modify the legacy typo to prevent misleading users who learn from test cases.

@fxxjdedd Could u check the review comments?

target branch should be develop;
rename legacyIssues;
restore @ts-ignore;

@LeoYuan
Couldn't find any comments about 'rename legacyIssues', are you sure you have commented?
And what name do you prefer?

@LeoYuan Couldn't find any comments about 'rename legacyIssues', are you sure you have commented?  I'm still struggling moving the metadata transducer's tests to editor-skeleton, it will take some time to complete all the tests (includes all the default transducer).

Grrrrrrreat, this PR has been merged already. Feel free to open another one plz.😃


On the Create Project window, the project icon fades

Hello there
I've been investigating this issue, but I haven't found any options to fix it without changing the entire color scheme.
Moreover, I've found a tons of examples where this occurs in other themes including official Microsoft theme packages.
Examples:

Darcula

Dark+

Monokai

I assume this is in order to make the icons more contrasting than the background. I guess it's supposed to be configurable somewhere deep in the API, but that's beyond the scope of this extension.
If in the future there is an opportunity in the theme development tools to fix this, I will do it. Unfortunately, at the moment everything will remain as it is.

You're right. Why don't you give feedback to Microsoft? I'm tired of them and don't want to give feedback anymore.


testing user mutexes

project was the result of a meeting with dave yesterday. goal is to try to help students who submit eg:
void mutex_lock(struct mutex *mp)
{
    while (!m->free) { continue; }
    m->free = false;
}

most of the infrastructure for handling this are already in place, just not "turned on" in the right way.

need to identify data races within mutex_lock (to learn to insert pps on m->free accesses). what currently happens is that all these accesses are "trusted" -- mp is already held for purposes of DR, so no DR will be identified.

Instead, must add a mode to not "trust" them (i.e. move lockset_add from user_mutex_lock_entering case to user_mutex_lock_exiting case instead.).
Then, make this configurable so it only happens for the mutex_lock calls in test program's main() (i.e., NOT the ones in thr_create etc).

Need to connect the user-yield-blocking logic with the infinite-loop detector (PROGRESS_TRIGGER_FACTOR) to recognize "xchg-continue" style loops WITHOUT atomic accesses.

OPTIONAL ENHANCEMENT: Distinguish "we think user-busy-blocked" from "we are sure it is blocked". If "all threads wedged" situation arises, then try running the "we think blocked" threads again. This allows us to handle the situation where a long-running (but not infinite/busy) loop triggered progress sense, we won't report it as a deadlock. (Issue #75)
Allow for counting infinite loops when there's a DR PP in the middle (issue #88). Except, when not counting xchgs, maybe this just means using PROGRESS_DEPTH_FACTOR instead of PROGRESS_TRIGGER_FACTOR.

This works.


RBAC: Support Keycloak

Which version of the app are you running?
latest
Is your proposal related to a problem?
Kafka-ui RBAC
Describe the solution you'd like
We are running the Openshift AMQ Stream Kakfka Cluster with OAuth authentication and Authorization using Red Hat SSO i.e Keycloak
we want to use Kafka ui with to access Kafka cluster with authorization enabled via Red hat SSO i.e keycloak
Users with certain ACL permission are allowed access to the broker's resource i.e topic read, create, etc
I see we already have support for RBAC for kafka ui but this is only for oauth_google, oauth_github, and oauth_cognito providers. Is there a plan to support other providers like Azure AD or Keycloak?
Provider: oauth_AzureAD or Oauth_Keycloak
This will allow kakka-ui to integrate with the Red hat SSO and ready users or client role/group or permission
Kafka-ui users should login with keycloak cred and should only see resources they have access to see

Hey, thanks for the suggestion. I was about to create one myself once I've seen your feedback in #753 :)
We have LDAP/LDAP_AD planned already and we'll do the keycloak for sure.

@Haarolean
Just for more clearification. We want to use the same ACL authorization from Kafka to authrorize users to the Kafka ui. A proposed solution might be take the principal from the authentication mechanism i.e Oauth from the Kafka ui and propagate that same principal when making a request to the Kafka broker with authorization enabled.

I think Principal Propagation means re-authenticating Kafka UI with the broker at every client/user authentication with the Kafka UI. That doesn't sound like an Ideal or optimal solution probably difficult to implement in my opinion but a better workaround could be to authenticate and authorize the Kafka UI and the broker with a super user and then apply RBAC between Kafka UI and OAuth clients/users using keycloak client Authorization.
All the Kafka UI RBAC configurations like Resource, scope, permission, and policies should be managed in Keycloak and not in the Kafka UI container using the keycloak client authorization. This will allow keycloak to serve as a centralized manager for all authentication and authorization for the KAFKA UI
@Haarolean

@sookeke let's raise a separate issue for this. We'll implement a keycloak extractor within this task, like we have one for oauth2.

@Haarolean right and hopefully the role config will be stored and managed in keycloak other than in Kafka UI

May I suggest making generic OIDC support instead to support a wider scope of identity providers. Most OIDC providers support adding roles to the access token by adding a "groups" scope or Keycloak may provide roles by default in the "realm_access.roles" claim. It could be configurable which claim to use for the groups.

@jasmdk This is what is planned actually. Most likely #2844 would be enough.

Implemented a generic oauth provider within #2844.
Comment here or raise a new issue if you have any further questions.


Added -e to ps

On my Android 9, ps without -e shows only sh and ps

On Android 10 -e option is also required, but on Android 6 cannot be included, otherwise processes are not listed... added variable on top which specifies which command lists all processes. Tried using busybox which would be a common approach for all Android devices, but doing busybox ps | grep frida-server also lists grep in the running processes which complicates it a bit


Parametric shapes

fix for RooParamatricShapesBinPdf.
still needs some testing for the correctness of the outcome, but the PR may be useful has starting point for the future.
Idea: pointers are not saved in the Workspace, therefore when loaded again are not valid.
This minimal changes, make it mutable (because evaluate is const), and when it needs to be used, if not properly initialized, initialization is performed.

Hi Andrea,
Thanks for this PR. It would be nice to have some check that it still gives
the same results as you say before merging.
For example, its probably enough just to make a comparison as was done
using a simple RooExponential for the documentation :
https://cms-hcomb.gitbooks.io/combine/content/part2/settinguptheanalysis.html#caveat-on-using-parametric-pdfs-with-binned-datasets
On Mon, Feb 12, 2018 at 5:38 PM, Andrea Marini<EMAIL_ADDRESS>wrote:

fix for RooParamatricShapesBinPdf.
still needs some testing for the correctness of the outcome, but the PR
may be useful has starting point for the future.
Idea: pointers are not saved in the Workspace, therefore when loaded again
are not valid.
This minimal changes, make it mutable (because evaluate is const), and
when it needs to be used, if not properly initialized, initialization is
performed.
You can view, comment on, or merge this pull request online at:
https://github.com/cms-analysis/HiggsAnalysis-CombinedLimit/pull/454
Commit Summary

scope specification
fix pointers in ParametricShape

File Changes

M interface/RooParametricShapeBinPdf.h
https://github.com/cms-analysis/HiggsAnalysis-CombinedLimit/pull/454/files#diff-0
(2)
M src/RooParametricShapeBinPdf.cc
https://github.com/cms-analysis/HiggsAnalysis-CombinedLimit/pull/454/files#diff-1
(2)
M src/SequentialMinimizer.cc
https://github.com/cms-analysis/HiggsAnalysis-CombinedLimit/pull/454/files#diff-2
(2)

Patch Links:

https://github.com/cms-analysis/HiggsAnalysis-
CombinedLimit/pull/454.patch
https://github.com/cms-analysis/HiggsAnalysis-
CombinedLimit/pull/454.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cms-analysis/HiggsAnalysis-CombinedLimit/pull/454,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABhK2whgtu_dfPO4dB4al0jatI2_jZK1ks5tUHcTgaJpZM4SCjdu
.

@amarini, I just started a new PR #493, which changes how RooParametricShapeBinPdf computes the integrals internally (uses RooAbsReal::createIntegral(), rather than the RooAbsReal::asTF(), which would not allow parameters to functions themselves).
Can you take a look and make sure this new branch still works for your use case (and if your original issue is still present?)?
Thanks!
Javier


failureStrategy: CONTINUE is not effective

the task 2 is not execute
dolphinscheduler v1.3.5

You got it wrong. FailureStrategy refers to whether the process instance continues to run in event of a task failure.The default is to continue. If the current task fails, the post-task cannot be executed.
你搞错了，FailureStrategy 是指在出现失败任务时，工作流实例是否继续运行。默认是继续的。如果当前任务失败，其后置任务是无法运行的。


Python smart navigation/auto-completion don't work anymore with 1.85.1

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.85.1
OS Version: Darwin arm64 23.2.0

Version : 1.85.1 (Universal)
Validation : 0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2
Date : 2023-12-13T09:48:06.308Z (il y a 3 jours)
Electron : 25.9.7
ElectronBuildId : 25551756
Chromium : 114.0.5735.289
Node.js : 18.15.0
V8 : <IP_ADDRESS>-electron.0
Système d’exploitation : Darwin arm64 23.2.0

Steps to Reproduce:

start VScode,
open Python project in DevContainer,
we should be able to navigate into the code using Option key over a method/attribut/class.

But no navigation is now available. No autocomplete is available also.

It seems that the Pylance extension which was pre-loaded should be now explicitly loaded in devcontainer.json:
            "customizations": {
		"vscode": {
			"extensions": [
...
				"ms-python.vscode-pylance"
			],

Fixes the issue.

But Pylance is not working for a long time:
2023-12-16 16:38:29.580 [info] [Error - 4:38:29 PM] Client Pylance: connection to server is erroring.
write EPIPE
Shutting down server.
2023-12-16 16:38:29.585 [info] (1488) [FG] parsing: /home/vscode/.vscode-server/extensions/ms-python.vscode-pylance-2023.12.1/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 18ms] (604ms)
2023-12-16 16:38:29.765 [info] [Error - 4:38:29 PM] Server process exited with signal SIGKILL.
2023-12-16 16:38:29.769 [info] (1488) [FG] binding: /home/vscode/.vscode-server/extensions/ms-python.vscode-pylance-2023.12.1/dist/typeshed-fallback/stdlib/builtins.pyi (3877ms)
2023-12-16 16:38:29.783 [info] [Error - 4:38:29 PM] Connection to server got closed. Server will not be restarted.
2023-12-16 16:38:29.786 [info] [Error - 4:38:29 PM] Stopping server failed
2023-12-16 16:38:29.786 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-12-16 16:38:29.788 [info] [Error - 4:38:29 PM] Stopping server failed
2023-12-16 16:38:29.788 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-12-16 16:38:29.788 [info] [Error - 4:38:29 PM] Stopping server failed
2023-12-16 16:38:29.788 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-12-16 16:38:29.788 [info] [Error - 4:38:29 PM] Stopping server failed
2023-12-16 16:38:29.788 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-12-16 16:38:29.788 [info] [Error - 4:38:29 PM] Stopping server failed
2023-12-16 16:38:29.788 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-12-16 16:38:29.788 [info] [Error - 4:38:29 PM] Stopping server failed
2023-12-16 16:38:29.788 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097

Normally Python intellisense is installed if the Python extension is installed. But it don't works and that is the bug.
The Pylance extension is always crashing (i guess because it is in conflict with the one installed by Python extension).


tests

[ ] for postman import

[ ] wrong url

[ ] working url with wrong params

[ ] save, not save

[ ] correct url

[ ] forms

[ ] data

[ ] json

[x] for content execute

[x] fail scenarios

[x] wrong input

[x] env/properties (env shound not consider)

[x] pass

[x] targets

[x] pass

[x] add url along with name

[x] windows target, linux target

[x] fail

[x] error message, with error range

closed https://github.com/cedric05/dothttp/pull/44


Issues and suggestions on building

Hi,
I am trying to contribute to this project (as I am using Xmonad and taffybar on Ubuntu) thus I am just throwing out suggestions and questions:

The stack and cabal building on Ubuntu is painful, I have played with it for some time and have no success. Later I figured out that I can already do apt install taffybar. Should we add this into the README?
I noticed that the travis CI build for stack 7.8 is always failing. Should we fix it? Or we can assume people should always do stack upgrade thus we can ignore the failure for that?

The apt package is out of date (which is partly my fault due to not having made a release in a long time).  A stack build will probably always be challenging due to the configuration system for taffybar.

It would be really nice to fix it.  It is failing for what seem to be strange cabal reasons that I haven't had time to track down.

Ok, so I have poked around and figured out that it seems like some haskell upstream changes break the building -- because the last PR which passed the CI is now breaking too. We can enable a field ignore failing in travis.yaml to ignore the stack 7.8 case, or someone need to dive deeper into the haskell stack.

A stack build will probably always be challenging due to the configuration system for taffybar.

As I mentioned elsewhere, it's not actually that hard. For the time being, it's simply a matter of depending on the git head version of dyre https://github.com/IvanMalison/dotfiles/blob/4a62c2c72a1296593f64a73dd82abb6f0746911c/dotfiles/config/taffybar/stack.yaml#L9
it has been working great for me over the last week.

#218 Could be relevant to this.
With that merged should be able to write a script that:

installs stack
install gtk2hsbuild tools using stack (possibly with --install-ghc)
installs taffybar using stack (possibly with --install-ghc)
creates the $HOME/.config/taffybar directory with starter stack, cabal and taffybar.hs files
builds the users taffybar

This would make taffybar much more approachable, and reduce the number of incoming issues about building (#207 #194 #193 #158 #156 #151 #5)

The stack and cabal building on Ubuntu is painful, I have played with it for some time and have no success. Later I figured out that I can already do apt install taffybar. Should we add this into the README?

#218 addresses this as best as possible for now. See #193 for further discussion on what could be done to make this easier.

I noticed that the travis CI build for stack 7.8 is always failing. Should we fix it? Or we can assume people should always do stack upgrade thus we can ignore the failure for that?

This was fixed a while ago.


error: migration:run is not a registered comman

I Got this after following the installation instruction.
node --version v8.10.0

@barak-haviv what is your node version?

same here,
adonis cli: 4.0.4
node: v9.10.1
npm: 5.6.0
on mac OS High Sierra - 10.13.2
Homebrew 1.5.13

@barak-haviv change
"version": "4.1",
to
"version": "4.1.5",
in package.json
and migration works, but with errors:
Knex:warning - Use async .hasTable to check if table exists and then use plain .createTable. Since .createTableIfNotExists actually just generates plain "CREATE TABLE IF NOT EXIST..." query it will not work correctly if there are any alter table queries generated for columns afterwards. To not break old migrations this function is left untouched for now, but it should not be used when writing new code and it is removed from documentation. Knex:warning - Use async .hasTable to check if table exists and then use plain .createTable. Since .createTableIfNotExists actually just generates plain "CREATE TABLE IF NOT EXIST..." query it will not work correctly if there are any alter table queries generated for columns afterwards. To not break old migrations this function is left untouched for now, but it should not be used when writing new code and it is removed from documentation. Knex:warning - Use async .hasTable to check if table exists and then use plain .createTable. Since .createTableIfNotExists actually just generates plain "CREATE TABLE IF NOT EXIST..." query it will not work correctly if there are any alter table queries generated for columns afterwards. To not break old migrations this function is left untouched for now, but it should not be used when writing new code and it is removed from documentation.

@barak-haviv @2peter3 thanks. For the warnings, it's from a knex lib used by @adonisjs/lucid. i don't know the cause but an issue has been raised  https://github.com/iamraphson/adonisjs-hackathon-starter/issues

@barak-haviv @2peter3 the warning is normal according to https://github.com/adonisjs/adonis-lucid/issues/304 so I will close this issue.

@iamraphson It's probably better to do as recommended, change migrations to:
   if (!this.hasTable('users')) {       this.createTable('users', table => {
to prevent the warning message.
As a sidenote sqlite can't consume your alter table command, since it's not supporting alter.
Lastly, to be able to run it out of the box you might want to add "sqlite3": "^4.0.1", to package.json


Better error message for network connect

Fixes  #18257
Relative comment: https://github.com/docker/docker/issues/18257#issuecomment-159959301
Use better error message when user want to connect container with same
name to one network, this can help avoid confusion.
Signed-off-by: Zhang Wei<EMAIL_ADDRESS>ping @thaJeztah @zhaoxpZTE, WDYT of this?

Thanks @WeiZhang555!

@thaJeztah updated. Final print:
Error response from daemon: Conflict. A container with name "test" is already connected to network dev1.

Cool, thanks @WeiZhang555! I left one more suggestion

@WeiZhang555 Question though, shouldn't we check the error, because it seems it might something else than just "the container is already connected" (see https://github.com/docker/libnetwork/blob/077b0764e4926509c9e6213ae7b110de48494810/network.go#L755) ?

@vdemeester good point!

@vdemeester Thanks for help reviewing.
I think the error has already been checked: https://github.com/WeiZhang555/docker/blob/net-err/daemon/container_operations_unix.go#L616-L623
As you can see, what we are expecting is libnetwork.ErrNoSuchEndpoint. Returning no error means there is container with same name already connected to this network; returning error other than libnetwork.ErrNoSuchEndpoint means some unexpected error happens, it will throw error out to its caller. So I think it's already handled appropriately. :smile:
Also ping @thaJeztah , code is updated, PTAL.

This is cool! Thanks! @WeiZhang555

@WeiZhang555 oh you're right :stuck_out_tongue:.

Thanks @WeiZhang555, LGTM
@vdemeester any concerns left here?
Tests are failing pending https://github.com/docker/docker/pull/18458, so this will need a rebase after that's been merged to fix the tests

https://github.com/docker/docker/pull/18458 was merged, so if you rebase, the tests should be green again

@thaJeztah nop, LGTM 🐢

Green is one of my favorite colors, let me do the rebasing to make it green :laughing:

LGTM


Copy hotfix

Fixes #422

Codecov Report

Merging #424 into master will increase coverage by 0.15%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #424      +/-   ##
============================================
+ Coverage     85.62%   85.77%   +0.15%
- Complexity     2278     2279       +1
============================================
  Files           159      159
  Lines          6829     6824       -5
  Branches       1026     1023       -3
============================================
+ Hits           5847     5853       +6
+ Misses          661      653       -8
+ Partials        321      318       -3

Impacted Files
Coverage Δ
Complexity Δ

...l/esciencecenter/xenon/engine/util/CopyEngine.java
77.62% <100%> (+0.85%)
62 <0> (+1)
:arrow_up:

...ecenter/xenon/engine/files/PathImplementation.java
82.85% <100%> (+1.27%)
16 <0> (-1)
:arrow_down:

.../esciencecenter/xenon/engine/util/JobExecutor.java
82.63% <0%> (-0.7%)
43% <0%> (-1%)

...nter/xenon/adaptors/ssh/SshMultiplexedSession.java
75.69% <0%> (+1.38%)
34% <0%> (+1%)
:arrow_up:

.../xenon/adaptors/scripting/SchedulerConnection.java
89.55% <0%> (+2.98%)
51% <0%> (+1%)
:arrow_up:

...nter/xenon/adaptors/ssh/SshInteractiveProcess.java
77.35% <0%> (+3.77%)
11% <0%> (ø)
:arrow_down:

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 a717d6f...4d62a01. Read the comment docs.


Branch Setup when branching for release

@joeloff FYI
@pranavkm does this just involve adding the Setup repo to the update script? Or do we have to do anything in the Setup repo too? Or the CI machine?

It's adding Setup to the list and making sure it branches correctly.

I doubt there's anything we'd would need to add for Setup.


Failed to parse source for import analysis because the content contains invalid JS syntax. If you are using JSX, make sure to name the file with the .jsx or .tsx extension.

When i change it to  Scene.jsx the error disappeared but the model does not render.

This is just your bundled, sind require *.jsx. As for loading, the glb needs to be inside public, practically all examples in Fiber docs went through gltfjsx, you can look up how it’s done there

ty

it returns *.jsx by default now


WOPI - Excel documents do not switch to edit mode when clicking on "Edit in Browser" button.

I have a WOPI service which returns in its CheckFileInfo all required data including:
"UserCanWrite": true,
"EditModePostMessage": true,
"UserCanNotWriteRelative": true,
"HostEditUrl": "https://domain.com/Home/Detail/fileId?action=edit",
"HostViewUrl": "https://domain.com/Home/Detail/fileId?action=view".
However, when WOPI returns the Excel in View mode, clicking on "Edit in Browser" button does not swhich the document into Edit Mode.
What could be the cause? Are we missing anything?

You’ve told the app to send a post message when the button is clicked (EditModePostMessage=true), so it’s sending that message when the button is clicked, and nothing else. If you’re not handling the message, then the button will appear to do nothing.
Either don’t use the post message by removing that property in check or add your own post message handling code and redirect to edit yourself. That’s what the post message is intended to enable.


Update collection folder and file names to match standard convention

Currently they're named /action/action.js for the Actions collection, it should be /actions/actions.js

Complete, commit e28e6ee16fcb9e63d021b26e6815584a4acaa523


Windows support?

Not sure whether this is something you guys care about, as I assume Brigade is an all-Unix shop, but it would be great if this tool supported Windows so that users in corporate environments (read: me) could share it with their coworkers.
Obviously this would require some fairly massive changes, so I understand if this isn't something you want to pursue.

I think it would be awesome if Overcommit supported Windows. The reality in the past was that since none of the core contributors to Overcommit used Windows, it was hard to justify adding support since no one would be there to support it.
Your contributions over the past few weeks suggest that you care about this tool.
If you are willing to research and explore what's involved in adding Windows support, drive the implementation, and maintain it, I would be willing to merge your pull requests. My hunch is that you would simply need to add some special cases to Overcommit's low-level git and process management helpers to get most of the way there.
Some known unknowns from my perspective (these may turn out to not be an issue, but as I don't use Windows I can't speak to them):

I'm not sure how Ruby threading support differs for Windows, so if we end up supporting parallelized hook runs this might get tricky (might have to just disable it for Windows)
I'm not sure how Windows handles process signals, so a lot of the logic we have in place for gracefully handling Ctrl-C (which sadly doesn't have any tests) might need to have an alternate Windows implementation
I'm not sure if there are any gotchas with Process.detach and Process.spawn on Windows. Specifically whether Overcommit::Utils.execute_in_background will work
We use the childprocess gem to manage reading standard out/error streams and obtaining exit codes of processes. I'm not sure if our use of the gem is cross-platform compatible, so there might be some work required in the Overcommit::Subprocess helper class

In light of the above, there's probably going to need to be some work to add more tests verifying the existing behavior of Overcommit so we ensure existing functionality isn't broken once we start going down this path.


bug:

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
hello, I have upgraded to the latest version and captcha does not work it does not generate any events
Expected Behavior
No response
Steps To Reproduce
No response
Exceptions (if any)
No response
.NET Version
No response
Anything else?
No response

not run  OnValid="@OnValid" event
<Captcha GetImageName="@GetImageName" @ref="Captcha" OnValid="@OnValid" />
private void OnValid(bool ret)
{
if (ret)
{
DisablePostButton = false;
StateHasChanged();
}
}

@Intekai  use OnValidAsync


Some places in Japan gives country support error message.

I'm trying to do this:

Add my neighborhood addresses

I expected to happen this:

Form to be working as I see in other area

But here's what actually happened

The editor gives the following message. 'Sorry, Address editor in this country (ISO code:) does not support yet.'

How to reproduce

Go to https://yuiseki.github.io/osm-address-editor-vite/#16.72/34.385708/133.780792
Click one of buildings with colors

Other notes

I see the same errors in several islands. I don't see them when I browse non-islands.

I also found this problem. I ignore first, but it can be reproduce.
Looks like this problem is not only in Japan, it can be triggered in other countries as well.
https://yuiseki.github.io/osm-address-editor-vite/#16.1/39.056308/118.45919

I am as confused as you are now, let's look forward to the author's reply together.


chore: fix markdown in the bug report template

Before

After

🚀 Thank you for your contribution! 🚀


update the document on protocol methods for non-azure libraries

Fixes https://github.com/Azure/autorest.csharp/issues/4481
Description
Add your description here!
Checklist
To ensure a quick review and merge, please ensure:

[ ] The PR has a understandable title and description explaining the why and what.
[ ] The PR is opened in draft if not ready for review yet.

If opened in draft, please allocate sufficient time (24 hours) after moving out of draft for review

[ ] The branch is recent enough to not have merge conflicts upon creation.

Ready to Land?

[ ] Build is completely green

Submissions with test failures require tracking issue and approval of a CODEOWNER

[ ] At least one +1 review by a CODEOWNER
[ ] All -1 reviews are confirmed resolved by the reviewer

Override/Marking reviews stale must be discussed with CODEOWNERS first

FYI @annelo-msft the doc link change is extracted from the other PR and merged here

Thanks, @ArcturusZhang!


Add troubleshooting tips for hostprocess containers 'failed to create user process token' error during container creation

Signed-off-by: Mark Rossetti<EMAIL_ADDRESS>
/sig windows
/assign @brasmith-ms @jsturtevant @dcantah

/lgtm

/lgtm
for sig-windows

/approve


Great Ideas if it is possible. Would greatly appreciate. -TLR

I think that everyone would agree, that if it were possible for you to create either a way for multi pin drops for scan locations, Also selecting different radius scans after login, for each pin drop as well. Each pin drop can be from a single account or multiple accounts. For instance, each pin before selecting it, you can select from a drop box of which user account you want to use. It can be the same account, or another account. (I have had success running 3 instances on one account with the current update.) When the pin is dropped, you can then adjust the radius settings under Example:  Pin 1. Settings, Pin 2 settings, Pin 3 settings, Pin 4 settings. Each pin has settings that would allow each pin to do specific things. Also, please note that the colors in my opinion would be amazing if they went from green to blue to green to blue, so we know that certain area is indeed being scanned for sure. First circle green, second blue, third green and so on... The reason for this is because if any pins get moved by chance, it causes an ugly overlay that is very difficult for us to see what we are scanning and if it is still scanning.
I think it would a really great idea if you could put in a feature that would allow a change from a circle pattern to a block pattern. a line that goes across, and then down and then across and so on. Lastly It would be amazing if the scanned area would turn to yellow after 10 seconds, instead of us waiting for color changes for too long. Just to let us know that the area was scanned and that the rest is being scanned. After the first scan, it would be very nice that all the colors drop off the map as soon as the scan starts up again. It would look much cleaner. These are my ideas please feel free to have input. -TLR

You may want to split these up into one item per issue for ease of tracking. Also, some of your requests, like radius, coloring, block pattern, etc are backend things that would need to be implemented on the map repo. You could raise them on MrChristopher's, but I think it'd be more useful to everyone to post them here: https://github.com/PokemonGoMap/PokemonGo-Map/issues


(PUP-7983) Enable testing system openssl linked PA on RHEL7 in CI pipes

Update openssl package to desired version on RHEL7 hosts since the default
version installed in images used by CI/VMPooler are not compatible with
agent setup and operation causing failures. Note that PA is built on centos7
which is also used to test on rhel platforms.
Related to PA-1580 (part of epic PA-1608). Has been tested in PA CI - logs would be attached to PR for PA-1264 (enables linking PA against system openssl).
This does not impact regular agent build using vendored openssl which disregard system
openssl.

CLA signed by all contributors.

I also pushed changes for PUP-8044 as part of this PR. That is because these changes to upgrade openssl on rhel7 are pre-requisite for the changes in PUP-8044.

What are you aiming for here?  As a feature branch it's fine.

I will be closing this PR. The way of detecting FIPS platforms and the custom actions based off it is anyway going to be different. Per discussions with the platform os team and others it was deemed that using actual platform names to denote FIPS was best long term approach. In addition, it was decided that the FIPS platforms would actually be FIPS enabled and hence will obviate the need for moving to FIPS mode from within scripts (PUP-8044).
Also we do want all acceptance tests enabled, after updating relevant ones to be FIPS compatible, when testing in FIPS mode. Their removal was temporary; that experimentation should not have been part of this PR.


Fix fast debounce validation

Coverage remained the same at 92.672% when pulling 9be5ab9fbf286f64e8bc99c63150f52e63de9c33 on fix_fast_debounce_validation into 3052d7c085a0d30465115aaef4fc2272aeed6658 on dev.

Coverage remained the same at 92.672% when pulling 9be5ab9fbf286f64e8bc99c63150f52e63de9c33 on fix_fast_debounce_validation into 3052d7c085a0d30465115aaef4fc2272aeed6658 on dev.


Triple pattern translation

I still need to do a last thorough check to compare with the rules on the paper, but this should be very close.

In addition to the comments in my review, I was also thinking whether the translateTriplePattern function should produce not only the Cypher query but also some data structure needed to interpret the result records after executing the Cypher query and converting these result records into solution mappings. However, I would say that you first complete this PR here, and after it is merged, you can think about extending the code to produce such a data structure.

In addition to the points in my review, I also notice that there are still some unmap... functions in the LPG2RDFConfiguration interface where the argument is of type String but should be Node.
Also, the JavaDoc comment in lines 22-23 is not entirely correct: i) the input is not a node id and ii) the output may be a blank node instead of an IRI.

As the next PR, extend the code of this one to produce not only the Cypher query but also some data structure needed to interpret the result records after executing the Cypher query in order to convert these result records into solution mappings.