System Logs Module Problem

Using the system logs module, there is a problem: If I open the configuration for the module, I can add 'other log files to show'.
I have 5 additional files there, each one in a separate line. Saving and closing the configuration yields the new logfiles, and I can use them. But every time, when I open the configuration again, all the logfile paths are concatenated in a single line, without anything in between. If I change something other than the logfiles, I loose my logfiles, because it becomes an unreadable long string, which makes no sense.
So the /n symbols are not preserved, and using semicolons or something like this does not work also. I need to edit this window every time I open the configuration and save it afterwards.
To repeat the bug:
Add more than one log files strings (i.e. /var/log/something1.log and /var/log/something2.log) to the window, each logfile in one line. Save and close, and you will have the logfiles pinned. Then try to change something again in the configuration, and your log file strings will become one long string.
I am using 19.10-beta-1 Authentic Thema.
Very nice theme, btw. ! :)

Hi,
Thank you for reporting.
What would happen if you switched to Gray Theme and tried it there?

I confirm that this is the theme bug.
I'll fix it. Thanks.

It's fixed. Thanks.
It affected things globally, so this fix will be applied to all configuration pages, that are wrapped into accordions by the theme.


CredentialManageApi -  When the incoming CSP is openstack, an error 'Plugin Not Found' is reported

1.getCredentialTypesByCsp()      When the incoming CSP is openstack, an error 'Plugin Not Found' is reported. 2.getCredentialCapabilitiesByCsp()    Same error.
3.getCredentialOpenApi()     Same error.

Fixed. Need to configure 'OS_AUTH_URL' in the system variable.


Full support for dask arrays

We should consider supporting DaskArray throughout the pipeline, in faim_hcs.io.* and in faim_hcs.Zarr.
For example, if the assemble_fn parameter for the get_well_image_C[Z]YX functions can be a Callable accepting dask arrays and returning a single (stacked/blocked) dask array, the function should not create a np.zeros() array first and fill it with the tile pixel data, but instead keep a list of arrays and use da.stack() with appropriate chunking options to create the CYX or CZYX output.
This would allow the pixel reading operation to be deferred until the writing step in Zarr.write_image_and_metadata.

Related:

metadata handling could (should?) be separated from the pixel data, as in some formats (e.g. CellVoyager) the metadata are already completely separate (.mlf etc.) from the pixel data (e.g. .tif without spatial calibration).
a remaining question is how to deal with the histograms (UIntHistogram): should we still read all pixel values to create them immediately when processing/stacking the image, or rather delay creation until we actually write the well/field into the zarr store?

Solved with #58 and #59.


Fix issue with alerts causing errors in playlist loads

Fixes #602

Will this be merged? Seems like a pretty critical bug


bump webpack to 4.21

Had to make a change in the webpack config due to a breaking change.

the contentBase, contentBasePublicPath, serveIndex, staticOptions, watchContentBase, watchOptions were removed in favor of the static option

It might be a good idea to doc that in the webpack README since it has a good chance of tripping up folks.

Doc'd it!


[consensus][rfc] Forcing BlockInfo creation to come from a Block or Execut…

just toying with an idea as:

execution of blocks is not specified anywhere
it is hard to trace how different BlockInfo are created (genesis ones, NIL ones, from ExecutedBlocks for votes)

Over a month old, no activity closing out, feel free to re-open.


License mismatch

Hi,
this packet declares its license as BSD2 in the LICENSE file and in the Cabal file, but the files

src/Data/Matrix/MatrixMarket.hs
src/Data/Matrix/MatrixMarket/Internal.hs

say that they're licensed under GPL3, which doesn't mix with the BSD2 in the way it's used here. As it is now, this package must be distributed under GPL3.
Is this situation intentional?

@peti Good catch! It was a sloppy copypaste on my part. The library as a whole is BSD2, I'll fix this asap.

@peti Fixed and updated on Hackage! Thanks for reporting


gitlab-ce: upgrade from 15.1.2 to 15.2.2

Changelog:
https://gitlab.com/gitlab-org/gitlab-foss/blob/master/CHANGELOG.md#1522-2022-08-01

bors r+


FIX: fix after #1370

Fix indentation issue after #1370

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Language of the app

It would be cool to have a language selection somewhere (from the user or from the device locale) for international use.

French added, and language selection added to main app menu


Move flake8 configuration to its own ini file

This PR was used to test the new configuration with Hound CI.  It is working based on the tests above passing.  Merging pull request.


Export Map to HTML zipfile

Optionally export data into a folder so the Parquet data can stay in binary form. Note that the output directory then needs to be served, it can't be opened as a file.

As more context on this issue:
Right now, we always export all the code and all the data into a single massive HTML file, where the binary buffers are Base64-encoded and saved as big strings. This is a pretty good compromise because it's very simple for end users while also being generally foolproof. You can move the file to another machine, double click on it (opening it as a file:// url) and it'll just work.
I was talking to @batpad and he mentioned that having a directory of files might be convenient in some situations. This would allow for some separation between the original data and the code.


CMake 3.15 introduces a new policy, CMP0094, could lead to a build failure if there are multiple python version

bring this new policy up for attention, CMP0094 https://cmake.org/cmake/help/v3.15/policy/CMP0094.html. Starting with CMake 3.15, FindPython method will select the most recent version in all specified locations by default.
If the most recent one is not the one you choose to compile onnx-mlir and install onnx from third-party folder, the build process will fail after run the back-end test for python and throws an error as ModuleNotFoundError: No module named 'onnx' . Passing the selected python path via DPython3_ROOT_DIR still does not work.
For this case, I think setting Python3_FIND_STRATEGY as LOCATION can work with DPython3_ROOT_DIR correctly.
Here are some workarounds I found to resolve this issue:

add set(Python3_FIND_STRATEGY LOCATION) to CMakeLists.txt
add -Python3_FIND_STRATEGY LOCATION to cmake command
use cmake_policy() to enable this policy as NEW
add -DPython3_EXECUTABLE=path_to_python to cmake command

To reproduce this error:

install multiple versions of Python, 3.8 and 3.9
use python3.8 with DPython3_ROOT_DIR and then follow the instruction of building the onnx-mlir
build process will select python3.9 to run the backend test and failed

I confirm that having multiple python indeed created the error listed above. Unfortunately, I was not able to use the hints above to fix this.
However, I solved it by doing a (on my Mac) brew list |grep pyton to detect the many versions.
I then did a brew uninstall of the older python version, and then rebuild the onnx-mlir compiler from scratch, after having added the new python's path in PATH env var, and it worked.


could not send payment threshold announcement to peer

Summary
Is this normal behavior? could not send payment threshold announcement to peer. What are the reasons for this?
Steps to reproduce
bee version: https://github.com/ethersphere/bee/releases/download/v0.6.2/bee_0.6.2_amd64.rpm

curl -s http://localhost:1635/peers | jq '.peers | length'
103

This does not look like a bug but more like a connectivity issue. Could you say if this is still an issue?


[Bug] Springboot maven app is incorrectly recognized as a gradle app

Plugin Name and Version:

1.2.1

Nx Version (nx --version):

11.1.5

Angular CLI version (ng --version):

11.0.4

Operating System:

Windows 10 20H2

Project setup:

Springboot app generated with nxrocks 1.2.1, type: Maven

Expected Behaviour
When nx serve app / nx run app:run / nx buildJar app /  nx buildWar app / nx buildImage app / nx buildInfo app commands are run, a mvaen equivalent should be executed and the command should complete successfully.
Actual Behaviour
When nx serve app / nx run app:run / nx buildJar app /  nx buildWar app / nx buildImage app / nx buildInfo app commands are run, a gradle equivalent is run (for nx serve app the command is ./gradlew.cmd bootRun), which fails due to the project not having gradle configured (I presume).
If I navigate to Java project root directory and run mvnw spring-boot:run, the application starts successfully.
Steps to reproduce the behaviour

