Pose Tracking - static_image_mode support?

Description
Do you support STATIC_IMAGE_MODE in Pose solution?
I've checked PoseTrackingConfig.cs and SidePackets that PoseTrackingGraph.cs is sending, but I couldn't find how to set STATIC_IMAGE_MODE.
Is it possible to set STATIC_IMAGE_MODE? If so, how do I do it?

STATIC_IMAGE_MODE is not implemented in the Pose Tracking sample currently.
You need to set use_prev_landmarks to false at runtime using ValidatedGraphConfig.
Please see https://github.com/homuler/MediaPipeUnityPlugin/issues/642#issuecomment-1177484869 for more details.

Thanks. Is this the correct way to set use_prev_landmarks?
bool STATIC_IMAGE_MODE = true;
_graph = new CalculatorGraph();

using (var validatedGraphConfig = new ValidatedGraphConfig())
{
	var graphConfig = CalculatorGraphConfig.Parser.ParseFromTextFormat(_textConfig.text);
	validatedGraphConfig.Initialize(graphConfig).AssertOk();

	var extensionRegistry = new ExtensionRegistry() { GateCalculatorOptions.Extensions.Ext };
	var cannonicalizedConfig = validatedGraphConfig.Config(extensionRegistry);
	var gateCalculators = cannonicalizedConfig.Node.Where((node) => node.Calculator == "GateCalculator").ToList();

	foreach (var calculator in gateCalculators)
	{
		if (calculator.Options.HasExtension(GateCalculatorOptions.Extensions.Ext))
		{
			var options = calculator.Options.GetExtension(GateCalculatorOptions.Extensions.Ext);

			// Set GateCalculator.Allow a.k.a use_prev_landmarks to STATIC_IMAGE_MODE
			options.Allow = STATIC_IMAGE_MODE;
		}
	}

	_graph.Initialize(cannonicalizedConfig);
}

