Add copyright headers to all files

Add Copyright headers

[ ] pywps-3.2 (GNU/GPL)
[ ] pywps-master (MIT)

On my branch I have commited the files with the licenses. I am have used the MIT on python-master with the following:
Copyright (C) 2014-2016 PyWPS Development Team, represented by
PyWPS Project Steering Committee

I am not certain if it should be represented by PyWPS Project Steering Committe or just @jachym. I prefer the first

Where I found the authors name (mainly @mgax  @Noctalin ) I have included them on author, I thinking to put a table on line and ask for people to fill it to clain authorship of code

The code needs to be passed by flake8 at least to check if modules are being used, already noticed some declared modules that are not used

Pull request: I would do it after I pass everything through flake8, @jachym  are all the points above OK with you ???

Good idea!  Suggestions:

let's get consensus on a standard header template
I would do a flake8 sweep separate/after a consistent header sweep to have a single clean commit of the header sweep

I'd argue against spamming each source file with a copyright header. It's common practice to just provide a LICENSE.txt file at the top level of the repo. But I think making a single commit to clean up pep8 issues is a great idea.

Having a standard header file is a requirement for OSGeo incubation and IMHO any project serious about copyright, distribution and related issues.

any project serious about copyright

I submit to you a source file from the Django project, I believe they qualify as "serious" :) No copyright header in there. And maybe it's a good time to raise the issue about this particular OSGeo incubation requirement. :)

@mgax thanks for the example ;)  Agree, worth a discussion, I will raise.

Update: thread started in https://lists.osgeo.org/pipermail/incubator/2016-September/003165.html.

A Licence file does not replace a Copyright notice. In Europe Copyright applies by default, but this is not the case elsewhere (e.g. US). Therefore I would argue for a Copyright notice in each file header, with a reference to the Licence file.

Hi to all
Will had my 2 cents. Yes adding a big header is a pain and having to update the dates even worst, but is a job that has to be done, and better to be "pedantic" now than to be sorrow in the future, meaning I am more in favor of  a copyright notice in each file header, I think that the heard was the standard in the past but people and new project stopped using it.
I have read the comments on the thread started by Tom, and maybe a good solution would be a smaller header like this:

/* (c) 2017 Open Source Geospatial Foundation - all rights reserved

This code is licensed under the GPL 2.0 license, available at the root
application directory.
*/
This is inline with the suggestion from @ldesousa

Precisely. The header needs only two lines: copyright notice and a reference to the licence file.

Update: this turns out to be not a hard OSGeo requirement after some clarifications.  I'm okay with going with @ldesousa's suggestion.

How about this? I think the "all rights reserved" is implied if you state the copyright owner.
# (c) 2017 OSGeo, licensed under GPL 2.0, see LICENSE.txt

Shall we also include the development team ???? and the author on the python code or not necessary?
(c) 2017 OSGeo, licensed under GPL 2.0, see LICENSE.txt on root directory PyWPS Development Team, represented by PyWPS Project Steering Committe
author = "Santa's little helper"
email  =<EMAIL_ADDRESS>Any email is not a good idea to void spammer crawlers?

Most files have more than one author, I would leave that bit out. On the demo this might make sense, but I guess not here.
Another thing: I doubt we can have copyright assigned to mlre than one entity. I suggest something like: Copyright OSGeo Foundation, represented by the PyWPS PSC.

PyWPS4.0(master)
Copyright 2016 OSGeo Foundation, represented PyWPS Project Steering Committe, licensed under MIT, see LICENSE.txt on root directory.
Personal authors only relevant on demos.
Do we need a final approval vode?

I would remove 'on root directory', otherwise looks good to me.
+1 to put to a vote.

+1 (also vote for remove of on root directory)

+1
I usually wirte something like: "Please consult the LICENCE file for details."

