matrixBlend does not set defaultValue

If the default value is not set for the attributes matrix blend creates the rig will break when you reset the controls.

Sorry, I am don understand. Can you elaborate a little more on the explanation? Thanks

add defaultValue when creating matrix blend #76.
When creating this matrixblend. The default  value is not set and when resetting all controls the value will be 0 and the constrain is not working.


Create gitter.im room

https://gitter.im is free for public projects. It is a great way to collaborate and enable the community to solve problems together. It is also growing in popularity among open source projects.

Thanks, done! https://gitter.im/platformio/platformio


Fix Checkstyle warnings

Another round of fixing Checkstyle warnings. In general:

Remove star imports;
Enforce immutability of local variables;
Enforce the maximum line length of 128 symbols.

The build on Travis is really flaky, but it completes successfully on my machine. Let see how it will going.

Looks good to me. I see that lambdas and streams are starting to pop up :sunglasses:


AttributeError on beet import -L

$ beet import -L long beach                                                                            ✔
Traceback (most recent call last):
  File "/usr/bin/beet", line 33, in <module>
    sys.exit(load_entry_point('beets', 'console_scripts', 'beet')())
  File "/home/jojo/git/beets/beets/ui/__init__.py", line 1285, in main
    _raw_main(args)
  File "/home/jojo/git/beets/beets/ui/__init__.py", line 1272, in _raw_main
    subcommand.func(lib, suboptions, subargs)
  File "/home/jojo/git/beets/beets/ui/commands.py", line 973, in import_func
    import_files(lib, paths, query)
  File "/home/jojo/git/beets/beets/ui/commands.py", line 946, in import_files
    plugins.send('import', lib=lib, paths=paths)
  File "/home/jojo/git/beets/beets/plugins.py", line 488, in send
    result = handler(**arguments)
  File "/home/jojo/git/beets/beets/plugins.py", line 145, in wrapper
    return func(*args, **kwargs)
  File "/home/jojo/git/whatlastgenre/plugin/beets/beetsplug/wlg.py", line 71, in setdown
    self.wlg.cache.save()
AttributeError: 'NoneType' object has no attribute 'cache'

Any ideas how to fix this? I would look into it if you could give me some startingpoints @YetAnotherNerd . Thanks in advance!
REgular calling of wlg works:
$ beet wlg long beach                                                                                1 ✘

Time elapsed: 0:00:00.004315 (0:00:00.004315 per directory)

$

@YetAnotherNerd It happens for example when --incremental is used and a folder was skipped. It seems wlg tries to do something even when there is nothing to do - non-technically speaking.
Also the error happens when no match is found when importing.
Since you know your codebase well - before I dig in - any hints where to start looking?
Thanks in advance!

Hi @YetAnotherNerd I fixed this in my clone of wlg and have it in use for months without a problem. Would you accept a PR?

@JOJ0 Sorry to revive this, but I didn't see a PR for this fix you mention. Could you share your edits? I am running into this issue too.

@Wolframme only if you open that PR for me then? too many projects... 😄

@JOJ0 Then we're at a dead end if you don't have your work in your own fork to make a PR from.


gmake: *** [Makefile:146: all] Error 2 Failed   <<< diff_drive_controller [11.9s, exited with code 2]

In Option B – Local Installation
# Build
colcon build --merge-install --symlink-install --cmake-args "-DCMAKE_BUILD_TYPE=Release"

In ubuntu 22.04 + ros2 humble

Option B – Local Installation
Build
colcon build --merge-install --symlink-install --cmake-args "-DCMAKE_BUILD_TYPE=Release"

Hello @xjtu19,
The error shown above is from the ros2_controllers package used as a dependency in this project. As indicated in README, this project is based on ROS Galactic. Therefore, it is not expected to be functional with Humble, and there is no plan to support this project and its dependencies beyond Galactic.
If you want to try this project, I would suggest starting with the prebuilt Docker image. That is by far the simplest and most reproducible approach.


Android

I know this is not quite part of this project bus is there any known web application or android app?

Not yet, but I'm hoping to add one eventually.

Getting things on/off my phone is a total pain right now.  magic-wormhole on my phone would be absolutely ideal.

Getting things on/off my phone is a total pain right now. magic-wormhole on my phone would be absolutely ideal.

Have you looked at syncthing by any chance?

I tried building magic-wormhole in (the awesome) Termux, but right now it won't work because of the cryptography - OpenSSL relationship
https://github.com/termux/termux-packages/issues/2847#issuecomment-421893169

I tried too building magic-wormhole on android, but using Entware - depend on libffi-dev

Not yet, but I'm hoping to add one eventually.

Are there some news about android version?

Use https://kivy.org/#home to port?

I tried building magic-wormhole in (the awesome) Termux, but right now it won't work because of the cryptography - OpenSSL relationship
termux/termux-packages#2847 (comment)

That's now fixed. It works :tada:
Termux commands are something like:
pkg install clang python-dev libffi-dev openssl-dev make python
pip install magic-wormhole
(pynacl takes ages to build).
Thanks @warner for the project :smile:

To avoid recompiling on device, it can be submitted here https://github.com/termux/termux-packages/tree/master/packages
Does it support sending file from another app?

Does it support sending file from another app?