Sorry, it seems that we don't need to modify the config dynamically.
Try adding an input_side_packet definition and setting the side packet at runtime.
diff --git a/Assets/MediaPipeUnity/Samples/Scenes/Pose Tracking/pose_tracking_gpu.txt b/Assets/MediaPipeUnity/Samples/Scenes/Pose Tracking/pose_tracking_gpu.txt
index 9a725b5..3b3ad9d 100644
--- a/Assets/MediaPipeUnity/Samples/Scenes/Pose Tracking/pose_tracking_gpu.txt
+++ b/Assets/MediaPipeUnity/Samples/Scenes/Pose Tracking/pose_tracking_gpu.txt
@@ -73,6 +73,7 @@ node {
   input_side_packet: "SMOOTH_LANDMARKS:smooth_landmarks"
   input_side_packet: "ENABLE_SEGMENTATION:enable_segmentation"
   input_side_packet: "SMOOTH_SEGMENTATION:smooth_segmentation"
+  input_side_packet: "USE_PREV_LANDMARKS:use_prev_landmarks"
   output_stream: "LANDMARKS:pose_landmarks"
   output_stream: "WORLD_LANDMARKS:pose_world_landmarks"
   output_stream: "SEGMENTATION_MASK:segmentation_mask_gpu"

Working great. Thanks for your help!


KAFKA-12648: fix bug where thread is re-added to TopologyMetadata when shutting down

We used to call TopologyMetadata#maybeNotifyTopologyVersionWaitersAndUpdateThreadsTopologyVersion when a thread was being unregistered/shutting down, to check if any of the futures listening for topology updates had been waiting on this thread and could be completed. Prior to invoking this we make sure to remove the current thread from the TopologyMetadata's threadVersions map, but this thread is actually then re-added in the #maybeNotifyTopologyVersionWaitersAndUpdateThreadsTopologyVersion call.
To fix this, we should break up this method into separate calls for each of its two distinct functions, updating the version and checking for topology update completion. When unregistering a thread, we should only invoke the latter method

cc @wcarlson5

All test failures are unrelated, going to merge this now


feat: implement rhc_proxy.scheme

Starting with community.general 6.2.0, the redhat_subscription module has a server_proxy_scheme parameter to configure the type of proxy server that subscription-manager uses (see [1], backported to community.general 6.x with [2]).
Hence, add a scheme attribute for the rhc_proxy role parameter, allowing users to configure the proxy type. To make sure to be able to test this, also add new optional test variables, using them in "tests_proxy" if specified.
[1] https://github.com/ansible-collections/community.general/pull/5662
[2] https://github.com/ansible-collections/community.general/pull/5671

Do you need to add proxy_noauth_scheme and proxy_auth_scheme to https://github.com/linux-system-roles/rhc/blob/main/tests/files/candlepin_data.yml and to our internal test data files?

I made them as omit, so there should be no immediate need for changes. I can add them to the included config to still be a good example. Thanks!

[citest]


Use sphinx autosummary for pytket-qiskit API docs

Description
I've used the sphinx :autosummary: role to summarise the pytket-qiskit API docs

Related issues
Please mention any github issues addressed by this PR.
Checklist

[x] I have performed a self-review of my code.
[ ] I have commented hard-to-understand parts of my code.
[x] I have made corresponding changes to the public API documentation.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have updated the changelog with any user-facing changes.

Is this ready for review? @CalMacCQ

Is this ready for review? @CalMacCQ

Sorry should have marked as a draft. Its almost done. There is just a CI failure to fix and some other minor things.


Heeelp please

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az spring app deploy
Errors:
The command failed with an unexpected error. Here is the traceback:
No module named 'termios'
Traceback (most recent call last):
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 233, in invoke
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 561, in execute
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/__init__.py", line 507, in load_arguments
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 318, in load_arguments
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/commands.py", line 104, in load_arguments
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 125, in arguments_loader
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 59, in get_op_handler
  File "importlib\__init__.py", line 126, in import_module
  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "C:\Users\Ozzy\.azure\cliextensions\spring\azext_spring\app.py", line 10, in <module>
    from .custom import app_get
  File "C:\Users\Ozzy\.azure\cliextensions\spring\azext_spring\custom.py", line 12, in <module>
    import tty
  File "tty.py", line 5, in <module>
ModuleNotFoundError: No module named 'termios'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az spring app deploy --resource-group {} --service {} --name {} --artifact-path {}

Expected Behavior
Environment Summary
Windows-10-10.0.18363-SP0
Python 3.10.5
Installer: MSI

azure-cli 2.40.0

Extensions:
spring 1.1.8

Dependencies:
msal 1.18.0b1
azure-mgmt-resource 21.1.0b1

Additional Context

route to CXP team

@OZZYTA Thank you for reaching out to us, we are looking into it.

@OZZYTA This issue seems to be fixed by this PR https://github.com/Azure/azure-cli-extensions/pull/5378. Could you please run the below command to update your spring extension and check if you still see the same issue ?

az extension update -n spring

Awaiting your reply.

@OZZYTA I wanted to do quick follow-up to check if you had a chance to look at my above comment. Please let us know if you had any updates on this. Awaiting your reply.

@OZZYTA The action is currently pending on you to update the spring extension using the above command. If you need any further assistance on this issue in future, please feel free to reopen this thread. We would be happy to help.


General: Configure GitLab for supporting GitLab CI

Checklist
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[ ] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Server

[x] I followed the coding and design guidelines.
[x] I added multiple integration tests (Spring) related to the features (with a high test coverage).
[x] I implemented the changes with a good performance and prevented too many database calls.
[x] I documented the Java code using JavaDoc style.

Changes affecting Programming Exercises

[ ] I tested all changes and their related features with all corresponding user types on Test Server 1 (Atlassian Suite).
[ ] I tested all changes and their related features with all corresponding user types on Test Server 2 (Jenkins and Gitlab).

Motivation and Context
As part of my thesis, I add the support of GitLab CI as a CI system for Artemis.
This is the first PR for configuring the CI correctly, when creating and starting an exericse in Artemis.
Description
I changed just the minimum for adding support for GitLab CI. I implemented the necessary interfaces required for creating and starting the exercises.
Steps for Testing
Prerequisites:

Local GitLab instance with a Runner (See #4881 for setup)
MySQL database

Please test this pull request locally.

Generate a personal access token with all scopes under http://localhost/-/profile/personal_access_tokens
Create application-local.yml and adapt the password and the access token

artemis:
    course-archives-path: ./exports/courses
    repo-clone-path: ./repos
    repo-download-clone-path: ./repos-download
    encryption-password: artemis_admin           # LEGACY: arbitrary password for encrypting database values
    bcrypt-salt-rounds: 11  # The number of salt rounds for the bcrypt password hashing. Lower numbers make it faster but more unsecure and vice versa.
    # Please use the bcrypt benchmark tool to determine the best number of rounds for your system. https://github.com/ls1intum/bcrypt-Benchmark
    user-management:
        use-external: false
        internal-admin:
            username: artemis_admin
            password: artemis_admin
        accept-terms: false
        login:
            account-name: TUM
    version-control:
        url: http://<IP_ADDRESS>:80
        user: root
        password: artemis_admin # Change here!
        token: artemis-gitlab-token # Change here!
    git:
        name: Artemis
        email<EMAIL_ADDRESS>server:
    port: 8080
    url: http://<IP_ADDRESS>:8080 # `http://host.docker.internal:8080` for Windows

Start Artemis with the gitlabci profile. Use Artemis (Server, GitLabCI & Gitlab) in IntelliJ.
Open Artemis in your browser and create a new course.
Generate a new programming exericise (with default configuration).
Open the template, solution and test repository. In the template and solution repository CI should be enabled and configured. Go to Settings > CI/CD > General Pipelines and check if https://home.in.tum.de/~scbe/Artemis/gitlabci-runners/getting-started-template.yml is the CI/CD configuration file. In the test repository CI should be disabled. Check if in Settings > General > Visibility, project features, permissions CI/CD is disabled.

Review Progress
Code Review

[ ] Review 1
[ ] Review 2

Manual Tests

[x] Test 1
[x] Test 2

Test Coverage

Class/File
Branch
Line

GitLabCIUserManagementService.java
-
25%

GitLabCIService.java
-
94%

GitLabCIAuthorizationInterceptor.java
-
30%

GitLabCIBuildPlanLinkInfoContributor.java
-
30%

GitLabCIProgrammingLanguageFeatureService.java
-
100%

GitLabCIException
-
30%

@jpbernius @Mtze The PR is now ready for review.

@bensofficial I tested it locally, worked without any issues!

@b-fine Thank you for your review and suggestions. I am not quite sure how to implement verifications and asserts if a method has been called. I tried my best, but please let me know if it is wrong or can be improved.

This PR is already open for more than 2 months (which is bad practice). Please finish this PR in the next couple of working days or we close it. You can then reopen it when you have again more time to actively work on it and finish it.

@krusche From my side, this PR is completed, so I am adding more commits to this branch. I'm just waiting for additional code reviewers to merge since I marked the PR as ready for review more than a month ago. I thought even though I don't want to merge into the "real" development branch, 2 code reviewers are better to get further feedback on the changes. If you disagree, please let me know.
Currently, I'm already working on the next follow-up tasks (in a different branch) to add the full functionality for GitLab CI.

@krusche From my side, this PR is completed, so I am adding more commits to this branch. I'm just waiting for additional code reviewers to merge since I marked the PR as ready for review more than a month ago. I thought even though I don't want to merge into the "real" development branch, 2 code reviewers are better to get further feedback on the changes. If you disagree, please let me know.
Currently, I'm already working on the next follow-up tasks (in a different branch) to add the full functionality for GitLab CI.

If the PR is in the state ready for review for more than a month, that's also best practice. Then, I suggest you ask some other developers for tests and reviews. You can organize a testing session and/or participate in one. You can also try to review more PRs from other developers, so that it's more likely to retrieve reviews from others as well.
Just labeling the PR as ready for review and then waiting is not enough in my opinion, you have to get active ;-)

@krusche Yes, of course it's not good to just wait, but I've already asked for reviews in Slack. Moreover, @jpbernius has written a message in the development Slack channel.
As for the testing sessions, unfortunately during school time it is not possible for me to attend any of them (I write my thesis as part of TUMKolleg).

@bensofficial I know all this and can understand it, nevertheless you could organize a testing session outside your school activities or add your PR to the Confluence page for an existing testing session. It's also possible to talk to other developers who have experience with programming exercises in personal (e.g. on Slack) and kindly ask them for a review.
Writing a message in the development Slack channel is typically not successful, especially for larger PRs, so I suggest you try out different techniques.

@krusche Thank you for your reply. I didn't know that I am allowed to add my PR to a test session on the Confluence page, even if I don't attend. I will do that and note that I only need another code review and no manual testing. Further, I don't know who is familiar with programming exercises (and ideally GitLab), so I was hoping someone in the Slack channel would feel addressed.
I just want to make sure my PR doesn't get closed.
As for hosting my own test session, I can do that during the summer holidays for my next PR if required.


Add getParameters to Request Hook API

This will add getParameters so that we can access the parameters sent. It's actually pretty similar to https://github.com/getinsomnia/insomnia/pull/731 but with smaller scope (and with test). I don't mind if the former PR got merged first as I really need this functionality 😆

This is exactly what I'm looking for.  Thank you @amree!

@gschier is there any chance to release this soon? Thanks

Getting to it soon. It'll be in the next release for sure

Added a fully-implemented solution in https://github.com/getinsomnia/insomnia/commit/dc0695de23f3c2b3a1d9086d1c972ca03313fdd6


Duplicate symbol error

Hi everyone,
When compiling on macOS 10.14 with Python 3.7 and GEOS 3.8 in a clean virtual env, I got a compiler/linker error:
duplicate symbol '_GeometryType' in:
    build/temp.macosx-10.14-x86_64-3.7/src/lib.o
    build/temp.macosx-10.14-x86_64-3.7/src/pygeom.o

I am not very well-versed in linker intricacies, so I looked around and it seems that the process can be fixed by declaring -fcommon. Not sure whether this is a macOS-only or newer clang problem and if this is the only viable solution, but it worked for me.

Thanks @thomersch  for your report and contribution. Your fix apparently breaks the windows build. I gave this issue another try in #79 , could you checkout that branch and see if it works for you?


clean up styles and move copy-paste from themes to common file

little bit cleaned up styles
will try to rewrite themes with stylus variables usage and so on

this is more than just formatting, eg the following i see introduced in ag-grid.css
.ag-column-moving .ag-cell
     transition: left 0.2s;

the core grid css is not meant to have any styling, just layout or the core grid to work. styling belongs in the themes.

@ceolter like for me it's much better to redefine few styles if you don't use them, then look through theme file and try to find all this .ag-column-moving  but anyway up to you.

at least I advice to add stylus variables for colors, paddings etc. in themes


How add cocoaui to cocoapod ?

How add cocoaui to cocoapod ?
Please give me some advice.

CocoaUI has nothing to do with cocoapod, just download the source code, and compile with Xcode, refer to this doc: http://www.cocoaui.com/docs/quickstart


Add support for multi-character labels

Labels can be more than single characters/unicode codepoints in practice.

Hi, is someone working on this?

Not at this time, no. PRs are welcomed.

Does this support utf-8 characters? I am particularly interested in the line https://github.com/parlance/ctcdecode/blob/7223cc4b308db76e71947f245e1e57ace1a00121/ctcdecode/src/scorer.cpp#L156


Cannot configure the 2023.12.6

Hi.
After update from 12.5 all data became 'Unavailable' with:
[custom_components.dabpumps.dabpumpsapi] Please re-check your username and password in your configuration!
Ok, I removed 12.5 and did a fresh installation of 12.6.
I cannot complete configuration steps now because the last step asks me to choose installation name  without any opton to select.
After the last window closed with X, integration remains not installed.
2024-01-01 19:43:52.287 INFO (MainThread) [custom_components.dabpumps.config_flow] Trying connection... 2024-01-01 19:43:58.447 WARNING (MainThread) [custom_components.dabpumps.dabpumpsapi] Unable to connect to dconnect.dabpumps.com. 2024-01-01 19:43:58.447 INFO (MainThread) [custom_components.dabpumps.config_flow] Successfully connected!

D.

Ran into the same issues while testing, but after a couple of retries I got through it. It is a strange issue, because no code changes were introduced in that part.
I strongly suspect that the problem is mainly with the DConnect.DabPumps.com website at the moment; when I try opening it in a web browser I often get an 'Internal Server Error' page displayed.
Will keep this issue report open for now, and will try to make my code more robust so that setup will not continue when no installation was found.

Improved exception handling where a failed communication will now be retried.
Will be included in the next version (v2024.03.1) that I hope to be able to release later this week.


Carthage SQLite.framework not portable to different systems: CSQLite missing

When I build the framework using carthage everything works as expected locally, but on other systems I get this error:
error: missing required module 'CSQLite'

Rebuilding with carthage on these systems fixes the error, but the framework then does not work on the first system anymore.

+1 for Xcode 8.0 GM

This was with 7.3.1

ah, I actually misread your bug report. weird, is the module loaded on runtime? can you explain what exactly you mean by "on other system"? do you take the compiled framework and include it another app, on a different machine?

We have a project checked in to git including the compiled framework. It is imported using the normal import statement in swift. By my system I meant my computer with my os, my coworker uses his mac.

Same here, I think I misopen my project with Xcode 8, then I open Xcode 7.3, then run the project, error appeared.
header "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator.sdk/usr/include/sqlite3.h" not found
And In Connection.swift
Could not build Objective-C module 'CSQLite'

@lyc2345  There is a tmp fix - You can change your Xcode app name Xcode7.3 to Xcode to solve this issue.

Both our Xcodes where named Xcode.app, still got the error.

fix has been released now (0.11.0). reopen if needed.

This is fixed, thanks.

Any suggestion? I was using this in another project in swift 2.2. Now i am using xcode 8.2 and facing this issue. Nothing helped about it.

Hi, I'm having this problem as of 11 March 2017 using Xcode 8.2.1, SQLite 0.11.2, and Carthage. Ideas?

same issue with @raybradley .

will be fixed once #615 is merged

I'm now seeing this issue using the Swift Package Manager, XCode 8.3.2, SQLite v0.11.3


I18n

linked compliance PR: https://github.com/Solinea/goldstone-compliance/pull/62
updates i18n.

Increases coverage to all known text instances outside of 3rd party libraries such as dataTables and a few d3 legends.
Translates side menu tooltips.

Current coverage is 69.15%

Merging #400 into master will not affect coverage as of 1947bcd

@@            master    #400   diff @@
======================================
  Files           64      64
  Stmts         2597    2597
  Branches         0       0
  Methods          0       0
======================================
  Hit           1796    1796
  Partial          0       0
  Missed         801     801

Review entire Coverage Diff as of 1947bcd

Uncovered Suggestions

+0.66% via goldstone/views.py#30...46
+0.62% via ...stone/drfes/views.py#134...149
+0.43% via ...tone/drfes/models.py#165...175
See 7 more...

Powered by Codecov. Updated on successful CI builds.

:+1:


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>

Codecov Report

Merging #276 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #276   +/-   ##
=======================================
  Coverage   71.42%   71.42%
=======================================
  Files           1        1
  Lines          49       49
=======================================
  Hits           35       35
  Misses         14       14

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 63cd933...2408e3a. Read the comment docs.

Coverage remained the same at 70.588% when pulling 2408e3afed7b59f7608c038a863f9a45ce1fa63c on template-sync-1 into 63cd93327d27242bb8783facc4b50d3ee559e5ca on master.

: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:


Feat/pip mode

Related to:
[iOS] Video starts playing on neighboring cards without video #362
[iOS] Wrong redirect from content, opened through Dates tab #380
[iOS] Add full support for PiP option on iPad #336

Are there any screenshots that can be included or linked here?

Note - I got additional context / detail on this from @volodymyr-chekyrta, no product concerns  or further questions for now, thanks!


[MISC] Add poetry integration

@zmraul don't thank me, Poetry and Ruff did most of the work, I'm just taking credit for that  :joy:


Capture log messages

This fixes log message capturing. I released a prerelease of ZeroLog (v2.1.0-pre1) with the necessary features to make this work. If you see anything else I missed or that could be useful, let me know! Otherwise, I'll release v2.1.0 soon.
Thanks again for this project! 🙂

I noticed that Verify.Serilog and Verify.MicrosoftLogging use the Level: Message output format, so I adjusted this one as well for consistency and brevity.


Possible Bug in QuaRot Implementation with remove_mean_from_embed()

First of all, thank the authors for the awesome work, It really benefits the research of quantization.
https://github.com/ModelTC/llmc/blob/4d31253ff06672612bc850afff7dd5ad41674abe/llmc/compression/quantization/quarot.py#L39
When reviewing the code for LLMC and the original repository of QuaRot, I noticed that the LLMC implementation subtracts the mean of the embedding layer weights in the line mentioned above. However, I did not find any corresponding operation to compensate for this difference. Could this discrepancy lead to variations compared to the original inference without QuaRot?
In most newer large language models (LLMs), such as the LLaMA series, the embedding layer is followed by an RMSNorm layer, which does not perform a zero-mean operation like LayerNorm. I assume the authors might be attempting to split the LayerNorm into a "subtract mean" operation followed by RMSNorm, particularly for models that use LayerNorm after the embedding layer (e.g., OPT).
I am curious about the rationale behind introducing the remove_mean_from_embed function, as I do not recall seeing it elsewhere. This function is specifically called for the QuaRot method. Clarification from the authors would be greatly appreciated. Thanks a lot!

Thanks for appreciating our work.
If the mean of $X$ is not zero, the following equation can't hold.
$$LayerNorm(X) = LayerNorm(XQ^⊤)Q.$$
Because the prerequisite $\Vert QX\Vert =\sqrt{X^⊤Q^⊤QX} =\sqrt{X^⊤X} = \Vert X\Vert$ is for the function $\Vert\dots\Vert$, and can't hold for $Var(\dots)$ where the input is a non-zero mean tensor.
remove_mean_from_embed derives from SliceGPT, and inherits into QuaRot.

Thank you for your response! However, I'm still unclear on when the subtraction of the mean is compensated to ensure the computation matches the original implementation.
From my understanding, the "SliceGPT" paper suggests that subtracting the mean is used to convert LayerNorm to RMSNorm. However, in the LLaMA model series, RMSNorm is applied after the embedding layers.
I agree with you that the remove_mean_from_embed should be called before the layernorms, however, for models that already has RMSNorm followed by embedding layers, I'm not sure whether this operation is necessary. Also, I didnot find the corresponding implementation for the llama2 quantization in the orginal QuaRot codebase.

For LayerNorm, it doesn’t need any compensation. You can find the relative code here.
https://github.com/spcl/QuaRot/blob/main/fake_quant/rotation_utils.py#L45
However, for models, e.g., Llama, I am also curious about why this function need to be used. I have tried to remove it and got the same performance for Llama. If you have the answer, please let me know.

remove_mean_from_embed

Llama does not need this operation, but performing this operation has little effect on the result because llama's embdding mean is small，https://github.com/spcl/QuaRot/issues/7，


How do I get runtime/length of the movie with DiscoverMoviesAsync ?

I got your TMDbLib to work with Visual Studio 2019 VB.Net Winforms.
I just want to drop some short "movies" like Breakdowns of 1936 and so on where actors are not acting in the same movie.

As you can see here: https://developers.themoviedb.org/3/discover/movie-discover
The discover API does not provide runtimes.
You can get this info with GetMovieAsync(id) for each move you find via. Discover.


Allow for puzzles to be replayed

This will require a screen to list puzzles, similar to how our website homepage works

Tracking in #34


H-AD causes a problem with Nightly.

see Bugzilla bug report for info ...  https://bugzilla.mozilla.org/show_bug.cgi?id=1339607

Bug has been marked RESOLVED FIXED now.


MM-15469 (Android) Alert if shared text is longer than message limit

Summary
On Android, one can't manually enter text into the share extension's text box past 4000 characters (the default/defined text size limit). However, this restriction can still be circumvented by sharing a large item of text. In this latter case, the textarea displays just the first 4000 characters, but the value buffer still contains the entire shared text. On hitting "Send", the oversize text can still be posted.
This commit implements MM-15469 to better align the Android sharing user experience with the existing iOS experience.
Bonus: Additional widget to show number of available characters remaining until textarea limit (default = 4000). Similar to iOS experience.
Since a pre-existing i18n string was used (mobile.message_length.message), no additional translations are required.
Ticket Link
https://github.com/mattermost/mattermost-server/issues/11431
Checklist

[x] Has UI changes

Device Information
This PR was tested on: OnePlus 5, Android 9.
Screenshots
Error alert (over share character limit)

iOS (normal) - existing
Android (normal) - new

iOS (past limit) - existing
Android (past limit) - new

@migbot Done!

testing comment

Build Apps for PR label detected. Will generate the app if build succeeds (checks pass and no conflicts with base branch).

Build the App failed. See the logs for more information.

Build the App failed. See the logs for more information.

What does this mean? Anything that I need to do to ensure success?

@chuttan not you, the failure is internal... @@migbot or @cpanato should be able to make it work (at least I hope so, if not I’ll do it)

@enahum alreay sent the logs to @migbot

No need for logs, just to perform the steps ;) I’m<PHONE_NUMBER>00% sure the problem is mattermost-redux not building correctly

