release tarballs don't include submodules

Hi,
If I download a release tar.gz (i.e. v1.36.4.tar.gz), and run cmake to build and include the option to build the viewer, it fails with this error:
CMake Error at source/MaterialXView/CMakeLists.txt:2 (message):
  Building the MaterialX viewer requires the NanoGUI submodule to be present.
  Update your repository by calling the following:

  git submodule update --init --recursive

-- Configuring incomplete, errors occurred!

Building from a git clone works great.
Is there a way the submodules could be included with the release tar.gz files?
Thanks,
Zach

Hi Zach,
If there's a straightforward way to include submodules in GitHub releases, I'd support making this change, but I haven't yet encountered a good solution for this.  Here's a related post on the GitHub community forum, which puts this in the category of feature requests for GitHub:
https://github.community/t5/How-to-use-Git-and-GitHub/Create-Release-that-contains-submodule/td-p/12073
All the best,
-Jonathan

Hi Jonathan,
So after some digging around and finding a ton of other people wanting the same feature, you are correct, there is no straightforward way to do it.
So I made a way (which hopefully proves good+easy+standalone) to do it here (including the module's source):
https://github.com/nzanepro/git-archive-submodules
(cd to your repo root, run git-archive-submodules.sh from the repo above, voila!)
I've forked this repo and tested adding the resultant tar.gz here:
https://github.com/nzanepro/MaterialX/releases/tag/v1.36.4-including-submodules
It's simple to add the tar.gz that is output from the git-archive-submodules to the release on the web interface of GitHub. This looks like a great way to automate the upload with the tagged release:
https://github.com/itchio/gothub
This is the piece I needed to get the homebrew formula for MaterialX working, which is now available here:
https://github.com/nzanepro/homebrew-usd
(install homebrew on macOS, then brew install nzanepro/usd/materialx)
I'm working my way through all the usd dependencies so we can have a full homebrew install of the usd stack. If you decide to incorporate this into your release system, please let me know and I'll delete my fork of MaterialX and repoint homebrew to your release. Maybe I can see if I can work this into GitHub somehow... :-)
Thanks
Zach

Thanks for this excellent follow-up, Zach, and we'll give your script a try for our next release!

Fixed in MaterialX v1.36.5:
https://github.com/materialx/MaterialX/releases/tag/v1.36.5


Non-GC implementation

Can we have a non-GC implementation? I want to understand the challenge.

Would you please elaborate your question?  It's open-ended, and I'd like you to narrow down the meaning of your question.

I'm building a realtime system, and when I notice that Crossbeam uses GC, I'm wondering why it needs one.
Or maybe I was wrong about GC. But the question remains the same, can we have a non-GC implementation of Crossbeam?

Nevermind, thanks @jeehoonkang :+1:

All pointer-based nonblocking data structures need a garbage collector, which may be a lot less sophisticated than JVM or .NET GC but still be at least (semi-)automatic.  This blog post nicely describes the reason: http://aturon.github.io/tech/2015/08/27/epoch/#the-problem
So the choices are (1) implementing a GC, or (2) giving up lock-freedom and implementing blocking data structures.


Internationalization / Translations

In order to make it easier for people we should localize the app and provide translations.
Opening this issue to track how we can approach this.
https://feedback.getalby.com/feature-requests-/posts/i-would-like-to-translate-the-extension-to-pt-br

raspiblitz-web ist running well with a react-i18next and weblate setup:
https://github.com/cstenglein/raspiblitz-web/tree/master/src/i18n

@pavanjoshi914 What setup would you suggest? You had a look at the raspiblitz-web project?

@pavanjoshi914 What setup would you suggest? You had a look at the raspiblitz-web project?

yeah, I just want to ask, if it is feasible to work on this at this moment. If yes, I will propose a detailed plan about, which setup we can integrate, locale management, translation key management , i18n rules for naming of keys etc

yeah, I just want to ask, if it is feasible to work on this at this moment. If yes, I will propose a detailed plan about, which setup we can integrate, locale management, translation key management , i18n rules for naming of keys etc

Sounds great! I assume because this issue exists you're good to go ahead and propose a draft-setup for further discussions. Would that be ok?

yeah, I just want to ask, if it is feasible to work on this at this moment. If yes, I will propose a detailed plan about, which setup we can integrate, locale management, translation key management , i18n rules for naming of keys etc

Sounds great! I assume because this issue exists you're good to go ahead and propose a draft-setup for further discussions. Would that be ok?

okay thanks!

I did not look into any of the options, yet. But you know it better anyway...
Suggestions and PRs on this are for sure welcome! thanks.

