autocast/orb-toggle

see
Also allow setting cast-mode to autocast.

As of dodekeract/manta-config-engine@5adb4be3e00da64521f012285c0821452ac6803a only the UI needs to be updated.

Fixed as of @537185f5c67cbc3364aa3f7c47b070b2cb73103c


Lost my wallet passphare

The problem that you wish to solve
Dear sir, I have lost my passphare because of lost my android phone and I have created new wallet but my 627 pi already mainnet in wallet so, please give me solution how to recover my old passphare to transfer the mainnet pi in new wallet..
Description
Please give the options to forget the passphare to recover the wallet pi
Implementation suggestions
No response

This issue has been previewed on Pull Request. To Resolve,
Contact the Support page to resolve your error.
Note: you can also initiate a chat with the live agent on the chat button to get more information about your request via Live Chat
@Shiv15399

Still no improvement in my wallet
Sir, pls check and synchronisation my wallet old and new both .
On Tue, 20 Aug 2024, 21:24 ACCmaintenance, @.***> wrote:

This issue has been previewed on Pull Request. To Resolve,
Contact the Support page https://livecustomers-support.web.app to
resolve your error.
Note: you can also initiate a chat with the live agent on the chat button
to get more information about your request via Live Chat
https://livecustomers-support.web.app
@Shiv15399 https://github.com/Shiv15399
—
Reply to this email directly, view it on GitHub
https://github.com/cardano-foundation/cardano-wallet/issues/4745#issuecomment-2299191547,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BKU62DHGV4FQL4TY2ERBOSTZSNRBPAVCNFSM6AAAAABMZ4QXZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJZGE4TCNJUG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

Sorry, but

cardano-wallet is for the Cardano blockchain, not for the Pi chain
cardano-wallet is not supported on mobile phones
In general, cryptocurrencies require you to remember your passphrase and/or mnemonic — or your funds are lost forever.


Rotation/reflection

Surprisingly, this doesn't seem to be an issue already, but it's frequently requested at this point.

[ ] Rotation by ±90°
[ ] Horizontal/vertical reflection
[ ] Arbitrary rotation

