Erizo components seem to crash randomly

TypeError: Cannot read property 'publishers' of undefined
at Object.that.removePublisher (/home/karthik/licode/erizo_controller/erizoController/roomController.js:345:57)
at Socket. (/home/karthik/licode/erizo_controller/erizoController/erizoController.js:759:60)
at Socket.emit (events.js:95:17)
at Socket.emit (/home/karthik/licode/node_modules/socket.io/lib/socket.js:128:10)
at Socket.onclose (/home/karthik/licode/node_modules/socket.io/lib/socket.js:425:8)
at Client.onclose (/home/karthik/licode/node_modules/socket.io/lib/client.js:232:24)
at Socket.emit (events.js:117:20)
at Socket.onClose (/home/karthik/licode/node_modules/socket.io/node_modules/engine.io/lib/socket.js:303:10)
at WebSocket.g (events.js:180:16)
at WebSocket.emit (events.js:92:17)
2016-01-17 20:56:41.830  - INFO: TokensResource - Created token for room  569b11c318a625ec17bc2373 and service  568a1ab7069cf7655216bf54
2016-01-17 20:56:44.167  - INFO: TokensResource - Created token for room  569b11c318a625ec17bc2373 and service  568a1ab7069cf7655216bf54
2016-01-17 20:56:49.048  - INFO: CloudHandler - ErizoController 1  in  <IP_ADDRESS> does not respond. Deleting it.
2016-01-17 20:56:49.049  - INFO: CloudHandler - [CLOUD HANDLER]: Warning! No erizoController is available.
express deprecated res.send(body, status): Use res.status(status).send(body) instead resource/tokensResource.js:172:21
_usr_bin_nodejs.0.crash.txt

Ah, looks like an issue on my end. I will try raising the ulimit.
2016-01-17 20:56:17,326  - DEBUG: WebRtcConnection - Setting VIDEO CANDIDATE
2016-01-17 20:56:17,326  - DEBUG: NiceConnection - Setting remote candidates 0, mediatype 0
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injectorboost::system::system_error >'
2016-01-17 20:56:17.327  - INFO: ErizoJSController - Process Signaling message:<PHONE_NUMBER>08819260 /#r3sWro3JYw5jcRIYAAAo { type: 'candidate',
candidate:
{ sdpMLineIndex: 0,
sdpMid: 'audio',
candidate: 'a=candidate:379460087 2 tcp<PHONE_NUMBER> 2607:fb90:f92:ab65:0:4a:4a78:401 0 typ host tcptype active generation 0' } }
what():  epoll: Too many open files
./launch.sh: line 5: 23349 Aborted                 (core dumped) node $*

Does erizo open a lot more connections than I expect? I only had 10 or 11 people in one room, and then it crashed when the 11th or 12th person tried to join. My ulimit is 1024, and the only extra connection to the server I had was an ssh session. I didn't have any extra open files.
How many connections/files does erizo open per person?

I'd like to reopen this issue because it may point to a fd leak of some kind. I'm using licode in a non-standard way. Rather than using Licode's concept of rooms, we have a slightly different, higher level concept of "spaces". So, I use one global, persistent Licode room.
I've seen licode periodically crash, usually days or weeks apart--with tens of people using it in the mean time.

I've just pushed a fix for a fd leak in ErizoAgent's log files.
What value did you set up in
config.erizoAgent.maxProcesses

The fd leak had the side effect of further limiting the amount of sockets each erizoJS (MCU process) could open as fds are inherited from the parent process (ErizoAgent in this case).
In any case you can try updating from the master branch and tell us how it went

I didn't set a value for that--I'm not sure what a good value for that would be.
This is a really well architected project, but my only gripe is that it's really poorly documented. It would be nice if there were (detailed) blog posts about how different components work. There are currently a few "god scripts" that abstract away how the system is architected, and that makes it difficult to understand.
It would also be nice to get insights into how to tune/configure licode. For example, can you run licode so that there are ErizoAgents spread across multiple servers?
In the mean time, thanks for the quick fix, I'll try it out and get back to you.


Generator doesn't work

Hi,
How are you?
Thanks for this great work. I have one question: I ran the pytorch code and the generator doesn't work.  It means: only model learned and saved, I used generator to generate the random noise and discriminator classify label. However, it always classify to one single or very few labels.  I tried so many ways: change noise to normal distribution, add some more layers , but it looks like generator doesn't learn ...
Can please give some guidance or workable code? thanks a lot!
Look forward to hearing from you soon!

Hi, Danilo,
Thank you so much for your response! It helps!
Linsey


Windows: protocol handler opens a new window and not existing window

Issue Type: Bug
With this release, invocations of vscode-insiders:// links always result in a new instance of VS Code opening, and vscode.window.registerUriHandler registrations in the new instance never getting called.
I also see an error of:
Warning: 'open-url --' is not in the list of known options, but still passed to Electron/Chromium.
when doing system invocations of vscode-insiders://
This breaks the extension I own as it uses the URI hanlder to notify the extension from cmdlet actions in the terminal.
VS Code version: Code - Insiders 1.65.0-insider (d09aeab62c1f93acf4a89b93e9a8a82419d6249a, 2022-02-09T05:16:17.063Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz (12 x 3696)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
31.78GB (8.42GB free)

Process Argv
--crash-reporter-id eca4b774-c277-477f-863a-1ad060bb6a90

Screen Reader
no

VM
0%

Extensions (16)

Extension
Author (truncated)
Version

vscode-research
alb
201021.0.1

npm-intellisense
chr
1.4.0

vscode-markdownlint
Dav
0.46.0

vscode-eslint
dba
2.2.2

vscode-npm-script
eg2
0.3.24

vscode-drawio
hed
1.6.4

tdpcode
Mic
1.10.9

remote-ssh
ms-
0.70.0

remote-ssh-edit
ms-
0.70.0

remote-wsl
ms-
0.64.2

vscode-remote-extensionpack
ms-
0.21.0

cpptools
ms-
1.8.4

js-debug-companion
ms-
1.0.15

powershell-preview
ms-
2022.2.0

debugger-for-chrome
msj
4.13.0

code-spell-checker
str
2.1.6

A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30422396
pythontb:30258533
pythonvspyt551:30291412
pythonptprofiler:30281269
vsdfh931:30280409
vshan820:30294714
pythondataviewer:30285072
vscod805:30301674
pythonvspyt200:30323110
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30404738
wslgetstarted:30421357
vs360cf:30404996
vsclayoutctrc:30405799
pythonvsnew555:30426298
vscscmwlcmt:30428973
azactmsalcf:30432849
vscgsvid2:30433758

Related to #142666

I can only reproduce since we use Electron 16, so I suspect it is related.
I am not so familiar with how we setup the protocol handler, code seems to be here:
https://github.com/microsoft/vscode/blob/4a130c40ed876644ed8af2943809d08221375408/src/vs/platform/url/electron-main/electronUrlListener.ts#L57
Maybe we no longer pass the arguments properly to the instance? Could this be related to the request single instance lock changes from @rzhao271 ?

request single instance lock exercises different code path than the protocol handler, so that change definitely shouldn't have an impact here.

Warning: 'open-url --' is not in the list of known options, but still passed to Electron/Chromium.

Considering this error, looks like the arg is incorrectly parsed. Not sure if its the runtime that is returning the bad argument, will check.

I would expect this place to be the location where we handle the URI:
https://github.com/microsoft/vscode/blob/01df559c184549248fcfbcecc5a616462e00c252/src/vs/code/electron-main/app.ts#L819-L833
I added some logging at that place.

Probably same as https://github.com/electron/electron/issues/32463 which was reported against Electron.

This issue affects GitHub and Microsoft authentication flows, unfortunately so new users will not be able to sign in at all until this is sorted. Just wanted to leave this context here as I will point others to this issue.

Is MS Authenticator affected? I think it's "self hosted" server, so no app schema handlers should be triggered.

True, @IllusionMH. Using the protocol handler is only done in Microsoft Auth if spinning up that server you mention doesn't work which should be relatively rare... so in auth world this mostly affects GitHub auth. Unfortunately, GitHub auth is used more than Microsoft auth.

Oh, nice to know. I stand corrected.

Will be fixed in today's insider
Refs https://domoreexp.visualstudio.com/Teamspace/_git/electron-build/pullrequest/479313

I verified that this isn't happening anymore, however, since it was related to the electron update and we've deferred that to March, I will move this out to March for true verification.


Regular Expression Denial of Service in markdown

I'm submitting a ...
[ ] language request
[ x ] bug report
[ ] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project

Summary
https://github.com/advisories/GHSA-wx77-rp39-c6vg

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)
Please switch from unmaintained markdown package to something else. I'm not feeling in a good position to propose any alternatives.

Would you like to give a PR ?


got a problem with Flow::default_fill() on your example..

Hi,
just tried the example on the front page of fltk-flow, but it doesn't compile because of this error :
   Compiling fltk_tst_flow v0.1.0 (C:\Data\Dev\rust_tst\fltk_tst_flow)
error[E0599]: no function or associated item named `default_fill` found for struct `Flow` in the current scope
  --> src\main.rs:10:26
   |
10 |     let mut flow = Flow::default_fill();
   |                          ^^^^^^^^^^^^ function or associated item not found in `Flow`
   |
   = help: items from traits can only be used if the trait is in scope
help: the following trait is implemented but not in scope; perhaps add a `use` for it:
   |
3  | use fltk::prelude::WidgetBase;
   |

For more information about this error, try `rustc --explain E0599`.
error: could not compile `fltk_tst_flow` due to previous error

what did I miss ?
thanks..

Hi
What's in your Cargo.toml?

here :
[package]
name = "fltk_tst_flow"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
fltk = { version = "^1.3", git = "https://github.com/fltk-rs/fltk-rs" }
fltk-flow = "0.1.4"

ok, if I specify an fltk version (like fltk = "1.3.13" stated on crates.io), I got an error telling me that flow need an older fltk version, (v1.2.30 the max usable). and effectively then it works..

That’s strange. I’ll publish a new release of fltk-flow which would use fltk-rs 1.3.

Hi,
it's ok now with fltk = "1.3.13" in cargo.toml, thanks !
and thank you for your great job on fltk-rs.  :+1:


[WIP] Some refactoring on converter

things needed

[ ] how to handle refresh
[ ] how to handle notebook header
[ ] how to handle os
[ ] how to get npm

@rchiodo not sure what it means by package.json needed to be updated.

Every update to the npm module requires that you increment the package.json (and package-lock.json) number by one. Otherwise npm won't publish.

@rchiodo I don't have permission to check in

That's weird. I'll see if you have write permissions.

Okay I think you have write access now.


feat(iframe) : Update next.config.js routing rules

:tada: This PR is included in version 1.31.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Question about LiDAR-IMU calibration tool

