olvid: 1.6.2 -> 2.2.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/olvid/versions.
meta.description for olvid is: Secure french messenger
meta.homepage for olvid is: https://www.olvid.io
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.0.0 with grep in /nix/store/5k2w0x4dxc9pxh2gvsz246ipbk3k0q00-olvid-2.0.0
found 2.0.0 in filename of file in /nix/store/5k2w0x4dxc9pxh2gvsz246ipbk3k0q00-olvid-2.0.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

olvid

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5k2w0x4dxc9pxh2gvsz246ipbk3k0q00-olvid-2.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A olvid https://github.com/r-ryantm/nixpkgs/archive/74e4b3bad886073a5e5ac603cbaa168e891c6616.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/74e4b3bad886073a5e5ac603cbaa168e891c6616#olvid

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5k2w0x4dxc9pxh2gvsz246ipbk3k0q00-olvid-2.0.0
ls -la /nix/store/5k2w0x4dxc9pxh2gvsz246ipbk3k0q00-olvid-2.0.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

olvid

Maintainer pings
cc @Rookeur for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@ofborg eval

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/olvid/versions.
meta.description for olvid is: Secure french messenger
meta.homepage for olvid is: https://www.olvid.io
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.2.0 with grep in /nix/store/a5lp7dih4zbl484113kdy5dyds9n0f73-olvid-2.2.0
found 2.2.0 in filename of file in /nix/store/a5lp7dih4zbl484113kdy5dyds9n0f73-olvid-2.2.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

olvid

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/a5lp7dih4zbl484113kdy5dyds9n0f73-olvid-2.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A olvid https://github.com/r-ryantm/nixpkgs/archive/3da44299e85d40d34258b5bd2c7fae60a203d464.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/3da44299e85d40d34258b5bd2c7fae60a203d464#olvid

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/a5lp7dih4zbl484113kdy5dyds9n0f73-olvid-2.2.0
ls -la /nix/store/a5lp7dih4zbl484113kdy5dyds9n0f73-olvid-2.2.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

olvid

Maintainer pings
cc @Rookeur for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.


Extension controls should be next to where the extensions info is rendered in focus order

CC: @isidorn
Issue Type: Bug

Open the info for any extension. E.g, ctrl+shift+x, and go to the first result for "Code Spell Checker".

Expected: when the problems view is open at the bottom, pressing shift+tab from the top of the virtual document which renders extension info should cause focus to move to the controls for managing the extension. E.g, the view changelog and install / uninstall extension button.
Actual: I'm forced to tab through all the controls in the problems pane first, which is about 8 tab stops before getting to where I need to be to install the extension
As an aside, pressing f6 does allow you to move focus to the virtual document where the extension's info is rendered. But f6 / shift+f6 isn't able to move focus from it, so focus is trapped there when using f6 / shift + f6 to cycle through major parts of the UI. Not sure if I should open a separate issue for this.
VS Code version: Code - Insiders 1.47.0-insider (9bf6af04dcb5c2e531cedca83cd188939ca1b0db, 2020-06-26T18:55:07.038Z)
OS version: Windows_NT x64 10.0.19041

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 x 1992)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onprotected_video_decode: enabledrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.86GB (4.37GB free)

Process Argv

Screen Reader
yes

VM
17%

Extensions (15)

Extension
Author (truncated)
Version

notes
can
1.0.1

vscode-markdownlint
Dav
0.36.1

vscode-eslint
dba
2.1.5

gitlens
eam
10.2.2

prettier-vscode
esb
5.1.0

Go
gol
0.14.4

rest-client
hum
0.24.1

python
ms-
2020.6.90262

remote-wsl
ms-
0.44.4

cpptools
ms-
0.28.3

vsnotes
pat
0.7.1

rust
rus
0.7.8

markdown-preview-enhanced
shd
0.5.12

code-spell-checker
str
1.9.0

vscode-webhint
web
1.5.6

I'm forced to tab through all the controls in the problems pane first, which is about 8 tab stops before getting to where I need to be to install the extension

@sandy081 here are two issues from the comment above

Have extension descriptoin open and focused in a web view, and have the panel open. Press Shit + Tab -> focus goes to panel, it should go to the sidebar
Have extension description open and focused. Press F6 -> no effect, focus is not moved across the workbench

Notice how the F6 key is registered with no precondition here so I am not sure why the extension webview is eating up the F6 and shift + F6 key.

@mjbvz Can you please let me know if there are any web view options I can use to fix this?

@sandy081 I pushed a fix for F6.
I'm not sure about the expected shift+tab behavior. Can you please test out the next insiders build and let me know what should be happening?

F6 is working but shift+tab from web view editor is going to panel. It is also true when you open Markdown preview editor and do shift+tab.

@mjbvz can we change that the shift + tab from webviews goes to sidebar and not to the panel. That is the only remaining problem here it seems?

@mjbvz friendly ping for this since I know you were fixing some webview focus issues lately

@mjbvz friendly ping

I'm not sure how to fix this


Various fixes, add room name to scene list

I've fixed some things and added the room name to the scene list.
At least in my setup, the scenes for a single room do not have the name of the room in their name,
so they are called "Up", "Down" etc. Without adding the room name it is hard to tell the room the scene is for.
Note: Maybe the scene(collection)id should be removed from the displayed name, since it does not make sense for normal users. I haven't done this yet.

We need to double check what happens with multiple rooms for one scene. but looks ok to me

As far as I know, you can't create scene with products from multiple rooms.
You can only create a scene collection containing the predefined scenes from multiple-rooms.
For scene collections, the room name(s) are not added, they are also not grouped per room in the powerview smartphone app, so for the scene collections it is common (although not mandatory) to define unique names. Listing all the rooms for a scene collection as part of the name could easily take up too much space in the list of the Homey flow card, so I've decided not to do this.
Unfortunately the way to display the list in a Homey flow card is limited and can not be as fancy as the powerview smartphone app


Where to include message for #pragma disable?

If I am disabling a warning, what is the format of the justification message.
Here's an idea/approach but it is still ugly, better suggestions welcome:
// Justifiction: Properties initialized by Entity Framework.
#nullable disable // CS8618: Non-nullable field is uninitialized. Consider declaring as nullable.
        public ApplicationDbContext(
#nullable enable
            DbContextOptions<ApplicationDbContext>? options) : base(options) { }

