event:generate command namespace issue

Laravel Version: 5.7.x
PHP Version: 7.2
Database Driver & Version: NA

Description:
php artisan event:generate command assumes that event class exists in app\Events
Steps To Reproduce:
Update your EventServiceProvider with event that are comming from vendor, for example
protected $listen = [
    'Laravel\Passport\Events\AccessTokenCreated' => [
        'App\Listeners\RevokeOldTokens',
    ],
];

Run php artisan event:generate
Check your app/Listeners/PruneOldTokens.php file, it should have wrong namespace imported.
use App\Events\Laravel\Passport\Events\RefreshTokenCreated;

Seems like a job for the make:listener command.

What happens when you use the ::class notation instead?

Tried this
    protected $listen = [
        \Laravel\Passport\Events\AccessTokenCreated::class => [
            'App\Listeners\RevokeOldTokens',
        ],
    ];

But same results

I can not reproduce it on laravel 5.7.x

@imanghafoori1
I have laravel passport installed, so i am sure that
Laravel\Passport\Events\AccessTokenCreated
event class exists

I can not reproduce the bug on 5.7.x It does successfully import like the following
use App\Providers\Laravel\Passport\Events\AccessTokenCreated;

But, if you don't install passport it seems like the behavior you described. Please make sure for us.

5.7.28
'Foo\Bar\Nonexisting\Event' => [
    'App\Listeners\Foo',
],

$ cat Events/Foo/Bar/Nonexisting/Event.php
<?php

namespace App\Events\Foo\Bar\Nonexisting;

I think the correct behavior in the case of nonexisting non-\App events would be throwing an error?

Another finding -
The command work well with event from Illuminate namespace
// EventServiceProvider
protected $listen = [
    'Illuminate\Notifications\Events\NotificationSent' => [
        'App\Listeners\LogNotification',
    ],
];

I've looked over the code involved with event:generate and believe I've come up with the problem and a solution. Looking for feedback before making a PR.
It all happens in the ListenerMakeCommand class.
There is a check to see if the given event namespace starts with (1)your project namespace(App), (2)"Illuminate", or (3)"\".
So it looks like the command expects 3 situations:

Your event is somewhere in your project's namespace.
Your event is in the Illuminate namespace.
Your event is elsewhere and you are showing that by starting with a '\'.

If those assumptions are true, then you should be able to generate listeners from events in third party namespaces by adding a starting '\' to your event in the $listen array of your EventServiceProvider.
However, if you do that, then the '\' doesn't get dropped and the namespace at the top of the generated listener for your event, will still have the starting '\'.
I propose a simple call to trim when replacing the 'DummyFullEvent' at the top of the listener class.
So instead of:
    return str_replace(
        'DummyFullEvent', $event, $stub
    );

We can do:
    return str_replace(
        'DummyFullEvent', trim($event, '\\'), $stub
    );

And the Event namespace will be correct in the Listener class.
Thoughts?
I've ran several test scenarios with this change in place and everything seems to work as expected?

@devcircus lgtm 👍

PR was merged.

#28007 was merged.

Note: Using event:generate as described by the OP, will still not work.

The command expects one of three event namespace styles:

Your event is in your local project's namespace (eg. App)

In this case, either import your event at the top of the service provider, or if it doesn't exist yet, just use the string version(eg. 'App\Events\MyEvent').

Your event is in the Illuminate namespace.

You can either import the event class or use the string version starting with 'Illuminate'.

Your event is in a third-party namespace.

You must use the string version and start it with a '\'. (eg. '\MyGreatVendor\MyGreatPackage\MyGreatEvent')

I guess this could be looked at in the future for a better way to handle all of these cases without having to differentiate, but for now, this should work.

#30796 I'v open a new issure for my problem.
Three ways only one could be work, and the others would not.
I do not think the problems were solved.


Visual Script property selector

3.3.rc8
WIN 10
GLES3
The visual script editor provides a limited amount of property's to select from.
That the VSeditor gives the same options as GDscript
I will give a example using the Timer Node timer.time_left

I assume this is due to this code difference in propery_selector.cpp vs visual_script_property_selector.cpp
(my understanding of c++ and the Godot project is minimal)
Control drag property
Add visual script try to get any autocomplete hints in the editor
Projects debug.zip
Being able to edit the inspector-property in line edit would be a awesome work around

This is because the time_left property is a read-only property.

get_time_left() is also not exposed to VisualScript So I think it is filtered on Property hints.

This issue exists because of this check: https://github.com/godotengine/godot/blob/8f7f5846397297fff6e8a08f89bc60ce658699cc/editor/property_selector.cpp#L170-L172
Many properties such as Node2D.global_transform have their usage flag set to 0, so they get excluded from the property selector.
I think the property selector should have a "Show all/hidden properties" checkbox to replace the usage flag filter to exclude any PROPERTY_USAGE_GROUP, PROPERTY_USAGE_CATEGORY, or PROPERTY_USAGE_INTERNAL.
This filter could be enabled by default (removing the need for a checkbox) but this risks a regression if any previously-viewable properties accidentally get filtered out.


Weights raster in DownslopeFlowpathLength producing unexpect results

I am trying to supply a weights raster to DownslopeFlowpathLength, but I'm seeing strange behavior. Originally, I my weights raster was non-uniform; each pixel generally had a different weight. After getting somewhat nonsensical results, I ran a more systematic test. In this test, I created a weight raster where all pixel weights were 0.5, 1 (default), and 2. I would expect for a given pixel that the flowpath length would roughly be 1/2 for the 0.5 weights and twice that for weights=2. Here is a table of four pixels across my DEM showing the flowpath lengths using the different weight rasters:

Clearly the weights raster is not simply scaling the flowpath lengths for pixels using the weights, and some of the values are alarmingly high (or low if very small weights are used). Note that my DEM is WGS84 unprojected, so the "lengths" reported in the above table are actually degrees.
I'm not sure if I'm misunderstanding the weights raster or if this is a bug, but figured I'd report it just in case.

Staring at the code a bit, I believe the bug is here:
https://github.com/jblindsay/whitebox-tools/blob/master/src/tools/hydro_analysis/downslope_flowpath_length.rs#L368
which should not include the weights factor.  The weights are multiplied as they are added into the pixel's distance (a few lines up) and so the data saved at each pixel includes the weights factor already.  The result of this extra factor of the weight is now a geometric series -- in the case where you "find" an "already calculated" distance, you apply another factor of the weight.  So the distance is now proportional (in some sense) to the weight raised to the "number of previously calculated pixels touched" power.  Hence weights < 1 result in distances <<< 1 * unweighted distances, and weights > 1 result in distances that blow up.
I believe just removing the weight factor at that line should fix things @jonschwenk , I'll try to build from source and see if I can confirm.
I'm a little confused by this line as well:
https://github.com/jblindsay/whitebox-tools/blob/master/src/tools/hydro_analysis/downslope_flowpath_length.rs#L299
as it looks to me (as someone who has never looked at Rust code before, nor looked at WBT code before) that everything else here assumes float64, but this suggests that the distances file is float32.  Is that ok?  Or is there potentially an issue here as well?

Ok, that was easy enough to build and check -- removing the weights factor on line 368 results in the expected output (e.g. weights of all 2 give twice the length, weights of all 0.5 give half the length).  @jblindsay let me know if you want a pull request, but I suspect this is faster for you to just fix.  @jonschwenk I have a version that works now, so we can try the biased weights for variable dx/dy and with/without 0-weight streams.

@ecoon Thanks, I built it with the proposed fix and results look as expected now.
@jblindsay There is still a minor unusual issue related to this function--the pixels immediately upstream of the outlet(s) have very small, nonzero flowpath lengths (like 10^-17 with a dx=dy=0.0002 and weight of ~30). All further-upstream pixels seem fine.


DEV2-1533 - introduce inline completions debounce

DEV2-1533
this pr adds a debounce before rendering capability as well as some tests refactoring
the debounce value can be modified via debounceMilliseconds property

@yonip23 @yairco1990 - pls review after my fixes 🙏


MultipartReader should support async for protocol

@kxepal would you take a look?

Sure!

Fixed by #640


Where to Find Ventium?

I can see that it's a Blue Skies ore, but Blue Skies has terrible documentation.  A lot of other ores (i.e. horizonite) have tooltips hinting where to find them, but ventium has nothing.  I've caved around in both the Everbright and Everdawn for quite a while and haven't come up with anything.

Frostbitten Forest biome


unixODBCDrivers: fix sqlite driver to link with sqlite3

Without this change, it doesn't actually link to libsqlite3.so
correctly, and so the output driver has unresolved symbols.
Motivation for this change
Someone on IRC noticed the unixODBC sqlite3 driver was broken, and I dug into it and eventually found this to be the problem.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

cc @vlstill as the maintainer

I need this change for some of the tools in #89787 to work properly; I can confirm that I've tested this patch and it makes broken things un-broken for me.

Fantastic! Merging based on author and tester feedback. Thanks all :tada:

@GrahamcOfBorg build unixODBCDrivers.sqlite


Ability to Blacklist/WhiteList AMIs in Launch Config

a request came in for the ability to shutdown ASGs if they're using an old AMI. If an EC2 policy to shutdown instances is based on a blacklist of amis, it could potentially cause ASGs to spin if ASG tag exception doesn't exist.

we can do this now with the new asg launch-config filter or alternative the asg image-age filter.


"ResolvePackageFileConflicts" task could not be loaded from the assembly

Getting below error while analyzing upgrade.
Msbuild failed when processing the file 'C:\Projects\xyz.csproj' with message: C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\Microsoft.NET.Build.Extensions\Microsoft.NET.Build.Extensions.ConflictResolution.targets: (30, 5): The "ResolvePackageFileConflicts" task could not be loaded from the assembly C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\Microsoft.NET.Build.Extensions\tools\net6.0\Microsoft.NET.Build.Extensions.Tasks.dll. Could not load file or assembly 'C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\Microsoft.NET.Build.Extensions\tools\net6.0\Microsoft.NET.Build.Extensions.Tasks.dll'. The system cannot find the path specified. Confirm that the  declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.

can you paste the output of dotnet --list-sdks? Thanks

2.1.202 [C:\Program Files\dotnet\sdk]
2.1.300 [C:\Program Files\dotnet\sdk]
2.1.511 [C:\Program Files\dotnet\sdk]
2.2.100 [C:\Program Files\dotnet\sdk]
3.1.405 [C:\Program Files\dotnet\sdk]
5.0.400 [C:\Program Files\dotnet\sdk]
6.0.401 [C:\Program Files\dotnet\sdk]

Fixed in new versions of UA CLI.


Budget allocation

Contributing to FB NextGen MMM R script
Issue
Hi,
Hope you are doing well. I have a question about budget allocation part.
Steps to Reproduce
model_output_collect$allSolutions
optim_result <- f.budgetAllocator(modID = "1_1_1"
,scenario = "max_historical_response"
,channel_constr_low = c(rep(1.0,14))
,channel_constr_up = c(rep(1.0,14))
I input 1 on channel_constr_low and channel_constr_up for each channels. I thought spending allocation may not be changed. However, I saw the optimize results. the spending shares changed a little bit. So I want to ask the reasons.
Another case I tried, I input 0.7 in channel_constr_low for one channel. however the results of that spending channel decrease 0.75 times. Could you please kindly explain it?
sometimes I tried different channels bounds which is 0.7-1.5. I found the response increase is negative sometimes. it makes me surprised.
Looking forward to your reply.
Thanks
Actual Results

Environment
R version (R --version)

Hey, I believe you should try out the beta version of our next release here :) The allocator is also adapted a bit and I'm curious if that works better. I've changed the default algo from MMA to SLSQP there and it seems to be more reliable so far.


