Improve git permissions guidance in docs/other/windows.md

I disagree with your suggested approach regarding workflow on windows. I figured it would be better to start with an issue rather than submitting a PR.
There are a number of advantages to being able to work directly in the VM rather than through the shared folder (speed, consistency when it comes to deployment, etc.). Because we always use a fix permissions script as part of the build process, we don't worry too much about the permissions in the repo, so anytime windows is in the picture we have git ignore file mode changes:
git config core.fileMode false

It seems to me that would be better guidance to give people as it would make their use of drupalvm more flexible.

And to be clear, are you suggesting setting that as a global inside the VM, or recommending it for Windows users on the host? (Or both?)

I usually do it in both places if I think I'm going to be touching the files from the host at all.


Why  the "java.security.auth.login.config" or "java.security.krb5.conf"  is needed for  HadoopJobHistoryNodeExtractor?

In java code  file(HadoopJobHistoryNodeExtractor.java,line 91) , the code force us to  config at least one of them？
if (System.getProperty("java.security.auth.login.config") == null
|| System.getProperty("java.security.krb5.conf") == null) {
throw new Exception("Can't find java security config files");
}

@superwood for a Hadoop w/o security configured, this may not be needed.
A warning in log can be sufficient.

#299 should relax the expectation for krb5.conf and gss-jaas.conf.
If your Hadoop cluster is secured by Kerberos, you have to provide both config files accordingly.


Project chat?

Is this a BUG REPORT or FEATURE REQUEST?:
feature
Would y'all be open to creating a Gitter/Discord/Slack or some other form of chat for Resumic? It might make lightweight conversations about new features or asking questions/quick communications easier, plus provide a way for the community to give feedback and participate. Totally understand if we wanna stick to Issues for right now, but just thought I'd throw the idea out! 😄

There is a basecamp, but we haven't publicly linked or pushed people there. For now I added a short link for the opt-in link: s.resumic.org/chat
Happy to iterate, if this makes sense in the long run as I find discord might be something better in terms of keeping information long term, but then we usually use issues for this.


“abort” in ControlService::snapshotInhibitSet

Function ControlService::snapshotInhibitSet  in Server/ControlService.cc
The variable “abort” is initialized as false.
And no other place set it true.
So in line 248, it is always false, and never do stopTakingSnapshot.
Whether is should be initialized as true here?
Thanks.

Good find. I think it should be initialized as true. What's supposed to happen is documented here: https://github.com/logcabin/logcabin/blob/v1.1.0/Protocol/ServerControl.proto#L226


Silenced resolution events with expire_on_resolve should be handled

Closes https://github.com/sensu/sensu/issues/1512

Hmm, we need to just exclude the silenced entry that expire on resolve, there may be others that do not.


Add ability to insert args to node-exporter container

Useful if you'd like to enable a collector from https://github.com/prometheus/node_exporter#disabled-by-default

I think this should be done with plain jsonnet as a patch in downstream usage.


Gridsome won't build – Cannot read property 'tapAsync' of undefined