sorry for the late! I had my semester exams so didn't have the bandwidth to work on this.
@bumi @escapedcat  here is the proposed i18n architecture for Alby
https://gist.github.com/pavanjoshi914/a65af473209541c3a5cfecbac0f6e70f
after a few revisions, this will also act as developer documentation for i18n in Alby! I will start implementation from now onwards. suggest any changes (if Any)

Setup was merged 🎉


compilation failure for .../migration/script.clj

On the Jenkins server, the build (mvn clean compile) fails because the compiler cannot find the Binding protocol.  The (partial) stack trace is:
Compiling com.sixsq.slipstream.ssclj.migrate.script to /var/lib/jenkins/workspace/Community_Build/SlipStreamServer/ssclj/jar/target/classes
Exception in thread "main" java.lang.ClassNotFoundException: com.sixsq.slipstream.ssclj.db.binding.Binding, compiling:(es_binding.clj:4:1)
	at clojure.lang.Compiler$InvokeExpr.eval(Compiler.java:3657)
	at clojure.lang.Compiler.compile1(Compiler.java:7474)
	at clojure.lang.Compiler.compile1(Compiler.java:7464)
[snip]

Whether this fails depends on the order of the compilation.

The problem is that the Binding protocol is imported as a Java interface rather than being required as a clojure namespace.  If something else hasn't been compiled and implicitly created the Binding class, then the compilation won't look for the clojure source.


[Feature Request] Show cpu temp in taskbar

Description of the new feature / enhancement
The feature would display the current CPU temperature in the taskbar, providing real-time temperature monitoring without the need to open any additional software or windows. Users should be able to see the temperature at a glance, similar to how system clocks or network statuses are shown.
Expected behavior:
The CPU temperature is shown in the taskbar as an icon or text.
The temperature should automatically update at regular intervals (e.g., every 1-2 seconds).
Users can customize the display, such as changing units (Celsius/Fahrenheit) or adjusting update frequency.
There should be an option to alert the user if the CPU temperature exceeds a certain threshold.
The feature should have minimal impact on system performance and resource usage.

Scenario when this would be used?
This feature would be particularly useful in the following scenarios:
Performance Monitoring: When users are running resource-intensive applications like gaming, video editing, or compiling large projects, they can monitor their CPU temperature in real-time to ensure it stays within safe limits, avoiding overheating and potential damage.

Overclocking: Users who overclock their CPUs often monitor temperatures to prevent overheating. Having this information directly in the taskbar helps them adjust performance and cooling mechanisms without needing additional software.

Thermal Troubleshooting: If a user suspects that their system is overheating or has poor cooling, they can use this feature to keep an eye on temperature spikes while running different applications and identify issues more easily.

Battery Optimization: Laptop users might want to keep an eye on CPU temperature to manage performance and prevent the laptop from becoming too hot, which could drain the battery faster and degrade battery health over time.

System Maintenance: Technicians or users maintaining multiple systems might use this to monitor system health quickly, ensuring that cooling mechanisms are functioning correctly across different machines.

Supporting information
No response

/dup #445


About and Contact page

Would like to create the about and contact pages(with a contact form to reach out to you) if you provide the information
please assign this to me under JWOC 24 @Spandan-Bhattacharya

This has already been addressed by some other issue.


Consider moving protocol-related proposal to SIP

Especially for the changes that require public consensus.
Semux enhancement proposals (SIPs) are here, https://github.com/semuxproject/SIPs.

Related issues: #163, #164, #171


Add a script for sneakersnstuff

Added script but keyword search and checkout are missing

Tested and getting errors. Could possibly be caused by Captcha. Is it possible to bypass or solve in browser?
python sneakersnstuff.py
Traceback (most recent call last):
File "sneakersnstuff.py", line 77, in
add_to_cart(early_link, shoe_size)
File "sneakersnstuff.py", line 49, in add_to_cart
size_divs = form.find_all('div', { 'class':  'size-button property available'})
AttributeError: 'NoneType' object has no attribute 'find_all'


Update openbazaar (1.1.0)

Changes to a cask
Editing an existing cask

[x] Commit message includes cask’s name (and new version, if applicable).
[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.

Thank you for the contribution. It was merged directly as 0744b768b7d7cd00dd1d9049caceedc4d4a7ce58 to keep commit history cleaner. Your contribution is still credited to you.


Make the package controller a package

Description of changes:
Helm chart changes for package controller as a package. This removes the CRDs from the main package meaning this will break installation with the current CLI. The CLI must be updated once this is available.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/hold
I want to test keeping the CRDs in the main chart temporarily.

/unhold Keeping the CRDs in, this makes the new chart compatible with the current docs/flow and means we have no CLI changes required outside of the namespace move and create-namespace flag.

/unhold

/lgtm


Very rough WIP draft of Rack cost summary

Release Playbook

[ ] Rebase against master
[ ] Code review
[ ] Merge into master
[ ] Verify changes at http://site-staging.convox.com
[ ] Promote release on site-production in the convox/production Rack

 List AWS resources & cost estimates on Install a Rack doc

Should probably have a section about ELB costs, as they can be significant.


Is there still a Non-OOP version?

Hi,
essentially the title says it :)