Implementing
PyWPS3-2:
Copyright 2016 OSGeo Foundation, represented PyWPS Project Steering Committe, licensed under GPL 2.0, Please consult LICENSE.txt for details.
PyWPS4.0(master)
`
Copyright 2016 OSGeo Foundation, represented PyWPS Project Steering Committe, licensed under MIT, Please consult LICENSE.txt for details.

Everything done made two pull requests #192 #193, when they are accepted please close issue

Thanks all!


Add versioning to NPI interfaces

This issue is to track adding versioning to the NPI interfaces for any future changes, to make sure new ebpfcore can still work with older extension drivers, in case the NPI interface changes.

https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/netioddk/ns-netioddk-_npi_provider_characteristics already has Version and Length.


Websocket connections not properly closed when switching regions

Expected behavior:
when I switch regions the existing websocket is closed.
Actual behavior:
It stays open
See https://www.loom.com/share/8dada9ce011f4e1d8dca42d499370feb

@ganchoradkov in your experimentation with manual websocket disconnecting at the client level, did you find a reliable way to do this?
Or is this a matter of implementing something like transportClose first as we discussed here: https://walletconnect.slack.com/archives/C03RME3BS9L/p1663859970679629

@bkrem, the way I managed to handle disconnect is more of a work-around and we really need to implement something like  transportClose
Currently, the only way to disconnect the socket is to call core.relayer.provider.connection.close() and to disable 2 event loops

heartBeat - it does jsonRPC request which reconnects the socket
RELAYER_PROVIDER_EVENTS.disconnect which listens for socket disconnect & reconnects it after a given delay

changing the relay url is only possible during core initialization.
The bottom line is - we need the transportClose to handle the above steps automatically

@ganchoradkov added an issue here (https://github.com/WalletConnect/walletconnect-monorepo/issues/1507)
Added all the relevant use cases I was aware of, please correct/augment as necessary based on your findings :pray:

Superseded by #149


CFR/RFD Weekly Report Redash Visualizations

Title of ticket:
Description
Summarize issue : Create Redash Visualization for CFR/RFD Weekly Report. Since OC environment is not ready @VineetBala-AOT  is developing this locally first, then will migrate to DEV, TEST
Dependencies
Are there any dependencies? - Since Environment is not Ready on OC, might need to migrate Visualizations to DEV, TEST once its up
DOD

[ ] Create Visualization for the listed reports (Locally)
[ ]  Confirm filters with business
[ ]  Confirm Visualization with Business
[ ]
[ ]


arch: arm: nordic: nrf52: Enable instruction cache

Enable the instruction cache by default in order to achieve a speedup of
up to 20% in code execution.
Signed-off-by: Carles Cufi<EMAIL_ADDRESS>

There is one thing here, @carlescufi : this code might not be executing from cold/warm reset, right?
So, the way you do it, you might be keeping cache profiling on, too.

Codecov Report

Merging #7970 into master will increase coverage by 3.71%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #7970      +/-   ##
==========================================
+ Coverage   51.31%   55.03%   +3.71%
==========================================
  Files         441      481      +40
  Lines       42284    53943   +11659
  Branches     8066    10474    +2408
==========================================
+ Hits        21700    29690    +7990
+ Misses      20065    19984      -81
- Partials      519     4269    +3750

Impacted Files
Coverage Δ

subsys/random/rand32_timer.c
0% <0%> (-100%)
:arrow_down:

drivers/console/native_posix_console.c
22.36% <0%> (-77.64%)
:arrow_down:

ext/lib/crypto/tinycrypt/source/ecc_dh.c
46.42% <0%> (-39.29%)
:arrow_down:

ext/lib/crypto/tinycrypt/source/cbc_mode.c
58.97% <0%> (-35.9%)
:arrow_down:

ext/lib/crypto/mbedtls/library/ecjpake.c
51.12% <0%> (-35.7%)
:arrow_down:

ext/lib/crypto/mbedtls/library/ecp.c
39.46% <0%> (-34.38%)
:arrow_down:

subsys/net/ip/net_stats.h
65.83% <0%> (-34.17%)
:arrow_down:

ext/lib/crypto/mbedtls/library/cipher_wrap.c
17.39% <0%> (-30.76%)
:arrow_down:

boards/posix/native_posix/cmdline.c
19.35% <0%> (-30.65%)
:arrow_down:

tests/crypto/mbedtls/src/mbedtls.c
43.05% <0%> (-30.56%)
:arrow_down:

... and 538 more

Continue to review full report at Codecov.

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


Test epoch processing rewards/penalties

This is a select set of tests isolated from the other tests that are included in the spec-freeze itself. Tests quality and feature-completeness was prioritized over rushing these in. Now after spec-freeze, the goal is to provide these as an addition (perfectly backwards compatible / not touching the spec itself), to complete the coverage.
Part of this functionality is already covered by the block tests and others. But to complete it, we need to dig into simulation of attestation (as done for earlier epoch processing justification/finalization tests), and crosslinks. Then see if we can cleanly model the balance changes for assertions.
TODO in process_rewards_and_penalties:

[ ] matching penalties/rewards

[ ] matching head: penalty, reward, none, both
[ ] matching target: penalty, reward, none, both
[ ] matching source: penalty, reward, none, both

[ ] proposer inclusion delay
[ ] inactivity penalty
[ ] crosslink committee:

[ ] penalty if not in committee, reward if in committee
[ ] no crosslink, empty participation, everyone penalty

Are these tests still TODO?

At the time it was considered too convoluted to setup tests for rewards/penalties, since the spec itself doesn't really isolate the computation from that of the chain inputs. But crosslinks have been removed, so it should be better now. I can pick it up now, but also want the phase1 pr merged first (and remaining complexities with factoring in phase 1 functionality). Maybe close this in favor of a phase1 ready testing issue?

Maybe close this in favor of a phase1 ready testing issue?

Sure, go ahead if you think that's the way forward :) I'm mainly doing a pass on old/stale issues.

Closing in favor of #1526


Deep Dive in to Diffusion Models

Title of the talk
Deep Dive in to Diffusion Models
Description
Introduction, Maths, and Training Diffusion Models. Presentation, Walk Through, and Other details on how Diffusion Models Work.
A workshop can be hosted if people show interest in the talk
What format do you have in mind for your talk?
Talk
Table of contents
Agenda:

Popular Diffusion Models
Diffusion Models capabilities, Use cases, shortcomings, etc.
Using opensource Python Libraries to train, deploy custom/ Personal diffusion moels
Training a diffusion model
Maths behind diffusion models

What domain would you say your talk falls under?
Data Science & Machine Learning
Duration in minutes (including Q&A)
45
Prerequisites
Basics of Machine Learning
Speaker bio
https://www.linkedin.com/in/varskann/
Working as Staff DS with one of the Cutting edge Saas companies in AI, with over 8 years of experience in the field
The talk/workshop speaker agrees to

[X] Share the slides, code snippets and other material used during the talk

[X] If the talk is recorded, you grant the permission to release
the video on BangPyper's YouTube
channel
under CC-BY-4.0
license

[X] Not do any hiring pitches during the talk and follow the Code
of
Conduct

@varskann Would you be willing to do this session on Nov 25th meetup?

@varskann Gentle reminder to confirm.

Hello,
I didn't receive any confirmation email before last week! I have come to my
native now and haven't planned for the presentation due to no confirmation!
I can plan for next month, if I can get some prior confirmation for the the
presentation eligibilty
Thanks,
Kanishk Varshney
On Sat, 11 Nov 2023, 00:11 Ani, @.***> wrote:

@varskann https://github.com/varskann Gentle reminder to confirm.
—
Reply to this email directly, view it on GitHub
https://github.com/bangpypers/meetup-talks/issues/15#issuecomment-1806240446,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABEIDPPKZADIJWUTJ7FB4ALYDZYL5AVCNFSM6AAAAAA43PTHNGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBWGI2DANBUGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

@varskann Can you present on Dec 16th meetup?

@anistark  I won't be in Bangalore for this week. Is it going to be an online talk?

@anistark I won't be in Bangalore for this week. Is it going to be an online talk?

No. It's only offline.

Oh, When is the Jan meetup? Can prepare the deck for that

Hey @varskann
Jan meetup is on 20th. Would you be presenting in it?

@anistark  you will have to update me a bit earlier. Let's do this, I am assuming Feb meetup will be on 20th? I will present in that meetup? Does that work for you?

Haven't planned for Feb meetup yet. Anyway, it'll be on 17th, if happens. But can only confirm closer to date. If you're visiting the city, it's fine. Or I'm sure there's a local python meetup where you can present your talk.
Closing this issue for now given it's been hanging for a while. If you're in the city, do feel free to reopen or submit new.

No no, I am stay in Bangalore only, just traveling once a month.
Coincidently the dates are clashing with your meetups.
I can start preparing for February one just in case... I have partial
material ready.
Thanks
On Thu, Jan 4, 2024 at 5:05 PM Ani @.***> wrote:

Haven't planned for Feb meetup yet. Anyway, it'll be on 17th, if happens.
But can only confirm closer to date. If you're visiting the city, it's
fine. Or I'm sure there's a local python meetup where you can present your
talk.
Closing this issue for now given it's been hanging for a while. If you're
in the city, do feel free to reopen or submit new.
—
Reply to this email directly, view it on GitHub
https://github.com/bangpypers/meetup-talks/issues/15#issuecomment-1876952147,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABEIDPKMEGWZSJERRYVMHJLYM2HZ3AVCNFSM6AAAAAA43PTHNGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZWHE2TEMJUG4
.
You are receiving this because you were mentioned.Message ID:
@.***>


Delay constraints

They kick in for single taps. Try only enabling after first drag callback.

Fixed with https://github.com/mfikes/impedance-converter/commit/0780ddd7402970170983a4a67ca9e7ec6475d51f


Support for multiple HTTPMethod handler for different routes in the same AWS Lambda handler

Firstly, thanks for this project. This is really helpful in stubbing up the handler for the API gateway.
I'm fairly new to the vandium and I was wondering how does one enable multiple handlers for routes
e.g.
GET /users
GET /user/1
Is it possible to do this via a single aws lambda handler or would I need to create separate handlers
Thanks in advance

You could, but it's not the most optimal from a security, testing and architecture perspective. I would suggest having each operation in a separate handler, use a layer to consolidate common logic and apply the least permissive access constraints. Testing a single operation will be a lot easier, and long term technical debt will be lower.
For my own projects, I am using AWS CDK rather than SAM or serverless, as it lets me deploy my application via code rather than configuration files.

Thanks @richardhyatt for the insights, much appreciated.
It's just that the api-gateway example in the docs show the GET, POST in a single handler due to which I presumed that is recommended way of implementing the handlers via vandium.
I understand and totally agree with the approach of separating the handlers for each operation and did feel like the obvious way of doing so.
Thanks again.


validation_epoch_end(self, outputs):

this method not have the “outputs”。。。。how to fix it

https://github.com/Lightning-AI/pytorch-lightning/issues/19419
Please check your version.
https://github.com/naver-ai/egtr/blob/7f87450f32758ed8583948847a8186f2ee8b21e3/train_egtr.py#L339
Our code uses validation_epoch_end instead of on_validation_epoch_end.

Hi I am using version 1.9.5 and it still shows this error


[Feature] filter dispatched events in event listener

What problem does this feature solve?
When I dispatch an 'datazoom' event manually, my 'datazoom' listener can know it is from code instead of user operations
What does the proposed API look like?
myChart.dispatchAction({
type: 'dataZoom',
emitEvent: false,
start: 20,
end: 30
});

Currently, you can put an extra parameter as a flag into the action payload and check it in the event handler. For example,
chart.on('datazoom', e => {
  if (e.emitEvent) {
    // do something
  }
})

chart.dispatchAction('datazoom', {
  type: 'dataZoom',
  emitEvent: false,
  start: 20,
  end: 30
})


[Feature] Add guidance to use .NET Standard instead of PCL

PCLs are less important now that .NET Standard 2.0 is coming.
We need to update our guidance to recommend .NET Standard - based libraries instead of creating PCLs.

I think this initiative should be carried out as soon as possible.
Documentation on PCL, such as this and this should be marked as obsolete.

This item is for more extensive revision of topics such as https://docs.microsoft.com/en-us/dotnet/standard/cross-platform/

During the last releases, we've updated and moved much of this content.  In particular, the introduction to .NET Standard highlights the new guidance.
Closing as completed.


Execution of Installer Codeunit

Based on this article it's not very clear when a "Installer Codeunit" is actually executed.
If I'm not mistaken, when an app gets an update with a new version ... the old version is uninstalled and the new version is installed. In this case the installer codeunit is not executed. For that scenario only upgrade codeunits are executed.
But the code example in this doc suggests that the installer codeunit can handle fresh installations and also reinstallations.
I was a bit surprised by this behaviour. As a user I expect that an installation of an app always runs through some installer code and makes sure that important base data is always there.

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

ID: c6dd7c9e-51a5-eeea-a2f6-dd4d40b93295
Version Independent ID: d6fb1d1b-fa2e-606e-6c79-115651b60a29
Content: Writing extensions installation code - Business Central
Content Source: dev-itpro/developer/devenv-extension-install-code.md
Service: dynamics365-business-central
GitHub Login: @jswymer
Microsoft Alias: solsen

Thanks for the feedback!
We've updated the article in hopes of making this more clear.
Install code is run only when an extension version is first installed or reinstalled by running the Install-NAVApp cmdlet or from the Extension Management page in the client. Install code isn't run when a new version of an existing extension is installed as part the upgrade operation using the Start-NAVAppDataUgrade cmdlet.
The update will be available soon.


mstatus.VS field location in version 0.8

I'm confused about the sequence of events regarding the changed location of the mstatus.VS field. Could you please confirm whether this field is at position 10:9 or 24:23 in release 0.8?
Reading backwards, the changes seem to be these:
February 9th 2020, commit bdb8b55 (Merge pull request #351 from jhauser-us/vs-field-10-9): seems to modify field location from 24:23 to 10:9. This postdates version 0.8.
December 14th 2019, commit 9a65519 (This version is official v0.8 release of vector spec): this defines version 0.8.
December 8th 2019, commit d8fbe85 (Move mstatus/sstatus VS field to bits 10:9): also seems to modify field location from 24:23 to 10:9. This predates version 0.8.
I'm no GitHub expert, but how can the same change seem to happen both before and after version 0.8, and which change wins?

On December 8th, John Hauser authored the commit d8fbe859002979aedf9d34d5be0a57262c45f20f and opened #351 to propose this change for inclusion in the spec. At this point the commit was not yet incorporated into this repository: if you had downloaded the spec or visited the URL https://github.com/riscv/riscv-v-spec/blob/master/v-spec.adoc, you would have seen mstatus.VS still in position 24:23. The pull request sat untouched for a long time, and during this time release 0.8 was made.
Then, on February 9th, Krste accepted/merged #351 and thereby incorporated these changes into the official version of the specification. Although this was just an administrative act, it is a separate commit in git (bdb8b5574ead5e8036d5f79902d4911a24d8c862), and GitHub displays what effectively changed as a consequence. In this case, no merge conflicts had to be resolved, so the change authored by John Hauser applied unmodified. Indeed, if you ask git or GitHub who authored the line "A vector context status field, VS, is added to mstatus[10:9] and shadowed" in the current version of the spec, it points to John Hauser's original commit.
In conclusion: this change was first proposed before release 0.8, but only incorporated into the specification some time after the release. In the official release 0.8, the VS field is in position 24:23.

Thanks Hanna.


Issues installing @sap/cds-dk on Windows 10

Hello CAP Team,
as the issues reported about the installation of  @sap/cds-dk on Windows  in the CAP OpenSAP course increase I create this issue to track the topic better. I've just also tried to install @sap/cds-dk on my Windows 10 system with this release:

I've used the following command:
C:\Users\Gregor>npm rm -g @sap/cds

npm WARN deprecated<EMAIL_ADDRESS>this package has been deprecated
removed 69 packages in 1.063s

C:\Users\Gregor>npm i -g @sap/cds-dk
npm WARN deprecated<EMAIL_ADDRESS>Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)

><EMAIL_ADDRESS>preinstall C:\Users\Gregor\AppData\Roaming\npm\node_modules\@sap\cds-dk
> node ./lib/util/preinstall.js

The command 'cds' has moved from library @sap/cds to @sap/cds-dk.
It is recommended to remove the global version of @sap/cds and
reinstall @sap/cds-dk via
    npm rm -g @sap/cds
    npm i -g @sap/cds-dk

npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\@sap\cds-dk\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>preinstall: `node ./lib/util/preinstall.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>preinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\Users\Gregor\AppData\Roaming\npm-cache\_logs\2020-04-23T05_39_29_058Z-debug.log

