i18n(es): update auto.mdx & configuration-reference.mdx

Description

Update content

Reference

b6f0f0c
configuration-reference.mdx

Hi! I can see the problem here is that the /es/ configuration-reference page has not yet been updated to include the new Dev Toolbar Options!
You have two choices... 1) update configuration-reference FIRST  :smile: OR 2) remove the link here now, then come back and put the link back in after configuration reference is updated!

Hi, finally I just updated the configuration-reference.mdx page. Also changed the /es/ link. Thanks! 🐳

Thanks! All done! 🙌


feat: integrate user network selection for managing deposit flow for non-NEAR users

Enhanced network selector to support EVM wallets

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


etherscan verification failure (when remapping points to external file)

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (bf56869 2023-07-05T00:05:02.811991000Z)
What command(s) is the bug in?
forge script
Operating System
macOS (Apple Silicon)
Describe the bug
If you use files that are outside the project through a remapping (like@remapped/=../remapped/), and a file there does a relative import, then verification fails.
Reproduction

forge init bad_verif,

Add this to the initial bad_verif/foundry.ml:

remappings =<EMAIL_ADDRESS>allow_paths = ["../remapped/"]

Create remapped/ so that you have

.
├── remapped
├── bad_verif

In remapped/, create Parent.sol:

// SPDX-License-Identifier: UNLICENSED
pragma solidity ^0.8.13;
import "./Child.sol";

and Child.sol:
// SPDX-License-Identifier: UNLICENSED
pragma solidity ^0.8.13;

In Counter.sol, add:

import<EMAIL_ADDRESS>

Deploy with --broadcast --verify

Expected
Verification works.
Actual
If you deploy and verify, you will get the following error (I tried on polygon):
Fail - Unable to verify. Solidity Compilation Error: Source "../remapped/Child.sol" not found: File not found. Searched the following locations: "".

This is because the input json contains the following:
{
   "sources":{
      "src/Counter.sol": <content of Counter.sol>
      "../remapped/Parent.sol":{
         "content":"// SPDX-License-Identifier: UNLICENSED\npragma solidity ^0.8.13;\nimport \"./Child.sol\";\n"
      },
      "/Users/ah/temp/remapped/Child.sol": <content of Child.sol>
   },
   "settings":{
      "remappings":[
<EMAIL_ADDRESS>      ],
   }
}

Suggestion
The key for Child.sol should probably use the relative path ../remapped/Child.sol instead of the absolute path /Users/ah/temp/remapped/Child.sol.

Any updates on this? It's a blocker for projects that use Node.js packages instead of git submodules.
We've bumped into this issue while deploying a new release of Sablier V2.


extent for cities?

This looks very nice! Will try it in a project soon!
I was wondering: how difficult is it to extent this for cities? So results will be land & city (if any)?

The big problem is that we have to map each relation on OpenStreetMap.
I've done manually for the countries in the osm-countries repo.

Yeah, I noticed. Great work! I looked around some time ago for a library that could go from coordinates to country (and city) name, but could not find anything close. Now you made it, thanks a lot!


How to detect merged cells?