I don't think so, it's not an Android app.
Termux:API has various commands that could be used to script something together - chiefly termux-file-editor (https://github.com/termux/termux-app/issues/150).

I managed to install magic-wormhole as follows:
$ pkg install clang python-dev libffi-dev openssl-dev libsodium-dev
$ SODIUM_INSTALL=system pip install pynacl
$ pip install magic-wormhole

There is a bug for adding magic-wormhole into termux here -
https://github.com/termux/termux-packages/issues/1327

I managed to cobble together an Android client using Kivy:
https://github.com/pavelsof/mobile-wormhole
It is ugly, it is slow to start, and for an app this small it has quite a few rough edges. But it already works for sending and receiving files; and I hope I will (slowly) continue working on it as Kivy turned out to be less painful than expected. Of course, pull requests are welcome (:

https://gist.github.com/lukestanley/d0daa98c86168971476f7d78ee840beb

I managed to cobble together an Android client using Kivy:
https://github.com/pavelsof/mobile-wormhole
It is ugly, it is slow to start, and for an app this small it has quite a few rough edges. But it already works for sending and receiving files; and I hope I will (slowly) continue working on it as Kivy turned out to be less painful than expected. Of course, pull requests are welcome (:

Great start! I gave it a shot and it seems to do what it says on the tin.

Just an FYI for folks looking for android options. I recently built a Magic Wormhole android app in Go: https://github.com/psanford/wormhole-william-mobile
Once Google gets around to approving it, it will show up in the Play Store as 'Wormhole William'.


Oozie sharelib directory changed between hdp2.0 to hdp2.2 and is cryptic

On hdp2.0, the oozie sharelib directory on hdfs was /user/oozie/share/lib. In the hdp2.2 installation, that changed to /user/oozie/share/lib/lib_ (eg: /user/oozie/share/lib/lib_20150605140532). This change of path could possibly break existing users after upgrading to hdp2.2.

After some analysis, found that the code that initiates oozie sharelib setup was change under commits 073ab64. It now calls oozie-setup.sh sharelib upgrade which internally calls OozieSharelibCLI.java. And for whatever reason, that class creates a new directory lib_ in hdfs:///user/oozie/share/lib instead of just copying over the libs in  hdfs:///user/oozie/share/lib.

So the changes may not have been caused by hdp2.0->hdp2.2, but the chef-bach code change which was changed to use the upgrade option. The libraries in the lib_ directory could still work, but it would be good to have consistency in oozie sharelib paths.

Also, the temp file created during share lib setup on hdfs isn't cleaned up correctly. This could skip sharelib upgrade in the next chef-client run.

For some more background on Oozie shared-libs:

Step 4 of the Hortonworks 2.1 to 2.2 upgrade guide
Oozie Initial Shared-Lib Rationale
Oozie Upgradeable Shared-Lib

Clearly this recipe needs some clean-up!

In Upgrade, after running the sharelib creation again, Oozie will automatically pick up the sharelib dir with the latest timestamp as the new sharelib dir.
One can confirm by checking the oozie.log. (/var/log/oozie/oozie.log)
Snippet from a sandbox.

2015-07-06 21:10:37,269 INFO ShareLibService:543 - SERVER[sandbox.com] USER[-] GROUP[-] Share lib for oozie:[hdfs://sandbox.com:8020/user/oozie/share/lib/lib_20141216191026/oozie/json-simple-1.1.jar, hdfs://sandbox.com:8020/user/oozie/share/lib/lib_20141216191026/oozie/oozie-hadoop-utils-<IP_ADDRESS>.2.0.0-2041.oozie-<IP_ADDRESS>.2.0.0-2041.jar, hdfs://sandbox.com:8020/user/oozie/share/lib/lib_20141216191026/oozie/oozie-sharelib-oozie-<IP_ADDRESS>.2.0.0-2041.jar]

Another issue Oozie server should be restarted after sharelib is updated.
After an upgrade (specially since I think you are not using Ambari), run the pig smoke test manually, and if there is a failure, pls make sure: hadoop-lzo jar etc. from /usr/lib/hadoop/lib are copied to /usr/lib/oozie/libext/ and the oozie server is restarted.

The related  PR is merged. Closing this issue.


Added tvOS support

Added framework and test target for tvOS. Requires Xcode 7.1 beta to build tvOS framework.

Thanks @cgoldsby ! :smile:
I've been making some big changes for the 2.0 release, which I'll be releasing tonight, or this week.
Thus, there are lots of conflicts here. If you would like to resubmit the PR, that'd be great!
Opened #39 to track this.


Build error double print

I think that forge build doesn't gracefully handle the error produced by solc. It should not produce a forge error and return stack trace, but rather surface the solc error and gracefully exit.
Using the latest version of forge.

I believe this due to the eyre hook because we currently "panic" on erroneous solc output.
instead, we should, as you suggested exit gracefully with std::process::exit(1)
here
https://github.com/gakonst/foundry/blob/8c234f75937d7cd06f6101fc298fe36da369ca44/cli/src/forge.rs#L24
or here
https://github.com/gakonst/foundry/blob/8c234f75937d7cd06f6101fc298fe36da369ca44/cli/src/cmd/build.rs#L84-L97
ideally there should be two versions of Build::run, one that std::process:exits and one that we can reuse anywhere else which returns the error instead of exiting


Add a EffectTask<Action> typealias for Effect<Action, Never> and rename Effect to EffectPublisher

Specifying Never in Effect<Action, Never> is slightly inconvenient, and it happens the majority of the times Effect is used.
Without changing the shape of Effect, this PR introduces:
typealias EffectOf<Action> = Effect<Action, Never>

to remove the mental burden of Never and save a few keystrokes.
Now that TCA is slowly moving away from Combine, most dependencies are modeled using async/await, and Effect is becoming more and more focused on reducer's products. I think that a one-generic Effect<Action> was envisaged at some point (there are a few traces in the documentation that are fixed by this PR), but it would be a source-breaking change. If it ever happens someday, this typealias should allow codebases to have smoothly migrated toward this shape already, easing the transition.
An alternative would be to define EffectOf<R:ReducerProtocol> = Effect<R.Action, Never>. In both cases, they make sense, as one can see the reducer Reducer producing an EffectOf<Action> when it receives an Action, or an EffectOf<Reducer>.
My personal preference goes toward the solution proposed in this PR, which is mentally more lightweight, but the Reducer one also packs more information, so that could be useful at some point (although I don't see any real application right now).
What do you think about it?

This sets in stone no evolution to add support of failure cases in reducers (which is the current direction anyhow 😕). Is TCA going to use the Effect type long term or opt for a strictly async return type once Combine is removed?

This sets in stone no evolution to add support of failure cases in reducers (which is the current direction anyhow 😕). Is TCA going to use the Effect type long term or opt for a strictly async return type once Combine is removed?

Given our current modeling of the reducer, Effect<Action> is definitely the most natural direction to take things. This doesn't mean we're not open to exploring how reducer "failure" could work in general, e.g. what it would mean to add throws to the signature, or what it would mean to allow effects to throw. However, previous discussion has been pretty abstract, and neither Brandon nor I understand how it could be motivated in practice yet, especially without real world uses or demonstrations via modification of the existing case studies/demos.
Your discussion and implementation definitely sound interesting, but they lacked updated sample code and real examples that demonstrate what the changes bring to the table, and so it was difficult for me to truly comprehend.
One thing that has changed since your explorations is that the new Effect.task and Effect.run modifiers are throwing, giving you some flexibility especially around cancelling async work, but if they throw something other than cancellation it is up to you to handle things, or you will get runtime warnings.

@stephencelis That is fair. It is quite an extensive change. It is a breaking change unless you can assume a generic type unless explicitly specified.
I have the strong preference of utilizing a result type rather than throws for type validation.
Not sure how to best demonstrate with sample code but will see if I can come up with something. 🙏

@tgrapperon Thanks for this! @mbrandonw and I decided to flesh out our current vision for 1.0 here: https://github.com/pointfreeco/swift-composable-architecture/discussions/1477
This includes a plan for simplifying the Effect type. In the discussion we propose EffectTask<Action> as the migratory placeholder instead of EffectOf. Would you like to make that change here? If you'd like, you can also take a stab at the associated changes for that release, like the EffectPublisher rename. If not, no worries! We'll try to tackle after merging this :smile:
Let us know what you think! Or if you have any questions/concerns.

(Oh, and if you do have things you wanna share, @JacksonUtsch, sorry to put more pressure on you to do so before 1.0, though if you don't have time to explore, there's always 2.0 😆)

I renamed EffectOf to EffectTask, and renamed Effect to EffectPublisher according to #1477.
I had already updated all occurrences of Effect<_, Never> to EffectTask in the documentation.
I've gone one step further by updating naked Effect occurrences to EffectTask or EffectPublisher according to the context. Depending on the duration of the transition to 1.0, I feel that it is better to have a documentation that is coherent with what users are experiencing, especially onboarding ones. One can easily spot these occurrences by searching for '``EffectTask``' and '``EffectPublisher``' and replace by Effect if needed.
I made the choice of seeing Effect(value:) as an EffectTask given the fact that it is often (over)used as the return value of a Reducer, even if this value's implementation is pure Combine.
I didn't update one occurrence of Effect in its own documentation, as well as the ones from README. Any general reference like "effect" was also preserved.
I've replaced all internal uses of Effect to EffectPublisher, as if Effect was already hard-deprecated. When possible, EffectTask was used.
Effect is soft deprecated. It means that Xcode won't show a warning, nor a "fix" suggestion. I've opted to EffectPublisher as the new name for this value, as it's technically correct, but I feel that EffectTask would be more effective. In any case, as long as the deprecation is soft, this fix can't probably be activated, and the renamed: argument can probably be removed.
This is not intended to be a definitive version of the PR. I'm open to any change you would suggest!

I'm good with the typealias , taking another direction for error handling. Don't believe any changes are needed for such.

The reception to the change has been positive, so we're going to move forward with this. Thanks again @tgrapperon!


Install has a problem

An error occurred when I executed my order ：
# sudo ./install
File "./install", line 48
names = {ps_line.split(' ')[0] for ps_line in ps_lines}
^
SyntaxError: invalid syntax

Can you check what version of Python is installed on your machine please? The Jobe installer needs at least Python 2.7.

I see. Thank you

After I installed Python 2.7.10, I ran into a new problem ：
Configuring for 10 simultaneous job runs
Exception during install: Couldn't determine web-server user id. Is the web server running?
Install failed
Please tell me how to solve it. Thank you very much

What flavour of Linux are you running?
Assuming the web server is running, what user_id does it have?
Line 48 in the install script
candidates = names.intersection(set(['apache', 'www-data']))

assumes the the web-server user id is either apache or www-data. Is it something else on your system, perhaps? I vaguely recall it was httpd on one system. If so, you could change line 48 to
candidates = names.intersection(set(['apache', 'www-data', 'httpd']))

Actually I think the fix for CentOS (is that what you're running?) is a couple of lines earlier, around line 46. Change the first line of get_webserver  to
ps_cmd = "ps aux | egrep /usr/sbin/(apache2|httpd)"

I've pushed a new version of the install script today with that patch in it.
I've also pushed an updated version of the documentation. I've added a new paragraph to the Installation instructions, which might be relevant if anything else goes wrong:
"Installation on Ubuntu 16.04 systems should be straightforward but installation on other flavours of Linux or on systems with non-standard configurations may require Linux administrator skills. A possible alternative approach if things go wrong is to try the experimental JobeInABox Docker image, which should be runnable with a single terminal command on any Linux system that has docker installed. Thanks to David Bowes (UHerts) for most of the work on this. Please be aware that it is still experimental and hasn't been used in production by the author. Feedback is welcomed."

Thank you for your reply. I need to have a try

Hello, I installed the Ubuntu 16.04 system using VMware. BuT Now I have a new problem:
root@admin:/var/www/html/jobe# sudo ./install
Configuring for 10 simultaneous job runs
/bin/sh: 1: Syntax error: "(" unexpected
Exception during install: Command 'ps aux | egrep /usr/sbin/(apache2|httpd)' returned non-zero exit
status 2
Install failed
Think  you

Yowch. My last push (8 days ago) introduced that bug. Sorry. Should be
fixed now.
On 05/10/17 21:32, 16sgit wrote:

Hello, I installed the Ubuntu 16.04 system using VMware. BuT Now I
have a new problem:
root@admin:/var/www/html/jobe# sudo ./install
Configuring for 10 simultaneous job runs
/bin/sh: 1: Syntax error: "(" unexpected
Exception during install: Command 'ps aux | egrep
/usr/sbin/(apache2|httpd)' returned non-zero exit
status 2
Install failed
Think you
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/trampgeek/jobe/issues/23#issuecomment-334396732,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDNVhyEg2Otdy-NWigWtII4e29DE671ks5spJQmgaJpZM4PiSNH.

Think you How to solve the problem :
root@admin:/var/www/html/jobe# sudo ./install
Configuring for 10 simultaneous job runs
Exception during install: Command 'ps aux | egrep '/usr/sbin/(apache2|httpd)'' returned non-zero exit status 1
Install failed

You don't appear to have pulled the fix I pushed to github, namely to
change that line to
ps_cmd ="ps aux | egrep '/usr/sbin/(apache2|httpd)'"
Richard
On 06/10/17 14:28, 16sgit wrote:

Think you How to solve the problem :
root@admin:/var/www/html/jobe# sudo ./install
Configuring for 10 simultaneous job runs
Exception during install: Command 'ps aux | egrep
'/usr/sbin/(apache2|httpd)'' returned non-zero exit status 1
Install failed
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/trampgeek/jobe/issues/23#issuecomment-334635288,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDNVs4j-uw70vHR764SdSv8a98wEsh_ks5spYJGgaJpZM4PiSNH.

Thank you for your reply, but I still don't know how to do it after your reply
In my code that line is
ps_cmd ="ps aux | egrep '/usr/sbin/(apache2|httpd)'"
What do i need to do

Ah, ok. Your previous posting had just a double quote at the end of that line and I thought that was the problem.
It looks like Apache isn't running. Did you run the commands given in the Jobe readme file? Specifically:
    apt-get install apache2 php libapache2-mod-php php-mcrypt mysql-server\
      php-mysql php-cli octave nodejs\
      git python3 build-essential openjdk-9-jre openjdk-9-jdk python3-pip\
      fp-compiler pylint3 acl
    pylint --reports=no --generate-rcfile > /etc/pylintrc

They need to be run before attempting the Jobe install.
If you did run those commands and Apache isn't running, you'll need to find out why. You could start by rebooting, then trying commands like sudo service apache2 restart. But it's strange, because installing on Ubuntu 16.04 is normally straightforward.

Closing as no recent communications.


[SPARK-42395][K8S]The code logic of the configmap max size validation lacks extra content

[SPARK-42395][K8S]The code logic of the configmap max size validation lacks extra content
What changes were proposed in this pull request?
This PR aims to add the extra content of the configmap into the configmap max size validation
In each configmap, Spark adds an extra content in a fixed format,this extra content of the configmap is as belows:
spark.kubernetes.namespace: default
spark.properties: |
#Java properties built from Kubernetes config map with name: spark-exec-b47b438630eec12d-conf-map
#Wed Feb 08 20:10:19 CST 2023
spark.kubernetes.namespace=default
The example specific content comes from the command output:
kubectl get cm spark-exec-b47b438630eec12d-conf-map -o yaml
apiVersion: v1
data:
spark.kubernetes.namespace: default
spark.properties: |
#Java properties built from Kubernetes config map with name: spark-exec-b47b438630eec12d-conf-map
#Wed Feb 08 20:10:19 CST 2023
spark.kubernetes.namespace=default
immutable: true
kind: ConfigMap
metadata:
creationTimestamp: "2023-02-08T12:14:13Z"
labels:
spark-app-selector: spark-9c4a3cc1d752491cba899135d8fbf492
spark-role: executor
name: spark-exec-b47b438630eec12d-conf-map
namespace: default
resourceVersion: "62638833"
uid: 28f7bbd1-38aa-4e8e-b715-9cc8eb047074
Why are the changes needed?
If no chanages,there may be a problem like jira SPARK-42344
Does this PR introduce any user-facing change?
The major of this pr is the same to the jira SPARK-42344.
How was this patch tested?
Local test
TEST CASE 1:
1.mock a file named log4j.properties in spark home directory
2.the file name length is 16,and the extra content size is 163.
set the size of the log4j.properties to:
1048576 - 163 -16 = 1048397
3.truncate the file to 1048397
truncate -s 1048397 log4j.properties
ls -l
-rwxr-xr-x 1 root root 1048397 Feb  9 16:13 log4j.properties
4.test with the commond spark-submit with arg :
--conf
spark.home=/home/work/code/apache/spark-github/dist
5.Test expectations:
The configmap is not include the content log4j.properties.Because the size is just equal to 1048576.
There is only one data in configmap spark-exec-d09ef186354c6ebe-conf-map
kubectl get cm
NAME                                   DATA   AGE
ingress-traefik                        1      203d
kube-root-ca.crt                       1      227d
spark-exec-d09ef186354c6ebe-conf-map   1      33s
spark-standalone-exporter              1      203d
spark-standalone-graphite-mapping      1      203d
kubectl get cm spark-exec-e33068863475c9ee-conf-map -o yaml
apiVersion: v1
data:
spark.properties: |
#Java properties built from Kubernetes config map with name: spark-exec-e33068863475c9ee-conf-map
#Thu Feb 09 12:36:20 CST 2023
spark.kubernetes.namespace=default
immutable: true
kind: ConfigMap
metadata:
creationTimestamp: "2023-02-09T04:36:20Z"
labels:
spark-app-selector: spark-8e68465119bd411ba0b0cc797abe294c
spark-role: executor
name: spark-exec-e33068863475c9ee-conf-map
namespace: default
resourceVersion: "62889868"
uid: ba8d7f31-a4c5-42fd-9aba-a02b73eb37bc
TEST CASE 2:
1.the file name length is 16,and the extra content size is 163.
set the size of the log4j.properties to:
1048576 - 163 - 16 - 1= 1048396
2.truncate the file to 1048396
truncate -s 1048396 log4j.properties
ls -l
-rwxr-xr-x 1 root root 1048396 Feb  9 16:32 log4j.properties
3.test with the commond spark-submit with arg :
--conf
spark.home=/home/work/code/apache/spark-github/dist
4.Test expectations:
The configmap is include the content log4j.properties.
There is 2 datas in the configmap spark-exec-1d90d186354e63ee-conf-map
kubectl get cm
NAME                                   DATA   AGE
ingress-traefik                        1      203d
kube-root-ca.crt                       1      227d
spark-exec-1d90d186354e63ee-conf-map   2      52s
spark-standalone-exporter              1      203d
spark-standalone-graphite-mapping      1      203d

Could you please review this pr? @dongjoon-hyun @LuciferYang
Thanks!

Can I take your free time to help me to review this pr please？@dongjoon-hyun  @HyukjinKwon @srowen @LuciferYang

I don't know enough about K8S to review this. Seems harmless

Thanks for review!

Can you help recommend others to the review？ @srowen

Can anyone else help review this PR? @viirya
Thanks!


Split large aggregations into multipl records

This adds a hedge into the binary opt builder to check if an append will cause the offsets to overflow an int32 (which is what the arrow arrays use for offsets) if so it returns an error indicating the max array size has been reached.
This updates the hash aggregator to check if this max array size error has been returned during aggregation; if it has, it will rollback the row appends and start a new set of arrays to aggregate onto. At the end it will create multiple records out of these aggregates and send them as the callback.
This does have a knock on effect of Hyrum's law, where previously a user may have correctly assumed that an aggregate would only every call the callback function once. However this is definitely no longer true, for example in Parca we currently have this problem.
So before clients of this code update they should take care to ensure they are correctly handling aggregate callbacks. That said; it's unlikely to hit because it requires a buffer overflow which means one would be querying lots of data.

name                  old time/op    new time/op    delta
Aggregation/sum-10      1.29ms ± 1%    1.31ms ± 0%  +1.33%  (p=0.000 n=10+10)
Aggregation/count-10    1.29ms ± 0%    1.31ms ± 0%  +1.17%  (p=0.000 n=10+9)
Aggregation/max-10      1.30ms ± 0%    1.31ms ± 0%  +1.05%  (p=0.000 n=10+8)

name                  old alloc/op   new alloc/op   delta
Aggregation/sum-10      1.39MB ± 0%    1.39MB ± 0%  +0.04%  (p=0.000 n=9+10)
Aggregation/count-10    1.39MB ± 0%    1.39MB ± 0%  +0.04%  (p=0.000 n=10+9)
Aggregation/max-10      1.39MB ± 0%    1.39MB ± 0%  +0.03%  (p=0.000 n=10+9)

name                  old allocs/op  new allocs/op  delta
Aggregation/sum-10       20.9k ± 0%     20.9k ± 0%  +0.11%  (p=0.000 n=10+10)
Aggregation/count-10     20.9k ± 0%     20.9k ± 0%  +0.11%  (p=0.000 n=10+10)
Aggregation/max-10       20.9k ± 0%     20.9k ± 0%  +0.11%  (p=0.000 n=8+9)

Here are the current benchmarks. Currently looking into bench marking large aggregations to see if it's going to make a difference to switch to the large binary arrays

thor@thors-MacBook-Pro physicalplan % benchstat largebinary_overflow.txt splitlarge_overflow.txt
name                         old time/op    new time/op    delta
_Aggregate_ArrayOverflow-10      102s ± 5%       63s ± 1%  -38.56%  (p=0.000 n=9+7)

name                         old alloc/op   new alloc/op   delta
_Aggregate_ArrayOverflow-10     245GB ± 0%     206GB ± 0%  -16.06%  (p=0.000 n=10+10)

name                         old allocs/op  new allocs/op  delta
_Aggregate_ArrayOverflow-10     3.23M ± 0%     3.23M ± 0%   +0.11%  (p=0.000 n=10+10)

Wrote a benchmark where it aggregates a ton of data to see what the difference between using large binary vs. splitting

implementation
memory
cpu

large binary array
https://pprof.me/b73bdb6/
https://pprof.me/a397fdf/

split binary array
https://pprof.me/ab7d3d0/
https://pprof.me/ae474c6/

I'm a little surprised by these results, I thought there would be only a small amount of memory overhead with the large binary arrays @asubiotto wdyt?

Thanks for running the experiments!
I do expect more memory used since we're adding 4 bytes per value, but probably not as large as you're seeing. BTW, I think there is still a difference in your second benchmark, just that benchstat probably determined there were not enough samples to display a statistically significant diff.
Here's one last suggestion:
In the Cockroach vectorized engine (and other columnar databases), there's a notion of a global "batch" size (https://github.com/cockroachdb/cockroach/blob/8b9c7dd37f2caafabe15167ef8410620415ee071/pkg/col/coldata/batch.go#L84) for execution that operators try to respect. I think we eventually want to have something like this so that buffering operators (like the hash agg) start emitting data early to reduce memory usage and unblock downstream operators. Maybe we should introduce a batch size and have the hash aggregate respect it (eventually moving all the other buffering operators to do so), so the split would happen a lot earlier than when we reach overflow, which also makes this behavior easier to test. The downside is that we definitely need to change the consumers of this API.

Yea you're definitely right about not running enough samples. The time to run these benchmarks is long so I definitely shorted it on that trial.
I like the idea of batch sizes and considered it initially, but it had two draw backs I could determine.

If we emit data early in the hash aggregate won't that mean we could potentially not be performing the full aggregation? Effectively kicking the can down the road.
It still doesn't solve the overflow problem, even if the batch size is small a binary column could use large enough values that it overflows the array without exceeding the batch size.

Yea you're definitely right about not running enough samples. The time to run these benchmarks is long so I definitely shorted it on that trial.
I like the idea of batch sizes and considered it initially, but it had two draw backs I could determine.

If we emit data early in the hash aggregate won't that mean we could potentially not be performing the full aggregation? Effectively kicking the can down the road.

Yes, the "emitting data early" part was more for other operators (e.g. ordered agg). In the hash agg's case it would still buffer all results (but a separate record per group, so it's not as big a problem as using a single record for all results), and split in the same path you do (i.e. in the Finish call before returning all results).

It still doesn't solve the overflow problem, even if the batch size is small a binary column could use large enough values that it overflows the array without exceeding the batch size.

It could, but it's a lot less likely. It depends how big we think a stacktrace will be. I've only seen 4KiB stacktraces max in prod, and with an 8192 batch size for example, we'd need every stacktrace to be around 250KiB.


Backend - /auth/forgot-password

[x]  Accept an email address as input.
[x]  Check if the email is associated with a registered user.
[x]  If the email is valid, generate a unique token.
[x]  Send an email to the user containing a link to reset their password. The link should embed the unique token.
[x]  Upon clicking the link, the user should be directed to a secure page where they can reset their password.

forgot-password api should return OK regardless of the user with the provided email is found or not to prevent attacks trying to obtain emails registered in the system.

#285


.NET Core detection seems to need support .NET 5 or more

Summary of your issue
OpenCvSharp.OpenCvSharpException: 'Failed to find dll "OpenCvSharpExtern", for processor architecture AMD64.' is thrown when create Mat at first time on .NET 5.
But it can ignore and it seems everything works fine.
I doubt WindowsLibraryLoader.cs#L110 misses to detect .NET 5 or more.
Environment

Visual Studio 2019 / .NET 5.0.8
OpenCvSharp <IP_ADDRESS>10725

What did you intend to be?
I guess, .NET Core detection needs to support .NET 5 or more (WindowsLibraryLoader.cs#L110).
            return RuntimeInformation.FrameworkDescription.StartsWith(".NET Core", StringComparison.Ordinal);

RuntimeInformation.FrameworkDescription returns

.NET 5 : ".NET 5.0.8"
.NET 6 (VS2022 preview 2) : ".NET 6.0.0-preview.6.21352.12"

I cannot show right answer is but it may check with Regex like @"^.NET (\d|Core)" or reject "NET Framework"?

Thank you :+1:
Here seems to be a simple solution: https://github.com/dotnet/runtime/blob/57bfe474518ab5b7cfe6bf7424a79ce3af9d6657/src/libraries/Common/tests/TestUtilities/System/PlatformDetection.cs#L24


testing: parent B.Cleanup() functions do not run if a sub-benchmark panics

What version of Go are you using (go version)?

$ go version
go version go1.20.4 darwin/arm64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="arm64"
GOBIN=""
GOCACHE="/Users/evan.jones/Library/Caches/go-build"
GOENV="/Users/evan.jones/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/evan.jones/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/evan.jones/go"
GOPRIVATE=""
GOPROXY=""
GOROOT="/opt/homebrew/Cellar/go/1.20.4/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/opt/homebrew/Cellar/go/1.20.4/libexec/pkg/tool/darwin_arm64"
GOVCS=""
GOVERSION="go1.20.4"
GCCGO="gccgo"
AR="ar"
CC="cc"
CXX="c++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-O2 -g"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-O2 -g"
CGO_FFLAGS="-O2 -g"
CGO_LDFLAGS="-O2 -g"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/g1/97d8s0r57hj4nv4_qd3fqcrm0000gp/T/go-build3259637153=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
The following benchmark named BenchmarkSubBenchPanicNeverRunsCleanup calls b.Cleanup, then panics in a sub-benchmark. The "higher level" Cleanup functions never run, but the ones in the specific benchmark do. The equivalent code for a Test calling T.Cleanup(), the cleanup functions are run correctly. This is similar to bug as #41355, which had similar problems when panicing in a sub-test. I believe the parent functions should run.
package benchcleanup

import (
	"testing"
)

func BenchmarkSubBenchPanicNeverRunsCleanup(b *testing.B) {
	b.Cleanup(func() {
		println("top-level benchmark cleanup is never called")
	})
	b.Run("subbench_level_1", func(b *testing.B) {
		b.Cleanup(func() {
			println("sub-benchmark level 1 cleanup is never called")
		})
		b.Run("subbench_level_2", func(b *testing.B) {
			b.Cleanup(func() {
				println("sub-benchmark level 2 cleanup IS called")
			})
			panic("sub-benchmark level 2 panic")
		})
	})
}

func TestSubTestPanicNeverRunsCleanup(t *testing.T) {
	t.Cleanup(func() {
		println("top-level test cleanup is called")
	})
	t.Run("subbench_level_1", func(t *testing.T) {
		t.Cleanup(func() {
			println("sub-test level 1 cleanup is called")
		})
		t.Run("subbench_level_2", func(t *testing.T) {
			t.Cleanup(func() {
				println("sub-test level 2 cleanup is called")
			})
			panic("sub-test level 2 panic")
		})
	})
}

What did you expect to see?
The cleanup functions should be called.
What did you see instead?
Only the cleanup function in the same benchmark are called.

Thanks for the report. Want to try a fix?


Stops showing Headsign for Route Even if One Direction of Travel

Summary of changes

Asana Ticket: Stops showing Headsign for Route Even if One Direction of Travel

When a headsign has no trips associated with it don't show departure row
Note: currently adding tests. Would like feedback on logic
General checks

[ ] Are the changes organized into self-contained commits with descriptive and well-formatted commit messages? This is a good practice that can facilitate easier reviews.
[ ] Testing. Do the changes include relevant passing updates to tests? This includes updating screenshots. Preferably tests are run locally to verify that there are no test failures created by these changes, before opening a PR.
[ ] Tech debt. Have you checked for tech debt you can address in the area you're working in? This can be a good time to address small issues, or create Asana tickets for larger issues.

New UI, or substantial UI changes

[ ] Cross-browser compatibility is less of an issue now that we're no longer supporting IE, but changes still need to work as expected in Safari, Chrome, and Firefox.
[ ] Are interactive elements accessible? This includes at minimum having relevant keyboard interactions and visible focus, but can also include verification with screen reader testing.
[ ] Other accessibility checks such as sufficient color constrast, or whether the layout holds up at 200% zoom level.

New endpoints, or non-trivial changes to current endpoints

[ ] Have we load-tested any new pages or internal API endpoints that will receive significant traffic? See load testing docs
[ ] If this change involves routes, does it work correctly with pertinent "unusual" routes such as the combined Green Line, Silver Line, Foxboro commuter rail, and single-direction bus routes like the 170?

Closing as obsolete.


Implement the getBlockLocations  to mock the block info for Presto

As Presto requires the Block Information based on a specific file path by default, we need to implement the getBlockLocations  to mock the block info for Presto. Otherwise, Presto will throw exception when querying.

@JiamingMai Does UFSBaseFileSystem needs to implement getBlockLocations?

@JiamingMai Does UFSBaseFileSystem needs to implement getBlockLocations?
No need to implement getBlockLocations in UFSBaseFileSystem.


Gradle plugin does not like my coverage data

When I debug my Gradle build, it seems the plugin wants to send data like this to Bitbucket:
{
  "files": [
    {
      "path": "my-submodule/src/main/java/com/example/service/somePackage/SomeFile.java",
      "coverage": "C:;P:;U:"
    },
    {
      "path": "my-submodule/src/main/java/com/example/service/someOtherPackage/SomeOtherFile.java",
      "coverage": "C:;P:;U:13,17,18"
    },
    {
      "path": "my-submodule/src/main/java/com/example/service/someThirdPackage/SomeThirdFile.java",
      "coverage": "C:;P:;U:"
    },
	// ...
  ]
}

If I try it on the command line, it fails:
curl --verbose -X POST -H "Content-Type: application/json" --data @data.json -u "myuser:$BITBUCKET_TOKEN" "https://my.bitbucket.host/bitbucket/rest/code-coverage/1.0/commits/63642f1b842e22d1e1218cc2404adabb8dd42b41"
(...)
< HTTP/1.1 400
(...)
{"context":null,"message":"Invalid or empty coverage data was supplied for one or more files.","exceptionName":null,"invalidEntities":[{"path":"my-submodule/src/main/java/com/example/service/somePackage/SomeFile.java","coverage":"C:;P:;U:"},
(...)
]}

So it has an issue with files for which only empty coverage was found.
Gradle however, does not detect this outcome, despite of the same HTTP response code (400) that I detect in the access log of Bitbucket server, and does not report this to the user, but something else:
2023-07-27T16:21:21.998+0200 [DEBUG] [jdk.internal.httpclient.debug] [HttpClient-6-Worker-0] [2923s 652ms] Http1Exchange getResponseAsync completed java.net.http.HttpTimeoutException: request timed out
2023-07-27T16:21:21.998+0200 [DEBUG] [jdk.internal.httpclient.debug] [HttpClient-6-SelectorManager] [2923s 652ms] SocketTube(6) got read error: java.io.IOException: connection closed locally
2023-07-27T16:21:21.998+0200 [DEBUG] [jdk.internal.httpclient.debug] [HttpClient-6-Worker-0] [2923s 652ms] Http1Exchange https://my.bitbucket.host/bitbucket/rest/code-coverage/1.0/commits/63642f1b842e22d1e1218cc2404adabb8dd42b41: completed cf with java.net.http.HttpTimeoutException: request timed out

So the outcome is a Gradle exception saying:
2023-07-27T16:21:22.010+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * Exception is:
2023-07-27T16:21:22.010+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':my-project-subproject:publishJacocoCodeCoverageToBitbucket'.
(...)
2023-07-27T16:21:22.010+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] Caused by: org.gradle.api.GradleException: Failed to send code coverage to Bitbucket.
(...)
2023-07-27T16:21:22.012+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] Caused by: java.net.http.HttpTimeoutException: request timed out
2023-07-27T16:21:22.012+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]   at java.net.http/jdk.internal.net.http.HttpClientImpl.send(HttpClientImpl.java:559)
2023-07-27T16:21:22.012+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]   at java.net.http/jdk.internal.net.http.HttpClientFacade.send(HttpClientFacade.java:119)
2023-07-27T16:21:22.012+0200 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]   at dev.turingcomplete.bitbucketcodecoverage.PublishCodeCoverageToBitbucketTask.publishCodeCoverageToBitbucketApi(PublishCodeCoverageToBitbucketTask.kt:221)

At least that's what I think is going on. I couldn't find a way to look into the HTTPS traffic via Gradle.

I have similar failure, but the error message is correct.
Failed to send code coverage to Bitbucket. Got unexpected status code 400 and body:

Thanks to the work of @madisparn, empty coverage should now work with version 1.1.0.


#153 Broker created by OpenShift operator does not support "oc port-forward"

Issue #153
Added a bindToAllInterfaces option for acceptors. The acceptor will
bind to <IP_ADDRESS> if this option is set to true.

I wonder if a boolean option is the best, would a comma list be better? I note that kubectl port-forward [1] has --address  as a comma list, where <IP_ADDRESS> is a valid option, as would localhost,w.x.y.z or localhost,CLUSTER_IP
All interfaces would work as an option, but it may be two open/exposed
[1] https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#port-forward/

@gtully The comma sep list supplied in --address option is the listening host's address, we don't need to specify that in CR. The broker acceptors can either bind to the pod's hostname or <IP_ADDRESS> (only for port-forwad, which is most for testing, not productization env). I think that'll be sufficient right?

my point is that is is not a binary decision, either or. The --addresses is an example where the list of bind addresses works for any case. It can contain a single entry for the all interfaces case or individual ips.

my point is that is is not a binary decision, either or. The --addresses is an example where the list of bind addresses works for any case. It can contain a single entry for the all interfaces case or individual ips.

what's the use case where use need the acceptor to bind multiple addresses in a pod?

@gtully Gary I'll mrge this. Pls raise an issue if you think there is more to improve.


⚠ Samsung has degraded performance

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

HTTP code: 200
Response time: 1873 ms

Resolved: Samsung performance has improved in 967feee.


Fix TypeError when using LogstashFormatter on Py3

When logging something using LogstashFormatter in python3, you get the following error:
TypeError: unsupported operand type(s) for +: 'dict_items' and 'dict_items'
To avoid that, casting both elements into _build_fields as list.

I committed 699cef8, thanks @afrancais


increase contrast for typing "Comments" in dark theme

When I entered a Comment (the only one I see at the moment!) for the "November update for docs.microsoft.com" (https://docs.microsoft.com/en-gb/teamblog/docs-november-update?hubRefSrc=email&utm_source=lfemail&utm_medium=email&utm_campaign=lfnotification),
my comment text went in with dark gray text on a black background.
I see other people have commented on the contrast in other areas already.
 Facebook header, MSDN header, ...)
Maybe a given developer can see low-contrast text with their particular monitors and room lighting and eyesight, but it's almost certain that SOMEBODY is going to find it difficult or impossible to read.

⚠ Idea migrated from UserVoice
Created By: Wayne Erfling
Created On: 2017/04/02 10:43:03 +0000
Votes at Migration: 1
Supporters at Migration: 1

This is no longer applicable as we switched to GitHub issues.


Add outline items for the PDF

Hello again Sara,
sorry if I create too many issues, but I just noticed today that the generated PDF doesn't have outline items for readers to jump around:

Is there a way to create an outline in the sidebar for PDF readers?
Many thanks and Happy New Year!

Hey!
I couldn't find a way to do it with code so I had to buy a software to do it
https://www.onekerato.com/pdfoutliner.html
Will add this to the readme.
When it comes to the other formats I added it with https://calibre-ebook.com/
It's a great free software that will pretty much any need edits on epubs and mobi but not on PDFs :/

Also no worries about creating this! It's good, reminds me to put some more info on the readme :)
Happy new year!!


set constraints for autocomplete suggestion overlay

This PR contains my attempt to set constraints on autocomplete suggestion layout such that it follows the textfield target width and height-constrained as the remaining available space without insets (soft keyboard).
Screenshots:

Before
After

Fixes:

https://github.com/flutter/flutter/issues/78746

Related PRs:

https://github.com/flutter/flutter/pull/143249

Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is [test-exempt].
[ ] I followed the [breaking change policy] and added [Data Driven Fixes] where supported.
[ ] All existing and new tests are passing.

Thanks for the work. I tested it and it looks really good.
https://github.com/flutter/flutter/pull/143249 contains a large autocomplete overhaul which seems to address the goals of this PR. However, if this PR can fulfill the same requirements, then we can work towards landing this instead.
I ran the tests in that PR with the changes in this PR, and the following tests are failing:
From that PR:

can split the field and options
correct options alignment for RTL in direction .up
correct options alignment for RTL in direction .down
options width matches field width after rebuilding
options width matches field width after changing
options when screen changes portrait to landscape and overflows
when opening up screen changes portrait to landscape and overflows

Originally in RawAutocomplete:

when not enough room for options, options cover field (OptionsViewOpenDirection.up)
when not enough room for options, options cover field (OptionsViewOpenDirection.down)

@victorsanni which test files that contain the failing tests? I run these test files and they are green.

@victorsanni what is the reason of using SizedBox.shrink() here? For search anchor purpose?
https://github.com/flutter/flutter/blob/3449a17109010b0349b4baf91460394c19bc9cb4/packages/flutter/lib/src/widgets/autocomplete.dart#L549-L550

Hi @dikatok, I think with the latest commit to @justinmc's PR, the issues linked to this PR should be fixed. I'd recommend holding off on this PR for a bit and following up on the other PR.

@victorsanni I tested using the code in @justinmc's PR, it does not fix part of the overlay hidden behind the soft keyboard.

In that case then it seems like this is a separate issue. Can you file an issue to go through the triage process so it can be verified as valid?
@justinmc's PR is a huge refactor of RawAutocomplete that will probably be incompatible with the changes in this PR, so it would be advisable to wait for the refactor to land (especially as its close to completion), then work with the post-refactored code to fix this issue. That PR fixes the linked issue, as well as a couple other issues.
Alternatively you could rebase with Justin's PR and work from there, although the PR is still in progress so changes can happen at any time. Personally I'd recommend just holding off on this PR until Justin's PR lands (or is closed).

@victorsanni Okay, here is my plan for this PR then

create the specific issue this PR is meant to fix
merge the test from https://github.com/flutter/flutter/pull/143249, and make it pass
rebase the result of https://github.com/flutter/flutter/pull/143249 when completed

What do you think?

Will wait for the result of https://github.com/flutter/flutter/pull/143249

Fixes https://github.com/flutter/flutter/issues/157664

@victorsanni Okay, so here is the plan for this PR then

create the specific issue this PR is meant to fix
merge the test from Autocomplete Options Width #143249, and make it pass
rebase the result of Autocomplete Options Width #143249 when completed

What do you think?

I'm thinking same but move the 2nd step to after the 3rd step?

As you are taking over that PR, do you have rough estimate on when it will be completed?

I am almost done, just fixing some failing tests.

@dikatok can you rebase with the changes in https://github.com/flutter/flutter/pull/143249 and start working to fix this issue from there? it should accelerate reviewing this PR.


dark mode fixed in all views (create project, view projects, dashboard)

Description
Fixes Dark mode in create project, view all, and profile page.
Type of change
Please delete options that are not relevant.
Bug fix (non-breaking change which fixes an issue)
Change Status

[ ] Complete, tested, ready to review and merge
[x] Complete, but not tested (may need new tests)
[ ] Incomplete/work-in-progress, PR is for discussion/feedback

How Has This Been Tested?

[ ] Test A
[ ] Test B

Checklist

[x]  My code follows the style guidelines of this project
[x]  I have performed a self-review of my own code
[ ]  My code has been reviewed by at least one peer
[ ]  I have commented my code, particularly in hard-to-understand areas
[ ]  I have made corresponding changes to the documentation
[ ]  My changes generate no new warnings
[ ]  I have added tests that prove my fix is effective or that my feature works
[ ]  New and existing unit tests pass locally with my changes
[ ]  There are no merge conflicts

I noticed that the dark mode toggle is broken in the settings tab of the application! Should be a fix pertaining to the toggle needing to look at the localstorage of the application and read the boolean true or false properly. example: sessionstorage.getItem('dark-mode')

Looks great!


HTML

HTML
User Story
As a bootcamp student
I want the prework notes to be structured on a webpage
so that I can easily find and read information
Acceptance Critera
GIVEN a Prework Study Guide website
WHEN I visit the website in my browser
THEN I see four boxes titled HTML, CSS, Git, and JavaScript with associated notes listed

Added HTML code to main


Allow php-jwt 4.0

firebase\php-jwt 3.0 and 4.0 are backwards compatible.

Are there any Plan to release this soon?
Would help us in Production, where we only have JWT 4.0.
Thanks!

Going to release master as 1.2.0 next week. Just need to do one more fix there.

Hello again :)
Sorry for asking again, but I would really love to use this Lib with this Change.
Thanks a lot!