Need to uninstall / install in Xcode 6.3 after update

to make KPRunEverywhereXcodePlugin work again.

KPRunEverywhereXcodePlugin has disappeared for me.  Re-installing does not fix the issue.

uninstalled
quit xcode
open xcode
reload packages in Alcatraz
install KPRunEverywhereXcodePlugin
works

@webdevotion thanks for sharing this. I've added another Xcode 6.3 UUID which will should fix this.


Merge/Inserting New PDF

Hi Team, Is that possible to merge two existing base64 Url string into one file? If there is a way to do then send me the samples. otherwise how to insert Created page with my existing base64 string or else how to convert pdf pages with my existing base64 string,  Thanks for you help.

Hello @kenzmca86! This is certainly possible. I've explained how to merge two documents in https://github.com/Hopding/pdf-lib/issues/252#issuecomment-566063380. I've adapted my example slightly for your specific question (merging existing documents stored as base64 data URIs):
const mergedPdf = await PDFDocument.create();

const pdfA = await PDFDocument.load(base64DataUriA);
const pdfB = await PDFDocument.load(base64DataUriB);

const copiedPagesA = await mergedPdf.copyPages(pdfA, pdfA.getPageIndices());
copiedPagesA.forEach((page) => mergedPdf.addPage(page));

const copiedPagesB = await mergedPdf.copyPages(pdfB, pdfB.getPageIndices());
copiedPagesB.forEach((page) => mergedPdf.addPage(page));

const mergedPdfFile = await mergedPdf.save();

Note that this example assumes base64DataUriA and base64DataUriB each contain a string that looks something like the following (or any other data format supported by PDFDocument.load):
data:application/pdf;base64,JVBERi0xLjcKJYG...

I hope this helps. Please let me know if you have any additional questions!


Move to scrapy

Move to a more modern/faster web crawler. Scrapy looks to be the way to go here. Beautiful soup worked well for a bit, but the results appear to be inconsistent. Find more information on scrapy.

This may be sidelined as I investigated scrapy. I don't need a better web crawler but a web parser. There may be some other ones out there but setting to low priority while I investigate.


An opportunity in ISPRS TC IV Symposium 2024

@hfu got an offer to contribute to the ISPRS Technical Commission IV Symposium 2024.
@hfu is thinking about presenting with the title UN Smart Maps: An Open Initiative for Data Fusion because one of the themes of ISPRS TC IV is data fusion.

I am closing considering that this issue is the same as #391.


Separate indexer into its own docker image

Description
Describe the changes or additions included in this PR.
Test Plan
How did you test the new or updated feature?

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

Going to wait to land this until we have a corresponding PR in sui-ops to manage build and deployment.


Return 404 to endpoints that don't exist

Problem Description:
Endpoints that don't exist return a HTTP 200 code and show a blank page with just the LUX header.
Expected Behavior/Solution:
Endpoints that do not exist should return the standard 404 Not Found page.
Requirements:

[x] fix routes to catch non-existing pages and return 404

Needed for promotion:
If an item on the list is not needed, it should be crossed off but not removed.

[x] Wireframe/Mockup - Kam
[x] ~Committee discussions - Sarah~
[x] ~Feasibility/Team discussion - Sarah~
[x] ~Backend requirements - TBD~
[x] Frontend requirements - Kam
[x] Are new regression tests required for QA - Amy
[x] ~Questions~

UAT/LUX Examples:

https://lux-front-tst.collections.yale.edu/notarealpage

Dependencies/Blocks:
N/A
Related Github Issues:
N/A
Related links:

Bugherd: https://www.bugherd.com/projects/284041/tasks/2590
Bugherd: https://www.bugherd.com/projects/284041/tasks/2591

Wireframe/Mockup:
Current:

Expected:

The existing 404 page also says 404 on the page, but the actual status code is a 200. Can we change the status code to be 404?

@clarkepeterf Sorry, I'm not following where this is taking place. Is that how it looks currently in production or in the current PR? When I run it locally in the current branch for this issue, I see the following (screenshot below). The frontend handles that 404 code in the ErrorPage component. I may be missing something though.

@kamerynB that is how it looks in production. You're seeing a http 304 on the frontend because my response is cached, so it is a 304 Not Modified. But if you try replacing "thisisnotreal" with something unique, the frontend will return a 200. I think the frontend should return a 404.

@clarkepeterf Ah, I see. Looking into this a bit, there are several blog and forum posts outlining how React Router doesn't/can't edit status codes. It has to be handled on a server. I've linked a few of them below. The last link outlines a possible solution with a server. We have the frontend server right now so I'm thinking the 404 pages would just be handled by the server.
https://stackoverflow.com/questions/76129187/react-error-page-return-status-code-200-how-can-i-fix-it-and-show-404-page
https://stackoverflow.com/questions/42699690/using-reactrouter-how-send-an-actual-404-status-code-on-not-found-pages
https://github.com/react-boilerplate/react-boilerplate/issues/1409
Solution that involves adding server support:
https://stackoverflow.com/questions/54727226/react-returns-a-200-for-a-page-not-found

Approved by UAT

Looks good in PROD. Closing.


end-downtime does not produce error when instance not downtimed

It makes sense to silently say "ok, instance is not downtimed anymore".

Same applied for end-maintenance


ClassCastException when using custom runtime

Describe the bug
The following error occurs when using spring native and the custom runtime:
Exception in thread "pool-4-thread-1" java.lang.ClassCastException: com.amazonaws.services.lambda.runtime.events.APIGatewayProxyResponseEvent cannot be cast to byte[]
  at org.springframework.cloud.function.adapter.aws.CustomRuntimeEventLoop.eventLoop(CustomRuntimeEventLoop.java:150)
  at org.springframework.cloud.function.adapter.aws.CustomRuntimeEventLoop.lambda$run$0(CustomRuntimeEventLoop.java:84)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
  at java.lang.Thread.run(Thread.java:829)
  at com.oracle.svm.core.thread.PlatformThreads.threadStartRoutine(PlatformThreads.java:705)
  at com.oracle.svm.core.posix.thread.PosixPlatformThreads.pthreadStartRoutine(PosixPlatformThreads.java:202)

The custom runtime just assumes that I return a byte[] from the function, which I don't. I think the regular Java runner does automatic conversion to JSON.
Maybe this cast is the problem? It just assumes that a Message<byte[]> is returned:
https://github.com/spring-cloud/spring-cloud-function/blob/b73b421366ecd4a939c9fcbc49f451ca98ac823f/spring-cloud-function-adapters/spring-cloud-function-adapter-aws/src/main/java/org/springframework/cloud/function/adapter/aws/CustomRuntimeEventLoop.java#L144
Sample
Any app with Spring Native + Spring Cloud Function that does not return byte[], running on an AWS custom runtime

I believe this was resolved with https://github.com/spring-cloud/spring-cloud-function/commit/2985193fd96b967f212eaf4c2d074432864c3e06 Feel free to reopen if it is not


[Hyperion] Add Support for rollback release for hyperion-app release (external and internal)

Proposal
https://github.com/devtron-labs/devtron/issues/1284

API Spec :
https://github.com/devtron-labs/devtron/blob/hyp_1281/specs/api-spec.yaml


Clarify how to model binary data in 3.1

Fixes #1544 for 3.1.x (See PR #3187 for the analogous 3.0.x fix).  If accepted, I will port this to 3.2.0.
Note:  I wrote most of this quite some time ago and just tidied it up now... please review it carefully as I might have missed some unfinished aspect.
This reorganizes binary data-related guidance into a "Working With Binary Data" section, as has already been done in 3.0.4.
This includes more detailed guidance on when various approaches to binary data make sense (e.g. you cannot stuff raw binary into JSON no matter what you put in your Schema Object, and while you can base64-encode entire message bodies, it takes up a lot more space for no clear benefit).
Also noted that only multipart media types with named parts are supported, as they are modeled as an object.

Paging @karenetheridge as it won't let me add you as a requested reviewer.

@ralfhandl after your approval I removed an example that contradicts the guidance in the revised section, and clarified that there is no HTTP header that can indicate base64-encoding of an entire message body (which was the problem with the removed example- it ended up senging a PNG as text with no in-message explanation of the encoding).

Nothing to preview


External links

The globbing patterns link seems to be down (Europe):
https://www.tldp.org/LDP/abs/html/globbingref.html
And the configuration options links:

CSS Minifier mentions no configuration options for CSS;
HTML Minifier points to the project's main wiki page.

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

ID: 36f55e9a-cd3f-83a0-f142-969dc10d3ceb
Version Independent ID: f6845f70-1ac6-2036-f213-a3b665b3d8bf
Content: Bundle and minify static assets in ASP.NET Core
Content Source: aspnetcore/client-side/bundling-and-minification.md
Product: aspnet-core
Technology: aspnetcore-clientside
GitHub Login: @scottaddie
Microsoft Alias: scaddie

Moved to Bundle and minify master issue #18523


Fix potential hang due to vnode proxy overload bug [JIRA: RIAK-3124]

If we call riak_core_vnode_master:sync_spawn_command, it ends up sending
a gen_event all-state event to the proxy for forwarding. However, in
handle_overload, the old code only had case clauses for '$gen_event' and
not '$gen_all_state_event'. This means the event would be passed to
handle_overload_info instead of handle_overload_request, which would
likely skip the vnode callback code that sends a response.
In Riak this meant that certain operations would hang during overload,
since the caller to sync_spawn_command would never be sent a response.
(This situation was made worse by the fact that the call is being done
with an infinity timeout, but that's an issue we'll have to address some
other time.)

create jira issue

Cherry pick of #884 - if one of these gets +1'd we can probably go ahead and merge both :)

:+1:

+1


Fix handling of stdio chunks that don't end in a new line

TaskLogWritable would cause the parts of chucks after the final new line in the chuck to be dropped. This change makes it so that they get correctly added to the buffer and logged on the next newline.
Version for master branch is #266

For a specific case where this matters, see this code in jest, which writes out each character of an error separately.

LGTM!


Copy content of one directory in other.

Java program to copy content of one directory to other.
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
This program take source and destination path as input and copy the content of source file/directory to given file/directory.
if destination file or directory doesn't exist it creates one. But if source file doesn't exist or source path is wrong it terminate with relevant message.
Fixes #78

Please delete options that are not relevant.

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

Checklist:

[x] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generates no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Changes and debugging required.

Please complete the documentation/ comments for the functioning of the code.
Bug: if the destination path is inside the source path, recursive copying occurs.

Okay got it, working on it.

Unnecessary .DS_store file detected, remove it, also don't add .gitignore file on your own, only collaborators are allowed to change/upload these files.

Deleted .DS_Store and .gitignore file. I will keep this in mind from next time.

It seems like you accidentally added the file outside the java folder, please put your code in the appropriate language folder. Then it should be good to merge. :)

@100RABHpy
Final check:
Update the readme of java directory

@100RABHpy Thanks for contributing !

Pleasure is all mine :)


0.29.0 seems incompatible with CameraX/Camera2 1.3.0

We are using CameraX/Camera2 apis in one of our projects, version 1.3.0 and are exploring libyuv-android atm. While everything works well with version 0.28.0, we are observing FATAL EXCEPTIONS when upgrading to 0.29.0. Any advice?

0.29.0 fixes a buffer size calculation bug, though. It may have been degrade.
Please let me know which class and method you used.
In addition, if you could provide a stack trace, that would be even better.

