DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/OPS-E2E-PPE/docs-archive-test-source

Docs Build status updates of commit a8877fe:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Release_Archive_master_2020-01-14-10-14-17 has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/Release_Archive_master_2020-01-14-10-14-17

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Fix numerical formatting on CritDamageBonusScale

"CritDamageBonusScale": 1 (meaning 1x crit dmg) was added as a stat to many heroes with recent update, though in game its displayed as 0% (meaning +0% crit dmg). Currently, this means its displayed on the wiki in stat infoboxes as 1%.
Reformat the numerical display the same way its reformatted here for CritDamageReceivedScale https://github.com/deadlock-wiki/deadbot/blob/f2512aabb57d2985af3244e63dcf72d7804858b0/src/parser/parsers/heroes.py#L35-L37.
Then reparse the data, and ensure it displays as 0 for 0%.

@Surxe I'm pretty sure "invalid" means the issue is invalid and shouldn't be done. Is that what you meant?

@Surxe I'm pretty sure "invalid" means the issue is invalid and shouldn't be done. Is that what you meant?

Ah I interpreted it differently, ill just swap to bugfix.


make rapids-configure-conda-channels idempotent

While testing some RAPIDS projects, I've found it helpful to do something like this to test conda builds.
docker run \
    --rm \
    -v $(pwd):/opt/rmm \
    -w /opt/rmm \
    -it rapidsai/ci-conda:cuda12.2.2-ubuntu22.04-py3.9-amd64 \
    bash

# build a conda package
ci/build_cpp.sh

