Cli inline config or configuration in package.json

Is your feature request related to a problem? Please describe.
Sometimes, the configuration is just so small and I'd prefer to add it into package.json or even use cli inline config instead:
overwrite: true
schema: "schema.graphql"
generates:
  schema.d.ts:
    plugins:
      - "typescript"

Describe the solution you'd like
As title, config inline or in package.json.
Describe alternatives you've considered
N/A
Additional context
N/A

Hi @JounQin
We are using cosmiconfig to manage configuration file. It support many forms of loading configurations.
You can use codegen config as JSON, and put it under your package.json and it will work the same:
"codegen": {
  "schema": "schema.graphql",
  // ...
}

@dotansimha Thanks for your reply, it's not well documented.

@JounQin you are right, I'll update the website. Thanks!

@dotansimha Sorry but I tried to add codegen in package.json but failed:
yarn graphql-codegenyarn run v1.22.10
$ /Users/JounQin/Workspaces/GitHub/graphql-schema/node_modules/.bin/graphql-codegen
Unable to find Codegen config file!
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

The cosmiconfig search places are not by default, which may cause confusion.
https://github.com/dotansimha/graphql-code-generator/blob/master/packages/graphql-codegen-cli/src/config.ts#L21-L29

Yeah, you are right. Just noticed it.
I created a PR here: https://github.com/dotansimha/graphql-code-generator/pull/5144
Can you please try the alpha version from that PR?

@dotansimha The alpha version works.

Perfect, thank you for helping me to test it. I will merge and release soon :)

Fixed in<EMAIL_ADDRESS>Thanks @JounQin !


Implements compilation of the delete operator

This branches enables compilation of the delete operator. Some thoughts I think are worth mentioning
1)
With this change, approximately 300 new seeds from test/mjsunit and the SpiderMonkey JIT test files will become compilable. If Fuzzilli treats the delete operation as a standard unary operator, delete might be applied to non-object properties, such as simple variables (var). If I understand correctly, semantic correctness will not be significantly impacted because delete does not cause a crash when called on unintended targets. For example, if applied to var, let, or parameters, it simply returns false and has no effect.
2)
It can happen that an object has a key that is a number. In that case DeleteElement will be called, even though it is not an array.
Example:
const obj = { 1: 'value' };
delete obj[1];

Similarly, we can delete elements from an array based on a computed index - in that case DeleteComputedProperty is called, not DeleteElement.
Example
const arr = [1, 2, 3];
delete arr[Math.floor(Math.random() * arr.length)];

Is that a problem? IIUC, the main difference between DeleteElement and Delete(Computed)Property In FuzzIL is only syntactical, not semantical.

Regarding you comments:

So IIUC we currently cannot compile something like delete a because that's not a MemberExpression? It's probably not super important, but maybe it's easy enough to fix. We could either add a DeleteName instruction, or, probably even simpler, just compile delete a to a delete this.a (which IIUC is effectively what it's doing). WDYT?

I think this all works correctly the way you describe/implemented it. delete x[1] should always be a DeleteElement and delete x[foo] should always be a DeleteComputedProperty, regardless of what the object or the computed property name is.