Stack trace is quite minimal:
FATAL EXCEPTION: CameraX-core_camera_0
java.lang.AbstractMethodError: abstract method "androidx.camera.core.impl.CameraFactory androidx.camera.core.impl.CameraFactory$Provider.newInstance(android.content.Context, androidx.camera.core.impl.CameraThreadConfig, androidx.camera.core.CameraSelector, long)"
at androidx.camera.core.CameraX.lambda$initAndRetryRecursively$2$androidx-camera-core-CameraX(CameraX.java:306)
at androidx.camera.core.CameraX$$ExternalSyntheticLambda3.run(Unknown Source:10)

We are using ProcessCameraProvider.getInstance(context) and adding the listener on the returned future with the main executor.
By applying
exclude group: 'androidx.camera', module: 'camera-core'

to libyuv-android dependency, everything seems to work fine though with camerax 1.3.0

Since this library depends only on the camerax-core library, perhaps the camerax version is different between core and others.
Version 0.30.0 is released to remove the dependency on camerax.
It resolves version mismatch.

Thanks, I tried with 0.30.0 and everything works well with camerax 1.3.0 (without the exclude) 👍


Add test adapter test coverage

Description

Results

Codecov Report
Attention: Patch coverage is 0% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 5.19%. Comparing base (eacadc8) to head (47f89e3).
Report is 1 commits behind head on main.

Files
Patch %
Lines

.../Statistics/Tests/TestResultWithOutlierAnalysis.cs
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #169       +/-   ##
==========================================
- Coverage   66.04%   5.19%   -60.86%
==========================================
  Files         309     232       -77
  Lines        8196    6743     -1453
  Branches      955     838      -117
==========================================
- Hits         5413     350     -5063
- Misses       2480    6379     +3899
+ Partials      303      14      -289

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


Server doesn't work with nghttp2

If I run the Ruby server, then try to make a request with nghttp2 like in the example readme, the request fails:
Server window:
[aaron@TC example (master)]$ ruby server.rb
Starting server on port 8080
New TCP connection!
Exception: HTTP2::Error::HandshakeError, HTTP2::Error::HandshakeError - closing socket.

Client window:
[aaron@TC example (master)]$ nghttp -vnu http://localhost:8080
[  0.001] Connected
[  0.001] HTTP Upgrade request
GET / HTTP/1.1
Host: localhost:8080
Connection: Upgrade, HTTP2-Settings
Upgrade: h2c-14
HTTP2-Settings: AAMAAABkAAQAAP__
Accept: */*
User-Agent: nghttp2/0.7.13

Some requests were not processed. total=1, processed=0

AFAICT, the state is waiting_magic, but it doesn't recognize the header sent from nghttp2.  I'll continue to investigate, but I thought I'd post here!

Don't have access to test it, but quick guess.. set the DRAFT version in helper.rb to "h2c-14".

Digging into it a bit more.. On first pass, it looks like PRIORITY before headers could be causing the protocol error on our side.
[  0.001] Connected
[  0.001] send SETTINGS frame <length=12, flags=0x00, stream_id=0>
          (niv=2)
          [SETTINGS_MAX_CONCURRENT_STREAMS(0x03):100]
          [SETTINGS_INITIAL_WINDOW_SIZE(0x04):65535]
[  0.001] send PRIORITY frame <length=5, flags=0x00, stream_id=3>
          (dep_stream_id=0, weight=201, exclusive=0)
[  0.001] send PRIORITY frame <length=5, flags=0x00, stream_id=5>
          (dep_stream_id=0, weight=101, exclusive=0)
[  0.001] send PRIORITY frame <length=5, flags=0x00, stream_id=7>
          (dep_stream_id=0, weight=1, exclusive=0)
[  0.001] send PRIORITY frame <length=5, flags=0x00, stream_id=9>
          (dep_stream_id=7, weight=1, exclusive=0)
[  0.001] send PRIORITY frame <length=5, flags=0x00, stream_id=11>
          (dep_stream_id=3, weight=1, exclusive=0)

Will have to spend more quality time with it to track it down.. /cc @mad-p

I sort of blindly added this case:
https://github.com/igrigorik/http-2/compare/master...kenichi:priority
and that seems to make server.rb work with nghttp client, unless you -u for an upgrade. No idea if that's the correct handling, to activate a new stream like that. But I had to do more invasive stuff to handle upgrade connections with reel:
https://gist.github.com/kenichi/816fdc13f0eff5194905

@kenichi yep, that's pretty close. Just pushed an update that allows PRIORITY to open streams in idle state (see https://github.com/igrigorik/http-2/commit/e4d17186149c76c9a66a176bc73c7d6396b66524).
@tenderlove apologies about the delay. If you try with above commit + NPN things should work (i.e. ruby server.rb -s, nghttp -v https://localhost:8080). We don't handle the http/1.1 upgrade flow in the demo server, which is why -u is causing an error.

@igrigorik cool, thanks!

{ ~/git/http-2  git:(upstream ⚡ master) 2≡ 2D 7A} > ruby example/upgrade_server.rb
...
{ /git/http-2/example  git:(upstream ⚡ master) 2≡ 2D 7A} > nghttp -vu http://localhost:8080
[  0.002] Connected
[  0.002] HTTP Upgrade request
GET / HTTP/1.1
host: localhost:8080
connection: Upgrade, HTTP2-Settings
upgrade: h2c
http2-settings: AAMAAABkAAQAAP__
accept: */*
user-agent: nghttp2/1.5.0

[  0.002] HTTP Upgrade response
HTTP/1.1 101 Switching Protocols
Connection: Upgrade
Upgrade: h2c

[  0.002] HTTP Upgrade success
[  0.002] send SETTINGS frame <length=12, flags=0x00, stream_id=0>
          (niv=2)
          [SETTINGS_MAX_CONCURRENT_STREAMS(0x03):100]
          [SETTINGS_INITIAL_WINDOW_SIZE(0x04):65535]
[  0.002] send PRIORITY frame <length=5, flags=0x00, stream_id=3>
          (dep_stream_id=0, weight=201, exclusive=0)
[  0.002] send PRIORITY frame <length=5, flags=0x00, stream_id=5>
          (dep_stream_id=0, weight=101, exclusive=0)
[  0.002] send PRIORITY frame <length=5, flags=0x00, stream_id=7>
          (dep_stream_id=0, weight=1, exclusive=0)
[  0.002] send PRIORITY frame <length=5, flags=0x00, stream_id=9>
          (dep_stream_id=7, weight=1, exclusive=0)
[  0.002] send PRIORITY frame <length=5, flags=0x00, stream_id=11>
          (dep_stream_id=3, weight=1, exclusive=0)
[  0.002] send PRIORITY frame <length=5, flags=0x00, stream_id=1>
          (dep_stream_id=11, weight=16, exclusive=0)
[  0.002] recv SETTINGS frame <length=6, flags=0x00, stream_id=0>
          (niv=1)
          [SETTINGS_MAX_CONCURRENT_STREAMS(0x03):100]
[  0.002] send SETTINGS frame <length=0, flags=0x01, stream_id=0>
          ; ACK
          (niv=0)
[  0.003] recv (stream_id=1) :status: 200
[  0.003] recv (stream_id=1) content-length: 27
[  0.003] recv (stream_id=1) content-type: text/plain
[  0.003] recv HEADERS frame <length=14, flags=0x04, stream_id=1>
          ; END_HEADERS
          (padlen=0)
          ; First response header
Hello[  0.003] recv DATA frame <length=5, flags=0x00, stream_id=1>
 HTTP 2.0! GET request[  0.003] recv DATA frame <length=22, flags=0x01, stream_id=1>
          ; END_STREAM
[  0.003] send GOAWAY frame <length=8, flags=0x00, stream_id=0>
          (last_stream_id=0, error_code=NO_ERROR(0x00), opaque_data(0)=[])

h2c upgrade should work now, closing.


[C++] Some navigation links don't have target IDs

This is no longer required. C++ parser has been rewritten and this issue was specific to older parser.


Use stable version of controller-runtime

Signed-off-by: Tamal Saha<EMAIL_ADDRESS>
What this PR does / why we need it:
controller-runtime and controller-tools have released stable versions. This pr just updates those. Also, they have updated to k8s v0.21.1. So, that is also updated.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

NONE

/test pull-cert-manager-bazel

/test pull-cert-manager-bazel

FYI The integration tests which failed were already known to be flaky: https://github.com/jetstack/cert-manager/issues?q=is%3Aopen+is%3Aissue+label%3Akind%2Fflake but perhaps this update made them even less reliable.

This test passed the first time https://prow.build-infra.jetstack.net/pr-history/?org=jetstack&repo=cert-manager&pr=4085 . It is failing after that.

/test pull-cert-manager-bazel
/lgtm

/retest

@tamalsaha I'm investigating why the integration tests keep failing. In https://github.com/jetstack/cert-manager/pull/4094 I've configured envtest to collect control-plane logs, which might show us what's going wrong.
I wonder if we need to update the etcd and kube-apiserver to match the new version of controller-runtime envtest.
I tried this https://github.com/kubernetes-sigs/controller-runtime/tree/master/tools/setup-envtest and it installed newer versions than we use:
richard  ~  setup-envtest use
Version: 1.20.2
OS/Arch: linux/amd64
md5: rRhNNycJ5TK2HQfap0M1yQ==
Path: /home/richard/.local/share/kubebuilder-envtest/k8s/1.20.2-linux-amd64

richard  ~  /home/richard/.local/share/kubebuilder-envtest/k8s/1.20.2-linux-amd64/etcd --version
etcd Version: 3.4.9
Git SHA: 54ba95891
Go Version: go1.12.17
Go OS/Arch: linux/amd64

 richard  ~  /home/richard/.local/share/kubebuilder-envtest/k8s/1.20.2-linux-amd64/kube-apiserver --version
Kubernetes v1.20.2

In https://prow.build-infra.jetstack.net/view/gs/jetstack-logs/pr-logs/pull/jetstack_cert-manager/4094/pull-cert-manager-bazel/1403353551941406720 we can see
2021-06-11 14:12:44.826737 W | etcdserver: read-only range request "key:\"/registry/health\" " with result "range_response_count:0 size:4" took too long (135.576691ms) to execute
2021-06-11 14:12:45.032608 W | etcdserver: read-only range request "key:\"/registry/clusterroles/system:controller:resourcequota-controller\" " with result "range_response_count:0 size:4" took too long (113.341189ms) to execute
2021-06-11 14:12:45.755349 W | etcdserver: read-only range request "key:\"/registry/health\" " with result "range_response_count:0 size:4" took too long (164.445525ms) to execute
2021-06-11 14:12:45.755408 W | etcdserver: read-only range request "key:\"/registry/clusterrolebindings/system:controller:cronjob-controller\" " with result "range_response_count:0 size:4" took too long (183.565072ms) to execute
2021-06-11 14:12:45.755566 W | etcdserver: read-only range request "key:\"/registry/health\" " with result "range_response_count:0 size:4" took too long (167.361993ms) to execute
I0611 14:12:45.899462    7819 controller.go:606] quota admission added evaluator for: roles.rbac.authorization.k8s.io

I0611 14:12:45.932346    7819 controller.go:606] quota admission added evaluator for: rolebindings.rbac.authorization.k8s.io
W0611 14:12:46.118891    7819 lease.go:224] Resetting endpoints for master service "kubernetes" to [<IP_ADDRESS>]
E0611 14:12:46.119913    7819 controller.go:222] unable to sync kubernetes service: Endpoints "kubernetes" is invalid: subsets[0].addresses[0].ip: Invalid value: "<IP_ADDRESS>": may not be in the loopback range (<IP_ADDRESS>/8)