The first two make sense as part of a selection overlay menu (#184).

I like the UI for rotation that is used in the fabric.js canvas library. It leaves an extra handle hanging out that can be dragged for arbitrary rotation. It also allows for rotating elements in groups and can resolve multiple separate rotations applied to different sub-groupings over time (where the point of rotation changes with different selections), as show in this screen-capture. You can possibly check out their codebase for some inspiration while implementing this feature. If you'd like some help I could probably spend some time working on this.
https://user-images.githubusercontent.com/365366/174153224-a52622ec-62b6-46aa-86ca-c2ebf919043a.mp4


MTL-2080 Ignore sha256sum initrd files

Summary and Scope

Fixes: MTL-2080

Issue Type

Bugfix Pull Request

The rootfs and kernel files search by suffix and in doing so they do not accidentally select sha256 sum files.
The initrd searches by prefix because the suffix could change in the future (if we change compression or format). Since it searches by prefix the search picks up the sha256 sums. This change will ensure those are excluded.
Prerequisites

[ ] I have included documentation in my PR (or it is not required)
[ ] I tested this on internal system (if yes, please include results or a description of the test)
[ ] I tested this on a vshasta system (if yes, please include results or a description of the test)

Idempotency

Risks and Mitigations

Will fix the shellcheck, and cleanup the globbing.

shellcheck fixup was tested thusly:
C02YR1QYLVCJ:~ heemstra$ cat bash.sh
#!/bin/bash

services=(basecamp.service dnsmasq.service nexus.service grok-exporter.service prometheus.service grafana.service)

services=("$(printf '%s\n' "${services[@]}" | sort)")

for service in "${services[@]}"; do
    echo "$service"
done
C02YR1QYLVCJ:~ heemstra$ ./bash.sh
basecamp.service
dnsmasq.service
grafana.service
grok-exporter.service
nexus.service
prometheus.service
C02YR1QYLVCJ:~ heemstra$

shellcheck test snippet:
redbull-pit:~/heemstra # cat test.sh
#!/bin/bash

services=(basecamp.service dnsmasq.service nexus.service grok-exporter.service prometheus.service grafana.service)

mapfile -t services < <(printf '%s\n' "${services[@]}" | sort)

for service in "${services[@]}"; do
    echo "service: $service"
done
redbull-pit:~/heemstra #
redbull-pit:~/heemstra #
redbull-pit:~/heemstra #
redbull-pit:~/heemstra # ./test.sh
service: basecamp.service
service: dnsmasq.service
service: grafana.service
service: grok-exporter.service
service: nexus.service
service: prometheus.service
redbull-pit:~/heemstra #


How to change spacing between different footnotes?

Describe the bug
It seems that I cannot change the spacing between different footnots. I have tried that
<style>
.footnotes-sep {
  @apply mt-10 opacity-10;
}
.footnotes {
  @apply text-sm opacity-75;
  line-height: 12;
  font-size: 10px;
  padding-bottom: 5px;
}
.footnote-backref {
  display: none;
}
</style>

If the line-height is changed, the spacing will not change, like changing it from 12 to 1200.
The footnotes are like the following pictures:

The spacing between two footnote items seems to be too large, it will be very good if there is some way to reduce the spacing, especially when the number of footnote items is large.
To Reproduce
Steps to reproduce the behavior:

Just use the default template from slidev's official website
Add serveral footnotes in any pages of the template
Try to reduce the spacing of footnotes

Desktop (please complete the following information):

OS: Ventura 13.5.2
Browser: Firefox 121.0 (64-bit)
Slidev version: 0.43.15

I think the following CSS can solve this problem.
<style>
li.footnote-item p {
 	margin: 0;
}
</style>


Unity setup instructions

It would be nice if there were instructions for how to add this project to a Unity project. NuGet doesn't appear to be supported.

I managed to get it working by deleting all the folders except "Priority Queue Unity Full" and "Priority Queue" and then dragging the files from "Priority Queue Unity Full" into "Priority Queue" and replacing the existing files. I also had to delete ".Task" from "System.Thread.Task" in several places.
Not sure if this is right but it worked for me.

It's possible to get NuGet working with Unity, but that is outside the scope of this project.  There are other sites for explaining how to do that.


[Tabs] - Component specs

Design Specification Table is missing.
Not enough of examples of header variants as compared to the images in the documentation.
icon color [image] = #6F2C91
icon color [implementation] = black
padding left in tab label after the icon [image] = 12px
padding left in tab label after the icon [implementation] = 0px
padding top in tab label above the icon [image] = 8px
padding top in tab label above the icon [implementation] = 0px
font in tab label [implementation] = Roboto, "Helvetica Neue"
font in tab label [image] = 'open sans semi bold'
Fixed Tab height [implementation] = 46px
Fixed Tab height [image] = 48px
scrollable tabs = no specs
tabs with notifications = no specs

It has been fixed, It will be available in the next release.


Support deafult .editorconfig

Would be great to have a default .editorconfig (eg stored in .config/Atom) which will be used if the project .editorconfig is absent.

Duplicate of #14


upstart no longer available on ubuntu

forever-service tries to use upstart instead of systemd

I am having the same issue

I think its duplicate of this issue
https://github.com/zapty/forever-service/pull/72


Provide examples of spatial data added to PubChem IDs in 2-3 spaces

You can use this as a proxy:
import numpy as np
n = 10000
dims = 2
scale = 1
data = pd.DataFrame(scale*np.random.randn(n, dims), index=np.arange(1, n+1))

Anything I provide will look similar to data, although scale may vary (autoscaling axes of a canvas/plot is probably sufficient here). n may be as high as ~100,000 and I would love to get to a million.  dims is likely to remain equal to 2. Additional columns may contains information about color, transparency, or size, or more likely information that might be mapped to those visual properties.  That information could be categorical (i.e. various strings like odor labels e.g. "grassy") or numeric (e.g. molecular weight or odor probability).
The spatial data could be provided directly (e.g. as a csv file) by me, or in a more exciting use case the model that produces it is retained (e.g. pickled) and a method of that model can be applied to generate the spatial data for any input list of CIDs.


chore: Add Docker setup and configuration files

Summary
Briefly describe the purpose of this PR.
This pull request introduces the setup and configuration files for Docker to streamline the development and deployment process. It includes Docker files for both the frontend and backend, as well as necessary configurations for building and running the application in isolated containers. Additionally, the PR ensures that the application can be easily deployed with consistent environments across different systems.
Description
This pull request introduces a complete Docker setup for the project, aiming to streamline the development, testing, and deployment processes by containerizing both the frontend and backend services. Additionally, it includes configuration for auxiliary services such as MongoDB and Redis to improve the scalability and maintainability of the application.
Problem Being Solved:
Inconsistent development environments across different developers' machines, leading to potential bugs that arise due to differing configurations.
Difficulty in replicating the production environment locally, which affects the testing process.
Managing and coordinating multiple services such as MongoDB and Redis, which can be challenging without proper isolation.
Approach Taken:
Docker Setup for Frontend: A Dockerfile has been created for the React-based frontend. It sets up a clean environment with all necessary dependencies, ensuring consistency across systems.
Docker Setup for Backend: The backend, built with Node.js, is containerized using a separate Dockerfile. It installs necessary dependencies and configures the environment for the application to run in isolation.
Multi-Container Docker Setup: Using Docker Compose, we have defined a multi-container environment for the backend, frontend, MongoDB, and Redis. This allows the services to run independently while communicating via Docker networks.
Environment Variables: The .env.docker file ensures that the containerized application can securely use environment variables to store sensitive information like database credentials, API keys, etc.
Automated Docker Engine Installation Script: A script is included that automates the installation of Docker Engine on Linux systems to facilitate easy setup of the development environment.
Technical Details:
New Files:
.dockerignore - Optimizes Docker builds by excluding unnecessary files.
.env.docker - Configures environment variables for the Docker containers.
docker-compose.yml - Defines the services for frontend, backend, MongoDB, and Redis in a multi-container setup.
get-docker.sh - A script to automate the installation of Docker Engine.
Updated Files:
.env.sample - Updated environment variable values to ensure proper connections to MongoDB and Redis.
Frontend Configuration - Modified the API path to point to an external server (backend service inside the Docker network).
Prerequisites
Have you followed all the CONTRIBUTING GUIDELINES?
Summary by CodeRabbit
New Features:
Introduced a new .dockerignore file to optimize Docker builds by excluding unnecessary files.
Added a new environment configuration file for Docker deployment, defining essential variables for application operation.
Implemented a multi-container Docker setup with services for MongoDB, backend, frontend, and Redis.
Updates:
Updated environment variable values in .env.sample for MongoDB and Redis connections.
Modified the API path in the frontend configuration to point to an external server.
Scripts:
Added a script for automated Docker Engine installation on Linux systems

Looks great overall! Here are a few suggestions for improvement:
Docker Setup: The Docker configuration is well-structured. Ensure that the .env.docker file is correctly configured with all necessary environment variables for deployment.
Prettier Formatting: It seems like there are some Prettier formatting issues in the code. Please run Prettier on the staged files to ensure consistent code style.
Documentation: Consider adding a brief README section explaining how to set up and run the Docker containers, as well as any dependencies needed.

Caution
Review failed
The pull request is closed.
Walkthrough
The changes in this pull request introduce several new configuration files and modifications related to Docker and environment settings for a backend application. A new .dockerignore file has been created to optimize Docker builds by excluding unnecessary files. Additionally, a new environment configuration file for Docker deployment has been added, defining essential variables. The .env.sample file has been updated to reflect changes in MongoDB and Redis URLs. A multi-stage Dockerfile for both backend and frontend applications has been introduced, along with a script for installing Docker on Linux systems.
Changes
File	Change Summary
backend/.dockerignore	New file created to specify files to ignore during Docker image builds.
backend/.env.docker	New environment configuration file for Docker with essential variables.
backend/.env.sample	Updated MongoDB URI, Redis URL, and Frontend URL to point to remote servers.
backend/Dockerfile	Introduced a multi-stage Dockerfile for the backend application.
frontend/.env.sample	Updated VITE_API_PATH to point to a remote server.
frontend/Dockerfile	Introduced a multi-stage Dockerfile for the frontend application.
frontend/get-docker.sh	New script added for installing Docker on Linux systems.
docker-compose.yml	Configuration for multi-container Docker application with services for MongoDB, backend, frontend, and Redis.
Assessment against linked issues
Objective	Addressed	Explanation
Introduce Docker configurations	✅
Update environment variables	✅
Optimize Docker build process	✅

🐰 In the land of code, where changes bloom,
A new .dockerignore clears up the room.
With variables set for the backend's delight,
Docker and scripts make everything right.
From local to remote, the paths now align,
Hopping along, our app's ready to shine! 🌟

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
❤ Share
🪧 Tips


ChaCha20 Poly1305 IETF decrypt fails with Invalid MAC (works on libsodium native)

This test works fine while using the libsodium extension, but fails with your awesome compat library.
//SessioKey
$sessionKey = hex2bin("846394900c6c826431361885cfbedf4ec77c44f3022b13e9a7d0200728f0a0e1");

//Encrypted
$encrypted = hex2bin("0ffb01f94450b6803ab9fa5994d4e6242c04ac312c8aae2c8de0effd54a0db9a867ee101bfc5ebb235d734edba3c27f299d81644c1bc7b6ca4802550c29d7b28f10e5f5721bcbad2330337b2b64072fb1ead0de5d4923568c6bae5d1cd6ac528ab4d9fda97fa612ffcac0ad68f79b1578b4f1ea1d241b49aff3c71ca0a6e1c1ede16903136baa3f1c4e38e6e021a697a5fd5fd4f7df199b54c6c");

//Decrypted
$decrypted = sodium_crypto_aead_chacha20poly1305_ietf_decrypt($encrypted, "", "\0\0\0\0PS-Msg05", $sessionKey);

//Encrypt and verify with test data
$reEncrypted = sodium_crypto_aead_chacha20poly1305_ietf_encrypt($decrypted, "", "\0\0\0\0PS-Msg05", $sessionKey);

if($encrypted == $reEncrypted) {
	echo "OK";
} else {
	echo "FAILED";
}

That's interesting. I'm not having any luck reproducing a failure, so I've committed a test case. Hopefully, if there is a bug, Travis CI will find it. https://github.com/paragonie/sodium_compat/commit/74d052857c7478f6f790e90f44cd6ce997f2debe

I am sorry. I forget to give more information. I am using the following PHP version:
php-5.6.30-Win32-VC11-x64

Looks like there are some outstanding issues with 32-bit integers, which the rest of the world no longer uses (PHP 7+ on Windows or PHP >= 5.6 on Linux). This is going to be a fun fix.

I've opened #38 to deal with the bigger issue.
In the meantime, if you upgrade to 7.0, then you'll be able to solve this problem immediately.
D:\temp\sodium_compat>\php\7.0-x64\php.exe vendor\phpunit\phpunit\phpunit
PHPUnit 5.7.20 by Sebastian Bergmann and contributors.

...............................................................  63 / 121 ( 52%)
.........SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS      121 / 121 (100%)

Time: 1.02 minutes, Memory: 22.00MB

OK, but incomplete, skipped, or risky tests!
Tests: 121, Assertions: 782, Skipped: 49.

Thanks for verifying! Unfortunately i need to stick to PHP 5.6 at the moment. (Though I am eagerly following the current ext/sodium merge/licensing discussion for PHP 7.2...)
If think we can close this bug in favor of #38 .
Thanks again!


fix: structured error response

could this work?
Fixes #181.

LGTM. I took the liberty to add some tests and assertions, as well as adding some context to the description for subject token validation failures


python3Packages.seatconnect: 1.1.3 -> 1.1.4

Motivation for this change
https://github.com/Farfar/seatconnect/releases/tag/v1.1.4
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 157530 run on x86_64-linux 1

2 packages built:

python310Packages.seatconnect
python39Packages.seatconnect


Refactored Json conversions to implicit methods instead of objects

Refactored out the need to define Reads and Writes objects. Instead one can just define implicit methods.
Also a lot of implicit conversions are now imported automatically so one could write:
  case class User(id: Long, name: String, friends: List[User])

  implicit def userListReader(json: JsValue): List[User] = listReader(json)
  implicit def reads(json: JsValue): User = User(
    json \ "id",
    json \ "name",
    (json \ "friends").asOpt[List[User]].getOrElse(List()))

Note the Json objects being implicitly converted into the correct types, instead of having to do this manually using json.as[Type].
Also note the pull request lacks conversions for Seq, Arrays, etc.

(conversations = conversions)

My point was that personally I like the current solution ie json.as[Type] as well as toJson better precisely because they are explicit, adding a helper method while leaving the rest of the questionable implicit conversions there still could lead to confusion.

I agree with Peter.

Imho the main point was making functions out of the converters instead of objects.


Add ARC Branding in README

To have a consistent header in all sourceloop packages.
Reference readme: https://www.npmjs.com/package/@sourceloop/cache

:tada: This issue has been resolved in version 2.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


wonderwall set wallpaper

Have Wonderwall installed on Fedora 36 that is using KDE Plasma 5. Can download a wallpaper, but cannot set wallpaper. Continuously get error that notes open an issue. Failed to set Wallpaper using- BackEnd: /home/david/snap/wonderwall/35/.local/share/ktechpit/WonderWall/backends/plasma5 BackTrace:

Currently Plasma back-end is not supported with flatpak and snap installs.


Automatically generate API export specifications for packages

Resolves #19.

Stale experiment, but I'll leave the issue up because I think it still has potential.


New stock mentor page design with social links

New stock mentor page design with social links
XD design: https://xd.adobe.com/view/52f2b514-460d-4431-bbcd-9aaf854e5e34-07a1/screen/c1953ac7-1ef0-42f0-9a77-86b0fb4f3dca/
TEST URLS:

before: https://stock.adobe.com/pages/artisthub/community/stock-mentors
test page: before / after
real page: before / after

@auniverseaway I don't have access to "Request a review" so I'm pinging you here instead :D


Line-height is expected to be bigger so that tags will not overlap in vertical direction

I am so sorry to say that the style of generation is sometimes unfriendly. For example, line-height is expected to be bigger so that tags will not overlap in vertical direction

This may be a problem with docute 😟

Close inactive


Tooltip Show on each day of Contribution Heatmap

The tooltip on the heatmap is not working

Hello @Mridul2820,
i work on this Issue Can you assign it to me ?

Yeah Task is completed
Can I raise PR on October 1st so that our contribution count hectoberfest

Yeah Sure @Diwanshumidha


Validate configuration before starting game

Allow rules to validate configuration.
Input: playerCount, GameConfigs
Output: List of rules, or list of strings that does not allow configuration
DSL Example:
val size = config("size") { 5 }
rule("test") {
    validateConfig { config.get(size) >= playerCount }
}

Example use-cases:

TTT, UTTT, Quixo, and all those kinds of games: m,n,k must be positive
Avalon: If you use Percival, then you must also use Merlin and/or Morgana
Liar's Dice: dice per player >= 1, exactly (or at most?) one of higher X any Y must be set
Skull: skulls >= 1, flowers >= 1
Splendor: maxMoney >= (min cost of starting cards), targetPoints >= 1
Hanabi:

Max clue tokens >= 1
max fail tokens >= 1
if only one card each of rainbow then also rainbow
If rainbow is all colors then also rainbow

Artax: x >= 4 and y >= 4
UR: pieces per player >= 1


Feature/add gain selection

I would like to include gain down-selection into the basic calibration.  In reality this may happen in-camera or at the DL0 level during data volume reduction (it is not yet decided). Nevertheless we need to have an implementation here, so that at least at the DL1 level, there is only a single calibrated image and parameters.
Implementation:

Created classes for GainSelector (base class)

NullGainSelector (will leave both gains remaining)
ThresholdGainSelector (chooses gain based on threshold, defined in a calibration table called gain_selection_table.ecsv in ctapipe-extra)

Created a GainSelectorFactory to allow the user to choose the method
The ThresholdGainSelector has an option to either replace the full waveform with the high-gain one, if the threshold is exceeded, or to only replace samples above threshold (the latter assumes all calibration has been applied such that this will not introduce a discontinuity).  The default is to replace the full waveform, as done in current experiments.

selector = ThresholdGainSelector()
wf, mask = selector.select_gains(cam_id="NectarCam", multi_gain_waveform=waveform)

Where wf is now a single-gain waveform, and mask tells which channnel was used per pixel (if the mode is the default one), or per sample, if the mode is select_by_sample.
Questions/Todos:

This must happen automatically for current MC files... so where should it go? In the CameraR1Calibrator, CameraDL1Calibrator, or CameraDL0Reducer? @watsonjj  do you have a preference?
[ ] write more tests
[ ] insert into calibration chain once the first question is answered.

I imagine the two channels are not both stored in the DL0 level? If not then the selection should definitely occur in either the R1 or DL0 level. Which one out of those depends on if you think the gain selection is something that is more likely handled by the camera teams, or is handled in a common way by the OES. I propose that the R1 calibration is a more appropriate area for it.
Regarding the NullGainSelector, would it not make more sense for it to also return a single-gain-channel waveform, otherwise operations down the chain would not work properly? So I suggest it should return the first channel, as it is mostly going to be used by cameras that do not have 2 gain channels.

is more likely handled by the camera teams, or is handled in a common way by the OES. I propose that the R1 calibration is a more appropriate area for it.

Just checked with Jim and he is advocating for the cameras doing it.  However, due to calibration, there may be special runs where both gains are read out, so R1 should support both cases.

NullGainSelector, would it not make more sense for it to also return a single-gain-channel waveform, otherwise operations down the chain would not work properly? So I suggest it should return the first channel, as it is mostly going to be used by cameras that do not have 2 gain channels

That sounds fine.

I think I'll merge this now, and add it to the R1CameraCalibrator in a separate step, since I have other pieces of the analysis chain to import from Tino's scripts and don't want to break anything yet.


Upgrade dependency of commonmark

Seems commonmark adds some breaking changes in version 0.23.0, and commonmark-react-renderer has been already updated.
Otherwise, a common error as Unknown node type "Header" would raise

Fixed in version 1.2.3 by https://github.com/rexxars/react-markdown/commit/99573fbb281dccebc682bde58849154f57935091


Fortigate command line table entries correction

There was a mismatch of the values for IdP Entity Id and IdP SSO URL, they were switched. Corrected it

@jeevansd,
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Failure with a stacktrace from inside cucumber

It seems I have a too new cucumber or something. When I run the tests, it fails with a stack trace somewhere deep within cucumber itself.
I don't know ruby and I'm not familiar with cucumber much (definitely not with its internals), but if I was to make a guess, I'd say it expects a groups field in some answer which is not being provided. I have cucumber 3.0.1.
Feature: Calling steps within steps

  Background:                                   # features/feature_features/calling_steps.feature:3
    Given a project if I don't already have one # features/step_definitions/project_steps.rs:16
    And the steps                               # features/step_definitions/project_steps.rs:25
      """
        When!(c, "^I get invoked indirectly$", |_, _, ()| {
          panic!("Indirect step got invoked!");
        });

        When!(c, "^I invoke a step indirectly$", |cuke: &Cucumber<u32>, world: &mut u32, ()| {
          cuke.invoke("I get invoked indirectly", world, None);
        });
      """
    Then the project compiles                   # features/step_definitions/project_steps.rs:36

  Scenario: Invoking a step indirectly                       # features/feature_features/calling_steps.feature:17
    When the following feature is executed                   # features/step_definitions/project_steps.rs:50
      """
        Feature: Invoking step indirectly
          Scenario: Invoking
            When I invoke a step indirectly
      """
undefined method `group' for #<Cucumber::StepArgument:0x00005592f4344ba8> (NoMethodError)
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/lib/cucumber/step_match.rb:70:in `block in replace_arguments'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/lib/cucumber/step_match.rb:69:in `each'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/lib/cucumber/step_match.rb:69:in `replace_arguments'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/lib/cucumber/step_match.rb:47:in `format_args'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/lib/cucumber/formatter/console.rb:42:in `format_step'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/lib/cucumber/formatter/pretty.rb:158:in `step_name'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/lib/cucumber/formatter/ignore_missing_messages.rb:11:in `method_missing'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/lib/cucumber/formatter/legacy_api/ast.rb:169:in `print_step_name'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/lib/cucumber/formatter/legacy_api/ast.rb:114:in `accept'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/lib/cucumber/formatter/legacy_api/adapter.rb:580:in `step_invocation'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/lib/cucumber/formatter/legacy_api/adapter.rb:543:in `step_invocation'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/lib/cucumber/formatter/legacy_api/adapter.rb:387:in `print_step'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/lib/cucumber/formatter/legacy_api/adapter.rb:251:in `after_test_step'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/lib/cucumber/formatter/legacy_api/adapter.rb:107:in `after_test_step'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/lib/cucumber/formatter/legacy_api/adapter.rb:31:in `block in initialize'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/event_bus.rb:34:in `block in broadcast'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/event_bus.rb:34:in `each'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/event_bus.rb:34:in `broadcast'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/event_bus.rb:40:in `method_missing'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/test/runner.rb:35:in `around_hook'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/test/around_hook.rb:12:in `describe_to'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/test/case.rb:120:in `block (2 levels) in compose_around_hooks'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/test/case.rb:121:in `compose_around_hooks'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/test/case.rb:26:in `block in describe_to'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/test/runner.rb:19:in `test_case'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/test/case.rb:25:in `describe_to'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/lib/cucumber/filters/prepare_world.rb:12:in `test_case'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/test/case.rb:25:in `describe_to'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/filter.rb:57:in `test_case'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/lib/cucumber/filters/retry.rb:18:in `test_case'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/test/case.rb:25:in `describe_to'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/lib/cucumber/filters/quit.rb:12:in `test_case'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/test/case.rb:25:in `describe_to'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/lib/cucumber/filters/broadcast_test_run_started_event.rb:20:in `block in done'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/lib/cucumber/filters/broadcast_test_run_started_event.rb:19:in `map'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/lib/cucumber/filters/broadcast_test_run_started_event.rb:19:in `done'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/filter.rb:62:in `done'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/filter.rb:62:in `done'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/filter.rb:62:in `done'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/filter.rb:62:in `done'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/filter.rb:62:in `done'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/filter.rb:62:in `done'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/filter.rb:62:in `done'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/test/filters/locations_filter.rb:20:in `done'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/filter.rb:62:in `done'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/test/filters/tag_filter.rb:18:in `done'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/compiler.rb:24:in `done'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/gherkin/parser.rb:37:in `done'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core.rb:32:in `parse'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core.rb:21:in `compile'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/lib/cucumber/runtime.rb:74:in `run!'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/lib/cucumber/cli/main.rb:33:in `execute!'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-3.0.1/bin/cucumber:9:in `<top (required)>'
/usr/bin/cucumber:9:in `load'
/usr/bin/cucumber:9:in `<main>'
error: test failed, to rerun pass '--test cuke'

When I downgrade to cucumber 2.4.0, I get a different error:
     Running target/debug/deps/cuke-5a76953049b7bcad
wrong number of arguments (given 0, expected 1) (ArgumentError)
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-core-3.1.0/lib/cucumber/core/report/summary.rb:8:in `initialize'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-2.4.0/lib/cucumber/runtime.rb:178:in `new'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-2.4.0/lib/cucumber/runtime.rb:178:in `summary_report'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-2.4.0/lib/cucumber/runtime.rb:172:in `report'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-2.4.0/lib/cucumber/runtime.rb:64:in `run!'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-2.4.0/lib/cucumber/cli/main.rb:32:in `execute!'
/usr/lib64/ruby/gems/2.3.0/gems/cucumber-2.4.0/bin/cucumber:8:in `<top (required)>'
/usr/bin/cucumber:9:in `load'
/usr/bin/cucumber:9:in `<main>'
error: test failed, to rerun pass '--test cuke'

What is the „supported“ version?

TL;DR: I've not nothing yet, but here are some links to start looking with.
The intent is to support the latest version. Looking into this error but... man reading cucumber source is painful. Here's where I'm at so far:
group = step_argument.group
from: https://github.com/cucumber/cucumber-ruby/blob/master/lib/cucumber/step_match.rb#L73
def initialize(step_definition, step_name, step_arguments)
from: https://github.com/cucumber/cucumber-ruby/blob/master/lib/cucumber/step_match.rb#L10
result << StepMatch.new(step_definition, name_to_match, arguments)
from: https://github.com/cucumber/cucumber-ruby/blob/88fe6414de548ad84c81c699911b246b8f979abd/lib/cucumber/glue/registry_and_more.rb#L67
The provided "arguments" are supposed to be StepDefinitions.
I diverged from here to just try to find some type that has a group "method" or "value"
https://github.com/cucumber/cucumber-ruby/search?utf8=✓&q=group&type=
... And I came up empty. No method called "group" and no field called "group". I suspect that there may be something serialized (coming from upstream cucumber server?) that has this field. Lack of types in Ruby is really painful.

Yes, that's what I think too.
I had the idea of looking at some other language with a wire server how it does that (spy on it through wireshark), but so far I didn't manage to set anything working up yet.

Hmm. This one fails with the same exact error: https://github.com/cucumber/cucumber-cpp. How probable is it that nobody really uses the wire protocol and it was not tested and it is a bug in cucumber itself?


Passing Variabel to ExportHandler

Hi
Im trying to pass a variable to my export handler. Im using NewExcelFile injections,
public function exportBlangko(BlangkoExport $export, $id)
{
return $export->handleExport();
}
How to pass $id to handlerExport() ??

You'll have to pass variables to the file instance itself, you can implement this yourself very easily with properties and setters:
class BlangkoExport extends ... {

    public $id;

    public function setId($id)
   {
       $this->id = $id;
   }
}

In your handler you now can do $file->idor$file->getId()` if your prefer getters;


{Release} Fix CI issue for release branch

Description

Cherry pick from dev branch:

https://github.com/Azure/azure-cli/pull/21206
https://github.com/Azure/azure-cli/pull/21207
https://github.com/Azure/azure-cli/pull/21230

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

https://github.com/Azure/azure-cli/pull/21206 is a breaking change and should be included in release notes.


Best technique to set up multiple sites?

Most people using this will have more than one website they want to update automatically. What is the best way to set that up with this?
At first, I thought to create a fork for each site we want to run updates on, but GitHub only lets you fork a project once per account. We could use a branch per site, but the site UUID is currently defined in a CircleCI environment variable which carries across all branches. Could that be moved into a file?
Alternatively, does it make more sense to simply clone and spin up a brand new repo? I'd rather it be a fork so that it's easier to pull in updates over time.
Other ideas?

I agree that one repo per site is not scalable. Overall, I think this repo is best understood as a proof of concept that shows visual regression autoupdating can be done rather than a fully packaged solution for large volumes of sites.
That being said, I think an easy/direct way scale up a bit is to make the site UUID/name be a variable passed into CircleCI. Or rewrite just a little more and have a preconfigured list of site names in the repo and instead of curling every hour, curl every minute or so to churn through the list.

Closing this out as the updated CircleCI 2.0 version allows for multiple sites to be updated from one repo and takes advantage of parallel workers.


Adding a tutorial on equivariance

Before submitting
Title: Introduction to Equivariant Learning tutorial
Summary:   It's a tutorial on Equivariant Learning
Relevant references: https://arxiv.org/abs/2205.06217
Possible Drawbacks: The runtime is unfortunately quite long. The thumbnail is a bit rubbish. I'm not totally convinced the seed is really fixed having seen the build here.
Related GitHub Issues:

Thanks for the review @gideonuchehara and for the changes @RDPEast
I'm going to give it a formatting review and read it again!
We will probably mark the demo as finished next week 🚀

Hey @RDPEast !
Now that I'm looking at it, this demo is going to require a little extra work 💪 Normally, every time we update the web page, all the demos are run to generate the outputs. However, there are some demos that take a long time to run and we decided not to run them automatically. In this case, the demo takes 35 minutes to deploy so it would be better not to run it with each update. The main difference is that you have to enter the outputs (either images or text) manually. Here is a link to a demo where this happens. Also you should remove the word "tutorial_" from the name of the demo, since that is the indicator that the code is executed each time. If you have any doubt let me know 😊

@co9olguy Which fixes are you referring to, as far as I can tell I'm accepting most of them?


Make connection bindings work for non Equatable types

Sometimes I need to use a "protocol type" as a prop. Unfortunately, there is an Equatable constraint on the types, that can be used to subscribe/bind.
There fore this is only possible going down the "type erasure road", afaik. But this is just completely overkill for me here.
So I would suggest, adding additional binders without the Equatable constraint, but instead enforce to supply a manual isEqual function. (like you actually do, one step deeper^^)
For testing I just modified the one of the existing binders:
    public func bind<S: Sequence,M>(_ keyPath: KeyPath<Props, S>,
                                    to binder: (Observable<M>) -> Disposable,
                                    isEqual: @escaping (S,S) -> Bool,
                                    mapping: ((S)->M)? = nil)
    {
        let distinctAtKeyPath = self.propsEntry(at: keyPath) { isEqual($0, $1) }

        let afterMapping: Observable<M>
        if let mapping = mapping {
            afterMapping = distinctAtKeyPath.map(mapping)
        } else {
            afterMapping = distinctAtKeyPath as! Observable<M>
        }

        afterMapping
            .bind(to: binder)
            .disposed(by: disposeBag)
    }

What do you think? :-)
If you like it, I can create a Pull request for this, but I just wanted to ask first, before I put more work into this.
Thanks in advance
Martin

