aws-sdk dependency ...

Hey,
Just a quick question ... I was hoping to test this before asking you this, but my serverless builds are stuck on various bugs I can't find yet and I was wondering...
I noticed your plugin has to be installed locally (like all serverless plugins), and is dependent upon aws-sdk. I haven't checked yet, but I'm guessing that the default behavior of serverless will be to grab all of the packages in /node_modules and wrap them up ... back in v0.5.6 subdirectories were essential to avoid recursive build of the /.meta directory, so all of the serverless plugins were in a separate package.json in the root directory and the service was in a subdirectory with its own package.json. If that isn't the way it's done now ... then it looks like the default behavior would be to wrap up an extra 14MB library that AWS advises not to bring along with you because it provides it to the Lambda container automatically?  I realize this probably isn't specific to your plugin...
I expect that I can put into serverless.yml to exclude certain plugins from being included in the uploaded package... do you have a more elegant solution that you guys use for your plugin?
Thanks in advance...

Hi,
The reason why the AWS sdk is included is, that prior Serverless 1.4 the version of the sdk this plugin needs wasn't included. Because of backwards compatibility we decided to leave the dependency in for a while.
I don't know what the current distribution of serverless versions is. I guess we could get rid of the dependency and use the build in sdk of serverless.
I will have a look if for me the sdk is included and give you an update on that.

Yeah, that makes complete sense why you do it. I was concerned that I had set up my service wrong, and that noone uses the same /node_module folder for both what the service needs and what the service plugin needs. But from your response it seems like this is quite the possibility.
It sounds like I should explicitly exclude the aws-sdk (and your plugin, for that matter) for now, and perhaps forever, to allow you guys the flexibility to do what makes best sense for your plugin. I can understand the backwards compatibility issue can take time, and right now your plugin serves an essential function for anyone who's using the APIG's generated Mobile SDKs IMO and shouldn't break on folks.
Thanks again, @tchock!

If you haven't guessed it btw, I'm just so relieved this plugin exists that you could translate my documentation to Italian every 3 weeks and I'd find a workaround for it. :)


feature: separate control of braces after anonymous constructs in BracesFixer

Add two "optional" options that give more control of how braces are positioned:

position_after_anonymous_classes - whether the opening brace should be placed on "next" or "same" line after anonymous classes. If not set, position_after_anonymous_constructs setting is used.

position_after_anonymous_functions- whether the opening brace should be placed on "next" or "same" line after anonymous lambda functions. If not set, position_after_anonymous_constructs setting is used.

To meet Laravel braces code style criteria configure fixer with:
[
'allow_single_line_anonymous_class_with_empty_body' => false,
'allow_single_line_closure' => false,
'position_after_functions_and_oop_constructs' => 'next',
'position_after_control_structures' => 'same',
'position_after_anonymous_classes' => 'next',
'position_after_anonymous_functions' => 'same',
]

Yes, I know, BracesFixer is going to be deprecated but this PR does small changes and brings very helpful capability. At least for Laravel developers. ;-)

This functionality of braces fixer has been moved to curly_braces_position_fixer, which seems to have these options:
https://github.com/FriendsOfPHP/PHP-CS-Fixer/blob/22804e82950a7d80f1185872c8396fca1c675f45/src/Fixer/Basic/CurlyBracesPositionFixer.php#L371-L374
https://github.com/FriendsOfPHP/PHP-CS-Fixer/blob/22804e82950a7d80f1185872c8396fca1c675f45/src/Fixer/Basic/CurlyBracesPositionFixer.php#L379-L382

Ok, I will experiment with combinations of braces and curly_braces_position fixers and see what will get.

BINGO !
Using following combination of braces i curly_braces_position fixers gives no style errors!
THX @jrmajor :)
'braces' => [
	'allow_single_line_anonymous_class_with_empty_body' => false,
	'allow_single_line_closure' => false,
	'position_after_functions_and_oop_constructs' => 'next',
	'position_after_control_structures' => 'same',
	'position_after_anonymous_constructs' => 'next',
],

'curly_braces_position' => [
	'control_structures_opening_brace' => 'same_line',
	'functions_opening_brace' => 'next_line_unless_newline_at_signature_end',
	'anonymous_functions_opening_brace' => 'same_line',
	'classes_opening_brace' => 'next_line_unless_newline_at_signature_end',
	'anonymous_classes_opening_brace' => 'next_line_unless_newline_at_signature_end',
	'allow_single_line_empty_anonymous_classes' => true,
	'allow_single_line_anonymous_functions' => false
]

Since braces fixer "internally" uses curly_braces_position fixer, "externally" appling it again makes no sense from performance perspective. I did some testing and using both fixers on average is 6% slower then using one modified curly_braces_position fixer.
Does the performance loss really matter in this case?
What you guys think?
@jrmajor @SpacePossum @keradus

The additional overhead might be justified by; more control for the end users through configuration, the code being easier to extend for future features, less complex priority settings and a far lower maintenance cost (for example for new PHP versions).
Also, the end-goal is to not have a single braces fixer with all the delegations to other fixers. When that is the case I suspect the overhead to be far less. Using the build-in file-based-caching should also mediate some of this overhead over a longer period of time.

@SpacePossum, thx for clearing this up!


Job summary triggered by summary-always: true has raw code characters markdown

When using job summaries via summary-always: true the summary that's added to the workflow run has raw markdown characters instead of pretty printed rendered summary like it's done for commits:
Exemplar workflow summary with mentioned problem: https://github.com/pmalek/benchtest/actions/runs/5236041026#summary-14168273532

Thanks @pmalek for filing an issue. We'll try to look into it as soon as possible

released in v1.19.2


MaxTileWidthGrid should not require columnSpacing and rowSpacing

Steps to Reproduce
I created a MaxTileWidthGrid
new MaxTileWidthGrid(
        children: profileWidgets, maxTileWidth: style.Size.settingsWidth);

where profile widgets are some other sort of list of widgets.
The problem is that when I run this, I get an error and red screen.
/usr/local/google/home/alexfandrianto/Documents/vanadium_root/flutter/packages/flutter/lib/src/rendering/grid.dart': Failed assertion: line 194: 'columnSpacing != null && columnSpacing >= 0.0' is not true.

This red screen occurs because of MaxTileWidthGridDelegate and GridDelegateWithInOrderChildPlacement. The latter contains the failed assertions.
And after setting columnSpacing to 0.0...
'/usr/local/google/home/alexfandrianto/Documents/vanadium_root/flutter/packages/flutter/lib/src/rendering/grid.dart': Failed assertion: line 195: 'rowSpacing != null && rowSpacing >= 0.0' is not true.

And after setting rowSpacing to 0.0... it works as expected.
new MaxTileWidthGrid(
        children: profileWidgets, maxTileWidth: style.Size.settingsWidth, columnSpacing: 0.0, rowSpacing: 0.0);

I think the MaxTileWidthGrid should set columnSpacing and rowSpacing to 0.0 by default though, to make the widget easier to use.
Flutter Doctor
[✓] Flutter (on Linux, channel unknown)
• Flutter at /usr/local/google/home/alexfandrianto/Documents/vanadium_root/flutter
• Framework revision 4df24ab (4 days ago), engine revision 3d944e1
[✓] Android toolchain - develop for Android devices (Android SDK 23.0.1)
• Android SDK at /usr/local/google/home/alexfandrianto/mojo/src/third_party/android_tools/sdk
• Platform android-23, build-tools 23.0.1
• OpenJDK Runtime Environment (build 1.8.0-google-v7-117372415-117822431)
[✓] Atom - a lightweight development environment for Flutter
• Atom installed; Flutter plugin version 0.2.1

Makes sense.  Will do.  Thanks!


Add utility methods to exact timestamp information from UUID1.

Ping @adamvoncorswant. Thanks.

But we only support java6 in the toolbox?

Well, as TC said OK, I assume we support Java-8 already in toolbox. :-)

Interesting. The pom for the izettle-java project specifies 1.6...

I'm up for discussing this though. Only reason we have java6 is because of Android. Most of the code they could probably copy to their repo, but especially the cart code seems a bit risky to maintain two version of. Thoughts?

Sure, fixed. Removed Java-8 stuff, replaced with Java-6 equivalent.


For 0.36 npm run biuild failed

Description
Got error when npm build
node_modules/@hashgraph/sdk/lib/topic/TopicUpdateTransaction.d.ts(174,52): error TS2304: Cannot find name 'Long'.
src/lib/clients/sdkClient.ts(150,21): error TS2304: Cannot find name 'Long'.
src/lib/clients/sdkClient.ts(151,21): error TS2304: Cannot find name 'Long'.
src/lib/eth.ts(660,25): error TS2345: Argument of type 'number | undefined' is not assignable to parameter of type 'number | bigint | BigNumber'.
Type 'undefined' is not assignable to type 'number | bigint | BigNumber'.
Waiting for the debugger to disconnect...
 ELIFECYCLE  Command failed with exit code 1.