(example: https://github.com/rapidsai/build-planning/issues/54#issuecomment-2072893399)
In that interactive case, it's useful to be able to modify the source of the project and directly run that ci/build_* script again.
Many of the RAPIDS projects' build scripts include a call to rapids-configure-conda-channels near the beginning. (GitHub search. That interrupts this workflow because that script is not idempotent... it raises an exception if asked to remove a channel that isn't currently in the conda configuration.
CondaKeyError: 'channels': 'rapidsai' is not in the 'channels' key of the config file

This proposes changing the behavior of that tool:

before: try to remove {channel} from the conda configuration, raise an error if {channel} isn't present there
after: if {channel} exists in the conda configuration, remove it, otherwise warn that it already doesn't exist there

Notes for Reviewers
I can think of 2 reasons we might decide not to merge this:

having this be a loud error means typos will be caught at CI time... e.g. trying to remove a channel called rapidz (note the z) would result in a CI failure on main but just a log message on this branch
this branch's changes make a fairly simple script more complex, which makes it harder to understand

I think these risks are worthwhile in exchange for removing some friction from local development on RAPIDS projects. I'm especially not too worried about the typo problem, because the channels this tool references are string literals within the tool, not coming through other configuration that's customized by projects.
How I tested this
in a container, using one of the images we use when building wheels in CI (click me)
From the root of this repo, on this branch.
docker run \
    --rm \
    -v $(pwd):/opt/gha-tools \
    -w /opt/gha-tools \
    -it rapidsai/ci-conda:cuda12.2.2-ubuntu22.04-py3.9-amd64 \
    bash

Checked the current set of configured channels.
conda config --get channels

That printed the following.
--add channels 'nvidia'   # lowest priority
--add channels 'conda-forge'
--add channels 'pytorch'
--add channels 'dask/label/dev'
--add channels 'rapidsai-nightly'
--add channels 'rapidsai'   # highest priority

Ran the script.
./tools/rapids-configure-conda-channels

Saw this in its logs
[rapids-is-release-build] is not release build

Checked the channels again.
conda config --get channels

As expected, rapidsai was removed.
--add channels 'nvidia'   # lowest priority
--add channels 'conda-forge'
--add channels 'pytorch'
--add channels 'dask/label/dev'
--add channels 'rapidsai-nightly'   # highest priority

Ran the script another 5 times, just to prove that it was really idempotent.
for i in {1..5}; do
    ./tools/rapids-configure-conda-channels
done

All of those succeeded, and the expected warning was issued.
[rapids-is-release-build] is not release build
[rapids-configure-conda-channels] channel 'rapidsai' not found via 'conda config --get channels'
[rapids-is-release-build] is not release build
[rapids-configure-conda-channels] channel 'rapidsai' not found via 'conda config --get channels'
[rapids-is-release-build] is not release build
[rapids-configure-conda-channels] channel 'rapidsai' not found via 'conda config --get channels'
[rapids-is-release-build] is not release build
[rapids-configure-conda-channels] channel 'rapidsai' not found via 'conda config --get channels'
[rapids-is-release-build] is not release build
[rapids-configure-conda-channels] channel 'rapidsai' not found via 'conda config --get channels'

Repeating this same process on main, the second call fails like this:
CondaKeyError: 'channels': 'rapidsai' is not in the 'channels' key of the config file

Thanks for reviewing!
I'm proposing not || true-ing it because that'd hide mean these types of issues wouldn't cause an immediate failure:

conda config no longer recognizing the arguments --system or --remove
channels itself not being a valid key in conda config anymore
conda executable not being found on PATH

I'll defer to you. If you think the added complexity in the current state of this PR isn't worth the protection against those types of issues, I'll revert out all the jq stuff and add || true instead.

@ajschmidt8 thoughts? Just noticed that this PR has been sitting for a bit.

also, i noticed this script is missing our standard set -euo pipefail. not sure if it's worth adding in this PR.

also, i noticed this script is missing our standard set -euo pipefail. not sure if it's worth adding in this PR.
I just added this in https://github.com/rapidsai/gha-tools/pull/104/commits/f1464ce274d5cca1b406adbea3b221101b5f73d4
Tested my new changes following the "How I tested this" steps in the description of the PR, all seemed to still work the expected way.
I'll wait til you have another chance to review before I merge this @ajschmidt8

Thanks again for the thorough review and for teaching me some new jq things @ajschmidt8 !


Wife 3 release prep

test version that sands off the rough edges in preparation for release version
everything is rerouted to old calc

almost everything is fixed and ready with the exception of display mismatches on eval with internal score due to missing mine hits and hold drops


Suggest details text doesn't wrap

I'm not sure if this is extension specific or vscode in general.
When using intellisense in vscode and trying to show more details for current suggestion, the header text (colored) does not wrap, but the description does. This makes for bad UX because mouse interaction is needed to scroll horizontally.

This behaviour is different to that of a mouse-hover popup with details, where both header text and descriptions wrap as expected.

I don't know if I'm even in the right place with this issue, I would appreciate if someone could confirm or redirect me if appropriate.
Additionaly, now even the horizontal scroll bar is missing, and only way to get full method signature shown is to resise the suggest details enough to the right, which might not even be possible(!) sometimes when the method signature is too long.

might be another duplicate of #6275?


esc_url_raw not listed as sanitizing function

According to the Codex, esc_url_raw should be used for sanitizing URLs, however the following fails WPCS:
$referer = esc_url_raw( $_SERVER['HTTP_REFERER'] );

Detected usage of a non-sanitized input variable: $_SERVER
Should this be added to the list of sanitizing functions? There isn't a sanitize_url, but there was, and it's now in deprecated.php and calls esc_url_raw. If this isn't the right function, if you could point me in the right direction as to which function should be used for sanitizing URLs, I'd greatly appreciate it! :smile:

Yes, I think you're right.

Awesome, thanks!


Allow configuring the provided fetch implementation

The documentation says that the provided fetch implementation can forward the Cookie and Authorization headers. I would like to configure on a root level, exactly what headers are forwarded by default.

Never mind, I think I found the solution.
  createPageHooks(requestContext) {
    requestContext.fetch = (input, init) => {
      init ??= {};
      init.headers ??= {};
      init.headers["some-header"] = requestContext.request.headers.get("some-header");
      return requestContext.fetch(input, init);
    };


[Diagnostics]: Associates logs to the correct trace/span if there is one.

Fixes #5190

(I'm running integration tests locally).

Just added a fix for test code (I had swapped a couple of IDs) that I caught while running integration tests in local. Everything is green now. Ready for review.

(Travis is failing to install .NET Core, will wait a little and retry)


Story 419757: Omit duplicate symbol already defined in Minecraft.Shared lib

Env::Default() is also defined in https://github.com/Mojang/Minecraftpe/blob/main/handheld/src/common/leveldb/LevelDbEnv.cpp, which results in a duplicate symbol error in Bedrock builds with unity disabled.
I verified that the default build (unity enabled) uses the method in src/common, so do we need this copy at all? The method already does almost nothing:
if (default_env == NULL)
    InitDefaultEnv(NULL, NULL, NULL);

Since #if 0 was already there and retaining changes in a third-party lib can make it easier to upgrade, I just expanded it to remove the whole method. Only concern is that I'm missing some other use case...

I didn't think we even compiled this file in our builds anymore.

This change is not needed, thanks Will!


BFF pattern to work with this SDK

Issue and Steps to Reproduce
Hello @guillaume-chervet, Recently our organization decided of creating common BFF proxy to serve all the OIDC / SSO needs to all the internal apps. May I know if you have any example or migration guide to switch from client/service worker appraoch to BFF proxy with custom routes/ configurations. I would like to continue using this library so asking this question especially the keepalive session etc.

Versions
ANy
Screenshots
Expected
Actual
Additional Details
Let me know if you require, additional information.

Installed packages:

Hi @pgangwani , if you are using a BFF it use cookies to authenticate with your BFF. You do not need this library any more. I think personally that using BFF mandatory for internal application inside an organisation is a time to market killer 😜 BFF is a nigthmare for doing thing like sharable widget.


GRUB Display Resolution width and height swapped?

This may be unique to my system but for me mentioning the width first works better.
I have a 1080p screen and entered this to my grub config: GRUB_GFXMODE=1080x1920x32. As I rebooted the theme was blurry and not in fullhd. I changed "GRUB_GFXMODE=1080x1920x32" to "GRUB_GFXMODE=1920x1080x32" because you mention the width first in programming. After rebooting the resolution is perfect.
I think "GRUB_GFXMODE=[height]x[width]x32" has to be "GRUB_GFXMODE=[width]x[height]x32".
It could be because I use linux arch and have weird nvidia drivers. Sorry for my bad english. Anyways, it still helped my to find the right setting.

Hey @LetzteFee
Yeah, this ( GRUB_GFXMODE=[width]x[height]x32 ) is how it should be, I might have missed it, thanks for letting me know. Normally, grub will set it for you during installation, so we don't have to worry about that and this type of error is extremely unlikely.

Thank you for fixing ;)


Add stats subcommand to get quick statistics about an index

I'm using this command to collect metrics for the scip-typescript announcement.
Test plan
Manually execute go run github.com/sourcegraph/scip/cmd stats and see it print out information like this
// $ go run github.com/sourcegraph/scip/cmd stats --from /Users/olafurpg/dev/coder/code-server/index.scip
{
  "documents": 73,
  "linesOfCode": 6524,
  "occurrences": 14653,
  "definitions": 2505
}

This implementation isn't perfect and there are no tests but this command has already been very useful for the scip-typescript blog post so I think it's OK to merge it as is.

Superseded by #14


Revert codecov change

What changed?
Revert codecov change

Why?

How did you test it?

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 018ea123-88b5-4bb0-97b9-c6d5c4b96eb1
Details

0 of 0   changed or added relevant lines in 0 files are covered.
74 unchanged lines in 13 files lost coverage.
Overall coverage decreased (-0.04%) to 65.796%

Files with Coverage Reduction
New Missed Lines
%

common/peerprovider/ringpopprovider/config.go
2
81.58%

service/matching/db.go
2
73.23%

service/matching/taskListManager.go
2
79.7%

common/persistence/historyManager.go
2
66.67%

common/log/tag/tags.go
3
50.18%

common/persistence/statsComputer.go
3
96.07%

service/history/task/fetcher.go
4
85.05%

service/matching/taskReader.go
5
84.08%

common/persistence/nosql/nosql_task_store.go
5
61.95%

common/task/fifo_task_scheduler.go
5
82.47%

Totals

Change from base Build 018ea11d-86da-4c81-b91c-dafc755f3c7a:
-0.04%

Covered Lines:
96285

Relevant Lines:
146338

💛  - Coveralls


Add a build.debug.yaml to examples/

... where we don't use --minify with Dart2JS.

We could also do this with an index.debug.html, which might be nice


ee_loss becomes "nan" type during training of the Retargeting model.

Hi there, I recently met a problem during training the retargeting model by myself. That is the "ee_loss" always became "nan" type during training,
Have you ever met this problem before?
Many thansk!

Hi. It seems that I have met the same problem. Would you mind telling me how you solve this problem? Thanks a lot!

Hi. It seems that I have met the same problem. Would you mind telling me how you solve this problem? Thanks a lot!

Sorry, I haven't solve that problem yet. But the author has published and updated his training script,  I thought this problem should be solved. I'm not sure whether you pull the latest code from the repository?

Hi. It seems that I have met the same problem. Would you mind telling me how you solve this problem? Thanks a lot!

Sorry, I haven't solve that problem yet. But the author has published and updated his training script, I thought this problem should be solved. I'm not sure whether you pull the latest code from the repository?

Thanks for your reminding. But I have pull the latest code from the repository. Maybe there is something wrong when I made my custom dataset.

Same problem. Do you solve it? Is it caused by your custom dataset? @MikeXuQ


TypeScript: Invalid output constructor: ; in 0.2.23

Wow, the latest release of wasm-bindgen is absolutely amazing!
I might have found a little bug in the TypeScript generation, though.
Using this Cargo.toml file:
[package]
name = "wasm-bindgen-ts-constructor"
version = "0.1.0"
edition = "2018"

[lib]
crate-type = ["cdylib"]

[dependencies]
wasm-bindgen = "0.2"

And this src/lib.rs file:
extern crate wasm_bindgen;

use wasm_bindgen::prelude::*;

#[wasm_bindgen]
pub struct Demo(u8);

#[wasm_bindgen]
impl Demo {
    #[wasm_bindgen(constructor)]
    pub fn new() -> Demo {
        Demo(0)
    }
}

Run the following:
cargo build --target wasm32-unknown-unknown --release
mkdir -p out
wasm-bindgen target/wasm32-unknown-unknown/release/wasm_bindgen_ts_constructor.wasm --out-dir out --no-modules

This will generate the following wasm_bindgen_ts_constructor.d.ts file:
/* tslint:disable */
export class Demo {
free(): void;
 constructor(): ;

}

The constructor(): ; syntax appears to be invalid.
Expected output: constructor();.
Thank you for a really promising tool!

Oh dear sorry about that! This should be fixed in https://github.com/rustwasm/wasm-bindgen/pull/921 and I've opened https://github.com/rustwasm/wasm-bindgen/issues/922 as well to track better testing here!


Related Safe Addresses

Related Safe Addresses
0x23cBF6d1b738423365c6930F075Ed6feEF7d14f3
0x822fdbd45b2bbdce402103d63a885c1253c6190e
0x16e016e5d801388a2682cc8369ffce0ad89f81d6
0x6159275fea1f9a6e197bd35cd317152fe6f08423
0x72d6c0c43067ac24a802508bebd803c9dc67d290
0x3b6befb464d620e956439fff48ab149e2e37048f
0xF15aBf59A957aeA1D81fc77F2634a2F55dD3b280
0x047bA525d9961CaA83FD37d4E209B10B96a93461
0x9f4cFcDf4942dD1e6aF2e0b53E70524F31708CE7

Reasoning

this address '0x23cBF6d1b738423365c6930F075Ed6feEF7d14f3' transfered 0.000001 Ether to the other 7 address within 15 minutes. and they are all on the airdrop list .

Methodology
i checked the csv list one by one and found this address '0x23cBF6d1b738423365c6930F075Ed6feEF7d14f3'. it sent same amount of ETH to different addresses, and all those address are on the csv list.

At least the following provided addresses aren't Safes:
https://etherscan.io/address/0x23cBF6d1b738423365c6930F075Ed6feEF7d14f3 is not a Safe but an EOA
https://etherscan.io/address/0xF15aBf59A957aeA1D81fc77F2634a2F55dD3b280 is not a Safe but a legacy Gnosis Multisig
Henc marking this as invalid.


[Defender (RiskIQ) - EASM] Api version 2024-03-01-preview

Data Plane API - Pull Request

API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.

Link to API Spec engagement record issue:

Is this review for (select one):

[ ] a private preview
[x] a public preview
[ ] GA release

Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified. Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.

Design Document:
Previous API Spec Doc: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/riskiq/data-plane/Microsoft.Easm/preview/2023-03-01-preview/easm.json
Updated paths:

Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.
Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
❔Got questions? Need additional info?? We are here to help!

 Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

💬 Teams Channel
💌 email

Click here for links to tools, specs, guidelines & other good stuff
Tooling

Open API validation tools were run on this PR. Go here to see how to fix errors
Spectral Linting
Open API Hub

Guidelines & Specifications

Azure REST API Guidelines
OpenAPI Style Guidelines
Azure Breaking Change Policy

Helpful Links

Schedule a data plane REST API spec review

Checks stuck in `queued` state?
If the PR CI checks appear to be stuck in `queued` state, please add a comment with contents `/azp run`.
This should result in a new comment denoting a `PR validation pipeline` has started and the checks should be updated after few minutes.

.Net CI pipeline failed because the model name broke the .NET SDK Analyzer rule AZC0030 (see following). You may need to customize the model's name for csharp or ask approval from arch board and then suppress it.
error AZC0030: Model name 'ObservationResponse' ends with 'Response'. Suggest to rename it to 'ObservationResult' or any other appropriate name. [/mnt/vss/_work/1/s/azure-sdk-for-net/sdk/easm/Azure.Analytics.Defender.Easm/src/Azure.Analytics.Defender.Easm.csproj::TargetFramework=netstandard2.0]

/azp run

/azp run

I checked this pr locally and the code could be generated correctly but we have an issue when generating apiView (tracked here). Will take a look when back from holiday.

/azp run

/azp run

There seems to be major changes to the new api-version.
Make sure you had scheduled an API review meeting.

There are no breaking changes so this PR wasn't labeled that we need a review. We are only adding new endpoints, not making breaking changes. Do we still need a review? If so, why?

There seems to be major changes to the new api-version.
Make sure you had scheduled an API review meeting.

There are no breaking changes so this PR wasn't labeled that we need a review. We are only adding new endpoints, not making breaking changes. Do we still need a review? If so, why?

https://eng.ms/docs/products/azure-developer-experience/design/api-review


How to test the turi detection model on video ?

Is there a built-in function for prediction on videos ?

Currently TuriCreate has no support for video. However that's a great feature request. I'll leave this issue open to track that feature request.
@ShreshthSaxena - please give us more details about what you would like TuriCreate to support. Are you using an image classifier model, an object detection or some other type of model?

I'm using an object detection model for detecting objects in videos.
Is it possible to export the turicreate model to a format other than 'mlmodel' (ex h5) where I can use it to predict on videos?
Makes it better to test the model instead of having to run it on an app every time.
Thanks

@ShreshthSaxena - it is not possible to export TuriCreate models to anything except CoreML (or TuriCreate's own binary format).
I'm going to close this issue as a duplicate of #343.


Deployment error: When processing VM extension

We are trying deploy Elasticsearch(Self-Managed) using Azure console. Selected existing Virtual network and Subnet  which are in a different resource group. Deployment is failed while processing VM extension. We are getting below error for all data node VM extensions.
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"Conflict","message":"{\r\n "status": "Failed",\r\n "error": {\r\n "code": "ResourceDeploymentFailure",\r\n "message": "The resource operation completed with terminal provisioning state 'Failed'.",\r\n "details": [\r\n {\r\n "code": "VMExtensionProvisioningError",\r\n "message": "VM has reported a failure when processing extension 'script'. Error message: \"Enable failed: processing file downloads failed: failed to download file[0]: failed to download file: http request failed: Get [REDACTED] dial tcp <IP_ADDRESS>:443: i/o timeout\"\r\n\r\nMore information on troubleshooting is available at https://aka.ms/VMExtensionCSELinuxTroubleshoot "\r\n }\r\n ]\r\n }\r\n}"}]}
Could you please let us know if we need to allow any NSG rules on the existing subnet?