@Spring-lovely  @xiaokn
Hi, Thanks for your great work!
I have some questions about the lidar2imu tool.

How could I get lidar_pose_file to use this tool?
What tool did you use to get the lidar_pose_file in your experiment?
Does initial values of extrinsic parameters have a lot of effect on the result?

Thanks,

@Spring可爱的@xiaokn 嗨，谢谢你的出色工作！
我对该工具有一些疑问。lidar2imu

我怎么能使用这个工具？lidar_pose_file
您使用什么工具在实验中获取了 ？lidar_pose_file
外在参数的初始值对结果有很大影响吗？

谢谢

Hello, I have the same problem with you. The initial external parameters seem to be closely related to the calibration results. The initial value of external participation after calibration is not much different. I try to change the external parameters slightly, and the calibration will not be able to proceed. How do you solve this problem.

@Spring-lovely @xiaokn Hi, Thanks for your great work!
I have some questions about the lidar2imu tool.

How could I get lidar_pose_file to use this tool?
What tool did you use to get the lidar_pose_file in your experiment?
Does initial values of extrinsic parameters have a lot of effect on the result?

Thanks,

lidar_pose_file is the pose output by the inertial navigation device after transformation with lidar-imu extrinsic parameters.
The initial extrinsic parameters have little effect on it, and the calibration environment may impact the results.

@xiaokn
Thanks for your reply.
Could you recommend some tools that make lidar_pose_file?
Thanks,


Support for PHP7 and PHPUnit 5.0?

Now that PHP7 has been tagged and PHPUnit 5.0 is stable, are there any plans to make vfsStream compatible to those?

PHP7 compatibility should come in December, even though I don't think the current version is not compatible, at least the tests didn't show a significant problem except for the output of a warning which is raised when simulating insufficient disk space, but that shouldn't effect most users.
Regarding PHPUnit 5.0 I don't see that there needs to be done anything about this. vfsStream has no runtime dependency to PHPUnit, and the dev dependency doesn't matter to users. If I'm not missing something here that shouldn't be a problem.

Well, didn't dig into it yet, but at least those "uninitialized strong offset" notices in https://travis-ci.org/kdambekalns/flow-development-collection/jobs/94757895 seem to be related to PHP7. Probably the "uniform variable access" changes, as far as we guess.

After digging into it I think it is not related to PHP 7, I was able to reproduce this with PHP 5.6.4. The problem is that the call to vfsStream::setup() passes a directory name with trailing slash, causing the vfsStream::newDirectory() method to create a directory instance with an empty name. I fixed this with 0ea19cb, a trailing slash will no longer cause the creation of such a directory instance.

I assumed it was related to PHP 7, since it didn't cause problems so far, but the code looks "broken" regardless of the PHP version. :-)
Anyway, thanks! Any chance to get a 1.6.1 tagged today?

Done, just released 1.6.1. I'll leave this issue open until PHP 7 compatibility is fully verified.

Thanks! For us it works so far…

There is stil a problem with a bug in PHP 7 itself: https://bugs.php.net/bug.php?id=71287

The bug is fixed in PHP 7.0.3.


onNoPermissionNeeded

You should provide a parameter in onNoPermissionNeeded method to distinguish multiple permissions callback;

in no Permission Needed is used for pre-M.


Xamarin.Forms GTK# platform setup is throwing an error

VS2019 Community 16.6.2, Xamarin.Forms & Xamarin.Forms.Platform.GTK <IP_ADDRESS>8 & GTK# 2.12 on Windows 10 x64 2004
Following the platform setup is leading to an error at build:
line 15 var app = new App();
namespace not found for App().
If i replace App() by Xamarin.Forms.Application(), it starts but throws a System.NullReferenceException at:
lien 21 Gtk.Application.Run();
Thank you !
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 66853f3d-854e-08ad-84d2-b2a98f88c48b
Version Independent ID: 77ea362d-ef46-f426-3d4a-5f99e39ce160
Content: GTK# Platform Setup - Xamarin
Content Source: docs/xamarin-forms/platform/other/gtk.md
Product: xamarin
Technology: xamarin-forms
GitHub Login: @davidbritch
Microsoft Alias: dabritch

I was not exactly referencing the GameOfLife class library. Sorry !


[ccapi] basic c++ API

Added initial draft for c++ API
This includes major headers with pure virtual classes
Updated internal classes to inherit them
Updated files names for clashing internal files
Updated MNIST example to use cpp api
Updated capi to use the factory methods
Updated internal enum classes with cc api exposed enum classes
Self evaluation:

Build test: [x]Passed [ ]Failed [ ]Skipped
Run test: [x]Passed [ ]Failed [ ]Skipped

Signed-off-by: Parichay Kapoor<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #622. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

:octocat: cibot: @kparichay, **** does not include doxygen tags such as @file @brief. You must include the doxygen tags in the source code at least.

:octocat: cibot: @kparichay, You wrote code with incorrect doxygen statements. Please check a doxygen rule at http://github.com/nnsuite/TAOS-CI/blob/master/ci/doc/doxygen-documentation.md

INFO: You can read if there are misspelled characters at our misspelling check report. Please read http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/622-202010061324520.27508902549744-dc27eccfc9a28fd63b843ce83857844a830789db/report/misspelling_result.txt.

:octocat: cibot: @kparichay, One of the module of prebuild group is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnstreamer/nntrainer/wiki/.

:octocat: cibot: @kparichay, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/622-202010061324520.27508902549744-dc27eccfc9a28fd63b843ce83857844a830789db/.

INFO: You can read if there are misspelled characters at our misspelling check report. Please read http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/622-202010082044210.33281803131104-d0e2840e10b3c1cc56acb6db8abe5e9c76202b8d/report/misspelling_result.txt.

:octocat: cibot: @kparichay, One of the module of prebuild group is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnstreamer/nntrainer/wiki/.

INFO: You can read if there are misspelled characters at our misspelling check report. Please read http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/622-202010082045010.30963897705078-72eff57f248ca36e9ab506e4ce94c5d4f9dd61d6/report/misspelling_result.txt.

INFO: You can read if there are misspelled characters at our misspelling check report. Please read http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/622-202010082053300.69383597373962-d5aad7b6616aa64755a2a658223e8fedb4fe56cb/report/misspelling_result.txt.

:octocat: cibot: @kparichay, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/622-202010082053300.69383597373962-d5aad7b6616aa64755a2a658223e8fedb4fe56cb/.

:octocat: cibot: @kparichay, One of the module of prebuild group is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnstreamer/nntrainer/wiki/.

:octocat: cibot: @kparichay, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/622-202010121421280.84495091438293-0bbcc44161efce0a3db45eaa793e90c718d75843/.

:octocat: cibot: @kparichay, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/622-202010121523090.89521789550781-f532aa4a4b1f2492b645b8ebeca6285112ce1753/.

:octocat: cibot: @kparichay, One of the module of prebuild group is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnstreamer/nntrainer/wiki/.

:octocat: cibot: @kparichay, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/622-202010141540520.99245500564575-80da23f376d94ae6c8fac0ce8060a8a448e8c348/.

:octocat: cibot: @kparichay, One of the module of prebuild group is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnstreamer/nntrainer/wiki/.

:octocat: cibot: @kparichay, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/622-202010191600380.053261995315552-8c3b27acdb51f5bfa4c9f7c43a0219d3db8b839b/.

:octocat: cibot: @kparichay, One of the module of prebuild group is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnstreamer/nntrainer/wiki/.

:octocat: cibot: @kparichay, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/622-202010191613230.50190591812134-a019d2d70844c256768dc510e7cf6f87ab9243bc/.

:octocat: cibot: @kparichay, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/622-202010191632250.47024011611938-72ef53979423049bd5d48a6d958efeb3244250b3/.

:octocat: cibot: @kparichay, One of the module of prebuild group is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnstreamer/nntrainer/wiki/.

:octocat: cibot: @kparichay, One of the module of prebuild group is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnstreamer/nntrainer/wiki/.

:octocat: cibot: @kparichay, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/622-202010191758520.50859904289246-6a964417aaecb3490c95e4cb94522558f588fa3b/.

:octocat: cibot: @kparichay, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/622-202010191905380.964684009552-f9218e9b7f4061d1a5c34bbfcb7da3851c9f6458/.

Rebased.


Remove jQuery

Hi Daniel, thank you for the excellent work with this add-on.
Now that jQuery is officially optional since Ember 3.3, I think that this add-on should not use jQuery anymore.
Doing a quick search within the repo I have only found a few instances in which jquery is imported and used:

addon/payload/json-api-payload.js
addon/mocks/mock-request.js
addon/utils/helper-functions.js
tests/unit/utils/helper-functions-test.js
tests/unit/shared-adapter-behaviour.js

However, I don't know if there are other underlying uses. In any case, do you think that it would be possible to get rid of jQuery?

There are only a few uses ( like $.params , $.extend ) which are no brainers
but others in testing  like:
$(document).ajaxComplete    with are relying on jquery  $.ajax   calls ( ie jquery )   which are harder to replace
but I think if we replace those in the files you mentioned ( production ) files, we can keep jquery for a devDependency  ONLY
feel like doing a PR for this ?

I dug in a little bit to remove jQuery from the addon directory. If my PR for RFC 176 is accepted the only function of jQuery outside of testing would be $.param, used here:

addon/utils/helper-functions.js
addon/mocks/mock-request.js

I tried to follow the approach of the ember-fetch adapter for ember-data, in which $.param is partially reimplemented (see the function serializeQueryParams). I practically copied and pasted this function (and the respective add companion function and RBRACKET const) into ember-data-factory-guy/addon/utils/helper-functions.js and used it instead of $.param.
I had a some success, but alas this approach is not enough for ember-data-factory-guy as some tests still fail, such as those with body or URL params.
My guess is that it would be necessary to fully re-adapt the $.param function as a util helper to support these other use cases.
Unfortunately I do not have enough time to dig deeper, but I hope that this info will be a good start in case someone else would like to tackle this task.

Thanks @amauryt , I will do that replacement ( I found some helper functions already ).  I really appreciate you taking the time to work on this.

as of v3.6 there is no more jquery used in factory guy code addon code. there is still some left in the tests, but as of 3.6 you can use factory guy and you should not need jquery at all.
as of v3.7 i am removing jquery entirely .. but as i said 3.6 is enough


[lapack-reference] lapack header file is missing

Describe the bug
some header file is missing in lapack-reference
Environment

Windows11
MSVC 2022

To Reproduce
Steps to reproduce the behavior:

./vcpkg install lapack-reference[core]:x64-windows-static

Expected behavior
I want lapack header file just like:
lapack.h
lapacke.h
lapacke_config.h
...

LAPACKE is not part of lapack-reference. lapack-reference only builds LAPACK. LAPACKE would require another port.