// Justifiction: Properties initialized by Entity Framework.
#nullable disable // CS8618: Non-nullable field is uninitialized. Consider declaring as nullable.
        public ApplicationDbContext(
#nullable enable

or, with pragma:
// Justification: Uninitialized properties set by Entity Framework.
#pragma warning disable CS8618 // Non-nullable field is uninitialized. Consider declaring as nullable.
        public ApplicationDbContext(DbContextOptions<ApplicationDbContext> options) : base(options) { }
#pragma warning restore CS8618 // Non-nullable field is uninitialized. Consider declaring as nullable.

BTW: Questioning the value here. It makes the code really difficult to read. Breaking up a declaration with a #nullable just seems like a bad idea. Even the #pragma obfuscates what is really happening.

I think this is no longer relevant for nullable scenarios as I think they can all be suppressed using one of the solutions proposed at #88.
Pragmas are rare - certainly pragmas for C# warnings.  I think the burden of adding a justification is justified.  We shouldn't be ignoring C# warnings except perhaps during work in progress.
For code analysis warnings I recommend using attributes or global suppression files, both of which support a justification property.

As per discussion, we should document that using #pragma warning disable should include a comment indicating why the warning is being suppressed. Similarly #nullable disable should also include a comment indicating why it is being disabled.


Python stopped working (Segfault?) with minimum/maximum filter and all-zero-footprint

Just out of coincidence I got a crash with minimum and maximum filter of the ndimage package in scipy 0.18.1:
arr = np.random.randint(0, 100, (100, 100))
kernel = np.zeros((3, 3), bool)
maximum_filter(arr, footprint=kernel)  # Crash

minimum_filter(arr, footprint=kernel)  # Crash

probably not the smartest move to pass in an all-zero-footprint but an Exception would fit better.

Thanks for the report. https://github.com/scipy/scipy/pull/6877 should fix it

Thank you! I can confirm that the change fixes the error for me.


[docs] ZeRO infinity slides and blog

We can probably remove that (2021) with all the paper bullets


minimap error

Hi,
I am trying to use ampBinner_10X.py on my fastq and getting errors on the alignment step. Could you please comment on that?
Thanks!
Running code:
ampBinner_10X.py --in_fq P.fastq.gz --barcode_list 3M_Feb_737_Apr_Aug.txt --barcode_upstream_seq AATGATACGGCGACCACCGAGATCTACACTCTTTCCCTACACGACGCTCTTCCGATCT --out_prefix D8 --num_threads 24 --minimap2 /linux-x86_64-centos7/minimap2-2.15/minimap2 >run.log 2>&1 &

Error:
sh: line 1: 51263 Killed                  //minimap2-2.15/minimap2 -t 1 --for-only --eqx -c --cs -N 200 -k 5 -w 3 -n 1 -m 10 -s 40 -A 4 -x map-ont /D8.tmp.thread16.barcode_with_anchor.fasta /D8.tmp.thread16.left_tail_barcode_candidate.fastq > /D8.tmp.thread16.left_tail_barcode_compare.paf 2> /dev/null
[01/06/2021 12:48:49] ERROR: Failed to run command: /minimap2-2.15/minimap2  -t 1 --for-only --eqx -c --cs -N 200 -k 5 -w 3 -n 1 -m 10 -s 40 -A 4 -x map-ont  /D8.tmp.thread16.barcode_with_anchor.fasta /D8.tmp.thread16.left_tail_barcode_candidate.fastq > /D8.tmp.thread16.left_tail_barcode_compare.paf 2> /dev/null
[01/06/2021 12:48:49] Return value is: 35072

Hi,
Thanks for using AmpBinner.
How many barcodes do you have in the 3M_Feb_737_Apr_Aug.txt file? I guess it's 3 million?

Hi,
Thanks for using AmpBinner.
How many barcodes do you have in the 3M_Feb_737_Apr_Aug.txt file? I guess it's 3 million?

No, unfortunately, I don't have the 10X data. That is why I am using all available barcodes to figure out the used ones.
I see some of the threads got failed (4 out of 24). I re-ran the failed commands and they got finished successfully. Not sure what is next after having the missing paf files?

No, unfortunately, I don't have the 10X data. That is why I am using all available barcodes to figure out the used ones.
I see some of the threads got failed (4 out of 24). I re-ran the failed commands and they got finished successfully. Not sure what is next after having the missing paf files?

If you finished AmpBinner successfully, you will see 3 output files:
prefix.all_reads.txt, which contains the barcodes of all reads
prefix.demultiplexing.PASS.reads.txt, which contains the barcodes that were confidently assigned.
prefix.demultiplexing.statistics.txt, which is the number of reads of each barcode.

If you finished AmpBinner successfully, you will see 3 output files:
prefix.all_reads.txt, which contains the barcodes of all reads
prefix.demultiplexing.PASS.reads.txt, which contains the barcodes that were confidently assigned.
prefix.demultiplexing.statistics.txt, which is the number of reads of each barcode.

Hi @fangli08,
We don't know the exactly used barcodes. That is why I am testing all possible ones. Anyway, I successfully ran your tool on the 50,000 split lists.
WRT to the barcode upstream sequence, I think the sequence should be the one that you've mentioned in your comment. I see more reads identified with that sequence compared with an alternative sequence identified by running some code on the reads (which seems to be the second half of the sequence in your comment).
#cellular_barcode_seq	num_reads
AACACACTCAGCCTTC	1481

Using the alternative sequence, ACACTCTTTCCCTACACGACGCTCTTCCGATCT.
#cellular_barcode_seq	num_reads
AACACACTCAGCCTTC	147

Please let me know your thoughts on that.
Thanks!

Hi @fangli08,
We don't know the exactly used barcodes. That is why I am testing all possible ones. Anyway, I successfully ran your tool on the 50,000 split lists.
WRT to the barcode upstream sequence, I think the sequence should be the one that you've mentioned in your comment. I see more reads identified with that sequence compared with an alternative sequence identified by running some code on the reads (which seems to be the second half of the sequence in your comment).
#cellular_barcode_seq	num_reads
AACACACTCAGCCTTC	1481

Using the alternative sequence, ACACTCTTTCCCTACACGACGCTCTTCCGATCT.
#cellular_barcode_seq	num_reads
AACACACTCAGCCTTC	147

Please let me know your thoughts on that.
Thanks!

That looks correct.

That looks correct.

Hi @fangli08 ,
Some of the 10X barcodes I used in running "ampBinner_10X.py" were duplicates and so when I split the list, they randomly ended up in two different files. Now, I see a different number of reads for the duplicate barcodes. Any thoughts on that?
grep AACCATGAGCAGGTCA *stat*txt
xac.demultiplexing.statistics.txt:AACCATGAGCAGGTCA	113
xfu.demultiplexing.statistics.txt:AACCATGAGCAGGTCA	7

wc -l xac*spli*txt
50000 xac.10X_barcodes_splitted.txt

wc -l xfu*spli*txt
50000 xfu.10X_barcodes_splitted.txt

Hi @fangli08 ,
Some of the 10X barcodes I used in running "ampBinner_10X.py" were duplicates and so when I split the list, they randomly ended up in two different files. Now, I see a different number of reads for the duplicate barcodes. Any thoughts on that?
grep AACCATGAGCAGGTCA *stat*txt
xac.demultiplexing.statistics.txt:AACCATGAGCAGGTCA	113
xfu.demultiplexing.statistics.txt:AACCATGAGCAGGTCA	7

wc -l xac*spli*txt
50000 xac.10X_barcodes_splitted.txt

wc -l xfu*spli*txt
50000 xfu.10X_barcodes_splitted.txt

When binning the reads, AmpBinner will consider the best matched barcode and the second best matched barcode, to exclude potential misclasification due to sequencing error of the long reads.
To confidently assign a read to a barcode, the following two criteria is required:

the number of edite bases (mismatch + insertions + deletions) of the best matched barcode < 3
the number of edite bases of the second best matched barcode -  the number of edite bases of the best matched barcode > 2

For example, if a barcode list has the following two barcodes:
barcode-1: AACCATGAGCAGGTCA
barcode-2: ATCCATGAGCAGGTCA
(only one base difference)
If a read has a sequence of AACCATGAGCAGGTCA right after the barcode_upstream_seq, then barcode-1 is the best matched barcode (num_edited_bases = 0) and barcode-2 is the second best matched barcode (num_edited_bases = 1) . It meets criterion 1 but not criterion 2, so this read is not assigned to barcode-1, because it may have barcode-2 but happen to have one sequencing error in the second base.
Therefore, all the barcodes should be supplied in one file. I thought you split the list simply to test if the tool works in your environment.
Since there are too many barcodes, which use too much resources, I think you can narrow down this list by collecting all barcodes from the prefix.all_reads.txt files of the split runs, generate a new barcode list, and then remove all duplicates in the barcode list file and run the tool with all the new barcodes in one file.

When binning the reads, AmpBinner will consider the best matched barcode and the second best matched barcode, to exclude potential misclasification due to sequencing error of the long reads.
To confidently assign a read to a barcode, the following two criteria is required:

the number of edite bases (mismatch + insertions + deletions) of the best matched barcode < 3
the number of edite bases of the second best matched barcode -  the number of edite bases of the best matched barcode > 2

For example, if a barcode list has the following two barcodes:
barcode-1: AACCATGAGCAGGTCA
barcode-2: ATCCATGAGCAGGTCA
(only one base difference)
If a read has a sequence of AACCATGAGCAGGTCA right after the barcode_upstream_seq, then barcode-1 is the best matched barcode (num_edited_bases = 0) and barcode-2 is the second best matched barcode (num_edited_bases = 1) . It meets criterion 1 but not criterion 2, so this read is not assigned to barcode-1, because it may have barcode-2 but happen to have one sequencing error in the second base.
Therefore, all the barcodes should be supplied in one file. I thought you split the list simply to test if the tool works in your environment.
Since there are too many barcodes, which use too much resources, I think you can narrow down this list by collecting all barcodes from the prefix.all_reads.txt files of the split runs, generate a new barcode list, and then remove all duplicates in the barcode list file and run the tool with all the new barcodes in one file.


Compile error in typespec-python when using @pattern decorator: "Converting circular structure to JSON"

I've trimmed down my TypeSpec to try and work out where this error is coming from, and here's a small repro:
import "@typespec/http";
import "@typespec/rest";
import "@typespec/versioning";
import "@azure-tools/typespec-azure-core";

using TypeSpec.Http;
using TypeSpec.Rest;
using TypeSpec.Versioning;
using Azure.Core;
using Azure.Core.Traits;

@service({
  title: "Contoso Widget Manager",
})
@versioned(Contoso.WidgetManager.Versions)
namespace Contoso.WidgetManager;

@doc("The Contoso Widget Manager service version.")
enum Versions {
  @doc("Version 2022-08-31")
  @useDependency(Azure.Core.Versions.v1_0_Preview_2)
  `2022-08-30`,
}

// Models ////////////////////

@pattern("^[a-f0-9]{64}$")
scalar widgetId extends string;

@doc("A widget.")
@resource("widgets")
model Widget {
  @key
  @doc("The widget name.")
  @visibility("read")
  name: widgetId;
}

// Operations ////////////////////

alias ServiceTraits = SupportsRepeatableRequests &
  SupportsConditionalRequests &
  SupportsClientRequestId;

alias Operations = Azure.Core.ResourceOperations<ServiceTraits>;

interface Widgets {
  @doc("Get a Widget")
  getWidget is Operations.ResourceRead<Widget>;
}

Trying to use the typespec-python emitter on that:
$ npx tsp compile . --emit @azure-tools/typespec-python
TypeSpec compiler v0.44.0

ExternalError: Emitter "@azure-tools/typespec-python" failed!
File issue at https://github.com/Azure/autorest.python/issues

TypeError: Converting circular structure to JSON
    --> starting at object with constructor 'Object'
    |     property 'id' -> object with constructor 'Object'
    --- property 'parent' closes the circle
    at JSON.stringify (<anonymous>)
    at getClientType (file:///data/src/2.CCF/typespec-ccf/node_modules/@azure-tools/typespec-client-generator-core/dist/src/client-code-model/converters.js:388:26)
    at getSdkModelPropertyType (file:///data/src/2.CCF/typespec-ccf/node_modules/@azure-tools/typespec-client-generator-core/dist/src/client-code-model/converters.js:346:15)
    at emitProperty (file:///data/src/2.CCF/typespec-ccf/node_modules/@azure-tools/typespec-python/dist/src/emitter.js:598:25)
    at getType (file:///data/src/2.CCF/typespec-ccf/node_modules/@azure-tools/typespec-python/dist/src/emitter.js:154:42)
    at emitCodeModel (file:///data/src/2.CCF/typespec-ccf/node_modules/@azure-tools/typespec-python/dist/src/emitter.js:1058:9)
    at Object.$onEmit [as emitFunction] (file:///data/src/2.CCF/typespec-ccf/node_modules/@azure-tools/typespec-python/dist/src/emitter.js:27:21)
    at async runEmitter (file:///data/src/2.CCF/typespec-ccf/node_modules/@typespec/compiler/dist/core/program.js:532:13)
    at async compile (file:///data/src/2.CCF/typespec-ccf/node_modules/@typespec/compiler/dist/core/program.js:242:9)
    at async Object.handler (file:///data/src/2.CCF/typespec-ccf/node_modules/@typespec/compiler/dist/core/cli/cli.js:118:25)
    at runEmitter (file:///data/src/2.CCF/typespec-ccf/node_modules/@typespec/compiler/dist/core/program.js:552:19)
    at async compile (file:///data/src/2.CCF/typespec-ccf/node_modules/@typespec/compiler/dist/core/program.js:242:9)
    at async Object.handler (file:///data/src/2.CCF/typespec-ccf/node_modules/@typespec/compiler/dist/core/cli/cli.js:118:25)

After a lot of manual bisection, this seems to be coming from the use of the @patttern decorator on a custom scalar type. If I apply the decorator directly to the name field, there's no error. The error persists with every non-empty regex I've tried (including fixed strings like @pattern("bob")), so I don't think it's anything about the regex itself.
So 2 queries:

Can you add support for this @pattern(...) scalar foo extends string; type definition? It's sensible TypeSpec, and supported by the other emitters I've tried.
Can you improve the error message on errors like this? The lack of source information makes it hard to work out what the emitter has a problem with.

I have found the root cause and am fixing it now. Will update later.


Since this older project is deprecated should it be removed?

Since the current project is https://github.com/donmelton/video_transcoding, wondering if this older project "video-transcoding-scripts" should be deleted so people don't come to it by accident? Also this older project shows up higher in Google search than the active project.

I didn't know this wasn't the latest version of the project until now, so +1 from me. :D

+1

@edrozenberg @shuckster and @gingerbeardman Good points. It's a problem. I'll probably first take @JMoVS 's patch here https://github.com/donmelton/video-transcoding-scripts/pull/28 to update the README first.

OK, I've updated the README with a warning, deprecation notice and link to the new project. But I don't plan on removing it. So I'll close this now.

Works for me, thanks @donmelton


filesystem: Fix theoretical bug on Linux.

We'd try to close even a null directory.
Found by clang-tidy.
perhaps @ChristophHaag and/or @Ralith could review?

ok, that makes sense.


Add support for ARM64

It would be great to have ARM64 builds available of uwsgi on Conda so it can be run on Apple silicon. Thankfully the infrastructure seems to make this straightforward.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin please rerender

@conda-forge-admin please rerender

@conda-forge-admin please rerender

@kalefranz @ocefpaf This change bumps the build version to 4. Initially I was considering this a separate logical release than https://github.com/conda-forge/uwsgi-feedstock/pull/64 but it could make sense to combine them.
Would love your input and support to merge this so all Mac users can run uwsgi locally!
Thanks,
Cory

@conda-forge-admin please rerender

Initially I was considering this a separate logical release than https://github.com/conda-forge/uwsgi-feedstock/pull/64 but it could make sense to combine them.

I'm a bit lost on why #64 is needed. See my question there.

Would love your input and support to merge this so all Mac users can run uwsgi locally!

+1, if you change to build number 3 we can merge this right away.

Initially I was considering this a separate logical release than #64 but it could make sense to combine them.

I'm a bit lost on why #64 is needed. See my question there.

Would love your input and support to merge this so all Mac users can run uwsgi locally!

+1, if you change to build number 3 we can merge this right away.

Thanks for the fast response and review. Updated build number!


no ir file generated when set extra_output_files = [ "ir" ]

Component
Forge
Have you ensured that all of these are up to date?

[ ] Foundry
[ ] Foundryup

What version of Foundry are you on?
forge 0.2.0 (dedc31e 2023-04-23T07:49:04.825009295Z)
What command(s) is the bug in?
forge build
Operating System
Linux
Describe the bug
after invoke forge build, no .ir files generated in the out dir.
but when set extra_output_files = ["irOptimized" ], the .iropt file is generated.

Sorry, what is the issue here? By default the IR is not generated, it must be specified like you did, then the file is generated

@mds1 I have set extra_output_files = [ "ir" ], no IR file generated.

Ah, yea according to the docs this should be supported, but you're right, I was able to reproduce this. cc @mattsse

Quick work around: include both options
extra_output = ['ir']
extra_output_files = ['ir']


misc/cgo/test: TestCrossPackageTests started to fail on release branches

The TestCrossPackageTests test is failing on the linux-386-longtest builder on the release-branch.go1.14 branch, from https://build.golang.org/?repo=&branch=release-branch.go1.14:
##### ../misc/cgo/test
--- FAIL: TestCrossPackageTests (0.84s)
    pkg_test.go:67: go test: exit status 2
        panic: runtime error: index out of range [2] with length 2

        goroutine 359 [running]:
        cmd/go/internal/work.(*Builder).cgo(0xad1db80, 0xb20db80, 0xb2947b0, 0x22, 0xb1199b0, 0x24, 0x0, 0x0, 0x0, 0x0, ...)
        	/workdir/go/src/cmd/go/internal/work/exec.go:2715 +0x3b42
        cmd/go/internal/work.(*Builder).build(0xad1db80, 0xb20db80, 0x0, 0x0)
        	/workdir/go/src/cmd/go/internal/work/exec.go:597 +0xdd0
        cmd/go/internal/work.(*Builder).Do.func2(0xb20db80)
        	/workdir/go/src/cmd/go/internal/work/exec.go:118 +0x7c
        cmd/go/internal/work.(*Builder).Do.func3(0xafd1370, 0xad1db80, 0xb40ab40)
        	/workdir/go/src/cmd/go/internal/work/exec.go:178 +0x63
        created by cmd/go/internal/work.(*Builder).Do
        	/workdir/go/src/cmd/go/internal/work/exec.go:165 +0x2dd
FAIL
exit status 1
FAIL	misc/cgo/test	2.727s

(Full log at https://build.golang.org/log/9e85634f5e633118d04a37b6ec4acc8af7a0ec06.)
It seems to have started after the most recent minor release, although there were some unrelated failures that may have masked when it first started. It doesn't seem to happen on the release-branch.go1.15 branch at https://build.golang.org/?repo=&branch=release-branch.go1.15. Update: It happened on release-branch.go1.15 branch too after CL 288112 was submitted.
However, it is happening on TryBots for both Go 1.15 and 1.14 release branches, see https://go-review.googlesource.com/c/go/+/288115/1#message-fc09f380d12c52f7cee4887d29ce110b4f7083b3 and https://go-review.googlesource.com/c/go/+/288112/2#message-74b2918d949d3bc7758e86c7a7a41db5e996b8de. (CC @neild.)
CC @rolandshoemaker, @ianlancetaylor, @jayconrod.

I took a quick look at this, but I wasn't able to reproduce it by running GO_TEST_SHORT=0 ./run.bash on a linux-386-longtest gomote on the release-branch.go1.14 branch.
The panic occurs in a place where we validate //go:cgo_ldflag pragmas in .go files generated by cgo. The the flags in the CGO_LDFLAGS environment variable as well as flags in #cgo LDFLAGS directives in source files should be written with these pragmas. We only need to validate the flags from #cgo LDFLAGS, since the user is in control of CGO_LDFLAGS.
The panic would occur if the flags from CGO_LDFLAGS weren't written as a consecutive sequence of //go:cgo_ldflag pragmas. I'm not sure why that would happen on this particular builder. If there's a way to manually reproduce this, we should be able to see what's going wrong with the generated files.

I'm able to reproduce the problem about 50% of the line on a linux-386-longtest gomote by running, in the /workdir/go/misc/cgo/test directory, the command go test -test.run=TestCrossPackageTests -test.v.
At least in one occasion, the error occurs when the test, which itself invokes go test, is building a copy of the directory misc/cgo/test/testdata/issue9026.  The variable flags, derived from the //go:cgo_ldflag comments in the generated files, is ["-g" "-O2"].  That is correct.  The variable cgoLDFLAGS, which should come from the environment variable, is ["-g" "-O2" "-lm"].  That is not correct.  I can't see any reason why it would contain "-lm".
The extraneous "-lm" may be coming from misc/cgo/test/testdata/issue8756.go or from misc/cgo/test/testdata/issue8756/issue8756.go, both of which have a line #cgo LFLAGS: -lm.  I'm not yet sure which or how.

The problem is the introduction of cgoEnvCache and the cgoEnv method.  It causes sharing of slices across different executions, so the environment passed to cmd/cgo varies.

It's fixed on tip by https://golang.org/cl/285873, which drops cgoEnvCache.
@jayconrod Since you already fixed this on tip, leaving for you to decide if we should backport that fix (which was for #43808 and only coincidentally fixes this bug).  Let me know if I didn't explain the problem.

In that case, merging CL 285952 and CL 285954 will probably fix the issue. They revert the change that added cgoEnvCache. I opened backport CLs to fix a different regression.

Thank you for diagnosing this issue. CL 285952 and CL 285954 have been submitted now, which remove cgoEnvCache and so far this test has been passing as expected.
I believe this issue is resolved. We can reopen if we see this again, or if someone thinks there should be a test added to Go 1.16 or 1.17, if there's insufficient test coverage.


[Sync] [Init] sync before firmware is available is noisy and wasteful

When FarmBot syncs it needs to do a bunch of stuff as side effects:

Read all peripherals
Index FarmEvents, Regimens etc
Start checking PinBindings

If any of those things require the Firmware server to be up and running, it has to fail and try again in the future. This has the effect of all the things requiring the Firmware to sync up and all fail because they are all blocking each other.

This has been fixed in V8.


Tutorial craftsman new:domain CarbonKitchen.yaml fails on Linux

Creating a template file by copying the one provided in tutorial section "Environment and Swagger Setup", and even placing it in the same directory I run the command craftsman new:domain  from leads to the following output:
No such file or directory
An unhandled exception occurred when running the API command.
The error details are:
No such file or directory

Nevertheless the following empty directory structure gets created:
CarbonKitchen
└── RecipeManagement
    ├── src
    └── tests

Further technical details
Craftsman version (craftsman version):
v<IP_ADDRESS>

what version of .net do you have installed? -- dotnet --version

dotnet --version
5.0.202

not able to repo, closing


test(search): fix the search by barcode test

The search product by barcode test is fixed.
#23

Resolves #22


Update normalize.js

Revert treatment of 'ph' so it can be dealt with separately in general-use mode.  Add mapping of apostrophe key to forward slash to allow non-technical users to be able to type an apostrophe or forward slash on the keyboard and have it render an 'apostrophe like' character and not error out.

Merged into #20 for review.


[AutoDiff] Part 6: Implement adjoint synthesis

This patch implements adjoint synthesis for automatic differentiation. An adjoint function corresponds to a primal function, representing the reverse sweep on the original function.
See Automatic Differentiation in Swift for more information about the adjoint function.
Adjoint synthesis consists of three parts:

AdjointValue (#18149) caches adjoint values that can be trivially optimized according to their mathematical properties.
AdjointRematCloner rematerializes non-checkpointed primal values on demand.
AdjointEmitter performs a reverse sweep on the original function, emitting the adjoint code for values that are active.

@swift-ci please test tensorflow

Does this PR enable e2e single basic block autodiff? Is it possible to add some tests?

Adding tests soon.

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

Spending some time to fix bugs recently. I'm gonna check this in and add follow-up patches later this week.


Create DhruvGupta.md

excited!!

Use markdown please.

Great to hear that you have interests in such a variety of fields, do start exploring from now itself @dhruvgupta1999 and do reach out on slack for any help.


Default Animation Left to Right

On iOS and Android, it seems the default animation for a content page that has not implemented IAnimationPage seems to be opposite what I would expect.  I purchased the control to use on just a few pages, but in order for it to behave correctly, I have to implement the interface on every page.
I am using FreshMVVM with a custom IFreshNavigationService to inject the AnimationNavigationPage.  I don't think that is causing the issue though as when I explicitly specify the animation I want, they work fine.

Hi !  i'm working on new version and . Component will be available for some days.


Rename "azure-pipelines.yml" to ".azure-pipelines.yml"

hi,
I started splitting it into several files
https://github.com/chipitsine/SoftEtherVPN/blob/azure/azure-pipelines.yml
did not finish yet

Excellent!


DOC-2620

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[* ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

https://harness.atlassian.net/browse/DOC-2620

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Preview environment: https://ci.pr.harness.io/pr-758

Preview environment: https://ci.pr.harness.io/pr-758


irritating donation pop-up

This is an idea for adding an un-install button to the irritating balloon that pops up asking for PayPal donations.
 It can save them a few button clicks to un-install this plugin (like I just did).
Hopefully others will enjoy this new feature as well.

@JunkMail4MJD There is no need to do that.
IDE allows to turn off permanently any notifications from the specific plugin/group:

Actually I find the request more irritating than .ignore's behaviour; obviously, that person does not know how much work a plugin is, or how much it actually does.

I see the opportunity for a small UX improvement here: Rename the entry from "IGNORE_GROUP_UPDAT" to something human-readable, like ".ignore donation reminder".


Add method to retrieve current time entry

A small PR to retrieve the current running time entry

Beautiful work @machiel - just what I was looking to add! Beat me to the mark! 💯

Thanks!


docs: Update all documentation to fix typos and improve readability

Update all documentation pages to fix typos and improve readability/consistency throughout.
Summary of documentation changes:

Reworked intro text in all sections for consistency
Consistency in capitalization
Github -> GitHub
CICD -> CI/CD
check the -> refer to the
GCP -> Google Cloud
Other various readability and consistency fixes

Please review and ensure that I have not changed the meaning of any substantial edits.
Also, thanks for all of the great documentation and explanations for this CLI tool!

@koverholt thank you very very much for this contribution!! I definitely have to improve my written English!

thank you very very much for this contribution!! I definitely have to improve my written English!

You are very welcome! Don't underestimate yourself, your 1) explanations of complex concepts and 2) comprehensive coverage of the CLI functionality made these docs super easy to work with, and you'll notice my PR was mostly minor/nitpicky details. 😁


Login page feature

Test three cases: Log in with a wrong password, wrong username, and successful login.
Should be show the suitable UI base on the role of the account we log in.
Status: Pass


{{#unless @last}} does not work

Hello,
I am trying to generate a structured JSON output : a list of dictionaries.
If I do this :
program = guidance("""[{{#geneach 'characters' num_iterations=3}}
    {
        "name": "{{gen 'name'}}",
        "age": "{{gen 'age'}}"
    },{{/geneach}}
]""")
output = program()

I get that :
[
    {
        "name": "John",
        "age": "27"
    },
    {
        "name": "Jane",
        "age": "25"
    },
    {
        "name": "Bob",
        "age": "30"
    },
]

I am not happy with this output because of the last comma : json.loads(output.text) will fail because of it. The handlebars solution would be :
program = guidance("""[{{#geneach 'characters' num_iterations=3}}
    {
        "name": "{{gen 'name'}}",
        "age": "{{gen 'age'}}"
    }{{#unless @last}},{{/unless}}{{/geneach}}
]""")
output = program()

But I get the following error :
KeyError: "Command/variable '@last' not found! Please pass it when calling the program (or set a default value for it when creating the program)."

Note that if I replace @last by @first it works as expected : there is a comma after each element of the list except the first one. Would it be possible to fix this ?
Thanks,
Simon

How are you able to run this at all?.. I read here that it stopped to work with new OPENAI versions and I also can not run.

We did away with handlebars support in the new release, hopefully pure python code is much cleaner :)


connection failed _ERROR

Did Google change something ?
I can connect to my network but it returns an error
Connected to ****** IP address: <IP_ADDRESS> connection failed _ERROR connection failed _ERROR

Hmm...
In my environment, it can get an mp3 URL without any problem.
And this library connects to only google, not Google Home.
So the message was written by other library such as esp8266-google-home-notifier.

Ok thanks
I thought I would also read the audio ... So it gives only the URL back ?

yes, this library just gets tts mp3 url from google tranlate.
what tries to connect to google home is other library you are using.


Make notifications less samey

Ways to do this:

When a single event has taken place, change title to reflect this

Could be "New thread created!" or "New message in ..."

Use freed up space in body of notification for the message or thread text
Take user directly to the specific thread on click
Show multimedia?

First three points done in aeb5273.
Last one far too much work for what it is.


Add sort on equivalent sort call simplifications

Implements #155 and add the same checks for sortBy, sortWith with equal arguments

Nice :blush:


support reserved pid for kube and system

support reserved pid for kube and system.
reference：https://kubernetes.io/docs/concepts/policy/pid-limiting/#node-pid-limits

Hi @Cweiping
These are generated documents. Has the equivalent change already been made upstream?
(if you're not sure what that question means, that's OK - we can explain in more detail if it's not clear)

@sftim kubelet doc has been maintained manually since they changed their intialization code a long time ago.

/lgtm

/approve


No such resource AWS::WAFv2::IPSet

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the
Amplify Console GitHub Issue Tracker

Describe the bug
A clear and concise description of what the bug is.
Added WAFv2 resources to my project's API Gateway CloudFormation template, attempted to get the WAFv2 IPSet ARN attribute to reference in the WAFv2 WebACL IPSetReferenceStatement.Arn property, and get the following error when I attempt to push: No such resource AWS::WAFv2::IPSet. After discussing this with the CloudFormation & Uluru teams, we found that if I import as a new stack via the UI, the same template provisions successfully.
Amplify CLI Version
You can use amplify -v to check the amplify cli version on your system
4.13.1
To Reproduce
Steps to reproduce the behavior or terminal output if applicable

Init a new project with Amplify CLI
Add API
Add the following resource in the API CloudFormation template "IPSetV2": {
   "Type": "AWS::WAFv2::IPSet",
   "Properties": {
     "Addresses": ["[insert test IPv4 CIDR block]"],
     "Description": "Test IPSetV2",
     "IPAddressVersion": "IPV4",
     "Name": "test-ipsetv2",
     "Scope": "REGIONAL"
   }
 },

Add the following output in the API CloudFormation template "IPSetV2": {
   "Description": "The WAFv2 IPSet",
   "Value": {
     "Fn::GetAtt": [
       "IPSetV2",
       "Arn"
     ]
   }
 }

amplify push -y
Receive error: No such resource AWS::WAFv2::IPSet

Expected behavior
A clear and concise description of what you expected to happen.
Amplify CLI should not throw an error for a valid get attribute call.
Screenshots
If applicable, add screenshots to help explain your problem.
Screenshot 1: Console error

Screenshot 2: CloudFormation Console: Template tab when template is imported via UI

Screenshot 3: CloudFormation Console: Outputs tab when template is imported via UI

Desktop (please complete the following information):

OS: [e.g. Mac/Windows/Ubuntu]
Ubuntu 18.04.3 LTS
Node Version. You can use node -v to check the node version on your system
v12.14.0

Additional context
Add any other context about the problem here.
N/A

@tdslinden With the latest version of the CLI I was able to deploy an IPSetV2 resource. Please make sure to add this resource under the "Resource" key
"Resources": {
		"IPSetV2": {
			"Type": "AWS::WAFv2::IPSet",
			"Properties": {
				"Addresses": [
					"<IP_ADDRESS>"
				],
				"Description": "Test IPSetV2",
				"IPAddressVersion": "IPV4",
				"Name": "test-ipsetv2",
				"Scope": "REGIONAL"
			}
		},

If you're still stuck, you can send your Cloudoformation file to<EMAIL_ADDRESS>and we can dig deeper.

@kaustavghosh06, you only followed half the steps to reproduce, which is why you failed to duplicate the issue.
Also, just updated the CLI and confirmed that I can still duplicate. Will send an email as requested.

Reproduced the issue.
The Amplify CLI uses "cfn-lint" to validate the Cloudformation template file.
In this particular case, there is an issue with its validation.

This is still an issue.

The same happens to me with AWS::WAFv2::WebACL
Invalid CloudFormation template: /home/****/****/amplify/backend/customResources/WAF/template_WAF.yaml
No such resource AWS::WAFv2::WebACL

But, the good thing to me is, the resource is being created and works fine.


Test cases not found if using CommonJS instead of ES6

I am new to node:test and wanted to use the extension to execute my first node unit tests.
I am usually using CommonJS module style for my node.js projects.
But i was only able to see the tests on the Testing window in VSCode if i use the ES6 module style.
Setup:
OS: Ubuntu 22.04
VS-Code: v1.90.1
Node.js: v22.3.0
node:test runner: v1.5.1
Test file (ES6): /test/test.js
import { test } from "node:test";

test("will pass", () => {
  console.log("hello world");
});

test("will fail", () => {
  throw new Error("fail");
});

Test file (CommonJS): test/test.js
const test = require('node:test');

test("will pass", () => {
  console.log("hello world");
});

test("will fail", () => {
  throw new Error("fail");
});

When i run the node:test's with the CLI it works with CommonJS module style.

You want to change
const test = require('node:test');

to
const { test } = require('node:test');

Thanks a lot for this tip, this works.
Even if i don't really know what the issue with
const test = require('node:test');
is.

We don't handle that case, I didn't know they default-export the test function. I'll add support for that.


Missing documentation link

F´ Version
3.x

Affected Component
n/a

Problem Description
There are some broken links in the README documentation:
How to Reproduce
See the documentation and user's guide links.

Expected Behavior
A description of the expected behavior.

Fixed by https://github.com/fprime-community/fprime-gds/pull/110


Set XMLHttpRequest manually

Hi,
this PR extends Global in such a way that XMLHttpRequest can be passed into it if it is not available (during server-side rendering for example). Libraries like this could then be used.
Usage:
import { Global } from 'oidc-client';

Global.setRequest(myNewXMLHttpRequestObject);

#243

I manually merged this since it took me forever to get to it and all the merge conflicts. Thanks.

Sorry for that - and thanks again :-)


[BUG] Poor error message on unclosed multi-line string

Describe the bug
When compiling a file with an unclosed multiline string the error message is confusing and unhelpful:

unclosedstr.pyx:2:0: Unexpected token None:'' in string literal

Code to reproduce the behaviour:
"""

Expected behaviour
An improved error message
OS
Linux
Python version
3.11
Cython version
Current master
Additional context
No response

.take


Can't access the webpage on my laptop connected to my android server through mobile hotspot

I have created the android server on my mobile phone and on the same phone I have opened my hotspot. Upon connecting my laptop to my mobile hotspot I can't access that webpage by my mobile's ip address. Please help me how I can do that?
Note: Right now I can only access the webpage on my mobile's localhost.

Check the IP address of your mobile.
Check the port you've started the hotspot at
In your browser go to http://ip:port/

I have the same problem，have you  fixed it?

Same here, with SimpleWebServer implementation only localhost seems to work, but no access through IP address (e.g. in browser), even on the same device. ERR_CONNECTION_REFUSED error is shown in browser and says "[IP address] refused to connect.". Is this a result of having no CORS settings set (cors = null) or should it work anyway?

Try setting your server on <IP_ADDRESS> rather then localhost in your code and
check carefully that you enter your mobile's private ip in your browser.
This worked for me.
On Thu, Sep 12, 2019, 10:18 AM AndreasGabel<EMAIL_ADDRESS>wrote:

Same here, with SimpleWebServer implementation only localhost seems to
work, but no access through IP address (e.g. in browser), even on the same
device. ERR_CONNECTION_REFUSED error is shown in browser and says "[IP
address] refused to connect.". Is this a result of having no CORS settings
set (cors = null) or should it work anyway?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NanoHttpd/nanohttpd/issues/556?email_source=notifications&email_token=AKKLEUEEPO4IPFCAAN3VMD3QJHCYVA5CNFSM4ISQOWWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6QUOLY#issuecomment-530663215,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKKLEUHL2Q7XU6FTMHZAMATQJHCYVANCNFSM4ISQOWWA
.


Removal of forced software layer rendering

Commit 95fc88e attempted to rectify artefacts being drawn using a forced software layer rendering. This process has had significant consequences on performance (#174) and introduced breaking rendering changes, for instance card views are no longer rendered correctly (see screenshots below). Furthermore, the developer documentation states that "Software layers should be avoided when the affected view tree updates often." which in the case of a chat interface can be very frequent.
A suggestion to prevent the artefacts from being rendered, that may need to be put in the usage docs/faq, you can instead apply the descendantFocusability="beforeDescendants" on the layout container to ensure it has focus rather than a descendant message bubble.
With software layer rendering

Without software layer rendering

Thanks @joostfunkekupper you are right. #174

No problem @bevzaanton. I noticed that this was also done in the ShapeImageView (bafd2e1). Might be worth removing it there as well. I can create a PR for that if necessary.


line breaks with two spaces or '' not working

Hi @Keisir ,
It looks like this module breaks the support for inserting line breaks with two spaces or '\' at the end of lines in quotes.
Could you look into it?
How to reproduce
The first line ends with two spaces:
> Each time you increase the amount of code, your software grows exponentially more complicated.
> -- DHH, Getting Real

Expected behavior
It should insert
 at the end of the first line like so:

Each time you increase the amount of code, your software grows exponentially more complicated.
-- DHH, Getting Real

Actual behavior

 is not inserted:

Hey,
I'm going to have a look at this next weekend.

I started looking into this. I may have found a solution but haven't had a chance to try it out yet. I will do it tomorrow.


Cant put antique laser back into glass box.

Description

Cant put it back in after taking it out.
Reproduction

Glass box
Open glass box
Take the antique laser
Try to put it back in
Cant do it.
Screenshots

Additional context

😔

On that note, a fake antique laser gun would make for a fun uplink item.


[Feature]: Discontinue direct PR from web-infra-dev/modern.js

What problem does this feature solve?
At present, any member of the web-infra-dev organization can push a branch directly to the web-infra-dev/modern.js, facilitating easy collaboration. However, I propose disabling this method of direct merging. Instead, I suggest almost contributors should fork the repository and submit changes via a PR. This approach could lead to a cleaner branch structure in the master repository.
What does the proposed API look like?
nothing

Does GitHub provide a switch to control this?

Sometimes we need to push a branch to the main repository, for example, when we release the canary version via actions.

Sometimes we need to push a branch to the main repository, for example, when we release the canary version via actions.

This would be an infrequent operation for most contributors, and we can assign additional permissions to those who require them.

The members of web infra org can push to this repo and release canary version. Community contributors need to fork this repo to submit a PR.
This is a common approach on GitHub and it allows us to limit the branch numbers of the main repo.


Conda environment

Need to remove the prefix and use the --from-history flag to work cross platforms

Fixed in 47ca274afdd93f5332165e36a3aa9f0e90cf8ab0


v2.2.0 breaks inheritance for user defined classes

from textx.metamodel import metamodel_from_str

grammar = """
MyModel: 'model' name=ID
  connections+=Connection
  sender+=Sender
  receiver+=Receiver;

Sender:
  'outgoing' name=ID 'over' connection=[Connection|ID];

Receiver:
 'incoming' name=ID 'over' connection=[Connection|ID];

Connection:
  'connection' name=ID
  'port' port=STRING
  'ip' ip=STRING;
"""

modelstring = """
model Example
connection conn port "1" ip "<IP_ADDRESS>"

outgoing out0 over conn
incoming in0 over conn

"""
class ConnectionHandler(object):
    def _init_(self):
        print('')

    def awesomeMethod4SenderAndReceiver(self):
        print("I am really important for Sender and Receiver")

class Sender(ConnectionHandler):
    def _init_(self, name=None, port=None):
        print('')

class Receiver(ConnectionHandler):
    def _init_(self, name=None, port=None):
        print('')

mm = metamodel_from_str(grammar, classes=[ConnectionHandler, Sender, Receiver])
m = mm.model_from_str(modelstring)

This minimal example results in the following error:
Traceback (most recent call last):
  File "C:\Users\v040226\Workspaces\francaWorkspace\ErrorReproduce\src\main.py", line 47, in <module>
    m = mm.model_from_str(modelstring)
  File "C:\Program Files\Python38\lib\site-packages\textx\metamodel.py", line 584, in model_from_str
    model = self._parser_blueprint.clone().get_model_from_str(
  File "C:\Program Files\Python38\lib\site-packages\textx\model.py", line 282, in get_model_from_str
    model = parse_tree_to_objgraph(
  File "C:\Program Files\Python38\lib\site-packages\textx\model.py", line 680, in parse_tree_to_objgraph
    model = process_node(parse_tree)
  File "C:\Program Files\Python38\lib\site-packages\textx\model.py", line 498, in process_node
    process_node(n)
  File "C:\Program Files\Python38\lib\site-packages\textx\model.py", line 564, in process_node
    value = process_node(n)
  File "C:\Program Files\Python38\lib\site-packages\textx\model.py", line 483, in process_node
    parser.metamodel._init_obj_attrs(inst)
  File "C:\Program Files\Python38\lib\site-packages\textx\metamodel.py", line 452, in _init_obj_attrs
    for attr in obj.__class__._tx_attrs.values():
  File "C:\Program Files\Python38\lib\site-packages\textx\model.py", line 315, in _getattribute
    return super(user_class, obj).__getattribute__(name)
  File "C:\Program Files\Python38\lib\site-packages\textx\model.py", line 311, in _getattribute
    return user_class._tx_obj_attrs[id(obj)][name]
AttributeError: type object 'ConnectionHandler' has no attribute '_tx_obj_attrs'

We are currently not sure on how to fix this issue

Thanks for the report. Would you be able to make a PR with failing regression test following the layout of other regression tests here.

Is ConnectionHandler part of your grammar as well ? In the example sketched above, the user class is not used in the Grammar?

@goto40 as shown in the example, it is not.
With the https://github.com/fgro93/textx-pyecoregen we have inheritance with classes that are not part of the grammar.
@igordejanovic I don't think I have time to write tests. I'm sorry :(

Don't worry, we will try to reproduce it...

Analysis ongoing: https://github.com/textX/textX/pull/273

Why do you need a used defined class as base class which is not defined in the grammar? See pull request...

Generating user classes from ECore meta-models: https://github.com/textX/textX/issues/115
That's why we have base classes which are not defined in the grammar

Classes not found in the grammar and thus not instantiated by textX shouldn't be supplied in the list of classes in the metamodel_from* calls. Accepting other classes might open a window for hard to trace bugs. I suggest solving this issue by catching this error and trowing appropriate exception with the link to the docs where rationale is explained like we did for unhashable name recently.

Couldn't we somehow remove/ignore such classes automatically?

We really should not do that as most of the time passing an unused class is an error and we should treat it as such. In my view the use-case reported here is very specific for pyecoregen and should be handled there.
Imagine a user mistakenly passing a wrong class (might be named similarly as the one he actually wanted) and then wonders why his class is not working.
An equivalent example in Python would be:
params = {'a': 2, 'b': 3}
def f(a):
    print(a)

f(**params)

Python will complain about getting a parameter b which is not expected. This behavior in my view is right. If Python would ignore unused params it would really be very bad.
The only problem I see here is that the error reported should be better. But I would leave the check for unused classes in place.
Of course, I'm open for discussion.

OK.

Note: I have not correctly documented where _tx_obj_attrs is set. Need to rework the comments...

Please have a look at the current master, if the fix works for you. You need to use the callback solution (see metamodel.md and/or the unit tests).


Constant e2e failures against unreleased Kong with Kuma

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Recently the daily e2e run against unreleased Kong fails on the 2 cases running with kuma:
https://github.com/Kong/kubernetes-ingress-controller/actions/runs/7683416231/job/20938806328#logs

TestDeployAllInOnePostgresKuma
TestDeployAllInOneDBLessKuma
Also the validate Kong image tests against kong/kong-gateway-dev:<IP_ADDRESS>-rc1 fails in the same cases:
https://github.com/Kong/kubernetes-ingress-controller/actions/runs/7675532503
The behaviors in the tests are the same: requests are only sent to 2 backend pods but expected all 3 pods:

    kuma_test.go:36: waiting for route from Ingress to be operational at http://<IP_ADDRESS>/echo and forward traffic to all 3 backends
    kuma_test.go:36:
        	Error Trace:	/home/runner/work/kubernetes-ingress-controller/kubernetes-ingress-controller/test/e2e/helpers_test.go:488
        	            				/opt/hostedtoolcache/go/1.21.6/x64/src/runtime/asm_amd64.s:1650
        	Error:      	"map[With IP address <IP_ADDRESS>.

        	            	:{} With IP address <IP_ADDRESS>.

        	            	:{}]" should have 3 item(s), but has 2

Expected Behavior
e2e test passes.
Steps To Reproduce
Run e2e tests TestDeployAllInOnePostgresKuma or TestDeployAllInOneDBLessKuma

Kong Ingress Controller version
`latest` image  3.0.2.

Kubernetes version
All supported k8s versions in this run:
https://github.com/Kong/kubernetes-ingress-controller/actions/runs/7675532503
- 1.29.0
- 1.28.0
- 1.27.4
- 1.26.6
- 1.25.11

Anything else?
No response

ref: #5496

Copy-pasting @rainest's investigation notes from Slack for posterity:

All Kuma tests failed on a check that uses multiple replicas for the test service. It should distribute requests across all three replicas, but only distributed across two. This needs more investigation, but IDK how it'd break. AFAIK it should just be a standard upstream with three targets and no special LB configuration.

distribution is ostensibly entirely up to Kuma in that test: those services don't use separate targets, they use the service hostname, so that Kuma can intercept them and forward them on to some upstream. it does look like this was some change to the gateway, however--we started seeing failures on the latest dev image as of the 22nd (https://github.com/Kong/kubernetes-ingress-controller/actions/workflows/e2e_nightly.yaml) and there haven't been any changes to the Kuma chart (so no new version of the mesh proxy) since the 10th. that suggests some change in how the gateway is sending requests that prompts Kuma to distribute them unevenly.

it doesn't appear to be sticky based on which kong instance originated the request. if I send through the pods individually, one distributes requests to only one (of three) upstream endpoints, and the other distributes to two:
root@cool:/# for i in `seq 1000`; do curl -s <IP_ADDRESS>:8000/echo >> /tmp/one; done
root@cool:/# for i in `seq 1000`; do curl -s <IP_ADDRESS>:8000/echo >> /tmp/two; done
root@cool:/# sort /tmp/one | uniq -c
 1000
  1000 With IP address <IP_ADDRESS>.
root@cool:/# sort /tmp/two | uniq -c
  1000
   504 With IP address <IP_ADDRESS>.
   496 With IP address <IP_ADDRESS>.

scaling tests indicate that we consistently only see two of the upstream replicas per proxy instance, but each instance sees a different set of endpoints. if I wait around for a while, that chosen set of upstream endpoints can change, suggesting the chosen set persists for the keepalive timeout. although scaling either the proxy or upstream replicas has no noticeable effect, increasing the worker count does. my intuition from that is that a worker delivers requests to the same endpoint for the duration of the keepalive period, though IDK what would have changed (were workers not maintaining keepalive connections to the mesh proxies before?)
// scaled echo replicas to 10
root@cool:/# for i in `seq 1000`; do curl -s <IP_ADDRESS>:8000/echo >> /tmp/noot; done
root@cool:/# for i in `seq 1000`; do curl -s <IP_ADDRESS>:8000/echo >> /tmp/poot; done
root@cool:/# sort /tmp/noot | uniq -c
1000
497 With IP address <IP_ADDRESS>.
503 With IP address <IP_ADDRESS>.
root@cool:/# sort /tmp/poot | uniq -c
1000
498 With IP address <IP_ADDRESS>.
502 With IP address <IP_ADDRESS>.

// scaled kong proxy replicas to 4
root@cool:/# for i in `seq 1000`; do curl -s <IP_ADDRESS>:8000/echo >> /tmp/1; done
root@cool:/# for i in `seq 1000`; do curl -s <IP_ADDRESS>:8000/echo >> /tmp/2; done
root@cool:/# for i in `seq 1000`; do curl -s <IP_ADDRESS>:8000/echo >> /tmp/3; done
root@cool:/# for i in `seq 1000`; do curl -s <IP_ADDRESS>:8000/echo >> /tmp/4; done
root@cool:/# sort /tmp/1 | uniq -c
1000
492 With IP address <IP_ADDRESS>.
508 With IP address <IP_ADDRESS>.
root@cool:/# sort /tmp/2 | uniq -c
1000
522 With IP address <IP_ADDRESS>.
478 With IP address <IP_ADDRESS>.
root@cool:/# sort /tmp/3 | uniq -c
1000
487 With IP address <IP_ADDRESS>.
513 With IP address <IP_ADDRESS>.
root@cool:/# sort /tmp/4 | uniq -c
1000
488 With IP address <IP_ADDRESS>.
512 With IP address <IP_ADDRESS>.

// worker count scaled to 5
root@cool:/# for i in `seq 1000`; do curl -s <IP_ADDRESS>:8000/echo >> /tmp/ppp; done
root@cool:/# sort /tmp/ppp | uniq -c
1000
176 With IP address <IP_ADDRESS>.
239 With IP address <IP_ADDRESS>.
189 With IP address <IP_ADDRESS>.
187 With IP address <IP_ADDRESS>.
209 With IP address <IP_ADDRESS>.

Reproduction steps:
# Install Kuma.
helm install kuma kuma/kuma

# Create `kong` namespace
kubectl create ns kong

# Enable Mesh in `kong` and `default` namespace.
kubectl label ns kong kuma.io/sidecar-injection=enabled
kubectl label ns default kuma.io/sidecar-injection=enabled

# Install KIC+Kong 3.6 (with OpenResty bumped) using the all-in-one manifests.
curl https://raw.githubusercontent.com/Kong/kubernetes-ingress-controller/v3.0.2/test/e2e/manifests/all-in-one-dbless.yaml | \
  sed -r 's/kong:3.4/kong\/kong-gateway-dev:dc683d70ced4795471a5416773b14e9771ae8a6c/g' | \
  kubectl apply -f -

# Deploy an echo server Deployment with 3 replicas and expose it via Ingress.
echo 'apiVersion: apps/v1
kind: Deployment
metadata:
  name: echo
  labels:
    app: echo
spec:
  replicas: 3
  selector:
    matchLabels:
      app: echo
  template:
    metadata:
      labels:
        app: echo
    spec:
      containers:
        - name: echo
          image: kong/go-echo:0.3.0
          ports:
            - containerPort: 1027
          env:
            - valueFrom:
                fieldRef:
                  fieldPath: status.podIP
              name: POD_IP
---
apiVersion: v1
kind: Service
metadata:
  labels:
    app: echo
  name: echo
spec:
  type: ClusterIP
  selector:
    app: echo
  ports:
    - port: 1027
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: echo-ingress
  annotations:
    konghq.com/strip-path: "true"
    konghq.com/methods: "GET"
spec:
  ingressClassName: kong
  rules:
    - http:
        paths:
        - path: /echo
          pathType: Prefix
          backend:
            service:
              name: echo
              port:
                number: 1027' | kubectl apply -f -

# Get Kong proxy IP.
PROXY_IP=$(kubectl get svc --namespace kong kong-proxy -o jsonpath='{.status.loadBalancer.ingress[0].ip}')
echo "$PROXY_IP"

# Send 100 requests to /echo endpoint and count unique responses (there will be Pod IPs in the response).
for i in `seq 100`; do curl -s "$PROXY_IP"/echo >> /tmp/hit_ips_with_bump; done
cat /tmp/hit_ips_with_bump | sort | uniq -c

# Get output only with 2 Pod IPs while 3 were expected:
# cat /tmp/hit_ips_with_bump | sort | uniq -c
#    100
#     40 With IP address <IP_ADDRESS>.
#     60 With IP address <IP_ADDRESS>.

# Change Kong version to 3.6 (one commit before OpenResty bump)
curl https://raw.githubusercontent.com/Kong/kubernetes-ingress-controller/v3.0.2/test/e2e/manifests/all-in-one-dbless.yaml | \
  sed -r 's/kong:3.4/kong\/kong-gateway-dev:eabdfbcedcd744546ee758275110a8790e038891/g' | \
  kubectl apply -f -

# Send 100 requests to /echo endpoint and count unique responses (there will be Pod IPs in the response).
for i in `seq 100`; do curl -s "$PROXY_IP"/echo >> /tmp/hit_ips_before_bump; done
cat /tmp/hit_ips_before_bump | sort | uniq -c

# Get output with 3 Pod IPs as expected:
# cat /tmp/hit_ips_before_bump | sort | uniq -c
#    100
#     44 With IP address <IP_ADDRESS>.
#     27 With IP address <IP_ADDRESS>.
#     29 With IP address <IP_ADDRESS>.

The issue was narrowed down to Kong OpenResty bump in this commit and is handled by the Gateway team in https://konghq.atlassian.net/browse/KAG-3633.
I think we can keep this issue open on our side and close it once a fixed nightly Gateway build passes our E2E tests.


user-data-helper.sh non-existent when using custom AMI

I'm launching a cluster on AWS with Cloudbreak using custom AMIs. I see that Cloudbreak spins up new EC2 instances for the cluster and adds user-data. Looking at the user data from curling http://<IP_ADDRESS>/latest/user-data/ I see that some variables are set and a script is called. The last line of the script calls /usr/bin/user-data-helper.sh
I sshed into one of the new instances that Cloudbreak spun up and tried to locate this file and it was missing. This was with the custom AMI. When I don't specify a custom AMI and use the defaults, it works just fine.
I assume this is a bug and that the user-data-helper code should be appended to the user data when the instance gets launched, or that I need to bake the user-data-helper.sh file into my AMI.
This is on version 1.6.1.

related to this: https://github.com/sequenceiq/cloudbreak/issues/2092


do not have dataSource twice in path to segment storage on hdfs

currently when you do hadoop batch ingestion with overlord , segment storage directory looks something like
%storageDir%/%dataSource%/%dataSource%/20141021T000000.000Z_20141022T000000.000Z/2015-09-04T15_28_26.533Z/0/index.zip
update in HdfsDataSegmentPusher.java makes changes that to dataSource being only once in the path.
..and piggybacked trivial cleanup to remove mention of DatasourceIngestionSpec from HadoopIndexTask

:+1: !

Will this cause extra moves if you are archiving on hdfs?

@drcrallen couldn't understand what you meant by archiving here?

@himanshug I literally mean the archiving task, where it judges if a thing is already archived by if its path is equal (at least for S3) io.druid.indexing.common.task.ArchiveTask. Though I think only S3 has a io.druid.segment.loading.DataSegmentArchiver imiplementation.

@drcrallen as you said DataSegmentArchiver does not exist for hdfs , even if it existed I don't see that getting impacted by this PR at all, the move would stay the same.


Comment says "request" instead of "certificate"

https://github.com/ARMmbed/mbedtls/blob/b363382ba4c0489b6045112dbaf100758ec72cc2/programs/x509/cert_write.c#L773
Could be a copy-paste bug (see cert_req.c)

Another comment to fix in the same module: should have been "certificate" instead of "key"
https://github.com/ARMmbed/mbedtls/blob/b363382ba4c0489b6045112dbaf100758ec72cc2/programs/x509/cert_write.c#L167

ARM Internal Ref: IOTSSL-2466


Use System.Runtime.Caching v8.0.0

Prior versions (including the one used by the adapters) depends on System.Drawing.Common. This is why we had that showing up available for compilation. This change forces us to use v8.0.0 so we don't accidently rely on it.
Fixes #125

FYI @birojnayak


chirpstack api for csharp

Hello! Sir!
I need to create a new SCADA project because I want to present a good interface to customers, which includes images and animations in industrial scenarios. This is more user-friendly to operate, and compared to the web approach developed by Golang, this undoubtedly has great advantages. Golang lacks graphic expression. I found that the chirpstack API does not have the csharp version of the gRPC method, which makes it even more difficult for me to choose which path to use to do this. Excuse me, do you have any gRPC methods for csharp that can be published? Thank you!

Please see: https://github.com/chirpstack/chirpstack/tree/master/api/csharp.

thank you very much!


Overriding custom property sets

Hi! I have a proposal that I'm not sure if skips the standard.
With custom properties you can define kind of a variable in the :root {} scope and use it in a block. If there is another :root {} below the usage redefining the property the final output would keep that value.
/* define a component */
:root {
  --my-color: blue
}

.myClass {
  color: var(--my-color);
}

/* override the custom property */
:root {
  --my-color: red;
}

Outputs
.myClass {
  color: red
}

I was wondering why can't we do the same with custom property sets. I think it's a desirable behavior to customize components. You can provide custom property sets for different nodes and then import the css at the top and redefine the default behavior.
Thanks!!

+1, @javivelasco  Is this causing a priority issue with react-css-themr? I think I just ran into this. I expected a nested theme to redefine properties set by react-toolbox, but ThemeProvider only seems to apply the new properties and not overwrite the ones already set.

@gharwood1 This issue is not directly related but I think it could be useful to solve some use cases of themr. By default themr combines theme objects and the final className respects the default but you can give a composeTheme={false}property and then it will just override the full object. If you want to override only the given classes composeTheme="softly".
This proposal would cover the case when you compose deeply to augment/override original styles of a particular node. You would give an @apply rule in your node classNames that could be defined later from the :root adding/overriding styles.
Feel free to open an issue or contact in Discord if you need to!

Hi,
I think the @apply plugin should follow the custom properties one closely.
Also in a browser environment I guess redefining a set on :root should "propagate" to the block where it's used.
I'll look into it.

Good to know!! Thanks @pascalduez !

I'm currently implementing this. I ended up with some sort of "granular" override (merging declarations), but I'm really not confident this would be "spec" compilant.
So calling @tabatkins again for help :)
What would be the desired behaviour when re-defining a set.
Given the following input:
:root {
  --foo: {
    color: red;
    background-color: red;
  }
}

.before {
  @apply --foo;
}

:root {
  --foo: {
    color: blue;
  }
}

.after {
  @apply --foo;
}

Result
1 - Overrides all declarations.
.before {
  color: blue;
}

.after {
  color: blue;
}

2 - Overrides only  selected declarations (merge).
.before {
  color: blue;
  background-color: red;
}

.after {
  color: blue;
  background-color: red;
}

Yes. Custom properties work the exact same regardless of how you're using them; they're just properties, and override each other.
(That said, we have a long-standing issue with CSS that you sometimes do want to merge with lower-specificity versions of a property, and custom property sets are definitely in that category. I may have written a draft for this that'll get proposed to the CSSWG at the big meeting next week...)

@tabatkins thanks a lot!

Fixed as of<EMAIL_ADDRESS>


[BUG] App Transport Insecure Domain Error

App Transport Remote Logging
Updated RemoteOutput server URL to use HTTPS instead of HTTP.

👍

👍


Plugin for ILSpy

hey i was wondering if you are will to create a plugin for ILSpy as there is an old plugin would be nice to have it on ILSpy and im also trying to Create a Debugger for as well if your interested maybe we can chat on discord about it modz2014#4684

See my reply on ILSpy repository


Opentecture Bookmarks View-a-line by Host R1.0

@opentecture/owners
Full Screen: Opentecture Bookmarks View-a-line by Host

Opentecture Bookmarks View-a-line by Host Read Me
Concept
See also Opentecture Bookmarks View-a-line Read Me
Both scripts link to each other

Access very large numbers of bookmarks
View contents of many sites in a speedy fashion
View bookmarks listed by host name with ease and speed
Speed up identification with descriptions added on-the-fly
Curate the output using comments

Change Log
view-a-line-bookmarks-by-host R1.0

First commit

@theo-armour how would you like to proceed with this issue?


Router support

[ ] react router (https://github.com/reactjs/react-router/milestone/14) 3.0
[ ] support lazy loading

there is a issue with typings, use @types/react-router once the correct version will be released


Update cipher-suites-in-schannel.md

Changed most recent link title - WS2022.

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


Externalise current local file response feature as a npm module

Externalise current local file response feature as a npm module

implemented since 2.x.x


Spelling cmake

This fixes some misspellings in Swift cmake, it is split per https://github.com/apple/swift/pull/42421#issuecomment-1101092698

@swift-ci smoke test


Add Proxy Protocol Support

Please describe the problem you have
Currently, the Envoy Service is annotated with "service.beta.kubernetes.io/aws-load-balancer-backend-protocol: tcp" that places the AWS ELB in TCP mode. This causes the ELB to masquerade the client IP. Adding proxy protocol support will allow the client IP to be preserved for ELB'd connections.
Another approach is to use AWS NLB instead of ELB since NLB natively preserves client IPs.
/cc @jpeach @stevesloka @michmike
xref: examples/contour/02-service-envoy

Maybe need to look more closely at AWS deployment options. I think the operator should deal with low-level stuff like what annotations to make and the user should specify some sort of high-level AWS-specific goals.

xref:  https://github.com/projectcontour/contour-operator/issues/70

I think switching over to NLBs is fine, but we're not an AWS only project. We might need to think about having supported configmaps which outline the various annotations or code in to the project support for whatever environment we're deploying into.

AFAIK the other major platforms provide source preservation.  At least Azure and GCP do.  AWS's ELBs are the odd one out here.

I think switching over to NLBs is fine, but we're not an AWS only project. We might need to think about having supported configmaps which outline the various annotations or code in to the project support for whatever environment we're deploying into.

Right. This was what the kustomize PR #2474 did.
Pretty sure that NLB works out cheaper https://aws.amazon.com/elasticloadbalancing/pricing/

xref contour nlb docs: https://projectcontour.io/guides/deploy-aws-nlb/

xref contour proxy protocol support docs: https://projectcontour.io/guides/proxy-proto/


Added Pancakeswap Router v2

Adds pancakeswap new router v2 which is the main router now.
Changed default router to PCS v2.

Thanks Taylor!


Keyless Entry

A feature I noticed Counterwallet has that Freewallet doesn't is keyless entry.
Will keyless entry for 12 word phrases and private keys be added to Freewallet as it was in Counterwallet?

Please move to discussions section as an idea.


ACCOUNTING: Implement accountant billing view

Thanks for creating an issue! Please fill out this form so we can be sure to have all the information we need, and to minimize back and forth.

What are we trying to do?
Generate a billing report for accountants!

What feature or behavior is this required for?
Easier accountant reconciliation data entry, since we tend to punch these in ~50 at a time!

How should we solve this issue?
@eheintzelman has put together a slamming design, so we're mostly just writing backend and frontend code to match!

I think what we want here is:

a Patient method that filters down to patients who have been marked as fulfilled (see the Fulfillment object)
Revise the accountant table_content to match the designs, with a few changes:

make abortion care $, weeks at proc, and pledge sent date editable

On loading the accountants page, make the report just load for now. don't worry about the reports dropdown above the accountant billing section
keep the search thing functioning the way it is now
add an integration test to confirm that you can find a patient from this search bar, and edit a patient's fulfillment information (we can spin this off if needed)

The troublesome parts of this are probably more frontend than backend, so marking accordingly.
Stems from #643

Tagging interest on this.

Working on this for hacknight

I have a bit done on this, but nothing substantial. Planning on picking it up again at hacknight Monday, but if someone wants to knock it out before then they're welcome to steal it :)

I'm gonna steal zing! @lomky do you have any code/branch that I might want to look at or should I go at it from scratch?

moving from the slack channel because I wrote kinda unclear directions here (sorry!):

the code should live in app/views/accountants/index.html.erb and associated partials
do the fields as follows (overruling what's in the designs):

clinic (sourced from patient.clinic_name / patient.clinic.name)
pt initials (source from patient.name)
abortion care $ (patient.fulfillment.procedure_cost, input field)
weeks at procedure (patient.fulfillment.gestation_at_procedure, input field)
pledge sent date (no great way to do this right now. let's use a placeholder for now and make a note to wire up something.)
check number (patient.fulfillment.check_number, input field)
date of check (patient.fulfillment.date_of_check)

Now that we can assign stuff I'm gonna assign to you @FeminismIsAwesome ! Please pop up a WIP PR if you have anything written when you get a chance!

Took a stab at this, but one thing I'm stumped on is iterating through Patients that have a fulfillment object that exists.
My mongoid isn't that fresh but I've tried variations of these
@test = Patient.where('fulfillment.created_at'.ne => nil)
 @test = Patient.where(:'fulfillment'.exists => true)

Could use some mongoid expertise on this one.

We do this kinda stupidly and create a fulfillment object at point of patient creation. Which is an antipattern we should do away with at some point! But I think in the meantime the best way to get at fulfille patients is like so:
Patient.where('fulfillment.fulfilled' => true)

To get at nested fields, easiest to wrap em in quotes and access fields with dots, I think.

Closed via #1292


Upgrade uglify-es

I'm running into a bunch of issues when trying to run my app on the tessel.
Unfortunately, the version that is bundled with the t2-cli does weird things to my code. For instance:
const contentLength = response.headers['content-length'];
const length = contentLength && Number(contentLength);

turns into
var u = (t.headers["content-length"], contentLength && +contentLength);

...which results in ReferenceError: contentLength is not defined
I upgraded uglify-es to the latest version, and all the build problems went away.
I could of course pass --compress=false  on every build, but as a library author, it would be nice not having to ask the users to do so.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @tcr (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Coverage decreased (-29.1%) to 50.512% when pulling bd3183d4b04c628b6c87e99a77362df000f28496 on rexxars:patch-1 into ca1b5a4804d8b5bf0a1b3043bf476f478ac1f245 on tessel:master.

Hum. Looks like the new version uses template literals when minifying, which breaks the test.

Oh, my bad, it looks like it's the other way around - it's changing template literals to regular quotes. I've updated the failing test to reflect the new uglify behavior, please have another look :smiley:

Coverage remained the same at 79.608% when pulling 5d07e1f979c5cecc2b7721abcc8e580bc63c0712 on rexxars:patch-1 into ca1b5a4804d8b5bf0a1b3043bf476f478ac1f245 on tessel:master.

@HipsterBrown can you do a release? Thanks!!

Fix released as<EMAIL_ADDRESS>https://github.com/tessel/t2-cli/releases/tag/v0.1.17
Thanks for contributing @rexxars! :clap:


adding categories page

Due to the number of posts it becomes hard to find something relevant - this isn't meant as the perfect solution but more as basis for discussion or further iterations

stale for three weeks - I just merge it


Draytek

Please provide the following information.

Vendor Name: Draytek
Product Name: Vigor Routers, Access Points, Switches, VigorACS Central Management software, and MyVigor platform
Version(s) affected: Multiple
Status:  Not Affected
Update Available:  No
Notes
References: https://www.draytek.com/about/security-advisory/log4shell-vulnerability-(cve-2021-44228)/
Last Updated:  14 December 2021

Thank you! This issue has been added.


Using arm-none-eabi

Can you tell me why you don't use a compiler arm-none-eabi-gcc and arm-none-eabi-g++ ?

Hi, @Tiket-s8d.
In this current version, I'm using the STM32CubeIDE for building and compiling the application project. The STM32CubeIDE uses the GCC ARM version. For test code project, I have to use the GCC for x86_x64 version because the GTest runs on an Ubuntu docker container. The original version of GTest is not able to runs on MCU.


Option to open complete path of favorite folder in "Columns" view

What's the Problem?
I have selected "Layout" option as "Columns"
Currently when I open a folder that is added to favorite from the favorites section, It opens only that folder in the leftmost column like below.

I would like some option in settings to open the folder including its parents in four columns with the target folder in rightmost column like seen below

Solution/Idea
Please can you add option in settings to make this feature available.
Alternatives
You can make this default method to open folder when Column is the selected layout.
Priorities

Capability
Priority

This proposal will allow developers to accomplish W
Must

This proposal will allow end users to accomplish X
Should

This proposal will allow developers to accomplish Y
Could

This proposal will allow end users to accomplish Z
Won't

Files Version
Version: <IP_ADDRESS> OS Version: 10.0.22000.434
Windows Version
Windows 11 21H2 OS Build 22000.434
Comments
No response

How is this handled in Mac OS?

As discussed in #9769, any folder pinned to favorites should start from the directory and everything else from root.
However, the behavior of the operation history and focusing the parent folder column should be as it is.
@yaira2 Is it now ready to build? I think it will resolve #6902 and #11274 too.

Yes


Feature request: support tagging?

Hey,
Just wondering if there is any intention to support tagging with that integration?
Would help organize tickets into releases (i.e. tag).
Thanks.

Hi @andreacab. I'm from a team at Atlassian that is currently in the process of migrating the ownership over to us from GitHub. As a part of this, we're currently going through the backlog of issues and prs to see what can still be addressed and what should be closed.
I've flagged this with the 'to-triage' label so my team can discuss. We'll keep you posted on the status of this.

Hi @andreacab, do you mind providing more details on the use-case?

Hi @andreacab. As we haven't heard from you in a while, I'm going to go ahead and close this issue. If you would still like the team to look into this, please feel free to reopen and see the above message from @ccrolf.

Maybe I can add my use case.
Some context: Our Product Manager (PM) only has access to Jira and we use changesets to manage our releases on Github.
When we release something to production, we create a Github Release (which is also a git tag) with the links of all the PRs merged for that release. But to share this with my PM I have to manually create a corresponding Jira release and add all the tickets of the merged PRs.
This means we end up maintaining releases in 2 places, in Github and Jira and sometimes they go out of sync because we forget to create a Jira release. Another reason we use Jira Releases is that we have a Jira Automation setup that sends release notes to Slack/Emails on marking it as "Released".
What I would like is for this sync to happen automatically, creating a Github Release should automatically create a corresponding Jira Release and it should figure out the tickets from the PRs that were a part of it.

Thanks @rohit-gohri. I've reopened this issue and will discuss with our team.

Hello @rachellerathbone,
Where are you guys with this feature? In our team we miss it too and have the same use case as mentioned by @rohit-gohri

I'm also waiting for this feature.
As our team manages both jira release feature and git tag, We need this feature as rohit-gohri commented.


replaced 'comprises' with 'is comprised of'

Description
This seems like smoother language to me. Less confusing.
Issues Resolved
N/A
Check List

[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 BSD-3-Clause License.

Ack! @macohen I didn't see this and made an edit in https://github.com/opensearch-project/project-website/pull/2506


Program can not find file symlinks

If the target file of an $include is a symbolic link, the program fails to find the file.
Steps
Environment
I made a clean environment of Ubuntu 18.04 with Docker for minimal testing (feel free to jump to "Recreation" if this isn't applicable).
docker --rm -it ubuntu:18.04
apt-get update && apt-get install npm
npm install -g<EMAIL_ADDRESS>mkdir testbed && cd testbed

Recreation
echo '$include: "./link.yaml"' > root.yaml
echo 'tacos: {}' > target.yaml
ln -s target.yaml link.yaml
yamlinc --strict root.yaml

Expected Behavior
I would expect the output to look something like this:
## --------------------
## warning stuff here...
tacos: {}

Actual Behavior
The program exits with code 1 and gives the following message:
   Analize : root.yaml
 > Problem : file not found './link.yaml' on 'root.yaml' at line 1.

Problem
The issue appears to be in helpers.js:91 with the usage of fs.lstatSync(file).isFile(), specifically, I do not think that lstat should be used. I do not think that a tool like yamlinc means to look at the link stats, but cares about the target file. I believe fs.statSync(file).isFile() is correct here.

Hi @tgockel
your patch is online on the new version
https://www.npmjs.com/package/yamlinc/v/0.1.9
Thanks


Prefer IPv6 over IPv4 by default

Hello team and @angristan ,
I have a Ubuntu 20.04 VPS on AWS Lightsail and I installed wireguard. IPv6 is supported and I can ping IPv6 address.
When I access some websites like google.com or youtube.com, IPv4 is preferred by default and I have to pass capthca screen sometimes for security reasons. Some shared public IPv4 address on cloud are blacklisted or suspicious because they are used too much on the cloud.
To overcome this issue I would like to use IPv6 by default and IPv4 as a fallback.
You can see the test results on https://ipv6-test.com/
Thanks
Wireguard is working

Wireguard is not working

@angristan Kindly ask your support. Thanks for your hard-working

I am able to get around this by changing the IPv6 subnet to something outside of the ULA range during setup. Below is what my address looks like in the client:
Address = <IP_ADDRESS>/32,2602:80a:200f::2/128
And you can see that Happy Eyeballs is now enabled:

This has to do with the use of utilizing IPv6 ULA addressing (fc00::/7), since most OSs will not prioritize ULA unlike regular IP space. In our instance since we own our own IPv6 space, we dedicated a /64 subnet for tunnel use, so we can avoid any conflicts.
If we wanted to follow RFCs, this behavior can't actually change, as everything outside of ULA space is owned by someone else, or has another purpose. I wonder if we can add a note in the script to change the IPv6 to an address you own if you want to use it with Happy Eyeballs.

Thanks @rootbeerdan :)

@angristan @rootbeerdan step 2(b) explains this configuration
https://www.digitalocean.com/community/tutorials/how-to-set-up-wireguard-on-ubuntu-20-04

@rootbeerdan If you open ICMPv6 port on your server, the score will be 19 points.


wavefront_alert resource keeps creating new alerts / destroy doesn't destroy the alert but blanks out state

I created an alert.  terraform plan, terraform apply.  Alert gets created.  With no changes to config, terraform plan.  It says it's refreshing the ID of the alert (ID matches correctly).  terraform plan output is to create a new alert again.  terraform apply will create a new alert with a new ID, resulting in a duplicate alert.
terraform destroy returns nothing to be destroyed but if I enter yes, the state is destroyed but the alerts still remain in wavefront.
using terraform v0.11.3

This may have been resolve with go-wavefront updates...I will try rebuilding.

@ognnaot - We've seen issues whereby the alert is not available immediately after creation; this was due to using a 'search' to perform the lookup, which is cached -  the cache takes a second to update.
I raised a case with Wavefront, they can't see anything wrong, but we're in the process of updating the provider to use the GET /alert/{id} endpoint (hence the go-wavefront update to implement the get function).
We've only seen this process when the plan/update/delete is performed immediately (sub-second) after the apply.

I've waited minutes and even to the next day and my tests still see the above symptoms.  Maybe my environment is caching much longer.
I've pulled in the go-wavefront changes and trying to do some patching on my end.  Looks like the Find functions can be removed since I don't see them being used after the Get function added.

The find functions are still useful, they allow searching on any criteria. For instance you may wish to search for all Alerts which are 'Snoozed'.
This is a strange issue. We use this provider to manage all of our Wavefront alerts (on the same version of terraform as yourself), without issue.
Does the WF token you are using definitely have sufficient permissions, and does it get passed in correctly each time?
Could you provide specific steps to reproduce the problem, and we can investigate our end?

@ognnaot I've just had #27 merged to start using 'get' over 'find' and this has alleviated the problems we were seeing.
v1.0.2 has these changes. Hopefully, this solves your problem too.
Thanks for your PR, the changes are essentially what I implemented (although there were some tests that also needed to be updated).