How to make hand devices function properly on official examples

I've been experimenting with using the lovr.headset button pressed methods, hand device inputs, as well as the pointer examples, such as this. In all cases, I get some input for the first, say 0.5-1 seconds, and then all readings stall at (0,0,0) and the device inputs are no longer reported through the relevant functions anymore. Is this behavior known/is there some workaround to this?
Relevant info:
Tested on Quest 2 and 3
Nightly and release build both tried

That's interesting, I haven't heard of this happening before and I'm not sure what the cause would be.  Does head tracking still work (i.e. lovr.headset.getPosition('head')) after the input is lost?  Does lovr.headset.vibrate vibrate the controllers?  Finally, are there any relevant log messages if you do adb logcat -s LOVR?

For posterity, here is a relevant message from logcat:
--------- beginning of main
06-10 03:35:21.469 13584 13584 D LOVR    : Using Generic OpenXR Loader
06-10 03:35:21.799 13584 13664 D LOVR    : REFLECT [RUNTIMEIPC] WARN@ arvr/first-party/sdks/internal/RuntimeIPCApi/Include/RuntimeReflectIPC.h(4130): InitClientInternal: Already initializedREFLECT [RUNTIMEIPC] WARN@ arvr/first-party/sdks/internal/RuntimeIPCApi/Include/RuntimeReflectIPC.h(4130): InitClientInternal: Already initializedREFLECT [RUNTIMEIPC] WARN@ arvr/first-party/sdks/internal/RuntimeIPCApi/Include/RuntimeReflectIPC.h(4130): InitClientInternal: Already initializedREFLECT [RUNTIMEIPC] WARN@ arvr/first-party/sdks/internal/RuntimeIPCApi/Include/RuntimeReflectIPC.h(4130): InitClientInternal: Already initializedREFLECT [RUNTIMEIPC] WARN@ arvr/first-party/sdks/internal/RuntimeIPCApi/Include/RuntimeReflectIPC.h(4130): InitClientInternal: Already initializedREFLECT [RUNTIMEIPC] WARN@ arvr/first-party/sdks/internal/RuntimeIPCApi/Include/RuntimeReflectIPC.h(4130): InitClientInternal: Already initializedFailed to suggest input bindings for /interaction_profiles/khr/simple_controller
06-10 03:35:21.799 13584 13664 D LOVR    : Failed to suggest input bindings for /interaction_profiles/oculus/touch_controller

I'm not sure what these logs mean or what part of lovr is even printing them... I also can't reproduce this on v65 and am using controllers and hand tracking successfully.  So for now this is still a mystery!

I got the v66 Quest OS update and also upgraded OpenXR to 1.0.38 for good measure, but I still haven't been able to reproduce this on multiple Quest 2 or Quest 3 devices.  I don't think I have enough information to fix this, sorry 😞

It's happening repeatedly to me on Quest 3. After I disable controllers by bumping them into each other I can see the hands for ~1s and then they disappear.
There are no logs, the head is being tracked and I believe the controllers do not vibrate but I wasn't sure if my code was correct.
After the hands disappear, lovr.headset.isTracked(device) returns false for hands.

Recently I noticed something that might be related -- on Quest, sometimes hands won't be tracked in my project and I have to turn off the headset display and turn it back on again (tap the power button twice).  After that, hand tracking works.  Does this also fix the issue for you?

I've just tried it - first moved my controllers to make the hands disappear, then turned the display off and on - and it did help.

Just tried to reproduce this for a while and wasn't able to trigger it.  This was on a Quest 2 though, I can try a Quest 3 in a couple of days.  I have a few ideas I want to try that might fix it, but I'd like to have the problem happening locally so I can see if the fixes actually work!

Thanks! Again - if I can be of any help just let me know. If you'd like to hop on a call with me, I could cast my headset for you.

I noticed that while controller/hand input isn't working, lovr.headset.isFocused returns false.  Turning the display off/on brings back input focus.  So it likely isn't something to do with actions, hand trackers, etc. and is instead something related to the OpenXR session state.
After printing out all the OpenXR session state events, it seems that LÖVR's OpenXR session never transitions to FOCUSED, only VISIBLE.

I think in my case, when I start the app using adb shell am start org.lovr.app/org.lovr.app.Activity when the headset is idle, the session never gets input focus, even after putting on the headset.  If I start the app with adb while wearing the headset, or start the app from the Quest UI, I get input focus.  And in all cases, turning the display off/on restores input focus.  So this maybe seems like a separate issue from the one reported here.


search.ipynb: Remove erroneous output and add RBFS visualisation.

The RBFS visualisation currently uses show_map to display the graph iterations, like the other algorithms. show_map is limited to setting node colors, so we cannot use it (in its current form) to add  f-cost labels to nodes. If it seems reasonable to you to extend the functinality of show_map, let me know, and I'll be happy to do it.