Steps to reproduce
git pull from   hedera-json-rpc-relay 0.36
rin npm i
run  npm build,
got that "Cannot find name 'Long'."  errors
Additional context
Need to add "@types/long" in package.json
Hedera network
testnet
Version
0.36
Operating system
Linux
### Tasks

Hi @stanta, Thanks for opening this ticket.
We resolved this shortly after but do let us know if you experience any other issues building.
Thanks


The bar code is missing and cannot be identified completely

Hello
I'm glad to find your open source project
However, during the testing process,
The bar code is missing and cannot be identified completely

Not sure what exactly is the problem?
Is barcode missing or is it not identified completely? These are two distinct cases.
If you're missing part of the barcode have you tried to specify bufferDuration  parameter to something longer, IE. 500 ms?

Bar code missing
Correct:<PHONE_NUMBER>168
Identified:<PHONE_NUMBER>58
There are fewer digits in the middle

Have you tried modifing bufferDuration parameter?
pon, 1. ožu 2021. 10:21 zouxianbincc<EMAIL_ADDRESS>je napisao:

Bar code missing
Correct:<PHONE_NUMBER>168
Identified:<PHONE_NUMBER>58
There are fewer digits in the middle
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/shaxxx/flutter_barcode_listener/issues/1#issuecomment-787796535,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANSJO4K3F4MPI22ZSAA4ALTBNMCVANCNFSM4YMEU46A
.

Thank you very much.
After testing, change RawKeyUpEvent to RawKeyDownEvent
It can be correctly identified

void _keyBoardCallback(RawKeyEvent keyEvent) {
if (keyEvent.logicalKey.keyId > 255 &&
keyEvent.data.logicalKey != LogicalKeyboardKey.enter) return;
if (keyEvent is RawKeyDownEvent) {
if (keyEvent.data != null) {
if (keyEvent.data is RawKeyEventDataAndroid) {
_controller.sink.add(((keyEvent.data) as RawKeyEventDataAndroid).codePoint);
} else if (keyEvent.data is RawKeyEventDataFuchsia) {
_controller.sink
.add(((keyEvent.data) as RawKeyEventDataFuchsia).codePoint);
} else if (keyEvent.data.logicalKey == LogicalKeyboardKey.enter) {
_controller.sink.add(lineFeed);
}
} else {
_controller.sink.add(keyEvent.logicalKey.keyId);
}
}
}

Glad it worked. If you check history you'll see I started with KeyDown but moved to KeyUp because there were some issues.
Don't remember why anymore.


/sys/subsystem subdirectory not created by udev anymore since 20.03

Describe the bug
My consul cluster doesn't come up in 20.03, as the following line fails:
https://github.com/NixOS/nixpkgs/blob/54eb2d10184124a8bd6cc01ff815c30aa8aebf35/nixos/modules/services/networking/consul.nix#L19 and consul service forever waits for the device to appear.
(this should really have been caught by a nixos test by the way!)
Digging further;
https://github.com/systemd/systemd/blob/master/rules.d/99-systemd.rules.in#L39-L49
should be responsible for creating the  /sys/subsystem directory; and linking devices there for discoverability. However; it seems  20.03 doesn't do this anymore. . The directory simply doesn't exist anymore..
To Reproduce
    services.consul = {
      enable = true;
      webUi = true;
      interface = {
        # For now only local
        advertise = "lo";
        bind = "lo";
      };
    };

Expected behavior
Service comes up.  Instead; the service fails whilst it waits for a non-existent device to come up.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Notify maintainers
@flokli
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

Nevermind; this is me mis-understanding systemd.
Systemd doesn't create the  symlink; but instead creates a .device unit of said name;  Because in the udev rules the systemd unit is described as a path; I thouht it would show up in /sys too; but this assumption is false.
And as you can see in  the udev rules  the loopback interface (for an undocumented reason) is exempt from this behaviour and hence the device is never coming up.
This is all a bit odd. Weird systemd


[diem framework] remove verify=false from scripts

Motivation
This PR removes outdated verify = false from some script modules since they no longer timeout.
Have you read the Contributing Guidelines on pull requests?
Yes

/land

:broken_heart: Test Failed - ci-test

/land

:broken_heart: Test Failed - ci-test

/land


Update documentation for article

PR Summary:
Includes examples from the listings in the foyer paper in response to reviewers.
If anyone knows a nice regex or some other method to remove the extraneous parameters not needed in the silica xml file, please edit it! all that is really needed are the necessary parameters for: opls_1001, opls_1002, opls_1008, opls_1009, but leaving the atom types for 1000-1009 is fine.
PR Checklist

[x] Includes appropriate unit test(s)
[x] Appropriate docstring(s) are added/updated
[x] Code is (approximately) PEP8 compliant
[x] Issue(s) raised/addressed?

Why do we have foyer/examples/, foyer/docs/examples/, docs/paper_examples?

There isnt really anything in foyer/examples, so I think that should probably be removed. Or we replace that with a submodule for our foyer tutorials.
The paper_examples.md file is a markdown version of the two jupyter notebooks in 	foyer/docs/examples.
Since these are small examples and just from the listings in the paper, i felt like they should go there.
Unless you think they should be put elsewhere in the repo?

+1 for removing one of them but my preference would be to have everything end up in /examples/ or /foyer/examples/. As a user those are the place I'm going to look first for examples, and digging through the docs for examples is not as intuitive imo.

Since these are small examples and just from the listings in the paper, i felt like they should go there.

This just isn't something I see very often. If they're a duplicate of examples we have elsewhere I don't see the point of having them here. Maybe while it's in review it's ok to leave them here but later I would push to have them removed in favor of linking to or simply uploading the paper itself.

Could have “paper_examples.md” just link to the notebooks under /examples.
The important point here is that we need to clearly have a page that says “paper_examples” so anyone reading the paper can go run them.  I’m going to make a doi for the repo on zenodo (which will also make an archival copy of the repo) and link to it from the paper.  If these examples are no longer relevant in the future, or things have changed, people can go back to that archive.
On May 9, 2019, at 9:41 AM, Matt Thompson <notifications<EMAIL_ADDRESS>wrote:
+1 for removing one of them but my preference would be to have everything end up in /examples/ or /foyer/examples/. As a user those are the place I'm going to look first for examples, and digging through the docs for examples is not as intuitive imo.
Since these are small examples and just from the listings in the paper, i felt like they should go there.
This just isn't something I see very often. If they're a duplicate of examples we have elsewhere I don't see the point of having them here. Maybe while it's in review it's ok to leave them here but later I would push to have them removed in favor of linking to or simply uploading the paper itself.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmosdef-hub%2Ffoyer%2Fpull%2F237%23issuecomment-490978743&data=02|01|christopher.r.iacovella%40vanderbilt.edu|88b4750109d44f941d1a08d6d49d332a|ba5a7f39e3be4ab3b45067fa80faecad|0|0|636930168963956887&sdata=cKlQW77YnERxudX2YEczhYrBsNCd2LEACDwGsFAf1jU%3D&reserved=0, or mute the threadhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAK3RK6PVVIGBGHQOLRSIMTPURH35ANCNFSM4HLV773A&data=02|01|christopher.r.iacovella%40vanderbilt.edu|88b4750109d44f941d1a08d6d49d332a|ba5a7f39e3be4ab3b45067fa80faecad|0|0|636930168963966901&sdata=9ofAufmTuY601bJRGGB5Bx9qykXrs%2BsI0XbwiJXgeIw%3D&reserved=0.

Please once-over and merge if acceptable @justinGilmer


Request Header Inheritance

Similar to how Google handles headers, batch-request should allow individual request headers to be inherited from the batch request.  This makes it easier for libraries like Angular to intercept the batch request right before it is sent and append headers as necessary.  It also allows us to access HTTPOnly cookies on the individual requests.
To quote from the link above,

The HTTP headers for the outer batch request, except for the Content- headers such as Content-Type, apply to every request in the batch. If you specify a given HTTP header in both the outer request and an individual call, then the individual call header's value overrides the outer batch request header's value. The headers for an individual call apply only to that call.

Totally on board with this improvement! Would happily accept a PR which would do this, as long as it's backwards compatible!

I don't think that could be guaranteed unless a configuration option was added similar inheritHeaders and the default was set to false.  Setting it to true would allow for header inheritance.

Created a PR.


Make processDependencyManagementTransitive as false by default

Fi: #1002

First we need resolve - investigate: #1004


Typo correction

Open Food Facts is a open database -> Open Food Facts is an open database.
Signed-off-by: P.-H. Lin<EMAIL_ADDRESS>

Thanks @Cypresslin :-)


buck2: crashes on aarch64 with a 16k page size

Describe the bug
On aarch64 systems such as Asahi Linux, or Raspberry pi 5 devices that use a 16k page size buck2 will not run due to jemalloc.
<jemalloc>: Unsupported system page size
memory allocation of 64 bytes failed

