Test

Why is your build failing?

This is because the constructor of my BaseModel class needs a .env file. And the file is not being located on travis.

You can put environment variables on Travis. Check the settings tab

I tried that already. The dotenv package requires the actual .env file to be readable.

I'm getting this on travis

Have you tried doing something like this:
optionally specify a list of environments, for example to test different RDBMS
env:

DB=mysql
DB=pgsql

Adding it from the .travis.yml file

I have:

-DB=mysql

Just that?..What of the remaining env variables?

Not anymore. I have put in all the variables. It's still failing.

I guess you would have to use the getenv function instead of the $_ENV you used


Migrate CI/CD to GitHub Actions

As described in  accordproject/technical-steering-committee#4
Please follow the conventions in https://github.com/accordproject/concerto/pull/236

[x] Remove secrets from Travis (for AP maintainers: in Travis Repository Settings)
[x] Disable Travis in the configuration (for AP maintainers: Travis Personal Profile > Settings > Accord Project
[x] Remove .travis.yml and .travis directories in repo
[x] Add .github/workflows directory based on those in ./concerto/.github/workflows
[x] ~Remove scripts in ./scripts replace by those found in ./concerto/scripts~
[x] Fix package.json notable adjustments: remove some of the old scripts, ~make sure code coverage works~
[x] ~Test build on PR with timestamps~
[x] ~Test build on GitHub release with version number~
[x] Update GitHub "branch protection" rules to point to the new workflows instead of Travis

@mttrbrts can I take this?

@mttrbrts can I take this?

Done and done! Your changes are now how we do CI in this repo. Thank you @Aniruddha-Shriwant for the great contribution (and being responding to requests for changes).


exclude reference terminal from port counting

Great catch@ring630!
Can you add a unit test? It seems we were not checking it. This could be the opportunity to avoid regressions in next modifications.

Great catch@ring630! Can you add a unit test? It seems we were not checking it. This could be the opportunity to avoid regressions in next modifications.

Done


Cleanup LocationGlobber and related code

PR Summary

Exclude extra IsHomePath() calls
Make AddQualifier() and RemoveQualifier() static
Make close code being span-based to reduce allocations

PR Context
First motivation was to exclude extra IsHomePath() calls.
LocationGlobber code is based on string operations and so it is a source of a huge amount of memory allocations. Then some low level methods was optimized with using ReadOnlySpan-s to reduce allocations and increase performance. This will later help to further optimize the performance of this code.
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[ ] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[x] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[ ] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

@TravisEz13 @daxian-dbw @SteveL-MSFT Could you please review? I want to continue with improvements in the LocationGlobber code.

@TravisEz13 Have you time to review the LocationGlobber cleanup?

I'm very uncomfortable change this code.  Very minor behavioral changes can result in large real changes.  I can mark the changes I think are at high risk of regression.

I think changes in the location globber are too risky at this point in the release.

Rebased to get latest commits for the old branch.

I feel like the risk in cleaning up the location globber is high.  We need to make sure we have tests for all altered code paths.
@daxian-dbw What do you think?

The PR does not contain functional changes. Also the code is well-covered by tests - we have many usages of cmdlets with Path and LiteralPath parameters.

I'd like to see a code coverage report so that I can review as see if new tests are needed.

I'd like too. MSFT team is working on the report for years. It says that it is not important for the project.

I'd like too. MSFT team is working on the report for years. It says that it is not important for the project.

You can produce one yourself
https://github.com/PowerShell/PowerShell/blob/b1e998046e12ebe5da9dee479f20d479aa2256d7/docs/testing-guidelines/getting-code-coverage.md

@TravisEz13 After bit investigations I see that we switched from OpenCover to CodeCov and our CIs generate code coverage artifacts for all platforms but these report is not uploaded to CodeCov site.
CodeCov docs say that the site supports report merging. Also it is possible set a custom flag at uploading report time. (Although there is a note that this is disabled in the Compare page temporarily). The feature allows upload many reports from different CIs for the same commit/PR. It seems that is what was required for cross-platform code coverage reports? Can MSFT team resume this uploading?


Bug: serialization of list items in forms when the list has a single element leads to a 400

Description
real-life situation is the following:

I have a form with a select, that has the multiple attribute
user can either select one or more entries, the resulting payload will be li=1 in case he chooses one element, li=1&li=2&li=3 if he chooses more
2.1. if he chooses more than one entry then validation works as intended, see tests 1 and 2 from the parametrization above
2.2. if he chooses only one entry, then a 400 occurs, which I think is incorrect, I should retrieve [1] in the handler

the following tests depicts I think the above, when I pass only one integer while the form is declared to expect list[int].
main...euri10:forms?expand=1#diff-13fb84aa44
URL to code causing the issue
No response
MCVE
# Your MCVE code here

Steps to reproduce
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Screenshots
"![SCREENSHOT_DESCRIPTION](SCREENSHOT_LINK.png)"

Logs
No response
Litestar Version
2.0.0beta3
Platform

[X] Linux
[ ] Mac
[ ] Windows
[ ] Other (Please specify in the description above)

Funding

If you would like to see an issue prioritized, make a pledge towards it!
We receive the pledge once the issue is completed & verified

So, this is not a bug par se. We cannot know from the form data whether its a list or not given the serialization format of multipart. Thus - single elements are not assumed to be a list. You can bypass this in one of two ways:

you can send serialized json arrays as values: "[1,2,3,4]” and we will deserialize this into a json list.
you can type you handler to receive a single or list: str | list[str] etc. This will also work.


Visual order of rows doesn't match DOM elements - causes tabbing into the grid to enter at the wrong row

I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[ x ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/ceolter/ag-grid/blob/master/CONTRIBUTING.md#question

(this could be labelled as a bug, but I assume it's by design)
Current behavior
The ordering of rows in the DOM doesn't match the visual rows. This doesn't cause issues for ag-grid itself because the rows are all placed as absolute elements with a fixed top offset and tabbing is handled by JS code. It does cause an issue however when you tab into the grid (we use input fields in our cell renderers allowing this to work), as this key event is still handled by DOM order/tabindex, causing the browser to focus the first row in the DOM (and that's quite often a row in the middle of the visual data set).
Expected behavior
The DOM should match the visual data.
Minimal reproduction of the problem with instructions
https://www.ag-grid.com/example.php inspecting the DOM while scrolling the grid.
What is the motivation / use case for changing the behavior?
Tabbing into the grid from another part of the page.

ag-Grid version: 8.2.0
If https://www.ag-grid.com/example.php uses 9.0.0 it's still an issue.

Browser:
"Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36"
"Mozilla/5.0 (Windows NT 6.1; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0"

Language: all

this is a tricky one to solve. thanks for raising. i have added 'tabbing into the grid' as a jira, it's number AG-419
two solutions i see:

when user tabs into the grid, somehow put the focus on the first row - which would be tricky if the user is scrolled down.
let the user decide somehow how to handle this. i think this is a can of worms, whatever we implement is bound to not work for everyone, as how you should tab into a grid that is scrolled half way down is open to user interpretation. eg if 1000 rows, and you are scrolled half way down, do you focus on row 500 (the first visible row) or row 1? and if row 500, what if the grid has some rows in the buffer? (the grid can draw a few rows extra, a buffer of rows above and below the viewport), then again what happens if a row is half visible?

because of the difficulties present, it may be better to document how to catch the tab event, and then let the user decide which row / cell gets the focus. it would be ag-grid's job to make sure this callback mechanism exists for the user.

because of the difficulties present, it may be better to document how to catch the tab event, and then let the user decide which row / cell gets the focus. it would be ag-grid's job to make sure this callback mechanism exists for the user.

This sounds like a decent solution. I could currently think of people asking to always tab into the first row (total), into the first visual row (based on scrolling) and we probably have a use case for the last total row (as it's an input dummy that acts as a search field).

Hi,
We are changing the process and closing all issues with a ticket number since they can be tracked from our pipeline https://www.ag-grid.com/ag-grid-pipeline/
Thanks
===============
If you are an ag-Grid Enterprise Customer, please raise this in our Zendesk support system - contact<EMAIL_ADDRESS>for access. This is our primary channel for Support.
Bugs Raised Here:
We will do a periodic review of GitHub issues for any bugs raised and these can be tracked on our pipeline page: https://www.ag-grid.com/ag-grid-pipeline
Feature Requests/Support Raised Here:
We are reviewing how we process Feature Requests that come from GitHub. We currently have a very full pipeline of work which will be our priority for the coming months.
As a result, we don’t have capacity to take feature requests from GitHub.
We will review this as we move through our current backlog.
Thanks for your understanding.
ag-Grid Team.


frontend listing tasks

[ ] creating/ scheduling tasks
[ ] list tasks (use this for cron strings)
[ ] stop/delete tasks

Originally posted by @jjjpanda in https://github.com/jjjpanda/Chimera/issues/78#issuecomment-963809281

use tabs and 2 lists

upcoming
all

with extra content being a button that opens a modal to create a task


Create Server Count command

I have done this this morning on my phone, so check for errors before merging.

Changes look good, definitely want to see this.

It is basicly only copied from the premium count command and from the server list command. I just copied everything from server list and removed the old an putted in the new stuff... But nice to see that you like it and it seems tohave no errors


Old cookie sent in requests if any code is placed in the afterResponse script

Expected Behavior
If I have a code in the afterResponse script (say to set an environment variable), after the request, any cookies saved by insomnia should be present in further requests.
Actual Behavior
Once there is a code in the afterResponse script (even if it is commented out), cookie session breaks. New cookies gotten in response does not override the old cookies saved, even though insomnia tries to save the new cookies.
Reproduction Steps

Build an endpoint that returns a cookie (random string) in the header.
Make a request to the end point and observe the cookie returned.
Make a request to the same endpoint again and observe that the cookie previously returned was sent in the request header.
Write anything in the afterResponse script (you can comment it out if you want).
Make a request to the same endpoint and observe the new cookie returned
Make another request to the same endpoint and observe that the cookie sent in the request header is the old one (not the latest one returned)

Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
You can do a simple express project that returns a cookie
Insomnia Version
9.3.3
What operating system are you using?
macOS
Operating System Version
Sonoma 14.5
Installation method
Download from Insomnia website
Last Known Working Insomnia version
No response

duplicate of #7808, it should have been fixed in the latest v10.0.

Hello @specialobyno please try the latest version (10.0.0) and thanks for your detailed feedback.


Reduce required boilerplate for implementing external simulators and samplers

I wrote a custom simulator recently and I had to copy quite a bit of boilerplate code out of cirq/sim/sparse_simulator.py.  Below is my code with the boilerplate pointed out.  It would be nice if the code in SimulatesSamples and SimulatesIntermediateState parent classes were rearranged to reduce this.  @Strilanc
class MySimulator(cirq.SimulatesSamples,
                  cirq.SimulatesIntermediateState):
    # Boilerplate
    def _run(self, circuit, param_resolver, repetitions):
        param_resolver = param_resolver or cirq.ParamResolver({})
        resolved_circuit = cirq.resolve_parameters(circuit, param_resolver)
        assert not cirq.is_parameterized(resolved_circuit)
        return self._run_sweep_repeat(resolved_circuit, repetitions)

    # Boilerplate
    def _run_sweep_repeat(self, circuit, repetitions):
        measurements = defaultdict(list)
        for _ in range(repetitions):
            all_step_results = self._base_iterator(
                circuit,
                qubit_order=cirq.QubitOrder.DEFAULT,
                initial_state=0)
            for step_result in all_step_results:
                for k, v in step_result.measurements.items():
                    measurements[k].append(np.array(v, dtype=np.uint8))
        return {k: np.array(v, dtype=np.uint8) for k, v in measurements.items()}

    # Boilerplate
    def _simulator_iterator(self, circuit, param_resolver, qubit_order,
                            initial_state):
        param_resolver = param_resolver or cirq.ParamResolver({})
        resolved_circuit = cirq.resolve_parameters(circuit, param_resolver)
        assert not cirq.is_parameterized(resolved_circuit)
        actual_initial_state = 0 if initial_state is None else initial_state
        return self._base_iterator(resolved_circuit, qubit_order,
                                   actual_initial_state,
                                   perform_measurements=True)

    def _base_iterator(self, circuit, qubit_order, initial_state,
                       perform_measurements=True):
        # Boilerplate
        qubits = cirq.QubitOrder.as_qubit_order(qubit_order).order_for(
            circuit.all_qubits())
        num_qubits = len(qubits)
        qid_shape = cirq.qid_shape(qubits)
        qubit_map = {q: i for i, q in enumerate(qubits)}
        if len(circuit) == 0:
            yield MySimulatorStep(<default state>, {}, qubit_map)
        def on_stuck(bad_op):
            return TypeError(
                "Can't simulate unknown operations that don't specify a"
                "unitary or a decomposition. {!r}".format(bad_op))
        def keep(potential_op):
            return (cirq.has_unitary(potential_op) or
                    cirq.has_mixture(potential_op) or
                    cirq.is_measurement(potential_op) or
                    cirq.op_gate_isinstance(potential_op, cirq.ResetChannel))

        simulator_state = ...  # New code
        for moment in circuit:
            measurements = defaultdict(list)
            known_ops = cirq.decompose(moment, keep=keep,
                                       on_stuck_raise=on_stuck)
            for op in known_ops:
                self.simulate_op(op, simulator_state)  # New code
            yield MySimulatorStep(simulator_state, measurements, qubit_map)

    def simulate_op(op, state):
        # Actual simulation code here
        ...

class MySimulatorStep(cirq.StepResult):
    # Boilerplate
    def __init__(self, state, measurements, qubit_map):
        super().__init__(measurements)
        self.state = state
        self.qubit_map = qubit_map

    # Boilerplate
    def _simulator_state(self):
        return self.state

    def sample(self, qubits, repetitions=1):
        # Actual sampling code here
        return ...

Blergh.
Basically every single parameter except the circuit can be handled via glue code inside SimulatesIntermediateState or similar. Qubit order? Transpose results on their way out. Parameter resolver? Resolve the circuit before passing it along. Repetition? For loop.
The only thing the implementer should have to write is def _iter_wavefunctions(self, circuit) or def _final_wavefunction(self, circuit) or something like that.

Is anyone working on this? It appears simulator has changed a bit since the issue was reported. Are there still improvements that can be made here? I may be interested if there is reasonable ROI. Presumably this is big enough to require a design first?

Is anyone working on this? It appears simulator has changed a bit since the issue was reported. Are there still improvements that can be made here? I may be interested if there is reasonable ROI. Presumably this is big enough to require a design first?

@cduck @Strilanc I submitted a PR that is lowest-hanging fruit here. The iterator code and a function check_all_resolved was copied verbatim between the simulator subclasses. In the _run code, only the first two lines were identical, and seemed not worth pulling out.
I didn't see anything else that would push down cleanly. There might be some higher-level repetition that I'm overlooking though. If so, I'd like to do that too, though maybe a separate PR since it'd be working at a different level of abstraction. LMK what you think.

@cduck @Strilanc I submitted a PR that is lowest-hanging fruit here. The iterator code and a function check_all_resolved was copied verbatim between the simulator subclasses. In the _run code, only the first two lines were identical, and seemed not worth pulling out.
I didn't see anything else that would push down cleanly. There might be some higher-level repetition that I'm overlooking though. If so, I'd like to do that too, though maybe a separate PR since it'd be working at a different level of abstraction. LMK what you think.

PR is open for it, but I'm having second thoughts. I pushed _base_iterator down into the base class so that it could be shared. That reduces duplication, but the problem is we can't just get rid of _simulator_iterator because of backwards compatibility. So now there's both _simulator_iterator and _base_iterator, which may end up creating more confusion than it's worth.
What do you think of starting to move toward an approach that decouples the simulation execution from the simulation strategy, get away from the multiple inheritance approach? So what I'm picturing is a static class SimulationExecutor that has methods like run(circuit, simulation_strategy), and the various simulation strategies would implement an interface that the executor would use? This decoupling should allow the simulators to have the bare minimum logic that differentiates them. I'll have to dig more to get a more detailed design, but does the idea sound okay?
It would be a v2 simulation API. I don't think there's a good way to integrate it with v1, but they should be able to exist side by side. Or actually I could probably rebuild v1 on top of v2 if desired, but IDK if the ROI would be there for that. So I don't know, do we want to do that.

PR is open for it, but I'm having second thoughts. I pushed _base_iterator down into the base class so that it could be shared. That reduces duplication, but the problem is we can't just get rid of _simulator_iterator because of backwards compatibility. So now there's both _simulator_iterator and _base_iterator, which may end up creating more confusion than it's worth.
What do you think of starting to move toward an approach that decouples the simulation execution from the simulation strategy, get away from the multiple inheritance approach? So what I'm picturing is a static class SimulationExecutor that has methods like run(circuit, simulation_strategy), and the various simulation strategies would implement an interface that the executor would use? This decoupling should allow the simulators to have the bare minimum logic that differentiates them. I'll have to dig more to get a more detailed design, but does the idea sound okay?
It would be a v2 simulation API. I don't think there's a good way to integrate it with v1, but they should be able to exist side by side. Or actually I could probably rebuild v1 on top of v2 if desired, but IDK if the ROI would be there for that. So I don't know, do we want to do that.

Pushed PR. Open item remaining to remove/inline deprecated function after v0.11.
The _run boilerplate seems to no longer be boilerplate, as other simulators have implemented it differently. However we may still want to revisit this in a v2 api because the feeling is there is still "similar functionality" that could be extracted, but would be a bigger project.

Pushed PR. Open item remaining to remove/inline deprecated function after v0.11.
The _run boilerplate seems to no longer be boilerplate, as other simulators have implemented it differently. However we may still want to revisit this in a v2 api because the feeling is there is still "similar functionality" that could be extracted, but would be a bigger project.

Hi,
I'm not sure if it's relevant, but there may have been a race condition with #3630 which had just added a new simulator. Sorry, I didn't know that you were working on this and either way, I don't think anything is broken (or even that there's anything issue at all).
Tony

Hi,
I'm not sure if it's relevant, but there may have been a race condition with #3630 which had just added a new simulator. Sorry, I didn't know that you were working on this and either way, I don't think anything is broken (or even that there's anything issue at all).
Tony

@tonybruguier everything should still be backward compatible. Overriding _simulator_iterator still works, is just marked deprecated in favor of overriding _base_iterator.  (Everyone's _simulator_iterator code was identical so we pulled it into the base class.)
The only issue I found in any existing simulator was a single unit test that counted compiler warnings, which changed due to the new deprecation warning. All else should continue to work as it was.

@tonybruguier everything should still be backward compatible. Overriding _simulator_iterator still works, is just marked deprecated in favor of overriding _base_iterator.  (Everyone's _simulator_iterator code was identical so we pulled it into the base class.)
The only issue I found in any existing simulator was a single unit test that counted compiler warnings, which changed due to the new deprecation warning. All else should continue to work as it was.


Mercurial: use prompt exptension if available

Mercurial has special extention for dislpay status in prompt: PromptExtension. This theme could use it if available for performance reasons.

Oh, sorry, this is already used. But before call hg propmt, hg id is called, which is slow. Is it possible to aviod tha call?

I've been trying to work out what has been breaking my prompt (ridiculously slow for me) thanks for the heads up.
Any chance this might be done anytime soon?


**kwargs for QuickUMLS creation

I am unable to create a PR here so would like to propose that the following is added:
https://github.com/medspacy/medspacy/blob/master/medspacy/util.py#L27
def load(model="default", enable=None, disable=None, load_rules=True, quickumls_path=None, **kwargs):
https://github.com/medspacy/medspacy/blob/master/medspacy/util.py#L72
comment something like: **kwargs: QuickUMLS keyword arguments (see QuickUMLS in core.py in QuickUMLS repo)
https://github.com/medspacy/medspacy/blob/master/medspacy/_quickumls.py#L6
def create_quickumls(nlp, name="medspacy_quickumls", quickumls_path=None, **kwargs):
https://github.com/medspacy/medspacy/blob/master/medspacy/_quickumls.py#L26
quickumls_component = SpacyQuickUMLS(nlp, quickumls_path, **kwargs)
Would be helpful to have these so we can pass through overlapping_criteria, threshold, window, similarity_name.

@burgersmoke related to https://github.com/medspacy/medspacy/issues/107

I finally have a PR ready for this one.  I did not follow this recommendation exactly, but I think my approach is a bit simpler and easy to maintain given our vision for QuickUMLS with respect to medspacy.  Thank you for your patience @kfujita-cohere
A new medspacy release with this will be coming soon, but let me know if you'd like to test it earlier.

This has now been resolved in medspacy 1.0.0.  All QuickUMLS arguments should now be supported when using a config dictionary when creating the component with add_pipe().


TypeError: require(...).jsdom is not a function in jest-environment-jsdom

"jest": "^20.0.4",
"jsdom": "11.0.0",

Using with enzyme as part of jestSetup step using this code

Please post it on jest-environment-jsdom issue tracker.


Terraform Module Registry example links are 404'd

Scroll down, click the Example links. Voila, GitHub 404 is your reward. ;)
https://registry.terraform.io/modules/terraform-aws-modules/rds/aws/1.9.0 (The current version, where you are sent after a search on "rds")

Thanks for reporting, but the latest version is 1.15.0 and I can't see broken links there.
I will try to figure out if there is anything I can do to force refresh search index. It looks like a bug on their end.

registry search redirects to 1.9.0 version, not the last one


Deflake Core SameHandleManagerTest

In addition to deflaking core's SameHandleManagerTest, this uncovered and fixed a bug in CrdtSet.merge that didn't update values for items which had been changed.
Related Bugs:
http://b/156865977
http://b/157052996
http://b/157203248
http://b/157267026

/gcbrun


Fix credentials + fallback for legacy API

I created these changes in 2014 when I was trying to fix NuGetPackageExplorer to work with a local Active Directory install of ProGet.
The changes were both to be able to download packages from and push packages to the server using Windows Integrated Authentication, as supported by ProGet.
Please review and approve/discard as you see fit - hopefully we can address #16 and #4 with this.

:)  thanks!
Will try to release this week a new version.

@rikoe Hello thanks for this change but what about if im not in the domain is there a chance to popup a login dialog to enter the credentials just like visual studio does?

Well, you'd need to be clear about your use case. When would you use
NugetPackageExplorer and not be in the domain already?
My fix was simply for authenticating against the NuGet server with the same
credentials you are already logged in with. It's just a few lines of code
to enable capturing the user's current credentials.
What you're asking for sounds a lot more complex, effectively supporting
multiple modes of authentication. Also keep in mind that the Visual Studio
dialog you are referring to is actually quite a lot more complex than it
first appears. It is hosting a browser control that authenticates against a
hosted OAuth security provider as far as I know (if we are referring to the
same one).
If you really need what you are asking for I would suggest opening a
separate issue for it describing exactly what you are authenticating
against and how (maybe with screenshots).
We can then try and prioritise it, but if it's not a common use case you
may need to fork it and try yourself! :-)
On 22 Feb 2016 23:08, "Scharly Ochoa"<EMAIL_ADDRESS>wrote:

@rikoe https://github.com/rikoe Hello thanks for this change but what
about if im not in the domain is there a chance to popup a login dialog to
enter the credentials just like visual studio does?
—
Reply to this email directly or view it on GitHub
https://github.com/NuGetPackageExplorer/NuGetPackageExplorer/pull/49#issuecomment-187430529
.

@rikoe is this PR better than https://github.com/NuGetPackageExplorer/NuGetPackageExplorer/pull/48?

It is a superset of #48 - it includes the same change to PackageDownloader.cs, but adds default credentials in a bunch of other places.
The one additional thing it does, is that (at the time) ProGet used a legacy NuGet API for searching packages by id, which didn't work with NuGetPackageExplorer, so I added some code to fall back to the legacy API

Fixes https://github.com/NuGetPackageExplorer/NuGetPackageExplorer/issues/4

How would one authenticate with a VSO nuget feed? https://blogs.msdn.microsoft.com/visualstudioalm/2015/08/27/announcing-package-management-support-for-vsotfs/

Hi @WiteCastle , only Windows authentication (without login form) is currently supported.
https://github.com/NuGetPackageExplorer/NuGetPackageExplorer/issues/92


Automate CHANGELOG.md creation

Idea
It is possible to create a changelog for the release creation based on commit messages.
This changelog shall be used to be written into the CHANGELOG.md. Consider appending the complete Release note on the top of the CHANGELOG.md file. Write the file in a GitHub workflow BEFORE the release is created and check if the workflow can commit changes to the main branch at tag event.

resolved by #18


Refactor project

Hi @silentworks
This is a bit of an opinionated PR, so I understand if you are not willing to merge it. But I think it is quite an improvement w.r.t. to the current package.
Let me know!
What is the current behavior?
The current library has some issues and was not working for me in a couple of ways:

The package does not setup logging in all modules properly (i.e. compare client.py and push.py)
The auto_reconnect did not work, and after a few hours the connection would drop without error
There are multiple instances of default mutable arguments
There are broken method calls (PR203)
The docs folder is outdated by 2 years

Personally, I found the mix of async / sync not that intuitive. Other Supabase libraries seem to stick to async for callbacks too.
What is the new behavior?
I have tried to maintain the same interface, to induce as little breaking changes as possible.
I have a list of larger changes:

Use async / await throughout the package

Note: This does require async callbacks from the user, as opposed to the sync

Logging is more abundant and properly initiated
Properly handle websocket disruptions, including rejoining channels
Heartbeat is initiated on connection, rather on listen. This aligns with realtime-js

Note: A separate call to client.listen is no longer needed

Smaller additions:

More exceptions types to better distinguish exception events
Use dataclass annotations for simple classes
Stronger typing for presence

Note: This changes the callback signature for presence joining and leaving

More robust URL rewriting

Understandable! My primary purpose was to get the library working for my internal projects. I am closing the PR for now, as I can't be sure I have the time to create many smaller structured PRs

I'll be creating smaller PRs with these changes throughout the week, thanks @yorickvanzweeden for the amazing work.


[FEATURE REQ] Check if App Service exists globally

Is your feature request related to a problem? Please describe.
I'm trying to automate the app service deployment to Azure via the SDK and it's a pain to create an app service that already exists globally.
Describe the solution you'd like
A function in the SDK that checks if an app service exists globally.
Describe alternatives you've considered
I can check via Azure portal if the app service exists but I want to do things in an automated approach. I can curl the possible app service URL but a method built right into the SDK would be a better solution.

@naveedaz FYI

After some time exploring the Azure SDK, I've learned that the CheckNameAvailabilityAsync method under the WebSiteManagementClientExtensions class does check if the App service exists globally. Will  now be closing this request.


Rate limited on 3.5

Could you manage this more gracefully please? currently just errors out instead of managing rate.

See AutoGPT for retry implementation on rate-limiting.


make wait_readable and wait_writable public

These methods are useful for integrating 3rd party libraries that require you to wait for a readable or writable socket.
Example libssh2
How this is implemented in crystal: https://github.com/spider-gazelle/ssh2.cr/blob/a93eb957420b9e9f31bb8cd46e50ff862c5bc54b/src/session.cr#L39-L49

@asterite how should one integrate libssh2 to prevent it blocking the event loop?
Using those methods definitely works to achieve what is required for libssh2

How is it done in Go?

Actually, nevermind, I have no idea what I am talking about :blush:

haha yeah, looks like they have a native golang implementation..

Can we make them :nodoc:? It would allow to use them, but make no guarantee these methods will continue to exist.


refactor(net): unify closed incoming session handling

followup for https://github.com/paradigmxyz/reth/pull/595
unifies how closed incoming sessions are handled, including IP ban if closed due to fatal protocol error

Codecov Report

Merging #600 (f1528a2) into main (43008b7) will increase coverage by 0.08%.
The diff coverage is 79.24%.

@@            Coverage Diff             @@
##             main     #600      +/-   ##
==========================================
+ Coverage   71.98%   72.06%   +0.08%
==========================================
  Files         250      250
  Lines       25266    25336      +70
==========================================
+ Hits        18187    18259      +72
+ Misses       7079     7077       -2

Flag
Coverage Δ

unit-tests
72.06% <79.24%> (+0.08%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

crates/net/network/src/manager.rs
46.19% <0.00%> (-0.70%)
:arrow_down:

crates/net/network/src/state.rs
50.20% <0.00%> (-0.63%)
:arrow_down:

crates/net/network/src/swarm.rs
65.51% <25.00%> (-3.33%)
:arrow_down:

crates/net/common/src/ban_list.rs
87.75% <92.30%> (+16.17%)
:arrow_up:

crates/net/network/src/peers/manager.rs
80.84% <92.42%> (+1.43%)
:arrow_up:

crates/net/network/src/error.rs
77.19% <100.00%> (+6.98%)
:arrow_up:

crates/net/network/src/session/active.rs
82.75% <0.00%> (-0.21%)
:arrow_down:

... and 2 more

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


Support updating types based on mutations made to an object when passed to a function, out keyword

Search Terms
typeguard for mutating function arguments
Suggestion
As it stands there's really no way of updating types based on mutations made to an object when passed to a function. E.g.
function Special(obj) {
  obj['foo'] = () => {};
}

const bar = {};
Special(bar);
bar.foo(); // ts-error, js-ok

However you can achieve something similar to the intended effect by using typeguards. E.g.
function Special<T>(obj: T): obj is T & { foo(): void; } {
  obj['foo'] = () => {};
  return true;
}

const bar = {};
if (!Special(bar)) throw 'Will never happen';
bar.foo(); // ts-ok, js-ok

But as you can see this is a rather hacky approach and it isn't exactly self-documenting.
I suggest that either:
a)
The type system should be able to infer that the type of an object has been updated through an object reference. This is relevant since this is how js works either way, no matter if ts acknowledges it or not
b)
Add another ts-keyword that suggests that the function will modify the type of a parameter, maybe we could use the out keyword from C#?
function Special(out obj) {
  obj['foo'] = () => {};
}

const bar = {};
Special(out bar);
bar.foo(); // ts-ok, js-ok

In the function scope an out argument should be considered a const value but not an immutable value.
function Fail(out obj) {
  obj = {}; // ts-error assigning to const
}

let obj = {};
Fail(out obj);

The out keyword is NOT optional.
function Fail(out obj) {}

let obj = {};
Fail(obj); // ts-error overload error, no overload takes a single "none out" argument

Use Cases
The first use case I've ran into, is when you are developing or using a library that decorates an object as part of the import. Using the out keyword would  in these cases help making the code more self-documenting.
const foo = {};
require('someLibrary')(out foo);
foo.bar(); // ts-ok, js-ok

Checklist
My suggestion meets these guidelines:

[x] I don't think it would be breaking This wouldn't be a breaking change in existing TypeScript / JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. new expression-level syntax)

Duplicate of #22865.


How do I send data from my DB on request ?

Instead of just echo I want to send some real data to the user whoever using the app/chatbot, simple approach say, user query:
what type of cars you have ?
and that should replay all cars names that I have stored in my database

@sanjay555, you will have to expand on server.py to do natural language processing on strings coming in, parse them for the bot to understand the user request and perform a particular action based on the user input.


Makefile should build for the current target by default

When using the makefile, most commands should use the current target by default. If a developer wants to compile the python bindings, he should call make python for example, and it should work for the target he is on currently.
In order to get the current target, we could use TARGET=$(rustc -vV | sed -n 's|host: ||p'). (not sure whether that works on all platforms). There should be logic for copying the correct binaries to the correct locations. It could be .dylib, .so, .dll for example.
So

use current target by default
Make sure the commands work on all platforms (with the current target)
Have specialist commands to build for specific platforms and combinations of platforms

The command produces x86_64-apple-darwin on mac 👍


Remove non-existing metrics.

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.
@ldalves These values were never produced. Please review and merge.

FYI @gjoranv


Collapse ChangeNoteValidator into Section

The "Rails Way" is to use ActiveModel::Validations. Prior to this PR, there was a mixture of the latter and the custom validation logic in ChangeNoteValidator. This led to non-standard code and unnecessary levels of indirection, making the code hard to understand. This PR collapses the logic in ChangeNoteValidator into Section using the standard approach.
I've also done a little simplification of the logic and renaming of variables missed in the SpecialistDocument -> Section rename.
I did also consider further simplifying Section#change_note_required? by inlining #never_published? into it. However, it feels as if "never published"  is communicating something slightly different from "not published", even though the implementation appears to be the same. So I've decided to leave this for now.

@chrisroos: Thanks for reviewing.
Rebased against master and force-pushed in preparation for merging.


Prevent HSpec from messing with ImpSpec colors

Description
@neilmayhew This is the piece you are missing for the first point in your PR:

hspec forces a red colour on every line when it outputs the text of a failure message.

Checklist

[ ] Commit sequence broadly makes sense and commits have useful messages
[ ] New tests are added if needed and existing tests are updated
[ ] All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages.
New section is never added with the code changes. (See RELEASING.md)
[ ] When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
versioning process.
[ ] The version bounds in .cabal files for all affected packages are updated.
If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
[x] Code is formatted with fourmolu (use scripts/fourmolize.sh)
[x] Cabal files are formatted (use scripts/cabal-format.sh)
[x] hie.yaml has been updated (use scripts/gen-hie.sh)
[ ] Self-reviewed the diff

We also need to reverse the addition of --no-color in GHA. However, I can take that out of my PR since it's a separate commit.

@neilmayhew I've changed the original fixup that you've reviewed, because it was only applicable to ImpSpec, while all other usages of color still had problems.
I did get to the bottom of it and it turned out if we report any failure that depends on color output with ColorizedReason, then the color will be preserved and not botched by hspec.
Failure reporting for ImpSpec was quite wrong too, which is also fixed in this PR.


enable hardware acceleration of VideoCapture and VideoWriter

add missing native methods for hardware acceleration
add methods of video Capture/Writer for hardware acceleration
add some missing properties of video Capture/Writer
add video Capture/Writer parameter for hardware acceleration

Current HW acceleration types support matrix, for more details please check the link
please review!

Thank you!!


Fix reversed args in README example for invoke

Description
Fixes reversed args in example snippet in README for invoking remote commands.
This is my first contribution here and it seemed like it would be more helpful to open this PR than create an issue first; if the latter is still preferable I'm happy to do so. Let me know!

Nice catch, Dan!

Thanks for the quick turnaround @Miserlou 👍

Coverage decreased (-15.7%) to 57.984% when pulling 59b68e872fb746389250c50dad8a469c1f189c02 on daneah:fix-command into 32bdc1ab2dcf94ccb304adbe199fd3b4f91eed23 on Miserlou:master.


Feat/add config base

Please verify the following:

[ ] yarn ci:test jest tests pass with new tests, if relevant
[ ] README.md has been updated with your changes, if relevant

Describe your PR
Add config.base to centralize the optional configuration in the template, and developers won't have to go looking for it in the code.
This might be useful when we have more configurations?
Of course I have now added isRestored: NavigtaionIsRestored, catchErrors, and exitRoutes to config.base from the template

If you cherry pick this commit, you're good:
https://github.com/infinitered/ignite/commit/f9b3792825abc6a453469d5f68b5ebd7baa21b22
git cherry-pick f9b3792825abc6a453469d5f68b5ebd7baa21b22


Kill run if intermediate scoring times out

Closes #626.
Right now, the score hooks API request will fail with a 500 after TASK_OPERATION_TIMEOUT_MINUTES minutes. This PR changes the endpoint to kill the run instead.
The reasoning is, if there's an issue with the task or Vivaria that's preventing intermediate scoring from working on the task, we want to find out about it, and we want to treat the run as compromised (not include it in our analysis of run outcomes).
Testing: I added automated tests that taken together cover the whole new code path. I haven't manually tested with a run where intermediate scoring times out.

Yes! Hjalmar suggested thinking about this as a safeguard and I agree.
Yeah this var hasn't been set in production either. I set it today. Thanks for noticing that we should set it on the AI R&D nodes, too.


Correctness

Is your formula for the correlation matrix actually correct? What we want to compute is
C_{ab} = \left\langle O_a O_b \right\rangle - \left\langle O_a \right\rangle \left\langle O_b \right\rangle.

The first term is fine but for the second term you are using the following matrix inside of pe.Obs:
vevs = self.vevs.sort_values(by=["Bin_index", "Op_index"]).Vac_exp.values.reshape(self.num_bins, self.num_ops)
vev_matrix = vevs[:, :, np.newaxis] * vevs[:, np.newaxis, :] / self.NT**2
pe.Obs([vev_matrix[:, op_idx1, op_idx2]], ["glue_bins"])

which for my understanding means multiply the two spacetime averages of $O_{a/b}$ and only afterwards take an expectation value. Shouldn't it be
vevs = self.vevs.sort_values(by=["Bin_index", "Op_index"]).Vac_exp.values.reshape(self.num_bins, self.num_ops)
vev_matrix = pe.Obs(vevs[:, :, np.newaxis]) * pe.Obs(vevs[:, np.newaxis, :]) / self.NT**2

(modulo details of correctly calling pe.Obs)?

Just confirmed that this issue is real. Working on it.


Powerful names

Metatron
Elion
Shaddai
Adonai
El
YWHW (speaker and interpreter character concepts)
Sowell
Soros
Native Americans? Maybe sleeping bull
Plato
Socrates
Alexandria
Cleopatra
Also, why? To promote general education by creating an affordance or incentive to ask about the names
We can lean particularly to tech names as well for tech purposes then also philosophy and religious figures which will intersect philosophy and history at some pt

duplicate of #74


localhost:3000 connection refused

Get the connection refused error when using OAuth to login to drive in Alfred. Any fix?

Working on it now - will post when bug fixed.

the issue should be resolved now. please let me know if this solved the issue.


Check for connection reset correctly

During ninenines/gun#241 I got an intermittent fault, that after a lot of tests boiled down to this correction.
It was usually test 6.5.1 that failed, and connection reset by peer was involved.
The type net.OpError actually embeds the type os.SyscallError, which holds the ECONNRESET.
I also added a test to trigger the fault, and to verify the remedy. (verified using GithubActions both on ubuntu and windows)
The test uses real tcp sockets to get an exact behavior in this case, but using real sockets in tests might make people scream, so its optional and can be removed if wanted.
Thanks!

Hi!
Just tell me if there is a need of more information or if there is any ambiguity about this PR.
I will happily help. Thanks!

Handled via https://github.com/summerwind/h2spec/commit/9b531573778859d5c8f147f358ebf28073d98fb9


Switch from execSync to exec to avoid delayed output

I noticed this task was using execSync which buffers all output until the process is complete, so the user experience is not ideal. I switched over to exec to improve the experience.
Take the PR if you want it, otherwise close. I have no stake in it.

Can someone look at this or comment?

Thanks. The change looks fine. I'll merge it.


rug plot

Helps show where the data is, marginally.

You could do this with MakieLayout's hlines! or vlines!:
scene, layout = layoutscene(resolution = (600, 400), fontsize = 10)
ax = layout[1, 1] = LAxis(scene)
# hidedecorations!(ax)
xs = randn(200)
ys = randn(200)

scatter!(ax, xs, ys, markersize = 5)
hlines!(ax, ys, xmin = 0, xmax = 0.05)
vlines!(ax, xs, ymin = 0, ymax = 0.05)

scene


[2.6] Forwardport vSphere CSI

Forwardport of: https://github.com/rancher/rancher/issues/34630
Note: We are considering moving the CSI chart to live with the other RKE2 charts so this issue might need to be refactored once a decision has been made.

Test Environment

Rancher Version:v2.6-head (a2ae06c)
Installation option (Docker install/Helm Chart): Docker

Information about the Cluster

Kubernetes version: v1.20 and v1.21 was used.
Cluster Type(s) tested on (Local/Downstream): Downstream

Result of validation
CPI and CSI Chart installation was successful.
Pod was successfully created with volume attached to it.
Fresh install checks passed.

Closing in favor of https://github.com/rancher/rancher/issues/35378


Crashes

The game crashed whilst rendering overlay
Error: java.lang.NullPointerException: Rendering overlay
Exit Code: -1

If you use optifine, try to turn off render regions

i dont i use forge


UnsignedLong needs help!

Description
I want to augment UnsignedLong's capabilities with extension methods, but Java doesn't support these natively.  Investigate the use of Manifold (or some other method) to give us the desired functionality.
http://manifold.systems/docs.html#extension-method-basics
I would like to have an easy way to do a bounds check on UnsignedLongs automatically when we do an UnsignedLong.plus() or UnsignedLong.minus().
Acceptance Criteria
Add the following extension methods to UnsignedLong:

tryMinus()
tryPlus()
tryLongValue()
tryIntValue()
integrate into the rest of Artemis

Note: tryMinus() and tryPlus() methods should throw an error if an underflow or overflow is detected

Here is a proposal via Cava: https://github.com/ConsenSys/cava/pull/173

Here is the issue where this will be debated:
https://github.com/ethereum/eth2.0-specs/issues/626

I'm thinking that we might want to switch to Cava's uint64 type now that it is backed by long and has implemented some convenience methods for overflow detection

@jrhea, has this been completed or is it still an open issue?

@akhila-raju it is still an open issue.  I think we want to replace unsigned long with uint64 from cava. Antoine created an implementation that didn't rely on big integer

For the sake of easier code readability and maintainability, we have decided to switch to long, since mathematical functions (addition, subtraction, multiplication, division, modulo, amongst others) are already supported by Java for longs. Every time we use an UnsignedLong to index an array, it has to be cast to an integer. Java already has long to int cast support.
If we were to keep UnsignedLong, there would be many files we would have to maintain, including SSZ implementation for UnsignedLong, all supporting mathematical functions implemented for UnsignedLong, etc. It's unnecessary overhead since integer indexes are the major limiting factor of using UnsignedLong.
Thus, to keep it simpler, we have decided, going forward, to use Java's native long rather than UnsignedLong.


Births and deaths registration fees in Europe

Postage fees for Albania, Armenia, Azerbaijan, Belarus, Bosnia and Herzegovina,
Georgia, Liechtenstein, Macedonia, Moldova, Montenegro, Russia, Serbia, Turkey
and Ukraine are the same as "Rest of World", not "Europe".
Make it clear in the fees table for births and deaths registration document returns.
Sample affected paths:

/register-a-death/y/overseas/bangladesh/same_country
/register-a-birth/y/austria/mother_and_father/no/same_country

I'll create a new PR as I've just learned there are more changes to this table and I'll also need to create a separate branch for FC v.s. merging to master :|


[Request deployment] New Hub: kush.af.catalystproject.2i2c.cloud

The GitHub handle of the community representative
Faisal M. Fadlelmola<EMAIL_ADDRESS>@Fadlelmola
Technical support contacts listed

[ ] Technical contact present

Hub important dates
Next iteration
Hub Authentication Type
GitHub (e.g., @mygithubhandle)
First Hub Administrators
Faisal M. Fadlelmola<EMAIL_ADDRESS>@Fadlelmola
[GitHub Auth only] How would you like to manage your users?
Allowing members of specific GitHub team(s)
[GitHub Teams Auth only] Profile restriction based on team membership
https://github.com/orgs/CatalystProject-Hubs/teams/kush
Hub logo image URL
https://catalystproject.cloud/_images/catalyst-icon-dark.png
Hub logo website URL
https://catalystproject.cloud/
Hub user image GitHub repository
Standard Catalyst Profile
Hub user image tag and name
Standard Catalyst Profile
Extra features you would like to enable

[ ] Dedicated Kubernetes cluster
[ ] Scalable Dask Cluster

(Optional) Preferred cloud provider
None
(Optional) Preferred cloud region
No response
(Optional) Billing and Cloud account
None
Other relevant information to the features above
This is for the Kush Centre of Genomics and Biomedical Informatics as a part of the Catalyst Project on the catastproject-af cluster. Please use standard catalyst profile being developed in

https://github.com/2i2c-org/infrastructure/issues/3631

Tasks to deploy the hub

[x] 1. Deploy information filled in above
[x] 2. Engineer who will deploy the hub is assigned
[ ] 3. If using GitHub Orgs/Teams Auth, Engineer is given Owner rights to the org to set this up.
[x] 4. Initial Hub deployment PR
[ ] 5. Administrators able to log on -> Hub now in steady-state

@Fadlelmola Can you confirm that you can log in to the hub? It was deployed at https://kush.af.catalystproject.2i2c.cloud
Also, you can now add more users to the Github Team: https://github.com/orgs/CatalystProject-Hubs/teams/kush

Can we close this one, @jmunroe?

Not quite yet... waiting on confirmation.  Email from the hub champion

Currently, I have electricity outrage since yesterday, as soon as the power is back, I will check and send feedback.

I can see that @Fadlelmola has been able to successfully log in into the hub. I think it is safe to close this issue now.


Is build command removed? Getting unknown command "build"

Fresh installed on macOS using $ brew reinstall ko
$ ko version
0.9.3

But I got the following error:
$ ko build

Error: unknown command "build" for "ko"
Run 'ko --help' for usage.
2022/02/10 09:53:41 error during command execution:unknown command "build" for "ko"

Any ideas on this? I couldn't figure it out.
Command: https://github.com/google/ko/blob/main/pkg/commands/build.go
I can see an integration test that calls build: https://github.com/google/ko/blob/00d0a34583b01b44548f70cdc84348c137921ed5/integration_test.sh#L61
publish is working by the way.

ko build was introduced as an alias for ko publish since the last release (v0.9 right now). It's not released yet, but you can use it if you install from HEAD (like integration tests do).
When the next ko release happens (#584), ko build will be available, and ko publish will remain an alias for it, forever, for backward compatibility.


Can't configure the controls

When i open my game i can use the controller to move, break blocks, i can open my inventory an etc. But for some reason i am unable to look up or down using the right stick. Also i'm only using this mod

I have the same bug.

Closing issue because it's stale. Reopen if still an issue on recent versions.

Closing issue because it's stale. Reopen if still an issue on recent versions.


Add RTS and token masking to top-2 gating + configurable jitter epsilon

Add Random Token Selection to top-2 gating
Add token masking to top-2 gating
Add no drop token to top-2 gating
Add configurable jitter epsilon (both top-1 and top-2)

Hi @awan-10.
I am trying to add some missing features to top-2 gating which are currently only available for top-1 gating.
Please take a look and let me know what you think.

Can one of the admins verify this patch?

Hi @ykim362 - is this still an issue or a PR you'd like to see completed?  If so we can fix the conflicts and review, otherwise we would like to close and clean up some older PRs.

Hi @ykim362 - I'm going to close this PR for now.  If this is still something you'd like to merge, we'd be happy to review promptly next time, just re-open and we will take a look.  Thanks for contributing to DeepSpeed!


[main] Upgrade to latest dependencies

Cron. -knative-prow-robot
/cc knative-sandbox/channel-wg-leads
/assign knative-sandbox/channel-wg-leads
Produced via:
./hack/update-deps.sh --upgrade --release v0.22
./hack/update-codegen.sh

Details:
bumping knative.dev/eventing c42772d...4e1a66b:
  > 4e1a66b Update community support instructions with ux issue template info (# 5109)
bumping knative.dev/reconciler-test fe1effb...d0acc6d:
  > d0acc6d add id for correlation (# 148)

Rekt test failure,
/retest

Rekt test failure
/retest

Rekt test failure
/retest

/close
This is the reason https://github.com/knative-sandbox/reconciler-test/pull/148


chore(deps): upgrade configuration

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-configuration-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3043

Questions ?
Please refer to the Backport tool documentation


Bug: Throws exception in Android project with localTest and local build types

Build scan link

https://scans.gradle.com/s/iz5db3a77i22g
Plugin version

1.15.0
Gradle version

7.4.2
(Optional) Android Gradle Plugin (AGP) version

4.2.2
Describe the bug

When importing this plugin into an Android project with two custom buildTypes, localTest and local, doing anything Gradle-related like syncing the project in Android Studio or running ./gradlew tasks causes this error message to be reported.
A problem occurred configuring project ':app'.
> Failed to notify project evaluation listener.
   > com.android.build.gradle.internal.crash.ExternalApiUsageException: org.gradle.api.internal.tasks.DefaultTaskContainer$DuplicateTaskException: Cannot add task 'artifactsReportLocalTest' as a task with that name already exists.
   > KotlinJvmAndroidCompilation with name 'local' not found.

The associated exception stack trace can be found in the Gradle Build Scan link above.
To Reproduce
Steps to reproduce the behavior:

Open the latest Android Studio (Android Studio Dolphin | 2021.3.1 Patch 1, at time of writing).
Go to "File" > "New" > "New Project..."
Select the "Phone and Tablet" > "No Activity" template and click "OK".
Click "Finish", accepting the default project settings.
In the root build.gradle, add the following line:

plugins {
    // ...
    id "com.autonomousapps.dependency-analysis" version "1.15.0"
}

In app/build.gradle, add the following lines to the android > buildTypes section:

// ...

android {
    // ...

    buildTypes {
        // ...

        localTest {}

        local {}
    }

    // ...
}

// ...

Tap Ctrl+Ctrl and enter gradle tasks. Alternatively, run ./gradlew tasks from the terminal.

Expected behavior

The list of tasks for this project should appear.
Additional context

I was trying to apply this plugin to our proprietary Android app's Gradle build, where I first saw the error message and stack trace mentioned above. We have a number of Android build types, including local and localType, which would be impractical to remove or adjust.

Could you provide the reproducer? Either zip or git project would work. I'm not going to go through those manual steps. I know this plugin works with custom build types because lots of Android projects have custom build types (including mine) and the plugin works. So, something else is going on here.

Sure, no worries. You may find a reproducer at the following GitHub repo: https://github.com/jbduncan/dependency-analysis-android-gradle-plugin-bug-repro.

Ohh haha the issue is due to the names of your buildTypes. Because you have a buildType is named "localTest", the plugin tries to create a task with the slug LocalTest. However, you also have a buildType named "local", which means the unit test analysis for the "local unit test" source will have the slug LocalTest—identical to the other slug.
The simplest solution is to not use the suffix "test" in any of your build types. You could also rename the "local" buildType to something else.

Ahh, gotcha!
I'll discuss this with my team, as I'm not sure of the consequences of renaming these build types, or if we even need them. Regardless, we could always temporarily rename them whilst trying out this plugin, and we have a couple of other apps that don't have build types like these, so we'd still benefit from this plugin, I imagine.
Many thanks for looking into this, and for all your effort with this plugin and the other tools you maintain. I'm acutely aware how time-consuming open source work is, having contributed to open source on and off over the years. :)
I'll keep this issue open in case you ever find the time to fix it.


sporadic test failures with new watcher

some integ tests occasionally fails with "Provided message has already been received."

Basic L1<>L2 Communication
L2 => L1
{tag:other} should be able to perform a withdrawal from L2 -> L1:
Bridged tokens
{tag:other} should withdraw tokens from L2 to the transfer recipient:

hints: fast-relayer might compete with message-relayer

remove duplicated message relay per @souradeep-das https://github.com/bobanetwork/boba/pull/19/commits/75a7addf80b5f0db3e4c8e435840fcf5a186be44


Fix CC plugin state and final 8.0.2 release notes

Going to send this one to merge as it is docs only and very limited changes.

@bot-gradle test and merge

I've triggered a build for you.


File Not Found Error in Sample View

I'm facing a file not found error when trying to click into any of the sample view pages after creating a project locally.

I believe the file that it is trying to find is located in my directory at this location but whatever process is trying to find it can't.

This is an old issue and should now be resolved


⚠ SceneTime has degraded performance

In dfa20f6, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1780 ms

Resolved: SceneTime performance has improved in 3045115 after 9 minutes.


Large numbers of plotted cells will be slow

Annotorious v2.x will work smoothly up until about 800-1.500 shapes, depending on the user's computer. Shape complexity has an impact. If, for example, you have polygons with many corners, you may get significant speed gains by simplifying polygon geometry before loading into Annotorious. (E.g. using something like simplify.js)
For bigger datasets: I'm currently working on Annotorious v3, which uses WebGL rendering. First tests suggest that this will handle up to 100.000 shapes in the browser.


Duplicate data-v-* attribute with render function scopedSlot and scoped styles

Version
2.6.10
Reproduction link
https://github.com/raWINce/nuxt-duplicate-data-v-attribute
Steps to reproduce

yarn install
yarn dev or yarn start
open localhost:3000

What is expected?
Correct html without duplicate attributes that is valid according to https://validator.w3.org
What is actually happening?
The div rendered inside the slot has a dupplicate data-v-* attribute. The html provided by the nuxt server is thus no valid html according to https://validator.w3.org

This behaviour only occurs, when

the parent of the component with the render function has scoped styles
the render function directly returns the slot: return this.$scopedSlots.default()
the child component has scoped styles and a slot

In vue-template-compiler/build.js#L4661 it seems that there is no check for already existing scopeIds in the segments array.
This issue has been posted as a nuxt issue, originally - see also nuxt/nuxt.js#6401 (comment) and a vue-loader issue - see also vuejs/vue-loader#1590 (comment)

Same problem here.

It seems to get the parent data-v attribute. The child (.stat-subscribers) is loaded in a router-view.

The issue seems to appear when using a nested component:
<template>

        Categories
        <MenuList class="nested" :children="item.children"/>

</template>

To clarify:

the original issue is that of adding exactly the same data-v-* attribute multiple times.
The "same problem" mentioned by someone else is actually not the same problem, it's having two different data-v-* attributes at the same time.

The former is a bug, but doesn't create problems in 99.9% of cases as browsers simply don't care about these duplicate attributes. So it's not something super critical.
The latter is actually expected behavior - in order for a parent with scoped styles to be able to style its children, it passes down its own data-v-* prop.
But due to that, styles leak to the children and when both parent and child use the same class names, problems can occur.
Workarounds for the latter would be to :

A: ensure class names don't collide manually.
B: use CSS modules instead of scoped styles.

To clarify:

the original issue is that of adding exactly the same data-v-* attribute multiple times.
The "same problem" mentioned by someone else is actually not the same problem, it's having two different data-v-* attributes at the same time.

The former is a bug, but doesn't create problems in 99.9% of cases as browsers simply don't care about these duplicate attributes. So it's not something super critical.
The latter is actually expected behavior - in order for a parent with scoped styles to be able to style its children, it passes down its own data-v-* prop.
But due to that, styles leak to the children and when both parent and child use the same class names, problems can occur.
Workarounds for the latter would be to :

A: ensure class names don't collide manually.
B: use CSS modules instead of scoped styles.

Oh alright. Thanks for the explanation . Actually I was running into hydration issues with no error messages . So thought this could be it.

Oh alright. Thanks for the explanation . Actually I was running into hydration issues with no error messages . So thought this could be it.

Actually it does create problems, but not in browsers. Duplicated attributes cause html parse error in Vite SSR since there is a check for duplicates.
// Somewhere in Vite deps
function parseAttribute(context, nameSet) {
    // Name.
    const start = getCursor(context);
    const match = /^[^\t\r\n\f />][^\t\r\n\f />=]*/.exec(context.source);
    const name = match[0];
    if (nameSet.has(name)) {
        emitError(context, 2 /* DUPLICATE_ATTRIBUTE */);
    }
    nameSet.add(name);
    // ...
}


pages_url with -index suffix

@rultor release, tag is 0.0.34

@rultor release, tag is 0.0.34

@rultor release, tag is 0.0.34

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.0.34

@yegor256 Done! FYI, the full log is here (took me 10min)


Combine Alpine Security Issue Tracker into OSV

OSV currently includes Alpine's fixed vulnerabilities (from Alpine secdb) in its CVE records, but it's missing information about unfixed vulnerabilities from Alpine's security issue tracker. This means OSV can't report to users about unfixed vulnerabilities when scanning containers. This will be an issue, and similar discussions have come up with other container scanning tools.
Most Linux distros have official security advisories listing fixed patches (e.g., Alpine secdb), and they also maintain a security tracker that records potential vulnerabilities (usually identified with CVE-). OSV has already integrated security data from Debian and Ubuntu (Ubuntu-CVE-).
For other Linux distros, OSV only has data on fixed vulnerabilities. We should probably add more security tracker data into OSV, but there are some challenges. Combining all security tracker data will give us a very large number of records (e.g., Ubuntu provided 20k CVE entries), and not all vulnerabilities are actually important. We can use fields like "ecosystem_specific" to indicate urgency (e.g., "urgency": "unimportant" for Debian, "Ubuntu_priority": "negligible" for Ubuntu). But we need a better way to filter this data to reduce noise for OSV-scanner result and API queries.

This should probably be implemented after https://github.com/google/osv.dev/issues/2465


SignalR and culture

SignalR server and client should run consistently regardless of the computer's configured culture.
Ensure CultureInfo.InvariantCulture is used when converting between strings and values, and when comparing strings.
http://www.moserware.com/2008/02/does-your-code-pass-turkey-test.html

For Mvc's functional tests, we use a middleware that sets up the culture to a non-US one (https://github.com/aspnet/Mvc/blob/dev/test/Microsoft.AspNetCore.Mvc.FunctionalTests/Infrastructure/CultureReplacerMiddleware.cs) - think we pick en-GB. You could consider something along these lines to start with.

Roslyn started running their PR tests on a Spanish OS

That's correct. We are essentially running our debug unit test 32 bit run on Spanish OS.

I'm pretty sure they use the .NET CI infrastructure we're transitioning to

Yes if you're on the .NET CI infrastructure you can just use the image name Windows.10.Amd64.ClientRS3.ES.Open. Here is the PR where we merged the work back into our production branches.
https://github.com/dotnet/roslyn/pull/25874


Boolean config options consistency

Does it make sense to always favor *_enabled option names for boolean variables?
Having both _enabled and _disabled is a bit confusing IMO.
Was the original purpose to set the values correctly without having to specify the options in the config file?

Was the original purpose to set the values correctly without having to specify the options in the config file?

That is exactly right LOL. I have a config overhaul planned for this sprint, so hopefully will become much easier!
The other thing to note is that there is no way to set a 0 value for some options because 0 is interpreted as desiring default. 🤦


Can you add the --cors option?

I try to use the --cors argument that main.py offers, but it doesn't seem that spotify-connect-web (Pyinstaller Test Release 0.0.3) has implemented it...?
# ./spotify-connect-web -n MAGICMIRROR -o plughw:CARD=ALSA,DEV=1 --cors http://raspberrypi:8080

Loading Spotify library...
min_volume_range: 0.0
usage: spotify-connect-web [-h]
                           [--device DEVICE | --playback_device PLAYBACK_DEVICE]
                           [--mixer_device_index MIXER_DEVICE_INDEX]
                           [--mixer MIXER] [--dbrange DBRANGE] [--debug]
                           [--key KEY] [--username USERNAME]
                           [--password PASSWORD] [--name NAME]
                           [--bitrate {90,160,320}]
                           [--credentials CREDENTIALS]
spotify-connect-web: error: unrecognized arguments: --cors http://raspberrypi:8080

Anyway, thanks for a GREAT and easy way of making my RPi a Spotify Connect'ed device! :-)

Nope :-( That's SAD. Damn..

Even though it doesn't show it in --help, the option should still work (at least for 0.0.3)
Try doing grep -i cors main.py in the main directory

Well Fornoth - As you can see, the option isn't supported. But, maybe we have to use it, in another way.

@exetico can you double check that you're running the 0.0.3 release by checking if main.py has any CORS references?

I can see that "CORS" is in the top header as "import CORS".
I'm using the Alpha-build of 0.0.3 currently. So.. Maybe that why?
https://github.com/Fornoth/spotify-connect-web/releases/download/0.0.3-alpha/spotify-connect-web_0.0.3-alpha.tar.gz

@exetico can you try re-downloading the 0.0.3 release? I've tried it on two devices, and the --cors argument exists

I'm gonna close this for now, feel free to re-open if you're still having problems


bugfix: fix allSessions/findGlobalSessions may return null and cause npe

[ ] I have registered the PR changes.

Ⅰ. Describe what this PR did
allSessions/findGlobalSessions 都有可能返回null，不判断的话可能导致npe
现在发现两个方面有这个问题

批量处理session（retry）
console相关的查询

Ⅱ. Does this pull request fix one issue?

https://github.com/seata/seata/issues/4560
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #4561 (e50440d) into develop (8cefdbb) will increase coverage by 0.00%.
The diff coverage is 75.00%.

@@            Coverage Diff             @@
##             develop    #4561   +/-   ##
==========================================
  Coverage      49.46%   49.47%
- Complexity      4071     4073    +2
==========================================
  Files            732      732
  Lines          25507    25515    +8
  Branches        3148     3152    +4
==========================================
+ Hits           12617    12623    +6
  Misses         11546    11546
- Partials        1344     1346    +2

Impacted Files
Coverage Δ

...o/seata/server/coordinator/DefaultCoordinator.java
53.65% <50.00%> (-0.07%)
:arrow_down:

...r/console/impl/file/GlobalLockFileServiceImpl.java
95.12% <100.00%> (+0.25%)
:arrow_up:

...onsole/impl/file/GlobalSessionFileServiceImpl.java
84.21% <100.00%> (+1.85%)
:arrow_up:

...erver/storage/file/session/FileSessionManager.java
50.31% <0.00%> (-0.64%)
:arrow_down:

...very/registry/zk/ZookeeperRegisterServiceImpl.java
61.76% <0.00%> (+0.73%)
:arrow_up:


[$250] [Wave Collect][QBO] Refactor the error text style

From this convo in another App PR.
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01ab49e87b72a1e37d
Upwork Job ID:<PHONE_NUMBER>359643648
Last Price Increase: 2024-05-29
Automatic offers:

s77rt | Contributor | 102509287

Issue OwnerCurrent Issue Owner: @laurenreidexpensify

@shawnborton can you please clarify - are we expecting Error Text position like this one?

While we are at it, I wonder if we should take a look at the hint text too to make sure the hint text works the same way - same distance below the push row, and is included in the hoverable interacation.

@shawnborton hover:

Yeah for sure - i will also include hint issue to this PR fix

Okay cool, as it stands now, it seems like maybe there is too much padding below the error text? Notice how the bottom portion of the hover is larger than the top.

Okay cool, as it stands now, it seems like maybe there is too much padding below the error text? Notice how the bottom portion of the hover is larger than the top.

Yeah - this coming from standard menu item component. - should we also change paddings which we already have?

Yeah, I would expect that vertical padding to be equal. So if we're doing 12px on top, why not 12px on the bottom? Or maybe we just do 16px vertically so we split the difference?

Yeah, I would expect that vertical padding to be equal. So if we're doing 12px on top, why not 12px on the bottom? Or maybe we just do 16px vertically so we split the difference?

Good point - but i do not see any vertical logic to make a difference.
In any case - it should be 12px below - based on all other menu items. I will update that for sure! Thanks!

Just popping in to say I agree with everything going on in this convo.

@shawnborton this one with hint text below:

Nice, and can you show us that same scenario but with no error text?
Also, in the error case, is it possible to move the red dot closer to the right arrow? They feel a little far away right now, cc @Expensify/design for a gut check on that one. Perhaps we can try 8px and 12px gaps, respectively, for comparison?

@shawnborton here you are:

And closer red dot as well:

Yes please! Not sure how 18px ever got introduced as a line height, I don't think we should be using it anywhere?

Nice - sure will update that!

@s77rt please accept role in Upwork and will issue payment thanks

@laurenreidexpensify Accepted! Please note this is due $125 as there was a regression

Payment Summary:
C+ Review $125 @s77rt paid in upwork


Error about running the design flow of a buffer.

Excuse me, let me ask a question. As the pictures shown, this design realizes a buffer. Why the server reports error?

@yyh-sjtu sorry for the delay, a single buffer should not be a problem, but we seem to have some issues returning results reliably at the moment

I hope things became more stable and you were able to run your design. Please reopen or open a new issue if you are still encountering issues.


Investigate disabling wifi / bt power management

@MuratUrsavas could you comment on this on the ticket?

From the latest tests I've done about power saving, I guess it is off by default in newer drivers. But I'm not sure of course. Maybe the default Debian Radxa image had it disabled and driver update didn't change it.
What I know is, having power save enabled, the latency increases a lot. So it is best to keep it off.

@MuratUrsavas do you know the process for turning it off?

Checked on the image from PR https://github.com/balena-os/balena-rockpi/pull/56 and power saving is off by default:
root@ff37d9c:~# iw wlan0 get power_save
Power save: off

Checked the brcmfmac source code and it seems off by default: https://github.com/balena-os/cypress-backports/blob/v5.4.18-2021_0527/v5.4.18-backports/net/wireless/core.c#L1389
Anyway, will also disable from Kconfig just to be sure that future changes to core.c won't take us by surprise: https://github.com/balena-os/balena-rockpi/pull/58

Thanks @floion :-)
Let us know when there's an OS update available

This is now in OS release v2022.1.3 which is available in production


(WIP) feat(chore): zkSync node public release

What :computer:

Renames External Node to zkSync node
Adds doc changes of new features

Why :hand:

To improve clarity on what the node is (just a full node, no need to call it external)
Improve docs on the new features/configs/ways of running

@githubdoramon are you then adding the quickstart guide or is there still a need for me to do so?

@dutterbutter I left the PR for Ago and Alex O to work on and do any additional changes. If you also have the context, please feel free to work on it :)

@dutterbutter please add the guide!  https://github.com/matter-labs/zksync-era/blob/main/docs/guides/external-node/00_quick_start.md
Nothing to add apart from that, ready to push this to be public on the week of 13 May

@agolajko added here: https://github.com/matter-labs/zksync-web-era-docs/pull/1063

@agolajko you need to add Gbps to the spelling dictionary here: https://github.com/matter-labs/zksync-web-era-docs/blob/main/cspell-zksync.txt


Boot.Server.ts should handle failures from reconnect during initial connect

The client does not inspect the result of the reconnect task during initial connection:
https://github.com/aspnet/AspNetCore/blob/b0be780f1b98db4c7d468f5167b6a439abf2f1b5/src/Components/Browser.JS/src/Boot.Server.ts#L98
This may return false when pre-rendering when the server no longer has any state:
https://github.com/aspnet/AspNetCore/blob/b0be780f1b98db4c7d468f5167b6a439abf2f1b5/src/Components/Browser.JS/src/Boot.Server.ts#L82-L84
See here for an example:

I'm also running in to the same error with Ignitor + perf labs. Benchmarks starts off 256 clients (connections) by default, but the server maxes out at 100 retained connections. The initial ConnnectCircuit call for over half of these 256 gets rejected. Adding retries in ConnectCircuit works, but it's really iffy.

Closing this for now, as we are removing the stateful prerendering for 3.0.


And how to configure when go2rtc is running in Frigate, and Frigate is running in Docker on another machine

And how to configure when go2rtc is running in Frigate, and Frigate is running in Docker on another machine

The same essence applies:
https://github.com/felipecrs/hass-expose-camera-stream-source#when-go2rtc-is-running-via-docker

If you are using Tuya cameras, you can also use:
https://github.com/felipecrs/hass-expose-camera-stream-source#bonus-importing-tuya-cameras-to-go2rtc-without-home-assistant
Then you don't need Home Assistant.

The essence of this applies:
https://github.com/felipecrs/hass-expose-camera-stream-source#when-go2rtc-is-running-via-docker

I can't use this option because after adding an entry about go2rtc to docker-compose, I have 2 instances of go2rtc running. Let me remind you once again that my go2rtc was created automatically in frigate when I launched docker-compose for frigate. Here is my docker-compose for frigate:
version: "3.9"
services:
  frigate:
    container_name: frigate-pro
    privileged: true # this may not be necessary for all setups
    restart: unless-stopped
    image: ghcr.io/blakeblackshear/frigate:stable-tensorrt
    deploy:    # <------------- Add this section
      resources:
        reservations:
          devices:
            - driver: nvidia
              count: 1 # number of GPUs
              capabilities: [gpu]
    environment:
      - YOLO_MODELS=yolov7-320
      - USE_FP16=false
    shm_size: "600mb" # update for your cameras based on calculation above
    devices:
      - /dev/bus/usb:/dev/bus/usb  # Passes the USB Coral, needs to be modified for other versions
      - /dev/apex_0:/dev/apex_0    # Passes a PCIe Coral, follow driver instructions here https://coral.ai/docs/m2/get-started/#2a-on-linux
      - /dev/video11:/dev/video11  # For Raspberry Pi 4B
      - /dev/dri/renderD128:/dev/dri/renderD128 # For intel hwaccel, needs to be updated for your hardware
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /opt/frigate/config/config.yml:/config/config.yml
      - /media:/media/frigate
      - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
        target: /tmp/cache
        tmpfs:
          size:<PHONE_NUMBER>
    ports:
      - "1984:1984"
      - "9150:5000"
      - "8554:8554" # RTSP feeds
      - "8555:8555/tcp" # WebRTC over tcp
      - "8555:8555/udp" # WebRTC over udp

I do not understand how this should work, I remind you that frigate is running on another machine with a different address other than HA, thank you in advance for your help!

If you are using Tuya cameras, you can also use:
https://github.com/felipecrs/hass-expose-camera-stream-source#bonus-importing-tuya-cameras-to-go2rtc-without-home-assistant
Then you don't need Home Assistant.
This option is more suitable for me, but there are two things that stop me:
1 - I do not understand how to install this script, I am new to linux, and your instructions are for advanced users
2 - I do not know if my intercom can broadcast in RTSP? I have taya tokens!
I tried to install go2rtc as an add-on in home assistant and I managed to get an image using your "When go2rtc is installed as an add-on" method, but the performance on the machine with home assistant is very poor, and I have 12 cameras. Therefore, go2rtc runs on more powerful hardware.
I will be very grateful for your help!

You don't need the go2rtc add-on if you have it running on Frigate. I meant that the instructions for go2rtc running as docker apply in essence for when Frigate is running as docker.

1 - I do not understand how to install this script, I am new to linux, and your instructions are for advanced users

All you need to do is to download the script to the same directory where you have your frigate.yaml file. Then, in your go2rtc configuration you can call it with python3 /config/script_name.py.
PS: I don't think my instructions are for advanced users. If you know how to deploy Frigate with docker, then I think that's sufficient knowledge to understand my instructions.

2- I do not know if my intercom can broadcast in RTSP?

Neither do I, you have to test it by yourself. :)
And I suggest you test it before adding to the go2rtc configuration. Just call the script as the README suggests and see if it outputs a RTSP link.

You don't need the go2rtc add-on if you have it running on Frigate. I meant that the instructions for go2rtc running as docker apply in essence for when Frigate is running as docker.

1 - I do not understand how to install this script, I am new to linux, and your instructions are for advanced users

All you need to do is to download the script to the same directory where you have your frigate.yaml file. Then, in your go2rtc configuration you can call it with python3 /config/script_name.py.
PS: I don't think my instructions are for advanced users. If you know how to deploy Frigate with docker, then I think that's sufficient knowledge to understand my instructions.

2- I do not know if my intercom can broadcast in RTSP?

Neither do I, you have to test it by yourself. :)
And I suggest you test it before adding to the go2rtc configuration. Just call the script as the README suggests and see if it outputs a RTSP link.

I run the script, and this is what I get in response:
root@frigate:/opt/frigate/config# python3 get_tuya_stream_url.py bf460591ec2a13805cfhlb yrxhc5hx8ejdx4fn85uq a68ee182adb6490ab9402627cc54a3ab https://openapi.tuyaeu.com RTSP
Traceback (most recent call last):
File "/opt/frigate/config/get_tuya_stream_url.py", line 73, in
get_tuya_stream_url(device_id, client_id, client_secret, tuya_base_url, stream_type)
File "/opt/frigate/config/get_tuya_stream_url.py", line 57, in get_tuya_stream_url
raise Exception(f"Failed to get url: {response_json.get('msg', response_data)}")
Exception: Failed to get url: No permissions. This API is not subscribed.

Sorry. I deleted your comment because you shared credentials to your Tuya IOT account.
Looks like you need to Subscribe to the IoT Video Live Stream. Here's how it can be done: https://github.com/azerty9971/xtend_tuya/blob/main/docs/enable_webrtc.md.
But hey, you probably don't need to do that if you do it from Home Assistant. If you wait, I can write a guide for when go2rtc is running within Frigate within docker.

Sorry. I deleted your comment because you shared credentials to your Tuya IOT account.

Thanks, I didn't think about security!

Looks like you need to Subscribe to the IoT Video Live Stream. Here's how it can be done: https://github.com/azerty9971/xtend_tuya/blob/main/docs/enable_webrtc.md.

I did as you said and I did get the RTSP link, I'm glad, but I don't understand where I need to put the file: get_tuya_stream_url.py I copied it to opt/frigate/config but go2rtc does not see it.

But hey, you probably don't need to do that if you do it from Home Assistant. If you wait, I can write a guide for when go2rtc is running within Frigate within docker.

Of course I will wait for this, I really don't fully understand what folder should be in, I'm confused, I'll be very glad if you help. Thanks!!!!

It should be like:
go2rtc:
  streams:
    my_camera:
      - echo:python /config/get_tuya_stream_url.py <device id> <client id> <client secret> https://openapi.tuyaus.com RTSP

In your frigate.yaml.

- echo:python /config/get_tuya_stream_url.py

I've tried it many times :)

go2rtc:
  streams:
    intercom:
      - echo:python /config/get_tuya_stream_url.py ********** ********** ***************** https://openapi.tuyaeu.com RTSP
    outside_left:
      - and so on........

Oh, my bad, I meant python3 not python, please try again.
9e337ac

Without changes :)

Take the RTSP link you were able to generate and play it on VLC. Be quick, it expires in a few seconds if not opened.
If it doesn't work in VLC, it won't work in go2rtc either.

I received the broadcast, it's not in RTSP but in RD, thanks for this promotion, but it still doesn't work in go2rtc

I have a camera like that, which only works through HLS. Unfortunately I was never able to make it work on go2rtc.
This is the relevant issue in go2rtc side:

https://github.com/AlexxIT/go2rtc/issues/1152

I have a camera like that, which only works through HLS. Unfortunately I was never able to make it work on go2rtc.
This is the relevant issue in go2rtc side:

Tuya HLS stream can be played on VLC but not on go2rtc AlexxIT/go2rtc#1152

Then the only option left is to pull the stream from the Home assistant? And wait for instructions from you ;)