The right way to do it is that def recursive_best_first_search should not mention anything at all about colors or display. It should just be the algorithm. All the code for display should go into a wrapper around problems. Then you call something like recursive_best_first_search(DisplayProblem(problem)).

Sorry, it was my fault for delaying in a review, but now there are conflicts. I think we can incrementally do the changes as you suggest. If it is not enough to wrap the problem, we can also make use of utils.injection, something like this:
 def DisplayPriorityQueue(...):
     "A PriorityQueue, but handles display of nodes."
     ...

 with injection(PriorityQueue=DisplayPriorityQueue):
     ... search(...) ...


total time not equals to inference + queue+ tokenizer time

System Info

Information

[X] Docker
[ ] The CLI directly

Tasks

[X] An officially supported command
[ ] My own modifications

Reproduction
send some request
Expected behavior
total time equals to inference + queue+ tokenizer time

Not if you send your requests in a batch.


fix: automatically set stream parameter based on the used method

Status
READY
Description
Set the stream parameter based on the used method.
Impacted Areas in Library
Model
Which issue(s) does this pull-request fix?
Closes: #162

Checklist

[ ] Automated tests exist
[ ] Updated Package Requirements (if required, and with maintainers' approval)
[ ] Local unit tests performed
[ ] Documentation exists link
[ ] Local pre-commit hooks performed
[ ] Desired commit message set as PR title and description set above
[ ] Link to relevant GitHub issue provided

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

16 of 16 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 96.848%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
2151

Relevant Lines:
2221

💛  - Coveralls


FE: Wizard: Fix sections collapsing

[ ] Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)
I update the configure cluster sections to open and close properly. Prior to this change they would open, but not close consistently. I added a configOpen variable to manage this. Rather than passing undefined when the form is closed it now sets it to an {isActive: false}. Then the data is reset in transformFormDataToPayload based on that actual flag rather than null checking.
Is there anything you'd like reviewers to focus on?
How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

[ ] No need to
[x] Manually (please, describe, if necessary)
[x] Unit checks
[x] Integration checks
[ ] Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
[x] My changes generate no new warnings (e.g. Sonar is happy)
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged

Check out Contributing and Code of Conduct

Thanks for approving @Haarolean ! This is an issue with the workflow I am thinking not code changes, right?

@masonwoodford thanks for your first contribution to kafbat ui!
It's related to the workflow running in a forked repo, ideally it shouldn't be running at all, there's an issue with the workflow I don't have time to take a look at.


增加Uniswap-V2白皮书中文版

抱歉，你能解释一下为什么不使用链接而不是文件吗？是私人版吗？

Because the link only points to a resource address, the resource is easily changed. Especially if the reference link to the public repository changes and the corresponding maintenance personnel have left, the file may be permanently lost and can no longer be found. If the community still wants to use links instead of files, I can also use links to introduce static resources.

Sorry, could you explain why not using links instead of files? Is it a private version?

Reply: Because the link only points to a resource address, the resource is easily changed. Especially if the reference link to the public repository changes and the corresponding maintenance personnel have left, the file may be permanently lost and can no longer be found. If the community still wants to use links instead of files, I can also use links to introduce static resources.

Sorry, could you explain why not using links instead of files? Is it a private version?

Reply: Because the link only points to a resource address, the resource is easily changed. Especially if the reference link to the public repository changes and the corresponding maintenance personnel have left, the file may be permanently lost and can no longer be found. If the community still wants to use links instead of files, I can also use links to introduce static resources.

I see，We just do not want to make the project so large.   We will approve the pr. Thanks your contrubution again.


Cannot open Choose File dialog

Expected Behavior
When press button "Choose File" dialog should show up
Actual Behavior
When press button "Choose File"  nothing happens.
In journalctrl:
rest.insomnia.Insomnia.desktop[9283]: (insomnia:2): Gtk-WARNING **: 10:57:12.837: Can't open portal file chooser: GDBus.Error:org.freedesktop.portal.Error.InvalidArgument: invalid filter: name is empty
Reproduction Steps

Go to Request Page
Change method to POST
Change type to "Multipart"
Add new line
Change to file
Press  "Choose File"

Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
Version: Insomnia 2023.5.8
Build date: 9/7/2023
OS: Linux x64 6.5.9-arch2-1
Electron: 25.2.0
Node: 18.15.0
Node ABI: 116
V8: <IP_ADDRESS>-electron.0
Architecture: x64
Insomnia Version
2023.5.8
What operating system are you using?
Other Linux
Operating System Version
ArchLinux
Installation method
Flatpak
Last Known Working Insomnia version
No response

I have the same problem, but I think flatpak is not a supported version