Another port? I install lapack and lapack-reference, but I can't find lapack header file too.

lapack header file

there are no lapack headers since lapack is a Fortran library. LAPACKE has headers since it is a C lib but that one does not have a port in vcpkg yet.

I include lapack.h and link to lapack-reference[core]:x64-windows-static, I can call lapack function (dgels_) normally. But if I include lapacke.h and use LAPACKE_dgels function, I will get an error "unresolved external symbol LAPACKE_dgels".
So lapack-reference only support xxxxx_() and don't support LAPACK_xxxxx() and LAPACKE_xxxxx()?

So lapack-reference only support xxxxx_() and don't support LAPACK_xxxxx() and LAPACKE_xxxxx()?

as I said. lapack-reference only contains the Fortran lapack library. The C wrapper is not part of it. If you want that a new port should be created for lapacke. The reason for that is that lapacke can use different lapack implementations as its backend and is thus not build together with lapack

When I install openblas as backend, I can't find lapacke too.

there are no lapack headers since lapack is a Fortran library.

lapacke is a new port.

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now.


Add block_number & transaction_count index for Block

Codecov Report

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

@@           Coverage Diff            @@
##           develop      #95   +/-   ##
========================================
  Coverage    97.36%   97.36%
========================================
  Files           55       55
  Lines         1403     1403
========================================
  Hits          1366     1366
  Misses          37       37

Continue to review full report at Codecov.

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

How do we know this would actually make the query(queries) performant? Which query will use this index?

BlocksController#index，but through logs, this query not actually cause problem, it about 11~12ms in query


Deck sync does not recognise regex route collissions

Environment
Kong Hybrid EE <IP_ADDRESS>

$ deck version
decK v1.11.0 (4235c73)
$ inso --version
2.4.1

Issue
If we create a route /example/{id} then in a separate workspace we create /example/{id_2} deck / Kong does not recognise this collision.
If we do not use parameters or use the same parameters naming we get this output, which is great.
while processing event: {Create} route demo_one-example_id-get failed: HTTP status 409 (message: "API route collides with an existing API")

Behaviour
So if we use the following curl command it will always route to /example/{id} i.e. the first one created.
curl -k https://${KONG_PROXY_URL}/example/1234

Example configuration
I assume this is happening because the collision matching is based off the .services.routes.paths which appears different because of the parameter naming, yet it is actually the same route.
Here is the sample of the kong declarative configuration we are applying
# id
services:
  - retries: 5
    name: demo_one
    protocol: https
    host: demo_one.upstream
    port: 443
    path: /
    plugins: []
    routes:
      - request_buffering: true
        response_buffering: true
        path_handling: v0
        https_redirect_status_code: 426
        tags:
          - OAS3_import
          - OAS3file_demo-one.yaml
        name: demo_one-example_id-get
        methods:
          - GET
        paths:
          - /example/(?<id>[^\/]+)$

# id_2
services:
  - retries: 5
    name: demo_one
    protocol: https
    host: demo_one.upstream
    port: 443
    path: /
    plugins: []
    routes:
      - request_buffering: true
        response_buffering: true
        path_handling: v0
        https_redirect_status_code: 426
        tags:
          - OAS3_import
          - OAS3file_demo-one.yaml
        name: demo_one-example_id_2-get
        methods:
          - GET
        paths:
          - /example/(?<id_2>[^\/]+)$
        strip_path: false

Since this is around Kong Enterprise, please open an Enterprise support request: https://support.konghq.com

What is the solution for this problem.??


added italian readme

Pull Request Status

[x] WIP

Description
Short summary of the changes and goals of this pull request.
Todo's

[X] Todo 1
[ ] Todo 2

Awesome work 👍


Test mail from admin interface rejected

Describe the bug
A mail that has been sent from the admin mail interface has been rejected by my Exim based MTA with the following error message:
2024-03-06 12:30:57 *redacted connection information*<EMAIL_ADDRESS>rejected after DATA: header syntax ("@" or "." expected after "undisclosed-recipients": failing address in "To:" header is: Dev Day Teilnehmer <undisclosed-recipients:;>): "@" or "." expected after "undisclosed-recipients": failing address in "To:" header is: Dev Day Teilnehmer <undisclosed-recipients:;>
To Reproduce

Login as admin
send a mail to a recipient that uses an Exim based MTA for his MX

Expected behavior

Mail is accepted

see https://lists.exim.org/lurker/message/20130508.103815.62972d63.ca.html


[3599] organisation context switching component

Context
https://trello.com/c/ZXKXSEAg/3599-m-organisation-context-switching-component
Changes proposed in this pull request

Updated NavigationBar component to allow right aligned menu item
Added change organisation link on application layout.

Guidance to review

Login with user which has multiple providers
I have added Bridget Campbell to two providers

Important business

Does this PR introduce any PII fields that need to be overwritten or deleted in db/scripts/sanitise.sql?
Does this PR change the database schema? If so, have you updated the config/analytics.yml file and considered whether you need to send 'import_entity' events?

 [M] Organisation context switching component

This one is borked, i created new PR with the changes:
https://github.com/DFE-Digital/register-trainee-teachers/pull/2013


Split base image into two parts

Since most of the time we're just changing the scripts and no the entire
base image, it's a shame to have to rebuild it.
Instead, split the base image into a shipyard-dapper-base-deps image
which contains the OS and all the downloaded & installed tools.
Each image would be rebuilt only when necessary.

Thanks to a suggestion from @mangelajo closing this in favor of #84


fix(dynamic-forms): material input name overriding (#1895)

Fixes #1895

I have time today. will just make the changes in another PR.

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

v4.1.6
GitHub release

Your semantic-release bot :package::rocket:


True / False isn't showing up in the UI

Description
True / False isn't showing up in the UI.  I'ved check the logs and its suppose dot be True

Python, Logfire & OS Versions, related packages (not required)
No response

Thanks for the report. Simple repro:
import logfire
logfire.configure()
logfire.info('hi', x=True, y=False)

This is fixed, thanks @dmontagu!


Patch: Change access specifier of createMatrix method

Made the method createMatrix accessible to subclasses

All fine of course. But what about changing the name of "createObservables" (e.g. into "createNumberOperatorsMatrices")?

Thanks!
I will add that with the next iteration when merging the ctest feature
branch.
I just wanted to keep changes as minimal as possible for a bugfix.
On Mon, 19 Sept 2022 at 12:01, sebastian-zell @.***>
wrote:

All fine of course. But what about changing the name of
"createObservables" (e.g. into "createNumberOperatorsMatrices")?
—
Reply to this email directly, view it on GitHub
https://github.com/marco-michel/TimeEvolver/pull/6#issuecomment-1250751403,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWSDKP4OV26CQAJW2WAHNBTV7ATWVANCNFSM6AAAAAAQPP3SAQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


ug: Add documentation for aktualizr-lite command line interface

A first draft for the CLI documentation, so I can share the preliminary data with the CS team.

PR Template and Checklist
Please complete as much as possible to speed up the reviewing process.
Readiness and adding reviewers as appropriate is required.
All PRs should be reviewed by a technical writer/documentation team and a peer.
If effecting customers—which is a majority of content changes—a member of Customer Success must also review.
Readiness

[ ] Merge (pending reviews)
[ ] Merge after date or event
[ ] Draft

Overview
Why merge this PR? What does it solve?
Checklist

[ ] Run spelling and grammar check, preferably with linter.
[ ] Avoid changing any header associated with a link/reference.
[ ] Step through instructions (or ask someone to do so).
[ ] Review for wordiness
[ ] Match tone and style of page/section.
[ ] Run make linkcheck.
[ ] View HTML in a browser to check rendering.
[ ] Use semantic newlines.
[ ] follow best practices for commits.

[ ] Descriptive title written in the imperative.
[ ] Include brief overview of QA steps taken.
[ ] Mention any related issues numbers.
[ ] End message with sign off/DCO line (-s, --signoff).
[ ] Sign commit with your gpg key (-S, --gpg-sign).
[ ] Squash commits if needed.

[ ] Request PR review by a technical writer and at least one peer.

Comments
Any thing else that a maintainer/reviewer should know.
This could include potential issues, rational for approach, etc.

I'm missing a note about stopping aklite daemon before running CLI.
We could cover:

manual updates (stop aklite and stop fioconfig)
skip daemon start from lmp-device-register
skip daemon from the build (we have an example for custom-sota, what would be the alternative for CLI?)

I haven't reviewed return codes and sample script yet.

Docs for 4564d81bbd36101ef653fd0fe339153bff190d83 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2717/docs/artifacts/html/index.html

Docs for 5e568db8bb424cebb1d1ce6084a4bf23e83025d1 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2742/docs/artifacts/html/index.html

Docs for 15489180d213f5cd85017a9b9fc156605f26699a are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2743/docs/artifacts/html/index.html

Docs for 9eebdc64277c4bc58fce8eac4700081894bfc394 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2751/docs/artifacts/html/index.html

I'm missing a note about stopping aklite daemon before running CLI. We could cover:

manual updates (stop aklite and stop fioconfig)
Added note.

skip daemon start from lmp-device-register
Added note.

skip daemon from the build (we have an example for custom-sota, what would be the alternative for CLI?)
We do need the daemon binary, so the build itself is not changed someone is going to use CLI. Perhaps adding something about not enabling the aklite service by default in the build? Not sure hot that can be done, will have to check it.

Docs for 968cbeef7cbe4976706db1a0f6869a173a489a44 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2752/docs/artifacts/html/index.html

Docs for f227e917db8d0b406d3e6c2e657a04a4501d9788 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2753/docs/artifacts/html/index.html

Docs for c9b613078f1d8efd6375abf6db3e1dab203f25de are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2758/docs/artifacts/html/index.html

@kprosise can you take a look? Feel free to do text adjustments and merge if no changes are required from our side. Thanks!

@detsch, if you could add the suggestions, if they seem appropriate, then squash the commits, I will then go ahead and merge. Thank you!

Thanks @kprosise! Applied all your suggestions, and rebased to the latest main . Feel free to merge when appropriate.

Docs for 9d9037ddd92af8a25048bfab8a839080a23ad29d are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2764/docs/artifacts/html/index.html


Allow LakeFS files to decay standard Blockstore files on request [ENG-92]

Closes https://github.com/appliedAI-Initiative/lakefs-spec/issues/81
Notable points

We disable bandit here. remote_url comes from a trusted source (our backend). Additionally, added a test for wrong protocols above.
We should still test this with Azure and AWS backends.
I did not extract the token from the staging_location. This proved unnecessary for the handling S3. We should test that that holds with other backends.
I was having trouble to identify valuable things to test as most of the code is LakeFS Client code. So if you think the tests are insufficient, just ping me on what else to add.
-- E.g. did not test upload with physical address because its three lines depending solely on lakeFS client APIs (see here).

Question to reviewer

Test support pre- and post breaking change of the get_config lakeFS API. Unsure what the best practice here is. See here

Other Changes

Removed ports from lakefs-s3-local. They have no effect when using network_mode: host
Removed restart: always from network_mode: host to enable shutdown with docker-compose down.

Todos

[x] Add tests
[ ] Test with Azure
[ ] Test with AWS

Codecov Report
Attention: 32 lines in your changes are missing coverage. Please review.

Comparison is base (bd20738) 92.55% compared to head (8538a3f) 85.90%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #95      +/-   ##
==========================================
- Coverage   92.55%   85.90%   -6.65%
==========================================
  Files           7        7
  Lines         403      440      +37
  Branches       67       75       +8
==========================================
+ Hits          373      378       +5
- Misses         14       45      +31
- Partials       16       17       +1

Files
Coverage Δ

src/lakefs_spec/spec.py
82.41% <23.80%> (-9.45%)
:arrow_down:

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

Regarding your comment on the token in the staging location: from reading the SDK docs I believe this is not meant for authentication but rather used to link the staging location later on:

token | str | opaque staging token to use to link uploaded object


Crash when using .context() where the contexObject thread is different

If the contextObject is in a different thread than the current execution thread, asyncfuture can cause a crash. This is because QFutureWatcher lives in the current execution thread() but communicating to the contextObject's thread(). In this case, it's possible for the QFutureWatcher to emit bath canceled() and finished() and since both the signals in a queued eventloop, they are handled. By the time they're handled, QFutureWatcher has been destroyed, causing a crash in the other single handler. This isn't a problem if QFutureWatcher and contextObject live in the same thread because QFutureWatcher gets disconnected, when it's destroyed.

Testcases and fix to this issue can be found here: https://github.com/vpicaver/asyncfuture/commit/6ec3c36a08eeb1e37c44454f03cd3fb3f9efba1f
Pull request seem a bit broken, but this commit should be atomic.


Make ToDer trait potentially more convenient by keeping state from to_der_len for write_der_content

This is just a abstract idea I had because I'm currently writing a serializer using this crate:
The pattern I hit right now is that to be able to calculate the final encoded length for write_der_header I have to wrap all tagged fields and resolve things like their lengths, recursively.
But I have to throw away that state directly afterwards, only to reconstruct it again in the directly following call to write_der_content.
It's not a big overhead by any means, but I was wondering if I could remove it regardless.
Is that something that'd you be interested in as well and/or would want to work on together?
An idea I had is to make ToDer have an associated type that stores what is in essence a weak normalized form. The basic idea is that the WNF can be encoded into bytes directly without conditionals and without having to allocate/wrap any fields.
That solution would however make ToDer not object-safe until GATs for trait objects land. Not sure if that is a significant usability problem though.
(Fun fact: The last time I had this issue in asnom I actually inverted encoding, writing out the bodies of fields first and the headers afterwards, making heavy use of scatter/gather-IO. But that approach was absurdly complex, hard to use, and not all that efficient in most cases anyway.)

Hi,
You are raising several good points here, on things that took me some time (and headaches) before getting to the current code. And I will humbly admit some better solution could exist :)
I'll reply here, but maybe it will be better to split the discussion on several issues.
About ToDer and length computation
I hesitated a long time between