at the end of the debug.log file I see this errors:
6998 verbose stack Error<EMAIL_ADDRESS>preinstall: `node ./lib/util/preinstall.js`
6998 verbose stack Exit status 1
6998 verbose stack     at EventEmitter.<anonymous> (C:\Users\Gregor\AppData\Roaming\nvm\v12.16.1\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
6998 verbose stack     at EventEmitter.emit (events.js:311:20)
6998 verbose stack     at ChildProcess.<anonymous> (C:\Users\Gregor\AppData\Roaming\nvm\v12.16.1\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
6998 verbose stack     at ChildProcess.emit (events.js:311:20)
6998 verbose stack     at maybeClose (internal/child_process.js:1021:16)
6998 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
6999 verbose pkgid<EMAIL_ADDRESS>7000 verbose cwd C:\Users\Gregor
7001 verbose Windows_NT 10.0.17763
7002 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "i" "-g" "@sap/cds-dk"
7003 verbose node v12.16.1
7004 verbose npm  v6.13.4
7005 error code ELIFECYCLE
7006 error errno 1
7007 error<EMAIL_ADDRESS>preinstall: `node ./lib/util/preinstall.js`
7007 error Exit status 1
7008 error Failed at the<EMAIL_ADDRESS>preinstall script.
7008 error This is probably not a problem with npm. There is likely additional logging output above.
7009 verbose exit [ 1, true ]

hope that someone who can fix this issue can also replicate it and provide a fixed version.
CU
Gregor

Hi @gregorwolf
first of all thanks for the detailed error description.
It looks like @sap/cds has not been removed correctly.
Could you run the following command?
npm list -g -depth 0

It should not list @sap/cds.
And also list the content of
dir C:\Users\Gregor\AppData\Roaming\npm\node_modules\@sap\cds

If the above folder exists, delete it and rerun the installation.
Thanks
Jörg

Thank you @joergmann, I've fixed the problem by deleting everything in C:\Users\Gregor\AppData\Roaming\npm\node_modules and removing the cds* files in C:\Users\Gregor\AppData\Roaming\npm\


(PUP-9469) Remove func3x_check setting

Remove func3x_check setting which made it possible to disable 3x function
checking and stray single quote in the exception message.
Preserve the "illegal function is loaded" test to show the behavior when an
invalid 3x function is loaded.

CLA signed by all contributors.


NIFI-11109 Allow registry client's class in flow.xml/json to not change when underlying nar for nifi-flow-registry-client-nar is missing

Summary
NIFI-11109
If nifi registry client comes up in "ghost" mode.  It can never be restored.   This resolves this situation.
To verify fix:
Start nifi
configure registry client (i.e. Global Menu -> Controller Settings -> Registry Clients)
Verify there are no warnings associated with registry client
Stop nifi
move  nifi-flow-registry-client-nar (found in lib directory) to another directory
Start nifi
Verify registry client (at above mentioned location) does not work (i.e. it will have a warning as it is now in ghost mode)
Restore  nifi-flow-registry-client-nar to lib directory
Restart nifi
Verify earlier warning is gone and registry client is restored
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[x] Apache NiFi Jira issue created

Pull Request Tracking

[x] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[x] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[x] Pull Request based on current revision of the main branch
[x] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[x] Build completed using mvn clean install -P contrib-check

[x] JDK 11
[x] JDK 17

Licensing

[x] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[x] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[x] Documentation formatting appears as expected in rendered files

Thanks for identifying and fixing @NissimShiman ! Looks good to me. +1 will merge.

Thank you @markap14 !


EISDIR: illegal operation on a directory error on React Native debug

Description
Hi, I've a problem with embedded Metro bundler dependency when I launch the debug in a completely fresh React Native application.
React Native version:
$ react-native info
info Fetching system and libraries information...
System:
    OS: Linux 5.11 Ubuntu 20.04.3 LTS (Focal Fossa)
    CPU: (8) x64 Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz
    Memory: 4.46 GB / 15.52 GB
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 14.17.5 - ~/.nvm/versions/node/v14.17.5/bin/node
    Yarn: Not Found
    npm: 7.22.0 - ~/.nvm/versions/node/v14.17.5/bin/npm
    Watchman: Not Found
  SDKs:
    Android SDK: Not Found
  IDEs:
    Android Studio: Not Found
  Languages:
    Java: 15.0.1 - /home/ccarcaci/jdks/jdk-15.0.1/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: https://github.com/expo/react-native/archive/sdk-42.0.0.tar.gz => 0.63.2
  npmGlobalPackages:
    *react-native*: Not Found

Expo version:
$ expo --version
4.11.0

Steps To Reproduce

I've started a fresh project following the guide Environment Setup with Expo.
My project sources are here.
I've created a new Android AVD.
Then I launched the application using $ npm run android command.
Application is running (see screenshot below).
No errors in the console log (see related console log section below).
When I open the debugger I get an EISDIR error in Expo console log and no debugger worker is shown (see related console log section below).
Browser debugger is displaying some mapping problems (see screenshot below).

Expected Results
I'd like to be able to debug my code.
Snack, code example, screenshot, or link to a repository:
Application is running:

No errors at first:
$ npm run android

> android
> expo start --android

Starting project at /home/ccarcaci/git/EisdirErrorInvestigation
Developer tools running on http://localhost:19002
Opening developer tools in the browser...
Starting Metro Bundler
› Opening exp://<IP_ADDRESS>:19000 on Pixel

  (QR Code)

 › Waiting on exp://<IP_ADDRESS>:19000
 › Scan the QR code above with Expo Go (Android) or the Camera app (iOS)

 › Press a │ open Android
 › Press w │ open web

 › Press r │ reload app
 › Press m │ toggle menu
 › Press d │ show developer tools
 › shift+d │ toggle auto opening developer tools on startup (enabled)

 › Press ? │ show all commands

Logs for your project will appear below. Press Ctrl+C to exit.
info Launching Dev Tools...
Android Bundling complete 29039ms
Android Running app on sdk_gphone64_x86_64(image)

EISDIR error is displayed:
Error: EISDIR: illegal operation on a directory, read
    at Object.readSync (fs.js:614:3)
    at tryReadSync (fs.js:383:20)
    at Object.readFileSync (fs.js:420:19)
    at UnableToResolveError.buildCodeFrameMessage (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:304:17)
    at new UnableToResolveError (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:290:35)
    at ModuleResolver.resolveDependency (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:168:15)
    at DependencyGraph.resolveDependency (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph.js:353:43)
    at /home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/lib/transformHelpers.js:271:42
    at Server.<anonymous> (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/Server.js:842:41)
    at Generator.next (<anonymous>)
Error: EISDIR: illegal operation on a directory, read
    at Object.readSync (fs.js:614:3)
    at tryReadSync (fs.js:383:20)
    at Object.readFileSync (fs.js:420:19)
    at UnableToResolveError.buildCodeFrameMessage (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:304:17)
    at new UnableToResolveError (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:290:35)
    at ModuleResolver.resolveDependency (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:168:15)
    at DependencyGraph.resolveDependency (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph.js:353:43)
    at /home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/lib/transformHelpers.js:271:42
    at Server.<anonymous> (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/Server.js:842:41)
    at Generator.next (<anonymous>)

Browser debugger screen:

Further investigations done on my own:
I've added the console.log(this.originModulePath); call before this line in my dependencies. The Expo console output is:
/home/ccarcaci/git/EisdirErrorInvestigation/.
Error: EISDIR: illegal operation on a directory, read
    at Object.readSync (fs.js:614:3)
    at tryReadSync (fs.js:383:20)
    at Object.readFileSync (fs.js:420:19)
    at UnableToResolveError.buildCodeFrameMessage (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:305:17)
    at new UnableToResolveError (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:290:35)
    at ModuleResolver.resolveDependency (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:168:15)
    at DependencyGraph.resolveDependency (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph.js:353:43)
    at /home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/lib/transformHelpers.js:271:42
    at /home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/Server.js:1097:37
    at Generator.next (<anonymous>)

It seems that Metro is unable to package correctly the debugger worker .js files.
I don't know how to proceed to enable debugging.

Unsubcribe
On Sun, Sep 19, 2021, 3:16 PM ccarcaci @.***> wrote:

Description
Hi, I've a problem with embedded Metro bundler dependency when I launch
the debug in a completely fresh React Native application.
React Native version:
$ react-native info
info Fetching system and libraries information...
System:
OS: Linux 5.11 Ubuntu 20.04.3 LTS (Focal Fossa)

CPU: (8) x64 Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz

Memory: 4.46 GB / 15.52 GB

Shell: 5.0.17 - /bin/bash

Binaries:
Node: 14.17.5 - ~/.nvm/versions/node/v14.17.5/bin/node

Yarn: Not Found

npm: 7.22.0 - ~/.nvm/versions/node/v14.17.5/bin/npm

Watchman: Not Found

SDKs:
Android SDK: Not Found

IDEs:
Android Studio: Not Found

Languages:
Java: 15.0.1 - /home/ccarcaci/jdks/jdk-15.0.1/bin/javac

npmPackages:
@react-native-community/cli: Not Found

react: 16.13.1 => 16.13.1

react-native: https://github.com/expo/react-native/archive/sdk-42.0.0.tar.gz => 0.63.2

npmGlobalPackages:
*react-native*: Not Found

Expo version:
$ expo --version
4.11.0
Steps To Reproduce

I've started a fresh project following the guide Environment Setup
with Expo https://reactnative.dev/docs/environment-setup.
My project sources are here
https://github.com/ccarcaci/eisdir-error-investigation.
I've created a new Android AVD.
Then I launched the application using $ npm run android command.
Application is running (see screenshot below).
No errors in the console log (see related console log section
below).
When I open the debugger I get an EISDIR error in Expo console log
and no debugger worker is shown (see related console log section below).
Browser debugger is displaying some mapping problems (see
screenshot below).

Expected Results
I'd like to be able to debug my code.
Snack, code example, screenshot, or link to a repository: Application is
running:
[image: Screenshot from 2021-09-19 10-48-56]
https://user-images.githubusercontent.com/7973726/133922773-8f30db9a-3553-4702-9bcf-2fd54c364263.png
No errors at first:
$ npm run android

android

expo start --android

Starting project at /home/ccarcaci/git/EisdirErrorInvestigation
Developer tools running on http://localhost:19002
Opening developer tools in the browser...
Starting Metro Bundler
› Opening exp://<IP_ADDRESS>:19000 on Pixel
(QR Code)
› Waiting on exp://<IP_ADDRESS>:19000
› Scan the QR code above with Expo Go (Android) or the Camera app (iOS)
› Press a │ open Android
› Press w │ open web
› Press r │ reload app
› Press m │ toggle menu
› Press d │ show developer tools
› shift+d │ toggle auto opening developer tools on startup (enabled)
› Press ? │ show all commands
Logs for your project will appear below. Press Ctrl+C to exit.
info Launching Dev Tools...
Android Bundling complete 29039ms
Android Running app on sdk_gphone64_x86_64(image)
EISDIR error is displayed:
Error: EISDIR: illegal operation on a directory, read
at Object.readSync (fs.js:614:3)

at tryReadSync (fs.js:383:20)

at Object.readFileSync (fs.js:420:19)

at UnableToResolveError.buildCodeFrameMessage (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:304:17)

at new UnableToResolveError (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:290:35)

at ModuleResolver.resolveDependency (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:168:15)

at DependencyGraph.resolveDependency (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph.js:353:43)

at /home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/lib/transformHelpers.js:271:42

at Server.<anonymous> (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/Server.js:842:41)

at Generator.next (<anonymous>)

Error: EISDIR: illegal operation on a directory, read
at Object.readSync (fs.js:614:3)

at tryReadSync (fs.js:383:20)

at Object.readFileSync (fs.js:420:19)

at UnableToResolveError.buildCodeFrameMessage (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:304:17)

at new UnableToResolveError (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:290:35)

at ModuleResolver.resolveDependency (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:168:15)

at DependencyGraph.resolveDependency (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph.js:353:43)

at /home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/lib/transformHelpers.js:271:42

at Server.<anonymous> (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/Server.js:842:41)

at Generator.next (<anonymous>)

Browser debugger screen:
[image: Screenshot from 2021-09-19 10-53-45]
https://user-images.githubusercontent.com/7973726/133922784-4395cfad-9282-4683-b43b-0d773124f37f.png
Further investigations done on my own:
I've added the console.log(this.originModulePath); call before this line
https://github.com/facebook/metro/blob/v0.59.0/packages/metro/src/node-haste/DependencyGraph/ModuleResolution.js#L317
in my dependencies. The Expo console output is:
/home/ccarcaci/git/EisdirErrorInvestigation/.
Error: EISDIR: illegal operation on a directory, read
at Object.readSync (fs.js:614:3)

at tryReadSync (fs.js:383:20)

at Object.readFileSync (fs.js:420:19)

at UnableToResolveError.buildCodeFrameMessage (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:305:17)

at new UnableToResolveError (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:290:35)

at ModuleResolver.resolveDependency (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:168:15)

at DependencyGraph.resolveDependency (/home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/node-haste/DependencyGraph.js:353:43)

at /home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/lib/transformHelpers.js:271:42

at /home/ccarcaci/git/EisdirErrorInvestigation/node_modules/metro/src/Server.js:1097:37

at Generator.next (<anonymous>)

It seems that Metro is unable to package correctly the debugger worker .js
files.
I don't know how to proceed to enable debugging.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/32234, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADMOKOWSOGOXOCM727634J3UCWWQ7ANCNFSM5EKE7QZQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Error prozeesing input image information multires pictures for pannellum

Hello,
i do not know what is wrong processing multires picture for pannellum. Last week it worked great. Today i realised that i still have a problem with this following error message.
admins-MBP:~ admin$ python /Volumes/EOS1100D/MultiRes/dll/generate.py -n /Volumes/EOS1100D/MultiRes/dll/nona.exe /Volumes/EOS1100D/MultiRes/input/Roessle_1.jpg -o /Volumes/EOS1100D/MultiRes/output/R
Processing input image information...
Assuming --haov 360.0
Assuming --vaov 180.0
Generating cube faces...
Traceback (most recent call last):
File "/Volumes/EOS1100D/MultiRes/dll/generate.py", line 165, in
subprocess.check_call([args.nona, ('-g' if args.gpu else '-d') , '-o', os.path.join(args.output, 'face'), os.path.join(args.output, 'cubic.pto')])
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 535, in check_call
retcode = call(*popenargs, **kwargs)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 522, in call
return Popen(*popenargs, **kwargs).wait()
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 710, in init
errread, errwrite)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 1335, in _execute_child
raise child_exception
OSError: [Errno 8] Exec format error
Thanks for any help
Mike

You have a broken Python / Nona install, since the OSError indicates that Python is unable to call nona. I also don't understand what you're doing, since you seem to be on a Mac but appear to be trying to use a Windows copy of Nona.

Thank you for your fast response. You are right. It is not the right way to use nona.exe on a Macintosh. I change the path from nona to the local hugin.application. Now the terminalcommand is running well.
Thank you
Mike
Mit freundlichen Grüßen
Mike Fischer

Am 15.02.2019 um 20:09 schrieb Matthew Petroff<EMAIL_ADDRESS>You have a broken Python / Nona install, since the OSError indicates that Python is unable to call nona. I also don't understand what you're doing, since you seem to be on a Mac but appear to be trying to use a Windows copy of Nona.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


I have a question about the training process

I'm sorry to disturb you. if I use your parameters to train the network, directly to train 200 epochs, do I need to adjust them in the process?

When I was using regular batch norm, I trained with the following params:
python3 train.py --max_epoch=200 --smoothing=0.9 --l1_weight=0.99 --base_lr_gen=3e-4 \
--base_lr_disc=6e-5 --lr_decay_steps=6e4 --disc_norm=batch --apply_weight_init=1

and for spectral norm:
python3 train.py --max_epoch=100 --smoothing=1.0 --l1_weight=0.985 --base_lr_gen=2e-4 \
--base_lr_disc=2e-4 --lr_decay_steps=4e4 --disc_norm=spectral --apply_weight_init=0

(in both cases, for the rest of the params, I used the default values from train.py)
I did not change any hyper params during training (other than the learning rate adjustments you can see line 105-108 in train.py), so if you just run the code like this, you should get similar results as I did (at least on CIFAR10).

Thank you very much for your reply.
I saw that the L1 loss parameter(MAE) was compared in that paper 《Image Colorization using Generative Adversarial Networks》, but when i run your code, it seems that i can't reach that goal(0.051). Have you compared with the parameter in the paper ?
(paper: MAE is computed by taking the mean of the absolute error of the generated and source images on a pixel level for each color channel)

Some of the hyper params I used for training were different than to those described in the article. So if you are trying to achieve the same results as the authors, I would check out their repo:
https://github.com/ImagingLab/Colorizing-with-GANs
I remember that I initially tried to reach the same MAE as the article, but it was difficult the reproduce, or to even reach comparable results (in terms of MAE). After a while I let it go. A 7.5 MAE on CIFAR seemed like a totally unrealistic goal.
In general, I would say that MAE is not the best way to evaluate image colorizing. For example, if you increase the weight of the L1 loss in the training, the network will produce more grayish/sepia like images but the MAE loss might decrease.

Thank you very much. And the value accuracy(24.1%,65.5%) ,can you reach that result? I wrote that code, but i can't reach that result.
(Accuracy is measured by the ratio between the number of pixels that have the same color information as the source and the total number of pixels.)

I haven't tried. I ran the training sessions until I stopped seeing improvements in image quality. For the batch norm use case this was around 170-200 epochs and for spectral norm ~ 80-100 epochs.

@787629504
I did some digging and coding. I think there might be a misinterpretation about MAE on either my side or in the article.
In my understanding, the mean absolute error is the same as the L1 loss, so in order to calculate the MAE, I am SUMMING up the ABSOLUTE difference of the real and generated pixel values of the test set (for every pixel on every image on every color channel) and I divide this sum by<PHONE_NUMBER> (num_imagesheightwidthnum_channels).
Using this definition in the standard RGB color space (so the test image and the generated image are both have pixel values from 0-255):

the MAE of my batch norm model is ~123 on the CIFAR10 test set
the MAE of my spectral norm model is ~123 on the CIFAR10 test set
the MAE of the CIFAR10 model in the article's repo is ~133 on the CIFAR10 test set
*using default batch sizes. (there might be some minor differences if we play around with the batch size during testing).

Obviously none of these are anywhere near the 5.1 MAE value stated in the article.
MAE on Wikipedia:
https://en.wikipedia.org/wiki/Mean_absolute_error
When I was working on this repo, I directed a question to the authors of the article since I figured maybe we are using MAE in different color spaces, but it seems like that is not the case:
https://github.com/ImagingLab/Colorizing-with-GANs/issues/13
So anyway, I am a little unsure what to do with all this. Maybe the MAE should be calculated differently in this case. :)