I have this issue, too. I am using Fedora Linux 39 (Workstation Edition).
Is there something new?
Additional information:
Version: Insomnia 2023.5.8
Build date: 9/7/2023
OS: Linux x64 6.7.9-200.fc39.x86_64
Electron: 25.2.0
Node: 18.15.0
Node ABI: 116
V8: <IP_ADDRESS>-electron.0
Architecture: x64

I manually installed 8.6.1 from the website, and the error no longer exists. Maybe you could change the version in Flatpak
Version: Insomnia 8.6.1
Build date: 2/5/2024
OS: Linux x64 6.7.9-200.fc39.x86_64
Electron: 28.0.0
Node: 18.18.2
Node ABI: 119
V8: 12.0.267.8-electron.0
Architecture: x64


Setting ssl ciphers config does not work

Description
If you uncomment ciphers or tls_versions for example in local.ini, starting couchdb fails. This could be something on my end, but I've been toying with this for a couple days with no luck. We have ssl working just fine, but are trying to restrict the ciphers to be used now.
Steps to Reproduce
Uncomment the default ciphers config in local.ini. The http server will fail to start when starting couchdb. If you tweak from the default at all, you'll likely get an error that mochi had an issue parsing
Expected Behaviour
Your Environment

CouchDB version used: 3.1.1
Browser name and version:
Operating system and version: CentOs7

tried several different erlang versions 20, 21, and 22 major versions
Additional Context

Is there a plan to fix this issue in a comping release?

Hi is there anyway for someone to check on this to at least verify it is truly a bug, whether or not that actually involves fixing it at the same time? We would like verification before we put more effort in trying to attempt to get this to work.


[Bug Fix] Incorrect calculation for container right overlap

This probably warrants adding some test cases for the hit detection.

"This probably warrants adding some test cases for the hit detection."  Indeed it does.  @tjhiggins do you want to tackle those tests?  I think this would be a good set of unit tests.
Alternatively, @Owlbertz this might be a good area to focus on some of your unit testing work, as the box utility impacts a ton of things.


Check if the drawer is open before responding to escape keystrokes.

Fixed base branch for original PR #4159.

Since we have 2 LGTM's from the original PR and this is simply a rebase, merging in now.
Thanks for spotting this and fixing it.


Resume previous chat context after restarting aider in the same repo

Is there anyway to resume a previous context? I see .aider.chat.history.md & .aider.input.history but I don't see any signs that this is being used in any way.
I'm experimenting using aider for pretty complex app and I have done a good amount of prompting to get the process going and then I entered a typo when adding a file that caused aider to crash. I open aider back up and it has no clue what I was doing and why. Nothing more than what it can gather from existing code

As a work around you could read through your chat history file and save snippets you want to reuse into ai specific documentation folder. Then you can just add and drop those snippets as you like and it should help you recreate chat context reasonably well.

file and save snippets you want to reuse into ai specific documentation folder.

I really liked this idea, I was always thinking about something like README.md but for aider to give it a more context about the project it is working in.
Never thought to do that manually through a file then just simply /add it to the conversation, Perhaps I have a tendency to over-engineer things. 😨
Still, it could serve as a good starting point for establishing best practices.
Thanks @joshuavial for the insight!

Aider saves all the messages you type and makes them available in the input history. These persist across sessions.
You can use the up arrow to scroll back through history. Or control-r to search.
By default the input history is stored in a file local to the git repo. You can use a command line option or config setting to store it in your home directory, if you want history to be shared across all projects.

I'm going to close this, and continue further discussion in #166 since there's already a bit more detail in that discussion.


Postal.local uesage

Hi, may I ask what Postal.local (in update_process_concurrency.rb)is used for?
File.open(Postal.app_root.join('Procfile.local'), 'w') { |f| f.write(hash + "\n")}

I can also start the postal with rails s, so it's quite confusing.

I probably should take look at procodile ;)

You should use the documented processes to start Postal using postal start or systemd.
If you want to run individual parts of Postal separately on different servers (or in kubernetes), the processes listed in Procfile are a good place to start.

Any drawbacks for not using Procfile?
I used to use puma.

Only that you would have to manage starting each of the processes yourself, depending on which parts of Postal you wanted to use.
The processes don't overlap that much but they almost all require access to the database and queue servers I believe.


New upload UI not compatible with night mode

From a user on our forum:
The text in the category selection dialog is very low contrast in dark/night mode; see attached screenshot for an example.

@Ojonathan great, let us know how you get on. :)


Allow Rasters as inputs for Coreg.fit() and Coreg.apply()

Solves #174.
See the issue for the new syntax!

Actually, a big question raised by this:
With https://github.com/GlacioHack/GeoUtils/pull/210 and this PR, we now have many use cases where we can use np.ndarray and Raster objects interchangeably. But there is still several functions for which it does not work, right? Such as terrain attributes.
Should we aim to have xdem working with np.ndarrays and Raster objects interchangeably? If yes, what is left to do? (I think that, @erikmannerfelt, you have the best viewpoint on all this!)
Also, it should be crystal clear when a Raster can be provided simply as a convenience and a np.ndarray would suffice, or when georeferenced data is absolutely necessary. It will get blurry for the users if we allow to provide both everywhere for convenience, so I'm not sure how to tackle this!

