Lapce crashes at character insertion then deletion when one of the cursors is at offset 0

Lapce Version
master
System information
Windows 11
Describe the bug

Place a cursor at offset 0, and another somewhere else
Press spacebar
Press backspace
Observe the following crash: thread 'main' panicked at 'attempt to subtract with overflow', lapce-core\src\syntax\edit.rs:118:13

Does this https://github.com/lapce/lapce/pull/1366 fix it?

no

It fixes the insert, but then after deleting what I inserted, Lapce still crashes on the same line. I updated the issue with the new line number and new instructions

@MinusGix Can you please have a look at this?

I don't think we really need that crashing line and shift calculation at all with CountMatcher::NonZero. It properly iterates deleted lines.


Bugfix Speed up emissions processing in PTMET subroutine

Contact:
Ben Murphy (US EPA)
Type of code change:
Bugfix
Description of changes:
The PTMET subroutine is streamlined so that it is not run for every point source and every stream every time each stream is called.
Issue:
Before CMAQv5.3, the PTMET subroutine looped over the every point source stream file to retrieve meteorological conditions for calculating plume height. When the DESID emissions module was added, the stream loop was conceptualized and implemented at a higher level, but PTMET still looped over every stream, effectively re-retrieving data more times than necessary. With this PR, the loop inside PTMET is removed and the stream number is passed into the subroutine instead.
Summary of Impact:
Drastically reduces runtimes in areas where there happen  to be lots of point sources on a particular processor. No impact on results.
Tests conducted:
This improvement was tested on the CONUS 2016 platform and on the EQUATES platform for 2015.

This summary documents the internal evaluation of this update (added by Ben Murphy):

Very long run-times in VDIFF are correlated with instances of large per-processor numbers of point sources (>100,000). See fig 1.Figure 1. Impact the number of point sources on a sub-domain on VDIFF runtimes.Because of the need for sharing data among processors in the next module (horizontal advection), the entire program is limited by the maximum time necessary to complete VDIFF among all the processes. The minimum achievable sub-process time for VDIFF (i.e. if no point sources are in the simulation) appears to be about 1-1.2 seconds.This PR reduces the runtime necessary to read and process point sources and thus reduces the overall model runtime, especially in simulations that have sub-domains with large numbers of point sources (e.g. EQUATES). See Fig. 2. This speed-up is accomplished with four improvements:PTMET_CONVT: the code was interpolating met conditions for every point source on every point stream every time each point stream was called, thus redundant by a factor of N_streams. The updated code only calculated the met conditions for the current stream.PT3D_DEFN: the base code reads point source emissions into a structure with multiple entries corresponding to each stream. The updated code replaces this structure variable with a simple vector to reduce cache misses and make the storing and subsequent use of the emission rates more efficient.PT3D_DEFN: PT_LAYS was diagnosed in the base code within an inefficient loop that was not vectorized. The update diagnoses PT_LAYS (now named PTLAYS to match EMLAYS) using vector operations and then applies it to the subsequent population of VDEMIS_PT so that calculations are skipped for layers without information.PT3D_DEFN: the variables containing the stack row, column and emissions are now preloaded and calculated in an order that minimizes inefficient memory accesses.Figure 2. Same as Fig. 1, but with the updates in this PR active.I have successfully run the code in debug and standard mode on all 3 compilers. There is no impact on ACONC values and the impact on model runtime is quite significant (Fig. 3).Figure 3. Model Runtimes for conventional CONUS 2016 domain (Dec 22, 2015) and EQUATES 2015 domain (Jan 1, 2015). 'Opt' indicates the model with this PR adopted.Table 1. 1-day speedup for each compiler in each tested scenario.

Scenario
Intel18
gcc
pgi

CONUS 2016
-15%
-6%
-10%

EQUATES 2015
-38%
-15%
-25%

There are still very significant penalties for running GNU Fortran or Portland Group Fortran, and these should be resolved.I recommend merging this PR as soon as possible to mitigate runtimes that are longer than necessary.

This PR passes the following build and run checks:
- Compilers: Intel, GNU, Portland Group
- Compile Mode: Optimized, Debug
- Model Scenario: 2016 Southeast U.S. Benchmark


game.input.activePointer worldX / worldY not updated when mouse pointer is kept down and mouse isn't moved.

<!--
## Version
* Phaser Version: Phaser v3.17.0-FB
* Operating system: Fedora Linux

## Description
When I click somewhere my character moves to that position.
When I keep the click down, my character should follow the mouse pointer, but if I don't move it at all, the worldX and worldY coordinates aren't updated at all.

I've made a video to illustrate it : https://youtu.be/2uPZv5aEP9c

## Example Test Code
```javascript
  update(time, delta) {
    if(this.game.input.activePointer.isDown){
      console.log(this.game.input.activePointer.worldX, this.game.input.activePointer.worldY)
    }
```
Also, the camera follows the character, this code is run when the player character information are received from the websockets server:
```javascript
      this.camera = this.cameras.main
      this.camera.scaleManager.setZoom(0)
      this.camera.startFollow(this.characters[character.id])
```

## Additional Information

I think that worldX and worldY coordinates in game.input.activePointer are only updated when the mouse moves or when the click is pressed.
The problem is, in games where the camera follows the character, even if the mouse doesn't move, the world coordinates change with the movement of the player.

Wow, my whole description got deleted... :'(
So I'm using  Phaser v3.17.0-FB and this bug isn't related to OS / browser.
The problem I'm having is that when I keep the mouse click pressed, and I don't move the mouse, the coordinates of game.input.activePointer.worldX / Y aren't updated.
I've made a video to illustrate the bug : https://www.youtube.com/watch?v=2uPZv5aEP9c
I don't think code can really illustrate the problem. It's a very specific case.
Thank you.

The worldX/Y values are only valid at the time the callback is invoked. If the pointer doesn't move, they don't update. 3.19 gave you the following method to work around this:
Pointer.updateWorldPoint is a new method that takes a Camera and then updates the Pointers worldX and worldY values based on the cameras transform


Add Builder interface for improved FunctionCallback construction

Problem
The current FunctionCallbackWrapper.Builder implementation has several limitations:

Lacks support for generic type parameters
Builder implementation is tightly coupled with FunctionCallbackWrapper
No standardized interface for different builder implementations
Schema generation is limited to simple class types

Proposed Solution
Introduce a proper FunctionCallback.Builder interface that:

Supports generic type parameters through Spring's ResolvableType
Provides a clean separation between interface and implementation
Enables custom builder implementations while maintaining consistent API
Adds JSON schema generation support for generic types

Resolved by https://github.com/spring-projects/spring-ai/pull/1732


Fix check-git-abc Makefile target

What are the reasons/motivation for this change?
https://github.com/YosysHQ/yosys/issues/4383
Explain how this is achieved.
Add the condition that if git submodule status abc results in a string starting with - then the git submodule is uninitialized.
If applicable, please suggest to reviewers how they can test the change.
Clone the repo, run make or make check-git-abc, examine instructions to initialize the submodule, git submodule update --init, re-run make or make check-git-abc and there should not be any error.

@dopamane thanks for changes suggestions.  Please note there are couple of cases we need to handle here

no "abc" directory ( ask for submodule init)
there is "abc" directory but it is empty ( ask for submodule init)
there is existing "abc" from before the change and there is .gitcommit (with "$Format:%h$")  ask for it to be removed and initialized
there is existing "abc" with .gitcommit containing  git revision number (this is fine it is unpacked abc tarball)

Last one is special case we need to handle for users not using git but  building all from source tarballs.
Meta code that should cover this
if abc dir exists
   if abc/.gitcommit is not "$Format:%h$"
          all fine abc tarball, just exit
   else if abc submodule status is "-"
          using old abc checkout, remove and initialize
   else
         all fine
else
   ask for submodule init

@dopamane Could you please take a look at https://github.com/YosysHQ/yosys/pull/4386 and if this one works fine for you.


Feature/kube to manged environment

In relation to:
https://github.com/nitrictech/cli/issues/232
Has been tested and fixes the above issue.

Codecov Report

Merging #233 (fdf7dae) into develop (3f0d71f) will decrease coverage by 0.13%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##           develop     #233      +/-   ##
===========================================
- Coverage    35.11%   34.98%   -0.14%
===========================================
  Files           49       49
  Lines         4317     4316       -1
===========================================
- Hits          1516     1510       -6
- Misses        2652     2655       +3
- Partials       149      151       +2

Flag
Coverage Δ