I have a doc (a simple snippet is attached to this issue) and I'd like to detect the merged cells after row 1. Right now, I'm just doing a check if the first two cells are the same content, but that seems not ideal (based on the discussion here https://github.com/python-openxml/python-docx/issues/1311).
butt_merged.docx
What's a better way of checking for merged cells?

Identifying merged cells is not enough by itself. I think you'll find you need to identify "root" cells and "spanned" cells.
A root cell (my term) is the upper-left cell in a merge. All the other cells in the merge are spanned.
Something like this will only produce root cells. An unmerged cell can be thought of as a root-cell of its own with no spanned cells.
from typing import Iterator
from docx.table import Table, _Cell

def iter_table_cells(table: Table) -> Iterator[_Cell]:
    """Generate each "visible" cell in `table`.

    Note that not all rows will necessarily have the same number of columns and
    a row can start in a column later than the first if there is a vertical merge.
    """
    for row in table.rows:
        tr = row._tr
        for tc in tr.tc_lst:
            # -- vMerge="continue" indicates a spanned cell in a vertical merge --
            if tc.vMerge == "continue":
                continue
            # --  --
            yield _Cell(tc, row)

What about this approach -

Determine the rows and columns for the table (max value).
Iterate over an underlying row column grid in 2 passes -
(a) First pass - For every row, identify horizontally (using grid_span) and vertically (matching cell contents) merged cells.
(b) Second pass - for every horizontally merged cell, check the cell below the root cell and the cells to the right to the extent of the grid span for matching contents with the root cell. Expand this check to establish the extents of the vertical extent of the merged cell. Retain the top left coordinate of the merged cell.
create a cell map that stores the top left coordinates and cell object ids.

This should allow contents of the cells to be accessed with only the top left cell being referenced for a merged cell


Unexpected behavior of the LoaderOptionsPlugin

I'm submitting a bug report
Webpack version:
2.x
Please tell us about your environment:
OSX 10.x
Current behavior:
I'm using LoaderOptionsPlugin to pass options to postcss-loader. When using the plugin, other loaders in the chain unable to access the webpack options object and failing with TypeError: Cannot read property 'path' of undefined at Object.module.exports ([project path]/node_modules/sass-loader/index.js:227:52). It seems that this plugin overriding entire options property in the loader context with the given values.
Expected/desired behavior:
LoaderOptionsPlugin should extend webpack options in the loader context with the given options instead of overriding entire object and making webpack options unaccessible for loaders.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem along with a gist/jsbin of your webpack configuration.

Used loaders:
{
  test: /\.scss$/i,
  loaders: [
    "style-loader",
    {
      loader: "css-loader",
      query: {
        sourceMap: true,
        modules: true,
        importLoaders: 2
      }
    },
    {
      loader: "sass-loader",
      query: {
        sourceMap: true,
      }
    },
    {
      loader: "postcss-loader"
    }
  ]
}

LoaderOptionsPlugin config:
new webpack.LoaderOptionsPlugin({
  test: /\.scss$/i,
  options: {
    postcss: {
      plugins: [autoprefixer, postcssReporter({ clearMessages: true })],
      syntax: scssSyntax
    }
  }
});

Loader versions:

style-loader: 0.13.1
css-loader: 0.23.1
sass-loader: 3.2.0
postcss-loader: 0.9.1

Browser: all

Language: all

This behavior is intended. Loaders should not access the webpack options (all passed options should be explicit). The plan (for webpack 3) is to remove the default this.options in the loader context and make loaders more independent from webpack env.
The sass-loader accesses this.options.output.path, which it shouldn't do. cc @jhnns
As workaround you can still pass output.path via the LoaderOptionsPlugin.

The css-loader accesses this.options as well :tongue:
I think a loader needs access to the context from the webpack options. I don't think that it should be configurable like it is in the css-loader. It would be nicer if things just work out-of-the-box.

@jhnns I just faced this issue and need to add content: __dirname...

@MoOx I think you meant context: __dirname.

We should still allow to read from the webpack config to allow sane defaults. But I agree that it is good practice to make it overwritable.

@sokra @jhnns  - Need help!
I have been trying to use React-toolbox in my project. I have finally been able to do everything but the setup of theme.
For sass-loader in webpack V1 i had used the following code in the configuration.
sassLoader: {
data: '@import "theme/_config.scss";',
includePaths: [resolve(__dirname, './src/client')]
}.
This was working as desired and the theme was reflected.
Now for webpack V2 I understand that we are not allowed to give it this way. So I have
new webpack.LoaderOptionsPlugin({
minimize: false,
debug: false,
options: {
postcss: [ autoprefixer({ browsers: ['last 5 versions'] })],
sassLoader: {
data: '@import "theme/_config.scss";',
includePaths: [resolve(__dirname, './src/client')]
}
}})
Somehow everything compiles fine but the variable values marked in config.scss do not change the theme.
Appreciate your help. Cheers

You should apply it this way:
new webpack.LoaderOptionsPlugin({
  test: /\.scss$/,
  minimize: false,
  debug: false,
  options: {
    postcss: [ autoprefixer({ browsers: ['last 5 versions'] })],
    sassLoader: {
      data: '@import "theme/_config.scss";',
      includePaths: [resolve(__dirname, './src/client')]
    }
  }
})

@jhnns - Firstly thanks for listening to my concern. I will just share my setup so that I am clear.
Boilerplate with Webpack V2, React-hot-loader V3, React-Router V4, React-toolbox (this has theming capabilities as given in their website react-toolbox.com), Webpack-dev-middleware and webpack-hot-middleware.
With Webpack V1 and Webpack-Dev-server, hot reloading on. Themeing was working fine but with browser refresh.
With Webpack V2 and the boilerplate mentioned above, using the above code did not pick the changes marked in the theme variable  scss file. Even on browser refresh somehow the default configuration was loading with the output bundle file.
So I am not confident but I think this is not working.  Autoprefixer is working for sure but the sassLoader is not possibly.
I have solved my problem with a hack using npm scripts to actually overwrite the node_modules global file thus giving me exactly what I need but yeah it certainly is and feels a hack :).