Sorry, got held up with other stuff - it is releassed now - https://github.com/TheNetworg/oauth2-azure/releases/tag/v1.2.0
Also, we are open for pull requests, so in case you would like to contribute :) There is going to be a version v2.0.0 released with more features and more awesomeness.

Wow, that was fast now :)
Thanks a lot!!!


fix(utils): support record-level default schema values

Before this change, during the process of filling default configuration values, if a record existed in the schema with a structure similar to the following:
{
  "default": {
   "some_field": "record_level_default"
 },
 "fields": [
  {
   "some_field": {
    "type": "string",
    "default": "field_level_default"
   }
  }
 ]
}

the value record_level_default would be ignored and the field set to the field_level_default value. Similarly, in case of no field-level default, the field would be set to null.
This commit modifies the utils/fillConfigRecord logic to assign fields with record-level default values when available.
Example of default configuration values that were previously ignored: https://github.com/Kong/kong/blob/8fe14097a17cf904676672fc8cdaabe5e02e4a2d/kong/plugins/opentelemetry/schema.lua#L49 https://github.com/Kong/kong/blob/8fe14097a17cf904676672fc8cdaabe5e02e4a2d/kong/plugins/opentelemetry/schema.lua#L90
KAG-4149

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 59.36%. Comparing base (241dbb8) to head (e1234b7).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #431      +/-   ##
==========================================
+ Coverage   59.32%   59.36%   +0.03%
==========================================
  Files          69       69
  Lines        4219     4223       +4
