Back to top Scroll button feature can be added

We can have a button of back to top from bottom. With time when content will increase It will be very useful.

I would like to work on this.

I want to contribute , Assign me under Apertre'24

Please complete the assigned task first, then i will assign the other tasks to you @AnitSarkar123


Setup docker configuration

I have set up Dev containers for backend and frontend.
To use the new setup simply open the folders backend-cal and frontend-cal either in vs code or in Code spaces and click on the reopen in container prompt
If this does not show up please ensure you have the dev containers extension installed.
If any additional programs or VS code extensions are required to be added, please post a comment on this issue with the name of the software / Vs code extension ID


chore(main): release 1.22.1

:robot: I have created a release beep boop
1.22.1 (2024-08-13)
Code Refactoring

reformat response (8a40e87)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/Andesite-Lab/Core/releases/tag/v1.22.1 :sunflower:


Last seen not saved

zigbee2mqtt add-on version (if edge, please report commit hash):
<IP_ADDRESS>
Operating environment (HassOS, Virtual Machine, Device/platform running Home Assistant):

Hassos 0.118.4
Description of problem:
If i change lastseen from none to another value in frontend, it work but if i restart zigbee2mqtt it return to "none"
Your entire configuration from the frontend (with sensitive fields redacted):
// replace this line with your pasted configuration

Your logs from Home Assistant

This is not a problem of the add-on. Try and post an issue on z2m issue tracker list for this. We won't be able to help you here.


PHP 8 support

Codecov Report
Patch and project coverage have no change.

Comparison is base (4ce1069) 100.00% compared to head (ec9ec4f) 100.00%.

Additional details and impacted files
@@             Coverage Diff             @@
##              master        #6   +/-   ##
===========================================
  Coverage     100.00%   100.00%
  Complexity        27        27
===========================================
  Files              1         1
  Lines             59        61    +2
===========================================
+ Hits              59        61    +2

Flag
Coverage Δ

unittests
100.00% <ø> (ø)

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

Files Changed
Coverage Δ

src/Residue.php
100.00% <ø> (ø)

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


⚠ PrivateHD has degraded performance

In acbbc23, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 5165 ms

Resolved: PrivateHD performance has improved in 9090fc4.


[Status checker] Add color coding to status and status-all commands; update status-upgrade to detect install version and check components based on 3.3 or 3.4 instance version

Added secure-tunnel checks to status-all and status-upgrade output
Added color-coding to oc waiops status and oc waiops status-all outputs to visually indicate output status, similar to how oc waiops status-upgrade handles its output. This is done with green indicating success/completion/etc. and red indicating incomplete/failure/etc.
Updated color-coding on upgrade-status to match scheme of status and status-all
As a result of adding color to the output to indicate component state, this means that the status and status-all commands now actively check components' status, as opposed to simply passively printing the components' outputs as it did previously, making the commands more immediately useful or actionable for users. See comment below for example of how the color-coding looks.
Updated oc waiops status-upgrade section of script to automatically check the versions of components automatically based on the install version of the CSV (3.3 or 3.4)
Created notation in oc waiops status-upgrade in the event a dev build (v0.1) is encountered that it will be checked against v3.4 component versions
Updated script version to 0.0.7

In the comments below, I pasted some screenshots of what the color-coded outputs look like for status and status-all, in addition to new checks on status-upgrade depending on the version installed.

I combined PR #77 and this one into a single PR to reduce confusion. #77 is now closed.

Example oc waiops status output with all components reconciling as expected (all component sections are green):

If something is wrong, that section with the failing or incomplete component will be shown as red. This is done at the section level to maintain the same output format (highlighting just the individual component in red isn't possible since this would mean a separate oc command would need to be made for that specific "red" component, which would make the output a lot longer and verbose with more separate individual headers per component. This is the best compromise to maintain consistency):

To be clear, the status is color-coded for both oc waiops status and oc waiops status-all now, in addition to the existing color-coding for oc waiops status-upgrade, meaning that all three commands now actively check component status rather than just printing it out.

In the event someone runs oc waiops status-upgrade on an internal dev build denoted v0.1 (for example, on a BVT build off the main branch), in such a situation, the checker will output a message at the beginning noting the checks will be against release-3.4 component versions and that the checker is designed to check upgrades to v3.3 and to v3.4 only.
Here's an example of what is outputted when oc waiops status-upgrade is run against a main branch BVT build (which often has advanced component versions ahead of release-3.3/release-3.4):

Awesome work with this @siyer-123.  Two questions:

Should we mark whole section red if only some items in that block are red  or just mark the specific items red?
I think this won't be accurate for 3.1.x &  3.2.x.  For those versions should we just exit?

Addressed @kvijai82's comments in the latest commit and updated my previous comment above with an up-to-date screenshot showing what would happen in a status-upgrade output for v3.2/v3.1/etc.


Please invite me to this organization.

I have sent an invite in an earlier open issue, in case the invite expires, feel free to reopen this issue, thanks : )


cargo build --release fails for ballista-scheduler

Describe the bug
The cargo build --release command documented here fails:

To Reproduce
git clone git@github.com:apache/arrow-ballista.git -b 0.9.0
cd arrow-ballista
cargo build --release

Expected behavior
Expected ballista-scheduler and ballista-executor binaries to be built into the target/release directory
Additional context
ubuntu 22.04 x86 ballista version 0.9.0

I checked out the master and 0.10.0 branches and both built fine.

I've tried the 0.10.0 branch build on x86 MacOS and Ubuntu 22.04...

...and on Ubuntu 22.04 on ARM64...

...and all looks good w/ the install, rust-wise, so closing this


Week3test

Need some help figuring out what's going on error wise

Program works with comments, will look into on click issue / needing on load hello()


Sample Tech Doc page has incorrect element nesting

The Responsive Web Design Projects Build a Technical Documentation Page sample codepen has

Introduction

which throws an error when run through a validator, The  element cannot be a child of the
 element
Browsers do support it but it's still incorrect coding. It would be better to refactor the code to something like;

Introduction

so it follows the HTML spec where only the list element is a direct decendant of the ul element.

I can take this one.

It has been fixed some time ago https://github.com/freeCodeCamp/testable-projects-fcc/pull/750 the Codepen is just not being updated for some reason. I can open an issue and ask if someone can update the Codepen.

Looks like this has been fixed so it can be closed - let me know if I'm mistaken.


x/tools/gopls: unsupported version 0 of Verneed record

gopls version

v0.9.3
go env

go env Output
$ go env
GO111MODULE="auto"
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/linux/.cache/go-build"
GOENV="/home/linux/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOMODCACHE="/home/linux/.go/pkg/mod"
GOOS="linux"
GOPATH="/home/linux/.go"
GOPROXY="https://mirrors.aliyun.com/goproxy/,direct"
GOROOT="/home/linux/sdk/go1.19"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/linux/sdk/go1.19/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.19"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOWORK=""
CGO_CFLAGS="-I/home/linux/rocksdb/include"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-L/home/linux/rocksdb -lrocksdb -lstdc++ -lm -lz -lbz2 -lsnappy -llz4 -lzstd"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2598684643=/tmp/go-build -gno-record-gcc-switches"

What did you do?

gopls version or vscode code tips
What did you expect to see?
gopls version or code tips
What did you see instead?
unsupported version 0 of Verneed record
Editor and settings

vscode

"go.useLanguageServer": true,

Logs

