How should we represent implicit downcast of a parameter default value in kernel?

The following code contains an implicit downcast of a parameter default value:
const List<Object> x = ...;
f({List<int> y: x}) {} // implicit downcast from `List<Object>` to `List<int>`.

Depending on the value of the constant x, this might or might not lead to an error.  Note that due to the exisence of fromEnvironment const constructors, the front end doesn't do constant evaluation, so it can't tell whether an error should occur--detecting the error is postponed to runtime (as it is with other implicit downcasts).  Currently the front end handles this by generating the following kernel representation:
static const field core::List<core::Object> x = ...;
static method f({core::List<core::int> y = self::x as{TypeError} core::List<core::int>}) → void {}

This seems undesirable, because:

compile-time constants are not normally allowed to contain as expressions
it seems a little strange that errors involving "constants" would not be detected until runtime
it's not clear when the runtime error is expected to occur (should it occur at the time of the call to f?  At the time of execution of any method which refers to f?  When the program starts?).  This makes it hard to write effective tests for this scenario.

Conceptually, it seems reasonable to expect that the use of x as a default value would be accepted or rejected (depending on the actual value) at compile time. But that notion is a bit blurred: There's "(real) compile time" and "analysis time", and fromEnvironment is not known at analysis time.
Given that constant expressions are intended to denote compile-time constant values, and "compile time" is usually not considered different from "analysis time", couldn't we approximate the strict approach where the actual value is used by evaluating constant expressions in the front end as far as possible? (That is, reverting to the current treatment when something like fromEnvironment is encountered, and otherwise using the actual values).
I suppose this could be valuable in several ways:

Developers could inspect compile-time constant values when they are also analysis-time constant, and hence rely on their actual value when reasoning about the program.
Checks like the one mentioned in this issue could be performed eagerly in the typical case, and hence errors would arise "properly", during development.
The run-time check could in any case be changed to a real compile-time check, because compilation would take place in a situation where fromEnvironment values are actually available.

So I guess the main issue would be "How much work would it take to get there?". ;-)

I think this representation is fine, and even desirable:

Kernel constant expressions can contain whatever we decide they can (Kernel is not Dart).  This should be OK.
We should just stop using the term compile-time error and switch to static error.  This is a static error.
It's not a runtime error.  It occurs whenever the back end signals static errors, which the user probably expects to be either before any code is run (AOT), or before this function is entered (JIT).


Check files only if they are of type text

https://gist.github.com/rayrutjes/db9b9ea8e02255d62ce2
https://github.com/h2non/filetype
https://golangcode.com/get-the-content-type-of-file/
Maybe something of this helps

Done in: https://github.com/editorconfig-checker/editorconfig-checker.go/commit/093f57304d63eb901829ad4aaaa3676b9baeeafc


 Any ideas what's going on?
I'm running on ubuntu 18.04.1.
-T

Looks odd.
You should never see username and password in log files.
It seems that somehow your installation uses GET instead of POST calls.

How strange. It appears to intentionally use GET. Could the browser cause something like that? Any idea what could be causing this? I tried installing again on centos 7.5 and Ubuntu 18.04.1 and ran into the same issues. To work around it I altered all columns with default "null" values to empty strings or 0. In MySQL 10.3 a default null column will not allow an insert if a value is omitted in the statement. This solved the immediate issue. I think the code my need some updating for newer releases of MariaDB and php.
And not to worry, the passwords were intentionally dummy passwords in the logs.
Great work on this by the way!!


Change macosx to macos

For the sake of consistency with the new command in master, change macosx to macos as the name of the target platform

Thanks!


Update data.json to comply with DCAT-US Metadata Schema

the federal data.gov catalog is able harvest catalogs from local jurisdictions. They used to harvest data from OpenDataPhilly but have suspended this harvesting because our data.json file is not compliant with the current metadata schema.
Our data.json file says it's 1.1, but when we run the validator at https://catalog.data.gov/dcat-us/validator (using the data.json at https://opendataphilly.org/data.json), there are a lot of errors, including:

missing required properties: bureauCode, ProgramCode, keyword, modified, publisher, identifier, accessLevel, on Dataset, for example
missing point of contact
all of our download points seems to not match the schema
they don't like the custom City of Philadelphia license (we probably can't fix this)

Upstream JKAN issue, although I haven't checked recently if it complies with it's single data set.   I believe some items needed to just be changed to output in a different field.
Some items like bureauCode IMU can be ignored as that's specific to the US government.  They used to have a different validator for non-federal orgs but I can't find that option.

I reached out to the Data.gov folks. Many of the "mandatory" fields are only mandatory for federal agencies. They ran it for non-federal data sets and identified only one mandatory field that we don't have:

We ran the harvest of the source and all the datasets failed for lack of an identifier. We don't have many mandatory fields, but identifier is one of them. Schema explanation is at resources.data.gov

We would need to have a unique id expressed in the "identifier" field.

It's a bit more complicated than I had hoped - but I understand why:
"This field allows third parties to maintain a consistent record for datasets even if title or URLs are updated. Agencies may integrate an existing system for maintaining unique identifiers. Each identifier must be unique across the agency’s catalog and remain fixed. It is highly recommended that a URI (preferably an HTTP URL) be used to provide a globally unique identifier. Identifier URLs should be designed and maintained to persist indefinitely regardless of whether the URL of the resource itself changes."
https://resources.data.gov/resources/dcat-us/#identifier
I see two options:

Just use the filename - figuring that will change much less than the Title or URL
Generate based on org/title/first URL - and save generated version to each dataset file

@BryanQuigley I received an annual check-in email from Data.gov asking for our harvest information, which caused me to come back to this.
After a year of editing the catalog over the past year, I definitely have seen several examples of the filename changing as well as being deleted. However, I also think it is the simplest approach as it could be generated in the data.json file without having to persist a unique ID and all of the issues that will go along with that.
So I propose we implement this using the file name as the unique ID.


HyCore

Expected behavior
Actual behavior
Information about the Issue
Steps to reproduce the behavior

...
...

No information provided or steps to replicate - Closing


Color scheme problems

I'm having issues with the color scheme under macOS / iterm / zsh. In short, this is the issue:

In comparison to what shown in README, colors look boring / flat / harder to read.
I'm not doing anything interesting with iterm's color schemes and I never had any issue with lost / altered colors before. Is there anything we should be careful about to get better colors, closer to what shown in the docs?

Hey @ulgens, I agree that really doesn't look great 😞
It looks like the background colors are not being rendered, but I don't really understand why. I went through my own iterm settings, but can't seem to reproduce what you are seeing.
Can you let me know the versions of textual and trogon that you are using? You should be able to see them with:
❯ pip freeze | grep -E 'textual|trogon'

It's working fine for me on:
textual==0.74.0
trogon==0.5.0

but I'll also try on the exact versions that you are on to make sure it's not a problem with upstream dependencies.
Also, have you tried running any other textual apps? There is a list of them here. If you have the same issue with any of these then it might be a problem with textual itself and we'll have to make a ticket there before I can fix it in django-tui.

I think I looked for the issue in the wrong place. Apparently, things work just fine locally.

The issue occurs when I run it in a Docker container. At the moment, with the same textual and trogon versions, it works just fine without Docker, but I encounter that color issue with Docker.
The code/project I'm doing this test is https://github.com/ulgens/django-blasphemy/pull/559 , I hope the problem is easily replicable. I'll check how other apps act when I have the time.
Thanks for the help and the quick response.

Awesome that you managed to solve this, I didn't know docker limits the colors, thanks for letting me know!


Make Side bar : position: sticky;

Make sidebar position: sticky; for easy accessibility and improved appearance.
Video of current functionality :
https://github.com/CircuitVerse/simple_discussion/assets/77102885/6c26b3ed-4651-433a-9811-1e60c5befc26
Video of Solution :
https://github.com/CircuitVerse/simple_discussion/assets/77102885/fd4fddd3-2105-42d4-9c96-5ff08d8f152b

Closing this as complegted by PR #6


#1 Adding support for calling actions on instance

Pull Request Test Coverage Report for Build 30

155 of 249 (62.25%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-4.1%) to 74.263%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/lambdas/internals/Expression.mon
41
43
95.35%

src/lambdas/internals/KnownActions.mon
47
78
60.26%

src/lambdas/internals/LambdaUtils.mon
67
128
52.34%

Totals

Change from base Build 26:
-4.1%

Covered Lines:
918

Relevant Lines:
1178

💛  - Coveralls


Use ScaledLSTM as streaming encoder

This PR implements ScaledLSTM as a light streaming encoder with the scaling mechanism in reworked model. We do not need to use time masking during training as in streaming Conformer, since the LSTM computation is essentially streaming.
The ScaledLSTM class is written in pruned_transducer_stateless2/scaling.py, which is modified from https://github.com/pytorch/pytorch/blob/master/torch/nn/modules/rnn.py, using the highly optimized operator _VF.lstm in pytorch.
@danpovey  Could you help me check for correctness of the value of fan_in in _reset_parameters function if you are free?
In lstm_transducer_stateless/lstm.py, each encoder layer consists of a lstm module and a feed_forward module, which adopts similar residual connection as in Conformer.

Currently, it only supports using jit.trace to export the SclaedLSTM model.
Pytorch does not support jit.script for nn.LSTM class, see https://github.com/pytorch/pytorch/blob/master/torch/nn/modules/rnn.py#L909 for detail.
Thers is an issue while exporting the model using onnx. torch.onnx does not support the case of using projections in LSTM class. See https://github.com/pytorch/pytorch/blob/master/torch/onnx/symbolic_opset9.py#L3666

Support only torch.jit.trace is fine with me.

What is the recommended recipe if one wants to do online ASR? Not clear to me whether this is recommended over the streaming conformer stuff or not? @danpovey

Trained a model on 1k hours and got twice the WER compared to a conformer model (greedy search) unfortunately.

Trained a model on 1k hours and got twice the WER compared to a conformer model (greedy search) unfortunately.

Do you mean the streaming conformer?

https://github.com/k2-fsa/icefall/pull/558 shows that when you use a larger dataset, e.g., 30k hours of data, ScaledLSTM
has competitive results with the streaming conformer in icefall.