Build Apps for PR label detected. Will generate the app if build succeeds (checks pass and no conflicts with base branch).

Android build App: https://releases.mattermost.com/mattermost-mobile-pr/PR-3264/Mattermost_Beta.apk)
iOS build App: itms-services://?action=download-manifest&url=https://releases.mattermost.com/mattermost-mobile-pr/PR-3264/Mattermost_Beta.plist

This or got merged recently https://github.com/mattermost/mattermost-mobile/pull/3349 that changed it as @esethna is suggesting...

Can we add unit tests for this?

I think so. The share extension as a whole didn't seem to have tests with it (not sure), but this would be a good place to start in any case. I'll handle.

Re-adding the dev review label for @enahum's comments

@chuttam how are those unit tests coming up?

Build Apps for PR label detected. Will generate the app if build succeeds (checks pass and no conflicts with base branch).

Android build App: https://releases.mattermost.com/mattermost-mobile-pr/PR-3264/Mattermost_Beta.apk)
iOS build App: itms-services://?action=download-manifest&url=https://releases.mattermost.com/mattermost-mobile-pr/PR-3264/Mattermost_Beta.plist

Thanks @chuttam @esethna
I've tested on Android 9 (Huawei P30 Pro) on the .apk built from this PR and I am not seeing the wording as per Eric's request:

Can we please reword the warning modal to say Message is too long. Character count: xxxx/yyyy.

I am seeing:

I have not tested any further as this will need to be addressed first.

I think the correct working was merged to master so maybe you just need to merge master into the PR

@lindy65 @esethna I see the problem. React Native limits the alert box title to two lines, and this effect is more pronounced on narrower screen devices, which is what you're seeing.
Elsewhere on the Share Extension, we show an alert with a title ("Extension Error") when there's been a problem with sharing, followed a body of text below ("An error has occurred while using the share extension.")
I could apply this pattern to the error message displayed when the user attempts to share text that's loo long. It would look like below:

Acceptable?

@chuttam, that works but then please help update the text:
Title: Message is too long
Body: Character count: xxxx/yyyy
Button: OK

Great. This will now require new i18n strings. I tried to reuse existing ones as much as possible to maintain consistency, but this suggestion feels so much cleaner. I haven't got to the unit tests too @enahum , but shouldn't be a problem to push all new changes out for review real soon.

Here you go, @esethna & @lindy65 . The alert box should now appear like this:

@enahum Unit tests done too. Had to do some mocking gymnastics for parts of the codebase I'm not too familiar with, so please let me know how this could be better.

Build Apps for PR label detected. Will generate the app if build succeeds (checks pass and no conflicts with base branch).

Build the App failed. See the logs for more information.

Build Apps for PR label detected. Will generate the app if build succeeds (checks pass and no conflicts with base branch).

Android build App: https://releases.mattermost.com/mattermost-mobile-pr/PR-3264/Mattermost_Beta.apk)
iOS build App: itms-services://?action=download-manifest&url=https://releases.mattermost.com/mattermost-mobile-pr/PR-3264/Mattermost_Beta.plist

Hi @chuttam @esethna
Thank you! I am seeing the correct warning message "Message is too long. Character count xxxx/yyyy"
However, I am seeing an issue when trying to backspace to decrease the character count so I can make the post. The character count goes from "-xxxx" to 1 and then 2 etc as I continue to hit the backspace/delete key on my keyboard.
Please see attached .gif.  I'm not sure whether this is in the scope of this PR?

You're right, this is pre-existing behaviour where the text box only shows text up to the allowed limit. Consequently, the first 4000 characters are the only text that's available to edit.
I found this a bit odd too but decided to leave pre-existing functionality intact. However now, based on your comment, I removed this maximum text length limitation on the editing text box. Here's the result:

Thanks @chuttam - I'll retest as soon as I have a new app built

Build Apps for PR label detected. Will generate the app if build succeeds (checks pass and no conflicts with base branch).

Android build App: https://releases.mattermost.com/mattermost-mobile-pr/PR-3264/Mattermost_Beta.apk)
iOS build App: itms-services://?action=download-manifest&url=https://releases.mattermost.com/mattermost-mobile-pr/PR-3264/Mattermost_Beta.plist


feat: capitalize navigation when title is not set

Thanks for submitting this. I think this is a good change. I actually had another similar change in mind (mentioned here) but probably better to make that separately.
Will come back to this soon.

Nice. The motivation for this feature is, when the title is the same to the name file, I wouldn’t like to set the title property every time.


Update translations

Wait for Gitian build

A new build of 8b80e5d74fc7ba1f21b2e1c5feb63e656590e8d4 has completed succesfully!
Binaries available at https://build.nav.community/binaries/update-translations-701


isRoboTest never set in matrix_ids.json for Robo Test matrices

Noticed in matrix_ids.json that isRoboTest is never set to true for Robo Test matrices as part of the TestMatrix.Data object.
We currently do result processing and parse through matrix_ids.json for data related to the matrice.

Hi @AaronMT , I'm able to reproduce this issue. I'm looking into it.

Hi @AaronMT, I'm pushing a fix for this issue.


Add Homepage content

Create home page, add markup and content

I would like to fix this issue.

