Add JSON Support to V2 Engine (#217)

Description
Phase 1 of adding JSON Support to V2 Engine
For example: The following request was handled by V2 engine:
curl --location 'http://localhost:9200/_plugins/_sql?format=json' --header 'Content-Type: application/json' --data '{
    "query": "SELECT * FROM calcs LIMIT 1;"
}'
{
    "took": 13,
    "timed_out": false,
    "_shards": {
        "total": 1,
        "successful": 1,
        "skipped": 0,
        "failed": 0
    },
    "hits": {
        "total": {
            "value": 17,
            "relation": "eq"
        },
        "max_score": 1.0,
        "hits": [
            {
                "_index": "calcs",
                "_id": "1",
                "_score": 1.0,
                "_source": {
                    "int0": 1,
                    "bool3": true,
                    "time1": "19:36:22",
                    "bool2": false,
                    "int2": 5,
                    "int1": -3,
                    "str3": "e",
                    "int3": 8,
                    "str1": "CLAMP ON LAMPS",
                    "str2": "one",
                    "time0": "1899-12-30T21:07:32Z",
                    "num1": 8.42,
                    "datetime0": "2004-07-09T10:17:35Z",
                    "num0": 12.3,
                    "datetime1": null,
                    "num4": null,
                    "key": "key00",
                    "num3": -11.52,
                    "bool1": true,
                    "num2": 17.86,
                    "bool0": true,
                    "str0": "FURNITURE",
                    "date3": "1986-03-20",
                    "date2": "1977-04-20",
                    "date1": "2004-04-01",
                    "date0": "2004-04-15",
                    "zzz": "a"
                }
            }
        ]
    }
}

Returning the raw response from OpenSearch made IT tests fail due to missing in-memory operations, difference in aggregation type (V2 is composite_bucket), and some bugs were discovered. The solution for these failing IT tests were to fall back to legacy for all functions, expect failures for IT tests with a comment for issues related.
List of expected failures in legacy IT:

DateFormatIT.and (1436)

DateFormatIT.equalTo (1436)

DateFormatIT.greaterThan (1436)

DateFormatIT.greaterThanOrEqualTo (1436)

DateFormatIT.lessThan (1436)

DateFormatIT.lessThanOrEqualTo (1436)

DateFormatIT.or (1436)

DateFormatIT.sortByDateFormat (1436)

