[Question] Blazor Server App example

Hello,
I just found this a few hours ago and currently I'm trying to get this running for Blazor Server App.
I successfully managed to get the loader working and loading the plugin, but the page I'm trying to load in is not available.
Loading classes works fine, but how can I dynamicly hot reload and load the .razor file too?
Thanks in advance and sorry if this might be trivial.

I don’t know. I have not looked at how the internals of Blazor works. This project doesn’t explicitly support Blazor, but it also doesn’t do anything to block you from building your own support for Blazor. I’m closing, however, as supporting Blazor is not something I plan to spend any time doing. If you (or anyone else reading this later) wants to support a library that integrates this project and Blazor, I’d be happy to link to it from the README


Padding is not working on windows platform Windows platform

Platform
Windows
Property
Padding
Version
.net version: NET8
Nuget version: 2.1.0
I notice that when I migrate to net 8 and use version 2.1.0 the padding is not working

This seems to be an issue with the NET8.0 MAUI framework. It was working fine in NET7.0, and I will continue to track this issue.

The issue has been temporarily resolved, please update the version to 2.1.1 ,Thanks


Casm 4350 ut

Internal merge for unit testing - update logic

Please add an entry in CHANGELOG.md summarizing the changes made

@mharding-hpe , its pr for a internal branch, so did not add these things.

Please add an entry in CHANGELOG.md summarizing the changes made

@mharding-hpe , its pr for a internal branch, so did not add these things.

Oh, I see that now. I apologize. That makes sense!


🌐Translate legal pages

Purpose
These 3 files have to be translated to english first:

src/frontend/apps/impress/src/pages/accessibility/index.tsx
src/frontend/apps/impress/src/pages/legal-notice/index.tsx
src/frontend/apps/impress/src/pages/personal-data-cookies/index.tsx

Load frontend dev
If you do make bootstrap, you can then access the frontend on http://localhost:3000.
If you want to load the stack without doing bootstrap, you can do:
make run-frontend-dev

Push / Pull
⚠ crowdin env must be set (env.d/development/crowdin)
To extract new translation and push to Crowdin, you must do:
make frontend-i18n-generate && make crowdin-upload

To pull your translated text:
make crowdin-download && make frontend-i18n-compile

@AntoLC Done! WDYT?
Note that this content should ideally not be in the opensource release and should instead be customisable. The subject is common to all our projects.


fix: set default linebreak for ts files

Thank you very much for the contribution :)

You are welcome!


bro how the hell do you use this

whats supposed to be in the config file in users/home?

@Navoichyk
At first thanks for your interesting in my project, I really appreciate that!
If you already have one of scapy dependencies like Npcap/Winpcap or libpcap, the most straightforward way for you to use my tool is to type commands:
pip install clients-scanner
scanner

in few seconds GUI should start with searching for local network devices. However it may fail at startup in case you don't have any WLAN network, because it looks for this one. But without digging into it, you may try to run above commands, and show the console output if you encounter any errors.
To be honest I tested my code on the limited number of devices/systems, so it may not work out of the box for everyone, but I'll try my best to make it work for newcomers.


fix(plugin-chart-echarts): support forced categorical x-axis

SUMMARY
This PR adds the option to force a chart with a numerical x-axis to categorical. This makes it possible to sort charts that have a numerical x-axis, while still retaining support for numerical x-axis functionality. This should clear up a compatibility issue between previous versions of Superset, where some versions always treated numerical x-axes as categorical, while others always treated them as numerical.
While working on this, I noticed that the Query based datasource was missing the generic data type information that's needed for charts to operate properly. I believe this should resolve some issues we've seen on charts that are using the SQL Lab query as the source.
Note, that I tried to add similar support for temporal x-axes, but that turned out to be very difficult due to how we handle timestamp formats. Therefore, the force option will only be available when the x-axis is numerical, but not for temporal ones. For use cases where similar sorting is needed for temporal charts, I recommend just casting and formatting them to a string based type first.
AFTER
Now there's a new control that makes it possible to force numerical x-axes to categorical (disabled by default):

Note, that if a sorting value had previously been defined, it will set this control to true by default. This is to ensure that charts that had been created on a previous version of Superset, where the x-axis was numeric but were treated as categorical, will work as they were originally intended.
Here we can see that we're able to sort by the metric value if the chart is forced to categorical style:

BEFORE
Previously the sorting control was visible, but didn't do anything if the x-axis was numeric:

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[x] Has associated issue: fixes #26323
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

/testenv up

This is amazing! thank you!

/testenv up

/testenv up

Thank you for the PR @villebro and for nice tests!
I noticed that a numerical chart is rendering as categorical when you navigate from the dashboard to Explore.
https://github.com/apache/superset/assets/70410625/c9cca9d1-f72b-4346-93a3-2ebf4569f8a8
I also noticed it's not possible to drill by when the chart is not categorical. I'm not sure if this is a restriction or if numerical bars could be selected too.
https://github.com/apache/superset/assets/70410625/c2aa4922-f0c3-4766-84f9-51b7fc5aa300

@yousoph @Vitor-Avila @sfirke Could you help testing this too?

I noticed that a numerical chart is rendering as categorical when you navigate from the dashboard to Explore.

Good catch, there must be something in the initialValue hook. I'll look into that now

I will test this but out sick good afternoon so probably not until Monday.

I will test this but out sick this afternoon so probably not until Monday.

I hope you get well soon!

@michael-s-molina the initial value issue should now be fixed. Please check out my new test dashboard: http://<IP_ADDRESS>:8080/superset/dashboard/p/qkWeveYvMXr/

I also noticed it's not possible to drill by when the chart is not categorical. I'm not sure if this is a restriction or if numerical bars could be selected too.

@michael-s-molina I believe this is by design - @kgabryje can probably add more context on this. Maybe something we can consider working in the near future?

@villebro Thanks for tackling the sorting issue. If I didn't forget that the x-axis sorting is using a sorting operator, so the data from backend was sorting ready, I tested this use case in Superset 3.0.2 release, but I can't reproduce it.
https://github.com/apache/superset/assets/2016594/ca14b725-9f80-4c7d-95c7-e8e4a4e10dfb

@michael-s-molina I believe this is by design - @kgabryje can probably add more context on this. Maybe something we can consider working in the near future?

Got it. Thanks for checking.

@michael-s-molina the initial value issue should now be fixed. Please check out my new test dashboard: http://<IP_ADDRESS>:8080/superset/dashboard/p/qkWeveYvMXr/

Thanks for adding this dashboard. It was very helpful!

I also noticed it's not possible to drill by when the chart is not categorical. I'm not sure if this is a restriction or if numerical bars could be selected too.

@michael-s-molina I believe this is by design - @kgabryje can probably add more context on this. Maybe something we can consider working in the near future?

Yes, unfortunately drill by requires a groupby, and the charts from Michael's examples don't have it. Of course a category from categorical x axis SHOULD be considered a dimension to drill by, but currently we don't support it.
Seems like a great opportunity to improve the feature! CC @yousoph

@michael-s-molina thanks for tagging me and apologies for the late response. I just tested creating a chart before this fix and tested the upgrade which successfully fixed the chart!
Thanks @villebro for working on this change.


Update packaging dep to v20.8

Resolves: python-poetry/poetry#3458

[ ] Added tests for changed code.
[ ] Updated documentation for changed code.

This should also resolve issue https://github.com/python-poetry/poetry/issues/3591 now that I understand the problem better.

This should also resolve issue https://github.com/python-poetry/poetry/issues/3591 now that I understand the problem better.

Based on the testing over at https://github.com/python-poetry/poetry/pull/3530, this PR does the trick.

Based on the testing over at https://github.com/python-poetry/poetry/pull/3530, this PR does the trick.

@finswimmer Could you review this?

@finswimmer Could you review this?

Hoping that Packaging 20.9 will be released soon (maybe today!) and that will also add support for Universal wheels on Apple Silicon, so it would be a fantastic upgrade (okay, not quite as important yet as loading any wheel on Intel Big Sur, which was the core of this update, but still and important step forward too!). https://github.com/pypa/packaging/issues/385

Hoping that Packaging 20.9 will be released soon (maybe today!) and that will also add support for Universal wheels on Apple Silicon, so it would be a fantastic upgrade (okay, not quite as important yet as loading any wheel on Intel Big Sur, which was the core of this update, but still and important step forward too!). https://github.com/pypa/packaging/issues/385

Thanks @sdispater!

Thanks @sdispater!

Packaging 20.9 is out, can we get an update? It's needed for proper Apple Silicon support.