Create an empty NX workspace (haven't tested on other workspace setups) with npx create-nx-workspace@latest app
Add the nxrocks springboot dependency npm install --save-dev @nxrocks/nx-spring-boot
Generate a Java Maven Springboot project nx g @nxrocks/nx-spring-boot:app app.
Select these options: Maven, Jar, Java 11 and Java.
Execute nx serve app from the workspace directory

Alternate way to reproduce the behaviour using existing repositories
I have two repositories where I have this bug (and no repositories where it works).
Both contain a description of how they were set up in docs/setup-guide.md

Older project, generated with nxrocks 1.2.0. Java app is called java-api
New project, generated with nxrocks 1.2.1. Java app is called api

Behaviour steps will be explained using the second repo:

Clone repository with git clone https://github.com/treecreate/webstore.git
cd webstore
Run npm install
Run nx serve api

Extra notes:
I was able to reproduce the bug on my laptop running Windows 10 2004.

Hi @Kwandes
Thank you for reporting the issue. I was able to reproduce it on my windows 10 machine (which is a good sign 😄 ). I will now look into a fix. Stay tuned!
Cheers

Hi @Kwandes
Thank you for reporting the issue. I was able to reproduce it on my windows 10 machine (which is a good sign 😄 ). I will now look into a fix. Stay tuned!
Cheers

Hi @Kwandes,
Looking at the 2 repos you mentioned in your first comment, I noticed that the Maven Wrapper (./mvnw) located at the root of the generated spring boot app, is not executable as it should.... which is causing the issue. Indeed, with current implementation of the plugin, the project build system is determined by trying to execute the ./mvnw --version command.
I wasn't able to reproduce the "non executable" ./mvnw on a new project generated from a empty Nx workspace...
Anyway, in the upcoming version of the plugin, I have improved the way the build system is determined
so hopefully, this should not happen again.
Feel free to re-open, or to file another issue if it does.
Cheers

Hi @Kwandes,
Looking at the 2 repos you mentioned in your first comment, I noticed that the Maven Wrapper (./mvnw) located at the root of the generated spring boot app, is not executable as it should.... which is causing the issue. Indeed, with current implementation of the plugin, the project build system is determined by trying to execute the ./mvnw --version command.
I wasn't able to reproduce the "non executable" ./mvnw on a new project generated from a empty Nx workspace...
Anyway, in the upcoming version of the plugin, I have improved the way the build system is determined
so hopefully, this should not happen again.
Feel free to re-open, or to file another issue if it does.
Cheers


Make vdebug keymaps only available once vdebug is started

Perhaps a feature, but I feel that the default configuration is a little invasive.
Personally I already had some key maps on my F keys which are now global overwritten.
I would much rather have vdebug key maps being effective only when a connection has been made with the server.  Is this even possible ?

Closing due to inactivity - please reopen if needed.


The source code seems to be missing

I am going through he video through Safari Books Online . I have tried downloading the source code from Packt Publishing website but the zip is empty. Seems like this repo is empty as well. Am I missing something?

Some help on this would be great.  Video tutorial is not quite as useful without the files.

Had to go here, search for the book, then register in order to get an email with the link to download the file.  Downloading now.  http://www.packtpub.com/support

Got the files.  1.28 GB download and the files are a complete mess.


Fixed #25609 - related field nested lookup error

https://code.djangoproject.com/ticket/25609

With an assert len(lookups) > 0 this looks ready for commit.

For what it's worth, I noticed that in pre-1.9 versions, this raises "FieldError: Relation fields do not support nested lookups". Maybe FieldError is better than TypeError?

I'm happy to do that. If it is changed, I suggest Article.filter(author__editor='James') should also raise FieldError.

Since I'd like to backport this to 1.9 as the regression was introduced there, I opted to change this occurrence to FieldError and leave the other as-is (for backwards compatibility at this point in the release cycle). If you want to do any other changes, feel free to submit a PR for master and we'll limit those changes to there.
Merged in 32ef48aa562e6aaee9983f5d0f1c60f02fd555fb, thanks!

Thanks!


extend benchmarks

Please be explicit on 1. allocation, 2. constrains, 3. usage of SIMD
I would be curious, how fast other SIMD-accelerated parsers are in comparison. For example, there is https://github.com/geofflangdale/simdcsv

The simdcsv library you mentioned was the first library we looked at when we wanted to find one instead of write our own. However, it appears that their library does not handle "real-world" CSV parsing, as they state here:

Real-life parsing of CSV files has to deal with a huge range of optional variations on what a CSV might look like. My plan is to initially focus on standards-compliant CSV files and potentially add some variations later

Handling the edge cases, while maintaining performance, is perhaps the single most challenging part of designing this library, so a comparison against a parser that ignores the edge cases is of limited value

Re your question sub-points 1, 2 and 3, not sure what you are requesting but happy to consider/accept contributions (even partial) if you have specific suggestions as to changes in the repository contents that may help to address them

Probably the description should include "CPU-based", as GPU-parsing sounds like it can be faster: https://github.com/antonmks/nvParse

We're not going to rename the library because the usual assumption is that a C library uses CPU i.e. libz is not called "libz-cpu".
Furthermore, just because something sounds like it can be faster doesn't mean it is.
First, GPU cannot be assumed to always be available, and in many circumstances (such as when running as web assembly, or in a typical serverless computing environment), it most definitively is not.
Second, even when GPU is available, there is still significant overhead in loading the memory into the GPU and getting it back out
Third, it is much harder to handle the edge cases with GPU instructions, and we are not inclined to spend our time solving that problem, especially given the above limitations (in particular, the first).
If anyone can point to a GPU library that works for CSV parsing including edge cases, and can be compiled to run "count" and "select", then we'll happily consider adding it to the benchmark. Until then, we don't have the resources here to add benchmarks against incomplete alternative parsers.


Add compatibility index for modules

After my intent to move outdated modules to undeaD failed, here's the suggested way of documenting old modules.

Great, I think starting with documentation should be the official way of implementing all deprecations.

tl;dr: This generalizes the deprecation warnings (and makes them look nicer than for std.xml).
As suggested this is heavily inspired by the way NodeJS marks their modules, but why not learn from successful ideas?
The overview page:

In practice:
Deprecated
$(COMPATIBILITY_BOX_0)

Experimental
$(COMPATIBILITY_BOX_1)

Stable
$(COMPATIBILITY_BOX_2)

And all in one:

CC @MartinNowak @CyberShadow @andralex @JackStouffer

IMHO we don't need the stable markers or the compatibility index. The deprecated/experimental warnings look great though.

We must have a "Stability: Obsolete" which predates deprecation. It means the code works and does not issue deprecated warnings but a superior solution (EXISTING!!!) is preferred for new code.

We must have a "Stability: Obsolete" which predates deprecation. It means the code works and does not issue deprecated warnings but a superior solution (EXISTING!!!) is preferred for new code.

Sure that should be easy enough:

(also added it to the PR)

IMHO we don't need the stable markers

Well, just because I add the macros here, doesn't mean that we need to apply all of them for Phobos.
However, it could be helpful to ensure to people that the module they use is rock-solid... (in theory :laughing:)
I don't feel strongly about the stable markers, I want to mark old modules ;-)

or the compatibility index.

I guess some people want to know what e.g. "Obsolete" means precisely, but there's no point in always showing the long text. Is this page hurting us?

I guess some people want to know what e.g. "Obsolete" means precisely, but there's no point in always showing the long text. Is this page hurting us?

No, but it seems redundant. I don't think the boilerplate is an issue. Also, the box itself would be a good place to mention the recommended replacements.

However, it could be helpful to ensure to people that the module they use is rock-solid... (in theory 😆)

I'm thinking, modules which may seem well designed today may not appear so 10 years from now :)

One other thing: for each artifact we should be able to automatically get the version that introduced it and (for removed ones) the version that made it unavailable. Perhaps a topic for a different PR.

One other thing: for each artifact we should be able to automatically get the version that introduced it and (for removed ones) the version that made it unavailable. Perhaps a topic for a different PR.

That shouldn't be too difficult. What to do with the result, show it on dlang.org for all symbols somehow?

Yes, it should be easy as people browse some library artifact to get extra info about it including this version stuff.

On Wed, Jun 28, 2017 at 10:57:50AM -0700, Andrei Alexandrescu wrote:

One other thing: for each artifact we should be able to automatically get the version that introduced it and (for removed ones) the version that made it unavailable. Perhaps a topic for a different PR.

I think we should also use the History: section in ddoc to document changes so like "argument foo introduced in June 2017"... generating it automatically would be good for many things but going forward we could just add it in after merging PRs.

Also, the box itself would be a good place to mention the recommended replacements.

Good point. I also removed the "Stability X" everywhere and replaced them with their respective name as the numeric scale is confusing and we can easier extend / modify this scheme without numbering.
Do you know a Ddoc trick to display the separator only if there's a message?

I think we should also use the History: section in ddoc to document changes so like "argument foo introduced in June 2017"...

We probably want to write 2.075?

generating it automatically would be good for many things but going forward we could just add it in after merging PRs.

Yep, I think this "naive" approach will be a lot easier and can be done once on every release by simply going over the changelog. We just need to remind people to add their changes to the changelog (or respective Bugzilla issue), but hopefully the Dlang-Bot is now loud enough ;-)

So @CyberShadow are we all happy with DEPRECATED, OBSOLETE, EXPERIMENTAL and STABLE to be stability categories? Of course, we can always extend them, but I would like to continue with my goal and document the old & ugly modules in Phobos. Most likely, during this process, we might rework this category schema anyways ;-)

Arghhh, GitHub ate my comment again.
Generally speaking this change has a larger scope so it's more up to the BDFLs than me to set the direction, but since you asked for my feedback:

DEPRECATED, OBSOLETE, EXPERIMENTAL

These seem fine to me.
I don't think we need stable.

Some are so proven, and so relied upon, that they are unlikely to ever change at all.

Can we really say that about anything? :) We change / deprecate things even in relatively new modules.

This feature is subject to change, and is gated by a command line flag

Seems like there are some conflicting goals here - nothing in Phobos is gated behind a compiler flag. Is the intent to use these macros in the spec as well?
Still not sure about the compatibility index page - it contains rather little information, and said information could be directly presented in the notice itself..

but I would like to continue with my goal and document the old & ugly modules in Phobos

I suggest to only keep what you need right now to do the above task, i.e. drop the compatibility index and stable macro, and just leave the macros for the notices to be used in Phobos.
Notice texts could be:

Warning: This module is deprecated and will be removed on $1. Use $2 instead.

Warning: This module is obsolete and may be removed in the future. $0

Warning: This module is experimental and may be removed, changed, or moved in the future. $0

BTW, intuitively "obsolete" seems like a stronger term than "deprecated", without prior knowledge I would guess that a module would go stable -> deprecated -> obsolete. I can't think of a better term though.

In C++ "deprecated" (e.g. exception specifications) is stronger than "obsolete" (e.g.strstream).
Interestingly http://m-w.com does not list the computer engineering meaning of "deprecated". However, it does suggest that "deprecated" is stronger than "obsolete":
https://www.merriam-webster.com/dictionary/deprecated
https://www.merriam-webster.com/dictionary/obsolete
The thesaurus may provide insight into possible alternative terms:
https://www.merriam-webster.com/thesaurus/deprecated
https://www.merriam-webster.com/thesaurus/obsolete

The obsolescence text should be:
Warning: This module is obsolete and may be superseded in the future. $0

In fact the way I see it something is obsolete if and only if it already has a better alternative.

Hmm, maybe before we proceed, let's better have a look on how we would apply and use these messages on Phobos.
Here's my list of OBSOLETE and DEPRECATED stuff.

std.container: OBSOLETE (There are the faster, @nogc emsi-containers and work is in progress for a Phobos replacement)
std.json: DEPRECATED -> std.data.json
std.net.curl: OBSOLETE -> requests
std.outbuffer: DEPRECATED -> std.conv + std.array.appender + the entire concept of output ranges needs to be reworked
std.signals: DEPRECATED, e.g. phobosx:

Replacement for std.signals, with more features and less bugs.

or observe etc.

std.stdint: DEPRECATED -> core.stdc.stdint
std.socket: most likely we need to create a new module without classes if we want Sockets to be @nogc. Of course Vibe.d does a pretty job in regards of async connections, e.g. TCPConnection.
std.uri: OBSOLETE -> alphaPhobos, vibe.inet.url, http2.d
std.variant: OBSOLETE -> taggedalgebraic
std.xml: OBSOLETE -> experimental.xml

Other ugly modules:

std.base64 (combine with std.base32)
std.encoding is really messy and semantically should contain std.utf

I think we'd be hasty.

OBSOLETE: a better alternative exists in the standard library.
DEPRECATED: a better alternative exists in the standard library, and the deprecated things will be removed on a precise schedule

We do NOT mark stuff as obsolete because there are alternatives outside the standard library.

There are the faster, @nogc emsi-containers

Is that project still alive? I sent a PR last year and it's still open. Last commit was also last year.

I now realize how my previous comment might have been misunderstood - I assumed "within the standard library" is implied.

Is that project still alive? I sent a PR last year and it's still open. Last commit was also last year.

IIRC EMSI uses the library internally, so it's probably not "dead".

Hmm, I guess it's not really relevant here any more but I guess a library may still be used whereas its open source project might be dead, due to dwindling interest of reviewing outside contributions or conflicts of interest.

In fact the way I see it something is obsolete if and only if it already has a better alternative.

That's a strong requirement, hardly anyone want's to introduce a replacement for std.signal.

We do NOT mark stuff as obsolete because there are alternatives outside the standard library.

If there was a much better alternative and everyone in the community knew to use fastxml instead of std.xml, is it really a good idea not to mention that?

This discussion suggests that there is not much difference between obsolete and deprecated.
https://english.stackexchange.com/questions/87887/what-is-the-difference-between-obsolete-and-deprecate-in-computer-science
We want something as simple as For new code it is recommended to use XYZ instead., maybe we don't even need to find/invent the right adjective for that.
If we still want one I'd rather use outdated or superseded than obsolete.