sure👍👍


Fix broken links to oauth2-proxy in the documentation

Description
This PR fixes a couple of broken links in the documentation.

/merge


Fix only zombie spawners can be generated in newly-generated dungeons

I'm not a programmer who masters Java. Sorry.
Now I'm hosting a modded Minecraft server. Players in my server reported that they could not find a  dungeon with a skeleton spawner or the spider one. Only zombie spawners can be found. I set up a server with the same configurations on my own computer and the problem appeared as expected. After removing all mods that the server installed expect SpongeForge, I found out the problem still exists. So this must be SpongeForge's fault.
Then I struggled to manually build SpongeForge with the latest modifications on git. The problem persists. To solve the problem, I had to inspect which part of the code that controls the dungeons' generation. I noticed that the mechanism related to the monster type in dungeons works as normal. However, after the monster type was generated, the monster type was not successfully applied to the mob spawner that was going to be placed in the world. No matter what the monster type is, the mob spawner is always assigned to the zombie one.
Finally, I found the following code might be responsible for this problem. The code locates in the file SpongeCommon/src/main/java/org/spongepowered/common/mixin/core/world/gen/feature/WorldGenDungeonsMixin.java.
@Mixin(WorldGenDungeons.class)
public abstract class WorldGenDungeonsMixin extends WorldGeneratorMixin {

