SOLR-15557 Script to generate refguide page .htaccess redirects

https://issues.apache.org/jira/browse/SOLR-15557
See https://github.com/apache/solr-site/pull/70 for the output of this script given the input files as of today
I added the output to this PR so it is easier to iterate in one PR and make review comments on the htaccess.txt directly. For every edit you make, please run this command before committing.
python3 gen-refguide-redirects.py --old old-guide.txt --new new-guide.txt --mapping mappings.csv --htaccess >htaccess.txt

I think you deleted the script  in your last commit...

I think you deleted the script in your last commit...

Yea, moved it into the folder, but forgot to git add it :) Now it's back

Did a bunch of 8_11 mappings, now there are only 25 pages left without a mapping. Some should point to landing pages which still does not exist in the new guide I think.

Now tested this on a real httpd server, with a new guide/.htaccess. Made adjustments to the rules based on that (Anchor with ^ and use relative names).

Separate htaccess did not play out as intended. Going back to using top-level one. Also merged the sub-path renames into larger regex lines, and separated 8_11 guide redirects into its own section.


[Bug Report] why new version（2.4.11）removed field url in el-upload “on-change” hook?

Element UI version
2.4.11
OS/Browsers version
Chrome  71.0.3578.80
Vue version
2.5.21
Reproduction Link
https://jsfiddle.net/gqxv53pr/1/
Steps to reproduce
1.change a local image ,
2.see the console of on-change hook,
3.the file didnt contain filed 'url',
4,change the version form 2.4.11 to 2.3.9,then repeat the above step，you can see the on-change file contain 'url' filed.
i have checked the releases logs,but there is nothing about this. i know i can use URL.createObjectURL(file.raw) ,but it's really not a good experience for me!
can you guys explain why remove 'url' filed in file when on-change happen?
What is Expected?
'url' filed can be finded in file
What is actually happening?
file params dont contanin url field

Yeah, this is a big problem for our project too. So we just can use old version.

Duplicate of #12934


Add an option to filter PR search by passing/failing/running CI checks

When a project has many open pull requests, just finding one which is ready for review can be tricky.  For example, pytest and matplotlib would both find this useful, along with smaller projects.  Terrible mockup:

I know I'd love to be able to filter down to just the PRs with passing tests to review, or tests+approval to merge, or ...  You get the idea.  No idea why this doesn't already exist, so Refined Github seemed the place to suggest it 😄

Is this something you can search GitHub for?

Is this something you can search GitHub for?

Yep. It's not even in the help pages or the search page, but it's been there for almost 4 years:
https://github.blog/2015-06-02-filter-pull-requests-by-status/
Demo passing: https://github.com/sindresorhus/refined-github/pulls?utf8=✓&q=is%3Apr+is%3Aopen+sort%3Aupdated-desc+status%3Asuccess

It's great that the feature exists.
I wonder why this is not documented on https://docs.github.com/en/github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests

It's currently in the docs, for anyone who stumbles across this.
https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests#search-by-commit-status


How many epochs are used to train the PruningNet(MobileNetv2) from scratch?

Rt.

64 epochs. The default epochs in the codes are the number of epochs I used in the experiment.


feat(sdf): Protect Admin Routes behind a new Administer role

We have an admin page controlled by a feature flag. We locked the API endpoints down to be those with systeminit.com emails, but we want to take advantage of spicedb to make this work correctly
Even if a user gets to the WorkspaceAdmin page, we have locked down all of the API endpoints for them based on a new role in spicedb
This role will be manually granted and can be done so using the following Zed cli command:
zed relationship create system:system admin administer:<user_pk>

This will be granted by TechOps on the SystemInitiative users that need access to it so that it can be tracked correctly

ok after talking this over with @sprutton1 and @britmyerss we are going to do the following:

For local installations of SI, we are going to use a wildcard that anyone on a local instance against a LOCAL spicedb will be an admin
For production system, we are going to add the work to the admin page to be able to make someone an admin

this is going to require us to manually seed a user in production and then that user (more than likely Scott / John) will then invite the SI team to be admins where appropriate
We will get an audit log event when a user is added / removed from the spicedb definition


chore(build): dev wheel versions on edge builds