Thanks for discussing this first, that's always so much nicer :)
I'm still working on wrapping my head around "type erasure". I didn't run into this problem with ReRxSwift and I'm not sure what causes you to have the problem. I just watched this great talk by Rob Napier: https://www.dotconferences.com/2016/01/rob-napier-beyond-crusty-real-world-protocols. Any solution directions for you in there maybe?
Having said all that, I'm not opposed to adding a variant with an isEqual parameter, as long as everything else keeps working the way it currently does :) In other words: I don't want to require an isEqual parameter...
If you do end up creating a pull request, could you kindly include also unit tests and doc updates? Thanks!

Thanks for your fast answer.
I must admit, protocols are also not my biggest strength, as well ;-)
But afaik it's just not possible to make a protocol conform to Equatable, as it "has Self requirements".
https://stackoverflow.com/a/24890041/2019384
I think there actually is a sense in this, as you don't know what the actual classes/structs that conform to your protocol will look like and you can not really ensure equatability on this (general) level.
However that's why it sometimes is really handy/necessary to be able to use a custom "isEqual"-like function.
I would actually add additional functions for that, without the Equatable constraint, but the custom isEqual closure instead.
Sure, I won't mess in your code too much^^ #docs #tests #code-style

Yeah I recommend watching that video I mentioned if you didn't yet. Rob explains some common architecture patterns that you can use to avoid this problem. And he also mentions that he hopes that the Swift compiler will take care of this for you some day :)