Not really. The stream from Home Assistant is always RTSP. If RTSP did not work for you, then the stream from Home Assistant won't work either.
But anyway, you can try playing the stream from Home Assistant in VLC.
Just call:
bash /config/custom_components/expose_camera_stream_source/get_stream.sh camera.my_camera

Inside the Terminal add-on.

Not really. The stream from Home Assistant is always RTSP. If RTSP did not work for you, then the stream from Home Assistant won't work either.

But when I
installed go2rtc as an add-on in HA for the test and wrote to gsrtc.yaml :
go2rtc:
streams:
my_camera:
- echo:bash /config/custom_components/expose_camera_stream_source/get_stream.sh camera.intercom
I got the broadcast, but I'm not satisfied with it because the performance is too low on the hardware on which the home assistant is installed, I plan to use face id and I need a broadcast on another go2rtc

Oh. Got it. Well, here are the instructions:
https://github.com/felipecrs/hass-expose-camera-stream-source/blob/new-guide/README.md#when-go2rtc-is-running-within-frigate-via-docker
#42

Immediately, the error of creating docker-compose:

Use:

HA_TOKEN=tokenhere

This happens because you are using a different syntax for the environment.
You can't mix the syntaxes.

- HA_TOKEN=tokenhere

Thank you, I am very grateful for your help, everything worked out!!! Please tell me it works over the Internet, but if there is a way to make it work locally?