Could you create a simple repo that demonstrates you problem? React has nothing to do with it. Just try to compile a simple scss file this way and then you'll see if the options are working as expected.

@jhnns Great News! It works. . Tested both regular scss file and react-toolbox stuff too.
I have to debug more as to why it is not working with my project with RHL3 and RR4.
Cheers!!


docs: Update step-3.md relative URL formatting

Documentation

Fix formatting for relative link

Hugo is throwing this error:
ERROR 2020/10/08 12:21:32 [en] REF_NOT_FOUND: Ref "/docs/get-started.html": "/Users/carobert/Projects/pfe-alt/docs/content/develop/step-3.md:22:37": page not found
ERROR 2020/10/08 12:21:32 [en] REF_NOT_FOUND: Ref "/docs/get-started.html": "/Users/carobert/Projects/pfe-alt/docs/content/develop/step-3.md:22:110": page not found

@mwcz or @wesruv Do either of you want to take code review on this docs update?  I updated all the URLs to use the ref syntax and fixed a bunch of 404s.


[SUGGESTION] Add option to use qb-target & qb-inventory

A good update for this script would be adding the option to also switch from ox to qb, in this case being able to select such as qb-target and qb-inventory

+1 QB-Inventory

will do


Moving Options to model package

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

/azp run java - azure-communication-networktraversal - tests

API changes have been detected in com.azure:azure-communication-networktraversal. You can review API changes here


aTLS support

I've added the CA certificate to the quote. Please notice that I still verify the certificates after I set the session.verify attribute, this is because I need to make a request to the server to retrieve a quote and the session needs to be verified by an existing CA bundle or a CA cert we specify to make a request.
This is not a problem because the session is dropped if the quote validation fails, so no requests can be made with that session anyway.
I call the disconnect() method if the validation fails before I raise an error, I do this to reset the session and to delete the client key and certs from the temp files they're stored in. However, disconnect() also destroys the runner and that may be undesirable when an attestation validation fails.


False positive for zip files

Using unzip will exit early with a false positive.

As noted above, the -P option may be used to supply a password on the command line, but at a cost in security. The  preferred  decryption  method is simply to extract normally; if a zipfile member is encrypted, unzip will prompt for the password without echoing what is typed.  unzip continues to use the same password as long as it appears  to  be  valid,  by testing a 12-byte header on each file.  The correct password will always check out against the header, but there is a 1-in-256 chance that an incorrect password will as well.  (This is a  security  feature  of  the PKWARE zipfile format; it helps prevent brute-force attacks that might otherwise gain a large speed advantage by testing only the header.)  In the case that an incorrect password  is  given  but  it passes  the header test anyway, either an incorrect CRC will be generated for the extracted data or else unzip will fail during the extraction because the ``decrypted'' bytes do not  constitute  a  valid  compressed  data stream

This can be fixed in one of several ways.