Yea that's a really interessting talk. So basically instead of using these crippled protocols, try generic structs. I'll definitely give it a try. If it doesn't work you'll see a PR in the near future 😉

This is quite a while ago now, so I'm assuming this is no longer an issue. Please reopen if needed.


Added my own ideas

Added the etee tracker to the list of trackers to consider, as well as creating my own .md file which I will keep my own ramblings to.
This communicates further on what I am thinking of, when I think of this project, and what it could do.
Essentially, if we were to re-focus the efforts, not into reverse-engineering the vive wand, but instead the way etee does things, with their separated tracker and controller, we could end up with a more flexible solution that could allow for better customizability.
I do not have enough for FBT and etee's way of doing things, not right now, but we can find out.
So, if you haven't died yet, let's work on figuring this out together!

I think including Etee trackers in the consideration for SteamVR tracked controllers would be pretty neat. Let's see where this goes!


[Feature Request] Change the SVG animation

Existing Component
Yes
Component Name
Loading
Description
Hello. How i change the SVG animation, i want add a custom SVG.
Thanks

Sorry, it's not supported.

@Leopoldthecoder But, how i dot this? need help.. please


In firefox one in two times the oauth login fails cause the popup closes too fast

I'm using Firefox 34.0.5 on Mac OS X Yosemite 10.10.1.
If I'm logged in Facebook and want to use the oauth to login in my web app using torii installed with npm, the first time I get an error that popup was closed.
The second time it is working.
It only happen with Firefox, for Chrome and Safari it is working fine.
This error is consistent, I can repeat it, and it is not only for facebook but also for linkedin and google.
It worked fine in Firefox too, if I add a timeout to the window.close of the popup.
var RedirectHandler = Ember.Object.extend({

      init: function(url){
        this.url = url;
      },

      run: function(){
        var url = this.url;
        return new Ember.RSVP.Promise(function(resolve, reject){
          if (window.opener && window.opener.name === 'torii-opener') {
            postMessageFixed(window.opener, url);
            var winPopup =window;  //this code I added
            setTimeout(function(){ winPopup.close(); }, 500); //this code I added
          } else {
            reject('No window.opener');
          }
        });
      }

    });

Are you aware of this issue? If you need more info ask away.
Thanks

The exception we got was with the message:

Popup was closed or authorization was denied

It could be similar to issue #111

+1 I see the same error happening with my users in Firefox.

Yes, see the exact same behavior.


TopN query with sorting by hyperUnique metric returns badly ordered results

tl;dr Probabilistic algorithms can bite you in the....
Here's our little story.
We are ingesting reasonably large amounts of data in real time (approximately 15k events per second). We are then querying the last week of data, for various, arbitrary intervals varying in length from hours to days.
Among other things, we issue queries structured as follows:
{
    "queryType":"topN",
    "aggregations":[
        {
            "filter":{
                "dimension":"SOME_DIMENSION",
                "value":"some value",
                "type":"selector"
            },
            "aggregator":{
                "fieldName":"UNIQUE_FIELD",
                "type":"hyperUnique",
                "name":"uniques"
            },
            "type":"filtered"
        },
        (some other aggregations),
    ],
    "intervals": (some interval),
    "filter":{
        "dimension":"OTHER_DIMENSION",
        "value":"other value",
        "type":"selector"
    },
    "threshold":100,
    "granularity":"all",
    "dataSource":"very_secretive_name",
    "metric":"uniques",
    "dimension":"KEY_DIMENSION"
}