I0611 14:12:48.305890    7819 dynamic_cafile_content.go:181] Shutting down client-ca-bundle::/tmp/k8s_test_framework_360675936/client-cert-auth-ca.crt
I0611 14:12:48.305942    7819 controller.go:180] Shutting down kubernetes service endpoint reconciler
I0611 14:12:48.306258    7819 controller.go:122] Shutting down OpenAPI controller
I0611 14:12:48.306282    7819 apiservice_controller.go:106] Shutting down APIServiceRegistrationController
I0611 14:12:48.306297    7819 apiapproval_controller.go:197] Shutting down KubernetesAPIApprovalPolicyConformantConditionController
I0611 14:12:48.306315    7819 cluster_authentication_trust_controller.go:463] Shutting down cluster_authentication_trust_controller controller
I0611 14:12:48.306331    7819 customresource_discovery_controller.go:219] Shutting down DiscoveryController
I0611 14:12:48.306344    7819 naming_controller.go:299] Shutting down NamingConditionController
I0611 14:12:48.306358    7819 establishing_controller.go:84] Shutting down EstablishingController
I0611 14:12:48.306377    7819 nonstructuralschema_controller.go:203] Shutting down NonStructuralSchemaConditionController
I0611 14:12:48.306391    7819 available_controller.go:398] Shutting down AvailableConditionController
I0611 14:12:48.306404    7819 crd_finalizer.go:275] Shutting down CRDFinalizer
I0611 14:12:48.306419    7819 crdregistration_controller.go:142] Shutting down crd-autoregister controller
I0611 14:12:48.306433    7819 autoregister_controller.go:164] Shutting down autoregister controller
I0611 14:12:48.306869    7819 dynamic_cafile_content.go:181] Shutting down client-ca-bundle::/tmp/k8s_test_framework_360675936/client-cert-auth-ca.crt
I0611 14:12:48.306943    7819 controller.go:87] Shutting down OpenAPI AggregationController
I0611 14:12:48.307239    7819 tlsconfig.go:234] Shutting down DynamicServingCertificateController
I0611 14:12:48.307263    7819 dynamic_serving_content.go:144] Shutting down serving-cert::/tmp/k8s_test_framework_360675936/apiserver.crt::/tmp/k8s_test_framework_360675936/apiserver.key
I0611 14:12:48.307339    7819 secure_serving.go:222] Stopped listening on <IP_ADDRESS>:40343
E0611 14:12:48.309013    7819 controller.go:183] Get https://<IP_ADDRESS>:40343/api/v1/namespaces/default/endpoints/kubernetes: write tcp <IP_ADDRESS>:57452-><IP_ADDRESS>:40343: write: broken pipe
2021-06-11 14:12:48.355603 N | pkg/osutil: received terminated signal, shutting down...

2021-06-11 14:12:48.355746 I | etcdserver: skipped leadership transfer for single member cluster
2021-06-11 14:12:52.511641 I | etcdmain: etcd Version: 3.3.12
2021-06-11 14:12:52.511676 I | etcdmain: Git SHA: d57e8b8
2021-06-11 14:12:52.511681 I | etcdmain: Go Version: go1.10.8
2021-06-11 14:12:52.511686 I | etcdmain: Go OS/Arch: linux/amd64

Which looks like an error in the kube-apiserver causes the whole control-plane to be torn down and restarted.
And also signs of etcd struggling with slow responses.
I'll try updating etcd and kube-apiserver. But I wonder if this might have been made worse when we reduced the CPU available to the test pods in https://github.com/jetstack/testing/pull/503

Thanks for looking into this @wallrj . There seems to be bunch of changes around envtest https://github.com/kubernetes-sigs/controller-runtime/releases . That might be it.

/test pull-cert-manager-bazel

Thanks @irbekrm ! Any idea what changed here?

Thanks to you @tamalsaha!

Any idea what changed here?

Things unrelated to the version bump as such- seems like pull-cert-manager-bazel CI job was previously failing because Bazel was spinning up multiple parallel processes which each ran tests that consume a lot of CPU, so individual tests were timing out- we fixed this by limiting Bazel job concurrency to 1 in testing#513 .
(This PR in particular hit that issue, because controller-runtime is a dependency of all our resource-intensive integration tests which caused them all to be re-run- we otherwise use Bazel to cache the test results).


Add extension support and first extension, unwrap_newtypes

TODO

[x] More tests, especially regarding error handling
[x] discuss TODOs / design
[x] docs for extensions (postponed)
[x] add syntax to Sublime plugin

Fixes
Fixes #69

@torkleyy The syntax highlighting in Sublime is messed up as soon as I add attributes:

Could you file that on https://github.com/ron-rs/sublime-ron please?

Done: https://github.com/ron-rs/sublime-ron/issues/6


Upstream CodecMK-based interface from ouroboros-consensus

https://github.com/input-output-hk/ouroboros-network/tree/feature/utxo-hd uses lmdb-simple, but it can not satisfy the Serialise constraints that are ubiquitous in lmdb-simple: ouroboros-consensus uses explicit encoders/decoders instead of Serialise instances to provide serialisation.
We should investigate whether we can come up with an interface that unifies the Serialise- and codec-based interfaces. One way this could be achieved is by rewriting the definitions in lmdb-simple to require explicit codecs instead of Serialise constraints, and add wrappers that can feed in the codecs.  Decoder s a) -> t) -> t
feedDecoder f = f decode

f_serialise :: Serialise a => a
f_serialise = feedDecoder $ feedEncoder $ f_codec

f_codec :: (a -> Encoding) -> (forall s. Decoder s a) -> a
f_codec _ _ = undefined

Also, the get,  put and delete functions (and auxiliary definitions) could be made to operate on bytestrings directly, moving the responsibility of serialisation/deserialisation up a few levels.


Develop yaml, WIP, just a beachhead to start iterating, runs kpng in …

…a pod but needs svc accounts, adding later

not needed, using dock/ds.yaml


In Net 6.0 frozen call  consumer.Subscribe(topic); when using .SetLogHandler

After migration wrom .Net 5 to .Net 6 my old code not worked
consumerConfig.Debug = "consumer";
consumerBuilder.SetLogHandler(delegate(IConsumer<string, string> arg1, LogMessage arg2)
{
SetLogHandler(arg1, arg2, consumerName);
});
consumer.Subscribe(topic);  <-- Here frozen
private void SetLogHandler(IConsumer<string, string> consumer, LogMessage message, string consumerName)
{
if (new[] {"REBALANCE", "ASSIGNOR", "ASSIGN"}.Contains(message.Facility))
{
_logger.LogInformation($"{consumerName} " + message.Message);
}
}
I am commented consumerBuilder.SetLogHandler and now all OK. Issue reproduced on 1.8.2 and om 1.9.0

Thanks. It's been reported before, but interesting to know that this is an issue on .NET 6 not .NET 5.
As a workaround, you could capture stderr to get the log messages instead of setting a log handler.

As a workaround, you could capture stderr to get the log messages instead of setting a log handler
Can you to show C# example?

I'm having the similar issue - asp.net core 6 app hangs, but only under IDE and only in Debug mode.
Removing LogHandler from consumers fixes it.
@mhowlett Could you please provide a link to previous report?
BTW. I'm using Rider and Linux

I am using VS and project in Docker Compose for Linux