QueryFunctionsIT.wildcardQuery (Dependent on PR #1314)

QueryIT.selectAllWithFieldAndOrderBy (785)

QueryIT.selectAllWithFieldReturnsAll (785)

QueryIT.selectAllWithFieldReverseOrder (785)

QueryIT.selectAllWithMultipleFields (785)

QueryIT.notLikeTests (1425)

Proposal for phase 2 of JSON support for V2
https://github.com/opensearch-project/sql/issues/1450
Issues Resolved
https://github.com/opensearch-project/sql/issues/1317
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

This PR is a first phase of JSON support implementation. Second phase assumes support of JSON response format for all datasources and queries. We have a PoC on test-json-pagination branch, it keep no raw response from OpenSearch/Prometheus/whatever, but it generates a response which looks 1:1 like returned by OpenSearch with resultset of the SQL plugin.
See example:
$ curl -s -XPOST http://localhost:9200/_plugins/_sql?format=json -H 'Content-Type: application/json' -d '{"query": "SELECT int0 + 1, 2, now() FROM calcs limit 2"}' | jq
{
  "took": 0,
  "timed_out": false,
  "_shards": {
    "total": 1,
    "successful": 1,
    "skipped": 0,
    "failed": 0
  },
  "hits": {
    "total": {
      "value": 2,
      "relation": "eq"
    },
    "max_score": 1,
    "hits": [
      {
        "_index": null,
        "_id": null,
        "_score": 0,
        "fields": {
          "2": 2,
          "int0 + 1": 2,
          "now()": "2023-03-17 13:07:47"
        }
      },
      {
        "_index": null,
        "_id": null,
        "_score": 0,
        "fields": {
          "2": 2,
          "int0 + 1": null,
          "now()": "2023-03-17 13:07:47"
        }
      }
    ]
  }
}

It is not completed yet (_id, _index fields are empty - depends on #1456, took is always 0), but it works fine. For another datasource, if fills meta info (e.g. _shards) with default values.
Once we will complete the fix and resolve all dependencies, we will publish Phase 2 implementation of JSON response format.

This PR is a first phase of JSON support implementation. Second phase assumes support of JSON response format for all datasources and queries. We have a PoC on test-json-pagination branch, it keep no raw response from OpenSearch/Prometheus/whatever, but it generates a response which looks 1:1 like returned by OpenSearch with resultset of the SQL plugin. See example:
$ curl -s -XPOST http://localhost:9200/_plugins/_sql?format=json -H 'Content-Type: application/json' -d '{"query": "SELECT int0 + 1, 2, now() FROM calcs limit 2"}' | jq
{
  "took": 0,
  "timed_out": false,
  "_shards": {
    "total": 1,
    "successful": 1,
    "skipped": 0,
    "failed": 0
  },
  "hits": {
    "total": {
      "value": 2,
      "relation": "eq"
    },
    "max_score": 1,
    "hits": [
      {
        "_index": null,
        "_id": null,
        "_score": 0,
        "fields": {
          "2": 2,
          "int0 + 1": 2,
          "now()": "2023-03-17 13:07:47"
        }
      },
      {
        "_index": null,
        "_id": null,
        "_score": 0,
        "fields": {
          "2": 2,
          "int0 + 1": null,
          "now()": "2023-03-17 13:07:47"
        }
      }
    ]
  }
}

It is not completed yet (_id, _index fields are empty - depends on #1456, took is always 0), but it works fine. For another datasource, if fills meta info (e.g. _shards) with default values. Once we will complete the fix and resolve all dependencies, we will publish Phase 2 implementation of JSON response format.
UPD Phase 2 is tracked in #1450

I believe that what we are targeting here is specific to the OpenSearch raw data response. Do other data sources have similar requirements?

I believe that what we are targeting here is specific to the OpenSearch raw data response. Do other data sources have similar requirements?

Not yet, but you're welcome to define them in #1450. It is possible to generate OpenSearch-like JSON using result set from Prometheus. Or create OpenSearch response for OpenSearch queries and Prometheus-like for Prometheus.

I believe that what we are targeting here is specific to the OpenSearch raw data response. Do other data sources have similar requirements?

Not yet, but you're welcome to define them in #1450. It is possible to generate OpenSearch-like JSON using result set from Prometheus. Or create OpenSearch response for OpenSearch queries and Prometheus-like for Prometheus.

IMO, if we touch core logic as what we're doing in this PR, we should clearly define what's the meaning of JSON format for all data sources. Otherwise, we may want to minimize such special logic that only work for OpenSearch.
@acarbonetto @Yury-Fridlyand
I expressed the similar concern in meta field PR: https://github.com/opensearch-project/sql/pull/1456#discussion_r1151006697. We've put lots of efforts to separate modules and abstraction since the beginning of V2 engine. It's true that OpenSearch is the primary storage and we're prioritizing legacy engine deprecate. However, if we keep adding special OpenSearch logic to core, I'm afraid V2 engine would be hard to maintain as legacy in future and all our previous efforts would be in vain.


Make rules search Check case sensitive to fix issue with ^i@ -> I false triggering

The new rules seach code does a case insensitive verification that the candidate rule's completion matches the buffer. This is not usable with rules like ^i@ -> I.
This tiny PR removes the tolower in the comparison, so i and I no longer match.

tolower was used so that this rule could be found: Missed rule: ^i* ⇒ I'm
But I agree that this is actually incorrect.
Removing it has the tester failing to find ␣i✪ ⇒ I though. I will investigate.


OSX/Linux Support

The current implementation as shown relies on cmd.exe which is not supported by any other operating system other than windows.

This may be a possible solution current have a fork so may try and PR this need check for any other references to windows only: https://stackoverflow.com/questions/23679283/c-sharp-execute-a-terminal-command-in-linux/23681651#23681651

Seem to be more Windows only references as here:

This is something we'd like to do but haven't got to yet. The weird behaviour around PATH was unexpected. We'd need to look into what happens on both Mac and Linux to see whether a similar problem exists there, or whether on those platforms we can just execute npm directly.
As for the KillProcessAndChildren, IIRC the problem here is that when you run the functions emulator, you get two processes: the NodeJS one, and then a separate one for the .NET code, and on Windows, killing the parent process doesn't automatically kill the children. I'm not sure whether we'll have the same problem on Mac or Linux, but if we did, we'd need something equivalent to find the process hierarchy and clean up the whole thing.

Based on a very quick experiment, this appears to work for launching npm in Linux:
var pi = new ProcessStartInfo("npm", "prefix -g");
var p = new Process { StartInfo = pi };
p.Start();

so on the face of it, it looks like the PATH issues we encountered on Windows are not an issue. (It's also possible, I suppose, that they're no longer a problem in Windows either—we haven't changed this for a while.)

This isn't only need for local dev but also for CI/CD pipelines. I want to deploy my functions to a Linux plan and want to run my tests in Azure Pipelines on a Linux agent. I just spent a day trying to figure out why my tests wouldn't run and then I came across this issue. I didn't see anywhere in the documentation saying this was a Windows only library. Since it is built on netstandard2.0 I just assumed it would run on Linux.

Since it is built on netstandard2.0 I just assumed it would run on Linux.

In general this is no guarantee. The System.Management NuGet package (which the Corvus.Testing.AzureFunctions package has a dependency on) supports netstandard2.0, but doesn't work on Linux. So one reason our netstandard2.0 library doesn't work on Linux is that it depends on a Microsoft-supplied netstandard2.0 library that also doesn't work on Linux.
The only thing netstandard2.0 really tells you is that a component can be loaded on both .NET FX and .NET Core. The extent to which it actually works across operating systems is determined by what the component actually does, and there are numerous examples in netstandard2.0 of APIs that appear to be available everywhere but which fail at runtime on some OSs.
And if you look at what System.Management actually does, it isn't entirely surprising it only works on Windows. There have been feature requests to make it "work" e.g. https://github.com/dotnet/runtime/issues/23918 but even then, there's more than one interpretation of "work". E.g., some people only want the ability to send a WMI query from a Linux machine to a Windows machine, and to be able to interpret the response on the Linux machine. But some people want to be able to run WMI queries against the local host.
That raises the question of what you'd actually expect a Linux box to do when asked to return a list of Win32_Process objects.
So I'd expect the only way for us to fix this is to find some way to achieve the same effect without using System.Management.
As I said earlier in the thread, we do want to fix this—we have several build pipelines currently using Windows where we'd prefer to use Linux (because if you're using single-use discardable build agents, Linux ones generally take less time to provision), but where we're stuck on Windows partly because of this limitation in this library. (Although there's also the fact that we've encountered a lot of problems deploying to Linux-based Azure Functions, meaning that in most cases we use Windows for the production deployments, at which point you tend to want to run your tests on Windows.)
So we do intend to fix this. It just hasn't reached the top of our priority list yet.

PRs from people well versed in the Linux side of this would be very welcome, though.

Since I'd already taken a look at the issues to be able to write a vaguely cogent reply, I thought I'd see if it's relatively straightforward. There's a draft PR, #271 which attempts to address the issues I know about. If you're feeling adventurous, I've produced a pre-release NuGet package https://www.nuget.org/packages/Corvus.Testing.AzureFunctions/1.5.0-253-unix-support.2 that you could try out to see if it works, but be aware that I've not tested it at all yet.

I have tried this out and there is an issue with how you are checking for the azure functions core tools. Using npm prefix -g on linux reports the path to be /opt/hostedtoolcache/node/10.24.1/x64 but the core tools are installed in /opt/hostedtoolcache/node/10.24.1/x64/lib so the check for the core tools being installed is failing.
To fix this you should use npm root -g. This will return the path including the node_modules folder so in your GetToolPath method you would need to change
    string toolsFolder = Path.Combine(
                npmPrefix,
                @"node_modules\azure-functions-core-tools\bin");

to
    string toolsFolder = Path.Combine(
                npmPrefix,
                @"azure-functions-core-tools\bin");

I unfortunately do not currently have a Linux environment set up so I could only test this on Azure Pipelines with both a Windows and Linux agent and printing out the results of the npm root -g command. They both reported the node_modules folder correctly. I am in the process of setting up WSL with VS Code for local Linux dev. It is really interesting (and a little sad) to see how much faster Linux is not only on Azure Pipelines but in running dotnet code.

I have gotten a local Linux environment set up to test this and I can confirm that the changes I outlined above do fix the npm issue with one small change - the path to the 'azure-functions-core-tools\bin' needs to use the OS specific directory separator. (@$"azure-functions-core-tools{Path.DirectorySeparatorChar}bin"). That is the good news. The bad news is that it is throwing an exception (System.ComponentModel.Win32Exception : No such file or directory) when it tries to start the process to run 'npm root -g'. From my search online this is supposed to work so not sure why it isn't. I will take another look at this on the weekend.


Potential bug: Authentication failure when downloading ERA5 data on HPC and Google Colab

Description
I encountered an issue while using the get_era5_reanalysis_data function to download ERA5 sample data. The function works fine on my local MacBook, but it fails with authentication errors both on my university's HPC and on Google Colab. The error logs suggest a failure to communicate with the Google Compute Engine Metadata server. Although this might point to networking issues specific to the HPC environment, the failure on Google Colab suggests a broader problem. Ideally, this function would work in any environment, so I conducted some tests and documented the results below.
Warnings and Download Failure on U-M HPC (Batch Job)
When run on U-M HPC as a batch job, the function hangs indefinitely and never starts the download. Here are the captured warnings:
2024-12-23 23:26:47,837 - INFO - Cache directory created at ./cache
2024-12-23 23:26:47,837 - INFO - Starting data download for variables: ['2m_temperature', '10m_u_component_of_wind', '10m_v_component_of_wind']
2024-12-23 23:26:51,776 - WARNING - Compute Engine Metadata server unavailable on attempt 1 of 3. Reason: timed out
2024-12-23 23:26:51,856 - WARNING - Compute Engine Metadata server unavailable on attempt 2 of 3. Reason: [Errno 113] No route to host
2024-12-23 23:26:54,859 - WARNING - Compute Engine Metadata server unavailable on attempt 3 of 3. Reason: timed out
2024-12-23 23:26:54,859 - WARNING - Authentication failed using Compute Engine authentication due to unavailable metadata server.

Warnings and Download Failure on U-M HPC (Jupyter Notebook)
In contrast to the batch job, the function crashes when run in a Jupyter Notebook. The full warning and error list is very long, but here is a key message:
Message: 'Authentication failed using [Google] Compute Engine authentication due to unavailable metadata server.'

Error and download failure when run on Google Colab
To determine if this issue was U-M-specific, I tested the function on Google Colab. The errors there were similar. The key excerpt is:
google.auth.exceptions.RefreshError: ("Failed to retrieve http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/?recursive=true from the Google Compute Engine metadata service. Status: 404 Response:\nb''", <google.auth.transport.requests._Response object at 0x7b5318b245b0>)
ERROR:root:Error during data download: ("Failed to retrieve http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/?recursive=true from the Google Compute Engine metadata service. Status: 404 Response:\nb''", <google.auth.transport.requests._Response object at 0x7b5318b245b0>)
Error during data download: ("Failed to retrieve http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/?recursive=true from the Google Compute Engine metadata service. Status: 404 Response:\nb''", <google.auth.transport.requests._Response object at 0x7b5318b245b0>)

Here is a link to the public Google Colab notebook showing the complete function call and the output
Additional Notes
This issue appears to stem from how the function interacts with the Google Compute Engine Metadata server. While the HPC environment might involve network restrictions, the occurrence of similar issues on Colab suggests this could be a broader problem related to authentication mechanisms.
As I mentioned above, I've encountered similar issues when trying to access publicly accessible data hosted on Google Cloud Platform. In all the cases I've encountered, a download function attempts to use Compute Engine authentication, which depends on the availability of a metadata server. However, this server is specific to Google Cloud virtual machines and is not available in other environments like HPC or Google Colab unless explicitly configured.
I'm guessing that in environments like HPC or Colab, the fallback authentication methods might not be set up or accessible due to different system configurations, firewalls, or network restrictions. This even seems to apply when no authentication is required, e.g. when using a publicly accessible bucket.
Reproduction steps
1. Set up an environment on HPC or Google Colab with DeepSensor installed.
2. Attempt to download ERA5 data using `get_era5_reanalysis_data`.
3. Observe warnings and errors as described above.

Version
0.4.2
Screenshots
![DESCRIPTION](LINK.png)

OS
Linux

Thanks @DaniJonesOcean much appreciated - I'll look into this in the new year.


Can't use node-option with ts-node

Prerequisites

[X] Checked that your issue hasn't already been filed by cross-referencing issues with the faq label
[X] Checked next-gen ES issues and syntax problems by using the same environment and/or transpiler configuration without Mocha to ensure it isn't just a feature that actually isn't supported in the environment in question or a bug in your code.
[X] 'Smoke tested' the code to be tested by running it outside the real test suite to get a better sense of whether the problem is in the code under test, your usage of Mocha, or Mocha itself
[X] Ensured that there is no discrepancy between the locally and globally installed versions of Mocha. You can find them with: node_modules/.bin/mocha --version(Local) and mocha --version(Global). We recommend that you not install Mocha globally.

Description
when running mocha with both ts-node and node-option parameters, ts-node file extensions (.ts) are no longer supported
Steps to Reproduce

Create a project with type module, install mocha, typescript, ts-node and ts-loader
typescript file test.spec.ts
run node node_modules/mocha/bin/mocha.js --no-warnings --loader=ts-node/esm --require ts-node/register --ui bdd --node-option experimental-wasm-gc src/test.spec.ts

Expected behavior:
I expect the test to run
Actual behavior:
When running the above, I get a TypeError: Unknown file extension ".ts"
If I remove --node-option experimental-wasm-gc I don't get the error
If I run node --experimental-wasm-gc node_modules/mocha/bin/mocha.js --no-warnings --loader=ts-node/esm --require ts-node/register --ui bdd  src/test.spec.ts, then the test complains that the experimental-wasm-gc option is missing (I'm loading a WebAssembly)
Reproduces how often:
Always
Versions

The output of mocha --version:
10.1.0
The output of node_modules/.bin/mocha --version:
10.1.0
The output of node --version:
v21.3.0
Your operating system

name and version: MacOS Ventura Version 13.0 (22A380)
architecture (32 or 64-bit): 64

Your shell (e.g., bash, zsh, PowerShell, cmd): bash
Your browser and version (if running browser tests): n/a
Any third-party Mocha-related modules (and their versions):
ts-loader": "^9.4.1
"ts-node": "^10.9.1",
Any code transpiler (e.g., TypeScript, CoffeeScript, Babel) being used (and its version):
tsc Version 4.9.5

Additional Information

It seems the issue could be located in mocha.js lines 84-86, where the presence of node-option drops the already parsed node args (in nodeArgs variable) instead of combining them

Curiosity: why provide both --loader=ts-node/esm and --require=ts-node/register?
The list of steps provided seems reasonable, but I'm not getting the exact same output locally.  Could you please post an isolated reproduction that a maintainer can run with only 1-2 commands, such as a GitHub repository, GitHub Gist, or Stackbliz container?

you need ts-node/register to compile ts on the fly
you need ts-node/esm to use esm module syntax
Here is an example
MochaBug.zip

Got it, thanks! Makes sense. +1 to your (very helpful, thanks!) comment that Mocha is overriding the implicit-ish --loader=ts-node Node option with the explicit --node-option experimental-wasm-gc. If you pass in --node-option loader=ts-node/esm instead, then everything works happily.
$ node node_modules/mocha/bin/mocha.js --no-warnings --require ts-node/register --ui bdd --node-option loader=ts-node/esm --node-option experimental-wasm-gc src/test.spec.ts
(node:37672) ExperimentalWarning: `--experimental-loader` may be removed in the future; instead use `register()`:
--import 'data:text/javascript,import { register } from "node:module"; import { pathToFileURL } from "node:url"; register("ts-node/esm", pathToFileURL("./"));'
(Use `node --trace-warnings ...` to show where the warning was created)

Hi there!
  ✔ runs a test

  1 passing (1ms)

...where "happily" ignores the loader notice. That's discussed in #5002.
I think we can consider this a docs issue similar to #5002 that it's not clear how to use Node import/loader/require options together. Filed #5087 to track adding docs. It links to https://github.com/mochajs/mocha-examples/pull/76 as a start.
Aside: in general, it's not great practice to upload a .zip. Downloading and extracting arbitrary files from the internet is kind of scary for us maintainers 🫠. An isolated GitHub repository, Gist, Stackblitz, or other more transparent environment would be nice in the future. This zip works for now.
Thanks for filing!


How to use it?

I am not a stranger of modding bannerlord, but I assume all the lose files here are not compiled into dll? I have no clue how to use this mod in this format. A little hint how to or where to find info about how to would be incredible.

Link to Download This Mod

I already tried this version, still has issues.

I already tried this version, still has issues. Not playing the game as the little bugs all over the place are just too annoying.

find Modules in Game Folder, and Create Folder for MarryAnyone!!!


rafs: reduce log level to avoid annoying messages on console

Details
Reduce log level to avoid annoying messages on console such as: root@liujiang-ecs-dev:~/ws/nydus-snapshotter.git/cmd/containerd-nydus-grpc# nerdctl run --rm -ti --snapshotter nydus busybox
docker.io/library/busybox:latest:                                                 resolved       |++++++++++++++++++++++++++++++++++++++|
index-sha256:6e494387c901caf429c1bf77bd92fb82b33a68c0e19f6d1aa6a3ac8d27a7049d:    done           |++++++++++++++++++++++++++++++++++++++|
manifest-sha256:1b0a26bd07a3d17473d8d8468bea84015e27f87124b283b91d781bce13f61370: done           |++++++++++++++++++++++++++++++++++++++|
config-sha256:b539af69bc01c6c1c1eae5474a94b0abaab36b93c165c0cf30b7a0ab294135a3:   done           |++++++++++++++++++++++++++++++++++++++|
elapsed: 11.3s                                                                    total:  4.2 Ki (378.0 B/s)
[2023-06-27 17:51:14.443766 +08:00] INFO RAFS features: COMPRESSION_NONE | HASH_SHA256 | EXPLICIT_UID_GID | TARTFS_MODE
Types of changes
What types of changes does your PullRequest introduce? Put an x in all the boxes that apply:

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation Update (if none of the other choices apply)

Checklist
Go over all the following points, and put an x in all the boxes that apply.

[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.

I will solve the issue in another way, so close this one.


Fix 4:2:0 and 4:2:2 chroma plane sizes

Rounding errors were causing issues with odd frame sizes.
Here is a sample. I tested encoding + decoding with y4m and verified that the output appears correct with this patch.
If you could bump the patch version after merging that would be appreciated.

Thanks. Will update crates version a bit later.

Done.


add types to package.json

@e111077 Does this look right to you? We can do an rc2 to test it (now that I know how to not screw it up). Note that #3774 also added typings, which seems to be a bit like types?

Can we do an RC2 to be safe?

The "type": "module" change is breaking our karma testing, so we'll have to sort that out first, but yes, RC2 sounds good.

we can move type: module out of this PR and TODO that for later


Update how-to-create-an-xml-document-based-on-an-xsd-schema.md #5664

#5664

@caro-oviedo : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@caro-oviedo : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Verified the revisions; merging.

@ktoliver The change at line 19 of "how-to-edit-xml-files.md" is incorrect - normally, we would just say "Open" rather than reference the specific tapping or clicking action (you can also use the keyboard).  But in this case, since it seems to be telling people how to open a file, "double-click or double tap" is probably best.


Add warning before doing the deposit to wait for beacon node sync

To avoid potential penalties, we should recommend that people wait until their beacon node is fully in sync before doing the deposit at the deposit step.
We could also automatically test it and show a progress bar on that screen.

Completed with a progress_log_dialog and a waiting loop until the beacon node is fully in sync or the user wishes to proceed anyway.

Completed on Windows with fa9a8537f1bbf170c191043962579d6174a73879


Feature Request: Allow Note (and other REs) to select for all spells cast

I would like for a Note RE to apply whenever an actor casts a spell. For example, a staff of healing grants an item bonus to the Hit Points you restore anytime you cast the heal spell using your own spell slots or using charges. If a Note could apply on spells being cast, it could mention this bonus. However, currently it doesn't seem like there is a selector that would work for this, as spell attack roll and DC don't quite work for this use-case.
If this able to be supported, it would also be nice to be able to specify certain spellcasting entries. However, these are currently just named by freeform text entry and don't appear to have a slug.

This would also be useful for, e.g., the note about ancestors oracles needing to make a flat check to cast any spell while not on a spellcasting ancestor.


On Laravel 5.x applications when Environment variables are saved, they should also be saved the the .env file

On Laravel 5.x applications when Environment variables are saved, they should also be saved the the .env file as unlike Laravel 4.x the CLI cannot access the settings when used in Nginx ENV vars.

This has been implemented this evening and has been tested as working on Ubuntu 14.04 LTS, I see no reason why this shouldn't equally work on FreeBSD.


Mistake in gitignore pattern documentation?

I think that the rule in the documentation is not correct:

If the pattern does not contain a slash /, Git treats it as a shell
glob pattern and checks for a match against the pathname relative to
the location of the .gitignore file (relative to the toplevel of the
work tree if not from a .gitignore file).

I tested it and it seems that this is not true. Instead, it looks to me like this is true:

If the pattern does not contain a slash /, other than a trailing slash, Git treats it as a shell
glob pattern and checks for a match against the pathname relative to
the location of the .gitignore file (relative to the toplevel of the
work tree if not from a .gitignore file).

Example:
For this folder:
.
├── foo
│   └── bar
│       └── New Document
└── test
    └── foo
        └── bar
            └── New Document

and this .gitignore file
foo/bar

the folder /foo/bar is ignored and the folder /test/foo/bar not.
On the other side, if one changes .gitignore file to
bar

or
bar/

then bar is ignored everywhere and not only relative to the .gitignore file.

hey @iwasherefirst2
As you can see in the issue template, this repository issue tracker should only be used to report problems found on the git-scm website (https://git-scm.com/).
Git specific issues should be raised with the community (https://git-scm.com/community). The documentation you refer to is imported from git man pages

hi @pedrorijo91
I think this is a problem found on the git-scm website. The information on the page https://git-scm.com/docs/gitignore is not true and the paragraph should be changed there?

although it appears on the git-scm website, the content is imported from the git man pages, meaning that if there's a problem, it should be fixed on the git man pages, and git-scm will pick up the changes afterwards

Oh I see. I will write to the mailing list then. Thank you for that info.

no problem! thanks for reporting @iwasherefirst2 :)


Support calling attached functions from attached functions in BIR

Sample:
type MyObj0 object {
   function a (int i){}
};
type MyObj1 object {
   function b (int i){
        MyObj0 myObj = new;
        myObj.a(8);
   }
};
function f(){
}

@manuranga , the streams related unit tests are failing with travis

Codecov Report

Merging #14945 into master will increase coverage by 0.62%.
The diff coverage is 71.42%.

@@             Coverage Diff              @@
##             master   #14945      +/-   ##
============================================
+ Coverage     64.44%   65.07%   +0.62%
  Complexity      544      544
============================================
  Files          2288     2250      -38
  Lines        100683    99520    -1163
  Branches      13357    13165     -192
============================================
- Hits          64888    64758     -130
+ Misses        30717    29698    -1019
+ Partials       5078     5064      -14

Impacted Files
Coverage Δ
Complexity Δ

...java/org/ballerinalang/packerina/BuilderUtils.java
71.66% <0%> (+2.31%)
0 <0> (ø)
:arrow_down:

...java/org/ballerinalang/test/util/BCompileUtil.java
56.93% <100%> (ø)
26 <0> (ø)
:arrow_down:

...erinalang/compiler/bir/writer/BIRBinaryWriter.java
88.73% <80%> (+0.32%)
0 <0> (ø)
:arrow_down:

...a/org/ballerinalang/bre/bvm/WorkerDataChannel.java
82.71% <0%> (-1.86%)
0% <0%> (ø)

...a/org/ballerinalang/bre/bvm/GlobalMemoryBlock.java
79.41% <0%> (ø)
0% <0%> (ø)
:arrow_down:

tool-plugins/vscode/src/api-editor/index.ts

tool-plugins/vscode/src/utils/logger.ts

tool-plugins/vscode/src/test-runner/runner.ts

tool-plugins/vscode/src/debugger/index.ts

tool-plugins/vscode/src/debugger/manager.ts

... and 34 more

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 7261e8b...04994c5. Read the comment docs.

lets fix conflicts :)

Fixed the conflicts and sent a separate PR: #14995
Hence closing this one.


Bug/export generators 178493308

Problem
Follow up to #63 to move test-generators out of devDependencies
link to Pivotal Tracker #178493308
Solution
Moved @dsnp/test-generators out of devDependencies
with @shannonwells
Change summary:

Moved @dsnp/test-generators out of devDependencies
Setup a CI test for testing this sort of thing

beleza!


Pulling metrics from managed apps in TC

Toward https://github.com/giantswarm/giantswarm/issues/7259
We are checking giantswarm_io_monitoring labels in services to ensure it is supporting app from giantswarm.

Goal of this;

Creating service service discovery on prom config, which would search for services objects containing 'giantswarm.io/monitoringlabel astrue.  (@JosephSalisbury have a different idea that we should use endpoint` to match multiple pods, but I'm not sure about this)
If it's true, then we crawl metrics, just change __address__ as a suitable value.
At the moment "https://master.${1}:443/api/v1/namespaces/${2}/pods/${3}/proxy/metrics"
cc> @puja108

Tested on ghost

Albeit pulling is working, I checked all targets are invalid as below.

I think this is because we are using a different path for prometheus, as prometheus.io/path indicates as below.
k get -nfluent-logshipping-app-chart svc -o yaml
apiVersion: v1
items:
- apiVersion: v1
  kind: Service
  metadata:
    annotations:
      prometheus.io/path: /api/v1/metrics/prometheus
      prometheus.io/scrape: "true"

@JosephSalisbury Can I manipulate metrics_path append this annotation?


Add act under new section named Tools

Create new section Tools
Add act under new Tools section

I actually think there is a difference between the two actions (the one I mentioned previously vs. this one) and value to having both. Sorry for the inconvenience of update + failure of linter, there was an issue that I think is now fixed in this repo - you may have to pull latest. Could you add yours right underneath the other Action with the title "Run GitHub Actions Locally with a web interface" and name it "Run GitHub Actions Locally in Terminal"

Thanks @jessicalostinspace - updates made


Add badges into README along with code coverage configuration (codecov.yml) into the repo

And please also add badges into README Including :

CI codecov
GitHub release
Docker Pulls
Go Report
TODOs
gitter
license
etc..

refer to the kubevela repo for details.

Hi!
I would like to work on this issue
Do assign me if approved

Added the following:
Any changes to be made?

@the-amazing-atharva Cool, you can send the PR and let's check.

Sure!


Audio/ogg mime type cannot be recognized

I have the file with mime type audio/ogg, then I put this file into docker-container with python3:latest, where is using buildpack-deps:jessie and in debian file system file has mime type application/octet-stream. Seems, that system just can't recognize the mime type and sets default type( application/octet-stream). I have tried to update the mime types lib, but it didn't give any results. Really need your help.

oit ys net microsof callerie debege is sosf awer extantion visual studio rpc

file is showing the correct audio/ogg mime type. So perhaps it is something in your python application or libraries?
$ docker run -it buildpack-deps:jessie

$ find / | grep ogg
/usr/share/mime/audio/ogg.xml

$ wget https://upload.wikimedia.org/wikipedia/commons/c/c8/ample.ogg

$ file --mime-type Example.ogg
Example.ogg: audio/ogg

Since this is not an issue with the buildpack-deps image, in the future, it'd be better to post questions like this in the Docker Community Forums, the Docker Community Slack, or Stack Overflow.


ND4J unit test failures

Nd4jTestsComparisonFortran.testGemvApacheCommons
CompressionMagicTests.testMagicDecompression3
CompressionSerDeTests.testAutoDecompression1
DataSetTest.testShuffle4d:459
DataSetTest.testShuffleNd:496
Tests run: 858, Failures: 5, Errors: 0, Skipped: 19
Most likely due to recent linspace changes.

2 issues here:

float precision issues when it should be an integer (no rounding should be required)
Nd4j.linspace(anything1 ,anything2, 1) -> NaN

.testGemvApacheCommons: edge case with Nd4j.linspace(anything,anything,1) -> returns NaN
.testMagicDecompression3 and .testAutoDecompression1: looks like a precision issue - conversion of values like 11.9999999 to INT16 (or INT8 for second). Either test needs to change, or we need both int and double/float versions of linspace?

.testShuffleNd: precision issue again with casting to int. 962.0 vs<PHONE_NUMBER>648438
        //Checking Nd dataset which is the data
        for (int dim = 1; dim < numDims; dim++) {
            //get tensor along dimension - the order in every dimension but zero should be preserved
            for (int tensorNum = 0; tensorNum < ds_data.tensorssAlongDimension(dim); tensorNum++) {
                //the difference between consecutive elements should be equal to the stride
                for (int i = 0, j = 1; j < shape[dim]; i++, j++) {
                    int f_element = ds.getFeatures().tensorAlongDimension(tensorNum, dim).getInt(i);
                    int f_next_element = ds.getFeatures().tensorAlongDimension(tensorNum, dim).getInt(j);
                    int f_element_diff = f_next_element - f_element;
                    if(f_element_diff != ds_data.stride(dim)){
                        System.out.println(ds.getFeatures().tensorAlongDimension(tensorNum, dim).getDouble(i) + "\t" + ds.getFeatures().tensorAlongDimension(tensorNum, dim).getDouble(j));
                        throw new RuntimeException();
                    }
                    assertTrue(f_element_diff == ds_data.stride(dim));
                }
            }
        }

Fixed: https://github.com/deeplearning4j/nd4j/pull/1483


KHARMA 2024.9

More transmissive boundaries, more stringent tests, more documentation, more cleaner, more faster, more better.
Highlights:

Option to allow fluxes over the pole as if it were excised ("true" transmitting polar boundary conditions).  Enable with boundaries/excise_polar_flux=true
Magnetic field cleanup for face-centered fields, allowing resizing more simulations (to resize SMR simulations see #109)
Fixes for polar mitigations (B3/T3/U3 averaging), including better ImEx driver support
Add an input deck of modified parameters when restarting, e.g. ./run.sh -r restart_file.rhdf -i new_input_parameters.par
Faster implicit solver for AMD hardware (#122)
Parameter updates and code cleanup (#94)

Finally a release with net negative line count!  The tests passed if you click through, GitHub limits the number of status updates per commit and our mirror with GitLab hits the limit if the tests take too long.


[FEATURE REQ] Adding managed RunCommand capabilities

Library name
Azure.ResourceManager.Compute
Please describe the feature.
There is an Azure Compute feature in public preview right now which allows naming of RunCommand execution and retrieval of the status of the RunCommand. https://docs.microsoft.com/en-us/azure/virtual-machines/linux/run-command-managed.

Currently, there is no method from VirtualMachineResource to deploy a managed run command (hitting the PUT /subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/Microsoft.Compute/virtualMachines/<vmName>/runcommands/<runCommandName> endpoint). I would like to request this feature to be added as an instance method to VirtualMachineResource.

The current GetVirtualMachineRunCommand and GetVirtualMachineRunCommandAsync methods can properly retrieve the status of the managed RunCommand. These methods can also expand the instanceView which contains the execution output results as long as the expand argument is equal to "instanceView". I saw this after sending my own PUT request to the endpoint I mentioned in point (1) using "TestingRunCommand" as the runCommandName and "echo 'Hello'" as the script in the request body.
However, the plural method GetVirtualMachineRunCommands has no expand parameter and there is no GetVirtualMachineRunCommandsAsync method at all. I would like to request that the expand parameter be added and that GetVirtualMachineRunCommandsAsync be added as well.

I am in need of this feature as I am building a DevOps service for the Azure Postgres team which will deploy and retrieve the status of these managed scripts. It is necessary for the service to know whether the script execution succeeded and the output of the script execution; this data is contained in the expanded instanceView portion of the GetVirtualMachineRunCommand data. However, it is important that deploying the RunCommand and retrieiving the status can be done asynchronously in case of a server failure. Currently, if the RunCommand is executed, but the service fails there is no way of knowing whether a particular virtual machine executed the RunCommand. We are trying to keep this DevOps service stateless, so enabling these features would be very helpful.

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Compute - VM:0.14831086,Service Bus:0.14037932,Compute:0.053964965'

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

Hi @samir-puranik , yes, we will support it soon in the stable release this month.

Hi @ArthurMa1978, even after stable release I'm still unsure how to deploy named RunCommands to the VM using the SDK. How can I run a named RunCommand? I still see that the only parameters for Azure.ResourceManager.Compute.Models.RunCommandInput are:

CommandId (not the same as name)
Script (script to run)
Parameters (parameters to script, if there are any)

Use the VirtualMachineRunCommandCollection.CreateOrUpdate


add test structure and coverage tests

This PR implements basic Jest Tests ensuring rendering screens.

Both fixed!

Should I change the message for the sake of history?
About the hack, I didn't manage to find out the reason circleCI wasn't
installing the packages correctly after researching for a while ...
On Mon, Jun 21, 2021 at 1:39 PM Bernardo Vieira @.***>
wrote:

@.**** commented on this pull request.
"Force Jest Installation" it's a bit strong. I would prefer "Install Jest
Locally".
But I'm wondering, why don't we install dev dependencies?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/impactMarket/mobile-app/pull/108#pullrequestreview-688373573,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKU4GNOBYEQGYPVHPCYLPTDTT4XH5ANCNFSM47AHB3BA
.

you were just missing one tiny detail


Added react-native-nigeria-community/react-native-cloudinary-image-picker to tools.

@all-contributors please add @just1and0 for docs

@all-contributors please add @just1and0 for docs


An unknown type seems to break validation

I tried a test with
{
"@context": "https://schema.org/",
"@type": "HeadphoneProduct", ...etc}
where some properties and specifically this type don't exist.
It gives only a dissapearing popup: "validation error - cannot ready property 'failures' of undefined".

There was a null check that I accidentally missed :( should be fixed now


Note that auth must be configured after rest/socket clients

It would be useful to note in the documentation that the auth client must be configured after the rest client. If they're configured in the opposite order, the auth token doesn't get added to the request header.

Oh, good addition.  Would you mind updating wherever applicable in the new API docs?  https://github.com/feathersjs/feathers-docs/blob/auk/api/authentication/client.md


Add ByteArray and List workarounds.

https://github.com/permissions-dispatcher/PermissionsDispatcher/issues/599 and https://github.com/permissions-dispatcher/PermissionsDispatcher/issues/619 would be resolved by this PR.

Let me merge.


Fix undefined method each error occurring on static assets. [Fix #9]

Hello everyone. Any news on this? Thanks!

+1

@futhr if you want we could probably just push our own copy to spree-contrib organization and cut our own release since this doesn't appear to be going anywhere.

@JDutil :+1: since this has not been maintained for 3 years, rename it with _ underscore so it may be released to rubygems.

Please Merge +1

Hi all, I left Sunlight Labs in 2012 and lost commit access. My apologies that this was left unattended. I've regained commit access for this repo, and will publish the gem update after getting myself set up for that again.

@luigi thanks!

:shipit:

Alrighty, version 0.1.3 is cut:
https://rubygems.org/gems/rack-honeypot

@luigi Thanks, and nice dedication :)


Static Build and CD for mxnet-cu102/mxnet-cu102mkl

Description
add mxnet-cu102/mxnet-cu102mkl, resolves #17058
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[x] add mxnet-cu102 and mxnet-cu102mkl static builds
[x] add CD job for the new packages.

We also should add the ci/docker/Dockerfile.build.ubuntu_gpu_cu102 - for testing and building the dynamic libmxnet ^^

I'm waiting for ci-dev to come back up properly so we can run a test =S

@perdasilva let me know how I can help


Add support for knockout text

Description
Text knockout is a quite important technique: instead of printing a text, a rectangle around the text is printed and the text is not printed. This means, the text looks white when printed on a white paper. But the text will be orange when printed on an orange paper, because it just gets the paper color and the text is never printed, only everything around the text is printed:

PDF supports this technique and I think it is also possible with SVG.
I reopen this as an issue here because the text in this discussion was not clear enough.
Example PDF from LaTeX with text knockout (Firefox pdf.js renders it correctly):
knockout.pdf (the code for this PDF file is from here)
And without background color: knockout2.pdf
Use Case
The use case is to make the knockout text technique possible with typst which allows for impressive design and headings.

Would be cool to support boolean operations more generally


Child debug sessions do not always show threads and stack traces

Hi,
I am trying to use vscode.debug.startDebugging in debug extension, passing a parentSession parameter. This produces a nice tree of debugging sessions in the call stack pane!
Example pseudo-code:
// ... get a root session
vscode.debug.startDebugging(folder, config, rootSession);
// ... get a child2 session
vscode.debug.startDebugging(folder, config, child2Session);

However, after some trial and error, I've found that non-leaf debugging session does not show any threads (I report multiple over Debug Adapter Protocol's ThreadsRequest). Also, when pausing in such a non-leaf debugging session, I do not see stack frames in the call stack pane, although the session itself is clearly marked as paused.
Example pseudo-code:
// ... get a child3 session
child3.dap.onThreads => return {threads: [thread1, thread2]}

Please see screenshot for the reference:

VSCode Version: 1.36.1
OS Version: macOS 10.14.5

Perhaps I am doing it wrong, but I wasn't able to find any documentation for this, unfortunately.

@dgozman  Thank you very much for reporting this.
Can you please create a reproducable sample by forking the vscode mock debug https://github.com/microsoft/vscode-mock-debug
That way I can easily reproduce this issue and try to fix it. And sorry for the slow response I was on vacation

@isidorn Here is a branch which shows the issue. Please run the "Extension" configuration and issue command "Trigger issue 77841". You will see a tree of debugging sessions in the call stack pane, all of them paused and only the deepest one showing a thread with call stack.

Thanks for the branch. I will look into this next week

@dgozman good catch. I pushed a fix, please try it out in vscode insiders from Wednesday onward https://code.visualstudio.com/insiders/
And let us know if the issue is fixed for you

@isidorn Thank you, seems to be fixed!

@dgozman Thanks for letting us know! Adding verified label.


Project Won't Build

Having a hard time building the project, using Android Studio 2.1.2. I can't comply with the instructions to create the build configuration. When I got to select a module for the Run->Edit Config step, the only module that appears is the "TerraLegion" one. Only have some basic knowledge of Android Studio, maybe someone else will have better luck figuring it out. If you could try to set it up from a clean install in a virtual machine, I find it helps.

Interesting. Just clarifying, when you opened the project, did you select the build.gradle file that is in the top directory of the project?

Yes I did. It looks like it ran some scripts and downloaded some files before it opened. Also tried other things like selecting the folder and such but it didn't change anything.

Can you go to the project explorer on the left side of Android Studio which lays out the folder hierarchy and post a screenshot if it extended out? I want to see where it is starting.

Not sure what happened but after I reinstalled Android Studio again it seems to be working now. Sorry for the trouble.


TextInput with Typescript Error:-Type 'number' is not assignable to type 'string | undefined'

 <TextInput           keyboardType="numeric"           style={{ marginHorizontal: 10, backgroundColor: 'white' }}           label="Mobile Number"           value={formData.mobileNumber}           onChangeText={(text) =>             setFormData({ ...formData, mobileNumber: parseInt(text, 10) })           }
typescript giving error in "value" attribute "Type 'number' is not assignable to type 'string | undefined'"

React Native does not support typescript officially. This sounds like an issue with the DefinitelyTyped typings, you probably want to submit an issue there


[FEATURE REQUEST] Persist search between tabs

Before submitting the issue

[X] I have checked that the requested feature is not a duplicate or, if it is, it needs to be reopened
[X] I have checked that I am running the latest version of WingetUI
[X] I have checked the FAQ section
[X] I have read the contributing guidelines and I agree with the Code of Conduct

Is your feature request related to a problem? Please describe.
It frustrates me when I want to check if a tool is installed and if not, install it. I enter a term into the installed packages tab and if I do not find and switch to the discover packages tab I expect the search bar to stay the same, instead I have to reenter the search term.
Describe the solution you'd like
I would prefer if the search bars always would contain the same text, or if there was an option for this.

hmm... I don't like the idea in general. Wouldn't it be even better for your use case if there would be a message on the Installed Packages page that sounds something like this:
The package you're searching for is not installed. Would you like to install it now?

With a button that takes you to the Discover Packages page with the search pre-filled?


porting master to dunfell

Hi,
I tried porting master to dunfell as I need a more recent scipy feature. I had to add a recipe for a more recent version of python3-pybind but that worked fine. Now, I'm stuck with a problem related to the compilation of lapack. This is the essence of the error output:
2022-04-13 13:07:02 - INFO     - |     /usr/share/cmake-3.16/Modules/FortranCInterface/Verify/main.c:14: undefined reference to `VerifyFortran'
2022-04-13 13:07:02 - INFO     - |     collect2: error: ld returned 1 exit status
2022-04-13 13:07:02 - INFO     - |     make[3]: *** [CMakeFiles/VerifyFortranC.dir/build.make:103: VerifyFortranC] Error 1
2022-04-13 13:07:02 - INFO     - |     make[3]: Leaving directory '/build/build/tmp-orange-pi-zero/work/armv7vet2hf-neon-poky-linux-gnueabi/lapack/3.9.0-r0/build/CMakeFiles/FortranCInterface/VerifyC'
2022-04-13 13:07:02 - INFO     - |     make[2]: *** [CMakeFiles/Makefile2:81: CMakeFiles/VerifyFortranC.dir/all] Error 2
2022-04-13 13:07:02 - INFO     - |     make[2]: Leaving directory '/build/build/tmp-orange-pi-zero/work/armv7vet2hf-neon-poky-linux-gnueabi/lapack/3.9.0-r0/build/CMakeFiles/FortranCInterface/VerifyC'
2022-04-13 13:07:02 - INFO     - |     make[1]: *** [CMakeFiles/Makefile2:88: CMakeFiles/VerifyFortranC.dir/rule] Error 2
2022-04-13 13:07:02 - INFO     - |     make[1]: Leaving directory '/build/build/tmp-orange-pi-zero/work/armv7vet2hf-neon-poky-linux-gnueabi/lapack/3.9.0-r0/build/CMakeFiles/FortranCInterface/VerifyC'
2022-04-13 13:07:02 - INFO     - |     make: *** [Makefile:121: VerifyFortranC] Error 2
2022-04-13 13:07:02 - INFO     - |
2022-04-13 13:07:02 - INFO     - |
2022-04-13 13:07:02 - INFO     - | Call Stack (most recent call first):
2022-04-13 13:07:02 - INFO     - |   CBLAS/CMakeLists.txt:9 (FortranCInterface_VERIFY)

I have
FORTRAN:forcevariable = ",fortran"
RUNTIMETARGET:append:pn-gcc-runtime = " libquadmath"

in my local.conf. Any hints are welcome! :)
Best

Just saw your hint on hosttools from here: https://github.com/tuxable-ltd/meta-scipy/issues/2#issuecomment-950039672
I'll try that... hang tight.

Just saw your hint on hosttools from here: #2 (comment) I'll try that... hang tight.

Didn't work ;(


Add Chinese translations in zh-CN.yml

This adds what I believe is the complete set of translations, in Chinese since we recently launched our store there and use solidus_auth_devise. The translations were provided by an agency based in mainland China, so should be as reliable as they come.

Thanks @chrisradford, much appreciated!

No problem at all, any idea when you might be cutting the next release?

@chrisradford there's still some discussion in #61, but I imagine a new release should be cut sometime this week or next.


Biscuit 2.0

Version 1.0 was released in March 2021 245ab9e. Since then, we got more experience using it, and there are still some rough edges. I discussed it a lot with @divarvel and we feel it could be improved, but that would require breaking changes, hence a 2.0 version.
Proposals
New cryptographic scheme
We're currently using aggregated signatures (pairings and VRF designs were abandoned early) over Ristretto to ensure Biscuit's security properties. The scheme is working fine, but is complex to implement, even when copying the libsodium calls list.  Auditing it, for every implementation, will be a pain.
Proposal: we move to a new scheme, similar to the "challenge tokens" idea described in the design document, but simplified
It boils down to having each block signing the next block's public key, and shipping the last secret key with the token (so it can add another level). It's basically a chain of signatures like a PKI, can be done with a serie of ed25519 keys (easy to find good implementations), and it is easy to seal a token (sign the entire token with the last secret key, remove the secret key, send the token with the signature).
breaking change: the entire protobuf format changes
cf issue #73
Aggregation operations
As mentioned in #38: it would be useful to support aggregation operation in Datalog, like count, sum, min, max, average, and set operations like union and intersection.
Potential problem: in biscuit implementations, Datalog uses the bottom up, naïve approach, which could result in infinite execution through rules like this one: fact($i) <- fact($j), $i = $j + 1
This could be fixed by moving to different implementations, like the top down approach. We could also restrict the kinds of operations available, but I'm worried we would spend a lot of time finding all possible cases. Fixing it once in the engine might be better.
TODO: write issue
Symbol table
Manipulating the symbol table is messy, and it use in both the format and the datalog engine do not help in understanding it. It was introduced both to reduce the token's size (because some names and strings might be repeated) and for faster datalog execution (by interning strings, we can unify them through comparing integers instead of comparing entire strings).
Unfortunately, the separation between "symbols" and "strings" is not clear, and providing custom symbol tables is error prone.
Proposal: remove the symbol type, except for some special symbols like authority and ambient, have every string be stored in the symbol table, add more elements to the default symbol table
It would probably reduce the token size a bit, and simplify the Datalog implementation (and make it slightly faster)
breaking change: this changes the Datalog serialization, and removes the symbol type
TODO: write issue, test implementationthis changes the Datalog execution
Revocation identifiers
We currently have two kinds of revocation identifiers, unique and not unique, because unique revocation identifiers were added afterwards. We should return to unique revocation identifiers only
breaking change: older revocation identifiers will not be used anymore
Ternary and n-ary operations
Currently expressions only support unary and binary operations, we'll probably need to support larger types of operations
Scoped rules
Currently we have a concept of "privileged rules" that can generate facts with #authority and #ambient symbols. Those symbols are used in facts describing the basic rights of the token (from the root block) and the current variables from the request (date, which resource is accessed, IP address, etc).
These symbols are confusing, and currently facts and rules in blocks other than block 0 can easily mess with each other (like, block N+1 generating facts to pass checks from block N).
Proposal: rules and checks should only be able to use facts from earlier and current blocks, not future ones, and generate facts scoped to the current block. The verifier generates facts at the scope of the first block but can check facts from all scopes
Potential problems:

this will be surprising compared to other Datalog implementations

breaking change: this changes the Datalog execution
cf issue #75

I can elaborate on scoped rules if needed. IMO, the main work would be nice tooling and error reporting, to help understand what rules are available. Putting block numbers in the syntax seems very error prone (more than the current system with #ambient and #authority, with the extra complexity of having to count block before creating the datalog statements).

new cryptographic scheme:

spec: https://github.com/CleverCloud/biscuit/pull/77/commits/d91e055156b1242a8905a25894633325d91655af
Rust: https://github.com/CleverCloud/biscuit-rust/commit/6aba60007df08109a359d21d67f9b1ef0f67d812

scoped rules #75:

spec: https://github.com/CleverCloud/biscuit/pull/77/commits/0175a4e3c5563b215a6c6530ad40d8e53944139f
Rust: https://github.com/CleverCloud/biscuit-rust/commit/f750e2bc69c58e1d7f949619459952ca7cbc04eb and https://github.com/CleverCloud/biscuit-rust/commit/42b4bece6b80581539a844432d186964a38b14dc

scoped rules are relatively painless to implement, the trick is in removing rules between each block so that they are not reused on later facts

removing the symbol type:

spec: https://github.com/CleverCloud/biscuit/commit/a195fb4a4cd27fb292b202a504a668c50c508ed0 (samples updated, spec not updated yet)
Rust: https://github.com/CleverCloud/biscuit-rust/commit/1decc95040d514560c24cc9829622d27e1a710cb

use the block signature as revocation id:

spec: https://github.com/CleverCloud/biscuit/commit/deb45ac1dbda9266259230bf00b41847d5358011 (samples updated, spec not updated yet)
Rust: https://github.com/CleverCloud/biscuit-rust/commit/d2de2c302f33d6334c482558411aa3bdc0edf912

so with these changes biscuit 2.0 is nearly done. Aggregation, ternary operations can come as future, smoother updates

rename ID to Term (this has always been confusing):

spec: https://github.com/CleverCloud/biscuit/commit/6c9f12d4b6de16adfbbc102f868a7a2ce2f0920b
Rust: https://github.com/CleverCloud/biscuit-rust/commit/a32425ab6dedb0be954b73d17a8fe28dda07713b

Still missing for this release:

adding a separating character in fact names to help in namespacing things (cc @meh), like module::fact("data"). The character would have no real meaning for datalog execution, it's mainly for the UX
specifying the accepted characters in strings: authorize tabs, unicode characters (with escapes)

sealed token sample: https://github.com/CleverCloud/biscuit/pull/77/commits/bc3a34b3b927e0cb4e90e8d8febbfa9f60bf234f

add an enum indicating the key's algorithm, sign it with the key:

spec: https://github.com/CleverCloud/biscuit/pull/77/commits/f38c856c78c3e3792ff482b415b6c2501cc02a70 and https://github.com/CleverCloud/biscuit/pull/77/commits/1ced35062ebe2ddc350464eb4f5304f708c2903e

rename verifier to authorizer:

spec: https://github.com/CleverCloud/biscuit/pull/77/commits/16357ce0fdac7b839f933b0f73576edfa067c629

As for #72, the spec does not provide a grammar for string literals and identifiers, afaik (for the haskell impl, I followed what was done in biscuit-rust).
I guess providing a grammar for datalog (or at least, literals and identifiers) would be good.
For string literals, idk if there is a standard way to parse them (eg with a complete list of authorized escapes). We could at least mandate utf8, no BOM, stuff like that.

add an EBNF grammar: cbc7aac #82

v2 has shipped :partying_face:


WIP: Add support for livy connections

WIP: More details as progress is made.
In broad terms, the plan is to make use of an interactive Scala Livy session as the main connection for sparklyr.
Scala supports Scala, Python and R sessions; with the R sessions being served by an sparkR client (https://github.com/cloudera/livy#session-kind). We could, potentially, push sparklyr as a type of session to Livy; however, this wouldn't help us at this point in time since sparklyr currently does not execute R code in it's backend, rather, sparklyr executes Scala code which is already supported in Livy's interactive session.
We could, as a separate effort, push in Livy an update to support sparklyr natively when requesting an R kernel; however, this might not require changes in sparklyr at all.

Do we plan on adding something like livy_install, analogous to spark_install, for easy installation + use of livy?

Adding livy_install seems reasonable. The install entails downloading this: http://archive.cloudera.com/beta/livy/livy-server-0.2.0.zip, running SPARK_HOME=<spark_home> ./livy-server and to kill the process to stop. We would need also livy_start and livy_stop. For windows is a bit more work since they currently only provide a launcher for bash: https://github.com/cloudera/livy/blob/master/bin/livy-server but it wouldn't be a stretch to provide something similar for windows. I'll work on this after finishing the core integration to make sure we don't run out of time.

I can take a shot at install_livy.


Read-Only File System Error- Vercel

Hello,
I have this persistent issue where I keep getting an EROFS when in production on Vercel.
For the following paths:
'/var/task/.cache/%2Fvar%2Ftask%2Fpublic%2Fsite-meta.png.txt'
'./public/rss.xml'
This doesn't happen locally (production) only on Vercel - I haven't tried Netlify yet I will update once I do.
I have two pages which have been added by me:

'About' /about
'Contact' /contact

UPDATE:
By disabling rssFeed it removed the rss issue.
By disabling fileCache it removed the site-meta issue.
Log:
[GET] /_next/data/uga8odFSy2oeXWkkOstfj/tag/poems.json 13:01:17:07  EROFS: read-only file system, open '/var/task/.cache/%2Fvar%2Ftask%2Fpublic%2Fsite-meta.png.txt'     at Object.openSync (fs.js:476:3)     at Object.writeFileSync (fs.js:1467:35)     at setCache (/var/task/.next/serverless/pages/tag/[...slug].js:7225:25)     at imageDimensionsFromFile (/var/task/.next/serverless/pages/tag/[...slug].js:7324:3)     at processTicksAndRejections (internal/process/task_queues.js:93:5)     at async seoImage (/var/task/.next/serverless/pages/tag/[...slug].js:6344:23)     at async getStaticProps (/var/task/.next/serverless/pages/tag/[...slug].js:5075:19)     at async renderToHTML (/var/task/node_modules/next/dist/next-server/server/render.js:28:109)     at async renderReqToHTML (/var/task/.next/serverless/pages/tag/[...slug].js:1256:334)     at async render (/var/task/.next/serverless/pages/tag/[...slug].js:1260:626) {   errno: -30,   syscall: 'open',   code: 'EROFS',   path: '/var/task/.cache/%2Fvar%2Ftask%2Fpublic%2Fsite-meta.png.txt' } 2021-02-26T13:01:20.587Z	209213c8-1b68-4f92-93f4-c01ce62c2bae	ERROR	Error: EROFS: read-only file system, open '/var/task/.cache/%2Fvar%2Ftask%2Fpublic%2Fsite-meta.png.txt'     at Object.openSync (fs.js:476:3)     at Object.writeFileSync (fs.js:1467:35)     at setCache (/var/task/.next/serverless/pages/tag/[...slug].js:7225:25)     at imageDimensionsFromFile (/var/task/.next/serverless/pages/tag/[...slug].js:7324:3)     at processTicksAndRejections (internal/process/task_queues.js:93:5)     at async seoImage (/var/task/.next/serverless/pages/tag/[...slug].js:6344:23)     at async getStaticProps (/var/task/.next/serverless/pages/tag/[...slug].js:5075:19)     at async renderToHTML (/var/task/node_modules/next/dist/next-server/server/render.js:28:109)     at async renderReqToHTML (/var/task/.next/serverless/pages/tag/[...slug].js:1256:334)     at async render (/var/task/.next/serverless/pages/tag/[...slug].js:1260:626) {   errno: -30,   syscall: 'open',   code: 'EROFS',   path: '/var/task/.cache/%2Fvar%2Ftask%2Fpublic%2Fsite-meta.png.txt' } 2021-02-26T13:01:20.589Z	209213c8-1b68-4f92-93f4-c01ce62c2bae	ERROR	Unhandled Promise Rejection 	{"errorType":"Runtime.UnhandledPromiseRejection","errorMessage":"Error: EROFS: read-only file system, open '/var/task/.cache/%2Fvar%2Ftask%2Fpublic%2Fsite-meta.png.txt'","reason":{"errorType":"Error","errorMessage":"EROFS: read-only file system, open '/var/task/.cache/%2Fvar%2Ftask%2Fpublic%2Fsite-meta.png.txt'","code":"EROFS","errno":-30,"syscall":"open","path":"/var/task/.cache/%2Fvar%2Ftask%2Fpublic%2Fsite-meta.png.txt","stack":["Error: EROFS: read-only file system, open '/var/task/.cache/%2Fvar%2Ftask%2Fpublic%2Fsite-meta.png.txt'","    at Object.openSync (fs.js:476:3)","    at Object.writeFileSync (fs.js:1467:35)","    at setCache (/var/task/.next/serverless/pages/tag/[...slug].js:7225:25)","    at imageDimensionsFromFile (/var/task/.next/serverless/pages/tag/[...slug].js:7324:3)","    at processTicksAndRejections (internal/process/task_queues.js:93:5)","    at async seoImage (/var/task/.next/serverless/pages/tag/[...slug].js:6344:23)","    at async getStaticProps (/var/task/.next/serverless/pages/tag/[...slug].js:5075:19)","    at async renderToHTML (/var/task/node_modules/next/dist/next-server/server/render.js:28:109)","    at async renderReqToHTML (/var/task/.next/serverless/pages/tag/[...slug].js:1256:334)","    at async render (/var/task/.next/serverless/pages/tag/[...slug].js:1260:626)"]},"promise":{},"stack":["Runtime.UnhandledPromiseRejection: Error: EROFS: read-only file system, open '/var/task/.cache/%2Fvar%2Ftask%2Fpublic%2Fsite-meta.png.txt'","    at process.<anonymous> (/var/runtime/index.js:35:15)","    at process.emit (events.js:327:22)","    at processPromiseRejections (internal/process/promises.js:245:33)","    at processTicksAndRejections (internal/process/task_queues.js:94:32)"]} Unknown application error occurred
[GET] /_next/data/uga8odFSy2oeXWkkOstfj/about.json 13:01:17:00 Loaded env from .env.local 2021-02-26T13:01:20.205Z	56c324e7-9d34-4443-a79e-e1ef9a5c5c1a	ERROR	Unhandled error during request: Error: EROFS: read-only file system, open './public/rss.xml'     at Object.openSync (fs.js:476:3)     at Object.writeFileSync (fs.js:1467:35)     at getStaticProps (/var/task/.next/serverless/pages/about.js:2730:27)     at processTicksAndRejections (internal/process/task_queues.js:93:5)     at async renderToHTML (/var/task/node_modules/next/dist/next-server/server/render.js:28:109)     at async renderReqToHTML (/var/task/.next/serverless/pages/about.js:1256:334)     at async render (/var/task/.next/serverless/pages/about.js:1260:626) {   errno: -30,   syscall: 'open',   code: 'EROFS',   path: './public/rss.xml' } 2021-02-26T13:01:20.206Z	56c324e7-9d34-4443-a79e-e1ef9a5c5c1a	ERROR	Error: EROFS: read-only file system, open './public/rss.xml'     at Object.openSync (fs.js:476:3)     at Object.writeFileSync (fs.js:1467:35)     at getStaticProps (/var/task/.next/serverless/pages/about.js:2730:27)     at processTicksAndRejections (internal/process/task_queues.js:93:5)     at async renderToHTML (/var/task/node_modules/next/dist/next-server/server/render.js:28:109)     at async renderReqToHTML (/var/task/.next/serverless/pages/about.js:1256:334)     at async render (/var/task/.next/serverless/pages/about.js:1260:626) {   errno: -30,   syscall: 'open',   code: 'EROFS',   path: './public/rss.xml' } 2021-02-26T13:01:20.209Z	56c324e7-9d34-4443-a79e-e1ef9a5c5c1a	ERROR	Unhandled Promise Rejection 	{"errorType":"Runtime.UnhandledPromiseRejection","errorMessage":"Error: EROFS: read-only file system, open './public/rss.xml'","reason":{"errorType":"Error","errorMessage":"EROFS: read-only file system, open './public/rss.xml'","code":"EROFS","errno":-30,"syscall":"open","path":"./public/rss.xml","stack":["Error: EROFS: read-only file system, open './public/rss.xml'","    at Object.openSync (fs.js:476:3)","    at Object.writeFileSync (fs.js:1467:35)","    at getStaticProps (/var/task/.next/serverless/pages/about.js:2730:27)","    at processTicksAndRejections (internal/process/task_queues.js:93:5)","    at async renderToHTML (/var/task/node_modules/next/dist/next-server/server/render.js:28:109)","    at async renderReqToHTML (/var/task/.next/serverless/pages/about.js:1256:334)","    at async render (/var/task/.next/serverless/pages/about.js:1260:626)"]},"promise":{},"stack":["Runtime.UnhandledPromiseRejection: Error: EROFS: read-only file system, open './public/rss.xml'","    at process.<anonymous> (/var/runtime/index.js:35:15)","    at process.emit (events.js:327:22)","    at processPromiseRejections (internal/process/promises.js:245:33)","    at processTicksAndRejections (internal/process/task_queues.js:94:32)"]} Unknown application error occurred
Please let me know what I can do.
Thank you

@ramosmikel : Welcome to this project!

The first error has been changed to a warning on #47, so it looks like you are running on an older version of this repo. Could you please update to the latest version? It's expected that the file cache can only be written during deploy and not at runtime.

I have to dig into the second issue a bit deeper, not sure why feed needs to write to file system.

@styxlab My apologies didn't see you replied so fast.
Thanks for all your hard work on this project.
I will merge the fixes on mine.
I disabled rss feed feature since my client doesn't really need it.
Unfortunately, it's for a client so I will be unable to publish or give access.
But if you bare with me I will try get more information.
From what I remember several pages triggered it, it wasn't just the about.
Thanks for the help.

I localized the rss.xml bug, this will be solved in the next release. Please report back, whether or not the latest current release fixes your first error message. Note: While I want to fix these issue, they are uncritical - your site will work regardless.

Just released a new version. These issue should be fixed now. Please report back.


Synthesis failed for Google.Cloud.Dialogflow.V2

Hello! Autosynth couldn't regenerate Google.Cloud.Dialogflow.V2. :broken_heart:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to branch 'autosynth-Google.Cloud.Dialogflow.V2'
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 256, in <module>
    main()
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 196, in main
    last_synth_commit_hash = get_last_metadata_commit(args.metadata_path)
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 149, in get_last_metadata_commit
    text=True,
  File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/subprocess.py", line 403, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'text'

Google internal developers can see the full log here.

Autosynth is still having trouble generating Google.Cloud.Dialogflow.V2. :sob:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to branch 'autosynth-Google.Cloud.Dialogflow.V2'
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 256, in <module>
    main()
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 196, in main
    last_synth_commit_hash = get_last_metadata_commit(args.metadata_path)
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 149, in get_last_metadata_commit
    text=True,
  File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/subprocess.py", line 403, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'text'

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


Add automated checks to make our lives easier.

Motivation
Alleviate some manual checks by letting automated jobs handle this for us. This pull request introduces three actions to do just that. They are as follows:

Check Repro - The github action for checking if issue author presented the repro.
Stale - Mark issues with no repro/response as stale.
Triage - The GitHub action will comment on any issue when you add a label (currently needs more info and needs repro). This can be helpful to not have to write a descriptive message every time when asking for more details.

Great!


"This plugin slows down Homebridge" Reported by Homebridge 1.3.x

Noticed while testing #32 and wanted to bring forward since still unresolved.
This is occurring when a bulb goes off-line or powered off at the mains. The below messages are logged to the console for each bulb that is powered off at the switch. I have two Wiz bulbs controlled by a single switch, so I see the below message twice. After about 10 seconds, the bulb reports in Homekit as "No Response". However, during this 10 seconds or so, the other Wiz lights are stuck on "Updating" until the timeout occurs. I have all plug-ins isolated with to their own Child Bridge, so for me only affects the Wiz lights.
[2/24/2021, 8:51:44 AM] [homebridge-wiz-lan] This plugin slows down Homebridge. The read handler for the characteristic 'On' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.
[2/24/2021, 8:51:44 AM] [homebridge-wiz-lan] This plugin slows down Homebridge. The read handler for the characteristic 'Brightness' didn't respond at all!. Please check that you properly call the callback! See https://git.io/JtMGR for more info.

Stats:

running on the Homebridge-VM-Image Boot2Docker virtual machine
OS: Ubuntu Bionic Beaver (18.04.5 LTS)
Node.js Version: v14.15.5
Npm Version: v6.14.11
Homebridge: 1.3.1

Unfortunately it seems like this might be a homebridge limitation. The plugin responds with the successful values as soon as possible, but it seems like homebridge will wait for everything to respond.
Since pretty much the only way to determine if the bulb is offline is by waiting 10s for it to respond there isn't much I can do about it :(

Is there a way to have HomeKit pull from cached values and just have the plugin update the cached values?

Came here to say the same. In my case the plugin was taking home bridge down, so I had to uninstall it. A shame, it was one of my favorite plugins, and also one of the more useful. It was like hue for the rest of us =)
For now I'll use the wiz app. I Hope you manage to resolve the issue.

@MoTechnicalities I could just have it report a successful change immediately, but that would not reflect real world conditions.
To be clear, we're talking about actually disconnected bulbs that don't have any power right?

I can only say that I noticed that the Tuya app advertises that they cache the state for greater speed. I don't pretense to understand the inner workings. But yes, something needs to be done about bulbs or devices that are in a powerless state. It simply takes too long for everything to come back if you have to wait the full 10 seconds or so just to find out that other bulbs that had nothing to do with this powerless state ARE available! How are other plugins doing this?

OR...
If it is posible for the plugin to know which bulbs have not responded within a certain short test cycle amount of time simply assign them to a "no response" state until the next short test cycle period.

Thanks for that Child Bridge tip! At least it put a bandaid on a really large wound￼! We need a cure though!￼

Let me know if 3.0.2 helps!

Thanks @kpsuperplane! Just updated and will give a full shakedown and let you know findings.

homebridge-wiz-lan v3.0.2.... Much improvement!

Closing this issue. After spending some time with the update, I think we are in a good spot. Thank you!


Vector2 values < 0.0005 are shown as integer 0 in Debug panel

Godot version
4.0.2
System information
Windows 11
Issue description
If a Vector2 value has "small" x or y values (< 0.0005), then in the Stack Variables part of the Debug panel, the values will be shown as "0". Hovering with the mouse also shows 0. Only by hovering over the variable name in the script window, can you see the actual value.
This can lead to annoying bugs where values are not close enough to zero for is_zero_approx to be true, yet are presented as being zero in the Debugger.
I suggest only rounding to zero if is_zero_approx is true for the value. Also, hovering over the value in the Stack Variables list should display the unrounded value in the tooltip.

Steps to reproduce
Set a Vector2 variable to small x and y values.
Set a breakpoint.
Inspect the variable's value in the debugger.
Minimal reproduction project
N/A

Thanks for the report! Consolidating in https://github.com/godotengine/godot/issues/18251- Duplicate of https://github.com/godotengine/godot/issues/18251, as the inspector and debugger rely on the same code.


Update glu-1.0-0.rockspec

Thanks for your contribution :)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
42

Relevant Lines:
42

💛  - Coveralls


Autopilot doesn't support some fields in daemonset

I tried to install Falcon Sensor on GKE Autopilot and this is the output:
Violations details: {"[denied by autogke-default-linux-capabilities]":["linux capability 'SYS_ADMIN,DAC_READ_SEARCH,BPF,PERFMON,SYS_RESOURCE,NET_ADMIN' on container 'falcon-node-sensor' not allowed; Autopilot only allows the capabilities: 'AUDIT_WRITE,CHOWN,DAC_OVERRIDE,FOWNER,FSETID,KILL,MKNOD,NET_BIND_SERVICE,NET_RAW,SETFCAP,SETGID,SETPCAP,SETUID,SYS_CHROOT,SYS_PTRACE'.","linux capability 'SYS_ADMIN,DAC_READ_SEARCH' on container 'init-falconstore' not allowed; Autopilot only allows the capabilities: 'AUDIT_WRITE,CHOWN,DAC_OVERRIDE,FOWNER,FSETID,KILL,MKNOD,NET_BIND_SERVICE,NET_RAW,SETFCAP,SETGID,SETPCAP,SETUID,SYS_CHROOT,SYS_PTRACE'."],"[denied by autogke-disallow-hostnamespaces]":["enabling hostPID is not allowed in Autopilot.","enabling hostIPC is not allowed in Autopilot.","enabling hostNetwork is not allowed in Autopilot."],"[denied by autogke-disallow-privilege]":["container falcon-node-sensor is privileged; not allowed in Autopilot","container init-falconstore is privileged; not allowed in Autopilot"],"[denied by autogke-no-write-mode-hostpath]":["hostPath volume falconstore in container falcon-node-sensor is accessed in write mode; disallowed in Autopilot."]}
The values are hard-coded in daemonset template.

Hello,

Did you set node.gke.autopilot to true and is your backend set to bpf?
Are you using the latest daemonset sensor image?
Are you using a custom registry? If you are using a custom registry, you will need to work with Google to allow this custom registry to work. Otherwise, it will fail with the above message.

Hi,

Yes
Yes
I'm using a custom registry, but I'm using the image that I've pulled from you registry with a key

Because you are using a custom registry url, you need to work with Google to allowlist the use of this registry url. Until they allow list it the custom registry url in your account, you will be prevented from deploying and keep getting the error message stating such.

I have already worked with Google to make GKE able to retrieve the docker image from our private Registry.
So much so that the same image is correctly downloaded by a GKE Standard.
The problem is not the download of the image by the kubernetes cluster (this step happens correctly both in GKE Standard and in GKE Autopilot), but it seems to be related to permissions that are set in the deployment and that in GKE Autopilot are not supported.


All patched SublimeLinter color schemes show up in the "UI: Select Color Scheme"

Beginning with ST3 3127 a new command UI: Select Color Scheme was introduced. It lists all *.tmTheme files it can find and thus shows all the patched versions SublimeLinter created, too. This is confusing.
Suggestion
To avoid this all the patched color schemes should use *.hidden-tmTheme as file extension.

I also created an issue in SublimeTextIssues as it was not clear who might be responsible to hide unwanted color schemes. The response seems clear.

Note that they also used to show up in the menu before the addition of the quick-panel selection (with previews).


This environment is missing some function environment variable values.

Before opening, please confirm:

[X] I have checked the custom domains troubleshooting guide.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
d2004l7njftm5k
Region
eu-central-1
Step
Backend Build
Status
Build failed
Issue or question
Hi,
Thank you in advance for your support.
We are working on a inherit project with Vue.JS / Nuxt, and when we try to start the build process in Amplify project, it seems to be missing a variable named S3_BUCKET which we are not aware of and not found in all other AWS services.
"This environment is missing some function environment variable values"
We know that seems intuitive, but already tried to remove this function in code and push to repo, and the same thing happens.
The repository is stored in CodeCommit, and uses some Lambda functions.
We tried to check all parameters in these services, but that one mentioned it's not present. Also, we reached out to the previous developer, and he was also unable to identify the issue, said it never happened.
Even when we try to redeploy the last successful build, it fails.
The question is: Is there a way to bypass this missing variable just to check if build will work; or maybe this is a recurring error that requires specific steps to rebuild project?
Does the error occur because of this function or because of the session identifier?
Let me know if you need more information.
We've been stuck with this error for a month. Appreciate any help.
Error message

Additional information
A curiosity: I don't know if this is normal, but most times when a new deploy happens, the message to reconnect repository appears. When I reconnect, and go back to the build screen it shows this error reported about environment variables missing.

Hi @rahulacoopers 👋🏽 It looks like there is a Lambda function that has environment variables configured for it and Amplify is having a hard time finding one of those variables during the build process.

already tried to remove this function in code and push to repo, and the same thing happens.

When you removed the function, did you run amplify push locally to push those changes to the backend environment?

Also, if you want to keep the function and the former developer can tell you what value the S3_BUCKET variable correlates to, you can add that value manually to SSM Parameter Store using this guide: https://docs.amplify.aws/cli/reference/ssm-parameter-store/#manually-creating-parameters

Hello @hloriii ,
Thank you for investigating this issue.
About requesting these variables values, we already did and the developer informed that he doesn't have it.
Although this function needs to exist, I'll try again to remove it as suggested and run the command mentioned. As far I remember, I did something like that but maybe removed the function in code and removed the env variables directly in Amplify.
I'll update you soon here.

Hello, @hloriii
Thank you for your patience.
I believe the build problem has been resolved, and I would like to provide some comments on the procedures performed.
Firstly, I had to remove the Amplify folder from the local repository and import it again. This was necessary because even after updating the AWS credentials through the terminal, I kept encountering the error "Token expired" when attempting to run commands in Amplify.
By removing the folder and downloading the Amplify environment again, I synchronized the previous changes that were made and was able to specify new Access Keys. Subsequently, I executed the amplify push command, specifying a fictitious value for the S3_BUCKET variable that I found in the changes history of another function. I am uncertain if this was the correct value for the variable, but I will be conducting tests to verify if the function is still operational.
Following that, the Amplify environment was successfully updated, and the build using the latest version of the repository was completed. Some changes were successfully uploaded.
Thank you in advance, and if you have any further suggestions, I would appreciate hearing them.


complete scipy.signal

it uses Untyped* ~662~ ~628~ 623 times

Once #157 is merged we'll be at 517

@pavyamsiri are you currently working on a particular module or something? Because I'd like to work on this as well, and we should probably avoid a situation where we're both working on the same code.

Not currently no. The remaining modules have a lot of functions in them so I haven't done any work on them yet. I'm not sure when I'll get back to working on this yet so you can have free reign over which ones you want to work on.

Not currently no.

Ok, no problem! If there's anything specific you'd like to work on, let me knoow, and I'll "reserve" it for you :)

The remaining modules have a lot of functions in them so I haven't done any work on them yet.

Yea there are a couple of real "plus-sized" modules left 😅. It's probably a good idea to split those up. At first glance there appear to be some natural clusters of functions in e.g. _filter_design and _signaltools, so I guess that could help.
FYI, I'd also gladly accept single-function "coffee-break" PR's 😄.


Feature request: Hide sidebar on startpage.

It happens often that a client find a page they shouldn't be on, that other client's should be on - due to recent activity and recently updated pages are visible on the startpage.
An option to disable this is deeply appreciated!

It would be nice to have one of the below:

a toggle button to expand the sidebar.  Save which state it is left in.
show sidebar on page load but then auto hide (to a button) to save screen space

This has had relatively minimal request over the years, and I don't want to go down the path of controls for every UI element, but we instead now have the visual theme system which can facilitate override and customization of any view, so I'll therefore close this off.


Show the transform operation numbers in 2D

Closes https://github.com/godotengine/godot-proposals/issues/267

That's quite a few manual update calls, I'm thinking it might end up leading to situations where we could forget adding new updates where relevant. Isn't there an existing update call that could be relied on for this? (E.g. whenever the transform actually changes)

There's some canvas item state. I'll see if it can be used for something 🤔

Thanks!


Breakout 'stickiness' into ip and session/cookie affinity

Non-browser clients may not be able to replay cookies for affinity; allow an optional fallback mechanism to use ip-based affinity.

Completed in v0.2.0-a1


pipenv run: Install packages automatically

Current Behavior
When running pipenv run in a directory that does not have a virtualenv yet, that virtualenv is automatically generated. But the packages are not installed.
Expected Behavior
When a virtualenv is not yet initialized for a project, I would expect the pipenv run command to either do nothing, or to create both the virtualenv and install the dependencies.
Maybe there are edge cases I haven't thought of yet though?
Describe your environment

OS Type: Linux
Python version: 3.6.4
Pipenv version: 9.0.3

Thanks for the recommendation -- we used to do this and I believe we opted to stop. The discussion is likely in an old issue or PR which revolved around changes to the behavior of pipenv run
closing for now, thanks for the suggestion!

Thanks for clarification. I searched for "pipenv run" in the closed issues and the search turned up 396 results, so I didn't manage to find one where this was discussed 🙂

I'm also very confused by this behaviour. If you could give a link to the mentioned issue that would be great, as I don't think this should remain as is.