Packaging 20.9 is out, can we get an update? It's needed for proper Apple Silicon support.

Any updates on a release? I had just switched my team to poetry before this started and hasn't been a great experience for everyone so we are looking forward to the release.

I'd love to see an update too; not being able to install NumPy on macOS Big Sur is a quite a bummer! I asked for Packaging 20.9 largely so it would be possible to be included in the Poetry 1.1.x series, since 21.0 will drop Python 2.7 and 3.5 (perfect for Poetry 1.2).

Looking forward to a release as well, as I'm sure are lots of other Big Sure users out there :)

Hi @sdispater I would really appreciate if this could be released or are there any reasons not to do so?

Has this fixed the problem for others? I still can't install packages
https://github.com/python-poetry/poetry/issues/3591#issuecomment-778862630


Is there a support for a making a custom api call, rather than directly calling in the google location api?

Use Case: I feel this would be a common use case for many, backend would actually hit the google api's to provide a cummulative result to the UI combining the results from google as well from its own db

Hey there is some discussion around in #525 and a PR that basically covers it in#514.


[Feature]: Hanging indent formatting for parentheses & routine definitions/calls etc.

Description
I would like to be able to format code like this:
PRO hanging_indent_test, a, b, c, d, e, f $
                         f, g, h, keyword = k, keyword2 = k2, $
                         keyword3 = k3
  local_var = k3

instead of this:
PRO hanging_indent_test, a, b, c, d, e, f $
  f, g, h, keyword = k, keyword2 = k2, $
  keyword3 = k3
  local_var = k3

and
  long_var_name = ( b + c + d + e + f $
                    + g + h )

instead of this:
  long_var_name = ( b + c + d + e + f $
    + g + h )

And something similar for structure definitions, e.g.,
  a = { MY_STRUCT, $
        b : 4, $
        c: 5 $
      }

and arrays:
  aaaa = [ 5, 3, 6, $
           7, 8, 8 ]

Why it Matters
I find such statements much more readable with hanging indents:
E.g., the keyword definition keyword3 = k3 gets entirely lost/confused with local variable assignments when formatted as is standard now.
This is the way idlwave-mode for emacs does it which presumably means there is a sizeable subcommunity that's used to it.
This is also the way a mathematician would write an equation (if there is enough space).
Suggested Behavior
See description.
This formatting style should/must probably become an optional choice, so as not to affect codebases using current formatting rules as a surprise. In fact, it may be an idea to have the option be called something along the lines of "emacs idlwave emulation", in case we find other things we miss :)
Alternate Behavior
Implement a directive "no-idl-format" which switches off automatic formatting for the next statement. Maybe also an on/off switch ("idl-format off" vs "idl-format on") to turn off formatting for a specific code section.

In general, I think our goal with formatting is to not go too crazy with options for the style and spacing of your code.
However, I do think this option makes sense, especially if you are working with other languages like Python where this can be a common style for multi-line expressions.
With that being said, let me think about if this would fit into our current implementation or not. This might be a fair amount of work to make sure we handle all of our edge cases for formatting and different tokens that we have to handle, but it could turn out to be easier than that.


404 page error on http://redux-form.com/6.0.2/syncValidation

This is not a major issue, but found this while going through documentation http://redux-form.com/6.0.2/syncValidation throws 404 error.

Which page did you get that URL from? The correct URL should be http://redux-form.com/6.0.2/examples/syncValidation/

Yes.. on http://redux-form.com/6.0.2/examples/simple/  if you click for synchronous validations it lands here


ColorPalette - Align To Grid

Browser
No response
Description
Color Palette off grid by a few pixels

Steps to reproduce

Added sprint 16 if this is ready for review.


Installation Exceptions

Hello,
Running into problems when trying to install - Advice appreciated.

Directory Permissions are 775
drwxrwxr-x. 12 deploy deploy 4096 Apr 21 20:47 grav-admin

NGINX Configuration
server {
    listen 80;
    index index.html index.php;

    root /var/www/grav-admin;
    server_name grav.domain.com;

    location / {
        try_files $uri $uri/ /index.html;
        if (!-e $request_filename){ rewrite ^(.*)$ /index.php last; }
    }

    location ~ \.php$ {
    try_files $uri =404;
    fastcgi_pass unix:/var/run/php-fpm/php-fpm.sock;
    fastcgi_index index.php;
    fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
    include fastcgi_params;
}
}

Env
CentOS Linux release 7.2.1511 (Core)
PHP 5.6.20 (cli) (built: Mar 31 2016 07:17:10)

It looks like you have a problem with your PHP/Apache setup.  PHP is not able to store session data:
https://www.google.com/?ion=1&espv=2#q=open(%2Fvar%2Flib%2Fphp%2Fsession%2F failed permission denied (13)
Google has lots of answers for you, try this one? http://stackoverflow.com/a/6628575

Just incase anyone experiences this, I ran the following and grav is now working
chown -R nginx: /var/lib/php/session


docs: add info about check in time and forcing an update

-update is short for -check_for_update plus -watch_update or whatever the option is, I don't have a CLI in front of me to check. If all you want is for the instance to appear in roller the check option may be better because it won't report failure if there was no update to apply. Either way it is kinda wonky and clearly was only written as a developer tool.

LGTM


password support

[x] adds support for md5 authentication request
[x] adds PostgreSQLPasswordMessage
[x] adds additional comments
[ ] adds MD5 password support
[ ] adds plaintext password support

@Joannis looks like MD5 support needs to be added to vapor/crypto (we implemented this w/ LibreSSL in Vapor 2)

Fixes #7
Fixes #8
Fixes #9


feat!: make compatible with<EMAIL_ADDRESS>

I got close but not close enough, using the branch https://github.com/mkrasnitski/pixels from the PR https://github.com/parasyte/pixels/pull/391 via the patches in cargo.

Blocked by https://github.com/parasyte/pixels/pull/391
Closes #22
Pixels added a lifetime to the struct so we need to add one too.
Not sure if <'win: 'static> is the way to go. Bevy query types want 'static but figured allowing our own lifetime bound by static is better than just static.

I can't figure out the error in src/system.rs.
It says that the window we get on line 33 doesn't have the trait HasWindowHandle.
I believe it should be on there because we've added the feature rwh_06.
Feel free to add to or change this as you wish!

FWIW, https://github.com/parasyte/pixels/pull/391 was merged today.

FWIW, parasyte/pixels#391 was merged today.

Thanks @parasyte! I'll look at getting bevy_pixels working with bevy 0.14 and pixels 0.14.

I haven't yet published a pixels release that supports wgpu 0.19, but I will be glad to if it will unblock this PR.

I haven't yet published a pixels release that supports wgpu 0.19, but I will be glad to if it will unblock this PR.

@parasyte Ahh, so the new release of pixels 0.14 just bumps to wgpu 0.17 while it's the PR you mentioned that brings you to wgpu 0.19 with support for raw-window-handle 0.6 (yet to be included in a release)? I just noticed pixels 0.14 was just released and assumed it was included.
It would be nice to get this into a release, but no rush. More than happy to wait until those changes have been battle tested first.


Problem with initialization of HC711 in C

Hello, I have been tried to deal with this HX711, but I have no success. I am new in Raspberry and I want to know how to do that, How to use the "initHX711" (I have been created variables for clock_pin and data_pin, because I have been used a function that gets some parameters in)
I tried to use "read_sacel.c", but it has so much errors of compilation. I tried to run the debug, but no success again, because hasn't compiled and built. I tried to create the "hx" struct, but again no success. I don't know what is wrong with my code, I don't know which is the syntax error. All older issues are starting from who inits with success, what isn't my case. I already downloaded all libraries as needed and all libraries are included in code. Hx711.h, hx711.c and read_scale.c are opened in another pages for verification of syntax.
This is the function that can't compile:
void init_weight(char gpio_clock, char gpio_data)
{
HX711 hx;
int err = initHX711(&hx, gpio_clock, gpio_data);
if (err)
{
	printf("\n!!! Failed to init HX711 struct !!!\n");
}

}
My Raspberry version: Raspberry 4B
Linux Version: Raspbian GNU/Linux 10 (buster)

Could you please provide the error message from the compiler, to give us a hint what might be wrong?
On February 20, 2020 3:03:18 PM GMT+01:00, Leandro Madureira<EMAIL_ADDRESS>wrote:

Hello, I have been tried to deal with this HX711, but I have no
success. I am new in Raspberry and I want to know how to do that, How
to use the "initHX711" (I have been created variables for clock_pin and
data_pin, because I have been used a function that gets some parameters
in)
I tried to use "read_sacel.c", but it has so much errors of
compilation. I tried to run the debug, but no success again, because
hasn't compiled and built. I tried to create the "hx" struct, but again
no success. I don't know what is wrong with my code, I don't know which
is the syntax error. All older issues are starting from who inits with
success, what isn't my case. I already downloaded all libraries as
needed and all libraries are included in code. Hx711.h, hx711.c and
read_scale.c are opened in another pages for verification of syntax.
This is the function that can't compile:
void init_weight(char gpio_clock, char gpio_data)
{
HX711 hx;
int err = initHX711(&hx, gpio_clock, gpio_data);
if (err)
{
printf("\n!!! Failed to init HX711 struct !!!\n");
}
}
My Raspberry version: Raspberry 4B
Linux Version: Raspbian GNU/Linux 10 (buster)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/gandalf15/HX711/issues/30

Could you please provide the error message from the compiler, to give us a hint what might be wrong?
…
On February 20, 2020 3:03:18 PM GMT+01:00, Leandro Madureira @.***> wrote: Hello, I have been tried to deal with this HX711, but I have no success. I am new in Raspberry and I want to know how to do that, How to use the "initHX711" (I have been created variables for clock_pin and data_pin, because I have been used a function that gets some parameters in) I tried to use "read_sacel.c", but it has so much errors of compilation. I tried to run the debug, but no success again, because hasn't compiled and built. I tried to create the "hx" struct, but again no success. I don't know what is wrong with my code, I don't know which is the syntax error. All older issues are starting from who inits with success, what isn't my case. I already downloaded all libraries as needed and all libraries are included in code. Hx711.h, hx711.c and read_scale.c are opened in another pages for verification of syntax. This is the function that can't compile: void init_weight(char gpio_clock, char gpio_data) { HX711 hx; int err = initHX711(&hx, gpio_clock, gpio_data); if (err) { printf("\n!!! Failed to init HX711 struct !!!\n"); } } My Raspberry version: Raspberry 4B Linux Version: Raspbian GNU/Linux 10 (buster) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #30

Yes, the error message is (I translated from portuguese):
/usr/bin/ld: /tmp/ccOMXwuJ.o: in function "init_weight":
TESTE.c:(.text+0x194): reference not defined to "initHX711"
collect2: error: ld returned 1 exit status
Compilation failed.
The original error message:
/usr/bin/ld: /tmp/ccOMXwuJ.o: na função "iniciar_sensor_peso":
TESTE.c:(.text+0x194): referência não definida para "initHX711"
collect2: error: ld returned 1 exit status
Compilação falhou.

I already inserted -l hx711 and -l gb_common and I had no success (again).

Hi,
Firstly I'm sorry that it took me that long to answer.
The message you posted clearly indicates a linking error. Since the function call to initHX711 looks correct, I guess that maybe you haven't told your linker where to find the function implementation. The implementation is located in hx711.c, respectively hx711.o after compilation. Your linker needs to know where to find hx711.o. Usually this can be adjusted in the project settings of your IDE.
Good luck!

Hi,
Firstly I'm sorry that it took me that long to answer.
The message you posted clearly indicates a linking error. Since the function call to initHX711 looks correct, I guess that maybe you haven't told your linker where to find the function implementation. The implementation is located in hx711.c, respectively hx711.o after compilation. Your linker needs to know where to find hx711.o. Usually this can be adjusted in the project settings of your IDE.
Good luck!

That is the point. I don't know if the call to function is right. I tried to call in different ways, but no success. How do you call in your code, can you show me?


feat(changelog): enhance format for multi-line and reduce commit noise

Motivation

Current changelogs are cluttered with commits noise, and restricted to single-line changelogs
Approach

Indent multi-line changelogs so it renders correctly under its bullet point (done)
Reduce the commit noise to only the short commit hash and the PR it was introduce in (done)
Group changelogs of dependencies under one bullet-point for each dependency (having a bit trouble with, explained below)

Screenshots
Ultimately a changelog could look like the following:

Fix a bug in this package

Add a feature to this package but needs to be explained in
multiple paragraphs
This could also include
code blocks

and also lists:

a1run this cmd

a2
a3

Fix another bug in this package

Bumped due to a bump in `package-utils`

A fix in package-utils

A feature in package-utils

A multi-line feature
in package-utils
because why not?

Performance gains

Bumped due to a bump in `package-macros`

A fix in package-macros

A feature in package-macros

A multi-line feature
in package-macros
because why not?

Performance gains

I think this PR is ready for review. I will fix the tests later after approval of the logic.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_6b65b737-26c4-4a01-89ca-d7ea3b389df2/pull/1 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target_6b65b737-26c4-4a01-89ca-d7ea3b389df2.git

Docs Build status updates of commit f2d6874:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Release_Archive_master_2020-03-19-06-12-14 has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/Release_Archive_master_2020-03-19-06-12-14

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Compatibility Symfony 5

Hi, we can't use it with Symfony 5.

Is it possible to make this possible?

Hi @hugoguitton-x, just added Symfony 5 support. Please check, thank you!

Hi @oliverschloebe thanks for the modification. I can install it thanks to composer, however I can't use it with Symfony apparently.
I have the following message: "DiscordPHP will not run on a webserver. Please use PHP CLI to run a DiscordPHP bot."

I have the following message: "DiscordPHP will not run on a webserver. Please use PHP CLI to run a DiscordPHP bot."

That is because you can't run DiscordPHP in the browser. You have to run it using CLI.

Okay.  This code works fine !
    $discord = new Discord([
        'token' => 'bot-token',
    ]);

    $discord->on('ready', function ($discord) {
        echo "Bot is ready!", PHP_EOL;

        // Listen for messages.
        $discord->on('message', function ($message, $discord) {
            echo "{$message->author->username}: {$message->content}",PHP_EOL;
        });
    });

$discord->run();

No worries! Glad you got it working. 👍🏻


Resolved [Werror=unused_result]  All warnings treated as errors

Thanks a lot for the PR!
I made a few small comments. If you can add a new commit fixing them, we'll merge your PR.


node_modules folder imported with npm

Hi, when this functionality is imported with npm, the subfolder node_modules of your project is imported too (with @angular package) so it can't compile until the folder is deleted.
Additionally there is a link in npm package web page what doesn't redirect to this page.
Thanks
Juanjo

The package was updated. Please install npm i<EMAIL_ADDRESS>


Updates to the code

band occupancies are now searched using bisection method and in parallel
allgather interface is unified: count and offset are provided in the same order
[WIP] documentation to the occupancy matrix

bors try

bors try

This is strange. I can run the tests on Daint manually and all of them pass.

Hm, it seems to be reproducible; fails also after restarting those band parallel tests by hand, just on test 20

bors try


[FIX] Replace deprecated calls in atob and btoa

Description
Resolves #799.
PR Type