Actually, a big question raised by this:
With GlacioHack/GeoUtils#210 and this PR, we now have many use cases where we can use np.ndarray and Raster objects interchangeably. But there is still several functions for which it does not work, right? Such as terrain attributes.
Should we aim to have xdem working with np.ndarrays and Raster objects interchangeably? If yes, what is left to do? (I think that, @erikmannerfelt, you have the best viewpoint on all this!)
Also, it should be crystal clear when a Raster can be provided simply as a convenience and a np.ndarray would suffice, or when georeferenced data is absolutely necessary. It will get blurry for the users if we allow to provide both everywhere for convenience, so I'm not sure how to tackle this!

Since, geoutils==0.0.3, Rasters implement the array interface, so they should be possible to use interchangeably with ndarrays. The tests don't cover that "should" part, however, and Rasters are not consistently returned if provided as an argument. For now, all functions that show a Raster/RasterType argument/return type hint returns a RasterType if given a RasterType, and those who don't will return an ndarray/masked_array.
Long story short, the only way to validate how interchangeable they are is to include more tests!!

I think I've fixed all of @rhugonnet 's comments.
Any other thoughts, @rhugonnet  and @adehecq ?

Already done in #178 !
Thanks, @rhugonnet !

Fantastic !


Remove the switch to Approver/Requestor UI

User Story
remove the "switch roles" button in the UI

T-shirt size: S(mall), M(edium), L(arge)
SMALL!

User Story
In the interest of not demoing vaporware, we should remove the UI switch between requestor and approver.  Instead, we will create role owner accounts that can be used to approve requests.

Description
A short description

Acceptance Criteria/Tests
This UI no longer shows.

move to toolbar or menu


Active tab highlighting does not work with Edge Chromium.

Hi.
As you know, any Chrome extension and theme can be installed on the Edge browser, which shares the same open source engine as Chrome, thanks to Chromium. I don't use Chrome, I use Edge because it consumes less resources than Chrome but I can use its extensions and themes.
So I have installed the Dracula theme in Edge, but when I hover the cursor over any tab the colored line does not appear in the tab header as shown in the gif in your repository, and it does not show in the active tab either. I have reinstalled the theme but it is still the same. So, can you do something about it so that the active tab highlighting feature also works with the Edge browser?
That's all.

Hi
The highlight is a new feature that was approved this morning.
I build the new package only a few hours ago and it's under review.
The review time depends on google, so i'll suggest to try again later.
The new version is 2.1
Thanks

The review time depends on google, so i'll suggest to try again later.
The new version is 2.1

Ok, I will try it later even though the 2.1 update is already shown in the store but I still don't get the feature I mentioned to you.

Well, as I said before I will try again later. If I don't succeed I will write you again, thank you.

Hi.
Several hours later, the new update does appear as in your image. Thank you very much, it looks great. 👍

Great!
Glad it arrived and glad you like my theme!

Great!
Glad it arrived and glad you like my theme!

Yes, I like it very much. I hope you can do the same with the vertical tabs. Thank you for your theme. 👍


Provide data process script

Could you please provide the data process script since I found that  ConfGF's code does not get the features like num_graphs, atom_type, pos, bond_index , etc.?

Hi Lei,
Thanks for your interest!
Are you sure any feature is missed during running the code? The data is processed by PyG:
https://github.com/DeepGraphLearning/ConfGF/blob/38aeb6c7719343d13fa867f4b17b02ed45d09bd0/confgf/dataset/dataset.py#L264
And as you can see from the function, all the features are handled:
https://github.com/DeepGraphLearning/ConfGF/blob/38aeb6c7719343d13fa867f4b17b02ed45d09bd0/confgf/dataset/dataset.py#L28-L76
So do you have any problems when running the code?

Thank you very much for your reply.
Is num_hs the same as num_graphs? Besides, how to get num_nodes_per_graph and batch features?
Thank you again!

Hi,
num_hs seems should be the number of Hydrogen atoms. The other mentioned features are the features of graphs. Many of them are automatically constructed from the PyTorch_Geometric library (https://pytorch-geometric.readthedocs.io/en/latest/notes/introduction.html#data-handling-of-graphs). Please take a look at their document. Thanks!

Thank you very much for your kind reply!


Add option to customize keycloak themes

Reference Issues or PRs
closes #1980

What does this implement/fix?
Put a x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features not to work as expected)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):

Testing

[ ] Did you test the pull request locally?
[ ] Did you add new tests?

Any other comments?

This issue has been on my plate since Qhub and we've wanted to address it for a while, but I only recently migrated it to the current source code.