The template assumes that VMs onto which software is deployed can connect to the public internet, in order to download the Elastic Stack packages from https://artifacts.elastic.co and supporting Ubuntu packages through apt get. For example, for Elasticsearch
https://github.com/elastic/azure-marketplace/blob/fb6690264515d8906d565c072ea8ac2830dbcb7c/src/scripts/elasticsearch-install.sh#L387-L388
and packages
https://github.com/elastic/azure-marketplace/blob/fb6690264515d8906d565c072ea8ac2830dbcb7c/src/scripts/elasticsearch-install.sh#L1137-L1163
The template takes care of this for a new vnet but if you have an existing vnet with an NSG in place, it'll need to allow this outbound traffic for the template to complete successfully.


Integrate cyber chef

Integrate CyberChef [https://github.com/gchq/cyberchef] for source / dest payload decoders.

Part of 0.19.0


Array of string

We can't bind array of strings.
var arr = ['David','Jhon','Lisa'].
My webApi returns array of string for many methods.
Thanks,
Kulwinder

Agree with this. Sometimes we need to use simple string arrays.
Is there any way to do this with the current version of the project without any hack?

Incase the options list is not fixed, but infact a REST resource,  we cannot change the producer to tailor the JSON in our required format. This I think needs to be taken up so as to handle simple list of array.

💯

Currently possible in 2.0.0-beta

Thank you @pkempenaers 🎉 🍰 🎈


storybook, storyshots, convert to hooks

good enough for government...
we can remove the class component thing now since it's all hooks

Were you able to get this to work by npm-linking to another project? When I try to do this, I'm getting:


[bitnami/redis] Use buster in CI

Use buster in CI
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] DCO signed
[X] Chart Version bumped
[X] Variables are documented in the README.md
[X] Title of the PR starts with chart name (e.g. [stable/mychartname])

/LGTM
Please @sameersbn or @javsalgar  , could you merge this, please?


Get npsso from email and password

Do you have any idea on how to get the npsso using email and password of the account rather than going to that url to get the npsso

Sorry, to the best of my knowledge this is not possible.


Add marking and sweeping time as Process stat

Add marking and sweeping time as GC stats. It was introduced in https://bugs.ruby-lang.org/issues/19437
I think we should also add GC.latest_gc_info[:major_by]. I can do it in another PR.
--- a/lib/prometheus_exporter/instrumentation/process.rb
+++ b/lib/prometheus_exporter/instrumentation/process.rb
@@ -65,6 +65,7 @@ module PrometheusExporter::Instrumentation
       metric[:allocated_objects_total] = stat[:total_allocated_objects]
       metric[:marking_time] = stat[:marking_time]
       metric[:sweeping_time] = stat[:sweeping_time]
+      metric[:last_major_by] = GC.latest_gc_info[:major_by]

We could store it as a last state like kube-state-metrics does for pod last state.
It's a fast method. At the moment it's not possible because gauge are only numeric in prometheus_exporter.
cc @mtparet @byroot

should we only add the matrics on Ruby versions that have it?

@SamSaffron Yes it's a good idea. I made the change. Do we want to test this?


some improvements

Hi, I've made some minor changes to the code base, including:

update of development dependencies (RSpec 3.4, recent webmock)
re-enable jruby-head on Travis, but allow for failures (I think, this will be fixed soon)
some workarounds/adjustments in the test code

I also started with a make-Rubocop-happy chore (only lib/ for now), maybe tomorrow I'll cleanup the spec/ dir, too.
--Dominik

@dmke These look like good changes across the board. Thanks!
Do you want me to go ahead and merge this in, or did you want to add more commits to this? I'm fine if you want to send those in under a separate PR.

You can go ahead and merge this (and I'll create another PR with the next batch of patches).

Awesome, thanks!


PHP 5.4

Short array syntax
Traits (maybe)

@hranicka @vojtech-dobes @haltuf Are you ok with it?

I lean to be conservative in adopting new features, when it does not have any practical meaning.
Short array syntax is rather cosmetical change, which IMHO only raises requirements (from PHP 5.3 to 5.4)
Traits - I can't say, never used them before. I have some awareness, but no practical experience :-)

The reasons should not be practical, but political - 5.3 is insecure and dangerous. Drop it!

Ok, I had no idea that it is so serious...

Well, we are fighting for better world, don't we? :)

@hrach :smile
In my opinion 5.3 compatibility is not necessary. Also 5.4 has been released 3 years ago and should be installed on almost hosts.

I suggest migrate to min 5.4 or even 5.5. For the future.

Regarding people with old PHP: good library can be incentive to upgrade :). I would raise the minimum PHP to 5.4 for now. And then raised it to 5.5 exactly when 5.4's "Security fixes only" phase will end. Which is until 14 Sep 2015.

@vojtech-dobes :+1:

@vojtech-dobes :thumbsup:

@vojtech-dobes 5.3 will be in "Security fixes only" in 3 months. Don't be better raise it to 5.5 at once?

Implemented.


How to get sr4_resolution_256.npz?

Thanks for the authors' nice implementation.
I have run the codes for super-resolution and encountered the following error.
Could anyone tell me how to get the file "sr4_resolution_256.npz"?
Thank you very much!
_FileNotFoundError: [Errno 2] No such file or directory: '/nvme/feiben/DDPM_Beat_GAN/scripts/imagenet_dataloader/sr4_resolution_256.npz_

Hi, since we are busy with our project, we are sorry for the late reply.  You can find the .npz files in https://drive.google.com/drive/folders/1Lvp6vjovXOa3vYv98evVSxsmGX_C9sgy?usp=drive_link


DBZ-3037 Key being used as value in pubsub batch handler

DBZ 3037 Key being used as value in pubsub batch handler

@pkpfr Applied, thanks!


Attitude problem because of changing magnetic field?

I have a problem. I am using a pixhawk with the latest firmware with lidar lite v3 and px4flow. I have problem with attitude because I am flying  indoors and there are many changes of magnetic field.
I have tried to change the EKF2_MAG_TYPE to "magnetic heading" but I see that the attitude (pitch, roll and yaw) is continually changing if the magnetic field changes. If I change EKF2_MAG_TYPE to "None", the pitch, roll and yaw attittude is zero, and I dont have feedback of attitude.
I have tried with another pixhawk and the same thing happens.
What is the problem? How to solve it?
Greetings and thanks

@nitehack You should post a log, otherwise it's going to be hard to find out what your problem is.

@tumbili
Log with mag type "none" http://logs.uaventure.com/view/kmeAFw4qMYwfQqfgEiuSxE
Log with mag type "magnetic heading" http://logs.uaventure.com/view/Y5kFTpykjc5eAbUHaMK7ti
To download:
https://drive.google.com/open?id=0BxwqX0HkT8MwN0hjdkcyYmxrWFU
https://drive.google.com/open?id=0BxwqX0HkT8MwYXAyamlPTjd3Sms
In the log with mag type "none" I cant see anything , in QGC the attitude is 0.
In the test with mag type "magnetic heading" I didnt fly really because it can be dangerous so I moved the drone and then I put it in the table. Time later you can see that attitude (roll, pitch and yaw) change and compass  rotates. (the drone was remain still)

Does the pixhawk fuse the local position NED data with the gyro and accelerometer sensors to calculate the attitude?
I have observed that having the drone still and fooling the optical flow, pitch and roll change their value.
Is there any way to disable this fusion?

Try using attitude_estimator_q instead of EKF. Its update() method is quite straightforward.

@kd0aij Is it posible to use attitude_estimator_q for attitude estimator and EKF2 for position estimator? I have others problems when I use LPE estimator for local position.

What's the issue with LPE?