If you go back in the git history you can find it. I don't remember how stable it was, so good luck :-)
https://github.com/alanszlosek/dbFacile/commit/529e25527238d1a11a1a46252d8be423f00af9bb

fair enough thanks! :+1:


Improving FreeMarker feature doc

Improving FreeMarker feature doc

On hold. Will merge this once tooling support is available with the next WSO2 Integration Studio release.

Closing this PR for now. Will apply these changes when the next Integration Studio version is released.


Type Detection

Summary:
When parsing files I ran into problems with how paratext parses some of the elements in a file. I believe these may be related to the process_token() function in colbased_worker.hpp that tries to detect whether a token is an integer, float, exponential/scientific number or otherwise.
Examples:
It detects a string such as A.1 as a number and I get 0.000000
It detects a string such as 3ABC as a number and I get 3.000000
Details:
Let A.1 be the input. When reading the token and checking if the token is an integer (line 270) it checks if token_[i] is a digit. If not, we move on to see if we are dealing with a float instead. However we advance the index, i, regardless of whether the integer check passes or fails. Therefore, when we get to the float check on line 279 we are looking at the . character instead of A. Then the check for a float passes since we see . and only digits after it. Finally the result is 0.000000 since A.1 gets converted to a float before it is passed to process_float.
Numbers like 12.345 are not picked up as floats (because the integer check fails on . and we check for float on the next character, here 3), but instead as exponentials. They pass as exponentials not because they pass the exponential check, but because exp_possible is set as true at the beginning (on line 272 after the integer check passes on line 270) and does not become false. Both exponentials and floats are passed to process_float in the end. For the same reason 3ABC is detected as an exponential instead of a string and we get 3.000000. (Numbers like .123 are not detected as floats or exponentials because  exp_possible is set as false after the integer check .)
Note:
When making updates to the process_token() function I did some simplifications, but did not change the behaviour of the function other than for the issues found.
In the code change suggestion I have let a number on the form 14e-3 be a valid exponential (compared to 14.0e-3). This can be changed if not desired.

This patch will need unit tests to demonstrate the problem and corrected output. Where are we at on unit test framework? I can potentially help get a googletest unit test setup going.

Why the source repository is unknown? I wanted to quickly apply the patch, but had to hand-code the change...

Thank you for the bug fix. Can you please pull from master and write a unit test for the fix and run the tests via Travis? Thank you!

Can you pull from wiseio/paratext into your local master so that our regression test suite can test your changes?
  git pull https://github.com/wiseio/paratext.git master

Thank you!

I do not know how your PR lost track of its original repo+branch. I have monkeypatched your PR into https://github.com/wiseio/paratext/pull/53 and added some tests.
I will go ahead and close this PR as it is now superseded by #53 .
Thanks for your bug fix!
Damian


NUID generate same consumers names for native compiled  executable

Proposed change
Reflect in DOCS that io.nats.client.NUID should be initialized at runtime as well:
--initialize-at-run-time=io.nats.client.NUID

Use case
Native compiled executables.
Contribution
No response

@Andro999b Are you sure, because it depends on RandomUtils, which is already identified in the readme. Maybe it's a Quarkus specific thing?

Is it the are static things in the NUID class that are problematic?
Would just saying initialize at runtime for the NUID cover RandomUtils since it's a dependency?
Have you verified the consumer names are identical? It could be that they are very similar and may only differ in the last character.

@scottf I'm pretty sure about this. I have updated my previous reproducer so you can check it: https://github.com/Andro999b/nats-java-native-build-reproducer
Don't know if this Quarkus specific or not. But NUID have static global instance that will be initialized in build time by default. Call to the RandomUtils(initialized in runtime) does not matter here because GralVM  does inline methods during compilation.


fixed links to Erlang and Akka

I have fixed the links to Erlang and Akka. I believe they point to the correct location now, hope that helps.

Thanks @AngusTheMack


[Feature] 官方文档数据的列数

Search before asking

[X] I had searched in the issues and found no similar issues.

Description
t1建表有5个列，插入时有6个列

Use case
No response
Related issues
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

There is an error in the document, I can help you to submit the pr for modification.

There is an error in the document, I can help you to submit the pr for modification.

how to submit it ?

There is an error in the document, I can help you to submit the pr for modification.

how to submit it ?

add my wechat: Faith_xzc


Step1:add admin server image - [closed]

In GitLab by @liyanq528 on Jan 16, 2019, 07:30
Merges add-admin-server -> dev

