Update to xtensor 20.3

I'm happy to see this broke Travis. I have been having the same Travis issues but all is well when I compile locally with clang. I think it shows up on g++ only but I may be wrong

Yes we are out for the day but neither johan or me can reproduce this locally.

seems like there might be a missing default construcotr for the buffer adaptor?

Actually not! We set it to = default... and both johan and I are not reproducing locally. Also it seems to occur across compilers and platforms.

Maybe it's because a pointer member is not default constructible (like a
reference or something?).
Also couldn't reproduce with gcc9
On Sun 14 Apr 2019 at 23:04, Sylvain Corlay<EMAIL_ADDRESS>wrote:

Actually not! We set it to = default... and both johan and I are not
reproducing locally. Also it seems to occur across compilers and platforms.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/QuantStack/xtensor-r/pull/110#issuecomment-483058153,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA2BPnjW_G4MDoJRA7ncoiev3a28Qz9sks5vg5fugaJpZM4cusA4
.

Based on what I am seeing, the issue is in the building of Xtensor.R not anything specific to xtensor-r right? And it looks like maybe it has something to do with one of the cpp files in Xtensor.R's src/ directory? I thought that was the case because I am seeing:
Error: package or namespace load failed for ‘xtensor’ in dyn.load(file, DLLpath = DLLpath, ...):
 unable to load shared object '/home/travis/miniconda/lib/R/library/xtensor/libs/xtensor.so':
  /home/travis/miniconda/lib/R/library/xtensor/libs/xtensor.so: undefined symbol: _ZNSaISt7complexIdEEC1Ev

which demangles to std::allocator<std::complex<double> >::allocator() being the undefined symbol.
Looking at Xtensor.R, you use complex here:
https://github.com/QuantStack/Xtensor.R/blob/dddfcbbd709d19ce60324e7f5fbc256de331b58d/src/test-types.cpp#L30
The #include header of rarray.hpp would also pull in rcontainer.hpp which has <complex> in it so idk why that would fail, but maybe that is it.

For reference when i was testing this a little while back i was just working with Xtensor.R and got the same error https://travis-ci.org/DavisVaughan/Xtensor.R/jobs/519931021#L1743

I can confirm that commenting out src/test-types.cpp and the corresponding testthat/test-types.R file results in passing Xtensor.R builds.
However:

Just adding #include <complex> to the top of src/test-types.cpp does not result in a passing build.
Adding #include <complex> to xtensor.h also does not result in a passing build (i thought this may help because xtensor.h get's included in the RcppExports.cpp file that compileAttributes() makes.

Thanks @DavisVaughan! I really don't know what is going on.
As I was suspecting a mismatch of STL versions used in R and our extension, I tried building xtensor-r with the GCC compiler that is used to build the R conda package, and am getting a similar error but with the tests of xtensor-r, and at build time:
https://travis-ci.org/QuantStack/xtensor-r/jobs/521041719

Maybe it might be smart to also try to make sure that things are still passing with the last known build that worked fine. Like, go restart a travis build that included std::complex pieces but uses an older version of xtensor that we know passes. If that still passes, we have isolated the problem to an xtensor change. (as opposed to some conda change or something)

This appears to be a compiler bug. @JohanMabille found a workaround for xtensor-r that I will push shortly.

All i have to say is, wow.


Allow FlaskApp to accept flask specific kwargs so that it can be passed to the Flask constructor

Description
We use connexion for REST API purposes and also use the Flask app object to setup the web GUI endpoints. Great but the problem is there seems to be no way to pass flask-related constructor arguments. This issue arises as we use py.test to test our REST and web endpoints and because the way how py.test sets the current working directory, it does not load the templates directory as Flask uses relative default path to load the templates.
Expected behaviour
I can provide a quick fix for it. The FlaskApp constructor [from .apps.flask_app import FlaskApp] can accept another argument called flask_kwargs which can then be passed to the Flask object in create_app. I will submit a fix for it. I think it will be very beneficial for a lot more people.
Actual behaviour
Steps to reproduce
Additional info:
Output of the commands:

python --version
python3 --version
Python 3.7.4
pip show connexion | grep "^Version\:"
python3 -m pip list | grep connexion
connexion                     2.4.0

You can do this via the server_args parameter.


Tag commit titles that require a fresh db: [db]

If there is going to be a commit that will require a fresh db, I suggest that the title is tagged with [db]. That will save us just a little time investigating why the server suddenly stopped working, especially since blowing away the db is a last resort.

Will do


Method removeHandler in m-microcart-panel.vue doesn't work

Current behavior

Add some product to cart
Click on cart icon en top menu
In right side cart click on (x) button of the product
It called these method
https://github.com/DivanteLtd/vsf-capybara/blob/c46f43df003d8b19b78df31fbd7bb06ba9b3ce98/components/organisms/o-microcart-panel.vue#L28
Nothing change

Expected behavior

Add some product to cart
Click on cart icon en top menu
In right side cart click on (x) button of the product
It called these method
https://github.com/DivanteLtd/vsf-capybara/blob/c46f43df003d8b19b78df31fbd7bb06ba9b3ce98/components/organisms/o-microcart-panel.vue#L28
Delete these product from cart

Steps to reproduce the issue

Add some product to cart
Click on cart icon en top menu
In right side cart click on (x) button of the product
The product is doesn't remove.

Can you handle fixing this bug by yourself?

[ ] YES
[ x ] NO

Environment details

Browser: Chrome Versión 84.0.4147.135 (Build oficial) (64 bits)
OS: Windows 10
Code Version: VSF 1.12,3, capybara theme

Additional information

@iehoshia This is bug fixed by SF UI
https://github.com/DivanteLtd/storefront-ui/commit/96a160fde2800e7ed78982e1c81d353dc6bc112c#diff-cd3d0d38f7909e7ef2754aea9c61c6af


Create a simple put-get-delete integration test.

Create a simple put-get-delete integration test. We are going to send alert if this test fails.

LGTM.  This is a great idea.


New PR to test SignCLA at 2019-08-08 12:33:17.830075541 -0700 PDT m=+4.796544463

Body of PR

unsigned-fail-fork-staging: test succeeded


Create eka_e.md

Notes for Reviewers

This PR fixes #

Signed commits

[ ] Yes, I signed my commits.

🚀 Preview for commit a9b0d5927fb3d3058250b9d5e5773078848be9d3 at: https://673f4e773c589507e8ff73c6--meshery-docs-preview.netlify.app


maximum decimal

Aptos only have a maximum decimal of 8 if you type 18 you can´t mint more than about 10 tokens

Thanks for your contribution 🫶.


Removing bash for building images using podman/docker

Signed-off-by: Mohammed Zeeshan Ahmed<EMAIL_ADDRESS>What type of PR is this:
/kind bug
What does this PR do / why we need it:
Which issue(s) this PR fixes:

Fixes #5588
PR acceptance criteria:

[ ] Unit test

[ ] Integration test

[ ] Documentation

How to test changes / Special notes to the reviewer:
On windows:
initialize component with a deploy devfile like for eg tests/examples/source/devfiles/nodejs/devfile-deploy.yaml
You may want to change image name for full deploy expirence so push can happen
C:\Users\Mohammed Zeeshan\work\odo\testing>"C:\Users\Mohammed Zeeshan\Downloads\odo.exe" deploy
  __
 /  \__     Deploying the application using nodejs-prj1-api-abhz Devfile
 \__/  \    Namespace: default
 /  \__/    odo version: v2.5.0
 \__/

- Building & Pushing Container: docker.io/mohammedzee1000/myimage
 -  Building image locally  ...
failed to get console mode for stdin: The handle is invalid.
[+] Building 1.4s (10/10) FINISHED
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 32B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.1s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for quay.io/phmartin/node:17                                                                                0.9s
 => [1/5] FROM quay.io/phmartin/node:17@sha256:204a4603f9eac642121286b1dd8cd629809461929af5700073024eaef9fe4931                                                                                0.0s
 => [internal] load build context                                                                                0.1s
 => => transferring context: 405B                                                                                0.0s
 => CACHED [2/5] WORKDIR /usr/src/app                                                                                0.0s
 => CACHED [3/5] COPY package*.json ./                                                                                0.0s
 => CACHED [4/5] RUN npm install                                                                                0.0s
 => CACHED [5/5] COPY . .                                                                                0.0s
 => exporting to image                                                                                0.2s
 => => exporting layers                                                                                0.0s
 => => writing image sha256:75c845a99439e2667fed274c9a8a08372455c7f54cc325046642f8ffc2e9e0b2                                                                                0.0s
 => => naming to docker.io/mohammedzee1000/myimage                                                                                0.0s

Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
 V  Building image locally [2s]
 -  Pushing image to container registry  ...
Using default tag: latest
The push refers to repository [docker.io/mohammedzee1000/myimage]
a46da801cfaa: Layer already exists
6cba780e5482: Layer already exists
2c14ea7cd532: Layer already exists
1b9c941aeeb4: Layer already exists
013fc0144002: Layer already exists
5723726afdfd: Layer already exists
02784cd376a2: Layer already exists
3525f11eba01: Layer already exists
8f56c3340629: Pushed
ba6e5ff31f23: Layer already exists
9f9f651e9303: Layer already exists
0b3c02b5d746: Layer already exists
62a747bf1719: Layer already exists
latest: digest: sha256:c82dc22348c465d7c3363e8ba0d5a845c8c4082903d8812fb3bb1a67cbcba5d3 size: 3048
 V  Pushing image to container registry [6m]

- Deploying Kubernetes Component: my-component
 V  Searching resource in cluster
 V  Creating kind Deployment [12ms]

Your Devfile has been successfully deployed

updated, ptal

/lgtm

@mohammedzee1000 Could we trigger the Windows tests, to make sure this is also covered by the existing tests? Since the original issue was more about building images on Windows.

@mohammedzee1000 Could we trigger the Windows tests in CI, to make sure the existing integration tests cover your changes? Since the original issue was specifically about both build-images and deploy on Windows.
BTW, I manually tested your changes on Windows, and it worked great 👍🏿

@mohammedzee1000 Could we trigger the Windows tests in CI, to make sure the existing integration tests cover your changes? Since the original issue was specifically about running both build-images and deploy on Windows.
BTW, I manually tested your changes on Windows, and they worked great 👍🏿

@rm3l I would love to but by the looks of it all tests have run for the PR but it does not seem to have windows test.
Also, we would need windows without bash installed for one test.
@anandrkskd @rnapoles-rh one of you guys know about win testing?

@mohammedzee1000 Could we trigger the Windows tests in CI, to make sure the existing integration tests cover your changes? Since the original issue was specifically about running both build-images and deploy on Windows.
BTW, I manually tested your changes on Windows, and they worked great 👍🏿

@rm3l I would love to but by the looks of it all tests have run for the PR but it does not seem to have windows test. Also, we would need windows without bash installed for one test.

Yup, I saw them triggered for some other PRs like #5675 but not for this one (where it could have been interesting), and was wondering what would be the condition to run them.

Yup, I saw them triggered for some other PRs like #5675

