Added imageSize and playableDuration to include param

Summary
I realized that the Android implementation still had poor performance since it looped through individual images to populate image.width/height (some of the time) and image.playableDuration (for every video).
Excluding playableDuration in particular improves performance significantly when the user has videos.
This change:

Adds include params for image.width, image.height, and image.playableDuration
Refactors Android code to respect those and avoid looping if the params are excluded
Makes iOS code respect it too
Adds documentation

Test Plan
Added toggles to GetPhotosPerformanceExample.

iOS
Android

What's required for testing (prerequisites)?
Just the standard yarn start:ios and yarn start:android
What are the steps to reproduce (after prerequisites)?
Compatibility

OS
Implemented

iOS
✅

Android
✅

Checklist

[X] I have tested this on a device and a simulator
[X] I added the documentation in README.md
[X] I updated the typed files (TS and Flow)
[X] I added a sample use of the API in the example project (example/App.js)

@hsource the other PR is merged, happy to help merging this

Thanks! I rebased the change and retested it, and updated the GIFs in the original post! Take a look. It should be ready for review and submission @bartolkaruza

Thank you for contributing @hsource !

:tada: This PR is included in version 3.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


GU - Duplicate Submissions (Failures from 1/30)

GU reported duplicates and failures. Attached is the list of all messages that need to be resubmitted to GU with valid LOINCs
https://app.zenhub.com/files/304423150/5376aced-e217-4536-9d68-eadcd3a7ddf2/download

@jbiskie Similar to what Mo did with MD, we can share the GU accession IDs with Zedd in SR team for resubmissions. Not sure how far you may have gotten on this, but consider this as an option. You can share this list in slack thread with Zedd.

Thanks, that makes things a lot easier than I thought they would be. So do we only need to manually resubmit those that didn't come from SR?

AFAIK, the duplicates all came from SR, so this might be as easy as asking SR team to resubmit the messages on this list.

Updates list here; failures as of 2/2 are greater than previously reported. Refer to the sheet for GU
https://app.zenhub.com/files/304423150/e1318207-fe16-4169-a13c-6d25c35b3b64/download

Thanks, I'm reviewing this against the first list

Full list has 1212 unique message id's vs 444 in first list.  Counts are approx the same between created_at > '2022-01-28T10:55:23.094780' and created_at < '2022-01-31T01:30:00.000000'.  Remainder were messages after that time span.

Sent json with all messages to Zedd.

Done! expect to see it in RS around 10:45 CST

Thank you @zdeveloper!

Inductive is reviewing the resubmissions.

From Inductive:
"Guam received the 1212 reprocessed labs yesterday and are officially caught up! All processed into the NBS system successfully. "


Explain how to configure the Git repo to build Docker image on Window

The root cause is file line ending. Windows uses CRLF, Unix - LF.
My Git client automatically switches line endings while cloning or committing sources, but to locally build Docker image some sources need to have LF ending otherwise TB will not be able to start.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.test seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Download and execute

I do not know if this function is already running like this...
download the payload and execute it in memory without dropping it on the disk and without encrypting the payload?
Same as Lime Downloader.

No, it will write it to disk then run it

If it were executed directly in memory, it would be a major improvement.


Docker Compose Building Error: http: invalid Host header

Error Code: http: invalid Host header
OS: Ubuntu 22.04
All the other stuff:
elias@hostedbox:~/quack_domains$ sudo docker compose up --build -d
[+] Building 32.4s (1/1) FINISHED
=> ERROR [internal] booting buildkit                                                                                32.4s
=> => pulling image moby/buildkit:buildx-stable-1                                                                                12.2s
=> => creating container buildx_buildkit_default                                                                                20.2s

[internal] booting buildkit:
#0 32.36 time="2023-10-09T11:35:29Z" level=warning msg="using host network as the defaultime="2023-10-09T11:35:29Z" level=warning msg="using host network as the default"
#0 32.36 time="2023-10-09T11:35:30Z" level=warning msg="skipping containerd worker, as "/run/containerd/containerd.sock" does not exist"
#0 32.36 dtime="2023-10-09T11:35:30Z" level=info msg="found 1 workers, default="ntmfw4zfvtle4ilngf8tqaiaw""
#0 32.36 `time="2023-10-09T11:35:30Z" level=warning msg="currently, only the default worker can be used."
#0 32.36 \time="2023-10-09T11:35:30Z" level=info msg="running server on /run/buildkit/buildkitd.sock"
#0 32.36 time="2023-10-09T11:35:30Z" level=warning msg="skipping containerd worker, as "/run/containerd/containerd.sock" does not exist"
#0 32.36 time="2023-10-09T11:35:30Z" level=warning msg="currently, only the default worker can be used."
#0 32.36 time="2023-10-09T11:35:30Z" level=warning msg="currently, only the default worker can be used."
#0 32.36

http: invalid Host header

Thanks for the report! That's a weird one, I can't reproduce, and I'm running 22.04.3 LTS (Jammy Jellyfish). I think buildkit is used by Docker to build all images (by default) - have you ever built anything else from a  Dockerfile? How did you install Docker? You could try reinstalling it, these are the instructions I always use: Install Docker Engine on Ubuntu

The container fails to start after ERROR [internal] booting buildkit, right? You can run sudo docker compose up --build without the -d to see it fail, and/or run sudo docker ps after to see what's running.

Never used Dockerfile
Installed it via APT

eee

Oh funky, not sure how leaving out --build could fix it; the Docker image has to build either way - this just triggers a re-build if it was already built.

eee

I don't speak dolphin 🐬, but if you hit another issue feel free to reopen and let me know what went wrong :)


Grouped MultiRider Mount broke after Update 36

I believe that after Update 36, pulling the Multi-Rider Mounts no longer works. I can be grouped, have a companion out, etc., it no longer pulls from the Multi-Rider Mounts.
It would be awesome to have this fixed again.
Thanks in advance.

Are you willing to test a debug version for me? I don't really play much anymore and do not have any multi-rider mounts in which to test.

Yes, I'll test for you
On Thu, Jun 22, 2023, 6:05 PM Brad Hughes @.***> wrote:

Are you willing to test a debug version for me? I don't really play much
anymore and do not have any multi-rider mounts in which to test.
—
Reply to this email directly, view it on GitHub
https://github.com/Oricul/eso-RandomMount/issues/6#issuecomment-1603418837,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6AYU4W5EOXR5IN24WOWSHDXMTFUJANCNFSM6AAAAAAVCLFDEI
.
You are receiving this because you authored the thread.Message ID:
@.***>

In the dev branch is an update for RandomMount.lua. The only change is a debug message when the script checks to see if the selected mount is multi-rider. All you need to do is replace your local copy with this one, /reloadui, make sure settings are enabled and checked for multi-rider. I just need a screenshot of the output that will be tossed into your chat when you go to dismount.
RandomMount.lua

ESO has added "Random Mounts" and "Random Favorite Mounts" to the base game. This was added during Update 38. At first you addon, the text for settings was missing. The Random Mount function isn't working. How they handle this now is to turn off the in-game random mount and random favorites, you select either of those options (after you choose your favorites). To turn off the Random Mount function of in-game, you select the mount that you want to use. I believe that it's overriding the Random Mount function of your addon.

I hope my explanation is understandable.

The thing with the in-game version is it doesn't distinguish between being grouped up or not, which is disappointing. I've had to favorite my 2 Multi-Riders, so I only get those...which sucks since I have so many mounts.

My bad... Forgot to format the string. I've uploaded a new version.

I left a comment on ESO.UI. The files aren't in their own "folder" when installing through Minion. The LibRandomMount, Localization folders and the manifest and LUA files get installed in the addons folder. ESO doesn't recognize the addon as being installed. I have moved my files in to a folder named RandomMount.

Have you had a chance to take the new dev version and take that screenshot?

I'm not sure how to get to the dev area...

RandomMount.lua

bad argument #3 to 'string.format' (string expected, got nil)
stack traceback:
[C]: in function 'string.format'
user:/AddOns/RandomMount/RandomMount.lua:754: in function 'RM_Object:IsMultiRider'
user:/AddOns/RandomMount/RandomMount.lua:722: in function 'RM_Object:GetUseableMounts'
user:/AddOns/RandomMount/RandomMount.lua:769: in function 'RM_Object:SummonMount'
user:/AddOns/RandomMount/RandomMount.lua:546: in function 'func'
/EsoUI/Libraries/Globals/globalapi.lua:260: in function '(anonymous)'

Thanks. I've made a change, same link as before. A lot of data will be output to chat, please share it.

just started vRG, it will be after that before I can test

When I have the addon running, it pulls out the horse I have selected. The "Random Favorite Mount" and "Random Mount" can only be turned off by selecting a specific mount. Not sure if that helps or not

Thanks for the screenshot. I did get the information I needed. I've pushed an update to dev branch that should remove debug messages and fix multi-rider mounts. Mind testing? RandomMount.lua


Update CONTRIBUTING.md

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] The changes are appropriately documented (if applicable).
[x] The changes have sufficient test coverage (if applicable).
[x] The testsuite passes successfully on my local machine (if applicable).

Summarize your changes:
fixed typo in contributing.md

add
docs: update to pr title 👍

add
docs: update to pr title 👍

or actually
have a look here

Annotations
1 error
Validate PR Title
No release type found in pull request title "Update CONTRIBUTING.md". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/
Available types:

feat: A new feature
fix: A bug fix
docs: Documentation only changes
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
refactor: A code change that neither fixes a bug nor adds a feature
perf: A code change that improves performance
test: Adding missing tests or correcting existing tests
build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
chore: Other changes that don't modify src or test files
revert: Reverts a previous commit

done


Quote and reply deletes topic and moves cursor to topic

Using quote and reply always results in me:
Starting to type a reply, realising it has typed it in the topic field, then having to close the onscreen key board and scroll up to see what the correct topic was and should again be, then deleting the reply I've started typing from the topic field, then typing the original correct topic again, searching and selecting in the list, then scrolling to the actual message field, then trying to remember the reply I started typing when it was wrongly entered in the topic field. Very frustrating and time wasting. Repeats about 5x daily, 6 days per week.
Desired behaviour:
When using quote and reply: use the same topic as the quoted message by default, and start with the cursor in the message field below the quoted text.
Thanks!

Thanks you for the report! I expect that we'll fix this in the flutter version of the app (https://github.com/zulip/zulip-flutter).