if the log handler is empty, do you still see problems?
reiterating that not using a log handler, and reading from stderr is preferable because it is much more efficient (in fact a log handler can't handle the volume of messages output by debug=all on many machines). suggest doing this as a work around (and best practice).

closing in favor of #1834 - they are not the same but bundling all the "problems with LogHandler" up into one issue.


Rules like eslint

Hi, this plugins works great but it doesn't detect typo/formatting bugs like eslint does, is it there possible to do that?
for example:
if(userData){
should warning that expected spaces after if and missing space before opening brace:
if (userData) {

Look into tslint. Out of scope for this project.


fix #909

Set the default value required by ECMA specification when parsing <w:br> tags. This avoids to unintentionally convert TextWrapping breaks (who are implicit when there is no type attribute) to Page breaks.

LGTM


xds: move admin protos used by CSDS into their own file

Signed-off-by: Mark D. Roth<EMAIL_ADDRESS>Commit Message: xds: move admin protos used by CSDS into their own file
Additional Description: This addresses some dependency problems that will allow us to move the non-Envoy-specific parts of the API to the cncf/xds repo while keeping the Envoy-specific parts here, as per the design doc.
Risk Level: Low
Testing: N/A
Docs Changes: N/A
Release Notes: N/A
Platform Specific Features: N/A
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]
@ejona86 and @dfawley, please confirm that this will not break anything for Java or Go.  Thanks!

/retest


Save the raster as an xarray

Continuation from PR #30

This should live in this repo: https://github.com/urbangrammarai/timeseries_signatures_archive


rename to arxiv

can you try to make an empty commit to see if I fixed the CI?

Not really sure why the ci is failing, during the checkout ... mmm 🤔

workflow should be ok now, it says it is pending your approval
https://github.com/FrancescoSaverioZuppichini/LinkedInGPT/actions/runs/5323727538


Margin & padding utils

What does this PR do?
Adds utility classes for margin and padding. Conventions borrowed from Bootstrap.
Where should the reviewer start?
Screenshots!
How should this be manually tested?
Run the docs locally, confirm that they all look good.
Any background context you want to provide?
I also extracted a table for utils out to an include b/c I didn't want to rewrite the same table 3 times. This partially fulfills the Refactor all the tables into an _includes template ticket.
As part of rebuilding the docs some of the order properties changed in unrelated files.
What are the relevant tickets?
Margin + Padding
Screenshots (if appropriate)

Any other deploy steps?
nope

I love the orange diagonal lines and how they show the spacing, that's really helpful.


Fixes RPY orientation in IMU output (based on testing).

During testing we noticed that the roll and pitch axes were swapped and the roll value (actually pitch) was inverse. This fix has been tested on a vehicle and appears to output both the correct roll and pitch.

Looks good, thanks.  By the way, as long as you're testing things, would you like to look at #9?  (auto-detect IMU rate)

I will try to get to #9. Would you mind merging this one since it built OK?


Feature Request: Use Name as Text Node

Are you reporting a bug, or opening a feature request?
Feature Request
What is the actual behavior/output?

What is the behavior/output you expect?
the names are at the position the nodes. Instead of beside the nodes

What version of react-d3-tree are you using?
1.16.1 (lastest)

There's a file https://github.com/bkrem/react-d3-tree/blob/master/src/Node/SvgTextElement.js, not sure if it's related

Isn't what you're looking for supported by nodeLabelComponent? https://github.com/bkrem/react-d3-tree#nodelabelcomponent

Isn't what you're looking for supported by nodeLabelComponent? https://github.com/bkrem/react-d3-tree#nodelabelcomponent

Thanks, this worked fine!


Improve error message for non-existent asset

Now we print the name of the asset and the base directory where we looked for
the error instead of throwing a null pointer exception.
Fixes #296

LGTM


provide better feedback when readme has the fair software badge, but with the wrong compliance

(currently, it says you don't have the badge)
see discussion here #54

Verified with on a GitHub README with
 [![fair-software.eu](https://img.shields.io/badge/fair--software.eu-%E2%97%8F%20%20%E2%97%8F%20%20%E2%97%8B%20%20%E2%97%8F%20%20%E2%97%8F-yellow)](https://fair-software.eu)

and howfairis reports
howfairis https://github.com/iomega/zenodo-upload
...
Calculated compliance: ● ● ● ● ●

It seems you have not yet added the fair-software.eu badge to
your README.md. You can do so by pasting the following snippet:

[![fair-software.eu](https://img.shields.io/badge/fair--software.eu-%E2%97%8F%20%20%E2%97%8F%20%20%E2%97%8F%20%20%E2%97%8F%20%20%E2%97%8F-green)](https://fair-software.eu)

The repo has a yellow badge while howfairis reports green.

Verified with on a GitHub README with
 [![fair-software.eu](https://img.shields.io/badge/fair--software.eu-%E2%97%8F%20%20%E2%97%8F%20%20%E2%97%8B%20%20%E2%97%8F%20%20%E2%97%8F-yellow)](https://fair-software.eu)

and howfairis reports
howfairis https://github.com/iomega/zenodo-upload
...
Calculated compliance: ● ● ● ● ●

It seems you have not yet added the fair-software.eu badge to
your README.md. You can do so by pasting the following snippet:

[![fair-software.eu](https://img.shields.io/badge/fair--software.eu-%E2%97%8F%20%20%E2%97%8F%20%20%E2%97%8F%20%20%E2%97%8F%20%20%E2%97%8F-green)](https://fair-software.eu)

The repo has a yellow badge while howfairis reports green.

solved by PR #135


Debugging hangs after logging some amount of text to the Debug Console

VSCode Version: 1.47.0
OS Version: Windows 10 1909

Steps to Reproduce:
Debug this JavaScript code in Node.js:
for(let i = 0; i < 20000; i++)
{
    console.log(i);
}

VSCode should still remain responsive while the loop should seemingly hang somewhere between logging 15,000 and 16,000.
The issue appears to be related to logging some amount of text to the Debug Console.
I also tested this code in 1.46.1 and the issue does not occur in that version.

Does this issue occur when all extensions are disabled?: Yes

Same issues running/debugging mocha tests. Just hangs after a lot of output to the debug window.
Only in 1.47 - related to the new javascript debugger perhaps?

Thanks for the issue. If this is causing problems, you can for the moment use the old debugger by setting debug.javascript.usePreview: false

Thanks again, this can be fixed by doing one of the following:

After 5PM today, using the latest nightly extension (recommended)
Setting outputCapture: "std" in your launch.json
Setting debug.javascript.usePreview: false to use the old debugger until this lands in a stable release

Yeah, no problem. Glad to see it's resolved!

I've encountered the same issue but only with debugging tests (mocha) for some reason.
happened in latest insiders:
Version: 1.48.0-insider (user setup)
Commit: cb31fc6ce2b4da3520392b622aa3ebc5b313533b
Date: 2020-07-15T05:34:49.078Z (1 day ago)
Electron: 8.3.3
Chrome: 80.0.3987.165
Node.js: 12.13.0
V8: 8.0.426.27-electron.0
OS: Windows_NT x64 10.0.18363
and also in latest stable:
Version: 1.47.1 (user setup)
Commit: 485c41f9460bdb830c4da12c102daff275415b53
Date: 2020-07-13T22:42:53.386Z (2 days ago)
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363
it seems it was enough to set debug.javascript.usePreview: false.
now debugger does not hang

@talr1 see the solution directly above: https://github.com/microsoft/vscode/issues/102254#issuecomment-658247768

@talr1 see the solution directly above: #102254 (comment)

i wrote at the end that the solution works for me :-)
however, was using this option (debug.javascript.usePreview: false)the debug console pane remain empty. if remove this option, it start showing content again (in those cases where the debugger did not hang)
any idea?

@connor4312 If I use those solutions, I can get the debugger to start running again, but no breakpoints work. Is that expected?

No; please file an issue using the bug template here https://github.com/microsoft/vscode-js-debug/issues/new/choose

Hey Connor, thank you for responding! It appears there was something else nefarious at work here. I was indeed able to set breakpoints. I don't remember exactly what was going on because it was a crazy day at work, but I think I had maybe not been running a watch task, so sourcemap debug breakpoint locations were incorrect. So the solution above did indeed get the debugger running as well as allow breakpoints to work. Thanks again!

Nightly extension does not fix this problem for me, only solutions #2 and #3.

Please file an issue and include a tracelog using the link above!

@connor4312 With so many dups of this bug I didn't want to pile on yet another, but will do.


fix: updated e2e test cases for VRFS

At least one VRF test is failing in the latest run: https://github.com/equinix/metal-cli/actions/runs/7412860080/job/20170604176?pr=393#step:5:230

Nevermind, everything's working fine after a rebase. Guess we fixed whatever was happening here.


For Consideration: Add support to replace "libde_rest_plugin.so" with custom binary.

It would be a nice to have feature to be able to replace the "libde_rest_plugin.so" plugin with one custom built between releases. I am working with some other people deploying their Home Assistant, but occasionally support for new sensors / lights need to be added.

I think you should be able to do this already, just mount your custom compiled libde_rest_plugin.so into the container:
-v /path/to/your/libde_rest_plugin.so:/usr/share/deCONZ/plugins/libde_rest_plugin.so

If i specify the path to the rest plugin, the custom path for the persist storage (-v /opt/deconz:/root/.local/share/dresden-elektronik/deCONZ ) don't work anymore. Or is ignored.

@marthoc any help on this please?

Anyone got this working?
Would be really good to have this feature.

I'm also started to compile latest commits before next release, 'coz I want to pair my brand new opple switches... and also confused faced with some procedure to replace plugin library. Not sure where need to move.

After compiling, I tried to:
docker cp ../libde_rest_plugin.so docker:/tmp
sudo docker exec -it deconz bash
cp /tmp/libde_rest_plugin.so /usr/share/deCONZ/plugins

After restarting the container, the plugin is simply ignored:
20:22:30:985 HTTP Server listen on address <IP_ADDRESS>, port: 80, root: /usr/share/deCONZ/webapp/
20:22:31:008 CTRL. 3.16.220:22:31:340 dev /dev/ttyAMA0
20:22:31:340 ZCLDB init file /root/.local/share/dresden-elektronik/deCONZ/zcldb.txt
20:22:31:436 found node plugin: libde_signal_plugin.so - Signal Monitor Plugin
20:22:31:453 found node plugin: libstd_otau_plugin.so - STD OTAU Plugin
20:22:31:727 dev /dev/ttyAMA0

This is strange I forked the git project which creates the docker container (marthoc/deconz) and adapted the Dockerfile
.......
COPY libde_rest_plugin.so /usr/share/deCONZ/plugins

VOLUME [ "/root/.local/share/dresden-elektronik/deCONZ" ]

EXPOSE ${DECONZ_WEB_PORT} ${DECONZ_WS_PORT} ${DECONZ_VNC_PORT}

ENTRYPOINT [ "/tini", "--", "/start.sh" ]

Which gives 0 results the login to RESt and Phoscon does not work

I do not understand why this does not work. I created a Dockerfile:
FROM marthoc/deconz
COPY libde_rest_plugin.so /usr/share/deCONZ/plugins

I verified that the file is copied to the container. Still does nor work. I am not able to login to Phoscon with the credential I used before.

Well guys, I previously reported that I did not succeed with replacing the plugin with a newly compiled one. Damn it, I'm tired of waiting, I have 6 switches already :))))

For the people using docker on a Raspberry Pi, i managed to compile the plugin from master on the docker image:
Start a shell in the docker image, then run
cd /opt
apt update
apt install qt5-default libqt5sql5 libqt5websockets5-dev libqt5serialport5-dev libsqlite3-dev build-essential git
git clone https://github.com/dresden-elektronik/deconz-rest-plugin.git
wget http://deconz.dresden-elektronik.de/ubuntu/beta/deconz-dev-2.05.75.deb
dpkg -x deconz-dev-2.05.75.deb ./deconz-dev
cp ./deconz-dev/usr/include/* /usr/include/ -R
qmake && make -j2

now the plugin ../libde_rest_plugin.so is created. Extract the plugin from the docker image and mount it to the image using the -v parameter
-v /path/to/your/libde_rest_plugin.so:/usr/share/deCONZ/plugins/libde_rest_plugin.so`
(I got this command from this thread, didn't test it bc i'm using Kubernetes)
After restarting the container the image should be refreshed and the new plugin is working, without any authentication issues to Phoscon, VNC or the API.

wget http://deconz.dresden-elektronik.de/ubuntu/beta/deconz-dev-2.05.75.deb
dpkg -x deconz-dev-2.05.75.deb ./deconz-dev
cp ./deconz-dev/usr/include/* /usr/include/ -R
qmake && make -j2

Compilation fails:
/usr/bin/ld: cannot find -ldeCONZ
collect2: error: ld returned 1 exit status
Makefile.Release:321: recipe for target '../libde_rest_plugin.so' failed
make[1]: *** [../libde_rest_plugin.so] Error 1
make[1]: Leaving directory '/home/lukics/git.com/deconz-rest-plugin'
Makefile:38: recipe for target 'release' failed
make: *** [release] Error 2

Instead you can do (take care about the architecture, which I did not do in the past):
wget -O - http://phoscon.de/apt/deconz.pub.key | \
           sudo apt-key add -

sudo sh -c "echo 'deb [arch=armhf] http://phoscon.de/apt/deconz \
            $(lsb_release -cs)-beta main' > \
            /etc/apt/sources.list.d/deconz.list"
sudo apt update
sudo apt install deconz-dev

I had an issue before because I did not see in the command above that [arch] has to be set and  I got the wrong package. Now the library is picked up and loaded

The complete steps I did on my Pi (armhf):
cd
mkdir git.com
cd git.com
git clone https://github.com/dresden-elektronik/deconz-rest-plugin.git
cd deconz-rest-plugin
wget -O - http://phoscon.de/apt/deconz.pub.key | \
           sudo apt-key add -

sudo sh -c "echo 'deb [arch=armhf] http://phoscon.de/apt/deconz \
            $(lsb_release -cs)-beta main' > \
            /etc/apt/sources.list.d/deconz.list"
sudo apt update
sudo apt install deconz-dev
qmake && make -j2

I am using docker-compose and defined for all my containers a mountpoint at /datavol.
For Phoscon it is:
/datavol/deconz/conf
/datavol/deconz/lib

I copied the compiled file to the mountpoint
cp ../libde_rest_plugin.so /datavol/deconz/lib
the docker-compose.yml is:
version: "2"
services:
  deconz:
    image: marthoc/deconz:latest
    container_name: deconz
    network_mode: host
    restart: always
    volumes:
      - /datavol/deconz/conf:/root/.local/share/dresden-elektronik/deCONZ
      - /datavol/deconz/lib/libde_rest_plugin.so:/usr/share/deCONZ/plugins/libde_rest_plugin.so
    devices:
      - /dev/ttyAMA0
    environment:
      - DECONZ_WEB_PORT=80
      - DECONZ_VNC_MODE=1
      - DECONZ_VNC_PASSWORD=.guesswhat.
      - DECONZ_WS_PORT=443
      - DEBUG_INFO=1
      - DEBUG_APS=0
      - DEBUG_ZCL=0
      - DEBUG_ZDP=0
      - DEBUG_OTAU=0

The complete steps I did on my Pi (armhf):

So for the newbs (like me) on the block, Raspberry Pi 4, that should normally run armhf? I have googled it, but haven't found a straightforward answer..

Raspberry Pi 4, that should normally run armhf?

Yes

While my solution does work on the docker image maintained by @marthoc, I tried to replicate the correct way to install the deconz headers using the deCONZ apt repo on the Docker image.
I had to install git, wget build-essential and lsb-release first:
apt update && apt install wget git lsb-release build-essential
then the instruction posted by @lukicsl can be used.

Hello !
I'm facing the same issue.
I'm running latest deCONZ docker on my Synology DS918+ with Portainer (1.23.2) and Docker 18.09.6 (API: 1.39). I run deCONZ as stack
version: '2'
services:
  app:
    image: marthoc/deconz
    network_mode: host
    restart: always
    ports:
      - 39980:39980
      - 39981:39981
      - 39982:39982
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /volume1/docker/deCONZ/config/:/root/.local/share/dresden-elektronik/deCONZ
      #FOR DEV MODE
      - /volume1/docker/deCONZ/lib/libde_rest_plugin_motion.so:/usr/share/deCONZ/plugins/libde_rest_plugin.so
    devices:
      - /dev/ttyACM0
    environment:
      - DECONZ_WEB_PORT=18080
      - DECONZ_WS_PORT=18081
      - DEBUG_INFO=1
      - DEBUG_APS=0
      - DEBUG_ZCL=0
      - DEBUG_ZDP=0
      - DEBUG_OTAU=0
      - DECONZ_VNC_MODE=1
      - DECONZ_VNC_PORT=18082
      - DECONZ_VNC_PASSWORD=HIDDEN
      - DECONZ_UPNP=1
      - DECONZ_DEVICE=/dev/ttyACM0

I've compiled a new lib rest and try to mount it but it's not working ... Same logs except the lib is not loaded by the binary

@smesguich how di you compile the library? did you select the right architecture (amd64) when setting the deb sources?

@smesguich how di you compile the library? did you select the right architecture (amd64) when setting the deb sources?

I've compiled the lib with WSL Ubuntu 18.04.

Hello !
I'm facing the same issue.
I'm running latest deCONZ docker on my Synology DS918+ with Portainer (1.23.2) and Docker 18.09.6 (API: 1.39). I run deCONZ as stack
version: '2'
services:
  app:
    image: marthoc/deconz
    network_mode: host
    restart: always
    ports:
      - 39980:39980
      - 39981:39981
      - 39982:39982
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /volume1/docker/deCONZ/config/:/root/.local/share/dresden-elektronik/deCONZ
      #FOR DEV MODE
      - /volume1/docker/deCONZ/lib/libde_rest_plugin_motion.so:/usr/share/deCONZ/plugins/libde_rest_plugin.so
    devices:
      - /dev/ttyACM0
    environment:
      - DECONZ_WEB_PORT=18080
      - DECONZ_WS_PORT=18081
      - DEBUG_INFO=1
      - DEBUG_APS=0
      - DEBUG_ZCL=0
      - DEBUG_ZDP=0
      - DEBUG_OTAU=0
      - DECONZ_VNC_MODE=1
      - DECONZ_VNC_PORT=18082
      - DECONZ_VNC_PASSWORD=HIDDEN
      - DECONZ_UPNP=1
      - DECONZ_DEVICE=/dev/ttyACM0

I've compiled a new lib rest and try to mount it but it's not working ... Same logs except the lib is not loaded by the binary

Actually your compose looks strange, 'coz u used the host, but continue to use port mapping, for?

Hello !
I'm facing the same issue.
I'm running latest deCONZ docker on my Synology DS918+ with Portainer (1.23.2) and Docker 18.09.6 (API: 1.39). I run deCONZ as stack
version: '2'
services:
  app:
    image: marthoc/deconz
    network_mode: host
    restart: always
    ports:
      - 39980:39980
      - 39981:39981
      - 39982:39982
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /volume1/docker/deCONZ/config/:/root/.local/share/dresden-elektronik/deCONZ
      #FOR DEV MODE
      - /volume1/docker/deCONZ/lib/libde_rest_plugin_motion.so:/usr/share/deCONZ/plugins/libde_rest_plugin.so
    devices:
      - /dev/ttyACM0
    environment:
      - DECONZ_WEB_PORT=18080
      - DECONZ_WS_PORT=18081
      - DEBUG_INFO=1
      - DEBUG_APS=0
      - DEBUG_ZCL=0
      - DEBUG_ZDP=0
      - DEBUG_OTAU=0
      - DECONZ_VNC_MODE=1
      - DECONZ_VNC_PORT=18082
      - DECONZ_VNC_PASSWORD=HIDDEN
      - DECONZ_UPNP=1
      - DECONZ_DEVICE=/dev/ttyACM0

I've compiled a new lib rest and try to mount it but it's not working ... Same logs except the lib is not loaded by the binary

Actually your compose looks strange, 'coz u used the host, but continue to use port mapping, for?

Well, I've comment the network_mode:host  (it was for a test) but the issue is the same

-/volume1/docker/deCONZ/lib/libde_rest_plugin_motion.so:/usr/share/deCONZ/plugins/libde_rest_plugin.so

Single file volume and renaming the file, I am not sure if this works.
do a
docker inspect -f '{{ .Mounts }}' yor_container_id
if the volume is mounted at all

I've tried with :
/volume1/docker/deCONZ/lib/libde_rest_plugin_motion.so:/usr/share/deCONZ/plugins/libde_rest_plugin.so
sudo docker inspect -f '{{ .Mounts }}' deconz_app_1
[{bind  /volume1/docker/deCONZ/config /root/.local/share/dresden-elektronik/deCONZ   true rprivate} {bind  /volume1/docker/deCONZ/lib/libde_rest_plugin.so /usr/share/deCONZ/plugins/libde_rest_plugin.so   true rprivate} {bind  /etc/localtime /etc/localtime  ro false rprivate}]

can you you make a try
chmod -R a+w /volume1/docker/deCONZ
before starting the container, just for try

It's strange but it's works
(Before)
user@NAS:~$ ll /volume1/docker/deCONZ
total 20
drwxrwxrwx+ 1 user users   112 Apr 27 09:29 .

can you do:
objdump -f libde_rest_plugin.so
what is the output?

objdump is not available inside the container. And not on my synology.

Issue found :
Samuel@NAS:~$ sudo docker exec -it deconz_app_1 /bin/bash
root@d97f43ce8c9d:/# ls -ali /usr/share/deCONZ/plugins/
total 2572
10634 drwxr-xr-x 1 root root      126 Mar  9 14:48 .
10605 drwxr-xr-x 1 root root       84 Mar  9 14:48 ..
81255 -rwxrwxrwx 1 1029 users 2329104 Apr 28 20:02 libde_rest_plugin.so
10636 -rwxr-xr-x 1 root root    72376 Mar  8 18:19 libde_signal_plugin.so
10637 -rwxr-xr-x 1 root root   229016 Mar  8 18:19 libstd_otau_plugin.so
root@d97f43ce8c9d:/# exit
exit

Samuel@ROLON-NAS918:~$ sudo ls -ali /volume1/docker/deCONZ/lib/
total 2276
80322 drwxrwxrwx 1 Samuel users      40 Apr 28 09:21 .
76030 drwxrwxrwx 1 Samuel users     112 Apr 27 09:29 ..
81255 -rwxrwxrwx 1 Samuel users 2329104 Apr 28 20:02 libde_rest_plugin.so

inside the conntainer with original lib :
root@eb5961ae44dd:/# objdump -f /usr/share/deCONZ/plugins/libde_rest_plugin.so

/usr/share/deCONZ/plugins/libde_rest_plugin.so:     file format elf64-x86-64
architecture: i386:x86-64, flags 0x00000150:
HAS_SYMS, DYNAMIC, D_PAGED
start address 0x00000000000425d0

With custom lib :
root@494d799bff67:/# objdump -f /usr/share/deCONZ/plugins/libde_rest_plugin.so

/usr/share/deCONZ/plugins/libde_rest_plugin.so:     file format elf64-x86-64
architecture: i386:x86-64, flags 0x00000150:
HAS_SYMS, DYNAMIC, D_PAGED
start address 0x0000000000040f20

@lukicsl Despite changing permission, It's still not working ....
IDK what could be the issue ....

Issue found :
Samuel@NAS:~$ sudo docker exec -it deconz_app_1 /bin/bash
root@d97f43ce8c9d:/# ls -ali /usr/share/deCONZ/plugins/
total 2572
10634 drwxr-xr-x 1 root root      126 Mar  9 14:48 .
10605 drwxr-xr-x 1 root root       84 Mar  9 14:48 ..
81255 -rwxrwxrwx 1 1029 users 2329104 Apr 28 20:02 libde_rest_plugin.so
10636 -rwxr-xr-x 1 root root    72376 Mar  8 18:19 libde_signal_plugin.so
10637 -rwxr-xr-x 1 root root   229016 Mar  8 18:19 libstd_otau_plugin.so
root@d97f43ce8c9d:/# exit
exit

Samuel@NAS:~$ sudo ls -ali /volume1/docker/deCONZ/lib/
total 2276
80322 drwxrwxrwx 1 Samuel users      40 Apr 28 09:21 .
76030 drwxrwxrwx 1 Samuel users     112 Apr 27 09:29 ..
81255 -rwxrwxrwx 1 Samuel users 2329104 Apr 28 20:02 libde_rest_plugin.so

I made the instruction from @lukicsl a oneliner :-)
sudo apt update && sudo apt install wget git lsb-release build-essential && cd && mkdir git.com && cd git.com && git clone https://github.com/dresden-elektronik/deconz-rest-plugin.git && cd deconz-rest-plugin && wget -O - http://phoscon.de/apt/deconz.pub.key | sudo apt-key add - && sudo sh -c "echo 'deb [arch=armhf] http://phoscon.de/apt/deconz $(lsb_release -cs)-beta main' > /etc/apt/sources.list.d/deconz.list" && sudo apt update && sudo apt install deconz-dev && qmake && make -j2 && cp ../libde_rest_plugin.so /usr/share/deCONZ/plugins/ && echo "Container should reboot now...."
Btw, I think this ticket can be closed as the original issue has been resolved. We could possible add all the information to an article on the wiki? (Like on a subsection of https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Update-deCONZ-manually)?
If the original poster still reads this ticket... @ericvandamme what do you think? Could you close this ticket?

I made a oneliner to compile a new version and to copy it:
sudo apt update && sudo apt install wget git lsb-release build-essential && cd && mkdir git.com && cd git.com && git clone https://github.com/dresden-elektronik/deconz-rest-plugin.git && cd deconz-rest-plugin && wget -O - http://phoscon.de/apt/deconz.pub.key | sudo apt-key add - && sudo sh -c "echo 'deb [arch=armhf] http://phoscon.de/apt/deconz $(lsb_release -cs)-beta main' > /etc/apt/sources.list.d/deconz.list" && sudo apt update && sudo apt install deconz-dev && qmake && make -j2 && cp ../libde_rest_plugin.so /usr/share/deCONZ/plugins/ && echo "Container should reboot now...."
Btw, I think this ticket can be closed as the original issue has been resolved. We could possible add all the information to an article on the wiki? (Like on a subsection of https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Update-deCONZ-manually)?
If the original poster still reads this ticket... @ericvandamme what do you think? Could you close this ticket?

That a not a good way to make a container, it would be better to bind a external files or include this step in the docker file in the building step image. A docker container should not compile in the lib.

I have mounted the plugin location to a NFS share in kubernetes. This way I can compile the plugin and then destroy the container.

Sorry but I still have the same issue.
I've tried an other strategy : I've tried a custom docker file based on original image.
Dockerfile
FROM marthoc/deconz
RUN rm -f /usr/share/deCONZ/plugins/libde_rest_plugin.so
COPY libde_rest_plugin.so /usr/share/deCONZ/plugins
RUN chown root:root /usr/bin/deCONZ

with
USER@SYNOLOGY:/volume1/docker/deCONZ/devCONZ$ ls
Dockerfile  libde_rest_plugin.so

USER@SYNOLOGY:/volume1/docker/deCONZ$ sudo docker build --tag devconz:0.0.1 devCONZ/
Password:
Sending build context to Docker daemon  2.362MB
Step 1/4 : FROM marthoc/deconz
 ---> 0d6e2f8979bc
Step 2/4 : RUN rm -f /usr/share/deCONZ/plugins/libde_rest_plugin.so
 ---> Running in b1b34765e2d1
Removing intermediate container b1b34765e2d1
 ---> 08dbc8b07402
Step 3/4 : COPY libde_rest_plugin.so /usr/share/deCONZ/plugins
 ---> aa0e54aed7e1
Step 4/4 : RUN chown root:root /usr/bin/deCONZ
 ---> Running in b1e81caf9c16
Removing intermediate container b1e81caf9c16
 ---> 56b592bb3b1a
Successfully built 56b592bb3b1a
Successfully tagged devconz:0.0.1

But IDK why the lib is not detected in the container logs
USER@SYNOLOGY:/volume1/docker/deCONZ$ sudo docker exec -it devconz_app_1 /bin/bash
Password:
root@4130559328d1:/# cd /usr/share/deCONZ/plugins/
root@4130559328d1:/usr/share/deCONZ/plugins# ls -ali
total 2612
10651 drwxr-xr-x 1 root root     126 Jun 14 13:33 .
10622 drwxr-xr-x 1 root root      84 May 26 12:39 ..
11322 -rwxr-xr-x 1 root root 2359656 Jun 14 13:30 libde_rest_plugin.so
10653 -rwxr-xr-x 1 root root   72376 May 24 20:35 libde_signal_plugin.so
10654 -rwxr-xr-x 1 root root  233496 May 24 20:35 libstd_otau_plugin.so

Hello there,
I'll be happy to contribute but IDK why, the problems is still present ...
@marthoc any idea to make it works ?

As there hasn't been any new replies and as there are newer versions, i'm closing this issue. If this needs to be re-opened, please ping me :)


Memory leak

Hello, I noticed that memory wasnt freed after download is complete, here's my code:
`app.get('/dltorrent', function (req, res) {
var urlObj = url.parse(req.url, true),
query = urlObj.query;
if (query.magnet !== undefined && query.title !== undefined && query.magnet !== 'undefined' && query.title !== 'undefined') {
	var opts = {
		tmp: '/usr/share/nodejs/www/data',
		connections: 10,
		uploads: 0
	}

	var engine = torrentStream('magnet:?xt=urn:btih:' + query.magnet, opts);
	engine.on('ready', function() {
		engine.files.forEach(function(file) {
			if (file.name == query.title) {
				var stream = file.createReadStream();
					res.setHeader('Content-disposition', 'attachment; filename=' + query.title);
					res.setHeader('Content-type', mime.lookup(query.title));
					stream.pipe(res);
			}
		});
	});
} else {
	res.end('invalid dl parameters');
}

});`

Okay, I noticed that these leaks were caused by:
swarm.add(addr) => torrent-stream index.js Line 702
Any idea on how to solve it ?

I simplified the leak reproduction, see https://github.com/dizel3d/node-memory-leak-sample
I made 300 iterations and couldn't detect leaking objects using v8-profiler, comparing heap snapshots. It seems the leak has native code roots.


Server side search does not work

Hello,
I have been trying hard to use server side search in a small project that I am doing, but it does not work. The search helper function gets called twice after injection and never after that. I thought I did something wrong in my code, but I found out even the demo of server search does not work - please see last input on the demo page. Problem with changed API?
It seems that in the helper definition:
Template.foo.helpers({
search: function(query, sync, callback){
....
all of query, sync or callback are undefined when this gets called, and it gets called only once after rendering...
Best regards
Jan

@janvydra please try again, it seems meteor now requires that Meteor.methods should be declared in server and client. On client it is used to generate stubs.

@janvydra I just ran the demo app and it took around 10 minutes for the server to populate the collection.  After it was populated the server-side search worked fine. The code was just updated this morning to work with version <IP_ADDRESS>; if you were trying to run the demos using that version then all would have been broken.

Thank you, it started to work now.
Jan


GitHub (balena) self-hosted runners (re)homing

Currently they live in an obscure location.
Should we re-home them to this repository and build the block(s) or give them a separate home (i.e. balenablocks/flowzone)?
After that we can add the block to existing Jenkins and resinCI fleets, since we have compute power there already.

I think they should have their own repo under the product-os GH org (not attached to Flowzone or resinCI).
They shouldn't be added to the balenablocks org for a few reasons:

Our GH orgs are based on loops, not application types (or that is the intent anyway)
Following the above, balenablocks repos may be moving to balenalabs soon (cc @nucleardreamer )
balenaCloud orgs support all application types, there is no reason to put all blocks in one org, and all fleets in another

So we should use Flowzone to build the product-os GH runners and deploy them to a product-os block.


@Input on a property throws exception

Repro:

tns create TestApp --ng

tns platform add android

Change app.component.ts to:
import {Component, Input} from "@angular/core";

@Component({
    selector: "my-app",
    template: ''
})
export class AppComponent {
    @Input() numberField: number;

    // Comment the @Input attribute and you'll
    // not get an exception
    @Input()
    public set NumberProperty(val: number) {
    }
}

Run

Expected: the app runs without any problem
Actual: exception:
java.lang.RuntimeException: Unable to create application com.tns.NativeScriptApplication: com.tns.NativeScriptException:
Fail to load module: /data/data/org.nativescript.TestApp/files/app/main.js

TypeError
File: "<unknown>, line: 1, column: 265

StackTrace:
	Frame: function:'decorate', file:'/data/data/org.nativescript.TestApp/files/app/tns_modules/reflect-metadata/Reflect.js', line: 76, column: 23
	Frame: function:'__decorate', file:'/data/data/org.nativescript.TestApp/files/internal/ts_helpers.js', line: 10, column: 96
	Frame: function:'', file:'/data/data/org.nativescript.TestApp/files/app/app.component.js', line: 16, column: 5
	Frame: function:'', file:'/data/data/org.nativescript.TestApp/files/app/app.component.js', line: 29, column: 2
	Frame: function:'require', file:'', line: 1, column: 266
	Frame: function:'', file:'/data/data/org.nativescript.TestApp/files/app/main.js', line: 4, column: 23
	Frame: function:'require', file:'', line: 1, column: 266

	at android.app.ActivityThread.handleBindApplica

Turns out that if you @Input() on a property, you get that exception. If you remove the property or the @Input, everything works. Also, note that @Input on a field works fine.

tns version: 2.0.1
OS: Win 10
Emulator: genymotion

I use them all over the place so they do work (on both properties and fields), but I do always give them a name, try checking that.
 public numberField: number;

 @Input("anotherField")
 public anotherField: any;

 @Input("NumberProperty")
 public set NumberProperty(val: number) {
   console.log(val)
   this.numberField = val
 }

I can't see any other problems in your code.

@matt4446 I tried your suggestion but it didn't solve the problem. I get the same exception. Maybe it's platform/version specific issue?

Just found out that if I use Component's inputs property, things work.
import {Component, Input} from "@angular/core";

@Component({
    selector: "my-app",
    template: '',
    inputs: [ 'NumberProperty' ]
})
export class AppComponent {
    public set NumberProperty(val: number) {
    }
}

I use Genymotion, so probably not ;)
Taking another look and this time creating from tns create TestApp --ng
By the way I'm no closer to solving your problem (using the @Input, so hopefully someone else can point it out. tns create TestApp --ng was quite easy to repeat a few. I'm leaning towards there is something wrong with the output of the command.
It seemed a little odd having an input parameter on the main component. (but I managed to reproduce the error).
So I added a very basic component which also blew up (to add to the main component), but before adding the input parameter it won't run:
JS: TypeError: Cannot read property 'query' of null
JS:     at /data/data/org.nativescript.TestApp/files/app/tns_modules/@angular/compiler/src/provider_parser.js:360:37
etc

So I've compared:
tsconfig, slightly different -> changed to be equal - probably not the problem.
package.json -> a few differences, changed that too. probably not the problem.
app/package.json -> cleared that out. probably not the problem.
Router is next ...
nope, not that either (same error as cannot read property query. Single page was fine, it just didn't like adding a component like the one at the end of this post).
Other things tried:
deleting the node_modules
and platforms a few times.
So I've currently failed to find a significant difference between the project setup now and one of my demos. I've never used the command tns create TestApp --ng` before so there could be just something obvious that isn't setup correctly.
I presume you don't get the same result by following the steps on the getting started page? Which continued to become this:
Where adding what failed before just works as with my other projects. Curios.
@Component({
  selector: "test",
  template: `

  `
})
export class TestComponent{

  @Input("hi")
  public set Hi(value: string){
    console.log(value);
  }

}

Add the directive to the component, and the xml
directives: [TestComponent]
<test hi="hello"></test>

output:
JS: ANGULAR BOOTSTRAP DONE.
JS: hello

It turned out to be an issue with the global __decorate function - we are using an outdated version of it in the android-runtime. It should be resolved with the next release of NativeScript (there is already a PR).
For now you can keep using the @Components({ ... inputs: [] }) workaround.


There is no password in docker-compose output

Question 1: There is no password output from docker-compose... Where is it?
Question 2: How to set own password during docker-compose instead of random password?
Question 3: What if I forgot a password, how can I reset password?
docker-compose  up bloodhound_app-db_1 is up-to-date bloodhound_graph-db_1 is up-to-date Starting bloodhound_bloodhound_1 ... done Attaching to bloodhound_app-db_1, bloodhound_graph-db_1, bloodhound_bloodhound_1 app-db_1      |  app-db_1      | PostgreSQL Database directory appears to contain a database; Skipping initialization app-db_1      |  app-db_1      | 2024-06-20 05:32:31.195 UTC [1] LOG:  starting PostgreSQL 13.2 (Debian 13.2-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit app-db_1      | 2024-06-20 05:32:31.195 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432 app-db_1      | 2024-06-20 05:32:31.195 UTC [1] LOG:  listening on IPv6 address "::", port 5432 app-db_1      | 2024-06-20 05:32:31.197 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" app-db_1      | 2024-06-20 05:32:31.201 UTC [25] LOG:  database system was shut down at 2024-06-20 05:24:47 UTC app-db_1      | 2024-06-20 05:32:31.204 UTC [1] LOG:  database system is ready to accept connections graph-db_1    | Changed password for user 'neo4j'. IMPORTANT: this change will only take effect if performed before the database is started for the first time. graph-db_1    | 2024-06-20 05:33:06.974+0000 INFO  Starting... graph-db_1    | 2024-06-20 05:33:07.274+0000 INFO  This instance is ServerId{5dbdd441} (5dbdd441-d6f2-4079-8d14-95c9cfff143b) graph-db_1    | 2024-06-20 05:33:08.080+0000 INFO  ======== Neo4j 4.4.34 ======== graph-db_1    | 2024-06-20 05:33:08.887+0000 INFO  Performing postInitialization step for component 'security-users' with version 3 and status CURRENT graph-db_1    | 2024-06-20 05:33:08.887+0000 INFO  Updating the initial password in component 'security-users' graph-db_1    | 2024-06-20 05:33:10.612+0000 INFO  Bolt enabled on <IP_ADDRESS>:7687. graph-db_1    | 2024-06-20 05:33:11.182+0000 INFO  Remote interface available at http://localhost:7474/ graph-db_1    | 2024-06-20 05:33:11.185+0000 INFO  id: 6C6C7C14D5CEFF7E24133DD85807E519418E22153FF54A8BC60969357256B966 graph-db_1    | 2024-06-20 05:33:11.185+0000 INFO  name: system graph-db_1    | 2024-06-20 05:33:11.185+0000 INFO  creationDate: 2024-03-23T12:47:16.55Z graph-db_1    | 2024-06-20 05:33:11.185+0000 INFO  Started. bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:27.52075751Z","message":"Reading configuration found at /bloodhound.config.json"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:27.521275275Z","message":"Logging configured"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:27.542572634Z","message":"No database driver has been set for migration, using: neo4j"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:27.542658787Z","message":"Connecting to graph using Neo4j"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:27.56317595Z","message":"Executing SQL migrations for v5.8.0"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:27.574250144Z","message":"Executing SQL migrations for v5.8.1"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:27.582041195Z","message":"Executing SQL migrations for v5.8.2"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:27.599381222Z","message":"Executing SQL migrations for v5.11.0"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:27.614729209Z","message":"Permission permission://graphdb/Mutate created during migration"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:27.61490039Z","message":"Permission permission://db/Wipe created during migration"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:27.623678786Z","message":"Role Power User updated during migration"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:27.625540854Z","message":"Role Administrator updated during migration"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:27.643783644Z","message":"Feature flag clear_graph_data created"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:27.644107673Z","message":"Feature flag fedramp_eula created"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:27.645156929Z","message":"Feature flag risk_exposure_new_calculation created"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:29.037819318Z","message":"Adding index issuancepolicy_system_tags_index to labels IssuancePolicy on properties system_tags using lucene+native-3.0"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:29.119926839Z","message":"Adding index issuancepolicy_user_tags_index to labels IssuancePolicy on properties user_tags using lucene+native-3.0"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:29.134588129Z","message":"Adding index issuancepolicy_name_index to labels IssuancePolicy on properties name using lucene+native-3.0"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:29.148028976Z","message":"Adding index issuancepolicy_domainsid_index to labels IssuancePolicy on properties domainsid using native-btree-1.0"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:29.171501809Z","message":"Adding index issuancepolicy_tenantid_index to labels IssuancePolicy on properties tenantid using native-btree-1.0"} bloodhound_1  | {"level":"error","time":"2024-06-20T05:33:29.406515275Z","message":"Invalid neo4j configuration supplied; returning default values"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:29.406533242Z","message":"Analysis requested by init"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:29.408110121Z","message":"Starting daemon API Daemon"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:29.408127569Z","message":"Starting daemon Tools API"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:29.408130259Z","message":"Starting daemon Data Pruning Daemon"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:29.408133117Z","message":"Starting daemon Data Pipe Daemon"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:33:29.408135522Z","message":"Server started successfully"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:30.836309815Z","message":"Fetching group members for 11 AD nodes"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:30.996614704Z","message":"Collected 5 group members"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:31.184428954Z","message":"Fetching group members for 8 AD nodes"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:31.225802189Z","message":"Collected 6 group members"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:31.322524964Z","message":"Fetching group members for 10 AD nodes"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:31.35602826Z","message":"Collected 5 group members"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:31.435942261Z","message":"Fetching group members for 11 AD nodes"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:31.498118476Z","message":"Collected 5 group members"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:31.596848341Z","message":"Fetching group members for 11 AD nodes"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:31.663886777Z","message":"Collected 5 group members"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:31.756563507Z","message":"Fetching group members for 2 AD nodes"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:31.756630052Z","message":"Collected 0 group members"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:31.808844498Z","message":"Fetching group members for 11 AD nodes"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:31.867540986Z","message":"Collected 4 group members"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:31.940450574Z","message":"Fetching group members for 1 AD nodes"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:31.94046347Z","message":"Collected 0 group members"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:31.978958813Z","message":"Fetching group members for 1 AD nodes"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:31.979467853Z","message":"Collected 0 group members"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:32.016524539Z","message":"Fetching group members for 11 AD nodes"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:32.062080856Z","message":"Collected 5 group members"} bloodhound_1  | {"level":"info","elapsed":1436.142525,"time":"2024-06-20T05:34:32.114466452Z","message":"Finished tagging Active Directory Tier Zero"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:33.108490243Z","message":"Expanding all AD group and local group memberships"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:33.127220342Z","message":"Collected 397 groups to resolve"} bloodhound_1  | {"level":"info","elapsed":1072.709152,"time":"2024-06-20T05:34:34.181232344Z","message":"ResolveAllGroupMemberships"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:34.363958694Z","message":"Finished post-processing 87 active directory computers"} bloodhound_1  | {"level":"warn","time":"2024-06-20T05:34:34.61621294Z","message":"Error in PostCanAbuseWeakCertBinding: unable to fetch strongcertificatebindingenforcementraw property for node ID 1933: property strongcertificatebindingenforcementraw: property not found"} bloodhound_1  | {"level":"warn","time":"2024-06-20T05:34:34.618830023Z","message":"Error in PostCanAbuseWeakCertBinding: unable to fetch strongcertificatebindingenforcementraw property for node ID 2322: property strongcertificatebindingenforcementraw: property not found"} bloodhound_1  | {"level":"warn","time":"2024-06-20T05:34:34.623120507Z","message":"Error in PostCanAbuseUPNCertMapping: unable to fetch certificatemappingmethodsraw property for node ID 1933: property certificatemappingmethodsraw: property not found"} bloodhound_1  | {"level":"warn","time":"2024-06-20T05:34:34.626204384Z","message":"Error in PostCanAbuseUPNCertMapping: unable to fetch certificatemappingmethodsraw property for node ID 2322: property certificatemappingmethodsraw: property not found"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:35.068484845Z","message":"Finished building adcs cache"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:35.567655725Z","message":"Started Data Quality Stats Collection"} bloodhound_1  | {"level":"info","time":"2024-06-20T05:34:35.912603958Z","message":"Cache successfully reset by datapipe daemon"} bloodhound_1  | {"level":"info","elapsed":6416.996682,"measurement_id":1,"time":"2024-06-20T05:34:35.91262394Z","message":"Graph Analysis"}

I wonder why it sets random password in neo4j instead of default password "neo4j:neo4j" which user change later.
docker install is so inconvenient as it sets random password first

The logs show that you were spinning up a previously created database; hence, an initial user password was not set. You'd need to re-use the previously set password. From your logs:
app-db_1      | PostgreSQL Database directory appears to contain a database; Skipping initialization app
If you don't know the password, you have two options:

Reset the installation: docker compose down -v
Reset the password in PostgreSQL. The following would set the password for the account, admin to the password admin

postgres=> select id from users where principal_name='admin';

id
--------------------------------------
long-uuid-value

postgres=> update auth_secrets set digest='$argon2id$v=19$m=1048576,t=1,p=2$QUB3+B/dvvpbOYKT9Wr1EA==$3sV71u+fW4kX+euamzIgOQ==' where user_id='long-uuid-value';

If you would like to set a default password, you may do so in either the .env file (here: https://github.com/SpecterOps/BloodHound/blob/main/examples/docker-compose/.env.example#L12) or in the docker_compose.yaml (here: https://github.com/SpecterOps/BloodHound/blob/main/examples/docker-compose/docker-compose.yml#L22).


update license with up-to-date year range

Only made 1 change:

Modified the license to include a range with the current year.

No other changes made.

Awesome! Thanks

You're welcome!


Updated popup code

Now, when the popup is opened it shifts left or right to avoid clipping off the left or right edge of the viewport.

Hey man, this thing is awesome! I'd love to help out more with it - if there's anything in particular you'd like me to pick up, let me know.


s2i: build hung, stuck

Bug 1370265
Bugzilla link https://bugzilla.redhat.com/show_bug.cgi?id=1370265
Detailed explanation
a timeout on container start could result on waitgroup.Done being called twice, the waitgroup going negative, and down a hung/panic path
the refactoring of pull 576 completed with this pull
@bparees @csrwng @rhcarvalho PTAL

reposting comment from @bparees in pr 576 for convenience:
@rhcarvalho would really appreciate if you could take a look at this fix, we're trying to resolve a blocker bug for 3.3. The go stacks for the hang we're trying to address are in the referenced bug.
The net is wg.Done() could get called twice (once for the source upload and once for the timeout error on starting the container)

@rhcarvalho belated apologies for tagging you in all this stuff on your PTO, forgot you were out.  So..welcome back and ptal when you can :)

+1 @rhcarvalho :-)

@rhcarvalho do you think you'll be able to take a look at this?  We are interested in your perspective as the one who originally introduced (if I read git blame correctly) the use of the wait group in this path.
thanks

Sorry for the delay. Looking at it.

no worries @rhcarvalho - we know you are super busy with feed henry

thanks for looking

closing in favor of https://github.com/openshift/source-to-image/issues/581


Prevent unstable rules from contributing to autoflagging weight

Until a rule has actually been tested against a reasonable number of messages, a 100% TP rate should not add 100 to the autoflagging weight.  A new rule (or ideally, to be really safe, any recently changed rule) should simply add 0 (or perhaps some small value instead of 100) to the autoflagging weight until we have substantial evidence to support it.
Tentatively, don't promote a rule to a position where it contributes to the weight until it has been run against 100 (or 200? or 500?) posts.
Discussion (or more like monologue): http://chat.stackexchange.com/transcript/message/34974667#34974667

Maybe the max. weight of a rule should be limited by the # of posts it ran on (e.g. a rule triggered by 50 posts has a weight of min(50, accuracy %)).

Already a thing - reasons have 0 weight until they've run on at least 20 posts. Threshold is open to debate.

Thanks.  What about edits to existing rules and quarantining those somehow?  I guess that should be a separate request and a fairly substantial effort in its own right anyway.

@tripleee Minor edits won't affect accuracy too much; we can probably rely on the existing system there. Major edits should probably be sent off to a new rule anyway.


Add some gifs or images in the README

I would suggest adding some images or gifs in the README file to better present your package.

Yeah, good idea. Will do soon.


Make project.json mandatory

The project.json file is not mandatory, the plugins add projects without project.json to the graph. But for more configuration, we need to create this file.
I am thinking  about making this file mandatory, and raising an error if the file is messing.
For maven, we can check if project name and artifactId are the same.
We can create a  project.json for the root project in wrapper folder so users can update namedInputs. And like this the maven/gradle root project is different from nx root project.
Create a generator to generate missing  project.json files

Why is it required to have a root Pom.xml? Is this a limitation of the nxgraph api?

For me, maven multi modules works like this :https://spring.io/guides/gs/multi-module/
How about make root pom.xm minimal and move everything to another pom.xm?
With this solution there is no chance to modify it. I can show you this in a GitHub repo.
Also I am making the wrapper optional and you will have less files in the root folder

A few things would need to be added to this root Pom like repositories and the preprocessing plugins like the flatten plugin

But this is only needed by the provider and is not needed by the consumer

Any ETA on this. Should I review something?

If you speak about optional wrapper, this week. If you speak about mandatory project.json it's in draft mode because maybe it will just make the plugin complex

Wrapper is not urgent

@jbadeau your idea about moving the pom.xml is not bad. It's good to isolate maven projects.
I think the best idea is to have a variable : mavenRootDirectory and generate there all maven projects and wrapper if it's not optional. The problem here is you will not merge maven projects with other projects

How’s it going? Do u need any help. We have some large maven repos using your plugins maybe it helps with the design if u see how we work?

@jbadeau for project.json, maybe i will make it mandatory but not as described in this issue. project.json and pom.xml should be in the same folder.
generating maven projects in a subfolder, it's not hard, just i need to choose where to save  mavenRootDirectory, first option inside nx.json or if i cant, i will try to put it in a env.file in root folder
will  close this issue and create a new one. Please comment on the new one

@jbadeau https://github.com/khalilou88/jnxplus/issues/519


Feature Request: option to auto generate profile picture

I love the boringavatar used on pocketbase dashboard, could we have option to autogenerate one of those for each new user record?

I don't think this need to be builtin as you can implement it on your own client-side with whatever library and user identifier you want (id, username, email, name, etc.).