unittests
34.98% <0.00%> (-0.14%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/provider/pulumi/azure/azure.go
7.10% <0.00%> (ø)

pkg/provider/pulumi/azure/containerapp.go
0.00% <0.00%> (ø)

pkg/provider/pulumi/azure/serviceprinciple.go
0.00% <0.00%> (ø)

pkg/ghissue/buglink.go
90.32% <0.00%> (-9.68%)
:arrow_down:

pkg/utils/paths.go
5.00% <0.00%> (-5.00%)
:arrow_down:

Continue to review full report at Codecov.

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


Lookup errors on demand

Allow errors to be searched for on demand (such as a database) using a dependency injection approach

Moved to external function, need to write some tests using database to see if this works as a consumer


Common identifiers validation

Fixes #3797
Rather than keep two similar but slightly divergent regular expression validators, I propose we ditch the namespaces validator and use the pre-existing identifiers package in namespaces like it is used elsewhere. Neither validation was actually keeping to RFC 1035 section 2.3.1 rules, so I also clarified the commentary in the identifiers package and added a test to show the validity of numerals following periods.

Codecov Report

Merging #3798 into master will decrease coverage by 0.04%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #3798      +/-   ##
==========================================
- Coverage   42.03%   41.98%   -0.05%
==========================================
  Files         131      130       -1
  Lines       14589    14577      -12
==========================================
- Hits         6132     6120      -12
  Misses       7543     7543
  Partials      914      914

Flag
Coverage Δ

#linux
45.42% <0%> (-0.05%)
:arrow_down:

#windows
36.94% <0%> (-0.07%)
:arrow_down:

Impacted Files
Coverage Δ

identifiers/validate.go
100% <ø> (ø)
:arrow_up:

metadata/namespaces.go
0% <0%> (ø)
:arrow_up:

events/exchange/exchange.go
68.91% <0%> (ø)
:arrow_up:

namespaces/context.go
55.55% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

LGTM


Fixes #73

Update git-url-parse package version
Fix parse-path vulnerability

Isn't this a duplicate of #72 that can be closed?

Yep, closing now.


Unit Testing

Based on Issue #177 and @abhisheksp 's reply to #160 I wanted to write some unit tests to automatically confirm that the result is sufficiently random. But when I add them to test_fact.py and run py.test with the bot running locally (via python jarvis.py in another window) I just get an error message as the result of each query to modules.search('fact') (specifically: {"text": "Something didn't work as expected! I'll report this to my master."}
Am I missing a step to get an actual response to test script queries run locally? I'd like to do this in order to be able to contribute some unit tests that verify that results are correct. As things stand, all of the tests I looked at just seem to verify that the query gets sent to the correct module.

You have to set your own keys in config.py, that's all.
I'd be extremely happy to include more unit tests! 😄
You're more than welcome to work on this.

@edadesd Will you be willing to work on this?

I'll look into this some more and let you know if I can commit to working on it.

Say you want to test dictionary module locally, then you'll have to set WORDS_API_KEY here: https://github.com/swapagarwal/JARVIS-on-Messenger/blob/master/config.py

The facts module does not have a relevant API key because the facts source file is a local file. But when I run test_fact the only return I ever get is {'text':'Something didn't work as expected! I'll report this to my master.'}

No, you only need a FB token to interact with messenger.
Try using this command:
py.test modules/tests/test_fact.py
Let's first only work on unit tests for one module (fact).
Initial structure looks good. We can even assert that the text is one of the lines in facts.json.

That command got me an actual response from the facts file. I submitted pull request #222 based on your comments to the above examples.

The Anime module was first on the list, so I'm working on some more tests for it. I'm basing it on a shuffled list of test titles and comparing the module's response to what I get from an API call made during the test, in addition to checking that the expected items are returned in the payload.


Allow two simultaneous auth tokens

Users should be able to be logged in on two devices at once, since we have an iOS and iPadOS version. Currently this is not possible because we dispose of a previous token as soon as a new one is created upon login, but we should only dispose old tokens if there are more than 2.

Closing in favour of #31


Implement IntoFormat for &T

Summary

Test Plan

Current dependencies on/for this PR:

main

PR #4781   👈

This comment was auto-generated by Graphite.


Delete User Data not deleting data in Cloud Firestore

Describe your configuration

Extension name:  Delete User Data
Configuration values:

Cloud Firestore path: users/{UID}
Realtime Database and Cloud Storage: unspecified

Cloud Firestore structure: /user/{UID}/
Describe the problem
Regardless of whether I delete a user from the console or the client (Android app), the user's document nor any sub-collections/documents are deleted. This occurs whether the user is created via the console or the client.
Function logs indicate that it finishes with status OK.

Hey @DavidPrecopia
Not sure if it's a typo, however above you mention the config value is users while the structure is user - that will be the issue if it's not a typo.

It’s a typo - I just triple-checked the console and it’s users in both places.

Ok, the other thing which has caught users out in the past is trailing spaces in the path names (which are valid Collection paths). If you go onto the console, click "Reconfigure extension" and highlight the box, just make sure there is no additional spaces on the end.

Checked, no whitespace.

After playing around some more I found out that the function only deletes the user document if does not contain sub-collection(s) with documents. If the sub-collection(s) is empty, the function deletes the user document.
Additionally, if the user document contains fields and a sub-collection with documents, the fields are deleted, but the sub-collection is left untouched.

There is currently code waiting to go into prod which handles nested sub-document delete using firebase-tools. That being said, if a document has sub-collections at the moment, that shouldn't impact the actual document being deleted.

Hi @DavidPrecopia, could you run the following command on your machine:
firebase ext:list --project=<name> --json

Could you extract the item for your deployed extension and ensure any sensitive data is removed. I'm not seeing this issue myself so understanding the exact instance config would be very helpful. Thanks!

Here you go @Ehesp,
{
  "status": "success",
  "result": {
    "instances": [
      {
        "name": "projects/lists-debug/instances/delete-user-data",
        "createTime": "2019-11-03T21:09:45.767898Z",
        "updateTime": "2019-11-05T18:43:49.548008Z",
        "state": "ACTIVE",
        "config": {
          "name": "projects/lists-debug/instances/delete-user-data/configurations/394e8b1f-a7b4-41e6-b6bc-cac55bffd1d9",
          "createTime": "2019-11-05T18:42:06.159691Z",
          "source": {
            "name": "projects/firebasemods/sources/8deccc46-5537-4631-929a-d087c961cee5",
            "packageUri": "http://storage.googleapis.com/bkend-firebase-tools/delete-user-data.1568839870.zip",
            "hash": "be5c4ff2ed9da9993e01884918d6f5c87dd65765c06d81e0184ae082cf91b41b",
            "spec": {
              "specVersion": "v1beta",
              "name": "delete-user-data",
              "version": "0.1.1",
              "description": "Deletes data keyed on a userId from Cloud Firestore, Realtime Database, and/or Cloud Storage when a user deletes their account.",
              "roles": [
                {
                  "role": "datastore.user",
                  "reason": "Allows the extension to delete (user) data from Cloud Firestore."
                },
                {
                  "role": "firebasedatabase.admin",
                  "reason": "Allows the extension to delete (user) data from Realtime Database."
                },
                {
                  "role": "storage.admin",
                  "reason": "Allows the extension to delete (user) data from Cloud Storage."
                }
              ],
              "resources": [
                {
                  "name": "clearData",
                  "type": "firebaseextensions.v1beta.function",
                  "propertiesYaml": "eventTrigger:\n  eventType: providers/firebase.auth/eventTypes/user.delete\n  resource: projects/${PROJECT_ID}\nlocation: ${LOCATION}\nsourceDirectory: .\n",
                  "description": "Listens for user accounts to be deleted from your project's authenticated users, then removes any associated user data (based on Firebase Authentication's User ID) from Realtime Database, Cloud Firestore, and/or Cloud Storage.",
                  "deletionPolicy": "DELETE"
                }
              ],
              "author": {
                "authorName": "Firebase",
                "url": "https://firebase.google.com"
              },
              "contributors": [
                {
                  "authorName": "Lauren Long",
                  "url": "https://github.com/laurenzlong"
                },
                {
                  "authorName": "Chris Bianca",
                  "email"<EMAIL_ADDRESS>                  "url": "https://github.com/chrisbianca"
                }
              ],
              "license": "Apache-2.0",
              "releaseNotesUrl": "https://github.com/firebase/extensions/commits/master",
              "sourceUrl": "https://github.com/firebase/extensions/tree/master/delete-user-data",
              "params": [
                {
                  "param": "LOCATION",
                  "label": "Deployment location",
                  "type": "SELECT",
                  "description": "Where should the extension be deployed? You usually want a location close to your database. For help selecting a location, refer to the [location selection guide](https://firebase.google.com/docs/functions/locations#selecting_regions_for_firestore_and_storage).",
                  "required": true,
                  "options": [
                    {
                      "value": "us-central1",
                      "label": "Iowa (us-central1)"
                    },
                    {
                      "value": "us-east1",
                      "label": "South Carolina (us-east1)"
                    },
                    {
                      "value": "us-east4",
                      "label": "Northern Virginia (us-east4)"
                    },
                    {
                      "value": "europe-west1",
                      "label": "Belgium (europe-west1)"
                    },
                    {
                      "value": "europe-west2",
                      "label": "London (europe-west2)"
                    },
                    {
                      "value": "asia-east2",
                      "label": "Hong Kong (asia-east2)"
                    },
                    {
                      "value": "asia-northeast1",
                      "label": "Tokyo (asia-northeast1)"
                    }
                  ],
                  "default": "us-central1"
                },
                {
                  "param": "FIRESTORE_PATHS",
                  "label": "Cloud Firestore paths",
                  "type": "STRING",
                  "description": "Which paths in your Cloud Firestore instance contain user data? Leave empty if you don't use Cloud Firestore.\nEnter the full paths, separated by commas. You can represent the User ID of the deleted user with `{UID}`.\nFor example, if you have the collections `users` and `admins`, and each collection has documents with User ID as document IDs, then you can enter `users/{UID},admins/{UID}`.",
                  "example": "users/{UID},admins/{UID}"
                },
                {
                  "param": "RTDB_PATHS",
                  "label": "Realtime Database paths",
                  "type": "STRING",
                  "description": "Which paths in your Realtime Database instance contain user data? Leave empty if you don't use Realtime Database.\nEnter the full paths, separated by commas. You can represent the User ID of the deleted user with `{UID}`.\nFor example: `users/{UID},admins/{UID}`.",
                  "example": "users/{UID},admins/{UID}"
                },
                {
                  "param": "STORAGE_PATHS",
                  "label": "Cloud Storage paths",
                  "type": "STRING",
                  "description": "Where in Google Cloud Storage do you store user data? Leave empty if you don't use Cloud Storage.\nEnter the full paths, separated by commas. You can represent the User ID of the deleted user with `{UID}`. You can use `{DEFAULT}` to represent your default bucket.\nFor example, if you are using your default bucket, and the bucket has files with the naming scheme `{UID}-pic.png`, then you can enter `{DEFAULT}/{UID}-pic.png`. If you also have files in another bucket called `my-awesome-app-logs`, and that bucket has files with the naming scheme `{UID}-logs.txt`, then you can enter `{DEFAULT}/{UID}-pic.png,my-awesome-app-logs/{UID}-logs.txt`.",
                  "example": "{DEFAULT}/{UID}-pic.png,my-awesome-app-logs/{UID}-logs.txt"
                }
              ],
              "preinstallContent": "Use this extension to automatically delete a user's data if the user is deleted from your authenticated users.\n\nYou can configure this extension to delete user data from any or all of the following: Cloud Firestore, Realtime Database, or Cloud Storage. Each trigger of the extension to delete data is keyed to the user's UserId.\n\n**Note:** To use this extension, you need to manage your users with Firebase Authentication.\n\nThis extension is useful in respecting user privacy and fulfilling compliance requirements. However, using this extension does not guarantee compliance with government and industry regulations.\n\n#### Additional setup\n\nDepending on where you'd like to delete user data from, make sure that you've set up [Cloud Firestore](https://firebase.google.com/docs/firestore), [Realtime Database](https://firebase.google.com/docs/database), or [Cloud Storage](https://firebase.google.com/docs/storage) in your Firebase project before installing this extension.\n\nAlso, make sure that you've set up [Firebase Authentication](https://firebase.google.com/docs/auth) to manage your users.\n\n#### Billing\n\nThis extension uses other Firebase or Google Cloud Platform services which may have associated charges:\n\n- Cloud Firestore\n- Firebase Realtime Database\n- Cloud Storage\n- Cloud Functions\n\nWhen you use Firebase Extensions, you're only charged for the underlying resources that you use. A paid-tier billing plan is only required if the extension uses a service that requires a paid-tier plan, for example calling to a Google Cloud Platform API or making outbound network requests to non-Google services. All Firebase services offer a free tier of usage. [Learn more about Firebase billing.](https://firebase.google.com/pricing)\n",
              "postinstallContent": "### See it in action\n\nYou can test out this extension right away:\n\n1.  Go to your [Authentication dashboard](https://console.firebase.google.com/project/${param:PROJECT_ID}/authentication/users).\n\n1.  Click **Add User** to add a test user.\n\n1.  Copy the test user's UID to your clipboard.\n\n1.  Create a new Cloud Firestore document, a new Realtime Database entry, or upload a new file to Storage - incorporating the user's UID into the path according to the schema that you configured.\n\n1.  Go back to your [Authentication dashboard](https://console.firebase.google.com/project/${param:PROJECT_ID}/authentication/users), then delete the test user.\n\n1.  In a few seconds, the new data you added above will be deleted from Cloud Firestore, Realtime Database, and/or Storage (depending on what you configured).\n\n### Using the extension\n\nWhen a user's account is deleted from your project's authenticated users, this extension automatically deletes their data from Cloud Firestore, Realtime Database, and/or Cloud Storage.\n\n* Cloud Firestore path(s): `${param:FIRESTORE_PATHS}`\n* Realtime Database path(s): `${param:RTDB_PATHS}`\n* Cloud Storage path(s): `${param:STORAGE_PATHS}`\n\nYou can delete a user directly in your [Authentication dashboard]((https://console.firebase.google.com/project/${param:PROJECT_ID}/authentication/users)) or by using one of the Firebase Authentication SDKs. Learn more in the [Authentication documentation](https://firebase.google.com/docs/auth).\n\n### Monitoring\n\nAs a best practice, you can [monitor the activity](https://firebase.google.com/docs/extensions/manage-installed-extensions#monitor) of your installed extension, including checks on its health, usage, and logs.\n",
              "readmeContent": "# delete-user-data\n\n**VERSION**: 0.1.1\n\n**DESCRIPTION**: Deletes data keyed on a userId from Cloud Firestore, Realtime Database, and/or Cloud Storage when a user deletes their account.\n\n\n\n**CONFIGURATION PARAMETERS:**\n\n* Deployment location: Where should the extension be deployed? You usually want a location close to your database. For help selecting a location, refer to the [location selection guide](https://firebase.google.com/docs/functions/locations#selecting_regions_for_firestore_and_storage).\n\n* Cloud Firestore paths: Which paths in your Cloud Firestore instance contain user data? Leave empty if you don't use Cloud Firestore.\nEnter the full paths, separated by commas. You can represent the User ID of the deleted user with `{UID}`.\nFor example, if you have the collections `users` and `admins`, and each collection has documents with User ID as document IDs, then you can enter `users/{UID},admins/{UID}`.\n\n* Realtime Database paths: Which paths in your Realtime Database instance contain user data? Leave empty if you don't use Realtime Database.\nEnter the full paths, separated by commas. You can represent the User ID of the deleted user with `{UID}`.\nFor example: `users/{UID},admins/{UID}`.\n\n* Cloud Storage paths: Where in Google Cloud Storage do you store user data? Leave empty if you don't use Cloud Storage.\nEnter the full paths, separated by commas. You can represent the User ID of the deleted user with `{UID}`. You can use `{DEFAULT}` to represent your default bucket.\nFor example, if you are using your default bucket, and the bucket has files with the naming scheme `{UID}-pic.png`, then you can enter `{DEFAULT}/{UID}-pic.png`. If you also have files in another bucket called `my-awesome-app-logs`, and that bucket has files with the naming scheme `{UID}-logs.txt`, then you can enter `{DEFAULT}/{UID}-pic.png,my-awesome-app-logs/{UID}-logs.txt`.\n\n\n\n**CLOUD FUNCTIONS CREATED:**\n\n* clearData (providers/firebase.auth/eventTypes/user.delete)\n\n\n\n**DETAILS**: Use this extension to automatically delete a user's data if the user is deleted from your authenticated users.\n\nYou can configure this extension to delete user data from any or all of the following: Cloud Firestore, Realtime Database, or Cloud Storage. Each trigger of the extension to delete data is keyed to the user's UserId.\n\n**Note:** To use this extension, you need to manage your users with Firebase Authentication.\n\nThis extension is useful in respecting user privacy and fulfilling compliance requirements. However, using this extension does not guarantee compliance with government and industry regulations.\n\n#### Additional setup\n\nDepending on where you'd like to delete user data from, make sure that you've set up [Cloud Firestore](https://firebase.google.com/docs/firestore), [Realtime Database](https://firebase.google.com/docs/database), or [Cloud Storage](https://firebase.google.com/docs/storage) in your Firebase project before installing this extension.\n\nAlso, make sure that you've set up [Firebase Authentication](https://firebase.google.com/docs/auth) to manage your users.\n\n#### Billing\n\nThis extension uses other Firebase or Google Cloud Platform services which may have associated charges:\n\n- Cloud Firestore\n- Firebase Realtime Database\n- Cloud Storage\n- Cloud Functions\n\nWhen you use Firebase Extensions, you're only charged for the underlying resources that you use. A paid-tier billing plan is only required if the extension uses a service that requires a paid-tier plan, for example calling to a Google Cloud Platform API or making outbound network requests to non-Google services. All Firebase services offer a free tier of usage. [Learn more about Firebase billing.](https://firebase.google.com/pricing)\n\n\n\n**ACCESS REQUIRED**:\n\n\n\nThis extension will operate with the following project IAM roles:\n\n* datastore.user (Reason: Allows the extension to delete (user) data from Cloud Firestore.)\n\n* firebasedatabase.admin (Reason: Allows the extension to delete (user) data from Realtime Database.)\n\n* storage.admin (Reason: Allows the extension to delete (user) data from Cloud Storage.)\n",
              "displayName": "Delete User Data"
            },
            "fetchTime": "2019-09-18T20:51:29.052758576Z",
            "lastOperationName": "projects/firebasemods/operations/f4893ccb-b57f-4a53-9df1-4b94345df1f8"
          },
          "params": {
            "LOCATION": "us-central1",
            "FIRESTORE_PATHS": "users/{UID}"
          },
          "populatedPostinstallContent": "### See it in action\n\nYou can test out this extension right away:\n\n1.  Go to your [Authentication dashboard](https://console.firebase.google.com/project/lists-debug/authentication/users).\n\n1.  Click **Add User** to add a test user.\n\n1.  Copy the test user's UID to your clipboard.\n\n1.  Create a new Cloud Firestore document, a new Realtime Database entry, or upload a new file to Storage - incorporating the user's UID into the path according to the schema that you configured.\n\n1.  Go back to your [Authentication dashboard](https://console.firebase.google.com/project/lists-debug/authentication/users), then delete the test user.\n\n1.  In a few seconds, the new data you added above will be deleted from Cloud Firestore, Realtime Database, and/or Storage (depending on what you configured).\n\n### Using the extension\n\nWhen a user's account is deleted from your project's authenticated users, this extension automatically deletes their data from Cloud Firestore, Realtime Database, and/or Cloud Storage.\n\n* Cloud Firestore path(s): `/users/{UID}`\n* Realtime Database path(s): `{unspecified parameter}`\n* Cloud Storage path(s): `{unspecified parameter}`\n\nYou can delete a user directly in your [Authentication dashboard]((https://console.firebase.google.com/project/lists-debug/authentication/users)) or by using one of the Firebase Authentication SDKs. Learn more in the [Authentication documentation](https://firebase.google.com/docs/auth).\n\n### Monitoring\n\nAs a best practice, you can [monitor the activity](https://firebase.google.com/docs/extensions/manage-installed-extensions#monitor) of your installed extension, including checks on its health, usage, and logs.\n"
        },
        "lastOperationName": "projects/lists-debug/operations/2ec120fc-85d5-4797-8909-5dec5746a13d",
        "serviceAccountEmail": "REDACTED"
      }
    ]
  }
}

Fixed as of v0.1.2.


Remnants of the Precursors!

I'm the flathub maintainer... all the data is here in https://github.com/flathub/com.remnantsoftheprecursors.ROTP/blob/master/com.remnantsoftheprecursors.ROTP.metainfo.xml

Thanks. Please give me a bit more context. Do you want to add a game to the list or modify an existing entry? What is the name of the game, is there another website for it.

name: Remnants of the Precursors
GPL-3.0-only
developer_name: Ray Fowler
A polished modernization of the original Master of Orion Strategy game from 1993.
Remnants of the Precursors is a modernization of the 1993 strategy game "Master of Orion". You will play as one of 10 unique races and lead them to galactic domination or, if you fail, humiliation and defeat. Micromanagement is minimal and the gameplay smooth and streamlined.
https://img.itch.zone/aW1hZ2UvMTc1MzcwLzgxODY4NC5qcGc=/original/udnpsm.jpg
https://img.itch.zone/aW1hZ2UvMTc1MzcwLzgxODM2My5qcGc=/original/f7%2Fd9g.jpg
https://img.itch.zone/aW1hZ2UvMTc1MzcwLzgxODM3My5wbmc=/original/hR1W%2Bh.png
https://img.itch.zone/aW1hZ2UvMTc1MzcwLzgxODM1Ni5qcGc=/original/wfdokK.jpg
https://img.itch.zone/aW1hZ2UvMTc1MzcwLzgxODM1Ny5qcGc=/original/FdNZv8.jpg
homepage: https://www.remnantsoftheprecursors.com
manual: https://raw.githubusercontent.com/rayfowler/rotp-public/master/src/rotp/lang/en/manual.pdf
bugtracker: https://www.reddit.com/r/rotp/comments/ms7r0t/psa_how_to_report_bugs_in_rotp/
donation: https://www.patreon.com/rayfowler

It has been added to this database locally and will appear on Github soon. There is no license information about the artwork. It looks very nice and coherent. Do you know by chance under which license it is?

CC-BY-NC-SA i think

Thanks, that is great news. A fully open source and open content game and quite advanced/mature too.


CBO documentation

See https://docs.starburstdata.com/latest/optimizer.html how this looks like.

CLA check is red, but the commits are annotated with Extracted-From:. @electrum ready for review.

ac

ac


[bittnet] logo is missing on https://firme.peviitor.ro/

bittnet : still working on it. Closing bugs


Support for chai 2.0.0

Peer dependencies in CaP 4.1.1 are currently restricted to chai 1.x:
"peerDependencies": {
    "chai": ">= 1.7.0 < 2"
},

Chai 2.0.0 was released recently, but trying to update using npm update chai with a package.json containing:
"devDependencies": {
    "chai": "^2.0.0",
    "chai-as-promised": "^4.1.1",

yields:
npm ERR! peerinvalid The package chai does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants chai@>= 1.7.0 < 2

:+1:

+1 Ple-e-e-e-ase.

Every +1 comment makes me delay this an extra day. Locking.

Fixed by 0bae928b72683b07c2b82b7974f71c500b5a2451, release coming soon, maybe with some more bug fixes.


When date is changed from backend the ngmodel is not updated from the datepicker

When the date is changed from backend code , we see the changes in the datepicker . But when save operation is done, we see that the old value which was set initially is considered. The new Date is never updated .
Is there a way that we can trigger the date change method from the code.
We are not using Jquery in our application.

Any updates on this?


Requirement for external storage access

Text Fairy currently requires the WRITE_EXTERNAL_STORAGE permission due to it using Environment.getExternalStorageDirectory() in com.renard.ocr.util.Util and com.renard.ocr.install.InstallTask and Environment.getExternalStoragePublicDirectory in com.renard.ocr.documents.creation.NewDocumentActivity.
Could that be changed to Context.getExternalFilesDir()? In that way Text Fairy would

make use of its assigned data directory instead of creating one in the external storage's root
not necessarily require external storage access anymore (unless someone wants to analyse independently taken images)

It could still ask for the permission but would not need to abort if it is not granted.

Thanks for your suggestion. I think it has a lot of merit but then the created pdf files would not be accessible for the user anymore. Let me think about it

They'd be still accessible. getExternalFilesDir() returns a path within the scope of the external storage. It would be the application's data directory on the external storage. The only potential problem could be that the user would lose the files if he uninstalls or resets the application without having prior moved the files elsewhere.

I fixed this on master


deprecate the scripts option

[ ] remove it from documentation
[ ] add a warning to say "instead write the script tag directly in the head option

re: #1270

https://github.com/observablehq/framework/commit/0982521d6db0dd97e28729d1300db2792cc2115b recommends using head


[Dev UI] More metadata in Eval run table

Is your feature request related to a problem? Please describe.
suggestion: would be great to see some kind of a summary here (# of samples, # success/failure ratio)
Additional context

Yes! I'd love to see some total scores, maybe even a graph of the eval scores from every run. That way we can actually compare how different eval runs (with different prompts etc) perform.


 I don't know if someone here can help me or I should consult someone who are familiar with the system of my computer.
I was trying to run the Kelvin-Helmholtz problem with Open-MPI. The problem generator function in the kh.cpp file was modified. It was the first time for me to use Open-MPI, I guess I have done something wrongly so the segmentation fault appear even when I configure Athena++ without the -mpi flag but there was no such problems before the first trial of using MPI.
Below is what I have done and the output
(base) laam@Lees-MacBook-Air athena % a++config --prob kh --nscalar 1 -hdf5 -mpi
...
(base) laam@Lees-MacBook-Air 18 % a++ -i athinput.kh-shear-lecoanet -m 4

Root grid = 2 x 2 x 1 MeshBlocks
Total number of MeshBlocks = 4
Number of physical refinement levels = 0
Number of logical  refinement levels = 1
  Physical level = 0 (logical level = 1): 4 MeshBlocks, cost = 4
Number of parallel ranks = 4
  Rank = 0: 1 MeshBlocks, cost = 1
  Rank = 1: 1 MeshBlocks, cost = 1
  Rank = 2: 1 MeshBlocks, cost = 1
  Rank = 3: 1 MeshBlocks, cost = 1
Load Balancing:
  Minimum cost = 1, Maximum cost = 1, Average cost = 1

See the 'mesh_structure.dat' file for a complete list of MeshBlocks.
Use 'python ../vis/python/plot_mesh.py' or gnuplot to visualize mesh structure.
...
...
(base) laam@Lees-MacBook-Air 18 % mpirun -n 2 ~/athena/bin/athena\ -i\ ~/work/kh/18/athinput.kh-shear-lecoanet
--------------------------------------------------------------------------
mpirun was unable to launch the specified application as it could not access
or execute an executable:

Executable: /Users/laam/athena/bin/athena -i ~/work/kh/18/athinput.kh-shear-lecoanet
Node: Lees-MacBook-Air

while attempting to start process rank 0.
--------------------------------------------------------------------------
2 total processes failed to start

As I failed to run with MPI, I tried
(base) laam@Lees-MacBook-Air 18 % a++ -i athinput.kh-shear-lecoanet -m 1

Root grid = 2 x 2 x 1 MeshBlocks
Total number of MeshBlocks = 4
Number of physical refinement levels = 0
Number of logical  refinement levels = 1
  Physical level = 0 (logical level = 1): 4 MeshBlocks, cost = 4
Number of parallel ranks = 1
  Rank = 0: 4 MeshBlocks, cost = 4
Load Balancing:
  Minimum cost = 1, Maximum cost = 1, Average cost = 1

See the 'mesh_structure.dat' file for a complete list of MeshBlocks.
Use 'python ../vis/python/plot_mesh.py' or gnuplot to visualize mesh structure.

(base) laam@Lees-MacBook-Air 18 % a++ -i athinput.kh-shear-lecoanet
[Lees-MacBook-Air:30732] *** Process received signal ***
[Lees-MacBook-Air:30732] Signal: Segmentation fault: 11 (11)
[Lees-MacBook-Air:30732] Signal code:  (0)
[Lees-MacBook-Air:30732] Failing at address: 0x0
[Lees-MacBook-Air:30732] [ 0] 0   libsystem_platform.dylib            0x00007fff6bf5f5fd _sigtramp + 29
[Lees-MacBook-Air:30732] [ 1] 0   athena                              0x0000000108c29478 _ZTVNSt3__118basic_stringstreamIcNS_11char_traitsIcEENS_9allocatorIcEEEE + 24
[Lees-MacBook-Air:30732] [ 2] 0   athena                              0x0000000108adc4cf _ZN14ParameterInput10GetIntegerENSt3__112basic_stringIcNS0_11char_traitsIcEENS0_9allocatorIcEEEES6_ + 271
[Lees-MacBook-Air:30732] [ 3] 0   athena                              0x0000000108be0891 _ZN12_GLOBAL__N_12sdEP9MeshBlocki + 161
[Lees-MacBook-Air:30732] [ 4] 0   athena                              0x0000000108bd3259 _ZN13HistoryOutput15WriteOutputFileEP4MeshP14ParameterInputb + 1289
[Lees-MacBook-Air:30732] [ 5] 0   athena                              0x0000000108bdadca _ZN7Outputs11MakeOutputsEP4MeshP14ParameterInputb + 522
[Lees-MacBook-Air:30732] [ 6] 0   athena                              0x0000000108ad735a main + 2154
[Lees-MacBook-Air:30732] [ 7] 0   libdyld.dylib                       0x00007fff6bd66cc9 start + 1
[Lees-MacBook-Air:30732] [ 8] 0   ???                                 0x0000000000000003 0x0 + 3
[Lees-MacBook-Air:30732] *** End of error message ***
zsh: segmentation fault  ~/athena/bin/athena -i athinput.kh-shear-lecoanet

Ever since, even when I configure the code without the -mpi flag, segfault appear. Is that I have altered the environment of my computer?
Thank you for your effort.
Regards,
Laam

This may sound trivial but are you sure that the path to the executable ~/athena/bin/athena is correct, and this is properly configured with MPI? It looks like you used an executable in a directory named "18".
This may also sound trivial, but did you perform "make clean" after reconfiguring the code? The code can fail if object files from previous configuration exist.

It seems mpirun recognize the whole line include the arguments as the executable due to the backslashes. Maybe try getting rid of the backslashes?

This may sound trivial but are you sure that the path to the executable ~/athena/bin/athena is correct, and this is properly configured with MPI? It looks like you used an executable in a directory named "18".
This may also sound trivial, but did you perform "make clean" after reconfiguring the code? The code can fail if object files from previous configuration exist.

Sorry for my late reply. The compilation should be fine and I am sure I have performed make clean. I put the Athena executable in `/athena/bin/athena while the 'athinput.kh-shear-lecoanet' in ~/work/kh/18.
Now, I try to put them in the same directory and delete the backslashes. It works this time.
Thank you so much for your suggestion.


Add support for stream of byte buffers

The main idea is read an spec from a collection of bytebuffers.

Merged in master.


Image jumping on page load

When I load the page with an image gallery slider on it, the images seem to be loading down the page for a split second before the slider 'kicks in' and puts them in place.
Why is this happening? Can anyone suggest a solution?

I've noticed that too. I always thought it was loading the HTML before the javascript and maybe being a little slow about it?

@davim00 Yep!
This is a pretty common issue. Should add it to the readme.md.
.my-slider-name:not(.slick-initialized){...pre initialized styles...}

Hope that helps.


How does this job perform on animal character?

Hi, this is an excellent job. But I found that applying videos to animals dancing can cause facial problems. Is it right?

Thank you for your interest in this work. This work cannot be directly applied to animal character, given the strong constraints of human geometry and motion.

We will consider this advice in the later project.


Add file languages.tsv

This file should be in tsv and provide major information on the languages we want to use, so we talk about Pano and additional languages as contact candidates.
An example for such a file is in allenbai.

@fractaldragonflies, since there never was a response on this, I went ahead and made the file myself. If you want to add or remove languages, please do so following the basic schema, note that the IDS_ID is very important.


Ambiguos medium-level API

Here are functions I'm not sure in. Which are better to discuss.

Considering Nudge I'm wondering in exact numbers for NudgeUnits.
Here is original API documentation:

nudgeunit: 0=ms, 1=seconds, 2=grid, 3=256th notes, ..., 15=whole notes, 16=measures.beats (1.15 = 1 measure + 1.5 beats), 17=samples, 18=frames, 19=pixels, 20=item lengths, 21=item selections

But, when I continued a sequence from 256th to 2th — I've finished on the literal 10, but not on the 14 as I would expect from docs.
I've never used nudge feature, so, here my expertise is out)

Well, not as straight, as I desired...

get_set_project_info_string_set constantly returns false in any language. OK.
get_set_project_info_string_get fails in test with category TrackGroupName(x). But it works in my working instance of Reaper, when built from my extension.

I feel, that AudioAccessor commit is OK. But, for the case, I put it here: not as straight, as type arguments in right order.


Swap even and odd bits(in Java)

🚀 Feature
(A clear and concise description of what the feature is.)
Swap all odd bits with even bits.
For example, if the given number is 23 (00010111), it should be converted to 43 (00101011).
Using Bit Manipulation
The program would be implemented in Java  language.
I am a GSSOC participant.
Have you read the Contributing Guidelines on Pull Requests?
yes

/assign


Add NetBSD instructions

Packaged for NetBSD and merged into the main repo, commit message

oh cool i had no idea! Thanks for the submission! :]

@solidiquis thanks!

i had no idea!

I've merged it today :)

@solidiquis Just FYI, I haven't updated erdtree on NetBSD to the latest release, yet.
The reason is that we are currently on a one week commit freeze ahead of branching the next quaternary stable packages release.
As soon as the freeze is over, the update is on my TODO list :smile:
Regards

@0323pin thank you for taking care of that! If that's the case you might as well wait until the next release (1.7.0) which will be out next Sunday. I plan to slow down a bit after the next release as there will be enough features to satisfy most so the frequency of needing to update erdtree on netbsd won't be as frequent but I'll let you know! Thanks again <33

@solidiquis in that case, I'll wait for 1.7.0, thanks for the heads-up. I'd expect the freeze to last until Monday, unless something large (e.g. Firefox) is broken, in which case, it could take longer. But, I've built Firefox today and it's ok, so it should end on Monday.

Apologies I've been quite busy with work and have fallen a bit behind schedule. 1.7.0 worst case will be out tomorrow night 10pm PDT.

No need to excuse yourself, we are all doing this for free, I was just curious. I'll wait for 1.7.0 to come out, our freeze should end in < 24h but, it's no issue to wait a bit longer.

@0323pin thanks for being understanding and thank you again for doing this. Just letting you know that 1.7.0 is now released and I think it's at the point now where releases won't be as regular :]

@solidiquis thanks for the heads-up. Actually, I've merged [1.6.0] yesterday :)
But, don't worry, I will update to 1.7.0 as soon as possible

1.7.0 merged, http://mail-index.netbsd.org/pkgsrc-changes/2023/03/30/msg271580.html
Tomorrow I'll try to get 1.7.1 merged, need to get some sleep now.


Query->count() fails when parameters are in SELECT statement

the following reasonably simple query fails with an "invalid parameter number" exception.
$query = User::find()
            ->addSelect( ['*', 'CASE WHEN username LIKE :phrase THEN 1 ELSE (0) END AS relevance'] )
            ->where( ['like', 'username', "admin%", false] )
            ->params( [':phrase'   => "admin %"] );

count = $query->count();

when performing the count, yii appears to throw away the select statements (thus removing the bound parameter) and then fails because the provided parameter is no longer in the SQL. i have encountered this problem before. why can't yii simply ignore provided parameters that aren't found in the query?

yii appears to throw away the select statements (thus removing the bound parameter)

Yes, howver it is unlikely we can do anything about it.

can't yii simply ignore provided parameters that aren't found in the query?

It can not: this matter is handled by PDO internally and Yii has not influence on it.
Try to use yii\db\Expression with parameters in your select, this should fix the issue for you:
$query = User::find()
            ->addSelect( [
                '*',
               new Expression( 'CASE WHEN username LIKE :phrase THEN 1 ELSE (0) END AS relevance', [
                   ':phrase'   => "admin %"]
               ])
            ] )
            ->where( ['like', 'username', "admin%", false] );

$count = $query->count();


[MB-4758] Add reviewed all rejected status for payment request in backend

Description
When all service items in a payment request are rejected we need a status to denote that it has been reviewed and rejected so we don't send an invoice request to Syncada.
Here we're adding a new status REVIEWED_AND_ALL_SERVICE_ITEMS_REJECTED to the payment request model, database type, and swagger apis enum.
Reviewer Notes
I refactored some of the model updates in the handler because we seemed to be copying too many values.  I added a test to verify that the handler will work for when we tackle the frontend work.
The database column comment needed to be modified as well since it lists out the enum options.
Setup
To view database column comment:
make schemaspy
open tmp/schemaspy/index.html

Code Review Verification Steps

[ ] If the change is risky, it has been tested in experimental before merging.
[ ] Code follows the guidelines for Logging
[ ] The requirements listed in
Querying the Database Safely
have been satisfied.
Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Screenshots

Messages

:book:
:link: MB-4758

  Generated by :no_entry_sign: dangerJS against 268a431eb76119639087f441529a9e0412824fa3

Messages

:book:
:link: MB-4758

  Generated by :no_entry_sign: dangerJS against 268a431eb76119639087f441529a9e0412824fa3


Add testing of web service

http://dennissuratna.com/testing-in-go/

Service layer for easier testing
https://github.com/tonyhb/tonyhb.com/blob/master/posts/Building a testable Golang database layer.md
https://groups.google.com/forum/#!topic/golang-nuts/9i01tuVo-1E

https://talks.golang.org/2014/testing.slide#1

http://blog.pivotal.io/pivotal-labs/labs/a-rubyist-leaning-go-testing-http-handlers


[BUILD] mvn clean fails if a spark profile is not specified

Bug description
Expected behavior
mvn clean executes successfully.
Actual behavior
Run mvn clean fails with the following message:
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] 'dependencyManagement.dependencies.dependency.artifactId' for io.delta:${delta.package.name}_2.12:jar with value '${delta.package.name}_2.12' does not match a valid id pattern. @ line 491, column 14
 @
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project org.apache.gluten:gluten-parent:1.2.0-SNAPSHOT (/Users/zhouyifan/git/incubator-gluten/pom.xml) has 1 error
[ERROR]     'dependencyManagement.dependencies.dependency.artifactId' for io.delta:${delta.package.name}_2.12:jar with value '${delta.package.name}_2.12' does not match a valid id pattern. @ line 491, column 14
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException

System information
Velox System Info v0.0.2
Commit: a683e318de54f411abdffa2a5a7278c4d98b5803
CMake Version: 3.29.2
System: Darwin-23.4.0
Arch: arm64
C++ Compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
C++ Compiler Version: <IP_ADDRESS>00309
C Compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
C Compiler Version: <IP_ADDRESS>00309
CMake Prefix Path: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.4.sdk/usr;/opt/homebrew;/usr/local;/usr;/;/opt/homebrew/Cellar/cmake/3.29.2;/usr/local;/usr/X11R6;/usr/pkg;/opt;/sw;/opt/local
Relevant logs
No response

This issue should be reported to https://github.com/apache/incubator-gluten


Google Service

Does it support google services?

yes
DevTrinh @.***> 于2022年12月14日周三 17:21写道：

Does it support google services?
—
Reply to this email directly, view it on GitHub
https://github.com/justin0kg/VirtualApp2022/issues/2, or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4JJIUJVV7MS2FKXDDDNLK3WNGGQXANCNFSM6AAAAAAS6G63FE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Yes, I can help you.
DevTrinh @.***> 于2022年12月19日周一 17:55写道：

i'm trying to use it (Google service) but still not working can you help me
—
Reply to this email directly, view it on GitHub
https://github.com/justin0kg/VirtualApp2022/issues/2#issuecomment-1357381622,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4JJIUMVU3QLTGZW3PFQPF3WOAWJXANCNFSM6AAAAAAS6G63FE
.
You are receiving this because you commented.Message ID:
@.***>

please give me telegram or discord or something that can easily exchange information with you, thanks for your help. I'm a beginner, it's really hard for me
https://t.me/ZeusL404


Add option to remove low PLDDT residues from domain assignments on AlphaFold structures

Add some functionality to the post-processing which modifies domain assignments to remove residues which have low PLDDT (which is the b-factor column of PDB files generated by AlphaFold).

I'm working on this currently

in case of any use i did some refactoring to support this here (was intended for unidoc but also compatible with chainsaw): https://github.com/JudeWells/chainsaw/compare/unidoc


build for Apple M1

just work
 $mkdir sdk   $cd sdk   $git clone https://go.googlesource.com/go   $cd go   $git fetch https://go.googlesource.com/go refs/changes/58/272258/1 && git checkout FETCH_HEAD   $cd src   $GOOS=darwin GOARCH=arm64 ./bootstrap.bash
then compile kcptun
env CGO_ENABLED=0 GOOS=darwin GOARCH=arm64 go build -mod=vendor -ldflags "$LDFLAGS" -gcflags "$GCFLAGS" -o client_darwin_arm64  github.com/xtaci/kcptun/client

create a PR to build-release.sh

not  stable, waiting Go 1.16 release


Add logo

#7

Hi @bedis-elacheche , thank you soooooo much for your contribution!
It has been merged to the master branch.
Feel free to add yourself to the contributors section in README!


Not working?

It seems to be giving false positives.  I adding some debugging output into the code, and it doesn't seem to be working at all actually.  I'm a bit confused by this.
Is there any way you can confirm for me that this project is supposed to be still working and if so, can you help me to understand what is going on, on my end?
---------------------------------------------------
2015-02-20 06:42:27,397 E :: {u'__class': u'dedicatedType:dedicatedAvailability2ZoneStruct', u'zone': u'bhs', u'availability': u'unknown'}
2015-02-20 06:42:27,397 SERVER: KS-1 :: ZONE: bhs
2015-02-20 06:42:27,398 E :: {u'__class': u'dedicatedType:dedicatedAvailability2ZoneStruct', u'zone': u'bhs', u'availability': u'unknown'}
2015-02-20 06:42:27,398 SERVER: KS-1 :: ZONE: rbx
2015-02-20 06:42:27,398 E :: {u'__class': u'dedicatedType:dedicatedAvailability2ZoneStruct', u'zone': u'bhs', u'availability': u'unknown'}
2015-02-20 06:42:27,398 SERVER: KS-1 :: ZONE: sbg
2015-02-20 06:42:27,398 E :: {u'__class': u'dedicatedType:dedicatedAvailability2ZoneStruct', u'zone': u'bhs', u'availability': u'unknown'}
2015-02-20 06:42:27,398 SERVER: KS-3 :: ZONE: bhs
2015-02-20 06:42:27,398 E :: {u'__class': u'dedicatedType:dedicatedAvailability2ZoneStruct', u'zone': u'bhs', u'availability': u'unknown'}
2015-02-20 06:42:27,398 SERVER: KS-3 :: ZONE: rbx
2015-02-20 06:42:27,398 State change - KS-3_available_in_rbx: True
2015-02-20 06:42:27,776 E :: {u'__class': u'dedicatedType:dedicatedAvailability2ZoneStruct', u'zone': u'bhs', u'availability': u'unknown'}
2015-02-20 06:42:27,776 SERVER: KS-3 :: ZONE: sbg
2015-02-20 06:42:27,776 E :: {u'__class': u'dedicatedType:dedicatedAvailability2ZoneStruct', u'zone': u'bhs', u'availability': u'unknown'}
2015-02-20 06:42:27,776 SERVER: KS-3 :: ZONE: bhs
2015-02-20 06:42:27,776 E :: {u'__class': u'dedicatedType:dedicatedAvailability2ZoneStruct', u'zone': u'bhs', u'availability': u'unknown'}
2015-02-20 06:42:27,776 SERVER: KS-3 :: ZONE: rbx
2015-02-20 06:42:27,776 State change - KS-3_available_in_rbx: False
2015-02-20 06:42:27,776 E :: {u'__class': u'dedicatedType:dedicatedAvailability2ZoneStruct', u'zone': u'bhs', u'availability': u'unknown'}
2015-02-20 06:42:27,776 SERVER: KS-3 :: ZONE: sbg

Thanks
B

I briefly looked at your logs, but sorry- could not identify the issue. I can tell however that the project is alive, because I get notifications sometimes, follow link and check it. I will take a closer look on next week, when I'm back from vacation.

For reference, the following is the block of code that I changed to get more verbose output.  I added two logger lines.  If I am understanding the JSON correctly, all the lines are referring to zone bhs
            # iterate over all tacked zones and set availability states
            for zone in config['zones']:
                _logger.info("E :: %s", e)
                server = SERVER_TYPES[item['reference']]
                _logger.info("SERVER: %s :: ZONE: %s", server, zone)
                state_id = '%s_available_in_%s' % (server, zone)

I debugged the script carefully and here is what I found:

script runs correctly
your example is logging e - the variable from list comprehension that is always pointing to last element of availability list. That's not relevant to loop you are debugging.
false-positives may be caused by duplicate entries in OVH api, as one entry sometimes has True availability immediately followed by False. Now script is catching this situation and logs it; if that gets too annoying we can put return after _logger.info to retry the whole thing.


Update blog posts for target_project changes in {link,branch}_package steps

 Adapt workflow steps for push events on branches


Fix DeviceConnection::receive

It was typed wrongly before

Thank you for your help! I'm glad to have a second pair of eyes looking at this function. I wrote most of those functions while sleep-deprived on a long plane ride, so thank you!
This would be a semver breaking change, so let's see if there's anything else we want to change while we're in the business of breaking semver (@michaelwright235 might have some items?).

I'm sorry for the late reply... I don't have anything done yet, but I have something in mind that will be semver breaking in the future.


feature/#1346 - new ScaleDiskOverlay class

A demo can be found in the "More Samples / Data / Marker" demo.
New class:

ScaleDiskOverlay: displays a disk of a given radius (distance) around a GeoPoint

Impacts:

GeoConstants: added enum UnitOfMeasure; gently refactored
ScaleBarOverlay: refactored the display of scale text, in order to be reused in ScaleDiskOverlay
strings.xml: created format_distance_only_% and format_distance_value_unit
SampleMarker: added a ScaleDiskOverlay for each POI

i like it, good work


Add more description into attributes for nutanix

I was able to get some informtion here;
https://github.com/nutanix-cloud-native/packer-plugin-nutanix/blob/main/docs/builders/nutanix.mdx
but its not real clear on what each does and can be used fo so it would be good to include a longer explanation of what each attribute is and what it can be used for with an example?

the renderer documentation is available here
https://developer.hashicorp.com/packer/plugins/builders/nutanix
https://developer.hashicorp.com/packer/plugins/builders/nutanix/nutanix
of course there is always room to improvement
what points in particular do you feel need to be improved?
thanks for your help

So maybe its a bit more of the variables too that are confusing me.
like nutanix_ *     All attributes that are used to log in to prisim.    OK perfect.
cluster_name ?      as in nutanix_cluster_name ?   but then description says its the nutanix cluster name.
os_type?  so assuming this some kind of vm, had to go back up to very top to see that this section was about the temporary vm to create the  image?      maybe should be vm_os_type ?   to keep it w/ similar variable names as other corresponding variables?
nutanix_port :     would good to put in the default port number ?
vm_name :    Nice to see this added now for the vm_name for the temporary vm
cpu?    :       aka the vm_cpu ?   for temporary vm ?
memory_mb :     vm_memory_mb ?
cd_files;    these then have a different variable name that obviouslly different from the vm attribute names for the temporary VM  but would be good to add an example here on how to use.
cd_label:    somewhere I believe in the examples folder where OEMDRV was used?   assuming I should be using that label so that it can find any files it may need?   aka kickstarter file ?   Or doesn't this label matter?   Or does it default to OEMDRV?
ip_wait_timeout :   good
vm_categories:    example?
project;   might be good enough,
image-name:  ?  still confusion here on what these are?  vs vm_name    ... doesn't seem to be the temporary iso created and uploaded to images as that's created dynamicaly with cd_files, cd_label
image_description?   above
image_categories?  above
force-deregister?   does that go with the output image_* or vm_*     seems to delete the vm_name type vm that i'm working on creating when if fails.
image_delete?  seems more like thse parameters are for what is put into the images area in nutanix?  where as the vm_* gets put into the vm area ;   aka back to other request to delete these images after packer is run?  maybe that's why they stuck around.    aka ; https://github.com/nutanix-cloud-native/packer-plugin-nutanix/issues/143 ?
image_export?   nots ure what this does, something about exporting a folder to images?   example?
shutdown_command ?  aka   vm_shutdown_command?   better to group this variable with the other vm variables?
shutdown_timeout?  aka vm_shutdown_timeout?   better to group this variable with the other vm variables?
communicator: aka vm_protocol?   decription is helpful for kinda help determine how its trying to connect
user_data ? aka vm_cloudinit ?  example?
ssh username ?  aka vm_ssh_username?
ssh password ? aka vm_ssh_password ?
winrm* all assocated to communicator or vm_protocol?  so could be under that?   vm_protocol_ssh_username, vm_protocol_ssh_password, vm_protocol_winrm_port, vm_protocol_winrm_insecure ? etc?
image_type ?  what 3 parameters?   example?
source_image_name?  is this like the iso image we are using to load windows?   iso_image_name ?     aka like windows / linux?  packer for vmware also was able to download that from a repo and upload it to a vmware datastore?  could this do the same vs having to manually upload the iso dvd of windows / linux to the image repository?
source_image_uuid ? example?
source_image_uri? Example?
source_image_delete? example?
source_image_force?  example?
disk_size_gb?   good example/sample that is included.  that helps.
subnet_name?       good example, helped to undertand this needed to be connected to our network uplink names
subnet_uuid;     ;    could even be vm_subnet_name, and vm_subnet_uuid?
ah, now seeeing an example more of catorries configuation that I was thinking may have been better ot have more up with the other variables?
Not trying to spark an entire remap of things but better descriptions of what they are and how to use them would certaily be a helpful addition.
Thanks!

This is probably too much, big rock.  will close and do more specific requests if needed for documentation.


Introduce new virtual-machine-restarted and container-restarted events

Right now when an instance self-restarts (reboot inside the instance), all we get is a container-started type event.
Instead, we should add logic so that instance initiated reboots only log a single container-restarted event.
Similarly, running lxc restart blah should also only log a single container-restarted event rather than the current container-stopped + container-started combination.

Hey @stgraber  , I want to do this.
Can you guide me a bit?
Thanks.

Assigned it to you.
You can see what events are emitted today with lxc monitor --type=lifecycle and then restart a container/virtual-machine both from inside (lxc exec NAME reboot) or outside (lxc restart NAME).
The current logic can be found in lxd/instance/drivers/driver_lxc.go and lxd/instance/drivers/driver_qemu.go.
I suspect I would do changes in this order:

Add the new event to the reboot section of onStop in both lxc and qemu
Introduce a new Restart(timeout time.Duration) error function in both lxc and qemu (base logic off of what's in lxd/instance_state.go)
Add that function to the interface in lxd/instance/instance_interface.go
Change the current restart logic to use that function in lxd/instance_state.go
Introduce a new operationlock for restart and use checks for that to avoid emitting needless stop/start events when in a restart

With all that done, running either lxc exec NAME reboot or lxc restart NAME against either a container or virtual-machine should yield just a single container-restarted or virtual-machine-restarted event.

Let me know if you have more specific questions when looking at the various bits.
Also feel free to send PRs as you go through this. Pretty much ever bullet-point above should be an improvement on its own and so could be submitted and be merged progressively.


[Feature Request] Add local Helm Chart templates to repository chart release

Let me start with describing the issue I am trying to solve.
Many (official) Helm charts allow you to specify annotations on object descriptions (e.g. ingress descriptions). Ingress controllers support f.e. authentication by looking at annotations on the ingress objects. E.g. ingress.kubernetes.io/auth-type and ingress.kubernetes.io/auth-secret. This ingress.kubernetes.io/auth-secret annotation defines the name of the k8s secret containing the username/password for basic auth.
But the charts don't offer a way to create the secret object. If the chart did include a secret template, you could have used the helm secret-plugin to render.
Manually creating the secrets feels bad...
Another option would be to create a helmfile release based on a local chart, having this local chart containing the secret template. Imho it would be a lot cleaner if this secret would be part of the same Helm release as f.e. the ingress object.
This makes me wonder if it is sensible to have a helmfile feature to merge arbitrary local Helm templates into the chart before rendering.
helmfile.yaml:
releases:
- name: myprometheus
  chart: stable/prometheus
  values:
  - values.yaml
  secrets:
  - secret/my-prometheus-secret.yaml
  templates:
  - templates/basic-auth-secret.yaml

values.yaml:
server:
  ingress:
    enabled: true
    annotations:
      ingress.kubernetes.io/auth-type: "basic"
      ingress.kubernetes.io/auth-secret: prometheus-basic-auth-secret

templates/basic-auth-secret.yaml:
apiVersion: v1
kind: Secret
type: Opaque
metadata:
  name: prometheus-basic-auth-secret
  labels:
    app: {{ template "prometheus.name" . }}
    chart: {{ .Chart.Name }}-{{ .Chart.Version }}
    heritage: {{ .Release.Service }}
    release: {{ .Release.Name }}
data:
  auth: {{ .Values.myPrometheusSecret | b64enc | quote }}

Feature request #392 describes how to get secrets from different backends/sources (Helm secret plugin / Vault / AWS / KeyHub :heart: ) into helmfile. This feature request is about a way to get those secrets into k8s as Secrets as part to the release they belong to.
Dream mode
Being able to add arbitrary Helm templates would allow me to do the following.
Define my own custom resource description containing all the metadata I need to sync a secret from a backend/source to a k8s Secret. A custom k8s controller would then be able to sync the secrets between backend/source and k8s. So changing the secret in the central secret store of truth would take effect without the need to do a deployment (helmfile sync).
And... deployers/releasers don't need access to the secrets themselves, as long as they know the metadata. Only the k8s controller requires access to the secrets.

@sboschman Hey! Thanks for the request, and the detailed explanation.
If you don't mind paraphrasing, you want adhoc resources to be injected into the helm release, right?
If so - yes, I felt similar frustration while using another charts, and wondered how I could fully manage all those with helm.
That being said, I was thinking that using the incubator/raw chart would be a potential solution here?
https://github.com/helm/charts/tree/master/incubator/raw
With the chart, instead of:
releases:
- name: myprometheus
  chart: stable/prometheus
  values:
  - values.yaml
  secrets:
  - secret/my-prometheus-secret.yaml
  templates:
  - templates/basic-auth-secret.yaml

You'll write:
releases:
- name: myprometheus-secret
  chart: incubator/raw
  values:
  - resources:
    - apiVersion: v1
      kind: Secret
      type: Opaque
      metadata:
        name: prometheus-basic-auth-secret
      stringData:
        auth: {{ env "MY_PROM_SECRET" }}
- name: myprometheus
  chart: stable/prometheus
  values:
  - values.yaml
  secrets:
  - secret/my-prometheus-secret.yaml

A few downsides of this approach is that you need to inject the prom secret as an envvar OR maintain not only the secret value but the whole secret object within a secret.yaml to be consumed by helmfile's secrets: field.
For that, I was considering to enhance the incubator/raw chart to accept templates settings, that can be used like:
releases:
- name: myprometheus-secret
  chart: incubator/raw
  values:
  - templates:
    - apiVersion: v1
      kind: Secret
      type: Opaque
      metadata:
        name: prometheus-basic-auth-secret
      stringData:
        auth: {{ .Values.myPrometheusSecret }}
  secrets:
  - secret/my-prometheus-secret.yaml
- name: myprometheus
  chart: stable/prometheus
  values:
  - values.yaml

I can send a PR to incubator/raw if that makes sense (or if you could do so I'd greatly appreciate it :)

PTAL: https://github.com/helm/charts/pull/12422

incubator/raw 0.2.0 has been released :)

@mumoshu Thanks for your elaborate reply.
Yes, it is basically about injecting adhoc / arbitrary resources into the release of a chart. Merging them into the release itself would be great, but I can live with the incubator/raw idea. That saves a lot of boiler plate chart stuff compared to including a local chart.
I have used envvar (required in helm template) for secrets before, and that is less than ideal for sure.
Being able to template stuff into incubator/raw looks like a nice solution to all this. :+1:
I see you beat me to making changes to incubator/raw, going to test them out asap. Thanks for the work!

I have used the incubator/raw successfully and that is a nice idea.
But the chart creates a configmap resource for ci that is present during the chart install :(.
here is an example
- name: test-docker-watcher
  namespace: test
  chart: incubator/raw
  values:
  - templates:
    - |
      {{- readFile "docker-image-change-watcher.yaml" | nindent 6 }}

where I have a pod manifest defined in the docker-image-change-watcher.yaml file.

Do you get the ci configmap using the templates option or did you see it using the resources option @sgandon ?
I get the following results, using helmfile v0.47.0. Using the templates option seems to overwrite the default with the ci configmap.
Use templates (:+1:):
releases:
- name: test-docker-watcher
  namespace: test
  chart: incubator/raw
  values:
  - templates:
    - |
      {{- readFile "docker-image-change-watcher.yaml" | nindent 6 }}

Fetching incubator/raw
---
# Source: raw/templates/resources.yaml

---apiVersion: v1
kind: Pod
metadata:
  labels:
    app: myapp
    chart: raw-0.2.0
    heritage: Tiller
    release: test-docker-watcher
  name: myapp-pod
spec:
  containers:
  - command:
    - sh
    - -c
    - echo Hello Kubernetes! && sleep 3600
    image: busybox
    name: myapp-container

Use resources (:-1:):
releases:
- name: test-docker-watcher
  namespace: test
  chart: incubator/raw
  values:
  - resources:
    -
      {{- readFile "docker-image-change-watcher.yaml" | nindent 6 }}

Fetching incubator/raw
---
# Source: raw/templates/resources.yaml

---apiVersion: v1
kind: Pod
metadata:
  labels:
    app: myapp
    chart: raw-0.2.0
    heritage: Tiller
    release: test-docker-watcher
  name: myapp-pod
spec:
  containers:
  - command:
    - sh
    - -c
    - echo Hello Kubernetes! && sleep 3600
    image: busybox
    name: myapp-container

---apiVersion: v1
kind: ConfigMap                            <<< what are you doing here ?
metadata:
  labels:
    app: raw
    chart: raw-0.2.0
    heritage: Tiller
    release: test-docker-watcher
  name: raw

Use resources, and explicitly disable templates (:+1: 1:):
releases:
- name: test-docker-watcher
  namespace: test
  chart: incubator/raw
  values:
  - resources:
    -
      {{- readFile "docker-image-change-watcher.yaml" | nindent 6 }}
  - templates: []

Fetching incubator/raw
---
# Source: raw/templates/resources.yaml

---apiVersion: v1
kind: Pod
metadata:
  labels:
    app: myapp
    chart: raw-0.2.0
    heritage: Tiller
    release: test-docker-watcher
  name: myapp-pod
spec:
  containers:
  - command:
    - sh
    - -c
    - echo Hello Kubernetes! && sleep 3600
    image: busybox
    name: myapp-container

@mumoshu Can we circumvent ci in some other way (https://github.com/helm/charts/blob/master/incubator/raw/values.yaml#L68) ? Everyone using the resources without the new templates gets the ci configmap I think.

indeed using the template is fine, I did try with resourcesand this is where I saw the ci-configmap.

https://github.com/helm/charts/pull/13633 should fix the ci-configmap issue.

I still think that this core ask is a good idea.  Consider for a moment a helm chart like Jenkins.  It might be desirable to store the CasC in a config map to limit the size of the values file:
https://github.com/helm/charts/blob/75a1020b6cce44cba3df11999b277e5c2c43db84/stable/jenkins/values.yaml#L603-L609
then to apply said config map when changing the chart:
repositories:
  - name: stable
    url: https://kubernetes-charts.storage.googleapis.com

releases:
  - name: '{{ requiredEnv "NAME" }}-{{ requiredEnv "PROJECT" }}-jenkins'
    namespace: '{{ requiredEnv "NAME" }}-{{ requiredEnv "PROJECT" }}'
    labels:
      app: '{{ requiredEnv "NAME" }}-{{ requiredEnv "PROJECT" }}-jenkins-master'
    chart: stable/jenkins
    version: ~1.27.0
    hooks:
    - events: ["prepare"]
      command: "kubectl"
      args: ["apply","-f", '{{ requiredEnv "NAME" }}/{{ requiredEnv "PROJECT" }}/casc-config-map.yaml', "-n", '{{ requiredEnv "NAME" }}-{{ requiredEnv "PROJECT" }}']

    values:
    - values.yaml.gotmpl
    wait: true
    # time in seconds to wait for any individual Kubernetes operation (like Jobs for hooks, and waits on pod/pvc/svc/deployment readiness) (default 300)
    timeout: 3600
    # performs pods restart for the resource if applicable
    recreatePods: true
    force: true

Where the values file will look something like this:
persistence:
  enabled: true
  storageClass:
  annotations: {}
  accessMode: "ReadWriteOnce"
  size: "200Gi"
  volumes:
    - name: casc-config
      configMap:
        name: jenkins-casc-config
  mounts:
    - name: casc-config
      mountPath: /var/jenkins_home/casc_configs
      readOnly: true

While this solution works it's not as clean as it could be, and it's impossible to review diffs in the CasC which can lead to problems if some Junior Dev or Old School admin is trying to do some ClickOps.
Maybe there's a way to copy a template to the chart directory using a hook.  If so please lemme know and that would solve my issue with the diffs, and I think it would solve the core of this issue.  Again not sure if that last part is possible.

I did it like this:
releases:
  - name: alertmanager-basic-auth
    chart: incubator/raw
    values:
    - templates:
      - |
        apiVersion: v1
        kind: Secret
        type: Opaque
        metadata:
          name: basic-auth
          namespace: monitoring
        stringData:
          auth: {{ `"{{ .Values.auth }}"` }}
    secrets:
      - secrets/alertmanager-basic-auth.yaml

the secret is looking like this:
auth: blablablablablablabla

incubator/raw is now deprecated : https://github.com/helm/charts/tree/master/incubator/raw

Hey everyone! I was recently playing around with the idea of "a helmfile-builtin raw-chart-like feature" https://github.com/roboll/helmfile/commit/25baebe2b18cc059389b4bb1fcd334383466f0e2. It turn any local directory containing "*.yaml.gotmpl" into a temporary helm chart by rendering each template with Helmfile's template context/funcs/data. Would it help?

I would really like that feature in order to be able to add k8s hooks as resources to the charts (instead of using the helmfile hooks directly)..
This would be a really powerful feature IMO 👍

Any chance this can be considered again, since incubator/raw is now deprecated?
It seems like this request was pretty much turned down due to that workaround, while being limiting in terms of integrating with the chart.

SO many charts don't include netpols, yet almost every production deployment we have requires one. The ability to add additional templates at release would be extremely helpful.


Fixes false positives for M0-1-3.

Description
This PR fixes issue 349
Constexpr variables which are used in template instantiations are not considered "used".
Example

template <int t>
class CharBuffer
{
  public:
  int member[t];
  CharBuffer():member{0}{}
};

int foo()
{
  constexpr int line_length = 1024U;
  CharBuffer<line_length> buffer{}; // line_length is used here but reported as a violation for M0-1-3
  return buffer.member[0];
}

The fix is to conservatively check that if a template instantiation or a static assert has a constant which is equal to a local variable marked as a constexpr, then the said variable is considered as used.
Change request type

[ ] Release or process automation (GitHub workflows, internal scripts)
[ ] Internal documentation
[ ] External documentation
[x] Query files (.ql, .qll, .qls or unit tests)
[ ] External scripts (analysis report or other code shipped as part of a release)

Rules with added or modified queries

[ ] No rules added
[ ] Queries have been added for the following rules:

rule number here

[x] Queries have been modified for the following rules:

M0-1-3

Release change checklist
A change note (development_handbook.md#change-notes) is required for any pull request which modifies:

The structure or layout of the release artifacts.
The evaluation performance (memory, execution time) of an existing query.
The results of an existing query in any circumstance.

If you are only adding new rule queries, a change note is not required.
Author: Is a change note required?

[x] Yes
[ ] No

🚨🚨🚨
Reviewer: Confirm that format of shared queries (not the .qll file, the
.ql file that imports it) is valid by running them within VS Code.

[ ] Confirmed

Reviewer: Confirm that either a change note is not required or the change note is required and has been added.

[ ] Confirmed

Query development review checklist
For PRs that add new queries or modify existing queries, the following checklist should be completed by both the author and reviewer:
Author

[x] Have all the relevant rule package description files been checked in?
[x] Have you verified that the metadata properties of each new query is set appropriately?
[x] Do all the unit tests contain both "COMPLIANT" and "NON_COMPLIANT" cases?
[x] Are the alert messages properly formatted and consistent with the style guide?
[x] Have you run the queries on OpenPilot and verified that the performance and results are acceptable?As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.
[x] Does the query have an appropriate level of in-query comments/documentation?
[x] Have you considered/identified possible edge cases?
[x] Does the query not reinvent features in the standard library?
[x] Can the query be simplified further (not golfed!)

Reviewer

[ ] Have all the relevant rule package description files been checked in?
[ ] Have you verified that the metadata properties of each new query is set appropriately?
[ ] Do all the unit tests contain both "COMPLIANT" and "NON_COMPLIANT" cases?
[ ] Are the alert messages properly formatted and consistent with the style guide?
[ ] Have you run the queries on OpenPilot and verified that the performance and results are acceptable?As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.
[ ] Does the query have an appropriate level of in-query comments/documentation?
[ ] Have you considered/identified possible edge cases?
[ ] Does the query not reinvent features in the standard library?
[ ] Can the query be simplified further (not golfed!)

@rak3-sh this also requires clang-format.

Applied clang-format in 7804c408d9302d4950aeb4ed95826389eb38da83


Add Docker config validation

Remove fallback logic to nanos on violation of CFS bandwidth configuration.  Fail fast instead.  This change also moves code for configuration out of the large docker.go file.

Pull Request Test Coverage Report for Build 2212

76 of 93 (81.72%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.06%) to 22.897%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

executor/runtime/docker/docker.go
0
3
0.0%

executor/runtime/docker/config.go
76
90
84.44%

Totals

Change from base Build 2197:
0.06%

Covered Lines:
2458

Relevant Lines:
10735

💛  - Coveralls


[5/x] Add veNft setup modal in project tools

What does this PR do and why?
Adds a button in the project tools drawer for owners of a project to open the venft setup modal
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] I have tested this PR in all supported browsers.
[ ] I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #1586

PR #1587

PR #1588

PR #1594

PR #1595   👈

This comment was auto-generated by Graphite.

Graphite Merge Job
Current status: ⏳ Queued to merge
This pull request is currently queued to be merged as part of a stack.
This comment was auto-generated by Graphite.

Job Reference: 5peKCVtRG7hIeC6BSrBI

Graphite Merge Job
Current status: ⏳ Queued to merge
This pull request is currently queued to be merged as part of a stack.
This comment was auto-generated by Graphite.

Job Reference: 0agyc4HkFZeecGjH4TTU

Graphite Merge Job
Current status: ⏳ Queued to merge
This pull request is currently queued to be merged as part of a stack.
This comment was auto-generated by Graphite.

Job Reference: I3QazDznUYZOKiV2bxLz


test(webhook): add test for Cryostat defaulter webhook

Welcome to Cryostat! 👋
Before contributing, make sure you have:

[ ] Read the contributing guidelines
[ ] Linked a relevant issue which this PR resolves
[ ] Linked any other relevant issues, PR's, or documentation, if any
[ ] Resolved all conflicts, if any
[ ] Rebased your branch PR on top of the latest upstream main branch
[ ] Attached at least one of the following labels to the PR: [chore, ci, docs, feat, fix, test]
[ ] Signed all commits: git commit -S -m "YOUR_COMMIT_MESSAGE"

Fixes: #
Description of the change:

Adds tests for the Cryostat defaulting webhook
Reduces visibility of some types if not required to be public

Motivation for the change:

Increases test coverage

How to manually test:

make test-envtest

/build_test


Update file path of QGC sample plan in the example

Update path of sample plan: plugins/mission/qgroundcontrol_sample.plan.
Fixes #272

Thanks @shakthi-prashanth-m !


dev secret inject

This add one variables to the project:
DEV_PULL_SECRET to be set to private registry token for HCP layer to pull images.

@jim-minter post review changes done


[WFLY-6936] RebindTestCase fails with security manager

Issue: https://issues.jboss.org/browse/WFLY-6936

This PR depends on https://github.com/wildfly-security/wildfly-elytron/pull/598 and https://github.com/wildfly/wildfly-core/pull/2010.


Demo window final updates

Wrap up feedback from team and adopters

Working with Wonil & James to finalize direction on demo window. Overall, the proposal is to customize our storybook to cut down on the dev work to build a whole new demo window.
Here are sketch files for the demo window: https://ibm.box.com/s/sdx55r4md8lv2hd3sgterrvz0souo6b2
Next steps coming soon.


Main rule functions automatically gets OrdinalElection

@rule decorator implicitly convert lists into OrdinalElection

 Main voting functions gets OrdinalElection automatically


Bug concerning Birds Nests, Lootbags and Dungeon Tactics when looking into EZ Storage 2 inventory system

Whenever I move items around in my inventory (mostly Bird's nests and Lootbags) The lootbags no longer open, the birds nests don't drop anything and the dungeon tactics loot bags don't drop any items. When I go into the ez storage 2 inventory system, where you create items, that is where I have to put them, then take them out of there. They will then drop their loot, as soon as I right-click them. I'll make sure to post the FML Log since no crash occurs. The other mod authors shall know of this issue and maybe one of them could fix it or at least keep abreast of the issue.
Minecraft: 1.10.2
Forge: <IP_ADDRESS>0
EZ Storage 2: 2.2.5
Dungeon Tactics: 0.10.4
LootBags: 2.1.3
BirdsNests: 1.4
FML Log: https://www.pastefs.com/pid/6969

Just incase.


Add GHA check for formal spec SRP validity

Description
Resolves #4549

Checklist

[x] Commit sequence broadly makes sense and commits have useful messages
[ ] New tests are added if needed and existing tests are updated
[ ] All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages.
New section is never added with the code changes. (See RELEASING.md)
[ ] When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
versioning process.
[ ] The version bounds in .cabal files for all affected packages are updated.
If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
[x] Code is formatted with fourmolu (use scripts/fourmolize.sh)
[x] Cabal files are formatted (use scripts/cabal-format.sh)
[x] hie.yaml has been updated (use scripts/gen-hie.sh)
[x] Self-reviewed the diff

It's great to have this in our CI now


Release?

https://github.com/auraphp/Aura.View/compare/2.2.1...2.x
@harikt added a useful way to pass layout/view maps/paths to the newInstance method in  07548bf2f51e07f08347b1c8dd9d7c0b77ba3089 some time ago, but I dont believe theres a release yet.

Hi @jakejohns ,
Thank you for reminding me.
I have made a 2.3.0 release for Aura.View https://github.com/auraphp/Aura.View/releases/tag/2.3.0 .


Problem with compile status

To reproduce
main
  var a set to "x"
  set a to 3
end main

When entering the set  statement, as soon as you type the value 3 a (red) compile error message correctly appears next to the field: cannot assign number to string.
At this point the field is still green because the field status is not aware of the compile error - any content in the  tags is automatically shown. The set statement also has a valid status.
So soon as you click/tab off the field:

The message disappears. This is not surprising  because the field no longer has focus. But in fact...
The message is no longer there, so if you click back on the field, the message does not reappear.
The field remains valid
The set frame is now invalid - but this is not visible anywhere
The file as a whole is now invalid (aggregated up from the set frame)
Changing the 3 to e.g. "y" does not clear the error on the set statement, nor hence on the file.

Analysis
The following are possible contributory factors:

the updateDisplay method in web-scripts.ts is assuming that the CompileError locationId is referring to Field, when it is quite possibly a Frame (must be for the set frame to change its status when it does (above).
AbstractField (unlike AbstractFrame) is deriving its CodeStatus from the parse status, rather than also the compile errors. However, changing this did not solve the problem.
AbstractField has no  tag in which to put (and hence display) a compile error at statement level.

Unresolved:

Why is the error message going (correctly) into the field, but the compile error going onto the frame
Why is one happening before the other

TODO

Separate ParseStatus from CompileStatus all the way up - though still combining them where necessary for display purposes - so that compiler can always activate if ParseStatus is valid.

Temporarily display both statuses in some minimally-breaking way e.g.border.

Second minimal example
(Advantage: has only one field)
main
  if 3
  end if
end main

As soon as you enter 3 error message appears expression must be boolean' - but the error is not shown in the Header, nor if the iformain` are collapsed.
TODO

Get rid of the message being provided externally
The compile method should update a compile status on each field and frame (note that frame compiles ultimately delegate to fields) and, if necessary, should update the `error' field, for inclusion in the Html
compile status should be aggregated up - but is there any need to aggregate up the CompileErrors?
restore ParseStatus, and keep compile status separate all the way up
combine the two statuses only for display purposes on the collapsed frame view
Note that, currently, the compile rule that the condition expression must be boolean, passes in the compileErrors[] of the if frame rather than of the condition field which it could be in this case. However, there are other situations (e.g. class not implementing abstract members, or set of arguments not matching those of the method being called) where the error cannot be associated with a single field. Would it be better to go the other way, and associate, and/or display, all compile methods on a frame? This could also be made visually distinct - either as a message alongside the frame, but separated from last field by a gap, or a change in colour to the frame, or block alongside the frame, with a tooltip.

Fixed with check-in c795c7a


Add Cloud Monitoring support

https://developer.rackspace.com/docs/cloud-monitoring/v1/developer-guide

Overall this looks great. Just a few suggestions above (one is a bulk change).


create a helper div whenever the element is floating

get the width and height of the element that is being fixed, and create a div with those dimensions and put in the position the element were previously, so the elements don't start "dancing"

This can be accomplished by copying the computedStyle of the pinned element into a variable
create a div, and copy some structure css properties:
width
height
position
float
display
by copying those the element can get the same structure of the pinned element, and prevent other elements from "dancing" around whenever the element gets pinned.

YEAHHHHH
https://github.com/mauriciosoares/pin.js/commit/e38f5184bae7827d17702af0e199ddc122da73eb
the new example is so damn awesome!


Azure Datacenter IP address list is deprecated

Hi MSFT,
Can you possibly update the links to the "Azure Datacenter IP address list" as it is pointing to a deprecated list now.
Thanks in advance.
Kr,
Bart van Berkel

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

ID: 3092ee3a-3c57-cc53-186b-b454e7d9d190
Version Independent ID: 6f6b5a07-397a-98a2-6091-941244a77837
Content: Azure Automation Hybrid Runbook Worker
Content Source: articles/automation/automation-hybrid-runbook-worker.md
Service: automation
Sub-service: process-automation
GitHub Login: @bobbytreed
Microsoft Alias: robreed

AFAIK this might be the latest one (i.e., referenced in this blog).
@bobbytreed Can you validate and confirm so that we can update the document with the new links ?

Assigning @bobbytreed for visibility and document enhancement considerations.

Added updated doc #please-close


Platform Maturity Model: Introduction

This is to track the progress on this specific details section.
Please see https://docs.google.com/document/d/11J_RpaUwydNNBg5aVjH5Uzn8i-b4urEtJzwR86XezFQ/edit#bookmark=id.6o3jkwbxp75m for more detail.
Everyone is enabled and encouraged to be a reviewed through Google Doc comments. To become a contributor directly please reach out to "Abby Bangser" or "Josh Gavant" on CNCF slack or via the Google Document comments.
This is a blocker to https://github.com/cncf/tag-app-delivery/issues/381

I am going to close this as the iterative work in Google Docs has been complete. For final review see https://github.com/cncf/tag-app-delivery/pull/464 and #381.
Thank you to everyone who contributed in the WG calls and in the Google Doc 🙇


Job Quests not displaying individual task progress

When you hover over a jobs quest, the individual tasks listed don’t keep progress, only the overall progress is kept.
so for example, my job Bomb Squad requires players to craft 64 tnt, and blow up 1000 stone. The overal progress bar works, it says ##/1064
But the hover event shows
TNTBreak stone 0/1000
Craft TNT 0/64
I’m on latest paper spigot 1.17.1 and latest version of jobs 5.0

I'm getting this, too.


Refactor Block Integrity Checks to Support Block Headers

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

feature/proof-of-stake

PR #875

PR #891   👈

This stack of pull requests is managed by Graphite.


feat: add performCount to derived state

Closes #87
This also kinda setup the testing for the derived state (which i think we should test separately for each field and following this pattern of adding the expected values in the each)...let me know what you think about it.

Is exporting the tasks from the tests/components/... folder setting it up for something else? If not we probably don't need the exports.

Those exports are imported in the test after the render so that we can check what's inside the store.

Out of curiosity, do you usually prefer to use an object perform_count : {expected} over a string/number expected_perform_count?

I just did that because for other derived state we might need more values so it's not everything inside the single object but we can organize the values in terms of the derived state they refer to. But we can change that.

Is exporting the tasks from the tests/components/... folder setting it up for something else? If not we probably don't need the exports.

Those exports are imported in the test after the render so that we can check what's inside the store.

Ah yeah, so they are


Fixed Number of Products in a WishList (if product is disabled or removed)

Questions
Answers

Description?
Fixed Number of Products in a WishList (if product is disabled or removed)

Type?
bug fix

BC breaks?
no

Deprecations?
no

Fixed ticket?
Fixes PrestaShop/PrestaShop#27488

How to test?
Cf. PrestaShop/PrestaShop#27488

@florine2623 Have you build assets ?

Hello @Progi1984 , Thanks for the PR !
After installing the PR, I can't add any product to my wishlist.
Screen.Recording.2022-03-10.at.12.29.44.mov
Could you check ? Thanks!

@florine2623 You probably need to reset the module, or test with the develop branch, this problem looks related to the core but not the module

Thanks @florine2623