Hi, this looks like some corruption of your gopls binary (compare #46680).
How did you install and update gopls? Did you use go get, or something else? If you installed from the command line, which command exactly did you execute?

Hi, this looks like some corruption of your gopls binary (compare #46680).
How did you install and update gopls? Did you use go get, or something else? If you installed from the command line, which command exactly did you execute?

I tried three methods

go install golang.org/x/tools/gopls@latest
go install<EMAIL_ADDRESS>vscode Go Install/Update tools

The three results are the same

I don't think this is related to gopls. It looks like this is some form of corruption of your shared libraries. For example:
https://bugzilla.redhat.com/show_bug.cgi?id=203311
Sorry, I don't think we'll be able to help you debug this. Please reopen if you think there is something gopls or go specific that is leading to this error.


[enhancement]: Support for custom upscalers rather than ESRGAN

Is there an existing issue for this?

[X] I have searched the existing issues

Contact Details
No response
What should this feature add?
Invoke has a folder for upscaling models but it really has no importance. The WebUI only uses ESRGAN. Is there any chance of support for custom upscalers in future releases? I drop them into the folder but looking through the documentation I could only find reference to ESRGAN. Sorry if there is already a request for this, I did look through the issues but could not find anything similar.
Alternatives
No response
Aditional Content
No response

Pleeease??


Re-center pagination

For some reason, the pagination of search results in the Hub seems to have
become left aligned instead of centered underneath search results. Can we
move them back to center?

Submitted pull request to resolve this issue.


CalculateDiscountTotal

discount_total
//sum(items.discount_total)+sum(discounts.amount)

Read only, auto calculated field in API


KVStore improvements: JSON in & out, without exceptions

Extracted from #135:

I am tempted to always have valid JSON in and out of the kvstore. The present exception being the Get interface, which returns a Golang array of JSON objects. It could return a JSON array of all the Added objects instead.

issue now reported in:
https://github.com/veraison/services/issues/87


chore(main): release 1.1.1

:robot: I have created a release beep boop
1.1.1 (2024-05-22)
Bug Fixes

fix docker image name (4abbc88)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wert2all/timeline-backend/releases/tag/v1.1.1 :sunflower:


Rule for only one jsx react element per line?

I would like to disallow multiple elements/components being opened on one line:
<Outer><Inner/></Outer>

and fix to:
<Outer>
  <Inner/>
</Outer>

I searched all over and could not find something like this. Thank you.

Would this rule also warn on  and fix to:

?

@ljharb Yes indeed.
However, maybe it could be configurable to conditionally support either of the following variants:
{whatever()}

  {whatever()}

Sounds great; want to make a PR? :-D

@ljharb I would be happy to when I get the chance. Never worked in this codebase before, but I assume jsx-max-props-per-line.js is probably a good starting reference point.

@ljharb Done in #1497

It's merged. Closing


add different options to change histogram settings (bin size etc.)

I started adding more options to customize histogram plots. It's now possible to
set different bin numbers, bin ranges, bin sizes, create cumulative
and normalized histograms.
To keep the % func for Trace a little cleaner, I added a parseHistogramFields func, which adds the histogram related fields to the result.
I'll add an example in the soon, that's why I mark this WIP.

Finally managed to fix some remaining bugs and add a few example plots. Sorry it took so long. :)

cheers!


Sfr/optiongroup and friends

Please review my code and if its okay include it to your repository. Please review carefully I'm new in rust.
As @alexcrichton has suggested some more information to this PR.
I have added a example repository here.

The first patch is the base for the other two patches. I introduce a content information for Opt and OptGroup (named variant) to differ between some modes. The first variant is OptionGroup for the current implementation.
The second patch use the first patch. It introduce a new variant Separator and the public accessible function separator() which results in a blank line at usage() call.
The third patch add two new functions description() and description_header() for the new variant Description which results in some desciptive text at usage() call.

Example separator:
This ...
opts.optflag("R", "recursive", "operate on files and directories recursively");
opts.separator();
opts.optflag("H", "", "if a command line argument is a symbolic link to a directory, traverse it");

... results in this:
[...]
    -R, --recursive     operate on files and directories recursively

    -H                  if a command line argument is a symbolic link to a
                        directory, traverse it
[...]

Example description*():
This:
[...]
opts.optflag("R", "recursive", "operate on files and directories recursively");
opts.description_header("Flags for -R");
opts.description("The following options modify how a hierarchy \
                  is traversed when the -R option is also specified.  \
                  If more than one is specified, only the final one \
                  takes effect.")
opts.optflag("H", "", "if a command line argument is a symbolic link \
                       to a directory, traverse it");
[...]

The result is:
[...]
    -R, --recursive     operate on files and directories recursively

    Flags for -R:
        The following options modify how a hierarchy is traversed when the -R
        option is also specified. If more than one is specified, only the final
        one takes effect.
    -H                  if a command line argument is a symbolic link to a
                        directory, traverse it
[...]

I have a little trouble understanding what's going on here, could you expand the commit PR description to include what this is along with some rationale? It'd also be great to have some tests showcasing the new functionality as well!

I have updated the commit message and remove some old examples.

Hm ok, interesting! Do you know if other getopts-like implementations have support for things like this? The current implementation seems to go out of its way to ensure that descriptions are formatted correctly, so it seems like it may be worth bolstering up that logic instead of adding new methods?

I don't know. A comment on #13 (from steve) looks like that its possible with docopt. But I'm not sure.
Can you give me a hint what's your idea for a better implementation. My first idea (beside this approach) was a new struct optiongroup for adding of several options. But I think it takes the flexibility to do some more formatting like a blank line etc...

docopt is a little different just because it parses the help string rather than programmatically constructing it. I'm a little hesitant to add a litany of methods just for helping format some descriptions, it also looks like it may be intended for delineating option groups or possibly providing extended help text for an option?
I was thinking it would be worth perhaps parsing the description of an option for the former case to do some nicer formatting, and then maybe one method could be added for option groups perhaps rather than for "formatting in general"

Other option parsers do support option groups.  For example, both glibc's argp and gtk's option parsers support this; as did the older popt.
http://www.gnu.org/software/libc/manual/html_node/Argp-Children.html#Argp-Children
https://developer.gnome.org/glib/stable/glib-Commandline-option-parser.html
IMO it would be better to have child groups handled via grouping objects rather than calls intended to change just the formatting of the help output.

Okay - I will rework my patchset at weekend.

Closed, replaced by #35


Cannot build 5.22.x due to cffi error

Hello,
I cannot build the 5.22.0 or 5.22.1 Docker image (I used to build them since 4.x without problem).
When I do :
 cd build/mattermost
 git fetch
 git checkout tags/5.22.1
 docker build app --build-arg edition=team --build-arg PUID=1000 --build-arg PGID=1000 -t mm_app:5.22.1 --no-cache

It fails with :
Executing busybox-1.28.4-r3.trigger
Executing ca-certificates-20191127-r0.trigger
OK: 272 MiB in 80 packages
Collecting wal-e<1.0.0
  Downloading https://files.pythonhosted.org/packages/7a/67/4da340652303e3adb26f6e9aa97b2118dbe5cd17be87e8a21dff9e9bc507/wal-e-0.9.2.tar.gz (100kB)
Collecting envdir
  Downloading https://files.pythonhosted.org/packages/75/dd/817dc77edf4807fc2c29e28046ab83aa7ccfe27e79d24ca37d7aaa1e36bb/envdir-1.0.1-py2.py3-none-any.whl
Collecting gevent>=1.0.2 (from wal-e<1.0.0)
  Downloading https://files.pythonhosted.org/packages/72/8b/20c2ebb3bda3f748f251115831568be202456138e088d3f25d24bf430690/gevent-20.4.0.tar.gz (5.5MB)
  Could not find a version that satisfies the requirement cffi>=1.12.3 (from versions: )
No matching distribution found for cffi>=1.12.3
You are using pip version 10.0.1, however version 20.1b1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
The command '/bin/sh -c apk add --no-cache       build-base       curl       libc6-compat       libffi-dev       linux-headers       python-dev       py-pip       py-cryptography       pv       libressl-dev     && pip --no-cache-dir install -c pip-constraints.txt 'wal-e<1.0.0' envdir     && rm -rf /var/cache/apk/* /tmp/* /var/tmp/*' returned a non-zero code: 1

Build is done on Debian 9 (stretch) but host OS shouldn't matter much when building a Docker image.
If you need any additional information feel free to ask.

See https://github.com/mattermost/mattermost-docker/issues/469
There is also an open PR (https://github.com/mattermost/mattermost-docker/pull/471). You can apply the changed if you want.

Thanks, it works with the fix. Since there are other issues opened already (sorry I did search but I couldn't find them) I'll close that one.


Language menu - sometimes too slow to open

Description
When using the attached file, the language menu can take a long time to open; sometimes 10 seconds or more.
Possible solutions

Improve performance
After a certain amount of time (5 seconds?), replace the menu with a text box input instead?

Additional requirements
By default, it says "Please select a file first". When the user selects a file, can you change the text to say "Processing file for languages..."?

Attachments

BFR6-Female-Questionnaire-v1-rmn.xlsx.zip

@bciar Works like a charm.


add embedding with different size(0) of tensor and metadata

Thanks for your work!
When I use the add_embedding, it requires the tensor and metadata has the same length.
However, when I have multiple columns for the metadata(muti labels), I need to have a header for the metadata(n+1 rows). Otherwise, the tensorboard raise an error saying "Multi-column metadata should have a header"..
So how should I include it in the metadata if it leads to different size(0)? Thank you!
I tried to save two metadata files with different global_step and replace the one without header with the one with header.

ed1643f This commit should handle your case.
What's your tensorboardX version?

Thanks!


feat: add just syntax checker

Integrate our new just syntax checker into the build action.
I assume this is the last repo that needs this, but if I missed anything, let me know!

@xynydev yes, this checks for all .just files in the repo

This seems to be failing because config/files/usr/share/ublue-os/just/60-custom.just contains !include /usr/share/ublue-os/just/100-bling.just, which does not exist, which triggers an error in just. I think we should probably just create an empty file with that name? @xynydev does that seem like a valid solution for you?

Took a bit of trial and error, but this now passes the syntax check (tested by triggering the workflow in my fork).

Why'd that fail? I think it's a worthwile effort to document the file's existence. Local --fmt --check 's don't cause failure for me...

@xynydev try running just --fmt before commit, just seems to be very picky


mouse_follows_focus=off applied to a rule doesn't seem to work

I am using the following configuration:
yabai -m config mouse_follows_focus          on

yabai -m rule --add title="JetBrains Toolbox" manage=off mouse_follows_focus=off
yabai -m rule --add app="System Preferences" manage=off
yabai -m rule --add app="choose" manage=off mouse_follows_focus=off
yabai -m rule --add app="CleanShot X" manage=off mouse_follows_focus=off

But the per-rule overrides of mouse_follows_focus do not seem to apply correctly. The mouse still jumps regardless.
Currently built from<PHONE_NUMBER>6232f4344329e250f38db2f0a1cc48.

Fixed on master.

Thank you, this looks to be working correctly now.


Tidy up - remove unused code

This commit has a conflict

what is the conflict?
On 22 April 2018 at 15:55, Chris Muktar<EMAIL_ADDRESS>wrote:

This commit has a conflict
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/chrism2671/PyTrendFollow/pull/24#issuecomment-383387294,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AdJDwCA5_Zi-T9oUnhlHzae0C08cQSGwks5trJn7gaJpZM4TeuqK
.

No problem, I managed to fix it! :)

Cheers!
On 23 April 2018 at 15:14, Chris Muktar<EMAIL_ADDRESS>wrote:

No problem, I managed to fix it! :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/chrism2671/PyTrendFollow/pull/24#issuecomment-383590282,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AdJDwO-KOE1CZOTUM1Zeg37-TBMEJ6OCks5treG8gaJpZM4TeuqK
.

Do you know resource where I can see all possible good trend following
strategies? to experiment pytrendfollow with new stragegies?
On 23 April 2018 at 15:14, Ram Kumar Koppu<EMAIL_ADDRESS>wrote:

Cheers!
On 23 April 2018 at 15:14, Chris Muktar<EMAIL_ADDRESS>wrote:

No problem, I managed to fix it! :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/chrism2671/PyTrendFollow/pull/24#issuecomment-383590282,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AdJDwO-KOE1CZOTUM1Zeg37-TBMEJ6OCks5treG8gaJpZM4TeuqK
.

IB native python API is available at http://interactivebrokers.github.io
On 23 April 2018 at 15:16, Ram Kumar Koppu<EMAIL_ADDRESS>wrote:

Do you know resource where I can see all possible good trend following
strategies? to experiment pytrendfollow with new stragegies?
On 23 April 2018 at 15:14, Ram Kumar Koppu<EMAIL_ADDRESS>wrote:

Cheers!
On 23 April 2018 at 15:14, Chris Muktar<EMAIL_ADDRESS>wrote:

No problem, I managed to fix it! :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/chrism2671/PyTrendFollow/pull/24#issuecomment-383590282,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AdJDwO-KOE1CZOTUM1Zeg37-TBMEJ6OCks5treG8gaJpZM4TeuqK
.


rustfmt makes it impossible to explain attributes with comments in the same line

Input
Sometimes an attribute needs a comment explaining why it exists:
#[cfg(not(miri))] // Miri does not deduplicate consts (https://github.com/rust-lang/miri/issues/131)

Output
Unfortunately rustfmt insists on putting the comment on a separate line (and it moves it after the attribute, which is even worse):
#[cfg(not(miri))]
// Miri does not deduplicate consts (https://github.com/rust-lang/miri/issues/131)

Expected output
Just like I can have comments to the right of code, explaining what the code does, I expect to have comments to the right of attributes, explaining what the attributes do:
#[cfg(not(miri))] // Miri does not deduplicate consts (https://github.com/rust-lang/miri/issues/131)

Meta

rustfmt version: whatever ./x.py fmt does in rustc

rustfmt version: whatever ./x.py fmt does in rustc

This is currently nightly-2020-11-19 (you can tell by looking at src/stage0.txt).

This looks very similar to https://github.com/rust-lang/rustfmt/issues/3255 -- in both cases rustfmt changes comment-after-code to move the comment onto its own line, thus changing the semantic meaning of the comment. IMO rustfmt should never do this.

I'm unable to reproduce this on rustfmt 1.4.38-nightly (2d9bc460 2022-04-07). Also It's not totally clear to me which PR resolved this. @calebcartwright any recollection of a PR that adjusted how missing comment spans were joined? without digging to deeply into it I'd assume that's where the fix was. I'll open a PR with tests cases for this.

I don't recall anything offhand, though it is getting a bit late in the day. Could you make sure you're testing locally with the same configuration settings that are used in the rust-lang/rust repo?

Closed as this does appear to be sorted, but please let us know if you see a recurrence @RalfJung


trying something else for publish

Coverage remained the same at 91.689% when pulling c019e25acce9232e03d3201b09586d245e349ee5 on sstoychev/fix-deploy into 71412e419961912e34a4fd2f134aa7ca1afe7998 on master.


Update kotlin-dsl-conventions plugin in gradle/gradle build

No more deprecation warnings from the ktlint-gradle plugin https://ge.gradle.org/s/6z2rea7scszes/deprecations
See https://github.com/gradle/gradle/issues/16030

@bot-gradle test RFM

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test RFM

OK, I've already triggered ReadyForMerge build for you.

Still seeing this on 7.0.x


PowerToys should restart after an update

Description of the new feature / enhancement
The program does not automatically restart after it is updated. It should.
Scenario when this would be used?
I extensively use FancyZones. I should not have to 'relaunch' PowerToys for FancyZones to work after the update has installed.
Supporting information
No response

This should be a very simple fix. Part of the update runtine should relaunch. Why is this taking so long? Every user on the planet using this application cant rely on it working -- because automatic updates closes Powertoys.

The update process needs work:

I get a notification that there is an update
I click the notification
I get to the powertoys main screen
I have to click the in-app notification that there is an update
I get to the update page
I have to click the update button
The updater does its thing
I have to remember to restart powertoys

The process should be simplified as demonstrated by #31806, #30151, #27651.

The notification's default action should bring the user directly to the update page, skipping 3-4
The notification should contain a button to install right away on top of the existing button to open the app, skipping 3-6
The in-app notification should have a button to install right away on top of the existing button that brings you to the update page, skipping 5-6
The app should restart after update.

These steps would bring down cognitive load on update (which are quite frequent) to

Get a notification
Click install


Evaluations get tuck on the last 4 questions

Sometimes, the evaluation (by GPT API) may get stuck on the last 4 questions. Kill the program and restart it will solve this.
But it's really inconvenient. Is there any method to avoid this?

I am having the same issue also! The evaluation gets stuck on the last 4 questions!!

Noticed this issue, will try to locate the problem that caused it.

@XuGW-Kevin @jeffhernandez1995
Hey guys. We have updated the implementation of track_progress_rich. You can have another try to check if the problem has been solved.


Eliminate the Psidekick dependency

Currently, to use this tool, it is necessary to first install the Psidekick docker extension. The reason this is necessary is that the psidekick extension is responsible for creating the docker network to which this dev container connects. If the network doesn't exist, then the container creation fails.
Ideally, both this tool and psidekick should connect to the network if it exists, and create it if it doesn't. But I don't think docker compose can do that... need to check.

If the psidekick dependency is eliminated, then this can be used by devs who want to deploy to an external psinode.

Ideally, both this tool and psidekick should connect to the network if it exists, and create it if it doesn't.
Unfortunately, I don't think this is possible.

I updated the template so it now asks if you want to use Psidekick.
If you specify "No," then it will create it's own docker network for the container.
If you specify "Yes," then it will look for the external network created by the Psidekick docker extension.


Improve github resolver

For example:

Is it the right character set that we are testing for?
How should we handle support for private keys?

This issue was moved to zeit/now-cli#771


Multiple errors in documentation and on charmhub.io

Multiple issues with the documentation for the VM charm in charmhub.io

The documentation URL for the VM charm points to the k8 repo. Is this the right place to file bugs also for the VM charm? Should I really file errors about the VM charm in here?

The documentation on how to deploy is for k8 charms. So, I get confused what this charm is about and how to use it.

The documentation states it can relate to charmcraft-prometheus, but it cant. "ERROR: No relations found" (See separate issue: )

Hi @erik78se -- the charms that the Observability team are working on right now are all targeting Kubernetes. The team plans to ship the stack essentially as an "appliance" on MicroK8s. The charms prefixed charmcraft- should be considered deprecated, we're in the process of cleaning those up.
The documentation about the new stack has a homepage here: https://juju.is/docs/lma2
There is a way for you do deploy the Charmed Observability Stack (COS) Lite into MicroK8s, then hook up your VM based applications using Cross-Model Relations, though. I think @mmanciop or @simskij should be able to point you in the right direction for that -- but this issue seems to relate to the "wrong" charms.
Sorry for any confusion here!

Edit: Found it! Check out the COS Proxy charm for a simple way to grab alerts/logs from your machine based models.

This is the way 👍🏽

But, why is this charm then in charmhub at all. It also deploys.
However, the documentation is totally bogus.
When I'm following build instructions, is also creates a k8 charm ... which happily deploys (but obviously errors).

Yeah, it should definitely be cleaned up. It's unfortunate that the charm listing points at this repo (it really shouldn't). Sorry for the confusion.


Issue/672 verbosecli

#672 Added comments in CLI to make it more verbose

@peterjan @ChrisSchinnerl @n8maninger I have made the requested changes. Kindly review and let me know if any other change is required

@ChrisSchinnerl I vote we close this out - we can always reopen if necessary

Some (possibly) unwanted user-feedback: the experience for new users is still quite poor. I though i may need to register for an API key or such just to run the software when reading then print.


How should an upload be resumed?

The spec talks about Resumable Push but it is not clear how this should be performed. Docker API v2 spec defines that when sending a chunk in a session, if the range does not match, then the response should be of the following form
416 Requested Range Not Satisfiable
Location: /v2/<name>/blobs/uploads/<uuid>
Range: 0-<last valid range>
Content-Length: 0
Docker-Upload-UUID: <uuid>

the key here being that there is Range: 0-<last valid range> that would tell the client about the last position written.

Under the Push definition, there's a PATCH description that includes the range. I don't think that's valid to resume a partial PUT, you'd need to do it from the first request.

The Resumable Push section reads (emphasis are mine)
Company X's build servers lose connectivity to a distribution endpoint before completing an artifact layer transfer. After connectivity returns, the build server attempts to re-upload the artifact. The registry notifies the build server that the upload has already been partially attempted. The build server responds by only sending the remaining data to complete the artifact file.
Following the same naming conventions, if the build server wants to know what is the last byte that was uploaded in order to resume the upload from this point. How it is suppose to do so? Returning Range: 0-<last valid range> is a way to inform this specific information.


Drawing new features on the globe

I think that being able to draw shapes (polygons, polylines etc.) is an essential feature for any online mapping library. Has this feature come up already? If I have time I could see how this could work, by taking inspiration from the openlayers implementation for example. That won't be soon but I wanted to share the idea already.

I'll start...https://github.com/openglobus/openglobus/pull/714


Side project: automatic UML export for ABAP codebase

will be done by abaplint.app, example https://abaplint.app/stats/abapGit/abapGit/uml?name=ZCL_ABAPGIT_GUI_PAGE_ADDOFFLIN
closing

will be done by abaplint.app, example https://abaplint.app/stats/abapGit/abapGit/uml?name=ZCL_ABAPGIT_GUI_PAGE_ADDOFFLIN
closing


Fail to call jax.device_count() after import jax in google cloud TPU-vm

Description
Python 3.11.4 (main, Jun  7 2023, 12:45:49) [GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.

import jax
jax.device_count()
WARNING: Logging before InitGoogle() is written to STDERR
I0000 00:00:1690231188.597418  174603 singleton_tpu_states_manager.cc:45] TpuStatesManager::GetOrCreate(): no tpu system exists. Creating a new tpu system.
F0000 00:00:1690231188.634652  174603 b295d63588a.cc:1205] File: InitGoogle() has not finished yet.
TPU
Additional system info
Python 3.11.4, Ubuntu 20.04.6 LTS (GNU/Linux 5.13.0-1027-gcp x86_64)
NVIDIA GPU info
No response