a streaming implementation, which would not need to allocate but would require computing the length recursively before writing the object (and thus, walking the DER tree twice).
an allocating version. The code is much easier, though in some cases you have to allocate twice: once to serialize contents, and then you can compute length [1], and then you need to allocate again to write the header and the object
finally I settled on using a Write trait so there is only one allocation

[1] Note that the fact that DER length is itself a variable-length fields does not make it easier to compute, and prevents leaving some placeholder bytes that could be updating after the computation.
I am not sure I get your idea of the weak normalized form, yet I'm really interested so if there is a way to write a minimal example or just some pseudo code it would be like, I'd gladly have a look. We can also discuss it on IRC/discord if you prefer.
Associated types and GAT on traits
I find it funny you are raising that, because it is something I also struggled on for other parts of this crate. In particular, I tried changing the Error parameter of the FromBer trait into an associated type (which would be better imho, since usually there is only one error type for a parse function), but quickly jumped into very complex errors. Roughly, they are related to the following:

I need to defined bounds on the associated types
FromBer is automatically implemented for any type providing TryFrom<Any>, but also needs to be implemented for Any. If the error type becomes too generic, then the compiler refuses because there is a default implementation of TryFrom<T> for T.
I had other errors, and could never finally have something satisfying.

On that issue, I'd gladly take some advice/hints!
Note: for the ToDer trait, maybe the situation is different because the error is not generic. But it would be good to have a similar solution in the different traits used in that crate


.env file needed

Can we distribute one outside of git? Or limit its visibility to contributors?

Issue #13 worked around this


Portrait mode with split screen as Aspen Avionics E5