Happy to help.
I believe the only way to make it work locally is by jailbreaking your camera to allow it to expose an RTSP stream itself.
Maybe this in go2rtc would also make it run better, I don't know:

https://github.com/AlexxIT/go2rtc/pull/1379


Want to Contribute to this amazing Project

Hi,
The Documentation of this project is very well maintained, thanks a lot. But I found some improvements as a beginner to this field. Can I make a pull request on this?
I have experience of making Pypi packages. Can I try to contribute to this project via making it as a Pypi package ? So that the installation will be much simpler.
Thank you

I am not maintaining any more from a year ago, and maybe I will archive this repository soon. But If you wanna add inference sources with pypi, I will check your PR.

I'm closing it now. If you wanna make a PR, I will check that request.

Hi ,
Ohk,Thank you for the reply and information.
On Mon, 4 Oct 2021 at 17:03, ILJI CHOI @.***> wrote:

I'm closing it now. If you wanna make a PR, I will check that request.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/AppleHolic/source_separation/issues/33#issuecomment-933395856,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APEMKZWNES3MXSK6TG7P47TUFGGIFANCNFSM5FHC3WBQ
.


API to declare snapshotting inside directory/archive/container

This is the testBinZip situation, where we'd need to specify that some JARs inside that archive constitute a runtime classpath that needs to be snapshot as such.

