webpack 5 has troubles to load vue-loader

Bug report

What is the current behavior?
With a very simple config
const { VueLoaderPlugin } = require('vue-loader')

module.exports = {
    entry: {
        caller: './src/caller.js',
        clients: './src/clients.js'
    },
    output: {
        filename: '[name].js',
        path: __dirname + '/public'
    },
    module: {
        rules: [
            {
                test: /\.vue$/,
                exclude: /node_modules/,
                loader: 'vue-loader'
            },
            {
                test: /\.js$/,
                exclude: /node_modules/,
                loader: 'babel-loader'
            },
            {
                test: /\.css$/i,
                use: ['style-loader', 'css-loader'],
            },
            { test: /\.(png|woff|woff2|eot|ttf|svg)$/, use: ['url-loader?limit=100000'] },
        ]
    },
    plugins: [
        new VueLoaderPlugin(),
    ],
};

I run webpack and it fails with
[webpack-cli] TypeError: The 'compilation' argument must be an instance of Compilation
    at Function.getCompilationHooks (/usr/home/tarkhil/client_base/node_modules/webpack/lib/NormalModule.js:171:10)
    at /usr/home/tarkhil/client_base/node_modules/vue-loader/lib/plugin-webpack5.js:36:70
    at Hook.eval [as call] (eval at create (/usr/local/lib/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:19:10), <anonymous>:100:1)
    at Hook.CALL_DELEGATE [as _call] (/usr/local/lib/node_modules/webpack/node_modules/tapable/lib/Hook.js:14:14)
    at Compiler.newCompilation (/usr/local/lib/node_modules/webpack/lib/Compiler.js:943:26)
    at /usr/local/lib/node_modules/webpack/lib/Compiler.js:984:29
    at Hook.eval [as callAsync] (eval at create (/usr/local/lib/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (/usr/local/lib/node_modules/webpack/node_modules/tapable/lib/Hook.js:18:14)
    at Compiler.compile (/usr/local/lib/node_modules/webpack/lib/Compiler.js:979:28)
    at /usr/local/lib/node_modules/webpack/lib/Compiler.js:470:12
    at Compiler.readRecords (/usr/local/lib/node_modules/webpack/lib/Compiler.js:821:11)
    at /usr/local/lib/node_modules/webpack/lib/Compiler.js:467:11
    at Hook.eval [as callAsync] (eval at create (/usr/local/lib/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (/usr/local/lib/node_modules/webpack/node_modules/tapable/lib/Hook.js:18:14)
    at /usr/local/lib/node_modules/webpack/lib/Compiler.js:464:20
    at Hook.eval [as callAsync] (eval at create (/usr/local/lib/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:15:1)

Tried vue-loader 14.2.4
[webpack-cli] TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
    at new NodeError (node:internal/errors:278:15)
    at validateString (node:internal/validators:123:11)
    at Object.basename (node:path:1156:5)
    at new module.exports (/usr/home/tarkhil/client_base/node_modules/vue-loader/lib/loader.js:32:25)
    at Object.<anonymous> (/usr/home/tarkhil/client_base/webpack.config.js:33:9)
    at Module._compile (/usr/local/lib/node_modules/webpack-cli/node_modules/v8-compile-cache/v8-compile-cache.js:192:30)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1131:10)
    at Module.load (node:internal/modules/cjs/loader:967:32)
    at Function.Module._load (node:internal/modules/cjs/loader:807:14)
    at Module.require (node:internal/modules/cjs/loader:991:19) {
  code: 'ERR_INVALID_ARG_TYPE'
}

package.json is simple as well
{
  "name": "client_base",
  "version": "1.0.0",
  "description": "",
  "main": "caller-b.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC",
  "dependencies": {
    "query-string": "^6.9.0",
    "vue": "^2.6.12",
    "vuejs-auto-complete": "^0.9.0"
  },
  "devDependencies": {
    "@babel/core": "^7.12.10",
    "babel-loader": "^8.2.2",
    "babel-preset-env": "^1.7.0",
    "css-loader": "^5.0.1",
    "html-webpack-plugin": "^4.5.1",
    "path": "^0.12.7",
    "postcss": "^8.2.3",
    "style-loader": "^2.0.0",
    "url-loader": "^4.1.1",
    "vue-loader": "^15.9.6",
    "vue-template-compiler": "^2.6.12",
    "webpack": "^5.11.1"
  }
}

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
Surely I was expecting webpack to run.

Other relevant information:
webpack version:
webpack-cli 4.2.0
webpack 5.4.0
Node.js version: v15.3.0
Operating System: FreeBSD 12.1-RELEASE-p10
Additional tools:

Well, total removal of all globally installed node-modules and reinstallation of global webpack and webpack-cli saved. I can only wonder if it is possible without such a great purge, but just reinstalling of webpack did not help

Well, total removal of all globally installed node-modules and reinstallation of global webpack and webpack-cli saved. I can only wonder if it is possible without such a great purge, but just reinstalling of webpack did not help


fix regression due to compiler refactor

General items:

[ ] I have updated the relevant documentation files under docs/
[ ] My code follows the:

[ ] Google Java style guide (for .java files)
[ ] Google JavaScript style guide (for .js files)

[x] ant tests passes on my machine

If your code changes how something works on the device (i.e., it affects the companion):

[ ] I branched from ucr
[ ] My pull request has ucr as the base

Further, if you've changed the blocks language or another user-facing designer/blocks API (added a SimpleProperty, etc.):

[ ] I have updated the corresponding version number in YaVersion.java
[ ] I have updated the corresponding upgrader in YoungAndroidFormUpgrader.java (components only)
[ ] I have updated the corresponding entries in versioning.js

For all other changes:

[x] I branched from master
[x] My pull request has master as the base

What does this PR accomplish?

Description

Fixes # .

Resolves # .

https://github.com/mit-cml/appinventor-sources/blob/ec1e463c9b7f819d00bd38b6774c9664d58fc80f/appinventor/buildserver/src/com/google/appinventor/buildserver/context/AndroidPaths.java#L29
In this line, the drawable dir is set relative to the build dir, but before the refactor, it was relative to build/res dir.

@pavi2410 What are the conditions to trigger this? Do you have a test project?

@pavi2410 What are the conditions to trigger this? Do you have a test project?

I am working on integrating the compiler refactor to Kodular codebase and this regressions were caught when building the companion app. I verified the changes with the App Inventor codebase before and after the refactor and thought to create the PR. I do not have minimal reproducible example.


request: output logging just to console

In next release, can we have the ability to log only to console without having to write a log file also? Thanks!

Sure, I'll add an option for that!

I was also looking for this, thanks @shiyuechengineer !

I was also looking for this, thanks @shiyuechengineer !

This feature has now been added. Thank you for the suggestion guys!


thoughts on reorganizing payload weights

This one ended up being tricky. Just eded up being a missing bracket [ for the array of json objects. It should be fixed and live now. Thanks


Test valid semver

Use https://github.com/npm/node-semver

Fixed in https://github.com/taataa/taaspace/commit/ac4a227ccc2bb7c120a6ad853a4183cb00062a59


Readiness probe fails when creating a Ray serve

Search before asking

[X] I searched the issues and found no similar issues.

KubeRay Component
ray-operator
What happened + What you expected to happen
When trying to create Ray serve using this yaml ray-operator/config/samples/ray-service.autoscaler.yaml, the worker pod never becomes ready
Reproduction script
Run yaml ray-operator/config/samples/ray-service.autoscaler.yaml, and watch the worker status
Anything else
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Actually, it is still a bug. It assumes that a ray cluster with serve support is already populated with the application, which might not be true. The following yaml is perfectly valid:
- apiVersion: ray.io/v1
  kind: RayCluster
  metadata:
    annotations:
      ray.io/creation-timestamp: 2024-01-11 10:34:56.38417242 +0000 UTC
      ray.io/enable-serve-service: "true"
    creationTimestamp: "2024-01-11T10:34:56Z"
    generation: 1
    labels:
      app.kubernetes.io/managed-by: kuberay-apiserver
      app.kubernetes.io/name: kuberay
      ray.io/cluster-name: test-cluster
      ray.io/environment: DEV
      ray.io/user: boris
      ray.io/version: ""
    name: test-cluster
    namespace: default
    resourceVersion: "3088"
    uid: e1ebb6f9-f951-4853-a934-ced65f02adac
  spec:
    headGroupSpec:
      rayStartParams:
        dashboard-agent-listen-port: "52365"
        dashboard-host: <IP_ADDRESS>
        metrics-export-port: "8080"
      serviceType: ClusterIP
      template:
        metadata:
          annotations:
            ray.io/compute-image: rayproject/ray:2.9.0-py310
            ray.io/compute-template: default-template
        spec:
          containers:
          - env:
            - name: MY_POD_IP
              valueFrom:
                fieldRef:
                  fieldPath: status.podIP
            image: rayproject/ray:2.9.0-py310
            name: ray-head
            ports:
            - containerPort: 6379
              name: redis
              protocol: TCP
            - containerPort: 10001
              name: head
              protocol: TCP
            - containerPort: 8265
              name: dashboard
              protocol: TCP
            - containerPort: 8080
              name: metrics
              protocol: TCP
            - containerPort: 52365
              name: dashboard-agent
              protocol: TCP
            - containerPort: 8000
              name: serve
              protocol: TCP
            resources:
              limits:
                cpu: "2"
                memory: 4Gi
              requests:
                cpu: "2"
                memory: 4Gi
    workerGroupSpecs:
    - groupName: small-wg
      maxReplicas: 5
      minReplicas: 1
      rayStartParams:
        node-ip-address: $MY_POD_IP
      replicas: 1
      scaleStrategy: {}
      template:
        metadata:
          annotations:
            ray.io/compute-image: rayproject/ray:2.9.0-py310
            ray.io/compute-template: default-template
        spec:
          containers:
          - env:
            - name: RAY_DISABLE_DOCKER_CPU_WARNING
              value: "1"
            - name: TYPE
              value: worker
            - name: CPU_REQUEST
              valueFrom:
                resourceFieldRef:
                  containerName: ray-worker
                  divisor: "0"
                  resource: requests.cpu
            - name: CPU_LIMITS
              valueFrom:
                resourceFieldRef:
                  containerName: ray-worker
                  divisor: "0"
                  resource: limits.cpu
            - name: MEMORY_REQUESTS
              valueFrom:
                resourceFieldRef:
                  containerName: ray-worker
                  divisor: "0"
                  resource: requests.cpu
            - name: MEMORY_LIMITS
              valueFrom:
                resourceFieldRef:
                  containerName: ray-worker
                  divisor: "0"
                  resource: limits.cpu
            - name: MY_POD_NAME
              valueFrom:
                fieldRef:
                  fieldPath: metadata.name
            - name: MY_POD_IP
              valueFrom:
                fieldRef:
                  fieldPath: status.podIP
            image: rayproject/ray:2.9.0-py310
            lifecycle:
              preStop:
                exec:
                  command:
                  - /bin/sh
                  - -c
                  - ray stop
            name: ray-worker
            ports:
            - containerPort: 80
              protocol: TCP
            resources:
              limits:
                cpu: "2"
                memory: 4Gi
              requests:
                cpu: "2"
                memory: 4Gi

It creates a cluster with serve annotation without any applications. Readiness probe in this case is guaranteed to fail

The failure of the readiness probe is an expected behavior. We rely on this failure to remove "not ready for serving" worker Pod's endpoint from the serve service.

@Yicheng-Lu-llll it is not. The cluster never becomes ready in the first place.

Another issue with this readiness check is that it not very reliable. I have seen worker pods never going ready even when the RayServe is created

Actually,before the moving ray serve check to readiness,Kuberay also checks serve health and the http request is exactly the same. The only change is know Pod will be in unready status once serve health check fails.


Is this faster then chrome?

Does this run faster then chrome because it's a stripped down version? Have any benchmarks been done?

Probably not, because it is still normal chromium in the background.
I will definitely investigate that, when version 1.0 is ready.


Build Date API

 Build-Date / git tag über API call

Pull Request Test Coverage Report for Build 849115144

3 of 5 (60.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 82.702%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

services/src/server.rs
3
5
60.0%

Totals

Change from base Build 842634288:
-0.1%

Covered Lines:
16906

Relevant Lines:
20442

💛  - Coveralls

 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.


Adding post method support with patch

IMO this change doesn't align with the http standards and I don't see how this is useful.
For transient changeset, a separate branch may be used.
Hence closing this pr. Feel free to reopen if you feel otherwise


Inheritance over composition for BaseXGateway-ILxBridge relationship

#35

On hold for now, as commented on the PR. Both approaches have merits with impacts mostly on the long term (maintainability), no strong reason to choose either way right now.

Done as part of #36


Get the actual File from the input.

Hi all,
I hope you are well. I've been trying to get the actual file so I can send it to the backend and store the image, but failed to do it.
Though the acceptFiles in function onDrop(acceptFiles, rejectReasons) seems only return an array of File objects, they turned out to be a normal object that I can't retrieve the file in the backend. The only things I receive in the backend are the path, name, and a few other props in the object.
I was wanting to do something equivalent to the following:
var formData = new FormData();
var imagefile = document.querySelector('#file');
formData.append("image", imagefile.files[0]);
axios.post('upload_file', formData, {
    headers: {
      'Content-Type': 'multipart/form-data'
    }
})

Side note: I'm using Laravel 8 in the backend and $request->hasFile('image') returns false axios.post the acceptFiles.

Hi, you can try to use formData in onDrop(acceptFiles) callback, like:

function onDrop(acceptFiles) {
  const formData = new FormData();
  const file = acceptFiles[0]
  formData.append("image", imagefile.files[0]);
  axios.post('upload_file', formData, {
      headers: {
        'Content-Type': 'multipart/form-data'
      }
  })
}

@Yaxian Thanks so much for this. Works like a charm. I've done some tweaks to save multiple files at one request but your suggestion got me in the right direction! Will try to submit a PR to update the doc a little bit. Just so some people's hours can be saved!


Inconsistent CIS v2 CR names

On master-head - commit id: ed2749841

Deploy CIS v2 app on a cluster in dashboard
The CIS CRs names seem inconsistent

Can we have them as -

- ClusterScanBenchmarkVersions
- ClusterScanProfiles
- ClusterScanReports
- ClusterScans

Because if these CRs are Starred then there will be no Header To indicate that these are related to CIS/cluster scans

I asked for these to be remapped because I'd rather have types that are concise and not-redundant shown for the primary way people see them, in the product-specific UI.  Or in the regular nav tree, under their Apigroup.
Even among the built-in standard k8s types, several names are ambiguous or exist in more than one API group.  So the problem with starred items being ambiguous exists irrespective of CIS.
Starring is an optional and relatively obscure feature, so my thinking is if a user has chosen to star a type they probably did it for a reason and will know which type it meant to them.
(ClusterScanReports could be remapped too, but hasn't been just because they aren't shown as a type in the CIS UI)

For now, let's not change this and if it becomes confusing to end users later, we can always update it.


docs: OpenVSX Registry listing to easy find

CLA is signed ✅

@guw Should i send an another empty commit to re-trigger salesforce-cla CI

@Siddhant-K-code close and re-open did the trick.


Replace pylint and black with ruff

Ruff is a faster alternative to pylint and black and it replaces both tools. We should replace those tools with ruff in our pre-commit configuration.
Link to ruff documentation: https://github.com/astral-sh/ruff

Please assign me the issue. I'd like to work on this.

Go for it @0scvr

Go for it @0scvr

Thank you. Do you need ruff to just check for issues or fix them as well ?

Go for it @0scvr

Thank you. Do you need ruff to just check for issues or fix them as well ?

fix would be nice. right now black is being used for autofixing issues. it would be nice to be able to autofix as many things as possible

Go for it @0scvr

Thank you. Do you need ruff to just check for issues or fix them as well ?

fix would be nice. right now black is being used for autofixing issues. it would be nice to be able to autofix as many things as possible

Ok, I can do that. Lastly, am I correct in assuming the typings folder should be excluded from ruff checks ?

Go for it @0scvr

Thank you. Do you need ruff to just check for issues or fix them as well ?

fix would be nice. right now black is being used for autofixing issues. it would be nice to be able to autofix as many things as possible

Ok, I can do that. Lastly, am I correct in assuming the typings folder should be excluded from ruff checks ?

yes, absolutely. those are not manually written files


Pie Chart Configuration:

Enable Ability to change Pie Chart, Doughnut type, Hole Color
if you are interested

this pull request change too much of my own project configuration. Can you just submit three code file and pull again?


Handling of QUOTATION MARK characters appears to have changed in 7.3.0

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
The following statement was working under 7.2.
& svn.exe co "https://svnrepo.myco.com/db/trunk/$_`"`
GRAVE ACCENT characters not showing up correctly. Sorry for the picture.

After installing 7.3.0, it produces:
svn: E170000: Illegal repository URL '%22https://svnrepo.myco.com/db/trunk/Scripts%22
Expected behavior
Working copy is checked out.

Actual behavior
Working copy is not checked out.

Error details
No response
Environment data
PSVersion                      7.3.0
PSEdition                      Core
GitCommitId                    7.3.0
OS                             Microsoft Windows 10.0.19042
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
No response

Have noticed this as well; it broke some of our CI scripts that call out to all sorts of executables. Have also experienced slightly different behaviors between windows and Linux depending on the target application (for example ef migration bundles) and sometimes different if I splat arguments.
So far only when invoking applications and not with commandlets
I intend on opening issues in a few repos that offer argument completer scripts (Flux, helm, kustomize) as their powershell variants are all broken since 7.3 (with a simple fix)... Will link here once I do.
I checked release notes and didn't see mention of this behavior.

v7.3 introduced a breaking change with respect to the - previously fundamentally broken - handling of (embedded) " chars. in arguments passed to external programs.
To make the previous workarounds that build on the broken behavior work, you must (temporarily) set $PSNativeCommandArgumentPassing to 'Legacy'.
For a summary of the consequence of the breaking change, see this comment.

As an aside re formatting, @Liturgist:
You can double the enclosing ` in order to (in-line) format code that has embedded `
E.g.,
`` a`b ``

renders as a`b

@mklement0, is it possible to write a script that will run unchanged on 7.3+ and 7.2- without embedding $PSNativeCommandArgumentPassing`? Is that the only way?
Trying to install 7.2.7 fails because. "A newer version of PowerShell is already installed"  How can I install the earlier version in order to test?

@Liturgist, unfortunately, I don't think that's possible: if you want existing code to run without (other) modifications on both 7.2- / Windows PowerShell and 7.3+, you'll need to deal with $PSNativeCommandArgumentPassing.
Going forward and/or if modifying old code is possible, for cross-edition / cross-version code you could consider using the ie function from my Native module (Install-Module Native), which works in both editions and all PS Core versions, irrespective of the effective value of $PSNativeCommandArgumentPassing.
Additionally, it incorporates the proposed-in-vain accommodations for batch files and other high-profile CLIs, so that no workarounds are needed in most cases: just prepend ie to your external-program calls.

@Liturgist, as for installing an older version alongside the most recent one: I haven't personally tried, but it looks like installing via a specific version's .zip package may do the trick.


Failure to unlock a collection

I have got a bug downstream about a crash caused by calling Collection::unlock
Zbus(MethodError("org.freedesktop.DBus.Error.InvalidArgs", Some("Invalid properties"), Msg { type: Error, sender: ":1.11", reply-serial: 4, body: Signature: [
	s (115),
] }))', src/application.rs:290:14

Got the same error in a different application. Seems like its less an error but rather just an unclear error message - adding "login" keyring fixed it, of course, but could use a clearer error message.


Dynamo Key requests with Ranges

Dynamo queries that take a primary key need to support more than one, because you can have primary keys based on hashes and ranges.

Actually on second thought, can't we do this already? @jschoch doesn't the following work?
Dynamo.create_table("Users", [email: :hash, age: :range], [email: :string, age: :number], 1, 1)
Dynamo.get_item("Users", [email<EMAIL_ADDRESS>age: 123])

Primary key spec is @type primary_key :: [{atom, binary}] | %{atom => binary} which allows for more than one key.

yes, this appears to be working now


Update working-at-mattermost.rst

Updated remaining holidays for 2016 and added holidays for 2017

+1

Sorry just adding the WIP label - I think IT was thinking about this still, or looking for a standard link we can use for the holidays.

Sorry, I was expressing myself earlier that I think our doc PR review process is not as good as it could be overall.
It's not specific to this PR. I'll bring it up in platform meeting.


[Proposal]: Simplify/improve the terminology around listener management

Describe your issue or feature request
Currently, in VerneMQ CLI, the management of the listeners seems somewhat confusing. You can "stop" a listener but it doesn't really stop it since you cannot start the same Address/Port combination again because it will return{already_started, Pid} even if the vmq_admin listeners show command presents the listener as "stopped". In that case, one needs to restart the listener to really start it again.,
Describe the solution you'd like
As a simplified, less confusing terminology, I propose that vmq_admin listeners stop ... really stops the listener, killing all the sessions, and removing the listener from the show output, and that way start can work again. Also, remove the restart command and replace it with:

vmq_admin listeners suspend ...: Does not kill connections but suspends any new connections.
vmq_admin listeners resume ...: Starts receiving connections again on a suspended listener, do nothing on others.

Probably remove the vmq_admin listeners delete ... command too since stop will signify this.
Describe alternatives you've considered
No response
Environment
No response
Add any other context, code samples or screenshots about the issue report here.
No response
Code of Conduct

[X] I agree to follow the VerneMQ's Code of Conduct

The terminology was chosen a long time ago... I agree it lacks clarity.
suspend/resume is great. start/stop will work, maybe start/terminate too to avoid redefining stop.
After that it's more of a documentation issue. I don't think the commands are widely used in a scripted fashion (breaking things).  In any case, better command terminology helps new users. So, adding my +1. Thanks for the idea, @codeadict !

:point_right: Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
:point_right: Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

Indeed, start/terminate is even cleaner.

I have a branch for this , will open PR in the next few day


Add readme.md, work with empty messages & private chats

Add suitable help text to new readme.md file.
Add test for empty message to avoid crash in case of simple mention of bot name
Use new send_reply function to simplify send_message logic & enable private chats
Hash on list of emails in private chats to allow application to private chats

Automated message from Dropbox CLA bot
@neiljp, it looks like you've already signed the Dropbox CLA. Thanks!

Merged, thanks @neiljp!


N44 : OpenCombat (#1317)

OpenCombat news for https://github.com/rust-gamedev/rust-gamedev.github.io/issues/1317 :)

Thx!


use no_filter = True by default.

not using the filter is better choice to avoid mistake and better serve as linker and not postprocessor.

Yeah that's a good idea, merged.


Figure out process for updating pre-registered BioSamples with additional metadata

We have a set of BioSamples that we need to update with additional metadata. This ticket is to track my progress on how I would go about doing that. Investigations will occur before I have any real information to add to the biosamples entries.
Currently working on:

get list of the biosamples ids that were provided to the Sanger
investigate how to get relevant authority to update these
figure out whether these were automatically linked to the EGA study/dataset/sample when the EGA submission was made or if we have to figure out how to do this

So far I have found out the following:
The a text file of the BioSamples IDs that were created can be found in the working directory for this ticket.
The IDs were created directly in BioSamples and so must be edited directly in biosamples, the documentation for their API is here: https://www.ebi.ac.uk/biosamples/docs/references/api/submit#_submission_minimal_fields
The samples were added using the AAP domain subs.team-34 which I have now been added to so I can update the samples.
These samples are both in dev and prod so I can test submissions in dev bearing in mind that the dev database gets replaced with prod data at the end of each week.

Using the biosamples python wrapper I have managed to turn a fairly minimal metadata spreadsheet into linked biosamples with references.
See here for a donor that has different libraries linked and a viral sample linked
https://wwwdev.ebi.ac.uk/biosamples/samples/SAMEA7060447
And here for a pool with several donors
https://wwwdev.ebi.ac.uk/biosamples/samples/SAMEA7060442
Commands are in spreadsheet-to-biosamples notebook

received spreadsheet with metadata from Elena that assigns biosamples IDs to samples and donors.
Now I am trying to link up with EGA accessions and am trying to chase up the Dataset or Study id so I can do a query like this:
https://ega-archive.org/metadata/v2/samples?queryBy=dataset&queryId=EGAD00001005516


BangleJS2: Barometer does not show any value

The barometer just shows the background image, error in console:

Uncaught Error: Unhandled promise rejection: Error: Cannot read property 'pressure' of undefined

Does it need a call to Bangle.setBarometerPower(true) first?

also see the discussion at http://forum.espruino.com/conversations/372900

added a workaround for now so the app works with existing firmware


feat: dependent resource context + my sql e2e test improvements

Added access to managed dependent resources, not sure if that is there the map in the context makes sense anymore.

Added access to managed dependent resources, not sure if that is there the map in the context makes sense anymore. @metacosm

What do you thin about this ? @metacosm

Added access to managed dependent resources, not sure if that is there the map in the context makes sense anymore. @metacosm

What do you thin about this ? @metacosm

We can remove it for now and re-add it if needed.

oki, will create a separate PR, others are fixed.


Can’t promote user via API [Nukkit]

PromotionResult#wasSuccess was true, but my player never got promoted. Here’s my code
public static PormotionResult rankup(Player player) {
     Track track = luckPermsAPI.getTrack(getCurrentConfig().getString("rankuptrack"));
     return track.promote(luckPermsAPI.getUser(player.getUniqueId()), luckPermsAPI.getContectForPlayer(player));
}

rankuptrack was set in the config properly, and if I do /lp user <user> promote rankuptrack in console, then it will promote them properly.

There are a number of typos in your code - it won't even compile.
Anyway, I suspect the reason it doesn't work is because you're not (it appears) making a call to save the user after promoting them.
See: https://github.com/lucko/LuckPerms/wiki/Developer-API:-Usage#saving-changes

The type wouldn't be there in the original code because my iPad wouldn't let me copy/paste however I didn't know I had to save the changes.


Bundle for browsers

Will it work?

The plan:

dist/index.js: ES module without dependencies bundled. For node, for example.
dist/electionguard.mjs: ES module with polyfills and bundled dependencies. For ESM-supporting browsers.
dist/electionguard.js: UMD module with polyfills and bundled dependencies.
(?) dist/mod.ts: For deno.

I'm also thinking about removing the index.ts exports to stuff in core and to ballot/decrypt.ts since IMO those should be internal to the library.

dist/index.js is as described above. It comes to around 65 KiB (minified). dist/electionguard.mjs and dist/electionguard.js are close to 220 KiB each. I'll look into building for deno later.
dist/electionguard.mjs usage:
<script type="module">
    import {ManifestParty, bigIntContext4096} from './electionguard.mjs';
    console.log(ManifestParty.simpleParty(bigIntContext4096(), 'example'))
</script>

dist/electionguard.js usage:
<script src="./electionguard.js"></script>
<!-- ... -->
<script>
    console.log(eg.ManifestParty.simpleParty(eg.bigIntContext4096(), 'example'))
</script>


Implement JWT Auth

Implemented JWT Auth that should work well with the backend by Randy.
Added src/utilities/env.js to have a single point to define the API server. As this changes, it would be apt for all contributors that make fetch requests to refer to the server via ${API_BASE_URL}/endpoint in their code. An example of this is shown in login.jsx and signup.jsx.
All code dealing with Auth is found in src/utilities/auth.js
To get the jwt token for use in the Authorization header, use getJwtToken(), that should be available in src/utilities/auth.js

Link test is failing, take a look

Issues corrected as per latest PR


Fixing user bug

Fixes redirect while selecting a user

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/541 (JID-2333)

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/541 (JID-2335)

@blueorangutan package

@davidjumani a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian :heavy_check_mark:archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/541 (JID-2336)

@Pearl1594 Could you review ?


project cleanup

Thanks for terminating those .yy files
How come mb_side1 and mb_side2 need macros? Aren't those included as constants in GMS2.3.3?

yes ! vestigial. will amend

Cool! Thank you Alynne


Feature/refactor

I've separated out the core components of the project for readability and understandability.

A p2p module
an http server
The blockchain

and also separated out their individual components.
I've also refactored the code a bit for readability, such as removing nested ifs, and nested functions, and introduced linting in order to spot errors and possible bugs.
I'd probably like to start retrofitting tests if this PR gets approved.
Cheers,
Antony

I actually don't like this approach because the main code is created with a clean Functional Programming approach for learning purposes. If you wanted to improve the previous code you should have embraced the same approach with Higher Order Functions, currying, composing, etc. Putting everything inside classes like a Java code doesn't make it necessarily better.

As I described in more detail in #2  , I intend to leave the main version of naivechain as a single 200 lines of code file.


Design System: Add Unit + Integer variants to input

Context
Building out the design system. These updates for the input are necessary in the editor.
Summary
Adds the Unit and Numeric input variants as described in #6414 and this comment: https://github.com/google/web-stories-wp/pull/6355#issuecomment-780749936
Relevant Technical Choices
The Input component is meant to be a 'presentational' component. However, the functionality of 'reverting to a previous value' makes this component more of a 'container' component.
I am keeping the Input as presentational as possible, but wrapping it in a container component to add functionality that the 'numeric' input will need (saving old inputs, only calling onChange when the value should be "submitted", etc.). Other changes:

allowNegative is redundant when paired with max and min. Removed it so that we use only max/min. If there is a bound, we can specify it there.
I kept the API similar to the old input rather than using type="numeric" for the input. I would prefer to use type="numeric" but there was already old logic written that I used instead of making a brand new component
created this without setting event listeners on the window. This should be more performant and relies on only "react"
added a hook to manage the Numeric input's state. This also makes testing easier.

To-do
After this PR is merged I'd like to make one final PR that merges Input and Numeric into one component. That component will decide which input type to use based on a type prop.

if type="numeric" - render the <Numeric /> input
else render the base <Input />

User-facing changes

none
Testing Instructions

Visit storybook. Design System -> Input -> Numeric
Test the following scenarios:

can enter any value while typing
blurring the field will trigger validation. If there is a valid number, the number will remain.

if the value is invalid and the previous value was valid, leave the valid number
if the value is invalid and the previous value was also invalid, leave a new valid number

isFloat=true will allow for float values as well as integers
arrow keys: ⬆  and ⬇  changes the value 1 up or down
arrow keys + alt: ⬆  and ⬇  changes the value by 0.1 up or down (if isFloat is true)
unit should only be visible when the field is not focused
field cannot be empty unless allowEmpty is true

All of these values can be configured in the knobs section in storybook
QA

[x] This is a non-user-facing change and requires no QA

UAT

[ ] UAT should use the same steps as above.

This PR can be tested by following these steps:
Visit storybook. Design System -> Input -> Numeric
Test the following scenarios:

can enter any value while typing
blurring the field will trigger validation. If there is a valid number, the number will remain.

if the value is invalid and the previous value was valid, leave the valid number
if the value is invalid and the previous value was also invalid, leave a new valid number

isFloat=true will allow for float values as well as integers
arrow keys: ⬆  and ⬇  changes the value 1 up or down
arrow keys + alt: ⬆  and ⬇  changes the value by 0.1 up or down (if isFloat is true)
unit should only be visible when the field is not focused
field cannot be empty unless allowEmpty is true

All of these values can be configured in the knobs section in storybook

Numeric input

Unit

Minimum

Maximum

ArrowUp and ArrowDown

Esc key press

Reviews
Does this PR have a security-related impact?
no
Does this PR change what data or activity we track or use?
no
Does this PR have a legal-related impact?
no
Checklist

[x] This PR addresses an existing issue and I have linked this PR to it in ZenHub
[x] I have tested this code to the best of my abilities
[x] I have verified accessibility to the best of my abilities (docs)
[x] I have verified i18n and l10n (translation, right-to-left layout) to the best of my abilities
[x] This PR contains automated tests (unit, integration, and/or e2e) to verify the code works as intended (docs)
[x] I have added documentation where necessary
[x] I have added a matching Type: XYZ label to the PR

Fixes #6414

Note: when testing this and changing the max and min knobs in storybook you will see this error:

When testing this, value was set the whole time and didn't get removed. I don't think this component is uncontrolled at all, but if you see something strange lmk.
I think the above error is a storybook 🐛

The only issue I can find is here - if you type something illegal and blur or press enter (both are routed through this callback), the input is left as "null", where it instead should revert to the original text ("last known valid state"). Otherwise, you can get his confusing output of nullms:

Great catch @BrittanyIRL and @barklund. Thanks for such a thorough review, and for reviewing such a large pr. I greatly appreciate it.
I fixed the bug! It now reverts to the original value if the new value is invalid.


out of memory for continuing pretraining llama3-8B

I am trying to use the framework to continue pretraining llama3-8B. I have converted the HF checkpoint into nanotron format and the generated tokens seem reasonable.
I use the following setting to train the model but I got the OOO with 8 GPUs. I tried HF accelerate with deepspeed zero-1 and flash-attention and it worked well previously:
model:
ddp_bucket_cap_mb: 25
dtype: bfloat16
init_method:
std: 0.025
make_vocab_size_divisible_by: 1
model_config:
bos_token_id: 128000
eos_token_id: 128001
hidden_act: silu
hidden_size: 4096
initializer_range: 0.02
intermediate_size: 14336
is_llama_config: true
max_position_embeddings: 8192
num_attention_heads: 32
num_hidden_layers: 32
num_key_value_heads: 8
pad_token_id: null
pretraining_tp: 1
rms_norm_eps: 1.0e-05
rope_scaling: null
tie_word_embeddings: false
use_cache: true
vocab_size: 128256
optimizer:
accumulate_grad_in_fp32: true
clip_grad: 1.0
learning_rate_scheduler:
learning_rate: 8.0e-07
lr_decay_starting_step: null
lr_decay_steps: 100
lr_decay_style: cosine
lr_warmup_steps: 100
lr_warmup_style: linear
min_decay_lr: 1.0e-05
optimizer_factory:
adam_beta1: 0.9
adam_beta2: 0.999
adam_eps: 1.0e-08
name: adamW
torch_adam_is_fused: true
weight_decay: 0.1
zero_stage: 1
parallelism:
dp: 8
expert_parallel_size: 1
pp: 1
pp_engine: 1f1b
tp: 1
tp_linear_async_communication: true
tp_mode: REDUCE_SCATTER
profiler: null
tokenizer:
tokenizer_max_length: null
tokenizer_name_or_path: meta-llama/Meta-Llama-3-8B
tokenizer_revision: null
tokens:
batch_accumulation_per_replica: 1
limit_test_batches: 0
limit_val_batches: 0
micro_batch_size: 1
sequence_length: 8192
train_steps: 200
val_check_interval: -1

Hi,
Thanks for your question. Here is my solution:
general:
  benchmark_csv_path: null
  consumed_train_samples: null
  ignore_sanity_checks: true
  project: test
  run: llama
  seed: 42
  step: 1
lighteval: null
logging:
  iteration_step_info_interval: 1
  log_level: info
  log_level_replica: info
model:
  ddp_bucket_cap_mb: 25
  dtype: bfloat16
  init_method:
    std: 0.2
  make_vocab_size_divisible_by: 1
  model_config:
    bos_token_id: 128000
    eos_token_id: 128001
    hidden_act: silu
    hidden_size: 4096
    initializer_range: 0.02
    intermediate_size: 14336
    is_llama_config: true
    max_position_embeddings: 8192
    num_attention_heads: 32
    num_hidden_layers: 32
    num_key_value_heads: 8
    pad_token_id: null
    pretraining_tp: 1
    rms_norm_eps: 1.0e-05
    rope_scaling: null
    tie_word_embeddings: false
    use_cache: true
    vocab_size: 128256
optimizer:
  accumulate_grad_in_fp32: true
  clip_grad: 1.0
  learning_rate_scheduler:
    learning_rate: 0.0003
    lr_decay_starting_step: null
    lr_decay_steps: 198
    lr_decay_style: cosine
    lr_warmup_steps: 2
    lr_warmup_style: linear
    min_decay_lr: 1.0e-05
  optimizer_factory:
    adam_beta1: 0.9
    adam_beta2: 0.95
    adam_eps: 1.0e-08
    name: adamW
    torch_adam_is_fused: true
  weight_decay: 0.01
  zero_stage: 0
parallelism:
  dp: 2
  expert_parallel_size: 1
  pp: 1
  pp_engine: 1f1b
  tp: 4
  tp_linear_async_communication: true
  tp_mode: REDUCE_SCATTER
profiler: null
tokenizer:
  tokenizer_max_length: null
  tokenizer_name_or_path: meta-llama/Meta-Llama-3-8B
  tokenizer_revision: null
tokens:
  batch_accumulation_per_replica: 32
  limit_test_batches: 0
  limit_val_batches: 0
  micro_batch_size: 1
  sequence_length: 8192
  train_steps: 30
  val_check_interval: -1

You can also try tp=8, dp=1.
Currently, we don't have good support for fine-tuning models converted from transformers library. So you have also to
1 Set these if conditions to false for the first time.
https://github.com/huggingface/nanotron/blob/6629dfaed368c45cbb171ca545d56fae2d927b94/src/nanotron/trainer.py#L191-L213
2 Set theta = 500000.0 for RotaryEmbedding

Thanks for the reply. Actually, my question is that when I use nanotron with pure DP (dp=8,pp=1,tp=1), I got OOO even if I use micro-batch-size=1. However, I did not get OOO when I use accelerate + deepspeed ZERO1 with the similar settings.
What would be the possible reason that nanotron uses more memory for pure DP? Also, if I want to implement that, where I should look into?

If my understanding is correct, ZERO1 is not pure DP, that's why you got the error.
Some links:
https://huggingface.co/transformers/v4.12.5/parallelism.html
https://blog.csdn.net/baoyan2015/article/details/136820078

Greetings! To share updates about the Hugging Face Nanotron with
individuals who might not be familiar with the technical details
(affectionately referred to as 'muggles'), you could consider the following
approach:

Simplify the Language: Use non-technical language to explain the
purpose and benefits of the Nanotron update. For example, you could say
it's a tool that helps machines understand and generate human language more
efficiently.

Use Analogies: Analogies can be powerful in explaining complex
concepts. You might compare the Nanotron to a library that's been
reorganized to help people find books faster.

Highlight the Benefits: Focus on how the update can impact their
interaction with AI. For instance, mention improvements in response times
or accuracy in language understanding.

Regarding the ZERO1 error, it seems like there might be a misunderstanding.
ZeRO-1 is a type of optimizer used in distributed training that helps
manage memory more efficiently. It's not directly related to differential
privacy (DP), which is about protecting user data. The error you
encountered could be due to a configuration issue or a mismatch in the
expected environment setup. Without more context, it's difficult to provide
a precise solution, but ensuring compatibility with the system requirements
and following the installation instructions carefully are good first steps.
For more detailed information, you can refer to the Nanotron GitHub
repository and the latest release notes for updates and
instructions on how to use the new features. If you're encountering
specific errors, checking the issues section on the repository might
provide insights or solutions from other users who faced similar problems.
Remember, when sharing with 'muggles', the key is to keep it relatable and
focus on the practical aspects that affect their experience.
Source: Conversation with Bing, 5/6/2024
(1) GitHub - huggingface/nanotron: Minimalistic large language model 3D
.... https://github.com/huggingface/nanotron.
(2) Releases · huggingface/nanotron · GitHub.
https://github.com/huggingface/nanotron/releases.
(3) GitHub - huggingface/nanotron: Minimalistic large language model 3D
.... https://github.com/huggingface/nanotron.
(4) nanotron (Nanotron Research) - Hugging Face.
https://huggingface.co/nanotron.
(5) regression - Lack of fit and Pure error - Cross Validated.
https://stats.stackexchange.com/questions/99989/lack-of-fit-and-pure-error/129482
.
(6) Static Zero | Automation & Control Engineering Forum.
https://control.com/forums/threads/static-zero.40643/.
(7) 9 common Dyson air purifier problems (and how to fix them).
https://housefresh.com/dyson-air-purifier-problems/.
(8) undefined. https://crfm.stanford.edu/2023/09/14/doremi.
On Mon, May 6, 2024, 12:06 PM zzhhjjj @.***> wrote:

If my understanding is correct, ZERO1 is not pure DP, that's why you got
the error.
Some links:
https://huggingface.co/transformers/v4.12.5/parallelism.html
https://blog.csdn.net/baoyan2015/article/details/136820078
—
Reply to this email directly, view it on GitHub
https://github.com/huggingface/nanotron/issues/161#issuecomment-2096716209,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADAN35OPGXSU3AZCQNJLFSLZA7ID5AVCNFSM6AAAAABHGAVZC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJWG4YTMMRQHE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Ah. Sorry for the confusion.
I compared nanotron with setting (dp=8, pp=1, tp=1, zero=1) on 8 GPUs and Deepspeed Zero1 on 8GPUs with tp&pp.
Actually, I found that when I use the deepspeed zero1, I also set gradient_checkpointing=True. Does nanotron support gradient_checkpointing to save memory?

Sorry for the confusion.
I was comparing nanotron with the setting "dp=8,pp=1,tp=1,zero=1" with deepspeed zero1 without pp&tp.
I actually found that in deepspeed, I set the gradient_checkpointing=True to save memory during training but I did not find any notes about gradient_checkpoint in nanotron.
In the doc, I found the "activation checkpointing" with a decorator "@checkpoint_method(attr_name="do_checkpoint")". I applied it on LLaMAModel and I got the following error:
"File "/home/kezhen/Documents/nanotron/src/nanotron/parallel/pipeline_parallel/engine.py", line 56, in forward
[rank3]:     assert output["loss"].requires_grad"
I have the following question:

Does nanotron support gradient_checkpointing right now?
Is the activation checkpointing similar with gradient checkpointing?
What is the correct way to use it?

Hello! It seems you're inquiring about gradient checkpointing in Nanotron
and how it compares to activation checkpointing. Here's some information
that might help:

Does Nanotron support gradient_checkpointing right now?

As of the latest information available, there was an open issue on the
Nanotron GitHub repository discussing the support for gradient
checkpointing⁴. This suggests that it might not be supported yet, or the
feature is still under development.

Is the activation checkpointing similar to gradient checkpointing?

Yes, activation checkpointing is similar to gradient checkpointing.
Both techniques aim to reduce memory usage during the training of deep
neural networks. They work by storing only a subset of the intermediate
activations and recomputing the rest during the backward pass¹².

What is the correct way to use it?

The correct way to use activation checkpointing in Nanotron would
typically involve using the provided decorator
@.***_method(attr_name="do_checkpoint")` on the methods of your
model that you want to checkpoint. The error you encountered suggests there
might be an issue with the loss tensor requiring a gradient. Without more
context, it's hard to provide a precise solution, but you might want to
ensure that the loss computation is part of the computational graph and
that gradients are being tracked correctly.

For the specific error you're facing, it would be beneficial to check the
Nanotron documentation or reach out to the Nanotron community for more
detailed guidance, as the implementation details can vary and might require
a deeper look into your code and settings.
I hope this helps, and if you have further questions or need more
assistance, feel free to ask!
Source: Conversation with Bing, 5/6/2024
(1) [Features] support gradient checkpointing for memory saving #99 -
GitHub. https://github.com/huggingface/nanotron/issues/99.
(2) Performance and Scalability: How To Fit a Bigger Model and Train It
Faster. https://huggingface.co/docs/transformers/v4.18.0/en/performance.
(3) Gradient Checkpoints — PyTorch Training Performance Guide - GitHub
Pages.
https://residentmario.github.io/pytorch-training-performance-guide/gradient-checkpoints.html
.
(4) Performance and Scalability: How To Fit a Bigger Model and Train It
....
https://huggingface.co/transformers/v4.11.3/performance.html?highlight=gradient_checkpointing
.
(5) GitHub - cybertronai/gradient-checkpointing: Make huge neural nets fit
.... https://github.com/cybertronai/gradient-checkpointing.
(6) Manual NanoTron P/R - Advantage Controls.
https://www.advantagecontrols.com/downloads/pdf/M-Nano_P-R.pdf.
(7) Manual NanoTron - es. I.
https://cms.esi.info/Media/documents/Advan_NanoTronman_ML.pdf.
(8) ADVANTAGE CONTROLS NANOTRON MANUAL Pdf Download | ManualsLib.
https://www.manualslib.com/manual/2319800/Advantage-Controls-Nanotron.html.
On Mon, May 6, 2024, 2:07 PM Kezhen Chen @.***> wrote:

Sorry for the confusion.
I was comparing nanotron with the setting "dp=8,pp=1,tp=1,zero=1" with
deepspeed zero1 without pp&tp.
I actually found that in deepspeed, I set the gradient_checkpointing=True
to save memory during training but I did not find any notes about
gradient_checkpoint in nanotron.
In the doc, I found the "activation checkpointing" with a decorator
@.***_method(attr_name="do_checkpoint")". I applied it on LLaMAModel
and I got the following error:
"File
"/home/kezhen/Documents/nanotron/src/nanotron/parallel/pipeline_parallel/engine.py",
line 56, in forward
[rank3]: assert output["loss"].requires_grad"
I have the following question:

Does nanotron support gradient_checkpointing right now?
Is the activation checkpointing similar with gradient checkpointing?
What is the correct way to use it?

—
Reply to this email directly, view it on GitHub
https://github.com/huggingface/nanotron/issues/161#issuecomment-2096920167,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADAN35J2VFCT7C3SNOARKITZA7WKTAVCNFSM6AAAAABHGAVZC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJWHEZDAMJWG4
.
You are receiving this because you commented.Message ID:
@.***>

Hello,
1,2 Yes, @checkpoint_method is the same as gradient checkpointing.
3 I didn't have enough time to check the code, but you can set use_reentrant=False to fix the error. Your observation is correct, even then there is still an OOO error, I will check the reason later when I have time.
Thanks a lot for your questions.


Different images for dark mode?

I would like to use different images based on light or dark mode as they don't always work with such extremely different color schemes. Or I would like to set the website permanently to dark or light mode. Is this possible?

Hi Yes you would first need to implement dark mode. Its possible but no plans to add it myself. You will need to make a PR or rely on the community.
Alternatively I have several premium themes that ship with Dark mode available at www.zerostatic.io


fix: Add brackets to querystring to clarify it's array (#1672)

If length of array is 1, it was being recognized as a string, not an array.

AS-IS:
{ colors: ['black', 'mustard'] } -> colors=black&colors=mustard
{ colors: ['black'] } -> colors=black
TO-BE:
{ colors: ['black', 'mustard'] } -> colors[]=black&colors[]=mustard
{ colors: ['black'] } -> colors[]=black

Added qs dependency for this fix.
Checklist

[x] I have ensured my pull request is not behind the main or master branch of the original repository.
[x] I have rebased all commits where necessary so that reviewing this pull request can be done without having to merge it first.
[ ] I have written a commit message that passes commitlint linting.
[x] I have ensured that my code changes pass linting tests.
[x] I have ensured that my code changes pass unit tests.
[x] I have described my pull request and the reasons for code changes along with context if necessary.

Is anyone willing to merge this PR?
I don't have write access so that I cannot merge this.

Please can we not introduce qs to Koa... it's one of the things I wanted to escape from Express. The behavior is very unusual compared to my experience with other web frameworks and makes working with the query object a pain. Any query value could be either a string, an array of strings, or an object, and these arrays/objects can also be nested. So all query values accesses need to be overly defensive, or just call .toString() and accept that sometimes you might be getting [object Object] as a value.
The "bug" that this is fixing doesn't really seem like a problem to me. I think it's reasonable to assume that ctx.request.query will never have any values that are single-value arrays, and that you should always expect that it could be either a string or an array of strings. As far as I can tell, the only situation that this is "fixing" is if you are modifying the request's query object in middleware, setting its value to something that Node's built-in querystring parser would never produce, and you want the rest of your middleware to be able to access ctx.request.query while assuming certain values are an array without checking. Adding non-standard syntax to the query string to support this edge case feels like a hack.

qs was intentionally not added to koa because it's very opinionated and has both performance and security issues. you can make your own plugin that defines ctx.qs or something. we should actually be moving to URLSearchParams


thanks for information

yes I seen many.inf files, I observed those lines inside.inf file

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

ID: e7924445-8edc-c398-3f95-3f1e905d4efd
Version Independent ID: c3609591-99fc-0e53-72d3-4944977f659f
Content: Differentiating the SKU for Windows 7 Display Drivers - Windows drivers
Content Source: windows-driver-docs-pr/display/differentiating-the-sku-for-windows-7-display-drivers.md
Product: windows-hardware
GitHub Login: @nabazan-microsoft
Microsoft Alias: windowsdriverdev

@RAJU2529 I'm glad you found this article useful!


Improve fit of drink cards

Currently the drink cards will basically fill the screen horizontally, want a more reasonable fit with respect to aspect ratio of the cards. Also need to make look better on mobile.

@Arctic8471 lol i went ahead and assigned this to u but lemme know if u don't feel like it and i'll put it back in the backlog

Improved with recent update


I don't find cordova.js file

I want to determine the device's network connection state. I have install cordova-plugin-network-information
But I don't find cordova.js

It should be added when you install cordova platform.
e.g.:
\platforms\browser\platform_www\cordova.js
\node_modules\cordova-browser\cordova-lib\cordova.js


fix: ACNA-1810 - update Template Registry API usage for OR category clauses

How Has This Been Tested?

npm test
manual test

Types of changes

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[X] I have signed the Adobe Open Source CLA.
[X] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[X] All new and existing tests passed.

Lgtm!


Non-existent agenda file  [R]emove from list or [A]bort?

Whenever org-journal creates a new file for entry I get the following (error) messages. I'm using EMACS 26.1 on ArchLinux.
(New file)
No previous journal entry before this one
Non-existent agenda file ~/Dropbox/org/journal/20190325.  [R]emove from list or [A]bort?
Saving file /home/name/Dropbox/org/journal/20190325...
Wrote /home/name/Dropbox/org/journal/20190325
I also just noticed that the first entry after file creation does not include "** TIME" but all subsequent entry attempts do.
CONFIG:
(use-package org-journal
:ensure t
:after org
:custom
(org-journal-dir "~/Dropbox/org/journal"))
(setq org-journal-file-type 'weekly)
(setq org-journal-enable-agenda-integration t)

Not sure if this is related, but org-mode TODO keywords not recognized unless journal file ending is set to .org

Is this fixed in Master? Many thanks in advance!

@anthrolisp Yes!

These are the changes https://github.com/bastibe/org-journal/commit/64183868033dd1aebe08b8722cb9ffd72b14198c.

Thank you!
On Wed, Mar 27, 2019 at 1:35 PM Christian Schwarzgruber <
<EMAIL_ADDRESS>wrote:

These are the changes 6418386
https://github.com/bastibe/org-journal/commit/64183868033dd1aebe08b8722cb9ffd72b14198c
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bastibe/org-journal/issues/152#issuecomment-477271125,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AjAs_4u9PKjYqnLSJtKRFUlR6Rji__Rbks5va6vcgaJpZM4cMdQ-
.

Welcome!


Fix(curriculum): Fix Typo in Build an RPG Game

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #48809

Changed the below string:

This code would change the element assigned to the div variable to have the text Hello World.

to:

This code would change the element assigned to the info variable to have the text Hello World.

Hey @Sriparno08
Thank you for opening this pull request.
Related issue is limited only to the first time contributors to this repository. Because of that we are going to close this PR.
Thank you and happy coding.

Okay, @gikf 👍


[Deployment] Week of 2019-09-02

[ ] INT

[x] Merge NuGetGallery: https://github.com/NuGet/NuGetGallery/pull/7508
[x] Merge NuGet.Jobs: https://github.com/NuGet/NuGet.Jobs/pull/810
[x] Gallery 3026413
[x] Validation.PackageSigning.RevalidateCertificate: Release

For https://github.com/NuGet/NuGetGallery/issues/7482

[x] Validation.Orchestrator: Release

For https://github.com/NuGet/NuGetGallery/issues/7489

[ ] Validation.SymbolsOrchestrator: Release

For https://github.com/NuGet/NuGetGallery/issues/7489

[ ] Validation.PackageSigning.ValidateCertificate: Release

For https://github.com/NuGet/NuGetGallery/issues/7482

[ ] Validation.PackageSigning.ProcessSignature: Release

For https://github.com/NuGet/NuGetGallery/issues/7482

[ ] PROD

[x] Gallery 3026413
[x] Validation.PackageSigning.RevalidateCertificate: Release
[x] Validation.Orchestrator: Release (This replaced INT's release)
[ ] Validation.SymbolsOrchestrator: Release
[ ] Validation.PackageSigning.ValidateCertificate: Release
[ ] Validation.PackageSigning.ProcessSignature: Release

Changes
Gallery

Embedded Icon validation;
Using POST everywhere for state changing requests;
Self-service account delete messaging.

I will combine this with the deployment work item for this week, because it is very difficult to work with multiple deployment items with this many deployments to do.


[Backport] SQL: Fix post-aggregator naming logic for sort-project.

Backport of #6250 to 0.12.3.

Had to fix a test-- repushed.


Architecture Diagram improvements

CA Advisor runs inside docker containers, but I don't believe it's correct to show the Kubelet and Proxy processes as inside the docker box on the minion.
Also, shouldn't the internet->firewall-> really load balance across minion proxies instead of be connected to just one SPOF minion, treating that connection more like a logical connection across all minion proxies?

We should just review the diagram and make it correctly reflect the state of 1.0.


fix(rpc): reduce Ethereum rpc API and improve websocket API

Description

Keep only the namespaces available on regular Ethereum rpcs. Disable eth_sendTransaction, eth_sign and eth_signTypedData
Set message read limit to 32 MB

To test:

Start smoke tests
Check APIs

Before:
curl -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"rpc_modules","id":1}' http://localhost:9545
{"jsonrpc":"2.0","id":1,"result":{"debug":"1.0","eth":"1.0","miner":"1.0","net":"1.0","personal":"1.0","rpc":"1.0","txpool":"1.0","web3":"1.0"}}

After
curl -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"rpc_modules","id":1}' http://localhost:9545
{"jsonrpc":"2.0","id":1,"result":{"eth":"1.0","net":"1.0","rpc":"1.0","web3":"1.0"}}

curl -X POST --data '{"jsonrpc":"2.0","method":"personal_sign","params":["0x48656c6c6f", "0x604BB0f27A24374f1a784C458aFB9210CaAA2EDA", "password"],"id":1}' -H "Content-Type: application/json" http://localhost:9545/
{"jsonrpc":"2.0","id":1,"error":{"code":-32601,"message":"the method personal_sign does not exist/is not available"}}

curl -X POST --data '{"jsonrpc":"2.0","method":"eth_sendTransaction","params":[{}],"id":1}' -H "Content-Type: application/json" http://localhost:9545

curl -X POST --data '{"jsonrpc":"2.0","method":"eth_sign","params":["0x604BB0f27A24374f1a784C458aFB9210CaAA2EDA", "0x48656c6c6f"],"id":1}' -H "Content-Type: application/json" http://localhost:9545

curl -X POST --data '{"jsonrpc":"2.0","method":"eth_signTypedData","params":["0x604BB0f27A24374f1a784C458aFB9210CaAA2EDA", {}],"id":1}' -H "Content-Type: application/json" http://localhost:9545

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Include instructions and any relevant details so others can reproduce.

[ ] Tested CCTX in localnet
[ ] Tested in development environment
[ ] Go unit tests
[ ] Go integration tests
[ ] Tested via GitHub Actions

Checklist:

[ ] I have added unit tests that prove my fix feature works

Could be great to also have a review from @zeta-chain/devops on this, thanks🙏

why do we disable eth_sendTransaction RPC?
As I understand, this is required for Ethereum wallet such as metamask to send tx to our EVM.

We use eth_sendRawTransaction with Metamask.
eth_sendTransaction allows sending unsigned transactions and getting them signed with unlocked accounts on the Node, hence why considered potentially unsafe.

From a quick glance, we're using ethers.Signer.sendTransaction() (in Hub and Labs for swaps, and the Faucet for transfers) and the useSignTypedData hook from wagmi in our full-stack apps.
@lumtis are those two getting disabled in this PR or am I looking in the wrong place and it's a different thing?

From a quick glance, we're using ethers.Signer.sendTransaction() (in Hub and Labs for swaps, and the Faucet for transfers) and the useSignTypedData hook from wagmi in our full-stack apps.
@lumtis are those two getting disabled in this PR or am I looking in the wrong place and it's a different thing?

Yeah, the Ethereum RPC naming is a bit confusing.
You have eth_sendTransaction to send tx to be signed on the node, and eth_sendRawTransaction to send tx signed on the client
https://ethereum.org/en/developers/tutorials/sending-transactions-using-web3-and-alchemy/#difference-between-send-and-send-raw
Unless we have a sytem we're we manage private keys on the node that users can unlock, we should be only using eth_sendRawTransaction


New Features

Added some new functions:
int32_t getLongitude_raw()
int32_t getLatitude_raw()
Returns lat and long in native UBlox formatting. 32bit vs 64 bit for the same information. Useful for data size critical applications.
void end()
Ends Serial bus. Useful for power critical applications that need serial busses closed for maximum sleep.
Updated Function:
void begin()
Clear out the _validPacket. Useful for waking from extended sleep periods where the information is invalid.

Hi,
although I was unsuccessful using your changes to UBLOX::end() my GPS device, cut the power and resume later, I still rebased them and put them into two separate commits instead of 11 :)
Do you still work on/with this lib?


QF-2908 openapi api docs

Task linked: QF-2873 Add pagination to the QFC API endpoints

Task linked: QF-2908 Revise swagger docs if they make sense and make sure all "hidden" params are documented


path to favicon bar url list?

I have totally missed the memo that upon Safari upgrade I would be losing my favicon bar. Now I'm on Safari 16.5 and of course it's gone :( I have several full system backups but I would rather not roll the system back because of this.
Any chance I can go back in Time Machine and look up my list of links for the FaviconBar? I don't have them backed up :( And I could not locate any file in Safari folder that would have them...
Thanks for your help!

Hi @ACBelkina, that is unfortunate. Did you manage to get them back again?


Possible null reference

Could these lines throw a null reference exception if the fragment is not immediately used after construction?
https://github.com/XamarinUniversity/AND205/blob/33bddd6c18a0ac6cd76a6f8a8db1e3d968fd3aef/Exercise 3/Start/Clock/Clock/TimeFragment.cs#L33
https://github.com/XamarinUniversity/AND205/blob/master/Exercise 3/Completed/Clock/Clock/TimeFragment.cs#L33

I know it's been a while, but I just ran this exercise and tried to reproduce the null reference exception without any luck.
@thisbarker were you seeing a specific error here or just posing the question hypothetically? Given all the things on that line, a couple potential null references could happen. It could fire if the current activity is null, which would suggest the fragment outlived its parent activity, but I'm not certain the exact situation that would cause that. Feel free to re-open if you have more details. I'd love to make sure we get this addressed, if it's still got a problem.


Fails to build

`Building df...
---> 3e09053df658
Step 1 : MAINTAINER Ben Cawkwell<EMAIL_ADDRESS>---> Using cache
---> e15a102e39b5
Step 2 : RUN echo "deb http://archive.ubuntu.com/ubuntu precise main universe" > /etc/apt/sources.list
---> Using cache
---> e0c68c6c40fa
Step 3 : RUN apt-get update
---> Using cache
---> ebcd0523e03f
Step 4 : RUN apt-get upgrade -y
---> Using cache
---> 3da1ba480a81
Step 5 : RUN apt-get install -y supervisor
---> Running in ae2b45f161e2
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
supervisor : Depends: python (>= 2.3) but it is not going to be installed
Depends: python-medusa (>= 0.5.4) but it is not going to be installed
Depends: python-meld3 but it is not going to be installed
Depends: python-pkg-resources (>= 0.6c7) but it is not going to be installed
Depends: python-support (>= 0.90.0) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Service 'df' failed to build: The command [/bin/sh -c apt-get install -y supervisor] returned a non-zero code: 100`

Thanks for reporting the issue. I tried reproducing the issue using the command:
docker build --no-cache -t df -rm .

The package supervisor was installed without problems, and the whole docker file was built without problems. I tested most of the commands from the README to check xpra still worked etc, as far as seeing the main menu in df. This was tested using Docker version 1.1.2, build d84a070.
Please try again using the --no-cache option, and if you are still getting problems let me know what version of docker you are using, and the command you are using to build.

Hi Ben,
I'm building with docker 1.3.2 and actually I used fig (www.fig.sh) to do
the build part. I got it to build in the end by changing the redirect in
the line which changes the /etc/apt/sources.list to append ( '>>' instead
of '>' ).
Could well just have been something with no-cache as well, I'll have a go
building it today maybe and see if using no-cache helps!
On 24 Jan 2015 07:51, "Ben Cawkwell"<EMAIL_ADDRESS>wrote:

Thanks for reporting the issue. I tried reproducing the issue using the
command:
docker build --no-cache -t df -rm .
The package supervisor was installed without problems, and the whole
docker file was built without problems. I tested most of the commands from
the README to check xpra still worked etc, as far as seeing the main menu
in df. This was tested using Docker version 1.1.2, build d84a070.
Please try again using the --no-cache option, and if you are still getting
problems let me know what version of docker you are using, and the command
you are using to build.
—
Reply to this email directly or view it on GitHub
https://github.com/bencawkwell/dockerfile-dwarffortress/issues/1#issuecomment-71303169
.

By changing that line, you essentially rebuilt without using the cache, since that line sits at the top of the Dockerfile. The actual change you made should make little difference, as the way it currently behaves is to remove  precise-updates and precise-security as sources.
Since you say it successfully built after you changed that line, I am going to close this issue since it was most likely caused by having an old cache of "apt-get update" that prevented installing supervisor. If I start to see this impact more people I might add "apt-get update" before each "apt-get install" command to reduce the chance of it happening, but that will make the built even slower than it is today so I would rather wait for proof that it is a common problem before changing it.
Feel free to report another issue if you get any more problems. I cannot promise I will have time to help right away but I will try.

Sound, that was probably it, I have a lot of stale ubuntu builds on the
machine I did this on.
On 24 Jan 2015 12:43, "Ben Cawkwell"<EMAIL_ADDRESS>wrote:

By changing that line, you essentially rebuilt without using the cache,
since that line sits at the top of the Dockerfile. The actual change you
made should make little difference, as the way it currently behaves is to
remove precise-updates and precise-security as sources.
Since you say it successfully built after you changed that line, I am
going to close this issue since it was most likely caused by having an old
cache of "apt-get update" that prevented installing supervisor. If I start
to see this impact more people I might add "apt-get update" before each
"apt-get install" command to reduce the chance of it happening, but that
will make the built even slower than it is today so I would rather wait for
proof that it is a common problem before changing it.
Feel free to report another issue if you get any more problems. I cannot
promise I will have time to help right away but I will try.
—
Reply to this email directly or view it on GitHub
https://github.com/bencawkwell/dockerfile-dwarffortress/issues/1#issuecomment-71312939
.


⚠ ClamAV has degraded performance

In 9e891c3, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 447 ms

Resolved: ClamAV performance has improved in 7f49276.


enable chat icon to show and hide ai bot chat

fixes ENG-84

This is good as a quick fix. We should probably do a more obvious close button, maybe an "X" that is absolutely positioned overlaidon the top right of the chat area. This current chat icon could be a good button to show up after it has been closed, and not when open or when it hasn't been used yet.


[Deposit Services] Change repo credentials in repository.json to props

We need to change repo credentials in repository.json to props so the username and password can be externalized from json config file.

i'll need to do a little more testing, so far only able to get the SWORD connection to work without specifying a port. I'll see if that can work, else we'll need to change how repositories.json processes the address. one solution is to have a single property which contains both the host and its port, so we can pass it along. right now, specifying an empty port leaves a trailing : in the address (will test that too)

Need to change the FTP environment variable username/password to pmc.ftp.user and pmc.ftp.password


Security contact needed (!!)

Hi Chris, I tried to reach you by email a few weeks ago but I didn't receive a response.  Could you look for an email from tim at timmcleandotnet?
Thanks!

I'm on the same boat as timmclean, a security contact is needed :)


Animation doesn't work for some type of charts starting from Angular 1.5.8

Currently using AngularJs 1.6.5 (latest), but in order to find from where the issue started to happen I have downgraded all the way till 1.5.7. In this version animation is working as expected. Starting from AngularJs 1.5.8 the animation for chart type: 'solidgauge' no longer works.
Link to jsfiddle showing the issue (AngularJs 1.5.8)
http://jsfiddle.net/bizon/h9v3wt8d/
Expected Behavior (AngularJs 1.5.7)
http://jsfiddle.net/bizon/rg8vr9ut/
Current Behaviour
The chart is rendered fully without animation.
Your Environment

AngularJs: 1.6.5
highcharts: 5.0.12
highcharts-ng: 1.1.0
Browser: Chrome

Related Issues found:
https://github.com/pablojim/highcharts-ng/issues/567

Another issue for the same case:
Highcharts-ng last tooltip visible on load (Angular 1.5.8) [Not Functional]
http://jsfiddle.net/bizon/9kvfncaa/
Highcharts-ng last tooltip visible on load (Angular 1.5.7) [Functional]
http://jsfiddle.net/bizon/j09cxj4m/
It seems that starting with Angular 1.5.8 something changed on animation side and this is not taken into consideration in highcharts-ng.

I meet the same problem
try to use highcharts5.0.10

@lyb12358 current version of Highcharts-ng doesn't work with 5.0.10 as you can see here, there are some console errors:
http://jsfiddle.net/bizon/aqoa6196/
And I really doubt this can be the issue, I've been working with Highcharts from younger versions, and this issue is way older then the release of 5.0.10


Compile error

I'm getting a compile error when trying to use keyring...
github.com/99designs/keyring/keychain.go:85:16: unknown field 'SelfUntrusted' in struct literal of type keychain.Access

I see the issue, the HEAD of keyring is dependent on your unmerged fork.  Dependencies! 😄
I'm using Dep, so I can workaround this until the merge:
[[override]]
  name = "github.com/keybase/go-keychain"
  branch = "master"
  source = "https://github.com/lox/go-keychain.git"

Apologies, I missed this issue! I'm perplexed how you ran into this given that library is vendored in.

No longer depends on a fork, so closing this!


the html is compling a wrong file

Description
the html is compling a wrong file, I have two "main" files, one with main.text and the other one cover_letter.tex. The HTML shows cover_letter.tex, but even after removing the cover_letter.tex, it is still compiling the cover letter.
(Optional:) Please add any files, screenshots, or other information here.
No response
(Required) What is this issue most closely related to? Select one.
Choose One
Internal issue ID
c2809e8d-82c8-48b4-bfe6-a45db7cddc21
Paper URL
https://services.arxiv.org/html/submission/5757027/view
Browser
Chrome/<IP_ADDRESS>
Device Type
Desktop

it is solved now, i noticed i have several main files, cover.tex, cover_letter.tex and main.tex. After removing the other two, it works.


Can't run on Cloudflare Workers

Hello,
Our team were interested in running an SSH client on Cloudflare Workers, and ssheasy seems to be a great fit. However, we hit a snag of not being able to connect to the proxy server.
After debugging, it turned out that the implementation of github.com/hullarb/dom/net/ws/wsconn_js uses new Function() to create the WebSocket instance, which is not allowed in such serverless environment.
Since github.com/hullarb/dom has no Issues reporting, I figure to report here, since it's related to ssheasy anyway.
Is there a way we can avoid using new Function()?

Hi!
Thanks for opening an issue. To be honest i have not much experience, knowledge about Cloudflare Workers, but i assume they have some alternative API to create  a websocket connection, don't they?
Also i'm wondering what would be the usecase to run the client in serverless environment, could you share some details on that?

Hi,
Thanks for the quick response!

i assume they have some alternative API to create a websocket connection

Yes. They support the full WebSocket API just like in browsers. They just don't allow your codes to call new Function(string) or eval(string). Just like in strict mode.

Also i'm wondering what would be the usecase to run the client in serverless environment, could you share some details on that?

We have a task runner that run on demand/schedule in serverless environment. One of the tasks is to SFTP a CSV from a remote server and process and store the data into database.

Thanks for sharing some details. Unforaunatelly i don't have experience with cloudflare workers, but based on the docs i'm not sure if reusing this code is the best option. ssheasy was design for the browser where you have to go through http, but in workers you could open TCP connections directly and just start an ssh connection, wouldn't that be option?

Thanks for checking! You're correct that using TCP connections directly is a better option. However, there is no readily-made JS library to set up SSH connection directly. That is why I'm looking at ssheasy as implementing the whole SSH protocol is out of my scope, and the Cloudflare Workers environment is very similar to the browser.
However, as I mentioned in the original post, the issue is actually inside your github.com/hullarb/dom library, specifically the net/ws/wsconn_js module that uses new Function to set up the WebSocket client. I'm not familiar with Go, but looking around and I find this wasmws that seems to manually construct the WebSocket instance, so I think it can be done.

sure, you could try to adapt the dom lib for the worker env.
but maybe you could look into https://www.npmjs.com/package/ssh2#get-a-directory-listing-via-sftp
i found some cloudflare worker example using this https://gist.github.com/DevCEDTeam/acfea17ed23ffe00ca67ece56444eb8c

maybe you could look into https://www.npmjs.com/package/ssh2#get-a-directory-listing-via-sftp

We did look at ssh2 as it's the most popular SSH/SFTP solution in Node.js ecosystem. However, it does not work in Cloudflare Workers, as Cloudflare only support a certain runtime APIs from Node.js, and they have to be prefixed with node:, which most of the NPM packages do not do, including ssh2.

i found some cloudflare worker example using this https://gist.github.com/DevCEDTeam/acfea17ed23ffe00ca67ece56444eb8c

Not sure how that gist works, but it does not look like a script that runs on Cloudflare Workers.


is it possible  to insert a insert/edit/delete from a ldap schema?

Hi
Sorry I am new using github. If its not the correct way to contact , please advice me 80).
I have been using ldap for a long time and now I decided to port a lot of scripts using python+ldap+html5 to django and django-ldapdb looks like very promising to me.
I am leaning django and learning simultaneos django-ldapdb.
Is it possible to create a  model that insert someting like below? I already made this schema...80)
dn: cn=Statefull_forward,cn=pauloric,cn=filter,cn=inet,cn=firewallng,cn=zeus.contatogs.com.br,uid=pauloric,ou=users,dc=contatogs,dc=com,dc=br
cn: Statefull_forward
objectClass: Firewallng
objectClass: FirewallngCT
objectClass: FirewallngVerdict
FirewallngTable: inet
FirewallngTableName: filter
FirewallngChainName: pauloric
FirewallngCTState: established,related
FirewallngRulesVerdict: accept
FirewallngRulesComment: Statefull_forward
FirewallngRulesOrder: FirewallngCTState,FirewallngRulesVerdict,FirewallngRulesComment

thanks in advanced

Yes, it should work properly; django-ldapdb does not care about the actual schema, you just have to provide the name and type of the fields :)
class FirewallRule(ldapdb.models.LdapModel):
    base_dn = 'cn=pauloric,cn=filter,cn=inet,...'
    object_classes = ['Firewallng', 'FirewallngCT', 'FirewallngVerdict']

    cn = fields.CharField(_("name"), db_column='cn', primary_key=True)
    table = fields.CharField(_("table"), db_column='FirewallngTable')
    table_name = fields.CharField(_("table name"), db_column='FirewallngTableName')
    chain_name = fields.CharField(_("chain name"), db_column='FirewallngChainName')
    ...


Clicking on a tool while editing a workflow leads to state loss

Steps to reproduce:

Begin editing a workflow
Click on a tool / data item

Expected result:
An error message is displayed about having unsaved work, and navigation is prevented.
Actual result:
The system navigates to the tool that was clicked on, abandoning all changes. Trying to open another workflow results in an error message about unsaved workflow changes being displayed.

Nope the changes are not abandoned.
Can you confirm?

Confirmed working, but it was non-obvious. Perhaps a tooltip or some other form of hint should be added to the "UNSAVED" button? Until now, I thought it was a simple indicator, not an interactive element.


Key

How it is possible to make the assignment of the keys, close the auto on the button of the keyboard U, open the auto on the button U

There are no shortcuts in vRP, most of the framework use menu based actions. It should not be difficult to create a resource to manage shortcuts and use it to call the vRP API (not documented, but it's vRP.vc_toggleLock(vtype) client tunnel).


Upgrade snowflake-connector-python version to support the token cache

Describe the feature
Upgrade snowflake-connector-python to >= v2.2.3 to support the Snowflake OAuth token cache. The only docs we could find on this were from the odbc connector, but the snowflake-connector-python says that... something... changed around a "Secure SSO ID Token" in v2.2.3 and the diff appears to be relevant to some sort of token cache.
We should:

Try out enabling the token cache in our Snowflake account
See if it works with the current version of snowflake-connector-python that dbt supports
If not, see if it magically works with v2.2.3
If not, see if we can find someone at Snowflake to give us the scoop on supported versions :)

Additional context
The token cache makes web-based oauth usable in dbt. Without the cache, each new connection (ie. thread) opened by dbt requires the user to login via a browser, rendering browser-based oauth basically useless in a multithreaded dbt run.
Who will this benefit?
Snowflake users using the oauth connection method

I was getting sufficiently annoyed by the multiple popups and was able to test this out recently.  Here are the steps I took:

Updated the allow_id_token parameter on our Snowflake account to true
Installed the keyring dependency that the Snowflake Python Connector uses for credentials caching.
Ran DBT 0.17.0 with 2 threads and still got 3 login prompts
Setup a local version of DBT to run from source in a Virtual Environment
Updated the version of Snowflake Python Connector to snowflake-connector-python==2.2.3
Ran local DBT 0.18.0-b1 with 2 threads.  Only got a single log in prompt.
Ran it again.  Did not get a login prompt at all!
Verified that the prior steps also work with the latest snowflake connector (2.2.9)

I'm working on verifying whether I'm allowed to sign the CLA before sending a PR (the change is very simple).

Ooh, thanks for linking to the source @ryano144, now I see there seems to be an alternative mechanism for Linux, I'll have to have a play with that

Hello there!
I played a bit with the SSO caching on Linux today.
I set up an environment as @ryano144 did, and on Linux the token will not be cached without editing the default configuration in connection.py.
As the comment says "Mac/Win will overlook this" but Linux will not.
Therefore on Linux at the moment I had to change the default configuration to return True, as I didn't find any other ways to set this session parameter.
Once I made this change however, I could benefit from the caching of my SSO token.

Hello everyone. I've updated to the latest version and still see this issue. Any pointers on how to resolve?

@don-at-omaze Which version of dbt are you using? Have you installed keyring? (See the discussion in #2689 as well)


missing source files

SdFatConfig.h and nvs_flash.h are missing from the source files.

nvs_flash.h is part of the esp32 library. If it is missing try installing the latest board support. I do not want to add it to this github repository.
I don't understand why sdfatconfig.h would be missing. It has been required for a long time and has never been part of this github repository. It is part the sdfat library.

This was me being stupid... I tried compiling it with VsCode, which has no libraries installed. Works with the Arduino IDE.


[Bug] unexpected token

🐞 Not js syntax
"@paypal/react-paypal-js": "^4.0.0"   in dist\react-paypal.node.js:286  unexpected token :
buttons?.current?.close();
_______ ^_______ ^

Hi @vladimircherevko nice catch! That is indeed a bug. That syntax is a new JS feature called optional chaining and I thought it would get transpiled down to ES5 in the dist files. I'll publish a bugfix asap.

Hi @vladimircherevko nice catch! That is indeed a bug. That syntax is a new JS feature called optional chaining and I thought it would get transpiled down to ES5 in the dist files. I'll publish a bugfix asap.

thanks

thanks

I just published 4.0.1 to npm which includes the bugfix for this. This should be resolved. Thanks for reporting the issue 😄

I just published 4.0.1 to npm which includes the bugfix for this. This should be resolved. Thanks for reporting the issue 😄


How to load other modules?

I use docker to install elastalert. I try to load the new module, but it fails
During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/bin/elastalert", line 8, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.10/site-packages/elastalert/elastalert.py", line 2155, in main
    client = ElastAlerter(args)
  File "/usr/local/lib/python3.10/site-packages/elastalert/elastalert.py", line 128, in __init__
    self.rules = self.rules_loader.load(self.conf, self.args)
  File "/usr/local/lib/python3.10/site-packages/elastalert/loaders.py", line 170, in load
    raise EAException('Error loading file %s: %s' % (rule_file, e))
elastalert.util.EAException: Error loading file /home/elastalert/rules/example_frequency.yaml: Error initiating alert ['elastalert_modules.dingtalk_alert.DingTalkAlerter']: Could not import module elastalert_modules.dingtalk_alert.DingTalkAlerter: No module named 'elastalert_modules'

load modules:
# ll /data/elastalert/elastalert_modules/
dingtalk_alert.py  __init__.py

rules:
alert_text_type: alert_text_only

alert_text_args:
  - host
  - method
  - request
  - status
  - upstream
  - num_hits

alert:
  - "elastalert_modules.dingtalk_alert.DingTalkAlerter"

yelp / elastalert does not work with python 3.9 and 3.10.
Ask the creator about dingtalk_alert.py.

jertel / elastalert2 is compatible with python 3.9 and 3.10. dingtalk is also supported.
https://github.com/jertel/elastalert2

Thank you for your help. I have solved the problem. In addition, I want to know how elasalert uses certificates to connect to es. I tried the following methods, but it doesn't work.
To generate a certificate, I use the existing p12 certificate (This certificate is used to generate the node certificate of the ES cluster)
echo "" | /usr/share/elasticsearch/bin/elasticsearch-certutil cert --silent --pem /etc/elasticsearch/ssl/elastic-stack-ca.p12 --ip <IP_ADDRESS> --dns es-master2 --out /tmp/1.zip

elastalert.yaml:
#Optional, select whether to connect es with SSL, true or false
use_ ssl: True

#Optional, whether to verify the TLS certificate. Set it to true or false. The default is - true
#verify_ certs: False

#Select certificate
ca_ certs: /home/elastalert/ssl/ca.crt
client_ crt: /home/elastalert/ssl/es-master2.crt
client_ key: /home/elastalert/ssl/es-master2.key

error log:
Traceback (most recent call last):
  File "/usr/local/bin/elastalert-create-index", line 8, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.10/site-packages/elastalert/create_index.py", line 278, in main
    create_index_mappings(es_client=es, ea_index=index, recreate=args.recreate, old_ea_index=old_index)
  File "/usr/local/lib/python3.10/site-packages/elastalert/create_index.py", line 23, in create_index_mappings
    esinfo = es_client.info()['version']
  File "/usr/local/lib/python3.10/site-packages/elasticsearch/client/utils.py", line 84, in _wrapped
    return func(*args, params=params, **kwargs)
  File "/usr/local/lib/python3.10/site-packages/elasticsearch/client/__init__.py", line 259, in info
    return self.transport.perform_request("GET", "/", params=params)
  File "/usr/local/lib/python3.10/site-packages/elasticsearch/transport.py", line 318, in perform_request
    status, headers_response, data = connection.perform_request(method, url, params, body, headers=headers, ignore=ignore, timeout=timeout)
  File "/usr/local/lib/python3.10/site-packages/elasticsearch/connection/http_requests.py", line 83, in perform_request
    raise SSLError('N/A', str(e), e)
elasticsearch.exceptions.SSLError: ConnectionError(HTTPSConnectionPool(host='<IP_ADDRESS>', port=9200): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:997)')))) caused by: SSLError(HTTPSConnectionPool(host='<IP_ADDRESS>', port=9200): Max retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:997)'))))
``

I think it will work if the ssl certificate related files are created correctly and set properly.
This is the setting I tried with ssl's self-signed certificate in the past.
# The elasticsearch hostname for metadata writeback
# Note that every rule can have its own elasticsearch host
es_host: es01

# The elasticsearch port
es_port: 9200

# Connect with TLS to elasticsearch
use_ssl: True

# Verify TLS certificates
#verify_certs: True

# Option basic-auth username and password for elasticsearch
es_username: elastic
es_password: xxxxxxxxx

# ssl
ca_certs: /usr/share/elasticsearch/config/certificates/ca/ca.crt
client_cert: /usr/share/elasticsearch/config/certificates/es01/es01.crt
client_key: /usr/share/elasticsearch/config/certificates/es01/es01.key

My es cluster node uses the following command to generate an xpack certificate:
echo "" | /usr/share/elasticsearch/bin/elasticsearch-certutil cert --ca elastic-stack-ca.p12 --ip <IP_ADDRESS> --dns es-master2 --out es-master2.p12 --pass ""
However, generating the certificate as at the beginning does not seem to work properly. I don't know how elasalert needs to generate a certificate

This is what I have confirmed in the past by generating a self-signed certificate with elastalert-server. Please refer only to the certificate creation part.
https://github.com/johnsusek/praeco/issues/345#issuecomment-822827568

There is no more information I can provide.

If the above answers do not help, ask in the discussion of elastalert2.
https://github.com/jertel/elastalert2/discussions

I've tried, but it didn't work

Through research, I solved the problem of loading modules. Thank you for your help


High priority messages converting OriginUrl

Was playing around with integrating SourceLink into one of my projects today. Using the SourceLink.Create.CommandLine package and manually providing values for: SourceLinkRootDirectory, SourceLinkOriginUrl and SoucreLinkCommit. This works and produces the expected values in the PDB files.
Unfortunately though it also causes high priority MSBuild messages to be emitted during build:
  SourceLinkUrl: https://raw.githubusercontent.com/dotnet/roslyn/{commit}/*
  CodeAnalysis -> E:\code\roslyn\Binaries\Debug\Dlls\CodeAnalysis\Microsoft.CodeAnalysis.dll
  SourceLinkUrl: https://raw.githubusercontent.com/dotnet/roslyn/{commit}/*
  CSharpCodeAnalysis -> E:\code\roslyn\Binaries\Debug\Dlls\CSharpCodeAnalysis\Microsoft.CodeAnalysis.CSharp.dll
  SourceLinkUrl: https://raw.githubusercontent.com/dotnet/roslyn/{commit}/*
  csc -> E:\code\roslyn\Binaries\Debug\Exes\csc\csc.exe

This appears to be coming from these lines in CreateTask:
url = ConvertUrl(OriginUrl);
Log.LogMessage(MessageImportance.High, "SourceLinkUrl: " + url);

This seems to be an expected operation hence a bit surprised it's issuing a high priority message here. Would expect Low or possible Normal here so that it doesn't clutter up minimal build output settings.
Is there a reason that it's high priority here? Is the expected use to instead provide SourceLinkUrl instead of SourceLinkOriginUrl and hence that's why the message is high priority?

CC @tmat

I'm happy to adjust the logging levels as needed. I simply picked high because I thought it was useful info. Happy to accept a PR for this change that bumps it down.

Happy to send a PR here. The high priority though made me question my overall approach. Made me consider that I should be using SourceLinkUrl directly which seemed a bit odd as it felt more like an implementation detail:
https://github.com/jaredpar/roslyn/commit/cdab03ca76f19e574c32e6b5910159942c5dbc45#diff-5784754bb70e21737b84a68a33ddef69R90
Will send a PR to bump down and go back to using SourceLinkOriginUrl.

Made me consider that I should be using SourceLinkUrl directly which seemed a bit odd as it felt more like an implementation detail.

Ohhh, I see how that may of been confusing.  The SourceLinkUrl is automatically detected if you are using GitHub. If you set SourceLinkUrl directly it skips trying to figure out the correct URL based off of origin. {commit} is replaced by SourceLinkCommit property.
It is currently set to high so that it shows up in the minimal logs like this:

Looking at your code:
  <!-- Utilize source linking whenever there is a valid git commit available. Won't be available during rebase,
       or build from zip for example -->
  <PropertyGroup Condition="'$(GitHeadShaRaw)' != ''">
    <SourceLinkCreate>true</SourceLinkCreate>
    <SourceLinkRootDirectory Condition="'$(SourceLinkRootDirectory)' == ''">$(RepoRoot)</SourceLinkRootDirectory>
    <SourceLinkOriginUrl>https://github.com/dotnet/roslyn</SourceLinkOriginUrl>
    <SourceLinkUrl>https://raw.githubusercontent.com/dotnet/roslyn/$(GitHeadShaRaw)/*</SourceLinkUrl>
    <SourceLinkCommit>$(GitHeadShaRaw)</SourceLinkCommit>
  </PropertyGroup>

You shouldn't need SourceLinkOriginUrl, SourceLinkUrl, or SourceLinkCommit. You don't need SourceLinkUrl if you set tSourceLinkOriginUrl. Since it  GitHub, it will be calculated. It will end up being https://raw.githubusercontent.com/dotnet/roslyn/{commit}/*. If you want to specify that and just SourceLinkCommit then you probably don't need SourceLinkRootDirectory, since it will not run a git command. This can all be seen in SourceLink.Create.CommandLine.targets. Hopefully, I made it clearer. ?

Reviewed and added comments directly to the pull request. https://github.com/dotnet/roslyn/pull/20719#pullrequestreview-50054526

@jaredpar Probably going to push 2.3 out soon'sh. You want to squeeze this in?


Silex 2 and CSRF support question

I see in the documentation that CSRF is only supported if you use the form provider.
is there a way to use it without needing to use the symfony form provider? I'd like to be able to use just a twig html template with my form like i could in silex 1.3
if that's not possible, I guess I'll just have to find a different way to add CSRF protection to my forms, but I'd prefer to use whats baked in if possible.

found a solution after further reading


How to upgrade Graphite from 1.1.4 to 1.1.7 ?[Q]

I was wondering how to upgrader Graphite from 1.1.4 to 1.1.7 because normally Graphite 1.1.4 and 1.1.7 are installed in different directories !!
Thanks

Hi @Jason-MK ,
It's not trivial to install Graphite in separate directory, I would not do that. Just install  whisper, carbon and graphite-web packages for 1.1.7 and restart carbon and graphite-web.

Thanks deniszh but I have an issue I did install 1.1.4 which is
Invalid theme 'default' when I click on dashboard
Best Regards