Thanks for the report! I think this won't be too difficult to fix.
I think I know what's going on:
When you want to compose a new message from an interleaved stream narrow, the app isn't good at choosing a reasonable value for the topic input; in fact, it doesn't choose any value. Instead, it has a (kind of awkward) mechanism to nudge the user to specify a topic: when the user taps the message input and the topic input is empty, we auto-focus the topic input. I guess that mechanism accomplishes its purpose, but it sure is annoying when it seems like the app could choose a reasonable topic for you.
I think that's what's going on here: when you do a quote-and-reply and the topic input is empty, probably you want the topic of the selected message, and the app should use that. PR coming soon. 🙂


delete VehicleUserService, add methods to VehicleService, fix bugs, l…

Hi,
Hope i could be helpful, for the lack of time i wasn't able to help more.
I left you some comments.
Try spend some time on naming classes, methods and variables its important to name them descriptively.
After implementing some service classes don't forget to do some unit tests, just to be sure your logic works!
If you have any questions, feel free to ask 🍡

Hi, thanks for your engagement to this project. I carefully check out your commit and I agree with most of them but I dont understand one thing i application properties file you set
spring.jpa.hibernate.ddl-auto=update
why? I read something about this and I find information about that  is not good practise in use.


MacOS Kivy.app 2.0.0 - no module named 'kivy'

OS: MacOS 10.14.4 Mojave installed as QEMU Virtual Machine on Kubuntu box
Kivy: Kivy.app version 2.0.0 (latest) installed as per documentation
Issue: starting kivy env and trying to "import kivy", error is returned: no module named 'kivy'
This morning I asked for help on Discord chat. In the chat I describe the problem. This is the full log:
radiolondraOggi alle 10:57
Hi guys,
not having a Mac, I installed a MacOS Mojave 10.14.4 in my linux box using Qemu. And it works fine. After I got the Kivy.app dmg from github and installed in my OSX VM following the instruction on the website. Using the 'kivy' link I created I tried to 'import kivy' but I got the error: no module named 'kivy'. Could someone help me? Do I have to set some environment vars? This happened using Catalina OSX too (it's more than 1 week I'm trying to run a simple test kivy app in MacOS using all the possible ways to install kivy without any success). On Windows everything works fine. On OSX I'm not able to do anything. For sure I'm missing something or doing something wrong... but what? Thanks a lot in advance for your help.

The OSX I installed this time is "as it is", that is, I didn't add anything, just the Kivy.app. In my previous attempts (I tried with pip, brew, MacPorts, frameworks, what else...every time using a fresh & clean OSX installation) I installed python, all the kivy dependencies, this and that without any success. After a week of unsuccessful attempts,  I'm really frustrated now... :frowning: and I feel myself very stupid... bah.
SnuOggi alle 11:09
@radiolondra not sure about that problem, but there's another issue with kivy on an osx vm that i ran into... no gpu
not sure if qemu has somehow made it around that... but virtualbox and vmware have not
(kivy wont run without proper opengl 3d acceleration)
radiolondraOggi alle 11:13
@Snu I know the GPU issue in VMWare and VB, in my previous attempts I used them to create a VM and the issue was on SDL2 and OpenGL, but at least the app started without any "module not found 'kivy'" issue. Here the python version implemented inside Kivy.app is saying "Module Not found" as it cannot find kivy.
SnuOggi alle 11:14
yeah, sounds like it was probably installed on the wrong python install
radiolondraOggi alle 11:14
And in another attempt I did with Kivy.app on VMWare I had the same result: no module found: kivy.
Kivy.app already contains Python ver. 3.8.6. As per documentation, when you start some python app using "kivy main.py", it shoud use the virtual env present inside Kivy.app. But the simple "proof of concept" of start kivy env and import kivy fails with Module Not Found: kivy, as it cannot find kivy in the included env. For this I'm suspecting some settings is missed somewhere (like a PATH or something). See the image I sent: I printed the sys.path saw by kivy.... I don't know if it's right but it should.... so... I don't know. :frowning:
My question is: did someone used Kivy.app in REAL MacOS (on a MacPro or iMac) without any issue? Is the whole thing related to the usage of Virtual Machines? Or ther's something else I don't know?
m1sl6Oggi alle 11:33
@radiolondra I can confirm that It doesn't work in that way. (Also if it's documented)
If you need to use the "Kivy.app", at this time please follow the "Using the App Virtual environment" section https://kivy.org/doc/stable/installation/installation-osx.html#using-the-app-virtual-environment
radiolondraOggi alle 11:40
@m1sl6 Thanks for your suggestion, but believe me I learned that document by hearth :slight_smile: and it says explicity that you should use the kivy link to launch your python app, this way the kivy env will be automatically used. If instead you want to use the normal way (python directly) you have to manually activate the kivy.app env as described in the doc.
and anyway... I just downloaded and installed an old Kivy.app (ver.1.9.0) and it works fine... Sooooo... ther's something wrong in the latest Kivy.dmg (ver.2.0)? or this version has been compiled with a different version of OSX? But the documentation explicity says "OSX ver 10.14.4+" so from Mojave base on....
m1sl6Oggi alle 11:52
The Kivy.app gets compiled via the CI. Actually, the CI relies on MacOS 10.15.7
Can you please open an issue on Github with all the logs so We can track this down?
Also (just personal interest), there's a specific reason that kept you choosing  Kivy.app instead of the pip version?
radiolondraOggi alle 11:57
I used Kivy.app as the latest beach of thousands of attempts to install Kivy on MacOS VM. I fighted against SDL2 and OpenGL issues in VMWare and VirtualBox (no 3D acceleration in VM), I tried to change the Window provider, recompiled kivy from source, and tons of other attempts. Now I was trying the same ways but using QEMU (which has a way to passthrough video cards) and the simplest way to start was using Kivy.app__
----------------------------------------- END OF LOG
Result: Although the documentation says that the minimum OSX version for Kivy.app is 10.14.4 (Mojave), Kivy.app ver.2.0.0 doesn't work (ModuleNotFoundError: No module named 'kivy'). But Kivy.app version 1.9.0 works fine.
I don't know if I misunderstood the compatibility of the OS versions (maybe the documentation should be a bit more clear and precise) or if there is a real problem in the 2.0 version of Kivy.app.

I can't tell from your comments whether you followed the instructions to activate the kivy virtualenv: https://kivy.org/doc/stable/installation/installation-osx.html#using-the-app-virtual-environment
pushd /Applications/Kivy.app/Contents/Resources/venv/bin
source activate
source kivy_activate
popd

I can't tell from your comments whether you followed the instructions to activate the kivy virtualenv: https://kivy.org/doc/stable/installation/installation-osx.html#using-the-app-virtual-environment
pushd /Applications/Kivy.app/Contents/Resources/venv/bin
source activate
source kivy_activate
popd

@matham
The point 4. of the documentation about Kivy.app install on MacOS answers your doubts:

As opposed to activating the virtualenv below, running with kivy will use the virtualenv but also properly configure the script environment required to run a Kivy app (i.e. setting kivy’s home path etc.).

To enter the python shell, I'm using "kivy" not "python", as I said in the chat. And "kivy main.py" not "python main.py"

@matham
The point 4. of the documentation about Kivy.app install on MacOS answers your doubts:

As opposed to activating the virtualenv below, running with kivy will use the virtualenv but also properly configure the script environment required to run a Kivy app (i.e. setting kivy’s home path etc.).

To enter the python shell, I'm using "kivy" not "python", as I said in the chat. And "kivy main.py" not "python main.py"

Kivy.app test results
Tests performed on Mojave and Catalina MacOSes
Tests are executed using the 'kivy' symlink (which enters the python shell) and simply write: import kivy in the shell.
1 - filename: Kivy-1.9.0-osx.dmg
it installs  Kivy version 1.9.0: WORKS
2 - filename: Kivy-1.10.1_osx10.13.5_packaged_python3.6.5_r1.dmg
it installs Kivy version 1.10.1: WORKS
3 - filename: Kivy-1.11.0-python3.6.5.dmg
it installs Kivy version 1.11.0: WORKS
4 - filename: Kivy.dmg
it installs Kivy version 2.0.0 (latest): DOESN'T WORK -> no module named 'kivy'
Also the makesymlinks executable, where present (2 and 3) fails miserably, doesn't create the link to kivy in /usr/local/bin and you have to create it manually (Permission denied).  Something like sudo ln -s /Applications/Kivy3.app/Contents/Resources/script /usr/local/bin/kivy3
In ALL MacOS Virtual Machines I used (VMWare, VirtualBox and QEMU) kivy fails running even the simplest Hello World app, whatever was the way you used to install kivy and all its dependencies (pip, brew, MacPorts, framework, conda, ... what else...).
Running 'kivy main.py' (or python main.py) the result is always the same:

[CRITICAL] [Window] Unable to find any valuable Window provider at all!
sdl2 - RuntimeError: Failed creating OpenGL pixel format

The very strange thing is that if you run some SDL2 python examples, they works fine without any issue in whatever Virtual Machine... Bah?

Kivy.app test results
Tests performed on Mojave and Catalina MacOSes
Tests are executed using the 'kivy' symlink (which enters the python shell) and simply write: import kivy in the shell.
1 - filename: Kivy-1.9.0-osx.dmg
it installs  Kivy version 1.9.0: WORKS
2 - filename: Kivy-1.10.1_osx10.13.5_packaged_python3.6.5_r1.dmg
it installs Kivy version 1.10.1: WORKS
3 - filename: Kivy-1.11.0-python3.6.5.dmg
it installs Kivy version 1.11.0: WORKS
4 - filename: Kivy.dmg
it installs Kivy version 2.0.0 (latest): DOESN'T WORK -> no module named 'kivy'
Also the makesymlinks executable, where present (2 and 3) fails miserably, doesn't create the link to kivy in /usr/local/bin and you have to create it manually (Permission denied).  Something like sudo ln -s /Applications/Kivy3.app/Contents/Resources/script /usr/local/bin/kivy3
In ALL MacOS Virtual Machines I used (VMWare, VirtualBox and QEMU) kivy fails running even the simplest Hello World app, whatever was the way you used to install kivy and all its dependencies (pip, brew, MacPorts, framework, conda, ... what else...).
Running 'kivy main.py' (or python main.py) the result is always the same:

[CRITICAL] [Window] Unable to find any valuable Window provider at all!
sdl2 - RuntimeError: Failed creating OpenGL pixel format

The very strange thing is that if you run some SDL2 python examples, they works fine without any issue in whatever Virtual Machine... Bah?