Doug is right (#20): the further development should prefer portrait mode in my opinion.
In portrait mode it would be possible to split the screen similar to Aspen Avionics E5:
in the upper section the display with the 2019 Release elements without heading,
in the lower section compass arc selectable from GPS or magnetic sensor (additional in Stratux necessary or are iPhone`s sensors suitable?) and heading bug input referring to this with values in true or magnetic north.
Perhaps it is possible to get values of lateral course deviation from Foreflight or a simple app running in Raspberry. In this way it could be possible to display a HSI screen ...
I´m very curious about the further development. Many thanks for the until now done.
Kind regards
Franz

Very interesting ideas! Such changes would certainly expand the usability of this software, making it more like a full backup piece of avionics. Below I'll re-list the proposed enhancements and mention my thoughts / basic feasibility research:
Proposed Enhancements (+1 new one)
Aspen E5 Style Portrait Split
Description
While in portrait mode on displays of sufficient size, the display could split, leaving much of the current AHRS on the top half, and adding new features such as a compass or HSI on the bottom half, similar to the Aspen E5. This change would greatly increase the effectiveness of the display space in portrait mode.
Feasibility: ✅
Allocating the space for more user interface elements based on screen configuration should be very doable. Moving the current GPS track compass to this new area should also be very doable.
Use of a Magnetic Compass Source
Description
Magnetic compass heading would provide a new type of navigational information. It would be especially useful due to the fast reaction time, as compared to the gps heading source.
Feasibility: ❓
Access to compass information is a bit limited. Some issues / research points:

Many phones implement access to sensor data differently, making it hard to effectively support a lot of devices.
The phone's compass direction will be heavily dependant on the user's device- if the pilot has the phone or tablet mounted to the yoke, for example, flight control inputs could actually change the compass value.
In iOS (haven't done research for Android), access to the sensor data (compass included) is only possible with permission from the user and if the web page is served via https. User permission is easy, however using https would be a challenge because the cert would be self-signed (prompting a warning on user devices) and stratux serves web pages over http. Moving to encryption may not be possible without extensive modification of stratux, a change that I find unlikely to gain traction.
Luckly, the sensor used on stratux is the MPU9250, which has a compass. In addition, the stratux situation websocket already contains fields for compass information. However, the current version of stratux does not populate these values because there is currently no way to calibrate the compass information.

Based on these items, it seems like the best chance to use compass data effectively is to either wait for compass support from stratux or make the proposed changes to stratux directly. However, much of the proposed modifications (E5 split, etc.) could be made without compass data available (this could be a longer-term enhancement).
Full HSI Support
Description
With room for a circular compass, an HSI could also be added to aid in navigational and situational awareness.
Feasibility: ❓
Currently there is no way to access course deviation information from Foreflight, though there may be support from other Electronic Flight Bags. This will require more research.
Basic Compass Radar Scope (NEXRAD) / Traffic
Description
Similar to the Aspen E5 middle display in this photo, it would be neat to be able to display simple weather information or traffic information inside the circular compass rose (especially if the HSI is inactive or not implemented). This change would allow stratux_ahrs to be used to display most all of the information stratux provides.
Feasibility: ✅
Save for unknown performance issues, this feature should be possible. stratux sends out NEXRAD weather information and traffic details in the blind, so pulling it would be trivial. Effectively and efficiently displaying it would be harder, but with optimization could be possible.
What's Next?
It seems like more research should be done to determine the benefits to this change. This thread might be a good location to document some additional features that could use this mod.
Performance of the device with the additional computational load of new UI elements, additional processing, and possibly image creation for weather could be a limiting factor.
Certainly this would be a big change to stratux_ahrs. Before actual modifications are made (after analyzing the feasibility and usability of this enhancement), there are some housekeeping items that the core application needs done, particularly related to performance, weight, code consistency, and ease of contribution. However, I certainly like the proposed items and the possibilities they bring.
At some point, I may make a github project for this to help track how things are going, and I'll see about planning a basic timeline (based on future releases, etc.). Thanks for the great suggestion; we'll see where it goes soon enough!


Enable dark mode on docs.sui.io

What are the existing URLs containing the issue, if any?
docs.sui.io/*
How would you describe the issue? (What needs changing?)
Our light background is difficult for some users. This is particularly hard for me in mobile.
We are requesting a dark mode. Looks available here:
https://color-mode.nuxtjs.org/
https://nuxtjs.org/tutorials/going-dark-with-nuxtjs-color-mode/
Where should this information land if new? (Learn, Build, Explore, Contribute.)
This should be available on every page and be sticky.
What changes are needed to support this new feature or product? (A simple overview, detailed procedures?)
Implement the feature above.
Who is the audience for that information? (App developers, investors, creators, validators, someone else?)
Folks who struggle with the light mode.
What precisely must they do with it? (Configure a new service? Process some output?)
Toggle from one mode to another easily.

Thanks for your suggestion. Since this issue was made, the dark mode was added to docs.sui.io.


Is there have any way to report TPS for commitOnly/endorsementOnly  option?

Is your proposal related to a problem?
Hi Guys, I am try using commitOnly/endorsementOnly  option.
But there have no TPS report from the result, just report "empty endorsement policy".
Is there any more setup need for this options? Or there have no this feature for report TPS?
Describe the solution you'd like
Could report the TPS from the result report.
Thank you very much~

ref to CI log:
https://dev.azure.com/Hyperledger/TWGC/_build/results?buildId=48128&view=logs&j=7cc4919e-7604-5b3d-4046-113f7a4a0843&t=41d9e55c-8c73-5183-9a6f-249cb9eb6101&l=3071
https://dev.azure.com/Hyperledger/TWGC/_build/results?buildId=48128&view=logs&j=42e0d588-4a05-5e49-cd2d-d02bafda4323&t=f5c4f82f-c626-5d7d-8eab-3a1459ea1449&l=8957
There is TPS in result report.
BTW,

I am really recommend you to take a look at https://github.com/Hyperledger-TWGC/fabric-performance-wiki/blob/master/performance-whitepaper.md

To reproduce your issue, could you please share with your start script?

For commitOnly/endorsementOnly mode... some how it is wired to calculate with TPS.
as endorsementOnly is only for query, but not block generation.
and for commitOnly, it used for test with consensus but not for a full traffic test.

Thank you very much~
I found branches  alpha support  commitOnly/endorsementOnly, so I build a tape and runs at test-network.
The module name is tape-r
The following is the output.
root@svl1:~/gubl/fabric-samples/test-network# ./tape-r commitOnly  -c config2.yaml -n 4
empty endorsement policyroot@svl1:~/gubl/fabric-samples/test-network# ./tape-r endorsementOnly -c config2.yaml -n 4
empty endorsement policyroot@svl1:~/gubl/fabric-samples/test-network#
I also try used normal tape, it works well.
root@svl1:~/gubl/fabric-samples/test-network# ./tape -c config2.yaml -n 4
Time     2.08s  Block   3077    Tx      4
tx: 4, duration: 2.082673559s, tps: 1.920608
And for fabric-network, I used fabric 2.4.1 and latest fabric-network
for create channel:
./network.sh createChannel
for deploy chaincode:
./network.sh deployCC -ccn basic -ccp ../asset-transfer-basic/chaincode-go -ccl go

you may need to apply with endorsement policy as https://github.com/Hyperledger-TWGC/tape/issues/238#issuecomment-1046908882


fix: Add debug messages for exclusions during bump lifecycle

Code has been modified to include debug messages in the bump lifecycle. When a filename is ignored by Git or is not a file, the program will now log a debug-level message.

I had a wrong gitignore file. These debug outputs would have helped me to identify the cause more quickly

I like to contribute something if I can.
Thanks for the feedback, I've adjusted the code accordingly.


feat(ProgressBar): [TEA-2569] Introduce ProgressBar component

TEA-2569
BASE design
Description
Introduce ProgressBar component to @toptal/picasso-lab package.
How to test

Run storybook locally or visit temploy
Under Picasso Lab, find ProgressBar component
Check if component covers all requirements from ticket description
Check if component is implemented according BASE design

Screenshots

Review

[x] Read CONTRIBUTING.md and Component API principles
[x] Annotate all props in component with documentation
[x] Create examples for component
[x] Ensure that deployed demo has expected results and good examples
[x] Ensure that tests pass by running yarn test
[x] Ensure that visuals tests pass by running yarn test:visual. If not - check the documentation how to fix visual tests
[x] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.

PR commands

List of available commands:

@toptal-bot run all - Run whole pipeline
@toptal-bot run build - Check build
@toptal-bot run visual - Run visual tests
@toptal-bot run deploy:documentation - Deploy documentation
@toptal-bot run package:alpha-release - Release alpha version

@toptal-bot run all

@toptal-bot run all

Thanks @besirovic My only concern is about font size for tooltips - it's 14px vs 12px in design, also @vedrani found a glitch with move from 90% to 100%. I didn't check code though 🙂


[BUG] Keyboard doesn't appear automatically on Android

Have you read the code of conduct?

[X] I have read the code of conduct.

Has this bug already been reported?

[X] This bug has not been reported yet.

Environment
OS: GrapheneOS 13
Browser: Vanadium
Suggested fix
No response
Anything else?
No response

Doesn't seem to be possible.


Address review comments for deprecated warning on NSObject.hashValue override

Address the review comments from @jrose-apple and @lorentey on https://github.com/apple/swift/pull/18407, cleaning up my newly-introduced warning for overriding NSObject.hashValue

@swift-ci please smoke test

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge


Introduce positionFixed optimization

Fixes #152
I'm not sure if I should adjust the documentation accordingly, so any suggestions are welcome. Thanks!

@zackbloom Any update on this?

@zackbloom @TrevorBurnham I've updated this branch, is there anything else I can do in order to get it merged?


VideoPlayerRenderer.CanPlay causes Object reference error

Given this method:
        public void ResumePlayback()
        {
            if (VideoPlayerControl.State == PlayerState.Prepared || VideoPlayerControl.State == PlayerState.Paused)
            {
                    VideoPlayerControl.Play();
            }
        }

I occasionally get this error on iOS only:
Object reference not set to an instance of an object
VideoPlayerRenderer.CanPlay ()
VideoPlayerRenderer.Play ()
<.ctor>b__77_1 ()
<.ctor>b__0 (System.Object o)
Command.Execute (System.Object parameter)
VideoPlayer.Play ()
EpisodeViewModel.ResumePlayback ()
EpisodeViewModel+<VideoPlayerControl_PlayerStateChanged>d__83.MoveNext ()
ExceptionDispatchInfo.Throw ()
AsyncMethodBuilderCore+<>c.<ThrowAsync>b__6_0 (System.Object state)
UIKitSynchronizationContext+<Post>c__AnonStorey0.<>m__0 ()
NSAsyncActionDispatcher.Apply ()
(wrapper managed-to-native) UIKit.UIApplication:UIApplicationMain (int,string[],intptr,intptr)
UIApplication.Main (System.String[] args, System.IntPtr principal, System.IntPtr delegate)
UIApplication.Main (System.String[] args, System.String principalClassName, System.String delegateClassName)
Application.Main (System.String[] args)

Any idea of the best way to prevent this error?

If your goal is just to play it as soon as the video has been loaded you could always just set AutoPlay="True" on the player and it will take care of playing the stream once the video has been prepared otherwise if you want more control, you can hook into the PlayerStateChanged event and do it yourself:
myPlayer.PlayerStateChanged +=> (sender, args) =>
{
   if(args.CurrentState == PlayerState.Prepared) {
      myPlayer.Play();
   }
}


Unittests

Fixed unit tests, added badge.

Changes Unknown when pulling 2152c41238868f328c85569270cde194db7bcad5 on unittests into ** on dev**.


Points/Vectors as VALJOs

Making all point and vector concrete classes meet the requirements for VALJOs. Also, addressing the comment from GEOMETRY-2 about the placement of the Serializable interface in the overall API (it should go on concrete classes and not top-level interfaces).

I'm closing this pull request and making a new one that combines changes from GEOMETRY-3 and GEOMETRY-4 so that we can have a clean CheckStyle report (GEOMETRY-4 includes misc cleanup like javadocs, etc).


Add support for param values of type array and objects

Description of problem
In the workload object, the params value can take any shape. The value can be a an array or object that the plugin should be able to parse into yaml.
Proposed solution
Given a workload create/update/apply command
When param value is a complex type like array or objects
Then apps plugin should be able to parse it and convert it into valid yaml

Example
Object support
Example Command:
tanzu apps workload create direct-smtp-mq-gateway --type tcp --app direct-project --git-repo https://github.com/gm2552/direct-smtp-mq-gateway.git --git-branch master --service-ref rmq=services.apps.tanzu.vmware.com/v1alpha1:ResourceClaim:rmq-1 --param ports={'smtp': 1026}

should create a workload as follows:
apiVersion: carto.run/v1alpha1
kind: Workload
metadata:
  name: direct-smtp-mq-gateway
  labels:
    apps.tanzu.vmware.com/workload-type: tcp
    app.kubernetes.io/part-of: direct-project
spec:
  serviceClaims:
  - name: rmq
    ref:
      apiVersion: services.apps.tanzu.vmware.com/v1alpha1
      kind: ResourceClaim
      name: rmq-1
  source:
    git:
      url: https://github.com/gm2552/direct-smtp-mq-gateway.git
      ref:
        branch: master
  params:
  - name: ports
    value:
      port: 1026
      name: smtp

Array support
Example Command:
tanzu apps workload create direct-smtp-mq-gateway --type tcp --app direct-project --git-repo https://github.com/gm2552/direct-smtp-mq-gateway.git --git-branch master --service-ref rmq=services.apps.tanzu.vmware.com/v1alpha1:ResourceClaim:rmq-1 --param ports=[{'smtp': 1026}]

should create a workload as follows:
apiVersion: carto.run/v1alpha1
kind: Workload
metadata:
  name: direct-smtp-mq-gateway
  labels:
    apps.tanzu.vmware.com/workload-type: tcp
    app.kubernetes.io/part-of: direct-project
spec:
  serviceClaims:
  - name: rmq
    ref:
      apiVersion: services.apps.tanzu.vmware.com/v1alpha1
      kind: ResourceClaim
      name: rmq-1
  source:
    git:
      url: https://github.com/gm2552/direct-smtp-mq-gateway.git
      ref:
        branch: master
  params:
  - name: ports
    value:
    - port: 1026
      name: smtp

CC @danfein @heyjcollins for Design and Product input

ytt does a decent job defining structured data-values from cli flags
https://carvel.dev/ytt/docs/v0.40.0/ytt-data-values/#configuring-data-values-via-command-line-flags

@atmandhol - recco for the help output for the --param flag has been provided. Removing needs-design label.
This should be good to go!

As per offline discussions, we've made a decision to add a new flag --param-json to explicitly/specifically/obviously support json (rather than to overload the existing --param flag to support literal and/or json values).
Some other decisions we made:

We chose JSON rather than YAML because it's less error prone for end-users and the datatypes provided are not ambiguous for the client.
We chose to NOT support patching behavior. If/when a user wants to provide an additional value or remove an existing value from the param, the entire desired json must be provided (whatever's passed in will overwrite the existing value).

We chose JSON rather than YAML because it's less error prone for end-users and the datatypes provided are not ambiguous for the client.

Since JSON is YAML why not define --param-yaml and let the user decide what to pass in? For complex structures on a command line I do think JSON is the better option since it's not whitespace dependent. But for simple values, it's tough to beat YAML.

Since JSON is YAML why not define --param-yaml and let the user decide what to pass in?
Given JSON is valid YAML (but not the other way around) - I agree with this suggestion and will update the issue accordingly.

AC:
This acceptance testing content can be re-purposed for examples in documentation.
object support - json (PASS)
tanzu apps workload create direct-smtp-mq-gateway --type tcp --app direct-project --git-repo https://github.com/gm2552/direct-smtp-mq-gateway.git --git-branch master --service-ref rmq=services.apps.tanzu.vmware.com/v1alpha1:ResourceClaim:rmq-1 --param-yaml ports='{"name": "smtp", "port": 1026}'
Create workload:
...
     10 + |spec:
     11 + |  params:
     12 + |  - name: ports
     13 + |    value:
     14 + |      name: smtp
     15 + |      port: 1026
     16 + |  serviceClaims:
     17 + |  - name: rmq
...

object support - yaml (PASS):
tanzu apps workload create direct-smtp-mq-gateway --type tcp --app direct-project --git-repo https://github.com/gm2552/direct-smtp-mq-gateway.git --git-branch master --service-ref rmq=services.apps.tanzu.vmware.com/v1alpha1:ResourceClaim:rmq-1 --param-yaml ports=$'name: smtp\nport: 1026'
Create workload:
...
     10 + |spec:
     11 + |  params:
     12 + |  - name: ports
     13 + |    value:
     14 + |      name: smtp
     15 + |      port: 1026
     16 + |  serviceClaims:
     17 + |  - name: rmq
...

array support - json (PASS):
tanzu apps workload create direct-smtp-mq-gateway --type tcp --app direct-project --git-repo https://github.com/gm2552/direct-smtp-mq-gateway.git --git-branch master --service-ref rmq=services.apps.tanzu.vmware.com/v1alpha1:ResourceClaim:rmq-1 --param-yaml ports='[{"port": 1026, "name": "smtp" },{"port": 8080,"name": "tcp"}]'
Create workload:
...
     11 + |  params:
     12 + |  - name: ports
     13 + |    value:
     14 + |    - name: smtp
     15 + |      port: 1026
     16 + |    - name: tcp
     17 + |      port: 8080
     18 + |  serviceClaims:
     19 + |  - name: rmq
...

array support - yaml (PASS):
tanzu apps workload create direct-smtp-mq-gateway --type tcp --app direct-project --git-repo https://github.com/gm2552/direct-smtp-mq-gateway.git --git-branch master --service-ref rmq=services.apps.tanzu.vmware.com/v1alpha1:ResourceClaim:rmq-1 ----param-yaml ports=$'- port: 1026\n  name: smtp\n- port: 8080\n  name: tcp'
Create workload:
...
     11 + |  params:
     12 + |  - name: ports
     13 + |    value:
     14 + |    - name: smtp
     15 + |      port: 1026
     16 + |    - name: tcp
     17 + |      port: 8080
     18 + |  serviceClaims:
     19 + |  - name: rmq
...

nesting support - json (PASS):
tanzu apps workload create direct-smtp-mq-gateway --type tcp --app direct-project --git-repo https://github.com/gm2552/direct-smtp-mq-gateway.git --git-branch master --service-ref rmq=services.apps.tanzu.vmware.com/v1alpha1:ResourceClaim:rmq-1 --param-yaml ports='[{"deployment": {"name": "smtp", "port": 1026}}]'
Create workload:
...
     11 + |  params:
     12 + |  - name: ports
     13 + |    value:
     14 + |    - deployment:
     15 + |        name: smtp
     16 + |        port: 1026
     17 + |  serviceClaims:
     18 + |  - name: rmq
...

nesting support - yaml (PASS):
tanzu apps workload create direct-smtp-mq-gateway --type tcp --app direct-project --git-repo https://github.com/gm2552/direct-smtp-mq-gateway.git --git-branch master --service-ref rmq=services.apps.tanzu.vmware.com/v1alpha1:ResourceClaim:rmq-1 ----param-yaml ports=$'- deployment:\n    name: smtp\n    port: 1026'
Create workload:
...
     11 + |  params:
     12 + |  - name: ports
     13 + |    value:
     14 + |    - deployment:
     15 + |        name: smtp
     16 + |        port: 1026
     17 + |  serviceClaims:
     18 + |  - name: rmq
...


Django 3 Upgrade

Updated MetaCI to Django to 3.1.5
Changes to get tests passing

Removed the use of the python_2_unicode_compatible decorator
Switched from staticfiles to static. The prior was deprecated in Django 2.1
Switched from django.conf.urls.url() to django.conf.ursl.re_path(). The prior was deprecated in Django 3.1

Configuration Changes/Considerations

Django 3 dropped support for PostgreSQL 9.4. MetaCI currently shows PG Version: 12.4 (heroku pg:info -a sfdo-metaci)
We now use gettext_lazy() instead of ugettext_lazy()

Stil Outstanding

django.db.backends.postgresql_psycopg2 module has been removed and we reference it the docker_ec2.rst file and also have pscopg2 as a dependency in base.txt but not sure if this is an issue or not.

Changes for fewer pytest warnings
These aren't directly related to the upgrade, but were some low-hanging warnings that I was able to get rid of when running pytest.

Included a __test__ = False on several classes so that Pytest doesn't complain about them.
Documented providing_args for the build_complete signal in a comment as they are for documentation only.
Switched a call from logger.warn to logger.warning (the prior is deprecated)
Removed the use of assertDictContainsSubset as it is deprecated

QA Checks Performed

[x] Ran a feature test plan against main and feature/brandon-test in the CumulusCI-Test repo

Initial runs of jobs gave objc[4506]: +[NSValue initialize] may have been in progress in another thread when fork() was called.. Adding OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES fixed this issue. I added it to the env.example file.

django.db.backends.postgresql_psycopg2 module has been removed and we reference it the docker_ec2.rst file and also have pscopg2 as a dependency in base.txt but not sure if this is an issue or not.

We still need psycopg2 as a dependency in order for Django's built-in postgresql support to work (see https://docs.djangoproject.com/en/3.1/ref/databases/#postgresql-notes) but it is now implemented in django.db.backends.postgresql rather than the removed django.db.backends.postgresql_psycopg2

django.db.backends.postgresql_psycopg2 module has been removed and we reference it the docker_ec2.rst file and also have pscopg2 as a dependency in base.txt but not sure if this is an issue or not.

We still need psycopg2 as a dependency in order for Django's built-in postgresql support to work (see https://docs.djangoproject.com/en/3.1/ref/databases/#postgresql-notes) but it is now implemented in django.db.backends.postgresql rather than the removed django.db.backends.postgresql_psycopg2

Adding OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES fixed this issue. I added it to the env.example file.

I've run into this too; this seems like a good approach.

Adding OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES fixed this issue. I added it to the env.example file.

I've run into this too; this seems like a good approach.

We currently set SESSION_COOKIE_HTTPONLY = True, not sure if we also need to do this for the language cookie... my guess is no.

It should be set to true for the language cookie unless the cookie needs to be accessed by client-side scripts, which it doesn't.

We currently set SESSION_COOKIE_HTTPONLY = True, not sure if we also need to do this for the language cookie... my guess is no.

It should be set to true for the language cookie unless the cookie needs to be accessed by client-side scripts, which it doesn't.


re-calc slippage based on estimate sell

Slippage is handled a little differently with balancer pool.
tell the user the sell estimate slippage is greater then user's configured slippage.

ticket is done, closing


Allow setting card background color

Is your feature request related to a problem? Please describe.
I currently have this dashboard using Lovelace Banner cards (https://github.com/crempp/banner-card) with a different colors for every room in the house.
I'd love to replace it using room-cards, but I cannot find the way to set up a different background color for every room.
Have you tried if it is already a feature? Have you checked the wiki?
I've checked, and I cannot find the way. The styles directive doesn't seem to work.
Describe the solution you'd like
I'd love having two new configuration directives for every card: background_color and text_color  that receive a color in any format allowed in CSS.
It would be really nice if we also could different color directives for the title bar and for the space where entities are shown.

Please look at this:
https://github.com/marcokreeft87/room-card/discussions/100
You can do the same for the things you want to  do

I'm not really sure why, but it's not working. This is my room-card configuration:
title: Jardín delantero
styles:
  background-color: lightgreen;
info_entities:
  - entity: binary_sensor.detector_presencia_input
    show_icon: true
entities:
  - entity: light.fuente_entrada
  - entity: light.lampara_entrada
  - entity: light.luz_fachada_delantera

And this is what I'm getting:

I've checked that the styles attribute in the corresponding generated <ha-card> tag is empty.

Hmm can you try with an entity? So like a main entity if you know what I mean?


Patch to the refactor PR of key_reader

Signed-off-by: Adam Lee<EMAIL_ADDRESS>Signed-off-by: Haozhou Wang<EMAIL_ADDRESS>

@yydzero, please review? thanks.

others LGTM.

It would be sweet if the commit message is richer.

Please invite more guys to review before we merge, it would be safer. --From: Kuien


Add an update feed loop coordinator ID

See: https://github.com/api3dao/airseeker-v2/blob/469e82d32ab937a25aa739db9b6a3c5094d17f8d/src/update-feeds/update-feeds.ts#L40
And also https://api3workspace.slack.com/archives/C05TQPT7PNJ/p1698255510998869?thread_ts=1698050547.420629&cid=C05TQPT7PNJ
I think it would be nice to have also an code comment mentioning why we have this ID.

This might be best to hold off until discussion around https://github.com/api3dao/commons/pull/22 is resolved as it would simplify the implementation (no need to pass the coordinator ID).


StyleSheetManager on the SSR ( FOUC )

Hi everyone , i'm using StyleSheetManager in a Next.js project in order to call stylisRTLPlugin
example : (i'm using styled_components in componentStepper )
example : https://codesandbox.io/s/hello-world-1urec
GO to https://1urec.sse.codesandbox.io/about and start refreshing the page === (FOUC)
the problem is when i load the page in first ms it shows the page without style , then the style is loaded.
Anyone one please know how can i solve this problem , Thank's :)
Originally posted by @ROUDALI in https://github.com/styled-components/styled-components/issues/2794#issuecomment-540485490

Hi, @ROUDALI
you must add styled like a child in the header at   _document.js
<Head>{this.props.styleTags}</Head>

it's already added on our project, I added it in sandbox example but still has same behaviour :/

Hey, I have the exact same problem with the v5 compared to the v4, styles are not originally picked up on the server side rendering for the initial html document load. I am using as well the ServerStyleSheet inside the getInitialProps hook from NextJS.

yes still same problem, I was hoping one of the next patches would fix it (love the perf improvements)

@ROUDALI I fixed my missing style problems, main reason was that my Layout component was wrapping  in the custom  and the layout style was not picked up anymore with the latest version during the SSR. Moved my  inside each page component and it solved the issue.

I still have the same problem, missing styles on the server, styles on the client.
I'm not using next.js tho.
On the server:
<StyleSheetManager
   stylisPlugins={features.ft_rtl ? [stylisRTLPlugin] : null}
   sheet={sheet.instance}
 >
   <HelmetProvider context={helmetContext}>
       <App> // inside app there is a Layout component
           {routes}
        </App>
   </HelmetProvider>
</StyleSheetManager>

On the client (same thing without sheet prop):
<StyleSheetManager
   stylisPlugins={features.ft_rtl ? [stylisRTLPlugin] : null}
 >
   <HelmetProvider context={helmetContext}>
       <App> // inside app there is a Layout component
           {routes}
        </App>
   </HelmetProvider>
</StyleSheetManager>

Is there anything I'm doing wrong?

My guess is there are multiple versions of s-c in use on the server/client - please ensure only a single version is installed via yarn's "resolutions" feature and then report back.

I will check that out. Thanks @probablyup

Just updated to the new RC for v5 and stylis-plugin-rtl, things seem to be happy now: https://codesandbox.io/s/hello-world-8zlb6

@probablyup thank's for your answer, yes true there is no FOUC anymore ,  i don't if you noticed that the ltr style still flashing when you refresh the page, thank's again

@ROUDALI updated my sandbox, there was some bad code in there (improper DOM nesting, and also some legacy next stuff that was sending warnings). appears to be fine: https://codesandbox.io/s/hello-world-8zlb6

thank's :)


Test Suite Updates

What's New?

buildResourceIndex was broke.
Still trying to figure out what's going on with FarmEvents (it seems to work....but only under certain situations...?)
Update badges (v. important)

Coverage increased (+0.4%) to 16.462% when pulling 07449575e6ec12c8b631d2096a690de4a8f1615a on RickCarlino:master into 22f225844bcbfc351313f88ffa4725584ffa70fe on FarmBot:master.


An example of using web socket with docker backend

I want to use django-channel with traefik, django-channel handles both http and websockets. Is there an example of handling both web sockets and http in docker backend

any one who as tried this to help me with

Hello,
I had the same problem as you and I just made it worked so I thought I would share my solution in case someone is facing the same problem.
I used traefik:raclette in a my Dockerfile.
traefik.toml :

I'll close this issue, because I think the question is answered, but feel free to continue the conversation.

Are you having to pass through nginx to help resolve the issue, or that's just part of your app?  I'm having the same problem with WebSockets through traefik.  The app works if I pass ports directly from the docker container, but not through traefik.  I was on 1.3.2 and just updated to 1.3.3.


Adding missing user defined primitives.

Signed-off-by: Tim 'mithro' Ansell<EMAIL_ADDRESS>

There really should be;

Tests for the UDP modules
A CI to test that this works with various tooling

Both related to https://github.com/google/globalfoundries-pdk-libs-gf180mcu_fd_sc_mcu7t5v0/issues/4

(I'm not going to block merging this pull request on those however.)

LGTM

Related change on the 9t cell library -> https://github.com/google/globalfoundries-pdk-libs-gf180mcu_fd_sc_mcu9t5v0/pull/20


feat: show server url by pressing u

Description
#11228 implemented keyboard shortcuts. A shortcut to open the local server URL by the browser was implemented in that PR and could be considered as a solution of #10527. But I think there's cases when I want to open other URLs or in a non-default browser.
This PR implements a shortcut to show the server URLs. This way we can avoid the terminal to be narrow. The disadvantage of this approach is that additional two steps ("focusing the terminal" and "pressing u key") are required compared to #10527's suggested solution.
closes #10527
alternative to close #10592
alternative to close #10594
Additional context

What is the purpose of this pull request?

[ ] Bug fix
[x] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

I think this is a good idea 👍🏼
About https://github.com/vitejs/vite/pull/10592, it would be interesting to provide more fine grained log levels or filtering. But I agree that this PR is a better alternative.
Would you add a line break when pressing u so the printed URLs are cleaner?


Run tests from origin/iOS_squid48_1585 in native mode.

Basically, we have the same results as yesterday in iOS branch. Following tests failed:
update - do we cancel timer properly on an immediate
test that we pick up new sequences while we wait
We properly fire peer unavailable and then available when connection fails


It is decreasing

This program will decrease my 16 gb pd  into 4 gb it is a big issue

format your pendrive

format your pendrive


Test against Rails 7.1

Since Rails 7.1 has already been released, I have removed the 'rc' notation.

Thanks!


Cannot build on Windows 10, VS 2017

Hi,
Has anyone tried to build this project in Windows? I got  a bunch of errors as follows:

Do you know how to fix them?
Thank you

I just tackled this problem today, and what I did was:
I opened the file where the errors are present (def.h) and included stdint.h
The next error you'll get is MSVC not being able to open stdc++fs.lib, I just removed it from the dependencies.
The next (and hopefully last) hurdle is trying to get ahold of the real smpl_female and smpl_male files, since they're supposed to be +100MBs, but due to Github's limitations, all I have is both files being a little more than 100 Bytes.

@neonguyen1287 Sorry for the late reply. I haven't tested this project on Windows yet. Apparently, there will be some problems if you build it directly in VS.
And thanks for your suggestion @tmsc5. You follow that one to see if it works.
I think there is a bug with git-lfs. I will provide the script to generate json files from official pkl files soon. Try to download the repo instead of cloning it to fetch all the data.
Thanks for your feedback!

Close issue since I have uploaded the converter script


Finance tutorial

Summary
Finishes the loans dataset tutorial.
I have not used story generators but have covered the other features (including the fact that we now have a SNS workaround for MariaDB).
Other Changes
1
Removes reference in readthedocs config to docs/requirements.txt, which no longer exists.
2
Uses yaml.load() rather than yaml.safe_load() as we are not using the safe dumper in download_table(). The alternative would be to use the safe version in both. The "unsafe" version gives us vocab export files that can look a bit like this, with the data type included when its literal value is not enough to fully define it:
- A10: !!python/object/apply:decimal.Decimal
  - '100'
  A11: 12541

Thanks @cptanalatriste
Changes made and branch merged.


[Feature]: Pagination UQI component

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
New component to be used with offset and limit options.
Why should this be worked on?
This should make using paginations across plugins have the same experience.

Not testable Ui not ready

Verified as a part of UQI and Regression


Update FSx for NetApp ONTAP lab to install CSI driver Marketplace add-on in content

What would you like to be added?
What would you like to be added?
Update the FSx for NetApp ONTAP lab to install the FSxN CSI driver Marketplace add-on using the AWS CLI instead of doing it in Terraform. The EBS lab has already been updated, see:
https://github.com/aws-samples/eks-workshop-v2/blob/main/website/docs/fundamentals/storage/ebs/ebs-csi-driver.md
And:
https://github.com/aws-samples/eks-workshop-v2/blob/main/manifests/modules/fundamentals/storage/ebs/.workshop/cleanup.sh#L5
Any IAM roles etc. required by the addon should still be created in Terraform.
Why is this needed?
This better illustrates how EKS add-ons through Marketplace make it easy to install components like the FSx for NetApp ONTAP CSI driver.

Fixed in latest release


File Not found error

Hi, while executing the code, it generates the following error. The file is also present in the current directory. I was just wondering if anyone could help with this.

@Angelina1996 Thank you for pointing it out. It's fixed now. Try cloning it again.

Thanks, Rahul Vigneswaran, for the reply and for fixing the issue. I also resolved the problem by changing the file's extension from .yaml to .yml. It started working.


Check have info for correct function when serializing functions

If there's a bug in Livepack which causes tracker not to execute when serializing a function, this can produce incorrect output rather than an error.
For example, currently there's a known issue with classes with properties potentially having side effects when attempting to serialize them (#549).
Input:
const f = function() {
  console.log('yo!');
};
export default class X {
  foo = f();
};

This is instrumented as:
const livepack_scopeId_2 = livepack_getScopeId();
const f = function () /*livepack_track:3;f;/src/index.js*/ {
  livepack_tracker(livepack_getFnInfo_3, () => []);
  console.log('yo!');
};
module.exports = class /*livepack_track:7;c;/src/index.js*/ X {
  foo = f();
  constructor() {
    livepack_tracker(livepack_getFnInfo_7, () => [[livepack_scopeId_2, f]]);
  }
};

When Livepack calls new X(), it intends to trigger the tracker in X's constructor, but instead class property foo is evaluated first. That calls f() which executes the tracker on function f instead.
So output is:
export default function X() {
  console.log('yo!');
}

Side effects when serializing functions is a serious problem. The code which is executed could do anything, and in worst case could be a security vulnerability if an attacker was able to leverage it in order to execute code which is only meant to execute on the client on a server at build time.
It isn't possible to prevent the code execution without fixing the bug which is the source of the problem (#549 in this case). However, can at least make sure it throws an error rather than silently succeeding.
This is not specific to the class properties bug. The point is that there might be other bugs which also cause side effects when serializing functions which are as yet unknown, and it's important to surface these bugs as soon as possible.
One solution would be to call the tracker with the function ID and file path:
class /*livepack_track:7;c;/src/index.js*/ X {
  constructor() {
    livepack_tracker(
      7, // <-- Function ID
      '/src/index.js', // <-- File path
      livepack_getFnInfo_7,
      () => [[livepack_scopeId_2, f]]
    );
  }
};

If the function ID and file path the tracker are called with don't match what's in the tracker comment, then the wrong tracker has executed.
Alternatively, could put the function ID and file path in the livepack_getFnInfo functions, but would have to make sure livepack_getFnInfo is always called, not just first time the function is serialized.

#549 is now fixed.
I have over-stated the security implications of bugs in this area. Livepack runs code at build time anyway, so there are far easier ways for an attacker to illicitly execute arbitrary code than exploiting bugs like this.
Class properties were a special case, and I am fairly confident that there are no other ways remaining for serializing a function to accidentally execute code. Therefore, adding a failsafe check would just be bloat.


fix(plugin-seo): Add new type inference for  DRAFT

Closes https://github.com/payloadcms/payload/issues/4544
Description
Updates the documentation and the types for the generator functions used in the SEO plugin to better match the actual type used

[x] I have read and understand the CONTRIBUTING.md document in this repository.

Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[x] This change requires a documentation update

Checklist:

[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Existing test suite passes locally with my changes
[ ] I have made corresponding changes to the documentation

Closing in favour of a new branch without these changes


Sanitize URL for services

As reported in Ref: https://github.com/cga-harvard/HHypermap/issues/242, when OWSLib initializes OWS class instances the usual behaviour is to internally build a full GetCapabilities request via HTTP GET.  We need to ensure that URLs passed with the basic service elements (service, version, request) are stripped of these elements so they are not passed twice when OWSLib interacts with the OWS.
Examples:
>>> from owslib.csw import CatalogueServiceWeb as csw
>>> c = csw('http://demo.pycsw.org/cite/csw')
>>> c.request
'http://demo.pycsw.org/cite/csw?version=2.0.2&request=GetCapabilities&service=CSW'
>>> c = csw('http://demo.pycsw.org/cite/csw?service=CSW&version=2.0.2&request=GetCapabilitiesd')
>>> c.request
'http://demo.pycsw.org/cite/csw?service=CSW&version=2.0.2&request=GetCapabilitiesd&version=2.0.2&request=GetCapabilities&service=CSW'
>>> from owslib.wms import WebMapService as wms
>>> w = wms('http://tepeserwery.pl/tileservice/wms.php/icrsptixwh?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetCapabilities')
>>> w.request
'http://tepeserwery.pl/tileservice/wms.php/icrsptixwh?SERVICE=WMS&VERSION=1.1.1&REQUEST=GetCapabilities&service=WMS&request=GetCapabilities&version=1.1.1'

Fixed in #375


chapter-4/4-improving-accuracy-with-fine-tuning.ipynb does not contain the final finetuning section that is in book

There is a final finetuning throwing away dense and dropout layers that was expected according to the book but is missing in the notebook

Thanks! Do you want to edit with a PR?


BUG: Some tests require dipy >= 1.3

There are a number of tests in mne/test/test_morph.py that will only pass if dipy>=1.3.0. This should probably be addressed outside of this PR, but could we require dipy>=1.3.0, at least for those particular tests?

yes agreed


Project Structure /assets/index.js page

In order to reference the new structure, I've had to change /src/server.jsx to include the <script> tag
<script src="/Pages/index.js"></script>

rather than
<script src="/assets/index.js"></script>

And then had to create a static route to /Pages
app.use('/Pages',
    express.static(path.join(__dirname, 'Pages')))

Is this wrong? Couldn't get the tut working past this point without doing this

Thanks a ton for reporting this and figuring out what I'd missed in the tutorial!

Great resource. Thanks


STORM-3984: Nimbus failover causes unnecessary reassign if 600s are passed after starting Nimbus.

https://issues.apache.org/jira/browse/STORM-3984
Since the TimeOutWorkerHeartbeatsRecoveryStrategy.startTimeSecs is set on Nimbus start-up and never updated,TimeOutWorkerHeartbeatsRecoveryStrategy#exceedsMaxTimeOut always returns true after 600s (the value of supervisor.w
orker.heartbeats.max.timeout.secs) are passed after Nimbus is started.
Invalid timeout in new leader Nimbus causes unnecessary reassign right after failover.
2023-09-25 15:16:46.538 o.a.s.n.NimbusInfo main-EventThread [INFO] Nimbus figures out its name to h02
2023-09-25 15:16:46.549 o.a.s.n.LeaderListenerCallback main-EventThread [INFO] Sync remote assignments and id-info to local
2023-09-25 15:16:46.571 o.a.s.n.LeaderListenerCallback main-EventThread [INFO] active-topology-blobs [word-count-1-1695654263] local-topology-blobs [word-count-1-1695654263-stormconf.ser,word-count-1-1695654263-stormjar.jar,word-count-1-1695654263-stormcode.ser] diff-topology-blobs []
2023-09-25 15:16:46.596 o.a.s.n.LeaderListenerCallback main-EventThread [INFO] active-topology-dependencies [] local-blobs [word-count-1-1695654263-stormconf.ser,word-count-1-1695654263-stormjar.jar,word-count-1-1695654263-stormcode.ser] diff-topology-dependencies []
2023-09-25 15:16:46.596 o.a.s.n.LeaderListenerCallback main-EventThread [INFO] Accepting leadership, all active topologies and corresponding dependencies found locally.
2023-09-25 15:16:46.596 o.a.s.z.LeaderListenerCallbackFactory main-EventThread [INFO] h02 gained leadership.
2023-09-25 15:16:46.744 o.a.s.n.TimeOutWorkerHeartbeatsRecoveryStrategy timer [WARN] Failed to recover heartbeats for nodes: [c26e72ef-b84b-4d44-820a-fec9407e38cf-<IP_ADDRESS>, 57ff205e-6d90-4305-abb8-b9ff0ff7bcc3-<IP_ADDRESS>, f10f6554-0e55-4c01-a6ce-834df068d753-<IP_ADDRESS>] with timeout 600s
2023-09-25 15:16:46.807 o.a.s.d.n.HeartbeatCache timer [INFO] Executor word-count-1-1695654263:[8, 8] not alive
2023-09-25 15:16:46.808 o.a.s.d.n.HeartbeatCache timer [INFO] Executor word-count-1-1695654263:[16, 16] not alive
...(snip)
2023-09-25 15:16:46.862 o.a.s.d.n.Nimbus timer [INFO] Reassigning word-count-1-1695654263 to 3 slots
2023-09-25 15:16:46.862 o.a.s.d.n.Nimbus timer [INFO] Reassign executors: [[20, 20], [14, 14], [12, 12], [16, 16], [18, 18], [28, 28], [26, 26], [10, 10], [8, 8], [24, 24], [6, 6], [22, 22], [2, 2], [4, 4], [13, 13], [11, 11], [7, 7], [9, 9], [19, 19], [23, 23], [21, 21], [25, 25], [27, 27], [5, 5], [1, 1], [3, 3], [15, 15], [17, 17]]

The startTimeSecs should be set after the Nimbus accepts leadership.

thanks @iwasakims


Update DB_query_builder.php

recent changes broke query ordering giving a warning in line 1238 = '$this->qb_cache_orderby = array_merge($this->qb_cache_orderby, $qb_orderby);'
the warning message was about array_merge not working with a NULL object.
this was because on subsequent re-queries, the qb_cache_orderby was set to NULL not Array() as it is should have been.  See the initial instantiation of the $this->qb_cache_orderby
This PR should fix it.

The "recent changes" in question is the patch for #5168.
But while I can confirm that this is a bug, the warning itself is only a symptom. What's the actual effect that this has on queries? How do they break?

This came up as a warning in my unit tests - I didn’t notice this affecting anything on prod.  But I use query caching to help with data tables.
if you array merge with null the output will be null.  So:
php > $a = null;
php > $b = [1,2,3];
php > $c = array_merge($a,$b);
PHP Warning:  array_merge(): Argument #1 is not an array in php shell code on line 1
PHP Stack trace:
PHP   1. {main}() php shell code:0
PHP   2. array_merge() php shell code:1
Warning: array_merge(): Argument #1 is not an array in php shell code on line 1
Call Stack:
62.1301     351296   1. {main}() php shell code:0
62.1301     351296   2. array_merge() php shell code:1
php > var_dump($c);
php shell code:1:
NULL
So, this means that the orders already set would be lost on subsequent orders, after that buggy line was executed.

On 3 Oct 2017, at 8:05 pm, Andrey Andreev<EMAIL_ADDRESS>wrote:
The "recent changes" in question is the patch for #5168 https://github.com/bcit-ci/CodeIgniter/pull/5168.
But while I can confirm that this is a bug, the warning itself is only a symptom. What's the actual effect that this has on queries? How do they break?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/bcit-ci/CodeIgniter/pull/5282#issuecomment-333782969, or mute the thread https://github.com/notifications/unsubscribe-auth/AFqfHgFcDB9zTXA0yFrY9L-qKBo9G7dRks5sofjGgaJpZM4PrYDt.

Ok, thanks!
Changed the title to reflect what the PR is actually about. As a side note, please target the develop branch unless you know that something is only relevant to 3.1-stable. We do backport all PR patches manually.


Pull request is not working with HTTPS clone

if we are cloning the repo with HTTPS option, we cannot create a pull request

@safwanebrahim-uc  Git is removed pushing the code using HTTPS :Please check here . But you can push the code using SSH key.
Instruction to use ssh key is added here. Please make sure you cloned the repo using SSH key.
PR : https://github.com/UniCourt/DataEngineering-Workshop1/pull/8/files

@shamiths-uc Thanks. it worked now


chore: dynamically update cluster state, rather than waiting for sync

Fixes #
Description
dynamically update cluster state, rather than waiting for sync
Remove the special testing flow in the provisioner and more accurately model cluster state during tests.
How was this change tested?
make test
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

19 of 25 (76.0%)  changed or added relevant lines in 6 files are covered.
56 unchanged lines in 6 files lost coverage.
Overall coverage increased (+0.3%) to 74.923%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/controllers/state/cluster.go
11
12
91.67%

pkg/controllers/provisioning/provisioner.go
2
7
28.57%

Files with Coverage Reduction
New Missed Lines
%

pkg/controllers/deprovisioning/controller.go
3
100.0%

pkg/controllers/state/cluster.go
3
100.0%

pkg/test/environment.go
6
100.0%

pkg/controllers/deprovisioning/events/events.go
9
100.0%

pkg/controllers/provisioning/scheduling/topology.go
10
100.0%

pkg/controllers/provisioning/provisioner.go
25
100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
5318

Relevant Lines:
7098

💛  - Coveralls


Troubleshooting issues with sse4_crc32

We're going on trying to troubleshoot the issues with sse4_crc32 (a dependency injected by parse-server-gcd-adapter and gcloud)
from: https://github.com/GoogleCloudPlatform/gcloud-node/issues/1197#issuecomment-204638692
If you face issues deploying your code, and that this module seems to be the culplrit, please upload your npm-debug.log or any relevant stack trace.
Please also include the version of parse-server you're deploying as well as your server configuration, distribution etc...
Thanks!

@anandsuresh AWS Elastic Beanstalk, AMI 2016
uname -r
4.1.17-22.30.amzn1.x86_64

https://gist.github.com/flovilmart/3bcb096ef70e28a71d62c49904e393e6

http://stackoverflow.com/questions/34084814/npm-error-when-deploying-nodejs-to-elastic-beanstalk

@flovilmart I'm not well-versed with AWS or Amazon's offerings. Tried googling but couldn't find much on any free/OSS offerings for Elastic Beanstalk. I'm looking for a way to spin up an instance and dig deeper into the build process logs. Any suggestions/links that would point me in the right direction would be super helpful.

@anandsuresh somewhat this was related to that: https://github.com/ParsePlatform/parse-server/issues/1276
Seems that the issue at hands is not the package or anything but a memory pressure problem.

@flovilmart Looking at the logs in that thread, it seems that the SSE4_CRC32 module is building successfully:
    CXX(target) Release/obj.target/crc32c_sse42/src/crc32c_sse42.o
    AR(target) Release/obj.target/crc32c_sse42.a
    COPY Release/crc32c_sse42.a
    CXX(target) Release/obj.target/sse4_crc32/src/crc32c.o
    SOLINK_MODULE(target) Release/obj.target/sse4_crc32.node
    COPY Release/sse4_crc32.node
  make: Leaving directory `/tmp/deployment/application/node_modules/parse-server/node_modules/parse-server-gcs-adapter/node_modules/gcloud/node_modules/hash-stream-validation/node_modules/fast-crc32c/node_modules/sse4_crc32/build'

However, the gist you posted seems to fail on SSE4_CRC32.
Also, very surprising that it is running into memory pressure on a machine with a gig of RAM, but if there is orchestration involved, then I can see that might be an issue.
At this point, I'm going to go ahead and consider this issue resolved, unless you find something otherwise. Please feel free to shoot me an email/open an issue if you find something else.

Yeah that was my feeling too. We've seen high memory pressure during the build. So that don't seem to be related to your package. Thanks again for your time!

We are going to remove the GCS adapter from the repo, which will solve the issue for anyone not using the GCS adapter.


Removed obsolete pipe characters from the hosts edit page

https://bugzilla.redhat.com/show_bug.cgi?id=1226085

verified in UI.