On that PR, I force pushed after a rebase because of a panic I saw in Windows test. But after the force push, I don't see Windows tests in the list.

That is inconsistant behavior

@mohammedzee1000 Can you rebase your branch onto main, so we can see if the Windows tests get triggered by chance? ¯_(ツ)_/¯

@anandrkskd not sure what happened for windows ocp test there

@anandrkskd not sure what happened for windows ocp test there

The windows tests failed with some network error, as tests failed on project creation, for multiple test cases.

Retriggering by using @valaparthvi hack :D

odd win test did not trigger

@rm3l well, it passed

@rm3l well, it passed

Awesome 🎉 - thanks.
/lgtm
/approve


[Defect] Failed to generate .NET sdk for contosowidgetmanager

In Unified pipeline, it failed to generate .NET sdk for contosowidgetmanager.
see:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=2653167&view=logs&j=03afb3bb-7296-55ad-aa07-ceee610c73b2&t=0f320c29-1c90-5304-d2d3-c58a6bb76437
root cause:
Contoso.WidgetManager has dependency on Contoso.WidgetManager.Shared. But in Unified pipeline there is no anyway to find this dependency, and the TypeSpec-Project-Sync.ps1 will only sync the TypeSpec project folder Contoso.WidgetManager, without dependency directory Contoso.WidgetManager.Shared.

Will create a new issue for this.

this defect will be resolved by the sdk automation E2E for typespec. There is another issue to track. close this.


canvasDrawing

Not final

This is looking good so far. Let me know when its ready. Also keep an eye on sanjeevs branch for clashes as our features we are working on are fairly close

Once the correct pixel art behavior is added to the tools this is good for merging

Closed for more recent PR


Add file and dataset size validation checks

To respond to #70 and complete #217, this PR adds two generic dataset validations for all archives:

dataset size changes: if the overall dataset size changes by more than |X| from the last archive, throw a validation error.
file size changes: if any one file size's changes by more than |X| from the last archive, throw a validation error.

To do:

[x] Figure out how to configure the threshold of change for each dataset
[x] Pick a more reasonable threshold than 10% (which seems too low)

I bumped up the tolerances - I suspect as we continue to make new archives we'll fine tune the expected common threshold and find some dataset specific outliers but this seems like a reasonable starting point.


Add link to app-mining github repo

This PR

adds a section about the app-mining github repo

 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.

Thanks for the PR @friedger .


linkage_checker: report linkage with system frameworks

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

Currently, brew linkage reports linkage with system frameworks only if
they can be found on the file system. This results in this linkage not
being reported on Big Sur and newer, where system libraries are stored
in the dyld cache instead.
Let's fix that by avoiding silently ignoring system frameworks by moving
them out of #harmless_broken_link?. We retain the behaviour desired
from 7228e60da51392b20d55e0c087b2082b86fb3bbf by deferring checking if a
broken library is actually a system framework to just before we add it
to @broken_dylibs.
To see how this changes the behaviour of brew linkage, here's an
example with this change:
❯ brew linkage neovim
System libraries:
  /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
  /usr/lib/libSystem.B.dylib
  /usr/lib/libiconv.2.dylib
  /usr/lib/libutil.dylib
Homebrew libraries:
  /usr/local/opt/gettext/lib/libintl.8.dylib (gettext)
  /usr/local/opt/libtermkey/lib/libtermkey.1.dylib (libtermkey)
  /usr/local/opt/libuv/lib/libuv.1.dylib (libuv)
  /usr/local/opt/luajit/lib/libluajit-5.1.2.dylib (luajit)
  /usr/local/opt/luv/lib/libluv.1.dylib (luv)
  /usr/local/opt/msgpack/lib/libmsgpackc.2.dylib (msgpack)
  /usr/local/opt/tree-sitter/lib/libtree-sitter.0.dylib (tree-sitter)
  /usr/local/opt/unibilium/lib/libunibilium.4.dylib (unibilium)

and without this change:
❯ brew linkage neovim
System libraries:
  /usr/lib/libSystem.B.dylib
  /usr/lib/libiconv.2.dylib
  /usr/lib/libutil.dylib
Homebrew libraries:
  /usr/local/opt/gettext/lib/libintl.8.dylib (gettext)
  /usr/local/opt/libtermkey/lib/libtermkey.1.dylib (libtermkey)
  /usr/local/opt/libuv/lib/libuv.1.dylib (libuv)
  /usr/local/opt/luajit/lib/libluajit-5.1.2.dylib (luajit)
  /usr/local/opt/luv/lib/libluv.1.dylib (luv)
  /usr/local/opt/msgpack/lib/libmsgpackc.2.dylib (msgpack)
  /usr/local/opt/tree-sitter/lib/libtree-sitter.0.dylib (tree-sitter)
  /usr/local/opt/unibilium/lib/libunibilium.4.dylib (unibilium)

Review period will end on 2022-07-19 at 04:05:57 UTC.

I'm not sure I understand the scenario presented in the original issue. It seems like the desire is to ship binaries built on older macOS versions linked with frameworks that only exist on newer macOS versions. Why?

I'm not sure I understand the scenario presented in the original issue. It seems like the desire was to ship binaries built on older macOS versions linked with frameworks that only exist on newer macOS versions. Why?

This is not clear to me either. Maybe @fxcoudert remembers?

Review period ended.


Allow node-sass 4.6.0?

Any chance that the node-sass dependency could be updated to allow 4.6.0?
I seem to have shot myself in the foot with by updating to node.js 9.1 -  which 4.5.3 doesn't have a prebuilt binary for.  So (being on windows) I'm into Windows node-gyp build hell...

Have you tried manually install node-sass into your devDependencies?

Hmm. I did yarn add node-sass --dev which runs fine and adds "node-sass": "^4.6.0" to package.json. but when I then add laravel-mix, it still fails downloading https://github.com/sass/node-sass/releases/download/v4.5.3/win32-x64-59_binding.node (which doesn't exist).

What about adding Laravel Mix then node-sass? Does that not work?

Laravel Mix explicitly requires node-sass 4.5.3 according to it's package.json, so when you do yarn add laravel-mix yarn tries to download the correct pre-built binary for node-sass, according to your node.js version. I have node.js 9 installed, and there's no node-sass 4.5.3 binary for that version.

just seen this commit message: https://github.com/JeffreyWay/laravel-mix/commit/03ae69849ac6c7454e299f964a9f977eab7e36c8
So looks like the 4.5.3 dependency is intentional right now, and Jeffrey is aware :)

@ruchern @JeffreyWay Looks like node-sass 4.6.1 has fixed the watcher bug.

@roddypratt Checking that discussion, it still seems like folks are having problems - even with 4.6.1. So I'm going to hold off a bit longer.

So I'm going to hold off a bit longer.

Then is it possible to keep this issue open? Will make it easier to follow resolution for everyone.

Checking that discussion, it still seems like folks are having problems

Which discussion? On https://github.com/sass/node-sass/pull/2147 nothing has been added/reported since release 4.6.1...
Thx! 👍

https://github.com/sass/node-sass/issues/2139

I also got the same error when upgrading my node to 9.2 in windows 10. Is there is any workaround beside downgrading my node version?

@bungcip You can pin lavarel-mix to version 1.5.0, but keep in mind it can be buggy.
@JeffreyWay Looks like node-sass 4.7.0 has fixed the watcher bug (seems really fixed this time 😄).

@LeoColomb, thank you. pinned to 1.5.0 for now.


Touchpad gestures are broken in 1.2 experimental

Describe the bug
After updating to 1.2 experimental, touchpad gestures like panning and zooming no longer work correctly (i.e. very laggy and no overscroll effect). This is a regression compared to 1.1.3.
Steps to reproduce the bug
Try any scrollviewer. All gestures seem to be translated to mouse wheel events.
Expected behavior
No response
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.2 Experimental: 1.2.220727.1-experimental1
Windows app type

[ ] UWP
[X] Win32

Device form factor
Desktop
Windows version
Windows 11 (21H2): Build 22000
Additional context
No response

This is still broken in 1.2 preview 1

Still broken in 1.2 preview 2...

Fixed in latest 1.2 stable


Update README: add button to launch Poetry playground in browser

Add the button to README to launch a Poetry playground and try it out right in the browser:

https://rootnroll.com is a standalone service for running cli playgrounds.
Source files used to create the Poetry playground: https://github.com/rootnroll/library/tree/master/poetry/
Automated build of the docker image: https://hub.docker.com/r/rootnroll/demo-poetry/

This would be great to encourage adoption

This looks like a cool service you've made.  well done!
I hope you understand that I'm hesitant to send traffic there though.  Its unclear to me who runs it and how it's funded.  So feel free to call me paranoid but I don't think we should link here.


Integration cannot be setup in HomeAssistant 2021.12

Version of the custom_component
0.6.3
Describe the bug
Integration doesn't start since HomeAssistant was upgraded to version 2021.12 (see error log).
Removing integration and rebooting HA core results in HASP discovery, but integration can't be added with the same error.
Removing and re-adding integration gives configuration flow error.
Debug log

Logger: homeassistant.config_entries
Source: custom_components/openhasp/__init__.py:409
Integration: openHASP (documentation, issues)
First occurred: 16:09:56 (1 occurrences)
Last logged: 16:09:56