How to test this PR:

Create a public github repo, containing a folder with the name to your theme (e.g demo);
Inside such folder copy over the contents from https://github.com/keycloak/keycloak/tree/main/themes/src/main/resources-community/theme/base or use my-cool-theme-name example from https://github.com/keycloak/keycloak-quickstarts/tree/latest/extension/extend-admin-console.
In your nebari-config.yaml, make sure to properly pass the URL for you github repo under the repository and branch fields, introduced in this PR
After deploying, go to the Keycloak UI and select your new theme

@viniciusdc is this ready for review? If yes, let me know and I'll test so we can merge it!

Hi @marcelovilla yes this is ready for review, I still need to open a doc PR for this, but in the meantime if you can test, that would be nice

@viniciusdc sorry that I haven't gotten around to test this PR but I'll do that between today and tomorrow


Add getQueryParam utility method to support pagination

This PR adds a small utility method to extract the value of a query parameter from a URL string. This will be used in the pagination support for Node.
Checklist

[x] npm test passes (tip: npm run lint-fix can correct most style issues)
[x] tests are included
[ ] documentation is changed or added

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Issue in all POPUP

Please check below Screenshot image.
There is a problem in every popup. When i try to install any extension or theme or change the setting the popup with White Color is occur. i can't see Text and Buttons when its come.

@sahilr2050 Can you please share the console logs when you encounter this issue.
Also, the issue looks to be because of some faulty extension. If you don't have too many extensions installed, can you try disabling extensions (in the installed tab) one by one to find the faulty one.
Let us know if this solves your issue.

Actually i am using ubuntu 15.04  and i don't know about bracket console. i disable all extensions and restart brackets but the new problem is IT'S HANG EVERY TIME.
One More Thing is when I DIRECTLY OPEN FILES FROM "FIREFTP" Or "FILEZILLA"  Brackets is open but there is PAST FILE WHICH IS OPEN FROM LOCAL FOLDER. Files are always show from SELECTED FOLDERS This is not Good IDEA.


Runelite parchment plugin

Hi, not sure if this is done correctly... but the runelite parchment plugin doesnt have a few items registered or all items that can be parched arent registered... i was pking with ice ancient sceptre but not parched and didnt flash for me...

Hey, ice sceptre should be in the list, but I don't have one to test it out. Would you mind taking a screenshot of it in your inventory with 4 other more expensive items. Please include your settings tab for the add-on as well.


feat: 🎸 update SQ v19 support for the latest changes

Description
instruction and authorization IDs are no longer padded. Queries are updated accordingly
Breaking Changes

JIRA Link
DA-1442
Checklist

[ ] Updated the Readme.md (if required) ?

/fast-forward

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

npm package (@release-v26 dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add pixi runx package@version

Problem description
It would be nice to have the ability to do something like npx, pnpx or https://github.com/pkgxdev/pkgx; i.e., run any conda package without installing it globally (and without installing it in your pixi project environment(s)).
Pixi should create a temporary environment and run the command in this environment.
How about the following syntax?
$ pixi runx conda-smithy
<downloads conda-smithy@latest and runs `conda-smithy`>
$ pixi runx<EMAIL_ADDRESS>-- build
<downloads<EMAIL_ADDRESS>and runs `rattler-build build`>
$ pixi runx rattler-build --command "rattler-build2 build"
<downloads rattler-build and runs `rattler-build2 build` (needed for packages where the executable differs from the package name)>

I don't think we should support multiple requirements, I cannot think of a specific use case where you would need to specify multiple requirements at once to run a one-off command.

Pretty good idea!

pixi runx conda-forge/conda-smithy or pixi runx https://github.com/conda-forge/conda-smithy as well no?

The first one yes 👍🏻
The second one no since pixi has no idea what https://github.com/conda-forge/conda-smithy is and the repo also doesn't tell pixi where the corresponding conda package lies / how to build itself.

It could work if a build logic is set in the pixi manifest (not available yet but on the roadmap I believe) no?

Ah yes but I think this is still a somewhat long way to go for now :)