[x] Snippets, Tests & Tags (new snippets, updated snippets, re-tagging of snippets, added/updated tests)
[ ] Scripts & Website & Meta (anything related to files in the scripts folder, how the repository's automated procedures work and the website)
[ ] Glossary & Secondary Features (anything related to the glossary, such as new or updated terms or other secondary features)
[ ] General, Typos, Misc. & Meta (everything else, typos, general stuff and meta files in the repository - e.g. the issue template)

Guidelines

[x] I have read the guidelines in the CONTRIBUTING document.

I noticed some inconstancy with the new placements

@skatcat31, you're right. Sorry for this. I made a fix on my branch, but I don't know if and how I could include this new commit in current (closed) pull request: https://github.com/hckr/30-seconds-of-code/commit/645cda1b9dd4d3d0546ad8c51bf3498eead65808

It's no mess, but thank you for fixing it so quickly with your own initiative. That's always a good quality to have. Feedback back and forth is a quality that developers need to thrive


Add Hardware Design Documentation

Add the basic Hardware Design document that will give overview as to how the hardware for the device will function

Hardware Design document created for draft version 1.0. To be updated


Tidy Manifest

For the MANIFEST.in, we can fix it in a follow-up. It needs more clean-up than just this .txt, and also do we include the data for the test files or not?
Let me know if the previous comment answers your question for the CAR issue.
Originally posted by @mscheltienne in https://github.com/jacobf18/iclabel-python/issues/18#issuecomment-1111113074
We should tighten up the MANIFEST file to remove any data files, and include only the necessary python and text files for a distribution.

To be done after iclabel submodule is added since it will impact paths. c.f. #21


Capybara theme error page fails when server is down

Current behavior
If the API is down, the capybara error page tries to do api requests for the menu, and fails if the API isn't running.
Expected behavior
A proper error page, probably without the menu.
Steps to reproduce the issue
Start vsf with capybara, kill the api server.
Repository
Can you handle fixing this bug by yourself?

[ ] YES
[x] NO

Which Release Cycle state this refers to? Info for developer.
Pick one option.

[x] This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.

Environment details

Browser: Firefox 75
OS: Windows 10
Node: 13.7
Code Version: head of both

Can you please post the issue to https://github.com/DivanteLtd/vsf-capybara so the team will take care?


issue fixed #1484 | Medium Issue 2 (C++)

Pull Request Type
What kind of change does this PR introduce?
[ ] Solved an issue/task
What is the current behavior?

Issue Number: https://github.com/fork-commit-merge/fork-commit-merge/issues/1484
What is the new behavior?

C++ program that reads a text file and counts the frequency of each word in the file.

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out our forkcommitmerge.io website repository. The repository contain real issues that you can help to resolve or create some of your own if you see any bugs or want to add new features to the site, etc. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!


Add WAF ACL to Cognito User Pool

Feature or Bugfix

Feature

Detail

Add WAF ACL to Cognito

Relates

Security
Please answer the questions below briefly where applicable, or write N/A. Based on
OWASP 10.

Does this PR introduce or modify any input fields or queries - this includes
fetching data from storage outside the application (e.g. a database, an S3 bucket)?

Is the input sanitized?
What precautions are you taking before deserializing the data you consume?
Is injection prevented by parametrizing queries?
Have you ensured no eval or similar functions are used?

Does this PR introduce any functionality or component that requires authorization?

How have you ensured it respects the existing AuthN/AuthZ mechanisms?
Are you logging failed auth attempts?

Are you using or adding any cryptographic features?

Do you use a standard proven implementations?
Are the used keys controlled by the customer? Where are they stored?

Are you introducing any new policies/roles/users?

Have you used the least-privilege principle? How?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Overall looks good! Testing in AWS with custom_waf_rules:

[ ] CICD Pipeline Succeeds
[ ] Added WAF Rules to Cognito User Pool (no updates to Cloudfront or API GW)
[ ] Log In, Log Out, and Access Data.all UI

I created another issue for the custom_waf_rules : https://github.com/data-dot-all/dataall/issues/995


Application not starting with orientdb (plocal mode) after application crash

After crash of our application that uses orientdb in plocal mode and we restarted it, the below log and exception come in nohup.out and it does not start
https://www.dropbox.com/s/67jpm7znckawvz6/nohup.out-application-not-starting-after-crash.txt?dl=0

What release?

Orientdb 2.0.1
On 31-Jan-2015 11:39 PM, "Luca Garulli"<EMAIL_ADDRESS>wrote:

What release?
—
Reply to this email directly or view it on GitHub
https://github.com/orientechnologies/orientdb/issues/3507#issuecomment-72328720
.

Hm,
That is bad.
I think you started and stopped it using the same version ?
Do you have this db ?
On Sun, Feb 1, 2015 at 4:59 AM, K Adithyan<EMAIL_ADDRESS>wrote:

Orientdb 2.0.1
On 31-Jan-2015 11:39 PM, "Luca Garulli"<EMAIL_ADDRESS>wrote:

What release?
—
Reply to this email directly or view it on GitHub
<
https://github.com/orientechnologies/orientdb/issues/3507#issuecomment-72328720>

.

—
Reply to this email directly or view it on GitHub
https://github.com/orientechnologies/orientdb/issues/3507#issuecomment-72348821
.

--
Best regards,
Andrey Lomakin.

Yes. I have the db. Can you tell which files you want. I will upload....

I think wal files would be enough.
On Mon, Feb 2, 2015 at 2:25 PM, K Adithyan<EMAIL_ADDRESS>wrote:

Yes. I have the db. Can you tell which files you want. I will upload....
—
Reply to this email directly or view it on GitHub
https://github.com/orientechnologies/orientdb/issues/3507#issuecomment-72449597
.

--
Best regards,
Andrey Lomakin.

Pls find the below the URL of full DB
url : http://nmsworks.co.in/ORIENTDB/rcainv.tar.bz2
login : orientdb
pwd : !@QWnms$
Pls update after you downloaded this... I will have to remove it from our server

WAL array out of bounds is fixed in 2.0.4 when we fixed durability issue.

WAL array out of bounds is fixed in 2.0.4 when we fixed durability issue.


Fix missing collabrative repos

As title. will fix #2365

LGTM

Also will fix #2369

make L-G-T-M work


Width of demo content is not correct

In the auto complete sample (customizing templates for example), the width of the autocomplete control is not equal to the width the autocomplete has in the telerik sample. Not sure why
ours

Telerik's

@adriatic can you check this out?

It has to be the consequence of our a bit inconsistent use of KendoUI "classes" (css files)

Can't find the cause though, as the divs are correct


KIM supports flag for making the auditlog-configuration mandatory

Description
It's not allowed to handover a productive sKR cluster to customers without a properly configured auditlog. But this requirement is only for productive SKR clusters. For clusters created on our KCP DEV or STAGE landscape the usage of an auditlog instance is optional.
We will establish a configuration flag in KIM, which indicates whether the auditlog configuration is mandatory for created clusters. If it's mandatory and no auditlog instance could be found for the region of the requested cluster, the cluster creation process has to be stopped and status of the corresponding RuntimeCR has to be set to ERROR.
If the flag indicates that the auditlog configuration is optional, the cluster creation process will try to find an appropriate auditlog instance in the log. But if no auditlog instance is configured for the region of the requested cluster, the cluster creation process continues. The status of the RuntimeCR is not influenced by the missing auditlog configuration.
AC:

[x] Establish a configuration flag (boolean) which indicates whether a proper auditlog configuration is mandatory for created SKR clusters.

[x] If flag indicates a mandatory auditlog configuration but no auditlog configuration could be found for the cluster region, the status of the corresponding RuntimeCR is set to ERROR and the cluster creation process stops
[x] If the indicates an optional auditlog configuration, the cluster creation process continues and the status of the RuntimeCR is not influenced.

Reasons
Ensure that productuve SKR clusters have always an auditlog instance configured.
Attachments

Implemented in #367, for example output please see this

The #367 is now merge with this feature. We can close this issue as resolved.


Proposal: window activity API

Motivation
Many implementors who manage remote resources, like Codespaces and Azure Functions, want to know if the user has been inactive for a while in order to suspend resources. Currently, they just listen to a ton of events and try to guess when the user is active. In effect:
vscode.workspace.onDidChangeTextDocument((e) => {
    this.onActivity();
}),
vscode.workspace.onDidOpenTextDocument((e) => {
    this.onActivity();
}),
vscode.workspace.onDidCloseTextDocument((e) => {
    this.onActivity();
}),
vscode.workspace.onDidSaveTextDocument((e) => {
    this.onActivity();
}),
// ...

This is still partial, since there is some activity (such as work in custom editors) which is not surfaced through these events at all. VS Code itself could provide a much simpler and more reliable approach.
Proposal
A new property to the WindowState:
export interface WindowState {
	/**
	 * Indicates whether the window has been interacted with recently. This will
	 * change immediately on activity, or after a short time of user inactivity.
	 */
	readonly active: boolean;

In core, we would set up a global handler for mouse movements and keystrokes that can be used to drive the handler logic.
Addition from standup discussion: if a notebook cell is running, we would never consider the window to be inactive. Probably have some register*able API in core for different components to hook into.
Alternatives
One alternative is what extensions do today, which is flawed.
Another proposed approach, which is mainly just useful in the remote case, is monitoring flowing bytes to the remote and developing a heuristic based off that. But this is very finicky and similarly doesn't capture activity which may only interact with the local editor or extension host.

:+1:

fyi for an alternative: https://github.com/microsoft/vscode/issues/134795

From discussion, it would make sense to have an active: boolean on the existing WindowState. Extensions can do what they want as a result of change to that, such as setting a timeout that will dispose resources

Yes. Generally it's helpful to see some consumers of it, so if you've used it and like it, dislike it, or ran into problems, please let us know!

Is this still on track to be finalized for July release 🙏 ?

Not currently, I haven't gotten any feedback on it yet, and it's likely to stay in proposed until I do

Thumbs up for stabilizing the API! I created a simple extension using this API to monitor user activity and update a heartbeat file. This allows for automatic shutdown of idle remote VMs, and it appears to function effectively. Only the problem is that I can not use the proposed API without Insider version :rofl:

Another thumbs up here! This works well for our use-case and we'd be happy to help get this stabilized.

This'll be finalized in our next release


opencv error(related to nppi) when docker build

I'm trying to build an inference-server docker image, but when docker build Dockerfile.tensorrt_server, i got this error. please help.
-- Configuring incomplete, errors occurred!
See also "/opencv/CMakeFiles/CMakeOutput.log".
See also "/opencv/CMakeFiles/CMakeError.log".
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
CUDA_nppi_LIBRARY (ADVANCED)
    linked by target "opencv_cudev" in directory /opencv/modules/cudev
    linked by target "opencv_cudev" in directory /opencv/modules/cudev
    linked by target "opencv_perf_core" in directory /opencv/modules/core
    linked by target "opencv_core" in directory /opencv/modules/core
    linked by target "opencv_core" in directory /opencv/modules/core
    linked by target "opencv_perf_cudaarithm" in directory /opencv/modules/cudaarithm
    linked by target "opencv_cudaarithm" in directory /opencv/modules/cudaarithm
    linked by target "opencv_cudaarithm" in directory /opencv/modules/cudaarithm
    linked by target "opencv_imgproc" in directory /opencv/modules/imgproc
    linked by target "opencv_imgproc" in directory /opencv/modules/imgproc
    linked by target "opencv_perf_imgproc" in directory /opencv/modules/imgproc
    linked by target "opencv_perf_video" in directory /opencv/modules/video
    linked by target "opencv_video" in directory /opencv/modules/video
    linked by target "opencv_video" in directory /opencv/modules/video
    linked by target "opencv_perf_cudafilters" in directory /opencv/modules/cudafilters
    linked by target "opencv_cudafilters" in directory /opencv/modules/cudafilters
    linked by target "opencv_cudafilters" in directory /opencv/modules/cudafilters
    linked by target "opencv_perf_cudaimgproc" in directory /opencv/modules/cudaimgproc
    linked by target "opencv_cudaimgproc" in directory /opencv/modules/cudaimgproc
    linked by target "opencv_cudaimgproc" in directory /opencv/modules/cudaimgproc
    linked by target "opencv_perf_cudawarping" in directory /opencv/modules/cudawarping
    linked by target "opencv_cudawarping" in directory /opencv/modules/cudawarping
    linked by target "opencv_cudawarping" in directory /opencv/modules/cudawarping
    linked by target "opencv_perf_imgcodecs" in directory /opencv/modules/imgcodecs
    linked by target "opencv_imgcodecs" in directory /opencv/modules/imgcodecs
    linked by target "opencv_imgcodecs" in directory /opencv/modules/imgcodecs
    linked by target "opencv_perf_videoio" in directory /opencv/modules/videoio
    linked by target "opencv_videoio" in directory /opencv/modules/videoio
    linked by target "opencv_videoio" in directory /opencv/modules/videoio
    linked by target "opencv_perf_cudacodec" in directory /opencv/modules/cudacodec
    linked by target "opencv_cudacodec" in directory /opencv/modules/cudacodec
    linked by target "opencv_cudacodec" in directory /opencv/modules/cudacodec
    linked by target "opencv_highgui" in directory /opencv/modules/highgui
    linked by target "opencv_highgui" in directory /opencv/modules/highgui
    linked by target "opencv_ts" in directory /opencv/modules/ts
    linked by target "opencv_ts" in directory /opencv/modules/ts

it was version issue.

@wonjin911 what did you change to fix it?

I found out that I had to use cuda 8.0 to fix the problem.


NSCharacterSet.ExceptionTests fails on OSX

This was a new test added recently.
[ RUN      ] NSCharacterSet.ExceptionTests
NSCharacterSetTests.m:228: Failure
Failed
[  FAILED  ] NSCharacterSet.ExceptionTests (0 ms)

@MSFTFox, this looks like bug introduced by 0bc4993f4d52f9fa53c0fb0ea711b4a388dab4f3, please take a look.


Document wordng

This paragraph could be worded better:
Administrators can secure and further control these Azure AD registered devices using Mobile Device Management (MDM) tools like Microsoft Intune
to
Administrators can further control these Azure AD registered devices by enrolling the device(s) into Mobile Device Management (MDM) tools like Microsoft Intune

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

ID: 8b5b4ad9-f729-c381-3a69-8aa0daf0b89f
Version Independent ID: ef468de3-24e5-52be-1984-b5ab4361b331
Content: What are Azure AD registered devices? - Microsoft Entra
Content Source: articles/active-directory/devices/concept-azure-ad-register.md
Service: active-directory
Sub-service: devices
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@danwdavey
Thanks for reporting this! We have created a PR for this issue and the changes should go live soon.


Publish the Event Type inside the meta data for Authentication and Session event publishers.

Describe the improvement
Publish the EventType inside the metadata for the Authentication and Session event publishers. ELK integration and other third-party integrations can be benefitted from this.
Additional context
Having the EventType inside the payload itself can help to prevent,

Custom header param for Event Type in HTTP adapter.
Issues with identifying the Event Type when Docker log publishing to ELK via LOGGER event adapter.

Event stream configuration should be like,
..."metaData": [
{
"name": "tenantId",
"type": "INT"
},
{
"name": "eventType",
"type": "STRING"
}
],
"payloadData": [
{
"name": "contextId",
"type": "STRING"
}...

We can introduce this custom header by changing the eventpublisher.xml
<eventPublisher name="LoggerOutputEventAdapter" statistics="disable" trace="disable" xmlns="http://wso2.org/carbon/eventpublisher">
  ....................
  <to eventAdapterType="logger">
    <property name="uniqueId">log_id</property>
  </to>
</eventPublisher>

Docker integration has an issue due to Docker log appends timestamps as prefix to each line and this can be handled on docker side.

We can introduce this custom header by changing the eventpublisher.xml
<eventPublisher name="LoggerOutputEventAdapter" statistics="disable" trace="disable" xmlns="http://wso2.org/carbon/eventpublisher">
  ....................
  <to eventAdapterType="logger">
    <property name="uniqueId">log_id</property>
  </to>
</eventPublisher>

Docker integration has an issue due to Docker log appends timestamps as prefix to each line and this can be handled on docker side.


International Designators are not handled properly with analyst objects

TLE with catalog numbers in the 80,000 range do not import because tle_util.py is expecting a launch number / launch piece.

Closed by PR https://github.com/consensys-space/trusat-orbit/pull/19


Switch Mac / MacPosts Bash Completion .bash_profile content

File: compose/completion.md, CC @londoncalling
It looks like the statements to add to .bash_profile are reversed for 'Bash' and 'MacPorts Bash Completion'.  Brew is a mac command and not found on linux distros.  I get this error when I try the docs as written on my ubuntu 16.0.4 system:
source .bash_profile
No command 'brew' found, did you mean:
Command 'brec' from package 'bplay' (universe)
Command 'qbrew' from package 'qbrew' (universe)

@shin- @dnephin  @mstanleyjones Can you guys take a look at this? I cannot find anything wrong with the referenced docs topic statements. Am I missing something?

@londoncalling In the Bash section, the part after the curl command only applies to Mac environments (brew doesn't exist on Linux), but it isn't really clear when reading the document.


feat: CVEarlyStopping

Alright, another big one.
Major feature was to implement CVEarlyStopping. This will need to be documented once the optimization documentation gets updated. There also needs to be some default variants select-able by keyword but for now that's the subject of experimentation.

class CVEarlyStopper:
    def __init__(self, metric: Metric, threshold: float):
        super().__init__()
        self.threshold = threshold
        self.metric = metric

    def update(self, report: Trial.Report) -> None:
        pass # Normally you would update w.r.t. a finished trial

    def should_stop(self, info: CVEvaluation.FoldInfo) -> bool:
        return info.scores[self.metric.name] < self.threshold

metric = Metric("accuracy", minimize=False)
evaluator = CVEvaluation(_X, _y)
early_stopper = CVEarlyStopper(metric=metric, threshold=0.8)

history = mlp_classifier.optimize(
    target=evaluator.fn,
    metric=metric,
    on_trial_exception="continue",  # Seems required to prevent early stopping raising

	# The primary job of the plugin is to establish a comm link between the worker and
	# the master process and use the class above to handle what to do.
   	plugins=[evaluator.cv_early_stopping_plugin(strategy=early_stopper)]
)

There were some larger updates that needed to be done to enable this, namely:

This is implemented as a Comm.Plugin such that the worker process can communicate with the main process, where the CVEarlyStopper lives.
The communication through Comm relies on the worker request()'ing whether it should stop and the main process msg.respond(should_stop)'ing on what to do.
To shield the user from having to know about the details of how this is implemented, we would rather they implement a simple function and use it's return value to handle all of this.

To illustrate the more explicit callback method, the above way of doing things is more or less equivalent to the following:
scheduler = Scheduler.with_processes(1)
evaluator = CVEvaluation(_X, _y)
metric = Metric("accuracy", minimize=False)

# Notably **nothing** passed in to `cv_early_stopping_plugin()` now, nothing will
# get called if we don't listen to the `@fold-evaluated` event.
task = scheduler.task(evaluator.fn, plugins=[evaluator.cv_early_stopping_plugin())

# Method one, listen to the `@fold-evaluated` callback and return what to do

@task.on("fold-evaluated")
def should_stop(self, info: CVEvaluation.FoldInfo) -> bool:
    return info.scores[metric.name] < 0.8

# Method two, this explicitly uses the `Comm` and `Msg` that happens underneath the hood.
# This is what `cv_early_stopping_plugin` is doing using the users object.

@task.on("comm-request")
def should_stop_2(msg: Msg.Data) -> None:
    fold_info: CVEvaluation.FoldInfo = msg.data
    if info.scores[metric.name] < 0.8:
        msg.respond(True)
    else:
    	msg.respond(False)

history = mlp_classifier.optimize(
    target=task,
    metric=metric,
    on_trial_exception="continue",
    scheduler=scheduler,
)

The notable change was that the callback of @task.on("fold-evaluated") returned a value, shielding the user from the Comm implementation detail. This required updating the Event system to allow for returned values from handlers, necessitating the updated signature of all existing events in amltk. Hence a lot of changes.

Last few changes were around code simplification while I was going through implementing this.

The concept of an Evaluator as something more than just a callable function was removed as there was little benefit seen while implementing this. It would help us shove more behavior into pipeline.optimize but for now, we should not hide people from the other parts of AMLTK which provides a lot more utility and customization, not afforded by just parameters to a function. (Maybe we revisit this at some point but it helps reduce maint. complexity)

The @events for the Scheduler and Task all had strings such as "on_result" while things like the Comm.Plugin had events like "comm-message". These were unified more to use hyphens ("-") and to remove the "on" part such that user code reads nicer.

# Before
@task.on("on_result")
def f(...): ...

@task.on("on_future_submitted")
def f(...): ...

# After
@task.on("result")
def f(...): ...

@task.on("future-submitted")
def f(...): ...

# Note comm message using hyphens
@task.on("comm-message")
def f(...): ...

This is backwards breaking, but given we advertise using task.on_result as a shorthand that should work the same, I'm okay with making the breaking change sooner rather than later. I think we should still advertise the on_<event> where it's possible as it provides a level of type safety we just can't do with strings.

The requirement of copy() for plugins is hard to meet for stateful plugins. While nice in principal, this was all done to support task.copy(). In all my use of the library so far, I've never once needed this feature. Remove for now.

Metric.compare(v1, v2) for knowing if a value is Metric.Comparison.EQUAL/WORSE/BETTER to not have to constantly check if a metric is minimize or not. This also allows match statements which are a bit more explicit in terms of behaviour routing and allow us to recommend this as public API for a Metric, hiding details behind curtains.

Docs are failing and rightfully slow, I'll update them soonish

@LennartPurucker Implemented changes to address your comments.


[WIP] Initial work on introducing a special subtree for certain RBAC features.

https://bugzilla.redhat.com/show_bug.cgi?id=1247375
For @h-kataria to take over.

I moved the tree building code into a separate class
Created a special top-level item
Put the named items under that special class

@martinpovolny can you give me permissions to push my changes on to your branch.

@h-kataria : would not it be simpler if you just checkout this branch and publish you own? I then close this PR as replaced by yours.

@h-kataria : push access granted, do it as prefer

@martinpovolny ok, i will check out this branch to use your commit as base and then apply my work on top of it and create my own PR.

@martinpovolny created https://github.com/ManageIQ/manageiq/pull/4063 to address the issue in a new PR with further changes.


Special characters in username

OS: Windows 10
Version v1.0.0
From Slack:
Arizen doesn't like when we put special char in the usernam. I've put "Cédric" for username but it fail when login so I had to create new wallet with cedzzz as username. Now it works.

Tested on Windows 7
Version v1.0.0
Issue confirmed. Special characters are not accepted (neither if it is Wolverine :-D). Please, see picture bellow:

Fixed in 9d25f24b

closed


This is running on c92a3017017dfa31241dec13dc6a1479090318d0/1.8.0-dev/Modified/DEBUG

It seems because of the header to be added (with append = true/default) is included in the StaticLookupTable.
My proposal will be skipping adding an request_headers_to_add entry (HeaderValueOption) when the entry is "static header" and append = true.
https://github.com/dio/envoy/commit/efe1e93cfda1cef2f9519035cc6e1a5bf729274e

Yeah, I bumped into this recently while writing a fuzzer for HeaderMapImpl. I think we should support this for consistency of the request_headers_to_add etc. interface. @alyssawilk

I find the behavior of tweaking headers in the StaticLookupTable vs not super confusing - I'm glad the assert caught the fact we were dropping headers on the floor and I'd like to see a better workaround than we have today.
addReferenceKey has never handled append if there's a preexisting key.  I considered fixing that when I fixed the other append functions to work better with inline headers (#3560) but my concern was if anyone really relied on the key being a reference that'd break the contract with them.  Basically if you added "x-foo-header: bar" and then changed the backing store of x-foo-header that might not work "as expected".  That said I'd be happy to disallow that behavior as risky anyway I just think we should make it clear what's going on.  Maybe we can just change the name to indicate the function is using a static const backing store so we should avoid copies where we can but it's Ok to not use the literal string in the header entry?

I find the behavior of tweaking headers in the StaticLookupTable vs not super confusing - I'm glad the assert caught the fact we were dropping headers on the floor and I'd like to see a better workaround than we have today.

+1 it would be great to continue to clean this up.

Maybe we can just change the name to indicate the function is using a static const backing store so we should avoid copies where we can but it's Ok to not use the literal string in the header entry?

Sorry can you rephrase? Didn't fully grok.

This showed up again under fuzzing at https://oss-fuzz.com/v2/testcase-detail/5107723602493440?noredirect=1.
@alyssawilk (in the absence of @mattklein123); wondering if we can brainstorm some reasonable solution here. Can we just use https://cs.corp.google.com/piper///depot/google3/third_party/envoy/src/source/common/http/header_map_impl.cc?rcl=209298018&g=0&l=267 to append to the existing entry?
I notice your objection above, but I think folks should not be holding a reference to the naked string, they should instead always go via the HeaderEntry (or maybe HeaderString).
I'm willing to take this on if we have a design consensus.

Sure, I totally back changing all the header ByReference functions to comment that the "ByReference" is best effort, and that underlying string may be copied for multi-value/multi-line headers.  I think we'd have to look carefully at the comments for how the existing API works and make sure it's all up to date, and consider it a super-high-risk change and have Lyft (and any others that opt-in) canary carefully to make sure nothing breaks.  We know from a small bug in some of the earlier "append to inline headers" fixes that existing Envoy users are dropping some headers on the floor to the existing implementation, so the change will likely cause some changes to what upstream sees.
I think we have to make some change of this sort because it's entirely possible we're failing to proxy existing headers.  These will be changes for the better, just potentially dangerous changes for the better :-)
@ccaraman @junr03

OK, I will take this one on.


chore: bdd-nh-1584717548 to 0.0.1

chore: Promote bdd-nh-1584717548 to version 0.0.1

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

Needs approval from an approver in each of these files:

OWNERS

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


Make Benchmark Tests Run as part of CI for Pull-Requests

What is your idea?
Right now its kind of annoying to ask for benchmark results as part of each pull-requests. Ideally, we'd have benchmarks run as part of the PR or on-command whenever someone wants it before merging a change.
This would have made the optimization PRs like https://github.com/aws/event-ruler/pull/37 and https://github.com/aws/event-ruler/pull/39 easier to merge in. Also, it reduces one more friction point for any future pull-requests.
Would you be willing to make the change?
Maybe
Additional Context
When we get this working, we should make sure benchmarks are only ever run as PR and not part of regular builds (where something running for 6~7 mins is painfully slow for development cycles).

I can help with the GHA part of this (including a small tweak to cancel long-running jobs such as benchmarks when new commits are pushed to a PR. Since I'm not an expert in Java benchmarking and the tooling, e.g. which output to use, creating +/- comparisons, etc. it would be great if someone could point me in the right direction so I can create the PR.

Hmm, I agree in principle but I think people shouldn't send us PRs that have big performance penalties because that will never be OK for Ruler. So I'd like to have some mechanism to provide an incentive to make this clear to a contributor. Maybe it's enough to write it into our submission guidelines or template?

The default template does ask for benchmarks which we can keep as it. The action here should help ensure as folks push additional updates to their PR, the github actions are good enough.
On steps to implement this, I suspect it'll be like

use maven surefire plugin to run a specific test https://maven.apache.org/surefire/maven-surefire-plugin/examples/single-test.html

This is the java class that needs to be run https://github.com/aws/event-ruler/blob/main/src/test/software/amazon/event/ruler/Benchmarks.java

update https://github.com/aws/event-ruler/blob/main/.github/workflows/CI.yml to setup automation

if there's any dependency changes required it'll be within https://github.com/aws/event-ruler/blob/main/pom.xml with this new configuration

closed by https://github.com/aws/event-ruler/pull/178


Add category filter for skills

Reference PR: https://github.com/hugo-toha/toha/pull/979

Thank you @joyao


[APPLE]Metal/bgfx concurrency with renderAutomatically off

I'm trying ValidationTests on Mac.
With renderAutomatically on, everything works as expected.
When it's off, I do the rendering in the MTKView delegate, it works fine for some scenes and then it crashes.
The callstacks I get for main and JS threads look like this:

Basically, a shader is created on the JS thread while the UI thread responsible for rendering is decoding and uploading a texture. It looks like both threads are accessing Metal resources which leads to a crash.
My guess is to use a rendering encode in the JS thread to not have direct access to graphic API.
What's your thoughts @syntheticmagus ?

I think this issue can be closed. Do you confirm @bghgary @syntheticmagus @ryantrem  ?

This shouldn't be an issue anymore.

Closing.


Add post about Dr. Brunswicker's affiliation with NICO!

Dr. Brunswicker has recently become affiliated with Northwestern's NICO. Write a short post about the affiliation and what will come from it.
Needed:

Information about the affiliation
Aspirations with the connection

https://www.nico.northwestern.edu/people/visiting-scholars.html


Thorium contains possible malware/trojan virus?

OS: [Windows 11]
Thorium Version [e.g.M117.0.5938.157] AVX2

Problem
Windows 11 Windows security has flagged thorium as a threat and instantly removed quarantined it.
Win32/DefenseEvasion.A!ml - was flagged as a trojan
Win32/Bearfoos.A!ml - was flagged as a trojan
I have been using Thorium for many months now to almost a year and this is pretty concerning to a loyal user. Hoping to get some explanation from the devs as to what this is and what this means. Have done my fair share of research on both of these "trojans" and from what im reading it, it is infact a virus/trojan but I have also read that there are some false positives with other programs in relation.

Hoping to get some explaination from the devs because this is a worrying concern. Will be uinstalling for the time being with the threat removed.

Got the same thing just today, is very concerning, I installed AVX2 version from the mini-installer, since I did not compiled it by myself I'm kinda worry about it, I guess is best to use another browser while this gets resolved.

The same issue is already reported in Thorium-Win repo or Thorium-AVX2 repo, mark this issue as duplicate

found 1 threat last week today 3 threats
|Name|Type|Description|ID|Hash|
Gen:Variant.Lazy.509733, file, C:\Program Files\Thorium\Application\chrome_proxy.exe, 0, cf158e44c1eb49bda56ac5d17d499d39
Gen:Variant.Lazy.509733, file, C:\Program Files\Thorium\Application\122.0.6261.132\chrome_pwa_launcher.exe, 0, 8ab84f3beccd6da83c6e4f13eb625378
Gen:Variant.Lazy.510014, file, C:\Program Files\Thorium\Application\122.0.6261.132\notification_helper.exe, 0, 7ae04416d23ad20f5836b1fe0b255c8a
?   halp

Microsoft has cleared the false positive
`
Analyst comments:
At this time, the submitted files do not meet our criteria for malware or potentially unwanted applications. The detection has been removed. Please follow the steps below to clear cached detections and obtain the latest malware definitions.
Open command prompt as administrator and change directory to c:\Program Files\Windows Defender
Run “MpCmdRun.exe -removedefinitions -dynamicsignatures”
Run "MpCmdRun.exe -SignatureUpdate"
Alternatively, the latest definition is available for download here: https://docs.microsoft.com/microsoft-365/security/defender-endpoint/manage-updates-baselines-microsoft-defender-antivirus
`
@alsdfjldafsjalsfjk


ElasticSearch 7.x support

I upgraded my Elasticsearch installation to 7.0.0 and since then elastalert is giving errors related to "[_source_include] -> did you mean any of [_source_includes, _source_excludes]", which I assume is due to "Remove deprecated url parameters _source_include and _source_exclude #35097 (issues: #22792, #33475)" (https://www.elastic.co/guide/en/elasticsearch/reference/7.0/release-notes-7.0.0.html)
Is there in plan to make Elastalert compatible with ElasticSearch 7.0.0 anytime soon?

I've currently got a pull request trying to resolve this issue https://github.com/Yelp/elastalert/pull/2194 . We are currently running this branch against our ES7.0-beta1 server. If the change is accepted into the main project is unknown

Same problem here. Worked nicely before. I hope it will be merged soon, else i have to downgrade or change component for alerts.
best regards.

Are there any updates on using elastalert on elastic 7.0?

Hi!
Is there any type of workaround? I couldn't postpone the upgrade, but the alert is pretty important for me :(

Try installing elastalert==0.2.0b2. I've just merged in a branch for ES7 support, but it's still under the beta releases as I've not extensively tested it.

I've tested the version 0.2.0b2 but unfortunatly. I'm still getting the error contains unrecognized parameter: [_source_include] -> did you mean any of [_source_includes, _source_excludes]?')"
I have been using the bitsensor/elastalert dockerfile to build an new image. Any other ideas?

@jbecker94 Can you provide more information? In order to track down a possible bug we need to know which version of Elasticsearch you're running  against so we can replicate this. Just to make sure can you compare the elastalert.py file in the docker image against the same file in tag 0.2.0b2? The complete stack trace would also be of benefit to us since we get more information of the origins of this error.

@matsgoran I have done a little bit more troubleshooting and it is now working using the follwing commands according to bitsensor:
git clone https://github.com/bitsensor/elastalert.git && cd elastalert make build v=v0.2.0b2
the only thing which isn't working is the elastalert-test-rule command. I'm not sure if this is an issue with the docker-container or the version. I used the following commands to test my rule which works under 0.1.39 but not using 0.2.0b2.
 sudo docker exec -it elastalert sh cd .. cd elastalert elastalert-test-rule rules/my-super-rule.yaml
This respond in the following stackstrace:
Traceback (most recent call last):   File "/usr/bin/elastalert-test-rule", line 11, in <module>     load_entry_point('elastalert==0.2.0b2', 'console_scripts', 'elastalert-test-rule')()   File "/usr/lib/python2.7/site-packages/elastalert-0.2.0b2-py2.7.egg/elastalert/test_rule.py", line 441, in main     test_instance.run_rule_test()   File "/usr/lib/python2.7/site-packages/elastalert-0.2.0b2-py2.7.egg/elastalert/test_rule.py", line 408, in run_rule_test     conf = load_conf(args, defaults, overwrites)   File "/usr/lib/python2.7/site-packages/elastalert-0.2.0b2-py2.7.egg/elastalert/config.py", line 44, in load_conf     conf = yaml_loader(filename)   File "/usr/lib/python2.7/site-packages/PyStaticConfiguration-0.10.4-py2.7.egg/staticconf/loader.py", line 167, in yaml_loader     with open(filename) as fh: TypeError: coercing to Unicode: need string or buffer, NoneType found

@jbecker94 from what i can figure the test-rule command expects a —config parameter pointing to the elastalert configuration, there is no default for this option as far as I can tell in elastalert. Therefore my first reaction would be that this option needs to be provided by  bitsensor/elastalert. FYI I may be wrong in this assesment since I'm away from the computer atm

@matsgoran for my understanding if it runs under 0.1.39  it should also be running under 0.2.0b2. The config should be available since the exact same folders are mounted into both of the containers. I have used the exact same Dockerbuildfile as the original bitsensor-docker-image, so there should be no difference except the different elastalert-version.
Hopefully in a couple of days there will be an offical bitsensor-version which fixes this issue. Most likely I have done something wrong in the build process or can anybody confirm that the test-rule command doesn't work?

@jbecker94 Let's hope so:)The changes related to the ES7 compatibility in the beta did not touch any part of the test-rule bootstrap prosess

[_source_include] -> did you mean any of [_source_includes..
Man, this is the most annoying kind of breaking change. Just grepping through the code I can see that these don't always appear together in a search/deprecated_search pairs. I'll go through the code and double check this gets used correctly. More context from THAT error would be useful.
Elastalert-test-rule is kind of a mess, the error handling there is not great, and there's all sorts of special snowflake config being done. The TypeError: coercing to Unicode: need string or buffer, NoneType found does seem clear cut like the config parameter was missing. Again, terrible error handling, sorry about that.

I tried with 0.2.0b version of ElastAlert (I'm using Elastic stack 7.0 version)
I'm still getting this error -
"message": "Error running query: TransportError(400, u\u0027illegal_argument_exception\u0027, u\u0027request [/auditbeat-/_search] contains unrecognized parameter: [_source_include] -> did you mean any of [_source_includes, _source_excludes]?\u0027)",
"traceback": [
"Traceback (most recent call last):",
"  File "/etc/elastalert/elastalert/elastalert.py", line 390, in get_hits",
"    **extra_args",
"  File "/usr/local/lib/python2.7/dist-packages/elasticsearch/client/utils.py", line 76, in _wrapped",
"    v = kwargs.pop(p)",
"  File "/usr/local/lib/python2.7/dist-packages/elasticsearch/client/init.py", line 655, in search",
"    to the total number of copies for the shard (number of replicas + 1)",
"  File "/usr/local/lib/python2.7/dist-packages/elasticsearch/transport.py", line 314, in perform_request",
"    # add a delay before attempting the next retry",
"  File "/usr/local/lib/python2.7/dist-packages/elasticsearch/connection/http_requests.py", line 90, in perform_request",
"    self.log_request_fail(method, url, response.request.path_url, body, duration, response.status_code, raw_data)",
"  File "/usr/local/lib/python2.7/dist-packages/elasticsearch/connection/base.py", line 125, in _raise_error",
"    error_message = additional_info.get(\u0027error\u0027, error_message)",
"RequestError: TransportError(400, u\u0027illegal_argument_exception\u0027, u\u0027request [/auditbeat-/_search] contains unrecognized parameter: [_source_include] -> did you mean any of [_source_includes, _source_excludes]?\u0027)"

@RiteshKuchukulla Are you running 0.2.0b1 or 0.2.0b2? ES7 support was added in 0.2.0b2

@RiteshKuchukulla Are you running 0.2.0b1 or 0.2.0b2? ES7 support was added in 0.2.0b2

I was running 0.2.0b1, which gave the above error.
Now I started to run 0.2.0b2, which doesn't give me the error but this doesn't post to pager duty.

hi here, I read different comments about beta version working or not in 7.x, Can anyone confirm if 0.2.0b2 works? I needed to upgrade to 7.1 and since then we dont have alerting so would like to give it a try soon.
I'll start with 0.2.0b2 but if you are using it already in 7.x please can confirm?
Thanks! great work

I Just installed latest version of ELK 7.1 but ElastAlert is not working i am getting. any one got any fixed for ES7.1

@fpompermaier
Did you try updating botocore?

@shahid-dgs
You need to share more info if you want help

@Qmando what should I do? I just followed the build instructions

Anyone bold enough to see if this works with 7.2 yet?

No new issues seen using v0.2.0b2 and running for 12 hours.

Hello,
I have installed elastalert beta from pip, when I am trying to create index I am getting the following error message:
Traceback (most recent call last):
  File "/usr/local/bin/elastalert-create-index", line 7, in <module>
    from elastalert.create_index import main
  File "/usr/local/lib/python3.5/dist-packages/elastalert/create_index.py", line 13, in <module>
    from auth import Auth
ImportError: cannot import name 'Auth'

Note I am running elasticsearch 7.2.0 with security enabled.

Getting the same errors as above.  Is there a resolution yet to the source_includes error?

Run python 2, use v0.2.0b2

Interesting. python2 is end of life in less than 6 months and we still have it as a dependency

velocidi/elastalert this docker image works well for es 7.x

Has anyone run this on elasticsearch 7.10.x or 7.11.x?

@gdoctor

Has anyone run this on elasticsearch 7.10.x or 7.11.x?

It should work.

@nsano-rururu
it seems that the elastalert version, that've pulled is not compatible with my elasticsearch version 7.9.1. when i run "npm run start", I got this error.

@NOULeENGINEER
It's not Esper, so that kind of listening is frustrating.
elastalert-server?
docker?
manual install?
What is the OS?
What command was executed and what was installed before execution?

The latest docker image should be python3.8 environment?
https://hub.docker.com/r/praecoapp/elastalert-server

@NOULeENGINEER
This repository is not a good place to ask ElastAlertServer questions.

@NOULeENGINEER
It works with the latest 7.11.1, but what?

I'm going to try your latest version on the docker hub

@NOULeENGINEER
It's not Esper, so that kind of listening is frustrating.
elastalert-server?
docker?
manual install?
What is the OS?
What command was executed and what was installed before execution?

the version of the elasticsearch is 7.9.1
the OS is ubuntu 18.04.5
the installation is manual, i followed steps that i've found in a medium blog : Deploying a SOCaaS infrastructure
the latest command that i've ran is npm run start

@NOULeENGINEER
See the official website for the manual installation procedure. I wrote. Because I'm the maintainer.
https://github.com/johnsusek/praeco#manualdev-installation

I have installed elasticsearch 7.0.1 and elastalert plugin. I am facing the same _source_include issue.  Any fix is provided?
Would have written the following documents to writeback index (default is elastalert_status):
elastalert_error - {'message': "Error running query: RequestError(400, u'illegal_argument_exception', u'request [/daq_log_qa1_*/_search] contains unrecognized parameter: [_source_include] -> did you mean any of [_source_includes, _source_excludes]?')", 'traceback': ['Traceback (most recent call last):', '  File "elastalert/elastalert.py", line 370, in get_hits',

I have installed elasticsearch 7.0.1 and elastalert plugin. I am facing the same _source_include issue. Any fix is provided?
Would have written the following documents to writeback index (default is elastalert_status):
elastalert_error - {'message': "Error running query: RequestError(400, u'illegal_argument_exception', u'request [/elastic_log_qa1_*/_search] contains unrecognized parameter: [_source_include] -> did you mean any of [_source_includes, _source_excludes]?')", 'traceback': ['Traceback (most recent call last):', ' File "elastalert/elastalert.py", line 370, in get_hits',

@udaykumar-tivo
Please create a new issue. Also, it is difficult to answer without more detailed information about the environment.


dataset problem - Need to revert covid19AbseqPBMC from complete -> exported

Blood bionetwork dataset
covid19AbseqPBMC

project uuid -  be010abc-fb68-4581-b61f-7dd7c3d7b044
link to browseHCA data portal
link to ingest UI

Relevant People

Wrangler: Rachel Schwartz
-Contributor: Rajesh Pandey

Description of the problem with the dataset
needs to be kicked from exported -> complete for ontology update

As I understand, the project needs to be updated.
I therefore changed the status to GraphValid.


Patch bug in remarshal

This bug prevents import of Prometheus operator CRDs, as some list contains a =.
remarshal doesn't seem to be actively maintained anymore. I think it is sensible to patch it here, as it is merely an implementation detail of importYAML.

instead of patching unmaintained software I'd recommend switching to yq:
let
  importYAML = path: lib.importJSON (runCommand "yaml-to-json" {}
    ''
      ${yq}/bin/yq -c . ${builtins.path { inherit path; }} > $out
    ''
  );

  toYAMLFile = attrs: runCommand "to-yaml" {}
    ''
      ${yq}/bin/yq -y . ${writeText "to-json" (builtins.toJSON attrs)} > $out
    ''
  ;

A cool! I tried searching for alternatives, I even tried switching to yaml2json, which is equivally as unmaintained and which has bugs that I quickly stumbled across as well. But yeah, that definitely makes more sense.

Thanks, both :100: closing in preference of #26.


towers of hanoi example

I think this could be a nice show case

nah, it looked like a funny idea, but this is just toooooo theoretical