These get uploaded to test pypi (where they are by and large never
downloaded, but it allows us to dry-run uploads to production pypi).
Test pypi doesn't allow you to reuse filenames, just like real pypi, and
each edge build in the same version will have the same wheel filename.
In the past, we overcame this by allowing the test pypi upload to fail,
but then... that doesn't really test anything.
Luckily, PEP4401 which defines python versioning conventions, allows a
.devN tag to be at the end of versions, with the intent being that the N
is a build number. So this pr adds the capability to specify a
BUILD_NUMBER= environment variable - which travis edge builds now do -
which will get added to
- the wheel filenames
- the actual versions encoded in the wheel metadata
- the required version for opentrons_shared_data in opentrons
and thus allow us to upload to pypi on every edge build.
Testing

Do a make clean wheel  in the python projects and make sure there's no .dev tag
Do BUILD_NUMBER=4 make clean wheel in python projects and make sure there is a .dev tag
Check on the build for the temp commit and make sure it uploaded something to test.pypi (https://test.pypi.org/project/opentrons/ and https://test.pypi.org/project/opentrons-shared-data/)

When will this be not a draft

When the upload succeeds and I can revert the temp commit

Successful build before reverting the deploy-on-any-branch commit: https://travis-ci.com/github/Opentrons/opentrons/builds/170579127
You can see opentrons-shared-data dev build here: https://test.pypi.org/project/opentrons-shared-data/#history
You can see opentrons dev build here: https://test.pypi.org/project/opentrons/#history


"uglifyjs-webpack-plugin": "^1.2.5"  cant't Protect the variables not to be compressed

excuse me,
i want to protect some variables not to be compressed,
so ，I did a bit of configuration

but,it seems does't work,  there's the following error

can you give me some advice?thanks.

@silence-may it is not QA service, also we just wrapper around uglify-es, please read their documentation or create issue there https://github.com/mishoo/UglifyJS2/tree/harmony. Thanks!


As an inspector, I want to store record_keeping options in fertiscan

Description
Context
We need to implement a new labelling option field as discussed with the main user. The field will provide two options: record keeping (tenue de document) and no record keeping. Record keeping refers to a legal practice where the manufacturer chooses not to disclose publicly the list of active ingredients. Instead, the label will indicate: "Active ingredients derived from registered and exempt materials". If record keeping is not chosen, the active ingredients will be listed on the label as usual.
Problem Statement
The datastore currently does not support a way to track or store the labelling option for record keeping. This feature needs to be added to the system, ensuring that it is properly stored. The developer should assess how this change impacts the database schema, determine the necessary adjustments and propose updates to the inspection data format.
Acceptance Criteria

A labelling option for record keeping and no record keeping must be added to the datastore.
The information must be stored correctly during creation and update, ensuring proper retrieval.
Investigate whether the database schema requires updates based on the new labelling option.
propose updates to the inspection data format

Additional Information

ref: https://github.com/ai-cfia/fertiscan-pipeline/issues/28
Example of legal record keeping PDF: Tenue de documentation.PDF
Additional info: https://inspection.canada.ca/en/plant-health/fertilizers/trade-memoranda/t-4-131
post update to the inspection data format here: https://github.com/ai-cfia/fertiscan-frontend/issues/229

This issue is too vague and we need to sit down and really think how we plan on retrieving this kind of data with the Backend and how we want to return it.

This issue is too vague and we need to sit down and really think how we plan on retrieving this kind of data with the Backend and how we want to return it.

Updated. Please concert with @Youllou on the inspection data format.

can the new data format be included in the Issue? @k-allagbe @Youllou.
Also, do we pick in the pipeline if it is a record keeping case?
If not, I advise we wait until all the changes picked from the pipeline are implemented before implementing these changes to avoid conflicts and problems.

Also this is not a as a dev issue since these changes are part of a user's need. @k-allagbe Can we make an Epic with all the requiered documentation to implement the changes?

Do we pick in the pipeline if it is a record keeping case? If not, I advise we wait until all the changes picked from the pipeline are implemented before implementing these changes to avoid conflicts and problems.

Please, have a chat with @snakedye and @Endlessflow. A discussion in teams would be great.

Also this is not a as a dev issue since these changes are part of a user's need. @k-allagbe Can we make an Epic with all the requiered documentation to implement the changes?

Done. If some are missing, please feel free to update the epic.

I've currently halted the work for the 📦 fertiscan.metadata.inspection.build_inspection_import() and asked the team how we should proceed regarding displaying the content of the fertilizer if it is a record_keeping label
        # Get the guaranteed analysis
        if product_info.record_keeping != True:
            guaranteed_analysis = nutrients.get_guaranteed_analysis_json(
                cursor, label_info_id
            )
        else:
            print("Record keeping is true")
            raise BuildInspectionExportError("Record keeping is true")
        guaranteed_analysis = GuaranteedAnalysis.model_validate(guaranteed_analysis)


Added New Footer Style [fixes #33]

Added new Footer Style
Used HTML, CSS and JavaScript
Added Social media links
Added new Footer Navbar
Added Arrow which takes to top of page

CodeFactor found an issue: Unexpected duplicate "padding" (declaration-block-no-duplicate-properties)
It's currently on:
style\style.css:330
Commit 2c2dbb38ec9f7006db9212f1d077ec22836cc5d1


Should have visual regression testing

All changes should be visual regression tested to ensure quality. It should be automated, and should run as part of the current PR testing process.
The framework was added in #1241. Examples just need to be added and tested. This should probably be broken up into multiple issues and most used components prioritized.

This should probably be broken up.

We should start with these when we work on this issue:

[] Combobox / Lookups / Picklist
[] Data Tables
[] Icons
[] Input
[] Menus
[] Page Headers
[] Tooltips
[] Trees

Theoretically: if we have the ability to automatically validate that our markup matches what is specified in SLDS, do we need visual regression testing?  I ask because visual regression testing is slow, fragile, and complicated... and to keep a high quality developer experience in my opinion we should avoid it unless we absolutely need it.

The most recent backstory on this is with that stories were manually checked with the CSS -- to _ BEM modifier change and VerticalNav broke and VRT would have blocked me from releasing that broke.
One option (which is similar to what SLDS does and is close to how a 3rd party VRT would work) is that the code review person would generate the snapshot image before code commits and after code commits and do a compare to better enable their code review.
Large codebase changes and side effects (one component changes another) are the primary issues we are trying to highlight here.

Closing with #1987 merged in and #2098 highlighting which components are missing from tests


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

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

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

Questions ?
Please refer to the Backport tool documentation


onBrokenLinks throw errors when linking to an external static html page

Edit from @slorber: the bug/repro is about a static/my-route/index.html resource and navbar item linking to it with a target:
        {
          href: '/my-route',
          label: 'My Route',
          prependBaseUrlToHref: true,
          target: '_blank',
          position: 'left',
        },

Links with a target: "_blank" should not be checked because they are unlikely to be internal SPA links.
Description
After upgrading from 3.0.1 to 3.1.0, the onBrokenLinks feature throw exception on static routes while it was not the case before.
Reproducible demo
https://stackblitz.com/edit/github-fausgf
Here is a fork of the repro project but using 3.0.1 without errors: https://stackblitz.com/edit/github-fausgf-qpa5vb
Steps to reproduce

Create a new Docusaurus project
Create a simple index.html file inside a subfolder in static directory
In the Docusaurus config, add a NavBar item to link to this static html page
Try to do a production build using npm run build
Observe thrown errors during server compilation

Expected behavior
Does not throw errors for static page links (like in 3.0.1)
Actual behavior
Throw errors for static page links
Your environment

Public source code: None
Public site URL: None
Docusaurus version used:3.1.0
Environment name and version:Node 18.17
Operating system and version:MacOS 14.2.1 and Unbuntu 22.01

Self-service

[ ] I'd be willing to fix this bug myself.

Thanks for reporting, I see where the issue is coming from, we'll fix it 👍
In the meantime, you can use this on your navbar item: 'data-noBrokenLinkCheck': true,

Just to add that now we're moving to 3.1 we've noticed a similar thing.  We have three different docs sources in our site and linking from one to another throws the warnings (was fine in 3.0.1 and earlier).

@andrewgbell is your link having target: "_blank" too?
Because it wasn't mentioned in the original issue, but it's what matters to me here.
If the link is always opened with such target, then we never navigate through a "soft/SPA navigation" and it's always a full page reload, so it doesn't make sense to check for broken links for such links with targets.
If your link does not have a target, please share another repro so that I understand the case better

@andrewgbell is your link having target: "_blank" too?
Because it wasn't mentioned in the original issue, but it's what matters to me here.
If the link is always opened with such target, then we never navigate through a "soft/SPA navigation" and it's always a full page reload, so it doesn't make sense to check for broken links for such links with targets.
If your link does not have a target, please share another repro so that I understand the case better

No, we don't have that.  The repo is private, however I can grant you access if that works for you?

@andrewgbell even if the repo is private, what prevents you from creating a smaller repro where I can clearly see which topology of link gets reported?
Giving me access to your repo is fine, but if I need to spend 2 hours figuring out a complex setup and identifying which link exactly we are talking about, I'm less likely to solve the problem.

This seems to have been resolved now by two things.  1, running the latest canary, 2, then adding a trailing slash after support below in docusaurus.config.js from
             to: "/support",
to
             to: "/support/",
(it wasn't needed in earlier versions, but maybe we were just lucky):
`   footer: {
  style: "dark",
  links: [
    {
      title: "Docs",
      items: [
        {
          label: "label1",
          to: "/label1/1/",
        },
        {
          label: "label2",
          to: "/label2/2/",
        },
        {
          label: "Support",
          to: "/support/",
        },
      ],
    }

,`

@andrewgbell I see where this might come from, but that would help to have a runnable repro to be sure we are talking about the same thing. Not seeing things such as your trailingSlash config and documents creates an ambiguity, and I won't be sure to solve exactly the problem you encounter

@andrewgbell

This seems to have been resolved now by two things.

Great, but unfortunately I don't even know what the issue is in the first place.

1, running the latest canary, 2, then adding a trailing slash after support below in docusaurus.config.js from /support to /support

I see where this trailing slash problem might come from.
But that would help to have a runnable repro to be sure we are talking about the same thing. Not seeing things such as your trailingSlash config and md docs creates an ambiguity, and I won't be sure to solve exactly the problem you encounter.

So TLDR:

I still don't know what the original issue is about

It's possible that my perf optimizations introduced a regression

These are 2 separate issues that both need to be solved. Can you please create a smaller repro detailing both? (I have no idea for 1, and only have a guess for 2)

Going to close this issue as part of https://github.com/facebook/docusaurus/pull/9788

@andrewgbell I'm not able to understand case 2 either, so if there is a problem I don't see, please open another issue with a repro.

The 2nd case (trailing slash url being reported) will probably be fixed in https://github.com/facebook/docusaurus/pull/9791

I'm getting this issue when I add html files to static.
Currently, I have a static html file known as playground.html.
If I try to access playground.html, directly using the URL bar, it loads up fine, but any links I create to it in the docs not only show up as broken while compiling, they also redirect the user to the 404 page, if the user clicks the links instead of opening them manually in the URL bar.

A temporary workaround is to add the aformentioned target: '_blank'


Query abstraction and initial work on one-to-one relationships

Query building is now the providence of the QueryBuilder implementations, no longer of the session. The session should be primarily for communicating with the dialects and underlying datastores.
Zero query building operations require an actual session. This is primarily because we want to support multiple sessions in the same environment, so that we can chat with multiple datastores at once. This means that we explicitly pass around model definitions a lot. This has the added advantage that the session does not get passed around. Seems a bit cleaner that way. The session should know about the domain, but not the other way around.
The basics for one-to-one relationships are now roughly in. Relationships can be eagerly loaded, but the default is lazy.

Coverage increased (+2.7%) to 86.424% when pulling 2321a392832f3ad3dfb803fd23f6dff67942a3eb on thomas-p-wilson:enhancement/query-abstraction into c7c4f38c1890f2b0be2927bef1ac78d55e366b5d on one-orm:master.


Add hosts to the inventory card

Pull Request Test Coverage Report for Build 1021

7 of 8 (87.5%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.06%) to 87.35%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/components/ClusterOverview/Inventory/utils.js
2
3
66.67%

Totals

Change from base Build 1010:
0.06%

Covered Lines:
3077

Relevant Lines:
3371

💛  - Coveralls

merging, there are TODOs, but they are not blocking since the inventory will just show number of hosts and ok statuses for all of them. Other statuses like Error/Warn/InProgress will be implemented in the future. Maybe in https://github.com/kubevirt/web-ui-components/pull/293?