After alleged success result verify that files have been created/modified since the app started (this may not be that great of an idea do to because of Rust's SystemTime types flaws.
PREFERRED METHOD: Create a temporary directory and extract contents to that (tempdir).  Then check if the directory has files when ever a successful extraction is reported.  This feature would be much better is the temporary directory is a Virtual Disk in RAM.
Integrate unzip code directly and re-implement the decryption without the false positives
(this may not work for AES encrypted zip files depending on visibility into contents) unzip will list the file contents it possesses.  We may be able to use that to compare the resulting output.

I just finished with the command line status false positive.  And I've found unzip has implemented another false positive of empty files made of the correct file names. :man_facepalming:


Identity profile metadata input with dynamic form

It works, but could likely use style and template cleanup. Leaving as draft since I'm not sure how much more I'm going to tinker with this. I might abstract this out to a generic key/value input _field and make another for single value (will be needed for also_known_as). The hyperscript to make a generic multivaluefield is beyond me at this point.

Having 4 hardcoded fields is an option, but I went dynamic for a few reasons:

our page layout is vertically longer than Mastodon's. Have 3-4 rows of empty inputs doesn't help.
I want more than 4 links. This allows a profile page to double as a "Little Link" page.

Have you checked what happens when you send more than 4 links over to Mastodon? I just want to make sure we don't break them.

Yes, it shows them.

Neat!

This looks a little weird when it's empty and has no fields - is there a way we can start with 2 empty ones?


bugfix: #573 sticky query should enforce sticky decision timeout

feel free to ask change the name of the new API on history side: ResetMutableState

Coverage increased (+0.03%) to 67.551% when pulling 840b283c187efa5e6e72a77137d5b75de557e90e on bugfix-query into 095fbd7a0e2d5af61bb0bdf488bf24965c9ef04b on master.


Module to create Global Environments using terraform

Currently creating Global environments is missing in Terraform and customers want this feature to automate it via Terraform.
In order to create a Global Environment Via UI, we need to navigate to JFrog _Platform_UI | Admin |  Environments | Create New Environment.
https://jfrog.com/help/r/jfrog-rest-apis/environments

Closing this as it's duplicate of https://github.com/jfrog/terraform-provider-project/issues/78.


fix(MQ): do not trigger the label checks in case of label/unlabel to prevent race condition during MQ

What does this PR do?
Do not automatically launch label-analysis workflow in case of label addition/suppression. As MQ is adding labels to the PR it created a race condition with this job being relaunched and considered not ran as it's part of the mandatory jobs for the main branch rule protection

Motivation
Stability. In case of failure in these jobs they will have to be launched manually

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided. Except if the qa/skip-qa label, with required either qa/done or qa/no-code-change labels, are applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

/merge

/merge -c

/merge

/merge -p incident

/merge

/merge

/merge


Make REES citable

repo2docker's "Reproducible Execution Environment Specification" right now is a single page on the website. It's charmingly short and pragmatic, and contributes to the current state of the art in defining computing environments.
But I cannot cite it in a research paper :disappointed: !
What about a new target in the docs/Makefile that creates a nice PDF from that one page, which could be uploaded to Zenodo to get a DOI? The process could even be automated as part of the release process.
The PDF should also include the release version of r2d and a full list of repo2docker contributors, which could even go into the Zenodo record.

I'm happy to take a stab at this, if there's agreement that this would be useful :-)
Or is it preferable to have articles cite repo2docker / the Binder paper?

I think citing the Binder paper is the most pragmatic solution for now. Later when the REES contains more content we can create a DOI for it and then people can cite either both or just one depending on what they want to reference.

Since I'm going to mention REES in a paper, a new question came to mind for @betatim:
When will we know that "later when there is more content" has happened?
:wegduck:

Yes.
I reckon citing the Binder v2 paper is still the way to go ;)


MSC 1267: Interactive key verification using short authentication strings

Define a more user-friendly method of verifying device keys.
Documentation: https://docs.google.com/document/d/1SXmyjyNqClJ5bTHtwvp8tT1Db4pjlGVxfPQNdlQILqU/edit#

I've just seen this issue from the recent blog post, it may be interesting to use something similar to diceware to generate easily verifiable passphrases for comparison.

@mscbot fcp merge

Just a couple of minor things on the doc: open questions we should close and updates to the emoji that got implemented. other than that, lgtm.

I've not worked through the cryptographic aspects of this, but from the protocol POV I'm happy. Have written a couple of questions on the doc which I'd like to see answers to over the next few days.
Also there seem to be a bunch of resolved comment threads on the doc which it would be good to close if you are happy they are addressed.

Spec PR: https://github.com/matrix-org/matrix-doc/pull/2072

merged 🎉


⚠ Mobitopup has degraded performance

In b773ae8, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 5413 ms

Resolved: Mobitopup performance has improved in 51055f2.


use NFD for node labelling

By using NFD we ensure that the integration with it works as intended.
TODO:

[X] documentation
[X] clean up commits (split out removal of Clear Linux workaround)
[x] ensure that downgrade tests work - they probably don't, because the node labels prevent running the older version