==========================================
+ Hits         2503     2507       +4
  Misses       1134     1134
  Partials      582      582

Flag
Coverage Δ

2.1
36.98% <100.00%> (+0.05%)
:arrow_up:

2.2
49.91% <100.00%> (-0.10%)
:arrow_down:

2.3
50.72% <100.00%> (+0.04%)
:arrow_up:

2.4
37.08% <100.00%> (-13.65%)
:arrow_down:

2.5
50.76% <100.00%> (+0.04%)
:arrow_up:

2.6
50.62% <100.00%> (-0.10%)
:arrow_down:

2.7
52.33% <100.00%> (-0.10%)
:arrow_down:

2.8
37.08% <100.00%> (-15.35%)
:arrow_down:

3.0
56.57% <100.00%> (+0.04%)
:arrow_up:

3.1
58.27% <100.00%> (+0.03%)
:arrow_up:

3.2
58.32% <100.00%> (+0.03%)
:arrow_up:

3.3
58.32% <100.00%> (+0.03%)
:arrow_up:

3.4
58.65% <100.00%> (+0.03%)
:arrow_up:

community
42.81% <100.00%> (+0.05%)
:arrow_up:

enterprise
57.92% <100.00%> (+0.03%)
:arrow_up:

integration
59.36% <100.00%> (+0.03%)
:arrow_up:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


