@azure/data-tables support $top operation

Hi,
wanted to ask if library support $top operation in listEntities?
Because I would like to use log tail pattern
https://docs.microsoft.com/en-us/azure/storage/tables/table-storage-design-patterns
Regards,
Adam.

@AdamMachera thanks for reaching out. The way you can achieve this is by querying the table and setting the maximum number of items per page to N and just retrieving the first page. Something like this:
// Items are returned in pages by the Table service, we'll use this to limit the max
// number of items per page.
const top = 10;

// Initialize the Table client. Replace CONNECTION_STRING and tableName
const client = TableClient.fromConnectionString("CONNECTION_STRING", "tableName");

// Create the query
const entitiesIterator = client.listEntities({
        // This is optional in case you need to set a query filter.
        queryOptions: { filter: "<Query>" }
      });

// Here we'll store the top N items
let topEntities  = [];

// entitiesIterator is an async iterator so you can do for await to fetch each paged result.
for await (const page of entities.byPage({ maxPageSize: top /*This limits the size of the page*/})) {
     topEntities = [...page];

     // We break so that we just get the first page of at most 10 (top) elements. This will only send one request to the service
     break;
}

I hope this helps, please let me know if you have any questions

@AdamMachera thanks for reaching out. The way you can achieve this is by querying the table and setting the maximum number of items per page to N and just retrieving the first page. Something like this:
// Items are returned in pages by the Table service, we'll use this to limit the max
// number of items per page.
const top = 10;

// Initialize the Table client. Replace CONNECTION_STRING and tableName
const client = TableClient.fromConnectionString("CONNECTION_STRING", "tableName");

// Create the query
const entitiesIterator = client.listEntities({
        // This is optional in case you need to set a query filter.
        queryOptions: { filter: "<Query>" }
      });

// Here we'll store the top N items
let topEntities  = [];

// entitiesIterator is an async iterator so you can do for await to fetch each paged result.
for await (const page of entities.byPage({ maxPageSize: top /*This limits the size of the page*/})) {
     topEntities = [...page];

     // We break so that we just get the first page of at most 10 (top) elements. This will only send one request to the service
     break;
}

I hope this helps, please let me know if you have any questions

Is there any plan to support "$top" operation?

The above code works, but when running under Jest, Jest detects an open Handle. Does a connection need to be closed?


Library problem

Dear Plux team.
I am trying to run the OneDeviceAcquisitionExample.py with the biosignalPlux device, and I have the problem with the library plux.
Maybe I didn't see well but I don't know how to install this library "plux". I tryed pip install plux but in https://pypi.org this library it is not related to this project.
also the other libraries: bitalino and biosignalsnotebooks does not seems to funtion with the example.
How could I solve the problem?
In advance thanks so much.
Joaku
PD. I am trying to use the the example

Hello,
Sorry for the late response. What OS and python version are you using? The library is not available in the pipit repository, but inside the PLUX-API-Python3 folder for the different OSs.
Best regards


gutrunks why did you change the controller?

Why did you change the controller and removed the Z position correction an rotation implementation? O.o

I changed nothing on the controller. Just added glut, camera component and a ton shader (that needs some tweaking and is completely commented) touched nothing else anywhere. Not even a call to what I did.

And regarding the z position, I used it for the camera, why would I change in in the controller. Anyway, I'm sorry if it happened from my commit, but it shouldn't have.

No probs :) i'll recommit after i see what happened there :) you probably haven't updated my last commit and that's why it they got erased :)

More that likely. Sorry again. Just mentioned I made no changes to those so you don't try to look for anything extra. Thanks again for the heads up.

Psst...could you recommit? apparently the component camera file and the tronshader.cpp one are not found by visual. And i can't find them either in the components folder... :)

Will do... But I'm not at my computer right now. But I'll do it when I can and I'll be sure to not mess it up this time

also: glut32.lib is missing...be sure to upload that as well :P


Managing Interactive Challenges in Recaptcha v3 Integration

Some recaptcha v3 requires interaction to access https://www.google.com/recaptcha/enterprise/reload, such as clicking some buttons. Simply waiting doesn't make sense. How should I handle this type of recaptcha v3 with your program?

In that case, you can just initialize the solver and click the button. Here is an example:
from playwright.sync_api import sync_playwright
from playwright_recaptcha import recaptchav3

with sync_playwright() as playwright:
    browser = playwright.firefox.launch()
    page = browser.new_page()
    page.goto("https://some-website-with-recaptcha-v3.com/")

    with recaptchav3.SyncSolver(page) as solver:
        page.get_by_role("button").click()

But in most cases, after clicking the button, the verification will be submitted directly, and the obtained reCAPTCHA token is invalid at this point.

If the button is a login button or something of that sort, you can simply abort the POST request to the login endpoint. Here is an example:
from playwright.sync_api import sync_playwright
from playwright_recaptcha import recaptchav3

with sync_playwright() as playwright:
    browser = playwright.firefox.launch()
    page = browser.new_page()
    page.goto("https://some-website-with-recaptcha-v3.com/")

    page.route(
        "https://some-website-with-recaptcha-v3.com/login",
        lambda route: route.abort()
        if route.request.method == "POST"
        else route.continue_(),
    )

    with recaptchav3.SyncSolver(page) as solver:
        page.get_by_role("button").click()
        token = solver.solve_recaptcha()


[ci] Fix pcre bump job

PR claimed by CI: https://ci.cryo.cf-app.com/teams/bosh-backup-restore/pipelines/backup-and-restore-sdk-release

PR merged by CI: https://ci.cryo.cf-app.com/teams/bosh-backup-restore/pipelines/bbr-sdk/jobs/merge-pr/builds/217


View panel does not stay at lesson list of student if user undoes a lesson operation command

Current implementation is to reset view panel during find operations, else no change to panel unless another view command is executed

Fixed in #276


feat(STONEINTG-171): add external secret for sync snyk token from vault

/retest-required

@gbenhaim could you please help to review it again?

/lgtm
/approve


make denseflow error.

libdenseflow.a(dense_flow_gpu.cpp.o): In function calcDenseFlowPureGPU(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int, int, int, int, std::vector<std::vector<unsigned char, std::allocator<unsigned char> >, std::allocator<std::vector<unsigned char, std::allocator<unsigned char> > > >&, std::vector<std::vector<unsigned char, std::allocator<unsigned char> >, std::allocator<std::vector<unsigned char, std::allocator<unsigned char> > > >&, std::vector<std::vector<unsigned char, std::allocator<unsigned char> >, std::allocator<std::vector<unsigned char, std::allocator<unsigned char> > > >&)': dense_flow_gpu.cpp:(.text+0x1b61): undefined reference to cv::cudacodec::createVideoReader(cv::String const&)'
collect2: error: ld returned 1 exit status
CMakeFiles/extract_gpu.dir/build.make:154: recipe for target 'extract_gpu' failed
make[2]: *** [extract_gpu] Error 1
CMakeFiles/Makefile2:141: recipe for target 'CMakeFiles/extract_gpu.dir/all' failed
make[1]: *** [CMakeFiles/extract_gpu.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 90%] Built target extract_warp_gpu
[100%] Linking CXX shared library libpydenseflow.so
[100%] Built target pydenseflow
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2

Hi, it seems you are not building this repo. There are no target named extract_warp_gpu

Thanks for your reply. Can you be more specific, or how to build this repo? I know less about it.

Hi, it seems you are not building this repo. There are no target named extract_warp_gpu

Thanks for your reply. Could you be more specific, or how to build this repo. I know less about it.

could you show the result of running git remote -v, and git branch --show-current and git rev-parse HEAD?

could you show the result of running git remote -v, and git branch --show-current and git rev-parse HEAD?