Yes, we first put our focus on making rattler-build`

$ pixi runx rattler-build --command "rattler-build2 build"

Interestingly, npx choose to take the main argument as the executable name. If they don't match (or the package provides several binaries to choose from), then the user can specify --package exe-provider instead.
So it would look like (with --spec instead of npx's --package):
$ pixi runx --spec=rattler-build rattler-build2 build

, which imo feels more natural than retrofitting args and commands, if that makes sense. It would also allow to specify several packages, in case there are e.g. optional dependencies that improve performance:
$ pixi runx --specs=some-project --spec=gpu-plugin some-project --with-gpu

Or maybe with --specs instead:
$ pixi runx --specs="some-project gpu-plugin" some-project --with-gpu

Or with a mix, having --spec and --extra-specs (so spec is the only one providing binaries, while extra-specs just fill in dependencies but don't contribute their binaries to PATH):
$ pixi runx --spec=some-project --extra-specs=gpu-plugin some-project --with-gpu

I also like this approach.
I'm in favor of not having extra-specs, though, that sounds oddly specific and I cannot think of a real world example that makes sense and would need this 👀


forgejo: 9.0.1 -> 9.0.2, forgejo-lts: 7.0.10 -> 7.0.11

7.0.11 Release Notes: https://codeberg.org/forgejo/forgejo/milestone/8609
9.0.2 Release Notes: https://codeberg.org/forgejo/forgejo/milestone/8610
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

vm tests pass on x86_64-linux
nix-build -A forgejo.passthru.tests -A forgejo-lts.passthru.tests
/nix/store/xh0pwbllvpmyw1mvhkrv6n7y76ypj3hd-vm-test-run-forgejo-mysql
/nix/store/ha34mixrwpd0k3mzzmmylhzrw7mwczgg-vm-test-run-forgejo-postgres
/nix/store/zjn3s1khg4109hv727pvqyqzwqipyi7p-vm-test-run-forgejo-sqlite3
/nix/store/i47kc54zr7s7ia6h6m5mw1ii1qqvyrbs-vm-test-run-forgejo-mysql
/nix/store/q1p6zyps93wz232msr32q7kfxgqd595s-vm-test-run-forgejo-postgres
/nix/store/3sk0id21y6h9cvy3dxsva88hknbpprc9-vm-test-run-forgejo-sqlite3

@NyCodeGHG are you also able to PR v7 to 24.05?


Remove false claim from plugins user manual chapter

This is simply not true in practice and confuses readers.

Your PR is queued. See the queue page for details.

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


Style place picker modal

Web
Before:

After:

iOS
Before:

After:

Btw why there is Austria when I search for os?

Could anyone try it on Android? My Android simulator is not fetching data right now

nice 🥇

Could anyone try it on Android? My Android simulator is not fetching data right now

@jvaclavik  did you try this? adb reverse tcp:4000 tcp:400


refactor(DiamondCutFacet.sol): use diamondCut from library

Motivation
Since this repo, just like the diamond-1-hardhat and diamond-3-hardhat are for reference implementations, was thinking reusing the diamondCut from the LibDiamond in the DiamondCutFacet.sol would be helpful for new readers to understand how the cut logic differs from the other implementations (instead of duplicating the same pre logic for addReplaceRemoveFacetSelectors).
I totally understand that diamond-2-hardhat should be the most efficient in terms of diamond cutting. Even so, using the library instead uses more gas (not that significant) 😅. Is this worth doing this to help demonstrate how the cutting logic works?

DiamondCutFacet from implementation 1
DiamondCutFacet from implementation 2 (current)
DiamondCutFacet from implementation 3

Gas report for the current repo test
Current:

diamondCut method:  avg gas for 22 calls 348444
DiamondCutFacet deployment method:  avg gas for 22 calls 1952190

Proposed:

diamondCut method:  avg gas for 22 calls 349019
DiamondCutFacet deployment method:  avg gas for 22 calls 1974592

You are right, it really isn't much more gas.  Will consider it.


New font - Argenmtum-Sans

New font from #504

Sorry for the delay. Looks good, thank you!

hey cant find this font on the website tho, is there some delay?

Within this week it should be published. All auto builds and publishes are broken rn.

cool!


Doesn't work properly when protractor is running with "shardTestFiles: true" config

Until now, we thought that the problem of "protractor-html-screenshot-reporter" when the protractor is running on sharding mode is related to the fact that the results folder was constantly deleted for each spec. Although, with this new version (0.0.19), we now have a way to preserve the results folder for each spec thanks to the option: "preserveDirectory: true".
Now we can see that the result (json and png) of every spec-result is inside the results folder. Although, the "combined.json" file does not contain every spec-result that is inside the results folder. What is the problem now?
My suggestion is:
How can we wait until every spec finishes? And than we can use something like "grunt-merge-data" to merge all the JSONs and only after that generate the HTML reporter.
Any thoughts?

:+1: Really want to have parallel tests in CI but not having screenshots makes debugging issues impossible.

Also waiting on this.

+1

+1

+1

+1

+1

+1

+1

Any solutions to this ?

+1


Regex for Random.id()

Hello Eric, where'd you find the info for this regex?

This can be closed, the source for the regex is stated in the comment above the linked to line.
character list: https://github.com/meteor/meteor/blob/release/0.8.0/packages/random/random.js#L88
string length: https://github.com/meteor/meteor/blob/release/0.8.0/packages/random/random.js#L143


Home Connect Alt installation problem

I'm sure this is me being dumb but I am following the instructions carefully to install Home Connect Alt for my new Bosch dishwasher and when I click to open it on HACS it just brings down the same readme page as I'm already on. I never see any popups to configure it (installation Step 2).
I am doing restarts at the correct time and also removing the credentials in between attempts.
Clicking Download also creates an entry in my HACS which also just open the readme.
I've carried out the pre-installation steps numerous times. The dishwasher is on and running a program.
(I tried first with the official Home Connect which worked but it found no devices,)

Ignore me, silly mistake


ISSUE: publishing views does not create view files (Laraval 6)

Running
php artisan vendor:publish --provider="JeroenNoten\LaravelAdminLte\ServiceProvider" --tag=views
does not create anything in resource/views/vendor as per docs.
Laravel Framework 6.4.0
"name": "jeroennoten/laravel-adminlte",
"version": "v2.0.2",

for me this returns the following in red: Unable to locate publishable resources

It should be php artisan vendor:publish --provider="JeroenNoten\LaravelAdminLte\AdminLteServiceProvider" --tag=views

Looks like this was affected by this recent commit:
https://github.com/jeroennoten/Laravel-AdminLTE/pull/400

Please change readme.MD Now here php artisan vendor:publish --provider="JeroenNoten\LaravelAdminLte\ServiceProvider" --tag=assets --force

The readme.md is correct, look at here (master) or here (laravel6-adminlte2) with the new adminlte:install command.

Why use publish assets in installation for v5 and dont for v6))
Need add publish assets for v6 in installation  or delete for v5?!
2. Installation
2.1 - Laravel 5 (Package version 1.x)
Require the package using composer:

composer require jeroennoten/laravel-adminlte "^1"
Publish the public assets:

php artisan vendor:publish --provider="JeroenNoten\LaravelAdminLte\ServiceProvider" --tag=assets
The make:adminlte artisan command

This package ships with a make:adminlte command that behaves exactly like make:auth (introduced in Laravel 5.2) but replaces the authentication views with AdminLTE style views.

php artisan make:adminlte
This command should be used on fresh applications, just like the make:auth command

2.2 - Laravel 6.x (Package version 2.x)
Require the package using composer:

composer require jeroennoten/laravel-adminlte
Install the package using the command (For fresh laravel installations):

php artisan adminlte:install
You can use --basic to avoid authentication scaffolding installation

You can use --force to overwrite any file

You can also use --interactive to be guided through the process and choose what you want to install

I need use php artisan vendor:publish --provider="JeroenNoten\LaravelAdminLte\AdminLteServiceProvider" --tag=assets --for for publish assets for v6 when installations

In which case do you want publishing the assets?

for me this returns the following in red: Unable to locate publishable resources.
The translations do publish though, so it is not an overall publishing problem.

I am also facing the same issue, did you find the solution?

Same here, I use Laravel 6.4.1,
when I execute the command it returns
Unable to locate publishable resources. then on the next line Publishing complete.,
that's weird, I need to change some of them

If you're using AdminLTE 3 with Laravel 6 you can use:
php artisan adminlte:install --only=main_views

In which case do you want publishing the assets?

Estou com o mesmo problema, não esta publicando nada.
A versão anterior está funcionado corretamente.

is working fine on Laravel 6.4.
create an extended view file in
resource\view
and master file create in
vendor\jeroennoten\laravel-adminlte\resources\views
plz, check that path.


Character Limits on User Input

https://trello.com/c/xyqOZzDv
Context
We want to apply a 255 character limit to strings in the database that are from user input. The Postgres varchar type allows strings of up to 65,535 bytes. So a user is able to submit a first name and a last name for example, that are over 10,000 characters long, and we want to avoid that.
Changes proposed in this pull request
I've added the change at the application level, by adding a before_validation to ApplicationRecord, which checks if the column is a string, and if its value is greater than 255 characters. This seemed a bit heavy-handed, but the alternative was to try to identify columns individually, and set the limit against each one. That leaves a lot of room for columns to be missed, or for new columns to be added later and for the rule to be ignored.
Guidance to review
I'm open to alternative approaches, this seemed the most sensible to me.
Important business

[x] Does this PR introduce any PII fields that need to be overwritten or deleted in db/scripts/sanitise.sql?
[x] Does this PR change the database schema? If so, have you updated the config/analytics.yml file and considered whether you need to send 'import_entity' events?
[x] Do we need to send any updates to DQT as part of the work in this PR?
[x] Does this PR need an ADR?

NB: Please notify the #twd_data_insights team and ask for a review if new fields are being added to analytics.yml

Would you mind linking to the Trello ticket in the description?

Note that if you add a deploy_v2 label, it will trigger a workflow to spin up an environment in Azure so people can see how this works in the wild.

overall i feel like this is a somewhat nuclear option. would be more comfortable with setting length validations in form objects (example). interested to know what other devs think though.

overall i feel like this is a somewhat nuclear option. would be more comfortable with setting length validations in form objects (example). interested to know what other devs think though.

@carlosmartinez I did think about that, or adding a length validation to individual columns in the model. But that seemed like a pattern that's easy to break and forget about as new columns are added. Happy to go that way though if you prefer.

Thanks Adam. What's your thoughts, @DFE-Digital/register-devs ?

overall i feel like this is a somewhat nuclear option. would be more comfortable with setting length validations in form objects (example). interested to know what other devs think though.

@carlosmartinez I did think about that, or adding a length validation to individual columns in the model. But that seemed like a pattern that's easy to break and forget about as new columns are added. Happy to go that way though if you prefer.

Thanks Adam. What's your thoughts, @DFE-Digital/register-devs ?

It doesn't look like there's a one-size-fits-all limit, there's a few set at 500, 100 and 50. So per attribute validations seem like the best approach to me, despite the fact that we've been fairly rubbish about declaring them in the past. Could we get ourselves doing the right thing with a custom Rubocop rule?

@carlosmartinez I've been through the views in the system-admin folder and added a maxlength where I thought it made sense. Let me know if that's ok. How far do you want me to go with making these changes? Shall I go through the whole app?

@carlosmartinez I've been through the views in the system-admin folder and added a maxlength where I thought it made sense. Let me know if that's ok. How far do you want me to go with making these changes? Shall I go through the whole app?

Thanks @AdColvin, looks good. Might be worth adding a scenario or two to the feature tests just to verify this (and to get up to speed on the feature tests!).
Could also take a look through the forms directory to see if there are any obvious cases that could do with maxlength validation.

I've tested a variety of lengths on different pages and all seems fine. From the comments on the Trello ticket the Withdrawal character limit has been set at 500 rather than 1000.
I did notice a typo with a variable not being pulled through to the hint text on the withdrawal page. It reads as follows;
What the Department for Education could have done must be x characters or less
This needs fixing but apart from that all good to go :shipit:


Notification title shows user email instead of user name

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Write a message to someone in NewDot
Unfocus the native NewDot window and wait for them to reply
Note that the pop-up notification show's the user's email address instead of their name

Expected Result:
I would expect to see the user's name if they've added it
Actual Result:
I see the user's email address only
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.19-2
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

https://github.com/Expensify/App/assets/43996225/d6c5e64a-55a2-45fe-929b-521e919ddcd4
Expensify/Expensify Issue URL:
Issue reported by: @greg-schroeder
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1684968338273599
View all open jobs on GitHub

Proposal
Please re-state the problem that we are trying to solve in this issue.
User email displayed in notification even if users display name is available.
What is the root cause of that problem?
While pushing the notification we are picking up the email always.
What changes do you think we should make in order to solve the problem?

Pickup user's Display Name using ReportUtils.getDisplayNameForParticipant()  and assign it to title here
Now line 118 looks like
title = ReportUtils.getDisplayNameForParticipant(plainTextPerson,false);
What alternative solutions did you explore? (Optional)
None

Proposal
Please re-state the problem that we are trying to solve in this issue.
Email is displayed in notification instead of displayName
What is the root cause of that problem?
In https://github.com/Expensify/App/blob/06192acc94f8fa31f95adb76f57bd9f4145bdf11/src/libs/Notification/LocalNotification/BrowserNotifications.js#L107-L108
We're getting the email from reportActions
What changes do you think we should make in order to solve the problem?
We should apply ReportUtils.getDisplayNameForParticipant() for each person
        const plainTextPerson = _.map(person, (f) => ReportUtils.getDisplayNameForParticipant(f.text)).join();

We also should update the push notification for native platform to show the displayName instead of email as well
What alternative solutions did you explore? (Optional)
None

Updated Proposal: After testing @tienifr 's proposal I found another issue in the code. Updating the proposal to address the notification issue with Chat Rooms (group chats)
Proposal
Please re-state the problem that we are trying to solve in this issue.
User email displayed in notification even if users display name is available.
What is the root cause of that problem?
There are two issues here

While pushing the notification we are picking up the email always. (As mentioned originally here
The chatType from API response is always an empty String ""; Hence the notification card for ChatRooms is never display as intended and it falls back to the notification card designed for user chats.

What changes do you think we should make in order to solve the problem?

Update here. To get messages senders name if available with.
const plainTextPerson = _.map(person, (f) => ReportUtils.getDisplayNameForParticipant(f.text)).join();

Ensure the Backend is updated to send proper chatType Value.

What alternative solutions did you explore? (Optional)
None.
###References & Screenshots:

Mocked chatType and tested :

This is also occurring on native Android, so likely other platforms too (iOS / Desktop).

I think this is likely an internal issue.

PR is posted

Waiting on deploy

Deployed to prod! Since this was reported, fixed and reviewed internally, no payment is needed!