Compatibility with Angular 9 Ivy

Hi,
I upgraded my NativeScript project to Angular 9 using this guide.
When enabling ivy in tsconfig.json it gives me multiple errors like:

Seeing the same. @PhilippS93 what did you do about it?

@madmas we have disabled ivy in the meantime and are waiting for the native i18n support Angular 10 offers.

For Angular 10, this is not working because Ivy cannot be disabled..

Still no ivy support :( Very unfortunate

I think you are looking for "@nativescript/localize"

@michaelprummer Didn't realized this one. Thank you Sir!


fix: update semantic-release configuration and CI/CD workflow

Description
This PR updates the configuration for semantic-release and the GitHub Actions workflow to ensure that the release process works correctly with the new setup.
Changes:

Updated .releaserc.json to exclude release/next branch from analysis.
Modified .yaml file for GitHub Actions to correctly handle releases and Pull Requests.

Type of Change

[x] Configuration update
[ ] New feature
[ ] Bug fix
[ ] Refactor
[ ] Documentation update
[ ] Other (please describe):

Checklist

[x] My code follows the project’s coding style
[x] I have performed a self-review of my code
[x] I have updated the documentation as necessary
[x] My changes generate no new warnings or errors
[x] I have checked my code and corrected any misspellings

Related Issues
No related issues.
Additional Information
N/A

:tada: This PR is included in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


bevy 0.13 update + wgsl binding group fix

Combines:
https://github.com/ForesightMiningSoftwareCorporation/bevy_transform_gizmo/pull/64#issue-2177638620
https://github.com/ForesightMiningSoftwareCorporation/bevy_transform_gizmo/pull/65#issue-2197950727
into a single pr.
All examples work and cargo test passes.

I don't know how to fix the cargo fmt error on this. 😭

Closing in favor of the individual PRs. Thank you though!


fix issue

Here are the issues.

skywalking extract binary data failed.
skywalking don't support peerhost tag of opentracing

Changes Unknown when pulling 0544edabf737d9b4cc6b8a842f38a553d75dc0cc on ascrutae:zhangxin/fix/169 into ** on wu-sheng:master**.

This issue includes:

[ ] Hostname, ipv4, ipv6 tags are not supported. Related #169
[ ] Inject and extract fail when using binary-map. Related #167
[x] peer.port is type of short, in some version of ot. Done in prev commits.
[ ] refactor codes about inject and extract when using text-map. #167


Update SiteIds

The following siteIds should be included:

§ K for Kiel
§ G for Muenster (GHI)
§ N for Newcastle
§ E for Rotterdam (Erasmus)
§ H For Harrow
§ Y For Leeds (Yorkshire)
§ D For Devon & Exeter
§ O For Pennine Acute Hospitals (in Manchester - Odham, Rochdale, Fairfield)
§ C For Glasgow (along the river Clyde)
§ M For Manchester
§ Q For QMUL
§ I For Limerick (Ireland) Conflict with the current one I for ICL
§ L For Leiden
§ B For Brescia
§ P For Lisbon (Portugal)
§ A For Innsbruck (Austria)
§ W For Warshaw
§ S For Madrid (Spain)
§ R For Stavanger (Rogaland, Norway)
§ T For Testing

We simply cannot reassign a field already in use. There are to many possible problem even if Imperial is the only one, we have a multitude of test files added with time. Most of which are still present in the Object Storage since we have never purged ⚠

While looking into this issue, I found a possible inconsistency:
The frontend use codes from of organizations to validate the sites:
https://github.com/ideafast/ideafast-portal/blob/8457080dc06728bac3a2a12b3eda84710c65964f/packages/itmat-ui-react/src/components/datasetDetail/tabContent/files/fileTab.tsx#L588-L591
While the backend hard-codes the sites for validation:
https://github.com/ideafast/ideafast-portal/blob/8457080dc06728bac3a2a12b3eda84710c65964f/packages/itmat-interface/src/utils/definition.ts#L24-L30
Should we use the organisations in both cases and avoid the hard-coding? @fguitton

Regarding the inconsistency, I think one solution maybe like this:

Store the organisations totally in the db;
All organisations will be used for registration;
Organisations with valid siteIdMarket in the metadata field will be used to validate the first letter of a participant Id;
Open a new tab in the DMP to let admins manage the organisation in the frontend.

@fguitton What do you think of this?

@wsy19961129

Store the organisations totally in the db;

This is already the case, the organisation collection contains a metadata object with a siteIDMarker which should be the tagging letter. It is true however that the front-end is not fetching that information and should.

All organisations will be used for registration;
I am not quite sure what you mean here.

Organisations with valid siteIdMarket in the metadata field will be used to validate the first letter of a participant Id;
👍🏼

Open a new tab in the DMP to let admins manage the organisation in the frontend.
This is only a feature for us. Lets not forget that this is supposed to be used by other project eventually as well. I think it's a bit larger of a feature than immediately thought about. I can see multiple conflicts. Organizations would have to be managed/attached to a project/dataset/study, the metadata right now are semantically OK in that sense. This means we are missing a lineage. But if we do that we are then opening the option in the future to have multiple times the same organisation registered. We could do this in two stage, with platform admin able to create organization and projects/dataset/study they have access to, and then a project/dataset/study level admin panel allowing to define the metadata. This would be the most elegant but require that we split the existing organisation table. It's a larger conversation.


Add data transformer

starknet-rs recently added a dsata transformer. We should think about adding support for it to cast.
In handy when, for example, passing some calldata to deploy command

https://docs.starknet.io/documentation/architecture_and_concepts/Smart_Contracts/serialization_of_Cairo_types/


FUT18

Multiple adjustments and refactoring for migrating to FUT18

@trydis - Can you have a look if we can push it into master? Usually we should push into vnext at first, but the master branch is useless as long as it is on FUT17 code.

Sure @tringler, I'll take a look a bit later tonight

Ok, i'm just gonna merge this to master and then let's take it from there.

https://www.nuget.org/packages/UltimateTeam.Toolkit/5.0.0-rc0003


Add a way to add specific songs in playlist

I would like to be able to navigate into my playlists and to add one song in the playlist, then go in another playlist and add another song and so on.
Same for the search results. Like this, I would be able to build a temporary playlist fitting my mood.
How I see the feature : just add an new entry in the right click of a song, to let the user to add it in the playlist.

I think what you need is more like a general queue ?

Yes, a queue that I can fill just for this Kaku session in order to have around several hours of playing without searching new song each time a song does finish


Qdrant update to 1.4.1

PRs:

https://github.com/code-kern-ai/refinery-neural-search/pull/34
https://github.com/code-kern-ai/dev-setup/pull/31
https://github.com/code-kern-ai/refinery-updater/pull/47

Could you refer to the Preparation PRs so we know where the change is coming from (like with this one).

I added a small fix to dev for the filter check.
should be easily mergeable

[ ] resolved


dbt clone fails on Redshift due to not being able to add comments to columns

Describe the bug
dbt clone fails on Redshift because it creates a view with with no schema binding and tries to add comments on column, which is not supported.
Steps To Reproduce

Run dbt clone --select "unsorted_data_history" --state latest_artefact/
Error appears

10:39:34    Database Error in model unsorted_data_history (path/to/model/unsorted_data_history.sql)
  column "ts" of relation "unsorted_data_history" does not exist
  compiled Code at target/run/path/to/model/unsorted_data_history.sql

Which is because it creates a view with with no schema binding

create view "prod"."dev_foo"."unsorted_data_history__dbt_tmp" as (
    select * from "prod"."observability"."unsorted_data_history"
  ) with no schema binding;

Adding a comment to with no schema binding view is not supported by Redshift (docs).
If I omit the with no schema binding, everything works.

Expected behavior

I expect this to work. Potentially have the option to choose to create a view without with no schema binding.

Screenshots and log output

NA

System information
The output of dbt --version:
Core:
  - installed: 1.8.6
  - latest:    1.8.7 - Update available!

  Your version of dbt-core is out of date!
  You can find instructions for upgrading here:
  https://docs.getdbt.com/docs/installation

Plugins:
  - redshift: 1.8.1 - Up to date!
  - postgres: 1.8.2 - Up to date!

The operating system you're using: Mac
The output of python --version: Python 3.12.4
Additional context

Upon closer look, this might not be a "bug", because in our project, we have:

models:
  foobar:
    +bind: False

However, I'd then expect an option in the command to not bind views.

Wrong Github, sorry!


Is there any way to find 'WHEN' a PDF starts rendering? like we have "PAGERENDERED" event!

After a page finished rendering we can find out by adding event listener for "PAGERENDERED". Like that is there any event triggered for start of a PDF rendering?

Check the dom_events.js file at https://github.com/mozilla/pdf.js/blob/f83bd721fc0fbc382f0059903e1f16a410401732/web/dom_events.js. There is, for example, the documentload event and the pagesloaded event, which I think is what you need. That file lists all the available events, so check their usages. Closing as answered.


Fix syntax of primary prompt of Python

Hi! I was reading the README and was wondering about the space in the primary prompt of Python, so I fixed it.

Thank you @tkoyama010! Not sure how I missed that, I really appreciate your taking the time to fix it 🙏 🙇

@all-contributors please add @tkoyama010 for docs


Add algorithm for merge-sort

amazing! Thank you so much @fr33m0nk. I would like to make more contributions here :)


Fixing the escape check to provide better errors

This fixes #3102, which I should have realized was a variable escaping in the type of the letbinding. But, the error message was bad since it was raising an internal failure instead of properly reporting the escape. A patch in this PR fixes it (https://github.com/FStarLang/FStar/commit/ae3e0cdda57bbbbf5d79ea5c85f99c7e2fc59ac5), and there's some other misc stuff too.

Got an everest green locally, merging.


Issue #18 Add search overloads that take in CancellationToken

Fixes #18

@jochenvanwylick Could you check if this PR works for you, and as expected? Thanks

@jochenvanwylick Sorry to bother you again. Are you planning on reviewing this PR?

Hi @tamasvajk - sorry for the late response. I'm checking right now!

@jochenvanwylick Thanks. If you have time, you could check the other one too: #19

Yeah - aswesome. It would have been fine to finish the ongoing HTTP call and just stop the polling with the token - but you pass it all the way down to GetAsync() which is even nicer. Cool - thanks!


Add documentation for the Kitura-Crendentials repos

Add documentation to the README.md files of the Kitura-Credentials and Kitura-CredentialsFacebookToken repositories

Reviewed the README.md files. They are OK.


Support adding columns in LanceDB

Problem Statement
Expose Lance's schema evolution capability to LanceDB

I need a way to understand through documentation how the schema evolves over time.
For example:
I start by saving a doc like {"a": 1} as the first record.
When I save {"a":2, "b":3} at the moment, not only is there no warning that "b" is not saved, there's no documentation to clearly indicate how I can get "b" to save.


Onboard to OpenSearch build distribution for release