    @Redirect(method = "generate", at = @At(value = "INVOKE", target = "Lnet/minecraft/tileentity/MobSpawnerBaseLogic;setEntityId(Lnet/minecraft/util/ResourceLocation;)V"))
    private void impl$updateDataAndChoices(final MobSpawnerBaseLogic logic, final ResourceLocation mobName) {
        if (((Dungeon) this).getMobSpawnerData().isPresent()) {
            // Use custom spawner data
            SpawnerUtils.applyData(logic, ((Dungeon) this).getMobSpawnerData().get());
            return;
        }

        if (((Dungeon) this).getChoices().isPresent()) {
            // Use custom choices
            final WeightedTable<EntityArchetype> choices = ((Dungeon) this).getChoices().get();
            final EntityArchetype entity = choices.get(logic.getSpawnerWorld().rand).stream().findFirst().orElse(null);
            if (entity == null) {
                return; // No choices to choose from? Use default instead.
            }
            SpawnerUtils.setNextEntity(logic, new WeightedSerializableObject<>(entity, 1));
            return;
        }

        // Just use the given mobName
        logic.setEntityId(mobName);
    }

By commenting the code before logic.setEntityId(mobName); in the method, the problem disappears.
It seems these codes relate to the APIs that the Sponge project provided, which means I must find the root cause of the problem. And here is the modification I made that might solve this problem and with no side effects.

Thanks for spotting this!

https://github.com/SpongePowered/SpongeCommon/commit/adeb48afebf91259fbd9232d82bd21204397cfd2


Feature Request: Add Setting to Show Horizontal and Vertical Scrolling

Hi,
Can you an a setting where the user can enable or disable horizontal and vertical scrolling so that you can reposition so fit the size of the video for those that don't properly resize the video within the popup window?
Also add this to the context menu so one can easily disable and enable in the player's window without going to the setting. Example: Once you reposition the video to fit the window size, you want to disable scrolling using context menu.
Another solution is to enable the user to drag the content to reposition the video to fit the window size.
Thanks.

No. Changing the content of web pages is beyond the scope of this extension.
Note that when the page cannot be embedded, the URL receives a "?floating_player=1" at the end, and thereby you can use the Tampermonkey extension to modify the page based on the URL using javascript or css.
If you need help with any particular website, just tell me so I can try to help you, okay?


Add overlay to flake typescript

This allows the typescript flake to be extended by modifying attributes under __typescriptFlake__.
This gives end users a little more flexibility with how the project / tarball is made.

@szg251 and @bladyjoker if you get a chance, don't be shy about leaving some comments :)


Update boringssl submodule version

This includes several fixes for compiling with old versions of gcc.
This is the same as https://github.com/grpc/grpc/pull/13105 targeting the base grpc repo.
With this change, I was able to successfully run make grpc_cli, and cargo build in grpc-rs.
If you want to minimise the diff from base grpc, I can drop the second commit, which re-generates the Makefile (which grpc-rs doesn't use), and cargo build will still work but make grpc_cli will not.

This PR is not valid anymore.


Introduce gopkg support

Hi,
I'm planning of using your library, but in order to have no future build-issues, I would like to pin versions to avoid the obvious problems. Would you mind creating branches/tags for your releases? The (simple) instructions are on: https://labix.org/gopkg.in
Cheers,
Mark

Sure thing. I added a v1.0.0 tag.
go get gopkg.in/renstrom/fuzzysearch.v1/...

Excellent, thanks!


File conflict to binance-futures-connector-python

There are many file conflics (same path) between this package and the binance-futures-connector-python package. Only one will be retained each if both packages were installed using pip.
Is there any plan to combine the two packages into one? I really don't think it is necessary to make two distinct packages.

I created a same issue in the binance-futures-connector-python: https://github.com/binance/binance-futures-connector-python/issues/197


react-hooks next example with npm package manager is not working

🐛 Current behavior
After scratching my head with the error:
Error: Unable to retrieve InstantSearch's server state in getServerState(). Did you mount the <InstantSearch> component?
I decided to try the next example in this repo and I get the same exact result using npm 8.19.2 and 9.6.2. Using yarn 1.22.17 works fine. Seems like you are relying on references between modules.
🔍 Steps to reproduce

clone your repo
cd examples/react-hooks/next
npm install
npm run dev

Live reproduction
none
💭 Expected behavior
Should probably work
Package version
latest
Operating system
macOS
Browser
No response
Code of Conduct

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

This monorepo uses Yarn, so to be able to use the examples in this repo, you should use Yarn as well. If you copy the example only in a separate setup, like can be done through codesandbox, you can run it with npm too. https://codesandbox.io/s/github/algolia/instantsearch/tree/master/examples/react-hooks/next

This monorepo uses Yarn, so to be able to use the examples in this repo, you should use Yarn as well. If you copy the example only in a separate setup, like can be done through codesandbox, you can run it with npm too. https://codesandbox.io/s/github/algolia/instantsearch/tree/master/examples/react-hooks/next

sure, but moving the examples/react-hooks/next example away from this repo and trying to install it with npm is broken.

I can also confirm that installing the example with npm yields the same error. It appears that the issue begins with the 6.39.0 release. It does not occur when you use 6.38.3.

This is because react-instantsearch-hooks-router-nextjs depends on 6.38.3, resulting in two copies of react-instantsearch-hooks being installed. I'd argue that the yarn behavior is actually incorrect in this scenario.
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>


projbuild_gitconfig.py fails due to the empty _CMAKE_TOOLCHAIN_PREFIX argument

I have noticed that the building(flashing, monitoring) of the system sometimes fails due to the empty TOOLCHAIN_PREFIX argument.
Logs:
Traceback (most recent call last):
  File "<path_to_the_script>/get_projbuild_gitconfig.py", line 25, in <module>
    TOOLCHAIN_PREFIX=sys.argv[6]
IndexError: list index out of range

It is hard to tell when and how this happens, but sometimes it just fails with the same error. I have noticed that the issue won't appear once  fullclean is performed before the build.
Looking at the build.ninja file I have seen that the argument TOOLCHAIN_PREFIX does not exist once the build fails.
I have tried to build the system using the idf.py directly as well as using the VS Code extension shortcuts. Both of them are sometimes failing.
ESP-IDF version: 4.4.3
Operating system: I have used both Linux Ubuntu and Windows 10(same behavior)
Target: esp32
ESP Insights version: 1.0.1
Thank you in advance,
Imer Hamidovic

It is my first time reporting some issue so I am not aware of how to properly do it. Please let me know if you need some more information.

Hi @ImerHamidovic,
When exactly do you encounter this issue? If toolchains are set properly (with . ./export.sh) and you can build the app, you should not get such error.
Did you update the asp-insights recently? If yes, you will need a clean build for this.

Here are some more logs:
[1157/1159] Generating binary image from built executable esptool.py v3.3.2 Creating esp32 image... Merged 25 ELF sections Successfully created esp32 image. Generated <path_to_project_folderbuild/conboard.bin [1158/1159] cd /......../Desktop/WorkingFolder/Schulthess/Projects/Connectivi...ess/Projects/ConnectivityBoard/conboard-esp32/conboard_root/build/conboard.bin conboard.bin binary size 0x16f9c0 bytes. Smallest app partition is 0x1d0000 bytes. 0x60640 bytes (21%) free. [1159/1159] Running utility command for app FAILED: CMakeFiles/app.util  cd <path_to_project_folderbuild && /....../.espressif/python_env/idf4.4_py3.10_env/bin/python <path_to_project_foldermanaged_components/espressif__esp_insights/scripts/get_projbuild_gitconfig.py <path_to_project_folder conboard HW_TEST_BLE_WORKING-54-g461e39b <path_to_project_folderbuild/project_build_config.json /.........../esp/esp-idf && /usr/bin/cmake -D BUILD_DIR=<path_to_project_folderbuild -D PROJECT_DIR=<path_to_project_folder -D PROJECT_NAME=conboard -D PROJECT_VER=HW_TEST_BLE_WORKING-54-g461e39b -D ARCHIVE_DIR=conboard-vHW_TEST_BLE_WORKING-54-g461e39b -D PROJ_CONFIG_FILE=project_build_config.json -D PARTITION_CSV_FILE=partition_table_16MB.csv -P <path_to_project_foldermanaged_components/espressif__esp_insights/scripts/gen_tar_dir.cmake && /usr/bin/cmake -E echo "===================== Generating insights firmware package build/conboard-vHW_TEST_BLE_WORKING-54-g461e39b.zip ======================" && /usr/bin/cmake -E tar cfv conboard-vHW_TEST_BLE_WORKING-54-g461e39b.zip conboard-vHW_TEST_BLE_WORKING-54-g461e39b --format=zip && /usr/bin/cmake -E remove_directory conboard-vHW_TEST_BLE_WORKING-54-g461e39b && /usr/bin/cmake -E remove project_build_config.json Traceback (most recent call last):   File "<path_to_project_foldermanaged_components/espressif__esp_insights/scripts/get_projbuild_gitconfig.py", line 25, in <module>       ##TOOLCHAIN_PREFIX=sys.argv[6] IndexError: list index out of range ninja: build stopped: subcommand failed.


IndexError: list index out of range

hello ， thank you very much for your work. When I run "python eureka.py env=humanoid sample=16 iteration=5 model=gpt-3.5-turbo-16k-0613", it occurs "IndexError: list index out of range". What should I do to run it correctly?

hello ， thank you very much for your work. When I run "python eureka.py env=humanoid sample=16 iteration=5 model=gpt-3.5-turbo-16k-0613", it occurs "IndexError: list index out of range". What should I do to run it correctly?

code_runs = []
rl_runs = []
for response_id in range(min(cfg.sample, len(responses))):  # 确保不超出 responses 列表的长度
if "message" in responses[response_id] and "content" in responses[response_id]["message"]:
response_cur = responses[response_id]["message"]["content"]
logging.info(f"Iteration {iter}: Processing Code Run {response_id}")
# 其他处理代码...
else:
logging.warning(f"Missing or incomplete response at index {response_id}. Skipping.")

@11whitewater  Hi, did you solve that issue? i face the same situation.Traceback (most recent call last):
File "eureka.py", line 115, in main
response_cur = responses[response_id]["message"]["content"]
IndexError: list index out of range


OCPBUGS-32054: PTP HA Profile with event enabled restarts due to concurrent write error

/jira refresh


Add scalar methods.

I added convenient methods to add scalar and multiply by scalars. This is my first open source commit and pull request so if I made some mistakes, please tell me kindly.

I was going to suggest something similar, but I see this is already a PR. Looking forward to it.

Apparently I never found the time to make the additions. Would you be interested in adding the missing features?


clear updated_queue after use.

The queue was never cleared.
@petterarvidsson ready for review

@nsg :+1:

Fixed by #192


proposal: add hooks for any function

Proposal Details
Introduction
This proposal aims to introduce an instrument package to the Go standard library. The purpose of the instrument package is to allow developers to inject custom code at the start and end of any function. This can be immensely valuable for tasks such as logging, performance monitoring, debugging, and other forms of instrumentation.
Motivation
Instrumenting code typically involves manually placing logging or monitoring statements at various points in the codebase. This practice is not only time-consuming but can also lead to cluttered and less readable code. An instrument package would simplify this process by providing a standardized way to insert custom logic before and after the execution of any function. This would result in higher code readability and maintainability while making instrumentation both flexible and powerful.
Proposed Design
The instrument package will allow the users to write custom enter and exit functions that can be applied to any target function. The design is intended to be straightforward and easy to use. Below is an illustrative example of how the proposed implementation would work:
package main

import "instrument"

// onEnterDo will be called at the start of the target function
func onEnterDo(ctx Context) {
	println("enter Do()")
}

// onExitDo will be called at the end of the target function
func onExitDo(ctx Context) {
	println("exit Do()")
}

func main() {
	// Apply instrumentation rules
	instrument.NewRule("net/http", "Do", "*Client", onEnterDo, onExitDo).Register()
}

Is it kind of dynamic proxying ? Or I should say AOP in Java ?

Given Go's compilation model, I don't see how this would feasibly be implemented.

Without a plan for how to actually do the instrumentation, I don't think we can do anything with this proposal.


[fix] [auto-recovery] Improve to the ReplicaitonWorker performance by deleting invalid underreplication nodes

Fixes #21058
Main Issue: #21058

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

Please add a test to cover this change

Addressed

Although ZooKeeper's containerManager exists and automatically deletes empty containers, it is not real-time. If new empty containers arrive while it is working, it cannot delete them promptly.
In a user's production environment, the deletion efficiency of the containerManager is lower compared to the efficiency of creating new empty containers. As a result, there will still be many empty containers present.
The zookeeper leader logs from the customer, it delete the empty node indeed, but there are still a significant number of empty nodes present.
00:04:43.060 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/0128/80b5
00:04:43.066 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/0167/0af7
00:04:43.072 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/00be/02d5
00:04:43.078 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/016a/0375
00:04:43.084 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/016e/0282
00:04:43.091 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/016a/8da8
00:04:43.097 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/0130/0920
00:04:43.103 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/0170/82b0
00:04:43.109 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/0126/8591
00:04:43.115 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/0170/07ba
00:04:43.121 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/0166/8952
00:04:43.127 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/0168/8b7b
00:04:43.134 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/0171/8610
00:04:43.140 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/0170/0047
00:04:43.146 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/0122/843e
00:04:43.152 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/0136/84ed
00:04:43.158 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/016a/059e
00:04:43.164 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/014a/82cf
00:04:43.171 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/00be/02c5
00:04:43.176 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/016f/80e5
00:04:43.182 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/014a/84fb
00:04:43.188 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/00ef/805e
00:04:43.194 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/0166/02b8
00:04:43.200 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/016e/84f7
00:04:43.206 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/00e2/053c
00:04:43.212 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/016e/82b5
00:04:43.218 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/016b/04b6
00:04:43.224 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/0167/8337
00:04:43.230 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/016b/04b5
00:04:43.236 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/00ef/805d
00:04:43.242 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/014a/82c6
00:04:43.248 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/0178/80c3
00:04:43.255 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/0128/0fbc
00:04:43.261 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/0170/0034
00:04:43.267 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/00be/02ab
00:04:43.273 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/010a/0711
00:04:43.279 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/014a/82d3
00:04:43.285 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/016d/8165
00:04:43.291 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/0130/8864
00:04:43.297 [ContainerManagerTask] INFO  org.apache.zookeeper.server.ContainerManager - Attempting to delete candidate container: /ledgers/underreplication/ledgers/0000/0000/00e2/052b


[Event request] Codeunit Gen. Jnl.-Post Line - StartPosting - OnBeforeGetVATEntryLastLineNo

Hi,
we need to set Security Filters on the VAT Entry table, because of the accounting team structure the client has.
The problem is that when we set Security Filters on VAT Entry table the sales/purchase invoice posting is broken, because system cannot get the last VAT Entry Entry No., because the users doesn't have access to whole table.
The problem is here:

Right now there is no option to get access to the VATEntry variable to set property SecurityFiltering to "Ignored".
Could you please expose appropriate event publisher, so we can subscribe, and set the SecurityFiltering property on the VATEntry variable.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 13321.


action invoked with double click

currently single click will open a file. it is very strange for most of the time.

Why double click? Single-click and double click do the same job.

@calidion This is a duplicate of https://github.com/atom/tree-view/issues/199. Please subscribe there for updates. If I'm misunderstanding, please let us know and if you can provide some more details it would be helpful!


[fix][broker] fix metric for delayed memory occupation of sub.

Motivation
There is already one metric called pulsar_delayed_message_index_size_bytes for the total memory occupation used by delayed queue of one topic.
writeMetric(stream, "pulsar_delayed_message_index_size_bytes", stats.delayedTrackerMemoryUsage,
                cluster, namespace, topic, splitTopicAndPartitionIndexLabel);

Whereas, the metric for one sub also called pulsar_delayed_message_index_size_bytes, which do not comform the metric name norm and is confusing.
writeSubscriptionMetric(stream, "pulsar_delayed_message_index_size_bytes",
                    subsStats.delayedTrackerMemoryUsage, cluster, namespace, topic, sub, splitTopicAndPartitionIndexLabel);

Modifications
Rename the metric for one sub to pulsar_subscription_delayed_message_index_size_bytes.
Verifying this change

[x] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[x] The metrics
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

LGTM. However, since it changes the metrics name, I'm not sure if it is OK to merge the PR without a discussion.

WDYT, @lhotari @coderzc

Whereas, the metric for one sub also called pulsar_delayed_message_index_size_bytes, which do not comform the metric name norm and is confusing.

@thetumbled  Does this cause any problem other than it's not consistent with other subscription level metric name?
According to our PIP guidelines, changes like this require a PIP since it would be a breaking change in metrics. However, if this would be a bug where the metric wouldn't be usable at all, then a PIP wouldn't be required.

Whereas, the metric for one sub also called pulsar_delayed_message_index_size_bytes, which do not comform the metric name norm and is confusing.

@thetumbled Does this cause any problem other than it's not consistent with other subscription level metric name?
According to our PIP guidelines, changes like this require a PIP since it would be a breaking change in metrics. However, if this would be a bug where the metric wouldn't be usable at all, then a PIP wouldn't be required.

Currently, it can export metric like:
# TYPE pulsar_delayed_message_index_size_bytes gauge
pulsar_delayed_message_index_size_bytes{cluster="MyPulsar",namespace="public/default",topic="persistent://public/default/testNack-partition-0"} 0
pulsar_delayed_message_index_size_bytes{cluster="MyPulsar",namespace="public/default",topic="persistent://public/default/testNack-partition-0",subscription="sub2"} 0

The metric of topic and subscription mix together. If we want to filter out the metric of sub to pick out the metric of topic, we need to use promsql like:
pulsar_delayed_message_index_size_bytes{subscription=""}
It is quite weird and i believe that if any user use it already, he/she will contribute a pr to fix this, as these label names can only be access by researching the code, which means he/she is an advanced user and is involved in the community.

Currently, it can export metric like:
# TYPE pulsar_delayed_message_index_size_bytes gauge
pulsar_delayed_message_index_size_bytes{cluster="MyPulsar",namespace="public/default",topic="persistent://public/default/testNack-partition-0"} 0
pulsar_delayed_message_index_size_bytes{cluster="MyPulsar",namespace="public/default",topic="persistent://public/default/testNack-partition-0",subscription="sub2"} 0

The metric of topic and subscription mix together. If we want to filter out the metric of sub to pick out the metric of topic, we need to use promsql like: pulsar_delayed_message_index_size_bytes{subscription=""} It is quite weird and i believe that if any user use it already, he/she will contribute a pr to fix this, as these label names can only be access by researching the code, which means he/she is an advanced user and is involved in the community probably.

@thetumbled Please add this directly to the description of this PR since it clarifies the issue. I'd suggest to start a discussion on that mailing list with these details. It's simplest to create a minimal PIP in any case to get this change documented.

Currently, it can export metric like:
# TYPE pulsar_delayed_message_index_size_bytes gauge
pulsar_delayed_message_index_size_bytes{cluster="MyPulsar",namespace="public/default",topic="persistent://public/default/testNack-partition-0"} 0
pulsar_delayed_message_index_size_bytes{cluster="MyPulsar",namespace="public/default",topic="persistent://public/default/testNack-partition-0",subscription="sub2"} 0

The metric of topic and subscription mix together. If we want to filter out the metric of sub to pick out the metric of topic, we need to use promsql like: pulsar_delayed_message_index_size_bytes{subscription=""} It is quite weird and i believe that if any user use it already, he/she will contribute a pr to fix this, as these label names can only be access by researching the code, which means he/she is an advanced user and is involved in the community probably.

@thetumbled Please add this directly to the description of this PR since it clarifies the issue. I'd suggest to start a discussion on that mailing list with these details. It's simplest to create a minimal PIP in any case to get this change documented.

Sure, i will start one to discuss on this change.

Currently, it can export metric like:
# TYPE pulsar_delayed_message_index_size_bytes gauge
pulsar_delayed_message_index_size_bytes{cluster="MyPulsar",namespace="public/default",topic="persistent://public/default/testNack-partition-0"} 0
pulsar_delayed_message_index_size_bytes{cluster="MyPulsar",namespace="public/default",topic="persistent://public/default/testNack-partition-0",subscription="sub2"} 0

The metric of topic and subscription mix together. If we want to filter out the metric of sub to pick out the metric of topic, we need to use promsql like: pulsar_delayed_message_index_size_bytes{subscription=""} It is quite weird and i believe that if any user use it already, he/she will contribute a pr to fix this, as these label names can only be access by researching the code, which means he/she is an advanced user and is involved in the community probably.

@thetumbled Please add this directly to the description of this PR since it clarifies the issue. I'd suggest to start a discussion on that mailing list with these details. It's simplest to create a minimal PIP in any case to get this change documented.

I propose a pip to discuss on this change: https://github.com/apache/pulsar/pull/23789.


Project settings not being applied

When worksheet settings are applied in .sublime-project they are not being applied.
To test: add the Python virtualenv settings from README.md to a project's settings, but change the prefix (and cmd path to the virtualenv python) to have an additional > like so:
"settings": {
    "worksheet_languages": {
        "Python": {
            "cmd": "/path/to/virtualenv/bin/python -i",
            "prompt": [">>> ", "\\.\\.+ "],
            "prefix": "# >> ",
            "error": ["Traceback ", "  File \"<stdin>\","]
        },
    }
}

Then evaluate a Python view and the project specific prefix is not used. This applies to the other settings as well. It also makes no difference if Sublime is started from the shell in an active virtualenv.
This is with ST2 2.0.2, build 2221 on OS X and sublime-worksheet a153ad8972

I can confirm the same.
I've tried using project settings, editing the USER worksheet.sublime-settings, and I even tried unzipping the local worksheet plugin, modifying the base settings file, and rezipping (that removed the plugin from sublime text, unfortunately).
All I want is to change the ruby from irb to use /usr/bin/env irb so that it will pick up my RVM installation instead of System Ruby, which doesn't have the proper gems installed.
Any luck on this settings bug?


Display a better syntax error

Babel syntax error includes the code frame pointing to the place where the error occurred. I think this gives a better feedback to the user about what happened.

thank you.


Error handling with sftp/ftp node

How can we do the error handling with sftp/ftp node. If sftp/ftp is not available, is this node raised error?

It should have been but feel free to submit a PR if you want to modify the code I will accept it. I have not modified this in a long time as I originally wrote for a client that was using SFTP and it is still in use.

SFTP is working fine for me but in case of sftp is not available or incorrect credential, error is not catch by "CATCH" node as node.error does not sent original message.
I want "node.error(err,msg)" change instead of  "node.error(err)"
Thanks

Fixed


[UA-7368] Allow cross domain tracking via link parameter

This PR implements this design to round off our cross-site tracking capabilities. In cases where a customer wants to track a single anonymous browser session across different top-level domain, they can add a query parameter to the outgoing link, which will be picked up by the coveo.analytics.js script on the incoming page, if the following conditions apply:

The parameter contains a valid uuid.
The parameter was created at most 5 seconds ago.
The referring page is present in a preset white list of accepted link referrers, which was set on the receiving page.
If a valid non-expired uuid is detected, and navigation is coming from a whitelisted page, this uuid will overwrite any previously stored uuid and will be valid on the entire toplevel receiving domain.

Implementation notes

The reason for having an expiration on the links is to prevent users from accidentally persisting them in their cache or sending them to others.
The parameter is called cvo_id and is formatted as <UUID>.<secSinceEpoch>. UUID has been stripped of dashes and we're using seconds to save 7 characters in the url.
It's implemented as a plugin to isolate some of the commands on coveoua. Similar to GA design.
I had to restructure and safeguard the plugin architecture a little bit, as the executePlugin command had access to any internal plugin function, not just the public ones.
Referrer are matched using wildcards, so * matches all. *.example.com would match all subdomains under example.com. Empty whitelists will cause nothing to match.
Inclusion of URL type mandated inclusion of nodePolyfills for the browser.
Updated docs and added battery of tests.

Testing notes
You can try this out by creating two arbitrary domains (e.g. in hosts) and forwarding both of them to localhost.

I think the acceptedLinkReferrers should be part of ClientOptions

Had a chat about this with Frank (in person), and apparently it isn't that easy. I still have my reservations about adding the set method, but if it's the only without refactoring a lot, I'm OK with it.

I think the acceptedLinkReferrers should be part of ClientOptions

Had a chat about this with Frank (in person), and apparently it isn't that easy. I still have my reservations about adding the set method, but if it's the only without refactoring a lot, I'm OK with it.

It's possible and sensible to move the storage of this variable to ClientOptions. What is comes down to is how to initialize the list from client code. I'll be either:
coveoua('init',<API_KEY>,{acceptLinksFrom: []}) // list initialized with library initialization

or
coveoua('init',<API>KEY>);
coveoua('link:acceptFrom', []); // list initialized immediately after library initialization

I picked the second one, initially because of the separation of concern. Doc on init can be kept completely devoid from any knowledge on linking. However, I'm also susceptible to Ruben's argument that this list should be fixed on initialization, or you run the risk of timing issues. Happy to take in comments from others.

@fvanham-coveo, @rphilippen no strong opinions on the public api, but when looking at the docs, a dedicated call does feel more in-line with the rest of coveo.analytics.

The docs show examples calling helper methods before init, presumably to avoid races. In this case it's setting context, but in a future cross-domain doc, is could be the referrer list?
The third param to init at least here isan endpoint string. If a ClientOptions object is also supported, it's not mentioned in that section of the docs.


License

Could you specify the license for this code. Thank you.

Hi, thanks for bringing up this issue. Just added an MIT license. Best, Zirui


[v6] ::placeholder & keyframes stripped in production build

Environment
System:

OS: macOS 12.6
CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
Memory: 112.43 MB / 16.00 GB
Shell: 5.2.15 - /usr/local/bin/bash

Binaries:

Node: 16.18.1 - ~/.nvm/versions/node/v16.18.1/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 8.19.2 - ~/.nvm/versions/node/v16.18.1/bin/npm

Reproduction
https://github.com/mAAdhaTTah/sc-issue-4007
Steps to reproduce

Run npm start
Open localhost:3000
See the (correct) green placeholder in the input.
Run npm run build && npx serve build
Open localhost:3000
See the (incorrect) grey placeholder

Expected Behavior
::placeholder works in dev & prod mode.
Actual Behavior
::placeholder is stripped in prod mode.

Hi @mAAdhaTTah can you please use LTS version of styled-components which is 5.3.10.
Also without your code snippet it's hard to understand what you are trying to explain.

@Sambhav399 I can't use the LTS version because I'm trying to upgrade to React 18, which didn't work with v5, hence starting the upgrade to v6.
As for a code snippet, I can try to provide a fuller example (this one doesn't seem to run after exporting from CodeSandbox), but basically I have an input that looks like this. The ::placeholder rule works in development but not production.

Ok, I have a reproduction example in this repo:
https://github.com/mAAdhaTTah/sc-issue-4007
If you git clone, npm i, then npm start, you'll see the site come up with a green placeholder. If you then run npm run build then npx serve build, and load up loadhost:3000, you see the placeholder is back to it's default grey.

hi @mAAdhaTTah It's working fine on my side.
please have a look

Did you test by running npm run build && npx serve build? Cuz this is why I see running it that way:

I have updated the original issue with the reproduction & steps to reproduce, highlighting the difference in behavior between dev & production mode.

I'm also experiencing a keyframes bug in production. I've updated the example to include that issue.

@probablyup Happy to spend some time on this myself or put a dev on this if you're able to give us a lead as to where the issue might be.

Usually when something doesn't work in production but does work locally it's because the CSSOM API rejected a rule we tried to insert. If you put a debugger here you should be able to see the rule as it fails the try block.

That being said, it seems to work with latest SC: https://codesandbox.io/s/styled-components-v6-sandbox-forked-n9bkqn?file=/src/App.tsx

@probablyup CodeSandbox runs in development mode so it won't be reproducible there. I'll take a look at the try/catch block.

@probablyup No, sorry, I got the repro from my actual application, not the repro. I can grab from there if that's helpful.

Here's the errors from the reproduction:
10:31:54.093 emotion-unitless.esm.js:48 inserting rule 0 .kRrqli{padding:4em;background:papayawhip;}
10:31:54.095 emotion-unitless.esm.js:48 inserting rule 1 .jUqIfC{font-size:1.5em;}
10:31:54.095 emotion-unitless.esm.js:48 inserting rule 2 .jUqIfC::-webkit-input-placeholder{color:green;}.jUqIfC::-moz-placeholder{color:green;}.jUqIfC:-ms-input-placeholder{color:green;}.jUqIfC::placeholder{color:green;}
10:31:54.095 emotion-unitless.esm.js:48 error inserting rule DOMException: Failed to execute 'insertRule' on 'CSSStyleSheet': Failed to parse the rule '.jUqIfC::-webkit-input-placeholder{color:green;}.jUqIfC::-moz-placeholder{color:green;}.jUqIfC:-ms-input-placeholder{color:green;}.jUqIfC::placeholder{color:green;}'.
    at e.insertRule (http://localhost:3000/static/js/main.e3e32077.js:2:158684)
    at e.insertRules (http://localhost:3000/static/js/main.e3e32077.js:2:156700)
    at e.insertRules (http://localhost:3000/static/js/main.e3e32077.js:2:160903)
    at e.generateAndInjectStyles (http://localhost:3000/static/js/main.e3e32077.js:2:165899)
    at http://localhost:3000/static/js/main.e3e32077.js:2:167863
    at http://localhost:3000/static/js/main.e3e32077.js:2:167917
    at w (http://localhost:3000/static/js/main.e3e32077.js:2:168066)
    at _o (http://localhost:3000/static/js/main.e3e32077.js:2:63145)
    at ki (http://localhost:3000/static/js/main.e3e32077.js:2:73255)
    at _u (http://localhost:3000/static/js/main.e3e32077.js:2:122321)
10:31:54.099 emotion-unitless.esm.js:48 inserting rule 2 @-webkit-keyframes QuPkj{0%{-webkit-transform:rotate(0deg);-moz-transform:rotate(0deg);-ms-transform:rotate(0deg);transform:rotate(0deg);}100%{-webkit-transform:rotate(359deg);-moz-transform:rotate(359deg);-ms-transform:rotate(359deg);transform:rotate(359deg);}}@keyframes QuPkj{0%{-webkit-transform:rotate(0deg);-moz-transform:rotate(0deg);-ms-transform:rotate(0deg);transform:rotate(0deg);}100%{-webkit-transform:rotate(359deg);-moz-transform:rotate(359deg);-ms-transform:rotate(359deg);transform:rotate(359deg);}}
10:31:54.099 emotion-unitless.esm.js:48 error inserting rule DOMException: Failed to execute 'insertRule' on 'CSSStyleSheet': Failed to parse the rule '@-webkit-keyframes QuPkj{0%{-webkit-transform:rotate(0deg);-moz-transform:rotate(0deg);-ms-transform:rotate(0deg);transform:rotate(0deg);}100%{-webkit-transform:rotate(359deg);-moz-transform:rotate(359deg);-ms-transform:rotate(359deg);transform:rotate(359deg);}}@keyframes QuPkj{0%{-webkit-transform:rotate(0deg);-moz-transform:rotate(0deg);-ms-transform:rotate(0deg);transform:rotate(0deg);}100%{-webkit-transform:rotate(359deg);-moz-transform:rotate(359deg);-ms-transform:rotate(359deg);transform:rotate(359deg);}}'.
    at e.insertRule (http://localhost:3000/static/js/main.e3e32077.js:2:158684)
    at e.insertRules (http://localhost:3000/static/js/main.e3e32077.js:2:156700)
    at e.insertRules (http://localhost:3000/static/js/main.e3e32077.js:2:160903)
    at e.inject (http://localhost:3000/static/js/main.e3e32077.js:2:163959)
    at xt (http://localhost:3000/static/js/main.e3e32077.js:2:165055)
    at http://localhost:3000/static/js/main.e3e32077.js:2:165146
    at Array.flatMap (<anonymous>)
    at xt (http://localhost:3000/static/js/main.e3e32077.js:2:165118)
    at e.generateAndInjectStyles (http://localhost:3000/static/js/main.e3e32077.js:2:165756)
    at http://localhost:3000/static/js/main.e3e32077.js:2:167863
10:31:54.099 emotion-unitless.esm.js:48 inserting rule 2 .GZzXb{display:inline-block;-webkit-animation:QuPkj 1s infinite;animation:QuPkj 1s infinite;}

Can also confirm that adding window.SC_DISABLE_SPEEDY = true; before the JS loads functions as a workaround for now.

Ah, I see. The vendor prefixed styles are supposed to be inserted separately, will look into it.

Could y'all try<EMAIL_ADDRESS>and let me know how it goes? It's this PR on top of main https://github.com/styled-components/styled-components/pull/4021

Nvm I found some further problematic scenarios... need to spend more time on it

I'm kind of stuck due to some stylis behavior... basically the way stylis's prefixer works in v4 is the vendor-prefixed styles get stringified together into a lump instead of being emitted as separate discrete rules. This by itself is not hard to work around, but when you add wrappers like @media queries things get complicated based on the way things get binned.
@Andarist if you guys figured out a workaround for this would love to know. I see emotion pinned the prefixing engine to an earlier iteration but I suspect you'll have the same issue as CSSOM injection time if multiple prefixes are in the same committed rule?

what exact call throws in the browser? what exact arguments are being passed to the browser API? in Emotion we wrap insertRule with try/catch (here) to avoid some problems with unknown pseudo selectors etc. I'm not sure if this issue here is about that though, just skimmed through it - if you could put up a TLDR summary for me... I would appreciate it 😅

Haha sorry, will write up something more cohesive to use moving forward for discussion

This has been partially resolved in RC.3. See the release notes for more info, there's some work that needs to happen on the stylis side for complete resolution.

Fixed in https://github.com/styled-components/styled-components/releases/tag/v6.0.0


import torch fails on P8

import torch fails on P8:
# python
Python 3.8.12 (default, Oct 12 2021, 13:02:29)
[GCC 7.3.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import torch
torch.Illegal instruction (core dumped)

We are not able to import pytorch from OpenCE successfully on P8 from v1.8 onwards (if it has been built on P9), because at https://github.com/pytorch/pytorch/blob/master/cmake/Modules/FindVSX.cmake#L11 the mcpu value is taken from the platform.
Thus if package is built on power9, mcpu=power9 is used.

Building PyTorch recipe on P8 will not lead to this issue.


fix: use win64 version of chromium when on arm64 windows

What kind of change does this PR introduce?
bugfix
Did you add tests for your changes?
not relavant
If relevant, did you update the documentation?
not relavant
Summary
no Win_arm available on storage.googleapis.com yet, and it currently defaults to win32
Does this PR introduce a breaking change?
nope
Other information

I'm getting some unrelated failed checks, and don't see a way to re-run them. Can I get some help?

Are win64 binaries executable on arm64 windows?

Are win64 binaries executable on arm64 windows?

good catch, only as of Windows 11. I'll add that check

should be good now


Fix incorrect cool_mode capability detection

Fixed an issue where cool_mode was incorrectly detected as unsupported

Here's some reference code which the comparison was made against
https://github.com/reneklootwijk/midea-uart/blob/12578ecb4a0dfc75a9c444fbf999a741ea441e66/src/B5_parser.cpp#L61-L91
and
https://github.com/dudanov/MideaUART/blob/3bbd505ee58792a620ad115f9f26652b688f58e3/src/Appliance/AirConditioner/Capabilities.cpp#L115-L142


Fix section editor and tune editor repositioning if off screen

On Linux with my dual monitor (one horiz and one vert) set up, the section and tune editors would appear off screen above my main monitor.

Changed it so that on the first open of the editors, they appear centered relative to the main Maestro jframe
For subsequent opens, they keep their previous position, but first check if the editor window at the prev position is still fully visible across all screens
If not, they will spawn centered relative to the Maestro window again

Cool change. You left a debug print, and no changelog.


[DC-325] Enable UI integration tests on alpha / staging

Remove targetEnvironments and update test for Alpha environment compatibility.

Flack test pass rate
request-access
Snapshots:   0 total
Running tests: 100%
link-to-new-workspace
Snapshots:   0 total
Running tests: 100%
preview-dataset
Snapshots:   0 total
Time:        307.14 s
run-catalog-workflow
Snapshots:   0 total
Running tests: 100%
Note: line 35 in jest-reporter.js is bugged and was commented out.
Error gave:
`Test suite failed to run
TypeError: Cannot read properties of undefined (reading 'forEach')`

Flack test pass rate
request-access
Snapshots:   0 total
Running tests: 100%
link-to-new-workspace
Snapshots:   0 total
Running tests: 100%
preview-dataset
Snapshots:   0 total
Time:        307.14 s
run-catalog-workflow
Snapshots:   0 total
Running tests: 100%
Note: line 35 in jest-reporter.js is bugged and was commented out.
Error gave:
`Test suite failed to run
TypeError: Cannot read properties of undefined (reading 'forEach')`

Note: line 35 in jest-reporter.js is bugged and was commented out. Error gave: `Test suite failed to run
TypeError: Cannot read properties of undefined (reading 'forEach')`

Changing line 35 as
_.forEach(({ message }) => writableStream.write(`${message}\n`), testResult?.console)

may prevent the error.

@slucasbroad Does run-catalog-filter need to be enabled as well?

run-catalog-filter

Note: line 35 in jest-reporter.js is bugged and was commented out. Error gave: `Test suite failed to run
TypeError: Cannot read properties of undefined (reading 'forEach')`

Changing line 35 as
_.forEach(({ message }) => writableStream.write(`${message}\n`), testResult?.console)

may prevent the error.

I filed a ticket for this: https://broadworkbench.atlassian.net/browse/QA-1879
There was a change to stop using _.forEach recently, I would rather have QA look at this than thrash on the code.

@slucasbroad Does run-catalog-filter need to be enabled as well?

This test will need some more changes: https://broadworkbench.atlassian.net/browse/QA-1879


Windows8 fix

Hi,
I fixed a wrong reference of the cordova-X.Y.Z.js file.
I also added a Visual Studio project template metadata file.
I get inspired by this post http://www.infragistics.com/community/blogs/mihail_mateev/archive/2013/01/07/using-phonegap-in-windows-8-store-applications.aspx
I test the template in Visual Studio Express 2012.
Thank you.
Corrado

Thanks for the pull request! However, this repository is outdated and no longer the canonical source. I've updated the README.md to explain where the main projects now live.


Add integration tests for v1beta1 conversion

Description
Changes proposed in this pull request:

Add integration tests for v1beta1 migration and deletion

Related issues

Those have been merged in another PR.


DNS Server Cache Snooping Remote Information Disclosure

We have a special requirement to expose one bosh dns server for access by some other components, those components are not managed by BOSH, so there can't deploy bosh dns, but they need to resolve cf/bosh domain name. But if we expose bosh dns service, we got security alert "DNS Server Cache Snooping Remote Information Disclosure". From this stackoverflow post, seems it can be solved by
Always return a SERVFAIL answer to DNS queries without the recursion desired bit set, UNLESS acting as an authoritative DNS server. This avoids a potential route to cache snooping.
Is it possible for bosh dns to apply the similar solution to avoid this disclosure? Thanks.

@luan When will you publish a new release for bosh-dns-release which contains the fix? Thanks.

We're working on releasing a new feature so this should be released shortly after this release marker here.

no-op closing this as a bosh-dns-release has been cut since.


Uncaught TypeError: Cannot read property 'x' of undefined in Round. This was working in previous version.

I have a component that was using this animation-component fine in previous versions, however we've done a recent upgrade which has broken it.
This is aframe 0.5.1 /Animation component 3.2 and was working fine.
https://jsfiddle.net/qzox15w5/1/
Upgraded to aframe 0.7.1 and Animation component 4.x
https://jsfiddle.net/jpvsrnq1/1/
Problem is here
    const positionAnimation = {
        property:     'position',
        from:         this._threeElement.position,
        to:           (reversed) ? this._initialPosition : **this._targetPosition,**
        dur:          2000,
        easing:       'easeInOutCubic',

        startEvents:  ['---non-existent-event---'], //Avoid auto-play of the animation
    }

This is a Vector3 that aframe is trying to round.  I tried round = false but that's not helping.
Get this error
three.js:3040 Uncaught TypeError: Cannot read property 'x' of undefined
at round (three.js:3040)
at d (aframe-animation-component.min.js:1)
at M (aframe-animation-component.min.js:1)
at aframe-animation-component.min.js:1
at Array.map ()
at S (aframe-animation-component.min.js:1)
at aframe-animation-component.min.js:1
at Array.map ()
at aframe-animation-component.min.js:1
at Array.map ()
I've tried on stackoverflow but it does appear to be a bug.
I tried using AFRAME.utils.clone which does get the correct values but isn't helping me.

AFRAME.utils.clone does get the correct values and is helping me.


JSS: Instead of extending with CSS specificity, extend via JS.

A Node creates a stylesheet and associates it with it's associated element. A Scene extends Node and creates a new stylesheet (new class name) and adds that class name next to what the base Node class already adds, and the Scene's style is supposed to override the super Node's style (the style should have higher specificity).
... But, it's hard to manage CSS specificity because classes can be added and removed in arbitrary order (and Scene or Node styles cleaned up in arbitrary order).
So, instead of dealing with CSS specificty, which morphs when styles are attached in the wrong order, let's just extend styles on the JavaScript side with good ol' object inheritance. Then the order will never matter!

Completed in fc5dea5551f8cdaf4d448a2e70c3b697ea598204


Example hello-world-mistral-curl Run status: failed with no reson for failure

Example hello-world-mistral-curl Run status: failed with no reson for failure,

Below is the output
{"id":"61d9cb05-989b-4b48-b520-xxxxxxxxx","object":"","created_at":1704030934,"thread_id":"cefa085b-263e-4e3c-a1c5-62699fxxxxxx","assistant_id":"65b76ee5-6223-4383-ae65-d23eecxxxxxx","status":"failed","required_action":null,"last_error":null,"expires_at":null,"started_at":null,"cancelled_at":null,"failed_at":null,"completed_at":null,"model":"","instructions":"Please solve the equation.","tools":[],"file_ids":[],"metadata":{}}
Can we get more reasons of failure in the output and how do we debug these failures ?

How do we get the run-id? Is it the output "id" from Step 5: Run the Assistant ?

Hey sorry for the delay, didn't get notified

Thanks I'll try to reproduce. Need to implement more error handling, should be an easy task

It seems to be a run output so the "id" is the id

hey i implemented #46 (better errors) and fixed the tutorial (there was an issue with the model url due to being in the host from the container child)
sorry for this, let me know if you have other issues, happy to help!


Excluding Libraries

Is there any possibility that there could be a setting added to, say, the config file, where we could tell bw_plex to exclude a specific library?
Like, lets say we only want the TV shows processed: no movies, no personal videos, etc. etc. Should that not be an easily-obvious option?

It not possible to exlude based on sections. As for movies just disable check_credits, create_edl etc. You can also exclude based on ratingkeys.


IF condition is ignored if test teardown was fail intentionally by Fail keyword

Why is a test status keeped like PASS if really the test status is PASS but we intentionally fail it by Fail keyword in teardown?
robotframework = 4.0.1
os = win 10
python = 3.7.9
*** Settings ***
Documentation      ...

*** Variables ***

*** Test cases ***
Some Test Case
    Should Be True    ${TRUE}
    [Teardown]    Test Teardown

*** Keywords ***
Test Teardown
    Log    ${TEST_STATUS}
    Fail
    Log    ${TEST_STATUS}
    IF    '${TEST_STATUS}' == 'FAIL' or '${TEST_STATUS}' == 'SKIP'
        Some needed operations
    END

Looks like the root cause is the ${TEST_STATUS} isn't updated in case the Fail was called in test teardown.
Though it looks pretty ok for me, actually test is pass, but the teardown is a fail really.

Yep, looks like so, so I have edited report.
Also, the gray state of IF is misleading - as if it was not executed at all. Shouldn't it be red if the condition is not true?

Yeah, the problem is that ${TEST STATUS} isn't updated if teardown fails. We have #2078 about that but no concrete plans when/if it will be fixed.
Un-executed IF/ELSE branches are gray by design. They aren't executed so they cannot really get PASS, FAIL or SKIP status.

Big thanks!!! I understood about variables.
And don't understand why IF is not executed only if condition is false?

How IF can not be exexuted if it is executed and does some work like Run Keyword If?

IMHO

With IF branches possible statuses and associated colors are:

NOT RUN (gray), when condition isn't true.
PASS (green), when condition is true and the executed branch passes.
FAIL (red), when condition is true and the executed branch fails or when evaluating the condition fails with an exception.
SKIP (yellow), when condition is true and there's a skip in the executed branch.

As you can see, there's a clear difference between NOT RUN and PASS statuses. This won't change.
Run Keyword If is a keyword. It can also have same statuses and colors but semantics are slightly different:

NOT RUN (gray), when the keyword isn't executed at all e.g. due to an earlier failure.
PASS (green), when the keyword is run and passes. This includes both the situation where the condition isn't true and the underlying keyword isn't run at all and the situation where the condition is true and the underlying keyword succeeds.
FAIL (red), when the keyword is run and fails. This includes both the situation where the condition is true and the underlying keyword fails and the situation where evaluating the condition fails with an exception.
SKIP (yellow), when the keyword is run, the condition is true, and the executed keyword causes a skip.

You'd probably get a better idea why colors with IF are what they are with an example with multiple branches where there's no failure. In such a case having only the executed branch in green when others are gray makes it easier to see what branch actually was run while still having all possible branches visible in the log file. Try, for example, running this example:
*** Test Cases ***
Example
    IF    1 < 0
        Log    Not executed
    ELSE IF    1 == 0
        Log    Executed
    ELSE IF    1 > 0
        Log    Executed
    ELSE
        Log    Not executed
    END

Big thanks for more explanation. I just more was wanted to get why status semantics are different between IF and Run Keyword If. We started to use IF instead the keyword recently and need to get used to that.
The example with multiple branches was more than descriptive.


Remove npm test from the prepush hook

After having worked with the prepush hook for some time I find it a bit annoying. When releasing a new version I have to wait for the tests to complete 5 times:

pushing master to my local mirror
pushing --tags to my local mirror
pushing master to github
pushing --tags to github
npm publish

I think it would be enough to run the tests one on prepublish. Because that’s what we care about – avoiding a broken release. And as for tests upon every push – that’s what travis is for, isn’t it?

:+1: yep. Was annoyed by this too.

:+1:
P.S: Gentelmen do contribute to npm-scripts ;)


Weekly Plays are off for last.fm

I haven't familiarized myself with how you are getting the weekly plays yet. However, I did notice that the numbers are wildly high as of late.

Yeah, this needs to be looked into. I've been crazy busy lately but I know
I haven't listened to thousands of song in the past week. Perhaps it has
something to do with the new last.fm redesign?
On Thu, Aug 27, 2015 at 6:19 PM, Elliot DeNolf<EMAIL_ADDRESS>wrote:

I haven't familiarized myself with how you are getting the weekly plays
yet. However, I did notice that the numbers are wildly high as of late.
—
Reply to this email directly or view it on GitHub
https://github.com/lukemiles/api.me/issues/9.

That's a definite possibility, especially considering the notification at the top regarding how they're migrating data. Not a huge deal, just something I noticed.

That's probably it. I'll look at the raw API data, but what the API seems to be returning doesn't reflect the website at all.


Feature/saving ideas in concept

Description
Added migration to add publishedDate field to the ideas table
Added migration to update all old plans with a publishedField value equal to their creation date
Changed onlyVisible to only return ideas that are in concept when created by yourself or if you are an admin.
Please include
Is a dependency of https://github.com/openstad/openstad-frontend/pull/359

Changed all ocurences of publishedDate to publishDate, will test tomorrow if everything still works and will give a sign if everything is ok


issues: Support getting an Issue from an IssueRef

Adds support for getting an issue by ID directly.

thanks @grahamc . I want to give you a heads up hubcaps is going through a decent sized refactor to switch to using async futures interfaces. if this change doesn't make it in a release before that gets finished, it will definitely be included in the larger refactor.

Cool, thanks! No worries. I’ll use my branch for now :). Thanks for an
excellent lib, the NixOS PR bot @grahamcofborg is based on it.
On Sun 19. Nov 2017 at 19:48, doug tangren<EMAIL_ADDRESS>wrote:

Merged #93 https://github.com/softprops/hubcaps/pull/93.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/softprops/hubcaps/pull/93#event-1349003510, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAErrEapmcVW-v2kXPjBOgadX9ewbaOyks5s4MxlgaJpZM4Qjkdo
.

awesome sauce. pushed up a WIP pr to help who where this lib is going here for the most part Result<Foo> -> Future<Foo> but there are a few things that didn't translate directly. I'll try to capture them all in the CHANGELOG once I get something in working order