I definitely agree with some flexibility.
If std.signal is rendered essentially useless by simple use of language features and idioms, yes let's mark it as obsolete/deprecate/yank.
Faster/better alternatives to standard artifacts exist in probably most languages, and for most artifacts. But it's uncommon to throw away the standard implementation on account of that - even for the most egregious cases such as C++ iostreams, which must count as the worst I/O library in the history of humankind.

Love Superseded by: $0. We could even make it a standard ddoc tag.

Alrighty - I rebased this PR to a general concept of a MESSAGE_BOX, s.t. defining a deprecation is as easy as:
COMPATIBILITY_BOX_DEPRECATED = $(MESSAGE_BOX red, $(B Deprecated) - $0)

I added a few predefined ones, but we could also remove all of them, and just add MESSAGE_BOX.
And with MESSAGE_BOX start adding warnings to Phobos and once we have agreed and realized which definitions are necessary, standardize and re-add them.

Merging, as it's now just a few macro definitions and CSS rules.


[BUG]intranet cannot work fine

Describe the bug
When used in an intranet environment, it does not work properly.  Maybe etcdmanager needs internet resource just like js,css,etc.
To Reproduce
any environment can't connect to internet, open etcdmanager.
Expected behavior
Screenshots

Desktop (please complete the following information):

OS: macOS
OS version: 10.15
ETCD manager version:1.1

Additional context

This fill be fixed in next release

Already fixed in develop branch, will be released soon.

@gtamas  thank you！


[BUG] - AIRPORTS_GEOMAP missing airports

Describe the bug
When drawing the new AIRPORT_TEXT_GEOMAP, there are text points for airports that don't have a symbol.
Take for example: 79FD, FA53, FL42 that don't have airport symbols in the AIRPORTS_GEOMAP.xml but KPCM, KLAL, and KBOW do.
At first, it appears that only fields with an ICAO get a symbol but 0L9 gets a symbol and has no ICAO code.

Fixed Version 0.7.2

Fixed Version 0.7.2


in the arm windows10,can't create virtual network adapter

I am using version 4.34, my operating system is macos (m1 chip), I use Parallels Desktop to create an arm windows10, I cannot create a virtual network adapter。
in the client_log,don't find error logs.
If you can get help, I am very grateful.

We currently don't provide drivers for ARM64, however I will work on it soon.

Do you have a driver for arm64 now ？

Unfortunately not, however I now have an ARM64 machine I can test on.

Hope to support MAC M1 soon

any updates on this one? I'd happily give an early version a crack, or even a use workaround

Do you have a driver for arm64 now ？

Do you have a driver for arm64 now ？

Is anything needed for supporting ARM based chips?

Is anything needed for supporting ARM based chips?

we need a developer with ARM hardware to test himself.

I have a newly bought M3 Pro, I could test it against an IPSec IKEv1 VPN. Where do I start?

I have a newly bought M3 Pro, I could test it against an IPSec IKEv1 VPN. Where do I start?

it would be nice if you test and confirm whether it works or not

I will have a look at it next week. Have to setup the project first.

So, these instructions here https://github.com/SoftEtherVPN/SoftEtherVPN/blob/master/src/BUILD_UNIX.md#build-from-source-code-and-install just work and doing an "./build/vpnclient start" produces no errors. Currently trying to connect to our VPN server.

So, these instructions here https://github.com/SoftEtherVPN/SoftEtherVPN/blob/master/src/BUILD_UNIX.md#build-from-source-code-and-install just work and doing an "./build/vpnclient start" produces no errors. Currently trying to connect to our VPN server.

is it working?

I'll have a look and see what I can get to work:
Win11 24H2, Snapdragon arm64 if you're interested

Yeah so I couldn't get it to build, Visual Studio is a pain. If someone could give me some pointers, I'll put some extra effort in 👍


How to set any zod schema as the attribute in z.object

i am trying to create a zod object schema for generic REST api request def.  this schema is generated by codegen.
const apiRequestSchema = z.object({
  apiConfig: apiConfigSchema, // another zod schema that specifies url, body etc.
  outputSchema: z.zodAny() // schema that will be used to parse the response. it can be any zod schema
})

type APIRequest = z.infer<typeof apiRequestSchema>

APIRequest typescript sets outputSchema as any zod schema that can be used to parse the response.
is there a zod method e.g. z.zodAny to specity zod schema as the value of outputSchema?

found it.
i used the z.instanceof(z.ZodType) and it works well.


[WIP] Possible to localized to help commands

When feature flag is specified, comments are switched to the respective language.
This can be used to switch help commands as well.
Translate from Japanese text to EN and CH.

[ ] Help command review

[ ] JA
[ ] EN
[ ] zh_CN
[ ] zh_TW

[ ] Mode help command review

[ ] JA
[ ] EN
[ ] zh_CN
[ ] zh_TW

Unwrap() is often used to parse arguments, causing panic with wrong arguments.
Changes proposed in this PR:

Possible to localize to help command
Add help_message.rs
Error handling of args parsing (Shouldn't this be included?)

@mtshiba

We need to write relevant development documents @GreasySlug

We need to write relevant development documents @GreasySlug

That's right.
I'm going to make how to localize help commands.

Translated Ja to Ch and En.
Especially, I cannot correct Chinese sentences, so I would appreciate your confirmation.

Is this PR completed? @GreasySlug

Drafts have been completed, @C-BJ


Fix typo of CodiMD

Hi @mattcone, I think it's "CodiMD" instead of "CodiME".

Sorry about that, @jackycute. My mistake. Thank you for opening this pull request!


Question about passive radar implementation

Hello, nice work.
I have two questions:

Can passive radar detect the distance of the target? If yes, how is this achieved?
Why do we need coherent SDRs in the same location? I can understand the concept of two coherent SDRs in different locations (due to TDoA estimation) but for the same location it is not obvious to me

Hmm for the second question, is this due to the need of reference path?

Hi,

Yes passive radar can detect range to the target based on time-difference-of-arrival or TDoA. If we Rx the reference signal at time T and the reflected signal at (T + T_r) we can derive the difference in range based on knowing:
a. the distance between the receiver and
b. the speed of light.
We can, with multiple measurements, fit an estimate to the position of the object and not just range.

Yes, we need a reference path to infer TDoA.  If the two Rx units at the Rx site are not coherent then there will be no way to infer TDoA between the signals.   Even a slight variance in phase will give huge errors in range.

I don't remember where I found the equations for the range and the position estimates but some googling this morning gave me some places to look:
https://www.mathworks.com/help/fusion/ug/track-using-bistatic-range-detections.html
https://dopplerfish.com/passive-radar/
Note that passive radar is bistatic radar.

Thank you.
Have you measured how accurate is the distance estimation? Also, I believe if you deploy 2 coherent RX pairs (in different location) you can improve the accuracy by using something like triangulation. Have you tried something like that? However, I believe that again the distributed RXs pair should be coherent too which as I know it is difficult task and even more challenging for RTL SDR

I have not measured the accuracy,  I think in the dopplerfish website Max Manning points out that the range estimates were good but the frequency shift was more accurate:

Comparing the experimental results to the predicted results from the plane trajectory, there is a very good match! Due to the nature of the FM signal that was used, the Doppler resolution is more precise than the range resolution.

I have not tried multistatic equations for this, but it probably would be more accurate.   If you derive the bistatic equations (hint: the answer is an ellipsoid) you could throw in more coherent Rx units and see where it goes.  It would be a system of nonlinear equations where you seek the intersection of multiple ellipsoids (one ellipsoid per Rx unit).  The Rx units would, as you said, need to be coherent with the Tx site, and hence would need two rtl-sdrs with the mod on the clocks.

Thank you. Just to make sure that we are in the same page, the first coherent RTL pair in position1 should be also coherent with the second coherent RTL pair in position2. Correct? Also, the transmitter should be reaching both RX positions.

I haven't done the derivation for multistatic problems but my first thought is

position1 coherent with Tx
position2 coherent with Tx

but I dont think 1&2 will be coherent since they do not Tx waveforms for TDoA calculations.  I think all they would communicate would be range estimates to the object.


providing executable for ARM

I'm currently working on a nvidia jetson tx1. Is there a chance that you provide the simulator compiled for arm architecture?

Hi @Grillen80,
Did you find any solution to your issue, please share so that other students can benefit?
Thank you


Replace real API requests with mocks

Tests can fail due to endpoint failure or slow response time

#96


Show a link after quick-adding an event

Firstly : the extension is amazing, keep up the good work!
About the feature: since there are known bugs with the quick-add feature of Google Calendar and because sometimes the user would add an event in the far future (the new event would not pop up in the extension UI), IMO it would be helpful to have a link pop up on the top of the UI to the event that was just created (or a notification that Calendar failed to create the event). It doesn't need to be anything fancy - just a link (that would not need to persist to the next UI opening), so that the user would be able to do a quick check on the new event.

@manastungare Can this issue be closed ?


cmake doesn't check for Judy.h

Describe the bug
cmake succeeds and the build then fails:
cmake should check all dependencies.
Environment:

OS: FreeBSD 14.0
Version: 4.1.1

IMO, I'm not sure this is a bug but rather a potential enhancement. It'd be nice if CMake would give the user a nice message about how Judy wasn't found and how to install. But INSTALL.md (which is referenced in the README.md) does mention exactly what you need to install to compile this from source.
I'll take a look at getting this into CMake though since it would improve the user experience.

cmake can easily check for the header with CHECK_INCLUDE_FILE.


Namespace view shows 'Active' state twice

See above- there are two cards for 'Active' - there should only be one.
Take a look in detail/namespace.vue, in namespaceCounts - I think the issue is a mismatch between 'activeandsuccess` states.

This issue is resolved by PR rancher/dashboard#5145

Reproduced the issue on 2.6.3

On 2.6-head commit id: 8c785a1

Resource tab is added, and columns - error, warning, transitioning, unknown, Active are seen
Active state is seen only one time


ErrorAction support in MicrosoftTeams

Errors stop progress when using MicrosoftTeams commands. -ErrorAction parameter is not an optional parameter.

Hi @cloudedturtle   thanks for your feedback,  I see that this wouldn't cause a change in documentation.  @yogkumgit can you kindly help here?

@cloudedturtle  Thank you very much for posting this issue. Considering the nature of the issue, it is advised that please open a service ticket in your tenant and follow with them for the resolution. If you wish to know how to open the service ticket, please follow this link:            https://docs.microsoft.com/office365/admin/contact-support-for-business-products
We will be very happy if you can share the outcome or resolution with us. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Datafusion invalid projection

Closes: #569

Codecov Report

:exclamation: No coverage uploaded for pull request base (datafusion-sql-planner@16282ed). Click here to learn what that means.
The diff coverage is n/a.

@@                    Coverage Diff                    @@
##             datafusion-sql-planner     #571   +/-   ##
=========================================================
  Coverage                          ?   57.82%
=========================================================
  Files                             ?       72
  Lines                             ?     3571
  Branches                          ?      724
=========================================================
  Hits                              ?     2065
  Misses                            ?     1372
  Partials                          ?      134

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

#558 should be merged in first. This PR was based off 558

#558 is merged now @charlesbluca so feel free to review this at your leisure


text-rendering: optimizeLegibility is buggy on Windows and Linux

@jonathantneal text-rendering: optimizeLegibility is buggy on Windows and Linux:
https://github.com/Microsoft/vscode/issues/192#issuecomment-171270723

The implementation has known bugs on Windows and Linux, which can break font substitition, small-caps, letter-spacing or cause text to overlap.

Maybe for now it'd be better to not include it by default?

Agreed, and this is related to #33, so the property has been removed as part of v3.1.1. Thanks.

Cheers.


Revert "Enable tf.log() for SparseTensor (#2763)"

This reverts commit 6e8cc50b80b00bbcb0095ec985e22db6bdd9b694.

Thanks Vijay!


#6 enable aws sso login support

Verified locally that plugin can use the token from aws sso login command

@madisparn Thanks for this! We'll take a look early next week and hopefully get it merged in ASAP.


Fix "use before define" issues so unspecified config keys are skipped; fix regexes; add missing globals; always ignore anteater_files

Successfully tested on a local repo with minimal config files:

ignore_list.yaml

project_exceptions:
  nullvalue

file_audits:
  file_contents:
    - "somevalue"

file_list.yaml

file_audits:
  file_names:
    - \.asc
  file_contents:
    password:
        regex: password
        desc: "Hardcoding passwords is baad!"

Hey @lukehinds what are the next steps to getting this released?

Hey @lukehinds what are the next steps to getting this released?

I will cut a release now. It's interesting that you're using anteater, please you're finding it useful. May I ask how you leverage the tool, perhaps on your CI (it's ok to not say if its internal work you need to keep private).