Thank you very much for your reply. I understand a lot through your explanation.
I saw that your code uses TORCH. nn. L1loss (reduction =' mean') to calculate L1 loss , i think it is the same as MAE loss value, but when I run the code, this value is usually around 0.07, There is a difference of 100 times from 13.8. I want to know why is this. Thank you!

Sorry to disturb you. Are you still studying the direction of colorization?  Does the current evaluation standard use PSNR more? I read the two standards MAE and Accuracy in GAN's paper, which seem to have nothing to do with the quality of coloring. do you think that these two standards are important?

First your first question:
Where did you see the 0.07 L1 loss? Is it printed during training? If so, during training the L1 loss is calculated on the training batches. In this phase, the images are in the LAB color space and they are normalized (all the pixel values are between -1 and 1). So the L1 loss here and the L1/MAE loss means something different.
Regarding the second question:
I am not an expert on image colorization. I just studied it for a few weeks to build this repo. I am not sure what loss function or eval method performs the best in the current state-of-the-art, but I think nor MAE nor accuracy are great ways to measure the capabilities of an image colorizing approach. The problem with these loss functions is that they are trying to quantify the difference between the original and the re-colorized image, but getting the exact same image as the original is not necessarily the goal here. I would say, the goal is the create a lifelike image that is "believable" to humans.
Example: the sky is obviously usually blue and the grass is usually green, but the color of a car can be any color basically. When we are using MAE or accuracy, the network is punished for painting a car red if it was originally blue, but that in itself is not necessarily a mistake if the results are believable.

Left to right: original, grayscale(input), and the output of two different color approaches.
I would say that the networks did a good job with the colorizing, but the MAE is probably pretty high because they did not "guess" the original color of the car correctly.

Thank you very much for your reply. I understand a lot through your reply.


Angular services should be loaded first

Some Angular providers may be needed at config state. So the services files must be loaded before the other JS files, especially the config ones.
But the assets.js object in config/env/all.js makes module.exports.getJavaScriptAssets() in config/config.js load all JS assets alphabetically.
This PR fixes this and makes the JS files being loaded in this order :