@mhkabir With LPE for any reason the local position X or Y NED is increasing or decreasing (meters) when drone is stop (I dont know the reason) , with EKF2 this doesnt happend. Futhermore I need that the height control only depends of Lidar lite (local position Z in LPE I see that depends of barometer and Lidar) and I cant select in LPE, with EKF2 I can select only Lidar lite.

@nitehack No, it's either EKF2 or LPE/Q; EKF2 does both position and attitude estimation

I assume you do not have a GPS or a secondary Compass which contradicts the other Compass (Orientation wise)? I had this behaviour when I had two Compass (internal and external) with incorrect Orientation settings.

@tops4u  I use only the internal compass but I also tried to connect a external compass with GPS, but in both cases is the problem. I observed that when I disconnet px4flow the problem disappears, and when the local position X or Y, also it change the attitude.

@nitehack Sorry for the delay, did not realize you posted the logs. I can have a look.

@nitehack From the log it seems that you are putting the drone upside down at some points. The result is that the range finder measurements will not be fused anymore and your height starts to drift off. As soon as you turn the drone around again the estimator re-initialises as supposed.
What are you trying to achieve when you have the drone upside down?

@tumbili I was testing extreme positions to reproduce the problem. Anyway I have seen that sometimes the problem appears even when the drone is stopped from the beginning (whithout the drone upside down). If I disconnect the optical flow, the problem disappears. Is EKF2 using optical flow data or local position to fuse them with attitude?

@nitehack Right, it looks like your magnetometer is disturbed quite a bit (heading innovations are huge). That won't help the optical flow since it needs to convert body frame measurements into earth frame.
Are you sure that your magnetometer is calibrated and that you have set the correct rotation? The only thing that remains to check for me is if the reset of position and velocity states works correctly. The EKF is fusing velocity data from the optical flow sensor, using also a distance to the ground estimate using the range finder.

@nitehack I see that this PR https://github.com/PX4/ecl/pull/234 has been merged just recently and brings in some optical flow improvements. Can you test with that?

@tumbili, I think master doesn't have the required submodule update yet.

@mhkabir Thanks, I'm doing that now then.

@tumbili I have calibrated the magnetometer many times and the orientation is correct. I will test these improvements. Thanks.

 Is it true that lidar lite v3 is supported in the 1.6.0 Release RC1?
And how can I test if the lidar is working?
Sorry for the intrusion hehe
Thanks!!

@nitehack Any update?

@dagar We are building a safe place for the drone before doing the flight test,  so I still can not confirm if the optical flow works well.

I am having this same problem on v1.6.3 and up. Have you found a fix, @nitehack? I have tried LPE and find EKF2 to be far more reliable when it's working so I would prefer to stick with it. This issue seems to randomly pop up after a varying number of flights.

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 30 days. Feel free to reopen this issue if you deem it appropriate.
(This is an automated comment from GitMate.io.)


Extended search does not provide all matched tokens in matches

Describe the bug
When the query has multiple tokens, only the matches from the last token is included in returned matches.
Version
5.1.0
Is this a regression?
Yes, although 3.6.2 has a different tokenize API. The results in 3.6.2 would include all matches.
🔬Minimal Reproduction
https://runkit.com/embed/p96hle7l44k6
const Fuse = require("fuse.js");
const objects = [{ title: 'Authors of "Fuse Proof of Concept"' }];

const fuse = new Fuse(objects, {
  includeMatches: true,
  useExtendedSearch: true,
  findAllMatches: true,
  threshold: 0.001,
  distance: 10000000,
  keys: ["title"],
});

const getHighlights = results => results.map((result) =>
  result.matches.map(({ value, indices }) =>
    indices.map(([start, end]) => value.substr(start, end - start + 1))
  )
);

const results = fuse.search("authors fuse proof");
console.log(getHighlights(results));
// → [[["or", "of", "F", "Proof", "of", "o", "p"]]]

(Expecting to see Authors and Fuse in the matches).

Seems like GH parsed my commit message wrong in our private repo. Reopening here.


Implement steps, events and forms in Runtime

[x] tests and linter show no problems (npm t)
[x] tests are added/updated for bug fixes and new features
[x] code is properly formatted (npm run fmt)
[x] description of changes is added in CHANGELOG.md
[x] update .d.ts typings

Landed in https://github.com/metarhia/lowscript/commit/114997a96454e3f560ee4dfcc2cc103082a31524 and https://github.com/metarhia/lowscript/commit/c514a198bf98e29d316ae2d628bf0d1c907bff88


Support to @Inject a SoftwareComponentFactory into a BuildService