chore(drivers): add a warning for not officially supported archs

Signed-off-by: Andrea Terzolo<EMAIL_ADDRESS>What type of PR is this?
/kind documentation
Any specific area of the project related to this PR?
/area build
What this PR does / why we need it:
This pull request wants to clarify which are officially supported. This doesn't mean that all other architectures won't work it only suggest that we are focusing our efforts on the officially supported ones.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
NONE

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 7fddc769352f93242bacf23b00d513a2510ed7ee

New changes are detected. LGTM label has been removed.

LGTM label has been added.  Git tree hash: d8ece2a8ef04f3f1b92171a9a709d4e59e72c1e9

/cc @leogr


When vieweing a post with multiple images, clicking on the arrows disables keyboard navigation

Describe the bug
What it says on the title. :)
To Reproduce
Steps to reproduce the behavior:

Open a post with more than one image.
Press the left or right arrow keys, the images will scroll.
Now click on one of the arrows to scroll again.
Press the left or right arrow keys, not the images will not scroll

Expected behavior
Images should always scroll when with the arrow keys.
Desktop (please complete the following information):

OS: elementary OS 6
Browser Firefox and Chrome
Version 115.

@eliocamp does this still happen for you? I can't repro anymore, so I think it might be fixed.

Nope, I think this was fixed.


fix(ngOptions): do not watch properties starting with $

Expressions that compute labels and track by values for ngOptions were
being called for properties, that start with $ even though those properties
were being ignored as options.
Closes #11930

LGTM


⚠ ClamAV has degraded performance

In 2bd87a0, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 77 ms

Resolved: ClamAV performance has improved in 686d2d9.


Update deployment docs to reference docs in IDR deployment github

Removes most of the technical detail from the deployment page and links to https://github.com/IDR/deployment/ which will contain the docs. This should be easier to keep up to date.
--depends-on https://github.com/IDR/deployment/pull/8
To test: docker run -it --rm -p 4000:4000  -v $PWD:/src jekyll/jekyll jekyll server -w -s /src and go to http://localhost:4000/

In terms of removing elements which have to be kept up-to-date, :+1: The page is a bit anemic, though. Perhaps longer-term we can try to develop a graphic of the deployment infrastructure (which we could hot-link...).
This may also be the place for rsync & download information, since that would be a pre-requisite to truly running your own.
Ok to merge once IDR/deployment#8 is in

Merging for demo34 release.


'_request_ctx_stack' is deprecated and will be removed in Flask 2.3

Appreciate this is a waning not a failure.  Just thought Id log it as I cant see it at this point.
Im getting this while using pytest, under normal flak run it doesn't throw the warning
venv/lib/python3.9/site-packages/flask_debugtoolbar/__init__.py:5
 /......./venv/lib/python3.9/site-packages/flask_debugtoolbar/__init__.py:5: DeprecationWarning:

  '_request_ctx_stack' is deprecated and will be removed in Flask 2.3.

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html

Hmm, this was fixed in https://github.com/pallets-eco/flask-debugtoolbar/pull/183
What's your entrypoint command? It must be doing something that causes:
if version_builder.parse(flask.__version__) >= version_builder.parse("2.2.0")

to be false.

I'm going to close, as I don't think there's much to do here, and this will go away once we drop support for flask versions < 2.2.
Happy to accept a PR if you end up wanting to tweak the if statement.

'_request_ctx_stack' is now removed in Flask 3.0.0, and flask-debugtoolbar 0.13.1 still tries to import it.
see:
https://flask.palletsprojects.com/en/3.0.x/changes/
https://github.com/pallets/flask/pull/5223/files
https://github.com/pallets-eco/flask-debugtoolbar/blob/45d3588bb6985e78ae06194d3ed8bf2de3c56594/src/flask_debugtoolbar/__init__.py#L5


Action command java

Added javaCode support for actions in cases of business logic being executed on server side for specific actions.
Added ActionCommand for sending command including object and action method (javaCode) to be performed on object.
Added ActionCommandDAO which listens for actionCommand instances and invokes the necessary methods.

Currently the action methods generated in Java are all static and do not contain meta-information such as label, isEnabled() and such.

@kgrgreer Can you advise on the use case for this? I'm having trouble with the design because I don't know what were designing it for.
Do we want to execute actions on objects that are already live instances on the Java side?  Or do we want to execute actions on objects that live in a DAO on the server?  Or are we sending complete objects to the server upon which we want the server to execute actions?


Model Binder: invalid value in property makes model null

I have the following ASP.NET Core controller action:
public async Task<IActionResult> Post([FromBody]Model model) { }

The Model is the following:
public class Model {
  public String Name { get; set; }
  public Int32? Age { get; set; }
}

I the post the following model to the API:
model = { name: "John", age: "Ab" }

On my controller the model becomes null. If I pass an int as age then it works fine:
model = { name: "John", age: 30 }

If a property has an invalid type should not the model get the default value for that property?
Instead of just setting the entire model to null?

This is all about Angular.js, Angular raises an "invalid field type" error.

@m4nd1cm4rk0 This is not an angular problem ... I also tested it with PostMan. I just updated my question to better explain the problem ... I am not sure if this is by design or something not expected. But if it is by design I don't think a model should be null when one of the properties has an invalid value.

I don't think a model should be null when one of the properties has an invalid value.

What is your reasoning for this preference?
In any case, it's up to the formatter or, in this case, the JSON.Net deserializer to instantiate the model. JSON.Net throws when it encounters an error. Eventually it returns null to MVC. Suggest you file a bug at https://github.com/JamesNK/Newtonsoft.Json/issues if you feel that's incorrect.

What is your reasoning for this preference?

Well, that way I will be able to validate the other properties of the model and say which ones are valid or not ... For those not being defined I could always compare with the default value and emit something ...
I mean, how do you do validation if the model is null? You can only say "The model is invalid".
Let me know your opinion ... Maybe I am missing something here ...

how do you do validation if the model is null?

When JSON.Net throws an Exception during deserialization, MVC adds the information to the ModelStateDictionary. Later validation isn't relevant because, as you point out, the model is null.
JsonSerializerSettings may include an option to continue after encountering an error. I didn't see anything like that last I looked at their code. I also wouldn't recommend using such an option because recovery from input corruption isn't at all reliable.
Again, I suggest you file a bug at https://github.com/JamesNK/Newtonsoft.Json/issues if you feel that's incorrect.

This is indeed a regular behavior of formatters: they rarely return a partially-constructed object; it's usually all-or-none.
If you instead use MVC's Model Binding feature, you will get partial construction as well as full ModelState describing all the errors.

@Eilon How can i use the MVC's Model Binding feature so that i will get partial construction as well as full ModelState describing all the errors ?

@Rickvanderwaal I don't think you need to do anything special. Action method parameters get bound using model binding by default, which in general will get you partial construction. If you apply the [FromBody] attribute to a parameter, it will use a formatter, and then it's up to the formatter to do whatever it does, which is typically not partial construction.

Well i have a problem related to this issue and i don't see partial construction.
Maybe i should create a new issue.
Let's suppose i have the following model with validation:
public class Car
{
    [Required(ErrorMessage = "Please provide a brand")]
    public string Brand { get; set; }

    [Required(ErrorMessage = "Please provide a color")]
    [MaxLength(10, ErrorMessage = "Color can be maximum 10 characters")]
    public string Color { get; set; }

    [Required(ErrorMessage = "Please provide a price")]
    public int Price { get; set; }
}

The following controller accept this car in the body:
[Route("api/[controller]")]
public class CarController : Controller
{
    [HttpPost]
    public IActionResult CreateCar([FromBody]Car form)
    {
        if (!ModelState.IsValid)
        {
            return BadRequest(ModelState);
        }

         return Ok();
    }
}

