Fix a type in the modules section: functions => modules

The last paragraph in the modules section talks about attributes on modules.  It then says, "The built-in attributes that have meaning on a function are ...", and lists attributes such as #[path] that work on modules.
This changes it to "The built-in attributes that have meaning on a module are ..."

Thanks!


Error: MountVolume.MountDevice failed for volume "pvc-XXXXXXXX" on microk8s cluster

After installing the driver on a microk8s cluster, the example dyn-app does not start successfully. Due to
Nov 12 11:01:13 node01.cluster microk8s.daemon-kubelite[255976]: E1112 11:01:13.907517  255976 csi_attacher.go:364] kubernetes.io/csi: attacher.MountDevice failed: rpc error: code = Internal desc = stat /var/snap/microk8s/common/var/lib/kubelet/plugins/kubernetes.io/csi/beegfs.csi.netapp.com/546560a6191b66852bcfc73103f6bc91327cf030684f8394f25acab2da84a015/globalmount: no such file or directory

Installed by
kubectl apply -k deploy/k8s/overlays/my-overlay
kubectl apply -f examples/k8s/dyn/dyn-sc.yaml
kubectl apply -f examples/k8s/dyn/dyn-pvc.yaml
kubectl apply -f examples/k8s/dyn/dyn-app.yaml

Best guess: microk8s does not use /var/lib/kubelet as root dir but /var/snap/microk8s/common/var/lib/kubelet, with sym-linking the common default to that dir. The sym-link does not work with the mounting used by the beegfs driver.
Unfortunately I do not see any config option to specify a prefix/alternate location. But this is needed here AFAIS (similar to the kubeletDirPath in ceph - they suffer from the same without having specified this correctly).
The following patching of sources seems to work for me - please correct me if I am wrong with that or if this could cause problems somewhere later!: from within the repo root dir (I used the 1.7 branch) replace the /var/lib/kubelet occurences in non-test yaml files with the micork8s specific path:
sed -i 's%/var/lib/kubelet%/var/snap/microk8s/common/var/lib/kubelet%g' \
    $(find . -name \*.yaml | grep -v '/test/')

I see the /var/lib/kubelethard-coded also in the driver sourcecode. But I guess (and hope) that for that the sym-link does it's job, that the problem is just a matter of mounting host dirs (being and/or including sym-links) into the containers ... ?