@dskrvk https://github.com/anteater/anteater/releases/tag/0.3.0

My goal is to use it for my team's Terraform project, initially in CI, and eventually in a pre-commit hook. A locally-patched version was already able to identify a few issues, so that's great. Thanks for creating the tool!
Sorry to be a bother, but v0.3.0 doesn't appear to be on pypi yet - is that a separate step?

@dskrvk ah, yep. will get that up this weekend!

Hi @lukehinds any chance you could get a new version released?

Hi @lukehinds any chance you could get a new version released?

hey @dskrvk , sorry about that will do, I am hitting some issues with pypi not liking the readme formatting, will have a another try.

Let me know if I can help in any way.
On Wed, Jun 23, 2021 at 11:23 PM Luke Hinds @.***>
wrote:

Hi @lukehinds https://github.com/lukehinds any chance you could get a
new version released?
hey @dskrvk https://github.com/dskrvk , sorry about that will do, I am
hitting some issues with pypi not liking the readme formatting, will have a
another try.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/anteater/anteater/pull/61#issuecomment-867344553, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AARJT2E3ILBAYV5JGIJVS5DTUK6MJANCNFSM447GC4WA
.

@dskrvk , really sorry this has taken so long. You would not believe the issues I hit, I had 2fa on pypi and my freeOTP was on an old phone given to another family member.
all sorted now: https://pypi.org/project/anteater/
p.s. happy to add you as a collaborator on the project?

Sure, I’ll try to help with the project. Glad you sorted out the OTP issues.
On Thu, Jul 1, 2021 at 10:37 PM Luke Hinds @.***> wrote:

@dskrvk https://github.com/dskrvk , really sorry this has taken so
long. You would not believe the issues I hit, I had 2fa on pypi and my
freeOTP was on an old phone given to another family member.
all sorted now: https://pypi.org/project/anteater/
p.s. happy to add you as a collaborator on the project?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/anteater/anteater/pull/61#issuecomment-872707042, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AARJT2HZTU5YF2FGZOHRFIDTVU7BNANCNFSM447GC4WA
.


Please update Bouncy Castle

Please update Bouncy Castle:

https://www.bouncycastle.org/
https://www.bouncycastle.org/releasenotes.html
http://www.bouncycastle.org/latest_releases.html
https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=bouncy castle
https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=bouncycastle
https://www.cvedetails.com/vulnerability-list/vendor_id-7637/Bouncycastle.html

I think this is a duplicate of #74

closing as duplicate of #74


WIP: Fix gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed

This MR will fix a critical warning that spams the stderr:
(gst-launch-1.0:4621): GStreamer-CRITICAL **: 15:51:27.489: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed
More information can be found there:
https://forums.developer.nvidia.com/t/gstreamer-udp-decoding-pipeline-in-jetson-tx2/128755/15
This basicaly backport two MR:
gstreamer: gst/bufferpool: only resize in reset when maxsize is larger
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/570
gst-plugins-good: v4l2: Various minor fixes
https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/-/merge_requests/649/commits
It compile and remove the warning on branch dunfell-l4t-r32.4.3 using gstreamer 1.16.3
I have marked it as WIP because it needs more testing. For now I tested it with:
gst-launch-1.0 videotestsrc ! nvvidconv ! nvv4l2h265enc ! fakesink

I applied both of these patches in my test environment and can confirm they eliminate the CRITICALs.
However, we can't really be patching gstreamer1.0 in a BSP layer.  If it's needed, could that patch go up to OE-Core?

The gstreamer1.0 patch is not very critical and it only warn the user when something is wrong with GstBufferPool.
I will try to submit it to OE-Core [dunfell] but because it not a critical bug fix I'm not sure if it will be accepted.
In the next days I will test this MR more deeply to check if it don't introduce any kind of regression.

I have submitted the gstreamer1.0 patch to OE-core
https://lists.openembedded.org/g/openembedded-core/topic/patch_v2_dunfell/78093156?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,78093156
This can be closed as the other patch have been back ported from #484


docs(@angular/cli): update add long description to analytics command

With this change we add a long description to analytics command with the information that is currently contain in https://angular.io/analytics which will be deleted at a later stage.

The motivation behind dropping angular.io/analytics. Is that at the moment we have 3 pages describing analytics. The majority of which have duplicate content. With this change we move all content to the  analytics command page.
This page was also not linked from the AIO guide which made it hard to discover as the only link was in the footer.


Remove the option to dynamically pass seed to rng generator

dibatable lose of functionality but simplifies the code so I think it worth it.
also, there's still the ability to pass the seed as env var in order to debug when needed.
commit-id:a694971d

Stack:

#639 ⬅
#638
#637
#636
#635
#634

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

This change is

crates/test_utils/src/lib.rs line 241 at r18 (raw file):
Previously, nagmo-starkware wrote…
I see what you mean. but read the two comments lines as if it is one comment.. same randomness was applied before. the difference is that we "fix" the stateDiff by adding a declared class with a different hash.
also, one more thing to note. Dan and I discussed adding a PR for documentation improvements of the public test utils functions once we finish with all the refactoring PRs.. so either way we'll look at it again soon.

Resolving
TBD: manual impl of get_test_instance for StateDiff for a valid instance instead of this function


Corrected URL to WSOA to avoid 404

There was a missing directory level on the WSOA link in the existing docs.

/m


add corresponding modification to readme_en.md with respect to PR 43

ref https://github.com/mini-sora/minisora/pull/43

See PR #54 and #55


DOC: Update readme for rank mismatch

As noted. The actual error is:
grasp/src/lib/lib9290/iniest2.f90:82:23:

   79 |          CALL DCOPY (NS, VEC(NS*(J-1)+1), 1, BASIS(NCF*(J-1)+1), 1)
      |                         2
......
   82 |       CALL DCOPY (NIV, EIGVAL, 1, BASIS(NIV*NCF+1), 1)
      |                       1
Error: Rank mismatch between actual argument at (1) and actual argument at (2) (scalar and rank-1)

I would like to vote this up.


Abstract the secret key names for Pinniped-generated certificates held in K8s secrets

Abstract the secret key names for Pinniped-generated certificates held in K8s secrets.
This does change production code, but should essentially be a refactor (no change in observable behavior). It's a refactor in preparation for any changes made for #1238 .

Marking this as draft until we have a path forward for #2027


(PUP-2838) Fix invalid .dot files due to missing escapes of quoted strings in resource names

When using resource names with quotes, the --graph functionality of puppet produce a broken dot file:
λ dot /var/puppet/state/graphs/relationships.dot
Error: /var/puppet/state/graphs/relationships.dot: syntax error in line 5765 near '"'

The puppetlabs/puppetlabs-postgresql generates a lot of such resources.
This Pull-Request workaround the problem by escaping quotes when generating the dot graph. A better fix strategy is described in the existing code, unfortunately I can't afford it 😄:
https://github.com/puppetlabs/puppet/blob/f01045901935c3cf62f2f4d0b83be7ea78972ac3/lib/puppet/external/dot.rb#L207

Can one of the admins verify this patch?

CLA signed by all contributors.

Thanks for also taking the time to clean up the warnings unrelated to the dot issue.


chore: add stale bot

@jawnsy brought this up the other day. Then GitHub mentioned we should it so I thought why not 🤷♂
I will take responsibility if it goes horribly wrong 😂
The way this works is we have a stale.yml under .github which is the configuration and then @jawnsy enabled Stale bot it at the cdr org level.
Fixes N/A

I guess you forgot to set exemptLabels and exemptMilestones. An On Deck bug is closed:
#1105

@Lemmingh thanks for pointing that out!
I guess we should add that. If no one responds though, it's still probably stale and makes sense to close, but I'll open an issue to do this.

Does that mean #33 will be considered stale at some point?

@bpmct yes if there is no activity for 180 days!


Loading Time on Web

Describe the bug
in the hosting simple example page with just the wave plugin as background take 1 minute and 3 seconds loading.
To Reproduce
just host a Flutter web project with this build
@override
 Widget build(BuildContext context) {
   return Scaffold(
     body: Center(
       child: WaveWidget(
         config: CustomConfig(
           gradients: [
             [Colors.red, Color(0xEEF44336)],
             [Colors.red[800], Color(0x77E57373)],
             [Colors.orange, Color(0x66FF9800)],
             [Colors.yellow, Color(0x55FFEB3B)]
           ],
           durations: [35000, 19440, 10800, 6000],
           heightPercentages: [0.20, 0.23, 0.25, 0.30],
           blur: MaskFilter.blur(BlurStyle.solid, 0.0),
           gradientBegin: Alignment.bottomLeft,
           gradientEnd: Alignment.topRight,
         ),
         backgroundColor: Colors.transparent,
         size: Size(double.infinity, double.infinity),
         waveAmplitude: 0,
       ),
     ),
   );
 }

Expected behavior
A nice loading time
Smartphone (please complete the following information):
WEB

Loading time depends on Flutter's optimization of the web page, which should be much better now. 😂


Unable to load BinExport as IDA-Pro plugins