When i send the following request, providing a valid brand and  a invalid color and price.
I want to show all the validation errors to the customer.
POST http://localhost:64829/api/car
{
	"brand": "Audi",
	"color": "very dark black",
	"price": ""
}

The response gives me only one error.
{
    "price": [
        "The input was not valid."
    ]
}

When i provide a valid price, then the remaining validation messages showing up.
POST http://localhost:64829/api/car
{
	"brand": "Audi",
	"color": "very dark black",
	"price": "7"
}

Response
{
    "Color": [
        "Color can be maximum 10 characters"
    ]
}

I want to show all the errors to the customer so he can fill the form correctly.
But the response only tell me that the price was not valid.
Also the form given in the CreateCar method is null. I expect that it was filled with the valid remaining data. (partial construction?)
Framework: .NET Core 2.0
When i use .NET 4.6.1 for the same example. I get all the validation errors with the first request.
{
    "Message": "The request is invalid.",
    "ModelState": {
        "form.price": [
            "Error converting value {null} to type 'System.Int32'. Path 'price', line 4, position 13."
        ],
        "form.Color": [
            "Color can be maximum 10 characters"
        ]
    }
}

I do like to hear from you about this issue.

Right, that's pretty much what I described. I suggested not using [FromBody], which will cause it to use model binding instead of formatters.

Thanks for your help. The project is working without [FromBody].
But now i have to use 'application/x-www-form-urlencoded' instead of 'application/json' for the body.
Is there any solution for that?

There's no built-in solution for this that I know of.

Thank you

For 1 year of using Asp.net core I though now on you can only use HttpPost with [FormBody]. This is a true revelation for me 😮


Passing block to super when calling Devise::RegistrationsController::update can give valid resource but not save

Before I take this any further I wanted to make sure I wasn't missing anything. In this example code:
class RegistrationsController < Devise::RegistrationsController
  def update
    super do |resource|
      # doing something after updating
    end
  end
end

I am using the ability to pass a block in as provided here. I found that resource could actually be valid in terms of the resource, but invalid in terms of the request completing because you are required to re-enter your password in order to complete the update. The check for this is actually done in line above:
....
resource_updated = update_resource(resource, account_update_params)
yield resource if block_given?
if resource_updated
...

I wonder if you also need to yield resource_updated, so you would end up with:
yield resource, resource_updated if block_given?

so you would have access to the resource and know whether it was updated OK.

You can always check resource.errors.empty?. I am already not a fan of the super with block syntax, so I am not really inclined to add even more params. :)

@josevalim you're right resource.errors was what I needed, thanks.

For the search engine users: it is important not to call resource.valid?, because that potentially clears the errors devise has set previously. As @josevalim mentions, use resource.errors.empty? or resource.errors.present? instead.


AI Code Reviewer Script Added

Description
The script is called "AI Code Reviewer." Its aim is to analyze and provide feedback on programming code written in the Python programming language. The primary goal of this script is to assist developers in identifying common coding errors, suggesting improvements, and evaluating the overall quality of the code they have written.
Features:

Indentation Error Detection: The script checks for indentation errors in loops, conditionals, and functions. Proper indentation is essential for Python code as it defines the scope and hierarchy of code blocks.

Undefined Variable Detection: It identifies variables that are used but not defined within the code. This helps prevent runtime errors caused by referencing variables that have not been assigned a value.

Code Style Checking: The script uses the pycodestyle library to check for code style violations. Code style refers to the formatting and layout of the code, making it more readable and adhering to standard coding conventions.

Comment Analysis: The script examines code comments to ensure they are well-formatted and provide clear explanations. It suggests improvements for better readability and clarity in the comments.

Fixes #2547
Type of change

[X] New feature

Checklist:

[X] My code follows the style guidelines(Clean Code) of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have created a helpful and easy to understand README.md
[X] My documentation follows Template for README.md
[X] I have added the project meta data in the PR template.
[X] I have created the requirements.txt file if needed.

Project Metadata
Category:

[ ] Calculators
[X] AI/ML
[ ] Scrappers
[ ] Social_Media
[ ] PDF
[ ] Image_Processing
[ ] Video_Processing
[ ] Games
[ ] Networking
[ ] OS_Utilities
[ ] Automation
[ ] Cryptography
[ ] Computer_Vision
[ ] Fun
[ ] Others

Title: AI Code Reviewer Script
Folder: AI Code Reviewer
Script: AI Code Reviewer\ai_code_reviewer.py
Contributor: andoriyaprashant
Description: AI Code Reviewer Script Added

Hey @1e9abhi1e10 please review my pull request
Thank you


Device interview, missing Binary Switch.

zwave-js-ui: 8.9.0
zwave-js: 10.10.0
Hi Everyone, I finally made the move in my homeassitant to migrate from legacy openzwave to zwavejs ui. So far the migration has worked great. However, I have a device that I just can't get to run.
The device is a: "EBV HeatApp! Floor"
Product Manufacturer: 0x017c
Product Identifiers: 0x0006:0x0003
This is actually a simple binary switch on which you can switch 8 relays. Since the migration only one relay can be switched, the other 7 are either not shown at all or sometimes only shown as readable "Binary Switch vundefined" (see picture).
Is there any way how I can get this device fixed? Maybe disabling the interview and adding the 7 missing relays?

node_26.zip
zwave-js-ui-logs.zip
I would be very happy about any help. The device controls my heating, and its currently snowing :-)

Seems no target value is exposed on other switches, also that undefined means the CC version is unknown, I have a feel that the interview may have failed for that device, could you try to re-interview it? Just press on advanced button and select the re-interview action.
cc @AlCalzone

Unfortunately, that would be too easy. I tried it several times, but the other Switches do not get in. I also tried to reset to factory defaults and to reinclude the device again. No success so far.
2023-03-08 11:17:30.898 DEBUG SOCKET: Event ZWAVE_API emitted to fPx9fmvHpsxdSEqgAAAJ
2023-03-08 11:17:30.914 INFO Z-WAVE: Calling api refreshInfo with args: [ 26, { resetSecurityClasses: false }, [length]: 2 ]
2023-03-08 11:17:30.934 INFO Z-WAVE: [Node 026] Interview started
2023-03-08 11:17:30.978 INFO Z-WAVE: Success zwave api call refreshInfo undefined
2023-03-08 11:17:31.076 INFO Z-WAVE: [Node 026] Interview stage PROTOCOLINFO completed
2023-03-08 11:17:31.296 INFO Z-WAVE: [Node 026] Interview stage NODEINFO completed
2023-03-08 11:17:31.560 INFO Z-WAVE: [Node 026] Metadata updated: 114-0-manufacturerId
2023-03-08 11:17:31.576 INFO Z-WAVE: [Node 026] Value added: 114-0-manufacturerId => 380
2023-03-08 11:17:31.582 INFO Z-WAVE: [Node 026] Metadata updated: 114-0-productType
2023-03-08 11:17:31.586 INFO Z-WAVE: [Node 026] Value added: 114-0-productType => 6
2023-03-08 11:17:31.604 INFO Z-WAVE: [Node 026] Metadata updated: 114-0-productId
2023-03-08 11:17:31.612 INFO Z-WAVE: [Node 026] Value added: 114-0-productId => 3
2023-03-08 11:17:31.988 INFO Z-WAVE: [Node 026] Metadata updated: 134-0-libraryType
2023-03-08 11:17:31.995 INFO Z-WAVE: [Node 026] Value added: 134-0-libraryType => 6
2023-03-08 11:17:32.000 INFO Z-WAVE: [Node 026] Metadata updated: 134-0-protocolVersion
2023-03-08 11:17:32.004 INFO Z-WAVE: [Node 026] Value added: 134-0-protocolVersion => 3.67
2023-03-08 11:17:32.014 INFO Z-WAVE: [Node 026] Metadata updated: 134-0-firmwareVersions
2023-03-08 11:17:32.018 INFO Z-WAVE: [Node 026] Value added: 134-0-firmwareVersions => 3.94,1.1
2023-03-08 11:17:32.022 INFO Z-WAVE: [Node 026] Metadata updated: 134-0-hardwareVersion
2023-03-08 11:17:32.026 INFO Z-WAVE: [Node 026] Value added: 134-0-hardwareVersion => 1
2023-03-08 11:17:34.524 ERROR Z-WAVE: [Node 026] Interview FAILED: Attempt 1/5 failed
2023-03-08 11:17:39.871 INFO Z-WAVE: [Node 026] Metadata updated: 37-1-currentValue
2023-03-08 11:17:39.877 INFO Z-WAVE: [Node 026] Value added: 37-1-currentValue => false
2023-03-08 11:17:39.881 INFO Z-WAVE: [Node 026] Metadata updated: 37-1-targetValue
2023-03-08 11:17:40.016 INFO Z-WAVE: [Node 026] Metadata updated: 37-2-currentValue
2023-03-08 11:17:40.037 INFO Z-WAVE: [Node 026] Value added: 37-2-currentValue => false
2023-03-08 11:17:40.044 INFO Z-WAVE: [Node 026] Metadata updated: 37-2-targetValue
2023-03-08 11:17:40.303 INFO Z-WAVE: [Node 026] Metadata updated: 37-3-currentValue
2023-03-08 11:17:40.309 INFO Z-WAVE: [Node 026] Value added: 37-3-currentValue => false
2023-03-08 11:17:40.313 INFO Z-WAVE: [Node 026] Metadata updated: 37-3-targetValue
2023-03-08 11:17:40.440 INFO Z-WAVE: [Node 026] Metadata updated: 37-4-currentValue
2023-03-08 11:17:40.447 INFO Z-WAVE: [Node 026] Value added: 37-4-currentValue => false
2023-03-08 11:17:40.451 INFO Z-WAVE: [Node 026] Metadata updated: 37-4-targetValue
2023-03-08 11:17:40.579 INFO Z-WAVE: [Node 026] Metadata updated: 37-5-currentValue
2023-03-08 11:17:40.590 INFO Z-WAVE: [Node 026] Value added: 37-5-currentValue => false
2023-03-08 11:17:40.596 INFO Z-WAVE: [Node 026] Metadata updated: 37-5-targetValue
2023-03-08 11:17:40.856 INFO Z-WAVE: [Node 026] Metadata updated: 37-6-currentValue
2023-03-08 11:17:40.864 INFO Z-WAVE: [Node 026] Value added: 37-6-currentValue => false
2023-03-08 11:17:40.868 INFO Z-WAVE: [Node 026] Metadata updated: 37-6-targetValue
2023-03-08 11:17:41.004 INFO Z-WAVE: [Node 026] Metadata updated: 37-7-currentValue
2023-03-08 11:17:41.010 INFO Z-WAVE: [Node 026] Value added: 37-7-currentValue => false
2023-03-08 11:17:41.013 INFO Z-WAVE: [Node 026] Metadata updated: 37-7-targetValue
2023-03-08 11:17:41.144 INFO Z-WAVE: [Node 026] Metadata updated: 37-8-currentValue
2023-03-08 11:17:41.150 INFO Z-WAVE: [Node 026] Value added: 37-8-currentValue => false
2023-03-08 11:17:41.156 INFO Z-WAVE: [Node 026] Metadata updated: 37-8-targetValue
2023-03-08 11:17:41.278 INFO Z-WAVE: [Node 026] Value updated: 37-3-currentValue false => false
2023-03-08 11:17:41.461 INFO Z-WAVE: [Node 026] Metadata updated: 37-0-targetValue
2023-03-08 11:17:41.483 INFO Z-WAVE: [Node 026] Metadata updated: 112-0-1
2023-03-08 11:17:41.488 INFO Z-WAVE: [Node 026] Metadata updated: 112-0-2
2023-03-08 11:17:41.710 INFO Z-WAVE: [Node 026] Value added: 112-0-1 => 240
2023-03-08 11:17:41.895 INFO Z-WAVE: [Node 026] Value added: 112-0-2 => 0
2023-03-08 11:17:41.909 INFO Z-WAVE: [Node 026] Interview stage COMMANDCLASSES completed
2023-03-08 11:17:41.913 INFO Z-WAVE: [Node 026] Interview stage OVERWRITECONFIG completed
2023-03-08 11:17:41.916 INFO Z-WAVE: [Node 026] Interview stage COMPLETE completed
2023-03-08 11:17:41.927 INFO Z-WAVE: [Node 026] Value added 26-112-0-1 => 240
2023-03-08 11:17:41.929 INFO Z-WAVE: [Node 026] Value added 26-112-0-2 => 0
2023-03-08 11:17:41.930 INFO Z-WAVE: [Node 026] Value added 26-114-0-manufacturerId => 380
2023-03-08 11:17:41.931 INFO Z-WAVE: [Node 026] Value added 26-114-0-productType => 6
2023-03-08 11:17:41.932 INFO Z-WAVE: [Node 026] Value added 26-114-0-productId => 3
2023-03-08 11:17:41.934 INFO Z-WAVE: [Node 026] Value added 26-134-0-libraryType => 6
2023-03-08 11:17:41.935 INFO Z-WAVE: [Node 026] Value added 26-134-0-protocolVersion => 3.67
2023-03-08 11:17:41.936 INFO Z-WAVE: [Node 026] Value added 26-134-0-firmwareVersions => 3.94,1.1
2023-03-08 11:17:41.938 INFO Z-WAVE: [Node 026] Value added 26-134-0-hardwareVersion => 1
2023-03-08 11:17:41.946 INFO Z-WAVE: [Node 026] Value added 26-37-3-currentValue => false
2023-03-08 11:17:41.947 INFO Z-WAVE: [Node 026] Value added 26-37-3-targetValue => undefined
2023-03-08 11:17:41.949 INFO Z-WAVE: [Node 026] Ready: EbV - heatapp! floor (heatapp! floor is a controller for thermal actuators in underfloor heating installations and is part of the heatapp! system, providing individual circ)
2023-03-08 11:17:41.965 INFO Z-WAVE: [Node 026] Interview COMPLETED, all values are updated