@avalluri I tested manually that version skew testing still passes. This is ready for review.
@marquiz FYI, we are going to use and recommend NFD for node labeling - this has been long overdue :sweat_smile:

FYI, we are going to use and recommend NFD for node labeling - this has been long overdue

Good to get some new users onboard 👍 Especially users we're aware of 😄 Please don't hesitate to bring up any issues or wishes for improvement you might have.


docs: correct confusing filename in enableAutomock example

Summary

Current example for jest.enableAutomock() functionality uses disableAutomocking.js as the filename for the example test file:

it results confusing for the reader.
Test plan

Here you can see a screenshot of the built website after the changes:

Hi @kenrick95 & @SimenB !
After implementing the requested change, the PR is ready for review now.
Thanks

Thanks @duxtinto!


feat: support minutes:seconds format in tc

in cutechess you can specify minutes in the tc
     Play a single game between Atak and Glaurung engines with a time control
     of 40 moves in one minute and 30 seconds with one second increment:

	   $ cutechess-cli -engine name=Atak cmd=Atak32.exe dir=C:\atak
	   proto=xboard -engine cmd=glaurung proto=uci option.Threads=1 -each
	   tc=40/1:30+1

with this patch fastchess can now do that too
tested it, works 👍

wasnt entirely sure if i'd want this but i guess it will be nice, needs a documentation change too

wasnt entirely sure if i'd want this but i guess it will be nice, needs a documentation change too

ill change the man in a followup pr alongside other fixes
also i renamed the variable for less confusion


Extension: feeAmount and gasLimit are always 1 in transaction details

Actually it looks like this depends possibly on the number of commitments. When staking to 3 validators, I get 3 for feeAmount and gasLimit.


Enable versioning only for specific routes