At some point, we noticed a very strange anomaly in the results returned from Druid. Small percentage (~4%) of our queries returned almost sorted results. For example, they could look like this:
[
    {
        "KEY_DIMENSION":"ID1",
        "uniques":32454.549667124706,
        "other_aggregation": xxxxxxxx
    },
    {
        "KEY_DIMENSION":"ID2",
        "uniques":29738.77111864203,
        "other_aggregation": xxxxxxxxx
    },
    (...)
    {
        "KEY_DIMENSION":'ID12_ANOMALY_START',
        "uniques":13531.402343246148,
        "other_aggregation": xxxxxxxxx
    },
    (...)
    {
        "KEY_DIMENSION":'ID16_ANOMALY_END',
        "uniques":10391.412343246148,
        "other_aggregation": xxxxxxxxx
    },
    {
        "KEY_DIMENSION":"ID14",
        "uniques":20141.402343256151,
        "other_aggregation": xxxxxxxxx
    },
    (...)

Root cause:
I did quite a lot of digging through the inner workings of Druid TopN queries. One particular area that seemed suspicious, was the merge phase, when results from different segments are merged together and sorted, prior to being returned to the caller.
The key observation at this point was that even though we issue almost identical queries ordered by different metrics, the anomaly only ever appears, when sorting by a hyperUnique metric. This pointed me to the implementation of HyperLogLogCollector (io/druid/query/aggregation/hyperloglog/HyperLogLogCollector.java).
Now, I'm convinced, the issue is almost certainly caused by unstable implementation of HyperLogLogCollector.compareTo(). HLL comparator is behaving inconsistently with the order imposed by estimated cardinalities. There are two unit tests verifying precisely that. Unfortunately, they are both too naive to detect such a rare and yet important anomaly.
Steps to reproduce:
Execute test added by https://github.com/DreamLab/druid/commit/3dbb4946ff5b3d838ae6bf738aad69154c52f459 to io.druid.query.aggregation.hyperloglog.HyperLogLogCollectorTest. Find it attached below:
  @Test
  public void testCompareToShouldBehaveConsistentlyWithEstimatedCardinalitiesEvenInToughCases() throws Exception {
    // given
    Random rand = new Random(0);
    HyperUniquesAggregatorFactory factory = new HyperUniquesAggregatorFactory("foo", "bar");
    Comparator comparator = factory.getComparator();

    for (int i = 0; i < 1000; ++i) {
      // given
      HyperLogLogCollector leftCollector = HyperLogLogCollector.makeLatestCollector();
      int j = rand.nextInt(9000) + 5000;
      for (int l = 0; l < j; ++l) {
        leftCollector.add(fn.hashLong(rand.nextLong()).asBytes());
      }

      HyperLogLogCollector rightCollector = HyperLogLogCollector.makeLatestCollector();
      int k = rand.nextInt(9000) + 5000;
      for (int l = 0; l < k; ++l) {
        rightCollector.add(fn.hashLong(rand.nextLong()).asBytes());
      }

      // when
      final int orderedByCardinality = Double.compare(leftCollector.estimateCardinality(),
              rightCollector.estimateCardinality());
      final int orderedByComparator = comparator.compare(leftCollector, rightCollector);

      // then, assert hyperloglog comparator behaves consistently with estimated cardinalities
      Assert.assertEquals(
              String.format("orderedByComparator=%d, orderedByCardinality=%d,\n" +
                      "Left={cardinality=%f, hll=%s},\n" +
                      "Right={cardinality=%f, hll=%s},\n", orderedByComparator, orderedByCardinality,
                      leftCollector.estimateCardinality(), leftCollector,
                      rightCollector.estimateCardinality(), rightCollector),
              orderedByCardinality,
              orderedByComparator
      );
    }
  }

Time to dig deeper:
Closer inspection of the .compareTo method reveals that it uses two optimizations/heuristics (in the following order), before falling back to calculating estimatedCardinality directly:

Comparison of register offsets
Comparison of the number of non-zero registers

To find out, which of those is causing the problem let's take a look at an example output produced by the above test:
java.lang.AssertionError: orderedByComparator=1, orderedByCardinality=-1,
Left={cardinality=13338.797458, hll=HyperLogLogCollector{initPosition=0, version=1, registerOffset=1, numNonZeroRegisters=1970, maxOverflowValue=16, maxOverflowRegister=911}},
Right={cardinality=13610.832917, hll=HyperLogLogCollector{initPosition=0, version=1, registerOffset=0, numNonZeroRegisters=2046, maxOverflowValue=16, maxOverflowRegister=1559}},

Expected :-1
Actual   :1

As you can see, when compared by cardinalities, Right > Left. However, if we apply the optimization 1. and compare registerOffsets instead, we will return a wrong result!
So, we've just empirically proven that optimization 1. should be removed. But, why is it so? And what about 2.. Can we prove that 2. is correct?
Back to basics:
Let's take a step back and consider, what HyperLogLog truly is, at the most basic level. At its core, it's not much more than a harmonic mean of a bunch of numbers.
Suppose we have two sets of integers:
M1 = [5, 5, 5]
M2 = [6, 4, 6]

We shall call integers M1_i and M2_i, registers. We will be calculating harmonic mean of powers of 2, with exponents given by M1_i and M2_i. We also introduce a fancy storage optimization, by storing an additional integer for each of the sets. We call those, register offsets. Now, instead of storing exact values of registers, we can store positive offsets from the register offset:
OFFSET1 = min(M1_i)
OFFSET2 = min(M2_i)
Hence we have,
OFFSET1 = 5; M1 = [0, 0, 0]
OFFSET2 = 4; M2 = [2, 0, 2]

Can we compare H1 and H2 by comparing their offsets?
If yes, then OFFSET2 = 4 < OFFSET1 = 5  =>  H2 < H1. Let's verify this claim:
H1 = 3 / (1 / 2^(5 + 0) + 1 / 2^(5 + 0) + 1 / 2^(5 + 0)) = 3 / (1/32 + 1/32 + 1/32) = 3 / 3/32 = 32
H2 = 3 / (1 / 2^(4 + 2) + 1 / 2^(4 + 0) + 1 / 2^(4 + 2)) = 3 / (1/64 + 1/16 + 1/64) = 3 / 6/64 = 32
Hence,
H1 == H2 !!!

No, we can't.
Can we compare H1 and H2 by comparing the number of non-zero registers?
If yes, then NUM_NON_ZERO1 = 0 < NUM_NON_ZERO2 = 2  =>  H1 < H2
As above, H1 == H2, therefore no, we can't.
Conclusion:
It appears that both optimizations used in the current implementation can't be considered safe and should be removed. I will try to open a pull request soon.
Performance implications:
It's hard to say what impact exactly, will the removal of those two optimizations have on the performance of the comparator (microbenchmarking is currently blocked by #2432). However, my claim is that actually, in the average case, it shouldn't be slower at all, thanks to another optimization implemented in the HLL - caching of estimated cardinalities.

@turu Nice Catch.

This issue wins bug report of the year


Create nko.ts

Description
Simple keyboard layout for N'ko script with all Unicode character included, layout follows Qwerty keyboard layout.
https://unicode-table.com/en/blocks/nko/
Checks

[x] Tests ( npm run test ) are passing

Sorry for the delay, will follow up & merge this PR shortly. Thanks!

thanks, looking forward to using it in projects soon

Thanks for the contribution @kjitteh! The N'ko layout is now live as of the latest version. Feel free to update and check it out.
Regards,
Francisco Hodge

glad to have contributed


restore backup without downtime

nice to have feature since we will probably be restoring only if the app is already not working

This would be an advanced upgrade / downgrade scenario where we spin up a second instance of bestie and switch traffic over


cant install with latest version of cordova

cordova plugin add https://github.com/fastrde/cordova-plugin-fastrde-checkgps.git
Returns exit code 1 failed to fetch plugin via registry, Probabally this is either a connection problem, or plugin spec is incorrect.

Have the same issue. I had to remove it.

it's solved by #5


Unable to open the Namespace Fable.Helpers.ReactToolbox

I think it is because the module itself is marked as internal.
This is in Beta 2.

Yea, that should definitely not be internal anymore. Thanks for pointing this out. Now fixed in beta-3 (57206de87433e0b56684f066ef8c202c795cea92).


b-modal: if okTitle / cancelTitle are given as empty strings, hide buttons

okTitle / cancelTitle might not be present, in this case they have the default values.
I also need to hide one of them, sometimes.
If if okTitle / cancelTitle are given as empty strings, please hide the buttons.
a v-if could be added here? Hoping the default value isn't set when given as empty strings, only when undefined.
https://github.com/cdmoro/bootstrap-vue-3/blob/19513da03986afa4da03198dfaa15f828d7749c5/src/components/BModal.vue#L40

meanwhile you can customize that part with hide-footer
example:
<b-modal id="exampleModal" hide-footer v-model="showModal" size="xl" title="Modal title">
  ...
</b-modal>

I don't know, if you need to hide one of the buttons you could use ok-only prop. For me, if you pass an empty string is a "valid" value, you have to worry about what type of variables you use.

Thanks, will use okOnly


Leak in RCTNetwork module

[x] Review the documentation: https://facebook.github.io/react-native
[x] Search for existing issues: https://github.com/facebook/react-native/issues
[x] Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment
Environment:
  OS: macOS High Sierra 10.13.5
  Node: 6.11.1
  Yarn: 1.6.0
  npm: 3.10.10
  Watchman: 4.9.0
  Xcode: Not Found
  Android Studio: 2.3 AI-162.4069837

Packages: (wanted => installed)
  react: 16.3.1 => 16.3.1
  react-native: 0.55.4 => 0.55.4

Description
A simple fetch call like the one below is enough to make various parts of RCTNetwork pile up references and memory allocations via malloc and etc. When I say pile up, what I mean is that every GET call is actually malloc-ing and retaining some data that never goes away. Simulating a low memory warning in Instruments also doesn't seem to get these references garbage collected away.
Reproducibility: 100%
  setInterval(() => {
    fetch('https://facebook.github.io/react-native/movies.json')
      .then((response) => response.json())
  }, 1000)

Screenshot 1

Screenshot 2

Screenshot 3

Screenshot 4

Some of the more obvious locations that I observed to be leaking:

RCTNetworkTask.m - There seems to be a retain cycle in the completionBlock
RCTNetworking.mm
RCTHTTPRequestHandler.mm

TLDR: I'm not too familiar with the inner workings with RCTNetwork but the memory allocation seems to suggest that something funky is going on with the completionBlock which is leading to the retention of these references.
This is also a continuation of the conversation we had in #19169. @oNaiPs, you might be interested in this. 😄
Reproducible Demo

Clone this basic RN project @ https://github.com/yinghang/react-native-leak
Profile app with Instruments using Allocations
Watch RCTNetwork related references pile up

cc a couple folks that show up in the blame for the networking modules
@javache @nicklockwood

Pretty sure I'm seeing this on RN0.56 as well, though for some reason it's not showing up in the Allocations tool mentioned in the issue. System Monitor shows the memory usage grow to 1400 MiB and the device log shows the kernel sending the process a SIGKILL due to the hard memory limit being reached. Once, the app crashed on an NSMallocException in RCTNetworkTask.m.
So far I've been able to largely alleviate the issue by getting rid of the Promise.race that wraps my fetch call. Not sure to what degree I've been successful yet.

I've opened #20352 for my issue. It turns out downloading a specifically-formatted tiny JSON file can cause a much bigger memory leak.
Separately, I'm definitely able to confirm that OP's issue is still occurring in 0.56.0. The memory leak is much smaller, but still significant.

Will this be fixed by https://github.com/facebook/react-native/pull/19333?
https://github.com/facebook/react-native/commit/122b3791ede095345f44666691aa9ce5aa7f725a

Not too sure, will def give it a try when I have time.


Add dependency logic to store migrations

I'll remove dependency logic and add a code comment instead ..


Please make the releases also available as Zip files

Tar is not available on Windows without loading extra 3rd party libraries. Please make releases in .zip format as well.
Thanks

@lulf this can be done easily I think


Update validations of Spark/FlinkProcessor and FeatureView

What is the purpose of the change
This PR updates the validation logic of Spark/FlinkProcessor and FeatureView.
Brief change log

Update Flink/SparkProcessor to report error when processor config conflict with native.* config
Introduce class to keep track of built-in functions
Validate features order in Sliding/DerivedFeatureView
Fix #119

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

Thanks for the update. LGTM. @lindong28 could you please take a look at this PR?

@lindong28 Thanks for your review! I updated the PR accordingly. Could you please take another look?

Thanks for the update! LGTM.


When starting the app, a call must be done to update sets

We don't wont an empty list of sets to be displayed.

Sets must not be loading at each start of the app. Only one time at the very beginning of the database.


Add module version constant

add crud.VERSION (_crud.VERSION) constant to make possible to determine module version in runtime.
I didn't forget about

[ ] Tests
[X] Changelog
[X] Documentation

Closes #240

NB: https://github.com/tarantool/graphql/pull/53#issuecomment-1093446929

Closed by #342


[BUG]

Describe the bug
A clear and concise description of what the bug is.
Modmail system relais from the wrong destination
To Reproduce
Steps to reproduce the behavior:

Go to open a thread with someone
Click on answer in a voice channel chat

Expected behavior
A clear and concise description of what you expected to happen.
Ignore the message in the voice channel chat
Please complete the following information

OS: [e.g. iOS]
Version [e.g. 22]
Python Version
Package Versions

Additional context
Add any other context about the problem here.

fixed in #57


New version: SuiteSparse_GPU_jll v5.10.1+2

Autogenerated JLL package registration

Registering JLL package SuiteSparse_GPU_jll.jl
Repository: https://github.com/JuliaBinaryWrappers/SuiteSparse_GPU_jll.jl
Version: v5.10.1+2
Commit: 6bb650d081a9236fe1eed8305572bc953e3e6552
Revision on Yggdrasil: https://github.com/JuliaPackaging/Yggdrasil/commit/99b076321ab5bbc87b8dfbb39ba33aaa3bb04da6
Created by: @ViralBShah

@maleadt This is just a rebuild of the same thing before, with no changes. Seems like you had to manually fix the compat bounds in https://github.com/JuliaRegistries/General/pull/76773/commits/cde1d9fbe52df0afc35d54ac32d7f866be222ffa
@giordano Would you know what is generating the incorrect bounds in the first place?

Would you know what is generating the incorrect bounds in the first place?

Changing compat bounds in a build version bump. Pkg has lots of troubles with build numbers, and so does the registry.

We don't really need bump anyways. But I didn't change any compat bounds, I believe.

We don't really need bump anyways. But I didn't change any compat bounds, I believe.


Tech debt: add from __future__ import annotations in the Parser models feature

Why is this needed?
Reference: https://github.com/aws-powertools/powertools-lambda-python/issues/4607
Add from future import annotations to all files, including examples
Which area does this relate to?
Static typing
Suggestion
No response
Acknowledgment

[X] This request meets Powertools for AWS Lambda (Python) Tenets
[ ] Should this be considered in other Powertools for AWS Lambda languages? i.e. Java, TypeScript, and .NET

Closed as complete.


Models refactor and update tools

This PR includes:
https://github.com/ipa320/ros-model/pull/26
https://github.com/ipa320/ros-model/pull/27
https://github.com/ipa320/ros-model/pull/28

I have tested creating components and ROS system from scratch.
Everything is working properly except the "Add new Component from ROS node" button, which needs further modifications.

@ipa-swk can you please test again? I fixed the  "Add new Component from ROS node" problem to work as said here: https://github.com/ipa-nhg/ros-model/blob/Refactor/docu/NewComponent.md
(This is basically the old version I already had. However this will be improved with a cleanest solution soon https://github.com/ipa-nhg/ros-model/tree/NewCI )

Tested and it works fine!


Tests on the react function with not an equatable or hashable Control.

Hi @kzaher , I've written some tests on feedbacks react function.
If they are okay, I will cover with similar tests other overloads of this function (Equatable and Hashable).

Hi @ixrevo ,
I've merged your PR, there were a couple of smaller things I've had to fix before merging it.

If you can add the rest of tests, that would be great.


Adding detection of '%+' and '+%' whitespace syntax

As of at least version 2.9.x, it is possible to use {%+ and +%} as tag delimiters to disable the lstrip_blocks option's behaviour, but this was not being searched for.

Excellent, thanks for the pull request!


Add wrappers for missing h3ron-sys bindings

A few methods are not available in the h3ron crate but are available in the C bindings h3ron-sys.

h3Line
h3LineSize
getBaseCell
etc

I can try to make a PR with the implementation if this is too much work

I implemented the wrappers for the line-functions a few days ago (in 282e474959f94c1f2d45c7e92385a67e0a4528fd), getBaseCell is in b5438af44a97acd997e1d57d6c67446488e08fbb.
I just did not do an release yet. Just have a look in the master branch if you are missing anything. PRs are of course welcome ;)

Thank you !


Digital Miner incorrectly mining "Lava Rock" from GeoStrata with Silk Touch

Hi, just wanted to report what happened when I put these two mods together in my pack. I ran a digital miner to see the amount of ore in a certain area, and to my surprise this appeared
Now, I've talked to Reika before posting here, and from his reply I get that he cannot do much on this, so I thought maybe you could fix this :)
There's not an issue with the collection of the block itself, but it should always be obtained with a metadata value of 0 (the block that looks like lava with a little bit of stone in it). All other variants should be transformed to that. This can be replicated by using picks both with and without a Silk Touch enchantment.

Oh, I just noticed that gfycat cropped the recording at 15 seconds. There's a part missing where I mine all 4 blocks in the chest with a pickaxe enchanted with Silk Touch, then with a regular one. In every case the block is returned as the more red one, with a metadata value of 0.

That's strange. I'm afraid there's not much I can do about this- I pass all the necessary information to blocks before they are destroyed. If I find a way to solve this later I'll definitely take another look :)