Hello @sta4152,
Thanks for doing the heavy lifting here to figure out what's going on :)
I believe updating the deployment manifests for a particular installation of the driver (as you've done) is the correct way to handle when some Kubernetes distribution like Micro K8s uses a "non-standard" path to /var/lib/kubelet. What you might consider doing instead of updating the default manifests, is creating a new overlay with the required patches/modifications to deploy for Micro K8s. That way you can continue to pull changes to the project including updates to the default manifests without having to stash/reapply your changes.
AFAIK all those hard-coded references to /var/lib/kubelet/ are only used for testing. The important places are not actually hard-coded, but rather passed as flags to the driver at startup (e.g., --cs-data-dir) and your sed command handles updating those and the volume mounts that get everything into the driver's container. So you should be all set, but let me know if you see any weird behavior.
I did want to confirm you didn't need to do anything else to get the driver to work with Micro K8s? You mentioned a symlink, but I wasn't sure if that was actually required or if simply updating the manifests was sufficient.

Hi, thanks for the response.
For patching using sed I already used an overlay, named my-overlay for the issue here as shown above in the report (using a more meaningful name in reality).
For the sym-link: I did not create it myself manually, but this was created by the microk8s deployment using snap (on ubuntu 22.04 LTS, installing microk8s the snap way).


how can I use python

Is there an python code ？

https://github.com/acheong08/ChatGPT

I have use this code  use revChatGPT.V1 but fail now ，get the error
tls_client.exceptions.TLSClientExeption: failed to do request: Get "https://explorer.api.openai.com/api/auth/session": dial tcp <IP_ADDRESS>:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

Internet errors are out of scope. OpenAI blocked in China

是不是要用代理啥的才可以解决这个问题


:bug: fix: fix export

💻 变更类型 | Change Type

[ ] ✨ feat
[x] 🐛 fix
[ ] 💄 style
[ ] 🔨 chore
[ ] 📝 docs

🔀 变更说明 | Description of Change
close https://github.com/lobehub/chat-plugins-gateway/issues/6

📝 补充信息 | Additional Information

:tada: This PR is included in version 1.17.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


String template not working in $queryRaw with postgres

Bug description

String template variable triggers an error in my raw postgres query. When the I dont use a variable, but instead hardcode the value the query is completed sucessfully
How to reproduce
This is my query
const tableName = openaddressesma;
const radiusSearch = await prisma.$queryRaw`SELECT postcode FROM ${tableName} where ST_Distance(geolocation::geography, ST_SetSRID(ST_MakePoint(${parseFloat(
          long
        )},${parseFloat(lat)}),4326)::geography) < ${
          parseFloat(miles) * 1609.34
        };`;

The above query fails and gives the error:
Invalid prisma.queryRaw() invocation:
Raw query failed. Code: 42601. Message: db error: ERROR: syntax error at or near "$1"
But It succeeds when I remove ${tableName} from the query and replace it with a hard code value. eg
const radiusSearch = await prisma.$queryRaw`SELECT postcode FROM openaddressesma where ST_Distance(geolocation::geography, ST_SetSRID(ST_MakePoint(${parseFloat(
          long
        )},${parseFloat(lat)}),4326)::geography) < ${
          parseFloat(miles) * 1609.34
        };`;

Expected behavior
I expect The query to complete and return results from the database.

Prisma information

Environment & setup

OS: ubuntu 18.0.1
Database: PostgreSQL
Node.js version: v14.5.0
Prisma version:
Prisma CLI version: prisma/1.34.10 (linux-x64) node-v14.5.0

I am having this issue as well. Here is a simple example:
async function testResolver() {
      // This will crash
      const name = "Tenant 1";
      const dbResult = await prisma.$queryRaw`select name from tenant where name='${name}'`;

      // This runs just fine
      //const dbResult = await prisma.$queryRaw`select name from tenant where name='Tenant 1'`;

      // As does this
      const name = "Tenant 1";
      const dbResult = await prisma.$queryRaw(`select name from tenant where name='${name}'`);

      console.log(dbResult[0]);
      return dbResult;
}

The error is:

Invalid prisma.queryRaw() invocation:\n\n\n  Your raw query had an incorrect number of parameters. Expected: 0, actual: 1

If you turn on prisma logging, for the non string template you get

prisma:query select name from tenant where name='Tenant 1'

and for the string template you get:

prisma:query select name from tenant where name='$1'

and with the parens around the string template

prisma:query select name from tenant where name='Tenant 1'
{ name: 'Tenant 1' }

Please fix. It is a very serious issue since it makes it very hard write safe SQL. Thank you.

@alexpmay you need to do the following:
const dbResult = await prisma.$queryRaw`select name from tenant where name=${name}`;

Since this will use a prepared statement it will translate the query to select name from tenant where name=$1 and send along $1 as a parameter so you don't need wrap it around quotations.

Closing due to inactivity from original author.

I got the same issues as @gizmoGremlin reported, see https://github.com/prisma/prisma/discussions/12817.

When I try to run DROP DATABASE url_shortener WITH (FORCE); I get:
Raw query failed. Code: `42601`. Message: `db error: ERROR: syntax error at or near "$1"`

      39 |     const dropDatabaseSql = `DROP DATABASE ${databaseName} WITH (FORCE);`
      40 |     console.log(dropDatabaseSql)
    > 41 |     await prisma.$executeRaw`${dropDatabaseSql}`
         |     ^
      42 |     return null
      43 |
      44 |     const initResult = await ctx.run(`npm run init`, { reject: true })

      at Object.request (../../../../../tmp/6d9e6b22c77de75c1a6d613455886d9e/node_modules/@prisma/client/runtime/index.js:45578:15)
      at Proxy._request (../../../../../tmp/6d9e6b22c77de75c1a6d613455886d9e/node_modules/@prisma/client/runtime/index.js:46405:18)
      at Object.<anonymous> (tests/e2e/__testers__.ts:41:5)

Prisma Client version 3.12

This worked:
await prisma.$executeRawUnsafe`DROP DATABASE ${databaseName} WITH (FORCE);`

Nevermind, this is not working actually, I must have misinterpreted my terminal output at the time.
await prisma.$executeRawUnsafe`DROP DATABASE ${databaseName} WITH (FORCE);`

    Invalid `prisma.executeRaw()` invocation:

      Raw query failed. Code: `42601`. Message: `db error: ERROR: syntax error at or near "$1"`

      32 |         })
      33 |         try {
    > 34 |           await prisma.$executeRawUnsafe`DROP DATABASE ${databaseName} WITH (FORCE);`
         |           ^
      35 |         } catch (error) {
      36 |           const isDatabaseNotFoundErorr = error instanceof Error && error.message.match(/does not exist/)
      37 |           if (!isDatabaseNotFoundErorr) throw error

      at node_modules/konn/src/runners.ts:66:16
      Invalid `prisma.executeRaw()` invocation:
        Raw query failed. Code: `42601`. Message: `db error: ERROR: syntax error at or near "$1"`
      at Object.request (../../../../../tmp/3f70588290d8a06de713dcbd0c2e4e93/node_modules/@prisma/client/runtime/index.js:45578:15)
      at Proxy._request (../../../../../tmp/3f70588290d8a06de713dcbd0c2e4e93/node_modules/@prisma/client/runtime/index.js:46405:18)
      at Object.dropTestDatabase (tests/e2e/__testers__.ts:34:11)
      at Object.setdown (tests/e2e/__testers__.ts:48:7)
      at node_modules/konn/src/runners.ts:60:7

IIUC also another mistake I made is that:
await prisma.$executeRawUnsafe`DROP DATABASE ${databaseName} WITH (FORCE);`

Should be:
await prisma.$executeRawUnsafe(`DROP DATABASE ${databaseName} WITH (FORCE);`)

For some reason, Prisma does not accept the use of variables for table names and field names.
One way I found to solve this problem was to use an auxiliary variable to assemble the query and then use this variable with queryRaw.
See an example below:
const query = `
  SELECT * FROM "${options.table}"
  WHERE "${options.column}" = '${value}'
  LIMIT 1
`;

const row: any[] = await prisma.$queryRaw`${Prisma.raw(query)}`;

Important:

If the name of the table or field contains double quotes, they must be placed in the query.
It is necessary to use Prisma.raw() for the query to work.


Add capability for frontend Notification component to display multiple messages

Current Frontend notification design does not have capability to show messages with the same types on ManagePermission page (on top of user-role table).
For example, for type 'error', with multiple errors to be shown, one will override the other, depending on which one would be later to add to the notification state object.
We need that showing multiple messages for the same type capability, such as displaying granting error + email not sent error.
Acceptance Criteria

[ ] Change notification state to handle multiple messages for a type.
[ ] Implement capability to be able to show multiple messages on UI (ManagePermission screen). Might need to talk to Olga how we like to see the order of the different types of messages.
[ ] Refactor/adjust several components for existing pushing to notification logic.
[ ] Adjust component testing if required.
[ ] Make sure scenarios work: single message type with single/multiple messages; muti-message types with single/multiple messages.

Additional Context

Current notification state:

done in #1650


[SPARK-39576][INFRA] Support GitHub Actions generate benchmark results using Scala 2.13

What changes were proposed in this pull request?
This pr aims let benchmark GitHub Actions support the specified Scala version, then it can produce benchmark results using Scala 2.13.
Why are the changes needed?
Help us check the microbenchmark results using Scala 2.13 and ensure they are not slower than using Scala 2.12
Does this PR introduce any user-facing change?
No
How was this patch tested?

Pass Github Actions

https://github.com/LuciferYang/spark/actions/runs/2554277213
Testing it , it seems work

thanks all


express similarity between hashes

distance between similarity hashes like tlsh can be calculated. We need a way to express the distance between two such hashes in rdf statements.
Something like:
hash:A  bash:B
or something qualified with an exact similarity value (or distance metric)

the relationship "is similar to" http://semanticscience.org/resource/SIO_000283 has a definition:
is similar to is a relation between two entities that share one or more features

Applying this to our case, you'd start with:
<http://example.org/a> <..hasVersion> <hash://sha256/abc...> .
...
<http://example.org/b> <..hasVersion> <hash://sha256/def...> .

after applying tika-tlsh hashes, you might get:
<hash://tika-tlsh/1234...> <..derivedFrom> <hash://sha256/abc> .
<hash://tika-tlsh/1233...> <..derivedFrom> <hash://sha256/def> .

Now, after realizing that distance( <hash://tika-tlsh/1234...> , <hash://tika-tlsh/1233...> ) < C where C is some chosen distance constant, we express that hash://tika-tlsh/1234... is similar to hash://tika-tlsh/1233... by :
<hash://tika-tlsh/1234...> <http://semanticscience.org/resource/SIO_000283> <hash://tika-tlsh/1233...> .

now, a indirect relationship between http://example.org/a and http://example.org/b has been established using a location-agnostic method.
fyi @mielliott

Alternatively, a more PROV compatible approach can be imagined.
With some qualified similarity detection activity producing some similarity metric given two tika-tlsh hashes:
(pseudo-quads)
<some:similarity> <...a> <...Entity> .
<some:similarty> <...hasValue> "1.2" .
<some:similarity> <qualifiedGeneration> <generation:uuid> .
<generation:uuid> <..used> <hash://tika-tlsh/1234...> .
<generation:uuid> <..used> <hash://tika-tlsh/1233...> .
<generation:uuid> <...activity> <similarity:calculating:activity:uuid>

examples of desired functionality can be found at #113 and associated issues.


Job summary is always being posted and attached to the workflow run

Issue:
The setup-android action is always posting the job summary (attached to the workflow run). This can be useful in some cases, but it also pollutes the workflow page.
Example:

Solution:
Add an optional parameter job-summary, and only run renderSummary if this is true (can be true by default).

What do you think @amyu?

@dinisnunes1
It was also an option in actios/gradle!
I think it's a very good suggestion!

@dinisnunes1
Changes have been included in v2 and published.


v1.11.0 broke lambdas

We noticed that after upgrading to v1.11.0:

local function development is broken with Runtime.HandlerNotFound
all deployed functions are broken with index.js content of

export function placeholder() {}

node runtime is hardcoded to nodejs16.x even though we set nodejs14.x with app.setDefaultFunctionProps

Fixed in v1.12.4


add ado agent for codeql reporting.

This is the new pipeline that will report codeql report

This runs weekly if there is any code changes.
https://azfunc.visualstudio.com/Azure Functions/_build?definitionId=324&_a=summary

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

Project coverage is 74.33%.  Consider uploading reports for the commit f3b4e91 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #224   +/-   ##
=======================================
  Coverage   74.33%   74.33%
=======================================
  Files          23       23
  Lines         674      674
  Branches      111      121   +10
=======================================
  Hits          501      501
  Misses        173      173

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


provide a single-jar package?

It is theoretically to package up a jruby package, including the jruby runtime and all gem dependencies, in a single jar.  I have considered that since the very first traject, as a possible way to ease installation for non-rubyists.  At first, I think Bill didn't think it was neccesary, but I think 'getting jruby installed and figuring out how to use it' has been shown to sometimes be a barrier to adoption.
Would 'single jar file' (basically the same installation model as SolrMarc) effectively meet this need?
https://github.com/jruby/warbler/issues/297

We could still potentially go this route, bundling up all the jruby-specific stuff (marc4j and solrj) into one big file, but I'm not sure we'll be gaining much over telling people to just install the appropriate gems. I think we should close this.

I think it actually would be gaining a lot (even without the jruby-specific stuff) -- the point is that you don't need to install anything, not even a ruby version (let alone deal with chruby/rvm/whatever), you just need java (which you already have), you download a .jar file, it just works.
Makes it a lot more accessible to the non-rubyist.
However, the fact that traject 2.0 will run in any ruby (does not require jruby anymore) lowers the barriers for use anyway.
However howerver, you still need jruby for performance.
But I'm not in a hurry to do this either. I'm sort of waiting and seeing if there's demand. But if we release 2.0 and still can't get hardly anyone to use traject, I'd reconsider trying this.
Can we just leave this ticket hanging around open, as an advertisement for people interested in it to tell us so?

Given how hard it is to produce such a jar (by which I mean "trivially easy"), there's no reason we shouldn't go ahead and provide one. There must be an automated way to keep up with dependent-gem updates we can tap into, right?

There are a couple things I'd want to figure out -- like how someone using such a jar COULD use additional gems not packaged with the jar if they wanted to, maybe.  But just generally think through different scenarios and try them out and make sure there's a good way to make it so. Which I don't feel like doing so much immediately honestly.
Also I'd want to build some deploy tools for it, so every time we did a release a .jar automatically got built AND packaged up as a github release artifact, etc.
Alternately, I suppose we could release a .jar as an experimental we-don't-promise-to-do-this-again release for people to try out and give us feedback.
If I understand what you mean by "keep up with dependent-gem updates", there's nothing to be done -- just run bundle update before you build the .jar, and it will include the most recent versions of all gems available that meet your gemspec.  If you mean a way for a user of the jar to do it in between jar releases -- I think they're probably out of luck.

If you mean a way to automatically notice that we the maintainers need to release a new .jar because there are new versions of dependencies that need to be packaged with it -- or even go so far as to automatically release the jar with the new bundled dependencies (.jar <IP_ADDRESS> or whatever, 2.0.0 traject code, but with udpated dependencies included) -- there probably IS a way to do that, but it'd be some work that might end up useless if nobody wants the .jar anyway haha.

I still find this idea intriguing, but there hasn't actually been a lot of demand for it, so closing for now.


Cannot open include file: 'google/protobuf/text_format.h': No such file or directory

Hello, I encounterred really odd issue, and stucked for a couple of days. Could someone help?
https://stackoverflow.com/questions/73254664/bazel-build-failed-cannot-open-include-file-google-protobuf-text-format-h

It's unclear what you're doing. The protobuf library looks nothing like the one on github: https://github.com/protocolbuffers/protobuf/blob/main/BUILD.bazel#L188


Question

Hello
I have some question about ur code !!
I want to drag and move your circle menu. Is it possible to do that?
Thank u

No, it does not support this functionality.

oh i got it!!!!
Thanks


Add gdbstub integration test

This depends on https://github.com/hermitcore/uhyve/pull/195, but is ready for review.

The pipe command has only been implemented since GDB 10.1 in 947d39.
Thus, this depends on https://github.com/hermitcore/uhyve/issues/199.

@jounathaen, I disabled the GDB integration test in CI.
Could we merge this now, so the test is available for running locally when adjusting the gdbstub implementation?

Ok!
bors r+


add observability CN blog

Changes:
add observability blog in Chinese by Wei Jin

This pr done the same work as the previous one.
https://github.com/apache/apisix-website/pull/528

This pr done the same thing as https://github.com/apache/apisix-website/pull/528.

This pr done the same work as the previous one.
#528

OK.

Changes made in this pr and https://github.com/apache/apisix-website/pull/528 are almost the same, close this one  and keep https://github.com/apache/apisix-website/pull/528 to reduce confusions.


add instance filed into metrics output to make the metrics line continuous

If we deploy pulsar in k8s without pulsar proxy, we use prometheus to collect metrics, the IP in pulsar cluster is reachable,
but if the pulsar pod restart for some reason, the metrics line is not continuous. we can add pod name into metrics output, thus the metrics line can be continuous.
When pulsar generate metrics output, for each metrics line, we frequently call System.currentTimeMills(), this function should not call frequently, this has performance issue, the document explain the reason, why System.currentTimeMills() is slow, we should try our best to use the same current time for each metrics collector.

When pulsar generate metrics output, for each metrics line, we frequently call System.currentTimeMills(), this function should not call frequently, this has performance issue, the document explain the reason, why System.currentTimeMills() is slow, we should try our best to use the same current time for each metrics collector.

@zplinuxlover Could you please open a separate PR for the performance improvements? The new features always present in the major release, but the performance improvements can be cherry-picked to release branches.

Closed as stale and conflict. Please rebase and resubmit the patch if it's still relevant.


Migrating from J2V8 to Javet/Javenode?

Since J2V8 isn't maintained that much lately, and there are better alternatives to work with, I think the actual library should've been deprecated from the project baseline and replaced with Javet/Javenode.
See here: https://www.caoccao.com/Javet/tutorial/migration_guides/migrate_from_j2v8.html

It's actually funny you should mention this, I've been working on trying to migrate this project to Javet for a little bit now (see branch at https://github.com/Block-JS/blockjs/tree/javet). The migration is done for the most part, I've just hit a couple snags (mainly not being able to import modules without Javet throwing an exception)

Yeah, I've noticed some issues with Javet as well, although I don't know if these are the same ones we're talking about. I just made a pull request, you can check it. As of now there's no way to directly pass a File/Path reference to the Javet runtime, as it messes up with the file reading/writing, possibly a bug?

Well the pull request seems to have fixed one of the issues, that being that whereas before the PR when I'd run the test command /bjs test again after having ran it before it wouldn't run again.
However another issue that I had before still remains. When I'd try to import another file/an NPM module using the import/export syntax Javet claims to support, I get an error like this:
[10:25:51 INFO]: litteraly1984 issued server command: /bjs test
[10:25:51 WARN]: [com.caoccao.javet.interop.NodeRuntime] 7 V8 callback context object(s) not recycled.
[10:25:51 WARN]: [com.caoccao.javet.interop.NodeRuntime] 7 V8 callback context object(s) not recycled.
[10:25:51 ERROR]: [BlockJS] There was an error with the script: test2.js
[10:25:51 ERROR]: [BlockJS] Error: Cannot find package './test'
[10:25:51 WARN]: [com.caoccao.javet.interop.NodeRuntime] 7 V8 callback context object(s) not recycled.

I'm not entirely sure if this is a problem with Javet or if it's perhaps something I'm doing wrong, but I haven't gotten things to work no matter what I try. If anyone wants to take a look I've attached the full logs along with the files I used to test.
test.js
export function test() {
  return 'test';
}

test2.js
import { test } from "./test";

console.log(test());

latest.log

Perhaps it might be related to https://github.com/caoccao/Javet/discussions/4

I checked it, and it looks like even after trying to set up a custom module resolver, it doesn't seem to help. When running the command for the first time it seems to be working, however when the V8 context is reused those imported modules appear to still be there despite the fact that V8Runtime.resetContext() is being used.

> bjs test
[INFO]: test
[INFO]: [BlockJS] [STDOUT] function test() {
return 'test';
}
> bjs test
[INFO]: test
[ERROR]: [BlockJS] There was an error with the script: test2.js
[ERROR]: [BlockJS] Error: Cannot read the array length because "" is null
...
[ERROR]: Could not save data net.minecraft.world.entity.raid.PersistentRaid
...
[ERROR]: Failed to save level ./world
...

Seems like it's the same thing https://github.com/Block-JS/blockjs/issues/2#issuecomment-1186707765

Alright, I was able to get a custom module resolver working in the test suite for the JSExecutionInterface, and it seems to work quite well. All that's left now is to get that resolver working in the JSRunner class

I ended up with something similar to this. I'm not entirely sure what I did different, but it seems to work when reusing the context:
NodeRuntime createRuntime(File file) throws JavetException {
        JavetEngineConfig config = new JavetEngineConfig();
        config.setJSRuntimeType(JSRuntimeType.Node);

        JavetEnginePool<NodeRuntime> pool = new JavetEnginePool<NodeRuntime>(config);

        NodeRuntime runtime = pool.getEngine().getV8Runtime();

        runtime.setV8ModuleResolver(((v8Runtime, resourceName, iv8Module) -> {
            // Matches the file extension
            Pattern pattern = Pattern.compile("((?<=\\w)\\.[^.]+)$");
            Matcher matcher = pattern.matcher(resourceName);

            String ext = matcher.find() ? matcher.group(1) : "";

            String trueResourceName;

            if (ext.equals("")) {
                trueResourceName = resourceName + ".js";
            } else {
                trueResourceName = resourceName;
            }

            File resourceFile = new File(file.getParentFile(), trueResourceName);

            if (!resourceFile.exists()) {
                // TODO: Resolve module from node_modules
                return null;
            }

            return runtime.getExecutor(resourceFile)
                    .setResourceName(resourceName)
                    .compileV8Module();
        }));

        return runtime;
    }

Pretty much all that needs to be done now is resolving any packages from node_modules.


A new service description format

Currently, the representation of chains and clusters is somehow complex/hard/time consuming. Unified, prettier and simpler

The initial idea for a new service description format could be something like:
{
  "latencies": {
    "cluster_1": {
      "cluster_2": 0.001,
      "cluster_3": 0.002
    },
    "clsuter_2": {
      "cluster_1": 0.003,
      "cluster_3": 0.004
    },
    "cluster_3": {
      "cluster_1": 0.005,
      "cluster_2": 0.006
    }
  },
  "clusters": [
    {
      "name": "cluster_1",
      "namespace": "ns_1",
      "nodes": [
        {
          "name": "node_1",
          "services": [
            {
              "name": "service_1",
              "endpoints": [
                {
                  "name": "/end_1",
                  "protocol": "http",
                  "cpu_consumption": 0.003,
                  "network_consumption": 0.002,
                  "memory_consumption": 0.003,
                  "called_services": [
                    {
                      "cluster": "cluster_1",
                      "service": "service_2",
                      "protocol": "grpc",
                      "traffic_ratio": 1
                    }
                  ]
                }
              ]
            }
          ]
        }
      ]
    }
  ]
}

It could help to solve #2 , #3, #4, #5, #8, #9, #12, #13, #14, #16, #18.

As we discussed, we decided to:

split the services for name services simply by having a list of dictionaries for each namespace.
Add a random option for both cluster or namespace placement
protocol could be deleted for each called service
traffic ratio should be renamed to traffic forward ratio.

Also, we decided to wait for merging this PR until the services are ready.
Another point is to fork the repo on our own account to make us able to use every possible feature of Github.

Based on our discussion and to support everything we needed in the previous comment, we decided to go for:
{
  "latencies": [
    {
      "src" : "cluster_1",
      "dest": "cluster_2",
      "latency": 0.002
    }
  ],
  "services": [
    {
      "name": "service_1",
      "clusters": [
        {
          "cluster": "cluster_1", // Random
          "namespace": "ns_1", // Random
          "node": "node_1"// Random
        }
      ],
      "resources": {
        "limits": {
          "memory": "1024",
          "cpu": "1000"
        },
        "requests": {
          "memory": "512",
          "cpu": "500"
        }
      },
      "endpoints": [
        {
          "name": "/end_1",
          "protocol": "http",
          "cpu_consumption": 0.003,
          "network_consumption": 0.002,
          "memory_consumption": 0.003,
          "calledservices": [
            {
              "cluster": "cluster_1",
              "service": "service_2",
              "endpoint": "/end_2",
              "traffic_forward_ratio": 1,
              "requests": "asynchronous"
            }
          ]
        }
      ]
    }
  ]
}


IOError: [Errno 2] No such file or directory: 'README.md'

pip install rant fails. There seems to be a problem with locating README.md
`Downloading rant-0.2.2.tar.gz
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/tmp/pip-build-UlDDzM/rant/setup.py", line 14, in <module>
    long_description=open('README.md').read(),
IOError: [Errno 2] No such file or directory: 'README.md`

Known issue with 0.2.2
Please try 0.5 (not yet released in pip)
pip install --user --upgrade -e git+https://github.com/lrvick/rant/#egg=rant

Closing as this does not seem reproducible in 0.5 but if you have any further issues lmk.


What is the roadmap for Azle to go live in production?

Hi folks,
Really look forward to using Azle in production for support JavaScript / TypeScript on ICP.
Just wonder is there a roadmap or plan for Azle to go live in production?
Thanks and regards,

We are scoping this out right now. It's very nuanced on what this means, as there are many possibilities before considering Azle production ready entirely. Our estimate is 3-9 months depending on what we fit in.
The idea right now is to move forward in the next 3ish months with getting the core ICP APIs in Azle production-ready, and then introducing an experimental flag for everything else.
So short overly-simplistic and probably overly-optimistic answer: 3ish months

But also, though we don't recommend Azle generally for production, you are free to make your own decision. We have many many (100s) of integration tests, a good amount of people using Azle, and we almost never receive bug reports outside of the installation/build process. Obviously that doesn't mean it's safe for general-purpose use, but perhaps your use-case based on your own analysis and safe-guards could be okay, at your entire discretion.

Thanks @lastmjs for the clarifications, they help us estimate our side of work.
Regarding we don't recommend Azle generally for production, did you mean at current stage only? Or for other reasons?
Thanks and regards

Yes at the current stage, we aren't going to give a general recommendation for production use until we've accomplished the work that will make us feel comforting. Your use case and decision making process doesn't have to align with ours


Support multiple inspector objects in the workspace

Derived from the issue #31. User should be able to select a desired inspector between waveform, spectrogram and audiograph. The workspace (right pane) will stack each inspector as a render request is served.

Not the right UI pattern for Canopy. Decided not to work on it.


[1.16] Reforged Dex Percentage Placeholder Not Parsing

As stated in title, using %reforged_dex_percentage% will parse to %reforged_dex_percentage%
Tested both in a ForgeMenu and using %FPAPIBridge_reforged_dex_percentage% and neither worked correctly

Is it specific to this one or is this something you can replicate with all of them?

In limited testing, I also parsed %reforged_party_slot_1_ability% using the FPAPI Bridge (%FPAPIBridge_reforged_party_slot_1_ability% and it did not parse either. Just to rule out any issues with FPAPIBridge, I also parsed %FPAPIBridge_forge_name% which did parse correctly

Oh I think it's probably because I changed it to "reforged16" in the ID

So it should look something like
%FPAPIBridge_reforged16_party_slot_1_ability% - I figured it'd be easier in case there was a conflict but then again how there would be a conflict between a 1.16.5 and 1.12.2 version IDK!

It was the ID change
%reforged16_dex_percentage% parses correctly


ci: only enable sdk dev engine checks on main

Based on https://github.com/dagger/dagger/pull/7483
Rework of https://github.com/dagger/dagger/pull/7628, that doesn't entirely disable these checks.

I would flip the condition & run dev in PRs, and stable on main. Since PRs are less stable than main, I would think that testing dev is more important there. As for stable, that seems to fit more in main since it's checking for backwards compatibility.
The more I think about this, the more I believe that we should run against both dev and stable all the time. The mental model that I have is:

did any of the changes in this PR break anything (a.k.a. dev) ?
are the changes in this PR compatible with latest release (a.k.a. stable) ?

Since new PRs could be merged in main while this PR is open, we want to run the same there since we want to be confident that the combination & ordering of PRs still results in green pipelines.

I would flip the condition & run dev in PRs, and stable on main. Since PRs are less stable than main, I would think that testing dev is more important there. As for stable, that seems to fit more in main since it's checking for backwards compatibility.

SGTM - do you want to handle rebasing / switching the check? I can also do it.

I would still like to take this as-is - we should be testing against both dev and non-dev for these jobs, which aren't currently doing at all (we're only using dev).
I think we should rework the priority of how we test dev at all, moving towards testing everything on dev but still keeping around a few more dedicated compatibility checks - but I think that's out of scope for here.

Looking at this now.


Conflict with jquery bxSlider

I'm using an image slider from jquery (bxslider) in a secondary tab. The slider doesn't work properly. Sometimes the are there after clicking the tab, sometimes not! After switching btw. the tabs, the images in the slider are gone, or only small images like thumbnails are shown.
Any help to fix this? Thanks

This problem is not caused by this plugin, but is a problem with a lot of plugins in general. Basically, this problem occurs because the bxslider plugin is initialized in an html element which is hidden with display: none. For more info, check out: http://stackoverflow.com/questions/11071269/bxslider-within-show-hide-divs


pgsql: add tests with alert metadata - v5

Check for transaction metadata in PGSQL alerts.
Add engine-analysis tests for the used rules, as well, to better describe them and compare with expected behavior.
Related to
Task #7000
Suricata PR: https://github.com/OISF/suricata/pull/11635
Previous PR: https://github.com/OISF/suricata-verify/pull/2014
Updates:

Rebase
deduplicate pcap used for pgsql-7000-ids

Ticket
If your pull request is related to a Suricata ticket, please provide
the full URL to the ticket here so this pull request can monitor
changes to the ticket status:
Redmine ticket:

https://redmine.openinfosecfoundation.org/issues/7000
https://redmine.openinfosecfoundation.org/issues/7113

Tests pass
But https://redmine.openinfosecfoundation.org/issues/7113 is not resolved ?
Is there a suricata PR for this ?

My understanding is that tests are meant to pass and that https://redmine.openinfosecfoundation.org/issues/7113 is not related to this SV PR

My understanding is that tests are meant to pass and that https://redmine.openinfosecfoundation.org/issues/7113 is not related to this SV PR

not fully related, but these tests help with cover for that, isn't that so?

Replaced by: https://github.com/OISF/suricata-verify/pull/2039


Proposed changes to identity-play-auth

Identity are wanting to centralise user authentication i.e. an application should authenticate a user by making a call to the authentication endpoint in identity API.
To achieve this for Guardian applications using this library (members-data-api, membership-frontend, support-frontend, subscriptions-frontend), update the implementation of the authentication methods in identity-play-auth to call identity API and then import this updated version.
Note that because this update will make breaking changes:
RequestHeader => Future[Option[U]]

instead of:
RequestHeader => Option[U]

this might be a good time to ship other breaking changes as well i.e. removing methods and data models that arguably don't belong in this library.
This PR details the proposed changes. Approving this PR = approving the plan laid out in the in-line comments.

Closing this in preference of #1576 in identity


fix: added uuid_extension_test.go test cases

Please provide a description of this PR:
Fix: Added uuid_extension_test.go test cases
(Ref: https://github.com/istio/istio/issues/37354)
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[X] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[X] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

Hi @ramanujadasu. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/ok-to-test

@ramanujadasu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
5f561777b06fc6a2ab4763f8977a20cc7b83037c
link
true
/test release-notes_istio

lint_istio
5f561777b06fc6a2ab4763f8977a20cc7b83037c
link
true
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramanujadasu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
5f561777b06fc6a2ab4763f8977a20cc7b83037c
link
true
/test release-notes_istio

lint_istio
5f561777b06fc6a2ab4763f8977a20cc7b83037c
link
true
/test lint_istio

gencheck_istio
5f561777b06fc6a2ab4763f8977a20cc7b83037c
link
true
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramanujadasu please add some more valuable tests.

FYI https://github.com/istio/istio/issues?q=is%3Aopen+is%3Aissue+label%3A"community%2Fhelp+wanted"+

Could you please add [release-notes-none] label

@ramanujadasu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
5f561777b06fc6a2ab4763f8977a20cc7b83037c
link
true
/test lint_istio

gencheck_istio
5f561777b06fc6a2ab4763f8977a20cc7b83037c
link
true
/test gencheck_istio

release-notes_istio
6e19d39041f51ea1c9e18c0f21719b9a492f938a
link
true
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramanujadasu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
5f561777b06fc6a2ab4763f8977a20cc7b83037c
link
true
/test gencheck_istio

release-notes_istio
6e19d39041f51ea1c9e18c0f21719b9a492f938a
link
true
/test release-notes_istio

lint_istio
6e19d39041f51ea1c9e18c0f21719b9a492f938a
link
true
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramanujadasu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
6e19d39041f51ea1c9e18c0f21719b9a492f938a
link
true
/test release-notes_istio

lint_istio
6e19d39041f51ea1c9e18c0f21719b9a492f938a
link
true
/test lint_istio

gencheck_istio
6e19d39041f51ea1c9e18c0f21719b9a492f938a
link
true
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramanujadasu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
6e19d39041f51ea1c9e18c0f21719b9a492f938a
link
true
/test lint_istio

gencheck_istio
6e19d39041f51ea1c9e18c0f21719b9a492f938a
link
true
/test gencheck_istio

release-notes_istio
b49c68b5d4beb33761354a3d6e90cd6624f603a0
link
true
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


⚠ Bofrost.lu has degraded performance

In 49777f0, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1740 ms

Resolved: Bofrost.lu performance has improved in 10b764d after 37 minutes.


Mac: Increase beacon frame tx attempts

This commit changes/increases the max attempts for a beacon frame to
kDirectFrameMacTxAttempts (direct frame tx attempts).

Codecov Report

Merging #1618 into master will decrease coverage by 1.14%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1618      +/-   ##
==========================================
- Coverage   70.48%   69.33%   -1.15%
==========================================
  Files         156      159       +3
  Lines       19028    20259    +1231
  Branches     2321     2487     +166
==========================================
+ Hits        13412    14047     +635
- Misses       4768     5306     +538
- Partials      848      906      +58

Impacted Files
Coverage Δ

src/core/mac/mac.cpp
79.53% <100%> (+1.25%)
:arrow_up:

src/ncp/ncp_base.cpp
35.84% <0%> (-12%)
:arrow_down:

src/core/coap/coap_server.cpp
81.48% <0%> (-7.41%)
:arrow_down:

src/core/coap/coap_server.hpp
88.88% <0%> (-3.97%)
:arrow_down:

src/core/coap/coap_client.cpp
71% <0%> (-1.78%)
:arrow_down:

src/core/thread/mesh_forwarder.cpp
78.21% <0%> (-0.49%)
:arrow_down:

src/ncp/ncp_base.hpp
0% <0%> (ø)

src/ncp/ncp_uart.cpp
71.6% <0%> (ø)

src/ncp/hdlc.cpp
76.34% <0%> (ø)

src/core/thread/mle_router.cpp
78.09% <0%> (+0.16%)
:arrow_up:

... and 20 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 8f10a45...282faf5. Read the comment docs.


Render Custom Inputs

Are you requesting a feature, reporting a bug or ask a question?
I am asking a question
What is the current behavior?
I dont know
What is the expected behavior?
Can override the render method (if exists) ? for adding  custom inputs. Like if a want to put another Range input or select.
If this is already implemented i would like to know how to  do it . I think that i can do it afterRender events  but i would be nice if can be done  before render
How would you reproduce the current behavior (if this is a bug)?
Provide the test code and the tested page URL (if applicable)
Tested page URL:
Test code
your_code_here

Specify your

browser: chrome
browser version: Versión 65.0.3325.181 (Build oficial) (64 bits)
surveyjs platform (angular or react or jquery or knockout or vue): jquery
surveyjs version:1.0.14

@tximpa91 I am not sure I got you completely.
You may change the rendering by using onAfterRender event, here is the demo
Another way is to create a custom widget. Please go to this repo, section 4. Add your own custom widget and see the plunker examples.
Thank you,
Andrew


Bulk download of all certificates

We should provide a bulk download of all the data about the certificates (ie the same information that is available in JSON), in a CSV file.

Is it ok to just flatten all the fields in the .json description into columns for CSV?
Also currently the .json version of certificates.theodi.org/datasets only shows the first 20 datasets as it's paginated by default.
There is not defined way to do pagination in .json or .csv like there is in .atom or .html, for .json I could use JSON Hyper Schema to define the next/prev links or include them in HTTP Link headers which would also work for .csv format.
The other option is to make .json and .csv be entire downloads of the database.

I think the CSV should be a dump of everything; flattening the JSON for that should be fine.
I think the JSON should probably still be paginated. Including next and prev links in the JSON is good. If it's easy to also use Link headers, do that too.

I had to make the csv download be a pre-generated dump as the app server can't stream responses and fetching the full set takes about 20 minutes of queries.
It also means you can't request subsets as csv which is a shame.
After deploying I did notice a problem which I'm not sure how to fix. The site is served from a cluster of machines but if I generate the .csv in the background it will only update on disk for one server in the cluster. I'm not sure how to get a job to run on all the nodes.

Could the dumped CSV file be put somewhere else (eg cloud storage, Google doc, file in Github) and referenced from there?

@JeniT yeah that would work, there is some other code that looks like it might put stuff on rackspace. I could base off that.


Refactor manual server adding

Right now, when you manually add a server, the input is just written to the registry as-is, no validation is done. What happens is that it sends you back to the HomeScreen, which will validate the registry entry and display the sections if appropriate. If the server is invalid, nothing changes. This has led to confusion on the forums with people saying that they added a server but still only see the preferences icon.
We should validate the server right when it is added (and store the details given back by the XML, such as the friendlyName attribute). This will allow us to kick the user back to the keyboard screen (perhaps with some dialog warning that the validation failed, if doing so won't wipe out what they entered before?) to adjust the input and try again.

Let me know if you're going to be in this code again in the next day or so. I'm not going to be doing anything related to validation per se, but I'm in similar code for myPlex servers and I want to try not to step on each other's changes.


fix: Relates to #487. Update readme with instructions to add missing dependencies

Thanks for the PR. I agree that it's a good idea to add some information about the required system deps to the README, but adding detailed docs for each platform seems superfluous to me. It's better to just link to the appropriate engine's docs - https://github.com/ggez/ggez/blob/a62acaa24/docs/BuildingForEveryPlatform.md


Add C++/WinRT links to IInspectable member functions

Today, the documentation IInspectable's member functions (GetIids, GetRuntimeClassName, and GetTrustLevel) does not mention their C++/WinRT equivalents. These wrappers are not obvious, since they are free functions in C++/WinRT and member functions in raw WinRT, plus they are named differently in C++/WinRT.
This change adds simple links to the C++/WinRT helper.

"See also" should be just a list of links, so I removed the annotations. If we want that kind of explanation, maybe put the link plus annotation in Remarks, or somewhere else in the body of the topic.


IF don't work

I'm trying to made a if in katalon recorder, but it alwatys in the condition, a get the samples and change the values to became false and the testes go in the if

Please edit and fix the screenshot, or upload the test case file.


clean.server missing?

I've got a clean task and in it I have the following:
module.exports = function(grunt) {
    return {
        dist: [
            '.tmp',
            '<%= yeoman.dist %>/*'
        ],
        server: ['.tmp'],
        cq: {
            src: [
                '<%= yeoman.cq %>/css',
                '<%= yeoman.cq %>/images',
                '<%= yeoman.cq %>/js'
            ],
            options: {
                force: true
            }
        },
        hooks: {
            src: ['../.git/hooks/pre-commit'],
            options: {
                force: true
            }
        }
    }
};

load-grunt-config acknowledges the clean task but when i run a task that uses clean:server (or just grunt clean:dist or any other for that matter) I see this:
Running "clean:server" (clean) task
Verifying property clean.server exists in config...ERROR
Any idea why I'm getting this?  Thanks in advance.

I'm seeing this too; could you provide your solution?

I fixed this, it was caused by still having grunt.initConfig in my gruntile


[Feature Request] Consider adding enumerations for glTF sampler filters and wrap modes

cgltf_sampler defines sampler filter and wrap modes using cgltf_int. This is unfortunate because it requires referring to the glTF specification to understand what values are allowed for each property in addition to hardcoding those values into a glTF loading implementation. A better user experience would be to represent those values using a dedicated enum similar to other cgltf enumerations such as cgltf_primitive_type and cgltf_attribute_type. A fix for this should be relatively straightforward and would look something like
// filter and wrap mode values defined at https://registry.khronos.org/glTF/specs/2.0/glTF-2.0.html#reference-sampler
typedef enum cgltf_filter_type {
  cgltf_filter_type_nearest = 9728,
  cgltf_filter_type_linear = 9729,
  cgltf_filter_type_nearest_mipmap_nearest = 9984,
  cgltf_filter_type_linear_mipmap_nearest = 9985,
  cgltf_filter_type_nearest_mipmap_linear = 9986,
  cgltf_filter_type_linear_mipmap_linear = 9987
} cgltf_filter_type;

typedef enum cgltf_wrap_type {
  cgltf_wrap_type_clamp_to_edge = 33071,
  cgltf_wrap_type_mirrored_repeat = 33648,
  cgltf_wrap_type_repeat = 10497,
  cgltf_wrap_type_default = cgltf_wrap_type_repeat
} cgltf_wrap_type;

Makes sense to me, it's the only case in the current API where integers are used instead of enums. Mind contributing a PR?

Gladly! Before I proceed, I would just like to confirm that you’re in alignment with the proposed approach of assigning glTF filter / wrap modes as enumeration values to maintain backward compatibility with implementations that previously relied on cgltf_int? This would diverge from the way that other enumerations are handled within the library, although the end-user experience should remain the same.

Hmm yeah I see. It's... probably fine? Any change to enum would require code that assigns these to change (but I'd expect this to be less frequent, as it only impacts cgltf_write). Using sequential enum values would silently break code like this:
https://github.com/google/filament/blob/main/libs/gltfio/src/GltfEnums.h#L27-L75
... whereas using enum with GL values would keep the code above working, and any issues would manifest as compile time errors, which feels safer. Ideally this probably should have used sequential enums to begin with, but right now changing this to non-sequential enums is the safest change. If this becomes a problem maybe these can be renumbered down the line (which would not break any users who migrate to using enum values).

Similar code from gltfpack: https://github.com/zeux/meshoptimizer/blob/master/gltf/write.cpp#L794-L820 -- this will also work without any changes if an enum with non-sequential values is introduced.
Minor note: cgltf_filter_type should also have an entry cgltf_filter_type_default = 0. This is because the specification does not specify default values for minFilter or magFilter, and when these aren't specified it allows the application to choose:

Client implementations SHOULD follow specified filtering modes. When the latter are undefined, client implementations MAY set their own default texture filtering settings.

Thanks for your patience with getting this out. Here is the PR with the proposed changes.


Request - Allow DNS vs. IP in endpoint config

I'd like to request for the next update to allow for DNS updates to the endpoint.  I set this in my current DSNET WireGuard stuff.  I use dynamic DNS to reach my home lab in case the IP changes.  This application is so awesome.  Thank you!

Thanks for the suggestion, makes total sense and should be fairly easy to change. I'll add this to our backlog and queue it for the next release.


Added Quest International College MBA Section

@vashukarn First stage of verification passed, official domain is quest.edu.np as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@vashukarn Please provide us with an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course. Thank you.

@vashukarn You might miss my previous comment. Please react.

@vashukarn I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for your understanding!

https://quest.edu.np/programs/2
https://quest.edu.np/programs/3
On Sun, 9 Oct 2022 at 09:19, Philip Torchinsky @.***>
wrote:

@vashukarn https://github.com/vashukarn You might miss my previous
comment. Please react.
—
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/15325#issuecomment-1272446014,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALRYPS5TOPBE6NMVQTAOF4TWCI4KRANCNFSM6AAAAAAQ7I735Q
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Vashu Karn
Software Developer
Tech & IT
9845850197
@.***
vashukarn.me
[image: twitter] https://twitter.com/karnvashu
[image: linkedin] https://www.linkedin.com/in/vijay-karn-600ab4137/
[image: instagram] https://www.instagram.com/vashukarn


REQUIRED:   The /explain flag.

With the goal of and 'end user' tool,
Add a flag called /explain that will tell the user in plan English just exactly what the commands they provide will do.
This should let someone - in theory anyway - to be able to take commands and add an /explain flag to receive what they will do without the need of them getting their feet wet in attempting to understand the code.

Needs testing to ensure emits English but the screenshot below should be promissing.

explain is done.  Also it works with file sizes.


Close Side Menu by Tap

How would you implement close slide menu if the menu is already open by tapping outside of menu?

You can reach menuActions on first-level components via this.props.menuActions

@Kureev, Thanks for answering it but that wasn't what I'm looking for. I think I didn't properly explain it.
in your example,

once the menu is opened, I want to tap any where on blue view and I want to close the menu. My Question is how would you do it?

Why was this closed? I'm also looking for this functionality. The view that gets hidden to make room for the menu should have interaction disabled except a tap should close the window. How can this be done?

@marcshilling I'm trying to find a solution for this. Unfortunately I haven't found one yet. @Kureev Do you know how this can be done with a simple example?

Okay, I'll try to explain the problem and purposed solution:
There's an API of component to do open, close and toggle. It's incapsulated into menuActions. Ideal solution for your case is to make menuActions methods available in all child views. The simplest way to do it - use context, but it doesn't work properly yet. So, to solve this issue, I decided to expose API only to first-level components out-of-box, so it means that in my simple example View and Button (first-level components inside SideMenu) would receive menuActions property. If you need to access those methods on N-th nested level, you'll need to pass these prop directly by hands. As soon as context gonna work OK, that solution gonna be replaced by context. For now I don't see any other way to give you access to these functions outside of menu.
@marcshilling @alinz

Ok, my super smart boss @skevy just figured this out...
Your top level component that implements the SideMenu will look something like this, where we subscribe to the SideMenu's onChange event, and update state accordingly:
export class MainScene extends React.Component {
  constructor() {
    super();

    this.state = {
      sideMenuOpen: false
    };
  }

  handleSideMenuChange() {
    this.setState({
      sideMenuOpen: !this.state.sideMenuOpen
    });
  }

  render() {
    return (
      <SideMenu menu={<Menu />} onChange={this.handleSideMenuChange.bind(this)}>
        <MainSceneInner sideMenuOpen={this.state.sideMenuOpen} />
      </SideMenu>
    );
  }
}

Then, in the inner component, we can put a transparent TouchableWithoutFeedback overlay on top of whatever your existing view is (that is only in the hierarchy when the SideMenu is open), which can call this.props.menuActions.close() on press:
class MainSceneInner extends React.Component {
  handleOverlayPress() {
    this.props.menuActions.close();
  }

  render() {
    return (
      <View style={{flex: 1}}>
        <YourViewHere />
        {this.props.sideMenuOpen && <TouchableWithoutFeedback onPress={this.handleOverlayPress.bind(this)}>
          <View style={{ position: 'absolute', top: 0, left: 0, bottom: 0, right: 0, backgroundColor: 'transparent' }} />
        </TouchableWithoutFeedback>}
      </View>
    );
  }
}

Pretty cool, huh? @alinz @Kureev

Yeah, that's perfectly cover the case imo. For more convenient I can also pass current menu state to first-level children (that will allow you avoid using high-order components in this case)

That would be cool. Honestly, this functionality COULD be implemented in react-native-side-menu...so that it would be a prop on side menu that would be, say, touchToClose={true}. If I got that to work and sent a PR, would you consider adding it in?

@skevy I'm always open to suggestions. If you can keep interface clean, I would be happy. Something like this would be nice:
render() {
    return (
      <SideMenu menu={<Menu />} touchToClose={true}>
          ...
      </SideMenu>
    );
}

That's the idea! I'll work on it tonight.

@skevy :+1: for your feature PR
@Kureev :+1: for this amazing library
@marcshilling :+1:  for good example
Thanks guys :D looking forward to this patch!

@skevy @Kureev @marcshilling @alinz checkout #36

Too live issue to be closed

So, after #36 has been merged... Should I close this?

LGTM :+1:

Yup, close away! This is great.


dashboard_client required fields

In CF, if the dashboard_client field is included in the catalog, then we check that the object contains id, secret and redirect_uri. If any of those fields do not exist, we fail broker registration.
However, in the spec, these fields are not required.
Are other platforms using the dashboard_client object? If so, are the fields inside required? I'd like to mark these as required in the spec (or at least think about doing that in the future) to match up with CF's behaviour.

While I have no idea how common of a use case it is, there could be global, static, services that don't require those fields - right?

As in they only require redirect_uri and not id and secret? (That does kinda make sense, especially if there is no authentication being used)

Closing this as this is likely a CF-only issue.


[Gallery] The Gallery doesn't show previews just the napari logo

Maybe this is just due to the build process? But I wanted to note it somewhere.

Opening a page ( first one ) there is no preview there either.
However, I love the contrasty code highlighting:

Looks very snazzy and snappy!

I belive this happens because I am just copying the files over to gh-pages for you folks to see but it does work fine locally. I'm leaving this open to observe later but I don't think it's an actual issue.

Solved


Replacing use of TFT's deprecated dataset_schema.from_feature_spec

Replacing use of TFT's deprecated dataset_schema.from_feature_spec with its replacement schema_utils.schema_from_feature_spec.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

LGTM


Install errors

Hi,
On Ubuntu-14.04-LTS, running Julia-0.4 (git master) I get the following errors while trying to install Conda.jl :
INFO: Building Conda
INFO: Downloading miniconda installer …
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (77) error setting certificate verify locations:
  CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
==========================================================================[ ERROR: Conda ]==========================================================================

LoadError: LoadError: InitError: failed process: Process(`curl -o /home/sva/.julia/v0.4/Conda/deps/usr/installer -L https://repo.continuum.io/miniconda/Miniconda-latest-Linux-x86_64.sh`, ProcessExited(77)) [77]
during initialization of module Conda
while loading /home/sva/.julia/v0.4/Conda/src/Conda.jl, in expression starting on line 349
while loading /home/sva/.julia/v0.4/Conda/deps/build.jl, in expression starting on line 1

====================================================================================================================================================================

==========================================================================[ BUILD ERRORS ]==========================================================================

WARNING: Conda had build errors.

 - packages with build errors remain installed in /home/sva/.julia/v0.4
 - build the package(s) and all dependencies with `Pkg.build("Conda")`
 - build a single package by running its `deps/build.jl` script

====================================================================================================================================================================

julia> Pkg.build("Conda")
INFO: Building Conda
==========================================================================[ ERROR: Conda ]==========================================================================

LoadError: could not spawn `/home/sva/.julia/v0.4/Conda/deps/usr/bin/conda list --json`: no such file or directory (ENOENT)
while loading /home/sva/.julia/v0.4/Conda/deps/build.jl, in expression starting on line 2

====================================================================================================================================================================

==========================================================================[ BUILD ERRORS ]==========================================================================

WARNING: Conda had build errors.

 - packages with build errors remain installed in /home/sva/.julia/v0.4
 - build the package(s) and all dependencies with `Pkg.build("Conda")`
 - build a single package by running its `deps/build.jl` script

====================================================================================================================================================================

julia>

Thanks!

There are two errors here: one from curl
curl: (77) error setting certificate verify locations:
  CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none

And one from Conda:
LoadError: could not spawn `/home/sva/.julia/v0.4/Conda/deps/usr/bin/conda list --json`: no such file or directory (ENOENT)
while loading /home/sva/.julia/v0.4/Conda/deps/build.jl, in expression starting on line 2

The second one should be fixed in the fix-4 branch, but I do not see what to do for the first one. Could you please try to do the following to test the fix?
julia> Pkg.checkout("Conda", "fix-4")
julia> Pkg.build("Conda")
julia> Pkg.test("Conda")
julia> Pkg.free("Conda")

1. Curl error
Tried it again, no luck.
julia> using Conda
INFO: Recompiling stale cache file /home/sva/.julia/lib/v0.4/Compat.ji for module Compat.
INFO: Recompiling stale cache file /home/sva/.julia/lib/v0.4/URIParser.ji for module URIParser.
INFO: Recompiling stale cache file /home/sva/.julia/lib/v0.4/SHA.ji for module SHA.
INFO: Downloading miniconda installer …
curl: (6) Couldn't resolve host 'repo.continuum.io'
ERROR: LoadError: InitError: failed process: Process(curl -o /home/sva/.julia/v0.4/Conda/deps/usr/installer -L https://repo.continuum.io/miniconda/Miniconda-latest-Linux-x86_64.sh, ProcessExited(6)) [6]
2. Fix-4 error
julia> Pkg.checkout("Conda", "fix-4")
INFO: Checking out Conda fix-4...
fatal: Cannot update paths and switch to branch 'fix-4' at the same time.
Did you intend to checkout 'origin/fix-4' which can not be resolved as commit?
ERROR: failed process: Process(git --work-tree=/home/sva/.julia/v0.4/Conda --git-dir=/home/sva/.julia/v0.4/Conda/.git checkout -q -B fix-4 -t origin/fix-4, ProcessExited(128)) [128]
in pipeline_error at process.jl:548
in run at process.jl:524
in anonymous at pkg/entry.jl:192
in transact#393 at pkg/git.jl:97
in _checkout at pkg/entry.jl:190
in checkout at pkg/entry.jl:205
in anonymous at pkg/dir.jl:31
in cd at file.jl:22
in cd at pkg/dir.jl:31

curl: (6) Couldn't resolve host 'repo.continuum.io'

That is the main issue ... Can you access this URL with your web browser?

Fix-4 error

I just realise that Conda was not tested on Linux with Travis. I am activating this, and will try to get it work first.

Yes, I can access the URL on the web (would it help if there was an extra space between the tick at the end of the URL?).
Ok, please announce that (tested on Linux with Travis) somewhere so that I can update later.
Thanks.

Yes, I can access the URL on the web (would it help if there was an extra space between the tick at the end of the URL?).

I'll try to use the http URL instead of the https here. It may help for people behind a firewall.

The Linux build is green! https://travis-ci.org/Luthaf/Conda.jl/builds/78566555
Can you try again with either Pkg.checkout("Conda", "fix-4") of Pkg.checkout("Conda", "origin/fix-4") ? And if any of them work, can you do the following?
julia> cd(Pkg.dir("Conda"))
julia> run(`git fetch origin`)
julia> run(`git checkout fix-4`)

Thanks, it gave similar errors but when I tried it 2-3 times it didnt throw errors, so I assume it works:
julia> run(`git checkout fix-4`)
Already on 'fix-4'
Your branch is up-to-date with 'origin/fix-4'.

julia> using Conda

julia> Pkg.update()
INFO: Updating METADATA...

INFO: Updating Conda...
INFO: Updating DataStructures...
INFO: Computing changes...
INFO: No packages to install, update or remove
Thanks.

Merged in master ! Within a few days you should be able to run Pkg.free("Conda") and use the official release.

A new version have been tagged, you can now run
Pkg.free("Conda")
Pkg.update()

To get it.

On Mon, Sep 7, 2015 at 3:14 PM, Luthaf<EMAIL_ADDRESS>wrote:

Pkg.free("Conda")

Thanks @luthaf
SVAKSHA ॥  http://about.me/svaksha  ॥


Reset Password failure

When using the live version, password recovery is failing for me. I'm in OSX Chrome and visiting http://hackathonstarter.herokuapp.com/forgot
I created an account ~1 month ago and tried to perform a password recovery.

Looks like this was intentional with the SendGrid API keys.

Yes, sorry I ran out of fake accounts, you will need to supply your own account keys.


Cannot set PRAGMA foreign_keys = OFF on migration

As SQLite has some limitations on ALTER TABLE , we usually have to DROP an existing table and create a new one to achieve a simple migration on a table.
Here is the orientations on the oficial docs: http://www.sqlite.org/faq.html:
The basic Steps:
1. CREATE TEMPORARY TABLE t1_backup(a,b);
2. INSERT INTO t1_backup SELECT a,b FROM t1;
3. DROP TABLE t1;
4. CREATE TABLE t1(a,b);
5. INSERT INTO t1 SELECT a,b FROM t1_backup;
6. DROP TABLE t1_backup;

So in my migration script I have tried to do it as described bellow:
  await database.execute("PRAGMA foreign_keys = OFF");
  await database.execute("CREATE TABLE IF NOT EXISTS  temp_table AS SELECT * FROM customer");
  await database.execute("DROP TABLE IF EXISTS customer");
  await database.execute("PRAGMA foreign_keys = ON");

But in fact the first query in my script is not been executed, consequently  throwing an error when the DROP table is called. (787) SQLITE_CONSTRAINT_FOREIGNKEY. It's because my customer table has some references that i need to ignore when I am dropping it
If I manually change the script in auto generated by build_runner database.g.dart   setting the PRAGMA foreign_keys = OFF the migration works fine, but i cannot set PRAGMA foreign_keys = ON after migration.
 Future<sqflite.Database> open(String path, List<Migration> migrations,
      onConfigure: (database) async {
        await database.execute('PRAGMA foreign_keys = OFF');
      },

So the issue is: how can I set PRAGMA foreign_keys OFF AND ON in the migration script?

Hm. I think this stems from the issue that all migration steps are run within a transaction (to be able to roll them back if something fails) and changing this setting is silently ignored within transactions (see https://www.sqlite.org/foreignkeys.html#fk_enable).
I'm not sure how to change this. We could provide an optional parameter which disables the foreign keys for migrations and switches back afterwards, regardless of migration success (seems to be useful imho).
PS: Maybe unrelated, but I'm interested: what are the limitations you're running into with ALTER TABLE?

I was slightly mistaken. The reason for the issue is right, but the transaction is opened within sqflite and not in floor, so we can not fix this in floor.

Thks @mqus .
Look: https://www.sqlite.org/lang_altertable.html

SQLite supports a limited subset of ALTER TABLE. The ALTER TABLE command in SQLite allows the user to rename a table or to add a new column to an existing table. It is not possible to rename a column, remove a column, or add or remove constraints from a table.

Altering a table structure is very limited in SQLite. The official documentation recommend the steps above in my post.

I'm not sure how to change this. We could provide an optional parameter which disables the foreign keys for migrations and switches back afterwards, regardless of migration success (seems to be useful imho).
That would be awesome. If you could give me a clue, may I can try to help on it. Once the official docs suggest set PRAGMA foreign_keys = OFF on migrations with FK restrictions It will become a important feature.

It is not possible to rename a column, remove a column, or add or remove constraints from a table.

Where do you read this?  Is this somthing that changed with past sqlite versions?

The only schema altering commands directly supported by SQLite are the "rename table", "rename column", "add column", "drop column" commands shown above

But I get that editing columns involved in constraints (like primary keys, foreign keys, unique columns etc) is not possible.

In the last versions of SQLite they are improving the procedures for altering tables, however we always have users with older versions of android and consequently SQLite ( KitKat and Jelly Bean have SQLite 3.7.4)
We aren't be able to migrate a drop column in older SQLite versions, also we cannot be able to change a FK or index in current SQLite version. The only security change on a table is add an ordinary column. That limitations of SQLite makes the migration very tricky.
I think there are 2 options:
1: Disable the transaction on migration.
2: Create a method to set PRAGMA foreign_keys = OFF
Otherwise the migration process will be very imitated.

Yes I understand the need.
Your option for a workaround (2.) would be to do the migrations manually by creating @Querys with your actions and manually determining which migrations to run and making sure that it runs before anything else. This is a pain in the ass, yes,  but the only option for now.
as for 1.: This is only possible if floor does not use the onUpgrade hook of sqflite. I have no clue if this is possible or feasible and how to achieve this, since I haven't looked at it.

https://github.com/tekartik/sqflite/issues/624 and https://github.com/tekartik/sqflite/issues/297 have suggestions for solutions useable by floor, all not perfect.

Ok, I have understood your suggestion  workaround (2.).
Tomorrow I'll make a try. I have another idea that consists in create 3 migration scripts instead one:
1st: foreign_keys = OFF,
2nd: make the migration;
3rd: set foreign_keys= ON.
May it work without plain @Query's. I will share my tests on this tomorrow. Thks for the great help today @mqus !

it will not work with 1, 2, 3, or even thousand migrations scripts because each and every one is executed within the same callback which only is executed within the transaction provided by sqflite (see https://github.com/vitusortner/floor/blob/develop/example/lib/database.g.dart#L76).
I noticed that you could try another workaround like described in the sqflite issues:
Edit the generated sources (if that makes sense in your workflow) and disable the foreignkeys in onConfigure and enable them in onOpen, as they are executed before and after the onUpdate step, respectively and get whole database access.

We could improve the workaround by also adding onConfigure to the callbacks you can provide to floor.

Yeap, your suggestion to add onConfigure is much better!
Look: https://github.com/tekartik/sqflite/issues/297#issuecomment-548607348

Maybe you could turn foreign keys off in onConfigure and turn it on later in onOpen (this is called after the transaction is closed)

@mqus  I have tested your commit. However the current floor version  is now depending on flutter above 2.x . Do you have plans to deliver your commit on older floor 0.1X ?

I don't think that we will release another 0.x update, we don't even have a branch for that. But I'm not managing the releases here ;)

You should be able to set it back to ON in the onOpen Callback. I added an example in the mentioned PR:
https://github.com/vitusortner/floor/blob/bc1f945d086fc59f250d996d8c67e5e20ba73e1b/floor/test/integration/database_test.dart#L377-L386

the callback order is roughly:
you call database.open() -> onConfigure -> (onCreate OR onUpgrade OR onDowngrade) -> onOpen ->you get your database instance.
in onCreate, the generated schema is applied beforehand by floor.
in onUpgrade, the migrations are applied beforehand by floor.

@mqus  I appreciated so much your help! About 0.1.x version today I have made my tests merging your code into 0.1.x. It's not easy to run it on older versions, a tons of older dependencies needed to match with flutter up2.x.  Better update my project to 2x... it's a painful job unfortunately
About the next release of floor do you have an idea when that commit will enter in production?

@mqus Do you know if there is a branch of floor related to published 0.19.1 (pub.dev)?

I have done merge of your branch onconfigure-callback on floor 0.19.1. and finally I get this to work including
I think it could be good to have a branch with this feature in previews version of floor compatible with

I have done merge of your branch onconfigure-callback with floor 0.19.1. and finally I get this to work including floor_generator.
I think it could be nice to have a branch with this feature in previews version of floor compatible with flutter 1.2.x.  If you agree I will make a PR


Select multiple ocurrences is broken

Issue Type: Bug
I select one text in the editor, and press ctrl+d to select some ocurrences. But when i press ctrl+shift+directional key to select all the word, the selection disappears. I disabled all extensions but it is still happening.
VS Code version: Code 1.60.1 (83bd43bc519d15e50c4272c6cf5c1479df196a4d, 2021-09-10T17:07:10.714Z)
OS version: Windows_NT x64 10.0.19041
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (12 x 2592)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.84GB (3.68GB free)

Process Argv
--crash-reporter-id 4166fa10-798c-484a-b453-40ce766216f0

Screen Reader
no

VM
0%

Extensions: none

Please create two selections (e.g. by using ctrl+d) first. Could you please try the following:

Run the command Developer: Toggle Keyboard Shortcuts Troubleshooting
This will activate logging of dispatched keyboard shortcuts and will open an output panel with the corresponding log file.
Press exactly the keybinding you desire. (ctrl+shift+right)
check what VS Code detects and what command is invoked.

If you are having trouble understanding the output, please feel free to paste here and I can try to help.

Ok, thanks for the response.
This is the output of the shortcuts log:
[2021-09-27 09:36:23.524] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [ctrl], code: ControlLeft, keyCode: 17, key: Control [2021-09-27 09:36:23.524] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [ctrl], code: ControlLeft, keyCode: 5 ('Ctrl') [2021-09-27 09:36:23.524] [renderer1] [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase. [2021-09-27 09:36:23.771] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [ctrl], code: KeyD, keyCode: 68, key: d [2021-09-27 09:36:23.771] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [ctrl], code: KeyD, keyCode: 34 ('D') [2021-09-27 09:36:23.772] [renderer1] [info] [KeybindingService]: | Resolving ctrl+D [2021-09-27 09:36:23.772] [renderer1] [info] [KeybindingService]: \ From 1 keybinding entries, matched editor.action.addSelectionToNextFindMatch, when: editorFocus, source: built-in. [2021-09-27 09:36:23.913] [renderer1] [info] [KeybindingService]: + Storing single modifier for possible chord ctrl. [2021-09-27 09:36:24.225] [renderer1] [info] [KeybindingService]: + Clearing single modifier due to 300ms elapsed. [2021-09-27 09:36:26.662] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [ctrl], code: ControlLeft, keyCode: 17, key: Control [2021-09-27 09:36:26.662] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [ctrl], code: ControlLeft, keyCode: 5 ('Ctrl') [2021-09-27 09:36:26.663] [renderer1] [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase. [2021-09-27 09:36:26.683] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [ctrl,shift], code: ShiftLeft, keyCode: 16, key: Shift [2021-09-27 09:36:26.684] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [ctrl,shift], code: ShiftLeft, keyCode: 4 ('Shift') [2021-09-27 09:36:26.685] [renderer1] [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase. [2021-09-27 09:36:26.831] [renderer1] [info] [KeybindingService]: / Received  keydown event - modifiers: [ctrl,shift], code: ArrowRight, keyCode: 39, key: ArrowRight [2021-09-27 09:36:26.832] [renderer1] [info] [KeybindingService]: | Converted keydown event - modifiers: [ctrl,shift], code: ArrowRight, keyCode: 17 ('RightArrow') [2021-09-27 09:36:26.833] [renderer1] [info] [KeybindingService]: | Resolving ctrl+shift+RightArrow [2021-09-27 09:36:26.833] [renderer1] [info] [KeybindingService]: \ From 1 keybinding entries, no when clauses matched the context. [2021-09-27 09:36:27.010] [renderer1] [info] [KeybindingService]: + Storing single modifier for possible chord shift. [2021-09-27 09:36:27.317] [renderer1] [info] [KeybindingService]: + Clearing single modifier due to 300ms elapsed.
I'm gonna try to find out what is happening.

I tried on my other computer, and it's firing the event cursorWordEndRightSelect.
But it's not firing on my current computer. May it be because some weeks ago i tried the accesibility functions on Windows? But now it's disabled and is still not working.

Ok. I needed to disable it on vscode, not only on windows. Now it's working again.
But when someone activates the accessibility options there should be some notice about the changes it carries.
And mayle some nottice on the keybord shortcuts window, to know which modifiers are active.
Has been dificult to find where was the problem.
Thanks for the support. Greetings.


Nullable fields produce '"nullable": true' in a oneOf

I've been using your serverless-openapi-documenter and I think the root cause is in here.
When converting something of the form:
"foo": {
  "title": "foo",
  "type": [
    "string",
    "null"
  ]
}

the converted output is
"foo": {
  "title": "foo",
  "oneOf": [
    {
      "type": "string"
    },
    {
      "nullable": true
    }
  ]
}

However, I don't think that is valid. (It certainly gives errors when I try to use the generated open api file, e.g. in postman)
I think it needs to be either:
"foo": {
  "title": "foo",
  "type": "string",
  "nullable": true
}

or
"foo": {
  "title": "foo",
  "oneOf": [
    {
      "type": "string"
    },
    {
      "type": "null"
    }
  ]
}

with the former looking slightly neater. Both work correctly when I manually update my generated open api file.
I can see convertNull in Converter.js appears to be making the transform, but don't know if it is as easy as just changing its return value.

Thank you so much for bringing this up, and sorry you're facing this issue.  I'm actually in the middle of rewriting this library to be a little better tested and to have a better structure, as well as try and do more transformations where possible of JSON schema keywords that aren't in draft-04 and the OpenAPI 3.0.X subset.
I think you're right, it needs to output as:
"foo": {
  "title": "foo",
  "type": "string",
  "nullable": true
}

or at least adding "nullable": true to each type in the array and removing the 'null' type from the array.
I don't believe "type": "null" is valid OpenAPI JSON.
If i can get a fix out later today, I will.  it shouldn't be too hard.  I am hoping to have the new version of the library out in a few weeks too.  If you wanted to try and fix, it'll be the convertTypeArrays function you need to change.
Apologies for this, i'll do my best to get it fixed and up on the serverless-openapi-documenter library ASAP.

No problem - I think the idea of using the serverless.yml & serverless.doc.yml to generate a comprehensive OpenAPI file, which is then actively shared and used is an excellent one. (Similarly, using the OpenAPI file to set the endpoint documentation seems vastly better than the bizarre mechanism AWS uses, though I have not attempted to actually merge the OpenAPI file with the AWS one.) I'm amazed the AWS support is generally quite weak - still draft-04.
In practice, I maintained a manually curated OpenAPI mirroring changes from the generated one. (I also needed to do the same with the auto-generated draft-07 JsonSchema files which serverless-openapi-documenter uses as part of its input - I had to "flatten" them by removing the very top level of reference & definition. I haven't raised that as an issue on serverless-openapi-documenter as I don't have a good enough understanding to know if I'm doing something wrong. I also don't have the time right now to educate myself properly, and I'm not working in this whole area any more - I can raise it if it is something you think might be relevant.)
Thanks for keeping all of this going btw - again, I'm surprised it isn't used much more widely!

Hey @OxonianCambion I think I should have a rather big rewrite out today for this which should fix the issue, though possibly introduce new ones :/

I had to "flatten" them by removing the very top level of reference & definition

I'd be interested to hear more about this.  Unfortunately OpenAPI 3.0.X only allows for schema 04 (much like AWS) and doesn't like definitions, however this library combined with serverless-openapi-documenter should be dereferencing and flattening the JSON schema for you.  The only thing is, if your $ref is behind a gated resource, you need to provide a way for the de-referencer a way to get access to that resource, which is documented in serverless-openapi-documenter, though perhaps I need to explain it better.
Please raise any issues/questions, whether it's a code issue or a lack of documentation (which might cause a lack of understanding).  I realise serverless-openapi-documenter is still missing some key things like authorisation.  I hope to rewrite/expand that library over the xmas period, but don't quote me.


docs(api): Edit Kleat API documentation for Bitbucket artifact config.

@dorbin I think you'll need to run make proto to generate the protos, which is why CI is failing.


[doc] Sort command line options and environment variables alphabetically in -h output and the man page

Fixes #2141.

Codecov Report

Merging #2174 (bb60145) into master (f20c2e9) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #2174   +/-   ##
=======================================
  Coverage   86.31%   86.31%
=======================================
  Files          53       53
  Lines        9557     9557
=======================================
  Hits         8249     8249
  Misses       1308     1308

Impacted Files
Coverage Δ

reframe/frontend/cli.py
76.31% <100.00%> (ø)

reframe/utility/osext.py
84.71% <0.00%> (ø)

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 f20c2e9...bb60145. Read the comment docs.


Haproxy: Mount config dir as read only

There is no good reason for this container to be modifying anything in
/etc/haproxy (or /etc/caasp/haproxy as seen on the host). Remove it's
ability to do so.

This will probably fail CI as the container entrypoint is currently doing this:
sed -Ei 's/^\s*daemon$//' $CONFIG


Missing M5 instances types for EC2

There are no M5 instance types defined in @pulumi/aws/ec2/instanceType.d.ts however they are supported as per EC2's docs: https://aws.amazon.com/ec2/instance-types/

We should bring these enums up to date with current EC2 offerings.
Note that in the meantime - you can pass any string you want and cast <any>”m5.large”.

We should bring these enums up to date with current EC2 offerings.
Note that in the meantime - you can pass any string you want and cast <any>”m5.large”.

I tried this but it failed:
// Create the Kubernetes cluster and all associated artifacts and resources
const cluster = new eks.Cluster(environment+"-eks-cluster", {
    vpcId             : config.require("vpc-id"),
    subnetIds         : vpcSubnetIds,
    instanceType      : "m5.large",
    nodePublicKey     : config.require("worker-ssh-key"),
    nodeRootVolumeSize: 250,
    desiredCapacity   : 3,
    maxSize           : 10,
    minSize           : 1,
    nodeUserData      : userData,
});

Can you paste an example that corrects it?

The list of instances can be programatically accessed and parsed for automated updates (with a little jq magic?):
curl https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonRDS/current/index.json
as per this: https://aws.amazon.com/about-aws/whats-new/2015/12/announcing-aws-price-list-api-programmatic-access-to-aws-prices/


caches: add a cache for building just the runtime on Windows

This allows configuration of a build for just the runtime/SDK components
rather than a complete toolchain.  It allows for more effective
iteration when working on just the runtime aspect of the toolchain.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please smoke test

CC: @shahmishal


Improved source date support

Instead of tracking user changes, use a diff tool to determine what lines have changed to rebuild the source dates.
https://github.com/micnil/vscode-diff

I wonder what the concept is for this. What will be diffed against what? If you have a clear idea how this would work and how it would be a definitive improvement, by all means give it a try. I have to say I have my doubts. I don't think any diff algorithm, no matter how sophisticated, is going to capture what source line dates in SEU capture. In fact, I see any diff-based scheme as basically a step toward ignoring dates (and just using Git) rather than preserving them. But you have exceeded expectations and proved people wrong plenty of times before; maybe this will be one of those times.

Some progress:

  /**
   * @param {string} alias
   * @param {vscode.TextDocument} currentDoc
   */
  static calcNewSourceDates(alias, currentDoc) {
    const baseDates = allSourceDates[alias].slice();
    const oldSource = baseSource[alias];

    const eol = (currentDoc.eol === vscode.EndOfLine.LF ? `\n` : `\r\n`);

    const diffComputer = new DiffComputer(oldSource.split(eol), currentDoc.getText().split(eol), diffOptions);
    const diff = diffComputer.computeDiff();

    const currentDate = this.currentStamp();

    diff.changes.forEach(change => {
      const startIndex = change.modifiedStartLineNumber - 1;
      const removedLines = (change.originalEndLineNumber === 0 ? 0 : (change.modifiedEndLineNumber - change.modifiedStartLineNumber + 1));
      const changedLines = (change.modifiedEndLineNumber - change.modifiedStartLineNumber) + 1;
      baseDates.splice(startIndex, 0, ...Array(changedLines).fill(currentDate));
    });

    return baseDates;
  }

@jkyeung If the PR gets approved, I would feel more comfy with enabling source dates by default in the future I think.


CreateObject() with IssueCustomField's doesn't work (seems missing in XML)

Hi,
thanks for the great work. I use the following code:
            TimeEntry t = new TimeEntry
            {
                Comments = "test",
                Hours = hours,
                SpentOn = DateTime.Now,
                Issue = new IdentifiableName {Id = ticket.Id}
            };
            IssueCustomField c = new IssueCustomField();
            c.Id = 32;
            c.Multiple = false;
            c.Name = "test";
            c.Values = new List<CustomFieldValue>();
            c.Values.Add(new CustomFieldValue{Info ="test"});

            t.CustomFields = new List<IssueCustomField>();
            t.CustomFields.Add(c);
            t.Activity = new IdentifiableName{Id = activity.Id};
            var entry = Redmine.CreateObject(t);

That results in the following XML (using t.ToXml()):
<time_entry>
<issue_id>22896</issue_id><spent_on>2016-03-03</spent_on><hours>15</hours><activity_id>10</activity_id><comments>test</comments>
</time_entry>

The CustomFields are missing and the request does not work, because one of the missing fields is required. Posting the XML manually, adding the XML as follows works:
<time_entry>
<issue_id>22896</issue_id><spent_on>2016-03-03</spent_on><hours>15</hours><activity_id>10</activity_id><comments>test</comments>
	<custom_fields type="array">
		<custom_field id="32" name="test">
			<value>test</value>
		</custom_field>
	</custom_fields>
</time_entry>

Update: It works with JSON.

solved.


Master

Tutorial for Digital Center of Excellence

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


hide API keys with dotenv

Must protect API keys in Node with environment variables

starting on this issue - we don't really have API keys but we do have config settings that we want to hide with dotenv

Just tested this and @TheCoaxial  got it working because he is awesome! Muchas gracias!


Fix typo in package description

Small nit I picked up whilst reading the package description on MELPA:

conventional line feed characters (U+000C) are output between pages

Obviously, this should say form feed, as indicated by the code point. I assume this was a simple typo.

Good catch, thanks!

No, thank you for the awesome package! (I actually wished for an easier way to peruse the x86_64 PDF from an editor… 😀 and then I found this)


Better source for Becker

This driveway point source appears to be better. The BASENAME field only has 11 records with nulls, and ADDRESS has 15, some of which otherwise appear to have real data. So this field mapping looks like an upgrade over using ADDRESS with a postfixed_street function.

I think I may have an even better source, researching it for the null geometry I found in the REST endpoint. The better source also has the UNIT field.

@mmdolbow Looks good, are you happy with this?

Yup, it's the best we can do. There's actually about 13 records with null geometries, but several of those don't even have any address info. I've notified them about all of the records, so hopefully they'll fix 'em and we'll see that in future updates. Definitely an upgrade over the former approach though, IMHO.

Sounds good, thx for tracking this down!


[kythe] missing references to existing type of type declaration

Input test case
//- @foo defines/binding Foo
typedef int foo;

//- @bar defines/binding Bar
//- @foo ref Foo
typedef foo bar;

Describe what is wrong or missing
In the above test case, the reference to Foo is missing.
In general, the type being referenced could be anything.
More examples:
typedef foo_pkg::bar_t baz;  // package qualified, expect references on both `foo_pkg` and `bar_t`
typedef foo_class#(123)::bar_t baz;  // class (parameterized) qualified, expect references on `foo_class` and `bar_t`

FWIW, this is covered in the symbol table based implementation.
Tests around here:
https://cs.opensource.google/verible/verible/+/master:verilog/analysis/symbol_table_test.cc;drc=ffba3629b4b3df299a23b739eba72034e83c641e;l=6917


Migrate main project to netstandard

Closes #47
This doesn’t do anything fancy like multi-targeting. It only changes the core library to be a netstandard lib instead of a PCL. This was done on purpose to keep changes at a minimum.

I'll have a look. But anyway, it requires changes in the nuget package as well.

Sorry for the delay. All test projects are now broken. I'll try to fix them but would be awesome if you could include those changes in your PR.

Good wrapper! Will you plan to update a project to support .Net Standard with last changes from Tesseract?