My application runs MVC and web API within the same project. Unless I explicitly define a default version (which I don't want to) going to any route besides my API ones with versions defined results in an error due to no API version (ex. mywebsite.com/about/ results in an error while mywebsite.com/api/v1/users works as expected).
It would be useful to toggle the API versioning middleware for specific routes only.

In general, if you own both the client (UI) and server (API) side of things, you probably don't need API versioning because you have total control over everything. From the looks of things, you want to have a documentation page for your API. That's a different scenario and completely reasonable.
As you've discovered, all routes get some intrinsic, default route once API versioning is applied. This is primarily to help grandfather in existing services. There are a number of situations where a service or some other route, like a UI page, will want to opt-out of versioning.
The simplest approach to achieve this is to decorate your controller as follows:
[ApiVersionNeutral]
public class AboutController : Controller { }

This configuration is also achievable using the conventions approach.
I hope that helps.

The offered methods of opting out of versioning is a bit cumbersome. It doesn't make much sense to thread ApiVersionNeutral attributes throughout a web application when a simple route mapping would suffice. You also risk creating UI specific controllers, forgetting to add the attribute and scratching your head why mywebsite.com/about/ is throwing no version defined errors.
The current library works great for strict API projects but falls short if using it intertwined with MVC. Being able to do something like so would be incredibly powerful:
services.AddApiVersioning(options => options.EnableForRoutePrefix("api"));
Or:
services.AddApiVersioning(options => options.DisableForRoutePrefix("admin/dashboard"));

Sorry, I saw the terms MVC and Web API and that threw me off for a second. As you know, a controller is just a controller in ASP.NET Core. There is no clear way to determine if a controller is for a UI, an API, or maybe even both.
Something that seems to confuse a lot of consumers of this library is the role of routing. The API Versioning libraries do not change any part of the routing infrastructure. Things work by letting routing do what routing has always done and then the results are disambiguated by using the API version information. If things are still ambiguous, then you get a failure identical to the behavior of duplicate routes. This is why you don't see any configuration or options for API Versioning that are related to routing. Furthermore, it was an important design decision to not make developers learn a new routing mechanism; you're able to capitalize on what you already know. The closest thing to a new routing concept is the single custom route constraint, but that is only used to extract the strongly-typed API version from a URL version segment without using magic strings.
Since there is no standard or out-of-the-box mechanism to determine which controller types are UI controllers and which ones aren't, I'm not sure how this library would necessarily provide that for you. I do agree that it would be something useful to have though.
Aside from documentation, I'm not sure (nor convinced) why you would have UI and API code together, while still needing API versioning. I can't imagine that there'd ever be an unmanageable number of documentation pages that require a large number of opt-out configurations.
If you want to manage all of that configuration in a single location, then the using the conventions support is the recommended way to go:
services.AddApiVersioning( o => o.Conventions.Controller<AboutController>().IsApiVersionNeutral() );

In case you're wondering, the convention and attribute-based models can be used simultaneously. If the two overlap, the attribute model overrides any conventions.
If you still don't fancy these methods given the additional context, you can fairly easily add your own conventions via the standard IApplicationModelConvention MVC interface. For example, something like:
public class UIApiVersionNeutralConvention : IApplicationModelConvention
{
  public void Apply( ApplicationModel application )
  {
    // RendersViewsOnly is your custom extension method that determines if
    // a controller is for views only (e.g. UI)
    var uiControllers = application.Controllers.Where( c => c.RendersViewsOnly() );

    foreach ( var controller in uiControllers  )
    {
      // this is same method that API versioning uses to wire up the model under the hood
      controller.Properties[typeof(ApiVersionModel)] = ApiVersionModel.Neutral;
    }
  }
}

Hopefully this helps clarify the challenge with identifying UI-based controllers. To my knowledge, there is not a base class, attribute, or other out-of-the-box method that would allow API Versioning to add a filtering capability in a straight forward manner. This division can be done many, many different ways in a project; potentially without any convention or method to the organization.
If we, or anyone else out there, has a suggestion on how this can be done, I'm open to entertaining the idea. However, if it can't be achieved without using an attribute, interface, or base class, then I don't see how it's any better than just applying the ApiVersionNeutralAttribute or defining a convention configuration for the target controller.

Circling back around to revisit this issue.  I don't want to get into the business of changing or otherwise enhancing the routing infrastructure. It's one of the API versioning prime directives to not make you learn a new way of routing.
All that said, your requirement is still valid.  API version neutrality should be inheritable, which would simplify these types of scenarios and meet your needs. However, I noticed that the ApiVersionNeutralAttribute is not currently inherited.  This is a mistake. I've filed #93 to specifically track this issue. The fix is simple and will arrive in the forthcoming 1.1.0 milestone release.
If you don't want to wait, you can get implement your own solution today.  You just need an attribute that implements the marker interface (which is what the code really cares about).
[AttributeUsage( AttributeTargets.Class, AllowMultiple = false, Inherited = true )]
public sealed class NotVersionedAttribute : Attribute, IApiVersionNeutral { }

[NotVersioned]
public abstract class UIController : Controller { }

[Route( "[controller]" )]
public class AboutController : UIController { /* omitted */ }

Once the fix is publicly available, you can swap out [NotVersioned] with [ApiVersionNeutral] and delete your custom attribute - if you want. Things will continue to work if you keep your custom attribute.
I hope that gets you closer to your goal.

Issue #94 provides a long-term, permanent solution and an alternate solution is provided here; therefore, I'm closing this issue out. Feel free to re-open or create a new issue if you have additional thoughts. Thanks for the in-depth feedback.


OperationalInsights: DataCollectorLogs new api support.

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

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

[x] 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

Can one of the admins verify this patch?

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

Hi @MyronFanQiu, feel free to review.

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

Hi @MyronFanQiu,
Hi, error response have been added, all comments are resolved and all validations have passed.
feel free to review, thanks.

@Dudi119 We need ARM's review as well.

/azp run automation - sdk

/azp run automation - sdk

please also add a GET "/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/workspaces/{workspaceName}/dataCollectorLogs/{tableName}

SIgning off conditionally assuming the point GET will not be a big deal to add.

@Dudi119 Hi. Could you please fix one lint error about the delete operation?

@MyronFanQiu, sure, i will review it, i also need to add another point get so a few more things to add.

/azp run automation - sdk

@MyronFanQiu, our Delete only returns 200 with no content, we do not supply 204.


Label 回调值始终为空

There is OK that there can be nil. That's for "empty" views.
Try the following code:
struct ContentView :  View {
    @State var source = (1...1000).map{ $0 }
    @State var selection = 1

    var body: some View {
        FiniteWheelPicker(selection: $selection, items: source) {
            if let item = $0 {
                Text("\(item)")
            } else {
                Text(verbatim:" ")
            }
        }
        .frame(maxWidth: .infinity)
    }
}


Move gltf to a module for future proposals.

Support for proposal https://github.com/godotengine/godot-proposals/issues/885
The goal of this pr is to try to make my work in progress https://github.com/godot-extended-libraries/gltf mergable. Also, this is how the new FBX importer works, so having the gltf2 importer be a module makes sense. The gltf2 doesn't have any internal dependencies so it can be moved out.
Thoughts on moving the collada and the escn importers out too?

I'm not sure I see much point in doing this. But let's see what @reduz thinks about it.

I can make a PR and move collada to a module too if you want @akien-mga we could do them all?

You should see with @reduz what he thinks of the proposal first.

Since there has been no movement, I'll work on implementing the whole proposal https://github.com/godotengine/godot/pull/34193. I was hoping this would be an easier merge.


Can't login on chrome brower and firefox brower. (safari is OK).

Expected behavior:
Actual behavior:
Steps to reproduce:
Screenshots (if applicable):
OS and Browser:
Mac OS X 10.12.6 - Safari - Chrome - Firefox

Dear all
I have a problem. I build hospitalrun-frontend on Ubuntu server.
I login from another computer with Safari is Ok. So, Login on Chrome or Firefox is not Ok.
I included content="chorme=1" on index.html file.
Could you help me?

I had a similar problem. It occurred because I didn't allow history on Firefox.
So if you use private browsing it seems that the script "vendor.js" from /dist/assets doesn't work as it should.
As I'm new on github I'm not sure whether it works.
I hope that this works and that I understood the question correctly.

Dear Primedi
I run chrome with incognito mode and Firefox with private mode but not OK.
So, I'm new on coder and fresh Emberjs.
Thanks,

Dear tamdaovssc,
maybe it is not OK because you run chrome with incognito mode and firefox with private mode.
If you get the "Loading"-preview try the inspector (on firefox) and try to figure out whether there is a failure that says "[...] maybe you run in a private mode". If there is a similar content, try to run e.g. firefox not with private mode to see, if thats ok.
If there's not, you please try to find the error and share it with us, so we can work to fix it.
Every error-text can be helpful as it gives us a hint where the problem may be.
Hope that helped a little.
Kindest regards

The system is really designed to run on Chrome. In general, it should work on Firefox, but there are some pieces that we're aware don't work on Safari (or at least some features on some versions of Safari). I'm unable to reproduce this. @tamdaovssc can you provide more detail?

Dear Tangollama
Run in Chrome and Firefox on localhost is OK. But, login from another PC (same LAN) it's not OK.
It run "no security" mode.
I used Ember Inspector and checking error.

Thanks,

Dear all
I check security issue for ember on link: https://github.com/ember-cli/ember-cli/issues/5123
I run ember s --host my IP.
It had only error: Error registering service worker:SecurityError: Only secure origins are allowed (see: https://goo.gl/Y0ZkNV).
(anonymous) @ (index):42
Promise rejected (async)
(anonymous) @ (index):41
Thanks

@tamdaovssc Can you post the full ember s command that you are using? Eg:
ember s --proxy website

I assume you're using
ember s --proxy http://<IP_ADDRESS>:49152
Have you also tried
ember s --proxy https://<IP_ADDRESS>:49152
?

Dear tchan
It is not fix.
Thanks and Regards,

@tamdaovssc Can you post the exact commands you've tried?

Dear tchan
I ran commands:
ember s --proxy http://<IP_ADDRESS>:49152

1.Kill the Chrome Process from Task manager – Open Task Manager and Kill Every process of Google Chrome.
2. Reboot Your Computer and check again.
3. If your computer has another user account then log on to that account and check whether it is working or not, if chrome is working on another user account then first user account got affected, If it doesn’t work on any user account then chrome got affected for all users.

Can be reproduced on Linux with docker, build and start docker containers. Check it works using localhost:4200 then find ip-address of container  docker container inspect hospitalrun-frontend and connect to ipaddress:4200 . You cannot get past the login screen, likely reason is security rules in Chrome that allow ws:// connections only to secured site or localhost and the docker container, or stand-alone install, have no ssl-cert at the moment.

Can repro by running HR+ in a VM and attempting to open it up in the host, with VM'sIP:port.
A "fix" for Chrome:
chrome.exe --unsafely-treat-insecure-origin-as-secure="http://HRIP:PORT"
Where HRIP is the IP address at which the HospitalRun server is located, and PORT is the port at which it listens.
Aside from this you may want to specify a custom --user-data-dir=DATADIR param, so that it keeps user data separate from your main browser's. For Linux that would look like --user-data-dir=/home/user/hrchrome, for Windows maybe something like --user-data-dir=C:\hrchrome.
May want to create something like a new shortcut to chrome.exe (on Windows) with the parameters above preset, so you can spawn it with one click. For Linux you can save the chrome invocation line to a shell script and run that.

@tamdaovssc did @BogdanAlexandru's recommendation address your issue? If so, can you close this.


[SPARK-49332][FOLLOWUP] Fix worker parameter to match with master service

What changes were proposed in this pull request?
This is a follow-up of the following to fix worker parameter accordingly to match with master service.

#83

Why are the changes needed?
This was missed when the original PR changes the master service name.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs and manually check.
Was this patch authored or co-authored using generative AI tooling?
No.

It seems that the newly added e2e test introduces a flakiness due to the image downloading.
Error from server (BadRequest): container "spark-kubernetes-driver" in pod "pyspark-3-5-2-0-driver" is waiting to start: trying and failing to pull image
    l.go:52: | 17:58:10 | spark-operator-python-validation | verify-common-created-resources | CMD       | ERROR |

Since K8s 1.31 passed, let me merge this. Thank you, @viirya !


Clicking on the link for the command 'Set-DLPComplianceRuleV2' redirects to the page for 'Set-DLPComplianceRule'

Reporting two issues :

Clicking on the link for the command 'Set-DLPComplianceRuleV2' redirects to the page for 'Set-DLPComplianceRule'.

This page is missing parameters like 'ExceptIfSentTo' for the command Set-DlpComplianceRule.

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

ID: e7d3411c-d81f-667b-84d1-6148291f4923
Version Independent ID: 5da6c19a-ecf7-7cc1-c120-119b12735303
Content: Set-DlpComplianceRule (exchange)
Content Source: exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpComplianceRule.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@dariomws306  Thank you very much for the contribution and updating the documentation with PR. @student-forever Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Add feature gate to support multiple sizes huge pages

As part of the telco effort, we should provide the possibility,
to use multiple sizes huge pages under the node.
Kubernetes supports this feature as alpha under the 1.18, to enable it
you should enable feature gate HugePageStorageMediumSize,
see https://github.com/kubernetes/kubernetes/pull/84051.
Signed-off-by: Artyom Lukianov<EMAIL_ADDRESS>

Hi, can anybody please take a look? It seems this is ready to go, just a review is missing.

/assign @knobunc

Thanks for review, I do not want to prevent the upgrade of the OpenShift, it the main reason why I added it under the LatencySensitive feature set, similar to the topology manager one.

The PR does not relevant anymore, working on promotion of the feature from alpha to beta.


chore: fix minor typos in passed props to GeneralInformation

Description
Fixes some minor typos; some components were accidentally mixed up with each other when passed into <GeneralInformation />
Type of change
What is it?

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] I run npm run lint:js:fix to check that my code is properly formatted

(Marking as WIP, before this gets merged by accident) This causes a slight UI regression in how things are ordered so I'm working on fixing that


Add conference ranking

Could it be useful to have the conference ranking along with the rest of the information?
Source can be found here:
http://portal.core.edu.au/conf-ranks/?search=&by=all&source=CORE2018&sort=atitle&page=1

Might be too much information :)


nuxt generate + i18n + dynamics routes

Hi guys, i hope you can help with an issue. I'm really enthusiastic about your project so I decided to do my latest project with Nuxtjs + i18n and dynamics routes.
I started from i18n example and added dynamics routes imported from a json following this example. My page folder is setted like this:

Right now i'm a little bit confused about how to generate a static package to host in a web hosting. How can I generate dynamically all the routes from the json files and how I should to manage _lang routes?
Thank you

With many languages site, you can use Layout to change without changing URL. But If you want to change URL, I think you consider Vue Router with Router Modules for Nuxtjs

I have solved with a list of all routes :worried:

@nicoladl Have you looked at the generate function? This way you can do an API call and return all necessary routes. See: https://nuxtjs.org/api/configuration-generate/