Steps To Reproduce
On an aarch64 host system with a 16k size, run:
nix run 'github:nixos/nixpkgs/master#buck2'

Expected behavior
The buck2 command and the buck2 init command should work.
Screenshots
Additional context
Notify maintainers

@thoughtpolice
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"

system: "aarch64-linux"
host os: Linux 6.11.0-400.asahi.fc40.aarch64+16k, Fedora Linux Asahi Remix, 40 (KDE Plasma), nobuild
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.24.9
channels(root): "nixpkgs"
nixpkgs: /nix/store/mln6wr5z539qgldmsm4j1k8k0dm19yvz-source

Add a :+1: reaction to issues you find important.

Hmm, this seems to be have been reported in https://github.com/facebook/buck2/issues/91 already 😕

There also seems to be a environment variable called JEMALLOC_SYS_WITH_LG_PAGE which can be set to 16 🤔

This should be fixed by https://github.com/NixOS/nixpkgs/pull/348911, which includes https://github.com/facebook/buck2/pull/693


Update ruby docker image to use pthread for win32

By default, MinGW doesn't have support for std::thread because libstdc++ uses pthread which Windows lacks. To use std::thread, there are two solutions:

Using pthread for Windows.
Using mingw-std-threads

This PR chose the first solution because it make this transparent with cost of adding new layer between gRPC and Windows thread.

grpc_build_artifacts_multiplatform


npm install on the front-end directory results in error

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: serverless-aws-react-saas-front-end@undefined
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/graphql
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>|| ^0.12.3 || ^0.13.0 || ^14.0.0 || ^15.0.0" from<EMAIL_ADDRESS>npm ERR! node_modules/apollo-link
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Hi, @absolutemadla8
You can solve this by using npm install --force or npm install --legacy-peer-deps.


Milestone 0.1.0 - Genesis

Let's handle this issue as a discussion forum for the first milestone
IMO, these are the things we should aim for our first MVP.
1. Storage

[ ] Core CommitLog

[ ] Segments

[x] ~Write to segments~
[x] ~Write across segments~
[x] ~Read from segment~
[x] ~Read across segments~