So, with that you mean there's a way a mod can say "hey, this block shouldn't be mined" or "hey, mining this block should always give this"?

When a block is defined, the modder can specify the block's drops. Making a block unbreakable is also possible.

Hmm, how odd that actual silk touch pickaxes do drop the correct block... Maybe I should try the Digital Miner without Silk and see if the same happens...


Remove experimental code

This PR reverts the changes in #11433 that are beyond reordering.

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

Does it work?

@yang-g I ran tools/run_tests/run_tests.py -l c++ -r "grpclb_end" -n inf for ~20 mins, the flakiness increases from 0.13% to 0.18% (without new flakes) after this PR.

@AspirinSJL Thanks. How about other (non grpclb) tests?

@yang-g I haven't run other tests. Should I run some or all?

@AspirinSJL These two lines were added because they seemed to reduce test failure rates. I guess looking at all the tests to see whether any new test failures pop up is a good idea.

@yang-g Yeah, that makes sense. Running tools/run_tests/run_tests.py -l c++.

@yang-g I've also submitted an internal global test for this change.

Please also run with -l c

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

Already removed.


v2.1.0 Release Checklist

Includes OOT Intel GPU driver release for RHOCP 4.14.0 and above
Checklist:

[x]  Update dockerfile with the latest driver release - I915_23WW51.5_682.48_23.6.42_230425.56. Release Notes here
[x]  Build and validate driver container for 4.14.0 OCP using KMM
[x]  Driver signing
[x]  Update release notes, root readme (if required), release readme table
[x]  Preflight certification scanning and publish image on RH catalog
[x]  Cut release on github

released - https://github.com/intel/intel-data-center-gpu-driver-for-openshift/releases/tag/v2.1.0


[Tutorial Docs] Changing PostAuthor userId property to consume a userId as opposed to a user

name: :book: New/Updated Documentation Content
about: Adding a new docs page, or updating content in an existing docs page
PR Type
Does this PR add a new page, or update an existing page?
Update
Checklist

[ ] Is there an existing issue for this PR?

link issue here

[x] Have the files been linted and formatted?

What docs page is being added or updated?

Section:
redux/docs/tutorials/essentials

Page:
part-4-using-data.md

For Adding New Content
n/a
What kind of content category is this page (tutorial, how-to, explanation, reference)?
tutorial
Who is the intended target audience?
new redux users
What knowledge are we assuming they have?
generic routing practices with regards to parameter passing
What are the intended results or takeaways from reading this page?
Best practice on generic routing practices with regards to parameter passing
What is the most critical info they should learn?
see above
For Updating Existing Content
What updates should be made to the page?
change holding user as a user object to userID
Do these updates change any of the assumptions or target audience? If so, how do they change?

Hey, appreciate the PR.  Not sure if this is going to be correct, though.  The examples need to match the app source code.  Is this fixing an error where the examples don't match the source, or is this trying to rename the fields to indicate to the reader that "this is an ID, not an object"?

I haven't gone through part 5 yet but after a cursory review it doesn't like it would break anything - i can report back shortly to confirm this.
It is more of a description change than an error, as there are a few cases where there is a mapping of user : userId which could be avoided if they were one in the same - in renaming the fields it makes more sense by using id to indicate the type of (lookup) relationship, as opposed to the reader thinking its the object itself.
I think its also important because this could be extended to where the the author component would make an API call to get the latest user info and compare it, which would also rely on the userId

@timdorr
There's a 3rd commit here - https://github.com/reduxjs/redux/pull/3963/commits/f46f65535ea6a78d43ae68820ca1801351bf66fd
Please let me know if you want me to make a separate PR for that?

@timdorr  / @markerikson
Although I agree with my suggestion, because of the API used in the subsequent tutorial page, this will be a breaking change.
The 2 options then would be

leave a not in existing doc commenting on why its user and not userId, in that its needed for a future API
accept the proposed change and then we would also have to make additional changes on the next page as well, effectively reverting this change

obviously the first option seems easier, if desired 👍


Update grpc version

This is a part of effort for #37.

Current coverage is 98.48% (diff: 100%)

Merging #38 into master will not change coverage

@@             master        #38   diff @@
==========================================
  Files            11         11
  Lines          1189       1189
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1171       1171
  Misses           18         18
  Partials          0          0

Powered by Codecov. Last update 5ff79c3...d1bb475

LGTM

LGTM


feat(trtexec_vendor): add vendor package for trtexec

Description
a vendor package for trtexec
Related links

Tests performed
Please check if you can build tensorrt engine from onnx file with trtexec
colcon build --cmake-args -DCMAKE_BUILD_TYPE=Release  --symlink-install --continue-on-error --packages-up-to trtexec_vendor lidar_centerpoint
source install/setup.bash
trtexec --onnx=$(ros2 pkg prefix lidar_centerpoint --share)/data/pts_backbone_neck_head_centerpoint.onnx --shapes=spatial_features:1x32x560x560 --saveEngine=$(ros2 pkg prefix lidar_centerpoint --share)/data/pts_backbone_neck_head_centerpoint.engine --buildOnly

Notes for reviewers

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[x] There are no open discussions or they are tracked via tickets.
[x] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

If you plan to release this package, I think it's better to manage this package in a separate repository and add it to build_depends.repos.
@wep21 Could you tell me your thought about it?

I won't make this package released because ros build farm cannot handle cuda libraries.
I will create a separate repository if it is preferable.

@wep21 I see, thanks!
Considering that CUDA is only used in autoware.universe, I feel it's reasonable to manage this package in this repository. :+1:

I have checked that almost the same performance is reproduced using engine files built with the following trtexec command.
trtexec \
    --onnx=$(ros2 pkg prefix lidar_centerpoint --share)/data/pts_voxel_encoder_centerpoint.onnx \
    --saveEngine=$(ros2 pkg prefix lidar_centerpoint --share)/data/pts_voxel_encoder_centerpoint.engine \
    --shapes=input_features:40000x32x9 \
    --optShapes=input_features:40000x32x9 \
    --workspace=1024 \
    --fp16 \
    --buildOnly