Description
My project use to build on a Mac Intel with Node v14.15.
However, Gridsome won't build with Node v15.0.1. I'm also now on an M1 Mac. I had previously fixed the Sharp issue. I removed the package-lock.json file, node modules, etc. Now when trying to run gridsome build, I get the following:
(BTW, Gridsome will still run in development gridsome develop.)
(node:26617) ExperimentalWarning: AbortController is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
Create GraphQL schema - 19.53s
Create pages and templates - 4.75s
Generate temporary code - 0.04s
Bootstrap finish - 27.18s
0% compilingTypeError: Cannot read property 'tapAsync' of undefined
    at /Volumes/Evo/Sites/mtype-alpha/node_modules/vue-server-renderer/server-plugin.js:52:39
    at SyncHook.eval [as call] (eval at create (/Volumes/Evo/Sites/mtype-alpha/node_modules/gridsome/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:19:10), <anonymous>:13:1)
    at SyncHook.lazyCompileHook (/Volumes/Evo/Sites/mtype-alpha/node_modules/gridsome/node_modules/webpack/node_modules/tapable/lib/Hook.js:154:20)
    at Compiler.newCompilation (/Volumes/Evo/Sites/mtype-alpha/node_modules/gridsome/node_modules/webpack/lib/Compiler.js:631:26)
    at /Volumes/Evo/Sites/mtype-alpha/node_modules/gridsome/node_modules/webpack/lib/Compiler.js:667:29
    at AsyncSeriesHook.eval [as callAsync] (eval at create (/Volumes/Evo/Sites/mtype-alpha/node_modules/gridsome/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
    at AsyncSeriesHook.lazyCompileHook (/Volumes/Evo/Sites/mtype-alpha/node_modules/gridsome/node_modules/webpack/node_modules/tapable/lib/Hook.js:154:20)
    at Compiler.compile (/Volumes/Evo/Sites/mtype-alpha/node_modules/gridsome/node_modules/webpack/lib/Compiler.js:662:28)
    at /Volumes/Evo/Sites/mtype-alpha/node_modules/gridsome/node_modules/webpack/lib/Compiler.js:321:11
    at Compiler.readRecords (/Volumes/Evo/Sites/mtype-alpha/node_modules/gridsome/node_modules/webpack/lib/Compiler.js:529:11)
    at /Volumes/Evo/Sites/mtype-alpha/node_modules/gridsome/node_modules/webpack/lib/Compiler.js:318:10
    at AsyncSeriesHook.eval [as callAsync] (eval at create (/Volumes/Evo/Sites/mtype-alpha/node_modules/gridsome/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
    at AsyncSeriesHook.lazyCompileHook (/Volumes/Evo/Sites/mtype-alpha/node_modules/gridsome/node_modules/webpack/node_modules/tapable/lib/Hook.js:154:20)
    at /Volumes/Evo/Sites/mtype-alpha/node_modules/gridsome/node_modules/webpack/lib/Compiler.js:315:19
    at AsyncSeriesHook.eval [as callAsync] (eval at create (/Volumes/Evo/Sites/mtype-alpha/node_modules/gridsome/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:15:1)
    at AsyncSeriesHook.lazyCompileHook (/Volumes/Evo/Sites/mtype-alpha/node_modules/gridsome/node_modules/webpack/node_modules/tapable/lib/Hook.js:154:20)

Paste the information here as shown by gridsome info
System:
    OS: macOS 11.4
    CPU: (8) arm64 Apple M1
  Binaries:
    Node: 15.0.1 - ~/.nvm/versions/node/v15.0.1/bin/node
    Yarn: 1.22.11 - /opt/homebrew/bin/yarn
    npm: 7.0.3 - ~/.nvm/versions/node/v15.0.1/bin/npm
  Browsers:
    Chrome: 92.0.4515.131
    Firefox: 91.0
    Safari: 14.1.1
  npmPackages:
    @gridsome/remark-prismjs: ^0.5.0 => 0.5.0
    @gridsome/source-filesystem: ^0.6.2 => 0.6.2
    @gridsome/source-graphql: ^0.1.0 => 0.1.0
    @gridsome/transformer-remark: ^0.6.4 => 0.6.4
    gridsome: ^0.7.0 => 0.7.23
    gridsome-source-rss: ^1.0.0 => 1.0.0
    gridsome-source-static-meta: ^1.0.1 => 1.0.1

BTW, I didn't have the issue when installed my dependencies with yarn install only npm install

I have the same problem with following gridsome info:

  System:
    OS: macOS 10.15.7
    CPU: (4) x64 Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz
  Binaries:
    Node: 16.6.2 - /usr/local/bin/node
    Yarn: 3.0.1 - /usr/local/bin/yarn
    npm: 7.20.3 - /usr/local/bin/npm
  Browsers:
    Chrome: 91.0.4472.114
    Safari: 14.0.1
  npmPackages:
    @gridsome/plugin-sitemap: ^0.4.0 => 0.4.0
    @gridsome/source-filesystem: ^0.6.2 => 0.6.2
    @gridsome/transformer-remark: ^0.6.4 => 0.6.4
    gridsome: ^0.7.23 => 0.7.23
    gridsome-plugin-algolia: ^2.1.4 => 2.1.4
    gridsome-plugin-i18n: ^1.6.0 => 1.6.0
    gridsome-plugin-ogp: ^0.0.14 => 0.0.14
    gridsome-plugin-robots-txt: ^1.0.2 => 1.0.2
    gridsome-plugin-rss: ^1.2.0 => 1.2.0
    gridsome-plugin-tailwindcss: ^4.1.1 => 4.1.1
    gridsome-plugin-typescript: ^0.4.0 => 0.4.0
    gridsome-source-graphql-prismic: ^0.1.6 => 0.1.6

Same issue here
  System:     OS: macOS 12.1     CPU: (8) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz   Binaries:     Node: 17.3.0 - /usr/local/bin/node     npm: 8.3.0 - /usr/local/bin/npm   Browsers:     Chrome: 97.0.4692.71     Edge: 97.0.1072.55     Firefox: 91.4.1     Safari: 15.2   npmPackages:     @gridsome/plugin-google-analytics: ^0.1.0 => 0.1.2      @gridsome/plugin-sitemap: ^0.4.0 => 0.4.0      @gridsome/remark-prismjs: ^0.5.0 => 0.5.0      @gridsome/source-filesystem: ^0.6.2 => 0.6.2      @gridsome/transformer-remark: ^0.6.4 => 0.6.4      gridsome: ^0.7.23 => 0.7.23      gridsome-plugin-gtag: ^0.1.10 => 0.1.10    npmGlobalPackages:     @gridsome/cli: 0.3.4

Same by me:
gridsome info
System:
OS: macOS 12.1
CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
Binaries:
Node: 17.4.0 - ~/.nvm/versions/node/v17.4.0/bin/node
Yarn: 1.22.17 - /usr/local/bin/yarn
npm: 8.3.1 - ~/.nvm/versions/node/v17.4.0/bin/npm
Browsers:
Chrome: 97.0.4692.99
Firefox: 96.0.3
Safari: 15.2
npmPackages:
gridsome: ^0.7.0 => 0.7.23
gridsome-plugin-typescript: ^0.4.0 => 0.4.0
npmGlobalPackages:
@gridsome/cli: 0.3.4

Same issue here - any solutions?
System:
OS: Windows 10 10.0.19043
CPU: (12) x64 Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz
Binaries:
Node: 16.3.0 - ~\AppData\Local\Volta\tools\image\node\16.3.0\node.EXE
Yarn: 1.22.5 - C:\Program Files\Volta\yarn.EXE
npm: 7.20.2 - ~\AppData\Local\Volta\tools\image\npm\7.20.2\bin\npm.CMD
Browsers:
Chrome: 97.0.4692.99
Edge: Spartan (44.19041.1266.0), Chromium (97.0.1072.76)
npmPackages:
@gridsome/source-filesystem: ^0.6.2 => 0.6.2
@gridsome/transformer-remark: ^0.6.4 => 0.6.4
gridsome: ^0.7.0 => 0.7.23
gridsome-helper-json: ^1.0.3 => 1.0.3
gridsome-plugin-pwa: ^0.0.21 => 0.0.21

I sadly cannot come up with a solution. But at least I found "the issue" in my project. Gridsome interally uses webpack 4.x, but in mx project I was using webpack 5. Somehow somewhere inside the gridsome dependency chain, some webpack 5 parts pierced threw. As I uninstalled my webpack 5 for testing, I could compile gridsome without problems.
As I said, not a real solution for the general problem. In my case I could switch to webpack 4 on project level and ignore the problem for now. Maybe this works as well for others ...

To anyone else who encounters this issue, I managed to fix it by downgrading the major version of these 2 packages from 5 to 4:
"@vue/cli-plugin-eslint": "^4.5.16",
"@vue/cli-service": "^4.5.18"

The 5th version of each of these depend on Webpack v5. By downgrading them they become dependent on v4.
I'm also using Node v16 (with NVM) and have switched from using Node to Yarn for package installation (due to some unrelated issues).


Display stat sums in loadout

 Issue by Trimatix
Sunday Aug 02, 2020 at 11:44 GMT
Originally opened as https://github.com/Trimatix/GOF2BountyBot/issues/16

Sum stats an place below base ship stats, e.g total armour, dps, etc.

this gets requested a lot, e.g: https://discord.com/channels/711548456019296289/711548456568750102/1061292833807540284


[proj4] update port

Update port and fix core build (there was no feature that you can turn off, it was always required (was default feature so nobody checked it))

Package proj4 does not have a database feature
Note: Updating vcpkg by rerunning bootstrap-vcpkg may resolve this failure.

Package proj4 does not have a database feature

I think this is a bug in the ci, or can you otherwise explain this error?

Port mapnik explicitly depends on proj[database]. Key proj data is stored in a sqlite database, so practically everyone needs it.

Package proj4 does not have a database feature

I think this is a bug in the ci, or can you otherwise explain this error?

Port mapnik explicitly depends on proj[database]. Key proj data is stored in a sqlite database, so practically everyone needs it.

Aah. Yeah the project also does not build without database feature (there is no database feature you can turn off, it then simply fails to find the sqlite executable)

@autoantwort
https://github.com/microsoft/vcpkg/blob/c26101d71e1e3f8a8a010bf6854c983ab777b9e9/ports/mapnik/vcpkg.json#L152-L162

When building python3:x64-osx:
install: mkdir /Users/vagrant/Data/packages/python3_x64-osx/Users/vagrant/Data/installed/x64-osx/debug/lib: File exists
make: *** [altbininstall] Error 71
make: *** Waiting for unfinished jobs....

I saw this error before, is that related to your changes?

When building python3:x64-osx:
install: mkdir /Users/vagrant/Data/packages/python3_x64-osx/Users/vagrant/Data/installed/x64-osx/debug/lib: File exists
make: *** [altbininstall] Error 71
make: *** Waiting for unfinished jobs....

I saw this error before, is that related to your changes?

@JackBoosY That's the error we saw in https://github.com/microsoft/vcpkg/pull/19540#issuecomment-927554949

I saw this error before, is that related to your changes?

No. I also get this error local all the time when I want to build python3.

Already tested all features successfully on x86-windows and x64-windows-static.

Thanks for the bugfix!


Problem whit Unique Monster (MoM2nd)

Hi, i'm a new user. Yesterday i try to make a new custom scenario of Mansions of Madness second edition, but i didn't find the option to make a monster Unique. I red the guide but i suppose it is an older version. Is it a bug or did i miss it? thank you!

'Unique' Monsters are a Descent concept.  What you probably want is a 'Custom' Monster, that allows you to set custom activations, evades and horror checks.  Create a new CustomMonster Component, select the base monster type then replace the parts you want to change.  Then use a Spawn component to add one to the scenario.
Hope that helps.


Patch 1

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Hi @traversaro! I'd like to drop the use of gym-ignition-models in favor of icub-models in the tests to be consistent with the readme!

I included the change of this PR in https://github.com/conda-forge/adam-robotics-feedstock/pull/2, so I think we can close this one!


Release/57.0.0

Explanation
See changelogs for details.

Added approval controller to the release. Non-breaking change.


[minor] Fix minor issue in the configure.ts

Change Description:
Fix minor issue in the configure.ts.

need to check whether app.DisplayName is truthy because the registry key may return invalid data (like DISPLAYNAME)

logoutAzure is async function so it should be await. Besides, it's OK for hitting error, because if the first login attempt fails, the logout will hit exception.

Do these changes impact command syntax of any of the packages? (e.g., add/remove command, add/remove a command parameter, or update required parameters)
No.
Do these changes impact documentation? (e.g., a tutorial on https://learn.microsoft.com/office/dev/add-ins/overview/office-add-ins)
No.
Validation/testing performed:
The fix is tested in local machine with the yo office command.

/azurepipelines run

/azurepipelines run

/azurepipelines run


1D convs throughout --  no sharding on C dim

@mywoodstock / @tt-nshanker, is this issue still relevant?  I'm not 100% sure what it's covering

this was actually for post conv2.0 implementation, but probably no longer relevant now.


fix change int to bigint for json function

Proposed changes
Issue Number: close #17607
Problem summary
Describe your changes.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 33.6 seconds
stream load tsv:          463 seconds loaded<PHONE_NUMBER>9 Bytes, about 154 MB/s
stream load json:         37 seconds loaded<PHONE_NUMBER> Bytes, about 60 MB/s
stream load orc:          74 seconds loaded<PHONE_NUMBER> Bytes, about 14 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230314073351_clickbench_pr_113945.html

run buildall

run buildall

run COMPILE

run COMPILE

run COMPILE

run COMPILE

run DORIS_COMPILE

run COMPILE

run COMPILE

run buildall

run p0

run p0

run p0

run p0

run p0

run p1

run p1

run p1

run buildall

run p0

run p0

run p0

run buildall

run p0

run p0

run buildall

run buildall

@nextdreamblue can you add a get_json_bigint instead of change the behavior of get_json_int

BTW, binary json type JSONB is much faster than json text, have you try it?

run buildall

run buildall


INVALID_TYPE: sObject type 'ReleaseUpdate' is not supported.

I am trying to run a tooling API query that I have run before and can run in Salesforce Inspector or Postman. However, I am now getting an error from jsforce when running it.
Tooling API Query:
select DurableId, Title, ReleaseLabel, DueDate, Category, Description, HasNewSteps, IsReleased from ReleaseUpdate ORDER BY DueDate

INVALID_TYPE: sObject type 'ReleaseUpdate' is not supported.
at HttpApi.getError (/Users/Tim.Paulaskas/git-repos/Monitor/node_modules/jsforce/lib/http-api.js:250:13)
at /Users/Tim.Paulaskas/git-repos/Monitor/node_modules/jsforce/lib/http-api.js:95:22
at tryCallOne (/Users/Tim.Paulaskas/git-repos/Monitor/node_modules/promise/lib/core.js:37:12)
at /Users/Tim.Paulaskas/git-repos/Monitor/node_modules/promise/lib/core.js:123:15
at flush (/Users/Tim.Paulaskas/git-repos/Monitor/node_modules/asap/raw.js:50:29)
at processTicksAndRejections (node:internal/process/task_queues:78:11) {
errorCode: 'INVALID_TYPE'
}`

This is the result I get from Postman:
{{_endpoint}}/services/data/v{{version}}/tooling/query/?q=select DurableId, Title, ReleaseLabel, DueDate, Category, Description, HasNewSteps, IsReleased from ReleaseUpdate ORDER BY DueDate
{
    "size": 53,
    "totalSize": 53,
    "done": true,
    "queryLocator": null,
    "entityTypeName": "ReleaseUpdate",
    "records": [
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/AuraSecStaticResCRUC"
            },
            "DurableId": "AuraSecStaticResCRUC",
            "Title": "Enable Secure Static Resources for Lightning Components",
            "ReleaseLabel": null,
            "DueDate": null,
            "Category": "Security",
            "Description": "This release update has been postponed indefinitely while we change the implementation to reduce customer impact. The release update won’t be enforced in its present form. Don’t enable it.",
            "HasNewSteps": false,
            "IsReleased": false
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/GuestUserEmailIdUpdate"
            },
            "DurableId": "GuestUserEmailIdUpdate",
            "Title": "Update Guest User’s Email Address",
            "ReleaseLabel": null,
            "DueDate": null,
            "Category": "Security",
            "Description": "When you create an Experience Cloud or Salesforce site, Salesforce automatically creates a guest site user. In any site created before the Summer ’21 release, the email address for the site guest user record was that of the Salesforce user who created the site. After the Summer ’21 release, the system generates a dummy email address to use in the guest site user record.",
            "HasNewSteps": false,
            "IsReleased": false
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/SDCAdoptionReleaseUpdate"
            },
            "DurableId": "SDCAdoptionReleaseUpdate",
            "Title": "Enable Content Delivery Network for Digital Experiences",
            "ReleaseLabel": null,
            "DueDate": null,
            "Category": "Usability",
            "Description": "Use CDN for Digital Experiences to ensure high performance of your site during peak traffic events. Allow Salesforce to manage your certificates for you.",
            "HasNewSteps": false,
            "IsReleased": false
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/ApexNoArgConstructorAccessCriticalUpdate"
            },
            "DurableId": "ApexNoArgConstructorAccessCriticalUpdate",
            "Title": "Restrict Reflective Access to Non-Global Constructors in Packages",
            "ReleaseLabel": "Summer '20 Patch 18.0",
            "DueDate": "2020-08-19",
            "Category": "Other",
            "Description": "When this update is enabled, regardless of API version, you can initiate only Apex classes that have a no-arguments constructor that is visible to the code running Type.newInstance.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/MigrateLegacyTransactionSecurityCRUC"
            },
            "DurableId": "MigrateLegacyTransactionSecurityCRUC",
            "Title": "Migrate Legacy Policies to the Enhanced Transaction Security Framework",
            "ReleaseLabel": "Winter '21",
            "DueDate": "2020-09-10",
            "Category": "EndOfLife",
            "Description": "We're retiring the legacy transaction security framework in the Winter '20 release.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/AuraApexCtrlAuthUserAccessCheckCRUC"
            },
            "DurableId": "AuraApexCtrlAuthUserAccessCheckCRUC",
            "Title": "Restrict Access to @AuraEnabled Apex Methods for Authenticated Users Based on User Profile",
            "ReleaseLabel": "Winter '21",
            "DueDate": "2020-09-10",
            "Category": "Security",
            "Description": "This update gives you more control over which authenticated users can access Apex classes containing @AuraEnabled methods. When this update is activated, an authenticated user can access an @AuraEnabled Apex method only when the user’s profile allows access to the Apex class.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/AuraApexCtrlGuestUserAccessCheckCRUC"
            },
            "DurableId": "AuraApexCtrlGuestUserAccessCheckCRUC",
            "Title": "Restrict Access to @AuraEnabled Apex Methods for Guest and Portal Users Based on User Profile",
            "ReleaseLabel": "Winter '21",
            "DueDate": "2020-09-10",
            "Category": "Security",
            "Description": "This update gives you more control over which guest, portal, or community users can access Apex classes containing @AuraEnabled methods. Add guest user profile access to any @AuraEnabled Apex class used by a community or portal.
When this update is activated, a guest, portal, or community user can access an @AuraEnabled Apex method only when the user’s profile allows access to the Apex class.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/AllowStdExtProfileLoginCRUC"
            },
            "DurableId": "AllowStdExtProfileLoginCRUC",
            "Title": "Allow Users to Use Standard External Profiles to Self-Register and Log In To Experience Cloud Sites",
            "ReleaseLabel": "Spring '21 Patch 18.0",
            "DueDate": "2021-01-06",
            "Category": "Other",
            "Description": "This update allows users to self-register with standard external profiles, and allows users assigned to those profiles to log in to Experience Cloud sites.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/InvocableActionPartialSaveCRUC"
            },
            "DurableId": "InvocableActionPartialSaveCRUC",
            "Title": "Enable Partial Save for Invocable Actions",
            "ReleaseLabel": "Spring '21",
            "DueDate": "2021-01-10",
            "Category": "Usability",
            "Description": "This update prevents a failed invocable action from causing the entire transaction to fail and prevents the execution of other invocable actions in the failed transaction. With this update, Salesforce rolls back only the records whose updates get blocked by failed invocable actions.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/FlowPluginModifiersCRUC"
            },
            "DurableId": "FlowPluginModifiersCRUC",
            "Title": "Make Flows Respect Access Modifiers for Legacy Apex Actions",
            "ReleaseLabel": "Spring '21",
            "DueDate": "2021-01-10",
            "Category": "Security",
            "Description": "With this update enabled, flows fail if they contain a public legacy Apex action.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/CustomNotifActionAccessCheckReleaseUpdate"
            },
            "DurableId": "CustomNotifActionAccessCheckReleaseUpdate",
            "Title": "Require User Permission for the Send Custom Notification Action",
            "ReleaseLabel": "Spring '21",
            "DueDate": "2021-01-10",
            "Category": "Security",
            "Description": "This update gives you more control over which of your users can trigger the Send Custom Notification action in most flows, REST API, and Apex. When this update is activated, a user must have the Send Custom Notifications user permission to trigger the Send Custom Notification action in flows that run in user context, REST API calls, or Apex callouts.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/AuraSecureEvalCRUC"
            },
            "DurableId": "AuraSecureEvalCRUC",
            "Title": "Prevent Creation of Function Expressions When Using $A.createComponent() or $A.createComponents() in Aura Components.",
            "ReleaseLabel": "Spring '21",
            "DueDate": "2021-01-10",
            "Category": "Security",
            "Description": "To improve security and stability, this update prevents attribute values passed to $A.createComponent() or $A.createComponents() from being interpreted as Aura function expressions.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/EnforceDataAccessInFlowFormulas"
            },
            "DurableId": "EnforceDataAccessInFlowFormulas",
            "Title": "Enforce Data Access in Flow Merge Fields",
            "ReleaseLabel": "Summer '21",
            "DueDate": "2021-05-10",
            "Category": "Security",
            "Description": "This update enforces the running user’s data access when Flow Builder uses a merge field to access a field on a related record.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/MngdCtrlActionAccessCRUC"
            },
            "DurableId": "MngdCtrlActionAccessCRUC",
            "Title": "Disable Access to Non-global Controller Methods in Managed Packages",
            "ReleaseLabel": "Summer '21",
            "DueDate": "2021-05-10",
            "Category": "Security",
            "Description": "This update corrects access controls on Apex controller methods in managed packages. When this update is enabled, only methods marked with the global access modifier are accessible by Aura components from outside the package namespace.
These access controls prevent you from using unsupported API methods that the package author didn’t intend for global access.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/ExternalServicesRetireV1CRUC"
            },
            "DurableId": "ExternalServicesRetireV1CRUC",
            "Title": "Migrate Legacy External Services to the Current External Services Version",
            "ReleaseLabel": "Summer '21",
            "DueDate": "2021-05-10",
            "Category": "EndOfLife",
            "Description": "Legacy External Services begins its phased retirement in Spring '21. To prepare for this retirement and take advantage of the new features, migrate your Legacy External Services to the current External Services version as soon as possible.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/ApexPropertyGetterCRUC"
            },
            "DurableId": "ApexPropertyGetterCRUC",
            "Title": "Enforce Access Modifiers on Apex Properties in Lightning Component Markup",
            "ReleaseLabel": "Summer '21",
            "DueDate": "2021-05-10",
            "Category": "Security",
            "Description": "This update makes Lightning components consistent with the use of Apex properties in other contexts. For example, a markup expression can no longer access an Apex property with a private Apex getter.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/RemoveTM1GroupMemberCRUC"
            },
            "DurableId": "RemoveTM1GroupMemberCRUC",
            "Title": "Delete Your Original Territory Management Sharing Records",
            "ReleaseLabel": "Winter '22",
            "DueDate": "2021-09-10",
            "Category": "EndOfLife",
            "Description": "Now that the original territory management feature was retired, this update deletes your original territory management sharing records to prevent issues in Enterprise Territory Management.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/AuraComponentAccessFix"
            },
            "DurableId": "AuraComponentAccessFix",
            "Title": "Enable Aura Component Access Fix",
            "ReleaseLabel": "Winter '22",
            "DueDate": "2021-09-10",
            "Category": "Security",
            "Description": "This update fixes a bug in Aura‘s Component access controls.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/RecognitionBadgeGuestUserAccessReleaseUpdate"
            },
            "DurableId": "RecognitionBadgeGuestUserAccessReleaseUpdate",
            "Title": "Removal of Guest User Access to Recognition Badges in Experience Builder Sites",
            "ReleaseLabel": "Winter '22",
            "DueDate": "2021-09-10",
            "Category": "Security",
            "Description": "To improve security, we're disabling guest user access to recognition badges in Experience Builder sites by default.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/VisualforceJSRemotingEnforcement"
            },
            "DurableId": "VisualforceJSRemotingEnforcement",
            "Title": "Enable Visualforce JavaScript Remoting Enforcement",
            "ReleaseLabel": "Winter '22",
            "DueDate": "2021-09-10",
            "Category": "Security",
            "Description": "This update will throw an error if the Visualforce JavaScript $RemoteAction.ApexController.method function is invoked improperly.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/LightningOAuthScopeSecurityFix"
            },
            "DurableId": "LightningOAuthScopeSecurityFix",
            "Title": "Enforce OAuth Scope for Lightning Apps",
            "ReleaseLabel": "Winter '22",
            "DueDate": "2021-09-10",
            "Category": "Security",
            "Description": "To improve security, this update enforces the scope of an OAuth token used to authenticate a Lightning app. The scope of an OAuth token is defined in a connected app.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/PartnerBTEnforceMFAReleaseUpdate"
            },
            "DurableId": "PartnerBTEnforceMFAReleaseUpdate",
            "Title": "Require Multi-Factor Authentication For Logins to Subscriber Orgs",
            "ReleaseLabel": "Spring '22",
            "DueDate": "2021-12-05",
            "Category": "Security",
            "Description": "Secure access to subscriber orgs by requiring multi-factor authentication (MFA) when logging into the License Management Org (LMO).",
            "HasNewSteps": true,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/VisualforceELApexModifierEnforcement"
            },
            "DurableId": "VisualforceELApexModifierEnforcement",
            "Title": "Enable Visualforce Expression Language Apex Method Access Modifier Enforcement",
            "ReleaseLabel": "Spring '22",
            "DueDate": "2022-01-10",
            "Category": "Security",
            "Description": "This update throws an error if the Visualforce Expression Language can't access the Apex method due to access modifier visibility.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/ProductOWDReleaseUpdate"
            },
            "DurableId": "ProductOWDReleaseUpdate",
            "Title": "Set Organization-Wide Sharing Defaults for Products",
            "ReleaseLabel": "Spring '22",
            "DueDate": "2022-01-10",
            "Category": "Security",
            "Description": "To better protect your data, this update does the following:\n            \n
\n
In Winter ’22, adds organization-wide sharing settings for product records
\n
As of Spring ’22, in new orgs only, sets the organization-wide sharing default for products to Private for external users
\n
",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/DisableForcedLoginReleaseUpdate"
            },
            "DurableId": "DisableForcedLoginReleaseUpdate",
            "Title": "Disable Users from Logging Into an Org or Experience Cloud Site with Login Credentials as URL Query String Parameters",
            "ReleaseLabel": "Spring '22",
            "DueDate": "2022-01-10",
            "Category": "Security",
            "Description": "Salesforce is removing the ability for users to log into orgs or Experience Cloud sites with usernames and passwords as query string parameters to the login URL.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/AuraCorsAllowlistSecurityFix"
            },
            "DurableId": "AuraCorsAllowlistSecurityFix",
            "Title": "Enforce CORS Allowlist for Lightning Apps",
            "ReleaseLabel": "Spring '22",
            "DueDate": "2022-01-10",
            "Category": "Security",
            "Description": "
The Cross-Origin Resource Sharing (CORS) allowlist in Setup isn’t currently enforced for Lightning apps. This update enforces the allowlist. Cross-origin requests to Lightning apps are blocked unless the request comes from a URL listed in your org’s CORS allowlist.
\n
\n
CORS enables web browsers to request resources from origins other than their own. For example, using CORS, JavaScript code at https://www.example.com could request a resource from https://www.salesforce.com. To access Lightning Out from JavaScript code in a web browser, add the origin requesting the code to your CORS allowlist in Setup.
",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/ProductOWDGuestUserReleaseUpdate"
            },
            "DurableId": "ProductOWDGuestUserReleaseUpdate",
            "Title": "Retain Guest Users’ Access to Products",
            "ReleaseLabel": "Spring '22",
            "DueDate": "2022-01-10",
            "Category": "Security",
            "Description": "To better protect your Salesforce org, this update changes how unauthenticated guest access to product records (the Product2 object) is controlled. The product organization-wide sharing default for external users is no longer applied to guest users. The organization-wide default is set to Private for guest users and can’t be changed. To retain guest users’ access to products, create guest user sharing rules.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/FlowNullInFormulaCRUC"
            },
            "DurableId": "FlowNullInFormulaCRUC",
            "Title": "Check for Null Record Variables or Null Values of Lookup Relationship Fields in Process and Flow Formulas",
            "ReleaseLabel": "Spring '22",
            "DueDate": "2022-01-10",
            "Category": "Usability",
            "Description": "This update enables process and flow formulas to reference a record’s field when the field is accessed via a null lookup relationship field or null record variable.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/FlowApexCpuTimingReleaseUpdate"
            },
            "DurableId": "FlowApexCpuTimingReleaseUpdate",
            "Title": "Accurately Measure the CPU Time Consumption of Flows and Processes",
            "ReleaseLabel": "Summer '22",
            "DueDate": "2022-05-10",
            "Category": "Usability",
            "Description": "This update lets Salesforce accurately measure, log, and limit the CPU time consumed by flows and processes.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/RqrEmlChgVerfAdmDrvnECRPReleaseUpdate"
            },
            "DurableId": "RqrEmlChgVerfAdmDrvnECRPReleaseUpdate",
            "Title": "Securely Update Email Addresses and Reset Passwords",
            "ReleaseLabel": "Summer '22",
            "DueDate": "2022-05-10",
            "Category": "Security",
            "Description": "To ensure the security of your org, users must now reset their password before your changes to their email address and password become active. When a user resets the password using the provided link, the new email address is activated. Previously, the user’s email address became active as soon as you saved the change.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/SuppressMfaForOidcSsoReleaseUpdate"
            },
            "DurableId": "SuppressMfaForOidcSsoReleaseUpdate",
            "Title": "Bypass MFA Challenges for Single Sign-On Auth Provider Logins",
            "ReleaseLabel": "Summer '22",
            "DueDate": "2022-05-10",
            "Category": "Security",
            "Description": "This release update will enforce the documented behavior of bypassing MFA challenges for users who are assigned the user permission Multi-factor Authentication for User Interface Logins.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/ApiVersions7to20Retirement"
            },
            "DurableId": "ApiVersions7to20Retirement",
            "Title": "Salesforce Platform API Versions 7.0 through 20.0 Retirement",
            "ReleaseLabel": "Summer '22",
            "DueDate": "2022-05-10",
            "Category": "EndOfLife",
            "Description": "Versions 7.0 through 20.0 of the Salesforce Platform SOAP, REST, and Bulk APIs will be deprecated and no longer supported in the Summer '21 release. Applications should be modified to consume the latest available API version.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/LLoginFlowWarningReleaseUpdate"
            },
            "DurableId": "LLoginFlowWarningReleaseUpdate",
            "Title": "Summer ‘22 - You can now disable the rendering of new Login Flows in Lightning Runtime.",
            "ReleaseLabel": "Spring '22",
            "DueDate": "2022-05-20",
            "Category": "Security",
            "Description": "As of the Summer ‘22 release, customers can improve security by disabling the rendering of new Login Flows in Lightning Runtime.",
            "HasNewSteps": false,
            "IsReleased": true
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/VisualforceELApexModifierGetSetEnforcement"
            },
            "DurableId": "VisualforceELApexModifierGetSetEnforcement",
            "Title": "Validate Getter and Setter Access Modifier Enforcement During Visualforce Expression Language Parsing",
            "ReleaseLabel": "Winter '23",
            "DueDate": "2022-09-10",
            "Category": "Security",
            "Description": "This update throws an error if the Visualforce Expression Language can’t validate the access modifier for the Apex get or set method.",
            "HasNewSteps": false,
            "IsReleased": false
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/VisualforceJSRemotingEnforcementWithPerm"
            },
            "DurableId": "VisualforceJSRemotingEnforcementWithPerm",
            "Title": "Enable Visualforce JavaScript Remoting Enforcement",
            "ReleaseLabel": "Winter '23",
            "DueDate": "2022-09-10",
            "Category": "Security",
            "Description": "This update will throw an error if the Visualforce JavaScript $RemoteAction.ApexController.method function is invoked improperly.",
            "HasNewSteps": false,
            "IsReleased": false
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/EnableEnhancedDomainsReleaseUpdate"
            },
            "DurableId": "EnableEnhancedDomainsReleaseUpdate",
            "Title": "Enable Enhanced Domains",
            "ReleaseLabel": "Winter '23",
            "DueDate": "2022-09-10",
            "Category": "Security",
            "Description": "To comply with the latest browser and security standards, enable enhanced domains on your Salesforce org’s My Domain. This update affects application and login URL formats across your org and is enforced in phases beginning in Winter ’23. This update is enforced in sandboxes and non-production orgs in Winter ’23 unless you enable the postponement setting on the My Domain Setup page. This update is enforced in production orgs and all remaining orgs in Spring ’23.",
            "HasNewSteps": false,
            "IsReleased": false
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/EnablePSAExpirationUI"
            },
            "DurableId": "EnablePSAExpirationUI",
            "Title": "Enable Permission Set Expiration and Enhanced UI",
            "ReleaseLabel": "Winter '23",
            "DueDate": "2022-09-10",
            "Category": "Security",
            "Description": "With this update enabled, permission set and permission set group assignments use a new Lightning interface and an improved workflow. Also, you have the option to assign an expiration date to each permission set and permission set groups",
            "HasNewSteps": false,
            "IsReleased": false
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/GuestUserPSLUpdate"
            },
            "DurableId": "GuestUserPSLUpdate",
            "Title": "Remove Guest User Assignments from Permission Sets Associated with Permission Set Licenses with Restricted Object Permissions",
            "ReleaseLabel": "Winter '23",
            "DueDate": "2022-09-10",
            "Category": "Security",
            "Description": "
To improve the security of your data, Salesforce is removing guest user assignments from permission sets and permission set groups associated with permission set licenses that contain View All, Modify All, edit, and delete object permissions. After the permission set or permission set group assignment is removed, guest user assignments of permission set licenses with these restricted permissions have no effect. The only object permissions allowed for guest users are read and create. Going forward, you can no longer assign guest users permission sets or permission set groups that are associated with these permission set licenses and contain the restricted permissions.
\n
\n
Note: This update was originally called \"Remove Permission Set Licenses with View All, Modify All, Edit, and Delete Object Permissions from Guest Users.\"
",
            "HasNewSteps": false,
            "IsReleased": false
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/EnhancedPersonalInformationManagementReleaseUpdate"
            },
            "DurableId": "EnhancedPersonalInformationManagementReleaseUpdate",
            "Title": "Enable Stronger Protection for Your Users’ Personal Information",
            "ReleaseLabel": "Winter '23",
            "DueDate": "2022-09-10",
            "Category": "Security",
            "Description": "To prevent external users, such as portal or guest users, from viewing other users’ personal information, enable Enhanced Personal Information Management. This feature replaces the Hide Personal Information setting and allows you to specify which fields are considered PII.",
            "HasNewSteps": false,
            "IsReleased": false
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/ExperienceDisableRunFlowsReleaseUpdate"
            },
            "DurableId": "ExperienceDisableRunFlowsReleaseUpdate",
            "Title": "Require Granular Flow Permissions for Experience Cloud Guest Users",
            "ReleaseLabel": "Spring '23",
            "DueDate": "2023-01-10",
            "Category": "Security",
            "Description": "This update removes the Run Flows permission from the guest user profiles associated with Experience Cloud sites. The change improves site security by requiring explicit guest user permissions to run flows.",
            "HasNewSteps": false,
            "IsReleased": false
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/NewOrderSaveLogicCRUC"
            },
            "DurableId": "NewOrderSaveLogicCRUC",
            "Title": "Enable New Order Save Behavior",
            "ReleaseLabel": "Spring '23",
            "DueDate": "2023-01-10",
            "Category": "Other",
            "Description": "After the New Order Save Behavior is enabled, whenever an order product update causes a change to the parent order, Salesforce runs custom application logic. Previously, in this scenario, Salesforce didn’t correctly evaluate custom application logic on the parent record. Users will have the option to enable the new behavior in Winter '21. Salesforce will automatically enforce the updated behavior in Spring '23.\n

Warning: Packages with orders created before Winter '21 don't support the New Order Save Behavior release update by default. If you use a package involving orders, wait for confirmation from your package provider before enabling the release update.",
            "HasNewSteps": false,
            "IsReleased": false
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/IsTimeResumedInSameRunContext"
            },
            "DurableId": "IsTimeResumedInSameRunContext",
            "Title": "Make Paused Flow Interviews Resume in the Same Context with the Same User Access",
            "ReleaseLabel": "Spring '23",
            "DueDate": "2023-01-10",
            "Category": "Security",
            "Description": "With this update enabled, paused autolaunched flows always resume in the same context and with the same user access they had before they were paused.",
            "HasNewSteps": false,
            "IsReleased": false
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/UseOpenSAMLV4ForOutboundReleaseUpdate"
            },
            "DurableId": "UseOpenSAMLV4ForOutboundReleaseUpdate",
            "Title": "Upgrade SAML Single Sign-On Framework",
            "ReleaseLabel": "Spring '23",
            "DueDate": "2023-01-10",
            "Category": "Security",
            "Description": "Salesforce is upgrading its SAML framework as part of regular ongoing maintenance. This update can impact integrations with third-party systems. For example, this update can impact integrations with SAML identity providers or SAML-enabled applications. This update applies to every SAML-based integration, whether you’re using Identity for Employees or Salesforce Customer Identity, including Experience Cloud.",
            "HasNewSteps": false,
            "IsReleased": false
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/FlowViaRestUsesUserCtxtCRUC"
            },
            "DurableId": "FlowViaRestUsesUserCtxtCRUC",
            "Title": "Run Flows in User Context via REST API.",
            "ReleaseLabel": "Spring '23",
            "DueDate": "2023-01-10",
            "Category": "Security",
            "Description": "With this update enabled, a flow that runs via REST API uses the running user’s profile and permission sets to determine the object permissions and field-level access of the flow.",
            "HasNewSteps": false,
            "IsReleased": false
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/LocaleFormatCRUC"
            },
            "DurableId": "LocaleFormatCRUC",
            "Title": "Enable ICU Locale Formats",
            "ReleaseLabel": "Spring '23",
            "DueDate": "2023-01-10",
            "Category": "Usability",
            "Description": "Changes the way that dates, times, numbers, and currencies appear, using locale formats from the International Components for Unicode (ICU) library.",
            "HasNewSteps": false,
            "IsReleased": false
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/OWAForCaseEmailsAllowedReleaseUpdate"
            },
            "DurableId": "OWAForCaseEmailsAllowedReleaseUpdate",
            "Title": "Use a Default No-Reply Address as System Address for Case Email Notifications",
            "ReleaseLabel": "Spring '23",
            "DueDate": "2023-01-10",
            "Category": "Security",
            "Description": "
From Setup, configure a default No-Reply address from the Organization-Wide Addresses page. Add an email address in Special Purpose Organization-Wide Email Addresses, then follow the steps outlined in the verification email sent to the new default No-Reply address.
\n
\n
After you verify your default No-Reply address, set up and start the Test Run in the Release Update.
",
            "HasNewSteps": false,
            "IsReleased": false
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/EmailThreadingCRUC"
            },
            "DurableId": "EmailThreadingCRUC",
            "Title": "Disable Ref ID and Transition to New Email Threading Behavior",
            "ReleaseLabel": "Summer '23",
            "DueDate": "2023-05-10",
            "Category": "Security",
            "Description": "Disable Ref ID and Use New Email-to-Case Threading.",
            "HasNewSteps": false,
            "IsReleased": false
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/ApiVersions21to30Retirement"
            },
            "DurableId": "ApiVersions21to30Retirement",
            "Title": "Salesforce Platform API Versions 21.0 through 30.0 Retirement",
            "ReleaseLabel": "Summer '23",
            "DueDate": "2023-05-10",
            "Category": "EndOfLife",
            "Description": "Versions 21.0 through 30.0 of the Salesforce Platform SOAP, REST, and Bulk APIs will be deprecated and no longer supported in the Summer '22 release. Applications should be modified to consume the latest available API version.",
            "HasNewSteps": false,
            "IsReleased": false
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/FlowCommunityApexContextRetiredCRUC"
            },
            "DurableId": "FlowCommunityApexContextRetiredCRUC",
            "Title": "Disable Rules for Enforcing Explicit Access to Apex Classes",
            "ReleaseLabel": "Summer '23",
            "DueDate": "2023-05-10",
            "Category": "Security",
            "Description": "With this update, the running user of a flow or process no longer requires explicit access to Apex classes that are invoked by the flow or process.",
            "HasNewSteps": false,
            "IsReleased": false
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/FlowNullPreviousValueFix"
            },
            "DurableId": "FlowNullPreviousValueFix",
            "Title": "Evaluate Criteria Based on Original Record Values in Process Builder",
            "ReleaseLabel": "Summer '23",
            "DueDate": "2023-05-10",
            "Category": "Usability",
            "Description": "This update fixes a bug with the evaluation criteria in processes that have multiple criteria and a record update.",
            "HasNewSteps": false,
            "IsReleased": false
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/ScopedModalsCRUC"
            },
            "DurableId": "ScopedModalsCRUC",
            "Title": "Keep Working with Tab-Focused Dialogs",
            "ReleaseLabel": "Summer '24",
            "DueDate": "2024-05-10",
            "Category": "Usability",
            "Description": "In Lightning console apps, dialogs no longer stop you from interacting with the rest of the UI. This release update limits the focus of dialogs triggered by a workspace tab or subtab to only the tab that triggered it.",
            "HasNewSteps": false,
            "IsReleased": false
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/DoubleNavApi"
            },
            "DurableId": "DoubleNavApi",
            "Title": "Prevent consecutive API navigation calls",
            "ReleaseLabel": "Summer '24",
            "DueDate": "2024-05-10",
            "Category": "Usability",
            "Description": "In Visualforce pages and Lightning components, API navigation calls can be fired consecutively. This release update prevents this API navigation call pattern, firing only the first navigation call.",
            "HasNewSteps": false,
            "IsReleased": false
        },
        {
            "attributes": {
                "type": "ReleaseUpdate",
                "url": "/services/data/v54.0/tooling/sobjects/ReleaseUpdate/FlowCommunityApexContextCRUC"
            },
            "DurableId": "FlowCommunityApexContextCRUC",
            "Title": "Require User Access to Apex Classes Invoked by Flow",
            "ReleaseLabel": "Winter '25",
            "DueDate": "2024-09-10",
            "Category": "Other",
            "Description": "This update requires a user running a flow to have access to all Apex classes invoked by that flow. If the user does not have an Apex class assignment via their profile or permission set, the flow fails when it invokes the Apex class",
            "HasNewSteps": false,
            "IsReleased": false
        }
    ]
}

when querying tooling objects you need to run the query via conn.tooling.query(<query>), not conn.query.
https://jsforce.github.io/document/#query-tooling-objects


[WIP] Feature/ionic4

I have taken https://github.com/ngx-rocket/generator-ngx-rocket/pull/335, fixed comments regarding typescript and ported to work with latest changes that master has regarding #231
Started porting to Ionic v4

Thanks for your contribution!
Though it seems there's some issues with your changes:
ERROR in src/app/app.component.ts(7,26): error TS2307: Cannot find module '@ionic-native/keyboard/ngx'.
src/app/app.component.ts(8,27): error TS2307: Cannot find module '@ionic-native/status-bar/ngx'.
src/app/app.component.ts(9,30): error TS2307: Cannot find module '@ionic-native/splash-screen/ngx'.

Also, we have a some PR to merge before this one can be merged, and the latest angular/cli release has some nasty bugs that broke the CI, so we're stuck until it's fixed for now.

Hi @iocaste
I hadn't noticed you already had a PR that's quite far along yesterday, so I started porting a stock generated ngx-rocket project so I can have an overview of the differences.  You can see the diff here: https://github.com/captaincaius/ngxrocket501toionic4beta/pull/1/files
I see your PR is pretty far along (I didn't touch the generator itself yet), but I wanted to offer some help if it's possible.
If you think it's not really practical and you wanna finish it, then let me know if it would be helpful to you for me to continue refining the port so you can use it as a checklist of sorts for your PR.  For example, from looking at the differences, the errors @sinedied mentioned above seem to be from the package updates.
Thanks!
Al

Oh also, as a slightly-related vision question for @sinedied ...
Do you intend to abandon ionic 3 entirely and just get ionic 4 working?  Or do you want to see it as a separate option?

@captaincaius Would be great if you could finish porting ionic-4. I saw that there is another PR that adds ionic tabs, looks like work for porting ionic 4 should be started from beginning.

@sinedied Can you accept this PR https://github.com/ngx-rocket/generator-ngx-rocket/pull/361 ?
Looks like only thing that you wanted, was commit squash, it can be done from your side. This PR is needed so that we could have ionic-4 version with tabs and sidebar.

Great!  I'll be happy to help.
But guys, I'm a little unclear what direction this is going with the multi-layout PR in mind...
It seems that in 5.0.1 there was the following options:

ionic (no layout options)
material

simple layout
side-menu layout

... others...

After the PR you linked, it will be:

ionic

side-menu layout (the same as 5.0.1)
tabs layout (new)

material

simple layout
side-menu layout

... others...

So for the port,

will ionic 4 be maintained alongside ionic 3, or will it replace it?  If it'll replace it, I think it would be easier to port THEN add tabs.
will both layouts need to be ported over?  If so, I should run the generator from that branch instead of master before starting the work?

Thanks!

@iocaste The PR for the tabs will be merged as soon as the CI is done, I was waiting for other commit to be merged before (cordova fix and circleCI builds)
@captaincaius I don't think it makes sense to keep a Ionic 3 path as it won't be maintained now that the v4 is out. As it has some hard Angular version dependencies anyways, if anyone want to generate a ionic 3 project an old ngx rocket version can still be used.
So this PR should completely replace the Ionic 3 code by Ionic 4, and move on from there 😃

That sounds like a smart plan to me.  Maintaining ionic 3 as well would have been messy :D.
Okay, so with that in mind, which one of these options would you like me to do?

branch off master and only port the one layout - the tabs PR will need to be redone for ionic4 in that case
branch off the tabs PR now and port both layouts, and then once the squashed tabs it's merged, reroll a PR for the new master
wait for the tabs PR to merge, then start the port for both layouts

I've merged the tabs branch, so now you can go for option 3) 😉

thanks :) on it today

quick update...
I ported most of the generated tabs over.
I made this PR to give you a chance to see the diffs more clearly than the PR I'm about to make for the generator itself.
https://github.com/captaincaius/ngx-rocket-20180825toionic4-tabs/pull/1/files

and FYI, it's functional and the tests pass, but I didn't fully update the styling, because it looks like it's still very much in flux over at ionic.

I'm closing this PR as captaincaius took this task.


Creating a client session outside of coroutine

Currently when the bot starts, it errors with:
ERROR:asyncio:Creating a client session outside of coroutine
client_session: <aiohttp.client.ClientSession object at 0x108db35c0>

However, it continues to work.
Here's a snippet of log around it:
- Loading bot code
 - Ready to start bot!
INFO:bot:Init: Getting cog folder
ERROR:asyncio:Creating a client session outside of coroutine
client_session: <aiohttp.client.ClientSession object at 0x108db35c0>
INFO:bot:Init: Loading cogs
INFO:bot:Init: Loading cog: cogs
INFO:bot:Init: Loading cog: admin
INFO:bot:Init: Loading cog: cosmetic

What could be the cause? I've confirmed it's not util.cleverbot or util.google.

It was discord.py.


get_recent_signage_point_or_eos endpoint clarification

Please provide more information about "get_recent_signage_point_or_eos" endpoint references. https://github.com/Chia-Network/pool-reference/blob/main/pool/pool.py#L471
Thanks.

Check this API documentation.
https://github.com/Chia-Mine/chia-agent/blob/v1.1.0/src/api/rpc/full_node/README.md#get_recent_signage_point_or_eosagent-params

Checks whether a signage point is real and is recent in the blockchain (and has not been reverted). This is used to check if farmers are responding within 28 seconds.


Tabs or spaces? (python 3 related)

Hi.  Python 3 is more picky than python 2 when it comes to indenting with space or tabs.  And the code currently only work with python 2, partly because it mixes tabs and spaces.  Do you have any opinion if tabs or spaces should be used?  Personally I prefer spaces, for various reasons, but my preference is not very strong.
Can we pick tabs or spaces, document the preference and convert the code to use it?  Switching to python 3 would make several charset encoding issues easier to solve, and I believe it is a good long term goal.

Please use tabs !
Tabs are better.
With tabs :

you have less characters
in your editor, you can chose the size of the indentation (ie: tabs = 2 spaces or 4 spaces or...)

[Oros42]

Please use tabs !

OK.  Can you tabify the source to ensure consistency, and increase the
chance of running it in python 3?

With tabs :

you have less characters

True.  I would be surprised if it have any effect on any measurable
metrix, though. :)

in your editor, you can chose the size of the indentation (ie: tabs
= 2 spaces or 4 spaces or...)

Not really true, if you like me sometimes want things to align
horizontally involving something that is not a tab, like this example
with the function arguments:
def myfunc(a,
b,
c,
d)
Anyway, I do not see it as my misssion to convince you that space are
better than tabs, so tabs it is. :)
--
Happy hacking
Petter Reinholdtsen


Installation instruction - Update

After followed the installation instructions, I got error "Vite not found".
I think you forgot a step before running the server:
npm install && npm run build

npm install && npm run build

For certain conditions, I am not aware, but I followed the installation process according to the instructions and didn't encounter any issues, as the TALL stack uses filamentphp, so there's no need to run the command npm install && npm run build anymore.


accessibility keyboard support for chart legends

What problem does this feature solve?
For accessibility the chart legend labels should be keyboard accessible with a tabindex and should be clickable with the enter key.  Also, the legend prev/next arrow buttons should have the same keyboard controls.
What does the proposed API look like?
adding tabindex to legend labels and buttons
adding keydown.enter events to legend labels and buttons

Hi!
I know that this is very specific to chart's legend, but since it is a new feature (based on the tag added by @plainheart) can I suggest to take a look at how Highcharts implemented the keyboard navigation for the whole chart? Maybe this issue might be more generic...
https://www.highcharts.com/accessibility/#exploreFeatures
In my company we are evaluating to change the chart library we are using, and se were really impressed by Echarts and all the possibilities it offers, also the documentation and samples are very clear an easy to understand, but one of the most important thing for us is the accessibility and it will be really important to understand which are the plans of Echarts to take the right decision 😃 🙇🏻

We also need at least keyboard accessibility at least for legends, but ideally for the whole chart.

Demo Code as proof-of-concept - integration of ECharts and chart2music.
Legend keyboard accessibility - try key 's' for scatter and 'b' for bar chart.
There is also individual data points highlighting with music(!) and more, press H to see hotkey Help.


"ATTACH" and connection pooling

I am having issues using the "ATTACH database" command.  Because of connection pooling, I find that sometimes my query executes on a different connection than the one I attached the database on.  I can't use a Tx to bind to a specific connection because I can't execute ATTACH within a transaction.  Is there another way to do ATTACH and ensure that the subsequent transaction is performed on the same connection?
Thanks.

I implemented a Connect Hook to do the attach command on every connection and then just never detach.  Let me know if there's a better way.


MIAD-236: Enable remaining South East and East prisons

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.83%. Comparing base (95cf632) to head (d274428).

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #219   +/-   ##
=========================================
  Coverage     90.83%   90.83%
  Complexity      505      505
=========================================
  Files            86       86
  Lines          1735     1735
  Branches        106      106
=========================================
  Hits           1576     1576
  Misses          120      120
  Partials         39       39

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


ChannelStreamInput  is not used

ChannelStreamInput is not used anywhere.
(Founded by @vanzin)

Fixed in 4d41bf596d97aeca958df218e7927ae69d630043.


JIT to a WebAssembly target

Feature request
Imagine writing an image transformation in python code and jitting it to output to WebAssembly for use in a browser.  This will allow python viz tools to push computations to the browser to reduce latency.
State of the tech:

LLVM has webassembly backend.  Since numba emits LLVM IR, emitting webassembly is not hard.
Numba (re)implements a lot of the NumPy API internally.  Any used NumPy functions will be encoded in webassembly.  Thus, allowing us to inject (almost) seamless NumPy support into the browser.

But if this works, it's pretty awesome.

it would amazing if this worked. What if this could be paired with bokeh to be able to write custom callbacks in (jit-decorated) python rather than JS?

Agree with this completely. I just wrote a binary parser in C and compiled to wasm because JS doesn't have a fast way to parse non-standard (12 bit) uints! This would be incredible to be able to write python code and have it accessible via browser (huge speedup in fast scientific computing in production scale apps)

Agree with this completely. I just wrote a binary parser in C and compiled to wasm because JS doesn't have a fast way to parse non-standard (12 bit) uints! This would be incredible to be able to write python code and have it accessible via browser (huge speedup in fast scientific computing in production scale apps)

Ha! This issue is still alive, years later.. :-)

It seems hacky but it already worked in 2015:
https://cyrille.rossant.net/numpy-browser-llvm/
What is the best way to get optimized LLVM IR from numba today ?
from numba.core.compiler import compile_isolated
with open('test.ll','w') as fp:
    cfunc = compile_isolated(foo, sig)
    ir=cfunc.library.get_llvm_str()
    fp.write(ir)

Then we could directly use emscripten compiler ?
emcc -s WASM=1 test.ll
Commenting with ';' the too first lines of test.ll allows to generate a.out.js and a.out.wasm

Hello @sfornengo ,
thank you for the article. I toyed around with it and could make parts of it working. The problem I face is that inspect_llvm() outputs also the wrapping code for python.
@jit(int32(int32, int32), nopython=True)
def f(x, y):
    return x + y

If I run the add function (see above) from the article with NUMBA_DUMP_LLVM=1 I get a cleaner version of the IR compared to inspect_llvm(). The output can be converted to wasm with (note you need at least llvm version 10):
llc -march=wasm32 -filetype=obj test.ll
wasm-ld --export-all --no-entry -o test.wasm test.o

I am able to run the wasm with wasmer in the backend, but should run in the browser as well.
Unfortunately, this approach does not work for me when using a function which actually uses numpy:
@jit(int32(int32[:]), nopython=True)
def np_sum(x):
    return x.sum()

It leads to invalid redefinition of function errors in the llc step.
If anybody knows the way to get the proper LLVM IR without the python wrapping code I would be grateful.

This will produce the LLVM IR without the wrapper code:
from numba import njit, int32
import numpy as np

@njit(int32(int32, int32), no_cfunc_wrapper=True, no_cpython_wrapper=True)
def f(x, y):
    return x + y

print(f.inspect_llvm(f.signatures[0]))

Is anyone trying this with Pyodide's Numpy yet?

@seibert Do you have specific ideas about AOT written somewhere to look at and discuss? We have some ideas also, and would be happy to help with the implementation in general.

I don't think there are concrete ideas written down for improvements.  The best starting place is to look at the current pycc documentation and figure out which limitations could be lifted, and how:
https://numba.pydata.org/numba-doc/dev/user/pycc.html
On that page, the 4 listed limitations are a good starting point to inspire possible improvements:

Only functions, not ufuncs: This is a special case of not having a sufficient abstractions for deserializing Numba functions that need to be wrapped in Python objects in special ways, or might contain embedded addresses to external symbols that need to be relinked at runtime.
You have to specific function signatures explicitly: This is a necessity of ahead-of-time compilation, of course, but we know that writing function type signatures is error-prone.  This could perhaps be improved by allowing a "define by call" form where the AOT compilation process is driven by capturing all the call signatures generated by running the code with some test data.
Each exported function can only have one signature: This is connected to the problem of the Dispatcher object not being saved with the generated functions or recreated when they are loaded again.  Solving this is probably related to limitation 1.
AOT produces generic code, not code tailored to your CPU:  This has connections to the dispatching problem (how would you pick between several specialized implementations at call time?).

Also, it is probably good to start with trying to agree on the goals of AOT compilation before improving it.  Is AOT for:

Producing completely standalone functions that can exist without most of Numba's runtime infrastructure? (that's how it is written now)
Avoiding slow compilation tasks at runtime, and/or redundant compilation across a cluster of systems?
Reducing warmup time by precompiling and packaging the implementations of functions for common type signatures, but allowing for JIT compilation of other type signatures.

In fact, there's a lot of overlap in concerns between AOT and the function cache.  Perhaps a more unified view of the two would solve problems with both at the same time.

Thank you @seibert! This is a good comprehensive overview of current AOT status and directions I think. From the use cases I have seen, it would be great if an overload could be pre-compiled for a set of common data types during package build time (and compiled versions shipped with the package) but jitted for other types during runtime. This use case essentially covers a couple of your points, and would reduce compilation time in practice substantially.

The first step to being able to run Numba inside the browser is getting llvmlite to run inside the browser, which is being tracked over here: https://github.com/numba/llvmlite/issues/836

While it isn't running numba itself in the browser, I have been exploring the mentioned idea of compiling numba functions AOT to WASM for use in JS (and pyodide!).
The implementation idea is very similar to the aforementioned 2015 article, though with some additional coating to make it more reasonably useable with pyodide. It's definitely not perfect, and not the ideal solution (which would likely be JIT compiling within the browser), but I find it pretty interesting and relevant to this discussion based on previous comments.
PYCC is used (though can likely be avoided as its pending deprecation) to generate wasm32-compatible LLVM IR (with a custom wrapper around array-returning/array-argument functions for ease of use from JS), which is then compiled to WASM via emscripten alongside numba's NRT library which is needed for numpy array creation. I believe there are additional parts of numba that need to be compiled to WASM for additional functionality, but that seems trivial enough and this is all that is needed for my minimal example. These wasm modules are then loaded into JS to allow access to their functions. A pure-python basic utility module that creates wrappers to easily call these functions from within pyodide's interpreter is loaded into pyodide and allows cleaner calling of these functions as if they were regular python functions.
I am absolutely no expert with LLVM nor numba's internals, so I believe this idea could definitely be expanded upon by someone more apt than I.
The repo containing this implementation can be found at https://github.com/Lincoln-LM/numba-wasm-example, and the minimal (console) example itself can be found at https://lincoln-lm.github.io/numba-wasm-example.


Dnadales/cad 4096 add sm tests for mempool

Description

description of the pull request, if it fixes a particular issue it should link
the PR to a particular issue, see
ref
Checklist

Branch

[ ] Commit sequence broadly makes sense
[ ] Commits have useful messages
[ ] New tests are added if needed and existing tests are updated
[ ] If this branch changes Consensus and has any consequences for downstream repositories or end users, said changes must be documented in interface-CHANGELOG.md
[ ] If this branch changes Network and has any consequences for downstream repositories or end users, said changes must be documented in interface-CHANGELOG.md
[ ] If serialization changes, user-facing consequences (e.g. replay from genesis) are confirmed to be intentional.

Pull Request

[ ] Self-reviewed the diff
[ ] Useful pull request description at least containing the following information:

What does this PR change?
Why these changes were needed?
How does this affect downstream repositories and/or end-users?
Which ticket does this PR close (if any)? If it does, is it linked?

[ ] Reviewer requested

Closing this as its only goal was to help me auditing the new mempool QSM tests for UTxO HD.


Revert "Add an idempotenceKey to the JobQueue interface (#1252)"

This reverts commit 44e18ba2a63d8b469b3c7da265909c46060d5b50.

nobody should be relying on these new interfaces, so it should be safe to revert


Customer view - SQL version

Describe your changes
As we decided to follow the SQL tables as pattern, the CustomerView was re-written with this method. The code is already uner the "flinkfood-demo".
@Niccolo-Francioni has done some experimentation under "flinkfood-demo-v2", I don't know if we should keep it or not.
A major detail: I can't test it properly in this new format. I don't know why, but when I did the merge with develop, the docker engine does not work properly. I am just unable to test it as it is right now. Rest assured that the code works and runs normally under its own folder, I just don't know how to solve my problems and orchestrate the whole demo execution, I am still having issues.
Checklist before requesting a review

[x] I have performed a self-review of my code
[ ] I have updated/created the corresponding documentation

As you know, for some reason the current architecture of the Demo does not work properly in my computer. The "jobmanager" fails right after startup

But reverting the docker-compose file description to an older version makes everything work to me. Again, I tested the code and it works! It should work as well in your computers
From

To

Makes it work

As you know, for some reason the current architecture of the Demo does not work properly in my computer. The "jobmanager" fails right after startup
But reverting the docker-compose file description to an older version makes everything work to me. Again, I tested the code and it works! It should work as well in your computers
From
To
Makes it work

@Niccolo-Francioni

I am wondering why there is +3000 and -2000 lines in this PR? Like when I look at the files it looks like nothing has changed (see for instance bug_reportd.md)


Allow setting full Ajv Instance on JSON options

In response to #236 I have created a quick pr that will allow setting a full ajv instance for the options.
closes #236

Thank you so much for fixing this @pgior001!
Can we merge this @tulios? This is causing so many issues in my project!!!

Thank you for the patience I am going to merge it now! 🙏


SAM/BAM alignment support

More general SAM/BAM format for alignment input

I was running into a difference in reference alignment positions between standard PAF alignment output and the SAM output from minimap2. This appears due to not performing base-level alignment in the standard PAF output. Equivalence is:
minimap2 -a ref.fa reads.fq
minimap2 -c ref.fa reads.fq

but these are different
minimap2 -a ref.fa reads.fq
minimap2 ref.fa reads.fq

see also: https://github.com/lh3/minimap2/issues/158


AudioStreamRandomizer.random_volume_offset_db not working

Godot version
Godot v4.2dev5
System information
Godot v4.2.dev5 - Windows 11- GLES3 (Compatibility) - NVIDIA GeForce GT 1030 (NVIDIA; <IP_ADDRESS>42) - AMD 4700S 8-Core Processor Desktop Kit (16 Threads)
Issue description
AudioStreamRandomizer's random_volume_offset_db does not make any audio volume variations playing an WAV file through an AudioStreamPlayer.
Steps to reproduce

Create an AudioStreamPlayer node
Load an AudioStreamRandomizer
Load an WAV file
Set Volume Offset to any value

Playing it gives the same audio level everytime
Minimal reproduction project
ASRandomizer Bug.zip

Confirmed. Looks like the value is set but not used when play the audio.

I don't know if it's worth mentioning, but I also checked the stable Godot v4.1.1 and the issue is also occuring there.


Ip balancer with more than one service ips

Can you explain to me what exactly this piece of code is done?
https://github.com/noxrepo/pox/blob/412a6adb38cb646748c8cfb657549787ab6d2e88/pox/misc/ip_loadbalancer.py#L336
I want to parse more than one service ip and to handle them inside class iplb, but I do not understand the use of this command

This and the block of code above it make the load balancer respond to ARPs, if I remember correctly.


zuul.servletPath=/  and zuul-health-check , can both be achieved?

Our calling chains:  Other App send post http request -> our zuul-gateway -> our microservice
Registry: Eureka
Spring-cloud: Dalston.SR5
zuul setting:
zuul.servletPath=/
eureka.instance.health-check-url = /health
When we process chinese garbled filename,  other apps do not want to change the  url.
Updating the whole Spring-cloud  costs a lot.
Thus, we set zuul.servletPath=/ . However, the health-check-url in zuul  does not work. Is there any solution to both achieve these two settings?
Our temporary solution:
Modify the class FormHttpMessageConverter in Spring-MVC to encoding filename with utf-8

This module has entered maintenance mode. This means that the Spring Cloud team will no longer be adding new features to the module. We will fix blocker bugs and security issues, and we will also consider and review small pull requests from the community.


Fix organization's profile picture wording

Whoops, this was already tracked by: https://github.com/NuGet/NuGetGallery/issues/6096


Multiple macro pages / bound key is displayed in the GUI menu without having to hit edit.

Hello,
I think this mod can benefit greatly with two features.
One would be having multiple nameable macro pages that you can swap too without having to rebind all your keys if dealing with a ton of macros and allows us to save different settings that we can swap too on the fly.
Secondly, this is a minor request but I'd like the ability to see what keys I have bound in the GUI where the list of all the commands we have are. Currently you have to click the edit macro button to see what key you have bound and it's hard to keep track of.
Here is a quick image displaying an example

I will definitely implement both features. Thanks :D

I will definitely implement both features. Thanks :D

Thanks! Looking forward to it.


create pipeline component for tagging phonological features

this would more properly be called the Phonologizer, and it could borrow heavily from spaCy's Morphologizer. see for reference Wikipedia on "distinctive features".

ultimately this could just be another function of the Phonemizer — when the output of the model is just a vector, it's up to the component how to translate that information into phonological data. we could have a new component type that sets phonological properties on tokens, or we could just make this a method available on the Token itself, so that the downstream consumer can request both the phonological features or the phonemes themselves from the same source data.

this becomes synonymous with the existing phonemizer as part of #24; we should rename it Phonologizer accordingly.
also with #22 we should make both components respect overwrite/extend config options (as spacy builtins do) so that they can work together in concert: rule-based runs first, then the statistical version runs and fills in all the gaps (e.g. polyphones).


Cs amador bio

.

Looks good

hi there ! Did you get an email from me ? I put your id in my request.

where is the thumbs up