Angular lib files
App config (public/config.js)
App init  (public/application.js)
Modules declarations  (public/modules/*/*.module.js)
Modules services (public/modules/*/services/*.js)
The remainder...

@herveguetin if you fix the pattern issue, then this PR should be good to go.

@herveguetin @ilanbiala
I think this has been resolved already in the 0.4.0 branch, but not entirely sure....
https://github.com/meanjs/mean/blob/0.4.0/config/assets/default.js#L33
If so, can this be closed?

Agreed


aws bedrock streaming

This PR adds streaming to Bedrock API similar to how it's handled in OpenAI. If no block is passed, the code works exactly the way it used to.
Usage:
Langchain::LLM::AwsBedrock.new.chat(messages:, model:) do |chunk|
  do_something(chunk)
end

@agomezcampero Great job, thank you!


Add package manager to package.json

Should be easier to make sure you use correct version of pnpm now.

What's the procedure to update this? Say I update pnpm and do make install (pnpm install -r), will that automatically update both the lockfile and the version in package.json?

Lockfile will be updated automatically when you install new deps, but version in package.json has to be managed manually

Is there a way to modify make install such that in addition to updating the lockfile, it also updates the packageManager property?
If that's too hard, we could add corepack enable to make setup then change all pnpm commands in the makefile to use corepack pnpm instead?

The scenario I'm thinking of is that right now if I (1) update pnpm, (2) run make install then push, then the version is not correct anymore (mismatch between pnpm-lock.json and packageManager & even someone using corepack will get an error.
Unless pnpm itself checks packageManager & prevents this from happening?

Ok, so I think this is good enough for now. Thinking of it, there is no trivial solution anyway, since the lock file version doesn't update with every version of pnpm. We'll just have to be vigilant to upgrade the statement in the package file every time the lock-file version changes.
I've added warnings to the Makefile and that'll have to do!

I completely missed that this also was setting up Vite. This was not fully integrated in the build flow & needs further review, so I've reverted on master.


Note RBG Setting

When i was messing around with the note RGB setting (which i really like) , i find it hard to manage around with. for example , when i want to use the same color for 2 arrows , its not the same exact color when i set the same numbers for the RGB . My idea of fixing this issue is when selecting such note on the option menu , it should reset the whole note color to gray (as in the receptor gray where it has no color) , then afterwards you can set your prefered color.
 image of the bug

I don't really want to redo the notes for supporting RGB at the moment.

Also making the notes grey would make the colors more stale/bland, i already have a solution for this but it would take a good while and too much work to do it.

3 years later it's added


no titlebar or hide titlebar request

the title-bar is usually used to help in moving/resizing whatever but as most of us have a keybind to do each of those things it becomes useless and as such i would like to ask/recommend as a user of this wm that an option be added to completely deactivate it like idk decoration="null" for example
love jwm keep up the awesome work

Did you try notitle? in group settings, that should do the job.

maybe but can i add everything to that group???? and also wouldn`t it be easier if we could do it it the widow decorations

I think you can use Regex in the tag itself, @joewing should be able to explain that better that me

you are totally right you can do it in the group options you just have to not put the Name tag like so

notitle

you are tottaly right just dont put the name tag and it will assume all of them thanks


⚠ Samsung has degraded performance

In 6420aac, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2390 ms

Resolved: Samsung performance has improved in 22d2cb9.


Every locale has own field in modal

looks like how it should look

Coverage remained the same at 87.5% when pulling 7fec2547f0c0b5a6471d87ba4c674f5fd4c0738e on auto-locale into 67285c8666b977bbd11224ad9e32bd82b6a0464e on master.


Task failing with npm 3.4.0

Been trying for a couple hours to get this working, but I'm having some issues.  I started a fresh project to make sure nothing I had set up before was messing up.
So - I'm on npm 3.4.0, node v4.2.1, Grunt 0.4.5
My Gruntfile:
module.exports = function(grunt) {

  // Project configuration.
  grunt.initConfig({
    pkg: grunt.file.readJSON('package.json'),
    phantomcss: {
      options: {
          screenshots: 'test/visual/screenshots/',
          results: 'results/visual/',
          viewportSize: [1280, 800],
          mismatchTolerance: 0.05,
          rootUrl: 'http://localhost:3000/' // Optional
        },
        src: [
          'test/visual/**/*.js'
        ]
      }

  });

  // Load the plugin that provides the "uglify" task.
  grunt.loadNpmTasks('grunt-phantomcss');

  // Default task(s).
  grunt.registerTask('default', ['phantomcss']);

};

Running grunt phantomcss with this setup gives me this error message: Local Npm module "grunt-phantomcss" not found. Is it installed?
If I change grunt.loadNpmTasks('grunt-phantomcss'); to grunt.loadNpmTasks('@micahgodbolt/grunt-phantomcss');, the task runs, but then outputs this:
Error: Cannot find module 'casper'

  phantomjs://bootstrap.js:289
  phantomjs://bootstrap.js:254 in require
  /sprokets/testing/phantomcss/node_modules/@micahgodbolt/grunt-phantomcss/phantomjs/runner.js:39

I started digging around in the code trying to change phantomCSSPath, phantom.casperPath, etc, to no avail. I was able to get different error messages, all of which were about not being able to find one package or another.
It seems like the original task is looking for packages inside of /node_modules/@micahgodbolt/grunt-phantomcss/node_modules, but this directory simple doesn't exist in my setup. I can see casperjs and phantomcss directly in node_modules, but the grunt task runner isn't able to get to them for some reason. I suspect it has something to do with the scoping, but my lack of npm package development is limiting my ability to diagnose the problem any further.
If some light could be shed on this, that would be awesome!

Hey @danieltott. I had the same issue. The workaround I'm currently using is an npm postinstall script I added to my package (which depends on this one). It jumps in to the directory it's looking for casper in and runs npm install so it will be present.
Here's the excerpt from my package.json which gets the job done:
"scripts": {
    "postinstall": "cd node_modules\\@micahgodbolt\\grunt-phantomcss && npm install && cd node_modules\\phantomcss && npm install"
  },

If you're just using this actual package rather than it being a dependency of something you're working on, then you should only need to run cd node_modules\phantomcss && npm install.
I need to fix this properly and make a PR but it's not priority right now, hopefully this can help you out in the meantime.

hmm...I'll take a look at this soon, see what I can do.

I'm having this issue as well, but the postinstall script doesn't work for me. Going into the grunt-phantomcss directory and manually running npm install doesn't fix it for me either.
Error: Cannot find module 'casper'

    phantomjs://bootstrap.js:289
    phantomjs://bootstrap.js:254 in require
    /Users/zrothauser/vagrant-local/www/test/htdocs/wp-content/themes/test/node_modules/@micahgodbolt/grunt-phantomcss/phantomjs/runner.js:39

I had to downgrade node/npm to get this working again (currently using node 0.12.9).
When running npm install with the older version, I get this deprecation error:
WARN peerDependencies The peer dependency<EMAIL_ADDRESS>included from @micahgodbolt/grunt-phantomcss will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
It looks like the use of peer dependencies may be what causes this problem?

Yup, sadly there was an architectural decision in the original project that assumes node modules are local to this module. It'll either need some major rework, or need to figure out if we can force that casperjs dependency to get loaded INTO the phantomcss module.

Will there be a fix for that?
Still getting stuck with "Error: Cannot find module 'casper'"

Replacing the \\ with / in that postinstall script worked for me. Thanks @callummr

Ah of course, we use Windows at work so the path is written differently @builtbyjay. Glad that helped you!

@rh1811 I'm open to pull requests for sure, but I dont' know when I'm going to get time to make this work for newer versions of Node. The code in question is inherited from the original project, so it'd take quite a bit of time to refactor.

It would seem the quick and dirty thing to do is just add an option to be able to override the default location of Casper and then you can configure it in the gruntfile.
I'll see if I can't put together a pull request to do that.

This should be resolved now.


improve (azure-pipelines): log url on error

Signed-off-by: Enderson Menezes<EMAIL_ADDRESS>Logging URL on Azure Pipelines Scaler Error!
Checklist

[X] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[X] Changelog has been updated

Hi, I'm new to Go and here at Keda we are running a POC within the company and this little addition helped us to better understand our mistake.
Does this change need to change CHANGELOG? Any other nonsense I've done let me know please!

Thanks a ton for your contribution! Only small nit

I'm going to look for more simple errors like that, and it helps me understand the code better.

Thanks a ton for your contribution! Only small nit

I'm going to look for more simple errors like that, and it helps me understand the code better.
Edit: I make error with Signature, i will correct then.

You need to amend the wrong commit, adding other one signed it's not enough.
You can see in the docs how to do it:
https://github.com/kedacore/keda/blob/main/CONTRIBUTING.md#i-didnt-sign-my-commit-now-what

Thanks a ton for your contribution! Only small nit

I'm going to look for more simple errors like that, and it helps me understand the code better.
Edit: I make error with Signature, i will correct then.

You need to amend the wrong commit, adding other one signed it's not enough. You can see in the docs how to do it: https://github.com/kedacore/keda/blob/main/CONTRIBUTING.md#i-didnt-sign-my-commit-now-what

Like that?

Thanks a ton for your contribution! Only small nit

I'm going to look for more simple errors like that, and it helps me understand the code better.
Edit: I make error with Signature, i will correct then.

You need to amend the wrong commit, adding other one signed it's not enough. You can see in the docs how to do it: https://github.com/kedacore/keda/blob/main/CONTRIBUTING.md#i-didnt-sign-my-commit-now-what

Like that?

Yes, exactly like that :)
Thanks a ton!

There is an error yet, could you take a look at it please? 🙏
https://github.com/kedacore/keda/runs/4242581591?check_suite_focus=true

Sorry, i will install pre-commit and take more attention.

Sorry, i will install pre-commit and take more attention.

Don't worry, It happens :)
Personally, I use dev containers in VS Code to avoid installing dependencies in my computer. KEDA supports it and pre-commit is already installed there. I prefer that than installing all dependencies for each project, maybe you'd like it
BTW, thanks for the contribution ❤

Sorry, i will install pre-commit and take more attention.

Don't worry, It happens :)
sorry for this because I didn't see it before: Error messages in golang shouldn't start with capital letters and that's the error that there is now. :(
Apart from this, personally, I use dev containers in VS Code to avoid installing dependencies in my computer. KEDA supports it and pre-commit is already installed there. I prefer that than installing all dependencies for each project, maybe you'd like it
BTW, thanks for the contribution heart

i will read this

I don't understand why the "CI / Static Checks (pull_request) " failed :(

I don't understand why the "CI / Static Checks (pull_request) " failed :(