TPU v2-8
software version: tpu-vm-base

You might try rebooting the VM and/or clearing out any lock files in /tmp/*tpu* as a workaround.

sudo rm -rf /tmp/libtpu_lockfile /tmp/tpu_logs


Allow use of alert_subject in PagerDuty

Instead of hard coding the description for PD to the rule name, could we consider using alert_subject?
https://github.com/Yelp/elastalert/blob/57a3d352b8d03980a28ed522e6774e34b5148eba/elastalert/alerts.py#L896

We've had a similar issue come up with our deployment of ElastAlert -> PagerDuty; so I've filed a PR to allow for the use of alert_subject; whilst defaulting back to the current behaviour of using the rule name in lieu of the former being set.


relative broken links not detected

Relative Links in the github pages index.html are broken but not detected:
https://github.com/lenisha/linkchecker-test/runs/2122896789?check_suite_focus=true
+ lychee '--exclude=^(javascript|chrome):.*' --verbose --accept=200,403,429 --base-url https://lenisha.github.io/linkchecker-test/   https://lenisha.github.io/linkchecker-test/ --output /tmp/lychee/out.md
+ exit_code=0
+ '[' 0 -ne 0 ']'
+ cat /tmp/lychee/out.md
+ echo
+ echo ::set-output name=exit_code::0
📝 Summary
---------------------
🔍 Total...........17
✅ Successful......17
⏳ Timeouts.........0
🔀 Redirected.......0
👻 Excluded.........0
🚫 Errors...........0

while  index.thml has broken link https://github.com/lenisha/linkchecker-test/blob/main/index.html#L53
About

that points to https://lenisha.github.io/linkchecker-test/abouterror.html
Could it be also checked locally? Similar to discussion #15

@mre  is there any option to detect problems with relative links right now?
I tried to go against the live website with base-url
lychee '--exclude=^(javascript|chrome):.*' --verbose --base-url https://lenisha.github.io/linkchecker-test/   https://lenisha.github.io/linkchecker-test/

and tried against files files in PR
lychee  --exclude="^(javascript|chrome):.*"   --accept=200,403,429 "**/*.md" "**/*.html"

non have found the simple error
About

@mre is there any option to detect problems with relative links right now?

There should be, once https://github.com/lycheeverse/lychee/pull/99 is merged. Right now, link-parsing debugging is a bit cumbersome (e.g. you have to modify the source).

No clue why it doesn't find the relative links, though. @pawroman do you know why?

weird thing is when I explicitly point to index.html page it finds it
lychee --verbose '--exclude=^(javascript|chrome):.*' --accept=200,403,429 --base-url https://lenisha.github.io/linkchecker-test/ https://lenisha.github.io/linkchecker-test/index.html --output /tmp/lychee/out.md
+ exit_code=2
+ '[' 2 -ne 0 ']'
++ dirname lychee/out.md
+ mkdir -p lychee
+ echo 'Errors were reported while checking the availability of links.'
+ echo
+ echo '```'
+ echo
+ cat /tmp/lychee/out.md
+ echo
📝 Summary
+ echo '```'
+ echo
+ echo '[Full Github Actions output](https://github.com/lenisha/linkchecker-test/actions/runs/662263907?check_suite_focus=true)'
+ cat /tmp/lychee/out.md
+ echo
+ echo ::set-output name=exit_code::2
---------------------
🔍 Total...........28
✅ Successful......27
⏳ Timeouts.........0
🔀 Redirected.......0
👻 Excluded.........0
🚫 Errors...........1

Errors in https://lenisha.github.io/linkchecker-test/index.html
✗ https://lenisha.github.io/linkchecker-test/abouterror.html [404 Not Found]

After thinking about this some more I think I know what's up:
The html  file extension triggers the HTML mode in lychee. URLs without any file extensions get treated as plaintext, in which case relative URLs don't exist (currently at least).
We can probably safely assume that a URL returns HTML by default, so we have to change the condition here to return FileType::HTML by default if there is no extension:
https://github.com/lycheeverse/lychee/blob/ae2d02b8a0bb5e186478c5cf6a2d1ecad0c5ac64/src/collector.rs#L141

@lenisha, this is fixed in master now. Will publish a new version of the lychee-action (1.0.7) shortly.


Enrich event with Android context on the Dart layer

Description
Relates to https://github.com/getsentry/team-mobile/issues/11
Closes https://github.com/getsentry/sentry-dart/issues/1205

PR should use the v8 branch as the base branch.
PR can follow https://github.com/getsentry/sentry-react-native/pull/3170 as an example, @krystofwoldrich and @markushi can help here with reviews since they worked on the implementation for RN and Android.


Fix an issue with datetime column in Rule Engine

Description
With the fix, Rule Engine now works with both time and dateTime types. Previously it used to only work for time column.
Testing Done

added a unit test for one of the rules to have dateTime column instead of time column
locally changed the inputs of all the rules in the unit tests to have dateTime column instead of time column and they all passed. Didn't want to duplicate all the unit tests - one for time column and one for dateTime column - so I didn't include them in the PR. One unit test with dateTime column should suffice.

Codecov Report

Merging #6731 (7a80670) into master (d77a8d8) will decrease coverage by 7.76%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master    #6731      +/-   ##
============================================
- Coverage     73.81%   66.04%   -7.77%
  Complexity       12       12
============================================
  Files          1402     1402
  Lines         68042    68047       +5
  Branches       9828     9831       +3
============================================
- Hits          50227    44945    -5282
- Misses        14559    19924    +5365
+ Partials       3256     3178      -78

Flag
Coverage Δ
Complexity Δ

integration
?
?

unittests
66.04% <100.00%> (+0.02%)
0.00 <0.00> (ø)

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

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


Use of "async_setup_platforms"

Version of the custom_component

latest
Configuration

n/a

Describe the bug
After updating HA to version 2023.2 started to get the message:
Logger: homeassistant.helpers.frame
Source: helpers/frame.py:77
First occurred: 23:08:22 (1 occurrences)
Last logged: 23:08:22
Detected integration that called async_setup_platforms instead of awaiting async_forward_entry_setups; this will fail in version 2023.3. Please report issue to the custom integration author for midea_dehumidifier_lan using this method at custom_components/midea_dehumidifier_lan/init.py, line 68: hass.config_entries.async_setup_platforms(config_entry, PLATFORMS)
Debug log

n/a

I opened a PR to fix the issue, however, the owner of the repo hasn’t done any changes to it since August.
If by the time ha 2023.3 is out the pr will not be merged you can add my fork to HACS with the fix in place.
I have it on my instance and it has been stable.
To switch first remove the files but keep the configuration and then install from the other repo.

Thank you

Thank you!
I will switch to your fork as it appears you are on the ball!
Krs
Mark

Hi,
Could you be a bit more specific about the steps involved here - it might be obvious to you, but it's not to me:-
To switch first remove the files but keep the configuration and then install from the other repo.
OK, so remove what files from where ?
Where is the configuration held - so that I can 'keep it' ?
Do I then need to add this github as a custom repository to HACS ?
Sorry for the all the questions....

Yes, you should add the forked repo as a custom repository on hacs.
Then go in the details of the installed midea integration and press the three dots on the top right, there remove and it will ask if you want to keep the configuration. Then you can install the other version which will pick up the same configuration and after a restart you'd be fully switched

Much appreciated - thanks!


deepdive-model for reusing weights and expediting other model tasks

Shorthand commands for repeating a group of processes related to inference.

deepdive model ground
deepdive model learn
deepdive model infer

Commands for keeping and reusing weights.

deepdive model weights keep
deepdive model weights reuse
deepdive model weights list
deepdive model weights drop
deepdive model weights init

(These work with factor graphs as well if you replace weights with factorgraph but more bits should be kept to make it fully useful/meaningful, e.g., speeding up grounding, etc.  Currently it just stashes/restores the dumped factorgraph binaries but that's quite useless unless we keep around the database tables for grounding as well.)
Here's a hypothetical workflow:
deepdive do init/app

# learn weights from a small corpus and keep it for future reuse
deepdive create table articles
deepdive load articles /data/small/corpus.tsv.bz2
deepdive mark new articles
deepdive model learn  # taking care of all necessary extraction and grounding
deepdive model weights keep foo

# load larger corpus
deepdive create table articles
deepdive load articles /data/LARGE/corpus.tsv.bz2
deepdive mark new articles

# reuse the weights (skipping learning) and do inference
deepdive model weights reuse foo  # taking care of all extraction and grounding for larger data
deepdive model infer

I'll soon add a test that looks like above for a few of our examples (either in this PR or another).
Closes #463

This works really great! Ready to merge.

@raphaelhoffmann Thanks for testing and reviewing it!  I'll press the button myself.


Mixtral convert error: t() expects a tensor with <= 2 dimensions, but self is 3D

System Info

CPU architecture (x86_64)
GPU name (NVIDIA A100)
TensorRT-LLM(version: 0.8.0.dev20240130000.8.0.dev2024013000)

Who can help?
No response
Information

[X] The official example scripts
[ ] My own modified scripts

Tasks

[ ] An officially supported task in the examples folder (such as GLUE/SQuAD, ...)
[ ] My own task or dataset (give details below)

Reproduction
call convert script:
python /app/tensorrt_llm/examples/llama/convert_checkpoint.py
--model_dir /xxxx/NousResearch/Nous-Hermes-2-Mixtral-8x7B-DPO/
--output_dir /xxxxx/checkpoint
--dtype float16
--use_weight_only
--weight_only_precision int8
--tp_size 8
Expected behavior
convert successful
actual behavior
You are using a model of type mixtral to instantiate a model of type llama. This is not supported for all configurations of models and can yield errors.
Loading checkpoint shards: 100%|████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 19/19 [29:54<00:00, 94.44s/it]
Traceback (most recent call last):
File "/app/tensorrt_llm/examples/llama/convert_checkpoint.py", line 1971, in
main()
File "/app/tensorrt_llm/examples/llama/convert_checkpoint.py", line 1956, in main
covert_and_save(rank, convert_args)
File "/app/tensorrt_llm/examples/llama/convert_checkpoint.py", line 1893, in covert_and_save
weights = convert_hf_llama(
File "/app/tensorrt_llm/examples/llama/convert_checkpoint.py", line 1393, in convert_hf_llama
get_tllm_linear_weight(moe_experts_w2_weights,
File "/app/tensorrt_llm/examples/llama/convert_checkpoint.py", line 676, in get_tllm_linear_weight
v = weight.t().contiguous()
RuntimeError: t() expects a tensor with <= 2 dimensions, but self is 3D
additional notes
NO

My solution in llama/convert_checkpoint.py
 if use_weight_only:
        if len(weight.shape)==3:
            v = weight.permute(0, 2, 1).contiguous()
        else:
            v = weight.t().contiguous()

but convert  tllm_prex + 'mlp.router.'
RuntimeError: [TensorRT-LLM][ERROR] Assertion failed: Number of bytes for rows and cols must be a multiple of 32. However, num_rows_bytes = 2048 and num_col_bytes = 4. (/TensorRT-LLM/cpp/tensorrt_llm/kernels/cutlass_kernels/cutlass_preprocessors.cpp:255)

router linear [4096,8]->will be error

I have exactly the same problem when I try to use the convert script for a Mixtral 8 x 7B for conversion to int8 :
python3 convert_checkpoint.py --model_dir ./Mixtral8x7B/
--output_dir ./tllm_checkpoint_1gpu_fp16_wq/
--dtype float16
--use_weight_only
--weight_only_precision int8
But this error appeared :
Traceback (most recent call last):
File "/home/TensorRT-LLM/examples/llama/convert_checkpoint.py", line 1547, in
main()
File "/home/TensorRT-LLM/examples/llama/convert_checkpoint.py", line 1523, in main
covert_and_save(rank, convert_args)
File "/homeTensorRT-LLM//examples/llama/convert_checkpoint.py", line 1489, in covert_and_save
weights = convert_hf_llama(
File "/home/TensorRT-LLM/examples/llama/convert_checkpoint.py", line 983, in convert_hf_llama
get_tllm_linear_weight(moe_experts_w2_weights,
File "/home/TensorRT-LLM/examples/llama/convert_checkpoint.py", line 660, in get_tllm_linear_weight
v = weight.t().contiguous()
RuntimeError: t() expects a tensor with <= 2 dimensions, but self is 3D
Do you have any update on the resolution to this issue please?
Many thanks!

I managed to quantize Mixtral 8x7B to 4 bpw.
I first tried running this command:
model="models--mistralai--Mixtral-8x7B-Instruct-v0.1"
model_dir="/models/$model"
model_chkpt_dir="/models/$model--trt-chkpt"

python3 TensorRT-LLM/examples/llama/convert_checkpoint.py \
    --model_dir "$model_dir" \
    --output_dir "$model_chkpt_dir" \
    --dtype float16 \
    --use_weight_only \
    --weight_only_precision int4 \
    --int8_kv_cache

and got the same error as @xesdiny:
RuntimeError: [TensorRT-LLM][ERROR] Assertion failed: Number of bytes for rows and cols must be a multiple of 32. However, num_rows_bytes = 2048 and num_col_bytes = 4. (/home/jenkins/agent/workspace/LLM/main/L0_MergeRequest/tensorrt_llm/cpp/tensorrt_llm/kernels/cutlass_kernels/cutlass_preprocessors.cpp:258)

There has been some changes in the library code since the comment of @xesdiny, the second change proposed by @xesdiny (disabling the router module) seems to be already implemented in models/llama/convert.py when a mixture of experts model is detected.
I tried applying the first changed proposed by @xesdiny (passing a False value to get_tllm_linear_weight), for clarity this is the diff of the change in the diff unified (-u) format:
--- convert.py	2024-03-25 19:38:29.042100000 +0100
+++ /usr/local/lib/python3.10/dist-packages/tensorrt_llm/models/llama/convert.py	2024-03-25 19:46:03.221558000 +0100
@@ -791,7 +789,7 @@
             weights.update(
                 get_tllm_linear_weight(
                     moe_experts_gate_weights.to(torch.float32),
-                    tllm_prex + 'mlp.router.', None, use_weight_only,
+                    tllm_prex + 'mlp.router.', None, False,
                     plugin_weight_only_quant_type, dtype, use_gemm_woq_plugin))
         else:
             mlp_gate_weight = get_weight(model_params, prefix + 'mlp.up_proj',

With that change I tried running again the conversion command and it succeeded. Then I built the engine without any error:
model_engine_dir="/models/$model--trt-engine"
trtllm-build --checkpoint_dir "$model_chkpt_dir" \
    --gemm_plugin float16 \
    --output_dir "$model_engine_dir"

Finally I tried the summarize example to test the engine, which also ran without error:
python3 TensorRT-LLM/examples/summarize.py --test_trt_llm \
    --hf_model_dir "$model_dir" \
    --data_type fp16 \
    --engine_dir "$model_engine_dir"

I managed to quantize Mixtral 8x7B to 4 bpw.
I first tried running this command:
model="models--mistralai--Mixtral-8x7B-Instruct-v0.1"
model_dir="/models/$model"
model_chkpt_dir="/models/$model--trt-chkpt"

python3 TensorRT-LLM/examples/llama/convert_checkpoint.py \
    --model_dir "$model_dir" \
    --output_dir "$model_chkpt_dir" \
    --dtype float16 \
    --use_weight_only \
    --weight_only_precision int4 \
    --int8_kv_cache

and got the same error as @xesdiny:
RuntimeError: [TensorRT-LLM][ERROR] Assertion failed: Number of bytes for rows and cols must be a multiple of 32. However, num_rows_bytes = 2048 and num_col_bytes = 4. (/home/jenkins/agent/workspace/LLM/main/L0_MergeRequest/tensorrt_llm/cpp/tensorrt_llm/kernels/cutlass_kernels/cutlass_preprocessors.cpp:258)

There has been some changes in the library code since the comment of @xesdiny, the second change proposed by @xesdiny (disabling the router module) seems to be already implemented in models/llama/convert.py when a mixture of experts model is detected.
I tried applying the first changed proposed by @xesdiny (passing a False value to get_tllm_linear_weight), for clarity this is the diff of the change in the diff unified (-u) format:
--- convert.py	2024-03-25 19:38:29.042100000 +0100
+++ /usr/local/lib/python3.10/dist-packages/tensorrt_llm/models/llama/convert.py	2024-03-25 19:46:03.221558000 +0100
@@ -791,7 +789,7 @@
             weights.update(
                 get_tllm_linear_weight(
                     moe_experts_gate_weights.to(torch.float32),
-                    tllm_prex + 'mlp.router.', None, use_weight_only,
+                    tllm_prex + 'mlp.router.', None, False,
                     plugin_weight_only_quant_type, dtype, use_gemm_woq_plugin))
         else:
             mlp_gate_weight = get_weight(model_params, prefix + 'mlp.up_proj',

With that change I tried running again the conversion command and it succeeded. Then I built the engine without any error:
model_engine_dir="/models/$model--trt-engine"
trtllm-build --checkpoint_dir "$model_chkpt_dir" \
    --gemm_plugin float16 \
    --output_dir "$model_engine_dir"

Finally I tried the summarize example to test the engine, which also ran without error:
python3 TensorRT-LLM/examples/summarize.py --test_trt_llm \
    --hf_model_dir "$model_dir" \
    --data_type fp16 \
    --engine_dir "$model_engine_dir"

which setup did you run for quantization? i thought about quantizing like this "--weight_only_precision int4" as well, but haven't been able to find how to use multi-gpu setup when quantizing with tensorrt, and single gpu would need to have over 100gb vram i think

Yes, this requires at least 100GB of VRAM. I executed the code on a system equipped with three Nvidia A100 GPUs, each with 40GB of VRAM, so 120GB in total. When running the convert_checkpoint.py script the model was automatically distributed across the three GPUs.


Dashboard Token Listing: GHOx

Discord Handle of Submitter: 0xkamal7#0
Token Symbol: GHOx
Network: Ethereum Mainnet
Token Address: 0x22064a21FEE226D8fFB8818E7627d5FF6D0Fc33a
Network Explorer Link: https://sepolia.etherscan.io/token/0x22064a21fee226d8ffb8818e7627d5ff6d0fc33a
Is a Super Token? true
Address of Underlying Token:  0xc4bF5CbDaBE595361438F8c6a187bDc330539c60
SVG Logo Link: https://assets.coingecko.com/coins/images/30663/large/ghoaave.jpeg?1696529533
Coingecko or Hardcoded Price?: Coingecko
Coingecko ID: https://www.coingecko.com/en/coins/gho
Harcoded Price (if Coingecko ID is unavailable):
Token HEX Color: #2596be
Info on Listing: GHO is the native token of AAVE and by listing this on the dashboard. It would nice to stream GHOx Super Tokens.
Please close only after token has been added to resolver!

@philipandersson @philipandersson @d10r  @seliqui please review .

it's now listed, see https://console.superfluid.finance/eth-sepolia/supertokens/0x22064a21FEE226D8fFB8818E7627d5FF6D0Fc33a?tab=streams


sql/driver: ensure driver not nil before lock

chore: ensure driver not nil before lock

@googlebot I signed it!


Refactor to support PyTorch 2.0 and Lightning 2.0

使用 PyTorch Lightning 2.0 作为框架，并对 base_task 和 acoustic_task 进行了适配。

自动多节点训练（CPU、单GPU、多GPU等）。
支持使用其他精度设置进行训练，例如'bf16'。
支持了梯度累积。
使用 K 个最近验证的检查点，并支持原有的永久检查点和间隔。
将采样器及其分布式版本重新编码为 PyTorch 的Sampler类的子类。

重新实现了按相似帧数分组的样本Shuffle。

使用PL的rank_zero工具来甄别主进程

升级到 PyTorch 2.0，对 torch.compile 的支持还有待测试。

为了与大多数深度学习服务提供商兼容，也支持 PyTorch 1.12/1.13，但是 Lightning 需要是 2.0.0 版本
（在 scripts/train.py 中，环境变量 TORCH_CUDNN_V8_API_ENABLED 的设置是防止在使用 16 位精度时过慢，如果它导致任何问题，请尝试将其注释掉。）

使用 HDF5 作为新的二进制数据集格式，以避免潜在的文件句柄争用。
更新了数据准备 Notebook，反映 PL 相关参数。

新参数说明：

PyTorch Lightning 相关：

pl_trainer_accelerator、pl_trainer_devices、pl_trainer_num_nodes、pl_trainer_strategy 和 pl_trainer_precision 请参阅 PyTorch Lightning 2.0 文档以了解它们在 Trainer 中的用法。
对于 pl_trainer_devices，它可以是：

pl_trainer_devices: 'auto': 自动选择
pl_trainer_devices: 2: 使用两个加速器，自动选择
pl_trainer_devices: [2, 3]: 使用 2 号和 3 号加速器

ddp_backend, 可选项有 'gloo', 'nccl', or 'nccl_no_p2p'。

数据加载器相关：

config/base.yaml 中的sampler_frame_count_grid：现在正确支持具有相似大小的样本的随机混洗。 首先，样本长度被归一为sampler_frame_count_grid的倍数（默认为 200），然后在每个 bin 内，样本在每个 epoch 进行洗牌。
config/base.yaml 中的 dataloader_prefetch_factor：PyTorch 的 DataLoader 设置（请参阅 PyTorch 文档）。

多 GPU 上的有效批量大小和梯度累积：

max_tokens 和 max_sentences 始终控制单个设备的Batch大小。 然后将有效批量大小全部相加。
accumulate_grad_batches 允许您在梯度下降之前反向传播多个批次，从而增加有效批次大小。
例如（假设 max_sentences 占主导地位），你有 4 个 GPU，max_sentences=8，accumulate_grad_batches=2。 那么有效批量大小 4*8*2=64。

Use official PyTorch Lightning 2.0 as the framework, and adapted base_task and acoustic_task to it.

Automatic multiple-node training (CPU, single-GPU, multi-GPU, etc).
Now support training with other precision settings, e.g., 'bf16'.
Gradient Accumulation works correctly.
Checkpointing with K most recent validations, and supports the original permanent checkpoint and interval.
Re-coded batch sampler and its distributed version as subclasses of PyTorch's Sampler class.

Sample shuffling with grouping by similar frame count is reimplemented.

Adapted multiple main process discrimination codes to use PL's rank_zero utility.

Upgrade to PyTorch 2.0, support for torch.compile is yet to be tested.

For compatibility with most deep learning service providers, PyTorch 1.12/1.13 is also supported, however, Lightning needs to be version 2.0.0
(In scripts/train.py, environment variable TORCH_CUDNN_V8_API_ENABLED is set to prevent excessive slowdown when using 16-bit precision. If it causes any problem, try to comment it out.)

Use HDF5 as the new binarized dataset format to avoid potential file handle sharing and race to perform file seeking.
Updated data preparation notebook to reflect several PL related parameters.

New parameter explanation:

PyTorch Lightning related:

Exposed pl_trainer_accelerator, pl_trainer_devices, pl_trainer_num_nodes, pl_trainer_strategy, and pl_trainer_precision, see the PyTorch Lightning 2.0 doc for their usage in Trainer section.
For pl_trainer_devices, it can be:

pl_trainer_devices: 'auto': Auto select
pl_trainer_devices: 2: Use two accelerators, auto select
pl_trainer_devices: [2, 3]: Use accelerator number 2 and 3

ddp_backend, choose from 'gloo', 'nccl', or 'nccl_no_p2p'.

DataLoader related:

sampler_frame_count_grid in config/base.yaml: Now random shuffling of samples with similar sizes is correctly supported. First, the sample length is rounded to multiples of sampler_frame_count_grid (default 200), and then within each bin, samples are shuffled every epoch.
dataloader_prefetch_factor in config/base.yaml: Setting for PyTorch's DataLoader (refer to PyTorch doc).

Effective batch size on Multi-GPU and gradient accumulation:

max_tokens and max_sentences always control batching for a single device. Effective batch size is then all of them summed.
accumulate_grad_batches allows you to backpropagate multiple batches before a gradient descent, effectively increasing the batch size.
Combining them, for example (suppose max_sentences is dominant), you have 4 GPUs, max_sentences=8, accumulate_grad_batches=2. Then you have effective batch size 4*8*2=64.

I formerly wrote a Python program to search for config keys that are never used in other codes: search_config2.txt (renamed to .txt because GitHub does not support uploading .py files). You can use it to clean unused config keys after refactoring.

This PR is ready to be merged after the final fixes and some simple tests on the incoming branch.
By the way, license of the refactor-v2 branch was formerly changed to Apache 2.0, which will be the new license of our forked DiffSinger once refactor-v2 is merged into the main branch. With your agreement, your contributions will also be licensed under Apache 2.0 in this repository.

My consent, thanks.

Due to some unresolved performance issues during tests, this branch will be merged into a temporary branch. It should be merged into the main branch after these issues are addressed.

Performance is tightly linked to the grid resolution when performing shuffling and sorting by similar lengths on samples. When fully sorted, the performance does not drop compared to the original codebase.

Performance issues addressed so I changed the base branch back to refactor-v2.


revert(ingest/airflow-plugin): "emit browsePathV2 (#10738)"

This reverts commit 190f09ad7ab3c0fd82963c303fda2774b391d5e4.
Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@coderabbitai full review

Closing in favor of https://github.com/datahub-project/datahub/pull/10803


Reinteract like notebook arrangement of script and figures

From<EMAIL_ADDRESS>on 2010-02-05T02:10:18Z
I like the way Reinteract arranges the figures amongst the scripts. It enables the user to
clearly see how the code progresses - more like a notebook.
I was wondering whether this feature could be implemented in Spyder somehow.  Perhaps
there could be an option to create multiple text editor windows of the same script but each
displaying different portions of that script between the plot.show() commands and
positioned between the figure windows. These script and figure windows could then be
grouped inside another scrollable window. When the script is modified, just hit refresh and
it repositions all the windows.
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=150

From pierre.raybaut on 2011-05-18T00:33:05Z
Status: ContributorNeeded

From pierre.raybaut on 2011-03-28T23:21:55Z
That is an interesting idea but it would require a lot of work. I'm letting this issue opened in case a contributor want to do something about it some day.
As for the technical part, I think that the best would be to reimplement Reinteract in PyQt and add a new plugin handling this Mathematical-like cell mode.
Summary: Reinteract like notebook arrangement of script and figures
Labels: -Type-Defect Type-Enhancement

From<EMAIL_ADDRESS>on 2011-08-10T01:19:54Z
The IPython v0.11 pylab inline mode should replicate something very similar to the feature i suggested in this issue. I suggested having figures embedded between the scripts in the editor rather than the console (as IPython v0.11) - which will be just as good. So, you could probably close this issue.
I look forward to the full integration of IPython v0.11. It'll be a superb enhancement to Spyder. Thanks for your hard work.

From pierre.raybaut on 2011-08-10T03:50:53Z
I completely agree.
Thanks for your support!
Status: Done


docs::Limitations: Repeated typo 'SimpleAggregare'?

The 'Limitations and Configuration' page of the documentation has repeated uses of SimpleAggregare, which seems to be a typo for SimpleAggregate

Thanks! Fixed


Add docs about vscode extension

Link to: https://github.com/bridgetownrb/vscode-serbea

Weird, this is already in the docs site. Closing!


Fix NameError for _machine reference when loading 'sndfile' library on darwin

There has been a typo with machine variable resulting NameError: name 'machine' is not defined which is fixed here.

My bad. Thank you for catching the issue!


chore(master): release 1.1.135

:robot: I have created a release beep boop
1.1.135 (2023-07-31)
Miscellaneous

deps: update dependency @wayofdev/lint-staged-config to v2.1.2 (cca1080)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/keywind/releases/tag/v1.1.135 :sunflower:


RC Spot-Check Test: Mean: Share and Balance 1.1.0-rc.3

RC Spot-Check Test
Mentions: @jbphet, @marlitas, @amanda-phet
Simulation links

github repository for issues
phet top-level directory
sim: all_phet.html
phet-io wrapper index
link to phet-io zip file

Test Matrices
General Test:

[x] Tester = NS , Platform = mac + safari , Time = 1.75
[x] Tester = KW, Platform = Win 11 Chrome, Time =1.75

PhET-iO Test:

[ ] Tester = , Platform = , Time =
[ ] Tester = , Platform = , Time =

Additional Features Test:

[ ] Tester = , Platform = , Time =
[ ] Tester = , Platform = , Time =

Features included

[x] PhET-iO
[x] Dynamic Locale
[x] Alternative Input
[x] UI Sound
[x] Sonification
 [ ] Description
[ ] Voicing

Focus and Special Instructions
This is a spot check after two full RCs for Mean Share and Balance. Most issues were modular and their scope does not need to be expanded. In general issues revolved around the group sort interaction in the Distribute and Balance Point screens.
Issues to Verify
All issues can be closed once verified.

[x] https://github.com/phetsims/mean-share-and-balance/issues/337
[x] https://github.com/phetsims/mean-share-and-balance/issues/329
[x] https://github.com/phetsims/mean-share-and-balance/issues/335
[x] https://github.com/phetsims/mean-share-and-balance/issues/343
[x] https://github.com/phetsims/mean-share-and-balance/issues/344
[x] https://github.com/phetsims/mean-share-and-balance/issues/345
[x] https://github.com/phetsims/scenery-phet/issues/841
[x] https://github.com/phetsims/mean-share-and-balance/issues/349
[x] https://github.com/phetsims/mean-share-and-balance/issues/346
[x] https://github.com/phetsims/mean-share-and-balance/issues/265

For QA...

General features

What to Test

Click every single button.
Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.

If there is sound, make sure it works.
Make sure you can't lose anything.
Play with the sim normally.
Try to break the sim.
Test some query parameters. (See QA Book for a
list of query parameters.)
When making an issue, check to see if it was in a previously published version.
Try to include version numbers for browsers.
If there is a console available, check for errors and include them in the Problem Description.
As an RC begins and ends, check the sim repo. If there is a maintenance issue, check it and notify developers if there
is a problem.
As the RC ends, notify the developer of any new QA credits that need to be added.

PhET-iO features

What to Test

Make sure that public files do not have password protection. Use a private browser for this.
Make sure that private files do have password protection. Use a private browser for this.
Make sure standalone sim is working properly.
Make sure the wrapper index is working properly.
Make sure each wrapper is working properly.
Launch the simulation in Studio with ?stringTest=xss and make sure the sim doesn't navigate to youtube
For newer PhET-iO wrapper indices, save the "basic example of a functional wrapper" as a .html file and open it. Make
sure the simulation loads without crashing or throwing errors.
Load the login wrapper just to make sure it works. Do so by adding this link from the sim deployed root:/wrappers/login/?wrapper=record&validationRule=validateDigits&&numberOfDigits=5&promptText=ENTER_A_5_DIGIT_NUMBER

Further instructions in QA Book
Conduct a recording test to Metacog, further instructions in the QA Book. Do this for iPadOS + Safari and one other
random platform.
Conduct a memory test on the stand alone sim wrapper (rc.1).
Test one platform combination with ?phetioDebug=true on the Studio and State wrapper.
If Pan/Zoom is supported, make sure that it works when set with PhET-iO State.
Test that the sim works offline:

Click the link to the phet-io zip file (at top of issue) to download the zip file.
Unzip it to a spot locally.
Open index.html by double clicking it on your desktop or in a Finder-view.
It should look like the standalone version of the sim in PhET-iO brand.

Accessibility features

What to Test

Specific instructions can be found above.

Make sure the accessibility (a11y) feature that is being tested doesn't negatively affect the sim in any way. Here is
a list of features that may be supported in this test:

Alternative Input
Interactive Description
Sound and Sonification
Pan and Zoom
Mobile Description
Voicing

Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.
Test all keyboard navigation inputs (if applicable).
Test all forms of input with a screen reader (if applicable).

If this sim is not in this list or up to date there, make an
issue in website to ask if PhET research page links need updating. Please
assign to @terracoda and @emily-phet.

Screen Readers
This sim may support screen readers. If you are unfamiliar with screen readers, please ask Katie to introduce you to
screen readers. If you simply need a refresher on screen readers, please consult the
QA Book, which should have all of the information
you need as well as a link to a screen reader tutorial made by Jesse. Otherwise, look over the a11y view before opening
the simulation. Once you've done that, open the simulation and make sure alerts and descriptions work as intended.

Platforms and Screen Readers to Be Tested

Windows 10 + Latest Chrome + Latest JAWS
Windows 10 + Latest Firefox + Latest NVDA
macOS + Safari + VoiceOver
iOS + Safari + VoiceOver (only if specified in testing issue)

Critical Screen Reader Information
We are tracking known screen reader bugs in
here. If you find a screen reader bug,
please check it against this list.

Keyboard Navigation
This sim supports keyboard navigation. Please make sure it works as intended on all platforms by itself and with a
screen reader.
Magnification
This sim supports magnification with pinch and drag gestures on touch screens, keyboard shortcuts, and mouse/wheel
controls. Please test magnfication and make sure it is working as intended and well with the use cases of the
simulation. Due to the way screen readers handle user input, magnification is NOT expected to work while using a screen
reader so there is no need to test this case.

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

Calling QA here

Closing. The next RC is up: https://github.com/phetsims/qa/issues/1137


Correct link to golint README

It works poorly in GitHub mobile version.
On Sat, Oct 28, 2017, 00:32 Will Norris<EMAIL_ADDRESS>wrote:

@willnorris commented on this pull request.
In CONTRIBUTING.md
https://github.com/google/go-github/pull/765#discussion_r147521225:

@@ -55,7 +55,7 @@ again.

-[golint https://github.com/golang/lint-[golint readme]: https://github.com/golang/lint/blob/master/README
+[golint readme]: https://github.com/golang/lint/blob/master/README.md
hmm, I'm not sure why we linked directly to the file in the first place.
How about https://github.com/golang/lint/#readme ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/google/go-github/pull/765#pullrequestreview-72635693,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AARuk3U4NwEjBm9dw2SfCrOThp3sw_UHks5swkwIgaJpZM4QJXxR
.


Use actual H1 page title for browser page title and OpenGraph title

Currently, we use the menu title from metadata, but that is usually short to fit the menu and misses the contact you have in the menu. So on its own it's not enough information for the Google or when sharing the page.

Ideally, we should parse it from the page markdown, and if this is not possible, we will move custom <h1 /> to a new metadata property.
More in: https://apifier.slack.com/archives/CQ96RHG2U/p1699475295877139

@B4nan could you handle it with @barjin ? You know the most about this.

Sure, I'll take a look.
Just FYI the title is not "menu title", it's a regular title, that's why it's used in the mets tags. There is a separate siderbar_label frontmatter option for that, I guess it's just about using it in the frontmatter. The fix will be most probably per page, I can try to quickly review things based on the frontmatter, but it's not like we use "menu titles for meta descriptions".

Yeah, if we could also remove the rogue H1 headings in the article bodies, that would be great :)
From what I remember, they (are|were) getting picked up by the Algolia Crawler, which messed up the search results a bit (the articles are segmented to searchable records by headings, so this double-heading situation led to one result with no body).

So you think we should prefer the title in frontmatter instead of keeping the one in the content? My plan was to rather remove the title from frontmatter and replace it with sidebar_label if it differs from the H1 in the content.

Imo keeping the title in the frontmatter is a bit nicer, but it apparently shouldn't matter:

Go with your instinct then, from the docs it seems that Docusaurus can even infer the title from the Markdown and vice versa. From what I saw, I've probably fixed the search issue :)

Go with your instinct then, from the docs it seems that Docusaurus can even infer the title from the Markdown and vice versa.

Yeah, that's what I thought as well, if it's not explicit, it should be inferred from the content, and that will be probably easier for docs contributors.

Hey, so basically we'll be able to override the menu text using the siderbar_label option, and the title will be kept as is (used for page title, H1 if there is none, and OG images) ? IMO that would be a good solution

Yes, the fix will be changing the title option to sidebar_label where the value differs, we don't need the title if there is a top-level H1 in the content, it will be respected automatically. Will write a short script for this and clean it up everywhere.

Okay, but if title is present, it will be used for page title and OG description? I think it would be good to still have it as a way to override the top-level H1

Yes, it's the same thing, if you don't provide both, the other is always inferred from the one with value. If the value differs, the title is (most probably) used for the metadata.
So you'd like to keep both the title and H1 in the content even if the content is exactly the same?

I think it's more transparent to keep the title in content, rather than the H1s, so I'd clean the H1 if they are the same. It's clearer that's what's used for page title, OG, etc.

Just to be clear, we want this
---
---

# Foo

this is page about foo

and not this
---
title: 'Foo'
---

this is page about foo

Honestly I'd prefer:
---
title: 'Foo'
---

this is page about foo

But that's just technicallity, so your call.
What's important is that title will keep working, and if both H1 and title is used, then title goes to page title and OG, and H1 is shown in the document


Automatic PR from RestAPI-PR1713

Generated from RestAPI PR: https://github.com/Azure/azure-rest-api-specs/pull/1713

Codecov Report

Merging #1471 into master will decrease coverage by 0.01%.
The diff coverage is 46.15%.

@@            Coverage Diff             @@
##           master    #1471      +/-   ##
==========================================
- Coverage    55.1%   55.09%   -0.02%
==========================================
  Files        3417     3420       +3
  Lines       83477    83565      +88
==========================================
+ Hits        45996    46036      +40
- Misses      37481    37529      +48

Impacted Files
Coverage Δ

...sql/operations/virtual_network_rules_operations.py
15.84% <0%> (ø)
:arrow_up:

azure-mgmt-sql/azure/mgmt/sql/version.py
100% <100%> (ø)
:arrow_up:

...ure/mgmt/sql/models/sql_management_client_enums.py
100% <100%> (ø)
:arrow_up:

...ure-mgmt-sql/azure/mgmt/sql/operations/__init__.py
100% <100%> (ø)
:arrow_up:

...e-mgmt-sql/azure/mgmt/sql/sql_management_client.py
100% <100%> (ø)
:arrow_up:

azure-mgmt-sql/azure/mgmt/sql/models/__init__.py
100% <100%> (ø)
:arrow_up:

...l/azure/mgmt/sql/operations/database_operations.py
28.26% <28.26%> (ø)

...mt-sql/azure/mgmt/sql/models/database_operation.py
29.41% <29.41%> (ø)

...-sql/azure/mgmt/sql/models/virtual_network_rule.py
55.55% <33.33%> (-15.88%)
:arrow_down:

.../azure/mgmt/sql/models/database_operation_paged.py
80% <80%> (ø)

... and 3 more

Continue to review full report at Codecov.

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


SRE-33 haskell overhaul

This is the overhaul of Haskell for cardano-base along the lines of cardano-node PR #507.

bors r+

bors ping

bors r+

bors r-

bors r+


Use empty list as categories

[ ] Tests added / passed
[x] Passes black dask / flake8 dask
[x] Closes #6364

Thanks, I think this is better.
Only suggestion would be to maybe preserve the dtype of the categories. Something like
In [50]: pd.Categorical(['a', 'b'], s.dtype.categories[:0])
Out[50]:
[NaN, NaN]
Categories (0, object): []

In [51]: pd.Categorical(['a', 'b'], pd.DatetimeIndex([]))
Out[51]:
[NaT, NaT]
Categories (0, datetime64[ns]): []

So use an empty index of the right dtype rather than an empty list.


wireframes for Topic Version flow

modify, cancel, error, completed

Conceptually, we have 5 different use cases for this:

Topic creation has failed: too big
a) on topic homepage, user is invited to create a new version
b) user is taken to 'Edit Topic' to edit seed stories, dates, media
b) save/rebuild

Topic creation is running/building
a) on topic homepage, user clicks cancel
b) on topic homepage, user is invited to create a new version

Topic creation is completed
a) user wants to change seed stories

user click into Version Manager (same flow as old Modify Topic)
user can edit seed stories
save --- respider behind the scenes?
b) user wants to create sub topics
user clicks Filter button at top right and selects Add/Remove SubTopics
user can add/remove subtopics
respider
c) user wants to respider

Case 1) Hurricanes, Desserts
Case 2) Robots
Cases 3, 4, 5) Topic: AI In US

met with Emily and Anissa. I think the friction point is versions w/r to subtopics. Otherwise, the use cases seem pretty clear

is digitizing new and clear paper mockups ok? or do we want more formal than that.


refactor to get_user in zerver/mgmt/commands/

Replaced all instances of get_user_profile_by_email with get_user in zerver/management/commands/ directory.
Passes ./tools/test-all (i.e., passes backend, linter, mypy, etc.)
[>>>DEPRECATED PER ADDITION OF get_user_for_mgmt FUNCTION>>>] Only change I'm not confident in is removing a section in turn_off_digests.py -- the prior logic checked for realm and then pulled all user profiles for that realm, now assumes realm is given for all commands so that get_user functions. If this isn't true, may need to go back through all of these changes and add logic for cases where options['string_id'] == None (i.e., realm is not given as part of the options parameter).

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

@hackerkid can you take a look at this please?

We will merge this once the get_user_mgmt gets merged. You may have to rename get_user to get_user_mgmt in this PR.

@hackerkid this should be good to go now

@LechX can you test running all of these manually at least to make sure they work?

Please hold on this, I am getting an error during testing in an area of code that I haven't been working on...

@LechX you might want to rebase..

@timabbott You can close this PR in favor of #5735

Thanks to @hackerkid, a version of this branch was completed in the last few days; we ended up creating a better API in zerver/lib/management.py to make this sort of change a lot cleaner.
Thanks for all your work on this @LechX!!


Missing Custom Validation

Hey,
there's a section in README about custom validation with objects like ResultValidator, CountValidator and ThresholdValidator. But it seems that the Dropshots API is missing those elements in my project (ver 0.3.0), could you please add a sample or small snippet on how to use that feature?

That's not released yet, so you'll need to use a snapshot version to access
it.
On Wed, Aug 31, 2022 at 1:14 AM Maciek Tomczyński @.***>
wrote:

Hey,
there's a section in README about custom validation with objects like
ResultValidator, CountValidator and ThresholdValidator. But it seems that
the Dropshots API is missing those elements in my project (ver 0.3.0),
could you please add a sample or small snippet on how to use that feature?
—
Reply to this email directly, view it on GitHub
https://github.com/dropbox/dropshots/issues/28, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJ4S3RIDD5JXJIDRHRI2XDV33Z4JANCNFSM6AAAAAAQBBTLII
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

This is available in 0.4.0 on Maven Central.


add a 'gravity' slider.

Effect of gravity is just to force particles to interact more at the bottom where they 'precipitate'.

forgot to mention that all particles have the same (unit) mass for now.

it might be interesting to have the particle attracted to the center instead of downward, if the world is unbounded they just vanish out of screen

the html version has a 'wall repel' feature to prevent this. Is it present in the cpp version?

the html version has a 'wall repel' feature to prevent this. Is it present in the cpp version?

no, i suppose i'll add it


chore(deps): update module github.com/goreleaser/goreleaser/v2 to v2.4.4

This PR contains the following updates:

Package
Update
Change

github.com/goreleaser/goreleaser/v2
patch
v2.4.3 -> v2.4.4

Release Notes

goreleaser/goreleaser (github.com/goreleaser/goreleaser/v2)
v2.4.4
Compare Source
Changelog
Bug fixes

606c0e7: fix(cmd): handle --skip=,names... (@caarlos0)

Other work

cc4427f: chore: auto-update generated files (@actions-user)

Full Changelog: https://github.com/goreleaser/goreleaser/compare/v2.4.3...v2.4.4
Helping out
This release is only possible thanks to all the support of some awesome people!
Want to be one of them?
You can sponsor, get a Pro License or contribute with code.
Where to go next?

Find examples and commented usage of all options in our website.
Reach out on Discord and Twitter!

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.2%) to 63.056%

Files with Coverage Reduction
New Missed Lines
%

pkg/config/env.go
4
79.65%

Totals

Change from base Build<PHONE_NUMBER>3:
-0.2%

Covered Lines:
1234

Relevant Lines:
1957

💛  - Coveralls


Record deletion: Data model

Note for the citation_text:
AFAIK, the generation of citation texts in a specific flavor (e.g. APA, IEEE, BibTeX) goes through the service layer, so adding that to the system field itself would mix layers.
I think it should probably be added as a default value in the upcoming service function that's used to delete records/set tombstone information.


Bitcode is not full enabled

Hi,
I get an error as below:

ld: bitcode bundle could not be generated because '/Users/Vic/projects/projecta/WindowsAzureMessaging.framework/WindowsAzureMessaging(SBNotificationHub.o)' was built without full bitcode. All object files and libraries for bitcode must be generated from Xcode Archive or Install build file '/Users/Vic/projects/projecta/WindowsAzureMessaging.framework/WindowsAzureMessaging' for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

But otool shows it contains bitcode:

Vic:projecta Vic$ (otool -arch arm64 -l WindowsAzureMessaging.framework/WindowsAzureMessaging | grep LLVM) || echo "no bitcode"
segname __LLVM
segname __LLVM
segname __LLVM
segname __LLVM
segname __LLVM
segname __LLVM
segname __LLVM
segname __LLVM
segname __LLVM
segname __LLVM
segname __LLVM
segname __LLVM
segname __LLVM
segname __LLVM
segname __LLVM
segname __LLVM
segname __LLVM
segname __LLVM
segname __LLVM
segname __LLVM
segname __LLVM
segname __LLVM

Any ideas?
Thanks,
Vic

Guys I am getting the same error. Actually we have created on static library which will work for our company and added to Project for Enable Bit Code    bitcode bundle could not be generated because.    When I disable Bit Code I can archive successfully but I should give Bit code enable.
How do I solve this can any one help me.

I had this issue with the Pod for v3.1.0, archiving with XCode 11.3.1.
I installed the package via Swift Package Manager, and that seemed to work.


Improve tab saving / reloading

I tend to have many tabs open with news that I want to read later, as I usually do in Safari or Firefox when investigating a topic.
I also usually close the application when I am done reading or have to go somewhere else.
The first part of the issue happens when opening Vienna again: Every open tab is being reloaded immediately, instead of when I select it. That needs an awfully long time and also internet volume.
The second issue affects me less often, but is worse: Sometimes, when the list was very long, after re-opening Vienna, all URLs to be loaded are gone. Every tab is still re-opened, but displays "No title" ("Ohne Titel" in German), does not load anything and has no url in the url field.
I suspect that the latter issue is a combination of the tabs still loading but me already closing Vienna again. This suspicion is supported by my observation, that Vienna starts loading the most recently opened tab first, and sometimes a small number of most recently opened tabs still has a title and a url when re-opening Vienna another time later, but the older ones do not. It does not happen every time when closing Vienna while the content of the tabs is still loading, though.
Sorry that I cannot pin the issue more closely. I love Vienna for being a still active RSS project, which for me is the favorite way to read my bundled news! Keep up the fantastic work! I might at some point help contributing a little...

CPU and memory management in relation to WebView is not that easy to do, especially not in a multi-tab interface. Loading a tab upon selection would be an efficient solution, but it will of course add delays. An alternative solution would be to fetch the web content in the background and then pass the data to the web view once it’s shown (then it ‘only’ needs to be drawn).
Sadly, we cannot use Apple’s solution of having multiple XPC services.

I think users are ok with delays when tabs are loaded on selection after they closed the application. Of course tab content would stay once loaded, for example if a user opened the tab from the feed or it was loaded due to some heuristic (e.g. the tab right to the selected one could be preloaded, and if it does not exist the left one, because it will be opened once the user closes the current tab). From my experience with Safari and Firefox, tab loading is done in such a way (minus the mentioned heuristic, so even more primitive).

This is solved in the current release candidate


error connecting to provider "aws": provider not found: provider "aws"

Update
ok I've fixed this issue setting the toleration value on secrets-store-csi-driver-provider-aws
tolerations:
  - operator: Exists

resource "helm_release" "secrets-provider-aws" {
  repository       = "https://aws.github.io/secrets-store-csi-driver-provider-aws"
  name             = "aws-secrets-manager"
  chart            = "secrets-store-csi-driver-provider-aws"
  namespace        = "kube-system"
  create_namespace = true
  version          = "0.3.4"

  values = [<<-EOF
tolerations:
  - operator: Exists
EOF
  ]
}

CLOSING THIS IN FAVOR OF #267
Describe the bug
I'm not being able to attach a secret on a pod, i get this error.
MY_POD_LOG
MountVolume.SetUp failed for volume "secrets-store-inline" : rpc error: code = Unknown desc = failed to mount secrets store objects for pod ns-ai-service/ns-ai-service-858bf5f554-2jp8c, err: error connecting to provider "aws": provider not found: provider "aws"

ecrets-store-csi-driver LOG
E0831 21:56:53.626573       1 nodeserver.go:242] "failed to mount secrets store object content" err="error connecting to provider \"aws\": provider not found: provider \"aws\"" pod="ns-ai-service/ns-ai-service-858bf5f554-2jp8c"
I0831 21:56:53.626595       1 nodeserver.go:88] "unmounting target path as node publish volume failed" targetPath="/var/lib/kubelet/pods/73dffdf5-a15c-4ece-b330-b627e636094e/volumes/kubernetes.io~csi/secrets-store-inline/mount" pod="ns-ai-service/ns-ai-service-858bf5f554-2jp8c"

aws-secrets-manager-secrets-store-csi-driver-provider-aws LOG
I0831 20:31:56.271368       1 main.go:32] Starting secrets-store-csi-driver-provider-aws version 1.0.r2-50-g5b4aca1-2<IP_ADDRESS>.19
I0831 20:31:56.271988       1 main.go:77] Listening for connections on address: /etc/kubernetes/secrets-store-csi-providers/aws.sock

I have 2 nodes, both nodes show the same 2 lines log

Already tried some of the solutions discussed on this issue #91 but found the  following:

the tolerations on secrets-store-csi-driver are already set on [{"operator": "Exists"}]

the grpcSupportedProviders setting is not available or needed anymore on the secrets-store-csi-driver chart

To Reproduce
Steps to reproduce the behavior:
Deploy the CSI drivers helm charts (I use terraform)
resource "helm_release" "secrets-store-csi-driver" {
  repository       = "https://kubernetes-sigs.github.io/secrets-store-csi-driver/charts"
  name             = "secrets-store-csi-driver"
  chart            = "secrets-store-csi-driver"
  namespace        = "kube-system"
  create_namespace = true
  version          = "1.3.4"

  set {
    name  = "syncSecret.enabled"
    value = "true"
  }
}

resource "helm_release" "secrets-provider-aws" {
  repository       = "https://aws.github.io/secrets-store-csi-driver-provider-aws"
  name             = "aws-secrets-manager"
  chart            = "secrets-store-csi-driver-provider-aws"
  namespace        = "kube-system"
  create_namespace = true
  version          = "0.3.4"

}

SecretProviderClass
apiVersion: secrets-store.csi.x-k8s.io/v1alpha1
kind: SecretProviderClass
metadata:
  name: ns-ai-service-secrets
  namespace: ns-ai-service
spec:
  provider: aws
  secretObjects:
  - data:
    - key: NS_AIS_REDIS_SECURE
      objectName: NS_AIS_REDIS_SECURE
    secretName: "ns-ai-secrets"
    type: Opaque
  parameters:
    objects: |
        - objectName: "/ns-ai-service/staging/NS_AIS_REDIS_SECURE"
          objectAlias: "NS_AIS_REDIS_SECURE"
          objectType: "ssmparameter"

serviceAccount
apiVersion: v1
kind: ServiceAccount
metadata:
  annotations:
    eks.amazonaws.com/role-arn: arn:aws:iam::XXXXXX:role/k8s-ns-ai-role
  name: ns-ai-service
  namespace: ns-ai-service

Deployment
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: ns-ai-service
  labels:
    app.kubernetes.io/name: ns-ai-service
  namespace: ns-ai-service
spec:
  selector:
    matchLabels:
      app.kubernetes.io/name: ns-ai-service
  replicas: 1
  strategy:
    rollingUpdate:
      maxSurge: 25%
      maxUnavailable: 25%
    type: RollingUpdate
  template:
    metadata:
      labels:
        app.kubernetes.io/name: ns-ai-service
    spec:
      serviceAccountName: ns-ai-service
      volumes:
      - name: secrets-store-inline
        csi:
          driver: secrets-store.csi.k8s.io
          readOnly: true
          volumeAttributes:
            secretProviderClass: "ns-ai-service-secrets"
      containers:
        - name: ns-ai-service
          image: debian
          command: ['sh', '-c', "sleep<PHONE_NUMBER>000000000"]
          imagePullPolicy: Always
          volumeMounts:
          - name: secrets-store-inline
            mountPath: "/mnt/secrets-store"
            readOnly: true

If yes, the issue is likely with the k8s Secrets Store CSI driver, not the AWS provider. Open an issue in that repo.
Expected behavior
I would like to make it work.
Environment:
Kubernetes version
1.25
AMI release version
1.25.12-20230825
AMI type
AL2_x86_64
Platform version
eks.6
Terraform Helm
source  = "hashicorp/helm"
version = ">= 2.9.0"
Thank you guys for any hint you can give to me.

Hi @pcnoic, yes take too look to this issue https://github.com/aws/secrets-store-csi-driver-provider-aws/issues/267


Update OpenSSH_Install_FirstUse.md

Fix spelling: Window --> Windows

@SarveshMD : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@SarveshMD : Thanks for your contribution! The author(s) have been notified to review your proposed change.


ImportError: libscip.so.8.0: cannot open shared object file: No such file or directory

Describe the bug
Import of cvxpy fails
To Reproduce
import cvxpy as cp
Expected behavior
No error to be raised.
Details
    import cvxpy as cp
  File "/opt/conda/envs/py310/lib/python3.10/site-packages/cvxpy/__init__.py", line 57, in <module>
    from cvxpy.problems.problem import Problem as Problem
  File "/opt/conda/envs/py310/lib/python3.10/site-packages/cvxpy/problems/problem.py", line 38, in <module>
    from cvxpy.reductions import InverseData
  File "/opt/conda/envs/py310/lib/python3.10/site-packages/cvxpy/reductions/__init__.py", line 24, in <module>
    from cvxpy.reductions.dcp2cone.dcp2cone import Dcp2Cone
  File "/opt/conda/envs/py310/lib/python3.10/site-packages/cvxpy/reductions/dcp2cone/dcp2cone.py", line 24, in <module>
    from cvxpy.reductions.dcp2cone.canonicalizers import CANON_METHODS as cone_canon_methods
  File "/opt/conda/envs/py310/lib/python3.10/site-packages/cvxpy/reductions/dcp2cone/canonicalizers/__init__.py", line                                                  44, in <module>
    from cvxpy.reductions.dcp2cone.canonicalizers.suppfunc_canon import (
  File "/opt/conda/envs/py310/lib/python3.10/site-packages/cvxpy/reductions/dcp2cone/canonicalizers/suppfunc_canon.py",                                                  line 5, in <module>
    from cvxpy.reductions.solvers.conic_solvers.scs_conif import (
  File "/opt/conda/envs/py310/lib/python3.10/site-packages/cvxpy/reductions/solvers/conic_solvers/__init__.py", line 31                                                 , in <module>
    from .scip_conif import SCIP
  File "/opt/conda/envs/py310/lib/python3.10/site-packages/cvxpy/reductions/solvers/conic_solvers/scip_conif.py", line                                                  38, in <module>
    from pyscipopt.scip import Model as ScipModel
  File "/opt/conda/envs/py310/lib/python3.10/site-packages/pyscipopt/__init__.py", line 11, in <module>
    from pyscipopt.scip      import Model
ImportError: libscip.so.8.0: cannot open shared object file: No such file or directory

Version

python              : 3.10.13.final.0
OS                  : Linux
OS-release          : 5.15.0-79-generic
CVXPY Version: 1.41

Additional context
I created a new docker image with mamba / conda-forge and the new build fails, same build was running last week without any issues. Not sure which dependency drives this issue.

The issue is with the latest pyscipopt release (interface to SCIP, not part of cvxpy)

I don't see any recent releases in this project - do I miss something?

I can confirm, setting the SCIP version to 8.0.4 fixes the problem


GlobalSimilarity_cluster.py returning empty Kernel.npy

Hi,
The GlobalSimilarity.py works well and seems very useful thanks! However, I have larger systems and would like to use your parallelised version GlobalSimilarity_cluster.py
When running it using:
python ../GlobalSimilarity_cluster.py small_molecules.xyz --xlim 0,11 --ylim 513661,21 -np 16 -sek
It terminates without any errors, but the pickle that should contain the Kernel is just empty? I tried using the example small_molecules.xyz too. What am I doing wrong?

Hi sorry for the late reply.
You end up with an empty pickle because "--ylim 513661,21" is out of bound: the ylim option set the structures range that needs to be considered. So here small_molecules.xyz has 500 structures and 513661 is out of bound and larger than 21 so the range of structures is empty.
Also, GlobalSimilarity_cluster.py is not meant to be used directly. Instead you probably want to use GlobalSim_cluster.py (that will rely on GlobalSimilarity_cluster.py) that handles the mpi dispatching.
Could you try to run:
"""
mpiexec -n 4 python  ../GlobalSim_cluster.py small_molecules.xyz --first 0 --last 73 -nt 2 -cl 11 -ngk
"""
from the examples folder after pulling the latest state of the repo ?

Hi Felix,
Thanks for your reply.
I pulled the latest state of the repo and run the command as you said from the examples/ folder. It didn't run fine straight away because there's a missing "/" symbol on line 173 of your code of GlobalSim_cluster.py. Which causes a faulty path to file:
 python: can't open file '/home/glosim2-masterGlobalSimilarity_cluster.py': [Errno 2] No such file or directory
# GlobSim_cluster.py:
# added slash here:
    path2GlobSim = path_to_executable+'/GlobalSimilarity_cluster.py'

Regarding running a molecule other than the sample input, I was wondering if you can tell me how
you got to the frames index 0 and 73 to input some structures from small_molecules.xyz. When you told me to put  --first 0 --last 73 -nt 2 -cl 11 -ngk, index of first and last frame, how do I end up with 26 log messages/.pck, molecules to be analysed? Where do you read the numbers 0,73 from? I get that my log files are somehow labelled from 0 to 73. But the idividual labels labels don't seem to match the number of atoms per molecule comparing with the first 26 molecules in small_molecules.xyz.
I get a folder with all the log files per job and each molecules kernel as a pickle. Then outside the tmp folder I get the normalised Global Average Kernel and the Rematch kernel. Do I follow this correctly and the environment kernels is all the tmp/kernels added together?
Now the example is running fine.
Thank you.


[C++]: Fixed segfault due to null ifa_addr from getifaddrs

BsdInterfaceLookup::lookupIPv4 and BsdInterfaceLookup::lookupIPv6 can segfault on a machine with interfaces that have NULL ifa_addr (e.g. OpenVPN tun interface).
From the documentation of getifaddrs:

ifa_addr and other fields can actually be NULL if the interface has no address, and no link-level address is returned if the interface has an IP address assigned.

Thank you for the fix.