Expected Behavior
It would be nice if a SoftwareComponentFactory could be given to a BuildService via Injection
Current Behavior (optional)
It doesn't seem to be possible to inject a SoftwareComponentFactory directly into a BuildService via the Inject annotation.
Notice that https://docs.gradle.org/current/userguide/dependency_management.html#sec:publishing-custom-components says:
To create a custom component, you first need to create an empty adhoc component. At the moment, this is only possible via a plugin because you need to get a handle on the [SoftwareComponentFactory](https://docs.gradle.org/current/javadoc/org/gradle/api/component/SoftwareComponentFactory.html) :

I also made a repro project at https://github.com/mathjeff/gradle-samples-2/tree/main/buildservice-componentfactory where I tried to inject a SoftwareComponentFactory directly into a BuildService like this:
abstract class SampleService
@Inject
constructor(val softwareComponentFactory: SoftwareComponentFactory) : BuildService<BuildServiceParameters.None> {
  init {
    System.out.println("Created SampleService with a reference to a SoftwareComponentFactory. Nice!")
  }
}

which gives this output:
A problem occurred evaluating root project 'buildservice-componentfactory'.
> Failed to create service 'SampleService'.
   > Could not create an instance of type example.SampleService.
      > Unable to determine constructor argument #1: missing parameter of type SoftwareComponentFactory, or no service of type SoftwareComponentFactory.

Context
In AndroidX we're trying to migrate towards compatibility with project isolation which entails more artifacts to publish from some projects and consume from other projects, so we're looking into making some helper methods for making this easier.
The first thing I tried was to directly inject the SoftwareComponentFactory into the BuildService, but that didn't work.
As a workaround it seems to work to inject the SoftwareComponentFactory into a Plugin which can then pass it to the BuildService
Thanks

It looks like we probably didn't end up needing this; see https://r.android.com/3065963 .
Part of the reason that I thought we would need this was some error messages were confusing, for example this one. I shared a pull request for that issue so I think this one can probably be closed as not important
Thanks


ghc: hadrian patch fix for fully_static

Description of changes
Fixes #208959 and #316850
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

This will need a backport to nixos-24.05 as well.

We could theoretically only apply this patch for the exact configuration which we want to use it for. i.e. enableShared = false;. Not sure. @sternenseemann, what do you think?

We can also only turn on this patch when enableShared is false, to make it less intrusive.

We could theoretically only apply this patch for the exact configuration which we want to use it for. i.e. enableShared = false;. Not sure. @sternenseemann, what do you think?

No, patches should be unconditional if possible to reduce complexity.

@sternenseemann Thanks for the quick review. I've fixed what you mentioned, I think.

Ah, one more thing: You need to remove the broken flag from meta in the expression since that is based on the problem we are fixing here.

@sternenseemann In order! What's the rest of the process? Is there any info about how to do a backport?

Is there any info about how to do a backport?

The backport will happen semi-automatically via github actions. The process is also described in CONTRIBUTING.md

Note that e.g. on nixos-24.05 there's still this code that makes pkgsStatic use GHC 9.4 instead of the default 9.6:
  haskellPackages = dontRecurseIntoAttrs
    # Prefer native-bignum to avoid linking issues with gmp
    # GHC 9.6 rts can't be built statically with hadrian, so we need to use 9.4
    # until 9.8 is ready
    (if stdenv.hostPlatform.isStatic then haskell.packages.native-bignum.ghc94
    # JS backend can't use gmp
    else if stdenv.hostPlatform.isGhcjs then haskell.packages.native-bignum.ghc96
    else haskell.packages.ghc96)

https://github.com/NixOS/nixpkgs/blob/3a0e59b841eff01ba5535b1cc807a60eff543c66/pkgs/top-level/all-packages.nix#L15900-L15907
This PR fixes at least part of that; we should see if that can be changed now.
There's still this problem:

https://github.com/NixOS/nixpkgs/issues/275304


custom decimal separator +  custom suffix

Added support for custom decimal separator
Added support for custom suffix

published 2.1.1


Mangled group names in RE_Match.groupdict()

Description
In IronPython 2.7.12 (and 3.4.0-beta1) RE_Match.groupdict() contains the mangled names of orginally unnamed groups,
when both named and unnamed groups are present in the expression. CPython only lists the explicitly named groups.
This is, of course, trivial to work around, but I still thought it worth the report.
Expected behavior:
Python 2.7.18 (v2.7.18:8d21aa21f2, Apr 20 2020, 13:25:05) [MSC v.1500 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import re; re.match('(?P<foo>.*)(.*)', 'bar').groupdict()
{'foo': 'bar'}

Actual behavior:
IronPython 2.7.12 DEBUG (<IP_ADDRESS>0)
[.NETFramework,Version=v4.5 on .NET Framework 4.8.4510.0 (64-bit)]
Type "help", "copyright", "credits" or "license" for more information.
>>> import re; re.match('(?P<foo>.*)(.*)', 'bar').groupdict()
{'foo': 'bar', '___PyRegexNameMangled2127356294': ''}

Thanks for the report!


h3spec

Hi,
i solved #110.
Some tests are failing. I will see if i can fix those.

Hi @seanmonstar ,
i fixed many of the http/3 failures, but some are left.

MUST send H3_MESSAGE_ERROR if a pseudo-header is duplicated [HTTP/3 4.1.1] FAILED [4]
I didn´t found that in the rfc, but maybe i just missed it.
MUST send H3_FRAME_UNEXPECTED if CANCEL_PUSH is received in a request stream [HTTP/3 7.2.5] FAILED [5]
In the accept method the poll_next returns an Error: received incomplete frame.
Also if the frame is received after the accept method is over how to close the connection without a reference to it? Maybe with a channel to the driver?
3. MUST send QPACK_ENCODER_STREAM_ERROR if a new dynamic table capacity value exceeds the limit [QPACK 4.1.3] FAILED [6]
MUST send QPACK_DECODER_STREAM_ERROR if Insert Count Increment is 0 [QPACK 4.4.3] FAILED [7]
These two i know not enough about qpack jet to debug why these are failing.

Also there are some Quic failures.
I skiped the 0-RTT one because the server-example crashes with this test.
What should be done with the Quic failures?
And there are many similar match expressions to handle the errors. I can think about a cleaner solution if you want. But i don´t have much time next week.
If you want to merge this this week, i can skip the failing tests, so the ci is green.

It could be the h3spec is using requirements from an old version of the spec... In that case, is there a way to ignore some?
Another option is to make your commits that fix various cases a separate PR, and we can merge that sooner, since they're straight improvements, while we figure out how to make the rest of h3spec happy.

We had to ignore a few test cases in s2n-quic, so it's doable: https://github.com/aws/s2n-quic/blob/dce3fd056f9a263d6fd97de932c9864d73a7e92f/.github/workflows/qns.yml#L556

The failing tests now getting ignored.
The QUIC servers/MUST send PROTOCOL_VIOLATION if CRYPTO in 0-RTT is received [TLS 8.3]
lets the example server panic so it crashes. That should probably be fixed, but I didn´t found the cause of the Problem.


nz-table nzScroll overfolow-y set percentage value not working

Hello guys,
when i try to use nz-table and set the nzScroll property like this  [nzScroll]="{ x:'130%',y: '130%' }", it's not working for me. Does there any workaround to fix this? What I need is overflow-y can also use percentage value and the table can responsive change height when the browser resizing. Just like writing in CSS set the max-height value and overflow-y to auto.
The below URL can reproduce my question

Thanks and Regards
Tony

may be helpful:
https://1-2-3.github.io/zorro-sharper/directives/auto-height-table-demo


💡[Feature]: want to add hover effect on social icons

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
when we hover over social icons it will convert to its actual colour ,
Use Case
it will look good to the users and you can visit any website all the website use this feature
Benefits
it willl look more appealing to users
Add ScreenShots
https://github.com/BamaCharanChhandogi/Diabetes-Prediction/assets/159682348/859bc0f8-d0a2-4f72-8d54-43c8f5abfe3b
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Thank you for creating this issue! 🎉 We'll look into it as soon as possible. In the meantime, please make sure to provide all the necessary details and context. If you have any questions or additional information, feel free to add them here. Your contributions are highly appreciated! 😊
You can also check our CONTRIBUTING.md for guidelines on contributing to this project.

@BamaCharanChhandogi please assign me this issue I want to work on it you and users will really like this feature .


jax_debug_nans silently letting nans through

I'm currently struggling to track down seemingly unexplainable nan problems (which might warrant its own issue once I figure out what is happening) but it seems like jax_debug_nan occasionally lets nan valued arrays through without raising an exception.
This whole thing seems either non-deterministic or triggered by very specific conditions so I am at a lose when it comes to distilling it down to a reproducible example. I will provide some context below but I know that with little info, it will be hard for the anyone to track this down so this first post is probably better seen as a call for help to try and isolate what might cause something like this.
Context
I am currently running some code that I last ran in late October (almost unmodified, but with updated dependencies) but now this code is spitting out nans very reliably when running jitted on CPU under the newer versions of jax/jaxlib. Both running jitted on GPU or non-jitted on CPU do not return nans. This might be a bug in and of itself, but I'll have to dig deeper before I can confidently eliminate the possibility of a bug in the dependencies or my code. The unexpected behavior that I'm observing here is something to do with how jax_debug_nans backtracks from running the compiled version of the function.
Unsurprisingly, jax will repeatedly spit out a warning that the compiled version spits out nans while not raising any exceptions since the non-compiled version executes normally. However, after some variable number of iterations varying between 100-600, an error is raised not as a result of a nan generated inside the function, but rather due to nans being given as inputs. What seems to be happening is that, at some point, the jitted update function manages to pass through some nan-valued arrays which are then given as input in the next iteration. I've manually confirmed that the update function does in fact return the nan values and aren't somehow introduced elsewhere.
Sample output just before exception is raised
Invalid value encountered in the output of a jit function. Calling the de-optimized version.

... continues for some number of iterations ...

Invalid value encountered in the output of a jit function. Calling the de-optimized version.
Invalid value encountered in the output of a jit function. Calling the de-optimized version.
Invalid value encountered in the output of a jit function. Calling the de-optimized version.
Invalid value encountered in the output of a jit function. Calling the de-optimized version.
Invalid value encountered in the output of a jit function. Calling the de-optimized version.
Invalid nan value encountered in the output of a C++-jit function. Calling the de-optimized version.
Invalid value encountered in the output of a jit function. Calling the de-optimized version.

... Exception with stack trace revealing nans in the input is the culprit ...

A few questions

What is the expected behavior of the output of a function that outputs nan while jitted and finite values otherwise when using jax_debug_nans?
What is the difference between the "regular" jit function warning and the C++ jit function warning?
The C++ one only seems to appear once towards the end (possibly always as the before last warning). Is this meaningful?

I'm going to try to report back with some more useful information but I thought I'd open an issue now since I've already spent a fair bit of time on this with little progress. Any insight, guesses or information about what might be happening would be very appreciated!

I don't really have time to follow up on this and some of my nan problems seem to have gone away in newer versions. Given I wasn't able to generate any reproducible example, I'm going to close this issue. I'll open a new one if I ever encounter this again.


How to setup and use this repo?

Would you mind providing an example of setup and usage of this repo?
I am confused when using this repo

Thanks for your question!
DeepSim is A Reinforcement Learning Environment Build Toolkit for ROS and Gazebo. DeepSim is a framework which provides customer easy to use toolkits to build simulation application on top of ROS and Gazebo.
You can read our paper https://arxiv.org/abs/2205.08034 to understand how you can use DeepSim framework to build your own simulation application.

Yeah, I have read the paper but I think I need a detail instruction or an example project code to understand what i should do with this repo.

I'm also looking forward to some brief documentation or instruction.


[Bug]: Invalid completion on after / in a service declaration

Description
Once we apply the http service template and fill in the context path as / the following suggestion comes:

When we press tab to go to the next placeholder, that on keyword gets applied.

This happens because we added / as a trigger character after the resource path segment support.
Steps to Reproduce
See description
Affected Version(s)
2201.2.2
Related area
-> Editor
Related issue(s) (optional)
#36997

Blocked by #38802


Date intervals in Loki queries too wide?

Our logs are taking quite a lot of time to load from Loki. I suppose it's caused by a very wide time range in which they are searched for in Loki:
start = ti.start_date - timedelta(days=15)
#if the task is running or queued, the task will not have end_date, in that
# case, we will use a resonable internal of 5 days

end_date = ti.end_date  or ti.start_date + timedelta(days=5)

end = end_date + timedelta(hours=1)

Why do we need to search for logs up to 15 days before task's start_date? Shouldn't it be just the start_date?
Also it would be nice to be able to parametrize the end_date for non-finished tasks (currently hard-coded to 5 days but that may be too much depending on the use case).

@zarembat  everytime the task is retried  the start_date will get updated to the current time.   so there is no way to know the time range for the older tries. so we query for the last 15 days.
if we retry the task after say 30 days. then it won't be possible to get the logs for the older task tries.
i agree that we can make the range offset configurable.
please feel free to open a PR with the changes or i will make the changes when i get a chance.

I found that you can change Loki setting split_queries_by_interval. The default value is 15m which means every query sends to loki splits into 15 * 24 * 4 (1440) sub queries. I changed to 24h in my environment and it helps a lot.


use with viewpager conflict

I use photoview with viewpager。
At first is work, but the image zooming and scrolling a few times will not be able to zoom.

Take a look at the sample project, it works in this case


remove tiktoken from glasslib

put it in glassc

https://github.com/foundation-ui/glass/commit/8d4386b48e0fe3142d5f3fddb7dc6a0fd1dd6999


Demonstrate need for imagenet preprocessing support for input tensors

With the goal of making input tensors as easy to use as numpy arrays, I'm trying to create an imagenet model loaded from pretrained weights that uses input tensors. This means for keras.applications.* images must be preprocessed in the same way as they are with numpy array inputs, so preprocess_input should support input tensors.

E   TypeError: 'Tensor' object does not support item assignment

build/bdist.linux-x86_64/egg/keras/applications/imagenet_utils.py:42: TypeError
====================== 1 failed, 3 passed in 1.58 seconds ======================

Am I correct that in the case of keras mean subtraction is performed without normalization for the models in applications?

This could likely be done with a type check in the existing function itself, a separate backend function. Thoughts?

In a related issue, it seems _obtain_input_shape fails on an input tensor as well:
$ python grasp_train.py
  [...snip...]
  File "build/bdist.linux-x86_64/egg/keras/applications/imagenet_utils.py", line 128, in _obtain_input_shape
  File "/home/ahundt/.local/lib/python2.7/site-packages/tensorflow/python/framework/ops.py", line 513, in __nonzero__
    raise TypeError("Using a `tf.Tensor` as a Python `bool` is not allowed. "
TypeError: Using a `tf.Tensor` as a Python `bool` is not allowed. Use `if t is not None:` instead of `if t:` to test if a tensor is defined, and use TensorFlow ops such as tf.cond to execute subgraphs conditioned on the value of a tensor.

It would be good to support tensors in these utils indeed. I believe the only operation that wouldn't work both on tensors and Numpy arrays would be the axis reversal op. We need a typecheck and a transpose op in that case.

Closing PR; feel free to reopen a PR that adds support for symbolic tensors in the util function (it would require a typecheck and different code for the symbolic case).


Provide Insert/Delete/Reload/Move Methods

The current implementation of sq_finishSendingOrReceivingMessage uses [self.collectionView reloadData] to update the collection view. Dies causes the collection view to reload on every new message, which looks weird if there are a lot of new messages. You can reprocude this by quickly pressing the "receive" button.
It would be better to provide an interface to the following methods in CollectionView:
- (void)insertItemsAtIndexPaths:(NSArray *)indexPaths;
- (void)deleteItemsAtIndexPaths:(NSArray *)indexPaths;
- (void)reloadItemsAtIndexPaths:(NSArray *)indexPaths;
- (void)moveItemAtIndexPath:(NSIndexPath *)indexPath toIndexPath:(NSIndexPath *)newIndexPath;

Hi. This feature is really needed in this great library. It will make it a lot smoother and much more performant. Is there any plan for this on the roadmap ?

Hello everyone!
I'm sorry to inform the community that I'm officially deprecating this project. 😢 Please read my blog post for details:
http://www.jessesquires.com/blog/officially-deprecating-jsqmessagesviewcontroller/
Thus, I'm closing all issues and pull requests and making the necessary updates to formally deprecate the library. I'm sorry if this is unexpected or disappointing. Please know that this was an extremely difficult decision to make. I'd like to thank everyone here for contributing and making this project so great. It was a fun 4 years. 😊
Thanks for understanding,
— jsq


Organize add more dark mode and stuff

#5 had broken some things - this is my 2nd attempt at it.
But of course I went down a bit of a rabbit hole, so this also organizes the styles a bit more, adds linting, adds some more styles, etc etc.
TODO:

[ ] @bradp needs to get better at doing separate PRs

I will have to personally test this one on my local environment before merging to main.

Before we merge this, @bradp  should also open a PR on MHCT to match the new file structure


DMN to XML conversion

Modified the original suggested changes in #14 and implemented the following:
– Redundant code was removed and use of generate_representation() was prioritised
– Endpoint /dmn was not correct and replaced by actual endpoint /rdf
– Class name changed to RepresentationGenerator for clarity
– Example was added to the notebook


.resolver.resolve_user should return the username/service with the User namedtuple

Something to add in, if it doesn't slow down the function substantially (over many runs).
Though there's not really much point? The code using it wouldn't need to be changed, and I'm not sure if the function would even be used outside of this package and the soulmate finder...

As tuple:
>>> import timeit
>>> timeit.timeit('aniffinity.resolver.resolve_user("XXX", "ANILIST")', setup="import aniffinity")
0.6346462229999972

As namedtuple:
>>> import timeit
>>> timeit.timeit('aniffinity.resolver.resolve_user("XXX", "ANILIST")', setup="import aniffinity")
1.5054766589999993

On average, 8.7E-7 slower (0.87 secs slower overall)
So shouldn't make that much of a difference.


Pattern matching - Stage 0

This issue is to keep track of the implementation in the parser of this proposal.
Champions: Brian Terlson (Microsoft, @bterlson), Sebastian Markbåge (Facebook, @sebmarkbage)
Spec Repo: https://github.com/tc39/proposal-pattern-matching

Remember that proposals are just that; subject to change until Stage 4!

Examples
let length = vector => match (vector) {
    { x, y, z }: Math.sqrt(x ** 2 + y ** 2 + z ** 2),
    { x, y }:   Math.sqrt(x ** 2 + y ** 2),
    [...]:      vector.length,
    else: {
        throw new Error("Unknown vector type");
    }
}

let isVerbose = config => match (config) {
    { output: { verbose: true } }: true,
    else: false
}

let outOfBoundsPoint = p => match (p) {
    { x > 100, y }: true,
    { x, y > 100 }: true,
    else: false
}

You can find more example in the spec repo.
Parsing

[ ] Babylon plugin: patternMatching
[ ] Babel AST changes

Should move this to https://github.com/babel/proposals?


Bug: When a custom text node is deleted, a new text node is inserted

When I delete a custom TextNode, a new Replace TextNode will be inserted. But without replacing text node, no new node will be inserted.
Please Watch the video below

Lexical version: 0.9.1 and latest
The current behavior
This unexpected behavior will trigger my editor.registerMutationListener(cusTextNode, onChange),  monitoring and bring unexpected results
The expected behavior
Uninserted node
Do not insert cusTextNode When a custom node is deleted

This case does not use with me

Inspired by the above code, my question is here

Inspired by the above code, my question is here

This solution solves the problem of inserting textNode, but customNode will be replaced by textNode. The reason for looking at the code is that the key of node is used.
Hope someone can give a solution to this problem😂

Your custom node class should define constructor and clone methods returning the new custom node.

Your custom node class should define constructor and clone methods returning the new custom node.

@ivailop7 https://codesandbox.io/p/sandbox/divine-feather-g8qq5w?file=%2Fsrc%2Fnodes%2FWordNode.tsx%3A25%2C23
I did this, but it still doesn't work,  This problem is related to whether WordNode is a token. This will happen when isToken is true.


Removed .location check

For now commented out the %  check as it relied on the .location field returned from ns.sleeve.getTasks(), and that is no longer in the return with v2

This should fix #209

Is there any other way to get this sleeve chance info? Without it, sleeves will early on be assigned to tasks they fail and build up a ton of shock, making them useless for the rest of the augmentation.

 I also can't seem to find any available sleeve property that shows a percentage success when doing BB stuff. I think the blade burner sleeve interactions have changed, but I'm still looking through the diff files around sleeves

Nevermind, they are just quietly failing. Retract the request as I further troubleshoot.

After further testing all available get methods in sleeve v2, and running BB assignments while monitoring fail/success messages in BB versus sync levels, it appears sleeves no longer lose sync on bb fails, though I have been unable to get a sleeve to fail any task other than recruitment. Until proven otherwise, I have removed the failure check completely.  You can hold this PR until we get additional support.


Improve docs for nerves use case pojiro

I failed to create PR, this PR is not for main. So I closed this.


Doesn't work properly with nwjs 0.22.0+

Chromium 58 has changed internal files tree and introduced use of symbolic links. Current implementation of nwjs-autoupdater uses https://github.com/mholt/archiver, which seems like doesn't play well with symlinks. I'm not sure how to fix this yet. Any help with this will be appreciated.

Something worth checking https://github.com/mholt/archiver/issues/21


add ElasticSearch

Got a request to add ElasticSearch...
its a bit odd, because it requires Java RE...so we have to test for that ,)

[x] crawler

crawl: https://www.elastic.co/downloads/elasticsearch
downloads

https://download.elastic.co/elasticsearch/elasticsearch/elasticsearch-1.5.1.zip
https://download.elastic.co/elasticsearch/elasticsearch/elasticsearch-1.7.1.zip 30mb

[x] registry
[x] download description file
[ ] installer registries
[ ] installation wizards

"JAVA_HOME environment variable must be set"

set JAVA_HOME C:\Program Files (x86)\Java\jre7\bin

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Added to registry.
Download is available.
No further integration.
Closing.


nixos/tests/plotinus: fix non-deterministic failures

Motivation for this change
The test failed sometimes on Hydra, likely because a window didn't get focus before typing into it.
Use xdotool to make sure the right window has focus.

@GrahamcOfBorg test plotinus

Success on x86_64-linux (full log)
Attempted: tests.plotinus
Partial log (click to expand)
machine: exit status 1
syncing
machine: running command: sync
machine: exit status 0
test script finished in 61.84s
cleaning up
killing machine (pid 593)
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: Could not remove ctl dir '/build/vde1.ctl': Directory not empty
/nix/store/myzfj2cxa3plz076gh83zjihib8fh12m-vm-test-run-plotinus

Success on aarch64-linux (full log)
Attempted: tests.plotinus
Partial log (click to expand)
machine: exit status 1
syncing
machine: running command: sync
machine: exit status 0
test script finished in 50.35s
cleaning up
killing machine (pid 627)
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: Could not remove ctl dir '/build/vde1.ctl': Directory not empty
/nix/store/8p745bbp2p4vmmjfn6cavwc8h3jww073-vm-test-run-plotinus


Add support for CPU pinning.

For certain workloads, CPU pinning will result in much better performance.
We need to take a look at the platform awareness features in K8s.

I would like to +1 this in lieu of the L1TF vulnerability.


Bug 1217758 - Add a dropmarker to filters button

I forgot to hover effect on caret. Because I worked only with colored squares symbols for filters, it wasn't visible for me.


We should export the engine with debug symbols

Right now all engine builds are release builds without debug symbols. If a crash occurs, the call stack might look like this:

If we were to attach debug symbols (mac and linux) or offer additional symbol files (windows) we could have a nice callstack. Downside would be the extra download size.

adding this now for our official release.


Xnero: Watch promosimple.com

Xnero requests the watch of the watch_keyword promosimple\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

promosimple\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


add performance focused APIs

In building out Jiff, my focus has generally not been on performance. There are some Criterion benchmarks, but they are by no means exhaustive. I would love to have more added.
While I think there's always room to optimize the implementation (and if you have ideas that require major refactoring, please file an issue), this issue is more about API changes or additions that are needed to improve performance. For example, I'm thinking about things like "datetime arithmetic requires the use of Span, and Span is a very bulky type." At time of writing, its size is 64 bytes. I presume that this means that there is some non-trivial amount of time being spent in various operations on Span memcpying around this enormous bag of bytes.
Getting rid of Span or splitting it up isn't really an option as far as I'm concerned. So in order to make things go faster, I think we really just need to be able to provide APIs that operate on more primitive data types. Like, for example, an i64 of nanoseconds. This would come with various trade-offs, so I'd expect these APIs to be a bit more verbosely named.
Here's a probably non-exhaustive list of API design choices that likely have an impact on performance:

A Timestamp is always a 96-bit integer.
A Span is a whopping 64 bytes. A Span is Copy and most APIs accept a Span instead of a &Span.
Dealing with spans generally takes a lot of work. So when you add, say, a Span to a Timestamp, it's not just a simple matter of ~one integer addition. There's work needed to be done to collapse all of the clock units on Span down to a single integer number of nanoseconds, and then i128 math is used. Perhaps there is a way to optimize a Span for the "single unit" case, although doing this without indirection will make a Span even bigger, and doing it with indirection will remove the Copy bound. Another alternative might be leaving Span as-is, but adding non-Span APIs to operate on durations. But that has some design work needed as well. See #21.
A Zoned embeds a TimeZone which means a Zoned is not Copy and cloning/dropping a Zoned is, while cheap, not as cheap as a small Copy type. (This also means most things take a &Zoned instead of a Zoned.)
A default TimeZoneDatabase uses a thread safe shared cache internally. This means time zone lookups by name require some kind of synchronization. (Usually this overhead can be worked around by asking for all the time zones you need up-front, but this is difficult if you're deserializing zoned datetime strings.)
The use of ranged integers internally makes some kinds of layout optimizations more difficult than they would be otherwise. For example, it might be tempting to bit pack the representation of some types, but if you do that, you'd have to either define a new ranged integer abstraction for bitpacking (plausible... but maybe complicated) or abdicate range checking altogether. You might think you can just convert to and from ranged integers as you need them, but the whole point of Jiff's ranged integer abstraction is that they track min/max values when debug_assertions are enabled. So if you drop the ranged integer type to do bit-packing and then re-create the ranged integer after unpacking, you will have lost the min/max values that were originally attached. Anyway, see #11 for more on this.

Anyway, before we get too focused on API design, I would like to see concrete use cases first in the form of executable code and/or benchmarks.

I think Zoned being !Copy isn't too much of an issue given what the type is designed to do. I would expect the Timestamp type to be far more commonly used in practice.
Timezones only really come into play in the front-end (which Rust is not typically used for...) or for some specific kinds of applications such as calendars, where events need to be scheduled at a "civil time" in the future.
Overall this crate seems very well designed, but if I have one criticism it's that I think it over-emphasizes the use of Zoned. Clearly there are cases when you need to store a runtime timezone, but IME they are few and far between (at least in the domains where Rust is most popular). Having this functionality, and having it interoperate perfectly with timestamps is very useful, but starting out with "The primary type in this crate is Zoned." is going to mislead some users I think.
If you intend this crate to displace chrono and time as "the" general purpose time crate, I would like to suggest:

Splitting the Timestamp type (and other non-timezone-aware functionality) into a jiff-core or similarly named crate. This way other crates (eg. database bindings) can provide integrations with jiff without needing to pull in all the timezone logic.

Adding a pure time interval version of Span for use with Timestamp.

Adding some guidance to the documentation about how to choose a particular timezone type depending on the use-case, so that users are directed to only store a dynamic timezone when actually necessary.

I think (3) is #24.
I think (2) is probably #21.
I am unsure about (1). I'm not sure if I agree that Timestamp is the right "default" to emphasize. Perhaps time zone aware datetimes aren't being used as much as they should be. I'm not sure. With that said, I am open to a jiff-core-style crate. But I think the API design and split will be challenging. In particular, I think it will be hard to do without sacrifices to API comprehensibility, which I am loathe to do. But like I said, I am open to it. I think we just need to collect more data.

Perhaps time zone aware datetimes aren't being used as much as they should be.

Heh, my experience is the opposite - in both JS and Python I've experienced significant extra complexity and bugs from their datetime types coming with a "packaged" timezone being used in places where timezones were not relevant.
In Python the main issue has been use of datetime where a simple timestamp would be more appropriate, since 99% of cases I'm dealing with a point in time, and the timezone is only relevant in so far as displaying that instant to the user in their preferred timezone. Storage should (in this case) be done in UTC and that's what the database expects.
In JS, only a couple of days ago I encountered a bug at work where a Date was being used to display a date (no time) but because the user's local timezone was offset it ended up showing the wrong date in the UI, despite being stored correctly in the backend. (Why did it use a JS Date? Because that's what the 3rd party date picker component was built around...) Variants of this bug are everywhere in JS.
In contrast, I haven't had any issues with chrono or time in Rust since they don't really have the capacity to mess up the timezone. They just don't support the rare case where you do care about it.
It's honestly quite hard to think of use-cases where I'd want to store a datetime + timezone. Storing a future event in a calendar is the go-to example, but even then the only motiviation for that is to deal with the edge-case where timezone data changes between the event being scheduled and it actually occurring, and doing that comes at a cost: it becomes impossible to schedule events at "ambiguous" times (at least with the default serialization implementation of Zoned).
If I want to build a best-possible calendar app, what's more likely? That the timezone data changes in a meaningful way, or that someone wants to schedule an event during a DST change... Both seem similarly likely.
Maybe there's a case for changing the serialization to disambiguate these cases... It doesn't help if the timezone data changes and the event lies on a DST change, but that's a legitimate ambiguity in that case.

Another option is making time zone support a crate feature.

Yeah that also works, I only didn't suggest it because I assumed you'd want to make the timezone functionality be default-enabled, and I really hate default features in Rust, since nobody remembers to turn them off.

It is had to disentangle your examples of bugs with the underlying datetime library. Both of the datetime libraries you mention have very serious deficiencies.

it becomes impossible to schedule events at "ambiguous" times (at least with the default serialization implementation of Zoned).

I don't see why this would be true. You can't schedule an event at 2am on March 10, 2024 in New York because that clock time didn't exist. That seems right to me?

Yeah that also works, I only didn't suggest it because I assumed you'd want to make the timezone functionality be default-enabled, and I really hate default features in Rust, since nobody remembers to turn them off.

Yes, it would be enabled by default.
I think we overall need to collect more data. That will take some time and require users. I don't know that you are wrong, but I think you are.

My very high level idea is that datetime libraries have sucked for so long, and this may have been inhibiting use cases or causing other problems that are falsely attributed. This is just an opinion though. So basically, I am excited to see what, if anything, Jiff unlocks for folks. IMO, its killer feature is not just Zoned but also Span. I think Span is going to take more time for folks to discover because I don't think anything like it has existing yet (until Temporal).

I don't see why this would be true. You can't schedule an event at 2am on March 10, 2024 in New York because that clock time didn't exist. That seems right to me?

That's a non-existent time, not an ambiguous time. If I schedule an event at a time that occurs twice due to clocks being put backwards, then jiff's Zoned type appears to be able to correctly disambiguate the actual time, but if I serialize/deserialize it, then that information will be lost. I would expect the default serialization format to faithfully round-trip the value.

IMO, its killer feature is not just Zoned but also Span. I think Span is going to take more time for folks to discover because I don't think anything like it has existed yet (until Temporal).

It's nice, but it's definitely not new. The interval type in PostgreSQL has always worked this way.

That's a non-existent time, not an ambiguous time.

Ah yeah, both Temporal and Jiff refer to it as ambiguous. The thing that is ambiguous is the offset.

but if I serialize/deserialize it, then that information will be lost

No, it is not! This is a key feature of Jiff:
use jiff::{civil::date, tz::TimeZone};

fn main() -> anyhow::Result<()> {
    // The ambiguous civil datetime:
    let dt = date(2024, 11, 3).at(1, 30, 0, 0);
    // By default, the "compatible" disambiguation strategy is used. Which
    // selects the later time for a gap and the earlier time for a fold:
    let zdt = date(2024, 11, 3).at(1, 30, 0, 0).intz("America/New_York")?;
    assert_eq!(zdt.to_string(), "2024-11-03T01:30:00-04:00[America/New_York]");
    // One can override and pick whichever strategy they want:
    let tz = TimeZone::get("America/New_York")?;
    let zdt = tz.to_ambiguous_zoned(dt).later()?;
    // Notice the offset change from above:
    assert_eq!(zdt.to_string(), "2024-11-03T01:30:00-05:00[America/New_York]");

    Ok(())
}

See jiff::tz::AmbiguousZoned for more details.
The fact that Jiff losslessly roundtrips Zoned values is a key comparison point between it and Chrono.

It's nice, but it's definitely not new. The interval type in PostgreSQL has always worked this way.

It doesn't though? I'm not intimately familiar with PostgreSQL's interval type, but from a quick glance I can immediately see several differences:

It doesn't keep of each unit separately. So it can't distinguish between 120 minutes and 2 hours.
It doesn't seem to support rounding/balancing.
It doesn't seem to support using a reference date for adding spans, or at least lets you add spans together even when they have non-uniform units.

So for example, on that last point, this is what PostgreSQL does:
postgres=# SELECT INTERVAL '1 months 27 days' + INTERVAL '3 days';
   ?column?
---------------
 1 mon 30 days
(1 row)

postgres=# SELECT INTERVAL '1 months 27 days' + INTERVAL '4 days';
   ?column?
---------------
 1 mon 31 days
(1 row)

postgres=# SELECT INTERVAL '1 months 27 days' + INTERVAL '5 days';
   ?column?
---------------
 1 mon 32 days
(1 row)

Compare this with Jiff:
use jiff::{civil::date, ToSpan};

fn main() -> anyhow::Result<()> {
    let span = 1.month().days(27);
    // The span has non-uniform units (months), so a
    // reference date is required to do addition. Otherwise,
    // you get an error:
    assert!(span.checked_add(3.days()).is_err());
    // So pick a date:
    assert_eq!(
        span.checked_add((3.days(), date(2024, 6, 1)))?,
        1.month().days(30)
    );
    // So pick a different date and notice that the span
    // returned reflects the actual duration of the
    // corresponding months:
    assert_eq!(
        span.checked_add((3.days(), date(2024, 1, 1)))?,
        2.months().days(1)
    );

    Ok(())
}

This all comes from Temporal and RFC 5545.

PostgreSQL can't balance days up into months.

reference_date + interval - reference_date will do that.
But I think we can agree that:

The representation used by PostgreSQL does not prevent such functionality being provided.
Jiff provides more functionality out of the box on top of that representation.

Yes. And we haven't even gotten to the time zone aware aspects of Span when used with a Zoned in Jiff. From the PostgreSQL docs:

The default time zone is specified as a constant numeric offset from UTC. It is therefore impossible to adapt to daylight-saving time when doing date/time arithmetic across DST boundaries.


remove vendor dir and create go module

Use the newer way of go dependency management instead of vendoring dependencies

I understand. Had to create this patch to fix the build for NixOS, and then decided that I could just as well make a pr as well.


cosmwasm-check multiple args

Closes #1392
Test cases:
[tom@trilby cosmwasm]$ export GLOBIGNORE=artifacts/floaty.wasm
[tom@trilby cosmwasm]$ cargo run --bin cw-check-contract artifacts/*.wasm
    Finished dev [unoptimized + debuginfo] target(s) in 0.05s
     Running `target/debug/cw-check-contract artifacts/burner.wasm artifacts/hackatom.wasm`
Available capabilities: {"staking", "stargate", "iterator"}

artifacts/burner.wasm: pass
artifacts/hackatom.wasm: pass

All 2 contracts passed checks!
[tom@trilby cosmwasm]$ echo $?
0

[tom@trilby cosmwasm]$ unset GLOBIGNORE
[tom@trilby cosmwasm]$ cargo run --bin cw-check-contract artifacts/*.wasm
    Finished dev [unoptimized + debuginfo] target(s) in 0.05s
     Running `target/debug/cw-check-contract artifacts/burner.wasm artifacts/floaty.wasm artifacts/hackatom.wasm`
Available capabilities: {"staking", "stargate", "iterator"}

artifacts/burner.wasm: pass
artifacts/floaty.wasm: failure
Error compiling Wasm: Could not compile: WebAssembly translation error: Error in middleware Gatekeeper: Float operator detected: F64Const { value: Ieee64(0) }. The use of floats is not supported.
artifacts/hackatom.wasm: pass

Passes: 2, failures: 1
[tom@trilby cosmwasm]$ echo $?
1

Added color, because green is good and red is bad.

Aaaand here's proof CI isn't broken:
https://github.com/CosmWasm/cosmwasm/pull/1396
https://app.circleci.com/pipelines/github/CosmWasm/cosmwasm/4240/workflows/3e7bc99a-a06c-457f-a660-d67a788e742d/jobs/55077


Players don't see notification of feature received?

I believe players can't see feature announcements when getting features?
https://www.ecocitycraft.com/forum/threads/possible-buycraft-feature-bug.147789/

BuycraftX no longer sends notifications when a package is credited to a user. This is better done with your own plugin.

Thanks :)


Document edgedb watch and new dev workflow

Keeping this as a draft PR until 3.0 launches since it is in non-versioned documentation, but the content is ready for review.

Feedback has been addressed with the exception of versionadded. I'll keep this PR as draft either until 3.0 is released or until we make a decision re: versioning for the CLI docs that would make merging earlier practical.


How to change language?

First of all, great work!
But you want to know how to change the language. Or add your own text. Thanks

Do the same thing as assets picker would do, and check the doc.
References:

https://github.com/fluttercandies/flutter_wechat_camera_picker#usage-
https://github.com/fluttercandies/flutter_wechat_camera_picker/blob/master/lib/src/delegates/camera_picker_text_delegate.dart

Thanks a lot! Sorry I didn't read that right


Improve xsimd::abs coverage

Let's open a discussion here: the test commented out in this PR don't pass, and I fail to understand why. Any hint?

can you remove the commenting out and let's see what CI says?

@wolfv here is CI output :-) Have fun

no longer relevant, @JohanMabille did a great job there.


Get-Help Set-RsDataSource

Hi,
I used Get-Help Set-RsDataSource, but there is not syntax to show.
PS C:\Windows\system32> Get-Help Set-RsDataSource
Name                              Category  Module                    Synopsis

Set-RsDataSource                  Function  ReportingServicesTools    ...
Set-RsDataSourcePassword          Function  ReportingServicesTools    ...
Set-RsDataSourceReference         Function  ReportingServicesTools    ...
Best regards.

Get-Help Set-RsDataSource -detailed, for the full documentation, also I would like to recommend to read some blogs about it like https://sqlvariant.com/2016/11/powershell-for-ssrs-is-here/


Merge prTesting_201909291320 branch to master branch

Docs Build status updates of commit a125593:
:warning: Validation status: warnings

File
Status
Preview URL
Details

split/updateTestRef.md
:warning:Warning

Details

split/updateTestRef.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.
[Warning] Missing attribute: title. Add a title string to show in search engine results.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[SPEC] Improving multi-asset handling

Overview
Simplify and improve how the dApp handles assets and balances.
Motivation
The dApp deals with multiple types of assets/balances

ERC20 tokens
Substrate tokens
Substrate ORML tokens
Native tokens
Wrapped assets

What do we have now?
Those forms of assets are mapped to a type CurrencyContent
for displaying.
Spec
Moving backward, what is needed by the UI?

Listing assets.

Asset name
Symbol
Image if any
Asset identifier
and the asset type

Get the balances of an asset with an account/address.
Determine whether an action is supported on a token (Ex bridge: can this asset moved between chains)
Determine what chain the asset lives in
Determine if an asset can be wrapped /unwrapped
...

Resources

https://github.com/makerdao/multicall
https://github.com/cavanmflynn/ethers-multicall

@nepoche can you update to include context for dynamic currency implementation.


CASMHMS-5603/CASMHMS-5562 Updates for HMS Helm CT tests

Summary and Scope
This PR includes changes for three scripts used for HMS CT testing during the CSM health checks:

run_hms_ct_tests.sh

This test wrapper script has been refactored for running the new Helm versions of the HMS CT tests which are no longer packaged as RPMs on the NCNs.

hsm_discovery_status_test.sh

This test script previously lived in the hms-smd repository and ran as a CT smoke test but it's being moved here since it was a one-off test of a different type than the others and is better suited to run here along with the other discovery validation tests.

verify_hsm_discovery.py

The test script is updated to use HSM v2 APIs instead of v1 which are deprecated and being removed.
The HMS CT test RPMs that are no longer needed have also been removed.
Issues and Related PRs

Resolves CASMHMS-5603.
Resolves CASMHMS-5562.

Testing
This change was tested by deploying the updated versions of the HMS services and charts onto Mug, executing the CT tests, and verifying that they passed.
Was a fresh Install tested? N
Was an Upgrade tested? Y
Was a Downgrade tested? N
Risks and Mitigations
Low risk, test update.

Looks like this was a little out-of-date, rebased it to see if it passes the branch build.

[2022-07-13T01:01:51.033Z] No provider of 'hpe-csm-scripts=0.0.35-1' found.

Yes, I expect this build to fail since the hpe-csm-scripts v0.0.35 RPM can't be built and tagged until my other PR for CASMHMS-5603 merges:

https://github.com/Cray-HPE/hpe-csm-scripts/pull/19

In that ticket they asked for the manifest PRs before the regular PR was merged.