result of running git remote -v :
git remote -vorigin	http://github.com/yjxiong/dense_flow (fetch)
origin	http://github.com/yjxiong/dense_flow (push)
the result of running  git branch --show-current：
error: unknown option `show-current'
usage: git branch [] [-r | -a] [--merged | --no-merged]
or: git branch [] [-l] [-f]  []
or: git branch [] [-r] (-d | -D) ...
or: git branch [] (-m | -M) []
or: git branch [] [-r | -a] [--points-at]
Generic options
-v, --verbose         show hash and subject, give twice for upstream branch
-q, --quiet           suppress informational messages
-t, --track           set up tracking mode (see git-pull(1))
--set-upstream        change upstream info
-u, --set-upstream-to
change the upstream info
--unset-upstream      Unset the upstream info
--color[=]      use colored output
-r, --remotes         act on remote-tracking branches
--contains    print only branches that contain the commit
--abbrev[=]        use  digits to display SHA-1s
Specific git-branch actions:
-a, --all             list both remote-tracking and local branches
-d, --delete          delete fully merged branch
-D                    delete branch (even if not merged)
-m, --move            move/rename a branch and its reflog
-M                    move/rename a branch, even if target exists
--list                list branch names
-l, --create-reflog   create the branch's reflog
--edit-description    edit the description for the branch
-f, --force           force creation, move/rename, deletion
--merged      print only branches that are merged
--no-merged   print only branches that are not merged
--column[=

do you need to warp flows? or simply extracting flows is enough?
for flow extraction, you may clone and build this repo. there are instructions in the README, and also https://github.com/open-mmlab/denseflow/blob/master/INSTALL.md

do you need to warp flows? or simply extracting flows is enough?
for flow extraction, you may clone and build this repo. there are instructions in the README, and also https://github.com/open-mmlab/denseflow/blob/master/INSTALL.md

Thanks very much！


[Bug] Name of Menu button has a space in it

There's a space in the object name, which is not allowed in Appsmith.

Reduce the default width of the menu button to be smaller so that it can fit in tighter spaces and let the default text just be 'Menu' instead of 'Open menu'

There's no hover state for the menu button

The white colors look a bit weird. We might need color options here

@areyabhishek this issue has been solved in this PR https://github.com/appsmithorg/appsmith/pull/5970


three spinner bounce fix to make sure only one show timeout created

Previously if onBuffering was called twice (which was happening for me sometimes when playing a vod hls stream), 2 timeouts would be created, and then if onStop() was called within the timeout interval, only the first of the timeouts would get cleared. This would then cause the loading indicator to reappear.
This should fix this but I haven't built and tested it yet as having some issues npm installing due to windows path length issues.

Merged, thanks @tjenkinson!


Inconsistent OS listings on Downloads page

On http://git-scm.com/downloads I see:
Mac OS X    Windows
Linux   Solaris
Linux and Solaris both link to http://git-scm.com/download/linux, which has instructions for 4 Linux distributions, 2 BSDs, and Solaris.
Objective OS market share data is hard to find, especially for other than Mac/Windows/Linux, but some sources put FreeBSD as about 5x that of Solaris.
FreeBSD should likely be added there, or perhaps just have an "other" link?

FreeBSD already has instructions on this page, added through https://github.com/git/git-scm.com/commit/8ff988c5792f4ca92c1ac2ba96555843276dd884
should be closed @peff ?

The /download page has a link for Linux and for Solaris, but not other Unixes.  Even though the Linux and Solaris links go to the same page, which does have instructions for FreeBSD and others.
So we could add more links there, but I think it might make more sense to go the opposite direction, and give the Linux link more generic and inclusive text. PRs welcome.

Barring further substantive discussion, I think it's safe to close this issue.

https://git-scm.com/downloads still lists:
Mac OS X 	Windows
Linux 	Solaris
so from my perspective the issue still exists.
How about changing "Linux" and "Solaris" to a single "Linux/UNIX"?

@emaste Exactly, I think that is the right direction. Want to open a PR?

closing as it seems fixed from #1033


[Bug]: Cannot find module 'tsparticles' or its corresponding type declarations.

Contact Details
<EMAIL_ADDRESS>What happened?
I get the following errors:
Error: Module not found: Error: Can't resolve 'tsparticles' in 'apppath'
error TS2307: Cannot find module 'tsparticles' or its corresponding type declarations.
Same issue as https://github.com/matteobruni/tsparticles/issues/1683
import { MoveDirection, ClickMode, HoverMode, OutMode, Engine, Container } from "tsparticles-engine";
import { loadFull } from "tsparticles";
"typescript": "~4.7.2"
"@angular/core": "^14.2.0",
tsParticles Version
2.5.2
Which library are you using?
Angular (ng-particles)
tsParticles Configuration
/* or the classic JavaScript object */
  particlesOptions = {
      background: {
          color: {
              value: "#0d47a1",
          },
      },
      fpsLimit: 120,
      interactivity: {
          events: {
              onClick: {
                  enable: true,
                  mode: ClickMode.push,
              },
              onHover: {
                  enable: true,
                  mode: HoverMode.repulse,
              },
              resize: true,
          },
          modes: {
              push: {
                  quantity: 4,
              },
              repulse: {
                  distance: 200,
                  duration: 0.4,
              },
          },
      },
      particles: {
          color: {
              value: "#ffffff",
          },
          links: {
              color: "#ffffff",
              distance: 150,
              enable: true,
              opacity: 0.5,
              width: 1,
          },
          collisions: {
              enable: true,
          },
          move: {
              direction: MoveDirection.none,
              enable: true,
              outModes: {
                  default: OutMode.bounce,
              },
              random: false,
              speed: 6,
              straight: false,
          },
          number: {
              density: {
                  enable: true,
                  area: 800,
              },
              value: 80,
          },
          opacity: {
              value: 0.5,
          },
          shape: {
              type: "circle",
          },
          size: {
              value: { min: 1, max: 5 },
          },
      },
      detectRetina: true,
  };

What browsers are you seeing the problem on?
Chrome
Relevant log output
./src/app/pages/confirmation/confirmation.component.ts:2:0-39 - Error: Module not found: Error: Can't resolve 'tsparticles' in 'R:\hivepass\donate_hivepass_app\src\app\pages\confirmation'

Error: src/app/pages/confirmation/confirmation.component.ts:3:26 - error TS2307: Cannot find module 'tsparticles' or its corresponding type declarations.

3 import { loadFull } from "tsparticles";

Code of Conduct

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

Install the missing module.


Complete implementation of the original spec

Implement what is left of the specification document at https://docs.google.com/document/d/1PAyNCXjtzoTNIxVRqoNjURrtoFDl6SQPPr-azWngw-Y/edit . Mark things with [DONE] in the Google doc as you progress.
Create issues on github for TODOs and questions that have not been addressed yet.

Done.


:sparkles:kafka

 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.zhao 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.


Dankositzke2

Description
Expanded Royce and Matt's notebook to include an algorithm that suggests 5 mentees for each mentor.
Type of change

[x] New feature

Checklist:

[x] My code follows PEP8 style guide
[x] I have removed unnecessary print statements from my code
[x] I have made corresponding changes to the documentation if necessary
[x] My changes generate no errors
[x] No commented-out code
[x] Size of pull request kept to a minimum
[x] Pull request description clearly describes changes made & motivations for said changes

https://www.loom.com/share/25a96cf7d9bc4d6ea9f4f3f9872f1cea?sharedAppSource=personal_library

Nice work! Great thinking using Euclidean distance.

Impressive work


🐛 Unable to pip install editable version

mqt.qecc version
mqt.qecc 1.3.1
OS
20.04.1-Ubuntu
Python version
Python 3.10
C++ compiler
No response
Additional environment information
No response
Description
When I follow the build instructions at https://qecc.readthedocs.io/en/latest/DevelopmentGuide.html errors occur:
Specifically when I type pip install --editable .[dev] this error occurs (The project also doesn't install without using the editable mode):
  error: subprocess-exited-with-error

  × Building editable for mqt.qecc (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [156 lines of output]
      /tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/config/pyprojecttoml.py:66: _BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml` is still *beta*.
        config = read_configuration(filepath, True, ignore_option_errors, dist)
      running editable_wheel
      creating /tmp/pip-wheel-7cj88rx4/.tmp-kn816tck/mqt.qecc.egg-info
      writing /tmp/pip-wheel-7cj88rx4/.tmp-kn816tck/mqt.qecc.egg-info/PKG-INFO
      writing dependency_links to /tmp/pip-wheel-7cj88rx4/.tmp-kn816tck/mqt.qecc.egg-info/dependency_links.txt
      writing entry points to /tmp/pip-wheel-7cj88rx4/.tmp-kn816tck/mqt.qecc.egg-info/entry_points.txt
      writing requirements to /tmp/pip-wheel-7cj88rx4/.tmp-kn816tck/mqt.qecc.egg-info/requires.txt
      writing top-level names to /tmp/pip-wheel-7cj88rx4/.tmp-kn816tck/mqt.qecc.egg-info/top_level.txt
      writing manifest file '/tmp/pip-wheel-7cj88rx4/.tmp-kn816tck/mqt.qecc.egg-info/SOURCES.txt'
      reading manifest template 'MANIFEST.in'
      no previously-included directories found matching '**/apps'
      adding license file 'LICENSE'
      writing manifest file '/tmp/pip-wheel-7cj88rx4/.tmp-kn816tck/mqt.qecc.egg-info/SOURCES.txt'
      creating '/tmp/pip-wheel-7cj88rx4/.tmp-kn816tck/mqt.qecc-1.3.2.dev5+g97b9c9a.dist-info'
      creating /tmp/pip-wheel-7cj88rx4/.tmp-kn816tck/mqt.qecc-1.3.2.dev5+g97b9c9a.dist-info/WHEEL
      running build_py
      running build_ext
      -- The CXX compiler identification is GNU 9.4.0
      -- Detecting CXX compiler ABI info
      -- Detecting CXX compiler ABI info - done
      -- Check for working CXX compiler: /usr/bin/c++ - skipped
      -- Detecting CXX compile features
      -- Detecting CXX compile features - done
      -- Performing Test HAS_MARCH_NATIVE
      -- Performing Test HAS_MARCH_NATIVE - Success
      -- Could NOT find GMP (missing: GMPXX_LIB GMPXX_INCLUDE_DIR GMP_INCLUDE_DIR GMP_LIB)
      Did not find GMP. Using Boost multiprecision library instead.
      -- Boost.Multiprecision: standalone mode ON
      -- Using the single-header code from /home/pderks/Documents/phd/qecc/extern/qfr/extern/json/single_include/
      -- pybind11 v2.11.0 dev1
      -- Found PythonInterp: /home/pderks/Documents/phd/qecc/qecc_venv/bin/python3 (found suitable version "3.9.7", minimum required is "3.6")
      -- Found PythonLibs: /home/pderks/anaconda3/lib/libpython3.9.so
      -- The C compiler identification is GNU 9.4.0
      -- Detecting C compiler ABI info
      -- Detecting C compiler ABI info - done
      -- Check for working C compiler: /usr/bin/cc - skipped
      -- Detecting C compile features
      -- Detecting C compile features - done
      CMake Error at /tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/cmake/data/share/cmake-3.26/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
        Could NOT find FLINT (missing: FLINT_LIBRARY FLINT_INCLUDE_DIR)
      Call Stack (most recent call first):
        /tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/cmake/data/share/cmake-3.26/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE)
        cmake/FindFLINT.cmake:83 (find_package_handle_standard_args)
        src/CMakeLists.txt:32 (find_package)

      -- Configuring incomplete, errors occurred!
      Traceback (most recent call last):
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/command/editable_wheel.py", line 155, in run
          self._create_wheel_file(bdist_wheel)
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/command/editable_wheel.py", line 344, in _create_wheel_file
          files, mapping = self._run_build_commands(dist_name, unpacked, lib, tmp)
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/command/editable_wheel.py", line 267, in _run_build_commands
          self._run_build_subcommands()
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/command/editable_wheel.py", line 294, in _run_build_subcommands
          self.run_command(name)
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
          self.distribution.run_command(command)
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/dist.py", line 1244, in run_command
          super().run_command(command)
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/command/build_ext.py", line 84, in run
          _build_ext.run(self)
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 345, in run
          self.build_extensions()
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 467, in build_extensions
          self._build_extensions_serial()
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 493, in _build_extensions_serial
          self.build_extension(ext)
        File "<string>", line 94, in build_extension
        File "/home/pderks/anaconda3/lib/python3.9/subprocess.py", line 373, in check_call
          raise CalledProcessError(retcode, cmd)
      subprocess.CalledProcessError: Command '['cmake', '/home/pderks/Documents/phd/qecc', '-DCMAKE_LIBRARY_OUTPUT_DIRECTORY=/tmp/tmp2h4mezoc.build-lib/mqt/qecc', '-DPYTHON_EXECUTABLE=/home/pderks/Documents/phd/qecc/qecc_venv/bin/python3', '-DQECC_VERSION_INFO=1.3.2.dev5+g97b9c9a', '-DCMAKE_BUILD_TYPE=Release', '-DBINDINGS=ON', '-GNinja']' returned non-zero exit status 1.
      /tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/_distutils/dist.py:988: _DebuggingTips: Problem in editable installation.
      !!

              ********************************************************************************
              An error happened while installing `mqt.qecc` in editable mode.

              The following steps are recommended to help debug this problem:

              - Try to install the project normally, without using the editable mode.
                Does the error still persist?
                (If it does, try fixing the problem before attempting the editable mode).
              - If you are using binary extensions, make sure you have all OS-level
                dependencies installed (e.g. compilers, toolchains, binary libraries, ...).
              - Try the latest version of setuptools (maybe the error was already fixed).
              - If you (or your project dependencies) are using any setuptools extension
                or customization, make sure they support the editable mode.

              After following the steps above, if the problem still persists and
              you think this is related to how setuptools handles editable installations,
              please submit a reproducible example
              (see https://stackoverflow.com/help/minimal-reproducible-example) to:

                  https://github.com/pypa/setuptools/issues

              See https://setuptools.pypa.io/en/latest/userguide/development_mode.html for details.
              ********************************************************************************

      !!
        cmd_obj.run()
      Traceback (most recent call last):
        File "/home/pderks/Documents/phd/qecc/qecc_venv/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
        File "/home/pderks/Documents/phd/qecc/qecc_venv/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
        File "/home/pderks/Documents/phd/qecc/qecc_venv/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 273, in build_editable
          return hook(wheel_directory, config_settings, metadata_directory)
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 445, in build_editable
          return self._build_with_temp_dir(
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 401, in _build_with_temp_dir
          self.run_setup()
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 338, in run_setup
          exec(code, locals())
        File "<string>", line 102, in <module>
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/__init__.py", line 107, in setup
          return distutils.core.setup(**attrs)
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 185, in setup
          return run_commands(dist)
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 201, in run_commands
          dist.run_commands()
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands
          self.run_command(cmd)
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/dist.py", line 1244, in run_command
          super().run_command(command)
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/command/editable_wheel.py", line 155, in run
          self._create_wheel_file(bdist_wheel)
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/command/editable_wheel.py", line 344, in _create_wheel_file
          files, mapping = self._run_build_commands(dist_name, unpacked, lib, tmp)
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/command/editable_wheel.py", line 267, in _run_build_commands
          self._run_build_subcommands()
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/command/editable_wheel.py", line 294, in _run_build_subcommands
          self.run_command(name)
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
          self.distribution.run_command(command)
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/dist.py", line 1244, in run_command
          super().run_command(command)
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/command/build_ext.py", line 84, in run
          _build_ext.run(self)
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 345, in run
          self.build_extensions()
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 467, in build_extensions
          self._build_extensions_serial()
        File "/tmp/pip-build-env-bcf33gnq/overlay/lib/python3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 493, in _build_extensions_serial
          self.build_extension(ext)
        File "<string>", line 94, in build_extension
        File "/home/pderks/anaconda3/lib/python3.9/subprocess.py", line 373, in check_call
          raise CalledProcessError(retcode, cmd)
      subprocess.CalledProcessError: Command '['cmake', '/home/pderks/Documents/phd/qecc', '-DCMAKE_LIBRARY_OUTPUT_DIRECTORY=/tmp/tmp2h4mezoc.build-lib/mqt/qecc', '-DPYTHON_EXECUTABLE=/home/pderks/Documents/phd/qecc/qecc_venv/bin/python3', '-DQECC_VERSION_INFO=1.3.2.dev5+g97b9c9a', '-DCMAKE_BUILD_TYPE=Release', '-DBINDINGS=ON', '-GNinja']' returned non-zero exit status 1.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building editable for mqt.qecc
Failed to build mqt.qecc
ERROR: Could not build wheels for mqt.qecc, which is required to install pyproject.toml-based projects```

### Expected behavior

I expected to be able to run `pip install --editable .[dev]`

### How to Reproduce

Follow steps 1-7 at [https://qecc.readthedocs.io/en/latest/DevelopmentGuide.html](url) and then run `pip install --editable .[dev]`

Thanks for opening this issue. The error message says it all

Could NOT find FLINT (missing: FLINT_LIBRARY FLINT_INCLUDE_DIR)

You are missing the flint dependency that's required for building the project.
On Linux it's as easy to get as sudo apt-get install libflint-dev.
On macOS you can get it via brew install flint.
On Windows, you might have to install it from source: https://github.com/flintlib/flint2
IIRC @lucasberent has plans to remove this dependency in the future and replace it with something else.


Refactors deps

updates and refactors sui deps
remediates missing dependency warnings
removes unused deps (ie use of the module patternfly.table is the only reason to have any data tables deps)
improves readability of inter-dependency dependencies

Ones that are seemingly innocuous but required by other libs are grouped together and annotated as being related, the following links rather helpful in this work:
https://github.com/patternfly/angular-patternfly/blob/master/README.md
https://github.com/ManageIQ/ui-components/blob/master/package.json#L89
Cleans up some awkward (service-details) styling that was hidden by a magic bug, long story short, we require('bootstrap') but which didn't resolve due to the packages package.json (it doesn't have a root main)
see, look, its not broken, its the same!

Removed requires:

angular-datatables
angular-datatables/dist/plugins/select/angular-datatables.select
angular-file-saver
bootstrap
bootstrap-select
bootstrap-switch
bootstrap-touchspin
datatables.net-select/js/dataTables.select
datatables.net/js/jquery.dataTables

So.. what I'm still confused about:

depending on commits
dropdown-kebab-pf
the new dependencies
adding bootstrap as a dependency but removing it from requires

Totally not working today but wanted to get in a response...

you'll notice the release commit hash refers to the release tag, (for no vnc tag v0.6.2 === e8986fa) while tags can always be fiddled with, commit hashes can't, its a better way to lock it down (also when referring to git urls, you'll notice the absence of branch tags https://docs.npmjs.com/files/package.json#github-urls)

yah can trace back the styling to some pf-sass stuff dealing with class="list-view-pf-actions" it yields a 16px font size applied to the dropdowns

new dependencies, including boostrap are/were missing peer dependencies that yarn and webpack would whine about when building/ installing  so we add bootstrap because its required by others, but not needed for our app directly, as we use it through others

good question, i wasn't aware we had any mechanism for running the specs in the browser, yarn test (only thing for test running) is a console only kinda thing

yeah so dev dependencies (as refactored in this pr) are all the things we don't for yarn build to run successfully...  so build vs tooling as it stands presently, except, really really, meaning someone intentionally checked 😏

Aah, ok, makes sense, I guess :)
Except for:

you'll notice the release commit hash refers to the release tag, (for no vnc tag v0.6.2 === e8986fa) while tags can always be fiddled with, commit hashes can't, its a better way to lock it down (also when referring to git urls, you'll notice the absence of branch tags https://docs.npmjs.com/files/package.json#github-urls)

Please don't :) From a commit hash, you can't tell which version it actually is supposed to be, and there's already yarn.lock for that.

So ya wanta keep them on the tags? That change and this is okie dokie?

Yes please, because we keep the version info that way..  I'm assuming most of those are github links because the npm package is not released, something we can fix perhaps :).
As for the rest, I don't think there's anything problematic assuming nothing breaks :). I'm still surprised that the bootstrap stuff came up now, but.. hey, it does seem to work :).

@himdel looooooooooks like da thing went 💚 🥗 🍏 📗  🙇♀

Tested, it works! Hwah hwah hwah hwah hwah :)


[FLINK-24948][jdbc] Fix bug that special character in column names breaks JDBC statement parsing

What is the purpose of the change
Currently, JDBC connector assumes columns names respect Java identifier naming restrictions, but databases that support JDBC may have different naming restrictions. For example, MySQL allows dots and colons in column names. In that case, JDBC connector would have trouble parsing the named parameters in SQL.
This PR fixes the problem by adding enclosing parentheses to the named parameters.
Brief change log

Add  enclosing parentheses to the named parameters
Escape reserved characters like ':'

Verifying this change
Update existing tests to cover some corner cases.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

cc @wuchong

ping @wuchong @AHeise

Thanks @link3280 for the contribution and sorry for the late reviewing.
The fixing looks good to me. But could you add one IT case for it? For example, add a SELECT case in JdbcDynamicTableSourceITCase to read a table with the special characters in column names.
Besides, please also rebase branch to latest master.

@wuchong I tried but found Derby (used in JdbcDynamicTableSourceITCase ) doesn't support identifiers with special characters, thus not able to test the escape. Do you have any idea to workaround?

We've now moved the code from the JDBC connector to its own dedicated repository; please re-route this PR to https://github.com/apache/flink-connector-jdbc


TEST

Summary
(Write a summary for proposed changes here including the motivation.)
Test Plan
(Share your test plan here. If you changed code, please provide us with clear instructions for verifying that your changes work.)

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

I'm closing this for you @CapCap


feat: Add NumberField.is_primitive_element_of_infinitePlace_lt

Prove the following
theorem NumberField.is_primitive_element_of_infinitePlace_lt (x : 𝓞 K)
     {w : InfinitePlace K} (h₁ : x ≠ 0) (h₂ : ∀ ⦃w'⦄, w' ≠ w → w' x < 1)
     (h₃ : IsReal w ∨ |(w.embedding x).re| < 1) : ℚ⟮(x:K)⟯ = ⊤ := by

If the place w is not real, we need the condition |(w.embedding x).re| < 1 to ensure x is not a real number at the place w.

Thanks!
bors merge


ansible-galaxy integration

Hello,
This doesn't show up on ansible-galaxy and cannot be retrieved by ansible-galaxy.
[WARNING]: - ansible-role-ovftool was NOT installed successfully: this role does not appear to have a meta/main.yml file.

@pierreact It's not currently setup in ansible-galaxy.  This project has been used in the Chaperone Project which uses google repo to collect the various needed  repositories.
I'll keep this open as we should also be pushing these to galaxy in the future.

fixed by #5, still must host the ovftool binary in another repository


Swift support

Hi Jon,
I hope you're doing well. I only see objective-c files in my test coverage report. Does this project support Swift ?
Thanks,
Alex

Swift doesn't seem to support coverage yet.


Wrap up alan's changes

Need a better way to get Jenkins to test branches that doesn't involve making PRs.
These are alan's branches, just rebased onto each other.

@tacketar I rebased your commits into a linear history and pushed them in. Please go ahead and rebase any work-in-progress branches you have, otherwise you'll conflict real obnoxiously.

Will do.


"Flow" section font size/scaling decreases when resizing view or switching sections.

The flow section font can become extremely small and impossible to read after performing certain actions. Fixed by reloading page.
To Reproduce
create a factory
go to the flow tab
resize the window using the drag-able dongle
or
create a factory
switch between flow and list tabs
Expected behavior
font size should not be affected by former actions or reloading
Normal (you may also note that text can be difficult to read due to overlap)

Switching between list and flow

resizing with window resizer

Windows 10 chromium browser

Fair enough, this is kind of a known behavior I hadn't considered a true bug but it's annoying enough that I'll see what can be done about it.

Fair enough, this is kind of a known behavior I hadn't considered a true bug but it's annoying enough that I'll see what can be done about it.


Match Data Against ClearlyDefined

What would you like to be added:
Add the check against: https://docs.clearlydefined.io/get-involved or a link to the corresponding artifact
Why is this needed:
To improve the Data and maybe check the detected data against that database
Additional context:
I think it would be cool to somehow "fact check" the detected components and licenses against this database

Hi @henrysachs, thanks for the suggestion and sorry for the delay acknowledging. We'll take a look and move this into the backlog for the future. Let us know if you are interested in working on it.


Wrong position for parens wrapped identifier

@ """val x = (a).value""".parse[Stat].get.collect {
    case n: Name => n.syntax
  }
res1: List[String] = List("x", "(a)", "value") // obtained
res1: List[String] = List("x", "a", "value") // expected

This causes problems when looking up symbols of names by their positions.

Just hit again on a similar problem
@ """
    List(builder) map (_.result)
  """.parse[Stat].get.collect {
  case t @ q"_.result" => t.syntax
  }
res1: List[String] = List("(_.result)") // obtained
res1: List[String] = List("_.result") // expected

Reported by @MasseGuillaume in #1444
def structure(source: String): String =
  source.parse[Stat].get.asInstanceOf[Term.ApplyInfix].args.head.tokens.structure

// This is what I get
structure("a op (f)") == "Tokens(( [5..6), f [6..7), ) [7..8))"

// This is what I expect
structure("a op (f)") == "Tokens(f [6..7))"

// With multiple args I get what I expect
structure("a op (f, g)") == "Tokens(f [6..7))"

A good place to look into this would be https://github.com/scalameta/scalameta/blob/97e1e8af7ba75b7508bc47e25c766c5f83c96e1c/scalameta/parsers/shared/src/main/scala/scala/meta/internal/parsers/ScalametaParser.scala#L1163-L1164
where Term.Name nodes are created.

I'm on this.

Closing as fixed then :)


Add Button enum

There should be an enum called Button that has all the various buttons on a computer (e.g. up, down, A, left-click, etc.). This should be exported from the top level.

It turns out keycodes are deprecated, and they provide a nice string representation. Sadly, there are thousands, and there's no typed library for them. I think this should go in a separate library, so I'm closing this for being out of scope, at least for now.

It turns out keycodes are deprecated, and they provide a nice string representation. Sadly, there are thousands, and there's no typed library for them. I think this should go in a separate library, so I'm closing this for being out of scope, at least for now.


Add documentation for mode IDs

Adds documentation for mode IDs

Changes default output of mode-changes to true since a null modelist is created in PGM for destroyables with no modes.
Any objective that does not have modes specified will use all monument modes by default.
Explains mode-changes can't be used with modes
Adds example with mode IDs and rearranges text explaining examples.

Currently in PGM, two or more mode changes cannot happen at the same time. I am going to check and see if this is a necessary limitation and document this if it's justified.

monument modes still default to false @CoWinkKeyDinkInc

monument modes still default to false @CoWinkKeyDinkInc

Thanks, it was really hard to wrap my head around any unintended aspects of my pull request for backwards compatibility.

Thanks, it was really hard to wrap my head around any unintended aspects of my pull request for backwards compatibility.

Thanks for contributing!


Hostnames in IP rotation

Can i add IP pools with following details ???
IP Address                      Hostname
<IP_ADDRESS>                     mydomain.com
<IP_ADDRESS>                     mydomain.com
<IP_ADDRESS>                     mydomain.com
or the hostname for each unique ip address should be different, like mydomain1.com, mydomain2.com ??? like
IP Address                      Hostname
<IP_ADDRESS>                     mydomain1.com
<IP_ADDRESS>                     mydomain2.com
<IP_ADDRESS>                     mydomain3.com

I think hostname parameter doen't affect much. I have added different ip addresses for same hostname. Also the IP rotation is working properly.

I'm not sure what the hostname means but if all the IP addresses are pointing at your Postal server and have the same hostname, I don't think there will be a problem

Yes the issues has been resolved. I am able to send emails via by IP pools. Thank you


Export things in a directory structure corresponding to their module (and maybe package)

correction: generate headers file extern/export regardless of import (this doesn't exclude export by package, export by package just becomes redundant)

This issue is actually referring to how we dump every generated .h into the --output-dir directory. Would probably be a bit nicer to output it into subdirectories according to the module name (and maybe package names?)
After all, multiple modules might be exporting things of the same name, which would cause collisions.

Done in #232!


Vite: Transitive dependencies are not resolved

Describe the bug
Apps using libraries which are using other libraries are not resolved.
To Reproduce
A detailed bug report is filed for library vite-tsconfig-paths:
https://github.com/aleclarson/vite-tsconfig-paths/issues/47
Demo repository:
https://github.com/realityfilter/bug-transitive-deps
Expected behavior
nx serve app will successfully serve the app
In the meantime we are resolving the dependencies manually:
const { readFileSync } = require('fs');
const { join } = require('path');

const calculateAlias = (rootPath) => {
    const tsConfigFile = join(rootPath, 'tsconfig.base.json');
    const tsConfig = JSON.parse(readFileSync(tsConfigFile).toString());

    const alias = {};
    Object.keys(tsConfig.compilerOptions.paths).forEach((key) => {
        alias[key] = join(rootPath, tsConfig.compilerOptions.paths[key][0]);
    });

    return alias;
};

const workspaceAliases = () => {
    const aliases: { [find: string]: string } = calculateAlias(rootDir);
    return sources = Object.keys(aliases).map((key) => ({ find: key, replacement: aliases[key] }));
};

export default defineConfig({
    resolve: {
        alias: [...workspaceAliases()],
    },
});

@realityfilter I saw your comment on the Bug report. You got it working with Nx I assume? The tsconfig.base.json is the default here so changig it could be hard ^^'

We are still having a symlink to tsconfig.base.json because of an older, unrelated bug.
Setting the loose option of vite-tsconfig-paths together with the symlink solved this issue.
We need our own vite.config.ts because of vue. So no problem for us.

But with the current nx setup transitive dependencies do not work out of the box, unfortunately.

I'll take a look at that later. Maybe it's possible to make it configurable on their side so we can set it to tsconfig.base.json

I ran into this as well and have posted how I resolved it based on the notes in this thread and elsewhere in the following issue: https://github.com/aleclarson/vite-tsconfig-paths/issues/12#issuecomment-1081160667


New node: scheme from Node 16 not handled

Bug report

What is the current behavior?
The new node: prefix from Node v16 causes an UnhandledSchemeError:
ERROR in node:path
Module build failed: UnhandledSchemeError: Reading from "node:path" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
    at /Users/k/p/webpack-babel-test/node_modules/webpack/lib/NormalModule.js:742:26
    at Hook.eval [as callAsync] (eval at create (/Users/k/p/webpack-babel-test/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (/Users/k/p/webpack-babel-test/node_modules/tapable/lib/Hook.js:18:14)
    at Object.processResource (/Users/k/p/webpack-babel-test/node_modules/webpack/lib/NormalModule.js:739:9)
    at processResource (/Users/k/p/webpack-babel-test/node_modules/loader-runner/lib/LoaderRunner.js:220:11)
    at iteratePitchingLoaders (/Users/k/p/webpack-babel-test/node_modules/loader-runner/lib/LoaderRunner.js:171:10)
    at runLoaders (/Users/k/p/webpack-babel-test/node_modules/loader-runner/lib/LoaderRunner.js:397:2)
    at NormalModule.doBuild (/Users/k/p/webpack-babel-test/node_modules/webpack/lib/NormalModule.js:729:3)
    at NormalModule.build (/Users/k/p/webpack-babel-test/node_modules/webpack/lib/NormalModule.js:878:15)
    at /Users/k/p/webpack-babel-test/node_modules/webpack/lib/Compilation.js:1311:12
 @ ./src/index.tsx 1:0-29 2:12-16

webpack 5.36.0 compiled with 1 error in 977 ms

This will be backported to at least also Node v14
If the current behavior is a bug, please provide the steps to reproduce.
Minimal reproduction repo (run yarn start): https://github.com/karlhorky/webpack-node-16-schema

What is the expected behavior?
webpack should throw a "Module not found" error with the polyfills warning, just like when you import path from 'path':
ERROR in ./src/index.tsx 1:0-24
Module not found: Error: Can't resolve 'path' in '/Users/k/p/webpack-babel-test/src'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
        - install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "path": false }
resolve 'path' in '/Users/k/p/webpack-babel-test/src'
  Parsed request is a module
  using description file: /Users/k/p/webpack-babel-test/package.json (relative path: ./src)
    Field 'browser' doesn't contain a valid alias configuration
    resolve as module
      /Users/k/p/webpack-babel-test/src/node_modules doesn't exist or is not a directory
      looking for modules in /Users/k/p/webpack-babel-test/node_modules
        single file module
          using description file: /Users/k/p/webpack-babel-test/package.json (relative path: ./node_modules/path)
            no extension
              Field 'browser' doesn't contain a valid alias configuration
              /Users/k/p/webpack-babel-test/node_modules/path doesn't exist
            *
              Field 'browser' doesn't contain a valid alias configuration
              /Users/k/p/webpack-babel-test/node_modules/path* doesn't exist
            .js
              Field 'browser' doesn't contain a valid alias configuration
              /Users/k/p/webpack-babel-test/node_modules/path.js doesn't exist
            .ts
              Field 'browser' doesn't contain a valid alias configuration
              /Users/k/p/webpack-babel-test/node_modules/path.ts doesn't exist
            .tsx
              Field 'browser' doesn't contain a valid alias configuration
              /Users/k/p/webpack-babel-test/node_modules/path.tsx doesn't exist
        /Users/k/p/webpack-babel-test/node_modules/path doesn't exist
      /Users/k/p/node_modules doesn't exist or is not a directory
      /Users/k/node_modules doesn't exist or is not a directory
      /Users/node_modules doesn't exist or is not a directory
      /node_modules doesn't exist or is not a directory

webpack 5.36.0 compiled with 1 error in 913 ms

Other relevant information:
webpack version: 5.36.2
Node.js version: 16.0.0
Operating System: macOS Big Sur 11.3
Additional tools:

Yep, we should improve this, you can help, here place https://github.com/webpack/webpack/blob/master/lib/node/NodeTargetPlugin.js

Sure, opened a quick PR here: https://github.com/webpack/webpack/pull/13311
Asked for some feedback from you over there.

Ok, @sokra mentioned there's already a PR open at #12693

So this feature is about to get more usage: the node: scheme / prefix / protocol was backported to Node.js 14.13.1 / 12.20.0 🎉
https://nodejs.org/api/esm.html -> link "node: Imports" (links with anchors don't scroll properly right now)

An alternative to the approaches in #13311 and #12693 would be to use is-core-module (which was split from resolve in browserify/resolve@7c26483), so that this list doesn't need to be maintained and tested by webpack itself.

I can confirm this issue is still relevant. I'm getting the following error:
Failed to compile.
node:fs/promises
Module build failed: UnhandledSchemeError: Reading from "node:fs/promises" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
> Build error occurred
Error: > Build failed because of webpack errors

Fixed by https://github.com/webpack/webpack/pull/12693

Nice, really cool! Looking forward to using this! (also with our students in Next.js!)
Will this be in a new patch (5.39.2) or minor (5.40.0)?

@karlhorky I think we will have minor release in near future

We want to finish some critical issues and support import something from './test.json' assert { type: "json" } https://github.com/tc39/proposal-import-assertions

Oh nice!! I've seen that syntax floating around, wanting to try it for a while 🙌

I've requested that the compiled version of webpack be upgraded in Next.js too: https://github.com/vercel/next.js/issues/26914

why you close issues if not solved?

You need to use externals, with absolute URLs, i.e. node:/http:/etc aliases do not work, you need to say it is external and provide path on polyfill if you need or set false if you don't need these modules

If you provide example with the problem I will show you how to setup it

here is my same failure. @alexander-akait  can you explain what I need to do with externals? I set my webpack config params in  next.config.js...
node:fs
Module build failed: UnhandledSchemeError: Reading from "node:fs" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
    at /Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:54718:25
    at Hook.eval [as callAsync] (eval at create (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:141201:10), <anonymous>:6:1)
    at Object.processResource (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:54715:8)
    at processResource (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:140174:11)
    at iteratePitchingLoaders (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:140125:10)
    at runLoaders (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:140351:2)
    at NormalModule._doBuild (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:54705:3)
    at NormalModule.build (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:54849:15)
    at /Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:29353:12
    at NormalModule.needBuild (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:55136:32)

Import trace for requested module:
./node_modules/fetch-blob/from.js
./node_modules/node-fetch/src/utils/multipart-parser.js
./node_modules/node-fetch/src/body.js
./node_modules/node-fetch/src/index.js
./public/js/face-api.js
./public/js/setUpWorker.js
./components/pages/SessionView3/TwilioDynamic.tsx
./components/pages/SessionView3/SessionConnectionWrapper.tsx
./components/pages/SessionView3/index.tsx
./pages/sessions3/[id]/index.tsx

node:https
Module build failed: UnhandledSchemeError: Reading from "node:https" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
    at /Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:54718:25
    at Hook.eval [as callAsync] (eval at create (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:141201:10), <anonymous>:6:1)
    at Object.processResource (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:54715:8)
    at processResource (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:140174:11)
    at iteratePitchingLoaders (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:140125:10)
    at runLoaders (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:140351:2)
    at NormalModule._doBuild (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:54705:3)
    at NormalModule.build (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:54849:15)
    at /Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:29353:12
    at NormalModule.needBuild (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:55136:32)

Import trace for requested module:
./node_modules/node-fetch/src/index.js
./public/js/face-api.js
./public/js/setUpWorker.js
./components/pages/SessionView3/TwilioDynamic.tsx
./components/pages/SessionView3/SessionConnectionWrapper.tsx
./components/pages/SessionView3/index.tsx
./pages/sessions3/[id]/index.tsx

node:http
Module build failed: UnhandledSchemeError: Reading from "node:http" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
    at /Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:54718:25
    at Hook.eval [as callAsync] (eval at create (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:141201:10), <anonymous>:6:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:141003:14)
    at Object.processResource (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:54715:8)
    at processResource (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:140174:11)
    at iteratePitchingLoaders (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:140125:10)
    at runLoaders (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:140351:2)
    at NormalModule._doBuild (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:54705:3)
    at NormalModule.build (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:54849:15)
    at /Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:29353:12

Import trace for requested module:
./node_modules/node-fetch/src/index.js
./public/js/face-api.js
./public/js/setUpWorker.js
./components/pages/SessionView3/TwilioDynamic.tsx
./components/pages/SessionView3/SessionConnectionWrapper.tsx
./components/pages/SessionView3/index.tsx
./pages/sessions3/[id]/index.tsx

node:path
Module build failed: UnhandledSchemeError: Reading from "node:path" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
    at /Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:54718:25
    at Hook.eval [as callAsync] (eval at create (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:141201:10), <anonymous>:6:1)
    at Object.processResource (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:54715:8)
    at processResource (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:140174:11)
    at iteratePitchingLoaders (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:140125:10)
    at runLoaders (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:140351:2)
    at NormalModule._doBuild (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:54705:3)
    at NormalModule.build (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:54849:15)
    at /Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:29353:12
    at NormalModule.needBuild (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:55136:32)

Import trace for requested module:
./node_modules/fetch-blob/from.js
./node_modules/node-fetch/src/utils/multipart-parser.js
./node_modules/node-fetch/src/body.js
./node_modules/node-fetch/src/index.js
./public/js/face-api.js
./public/js/setUpWorker.js
./components/pages/SessionView3/TwilioDynamic.tsx
./components/pages/SessionView3/SessionConnectionWrapper.tsx
./components/pages/SessionView3/index.tsx
./pages/sessions3/[id]/index.tsx

node:process
Module build failed: UnhandledSchemeError: Reading from "node:process" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
    at /Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:54718:25
    at Hook.eval [as callAsync] (eval at create (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:141201:10), <anonymous>:6:1)
    at Object.processResource (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:54715:8)
    at processResource (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:140174:11)
    at iteratePitchingLoaders (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:140125:10)
    at runLoaders (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:140351:2)
    at NormalModule._doBuild (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:54705:3)
    at NormalModule.build (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:54849:15)
    at /Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:29353:12
    at NormalModule.needBuild (/Users/cindybishop/Documents/GitHub/bongo-focus/node_modules/next/dist/compiled/webpack/bundle5.js:55136:32)

Import trace for requested module:
./node_modules/fetch-blob/streams.cjs
./node_modules/fetch-blob/index.js
./node_modules/node-fetch/src/body.js
./node_modules/node-fetch/src/index.js
./public/js/face-api.js
./public/js/setUpWorker.js
./components/pages/SessionView3/TwilioDynamic.tsx
./components/pages/SessionView3/SessionConnectionWrapper.tsx
./components/pages/SessionView3/index.tsx
./pages/sessions3/[id]/index.tsx

> Build failed because of webpack errors

can you explain what should be done with externals and absolute URLs?

Because it is URLs, so you need to use externals to use other modules for them

I have this- it appears to compile?
this is inside my next.config.js file
webpack: (config, { buildId, isServer, webpack }) => {
        config.plugins.push(new Dotenv({ silent: true }));
        config.plugins.push(
          new webpack.DefinePlugin({
            "process.env.SENTRY_RELEASE": JSON.stringify(buildId),
          })
        );
        config.resolve.fallback = {
              http: require.resolve('stream-http'),
              https: require.resolve('https'),
              path: require.resolve("path-browserify")
              //fs: require.resolve("node-fetch")
          };

        //config.resolve.alias["@"] = path.resolve(__dirname, 'src');
        config.resolve.alias["https"] = "https";
        config.resolve.alias["process"] = "process";
        config.resolve.alias["path"] = "@node/path";
        //config.resolve.alias["fs"] = "@node/fs";
        //config.resolve.alias["@node/fs"] = "@node/fs";
        config.resolve.alias["http"] = "stream-http";
        config.resolve.alias["fs"] = "node";
        config.resolve.alias["fs"] = "node-fetch";

Please use config.externals["node:fs"]

@alexander-akait this still doesn’t work in combination with resolve.alias and resolve.fallback (see https://github.com/webpack/webpack/issues/14166)

You should not use resolve.alias for URLs, if you provide small example how you are using it I will show you how to fix it, node:something URLs are just external URLs (because node: is external protocol for web target)

@alexander-akait could you please add more info - I am using next.config.js, so the docs don't really tell me the correct syntax
you mean like this:
config.externals["node:fs"],

or do you mean like this
config.externals["node:fs"]= "node",

If you need an empty module, you can use (works like config.resolve["path"] = false):
externals: {
   // You can use `false` or other values if you need something strange here
  "node:path": "{}",
},

If you need polyfill please you:
plugins: [
  new webpack.NormalModuleReplacementPlugin(/node:/, (resource) => {
    const mod = resource.request.replace(/^node:/, "");

    switch (mod) {
      case "path":
        resource.request = "path-browserify";
        break;
      default:
        throw new Error(`Not found ${mod}`);
      }
  }),
]

For aliases we have an issue, but NormalModuleReplacementPlugin should works without any problem with any imports

It seems like the compiled webpack version in Next.js 12.2.2 still doesn't support this, still getting the following error:
error - node:path
Module build failed: UnhandledSchemeError: Reading from "node:path" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.

cc @sokra

Workaround (node: scheme in Next.js)
Fixed in my next.config.mjs with NormalModuleReplacementPlugin, similar to @alexander-akait's comment above:
export default /** @type {import('next').NextConfig} */ ({
  webpack: (config, { webpack }) => {
    config.plugins.push(
      // Remove node: from import specifiers, because
      // webpack does not yet support node: scheme
      // https://github.com/webpack/webpack/issues/13290
      new webpack.NormalModuleReplacementPlugin(
        /^node:/,
        (resource) => {
          resource.request = resource.request.replace(/^node:/, '');
        },
      ),
    );

    return config;
  },
});

@karlhorky please use externals for this. e.g. your webpack config
module.exports = {
  externals: { "node:path": "commonjs path" }
};

I tried this, didn't work with Next.js... 🤔

@alexander-akait i am getting the error:
UnhandledSchemeError: Reading from "node:event" is not handled by plugins (Unhandled scheme). Webpack supports "data:" and "file:" URIs by default. You may need an additional plugin to handle "node:" URIs.
when I try to work with the discord.js package. But i keep getting the error mentioned above from this code:
import { WebhookClient } from 'discord.js'

const myWebhook = 'https://discord.com/api/webhooks/9028989097053016106/RIu4KtG0upgB6D0ppzB5wikSOxfk8sYZeWnhMTvBHqYBm1L6W4ab7d97auMq8nsAniEc'

export const discordWebhook = async () => {
    const webhookClient = new WebhookClient({ url: myWebhook })
}

These are my webpack configs:
main webpack
module.exports = {
  resolve: {
    extensions: ['.ts', '.js']
  },
  entry: './electron/main.ts',
  module: {
    rules: require('./rules.webpack'),
  },
  output: {
    environment: {
      // Disable arrow function to prevent bytenode from giving errors
      arrowFunction: false,
    }
  }
};

webpack rules
module.exports = [
  {
    test: /\.node$/,
    use: 'node-loader',
  },
  {
    test: /\.(m?js|node)$/,
    parser: { amd: false },
    use: {
      loader: '@marshallofsound/webpack-asset-relocator-loader',
      options: {
        outputAssetBase: 'native_modules',
      },
    },
  },
  {
    test: /\.(js|ts|tsx)$/,
    exclude: /node_modules/,
    use: {
      loader: 'babel-loader',
    },
  },
  {
    test: /\.(png|jpe?g|gif)$/i,
    loader: 'file-loader',
    options: {
      name: '[path][name].[ext]',
    },
  }
];

Hope you (or anyone else) can help me out, since I am stuck for a while now 😅

Please use externals, to provide polyfill for node: and other protocols

@alexander-akait do you have an example on him to add node:events to externals in my webpack config?

externals: { 'node:events': pathToFileWhichContaintPolyfill }, it can be empty file with export {} if you need just mock

To circle back here, I've opened a PR to Next.js to support node:. https://github.com/vercel/next.js/pull/45149

The PR above https://github.com/vercel/next.js/pull/45149 by @timneutkens added support for the node: prefix in Next.js v13.1.5 🙌
Also updated my workaround post above: https://github.com/webpack/webpack/issues/13290#issuecomment-1188760779

@alexander-akait do you have an example on him to add node:events to externals in my webpack config?

Hey @colinrw I'd also just came across the same problem as you did, was wondering if you managed to solve the problem with adding externals to webpack.config? I tried doing it and managed to not get any error but when trying to run the Client, I get something that say "unexpected token : ..."

@alexander-akait do you have an example on him to add node:events to externals in my webpack config?

Hey @colinrw I'd also just came across the same problem as you did, was wondering if you managed to solve the problem with adding externals to webpack.config? I tried doing it and managed to not get any error but when trying to run the Client, I get something that say "unexpected token : ..."

Hey! I don't know why, but my project was not able to run lots of different internal API calls from different packages. I mainly had to use regular REST calls to make these calls. Therefor I was not able to solve this webpack issue.

@alexander-akait do you have an example on him to add node:events to externals in my webpack config?

Hey @colinrw I'd also just came across the same problem as you did, was wondering if you managed to solve the problem with adding externals to webpack.config? I tried doing it and managed to not get any error but when trying to run the Client, I get something that say "unexpected token : ..."

Hey! I don't know why, but my project was not able to run lots of different internal API calls from different packages. I mainly had to use regular REST calls to make these calls. Therefor I was not able to solve this webpack issue.

Yeah having the same problem as well.. will look into how to use REST then, thank you!

Hi, i've implemented the fix for Module build failed: UnhandledSchemeError: Reading from "node:fs/promises" is not handled by plugins (Unhandled scheme).
 webpackConfig.plugins.push(             new webpack.NormalModuleReplacementPlugin(/^node:/, (resource) => {                 resource.request = resource.request.replace(/^node:/, '')             })         )
But now i am getting
⨯ node_modules/langchain/dist/vectorstores/hnswlib.js (209:55) @ join
⨯ path.join is not a function
null
does anyone have a clue why this is is happening?
below is what is causing the issue inside the node_modules/langchain/dist/vectorstores/hnswlib.js
static async load(directory, embeddings) {         const fs = await import("node:fs/promises");         const path = await import("node:path");         const args = JSON.parse(await fs.readFile(path.join(directory, "args.json"), "utf8"));         const index = await HNSWLib.getHierarchicalNSW(args);         const [docstoreFiles] = await Promise.all([             fs                 .readFile(path.join(directory, "docstore.json"), "utf8")                 .then(JSON.parse),             index.readIndex(path.join(directory, "hnswlib.index")),         ]);         args.docstore = new SynchronousInMemoryDocstore(new Map(docstoreFiles));         args.index = index;         return new HNSWLib(embeddings, args);     }

@alexander-akait do you have an example on him to add node:events to externals in my webpack config?

Hey @colinrw I'd also just came across the same problem as you did, was wondering if you managed to solve the problem with adding externals to webpack.config? I tried doing it and managed to not get any error but when trying to run the Client, I get something that say "unexpected token : ..."

Hey! I don't know why, but my project was not able to run lots of different internal API calls from different packages. I mainly had to use regular REST calls to make these calls. Therefor I was not able to solve this webpack issue.

Yeah having the same problem as well.. will look into how to use REST then, thank you!

@alexander-akait @colinrw Swapping out node:events with events seems to appease Webpack.

@fergiemcdowall Can you create reproducible test repo?, for schemes you need to use externals, not alias


refactor: Add CT meters model datastructures

Envoy Metered with consumption Current Transformers (CT) implemented report CT details in /ivp/meters/readings. For the consumption CT configured in Solar with Load this provides information on net-production (grid export) and net-consumption (grid-import). Net-consumption is also reported in /production as an increasing/decreasing total of import and export, CT readings however provides these as 2 increasing properties. [^1]
[^1]: variations between firmware release may exist.
This PR is step 1 of 3 to implement #69. It adds the meters model and Envoy data structures to store the CT data as well as tests for these. In addition to energy delivered and received it collects active power, frequency, voltage, Current, power factor, State, measurement type, metering status and status flags for the CT.

Thanks @bdraco


⚠ ClamAV has degraded performance

In 4c3e71c, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 195 ms

Resolved: ClamAV performance has improved in 3c4a237.


Error in set-up

when i run the setup of ferminet, I got an error below:
File "C:\Users\user\anaconda3\envs\FermiNet\lib\site-packages\setuptools\package_index.py", line 119, in distros_for_location
wheel = Wheel(basename)
File "C:\Users\user\anaconda3\envs\FermiNet\lib\site-packages\setuptools\wheel.py", line 61, in init
raise ValueError('invalid wheel name: %r' % filename)
ValueError: invalid wheel name: 'pyscf-1.4.3-cp34-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl'
I am using anaconda in window 64 bits to setup using terminal

I'm sorry, but I'm not familiar with Windows and don't have a Windows machine to test. I also do not use anaconda. It looks like something is going wrong with installing the pyscf dependency, so I suggest you focus on installing that separately first inside the same environment. Once you have installed pyscf, then proceed to installing ferminet. The pyscf documentation contains installation instructions: https://sunqm.github.io/pyscf/install.html
Some general observations:

Despite being on Windows, anaconda is attempting to find a Mac OSX wheel for pyscf.
The pyscf version installed (1.4.3) is some years old (1.7 is now available).

This points to a problem with your anaconda setup...

I'm sorry, but I'm not familiar with Windows and don't have a Windows machine to test. I also do not use anaconda. It looks like something is going wrong with installing the pyscf dependency, so I suggest you focus on installing that separately first inside the same environment. Once you have installed pyscf, then proceed to installing ferminet. The pyscf documentation contains installation instructions: https://sunqm.github.io/pyscf/install.html
Some general observations:

Despite being on Windows, anaconda is attempting to find a Mac OSX wheel for pyscf.
The pyscf version installed (1.4.3) is some years old (1.7 is now available).

This points to a problem with your anaconda setup...

Thanks, problems solved by transporting to a Linux system. Still need to install pyscf before installing ferminet

Thanks, problems solved by transporting to a Linux system. Still need to install pyscf before installing ferminet


basic translation lib #643

It's a basic lib to ease the translations. It gets at first parameter the language you're passing, and as second the string you want to translate. And it translates it to all the other languages.
e.g. running:
node ./bin/dos-translate en "Hello"
will print:
es: Hola
de: Hallo
nl: Hallo
fr: Bonjour
fi: Hei
ru: Здравствуйте
gl: Ola
it: Ciao
sv: Hallå
ca: Hola
pt: Olá
uk: Здрастуйте

It needs a Google Translation API Key, can be obtained here. It's a paid service but google is giving free 50k words on registering.

Is it possible you add to this script the option of actually adding translated keys into the existing language file? For example:

I code some stuff and add 2 new dictionary entries to en.json. For instance:
"someComponent.welcome.text": "Welcome"
"someComponent.welcome.error": "Something went wrong"
I run something like node ./bin/dos-translate en --mising
All language files apart from en.json get updated with the missing translations for 1.1 and 1.2.

I think this isn't too far from what's already done, but it adds the auto-updating of language files, which is the one error-prone thing we have right now.


add a Review page

please assign this to me under gssoc ext and hacktoberfest

Can you show me any sample. which type of review page you are talking about?


Introduce DynamicTypedClientFactory

Enables services to dynamically build up typed clients
with the same interceptors / listeners that you would
get with TypedHttpClientModule.
Useful for platform services such as backfila that may
not know all the services they talk to upfront.

Notably I'm deferring any desired client caching to the application layer, I don't think it's appropriate for Misk / this specific layer to provide that functionality

Notably I'm deferring any desired client caching to the application layer, I don't think it's appropriate for Misk / this specific layer to provide that functionality

I think this is the right call. In terms of the existing usages of the now-renamed module, presumably they are already dealing with this? I didn't see the diff touching any bindings or removing anything that might currently be relied on for caching of these clients?

Diff is nice and minimal, couldn't think of any line level feedback. Only question I had was whether this would change anything about the existing usages of the formerly static module. My read is that it does not change anything, i.e., that it is strictly additive (the addition being the dynamic usage support).

Exactly. What would change is in services like backfila, that appear to have spun up their own dynamic setup without the benefits of shared interceptors / observability. I'll ping the backfila folks to let them know this is available.


Strip glsl comments

Saves ~6K in standalone bundle

Saves ~6K in standalone bundle

And this is just for comment stripping plugin, we haven't applied the constant remover yet...


zipfile.BadZipFile: File is not a zip file

First of all: thanks for the great library!
I am getting the following error when using dload.git_clone. I tried with different repo's but get the same error.
dload.git_clone("https://github.com/aaaa/aaaa.git", clone_dir=LOCAL_DST)
None
Traceback (most recent call last):
  File "C:\Users\a316283\AppData\Local\Continuum\anaconda3\lib\site-packages\dload\__init__.py", line 256, in save_unzip
    with zipfile.ZipFile(zip_path, 'r') as zip_ref:
  File "C:\Users\a316283\AppData\Local\Continuum\anaconda3\lib\zipfile.py", line 1222, in __init__
    self._RealGetContents()
  File "C:\Users\a316283\AppData\Local\Continuum\anaconda3\lib\zipfile.py", line 1289, in _RealGetContents
    raise BadZipFile("File is not a zip file")
zipfile.BadZipFile: File is not a zip file

Any ideas?
Thanks!

Same here. Any resolve on this issue @x011 ?

Could it be that there is no "master" branch in your repo which you want to clone ?
The branch name which will be downloaded is currently hardcoded to "master" if i understand it right.
https://github.com/x011/dload/blob/master/dload/__init__.py#L280

That's frustrating given GitHub's efforts to remove the unnecessary references to histories of enslavement. @x011 it might be something you want to address in the code.


feat: inventory host groups support (for history)

adds parsing of host groups from RBAC
stores allowed host groups to user principal(s)
adds filtering of PoliciesHistoryEntries based on allowed host groups

Out of scope: returning host groups on the API.
Hint: review by commits
RHINENG-1282

Hint: review by commits

Are you suggesting to review each commit as a single unit of work?


Add EKS Cluster Compositions using upbound-aws-provider

What does this PR do?
This PR adds 2 compositions to create EKS clusters.

eks/cluster-basic: Creates a basic cluster and nodegroup, with only the required pre-requisites to get the cluster deployed and active.
eks/cluster-with-extras: Creates the cluster and nodegroup, but adding features like KMS key for Secrets encryption, Addons for EFS, S3 and EBS CSI, as well as the AWS Load Balancer Controller.

Motivation
https://github.com/awslabs/crossplane-on-eks/issues/164
More

[x] Yes, I have tested the PR using my local account setup  (Provide any test evidence report under Additional Notes)

[ ] Yes, I have added a new example under examples to support my PR

[ ] Yes, I have updated the docs for this feature

[x] Yes, I have linked to an issue or feature request (applicable to PRs that solves a bug or a feature request)

Note:

Not all the PRs require examples and docs
We prefer small, well tested pull requests. Please ensure your pull requests are self-contained, and commits are squashed

For Moderators

[ ] E2E Test successfully complete before merge?

Additional Notes

Thank you for this PR @hflobao!
Can you please add two claims, one per compositions in a folder examples/upbound-aws-provider/composite-resources/eks? Please include a Readme in that folder to explaining what each claim creates and how to use it, include a kustomization.yaml file that links to the compositions like this one: https://github.com/awslabs/crossplane-on-eks/blob/main/examples/upbound-aws-provider/composite-resources/s3-irsa/kustomization.yaml.

@candonov , I've added claims for both EKS compositions.
Thanks!

@hflobao -- great work! how about creating the networking infrastructure (VPC, subnets, etc.) as part of the composition? I think we should make it easy for users to experiment with this composition; asking them to create the networking infrastructure themselves, then passing the subnet ids in the claim may discourage them from trying the composition. The other option is modify the instructions in the README to patch the claims YAML with the ids of the existing subnets via snippets that users can easily copy/paste. What do you think?

Hi @iamahgoub
I was thinking in provide a composition that could integrate and be deployed in an existing environment. That way, accepting existing network parameters makes sense for me.
But yes, you have a point regarding someone just trying it out in a completely new environment. Giving that, I'll create a third composition option in addition the ones already provided. I'll start from the 'cluster-with-extras' and add a 'vpc-and-cluster' composition, creating a VPC and public subnets to provision the cluster and nodegroup. How this sounds to you?

Apologies for the delayed response.
Sounds good! Just not to delay this PR any further, let's target closing this PR with compositions that create EKS clusters in existing VPCs, and have another PR for EKS composition with new VPC. Can you update the instruction in the README so the VPC hosting the management cluster is used for hosting the workload cluster as well? It would be great if the users can copy/paste a snippet (e.g. sed commands) that updates the files with the required VPC/subnet ids rather than manually editing files.


FAAS_NAMESPACE is confusing

On various places accros the project, the image repository is referred as namespace or FAAS_NAMESPACE. It could be confusing as user could get impression that we are talking about kubernetes namespace (I was mistaken as well) and as CLI help is suggesting.
https://github.com/boson-project/faas/blob/develop/docs/developers_guide.md#local-setup-and-configuration
$ faas create --help
Create a new Function, including initialization of local files and deployment.

Usage:
  faas create <name> [options] [flags]

Flags:
  -h, --help                help for create
  -i, --image string        Optional full image name, in form [registry]/[namespace]/[name]:[tag] for example quay.io/myrepo/project.name:latest (overrides --repository) - $FAAS_IMAGE
  -n, --namespace string    Override namespace into which the Function is deployed (on supported platforms).  Default is to use currently active underlying platform setting - $FAAS_NAMESPACE

What if we use image registry/repository nomenclature for the image name that we are going to build, eg. docker.io/johndoe? This way we can avoid the confusion with namespace.

@zroubalik with the latest builds, this has changed. I think this issue can probably be closed.
❯ faas help create                                                                                227ms  Tue 08 Sep 2020 02:22:24 PM EDT
Create a new Function, including initialization of local files and deployment.

Usage:
  faas create <name> [options] [flags]

Flags:
  -h, --help                help for create
  -i, --image string        Optional full image name, in form [registry]/[namespace]/[name]:[tag] for example quay.io/myrepo/project.name:latest (overrides --repository) - $FAAS_IMAGE
  -n, --namespace string    Override namespace into which the Function is deployed (on supported platforms).  Default is to use currently active underlying platform setting - $FAAS_NAMESPACE
  -p, --path string         Path to the new project directory - $FAAS_PATH (default "/home/lanceball/src/go/src/github.com/boson-project/faas")
  -r, --repository string   Repository for built images, ex 'docker.io/myuser' or just 'myuser'.  Optional if --image provided. - $FAAS_REPOSITORY
  -l, --runtime string      Function runtime language/framework. - $FAAS_RUNTIME (default "go")
      --templates string    Extensible templates path. - $FAAS_TEMPLATES (default "/home/lanceball/.config/faas/templates")
  -t, --trigger string      Function trigger (ex: 'http','events') - $FAAS_TRIGGER (default "http")
  -y, --yes                 When in interactive mode (attached to a TTY) skip prompts. - $FAAS_YES

Global Flags:
      --config string   config file path (default "~/.faas/config")
  -v, --verbose         print verbose logs

Echoing what Lance said:  This changed recently such that FAAS_REPOSITORY assimilated FAAS_NAMESPACE, and the latter was repurposed to refer to the Kubernetes Namespace.  If there are areas in the documentation, or help text, where the former meaning still exists, we should definitely treat it as a clean-up chore.  I am in the process of updating the developer's guide, so I agree this can be safely closed if this explanation is to your satisfaction @zroubalik.

With the release of 0.6.1 I think this can be closed now. @zroubalik if you feel like we need to reopen, feel free to do so.


Properties column in contract item overview needs overflow

In some instances, when creating an item definition attributes they will have long text, causing the Properties column overflow. Leaving the Claimed Supply and Actions hidden and needed to be scrolled.
Affects also the UI for settings of that item

.

properties are now displayed in the "details drawer" only and have an overflow in there


Regression in lint 'line-length'

Background
It seems like the lint rule 'line-length' does not report errors anymore in version v0.3.0.
Reproducing it
With the following policy, ./tmp/rule.rego
package mypackage

rule1 := {"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa": "bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb", "ccccccccccccccccccccccccccccccc": "dddddddddddddddddddddd"}

Running regal v0.2.0
$ regal lint tmp
Rule:           line-length
Description:    Line too long
Category:       style
Location:       tmp/rule.rego:3:142
Text:           rule1 := {"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa": "bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb", "ccccccccccccccccccccccccccccccc": ...
Documentation:  https://github.com/StyraInc/regal/blob/main/docs/rules/style/line-length.md

While running regal v0.3.0:
$ regal lint tmp
1 file linted. No violations found.

Additional information
Versions:
# Regal v0.2.0 version
$ regal version
Version:    0.2.0
Go Version: go1.20.5
Platform:   darwin/arm64
Commit:        unknown
Timestamp:  2023-06-21T14:48:38Z
Hostname:   github.actions.local

# Regal v0.3.0 version
$ regal version
Version:    0.3.0
Go Version: go1.20.5
Platform:   darwin/arm64
Commit:        unknown
Timestamp:  2023-06-27T13:35:54Z
Hostname:   github.actions.local

.regal/config.yaml (shortened for brevity):
rules:
  style:
    line-length:
      level: error
      max-line-length: 120

#192 mentions a bug in line-length. Could you try with regal built from that branch, by any chance? 😃

Thanks for reporting, @kristiansvalland! As @srenatus said, that should be fixed in the open PR. I’m not close to a computer today, but if @srenatus or @charlieegan3 would want to merge that and tag v0.4.0, feel free to do so! If not I’ll get to it tonight.

I did go install github.com/styrainc/regal@e2e-tests, and can confirm that it fixes the issue. It also seems to fix at least one other lint too.
$ regal3 lint tmp
1 file linted. No violations found.

# from e2e-tests branch
$ regal lint tmp
Rule:           no-whitespace-comment
Description:    Comment should start with whitespace
Category:       style
Location:       tmp/rule.rego:3:1
Text:           #tmp
Documentation:  https://github.com/StyraInc/regal/blob/main/docs/rules/style/no-whitespace-comment.md

Rule:           line-length
Description:    Line too long
Category:       style
Location:       tmp/rule.rego:4:142
Text:           rule1 := {"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa": "bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb", "ccccccccccccccccccccccccccccccc": ...
Documentation:  https://github.com/StyraInc/regal/blob/main/docs/rules/style/line-length.md

I think this can be closed after that is merged.
As an unrelated note: Thanks for creating such a great tool! 🚀

The no-white space-comment one is actually a new rule since v0.3.0 :)

I've pushed v0.4.0 and this appears to be fixed.
tmp.Oba46CxF $ regal lint tmp
Rule:         	line-length
Description:  	Line too long
Category:     	style
Location:     	tmp/rule.rego:3:142
Text:         	rule1 := {"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa": "bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb", "ccccccccccccccccccccccccccccccc": ...
Documentation:	https://github.com/StyraInc/regal/blob/main/docs/rules/style/line-length.md

1 file linted. 1 violation found.
[3]tmp.Oba46CxF $ regal version
Version:    0.4.0
Go Version: go1.20.5
Platform:   darwin/arm64
Commit:        unknown
Timestamp:  2023-07-04T09:02:54Z
Hostname:   github.actions.local

Re-open if there's something I've missed 🙂


Define new controller for framework.

Describe the feature
Define new controller for framework, not change the recommendation controller, for compatible.

First commit in #427

done in #445


TaxID 426428 is not found in taxonomy database

Hello Qiyun,
When I used command as following:
hgtector analyze -i L001_L001.proteins.tsv -o . -t database/taxdump --bandwidth auto
I met the error as following:
`Analysis started at 2021-12-03 10:15:57.662288.
Reading local taxonomy database...
Done. Read 26558 taxa.
Reading homology search results...
L001_L001.proteins: 13277 proteins.
Done. Read search results of 1 samples.
Auto-inferring plausible taxIds for input genomes based on taxonomy of search results...
Traceback (most recent call last):
File "/isilon/saskatoon-rdc/users/fuf/comDIR/miniconda/envs/hgtector/lib/python3.8/site-packages/hgtector/util.py", line 422, in _get_taxon
return taxdump[tid]
KeyError: '426428'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/isilon/saskatoon-rdc/users/fuf/comDIR/miniconda/envs/hgtector/lib/python3.8/site-packages/hgtector/analyze.py", line 364, in assign_taxonomy
tid, cov = self.infer_genome_tax(
File "/isilon/saskatoon-rdc/users/fuf/comDIR/miniconda/envs/hgtector/lib/python3.8/site-packages/hgtector/analyze.py", line 420, in infer_genome_tax
for tid in get_lineage(bestid, taxdump):
File "/isilon/saskatoon-rdc/users/fuf/comDIR/miniconda/envs/hgtector/lib/python3.8/site-packages/hgtector/util.py", line 659, in get_lineage
taxon = _get_taxon(cid, taxdump)
File "/isilon/saskatoon-rdc/users/fuf/comDIR/miniconda/envs/hgtector/lib/python3.8/site-packages/hgtector/util.py", line 424, in _get_taxon
raise ValueError(f'TaxID {tid} is not found in taxonomy database.')
ValueError: TaxID 426428 is not found in taxonomy database.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/isilon/saskatoon-rdc/users/fuf/comDIR/miniconda/envs/hgtector/bin/hgtector", line 96, in
main()
File "/isilon/saskatoon-rdc/users/fuf/comDIR/miniconda/envs/hgtector/bin/hgtector", line 35, in main
module(args)
File "/isilon/saskatoon-rdc/users/fuf/comDIR/miniconda/envs/hgtector/lib/python3.8/site-packages/hgtector/analyze.py", line 141, in call
self.assign_taxonomy()
File "/isilon/saskatoon-rdc/users/fuf/comDIR/miniconda/envs/hgtector/lib/python3.8/site-packages/hgtector/analyze.py", line 368, in assign_taxonomy
raise ValueError(f'Cannot auto-infer taxonomy for {sid}.'
ValueError: Cannot auto-infer taxonomy for L001_L001.proteins. Please specify manually.
`
In fact, my data is good before I updated HGTector.
Thanks,
Fuyou

Likely because the protein sequence database and the taxdump are not compatible. For example, if you did search using the old database, and do the analysis using the new database, there could be some missing TaxIDs.


Update dapr bundle to use helm3

Cool! Is this using the new helm3 mixin from MChorfa? I think that's the best one to bet on going forward.
https://github.com/deislabs/porter-packages/blob/6a3c0c81e09e06b24e2af1c00fb0ab26cb95d65c/mixins/index.json#L56-L60

It's currently using Ralph's helm3 mixin https://github.com/squillace/porter-helm3 but I can update to use the one you linked to above.

I'm working with mchorfa's, as he has a stronger typing for helm3. It's fine to use that one, though we will merge where it is.


Is the itkMemoryProbesCollecterBaseTest useful?  It fails on macOS, at least in some conditions

The itkMemoryProbesCollecterBaseTest fails on macOS, at least in some conditions, ex:
https://open.cdash.org/tests/1690707341
where it gives:
Freeing memory should result in less memory but it is 262216kB instead of 262164kB

I have a suspicion that this test is quite old, and being tripped up by modern OS memory management (ex: memory compression and other magic).
I wonder if this test really gives any value?

In fact, unless I've missed something in my searching, itkMemoryProbe* is only used in Examples and Tests...

Of course, that class is meant for testing and debugging. Perhaps increase the amount of memory being released? That should prevent it from being lost in the noise.


remove unused main methods from codebase

already created daggy PR
https://github.com/Terracotta-OSS/dso/pull/153