[x] Index
[x] ~Better API for reading~ (#5) Thanks @cuichenli

[x] ~Record Struct~

[x] ~End-to-end use of records~

[x] ~Extract logfile from segment~
[x] ~Memory Mapped IO~

[x] ~Write~

[x] ~Index~
[x] ~Segment~
[x] ~Refactor segment split to take index into account~

[x] ~Read~

[x] ~Index~
[x] ~Segment~

[ ] Restore state from disk (#4)

2. Networking

[ ] Networking/API (#6)

[ ] Decide simple inicial protocol
[ ] Implement Basic Socket Communication
[ ] Implement TCP/HTTP?
[ ] Write to streams over the network
[ ] zero-cost copy (OS sendfile)

3. Operational

[ ] Operational

[ ] Configuration

[ ] CLI Basics

We'll leave replication out of the first Milestone.

Extra

[x] ~CI/Tooling~

[x] ~Setup Travis~

[x] ~Build with Linux/macOS~

[ ] Docker

[ ] Alpine

[ ] Consistency Testing (#8)
[ ] Benchmarks (#10)

I’m glad to have helped 😄 . I will also have a look at other issues. Also thanks for the good opportunity to let me contribute and learn.

Hi,
Really interesting project you've got here and would really be interested in contributing. Been looking at some issues and wondering if you had anything you'd like me to work on.
Both restoring state from disk #4  and Consistency integration test #8 seemed to catch my eye.
Let me know if I can work on either of these and I'll get to work on them.


Crash on Debian/Ubuntu when opening UI twice

plugins seem to crash on Debian/Ubuntu when opening the UI a second time (CLAP or VST3). I've had reports of this in Reaper/Bitwig on Ubuntu 22.04, and was able to confirm it myself on Debian 11 with Reaper 7.0.6.  I haven't seen it at all on Arch/Manjaro for some reason
Here's a stack trace of the Egui Gain Example plugin, running in Reaper 7.0.6 on Debian 11:
(gdb) bt
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x00007fffaa1f3e64 in std::sys::unix::futex::futex_wait () at library/std/src/sys/unix/futex.rs:62
#2  std::sys_common::thread_parking::futex::Parker::park () at library/std/src/sys_common/thread_parking/futex.rs:52
#3  std::thread::park () at library/std/src/thread/mod.rs:1068
#4  0x00007fffa9d00536 in std::sync::mpmc::context::Context::wait_until (self=0x7fffffff9598, deadline=...)
    at /rustc/79e9716c980570bfd1f666e3b16ac583f0168962/library/std/src/sync/mpmc/context.rs:139
#5  0x00007fffa9ca300c in std::sync::mpmc::array::{impl#1}::recv::{closure#1}<core::result::Result<baseview::x11::window::SendableRwh, ()>> (cx=0x7fffffff9598) at /rustc/79e9716c980570bfd1f666e3b16ac583f0168962/library/std/src/sync/mpmc/array.rs:397
#6  0x00007fffa9c6fa68 in std::sync::mpmc::context::{impl#0}::with::{closure#0}<std::sync::mpmc::array::{impl#1}::recv::{closure_env#1}<core::result::Result<baseview::x11::window::SendableRwh, ()>>, ()> (cx=0x7fffffff9598)
    at /rustc/79e9716c980570bfd1f666e3b16ac583f0168962/library/std/src/sync/mpmc/context.rs:50
#7  0x00007fffa9c6f765 in std::sync::mpmc::context::{impl#0}::with::{closure#1}<std::sync::mpmc::array::{impl#1}::recv::{closure_env#1}<core::result::Result<baseview::x11::window::SendableRwh, ()>>, ()> (cell=0x2ebdb50)
    at /rustc/79e9716c980570bfd1f666e3b16ac583f0168962/library/std/src/sync/mpmc/context.rs:58
#8  0x00007fffa9c9f11b in std::thread::local::LocalKey<core::cell::Cell<core::option::Option<std::sync::mpmc::context::Context>>>::try_with<core::cell::Cell<core::option::Option<std::sync::mpmc::context::Context>>, std::sync::mpmc::context::{impl#0}::with::{closure_env#1}<std::sync::mpmc::array::{impl#1}::recv::{closure_env#1}<core::result::Result<baseview::x11::window::SendableRwh, ()>>, ()>, ()>
    (self=0x7fffaa4d36d8, f=...) at /rustc/79e9716c980570bfd1f666e3b16ac583f0168962/library/std/src/thread/local.rs:270
#9  0x00007fffa9c6e6de in std::sync::mpmc::context::Context::with<std::sync::mpmc::array::{impl#1}::recv::{closure_env#1}<core::result::Result<baseview::x11::window::SendableRwh, ()>>, ()> (f=...)
    at /rustc/79e9716c980570bfd1f666e3b16ac583f0168962/library/std/src/sync/mpmc/context.rs:53
#10 0x00007fffa9ca2edb in std::sync::mpmc::array::Channel<core::result::Result<baseview::x11::window::SendableRwh, ()>>::recv<core::result::Result<baseview::x11::window::SendableRwh, ()>> (self=0x1682400, deadline=...)
    at /rustc/79e9716c980570bfd1f666e3b16ac583f0168962/library/std/src/sync/mpmc/array.rs:386
#11 0x00007fffa9c5847b in std::sync::mpmc::Receiver<core::result::Result<baseview::x11::window::SendableRwh, ()>>::recv<core::result::Result<baseview::x11::window::SendableRwh, ()>> (self=0x7fffffff99c0)
    at /rustc/79e9716c980570bfd1f666e3b16ac583f0168962/library/std/src/sync/mpmc/mod.rs:306
#12 0x00007fffa9d2d5b7 in std::sync::mpsc::Receiver<core::result::Result<baseview::x11::window::SendableRwh, ()>>::recv<core::result::Result<baseview::x11::window::SendableRwh, ()>> (self=0x7fffffff99c0)
    at /rustc/79e9716c980570bfd1f666e3b16ac583f0168962/library/std/src/sync/mpsc/mod.rs:849
#13 0x00007fffa9c9ffb5 in baseview::x11::window::Window::open_parented<nih_plug::editor::ParentWindowHandle, egui_baseview::window::EguiWindow<alloc::sync::Arc<lock_api::rwlock::RwLock<parking_lot::raw_rwlock::RawRwLock, ()>, alloc::alloc::Global>, nih_plug_egui::editor::{impl#0}::spawn::{closure_env#2}<()>>, egui_baseview::window::{impl#2}::open_parented::{closure_env#0}<alloc::sync::Arc<lock_api::rwlock::RwLock<parking_lot::raw_rwlock::RawRwLock, ()>, alloc::alloc::Global>, nih_plug_egui::editor::{impl#0}::spawn::{closure_env#2}<()>, nih_plug::editor::ParentWindowHandle, nih_plug_egui::editor::{impl#0}::spawn::{closure_env#1}<()>>>
    (parent=0x7fffffffa310, options=..., build=...)
    at /home/skunkie/.cargo/git/checkouts/baseview-9d6c750431f4479e/1d9806d/src/x11/window.rs:143
#14 0x00007fffa9c642cd in baseview::window::Window::open_parented<nih_plug::editor::ParentWindowHandle, egui_baseview::window::EguiWindow<alloc::sync::Arc<lock_api::rwlock::RwLock<parking_lot::raw_rwlock::RawRwLock, ()>, alloc::alloc::Global>, nih_plug_egui::editor::{impl#0}::spawn

The issue appears to have started at this commit: eb968ba44666d96cb2349ad877fcdcbccb993f8c
Edit: This seems to likely be a baseview issue: https://github.com/RustAudio/baseview/issues/142
Edit: I have now seen this on Manjaro as well. It took about 300 open/close cycles, but this may be because I have a lot of RAM/VRAM, and my Debian/Ubuntu tests were on more limited VMs.  As far as I can tell, this is just a baseview bug/leak, probably a duplicate of: https://github.com/robbert-vdh/nih-plug/issues/93
Edit: This apparently happens with VIZIA as well.

Similar crash is happening to me on Studio One (Studio One <IP_ADDRESS>528 Win x64).  The 1st instance was dragged and dropped onto a bus channel and it works fine.  When I tried to add an additional instance (via drag/drop or choosing from list) onto a different audio channel, the DAW crashes and I need to re-open it.  I'm using the [2024-05-05-230535-windows.zip] version of the VST3 plugin.  I have a PreSonus diagnostic crash report if anyone is interested.

We've been getting more reports of this with our Linux plugins in Debian+Reaper.  It can be triggered with iced, vizia, and egui examples, as well as the Spectral Compressor plugin. I simply open and close the UI a few times and it usually goes blank or crashes.  Pretty sure it's a baseview issue from these two errors:
BadDrawable:
10:10:30 [ERROR] thread 'unnamed' panicked at 'called Result::unwrap()on anErr value: XLibError { error_code: 9, error_message: "BadDrawable (invalid Pixmap or Window parameter)", minor_code: 3, request_code: 130, type: 0, resource_id: 65011716, serial: 302 }': /home/skunkie/.cargo/git/checkouts/baseview-9d6c750431f4479e/2c1b1a7/src/gl/x11.rs:236
and BadRequest:
10:10:31 [ERROR] thread 'unnamed' panicked at 'called Result::unwrap()on anErr value: XLibError { error_code: 1, error_message: "BadRequest (invalid request code or no such operation)", minor_code: 0, request_code: 0, type: 0, resource_id: 65011716, serial: 65 }': /home/skunkie/.cargo/git/checkouts/baseview-9d6c750431f4479e/2c1b1a7/src/gl/x11.rs:236


Fixing TIMESTAMP data type usage during segment creation

Description
Missed a few places during segment creation/segment name generation for TimeFormat.TIMESTAMP usage.
Upgrade Notes
Does this PR prevent a zero down-time upgrade? (Assume upgrade order: Controller, Broker, Server, Minion)

[ ] Yes (Please label as backward-incompat, and complete the section below on Release Notes)

Does this PR fix a zero-downtime upgrade introduced earlier?

[ ] Yes (Please label this as backward-incompat, and complete the section below on Release Notes)

Does this PR otherwise need attention when creating release notes? Things to consider:

New configuration options
Deprecation of configurations
Signature changes to public methods/interfaces
New plugins added or old plugins removed

[ ] Yes (Please label this PR as release-notes and complete the section on Release Notes)

Release Notes

Documentation

Codecov Report

Merging #8407 (a334419) into master (4bb7e4f) will decrease coverage by 56.72%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             master    #8407       +/-   ##
=============================================
- Coverage     70.88%   14.15%   -56.73%
+ Complexity     4280       84     -4196
=============================================
  Files          1655     1610       -45
  Lines         86607    84726     -1881
  Branches      13064    12861      -203
=============================================
- Hits          61389    11995    -49394
- Misses        20982    71826    +50844
+ Partials       4236      905     -3331

Flag
Coverage Δ

integration1
?

integration2
?

unittests1
?

unittests2
14.15% <0.00%> (+0.04%)
:arrow_up:

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

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


api: compilerhost async fs

Hi, would you consider adding ability to create compiler host using async filesystem functions(or any other solution to the problem at hand). Possible support for either sync/async
Use case is using the typescript api in a VSCode for the web extension, where the VSCode workspace.fs functions to acess the file system are all async: https://code.visualstudio.com/api/references/vscode-api#FileSystem
Tia

The problem is that the checker, which is by far our performance bottleneck, can (in rare cases) need to read a file when resolving the type of an object. Because async is infectious, this would make the entire typecheck phase a very long and slow sequence of async calls -- I can't even speculate how slow this would be.

Thanks @RyanCavanaugh , i fully understand. However i do not see any workaround at this time to support VSCode for the web. Do you have any clues in which direction i should look? The VSCode team also seem pretty set on not providing blocking sync versions of their workspace.fs routines, as some remote file systems do need to be async.

The general idea is the (somehow) know ahead of time which files will be needed and preload them so they can be synchronously returned. For any other files, you can record when they're probed, fetch them if they exist, then fire the file watcher so TS recomputes the program. This is how e.g. the TypeScript Playground works.

Thanks for the suggestion. I dont it works for my use case - running the checker on the selected file (i can pre-load this first file selected in VSCode), but then loading all required dependencies. Recomputing one by one on each file request also doesnt seem workable.
Can you point me to the code for ts playground - it seems a different use-case as it knows the files upfront and loads them in its virtual fs, but maybe i am missing something.

https://github.com/microsoft/TypeScript-Website/tree/v2/packages/playground


Removed nette/tester from prod dependencies and some other changes

PHP to >=7.2, removed .idea/ files from repo, nette/tester is dev dependency, nette/di is required only for tests (any other DI can be used instead)

Thanks!


CKEditor5Field

@jowilf I have renamed the branch so GitHub automatically closed the PR. If it sounds good, I can open another PR.

It's available in the starlette-admin-fields project.


Add an example model that uses MIDI I/O

Have an example MIDI model on our dropdown menu
Have an example MIDI model in our code for PyHarp so that people know how to code it/

Although HARP now supports midi-to-midi models, we currently do not provide any useful or convincing examples. We need to identify at least one such model (e.g., Anticipatory Music Transformer) and create a demo for HARP.


[Question] Fetch Recursive

Hi..
I wanna ask..

Can i use recursive without get infinite loop?
If can't, can i fetch another link in multi level (another link inside another link)?

Thank You

Hi Romy,
so you want to call the adapter the following way:
SpringDataRestAdapter.process(response, '_allLinks')

But in your data model you have links which point to entities from which they are linked from and thus causing a loop in the adapter. What you can do is to define which links you want to automatically resolve with the following usage:
SpringDataRestAdapter.process(response, ['anotherLink', 'testLink'])

Please also have a look at the documentation here: https://github.com/guylabs/angular-spring-data-rest#fetch-multiple-or-all-links
I hope that answers your two questions.
Thanks and regards,
Guy

Thanks for your response @guylabs
SpringDataRestAdapter.process(response, ['anotherLink', 'testLink'])

I mean if 'anotherLink' have 'anotherAnotherLink', can i get 'anotherAnotherLink' automatically?

Well you would need to define all the links you want to resolve in this list. So if you want to resolve the anotherAnotherLink then you need to call it this way:
SpringDataRestAdapter.process(response, ['anotherLink', 'testLink', 'anotherAnotherLink'])

What is your use case and how is your data model such that you get an infinite loop ?

I have response JSON like this:
{
    "_links": {
        "self": {
            "href": "http://localhost:8080/api/reports"
        }
    },
    "_embedded": {
        "reports": [
            {
              "reportNumber": "00001",
              "reportedBy": "Xxx",
              "_links": {
                "self": {
                  "href": "http://localhost:8080/api/reports/00001"
                },
                "city": {
                  "href": "http://localhost:8080/api/reports/00001/city"
                },
                "reportStatus": {
                  "href": "http://localhost:8080/api/reports/00001/reportStatus"
                },
                "reportDates": {
                  "href": "http://localhost:8080/api/reports/00001/reportDates"
                },
                "accident": {
                  "href": "http://localhost:8080/api/reports/00001/accident"
                }
              }
            }
        ]
    },
    "page": {
        "size": 20,
        "totalElements": 4,
        "totalPages": 1,
        "number": 0
    }
}

And i need to fetch all links recursively.

Just in case reportDates have more 2 links, how can i get them?
In accident, there is link to report.
Here is response from accident:

{
    "accidentDate": "2015-07-05",
    "accidentLocation": "In Main Street",
    "_links": {
        "self": {
            "href": "http://localhost:8080/api/accidents/00001"
        },
        "city": {
            "href": "http://localhost:8080/api/accidents/00001/city"
        },
        "report": {
            "href": "http://localhost:8080/api/accidents/00001/report"
        }
    }
}

fetching report will make infinite loop, because report have links accident and accident have links to report.
Thanks for your response. :+1:

Ok I see the problem. Well you could implement an own fetch function which deals with this situation: https://github.com/guylabs/angular-spring-data-rest#exchange-the-underlying-fetch-function.
Because implementing a logic for that is not that trivial, as you would need to have a structure where you would store all links and which links are referencing other links and therefore it would consume memory just for avoiding infinite loops. Do you know what I mean?
Another solution would be to add a level option where you could define how much levels it should recursively resolve such that you do not get an infinite loop.
I think the second solution would be easier and doesn't complicate the whole codebase.
What do you think?
Thanks and regards,
Guy

I see..
so what you mean we must implement new fetchFunction with level option ?
I think it still not solve the problem, because if i have to avoid infinite loop with 2 level recursive and i need another link fetch rescursively until 4 level, then i will not get all the fetched data.
How about you add param array of ignoredFetchLinkNames, and while fetching the links it will skip the links in ignoredFetchLinkNames.
What do you think?
Thanks @guylabs

But then you would have the same problem that when you need the link fetched once you are not able to fetch it.
One possibility would be to create a map which has the self link as key and a list of linkNames which were already fetched for that self key here: https://github.com/guylabs/angular-spring-data-rest/blob/master/src/angular-spring-data-rest-provider.js#L257
Then here https://github.com/guylabs/angular-spring-data-rest/blob/master/src/angular-spring-data-rest-provider.js#L252 we would check if the link to be fetched is already in the list and then skip the fetching.
This way you could use the recursive fetching and it would just fetch each link once.
I think this would be the proper solution. What do you think?
Regards,
Guy

I think that's a good idea @guylabs !
So we can use recursive without thinking about infinite loop.
when you would implement that idea ?

Hi Romy,
well that is the other problem. As I do  not have much time and I also have some other open source projects I need to work on I cannot tell you. But you could come up with a solution with some tests and create a pull request if you need the feature in the near future.
Thanks and regards,
Guy

@guylabs
SpringDataRestAdapter.process(response,  ['anotherLink', 'testLink']).then(function(processedResponse) {
  ...
});

Can i use recursive in that code example?
SpringDataRestAdapter.process(response,  ['anotherLink', 'testLink'], true).then(function(processedResponse) {
  ...
});

Yes this should also work, so you tell the adapter to recursively process the anotherLink and testLink. So does this solves your problem?

@guylabs yes.. that solve one of my problem..
now only infinite loop problem..

Pull request #15 has been integrated.

Hi @guylabs,
How to reinitialized the linkMap for each item in _embeddedItems ?
For example:
{
    "_links": {
        "self": {
            "href": "http://localhost:8080/api/reports"
        }
    },
    "_embedded": {
        "reports": [
            {
              "reportNumber": "00001",
              "_links": {
                "self": {
                  "href": "http://localhost:8080/api/reports/00001"
                },
                "city": {
                  "href": "http://localhost:8080/api/reports/00001/city"
                },
                "accident": {
                  "href": "http://localhost:8080/api/reports/00001/accident"
                }
              }
            },
            {
              "reportNumber": "00002",
              "_links": {
                "self": {
                  "href": "http://localhost:8080/api/reports/00002"
                },
                "city": {
                  "href": "http://localhost:8080/api/reports/00002/city"
                },
                "accident": {
                  "href": "http://localhost:8080/api/reports/00002/accident"
                }
              }
            }
        ]
    },
    "page": {
        "size": 20,
        "totalElements": 4,
        "totalPages": 1,
        "number": 0
    }
}

Should each item have their own linkMap ?

Hi Romy,
so you want to move the line https://github.com/guylabs/angular-spring-data-rest/blob/master/src/angular-spring-data-rest-provider.js#L370 to here https://github.com/guylabs/angular-spring-data-rest/blob/master/src/angular-spring-data-rest-provider.js#L136 right?
Well I think that would be a good idea, as I think this would be the correct way of dealing with this map. I can do that when I have more time than now or may you want to create a pull request for this small change such that you can use it in the master?
Thanks and regards,
Guy

I think if we move it like you said, then it will cause infinite loop again, every time we call function processData the linkMap is empty again.
CMIIW

Yes you are right I just overflew it briefly. Well then we need to leave it as it is right now or is there still an issue?

Hi Guy,
Yes there still an issue.
API return like this:
{
    "_links": {
        "self": {
            "href": "http://localhost:8080/api/reports"
        }
    },
    "_embedded": {
        "reports": [
            {
              "reportNumber": "00001",
              "_links": {
                "self": {
                  "href": "http://localhost:8080/api/reports/00001"
                },
                "city": {
                  "href": "http://localhost:8080/api/reports/00001/city"
                },
                "accident": {
                  "href": "http://localhost:8080/api/reports/00001/accident"
                }
              }
            },
            {
              "reportNumber": "00002",
              "_links": {
                "self": {
                  "href": "http://localhost:8080/api/reports/00002"
                },
                "city": {
                  "href": "http://localhost:8080/api/reports/00002/city"
                },
                "accident": {
                  "href": "http://localhost:8080/api/reports/00002/accident"
                }
              }
            }
        ]
    },
    "page": {
        "size": 20,
        "totalElements": 4,
        "totalPages": 1,
        "number": 0
    }
}

If the _embedded is Array and city in report[0] and report[1] is the same, then city in report[1] will not be fetched. That's why we should have linkMap in each _embeddedItems.
Any solution for this issue ?

Hi Romy,
currently not as I do not have the time for it. But maybe you could come up with a solution as you have the context and currently work with it more than I do ;). Then we can have a look at it and merge it into the master.
Thanks and regards,
Guy


Create UX contribution guide on the wiki

Create a guide on the Wiki to show UXers how to contribute. Mention:

Look for the UX label on github https://github.com/seattle-uat/civiform/labels/UX
Look for the Good First Issue label https://github.com/seattle-uat/civiform/labels/good first issue
Join the Miro board (whatever the link ends up being)
Drop your mocks in Miro, put them in a frame, and copy the link

https://github.com/seattle-uat/civiform/wiki/UX


DateTime is not supported for AppendValue method of Appender.

https://github.com/Giorgi/DuckDB.NET/blob/5585dc529a9e7b92fb8478acf4508b4f3e2eec5c/DuckDB.NET.Data/DuckDBAppender.cs#L160

It appears its supported in the underlying method, but not in the AppendValue method overloads. I will add support and create a PR.

Implemented in 2cc5b99


Cluster state refactor Part 2

Which issue does this PR close?

Closes #554
Rationale for this change

See original ticket for full description but the tl;dr; is:

The existing interface for managing shared state among schedulers is too low-level and both pushes too much complexity into other layers and prevents us from taking advanatage of data store specific freatures (atomics, transactions, etc) to avoid locking in the application layer.
By forcing everything through the KV interface we force all the serialization overhead even if we are only using in-memory state.

What changes are included in this PR?

There are a lot of changes because the StateBackendClient was baked in everywhere but at a high level:

Create JobState trait to complement ClusterState created in last PR. This in the interface for storing/managing global state w/r/t jobs and sessions.
Refactor in-memory implementation to not serialize things to protobuf
Provide KeyValueState implementation based on existing KV interface so we can continue to use etcd and sled for state without any changes.
Take advantage of curated job architecture to minimize distributed locking. Since jobs are owned by a single scheduler we don't need to lock beyond the node level.
Cleanup configs.
Move everything related to state the ballista_scheduler::cluster module

I removed the separate configs for cluster-backend and config-backend because it seems confusing. So currently if you want to use different implementations for the ClusterState and JobState you would need to write your own entrypoint. We might introduce standard "profiles" (standalone/ha/etc) for setting up the two state backends on different implementations but for now it seems too noisy config wise.
NOTE: I was not able to run the integration tests using the standard configuration due to weird timeouts. When using push scheduling everything worked fine so not sure what's going on. I also checked on main and see the same issue so maybe something related to the M1 macbook?
Are there any user-facing changes?

The storage layout for etcd and sled are simplified so existing state would not be valid after upgrade.

@mingmwang @yahoNanJing @Dandandan

Not sure why this is failing (https://github.com/apache/arrow-ballista/actions/runs/4123347318/jobs/7121701363) but it doesn't seem to be an issue with the actual formatting

I'll plan on merging this weekend unless someone else would like more time to review.


Improve README.md

Adding features of the program.

can I be assigned this?

can I be assigned this?

Go ahead and make a pull request

@sakshi2912 thank you.


in ios routes are not displaying

Hi,
Thanks for develop this package. In my ios simulator routes are displaying but coming to device routes are not displaying.
Regards.

Do you call TKCustomMapRenderer.InitMapRenderer(); ?

yes i called it in my AppDelegate.cs

In my ios simulator routes are displaying good but coming to device routes are not displaying.

Maybe it is the linker again. You can try this.
https://github.com/TorbenK/TK.CustomMap/issues/29#issuecomment-188826339

no it's not working in my case. i don't have any problem in android and ios simulators also, routes are showing well but in ios devices only the routes were not showing

That sounds exactly like the linker issue to me.
Anyway, you can observe RouteCalculationFailed to see what's going wrong.

in ios simulator it's not firing, but in device it's firing and shows  error message as a "Directions Not Available".

Please check whether directions API is avaiable in your country. http://www.apple.com/uk/ios/feature-availability/#maps-directions

yes directions API is not available here sorry


New EulerToQuaternion

Testing and tweaking on @lucas-vrtech's rig while @danwillm is unavailable

@lucas-vrtech it can be slightly faster: https://github.com/libgdx/libgdx/blob/master/gdx/src/com/badlogic/gdx/math/Quaternion.java#L131

@yuripourre Excellent, thank you for the suggestion. I will give that a try.


Skip spybackend test when in racetest

The racetest is steadily failing since #11197 has been merged.
Deeper analysis shows that it fails on spybackend with no error message and memory profiling hints that it's because the test is very intensive on memory when running in race mode. Running the test locally on a machine with higher memory will succeed.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ymesika
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: linsun
If they are not already assigned, you can assign the PR to them by writing /assign @linsun in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: linsun, ymesika
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [linsun]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Upgrade planner to Angular 6 and RxJS 6

Note: If there are pending changes to the PR, prefix the PR title with "WIP" and add the label "DO NOT MERGE"
Mandatory

[x] What does this PR do?
This PR upgrades planner to Angular 6 and RxJS 6

[ ] What issue/task does this PR references?

[ ] Are the tests Included?

Optional

[ ] Is the documentation Included?

[ ] Are the Release Notes included?

[ ] @mention(s) to expected reviewer(s) included

[test]

Closing this PR. New PR: https://github.com/fabric8-ui/fabric8-planner/pull/2794


OpenRoad crashes due to an assert

Describe the bug
I installed binaries from:

https://github.com/Precision-Innovations/OpenROAD/releases/download/2023-07-31/openroad_2.0_amd64-ubuntu22.04-2023-07-31.deb
https://github.com/YosysHQ/oss-cad-suite-build/releases/download/2023-08-04/oss-cad-suite-linux-x64-20230804.tgz
https://www.klayout.org/downloads/Ubuntu-22/klayout_0.28.10-1_amd64.deb

And got OFSR as of 392edae54a52586959855228f9fbfee50ebb56e4
When testing installation with make, openroad crashes due to an assert:
openroad: ./src/odb/src/db/dbWireCodec.cpp:481: void odb::dbWireEncoder::newPathVirtualWire(int, odb::dbTechLayer*, odb::dbWireType): Assertion `(jct_id >= 0) && (jct_id < _idx)' failed.
Signal 6 received
Stack trace:
0# 0x000055732DC089CD in /usr/bin/openroad
1# 0x00007F02D7242520 in /lib/x86_64-linux-gnu/libc.so.6
2# pthread_kill in /lib/x86_64-linux-gnu/libc.so.6
3# raise in /lib/x86_64-linux-gnu/libc.so.6
4# abort in /lib/x86_64-linux-gnu/libc.so.6
5# 0x00007F02D722871B in /lib/x86_64-linux-gnu/libc.so.6
6# 0x00007F02D7239E96 in /lib/x86_64-linux-gnu/libc.so.6
7# odb::dbWireEncoder::newPathVirtualWire(int, odb::dbTechLayer*, odb::dbWireType) in /usr/bin/openroad
8# grt::RepairAntennas::addWireTerms(grt::Net*, std::vector<grt::GSegment, std::allocatorgrt::GSegment >&, int, int, int, odb::dbTechLayer*, int, std::map<grt::RoutePt, std::vector<grt::Pin*, std::allocatorgrt::Pin* >, std::lessgrt::RoutePt, std::allocator<std::pair<grt::RoutePt const, std::vector<grt::Pin*, std::allocatorgrt::Pin* > > > >&, odb::dbWireEncoder&, std::map<int, odb::dbTechVia*, std::less, std::allocator<std::pair<int const, odb::dbTechVia*> > >&) in /usr/bin/openroad
9# grt::RepairAntennas::makeNetWire(odb::dbNet*, std::vector<grt::GSegment, std::allocatorgrt::GSegment >&, std::map<int, odb::dbTechVia*, std::less, std::allocator<std::pair<int const, odb::dbTechVia*> > >&) in /usr/bin/openroad
10# grt::RepairAntennas::makeNetWires(std::map<odb::dbNet*, std::vector<grt::GSegment, std::allocatorgrt::GSegment >, grt::cmpById, std::allocator<std::pair<odb::dbNet* const, std::vector<grt::GSegment, std::allocatorgrt::GSegment > > > >&, int) in /usr/bin/openroad
11# ant::AntennaChecker::checkAntennas(odb::dbNet*, bool) in /usr/bin/openroad
12# ant::check_antennas(char const*, bool) in /usr/bin/openroad
13# 0x000055732E616A04 in /usr/bin/openroad
14# TclNRRunCallbacks in /lib/x86_64-linux-gnu/libtcl8.6.so
15# 0x00007F02DB808028 in /lib/x86_64-linux-gnu/libtcl8.6.so
16# Tcl_EvalEx in /lib/x86_64-linux-gnu/libtcl8.6.so
17# Tcl_Eval in /lib/x86_64-linux-gnu/libtcl8.6.so
18# sta::sourceTclFile(char const*, bool, bool, Tcl_Interp*) in /usr/bin/openroad
19# ord::tclAppInit(Tcl_Interp*) in /usr/bin/openroad
20# Tcl_MainEx in /lib/x86_64-linux-gnu/libtcl8.6.so
21# main in /usr/bin/openroad
22# 0x00007F02D7229D90 in /lib/x86_64-linux-gnu/libc.so.6
23# __libc_start_main in /lib/x86_64-linux-gnu/libc.so.6
24# _start in /usr/bin/openroad
Command terminated by signal 6
Elapsed time: 0:08.66[h:]min:sec. CPU time: user 0.75 sys 0.17 (10%). Peak memory: 190908KB.
make[1]: *** [Makefile:655: do-5_1_grt] Error 134
make[1]: Leaving directory '/media/sf_virtual_box/OpenROAD-flow-scripts/flow'
make: *** [Makefile:655: results/nangate45/gcd/base/5_1_grt.odb] Error 2
Expected Behavior
This is a installation test as mentionned at https://github.com/The-OpenROAD-Project/OpenROAD-flow-scripts/blob/master/docs/user/BuildWithPrebuilt.md
Environment
It is a prebuilt installation as mentioned above.

kernel: Linux 5.19.0-32-generic
os: Ubuntu 22.04.2 LTS (Jammy Jellyfish)

To Reproduce
make
Relevant log output
No response
Screenshots
No response
Additional Context
No response

https://github.com/The-OpenROAD-Project/OpenROAD-flow-scripts/issues/1306#issuecomment-1665349789 similar to this.
@vvbandeira is OpenROAD Debian package issue?
Because locally built binaries working fine.

I suggest trying the latest build as there was a similar bug fixed recently.

Crash is gone with latest .deb. Thanks!

Also bug was similar to https://github.com/The-OpenROAD-Project/OpenROAD/pull/3757.


Validate file name/level name

Cannot be empty
Cannot contain invalid characters (i.e. special characters used for file system paths)

Fixed in #15


fix(Curriculum): Fixed assert cases

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #51330

Test images

As a new contributor, we encourage you to read our contributing guidelines.
We expect our contributors to be aware of the process specific to this project. Following the guidelines religiously earns you the respect of fellow maintainers and saves everyone time.
Some examples of this are:

Do not edit files directly through GitHub – while you can, it's not a good idea.
Make sure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously.
Use the correct way to link issues in the description of the PR by updating the XXXXXX. Do not just add issue numbers everywhere and anywhere you feel like.
Keep mentions and review requests to a minimum. We understand you are excited about contributing, and our maintainers will get back to you as soon as they get a chance.
Do not work directly off your main branch - create a new branch for the changes you are working on.

We appreciate you taking the time to help us, and we hope to see more contributions from you.
Happy Contributing.

Thanks for taking the time to contribute. We have decided to go with another PR that satisfies the needs of the issue.
We are grateful for your help and look forward to future contributions.
Happy coding!


Padder

updated changelog
added Padder
added unittest

I commented, but also committed to address those comments.
The code looks fine to me now but I have not tested it yet.

Is there a reason to pad angles before and after? I'd be tempted to remove that functionality and only run on the x,y,z dimensions.

I'd say to keep it.  Padding in angles is a very basic form of sinogram
completion in case of limited angle data.
On Fri, 18 Jun 2021 at 12:36, Gemma Fardell @.***>
wrote:

Is there a reason to pad angles before and after? I'd be tempted to remove
that functionality and only run on the x,y,z dimensions.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/TomographicImaging/CIL/pull/910#issuecomment-863941425,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACMDSCGUK5GZJMZYWS6XNVTTTMOSVANCNFSM4637353A
.

I guess I don't really understand padder to do that. Padding the data in the angular dimension is fine, if it's sorted by angle initially (which I don't think we ever impose or require). But that's very specific to padding the array in one direction, wouldn't you want to  specify the angles you want to create and where it should get the data from (i.e. nearest projection, linear interp of two projections)? You might want to pad it between two collected angles, not just outside the angles that happen to be at index 0 and -1.
It looks like this pads the angular array too, so presumably if you have [0,45,90] and pad by 1, with 'extend' you get [0,0,45,90,90], with the data replicated also. It also doesn't make sense to me to have options ''reflect', 'symmetric', 'wrap', 'edge''.  I think I'd expect 'extend' 'constant or 'linear interp'.
I think there's an argument for a separate processor to handle it as it's a very different use case to the spatial padding which we know is always uniform and ordered.

Good points. I see now it is a separate case that requires more thought. So
I agree it makes sense to remove support for the angle dimension.
On Fri, 18 Jun 2021 at 13:28, Gemma Fardell @.***>
wrote:

I guess I don't really understand padder to do that. Padding the data in
the angular dimension is fine, if it's sorted by angle initially (which I
don't think we ever impose or require). But that's very specific to padding
the array in one direction, wouldn't you want to specify the angles you
want to create and where it should get the data from (i.e. nearest
projection, linear interp of two projections)? You might want to pad it
between two collected angles, not just outside the angles that happen to be
at index 0 and -1.
It looks like this pads the angular array too, so presumably if you have
[0,45,90] and pad by 1, with 'extend' you get [0,0,45,90,90], with the data
replicated also. It also doesn't make sense to me to have options
''reflect', 'symmetric', 'wrap', 'edge''. I think I'd expect 'extend'
'constant or 'linear interp'.
I think there's an argument for a separate processor to handle it as it's
a very different use case to the spatial padding which we know is always
uniform and ordered.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/TomographicImaging/CIL/pull/910#issuecomment-863969959,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACMDSCCNGEK4O46DMEGYXZDTTMUWBANCNFSM4637353A
.

@paskino and I will make any changes and merge today,


Fix crash nil outstream

Expected to fix #523
Looks like there is a code path in which websocket.sslTrust() may be called when outputStream is nil. The cast to create domain is unsafe, because nil as! String may crash, while nil as! String? will never crash.
Using an optional String? here is perfectly fine because a String would be cast to String? anyway when returned in the tuple (SecTrust?, String?).
I have also added a guard at the top which itself will probably fix the issue. IMO having both safeguards in place is the best practice. TheoutputStream should not be nil for this function to produce anything useful (hence the guard). While it is technically still possible for kCFStreamSSLPeerName to be nil, although it should not be.

Don’t worry about it! Took me a few moments to realize why that works too.

We are also seeing a lot of crashes caused by nil output stream. This PR attempts to solve the underlying issue https://github.com/daltoniam/Starscream/pull/519
Either way, this PR or both should be merged in asap.

Is there a consensus on the proper/best fix for the sslTrust() crash (this PR or https://github.com/daltoniam/Starscream/pull/519?) We are seeing it quite frequently as well and would like to pull in the fix for our next release even if its not officially merged into the library yet.

@mgrant34 @jrendel My team deployed using my branch of StarScream late last week. Steady rate of ~500 crashes/day in StarScream has dropped to 0 in the updated version.
I suggest you deploy off my branch until @daltoniam comes back and merges this. Put this in your Podfile:
# Override Starscream until the fix: https://github.com/daltoniam/Starscream/pull/524
pod 'Starscream', :git => 'git@github.com:adamkaplan/Starscream.git', :branch => 'fix-crash-nil-outstream'

Sorry about the delay. Looks good! Thanks!

thanks @daltoniam

@daltoniam could you please create a new release? Seems like a lot (or all) of the library users are affected by this crash. Also projects like https://github.com/socketio/socket.io-client-swift could then update to the new version.

+1 I have also created an issue https://github.com/daltoniam/Starscream/issues/534 with 6 likes, even a minor version bump would really help a lot of us. Please!


feat: migrate definition of the subnet privatek8s-tier in the private vnet from jenkins-infra/azure

This PR should not change anything: the privatek8s-tier subnet was imported in the azure-net's state with the command
terraform import 'azurerm_subnet.privatek8s_tier' '/subscriptions/dff2ec18-6a8e-405c-8e45-b7df7465acf0/resourceGroups/private/providers/Microsoft.Network/virtualNetworks/private-vnet/subnets/privatek8s-tier'

(edit) internal renaming of the subnet data-tier. Used the command
terraform state mv 'azurerm_subnet.data_tier' 'azurerm_subnet.private_vnet_data_tier'

to avoid destroy/create.

No changes. Your infrastructure matches the configuration.


[doc] Add use cases to the README

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


Contact

Super sorry to reply here but was curious the best way to contact you to ask a few questions on another one of your projects? Discord/email/? looking forward to your response!
(tried twitter but cant send message there)

you can contact me via my website https://fransbouma.com :)


Hosted macOS workflows will experience longer wait times the week of December 14th.

Breaking changes
GitHub's macOS datacenter is performing scheduled maintenance December 14-18. During this time customers may experience longer than normal wait times for their macOS workflows to begin.
Target date
December 14-18
Possible impact
Jobs using any of the macOS virtual environments may experience longer than normal queue times. In some cases it's possible workflows will time out, be cancelled, and need to be restarted.
Virtual environments affected

[ ] Ubuntu 16.04
[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[X] macOS 10.13
[X] macOS 10.14
[X] macOS 10.15
[X] macOS 11.0
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

Good luck on your work. I wonder, if there will be any discounts on macOS hosted github-actions in this time interval?

Does this maintenance include fixing the network issues with macOS?

I wonder, if there will be any discounts on macOS hosted github-actions in this time interval?

The problem is that there is no way to re-run individual jobs in GitHub Actions so far.

Volleyball geil

Thank you

@Regarding hawkery here @regamask

/Allupdated block

Nice

Quite bad timing knowing that App Store Connect is going on holiday next week and everyone rushes to release their apps.

Thanks for the warning!

I'm also facing network issues when installing yarn packages on a MacOS runner. I get error messages similar to the ones shown by @styfle , has this issue been identified and will the maintenance try to fix it, or should I raise it to the Github support?

Does this maintenance include fixing the network issues with macOS?

@styfle actually it's a bug from yarn. https://github.com/yarnpkg/yarn/issues/8242
The reason for this bug is that the macOS host disk is slow, and extra  large number of files from npm package such as rxjs would trigger this bug in yarn.
Maybe you have already observed that this  issue always happened on rxjs @material/icons etc. It couldn't be so accident that network always failure on downloading these packages.

@Brooooooklyn Its not just yarn that fails, all network requests fail eventually.
Even spawning a server on localhost will sometimes fail with ECONNREFUSED.

@styfle can you provide repro steps? I want to try and chase that down.

@nodeselector Thanks! The yarn issue should be easy to reproduce because it fails early.
Create a repo with this package.json and yarn.lock in the root.
And then create a workflow that runs yarn install.
on:
  push:
    branches:
    - master
    tags:
    - '!*'
  pull_request:

jobs:
  test:
    timeout-minutes: 15
    strategy:
      fail-fast: false
      matrix:
        os: [macos-latest]
        node: [10, 12]
    runs-on: ${{ matrix.os }}
    steps:
      - uses: actions/checkout@v2
        with:
          fetch-depth: 100
      - uses: actions/setup-node@v1
        with:
          node-version: ${{ matrix.node }}
      - run: yarn install

Y'all are amazing

Awesome indeed.

WebDav binary codes are not authentic. The codes were submitted by William (Dav)id Smith. DOB 7-23-1977. He stole the codes off my Moto e5 Plus.  Then submitted the data on github and VLC media as a decoder (DAV 1D IS AV 1 DECODER :D). This is why the network is all messed up. Ive been back tracing his steps and fixing everything. Most of the time all I do is search the web and the sites that appear in the suggestions is mostly ones that ge is on. He has been using my gmail & everytime i ask him to stop using it he denies it. It is to the point where I've had enough. Ive tried to make police reports and they do jot take cyber crime serious around here. So I am going to hire a lawyer ti getbthe process on tge ball.   They i can claim my assets.

Was publishing a GitHub action but not getting marketplace agreement option during release - https://github.com/Zomato/android-lib-release-action
is this somehow related to this?? please help

Why is it a issue this week we need these systems running what can we do

we need to boost the server speed it needs a severe enhanced signal

Does this maintenance include fixing the network issues with macOS?

@styfle actually it's a bug from yarn. yarnpkg/yarn#8242
The reason for this bug is that the macOS host disk is slow, and extra large number of files from npm package such as rxjs would trigger this bug in yarn.
Maybe you have already observed that this issue always happened on rxjs @material/icons etc. It couldn't be so accident that network always failure on downloading these packages.

Try to not merge them so many times only merge them about 4 times a day and even when you merge them you need to filter out all the bad ones

Keep it simple try to earn only merge maybe 3 times a day don't repeat process is more than you need to keep it simple go back to the basics

You're overworking the computer is confusing it and when you get confused you can't function so you need to make sure the computers okay

Think about it a computers like a little kid is going to do exactly what you tell it to do but if you overwork it it's going to shut down a computer is like a body if you don't get that what it needs then it can't survive and it can't function

Breaking changes
GitHub's macOS datacenter is performing scheduled maintenance December 14-18. During this time customers may experience longer than normal wait times for their macOS workflows to begin.
Target date
December 14-18
Possible impact
Jobs using any of the macOS virtual environments may experience longer than normal queue times. In some cases it's possible workflows will time out, be cancelled, and need to be restarted.
Virtual environments affected

[ ]  Ubuntu 16.04
[ ]  Ubuntu 18.04
[ ]  Ubuntu 20.04
[x]  macOS 10.13
[x]  macOS 10.14
[x]  macOS 10.15
[x]  macOS 11.0
[ ]  Windows Server 2016 R2
[ ]  Windows Server 2019

You need to take that yarn completely out

Breaking changes
GitHub's macOS datacenter is performing scheduled maintenance December 14-18. During this time customers may experience longer than normal wait times for their macOS workflows to begin.
Target date
December 14-18
Possible impact
Jobs using any of the macOS virtual environments may experience longer than normal queue times. In some cases it's possible workflows will time out, be cancelled, and need to be restarted.
Virtual environments affected

[ ]  Ubuntu 16.04
[ ]  Ubuntu 18.04
[ ]  Ubuntu 20.04
[ ]

macOS 10.13
[ ]  macOS 10.14
[ ]  macOS 10.15
[ ]  macOS 11.0
[ ]  Windows Server 2016 R2
[ ]  Windows Server 2019
just the yarn instalation is what stopped it

The maintenance for this week is now complete! If there are continued issues, please let us know by creating new issues because they will be unrelated to this maintenance cycle. Thanks for your patience everyone!

HiengoKu

How can I stop my phone from causing anymore problems?
On Tue, Dec 15, 2020, 8:24 PM RegaMask<EMAIL_ADDRESS>wrote:

@regarding https://github.com/regarding hawkery here @regamask
https://github.com/regamask
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/actions/virtual-environments/issues/2247#issuecomment-745721441,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASDGLLDOOUQJ73TUTH2A273SVAK7VANCNFSM4UWWVY4A
.

Can someone help me or not?
On Mon, Dec 21, 2020, 8:31 AM Gina Henderson<EMAIL_ADDRESS>wrote:

How can I stop my phone from causing anymore problems?
On Tue, Dec 15, 2020, 8:24 PM RegaMask<EMAIL_ADDRESS>wrote:

@regarding https://github.com/regarding hawkery here @regamask
https://github.com/regamask
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/actions/virtual-environments/issues/2247#issuecomment-745721441,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASDGLLDOOUQJ73TUTH2A273SVAK7VANCNFSM4UWWVY4A
.

Breaking changes
GitHub's macOS datacenter is performing scheduled maintenance December 14-18. During this time customers may experience longer than normal wait times for their macOS workflows to begin.
Target date
December 14-18
Possible impact
Jobs using any of the macOS virtual environments may experience longer than normal queue times. In some cases it's possible workflows will time out, be cancelled, and need to be restarted.
Virtual environments affected
* [ ]  Ubuntu 16.04

* [ ]  Ubuntu 18.04

* [ ]  Ubuntu 20.04

* [x]  macOS 10.13

* [x]  macOS 10.14

* [x]  macOS 10.15

* [x]  macOS 11.0

* [ ]  Windows Server 2016 R2

* [ ]  Windows Server 2019

Delete

@thejoebourneidentity It's Jan 2, and wait times on macOS 11.0 runners still seem to be very long. Is this because of a general scarcity of Big Sur runners or is there ongoing maintenance on those?

@thejoebourneidentity It's Jan 2, and wait times on macOS 11.0 runners still seem to be very long. Is this because of a general scarcity of Big Sur runners or is there ongoing maintenance on those?

I’m seeing over an hour wait in the queue for my workflows on a paid, private repository.

I’m seeing over an hour wait in the queue for my workflows on a paid, private repository.

I’m seeing over an hour wait in the queue for my workflows on a paid, private repository.

My workflow with two jobs on a PR now shows three checks, two passing and one failing. One of them is the original Ubuntu job, which started instantly. The failing one is the original macOS job, which sat in the queue for almost 2 hours until it was cancelled, and now reports as a failed check on the PR, making it unclear for maintainers. The other passing check is the automatically restarted macOS job, which completed two hours after the original Ubuntu job completed, which was soon after the PR push.

I’m seeing over an hour wait in the queue for my workflows on a paid, private repository.

My workflow with two jobs on a PR now shows three checks, two passing and one failing. One of them is the original Ubuntu job, which started instantly. The failing one is the original macOS job, which sat in the queue for almost 2 hours until it was cancelled, and now reports as a failed check on the PR, making it unclear for maintainers. The other passing check is the automatically restarted macOS job, which completed two hours after the original Ubuntu job completed, which was soon after the PR push.

@richiksc @tonyarnold
https://github.com/actions/virtual-environments/issues/2247#issuecomment-748238434
@tonyarnold refer to created issue #2381
I also do experience long waiting queues for macOS runners - both private/public repositories.

@richiksc @tonyarnold
https://github.com/actions/virtual-environments/issues/2247#issuecomment-748238434
@tonyarnold refer to created issue #2381
I also do experience long waiting queues for macOS runners - both private/public repositories.

switching the base

switching the base

switching the base

switching the base

Could someone from GitHub please update this issue and let us know what's happening with the extremely long queue times for macOS 11 runners? I'm at a bit of a standstill with basic CI taking over an hour every time it's run.

Could someone from GitHub please update this issue and let us know what's happening with the extremely long queue times for macOS 11 runners? I'm at a bit of a standstill with basic CI taking over an hour every time it's run.

Same issue here, queue times are really long on mac-os hosted machines. (around 1h to start the workflow when it doesn't "check fail")
Can we get an ETA on a resolution for this?

Same issue here, queue times are really long on mac-os hosted machines. (around 1h to start the workflow when it doesn't "check fail")
Can we get an ETA on a resolution for this?

Yes, the problem is there all the time .. How can I find out who is behind it and is following me?  Jan can I delete it ??
Dnia 12 stycznia 2021 23:19 KeiroMidori   napisał(a):
Same issue here, queue times are really long on mac-os hosted machines. (around 1h to start the workflow when it doesn't "check fail")
Can we get an ETA on a resolution for this?
—  You are receiving this because you commented.  Reply to this email directly,  github.com view it on GitHub , or  github.com unsubscribe .

Yes, the problem is there all the time .. How can I find out who is behind it and is following me?  Jan can I delete it ??
Dnia 12 stycznia 2021 23:19 KeiroMidori   napisał(a):
Same issue here, queue times are really long on mac-os hosted machines. (around 1h to start the workflow when it doesn't "check fail")
Can we get an ETA on a resolution for this?
—  You are receiving this because you commented.  Reply to this email directly,  github.com view it on GitHub , or  github.com unsubscribe .

Migraines


Add support for native node esm

Fixes #11

Just gave a quick test, and the require.resolve in hook-names is still an issue as it doesn't get caught by the content to replace regex

Ah shoot, looks like I need something more reliable than my shitty regexes. I'll check tomorrow.

Certainly no worries / rush! That's more of an issue with TSC anyhow, not the regex. That require.resolve is just as invalid in the "esm" that TSC outputs. Not sure why it doesn't do anything with that?


Display older comments

This hasn't been added yet, has it? I can't find evidence of it, but I'm not sure why we didn't create an Issue for it.
In machine info at a location, the most recent five comments should be displayed.

I confirmed that older comments aren't on the iOS app yet.
Some users are getting confused by comments that reference comments they can't see. So I think it would be great to have this added to the app.

More detail: On the website we display the most current comment (with a timestamp), and then there's a button saying "show past conditions" that, when clicked, shows the last FIVE comments.
Note to myself, I think I'm going to change "show past conditions" to "show past comments."

When the user taps the machine from the location info view they are brought to this view with the past condition

Great! Can you include a timestamp for each one?
Also, this is almost unrelated, but I've noticed that the iOS app has a tendency to double post comments. I don't know if it's an issue of the comment form not clearing out after it's been submitted (that probably doesn't make sense) or if it's a weird network-related issue. It definitely doesn't happen 100% of the time. But it happens fairly often.

Yup, I added that after I sent that image. I will open a new issue for what you brought up. Going to close this issue