https://github.com/kivy/kivy-sdk-packager/pull/62 should fix the issue in master. Try the newest Kivy.app once generated again.
I removed the makesymlinks GUI option from 2.0.0, because frankly it was confusing before, visually (what was shown on screen didn't make sense unless you already knew what makesymlinks does and this prevented using Kivy.app to repackage your own app because the end user shouldn't have to see anything beyond the option to install their app) and I couldn't get it to work IIRC correctly anyway.
About the VMs, I don't think anyone has managed to get kivy to display in a VM because Kivy needs minimum 2.0 gl, which is not available in any OSX VM because in a VM it doesn't have access to hardware acceleration.


🎃🍂 Use BigIntegers class to run algorithms

Create a new function to implement Fermat's Factorisation Method, Brute Force Method or Pho's Rollard method with BigIntegers.
See Main.java for current implementation without BigIntegers.

[x] Brute Force #10
[ ] Fermat's Factorization Method
[x] Pho's Rollard Method #18
[ ] Some other factorization method? #15

Unticked ones are not claimed.

Review the PR.

Hey, I can do this.Is it already assigned to somebody?

@richa-coder brute force has been done already. Fermat's Factorization Method and Pho's Rollard Method left.

okay,i will do it then
[image: --]
Richa Singh
[image: https://]about.me/richa-singh
https://about.me/richa-singh?promo=email_sig&utm_source=email_sig&utm_medium=email_sig&utm_campaign=external_links
On 19 October 2016 at 00:11, Yong Cho Yin<EMAIL_ADDRESS>wrote:

@richa-coder https://github.com/richa-coder brute force has been done
already. Fermat's Factorization Method and Pho's Rollard Method left.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/choyiny/factorizing-semiprimes/issues/3#issuecomment-254600622,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATs_eKnupMkjvrMnOjXU3S38p6QDFJ9Cks5q1RL1gaJpZM4KZAHF
.

Has the Fermat's Factorization Method already been implemented or can I work on that ?

@aarush22 nope, you can work on it.


Morning session exercise

Let your comments about the code, please.

You are doing a great job with the code, I think everything is fine, maybe you could better organize the syntax of the code with the class naming practices you mentioned.

Hey Sergio, great work with your Mobile version! I think it is responsive and you fulfill all the requirements.  However, if I may suggest something to improve it, I would make the commits much more descriptive, so the reviewer could see clearly the changes you made and understand better your code style...thank you very much! Have a nice day...

well done with the requirements. 👍


Adding required 'version' field for Helm Charts

Without the 'version' field, Argo CD application fails to sync with
rpc error: code = Unknown desc = helm template . --name-template prometheus-operator --namespace prometheus-operator --api-versions v1 --api-versions apiregistration.k8s.io/v1 --api-versions `...
... missing 'version' field

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


sneakers:run rake task bug and fix for it.

If I tried to run WORKERS=DoThings rake sneakers:runon latest sneakers version on my local machine on Ruby 2.2.2. I got following error:
rake aborted!
NoMethodError: undefined method `present?' for nil:NilClass
/Users/otobrglez/.rvm/gems/ruby-2.2.2@hunter/gems/sneakers-1.0.4/lib/sneakers/tasks.rb:29:in `block (2 levels) in <top (required)>'
Tasks: TOP => sneakers:run
(See full trace by running task with --trace)

So I decided to hunt down this bug and fix it. This is the patch. Hope it helps. :)

yikes!! awesome catch!! thanks :+1: :+1:

I was struggling to solve this issue for a long time, this helped me a lot. This works in rails console, but I was wondering why does "present?" not work in rake?

@shhrikatta I think it's because the .present? method is defined in activesupport which may not be loaded when the rake-task runs. Docs are here: http://api.rubyonrails.org/classes/Object.html#method-i-present-3F


connman: move "networking.connman" options to "services.networking.connman"

Motivation for this change
As part of the networking.* name space cleanup, connman should be moved to services.networking. The same will happen for example with networkmanager in a separate PR.
Side note: The connman module lacks a test. Anyone to contribute one?
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip" -> none
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after) -> minimal
[x] Ensured that relevant documentation is up to date -> not mentioned outside options.html
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @matejc @romildo

Where was there consensus on removing a networking namespace and moving it into services.networking.?

See https://discourse.nixos.org/t/networkd-sprint-2019-11-23-24-in-munich/4578/24 for background.

@GrahamcOfBorg test networking.scripted

I think we shouldn't have services.networking.connman but rather just have services.connman. Generally I don't think we should have services.networking as a lot of services have something to do with networking to varying degree and it will be impossible to draw a line where it belongs.

@globin Sure, I don't have any problem with that approach. We should probably also move services.networking.websockify to services.websockify then. This would render the services.networking namespace empty.

moved it again from services.networking.connman to services.connman


Feature/selective aruco detect

Hello!
This PR is adjacently related to this issue that I reported. However it does not directly fix that. While I was debugging the issue, I found that the aruco_detect node was also consuming CPU when the autodock algorithm was idle. Screenshot of htop shown below shows aruco_detect CPU consumption when IDLE:

Ideally, we should not be detecting/looking for aruco markers until an AutoDock action itself is started. But it seems like on default config, the aruco_detect is always on and looking for these markers resulting in high CPU consumption. Looking into this further, the aruco_detect node DOES have a neat service called /enable_detections that lets us enable/disable detections. So without touching the source code for aruco_detect, we will be able to manage the state of these detections from the autodock node itself.
This PR primarily helps implement this with the following changes:

Add service client and utility function to set detections
Set aruco detections based on autodock state

Some screenshots below from interactive testing with Turtlebot sim:
Below, you can see that aruco_detect consumption has reduced when the autodock is idle:

On startup itself, we disable detections so when the sim is launched with the rviz, we will NOT see any images from the /fiducial_images topic:
[INFO] [1652233347.443160, 0.000000]: Starting AutoDockServer Node
Enable detections response:  Disabled aruco detections.

Below, you can see that aruco_detect is back to normal consumption when autodock is in progress:

Now we start seeing images on the /fiducial_images topic:
Enable detections response:  Enabled aruco detections.
[INFO] [1652233573.711246, 104.431000]: Will attempt with 1 retry

When autodock fails:
[ERROR] [1652233576.152186, 106.457000]: Not detecting two side markers, exit state
[WARN] [1652233576.159298, 106.460000]: Failed to Dock attempt
[WARN] [1652233576.163408, 106.467000]: Attempting retry: 1/1
[INFO] [1652233576.180853, 106.479000]: State is not retry-able
[WARN] [1652233576.187205, 106.482000]: Not able to retry
Enable detections response:  Disabled aruco detections.
[WARN] [1652233576.213065, 106.503000]:  State: [IDLE] | Failed execute Dock Action

When autodock succeeds:
[WARN] [1652233696.103499, 210.448000]:  State: [ACTIVATE_CHARGER] | Docked, activate charger!
[ INFO] [1652233696.111709104,<PHONE_NUMBER>00]: ObstacleObserver received autodock state: 6
[WARN] [1652233698.406090, 212.458000]:  State: [ACTIVATE_CHARGER] | Celebration!!
[ INFO] [1652233698.411430833,<PHONE_NUMBER>00]: ObstacleObserver received autodock state: 6
[WARN] [1652233698.411304, 212.461000]:  State: [IDLE] | All Success!
[ INFO] [1652233698.422862282,<PHONE_NUMBER>00]: ObstacleObserver received autodock state: 1
Enable detections response:  Disabled aruco detections

Note that in rviz, once the docking action is complete, the image will look "frozen". That is because, we disable detections at the end of the action and aruco_detect will stop publishing to the /fiducial_images topic.
Points to ponder:

Currently the behavior is the detections are off on startup and are selectively enabled/disabled based on the dock state. Should there be an option to not do this when some sort of debug flag is passed for ease of debugging which in essence will turn off this feature and go back to previous default behavior?
There is now extra dependency on the /enable_detections service succeeding. In the event of failure of this service, we rely on the Autodock action's built-in retry mechanism to re-call the service instead of its own retry. I thought it was easier to keep track of the retries this way and conceptually consider that enabling/disabling detections is part of the docking algorithm itself.

@youliangtan I have updated the PR with your recommendations. Try it with the following two launch variations:
Default behavior when debug_mode set to True:
roslaunch autodock_sim tb3_nav_dock_sim.launch
debug_mode set to False that can be used for deployments:
roslaunch autodock_sim tb3_nav_dock_sim.launch debug_mode:=False
Note: Even though it was not in the scope of our original conversation, I used parameter to turn "off" the timer used to publish debug viz markers to visualize in rviz. If for some reason you think we should not be doing this, let me know and I can remove the logic around it.

I tested the debug_mode on simulation with the turtlebot. It works well!  Thanks again for the contribution


Any attempt for some new algorithms?

Will you keep it maintained for some new algorithms such  as YOLOv3 and so on ?
Or just stop updating it ?==

Yes it will be maintained. Bug fixes and minor updates are always going on and we are also planing some major updates after ICCV. However, we have no recent plan for YOLO-series and contributions are welcome.

Thanks for your reply !! It really helps.


index.less

在vue工程里
import Spreadsheet from 'x-data-spreadsheet'
时报错
This relative module was not found:
./index.less in ./node_modules/x-data-spreadsheet/src/index.js
很奇怪

在vue工程里
import Spreadsheet from 'x-data-spreadsheet'
时报错
This relative module was not found:

./index.less in ./node_modules/x-data-spreadsheet/src/index.js
很奇怪！

npm install less-loader less

npm install less-loader less

为什么要把源码暴露给开发者引用呢，暴露打包后的bundle会更好

npm install less-loader less

wouldn't it be better to remove the index.less from index.js and rather add it to the webpack.config.js entry? This would give me more control on the styles-compilation (e.g to configure the variables or even to integrate with sass).

npm install less-loader less

wouldn't it be better to remove the index.less from index.js and rather add it to the webpack.config.js entry? This would give me more control on the styles-compilation (e.g to configure the variables or even to integrate with sass).

npm install less-loader less

为什么要把源码暴露给开发者引用呢，暴露打包后的bundle会更好

是的 搞不懂为什么 。。。我为什么要在我的工程中使用less这样不必要的工具。

npm install less-loader less

为什么要把源码暴露给开发者引用呢，暴露打包后的bundle会更好

是的 搞不懂为什么 。。。我为什么要在我的工程中使用less这样不必要的工具。

For workaround.
I use the same version of less,less-loader described in x-spreadsheet/package.json .
"less": "^3.8.1",
"less-loader": "^4.1.0",
And it worked for me.
Hope this help.

npm install less-loader less

This should be a peer dependency.


Closes #193 Add optimization options to jaspr build command

Description
See #193 For details and rationale.
The implementation here inherits form the dart2js optimization options:
>>> dart compile js -h

Usage: dart compile js [arguments] <dart entry point>
  -h, --help      Print this usage information.
  -h -v           Show detailed information about all options.
  -o, --output    Write the output to <file name>.
  -O<0,1,2,3,4>   Set the compiler optimization level (defaults to -O1).
     -O0          No optimizations (only meant for debugging the compiler).
     -O1          Default (includes whole program analyses and inlining).
     -O2          Safe production-oriented optimizations (like minification).
     -O3          Potentially unsafe optimizations (see -h -v for details).
     -O4          More agressive unsafe optimizations (see -h -v for details).

The new, analogous, jaspr build command options:
>>> jaspr build -h

-O, --optimize               Set the dart2js compiler optimization level

          [0]                No optimizations (only meant for debugging the compiler).
          [1]                Includes whole program analyses and inlining.
          [2] (default)      Safe production-oriented optimizations (like minification).
          [3]                Potentially unsafe optimizations.
          [4]                More aggressive unsafe optimizations.

Note that dart compile js uses O1 as the default. Since jaspr build is intended for release/production, it seems that a better default here would be O2.
Users can change the optimization level via this command option. To revert to the previous build configuration, simply specify:
jaspr build --optimize 1
jaspr build  -O 1

Results
New results using this updated jaspr build (without any options specified).
du -sh build/jaspr/web/*.js && du -sh build/jaspr/web/components/*.js

Before
1.0M	build/jaspr/web/main.clients.dart.js
560K	build/jaspr/web/main.clients.dart.js_1.part.js
1.5M	build/jaspr/web/components/app.client.dart.js

After
360K	build/jaspr/web/main.clients.dart.js
180K	build/jaspr/web/main.clients.dart.js_1.part.js
528K	build/jaspr/web/components/app.client.dart.js

Type of Change

✨ New feature or improvement

Ready Checklist

[x] I've read the Contribution Guide.
[x] In case this PR changes one of the core packages, I've modified the respective CHANGELOG.md file using
the semantic_changelog format.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added myself to the AUTHORS file (optional, if you want to).

LGTM


ENH: implemented kendall tau distance

#7089
I put the code of function in scipy.stats, is it right?
What do you think about long name of the method, make it shorter or leave as is?
And is it required nan_policy(raise, propagate, omit) option?

Thanks @evgenyzhurko. scipy.stats looks like the right place.
@josef-pkt @ev-br on gh-7089 there's was no discussion about whether Kendall tau rank distance is worth adding. I'm +0.5, seems common enough.
Could make sense to call it rank_distance and allow other metrics within that same function (e.g. https://arxiv.org/abs/1207.2541)

I'm also +0.5 but haven't looked at the details (I'm in different neighborhoods at the moment.)
Reasonably good speed is important for these kind of functions. (I don't have problems writing computationally inefficient functions as a user, and having access to good library functions are very useful.)
In general I think distance measures are fine in stats, but the names should not be confusing
http://jpktd.blogspot.ca/2012/06/non-linear-dependence-measures-distance.html
(once upon a time I was writing blog posts)

26.03.2017 8:54 пользователь "Ralf Gommers"<EMAIL_ADDRESS>написал:

Thanks @evgenyzhurko. scipy.stats looks like the right place.
@josef-pkt @ev-br on gh-7089 there's was no discussion about whether
Kendall tau rank distance is worth adding. I'm +0.5, seems common enough.
Could make sense to call it rank_distance and allow other metrics within
that same function (e.g. https://arxiv.org/abs/1207.2541)

+1

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Nice blog post Josef, and I fully agree with "names should not be confusing". I can't make out though which (if any) of {kendalltau_distance, rank_distance} you find confusing. Can you clarify?

@rgommers Is it will be good if i'll create function rank_distance with optoinal param method='kendall' or 'spearman' and put this fucntion in stats  module? And how i can be with two type of kendall distance:

Kendall tau rank distance between two list(total number of discordant pairs) Example Wikipedia
Kendall tau rank distance between two rankings. "The Kendall tau distance between two rankings is the number of pairs that are in different order in the two rankings. For example, the Kendall tau distance between 0 3 1 6 2 5 4 and 1 0 3 6 4 2 5 is four because the pairs 0-1, 3-1, 2-4, 5-4 are in different order in the two rankings, but all other pairs are in the same order." (from Wikipedia).

Link https://arxiv.org/abs/1207.2541 say about second type of Kendall method, so i'll plan to put second type into rank_distance. And where i can put first method, maybe scipy.spatial.distance?

Lots of things need to be fleshed out here and not much activity since 2017 so I'm bumping the milestone again.
Also, look like performance is an important concern here and Cythonization looks like it could be helpful for some of those loops I see added.

There haven't been any comments / changes since I noted the need for improvements here before the last release, so bumping the milestone again.

Will this feature be released soon?

@superRookie007 no unfortunately not, it's stalled. Looking at this PR, there's both an unanswered query from the author (would be good if one of the stats maintainers can look at that), and unaddressed review comments.

Thanks @evgenyzhurko. There may be value in a statistical distance function like this, but I don't think it could be based on this PR now. The PR uses Python 2, there are merge conflicts, and the implementation should be unified with that of the relevant stats functions (e.g. stats.kendalltau, based on the information in gh-7089 that the distance and correlation are related and can be calculated from the same building blocks). The speed is also a concern.
from scipy import stats
import numpy as np
np.random.seed(0)
n = 10000
x = stats.rankdata(np.random.rand(n)).astype(int)
y = stats.rankdata(np.random.rand(n)).astype(int)
weights = np.ones_like(x)
%timeit stats.kendalltau(x, y)  # 1.54 ms ± 5.44 µs per loop (mean ± std. dev. of 7 runs, 1000 loops each)
%timeit _kendalltau_distance(x, y, weights)  # I gave it about a minute, but it didn't finish

There also hasn't been movement since 2018, so I'll go ahead and close. Note that a future PR can still find this one linked from gh-7089 and borrow what is still useful.


When timer is started again after a finished focus session, shows alert about finished session of length 0

After a focus session is finished, starting another one makes TamoStudy think that the length set is 0 and immediately finishes it:

Swapping the time from the dropdown for a different one (and then back) seems to solve it, but only until the next session.
(This is on Linux, despite the Mac-like theme, just in case that makes a difference)

Hey stayinside4ever,
Firstly I'd like to say that I'm glad you are using TamoStudy! It really means a lot to me and the future of this project.
In regards to your issue thread, I've actually coded it this way. (As in, it's not a bug or anything) I will though, rid the zero seconds as no one will study for zero seconds, and hopefully update the timer so if the user is on the 5-min increment the lowest possible session will be 5-min.
I could potentially also set up an automated session timer. for instance, if you selected 60 minutes for a session, when the session pop up is closed the time will go back to that 60 minutes (on the actual timer, without need for re-selection; although I believe it already worked like this? I can look into the solution)
As far as versions go, TamoStudy works the same no matter the operating system the user has.
Let me know your thoughts!

Thanks, Anthony! It does seem like a cool project!
If it's not meant to be a bug - why choose to do it this way? Most users would use the app to study for more than one session of the same length in a row, presumably. It would make sense to reset the timer start values to the amount already selected in the dropdown after closing the session end alert, rather than let it sit at 0 until the time is re-selected (which is what I assume you meant by "automated session timer"?).

It appears that the user that originally created this post is no longer a user on GitHub
This solution has been temporarily fixed: the fix is similar to if the use was just using the standard interval timer. The timer will reset back to zero, and the selected Index of the dropdown menu will return to it's original place - for the five-minute interval timer, this position is 05:00, however, the time will need to be set for the time being
Later, I will implement a solution in which the user can most likely choose how they want this setting to work, whether they want the timer to reset completely (consider, if they want to count their "break" time through TamoStudy as well, they would probably want to change it) instead of resetting it back to what they had originally.
This will close this issue thread.


Update test-file-03.md

@TinaLiuGirl : Thanks for your contribution to the Azure documentation! The author, @v-caxian, has been notified to review your proposed change.

#sign-off

@TinaLiuGirl: I'm sorry - only the author of this article, @v-caxian, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


characterize uniform random variable by entropy

Looks great!  Some comments:
I just added at the start of entropy_basic.lean the line
instance Fintype.instMeasurableSpace [Fintype S] : MeasurableSpace S := ⊤
which should hopefully make the MeasurableSingletonClass hypothesis automatic.
When mu has zero measure, the claim is true for trivial reasons, so we can wlog assume this.
When S is empty, then mu has zero measure.  So we can wlog assume that S is non-empty.
When mu is infinite, the claim is trivially true because the RHS is infinite.  So we can assume wlog that mu is finite.
But measurability of X is probably necessary and should be added to the explicit list of hypotheses.


add documentation for action system and optimistic components

I have had trouble understanding how these concepts work in relation to the rest of the client -- documentation on Mud.dev would be useful

For reference, here is the source code for the action system: https://github.com/latticexyz/mud/tree/main/packages/std-client/src/systems/ActionSystem
And here for optimistic components: https://github.com/latticexyz/mud/blob/main/packages/recs/src/Component.ts#L282-L397

Does anybody object to closing this? I don't even know what optimistic components are, so I assume we don't have them.


Mark destructors which can throw with noexcept(false)

Destructors in C++11 are implicitly marked noexcept(true). It's generally considered a bad idea to throw from a destructor, but I figured this was an easier change to make than to re-architect the whole thing to not throw.
I've tried LUABIND_NO_EXCEPTIONS, but that seems to be a somewhat unmaintained branch.
Use BOOST_NOEXCEPT_IF so that in C++03 it evaluates to nothing.

See #25.

Oh, interesting. It looks like build-improvements is actually much further along than master, is that a better one to use?


[Tech-Debt] Refactor the repeated blocks in compose-builder/makefile to use script or function

🚀 Feature Request
Relevant Package [REQUIRED]

 This feature request is for Makefile of docker-compose
Description [REQUIRED]
 A clear and concise description of the problem or missing capability...
To reduce the clutter of makefile, refactor similar repeated code into shell script or makefile function.
Describe the solution you'd like
 If you have a solution in mind, please describe it.
Describe alternatives you've considered
 Have you considered any alternative solutions or workarounds?

On hold until after 31. release.


Add dolly-v2-12b and RedPajama-INCITE-7B-Instruct

Databricks' dolly-v2-12b, an instruction-following large language model.
https://huggingface.co/databricks/dolly-v2-12b

@yuravorobei
Dolly image
Unfortunately, after more than an hour of waiting, I could not get a working container from the only provider available ingress.gpu-testnet.praetorapp.com

@Dimokus88
Strange, for me with the same provider and the same SDL it starts in 5-6 minutes:

@Dimokus88 Strange, for me with the same provider and the same SDL it starts in 5-6 minutes:

I've been waiting for more than an hour on the same provider, but the page is still not available.
Let's ask @arno01  to check out this deployment as well.

@yuravorobei ok, I got confirmation that the deployment was working, the error was in my internet connection.
Modify the root README.md ( https://github.com/akash-network/awesome-akash/blob/master/README.md ) of the awesome-akash repository to include a link to your deployment and you're ready to merge.

I closed my previous PR 406 (https://github.com/akash-network/awesome-akash/pull/406), because in this PR duplicates the addition of the same deployment. So two my deployments are added to this PR - redpajama-incite-7b-instruct and dolly-v2-12b.
I also updated the root README.md file and include links to both my deployments.

Ready to merge @andy108369 @brewsterdrinkwater

@Dimokus88 @yuravorobei , there is just a conflict to resolve, then I will merge this!

@brewsterdrinkwater , conflict resolved

@Dimokus88 @yuravorobei , there is just a conflict to resolve, then I will merge this!

Conflict resolved, this is an actual PR @brewsterdrinkwater


AJP support in standalone components

We should retain the support of AJP13 in 3.0+ for loadbalancing purposes.
http://www.appsdev.is.ed.ac.uk/blog/?p=525

We decided not to migrate to fatjar. We believe that it is a good idea to stay with the war, which is also runnable as standalone application (so it's a fatwar). So if you need to use AJP, you can still use it when deploying the fatwar to an external tomcat. I don't think it is a good idea to support this with the standalone applications, because OSIAM can not be load balanced with its state.

If it's ok with you, I'd like to keep this issue open until AJP functionality has been proved working with 3.0. Just so we don't forget that AJP connectivity is actively used in some projects and thus has to be retained.

Just so we don't forget that AJP connectivity is actively used in some projects and thus has to be retained.

Then, IMHO, we should offer this functionality in the standalone version too, because I suppose, that these projects also want to migrate to the standalone version eventually.


Add jan.alphadev.net

This PR is:

[X] Adding a new domain
[ ] Updating existing domain size
[ ] Changing domain name
[ ] Removing existing domain from list
[ ] Website code changes (512kb.club site)
[ ] Other not listed

[X] I used the uncompressed size of the site
[X] I have included a link to the GTMetrix report
[X] The domain is in the correct alphabetical order
[X] This site is not a ultra lightweight site
[X] The following information is filled identical to the data file

I confirm that I have read the FAQ section, particularly the two red items around minimal pages and inappropriate content and I attest that this site is neither of these things.

[X] Check to confirm

- domain: jan.alphadev.net
  url: https://jan.alphadev.net/
  size: 76.7
  last_checked: 2023-08-02

GTMetrix Report: https://gtmetrix.com/reports/jan.alphadev.net/ccimAxqF/

Thanks!


Add support for parameterized macros

In some cases, there are repeated segments of condition text that differ only in a path, process name, etc. For example container.image startswith <prefix> or container.image.repository contains <prefix> is a way to check for a container name containing a prefix.
To address cases like this, it would be useful to have parameterized macros, for example:
- macro: container_image
       param: name
       condition: container.image startswith name or container.image.repository contains name
...
      condition: container_image(<prefix>) or ....

This would allow avoiding having repeated text for these common patterns.

We should keep this on the roadmap.

Keep
On Fri, Oct 11, 2019, 6:39 PM stale[bot]<EMAIL_ADDRESS>wrote:

This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Thank you
for your contributions.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/falcosecurity/falco/issues/510?email_source=notifications&email_token=AAA5J4ZBYQKW4PU3MOK33CDQOCT27A5CNFSM4GTTOGGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBARREA#issuecomment-541137040,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA5J44SUDYUGCL26YZIY33QOCT27ANCNFSM4GTTOGGA
.


Add OpenCL.DebugInfo.100 DebugValue propagation pass

We cannot find actual cases that need this PR for now and we decided to not include it for the code simplicity.


Use the parser's locations in use_args

Fixes https://github.com/sloria/webargs/issues/44

@sloria Thanks for merging! Any rough ballpark on a 0.13.1 release?


Investigating tox for local integration tests

Didn't make a lot of progress on this PR. @smcguire-cmu if you're interested in taking a look, please do! However, since it's been sitting for so long, we should go ahead and close it for the time being. We can alway reopen if needed.


Warning message shows in published MODFLOW model instance

When a MODFLOW model instance is published, it shows a warning message like below.

This message should not be shown to non-owners of the resource. It should only be shown to owners and editors of the resource.
Step 1: Disable this message for now (quick fix).
Step 2: Only show message if owner/editor is viewing the resource.

Nice labeling @goodalljl !

I feel so powerful assigning tasks to others :)

@goodalljl @dtarb do you think this is "hotfix" worthy?

Not www hotfix worthy.  Hotfix to www should be used only for something that is a functionality breaking bug.  This is a message that does not break any functionality.  This is premised on frequent small releases so that waiting for the next release is not long.
Hotfixes to a candidate release undergoing beta testing have a lower bar for getting in, but we are not in a candidate release testing phase right now.

Okay. That makes sense, @dtarb. I also appreciate you including the broader principle. That is helpful.

In addressing this issue, @mohamedmorsy  and I thought of two alternatives:

The warning shows up only in edit mode.
The warning shows up in view and edit mode but only for resource owners or those who have edit privileges

We think it's better to do number 2 so it's clearer to the user that there are probably files missing from the resource. If it only shows in edit mode, it might not be noticed. We have either solution ready to commit. Do you have an opinion @dtarb? @goodalljl?

I support No. 2.

I agree.
On Thu, Nov 2, 2017 at 3:43 PM David Tarboton<EMAIL_ADDRESS>wrote:

I support No. 2.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hydroshare/hydroshare/issues/2370#issuecomment-341536147,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEmWVJgSyHKF_6kwpZsdnoRn0-PIuJ2Hks5syhtKgaJpZM4QIKny
.

--

@jsadler2 1.14 is going out next week. We should be able to close this ticket then


Add support for pinning a package to a specific index

Discussed this with Armin -- pip doesn't support it, and it seems like a big problem? If you have an internal index, but also want to get some packages from PyPI, there's no way to ensure that your internal packages come from your internal index. Packages on PyPI could even shadow them.

Please consider dependency confusion attacks<EMAIL_ADDRESS>Use of --extra-index-url as they are presently used are a security vulnerability.
PEP 708 is a yet-to-be-implemented approach to improving the security posture.

I would love to implement improvements to this (like the ability to pin a dependency to a specific index)… We specifically held off and implemented indexes as-is to be spec-compliant. I’ll implement this as soon as it’s supported and there’s clarity on how installers should handle it!

Makes sense.
I think you may receive a lot of duplicate feature requests from the folks who do misuse --extra-index-url and who aren't aware that it is not currently intended to be used to append additional sources of dependencies, it's purpose is to provide a set of fallback mirrors of the primary index (--index-url) which is PyPI in the general case.
We may need to consider offering some help as mentioned in the PEP to move this along.
In the short-term, if you don't want to bug-for-bug implement pip, we may need to point people at alternatives like https://github.com/uranusjr/simpleindex to help them merge indexes behind the scenes on localhost. I don't think many will like it 😂

@groodt can you point at official docs that confirm this use of extra index is indeed misuse? To me it fits well with local versions for example?
In any case, thanks for the links to simple index, this will be useful if case you're right and UV does not allow this use of extra index :) A bit sad to have to run two local servers instead of one, but that's not that bad.

I don't quite understand why this is so hard

From what I recall (I quickly refreshed my memory on the issue but didn’t review the details) it’s a “design decision that was made a long time ago” type of complexity. Pip has built a bunch of choices on top of the “all indexes are equal and get merged” model, and it’s hard to know what we’d need to change if we were to revisit that decision. Add to that the need for backward compatibility and it’s a much bigger question than people saying “just pick the index I ask for” will accept.
For uv, I foresee the following issues:

Compatibility - you’ll diverge from pip in both subtle and not-so-subtle ways. This isn’t a bad thing, but your stated intention is to be compatible with pip, so you need to make choices here.
Being an outlier - the “all indexes are equal” model is not just something pip does. Standards like PEP 708 are built on the idea, so you may have trouble fitting that standard into your implementation. More generally, you’ll have to make a bunch of UI and design issues where there is less pre-existing experience to draw on.
Scope creep - people start wanting things like index priorities (“get these from piwheels when you can, but fall back to PyPI if there’s nothing at all published on piwheels”) which have their own issues.
You open yourself up to the idea that a package is no longer identified by just name and version - where it came from becomes important as well. This may have wider implications - for example, SBOM data might need extra information like source URL.

On the plus side, you’ll be offering a solution to something users have been wanting for a long time, and which is often characterised as a security issue. And practicality may well beat purity here.

can you point at official docs that confirm this use of extra index is indeed misuse

It doesn’t describe it as “misuse”, but the pip docs are clear that we treat all indexes as equal: “There is no ordering in the locations that are searched” from here. We (pip) could add a guide-type article discussing this in more depth, but we don’t have one currently.

There’s a small security warning in the pip docs here
Using this option to search for packages which are not in the main repository (such as private packages) is unsafe, per a security vulnerability called [dependency confusion](https://azure.microsoft.com/en-us/resources/3-ways-to-mitigate-risk-using-private-package-feeds/): an attacker can claim the package on the public repository in a way that will ensure it gets chosen over the private package.
There is also an in progress pip PR to make this more explicit here https://github.com/pypa/pip/issues/11694
Here’s a major recent dependent confusion attack that impacted PyTorch (caused by instructions to use —extra-index-url) https://news.ycombinator.com/item?id=34202662

I'm not sure this is to answer my previous question ("can you point at official docs that confirm this use of extra index is indeed misuse"), but I was especially referring to "it's purpose is to provide a set of fallback mirrors of the primary index".
I distinguish two use-cases for extra indexes:

extend main index with additional projects (subject to dependency confusion)
extend specific projects in main index with additional versions (not subject to dependency confusion)

My understanding of your "append additional sources of dependencies" was that it referred to case 2, but now I think you were speaking of case 1.
So, to rephrase, and given pip currently considers all indexes to be equal, is case 2 is a misuse too?

Stepping back from the question of "why is this so hard", @groodt is correct that PEP 708 is the better solution here. Otherwise, does the user need to specify an explicit index for the whole of their internal package's dependency tree? What if someone adds a new internal module, and forgets to add it to the list of "must come from the internal index" list in all of their install jobs? Are we going to consider that as "user error"? The torchtriton attack took exactly this form. Or an attacker could compromise a public dependency of your internal project.
Having an index pin option doesn't prevent you from needing to handle the consequences of a "all distributions with the same name and version are interchangeable" model. It just gives users a manual way of firefighting issues with that model.

So, to rephrase, and given pip currently considers all indexes to be equal, is case 2 is a misuse too?

It's not that "pip considers all indexes to be equal" but rather that "pip considers all distributions with the same name and version to be interchangeable regardless of which index they came from". The difference is subtle but important. Whether case 2 is a problem depends on whether you trust the "main index", just the same as with case 1. The trust issue is what's important here rather than what is "considered equal"[^1].
The --extra-index-url argument for pip was added long ago, in simpler times when people weren't anywhere near as worried about attackers targetting PyPI, and nobody was running multinational businesses based on Python code. Trust was generally assumed to be present, and in particular no-one was worrying about relative trust between indexes. Things have changed, for better or worse, and --extra-index-url doesn't match the new reality. This is why one of the options pip is considering is simply removing it, and demanding that users pick a single index and ensure that they trust that one index. That's unlikely to ever happen because the breakage would be significant, but it's absolutely an option that a new project like uv could (and should) consider.
To answer your question more explicitly, your case (2) is a "misuse" in the sense that it has risks (the same as case 1). The risks may not be a dependency confusion attack, but they do include compromise of the PyPI account owning of the code you're extending. Is that a more acceptable risk? Only you can decide that.
The point is that mixing indexes with different trust levels[^2] is the problem here. Even the "mirror PyPI" case involves a risk if the mirror is compromised.
[^1]: You could argue that if you don't trust two indexes equally, you don't "consider them equal", I guess...
[^2]: Within the same install command, which is why pinning for a set of named packages isn't a sufficient solution.

Thanks @pfmoore!
(Side note: I just discovered that PDM supports respecting the order of indexes: https://pdm-project.org/latest/usage/config/#respect-the-order-of-the-sources.)

Just as an example (and yes, it's a pathological case) if you have ordering, suppose you have index1 and index2 (ordered with 1 having priority over 2). Index 1 contains A 1.0 and B 1.0, with A 1.0 depending on B. Index 2 has B 2.0. If you install A, do you get B 1.0 or B 2.0? If the answer is 1.0, why did you bother specifying index 2? If you get B 2.0, and someone now adds A 2.0 to index 2, and changes B 2.0 to depend on A > 1.0, is the correct thing to upgrade A to 2.0, or downgrade B to 1.0?
The point here is that there's multiple possible choices, and if you don't factor index priority into the core of your resolution algorithm, you end up with a system that users won't have a good intuition about, and which might depend on implementation details. Both of which can lead to security issues. I'm not saying that PDM has such a problem - they may well have considered all of this. Just that "which index did this come from" is an extra axis you have to consider as part of resolution, not just something you can keep separate from the resolver.
Anyway, the key point for uv, and in answer to the question @charliermarsh asked above, is that this is why pip is still trying to work out a good answer to how we could allow users to choose which index to use at a more fine grained level than "per install".

In my case, all packages from index 1 take precedence, even if higher versions are available in index 2.

Cool, so your approach to priority is like pinning, but with the decision on whether to pin being "if package A is in index 1, then pin to index 1, else fall through". That works, but it doesn't support the piwheels case where they supplement PyPI with wheels for the raspberry pi architecture, letting installers fall back to PyPI if the wheel isn't valid for the user's architecture (at least that's how I understand what they do...)
Getting into this much detail may be more than the uv maintainers want, though. Let's see if this is useful to them. I don't want to come across as saying that this is too hard to do - it's too hard for pip to easily do (which is what triggered my original comment) but uv may well have different priorities and choose different trade-offs. They also don't have backward compatibility to deal with (unless they want to match pip feature for feature).

@pfmoore Thank you very much for your detailed comments here. They've been super helpful.
I'd like to make a small tweak to how uv behaves today that will hopefully resolve at least some of the issues users are hitting (#1377, #1600, #1451) in practice, but do it in a way that doesn't make uv behave like pip (which, AIUI, is to consider all available packages from all indexes, without any guaranteed priority order).
So today, our implementation works by giving a preference order to the indexes made available to uv:
https://github.com/astral-sh/uv/blob/995fba8fec6ac6569e5f7ffe8d244faddef98692/crates/uv-client/src/registry_client.rs#L191-L210
That is, given uv pip install --index-url foo --extra-index-url bar --extra-index-url quux package, it will first try foo, then bar and then quux. Once a package is found, uv will stop looking for it in any other indexes. So for example, if package is found in bar, then that means it definitely wasn't found in foo, and it may or may not be in quux. We never check.
Since --index-url defaults to PyPI, that means something like uv pip install --extra-index-url bar package will check PyPI first for package, and if it's found, stop. I think this turns out to be the reverse of what the commonly desired behavior is. And while it won't address every use case, I think a nice stop-gap solution here would be to flip the preference order with respect to --index-url and --extra-index-url. That is, we check PyPI after all other extra index URLs given.
This will not match pip's behavior in every case, but I think it does help address some of the common cases and I think also helps to mitigate the dependency confusion concerns. That is, if package is in bar, then uv would completely ignore any packages named bar on PyPI. (Today, that's flipped. If package is on PyPI, then it will completely ignore any package on bar.)
Otherwise, I do agree that if we can get away with it, we should probably avoid encoding pip's behavior of including packages from all indexes without regard to priority into uv. But we can certainly revisit this if my tweak above doesn't pan out.
And popping up a level, I do think we'll want to absolutely address the multi-registry issue by giving users more control when we build out more project management features. But I think until then, we'll probably want to avoid adding too many additional abstractions into uv pip install for dealing with multiple registries. And of course, I suspect we will want PEP 708 support eventually too.

Nice! Worth noting is users who want the flipped behavior can do uv pip install --index-url https://private-index.com/simple --extra-index-url https://pypi.org/simple, right?

Nice! Worth noting is users who want the flipped behavior can do uv pip install --index-url https://private-index.com/simple --extra-index-url https://pypi.org/simple, right?

Ah yes! I meant to call that out, but yes indeed.

... while a proper solution would be enforcing association between specific packages and registries.

I think this is roughly what I meant above with:

And popping up a level, I do think we'll want to absolutely address the multi-registry issue by giving users more control when we build out more project management features.

I have a similar problem.

Lets say you have a PKG with 1 yanked version available in UV_INDEX_URL or pypi.org
You have the same package in your UV_EXTRA_INDEX_URL, but with valid versions.

when PKG is a dependency of something that we try to install, it works with latest uv version. :ok:
trying to install the PKG, gives an error: :no_entry:

error: Missing `Content-Type` header for <EXTRA_INDEX_URL>/PKG

When you have multiple indexes in UV_EXTRA_INDEX_URL and the PKG is in the first extra:

same behaviour as with just 1 extra  :no_entry:

When the PKG is not in the first extra, but in subsequent extra indexes:

installation is not possible, it only looks for the package in the UV_INDEX_URL  :no_entry:

× No solution found when resolving dependencies:
  ╰─▶ Because only PKG==0.0.0a1 is available and PKG==0.0.0a1 is unusable because it was yanked (reason: not stable), we can conclude that all versions of PKG cannot be used.
      And because you require PKG, we can conclude that the requirements are unsatisfiable.

      hint: PKG was requested with a pre-release marker (e.g., any of:
          PKG<0.0.0a1
          PKG>0.0.0a1
      ), but pre-releases weren't enabled (try: `--prerelease=allow`)

What's the case in which you're seeing error: Missing Content-Type header for <EXTRA_INDEX_URL>/PKG? That seems like a bug in the registry, but perhaps we can handle it gracefully.

What's the case in which you're seeing error: Missing Content-Type header for <EXTRA_INDEX_URL>/PKG? That seems like a bug in the registry, but perhaps we can handle it gracefully.

UV_INDEX_URL is undefined.
UV_EXTRA_INDEX_URL points to a NEXUS instance with pypi repo

It only happens if I try to install a package that is available in both pypi.org and in the nexus.
Installing packages that are only in the nexus or pypi works.

I think you want https://github.com/astral-sh/uv/issues/1754.

Yes I can confirm using --no-cache removes the error message.
Do you know anything about using multiple extra-index-urls, is that supposed to work?
it only resolved the package if it was in the first one, tried --extra-index-url and env too.

Do you know anything about using multiple extra-index-urls, is that supposed to work?
it only resolved the package if it was in the first one, tried --extra-index-url and env too.

See #2083

My package is only available in one of the extra-index-urls outside of index-url, but it still cannot find it, if it's not the first.

Do you know anything about using multiple extra-index-urls, is that supposed to work?
it only resolved the package if it was in the first one, tried --extra-index-url and env too.

See #2083

My package is only available in one of the extra-index-urls outside of index-url, but it still cannot find it, if it's not the first.

It might be worth opening a new issue with a repro.

It seems like gitlab is doing an automatic pypi lookup:
https://docs.gitlab.com/ee/user/packages/pypi_repository/#install-a-pypi-package
In [GitLab 14.2 and later](https://gitlab.com/gitlab-org/gitlab/-/issues/233413), when a PyPI package is not found in the package registry, the request is forwarded to [pypi.org](https://pypi.org/).

Probably that's why it finds the yanked version again and stops looking at the subsequent extra-index-urls

The next version of uv will include an opt-in flag to allow users to search for packages across multiple indexes. This is less secure, but closer to pip's behavior.
https://github.com/astral-sh/uv/pull/2815

@smphhh me too, and I've used poetry plugin to accomplish something similar.  I know it's funky but it's a big 80/20 for corporate usecases.  It solves the problem of "if I pin a dependency to an index, from which index do I get the transitive dependencies?" for a narrow but useful set of cases.

Removing with wish label here, as we expect to implement this in tool.uv.sources

Current uv docs for dependencies make it sound like this feature is already available. Let to a bit of churn trying to figure out how to use it 😅
https://docs.astral.sh/uv/concepts/dependencies/

tool.uv.sources enriches the dependency metadata with additional sources, incorporated during development. A dependency source can be a Git repository, a URL, a local path, or an alternative registry.

Does uv not expand environment variables in the extra-index-url setting in pyproject.toml? I couldn't get this to work:
[tool.uv]
# uv doesn't expand ARTIFACTORY_USER and ARTIFACTORY_API_TOKEN?
extra-index-url =<EMAIL_ADDRESS>
Great work on uv!

Please comment on https://github.com/astral-sh/uv/issues/5734 regarding environment variable expansion.

This is starting to come together in https://github.com/astral-sh/uv/pull/7481.

Poetry's design is interesting: https://python-poetry.org/docs/repositories/. It feels a bit more complex than is necessary though.

Here's an interesting pattern w/ poetry I've seen used to allow local dev on osx with pytorch but also enable GPU usage on linux.
[tool.poetry.dependencies]
...
torch = [
    ...
    { markers = "sys_platform == 'darwin' and platform_machine == 'arm64'", url = "https://download.pytorch.org/whl/cpu"},
    { markers = "sys_platform == 'linux' and platform_machine == 'aarch64'", url = "https://download.pytorch.org/whl/cpu"}
    { markers = "sys_platform == 'linux' and platform_machine == 'x86_64'", url = "https://download.pytorch.org/whl/cu121"}
]

Good news! 🎉
Initial PEP 708 support has arrived on pypi

What about CLI? Will uv support adding dependencies with custom registries via uv add?

What about CLI? Will uv support adding dependencies with custom registries via uv add?

It looks like #7747 sorta does that. It doesn't allow just giving the index name though, you have to give the name and url. uv add --index internal=https://internalindex.url somepackage Allowing just using an existing index name would be a nice improvement.


Histogram scatter sync

This PR adds synchronization between the selection in the first histogram viewer on page 4 (that shows data for the students' class), and a subset in the scatter viewer on the same screen. Since the selection in the histogram is along the age component of the summary data, which we can't link to the individual student measurements, this is achieved via a custom listener (HistogramListener) descended from glue.core.HubListener.
Additionally, since a student won't have access to the standard glue UI, they won't be able to change the active subset in the usual way. To get around this, I've augmented the activate and deactivate methods for the x-range selector on the histogram viewer to set the active subset to the (only) subset defined on the histogram viewer when the tool is activate and unset the active subset when the tool is deactivated. The function that I used to do this is extend_tool, which was added to utils.py - I anticipate that we may need to do this for some of the other viewers in the story.
Edit: I also added a line fit to the student's selected subset (that vanishes when the selection is empty/deleted), as well as a button to let them clear their selection (necessary since they don't have access to the glue UI that one would typically use to do this).

The described functionality seems to work for me.
Some related things I noticed:

If you first select within the scatterplot using Glue features (which I can't seem to unselect), this undermines what happens when you select in the histogram after. Shall we turn of Glue selector for scatterplot?
Didn't My value and Class value used to display a vertical line with age estimates in the histogram? It's not activating anything for me.
Will the data available in the scatterplot change if we switch from MY CLASS to ALL DATA? Do we want it to?
Selection tool for ALL DATA histogram doing some unexpected stuff that I don't understand.
Interesting that the color of the selection changes after every time you use CLEAR SELECTION. It's fun, but perhaps confusing to a student? just a thought.


setGuard and deleteGuard display as settings transactions

Description
For the setGuard and deleteGuard transaction types, both should be displayed as Settings transactions. Similarly to changeMastercopy transactions
Environment

Browser: Chrome
Wallet: MetaMask
Chain: Rinkeby

Steps to reproduce

Open rin:0x6cf158C37354d8da5396fb6d3e965318CCf119c1 safe and observe that the setGuard transaction

Expected result
setGuard and deleteGuard transaction should display as Settings transactions
Screenshots

Shouldn't this be an issue on the client gateway?

Currently there are 3 txTypes that display the "SettingsIcon" in the TransactionList:

Creation tx
SettingsChange
Module transaction (tx identifyed by txInfo.type === "Custom" without executionInfo)

One way we could display setGuard and deleteGuard as per the issue description is like Richard comments:

Changing the Client GW. Returning these 2 transaction types as "SettingsChange"

My hesitation however is if these two transactions fall under the "SettingsChange" category. Is that a correct categorization?
If so, let's move this issue to the client gateway.


Requirement test/uf

Please review

Added support for forwarder transport type.
It will use FileMonitorEventIngestor Class to ingest events to Splunk. Similar to mod input it requires host, source, source type defined with default host_type = "plugin"

<transport type="forwarder" host="sample_host" source="sample_source" sourcetype = "aix_secure" />

Added forwarder TA to "TA_requirement_test_uf"
Added test logs to  "test_requirement_test_uf"  containing both failure and success test cases
Updated unit tests

:tada: This PR is included in version 1.10.0 :tada:
The release is available on:

v1.10.0
GitHub release

Your semantic-release bot :package::rocket:


How to know the size of the file after converted?

Please tell me How to know the size of the file (fileSize  not width and height) after converted

Hello, there's not really enough information in your question to help me help you with what you're trying to achieve. What output method? Does size refer to file size, image dimensions?
Did you see the documentation for the various output functions?
https://sharp.pixelplumbing.com/en/stable/api-output/

info contains the output image format, size (bytes), width, height

sharp(input)
  .toFile('output.png', (err, info) => { ... });

file size
not (width and height)

Thanks, the following should help you:
sharp(input)
  .toFile('output.png', (err, info) => {
    // info.size contains the file size
  });


Adding 'test' environment to playbook

The test environment currently points to the prod environment for now, but I wanted to at least put this in place until we have that environment fully stood up.


Error: Unexpected key 'entryPoint' found in params.overrides.containerOverrides[0]

Since https://github.com/railsware/github-actions/commit/9889d87aad9ffd4c0bc373bb7c962d9ee3ea65f2 I am running into this error when using the run-ecs-task action.

Hey! Sorry to break this for you - we have rolled back this change in tag 1.1.3.


Results of KE-Omni-v1.5

Here are the results of KE-Omni-v1.5, which has been fine-tuned from KE-Omni-v1.0 to enhance its safety capabilities.

Model
AlpacaEval
CommonEval
SD-QA
MMSU
OpenBookQA
IFEval
AdvBench
Overall

KE-Omni-v1.5
3.82
3.20
31.20
32.27
58.46
15.00
100.00
53.90

Hi,
Thank you for sharing the results! We have updated the leaderboard accordingly.


MARPA_LINKAGE seems to break many installations

@jddurand I brought the latest Libmarpa into Marpa::R2 developer's version and the MARPA_LINKAGE change seems to break things on a lot of systems.  An example is in this log.  Maybe I should back this change out.    Suggestions?

@jeffreykegler this is because the generated sources are missing extern keywords, i.e.:

marpa.c from Marpa-R2-11.002_000:

# 17051 "./marpa.w"
             const int marpa_major_version;
 const int marpa_minor_version;
 const int marpa_micro_version;
...
# 576 "./marpa.w"

 const int marpa_major_version= 11;
 const int marpa_minor_version= 0;
 const int marpa_micro_version= 1;

marpa.c from Marpa-R2-10.000000

# 16805 "./marpa.w"
extern const int marpa_major_version;
extern const int marpa_minor_version;
extern const int marpa_micro_version;
...
# 571 "./marpa.w"

const int marpa_major_version= 9;
const int marpa_minor_version= 0;
const int marpa_micro_version= 3;

@jddurand The change happens in one of your commits: https://github.com/jeffreykegler/libmarpa/commit/85001583fda9b4f90490ed5e131e1ddee84fa297.
Any suggestions what to do here?  It's tempting to just back the whole thing out, as too high-risk.  You did warn me that the change was experimental.

I made a comment in this commit. This is experimental, sure, though IMHO if you look at a marpa.c generated with a marpa.w that takes into account my comment, and find that the only difference are those "extern" thingy, this ought to work.
Still, this remain experimental, as you said.

I think, regretfully, I will back this commit out.  A CPANtesters release can take weeks or even months to go on obscure systems, making experiments of this kind a real problem.  The cost-benefit ratio just doesn't work for this one.  Sorry.

I did the back-out in commits https://github.com/jeffreykegler/libmarpa/commit/4d4bf0959cfb542b726cb8b3990f9d046e92393f, https://github.com/jeffreykegler/libmarpa/commit/d02ef9090be85fe7668c72e70a24b739fa3940b7, and https://github.com/jeffreykegler/libmarpa/commit/2ee0c21999714901a0d852943110baad65512454.  Testing looks a lot better.  I will wait a few days, and if the testing continues to look good, schedule this issue for closing.

Testing looks good.  Absent feedback to the contrary, I will close this issue after a couple of days.

Closed per https://github.com/jeffreykegler/libmarpa/issues/125#issuecomment-1358115456.


Fix plan definitions for cqf-ruler master

Latest changes in cqf-ruler require each plan definition action to have a trigger that matches the hook name. All plan definition actions need this snippet:
  "trigger": [{
    "type": "named-event",
    "name":"patient-view"
  }],

Resolves with https://github.com/OHSUCMP/htnu18ig/commit/bea75df95e9a728d839e34b680b3d46296fd2dc5


[Feature Request] More options in filenamecaption

Adding more options to customize SendFile message in filenamecaptions like :
Servername
Filename
Filesize
Byauthor
All form of dates

@xTeooo I will add everything else but dates already work, see here

Okej thanks @get-got 🤩


Colors are not respected in a Uno Project on MacOS

Issue:
In the following code, I use: Red, Dark Orange and Green, but on MacOS, I see Purple, Blue and Green

MacOS

PC

ScottPlot Version: (What NuGet package are you using?)
5.0.39
Code Sample: See http://scottplot.net/faq/repro/ for tips about creating reproducible code samples
            var array = new double[]{1, 2, 3};
            var sig1 = WinUIPlot1.Plot.Add.Signal(array);
            //sig1.Axes.XAxis = WinUIPlot1.Plot.Axes.Bottom; // standard X axis
            sig1.Axes.YAxis = WinUIPlot1.Plot.Axes.Left; // standard Y axis
            sig1.Color = Colors.Red;
            WinUIPlot1.Plot.Axes.Left.Label.Text = "Amperage";
            WinUIPlot1.Plot.Axes.Left.Label.ForeColor = Colors.Red;

            WinUIPlot1.Plot.Axes.Bottom.TickLabelStyle.IsVisible = false;
            WinUIPlot1.Plot.Axes.Bottom.MajorTickStyle.Length = 0;
            WinUIPlot1.Plot.Axes.Bottom.MinorTickStyle.Length = 0;

            // create a second axis and add it to the plot
            var yAxis2 = WinUIPlot1.Plot.Axes.AddLeftAxis();
            // add a new plottable and tell it to use the custom Y axis
            var sig2 = WinUIPlot1.Plot.Add.Signal(array);
            //sig2.Axes.XAxis = WinUIPlot1.Plot.Axes.Bottom; // standard X axis
            sig2.Axes.YAxis = yAxis2; // custom Y axis
            sig2.Color = Colors.DarkOrange;
            yAxis2.LabelText = "Voltage";
            yAxis2.LabelFontColor = Colors.DarkOrange;

            // create a second axis and add it to the plot
            var yAxis3 = WinUIPlot1.Plot.Axes.AddLeftAxis();
            // add a new plottable and tell it to use the custom Y axis
            var sig3 = WinUIPlot1.Plot.Add.Signal(array);
            //sig2.Axes.XAxis = WinUIPlot1.Plot.Axes.Bottom; // standard X axis
            sig3.Axes.YAxis = yAxis3; // custom Y axis
            sig3.Color = Colors.Green;
            yAxis3.LabelText = "Power";
            yAxis3.LabelFontColor = Colors.Green;

Hi @swharden, I noticed @ArchieCoder opened this issue and wanted to have your feedback as it is platform-specific to see if it is something to be fixed on the ScottPlot side or the Uno Platform side.

This issue is very similar to the following (inverting red and blue channels):

#2818
Red and blue channels are inverted with Skia.Gtk on M1-based Macs #8580

Although it is strange, because this issue was closed with the following commit bdf6c57.

This issue is very similar to the following (inverting red and blue channels):

SP5 Avalonia: Wrong colors in Android projects #2818
Red and blue channels are inverted with Skia.Gtk on M1-based Macs #8580

Although it is strange, because this issue was closed with the following commit bdf6c57.

Yeah maybe related to previous https://github.com/unoplatform/uno/issues/8580 (cc @spouliot)

This is generally an issue when the Skia surface is created.
That could be Uno (because we definitively create some) but it should show up in our own rendering. It could also be created inside ScottPlot with the wrong options.
Sadly it's not always possible to use the same, default Skia code to target all platforms :( That was the root issue for GTK+ on Apple Silicon Macs.
@ArchieCoder just to be sure was this tested with netXX-desktop on Mac ? or netXX-maccatalyst ? or netXX-macos ?

@spouliot net80-desktop

@ArchieCoder If you use Uno.SDK 5.4.8 and update Skia to 2.88.9-preview.1.1 then it should work. I'll double check that my earlier fix did not influence the results...
  "msbuild-sdks": {
    "Uno.Sdk": "5.4.8"
  },

  <ItemGroup>
    <PackageVersion Include="SkiaSharp" Version="2.88.9-preview.1.1" />
    <PackageVersion Include="SkiaSharp.Views.Uno.WinUI" Version="2.88.9-preview.1.1" />
  </ItemGroup>

Seems to works fine with Uno.Sdk 5.5.0-dev.90 too 😄
So there's less variations on the surface types being used.

@spouliot I tried with both Uno.SDK and both of them have the bug still.
Here is a video of the proof via my OneDrive link: https://1drv.ms/v/s!Aj7hlcEeURZfncBiaWnCikl2CYE7Tw?e=Hc3RmG

@ArchieCoder with the Skia* 2.88.9-preview.1.1 ?

@ArchieCoder Make sure your *.csproj has <PackageReference> to the Skia* assemblies. Having the Directory.Packages.props file with the updated version is not enough to include that specific version inside the app.

For reasons I modified Uno.Samples/UI/ScottPlot/QuickstartSample/ScottPlotSample to match your original test case.
It works fine with the following changes (and I tested it multiple times to convince myself 😄). However if you don't apply the change to the .csproj file an older version of Skia will be included.
diff --git a/UI/ScottPlot/QuickstartSample/Directory.Packages.props b/UI/ScottPlot/QuickstartSample/Directory.Packages.props
index a6c64339..ba5de551 100644
--- a/UI/ScottPlot/QuickstartSample/Directory.Packages.props
+++ b/UI/ScottPlot/QuickstartSample/Directory.Packages.props
@@ -7,5 +7,7 @@
   -->
   <ItemGroup>
     <PackageVersion Include="ScottPlot.WinUI" Version="5.0.39" />
+    <PackageVersion Include="SkiaSharp" Version="2.88.9-preview.1.1" />
+    <PackageVersion Include="SkiaSharp.Views.Uno.WinUI" Version="2.88.9-preview.1.1" />
   </ItemGroup>
-</Project>
+</Project>
\ No newline at end of file
diff --git a/UI/ScottPlot/QuickstartSample/ScottPlotSample/MainPage.xaml.cs b/UI/ScottPlot/QuickstartSample/ScottPlotSample/MainPage.xaml.cs
index c3140fe6..93027621 100644
--- a/UI/ScottPlot/QuickstartSample/ScottPlotSample/MainPage.xaml.cs
+++ b/UI/ScottPlot/QuickstartSample/ScottPlotSample/MainPage.xaml.cs
@@ -7,8 +7,38 @@ public sealed partial class MainPage : Page
     public MainPage()
     {
         this.InitializeComponent();
-        WinUIPlot1.Plot.Add.Signal(Generate.Sin(51));
-        WinUIPlot1.Plot.Add.Signal(Generate.Cos(51));
+        var array = new double[]{1, 2, 3};
+        var sig1 = WinUIPlot1.Plot.Add.Signal(array);
+        //sig1.Axes.XAxis = WinUIPlot1.Plot.Axes.Bottom; // standard X axis
+        sig1.Axes.YAxis = WinUIPlot1.Plot.Axes.Left; // standard Y axis
+        sig1.Color = Colors.Red;
+        WinUIPlot1.Plot.Axes.Left.Label.Text = "Amperage";
+        WinUIPlot1.Plot.Axes.Left.Label.ForeColor = Color.FromHex("#FF0000"); //new Color(255,0,0); //Colors.Red;
+
+        WinUIPlot1.Plot.Axes.Bottom.TickLabelStyle.IsVisible = false;
+        WinUIPlot1.Plot.Axes.Bottom.MajorTickStyle.Length = 0;
+        WinUIPlot1.Plot.Axes.Bottom.MinorTickStyle.Length = 0;
+
+        // create a second axis and add it to the plot
+        var yAxis2 = WinUIPlot1.Plot.Axes.AddLeftAxis();
+        // add a new plottable and tell it to use the custom Y axis
+        var sig2 = WinUIPlot1.Plot.Add.Signal(array);
+        //sig2.Axes.XAxis = WinUIPlot1.Plot.Axes.Bottom; // standard X axis
+        sig2.Axes.YAxis = yAxis2; // custom Y axis
+        sig2.Color = Colors.DarkOrange;
+        yAxis2.LabelText = "Voltage";
+        yAxis2.LabelFontColor = Colors.DarkOrange;
+
+
+        // create a second axis and add it to the plot
+        var yAxis3 = WinUIPlot1.Plot.Axes.AddLeftAxis();
+        // add a new plottable and tell it to use the custom Y axis
+        var sig3 = WinUIPlot1.Plot.Add.Signal(array);
+        //sig2.Axes.XAxis = WinUIPlot1.Plot.Axes.Bottom; // standard X axis
+        sig3.Axes.YAxis = yAxis3; // custom Y axis
+        sig3.Color = Colors.Green;
+        yAxis3.LabelText = "Power";
+        yAxis3.LabelFontColor = Colors.Green;
         WinUIPlot1.Refresh();
     }
 }
diff --git a/UI/ScottPlot/QuickstartSample/ScottPlotSample/ScottPlotSample.csproj b/UI/ScottPlot/QuickstartSample/ScottPlotSample/ScottPlotSample.csproj
index 413f5adf..edd8104a 100644
--- a/UI/ScottPlot/QuickstartSample/ScottPlotSample/ScottPlotSample.csproj
+++ b/UI/ScottPlot/QuickstartSample/ScottPlotSample/ScottPlotSample.csproj
@@ -42,6 +42,8 @@

   <ItemGroup>
     <PackageReference Include="ScottPlot.WinUI" />
+    <PackageReference Include="SkiaSharp" />
+    <PackageReference Include="SkiaSharp.Views.Uno.WinUI" />
   </ItemGroup>

 </Project>

@spouliot thanks! I was missing this in csproj. Appreciate your fix :)


bug: security policy check does not find /SECURITY.md in KubeStellar repo

Per the security policy section in clomonitor, our repo has "SECURITY.md" in the root of the main branch of our repo kubestellar/kubestellar. However, clomonitor flags the file as missing.
SECURITY POLICY:
ID: security_policy
Clearly documented security processes explaining how to report security issues to the project.
This check passes if:
A security policy file is found in the repository. Globs used:
"security*"
".github/security*"
"docs/security*"
CASE SENSITIVE: false
A security policy reference is found in the repository’s README file. This can be in the form of a title header or a link. Regexps used:
"(?im)^#+.security.$"
"(?im)^security$"
"(?i)[.security.](.*)"
A security policy file is found in Github (in the .github default community health files repository, for example).

Hi @clubanderson 👋
From: https://clomonitor.io/projects/cncf/kubestellar#kubestellar_security
That check seems to be passing and the link points to the SECURITY.md file in the KubeStellar repo.

Thank you - I will close


Bug in MIT App Inventor Documentation

Describe the bug
There is a bug in the MIT App Inventor documentation of some blocks are old and are not updated. For example, in the Math drawer, there is currently a 'square root' block, however, in the documentation, it is 'sqrt'. Advanced users can understand, but it might confuse new users.
Affects

[ ] Documentation

Expected behavior
I expected the documentatin to match the block names. I think the documentation took screenshots of blocks of more than 2 years ago. Can the MIT App Inventor team fix this?
Steps to reproduce
Probably go to the documentation to create new screenshots. The problem is simple.

I want to work on this please assign me this task

@GordonL0049 I have fixed 2 small documenation bugs can you please check the pull request
https://github.com/mit-cml/appinventor-sources/pull/2632

I have solved this issues @GordonL0049 can you please approve this PR https://github.com/mit-cml/appinventor-sources/pull/2633


Show number of suggestions

Problem
I was previously using the codeium.vm plugin and there is a way to show the number of suggestions in the lualine plugin. I was wondering if this also available in this plugin? Thanks.
Expected behavior
If possible, is there a way to see the number of suggestions in a status line? Thanks.

They are shown at number column.

I see them now. Don't know how I missed that. Thanks.