trtexec \
    --onnx=$(ros2 pkg prefix lidar_centerpoint --share)/data/pts_backbone_neck_head_centerpoint.onnx \
    --saveEngine=$(ros2 pkg prefix lidar_centerpoint --share)/data/pts_backbone_neck_head_centerpoint.engine \
    --shapes=spatial_features:1x32x560x560 \
    --optShapes=spatial_features:1x32x560x560 \
    --workspace=1024 \
    --fp16 \
    --buildOnly

@wep21 @yukke42
For me build failed.
But when I add below in cmake file, it works.
  if(${TENSORRT_VERSION} VERSION_EQUAL 8.2.2)
    set(TENSORRT_VERSION 8.2.1)
  endif()

--- stderr: trtexec_vendor
[ 11%] Performing download step (git clone) for 'tensorrt-populate'
Cloning into 'tensorrt-src'...
fatal: invalid reference: 8.2.2
CMake Error at tensorrt-subbuild/tensorrt-populate-prefix/tmp/tensorrt-populate-gitclone.cmake:40 (message):
  Failed to checkout tag: '8.2.2'

make[2]: *** [CMakeFiles/tensorrt-populate.dir/build.make:92: tensorrt-populate-prefix/src/tensorrt-populate-stamp/tensorrt-populate-download] Error 1
make[1]: *** [CMakeFiles/Makefile2:76: CMakeFiles/tensorrt-populate.dir/all] Error 2
make: *** [Makefile:84: all] Error 2

CMake Error at /usr/share/cmake-3.16/Modules/FetchContent.cmake:915 (message):
  Build step for tensorrt failed: 2
Call Stack (most recent call first):
  /usr/share/cmake-3.16/Modules/FetchContent.cmake:1006 (__FetchContent_directPopulate)
  CMakeLists.txt:41 (fetchcontent_populate)

---
Failed   <<< trtexec_vendor [7.48s, exited with code 1]


Create test.yml

Even though the build is broken (due to changes in luau-ast), I'm going to merge this so that future PRs can unbreak the build.


Page Query Returns long string instead of metaInfo Title

Description
A query for the title of a page does not return the page but a long random string.
Steps to reproduce
create a new gridsome project. Head to the playground, query:
  allPage {
    slug
    title
  }

Expected result
title in the object should equal what's listed in meta info. aka About Us
Actual result
A long random string is returned.
    "allPage": [
      {
        "slug": "posts",
        "title": "eece9165dcac65fbf3a9ec45e4e7d854"
      },
      {
        "slug": "index",
        "title": "be19209865d1080b24679f9f34f803f3"
      },
      {
        "slug": "about",
        "title": "f965356798034b782b9ae752a852689d"
      }
    ],

Environment

Libs:
- gridsome version: 0.5.5
- @gridsome/cli version: 0.8.0

The GraphQL layer doesn't have access to the state inside Vue components, unfortunately. We could solve it by having a custom <front-matter> block with yaml in each single file component in order to show more information about the pages in the schema, but that is up for discussion.

I'm confused about why title is an option to query off of for a page.
I was thinking it matched up to https://gridsome.org/docs/head#add-head-meta-data-to-pages--templates for some reason. Probably just because there was meta info like page title in the schema.

I understand that it's confusing :) At the beginning of this project, we had an idea about having a good overview of pages in the schema that could be used for creating menus etc. But we didn't get that far because other parts of the API was prioritized. I hope we are able to improve it in the following weeks.


Update View Components article

The View Components article is a bit dated and could use an update:

Rework the intro text
Review with @rynowak and update accordingly

Overview

A View Component renders a chunk of output for a view
View components can have parameters and business logic
Typically invoked from a layout page

How to define a view component

Create a class that inherits from ViewComponent or ends with the suffix ViewComponent or has a ViewComponentAttribute.
Write a Invoke or InvokeAsync method that returns an IViewComponentResult

Typically initialize a model and pass it to a view by calling the View() method on ViewComponent
View search paths:

By default the view name is Default.cshtml, search paths are Views/<controller_name>/Components/<view_component_name>, Views/Shared/Components/<view_component_name>
Ex. HomeController, TagCloudViewComponent -> search paths are Views/Home/Components/TagCloud, Views/Shared/Components/TagCloud

Support ctr injection - link to DI

Fixes https://github.com/aspnet/Docs/issues/868


Preview file tree inside zip folder from Preview Pane (without navigating inside the archive

Description of the new feature / enhancement
Currently, with Peek we are able to preview the contents of a zipped folder without actually opening it (navigating inside of it).  However, it is not possible to view the same simply by selecting the zip file (in File Explorer) without actually navigating into the archive.
To illustrate:
Zip Archive Previewed in File Explorer:

The very same Zip Archive Previewed in Peek:

Scenario when this would be used?
Currently to view the files contained within an archive we have two options, we can either:

navigate into the zip, browse the files, then navigate back out;
select the zip file, open Peek browse the files, then close Peek

I propose that File Explorer's preview pane be extended to usee the same preview handler that Peek uses to display the file tree contained with an archive.
Supporting information
No response

/dup #13805


Application Extension Name

Hey I would recommend changing the extension name because omni is reserved for NVIDIA Application or Extensions.

Hi @JenNVIDIA
The name of the extension was changed in the latest version [0.2.0] available since 2022-05-21 :)


Can't install vagrant subutai box on Mac OS

Steps to reproduce:
Use VMWare Fusion
Install vagrant subutai box

File download error. Connection closed
This is network issue. Please try again.

Successfully started the subutai box installation on windows:

Done:

Successfully installed on Linux:


ultralytics yolo support for tracks

Summary

https://github.com/cvat-ai/cvat/issues/8645
Adding support for tracks for Ultralytics YOLO formats. All of them can now import annotations with track_id present, and have an option to export with track_id
How to test

Checklist

[ ] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues

License

[ ] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[ ] I have updated the license header for each file (see an example below)

# Copyright (C) 2022 CVAT.ai Corporation
#
# SPDX-License-Identifier: MIT

Summary by CodeRabbit

New Features

Added support for optional track IDs in YOLO format annotations.
Introduced a command line option to control the inclusion of track IDs during export.

Bug Fixes

Enhanced error handling for invalid annotation fields related to track IDs.

Tests

Added tests to verify functionality for track ID handling in both conversion and import processes.

Please add PR description and update the changelog

done


Allow the user to send a new invite to an external email address

Invite sent to an email bound to the external instance has an expiration date.
We should allow the user to send a new invite. Presently the application refuses to create a new direct chat.
I suggest leaving the pending direct chat and create a new one...

Available on Btchap only

revoke the pending invite before leaving the existing discussion


TableContainer background

Default bg colour for Table Container + fix Select bg

Might close this one off for now, given it's starting to show its age 👴🏻


add sleep to allow server to start

This deflakes the windows "h2_http_proxy_nosec_test.exe connectivity"
test. The reason why is unclear.

test this please

I'd rather not start down the path of adding arbitrary sleeps to cover bugs.
If this were accompanied by 'this covers identified problem X which is tracked by bug Y' then it's a different story. (where identified problem is more than 'test Z is flaky' but more a 'iocp based poller misses wakeups in circumstance A, B, C')

No longer needed.


Database management cleanup

See individual commit messages for details

Spotted more stuff to do, closing while I add it


Could not find module active-model-adapter

