[FEATURE] [Add Multi-Language Support for Global Accessibility]

Is your feature request related to a problem? Please describe.
Implement multi-language support , allowing users from different regions to interact with the website in their preferred language. This feature will enhance accessibility and usability, making it easier for non-English-speaking users to browse the site.
Describe the solution you'd like
Set up a language selection dropdown or toggle in the header/footer for easy switching.
Store language preferences using cookies or local storage.
Ensure that the translated content adapts dynamically based on the selected language.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
please assign this to me under gssoc-ext and hacktoberfest

@sezallagwal  what would be the complexity to implement it ?

@AshuKr22 im planning to use google translator


Documentation

Do you have a strategy for adding documentation? Are you planing on using a specific system like JSDoc, or just some basic markdown, or the Github Wiki? I would be happy to help with anything.
The code is fairly clear to read and see the options, but I think some basic documentation would really help people get started with this project.

The ongoing work is at https://github.com/posva/vue-mdc.js.org
I have been undergoing under too many things for a couple of months and haven't been able to set out the foundation yet... I'll do my best to get the foundation ready asap so people like you can help
integrating mdc with vue is actually quite easy, but I really struggle to find the moment to finish the foundation of docs so people can easily contribute :(


Error from 0001_retrieve-secrets

One of our users is getting this error when pushing their app.
2020-03-13T13:51:13.26-0500 [APP/PROC/WEB/0] OUT [cyberark-conjur-buildpack]: retrieving & injecting secrets
2020-03-13T13:51:13.26-0500 [APP/PROC/WEB/0] OUT ~ ~
2020-03-13T13:51:13.43-0500 [APP/PROC/WEB/0] ERR .profile.d/0001_retrieve-secrets.sh: line 44: export: `security.config.user.name=': not a valid identifier
2020-03-13T13:51:13.43-0500 [APP/PROC/WEB/0] ERR .profile.d/0001_retrieve-secrets.sh: Error on line 44
2020-03-13T13:51:13.45-0500 [APP/PROC/WEB/0] OUT Exit status 1
2020-03-13T13:51:13.45-0500 [CELL/SSHD/0] OUT Exit status 0
This is the matching line from their secrets.yml, where all of their entries follow the same format:
security.config.user.name: !var QA-CyberArkVault/PCF/DAP_PCF_RITM0283092/security_config_username/password

The first ERR line had the actual value in the output and I tried to redact it in the copy/paste, but my redaction didn't show through.

I had the user change their secrets.yml to use underscores instead of periods in the env var names, and that solved their problem.

@cbarga thanks for reporting this! I'm sorry for the long delay before you received a response.
It looks like you are right, that we don't allow periods in the environment variable names. I know some systems support this, but it looks like our buildpack leverages the bash export method to set the variable names. The export method fails if the supplied name is not a valid shell variable name.
I've added an update to the README to hopefully make this clearer for other users in #65 - I'm glad you were able to figure this out, but I regret that you had to!
Since this issue appears to be resolved for you, I'll close this issue now.

this is a huge limiting factor. There is 2 issues with this method:

the obvious cant use dots in variable names
when you are viewing environment variables from PCF console you cant see these specified there, even for troubleshooting
when you ssh into the container you still cant see them in the env variable, unlike every other variable being set with manifest.yml

how have people solved these cases? the buiildpack also doesn't fail on a push of an app when it CANT retrieve the credentials, so again left in the dark as to whether this worked or not at all. see https://github.com/cyberark/cloudfoundry-conjur-buildpack/issues/81

@mkkeffeler the environment variables set by this buildpack are only loaded into the runtime process, which is consistent also with how the Summon project injects environment variables. We believe it is better for the security of these secret values that they are not exposed in the app manager UI or when you run cf env.
The variables that are being set are intended to have limited visibility; they are visible to the app that needs them, but not to any end users trying to access them.
If you want to validate the secrets.yml syntax or verify that the variables can be retrieved, you have some options. If you have a user that can access the variables, you can try to retrieve them by invoking summon and pointing it at the correct secrets.yml file:
summon -f /path/to/secrets.yml bash -c "printenv"

If you want to verify that a specific app deployed to TAS / connected to the Conjur service broker will have the correct access, you can log in via the CLI with a user with appropriate privileges and query:
conjur resource permitted_roles path/to/variable read
conjur resource permitted_roles path/to/variable execute

If the app is appropriately privileged, you should expect to see their host identity listed in the responses from the two requests above. The app identity is of the form {TAS policy branch}/{org guid}/{space guid}/{binding id} if using app-scoped identities and {TAS policy branch}/{org guid}/{space guid} if using space-scoped identities, where:

TAS policy branch is defined in the tile configuration
Org GUID can be determined by running cf org ORG_NAME --guid for the ORG_NAME where the app lives
Space GUID can be determined by running cf space SPACE_NAME --guid for the SPACE_NAME where the app lives
Binding ID (if used) will show in VCAP_SERVICES

I hope this helps. It sounds like filing the issue #81 was the right call - we'll look into that shortly.


Efficient computation

Possible enhancements for the computations in decrease order of development time:

JAX
Numba
Cython
C or C++ bindings

We might want to consider such possibilities after the original code optimised. Code optimisation entails documentation of the time and space complexity for method. Following, we can start considering which possibility to choose.

I close this issue due to the followings

JAX, Numba, or Cython are not prefered as we use Pytorch for the RL part.
C or C++ bindings will probably be required once we want to use Tentris.
Writing documentation pertaining to the time and space complexity for each model seems to be good idea but also a hindrance to efficient software development.


Handling "not found" and other IOExceptions differently in ParseableURL

Hi.
Recently I got some weird bugs because a web server that distributes configuration over parts of my system went crazy and kept responding 503 to some urls used in "include" statements in the system configuration. Corresponding exceptions were silently ignored and we ended up with the system running on default settings.
It seems to me that errors which are essentially a "missing file" error, should be treated as they are now, but other types of IOExceptions should attract some user attention, because they are most probably an evidence of broken environment.
Here is a patch for ParseableURL that do it.
Thanks for this awesome library,
Pavel.

@lemmsh note that this patch won't apply cleanly anymore. could you rebase it?

Rebased as #273


minikerberos 0.2.0 has requirement asn1crypto>=1.3.0, but you'll have asn1crypto 0.24.0 which is incompatible.

root@kali:~/scripts# pip3 install pypykatz
Collecting pypykatz
Downloading https://files.pythonhosted.org/packages/69/1a/61511c8ad262064bf0c0e022c5a5a936dce8b7f0e48a8e2ec42b8e0ced3a/pypykatz-0.3.6-py3-none-any.whl (276kB)
100% |████████████████████████████████| 276kB 3.7MB/s
Collecting msldap>=0.2.7 (from pypykatz)
Downloading https://files.pythonhosted.org/packages/2c/d2/280e6d6ece46fdb6393dee3470ef6f4973bb50b2a32559a33c859cc48b13/msldap-0.2.8-py3-none-any.whl (127kB)
100% |████████████████████████████████| 133kB 8.6MB/s
Collecting minidump>=0.0.12 (from pypykatz)
Downloading https://files.pythonhosted.org/packages/5e/75/a8f5a59beb8a049fdf9e9af1c9cf4b99bcb25a970bbe46fc9592f1865b96/minidump-0.0.12-py3-none-any.whl (64kB)
100% |████████████████████████████████| 71kB 13.0MB/s
Collecting winsspi>=0.0.3 (from pypykatz)
Downloading https://files.pythonhosted.org/packages/28/3e/6225f5cf793492a4abb9587fe2971d5dd768fbe2a7ba33b001c75888f0bd/winsspi-0.0.5-py3-none-any.whl
Collecting minikerberos>=0.2.0 (from pypykatz)
Downloading https://files.pythonhosted.org/packages/ca/24/f814f4f31fcad73865880397bb3db97813ba07d38a5e86b38df183ad478b/minikerberos-0.2.0-py3-none-any.whl (101kB)
100% |████████████████████████████████| 102kB 10.5MB/s
Collecting aiowinreg>=0.0.2 (from pypykatz)
Downloading https://files.pythonhosted.org/packages/59/25/31cd1c57c8322e1e88d246d923bb00a88e326722c238b3a466d411d73fd4/aiowinreg-0.0.2-py3-none-any.whl
Requirement already satisfied: asn1crypto in /usr/lib/python3/dist-packages (from msldap>=0.2.7->pypykatz) (0.24.0)
Collecting asciitree (from msldap>=0.2.7->pypykatz)
Downloading https://files.pythonhosted.org/packages/2d/6a/885bc91484e1aa8f618f6f0228d76d0e67000b0fdd6090673b777e311913/asciitree-0.3.3.tar.gz
Collecting aiocmd (from msldap>=0.2.7->pypykatz)
Downloading https://files.pythonhosted.org/packages/a7/d7/1237391649ab4d86a6d5520361727e938b4ec47df834e688189dd83642bf/aiocmd-0.1.2-py3-none-any.whl
Collecting winacl>=0.0.2 (from msldap>=0.2.7->pypykatz)
Downloading https://files.pythonhosted.org/packages/a7/5e/62e8d5e9987e2c4ae46dd32eea3ede36eadb82c04892ffeb73659fca2068/winacl-0.0.2-py3-none-any.whl (42kB)
100% |████████████████████████████████| 51kB 15.4MB/s
Collecting asysocks (from msldap>=0.2.7->pypykatz)
Downloading https://files.pythonhosted.org/packages/94/34/dd3083b54dc78a5e32ee132ea2c7544c234796cc9922cc62fff7fb3c2634/asysocks-0.0.2-py3-none-any.whl
Collecting ldap-filter (from msldap>=0.2.7->pypykatz)
Downloading https://files.pythonhosted.org/packages/d3/99/5192881858166d59cbd252366b03128ff777682171e890a3b9a36e726b77/ldap-filter-0.2.1.tar.gz
Requirement already satisfied: prompt-toolkit>=2.0.9 in /usr/lib/python3/dist-packages (from aiocmd->msldap>=0.2.7->pypykatz) (2.0.10)
Building wheels for collected packages: asciitree, ldap-filter
Running setup.py bdist_wheel for asciitree ... done
Stored in directory: /root/.cache/pip/wheels/1d/d9/58/9808b306744df0208fccc640d3d9952a5bc7468502d42897d5
Running setup.py bdist_wheel for ldap-filter ... done
Stored in directory: /root/.cache/pip/wheels/e0/e0/62/4aeb744457591783ebb19e6596216aec2c0af6c6b778e3b15d
Successfully built asciitree ldap-filter
minikerberos 0.2.0 has requirement asn1crypto>=1.3.0, but you'll have asn1crypto 0.24.0 which is incompatible.
Installing collected packages: asciitree, aiocmd, winacl, asysocks, ldap-filter, msldap, minidump, minikerberos, winsspi, aiowinreg, pypykatz
Successfully installed aiocmd-0.1.2 aiowinreg-0.0.2 asciitree-0.3.3 asysocks-0.0.2 ldap-filter-0.2.1 minidump-0.0.12 minikerberos-0.2.0 msldap-0.2.8 pypykatz-0.3.6 winacl-0.0.2 winsspi-0.0.5

Yes, the minimum requirement of asn1crypto has changed a few weeks back, the old version was a workaround to support other creator's tools but now everybody seems to have switched to the new version. The old version of asn1crypto is not compatible with the new one (especially on the datetime conversion part which is needed for kerberos and thus for the ticket parsing)
To solve the problem for minikerberos:
pip uninstall asn1crypto
pip install asn1crypto>=1.3.0

But be aware you might need to update other security tools (impacket/krbrelayx etc) as well, otherwise they might crash.


Add harvester load balancer chart

issue: https://github.com/harvester/harvester/issues/1019

It should be merged after the version 0.1.1 release.


[NBS Docs] for catalog-backend-module-incremental-ingestion plugin

Hey, I just made a Pull Request!
Add new backend setup doc for plugin https://github.com/backstage/backstage/tree/master/plugins/catalog-backend-module-incremental-ingestion
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Thanks @jhaals. I have moved old backend doc at bottom.

Nice one! @jhaals Just wondering, and also maybe @ahhhndre / @sennyeya in terms of these NBS docs are we following this pattern? e.g. https://github.com/backstage/backstage/pull/25805
Where we make an --old for the old backend?
WDYT?
Thanks! 🙏

@Parsifal-M as this is in a README.md it's hard to apply that pattern here. I think in this case merging this PR as is makes sense but then adding it somewhere in the Software Catalog section of the docs would be great to raise awareness.

Thanks, @awanlin! I'll work on the suggested changes. Regarding the follow-up PR, are you suggesting that this document be added to the main documentation? If so, where should it be linked, perhaps under the External Integrations page as an "Incremental Entity Providers" section?

Yes, that sounds like a good place for it to go @zeshanziya 👍

Hey @awanlin, I have made the suggested changes. Please review. Thank you.

Glad to see docs improvements! I just want to point out that we plan to completely remove the old backend system this year so I don't think we should much time on having docs for both new and old system, I rather have us just support the new system as we are currently working on deprecating createRouter and similar exports across all backend plugins. Meta issue will follow with some more context and how to update each plugin accordingly.

I'll re-review once the changes @jhaals requested are made @zeshanziya 👍

Thanks @jhaals @awanlin. As suggested, I have removed old backend related docs.


API list for Phython SDK

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

I can't find documentation on python sdk's APIs

Any log messages given by the failure

n/a

Expected/desired behavior

having list of API supported by python SDK would increase the productivity.

OS and Version?

n/a

Versions

n/a

Mention any other details that might be useful

Thanks! We'll be in touch soon.

Here's the Python SDK reference https://azure.github.io/azure-sdk-for-python/

Here's the Python SDK reference https://azure.github.io/azure-sdk-for-python/

thanks


Ethan: Watch rtp-bahagia.vip

Ethan requests the watch of the watch_keyword rtp-bahagia\.vip. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

rtp-bahagia\.vip has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


[FLINK-10289] [JobManager] Classify Exceptions to different category for apply different failover strategy

What is the purpose of the change
We need to classify exceptions and treat them with different strategies. To do this, we propose to introduce the following Throwable Types, and the corresponding exceptions:

NonRecoverable

We shouldn’t retry if an exception was classified as NonRecoverable
For example, NoResouceAvailiableException is a NonRecoverable Exception
Introduce a new Exception UserCodeException to wrap all exceptions that throw from user code

PartitionDataMissingError

In certain scenarios producer data was transferred in blocking mode or data was saved in persistent store. If the partition was missing, we need to revoke/rerun the produce task to regenerate the data.
Introduce a new exception PartitionDataMissingException to wrap all those kinds of issues.

EnvironmentError

It happened due to hardware, or software issues that were related to specific environments. The assumption is that a task will succeed if we run it in a different environment, and other task run in this bad environment will very likely fail. If multiple task failures in the same machine due to EnvironmentError, we need to consider adding the bad machine to blacklist, and avoiding schedule task on it.
Introduce a new exception EnvironmentException to wrap all those kind of issues.

Recoverable

We assume other issues are recoverable.

Brief change log

Add exception types
Add a class to classify exceptions
Unittests

Verifying this change
This change added tests and can be verified as follows:

Added test that validates SuppressRestartsException was a NonRecoverable Exception

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? YES, Document is (Here)

I really like this idea in principle.
Instead of attaching an enum classifier, could we solve this by exception inheritance? Having exceptions that represent the categories and then making the specific exceptions subclasses of the category exceptions?

I really like this idea in principle.
Instead of attaching an enum classifier, could we solve this by exception inheritance? Having exceptions that represent the categories and then making the specific exceptions subclasses of the category exceptions?

Thanks Stephan, use exception inheritance certainly a good way, however:

enum explicitly tell that there are four types of exceptions, while exception is more scattered.
Java doesn't support multi-inherits that will make subclasses a little harder but we can also use Java interface or Java annotation
There is a high level class need to consume this classification logic, so the ThrowableClassifier here is simply the logic, eg: if we use annotation, we need a logic to extract the annotation.

so i would propose to mix those ideas together, keep the classify logic and use Java annotation/interface, @StephanEwen let me know what you think.
Jin

@StephanEwen , i have changed the implementation with java annotation, could you take a look?

@isunjin I also like the general idea, but not so much the current implementation. One disadvantage I see with the annotation is that they are not propagated in inheritance hierarchies and you always need to remember adding them in such a case. I also wonder where and how this classifier will be invoked later. Maybe an alternative approach could be to have a fixed set of TaskExceptions for the cases, and before leaving the TM, all exceptions are wrapped as cause into their matching TaskException  to classify them for the JM's recovery approach. However, the "best" approach might also depend on the intended use, which is not clear for me from the PR and that is why I am asking.

@StefanRRichter Thanks for review and you make a very good point, but annotation can be propagate with a '@Inherited' annotation, i have modified the code with unittest.
for the consumer of this class, i would like to split the commit to make it simple, it will be in another PR, that basically implement the logic mentioned in the design doc.

@isunjin I think this looks good now. I wonder if we should rename the type Other to something like RecoverableFailure?

@StefanRRichter Thank you, pushed the change.


New conversation flow

On the main screen there should be a new conversation button. When clicked, a new view appears that is dedicated to picking a recipient.
The user selects a recipient by typing in part of a username and then selecting from a list of results. When a recipient is selected, a new view appears for the conversation with that recipient. If a conversation already exists, it is loaded; otherwise a new conversation is created.
The user inputs text into a text field.
The user sends the text.
The conversation view is updated to display the sent message.

https://github.com/stfalcon-studio/ChatKit


Folder tree stops loading when using CTRL+Click to jump to a function in another folder

Version: 1.33.1 (user setup)
Commit: 51b0b28134d51361cf996d2f0a1c698247aeabd8
Date: 2019-04-11T08:27:14.102Z
Electron: 3.1.6
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763
Steps to Reproduce:

Have a workspace that has two folders [in my case they are two different repos], say folder A and B
B is more like a wrapper layer that have the actual implementation in A
Load the workspace and check the folder tree. All folders and files are loaded normally
Open a file in B whose implementation is in A. eg: self.my_object.MethodInA(). Do not open any files from A
CTRL + Click to jump to the implementation
The file containing that implementation is opened
Now start expanding folder 'A'. No files/folder are found

Does this issue occur when all extensions are disabled?: Did not test
exthost.log
Window log has the following exception:
[2019-05-02 11:29:04.378] [renderer6] [error] Tree element not found: [object Object]: Error: Tree element not found: [object Object]
    at s.getElementLocation (file:///C:/Users/RSekhri/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:91:674)
    at setCollapsed (file:///C:/Users/RSekhri/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:91:102)
    at s.collapse (file:///C:/Users/RSekhri/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:940:219)
    at Y.<anonymous> (file:///C:/Users/RSekhri/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:956:590)
    at Generator.next (<anonymous>)
    at r (file:///C:/Users/RSekhri/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:32:293)
![load_steps](https://user-images.githubusercontent.com/46380417/57091969-5f5a4d00-6cd8-11e9-9069-bbccf8974d26.gif)

Can you reproduce this with latest vscode insiders
https://code.visualstudio.com/insiders/

Yes. It's reproducible on insiders too. The insiders build had only the Python extension. However, the exception was not seen but folders disappeared after CTRL+Click.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Isidor Nikolic<EMAIL_ADDRESS>Sent: Friday, May 3, 2019 5:13:05 AM
To: Microsoft/vscode
Cc: Rohan Sekhri; Author
Subject: Re: [Microsoft/vscode] Folder tree stops loading when using CTRL+Click to jump to a function in another folder (#73177)
Can you reproduce this with latest vscode insiders
https://code.visualstudio.com/insiders/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vscode/issues/73177#issuecomment-489023006, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALB3LAL2CMENNANV2ABQUCLPTP62DANCNFSM4HKAH7OQ.

Please share a folder for which you can reproduce all the time. Can you please put it on GitHub so we can reproduce this issue on our machine?
Also exact steps would be useful.

Exact steps are there. In case, anything is not clear, please feel free to ask.
The code is company proprietary, so I won't be able to upload that code. However, I can try on some custom code and see if it shows up. I would need some time on that.

I tried reproducing this with the version below using a small project which wasn't source controlled. Could not reproduce it. But, with the folder structure I have in my company, I can repro this 100%. Is there anything else I can share to resolve this issue?
Version: 1.34.0 (user setup)
Commit: a622c65b2c713c890fcf4fbf07cf34049d5fe758
Date: 2019-05-15T21:59:37.030Z
Electron: 3.1.8
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763

Looks like a duplicate of https://github.com/microsoft/vscode/issues/73469

Exception is similar to what I posted earlier. I saw your comment there that you were able to reproduce it, so let's go with that fix and see if these two are related (on the insiders build, I didn't have any exceptions). Apologies, I haven't had much time to play around much the past weeks.

No data provided -> closing issue.
If you still see it please let me know with steps so I can reopen this. Thank you


Adding version sorting (renew PR due to some rebase issues)

Please squash these commits so the PR starts with a clean commit log.

            CompletionSet set = task.Result;

Can you rename this so it's not a C# keyword?

Refers to: src/LibraryManager.Vsix/Json/Completion/LibraryIdCompletionProvider.cs:74 in d0c64d0. [](commit_id = d0c64d072dd4e1c8ba98e50347e7122291582a77, deletion_comment = False)

            CompletionSet set = task.Result;

Will do

In reply to: 408188777 [](ancestors = 408188777)

Refers to: src/LibraryManager.Vsix/Json/Completion/LibraryIdCompletionProvider.cs:74 in d0c64d0. [](commit_id = d0c64d072dd4e1c8ba98e50347e7122291582a77, deletion_comment = False)

                if (!context.Session.IsDismissed)

It looks like the current one will do an extra UpdateListEntriesSync() operation if set.completions is not null.
Do you think we should have a private function to handle the duplicated part?

In reply to: 408190628 [](ancestors = 408190628)

Refers to: src/LibraryManager.Vsix/Json/Completion/LibraryIdCompletionProvider.cs:105 in d0c64d0. [](commit_id = d0c64d072dd4e1c8ba98e50347e7122291582a77, deletion_comment = False)

                if (!context.Session.IsDismissed)

Yes

In reply to: 408205133 [](ancestors = 408205133,408190628)

Refers to: src/LibraryManager.Vsix/Json/Completion/LibraryIdCompletionProvider.cs:105 in d0c64d0. [](commit_id = d0c64d072dd4e1c8ba98e50347e7122291582a77, deletion_comment = False)

Squashed

In reply to: 404975539 [](ancestors = 404975539)

                assets = ConvertToAssets(json);

Are these changes related to your other changes in this PR or for something different?

Refers to: src/LibraryManager/Providers/Cdnjs/CdnjsCatalog.cs:292 in 0bff13d. [](commit_id = 0bff13d74a77e24405d816f81fda838ed88f5a2b, deletion_comment = False)

                if (!context.Session.IsDismissed)

Why not include the isVersionCompletion and Completions null check in the method?

In reply to: 408217065 [](ancestors = 408217065,408205133,408190628)

Refers to: src/LibraryManager.Vsix/Json/Completion/LibraryIdCompletionProvider.cs:105 in d0c64d0. [](commit_id = d0c64d072dd4e1c8ba98e50347e7122291582a77, deletion_comment = False)

                assets = ConvertToAssets(json);

No. This is some code sync from the master as this branch is not very much updated yesterday. So I have do a rebase operation.

In reply to: 408473549 [](ancestors = 408473549)

Refers to: src/LibraryManager/Providers/Cdnjs/CdnjsCatalog.cs:292 in f387da5. [](commit_id = f387da55f84869f47d57065f34f92311bb2a280a, deletion_comment = False)

                if (!context.Session.IsDismissed)

Yes. I can include in the method. Just think of need to obtain this value again in the above yield return part.

In reply to: 408474137 [](ancestors = 408474137,408217065,408205133,408190628)

Refers to: src/LibraryManager.Vsix/Json/Completion/LibraryIdCompletionProvider.cs:105 in f387da5. [](commit_id = f387da55f84869f47d57065f34f92311bb2a280a, deletion_comment = False)


fixed some visual bugs on search

Current dependencies on/for this PR:

trunk

PR #2   👈

This comment was auto-generated by Graphite.


add cloud availability setting

Sorry, I just realized that this setting is not required, because the auth_url is given and no other OpenStack services are called.


chore(Deps) dependency next to v14.2.0

This PR contains the following updates:

Package
Type
Update
Change

next (source)
dependencies
minor
14.1.4 -> 14.2.0

Release Notes

vercel/next.js (next)
v14.2.0
Compare Source
Core Changes

Update build worker warning to use debug: #60847
fix: added @sentry/profiling-node to sep list to prevent build/bundle breakage: #60855
Optimize build trace ignores: #60859
Deprecation warning for config.analyticsId: #60677
chore: indicate staleness more prominently in next info output: #60376
Telemetry: createComponentTree span: #60857
chore: replace micromatch w/ picomatch: #60699
Report HMR latency as trace spans for Turbopack: #60799
Turbopack: always log HMR rebuild times: #60908
Error overlay refactors: #60886
Use precompiled source-map in overlay middleware: #60932
Use more precompiled deps in react-dev-overlay: #60959
Fix next phase for next build: #60969
chore: update turbopack: #60980
refactor(analysis): rust based page-static-info, deprecate js parse interface in next-swc: #59300
disable static generation on interception routes: #61004
Docs: Address community feedback: #60960
avoid output of webpack stats: #61023
Revert "refactor(analysis): rust based page-static-info, deprecate js parse interface in next-swc": #61021
fix useSelectedLayoutSegment's support for parallel routes: #60912
Dynamic APIs: #60645
Enable next.js version checker in turbopack: #61034
chore: Update terser to v5.27.0: #61068
Update swc_core to v0.87.28: #60876
update turbopack: #61015
Implement client_root for edge in Turbopack: #61024
fix parallel route top-level catch-all normalization logic to support nested explicit (non-catchall) slot routes: #60776
fix(image): warn when animated image is missing unoptimized prop: #61045
Fix version checker not displaying when version newer than npm: #61075
Fix sitemap generateSitemaps support for string id: #61088
ppr: ensure the router state tree is provided for interception routes: #61059
Improve the Server Actions SWC transform: #61001
Fix instrument bundling as client components: #60984
fix(turbopack): use correct layout for 404 page: #61032
fix: emotion import source should be enabled in SSR contexts: #61099
chore: update turbopack: #61090
fix(turbopack): custom page extensions for _app: #60789
Disable trace uploads with NEXT_TRACE_UPLOAD_DISABLE: #61101
add optimizeServerReact to config-shared: #61106
Fix filesystempublicroutes test for Turbopack: #61132
chore: upgrade webpack to 5.90.0: #61109
Add maxDuration to typescript plugin allowed exports: #59193
Upgrade Turbopack: #61190
build: remove sentry from the externals list: #61194
exclude default routes from isPageStatic check: #61173
Add stack trace to client rendering bailout error: #61200
chore: refactor image optimization to separate external/internal urls: #61172
parallel routes: support multi-slot layouts: #61115
Refine revalidatePath warning message: #61220
revert changes to process default routes at build: #61241
Fix cookie merging in Server Action redirections: #61113
Update swc_core to v0.89.x: #61086
Fix Server Reference being double registered: #61244
Fix Server Action redirection with absolute internal URL: #60798
Fix indentation in source code of dev overlay: #61216
Update swc_core to v0.89.4: #61285
fix: Revert preset-env mode of styled-jsx in webpack mode: #61306
DX: add route context to the dynamic errors: #61332
Telemetry: add time-to-first-byte signal: #61238
Refine logging message of experiments: #61337
fix(turbopack): don't parse .ts files as .tsx: #61219
Update turbopack: #61381
Same as #61360: #61369
Always respect NEXT_TRACE_UPLOAD_DISABLED: #61402
parallel routes: fix catch-all slots being treated as optional catch-all: #61174
fix hmr telemetry reporting: #61420
chore: Update swc_core to v0.89.6: #61426
Update turbopack: #61433
fix a perf problem in VersionedContentMap: #61442
Fix next dynamic import named export from client components: #61378
fix issues loading CSS in default slots: #61428
avoid sending issues turbopack messages to browser: #61443
Support crossOrigin in Turbopack: #61461
Pass down __NEXT_EXPERIMENTAL_REACT env to webpack build worker explicitly: #61463
Replace image optimizer IPC call with request handler: #61471
feat(next): trace build dependencies for turborepo: #59553
Turbopack: fix telemetry attributes for swc options: #61474
Always show version text in error overlay: #61421
Fix build worker callback arg missing correct page path : #61347
Update font data: #61479
build: upgrade edge-runtime: #61030
Fix experimental react support in app-route runtime: #61511
Fix .env hmr for Node.js runtime in Turbopack: #61504
remove unnecessary PPR branch in non-PPR reducer: #61176
fix: bump<EMAIL_ADDRESS>#61538
chore: update ESLint and plugins to latest: #61544
Update turbopack: #61553
feat: first pass of next/font manifest: #61424
Fix .env HMR for Turbopack in Edge runtime: #61565
build(cargo): bump up turbopack: #61590
refactor(next-core): consolidate custom ecma transform rules: #61481
ensure server action errors notify rejection handlers: #61588
feat(turbopack): only preload fonts that opt in: #61591
feat(turbopack): serve google fonts locally and allow preloading them: #61596
Update font data: #61621
Remove unused mockedRes in resolveRoutes: #61635
Fix @react-pdf/renderer not working in RSC: #61317
Remove extra edge-runtime/primitives override: #61641
Encode revalidateTag value fixes #61390: #61392
Update README.md: #48717
chore: update README.md: #61650
avoid processing client components and server actions in route handlers: #60985
chore: Update @swc/helpers to v0.5.5: #61659
feat(ts): expose MiddlewareConfig interface: #61576
Revert "build: upgrade edge-runtime": #61686
feat(ts): add JSDoc comments for public APIs: #61649
fix(next-core): adjust server alias for the context: #61690
fix setAssetPrefix when running on NextCustomServer: #61676
fix: status code for 404 props queries to avoid client side navigation with empty props: #60968
fix(next-eslint): .eslintrc.json not being created by next lint on App Router: #55104
Update React from 60a927d to 2bc7d33: #61522
fix(turbopack): read preload option for google fonts: #61679
decode magic identifiers: #61658
Associate server error digest with browser logged one: #61592
chore: update turbopack: #61682
fix loading issue when navigating to page with async metadata: #61687
fix(ts): ReadonlyURLSearchParams should extend URLSearchParams: #61419
fix navigation issue when dynamic param casing changes: #61726
Fix next/server api alias for ESM pkg: #61721
feat(transforms): enable rsc transforms for the remaining contexts: #61231
fix: allow some recursion for middleware subrequests: #60615
feat(next-swc): support wasm32-* build target: #61586
Turbopack: convert between locations correctly: #61477
feat(next/image)!: remove squoosh in favor of sharp as optional dep: #61696
Navigation Signals in PPR: #60450
Revert "Turbopack: convert between locations correctly (#61477)": #61733
Fix duplicate line in README: #61691
docs: fix example code missing comma: #59012
Reapply "Turbopack: convert between locations correctly (#61477)" (#61733): #61735
Fix: Error Fetching _devpagesmanifest.json #17274: #60349
fix jsDoc of notFound: #61692
feat(next-core): expand matching js extensions for the rules: #61745
source map fixes: #61723
Add experimental touchstart flag for testing: #61747
partially fix css duplication in app dir: #61198
build(cargo): add deps for the wasi: #61784
fix(ts): match MiddlewareConfig with documentation: #61718
Fix attempted import error for react: #61791
consolidate prefetch utils & separate build util: #61789
Skip client-side data-fetching after ssr error : #51377
fix(next-swc): Detect exports.foo from cjs_finder: #61795
feat(next-core): build time client|server-only assertion: #61732
Fall back loading chunks for sourcemap tracing: #61790
Increase Rust stack size: #61809
Revert "feat(next/image)!: remove squoosh in favor of sharp as optional dep": #61810
DX: fix error overlay flash: #61813
feat: Allow specifying useLightningcss  for styled-jsx: #61359
Guard against restoring router state with missing data: #61822
fix: babel usage with next/image: #61835
fix:(next/image) handle remotePatterns with a dot in the pathname: #60488
Update React from 2bc7d33 to ba5e6a8: #61837
DX: fix error overlay flash: #61813
feat: Allow specifying useLightningcss  for styled-jsx: #61359
Guard against restoring router state with missing data: #61822
fix: babel usage with next/image: #61835
fix:(next/image) handle remotePatterns with a dot in the pathname: #60488
Update React from 2bc7d33 to ba5e6a8: #61837
update turbopack: #61187
conditionally send Next-URL in Vary response: #61794
provide interception rewrites to edge runtime: #61414
Update app-index to only ever construct the initial data response once: #61869
Move turbopack helpers: #61917
hot-reloader-turbopack refactors: #61929
More hot-reloader-turbopack refactors: #61940
fix(next/image): improve warning when fill and sizes="100vw": #61949
build(cargo): bump up turbopack to latest: #61952
build(cargo): update turbopack for filewatcher fix: #61955
ci(workflow): deploy rustdocs for turbopack: #61958
Support resuming a complete HTML prerender that has dynamic flight data: #60865
Fix empty white page with parallel routes + loading boundaries: #61597
Update swc_core to v0.90.7 and update turbopack: #61662
Turbopack: remove server addr: #61932
More hot-reloader-turbopack refactors: #61993
Use destructured object for #61993: #61996
only prefix prefetch cache entries if they vary based on Next-URL: #61235
seed prefetch cache with initial page: #61535
Remove leftover server addr references: #61997
log fast refresh in app dir: #61441
docs(turbopack): build more docs: #61977
fix(next-core): correct error message: #62011
docs(turbopack): reduce documentation size: #62016
Reduce memory/cache overhead from over loader processing: #62005
fix: bump<EMAIL_ADDRESS>#62019
refactor(next-core): do not reexport turbopack_binding: #62018
build: Update swc_core to v0.90.8: #61976
merge pages and app overlays: #60899
Rename internal utility naming for clarification : #62048
fix: handle multiple x-forwarded-proto headers: #58824
Fix server components externals on SSR layer: #61986
Fixed useParams hook undesired re-renders and updated it to use PathParamsContext in the app router.: #60708
docs(turbopack): conslidate existing links: #62034
fix(custom-transform): allow to assert empty program for rsc: #61922
fix navigation applying stale data when triggered from global not found: #62033
fix(turbopack): react-dom/server in rsc context: #61165
refactor(tests): make chain more "correct": #51728
Add puppeteer-core to server-external-packages.json: #62063
Fix extra swc optimizer applied to node_modules in browser layer: #62051
docs(turbopack): revise links: #62062
Fix output: export with custom distDir: #62064
fix(next-core): apply image-loader alias to the remaining context: #62070
More hot-reloader-turbopack refactors: #62055
Ensure Turbopack writes font optimization manifest: #62079
update turbopack: #62080
chore: hide version info network error: #62084
Add dev option to Turbopack createProject(): #62083
Remove unused app-turbopack files: #62087
make router restore action resilient to a missing tree: #62098
Turbopack: add support for dynamic requests in require() and import(): #62092
docs(turbopack): move docs to separate: #62069
Implement Vc: #62099
fix: add zeromq to server-external-packages.json: #62105
Fix trailing slash for canonical url: #62109
Consolidate NextMode checks: #62106
Improve the Server Actions SWC transform (part 2): #62052
Should not warn metadataBase missing if only absolute urls are present: #61898
Update to turbopack-240215.5: #62119
Add polyfill for Object.hasOwn: #60437
OpenTelemetry: trace API routes in page router: #62120
Fix @next/mdx types: #57580
DX: hide the webpack info prefix for module paths: #62101
Show build errors from Turbopack: #62139
Fix issue with ComponentMod being read in Turbopack: #62141
Fix handling subpath for server components externals: #62150
docs(next-api): trying to document project_update_info_subscribe: #61962
add support for esmExternals in pages: #61983
docs: updated link in JSDoc for the shallow property in link.tsx: #62181
Update font data: #62173
Update split chunk handling for edge/node: #62205
Ensure webpack build worker defaults on: #62214
feat: Lint invalid CSS modules: #62040
Add page name to error logged in Turbopack: #62218
add turbo.resolveExtensions to allow to customize extensions: #62004
fix(turbopack): catchall route matching: #62114
fix: clarify Dynamic API calls in wrong context: #62143
refactor(turbopack): wrap manifest loading in helper class: #62118
refactor(turbopack): resolve routes by page name instead of pathname: #61778
Ensure handleRouteType does not throw in production builds: #62234
fix: set swr delta: #61330
Fix type error in build.ts: #62253
fix(next): terser-webpack-plugin path in taskfile.js is missing 'src': #62229
Update swc_core to v0.90.10: #62222
Add test log prefix for otel: #62258
Update turbopack: #62263
feat(cli): show available memory/CPU cores in next info: #62249
fix(turbopack): print missing slots in debug message: #62280
Tree shake the unused exports in direct relative imported client component module: #62238
Verify correctness of externals: #62235
Renew prefetch cache entry after update from server: #61573
fix(next-core): fix aliased free var for edge runtime: #62289
update turbopack: #62285
Allow fetch to propagate arbitrary init options: #62168
Add flag for early import app router modules: #61168
Add otel span for client component loading: #62296
Fix perf spans: #62306
fix(next-core): properly normalize app route for _: #62307
fix(next-font): update capsize css so fallbacks are updated with the …: #62309
Fix draft mode invariant: #62121
Revert "Update split chunk handling for edge/node": #62313
Turbopack: reduce tasks needed for emitting: #62291
Turbopack: add SSR category to tracing: #62318
fix(error-overlay): correct module grouping: #62206
Revert "Turbopack: reduce tasks needed for emitting": #62324
feat(error-overlay): hide <unknown>/stringify methods in <anonymous> file from stack: #62325
eslint-config-next: allow typescript eslint v7: #62137
Revert "Revert "Update split chunk handling for edge/node" (#62313)": #62336
Revert "Ensure webpack build worker defaults on": #62342
avoid loading the page loader chunk on initial page load: #62269
output filesystem without watching: #62340
Turbopack: limit build concurrency, show progress bar: #62319
Update data cache max size error: #62348
Add experimental flag for early exit on prerender error: #62367
fix(next-swc): Fix span for invalid 'use server' directives: #62259
scope issues from subscriptions to the websocket connection: #62344
Turbopack: resolve endpoints to avoid extra nesting in tracing: #62317
fix(next-lint): fix next lint not throwing exit 1 on error: #62378
Remove default fallback behavior when route group is missing a default: #62370
Correctly pass prependData and additionalData to sass-loader for Turbopack: #62397
chore(docs): mention that next.config.js must have default export: #62341
chore(cli): add clarifying comment: #62418
OTEL: Add top span for middleware: #62421
Turbopack react-refresh: perform full reload on runtime error: #62359
Simplify node/edge server chunking some: #62424
update configSchema.ts with experimental#useEarlyImport: #62408
Fix module-level Server Action creation with closure-closed values: #62437
Upgrade vendored react: #62326
Turbopack: reduce memory usage: #62432
Fixed typo.: #62440
fix(turbopack): deal with eventual consistency in get_directory_tree: #62444
Telemetry: ensure the ClientComponentLoad metric is only reported when available: #62459
[turbopack] update edge alias: #62461
Rename currentIssues to currentEntryIssues: #62524
update turbopack: #62523
add plugin to avoid too many css requests: #62530
feat(error-overlay): hide Node.js internals: #62532
Create react server condition alias for next/navigation api: #62456
Add IssueKey type: #62526
OTEL: Ensure that RSC:1 requests get the next.route attr: #62464
Display only one hydration error when there's few in error overlay: #62448
Upgrade vendored react: #62549
Improve TS plugin options: #62438
Revert "fix(build-output): show stack during CSR bailout warning": #62592
Improve redirection handling: #62561
fix router crash on revalidate + popstate: #62383
fix: improve error when starting next without building: #62404
feat(turbopack): Sort issues: #62566
refactor createInfinitePromise to be re-used unresolveable thenable: #62595
fix(build-output): show stack during CSR bailout warning: #62594
Fix redirect under suspense boundary with basePath: #62597
Ensure dynamic routes dont match _next/static unexpectedly: #62559
Fix metadata json manifest convention: #62615
Migrate locale redirect handling to router-server: #62606
fix(next-swc): Provide tokio context required for WASM plugins: #62441
Update swc_core to v0.90.12: #62518
Update Turbopack: #62632
Fix instrumentation with only pages: #62622
Fix: generateSitemaps in production giving 404: #62212
Refactor flight-manifest-plugin to use compilation.entrypoints directly: #62636
Fix Router Error Events in Shallow Routing by Skipping cancelHandler Creation: #61771
DX: display highlited pesudo html when bad nesting html error occurred: #62590
build(cargo): remove unused features: #62616
feat(next-swc): lightningcss binding: #62604
fix: Enable SearchParams to be displayed after redirect in Server Action: #62582
fix(navigation): allow useSelectedLayoutSegment(s) in Pages Router: #62584
Consistently use /_not-found for not found page in App Router: #62679
Add experimental config for navigation raf test: #62668
Turbopack: remove unused code: #62690
Revert "Ensure dynamic routes dont match _next/static unexpectedly": #62691
fix(turbopack): don't emit issues for deleted pages: #62012
perf: don't emit issues via websocket for now: #59024
add native css nesting support: #62644
refactor(next-swc): remove unused features: #62696
Upgrade mini-css-extract-plugin: #62698
Update precompiled for mini-css-extract-plugin: #62699
feat: display text diff for text mismatch hydration errors: #62684
Fix lint check: #62702
chore: remove unused helper: #62701
Add param to debug PPR skeleton in dev: #62703
Update font data: #62704
Turbopack: remove node_modules error filter: #62586
fix(error-overlay): improve a11y, minor refactors: #62723
Handle top level errors coming from Turbopack entrypoints subscription: #62528
Add compiler error for conflicting App Router and Pages Router in Turbopack: #62531
fix dev overlay pseudo html collapsing: #62728
Route static render error message: remove duplicate word: #62738
Update version from backport: #62745
Add a flag to disable MergeCssChunksPlugin: #62746
refactor(cli): refactor cli to commander: #61877
Turbopack: Trace server app render errors through source maps: #62611
build(cargo): update turbopack: #62744
Turbopack: sass support: #62717
refactor(analysis): rust based page-static-info, deprecate js parse interface in next-swc: #61832
fix: Add stricter check for "use server" exports: #62821
fix(next-core): throw on invalid metadata handler: #62829
Revert "Add experimental config for navigation raf test (#62668)": #62834
Revert "refactor(analysis): rust based page-static-info, deprecate js parse interface in next-swc": #62838
remove reducer unit tests: #62766
fix(next-lint): do not pass absolute path to distDir: #62797
Update to latest version: #62850
fix "setBlocking is not a function" errors on StackBlitz: #62843
Remove extra logic of Server Reference check for registering twice: #62486
Update readme of @next/bundle-analyzer package: #62804
Don't emit crossorigin attributes for output: "export" by default: #61211
apply some transforms on foreign code too: #62827
update turbopack: #62884
refactor: rename isAppDirEnabled to hasAppDir: #62837
bump @edge-runtime/cookies for Partitioned cookie support: #62889
refactor(next): fix spacing on auto-generated root layout: #62769
fix(cli): fix allowRetry when using port 3000: #62840
Fix: missing crossorigin property on manifest link: #62873
Turbopack: Trace edge runtime app render errors through source maps: #62901
fix merge css plugin to account for css order: #62927
fix(next-api): correct font manifest generation: #62916
feat(error-overlay): notify about missing html/body in root layout: #62815
fix graph update: #62933
refactor(error-overlay): improve server code for webpack/Turbopack middleware: #62396
feat(error-overlay): version staleness in Pages Router: #62942
feat: Introduce lightningcss-loader for webpack users: #61327
feat(eslint): enhance no-unwanted-polyfill w/ new endpoints: #62719
simplify streamToString method from node-web-streams.helper.ts: #62841
Allow ppr only flag in test mode: #62911
Upgrade to latest @edge-runtime packages: #62955
chore(next-font): update @capsize/metrics package to the latest: #62896
Remove Payload from server-external-packages.json: #62965
Pass whole prefetch entry rather than status property: #62345
build: Update swc_core to v0.90.17: #62924
refactor(ts): type fastRefresh: #62848
[error overlay] move missing tags error inside error overlay: #62993
Update turbopack: #62971
fix(next-core): honor basepath for the metadata property: #62846
fix(next-core): do not apply ecma transforms for custom js rules: #62831
feat(next): fallback lightning if swc/wasm loaded: #62952
Fix the plugin state for async modules in webpack plugins: #62998
Turbopack + pages router: recover from runtime errors by reloading: #63024
Enable minification for Turbopack: #62994
app layouts/pages depend on shared main files: #63042
DX: add route context to dynamic errors for app routes: #62844
Fix metadata url cases should not append with trailing slash: #63050
Turbopack: Decode module component when tracing stack frames: #63070
build(cargo): bump up turbopack: #63073
OTEL: add next.rsc attribute for RSC requests: #63074
Correctly deserialize undefined unstable_cache data: #59126
refactor(error-overlay): unify Pages/App router error overlay source: #62939
feat(turbopack): Enable lightningcss for turbopack by default: #62565
ignore fully dynamic requests on server side: #62949
Refactor define-env-plugin to have stricter types: #63128
[PPR] Support rewrites in middleware: #63071
Fix webpack HMR for pages on the edge runtime: #60881
fix typo in server/config.ts: #62795
ensure mpa navigations to the same URL work after restoring from bfcache: #63155
Ensure PromiseLikeOfReactNode is not included in .d.ts files: #63185
Ensure undefined values end up being replaced: #63138
fix: x-forwarded-port header is 'undefined' when no port in url: #60484
Fix generateMetadata race condition: #63169
feat(next-core): apply invalid import assertion on the remaining contexts: #63146
build(cargo): bump up turbopack: #63205
add support for assets in edge: #63209
fix: Loose Server Actions runtime check: #63200
fix(log): improve error when dynamic code eval is disallowed: #62999
fix(error-overlay): strip line+column from webpack internal frames: #63133
fix revalidation issue with route handlers: #63213
fix(error-overlay): show Turbopack indicator for any staleness level: #63130
fix: re-export internal path: #63222
build: Update turbopack: #63229
make CacheNode properties non-optional: #63219
Implement new runtime_type for Turbopack: #63212
Use SWC to valid client next/navigation hooks usage in server components: #63160
chore: Update swc_core to v0.90.21: #63031
fix(turbopack): Do not report hmr timing twice: #63227
enable optimizeServerReact by default: #62658
feat(turbopack): emit well known error into cli: #63218
feat: add deploymentId config: #63198
Fix middleware catch-all rewrite case: #63254
fix(route-handlers): make sure preflight has CORS headers: #63264
fix(turbopack): Remove error overlay when issue is resolved: #62983
Disable cache in testmode: #63265
Turbopack: app externals test case improvements: #62871
build: Update turbopack: #63273
fix: hydration error display for text under tag case: #63288
Fix URL displayed in Server Action bodysizelimit error: #63295
Store loading data in CacheNode: #62346
fix(turbopack): Remove error overlay when pages/_app is fixed: #63306
Ensure changes in optimizePackageImports invalidate webpack cache: #63284
Polish the display color styles for component diff: #63342
Turbopack HMR: Log when more errors cause full page reload: #63220
Fixes typo in Route handler static generation error handling: #63345
Add JSM (ESM) support for next/lib/find-config: #63109
fix(error-overlay): matching html tag with brackets in hydration error: #63365
add conditions for webpack loader rules: #63333
fix transform of files ending with d: #63367
Use correct protocol and hostname for internal redirections in Server Actions: #63389
bug: Fields truncated when submitting form using Server Actions: #59877
New CSS chunking algorithm: #63157
Ensure all metadata files have missing default export errors in Turbopack: #63399
Code refactor: #63391
feat(error-overlay): handle script under html hydration error: #63403
Add Bun lockfile to project root resolving heuristic: #63112
build(package): pin typescript-eslint/parser for supported node.js: #63424
fix(next-core): carry over original segment config to metadata route: #63419
fix x-forwarded-port header: #63303
build(cargo): bump up turbopack: #63429
Turbopack HMR: Reload when recovering from server-side errors: #63434
Eliminate unnecessary decode operations in node-web-streams-helpers.ts: #63427
Update React from 6c3b8db to 14898b6: #63439
chore(next/font): update @capsizecss/metrics package to the latest: #63440
update turbopack: #63475
Fix instant loading states after invalidating prefetch cache: #63256
Update tags limit handling for max items: #63486
feat(next-core): support unsupported module runtime error: #63491
Update RSC etag generation handling: #63336
Simplify createRootLayoutValidatorStream: #63484
Fix interception/detail routes being triggered by router refreshes: #63263
route/middleware/instrumentation use server assets instead of client assets: #62134
feat: add support for localizations in sitemap generator: #53765
Turbopack: Fail when module type is unhandled: #63535
feat(custom-transform): middleware dynamic assert transform: #63538
fix: call instrumentationHook earlier for prod server: #63536
Revert "feat(next-core): support unsupported module runtime error (#63491)": #63575
Upgrades enhanced-resolve: #63499
Improve experimental test proxy: #63567
Remove the erroring on force-dynamic in static generation for app route: #63526
the argument might be written with underscores: #63600
Remove lodash from external packages list: #63601
upgrade @edge-runtime/cookies: [#63602](https://togithub.com/vercel/n

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

🦙 MegaLinter status: ✅ SUCCESS

Descriptor
Linter
Files
Fixed
Errors
Elapsed time

✅ COPYPASTE
jscpd
yes

no
1.12s

✅ CSS
stylelint
1
0
0
1.45s

✅ JAVASCRIPT
standard
1
0
0
1.53s

✅ JSON
eslint-plugin-jsonc
3
0
0
3.45s

✅ JSON
npm-package-json-lint
yes

no
0.51s

✅ JSON
prettier
3
0
0
0.34s

✅ JSON
v8r
3

0
9.76s

✅ MARKDOWN
markdownlint
8
0
0
0.6s

✅ MARKDOWN
markdown-link-check
8

0
2.04s

✅ MARKDOWN
markdown-table-formatter
8
0
0
0.34s

✅ REPOSITORY
gitleaks
yes

no
0.16s

✅ REPOSITORY
git_diff
yes

no
0.01s

✅ REPOSITORY
grype
yes

no
10.11s

✅ REPOSITORY
secretlint
yes

no
1.44s

✅ REPOSITORY
trivy
yes

no
5.98s

✅ REPOSITORY
trivy-sbom
yes

no
1.29s

✅ YAML
prettier
2
0
0
0.6s

✅ YAML
v8r
2

0
5.0s

See detailed report in MegaLinter reports
MegaLinter is graciously provided by


Update Popover.vue - fix auto close

Thank you for your wonderful component v-tooltip.
There is a bug in it:
It listens on window click event, and if the element clicked is outside the popover - the popover is closed.
BUT. the check if the element is inside the container, happens with a delay, therefore, if the element WAS inside, but on click is removed - then the popover won't know it was there.

Thanks, a fix was released in 2.0.2


[bug]: Install.bat failed, got ModuleNotFoundError: No module named 'torch'

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Windows
GPU
cuda
VRAM
8GB
What version did you experience this issue on?
3.1.1
What happened?
Failed to install InvokeAI via install.bat. Got "ModuleNotFoundError: No module named 'torch'".
Screenshots

Additional context
Windows 11, python 3.10.9, Using VPN but don't see any pip downloading promblem.
I was using 3.11 python according to the web docs and failed; then I saw the console prompt saying that 3.11 and above versions don't work, so I uninstalled 3.11 python and installed 3.10, but it still didn't work.
I just updated to release 3.1.1 and emptied the installation folder, but that didn't solve the problem either. Both fresh installs and folder overwrite installs (as shown in the picture) get the same error.
Contact Details
No response

Here's the results of my last run: CWindowssystem32cmd.exe.txt

Here's the results of my last run:
CWindowssystem32cmd.exe.txt

Could you try installing torch manually inside your venv?
pip install torch


Update actions to Node 20 & Deps update

GitHub is upgrading actions from Node 16 to Node 20, see the Changelog post. This PR should update all our used actions to their newest versions.
Will also do a dependency update once actions runs are successful

Ready for review :+1:


TestVolumesFromHasPriority fix race

this one would always fail for me locally
and yes, I took the easy way out on it :smiling_imp:

This is horrible :(
LGTM

ping @tiborvass ;P

Whoops sorry :S
LGTM


RFC: Do not implement safe navigation operator

This meta-RFC proposes removing the previously accepted RFC on safe navigation operator. This is probably going to be disappointing but I feel like this is the best course of action that reflects our ideals in language evolution.
Problem
The RFC specifies a new navigation operator, ?., that returns nil when the left hand side is nil, as well as skipping the rest of the indexed chain evaluation (e.g. vehicle.Turret?.Frame?.CFrame.LookVector evaluates to nil if vehicle.Turret or vehicle.Turret.Frame is nil). Initially the RFC only specifies this one operator, although future extensions like ?:, ?[], ?() are possible -- the RFC stands on its own, but it opens the path to more "nil-safe" operators in the future.
Unfortunately, we discovered a significant problem (after the RFC was merged) in the operator, in its interaction with the Roblox instance hierarchy. This is a userdata based DOM tree that (unfortunately) overloads __index to access children, and (fortunately?) attempting to access a non-existent child raises an error. As such, it's not compatible with this proposal in the sense that trying to use ?. in combination with the instance hierarchy will only work if the child is present, and will raise an error otherwise.
Importantly, in the previous example, vehicle.Turret is one of the accesses that may cause the problem - if Turret is a non-existing child, __index acess would throw, even though to a reader it may look as if ?. operator applied to the result of the operation handles the potential non-existence of Turret child by checking the result for nil.
Alternatives
There are several ways to address that problem and still ship this; all of them are unsatisfactory.
1. Change Instance.__index
We can change the instance hierarchy at Roblox to return nil instead.
If Luau existed 15 years ago with ?. feature, we probably would not have implemented dot-access in the first place, or maybe had it return nil... However, at present this is a very significant change that very dramatically changes the contract around instance access and may have large unintended consequences.
It's something that isn't obviously a good idea in the first place, and not something we'd want to do for a single language feature as other features may pull us into maintaining the status quo instead.
2. Just ship it
We can ignore this footgun and/or try to help with static analysis.
The issue here is that static analysis must depend on us knowing the precise type and tree location of the first object in the chain, something that will very often not work reliably, and the pattern is too convenient and too common - so we should probably admit that with or without analysis, people will be hitting this often accidentally.
Importantly, it's not even enough to know that ?. chain starts from an Instance -- some types of access, such as part.Attachment0?.Position, are safe, whereas some others, like part.Child?.CFrame, aren't, and to perform accurate analysis here it's insufficient to know the class type -- which is an unfortunate side effect of the way in which Roblox instances overload __index for child/property access.
This can be treated as a reasonable compromise - we're adding a convenient feature that requires a little care around some constructs, and as long as the users "know what they are doing" it's going to be okay - but my perspective is that we should try to keep the language as free of footguns / as orthogonal / as simple as possible, and any feature that has significant issues around these must be a critical feature we can't live without for us to tolerate these.
3. Add __safeindex
We can introduce a new metamethod, __safeindex, that will be called for ?. instead of __index, if present. This metamethod can then be defined for Roblox instance hierarchy to return nil.
It's important to note that this doesn't fully solve the problem as sometimes, like in the example in the problem statement, the issue is with __index (as a result of a regular . access!). To fully solve the footgun, any expression chain with ?. in it must switch to safeindex for all accesses instead, which complicates the metamethod relationship that usual operators have.
In addition, this violates the orthogonality / simplicity of the null safety operators in general - just for this one operator it now requires new VM opcodes, new table lookup functions that use either __safeindex or __index metamethods, and creates questions for any future null safety operators wrt whether or not we will go through the same process for consistency (eventually yielding __safecall, __safenewindex, __safeadd etc. in the extreme), or if __safeindex is a one-off ad hoc addition to solve a specific problem we have for one of the (well, largest) users of Luau language.
This in general turns the safe navigation operator from "cheap convenient syntax sugar" to "full blown operator every element of the stack must be aware of with a custom metamethod that plays by very special rules", which in my perspective shifts the balance for this feature, as the costs no longer seem to justify the benefit.
4. Use pcall
We could automatically add pcall to chains with safe navigation operator, and convert the error to nil.
The problem here is that it's very inefficient compared to a simple property access with the existing implementation options for error handling in VM (so it conflicts with performance goals), and conflates the source of runtime error between whether the element is actually nil or some intermediate part of the chain threw a legitimate error that got swallowed, which hides errors (which conflicts with robustness goals a little bit, depending on how you understand robustness).
For example, vehicle?.CFrame will return nil if vehicle is nil, but it will also catch any other error, such as one that results from vehicle.CFrame access if vehicle is not nil. Note that it's also necessary to pcall the entire chain, not just handle the error during __index execution when evaluating ?., since sometimes, like in the example in the problem statement, the issue is with a regular . access preceding ?. in the chain, not with ?. access itself. This increases the scope of error silencing further.
Conclusion
While we have ways forward for this proposal, they either make the language less robust [when used in Roblox environment], mean this feature is much less orthogonal/simple than initially understood, or mean we need to dramatically change the access rules [in Roblox environment] for a single small language feature.
While it's unusual to judge a feature of a general purpose language based on a single user of the said language, given Luau's heritage and the fact that the majority of the programmers who interact with Luau presently use it in context of Roblox, I think we must take this into account. These situations will probably happen rarely - in fact it's the first feature proposal like this! - but when they do, we should strive to keep the language simple and devoid of footguns, thus I believe it's overall beneficial to maintain the status quo and not implement this proposal.
As suggested in the RFC, this still means you can use and operator as a replacement for very basic single-element chains, e.g. dog and dog.name, but for more complex chains with nils unfortunately the existing longer patterns must be used. We plan to look into common subexpression elimination that, under certain conditions, will allow us to maximally efficiently evaluate seemingly redundant expressions like foo and foo.bar and foo.bar.baz, and if that doesn't work you'd need to settle for multiple expressions to evaluate these chains efficiently in presence of nils - that said, I think in this case shorter code for some cases like this is not a strong enough motivation to ship the feature in the face of the problem discussed above.
cc @Kampfkarren and #142 for visibility

What's the downside of having ?. consume errors from __index? I assume that wouldn't be a good idea, but I'm having trouble thinking of a case where I wouldn't want ?. to still return nil.

This is noted in p4 - in addition to performance issues, it masks errors, which may lead to code paths you thought would work to not work. For example, vehicle?.CFrame where vehicle never has a CFrame property to begin with (nor does it have a CFrame child).

Why would you use ?. to access a property though? If you're using ?. then presumably you acknowledge the fact that it might not exist, whereas properties are fixed so you shouldn't be concerned with them not existing. In your example, if I've written vehicle?.CFrame then that means I have reason to suspect that vehicle might or might not have a CFrame (maybe it could be multiple types in this function) and I would otherwise need to write several checks, if it exists as a property or a child, to get the same result. (There's no good way to test if an Instance has a property though, but I could test its type or use a pcall.)

If you're using ?. then presumably you acknowledge the fact that it might not exist

You’d use it if you wanted to handle the case when vehicle is nil, and get nil as a result.

Really disappointed, but not unexpected after the last discussions we had, and I don't have any outstanding objections. It's unfortunate because most of my usage around ?. would be based around data structures, rather than instances.

(in fact actually safeindex doesn’t solve the problem fully either because ‘foo.bar?.baz’ would still error if foo.bar does, so it would only solve the issue if all accesses in the path use ?.)

Have we considered adding a new parameter to __index? Perhaps a third argument could provide additional information to Instance.__index. For example, a boolean that describes whether the index is nil-forgiving. If true, Instance.__index would return nil instead of raising an error.

(in fact actually safeindex doesn’t solve the problem fully either because ‘foo.bar?.baz’ would still error if foo.bar does, so it would only solve the issue if all accesses in the path use ?.; similarly for pt4 it doesn’t fully resolve the issue unless you wrap the entire expression that contains ?. in a pcall because the footgun is due to a regular index access that errors instead of returning nil)

I feel the use cases of ?. for child accesses are actually invalidated just by the problems child accesses through . pose in the first place. My stance is that child accesses through . is more of a deprecated feature, and I don't think it should be embraced.
Rather, I would much prefer a more convenient way (that is not a feature of luau) to perform chained :FindFirstChild calls, which solves the same problem as ?. for child accesses without embracing . for child accesses. That is also the perfect opportunity to find a general solution for the numerous :Find and :WaitFor variants that are slowly sneaking their way into the engine.
After all, Instances are not a thing in plain luau, nor is this problem a thing in plain luau, so, it does make some sense that this problem is not a luau problem as much as it is a Roblox one (not that the two are not tangled with eachother or anything)

Have we considered adding a new parameter to __index? Perhaps a third argument could provide additional information to Instance.__index. For example, a boolean that describes whether the index is safe. If true, Instance.__index would return nil instead of raising an error.

I also thought of this, and, it sounded appealing to me too at first.
Unfortunately the primarily problem is that it is not very flexible. Appending an additional argument to various metamethods for explicitly just this safety feature means similar problems to just adding new metamethods, more branching, and a little clutter.
I think the most flexible point for change to occur is in the fact that parent.Child will throw if Child is not a property, which has complications.

Catching up:

A third argument to __index doesn't solve the problem in the same way that __safeindex doesn't solve the problem fully.

I agree that the fact that . is used for child access is unfortunate, but from the perspective of this RFC it doesn't remove the problem - it's used a lot today, after all; it's unfortunately not possible for us to go back on . being used for child access for compatibility. For similar reasons we can't really "deprecate" this in any reasonable sense of the word.

Importantly, in the previous example, vehicle.Turret is one of the accesses that may cause the problem - if Turret is a non-existing child, __index access would throw, even though to a reader it may look as if ?. operator applied to the result of the operation handles the potential non-existence of Turret child by checking the result for nil.

Have we considered adding a new parameter to __index? Perhaps a third argument could provide additional information to Instance.__index. For example, a boolean that describes whether the index is safe. If true, Instance.__index would return nil instead of raising an error.

I would think the only way safe indexing would stop Instance.Child from erroring using this third argument is by changing what __index's third argument refers to. From an implementation perspective, it would be the most intuitive to make the third argument refer directly to the type of index.
--      VV '?.' means arg #3 is true
Instance?.Child

However, this can lead to errors in partial safe indexing.
--      V This errors although we are unsure if `Child` exists!
Instance.Child?.Grandchild

The problem is solved if arg #3 refers to the type of the next index. In the above case, the first index should receive a boolean true argument indicating that the next operator is safe. It should be false when the next operator is unsafe or there is no operator after it.
--     [1]    VV '?.' means arg #3 is true for [1]
Instance.Child?.Grandchild

If Instance does not exist, it will error with attempt to index a nil value.

This makes sense because we are confident Instance exists, and we would've used Instance?.Child if not.

If Instance.Child does not exist, it will return nil because argument 3 was true and break the index chain.

If Child.Grandchild does not exist, it will error with Grandchild is not a valid member of Child.

This makes sense because we are also confident Grandchild exists, and we would've used Child?:FindFirstChild("Grandchild") or split the expression if not.

In general, given an index chain A . B . C . D...,

If the first index A ?. B... is safe, just replace the chain with A ~= nil and A . B . C . D...

If any further indexes in the chain ...R . S ?. T... are safe, give R.S a third argument of true if it has an __index and replace the chain with ...R . S ~= nil and ...R . S . T....

To further clarify, R.S can also be a safe index i.e. R?.S. Both index types will receive a third argument of true because S?.T is a safe operation.
I would also argue that this behavior is still intuitive, but the third argument would have to mean something that isn't the type of index. For example, it could describe whether the resulting value is "nilable."

This may be an unpopular opinion but I think dropping this feature is actually better for the long run.
Correct me if I'm wrong but there would have been some runtime overhead to the ?. operator, right? Since ?. is so easy to type, it could lead into defensive coding style (especially among less experienced programmers) where ?. is overused. If carried out too far and in perf critical sections, this could result in death by thousand cuts perf issues.
FWIW, I have programmed in Lua for the past ~11 years almost daily and I can't think of a single instance where I would have actually missed this feature. Maybe this construct would be more useful with certain programming styles or data models, I don't know. I have to confess I'm not familiar how Roblox API or data is structured.
The example given in the original RFC is:
local dogName = nil
if dog ~= nil then
    dogName = dog.name
end

=>

local dogName = dog?.name

I'm not sure I completely understand the motivation of the RFC... Why would dog be nil in the first place? In my experience it's usually better to write code so that variables and function arguments are expected to have known types. With this approach dog being nil would very likely be a bug which should be catched as early as possible. With defensive coding nils would be propagated and tracking the error to the source becomes more difficult.
I know I'm late to the party, sorry about that.

@goldenstein64 You're correct in that changing the value of the third argument based on the next operation in the chain would work. But that goes even further against the general principle of metamethods (which makes this even more adhoc / less pure) and doesn't alleviate the other concerns wrt implementation.

Since this has been pending for more than two weeks and the substance of the issue haven't changed I'm going to merge this, thereby removing the original RFC. Thanks everyone for discussion!

I don't understand why this was vetoed.
We have reliable methods for indexing children without errors, such as FindFirstChild and its counterparts. Directly indexing instances, i.e. instance.foo.bar is intentional; it communicates to both the reader and the VM that these instances should exist, and if they don't, an error should be thrown.

instance.foo returns Instance, and is functionally equivalent to assert(FindFirstChild("foo"))
FindFirstChild("foo") returns Instance | nil

The sole purpose of ?. is to suppress nil values. It should not catch errors or silently wrap them in pcalls.
For those familiar with Zod, this is like doing z.string().parse(...)?.toUpperCase() and being upset that ?. doesn't catch errors from parse. The parse method asserts, you should instead use safeParse to avoid errors on failure.
In Roblox terms, safeParse is like FindFirstChild.
Currently when doing FFC chains, the lack of an optional index operator forces you to:
-- clunky way
local result = instance.Parent
if result then
    result = result:FindFirstChildWhichIsA("Humanoid")
    if result then
        result:TakeDamage(100)
    end
end

or
-- equally clunky, one-liner way
instance.Parent and instance.Parent:FindFirstChildWhichIsA("Humanoid") and instance.Parent:FindFirstChildWhichIsA("Humanoid"):TakeDamage(100)

Using optional indexing would simplify this drastically:
instance.Parent?:FindFirstChildWhichIsA("Humanoid")?:TakeDamage(100)

I think the reasoning behind this PR is flawed and was acted on prematurely (no offense ofc). Releasing this as-is would've been more than satisfactory for everyone.
This should be looked into again in the future if possible.

You seem to argue for having ?: operator, while the RFC that has been removed was for a different operator - ?..
Having ?. available doesn't open a path for having ?:, that one was rejected for a different set of problems https://github.com/luau-lang/luau/pull/142#issuecomment-990563536


⚠ RPC server - Figment Solana has degraded performance

In 2ddacfd, RPC server - Figment Solana ($FIGMENT_SOLANA_RPC_URL) experienced degraded performance:

HTTP code: 429
Response time: 127 ms

Resolved: RPC server - Figment Solana performance has improved in 778a909.


Fix migrations

Needed to add version number for Rails 5.1 upgrade and was missing some
translation migrations

👍


Problem names must be more than a number

This is an odd edge-case, but as it stands, if you name a problem a number, say 12, then when you do any sort of get on the problem e.g. /api/problems/12, the problem with PID 12 will be returned. I like the idea of being able to access problems from their PID, so I think that we should restrict problems from being named only numeric values. In a way, this falls under form-validation, but I don't think anyone mentioned it.

I created a custom form validator that gives an error if the problem name is only numbers. It also disables the save button until it is correct.

Please don't close the issue until the changes have been merged into master

Ah, sorry about that. Hopefully they will be merged soon!

No problem, and thank you for commenting so it's public that you're working on it.
You can actually mention issues in your PR, and when the PR gets merged the issue will automatically close. Just put something like "Fixes #53" in the PR description

Cool! I didn't realize that was a thing. I'll definitely add that to my next commits

This change has been added to master. Can I close this issue now?

Sure


[IOS] RN 0.27 Can't use whole view with Action Button on it

Hey,
I have the Action Button for a while now. It started well and everything works fine. But since the last update I have an weird Problem. The Action Button Component seems to be over the whole View. As I try to Touch my Buttons I can't reach them. So I started the Inspector and clicked on an Button an whups there I got the ActionButton backdrop for the whole screen. As I deleted the Button out of my project everything works again fine.
PLS fix asap.
Cheers
Alex

its fixed in v1.1.11


Project setting: show parameters

Now with presets, we might want to show parameters only in dev, or not at all

Should be a general setting maybe?


[Installation] Fail to install with conda environment on Mac

Hi,
I'm trying to install gfootball with pip in a conda environment following compile_engine.md and I come across the following issues:
      -- Detecting CXX compile features - done
      -- Found OpenGL: /Library/Developer/CommandLineTools/SDKs/MacOSX13.1.sdk/System/Library/Frameworks/OpenGL.framework
      CMake Error at CMakeModules/FindPackageHandleStandardArgs.cmake:110 (MESSAGE):
        Could NOT find SDL2_image (missing: SDL2_IMAGE_LIBRARIES
        SDL2_IMAGE_INCLUDE_DIRS)
      Call Stack (most recent call first):
        CMakeModules/FindPackageHandleStandardArgs.cmake:301 (_FPHSA_FAILURE_MESSAGE)
        CMakeModules/FindSDL2_image.cmake:104 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
        CMakeLists.txt:56 (FIND_PACKAGE)

      -- Configuring incomplete, errors occurred!
      See also "/private/var/folders/h9/hrvgm2ms1vqbj81fm676_rt00000gn/T/pip-install-x0hs__f9/gfootball_5ce06935c5fb4999b2c0b998064c5633/third_party/gfootball_engine/CMakeFiles/CMakeOutput.log".
      See also "/private/var/folders/h9/hrvgm2ms1vqbj81fm676_rt00000gn/T/pip-install-x0hs__f9/gfootball_5ce06935c5fb4999b2c0b998064c5633/third_party/gfootball_engine/CMakeFiles/CMakeError.log".
      gfootball/build_game_engine.sh: line 29: pushd: third_party/gfootball_engine: No such file or directory
      error: Google Research Football compilation failed
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure

× Encountered error while trying to install package.
╰─> gfootball

It says SDL2_image is not installed though I installed it with brew and I can see the folder /opt/homebrew/Cellar/sdl2_image.
Could you kindly give some suggestions on debugging this issue? Thank you very much.

same problem

Hi
Did anyone find a fix for this?

Hi Did anyone find a fix for this?

Not really. What I do instead is to install it on the Linux server and download the visualization....

I could fix it by pasting SDL2_image.framework folder in /Library/Frameworks folder. The installation was successful. I can run the code without rendering the game.
I guess rendering will not work on apple silicon. Where you able to get the video replays?


fix: 修改dockerfile编写方式

使用turborepo的prune --docker功能（ https://turbo.build/repo/docs/handbook/deploying-with-docker ）以及pnpm deploy（ https://pnpm.io/cli/deploy ）功能来重新编写dockerfile，有以下好处：

无需手动在dockerfile中根据库之间的依赖关系来复制文件
构建好的镜像中构建的文件只有一个层

有以下问题：

构建镜像过程需要网络的步骤现在有3步：pnpm fetch获取所有依赖、pnpm dlx安装turbo cli、pnpm deploy整理构建好的文件（之后只有pnpm fetch一步），会影响本地构建镜像的速度。理论上来说pnpm dlx和pnpm deploy都不应该需要网络，因为所有包都已经在pnpm fetch步骤获取到。已经向pnpm提交反馈（https://github.com/pnpm/pnpm/discussions/5761）
pnpm deploy会根据package.json中的files字段来仅复制需要的文件，但是它只会影响发布的包（也就是apps/中的包），被依赖的内部包（libs下的包）的所有文件都会被复制到最终的镜像中（设置了files字段也一样）。所以，此方法构建的镜像大小会比之前大一点（因为包含了libs下包的源代码），当前是1M-2M左右

Codecov Report
Base: 64.68% // Head: 64.46% // Decreases project coverage by -0.22% :warning:

Coverage data is based on head (b600cce) compared to base (d8c0d63).
Patch coverage: 42.85% of modified lines in pull request are covered.

:exclamation: Current head b600cce differs from pull request most recent head 936197f. Consider uploading reports for the commit 936197f to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #369      +/-   ##
==========================================
- Coverage   64.68%   64.46%   -0.23%
==========================================
  Files         102      102
  Lines        2843     2873      +30
  Branches      353      361       +8
==========================================
+ Hits         1839     1852      +13
- Misses        959      976      +17
  Partials       45       45

Impacted Files
Coverage Δ

apps/mis-server/src/plugins/price.ts
65.47% <ø> (ø)

apps/portal-server/src/services/app.ts
10.66% <0.00%> (-0.15%)
:arrow_down:

apps/portal-server/src/clusterops/slurm/app.ts
16.29% <11.11%> (-0.92%)
:arrow_down:

libs/ssh/src/ssh.ts
54.28% <14.28%> (-2.06%)
:arrow_down:

...s-server/src/migrations/Migration20221213020347.ts
55.55% <55.55%> (ø)

apps/mis-server/src/plugins/clusters.ts
47.91% <80.00%> (+3.47%)
:arrow_up:

apps/mis-server/src/entities/JobInfo.ts
92.18% <100.00%> (+0.12%)
:arrow_up:

apps/mis-server/src/tasks/fetch.ts
92.00% <100.00%> (+0.10%)
:arrow_up:

apps/portal-server/src/utils/turbovnc.ts
86.20% <100.00%> (ø)

libs/libconfig/src/parse.ts
94.11% <100.00%> (+2.45%)
:arrow_up:

... and 1 more

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.


Added negotiate tests

I don't quite understand why it is necessary to order the processors.  Can you elaborate?

If you have a processor that handles collection+json but if it's last in
the array the json processor will handle it before the custom one. Custom
ones should always be looped on first.
On Thursday, 12 November 2015, Phil Cleveland<EMAIL_ADDRESS>wrote:

I don't quite understand why it is necessary to order the processors. Can
you elaborate?
—
Reply to this email directly or view it on GitHub
https://github.com/jchannon/negotiator/pull/7#issuecomment-156231183.

I wonder if a simpler solution is to not have default processors. Instead have the user pass in processors to New in prioritized order.
In addition I also think that having CanProcess be more strict would help.  For instance instead of strings.HasSuffix(mediaRange, "json) it could be strings.EqualFold(mediaRange, "application/json"). Really the json processor shouldn't be used for collection+json right?

Right but it could be used for patch json
Tbh the design of negotiator I've borrowed from Nancy :)
On Thursday, 12 November 2015, Phil Cleveland<EMAIL_ADDRESS>wrote:

I wonder if a simpler solution is to not have default processors. Instead
have the user pass in processors to New in prioritized order.
In addition I also think that having CanProcess be more strict would help.
For instance instead of strings.HasSuffix(mediaRange, "json) it could be
strings.EqualFold(mediaRange, "application/json"). Really the json
processor shouldn't be used for collection+json right?
—
Reply to this email directly or view it on GitHub
https://github.com/jchannon/negotiator/pull/7#issuecomment-156248371.

Gotcha


skip validation on unreleased proposals

closes: #146

Using UNRELEASED_UPGRADE or any value from the plan name won't work for dev release branches

Example: https://github.com/Agoric/agoric-sdk/pull/9242/files#diff-6794d7dc96f919b87faf6868d2d642e3c3eb44e9689b3b4745437f4de869f9b5
https://github.com/Agoric/agoric-sdk/blob/2f0f1c4fc08633f246e69fa626172698e96e3072/a3p-integration/proposals/a:upgrade-15/package.json#L2-L8
  "agoricProposal": {
    "releaseNotes": "https://github.com/Agoric/agoric-sdk/releases/tag/agoric-upgrade-15",
    "sdkImageTag": "unreleased",
    "planName": "agoric-upgrade-15",
    "upgradeInfo": {},
    "type": "Software Upgrade Proposal"
  },


Enable Link-Time Optimization (LTO)

Hi!
I noticed that in the Cargo.toml file Link-Time Optimization (LTO) for the project is not enabled. I suggest switching it on since it will reduce the binary size (always a good thing to have) and will likely improve the application's performance a bit.
I suggest enabling LTO only for the Release builds so as not to sacrifice the developers' experience while working on the project since LTO consumes an additional amount of time to finish the compilation routine. If you think that a regular Release build should not be affected by such a change as well, then I suggest adding an additional dist or release-lto profile where additionally to regular release optimizations LTO will also be added. Such a change simplifies life for maintainers and others interested in the project persons who want to build the most performant version of the application. Using ThinLTO should also help to reduce the build-time overhead with LTO. If we enable it on the Cargo profile level, users, who install the application with cargo install, will get the LTO-optimized version "automatically". E.g., check cargo-outdated Release profile.
Basically, it can be enabled with the following lines:
[profile.release]
lto = true

Thank you.
P.S. It's more like an improvement idea rather than a bug. I created the issue just because the Discussions are disabled for the repo for now.

Good catch, I've just recently started updating a bunch of Cargo files in my projects but have not yet gotten to this one yet. I'll add it.
Thanks for the suggestion.

Will be included in next release.
https://github.com/replicadse/complate/commit/97257b9660680e28c685826832aab49694850316#diff-2e9d962a08321605940b5a657135052fbcef87b5e360662bb527c96d9a615542R50


Some trees only drop sticks?

Describe the bug
Felling certain trees appear to result in nothing but sticks or only 1 log:
Minecraft: Birch
Biomes O' Plenty: Ebony (Yes, the add on is installed as well)
Biomes O' Plenty: Eucalyptus
Biomes O' Plenty: Fir
Minecraft: Dark Oak
Minecraft: Jungle (This makes no sense, I've broken several very tall Jungle trees and only received sticks)
Narrow trees like the Birch will "revert" to the smallest form of log (like the end of the branches) before falling over.
This occurs even to trees that have their trunk as wide/large as the block they sit on.
To Reproduce
Steps to reproduce the behavior:
Chop down a Dynamic Tree of any of the above listed
Mods List
FML: MCP 9.42 Powered by Forge <IP_ADDRESS>23
Dynamic Trees v1.12.2-0.9.4
Dynamic Trees BOP v1.12.2-1.4.1e
Dynamic TreesPHC v1.12.2-1.4.2
Tinker's Construct v1.12.2-<IP_ADDRESS>
And several other non-world specific related mods.. If these are needed I will try to compile entire list.
NOTES
I will try to add to this ticket as I find more that behave the same way, so far these are all I've noticed behaving this way.
It makes it incredibly difficult to harvest wood from trees that appear to be full-grown.

:|
I was still waiting to hear what would become of this issue.
Kind of a real let-down to only see it "Closed" after waiting this long.

I closed it because it was a mod conflict on an older version. It's nearly impossible to identify those without a full list and tracing the code is not worth the devs' time. Therefore, unless you have a specific bug, it's highly unlikely that it'll be fixed.


Cannot use on windows

On Windows 10 64bits, when I run the exe file I get the following message:

Strangely, using 7-zip to unzip ends with not everything unziped, and using explorer to look inside the zip file don't show all files, but, instead, only those that managed to be unziped by 7-zip:

Force copying from 7-zip works, but then I got the before mentioned error. Looking at the files from 7-zip it seems there is some malformation on it's creation:

Seems to me that some folders, such as bin and gt-extra, were not zipped correctly, or not recognized as such.

Please try unzipping with File Explorer.

Using the windows file explorer to unzip render the same result of the 7-zip

Could it be a damaged/incomplete download? I use 7-zip for GT and have never had any issues.

I download twice on two different computers with Windows 10 installed and tested the unzip with 7-Zip latest version.
But now I figured that using windows explorer works. I thought the exe would be on the folder root, but it is inside bin — my bad.
I don't know why 7zip open it wrongly, maybe it is a problem with 7zip itself.


Handle casing in usernames

Cased variations should be considered duplicates. Need to do a lower case comparison.
i.e. satoshi vs Satoshi vs SAToshi

Maybe the API lowercases all strings before checking/adding to Cloudflare?