What surprises me is that during the interview the line "[Node 026] Interview FAILED: Attempt 1/5 failed" appears every time. Apart from that, all targetValue entries are listed in the log, but still don't seem to end up in the config.

Unfortunately, I have tried this several times. Resetting the device to factory settings did not help either.
2023-03-08 11:17:30.898 DEBUG SOCKET: Event ZWAVE_API emitted to fPx9fmvHpsxdSEqgAAAJ
2023-03-08 11:17:30.914 INFO Z-WAVE: Calling api refreshInfo with args: [ 26, { resetSecurityClasses: false }, [length]: 2 ]
2023-03-08 11:17:30.934 INFO Z-WAVE: [Node 026] Interview started
2023-03-08 11:17:30.978 INFO Z-WAVE: Success zwave api call refreshInfo undefined
2023-03-08 11:17:31.076 INFO Z-WAVE: [Node 026] Interview stage PROTOCOLINFO completed
2023-03-08 11:17:31.296 INFO Z-WAVE: [Node 026] Interview stage NODEINFO completed
2023-03-08 11:17:31.560 INFO Z-WAVE: [Node 026] Metadata updated: 114-0-manufacturerId
2023-03-08 11:17:31.576 INFO Z-WAVE: [Node 026] Value added: 114-0-manufacturerId => 380
2023-03-08 11:17:31.582 INFO Z-WAVE: [Node 026] Metadata updated: 114-0-productType
2023-03-08 11:17:31.586 INFO Z-WAVE: [Node 026] Value added: 114-0-productType => 6
2023-03-08 11:17:31.604 INFO Z-WAVE: [Node 026] Metadata updated: 114-0-productId
2023-03-08 11:17:31.612 INFO Z-WAVE: [Node 026] Value added: 114-0-productId => 3
2023-03-08 11:17:31.988 INFO Z-WAVE: [Node 026] Metadata updated: 134-0-libraryType
2023-03-08 11:17:31.995 INFO Z-WAVE: [Node 026] Value added: 134-0-libraryType => 6
2023-03-08 11:17:32.000 INFO Z-WAVE: [Node 026] Metadata updated: 134-0-protocolVersion
2023-03-08 11:17:32.004 INFO Z-WAVE: [Node 026] Value added: 134-0-protocolVersion => 3.67
2023-03-08 11:17:32.014 INFO Z-WAVE: [Node 026] Metadata updated: 134-0-firmwareVersions
2023-03-08 11:17:32.018 INFO Z-WAVE: [Node 026] Value added: 134-0-firmwareVersions => 3.94,1.1
2023-03-08 11:17:32.022 INFO Z-WAVE: [Node 026] Metadata updated: 134-0-hardwareVersion
2023-03-08 11:17:32.026 INFO Z-WAVE: [Node 026] Value added: 134-0-hardwareVersion => 1
2023-03-08 11:17:34.524 ERROR Z-WAVE: [Node 026] Interview FAILED: Attempt 1/5 failed
2023-03-08 11:17:39.871 INFO Z-WAVE: [Node 026] Metadata updated: 37-1-currentValue
2023-03-08 11:17:39.877 INFO Z-WAVE: [Node 026] Value added: 37-1-currentValue => false
2023-03-08 11:17:39.881 INFO Z-WAVE: [Node 026] Metadata updated: 37-1-targetValue
2023-03-08 11:17:40.016 INFO Z-WAVE: [Node 026] Metadata updated: 37-2-currentValue
2023-03-08 11:17:40.037 INFO Z-WAVE: [Node 026] Value added: 37-2-currentValue => false
2023-03-08 11:17:40.044 INFO Z-WAVE: [Node 026] Metadata updated: 37-2-targetValue
2023-03-08 11:17:40.303 INFO Z-WAVE: [Node 026] Metadata updated: 37-3-currentValue
2023-03-08 11:17:40.309 INFO Z-WAVE: [Node 026] Value added: 37-3-currentValue => false
2023-03-08 11:17:40.313 INFO Z-WAVE: [Node 026] Metadata updated: 37-3-targetValue
2023-03-08 11:17:40.440 INFO Z-WAVE: [Node 026] Metadata updated: 37-4-currentValue
2023-03-08 11:17:40.447 INFO Z-WAVE: [Node 026] Value added: 37-4-currentValue => false
2023-03-08 11:17:40.451 INFO Z-WAVE: [Node 026] Metadata updated: 37-4-targetValue
2023-03-08 11:17:40.579 INFO Z-WAVE: [Node 026] Metadata updated: 37-5-currentValue
2023-03-08 11:17:40.590 INFO Z-WAVE: [Node 026] Value added: 37-5-currentValue => false
2023-03-08 11:17:40.596 INFO Z-WAVE: [Node 026] Metadata updated: 37-5-targetValue
2023-03-08 11:17:40.856 INFO Z-WAVE: [Node 026] Metadata updated: 37-6-currentValue
2023-03-08 11:17:40.864 INFO Z-WAVE: [Node 026] Value added: 37-6-currentValue => false
2023-03-08 11:17:40.868 INFO Z-WAVE: [Node 026] Metadata updated: 37-6-targetValue
2023-03-08 11:17:41.004 INFO Z-WAVE: [Node 026] Metadata updated: 37-7-currentValue
2023-03-08 11:17:41.010 INFO Z-WAVE: [Node 026] Value added: 37-7-currentValue => false
2023-03-08 11:17:41.013 INFO Z-WAVE: [Node 026] Metadata updated: 37-7-targetValue
2023-03-08 11:17:41.144 INFO Z-WAVE: [Node 026] Metadata updated: 37-8-currentValue
2023-03-08 11:17:41.150 INFO Z-WAVE: [Node 026] Value added: 37-8-currentValue => false
2023-03-08 11:17:41.156 INFO Z-WAVE: [Node 026] Metadata updated: 37-8-targetValue
2023-03-08 11:17:41.278 INFO Z-WAVE: [Node 026] Value updated: 37-3-currentValue false => false
2023-03-08 11:17:41.461 INFO Z-WAVE: [Node 026] Metadata updated: 37-0-targetValue
2023-03-08 11:17:41.483 INFO Z-WAVE: [Node 026] Metadata updated: 112-0-1
2023-03-08 11:17:41.488 INFO Z-WAVE: [Node 026] Metadata updated: 112-0-2
2023-03-08 11:17:41.710 INFO Z-WAVE: [Node 026] Value added: 112-0-1 => 240
2023-03-08 11:17:41.895 INFO Z-WAVE: [Node 026] Value added: 112-0-2 => 0
2023-03-08 11:17:41.909 INFO Z-WAVE: [Node 026] Interview stage COMMANDCLASSES completed
2023-03-08 11:17:41.913 INFO Z-WAVE: [Node 026] Interview stage OVERWRITECONFIG completed
2023-03-08 11:17:41.916 INFO Z-WAVE: [Node 026] Interview stage COMPLETE completed
2023-03-08 11:17:41.927 INFO Z-WAVE: [Node 026] Value added 26-112-0-1 => 240
2023-03-08 11:17:41.929 INFO Z-WAVE: [Node 026] Value added 26-112-0-2 => 0
2023-03-08 11:17:41.930 INFO Z-WAVE: [Node 026] Value added 26-114-0-manufacturerId => 380
2023-03-08 11:17:41.931 INFO Z-WAVE: [Node 026] Value added 26-114-0-productType => 6
2023-03-08 11:17:41.932 INFO Z-WAVE: [Node 026] Value added 26-114-0-productId => 3
2023-03-08 11:17:41.934 INFO Z-WAVE: [Node 026] Value added 26-134-0-libraryType => 6
2023-03-08 11:17:41.935 INFO Z-WAVE: [Node 026] Value added 26-134-0-protocolVersion => 3.67
2023-03-08 11:17:41.936 INFO Z-WAVE: [Node 026] Value added 26-134-0-firmwareVersions => 3.94,1.1
2023-03-08 11:17:41.938 INFO Z-WAVE: [Node 026] Value added 26-134-0-hardwareVersion => 1
2023-03-08 11:17:41.946 INFO Z-WAVE: [Node 026] Value added 26-37-3-currentValue => false
2023-03-08 11:17:41.947 INFO Z-WAVE: [Node 026] Value added 26-37-3-targetValue => undefined
2023-03-08 11:17:41.949 INFO Z-WAVE: [Node 026] Ready: EbV - heatapp! floor (heatapp! floor is a controller for thermal actuators in underfloor heating installations and is part of the heatapp! system, providing individual circ)
2023-03-08 11:17:41.965 INFO Z-WAVE: [Node 026] Interview COMPLETED, all values are updated

What surprises me is that during the interview the line "[Node 026] Interview FAILED: Attempt 1/5 failed" appears every time. Apart from that, all targetValue entries are listed in the log, but still don't seem to end up in the config.

Please make a driver log of a re-interview, loglevel debug and attach it here as a file (drag & drop into the text field).

zwavejs_2023-03-08.zip
Sorry, forgot to activate Debug Level before.