I think that it was a random fail :(


Samples for secret's client

Working samples for sync and async secrets client

Can one of the admins verify this patch?

make sure the samples run on supported platforms (recover_purge_operations.py would crash on 2.7)

recover_purge_operations.py doesn't currently crash. do you see something specific that would fail?

would be nice to mention soft-delete when errors are raised because it's disabled

Added a specific message to mention soft-delete to be enabled for performing operation.

recover_purge_operations.py doesn't currently crash. do you see something specific that would fail?

It was the import asyncio. That won't fly in typical 2.7 environments.


Can anyone share trained model weights or ckpt. It would be really helpful ,  Thanks.

We provided our checkpoints here.


Cannot add emojis or use boolean props. react-chat-widget 3.1.0

guys i'm trying to add emojis but none of the boolean props doesn't seem to work
<Widget
title="Troll box"
subtitle=""
emojis={true}
showCloseButton={true}
showBadge={false}
handleNewUserMessage={handleNewUserMessage}
/>

am i doing something wrong ?

no errors.. it works for you ?

Yes, it works to me, but ....

I forked package due to an error https://github.com/Wolox/react-chat-widget/issues/269 and I revert commit with bug
Emojis dont work good. When I select emojis then to sender component I get native emojis instead google emojis and a lot emojis don`t work and display as rectangle


Fleet - add caBundle field to add a private CA certificate to a GitRepo

fleet:v0.3.2-rc5 adds support to handle git repositories using custom certificates using the caBundle.
We should add this new field to the gitRepo UI
https://github.com/rancher/fleet/issues/150
http://fleet.rancher.io/gitrepo-add/

Also the insecureSkipTLS flag.

caBundle needs to be base64 encoded.

Rancher version v2.5-head (12/22/2020) bd660e1
I tested this using a private Gitlab instance with self signed certificates. I added the CA with the option Specify additional certificates to be accepted
The certificate is automatically base64 encoded and used properly.
I also used the Accept any certificate (insecure) option. Which also worked with the private Gitlab.
The default is require a valid certificate always like the case of Github repos pulled using https.


Add get_nondiag_weight

Compute non-diagonality weights for square matrices. Related to #90.

thx @qbarthelemy


update version

Stack:

#21
#20
#19
#18 ⬅

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

✓ Commit merged in pull request #21


Application crashes when attempting to broadcast WiFi

Describe the bug
The application crashes when selecting "Start Engine"
Devices

Wifi MAX 802.11g (b/g) WLAN Compact USB Adapter (ZyDAS WL-685Z)
PSP 2000 (Slim)
Monster Hunter Freedom Unite

Versions

What commit has this bug been found on?

47fc19a / Release 1.2

What version of XLink Kai was running?

7.4

To Reproduce
Steps to reproduce the behavior:

Installed Wifi Max driver (via Mediafire link)
Install xlink assistant
Configure assistant
Select "Start Engine"
Observe that the application crashes

Expected behavior
Expected the WiFi network to be hosted successfully
Screenshots

Desktop:

OS/Distro: Windows 11

Log.txt
(obscured the MAC address)
20:58:47:065: Info: D:\xlinkhandheldassistant2\main.cpp:180:Plugin Device created!
20:58:47:066: Error: D:\xlinkhandheldassistant2\Sources\WifiInterfaceWindows.cpp:253:Could not send Scan requestUnknown error
20:58:47:070: Trace: D:\xlinkhandheldassistant2\Sources\MacBlackList.cpp:11:Added: xx:xx:xx:xx:xx:xx to blacklist.

Additional context
Followed this guide: https://www.teamxlink.co.uk/wiki/PlayStation_Portable_XLink_Kai_Setup

Try using a more recent version of npcap, winpcap crashes on xlha


Update glium so that rayon-demo runs on Gnome Wayland

Currently, the nbody demo fails to open in the Gnome 3.38 Wayland session:
rayon-demo]$ cargo run --release -- nbody visualize

[wayland-client error] Attempted to dispatch unknown opcode 0 for wl_shm, aborting.

The problem has already been fixed in glium 0.28.0. After updating the crate version, the demo runs as expected.

Thanks! I updated the CI lockfile as well to get that passing.
bors r+


TypeError: iteration over a 0-d tensor

File "main_dev.py", line 99, in repackage_hidden
return [repackage_hidden(state) for state in h]
File "/Users/admin/anaconda3/lib/python3.7/site-packages/torch/tensor.py", line 381, in iter
raise TypeError('iteration over a 0-d tensor')
TypeError: iteration over a 0-d tensor
Have you met this kind of question before?

Did you print the shape of the h variable? It is a recursive function, so there might be a corner case that needs to be fixed. You get this error when h is an empty tensor.


Module fields not appearing in SilverStripe 5

That issue has already been reported but not properly fixed so reposting.
Both my last installs on SS5 have that issue, none of the SS4 (6 of them) have that error, so it's clearly a SS5 issue.
See how the fields (don't actually) appear

Ok, I wasn't using the dev-master. Maybe would be better to not allow the installation of the release v1 if not compatible with SilverStripe 5. But yeah, closing the ticket technically solved.

@fonsekaean could you create a tagged release to include the SS5 fixes? I also had to dig through the tickets, to find out SS5 will only work on dev-master. Thanks in advance!


Website->Create account, border missing

Description

If a field is highlighted, it loses it's border.
To Reproduce
Highlight a field.
Expected behavior
See the border
Version information
N/A
Additional context
No response

The problem:
input[type="text"]:focus, input[type="password"]:focus, input[type="email"]:focus {
    outline: none;
    border: none;
}

https://github.com/AuroraEditor/auroraeditor.com/blob/main/src/Assets/aurora/styles/Auth/aurora-register.css#L226-L229

Wrong Repo, please add it to the website repo.

Website repo has no issues tab.


Tc dev 2021 1

Devicetree changes for axi_intc settings and some other cleanup.

Approved, with fix for axi_intc device-tree definition ( b2e7f6b )
Verified with vitis build of dpu design for u96v2-sbc-base platform.


Do not fail fatal if OS is unsupported.

Affected Puppet, Ruby, OS and module versions/distributions

Puppet: 6.0.2
Ruby:
Distribution: Ubuntu 18.04
Module version: 7.3.0

How to reproduce (e.g Puppet code you use)
What are you seeing

Evaluation Error: Error while evaluating a Function Call, unsupported OS Ubuntu 18.04

What behaviour did you expect instead

Just working

Output log
Any additional information you'd like to impart
The module works totally fine under Ubuntu 18.04. I had no issues but I also do not test some edge cases.
Anyway please do not fail if the version is unsupported. I can understand if you auto config may not work for unsupported version but let the user the chance to configure the module manually.

hey Jan, can you provide a PR for this?


Natural sorting of samples

Samples are a bit messy

done in https://github.com/melonora/napari-cell-gater/pull/17/commits/17cb18371b3ae5d5411387f54d0d1a5e2f183f10


update homebrew formula to newest microk8s version (1.28) - otherwise Mac Users can't use it.

Summary
The latest present formula on homebrew as of October 2023 point to ubuntu version 22.04 and microk8s version 1.27. This makes it near to impossible for mac users to use it.
Why is this important?
Lot has changed since that time. The instructions do not work in the present day, leading to newbies like myself wasting precious time, assuming the fault is theirs :)
Are you interested in contributing to this feature?
yep definitely.

Thank you for this work @AjayKumar4 we will re view it ASAP


added volume backup script and scripts directory

Thanks for the PR.  @Nitrousoxide would you mind squashing your commits down a single one, and signing it with -s?

Well that was an ordeal getting the squash and gpg working.  Let me know if you need anything else

Oh I'm so sorry I wasn't clear, a GPG signature is nice to have, but I was only asking for the Signed-off-by: Brian<EMAIL_ADDRESS>at the bottom of the commit message (git commit -s ... (small s vs big S).  This is what's causing the "DCO" check to fail - There's still a commit w/o a signature line (41464e9).
Try a git rebase -i upstream/main (or origin/main), then in the list, on the last line only, change pick to squash.  Exit the editor.  That should drop you into another editor where you can fixup the commit message.  Exit that and the rebase will finish.  Lastly, a git commit --amend -s (small s) will add a DCO signature line to the commit.
Hope that helps.  Don't feel bad, we were all new to git at some point :smile:

There you go, now it's passing the DCO check.  When you rebase-squashed, you're suppose to hand-edit the two commit messages into a single message.  Git is a fantastic tool, but it's terrible at mind-reading and even worse at fixing English :laughing:  I feel bad asking for yet another change...let me see if I can help consolidate the message a bit...

okay I edited the commit message down to a one-liner.  Sorry about this whole pull process.  I generally don't contribute to projects so it doesn't matter how sloppy I am with git in a personal repo.

@rhatdan a bit of context:  I was chatting with @Nitrousoxide and thought this was a cool first contribution.  I wasn't 100% on where it could go, with this repo. seeming the best fit.  I'm aware more changes are likely needed (a README.md, CI tests, etc.).  But for a new contributor and as a first addition to this repo., it seemed an acceptable starting point.    I spoke with the team about it, and they all agreed it's up to you if this could be inline with the direction you want to take this repo. or not.

LGTM


Compel influencing lora_scale when using LoRA in Diffusers

Describe the bug
When using compel and prompt embeddings, and performing inference with LoRA weights loaded, lora_scale doesn't work as expected. Specifically, if I do the following actions in the following order:

Create a SD pipeline
Load a model
Load a LoRA
Generate an image with lora_scale = 1
Generate an image with lora_scale = 0
Generate an image with lora_scale = 1
Generate an image with lora_scale = 1

The image generated in Step 6. is different from the image generated in Step 4. All the following images, if  lora_scale is not changed again, remain consistent. Basically what happens is that somehow it takes one generation to get back on track and remain consistent. See plot attached:

We can see that Image 3 is different from Image 1, and from Image 4 on, as long as lora_scale don't change, it remains consistent.
This doesn't happen when not using compel and prompt embeddings:

Reproduction
I prepared a colab that shows the issue, accessible here: https://colab.research.google.com/drive/1ciFZPcvMsNZiZOpfHtLih5V6OyRh8Z6d?usp=sharing
System Info
diffusers[torch]==0.18.1
transformers==4.30.2
compel==1.2.1

strange.
what i'm imagining is that the prompt= kwargs to the pipeline involve some kind of cleanup/init that you don't benefit from when passing prompt_embeds.
what happens if you take compel out of the equation completely, and generate the embeds by hand? i.e. push the prompt through pipe.tokenizer then take the output of that and push it through pipe.text_encoder, and then pass that as prompt_embeds?

The lora scale value is provided at image generation time which isn't going to work for custom prompt embeds.  Your image 2 with Compel is also wrong (still having text encoder weights scaled to 1.0 from the previous generation).
Adding this line before using Compel fixes the issue:
pipeline._lora_scale = lora_scale

@pietrobolcato is this still an issue?

which isn't going to work for custom prompt embeds

if load multi lora like,
self.pipe.load_lora_weights(adapter_id_pixel, adapter_name="pixel")
self.pipe.load_lora_weights(adapter_id_chalkboardbrawing, adapter_name="chalkboardbrawing")
self.pipe.set_adapters(["pixel", "chalkboardbrawing"], adapter_weights=[1.0, 1.0])
and then, do generate the image,
sdout_image = self.pipe(prompt_embeds=prompt_embeds,
pooled_prompt_embeds=pooled_prompt_embeds,
negative_prompt_embeds=negative_prompt_embeds,
negative_pooled_prompt_embeds=negative_pooled_prompt_embeds,
num_inference_steps=num_inference_steps,
num_images_per_prompt=num_images_per_prompt,
generator=generator,
height=height,
width=width,
guidance_scale=guidance_scale,
controlnet_conditioning_scale=controlnet_conditioning_scale,
#controlnet_kwargs={"image": can_image},
cross_attention_kwargs={"scale": lora_scale},
control_guidance_start=control_guidance_start,
control_guidance_end=control_guidance_end,
clip_skip=2,
image=can_image,
).images[0]
how to deal with it ?
because there is multi lora

@damian0815 @pdoane
and ,one more question. The lora tagger's words in prompt and negative prompt's text-inversion embedding with tagger's word, how do the "Comple" affect these trigger words？And, i do some comparative experiment between the "stable diffusion webui" and the "diffusers inference", but the result is very bad in "diffusers inference" and the  "stable diffusion webui"  is normal and good .
thanks.
looking forward to reply.

@damian0815 @pdoane
and ,one more question. The lora tagger's words in prompt and negative prompt's text-inversion embedding with tagger's word, how do the "Comple" affect these trigger words？And, i do some comparative experiment between the "stable diffusion webui" and the "diffusers inference", but the result is very bad in "diffusers inference" and the "stable diffusion webui" is normal and good .
thanks. looking forward to reply.

yes, i've found same issue
and i think this is not fully related to compel
without compel, the quality still degraded compare to sd-webui

same problem.

@damian0815 @pdoane
and ,one more question. The lora tagger's words in prompt and negative prompt's text-inversion embedding with tagger's word, how do the "Comple" affect these trigger words？And, i do some comparative experiment between the "stable diffusion webui" and the "diffusers inference", but the result is very bad in "diffusers inference" and the "stable diffusion webui" is normal and good .
thanks. looking forward to reply.

yes, i've found same issue and i think this is not fully related to compel without compel, the quality still degraded compare to sd-webui
same promble.
yes, the diffuser's result is not good or better than the a111-webui.

Sure, diffusers is degraded compared to others, but every time I've tried it with a lora, compel seems to be heavily degraded vs diffusers with no compel.


mailchimp-api Batch execute returning null - timeout?

I am using your mailchimp-api package in my application and I am utilise a large sync process which takes 56,000 user records from my database, batches it and sends it through to Mailchimp.
My code:
$batch = $this->mailchimp->new_batch();
foreach ($subscribedUsers as $subscribedUser) { // 56k array
     $batch->put('batch'.$subscribedUser->getId(), $endpoint, [
         'email_address' => $email,
         'status_if_new' => 'subscribed',
         'merge_fields' => $mergeFields,
     ]);
}
$result = $batch->execute(); // this returned null
$batch = $this->mailchimp->new_batch($result['id']); // the script fell over here
$batch->check_status();

Here is some output from my script which shows that it took 522 seconds (8 mins) from creating the batch to queueing up the batch with 56785 records to executing it.

Created Mailchimp batch : timeSeconds=0.00026
Batched all Mailchimp users : timeSeconds=522.63815
Sent Mailchimp batch : timeSeconds=10.17836
Synced all Mailchimp user records : noOfPersons=56785 : executionTime=538.97

The batch appears to have made it through to Mailchimp as over the course of the next hour after running the script my mailing list was gradually updated every minute to reflect the changes I sent through.
What I am trying to understand is why did the call to execute return null when it should return an array which includes the all important batch id.
I notice there is a $timeout parameter to the  execute method - would increasing this to something high, say 1000 seconds, solve this issue?

You don't need this line $batch = $this->mailchimp->new_batch($result['id']); // the script fell over here if you're checking on the status of the batch previously posted. See this which shows the previously-set batch_id property being used. Oddly enough, however, $batch->execute() should be returning something... I would wonder if this is more of a cURL issue...

The call to new_batch isn't the problem here, it's the fact that execute returns null when it shouldn't. I've boosted the timeout parameter, but i'd like to know if that is likely to fix it in future runs.

That's still a very big batch. Does a smaller batch work? It does sound like you're hitting into configured or available resource limits.

Yes, smaller batches work with no error and execute returns as expected. Where would the configured/available resource limits be? In the PHP app? cURL? In the Mailchimp bundle?

Yes, could be any of those. This library only implements a cURL timeout option, which is configurable. Other than that, you could be hitting script timeout limits, memory limits, anything. That's not easy for someone without access to your server to investigate.

@crmpicco as @drewm said you need to break up your batches into smaller ones.
Anything over 5000 operations might fail. That came straight from MailChimp. I tried to batch over 10k operations and received the null back.
At the end my foreach, I broke it down into small batches like this:
if( $counter === 500 ) { 	$counter = 0; 	$result = $batch->execute(); 	$batch = $this->mailchimp->new_batch(); } $counter++;
$result now contains the correct response data.

I have the same problem - curl calls returns null (at method makeRequest in Mailchimp class, $responseContent = curl_exec($ch); $responseContent is empty) - even if i split the batch op to contain only 400 ops per batch. And every batch is executed when previus is finished. That may occur not only in batch ops but to any curl call to mailchimp api.
I have asked the same question in [https://stackoverflow.com/questions/62784896/mailchimp-api-problem-with-dropped-curl-calls]  where is explained the situation.
I cannot find any reason why that happens.
foreach($accounts as $idx => $email) {                          $members[] = $email;                             if($idx > 0 && (($idx % 400) == 0 || count($accounts) - 1 == $idx)){                                 if( ($status = $this->_addMembersInAList($listID, $members)) === 1) {                                     $transfered += count($members);                                     $this->updateProcessStatus($pid);                                     $members = [];                                 }else{                                     return $this->updateProcessStatus($pid, $api->getLastError(), true);                                 }                             }                         }
where _addMemebersInAList is
$batch = $api->new_batch();             foreach($members as $idx => $email){                 $batch->post("m".$idx, "lists/$listID/members", [                     'email_address' => $email,                     'status'        => 'subscribed',                 ]);             }             $batch_status = $batch->execute(3000);             if($batch_status === false){                 return 0;             }             while(1){                 $status = $batch->check_status();                 if(isset($status["status"]) && !empty($status["status"])){                     if($status["status"] === "finished"){                         return 1;                     }else{                         sleep(1);                     }                 }else{                     return 0;                 }             }
It does not hit script timeout, memory limits or anything else..
One day may some calls returning null and the next day may run smooth, until i try to create a campaign with several emails (more than 20K for example).
Any thoughts? I have stuck here


Could not determine java version from '9.0.1'.

Has anyone come across this issue? If so, let me know the solution.
I get the error when running 'react-native run-android'.
Thank you in advance.

so please close this issue


Unable to use parameters within procedures

The following query creates a node Foo within a procedure.
CALL apoc.do.when(true, 'CREATE (foo:Foo {Id: 12345}) RETURN foo', '', {})
YIELD value
WITH value.foo AS foo
RETURN foo

While it is possible to create this cypher with Neo4jClient, it is not possible to do so with parameters.

Case 1: No parameters, works and produces the expected query

var result1 = await graph.Cypher
    .Call(@"apoc.do.when(true, 'CREATE (foo:Foo {Id: 12345}) RETURN foo', '', {})")
    .Yield("value")
    .With("value.foo AS foo")
    .Return<string>("foo")
    .ResultsAsync;

Case 2: Produces exactly the same valid query as case 1, but fails to deserilize the result

var result2 = await graph.Cypher
    .Call(@"apoc.do.when(true, 'CREATE (foo:Foo {Id: $Id}) RETURN foo', '', {})")
    .Yield("value")
    .With("value.foo AS foo")
    .WithParam("Id", 12345)
    .Return<string>("foo")
    .ResultsAsync;

Case 3: Doesn't work at all because of quoted property names in the parameter (same problem as #316?)

var result3 = await graph.Cypher
    .Call(@"apoc.do.when(true, 'CREATE (foo:Foo $newFoo) RETURN foo', '', {})")
    .Yield("value")
    .With("value.foo AS foo")
    .WithParam("newFoo", new {Id = 12345})
    .Return<string>("foo")
    .ResultsAsync;

This is the exception produced by case 2:
System.ArgumentException: Neo4j returned a valid response, however Neo4jClient was unable to deserialize into the object structure you supplied.

First, try and review the exception below to work out what broke.

If it's not obvious, you can ask for help at http://stackoverflow.com/questions/tagged/neo4jclient

Include the full text of this exception, including this message, the stack trace, and all of the inner exception details.

Include the full type definition of System.String.

Include this raw JSON, with any sensitive values replaced with non-sensitive equivalents:

 (Parameter 'content')
 ---> System.ArgumentNullException: Value cannot be null. (Parameter 'input')
   at System.Text.RegularExpressions.ThrowHelper.ThrowArgumentNullException(ExceptionArgument arg)
   at System.Text.RegularExpressions.Regex.Replace(String input, String replacement)
   at Neo4jClient.Serialization.CommonDeserializerMethods.ReplaceAllDateInstancesWithNeoDates(String content)
   at Neo4jClient.Serialization.CypherJsonDeserializer`1.Deserialize(String content, Boolean isHttp)
   --- End of inner exception stack trace ---
   at Neo4jClient.Serialization.CypherJsonDeserializer`1.Deserialize(String content, Boolean isHttp)
   at Neo4jClient.GraphClient.Neo4jClient.IRawGraphClient.ExecuteGetCypherResultsAsync[TResult](CypherQuery query)
   at ...

Can you try running the following?
var result2 = await graph.Cypher
    .Call(@"apoc.do.when(true, 'CREATE (foo:Foo {Id: $Id}) RETURN foo', '', {Id:Id})")
    .Yield("value")
    .With("value.foo AS foo")
    .WithParam("Id", 12345)
    .Return<string>("foo")
    .ResultsAsync;

Thanks for the speedy response! Unfortunately that produces invalid cypher.
CALL apoc.do.when(true, 'CREATE (foo:Foo {Id: 12345}) RETURN foo', '', {Id:Id})
YIELD value
WITH value.foo AS foo
RETURN foo

Variable `Id` not defined (line 1, column 76 (offset: 75))
"CALL apoc.do.when(true, 'CREATE (foo:Foo {Id: 12345}) RETURN foo', '', {Id:Id})"
                                                                            ^

Sorry - might need to be:
var result2 = await graph.Cypher
    .Call(@"apoc.do.when(true, 'CREATE (foo:Foo {Id: Id}) RETURN foo', '', {Id:$Id})")
    .Yield("value")
    .With("value.foo AS foo")
    .WithParam("Id", 12345)
    .Return<string>("foo")
    .ResultsAsync;

That works, thanks! The query becomes quite verbose, but it gets the job done.

This is the way apoc works - you have to pass in the parameters to the method, it's the reason you have the {} in the call, and is the same for any of them (take periodic.commit etc) - if you were writing in Cypher directly, and 'faked' the parameter bit a bit by doing:
WITH 'abc' AS Id

You'd have to do the same thing:
CALL apoc.do.when(true, 'CREATE (foo:Foo {Id: Id}) RETURN foo', '', {Id: Id})
//ETC

It's always worth trying out in a similar way to ^ to see what you need to do.
Your third example is the same deal, you need to pass you parameters into the apoc call so that it can use them.

That makes sense. In my actual code I am passing values from the "outer query" into the apoc method, so it makes sense that "outer parameters" need to be passed in also. Part of what was throwing me was that case 1 and 2 above result in the same cypher (when checking Query.DebugQueryText) so it wasn't immediately obvious I was trying to do something invalid.
Thanks again for the help, really appreciate it!


STM32F730 Memory descriptor fails

When connecting to an STM32F730, the usbDevice gives a descriptor string of:
"@Internal Flash  /0x08000000/04016Kg,0164Kg,03*128Kg\0"
for the Memory description.
In the STM device itself, the descriptor string includes a single trailing '\0' character within the length of the string, and this is interpreted by the usbDevice as a trailing "\0" (2 characters) on the end of the string, as seen above.
This then fails the SeMemoryLayoutRegex and aborts the process.
Editing the string to remove the "\0" in debug 'fixes' the problem.
So, this appears to be a failure to handle unexpected descriptor string contents as parsed by LibUsbDotNet.
I don't know if there are options for IUsbInterface to parse this differently (and just truncate the string at the zero) or if it could be stripped off in LibUsbDfu.
(Strictly speaking, the actual zero in the descriptor itself shouldn't really be there, but it is.)

Well this really is a bug of the STM32 ROM bootloader implementation. That being said, it's not really possible to do anything about it where it's broken, we have to find a sensible workaround that doesn't produce other side effects. I think this fix is suitable.

Thanks for looking at this, but that solution does not fix the problem.
The trailing zero chars in the descriptor are being read by UsbLibDotNet and translated into the two characters '','0' (i.e. a string "\0") not the single character '\0'.
My solution:
I added the characters "(?:\0)*" just before the last '$' in the regex SeMemoryLayoutRegex.
This causes the regex to ignore any trailing "\0" at the end of the line.  Just to confuse things, that \0 in the regex should actually be \0 and it is interpreted as such.  It required \0 when testing externally.
It is only the SeMemoryLayoutRegex.Match(dfuSeFormat) which fails - the rest of the parsing works fine whether those trailing characters are there or not.

Are you sure that this character translation only happens in LibUsbDotNet, i.e. not done by the OS driver for example? Could you give me a screenshot of the device in usbview.exe? And maybe also dump the ROM code with a utility? (If the ROM area isn't directly accessible by a debugger, you could copy it to RAM with a simple firmware, and then dump that RAM area.)

I don't know where the character translation happens, so it could be in the driver.  The driver is an STM driver 1.1.0 07/05/2018.
USBView actually stalls on that string, and doesn't render anything after it, as seen here:

Here also is the raw descriptor in the STM32 RAM as viewed while debugging (the ROM image doesn't appear to contain the raw descriptor strings):

I also highlighted the OTP Memory string as it is even worse, with 10 trailing null characters, but they are definitely just null characters at this point.
Finally, here is the resulting string in DeviceProgramming, at the point where it is causing the problem:

The strings are the same in the LibUsbDotNet object, so it is not caused by anything that happens in DeviceProgramming itself.

I checked what LibUsbDotNet is actually doing, it's only calling Encoding.ASCII.GetString() on the received buffer. I've set up a simple test to replicate the events, and test the fix:
static bool TrailingTest()
{
    int trailingzeroes = 1;

    // start with valid string
    string good = "@Internal Flash /0x08000000/04*016Kg,01*64Kg,03*128Kg";

    // simulate issue: put into bytes, append zeroes
    byte[] buffer = Encoding.ASCII.GetBytes(good);
    Array.Resize<byte>(ref buffer, buffer.Length + trailingzeroes);

    // encode it back
    string bad = Encoding.ASCII.GetString(buffer, 0, buffer.Length);

    // perform countermeasure
    string fix = bad.TrimEnd(new char[] { '\0' });

    // check regex
    var result = SeMemoryLayoutRegex.Match(fix);
    Console.WriteLine(result.Success ? "Success" : "Fail");
    return result.Success;
}

This test passes for me, so the same should also work for you with 664e661.
What you stated above

The trailing zero chars in the descriptor are being read by UsbLibDotNet and translated into the two characters '','0' (i.e. a string "\0") not the single character '\0'.

is not the case, it is only the Visual Studio debugger showing you that way. Also if you add "(?:\0)*" to the regex that only matches the 0x00 bytes, not the "\0" string, for that you'd need to escape the backslash character separately.


[Vue Router warn]: No match found for location with path "blank"

Whenever I run any unit test with a file with *.nuxt.spec.* in the name I get the following errors:
[Vue Router warn]: No match found for location with path "blank"
[Vue Router warn]: No match found for location with path "blank"
[Vue Router warn]: No match found for location with path "blank"
[Vue Router warn]: No match found for location with path "/blank"

I've tried mocking the router and also creating a new router but nothing seems to help.
ModalShell.nuxt.spec.ts
import { describe, it, beforeEach, expect } from 'vitest'
import { VueWrapper } from '@vue/test-utils'
import { mountWrapper } from '@/tests/testUtils'
import ModalShell from<EMAIL_ADDRESS>
describe('Invite Members Modal', () => {
  let wrapper: VueWrapper

  beforeEach(() => {
    wrapper = mountWrapper({
      component: ModalShell,
    })
  })

  it('matches snapshot', () => {
    expect(wrapper.html()).toMatchSnapshot()
  })
})

testUtils.ts
import { shallowMount, RouterLinkStub } from '@vue/test-utils'
import { createTestingPinia } from '@pinia/testing'
import { createI18n } from 'vue-i18n'
import messages from '@/lang/messages'

interface MountConfig {
  component?: object
  initialState?: object
  props?: object
}

export function mountWrapper({ component, initialState, props }: MountConfig) {
  const i18n = createI18n({
    legacy: false,
    globalInjection: true,
    locale: 'en',
    messages,
  })

  return shallowMount(component as object, {
    global: {
      plugins: [
        createTestingPinia({
          initialState,
        }),
        i18n,
      ],
      stubs: {
        NuxtLink: RouterLinkStub,
      },
    },
    props,
  })
}

export { createTestingPinia }

Any help is appreciated. Thanks

Getting the same error

I'm using pure vue3 setup and getting the same error, even when importing the actual router in my tests.

Any ideas?

The only workaround/hack I found was to create a page named blank.vue. Obviously that's not ideal but it stops the warnings at least.

Thanks @ivan-barragan - I believe we shouldn't have to add a blank page, so I am wondering if there is something else we can do or is this something being figured out in the next release. cc @danielroe

I have a same problem :(

Also having this issue

Still present, even with version 0.7.0 of the module in a vanilla Nuxt 3.4.2 environment with @vue/test-utils 2.3.2 and vitest 0.30.1 installed.

was anyone able to create a minimal reproduction for this?

https://github.com/ouuan/nuxt-vitest-76-reproduction

navigateTo with a nested route also navigate to /blank
https://stackblitz.com/edit/nuxt-vitest-fv5tbr?file=test%2Fapp.nuxt.spec.ts,pages%2Fsubfolder%2F[slug].vue

I think the module is dependent on the [...slug].vue page in the testing repo to work, adding this to my repository fixed it

@bmoret while this may be a solution in your case technically that's a catchall route all which is most likely not want one wants to use as a workaround

Oh i definitely agree, I meant that it got rid of the error message!
Op do 22 jun. 2023 10:50 schreef Lasse Diercks @.***>:

@bmoret https://github.com/bmoret while this may be a solution in your
case technically that's a catchall route all which is most likely not want
one wants to use as a workaround
—
Reply to this email directly, view it on GitHub
https://github.com/danielroe/nuxt-vitest/issues/76#issuecomment-1602258756,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOPNWSFLMYXLWI37XRHIZW3XMQBOFANCNFSM6AAAAAAVK7T77E
.
You are receiving this because you were mentioned.Message ID:
@.***>

yeah I checked that after re-reeading and felt my comment was not adequate anymore thus removed it

navigateTo with a nested route also navigate to /blank
https://stackblitz.com/edit/nuxt-vitest-fv5tbr?file=test%2Fapp.nuxt.spec.ts,pages%2Fsubfolder%2F[slug].vue

Been trying to work with this example. Issue has morphed a bit since v0.8.6. The blank path seemed to be coming from happy-dom and this change has now made the navigation to go to / first. Example with latest version: https://stackblitz.com/edit/nuxt-vitest-mtv3z5

yes, let's track this as a separate issue.


Add configuration file example to README

Small doc improvement
@masongup-mdsol

I discussed this with Jordi already, but just to document it here:
The README update content looks good, but I'd like to see it be done in the doc comments in src/lib.rs. This will ensure that it will be present in the Rustdocs too. The README should be regenerated with this helper crate.
Also, I presume the timeouts are a standard thing for the current mauth client config, but they aren't currently used in this crate.

This change is included in my new PR


[APM] Aggregate Client-Side Stats sketches

What does this PR do?
Context/Jira card: https://datadoghq.atlassian.net/browse/APMSP-1242
This is a refactor that adds ddsketch aggregations on the existing client-side stats aggregator. Until now, we were only performing aggregations on counts, while forwarding the distributions (ddsketches) in their original payloads.
Through this PR, distributions are also decoded/merged into the combined aggregated payload.
The main changes are:

Simplify the aggregation logic (not buffering the 1st payload)
Aggregate toplevel hits (count)
Decode and aggregate OK and ERROR distributions (ddsketch)

Most if not all tests are failing for now, which will be addressed on a separate commit.
Motivation
https://datadoghq.atlassian.net/browse/APMSP-1242

Additional Notes
ClientStatsBucket.AgentTimeShift and ClientStatsPayload.AgentAggregation are no longer needed, since aggregated payloads are now fully aggregated buckets. Adding apm-astra team to the reviewers to ensure this is OK with the backend pipeline.

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes
N/A

LGTM but I don't have membership in opentelemetry on GitHub yet; I've forwarded it to our private Slack channel

/merge


Add Accessible Poverty Estimates

Insert URLs to the project here: https://github.com/aiddata/accessible-poverty-estimates

[x] The projects is active, documented, open source licensed, shows usage from external parties and is directly targeting environmental sustainability. Find more details in the Contribution Guide.

All issues labeled as Good First Issue of the project listed on OpenSustain.tech will be visible on ClimateTriage.com. This is a great way to welcome new community members to your project.
All projects listed will be posted on our Mastodon channel

@sgoodm @jacobwhall