In GitLab by @wknet123 on Nov 13, 2019, 11:36
The test coverage for backend is %  38.96%  , check  console log

In GitLab by @wknet123 on Nov 13, 2019, 11:36
closed


error when run ./strato-run.sh

% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100   615    0   615    0     0   1773      0 --:--:-- --:--:-- --:--:--  17721
100  4939  100  4939    0     0   5909      0 --:--:-- --:--:-- --:--:--  5909
ERROR: Version in "./docker-compose.latest.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a version of "2" (or "2.0") and place your service definitions under the services key, or omit the version key and place your service definitions at the root of the file to use version 1.
For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/

found answer from pervious issue.
sudo curl -L https://github.com/docker/compose/releases/download/1.19.0/docker-compose-uname -s-uname -m -o /usr/local/bin/docker-compose


Engagement Metadata

Issue #:
https://github.com/bcgov/met-public/issues/
Description of changes:
Add engagement metadata fields
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the met-public license (Apache 2.0).

Codecov Report

Merging #1407 (72d7fa1) into main (18af06c) will decrease coverage by 0.20%.
The diff coverage is 54.76%.

@@            Coverage Diff             @@
##             main    #1407      +/-   ##
==========================================
- Coverage   71.13%   70.94%   -0.20%
==========================================
  Files         324      328       +4
  Lines        9396     9516     +120
  Branches      677      677
==========================================
+ Hits         6684     6751      +67
- Misses       2593     2646      +53
  Partials      119      119

Flag
Coverage Δ

metapi
78.17% <54.76%> (-0.58%)
:arrow_down:

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

Impacted Files
Coverage Δ

met-web/src/apiManager/endpoints/index.ts
100.00% <ø> (ø)

...b/src/components/engagement/form/ActionContext.tsx
60.86% <ø> (-0.84%)
:arrow_down:

...agement/form/EngagementFormTabs/EngagementForm.tsx
75.58% <ø> (ø)

...ent/form/EngagementFormTabs/EngagementSettings.tsx
71.42% <ø> (-2.77%)
:arrow_down:

.../form/EngagementFormTabs/EngagementTabsContext.tsx
64.28% <ø> (-0.63%)
:arrow_down:

met-web/src/models/engagement.ts
100.00% <ø> (ø)

...rc/met_api/services/engagement_metadata_service.py
48.38% <48.38%> (ø)

...t-api/src/met_api/resources/engagement_metadata.py
50.00% <50.00%> (ø)

met-api/src/met_api/models/engagement_metadata.py
59.09% <59.09%> (ø)

met-api/src/met_api/resources/__init__.py
100.00% <100.00%> (ø)

... and 1 more

... and 1 file with indirect coverage changes


Update the "Improving The Documentation" section of the README.md file

Right now there is no content. This would be a good first issue.
See Improving The Documentation

I have raised pr , please check


Support Eclipse 3.8

The Eclipse available in Debian and Ubuntu is version 3.8.1.
Please make this plug-in support Eclipse 3.8.x and later.

:-1:
Just get the latest 4.5-based solution. You may loose a lot by using 3 years-old software, while it will become burden for a new project to support older platform versions.


[iOS]bugfix: toast should display on weex window

bugfix: weex toast should display on the window that contain weex root view

bugfix: weex toast should display on the window that contain weex root view

hi @x461909066   please follow the development-process  here, pay more attention to the commit message format http://weex.apache.org/development-process.html


v0.0.9 version bump & changelog update

v0.0.9 - 2024-08-22 - Retry until your hearts content

Add support for fully managing/configuring the client retry policy & fix
previous config options so that they actually take effect

/cc Fixes https://github.com/octodns/octodns-azure/issues/97

/cc https://pypi.org/project/octodns-azure/0.0.9/


"Encoder: Image creation failure: Unknown error" after update to Mesa 23.6

Description

Everything worked amazingly well on Mesa 23.2.1 but after I updated to the latest Mesa 23.6.3 I am getting the error "Encoder: Image creation failure: Unknown error" followed by "error in encoder thread: Failed to initialize vulkan frame context: Invalid argument"
I managed to trace the problem to a failed call to av_hwframe_ctx_init() in ffmpeg_helper.cpp which in turn calls vulkan_frames_init() in ffmpeg's hwcontext.c itself calling create_frame() on line 2374 in hwcontext_vulkan.c
The call seems to be the exact same with identical parameters but for some reason the new Mesa 23.6.3 refuses to create this frame and returns an unknown error.
I can regain full function by swapping to the original libvulkan_intel.so library version 23.2.1, no other changes to ICD files or any other part of Mesa, so the problem seems to be with this exact function.
I realise that this is technically on the ffmpeg side of things and I did try to change the dependency in the ALVR sources from ffmpeg 6.0 to 6.1.1 but because of various patches being applied this didn't work out.