This is something we still want to do.


Auth UI incorrectly show AAD instead of new term Microsoft Entra ID

This React app front-end shows how I fixed this issue for the UI. https://github.com/Azure-Samples/azure-typescript-e2e-apps/pull/69
@adrianhall @BandaruDheeraj @craigshoemaker

This is actually correct, as the identity provider name is azureActiveDirectory, which means aad is the correct abbreviation. This issue can be closed or set on halt until the official json schema was updated.


Why aren't Swagger services added to DI container conditionally (only in development)?

When using the ASP.NET core Web API template to create an API application with OpenAPI support (Checked the Enable OpenAPI support). The Program.cs file is below:

As we can see, the UseSwagger() and UseSwaggerUI() middleware are activated only in development. But why AddEndpointsApiExplorer() and AddSwaggerGen() are not activated only in development as well.
I know we can add Swagger services to the DI container conditionally using the following code. But I hope this operation can be achieved by design, it will auto generate after creating the application using the template.
builder.Services.AddEndpointsApiExplorer();
if(builder.Environment.IsDevelopment())
{
    builder.Services.AddSwaggerGen();
}

Environment: VS 2022, Asp.Net 6.

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

ID: 14fce65f-1337-58cb-2193-8d8e0e62792d
Version Independent ID: 59222460-a971-e76e-4fe9-23d4d7d768ee
Content: Get started with Swashbuckle and ASP.NET Core
Content Source: aspnetcore/tutorials/getting-started-with-swashbuckle.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @zuckerthoben
Microsoft Alias: scaddie

Hi @Dillion132,
Thanks for providing the product feedback.  For this product change/feature you would like to file, please select to provide feedback on "This Product" at the bottom of the page.  Then you are filling an issue on the product at the product repository.  You can copy paste to a new issue there and consequently receive notification as it is reviewed.

Go here: Get started with Swashbuckle and ASP.NET Core
Select to provide feedback to "This Product" at the bottom of the page.