Since we want to release in 2.5, there are a few things we should double-check:
https://github.com/opensearch-project/opensearch-build/blob/main/ONBOARDING.md
https://github.com/opensearch-project/opensearch-plugins/blob/main/BUILDING.md

Moved to 2.6 for now

@msfroh will we onboard this repo for search pipelines?

No AI for now. Free to open in the future


Using <IP_ADDRESS>/0 in the security group for port 22 is a very bad idea

Thanks Tony for you feedback.  We were trying not to introduce any concepts of security groups when just doing an evaluation of Athenz so we left the default AWS setting as is (even though AWS itself presents with a warning). We updated the documentation to point this out as well and the steps were updated to use the "My IP" option for the evaluation.


running exit isn't closing the terminal

Does this issue occur when all extensions are disabled?: Yes/No
yes

VS Code Version: 1.69.0
OS Version: windows 11

Steps to Reproduce:

enable shell integration

  "terminal.integrated.shellIntegration.enabled": true,

run exit in the terminal

Spotted this yesterday, I think it's annoying enough to get into the recovery build. I'll reopen https://github.com/microsoft/vscode/issues/154421
/duplicate


Support for class = ... in view! macro.

It looks like leptosfmt does yet like the class = ... syntax introduced in https://github.com/leptos-rs/leptos/pull/351
Small test case:
use leptos::*;

#[component]
pub fn Test(cx: Scope) -> impl IntoView {
    view! {
        cx,
        class = STYLE,
        <p>"Test paragraph"</p>
    }
}

const STYLE: &str = "some-class";

Currently panics with
thread 'main' panicked at 'invalid rsx tokens at line: 5:4', /home/fabian/.cargo/registry/src/index.crates.io-6f17d22bba15001f/leptosfmt-formatter-0.1.4/src/formatter/mac.rs:14:13
stack backtrace:
   0: rust_begin_unwind
             at /rustc/900c3540378c8422b8087ffa3db60fa6c8abfcad/library/std/src/panicking.rs:579:5
   1: core::panicking::panic_fmt
             at /rustc/900c3540378c8422b8087ffa3db60fa6c8abfcad/library/core/src/panicking.rs:64:14
   2: leptosfmt_formatter::formatter::mac::<impl leptosfmt_formatter::formatter::Formatter>::view_macro
   3: leptosfmt_formatter::source_file::format_source
   4: leptosfmt_formatter::source_file::format_file_source
   5: leptosfmt_formatter::format_file
   6: core::ops::function::impls::<impl core::ops::function::FnMut<A> for &F>::call_mut
   7: <rayon::iter::for_each::ForEachConsumer<F> as rayon::iter::plumbing::Folder<T>>::consume_iter
   8: <rayon::vec::IntoIter<T> as rayon::iter::IndexedParallelIterator>::with_producer
   9: leptosfmt::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
❌ src/fmt_test.rs
		invalid rsx tokens at line: 5:4
Formatted 1 files in 6 ms

Removing the class = STYLE line makes the example work, indicating that it should be the culprit.

Hey, thanks for reporting this. I was not aware of the scoped styling feature of the view! macro.
Will fix this soon : )


non-blocking option?

We had an issue that generated lots of spurious logging, and as a result the website became unusable. After some digging, I believe it because every log call blocked waiting for the Slack request to round trip. I would like an option to make Slack calls best-effort and non-blocking.
I'm open to sending a PR if you'd rather review than write yourself. (Not always obvious which is better for a small feature like this.)
Thanks for all the slog-ish packages.

Thanks for the suggestion.
Fixed in v2.1.0.


How to figure out what color is responsible for

When I downloaded colors config and apply it to termit, mostly I have noticed background is changed.
How I can understand fro example
# Yellow
color3  = #a06e3b
color11 = #a06e3b

where yellow color is using?

Its setting the 16 colors for terminals, you can see them running something like
$ for i in {30..37}; do for a in {40..47}; do echo -ne "\e[$i;$a""m$i;$a""m\e[0m "; done; echo; done

or
$ npx colortest

base16 only provides 16 colors, half of which are typically a gray scale, so it only have one yellow per scheme - the bold variants that terminals have are just set to reuse the same yellow as non-bold.


Teku start script Win10: Syntax error. Command too long.

Description

Using Windows 10 x64 with teku-0.12.0-SNAPSHOT
Running bin\teku.bat throws a syntax error. The command is too long.

Acceptance Criteria

Start up scripts gets executed without error

Steps to Reproduce (Bug)

Use Win10
Download teku-0.12.0-SNAPSHOT
run command: bin\teku

Expected behavior: [What you expect to happen]
Start up scripts gets executed without error
Actual behavior: [What actually happens]
syntax error. The command is too long
Frequency: [What percentage of the time does it occur?]
100%
Versions (Add all that apply)