I tried upgrading to 1.13.6 but now my tests fail.  I'm on Ember 1.13.7, ED 1.13.8, and Ember-cli 1.13.8.
Here's what I'm seeing:
    at Object.TestLoader.require (http://localhost:4200/assets/test-loader.js:31:14)
    at Object.TestLoader.loadModules (http://localhost:4200/assets/test-loader.js:21:18)
    at Function.TestLoader.load (http://localhost:4200/assets/test-loader.js:40:24)
    at http://localhost:4200/assets/test-support.js:6647:16: Could not find module `active-model-adapter` imported from `ember-data-factory-guy/factory-guy`@ 1 ms
Source:
Error: Could not find module `active-model-adapter` imported from `ember-data-factory-guy/factory-guy`
    at requireFrom (http://localhost:4200/assets/vendor.js:119:13)
    at reify (http://localhost:4200/assets/vendor.js:106:22)
    at mod.state (http://localhost:4200/assets/vendor.js:149:17)
    at tryFinally (http://localhost:4200/assets/vendor.js:30:14)
    at requireModule (http://localhost:4200/assets/vendor.js:148:5)
    at requireFrom (http://localhost:4200/assets/vendor.js:121:12)
    at reify (http://localhost:4200/assets/vendor.js:106:22)
    at mod.state (http://localhost:4200/assets/vendor.js:149:17)
    at tryFinally (http://localhost:4200/assets/vendor.js:30:14)
    at requireModule (http://localhost:4200/assets/vendor.js:148:5)```

I'm seeing the same thing running 1.13.6, with Ember 1.13.7 and ED 1.13.8

same here

hmm .. yeah .. that is a bummer .. I think what happened was in v1.3.6 ( which was created from merged PR ) the active-model-adapter was included in package.json ( of ember-data-factory-guy) so it's not really imported by npm when you install factory guy, which means I kind of messed that up.
Give me a few days to work that out and use v1.3.5 till I get that sorted out.

Absolutely!  Thanks for your amazing and super-helpful work!

@mminkoff, can you try v1.3.7 and see if this fixes the issue for you. I think it does, but want to verify.

looks all clear here @danielspaniel - thanks!


@conda-forge-admin, please add user @gmarkall

Additional comment:
No response

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added user @gmarkall in conda-forge/ptxcompiler-feedstock#24.


Define system property aliases for the configuration properties

Define property names for the configuration properties to allow specifying them by means of -D, setting properties, or pom properties.

/integration-test

Integration tests have been started. Please click here to see the status.

/integration-test

Integration tests have been started. Please click here to see the status.

/integration-test


add support for Elixir language

Please add support for the Elixir language, which has Ruby-like block syntax:
# when split
def function(arguments) when condition do
  body
end

# when joined
def function(arguments) when condition, do: body

Thanks for your consideration.

I've pushed a commit that implements function splitting. Bear in mind that I don't have any elixir experience, so if I've messed something up (or there's an edge case I've missed), please let me know :).

Wonderful! :+1: We need to adjust the regexps to look at do...end blocks only, because Elixir gives us the same choice between one-line do: ... syntax and multi-line do ... end syntax for all  of its keywords (not just def).  For example:
# when split
defmodule Foo do
  bar
end
if hoge do
  piyo
end

# when joined
defmodule Foo, do: bar
if hoge, do: piyo

Thanks for your consideration.

It's not a problem, I just pushed a commit that adds if and defmodule, but I don't know if there are any more. Do you have a full list of all of these keywords? I took a quick look at the documentation, but I couldn't see an exhaustive list of reserved keywords.

Yes, there are more (search for "def" on this page: http://elixir-lang.org/docs/stable/elixir/Kernel.html) but the problem is that users can define their own macros (which take such do..end blocks) as well.  So I would advise that we just look for do..end blocks (i.e. with "do" at the end of a line, regardless of what keyword the line begins with) and just perform the splitjoin operations. :sunglasses:

Here is a diff that demonstrates my suggestion:
diff --git a/autoload/sj/elixir.vim b/autoload/sj/elixir.vim
index 8ad2160..398c644 100644
--- a/autoload/sj/elixir.vim
+++ b/autoload/sj/elixir.vim
@@ -1,5 +1,5 @@
 function! sj#elixir#SplitDef()
-  let function_pattern = '^\s*\%(defmodule\|def\|if\) \%(\k\+\).*\zs,\s*do:'
+  let function_pattern = ',\s*do:'
   let line             = getline('.')

   if line !~ function_pattern
@@ -15,7 +15,7 @@ function! sj#elixir#SplitDef()
 endfunction

 function! sj#elixir#JoinDef()
-  let function_pattern = '^\s*\%(defmodule\|def\|if\) \%(\k\+\).\{-}\zs\s*do\s*\%(#.*\)\=$'
+  let function_pattern = '\s*do\s*\%(#.*\)\=$'
   let def_lineno       = line('.')
   let def_line         = getline(def_lineno)

Seems reasonable and it seems like it works fine. If we eventually add more elixir definitions, we may have to revisit this one so there are no conflicts, but for now this looks good to me :).
I've pushed the change to master. Could you check it out and let me know if this works alright?

:+1: It works well, thanks. :bow:


KAFKA-12342; Merge RaftClient and MetaLogManager interfaces and remove shim

This patch removes the temporary shim layer we added to bridge the interface differences between MetaLogManager and RaftClient.

Reverse dependency between :raft and :metadata modules.
Consolidate handleResign and handleNewLeader APIs into single handleLeaderChange API
Move MetadataRecordSerde into :metadata
Update listeners to use BatchReader which takes disk reads out of the Raft IO thread
Delete MetaLogRaftShim, MetaLogManager, and MetaLogListener

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

cc @jsancio

This PR was moved to https://github.com/apache/kafka/pull/10705. @ijuma @cmccabe  feel free to close this PR.


OpenAI callback is deceiving when used with Azure OpenAI

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Description and Example Code
Langchain seemingly computes token usage and cost for both OpenAI and AzureOpenAI models using OpenAICallbackHandler. However,  that relies on the fact that both the APIs retrieve the "complete" name of the called model, which is not the case in Azure OpenAI.
In my subscription I have 3 deployments of gpt-3.5-turbo corresponding to gpt-35-turbo-0613, gpt-35-turbo-0312, gpt-35-turbo-1106 and 2 deployments of gpt-4 corresponding to gpt-4-1106-preview and gpt-4-0613. However, when calling them for inference, the model is called, respectively gpt-35-turbo and gpt-4 regardless of the version. Langchain can't compute the correct cost then, despite no warning is thrown. This dictionary here also contains entries that would never be used because of the above, e.g. this one.
from langchain_openai import AzureChatOpenAI

llm1 = AzureChatOpenAI(
        api_version="2023-08-01-preview",
        azure_endpoint="https://YOUR_ENDPOINT.openai.azure.com/",
        api_key="YOUR_KEY",
        azure_deployment="gpt-35-turbo-0613",
        temperature=0,
)

llm2 = AzureChatOpenAI(
        api_version="2023-08-01-preview",
        azure_endpoint="https://YOUR_ENDPOINT.openai.azure.com/",
        api_key="YOUR_KEY",
        azure_deployment="gpt-35-turbo-0312",
        temperature=0,
)

messages = [
    (
        "system",
        "You are a helpful assistant that translates English to French. Translate the user sentence.",
    ),
    ("human", "I love programming."),
]

llm1.invoke(messages).response_metadata['model_name'] # gpt-35-turbo
llm2.invoke(messages).response_metadata['model_name'] # gpt-35-turbo

System Info
Not applicable here.

You need to use the parameter model_version to get the correct pricing information


feat: support importing CommonJS from ESM files

Summary
Luckily importing CJS from ESM should use the normal require caching mechanisms, so we can just hook into the code we already have for this.

Test plan
E2E test expanded with new test cases.

Codecov Report

Merging #9842 into master will decrease coverage by 0.07%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #9842      +/-   ##
==========================================
- Coverage   64.52%   64.45%   -0.08%
==========================================
  Files         290      290
  Lines       12325    12336      +11
  Branches     3048     3052       +4
==========================================
- Hits         7953     7951       -2
- Misses       3732     3744      +12
- Partials      640      641       +1

Impacted Files
Coverage Δ

packages/jest-runtime/src/index.ts
60.00% <0.00%> (-1.30%)
:arrow_down:

packages/expect/src/utils.ts
94.96% <0.00%> (-1.26%)
:arrow_down:

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 3681cca...1c6555b. Read the comment docs.


v1.5.1

Changes:

Add flatpak as a build target (https://github.com/la-jarre-a-son/midi-jar/issues/14) - NOTE: this does not provide Flathub submission, and may never go to Flathub
Use a published fork of nlf<EMAIL_ADDRESS>to ensure no issue with dependencies (https://github.com/la-jarre-a-son/midi-jar/issues/20)
Disables autoupdate as it is not working probably due to app not being signed (https://github.com/la-jarre-a-son/midi-jar/issues/22), replaced by a modal with a link to the release
Removes M and maj in chord notation for major chord (https://github.com/la-jarre-a-son/midi-jar/issues/23) - this was misleading
Fix Chord not being ordered correctly - omissions should be before inversion, BUT omission+inversions should be after inversions with no omission (https://github.com/la-jarre-a-son/midi-jar/issues/24)
Reopen window with last state for maximized, alwaysOnTop and path (https://github.com/la-jarre-a-son/midi-jar/issues/25)

New features and fixes are tested and seems to work as intended. Good utility becomes perfect. Thank you!


Quote should not have a parent

I tried to repost a note by using quote (as I see no other option for it).
Clicked on Quote, added no comment and clicked Send.
I expected the event to show in my notes but instead it's a reply (it has an e tag): https://www.nostr.guru/e/3c375577086d77c731cd694325d578c76738ad55e950dc1f98cb0383f0ac6da5
If this is not a bug, what is the purpose of quoting if it ends up as a reply?

If the e tag is there as a mention consider using NIP-10 and write it as ["e", "hex", "", "mention"]. The legacy syntax is too confusing as what an e refers to


Same problem, multiple Macs running Mavericks

I am having the same issue on multiple machines running Mavericks.  I install DNSCrypt and select DNS provider.  I restart but the machine will not connect to the internet.  I check the network settings and the DNS settings does not have an IP address or addresses.  I set a DNS address and now DNScrypt starts working.  If I restart the machine again, DNS will again stop working.  I go to network settings and check DNS settings again and sure enough DNS settings are blank.  I once again manually set the DNS and DNSCrypt (and DNS services) start working.
One other point that might be related..  These machines are set up with static IPs.

Unfortunately, the user interface requires a DHCP server. It doesn't work with static IPs.

That's too bad... I never had that problem when OPENdns started the DNSCrypt project and had their client....

Maybe it didn't work and you didn't notice. The first user interface didn't really check that it worked as expected (disclaimer: I wrote it). It was just a simple proof of concept. The current code is a bit more serious.

I used DNScrypt since very early on and never had a problem and on my network I always use static IPs, so I think that for whatever reason it did work with that configuration.  I started having problems as I updated OS X and went to DNSCrypt.
I am sure you recognize that the problem results from clearing out user DNS settings so that after startup it does not know where to go...  Perhaps it should have a default dns at startup so that it knows how to start??

In any case, thanks for the quick response... keeps me from chasing something that might not ever work!!


Fix #2902: Adapt to jsdom v10.

While still retaining compatibility with jsdom v9.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3908/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/5167/
Test PASSed.

I am following the Scala.js tutorial [https://www.scala-js.org/tutorial/basic/] and I got the error this PR is said to have fixed:
[info] Running tutorial.webapp.TutorialApp
[error] [stdin]:40
[error]     virtualConsole: jsdom.createVirtualConsole().sendTo(console),
[error]                           ^
[error]
[error] TypeError: jsdom.createVirtualConsole is not a function
[error]     at [stdin]:40:27
[error]     at [stdin]:61:3
[error]     at ContextifyScript.Script.runInThisContext (vm.js:25:33)
[error]     at Object.exports.runInThisContext (vm.js:77:17)
[error]     at Object.<anonymous> ([stdin]-wrapper:6:22)
[error]     at Module._compile (module.js:570:32)
[error]     at Immediate.<anonymous> (bootstrap_node.js:357:29)
[error]     at runCallback (timers.js:649:20)
[error]     at tryOnImmediate (timers.js:622:5)
[error]     at processImmediate [as _immediateCallback] (timers.js:594:5)

I have checked the steps multiple times to eliminate if I am screwing something up. I have also cloned this repo that is exactly the tutorial describes: [https://github.com/scala-js/scalajs-tutorial]
I was running the latest version of jsdom (npm install jsdom). I followed [https://github.com/scala-js/scala-js/issues/2902#issuecomment-296776240] to downgrade jsdom, then it worked.

It's a PR, not a release. Unless you have cloned and locally published a snapshot of Scala.js, obviously you won't be enjoying the fix.
A new release is about to arrive (a couple of days if all goes well).

Ohh, my bad!


服务调用报错：TypeError: _create_embedding() got an unexpected keyword argument 'model_config'

The issue is fixed by a contributor Vokturz at #2: support for CPU/GPU choice and initialization before starting the app.
I just released the package at https://pypi.org/project/open-text-embeddings/.
Kindly let's me know if you think there are ways to improve it. This is the first python package I publish to pypi.


Pdf viewer shows black pages

Some pdf files are shown as black pages with the internal pdf viewer; see http://www.braidense.it/rd/03595.pdf; if using any acrobat viewer or saved, pages appear correctly

This bug might be related to the 4 BitsPerComponent, which is not handled correctly. See https://bugzilla.mozilla.org/show_bug.cgi?id=1659412

IrfanView claims that the image inside the PDF from the bugzilla issue has 12 bits per pixel?!