Interesting. I just realized I wasn't using musan augmentation which I presume is suboptimal.
I'm comparing to the normal conformer, the impression I got from the librispeech results file was that the lstm model will keep up with pruned_transducer_stateless2.
It does make sense to me that a 12 layer LSTM model needs a lot of data to work well.


chore: add shane sveller to team members

First day, and he's already got code running in production. Welcome to The Team @shanesveller


bugfix:  2.0 Agent 配置文件更新流程错误 (closed #1202)

Codecov Report

Merging #1203 (4c7a56e) into V2.2.31-rc (a00c0e1) will increase coverage by 0.01%.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           V2.2.31-rc    #1203      +/-   ##
==============================================
+ Coverage       73.24%   73.25%   +0.01%
==============================================
  Files             357      357
  Lines           24005    24005
==============================================
+ Hits            17582    17585       +3
+ Misses           6423     6420       -3

Impacted Files
Coverage Δ

apps/backend/subscription/steps/plugin.py
55.86% <0.00%> (+0.65%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Fix ConfigMap rendering

Fix ConfigMap rendering in Kubernetes
Grafana Agent ConfigMaps are not rendering properly in Kubernetes due to extra indentations on blank lines. This fix removes the extra indentations.
Before
# kubectl get configmap release-name-grafana-agent -o yaml

apiVersion: v1
kind: ConfigMap
data:
  config.river: "discovery.kubernetes \"nodes\" {\n  role = \"node\"\n}\n    \ndiscovery.kubernetes
    \"pods\" {\n  role = \"pod\"\n}\n    \ndiscovery.kubernetes \"services\" {\n  role
    = \"service\"\n}\n    \n// Grafana Agent\ndiscovery.relabel \"agent\" {\n  targets
    = discovery.kubernetes.services.targets\n  rule {\n    source_labels =
    ...

After
# kubectl get configmap release-name-grafana-agent -o yaml

apiVersion: v1
kind: ConfigMap
data:
  config.river: |-
    discovery.kubernetes "nodes" {
      role = "node"
    }

    discovery.kubernetes "pods" {
      role = "pod"
    }

    discovery.kubernetes "services" {
      role = "service"
    }

    // Grafana Agent
    discovery.relabel "agent" {
      targets = discovery.kubernetes.services.targets
      rule {
        source_labels = ["__meta_kubernetes_service_label_app_kubernetes_io_instance"[]
        regex = "release-name"
        action = "keep"
      }
      rule {
        source_labels = ["__meta_kubernetes_service_label_app_kubernetes_io_name"[]
        regex = "grafana-agent"
        action = "keep"
      }
      rule {
        source_labels = ["__meta_kubernetes_service_port_name"[]
        regex = "http-metrics"
        action = "keep"
      }
    }
    ...

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

That's why the Test / static-test-chart tests are failing.


Fix the deploy pipeline by updating versions

Update versions of the github actions, deploy dependencies, and python version in an attempt to fix the sceptre installation in the deploy pipeline.
The deploy pipeline is failing while installing sceptre with:
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv

Notice:  A new release of pip is available: 23.0.1 -> 24.3.1
Notice:  To update, run: pip install --upgrade pip
Traceback (most recent call last):
  File "/usr/local/bin/sceptre", line 5, in <module>
    from sceptre.cli import cli
  File "/usr/local/lib/python3.8/site-packages/sceptre/cli/__init__.py", line 17, in <module>
    from sceptre.cli.new import new_group
  File "/usr/local/lib/python3.8/site-packages/sceptre/cli/new.py", line 7, in <module>
    from sceptre.config.reader import STACK_GROUP_CONFIG_ATTRIBUTES
  File "/usr/local/lib/python3.8/site-packages/sceptre/config/reader.py", line 20, in <module>
    from jinja2 import Environment
  File "/usr/local/lib/python3.8/site-packages/jinja2/__init__.py", line 12, in <module>
    from .environment import Environment
  File "/usr/local/lib/python3.8/site-packages/jinja2/environment.py", line 25, in <module>
    from .defaults import BLOCK_END_STRING
  File "/usr/local/lib/python3.8/site-packages/jinja2/defaults.py", line 3, in <module>
    from .filters import FILTERS as DEFAULT_FILTERS  # noqa: F401
  File "/usr/local/lib/python3.8/site-packages/jinja2/filters.py", line 13, in <module>
    from markupsafe import soft_unicode
ImportError: cannot import name 'soft_unicode' from 'markupsafe' (/usr/local/lib/python3.8/site-packages/markupsafe/__init__.py)

Attempting to run pipenv lock -d locally resulted in a cryptic dependency resolution error:
Locking packages...False
<console width=350 ColorSystem.TRUECOLOR>
Traceback (most recent call last):
  File "/opt/homebrew/bin/pipenv", line 8, in <module>
    sys.exit(cli())
             ^^^^^
  File "/opt/homebrew/Cellar/pipenv/2024.0.2/libexec/lib/python3.12/site-packages/pipenv/vendor/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Cellar/pipenv/2024.0.2/libexec/lib/python3.12/site-packages/pipenv/cli/options.py", line 52, in main
    return super().main(*args, **kwargs, windows_expand_args=False)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Cellar/pipenv/2024.0.2/libexec/lib/python3.12/site-packages/pipenv/vendor/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Cellar/pipenv/2024.0.2/libexec/lib/python3.12/site-packages/pipenv/vendor/click/core.py", line 1688, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Cellar/pipenv/2024.0.2/libexec/lib/python3.12/site-packages/pipenv/vendor/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Cellar/pipenv/2024.0.2/libexec/lib/python3.12/site-packages/pipenv/vendor/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Cellar/pipenv/2024.0.2/libexec/lib/python3.12/site-packages/pipenv/vendor/click/decorators.py", line 92, in new_func
    return ctx.invoke(f, obj, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Cellar/pipenv/2024.0.2/libexec/lib/python3.12/site-packages/pipenv/vendor/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Cellar/pipenv/2024.0.2/libexec/lib/python3.12/site-packages/pipenv/vendor/click/decorators.py", line 33, in new_func
    return f(get_current_context(), *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Cellar/pipenv/2024.0.2/libexec/lib/python3.12/site-packages/pipenv/cli/command.py", line 552, in update
    do_update(
  File "/opt/homebrew/Cellar/pipenv/2024.0.2/libexec/lib/python3.12/site-packages/pipenv/routines/update.py", line 61, in do_update
    do_lock(
  File "/opt/homebrew/Cellar/pipenv/2024.0.2/libexec/lib/python3.12/site-packages/pipenv/routines/lock.py", line 67, in do_lock
    venv_resolve_deps(
  File "/opt/homebrew/Cellar/pipenv/2024.0.2/libexec/lib/python3.12/site-packages/pipenv/utils/resolver.py", line 859, in venv_resolve_deps
    c = resolve(cmd, st, project=project)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/homebrew/Cellar/pipenv/2024.0.2/libexec/lib/python3.12/site-packages/pipenv/utils/resolver.py", line 723, in resolve
    raise RuntimeError("Failed to lock Pipfile.lock!")
RuntimeError: Failed to lock Pipfile.lock!

i don't get why we are still fixing up this repo?  i asked to check if this repo is still being used in a previous PR but never got a definitive answer?

@zaro0508 this repo is in a nebulous half-state, it hasn't had any development beyond the one vpc created in htan-dev, but that vpc is the primary vpc used by htan-dev according to vpc flow logs. So we shouldn't archive the repo even though it isn't active.


8a62be8 is a hack to fix an attribute error on d.retired - instead make sure we load retired when we load decks

load_decks loads retired in every case. I wonder where we load decks without it. Possibly nowhere. Might be ok to just changed this to d.retired.

"Fixing" this gains us nothing in practical terms and risks reintroducing the bug it fixes so I'm closing this. Doing a get on an attribute that should always exist is not the greatest crime.


fix(Portal): use portalNode to check focus

Fixes #3005.

Codecov Report

Merging #3015 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master    #3015   +/-   ##
=======================================
  Coverage   99.96%   99.96%
=======================================
  Files         163      163
  Lines        2743     2743
=======================================
  Hits         2742     2742
  Misses          1        1

Impacted Files
Coverage Δ

src/addons/Portal/Portal.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Released in<EMAIL_ADDRESS>


Installation instructions are missing one step

Hi there,
I've just installed your theme as described in the README, i.e. I cloned the theme into the themes subfolder, and then changed the theme in the main _config.yml.
However, when I then start hexo server, I get this error.

...and the webpage does not show up.
It seems Hexo cannot find the theme if the project is merely cloned as-is.
One also needs to change the target folder when cloning, so
git clone https://github.com/MrWillCom/hexo-theme-cupertino.git
should be:
git clone https://github.com/MrWillCom/hexo-theme-cupertino.git cupertino

Thanks. You are right. It's necessary to move themes/hexo-theme-cupertino/ to themes/cupertino/ .

It's fixed now. :smiley: 53264e6

That's super-fast turnaround!


Tmsagarofficial patch 1

Description
Grammar and typo fixes
References
This is just a simple PR to address the issues as mentioned in the descrption
Review Checklist

[x] I have clicked on "allow edits by maintainers".
[NA] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[x] The correct base branch is being used, if not main
[NA] I have added tests to validate that the change in functionality is working as expected

Thanks @aaguiarz

Can hacktoberfest label be added to this? @aaguiarz

@tmsagarofficial just added it

@aaguiarz Ohh okay Thanks , I see that this repo doesn't have hacktoberfest label 😅, In this case adding hacktoberfest-accepted would help me make this contribution count towards some streak.

@tmsagarofficial I just added the hacktoberfest / hacktoberfest-accepted  labels to the repo and to the PR.
Does this work?

Yeah thanks mate
On Mon, Oct 7, 2024, 19:04 Andrés Aguiar @.***> wrote:

@tmsagarofficial https://github.com/tmsagarofficial I just added the
hacktoberfest / hacktoberfest-accepted labels to the repo and to the PR.
Does this work?
—
Reply to this email directly, view it on GitHub
https://github.com/openfga/sample-stores/pull/42#issuecomment-2396951610,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2MYN4OON4XRVDY6F7BVZCTZ2KEUZAVCNFSM6AAAAABPIAG2COVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJWHE2TCNRRGA
.
You are receiving this because you were mentioned.Message ID:
@.***>


[Do_NOT_MERGE] run all test under new security plugin

Description
[Describe what this change achieves]
Issues Resolved
[List any issues this PR will resolve]
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

One issue is: https://github.com/opensearch-project/security-dashboards-plugin/pull/1705

Other issue is that security dashboards plugin seems not to be installed, checking manifests

@prudhvigodithi @rishabh6788 @peterzhuamazon seems like the latest 3.0.0 build doesn't have security dashboards plugin, but I see it present in the manifest file: https://github.com/opensearch-project/opensearch-build/blob/main/manifests/3.0.0/opensearch-dashboards-3.0.0.yml, is it just because we haven't had a successful build for a while? Any way to get this plugin in the build image somehow?
2023-12-22T10:04:52.6475682Z {"type":"log","@timestamp":"2023-12-22T10:04:52Z","tags":["fatal","root"],"pid":2115,"message":"InvalidConfigurationError: Unknown configuration key(s): \"opensearch_security.multitenancy.enabled\", \"opensearch_security.multitenancy.tenants.preferred\", \"opensearch_security.readonly_mode.roles\", \"opensearch_security.cookie.secure\". Check for spelling errors and ensure that expected plugins are installed.\n    at ensureValidConfiguration (/home/runner/work/opensearch-dashboards-functional-test/opensearch-dashboards-functional-test/opensearch-dashboards-3.0.0/src/core/server/legacy/config/ensure_valid_configuration.js:50:11)\n    at Server.setup (/home/runner/work/opensearch-dashboards-functional-test/opensearch-dashboards-functional-test/opensearch-dashboards-3.0.0/src/core/server/server.js:156:5)\n    at Root.setup (/home/runner/work/opensearch-dashboards-functional-test/opensearch-dashboards-functional-test/opensearch-dashboards-3.0.0/src/core/server/root/index.js:60:14)\n    at bootstrap (/home/runner/work/opensearch-dashboards-functional-test/opensearch-dashboards-functional-test/opensearch-dashboards-3.0.0/src/core/server/bootstrap.js:113:5)\n    at Command.<anonymous> (/home/runner/work/opensearch-dashboards-functional-test/opensearch-dashboards-functional-test/opensearch-dashboards-3.0.0/src/cli/serve/serve.js:191:5) {\n  code: 'InvalidConfig',\n  processExitCode: 64,\n  cause: undefined\n}"}

Run wget https://ci.opensearch.org/ci/dbc/distribution-build-opensearch-dashboards/3.0.0/latest/linux/x64/tar/dist/opensearch-dashboards/opensearch-dashboards-3.0.0-linux-x64.tar.gz

Hey @derek-ho even though its part of the manifest the security dashboards plugin failed to build for 3.0.0 version, please check the created AUTOCUT issue.
https://github.com/opensearch-project/security-dashboards-plugin/issues/1682


prompter exit on ESC or Ctrl+C

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 26.872%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1224

Relevant Lines:
4555

💛  - Coveralls


Add a "Reviewed by Hound" badge

Coverage remained the same at 100.0% when pulling 378d1352e8cf9d776c8e7e93ba34f433e0ea22c2 on salbertson:patch-1 into 6a7d6e94cb7f35a279079678d83938e85dd6c509 on RobinCK:master.


[Proposal] Remove / prefix in container names

All containers get this weird / prefix which we have to account for all over the code.
This was used, IIRC, for the graphdb but is not needed today (and arguable that it was ever really "needed").
When I removed graphdb I chose to keep it so as to minimize the change and potential pieces that could break at the time.
It would be really great to remove this.

Yeah, it has cropped up in lots of questions and has had handling code added. Its time for it to go. If we wanted a name hierarchy, we could still have a/b without an initial /.

Yup, would be glad to see it go as well; here's an earlier PR doing this; https://github.com/docker/docker/pull/11080
And related PR's / issues; https://github.com/docker/docker/pull/16577, https://github.com/docker/docker/pull/18524

👍 #29007 is also related to the / naming issue.

Is this still on plan?
Wondering it might break compatibility

Yes, I think that's the reason attempts to remove this failed so far

I haven't tried to remove it. I honestly don't think it should be a break... but I haven't looked at it in awhile.


Use nested set pattern for Group nesting

https://github.com/etrepat/baum might be worth considering for this. Edit: or not, because it hasn't been updated for 2 years... but yeah. Nested set pattern!

I've been using this https://github.com/lazychaser/laravel-nestedset for a while

Solved in #120


Partial fix for Linux

Issue 6 is fixed complety* with the addition of local compilation with submodules, with the liberty of enhance the project structure and README.md
*: Note that problems can still occur given that no all used libraries are being packed with the binary and submodules may need configuration to be sure they use themselves as dependencies.

Sorry for the late response. I haven't had the chance to test this yet, I'll read through it and merge.

I can't get it to run, are there instructions on how to make it run? it seems to be nested with submodules. I don't understand it.

@Bohmthedudevulture I tried cloning on Windows. It failed after downloading 7.5gb of Qt, because the filenames ended up too long. Can you precompile the binaries instead of submoduling everything? You could even edit the existing binaries to use the correct RPATH, if that's the problem. Qt's source code won't be changed, so it's more economical like this

@Bohmthedudevulture I tried cloning on Windows. It failed after downloading 7.5gb of Qt, because the filenames ended up too long. Can you precompile the binaries instead of submoduling everything? You could even edit the existing binaries to use the correct RPATH, if that's the problem. Qt's source code won't be changed, so it's more economical like this

Same here on linux, it tried cloning GB of QT which isn't needed.

@Bohmthedudevulture  and @craftablescience Some instructions first, (1) You don't need to clone all of the Qt repository, just his base submodule, and compile it with the icu binaries. (2) You must also, and firstly compile the submodule icu. (3) The Qt base qmake will generate a cmake imports where a line is wrong, is a trivial fix with a StackOverflow at respect. (4) finally compile the p2-publishing-tool root.

@Bohmthedudevulture I do have to clone the entire Qt repo, because you made the entire thing a submodule.

@Bohmthedudevulture I do have to clone the entire Qt repo, because you made the entire thing a submodule.
You don't have to. Neither after that.

@Bohmthedudevulture i know how submodules work, thanks. What my point is is what's the point of adding the entire Qt repo as a submodule when you don't use nearly any of it? It's wasteful and pointless

@craftablescience (1) New users, no just download the releases?. (2) Well, it can be added to the instructions, or instead submodule Qt's base submodule instead.

Is it not possible to precompile Qt instead?

Is it not possible to precompile Qt instead?
In windows, may be really easy to get the standalone binary. But in linux you basically have to compile it yourself anyway. And given that we have to ship all the no GNU user space dependencies and link they with the local copies, is just easier to sub-module the dependencies and give a build script, this is ignoring that independently that independently builds may differ more than the RPATH.

Fair enough then. It would still be great if you could change it to only have the necessary submodules though

The TLDR here is that unless the submodule issue has been fixed, we'll likely won't merge this.

also, if it's of your interest, @Bohmthedudevulture, the github action already downloads the full QT libraries and compiles them, all that really needs to be fixed is the linking.


Creating a Prototype API with Mock Payload Generated Inline Scripts

Purpose

Mock response payload generation for inline scripts for prototyping APIs.

Goals

Mock response payloads defined by the user in the swagger definition will be injected to a generated javascript code, which will then be shown under each respective method in inline scripts. This allows users to easily prototype an API without manually writing implementations for each method.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Enabled CR validation through admission webhooks

Implemented both validating and mutating admission webhooks
Generate required certs for the webhook and patch required k8s objects during controller init.
Removed object validation from the Reconcile function
Updated the README.md
Closes #20

main.go issues will be tracked in issue #23


Added solutions to Cracking the Coding Interview questions

Hi,
I have added a link to my solutions for the problems in Cracking the Coding Interview. This makes it possible to view and understand the approach to problem solving. Also, bring in more people to contribute to code. :D
Thank You!

Hi,
Thank you! This will give your repo more visibility and also help everyone in interview preparation.
Thank you for helping us in collective and curating all the CS resources at one place - AlgoWiki 👍


Github Actions - Releases

Automate building and releasing binaries to Github. I assume there will be an Action available to do this.

Fixed in e4c3dcd


Django 1.11

Passage en Django 1.11

Coverage increased (+0.4%) to 84.517% when pulling 0ddf836482b1c6a509871b521ef357353f568d34 on LePetitTim:django_111 into a84b7b3b2b16945c3bbc788664568b02be0f4501 on makinacorpus:master.


Workspace - Workspace name is not reset when creating new workspace on the next new account

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.84-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail: n/a
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
Action Performed:

Go to staging.new.expensify.com
Log in with a new account (must be on a private domain, like<EMAIL_ADDRESS>)
Create a few workspaces.
Note that the workspace name follows the order of 1,2,3 etc.
Log out.
Log in with another new account.
Create a few workspaces.

Expected Result:
The workspace name will reset and start from the order (1,2,3 etc) when creating new workspace on the next new account.
Actual Result:
The workspace name does not reset and continues from the order (4,5,6 etc) when creating new workspace on the next new account.
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/38435837/67d5c59c-361c-42a3-819e-7535204ba48d

View all open jobs on GitHub

@VictoriaExpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to  #vip-vsb

Proposal
Please re-state the problem that we are trying to solve in this issue.
Workspace - Workspace name is not reset when creating new workspace on the next new account
What is the root cause of that problem?
When user sign out, the allPolicies const in here:
https://github.com/Expensify/App/blob/75c104bfe009ef937bcd129a35bb5a2e52f4339d/src/libs/actions/Policy/Policy.ts#L90-L95
is not cleared. There is no call back for each key and value of polies to be undefined. So the allPolicies value is preserved across user.
What changes do you think we should make in order to solve the problem?
In callback here:
https://github.com/Expensify/App/blob/75c104bfe009ef937bcd129a35bb5a2e52f4339d/src/libs/actions/Policy/Policy.ts#L138-L141
we add code to reset the value of allPolicies, the code could be:
in the first line of callback
if (sessionAccountID !== 0 && sessionAccountID !== val?.accountID) {
      Object.keys(allPolicies).forEach(key => delete allPolicies[key]);
}

so when

Hmm I'm not sure that this is a bug, it seems more like the system is recognising that these are essentially linked to the same account. This would not be a real-world problem for our customers; it is very specific to our test account set-up.
For example, when I sign in with my test account<EMAIL_ADDRESS>I can still see new.dot messages from my production account (victoria@expensify.com). I believe that's because these are essentially the same email addresses.
If you believe this could, in fact, have an impact on a real-world customer scenario, could you please provide more information and specific examples of how?


MicroRos Agent Stucked

I succesfully uploaded the firmware into teensy 4.0, but then when I run micro-ros-agent, it won't start any node as attached picture below:
I have tried to push the reset button then it become like this:
I also tried to unplug and plugged again teensy board then it become like this:
I'm using ros2 humble, but I already tried on ros2 galactic also. Already tried both on laptop and Raspberry Pi 4B.

Please check your USB connection.

lsusb
ls /dev/tty*

If you are new to micro-ROS, you may use pico and esp32 instead of teensy.  Please check my wiki at https://github.com/hippo5329/linorobot2_hardware/wiki .

If you are new to micro-ROS, you may use pico and esp32 instead of teensy.  Please check my wiki at https://github.com/hippo5329/linorobot2_hardware/wiki .

can I use teensy and for your github repo?

Yes, it should work. I suggested esp32 and pico because they are cheaper than teensy and have hardware encoder counters instead of the interrupt-driven on teensy. I have tested upload and connect to micro-ROS agent with teensy40 and teensy41. Though I do not use teensy to build robots and have not test teensy on real robots. There are issues in platformio teensy upstream, so the first upload to teensy might fail. But the second upload should success. It is not related to linorobot. You may use lino_base_config.h as a template and create your custom configuration. I have suggested test the micro-ROS agent connection with the micro-controller module alone before wiring and building the robot. BTW, Can you see the /dev/ttyACM0 device after upload?

Test micro-ROS agent connection - Recommended
It is recommended to test the micro-ROS agent connection with the micro-controller module alone before wiring and building the robots.  If you use teensy and lino_base_config, comment out the "#define USE_GY85_IMU" in lino_base_config.h.
Then test the micro-ROS agent connection.

Esp32 and pico are suggested because they are cheaper than teensy and have hardware encoder counters instead of the interrupt-driven on teensy. The hardware encoder counters can count up to MHz. It will be almost impossible for the more expensive teensy to reach this speed.

Test micro-ROS agent connection - Recommended
It is recommended to test the micro-ROS agent connection with the micro-controller module alone before wiring and building the robots.  If you use teensy and lino_base_config, comment out the "#define USE_GY85_IMU" in lino_base_config.h.
Then build, upload and test the micro-ROS agent connection.

I see, alright thanks

Test micro-ROS agent connection - Recommended
It is recommended to test the micro-ROS agent connection with the micro-controller module alone before wiring and building the robots.  If you use teensy and lino_base_config, comment out the "#define USE_GY85_IMU" in lino_base_config.h.
Then build, upload and test the micro-ROS agent connection.

May I know why need to comment out the IMU define?

We would like the teensy module connects to micro-ROS agent without the IMU. If the IMU is enabled but failed to initialize, the teensy will stop and blink the LED 3 times per second. So we comment out the IMU. Only the teensy module alone is needed to perform this connection test.

I am also having these problems.
Motor / encoder checks work - teensy40 firmware upload works
Is running the micro_ros_agent supposed to have more output?
ros2 run micro_ros_agent micro_ros_agent serial --dev /dev/ttyACM0
Commenting out the IMU shows error about commenting out IMU
I am using IMU GY-521

Please switch to my fork.
cd linorobot2_hardware
git remote add hippo https://github.com/hippo5329/linorobot2_hardware.git
git fetch hippo
git reset --hard
git checkout -b hippo hippo/master
Comment out the GY85 in line_base_config.h, build, upload and test connection.

Gy-521 is MPU6050.

Oh nice I switched over to your fork and it seems to be working now
There is more output after running micro_ros_agent
Teensy has solid light - keys pressed for teleop_twist move wheels
Will investigate further
Thank you @hippo5329 for the work


Debug progress bar fills up too quickly

Refs: https://github.com/microsoft/vscode/issues/92914
Seems like the bar is filled around 40-45% or so
dap.progressUpdate({
  progressId: 'p1',
  message: String(percentage),
  percentage,
});

Great catch. My 4th grade math was a bit off :)


NFT sharing dApp

Project title
NFT sharing dApp
Project Description
A Social Media dApp, similar to Instagram, is a decentralized version of the Instagram platform for pets where users can browse photos of their favorite pets, see details of a specific pet, create a post and earn NFTs.
Doc Domain

[x] Solidity , ReactJs /NextJs , Web3.js /Ether.js, IPFS

Are you contributing under any open-source program?
SSOC '22

Great idea @AyushPathak3011  can u please tell the folder structure in which u wana to add this .

Great idea @AyushPathak3011 can u please tell the folder structure in which u wana to add this .

Web3.0-World/Level2/NFT-Sharing-dApp

Great idea @AyushPathak3011 can u please tell the folder structure in which u wana to add this .

Web3.0-World/Level2/NFT-Sharing-dApp

Fine .. start working on this

HI @AyushPathak3011 since this seems to be a long project , would you mind working on this together?
// @Vikash-8090-Yadav is that possible?

If u  are talking  under the SSOC'22 then not possible cux this is open source programme individual contribution matters.

@AyushPathak3011 any updates ?

@AyushPathak3011 any updates ?

Sorry for being inactive, had some personal commitments.
Yes I am working on the final stages of this project, will update soon.

@AyushPathak3011  . Any updates ???

@AyushPathak3011 areu still working on this ?


Restore previous unsafe chain when invalid span batch

WIP

Cleanup at https://github.com/testinprod-io/optimism/pull/45


Question Regarding Direct Line Sites & Limits

Is there a limit to the number of Sites you can configure against a single Direct Line connection? If so, what is the restriction?
Apologies if this is documented somewhere but I've been unable to find any answer. Any help will be much appreciated.

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

ID: 71081bf9-a44f-7f24-040a-fcc6bc6dca02
Version Independent ID: d5f6d9e6-9522-5915-0bbe-28b9b7f4725f
Content: Connect a bot to Direct Line - Bot Service
Content Source: articles/bot-service-channel-connect-directline.md
Service: bot-service
GitHub Login: @mmiele
Microsoft Alias: v-mimiel

We don't impose any limits on the number of sites that can be created.  How many are you expecting to create?

Closing, per request.

@craigjensen Many thanks for your response. To answer your question; we're not sure, we were thinking of potentially having a site per tenant but the number of tenants would depend on how many companies would use our product. Having looked further into how we can configure & identify the sites, it suggests that perhaps this is not the best route to take. Thanks again for your help.


Trivy analyzer integration

Description
Migrating the Trivy support added in Dependency-Track v4.11 to Hyades.
Co-authored-by: Marlon Pina Tojal<EMAIL_ADDRESS>Addressed Issue
Port change https://github.com/DependencyTrack/hyades/issues/1343
Checklist

[x] I have read and understand the contributing guidelines
[ ] This PR fixes a defect, and I have provided tests to verify that the fix is effective
[x] This PR implements an enhancement, and I have provided tests to verify that it works as intended
[ ] This PR introduces changes to the database model, and I have updated the migration changelog accordingly
[ ] This PR introduces new or alters existing behavior, and I have updated the documentation accordingly

looks ok to me


[Design] Create Template engine from project snapshot

I have not updated all of the tests yet, but just check out how this works now.

Updated and fixed tests


MTRL K6 robot

MTRL robot

Hi, you opened two PRs with the same aparent changes. This one is the older one, should I close this without merging?

Hi
The first one didn't work well I have updated with the second one and would
appreciate if you can merge the 2nd one
Thanks a lot
and thank you for your tool
On Tue, May 9, 2023 at 1:41 PM visose @.***> wrote:

Hi, you opened two PRs with the same aparent changes. This one is the
older one, should I close this without merging?
—
Reply to this email directly, view it on GitHub
https://github.com/visose/Robots/pull/227#issuecomment-1539930506, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABAM6GKNMHGJOQGAUPSVC53XFINPFANCNFSM6AAAAAAX3ANGZ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
OHAD MEYUHAS, ARCHITECT
Mobile +972.54.666.2046


Upgrading to FSharp.Core 4.5.1 causes build error

Upgrading my solution to FSharp.Core 4.5.1 causes an unexpected build error.
Repro steps
Provide the steps required to reproduce the problem

Upgrade to FSharp.Core 4.5.1.

Build solution.

Unfortunately I'm not able to provide the source code.
Expected behavior
The solution builds successfully.
Actual behavior
The following error occurs:
FSC : error FS0193: The module/namespace 'Control' from compilation unit 'FSharp.Core' did not contain the val '{MemberParentMangledName = Some "AsyncActivation`1"; MemberIsOverride = false; LogicalName = "OnSuccess"; TotalArgCount = 2;}' [/home/nat/Projects/shopmasse-backend/fsharp/src/Masse.SearchProduct/Masse.SearchProduct.fsproj]

Known workarounds
Downgrade to FSharp.Core 4.5.0.
Related information
Provide any related information
dotnet --info output:
.NET Core SDK (reflecting any global.json):
 Version:   2.1.302
 Commit:<PHONE_NUMBER>

Runtime Environment:
 OS Name:     ubuntu
 OS Version:  18.04
 OS Platform: Linux
 RID:         ubuntu.18.04-x64
 Base Path:   /usr/share/dotnet/sdk/2.1.302/

Host (useful for support):
  Version: 2.1.2
  Commit:  811c3ce6c0

.NET Core SDKs installed:
  2.1.105 [/usr/share/dotnet/sdk]
  2.1.302 [/usr/share/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.2 [/usr/share/dotnet/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.2 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.0.7 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.2 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

That's rather strange, since the API diff from 4.5.0 and 4.5.1 has nothing to do with Async:

There was a source code change to move stuff out of the massive control.fs file into various other files that are appropriate for what they do, but the compiled .dll is still the same. Are there any other details you could share about your code that could give a hint?

@cartermp Unfortunately, after switching back to FSharp.Core 4.5.0, building successfully, and then switching back to FSharp.Core 4.5.1, I'm not able to reproduce this.  If I figure out any kind of consistent pattern I'll report back.

Closing in favor of #5369, as discussion about a root cause is going on there.
TL;DR - later versions of FSharp.Core are not guaranteed to work (at all) with earlier versions of the F# compiler. This is likely such an occasion. The recommendation is to depend on FSharp.Core 4.2.3 (even if 4.5.0 works for you), because this is what has been tested against F# 4.1. Any combination of an F# 4.1 compiler and a later FSharp.Core package working properly is coincidental.


Add ipv4 and ipv6 forwarding recipe

Add recipe to ensure IP forwarding is enabled in /etc/sysctl.conf

Dupe of #211


Adding Chef Infra Server to Chef Automate

:nut_and_bolt: Description: New Page named chef_infra_server has been created in Chef Automate.
:chains: Newly added Chef Infra Section in Infrastructure.
:+1: The Documentation is created and ready for review.
:athletic_shoe: How to Build and Test the Change.
Check out the steps provided on the page.
:white_check_mark: Checklist

[x] I have read the CONTRIBUTING document.
[x] Tests added/updated?
[x] Docs added/updated?
[x] All commits have been signed-off for the Developer Certification of Origin.

NOTE: The section of the Infrastructure has not been created yet. Will be added once the review is done.

I made some edits that I think improve things a bit, although I'm not 100% sure that they're correct. But hopefully they improve things a bit.


Temporal proxy not building

The Temporal proxy isn't building:
1>***************************************************************************
1>EXCEPTION:   build command-line-arguments: cannot load github.com/stretchr/objx: open C:\src\neonKUBE\Go\src\temporal-proxy\vendor\github.com\stretchr\objx: The system cannot find the file specified.
1>MESSAGE:     build command-line-arguments: cannot load github.com/stretchr/objx: open C:\src\neonKUBE\Go\src\temporal-proxy\vendor\github.com\stretchr\objx: The system cannot find the file specified.
1>SCRIPT NAME: C:\src\neonKUBE\Go\build-temporal-proxy.ps1
1>SCRIPT LINE: 59
1>SCRIPT STACK TRACE
1>------------------
1>at <ScriptBlock>, C:\src\neonKUBE\Go\build-temporal-proxy.ps1: line 59
1>***************************************************************************

Never mind, somehow several GO source files got deleted on my workstation.


CDR3 clustering among multiple samples (bulk RNA-seq)

Thank you for your great tool. I have three questions as for clustering.

As indicated in the title, is it possible to cluster CDR3nt among multiple samples? Although CDR3nt in a sample can be clustered by "trust-cluster.py", inputting multiple trust_report.tsv files is not allowed. I suppose putting together the trust_report.tsv files into a whole and executing trust-cluster.py will work. Is it correct?

Alternatively, trust_report.tsv files provide "cid" (assemble~), and the cids seem to be consistent with other samples'. So, can I substitute cid for cluster?

I'm wondering whether CDR3nt in the same cluster show similar antigenic specificities or their sequences are just similar.

I'd appreciate if you could reply.

Yes, you can put them together and then run the cluster script.
Though the cluster script does not use that column information, but you shall still rename the assembled contig's names in the cid column to track the samples.
The cluster is just based sequence similarity. For BCR, this is mainly for clustering the clonotypes from the same lineage that become different due to SHM.

Thank you for your prompt response!
As for cid, I found some of the same cids separating into a few lines, and their CDR3nt are slightly different. So, I'm interested in the difference between cid and cluster. Would you tell me about this?

cid is the consensus ID, where each consensus sequence may encode multiple CDR3 sequences. They will be automatically in the same cluster.

I understand. Thank you so much!


Accept injected useReducer function to enable reinspect to attach to bus

Currently we cannot tool useBusReducer with https://github.com/troch/reinspect because it automatically uses the React peer dependency.
Thinking syntax might be able to be something like this:
import React from "react";
import { useBusReducer } from "ts-bus";
import { useReducer } from "reinspect";

const useReducer = useBusReducer.with(useReducer);

export default function App() {
  const state = useReducer(...);
}

Workshopping the syntax a bit more @dmicic what do you think about this? I am starting to think configuring via options makes more sense as it enables us to mimic the React API:
import {useBusReducer} from 'ts-bus/react';

// The output shares the exact signature of the React equivalent
// This would be a breaking change
useBusReducer(reducer, initState, init);

import {useBusReducer} from 'ts-bus/react';

// Create a configured useReducer function
const useReducer = useBusReducer.configure({subscriber, useReducer});

// The output shares the exact signature of the React equivalent but with the configuration applied
useReducer(reducer, initState, init);

This would also be applicable to the useBusState PR: https://github.com/ryardley/ts-bus/pull/28

@ryardley In general, I like the the option based configuration idea. I would have to get my hands on reinspect to provide a constructive comment.
But some random thoughts... At first glance, the integration could work nicely. The event name can be used for the "id" parameter required by reinspect. The only issue I see if you have multiple subscribers per event. In that case, the react devTools would probably dump the message 1*n-subscribers time. It would be useful to display to which component/subscriber the state belongs to.
I've actually started aligning useBusState to react's useState. (However, still struggeling to extract the event name from the type in order to avoid the additional parameter #28)


Adwords reporting

How to use limit in reporting ?

Hi @nmfarshad  ,
Have you tried with during method?


[eslint-plugin] support Flat Config

ESLint v9 drops support for legacy .eslintrc style configuration files.  To move to v9 we need to migrate to the new Flat Config files.  This PR adds support for Flat Config file and migrate cosmos and identity-broker packages to use the flat config.  Legacy config files are still supported.
Some eslint plugins that we use don't support flat config yet so they are disabled.
Related issue: https://github.com/Azure/azure-sdk-for-js/issues/29750

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

/check-enforcer override


chore: AVM issue automation

Overview/Summary
Updates to better manage AVM related issues.
This PR fixes/adds/changes/removes

New issue templates for AVM
New GitHub policy service rules

Breaking Changes
n/a

@shenglol, as discussed in the previous weeks, we've prepared 2 new issue templates that help route/triage AVM related issues, and also automated many steps of the triage process using GH policy service. Please review/comment/approve. Thanks!


Fix styleguide link

Ahah, the fact that this changed needed to be made is kind of ironic.

Thanks so much for the fix @paked :-). I extracted your second commit into a separate pull request over in #62 so I don't also merge the test file included in this pull request.


[Feature Request] Allow the region to be set on AWS-signed requests to custom domains so that the signature is valid

Insomnia Version: ___
Operating System:  Windows 8.1

Details
I have a custom domain on API Gateway, example domain is myapi.example.com . The endpoint uses an AWS signature for authentication.  I want to be able to specify the region and the service to be used for the generated credential scope part of the signature, as the region  / service aren't in the custom domain.
As it is, the observed response from AWS to an API Gateway endpoint on my custom domain generates this:
{
	"message": "Credential should be scoped to a valid region, not 'us-east-1'. Credential should be scoped to correct service: 'execute-api'. "
}

My hypothesis is that without the custom domain (using a standard AWS domain such as xxx.execute-api.eu-west-1.amazonaws.com), the region and the service in the domain are used to set the credential scope part of the signature (which would be execute-api and eu-west-1 in this case).  However as my custom domain doesn't have the region or service as part of it, the region in the credential scope is defaulting to us-east-1, and the service is incorrect.  This then generates the error above.
A resolution would be to allow for the region and service to be set explicitly in the UI, and for those to then be used in the credential scope portion of the AWS sig.

Can this be reopened?

I've recreated in #830


Compile error

Trying to compile App6.cc
Get this:
zony@DESKTOP-LGIFS31:~/ns3/ns-allinone-3.29/ns-3.29$ ./waf
Waf: Entering directory `/home/zony/ns3/ns-allinone-3.29/ns-3.29/build'
[2684/2739] Compiling scratch/App6.cc
[2685/2739] Compiling scratch/scratch-simulator.cc
[2686/2739] Compiling scratch/subdir/scratch-simulator-subdir.cc
[2697/2739] Linking build/scratch/subdir/subdir
[2698/2739] Linking build/scratch/scratch-simulator
../scratch/App6.cc: In function ‘ns3::Ptrns3::Socket uniFlow(ns3::Address, uint, std::string, ns3::Ptrns3::Node, ns3::Ptrns3::Node, double, double, uint, uint, std::string, double, double)’:
../scratch/App6.cc:246:68: error: ‘TcpReno’ was not declared in this scope
246 |   Config::SetDefault("ns3::TcpL4Protocol::SocketType", TypeIdValue(TcpReno::GetTypeId()));
|                                                                    ^~~~~~~
../scratch/App6.cc:250:68: error: ‘TcpTahoe’ was not declared in this scope
250 |   Config::SetDefault("ns3::TcpL4Protocol::SocketType", TypeIdValue(TcpTahoe::GetTypeId()));
|                                                                    ^~~~~~~~

Hello, did you find a solution to that problem?

I discovered that this problem is caused by that the NS-3 team has deleted the TCP flavours used in this repo. But I haven't find out which version of NS-3 supports them.


Updated cve-bin-tool to 3.2

Description of changes
Updated cve-bin-tool to 3.2
Resolved build problems with packaging version
It was neccessary to update cve-bin-tool to a newer version to resolve problems
with building. cve-bin-tool<3.2 uses LegacyVersion which was removed from packaging>23.0, which is currently packaged in unstable.

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Contributes to ZHF #230712

packaging<22.0 is a required dependency according to #210230, so this PR is a no-go. Closing.
Also, the commit message didn't follow CONTRIBUTING.md.


Incompatible with Krypton

Minecraft Version: 1.17.1
Immersive Portals Commit: b6117d4
The conflicting mod's GitHub: https://github.com/astei/krypton
Mixin conflict, log here:
[02:20:11] [Server thread/FATAL]: Mixin apply failed krypton.mixins.json:shared.network.avoidwork.ThreadedAnvilChunkStorageMixin -> net.minecraft.class_3898: org.spongepowered.asm.mixin.injection.throwables.InvalidInjectionException InjectionPoint(Shift)[@At("INVOKE")] on net/minecraft/class_3898::sendChunkDataPackets$beSmart with priority 1000 cannot inject into net/minecraft/class_3898::method_18715(Lnet/minecraft/class_3222;[Lnet/minecraft/class_2596;Lnet/minecraft/class_2818;)V merged by qouteall.imm_ptl.core.mixin.common.chunk_sync.MixinThreadedAnvilChunkStorage_C with priority 1100 [PREINJECT Applicator Phase -> krypton.mixins.json:shared.network.avoidwork.ThreadedAnvilChunkStorageMixin -> Prepare Injections ->  -> handler$bca000$sendChunkDataPackets$beSmart(Lnet/minecraft/class_3222;[Lnet/minecraft/class_2596;Lnet/minecraft/class_2818;Lorg/spongepowered/asm/mixin/injection/callback/CallbackInfo;)V -> Prepare] org.spongepowered.asm.mixin.injection.throwables.InvalidInjectionException: InjectionPoint(Shift)[@At("INVOKE")] on net/minecraft/class_3898::sendChunkDataPackets$beSmart with priority 1000 cannot inject into net/minecraft/class_3898::method_18715(Lnet/minecraft/class_3222;[Lnet/minecraft/class_2596;Lnet/minecraft/class_2818;)V merged by qouteall.imm_ptl.core.mixin.common.chunk_sync.MixinThreadedAnvilChunkStorage_C with priority 1100 [PREINJECT Applicator Phase -> krypton.mixins.json:shared.network.avoidwork.ThreadedAnvilChunkStorageMixin -> Prepare Injections ->  -> handler$bca000$sendChunkDataPackets$beSmart(Lnet/minecraft/class_3222;[Lnet/minecraft/class_2596;Lnet/minecraft/class_2818;Lorg/spongepowered/asm/mixin/injection/callback/CallbackInfo;)V -> Prepare] 	at org.spongepowered.asm.mixin.injection.code.Injector.findTargetNodes(Injector.java:293) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.injection.code.Injector.find(Injector.java:240) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.injection.struct.InjectionInfo.prepare(InjectionInfo.java:375) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.transformer.MixinTargetContext.prepareInjections(MixinTargetContext.java:1255) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.transformer.MixinApplicatorStandard.prepareInjections(MixinApplicatorStandard.java:1033) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.transformer.MixinApplicatorStandard.applyMixin(MixinApplicatorStandard.java:388) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.transformer.MixinApplicatorStandard.apply(MixinApplicatorStandard.java:320) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.transformer.TargetClassContext.applyMixins(TargetClassContext.java:345) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.transformer.MixinProcessor.applyMixins(MixinProcessor.java:569) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.transformer.MixinProcessor.applyMixins(MixinProcessor.java:351) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.transformer.MixinTransformer.transformClass(MixinTransformer.java:208) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.transformer.MixinTransformer.transformClassBytes(MixinTransformer.java:178) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.transformer.FabricMixinTransformerProxy.transformClassBytes(FabricMixinTransformerProxy.java:23) ~[universe-loader-0.11.6.jar:0.9.4+mixin.0.8.2] 	at net.fabricmc.loader.impl.launch.knot.KnotClassDelegate.getPostMixinClassByteArray(KnotClassDelegate.java:162) ~[universe-loader-0.11.6.jar:?] 	at net.fabricmc.loader.impl.launch.knot.KnotClassLoader.loadClass(KnotClassLoader.java:154) ~[universe-loader-0.11.6.jar:?] 	at java.lang.ClassLoader.loadClass(ClassLoader.java:519) ~[?:?] 	at net.minecraft.class_3215.<init>(class_3215.java:87) ~[intermediary-universe-fabric-loader-0.11.6-1.17.1.jar:?] 	at net.minecraft.class_3218.<init>(class_3218.java:200) ~[intermediary-universe-fabric-loader-0.11.6-1.17.1.jar:?] 	at net.minecraft.server.MinecraftServer.method_3786(MinecraftServer.java:383) ~[intermediary-universe-fabric-loader-0.11.6-1.17.1.jar:?] 	at net.minecraft.server.MinecraftServer.method_3735(MinecraftServer.java:350) ~[intermediary-universe-fabric-loader-0.11.6-1.17.1.jar:?] 	at net.minecraft.class_1132.method_3823(class_1132.java:71) ~[intermediary-universe-fabric-loader-0.11.6-1.17.1.jar:?] 	at net.minecraft.server.MinecraftServer.method_29741(MinecraftServer.java:670) ~[intermediary-universe-fabric-loader-0.11.6-1.17.1.jar:?] 	at net.minecraft.server.MinecraftServer.method_29739(MinecraftServer.java:270) ~[intermediary-universe-fabric-loader-0.11.6-1.17.1.jar:?] 	at java.lang.Thread.run(Thread.java:831) [?:?] [02:20:11] [Server thread/ERROR]: Encountered an unexpected exception org.spongepowered.asm.mixin.transformer.throwables.MixinTransformerError: An unexpected critical error was encountered 	at org.spongepowered.asm.mixin.transformer.MixinProcessor.applyMixins(MixinProcessor.java:363) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.transformer.MixinTransformer.transformClass(MixinTransformer.java:208) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.transformer.MixinTransformer.transformClassBytes(MixinTransformer.java:178) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.transformer.FabricMixinTransformerProxy.transformClassBytes(FabricMixinTransformerProxy.java:23) ~[universe-loader-0.11.6.jar:0.9.4+mixin.0.8.2] 	at net.fabricmc.loader.impl.launch.knot.KnotClassDelegate.getPostMixinClassByteArray(KnotClassDelegate.java:162) ~[universe-loader-0.11.6.jar:?] 	at net.fabricmc.loader.impl.launch.knot.KnotClassLoader.loadClass(KnotClassLoader.java:154) ~[universe-loader-0.11.6.jar:?] 	at java.lang.ClassLoader.loadClass(ClassLoader.java:519) ~[?:?] 	at net.minecraft.class_3215.<init>(class_3215.java:87) ~[intermediary-universe-fabric-loader-0.11.6-1.17.1.jar:?] 	at net.minecraft.class_3218.<init>(class_3218.java:200) ~[intermediary-universe-fabric-loader-0.11.6-1.17.1.jar:?] 	at net.minecraft.server.MinecraftServer.method_3786(MinecraftServer.java:383) ~[intermediary-universe-fabric-loader-0.11.6-1.17.1.jar:?] 	at net.minecraft.server.MinecraftServer.method_3735(MinecraftServer.java:350) ~[intermediary-universe-fabric-loader-0.11.6-1.17.1.jar:?] 	at net.minecraft.class_1132.method_3823(class_1132.java:71) ~[intermediary-universe-fabric-loader-0.11.6-1.17.1.jar:?] 	at net.minecraft.server.MinecraftServer.method_29741(MinecraftServer.java:670) ~[intermediary-universe-fabric-loader-0.11.6-1.17.1.jar:?] 	at net.minecraft.server.MinecraftServer.method_29739(MinecraftServer.java:270) ~[intermediary-universe-fabric-loader-0.11.6-1.17.1.jar:?] 	at java.lang.Thread.run(Thread.java:831) [?:?] Caused by: org.spongepowered.asm.mixin.throwables.MixinApplyError: Mixin [krypton.mixins.json:shared.network.avoidwork.ThreadedAnvilChunkStorageMixin] from phase [DEFAULT] in config [krypton.mixins.json] FAILED during APPLY 	at org.spongepowered.asm.mixin.transformer.MixinProcessor.handleMixinError(MixinProcessor.java:642) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.transformer.MixinProcessor.handleMixinApplyError(MixinProcessor.java:594) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.transformer.MixinProcessor.applyMixins(MixinProcessor.java:356) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	... 14 more Caused by: org.spongepowered.asm.mixin.injection.throwables.InvalidInjectionException: InjectionPoint(Shift)[@At("INVOKE")] on net/minecraft/class_3898::sendChunkDataPackets$beSmart with priority 1000 cannot inject into net/minecraft/class_3898::method_18715(Lnet/minecraft/class_3222;[Lnet/minecraft/class_2596;Lnet/minecraft/class_2818;)V merged by qouteall.imm_ptl.core.mixin.common.chunk_sync.MixinThreadedAnvilChunkStorage_C with priority 1100 [PREINJECT Applicator Phase -> krypton.mixins.json:shared.network.avoidwork.ThreadedAnvilChunkStorageMixin -> Prepare Injections ->  -> handler$bca000$sendChunkDataPackets$beSmart(Lnet/minecraft/class_3222;[Lnet/minecraft/class_2596;Lnet/minecraft/class_2818;Lorg/spongepowered/asm/mixin/injection/callback/CallbackInfo;)V -> Prepare] 	at org.spongepowered.asm.mixin.injection.code.Injector.findTargetNodes(Injector.java:293) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.injection.code.Injector.find(Injector.java:240) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.injection.struct.InjectionInfo.prepare(InjectionInfo.java:375) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.transformer.MixinTargetContext.prepareInjections(MixinTargetContext.java:1255) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.transformer.MixinApplicatorStandard.prepareInjections(MixinApplicatorStandard.java:1033) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.transformer.MixinApplicatorStandard.applyMixin(MixinApplicatorStandard.java:388) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.transformer.MixinApplicatorStandard.apply(MixinApplicatorStandard.java:320) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.transformer.TargetClassContext.applyMixins(TargetClassContext.java:345) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.transformer.MixinProcessor.applyMixins(MixinProcessor.java:569) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	at org.spongepowered.asm.mixin.transformer.MixinProcessor.applyMixins(MixinProcessor.java:351) ~[sponge-mixin-0.9.4+mixin.0.8.2.jar:0.9.4+mixin.0.8.2] 	... 14 more

Associated issue report: https://github.com/astei/krypton/issues/46

Turns out even after that mixin is disabled, there is a memory leak in direct buffers when running with Immersive Portals.

@Justsnoopy30 I roughly read through Krypton code and see that, apart from that Mixin, IP does not change anything that Krypton changes.
How did you get the conclusion that the memory leak is in direct buffers? You can use /portal debug profile gc to enforce a GC and see the real memory usage.

Can confirm Krypton + ImmP leaks on MC 1.18.1
Which side is the conflicting side, however, I know not.

I will mark it incompatible in fabric.mod.json

I decided to take a look for myself. Disabling the Krypton mixin me.steinborn.krypton.mixin.shared.network.avoidwork.ThreadedAnvilChunkStorageMixin fixes the incompatibility.
I cannot reproduce @Justsnoopy30's direct buffer memory leak with Immersive Portals and Krypton alone. I ran the game for about 10 minutes with the JVM argument -Dio.netty.leakDetection.level=paranoid, which would have immediately flagged any direct buffer memory leaks if there were any. It did not print any warnings, and given Minecraft's abuse of the JVM garbage collector, I would have easily expected a warning to pop up in the first few seconds.
astei/krypton@b251fa0 fixes the incompatibility on my end.

@astei Thanks for your effort.

@astei thanks for looking into it! 👍🏻


Crash with EnderIO Cables in same block space

Issue Description:
Placing a soul cage down with two enderio cable sharing the same block space causes the server to crash and continue to crash every time the world is loaded.
What happens:
When a soul cage has two different EnderIO cables sharing the same block space near it, it crashes the server.
What you expected to happen:
Regular interaction
Steps to reproduce:

Place down soul cage
Place down redstone conduit underneath
Place down energy conduit (2nd tier) in same blockspace
...

Affected Versions (Do not use "latest"):

Soul Shards: SoulShardsRespawn-1.12.2-1.0.5-7
Minecraft: 1.12.2
Forge: <IP_ADDRESS>39

Log: https://paste.ee/p/0ZigE

idk if you noticed, but this does not mention Soul Shards: The Old Ways anywhere.
You can find the Soul Shards: Respawn repo here

Fixed by https://github.com/TehNut/Soul-Shards-Respawn/commit/bccaa374e70968cf9df2f21894c61d650da37d96


{Front Door} Fix #5625: az network front-door waf-policy create: Update help message for --policy-name

fixes Azure/azure-cli-extensions#5625 Update the help message for PolicyName
Giving "-" 'hyphen' in the policy name fails. The help message should include that the " Name must begin with a letter and contain only letters and numbers."

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

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify src/index.json.

AzureFrontdoor

Hi.
Can you please try to implement this change to deployment using bicep/arm via pipeline as well?
The error I get from (I suspect, using - in the policy name as well) trying to create a policy is this:
{"code":"BadRequest","message":"WebApplicationFirewallPolicy validation failed. More information "Policy ArmResourceId has incorrect formatting"."}
Took me a while to find this page...
Thanks


ComputeRP 2022-08-01 release

Creating new branch/PR from https://github.com/Azure/azure-rest-api-specs/pull/20510 because that branch had a large amount of unrelated files changes somehow
Features in this file:
https://github.com/Azure/azure-rest-api-specs/pull/20083 - adding property
https://github.com/Azure/azure-rest-api-specs/pull/20211 - adding property
https://github.com/Azure/azure-rest-api-specs/pull/20076 - adding property
https://github.com/Azure/azure-rest-api-specs/pull/20079 - adding property
https://github.com/Azure/azure-rest-api-specs/pull/20097 - breaking change; approved
ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[x] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

added "Approved-Breakingchange" tag since it was approved here in the child PR https://github.com/Azure/azure-rest-api-specs/pull/20097

@mentat9 your comments are addressed. Please take a look again

@ArcturusZhang pls review/merge

@ArcturusZhang thank you for merging Haider's 2022-07-02 version PR.
I've resolved the conflict. Please merge this one also

Approved for Go breaking. @Alancere When release, please wait for the codegen change and add proper flags. Thanks.


Fixing IE gradient

Shorthands for colors not allowed in IE gradients.
Bootstrap use them a lot.
Result is painfully 80ish.
Compass already implements a hack, thinking about doing the same for bootstrap-sass:
https://github.com/thomas-mcdonald/bootstrap-sass/issues/14
http://pinds.com/2011/11/30/fixing-ie-gradients-with-rails-3-1-and-scss/
cc @thomas-mcdonald @rjackson

I think it's ok if sass pulls this in. It's life is limited tho, IE is getting on the CSS3 bandwagon.

link to code: https://github.com/chriseppstein/compass/blob/stable/lib/compass/sass_extensions/functions/colors.rb#L35-42

+1 bootstrap-sass doesn't seem to be able to precompile assets without this because rake isn't loading it's hack

+1 This would be a boon…

+1

Closed by 374d8c94b2c794d5b73ad7218f1fd5367755dd7b.


test PR with Github API

Please pull this in!

Docs Build status updates of commit 009e530:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

sdp-test/index.md
:white_check_mark:Succeeded

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.


Provide a configurable resolution for classes

Default is Simpleclassname
Other is FQN for classes
Add the ClassResolution object to the configuration.

PR #34


Detect MSVC 2017. Closes #1003

Rust itself won't actually work until it is also updated. This just lets rustup install without a warning.

@brson Error looks legit!

OK, I think I see the issue.

Testing using a temporary branch of gcc-rs

Oh yay!

@bors r+

:pushpin: Commit 99cbfe0 has been approved by brson

:hourglass: Testing commit 99cbfe0 with merge 6dead9a...

still just testing

:pushpin: Commit 99cbfe0 has been approved by brson

@bors r+

:hourglass: Testing commit 99cbfe0 with merge 089e2c4...

:broken_heart: Test failed - status-appveyor

@bors retry
Spurious. Suspicious.

:hourglass: Testing commit 99cbfe0 with merge c60e5e4...

:sunny: Test successful - status-appveyor, status-travis
Approved by: brson
Pushing c60e5e4f046eef7d795d85b11e6801c6ca701459 to master...


 Running locally on regtest.
Also, be sure to pull new images from dockerhub, as I updated a few of them. Perhaps this is the part we should automate or offer to do as an inquirer option during deploy?

try on signet?

How do I enable signet?

There is a signet test you can use. I saw this failure while testing out Galen Eros


Example to run yolo model on NPU

I made some sample code to show how to use the NPU to run a yolo model on mp4 files.
Currently it runs in real time on my Snapdragon X Elite Dev Box. Twice as fast as the Yolov4 GPU DirectML sample while using less than half the power.
You can see it here: https://github.com/fobrs/yolov9_npu
Should I make a pull request?

wow, nice work man Thanks!
I'm thinking hard and long about selecting a platform to deploy an assembly-of yolo models on-to.
And surface-pro with the snapdragon elite chip comes to mind. But i have no confidence in it.

I hoped Qualcomm would have had all NPU drivers 100% ready when they started shipping the Copilot Laptops. BUT that's not the case. DirectML is not 100% supported. Not all ONNX models run without errors, only Qualcomm approved ones from their AI Hub. The latest version of the demo supports running some models on the GPU (Press G). A Yolov8s-seg.onnx model, not approved by Qualcomm runs ok on the GPU, but with errors on the NPU.
And something about the speed, my 5 year old Dell precision, with an nVidia RTX 3000 graphics adapter runs these yolo models as fast as the Qualcomm NPU. I guess the speed Qualcomm advertises is from running quantized (int8) models.


[$1000] mWeb - Close Account - Scroll bar is black color instead light green

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to URL https://staging.new.expensify.com/
Login with any account
Go to Settings > Security > Close Account
Enter the any letter and tap Return button
Do it until you can see the scroll bar

Expected Result:
The scroll bar should be light green
Actual Result:
Scroll bar is black color
Workaround:
Unknown
Platform:

Where is this issue occurring?

Mobile Web (only Safari)

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/207699235-6070cf18-cfcd-4cb4-a64e-f956e249c57a.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~013fdb138457063279
Upwork Job ID:<PHONE_NUMBER>957001216
Last Price Increase: 2022-12-15

Proposal
If we want to change scrollbar color we can just add this CSS.
textarea {
  scrollbar-width: thin;
  scrollbar-color: #03d47c transparent;
}
textarea::-webkit-scrollbar {
  width: 6px;
}
textarea::-webkit-scrollbar-track {
  background-color: transparent;
}
textarea::-webkit-scrollbar-thumb {
  background-color: #03d47c;
  border-radius: 6px;
  border: 3px solid #03d47c;
}

It will work on cross browser.
Ios safari mobile web working example.

I believe this issue to be a dupe of GH Issue. As we might end up updating -webkit-scrollbar styles there it will fix the issue of scrollbar inconsistency in the app. It should be fixed automatically here also. I think it should be put on hold till then.

do you mean this issue?

Proposal
If we want to change scrollbar color we can just add this CSS.
textarea {
  scrollbar-width: thin;
  scrollbar-color: #03d47c transparent;
}
textarea::-webkit-scrollbar {
  width: 6px;
}
textarea::-webkit-scrollbar-track {
  background-color: transparent;
}
textarea::-webkit-scrollbar-thumb {
  background-color: #03d47c;
  border-radius: 6px;
  border: 3px solid #03d47c;
}

It will work on cross browser.
Ios safari mobile web working example.

this will works, but it has ability to affect others).
This is my suggestion.

Proposal
Actually this problem exists for all scrollbars throughout the app and is a complex problem for iOS & android as react-native doesn't provide an easy way to do this.
All platforms
For iOS we do have an indicatorStyle prop for scrollview with values either 'light', 'dark' or 'default' but nothing for custom colour. It can be implemented in native code or we can hide the native scrollbars and create our custom scrollbar and display it over the scrollview with the help of Animated API and a few scroll events, somewhat like this but that will need to be implemented for Flatlists too.
Sorry, I am currently not in a position (time-wise) to provide the full code for this.
Web only solution:
Add the below css in web/index.html
/* Customize scrollbar color & width for firefox */
body {
    scrollbar-width: thin;
    scrollbar-color: #03d47c transparent;
}
/* Customize scrollbar color & width for most browsers except firefox */
::-webkit-scrollbar {
    width: 4px;
}
::-webkit-scrollbar-track {
    background-color: transparent;
}
::-webkit-scrollbar-thumb {
    background-color: #03d47c;
    border-radius: 4px;
}

I agree with @syedsaroshfarrukhdot that this is a dupe. Let's close this and tackle it in https://github.com/Expensify/App/issues/12914


Set main to es5/server

What's the point to have main = src/server? For older NodeJS installations users have to manually alter it to fetch-mock/es5/server and this breaks compatibility with browser property of package.json, Webpack cannot locate proper file, so the code can't be universal.

Which node version? If it's 0.x then I'm afraid that defaulting to the uncompiled source code makes it easier to work with in newer node versions, and that's a bigger priority for me. If src/server won't run on  a later version of node then that's a bug which I'll fix.
Could you explain the problem you're having with webpack? Webpack is very configurable, and you can point most file path strings at any file you want using the resolve.alias property in config.

I have same set of tests for:

Browser
Node 0.x
Node 4+

Browser tests are compiled by webpack so yes, there I can use alias. But for Node 0.x I need to point to es5/server. So webpack is unable to pick up proper version w/o manual alias, which is bad.
Since you still deliver the pre-compiled version too, what's the point to deliver both? Why not just precompiled for all Node versions + proper browser property in package.json, this will allow config-free usages for all use cases.

It's an easier development and debugging workflow working in the src code rather than compiled. As pretty much the only maintainer of this repo I'm going to stick to my priorities here.
You should be able to use es5/server in all your tests, and then use a webpack alias in the browser to point it at es5/client, so there is a workaround available. If you want to add this to the bottom of the README I'd accept a PR.

I totally understand your priorities :)
I did the stuff exactly as you described and it's kinda awkward... 2 workarounds (fetch-mock/es5/server require instead of just fetch-mock and alias in Webpack config) is really an overkill for such an easy case.
Btw, what's there in the SRC that can't be ported to ES5 (manually) so that all Node versions will always use same SRC? I mean are you sure that benefits of having advanced stuff in SRC outweighs downsides (build procedure, tricky configuration for old Nodes, README sections, etc.)?

It's mainly arrow functions. While it is would be possible to convert the code to be node 0.x compatible, unless there's something in CI to test in multiple versions of node, then it'll be vulnerable to regressions.
I sympathise with your having to write hacky workarounds to get your tests running in node 0.12, but even nodejs doesn't officially support 0.12 any more, so I don't feel I should optimise for a deprecated environment. If there were no workarounds possible then I would be open to changing the codebase to support 0.12.


Add .npmignore back to root

Description
The .npmignore file was removed in v1.3.0: 6885af6b0a6b984a90fe203f00451316656f1355
This PR adds it back so that the npm publish size is smaller.
Code sample
You can see the effect of removing npmignore with Package Phobia

@styfle Good call 🚀


Video Review - Drew

Do the review and add to VideoReviews.md

Fixed by https://github.com/SheffieldSoftwareCarpentry/InstructorTraining2015/pull/29


Switches are working but lock is not working

Hi,
In HASS, I have the following for lock, but I cannot lock/unlock through homeassistant.  But I am able to turn on switch/lights.
lock:

platform: mqtt
name: "Front Door"
state_topic: "smartthings/Front Door/lock"
command_topic: "smartthings/Front Door/set"
payload_lock: "LOCKED"
payload_unlock: "UNLOCKED"

switch:

platform: mqtt
name: "Lamp"
state_topic: "smartthings/Lamp/switch"
command_topic: "smartthings/Lamp/switch"
payload_on: "on"
payload_off: "off"
retain: true

I also seem to be having this same issue.

This is what is working for me:
state_topic: "smartthings/Front Door/lock"
command_topic: "smartthings/Front Door/lock"
payload_lock: "locked"
payload_unlock: "unlocked"


useSessionStorage improvements

This PR has 3 changes for the useSessionStorage hook:

It allows an initial value function to be used without provoking TS errors.
It eliminates changes to the hook state when another instance of the hook with a different storage key is updated.
It ensures that the value set to the hook is referentially equal to the value reported by the hook.

I love the library! Please let me know how I can improve the PR for your approval!

Hi @sskirby, thanks for the PR. I will unfortunately close it because most of the changes already have been addressed now, see #435, #436 and #437


HTTP range download for large dependencies

Expected Behavior
When downloading large dependencies, gradle should be able to use HTTP Range header to recover download from previous breakpoint.
Current Behavior (optional)
Gradle starts to re-download from the first byte for those not downloaded dependencies.
Context
I was trying to create an IDEA plugin, then I found it was trying to download an IDEA CE zip as dependency, which is nearly 1 Gb.
Once there is something wrong when downloading such large dependency, you have to re-download the whole zip even if you have downloaded the first 800 Mb in the past 10 minutes.
It took me almost a morning to setup the project in the end, which decourage me a lot from trying new things.

I'd like to know if this feature should be implemented in Gradle itself or in a standalone Gradle plugin, and which classes should I pay attention to if I want to make a PR or create a plugin.

Do Maven repositories support that?

Maven central repository support HTTP range header:
curl "https://repo1.maven.org/maven2/org/springframework/spring-core/6.1.12/spring-core-6.1.12.jar" -o spring-core-6.1.12.jar -H "Range: bytes=0-100"

Some organizations use Sonatype nexus maven repository to setup private maven repositories, which support HTTP range header too:

IntelliJ IDEA repository support HTTP range header:
curl "https://www.jetbrains.com/intellij-repository/snapshots/com/jetbrains/intellij/idea/ideaIU/LATEST-EAP-SNAPSHOT/ideaIU-LATEST-EAP-SNAPSHOT.zip" -o ideaIU-LATEST-EAP-SNAPSHOT.zip -H "Range: bytes=0-100" -L

There is a straightforward work flow design:
flowchart TD
    A((Start)) --> B{Does repository support range request ?}
    B --> |Not support| B1C[Download as usual]
    B --> |support|B2C[(Record downloaded progress in database)]
    B1C --> B1D{Download completed ?}
    B1D --> |Not completed|Error((Error))
    B1D --> |Completed|End((End))

    B2C --> B2D{Download completed ?}
    B2D --> |Not complete| B2F[Download next part]
    B2F --> B2C
    B2D --> |Completed|End

Download progress could be stored in any kind of database:

option 1: some files containing downloaded bytes number under certain directory
option 2: embeded sql database like H2, SQLite

the location of the partially downloaded files and how this location will be cleaned

What about the user's temp folder for windows user?
It usually located at %userprofile%\AppData\Local\Temp, eg: C:\Users\Admin\AppData\Local\Temp .
This folder will not be cleaned by the system automatically: https://superuser.com/questions/296824/when-is-a-windows-users-temp-directory-cleaned-out

There is more description of how to operate temp dir in Java: https://docs.oracle.com/en/java/javase/21/docs/api/java.base/java/io/File.html#createTempFile(java.lang.String,java.lang.String,java.io.File)

@DevDengChao We should not rely on that OS-specific behavior. And there is a relevant open issue that is planned to be addressed:

https://github.com/gradle/gradle/issues/15367

What about put the partially downloaded files to the folder where they finally goes to ?
Then all you need to do is add a .part suffix when creating the file, and remove that suffix after download completed.
Just like what gradle wrapper does:

This sounds promising. I think you can re-use that logic from the wrapper code.

For temp file logic, take a look at org.gradle.wrapper.Install#forceFetch, org.gradle.caching.local.internal.DefaultBuildCacheTempFileStore, and org.gradle.jvm.toolchain.internal.install.SecureFileDownloader#downloadResource
For changing the code, you can start from org.gradle.api.internal.artifacts.repositories.DefaultMavenArtifactRepository and org.gradle.internal.resource.transport.http.HttpConnectorFactory

the number of downloaded bytes can be tracked by querying the file itself.

There is something wrong when tracking downloaded size from a partial file. :rofl:


investigate why release build dies on macos

note, this only happens on travis-ci... must be some sort of discrepancy in the packages

nope, swift version was the problem (i was running 3.0.2 on my local). bumped xcode version from 8.1 to 8.2 on travis yaml which made swift version 3.0.1 -> 3.0.2. this resolved the issue.


Function nesting

Have to clean up the code and remove all that function nesting.

Fixed with releases keteg-2.0.0 and mhwd-2.0.0!


Exterminator's branch

Merging the rest of the files in and redoing the file structure

There were some bugs in the code listed here:
Script Tag in Head (head script disabled)
no closing > for header
no closing header tag

awesome! thank you!


Detect not functioning Tor before start not in runtime

Related: https://github.com/nopara73/HiddenWallet/issues/27

Fixed: https://github.com/nopara73/HiddenWallet/commit/8d9e05f4ad1794df22ac938d0b108e5fcdcfd8ba


[Commerce] Refactor md-commerce-panel-filled

Ideally we shouldn't be creating utility classes with a md prefix. Refactor.

Think about changing to commerce-sidepanel


Registration page throws fatal

An exception has been thrown during the rendering of a template ("No element by the name of [tos] found in form") in "user/user/register" at line 10.
@inyono I believe this to be caused by your latest changes to the ToS thingy. Could you please take a look at it?

Are you sure that all files are updated? Since user/user/register.twig has no more usage of tos

Ok thanks, I'll look into it

It was indeed a problem with the cache.


Exllama kernels

for https://github.com/casper-hansen/AutoAWQ/pull/313

I have a few questions about the ExLlama kernels.

Is it necessary to include v1 and v2, why not just v2 (seems they are better)?
Are these kernels updated with the latest commits from ExLlamaV2?

I think it's always best to have a fallback in case exllamav2 doesn't work or build, an example is exllamav2 not building on rocm6.0 https://github.com/AutoGPTQ/AutoGPTQ/pull/515/files
Not sure, the ones in the original repo contain a lot of unused components (e.g. moe specific stuff). I took the one in AutoGPTQ for now, which I believe to be minimal and fixed for AutoAWQ (bit overflow from removing and adding 1 to zeros).