Regarding 1), I initially had this in the code, but then I found out that an implicit global variable does not become a property of this in all engines. For example, in Node.js, it becomes a property of global. I am not sure how this is handled in other JS engines, so I avoided it. Also, another problem would be to distinguish between implicit global variables and let, var, etc. The data structure that is processed by Compiler.swift only says that it is an identifier and what name it has.
I did a quick check of how many files in test/mjsunit/* have delete but are not compilable. We are talking about 28 files, and therefore they are in position 12 on the priority list. So perhaps it is best not to invest time in this right now and come back to it later.

Cool, just a question and one more suggestion. And sounds good, let's not bother with delete a stuff for now :)


Support for Telescope

Is your feature request related to a problem?
You mentioned that Preview with fzf needs a pipe command, Windows can't be supported.. But there is an awesome telescope.nvim that works fast and allows to avoid using external program. It would be nice to support it :)
Describe the solution you'd like
It would be nice to have an option to use Telescope instead of FZF.

Every fuzzy find can import the data of the current quickfix and become a filter for quickfix. But for now, only the UI of fzf perfectly compatible with quickfix.
If you want to filter data for quickfix, I think you can do it in telescope.nvim.

You mentioned that Preview with fzf needs a pipe command, Windows can't be supported.. But there is an awesome telescope.nvim that works fast and allows to avoid using external program. It would be nice to support it :)

I am not sure if you are still using bqf, but preview with fzf has been supported for Windows since https://github.com/kevinhwang91/nvim-bqf/commit/50dae9a5ebabaf8857ccb6becabe708b440360f0.

nvim community is all moving to telescope so

nvim community is all moving to telescope so

so PR is welcome

Telescope already supports quickfix filtering, so not sure if anything is actually needs to be done here.
The workflow is this:

Get your data into a quickfix
Run :Telescope quickfix, this will open the telescope with the current quickfix contents.
Filter data as needed in Telescope UI.
Send the results from Telescope back into the quickfix, default action is <C-q>.

Voila, now the quickfix is filtered.

Telescope already supports quickfix filtering

The issue is it uses fuzzy finding which is not always desirable.

Describe the solution you'd like
It would be nice to have an option to use Telescope instead of FZF.

Then maybe I did not understand what this issue is about. It says:
Describe the solution you'd like
It would be nice to have an option to use Telescope instead of FZF.

Isn't FZF a fuzzy finder by definition? :)

Oh, sorry, I thought that it's a different issue :)
The workflow is good, but bqf provides more.
Fzf integration for Neovim also have quickfix picker.

Currently no nvim-bqf change (more: no nvim-bqf) is needed to filter quickfix list using Telescope. Try :Telescope quickfix or create a keymap like below (possibly with pcall on require):
local function configureWindow()
 --- other settings
  vim.keymap.set({'n'}, 'zf', require('telescope.builtin').quickfix, {buffer = true})
end

local augroup = vim.api.nvim_create_augroup ('BqfMappings', {clear = true })
vim.api.nvim_create_autocmd ('FileType', {
  group = augroup,
  pattern = 'qf',
  callback = configureWindow,
})

Conversely, on the Telescope side we can create the new quickfix list (<C-q> by default, run <C-/> for help).
@kevinhwang91 it would be good to add such hint to README.

Currently no nvim-bqf change (more: no nvim-bqf) is needed to filter quickfix list using Telescope. Try :Telescope quickfix or create a keymap like below (possibly with pcall on require):
local function configureWindow()
 --- other settings
  vim.keymap.set({'n'}, 'zf', require('telescope.builtin').quickfix, {buffer = true})
end

local augroup = vim.api.nvim_create_augroup ('BqfMappings', {clear = true })
vim.api.nvim_create_autocmd ('FileType', {
  group = augroup,
  pattern = 'qf',
  callback = configureWindow,
})

Conversely, on the Telescope side we can create the new quickfix list (<C-q> by default, run <C-/> for help).
@kevinhwang91 it would be good to add such hint to README.

It's not necessary to add this hint because this issue is open.


TypeError: No matching definition for argument type(s) array(uint8, 3d, C), array(int32, 2d, C).

Thanks for your excellent work.
But, I am unable to successfully run any scripts on v1.0-mini.
I made sure to look through previous issues, downloaded the corresponding .pkl file and followed the instructions to execute the script. However, I always encounter a problem on line 100 of dataset_wrapper.py (update to line 91):
processed_label = nb_process_label(np.copy(processed_label), label_voxel_pair)
raise TypeError: No matching definition for argument type(s) array(uint8, 3d, C), array(int32, 2d, C).

I confirm that this issue is related to Numba’s signature, but I don’t know the specific reason.

Hi, we successfully ran a training script on v1.0-mini just now.
Given your bug report, we suggest replacing the original signature with "uint8[:,:,:](uint8[:,:,:],int32[:,:])" or "uint8[:,:,:](uint8[:,:,:],int64[:,:])".
https://github.com/wzzheng/TPVFormer/blob/207358903342962df1b69cd7da27301241df39dc/dataloader/dataset_wrapper.py#L99

Hi, we successfully ran a training script on v1.0-mini just now. Given your bug report, we suggest replacing the original signature with "uint8:,:,:" or "uint8:,:,:".
https://github.com/wzzheng/TPVFormer/blob/207358903342962df1b69cd7da27301241df39dc/dataloader/dataset_wrapper.py#L99

Thx. I made it.


What is the port number of Teltonika FM1202 for traccar?

i need to configure this device to traccar.. what is the port no of this?

Try port 5027.

this port is also not working.. now also i am not getting the data... any other option for fix this...

Do you see any HEX messages in the log file?

no, i didnt see.......

It means either your device can't connect to the server (possibly firewall or router issue) or it doesn't send any data.

how to check that? device connected or not.?

You can start by checking if port is visible from internet. For example here.

i had check.. Result -Port is closed, its means connected or not?

Port is closed means that your computer is not visible from internet. Do you have public IP? If yes, then there must be some problem with router or firewall.


Add actions tests

Test for is_button_toggled and for custom napari actions.
One test is skipped because it needs Qt. It can be restored after merging #51.

The reviewers did not express a willingness to conduct the review.


[Dependency Update] Update braces 3.0.2 dependency

Description
For CVE-2024-4068, which affects 3.0.2 but is fixed in 3.0.3,
npm update braces

Issues Resolved
Testing
[Please provide details of testing done: unit testing, integration testing and manual testing]
Check List

[ ] New functionality includes testing

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

[ ] New functionality has been documented
[x] Commits are signed per the DCO using --signoff

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

The build failure is because there was a network hiccup when the docker container assembly failed to download the kafka distribution - the external network call failed.
I proposal to pull the download of kafka and aws-msk-iam-auth out of the image building process, pulling them instead from gradles cache.  Maybe there is a precedent for how another project accomplishes this?
Pro:

Reused already downloaded artifacts from gradle build
Removes potential source of flakiness from build
Prevent version mismatches if latest != the version we depend on in the common dependencies

Con

Effort to build it

> Could not build image: The command '/bin/sh -c wget -qO- https://archive.apache.org/dist/kafka/3.6.0/kafka_2.13-3.6.0.tgz | tar --transform 's!^[^/]*!kafka!' -xvz' returned a non-zero code: 2
> Task :TrafficCapture:dockerSolution:buildDockerImage_migrationConsole FAILED

https://github.com/opensearch-project/opensearch-migrations/blob/22d3f74f350531b0eedc781e81eae185007d3783/TrafficCapture/dockerSolution/src/main/docker/migrationConsole/Dockerfile#L8-L9

@mikaylathompson I've retriggered E2E Testing / test (pull_request) after filing #700 to account for the flaky behavior


feat: Remove references to signatures

Removes old references to contract agreement signatures.
Linked Issues
Closes #176

I think some of the *.png files also need an update or are they generated automatically?
Found it at least in contract-agreement-message.png

I think some of the *.png files also need an update or are they generated automatically? Found it at least in contract-agreement-message.png

Thx. I updated the contract agreement png. Are there others I missed?


Only one describe block per module

It seems that zUnit only runs the first test suite (aka describe block) in a module and ignores subsequent ones.
const { describe, it } = require("zunit");

describe("first", () => {
  it("tests");
});

describe("second", () => {
  it("tests");
});

gives following output when run
$ npx zunit

bar

  first
    tests
     - SKIPPED: Pending (0ms)

Summary
  Tests: 1, Passed: 0, Failed: 0, Skipped: 1, Duration: 7ms

One or more tests were not run!

as a contrast mocha will run both
describe("first", () => {
  it("tests");
});

describe("second", () => {
  it("tests");
});

output
npx mocha

  first
    - tests

  second
    - tests

  0 passing (2ms)
  2 pending

Is this behaviour as designed or a bug? If it is deliberate, I would love to learn why.
Cheers

Sorry for the delay @BorePlusPlus. It's deliberate. The reason was the way I original implemented zUnit to automatically add the suite to the modules default export. This broke with ESM so I have since re-implemented. I suspect it may be possible now.


Fixes for runtime errors when running EN track check.

This pull request fixes a couple of issues I found when running the EN track check on the full QuOTA dataset:

util/geo.py needs to handle missing data when creating datetime instances.
The test crashes if number of data files > number of threads because the EN_track_headers variable is not {} after the first file is processed in the thread. I've attempted to fix this by saving the data file name and updating EN_track_headers when this changes.

@s-good good catch, I didn't consider not parallelizing over multiple files. It would be interesting to see if results are globally the same for two files on one thread vs. the same files on separate threads - but that's a task for another day. Thanks!


Fix tests

The tests are failing, this will fix them.
I would also highly recommend setting up a Travis to run the tests automagically.

Thanks for the contribution.
I think we used to have Travis set up. At least I could see travis files


Complete Queue Overflow

[0 - 7f3f4c26a700] {4}{runtime}: [warning 1071] LEGION WARNING: Region requirement 1 of operation transpose_copy (UID 793) in parent task cholesky (UID 3) is using uninitialized data for field(s) ,101 of logical region (1014,1,1) (from file /home/users/adncat/yizhou/Legion/runtime/legion/legion_ops.cc:539)[warning 1071]
For more information see:
http://legion.stanford.edu/messages/warning_code.html#warning_code_1071
[0 - 7f3f4c26a700] {4}{runtime}: [warning 1071] LEGION WARNING: Region requirement 1 of operation transpose_copy (UID 795) in parent task cholesky (UID 3) is using uninitialized data for field(s) ,101 of logical region (1054,1,1) (from file /home/users/adncat/yizhou/Legion/runtime/legion/legion_ops.cc:539)[warning 1071]
For more information see:
http://legion.stanford.edu/messages/warning_code.html#warning_code_1071
[0 - 7f3f4c26a700] {4}{runtime}: [warning 1071] LEGION WARNING: Region requirement 1 of operation transpose_copy (UID 797) in parent task cholesky (UID 3) is using uninitialized data for field(s) ,101 of logical region (1094,1,1) (from file /home/users/adncat/yizhou/Legion/runtime/legion/legion_ops.cc:539)[warning 1071]
For more information see:
http://legion.stanford.edu/messages/warning_code.html#warning_code_1071
[0 - 7f3f4c229700] {6}{compqueue}: completion queue overflow: cq=1900000000000003 size=1024

@qyz96 based on the discussion in #663, I believe we've resolved the issue that this PR was demonstrating, so I'd line to close it out.  Do you have any remaining concerns?


upgrade-bridge fails on lxd 2.3

Ubuntu 16.04
lxd 2.3-0ubuntu5~ubuntu16.04.1~ppa1
Apt fails to upgrade package if there is old bridge configuration in /etc/default/lxd-bridge. Here is installation log:
Selecting previously unselected package ebtables.
(Reading database ... 360771 files and directories currently installed.)
Preparing to unpack .../ebtables_<IP_ADDRESS>-3.4ubuntu1_amd64.deb ...
Unpacking ebtables (<IP_ADDRESS>-3.4ubuntu1) ...
Preparing to unpack .../lxd-client_2.3-0ubuntu5~ubuntu16.04.1~ppa1_amd64.deb ...
Unpacking lxd-client (2.3-0ubuntu5~ubuntu16.04.1~ppa1) over (2.0.4-0ubuntu1~ubuntu16.04.1) ...
Preparing to unpack .../lxd_2.3-0ubuntu5~ubuntu16.04.1~ppa1_amd64.deb ...
Warning: Stopping lxd.service, but it can still be activated by:
  lxd.socket
Unpacking lxd (2.3-0ubuntu5~ubuntu16.04.1~ppa1) over (2.0.4-0ubuntu1~ubuntu16.04.1) ...
Warning: Stopping lxd.service, but it can still be activated by:
  lxd.socket
Preparing to unpack .../lxd-tools_2.3-0ubuntu5~ubuntu16.04.1~ppa1_amd64.deb ...
Unpacking lxd-tools (2.3-0ubuntu5~ubuntu16.04.1~ppa1) over (2.0.4-0ubuntu1~ubuntu16.04.1) ...
Processing triggers for systemd (229-4ubuntu10) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up ebtables (<IP_ADDRESS>-3.4ubuntu1) ...
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Setting up lxd-client (2.3-0ubuntu5~ubuntu16.04.1~ppa1) ...
Setting up lxd (2.3-0ubuntu5~ubuntu16.04.1~ppa1) ...
Installing new version of config file /etc/init.d/lxd ...
Installing new version of config file /etc/init/lxd.conf ...
Setting up lxd dnsmasq configuration.

Old bridge configuration detected in /etc/default/lxd-bridge, upgrading
Unsetting deprecated profile options
Attempting to kill current lxd-bridge
/usr/lib/lxd/upgrade-bridge: 58: kill: No such process

Bringing down and renaming existing bridge lxdbr0 to lxd-upgrade
Creating a new LXD bridge
/usr/lib/lxd/upgrade-bridge: 147: /usr/lib/lxd/upgrade-bridge: Syntax error: end of file unexpected (expecting "fi")
dpkg: error processing package lxd (--configure):
 subprocess installed post-installation script returned error exit status 2
Setting up lxd-tools (2.3-0ubuntu5~ubuntu16.04.1~ppa1) ...
Processing triggers for systemd (229-4ubuntu10) ...
Processing triggers for ureadahead (0.100.0-19) ...
Errors were encountered while processing:
 lxd
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up lxd (2.3-0ubuntu5~ubuntu16.04.1~ppa1) ...

Old bridge configuration detected in /etc/default/lxd-bridge, upgrading
Unsetting deprecated profile options
Attempting to kill current lxd-bridge
/usr/lib/lxd/upgrade-bridge: 58: kill: No such process

Creating a new LXD bridge
/usr/lib/lxd/upgrade-bridge: 147: /usr/lib/lxd/upgrade-bridge: Syntax error: end of file unexpected (expecting "fi")
dpkg: error processing package lxd (--configure):
 subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
 lxd

Sorry, I just found more appropriate place for this issue https://github.com/lxc/lxc-pkg-ubuntu/issues/7


feat: Add 'IntoSeries'

What type of PR is this? (check all applicable)

[ ] 💾 Refactor
[x] ✨ Feature
[ ] 🐛 Bug Fix
[ ] 🔧 Optimization
[ ] 📝 Documentation
[ ] ✅ Test
[ ] 🐳 Other

Related issues

Related issue #
Closes #387

Checklist

[ ] Code follows style guide (ruff)
[ ] Tests added
[ ] Documented the changes

If you have comments or can explain your changes, please do so below.
I think I should keep learning from #365 to improve the current PR.

looks good, just got a little question

Should we miss some questions here?


|| does not work if first value is 0 and second is 1.

https://github.com/sinedied/dmx-hue/blob/6aa6a574f4d77dcf89ede24d7f4c008d8561f8b6/index.js#L273
Need something like to have it not always fall to second value:
universe: this._args.universe === 0 ? 0 : (this._args.universe || Util.config.get('universe') || 0),
(I had config universe to 1 and was unable to argh override it to 0)

Fixed in 2.0


hide redo button when filtering or color adjusting

Hi @longitachi,
I fixed a bug which the redo button remained displayed when in filtering mode and color adjustment mode.

Before
After

Thanks for your pr.


LeapHybridNLSampler not rejecting for state_size() > maximum_number_of_states

Description
LeapHybridNLSampler accepts models with more than maximum_number_of_states states initialized but quietly ignore the rest. Users might think the rest are being used.
To Reproduce
model = traveling_salesperson(distance_matrix=DISTANCE_MATRIX)
route, = model.iter_decisions()
with model.lock():
    model.states.resize(2)
     route.set_state(0, [0, 1, 2, 3, 4])
    route.set_state(1, [0, 1, 2, 3, 4])
results = sampler.sample(
     model,
     label='SDK Examples - TSP')

Expected it to reject: "Alex C 6  days ago Something that came up... we need to add it. And reject problems based on that num_states field in the header"
Expected behavior
Reject such problems
Environment:

OS: WIN
Python version: 3.11

Additional context
@alexzucca90 suggested to move to here.
I notice we actually check maximum_number_of_states property here so can easily do this in the client.

We could also just raise a user warning and continue with the truncated states. Seems more user friendly (but less explicit), unless you think it's really important for users to realize only one state is used (currently).


Undici MockAgent cannot intercept fetch request anymore

Describe the bug
Since the version 2.1.5, we cannot mock anymore our http calls with undici MockAgent due to the bug fix:
vitest:
Use fetch() implementation from happy-dom  -  by @capricorn86 in https://github.com/vitest-dev/vitest/pull/6879 (3c56f)
Reproduction
import { MockAgent, setGlobalDispatcher } from 'undici';

describe('Test mock fetch with undici', () => {
    it('should success', async () => {

       const mockAgent = new MockAgent();
       mockAgent.disableNetConnect();
       setGlobalDispatcher(mockAgent);

        const apiMockPool = mockAgent.get('https://localhost');

       apiMockPool
         .intercept({ method: 'GET', path: '/api/v1/test' })
         .reply(200, { success: true })
         .persist();

       const result = await fetch('https://localhost/api/v1/test');
       expect(result).toBeDefined();
    });

System Info
System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz
    Memory: 16.25 GB / 31.71 GB
  Binaries:
    Node: 23.2.0 - ~\bin\node-v23.2.0-win-x64\node.EXE
    Yarn: 4.5.0 - ~\bin\node-v23.2.0-win-x64\yarn.CMD
    npm: 10.9.0 - ~\bin\node-v23.2.0-win-x64\npm.CMD
  Browsers:
    Edge: Chromium (128.0.2739.67)
    Internet Explorer: 11.0.19041.4355
  npmPackages:
    @vitejs/plugin-react: ~4.3.3 => 4.3.3
    @vitest/coverage-v8: ~2.1.5 => 2.1.5
    vite: ~5.4.11 => 5.4.11
    vitest: ~2.1.5 => 2.1.5

Used Package Manager
yarn
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

As this looks more like a feature of happy-dom, can you open an issue there?
On Vitest, you can probably try overwriting fetch (and other) globals back to undici by following
import { fetch } from "undici"
globalThis.fetch = fetch;

Oh ok I'm scared no money go in where okok

From: Hiroshi Ogawa @.>
Sent: Saturday, November 23, 2024 7:15 AM
To: vitest-dev/vitest @.>
Cc: Subscribed @.***>
Subject: Re: [vitest-dev/vitest] Undici MockAgent cannot intercept fetch request anymore (Issue #6952)
As this looks more like a feature of happy-dom, can you open an issue there?
On Vitest, you can probably try overwriting fetch (and other) globals back to undici by following
import { fetch } from "undici"
globalThis.fetch = fetch;
—
Reply to this email directly, view it on GitHubhttps://github.com/vitest-dev/vitest/issues/6952#issuecomment-2495378169, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BF53BVHNMEQQVXQ45VD33YT2CATP3AVCNFSM6AAAAABSJJC2XCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJVGM3TQMJWHE.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Make it easier to notice production alerts

User Story
As the engineer on support
I need production alerts to be easily noticeable
So that I can respond quickly to problems
At the moment production/non-production alerts go to the same channel, and they are not visually distinguishable.
For example, the below screenshot shows 2 alerts, one which is affecting prod, the other which is affecting dev. Spot the difference...

The "live" label is a red herring, as this refers to the cloud platform cluster name, not our environment.
Value / Purpose
This is a follow on ticket from https://github.com/ministryofjustice/find-moj-data/issues/832
Even after removing some of the false positives, it is currently very easy to miss alerts on prod, because we send non-prod alerts to the same channel, and don't distinguish them.
Solving this will improve our ability to respond more quickly to incidents.
Hypothesis
If we make the important alerts easier to notice, we will act on them faster
Proposal
A couple of options:

Send non-prod alerts to a different channel
Clearly mark the environment in the title of the alert

Raised https://github.com/ministryofjustice/cloud-platform/issues/6294 to add a pingdom integration for prod only

Also raised a support request with CP to change the Alertmanager alerts from Prometheus https://github.com/ministryofjustice/cloud-platform/issues/6300

I have separated out our Sentry alert rules into environments so we can direct prod alerts to the new channel
https://ministryofjustice.sentry.io/projects/find-moj-data/?project=4507181591101440
https://ministryofjustice.sentry.io/alerts/rules/?environment=prod&statsPeriod=14d


[Doc] Add back link to GitHub in header

I would often open the GitHub repo through this link. Is it possible to add it back, along with the version number? Exactly like on https://tailwindcss.nuxtjs.org/
I can submit a PR if you're okay with this change.

Yes, that would be great!


chore: add pyflakes, pycodestyle, isort and flake8 rules to ruff

Description
This PR updates the ruff configuration in pyproject.toml, so rules from pyflakes, pycodestyle and isort are checked by ruff. These ones are useful, as ruff will warn us about unused imports, not used variables, etc.
The command ruff --fix has been executed in the files from src and tests directories, which has automatically removed unused imports and variables, as well as sorted the imports.
After running the command, the tests were not working because in argilla/server/models/__init__.py we were importing everything from argilla/server/models/models.py and argilla/server/models/questions.py modules using * wildcard. Both modules have a Field class/function, so when creating the factories in tests/factories.py, instead of using the Field SQLAlchemy ORM class, the Field function from pydantic was being used causing the error. Before this error was not occurring because the Field from models.py was being imported after the one from questions.py.
Type of change

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested
N/A
Checklist

[x] I added relevant documentation
[x] follows the style guidelines of this project
[x] I did a self-review of my code
[x] I made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I filled out the contributor form (see text above)
[ ] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)

@gabrielmbmb This is awesome!
Perhaps we can also incorporate these ones that I once researched but never included?
https://github.com/argilla-io/argilla/pull/2325#issuecomment-1424320210

You might have to just rebase efb86f788f223660da4deb61297025b4d02fad08 and 8a702a27475c050bfaa54f095de3ed53e15678ee on top of develop again, and redo the pyproject.toml changes before re-running pre-commit run --all. These merge conflicts seem like hell otherwise 😅

as @tomaarsen suggested, I've added flake8-comprehension and flake8-pytest-style. pyupgrade could be a nice edition, but I think that could be added in another PR, as we will need to select which rules of pyupgrade to apply so everything works fine with old Python versions. For example, pyupgrade will update the code to PEP604 which is compatible from python>=3.10:
from typing import Union
from pydantic import BaseModel

class MyModel(BaseModel):
    number: Union[int, None] = None

will get upgraded to:

from pydantic import BaseModel

class MyModel(BaseModel):
    number: int | None = None

and in python<=3.10, pydantic won't be able to parse it.

I think it's a nice chance to have another look into this, and eventually include it right before the 1.15.0 release, WDYT? @gabrielmbmb I feel like if we don't tackle this now then we'll have more conflicts and will never be tackled...


Can TensorRT-LLM supoort facebook/nllb-200-3.3B?

System Info
Nvidia A100 PCIe 80G
Who can help?
none
Information

[X] The official example scripts
[X] My own modified scripts

Tasks

[X] An officially supported task in the examples folder (such as GLUE/SQuAD, ...)
[X] My own task or dataset (give details below)

Reproduction
Can TensorRT-LLM supoort facebook/nllb-200-3.3B?
Expected behavior
Can TensorRT-LLM supoort facebook/nllb-200-3.3B?
actual behavior
none
additional notes
none

@ncomly-nvidia  hey any update on this, i am looking forward to also port seamlessM4T_v2 models to tensorRT LLM. would be willing to write all the code and make the port, and submit a PR.
need some direction and rough guidance.

re-assign to  @laikhtewari


Bug in Duckling_ner with the name of the language

rasa NLU version :
0.9.0a4
Used backend / pipeline :
["nlp_spacy",
"ner_spacy",
"ner_synonyms",
"intent_featurizer_spacy",
"intent_classifier_sklearn",
"ner_duckling"]
Operating system :
OSX
Issue:
In multi-tenancy mode, when I loaded all the models and tried to parse some sentences I noticed the following error from Duckling showing it can't load the language module:
Jul 7, 2017 12:12:24 PM clojure.tools.logging$eval277$fn__281 invoke
SEVERE: [duckling] Module en is not loaded. Did you (load!)?

After digging I noticed that Duckling is being loaded with language 'en' inside duckling_extractor.py.
The name of the language should be as following:
  | DANISH = 'da$core'
  | GERMAN = 'de$core'
  | ENGLISH = 'en$core'
  | SPANISH = 'es$core'
  | ESTONIAN = 'et$core'
  | FRENCH = 'fr$core'
  | IRISH = 'ga$core'
  | INDONESIAN = 'id$core'
  | ITALIAN = 'it$core'
  | JAPANESE = 'ja$core'
  | KOREAN = 'ko$core'
  | PORTUGUESE = 'pt$core'
  | RUSSIAN = 'ru$core'
  | UKRAINIAN = 'uk$core'
  | VIETNAMESE = 'vi$core'
  | CHINESE = 'zh$core'

Replacing 'en' with 'en$core' fixed the issue.

@amirkargar which version of duckling are you using? I created a PR at the duckling repo a while ago fixing that, so a version update there might resolve that.

I’m using Duckling 1.3.0. I should update and see how it works. Thanks.

On Jul 7, 2017, at 1:53 PM, Tom Bocklisch<EMAIL_ADDRESS>wrote:
@amirkargar https://github.com/amirkargar which version of duckling are you using? I created a PR at the duckling repo a while ago fixing that, so a version update there might resolve that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/RasaHQ/rasa_nlu/issues/465#issuecomment-313639383, or mute the thread https://github.com/notifications/unsubscribe-auth/AK2FHkAqIryiDw-703Y8t0bfWR0OHgHXks5sLgAtgaJpZM4OQo7-.

I'll close this one, let me know if the problem persists with the updated version.

The upgrade fixed the issue, thanks.

On Jul 7, 2017, at 6:17 PM, Tom Bocklisch<EMAIL_ADDRESS>wrote:
I'll close this one, let me know if the problem persists with the updated version.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/RasaHQ/rasa_nlu/issues/465#issuecomment-313694976, or mute the thread https://github.com/notifications/unsubscribe-auth/AK2FHkdowHM8jpyvwd7T6VpH0sYzOCwyks5sLj4IgaJpZM4OQo7-.


Stylise the Try Now! link in the home page

Make the Try Now! link look like a button.
You can do that by implementing the trynow-button class in styles.css.
Make sure the Button fits the Aesthetic of the page.

I am interested in contributing to this as a part of JWOC. Please assign it to me.

Comment when the coding phase begins. It will be assigned then as per first cum first serve

I want to contribute here. please , assign me this issue. I will give my best

Hello @Spandan-Bhattacharya !
I am from JWoC'24
I have a good hold in web development.
Could you please assign me tis issue after the coding period starts?

Comment after the coding phase begins, otherwise we are not allowed to assign you the task.

Hello @Spandan-Bhattacharya
Please assign me this issue under JWoC'24.

Hello @Spandan-Bhattacharya , I would like to work and contribute on this issue under JWOC.  Kindly assign it to me.

@Sruti-sahini you are assigned this issue, best of luck!!

i want too work on this project

Everyone if you have not joined the Discord server yet, please do so, as I will be sharing instructions on the solve-it! channel under projects.
Link to the server:
https://discord.gg/bcgZ9RZZ8r

@Spandan-Bhattacharya  can you assign me this issue under JWOC.. i would like to contribute


.Net Processes - Map Step Feature

DRAFT
Motivation and Context

Fixes: https://github.com/microsoft/semantic-kernel/issues/9193
Description

Map each value from a set to a map-operation and present the results as a set for potential reduction.
Includes:

ProcessMapBuilder (Core)
KernelProcessMap / KernelProcessMapState (Abstractions)
LocalMap (LocalRuntime)

Features:

Handles when output type has been transformed from input type
Accepts either step or subprocess for map operation

Contribution Checklist

[X] The code builds clean without any errors or warnings
[X] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[X] All unit tests pass, and I have added new tests where possible
[X] I didn't break anyone :smile:

General thoughts about State + Map:
Since the map is a subprocess with N steps (to be defined at runtime), I'm thinking of 2 scenarios:

Map steps are volatile and no state is saved, and if the root process pauses while running the map, the last event received by the map gets re-propagated and the map steps get re-spawned -> only works if map steps steps are not too complex
Assuming the Map steps are complex enough (another subprocess as step + state) different strategies could be taken, since at this point the map steps act as workers -> trying to get multiple jobs (same jobs) done, and return a result:

all Map steps steps are singletons and share same resources, so on pause/resume only 1 state per map step step is saved -> using as example the foodprep -> if 5 fish orders get triggered the ingredient stock should be globally -5

also the singleton step may be an interesting feature to explore when reusing steps so they all use same resources just used multiple times by different processes, emitting result to different parent processes

on pause, the most completed process state gets saved, and on resume this one gets passed as initial state to all map steps:

with this consideration, when loading a processes with state at most for map steps we offer to pass along the same initial state to all map children

Additional considerations - not for this PR but for the feature in general:

timeout management: if spawning N events, have timeout logic and if some map steps are not done, null is returned
limiting number of N elements: depending on how complex the inner steps are (nested subprocesses)
volatile state: since map steps are spawned on runtime have checkpoints before and after the map step

Additional considerations - not for this PR but for the feature in general:

timeout management: if spawning N events, have timeout logic and if some map steps are not done, null is returned
limiting number of N elements: depending on how complex the inner steps are (nested subprocesses)
volatile state: since map steps are spawned on runtime have checkpoints before and after the map step

I like these considerations.  I feel that timeout and depth considerations apply generally to the entire framework, not just the map-step.
I very much like the volatile concept.  I have to admit, I'm not entirely clear on the pause or cancel mechanics in the runtime.  I don't see the cancel-token being propagated much, but I need to take a closer look

all Map steps steps are singletons and share same resources, so on pause/resume only 1 state per map step step is saved -> using as example the foodprep -> if 5 fish orders get triggered the ingredient stock should be globally -5

also the singleton step may be an interesting feature to explore when reusing steps so they all use same resources just used multiple times by different processes, emitting result to different parent processes

on pause, the most completed process state gets saved, and on resume this one gets passed as initial state to all map steps:

Ben and I did discuss this "functoid" constrain for the map operation and felt it might be too limiting.  At this point, the feature is functional without constraining the map operation state.  Also if we apply the "volatile" concept, I wonder if the need exists to constrain the map operation.
Another question that comes to mind is how to enforce such a constraint (singleton / functoid).


fix fix error due to jsonpaths resolution results

Proposed changes

problem
When the key name in json is a.b, the value will be parsed incorrectly
resolve
Add rules and put a.b in parentheses
sql

CREATE TABLE `test`.`q1` (
  `k1` varchar(1024) NULL,
  `k2` varchar(1024) NULL,
) ENGINE=OLAP
DUPLICATE KEY(`k1`)
COMMENT 'OLAP'
DISTRIBUTED BY HASH(`k1`) BUCKETS 1
PROPERTIES (
"replication_allocation" = "tag.location.default: 1"
);

json

{
        "tags": {
                "a.b": "test",
                "k2": "k2_value"
        }
}

stream load

curl -v --location-trusted -u root:"" -H "format: json" -H "jsonpaths: [\"$.tags.[a.b]\",\"$.tags.k2\"]" -T test.json http://<IP_ADDRESS>:8030/api/test/q1/_stream_load

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

run buildall

run beut

run p0

run p0

run buildall

run p0

run buildall

run p0

run p0

run p0

run p0

run buildall

run buildall

run buildall

run p0

run p0


Update Targets/Actuals slide graph on Home page and the Custom Dashboard Indicators tab

Please update the slider to show useful numbers. Right now in DEMO it only shows targets.
Production is more useful as it shows the actuals and targets

Production:

Hide the custom dashboard for now at least until it is ready for production use

The same feature (it is labeled target/target, not target and actuals) is broken on the Home Dashboard:

The Target doesn't look right. Example DEMO - there is only one Indicator associated to the SO1 -
SO1: Tola will be the primary system of record for managing indicators
The LOP target of that one indicator is 80
The individual data collected targets sum to 54
And the actuals sum to 54
But the slider chart shows a target of 11 303

The actuals are correct:

This visualization is not showing you target vs actuals per indicator. It is per strategic objectives. That "SO1: Tola will be the primary system of record for managing indicators" is not an indicator, it is a strategic objective.

yes, understood, still, the target of 11 303 does not make sense.

In addition to fixing the bug in calculating the total sum of targets I also fixed the indicator count. Currently it is counting number of data collection records but the UI is suggesting # of indicators so I changed it to count indicators instead.


chore(issue_template): add issue template

Codecov Report

Merging #289 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #289   +/-   ##
========================================
  Coverage    90.03%   90.03%
========================================
  Files           29       29
  Lines         1324     1324
========================================
  Hits          1192     1192
  Misses         132      132

Continue to review full report at Codecov.

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


[bug] Can't add a new note

🐞 Bug report
Description
When adding a note, clicking on the "Add Note" button has no effect.
Reproduction

Create a new note.
Add a description.
Click on the "Add Note" button.

Error message
When looking at the development console, the following message appears:

mainThreadExtensionService.ts:65 [[object Object]]Cannot create property 'id' on string '{"sha":"","filename":"","url":"","lines":"","title":"Some title","comment":"Some description","priority":1,"category":"Suggestion","additional":"","private":1,"code":""}'

🌍 Your Environment

vscode-review Extension 1.22.0

Version: 1.52.1
Commit: ea3859d4ba2f3e577a159bc91e3074c5d85c0523
Date: 2020-12-16T16:32:10.090Z
Electron: 9.3.5
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.10.0-051000-generic

I will try to investigate as soon as possible.

Hi,
I have also just given this tool a go and rand into similar issues. If I have a workspace open where I added multiple directories it looks like the code-review.csv is not created. I tried a second time (also linux) on a different project and now the file was created but still I can not add notes. cool project

Hi,
I have also just given this tool a go and rand into similar issues. If I have a workspace open where I added multiple directories it looks like the code-review.csv is not created. I tried a second time (also linux) on a different project and now the file was created but still I can not add notes. cool project

I did a quick first investigation.
I think I identified the problem: https://github.com/d-koppenhagen/vscode-code-review/commit/9f53d87fcfae97364cf2fe978cf8769762536651#diff-6bfea2ec3c1d21c90d6e1ecd704f380a6eeb44521e1da1a87b6a48ea691b6a43
The JSON.parse call const comment = JSON.parse(object) as CsvEntry; is necessary to make the object schema updatable (i.e. add the idproperty).
More investigations to come later.

I did a quick first investigation.
I think I identified the problem: https://github.com/d-koppenhagen/vscode-code-review/commit/9f53d87fcfae97364cf2fe978cf8769762536651#diff-6bfea2ec3c1d21c90d6e1ecd704f380a6eeb44521e1da1a87b6a48ea691b6a43
The JSON.parse call const comment = JSON.parse(object) as CsvEntry; is necessary to make the object schema updatable (i.e. add the idproperty).
More investigations to come later.

Hey, that's a strange behavior indeed.
I mainly made this code change because the extension tests were failing before which blocked the release.

Hey, that's a strange behavior indeed.
I mainly made this code change because the extension tests were failing before which blocked the release.

The header of the function export function createCommentFromObject(object: any | CsvEntry): CsvEntryis erroneous and confusing.
At the moment, it must receive a string.
I will rework it to accept any kind of representation (string, object).

The header of the function export function createCommentFromObject(object: any | CsvEntry): CsvEntryis erroneous and confusing.
At the moment, it must receive a string.
I will rework it to accept any kind of representation (string, object).


Firefox hello is not working in flame device

I can install this app successfully in my flame device. But while trying to run this app, they are saying "your device is not compatible with this app".

Please take a look at your user-agent because you should be able to see what your user agent contains 'ALCATELOneTouch6015X' or 'Mozilla'
https://github.com/mozilla-b2g/firefoxos-loop-client/blob/master/app/compatibility.json

@crdlc, Can you plz make it more clear? I'm using Flame reference device with fxOS 2.0. Can I install fx hello? If So, How?

AFAIR all the info is available in de README
https://github.com/mozilla-b2g/firefoxos-loop-client/blob/master/README.md

I had no problems pulling it from here and running it on My flame running 3.0 nightly. if you allow the install from a hello chat link however this error message does occur.

Yes, The error occured while I'm trying to install hello from the chat link.
I installed hello by pulling it from here. Its now working fine.
Thanks all :)


Track problems in Envoy 1.22.0

I clicked Run Workflow for v1.22.0 and v1.22.0_debug on
https://github.com/tetratelabs/archive-envoy/actions/workflows/release.yaml
Only windows worked.

The linux image changed, so scripts failed to find the binaries
Envoy 1.22.0 hasn't made it to OS/x due to drift https://github.com/Homebrew/homebrew-core/pull/99389

Next steps:

figure out drift in linux image and make a change to the shell script in a way that doesn't break versions before 1.22. re-run v1.22.0 and v1.22.0_debug workflows after that workaround is merged.
re-run workflow v1.22.0 once the 1.22.0 formula is fixed in homebrew

Update:

no update on homebrew as no-one has attempted to add 1.22
below are some breadcrumbs for linux image drift

Looks like the image layer changed in 1.22.0 (for linux). It is still the same in windows and <1.22 linux
$ sh -x ./bin/archive_release_version.sh envoyproxy/envoy v1.22.0 check
--snip--
using dist: envoy-v1.22.0-linux-amd64
+ set +e
+ ./bin/car_envoy.sh v1.22.0 linux amd64 list v1.22.0/envoy-v1.22.0-linux-amd64
error: usr/local/bin/envoy not found in layer
--snip--
$ sh -x ./bin/car_envoy.sh v1.22.0 linux amd64 list v1.22.0/envoy-v1.22.0-linux-amd64
--snip--
+ reference=envoyproxy/envoy:v1.22.0
+ car -t --platform linux/amd64 --created-by-pattern 'ADD linux' --strip-components 2 -qf envoyproxy/envoy:v1.22.0 usr/local/bin/envoy
error: usr/local/bin/envoy not found in layer
--snip--
$ car -t --platform linux/amd64 --strip-components 2 -vvf envoyproxy/envoy:v1.22.0 usr/local/bin/envoy
--snip--
https://index.docker.io/v2/envoyproxy/envoy/blobs/sha256:4086e842c0d1e552c62d8b94d92cb0c5a91fbccf62284f1e1c60d60a182270fa size=21351994
CreatedBy: COPY /usr/local/bin/envoy* /usr/local/bin/ # buildkit
-rwxr-xr-x	59397736	Apr 16 01:42:42	usr/local/bin/envoy
--snip--
$ car -t --platform linux/amd64 --created-by-pattern '/usr/local/bin/envoy' --strip-components 2 -qf envoyproxy/envoy:v1.22.0
usr/local/bin/envoy

So what happened was the image layers changed in 1.22. To fix this requires a patch. I've put this here as for the sake of project continuity someone besides me needs to become familiar with the project, even if a volunteer. PR welcome!
diff --git a/bin/car_envoy.sh b/bin/car_envoy.sh
index ea1a34f..05d9353 100755
--- a/bin/car_envoy.sh
+++ b/bin/car_envoy.sh
@@ -110,7 +110,15 @@ linux)
     reference=envoyproxy/envoy:${version}
   fi

-  ${car} --created-by-pattern 'ADD linux' --strip-components 2 -qf "${reference}" ${files}
+  # As the Envoy image is large, select a layer that includes the binary instead of extracting all layers.
+  case ${version} in
+    1.19.*|1.20.*|1.21.*) # Envoy doesn't release old versions
+      ${car} --created-by-pattern 'ADD linux' --strip-components 2 -qf "${reference}" ${files}
+      ;;
+    *) # 1.22.0 changed the image layout.
+      ${car} --created-by-pattern '/usr/local/bin/envoy' --strip-components 2 -qf "${reference}" ${files}
+      ;;
+  esac
   ;;
 windows)
   reference=envoyproxy/envoy-windows:${version}

With the patch applied, the following should work for linux even if darwin is still waiting for someone to get homebrew working:
$ ./bin/archive_release_version.sh envoyproxy/envoy v1.21.0 check
$ ./bin/archive_release_version.sh envoyproxy/envoy v1.22.0 check

Next action:

someone raise a PR with the patch I mentioned and test it locally as mentioned
once the above is merged, click "run workflow" here and enter the pattern as prompted. once for v1.22.0 and again for v1.22.0_debug

After that:

someone try to get the homebrew 1.22.0 working
once that is available on homebrew-core run the v1.22.0 release again.

Note: release steps are in the README, I'm just being specific.

Tips on OS/x.

Try local first as you can do this without effecting your laptop setup: brew install --build-from-source envoy --HEAD
The actual syntax is something like brew bump-formula-pr --no-browse --no-audit --version v1.22.0
Most Envoy minor releases break and you can enlist help once you have a PR up by pinging people who usually help. Ex https://github.com/Homebrew/homebrew-core/pull/90921

here's a smaller diff that @cpakulski can use to work around this. I tested it.
diff --git a/bin/car_envoy.sh b/bin/car_envoy.sh
index ea1a34f..88a3176 100755
--- a/bin/car_envoy.sh
+++ b/bin/car_envoy.sh
@@ -110,7 +110,9 @@ linux)
     reference=envoyproxy/envoy:${version}
   fi

-  ${car} --created-by-pattern 'ADD linux' --strip-components 2 -qf "${reference}" ${files}
+  # Don't use --created-by-pattern because Envoy 1.22.0+ changed the image layer containing the binary.
+  # Note: Unlike windows, layers preceding the Envoy binary are small, so scanning through is OK.
+  ${car} --strip-components 2 -qf "${reference}" ${files}
   ;;
 windows)
   reference=envoyproxy/envoy-windows:${version}

$ ./bin/archive_release_version.sh envoyproxy/envoy v1.22.0
archiving envoyproxy/envoy v1.22.0 released on 2022-04-15
using dist: envoy-v1.22.0-darwin-amd64
./bin/car_envoy.sh: line 98: tag: unbound variable
using dist: envoy-v1.22.0-darwin-arm64
./bin/car_envoy.sh: line 98: tag: unbound variable
using dist: envoy-v1.22.0-linux-amd64
creating envoy-v1.22.0-linux-amd64.tar.xz
using dist: envoy-v1.22.0-linux-arm64
creating envoy-v1.22.0-linux-arm64.tar.xz
using dist: envoy-v1.22.0-windows-amd64
creating envoy-v1.22.0-windows-amd64.tar.xz
using dist: envoy-v1.22.0-windows-arm64
error: windows/arm64 is not a supported platform: windows/amd64
$ tar -tvf v1.22.0//envoy-v1.22.0-linux-arm64.tar.xz
drwxr-xr-x  0 65534  65534       0 Apr 15 08:00 envoy-v1.22.0-linux-arm64/
drwxr-xr-x  0 65534  65534       0 Apr 15 08:00 envoy-v1.22.0-linux-arm64/bin/
-rwxr-xr-x  0 65534  65534 55335328 Apr 15 08:00 envoy-v1.22.0-linux-arm64/bin/envoy

Note: this only fixes the linux thing and only becomes usable when someone clicks release

nit: let's avoid using the keyword "fixes" in PRs unless they do that as it closes the corresponding issue
NEXT STEPS:

click through release workflow for v1.22.0 and v1.22.0_debug. The former should work for linux and windows and the latter linux only (as there's no debug release for windows)
once homebrew has envoy 1.22.0 merged, re-click release v1.22.0 to add os/x to it.  Also v1.21.2 once that's fixed which is probably the same issue.

cc also @jcchavezs as due to travel I may be sporadic and I think you can help guide @cpakulski as needed

Current status:

linux and windows images are available for v1.22.0.
linux image is available for v.22.0_debug

Next steps:

fix homebrew for v1.22.0

Opened PR for homebrew-core to build version 1.21.1: https://github.com/Homebrew/homebrew-core/pull/101428

Current status:
macOS image obtained by car works only for macOS version 12. Envoy image fails when run on macOS 10.15 and 11.
Next steps:
Do not verify macOS image for macOS 10.15 and macOS 11.

Are we stop supporting this versions or just disable verification. Also can you point out the failure or describe the error (for context purposes)

We stop supporting those. Verification fails because binary cannot be executed on versions 10.15 and 11. We would have to introduce another dimension to indicate OS version. However, users can install Envoy on 10.15 and 11 via brew, because it takes it from different bottles.

Thanks for the clarification.
ons. 25. mai 2022, 20:41 skrev Christoph Pakulski @.***

:

We stop supporting those. Verification fails because binary cannot be
executed on versions 10.15 and 11. We would have to introduce another
dimension to indicate OS version. However, users can install Envoy on 10.15
and 11 via brew, because it takes it from different bottles.
—
Reply to this email directly, view it on GitHub
https://github.com/tetratelabs/archive-envoy/issues/34#issuecomment-1137705236,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXOYATD2UU3SQ7L2LBFDXTVLZX4BANCNFSM5UDW7TCA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Closing this. Nothing is left to be done for rel. 1.22.0.


Fix action link tracking on browse pages

⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠
Follow these steps if you are doing a Rails upgrade.
What
Fixes the attributes for index_link and index_total on GA4 tracking attributes on action links on https://www.gov.uk/browse/business and https://www.gov.uk/browse/benefits

when the GA4 tracking was first added to the action link, there was only one action link on one browse page
now there are two browse pages with action links, and one of them (business) has three links
for GA4 tracking purposes, each link needs a distinct index_link value, and an index_total value that reflects the total number of action links

I've moved the code for this into the helper to hopefully make it more maintainable over time, and to make the generated values for the indexes hopefully a bit more robust.

Why
Part of the GA4 migration.
Visual changes
None.
Trello card: https://trello.com/c/mI6jxJru/752-placeholder-fix-indexes-on-action-links-when-more-than-one-link-present

That's a good suggestion @AshGDS, thanks, have implemented. Ready for re-review.


Some Samples Don't work

Some samples I tried (in dist/samples) reference JS code that does not exist. For example dist\samples\Components\Table\index.html has a reference to Jquery.Table.js, Table.js: both of which do not exist. Same for Breadcrumb sample. Those are the ones I tried, but maybe there are others.

Thanks! This is actually a known issue: https://github.com/OfficeDev/Office-UI-Fabric/issues/67 . We're working on a fix for it now.
Basically, the template used for component demo HTML pages has a hard-coded reference to <Component>.js and Jquery.<Component>.js, even if those files don't exist. Since several components, like the ones you mentioned and a few others, do not require JavaScript to function, those files don't exist--hence the errors.
The fix for this should be ready soon, and will be available in our next release. I'll close this issue for now since the work for it is already being tracked, unless I'm missing something. Thanks for catching this!


Temporary count-up?

Can the number of viewers be retained only temporarily?

Is this temporary?
I tried to move it, but the number of viewers increased only temporarily.

ahh Runnable getExecutable
Thread.sleep(XXXXXX)!
?

Still didn't find out how to make it not temporarily. Working on it.

With good proxies the bot works like a charm, residential proxies get banned afer about 20minutes but use rotating proxies


Panic on no supported client-requested "namedCurves"

Your environment.

Version: 1.5.0
Browser: Node.JS @nodertc/dtls library
Other Information:

panic: runtime error: index out of range

goroutine 266 [running]:
github.com/pion/dtls.serverHandshakeHandler.func1(0xc0000cc360, 0x52, 0x60, 0x1, 0xc0000c4050)
	/go/pkg/mod/github.com/pion/dtls@v1.5.0/server_handlers.go:38 +0x13cd
github.com/pion/dtls.serverHandshakeHandler(0xc0000ec500, 0x1c9eed8, 0xc0000ec500)
	/go/pkg/mod/github.com/pion/dtls@v1.5.0/server_handlers.go:163 +0x5af
github.com/pion/dtls.(*Conn).handleIncomingPacket(0xc0000ec500, 0xc000128000, 0x5f, 0x2000, 0x0, 0x0)
	/go/pkg/mod/github.com/pion/dtls@v1.5.0/conn.go:417 +0x4bc
github.com/pion/dtls.(*Conn).inboundLoop(0xc0000ec500)
	/go/pkg/mod/github.com/pion/dtls@v1.5.0/conn.go:360 +0x1bb
created by github.com/pion/dtls.createConn
	/go/pkg/mod/github.com/pion/dtls@v1.5.0/conn.go:170 +0x600

What did you do?

Started a pion/dtls listen server.
Using openssl 1.0.2s client:
openssl s_client -dtls1_2 -connect <IP_ADDRESS>:4444 -debug -cipher ECDHE-ECDSA-AES128-GCM-SHA256 -curves secp384r1

What did you expect?
Connection closes gracefully, rather than a panic
What happened?
The application panic'ed and crashed.
The offending line is here: https://github.com/pion/dtls/commit/6dec1ec79e7ecb3d01bcd70967c13592da7e13e4#diff-84f73d0d6a8b3cb71ba4ae9da4d57470R51
This assumes the client provides at least one supported Elliptic Curve, but in some cases the server may not support any of Elliptic Curve's that the client is requesting be used.

Nice find!
You interested in fixing @RyanGordon? That would be an awesome first issue! If there is anything I can do to help please tell me.
If you don't have the time/aren't allowed I can grab instead!

Yes, I will gladly put up a PR tomorrow


Where can I get the api (projects)

For learning the resources, I want to collect the php files with this projects. Could you help me?

@kabircse there's no relation between this codelab and PHP, I don't think this is the right venue for your question.


Ignore Tunnels

When a tunnel is open (VPN for example) the gauge should not consider the traffic that is passing through it.

Thanks for your contribution.


chore: manually bumping up minor versions

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #2960 into master will decrease coverage by 0.41%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2960      +/-   ##
==========================================
- Coverage   62.58%   62.17%   -0.42%
==========================================
  Files         226      222       -4
  Lines       11202    11277      +75
  Branches     2307     2329      +22
==========================================
  Hits         7011     7011
- Misses       3878     3954      +76
+ Partials      313      312       -1

Impacted Files
Coverage Δ

...-appsync-simulator/src/data-loader/lambda/index.ts

...ages/amplify-appsync-simulator/src/server/index.ts

...ync-simulator/src/mqtt-server/abstract-listener.ts

...ync-simulator/src/velocity/util/transform/index.ts

...ackages/amplify-appsync-simulator/src/utils/log.ts

...psync-simulator/src/resolvers/pipeline-resolver.ts

...sync-simulator/src/velocity/value-mapper/mapper.ts

...sync-simulator/src/schema/appsync-scalars/index.ts
0% <0%> (ø)

...-appsync-simulator/src/velocity/util/list-utils.ts
0% <0%> (ø)

...mplify-appsync-simulator/src/mqtt-server/server.ts
0% <0%> (ø)

Continue to review full report at Codecov.

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


angular should be a peerDependency

This stops npm from nesting angular under ngClipboard

Thansk :)

Do you know when you'll have time to cut a release?
On 19 Oct 2017 09:46, "Sachin N"<EMAIL_ADDRESS>wrote:

Thansk :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sachinchoolur/ngclipboard/pull/31#issuecomment-337841486,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAZQTIpM8E9xUOZkRXMcviL67ZFI-vo3ks5stwxfgaJpZM4LR7lH
.

Done.


Hello World in Pascal

Waiting until the formal release of the article on 4/14/18.

Pulling this in Saturday, the 14th.


Migration tool exception when code contains an unreferenced part file

Migration branch: https://github.com/parse-community/Parse-SDK-Flutter/pull/579
I have annotated a lot and now clicking migrate it just crashes. Restarted multiple times. Tried on MacOs and Windows.
Tried 2.12.2 (newest stable) and dev on Mac.
Could not apply migration
Error: NoSuchMethodError: The method 'hadDiskContent' was called on null.
Receiver: null
Tried calling: hadDiskContent("part of flutter_parse_sdk;\n\nabstract class AppInfo {\n  Future getLanguage();\n\n  Future getAppName();\n\n  Future getPackageName();\n\n  Future getVersion();\n\n  Future getBuildNumber();\n}\n")
Stacktrace: auto populated by migration preview tool.
#0      Object.noSuchMethod (dart:core-patch/object_patch.dart:54:5)
#1      PreviewSite.performApply (package:nnbd_migration/src/preview/preview_site.dart:501:35)
#2      PreviewSite.handlePostRequest (package:nnbd_migration/src/preview/preview_site.dart:449:9)
<asynchronous suspension>
#3      HttpPreviewServer._handlePostRequest (package:nnbd_migration/src/preview/http_preview_server.dart:109:5)
<asynchronous suspension>
#4      HttpPreviewServer._handleServer.<anonymous closure> (package:nnbd_migration/src/preview/http_preview_server.dart:119:9)
<asynchronous suspension>

EDIT: Works when using dart migrate --apply-changes!
Env
Dart: 2.12.2 (macos, windows), 2.13.0-144.0.dev(macos, windows)
Chrome: Version 91.0.4449.6 (Official Build) dev (64-bit) Windows. (on mac it was the stable version).

I'm able to reproduce this.  Investigating now...

Aha, I see the problem!  The migration tool gets confused when it sees an unreferenced part file.  The file in question, packages/dart/lib/src/data/app_info.dart claims to be a part of flutter_parse_sdk, but the definition of that library (in packages/dart/lib/parse_server_sdk.dart) doesn't list it as a part file.
Downgrading priority since this is a pretty rare corner case, but I'll still try to get a fix out soon.

Uhh interesting. Will fix that then.
Pretty frustrating case though.
Since dart migrate --apply-changes was working , maybe it makes sense to add a disclaimer: "Please try it in cli as well"
Just for less frustration, if somebody has a similar issue.

Uhh interesting. Will fix that then.
Pretty frustrating case though.
Since dart migrate --apply-changes was working , maybe it makes sense to add a disclaimer: "Please try it in cli as well"
Just for less frustration, if somebody has a similar issue.

Yeah, if fixing the bug were difficult I would definitely consider this.  Fortunately the fix isn't too difficult.  I'm already most of the way through it :)


Elixir support

It will be great to have Elixirlang support

Wow, brave. The compiled binaries must be pretty big.


Bug Fix: Moved UI Update to Main Queue

This PR

fixes bug that might stop UI update from rendering
updates CocoaPods version to 1.5.0
update spec repos

Thanks @t-adedotun for having noticed the thread issue.
Could you please sign off your changes as per
https://github.com/matrix-org/synapse/blob/master/CONTRIBUTING.rst, please?
PR must target the develop branch but I can change it.

Oh! I'll do that right away.

@manuroe Done.

Thanks @t-adedotun


wiki:

Related Issues and Documentation

- #68535 (closed)
- #18957 (closed)
- #64529 (closed)
.  #17781 (closed)
. #26423 (closed)
. #44665 (closed)
. #66738 (closed)
- #66830 (closed)
- #68536 (closed)
- #69474 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

Empty.


Query specification processing

Codecov Report

Merging #27 (10873e4) into main (ad1bdda) will increase coverage by 1.36%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #27      +/-   ##
==========================================
+ Coverage   94.90%   96.26%   +1.36%
==========================================
  Files          13       13
  Lines         903      991      +88
==========================================
+ Hits          857      954      +97
+ Misses         46       37       -9

Flag
Coverage Δ

pytest
96.26% <100.00%> (+1.36%)
:arrow_up:

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

Impacted Files
Coverage Δ

...ylegend/core/databse/sql_to_string/db_extension.py
94.48% <100.00%> (+2.11%)
:arrow_up:

pylegend/tests/core/database/test_sql_to_string.py
100.00% <100.00%> (ø)

pylegend/core/sql/metamodel.py
94.33% <0.00%> (+1.88%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


where is the annotations files

Hi, thanks for your interesting work. But I fail to run the code cause I can't find the annotation file `instances_hico_train_hoi_seen_github'.  Where is it?

Please download from https://drive.google.com/file/d/11e5mymZWOIc-2tf2xSoE4AqDf21qaUul/view?usp=sharing.

Thanks for your sharing


Combining Forces

Hi there,
I wrote a Rust mmap wrapper a few months ago, before you had published your crate on crates.io.  My implementation is largely the same as yours, the main differences seem to be that I have more support for high-level Rust traits that make it easy and safe to work with (e.g. exposing &mut [u8] instead of *mut u8), but I expose fewer non-cross platform options.  It's fully cross platform and tested on Linux, OS X, and Windows.  Check out the API here.
I don't see much need for two crates doing essentially the same thing, so I wanted to know if you would be interested in teaming up on this effort, and potentially merging the projects.  I'm pretty open particulars; my only real concern is that there is a go-to high quality mmap library for Rust, and I'd prefer if we didn't duplicate effort!

@rbranson ping, I'd like to get your thoughts on this.  Thanks!

@danburkert looks like you've done a great job on this other project. Acknowledge that my stuff is pretty unsafe. What do you think are next steps?

@rbranson would it be acceptable to add you as a committer on my repo, and have you add me as an owner on crates.io?  The next step is that I would push a version of my repo to crates.io with a minor version bump.
I'm a bit worried about breaking any projects that depend on the current version of the crate.  Projects can always pin the version to the current one, but I may take a look with cargo-crusader to see how bad breakage will be before publishing a new version.  Transitioning to the new API should be straightforward for downstream dependencies, the only feature mismatch that I can see that is not platform-specific is creating a mmap with offsets, but I've been working on that.

You have laid claim on a very good name for a memory mapped file crate (mmap), but you've shown absolutely no effort in maintaining it. If you could at least allow others like @danburkert to make mmap continue on as a maintained library, that would be the best thing you've done for this project in months, and would take minimal effort from you.

It looks like there are five crates depending on mmap right now:

block_allocator - anonymous mmap
context - anonymous stack mmap
coroutine - anonymous stack mmap
wayland-kbd - file-backed mmap

All of these use cases are covered right now by my version (stack support will be landing soon), so it should be a straightforward update across the board.

@retep998 your response comes across as very rude. This is a volunteer-based community, please try to treat others with respect for their time and effort.
I am waiting on danburkert's version of mmap to become public so I can push up code. But likewise, I am patient with @rbranson response. I am sure this will be resolved soon.


AzureFileCopy - set automatically Content-Encoding

I am using latest cloud Azure DevOps - Release - Task Azure File Copy - version 4.*
to copy static files for web page to Azure Storage blob account container.
It also automatically sets correct content-type attribute in azure storage account.
However, attribute content-encoding is not set, and should be set for gzip,or brotli / .br files etc.
This is needed due to HTTP browser requirements, and CDN only pick-up data from Azure storage account with metadata.
Anyhow, like you support automatically setting the content-type, i suggest for azcopy.exe to support auto setting the content-encoding attribute.

gzip files can be inferred by checking their magic number as described here : https://stackoverflow.com/questions/6059302/how-to-check-if-a-file-is-gzip-compressed
Unfortunately it does not seem feasible for other compression scheme, such as brotli https://stackoverflow.com/questions/6059302/how-to-check-if-a-file-is-gzip-compressed - There's an issue opened about this topic : https://github.com/google/brotli/issues/867


This does not work with current NFX

Does it need the Nuget Update?

Please link aganst latest nuget <IP_ADDRESS>

Actual  NFX nuget version is <IP_ADDRESS>


Use case for states

String interpolation. It's hard to tokenize this otherwise:
a.b(`c \` ${d.e(`f`, g => {})} h \x0a`)

It's also nice to let states inherit rules from other states and be able to count things, e.g. the interpolated expression state needs a } rule that can tell if it's a closing brace or the end of the interpolation, but is otherwise identical to the normal expression state.

Also, I think nested OCaml or Haskell comments might need states if you want to handle the nesting at the lexer level.

handle the nesting at the lexer level.

I think that requires counting more than states, unless you want an indefinite number of states.

Oh, interesting. I guess you can do nested string interpolation because you always escape to the opposite state.
`abcdef ${12 + `   ${10e10}   ` + 34} ghijkl`
 -------  ***** ---  ***** --- ***** -------

With comments (and possibly with something with three kinds of states?) this wouldn't work. Yikes.
I guess adding a stack would be too much, Tim? :P

you always escape to the opposite state.

Not exactly—consider
`a${{c: d}}e`
--- *****??--

You have to have some way of differentiating between closing braces and the end of ${…}.

I guess adding a stack would be too much, Tim? :P

I think pushing/popping of states is the right way to handle this sort of thing. Perhaps:
moo.states({
  main: {
    str: {match: '`', push: 'lit'},
    ident: /\w+/,
    lbrace: {match: '{', push: 'main'},
    rbrace: {match: '}', pop: 1},
  },
  lit: {
    interp: {match: '${', push: 'main'},
    escape: /\\./,
    end: {match: '`', pop: 1},
    const: /(?:[^$]|\$(?!\{))+/,
  },
})

pushing/popping of states is the right way to handle this sort of thing

That's how most other tokenizers seem to do things.

moo.states

Interesting!
How would you handle sharing tokens between states?

How would you handle sharing tokens between states?

You can let the user do it herself with Object.assign, or you can do something slightly horrible like { start: {…}, other: {_extend: 'start', …} }.


HADOOP-19084. Pruning some of the transitive dependencies of imports

In particular
-zookeeper
-other libraries referencing logging
This doesn't seem to fix the problem were dependencies on hadoop-common and hadoop-client API pull in conflicting stuff, but it tries.
How was this patch tested?
hadoop release support viewing output of published artifacts in repo.
For code changes:

[X] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 57s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
xmllint
0m  1s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-3.4 Compile Tests _

+0 :ok:
mvndep
4m 17s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
46m 24s

branch-3.4 passed

+1 :green_heart:
compile
21m  6s

branch-3.4 passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
19m 26s

branch-3.4 passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
mvnsite
1m 17s

branch-3.4 passed

+1 :green_heart:
javadoc
1m 19s

branch-3.4 passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 12s

branch-3.4 passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
shadedclient
134m 29s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 33s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
0m 32s

the patch passed

+1 :green_heart:
compile
20m  2s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
20m  2s

the patch passed

+1 :green_heart:
compile
19m 55s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
19m 55s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
1m 19s

the patch passed

+1 :green_heart:
javadoc
1m 14s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 15s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
shadedclient
45m 55s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
0m 34s

hadoop-project in the patch passed.

+1 :green_heart:
unit
0m 41s

hadoop-yarn-applications-mawo-core in the patch passed.

+1 :green_heart:
asflicense
1m  3s

The patch does not generate ASF License warnings.

229m 51s

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6574/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6574

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint

uname
Linux e3eb12ecb4ca 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.4 / 820a73b8094b6f99ffa83e64239b06b9f4136ab4

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6574/1/testReport/

Max. process+thread count
535 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-mawo/hadoop-yarn-applications-mawo-core U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6574/1/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.


Failure with numpy 1.18.4

We're experiencing a bug with pyxDamerauLevenshtein 1.5.3 (any version above, and including, 1.5.2, really), when using it with numpy 1.18.4 (or any version between 1.18.4 and 1.20.0).
Here's how to reproduce (using docker):
docker run --rm -ti python:3.7.6 bash
pip install numpy==1.18.4
pip install pyxdameraulevenshtein==1.5.3
python -c 'from pyxdameraulevenshtein import damerau_levenshtein_distance'

This will produce the following error:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "__init__.pxd", line 242, in init pyxdameraulevenshtein
ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 88 from C header, got 80 from PyObject

This was working fine until at least last Friday, but started failing without any change on our part.
I'm not sure if anything can be done (seems pretty hard to debug), but if someone has the same issue, upgrading numpy to 1.20.0+ or downgrading pyxDamerauLevenshtein to 1.5.1 works.

I missed it before, but this seems very similar to #14, although possibly not a duplicate since that bug was fixed.

Thanks for the issue, @patatepartie. I was able to replicate this. A few things:

Note that you're using an old version of this library. 1.6.1 is out. If I try to use NumPy 1.18.4 with it, though, it does still throw an error.
I think what I'll do is increase the minimum NumPy version in setup.py just to make sure everyone is using a compatible version.

Ok, I just released a new version of the library (1.6.2) that upped the minimum NumPy version number to 1.19.5. This is passing all CI tests. Can you let me know how this works for you?

Thank you, @gfairchild .

Note that you're using an old version of this library. 1.6.1 is out. If I try to use NumPy 1.18.4 with it, though, it does still throw an error.

Indeed. I did try 1.6.1 (all versions between 1.5.0 and 1.6.1, actually) before submitting the issue, but, as you noted, it has the same problem.

Ok, I just released a new version of the library (1.6.2) that upped the minimum NumPy version number to 1.19.5.

I just tried, using the reproduction steps I listed in this issue (changing the versions to 1.19.5 for numpy and 1.6.2 for pyxDamerauLevenshtein), but it fails with the same error.
It works if I don't install numpy explicitly, as pyxDamerauLevenshtein will install the latest version of numpy which satisfies its requirements, which is currently 1.20.1.
I think the minimum compatible numpy version should be 1.20.0, as all versions below that, that I tested, fail.

Thank you, @gfairchild .

Note that you're using an old version of this library. 1.6.1 is out. If I try to use NumPy 1.18.4 with it, though, it does still throw an error.

Indeed. I did try 1.6.1 (all versions between 1.5.0 and 1.6.1, actually) before submitting the issue, but, as you noted, it has the same problem.

Ok, I just released a new version of the library (1.6.2) that upped the minimum NumPy version number to 1.19.5.

I just tried, using the reproduction steps I listed in this issue (changing the versions to 1.19.5 for numpy and 1.6.2 for pyxDamerauLevenshtein), but it fails with the same error.
It works if I don't install numpy explicitly, as pyxDamerauLevenshtein will install the latest version of numpy which satisfies its requirements, which is currently 1.20.1.
I think the minimum compatible numpy version should be 1.20.0, as all versions below that, that I tested, fail.

This is really interesting. I'm not quite sure where the incompatibility comes from. I'm hesitant to require NumPy 1.20.x because 1.20.x dropped support for Python 3.6 and requires 3.7+; I'm trying to maintain compatibility with all currently-supported version of Python (3.6 doesn't hit EOL until the end of this year).
I'm still struggling to understand where exactly the incompatibilities are coming in. I think it has to do with Cython's NumPy integration being tied to specific version numbers, but I can't tell. When I create pyxdameraulevenshtein.c (i.e., via cython pyxdameraulevenshtein.pyx), my virtual environment has NumPy 1.19.5, so Cython should be making pyxdameraulevenshtein.c that relies on that version.
Part of me just wants to remove the NumPy dependency entirely because I'm not sure it's really all that useful in practice; I could pretty easily modify https://github.com/gfairchild/pyxDamerauLevenshtein/blob/master/pyxdameraulevenshtein/pyxdameraulevenshtein.pyx#L165-L180 to just use a list rather than np.ndarray, and I'm not convinced that performance would be meaningfully different. It seems to me that removing the NumPy dependency would solve multiple headaches.

I'm not quite sure where the incompatibility comes from.

The weird thing is that it happened all of a sudden, without anything related (versions of python, numpy or pyxdameraulevenshtein) changing.
The only thing I can think of is the system packages (build-essential, git, curl, unzip, in our debian-based docker image).

Part of me just wants to remove the NumPy dependency entirely

I can only speak for our case: numpy is required by many libraries we use, so having to upgrade it is a pretty big risk.
Having one less library depending on numpy lower both the risk of having to upgrade numpy and the risk of breakages when we do have to upgrade numpy.

Ok, I just completed the transition away from NumPy. The same functionality exists, but it relies on native Python objects (e.g., list, tuple) rather than NumPy ndarray (the methods have been renamed, as indicated in the changelog). This should make the build process much simpler, and there shouldn't be any meaningful performance loss since we weren't actually using NumPy for high-performance array math.
I'm about to push 1.7.0, which will make this change. I'll post once more in this issue once 1.7.0 is live, and then hopefully you can test installing this library to make sure it installs without issue.

Ok, 1.7.0 is live! @patatepartie, would you mind testing when you have a moment?

Thank you, @gfairchild 👍🏻 , especially for your responsiveness!
I tested with the reproduction steps above (without installing numpy first), and by running our unit test: everything seems ok.
We can close this issue!


Saturation correction from pax

Like the correction updated at pax 6.10.0, the same procedure can be applied to raw_records, from records onwards, data field is corrected from certain saturation effects.
This is still a working progress. Also, a part of the changes needs to be done in strax upon implementation.

This approach, that correct saturation at record level is abandoned. See the peak level approach in https://github.com/XENONnT/straxen/pull/244.