Azure task "sfpwowerscript-installsfdx-task@6" fails with "##[error]Command failed: sfdx plugins:install sfpowerkit@latest"

I just installed latest version sfpowerscripts in Azure devops : 13.8000.9 (Latest)
I ran the task sfpwowerscript-installsfdx-task@6
And it fails with :
Installing Plugin sfpowerkit@latest
'sfdx' is not recognized as an internal or external command,
operable program or batch file.
##[error]Command failed: sfdx plugins:install sfpowerkit@latest
'sfdx' is not recognized as an internal or external command,
operable program or batch file.

Can you let me know which agent you are running this on?

Hi,
Windows server 2019
vsts-agent-win-x64-2.168.2
node v12.16.3
Let me know if you want some more informations...

Are you using a microsoft hosted agent or self hosted agent?

Host is a VM on MS Azure

@ggciteo Can you confirm whether npm and yarn is installed in your host?

@aly76  We will have to add a prerequisite check and show proper error messages

I installed only npm, as I got an error message saying npm is lacking.
I was thinking yarn is no use...
So, I just installed yarn, and still the same error message.

I am not sure what is causing it, i think the best course of action is to skip this task and install the sfdx cli and the sfpowerkit plugin manually.
My guess it could be related to permissions as these are tried to be install globally
Sent from Outlook Mobilehttps://aka.ms/blhgte

From: ggciteo<EMAIL_ADDRESS>Sent: Sunday, May 24, 2020 6:14:15 AM
To: Accenture/sfpowerscripts<EMAIL_ADDRESS>Cc: Abdulsalam, Azlam<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: [External] Re: [Accenture/sfpowerscripts] Azure task "sfpwowerscript-installsfdx-task@6" fails with "##[error]Command failed: sfdx plugins:install sfpowerkit@latest" (#17)
This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments.

I installed only npm, as I got an error message saying npm is lacking.
I was thinking yarn is no use...
So, I just installed yarn, and still the same error message.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Accenture_sfpowerscripts_issues_17-23issuecomment-2D633131163&d=DwMCaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=1gQkLqWJ0FVakrZpcYuRfbSfKnJcxUN9BD1bMOCTMSA&m=l2f3PJ1b4rBNzqT7jOLemUINebvr8Hr9RU7qwUpbIhM&s=J-A6vFokrSmH_t9wIbmwqzbJV0w5i6jiwZVgB4AaDC8&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AKN5RJEGL7IUNMTR642ERCLRTAVBPANCNFSM4NFFB6DQ&d=DwMCaQ&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=1gQkLqWJ0FVakrZpcYuRfbSfKnJcxUN9BD1bMOCTMSA&m=l2f3PJ1b4rBNzqT7jOLemUINebvr8Hr9RU7qwUpbIhM&s=9GRrQXKtncIYhZx65WHdWN7XBuBElTvm16XMIJD8OQc&e=.

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.

www.accenture.com

Hi there,
It works if I install sfdx manually.
It then install sfpowerscript automatically.


Add toString() to all classes

Please implement toString() in all classes.  This will help when debugging since the programmer can see what the state of the object is.

Did you have classes in particular packages in mind, or all of them?

All of them.
I was stepping through code that was calling RetryPolicyBuilder.  It would be nice to see the state in the debugger to make sure I got the code right.  I know I can expand the object and see it's fields, but this interrupts my flow.
Note: RetryPolicyImpl does not have any state except RetryPolicyConfig.  So, this would be the implementation of RetryPolicyImpl.toString().
@Override
public String toString() {
   return config.toString();
}

However, RetryPolicyConfig has a lot of state.  So, perhaps toString() only returns the values that are set.  For example, if jitter is not set, then toString() won't show it.

The easiest solution to make it done in five minutes :-)
https://projectlombok.org/features/ToString


Remote explorer showing more than 1 view at the time (though one is dead)

Not sure how I got into this state exactly, but I did have both a Codespace and a WSL session open. I closed the WSL session, and went back to the Codespace and saw this:

The GitHub Codespaces view seems dead -- refresh doesn't do anything, while the WSL view seems to work.
If I switch views via the dropdown, then it fixed things.
I also for some reason seem to have 2 Codespaces items in the dropdown:

The GitHub Codespaces one works, while the other wants me to sign in via the Azure account extension (which isn't installed)

The two Codespaces is probably because you have the old Visual Studio Codespaces extension installed.

I can repro the extra views showing.

Wrong issue tagged in the commit!


5.9: [SemanticARCOpts] Don't shorten owned lexical values lifetimes through deinit barriers.

Cherry-pick of https://github.com/apple/swift/pull/65164 .
Prevent joining lifetimes of copies with destroyed owned lexical values if there may be deinit barriers between the final consume of the copy and the destroy of the lexical value.
rdar://108014714

@swift-ci please test

@swift-ci please test macos platform


TemboCoin logo and smart contract.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

[ ] Filename in the lowercase format
[ ] Image format: png
[ ] Image size: 256 by 256 px

TemboCoin smart contract: 0x1de09690e0d3c75c22cd19acc1aebde46bbc7d25

Added here https://github.com/TrustWallet/tokens/commit/5b6f6314ae77813c2bb481b3aa0a1ee048bedebf
Also, you can use these graphics to say that your ERC20 token fully compatible with Trust Wallet (https://trustwalletapp.com/logo-assets). Tokens will show up automatically once the user receives them.
Feel free to share this on social media and tag Trust Wallet:

Twitter: @trustwalletapp

Facebook: @trustwalletapp

so its already listed wright?


table_bloat : fails with PG 12

psql:/tmp/check_pga-42bdwtPa:49: ERROR: column tbl.relhasoids does not exist LINE 34: + CASE WHEN tbl.relhasoids THEN 4 ELSE 0... ^

TODO : Update from the last version from the query: https://github.com/ioguix/pgsql-bloat-estimation/blob/master/table/table_bloat.sql
I'm just wondering if I create a whole new query for v12 (safe way) or if I update the current one (>9.0).

As discussed with ioguix: new query version only for v12

See PR #239


If the proxy parameters are wrong, exceptions are thrown. Is there a way to catch these exceptions and show to the user that what went wrong?

The users sometimes accidently put wrong data in proxy. Is it possible to catch these exceptions?

Sorry ..l listed on wrong page


patched out sleep

Patches out the time.sleep and mocks the time.time to one second ahead
resolves #2239

Automated message from Dropbox CLA bot
@jQwotos, it looks like you've already signed the Dropbox CLA. Thanks!

Hi @jQwotos thanks for the pull request! I need to look at this area of the code a bit before I review your change, I'm not familiar with it.
While I do that, can you edit your commit message? The style guide describes how commit messages for Zulip should be written, the first line should be a complete sentence and in present tense. (An example would be "Add new foo option in function_bar.") Also the github issue link should be the last line in the message.
 Since you've pushed the branch to github, you will also have to --force to update it there. You can find information on doing this here: https://help.github.com/articles/changing-a-commit-message. If you have any questions, please ask us in chat! Someone will be there to help if you need it.
If you would like to see some additional examples of commit messages, there are some here: https://zulip.readthedocs.io/en/latest/version-control.html#commit-messages
Thanks!

I've changed updated the msg and moved the issue link to the bottom @feorlen . Could you please give me feedback about what you think.

Thanks for editing the message. The new wording for the summary is great, it clearly describes the purpose of the change. But it looks like the rest of the description is only in the pull request rather than the commit. I only see the first line of the commit message when I view the commit itself. Can you look into that?
I have other one super-nitpick comment on the message, the Zulip style is to capitalize the beginning and have a period at the end. (You are likely going to be editing the commit message again anyway.)
I asked for a second opinion on reviewing the code, I don't know enough about tests yet and I saw one of the other mentors noted that this bug might be deceptively not simple. I'm not confident in pronouncing it done on my own.

@feorlen I updated the commit description and the pr comment. Thanks for all the tips about properly naming and styling. Feel free to tell me if there is anything else that I should look into.

Awesome, this looks great!  Merged, thanks @jQwotos!  This made the overall Zulip test suite about 2% faster on my computer, which is pretty good given that we have over 1000 tests :).


Daily backup feature

I would like teslamate to supply an automated backup feature. I'm running it off my Pi and the SD cards are known to fail at random times.
I would like that the daily backup supports sending the backup files to a remote location. This could be S3, ssh or something else.

There are already several solutions to this problem: https://github.com/search?q=docker+postgres+s3+backup It does not require a built-in TeslaMate feature.


Admin panel that works with Orator

Hello guys, this isn't really an issue, but this place is like the only community Orator-orm currently has. My question is: Is there any admin panel like Flask-admin that works with orator just like we have for pewee and sql-alchemy

no comment?

@tantita As far as I know, there's no official support from the biggest admin libs right now. Unfortunately. :cry:


Calendar shows wrong week numbers

I'm using the default calendar format  from man waybar-clock and I think the week numbers are wrong. Unless I'm missing something, the week number of the last week of the month should repeat at the first week of the following month (unless the first day of the month is a Sunday). However, currently the week number of the first and second weeks of the month repeat (if month doesn't start on a Sunday) and every month gets a new first week number.
      "calendar": {
                  "mode"          : "year",
                  "mode-mon-col"  : 3,
                  "weeks-pos"     : "right",
                  "on-scroll"     : 1,
                  "on-click-right": "mode",
                  "format": {
                              "months":     "{}",
                              "days":       "{}",
                              "weeks":      "W{}",
                              "weekdays":   "{}",
                              "today":      "{}"
                              }
            }

Hi @J0nnyMak0 , can you please share additional info:

date '+%c'
echo $LANG
waybar --version
uname -a
Please provide here the whole block for clock module

Hi @J0nnyMak0 , can you please share additional info:

date '+%c'

Wed 19 Jul 2023 10:13:02 AM CDT

echo $LANG

en_US.UTF-8

waybar --version

Waybar v0.9.19-39-g1e2b9cb5 (branch 'master')

uname -a

Linux jonmhome 6.4.3-arch1-2 #1 SMP PREEMPT_DYNAMIC Sat, 15 Jul 2023 19:25:49 +0000 x86_64 GNU/Linux

Please provide here the whole block for clock module

        "clock": {
                "timezone": "America/Chicago",
                "format": "{:%a}",
                "tooltip-format": "<tt>{calendar}</tt>",
                "calendar": {
                  "mode"          : "year",
                  "mode-mon-col"  : 3,
                  "weeks-pos"     : "right",
                  "on-scroll"     : 1,
                  "on-click-right": "mode",
                  "format": {
                              "months":     "{}",
                              "days":       "{}",
                              "weeks":      "W{}",
                              "weekdays":   "{}",
                              "today":      "{}"
                              }
               }
        }

I reproduced the same issue in my machine. Need to take some time to clarify how your case should be look like. Now I suspect 3-rd party library is used by waybar calendar provides not ocrrect result. Utility  date  shows me correct results.... so . Will reply once I've got a clear vision on the case

So... issue is found. But... needs to think now how to handle. It appears due to calendar for it's need uses date::sys_days typedef... which represents time point in UTC... Where there's another time point structure date::local_days which represents time point associated with timezone... I guess I'll provide new implementation.... Will notify once it's done.
Thank you

I have the same problem as @randomn4me.
    "clock#date": {
        "format": "  {:%a. %d. %b. %Y}",
        "tooltip-format": "<tt>{calendar}</tt>",
        "locale": "en_GB.UTF-8",
        "calendar": {
            "mode": "month",
            "weeks-pos": "left",
            "on-scroll": 1,
            "format": {
                      "months": "{}",
                      "days": "{}",
                      "weeks": "W{}",
                      "weekdays": "{}",
                      "today": "{}"
            }
        },
        "actions":  {
            "on-scroll-up": "shift_down",
            "on-scroll-down": "shift_up"
        }
    },

~ > date '+%c'
Fri 19 Jan 2024 10:21:47 AM CET
~ > echo $LANG
en_US.UTF-8
~ > waybar --version
Waybar v0.9.24
~ > uname -a
Linux desktop 6.6.11-200.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Jan 10 19:25:59 UTC 2024 x86_64 GNU/Linux


Error  - FormEditor.SqlIndex.Storage.Index

I have undocumented the FormEditor.config line to enable SQLIndex, I get this error.
Am I missing something? Is this not included in the Core?
Could not load custom Index type (requested content ID: 4610)
System.Configuration.ConfigurationErrorsException: Custom Index type "FormEditor.SqlIndex.Storage.Index, FormEditor.SqlIndex" could not be found
at FormEditor.Configuration.Load()

@kjac
Definitly, I would add a note to the documentation section...

Hey @eriksimonic,
It's in the docs already: https://github.com/kjac/FormEditor/blob/master/Docs/storage.md#changing-the-storage-index
But for clarity I'll add a note to FormEditor.config too :)


Cache generated rustdoc for registry baselines

This implements the suggestion discussion in https://github.com/obi1kenobi/cargo-semver-checks/issues/214. It turned out surprisingly simple :)

I've tested it locally on the rust-libp2p repository. It works after a cargo clean and cleans up after itself. A subsequent run detects the cached file and reuses it which speeds up things a fair bit.

@thomaseizinger if I were to release 0.18 with this caching change soon, when would be the best time for you? I'd love to have you onboard to test it in "the real world" as soon as it comes out, in case something doesn't behave quite as well as we had hoped.

@thomaseizinger if I were to release 0.18 with this caching change soon, when would be the best time for you? I'd love to have you onboard to test it in "the real world" as soon as it comes out, in case something doesn't behave quite as well as we had hoped.

We can test it as soon as there is a binary. Why don't we release 0.18.0-alpha and we use that in our CI for a bit?

@thomaseizinger if I were to release 0.18 with this caching change soon, when would be the best time for you? I'd love to have you onboard to test it in "the real world" as soon as it comes out, in case something doesn't behave quite as well as we had hoped.

We can test it as soon as there is a binary. Why don't we release 0.18.0-alpha and we use that in our CI for a bit?

I am gonna be on NZ timezone for the next two weeks. With a pre-release, I can adjust our CI to create a cache on master and use that on PR workflow runs and play around what happens when we nuke the cache etc.

@obi1kenobi it would be good to first merge #340 before creating the alpha release, since it touched some of this PR's code.


ContainerProperties setSyncCommits javadoc

	 * Set whether or not to call consumer.commitSync() or commitAsync() when the
	 * container is responsible for commits. Default true. See
	 * https://github.com/spring-projects/spring-kafka/issues/62 At the time of
	 * writing, async commits are not entirely reliable.
	 * @param syncCommits true to use commitSync().
	 */
	public void setSyncCommits(boolean syncCommits) {
		this.syncCommits = syncCommits;
	}

Is this warning still valid?

I believe it is fixed; we can remove that comment, but I'll try a run of the test suite with it set to false, just to be safe.
https://issues.apache.org/jira/browse/KAFKA-3412


Correct argument order for StringBuilder.Insert

The internal implementation function expected (self, string, startIndex,
count), but the bound methods both passed (self, startIndex, string,
count). The implementation would then insert the index at (usually) the
start of the string, which was not the desired behaviour.

Thanks.


Merge dev to master

This PR contains the following changes:

Fairly substantial refactor of src/bridge/bridge.ts
Addition of gOHM token

Looks good, can you add some tests to this? You can view the code coverage using yarn coverage.

@BlazeWasHere does this look good and ready for master and a release?


keyboard_mode=systemanddocked

when keyboard_mode is systemanddocked and the browser loses focus (another widget is focused), the browser won't un-focus the active HTML element

this is fixed with the introduction of FocusBehavior


Added route to get a user e. g. for third-party applications.

Why is this necessary?

Please ask @emanuelschuetze  for this special feature request.


Secret Option Require to access

When opening your hosted site, https://insta-vids-downloder.riadazzoun.repl.co/  it is showing {"error":"secret option required for sessions"}

Thanks it was fixed, replit deleted my .env without saving the enviroment variables as secrets.
Now its live and working.

Also, I wanted to make this for a mobile application. I just wanted to ask if it is legit to get/download videos from Instagram or YouTube and What could be done?
Do we need to get this API from somewhere or do we need to make it ourselves?

If you are talking about license the API is fully mine, it just scrapes the instagram post  page and fetches the mp4 link, and yeah you can use it in your application.
Just host it somewhere, remove the index route and add a access_key  key to the /api route and you should be good.
But if you are talking about if its legit to download instagram videos you will have to check their Terms of service.

Thank You So Much @riad-azz for your help. It means a lot.


preprocessed dataset

This work is excellent, but I encountered an issue while reproducing it. I found that the preprocessed dataset has inconsistencies, as the Clinica tool and the current ADNI format are not aligned. Could you kindly share your preprocessed ADNI dataset with me?

Thank you for bringing this up. I also had trouble processing the data from the original paper (https://www.nature.com/articles/s41598-022-20674-x). I'd normally be happy to share my data, but in this case I worry that it would violate the ADNI terms.
If you can elaborate more on the issue you are facing I'd be glad to try to help anyway.

Thank you very much! I have downloaded the ADNI1 1.5T MRI dataset, but it seems that the data I obtained is only post-processed data. There is a CSV file included, but it does not match the format required by Clinica.
Based on the files I currently have, it seems insufficient to convert the data into the format required by Clinica. Is there an alternative conversion pathway that I could use? Additionally, does this conversion process require Freesurfer and MATLAB software?
Thank you in advance for your help!

The tree structure of MR images

The clinica csv that I have

The clinica information which contained in xml file
so  how can i changed those to prepocessed data for this program.

Thank you for bringing this up. I also had trouble processing the data from the original paper (https://www.nature.com/articles/s41598-022-20674-x). I'd normally be happy to share my data, but in this case I worry that it would violate the ADNI terms.
If you can elaborate more on the issue you are facing I'd be glad to try to help anyway.

I'm not entirely sure if sharing the processed data would violate ADNI's regulations, but I assure you it will only be used for research purposes and not for any commercial use. Thank you again!

So I more or less just ended up using adni_to_bids (link) to convert my data directory into BIDS format and then iterated through the BIDS directory and used
torchio.transforms.Resample (link) to fit everything to the MNI template provided [here].
I found that Clinica was doing a lot of extra stuff that I didn't need and the original authors provided their MNI template, which let me register everything so that should be sufficient.

torchio.transforms.Resample maybe good. Thanks


Alienware 15R3 IR camera Drivers

Howdy is working perfectly with the Regular camera but I can't use IR camera as it is not detected by Ubuntu 18.04 beacuse of drivers issue i guess.
$ls -ltrh /dev/video*
crw-rw----+ 1 root video 81, 0 Oct 26 02:02 /dev/video0

I searched for hours but no luck. Please help me finding the IR camera drivers or any working technique so that i can use the Howdy with IR Camera.

That does sound like a driver issue, does running dmesg | grep "Unknown video format" output anything?

You could take a manual look at dmesg and search for video related errors, especially those mentioning uvcvideo. Does Cheese show the IR camera in Preferences?

Try to update to kernel 4.19. My archlinux XPS13 9370 IR camera is working after update the kernel

I didn't get time to look more into the issue. @boltgolt cheese is showing only the regular camera in preferences. I will look more into the dmesg logs and get back.
@sapjuniorI will give a try and see, thanks!

@sapjunior what's your exact kernel version number?

I'm using 4.19.2-1-ck-skylake

@boltgolt I looked into DMESG logs and grep with the camera I found following lines
 18.698893] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD (0bda:58c2) [   18.706178] uvcvideo 1-7:1.0: Entity type for entity Extension 4 was not initialized! [   18.706179] uvcvideo 1-7:1.0: Entity type for entity Extension 7 was not initialized! [   18.706180] uvcvideo 1-7:1.0: Entity type for entity Processing 2 was not initialized! [   18.706181] uvcvideo 1-7:1.0: Entity type for entity Camera 1 was not initialized! [   18.706225] input: Integrated_Webcam_HD: Integrate as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/input/input19 [   18.706262] usbcore: registered new interface driver uvcvideo [   18.706262] USB Video Class driver (1.1.1)
I see some 'camera 1' was not initialized which i think is IR camera ?

There's a similar bug on launchpad, could you try running sudo apt install uvcdynctrl and rebooting?

IR camera is still not working.
HW: Alienware 15R3
Distro: Ubuntu Studio 19.04
Kernel: 5.0.0-20-lowlatency

IR camera is still not working but the webcam works.
HW: Alienware 15R3
Distro: Ubuntu Studio 19.04
Kernel: 5.0.0-20-lowlatency
$ ls -ltrh /dev/video*
crw-rw----+ 1 root video 81, 1 Jul 14 01:27 /dev/video1
crw-rw----+ 1 root video 81, 0 Jul 14 01:27 /dev/video0

HW: Alienware 13R3
Not working for me too :(

Dell Inspiron 13 5378 not working.
dmesg:
[    6.126056] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD (0bda:58c2) [    6.165605] uvcvideo 1-5:1.0: Entity type for entity Extension 4 was not initialized! [    6.165608] uvcvideo 1-5:1.0: Entity type for entity Extension 7 was not initialized! [    6.165612] uvcvideo 1-5:1.0: Entity type for entity Processing 2 was not initialized! [    6.165614] uvcvideo 1-5:1.0: Entity type for entity Camera 1 was not initialized! [    6.166943] usbcore: registered new interface driver uvcvideo
lsusb:
Bus 001 Device 002: ID 0bda:58c2 Realtek Semiconductor Corp. Integrated_Webcam_HD

Similar issue on Ubuntu 20.04, kernel 5.8.0, Dell Inspiron 13 5378 -- I'm sure this is a driver problem rather than a howdy problem, but I figured I'd update the information on this

That does sound like a driver issue, does running dmesg | grep "Unknown video format" output anything?

No output

You could take a manual look at dmesg and search for video related errors, especially those mentioning uvcvideo. Does Cheese show the IR camera in Preferences?

I looked through but didn't notice any -- the only lines mentioning uvc were:
[    3.772662] videodev: Linux video capture interface: v2.00
[    3.802933] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD (0bda:58c6)
[    3.829097] input: Integrated_Webcam_HD: Integrate as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input20
[    3.829685] usbcore: registered new interface driver uvcvideo
[    3.829686] USB Video Class driver (1.1.1)

There's a similar bug on launchpad, could you try running sudo apt install uvcdynctrl and rebooting?

Unfortunately, no effect
Output of v4l2-ctl -d /dev/v4l/by-id/usb-CNFGE11F301030046600_Integrated_Webcam_HD_0x001-video-index1 --list-formats-ext
ioctl: VIDIOC_ENUM_FMT
	Type: Video Capture

Output of ffmpeg -f v4l2 -list_formats all -i /dev/video1
ffmpeg version 4.2.4-1ubuntu0.1 Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 9 (Ubuntu 9.3.0-10ubuntu2)
  configuration: --prefix=/usr --extra-version=1ubuntu0.1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-avresample --disable-filter=resample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librsvg --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-nvenc --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared
  libavutil      56. 31.100 / 56. 31.100
  libavcodec     58. 54.100 / 58. 54.100
  libavformat    58. 29.100 / 58. 29.100
  libavdevice    58.  8.100 / 58.  8.100
  libavfilter     7. 57.100 /  7. 57.100
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  5.100 /  5.  5.100
  libswresample   3.  5.100 /  3.  5.100
  libpostproc    55.  5.100 / 55.  5.100
[video4linux2,v4l2 @ 0x556aa2b876c0] ioctl(VIDIOC_G_INPUT): Inappropriate ioctl for device
/dev/video1: Inappropriate ioctl for device

The normal webcam is on /dev/video0 and has no issue -- running the above commands on it has the expected output

Closing as stale and out of scope, driver issue


[Bug] Minor - The name of the password field in the Registration form begins with a small letter

Describe the bug
All the fields' names in the Registration form in English begins with capital letters, except the password field
To Reproduce
Steps to reproduce the behavior:

Go to site URL
Click on burger menu
Choose 'Регистрация'
Choose English from the drop-down menu in the upper right corner
A registration form in English is opened and all the fields' names begins with capital letters, except the password field

Expected behavior
A registration form in English is opened with names of the fields in the same style

Smartphone (please complete the following information):

Device: Xiaomi Redmi Note 10 S
OS: Android
Browser: Chrome
Version v0.9.8

The fix for password casing needs to happen in the Keycloak Theme theme-podkrepi/register. See how to setup a local Keycloak and edit the theme here: https://github.com/podkrepi-bg/infrastructure/tree/main/keycloak#local-testing


remove java unused file

.classpath
.project
target

I think you should use git submodule and point to official oM2M repository?

I modified some config in some module of origin om2m project, so i pushed all of them to remain that config.


Preserve EXIF orientation information

Coverage remained the same at 100.0% when pulling 1f9279f43219b46b42cdf09815b7b77e8ff1a7f9 on exif-rotation into 0cc608031ed52caa3f91e0e9a7b6d9dee6d9ec3a on master.


HTTP calls with host header ending with a dot is blocked by sidecar

Bug description
404 is returned when http calls contain host with a trailing dot. For ex: http://webservice.svc.cluster.local.:8080/
Expected behavior
Steps to reproduce the bug
On any kubernetes webservice, access the service using the trailing dot url.
Version (include the output of istioctl version --remote and kubectl version)
$ istioctl version
client version: 1.3.3
control plane version: 1.3.3
How was Istio installed?
https://istio.io/docs/setup/install/helm/#option-1-install-with-helm-via-helm-template
Environment where bug was observed (cloud vendor, OS, etc)

The challenge with this is that there is a huge matrix of clients/server behavior:

Client sends trailing . but strips it from Host header
Client sends trailing . and keeps in in Host header
Server accepts trailing .
Server rejects trailing .
Server sends a 301 for trailing dot

From Istio perspective, we would likely need to double the virtualHosts so we have variants with . and without

@ffarozan if you define a VirtualService for the hostname in question webservice.svc.cluster.local., does routing behave as you expect?  The trailing . should make it through Istio's validation logic

I haven't defined a VirtualService. My initial use-case with istio is to observe layer 4 metrics from all pods. So there is no use-case for me to define a VirtualService.

Was this somehow resolved already by any chance?
We just discovered that FQDN hosts are not matched because of the mentioned problem. So we have to actually create double records for each host in gateways and virtualservices.

We hit this old issue here in October 2021. If you're seeing it too and don't like the idea of doubling all your VirtualServices and ServiceEntries, try this EnvoyFilter. It toggles the Envoy strip_trailing_host_dot feature. It completely solved the problem for us.
apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  name: strip-trailing-dot
  namespace: istio-system
spec:
  configPatches:
  - applyTo: NETWORK_FILTER
    match:
      listener:
        filterChain:
          filter:
            name: "envoy.filters.network.http_connection_manager"
    patch:
      operation: MERGE
      value:
        typed_config:
          "@type": "type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager"
          strip_trailing_host_dot: true

🎃

@howardjohn it's possible to create flag so we can enable/disable strip_trailing_host_dot in HTTP connection manager?


websocket is not created correctly in a proxied environment

Since the websocket address is created using window.location.hostname, any information regarding the true URL (e.g. the custom port) is missed.
https://github.com/Evidlo/picklecast/blob/1ae55d17b0bf4c8b5ff5f30fea1f84f9bd46bd33/picklecast/webrtc.js#L25
One possible fix would be to use window.location.href and strip the https:// part and the display part, if exists.
Example: window.location.href.replace("https://","").replace("display","").

Should be fixed now.


feat: Sync from noir

Automated pull of development from the noir programming language, a dependency of Aztec.
BEGIN_COMMIT_OVERRIDE
feat: add de-sugaring for impl Trait in function parameters (https://github.com/noir-lang/noir/pull/4919)
feat(experimental): comptime globals (https://github.com/noir-lang/noir/pull/4918)
chore: update error conversion traits to act on references (https://github.com/noir-lang/noir/pull/4936)
fix: ban self-referential structs (https://github.com/noir-lang/noir/pull/4883)
chore: add regression test for #3051 (https://github.com/noir-lang/noir/pull/4815)
fix: discard ref counts during unrolling (https://github.com/noir-lang/noir/pull/4923)
feat!: Bit shift is restricted to u8 right operand (https://github.com/noir-lang/noir/pull/4907)
END_COMMIT_OVERRIDE

Benchmark results
Metrics with a significant change:

circuit_simulation_time_in_ms (merge-rollup): 6,542 (+22%)
tx_pxe_processing_time_ms (0): 1,391 (-21%)
batch_insert_into_append_only_tree_32_depth_ms (512): 263 (-24%)
tx_sequencer_processing_time_ms (2): 787 (-23%)
tx_sequencer_processing_time_ms (4): 934 (-24%)
tx_sequencer_processing_time_ms (5): 2,172 (-18%)
tx_sequencer_processing_time_ms (8): 1,107 (-28%)
node_history_sync_time_in_ms (10): 31,919 (+18%)
l2_block_public_tx_process_time_in_ms (8): 8,994 (-18%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
64 txs

l1_rollup_calldata_size_in_bytes
740
740
740

l1_rollup_calldata_gas
6,680
6,692
6,680

l1_rollup_execution_gas
586,812
586,824
586,812

l2_block_processing_time_in_ms
1,659 (-1%)
5,379 (+3%)
10,622 (+8%)

l2_block_building_time_in_ms
22,691 (-13%)
89,527 (-1%)
177,940 (+5%)

l2_block_rollup_simulation_time_in_ms
22,480 (-12%)
88,774 (-1%)
176,461 (+5%)

l2_block_public_tx_process_time_in_ms
:warning: 8,994 (-18%)
34,790 (-8%)
69,850 (-1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
16,960 (+15%)
:warning: 31,919 (+18%)

node_database_size_in_bytes
20,725,840
37,412,944

pxe_database_size_in_bytes
29,868
59,425

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
175 (-8%)
46,819
28,822

private-kernel-inner
208 (-8%)
76,734
28,822

private-kernel-ordering
229 (-8%)
53,040
42,751

base-parity
69.1 (-15%)
128
64.0

base-rollup
16,455 (+13%)
111,062
925

root-parity
1,624 (-3%)
27,064
64.0

root-rollup
64.4 (-16%)
11,454
789

public-kernel-app-logic
1,995 (-1%)
54,321
22,677

public-kernel-tail
4,870 (-2%)
159,770
3,898

merge-rollup
:warning: 6,542 (+22%)
2,696
925

public-kernel-teardown
160 (-7%)
54,321
30,042

public-kernel-setup
220 (-4%)
54,321
30,042

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
512 leaves
1024 leaves
2048 leaves
4096 leaves
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
11.0 (-4%)
17.8 (-9%)
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.7
31.8
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.643 (-4%)
0.547 (-9%)
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
51.8 (-5%)
80.5 (-2%)
:warning: 263 (-24%)
504 (+3%)
990
1,968 (+2%)
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
543
1,055
2,079
4,127
N/A

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.530 (-5%)
0.496 (-2%)
0.478 (-24%)
0.470 (+3%)
0.468
0.469 (+2%)
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
61.2 (-4%)
121 (-5%)
378 (-14%)
742 (+4%)
1,480 (-4%)
2,953 (+2%)
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
105
208
692
1,363
2,707
5,395
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.537 (-3%)
0.542 (-4%)
0.513 (-14%)
0.509 (+3%)
0.510 (-4%)
0.512 (+1%)
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
67.3

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
108

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.590 (-1%)

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
44,613
535,433

Transaction size based on fee payment method

Metric
native fee payment method
fpc_public fee payment method
fpc_private fee payment method

tx_with_fee_size_in_bytes
897
1,145
1,345

Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes
2 new note hashes

tx_pxe_processing_time_ms
:warning: 1,391 (-21%)
1,015 (-8%)
3,623 (-13%)

Metric
1 public data writes
2 public data writes
3 public data writes
4 public data writes
5 public data writes
8 public data writes

tx_sequencer_processing_time_ms
890 (-3%)
:warning: 787 (-23%)
1,418 (-11%)
:warning: 934 (-24%)
:warning: 2,172 (-18%)
:warning: 1,107 (-28%)


Support add / remove class in SVG elements (IE11)

In IE11, SVG elements do not support classList, and className is not a string; rather, is an object with the properties baseVal and animVal. This PR checks the type of className when it reaches that case and properly manipulates the SVG property when dealing with such an element.

Thanks. If you both approve, what is the timetable on this getting merged / published?

I'm not a repo maintainer, but I'm very much interested in this bugfix
BTW thanks for PR


Regression in binding_array after update to 0.11.0

Bevy version
0.11.0
Relevant system information
OS: NixOS 23.11.20230719.7f256d7 (Tapir)
AdapterInfo { name: "AMD Radeon RX 6800 XT (RADV NAVI21)", vendor: 4098, device: 29631, device_type: DiscreteGpu, driver: "radv", driver_info: "Mesa 23.1.3", backend: Vulkan }

What you did
I'm using binding_array<texture_2d<f32>> in my shaders.
What went wrong
When upgrading from 0.10.0 to 0.11.0, I started experiencing weird artifacts in my textures.
Additional information
While investigating, I decided to sanity check myself and make sure the texture_binding_array example worked. It worked great on 0.10.0, but had issues on 0.11.0, as shown below:

Left: 0.10.0 - Right: 0.11.0
Bisecting the commits revealed the culprit as being the upgrade to wgpu 0.16.0: https://github.com/bevyengine/bevy/commit/4d54ce14aaee8d7432380df37c41c03c28594b27.
Running the texture_binding_array example works great on the commit prior (https://github.com/bevyengine/bevy/commit/75130bd5ecfe58693b6a6777fd5cee04b6a34489), and after backporting my project and dependencies back to that commit, my texture artifacts also disappeared.

I can't reproduce on macOS / Metal, the example look like the left cube for me

I'm closing this, I've bisected all the way up to naga as being the problem child. Continuing in #2408


How to Force TLSv1.2 or Http1.0/1.1?

I am trying to run the gRPC client from .NET Framework 4.6.2 in Windows 10 with the LabVIEW gRPC server. So far I encountered multiple limitations of Grpc.Net.Client in .NET Framework 4.6.2.

.NET implementations that don't support HTTP/2 (Use gRPC client with .NET Standard 2.0)
WinHttp supports HTTP/2 but only gRPC calls over TLS are supported.
I generated the cert file using openssl and include the credential into the WinHttp. LabVIEW client works but the C# client fails with error 12175 (One or more errors were found in the Secure Sockets Layer (SSL) certificate sent by the server.). Upon inspecting Wireshark, I found out that the LabVIEW gRPC client uses TLSv1.3 but the C# client uses TLSv1.2. Unfortunately, TLSv1.3 is not supported in Windows 10. (Protocols in TLS/SSL (Schannel SSP))

Since I am planning to implement the C# client for VeriStand Editor Plugin Examples, I cannot change the .NET Framework version. My only option now is to use a lower TLS or HTTP version. Appreciate it if you can point out how can I make this configuration.
AB#2285612

@ZhiYang-Ong, I am not sure of you got the answer for this or if your issue is resolved. Can you conform if I can close this issue?

@Rohith-Grandhi I have managed to work around this by exporting the LabVIEW gRPC Client VI as an interop assembly in .NET. Please feel free to close this ticket. Thanks.


Move getters to web worker

Closes #3250. Unfortunately, this change did not fix the large number of threads, but I did notice that commenting out all code related to FlexSearch caused them to go away, so apparently there is something else related to FlexSearch that's still causing this. I filed #3271 to investigate this further.

Have you cranked up the UI to test that it doesnt blow up?

The markets show up in the UI, but as I mentioned in the PR description, it doesn't fix the large number of threads. Still need to look into that more.


Bugfix: sets have ValueType not KeyType

Yikes, good catch. I guess none of the test thrift files must use sets.

Added test: https://github.com/samuel/go-thrift/commit/863307e10d68fa10d0fb2b7bfc547dcfd7ab3948
Thanks for the fix

Sorry, this was my fault. I broke it in #44 when I factored out the formatKeyType function.


fix: issue where sometimes showed unused import remappings in settings

What I did
Allow getting import remappings to filter by the given source paths.
This allows us to remove unused remappings from settings if possible.
How I did it
Read the lines of the source files and only use remappings from config if present
How to verify it

Have a bunch of remappings in config e.g.

solidity:
  import_remapping:
    -<EMAIL_ADDRESS>    -<EMAIL_ADDRESS>    -<EMAIL_ADDRESS>

Have a source file only use one of them e.g.:

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.2;
import "@openzeppelin/contracts/<something>";
contract Contract {
    address public owner;
}

Check settings and make sure only the 1 shows:
project.extract_manifest().compilers[0].settings["remappings"]

Checklist

[ ] Passes all linting checks (pre-commit and CI jobs)
[ ] New test cases have been added and are passing
[ ] Documentation has been updated
[ ] PR title follows Conventional Commit standard (will be automatically included in the changelog)

issue with this... need to refactor to only change imports at settings level and not always


Syntax code blocks lose indenting but keep colours in PDF

Code that is rendered correctly in the HTML output  is coloured correctly (indicating that Pygments styling is occurring), but the indenting is lost in the PDF:

Aha! This is a tab issue. We convert spaces (to an internal PDF spacer character) but we do not current convert tabs. Therefore, the tabs get dropped.
This is related to https://github.com/asciidoctor/asciidoctor/issues/1170. We can implement this feature ahead of core since it is handled by different code anyway. But that proposes the design we indent to implement.

A quickfix is to use spaces instead of tabs, but I do understand that it's necessary to support both.

Using spaces does work, and that's pretty acceptable from my point of view. The confusing thing is when something renders the way you expect in HTML but not in the PDF.

The confusing thing is when something renders the way you expect in HTML but not in the PDF.

That's just life at the moment since these are two completely different worlds. We're doing our best to squash these differences so that you can think at the higher level of abstraction...and I believe we can achieve that for all but the rarest edge cases. We just have to keep throwing data at it so we can see the trouble spots light up.

I'm going to leave this issue open so that we normalize tabs, one way or another.

It may be worth adding something to the Asciidoctor user guide here and/or here to say: use spaces to be sure of getting expected output, since noone can be sure how TABs might render.

I decided to do this correctly by actually expanding tabs to spaces instead of simply replacing them. That means counting columns and expanding tabs to the number of spaces needed to fill the column in which the tab is used. Not only will the spaces be preserved, it will now be possible to use tabs to align output into columns (such as the output of a command or otherwise tab-separated data).
Unfortunately, things are going to be a bit weird before Asciidoctor 1.5.3 if you're using the indent attribute. The indent attribute triggers a replacement of tabs to spaces, but not with the expand logic (see https://github.com/asciidoctor/asciidoctor/blob/v1.5.2/lib/asciidoctor/parser.rb#L2632). Therefore, you may get mixed and unexpected behavior. If you aren't using the indent attribute, you won't be affected.
The good news is now I know how to solve https://github.com/asciidoctor/asciidoctor/issues/1170 properly.


metrics flatline, no more 'complete proposal block' messages seen on validators in federated mode after adding a 3rd

Issue type
Support
Have you reproduced the bug with the latest dev version?
Yes
Version
0.1.0
Custom code
Yes
OS platform and distribution
Ubuntu 22.04
Describe the issue
Created a federated subnet /r314159/t410f3rhmoqizadf6kws5sup6y3g77swnrippfhvdxbq on 9/13 with 2 validator nodes, power 10000 each.  The abci_committed_block_height metric grew normally.
On 9/16 approx 16:40 UTC added a 3rd validator power 2.  also glif nodes may have gone down around that time.  From 9/16 17:15 UTC the abci_committed_block_height metric flatlined.

(times in the image are in PST)
Restarted the fendermint and cometbft containers several hours later.
In the logs, the last received complete proposal block message in the cometbft logs appears at 2024-09-16|22:50:39
Currently the nodes are not seeing any 'proposal block' messages in the cometbft logs, and the abci_committed_block_height remains flat.  we need the nodes to start working again, but not clear how.
Repro steps
This has happened to us twice on adding a 3rd node to federated mode, the first time was on Friday when they each had federated power of 2.  we since created a new subnet and it has happened again.
Relevant log output
not sure if this is the most relevent snippet, this is around the time that it stopped receiving proposals, but the flatline was actually several hours earlier

[2024-09-16|22:50:39.376] received proposal                            module=consensus proposal="Proposal{286202/0 (61217EF0483E665916F16DCA289CE5714BD6D989ECB37AABBAE60AF1AAAB427A:1:2BF617C15BBF, -1) 61AFE75411CC @ 2024-09-16T17:14:24.328154069Z}" proposer=51AEE530738E76C647B97E76305EEB8818C35E27
I[2024-09-16|22:50:39.376] Replay: BlockPart                            module=consensus height=286202 round=0 peer=53168b782187ff431d86849251ec28f274d9c703
I[2024-09-16|22:50:39.376] received complete proposal block             module=consensus height=286202 hash=61217EF0483E665916F16DCA289CE5714BD6D989ECB37AABBAE60AF1AAAB427A
I[2024-09-16|22:50:39.922] New websocket connection                     module=rpc-server protocol=websocket remote=<IP_ADDRESS>:48544
I[2024-09-16|22:50:39.922] service start                                module=rpc-server protocol=websocket remote=<IP_ADDRESS>:48544 msg="Starting wsConnection service" impl=wsConnection
I[2024-09-16|22:50:39.922] Subscribe to query                           module=rpc remote=<IP_ADDRESS>:48544 query="tm.event = 'NewBlock'"
I[2024-09-16|22:50:39.922] WSJSONRPC                                    module=rpc-server protocol=websocket remote=<IP_ADDRESS>:48544 method=subscribe
I[2024-09-16|22:50:40.164] Replay: New Step                             module=consensus height=286202 round=0 step=RoundStepPrevote
I[2024-09-16|22:50:40.164] Replay: Vote                                 module=consensus height=286202 round=0 type=SIGNED_MSG_TYPE_PREVOTE blockID=61217EF0483E665916F16DCA289CE5714BD6D989ECB37AABBAE60AF1AAAB427A:1:2BF617C15BBF peer=53168b782187ff431d86849251ec28f274d9c703
I[2024-09-16|22:50:40.165] Replay: Timeout                              module=consensus height=286202 round=0 step=RoundStepPropose dur=3s
I[2024-09-16|22:50:40.165] Replay: New Step                             module=consensus height=286202 round=0 step=RoundStepPropose
I[2024-09-16|22:50:40.165] Replay: New Step                             module=consensus height=286202 round=0 step=RoundStepPrevote
I[2024-09-16|22:50:40.165] Replay: Proposal                             module=consensus height=286202 round=0 header=1:2BF617C15BBF pol=-1 peer=53168b782187ff431d86849251ec28f274d9c703
I[2024-09-16|22:50:40.165] Replay: Vote                                 module=consensus height=286201 round=0 type=SIGNED_MSG_TYPE_PRECOMMIT blockID=F3411281509D72C63E5F26E6A7CD00B1481AABBEF205DC48B494BA79E4E16455:1:E2AFB8D15671 peer=53168b782187ff431d86849251ec28f274d9c703
I[2024-09-16|22:50:40.165] Replay: BlockPart                            module=consensus height=286202 round=0 peer=53168b782187ff431d86849251ec28f274d9c703
I[2024-09-16|22:50:40.165] Replay: Vote                                 module=consensus height=286202 round=0 type=SIGNED_MSG_TYPE_PREVOTE blockID=61217EF0483E665916F16DCA289CE5714BD6D989ECB37AABBAE60AF1AAAB427A:1:2BF617C15BBF peer=53168b782187ff431d86849251ec28f274d9c703

@cryptoAtwill @raulk i put the issue here so others could see, we have limited seats in the hoku-deploy repo

Fendermint logs
Key: ProposalProcessed completely halted
root@c2-xm-f37e35:~# grep 'ProposalProcessed' /tmp/f-all.err | grep '2024-09-14' | wc
103219 1032190 41490853
root@c2-xm-f37e35:~# grep 'ProposalProcessed' /tmp/f-all.err | grep '2024-09-17' | wc
0       0       0
on 9/14, when working well, showed
2024-09-14T00:00:04.172580Z  INFO fendermint/app/src/app.rs:698: event=ProposalProcessed is_accepted=true block_height=
1802 block_hash="B7A907496E783088CDACEEF3EB631E393498B5A4787ABAF8C623120BE164BE18" num_txs=0 proposer="84D0DF30D7D27B0D4B1414D00A20C52B6DDEBB5D"
2024-09-14T00:00:04.426911Z  INFO fendermint/app/src/app.rs:891: event=NewBlock block_height=1802
2024-09-14T00:00:04.741345Z  INFO query{request=Query { data: b"\xa1jActorStateV\x04\n\x91\xc9/\xee\xc2\x85\xddV\xd5\x06\xf9\xebM\xdc.\xb7\xcdnq\x
dd", path: "", height: block::Height(9223372036854775807), prove: false }}: fendermint/vm/interpreter/src/fvm/query.rs:66: query actor state height

on 9/17, no new blocks, logs like
2024-09-17T00:01:13.899797Z  INFO fetch_data{height=1973485 block_hash=[197, 170, 93, 78, 100, 151, 154, 43, 181, 146, 8, 171, 67, 100
, 185, 91, 77, 154, 81, 154, 222, 217, 157, 215, 178, 49, 52, 111, 230, 22, 170, 161]}:get_validator_changes{height=1973485}: ipc/pr
ovider/src/manager/evm/manager.rs:202: querying validator changes in evm subnet contract: 0xdc4e…a1ef
2024-09-17T00:01:14.355625Z  INFO fendermint/vm/topdown/src/sync/syncer.rs:259: event=NewParentView is_null=false block_heigh
t=1973485 block_hash="c5aa5d4e64979a2bb59208ab4364b95b4d9a519aded99dd7b231346fe616aaa1" num_msgs=0 num_validator_changes=0
2024-09-17T00:01:33.879929Z  INFO fetch_data{height=1973486 block_hash=[122, 112, 230, 197, 22, 29, 82, 162, 30, 195, 154, 160, 60, 25
0, 37, 147, 247, 176, 137, 22, 29, 253, 30, 13, 101, 254, 199, 24, 227, 56, 178, 175]}:get_validator_changes{height=1973486}: ipc/pr
ovider/src/manager/evm/manager.rs:202: querying validator changes in evm subnet contract: 0xdc4e…a1ef

at 9/16 at 17:15 approx when broke
2024-09-17T00:00:34.362664Z  INFO fendermint/vm/topdown/src/sync/syncer.rs:259: event=NewParentView is_null=false block_heigh
t=1973484 block_hash="b0f6a09ff7c5c6de2bef6b14fbecfaa02cb3f1afec92259b3bc776d28b78e14f" num_msgs=0 num_validator_changes=0
2024-09-17T00:01:03.181328Z ERROR fendermint/vm/topdown/src/sync/mod.rs:191: sync with parent encountered error error="failed to get Tenderm
int status"
2024-09-17T00:01:13.899797Z  INFO fetch_data{height=1973485 block_hash=[197, 170, 93, 78, 100, 151, 154, 43, 181, 146, 8, 171, 67, 100
, 185, 91, 77, 154, 81, 154, 222, 217, 157, 215, 178, 49, 52, 111, 230, 22, 170, 161]}:get_validator_changes{height=1973485}: ipc/pr
ovider/src/manager/evm/manager.rs:202: querying validator changes in evm subnet contract: 0xdc4e…a1ef
2024-09-17T00:01:14.355625Z  INFO fendermint/vm/topdown/src/sync/syncer.rs:259: event=NewParentView is_null=false block_heigh
t=1973485 block_hash="c5aa5d4e64979a2bb59208ab4364b95b4d9a519aded99dd7b231346fe616aaa1" num_msgs=0 num_validator_changes=0
2024-09-17T00:01:33.879929Z  INFO fetch_data{height=1973486 block_hash=[122, 112, 230, 197, 22, 29, 82, 162, 30, 195, 154, 160, 60, 25
0, 37, 147, 247, 176, 137, 22, 29, 253, 30, 13, 101, 254, 199, 24, 227, 56, 178, 175]}:get_validator_changes{height=1973486}: ipc/pr
ovider/src/manager/evm/manager.rs:202: querying validator changes in evm subnet contract: 0xdc4e…a1ef
2024-09-17T00:01:34.333529Z  INFO fendermint/vm/topdown/src/sync/syncer.rs:259: event=NewParentView is_null=false block_heigh
t=1973486 block_hash="7a70e6c5161d52a21ec39aa03cfa2593f7b089161dfd1e0d65fec718e338b2af" num_msgs=0 num_validator_changes=0
2024-09-17T00:01:53.180739Z ERROR fendermint/vm/topdown/src/sync/mod.rs:191: sync with parent encountered error error="failed to get Tenderm
int status"

the 'failed to get Tendermint status' happened some when things were working but much more now
root@c2-xm-f37e35:~# grep 'failed to get Tendermint status' /tmp/f-all.err | grep '2024-09-14' | wc
16     208    3344
root@c2-xm-f37e35:~# grep 'failed to get Tendermint status' /tmp/f-all.err | grep '2024-09-17' | wc
723    9399  151107

The cometbft addrbook shows a last success time of just prior to the error condition
63505f0688d0:/cometbft# cat /cometbft/config/addrbook.json
{
	"key": "e9da010b4783a6485bf4007c",
	"addrs": [
		{
			"addr": {
				"id": "53168b782187ff431d86849251ec28f274d9c703",
				"ip": "<IP_ADDRESS>",
				"port": 26656
			},
			"src": {
				"id": "a918bb7532318af7ec00eef2ec3fa1341d8f78e3",
				"ip": "<IP_ADDRESS>",
				"port": 26656
			},
			"buckets": [
				25
			],
			"attempts": 1,
			"bucket_type": 2,
			"last_attempt": "2024-09-16T21:42:33.928681864Z",
			"last_success": "2024-09-16T17:03:30.733503089Z",
			"last_ban_time": "0001-01-01T00:00:00Z"
		}
	]
}

NOTE: I had erroneously NOT started the relayer until 9/16, so the successful period was without a relayer running.
The relayer logs are as follows:
root@c2-xm-f37e35:~# docker logs 5dbd5ae739e4
2024-09-16T21:25:58.920099Z  INFO ipc_provider::checkpoint: launching bottom-up relayer, parent: /r314159, child: /r314159/t410f3rhmoqizadf6kws5sup6y3g77swnrippfhvdxbq for t410fshes73wcqxovnvig7hvu3xbow7gw44o5e6a2lsa
2024-09-16T21:25:59.037570Z  INFO ipc_provider::checkpoint: last submission height: 0
2024-09-16T21:31:34.139495Z  INFO ipc_provider::checkpoint: last submission height: 0
2024-09-16T21:37:08.978150Z  INFO ipc_provider::checkpoint: last submission height: 0
2024-09-16T21:42:11.320313Z ERROR ipc_provider::checkpoint: cannot submit checkpoint for submitter: t410fshes73wcqxovnvig7hvu3xbow7gw44o5e6a2lsa due to (code: 0, message: Tendermint RPC error: response error

Caused by:
    Internal error: leveldb: closed (code: -32603)

Location:
    /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/flex-error-0.4.4/src/tracer_impl/eyre.rs:10:9, data: None)
2024-09-16T21:42:26.647738Z  INFO ipc_provider::checkpoint: last submission height: 0
2024-09-16T21:42:28.348755Z ERROR ipc_provider::checkpoint: cannot submit checkpoint for submitter: t410fshes73wcqxovnvig7hvu3xbow7gw44o5e6a2lsa due to (code: 0, message: Tendermint RPC error: HTTP error

Caused by:
    connection error: Connection reset by peer (os error 104)

Location:
    /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/flex-error-0.4.4/src/tracer_impl/eyre.rs:10:9, data: None)
2024-09-16T21:42:43.462467Z  INFO ipc_provider::checkpoint: last submission height: 0
2024-09-16T21:42:43.464295Z ERROR ipc_provider::checkpoint: cannot submit checkpoint for submitter: t410fshes73wcqxovnvig7hvu3xbow7gw44o5e6a2lsa due to (code: 0, message: Tendermint RPC error: HTTP error

Caused by:
    error trying to connect: tcp connect error: Connection refused (os error 111)

Location:
    /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/flex-error-0.4.4/src/tracer_impl/eyre.rs:10:9, data: None)
2024-09-16T21:42:58.580812Z  INFO ipc_provider::checkpoint: last submission height: 0
2024-09-16T21:48:36.238959Z  INFO ipc_provider::checkpoint: last submission height: 0
2024-09-16T21:54:10.901048Z  INFO ipc_provider::checkpoint: last submission height: 0
2024-09-16T21:59:47.961852Z  INFO ipc_provider::checkpoint: last submission height: 0
2024-09-16T22:05:22.559853Z  INFO ipc_provider::checkpoint: last submission height: 0

One theory is that the problem is the wallet balances, also there is an error we do not understand about 'sender invalid'.
testnet-ansible-v3@c2-xm-f37e35:/home$ ipc-cli subnet send-value --subnet /r314159/t410f3rhmoqizadf6kws5sup6y3g77swnrippfhvdxbq --from 0x91c92feec285dd56d506f9eb4ddc2eb7cd6e71dd --to 0x1ae0a65e99d41c74e85ae58e8eec65fe9f569fd0  .0002
2024-09-17T18:57:18.467241Z ERROR ipc_cli: main process failed: error processing command Some(Subnet(SubnetCommandsArgs { command: SendValue(SendValueArgs { from: Some("0x91c92feec285dd56d506f9eb4ddc2eb7cd6e71dd"), to: "0x1ae0a65e99d41c74e85ae58e8eec65fe9f569fd0", subnet: "/r314159/t410f3rhmoqizadf6kws5sup6y3g77swnrippfhvdxbq", amount: 0.0002 }) })): (code: 1, message: failed to estimate gas: pre-validation failed: Sender invalid
, data: Some(String("")))
testnet-ansible-v3@c2-xm-f37e35:/home$ ipc-cli wallet balances --subnet /r314159/t410f3rhmoqizadf6kws5sup6y3g77swnrippfhvdxbq --wallet-type evm
0x91c92feec285dd56d506f9eb4ddc2eb7cd6e71dd - Balance: 0.0
0x8ca38bf111456f4733e9ff55ef21f6e693f83baf - Balance: 0.0
0x731d8dcfd82a90b63e9fa0c49f0c43f9c3b5a4cf - Balance: 0.0
0x93b269addeefd6276d115a0816c4d841255788fb - Balance: 0.0
testnet-ansible-v3@c2-xm-f37e35:/home$ ipc-cli subnet list --parent /r314159
/r314159/t410fwwfc3my2jrejevghickfx66tjhubanqhvauwizi - collateral: 0.0 FIL, circ.supply: 0.0 FIL, genesis: 1974726
/r314159/t410fhcefljyminf6mgmcj7tqzef2fhppy7wg23r22ea - collateral: 0.0 FIL, circ.supply: 20110.0100001000000002 FIL, genesis: 1958160
/r314159/t410f3rhmoqizadf6kws5sup6y3g77swnrippfhvdxbq - collateral: 0.0 FIL, circ.supply: 1000.000002 FIL, genesis: 1964397
/r314159/t410fdt67sqg7fvju6z3y7jl3awvrvu445jihustvmwi - collateral: 0.0 FIL, circ.supply: 0.0030000000000001 FIL, genesis: 1952931
/r314159/t410fmnm74ynqjpkdmfxtakd4b7or2jbp4s2jsixretq - collateral: 0.0 FIL, circ.supply: 0.0000000100000001 FIL, genesis: 1957433

To attempt to get funds into the subnet, we performed both
ipc-cli cross-msg fund-with-token --subnet /r314159/t410f3rhmoqizadf6kws5sup6y3g77swnrippfhvdxbq --from 0x91c92feec285dd56d506f9eb4ddc2eb7cd6e71dd --approve<PHONE_NUMBER>000

and
cast send $SOURCE_SUPPLY_ADDRESS \
  "mint(address,uint256)" \
  0x7287922457de4095e7b7e8cdcddf6be48c3f1f4a \
1000000000000000 \
  --private-key $VALIDATOR_0_PRIVATE_KEY \
  --rpc-url $PARENT_CHAIN_RPC

on 9/16/2024.
On 9/13/2024, when the validator nodes appeared to be working, the only funding had been thru the set-federated-power command.

@sanderpick @raulk if you think i should start a new subnet let me know, my concern is this one already was given to Matrixed.link, and really we don't know why it stopped processing proposals, so not sure starting a new one is the answer.

at 9/17/2024 21:18 UTC i simul-restarted all containers on all 3 validators (the 2 original and the new one) but did not make any difference, same types of log messages, no new blocks.

from Ben Wilson - these broadcast errors may be a root cause, that the checkpoints are not being signed
docker logs testnet-belgrade-v1-fendermint 2>&1 | grep -i checkpoint
...
2024-09-17T14:40:07.979239Z  INFO fendermint/vm/interpreter/src/fvm/checkpoint.rs:124: event=NewBottomUpCheckpoint block_height=600 block_hash="48da220db674f65ad544b1b69feb2539252607ed64ede28dfeebb78f51391512" num_msgs=0 next_configuration_number=2
2024-09-17T14:40:09.988490Z ERROR fendermint/vm/interpreter/src/fvm/exec.rs:224: error broadcasting checkpoint signature error=failed to broadcast checkpoint signature

resulting in empty signatory lists
[[4,10,181,138,45,179,26,76,72,146,84,199,64,148,91,251,211,73,232,16,54,7]]],"block_height":2400,"block_hash":"976d0261db46657080319252ee58c8d1dc62e3671fcd907f339ab3ce39599487","next_configuration_number":0,"msgs":[]},"signatures":[],"signatories":[]}

those error will happen if the validators dont have funds in the subnet. this will only have an effect on bottom up relayer messages, not block production.
from an initial look... this seems to be a misconfiguration with cometbft... i would recommend starting fresh with two working validators and then try to add a third again.
i can try this on some separate infra just to sanity check.

Btw, @gvelez17, I also noticed a misconception (maybe), set-ferederated-power and fund-with-token are two different methods. set-federated-power gives voting power and fund-with-token is actually providing funds. So set-federated-power will not increase balance in anyway.
For the relayer, can you check if your gateway configuration in the child subnet is correct?
I rmb I had a call with Ben and everything is working, so the change is just set-federated-power and everything broken?

noticed that an ip address from a previous testnet subnet kept showing up in the cometbft addrbook.json, apparently being gossiped between nodes (even if simul removed and restarted)
Added the "bad" peer id into the private_peer_ids list in each node
private_peer_ids = "bd5f0ca740089aeab7f16f00c3e8a7c69e99b41e"
cleaned and restarted again, this time it did not show up and proposals started again!

still having some issues with checkpoints not being signed by all validators, but the original issue is resolved, closing.  thanks for help!


Minimize PACKMOL-generated systems against Parsley 1.1.0

Fixes #557
Here is the script I used to modify these files. It mostly takes @j-wags's snippet in #324 and does the energy minimization. There's a lot of validation that could be done to ensure that the configuration is ok; all I did was run an OpenMM simulation for 1000 steps to ensure it doesn't immediately, or nearly immediately, crash, which was the origin of the issue.
I'm also sharing my script because it could be used, with some modifications, to minimize configurations against particular force fields. This is out of the scope of this PR but that could be a valuable utility at some point.

[x] Tag issue being addressed
[ ] Add tests
[ ] Update docstrings/documentation, if applicable
[ ] Update changelog

I embedded it as a hyperlink, although it's easy for that go missed if the color of the text is not too brights
https://gist.github.com/mattwthompson/4fb7dfa779734011e81019134ce764c0

Ooh this is great, thanks!


[red-knot] Autoformat mdtest Python snippets using blacken-docs

Summary
This PR adds a blacken-docs hook to our .pre-commit-config.yaml so that we can easily autoformat all Python code snippets in our mdtest Markdown files en masse. Since we run pre-commit in CI, this will also enforce a consistent style for these Python snippets in CI.
Although Ruff is able to format Python code snippets in docstrings, it doesn't seem like it's yet capable of formatting Python code snippets in Markdown files, so it seems like blacken-docs is the best option here for now.
I went with --line-length=1000, because the assertion comments in our test files can get quite long, and it seems more annoying than helpful if autoformatting results in changes such as
- x = a  # error: some verrrrrrrrrrrrrrrrrry verbosssssssssssse error messageeeeeeeeeeee
+ x = (
+     a # error: some verrrrrrrrrrrrrrrrrry verbosssssssssssse error messageeeeeeeeeeee
+ )

Test Plan
pre-commit run -a

Cc. @sharkdp as well, for interest :-)

Nice but.... that would force me to use pre-commit which I rather don't
I also think that a line length of 1000 is too high. How about something more realistic like 120? What I remember is that
revealed and expected can be used as own line comments. I would argue that that's probably a better style for very long diagnostics.

A line length of 1000 is actually problematic because Black then collapses expressions onto a single line. E.g. long comprehensions or binary expressions would be printed as a single line statement.

I wonder if we should integrate this into the mdtest framework instead where setting an environment variable formats the snippets

Nice but.... that would force me to use pre-commit which I rather don't. But not sure how we can accomplish this today without pre-commit.

You can also run blacken-docs manually. Pre-commit makes the experience much nicer IMO, but there's some docs here on how to manually run it.
We already do nearly all our other linting (typos-checking, Markdown checking, etc.) via pre-commit in this repo, so I'd personally prefer to stick to that here.

I also think that a line length of 1000 is too high. How about something more realistic like 120? What I remember is that
revealed and expected can be used as own line comments. I would argue that that's probably a better style for very long diagnostics.

Yeah, that's a fair point. I'll switch to 130, for no other reason than it's what typeshed uses, and I like the formatting of typeshed's stubs 😄

I wonder if we should integrate this into the mdtest framework instead where setting an environment variable formats the snippets and files that are not correctly formatted fail otherwise (that seems somewhat annoying)

I would much prefer to be able to easily autoformat all the files with a single command. And this also feels like a linting issue than something that should cause the tests to fail, to me

(To elaborate on how I use pre-commit, in case it's helpful: I don't much like installing git hooks locally. I actually never set them up; I never run pre-commit install in a repo locally. I only ever use pre-commit as a command runner. But for the purpose of orchestrating various linting tools and running them over a codebase, it's pretty nice IMO. Just because it can be used as a way of coordinating git hooks that run on every commit, doesn't mean that that's the way you have to use it.)

Out of curiosity, is there any particular reason for using black to format rather than the ruff formatter, which is how the ruff docs are formatted (https://github.com/astral-sh/ruff/blob/main/scripts/check_docs_formatted.py#L147C1-L176C23)?

Out of curiosity, is there any particular reason for using black to format rather than the ruff formatter, which is how the ruff docs are formatted (main/scripts/check_docs_formatted.py#L147C1-L176C23)?

The check_docs_formatted.py script will check that the docs are formatted and complain if they aren't, but it won't actually format them for you. That feels like the opposite of what I want for mdtest :-)
I want something that's going to make my life easier (by making it easy to apply a consistent style across these Markdown files, using only a single CLI command). If check_docs_formatted.py complains at me about things being badly formatted but doesn't actually fix things for me, that feels like it makes my life harder, not easier.

We already do nearly all our other linting (typos-checking, Markdown checking, etc.) via pre-commit in this repo, so I'd personally prefer to stick to that here.

Yes, we use pre-commit to check consistent styling in CI. But it's not a tool required when developing locally (or only very rarely and I then often have to run it multiple times which I don't understand why).

You can also run blacken-docs manually. Pre-commit makes the experience much nicer IMO, but there's some docs here on how to manually run it.

What's nice about Rust is that you can check out any project and you know how to run, test, and format it. Requiring users to figure out how to install a python tool and figure out the right pattern seems too much to ask (yes, uvx makes that easier).
That's why I still think an integration into mdtest is the better solution because the framework can print a useful message telling you that there are incorrectly formatted tests at the end of the run (as the last check) and suggest the command how you can update it, without any extra dependencies. mdtest can also use ruff's formatter

Yes, we use pre-commit to check consistent styling in CI. But it's not a tool required when developing locally (or only very rarely

Actually, I've found that our existing pre-commit hooks for Markdown linting have had complaints about the initial revision of nearly every red-knot PR I've submitted using mdtest 😆 So the situation you describe here has arguably already changed recently, whether for better or worse

I then often have to run it multiple times which I don't understand why

It generally stops after a single hook fails, so that you can then evaluate the changes that the hook might have made to your code before deciding whether you want to proceed. I agree that this is a bit annoying sometimes.

What's nice about Rust is that you can check out any project and you know how to run, test, and format it. Requiring users to figure out how to install a python tool and figure out the right pattern seems too much to ask (yes, uvx makes that easier).

I would say a common convention in a Python project is that you can run all the linting tools using pre-commit run -a 😄
And again, this is an existing problem on main. We should re-evaluate our existing pre-commit hooks if you have this concern; they're already quite picky about Markdown styling, and we have many more Markdown files now than we used to.

That's why I still think an integration into mdtest is the better solution because the framework can print a useful message telling you that there are incorrectly formatted tests at the end of the run (as the last check) and suggest the command how you can update it, without any extra dependencies. mdtest can also use ruff's formatter

It still feels "wrong" to me for the test framework to fail because of a linting error. To use your analogy of how nice it is that Cargo can generally manage everything for you in a typical Rust project, the result of cargo test is wholly independent from whether or not cargo fmt is going to reformat your code or not. They're fully separate concerns.

Actually, I've found that our existing pre-commit hooks for Markdown linting have had complaints about the initial revision of nearly every red-knot PR I've submitted using mdtest 😆 So the situation you describe here has arguably already changed recently, whether for better or worse

Uhh true. I wasn't aware of this

I then often have to run it multiple times which I don't understand why

It generally stops after a single hook fails, so that you can then evaluate the changes that the hook might have made to your code before deciding whether you want to proceed. I agree that this is a bit annoying sometimes.

I don't think I have this problem in other repos that use pre-commit. I think it's because of a specific setting in our pre-commit config. I filed https://github.com/astral-sh/ruff/pull/13811 to fix it.

Out of curiosity, is there any particular reason for using black to format rather than the ruff formatter, which is how the ruff docs are formatted (main/scripts/check_docs_formatted.py#L147C1-L176C23)?

The check_docs_formatted.py script will check that the docs are formatted and complain if they aren't, but it won't actually format them for you. That feels like the opposite of what I want for mdtest :-)
I want something that's going to make my life easier (by making it easy to apply a consistent style across these Markdown files, using only a single CLI command). If check_docs_formatted.py complains at me about things being badly formatted but doesn't actually fix things for me, that feels like it makes my life harder, not easier.

Understood. So if there were "ruffen-docs", it would be preferred, but as this doesn't exist (as far as I'm aware), then blacken-docs is a good substitute?

Understood. So if there were "ruffen-docs", it would be preferred, but as this doesn't exist (as far as I'm aware), then blacken-docs is a good substitute?

Yup!

I'll submit to the pre-commit torture, considering that this PR doesn't make it worse. We can re-visit if we decide to use a different mechanism to format our markdown file.

I'm going to land this as-is. The less-than-optimal parts of this are:

We'd prefer to use our own formatter to format these Python snippets rather than Black. I agree this would be better (dogfooding is good!), but there currently isn't a ruffen-docs equivalent to blacken-docs. (check_docs_formatted.py will check formatting using our formatter, but won't do autofixes, and the capacity to do autofixes to me feels crucial for ease of development.)

We'd prefer for these snippets to be formatted concisely, as if they were stubs. Black has a --pyi flag but it's not possible to pass that flag to blacken-docs. To me, having an autoformatter feels much more important than the specific formatting choices it makes. Possibly we could file a feature request with blacken-docs asking them to add a --pyi flag.

We're not necessarily wild about doing all our linting via pre-commit for this repo: it's not such a popular tool in the Rust ecosystem as it is in the Python ecosystem, it can be slowish, and we don't want to require contributors to have to download another tool if they want to contribute. I agree that in a perfect world we'd use a faster tool that comes builtin with cargo to do our linting, but I'm not sure such a tool exists right now. We already do a bunch of our linting via pre-commit currently, and the existing hooks we have are already very picky about Markdown files, so this PR doesn't change much in this regard.
I'd be happy to review another PR that gets rid of our .pre-commit-config.yaml file in favour of a justfile to coordinate all our linting tools, but that's outside the scope of this PR. (Even if we switched to using just rather than pre-commit, that would also still be a separate tool that we'd require contributors to install, so this wouldn't fully solve the problem.)

We'd prefer for the --line-length=130 flag to be set in some kind of persistent configuration, so that it's easier for folks to run blacken-docs without having to install pre-commit if that's what they'd prefer. Unfortunately blacken-docs does not read any configuration files directly, and because of the way it runs Black, Black-as-invoked-by-blacken-docs also ignores all [tool.black] configuration files in any pyproject.toml files in the repo.

Overall, then, lots of issues here and potential for improvement, but I still think the benefits outweigh the costs here. Lots of these things could possibly be improved by us building our own ruffen-docs tools!


apollo.nuxtjs.org blocked by uBlock ad blocker

Sorry for abusing the issue tracker but as I can't access your website I have no way to find another way to contact you.

Ok, parts of the site is blocked by uBlock on Chrome. No idea why that is or if you want to fix anything.
GET https://apollo.nuxtjs.org/_nuxt/SocialIcons-4cc53d7e.mjs net::ERR_BLOCKED_BY_CLIENT
TypeError: Failed to fetch dynamically imported module: https://apollo.nuxtjs.org/_nuxt/fluid-93051cdb.mjs

Reported: https://github.com/uBlockOrigin/uAssets/issues/15583

It was caused by a filter for */SocialIcons/*. It should be fixed in the next release of easylist:
https://github.com/easylist/easylist/commit/2d314d4ff7f8c0c48ecf2f305a22b4f687da2d38
Leaving this open FYI.

I encountered this issue myself today.
Have been experiencing some weird bugs where Graphql data wasn't working correctly.
Disabling uBlock fixed the issue.


I have facing issue while running ui

2024-05-02 05:49:08.206 Uncaught app exception Traceback (most recent call last):   File "/usr/local/lib/python3.11/site-packages/streamlit/runtime/scriptrunner/script_runner.py", line 565, in _run_script     exec(code, module.__dict__)   File "/home/user/app/main.py", line 187, in <module>     view(Model())   File "/home/user/app/main.py", line 64, in view     Dashboard().view(Dashboard.Model())   File "/home/user/app/views/dashboard.py", line 61, in view     with st.container():          ^^^^^^^^^^^^^^   File "/usr/local/lib/python3.11/site-packages/streamlit/runtime/metrics_util.py", line 332, in wrapped_func     result = non_optional_func(*args, **kwargs)              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/usr/local/lib/python3.11/site-packages/streamlit/elements/layouts.py", line 74, in container     return self.dg._block()            ^^^^^^^^^^^^^^^^   File "/usr/local/lib/python3.11/site-packages/streamlit_nested_layout/nest.py", line 22, in _nestable_block     ancestor_block_types = list(dg._ancestor_block_types)                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ TypeError: 'function' object is not iterable

You should debug Dashboard.view code, see stack trace. Here same UI works: https://huggingface.co/spaces/katanaml-org/sparrow-ui


balancesForAddress does not reflect balance for several minutes

A token was sent to an address and the explorer presented the validity of the token transfer immetiatly:

https://explorer.bitcoin.com/bch/tx/d4ea12959dcb476e4e9149095300572ef9f88e88ca5e901320ecb2f674c6a8e3#o=1

Nevertheless both the explorer and the REST services reported "no balance" for several minutes:

https://explorer.bitcoin.com/bch/address/1H4iZcMnaJWGgkYVfqqdSHtDx2gyeSGgSV
https://rest.bitcoin.com/v2/slp/balancesForAddress/simpleledger:qzcrtar0uj83gme5rckr6ug5jk6fymcsxv4czmypeh

Note: The balance is now correctly reported.
Since most of the time time balances are correctly reported after a few seconds and another times after a few minutes a seemingly reasonable 1 minute interval is not enough to ensure a result.
Is there an "official" latency, that must be assumed, between broadcasting the transaction and the update of balances?

I think this is a case of things being in flux. Minor bugs are still being ironed out in SLPDB and rest.bitcoin.com.
Please keep an eye on this failure mode. If you find a way to consistently reproduce it, please share it with us.
I really appreciate you taking the time to report these issues.


Sprite size inconsistency depending on parent.

Expected Behavior
Two sprites that are set up with identical sizes should be rendered as the same size.
Current Behavior
The 2 identical sprites are rendered at different sizes.
Steps to Reproduce
https://codepen.io/Lancer611/pen/YzKVEEd
The green squares are set up with identical values.  However, s3 is added as child of s, while t3 is added as child of t2.  Why does the parent affect the rendered size of the child?  Shouldn't the child's size be unaffected by its parent?
Environment

pixi.js version: 5.1.1
Browser & Version: Chrome 75.0.3770.142
OS & Version: Windows 10
Running Example: https://codepen.io/Lancer611/pen/YzKVEEd

Because its same in Flash.
There are many hacks that can help with that, I dont know even which one to recommend ...
My attempt at making frame size independent from scale was rejected 4 years ago.


[#456] #EXTEND 'assemblyName: DotNet.Testcontainers; function: WithDo…

…ckerEndpoint ' {Extended method with Docker.DotNet.Credentials parameter and made required changes to related code to pass credentials to Docker.DotNet.DockerClientConfiguration ctor }

I'll close this in favor of https://github.com/HofmeisterAn/dotnet-testcontainers/issues/370#issuecomment-1146842098. You can now use the latest version to configure / authenticate the client.


XYZ → LUV quesionable results

I’m using your converter http://colormine.org/convert/xyz-to-luv to check XYZ→LUV space translations in color-space.js.
I’ve implemented conversion by formulas from here: http://www.brucelindbloom.com/index.html?Eqn_XYZ_to_Luv.html (same as wikipedia's).
Strangely, I get different results with your convertor.
Your converter gets xyz(100,0,0) → luv [6.3, 20.2, 3.87], whereas it is impossible according to the XYZ→LUV formula. (If Y is 0 L can’t be anything but 0).
I suppose it is because you’re converting XYZ to RGB first, and then RGB to LUV. But is it a proper way to do the conversion?

Hi @tompazourek , as you know I'm implementing another library to handle color spaces, but more focused on light spectral data.
I've looked into your code to learn about chromatic adaptations, but what I've seen in books and articles doesn't match ColorMine's behavior.
As fas as I know, there are more than one chromatic adaptation transform method (different matrix and different non-linear pre & post transformations: Von Kries, Bradford, Sharp, ...). Even more, some methods apply the chromatic adaptation in the LMS space and others apply the chromatic adaptation in the CIE's RGB color space).
What transformation did you choose..? and why? (I don't know barely nothing about colorimetry, I'm a beginner).
Because this great number of options, I'm modifying ColorSharp in order to apply the chromatic adaptation only if the user requests it, and giving tho him the full control of the process. Maybe it's a bad idea?

Hi @castarco, as you can see here 1, the library supports multiple ways of chromatic adaptation. You can even implement your own and use it in the conversion.
The ColourfulConverter facade uses the Von Kries as the chromatic adaptation method 2 with Bradford LMS transformation matrix 3.
I chose Bradford as the default since I saw it used the most, it's the  method of CMCCAT97 and CAT97s color appearance models 4 and it is said to be used in Adobe Photoshop as well 5.


TypeError: Cannot read property 'split' of undefined

node -v
v6.10.1
npm -v
3.10.10
git-labelmaker
? What is your GitHub Access Token?
? What is your master password, to keep your access token secure? ******
TypeError: Cannot read property 'split' of undefined
at module.exports (/usr/lib/node_modules/git-labelmaker/bin/modules/readRepo.js:14:32)
at Promise.all.then (/usr/lib/node_modules/git-labelmaker/bin/index.js:38:19)
For now I have uninstalled git-labelmaker. It is promising though ;-)

Thanks for submitting, sorry about the issue!
This has been fixed in https://github.com/himynameisdave/git-labelmaker/pull/66 and will be published in v0.9.0 which I will release today.


3 Namespaces counted but only 2 available

Steps to reproduce

Use the docker-compose.yml or docker-compose.insecure.yaml to start a new Portus 2.4.3 instance.
Create the Admin user.
Login to the dashboard und check the counter on top right for the namespaces. It shows 3. But only the admin namespace and the global namespace exists. What ist number 3?

Expected behavior: The namespace count shows 2.
Actual behavior: The namespace count shows 3.

Deployment information
Deployment method:
https://github.com/SUSE/Portus/blob/master/examples/compose/docker-compose.insecure.yml
version: "2"

services:
  portus:
    image: opensuse/portus:head
    environment:
      - PORTUS_MACHINE_FQDN_VALUE=${MACHINE_FQDN}

      # DB. The password for the database should definitely not be here. You are
      # probably better off with Docker Swarm secrets.
      - PORTUS_DB_HOST=db
      - PORTUS_DB_DATABASE=portus_production
      - PORTUS_DB_PASSWORD=${DATABASE_PASSWORD}
      - PORTUS_DB_POOL=5

      # Secrets. It can possibly be handled better with Swarm's secrets.
      - PORTUS_SECRET_KEY_BASE=${SECRET_KEY_BASE}
      - PORTUS_KEY_PATH=/certificates/portus.key
      - PORTUS_PASSWORD=${PORTUS_PASSWORD}

      # SSL
      - PORTUS_CHECK_SSL_USAGE_ENABLED='false'

      # Since we have no nginx in insecure mode, portus have to
      # serve the static files
      - RAILS_SERVE_STATIC_FILES='true'
    ports:
      - 3000:3000
    depends_on:
      - db
    links:
      - db
    volumes:
      - ./secrets:/certificates:ro

  background:
    image: opensuse/portus:head
    depends_on:
      - portus
      - db
    environment:
      # Theoretically not needed, but cconfig's been buggy on this...
      - CCONFIG_PREFIX=PORTUS
      - PORTUS_MACHINE_FQDN_VALUE=${MACHINE_FQDN}

      # DB. The password for the database should definitely not be here. You are
      # probably better off with Docker Swarm secrets.
      - PORTUS_DB_HOST=db
      - PORTUS_DB_DATABASE=portus_production
      - PORTUS_DB_PASSWORD=${DATABASE_PASSWORD}
      - PORTUS_DB_POOL=5

      # Secrets. It can possibly be handled better with Swarm's secrets.
      - PORTUS_SECRET_KEY_BASE=${SECRET_KEY_BASE}
      - PORTUS_KEY_PATH=/certificates/portus.key
      - PORTUS_PASSWORD=${PORTUS_PASSWORD}

      - PORTUS_BACKGROUND=true
    links:
      - db
    volumes:
      - ./secrets:/certificates:ro

  db:
    image: library/mariadb:10.0.23
    command: mysqld --character-set-server=utf8 --collation-server=utf8_unicode_ci --init-connect='SET NAMES UTF8;' --innodb-flush-log-at-trx-commit=0
    environment:
      - MYSQL_DATABASE=portus_production

      # Again, the password shouldn't be handled like this.
      - MYSQL_ROOT_PASSWORD=${DATABASE_PASSWORD}
    volumes:
      - ./lib/portus/mariadb:/var/lib/mysql

  registry:
    image: library/registry:2.6
    environment:
      # Authentication
      REGISTRY_AUTH_TOKEN_REALM: http://${MACHINE_FQDN}:3000/v2/token
      REGISTRY_AUTH_TOKEN_SERVICE: ${MACHINE_FQDN}:5000
      REGISTRY_AUTH_TOKEN_ISSUER: ${MACHINE_FQDN}
      REGISTRY_AUTH_TOKEN_ROOTCERTBUNDLE: /secrets/portus.crt

      # Portus endpoint
      REGISTRY_NOTIFICATIONS_ENDPOINTS: >
        - name: portus
          url: http://${MACHINE_FQDN}:3000/v2/webhooks/events
          timeout: 2000ms
          threshold: 5
          backoff: 1s
    volumes:
      - ./lib/portus/registry:/var/lib/registry
      - ./secrets:/secrets:ro
      - ./registry/config.yml:/etc/docker/registry/config.yml:ro
    ports:
      - 5000:5000
      - 5001:5001 # required to access debug service
    links:
      - portus:portus

I created the secrets with the example command:
openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout portus.key -out portus.crt

Portus version: 2.4.3@5a616c0ef860567df5700708256f42505cdb9952

If I created a second user, the dashboard shows me 4 Namespaces. But if I check the Namespace page, I can only see 3 Namespaces. So the dashboard counts wrong +1.

This issue still exists.

+1

+1


Make Credentials usage more flexible

Hey, I'd like to propose 2 improvements into how Credentials are handled right now:

Use ICredentials instead of NetworkCredential. It would allow passing the CredentialCache which may be required in some cases, for example.

Optionally, allow sending Credentials with request right away.

By default, Credentials will send only after server return 401 status code.
But it's often a good idea to reduce bandwidth and requests count when dealing with CDNs which do require auth, so it's preferable to send the Credentials with the initial request instead.
It's possible to achieve by extending WebClient (if you will not switch to HttpClient) and setting WebRequest.PreAuthenticate to True, like it's shown in this Microsoft Learn example.
Alternatively, it's possible to do this with manually constructing and adding the HttpRequestHeader.Authorization header from the Credentials right to the initial request. This will be possible after #59 implementation, but still would be nice to just have an option to do this, like:
context.Downloader.Credentials = myNetworkCredential;
context.Downloader.PreAuthenticate = true;

and allow it to do all the rest under the hood.

All IDownloader-derived downloaders now expose credentials as ICredentials.
Also, all WebRequests created by the downloaders now have PreAuthenticated flag set.
For the sake of completeness, I introduced PreAuthenticatedWebClient class that always returns a PreAuthenticated WebRequest.
This will be released with the next version!


Install via Homebrew

Would be great if users will have ability to install Spaceship using Homebrew. Don't know how to do this. Can anyone help?

This doesn't really seem to be a solution for brew to install, it seems like the current support for zsh-specific plugin managers is a good solution.

@jwkicklighter That does also count for npm then? I think options like npm and brew make it much faster / easier to install a theme. Especially if you are not familiar with zsh plugin managers.

I think brew is nice and we definitely need to give users a possibility to install 🚀 via this tool.

Homebrew don't allow direct write to /usr/local/share/zsh-functions. So, I had to copy install sections and lib folders to the destination as zsh_function. Can you guys test it ?
brew install salmanulfarzy/spaceship-prompt/spaceship-prompt

Homebrew Formula : https://github.com/salmanulfarzy/homebrew-spaceship-prompt/blob/master/Formula/spaceship-prompt.rb

@salmanulfarzy what about git clone to ~/.zfunctions folder?

@salmanulfarzy what about git clone to ~/.zfunctions folder?

I haven't tried with ~/.zfunctions. Because installation to ~/.zfunctions is required only if user don't have access to /usr/local/share/zsh/site-functions (In case of non-root Linux user). Here Homebrew allows us to write there as zsh_function, But not directly. If writing to ~/.zfunctions is possible with Homebrew, Then it might also require user to modify $fpath.
Problem with the current approach I've followed is if user have similarly named directories at zsh/site-functions, It's going to break the prompt.

FYI, there is a formula with spaceship-prompt v3.11.2 in homebrew-core now, it works well.
brew install spaceship

Already implemented. Just hit brew install spaceship

@denysdovhan nothing happens after installing via homebrew?
What I might be doing wrong?
==> Downloading https://ghcr.io/v2/homebrew/core/spaceship/manifests/3.15.0
Already downloaded: /Users/renoirtech/Library/Caches/Homebrew/downloads/828af6113767d6528cb6320a5f9ec479c1291205dd860fae6483c19c25d4a09b--spaceship-3.15.0.bottle_manifest.json
==> Downloading https://ghcr.io/v2/homebrew/core/spaceship/blobs/sha256:e283232d5b5b4695526dd2ad3796542e18cb03c262da79d3560d1
Already downloaded: /Users/renoirtech/Library/Caches/Homebrew/downloads/34ae384e832993c7d75b4ef6f869b9541bd83061aeb46a4c03453029659a6efd--spaceship--3.15.0.all.bottle.tar.gz
==> Pouring spaceship--3.15.0.all.bottle.tar.gz
==> Caveats
zsh functions have been installed to:
  /opt/homebrew/share/zsh/site-functions
==> Summary
🍺  /opt/homebrew/Cellar/spaceship/3.15.0: 55 files, 122.8KB```

Is there something additional to configure?

I have the same problem
autoload -U promptinit; promptinit
prompt spaceship
but this works

@denysdovhan nothing happens after installing via homebrew?
What I might be doing wrong?
==> Downloading https://ghcr.io/v2/homebrew/core/spaceship/manifests/3.15.0
Already downloaded: /Users/renoirtech/Library/Caches/Homebrew/downloads/828af6113767d6528cb6320a5f9ec479c1291205dd860fae6483c19c25d4a09b--spaceship-3.15.0.bottle_manifest.json
==> Downloading https://ghcr.io/v2/homebrew/core/spaceship/blobs/sha256:e283232d5b5b4695526dd2ad3796542e18cb03c262da79d3560d1
Already downloaded: /Users/renoirtech/Library/Caches/Homebrew/downloads/34ae384e832993c7d75b4ef6f869b9541bd83061aeb46a4c03453029659a6efd--spaceship--3.15.0.all.bottle.tar.gz
==> Pouring spaceship--3.15.0.all.bottle.tar.gz
==> Caveats
zsh functions have been installed to:
  /opt/homebrew/share/zsh/site-functions
==> Summary
🍺  /opt/homebrew/Cellar/spaceship/3.15.0: 55 files, 122.8KB```

Is there something additional to configure?

I have the same problem
autoload -U promptinit; promptinit
prompt spaceship
but this works

Never worked for me. I always have to install via NPM (which seems a little odd since in my head NPM is for node stuff only).

Homebrew doesn't work. Always have to use npm as well which works fine.

Homebrew doesn't work. Always have to use npm as well which works fine.

Adding what @denysdovhan suggested to .zshrc works.


Add patch and get endpoint for users

Ticket
https://github.com/navapbc/template-application-flask/issues/4
Changes
This PR adds a GET and PATCH endpoint for the user model to the template repo. This follows up work that added a POST endpoint and related components.
Context for reviewers
GET endpoint is pretty routine, give an ID, get the model.
PATCH is mostly routine, although the conventions there are slightly less defined. Any unset fields aren't modified, only the set fields. The primary complexity was adjusting roles. It might make more sense to have these as their own separate dedicated endpoint (something like user-add-role and user-remove-role) if this is deemed too complex. It basically does a set-diff to see what needs to be added/removed to get to the desired state.
Are there any other common-ish endpoint types you would like to see added?
Testing
Create a user via the POST endpoint:

You can GET them:

PATCH request:

PATCH response:

GET again after the PATCH:

@chouinar should I still review this PR, or would we end up changing it anyways based on the decision around openapi framework (switching from connexion)?

I'd still like to merge this as that switch will only adjust the model definitions. The more endpoints I have to work with, the more I can document how it's different as I switch it over.


Using Docker BuildKit as a default

Explain the changes
Using Docker BuildKit as a default

In the Makefile we can pass DOCKER_BUILDKIT="DOCKER_BUILDKIT=0" to disable BuildKit
When we use podman we will not use BuildKit as it is not supported
The test image will now use the untar Directory of noobaa.

Signed-off-by: liranmauda<EMAIL_ADDRESS>

doesn't break builds US/DS?

doesn't break builds US/DS?

No, DS build doesn't use any of those files.


Warning: Can't find file "MachDeps.h" in directories GHC

Hlint version: v3.1.6
OS: Fedora 32
Repo: The GHC namespace in base

Warning: Can't find file "MachDeps.h" in directories
	GHC
	.
  Asked for by: GHC/Enum.hs  at line 23 col 1
hlint: #error Unhandled value for WORD_SIZE_IN_BITS
in GHC/Enum.hs  at line 672 col 1
CallStack (from HasCallStack):
  error, called at ./Language/Preprocessor/Cpphs/CppIfdef.hs:113:21 in cpphs-1.20.8-DevT7HkEKU3DDQgUoHVnJY:Language.Preprocessor.Cpphs.CppIfdef

It feels related to https://github.com/ndmitchell/hlint/issues/228

Hi @Kleidukos , I see you've closed this out. I have a bunch of questions 😀 :

Is it closed because you've determined it's not a HLint problem?

If so, what was the problem and what was it's resolution?

Is HLint in general working OK on Fedora 32?
Are you using HLint with ghc-8.10.1?

If so, out of interest, have you tried with an older GHC?

Hi @shayne-fletcher ! The real issue I had is actually on https://github.com/ndmitchell/hlint/issues/1075

Is it closed because you've determined it's not a HLint problem?
'tis not! I had forgotten to add the CPP include paths

Is HLint in general working OK on Fedora 32?
Like a charm!

Are you using HLint with ghc-8.10.1?
It's compiled with lts-14.20, so 8.6.5.

Is HLint in general working OK on Fedora 32?

Like a charm!

This is very satisfying to hear 😍 .

Are you using HLint with ghc-8.10.1?

It's compiled with lts-14.20, so 8.6.5.

Quite the stress test then as it will be using ghc-lib!

@shayne-fletcher Do you have any wish regarding how I'm compiling it while working on GHC? (we take this discussion elsewhere, by the way)

@shayne-fletcher Do you have any wish regarding how I'm compiling it while working on GHC? (we take this discussion elsewhere, by the way)

No, it's all good!


[AttributeAccessInterface] Handle write is to a single list element

Problem
What if the write is to a single list element? Or an append/delete operation?
We need to update ConcreteAttributePath to include lixt index field before handle those cases
Proposed Solution
<suggested fix, suggested enhancement>

Is this resolved now?