Software version: [teku --version]
teku-0.12.0-SNAPSHOT
Java version: [java -version]
jdk-14.0.1
OS Name & Version: [cat /etc/*release]
Windows 10 64bit

Additional Information

Thanks for reporting this.  Could you confirm the build at https://28753-147802356-gh.circle-artifacts.com/0/distributions/teku-0.11.4-SNAPSHOT.zip works for you please?
This is from the master branch so will be compatible with witti, but not Prysm's new Onyx testnet.  We regularly merge changes from master over to our v0.12 branch so 0.12.0 builds with this fix should come through within a few days of this being merged.

I can confirm https://28753-147802356-gh.circle-artifacts.com/0/distributions/teku-0.11.4-SNAPSHOT.zip is working and doesn't show this behavior.
So I should wait for a release of 0.12 and do not grab the snapshot?

Which version to use depends on which testnet you're trying to connect to. There are two incompatible versions of the beacon chain spec currently in use (because not all clients are ready for the new version and some testnets are still running the older one).
So:

The Witti testnet uses beacon chain spec 0.11.3, which is supported by the 0.11.x series of Teku releases and our master branch.  The build I linked to above is fine to use to connect to Witti.
Prysm's new Onyx testnet uses beacon chain spec 0.12.1 which is supported by the 0.12.x series of Teku releases and our 0.12.1-integration branch.  Our v0.12.1 support is very new and still untested (not even sure if we agree on the Onyx genesis state yet).

So my recommendation would be to use the build I link above and connect to the Witti testnet (bin\teku.bat --network witti) which we know works well.  The fix will find it's way into both master and 0.12.1-integration branch in time and both should get a release put out later this week.   Because things are changing so rapidly we recommend that most people use the very latest -SNAPSHOT builds of either the 0.11 or 0.12 streams and not wait for a release.  You may hit a few more unexpected bumps doing that but finding issues is the aim of these testnets so it would really help us with getting ready for the real beacon chain main net.

Sorry that I wasn't clear. I want to use the latest version reflecting 0.12.1 spec.
I'll wait until teku is ready for Onyx or Altona. Thanks!

For the record, this fix has now been merged into the 0.12.1-integration branch.  We're still primarily focussed on Witti though so haven't done any significant work to investigating compatibility with Onyx.  It's likely to be unstable at this point.


updated contributors.js in data directory

Please add the hacktoberfest-accepted labels in this contribution. Thank you

Hey, there are some merge conflicts please fix that. @AdityaMore7000

Ok

conflict has been resolved

Congrats 🎉, your PR got merged. To be eligible for the swags from iNeuron X ClueLess. Follow this steps.

SignIn / SignUp in ClueLess Website .

Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.


feat: client and composer

This PR adds two new classes, AlgokitComposer and AlgokitClient. The core idea is to provide a smooth experience for all chain interactions as discussed in #215. In most cases users are not expected to use the composer directly, but rather through the client. The composer, however, is still exported in case someone wants to use it without the client.
TODO

[ ] test coverage for all methods
[ ] test cachedSuggestedParamsTimeout
[ ] test defaultSigner
[ ] test multi-level nested method call args
[ ] test defaultValidityWindow
[ ] comments/documentation
[ ] test flatFee and extraFees

Problems Addressed
Mixing of algosdk and algokit-utils
Sending transactions currently requires mixing the usage of algosdk and algokit-utils.
Solution
AlgokitClient eliminates need for algosdk usage for chain interactions. AlgokitComposer is also able to take an algosdk.AtomicTransactionCompsoer and add it to its group.
Confusing interfaces
Currently, a lot of the interface on algokit-utils can be rather confusing. There are many union types and many ways to do the same thing. For example, in some places when passing a tranasction you use {txn, signer}, {tranasction, signer}, or {transaction, from}. signer and from can be many different types, inlcuding but not limited to the types used by signer or from fields in the SDK.
Solution
AlgokitComposer has straight-forward interfaces for all actions. There are no union types and the functions are not clever. There is one way to do a specific action and it is always done that way.
A lot of async functions
Because of suggestedParams, async calls may currently required when forming transactions. This is paticularly annoying when using .compose() on an generated app client. Because the chain of function calls require await in the middle making it a bit annoying to work with.
Solution
Nothing async happens until AlgokitCompose.execute() or AlgokitComposer.buildGroup()
Repetitive or old suggestedParams
Suggested params is currently needed for every transaction formation. A common solution is to just get suggested params once, but its possible that the suggested params could be out of date.
Solution
AlgokitComposer caches suggestedParams and only does the API call after a certain amount of time has elapsed
Repetitive signers
For every transaction, there needs to be a way to sign it. Currently there are many different ways to sign transactions with algokit and often you use a signer function in multiple places.
Solution
AlgokitClient allows you to specify a defaultSigner to use for all transactions (useful for wallet interaction). You can also set a unique signer per address (useful for localnet or custodied accounts). Attaching a unique signer to a tranasction is still possible if necessary.
Improper fee setting
Many dApps currently do not set fees properly. For example, if an app wants to add extra fees to their current transaction it is common practice to do (1 + extra_txns) * MIN_FEE. This is problematic because it does not account for fee scaling.
Solution (Partial)
AlgokitComposer transactions have two fee fields: flatFee for setting the flatFee on the transaction and extraFee for adding additional microAlgos to the suggested fee. This is important because it still takes into account the feePerByte recommended by algod for the given transaction. This means you can simple set extraFee to numInners * MIN_FEE to ensure the fee will always be correct for app calls with inner transactions, even under fee scaling.
TODO
In the future we need to devise a smart way to handle scenarios where one outer transaction might want to cover the fee for another out transaction. If feePerByte is non-zero, then this is hard to calculate.
Differing validity window and wait times
It is currently common practice to use the default validity window (1000 rounds) on transactions but only wait a short amount of rounds for confirmation (typically 3-5). This can lead to a confusing UX and potentially double transactions if the user is not aware of the validty windows of their transactions in the event of longer confirmation times.
Solution
AlgokitComposer.defaultValidityWindow is set to a much more reasonable window (for user-facing dApps) of 10 rounds (~30 seconds). By default, AlgokitComposer.execute() will wait until the last valid round in the transction group has passed to ensure tranasctions are confirmed when the user is not expecting it.
ABI method argument composability
Currently, if an application expects another ABI method call as an argument there is no great way to handle that other than manually building the ATC and deconstructing the group. Even after doing that, the return values for the argument calls will not be availible.
Solution
AlgokitComposer method calls support other method calls as arguments.

@robdmoore as we discussed I added the .send and .transaction interface. I also implemented a maxFee mechanism. I know it's duplicating whats done at a lower level, but properly integrating all the fee features at a lower level would require a good amount of refactoring so I think it's just best to leave it as is now and we can refactor later. I just want to get user-facing stuff out the door ASAP.
Only major thing I can think of that we discussed is supporting string on lease and note fields, which shouldn't be too hard. Then testing and docs.

FYI @robdmoore in b01bd65 I changed the algorand client used in the test fixture to be persistent. This is particularly useful when you want to use an account across multiple tests and preserve the signer.


Add script to create a release on GitHub Actions from a tag

Summary of changes
Add a script to create a release on GitHub Actions from a tag.
Usage:
$ python tools/create_release.py --help
usage: create_release.py [-h] [repo] [tag]

Create a release on GitHub Actions from a tag.

positional arguments:
  repo        Repo to release to (default: pypa/setuptools)
  tag         Tag to release (default: v49.7.0)

optional arguments:
  -h, --help  show this help message and exit

Calls finalize.get_version and prepends v to get the default tag.
Needs a GITHUB_TOKEN environment variable.

How to create a token:
https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token#creating-a-token
I think only the public_repo permission is needed

Example in my fork with explicit args:
$ git tag v<IP_ADDRESS>
$ git push origin v<IP_ADDRESS>
Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
To https://github.com/hugovk/setuptools
 * [new tag]           v<IP_ADDRESS> -> v<IP_ADDRESS>
$ python tools/create_release.py hugovk/setuptools v<IP_ADDRESS>
Creating release v<IP_ADDRESS> at hugovk/setuptools
Released to https://github.com/hugovk/setuptools/releases/tag/v<IP_ADDRESS>

API docs: https://docs.github.com/en/rest/reference/repos#create-a-release
I'd need some guidance if this is to go in https://github.com/jaraco/skeleton first.
A body parameter can be used to add release notes, I'd suggest this be added in a follow-up once the general flow is working.
Closes #2328.
Pull Request Checklist

[n/a] Changes have tests
[n/a] News fragment added in changelog.d. See documentation for details

So I decided to take inspiration from this PR and put together a routine in a library to do the work in jaraco/develop@
But when I ran it on a recent release of keyring, I got a 403 Forbidden.
keyring master $ pip-run setuptools git+https://github.com/jaraco/jaraco.develop@178c073 -- -m jaraco.develop.create-github-release
Collecting git+https://github.com/jaraco/jaraco.develop@178c073
  Cloning https://github.com/jaraco/jaraco.develop (to revision 178c073) to /private/var/folders/c6/v7hnmq453xb6p2dbz1gqc6rr0000gn/T/pip-req-build-09edlulu
  WARNING: Did not find branch or tag '178c073', assuming revision or ref.
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
    Preparing wheel metadata ... done
Collecting setuptools
  Using cached setuptools-49.6.0-py3-none-any.whl (803 kB)
Collecting requests-toolbelt
  Using cached requests_toolbelt-0.9.1-py2.py3-none-any.whl (54 kB)
Collecting jaraco.ui
  Using cached jaraco.ui-2.0.1-py2.py3-none-any.whl (7.5 kB)
Collecting keyring
  Using cached keyring-21.4.0-py3-none-any.whl (31 kB)
Collecting autocommand
  Using cached autocommand-2.2.1-py3-none-any.whl (22 kB)
Collecting requests<3.0.0,>=2.0.1
  Using cached requests-2.24.0-py2.py3-none-any.whl (61 kB)
Collecting jaraco.text
  Using cached jaraco.text-3.2.0-py2.py3-none-any.whl (8.1 kB)
Collecting six
  Using cached six-1.15.0-py2.py3-none-any.whl (10 kB)
Collecting jaraco.classes
  Using cached jaraco.classes-3.1.0-py2.py3-none-any.whl (5.7 kB)
Collecting chardet<4,>=3.0.2
  Using cached chardet-3.0.4-py2.py3-none-any.whl (133 kB)
Collecting certifi>=2017.4.17
  Using cached certifi-2020.6.20-py2.py3-none-any.whl (156 kB)
Collecting idna<3,>=2.5
  Using cached idna-2.10-py2.py3-none-any.whl (58 kB)
Collecting urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1
  Using cached urllib3-1.25.10-py2.py3-none-any.whl (127 kB)
Collecting jaraco.functools
  Using cached jaraco.functools-3.0.1-py3-none-any.whl (6.7 kB)
Collecting more-itertools
  Using cached more_itertools-8.5.0-py3-none-any.whl (44 kB)
Building wheels for collected packages: jaraco.develop
  Building wheel for jaraco.develop (PEP 517) ... done
  Created wheel for jaraco.develop: filename=jaraco.develop-7.0.1.dev2+g178c073-py3-none-any.whl size=7484 sha256=58d218b7deafe0d3cba959f7f5b0f944e487530a472a8541288261335cf9a450
  Stored in directory: /private/var/folders/c6/v7hnmq453xb6p2dbz1gqc6rr0000gn/T/pip-ephem-wheel-cache-97mleq6e/wheels/14/84/4d/941b19c6c41939bb21ae0e7dc4b2998c281c1c32f83e6287db
Successfully built jaraco.develop
Installing collected packages: setuptools, chardet, certifi, idna, urllib3, requests, requests-toolbelt, six, more-itertools, jaraco.functools, jaraco.text, jaraco.classes, jaraco.ui, keyring, autocommand, jaraco.develop
Successfully installed autocommand-2.2.1 certifi-2020.6.20 chardet-3.0.4 idna-2.10 jaraco.classes-3.1.0 jaraco.develop-7.0.1.dev2+g178c073 jaraco.functools-3.0.1 jaraco.text-3.2.0 jaraco.ui-2.0.1 keyring-21.4.0 more-itertools-8.5.0 requests-2.24.0 requests-toolbelt-0.9.1 setuptools-49.6.0 six-1.15.0 urllib3-1.25.10
WARNING: The wheel package is not available.
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/var/folders/c6/v7hnmq453xb6p2dbz1gqc6rr0000gn/T/pip-run-eawuq_zh/jaraco/develop/create-github-release.py", line 24, in <module>
    def run():
  File "/var/folders/c6/v7hnmq453xb6p2dbz1gqc6rr0000gn/T/pip-run-eawuq_zh/autocommand/autocommand.py", line 66, in autocommand_decorator
    func = automain(module)(func)
  File "/var/folders/c6/v7hnmq453xb6p2dbz1gqc6rr0000gn/T/pip-run-eawuq_zh/autocommand/automain.py", line 55, in automain_decorator
    sys.exit(main(*args, **kwargs))
  File "/var/folders/c6/v7hnmq453xb6p2dbz1gqc6rr0000gn/T/pip-run-eawuq_zh/autocommand/autoparse.py", line 301, in autoparse_wrapper
    return func(*parsed_args.args, **parsed_args.kwargs)
  File "/var/folders/c6/v7hnmq453xb6p2dbz1gqc6rr0000gn/T/pip-run-eawuq_zh/jaraco/develop/create-github-release.py", line 38, in run
    session.post(releases, json=dict(tag_name=tag, name=tag)).raise_for_status()
  File "/var/folders/c6/v7hnmq453xb6p2dbz1gqc6rr0000gn/T/pip-run-eawuq_zh/requests/models.py", line 941, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://api.github.com/repos/jaraco/keyring/releases

So I went to keyring and see that releases are generated automatically from tags:

I double-checked that the token I'm using has all repo permissions (though I don't see any settings relevant to releases).

Aha, after emitting the error message in jaraco/develop@85b9c5e, it became clear that the request was being rejected for a missing User-Agent header, so I've fixed that (in the same commit).

Thanks for drafting this PR. I was able to adapt the technique into a re-usable solution in jaraco/skeleton#26 which I hand-cherry-picked in 17cb9d6bf. Future releases should get Github releases. Let me know if you find otherwise.

Good stuff, thank you!


Logging server requests in verbose mode

Logging every HTTP request into console output would help debugging.
Currently no output is generated in server mode with the verbose option.
versatiles serve --verbose --port 80 -s frontend.tar.gz osm.versatiles

I have added more logging in v0.12.7. The new release will be available in a few minutes.
Use the flag ‘-vvvv’ to get the full power of maximum verbosity. :)
Does this help you?

Yes, works well and helps a lot. Can you add the -vvvv option to the program help?


change method and veriables to public scope in clusterset_bind command.

related issue #122
Signed-off-by: mgold1234<EMAIL_ADDRESS>

/lgtm

/approve


rocPRIM defines a __atomic_work_item_fence with conflicting types to original

AMD Internal Bug:
rocPRIM defines in file  /opt/rocm/rocprim/include/rocprim/intrinsics/thread.hpp:282:36:
extern "C" ROCPRIM_DEVICE void __atomic_work_item_fence(unsigned int, unsigned int, unsigned int);
Original definition in /opt/rocm/include/hip/hcc_detail/device_library_decls.h:115:1 is:
__atomic_work_item_fence(__cl_mem_fence_flags, __memory_order, __memory_scope);
This causes compile time errors for PyTorch.
It looks like a forward declaration gone wrong.

https://github.com/ROCmSoftwarePlatform/rocPRIM/blob/master/rocprim/include/rocprim/intrinsics/thread.hpp#L282
__atomic_work_item_fence is declared and used only in HC API (because HC doesn't have correctly defined fences).
Why do you use it? Why not ROCPRIM_HIP_API?

The call was used in rocThrust. Once the HC_API is removed completely, this issue will disappear.

This is odd, because rocThrust uses ROCPRIM_HIP_API.


Fix typo

Checklist

[x] I read the CONTRIBUTING GUIDE
[ ] I opened a CONTRIBUTING ISSUE before opening the PR

Description
Screenshots

if relevant please add screenshots to show how it looks on your machine

If you are adding new plugin support please fill out the following :)
Which plugin?
flash.nvim

put a link to the plugins repository below

Example plugin config

help me test your changes by showing me how to setup the plugin you implemented

-- please put an example config for setting up the plugin here

thanks :)


F#543 response grids of excel at once

Description

Originally grid information was requested every time user clicks on the sheet button.
Now grid information is returned with an array so the user doesn't need to wait for the server response
every time user clicks on the sheet button.
Related Issue :

#543
How Has This Been Tested?

Go to create dataset by file (excel)
Make sure excel file has at least two sheets
Click on the sheets, check if grid is shown without delay
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code follows the code style of this project. it will be added soon
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document. it will be added soon
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Additional Context

run build
deploy to 2


chore(transporter): fix typo

This isn't per se a typo, but retryable is "more common" https://english.stackexchange.com/questions/364277/which-spelling-is-preferred-retriable-or-retryable

your bundlesize is set very strict haha

Thanks!


Added AUR package

i'll maintain it

This is a great idea;)
But first, correct this comment https://aur.archlinux.org/packages/fetch-scm#comment-822664 and then I'll accept the pull request.

This is a great idea;)
But first, correct this comment https://aur.archlinux.org/packages/fetch-scm#comment-822664 and then I'll accept the pull request.

I will xorrect only the second issue, because there's no need in installing license, if it's provided by the corresponding variable. It is unnecessary step at all, as I read AUR guidelines. But he's right about provides, which will be fixed as soon as I get to my PC. besides, removing provides doesn't change a thing at all, it's all about PKGBUILD code quality.

@q60 As far as I understand, you have fulfilled the AUR requirements?

i did


blob size metric

add a simple metric to include blob sizes when proxy handle GET or PUT

dispersal latency looks equivalent to the duration recorded for PUT

for later we could add store as a label and replace Store.Stats()

@hopeyen what's up with this?

@hopeyen what's up with this?

Was gonna add a blob size metrics to eigenda proxy for throughput testing, but now I think there are better places where this metrics could live, perhaps EigenDA client 🤔 Since there's no clear motivation to add this metrics, I will close the PR for now


Dragen germline tool error

Our dragen v4 germline tool definition is failing with:
ask-container exitCode [1] in Reason [Error].  Message: [Generating run log at /var/log/dragen/dragen_run_1680551660203_7.log\n\nCommand Line: /opt/edico/bin/dragen --partial-reconfig HMM --ignore-version-check true \nDRAGEN Host Software Version 05.121.6<IP_ADDRESS> and Bio-IT Processor Version 0x00000000\n\nAutoDetected reference: UNKNOWN\nINFO: Loaded empty agfi\n\n==================================================================\nDownloading HMM HW bitstream (agfi-082bc7358866a1780) - do not interrupt\n==================================================================\n......\nAGFI: Downloaded HW bitstream agfi-082bc7358866a1780\nLICENSE_MSG| Requested streams:empty\nLICENSE_MSG| Empty (No AFUs) request\nPlease set no more than one of fastq_list, fastq_list_rows and bam_input for normal sample\n]\n

Ref: trn.b4993d0e133a41b087aed438f636ef73
Introduced in this commit https://github.com/umccr/cwl-ica/commit/5807359ef8a1d6cad655cbcb7488f949ee3102ef#diff-d982735ea5e3abfe93cd80017c44ce9d6fd525db2ae811791de4c3dbc3a54a57R76.

Ah I'm not sure that this is reproducible, from the log directory
gds://development/temp/sehrish/analysis_data/dragen_germline/03042023/work/logs/main/try-1/

Looks like two tasks tried to run in the same log directory
gds://development/temp/sehrish/analysis_data/dragen_germline/03042023/work/logs/main/try-1/trn.8269ad639dbf481988ee64acc38342b4.json
gds://development/temp/sehrish/analysis_data/dragen_germline/03042023/work/logs/main/try-1/trn.b4993d0e133a41b087aed438f636ef73.json

And the second task trn.8269ad639dbf481988ee64acc38342b4 completed successfully!

Please avoid using the same engine parameters for two separate workflow runs
ica-get-tasks-from-workflow-history --ica-workflow-run-id wfr.011b74982a1e4ba6af94f1c2502a7aa3
{
  "/main": {
    "task_id": "trn.8269ad639dbf481988ee64acc38342b4",
    "task_name": "main",
    "task_launch_time": "2023-04-03T22:07:47.115492Z",
    "task_completion_time": "2023-04-03T23:45:07.806491Z",
    "task_status": "Succeeded",
    "task_stdout": "gds://development/temp/sehrish/analysis_data/dragen_germline/03042023/work/logs/main/try-1/task-stdout-0.log",
    "task_stderr": "gds://development/temp/sehrish/analysis_data/dragen_germline/03042023/work/logs/main/try-1/task-stderr-0.log"
  }
}

 ica-get-tasks-from-workflow-history --ica-workflow-run-id wfr.e7a320a59ece4a7ba4a031ca299b2330
{
  "/main": {
    "task_id": "trn.b4993d0e133a41b087aed438f636ef73",
    "task_name": "main",
    "task_launch_time": "2023-04-03T19:37:56.782388Z",
    "task_completion_time": "2023-04-03T19:59:59.643539Z",
    "task_status": "Failed",
    "task_stdout": "gds://development/temp/sehrish/analysis_data/dragen_germline/03042023/work/logs/main/try-1/task-stdout-0.log",
    "task_stderr": "gds://development/temp/sehrish/analysis_data/dragen_germline/03042023/work/logs/main/try-1/task-stderr-0.log"
  }
}

This can't be reproduced since the shell script actually doesn't evaluate that line?
gds://development/temp/sehrish/analysis_data/dragen_germline/03042023/work/steps/main/try-1/run-dragen-script.sh

#!/usr/bin/env bash

# Fail on non-zero exit of subshell
set -euo pipefail

# Run partial reconfig
/opt/edico/bin/dragen \
  --partial-reconfig HMM \
  --ignore-version-check true

# Create directories
mkdir --parents \
  "/ephemeral/ref/" \
  "/ephemeral/intermediate-results/" \
  "2137_germline"

# untar ref data into scratch space
tar \
  --directory "/ephemeral/ref/" \
  --extract \
  --file "/data/cwl-stage-dir/stg9871678f-6b48-4f88-8ad9-989cd64a1c26/hg38-v8-altaware-cnv-anchored.tar.gz"

# Confirm either of fastq_list, fastq_list_rows or bam_input is defined
if [[ "1" -gt "1" ]]; then
  echo "Please set no more than one of fastq_list, fastq_list_rows and bam_input for normal sample" 1>&2
  exit 1
fi

# Run dragen command and import options from cli
eval "/opt/edico/bin/dragen" '"$@"'

But if you run
if [[ "1" -gt "1" ]]; then
  echo "foo"
else
  echo "bar"
fi

Will yield bar since "1" is not greater than "1"

Please use cwl-ica create-workflow-submission-template in future and ensure that the DATE_STR is present in the engine parameters, especially for the work directory. This will prevent unreproducible errors like this happening in the future.

Okay - this requires explanation.
First workflow run wfr.e7a320a59ece4a7ba4a031ca299b2330 failed with the error I have pasted in my issue in task trn.b4993d0e133a41b087aed438f636ef73.
The script is your message is from second successful task run trn.8269ad639dbf481988ee64acc38342b4 that I executed after making an update https://github.com/umccr/cwl-ica/compare/main...fix/dragen-germline-tool#diff-d982735ea5e3abfe93cd80017c44ce9d6fd525db2ae811791de4c3dbc3a54a57R76 (that I have just pushed).
Re reproducibility of the error, I agree the logs have been overwritten by the latest task run. I am launching a run again so that this could be reproduced.

The script is your https://github.com/umccr/cwl-ica/issues/316#issuecomment-1496748740 is from second successful task run trn.8269ad639dbf481988ee64acc38342b4 that I executed after making an update main...fix/dragen-germline-tool#diff-d982735ea5 (that I have just pushed).

Ah this makes a lot more sense!
I'd update the logic to be if [[ ! (js) == "1" ]]; then error; fi. For the dragen-germline pipeline, we want 1 and ONLY 1 of those inputs. For the somatic pipeline, it can be 0 or 1 since we can run it as tumor only


Python 3 compatibility

The code is not compatible with Python 3. The usage of "Print" function is obsolete.

There are potentially more issues with Python 3 compatibility than just print function. However, even though the project started on Python 2 due to some compatibility concerns, they are most probably gone now and migration to Python 3 is in plans. However, full transition requires considerable efforts including thorough testing and will take quite some time. Suggestions on how to make this transition as painless as possible are welcome.
There's also a different task of substituting print function with adequate logger, which is an important task as well and will be resolved much sooner. But it's unlikely to resolve 2 vs. 3 compatibility problem.

Closing. Fixed by 0.5.1 release.


Extract file#handleTypescript to plugin?

Please correct me if I missed it, but is there a mechanism to use an alternate typescript compiler?
Such as byots or angular's ngc? Right now it seems like the default typescript compiler is hardcoded.
Wondering if it would make sense to put it in a plugin. But would need a way to disclude it if you wanted to provide your own...

@calebboyd  Fuse uses TS by default, but nothing prevents you from creating a plugin to plug in your favorite compiler, the same we did for babel, and even coffeescript.

As far as I can tell I cannot prevent fusebox from trying to transpile typescript. (and do it myself instead). For example, if I want to use the AOT angular compiler.
If I try to make a .ts plugin and use a different one I inevitably end up with:
{ Error: Cannot find module 'typescript'
    at Function.Module._resolveFilename (module.js:469:15)
    at Function.Module._load (module.js:417:25)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at File.handleTypescript (/my/project/node_modules/fuse-box/dist/commonjs/core/File.js:283:20)

If i'm reading it right I can apply a plugin to a typescript file, but only if the typescript file is already cached??
https://github.com/fuse-box/fuse-box/blob/master/src/core/File.ts#L466
I could also use onTypescriptTransform but that still does double work if I wanted to transpile it myself.

@calebboyd yes we could have an option that would override and give a full control. But there are places where typescript is mandatory as, for example, it transpiles node_modules if es6 is detected

https://gitter.im/fusebox-bundler/Lobby?at=5981e55b4bcd78af56098b63
@calebboyd 09:44
Why would node modules be es6?
to support treeshaking? -- if so what will typescript do anyway if its configured to output es2015 modules

@nchanged 09:45
that’s for node_modules
if there is an es6 module ts will transpiled it
@troynt feel free to improve the plugin, but don’t make breaking changes please https://github.com/fuse-box/fuse-box/blob/master/src/plugins/WebIndexPlugin.ts

@nchanged 09:46
to support running on fusebox -)

@calebboyd 09:48
I'm not following... Why would someone publish an unconsumable module on npm

@nchanged 09:48
angular

calebboyd @calebboyd 09:50
Angular is published as umd, Are you saying fusebox will consume the es2015 entrypoint?

@nchanged 09:51
well you don’t know the whole story
well fuse can consume anything
some users import es6 code from node_module
http://fuse-box.org/page/configuration#usejsnext

@devmondo 09:59
we dont control what libraries put, but for a long time, we have solved edge cases u would never ever think of, those edge cases are the result of people smoking and drinking and then creating libraries with all sort of imagination formats, structure that comes to their mind while drunk  that is why fuse can eat whatever u feed it, it was and still not a trivial task to manage internally, yet u get the awesome beauty

@calebboyd 10:04
Okay, so you're accommodating the rollup "standard". You mentioned angular but it doesnt use either of those (it uses pkg.es2015). Which seems to be the same thing, but isn't picked up by fusebox

Thanks for the clarification. Is there a different codepath that handles the jsnext/es6 module transpilation? (other than File#consume?)

@calebboyd are you working on integrating the AOT compiler into a plugin? I have an open ticket in my starter repo for this issue I haven't had time to investigate much yet.
https://github.com/patrickmichalina/fusebox-angular-universal-starter/issues/44

@patrickmichalina yeah @dgreif and I will be looking into adding this. Right now its not too easy to use alternate typescript compilers. So I have to find a way around that first...

So, Exploring this a bit more now that 5 is out with a better compiler. -- It looks like to perform AOT using ngc you have to use a program. Which is problematic because fusebox makes use of transpileModule exclusively.
Any ideas on how to support that are most welcome

This is how a poor mans integration could look like: https://github.com/sod/fuse-angular5
fuse.js
const ngc = require('@angular/compiler-cli/src/main');
const {FuseBox} = require('fuse-box');

ngc.main(['--watch']);

const fuse = FuseBox.init({
    sourceMaps: true,
    homeDir : "dist/out-tsc/src",
    output : "src/dist/$name.js"
});

fuse.dev({
    root: 'src',
    open: true,
});

fuse.bundle("bundle/main")
    .instructions(`> main.aot.js`)
    .watch("dist/out-tsc/**");

fuse.run();

Just runs ngc in a separate process and fuse-box only touches the files that ngc emits.

Got this working with lazy loading! https://github.com/patrickmichalina/fusing-angular
If anyone needs it :)

FuseBox v4 Major Upgrade
As of today, the latest major version of FuseBox v4 is available in fuse-box@next. FuseBox has undergone a full re-write from scratch, learning from its mistakes in the previous versions.
There are a lot of improvements, speed and config wise.
Get started here
We are still working on the documentation and polishing before the major release. We are getting very close. And we need help testing.
npm install fuse-box@next

Most of the issues that I am closing have been resolved, however, if you find that your issue is still relevant in v4 don't hesitate to re-open or (better) create a new one with v4 configuration.


Unite search experience in Collections with Gallery

Is your feature request related to a problem?
When you try search in "Collections" you are getting realtime results with loading progress while you typing.
It's messy and not much user friendly.

Describe the solution you would like
It will be nice to implement same search experience that is used in "Gallery".

related to (or included in) issue https://github.com/kodadot/nft-gallery/issues/2100 . As discussed with @vikiival there's difference in queries used in these two components. I'd like to work on unification of search between gallery / collections. There's actually even design difference for some reason, which I don't see right now:
Gallery (after toggling filter -> default is hiddenbottom section with newest / buynow toggle)

Collections

Collections have legacy search iirc.
Gallery is definitely a few iterations further as we've been focusing there.
Unify those two components would be really much needed, #1678
In collections queries need major rehaul iirc to work properly, collection view is still experimental, where gallery showing NFTs per se and collections should offer way essential on recent new collections.

@yangwao I've fixed the edgecases in #2100. Now to your comment :

Gallery is definitely a few iterations further as we've been focusing there.

Should I make Collection search same as Gallery search then? Perhaps as a starting point and we'll keep them updated together from now on?

Will be resolved in https://github.com/kodadot/nft-gallery/issues/2719


chore: Actually use dtslint

Glad it's working again. I killed it bc it was doing something super weird and erroring only in dslint.👍


Wrong search index URL when using sub path as baseURL

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have searched for relatived questions
[X] I have read documentations

Describe the issue
The sub path appears twice in search index URL.
Steps to reproduce
https://hbs.razonyang.com/v1/v1/en/search/index.json
Expected behavior
https://hbs.razonyang.com/v1/en/search/index.json
What operating system(s) are you seeing the problem on?
Windows, Linux
What browser(s) are you seeing the problem on?
Chrome, Firefox
What version of theme are you using?
master
What version of Hugo are you using?
0.100.0
What version of Node.js are you using?
16
What version of Git are you using?
2.25
Additional context
No response

Fixed by latest version.


Add fake gNMI server and license headers

This fake gNMI server has a mechanism for adding new "tasks", or go thread agents that can subscribe to particular values in ONDATRA's OpenConfig tree and write back values to it. It supports Set and Subscribe. For Set it supports both JSON and scalar value inputs.
See gnmi/main/README.md for running/testing the server.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

354 of 540 (65.56%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-9.5%) to 66.205%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

gnmi/gnmit/gnmit.go
110
191
57.59%

gnmi/subscribe/subscribe.go
244
349
69.91%

Totals

Change from base Build<PHONE_NUMBER>:
-9.5%

Covered Lines:
382

Relevant Lines:
577

💛  - Coveralls

It looks like the linter is super strict, I'm not sure if it's suitable at this stage of development, but I'm open to a discussion. I think I want to get some review done before we deal with them. A lot of this is from the copied code from openconfig/gnmi. I'm thinking disabling the linting at the very least in those files makes sense.

In the latest few commits gnmit.Set was modified and systemBaseTask in the fakedevice package is added to demonstrate how config paths can be mirrored to state paths using tasks. Using an image built from this most tests in here passes: https://github.com/openconfig/featureprofiles/tree/main/feature/system/tests (all except the time zone tests).

@marcushines I changed the base commit here, so that's why the CI checks didn't run. We'd need to enable it by removing branches: [main] from the CI config to see it on other branches.


Keep object keys indented on multiline

It will be great if object's keys can be correctly aligned for better readability.

Refer to #74.


Merging state with lodash

This works:
(state, {result}) => {
  state.myData = result.data.myData
  return state
}

This doesn't work:
(state, {result}) => _.merge(state, result.data)

Somehow the first example triggers a render of my component, but the second doesn't, even if the redux-dev-tools show that data is there.

_.merge is mutative. You should never mutate the state in Redux.
This should work: _.merge({}, state, result.data).

I see, but wasn't my first example mutative too?

It was. It's hard to say why it worked without seeing the whole app. Either way don't mutate the state :-).

I switched to lodash.merge because I wanted to avoid mutation, but then everything broke, haha
Thank you for the quick help :)

@gaearon @kay-is I'm learning much about working in an immutable way. How do you deal with nested objects? _.merge() will not remove objects or key/value pairs.

@chandlervdw can you elaborate on what you would expect _.merge to remove? It's an additive operation, so it shouldn't ever leave you with less than you started with!

@jmeas I just learned that it's additive! So, _.extend() seems to be what I want but I want to ensure that I'm understanding things correctly and am learning the right paradigm. If I've got an object which contains an array of key/value pairs, and I want to update the state of that array upon removal of one of those pairs, is _.extend() the best approach? It works, I just don't see it being used by anyone else in the redux community. What am I missing?


Optimization and refinements done for Home-Assistant

This PR contains some optimization done for Home-Assistant
Question: Is there a plan to send this API on Pypi so it will be easier to deploy and manage ?

Looks good! Thanks!
I did some preparations for adding it to Pypi, but never actually launched id. I'll look into it.

@stianaske please upload to pypi if possible.
I think it should be as easy as
pip3 install twine
python3 setup.py sdist
twine upload dist/*

after you create pypi user.

@andrey-git version 0.0.7 has been uploaded to pypi. Appologies for the slow response.


Updated previous acceptance tests and added all possible tests

with the exception of storage attachment and mirror ports which are not supported by fablib currently

I'm assuming @kthare10 you will merge? I don't want to mess with your merge schedule.


feature: allow response from 'Respond to Webhook' node

At present it seems there is only a fixed response to any submission.
Allowing customized response options from the 'Respond to Webhook' node (just like with regular webhooks) would be useful, especially when working with custom html forms or javascript libraries.

A work around I've found for this is the setup a n8n Webhook node that has a Respond to Webhook node down the line.
Then just update the javascript code to post to the webhook url node.
Optional addition: Add a body.innerhtml replace and place the response data to update the form page on the fly:


Trains derailing on track split junctions

BkCommonLib version: 1.14.4-v1
TrainCarts version: 1.14.4-v1 (build: 503)
Spigot version: 1.14.4-R01-SNAPSHOT

Problem or bug: Trains derailing when merging from an angled split track to single straight track even when track is selected and no matter the speed.
Expected behaviour: Trains should continue to move forward when going over track splits no matter the direction.
Steps to reproduce: Look to the screen shots as posted below. pics show the track set up
and what happens when it reaches the merge. The trains are being moved from this building using the /train launch (speed) chat command and unless its on the straight track the train will derail and even if the desired track isn't selected it will stop and squish together. (I do not know if there are console errors but i will try and get the Dev to see when he is available)

Can you post a video about it instead? That looks like a discrepancy between reality and user expectations, so when berger comes back he might do something about it.

I will see what i can do.

I mean, it could also be intentional, as the node has been defined at some point to switch the train towards, idk, say 2, no matter the input direction, unless a switching table has been configured or it has a switcher sign.

we have been manually changing the track nodes for these monorails, but it still happens on this track.

oops dont mind that tried to upload the video here but it didnt work.

Here is the video as requested. https://youtu.be/bEWXZR4Dm_U

One more thing to add, and that is this Bug doesn't seem to happen on all the track splits we have on the server it just seems to be on this kind with the 3 split track.

Should be fixed since bergerhealer/TC-Coasters@d78cc77a9d04aef0da40a3bdcc124c47a60cf7f6
https://ci.mg-dev.eu/job/TC Coasters/80/artifact/target/TCCoasters-1.14.4-v2-SNAPSHOT.jar


Can't drop the item back in the same spot

When dragging an item in the list, it's not possible to put it back where it was taken from without putting it somewhere else first.

Sorry for the late reply. This problem has been fixed in the latest version

@krispern
Sorry for the late reply. This problem has been fixed in the latest version

After updating to version 2.4.0, I get the following error message when running my project:
 ERROR  Failed to compile with 1 error                                                                        15:33:25

This dependency was not found:

* js-draggable-list in ./node_modules/vue-virtual-draglist/dist/index.js

To install it, you can run: npm install --save js-draggable-list
Error from chokidar (C:\): Error: EBUSY: resource busy or locked, lstat 'C:\DumpStack.log.tmp'

Looks like there's a new package that's not in the build?

@krispern
i made a mistake，please update to 2.4.1 to solve this problem

I think I've figured out the issue. The array returned with @ondragend is not ok. The item being moved is still in the same place in the list and the location moved to has been set to null in the returned array.

Can you take a look at your code if I can, I can probably see where the problem is

@krispern
please update to 2.4.2，now you can define the elements you need to drag and drop by yourself，If not set, it will drag a whole row

Works as it used to now. Thank you


Add version of HAProxy BOSH release with new org

HAProxy BOSH release was recently moved from the cloudfoundry-incubator org to cloudfoundry. This change:

Adds a BOSH release for HAProxy using the path for the new org
Removes the very old Cloud Foundry community version of HAProxy BOSH Release
Keeps the cloudfoundry-incubator (I expect this is be necessary so users can access old versions?)

Related discussion in CF Slack https://cloudfoundry.slack.com/archives/C01ABMVNE9E/p1634666203051000
Checklist for submission:

✅ LICENSE and NOTICE files are up to date
✅ at least one final release is checked in on the default repo branch (there's a .final_builds folder)
✅ of use to the general community and will be maintained
✅ github repo must be public
✅ bosh create-release must run successfully against all final releases (the blobstore needs to be public)

if not all final releases are valid, specify a min_version

✅ a README explaining what the repo does
✅ [optional] deployment manifests/ directory contains example manifest

Thanks for merging @lnguyen,
I see that https://bosh.io/releases/github.com/cloudfoundry/haproxy-boshrelease?all=1 is already visible on bosh.io but doesn't have any releases yet. Do you know if there is a way to get the most recent release to appear there, or do we need to wait for there to be a new release?
cheers,
Pete


Apply fixes from StyleCI

This pull request applies code style fixes from an analysis carried out by StyleCI.

For more information, click here.

其实没问题的


39 change readmemd to include package install information

Modify README.md so that it does not tell the users to install via PyPI.
Also added a environment.yml to control conda environment creation.
Closes #39.

Thanks @Marcony1, merging to main.


Suggestion - Missing validation to prevent duplicate entries

I found that there were duplicate entries of the same input (same site with same pattern/regex syntax, e.g. 2 entries of "/www.foobar.com").
I used Microsoft Excel's "Remove Duplicates" function to trim the duplicate.
Is this normal behavior? Maybe certain validation can be put in place to prompt a reminder to user that it was already in the list before and only unique input should be appended?

Unless you edit rules manually, duplicate rules should not be generated because you cannot block again a search result that has already been blocked.
If you edit rules manually, duplicates are not and will not be checked.


translate configmap into chinese

translate configmap into chinese

nice.
/lgtm

@fancc Would you address the feedbacks from Tim?

/lgtm
/approve


add cloodot.com to showcases

📝 Description
Add cloodot.com to the chakra ui showcase page
💣 Is this a breaking change (Yes/No):
No
📝 Additional Information
cloodot.com is omni channel customer experience suite for small businesses.

Hi @thareekanvar. Thanks for opening this PR, but we're not accepting community contributions to the showcase page right now.


Fixes

Travis CI build is failing: https://travis-ci.org/KyranRana/cloudflare-bypass/builds/419885711?utm_source=github_status&utm_medium=notification
Changes look good though.


Icons don't have colors anymore in suggest and symbol widgets

monaco-editor version: 0.22.1
Browser: Firefox, Chrome, Edge (current stable version)
OS: Windows
If you open the suggest widget in a TypeScript sample in the playground, or you select "Go to Symbol..." from the context menu, the icons don't have color anymore. I confirmed this locally so it seems to be an issue with the editor, and not with the playground itself.

published<EMAIL_ADDRESS>


[name of the chart e.g. stable/chart] issue title

Description
I am trying to install prometheus-operator in AWS EKS
But not able to do that for versions higher than 6.4.0. Tried with 7.0.0 as well as last 8.1.2
On some release
Version of Helm and Kubernetes:
Helm and tiller version
Client: &version.Version{SemVer:"v2.16.0", GitCommit:"e13bc94621d4ef666270cfbe734aaabf342a49bb", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.16.0", GitCommit:"e13bc94621d4ef666270cfbe734aaabf342a49bb", GitTreeState:"clean"}
kube:
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.10", GitCommit:"37d169313237cb4ceb2cc4bef300f2ae3053c1a2", GitTreeState:"clean", BuildDate:"2019-08-19T10:52:43Z", GoVersion:"go1.11.13", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.10-eks-5ac0f1", GitCommit:"5ac0f1d9ab2c254ea2b0ce3534fd72932094c6e1", GitTreeState:"clean", BuildDate:"2019-08-20T22:39:46Z", GoVersion:"go1.11.13", Compiler:"gc", Platform:"linux/amd64"}
Which chart:
stable/prometheus-operator
What happened:
Error during install:
helm install   --name mon   --namespace monitoring   stable/prometheus-operator
Error: no kind "Job" is registered for version "batch/v1" in scheme "k8s.io/kubernetes/pkg/api/legacyscheme/scheme.go:30"
What you expected to happen:
Process successfully complete.
How to reproduce it (as minimally and precisely as possible):

Deploy kubernete cluster with eksctl
Install tiller
Try to install mentioned chart

Anything else we need to know:
When I am tryiing to create Job object manually with kubectl from yaml file I am able to create it without any issues.
# mon-prometheus-operator-admission-create
apiVersion: batch/v1
kind: Job
metadata:
......

After mentioned error I see only one pod in monitoring namespace:
[progman@fantom k8s-cluster]$ kubectl get pods --all-namespaces
NAMESPACE     NAME                                             READY   STATUS      RESTARTS   AGE
kube-system   aws-node-2ch8n                                   1/1     Running     0          14m
kube-system   aws-node-st5pb                                   1/1     Running     0          14m
kube-system   coredns-677ff99477-4wzgc                         1/1     Running     0          19m
kube-system   coredns-677ff99477-xsjlf                         1/1     Running     0          19m
kube-system   kube-proxy-bgm7v                                 1/1     Running     0          14m
kube-system   kube-proxy-zg2q6                                 1/1     Running     0          14m
kube-system   tiller-deploy-649db8f75b-qgf6v                   1/1     Running     0          7m37s
monitoring    mon-prometheus-operator-admission-create-4vv98   0/1     Completed   0          3m52s

That is something related to helm 2.16 release
downgrading to 2.15 fixed issue
Was able to install prometheus-operator-8.1.2

follow uphelm 2.16

https://github.com/helm/helm/issues/6894


[Q] Query sequences that are kmers of length 31

Hello, I am trying to query kmers in 150 genomes, plus 4 files corresponding to kmers that are unique to 4 of these genomes. My queries already have a length of 31. I thought that I would not need to change the -e parameter, since the query sequences would be decomposed in kmers of length 31, wich results in the query themselves. I thought the outcomes would be:

the kmer from the query (aka the query itself) is absent: <0.8 of the kmers from the query are present: query is absent: 0
the kmer from the query (aka the query itself) is present: >0.8 of the kmers from the query are present, query is present: 1

But then the output.tsv contains only 1's, which is impossible, at least because a kmer unique to a genome cannot be found in other genomes. I checked if the unique kmers were actually unique, it seems that they are. I ran again my script and changed the -e 0.8 to -e 1. I now have a majority of 0's and kmers that are present in a kmers_unique_to_genome_X are also present only in the genome_X, which makes sense,
I feel like I misunderstood the option -e. I thought it means that if 80% of the kmers from the query are found, then it is present. If there is only 1 kmer in the query, does that parameter allow for an approximation of the kmer sequence ? E.g., it would allow for 6 mismtaches ? (0.2*31=~6)

Hi @Louis-MG,
Sorry about getting back to you about this issue only now, somehow I have missed the notification about this.
Your interpretation of the -e parameter is correct, you did not misinterpret it: using the default -e 0.8 means that if 80% of the kmers from the query are found then the query is present.
I suspect what is happening here is that Bifrost always round down the number of k-mers to find per query so finding 80% of a single k-mer would be rounded down to finding at least 0 k-mer... So when the query/k-mer is not found, it hits the minimum threshold for being found which obviously does not make any sense.
I'll fix this in the next release of Bifrost coming soon. In the meantime, using  -e 1.0 for queries that are k bases long will yield the expected result.
I'll keep the issue open and notify you when the new release is up.
Guillaume

Alright so the upcoming Bifrost version will be rounding to the nearest integer for the number of k-mer to find in a query. Which means that -e 0.8 on a single k-mer query should reports the query as present only if the k-mer is found (it is "rounded up" to one k-mer to find). However, using -e 0.3 would still round down which makes sense for multi-kmer queries but not for single-kmer queries (it does not makes sense to report a query as being found if its only k-mer is not found...). So there will be an additional rule which is that a query can only be reported as present if at least one of its kmer is found.

Next release will mostly bring memory and speed improvements with up to 30% memory usage decrease on "larger" input (HG002 30x Illumina FASTQ but also HG38 FASTA). This will be at the expanse of using a little bit of tmp disk.
That aside, the search  subcommand will offer the option to report either the number of k-mers found per query or the ratio of found k-mer per query (rather than reporting a query as "present" or "absent" based on the usage of -e).
The library libdivide will be replaced with library fastmod so compilation warning that occur when compiling the current version will be gone too.
You can try it now if you would like, it is on the bifrost-robin branch. I'll merge it with main very soon. Note that this new version will break index file compatibility with previous version (so this new version won't be able to read an index file (.bfi) generated prior to this new version).

Thanks, closing the issue now !


This is old. There is no sharing of reports.

Need to edit this:
There's no share in CHROME. When I open the exact same report in Firefox or Edge, share is available.
My company uses Chrome by default.
Chrome Version: Version 87.0.4280.66 (Official Build) (64-bit)

Firefox Version: 83.0 (64-bit)

Edge Version: 44.17763.831.0

In Chrome only, the share item is gone.
This is either a Chrome issue or a MS issue. Sending bugs to both.

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

ID: d7b3989d-4ab1-51f2-6823-970c04f6fba9
Version Independent ID: 673ccbe9-ef77-5c5b-9936-37eaeb4d3762
Content: Filter and share a Power BI report - Power BI
Content Source: powerbi-docs/collaborate-share/service-share-reports.md
Service: powerbi
Sub-service: powerbi-service
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Hi, @kristyler -- hmmm, I just checked Power BI in Chrome and I see Share.

Not sure what's causing your issue. You can contact Power BI support: https://powerbi.microsoft.com/en-us/support/
Hope that helps!


Move Kokoro build files to /tmpfs

Some ObjC builds seem to be suffering insufficient space issue on Kokoro. Moving the build files to /tmpfs which provides more space.
Also fixes a test flake in CFStream-test
Fixes #17814

no longer need this one since it was not the problem


subtract 10 minutes leaves a pixel illuminated

If you press the -10 minutes button, it all appears to work fine until the time ticks down by another minute, at which point you can see it's left the latest pixel illuminated. It stays illuminated even after the time elapses entirely.

However, it is repainting the display waay more often than before, but so far that seems undetectable to the eye.


Download as SVG map

Added posibility to download map as SVG image. In Plain style, background is now white, to keep map always visible after download.

fixes: https://github.com/damonsk/onlinewardleymaps/issues/141

This would be swell ❤


Executing GLTFCamera.new().from_node(null) crashes Godot

Godot version
4.0.alpha.custom_build. b6d102c7c
System information
Ubuntu 22.04 - Nvidia GTX 970, Gnome shell 42 X11
Issue description
When executing
	GLTFCamera.new().from_node(null)

Godot crashes with this backtrace
modules/gltf/structures/gltf_camera.cpp:61:45: runtime error: member call on null pointer of type 'const struct Camera3D'
modules/gltf/structures/gltf_camera.cpp:61:45: runtime error: member access within null pointer of type 'const struct Camera3D'

================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.0.alpha.custom_build (b6d102c7c2d5e9f39f368bf1ebc91a48bf762c42)
Dumping the backtrace.
-- END OF BACKTRACE --
================================================================
Aborted (core dumped)

This example was found by Godot fuzzer - Qarminer, so it is quite unlikelly that this code could be used in real project, but still this should be handled gracefully.
Steps to reproduce
Above
Minimal reproduction project
No response

Fixed in #65327. By the way, it's a static method, so you can test it with GLTFCamera.from_node(null) too.


Added gpg certificates for vendors repositories

Starting with v0.19, leapp enables gpgcheck during upgrade, so we need gpg files to be present on the system.
This change adds missing gpg files and changes paths in repo configs.

Looks good. ELevation works with the data changes.


Track 'React Bricks'

Vendor Site - https://reactbricks.com/
Example Site - See this for example sites - https://reactbricks.com/use-cases/showcase
Category - CMS
Detection - Look for references of 'images.reactbricks.com'

Hey @rockeynebhwani , added thanks!!


Added package glfw

Re-opened pull request https://github.com/ruslo/hunter/pull/480 against the develop branch

Testing here: https://github.com/ruslo/hunter/pull/480#issuecomment-237862975

Uploading:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.765
https://travis-ci.org/ingenue/hunter/builds/150082953

Ура!! Спасибо!!

Ура!! Спасибо!!

You're welcome :)
Released: https://github.com/ruslo/hunter/releases/tag/v0.15.9
Feel free to add wiki page and close the https://github.com/ruslo/hunter/issues/293.

I think we have problems with full paths in cache:

https://travis-ci.org/ingenue/hunter/jobs/150091811

make[2]: *** No rule to make target `/home/travis/build/ingenue/hunter/_testing/Hunter/_Base/9ed9e77/304b278/c07028d/Install/lib/libX11.a', needed by `glfw-example'.  Stop.

But ids: -- [hunter] [ Hunter-ID: b4315bf | Config-ID: 304b278 | Toolchain-ID: c07028d ]

The references to the full paths are in <root-id>/lib/cmake/glfw3/glfw3Targets.cmake:
# Create imported target glfw
add_library(glfw STATIC IMPORTED)

set_target_properties(glfw PROPERTIES
  INTERFACE_INCLUDE_DIRECTORIES "${_IMPORT_PREFIX}/include"
  INTERFACE_LINK_LIBRARIES "/usr/lib64/librt.so;/usr/lib64/libm.so;dl;/usr/lib64/libGL.so;/home/builder/.hunter/_Base/xxxxxxx/6c9a4aa/d17a7ab/Install/lib/libX11.a;-lpthread;/home/builder/.hunter/_Base/xxxxxxx/6c9a4aa/d17a7ab/Install/lib/libXrandr.a;/home/builder/.hunter/_Base/xxxxxxx/6c9a4aa/d17a7ab/Install/lib/libXinerama.a;/home/builder/.hunter/_Base/xxxxxxx/6c9a4aa/d17a7ab/Install/lib/libXxf86vm.a;/home/builder/.hunter/_Base/xxxxxxx/6c9a4aa/d17a7ab/Install/lib/libXcursor.a;/home/builder/.hunter/_Base/xxxxxxx/6c9a4aa/d17a7ab/Install/lib/libxcb.a;/home/builder/.hunter/_Base/xxxxxxx/6c9a4aa/d17a7ab/Install/lib/libXext.a;/home/builder/.hunter/_Base/xxxxxxx/6c9a4aa/d17a7ab/Install/lib/libXrender.a;/home/builder/.hunter/_Base/xxxxxxx/6c9a4aa/d17a7ab/Install/lib/libX11.a;/home/builder/.hunter/_Base/xxxxxxx/6c9a4aa/d17a7ab/Install/lib/libXfixes.a;/home/builder/.hunter/_Base/xxxxxxx/6c9a4aa/d17a7ab/Install/lib/libXau.a"
)

Should this file be added to PACKAGE_UNRELOCATABLE_TEXT_FILES or should *.cmake files be treated differently? I wrongly assumed *.cmake files were treated by the current implementation of hunter_cacheable

Should this file be added to PACKAGE_UNRELOCATABLE_TEXT_FILES

I think no. CMake designed to do it nicely.

it could be that the implementation of glfw's CMakeLists is not correct

Kind of. This is very similar to what is described here: https://github.com/ruslo/hunter/wiki/example.find_package.config#relocation-challenge

Сэнсэй, что делать?

The final goal is not to have full path in glfw*.cmake installed files. It means we must not have commands like target_link_libraries(glfw PUBLIC "<full-path-to-some-library>"). I guess this is what happenning now by target_link_libraries(glfw PUBLIC "${X11_LIBRARIES}"). I need to think, usually introducing imported targets helps.

This is very similar to what is described here: https://github.com/ruslo/hunter/wiki/example.find_package.config#relocation-challenge

Thanks

It means we must not have commands like target_link_libraries(glfw PUBLIC "")

Can you think of a way of making those paths relative? It is a hack it seems, but could (?) be valid.

I need to think, usually introducing imported targets helps.

glfw is using CMake's FindX11.cmake which does not provide those targets, I guess we could either

Do like how you did with boost and have a X11Config.cmake in hunter which creates those targets. Downside is that there is quite a lot of targets to create in X11, but could start with the targets used by glfw
create those targets in a modified FindX11.cmake and try to push it upstream, but I believe it wouldn't help in practical terms because of the minimum required version for CMake being 3.0 for hunter. I just mention it because it breaks my heart that the CMake modules that come by default use old style CMake.

Do like how you did with boost and have a X11Config.cmake in hunter which creates those targets. Downside is that there is quite a lot of targets to create in X11, but could start with the targets used by glfw

This one is best, I guess. Also having the same problem with the glew package, which needs to link to x11.

I like X11Config.cmake approach. Also since everything looks quite pretty for autotools projects we can keep high standards and make generation of *Config.cmake automatic. May be read info from *.pc files? Might be helpful: https://cmake.org/cmake/help/latest/module/FindPkgConfig.html

Also since everything looks quite pretty for autotools projects we can keep high standards and make generation of *Config.cmake automatic. May be read info from *.pc files?

Ok, so let's say we want a function to createxrandrConfig.cmake for the package xrandr which depends on hunter/pkgconfig package x11.

if(NOT TARGET xrandr)
    find_package(X11 CONFIG REQUIRED)
    # should X11 be renamed to x11?
    #   If so, we would have to patch the packages CMake scripts to find_package(x11 CONFIG ...)
    #   If not, we will have to somehow associate the uppercase X11 of the package with lower case x11 - any CMake tricks for that?
    add_library(xrandr IMPORTED ...)
    pkg_search_module(XRANDR xrandr REQUIRED)
    set_target_properties(xrandr PROPERTIES
        IMPORTED_LINK_INTERFACE_LANGUAGES_RELEASE "C"
        INTERFACE_LINK_LIBRARIES "${XRANDR_LIBRARIES}"
    )
    target_link_libraries(randr INTERFACE x11)
endif()

I wonder how the arguments to the function will be for  difference between in cases between X11 and x11 makes this not so trivial :|
Any thoughts?

should X11 be renamed to x11

Yes, I guess if we are planning to do generation automatically it make sense to rename package so it fits *.pc layout: lib/pkgconfig/x11.pc.

pkg_search_module(XRANDR xrandr REQUIRED)

I guess this will not work as is, at least correctly. There must be our custom root variables somewhere, no?

I guess this will not work as is, at least correctly. There must be our custom root variables somewhere, no?

Well, spotted, there seems to be  PKG_CONFIG_USE_CMAKE_PREFIX_PATH, but I can only find it on cmake's 3.1 onwards documentation.
Maybe in this particular case we can have glfw3Targets.cmake + glew's files  as exceptions in PACKAGE_UNRELOCATABLE_TEXT_FILES to not have a broken package? I'm sure the CMake best practice police won't be knocking at your door for it.
I would rather first spend time in https://github.com/ruslo/hunter/issues/218 [ + https://github.com/ruslo/hunter/pull/469 ] as I believe it is blocking your project to have some visibility: [odb-users] Need Help for compiling ODB for iOS. I remember that with hunter, odb was working in iOS when *.la and *.pc files were removed from packages.
But I have to finish pushing these 3D graphics related packages before https://github.com/ruslo/hunter/issues/218 , so I give the students a hunter based build of Computer Graphics course practical assignments. This should also give some visibility plus will help students, as they have Win/Linux/OSX builds. Right now they are only provided Visual Studio projects with the libraries included [ some are not able to setup an Xcode project with the libraries from brew by themselves, so hunter would do the library dependency management ].

Maybe in this particular case we can have glfw3Targets.cmake + glew's files as exceptions in PACKAGE_UNRELOCATABLE_TEXT_FILES to not have a broken package?

You can try it. I don't know how glfw *.cmake modules generated but usually there are build specific configs like *-Debug.cmake or *-Release.cmake so it may be tricky.
Also if we are postponing this enhancement let's open separate issue with description and applied workarounds.

I would rather first spend time in #218 [ + #469 ]

Yep, I remember we do hit this at least 3 times :) and @lucmichalski reported this one once. It would be awesome to have it fixed.


Support symlinking transform.sh into a different directory

Hi Robert,
I like to symlink scripts in ~/.local/bin so I can call them from any
directory and not have to deal with long paths. However, the script does not
work properly if from_to_flat.txt and from_to.txt are not in the same
directory as transform.sh. This PR fixes that problem by first passing $0
to readlink -f and then passing that output to dirname in order to figure
out where those files are located.
I tested this on my Fedora 34 machine. Can you make sure it works on MacOS, as
well? Doesn't it ship with older/different versions of coreutils due to
licensing shenanigans? Is that the point of the case "${output}" in portion
of the sedder() function?
Thanks,
Maxwell

Lots better, thanks!


Expose imperative API

Expose an imperative API for manipulating queries from outside the component.
There are several options for API design:

Hooks (useQueryBuilder?). Not sure how that would connect with a specific <QueryBuilder /> instance, in case there were multiple being rendered.
Refs. Might have to wrap the main component with forwardRef(), but maybe not. See react-select implementation of focus() and blur() methods.
Callback that provides an api parameter, a la AG Grid. This would probably be the easiest to implement.

@zukilover, since you gave me the idea, do you have any preference among the API design choices?

While callback is the easiest one, the original purpose of the request was really to enhance controlElements, so that we could rearrange the interfaces as much as we like. With that in mind, I think refs is the most elegant way of doing it.

Thanks for the feedback, @zukilover. I've been looking at this and I can't wrap my head around a ref-based solution. It seems like it would be fairly trivial if QueryBuilder was a class component, but it's a function component. I don't really want to convert it (back) to a class component, and other methods using refs (forwardRef, using a custom ref-type prop, etc.) don't seem to accomplish the goal.
So, considering all that, I'm leaning toward the callback solution. It would be fairly simple to implement, and it's an acceptable solution in other libraries (e.g. AG Grid which I mentioned above). Should end up working something like this:
const App = () => {
  const [api, setApi] = useState();

  return (
    <>
      <div>
        <button onClick={() => api?.addRule({ field: 'f1', operator: '=', value: 'val' }, [])}>
          Add rule
        </button>
      </div>
      <QueryBuilder onLoad={e => setApi(e.api)} />
    </>
  )
}

Thoughts?

@zukilover - After working on the callback solution for a while, I realized that's not going to work either. Without a class instance to hang on to, it's really hard to keep the object references updated.
The best I could come up with is a set of utility functions (add, remove, update, move, and clone) that perform modifications to a provided query object and return a new query object. Would that even be useful?

@jakeboone02 I really appreciate your effort on this enhancement. Although, utility functions will not really add that much of an improvement because we can actually do that per implementation basis without having to expose those abilities from within the library.
I would really like to help with the ref approach, that in my scenario will not only add enhancement to the library but also solve another new problem that I have related to multiple instances of react-dnd HTML5 backend. I could not provide details to the problem nor contributing with the enhancement at the moment. If this sounds alright with you, we could close this now and revisit later when we have more effective solutions.

Yeah, it's probably better to wait to address this until after 4.0 is released, anyway. Lots of churn in the codebase at the moment.


New labels for OSBS

Labels now should follow spec at https://github.com/projectatomic/ContainerApplicationGenericLabels/blob/master/vendor/redhat/labels.md

[test]

Rebase needed to get RHEL CI working - nss_wrapper is missing now.

[test]


[RFE] Improve handling of dynamicSchemaSpec

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
https://github.com/rancher/rancher/pull/40730 was initially merged for https://github.com/rancher/rancher/issues/40609, introducing the dynamicSchemaSpec field under the provisioning cluster resources machinePools list to prevent automatic and unintended machine rollout when switching between node driver versions. Built-in and custom node drivers may be updated to add new fields, typically when a new version of rancher-machine is released and vendored in as part of a rancher upgrade, or a new version of the custom node driver is released respectively. This approach works for fetch based update methods (such as Edit Yaml or Edit Config within the Rancher UI), as well as path based update methods, however declarative (i.e. desired state) methods such as terraform or fleet drop this field from the request. As such, this can result in unexpected reprovisioning to the user, as removal of this field will cause it to be repopulated, and the change in machine-template-hash by no longer dropping the new fields added since initial provisioning will cause a rollout. While potential workarounds should be investigated in the short term for both fleet and terraform, it is worth investigating a more permanent long term solution.
Describe the solution you'd like
A clear and concise description of what you want to happen.
There are a number of potential solutions, but no clear path at this time. The team will evaluate options internally and update this ticket accordingly.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
SURE-7751

Ticket #44618 - Test Results - ✅

Scenario
Test Case
Result

1.
Dynamic schema repopulation test
PASS

Verified with Docker on Rancher v2.9-3c4ccdc5bc9fde3510089153b5ad58fdbe604880-head:
NOTE: Tested on RKE2/K3s
Scenario 1: Dynamic schema gets repopulated

Provision an rke2 cluster with the dynamic schema
Wait for the cluster to finish provisioning
Remove the dynamic schema

Results: the dynamic schema repopulates and the cluster doesn't re-provision.


[spaceship_ember] yarn workspaces compat

Is your feature request related to a problem? Please describe.
When the ember app is using Yarn workspaces, the ember version is not show in the prompt.
After having a quick look at the current implementation, I believe this is because we check the presence of both ember-cli-build.js and node_modules/ember-cli/package.json in ember.zsh.
Describe the solution you'd like
The ember version should be shown when inside that app folder just like it is already the case when not using yarn workspaces.
Describe alternatives you've considered
We could also display the ember version when we enter the yarn workspaces root folder, but what would happen if there are multiple ember apps inside the workspaces?

Ember is section is moved to spaceship-ember. We're cleaning up old issues.


add highlighting of all messages from a certain user

like what better twitch tv does, where it highlights all messages from the list of users you give it

Agree with this, really really wanting something like this

https://github.com/fourtf/chatterino2/pull/564


[python][tests] transfer test_save_and_load_linear to test_engine

test_basic.py contains tests only for Dataset and Booster classes. There is train() function which we test in test_engine.py file in test_save_and_load_linear test.
<No changes, simple copy-paste.>

Azure DevOps might be experiencing an outage

even though there are no issues on https://status.dev.azure.com/

Azure DevOps might be experiencing an outage

even though there are no issues on https://status.dev.azure.com/

Azure DevOps might be experiencing an outage

Microsoft-hosted agents are running right now... Self-hosted ones are stuck.

Azure DevOps might be experiencing an outage

Microsoft-hosted agents are running right now... Self-hosted ones are stuck.


[CHEF-2207] Add gemfile and development dependencies to chef client

Add gemfile and development dependencies to chef client

This was previously merged. Please see the ticket on http://tickets.opscode.com for more information. In the future, please provide a link to the pull request in the ticket to help us find and close them when we close tickets.


fix source of input bam in  the methods.json file for variant calling

Thanks @hbeale for spotting this.
The methods.json for variants still claims the bam is coming from ucsc_cgl-rnaseq-cgl-pipeline when instead it is actually coming from ucsctreehouse-bam-umend-qc - update the code here with correct hash.
We should probably also retroactively correct the outputs from this version as the line; can detect by the line's change from sorted.bam to sortedByCoord.md.bam:
https://github.com/UCSC-Treehouse/pipelines/commit/dca77ed4987640ef949cde0aeaf50bc49a3d0364#diff-65218180447789ae9b6a89838c1966c9L485

master's Makefile still has the incorrect variant on the expression vs. qc bam. Looks like there have also been some other changes to treeshop so I'm hesitant to do the fixes. @aglyle or @e-t-k do you want to update and remove the other branches or I can if there are no other changes. Not exactly sure what katrina et. al. are running - hopefully not master...

@aglyle @e-t-k Ignore - the master Makefile is pulling from qc for variants...brain toast from dna nexus hacking...time to make dinner...


Directly use fold expression in TypeListHasPixelIDValue

The lambda calls are removed.
Also simplify the has_type expression.

@N-Dekker Thought you might find these fold expressions interesting.


Remove the Model abstract type, simplify model migration code.

This PR removes the Model abstract type which was overly constraining (preventing one and the same struct from being a model of many different theories). One purpose the Model type served was to make it easy to see what Julia types were associated with the theory type constructors, but this functionality is now provided by impl_type methods which get defined by @instance.
This also led to an opportunity to simply model migration code, which is no longer handled convolutedly within the module of a @theorymap but instead is a function (which calls eval to create a new struct which just wraps the input model). If we start actually using model migrations and get worried about generating too many structs, it wouldn't be hard to cache the inputs to this function.
All interesting changes are in ModelInterface.jl. Lots of tiny changes (mostly removing <: Model{...} are in other files.

This PR's change makes life much easier in many ways, including those in the original description and also things like allowing Models to be subtypes of other abstract types (rather than forcing any type that is used as a Model to be a subtype of GATlab's particular abstract type). But I've realized now that GATlab's getindex trick inadvertently performs type piracy. Something like following code is generated for any theory T and constructor f:
Base.getindex(::typeof(f), m::Any) = args -> f(WithModel(m), args...)

However GATlab doesn't own any of getindex, f (since we may be overloading some external method), or whatever type m is, now that m is not forced to be a Model{Tuple{...}}.
There are a few ways to address this.

Require that one index the method name with a WithModel. This makes the sugar less sweet - it's not that much more convenient then just passing in WithModel(m) as the first argument, though it is much more legible how the first parameter is quite different from the rest.
Just drop the getindex sugar. We can still use @withmodel to automate the insertion of WithModel arguments. The problem with @withmodel is that it's really only convenient when you have a bunch of different methods all indexed by the exact same model.
Reintroduce abstract type Model end but retain this PR's handling of type parameters (so the same model can still be used for many different theories, which is certainly the most important benefit that came from this PR. We should ask ourselves if we ever want to be able to declare such-and-such (arbitrary type) is a model of such-and-such theory (e.g. I declare that Int is a model of ThCategory and my implementation is that of categories generated by path graphs vs I'm forced to create a type struct PathGrphCat <: Model i::Int end and then use that).

I came to this realization because I wanted to write pullback[FinSet()](f, g) in some test file. However, pullback[m] is just sugar for limit[m](Cospan(f,g)), where limit is the name of the term constructor  that actually appears in ThCategoryWithPullbacks. So because pullback does not explicitly appear in any theory, there was no getindex method generated for it. So I'd have to write pullback(WithModel(FinSet()), f, g). This surprised me because I hadn't had this problem for product or equalizer etc., but that's because those names have appeared as constructors in some theory (doesn't matter which), thus the getindex(::typeof(product), m) method gets generated. This seemed bad.
What would be nice is to just define once
Base.getindex(any_method, any_model) = args -> any_method(WithModel(any_model), args...)

Which is blatant type piracy that brought this all to my attention.
So, one argument for option 3 above is that we could do this:
Base.getindex(any_method, any_model::Model) = args -> any_method(WithModel(any_model), args...)

Or perhaps with any_method::Function.

I think that requiring a fixed super type for models or methods would really limit the utility of this whole goal. Can we provide a macro that is a thin wrapper around function definition that lets users register the method with the model and generate the right method definition to avoid piracy?
The problem is that we can't overload getindex withour specializing on the type of the model or the type of the function. But if we used a manual opt-in, you would have those types to define specialized methods.

I think you're suggesting a macro that take a function name (e.g. pullback) and defines a method
Base.getvalue(::typeof(pullback), m::WithModel{T}) where T = xs -> pullback(m, xs...)

I agree this is nicer than making some random theory with pullback as a term constructor in order to make @theory do this. One could even do this for specific T's, though I don't see how that could be useful yet.
This doesn't address the problem of needing to sprinkle in WithModel when one calls compose[WithModel(nothing)](nothing, nothing) but I think that's a minor inconvenience. Also I think we should just replace WithModel with Model. Then Model is a wrapper one encases a value in to say "use this as a model" (in particular, when indexing a method name).


Update cloud-seats-and-users.md

After the UI update it's mandatory to fill in Payment and Billing information before changes can be saved ticket: https://dbtcloud.zendesk.com/agent/tickets/48344
What are you changing in this pull request and why?

Checklist

[ ] Review the Content style guide and About versioning so my content adheres to these guidelines.
[ ] Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."

Adding new pages (delete if not applicable):

[ ] Add page to website/sidebars.js
[ ] Provide a unique filename for the new page

Removing or renaming existing pages (delete if not applicable):

[ ] Remove page from website/sidebars.js
[ ] Add an entry website/static/_redirects
[ ] Ran link testing to update the links that point to the deleted page

nice one, thnks so much @Lana-hl ! great contribution ✨going to to make one small tweak and merge this for you!

deploy preview looks good @Lana-hl ,going to merge.
i also think im going to flag this in the feedback channel and product board because the UI should have a visible cue that lets ppl know those fields are mandatory

i'm also going to update the screenshots Lana!