Accordion NVDA browse mode adjustment causes long announcements to be cut off in NVDA browse mode

What
The accordion section button has a CSS adjustment that potentially improves the NVDA browse mode announcements by making NVDA browse mode perceive the button content as one element and announcing it as such, instead of multiple ones that are announced separately. It was implemented after some discussion at the accessibility clinic - see commit message for details.
However, it seems that the CSS adjustment causes long announcements to be cut off in NVDA browse mode, for instance
clickable  heading    level 2  button  collapsed    Providing assisted digital support   , Helping people who don't have the skills or access to use a

(This is on the second accordion on https://govuk-frontend-pr-2257.herokuapp.com/full-page-examples/campaign-page).
The CSS adjustment incidentally has the favourable effect of limiting the width of the focus state so we'd have to handle the width of the focus state in a different manner if we removed this fix. I've prototyped that in JS and it seems to work although I need to do a bit more testing. Reverting the fix also seems to resolve this (rather minor) bug in Windows High Contrast Mode: https://github.com/alphagov/govuk-frontend/issues/2354
I think we'd just like to find out from the original contributor on whether they agree that we should revert the CSS adjustment or if there is something we're not aware of.
Why
We don't have evidence that the default NVDA reader mode behaviour that the CSS adjustment overrides is an issue as was discussed at the accessibility clinic. If we get evidence that there is an issue with it, we could investigate that. However, for now it might be safer to remove the CSS adjustment to makes sure long NVDA browse mode announcements aren't cut off.
Who needs to know about this
Developers
Done when

[ ] We've considered what impact removing the CSS adjustment might have by speaking to the GOV.UK Accessibility team
[ ] We've agreed next actions

(Draft)
Upon investigation of this issue there have been a few discoveries
NVDA has two types of modes, Browse Mode and Focus Mode.

Browse Mode (using arrow keys) allows "complex read-only documents such as web pages are browsed in NVDA using browse mode"

Focus mode is used when interacting with an element

The original intent of the NVDA investigation was to resolve a disjointed announcement of "Show this section" while in Browse Mode.
This disjointed issue on NVDA was highlighted at the Accessibility clinic yet noted as not a WCAG fail.  It was also noted as being unclear if this would be an issue to NVDA users or if they would expect this.  After investigation a technique was found that resolved this, and on balance, we decided to proceed.
"this section" was added as hidden text next to the new icon and the word "Show".
This was done to provide a balance between the desired Design while providing additional context for users with visual impairments. A user would hear "Show this section" giving additional context instead of just "Show" - Show what?

The issue raised above highlights a particular behaviour when the user is using NVDA Browse Mode and is navigating through the Accordion.  As they moves through the button  the text that is announced is:
[Insert to go into browse mode, press down key]
clickable  heading    level 2  button  collapsed    Providing assisted digital support , Helping people who don't have the skills or access to use a

[press down key again]
heading    level 2  button  collapsed    service. , Showthis section

The word service is not read out by NVDA Browse mode in this context and is missed off.
It was unclear why the sentence "Helping people who don't have the skills or access to use a service" was being cut off, on deeper investigation this is related to the user-defined setting while in Browse Mode.
The number of characters is restricted - in this case to 100.  After reading 100 characters the Content being read will stop and user can press the down arrow to read the next section.  In this context the total number of characters inside the entire button is being calculated and as a result, it stops - as expected.  Should a user increase this number to 200 the behaviour is not present.
"Maximum Number of Characters on One Line
This field sets the maximum length of a line in browse mode (in characters)."

In addition, to this should user press the "B" key (or Shift-B) for "button" NVDA will cycle through the buttons on the page much like headings or the H key.  Using the "B" will announce the full Content within the button as expected with no cut off to the word service
While in browse mode NVDA + Firefox indicates this mode with a red outline while Focus mode is shown with a blue outline (switching from Focus Mode to Browser mode is show with a dotted blue outline)

On balance we've decided to revert this.
Firstly, it's unclear why the word service continues not be announced by NVDA.  Additionally, Focus Mode seems more appropriate for this interaction, and based on NVDA documentation, would expect users to interact with the Accordion in this way.  Browse Mode seems to be more suitable for reading Content.  Should there be a long piece of content NVDA would appear to intentionally pause for user input rather than read the entire paragraph (based on user settings).  However at present this is unclear if users actually interact with the NVDA in this way on a day-to-day basis and the real-world impact to user from the original disjointed issue.
Another possible solution is to alter the Design to reflect the hidden text, so instead of just "Show" - "Show this section" is present removing the need for hidden text and the additional CSS technique.  Additionally this solution has the added benefit that what is visually seen matches up what is heard from a screen reader.
Should user testing, feedback or additional information change our understanding of this we can review


DGJ-1785 | always showing submission loading

Summary

To always show submission loading

Solution

I found that after fetching, isTaskLoading become true, and then will show 3-ball loader.
so we add one more condition !isCustomFormSubmissionLoading

Tested on TEST env, working fine now. Did not see 3-dots loader now.


Redirect to intented URL after registration

Hi there 👋
I'm not sure if this is done on purpose but the redirection post-registration differs from the redirection post-authentication in the following way:
redirect()->intended($this->redirectPath()); // Authentication
redirect($this->redirectPath()); // Registration

This issue has been mentioned a few years ago and a PR was welcomed but I couldn't find any PR related to this.
I apologise in advance if a written decision has been made about this and I wasn't able to find it.
Let me know if you need any more work from me.

I don't see a problem there really. It doesn't make make such to redirect to an intended path right after registration. They have never used the app before.


Adding deepnet cross-validations

When running the test, I'm getting an error when testing the deepnet script.
Failed to obtain a finished resource: {u'code': -1, u'call_stack': [[0, [60, 60], [5, 60]], [0, [496, 496], [4, 64]], [0, [500, 517], [2, 32]]], u'source_location': {u'origin': 0, u'lines': [60, 60], u'columns': [5, 60]}, u'elapsed_times': {u'in-progress': 77268, u'started': 127, u'queued': 50}, u'instruction': {u'source': {u'origin': 0, u'lines': [60, 60], u'columns': [5, 60]}, u'instruction': u'apply'}, u'elapsed': 77395, u'error': -8200, u'progress': 0.1, u'message': u'Problem while executing script: Error handling resource (Validation error)', u'cause': {u'code': -1206, u'http_status': 400, u'extra': {u'evaluations': u'Cross-validation is available to evaluations for models, ensembles, and logistic regression: 59e7af294006831a1800799c'}}}.
More specifically, I think this comes from the function create-k-models. While is seems to work fine for other resource types, using "type" as "deepnet" returns the error Error computing primitive operation 'create'. Expected arguments of types [[resource-type [resource-id map]] [resource-type resource-id [resource-id map]] [resource-type resource-id resource-id map]], but got ["deepnet" {"datasets" ["dataset/59e7a78b7e0a8d0cba000faa" "dataset/59e7a78c3645270f7400118...]. I'm not sure exactly why, but it seems we can't create a list of deepnets from a list of datasets as we can with other resources.

Yes, we need to wait for the apian version in next. They have extended the list of models to include deepnets.

Tests are finally passing, apain must be ready! Merging.


Deprecate browserify in favor of babel

Create a new JS flow that uses gulp-babel or something similar. Get off the weirdness of browserify and onto something less aged and more comfortable.

Helpful reading:

http://macr.ae/article/gulp-and-babel.html
https://github.com/babel/gulp-babel

Seems like browserify is sticking with this project until the entire thing is reborn in webpack.

Fixed in https://github.com/uncleSoWise/gulp-khup/pull/15.


Button that downloads user's collection

User Story :
As a User, I can click a button that will download the Board Game Geek user I specified's game collection as a csv.
Acceptance Criteria

A BoardGameGeek user's game collection can be downloaded as a csv through BGG Companion.

https://stackoverflow.com/questions/68392446/download-html-table-when-clicked-on-button

https://github.com/rusty1s/table2excel

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import


1.14 Enchantment compat

Add new 1.14 enchantments & test

Added with 3ba06c54654da7797f2c5a900d47d77ea5432cb4. Needs testing


fix: incorrect type in getMyDefaultAdministratorRights

It should be get... not set... in the other parameter.

Codecov Report
Patch and project coverage have no change.

Comparison is base (ee66178) 36.65% compared to head (2e5dfc4) 36.65%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #375   +/-   ##
=======================================
  Coverage   36.65%   36.65%
=======================================
  Files          18       18
  Lines        4602     4602
  Branches      166      166
=======================================
  Hits         1687     1687
  Misses       2913     2913
  Partials        2        2

Impacted Files
Coverage Δ

src/core/api.ts
4.91% <0.00%> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Issue Deploying TensorFlow on Heroku Server Using Flask Technology

I am experiencing issues deploying my Flask-based Python application to Heroku when using TensorFlow. Specifically, I encounter the following error during the deployment process:
ERROR: Could not find a version that satisfies the requirement tensorflow-intel==2.17.0 (from versions: 0.0.1) ERROR: No matching distribution found for tensorflow-intel==2.17.0
The application is being deployed on the Heroku-22 stack, and I have specified Python 3.10.11 in my runtime.txt. The issue seems to be related to the compatibility of tensorflow-intel==2.17.0 with the environment Heroku provides.
Here are the steps I followed:
I generated a requirements.txt file using pip freeze.
Attempted to push the application to Heroku.
The deployment was rejected due to the inability to find a compatible version of tensorflow-intel.
I have tried removing tensorflow-intel and replacing it with the standard TensorFlow package (e.g., tensorflow==2.10.0), but I still encounter difficulties ensuring that the correct dependencies are installed in the Heroku environment.
Additional Information:
The app is built using Flask and involves machine learning models that require TensorFlow.
The error occurs during the dependency installation step on Heroku.
The full traceback and error logs can be provided upon request.
Is there a recommended approach to resolve this issue, or is there a specific TensorFlow version that is known to work well with the Heroku environment?
Thank you for your assistance.

Unfortunately I cannot help with this. You may need to discuss with Heroku support.


check not working

"Check" option is not working and causing error to the rest of the options.

Works for me. Make sure you're on the latest version of this task and Sass.

This is also not a good issue. Please make an effort the next time.


subscribing topic(e.g imu data) makes web browser slower

first of all, @tasada038  thanks you for sharing it.
I'm doing ros2 web dash board using react with roslibjs.
Everything worked fine, but I'm having a problem subscribing to ros topics.
For example, when I try to subscribe to the ImuData topic, the web browser outputs it through react's state quickly and
without any problem at first. However, as time goes by, it becomes slower and slower to subscribe through rosbridge_server and the
output to the screen is also slower. I checked it through the performance check of the web browser, and
it seems to be the problem of calling the callback function frequently. How should I solve this problem?

I solved problem. Change throttle_rate for topic.


Introduction of error codes

Currently, functions that return error codes have a return value of uint8_t. Depending on the function, that could imply different things, for example the number of read bytes in rom_load. To avoid that confusion, I suggest using something like this:
typedef enum error_code {
    ERR_OK,
    ERR_FAIL,
    ERR_TO,
    ...
} error_code;

This would make interpretation of return values much easier.
TODO for places that need error codes:

[ ] rom_load
[ ] mem_init
[ ] rom_setup (maybe just remove return 0? and make void instead)
[ ] lcd_load (same as rom_setup)

Note the edit of a todo list for places that need review


[Bug] space push return wrong exit code when has error

space push has exit status with 6, but build.sh shell receive 0 exit code. It's a problem when we make space push automatically.

@brkp could we investigate?


Is this now legacy in light of Meteor 1.3?

Yes, it aimed for Meteor 1.2
I have no time to test it with new meteor 1.3
So if you want to connect redux with meteor 1.3 maybe you need to check something else.
Sorry

I created a package that allows you to use React and Redux with Meteor 1.4 in a clean way.
Thanks to two Redux middlewares, you can subscribe with Redux actions and sync your Redux store with the data from Mongo or from any reactive data source.
The package: https://github.com/samybob1/meteor-redux-middlewares/
The live demo: https://meteor-redux-middlewares-demo.herokuapp.com/
The demo sources on GitHub: https://github.com/samybob1/meteor-redux-middlewares-demo/


Parameters to modulate granularity

The biolink model contains a tree of predicates under the related_to slot.  Each can have mappings to different curie-based vocabulary terms.  So for example, there might be a chunk that looks like:
-predicate 1
  mapping: m1
     - predicate 2
        mapping: m2
        - predicate 3
           mapping: m3

Currently, edge normalization takes a curie.  The first thing it does is that it looks for an exact mapping.  So if the input curie is m2, it will return predicate 2.  If the input curie is m1 it will return predicate m1.  So the first thing it does is attempt to match the granularity of the predicate as closely as it can.
If there is not a match however, the norm will attempt to find the most granular match that it can.  It can currently only do this for RO terms.  So let's say that in RO there is a grouping of terms like
  RO1
   - RO2
      - RO3

Let's say that you're passing RO3 into edge norm and it is not an exact match.  Then edgenorm will go up the RO hierarchy and see if RO2 is a match to something in a biolink mapping.  If it is not, then it will go to RO1 and see if that is an exact match.  If it is a match then it returns that term.   Sometimes the matching RO may be mapped to a leaf node (say RO2 == m3 in which predicate 3 is returned) and sometimes not (maybe RO2 maps to m1 and predicate 1 is returned).
So the current approach is to find the most granular term that can be reasonably mapped to the input curie.  If the user wants to create a less granular term then we force them to interrogate the biolink model themselves.
But there's no reason we can't do that as well.   So edgenorm could take a set of predicates as input that represent that user's preferred level of aggregation for whatever task they are engaged in.    So maybe they pass in [..., predicate 2, ...].
In that case, if their input curie gets mapped to either predicate 2 or predicate 3, predicate 2 will be returned.  If it maps to predicate 1, it cannot necessarily be pushed down to 2, so predicate 1 will be returned.
In other words, this approach can only make the output less granular, not more granular than the current approach.  The only way to do that is add more granular predicates to the model, either individually or in bulk (i.e. all RO terms are now in the model)
One add-on to this would be some prebuilt profiles ['pharmacology', 'genetics','robokop', 'rtx','classic'] or whatever that would be some conception of a particular set of tradeoffs. (I want the most granular parts of chemistry predicates, but I don't care about a bunch of fine grained anatomical predicates).
Thoughts @cmungall @cbizon @RichardBruskiewich @mbrush @andrewsu @saramsey @TriageDr @deepakunni3 ?

In other words, this approach can only make the output less granular, not more granular than the current approach. The only way to do that is add more granular predicates to the model, either individually or in bulk (i.e. all RO terms are now in the model)

So that is true if BioLink Model specifies both a vocabulary and a specific "allowed subset" of that vocabulary (the R01, 'R02, and R03` in your example above).  But what if we only asked BioLink Model to specify allowed vocabularies?  Then wouldn't that allow users the full flexibility to specify their granularity of interest as a parameter to edgenorm, without being constrained by any centralized decisions?  (I suppose this is functionally equivalent to @cbizon's suggestion of "add items in bulk, (i.e. all RO terms are now in the model)".)
(Note also that I realize BioLink Model has applications outside of Translator, so if it's impractical to make such a fundamental change like this to BioLink Model, perhaps that argues for something similar-but-different...)


PLASE store the settings into app path on portable version

if i lost my settings when moving to another pc or just put it into my usb stick, it's not portable at all!

now it stores into %AppData%\Captura.

For reference: #376
Ideally, fully portable tools write to the local app folder (usually to a subfolder like \data or similar) and nowhere else.

As you may see from #376, starting from the next release, Settings will be stored in the local app folder by default for portable builds.
Also, FFmpeg will be downloaded into the app folder too.

downloaded the portable version, read all the bug reports, created a "Settings" folder where captura.exe resides, still settings files are created here:
C:\Users%username%\AppData\Roaming\Captura
How to make this software truly portable by writing nothing outside the "Captura-Portable" folder?


Implementation of Stopgrad

May I a ask you a question, how did you implment stop grad? I viewed the code, but I didn't find it. Thank you!

def D(p, z, version='simplified'): # negative cosine similarity
    if version == 'original':
        z = z.detach() # stop gradient
        p = F.normalize(p, dim=1) # l2-normalize
        z = F.normalize(z, dim=1) # l2-normalize
        return -(p*z).sum(dim=1).mean()

Stop grad is implemented using the detach operation

OHHHH, I see, Thank you very much!


Error 400 Bad Request

Hello, congratulations on your project, really good!
I have a problem, when i search a Flight, the search fail and i get this error:
aiohttp.client_exceptions.ClientResponseError: 400, message='Bad Request', url=URL('https://api.tequila.kiwi.com/v2/flights_multi').
I tried to make the request via curl and the response is:
{"status": "Bad Request", "error": "unknown partner provided - if you would like to cooperate with Kiwi.com, please register at tequila.kiwi.com"}.
Do you know how i can fix it?
Thank You

Hi and Thank you!
with your first error, this is a bug in the code when searching for a multi-city flight search. you can only search/call api when you have more than two flight requests. I have pushed a new pull request now and fixed this bug.
The second error you getting via curl is because you may have not added your api key in your header.

Thank you for the reply!


Catalan translation

{
  "Azimuth": "Azimut",
  "Dawn": "Alba",
  "Dusk": "Capvespre",
  "Elevation": "Elevació",
  "Noon": "Migdia solar",
  "Sunrise": "Sortida del sol",
  "Sunset": "Posta del sol",
  "errors": {
    "SunIntegrationNotFound": "No s'ha trobat la integració Sun"
  }
}

language code => ca
For doubts check https://ca.wiktionary.org/wiki/capvespre

Gracies! There was already a PR that I just merged, my Catalan is very limited so feel free to take a look to it just in case! https://github.com/AitorDB/home-assistant-sun-card/pull/88

Reviewed and new pull request: https://github.com/AitorDB/home-assistant-sun-card/pull/92

Thanks! I merged it in develop, I'll close the issue, feel free to reopen if needed


Archive DeviantArt

Profile: https://www.deviantart.com/anticide

I think I archived everything:

88 featured pictures (+ metainfo + comments)
5 favorites (+ metainfo + comments)
27 scraps (+ mtainfo + comments)


Cannot match all projects or contexts using + or @

Bug Report
App Version: 2.0.3
Platform: macOS
Installation Method: Direct Download
Bug Description:
Using advanced search, I cannot filter my todo for + or @ (which is supposed to match any todo with a project or context). It is possible to match other projects or context using +test or @test. Specifically I would like to filter for any todos without a project (i.e. "!+" or "not +") or without a context (i.e. "!@" or "not @")
Steps to Reproduce:

Enter, e.g., "+", "!+", "not +", "@", "!@" or "not @" without quotations marks in the search field.

Expected Behavior:
To find todos that don't have any project or that don't have any context.
Actual Behavior:
When using NOT operators, no todos are displayed. Otherwise, all todos are displayed.
Additional Information:
The same bug is present in 2.0.2 installed through homebrew.

I also tested this on Linux, and it seems to be an issue there as well.

@jloow can you please share an example todo list, the exact search string you're applying and the expected result?

Sure!
Example todo.txt:
2023-12-13 Test 1 +project_a
2023-12-13 Test 2 +project_b
2023-12-14 Test 3 @context_a
2023-12-14 Test 4 @context_b
2023-12-15 Test 5 +project_a @context_a
2023-12-15 Test 6

Search string: +
Expectation:
2023-12-13 Test 1 +project_a
2023-12-13 Test 2 +project_b
2023-12-15 Test 5 +project_a @context_a

Result:
2023-12-13 Test 1 +project_a
2023-12-13 Test 2 +project_b
2023-12-14 Test 3 @context_a
2023-12-14 Test 4 @context_b
2023-12-15 Test 5 +project_a @context_a
2023-12-15 Test 6

Search string: @
Expectation:
2023-12-14 Test 3 @context_a
2023-12-14 Test 4 @context_b
2023-12-15 Test 5 +project_a @context_a

Result:
2023-12-13 Test 1 +project_a
2023-12-13 Test 2 +project_b
2023-12-14 Test 3 @context_a
2023-12-14 Test 4 @context_b
2023-12-15 Test 5 +project_a @context_a
2023-12-15 Test 6

Search string: !+ or not +
Expectation:
2023-12-14 Test 3 @context_a
2023-12-14 Test 4 @context_b
2023-12-15 Test 6

Results: None.

Search string: !@ or not @
Expectation:
2023-12-13 Test 1 +project_a
2023-12-13 Test 2 +project_b
2023-12-15 Test 6

Result: None.

@jloow this does not solve the issue at hand – which I have to admin, I have not looked into yet – but since you are using the advanced search, you might be interested in a proof of concept, that has been implemented based off this feature request: https://github.com/ransome1/sleek/issues/179
Feel free to test it out and share your feedback.

@zerodat are you around these days? @jloow report is valid. The Wiki says @ or + should narrow down the list to contexts or projects.
But doing so has no effect.
I also looked into the implementation but could not figure out exactly how it works. The easiest would probably be, if you could take a look at it.
At some point, we should add some test cases, since this is easy to test.

@ransome1, I'm still out here. :smile: I'll try to take a look at this issue.

@ransome1 still taking a preliminary look and I will be busy for the next 8 or 10 hours, but later I will look deeper.  The code for the query engine seems basically the same as it was back in the 1.2.9 version.  I confirmed that it works properly in that version.  What should be happening is that in the case of a query like "@" or "+" it will check the state of todoObject.contexts (line 127 of FilterQuery.js) or  todoObject.projects (line 113).  That all looks like it ought to work unless the todoObject is much different now in version 2 of sleek.  I'll try to do some debugging later to see where it is going wrong.

@ransome1, I confirmed that this worked in 1.2.9 and no longer works in 2.0.6.
The problem seems to be that I tested for the list of projects or contexts to be empty by just testing todoObject.contexts (or projects) as a boolean value.  That works if the contexts is nil or undefined when there are none.  However, in Javascript an empty list tests as "true" (which is the opposite of the behavior in Python, my usual language).
It seems like the 2.0.6 version is setting contexts or projects to an empty list rather than undefined in the case where there are no contexts or projects.  Maybe that's a change in behavior of the upstream todo parser.
In any case, we need to change the code in FilterQuery.js to test the length of the list explicitly.  I'm submitting a pull request that fixes the issue.

@jloow I can confirm that @zerodat PR fixed this. I will include it into the next release.

Great! I've been a bit busy but I'll be sure to check out the next release.

@jloow @zerodat this has been released with 2.0.7: https://github.com/ransome1/sleek/releases/tag/v2.0.7

I've done some quick testing and this seems to have been fixed. The other updates work really well as well.
How does this work - do I close the issue?

How does this work - do I close the issue?

Yes please :)


add explanations

add some kind of header/footer in the page to explain the context and the purpose of this page:

the inspiration of th Library of Babel
the link to the github
maybe some references to hacktoberfest
any relevant thing

assign to me

Here are some insights. First, the plot from "The Library of Babel" taken from wikipedia:

[The] narrator describes how his universe consists of an enormous expanse of adjacent hexagonal rooms. In each room, [...] walls of bookshelves. Though the order and content of the books are random and apparently completely meaningless, the inhabitants believe that the books contain every possible ordering of just 25 basic characters (22 letters, the period, the comma, and space). Though the vast majority of the books in this universe are pure gibberish, the library also must contain [...] all useful information, including predictions of the future, biographies of any person, and translations of every book in all languages.

So the Library of Twitter is designed after this short story. It proposes a random tweet generator, with the hope that someday a useful tweet will be generated... and shared with Humanity


Event-sourced processors

See event-sourced processors section in documentation.

When does this feature is planned to be released roughly? Is there some usable code already available in a branch?

@Tvaroh I just commited an example using Cassandra as query database. This will be in master next week (and available as 0.5-SNAPSHOT in the our repo). An 0.5 release is planned for beginning of next year.

@krasserm awesome, thank you! Does it make sense to just use the Writer in your example to update external database, e.g. build some graph, but read it directly using specific API? I mean, read that can only return value of one type cannot express all the cases. Or am I misunderstanding the Writer.read method purpose?

Writer.read is only to initialize the writer (for details, see API docs of EventsourcedWriter). Of course, all other queries should use the DB directly.

@Tvaroh Event-sourced writers are now in master (see documentation for details).

@krasserm awesome, will try them out in a near future. Thanks for this awesome work.
Sorry for the unrelated to this discussion question, but what monitoring solution would work better with eventuate?

Thanks for this awesome work.

Thank you for your interest.

what monitoring solution would work better with eventuate

We are currently evaluating that. Follow #110 for updates.

Great, thank you.


Support "Outline view" for Prisma Schema

https://code.visualstudio.com/docs/getstarted/userinterface#_outline-view

Could list the top level blocks like generator, datasource, model and so on with their names.
Possibly implementable via this: https://stackoverflow.com/a/59132169

Duplicate of #751


Create Translate-XliffTranslations.ps1

Added Translate-XliffTranslations.ps1 file to generate missing translations using Azure Cognitive Services.

Thanks again for your PR. I will try to review it soon!

I would like to merge this into the Set-XliffTranslations function. Idea is to have a different required parameter set when using the Azure Cognitive Services rather than a given file.

As said in the previous comment. If/when this is to be integrated, I would like to merge it into the Set-XliffTranslations command.
Thank you very much for your PR again though! 😊💪


How to use with SSR

I'm trying to sketch a site on quasar with ssr. In dev mode everything is fine, but as soon as I build a bundle and start the server all images and their variations that I declared via import are automatically loaded.
I don't even know how to explain the problem properly.

Here's what I found out.
if I specify 1 format (and even multiple sizes) everything works as it should. As soon as I start listing several, it simply loads a bunch of sizes automatically on the client, even if I didn't call anything on the page.
That's how it works:
src/assets/img/background.jpg?aspect=75:14&w=600;1200&format=avif&as=metadata
It doesn't work like that anymore:
src/assets/img/background.jpg?aspect=75:14&w=600;1200&format=avif;jpg&as=metadata


dma: Clean up _dma_mark_dirty

Low priority - just the suggestion I had here: https://github.com/nutanix/libvfio-user/pull/677#issuecomment-1140871862

@raphael-nutanix as I mentioned, this implementation won't work as is, you should be able to reproduce with "make pytest"

Haven't debugged the timeout. I'm seeing it on my local with the prior commit checked out so not sure it's me.

timeout isn't you, we have a long-standing race in client/server code.

Is this PR still relevant?

It's as relevant as it ever was. I still think it's a nice cleanup and possibly comes with a perf boost but I'll leave it to you guys to decide.

Closing this as there's nothing particularly wrong with the existing code, that we're aware of.


potentially customize sbt-git versioning

(Documenting some of my conversations with @outkaj for broader discussion and async. Note this is a discussion related to the upcoming changes switching to sbt-git versioning, not what is currently in master.)
Currently we have sbt-git utilizing it's default versioning schematic, which is almost identical to what git describe does.
In this schematic, if the last release was tagged v1.2.3, you may notice your local version is something like 1.2.3-7-a1b2c3d. This means you are 7 commits past release 1.2.3, and the latest commit was SHA a1b2c3d.
There are two changes we may want to discuss making to this behavior.
Making the versions more SemVer compliant
There is an official specification for allowing pre-release versions in SemVer, and this differs from it a little. Basically it's this:

Major.Minor.Patch-pre(.pre)*+metadata
Primary section: 3 dot separated fields, numeric major, minor, patch numbers (MUST exist, and MUST be numeric). This is the "public API" of SemVer.
Optional pre-release section: Following a - separator, any number of dot separated fields. What can go in them is more relaxed, alphanumerics are supported, thus you'll often see things like -rc.3 or -1 or alpha.123. While this portion is less standardized, generally people try to keep them as something that can be ordered.
Build metadata: Following a +, anything goes here that should not affect version ordering.

(For more formal spec with more detail see https://semver.org)
Version ordering: The most notable change is the that in SemVer, 1.2.3-7 would indicate a prerelease of 1.2.3, e.g. something that comes before it.
This is very common with pre-releases in SemVer, and is widely adopted in the wild. (This is what we do with NPM in openlaw-client, as it's the default.)
Metadata: In SemVer, the separator before build metadata field should be +. I don't see this as often in the wild, but it's in the specification. I consider this to be less of an issue but it's there.
Combing the above, the simplest set of changes would mean 1.2.3-7-a1b2c3d would become 1.2.4-7+a1b2c3d.
Neither would affect public releases at all unless we wanted to start pushing these versions to GitHubReleases+BinTray. This is more for our local development currently? Unknown to me is how SBT considers version ordering and how this might affect it.
We could also use a different schematic for pre-release versions if we ever want to actually "release" them, and not care so much about what sbt-git shows locally when doing development. Combining this choice with the SNAPSHOT option below could help enforce that better.
Adding in SNAPSHOT for more cases
Currently sbt-git only appends SNAPSHOT if your local worktree is dirty (e.g. non-commited changes). We may wish to make it so anything not explicitly on a release tag is considered a SNAPSHOT -- and thus can't accidentally be released to BinTray.
(If we did that, but still wanted to release a "pre-release" version at some point, we could just do a semver prerelease git tag within our normal release process and it would work.)
Implementation
sbt-git gives us the flexibility to totally override the versioning schematic as we see fit. So anything we want should be achieveable. An example from someone's blog post where they were doing something fairly similar (I think? I still don't grok sbt-git configuration intuitively. But it still shows it's easy to get under the hood):
val VersionRegex = "v([0-9]+.[0-9]+.[0-9]+)-?(.*)?".r
git.gitTagToVersionNumber := {
  case VersionRegex(v,"") => Some(v)
  case VersionRegex(v,"SNAPSHOT") => Some(s"$v-SNAPSHOT")
  case VersionRegex(v,s) => Some(s"$v-$s-SNAPSHOT")
  case _ => None
}

Been doing some research on the semver+git describe options. A live "defacto standard" I found in the NodeJS/NPM community is basically $FULL_TAGGED_SEMVER+$gitcommitsahead.$gitsha, e.g. for above example would be:
1.2.3+7.a1b2c3d
I actually kinda like this upon reflection, as you completely make your local state into the build metadata field only, and releasing a pre-release version becomes always an active decision, e.g. tagging v1.2.4-rc1 or whatever you choose, at which point the above local autoversioning schematic would continue past that in local commits as 1.2.4-rc1+1.b2c3d4e etc.  This solves the issue of not knowing whether a next release is going to be major/minor/patch in advance, and acknowledges that trying do comparison based on number of commits is error prone, due to git rebase et al, so keeping it in the buildinfo field (which does not determine precedence by nature) is desirable.
If melding that mechanism with "SNAPSHOT" (it's still unclear to me if we want this for local versioning), I imagine we would simply append it as the buildinfo suffix in all cases where we are not on a direct tagged commit, e.g. 1.2.3+7.a1b2c3d.SNAPSHOT and 1.2.4-rc1+1.b2c3d4e.SNAPSHOT.
(I'm assuming this would be compatible with SBT versioning schematics, however if not, a close reading of the semver spec does seem to technically allow a - in  build metadata field, even though that looks confusing.  With that, we would do 1.2.4-rc1+1.b2c3d4e-SNAPSHOT instead.


"An error occurred while enumerating through a collection" when running winutil

Describe the bug
When running winutil 24.06.28 (before doing anything else) it shows the following error (part of the error message is in Portuguese because I'm running it in a portuguese Win 11 Pro and you have the translation in the below "Additional context" section):
=====Windows Toolbox=====
An error occurred while enumerating through a collection: A colecção foi modificada; a operação de enumeração poderá
não ser executada..
At line:589 char:5
+     $keys = ($sync.keys).where{ $_ -like "WPF*" }
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Collecti...tableEnumerator:HashtableEnumerator) [], RuntimeExc
   eption
    + FullyQualifiedErrorId : BadEnumeration

Additional context
I run it on a portuguese Windows 11 Pro 23H2 (compilation 22631.3737).
The translation of the portuguese part of the error message is
The collection was modified; the enumeration operation may not be executed..

Commenting on this issue to keep it open, please ignore this comment...

====Chris Titus Tech=====
=====Windows Toolbox=====
InvalidOperation:
Line |
5401 |      $sync.GetEnumerator() | Where-Object {$psitem.Key -in $filter} |  …
|      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| An error occurred while enumerating through a collection: Collection was modified; enumeration operation may not execute..
---        Winget is installed          ---

An error occurred while enumerating through a collection: Collection was modified; enumeration operation may not
execute..
At line:770 char:5

$keys = ($sync.keys).where{ $_ -like "WPF*" }

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : InvalidOperation: (System.Collecti...tableEnumerator:HashtableEnumerator) [], RuntimeExc
eption
FullyQualifiedErrorId : BadEnumeration

=====Windows Toolbox=====
An error occurred while enumerating through a collection: Collection was modified; enumeration operation may not execute..
At line:399 char:5
+     $keys = ($sync.keys).where{ $_ -like "WPF*" }
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Collecti...tableEnumerator:HashtableEnumerator) [], RuntimeException
    + FullyQualifiedErrorId : BadEnumeration

Key cannot be null.
Parameter name: key
At line:5908 char:13
+             $sync.$tabNav.Items[$tabNumber].IsSelected = $true
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (:) [], ArgumentNullException
    + FullyQualifiedErrorId : System.ArgumentNullException


feat: support script for SURE-5880

This includes a support script that can be used to upgrade an EKS cluster using the Rancher API. It's designed for Rancher 2.6.10 where there is a UI bug that prevents users from doing this. This is a temporary solution until the bug fix is released in 2.6.11.
See the README.md for usage instructions, requirements and a demo.

This should should only be used as directed by SUSE support.

Relates To: https://github.com/rancher/eks-operator/issues/103

Seems that only control-plane has been updated.

upgrade the downstream EKS v1.22 cluster to v1.23 by:

./eks-support.sh upgrade -t $RANCHER_TOKEN --endpoint $RANCHER_API --from 1.22 --to 1.23 --name $CLUSTER
[] ONLY USE THIS SCRIPT AS DIRECTED BY SUSE SUPPORT
[] Upgrading cluster th-downstream1 to version 1.23
[] Getting details for cluster th-downstream1
[] Checking cluster is active and with expected version 1.22
[] Sending request to upgrade cluster th-downstream1 (c-frpgz) to 1.23

After a while I checked Rancher UI and the downstream cluster reported new version v1.23

But then I noticed that actually only control-plane was updated, worker nodes are still using v1.22 for some reason.

But then I noticed that actually only control-plane was updated, worker nodes are still using v1.22 for some reason.

This is intentional. For the customers' scenario, they upgrade the node groups via a different mechanism and only needed a script to update the control plane.

@richardcase thanks for confirmation, then the script is working as expected and my approval is legit.

The customer asked for something that would work against the Rancher API, so thats what we did.

Converting back to draft whilst more changes are made for kev1

@dkeightley - for a kev1 cluster i think your suggestion is the best, thanks.
I have created an update to the original script that uses the api and also a new script that uses kubectl patch.


lin_comb method does not produce symmetric Hessian

Information

Qiskit Terra version: 0.16.1     698bd3faf546ac335c3e1a6b202a089e75a19fcd
Python version: 3.7
Operating system: OSX

What is the current behavior?
Methods param_shift and fin_diff produce symmetric hessian, but lin_comb does not.
Steps to reproduce the problem
import numpy as np
from qiskit import QuantumCircuit, QuantumRegister
from qiskit.circuit import Parameter
from qiskit.opflow import X, Z, StateFn, CircuitStateFn
from qiskit.opflow.gradients import Hessian

ham = 0.5 * X - 1 * Z
a = Parameter('a')
b = Parameter('b')
params = [(a, b), (b, a)]

q = QuantumRegister(1)
qc = QuantumCircuit(q)
qc.h(q)
qc.rz(a, q[0])
qc.rx(b, q[0])

op = ~StateFn(ham) @ CircuitStateFn(primitive=qc, coeff=1.)
state_hess = Hessian(hess_method='lin_comb').convert(operator=op, params=params)

print(state_hess.assign_parameters({a: np.pi / 2, b: np.pi / 4}).eval())  # [0j, (-0.7071067811865474-7.8e-16j)]

What is the expected behavior?
print(state_hess.assign_parameters({a: np.pi / 2, b: np.pi / 4}).eval())  # [0j, 0j]

This will be fixed by #5501

fixed by #5501


Fix broken headings in Markdown files

GitHub changed the way Markdown headings are parsed, so this change fixes it.
See bryant1410/readmesfix for more information.
Tackles bryant1410/readmesfix#1

Codecov Report

Merging #25 into master will increase coverage by 0.38%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #25      +/-   ##
==========================================
+ Coverage   83.87%   84.25%   +0.38%
==========================================
  Files           6        6
  Lines         217      216       -1
  Branches       46       46
==========================================
  Hits          182      182
+ Misses         35       34       -1

Impacted Files
Coverage Δ

src/redux-bug-reporter.js
68.57% <0%> (+0.64%)
:arrow_up:

Continue to review full report at Codecov.

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

You're a hero, thanks!


Update expressroute-erdirect-about.md

clarify over-subscription and current lack of portal support

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

File
Status
Preview URL
Details

articles/machine-learning/how-to-auto-train-image-models.md
:warning:Warning

Details

articles/machine-learning/how-to-configure-cli.md
:warning:Warning

Details

articles/machine-learning/how-to-create-attach-compute-cluster.md
:warning:Warning

Details

articles/machine-learning/how-to-create-component-pipeline-python.md
:warning:Warning

Details

articles/machine-learning/how-to-create-manage-compute-instance.md
:warning:Warning

Details

articles/machine-learning/how-to-customize-compute-instance.md
:warning:Warning

Details

articles/machine-learning/how-to-manage-workspace.md
:warning:Warning

Details

articles/machine-learning/how-to-prepare-datasets-for-automl-images.md
:warning:Warning

Details

articles/machine-learning/how-to-read-write-data-v2.md
:warning:Warning

Details

articles/machine-learning/how-to-schedule-pipeline-job.md
:warning:Warning

Details

articles/machine-learning/how-to-secure-online-endpoint.md
:warning:Warning

Details

articles/machine-learning/how-to-train-cli.md
:warning:Warning

Details

articles/machine-learning/how-to-train-sdk.md
:warning:Warning

Details

articles/machine-learning/how-to-use-sweep-in-pipeline.md
:warning:Warning

Details

articles/machine-learning/tutorial-auto-train-image-models.md
:warning:Warning

Details

articles/machine-learning/v1/how-to-deploy-and-where.md
:warning:Warning

Details

articles/machine-learning/v1/tutorial-pipeline-python-sdk.md
:warning:Warning

Details

includes/machine-learning-connect-ws-v2.md
:warning:Warning

Details

includes/machine-learning-service-local-deploy-config.md
:warning:Warning

Details

articles/expressroute/expressroute-erdirect-about.md
:white_check_mark:Succeeded

articles/machine-learning/how-to-auto-train-image-models.md

Line 197, Column 1: [Warning: invalid-code] The code snippet "~/azureml-examples-main/sdk/jobs/automl-standalone-jobs/automl-image-object-detection-task-fridge-items/data/training-mltable-folder/MLTable" could not be found.
Line 225, Column 1: [Warning: codesnippet-not-found] Invalid code snippet link: '~/azureml-examples-main/sdk/jobs/automl-standalone-jobs/automl-image-object-detection-task-fridge-items/automl-image-object-detection-task-fridge-items.ipynb'.
Line 349, Column 1: [Warning: codesnippet-not-found] Invalid code snippet link: '~/azureml-examples-main/sdk/jobs/automl-standalone-jobs/automl-image-object-detection-task-fridge-items/automl-image-object-detection-task-fridge-items.ipynb'.
Line 426, Column 1: [Warning: codesnippet-not-found] Invalid code snippet link: '~/azureml-examples-main/sdk/jobs/automl-standalone-jobs/automl-image-object-detection-task-fridge-items/automl-image-object-detection-task-fridge-items.ipynb'.
Line 450, Column 1: [Warning: codesnippet-not-found] Invalid code snippet link: '~/azureml-examples-main/sdk/jobs/automl-standalone-jobs/automl-image-object-detection-task-fridge-items/automl-image-object-detection-task-fridge-items.ipynb'.
Line 542, Column 1: [Warning: codesnippet-not-found] Invalid code snippet link: '~/azureml-examples-main/sdk/jobs/automl-standalone-jobs/automl-image-object-detection-task-fridge-items/automl-image-object-detection-task-fridge-items.ipynb'.
Line 572, Column 1: [Warning: codesnippet-not-found] Invalid code snippet link: '~/azureml-examples-main/sdk/jobs/automl-standalone-jobs/automl-image-object-detection-task-fridge-items/automl-image-object-detection-task-fridge-items.ipynb'.
Line 574, Column 1: [Warning: codesnippet-not-found] Invalid code snippet link: '~/azureml-examples-main/sdk/jobs/automl-standalone-jobs/automl-image-object-detection-task-fridge-items/automl-image-object-detection-task-fridge-items.ipynb'.
Line 576, Column 1: [Warning: codesnippet-not-found] Invalid code snippet link: '~/azureml-examples-main/sdk/jobs/automl-standalone-jobs/automl-image-object-detection-task-fridge-items/automl-image-object-detection-task-fridge-items.ipynb'.
Line 594, Column 1: [Warning: codesnippet-not-found] Invalid code snippet link: '~/azureml-examples-main/sdk/jobs/automl-standalone-jobs/automl-image-object-detection-task-fridge-items/automl-image-object-detection-task-fridge-items.ipynb'.
Line 615, Column 1: [Warning: codesnippet-not-found] Invalid code snippet link: '~/azureml-examples-main/sdk/jobs/automl-standalone-jobs/automl-image-object-detection-task-fridge-items/automl-image-object-detection-task-fridge-items.ipynb'.
Line 635, Column 1: [Warning: codesnippet-not-found] Invalid code snippet link: '~/azureml-examples-main/sdk/jobs/automl-standalone-jobs/automl-image-object-detection-task-fridge-items/automl-image-object-detection-task-fridge-items.ipynb'.
Line 671, Column 1: [Warning: codesnippet-not-found] Invalid code snippet link: '~/azureml-examples-main/sdk/jobs/automl-standalone-jobs/automl-image-object-detection-task-fridge-items/automl-image-object-detection-task-fridge-items.ipynb'.
Line 691, Column 1: [Warning: codesnippet-not-found] Invalid code snippet link: '~/azureml-examples-main/sdk/jobs/automl-standalone-jobs/automl-image-object-detection-task-fridge-items/automl-image-object-detection-task-fridge-items.ipynb'.
Line 709, Column 1: [Warning: codesnippet-not-found] Invalid code snippet link: '~/azureml-examples-main/sdk/jobs/automl-standalone-jobs/automl-image-object-detection-task-fridge-items/automl-image-object-detection-task-fridge-items.ipynb'.

articles/machine-learning/how-to-configure-cli.md

Line 80, Column 1: [Warning: invalid-code] The code snippet "~/azureml-examples-main/setup-repo/azure-github.sh" could not be found.
Line 87, Column 1: [Warning: invalid-code] The code snippet "~/azureml-examples-main/setup-repo/azure-github.sh" could not be found.
Line 91, Column 1: [Warning: invalid-code] The code snippet "~/azureml-examples-main/setup-repo/azure-github.sh" could not be found.

articles/machine-learning/how-to-create-attach-compute-cluster.md

Line 90, Column 1: [Warning: codesnippet-not-found] Invalid code snippet link: '~/azureml-examples-main/sdk/resources/compute/compute.ipynb'.
Line 176, Column 1: [Warning: codesnippet-not-found] Invalid code snippet link: '~/azureml-examples-main/sdk/resources/compute/compute.ipynb'.

articles/machine-learning/how-to-create-component-pipeline-python.md

Line 62, Column 1: [Warning: codesnippet-not-found] Invalid code snippet link: '~/azureml-examples-main/sdk/jobs/pipelines/2e_image_classification_keras_minist_convnet/image_classification_keras_minist_convnet.ipynb'.
Line 72, Column 1: [Warning: codesnippet-not-found] Invalid code snippet link: '~/azureml-examples-main/sdk/jobs/pipelines/2e_image_classification_keras_minist_convnet/image_classification_keras_minist_convnet.ipynb'.
Line 106, Column 1: [Warning: invalid-code] The code snippet "~/azureml-examples-main/sdk/jobs/pipelines/2e_image_classification_keras_minist_convnet/prep/prep_component.py" could not be found.
Line 130, Column 1: [Warning: invalid-code] The code snippet "~/azureml-examples-main/sdk/jobs/pipelines/2e_image_classification_keras_minist_convnet/prep/prep_component.py" could not be found.
Line 136, Column 1: [Warning: invalid-code] The code snippet "~/azureml-examples-main/sdk/jobs/pipelines/2e_image_classification_keras_minist_convnet/prep/conda.yaml" could not be found.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit c7166c9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/expressroute/expressroute-erdirect-about.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

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

#sign-off


TPI: Symlinks with Pytest

Refs: 22658

[x] macOS @rzhao271
[x] linux @roblourens
[x] windows @luabud

Complexity: 3
Author: @eleanorjboyd
Create Issue
Create Issue

Thank you for doing this testing!

in terminal cd to parent folder parent
create folder inside parent target_folder with tests such as test_example.py (a file with a test inside)
from terminal create a symlink ln -s target_folder symlink_to_target_folder (this is for mac specifically)
open vscode with the folder symlink_to_target_folder can be done with code symlink_to_target_folder in terminal
from command palette use create environment command
in terminal install pytest via python -m pip install pytest
run test discovery (click beaker icon), test UI will be populated
check to make sure the root test explorer view is symlink_to_target_folder
click on "go to file" on a test, make sure the symlink file opens
try to run tests make sure it works

At this step

run test discovery (click beaker icon), test UI will be populated

I had to click "Configure Python Tests", is that right, or is it supposed to pick them up automatically?

yes configure python tests is correct! Currently setting the setting "python.testing.pytestEnabled: true" is required to discover which is done via this configure button

worked great! 🥳


ci: fix lint

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Test/pnpm strict peer dependencies

Description

Example

[ ] I have verified if my change requires an example

Screenshots/screencasts

Changeset

[ ] I have verified if my change requires a changeset

Related tasks and documents

Open TODOs/questions

Further information

testing if - pnpm install fails


Add protocol parameter to "application-gateway http-listener" and "application-gateway listener" Commands

Describe the bug
Add protocol parameter to "application-gateway http-listener" and "application-gateway listener" Commands
Currently "az network application-gateway http-listener create" and "az network application-gateway listener create" do not have protocol parameter and if --ssl-cert parameter is mentioned it implicitly creates a HTTPS or TLS listener. And this is confusing for the customers.
Example cmdlet having protocol parameter : az network application-gateway http-settings create
Related command
az network application-gateway http-listener create
az network application-gateway listener create
Errors
commands do not support protocol parameter
Issue script & Debug output
commands do not support protocol parameter
Expected behavior
commands should have protocol parameter
Environment Summary
azure-cli                         2.39.0 *
core                              2.39.0 *
telemetry                          1.0.6 *
Extensions:
azure-devops                      0.23.0
Dependencies:
msal                            1.18.0b1
azure-mgmt-resource             21.1.0b1
Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\gdhillon.azure\cliextensions'
Python (Windows) 3.10.5 (tags/v3.10.5:f377153, Jun  6 2022, 15:58:59) [MSC v.1929 32 bit (Intel)]
Legal docs and information: aka.ms/AzureCliLegal
Additional context
No response

Thank you for opening this issue, we will look into it.

Hi @gdhillon24,
2.39.0 is not the latest Azure CLI(2.61.0).
If you haven't already attempted to do so, please upgrade to the latest Azure CLI version by following https://learn.microsoft.com/en-us/cli/azure/update-azure-cli.

Hey I have verified with the latest version as well --protocol  parameter is not supported
PS C:\tenant\Networking-AppGW> az network application-gateway http-listener create --gateway-name "wafv2appgw" --resource-group "guruMig" --name "httpsLis4" --frontend-ip "appGwPublicFrontendIpIPv4" --frontend-port "port446" --ssl-cert "cert1" --host-name "hostname2" --protocol Https
unrecognized arguments: --protocol Https
Examples from AI knowledge base:
https://aka.ms/cli_ref
Read more about the command in reference docs
PS C:\tenant\Networking-AppGW> az version
{
"azure-cli": "2.61.0",
"azure-cli-core": "2.61.0",
"azure-cli-telemetry": "1.1.0",
"extensions": {
"azure-devops": "0.23.0"
}
}

Hi @yonzhan
I have updated the description of the bug (included important notes )and the related commands section


Not success status code: 403

Hi ! Yesterday I had a problem that I never seen before . I got a "Not success status code: 403 " trying to play some yt track ( full logs in the image )

I cant reproduce it becouse happen randomly :(
Anyone have the same problem ?
Lavaplayer version : 1.4.0

There's no 1.4.0 in this repo, are you sure you're not using https://github.com/Walkyst/lavaplayer-fork ? (If you aren't, make sure you do, this repo is dead. Also update to 1.4.2)

There's no 1.4.0 in this repo, are you sure you're not using https://github.com/Walkyst/lavaplayer-fork ? (If you aren't, make sure you do, this repo is dead. Also update to 1.4.2)

im using this lavalink version with lavaplayer on 1.4.0 https://github.com/lavalink-devs/Lavalink/releases/tag/3.7.5


Updated Protobuf

Testing:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.2420
https://travis-ci.org/ingenue/hunter/builds/276886736?utm_source=github_status&utm_medium=notification

Testing

Something wrong with Protobuf-legacy example.
I've recently updated instructions how you can test it yourself before making pull request:

https://docs.hunter.sh/en/latest/creating-new/create/cmake.html#ci-testing

Testing:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.2431
https://travis-ci.org/ingenue/hunter/builds/277364926?utm_source=github_status&utm_medium=notification

Testing

Android stop working. Please test new version before sending updates, details here:

https://docs.hunter.sh/en/latest/creating-new/create/cmake.html#ci-testing

Sorry, i tested with the archive uploaded to my fork and then... yeah, lets say i am too dump to generate the  archive from the right branch :D. 3.1.0-hunter-2 is pointing to 3.3.0 (which has the problem in the tests).
You will see in commits soon.

sec, wrong branch

Is it ready for testing now?

yep, thx

yep, thx

Have you tested with these instructions?

https://docs.hunter.sh/en/latest/creating-new/create/cmake.html#ci-testing

i tried, didn't get it to work, but it's a long day for me, so that could be the problem, i tested all toolchains with the example locally.

i tried, didn't get it to work, but it's a long day for me, so that could be the problem, i tested all toolchains with the example locally.

I've just added testing documentation so it would be nice to have some feedback. Basically you need to register in Travis/AppVeyor and push one branch, that's all. Currently testing part is the longest one because I have to retest pull request again and again. It's a waste of time.

It's 21:00 here, but ill have a look at this tomorow morning. I'll give you feedback!

Ok I guess my tests are running:

Is there an option to setup appveyor to respect the test.* convention?

Ok I guess my tests are running

Looks good, congrats! :tada:

Is there an option to setup appveyor to respect the test.* convention?

What do you mean?

I had to select the branch in my config on the site, it defaults to master branch. Thought there is an option to select all test.* branches. But maybe it picks every branch up and I just didn't wait long enough ...
Von meinem iPhone gesendet

Am 20.09.2017 um 18:03 schrieb Ruslan Baratov<EMAIL_ADDRESS>Ok I guess my tests are running
Looks good, congrats! 🎉
Is there an option to setup appveyor to respect the test.* convention?
What do you mean?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I had to select the branch in my config on the site, it defaults to master branch. Thought there is an option to select all test.* branches. But maybe it picks every branch up and I just didn't wait long enough ...

Not sure I understand. Select for what? Select where?

Never mind, I just need to read into the AppVeyor docs.
For feedback to your testing documentation:
It is kind of hard to get into it, because you explain it on an abstract level and mix in an example of a new package. I think the document would be a lot simpler if you describe the process with two examples. One for package updates and one for new packages. I imagine something like:
Prepare:

Sign in to AppVeyor and Travis with your GitHub Account, and enable your hunter fork for testing. (Note: Those services are free to use with public repos)
$git remote add ci https://github.com/ingenue/hunter

Package Update: GTest (assumes no test needs to be changed)

$git fetch ci
$git checkout pkg.gtest
$git checkout pr.gtest (your branch where you requested the pull)
$git checkout -b test.gtest
$git merge pkg.gtest

$git push -u origin test.gtest

What happens:

1-2 checking out branch for ci repo to get the current test configs
3-4 create a tmp branch to run tests against from your pull request
5-6 get the test configs from 1-2 into your tmp test branch
7 push test branch to your hunter fork to trigger tests in AppVeyor and Travis

New Package: MyPackage

...

What happens:

....

Advanced
Disable specific tests
...
So it would easy to get up and running with a single glance, and you'd still be able to dig deeper.

Prepare
Sign in to AppVeyor and Travis ...
git remote add ci https://github.com/ingenue/hunter

This part is the same as Create: CI testing, I've already added a note:

https://docs.hunter.sh/en/latest/creating-new/update.html#testing

Package Update: GTest (assumes no test needs to be changed)

So it's the same as current documentation (?)

What happens

I've added few notes to documentation:

https://docs.hunter.sh/en/latest/creating-new/update.html#testing

:D Wow, i just looked at the site you linked earlier for new packages. Yeah now it makes sense, and is exactly what I was looking for.

One small point: First point should say that you explain update with hunter_box as an example. Due to the 'hunter' in it, it could be a bit confusing (could be something special for tests...). Otherwise its a very nice doc and should be foolproof!

Due to the 'hunter' in it, it could be a bit confusing

You mean like renaming it to my_cool_package? Something without hunter?

Did @fwinnen ever update the Hunter config to add Protobuf 3.1 and 3.3? This might answer #1091 for me.

@isaachier Not sure I understand the question. Current version is 3.0.0:
https://github.com/ruslo/hunter/blob/ce2637526f3ad3d1e6f1cd64e02bd002ea6d0e21/cmake/configs/default.cmake#L107

Right but I don't think I am able to access any upstream version (meaning 3.1 and 3.3) even when overriding the config. I believe those releases are available on hunter-packages/protobuf, but @fwinnen did not add them to the Protobuf Hunter file for use.

I don't think I am able to access any upstream version (meaning 3.1 and 3.3) even when overriding the config

@isaachier They are in this pull request which is opened and not merged. Feel free to work on it.

https://github.com/ruslo/hunter/pull/1096


Add basis of command-support for Paper plugins

Some parts of the code were rearranged or removed to reduce the amount of duplications and the size of the plugin.
I combined the code that validates the commands into one extension to also reduce the number of duplicates and the size of the plugin.

Thanks for working on this! I'm a bit confused though: As far as I understood, commands is intentionally not supported in paper-plugin.yml (see https://github.com/PaperMC/Paper/issues/8859#issuecomment-1438838087). Has this changed? If yes, can you point to the change in Paper that adds support for reading commands from paper-plugin.yml? I didn't find anything related on a quick look.

Hi! I'm not exactly up-to-date about the command system in the newest version, but yes, you seem to be right.
My thought on why I wanted to implement this was the point that if you use paper {} you can't access the legacy command feature from bukkit. For people not knowing enough about the latest changes in the Paper API this would be useful, as far as I thought...
For me, this would be useful because at the moment my plugins rely on the legacy system. Because the paper-plugin.yml is just a drop in replacement for the plugin.yml I don't think that the commands  feuture will be removed.

I think that paper-plugin.yml is a drop in replacement for plugin.yml only in the sense that it serves the same purpose. This doesn't mean that everything from plugin.yml is supported exactly the same way with paper-plugin.yml. The format is actually (intentionally) different in some aspects, e.g. the dependencies.
As far as I can tell there is not any code in Paper that would parse the commands from the paper-plugin.yml (I looked mostly around https://github.com/PaperMC/Paper/blob/master/patches/server/0013-Paper-Plugins.patch#L4768 where most of the paper-plugin.yml parsing happens). Please check if adding commands in paper-plugin.yml really makes any noticeable difference, or maybe ask in the Paper chat if this is supported.
If your plugins rely on the legacy command system it might be easier if you stick to plugin.yml for now. This is still supported just fine when using Paper. paper-plugin.yml is still experimental AFAIK and only meant for plugins that really can and want to make use of the new functionality.

So - I've talked a bit with some people from Paper. The plan is pretty much like you said it would be. The implementation of the commands should be completely in the code-basis, not in the yml's anymore, so you're right and my "comfort-solution" is now unfortunately obsolete. 🥲
But thank you for your time, was still interesting to look at a Gradle plugin for the first time, lol. Good idea, but I would still adapt a few things - especially since there are an extremely large number of duplicates and, despite the same functionality or the same result, are designed differently in the real function.


Segmentation fault

I deployed my rails application on Google Kubernetes Engine.
ruby '2.5.1'
rails '5.1.7'

Server:
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"

When I try to use any method from taglib-ruby library, I get an error.
What could be the problem?

Sounds like it could be a Clang problem. Have you established that on the
server, the C extensions of taglib-ruby were compiled using Clang? I can't
tell from the output.
If the server is using Clang you could try getting it to use GCC instead.
This might help:
https://github.com/robinst/taglib-ruby#os-x-c-compiler-override
Op di 3 mrt. 2020 om 14:41 schreef Roman<EMAIL_ADDRESS>
I deployed my rails application on Google Kubernetes Engine.
ruby '2.5.1'
rails '5.1.7'
Server:
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
When I try to use any method from taglib-ruby library, I get an error.
What could be the problem?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/robinst/taglib-ruby/issues/90?email_source=notifications&email_token=AAKGH57T36J7ITMDEB5E2VDRFUCIPA5CNFSM4LAKW2W2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ISA3TXQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKGH52VCZGQEUD467IE4ELRFUCIPANCNFSM4LAKW2WQ
.

@jacobvosmaer When using gcc instead of clang, same error occurs.

Hm, does the segmentation fault also occur when you do this?:
TagLib::MPEG::File.open('file.mp3') { |file| file.id3v2_tag.title }

@robinst  Yes, in this case, an error also occurs.
It appears when I try to open a file.

I have this problem too but only on my CENT OS 7 production sever. On my local dev server, I don't have this issue. I'm also only getting it when I do anything with the database. The different there also is that I'm using MySQL on the dev machin and MariaDB on the production server.

@oksromn Can you please try again with a newer release of taglib-ruby and taglib?


Dooit: fix build

Description of changes
Resolves https://github.com/NixOS/nixpkgs/issues/330380
A dependency Textual was recently refactored to include tree-sitter-languages as a dependency. That package has a dependency on tree-sitter0_21 which doesn't support Python 3.12 atm.

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 330518 run on aarch64-darwin 1

2 packages built:

dooit
dooit.dist

@ofborg build Dooit

@ofborg build dooit

Result of nixpkgs-review pr 330518 run on aarch64-darwin 1

2 packages built:

dooit
dooit.dist


0.27: Direct store mutation through model

Hey,
I am not sure if this is a mistake or if we used the library incorrectly:
Our concept:

load Data in the Store
receive a model instance by id
change some values (e.g. model.name = 'newName')
call our custom save Method in the Model
=> The save Method will make an API-Request. On success the new data will saved in the store.

This was possible because the getter created new instances of the model. Now, however, the object is returned directly from the store. As a result, the store is unfortunately mutated directly (without an mutation).
If you have an store with activated strict mode (https://vuex.vuejs.org/guide/strict.html) you will get the following error: Do not mutate vuex store state outside mutation handlers.
Unfortunately I do not know if you want to support this use case.
But tickets like this at least indicate that. https://github.com/vuex-orm/vuex-orm/issues/150

Hi! Thank you for the report!
Yes, this behavior is intended at 0.27.0. I know it was possible to mutate the retrieved records before 0.27.0, but I never wanted to recommend such usage.
Since Vuex ORM is just a Vuex plugin, mutating the value returned from getters should be considered as an anti-pattern.
I understand what you're trying to do, but I think it should be supported in a different way, such as creating temporary "workspace" store state. Mutating the object returned from getters may cause some unwanted result regarding the reactivity system as well.
You are also right about "save" method - #150 -, but that method is more intended to be used something like follows (user object is not created inside Vuex Store).
export default {
  data () {
    return {
      user: new User()
    }
  },

  methods: {
    save () {
      this.user.$save()
    }
  }
}

Maybe we could add some option or method to get a fresh instance from getters. I see some use case for that. But again, I'm not sure if we really want to take that path as we're using Vuex under the food.
What do you think?

Since Vuex ORM is just a Vuex plugin, mutating the value returned from getters should be considered as an anti-pattern.

Yes, you are absolutely right.
Before we used this library, we cloned the data to fill our forms. We should do that now too.
Thanks for the response ;)

Thanks for your kind understanding! Please feel free to open another issue if you have any trouble!

I bumped into this issue recently, and I am not sure I understand all the reasons.
We wanted to use this package the following way:

get a copy of the record in the vuex store by a getter
mutate the properties of this copy by v-model in the forms
save the changes to the vuex store at a given point

The funny thing it kinda worked as long as we used queries like User.query().with('roles').all() - the important part being with(). This is because Query.ts#L732 re-initializes the model instances if load property is not empty (is filled by with()). But recently we had a rare case, when no relations were needed, and we bumped into vuex's error.
So, the point is, we do not intend to mutate the vuex store state outside mutations, but mutate the copy, and save the changes via mutations.
Furthermore I think the behaviour is inconsistent, since it works makes copies when with() is used, but without it a workaround is needed (like new User(User.find(1)) or User.query().with('').find(1))
@kiaking what do you think about it?
Thanks in advance!

@SzNagyMisu Hi! Yeah, the getter will return a new copy of Model when you fetch them with a relationship. This is by design.
I agree that the behavior is inconsistent, but I made it like so to gain a bit of performance when you don't need relationships. Furthermore, it is going to be essential to return the state as is when we implement lazy loading.
Maybe it's a bit opinionated, but I strongly don't recommend trying to mutate the value returned from the getter. I understand you're not trying to mutate them, but I think copying the object should be done inside Vue Component rather than in Getters. Because getters a like computed property in Vue Component, and I think it's a kinda anti-pattern to mutate the value you get from the computed property.
But, I still understand your case too. So I'm kinda open on idea to have another API that explicitly tells Vuex ORM to fetch a copy of models. What do you think?

Hi @kiaking
I see your point about mutating the value recieved from a getter being an anti-pattern. In order to understand my point of view I tell you my story:
Just before we found vuex-orm, I have been reading a Vue forum discussion about storing data in vuex, where LinusBorg advised two important things:

to normalize data (this is done well in vuex-orm)
to store only plain objects in vuex

So, after that, when we found your plugin, I assumed it is built upon those priciples, I was sure that the data stored in vuex is normalized and converted to plain objects. I thought it worked like the getters returned the plain object, and the model methods converted them to instances. A bit like the way ActiveRecord works.
This way the principle of not mutating data from getters directly would be respected, but we would have the possibility of mutating the instance and saving it to the store on appropriate moments.
Now, being more familiar with the way vuex-orm works, I am not sure this logic can be implemented... Perhaps an option could be passed to the install() function indicating that I want my data not only normalized but converted to plain objects as well. But that would be hard work to implement.
Until then, I think, I will just use new User(User.find(1)).

@SzNagyMisu Thank you for the detailed explanation! Yeah, I understand your use case.
Well, Vuex ORM actually stores Class instance directly to the Vuex Store. The reason is it's going to be a bit faster to load data because we don't have to instantiate each record every time we fetch from the store.
So I guess, as you said, we could have a new API that returns a copy of the record. Since your workaround new User(User.find(1)) should work on most of the cases, there is a chance that records could have Object and Array, in that case, it will not work correctly. We must do a deep copy.
Something like User.query().getNew() could be nice...?

@kiaking I like the idea of deep copying a record. Although, I'd rather prefer something like User.find(1).$clone() or $deepClone(). What do you think?

@SzNagyMisu Ah, good idea! That makes much more sense. Could you open another issue for adding $clone method to the model?


Optionally disables parsing of dependent projects in the background

... on file open/save. This is a workaround for intellisense performance issues in large solutions where some projects are referenced by many other projects.

@Krzysztof-Cieslak, hi! Meant to assign you as a reviewer.

Seems good, thanks!


Sorting Posts By Payout Displays ''Nothing Here'

Expected behavior
Sorting post using the Payout button was expected to display ports posted within 7days according to their total payout (Highest To lowest).
Actual behavior
After clicking on the payout button, it displays  a page with Nothing Here.
How to reproduce

Download eSteem Surfer. Version 1.0.6

Open eSteem Surfer.

locate  and click Payout button from the drop down

Browser/App version:   and Google Chrome Version 67.0.3396.87

Operating system: Windows 10 (64-bit)

Recording Of The Bug
https://youtu.be/3l5AUUpdmrY

This depends on selected Server from Settings page. 1.0.7 has proper error handling to address this.


Revert "Build: Save build artifact and publish release (#2633)"

This reverts commit 19b57d83f881caf998a788c5392514fbeaa9d89f.
See https://github.com/envoyproxy/envoy/issues/2812

@taion809

LGTM


Fix Demote Locking/banning users

According to resource monitor Locking/banning is implied that it will demote both the target users global and room auth, where as currently it only demotes the target user from roomauth, this commit fixes it to demote the user from both room and global auth.

Does the current code for it not work?
https://github.com/Zarel/Pokemon-Showdown/blob/master/users.js#L1159
If it doesn't, fix it there rather than where you've done it right now

Alright, I used the users.js implentation this time after taking kota's advice.

This is still wrong.

This actually confirms a user, which is the opposite of what deconfirm is supposed to do.

Done in 169a9756ad7


Cargo deletes executables in same workspace when doing cargo build on both at the same time.

When I have multiple executables in a workspace, and do cargo build on one and then before it finishes I do it also on the other exe, it says Blocking waiting for file lock on the git checkouts event though there are no git checkouts happening.
And when the second exe finishes building, the first one is not there!
But it should have built both.
Then I have to build the first one again, which is annoying because it takes the full build time again.

Do you have an example project I could poke around to investigate this? Are you sure there are zero git dependencies in the entire dependency graph?

There are git dependencies, but none that have to be checked out. They are all up-to-date.
If I wait until the first exe has finished building and only then run cargo build, it works, but if I start running cargo build on the second one before the first one has finished, it deletes the first exe for some reason.
I'll make an example project..

Cargo globally synchronizes access to git dependencies, so that's expected behavior.

Why does it have to delete the exe if the git dependency didn't change?

That does indeed sound buggy! Was waiting for an example project to test it out and poke around myself :)

Closing due to inactivity and inability to reproduce. Please reopen if you have a chance to make an example project illustrating this problem! Thanks!


Remove weekly and monthly options from replicationSchedule

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Replication is currently in private preview. NetApp and Microsoft have decided that weekly and monthly replication schedules will not be an option in the future (going to public preview) so an error will be thrown if they are sent in.
We are updating the older swagger files to represent this change in order to avoid confusion.
Contribution checklist:

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

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

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

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

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

/azp run automation - sdk

@lirenhe Regarding the error in Swagger ModelValidation, the password value is masked in the response. Does this require any action in this pull request or can it be ignored?


Tasks with same name from different workspaces conflict in multi-root workspace environment

VSCode Version: 1.43.2
OS Version: macOS Catalina Version 10.15.4

Steps to Reproduce:

Create a folder called vs-code-potential-bug
Then, create vs-code-potential-bug/project-1 and vs-code-potential-bug/project-2
Inside each project folder, create a TypeScript project
Create a multi-root workspace configuration file; e.g. vs-code-potential-bug/default.code-workspace
Open that new workspace with VS Code
Launch a TypeScript watch task for project-1
Try launching a TypeScript watch task for project-2 while the previous watch task is still running.

On my system, that last step prompts a warning box saying: The task 'tsc: watch - tsconfig.json (Project #1)' is already active.

Does this issue occur when all extensions are disabled?: Yes
Additional notes

As far as I can tell, this occurs for any task that has the same name as a task inside another project inside the same multi-root workspace.
I started noticing this behaviour about two months ago, but, if I recall correctly, I used, with earlier versions of VS Code, to be able to run those "same-named tasks" without problem.

Thank you for your time and support. :)

@focorner I fixed something that looks exactly like this recently. Can you try with the insiders build? It installs side by side with stable, so it won't change your current install. https://code.visualstudio.com/insiders/

@alexr00 I just tried with Visual Studio Code - Insiders as you recommended and it worked! The problem is no longer there. Great job!
Do you know if this fix will be shipped with the next release?
Thank you very much for your time and support. A+

@focorner Thanks for trying it! It is planned to be in the next release.

duplicate of https://github.com/microsoft/vscode/issues/93398


[Feature request] Allow array when set build.rollupOptions

Clear and concise description of the problem
I want to set different output format for different input file. such as es for index.html, cjs for 'app.js'
But currently build.rollupOptions can only be a object.
when set build.rollupOptions as an array:
Unknown input options: 0.

Suggested solution
From https://rollupjs.org/guide/en/#configuration-files
// can be an array (for multiple inputs)

so we can extend build.rollupOptions to accept an array.
Alternative
allow to set a function as output format.
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Duplicate of #2039


Document tabbing to hyperlink

Document that in mark mode you can now tab to the next/previous hyperlink.

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

File
Status
Preview URL
Details

TerminalDocs/selection.md
:warning:Warning
View
Details

TerminalDocs/selection.md

Line 43, Column 206: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/windows/terminal/customize-settings/interaction#automatically-detect-urls-and-make-them-clickable' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 43, Column 206: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/windows/terminal/customize-settings/interaction#automatically-detect-urls-and-make-them-clickable' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 5628a35:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

TerminalDocs/selection.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Kayla is investigating to ensure this is in the current GA release.

Not yet ready for merge - still in a PR

Docs Build status updates of commit 5628a35:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

TerminalDocs/selection.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


[pulsar-broker] Add stop replicator producer logic when start replicator cluster failed

Motivation
When create persistent topic in BrokerService#createPersistentTopic:
public void openLedgerComplete(ManagedLedger ledger, Object ctx) {
                            public void openLedgerComplete(ManagedLedger ledger, Object ctx) {
                            try {
                                PersistentTopic persistentTopic = isSystemTopic(topic)
                                        ? new SystemTopic(topic, ledger, BrokerService.this)
                                        : new PersistentTopic(topic, ledger, BrokerService.this); // @ Here may throw NamingException
                                ...
                                }).thenRun(() -> {
                                    ...
                                }).exceptionally((ex) -> {
                                    log.warn(
                                            "Replication or dedup check failed."
                                                    + " Removing topic from topics list {}, {}",
                                            topic, ex);
                                    persistentTopic.stopReplProducers().whenComplete((v, exception) -> {
                                        topics.remove(topic, topicFuture);
                                        topicFuture.completeExceptionally(ex);
                                    });

                                    return null;
                                });
                            } catch (NamingException | PulsarServerException e) {
                                log.warn("Failed to create topic {}-{}", topic, e.getMessage());
                                pulsar.getExecutor().execute(() -> topics.remove(topic, topicFuture));
                                topicFuture.completeExceptionally(e);
                            }
                        }

It may throw NamingException when new PersistentTopic. We don't stop replicator producers in the NamingException catch block. This will result in some replicator producers being created and keep in the remote clusters producers list.
Any later retry to add replicator producers fails with the below logs :
Nov 05 13:25:31 pulsar-broker-node-1 pulsar[11435]: 13:25:31.054 [ForkJoinPool.commonPool-worker-29] ERROR org.apache.pulsar.broker.service.ServerCnx - [/<IP_ADDRESS>:34976] Failed to add producer to topic persistent://SD/operator20018/groupsettings: producerId=17690, org.apache.pulsar.broker.service.BrokerServiceException$NamingException: Producer with name 'pulsar.repl.ctp-pulsar-stage-cluster' is already connected to topic
Nov 05 13:25:33 pulsar-broker-node-1 pulsar[11435]: 13:25:33.351 [ForkJoinPool.commonPool-worker-29] ERROR org.apache.pulsar.broker.service.ServerCnx - [/<IP_ADDRESS>:34952] Failed to add producer to topic persistent://SD/operator20018/groupsettings: producerId=17694, org.apache.pulsar.broker.service.BrokerServiceException$NamingException: Producer with name 'pulsar.repl.ctp-pulsar-stage-cluster' is already connected to topic
Nov 05 13:25:33 pulsar-broker-node-1 pulsar[11435]: 13:25:33.670 [ForkJoinPool.commonPool-worker-29] ERROR org.apache.pulsar.broker.service.ServerCnx - [/<IP_ADDRESS>:34970] Failed to add producer to topic persistent://SD/operator20018/groupsettings: producerId=17696,

Documentation

[ x ] no-need-doc

@Technoboy- It seems that this solution doesn't work in all cases.
I've been debugging the issue and it looks like the changes in #11804 limited the producer replacement to one connection (&& Objects.equals(cnx, other.cnx)). The replacement won't happen if another connection is chosen on the client side for creating the next producer. The changes in #11804 were refactored further in #12846.
I'm not sure about the reason yet, just making some initial guesses.


Added validator for @TypeConverters

Table of Contents
Link to GitHub issues it solves
closes #9
Description
Added validator for @TypeConverters in the depot dispatcher.
Contributing has more information and tips for a great pull request.

@zeobot set lc to pass