General Troubleshooting

[x] I carefully followed the instructions in the README and successfully completed the setup wizard
[x] I read the ALVR Wikis here and here

Environment
Hardware
hw-probe -all -upload: https://linux-hardware.org/?probe=0ee555fcd8
Installation
ALVR Version:
Latest git, but problem has already persisted for weeks.
ALVR Settings File:
session.json
SteamVR Version: 2.3.5
Install Type:

[x] Packaged (exe, deb, rpm, etc)
[x] Portable (zip)
[x] Source

OS Name and Version
openSUSE Tumbleweed

@nowrep, apologies for calling you out, but I believe you last worked on the Linux ffmpeg code. Do you have any insight why the latest Mesa libvulkan_intel.so library doesn't accept the arguments anymore it receives from ffmpeg?

Mesa 23.6.3

This is not a valid version.

I managed to trace the problem to a failed call to av_hwframe_ctx_init() in ffmpeg_helper.cpp which in turn calls vulkan_frames_init() in ffmpeg's hwcontext.c itself calling create_frame() on line 2374 in hwcontext_vulkan.c

Sounds like ffmpeg bug or mesa regression.
But also the Vulkan ffmpeg context in alvr is only used for nvidia, so probably it could just ignore these errors on intel/amd.

Thanks for the quick reply and apologies for the typo, it should have been 23.3.6 rather than 23.6.3. I can see how that was very unhelpful in identifying the issue.
If the respective ffmpeg code is not required for intel/amd hardware, perhaps it could be factored out rather than let it fail? Not sure why it would fail though.

For what it's worth, I skipped the call to av_hwframe_ctx_init() in ffmpeg_helper.cpp by commenting it out and this solves the issue for me.
Maybe if one calls cargo prepare-deps with the --no-nvidia option this part of the code shouldn't be compiled in, if it's only used on nvidia cards?
Or maybe somebody can find out why this fails in the first place. It used to work just fine until Mesa 23.2.1 but hasn't worked since. The latest version I tried was Mesa 24.0.3. Possibly it should fail because it's nvidia specific, but I haven't got the insight to understand what this call is really doing, which to me looks like generic Vulkan code.

I can confirm that this happens on an Intel ARC a750 as well. Some games don't render correctly on the older mesa versions and require a broken version to render correctly so there is definitely some benefit to having this work over just using the old version of mesa.

To the best of my knowledge this still hasn't been fixed even though the fix is trivial. Just don't call av_hwframe_ctx_init() on Intel graphics cards.

Has this been resolved by anyone yet? The issue is still present for me. Arc A770, newest version of ALVR and SteamVR.

I'm having the exact same issue with GTX 1650. Mesa version is 24.1.5 and Nvidia driver version is 555.58.02. Instead of SteamVR home I get black screen in the VR

Same issue on Debian 12 Stable. Dell G7 with Nvidia RTX 2060. Can provide more information if necessary. A fix is greatly appreciated. I need this for my studies.

If you really need VR streaming maybe try Wivrn. I've found it to be much easier to work with since it is standalone from SteamVR. https://lvra.gitlab.io has a trove of information about this.

I'm having the exact same issue with GTX 1650. Mesa version is 24.1.5 and Nvidia driver version is 555.58.02. Instead of SteamVR home I get black screen in the VR

Afaik this is an intel specific issue. Are you actually getting the error mentioned or just the black screen issue? If it's the latter you should go check out https://github.com/alvr-org/ALVR/wiki/Linux-Troubleshooting, it has a fix for that.

I'm having the exact same issue with GTX 1650. Mesa version is 24.1.5 and Nvidia driver version is 555.58.02. Instead of SteamVR home I get black screen in the VR

Afaik this is an intel specific issue. Are you actually getting the error mentioned or just the black screen issue? If it's the latter you should go check out https://github.com/alvr-org/ALVR/wiki/Linux-Troubleshooting, it has a fix for that.