Error setting up entry plate for openhasp
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 313, in async_setup
    result = await component.async_setup_entry(hass, self)  # type: ignore
  File "/config/custom_components/openhasp/__init__.py", line 251, in async_setup_entry
    await component.async_add_entities([plate_entity])
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 382, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 613, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 747, in add_to_platform_finish
    await self.async_added_to_hass()
  File "/config/custom_components/openhasp/__init__.py", line 409, in async_added_to_hass
    self.hass.components.mqtt.async_publish(
TypeError: async_publish() missing 1 required positional argument: 'payload'

Please try upgrading to the newly released version 0.6.4 of the custom component.

Thank you, it worked.


[Enhancement request] write variable to env file

Hello there,
This is my first post in this repo. If not anything else, big thanks for this very cool project.
I would like to ask if it is possible to start a feature request.
As of right now, it is possible to "read" a env file by doing the dotenv.get("mykey")
Would it be possible to have a feature to write some values?
For instance: starting with the file .env
With content
mykey = somevalue

Then to run dotenv.set("anotherkey", "someothervalue")
And the .env file would be
anotherkey =someothervalue

Hope this is not too much of a trouble.
Thank you

This feature is out of scope for this lib. The lib is intended to load config rather than write it.


Error building Conditional Router Component

Component Conditional Router failed to build with error "You must specify an output name to call stop"
Version

v1.0.0rc0

To Reproduce

Add Component Conditional Router
Build Component
You get the error message: "You must specify an output name to call stop"

To Solve
I added if len(self.vertex.outputs) < 2 condition in custom_component.py
https://github.com/langflow-ai/langflow/blob/a9b2f5f82e0e4ea849914c2f6e2e7082dbd54c61/src/backend/base/langflow/custom/custom_component/custom_component.py#L99
    def stop(self, output_name: str | None = None):
        if not output_name and self.vertex and len(self.vertex.outputs) == 1:
            output_name = self.vertex.outputs[0]["name"]
        else:
            if len(self.vertex.outputs) < 2:
                raise ValueError("You must specify an output name to call stop")

Component Conditional Router failed to build with error "You must specify an output name to call stop"
Version：
v1.0.5
ValueError: You must specify an output name to call stop
[06/27/24 16:23:20] ERROR    2024-06-27 16:23:20 - ERROR    - service - Error stopping tracing service: 'NoneType' object has no attribute 'cancel'

Component Conditional Router failed to build with error "You must specify an output name to call stop"
Version：
v1.0.5
ValueError: You must specify an output name to call stop
[06/27/24 16:23:20] ERROR 2024-06-27 16:23:20 - ERROR - service - Error stopping tracing service: 'NoneType' object has no attribute 'cancel'

Component Conditional Router failed to build with error "You must specify an output name to call stop"
Version

v1.0.0rc0

To Reproduce

Add Component Conditional Router
Build Component
You get the error message: "You must specify an output name to call stop"

To Solve
I added if len(self.vertex.outputs) < 2 condition in custom_component.py
https://github.com/langflow-ai/langflow/blob/a9b2f5f82e0e4ea849914c2f6e2e7082dbd54c61/src/backend/base/langflow/custom/custom_component/custom_component.py#L99
    def stop(self, output_name: str | None = None):
        if not output_name and self.vertex and len(self.vertex.outputs) == 1:
            output_name = self.vertex.outputs[0]["name"]
        else:
            if len(self.vertex.outputs) < 2:
                raise ValueError("You must specify an output name to call stop")

Component Conditional Router failed to build with error "You must specify an output name to call stop"
Version：
v1.0.5
ValueError: You must specify an output name to call stop
[06/27/24 16:23:20] ERROR 2024-06-27 16:23:20 - ERROR - service - Error stopping tracing service: 'NoneType' object has no attribute 'cancel'

Hello,
Sorry for the delay. Did you try using the new version? Does the error still persist?

@anovazzi1 is this component the conditional routing you said was in the new version? Or is it another component? (i.e. route based on previous user's message)

v1.0.5

v1.0.5，thanks

Component Conditional Router failed to build with error "You must specify an output name to call stop"
Version

v1.0.0rc0

To Reproduce

Add Component Conditional Router
Build Component
You get the error message: "You must specify an output name to call stop"

To Solve
I added if len(self.vertex.outputs) < 2 condition in custom_component.py
https://github.com/langflow-ai/langflow/blob/a9b2f5f82e0e4ea849914c2f6e2e7082dbd54c61/src/backend/base/langflow/custom/custom_component/custom_component.py#L99
    def stop(self, output_name: str | None = None):
        if not output_name and self.vertex and len(self.vertex.outputs) == 1:
            output_name = self.vertex.outputs[0]["name"]
        else:
            if len(self.vertex.outputs) < 2:
                raise ValueError("You must specify an output name to call stop")

Tried adding if len(self.vertex.outputs) < 2 condition in custom_component.py, still doesn't work.

 谢谢！
------------------ 原始邮件 ------------------
发件人: "Hongxuan @.>;
发送时间: 2024年7月2日(星期二) 中午11:14
收件人: @.>;
抄送: @.>; @.>;
主题: Re: [langflow-ai/langflow] Error building Conditional Router Component (Issue #2268)
Component Conditional Router failed to build with error "You must specify an output name to call stop"
Version
v1.0.0rc0
To Reproduce
Add Component Conditional Router
Build Component
You get the error message: "You must specify an output name to call stop"
To Solve
I added if len(self.vertex.outputs) < 2 condition in custom_component.py
https://github.com/langflow-ai/langflow/blob/a9b2f5f82e0e4ea849914c2f6e2e7082dbd54c61/src/backend/base/langflow/custom/custom_component/custom_component.py#L99
def stop(self, output_name: str | None = None):         if not output_name and self.vertex and len(self.vertex.outputs) == 1:             output_name = self.vertex.outputs[0]["name"]         else:             if len(self.vertex.outputs) < 2:                 raise ValueError("You must specify an output name to call stop")
Tried adding if len(self.vertex.outputs) < 2 condition in custom_component.py, still doesn't work.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

@Alex-Poon yes, it was, I'll take a look and fix it ASAP

Hi @GordeyChernyy,

I hope you're doing well. Just a friendly reminder that if we do not hear back from you within the next 3 days, we will close this issue. If you need more time or further assistance, please let us know.
Thank you for your understanding!

Thank you for your contribution! This issue will be closed. If you have any questions or encounter another problem, please open a new issue and we will be ready to assist you.


Warning about missing keyExtractor

When i enabled debugging, I always got warning about DataSource.js:8 RecyclerViewList/DataSource: missing keyExtractor, it's strongly recommended to specify a keyExtractor function in order to use all the features correctly
This is the code to define dataSource
    var dataSource = new DataSource(
      this.props.activities,
      (item, index) => item.id
    );

@arryanggaputra  got any solution?
@godness84  Please help...

I found it..
As the warning is present in the constructor part of DataSource.js, whenever the "DataSource" is imported, that time no "keyExtractor" is provided, so the warning appears.
So the constructor method can be changed to overcome this.
@godness84  Please take a look into this issue.

you were right @maxme, solved!


EPIC: Formalise the ethnic group question guidance

Reference for later:
https://uxdesign.cc/rethinking-the-design-of-the-race-and-ethnicity-question-on-surveys-6f9066c69392

Related issue: Ask users for ethnic groups #237

User research findings on Confluence: https://confluence.service.nhs.uk/display/PTC/Ethnicity+question


Auto-completions show twice

Auto-completions get listed twice in MXML Script section.

I cannot reproduce this behavior. Can you provide an example MXML class where you're seeing duplicate items in the list? Thanks!

Hmm, it's all part of a huge Flex 4.6 app. I'll see if I can extract something.
May it have something to do with the fact that I'm settings the "nextgenas.frameworksdk" in a project-specific settings.json and "nextgenas.flexjssdk" in the default settings.json ?

No, when nextgenas.frameworksdk is set, the framework from nextgenas.flexjssdk should be completely ignored. The compiler has a special "flexlib" path that determines where to find the framework SWCs and things.

Still looking for a suitable MXML file, but here's a screenshot first:

Is the text on the right side the same if you highlight the duplicate one? I have code to skip overrides, but maybe it's similar. If we can find two different locations for the same property, that might give us a clue.

Yes, the locations are identical for each pair (acContent, de_DE$..., en_US$...).

There's something interesting that I found:
a) this var gets listed twice:   	[Bindable] public var xml : XML;
b) this var gets listed only once:     public var xml : XML;
Tried switching multiple times and same result each time.

That's a good clue! I'll take a look. Bindable variables get converted to properties, and I could see how that process might contribute to this issue.


SQL Server Service Won't Stay Running on SQL Server 2022

I just tried to install SQL Sever 2022 Developer using this script on a Snapdragon X Elite X1E78100 Qualcomm Oryon and whilst I was able to install it and also enable TCP/IP by comparing the registry entries to another install, as soon as I try to create a new database the service crashes:
Faulting application name: sqlservr.exe, version: 2022.160.1000.6, time stamp: 0x63418705
Faulting module name: ntdll.dll, version: 10.0.26311.5000, time stamp: 0xc508eada
Exception code: 0xc0000005
Fault offset: 0x0000000000184a6c
Faulting process id: 0x1E40
Faulting application start time: 0x1DB382146FA0060
Faulting application path: C:\Program Files\Microsoft SQL Server\MSSQL16.SQLDEVELOPER\MSSQL\Binn\sqlservr.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 009ee8b9-fa0e-48ec-b924-0047c21eee28
Faulting package full name:
Faulting package-relative application ID:

Then:
The MSSQL$SQLDEVELOPER service terminated unexpectedly.

Is there some way to fix this. Is it due to reading folder permissions or something?
Also if there is a way to make it work I'm assuming it's best not to install any cumulative updates.
Thanks
Robin

I have managed to fix the issue.
If the SQL Service does not have folder permissions to the location you are trying to create a new database it just crashes but if you set the permissions as follows then it works:

The service account had to be added as NT Service\MSSQL$SQLDEVELOPER


Combined ion mobility format

Hi MSConvert/Proteowizard team,
based on the request (https://github.com/mzmine/mzmine/issues/2169), I implemented the combined ion mobility format in mzmine.
When testing the results, i noticed that the combineIonMobility option fails to produce correct files as soon as peak picking is enabled.
I ran from the msconvert gui with the following command line:
"C:\Users\Steffen\AppData\Local\Apps\ProteoWizard 3.0.24255.d464da9 64-bit\msconvert.exe" --zlib --combineIonMobilitySpectra --filter "peakPicking vendor msLevel=1-" --filter "titleMaker <RunId>.<ScanNumber>.<ScanNumber>.<ChargeState> File:"""^<SourcePath^>""", NativeID:"""^<Id^>""""  "D:\OneDrive - mzio GmbH\mzio - shared\Example data\Waters\ims_mse_20180205_0099.raw"

The file: https://mzio-my.sharepoint.com/:f:/g/personal/ansgar_korf_mzio_io/EqIT9DiWBzpChMhAatVOvksBZoBj2Q2NUSt51_Nb0UI8Lg?e=ccU1TJ
The resulting file contained only 2 binary data arrays and a single ion mobility value in the scan header, corrupting the file.
The log (Waters):
D:\OneDrive - mzio GmbH\mzio - shared\Example data\Waters\ims_mse_20180205_0099.raw
------------------------------
Starting...
Opening file "D:\OneDrive - mzio GmbH\mzio - shared\Example data\Waters\ims_mse_20180205_0099.raw" for read...
Calculating SHA1 checksum...
Processing...
Writing "D:\OneDrive - mzio GmbH\mzio - shared\Example data\Waters\ims_mse_20180205_0099.mzML"...
[SpectrumList_Waters]: vendor centroiding is not supported for Waters ion mobility data

[SpectrumList_PeakPicker]: vendor centroiding requested but not available for non-vendor formats (and UNIFI); falling back to local maximum peak picker

The log (Agilent):
Writing "D:\OneDrive - mzio GmbH\mzio - shared\Example data\Agilent\LC-DTIMS-MS_6560_PFAS_MS1_only\merged\NISTSERUM.d.DeMP.mzML"...
[SpectrumList_PeakPicker]: vendor centroiding requested but not available for non-vendor formats (and UNIFI); falling back to local maximum peak picker

I tested with files from Waters and Agilent instruments, the results were identical. I can see the log message that the centroiding is not support for ims data, but it works as expected if the combine option is not used.
I suspected the --combineIonMobilitySpectra being mentioned before the peak picking in the commandline being an issue, but it produced the same error.

I feel like the conversion should actually fail if the centroiding is not supported instead of running as normal and producing a file that does not contain the expected properties.
It would be great if the conversion was actually possible with peak picking enabled. From reading the log messages and knowing that peak picking works if the scans are not combined, I would assume that the scans are merged first and then the peakpicking is applied.

Is it possible to change the order of these steps?
Could the issue of the peak picking not being supported be solved by applying it to the mobility scans first and combining the scans afterward?

The reason we're asking for this is that we usually see that the vendor algorithms perform better on their own data than algorithims that are made to work on generic data types. Hence, we try to use vendor peak picking where possible.
Best,
Steffen

The Waters and Agilent SDKs just don't support peak picking for IMS data either for combined or uncombined representation. The CWT peak picking in pwiz works ok for combined spectra but the mobility scans are generally too sparse to be individually peak picked then merged. Because CWT peak picking only considers the m/z and intensity dimensions, it drops the mobility dimension entirely.
I will work on improving the error message to fix the confusing "vendor centroiding requested but not available for non-vendor formats (and UNIFI)" part. Probably just by including Agilent and Waters IMS in the parentheses and removing the [SpectrumList_Waters] message.
I could also make a "use vendor algorithm or abort" option but it's not a high priority.

Ok that's too bad. For some reason i thought that the vendor algorithms would support that, because i thought i did not see the error message in the past when converting. Re-trying it now shows the error though.
Do you have a recommendation for peak picking on profile mobility scan data then?

You can try peak picking on the uncombined spectra with CWT and see how that goes for your data. It's definitely technically possible to merge into the combined representation after that, pwiz is just not set up to do it. Mainly we just don't recommend peak picking on Agilent and Waters IMS data: Skyline just extracts chromatograms from the profile spectra.

Ok, thanks. I'll close the issue then 👍


Something wrong with report

Reports works fine, but for now I got error:
Data successfully retrieved. Starting report calculations.
/home/runner/work/_actions/AlexSim93/pull-request-analytics-action/master/build/index.js:1345
                collection[userLogin][key].commentsConducted =
                                     ^

TypeError: Cannot read properties of undefined (reading 'total')
    at /home/runner/work/_actions/AlexSim93/pull-request-analytics-action/master/build/index.js:1345:38
    at Array.forEach (<anonymous>)
    at /home/runner/work/_actions/AlexSim93/pull-request-analytics-action/master/build/index.js:1342:26
    at Array.forEach (<anonymous>)
    at prepareDiscussions (/home/runner/work/_actions/AlexSim93/pull-request-analytics-action/master/build/index.js:1286:24)
    at /home/runner/work/_actions/AlexSim93/pull-request-analytics-action/master/build/index.js:738:40
    at Array.forEach (<anonymous>)
    at collectData (/home/runner/work/_actions/AlexSim93/pull-request-analytics-action/master/build/index.js:713:26)
    at main (/home/runner/work/_actions/AlexSim93/pull-request-analytics-action/master/build/index.js:18[30](...):55)

Example of config:
name: "PR Analytics"
on:
  workflow_dispatch:
    inputs:
      report_date_start:
        description: "Report date start(d/MM/yyyy)"
        required: false
      report_date_end:
        description: "Report date end(d/MM/yyyy)"
        required: false
jobs:
  create-report:
    name: "Create report"
    runs-on: ubuntu-latest
    steps:
      - name: "Run script for analytics"
        uses: AlexSim93/pull-request-analytics-action@master
        with:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          LABELS: "Report"
          GITHUB_REPO_FOR_ISSUE: "owner"
          GITHUB_OWNER_FOR_ISSUE: "owner"
          GITHUB_OWNERS_REPOS: "owner/owner"
          CORE_HOURS_START: "9:00"
          CORE_HOURS_END: "18:00"
          TIMEZONE: "Europe/Kiev"
          REPORT_DATE_START: ${{ inputs.report_date_start }}
          REPORT_DATE_END: ${{ inputs.report_date_end }}

I have added checking for property in collection. I think It should fix error during report creation. Probably, there were user who just commented on Pull Requests. And I hadn't handled it properly.

@AlexSim93 all fine for now, thanks


Issue #41 Add ROS Installation script Ubuntu

Tested here https://github.com/Vourhey/robonomics_dev/actions/runs/90366820

@Vourhey could you add it into Integration workflow please.

And, It also could be useful to receive a list of user packages that should be added into environment.
PS: probably catckin environment should be turn-on in .bashrc.

The last thing the script does is adds environment to ~/.bashrc
echo "[Setting the ROS evironment]"
echo "source ~/${name_catkinws}/devel/setup.${user_shell}" | tee -a ~/.${user_shell}rc

Is it okay?


fix: query operator $exists does not work correctly with tags (#911)

See #911.

Fix behaviour of $exists operator when applied to fields in tags: {'tags__x': {'$exists': True}} returns True when tags.x is not None
Update documentation accordingly.

Codecov Report
Base: 88.06% // Head: 30.17% // Decreases project coverage by -57.88% :warning:

Coverage data is based on head (d1d8dfd) compared to base (d9e5b26).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #923       +/-   ##
===========================================
- Coverage   88.06%   30.17%   -57.89%
===========================================
  Files         138      149       +11
  Lines        7154     7675      +521
===========================================
- Hits         6300     2316     -3984
- Misses        854     5359     +4505

Flag
Coverage Δ

docarray
30.17% <0.00%> (-57.89%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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

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


Email alerts have stopped working

My email alerts have stopped working. I am still getting the heartbeat notifications and the system appears to be working normally in all other respects.  Can you suggest any trouble shooting steps I can take?

I have the same problem.
If i simulate an alert the reading on the LCD change but no email and the buzzer doesn't sound and no entry in the alert log
I see the change in the csv
In the error log I got this
2020-02-05 12:13:35,**ERROR - Signal not received. Possible cable or sensor problem.
in the process log It seem the process is stopping multiple time
2020-01-11 11:08:03,Process stopped, restarting
2020-01-11 15:54:03,Process stopped, restarting
2020-01-15 23:46:02,Process stopped, restarting
2020-01-28 10:52:03,Process stopped, restarting
2020-02-01 00:36:03,Process stopped, restarting
2020-02-01 16:12:02,Process stopped, restarting
2020-02-01 19:00:03,Process stopped, restarting
2020-02-03 08:02:02,Process stopped, restarting
2020-02-05 12:14:02,Process stopped, restarting
2020-02-08 09:40:03,Process stopped, restarting
``
Thanks
Dan

Are you getting heartbeat notifications?
On Sat, Feb 8, 2020, 10:32 AM lecrote<EMAIL_ADDRESS>wrote:

I have the same problem.
If i simulate an alert the reading on the LCD change but no email and the
buzzer doesn't sound and no entry in the alert log
I see the change in the csv
In the error log I got this
2020-02-05 12:13:35,**ERROR - Signal not received. Possible cable or
sensor problem.
in the process log It seem the process is stopping multiple time
2020-01-11 11:08:03,Process stopped, restarting
2020-01-11 15:54:03,Process stopped, restarting
2020-01-15 23:46:02,Process stopped, restarting
2020-01-28 10:52:03,Process stopped, restarting
2020-02-01 00:36:03,Process stopped, restarting
2020-02-01 16:12:02,Process stopped, restarting
2020-02-01 19:00:03,Process stopped, restarting
2020-02-03 08:02:02,Process stopped, restarting
2020-02-05 12:14:02,Process stopped, restarting
2020-02-08 09:40:03,Process stopped, restarting
``
Thanks
Dan
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/alaudet/raspi-sump/issues/61?email_source=notifications&email_token=ABZWS52NIGUCVWW4UMQU3ATRB3GATA5CNFSM4KJKBTQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELFULMQ#issuecomment-583746994,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZWS52EPD4GH5S75NRTB23RB3GATANCNFSM4KJKBTQQ
.

Sorry but I don't think its the same problem as mine.  I am not seeing anything in the error log.  I am still getting heartbeat emails just not alerts.

Are you getting heartbeat notifications?
…
On Sat, Feb 8, 2020, 10:32 AM lecrote @.***> wrote: I have the same problem. If i simulate an alert the reading on the LCD change but no email and the buzzer doesn't sound and no entry in the alert log I see the change in the csv In the error log I got this 2020-02-05 12:13:35,**ERROR - Signal not received. Possible cable or sensor problem. in the process log It seem the process is stopping multiple time 2020-01-11 11:08:03,Process stopped, restarting 2020-01-11 15:54:03,Process stopped, restarting 2020-01-15 23:46:02,Process stopped, restarting 2020-01-28 10:52:03,Process stopped, restarting 2020-02-01 00:36:03,Process stopped, restarting 2020-02-01 16:12:02,Process stopped, restarting 2020-02-01 19:00:03,Process stopped, restarting 2020-02-03 08:02:02,Process stopped, restarting 2020-02-05 12:14:02,Process stopped, restarting 2020-02-08 09:40:03,Process stopped, restarting `` Thanks Dan — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#61?email_source=notifications&email_token=ABZWS52NIGUCVWW4UMQU3ATRB3GATA5CNFSM4KJKBTQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELFULMQ#issuecomment-583746994>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABZWS52EPD4GH5S75NRTB23RB3GATANCNFSM4KJKBTQQ .

In the raspisump.conf I don't see heartbeat config. I may have an old version.

Make sure you are using the latest version of raspisump.  Backup your
config file and replace it with the latest one manually.  Reenter all of
your values in the new file.  Test with heartbeat notifications.  If they
work simulate an actual alert.  Reassess the issue then.
On Sun, Feb 9, 2020, 10:23 AM lecrote<EMAIL_ADDRESS>wrote:

Are you getting heartbeat notifications?
… <#m_-6491576694174267553_>
On Sat, Feb 8, 2020, 10:32 AM lecrote @.***> wrote: I have the same
problem. If i simulate an alert the reading on the LCD change but no email
and the buzzer doesn't sound and no entry in the alert log I see the change
in the csv In the error log I got this 2020-02-05 12:13:35,**ERROR - Signal
not received. Possible cable or sensor problem. in the process log It seem
the process is stopping multiple time 2020-01-11 11:08:03,Process stopped,
restarting 2020-01-11 15:54:03,Process stopped, restarting 2020-01-15
23:46:02,Process stopped, restarting 2020-01-28 10:52:03,Process stopped,
restarting 2020-02-01 00:36:03,Process stopped, restarting 2020-02-01
16:12:02,Process stopped, restarting 2020-02-01 19:00:03,Process stopped,
restarting 2020-02-03 08:02:02,Process stopped, restarting 2020-02-05
12:14:02,Process stopped, restarting 2020-02-08 09:40:03,Process stopped,
restarting `` Thanks Dan — You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#61
https://github.com/alaudet/raspi-sump/issues/61?email_source=notifications&email_token=ABZWS52NIGUCVWW4UMQU3ATRB3GATA5CNFSM4KJKBTQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELFULMQ#issuecomment-583746994>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZWS52EPD4GH5S75NRTB23RB3GATANCNFSM4KJKBTQQ
.
In the raspisump.conf I don't see heartbeat config. I may have an old
version.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/alaudet/raspi-sump/issues/61?email_source=notifications&email_token=ABZWS5ZGVXLIVEX5MEHDP7LRCANWFA5CNFSM4KJKBTQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELGPIMA#issuecomment-583857200,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZWS5ZJ5GTDAQAMN27JTDLRCANWFANCNFSM4KJKBTQQ
.

I did find the error!
Gmail was blocking email connection.
I unlock it and it is working again.
I will upgrade to the new version for sure.
And I would like to add on the raspberry a freezer temp sensor to.
Thanks
Dan

Great glad you got it working
On Sun, Feb 9, 2020, 11:34 AM lecrote<EMAIL_ADDRESS>wrote:

I did find the error!
Gmail was blocking email connection.
I unlock it and it is working again.
I will upgrade to the new version for sure.
And I would like to add on the raspberry a freezer temp sensor to.
Thanks
Dan
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/alaudet/raspi-sump/issues/61?email_source=notifications&email_token=ABZWS5Y247UR66V6DBRH6RDRCAWCRA5CNFSM4KJKBTQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELGRJWY#issuecomment-583865563,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZWS53GIWQTDQAHP2X34B3RCAWCRANCNFSM4KJKBTQQ
.


Is it possible to use tvm in spark framework???

I want to use tvm to compiler spark pipeline model, is it possible?

Please use https://discuss.tvm.ai/ for general usage discussions


Reports will not generated if javascriptprocessing takes over 10 seconds

Issue Description

Our Dashbords for our monthly Reports can take up to 2 minutes to generate all visualisations. In the native phantomjs with the attached rasterize.js i can create Reports with no problems (modified by adding a waitTime of 120 seconds ) .
rasterize.zip
The sentnl builtin phantomjs acts differently. The delaysettings works, but in the Reports i get an Error "Visualize: unknown error" exactly 10 seconds after opening the Dashboard.

Additional Details:
Kibana 5.6.4 + Sentinl 5.6.4
Native PhantomJS: 2.1.1

I have the same issue with one dashboard that takes between 15 - 40 seconds to load, so sometimes the report is generated without any problem but sometimes i got a report with same error "Visualize: unknown error".
My enviornment: Kibana 5.5.2 + Sentinl 5.5.2
@Crazyigor1987  Do you know what is the limitation ?
Someone know any workaround ?
Thanks

Not really. It has to be an timeout of 10 seconds somewhere within the code, but i cannot find it.
I played much around the settings but found nothing.
My currently workaround is not to use the sentinl plugin for reports. I created a cronjob which create my report with the native phantomjs (with my modified rasterize.js) and send it to me via email. The Sentinl solution would be far better of course...

Not really. It has to be an timeout of 10 seconds somewhere within the code, but i cannot find it.
I played much around the settings but found nothing.
My currently workaround is not to use the sentinl plugin for reports. I created a cronjob which create the pdfreport with the native phantomjs (with my modified rasterize.js) and send it to me via email. The Sentinl solution would be far better of course...

Just to be sure, you already played with the delay option and failed?
            "params": {
              "delay": 5000
            }

That option works i use it for example
"params": {               "delay": 85000 }
But the problem is with the heavy dashboards that take more than, i don't know exactly maybe 30 seconds, the report come with an visualization: unknown error

Hello Imangani,
yes, i played with the delay option and failed.

Hi,
is there any update regarding this problem?

This issue should be addressed in recent releases. Moving to 6.x and cleaning up issues. Please reopen if this is still useful / required. Thanks!


[Bug] vuetify-nuxt-module NuxtApp type interfering with Nuxt's NuxtApp type

Since I updated vuetify-nuxt-module from 0.6.0 to 0.6.5 I have issues with my plugins. Somehow vuetify-nuxt-module is overwriting the return type of UseNuxtApp() so that it only contains $vuetify and not my own provided plugins. See https://github.com/mtdvlpr/reproduction/tree/vuetify for a reproduction.

I Will revert last commit tmr about module augmentation

@userquin thanks! BTW, you're probably already aware, but Vuetify has finally released v3.4.0 so this module needs to update the references from prior lab components.

I'm getting the following error without specifying any labComponents in the config:
Failed to resolve import "vuetify/labs/VDatePicker" from "..\..\..\..\..\..\@nuxt-vuetify-configuration\vuetify-configuration". Does the file exist?


Add File built-in type

I had the same thought as the folks in this discussion, so I took a quick swing at the task.
https://github.com/dry-rb/dry-types/issues/28

Hey @solnic, is similar to what you had imagined for a built-in File type?

Can I please get 👀 on this @timriley @flash-gordon?


Do Image XML  Improper Linking Matter?

All my  locations in the XML files are not set to \object_detection\images\train or \object_detection\images\test directories. Does  location in the XML record matter or is Tensorflow API smart enough to use whatever is inside the Images folders?

I believe the linking does matter. I haven't been able to successfully train a model otherwise.


updated Attunity's link

partner's request to update landing page

Hi @liangjonathan, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (joliang). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;


[desktop] Leave FrostWire 6.8.0 Beta Bug Reports here

If you are testing FrostWire 6.8.0 please leave a detailed report of your issue, preferably with screenshots.
If you manage to install the app and you have issues using it, try running it using the Safe-Mode launcher so that you can paste any console output you may have.
Thank you so much

If the Launcher shows a windows that says the installation fails, this is because the last build requires the host machine to have the Microsoft Visual C++ Redistributable. This is not the case for FrostWire 6.7.x and we're trying to solve the issue by statically including this libraries into the executable, or ultimately not needing such dependencies.

Found the cause of the problem.
The launcher could not start the JDK12's JVM because awt.dll was missing a dependency.
https://bugs.openjdk.java.net/browse/JDK-8203790
My moving jre/bin/msvcp140.dll to the same folder as the java.library.path (the same directory where the launcher .exe lives) the dependency link issue is gone and the installer works.
You can fix this manually in the meantime while we prepare a new build with the .dll in the place where it works.

New macOS installer is now available for 6.8.0!!!!
https://github.com/frostwire/frostwire/releases/tag/frostwire-desktop-6.8.0-build-280-BETA


add feature to query more data when panning chart out of range of queried data

Currently, the chart only displays data fetched from the db given the ranges specified by the datetime pickers in the header. If the user pans the chart outside of the given ranges, the charts will be blank since no new data was fetched.
With this new feature, when the user pans outside of the given range, it should smoothly fetch new data that fills in the empty gap in the graph if there's any new data.

In the above screenshot, the chart's start date stops 1/29/24, but more there is more data in the db isn't queried yet. So with this new feature, the chart should also display the data before 1/29/24. This can be accomplished by utilizing the pan callback to query for new data, if needed.
Resources to look at:
https://www.chartjs.org/chartjs-plugin-zoom/samples/fetch-data.html

I wonder if as a temporary fix we don't allow users to move outside the specified date range.


Update - Broken link in MDX

Updated "How to contribute" URL. Earlier it was giving 404 error.
Describe Changes
Earlier URL was 'https://github.com/markmead/hyperui/blob/main/blog/how-to-contribute'. It was showing 404 error.
U[dated URL: 'https://github.com/markmead/hyperui/blob/main/src/data/posts/how-to-contribute.mdx'

There is no issue here.

Hey @markmead as a first time contributor I was not aware that these files are rendered on a different website. When I tried accessing it from github, it was throwing 404. So I raised a bug and its PR after reading "How to contribute" section. There was no intention of raising a spam PR. Is it possible to remove the spam label this time?

I'll remove it but take in my perspective of this.
You make a PR for a project meaning you have some understanding of it and therefore, you should know it's a website. It also takes 30 seconds to check as the link is on the GitHub repository.
I appreciate you following the "How to Contribute" guide, but when creating an issue don't jump into a PR before acknowledgment from a maintainer. If you had waited you'd have seen my response.

Thanks for the advice, I'll keep these points in mind before raising future PRs.


ChatLocalAI Module Connection Issue: ECONNREFUSED Error

LocalAI version:
Latest version as of June 11, 2023
Environment, CPU architecture, OS, and Version:
Windows 11 Pro (Intel), CPU: i9-10900K, RAM: 32GB
Describe the bug
I am unable to connect to the LocalAI server from Flowise using the ChatLocalAI module in the Conversational Retrieval QA Chain. When I send a request, I receive an ECONNREFUSED error on <IP_ADDRESS>:8080. This occurs despite the server appearing to be running correctly according to the Docker logs, the docker ps command, and the successful response from curl http://localhost:8080/v1/models.
To Reproduce
Clone and set up the LocalAI repository.
Run docker-compose up -d --pull always to start the server.
In Flowise, use the ChatLocalAI module within the Conversational Retrieval QA Chain to send a request.
See ECONNREFUSED error.
Expected behavior
I expected to be able to connect to the LocalAI server at localhost:8080 and send requests from Flowise using the ChatLocalAI module within the Conversational Retrieval QA Chain.
Logs
The Docker logs appear to indicate that the server is starting correctly. There is no obvious error message. The response from curl http://localhost:8080/v1/models is successful.
Additional context
I have installed Flowise and LocalAI locally on my machine, both using Docker. I have also ensured that the appropriate model files are present in the /models directory. Pinecone and OpenAI API are set up correctly. Flowise is accessible at http://localhost:3000/ and LocalAI is accessible at http://localhost:8080/.

Having the same issue. Using docker for both Flowise and LocalAI. Both are installed and work independently of one another but not together.
curl http://localhost:8080/v1/models
{"object":"list","data":[{"id":"openassistant-llama2-13b-orca-8k-3319.ggmlv3.q8_0.bin","object":"model"},{"id":"~BROMIUM","object":"model"}]}(

System Specs
OS Name:                   Microsoft Windows 11 Pro
OS Version:                10.0.22621 N/A Build 22621
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
System Model:              HP ZBook Studio 15.6 inch G8 Mobile Workstation PC
System Type:               x64-based PC
Processor(s):              1 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 141 Stepping 1 GenuineIntel ~2611 Mhz
BIOS Version:              HP T92 Ver. 01.13.01, 3/31/2023
Total Physical Memory:     32,432 MB

GPU 1

	NVIDIA RTX A5000 Laptop GPU

	Driver version:	<IP_ADDRESS>25
	Driver date:	6/10/2023
	DirectX version:	12 (FL 12.1)
	Physical location:	PCI bus 1, device 0, function 0

	Utilization	0%
	Dedicated GPU memory	0.0/16.0 GB
	Shared GPU memory	0.0/15.8 GB
	GPU Memory	0.0/31.8 GB

Inside docker_flowise_1
2023-08-01 17:51:09 2023-08-01 21:51:09 [INFO]: ⬆ POST /api/v1/chatmessage/b9af940f-a720-46d0-899a-309ebf4ff59c
2023-08-01 17:51:09 2023-08-01 21:51:09 [INFO]: ⬆ POST /api/v1/internal-prediction/b9af940f-a720-46d0-899a-309ebf4ff59c
2023-08-01 17:52:37 2023-08-01 21:52:37 [ERROR]: [server]: Error: connect ECONNREFUSED <IP_ADDRESS>:8080
2023-08-01 17:52:37 Error: connect ECONNREFUSED <IP_ADDRESS>:8080
2023-08-01 17:52:37     at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16)
2023-08-01 17:52:37 2023-08-01 21:52:37 [INFO]: ⬆ POST /api/v1/chatmessage/b9af940f-a720-46d0-899a-309ebf4ff59c

Inside LocalAI-Docker

2023-08-01 03:38:31 CPU info:
2023-08-01 03:38:31 model name  : 11th Gen Intel(R) Core(TM) i9-11950H @ 2.60GHz
2023-08-01 03:38:31 flags               : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology cpuid pni pclmulqdq vmx ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves avx512vbmi umip avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg avx512_vpopcntdq rdpid movdiri movdir64b avx512_vp2intersect flush_l1d arch_capabilities
2023-08-01 03:38:31 CPU:    AVX    found OK
2023-08-01 03:38:31 CPU:    AVX2   found OK
2023-08-01 03:38:31 CPU:    AVX512 found OK
2023-08-01 03:38:31 @@@@@
2023-08-01 03:38:32
2023-08-01 03:38:32  ┌───────────────────────────────────────────────────┐
2023-08-01 03:38:32  │                   Fiber v2.48.0                   │
2023-08-01 03:38:32  │               http://<IP_ADDRESS>:8080               │
2023-08-01 03:38:32  │       (bound on host <IP_ADDRESS> and port 8080)       │
2023-08-01 03:38:32  │                                                   │
2023-08-01 03:38:32  │ Handlers ............ 31  Processes ........... 1 │
2023-08-01 03:38:32  │ Prefork ....... Disabled  PID ................ 14 │
2023-08-01 03:38:32  └───────────────────────────────────────────────────┘
2023-08-01 03:38:32
2023-08-01 03:38:31 7:38AM DBG no galleries to load
2023-08-01 03:38:31 7:38AM INF Starting LocalAI using 4 threads, with models path: /models
2023-08-01 03:38:31 7:38AM INF LocalAI version: v1.23.0-19-gae36bae (ae36b

Having the same issue here.

Having the same issue here. Tried running on different port with same result.

Same here, getting the same error and switching to a different port won't fix the problem. Same OS and similar hardware as the creator of this issue.

I was able to resolve this issue by using 'http://host.docker.internal:8080/v1" as the Base Path for the ChatLocalAI module in Flowise.

I had the same issue - and it took me some time to find out why:
looks like a trailing slash in Base Path leads to this error.
Would it perhaps make sense to remove a trailing slash close to
https://github.com/FlowiseAI/Flowise/blob/main/packages/components/nodes/chatmodels/ChatLocalAI/ChatLocalAI.ts#L80 with something like
var lastChar = basePath.substr(-1);
if (lastChar === '/') {
  basePath = basePath.substring(0, basePath.length - 1);
}

(yes, there is probably a more elegant solution. But these lines I did test)

The probelm seems to be that LocalAI allows traffic on http://localhost:8080 but not on http://<IP_ADDRESS>:8080
When configuring the ui, http://localhost:8080/v1 can be configured, but by the time the request is made, it has been transformed to http://<IP_ADDRESS>:8080/v1 which is not allowed.
There should be a configuration for allowing other domains to be used to access LocalAI. If there is such a setting or environment variable already, could somebody please point that out.

The probelm seems to be that LocalAI allows traffic on http://localhost:8080 but not on http://<IP_ADDRESS>:8080
When configuring the ui, http://localhost:8080/v1 can be configured, but by the time the request is made, it has been transformed to http://<IP_ADDRESS>:8080/v1 which is not allowed.
There should be a configuration for allowing other domains to be used to access LocalAI. If there is such a setting or environment variable already, could somebody please point that out.

Actually this is completely false. My two services were running in different containers, and the front-end was calling its own backend and then proxying that call to the LocalAI api. Inside the docker container, localhost means itself, and not the host. So @OrsonAround was spot on with his advice -- I should be using http://host.docker.internal:8080 as my host
Still doesn't work for some reason, but that is unrelated to the issue described here.
BONUS: there is a config for allowing other domains on LocalAi, which defaults to * and is plain as day in the .env file:
CORS_ALLOW_ORIGINS=*

I was able to resolve this issue by using 'http://host.docker.internal:8080/v1" as the Base Path for the ChatLocalAI module in Flowise.

absolutely the solution!

where can I find the connect credentials for ChatLocalAI node in Flowise?


Is there any kql/cli or any method which can be used to proactively monitor the number of GB scanned by storage malware scanning feature?

Below is a really frequently asked question asked by customers. Can we get some documentation on it added?
"Is there any kql/cli or any method which can be used to proactively monitor the number of GB scanned by storage malware scanning feature?"
is it possible? yes/no
and so on.

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

ID: a516ba36-643a-e308-ca42-3cd788bb3488
Version Independent ID: c03780b4-a6f5-0eaa-68fe-100ab085bffa
Content: Common questions - Defender for Storage - Microsoft Defender for Cloud
Content Source: articles/defender-for-cloud/faq-defender-for-storage.yml
Service: defender-for-cloud
GitHub Login: @dcurwin
Microsoft Alias: dacurwin

@ankkp
Thanks for your feedback! We will investigate and update as appropriate.

Hello @ankkp
It is possible to proactively monitor the number of GB scanned by the storage malware scanning feature in Azure.
One way to do this is by using Azure Monitor to collect and analyze logs from the storage account. You can use Kusto Query Language (KQL) to query the logs and extract the necessary information, such as the number of GB scanned by the malware scanning feature.
To set up monitoring for the storage account, you can follow these steps:

Enable diagnostic logging for the storage account. You can do this by going to the storage account in the Azure portal, selecting "Diagnostic settings" under the "Monitoring" section, and then configuring the desired diagnostic settings.

Create a Log Analytics workspace in Azure Monitor. This workspace will be used to collect and analyze the logs from the storage account.

Configure the storage account to send its diagnostic logs to the Log Analytics workspace. You can do this by going to the storage account in the Azure portal, selecting "Diagnostic settings" under the "Monitoring" section, and then configuring the desired destination for the logs.

Use KQL to query the logs and extract the necessary information. For example, you can use the following query to get the total number of GB scanned by the malware scanning feature over the last 24 hours:

StorageBlobLogs
| where TimeGenerated > ago(24h)
| where OperationName == "Microsoft.Storage/storageAccounts/blobServices/containers/blobs/write"
| where MalwareDetectionResult == "Detected"
| summarize TotalScannedGB = sum(ScannedBytes) / 1024 / 1024 / 1024 by bin(TimeGenerated, 1h)

This query uses the StorageBlobLogs table to filter for write operations to blobs that were detected as malware, and then summarizes the total number of GB scanned by the malware scanning feature by hour.
I hope this helps! If there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

@ankkp
We are going to close this thread, if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.
#Please-close

@Naveenommi-MSFT
Can you please reopen this?
"MalwareDetectionResult" does not exist in StorageBlobLogs. | ref StorageBlobLogs
Again, the question is total GB of data scanned. No total size of malware files detected.

@ankkp
I reopen this issue, I've delegated this to content author @dcurwin, who will review it and offer their insightful opinions.

@ankkp Thanks for your question. The product team is investigating this capability, and the documentation will be updated in accordance with that investigation.
#please-close

#please-close

@ankkp I would like to understand a bit more what the expectation is - do you want to get this number (GB scanned) for a specific storage account or for all storage accounts in a subscription or tenant?

@yoavfr for monitoring purpose it would be best at storage level (so, custom alerts can be triggered for data capping threshold).
if possible, it would be great to have this option for subscription and tenant level to verify/estimate the billing.

@ankkp Alerts (in Microsoft Defender for Cloud) are currently generated when 75% and 100% of cap is reached per storage account. Does that address the requirement?

@yoavfr Yes, We are aware of that. but that is not the question.
question is if there is any proactive way to monitor the usage(GB Scanned).


Check for the MySQL open files limit

https://access.redhat.com/solutions/1598733
This checks whether the open-files-limit limit passed to MySQL/MariaDB is greater or equal to 16384 (the recommended value).

You can get the open-file-limit much more reliably by querying mysql server at runtime:
select @@global.open_files_limit;

Ooh, nice! I've updated the pull request.

It can be useful to add the current value for open_files_limit to the error message.
Looks a lot better now :+1:

Good point. Added.

Actually, I realized there is an ansible module to do just that: http://docs.ansible.com/ansible/mysql_variables_module.html. It adds a dependency on MySQL-python but it should already be satisfied on the controller nodes.
Would you mind changing once again?
Also, I realized you used the shell module while you should really have used the command module. The shell module should be avoided when possible.

All right, this should be fixed up & rebased now.
I was originally using shell pipes which don't work with the command module, but you're right that when that was removed, I should have switched to command.


[colm] need a syntax for constructing tokens with a str

Currently using parse, which is just way too much overhead for just a token.

Rather than use a syntax it would make more sense to optimize parse for the case where the target type is a token. Could just invoke the scanner and add some extra steps.


[ros2] Various updates

Fix changelogTemplate
Remove latest column (This column only repeat what can be found in releaseCycle / releaseDate)
Normalize page (#2124)

Would http://docs.ros.org/en/humble/Releases/Release-Humble-Hawksbill.html be a better link than https://docs.ros.org/en/rolling/Releases/Release-Humble-Hawksbill.html?
The rolling documentation might contain unrelease stuff?

You are right, this link is better. Don't know if it contains unreleased stuff, but anyway the "rolling" link says: You're reading the documentation for a development version. For the latest released version, please have a look at Humble..
Other release cycles also have their own link:

https://docs.ros.org/en/galactic/Releases/Release-Galactic-Geochelone.html
https://docs.ros.org/en/foxy/Releases/Release-Foxy-Fitzroy.html.
https://docs.ros.org/en/eloquent/Releases/Release-Eloquent-Elusor.html
https://docs.ros.org/en/dashing/Releases/Release-Dashing-Diademata.html
https://docs.ros.org/en/crystal/Releases/Release-Crystal-Clemmys.html

Unfortunately last two release cycles do not have a similar link:

https://docs.ros.org/en/bouncy/Releases/Release-Bouncy-Bolson.html
https://docs.ros.org/en/ardent/Releases/Release-Ardent-Apalone.html

I updated the changelogTemplate and keep https://docs.ros.org/en/rolling/Releases/Release-Bouncy-Bolson.html and https://docs.ros.org/en/rolling/Releases/Release-Ardent-Apalone.html for the last two.


'import' and 'export' may only appear at the top level

I'm having trouble bundling handlebars. On bundling I get the following error:
Error parsing /myproject/node_modules/handlebars/dist/cjs/handlebars/no-conflict.js: 'import' and 'export' may only appear at the top level (4:0) in /myproject/node_modules/handlebars/dist/cjs/handlebars/no-conflict.js

My first try to fix this, was to use the named exports feature. But although I've explicitly specified handlebars as a named export, it seems to be ignored and I always get the same error message as above.
Here is my setup:
// rollup.config.js
const rollup = require('rollup');
const babel = require('rollup-plugin-babel');
const replace = require('rollup-plugin-replace');
const commonjs = require('rollup-plugin-commonjs');
const globals = require('rollup-plugin-node-globals');
const nodeResolve = require('rollup-plugin-node-resolve');

export default {
  entry: 'scripts/main.js',
  dest: 'public/assets/js/bundle.js',
  format: 'iife',
  moduleName: 'test',
  sourceMap: true,
  plugins: [
    globals(),
    nodeResolve({
      jsnext: true,
      main: true,
      browser: true,
      preferBuiltins: false
    }),
    commonjs({
      include: ['node_modules/**'],
      namedExports: {
        'node_modules/handlebars/dist/handlebars.min.js': ['handlebars']
      }
    }),
    babel({
      exclude: ['node_modules/**'],
      runtimeHelpers: true
    }),
    replace({
      'process.env.NODE_ENV': JSON.stringify(process.env.NODE_ENV)
    })
  ]
}

// main.js
import Handlebars from 'handlebars';

console.log(Handlebars.compile('
Hello World
');

// .babelrc
{
  "presets": [
    ["es2015", {
      "modules": false
    }]
  ],
  "plugins": [
    "external-helpers",
    "transform-object-rest-spread"
  ]
}

So, there are a few things going on here, it turns out. The error message you saw was caused by this plugin attempting to transform a module which had an import declaration added to it by rollup-plugin-node-globals. Moving that plugin to the bottom (so that the CommonJS module was converted to ES6 before the import got added) fixed that issue, but created another (which would be fixed by https://github.com/calvinmetcalf/rollup-plugin-node-globals/pull/3. A workaround in the meantime is to ensure that rollup-plugin-node-globals comes before rollup-plugin-node-resolve in the plugins array).
After that, the bundle builds fine. But it doesn't run. Because path and fs are required from somewhere, they're treated as external dependencies, which means the IIFE expects them as arguments...
(function (fs, path) {
/* bundle goes here */
}(fs, path));

...but path and fs don't exist as variables on the page, so it blows up. Using rollup-plugin-node-builtins we can add a browser-friendly path (obviously only some of its functions work outside of Node), but there's no browser equivalent of fs.
We can use the globals option to replace those modules with whatever expression we like (since presumably path and fs are only there for some Node-specific functionality):
// rollup.config.js
export default {
  entry: 'scripts/main.js',
  dest: 'public/assets/js/bundle.js',
  ...,
  globals: { fs: '{}', path: '{}' }
};

That results in this:
(function (fs, path) {
/* bundle goes here */
}({}, {}));

But then we get this error...

bundle.js:3828 Uncaught ReferenceError: require is not defined

...because of this line inside the source-map module:
if (typeof define !== 'function') {
    var define = amdefine_1(module, require);
}

In case you weren't familiar with it, amdefine is a package that allows you to write AMD modules and have them converted into CommonJS modules at runtime by adding that snippet. It's exactly as ridiculous an idea as it sounds, and it means your bundle has to include this dead weight (in fact, now that I investigate, that's the only reason the bundle needs path – so that it doesn't need to implement dirname. Literally the only reason!). So we're attempting to transform a CommonJS module that is really an AMD module that only gets converted at runtime. Teetering atop this house of cards, it's a wonder that anything stable was ever built.
Of course, we don't actually need the source-map stuff, as evidenced by this block:
try {
  /* istanbul ignore next */
  if (typeof define !== 'function' || !define.amd) {
    // We don't support this in AMD environments. For these environments, we asusme that
    // they are running on the browser and thus have no need for the source-map library.
    let SourceMap = require('source-map');
    SourceNode = SourceMap.SourceNode;
  }
} catch (err) {
  /* NOP */
}

Rollup doesn't have the luxury of running the code to find out what's necessary and what isn't, so it has to import source-map. But we can disable it by modifying our config like so:
// rollup.config.js
plugins: [
  ...,
  nodeResolve({
    jsnext: true,
    main: true,
    browser: true,
    preferBuiltins: false,
    skip: [ 'source-map' ]
  })
],
external: [ 'source-map' ],

Then we hit another 'require is not defined' error caused by this code:
if ('function' !== 'undefined' && require.extensions) {
  require.extensions['.handlebars'] = extension;
  require.extensions['.hbs'] = extension;
}

Another runtime check, this time to see if we want to make it possible for Node users to compile templates at runtime by doing var compiled = require('template.hbs'). Which isn't even remotely a concern for browser users, but we still have to deal with it. (The 'function' !== 'undefined') thing is to allow UMD modules to work with this plugin.)
We can get rid of that whole block by replacing require.extensions with null:
// rollup.config.js
plugins: [
  ...,
  replace({
    'require.extensions': 'null'
  })
]

And after that, it works. Whether it will continue to work as you use more of Handlebars remains to be seen.
So the blame is shared between Rollup (for making it too easy for plugins to be in the wrong order) and the ghosts of module systems past. I wouldn't judge you for using Rollup to bundle your own code as a CommonJS module, then handing the result off to Browserify or Webpack to deal with the various layers of insanity that have accreted in the Node ecosystem over the past few years. There's also Rollupify, if you wanted to take a Browserify-first approach.
I've put a working version of the example in this repo, so you can poke and prod it: https://github.com/Rich-Harris/rollup-plugin-commonjs-issue-90
Thanks for coming on this wild adventure with me, hope it helps!

@Rich-Harris Wow, didn't know it was this bad with the dependencies! That is some quality investigation of yours! Really appreciate your detailed response.
Regarding the complexity of the bundling layers I'm totally on your side.
I agree that this is more the fault of library authors and nothing which rollup should invest time in supporting. I can't wait for the day when most modules are es6 based. Thanks for an awesome bundler! We've been using it with great success at work!
Thanks for the working repo, I can only imagine how much time it took to step through all these corner cases 🎉


Sandbox - Kafka Error

null_resource.cdh-setup (remote-exec): 120
null_resource.cdh-setup: Still creating... (11m20s elapsed)
null_resource.cdh-setup (remote-exec): Starting CDH Manager...
null_resource.cdh-setup (remote-exec): [QuickStart] Shutting down CDH services via init scripts...
null_resource.cdh-setup (remote-exec): kafka-server: unrecognized service
null_resource.cdh-setup: Still creating... (11m30s elapsed)
null_resource.cdh-setup: Still creating... (11m40s elapsed)

This seems to be what's causing the kafka error: docker exec -it ${container} /home/cloudera/cloudera-manager --express

This seems to be a docker container issue specific to Cloudera, not anything we did wrong.  Closing....


About Fitting the local ground plane

Thank you for your excellent work!
I have two questions for you.

Is the lidarframelist holding the poses in the lidar coordinate system?
What is the logic in Cost_NavState_PR_Ground? Is the P and Q (translation and rotation) in lidarframelist converted to the world coordinate system? And how is the local ground plane calculated?

I am new in this field, and the transformation makes me confused. I'm sorry for all the questions and look forward to your reply!

poses aligned with the lidar coordinate system. If so, should it be an identity matrix?
For the local ground, I suggest you look in LOAM or Lego-LOAM. Most LOAM follows that typical logic.

Bests


[SYS_TEST] HTX stress test

Code to stress the system using HTX ..

Code is in place.. system test and FVT team are running the test now .. closing this.


filelog: Multiline merging mixes up logs from different files

this works fine.
operators:
    - default: clean-up-log-record
      routes:
      - expr: ($$resource["k8s.namespace.name"]) matches ".*" && ($$resource["k8s.container.name"])
          == "loggen"
        output: .*_loggen
      - expr: ($$resource["k8s.container.name"]) == "loggen2"
        output: loggen2
      type: router
    - combine_field: log
      id: .*_loggen
      is_first_entry: '($.log) matches "num: \\d+0\\s"'
      output: clean-up-log-record
      type: recombine
    - combine_field: log
      id: loggen2
      is_first_entry: '($$.log) matches "num: \\d+0\\s"'
      output: clean-up-log-record
      type: recombine
    - id: clean-up-log-record
      ops:
      - move:
          from: log
          to: $
      type: restructure

because loggen container and loggen2 container is separately routed to its own recombine operator.
but with configurations like this one
operators:
    - default: clean-up-log-record
      routes:
      - expr: ($$resource["k8s.namespace.name"]) matches ".*" && ($$resource["k8s.container.name"])
          == "loggen.*"
        output: .*_loggen.*
      type: router
    - combine_field: log
      id: .*_loggen.*
      is_first_entry: '($.log) matches "num: \\d+0\\s"'
      output: clean-up-log-record
      type: recombine
    - id: clean-up-log-record
      ops:
      - move:
          from: log
          to: $
      type: restructure

they get mixed up

Do both containers log to the same file? Can you provide input and output samples?

sorry for late reply. it is logging to a separate files. I can't reproduce it so i think it was a misconfiguration. Thank you.

reopening this. similar issue is reported. https://github.com/signalfx/splunk-otel-collector-chart/issues/309

I also see it now.

num: 100061 | loggen-tjh79 | 2021-11-19T21:23:21.643933 | rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr  this is from log generator.  i have it merging at every 10 events.
but 2021/11/19 21:23:22 EPS: 0 this like is from another pod

for more context, this works fine.
operators:
    - default: clean-up-log-record
      routes:
      - expr: ($$resource["k8s.namespace.name"]) matches ".*" && ($$resource["k8s.container.name"])
          == "loggen"
        output: .*_loggen
      - expr: ($$resource["k8s.container.name"]) == "loggen2"
        output: loggen2
      type: router
    - combine_field: log
      id: .*_loggen
      is_first_entry: '($.log) matches "num: \\d+0\\s"'
      output: clean-up-log-record
      type: recombine
    - combine_field: log
      id: loggen2
      is_first_entry: '($$.log) matches "num: \\d+0\\s"'
      output: clean-up-log-record
      type: recombine
    - id: clean-up-log-record
      ops:
      - move:
          from: log
          to: $
      type: restructure

because loggen container and loggen2 container is separately routed to its own recombine operator.
but with configurations like this one
operators:
    - default: clean-up-log-record
      routes:
      - expr: ($$resource["k8s.namespace.name"]) matches ".*" && ($$resource["k8s.container.name"])
          == "loggen.*"
        output: .*_loggen.*
      type: router
    - combine_field: log
      id: .*_loggen.*
      is_first_entry: '($.log) matches "num: \\d+0\\s"'
      output: clean-up-log-record
      type: recombine
    - id: clean-up-log-record
      ops:
      - move:
          from: log
          to: $
      type: restructure

they get mixed up

I think in the recombine operator, everything is store in batch. it is just an array.
I think we need to make it into a map. make(map[string][]*entry.Entry)
Add separatorField parameter that this recombine operator will be applied separated.  (good default would be filename)
and get string of separatorField and use it as s key field for batch Map.

@djaglowski Any suggestions?

Thanks for putting your thoughts into it. I can take a stab at it if no one yet started.


I don't think this header exists anymore in VS2019

When I try to
#include <allocators>

in a new C++ console app, I get a C1083 error:
Cannot open include file: 'allocators': No such file or directory
If so, this section of the documentation should be removed from Version = Visual Studio 2019.

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

ID: 4a61622c-5c78-5983-46a7-a1eda77c2225
Version Independent ID: 1077068c-1f4a-a305-d6c0-d9a54e33e7c9
Content: <allocators>
Content Source: docs/standard-library/allocators-header.md
Product: visual-cpp
Technology: cpp-standard-libraries
GitHub Login: @TylerMSFT
Microsoft Alias: twhitney

Hi @davidmatson, I'm looking into this.

@davidmatson, You are correct--this header was removed.
Unfortunately, the filter won't work with this topic, so I updated the topic to indicate when it was deprecated (VS 2019 v 16.3)
#please-close

@TylerMSFT  - I don't think deprecated is quite the correct term - I think removed would be more accurate. From bing defining deprecate:
"(chiefly of a software feature) be usable but regarded as obsolete and best avoided, typically due to having been superseded."
But I'd suggest considering a more extensive approach. There are almost 2 dozen doc pages impacted, and having this sentence on just one of them may mean in a lot of cases it is missed.
Additionally, this content appears under C++ Standard Library reference/header files, but it is not a C++ Standard Library header file or part of the C++ Standard.
Instead, could all of this content either: a) be removed, or b) be moved to a different location in the TOC (ideally, a place where the filter will work, or if not, at least under a node named something like Previous Visual Studio Versions)?

There are other headers that are showing up in this list that shouldn't. Some of them may also have been deleted, and if not, I think all should be move out from the C++ Standard Library header file list:

cvt-wbuffer
cvt-wstring
hash_map
hash_set
(probably others)

Could we compare the TOC (left side):
https://docs.microsoft.com/en-us/cpp/standard-library/cpp-standard-library-header-files?view=vs-2019
With the list of Standard C++ header files here:
https://en.cppreference.com/w/cpp/header
And move (or remove) any header files we have that are not in that second list?

I'm not sure why this got closed. Reopening.

Note to self: see mail from David, 4/26/2020, for some background.

We are in the process of moving away from GitHub issues for C++ documentation (we still accept pull requests). For details, please see Announcing a new way to give feedback on Microsoft Learn This issue will be closed after it is copied to an internal tracking system.


ARROW-17525: [Java] Read ORC files using NativeDatasetFactory

Support ORC file format in java Dataset API

@davisusanibar or @lwhite1, would either of you like to take a look here?

Hi @davisusanibar or @lwhite1
Any comments?
I am ready to work on next PRs related to #14039 after merge of current PR into master branch

Hi @davisusanibar or @lwhite1 Any comments? I am ready to work on next PRs related to #14039 after merge of current PR into master branch

Hi @igor-suhorukov let me review this today, sorry for the long time

Integration test failure should be unrelated, see #14069

Thank you @lidavidm and @davisusanibar
Yes, looks like by CI log details


BrokenPipeError: [Errno 32] Broken pipe

When I cloned the repository and ran main.py (without changing anything) I get this output:
 not enough values to unpack (expected 2, got 0)
 ==> Preparing data..
 Files already downloaded and verified
 Files already downloaded and verified
 Training with dataset CIFAR10 and 10 classes
 ==> Building model..
 ==> Checkpoints will be saved to: ./checkpoint/ckpt-CIFAR10-ResNet18.pth
 classes:	(callable)

 Epoch: 0
 Traceback (most recent call last):

File "<ipython-input-7-f9bd8031870b>", line 1, in <module>
  runfile('C:/Users/Matthew Chen/Documents/GitHub/neural-backed-decision-trees/main.py', wdir='C:/Users/Matthew Chen/Documents/GitHub/neural-backed-decision-trees')

File "C:\Users\Matthew Chen\Anaconda3\lib\site-packages\spyder_kernels\customize\spydercustomize.py", line 827, in runfile
  execfile(filename, namespace)

File "C:\Users\Matthew Chen\Anaconda3\lib\site-packages\spyder_kernels\customize\spydercustomize.py", line 110, in execfile
  exec(compile(f.read(), filename, 'exec'), namespace)

File "C:/Users/Matthew Chen/Documents/GitHub/neural-backed-decision-trees/main.py", line 315, in <module>
  train(epoch, analyzer)

File "C:/Users/Matthew Chen/Documents/GitHub/neural-backed-decision-trees/main.py", line 227, in train
  for batch_idx, (inputs, targets) in enumerate(trainloader):

File "C:\Users\Matthew Chen\Anaconda3\lib\site-packages\torch\utils\data\dataloader.py", line 279, in __iter__
  return _MultiProcessingDataLoaderIter(self)

File "C:\Users\Matthew Chen\Anaconda3\lib\site-packages\torch\utils\data\dataloader.py", line 719, in __init__
  w.start()

File "C:\Users\Matthew Chen\Anaconda3\lib\multiprocessing\process.py", line 112, in start
  self._popen = self._Popen(self)

File "C:\Users\Matthew Chen\Anaconda3\lib\multiprocessing\context.py", line 223, in _Popen
  return _default_context.get_context().Process._Popen(process_obj)

File "C:\Users\Matthew Chen\Anaconda3\lib\multiprocessing\context.py", line 322, in _Popen
  return Popen(process_obj)

File "C:\Users\Matthew Chen\Anaconda3\lib\multiprocessing\popen_spawn_win32.py", line 89, in __init__
  reduction.dump(process_obj, to_child)

File "C:\Users\Matthew Chen\Anaconda3\lib\multiprocessing\reduction.py", line 60, in dump
  ForkingPickler(file, protocol).dump(obj)

  BrokenPipeError: [Errno 32] Broken pipe

I'm not sure if I downloaded all the packages correctly, but this seems to be an error where the request to some server is blocked/timed out?

Nevermind! I realized this is a Windows-only issue (https://pytorch.org/tutorials/beginner/blitz/cifar10_tutorial.html). In order to prevent this error you'll have to change num-workers from 2 to 0.

Nevermind! I realized this is a Windows-only issue (https://pytorch.org/tutorials/beginner/blitz/cifar10_tutorial.html). In order to prevent this error you'll have to change num-workers from 2 to 0.


Fix workspace arm template

The workspace arm template did not account for the endpoints that are supposed to be created when a workspace hub is created. I added some copied template values from the working UI's ARM template, then adjusted the python code that injects values into it to perform the following:

Create 3 endpoints if no endpoint resource id is provided based on a new AI service resource that's created as part of the hub creation for this purpose.
Create 3 endpoints pointing to an existing AI Service if one is supplied via a new endpoint_resource_id keyword argument in the workspace hub create operation
Create a single AOAI endpoint pointing to an existing AOAI resource if such an ID is provided via the legacy byo_open_ai_resource_id kwarg.

All of this only occurs for hubs as specified in the template logic, so normal workspaces shouldn't be affected.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-ml

Non-blocking question: What's the significance of 3 for the number of endpoints?


[9.x] Use Guzzle to resolve the URL against the base URL

Problem
I've created an HTTP macro to easily work with an API, just like the documentation suggests. The response of this API is paginated and the URL of the next page is returned in the response. This URL is absolute and making a request with a base URL and an absolute URL currently results in requests like https://api.github.com/https://api.github.com/organizations/laravel. Guzzle allows you to set a base URL and use absolute URL's in conjuction, so I'd expect this client to support that too.
Solution
Guzzle has quite some logic to resolve the URL against the base URL, so I've chosen to use the same logic. If you prefer not to use an external dependency and would like to use some other logic, please let me know!

I've converted it to draft as I've found some breaking changes;

baseUrl
Url
Current result
New result

http://foo.com
/bar
http://foo.com/bar
http://foo.com/bar

http://foo.com/foo
/bar
http://foo.com/foo/bar
http://foo.com/bar

http://foo.com/foo
bar
http://foo.com/foo/bar
http://foo.com/bar

http://foo.com/foo/
bar
http://foo.com/foo/bar
http://foo.com/foo/bar

http://foo.com
http://baz.com
http://foo.com/http://baz.com
http://baz.com

http://foo.com/?bar
bar
http://foo.com/?bar/bar
http://foo.com/bar

Guzzle follows the rules described in RFC 3986, but as seen above that will be a breaking change. We can focus on fixing the issue with absolute URL's now and move this change to 10.x?

Retargeted to 10.x and created #41307 as a fix for the base URL + absolute URL issue.


Fix failing FlagsTest on Windows

On Windows, the FlagsTest.dumpOpenSslInfoDoNotThrowStackOverFlowError() test will fail because it cannot find Flags.class in the classpath (url will be null). This PR replaces File.separatorChar with '/' so the class(es) can be found successfully.
I'm not sure why this was fine on CI. Maybe it's a problem on my PC?

Not sure why it has failed

When loading a class/resource via a class loader we must always use /.

When loading a class/resource via a class loader we must always use /

TIL 😄


deprecate windows_package and forward to new provider if running 12.6 or higher

LGTM :+1:

If the windows cookbook is included for any reason, won't this throw the warning every time?
Since the Chef Core version is named windows_package just like the cookbook windows_package, the cookbook version will override the core version and cause the warning to be thrown? The only way to get rid of the warning would be to remove the windows cookbook from the run list so the core version of windows_package doesn't get overridden, correct?

@Tech356 you could get around it by using package instead of windows_package. On a windows system that will use the core windows_package without going through the cookbook.

:+1:


Added counting sort implementation in Python

Can you add the "hacktoberfest" label to the repo or "hacktoberfest-accepted" label to my PR?


When scrolling up too fast in a playlist, the screen goes back to the "My Playlists" section

OS:
Mac OS Sierra
Issue Descriptions:
Whenever I scroll up too fast in a playlist, it brings me back to the "My Playlists" section.
It may have to do with the size of my playlists (the issue I have it most commonly in my "Thumbs up" playlist with 1500 songs...)
By scrolling up, I mean using the touchpad to scroll up with two fingers, not clicking and holding the scrollbar.
With just one flick downwards to go up in the playlist its fine, but with a lot in succession is when it brings me back to my playlists.
I think it may have to do with scrolling at an angle, ie not flicking your fingers in a straight line up-down, but instead angled slightly. If the issue is that I'm angling my fingers too much then this is not an issue with the software, its an issue with me (although I haven't experienced this issue in any other piece of software so I don't think that's the case)
Steps to Reproduce:
Simple!

Open the music player
Go to one of your playlists
Go to the bottom of the playlist
Scroll up with two fingers on the trackpad

It'll be the two finger swipe navigation we have in this app.  You're super fast swipe is probably slightly angled and is being ndetected as a horizontal swipe because it's so fast.


Use ImagedProvider for gplus oauth2 provider (#18504)

Backport of #18504

(it's a regression but since v1.16.0 got released its a bugfix for the next version)


migrate to null safety

migrate to null safety
add types to getters
dartfmt
rev pubspec version

This is in prep for migrating https://github.com/flutter/flutter-github-scripts.dart to null safety.
@csells

closing as we can just remove the use of this package from the flutter repo scripts

even better!