Hello,
I downloaded the binaries in the release folder (zynamics_binexport_9.plx + zynamics_binexport_9.plx64) and put them into the plugins folder of IDA-Pro (version 6.95).
However, I am unable to load binexport as a plugin of IDA-Pro. Actually I just cannot find it in the plugins item:

Could anyone shed some lights here? Am I missed anything? Thank you!

Sorry, we do not support the text version of IDA Pro any longer. In fact, I personally can't even test this anymore, as my version of IDA (6.95 on Linux) does not even load with the text UI any longer (64-bit host).
That said, set IDALOG=/path/to/some/file and start idal/idal64 again and paste the contents of the log file afterwards.


refactor: use whiskers

Adds Whiskers, Catppuccin's in-house templating tool, to build the themes. Instead of the Python build script, edit the helix.tera file and then run just build to build the output themes. You will need Whiskers (linked above) and optionally Just installed.

thanks!


\r in cmd break cursor position

Expected behavior
if you paste text with \r characters it should work the same as with it.
Actual behavior
Cursor position is broken
Steps to reproduce
create file with CRLF ending on windows and enter some text with newlines and copy past it to terminal.
the cursor is off my the number of newlines.
Browser and OS
Windows

Possible solution use tracking_replace to remove CR from string.

Actually \r in command line don't give problems it give width: 0ch and browser threat it as space.


Add Mathway

Backstory
I just visited the site, went to settings, then account, and there was an option to delete it.
Let me know if there's anything wrong with this submission, as I probably can help with more.
Data

name: mathway
url: https://www.mathway.com/privacy
difficulty: easy
notes: Even though they state in their privacy policy that account deletion should be handled by contacting them, one can easily delete it by going into settings -> account.
domains: https://www.mathway.com/Algebra

The sites, urls and additional notes are stored in _data/sites.json.
Try editing it yourself. There's an edit button at the top (what actually forks (makes a copy) and edits your copy).
Other than following alphabetical order, a copy-pasta of an another entry should work.
After committing ('saving'), make a PR with a comment 'Closes #598'.
A few remarks:

URL should point to as close to the deletion page as possible (Something like https://www.mathway.com/settings/account maybe?).
Domains, not URLS, aka without the protocol (https://), skip the www subdomain and Algebra path. Giving you mathway.com.

If you get stuck, ask help here for any dumb reason.

I found out that https://www.mathway.com/settings is the link to the deletion page. Filed a PR.

The comment looked so close to a PR, hoped we'd get somebody's hands making a comit.

The comment looked so close to a PR

That's the goal of the template!

hoped we'd get somebody's hands making a commit.

I don't mind making the PRs every now and then. Every help counts, but some people aren't really accustomed to the whole git stuff, so it's alright

some people aren't really accustomed to the whole git stuff

Myself included! I'm new around. Now that I know how it works, I hope to contribute more in the future.


CMD's start command and Start-Process pwsh opens all new tabs in new second instance of WT, despite settings

Windows Terminal version
1.20.11781.0
Windows build number
10.0.19044.5011
Other Software
No response
Steps to reproduce
Edit: This can also be done from Powershell using start-process pwsh (and likely start powershell)

Open Windows Terminal with no other instances already running.
In that same window, open Command Prompt profile (unless it is your default launch profile)
Execute start command.
Execute start command from the same window as step 3.
Execute start command on the new spawned window from steps 3 or 4.

Startup settings:

Expected Behavior

With step 3, start should open a new tab in the same window we just opened.
With step 4, start should open a new tab in the same window we just opened, again.
With step 5, if executing start from a new window, it should open a new tab in that same window.
If step 3 and 4 go as expected, step 5 shouldn't even exist.

Actual Behavior

With step 3, start opens a new tab in a new window. (unexpected)
With step 4, start opens a new tab in the same new window opened in step 2. (unexpected)
With step 5, start in the same new window as step 3 opens a new tab in the same new window opened in step 3 (this one works as expected).

This is definitely highly irregular.
Can I ask a couple follow ups?

When you're launching the Terminal "Open Windows Terminal with no other instances already running"
Are you starting the Terminal from the Start Menu / taskbar, or by running wt.exe?
Is there an elevated (admin) instance running by any chance?
Does this repro with Terminal 1.22 Preview (you can find this on our releases page)
By any chance, are you running a portable / unpackaged Terminal in step 1?

I seemingly can't repro this locally.

I am running it from the Start bar via Searching, and from my taskbar (it's pinned)
No. I launch it when there are no other Windows Terminal windows opened.
I'll give that a try and update this then. Currently on 1.20.11781.0
I installed Windows Terminal as Microsoft.WindowsTerminal from winget, so whatever the default app/environment that provides.

Here's the terminal-trace.etl: https://user.fm/files/v2-8e77f46b31d98ec7a911ad51c7a49329/terminal-trace.zip

I have to add, this does not happen if I spawn my first WT window by running pwsh.exe, powershell.exe or cmd.exe, only if I launch WT itself.

So, so far the only weird thing I've found is that during your first "open a new tab in the existing window" (with start), we for some reason disconnect the window from its desktop in our internal accounting...
I can't explain that.
Still looking!


Unknown syslog line format for multiline logs

When running pgbadger against the syslog file I have received, I only see errors on the multi-line query lines as it seems to not be able to parse it properly, my assumption is this is because the log_line_prefix isn't present on those lines?
There are a number of connections which are received/disconnected too, but these do not seem to display errors when using a verbose output. Although they are not present in the output report.
An example snippet from the log file is
Nov 24 16:38:58 my-db-8 postgresql-11: [901-1] user=fusion,db=intelligence,app=[unknown],client=[local] LOG:  duration: 19623.550 ms  execute pdo_stmt_00006117: select <QUERY>
Nov 24 16:38:58 my-db-8 postgresql-11: [901-2] user=fusion,db=intelligence,app=[unknown],client=[local] DETAIL:  parameters: $1 = <params>
Nov 24 16:38:58 my-db-8 postgresql-11: [8-1] user=,db=,app=,client= LOG:  temporary file: path "base/pgsql_tmp/pgsql_tmp1489068.0", size 42500096
Nov 24 16:38:58 my-db-8 postgresql-11: [8-2] user=,db=,app=,client= STATEMENT:  select
Nov 24 16:38:58 my-db-8 postgresql-11: [8-3] 	               <Query-line-1>,
Nov 24 16:38:58 my-db-8 postgresql-11: [8-4] 	                <Query-line-2>,
Nov 24 16:38:58 my-db-8 postgresql-11: [8-5] 	               <Query-line-3>,
Nov 24 16:38:58 my-db-8 postgresql-11: [8-6] 	               <Query-line-4>
Nov 24 16:38:58 my-db-8 postgresql-11: [8-7] 	             <Query-line-5>

The returned verbose output would then be
DEBUG: Unknown syslog line format: Nov 24 16:38:58 my-db-8 postgresql-11: [8-3] <Query-line-1>,
...

The log_line_prefix on the database is set to user=%u,db=%d,app=%a,client=%h  with log_destination as syslog.
The command I am running has moved between using the prefix and not, whilst also trying different variations, although the issues still persist.
pgbadger --prefix "user=%u,db=%d,app=%a,client=%h " -v -f syslog <log_file>
and have attempted others like
pgbadger --prefix "[%p-%l] user=%u,db=%d,app=%a,client=%h " -v -f syslog <log_file>
Is this an issue which needs to be fixed or am I missing something with my prefix indication?

What operating system or cloud system produce these logs? Actually this is not a common syslog format. You have the following prefix:
Nov 24 16:38:58 my-db-8 postgresql-11: [901-1] user=fusion,db=intelligence,app=[unknown],client=[local] LOG: ...

where the expecting format would:
Nov 24 16:38:58 my-db-8 postgresql-11[32456]: [901-1] user=fusion,db=intelligence,app=[unknown],client=[local] LOG: ...

outside the format the trace seems to not include the pid ([32456] in my example) which prevent pgbadger to build statistics.

The logs are generated from Digital Ocean, so their managed DB service.
Do you think there is anyway to transform the logs into a usable state? Or is it a dead end to be able to analyse these logs they've sent, as they're not in the appropriate format to do so in the first place?

If you can change the log_line_prefix value set it like that: 'user=%u,db=%d,app=%a,client=%h,pid=%p ' I will train the badger to support more exotic format. Please post some log lines with this change so that I will have a working sample.

Since the database is managed by Digital Ocean, I don't have access to alter the log_line_prefix setting itself unfortunately. I believe without that, it could be a dead end?

Unfortunately but you should report this discussion to Digital Ocean, being a cloud solution provider that can not support pgBadger is not a good point. I think they can do something.

I shall definitely do that, much appreciated for taking a look at my issue Darold, thank you.


CVEs & CIS issues in Helm Chart 1.4.3

csi-secrets-store-provider-azure Chart version 1.4.3 has CVEs & CIS Docker Benchmark issues:
mcr.microsoft.com/oss/kubernetes-csi/secrets-store/driver:v1.3.3

VULNERABILITY TITLE
SEVERITY
CVE
PATCH AVAILABLE

Debian Security Update for ncurses (CVE-2022-29458)
CRITICAL
CVE-2022-29458
True

Debian Security Update for Open Secure Sockets Layer (OpenSSL) (DSA 5417-1)
CRITICAL
CVE-2023-0465, CVE-2023-0464, CVE-2023-0466, CVE-2023-2650
True

Debian Security Update for systemd (CVE-2022-4415)
SERIOUS
CVE-2022-4415
True

Debian Security Update for systemd (CVE-2022-3821)
SERIOUS
CVE-2022-3821
True

``
mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.10.0

SEVERITY
STATEMENT
REMEDIATION

SERIOUS
Status of the ADD instructions in Dockerfile
Use COPY rather than ADD instructions in Dockerfiles.

MEDIUM
Status of the HEALTHCHECK setting for the Docker Images
Follow Docker documentation and rebuild the Docker Images with HEALTHCHECK instruction.

@dkirrane You should be able to use driver image v1.3.4 using the helm chart values --set secrets-store-csi-driver.linux.image.tag=v1.3.4.
For livenessprobe image, you'll need to open an issue here. Once a new release is available, we will have that published in MCR.


Instance of PageScrollService already exists when using TestingModule

@NgModule({     imports: [Ng2PageScrollModule.forRoot()] }) export class AppModule
We need Ng2PageScroll directives to achieve the following:
ref1 ref2
So we import it into the module that wants to to declare a component that uses Ng2PageScroll.
@NgModule({     imports: [Ng2PageScrollModule] }) export class ModuleUsesNg2PageScroll
All this works fine, but the moment we run unittests the following warning appears:
An instance of PageScrollService already exists, usually including one provider should be enough, so double check.
It appears the moment, the first beforeEach() finishes and the second beforeEach() starts:
 beforeEach(done => { TestBed.configureTestingModule({             imports: [ModuleUsesNg2PageScroll, ModuleUsesNg2PageScroll.forRoot()]         }).compileComponents().then(() => {             fixtureComponent = TestBed.createComponent(ComponentWithScrolling); done();         });     });
Some logs:
LOG: 'Before Each 0'
LOG: 'PageScrollService.instanceCounter'
LOG: 1
LOG: 'Before Each 1'
WARN: 'An instance of PageScrollService already exists, usually including one provider should be enough, so double check.'
LOG: 'PageScrollService.instanceCounter'
LOG: 2
LOG: 'Before Each 2'
WARN: 'An instance of PageScrollService already exists, usually including one provider should be enough, so double check.'
LOG: 'PageScrollService.instanceCounter'
LOG: 3
The moment I remove Ng2PageScrollModule from the imports of ModuleUsesNg2PageScroll all works fine for testing, but of course the application can not use the pageScroll directive anymore and does not scroll correctly. I'm not sure if this behaviour is intented and would be happy about further informations.

The warning is displayed if a static instance counter of the PageScrollService detects that multiple instances are constructed (see https://github.com/Nolanus/ng2-page-scroll/blob/1101e043a476b7fca13de4f02c54131d2600fd42/src/ng2-page-scroll.service.ts#L201). Scroll animations started by two different instances of the PageScrollService are not aware of each other. This prohibits that a later started scroll animation first stops the previously started one before starting its own animation.
The warning is in place to point out this possibly expensive situation producing unintended behavior.  I assume in your testing situation the code is loaded once and multiple angular2 applications are created, each one of course constructing its own PageScrollService instance. Thus it should be no problem.


Sameersbn/Openfire

Hi,
I'm new to docker implementations.
However, I've been using Sameer's implementation on my Synology Container.  I see that your's is much more updated.  Is there a way to replace Sameer's docker image with all it's settings to yours?
Sorry if this is so basic.  But, as I mentioned, I'm very new to images.
Thanks,
Gus

I don't have any experience with Synology devices. What I can say is that in order to do this, you need to have a Docker volume mapped to /var/lib/openfire in the container. You may use the same volume with this image that you did with sameersbn/openfire.
One place you could run into trouble is the database. The embedded HSQL database is not intended for production use, so I've always used Openfire with an external database. If you chose the embedded database during initial setup and it doesn't work properly, I'm afraid I am not going to be of any help.


Support SAML2 scoping in authn requests

Scoping allows a pac4j SAML2 service provider to specify a list of identity providers in an authnRequest to an identity provider. This is an indication to the identity provider that the service will only deal with the identity providers specified.
Authn requests may look like this:
<?xml version="1.0" encoding="UTF-8"?>
<saml2p:AuthnRequest xmlns:saml2p="urn:oasis:names:tc:SAML:2.0:protocol"
  AssertionConsumerServiceIndex="1" ForceAuthn="false"
  ID="_ebf5682cbf7c48cf908c4d9127057b09920a3b2" IsPassive="false" IssueInstant="2021-07-01T11:31:27.426Z"
   ProviderName="pac4j-saml" Version="2.0">
<saml2:Issuer xmlns:saml2="urn:oasis:names:tc:SAML:2.0:assertion"
   Format="urn:oasis:names:tc:SAML:2.0:nameid-format:entity">entity-id</saml2:Issuer>
<saml2p:Scoping>
<saml2p:IDPList>
   <saml2p:IDPEntry Name="My Identity Provider" ProviderID="idp-entity-id"/></saml2p:IDPList>
</saml2p:Scoping>
</saml2p:AuthnRequest>

PS Support for this change will be added to CAS once pac4j is released.

I will be very soon on holidays, bu I'll cut a v5.1.2 release before that...


Error: [Syntax Checker] The current build fails due to an incompatible syntax, which can be fixed in the following ways:

这些版本升级到1.0试试。
"@rsbuild/core": "^0.4.6",
"@rsbuild/plugin-assets-retry": "^0.4.6",
"@rsbuild/plugin-babel": "^0.4.6",
"@rsbuild/plugin-check-syntax": "^0.4.6",
"@rsbuild/plugin-eslint": "^0.4.8",
"@rsbuild/plugin-image-compress": "^0.4.6",
"@rsbuild/plugin-rem": "^0.4.6",
"@rsbuild/plugin-type-check": "^0.4.6",
"@rsbuild/plugin-vue": "^0.4.6",
"@rsbuild/plugin-vue-jsx": "^0.4.6",


Math.trunc

Are you requesting a feature or reporting a bug?
bug
What is the current behavior?
Math.trunc return ReferenceError: _trunc2 is not defined
What is the expected behavior?
Math.trunc return a value
How would you reproduce the current behavior (if this is a bug)?
see script under
Provide the test code and the tested page URL (if applicable)
Tested page URL:
Test code
import { Selector } from 'testcafe'
fixture('Math test')
test('Math.ceil', async (t) => {
  const result = await t.eval(() => Math.ceil(13.37)) // <=== OK
  await t.expect(result).eql(14)
})
test('Math.trunc', async (t) => {
  const result = await t.eval(() => Math.trunc(13.37)) // <== BAD
  await t.expect(result).eql(13)
})

Specify your

operating system: Win7.0.0
testcafe version: 0.18.6
node.js version: 6 and 8

Hi @xcb6,
Thanks for the issue. We've faced with such problems before. It happens because we compile the test code with Babel. Server-side and client-side (code inside ClientFunction and t.eval) are compiled in the same scope thought actually they are executed in different environments. I described this in more details in my comment.
You can use one of the following workarounds:

move the Math.trunc execution to the server side if it's possible;
add the following line into your test: const Math = global.Math; (it's rather a hack but should work).

We already have an issue for such cases (see #1596). I close this one in favor of it and add the info about your case there.

Thank


Issue Sending Data from Cloned Nodes

I am having trouble posting data from nodes (Intel Galileos) which originally came from a fully functioning node (Intel Galileo). While everything seems fine, for some reason the observations are not appearing on the backend. I have posted my issue to the Intel community forums but have not received any useful answers:
https://communities.intel.com/message/336807
Im not sure whats up, if it has to do with the fact that the nodes are cloned or what...

Closing issue as it's not problem with agent itself but with mqtt broker. Temporary workaround was provided in discusion


Validate the NI number correctly

The validations for the NI number fields aren't triggering correctly in
the UI.
The 2 issues are that the error message for the validation is the Rails
default rather than the GOVUK style, which makes identifying the issue
hard. The GOVUK component doesn't render the field name in the errors,
so it relies on the error message including it.
Also, the ITT provider enrolled validation is firing at the wrong time.
This needs to be extracted to its own form object (which will happen in
another PR).
Checklist

[x] Attach to Trello card
[x] Rebased master
[x] Cleaned commit history
[x] Tested by running locally

When I click the error link locally in Chrome, I get the input highlighted.
eg.

Do you get something different?

@felixclack ahhh, I figured out what the issue is, it doesn't work without JavaScript! I never noticed that this behaviour requires JS in the design system. Nevermind my comment then.


Cant Flash - cant find ttyACM0?

Everything seems to go well, up to erasing the flash - It cant find the port, but dmesg shows the Espressif and that it is on /dev/ttyACM0.  Looking at /dev - I can see ttyACM0 is there.   If I disconnect the USB cable, ttyACM0 does go away...
Using venv for esptool
esptool.py v4.5.1
Serial port /dev/ttyACM0
A fatal error occurred: Could not open /dev/ttyACM0, the port doesn't exist
dmesg when plugged in:
[ 3364.126378] usb 2-2.1: new full-speed USB device number 8 using uhci_hcd
[ 3364.434428] usb 2-2.1: New USB device found, idVendor=303a, idProduct=1001, bcdDevice= 1.01
[ 3364.434435] usb 2-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3364.434437] usb 2-2.1: Product: USB JTAG/serial debug unit
[ 3364.434439] usb 2-2.1: Manufacturer: Espressif
[ 3364.434440] usb 2-2.1: SerialNumber: 7C:DF:A1:E8:22:F8
[ 3364.438405] cdc_acm 2-2.1:1.0: ttyACM0: USB ACM device
[ 3408.337353] usb 2-2.2: USB disconnect, device number 7
[ 3412.010379] usb 2-2.1: USB disconnect, device number 8
[ 3412.923174] usb 2-2.1: new full-speed USB device number 9 using uhci_hcd
Only potential issue - this is a VM, but Im passing the USB through, and I never had issues in the past doing this on any flashing (ESP / etc...)
Any ideas?

Which distro is this?
Can you run:
ls -l /dev/ttyACM0
id

Damn - Was just going to send it and noticed I was running it as my standard user - ran utils.sh in a root shell and its working.
Sorry for the rookie mistake!    and thanks for the quick reply.

Different issue on the flash now:
Using venv for esptool
esptool esp32s3 -p /dev/ttyACM0 -b 2000000 --before default_reset --after hard_reset write_flash --flash_mode dio --flash_freq 80m --flash_size 16MB 0x0 bootloader/bootloader.bin 0x10000 willow.bin 0x8000 partition_table/partition-table.bin 0x210000 srmodels/srmodels.bin 0x710000 audio.bin
esptool.py v4.5.1
Serial port /dev/ttyACM0
Connecting...
Chip is ESP32-S3 (revision v0.1)
Features: WiFi, BLE
Crystal is 40MHz
MAC: 7c:df:a1:e8:22:f8
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 2000000
Changed.
Configuring flash size...
Flash will be erased from 0x00000000 to 0x00005fff...
Flash will be erased from 0x00010000 to 0x00191fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Flash will be erased from 0x00210000 to 0x005f3fff...
Flash will be erased from 0x00710000 to 0x0078ffff...
Compressed 22256 bytes to 13957...
Wrote 22256 bytes (13957 compressed) at 0x00000000 in 0.4 seconds (effective 454.7 kbit/s)...
A fatal error occurred: Packet content transfer stopped (received 24 bytes)
Ideas??

Try creating a .env file in the willow directory with:
FLASH_BAUD=115200
and run erase-flash and flash again.

No luck ... same issue
Using configuration overrides from .env file
Using venv for esptool
esptool esp32s3 -p /dev/ttyACM0 -b 115200 --before default_reset --after hard_reset write_flash --flash_mode dio --flash_freq 80m --flash_size 16MB 0x0 bootloader/bootloader.bin 0x10000 willow.bin 0x8000 partition_table/partition-table.bin 0x210000 srmodels/srmodels.bin 0x710000 audio.bin
esptool.py v4.5.1
Serial port /dev/ttyACM0
Connecting....
Chip is ESP32-S3 (revision v0.1)
Features: WiFi, BLE
Crystal is 40MHz
MAC: 7c:df:a1:e8:22:f8
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Flash will be erased from 0x00000000 to 0x00005fff...
Flash will be erased from 0x00010000 to 0x00191fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Flash will be erased from 0x00210000 to 0x005f3fff...
Flash will be erased from 0x00710000 to 0x0078ffff...
Compressed 22256 bytes to 13957...
Wrote 22256 bytes (13957 compressed) at 0x00000000 in 0.4 seconds (effective 455.3 kbit/s)...
A fatal error occurred: Packet content transfer stopped (received 24 bytes)
The erase was fine - of course that means the unit has nothing on the LCD now :)  But it just wont flash

We haven't done any testing with USB passthrough or VMs... Here's a workaround for you (for now):
./utils.sh dist
Disable USB passthrough to the VM.
Copy sallow-dist.bin to your host machine.
Unplug and plug-in your ESP BOX just to be sure.
Then head over to the ESP web flashing tool (Chrome is best if you have it)
Provide access to the port when prompted
Click the red "Erase flash"
Set flash address to 0x0
Click chose file, find sallow-dist.bin wherever you put it on your host.
Click Program

I suspect the USB device disconnects during flash. In another terminal, run journalctl -f -k to confirm that. If that's the case, you might be able to work around that by enabling download mode: press the BOOT/CONFIG button (top button on the left side) while powering up the device. Try flashing again after that.
If that doesn't work, you'll have to use the web flashing tool.

Strange - I program a lot of ESP chips with the same laptop and cable.  Im having no luck here - Tried the web tool, crashes at 2% - Erased again, enabled download mode, and same thing stops at 1 or 2%
esptool.js
Serial port WebSerial VendorID 0x303a ProductID 0x1001
Connecting....
Detecting chip type... ESP32-S3
Chip is ESP32-S3
Features: Wi-Fi,BLE
Crystal is 40MHz
MAC: 7c:df:a1:e8:22:f8
Uploading stub...
Running stub...
Stub running...
Changing baudrate to 921600
Changed
Erasing flash (this may take a while)...
Chip erase completed successfully in 1.443s
Compressed 7929856 bytes to 4295190...
Writing at 0x1000... (0%)
Writing at 0x1216f... (0%)
Writing at 0x1d225... (1%)
Writing at 0x287b3... (1%)
Error: Timeout

Im going to try a new cable - another attempt got to 4%
Writing at 0x0... (0%)
Writing at 0x1116f... (0%)
Writing at 0x1c225... (1%)
Writing at 0x277b3... (1%)
Writing at 0x2c265... (1%)
Writing at 0x3380e... (2%)
Writing at 0x3f3ea... (2%)
Writing at 0x4ab20... (3%)
Writing at 0x55fd0... (3%)
Writing at 0x5db1e... (3%)
Writing at 0x635f5... (4%)
Error: Timeout

I've seen this on S3 chips a bit, and recommend the boot/reset combination if you haven't tried it already

That's really good information! Flashing S3 has always been really reliable to me and I've never had to use the boot/reset trick but I'll add it to the README.

Yeah, still no luck - Ive tried the Windows Flasher, web, and of course the utils.sh flasher - the highest a flash has managed to get to is 5% before it fails.  Its usually 2-3% before it fails.
Ive tried 2 machines and countless different cables - and since its been erased, I only have a brick now with a black screen.  Bought from Adafruit and since it was erased and a flash was attempted, Im guessing they wouldnt accept a return on it.

Have you tried the boot/reset button combination as suggested by @stintel and @hamishcunningham :
"I suspect the USB device disconnects during flash. In another terminal, run journalctl -f -k to confirm that. If that's the case, you might be able to work around that by enabling download mode: press the BOOT/CONFIG button (top button on the left side) while powering up the device. Try flashing again after that."

I did - Ive tried programming using download mode and standard - Actually, without download mode the device will just loop now between connected and disconnected - If I enter download mode, it at least stays connected.

I had the same issue. Only using esptools from CLI worked, all other flashers didn't (multiple web, the Chinese one)
In my case, it is because I didn't erase_flash before first time Willow flash (it's in the manual....).
Your device is indeed boot looping
The device is recoverable, you can flash the demo bin on 0x0 and then erase_flash.

What's interesting about this issue is I would have expected the build steps would be the most problematic yet here we are.
The ESP BOX is manufactured by Espressif. We don't have anything to do with the hardware other than building software for it. After build, we use bog-standard esptool.py from Esspressif to flash a device that is 100% built and sold by Espressif. One perspective could be we have nothing to do with the flashing failures discussed in this issue.
However, I take ownership of issues users experience even it they're not technically our fault. We will work through this one way or another.

@robotica72 "Never had an issue like this, I use ESP32s in a lot of devices I create"
The ESP BOX uses the ESP32 S3 which is more-or-less the latest and greatest from Espressif. I suspect a lot of these issues are due to that. It's an "ESP32" but different enough to also kind of not be one at the same time.

A big difference is that the S3 has internal USB support, which means that most dev boards connect USB directly to the chip instead of to a separate UART translator like CP2104. This makes it harder to flash in my experience.
I've seen errors with older esptool versions that went away with later versions but I can't remember the exact numbers :(

Wow, thanks for letting me know! I missed that somehow and yes that's definitely a BIG difference vs ESP32.
By default we're installing the latest esptool.py 4.5.1 in the venv on the host for flashing. It can be overriden in the .env file so might be worth asking users to try different versions for now in case there's a regression or something in the latest-latest.

I just had success - I had to use the Python esptools in Windows to flash the firmware and it went through without any issues!
Maybe it will help others that have issues

Great! Let us know how things go!
None of the devs use Windows personally and I thought we might want to add something to use python esptools natively in Windows for Windows users. I'll just have to dig up something running Windows and work on it...

Yeah, I use Linux  a lot but only in VMs - I do 3D work too much and need my Windows tools for Photogrammetry, 3D Scanning, etc...
If I can offer anything to help on the Windows side to save you time, let me know

We'd really appreciate the help with Windows!
From what I remember we'll probably have to have users install Python from the official Windows installer and write a Powershell script? Does that make sense?

No worries! I don't mean to sound preachy but even though it might not look like it on the surface and with demo videos, etc Willow is still VERY young and I want to make sure people understand that.

@robotica72 #70

We'd really appreciate the help with Windows!
From what I remember we'll probably have to have users install Python from the official Windows installer and write a Powershell script? Does that make sense?

Makes sense - My Python27 is just a plain old install, so could use any deployment I think.  Just needs Python, pip and then pip install for the esptools (and of course the firmware).   The steps are pretty easy, assuming you have the FW file.
Ill joing this conversation from my "normal" GIT account, I use this one for only a few things and didnt mean to use it when I posted.

It's young but men is it everything I hoped for...! I do have some issues of course, will report / ask later

Its speedy, no doubt - instant for basic HA intents.   Im already thinking about how I can, finally, move on to having my HA be Jarvis - The voice part is pretty easy now with Willow - Now I need to figure out how to add feedback to my Google Home speakers when Willow executes something.  Ive re-created Jarvis' voice using services out there, but they are all API driven rather than local, so that will add delay to the replies (and a cost ... Im okay with a cost add-on if it works quick).

Thanks! Depending on which rev you have we've improved response times by about 30% in the last 24 hours or so.
We also introduced a new user-configurable VAD timeout (that depending on your rate of speech) is truly "did that really just happen?" fast.
Are you using local or server based speech rec? I only ask because the Willow Inference Server (open source release next week) and current default in the config (our best-effort community hosted server) can transcribe anything and you should be able to do everything you're describing with that.
We have audio output and TTS (WIS already provides TTS) on the roadmap for Willow.

Local for now - Just wanted to get the flash working and test it out at a high level - Hard to believe it an be improved actually!  (Its that good)
I was looking into the Inference Serer and that will be the way to go - I have no isses putting some GTX/RTX card in one of my servers just for that to make sure its quick - Im assuming it will be more about the RAM, so I wont need an RTX 4090 or anything crazy?

We've spent months highly optimizing the Willow Inference Server. Lowest support card is the GTX 1060 3GB to load base, medium, and large simultaneously and with the default model and settings we have on the community hosted server (Whisper medium > 40 languages, beam 1) it can transcribe 3.8 seconds of speech in 588ms on a GTX 1060. That's fairly long for a voice command but gives a general idea. Here are some other benchmarks:

Device
Model
Beam Size
Speech Duration (ms)
Inference Time (ms)
Realtime Multiple

RTX 4090
large-v2
5
3840
140
27x

H100
large-v2
5
3840
294
12x

H100
large-v2
5
10688
519
20x

H100
large-v2
5
29248
1223
23x

GTX 1060
large-v2
5
3840
1114
3x

Tesla P4
large-v2
5
3840
1099
3x

RTX 4090
medium
1
3840
84
45x

GTX 1060
medium
1
3840
588
6x

Tesla P4
medium
1
3840
586
6x

RTX 4090
medium
1
29248
377
77x

GTX 1060
medium
1
29248
1612
18x

Tesla P4
medium
1
29248
1730
16x

RTX 4090
base
1
180000
277
648x (not a typo)

I think it's clear we have a different approach to a locally hosted private voice assistant than the rest of the open source ecosystem and buying NVIDIA hardware may be off-putting for some users but I'm going to write up our approach, the thinking behind it, and of course the tangible results.
Long story short the approach up to this point has been to spend ~$120 (at retail prices) per Raspberry Pi as a voice assistant. I don't want to speak ill of projects but the results aren't going to threaten Alexa anytime soon and while we might not have a problem with a jumbled mess of wires, assembly, and managing what is a full Linux computer X number of assistants isn't compelling for most people.
With Willow it's $50 per assistant that can do local recognition. Or if you want Jarvis and are starting from zero you can buy a GPU off eBay (I think GTX 1070 is the sweet spot right now) for $120 and put it in an existing desktop or get something like a Dell Precision off eBay for $200 (I just ordered this exact configuration to demo and document it). So for us, the math breaks down thusly:
Four Raspberry Pis = $480 (MSRP pricing, in reality much more than that)
Something to run Home Assistant = another $120 (let's say Raspberry Pi again)
Total = $600
VS
Four Willows = $200
Machine of your choice from eBay = $200
GTX 1070 = $120
Total = $520
...and meanwhile this machine (with CUDA GPU with spare memory and compute) is going to absolutely crush a Raspberry Pi for Home Assistant and anything else tinkerers like us enjoy experimenting with.

Sorry, too excited to have mentioned this - if we want to move the GPU, etc discussions to GH discussions that would be better as eventually we'll close this issue and it will effectively disappear.

I ran into a failure flashing from my Linux host which I used to build the image using  Docker. So I began to use the method of copying the willow-dist.bin file so I could try and flash on Windows. I was able to erase the device using the ESPWebTool and then flashed it with the bin. However after the device boots up, it's stuck on a screen that says:
Welcome to Willow
Starting up (server)
Any ideas where I could have messed up?

I ran into a failure flashing from my Linux host which I used to build the image using Docker. So I began to use the method of copying the willow-dist.bin file so I could try and flash on Windows. I was able to erase the device using the ESPWebTool and then flashed it with the bin. However after the device boots up, it's stuck on a screen that says:
Welcome to Willow Starting up (server)
Any ideas where I could have messed up?

Strange - I didnt have any luck with the Webtool completing, so I used esptools on Windows in Python and it worked great.  Im wondering if that would fix your issue (No idea why, but since it worked well for me... who knows).

Figured it out! The config tool was appending data to items I was configuring such as my Wifi SSID and HomeAssistant URL. When I edited the sdkconfig file manually with pico in the container and re-built, it all worked fine!

Following all the suggestions I have gotten Willow Flashed across!
But am faced with the following error when I monitor
" (04:20:13.436) WILLOW: [ + ] HTTP client HTTP_STREAM_ON_REQUEST, length=4096
I (04:20:13.439) WILLOW: AUDIO_REC_VAD_END
Total bytes written: 45056
Total bytes written: 47104
I (04:20:13.509) AUDIO_ELEMENT: IN-[http_stream_writer] AEL_IO_DONE,-2
I (04:20:13.510) WILLOW: [ + ] HTTP client HTTP_STREAM_POST_REQUEST, write end chunked marker
I (04:20:14.123) HTTP_CLIENT: Body received in fetch header state, 0x3d955d93, 41
I (04:20:14.124) WILLOW: [ + ] HTTP client HTTP_STREAM_FINISH_REQUEST
I (04:20:14.128) WILLOW: Got HTTP Response = {"text":"Turn on light.","language":"en"}
I (04:20:14.138) WILLOW: sending command to Home Assistant via WebSocket: {
"end_stage":	"intent",
"id":<PHONE_NUMBER>,
"input":	{
"text":	"Turn on light."
},
"start_stage":	"intent",
"type":	"assist_pipeline/run"
}
I (04:20:14.245) WILLOW: home assistant response_type: error
I (04:20:14.250) WILLOW: received run-end event on WebSocket: {
"id":<PHONE_NUMBER>,
"type":	"event",
"event":	{
"type":	"run-end",
"data":	null,
"timestamp":	"2023-05-29T09:20:14.375267+00:00"
}
}
I (04:20:14.263) AUDIO_THREAD: The play_tone_err task allocate stack on external memory
I (04:20:16.165) AUDIO_ELEMENT: [http_stream_writer] AEL_MSG_CMD_PAUSE
I (04:20:24.271) WILLOW: Wake LCD timeout, turning off LCD
"

I tried to flash my first ESPbox last night and had trouble regarding the USB port as well.  I'll have to come back here with the actual error message but it was along the lines of not having access to the port.  I am running in a Terminal window in Ubuntu.  I had to use sudo for a lot of commands through the process as I was logged in as a normal? user.  (My Linux experience is limited)
When I executed the export PORT=/dev/ttyACM0 command, nothing displayed, it just seemed to accept the command and did a line return.  Is that expected?
When I entered the ./utils.sh erase-flash command I got a PORT error.

Hah yes, this is the issue that will never die ;).
Yes, the export isn't supposed to return anything. General long-standing Unix/Linux convention is to not output anything when a command is successful.
Almost all of these issues come down to permissions. Linux doesn't let regular users write to ports by default so you (usually) either need to be in the dialout group or use sudo with the serial port access commands. utils.sh checks for these things now and will try to (hopefully helpfully) tell you where things are going wrong.

I have updated the help text for these issues. Please run git pull in your willow directory and read the error messages from these various commands.
Let us know if it is helpful and leads to success or if you have any other additional issues or feedback!

Perfect!  That's for the new tips.  I got it flashed.  Now to get it connected to Home Assistant :-)

I was in the process of re-flashing my S3 with the latest updates, and now having the error of finding the USB device. I am also flashing via a VM with USB passthrough, but was fine the first time around, and also just flashed a different S3. just fine.
I've tried  resetting the environment ./utils.sh destroy and re-building but still no luck. The output from dmesg shows
[286570.045746] cdc_acm 2-1:1.0: ttyACM0: USB ACM device
[286573.387236] usb 2-1: USB disconnect, device number 82
[286575.892954] usb 2-1: new full-speed USB device number 83 using xhci_hcd
[286581.480928] usb 2-1: device descriptor read/all, error -110
[286581.816829] usb 2-1: new full-speed USB device number 84 using xhci_hcd
[286582.272759] xhci_hcd 0000:02:1b.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[286587.368799] usb 2-1: device descriptor read/all, error -110
[286587.369550] usb usb2-port1: attempt power cycle
[286588.020713] usb 2-1: new full-speed USB device number 85 using xhci_hcd
[286593.512687] usb 2-1: device descriptor read/8, error -110
[286598.888572] usb 2-1: device descriptor read/8, error -110

I ran into a bunch or USB disconnect issues myself yesterday. Try another cable and/or reduce FLASH_BAUD in utils.sh.

I had nothing but issues with passthrough (and Ive been around VMware since Workstation 1 and ESX 1.7) - Thats why I gave up and went to native Windows to flash, and that work right away.   I flashed about 20 times to test the workflow and it did fail once with a timeout, but it worked right after that.
Have you tried to enter download mode on the ESP before flashing?    That does see to help a lot when you have timeouts.

I'm at a point where it's no longer detecting the USB device when even trying to erase the flash, tried a couple cables, but no luck. dmesg will show the device listed, but ls -l /dev/ttyACM0 won't find it.

ls /dev/ttyACM*
too?
On Fri, 16 Jun 2023, 16:46 skrilla0, @.***> wrote:

I'm at a point where it's no longer detecting the USB device when even
trying to erase the flash, tried a couple cables, but no luck. dmesg will
show the device listed, but ls -l /dev/ttyACM0 won't find it.
—
Reply to this email directly, view it on GitHub
https://github.com/toverainc/willow/issues/60#issuecomment-1594895099,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABBRBFFJ4NRLJMZJM6G65PDXLR5VFANCNFSM6AAAAAAYHCOWQ4
.
You are receiving this because you were mentioned.Message ID:
@.***>

Yes, ls /dev/ttyACM* doesn't show the device anymore.
I tried connecting a different S3 that was recently successfully flashed, and host machine is able to identify the USB device fine. When I reconnect the problematic S3, the errors are there: device descriptor read/8, error -110
Could I have bricked the device creating this issue?

I haven't managed to brick any S3-based boards, but I have seen similar
behaviour where it is almost impossible to get them to flash, but then
once flashed they start working again. Mind you I've mostly been working on
boards that have the UF2 bootloader underneath, which is a whole other can
of worms :(
Sorry can't be more helpful!

We haven't done any testing with USB passthrough or VMs... Here's a workaround for you (for now):
./utils.sh dist
Disable USB passthrough to the VM. Copy willow-dist.bin to your host machine. Unplug and plug-in your ESP BOX just to be sure.
Then head over to the ESP web flashing tool (Chrome is best if you have it)
Provide access to the port when prompted Click the red "Erase flash" Set flash address to 0x0 Click chose file, find willow-dist.bin wherever you put it on your host. Click Program

Thank you!  I was having issues with the Box disconnecting in my Ubuntu VM and USB passthrough.   I used the flash_download_tool_3.9.5 from the Espressif website to flash the willow-dist.bin.
https://www.espressif.com/sites/default/files/tools/flash_download_tool_3.9.5.zip

Closing as we now offer https://flash.heywillow.io/.


New package: TextClassification v0.1.0

Registering package: TextClassification
Repository: https://github.com/sadit/TextClassification.jl
Created by: @sadit
Version: v0.1.0
Commit: 1e625930c429ba5694e5a7fb0ddfc515b48ed414
Reviewed by: @sadit
Reference: https://github.com/sadit/TextClassification.jl/commit/1e625930c429ba5694e5a7fb0ddfc515b48ed414#commitcomment-36192959

please don't merge this PR, I will prepare another one following the recommendations


Master to Live

Docs Build status updates of commit 558a7ea:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/app-only-auth-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 558a7ea:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/app-only-auth-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[bug]: Documentation playground example application error

Describe the bug
ee36f67b-a857-4e24-b46d-cea87008bb49.webm
Affected component/components
Examples/Playground : Combobox
How to reproduce

Go to examples.
Go to playground.
Click on load preset combobox

Codesandbox/StackBlitz link
No response
Logs
No response
System Info
Chrome

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

Thank you for finding a solution! This fixed my issues with combobox.


check the notes!

Hiya bb,
Thank you for this!
Shé
On Saturday, January 30, 2021, 04:11:03 PM CST, dwayne<EMAIL_ADDRESS>wrote:
You can view, comment on, or merge this pull request online at:
https://github.com/abduamal/Financierv2/pull/1
Commit Summary

File Changes

A notes.md (25)

Patch Links:

https://github.com/abduamal/Financierv2/pull/1.patch
https://github.com/abduamal/Financierv2/pull/1.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Are local options mandatory? Some errors I encountered in this branch.

https://github.com/neuromodulation/perceive/blob/45915ca36c8160e7d4e94bff99f91604757a8780/perceive_options.m#L73
I tried to run this branch today and got the following errors:

perceive
Error using perceive_options (line 108)
perceive_options: perceive_options_local.m was not present > generated in the current directory E:\OneDrive - Charité - Universitätsmedizin
Berlin\Dokumente\Data_non_BIDS_data\PERCEPT\sub-011. Please review it, adapt according to your needs, but DO NOT COMMIT this file! Then, rerun
perceive.

Error in perceive (line 55)
popt = perceive_options();
After that I ran it again and it resulted in this error:
Dot indexing is not supported for variables of this type.
Error in pdisp (line 18)
if level<=popt.verbosity
Error in perceive_options (line 71)
pdisp('Error using local options, please check ''perceive_options_local.m''.');
Error in perceive (line 55)
popt = perceive_options();

Thanks for reporting.
There was a bug in pdisp.m (sorry for that). It does not signal a problem with local options.
The bahaviour of generating local options is desired (and only happens once when no local options exist).

Ok, I will try it again!

Ok, awesome, it worked now. Although I do not quite understand why we would want to create it in cases where the user does not want to change any options? Also, maybe it would be nicer to have it in the perceive folder?

When the user does not want to change any options, they would simply leave the local options empty. My motivation for local options was twofold:
i) if there are only global options, the user would change them and unintentionally commit them affecting other users,
ii) several versions of local options can be created serving the purpose of e.g. specific settings for specific data (e.g. you may want to routinely process data from one lab, but debug data from another lab, where you would need to increase the verbosity of messages and increase the number of open figures)
Local options get created in the directory where you run perceive from, usually the perceive folder itself.
If, however, you have perceive on matlab path, you may run it from anywhere, and local options get created there. This is intended behaviour. You don't like it? I understand that some users would argue against creating local options in folders with data...


added customFormats argument to moment and globalize localizer

This PR added a customFormats argument to moment and globalize localizer function
Use case: in my calendar I want to format time string in gutter in different format but keep other format as default, I'll have code like
const localizer = BigCalendar.momentLocalizer(moment, {timeGutterFormat: 'LTS'});

is there a big advantage to this approach over passing a formats prop to the Calendar itself? Generally there aren't a lot of calendar instances in most apps

👍 Good point, I'm new to the library and missed the formats prop of the Calendar. Will close the PR