I am having the error mentioned. This may have something to do with the fact that my PC has an integrated Intel GPU (Intel® UHD Graphics 730 (ADL-S GT1) in the 12th Gen Intel® Core™ i5-12400 CPU) that I can't disable because my monitor could only be connected to the motherboard's HDMI port (the GPU's HDMI port is inaccessible in my PC case). But I wrote __NV_PRIME_RENDER_OFFLOAD=1 __VK_LAYER_NV_optimus=NVIDIA_only __GLX_VENDOR_LIBRARY_NAME=nvidia %command% in the SteamVR's launch options. With or without them the two mentioned error windows (one with "Encoder: Image creation failure: Unknown error" and the other one with "error in encoder thread: Failed to initialize vulkan frame context: Invalid argument") aren't affected

@Alvenster @Akeem29 you both seem to suffering from the integrated gpu taking precedence rather than the dedicated gpu.
Note that you currently always need to apply the first fix on the linux troubleshooting page. In your case you'd also need the nvidia dedicated gpu fix. If that doesn't work you should run vulkaninfo (normally available through vulkan-tools) with the environment variables from the dgpu fix and report back what it outputs to debug the gpu selection.
Although since what you're encountering aren't really bugs but rather configuration issues and they're in fact unrelated to this issue you'd probably be better off asking for help on the discord/matrix.

Couple of fresh notes to the issue:
I got it to work only on mesa-tkg-git (https://github.com/Frogging-Family/mesa-git/tree/master) and with https://github.com/Aikufurr/ALVR/commit/f1ffa2a94e72426a0eeb6940be76a3a948fb6dfc commit
Intel Arc igpu on laptop
software encoder though doesn't work, it crashes steamvr, and backtracing points to this only (no idea what's wrong, segfault happens here, variables are present and it's not out of boundary)

Same error as the OP - "Encoder: Image creation failure: Unknown error" followed by "error in encoder thread: Failed to initialize vulkan frame context: Invalid argument".
Have done all the Linux troubleshooting and still happens.
Intel Arc A770, no integrated GPU.

Yes, this a known bug due to amd drivers messing up their vaapi implementation. I know how to fix it, I just haven't gotten around to implementing it in alvr.


Added a short intro to the project.

Closes #50
Added a short intro to the project.
The readme.md file of the project did not introduce the project to the New contributors. New Contributors including me need  some idea about what the project is, in order to be familiar about the project.
Proposed Changes
I  added a short intro to the project.
Check List (Check all the applicable boxes)

[ ] Bug(s) fixed
[x] Enhancement done
[ ] New Feature(s) added
[x] Documentation changed
[x] All new and existing tests passed.
[x] My code follows the code style of this project.

Screenshots (if any)

Additional Information

Now the readme file looks better. Thank you for your contributions.

Thank you bhaiya. Thanks a lot for merging


[trac_ik_kinematics_plugin]: Add support for ROS 2

From #1, the primitive directives are:

[ ] Write the plugin for moveit2.
[ ] Update moveit documentation about the trac_ik library and about writing said plugins.

I'm labeling this Help Wanted because I have zero experience with MoveIt!, but that's always a learning opportunity...

Came from https://bitbucket.org/traclabs/trac_ik/issues/68/ros2-support#comment-60898131
Assuming this repo is a fork from there, why don't you open a PR to that repo? That may accelerate the work to port trac-ik to ros2.


Handling query string with same path, component

I'm using<EMAIL_ADDRESS>and<EMAIL_ADDRESS>And I'm trying to change data when query string was changed by user actions (maybe commonly using querystring with filtering)
/search?q=blah&isComment=0
to
/search?q=blah&isComment=1
But <Search/> Component does not re-rendering.
Search.jsx
class Search extends React.Component {
  componentDidMount () {
   // **maybe here is not work when query string is changed on same path.**
    const {query, comment} = someThingParseQueryString(this.props.location.search)
    this.fetchData(query, comment)
  }

  fetchData(query, isComment) {
    getSearch(query, isComment)
      .then(res => {
        this.setState({posts: res.data.posts})
      })
  }

  handleClick = comment => event => {
    const {query, comment} = someThingParseQueryString(this.props.location.search)
    this.history.push(`/serach?q=${query}&isComment=${comment}`}
  }

  render () {
     return (
       <Fragment>
         Only Post
         Only Comment
         {this.state.posts.map(item =>

              {item.title}

         )}
       </Fragment>
     )
  }
}

Root.jsx
import { Provider } from 'react-redux'
import { Route } from 'react-router-dom'
import { ConnectedRouter } from 'react-router-redux'

<Provider store={store}>
  <ConnectedRouter history={history}>
    <Route path="/:filter?" component={App} />
  </ConnectedRouter>
</Provider>

App.jsx
const ConnectedSwitch = connect(state => ({
  location: state.router.location
}))(Switch)

const App = () => (
    <ConnectedSwitch>
      <Route path='/search' component={Search}/>
    </ConnectedSwitch>
)

I read the docs about Dealing with Update Blocking. but In my opinion, This is not same issue my cases.

Maybe using React lifecycle componentDidUpdate (prevProps) right?

This is a bug tracker, not a support system. For usage questions, please use Stack Overflow or Reactiflux where there are a lot more people ready to help you out. Thanks!

this seems like a bug or undocumented "feature" in the router to ignore search-string changes.


Release/0.2

Codecov Report

Merging #494 (42810cb) into release/0.2 (2f565d7) will decrease coverage by 0.05%.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           release/0.2     #494      +/-   ##
===============================================
- Coverage        69.32%   69.26%   -0.06%
===============================================
  Files              217      217
  Lines            11841    11841
===============================================
- Hits              8209     8202       -7
- Misses            3632     3639       +7

Impacted Files
Coverage Δ

mediaPlayer/media_packet_queue.cpp
72.80% <0.00%> (-10.41%)
:arrow_down:

framework/demuxer/play_list/SegmentList.cpp
86.20% <0.00%> (-10.35%)
:arrow_down:

mediaPlayer/buffer_controller.cpp
55.08% <0.00%> (-2.55%)
:arrow_down:

mediaPlayer/player_notifier.cpp
81.81% <0.00%> (-1.07%)
:arrow_down:

framework/demuxer/play_list/SegmentTracker.cpp
83.33% <0.00%> (-0.54%)
:arrow_down:

framework/codec/ActiveDecoder.cpp
84.50% <0.00%> (-0.47%)
:arrow_down:

framework/demuxer/play_list/HLSStream.cpp
67.65% <0.00%> (-0.26%)
:arrow_down:

mediaPlayer/MediaPlayer.cpp
69.57% <0.00%> (-0.21%)
:arrow_down:

mediaPlayer/SuperMediaPlayer.cpp
74.93% <0.00%> (-0.10%)
:arrow_down:

framework/data_source/curl/curl_data_source.cpp
85.31% <0.00%> (+1.58%)
:arrow_up:

... and 4 more

Continue to review full report at Codecov.

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


[glance] Add canonical layout demo browser activity

I was unable to run the script ./gradlew --init-script gradle/spotless-init.gradle.kts spotlessApply

Can you update Glance to rc01 from the SNAPSHOT?
How hard would it be to make the Canonical Widgets screen match the app theme?


Add default impl to handle token challenges

API change check
API changes are not detected in this pull request.

/check-enforcer override


⚠ Bofrost.de has degraded performance

In 8f152d8, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1968 ms

Resolved: Bofrost.de performance has improved in 88aad1b after 13 minutes.


Add elb

Please check if the PR fulfills these requirements

[X] The commit message describes your change
[X] Tests for the changes have been added if possible (for bug fixes / features)
[X] Docs have been added / updated (for bug fixes / features)
[ ] Changes are mentioned in the changelog (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Add methods for managing the AWS ALB within Jenkins

What is the current behavior? (You can also link to an open issue here)
New functionality

What is the new behavior (if this is a feature change)?
Add methods to register/deregister a target from a target group and to check that both have completed successfully (as the SDK makes a request but does not wait for a response that can be returned)

Does this PR introduce a breaking change? (What changes might users need to make in their setup due to this PR?)
No

Other information:

There seems to an issue with the Jenkins server that is running these tests.
How can we get this reviewed?

Thanks for the addition. Can you please add it to the changelog in the README file? I will then force merge it, as it was successful but the build server failed to cleanup.

Changelog has been updated @hoegertn


Parse only date but not time

Hi,
is there a possibility to pre-define that only dates will be parsed?
Would this speed up the computation?
Right now the parsing of many languages takes too long so we have narrowed it down to EN, DE and ES. But we would like to apply it to all available languages.
Thanks in advance

Not sure if avoiding parsing times will help and how hard it is, but there were some speed improvements in master related to using all available language, which are not yet released on PyPI - maybe they will already help your use case.

Ok, thanks for your reply!


Clear-All button feature

A classical way to clear all input values. Created a button and added an Event Listener targeting the values of the inputs.
Issue: #2

Thank you for your contribution! Although I've noticed that this doesn't yet remove the data from the browser's local storage, so the extension only "demonstrated" data deletion, which is not quite what was intended for this feature. If it's not much of a problem, then I'd kindly ask you to apply that change as well so the Pull Request becomes merge-able.


Confirm prompt defaults to $true

Related: https://social.technet.microsoft.com/Forums/windowsserver/en-US/68274d6e-db57-43ad-beca-aaa048438842/removeadgroupmember-disable-confirm-prompt?forum=winserverpowershell
Remove-ADPrincipalGroupMembership asks for confirmation even without passing -Confirm.
Taken from the linked page above I was able to get it to silently process by passing -Confirm:$false.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a040d973-5979-a10d-bbed-3b4221f45cda
Version Independent ID: dc1ba824-fdb3-9160-9e74-c6ecf57629b5
Content: Remove-ADPrincipalGroupMembership (activedirectory)
Content Source: docset/winserver2012-ps/activedirectory/Remove-ADPrincipalGroupMembership.md
Product: w10
Technology: powershell
GitHub Login: @brianlic-msft
Microsoft Alias: brianlic

@officedocsbot assign @e0i

Hi @Nothing4You
Thank you for reaching out!
Yes, document has been updated with the notes section.
https://docs.microsoft.com/en-us/powershell/module/activedirectory/remove-adprincipalgroupmembership?view=winserver2012-ps#notes
By default, this cmdlet has the -Confirm parameter set, which prompts you to confirm before a removal of the specified object type can occur. To bypass prompting for confirmation before removal, you can specify -Confirm:$false when using this cmdlet.
Hope this clarifies. Thank you.

Hi @sowjanya365, thanks for your response.
That note should not be needed if the parameter documentation gets corrected here: https://github.com/MicrosoftDocs/windows-powershell-docs/blob/master/docset/winserver2012-ps/activedirectory/Remove-ADPrincipalGroupMembership.md#-confirm
The Default value should be True from my understanding.

Hi @Nothing4You
Thanks for your inputs. We've updated the document now. Once the PR gets merged, we will be able to see the changes.

@Nothing4You
With the help of your feedback, the content has been updated with relevant changes accordingly. Thanks.

@officedocsbot close


NumPy Algebra and Size: Size and Efficiency Question

Checklist:

[X] I have read freeCodeCamp's contribution guidelines.
[X] My pull request has a descriptive title (not a vague title like Update index.md)
[X] My pull request targets the master branch of freeCodeCamp.
[X] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #XXXXX

Makes sense, thanks for catching that!


bug: Can't disable the bufferline's mapping of ,  to unveil original Vim motion

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have searched the existing issues of LazyVim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
v0.9.4
Operating system/version
Arch Linux Kernel 6.6.2
Describe the bug
I'm trying to disable bufferline's mapping of <S-h> and <S-l> to cycle buffers, i.e:
  {
    "akinsho/bufferline.nvim",
    event = "VeryLazy",
    keys = {
      ...
      ..
      { "<S-h>", "<cmd>BufferLineCyclePrev<cr>", desc = "Prev buffer" },
      { "<S-l>", "<cmd>BufferLineCycleNext<cr>", desc = "Next buffer" },
      ...
      ..
    },

by disabling the mappings as described in Adding & Disabling Plugin Keymaps:
return {
  {
      -- Other UI plugins
  },
...
..
  {
    "akinsho/bufferline.nvim",
    keys = {
      { "<S-h>", false },
      { "<S-l>", false },
    },
  },
}

in a ui.lua file.
What I hoped for is that would unveil the default Vim motions for these mappings, i.e. "move to top of screen"/"move to bottom of screen".
I looked through a bunch of issues and my case resemble #1485 a bit but it doesn't matter if you provide arguments or not.
Steps To Reproduce

default behavior of LazyVim is to cycle buffers for <S-h> and <S-l>
Add a file lua/plugins/ui.lua with the following content:{
 "akinsho/bufferline.nvim",
 keys = {
   { "<S-h>", false },
   { "<S-l>", false },
 },
},

Reload nvim.
The keys still cycle buffers.

Expected Behavior
The normal Vim motions for the key should be unveiled, i.e. "move to top of screen"/"move to bottom of screen" respectively.
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  "folke/LazyVim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

If you search for <s-h> in the search box for this repo, you will see these results and you can see that <s-h> is defined in 2 places. One place is the bufferline spec like you already mentioned and the other place is in lazyvim/config/keymaps.lua as general keymaps that map to the vim bnext/bprevious for cycling buffers without Bufferline. So, in your /lua/config/keymaps.lua you have to delete those mappings as well. Not a bug either case.

Oh, totally missed the mapping in keymaps.lua. Deleting the mappings with vim.keymap.del did the trick. Thanks @dpetka2001 .

@olatheander Could you kindly close this issue if it's resolved?

For those who reached here for the same reason as me, just add this to your ~/.config/nvim/lua/config/keymaps.lua:
vim.keymap.del("n", "<S-h>")
vim.keymap.del("n", "<S-l>")

For those who reached here for the same reason as me, just add this to your ~/.config/nvim/lua/config/keymaps.lua:
vim.keymap.del("n", "<S-h>")
vim.keymap.del("n", "<S-l>")

Appreciated when someone is helpful and clear and not patronizing to users who are puzzled as to why a tool behaves in an unexpected manner (ie overridding native Vim keybindings that are indeed used frequently)

@davetrust,
You are indirectly saying: The comment from @dpetka2001 is patronizing. You even added a thumb down.
I really dislike indirect qualifications and I think your comment is totally inappropriate.
Please, have a look at the closed issues in this repository. While you're at it, also have a look at the responses in the discussions.
I think the answer is very clear and helpful. It's important to understand the "why". And indeed, it's not a bug. That can happen.