Ok that's an ahem interesting behavior...
The device responds that it has 8 endpoints. When queried which endpoints it has (they don't always have to be sequential), it first responds that it has a single endpoint no. 11. When queried for that endpoint's capabilities, it doesn't respond (I assume because the endpoint does not exist).
As a result, the interview aborts and restarts. This time it claims that it has a single endpoint no. 3.


Add possibility to set nameId NameQualifier attribute in SLO Request

Hello,
I added possibility to set nameId NameQualifier attribute in SLO Request. This is required at least in case of IdP implemented using Lasso because if the NameQualifier attribute is not defined, the request will be recognized as invalided. For the same purpose, I add possibility to retrieve NameQualifier attribute in the IdP Response.

Can you add as well unit tests?

I had some unit tests to cover this new features. I survey Travis result to fix it in case of problem.

Thanks for the feature and for fixing the travis issue!


Font size inconsistent

ylabel font size is bigger than in other plots
could you please use a global variable so the font size can be defined not at each plot individually, but using a global variable

I managed to add variables for the font-sizes: 23d2a82380d2f6f06bac48c0192cc5d2dcc2c0ec


strike_lookup when used in strike_modal throws an exception on focus

If I use a strike_lookup in a strike_modal window, then as soon as I move my cursor to the lookup field I get the following error:
Uncaught Error in $A.getCallback() [Cannot convert undefined or null to object]
Screen shot is attached.

Here the markup of the component where I am using both:
<c:strike_modal aura:id="editModalWindow" title="Edit Support Information"
primaryButtonLabel="Save" secondaryButtonLabel="Cancel">
<aura:set attribute="body">

<lightning:textarea name="criticalInfo" variant="label-hidden"
placeholder="Enter support information"
value="{!v.criticalInfoEdit}"/>
<c:strike_lookup label="Account"
object="Account"
searchField="Name"
placeholder="Select an option"
iconName="standard:account"
subtitleField="Industry"
order="Name"
limit="5"
loadingMessage="Loading..."
errorMessage="Invalid input"/>

</aura:set>
</c:strike_modal>

Same error is coming when I add an anchor tag  to the modal window body

Hi @Simran-Sohal. Thanks for logging this. First, try removing the <aura:set> tags completely from the markup. <aura:set> is not necessary for strike components. Then it appears that the issue is not with <strike_lookup> but with lightning:textarea. I will continue to explore why that is interfering with the modal, but for now, you can convert lightning:textarea to a standard textarea, which worked for me.

Oh. I see. When using lightning:textarea, label is a required attribute. So add a label and remove aura:set and see if that fixes it.

Hi @trentchilders ... thanks for getting back to me. I will try the suggested solution and let you know.

I'm running into the same issue. In my case, the line that caused the issue was in strike_modalHelper.js:42:
if(!$A.util.isEmpty(el) && el.id == params.targetEl){

By commenting out the first part of the conditional things seemed to work as expected:
if(el.id == params.targetEl){

Somehow el is considered "empty" even though it has properties (including the id that's being checked in the remaining part of the conditional).

Hi @trentchilders ... still the error is there
Same error is coming when I add an anchor tag to the modal window body. As soon as I hover on the link created by anchor tagI get the error.

After fixing the issue with my line change above, I hit a second problem, this time on the lookup itself (instead of the modal component). There's an error in the function handleFocusIndexChange in strike_lookupController.js:118. In the case where the lookup is in a modal, lookupMenu can actually be null on the first focus event, so the fix is to check to ensure lookupMenu is not null before continuing in the function:
handleFocusIndexChange: function(component, event, helper) {
        var focusIndex = component.get('v.focusIndex');
        var lookupMenu = component.find('lookupMenu').getElement();

        if(lookupMenu != null) {
            var options = lookupMenu.getElementsByTagName('li');
            ...
        }

I'm not getting this error on my end. Maybe this is browser related. Which browser are you using? @pauljrooney @Simran-Sohal

I’m using the newest version of Chrome.

On Aug 28, 2017, at 1:22 PM, trentchilders<EMAIL_ADDRESS>wrote:
I'm not getting this error on my end. Maybe this is browser related. Which browser are you using? @pauljrooney @Simran-Sohal
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I am using Chrome as well

And are you both using the strik_modal version 0.9.0. That's the most recent release and the code that @pauljrooney has above does not match up with the current version. If you aren't using the most recent version, try upgrading and see if that fixes it.

@trentchilders - I was able to replicate Paul & Simran's issues in version 0.9.0 as well as fix them with the lines below.
FWIW - We were getting the error on a strike_modal that was opened from the "strike_evt_addNewRecord" event of a strike_lookup. The strike_lookup itself was not in a strike_modal at all. Seems like the issue for us was related to the contents of that strike_modal - Maybe because some of those contents did not have an aura:id set? Or maybe because that strike_modal was conditionally displayed using an aura:if?
strike_lookupController.js:122
var lookupMenu = component.find('lookupMenu').getElement();
if (lookupMenu != null) {
    ...
}

strike_modalHelper.js:48
var el = e.srcElement;
if (el != null) {
    ...
}

I believe I'm using 0.9.0, though it's slightly challenging to ensure I'm updated across the board using the strike cli.
In my case, the modal contained an aura:if, not sure if it's related.


fix: signedURL cname (#210)

Fixes #210

[X] Tests and linter pass
[X] Code coverage does not decrease (if any source code was changed)
[X] Appropriate docs were updated (if necessary)

I signed it!

Awesome, thank you!


Use a base toml

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (849b72b) 23.17% compared to head (de51ae0) 23.17%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #754   +/-   ##
=======================================
  Coverage   23.17%   23.17%
=======================================
  Files          33       33
  Lines        4293     4293
=======================================
  Hits          995      995
  Misses       3197     3197
  Partials      101      101

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Upgrade the CDI TCK for the Jakarta EE Core TCK Runner to 4.0.12

Once https://github.com/jakartaee/specifications/pull/659 has been merged, we should be able to upgrade the CDI TCK in the wf-core-tck-runner to 4.0.12.
This includes https://github.com/jakartaee/cdi-tck/issues/485 which will allow the WildFly to pass the Jakarta EE Core TCK with Java 21.
As part of this, we should add Java 21 TCK testing to the CI job.

This is currently semi-blocked by https://github.com/jakartaee/platform/issues/763. We can still upgrade the TCK, but we can't pass with Java 21.


chirpstack-gateway-bridge doesn't seem to be up

Hi,
I have used the docker-compose.yml to setup my docker environment through docker-compose. Although everything seems to be up and running, the chirpstack-gateway-bridge is not up. The docker yes, but not the service inside the docker.
For simplicity I have run only bridge and mosquito, i.e.
docker-compose up chirpstack-gateway-bridge
With docker ps I have:
CONTAINER ID   IMAGE                                         COMMAND                  CREATED          STATUS          PORTS                                       NAMES
0246623d4ae2   docker-chirpstack_chirpstack-gateway-bridge   "/usr/bin/chirpstack…"   44 minutes ago   Up 20 minutes   <IP_ADDRESS>:1700->1700/udp, :::1700->1700/udp   docker-chirpstack_chirpstack-gateway-bridge_1
a2663bda40d9   eclipse-mosquitto:2                           "/docker-entrypoint.…"   44 minutes ago   Up 21 minutes   <IP_ADDRESS>:1883->1883/tcp, :::1883->1883/tcp   docker-chirpstack_mosquitto_1
symeon@debian:/media/extra_partition/MyProjects/MbedPrograms/Prototypes/server-prototype-environment$

I login to mosquito container with nmap installed:
docker exec -u 0 -it a2663bda40d9 /bin/sh
Starting Nmap 7.80 ( https://nmap.org ) at 2021-07-11 17:25 UTC
Nmap scan report for localhost (<IP_ADDRESS>)
Host is up (0.0000090s latency).
Other addresses for localhost (not scanned): ::1
Not shown: 65499 closed ports
PORT     STATE SERVICE
1883/tcp open  mqtt

And then I login to bridge:
docker exec -u 0 -it 0246623d4ae2 /bin/sh
 nmap localhost -p 1-65535
Starting Nmap 7.91 ( https://nmap.org ) at 2021-07-11 17:26 UTC
Nmap scan report for localhost (<IP_ADDRESS>)
Host is up (0.0000080s latency).
Other addresses for localhost (not scanned): ::1
All 65535 scanned ports on localhost (<IP_ADDRESS>) are closed

Nmap done: 1 IP address (1 host up) scanned in 1.27 second

The bridge doesn't seem to be up...Is it a bug or should I do anything else?
In https://github.com/brocaar/chirpstack-docker/blob/master/configuration/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
I have tried also to use the ip of the mosquito container which in my case was
[integration.mqtt.auth.generic]
servers=["tcp://<IP_ADDRESS>:1883"]     | instead of tcp://mosquitto:1883
username=""
password=""

But again nothing is up

Are you sure you are scanning for UDP ports?
https://nmap.org/book/scan-methods-udp-scan.html

Hi @brocaar
You're very right...I didn't notice it's UDP.
Thanks
Cheers


Vladimir vs volodymyr token info Build #28207  ( Still haven not got any reply )

Having problem with pushing my token name update , running into automerge build issue . RUN YARN TEST
Error: Process completed with exit code 1.

what's your PR?

#20664 opened 7 days ago by cariocc

what's your PR?

Trying to find solution for days already... Not so familiar with github as well but already tried everything i could by running commands on dekstop version etc. (maybe even messed up it more)

This PR has two problems

Duplicate token: https://github.com/solana-labs/token-list#duplicate-token (you already added this token and should edit the existing token you added rather than creating it again)
you edited vscode settings file, which you shouldn't touch

try again with a fresh copy of the solana token list repo. find your vvv token and edit it only instead of adding it again at the end.


[FLINK-2126] Fixed Flink scala shell ITSuite sporadic failures

Add-numbers from 1..10 now does not check for "Job execution switched to status FINISHED.", which sometimes was not printed.
Fixed typo in add numbers test

Can you just remove the commented lines? And I think that we should also remove the check from the other tests.
From @tillrohrmann: the issue with the LOG file not being created is a separate issue. Till, do we have an issue for that one? Is this the only tests, which runs with scalatest or why does it not affect other tests?

We haven't created an issue for the logging file, yet. Will do. The
flink-scala-shell and the flink-ml modules use the scalatest maven plugin.
The fix should be easy, though. Simply give these two modules a different
travis log4j properties file where you don't depend on the fork number.
On Wed, Jun 3, 2015 at 7:13 PM, Ufuk Celebi<EMAIL_ADDRESS>wrote:

Can you just remove the commented lines? And I think that we should also
remove the check from the other tests.
From @tillrohrmann https://github.com/tillrohrmann: the issue with the
LOG file not being created is a separate issue. Till, do we have an issue
for that one? Is this the only tests, which runs with scalatest or why does
it not affect other tests?
—
Reply to this email directly or view it on GitHub
https://github.com/apache/flink/pull/768#issuecomment-108527888.

Ok, removed the comments and the "Job execution switched to status FINISHED." for all tests now (although, till now it only happened in the "add numbers" Tests.)

+1
Having the correct result is the main validation we need.
Merging this...

...merge race :D Can you change the commit msg to include the issue ID please?

Changed to include the issue ID, 3..2..1 GO !


Removed object deletes from the drop_database call

Is this pull request going to be reviewed?

Note that I did not update the tests (I couldn't get them running) so someone will need to update the unit tests for this change

closing this PR for inactivity. Please feel free to comment to reopen.

I can confirm this fixes the issue #238 why wasn't merged?

Would you like to take this up?  Could you please write unit test cases so that i can merge?


segfault if function modules are not loaded

if the function module is not loaded you get a segfault when running
# gt func create cyberkey mass_storage usb0
(when usb_f_mass_storage) is not loaded, likewise with hid

@xzcvczx could you compile libusbgx/gt with debug symbols and provide the traceback?
Use this command to get the traceback:
gdb -batch -n -ex 'set pagination off' -ex run -ex bt -ex 'bt full' --args gt func create cyberkey mass_storage usb0