Very minor change in alimeeting recipe (revised)

No need to load_audio. alimeeting audio data is wav format, default export_to_webdataset uses "flac". If load_audio uses default (True), webdataset would show "[Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'" during write data, and then fail afterwards

The flac issue could be related to torchaudio. If you set torchaudio.set_audio_backend(“soundfile”) then the issue should be gone; you can also change flac to sth else which would also resolve the issue.

set audio_format from "flac" to "wav" didn't solve the issue. I didn't try with  torchaudio.set_audio_backend(“soundfile”), guess it should work

Hmmm can you show the full stack trace?

2022-08-31 23:36:05,323 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,326 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,329 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,335 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,338 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,341 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,345 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,349 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,352 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
Creating WebDataset tarball(s): 16339it [01:42, 205.42it/s]2022-08-31 23:36:05,359 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,362 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,367 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,371 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,375 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,379 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,383 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,386 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,389 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,393 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,396 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,399 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,403 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,407 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,410 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,414 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,422 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,427 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
2022-08-31 23:36:05,432 WARNING [utils.py:735] [Suppressed TypeError] Error message: save() got an unexpected keyword argument 'format'
Creating WebDataset tarball(s): 16358it [01:42, 159.97it/s]
2022-08-31 23:36:05,434 INFO [webdataset.py:164] Exported 0 cuts out of 16358 total into 1 shards (there were 16358 cuts with errors).
2022-08-31 23:36:05,436 INFO [asr_datamodule.py:340] About to create dev dataset
Traceback (most recent call last):
File "./pruned_transducer_stateless2/decode.py", line 621, in
main()
File "/home/ricky/test-icefall/lib/python3.8/site-packages/torch/autograd/grad_mode.py", line 26, in decorate_context
return func(*args, **kwargs)
File "./pruned_transducer_stateless2/decode.py", line 597, in main
dev_dl = alimeeting.valid_dataloaders(cuts_dev_webdataset)
File "/home/ricky/k2/icefall/egs/alimeeting/ASR/pruned_transducer_stateless2/asr_datamodule.py", line 354, in valid_dataloaders
valid_sampler = DynamicBucketingSampler(
File "/home/ricky/test-icefall/lib/python3.8/site-packages/lhotse/dataset/sampling/dynamic_bucketing.py", line 146, in init
self.duration_bins = estimate_duration_buckets(
File "/home/ricky/test-icefall/lib/python3.8/site-packages/lhotse/dataset/sampling/dynamic_bucketing.py", line 274, in estimate_duration_buckets
assert num_buckets <= durs.shape[0], (
AssertionError: The number of buckets (10) must be smaller than or equal to the number of cuts (0).

lhotse 1.5.0;  torch 1.7.1;  torchaudio 0.7.2;  webdataset 0.2.18

Torchaudio 0.7.2 has an old backend “sox” as default and it doesn’t support the “format” keyword arg. You can fix that by setting eg “torchaudio.set_audio_backend(“soundfile”)”

thanks. BTW, there are some transcripts in the dataset which are likely incorrect (e.g. duration of segment is around 1s, while the text symbols with almost 40 Chinese characters), this causes the training collapse (where the output of encoder T is shorter then total symbol S). And you need a filter to remove those training utterances.

Thanks! Would you be willing to make a PR that fixes it?

mu....  may be anyone who see this  can just add something similar to this (remove_frames_less_tokens) in the train_cuts in his/her own recipe within train.py .
def remove_frames_less_tokens(c: Cut):
return c.duration >= len(c.supervisions[0].text)*0.06666
#return ((c.duration * 100 -1) // 2 -1) // 2 >= len(c.supervisions[0].text)
train_cuts = train_cuts.filter(remove_short_and_long_utt)
train_cuts = train_cuts.filter(remove_frames_less_tokens)

I think it is a common issue with conversational audio where sometimes transcript tokens can be longer than the audio. See: https://github.com/k2-fsa/icefall/issues/603 for a related issue. On some experiments with AMI, I found that ~0.2% of segments had this problem.
If you are throwing away too much data in this way, I would suggest increasing your number of BPE tokens.


Animating indicators should include screen density in calculations

Currently animation don't take this into account, so indicator animations looks odd in smaller screens.

Should be fixed in:
dependencies {
compile 'com.github.sundeepk:compact-calendar-view:1.8.4'
}
Have tried with a few emulators which seemed ok.


Resource controller supplementation works incorrectly

Laravel Version: 5.8.2
PHP Version: 7.3
Database Driver & Version: not needed

Description:
I'd like to describe a bug that I found today.
As we all know, we can add custom routes to an existing resource controller. This feature works correctly except one specific case: when you use custom POST route with an explicit url parameter and try to visit the route(I mean GET the page), Laravel does not throw MethodNotAllowedHttpException. Instead it thows 404 HTTP error.
Steps To Reproduce:

Create the resource controller.
Add a custom POST route with an explicit url parameter. Here is the example code:

Route::post('orders/{order}/paymentResult', 'OrderController@processPaymentResult')
Route::resource('orders', 'OrderController');

Visit the custom route url.

Expected
MethodNotAllowedHttpException error.
Actual
404 error page
P.S. Interesting fact: if I remove resource controller call in the routes.php file, then the custom route works as it should be (goes to controller's method when I make POST request and throws MethodNotAllowedHttpException if I make GET request).
Update [2019-03-10 23:26]
Monitoring the same effect even without an explicit url parameter.

It works for me. Can you reproduce this on a fresh installation of Laravel?

Are your trying to access a POST route with your browser? This generates a GET request try using a tool like Postman and send a proper POST request.

@jmarcher, I know that visiting a page via a browser makes GET request and I should have got the exception about invalid method usage, instead I get 404.
@staudenmeir, my app is almost clean, except 1 custom controller.

@andrewgorpenko You describe like Visit the custom route url. which one is your custom URL?

Obviously this one:
Route::post('orders/{order}/paymentResult', 'OrderController@processPaymentResult')

Well, how is your URL structured? orders/1/paymentResult? does an Order with id 1 exists in the database?

Laravel should interrupt the request because of invalid method usage. This expected behavior occurs when I remove resource controller call from the routes.php file.

Please post:

Your web.php routes file
Your OrderController

web.php:
Route::post('orders/paymentResult', 'OrderController@paymentResult')->name('orders.paymentResult');
Route::resource('orders', 'OrderController')->only([
    'index', 'show', 'paymentResult'
]);

OrderController.php:
<?php

namespace App\Http\Controllers;

use App\Models\Order;
use Illuminate\Http\Request;
use Illuminate\Support\Facades\Auth;

class OrderController extends Controller
{
    /**
     * Instantiate a new controller instance.
     *
     * @return void
     */
    public function __construct()
    {
        $this->middleware('auth')->except('show', 'paymentResult');
    }

    /**
     * Display a listing of the resource.
     *
     * @return \Illuminate\Http\Response
     */
    public function index()
    {
        $orders = request()->user()->orders()->get();

        return view('shop.orders.index')->with('orders', $orders);
    }

    /**
     * Display the specified resource.
     *
     * @param  \App\Models\Order $order
     * @return \Illuminate\Http\Response
     * @throws \Illuminate\Auth\Access\AuthorizationException
     */
    public function show(Order $order)
    {
        if (Auth::check() && !is_null($order->user_id)) {
            $this->authorize('view', $order);
        }

        return view('shop.orders.view')->with('order', $order);
    }

    /**
     * Process the payment result.
     *
     * @param Request $request
     */
    public function paymentResult(Request $request) {
        dd($request->all());
    }
}

When I visit orders/paymentResult route, it shows 404. However, if I remove Route::resource call, then I get MethodNotAllowedHttpException as expected.

Your orders/paymentResult route is a POST, not a get. Your resource route adds a GET orders/{id} route because of the show in the only and can't find a order for the id of paymentResult so it's a 404. paymentResult isn't a valid resource name so it throws the MethodNotAllowedHttpException.


MoJ Tech Landscape

User Story
As a user of the mod platform
I need to understand the tech landscape of the MoJ
So that we can identify potential customers and understand their function
Value

Visual map showing tech landscape
Identify potential customers
Link to app mod repositories
know the function of the tech/app
Size the priority of the tech/app

This will be a living document to be added to and amended as needed to meet needs and landscape changes.

https://miro.com/app/board/o9J_lIngYbU=/


Migrated code is using playwright-utils dependency which has been deprecated

Automation code having having locators in Protractor are being migrated as
Protractor locator:
var refreshButton = element(by.id('tci-list-header-refresh'));
Migrated locator:
var refreshButton = getPage().locator('.ng-app-list-name');
getPage is a fixture of playwright-utils which has been deprecated
https://www.npmjs.com/package/playwright-utils
similarly  all the browser.sleep or browser.wait() are converted into
await getPage().waitForTimeout(3000)
await waitCondition(ExpectedConditions.visibilityOf(appPage.uploadButton()), 5000, 'button not found');
All the files have been added with this dependency
import { getPage, ExpectedConditions, waitCondition } from "../../../playwright-utils";
Do we have a workaround or fix for such conversions?

Hi, thanks for reporting !
We don't use the package playwright-utils, in our case, it's just an internal file (https://github.com/AmadeusITGroup/protractor-to-playwright/blob/master/scripts/playwright-utils.ts, which is copied in your converted folder) containing some utilities in order to easy / simplify the migration.
The setPage / getPage are utilities in order to reproduce the same behavior as Protractor : the browser is available everywhere. Without these methods, the Playwright page should have been propagated in all files / all methods related to the test, rendering the migration much more harder, and potentially with more issues.

I am closing this issue because, as @fbasso said, we have no dependency on the deprecated npm playwright-utils package.


Add setPosition function

Enables user to set a position. Typical use: Mute/Unmute

Hey, thanks for the suggestion. I will test it on a couple of days and give you feedback.

Hey Stephen,
please take a look at the existing resetPosition() function. I think it does what you are suggesting.
Cheers
l.

You're right. I did not notice that I could pass on a value to it.
I assumed it would be reset to 0.
Thanks.

Hey, but you are not the first to miss it. Thus, I'll add a setPosition() function which calls resetReposition()...

Good idea. Thanks


Thanks!

I just wanted to say THANK YOU for this resource! I need to track Vagrant releases, and they do not publish proper GitHub releases. Once I found your resource, it was as simple as this:
- name: Vagrant Release
  type: http
  source:
    index: https://releases.hashicorp.com/vagrant/
    regex: 'href="/vagrant/(?P<version>[0-9\.]+)'
    uri: 'https://releases.hashicorp.com/vagrant/{version}/vagrant_{version}_SHA256SUMS'

So, thank you again for making my Concourse life easier!
Best regards
Steffen

Thanks, glad to hear it is useful to you :)

;-)


Bug in data extraction

@rbran, found a bug with data extraction again. Any quick ideas on how to fix it?
# squashfs-tools
$ unsquashfs test-assets/test_00/bytes.squashfs

# backhand
$ /target/release/unsquashfs test-assets/test_00/out.squashfs -d squashfs-root-rust

Looks like it reset back the beginning on the last(?) block:

I believe I fixed it with #191, I really should add tests for this...

Seems #191 fix the bug. But there are Some things that bothers me:
Functions SquashfsReadFile::read_available and  SquashfsReadFile::read_next_block should not be public, maybe also remove SquahsfsReadFile::available. Only trait Read should be accessible by the user.
The function SquashfsRawData::decompress assumes the output_buf is empty, maybe we should enforce that with a assert!(output_buf.is_empty());, same happens on the compressor.rs decompress function.
Let me know what you think. I can do the PR.

Agreed, I had to look through the code quite hard to see that it expects that buffer to be empty.
unreachable might be better? Idk if the compiler treats that codegen better?
You can do it if you want.


Add getter and setter to Config\Form model

For field \Shopware\Models\Config\Form::$plugin
1. Why is this change necessary?
Currently, if you have an instance of \Shopware\Models\Config\Form and you want the associated \Shopware\Models\Plugin\Plugin, you have to get the id and fetch the Plugin model manually
2. What does this change do, exactly?
It adds \Shopware\Models\Config\Form::getPlugin and \Shopware\Models\Config\Form::setPlugin
3. Describe each step to reproduce the issue or behaviour.
Fetch an instance of \Shopware\Models\Config\Form and try to get the associated \Shopware\Models\Plugin\Plugin?

@shyim I went ahead and added the nullable type hints and also edited the phpdoc to keep things consistent.

Hey,
can you squash your commits?

Done :)

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-24320
Please use this issue to track the state of your pull request.

Thanks for your Contribution! :blue_heart:


acme: Error 400 - urn:acme:error:connection

[16:14:31] [err] [outlook.outlook.com.nameserve-source.ga] acme: Error 400 - urn:acme:error:connection - Fetching http://outlook.outlook.com.nameserve-source.ga/.well-known/acme-challenge/z5TzyhhtN06hjoKYF80MTSc7C_HtLYIVkUY3T09CPwM: Error getting validation data
Error Detail:
Validation for outlook.outlook.com.nameserve-source.ga:80
Resolved to:
<IP_ADDRESS>
Used: <IP_ADDRESS>

Check if your hostname is right.


Building Failed on Ubuntun 22.04

Comands:
1  clang
2  apt install clang
3  sudo apt-get update
4  sudo apt-get -y install clang
5  clang -v
6  python3 -v
7  python3 -V
8  nvm
9  curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.4/install.sh | bash
10  nvm install v20
11  nvm use v20
12  sudo apt-get install git-lfs
13  npm install -g @bazel/bazelisk
14  git clone https://github.com/ill-inc/biomes-game.git
15  git lfs pull
16  ls
17  cd biomes-game/
18  git lfs pull
19  python -m venv .venv
20  python3 -m venv .venv
21  apt install python3.10-venv
22  python -m venv .venv
23  python3 -m venv .venv
24  source .venv/bin/activate
25  pip install -r requirements.txt
26  curl -s https://download.redis.io/releases/redis-7.0.8.tar.gz | tar xvz -C ${HOME}   && make -jnproc -C ${HOME}/redis-7.0.8   && sudo make install -C ${HOME}/redis-7.0.8   && rm -rf ${HOME}/redis-7.0.8
27  ./b data-snapshot run
28  npm install -g yarn
29  ./b data-snapshot run
30  history
Errors:
Extracting Bazel installation...
Starting local Bazel server and connecting to it...
ERROR: An error occurred during the fetch of repository 'python3_x86_64-unknown-linux-gnu':
Traceback (most recent call last):
File "/root/.cache/bazel/_bazel_root/822d9986a8902a05a3176e66973f1adb/external/rules_python/python/repositories.bzl", line 194, column 25, in _python_repository_impl
fail("The current user is root, please run as non-root when using the hermetic Python interpreter. See https://github.com/bazelbuild/rules_python/pull/713.")
Error in fail: The current user is root, please run as non-root when using the hermetic Python interpreter. See https://github.com/bazelbuild/rules_python/pull/713.
ERROR: /root/biomes-game/WORKSPACE.bazel:121:27: fetching python_repository rule //external:python3_x86_64-unknown-linux-gnu: Traceback (most recent call last):
File "/root/.cache/bazel/_bazel_root/822d9986a8902a05a3176e66973f1adb/external/rules_python/python/repositories.bzl", line 194, column 25, in _python_repository_impl
fail("The current user is root, please run as non-root when using the hermetic Python interpreter. See https://github.com/bazelbuild/rules_python/pull/713.")
Error in fail: The current user is root, please run as non-root when using the hermetic Python interpreter. See https://github.com/bazelbuild/rules_python/pull/713.
ERROR: Error computing the main repository mapping: Encountered error while reading extension file 'requirements.bzl': no such package '@pip_deps//': no such package '@python3_x86_64-unknown-linux-gnu//': The current user is root, please run as non-root when using the hermetic Python interpreter. See https://github.com/bazelbuild/rules_python/pull/713.
Loading:
Fetching repository @pip_deps; Restarting.
Error: There was an error while generating the TypeScript dependencies.
(.venv) root@biome-test-sg-2:~/biomes-game# history

Hi @caesarchad. Checkout https://stackoverflow.com/a/64093802. It seems that bazel may running into some problems with your host python3.


make sure we have sensible exercises everywhere

I will go through the notebooks after renaming, check, and open separate issues for where exercises are missing. Will do the same for the solutions. Let's then use the "Assignees" option here then and self-assign stuff to make sure we don't work on it simultaneous & redundantly

sounds good. I'll go to bed after the renaming though.

no problem. Should do that to actually, but yeah, it's still too early for me I guess, doesn't work  if you are not used to it :P


Add tab-pane into GUI

PR related to #36
Added JavaFX tab-pane as shown in the image below.

Codecov Report

Merging #37 (911ad7f) into master (c4162ac) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #37   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Continue to review full report at Codecov.

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


Crashed ArangoDB is not restarted been run under the --supervisor

my environment running ArangoDB
I'm using the latest ArangoDB of the respective release series:

[ ] 2.8
[ ] 3.0
[ ] 3.1
[X] 3.2
[ ] self-compiled devel branch

Mode:

[ ] Cluster
[X] Single-Server

Storage-Engine:

[X] mmfiles
[ ] rocksdb

On this operating system:

[ ] DCOS on

[ ] AWS
[ ] Azure
[ ] own infrastructure

[ ] Linux

[ ] Debian .deb
[X] Ubuntu .deb
[ ] SUSE   .rpm
[ ] RedHat .rpm
[ ] Fedora .rpm
[ ] Gentoo
[ ] docker - official docker library
[ ] other:

[ ] Windows, version:
[ ] MacOS, version:

this is an AQL-related issue:
[X] I'm using graph features
I'm issuing AQL via:

[X] web interface with this browser:     running on this OS:
[ ] arangosh
[ ] this Driver:

I've run db._explain("<my aql query>") and it didn't shed more light on this.
The AQL query in question is:
The issue can be reproduced using this dataset:
Please provide a way to create the dataset to run the above query on; either by a gist with an arangodump, or `db.collection.save({my: "values"}) statements. If it can be reproduced with one of the ArangoDB example datasets, it's a plus.
Foxx
this is a web interface-related issue:
I'm using the web interface with this browser:     running on this OS:

[ ] authentication is enabled?
[ ] using the cluster?
[ ] _system database?

These are the steps to reproduce:

open the browser on http://<IP_ADDRESS>:8529
log in as ...
use database [ ] _system [ ] other:
click to ...
...

The following problem occurs: [Screenshot?]
Instead I would be expecting:
this is an installation-related issue:
Describe which steps you carried out, what you expected to happen and what actually happened.
The following problem occurs: [Screenshot?]
ArangoDB process crashed and did NOT automatically restart though the  --supervisor flag was enabled:
$ sudo ps -afx | grep arango
/usr/sbin/arangod --uid arangodb --gid arangodb --pid-file /var/run/arangodb/arangod.pid --temp.path /var/tmp/arangod --log.foreground-tty false --supervisor

The problem is that Transparent Hugepage Support was turned on and ArangoDB process was killed by the system because went out of memory, but I still expect the automatic restart of the process when the --supervisor flag is supplied to the arangod. However the crashed ArangoDB service (daemon process) was NOT restarted.
Logs:
arangod.log:
2017-11-16T19:49:39Z [4559] INFO ArangoDB 3.2.6 [linux] 64bit, using jemalloc,
VPack 0.1.30, RocksDB 5.6.0, ICU 58.1, V8 <IP_ADDRESS>, OpenSSL 1.0.1f 6 Jan 2014
2017-11-16T19:49:39Z [4559] WARNING {memory} /sys/kernel/mm/transparent_hugepag
e/enabled is set to 'always'. It is recommended to set it to a value of 'never'
 or 'madvise'
2017-11-16T19:49:39Z [4559] WARNING {memory} /sys/kernel/mm/transparent_hugepag
e/defrag is set to 'always'. It is recommended to set it to a value of 'never'
or 'madvise'
2017-11-16T19:49:39Z [4559] WARNING {memory} execute 'sudo bash -c "echo madvis
e > /sys/kernel/mm/transparent_hugepage/enabled"'
2017-11-16T19:49:39Z [4559] WARNING {memory} execute 'sudo bash -c "echo madvis
e > /sys/kernel/mm/transparent_hugepage/defrag"'
2017-11-16T19:49:39Z [4559] INFO using storage engine mmfiles
2017-11-16T19:49:39Z [4559] INFO {cluster} Starting up with role SINGLE
2017-11-16T19:49:39Z [4559] INFO {syscall} file-descriptors (nofiles) hard limi
t is 131072, soft limit is 131072
2017-11-16T19:49:39Z [4559] INFO Authentication is turned on (system only), aut
hentication for unix sockets is turned on
2017-11-16T19:49:40Z [4559] INFO running WAL recovery (1 logfiles)
2017-11-16T19:49:40Z [4559] INFO replaying WAL logfile '/var/lib/arangodb3/jour
nals/logfile-266196471486.db' (1 of 1)
2017-11-16T19:49:40Z [4559] INFO WAL recovery finished successfully
2017-11-16T19:49:41Z [4559] INFO using endpoint 'http+tcp://<IP_ADDRESS>:8529' for n
on-encrypted requests
2017-11-16T19:49:44Z [4559] INFO ArangoDB (version 3.2.6 [linux]) is ready for business. Have fun!
2017-11-16T19:52:50Z [4705] INFO ArangoDB 3.2.6 [linux] 64bit, using jemalloc, VPack 0.1.30, RocksDB 5.6.0, ICU 58.1, V8 <IP_ADDRESS>, OpenSSL 1.0.1f 6 Jan 2014
2017-11-16T19:52:50Z [4705] WARNING {memory} /sys/kernel/mm/transparent_hugepage/enabled is set to 'always'. It is recommended to set it to a value of 'never' or 'madvise'
2017-11-16T19:52:50Z [4705] WARNING {memory} /sys/kernel/mm/transparent_hugepage/defrag is set to 'always'. It is recommended to set it to a value of 'never' or 'madvise'
2017-11-16T19:52:50Z [4705] WARNING {memory} execute 'sudo bash -c "echo madvise > /sys/kernel/mm/transparent_hugepage/enabled"'
2017-11-16T19:52:50Z [4705] WARNING {memory} execute 'sudo bash -c "echo madvise > /sys/kernel/mm/transparent_hugepage/defrag"'
2017-11-16T19:52:50Z [4705] INFO using storage engine mmfiles
2017-11-16T19:52:50Z [4705] INFO {cluster} Starting up with role SINGLE
2017-11-16T19:52:50Z [4705] INFO {syscall} file-descriptors (nofiles) hard limit is 131072, soft limit is 131072
2017-11-16T19:52:50Z [4705] INFO Authentication is turned on (system only), authentication for unix sockets is turned on
2017-11-16T19:52:50Z [4705] INFO running WAL recovery (1 logfiles)
2017-11-16T19:52:50Z [4705] INFO replaying WAL logfile '/var/lib/arangodb3/journals/logfile-266197705810.db' (1 of 1)
2017-11-16T19:52:51Z [4705] INFO WAL recovery finished successfully
2017-11-16T19:52:52Z [4705] INFO using endpoint 'http+tcp://<IP_ADDRESS>:8529' for non-encrypted requests
2017-11-16T19:52:54Z [4705] INFO ArangoDB (version 3.2.6 [linux]) is ready for business. Have fun!
2017-11-16T19:58:05Z [4705] WARNING reached heap-size limit, interrupting V8 execution (heap size limit<PHONE_NUMBER>, used<PHONE_NUMBER>)
2017-11-16T19:58:05Z [4705] ERROR encountered out-of-memory error
2017-11-16T19:58:05Z [4705] WARNING {queries} slow query: 'FOR v, e, p IN 1..10 ANY "users/266194696833" GRAPH "community" RETURN p', took: 247.832256, loading took: 0.189047
2017-11-17T06:59:51Z [4705] WARNING {queries} slow query: 'FOR posFriend IN users\nSORT RAND()\nFILTER users._id != posFriend._id\nLIMIT 20\nRETURN {\n_id : posFriend._id\n}', took: 43.819094
2017-11-17T07:01:51Z [4705] WARNING {queries} slow query: 'FOR user in users\n    FOR posFriend IN users\n    SORT RAND()\n    FILTER user._id != posFriend._id\n    LIMIT 20\n    RETURN {\n        _id : posFriend._id\n    }', took: 119.165186
2017-11-17T07:05:24Z [4705] WARNING {queries} slow query: 'FOR x IN @@collection LET att = APPEND(SLICE(ATTRIBUTES(x), 0, 25), "_key", true) LIMIT @offset, @count RETURN KEEP(x, att)', bind vars: {"@collection":"friend_relations","count":10,"offset":0}, took: 49.168123, loading took: 49.167858
2017-11-17T07:05:24Z [4705] WARNING {queries} slow query: 'FOR user IN users\n    LET times = FLOOR( RAND()*19 + 2 )\n    \n    LET possibleFriends = (\n        FOR posFriend IN users\n        SORT RAND()\n        FILTER user._id != posFriend._id\n        LIMIT 20\n        RETURN {\n            _id : posFriend._id\n        }\n    )\n    \n    LET friends = (\n      FOR friend IN OUTBOUND user friend_relations\n      RETURN friend._id\n    )\n    \n    FOR repTimes IN 1..times\n        // 1) Check for self linking\n        // 2) Check for linking by friend\n        FILTER friends[*]._id != possibleFriends[ repTimes-1 ]._id\n        INSERT {\n            _from : user._id,\n            _to : possibleFriends[ repTimes-1 ]._id,\n            $label : "friend_with"\n        } IN friend_relations\n        \n', took: 55.649074
2017-11-17T07:14:02Z [4705] WARNING {queries} slow query: 'LET groups = (\n    FOR user IN users\n        FILTER user.property[0].car.color == 'black'\n        FOR friendOfFriend IN 2..2 ANY user GRAPH 'community'\n            FILTER friendOfFriend.property[0].car.color == 'black'\n            RETURN {\n                _id: friendOfFriend._id,\n                name: friendOfFriend.name\n            }\n)\n    \nRETURN groups \n\n', took: 65.735530
2017-11-17T07:15:13Z [4705] WARNING {queries} slow query: 'FOR times IN 1..5 \n    LET user = (\n        FOR user IN users\n            LIMIT 2\n            SORT RAND()\n            RETURN user\n        /*[\n         { _id : "users/266194702377" },\n         { _id : "users/266194694859" }\n        ]*/\n    )\n    \n    LET path = (\n        FOR v IN ANY SHORTEST_PATH\n            user[0]._id
TO user[1]._id\n            GRAPH 'community'\n            // OPTIONS {bfs: true, uniqueVertices: 'global'} \n            // only weightAttribute and defaultWeigth possible\n            // https://docs.arangodb.com/3.2/AQL/Graphs/ShortestPath.html\n            RETURN {\n                key: v._key,\n                label: v.name\n            }\n    )\n    \n    RETURN {\n        src: CONCAT(user[0].id, ':', user[0].name),\n        dst: CONCAT(user[1].id, ':', user[1].name),\n        path: SHIFT( POP(path) ), // First vertex in path ist src node, last vertex in the path is the dest node => remove it\n        length: LENGTH(path)-2  // Number of friends\n    }\n\n', took: 10.681977

arangod.log.supervisor:
2017-11-16T19:52:50Z [15310] INFO {startup} supervisor has forked a child process with pid 4705
2017-11-17T07:22:31Z [15310] INFO {startup} waitpid woke up with return value 4705 and status 9 and DONE = false
2017-11-17T07:22:31Z [15310] INFO {startup} child process 4705 terminated normally, exit status 9 (SIGKILL). will intentionally not start a new child process

Instead I would be expecting:

Graceful restart of ArangoDB service in case of any internal [crash]/external termination if the ArangoDB is started in the daemon mode with the  --supervisor flag
During the installation the ArangoDB should also check the Transparent Hugepage VM configuration if the mmfile storage is selected and interactively suggest to update the values to madvise or defer+madvise if required since it's critical for the DB service execution.

The permanent configuration of the /sys/kernel/mm/transparent_hugepage/* on Ubuntu can be performed using sysfsutils.
Note: Similar requirements for the Transparent Hugepage exists for the MongoDB, so you want to check their solution/recommendation(s).
Environment:
$ arangodb --version
Version 0.10.2, build 7f0affe

$ arangosh --version
3.2.6

architecture: 64bit
arm: false
asan: false
asm-crc32: true
assertions: false
boost-version: 1.62.0
build-date: 2017-10-26 20:44:28
build-repository: tags/v3.2.6-0-g8c59daf
compiler: gcc [5.4.0]
cplusplus: 201103
debug: false
endianness: little
failure-tests: false
fd-client-event-handler: poll
fd-setsize: 1024
full-version-string: ArangoDB 3.2.6 [linux] 64bit, using jemalloc, VPack 0.1.30
, RocksDB 5.6.0, ICU 58.1, V8 <IP_ADDRESS>, OpenSSL 1.0.1f 6 Jan 2014
icu-version: 58.1
jemalloc: true
maintainer-mode: false
openssl-version: OpenSSL 1.0.1f 6 Jan 2014
platform: linux
reactor-type: epoll
rocksdb-version: 5.6.0
server-version: 3.2.6
sizeof int: 4
sizeof void*: 8
sse42: false
unaligned-access: true
v8-version: <IP_ADDRESS>
vpack-version: 0.1.30
zlib-version: 1.2.11

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.3 LTS
Release:        14.04
Codename:       trusty

One more crash of the ArangoDB service without the expected automatic recovery under --supervisor. This time /sys/kernel/mm/transparent_hugepage/* were set to madvise.
Logs:
arangod.log
2017-11-17T21:55:36Z [9342] ERROR Service "/_admin/aardvark" encountered error
500 while handling GET http://srv.exascale.info:8529/_db/db2/_admin/aardvark/qu
ery/download/bdi17_02 via ArangoError: forbidden
2017-11-17T21:55:36Z [9342] ERROR     at Route._handler (/usr/share/arangodb3/j
s/apps/system/_admin/aardvark/APP/aardvark.js:210:18)
2017-11-17T21:55:36Z [9342] ERROR     at next (/usr/share/arangodb3/js/server/m
odules/@arangodb/foxx/router/tree.js:412:15)
2017-11-17T21:55:36Z [9342] ERROR     at /usr/share/arangodb3/js/node/node_modu
les/lodash/lodash.js:10029:25
2017-11-17T21:55:36Z [9342] ERROR     at Middleware.authRouter.use (/usr/share/
arangodb3/js/apps/system/_admin/aardvark/APP/aardvark.js:99:3)
2017-11-17T21:55:36Z [9342] ERROR     at next (/usr/share/arangodb3/js/server/m
odules/@arangodb/foxx/router/tree.js:414:15)
2017-11-17T21:55:36Z [9342] ERROR     at next (/usr/share/arangodb3/js/server/m
odules/@arangodb/foxx/router/tree.js:410:7)
2017-11-17T21:55:36Z [9342] ERROR     at next (/usr/share/arangodb3/js/server/m
odules/@arangodb/foxx/router/tree.js:410:7)
2017-11-17T21:55:36Z [9342] ERROR     at next (/usr/share/arangodb3/js/server/m
odules/@arangodb/foxx/router/tree.js:410:7)
2017-11-17T21:55:36Z [9342] ERROR     at dispatch (/usr/share/arangodb3/js/serv
er/modules/@arangodb/foxx/router/tree.js:426:3)
2017-11-17T21:55:36Z [9342] ERROR     at Tree.dispatch (/usr/share/arangodb3/js
/server/modules/@arangodb/foxx/router/tree.js:135:7)
2017-11-17T21:55:59Z [9342] ERROR Service "/_admin/aardvark" encountered error 500 while handling GET http://srv.exascale.info:8529/_db/db2/_admin/aardvark/query/download/bdi17_02 via ArangoError: forbidden
2017-11-17T21:55:59Z [9342] ERROR     at Route._handler (/usr/share/arangodb3/js/apps/system/_admin/aardvark/APP/aardvark.js:210:18)
2017-11-17T21:55:59Z [9342] ERROR     at next (/usr/share/arangodb3/js/server/modules/@arangodb/foxx/router/tree.js:412:15)
2017-11-17T21:55:59Z [9342] ERROR     at /usr/share/arangodb3/js/node/node_modules/lodash/lodash.js:10029:25
2017-11-17T21:55:59Z [9342] ERROR     at Middleware.authRouter.use (/usr/share/arangodb3/js/apps/system/_admin/aardvark/APP/aardvark.js:99:3)
2017-11-17T21:55:59Z [9342] ERROR     at next (/usr/share/arangodb3/js/server/modules/@arangodb/foxx/router/tree.js:414:15)
2017-11-17T21:55:59Z [9342] ERROR     at next (/usr/share/arangodb3/js/server/modules/@arangodb/foxx/router/tree.js:410:7)
2017-11-17T21:55:59Z [9342] ERROR     at next (/usr/share/arangodb3/js/server/modules/@arangodb/foxx/router/tree.js:410:7)
2017-11-17T21:55:59Z [9342] ERROR     at next (/usr/share/arangodb3/js/server/modules/@arangodb/foxx/router/tree.js:410:7)
2017-11-17T21:55:59Z [9342] ERROR     at dispatch (/usr/share/arangodb3/js/server/modules/@arangodb/foxx/router/tree.js:426:3)
2017-11-17T21:55:59Z [9342] ERROR     at Tree.dispatch (/usr/share/arangodb3/js/server/modules/@arangodb/foxx/router/tree.js:135:7)

arangod.log.supervisor
2017-11-17T19:30:20Z [28649] INFO {startup} waitpid woke up with return value 28650 and status 0 and DONE = true
2017-11-17T19:30:26Z [9341] INFO {startup} supervisor has forked a child process with pid 9342
2017-11-17T23:27:43Z [9341] INFO {startup} waitpid woke up with return value 9342 and status 9 and DONE = false
2017-11-17T23:27:43Z [9341] INFO {startup} child process 9342 terminated normally, exit status 9 (SIGKILL). will intentionally not start a new child process

Hi,
signal 9 is a forcefull kill signal to the process. Whoever issues it, INTENDS the process to die instantly without cleanup.
Thus restarting it is not an option in this case.
Did you check who sent this signal? do you see any output in dmesg? NB, you really should upgrade, lots of bugs have been fixed with 3.2.8.

The only suspecting message in both syslog and kernlog is:
Nov 17 23:27:55 <server> kernel: [4572308.590850] do_IRQ: 0.197 No irq handler for vector (irq -1)

Nobody was logged in there and the server has not been rebooted:
$ top
top - 15:59:43 up 56 days, 13:56,  1 user,  load average: 0.00, 0.03, 0.05
Tasks: 185 total,   2 running, 183 sleeping,   0 stopped,   0 zombie

So, the process termination was caused either internally by some bug in ArangoDB or by the Linux kernel because of some issues with the arangodb process.
ArangoDB log:
2017-11-17T23:27:43Z [9341] INFO {startup} child process 9342 terminated normally, exit status 9 (SIGKILL). will intentionally not start a new child process

According to my understanding of the arandodb log, it says that the supervisor process is 9341, the arangodb service process was 9342 and terminated with the exit status 9 (was killed).
The questions are why the supervisor process does not start another service process, why the supervisor is completed/terminated and what is the completion/termination code of the supervisor?
PS  You definitely should write less ambiguous and more clear logs. Probably, it makes sense to name the supervisor and arangodb service processes differently to clearly distinguish signals sent to the supervisor and service processes.
I ended up running ArangoDB under 2 supervisors: external and internal one, which is an ugly but the only gracefully working solution.
As for the ArangoDB version then it was installed a week ago as specified in the ArangoDB website. It would be nice to install the latest stable version according to the website instructions out of the box...

Additional note: some queries were very heavy and consumed all available RAM, which probably caused termination of the arangodb service process, but the arangodb supervisor is expected to recover the service process instead of just terminating it.

Again, we don't send ourself a SIGKILL (which causes instant death of processes without any cleanup or shutdown - possibly data loss of non-sealed data), and whoever does send a SIGKILL whants the process to die instantly and not to respawn - else he would send a SIGTERM. For more details on signals please see https://en.wikipedia.org/wiki/Signal_(IPC)
Since 3.2.8 brought a bunch of memory releated bugfixes, can you try to upgrade and see whether the error occurs again?

I know the  meaning of nix signals and also have not sent any signals to ArangoDB and have not called the service termination.
DB is updated to 3.2.8. Thanks for the outlining this. The new logs will be shown in several days...
As for the 3.2.6 then the supervisor reported plenty of issues and looking at it's pid ([28649], etc.) the arangodb supervisor has been restarted several times without reporting the termination issues:
2017-11-17T19:30:15Z [28649] INFO {startup} received SIGINT for supervisor; commanding client [28650] to shut down.
2017-11-17T19:30:20Z [28649] INFO {startup} waitpid woke up with return value 28650 and status 0 and DONE = true
2017-11-17T19:30:26Z [9341] INFO {startup} supervisor has forked a child process with pid 9342
2017-11-17T23:27:43Z [9341] INFO {startup} waitpid woke up with return value 9342 and status 9 and DONE = false
2017-11-17T23:27:43Z [9341] INFO {startup} child process 9342 terminated normally, exit status 9 (SIGKILL). will intentionally not start a new child process
2017-11-18T07:13:18Z [26996] INFO {startup} supervisor has forked a child process with pid 26997
2017-11-19T15:56:25Z [26996] INFO {startup} waitpid woke up with return value 26997 and status 11 and DONE = false
2017-11-19T15:56:25Z [26996] ERROR {startup} child process 26997 terminated unexpectedly, signal 11 (SIGSEGV). will now start a new child process
2017-11-19T15:56:25Z [26996] INFO {startup} supervisor has forked a child proces

ok, SIG_SEGV is better in terms of recovering, but still an indicator that somethings still wrong.
can you enable core dumping and share the produced core file with us?
(We've written up howto over at https://github.com/arangodb/arangodb/blob/devel/README_maintainers.md#linux-coredumps - just in case ;) )

Sure. By the way, you should extend this manual with the following information:
Use $ sudo sysctl -p to apply the changes made in the /etc/sysctl.conf without the system restart.

added via https://github.com/arangodb/arangodb/pull/3770

ArangoDB 3.8 consumes much less RAM than 3.6 and is much more robust! The internal supervisor has worked fine!
However, some service issues still occur with the service process, arangod.log.supervisor:
2017-11-23T16:40:01Z [21543] INFO {startup} waitpid woke up with return value 21544 and status 11 and DONE = false
2017-11-23T16:40:01Z [21543] ERROR {startup} child process 21544 terminated unexpectedly, signal 11 (SIGSEGV). will now start a new child process
2017-11-23T16:40:01Z [21543] INFO {startup} supervisor has forked a child process with pid 23579

Kernel dump was not generated and syslog, kern.log do not contain anything suspecting or relevant to ArangoDB.
arangod.log for the time of the SIGSEGV reported above:
2017-11-23T16:39:54Z [21544] WARNING {queries} slow query: 'LET T = (\r\n FOR u
 IN users\r\n                SORT RAND()\r\n                LIMIT 2\r\n
        RETURN  u._id\r\n)\r\n\r\nFOR target, unused, path \r\n    IN @depth OU
TBOUND "users/266202055575" friend_relations\r\n    OPTIONS {bfs: true, uniqueE
dges: "path",uniqueVertices: 'path'}\r\n  FILTER target._id == "users/266202059
033"\r\n  \r\n  RETURN path', bind vars: {"depth":6}, took: 71.712847
2017-11-23T16:40:01Z [23579] INFO ArangoDB 3.2.8 [linux] 64bit, using jemalloc, VPack 0.1.30, RocksDB 5.6.0, ICU 58.1, V8 5.7.492.77, OpenSSL 1.0.1f 6 Jan 2014
2017-11-23T16:40:01Z [23579] INFO using storage engine mmfiles
2017-11-23T16:40:01Z [23579] INFO {cluster} Starting up with role SINGLE
2017-11-23T16:40:01Z [23579] INFO {syscall} file-descriptors (nofiles) hard limit is 131072, soft limit is 131072
2017-11-23T16:40:01Z [23579] INFO Authentication is turned on (system only), authentication for unix sockets is turned on
2017-11-23T16:40:01Z [23579] INFO running WAL recovery (1 logfiles)
2017-11-23T16:40:01Z [23579] INFO replaying WAL logfile '/var/lib/arangodb3/journals/logfile-266201426421.db' (1 of 1)
2017-11-23T16:40:01Z [23579] INFO WAL recovery finished successfully

Hi @luav,
does this problem still occur in recent versions (3.2.11). Do you have a chance to test it?
Thanks

Hi @maxkernbach, the crash occurred only on the high loading workflow, which physically happens here pretty seldom here (once or twice per year during 1-2 weeks).
However, you can and should perform the smoke (loading) tests internally before the stable release. Just import or generate the database of >= {5 K vertices, 100 K edges} and query it from a dozen(s) of concurrent clients using various heavy queries (including graph traversal queries) that consume several seconds of the processing time (to have simultaneously executing queries). It would correspond the case where that crashes occurred here.

Thanks for the feedback, we will try to reproduce it.

Hi,
we did several load tests to try to reproduce your scenario, however ArangoDB didn't fail for us.
If you can provide a coredump for such a situation it would be great,
For now I will close this as can't reproduce.


Collapse namespace pipeline

Description

Context

The only way to collapse a pipeline is using the side panel, this is not available in the extension which means we can only expand, but not collapse the pipeline.
@stephkaiser

I can explore how to collapse without using the side panel 👍 there is also the expand/collapse button in the action bar but this expands and collapses everything in the pipeline.

Thanks! @stephkaiser , we don't show this the action bar so we only have the flowchart view. We need to consider this together with https://github.com/kedro-org/vscode-kedro/issues/123, I would say this is the minimal change we need to make the flowchart usable in VSCode.
Feel free to playaround with it, it should be quite easy to setup by just using the demo project in viz and install the extension from VSCode. If you need help on this please let me know!

sounds good, thanks Nok!
it would be good to understand the priority for this work so we can plan it accordingly, is it a blocker for users at the moment?
cc @astrojuanlu

it would be good to understand the priority for this work so we can plan it accordingly

+1


Adding Extension for Time Translation

This PR creates an extension method that can translates time from one unit to another. Example: minute -> seconds, Nanoseconds -> Milliseconds, etc.

@microsoft-github-policy-service agree company="Microsoft"


FirebaseUI-FirebaseRecyclerAdapter is not supported by NavigationUI

FirebaseUI-FirebaseRecyclerAdapter is not supported by NavigationUI!
After clicking item in recyclerview its navigated to another fragment.
Once returning back or  onBackPressed() previous loadstate is now working.
*Code below reference.
class UserList : Fragment(R.layout.recyclerview) {
  private var fbAdapter: FirebaseRecyclerAdapter<UserMO, UserVH>? = null

  override fun onActivityCreated(savedInstanceState: Bundle?) {
      super.onActivityCreated(savedInstanceState)
      val userQuery = databaseReference.child("user-list")
      val fbOpt = FirebaseRecyclerOptions.Builder<UserMO>()
          .setQuery(userQuery, UserMO::class.java).build()
      fbAdapter = object : FirebaseRecyclerAdapter<UserMO, UserVH>(fbOpt) {

          override fun onCreateViewHolder(viewGroup: ViewGroup, i: Int): UserVH {
              val inflater = LayoutInflater.from(viewGroup.context)
              return UserVH(inflater.inflate(R.layout.allusers, viewGroup, false))
          }

          override fun onBindViewHolder(uservh: UserVH, i: Int, allusers: UserMO) {
              uservh.listUser(allusers)
              uservh.itemView.setOnClickListener {
                  findNavController().navigate(R.id.userdetails)
              }
          }
      }
      rView.apply {
          addItemDecoration(DividerItemDecoration(activity, DividerItemDecoration.VERTICAL))
          layoutManager = LinearLayoutManager(activity)
          adapter = fbAdapter
      }
  }

  override fun onStart() {
      super.onStart()
      fbAdapter?.startListening()
  }

  override fun onStop() {
      super.onStop()
      fbAdapter?.stopListening()
  }
}

NavigationUI loadstate issue

@15r can you explain how this is a bug in FirebaseUI?  What does this library do wrong?  RecyclerView shouldn't have anything to do with navigation.

App output
Step 01 - Open app
Step 02 - Scroll down and click USER16 item
Step 03 - Onclick navigated to UserDetails fragment and onBackPressed() Step 04 is the result.
Step 04 - See the image.

Expected output
Step 01 - Open app
Step 02 - Scroll down and click USER16 item
Step 03 - Onclick navigated to UserDetails fragment and onBackPressed() Step 04 has to the result.
Step 04 - See the image.

@samtstern find the android project for reference https://github.com/15r/Users

@15r sorry for the slow response but maybe you want to follow this guide:
https://proandroiddev.com/fui-rv-state-a66833c3bb88
I'm still not sure this is a FirebaseUI issue, sounds like a general difficulty with RecyclerView + Navigation.


Provide a way to get only the number of files or test cases that will be tested with --changed option without actually running tests

Clear and concise description of the problem
In my CI environment, I use the --changed option to run tests only on modified files for faster performance, alongside sharding for parallel processing. However, when there are few modified files and therefore a small number of tests, using sharding becomes inefficient as it consumes workers without improving performance. I want to configure the system to skip sharding when there are only a few tests and to use sharding only when there are many tests. Currently, though, there isn’t a way to determine the test load in advance.
Suggested solution
I would like a CLI command that, without actually running tests, provides the number of files or test cases that would be tested when using the --changed option.
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

There is vitest list --filesOnly: https://vitest.dev/guide/cli.html#vitest-list
You can combine it with other flags like --changed.


Tab character warning breaks stack test --pedantic

Hey, thanks for the report!
Where did you run stack test --pedantic? I could only find a tab in the Makefile.
[tasty-discover][master] λ grep -rP '\t' * | grep -Ev "(stack-work)"
Makefile:       find /tmp -name ghc* -print0 | xargs -0 rm -r

I couldn't really find what --pedantic does?

Ah, or it was perhaps the \t in the tmpModule source ...


Upgrade plugin python module to 3.9

As Python 3.8 is nearing EOL and will shortly stop getting security updates, we should upgrade the Plugin module from Python 3.8  to python 3.9.

Closing in favor of https://github.com/chanzuckerberg/napari-hub/issues/1225


[GPartition] Rename the input argument for dispatch

Issue #, if available:
Description of changes:
We now reverse the meaning of the original --do-dispatch input argument.
Successfully test with
python3 -m graphstorm.gpartition.dist_partition_graph \
    --input-path ./test-gsprocessing/ \
    --metadata-filename updated_row_counts_metadata.json \
    --output-path ./gspartition-example/ \
    --num-parts 1 \
    --dgl-tool-path ./dgl/tools \
    --partition-algorithm random \
    --ip-config ip_list.txt \
    --ssh-port 2222 \
    --partition-assignment-only

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Marking as breaking change since this changes a user-facing argument.

Changes LGTM, this better communicates intent and ensures we do the file creation by default, which is the most common use case.
Do we have integ tests for dist_partition_graph? We should in the future if not.

Let us create an issue and do it in another PR, it should request us to add some more dependencies.


Update samples repo

Generate content for our Samples repo: https://github.com/Azure/azure-cli-samples

General

[ ] Landing page
[ ] Using account (login, logout, account set, account list, configure)
[ ] Using --query and JMESPath
[ ] Using --output
[ ] Automating the CLI

Services

[ ] Network
[ ] Compute (VM and VMSS)
[x] Storage
[ ] RBAC and AD
[ ] ARM
[ ] App Service and Web App
[ ] KeyVault
[ ] Insights

Scenarios

TBD, anything that isn't likely to be covered by the service sample

Since this is not directly related to work required for the Azure CLI 2.0, I'm closing this. Feel free to open an issue somewhere else if this is for personal work item tracking.


sidecar: Timeout on high latency links

Thanos, Prometheus and Golang version used:
Version: v0.15.0
Object Storage Provider: GCS
What happened: On some queries the sidecar closes connections (nginx 499 errors and envoy_proxy http2_client reset errors). This only seems to happen to storegateways that are connected over high latency links (1000ms+) the configuration is identical otherwise.
The sidecar storageapi/object storage upload also times out.
What you expected to happen: I expect the query to succeed albeit somewhat slowly.
How to reproduce it (as minimally and precisely as possible): In my scenario I is this particular query that is causing trouble:
        sum(
        avg_over_time(node_namespace_pod_container:container_cpu_usage_seconds_total:sum_rate[24h])
        * on(namespace,pod, environment,location,name)
          group_left(workload, workload_type) namespace_workload_pod:kube_pod_owner:relabel
        * on (namespace, pod, environment,location,name) group_left(label_slack_contact) kube_pod_labels
        ) by (namespace, workload, workload_type, label_slack_contact, environment,location,name) / sum(
          avg_over_time(kube_pod_container_resource_requests_cpu_cores[24h])
        * on(namespace,pod, environment,location,name)
          group_left(workload, workload_type) namespace_workload_pod:kube_pod_owner:relabel
        * on (namespace, pod, environment,location,name) group_left(label_slack_contact) kube_pod_labels
        ) by (namespace, workload, workload_type, label_slack_contact, environment,location,name) < 0.5

Full logs to relevant components:
Nginx

{ "msec": "1613098229.442", "connection": "16756763", "connection_requests": "22", "pid": "1130", "request_id": "afbccc29b952272eacc07dc6cd69a285", "request_length": "66", "remote_addr": "<IP_ADDRESS>", "remote_user": "", "remote_port": "32577", "time_local": "12/Feb/2021:02:50:29 +0000", "time_iso8601": "2021-02-12T02:50:29+00:00", "request": "POST /thanos.Store/Info HTTP/2.0", "request_uri": "/thanos.Store/Info", "args": "", "status": "499", "body_bytes_sent": "0", "bytes_sent": "93", "http_referer": "", "http_user_agent": "grpc-go/1.29.1", "http_x_forwarded_for": "", "http_host": "thanos.toda.company.net", "server_name": "thanos.toda.company.net", "request_time": "5.116", "upstream": "<IP_ADDRESS>:10901", "upstream_connect_time": "0.000", "upstream_header_time": "0.004", "upstream_response_time": "5.116", "upstream_response_length": "555", "upstream_cache_status": "", "ssl_protocol": "TLSv1.2", "ssl_cipher": "ECDHE-RSA-AES128-GCM-SHA256", "scheme": "https", "request_method": "POST", "server_protocol": "HTTP/2.0", "pipe": ".", "gzip_ratio": "", "http_cf_ray": "", "geoip_country_code": "" }

Envoy

[2021-02-12T02:53:13.885Z] "POST /thanos.Store/Info HTTP/2" 0 - 5 0 5000 - "-" "grpc-go/1.29.1" "b06b2506-208b-4a7c-b48c-20cbdff528b3" "thanos.toda.company.net" "<IP_ADDRESS>:443"
[2021-02-12T02:53:10.212Z] "POST /thanos.Store/Series HTTP/2"
200 DC downstream_remote_disconnect 83 11493 8673
7440 "-" "grpc-go/1.29.1"

Anything else we need to know: Not that I can think of

Hey @evoicefire, Thanks for reporting. Could you share your querier configuration? And have you tried to adjust the timeout values for querier?

Hi @kakkoyun
Sure it is below. I have tried setting the timeout values to no effect (it seems the client is terminating the connections ie. sidecar ).
query --log.level=info --grpc-address=<IP_ADDRESS>:10901 --http-address=<IP_ADDRESS>:10902 --query.replica-label=replica --query.timeout=5m --store.response-timeout=5m
I've excluded the store definitions for the querier as there are many of them.

Still an issue at the moment

Still an issue
On Fri, 4 Jun 2021, 05:03 stale[bot], @.***> wrote:

Closed #3787 https://github.com/thanos-io/thanos/issues/3787.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/thanos-io/thanos/issues/3787#event-4839322207, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACR5JZQT3SJ2EHK62MB2STDTQ7GZNANCNFSM4XP6JM2A
.

I seem to be seeing the same problem -- HTTP2 stream resets over high latency links. This can probably be simulated by using tc: https://www.pico.net/kb/how-can-i-simulate-delayed-and-dropped-packets-in-linux/


Only run when contributors change

As of now the contributor-readme-bot runs on each commit or merge. Would it be possible to only run it when the list of contributor actually changes? The annoying part of it running all the time is that making two quick commits and pushes locally fails, since contributor-readme-bot gets in between them. Not sure if I'm making sense.
Thank you for a great bot, really helps push the community part of open source!

@EmilStenstrom ohhhhh really. That's a bug then I guess. Cause I trigger commit only when the readme needs to be changed. By comparing base64 of original readme and formatted one. So I am assuming there must have happened a bug. Definitely will check it. Give me two days, cause currently in another work 😢 . But will fix it asap.
Also tysm for your kind words. Much appreciated 😄

Ah, that makes sense. But then the bot will run when the README is changed for other reasons. I think that's what happened to me. I thought it ran on every commit, but the commits I looked at was other changes to README.

But still its an annoying thing agreed. I'll definitely look into this and find a solution. ✌🏽

@EmilStenstrom Can u please tell me a way to reproduce this bug. I have solved other two bugs. So planning to solve this one also in this patch

I thought the action was run each time the README was changed? In that case, changing the README should trigger it?

@EmilStenstrom  I did made a change to readme's other parts. But it waas working fine. the bot didn't updated it.

Ah, so maybe it was the newline change that triggered it? That would make sense because it was technically between the comments. Thank you for your hard work! :)


nix build is failing on Python 3.7

The nix build is failing with an error:
/nix/store/63karsgdg7fm3q0if4zfd7apbd8ac1ci-stdenv-linux/setup: line 1314: py.test: command not found
builder for '/nix/store/2iylyy9gnk9p53gsb5f954kczfkbpj1j-python3.7-pew.drv' failed with exit code 127
error: build of '/nix/store/2iylyy9gnk9p53gsb5f954kczfkbpj1j-python3.7-pew.drv' failed
The command "nix-build" exited with 100.

I know nothing about nix, so if anyone can help with this issue that would be fantastic. It looks as if py.test isn't getting installed properly, but I can't see anywhere in the nix script that says what needs to be installed :-(

Fixed.
More than 3 years ago there was only buildInputs, nixpkgs in the meanwhile added checkInputs
Now, build inputs will not be available anymore at test time (this is nice, since it pushes people to separate build and test dependencies, which means that if you don't need to run the tests you won't have to build the test dependencies either.)
Besides that, I added repository pinning, so we won't risk any new unexpected failures in the future, and yet I added a separate configuration that will automatically pick up the latest version of the nixpkgs channel (but that is marked as allowed to fail, so it won't fail the build). I enabled Travis' monthly cron, so we should be able to detect if new Nixpkgs versions will introduce other changes.


RFC: j.u.c APIs

I'm in the process of (tentatively) adding reactive-stream APIs in java.util.concurrent (targeting JDK9). The current somewhat unusual plan is nest all four interfaces inside new class Async, that will also include some other new async support stuff.  (None of the standard alternatives (creating new package or adding all four into j.u.c itself) work out very well.
A snapshot of the draft reactive-stream parts of Async.java is temporarily at
http:/gee.cs.oswego.edu/dl/wwwtmp/Async.java
It is written in standard jdk javadoc style, intending to correspond (and cites) the reactive-stream specs. But please let me know about errors or suggestions for improvement.
Also, comments welcome on a draft snapshot of one of the associated upcoming utility classes, BufferedSubmissionPublisher, that can be used as an adaptor for item generators that want to be Publishers.
http:/gee.cs.oswego.edu/dl/wwwtmp/BufferedSubmissionPublisher.java

@DougLea  parameters tag should be add to the inner interface documentation.

@DougLea  Why Async is not a final class nor interface ?

@ouertani Thanks! I added these. The missing "final" for Async was  just a mistake I made while snapshotting this to get rid of other in-progress stuff.

@DougLea I noticed the addition of an onError(CancellationException) after calling 'Subscription.cancel()`.  If every subscription must be canceled wouldn't that cause a lot of additional work to ignore these when operators are trying to unsubscribe?
https://github.com/reactive-streams/reactive-streams#user-content-2.5

@abersnaze Rule 3.15 says:
Subscription.cancel MUST NOT throw an Exception and MUST signal onError to its Subscriber
You might argue that the spec should relax the overall protocol rules to allow no response. But as stated, I think this is the only allowed reasonable implementation.

I think 3.15 was intended for a situation where an exception occurred during the cleaning up resources during the cancel() not that every cancel() should result in an onError().

Yes, @abersnaze is right, look at 3.16, perhaps we should clarify the wording to use the "Invoking Subscription.cancel MUST return normally."

OK (In some ways it is good to have a year pass between helping write specs and  implementing -- at the moment I'm just cross-checking them!). Rule 3.15 should be reworded to say that on normal return, no signals are issued.

On Tue, Jan 6, 2015 at 10:36 PM, DougLea<EMAIL_ADDRESS>wrote:

OK (In some ways it is good to have a year pass between helping write
specs and implementing -- at the moment I'm just cross-checking them!).

Also, I'm finding again and again that a "rationale"-section for each rule
would be immensely valuable.

Rule 3.15 should be reworded to say that on normal return, no signals are
issued.

I love all improvements to the spec that doesn't change the semantics but
improves the clarity :)

—
Reply to this email directly or view it on GitHub
https://github.com/reactive-streams/reactive-streams/issues/195#issuecomment-68938194
.

--
Cheers,
√

A few more notes after a touch up pass -- see
http:/gee.cs.oswego.edu/dl/wwwtmp/Async.java
and the (renamed)
http:/gee.cs.oswego.edu/dl/wwwtmp/SubmissionPublisher.java
One difference between jdk specs and r-s specs is that in cases where r-s specs say "MUST NOT X", the jdk versions say "if X, resulting behavior is undefined".  These mean almost the same thing, but the latter more clearly allows implementations to try to be helpful in their undefinedness, for example somehow reporting Subscriber exceptions that must not be thrown in compliant implementations, or, as mentioned in the current javadoc, at least auto-cancelling if onNext throws. Which as far as I can see is legal in r-s spec.

@DougLea the switch to positive wording (https://github.com/reactive-streams/reactive-streams/pull/200) is hopefully merged within a couple of days

@DougLea I'm curious about the behavior specification itself, as well as the TCK. If we port the Reactor library to use the j.u.c.Flow classes, how will we check our implementation for adherence to the spec?

Does that mean only JDK 9 libraries (and apps) will be able to be interop ? Can't we have a javax based package that just moves over the reactive-streams jar ?
I am thinking about the interop of the current libraries (not only Reactor or Akka Streams who directly implement the interfaces from RS) but also for the micro libraries popping around the net (Kafka RS, MongoDB driver, Ratpack RS) directly accepting Publisher or Subscriber as input/output. What is the point I am missing to have JDK9 JSR166 RS repackaged ?

@jbrisbin j.u.c will only provide underlying support for building useful RS components. In principle, people should independently validate Publishers that actually publish items and subscribers that actually process them. But the intent is that all straightforward usages will be guaranteed to validate.
@smaldini Two reasons:
(1) Guaranteeing that anyone using JDK9 can interoperate. This may seem too long from now, but you have to start somewhere.
(2) Without placing these interfaces in the JDK, we cannot provide core library support for them. (Or even JVM support, if it ever came to it).

@DougLea Please correct me if I am wrong:
Since j.u.c.Flow are carbon-copies of RS, it is dead simple to map it to RS—we can even provide a compat jar in RS. (Something like "reactive-streams-jdk9plus-compat-1.0.0.final.jar")
If one implements the j.u.c.Flow interfaces and want it to work on pre JDK9, one'll need to put a backport jar on your bootclasspath.

@viktorklang Yes. People have generally found it easy to replace import startements in analogous cases of moving from jsr166 pre-release/compat packages to new jdk releases.

@DougLea Given that no changes are expected in neither spec nor interfaces, I propose to close this issue and presume that the JDK9 version will be verbatim "1.0.0" interfaces + spec.
Please reopen if this is contentious in any way.


Is there support for GNURoot Debian?

I can't test it because the app tells me it's no longer being mantained, and to switch over to an app called User-LAnd. So you can't and shouldn't be using it regardless.


Could not get the stamp id. Aborting the upload process

Describe the bug
I'm running the profiler in a container in AKS. About 2 minutes fter ethe container has started i receive the following error in the logs:
 2023-11-02 19:15.11 -- info: Microsoft.Hosting.Lifetime[0]
       Hosting environment: Staging
 2023-11-02 19:15.11 -- info: Microsoft.Hosting.Lifetime[0]
       Content root path: /app
 2023-11-02 19:17.11 -- fail: Microsoft.ApplicationInsights.Profiler.Core.UploaderProxy.TraceUploaderProxy[0]
       Could not get the stamp id. Aborting the upload process.
 2023-11-02 19:17.41 -- fail: Microsoft.ApplicationInsights.Profiler.Core.ServiceProfilerProvider[0]
       Unexpected error happens on stopping service profiler.
       System.OperationCanceledException: The operation was canceled.
          at System.Threading.CancellationToken.ThrowOperationCanceledException()
          at System.Threading.CancellationToken.ThrowIfCancellationRequested()
          at System.IO.Pipes.NamedPipeClientStream.ConnectInternal(Int32 timeout, CancellationToken cancellationToke
 n, Int32 startTime)
          at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionConte
 xt executionContext, ContextCallback callback, Object state)
       --- End of stack trace from previous location ---
          at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionConte
 xt executionContext, ContextCallback callback, Object state)
          at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
       --- End of stack trace from previous location ---
          at Microsoft.ApplicationInsights.Profiler.Core.IPC.DuplexNamedPipeService.ConnectAsync(String pipeName, Ca
 ncellationToken cancellationToken)
          at Microsoft.ApplicationInsights.Profiler.Core.ServiceProfilerProvider.<>c__DisplayClass4_0.<<PostStopProc
 essAsync>b__0>d.MoveNext()
       --- End of stack trace from previous location ---
          at Microsoft.ApplicationInsights.Profiler.Core.ServiceProfilerProvider.PostStopProcessAsync(PostStopOption
 s e, CancellationToken cancellationToken)
 2023-11-02 19:17.41 -- fail: Microsoft.ApplicationInsights.Profiler.Core.ServiceProfilerProvider[0]
       Unexpected error happens on stopping service profiler tracing.
       System.OperationCanceledException: The operation was canceled.
          at System.Threading.CancellationToken.ThrowOperationCanceledException()
          at System.Threading.CancellationToken.ThrowIfCancellationRequested()
          at System.IO.Pipes.NamedPipeClientStream.ConnectInternal(Int32 timeout, CancellationToken cancellationToke
 n, Int32 startTime)
          at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionConte
 xt executionContext, ContextCallback callback, Object state)
       --- End of stack trace from previous location ---
          at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionConte
 xt executionContext, ContextCallback callback, Object state)
          at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
       --- End of stack trace from previous location ---
          at Microsoft.ApplicationInsights.Profiler.Core.IPC.DuplexNamedPipeService.ConnectAsync(String pipeName, Ca
 ncellationToken cancellationToken)
          at Microsoft.ApplicationInsights.Profiler.Core.ServiceProfilerProvider.<>c__DisplayClass4_0.<<PostStopProc
 essAsync>b__0>d.MoveNext()
       --- End of stack trace from previous location ---
          at Microsoft.ApplicationInsights.Profiler.Core.ServiceProfilerProvider.PostStopProcessAsync(PostStopOption
 s e, CancellationToken cancellationToken)
          at Microsoft.ApplicationInsights.Profiler.Core.ServiceProfilerProvider.StopServiceProfilerAsync(IProfilerS
 ource source, CancellationToken cancellationToken)
 2023-11-02 19:17.41 -- fail: Microsoft.ApplicationInsights.Profiler.Core.Orchestration.OneTimeSchedulingPolicy[0]
       Unexpected exception in the last cycle.
       System.OperationCanceledException: The operation was canceled.
          at System.Threading.CancellationToken.ThrowOperationCanceledException()
          at System.Threading.CancellationToken.ThrowIfCancellationRequested()
          at System.IO.Pipes.NamedPipeClientStream.ConnectInternal(Int32 timeout, CancellationToken cancellationToke
 n, Int32 startTime)
          at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionConte
 xt executionContext, ContextCallback callback, Object state)
       --- End of stack trace from previous location ---
          at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionConte
 xt executionContext, ContextCallback callback, Object state)
          at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
       --- End of stack trace from previous location ---
          at Microsoft.ApplicationInsights.Profiler.Core.IPC.DuplexNamedPipeService.ConnectAsync(String pipeName, Ca
 ncellationToken cancellationToken)
          at Microsoft.ApplicationInsights.Profiler.Core.ServiceProfilerProvider.<>c__DisplayClass4_0.<<PostStopProc
 essAsync>b__0>d.MoveNext()
       --- End of stack trace from previous location ---
          at Microsoft.ApplicationInsights.Profiler.Core.ServiceProfilerProvider.PostStopProcessAsync(PostStopOption
 s e, CancellationToken cancellationToken)
          at Microsoft.ApplicationInsights.Profiler.Core.ServiceProfilerProvider.StopServiceProfilerAsync(IProfilerS
 ource source, CancellationToken cancellationToken)
          at Microsoft.ApplicationInsights.Profiler.Core.Orchestration.OrchestratorEventPipe.StopProfilingAsync(SchedulingPolicy policy, CancellationToken cancellationToken)
          at Microsoft.ServiceProfiler.Orchestration.SchedulingPolicy.StartPolicyAsync(CancellationToken cancellatio
 nToken)

Application insight is working fine and are reporting the same exception so I know the instumentationkey is working.
Desktop (please complete the following information):

OS:
Package version (Microsoft.ApplicationInsights.Profiler.AspNetCore): 2.5.3
Application Insights: 2.21.0
.Net 7 (latest)
Base image: mcr.microsoft.com/dotnet/aspnet:7.0-alpine

The instrumentation key is stored in AzureAppConfig and the application is using Workload identity to access it.
I have been searching everywhere for an answer and I just can't figure out why it's not working when AI is working fine.

@Eneuman,
Thanks for reporting this issue. It looks like this is something new. I will need to spend some time to understand the setup to see if the current implementation is going to work or not:

The instrumentation key is stored in AzureAppConfig and the application is using Workload identity to access it.

When there's an update or if I need more info, I'll post a reply here.

The config setup looks like this
  public static IHostBuilder CreateHostBuilder(string[] args) =>
      Host.CreateDefaultBuilder(args)
      .ConfigureAppConfiguration(config =>
      {
        config.AddJsonFile("config/appsettings.json", optional: true);
      })
      .ConfigureWebHostDefaults(webBuilder =>
      webBuilder.ConfigureAppConfiguration((hostingContext, config) =>
      {
        var settings = config.Build();

        config.AddAzureAppConfiguration(options =>
        {
          options.Connect(new Uri(settings["AppConfig:Endpoint"]!), new DefaultAzureCredential());
          options.ConfigureKeyVault(kv =>
          {
            kv.SetCredential(new DefaultAzureCredential());
          });
        });
      })
      .UseStartup<Startup>());

Hi @Eneuman ,
I read the callstack, and the error message is: "Could not get the stamp id. Aborting the upload process. ". Based on that, I think you have configured the iKey correctly for the Profiler. Otherwise, it would be something like Please make sure the instrumentation key is valid.
Now, the part I have no clue, about is why the stamp id is not returned properly.
Let's troubleshoot that a bit.

One possible thing is authorization:

In the application insights resource, what is the value for the local auth?

Another possible issue is networking/firewall:

Could you please replace the iKey below and try to see if you could hit this endpoint, and what's the response?
HTTP GET: https://agent.azureserviceprofiler.net/api/profileragent/v4/stampid?iKey=<your-ikey>&machineName=troubleshooting

Please try to see if you could curl it within your container to run the app.

It would also help if I can check the backend telemetry. Could you please send over your instrumentation key to<EMAIL_ADDRESS>mention the url to this issue, and I will be able to look for the telemetries on the requests if they reach our backend.

Thanksl

Hi!
Local authentication is enabled.
I think the wget was successfull
This is the result:
Connecting to agent.azureserviceprofiler.net (<IP_ADDRESS>:443)
Connecting to westeurope.agent.azureserviceprofiler.net:443 (<IP_ADDRESS>:443)
saving to 'stampid?iKey=REDACTED&machineName=troubleshooting'
stampid?iKey=REDACTED 100% |************************************************************************|    24  0:00:00 ETA
'stampid?iKey=REDACTED&machineName=troubleshooting' saved

I have mailed you the iKey :)

Hi @Eneuman, I got your iKey, but I can't find any related telemetries:

We did have some high sampling(dropping telemetries) last week. Do you mind run your application again, try to upload the profile a couple of times to see if that works for you? And then I will check the telemetry again.
At the same time, I will need to check something else - maybe it is the uploader that is staled somehow.

Hi
I opened a shell to my conatiner and ran the following comand:
wget https://agent.azureserviceprofiler.net/api/profileragent/v4/stampid?iKey=REDACTED&machineName=troubleshooting
This time, the result was this:
/app $ Connecting to agent.azureserviceprofiler.net (<IP_ADDRESS>:443)
Connecting to westeurope.agent.azureserviceprofiler.net:443 (<IP_ADDRESS>:443)
wget: server returned error: HTTP/1.1 400 Bad Request

[1]+  Done(1)                    wget https://agent.azureserviceprofiler.net/api/profileragent/v4/stampid?iKey=REDACTED

Hi
I have now send about 15 mor gets :)

Hey @Eneuman, now I see what is going on, let me explain. According to the telemetry:

The profiler client is supposed to follow the redirect (307) automatically, but it isn't. A potential cause is that a newer Azure.Core package that we rely on introduced a break change lately to stop automatically following redirects. That is a known issue. That could explain the behavior (and why wget works). What I am not sure about is what brings in the new version.
Do you mind sharing the project.assets.json in your startup project (after a restore), under the folder of obj? I can do an analysis there to see which one brings in it, and see if there's a potential fix
At the same time, this could be your workaround for now, add a setting to the appsettings.json:
{
    "ServiceProfiler": {
        "Endpoint": "https://westeurope.agent.azureserviceprofiler.net/"
    }
}

Or, in your app configure store, I believe the settings could be formatted as:
ServiceProfiler:Endpoint = https://westeurope.agent.azureserviceprofiler.net/

Hi
I think you found the problem :)
Adding the key to AppConfiguration solved the problem.
Here is the file your requested.
project.assets.json

Hey @Eneuman,
This is a dependency analysis, Azure.Core is set to 1.35.0 due to multiple dependencies:

The redirect issue I mentioned was introduced at around 1.33.0. And I think that is why the auto-redirect is disabled.
We have a fix for that in our codebase already. I'll get the beta out soon and let you know.

Hi @Eneuman,
Please try out the new release and see if that works without the workaround:
https://www.nuget.org/packages/Microsoft.ApplicationInsights.Profiler.AspNetCore/2.6.0-beta1
Thanks again for reporting the issue.

What's the ETA on the Microsoft.ApplicationInsights.Profiler.AspNetCore 2.6.0 release with this fix in place?

I am having the same problem and tried the v2.6.0-beta2 but then I got another error just like in this other issue:
[18:51:37 ERR] Trace upload failed. Exit code: 137
[18:51:37 ERR] Unexpected error happens on stopping service profiler.
Microsoft.ApplicationInsights.Profiler.Core.IPC.UnsupportedPayloadTypeException: Can't deserialize message over the named pipe.
   at Microsoft.ApplicationInsights.Profiler.Core.IPC.DuplexNamedPipeService.ReadAsync[T](TimeSpan timeout, CancellationToken cancellationToken)
   at Microsoft.ApplicationInsights.Profiler.Core.ServiceProfilerProvider.<>c__DisplayClass4_0.<<PostStopProcessAsync>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.ApplicationInsights.Profiler.Core.ServiceProfilerProvider.PostStopProcessAsync(PostStopOptions e, CancellationToken cancellationToken)

[18:51:37 ERR] Unexpected error happens on stopping service profiler tracing.
Microsoft.ApplicationInsights.Profiler.Core.IPC.UnsupportedPayloadTypeException: Can't deserialize message over the named pipe.
   at Microsoft.ApplicationInsights.Profiler.Core.IPC.DuplexNamedPipeService.ReadAsync[T](TimeSpan timeout, CancellationToken cancellationToken)
   at Microsoft.ApplicationInsights.Profiler.Core.ServiceProfilerProvider.<>c__DisplayClass4_0.<<PostStopProcessAsync>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.ApplicationInsights.Profiler.Core.ServiceProfilerProvider.PostStopProcessAsync(PostStopOptions e, CancellationToken cancellationToken)
   at Microsoft.ApplicationInsights.Profiler.Core.ServiceProfilerProvider.StopServiceProfilerAsync(IProfilerSource source, CancellationToken cancellationToken)

[18:51:37 ERR] Unexpected exception in the last cycle.
Microsoft.ApplicationInsights.Profiler.Core.IPC.UnsupportedPayloadTypeException: Can't deserialize message over the named pipe.
   at Microsoft.ApplicationInsights.Profiler.Core.IPC.DuplexNamedPipeService.ReadAsync[T](TimeSpan timeout, CancellationToken cancellationToken)
   at Microsoft.ApplicationInsights.Profiler.Core.ServiceProfilerProvider.<>c__DisplayClass4_0.<<PostStopProcessAsync>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.ApplicationInsights.Profiler.Core.ServiceProfilerProvider.PostStopProcessAsync(PostStopOptions e, CancellationToken cancellationToken)
   at Microsoft.ApplicationInsights.Profiler.Core.ServiceProfilerProvider.StopServiceProfilerAsync(IProfilerSource source, CancellationToken cancellationToken)
   at Microsoft.ApplicationInsights.Profiler.Core.Orchestration.OrchestratorEventPipe.StopProfilingAsync(SchedulingPolicy policy, CancellationToken cancellationToken)
   at Microsoft.ServiceProfiler.Orchestration.SchedulingPolicy.StartPolicyAsync(CancellationToken cancellationToken)

I was having the same issue, and the beta package fixed it for me.


[BUG] ai.rapids.cudf.CudaException: an illegal instruction was encountered in databricks 9.1

Describe the bug
Integration tests failed in databricks 9.1 runtime
some results (non-deterministic)
8014 failed, 4989 passed, 171 skipped, 470 xfailed, 163 xpassed, 510 warnings, 19 errors in 6579.11s (1:49:39)
10983 failed, 2039 passed, 171 skipped, 545 xfailed, 88 xpassed, 638 warnings, 31 errors in 5842.30s (1:37:22)
[2022-01-17T12:04:17.756Z] E                   Driver stacktrace:
[2022-01-17T12:04:17.756Z] E                   	at org.apache.spark.scheduler.DAGScheduler.failJobAndIndependentStages(DAGScheduler.scala:2828)
[2022-01-17T12:04:17.756Z] E                   	at org.apache.spark.scheduler.DAGScheduler.$anonfun$abortStage$2(DAGScheduler.scala:2775)
[2022-01-17T12:04:17.756Z] E                   	at org.apache.spark.scheduler.DAGScheduler.$anonfun$abortStage$2$adapted(DAGScheduler.scala:2769)
[2022-01-17T12:04:17.756Z] E                   	at scala.collection.mutable.ResizableArray.foreach(ResizableArray.scala:62)
[2022-01-17T12:04:17.756Z] E                   	at scala.collection.mutable.ResizableArray.foreach$(ResizableArray.scala:55)
[2022-01-17T12:04:17.756Z] E                   	at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:49)
[2022-01-17T12:04:17.756Z] E                   	at org.apache.spark.scheduler.DAGScheduler.abortStage(DAGScheduler.scala:2769)
[2022-01-17T12:04:17.756Z] E                   	at org.apache.spark.scheduler.DAGScheduler.$anonfun$handleTaskSetFailed$1(DAGScheduler.scala:1305)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.scheduler.DAGScheduler.$anonfun$handleTaskSetFailed$1$adapted(DAGScheduler.scala:1305)
[2022-01-17T12:04:17.757Z] E                   	at scala.Option.foreach(Option.scala:407)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.scheduler.DAGScheduler.handleTaskSetFailed(DAGScheduler.scala:1305)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.doOnReceive(DAGScheduler.scala:3036)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:2977)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:2965)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.util.EventLoop$$anon$1.run(EventLoop.scala:49)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.scheduler.DAGScheduler.runJob(DAGScheduler.scala:1067)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.SparkContext.runJobInternal(SparkContext.scala:2476)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.sql.execution.collect.Collector.runSparkJobs(Collector.scala:264)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.sql.execution.collect.Collector.collect(Collector.scala:299)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.sql.execution.collect.Collector$.collect(Collector.scala:82)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.sql.execution.collect.Collector$.collect(Collector.scala:88)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.sql.execution.collect.InternalRowFormat$.collect(cachedSparkResults.scala:75)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.sql.execution.collect.InternalRowFormat$.collect(cachedSparkResults.scala:62)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.sql.execution.ResultCacheManager.$anonfun$getOrComputeResultInternal$1(ResultCacheManager.scala:512)
[2022-01-17T12:04:17.757Z] E                   	at scala.Option.getOrElse(Option.scala:189)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.sql.execution.ResultCacheManager.getOrComputeResultInternal(ResultCacheManager.scala:511)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.sql.execution.ResultCacheManager.getOrComputeResult(ResultCacheManager.scala:399)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.sql.execution.ResultCacheManager.getOrComputeResult(ResultCacheManager.scala:374)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.sql.execution.SparkPlan.executeCollectResult(SparkPlan.scala:406)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.sql.Dataset.$anonfun$collectToPython$1(Dataset.scala:3613)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.sql.Dataset.$anonfun$withAction$1(Dataset.scala:3825)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.sql.execution.SQLExecution$.$anonfun$withCustomExecutionEnv$5(SQLExecution.scala:130)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.sql.execution.SQLExecution$.withSQLConfPropagated(SQLExecution.scala:273)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.sql.execution.SQLExecution$.$anonfun$withCustomExecutionEnv$1(SQLExecution.scala:104)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.sql.SparkSession.withActive(SparkSession.scala:854)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.sql.execution.SQLExecution$.withCustomExecutionEnv(SQLExecution.scala:77)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.sql.execution.SQLExecution$.withNewExecutionId(SQLExecution.scala:223)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.sql.Dataset.withAction(Dataset.scala:3823)
[2022-01-17T12:04:17.757Z] E                   	at org.apache.spark.sql.Dataset.collectToPython(Dataset.scala:3611)
[2022-01-17T12:04:17.757Z] E                   	at sun.reflect.GeneratedMethodAccessor139.invoke(Unknown Source)
[2022-01-17T12:04:17.757Z] E                   	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[2022-01-17T12:04:17.757Z] E                   	at java.lang.reflect.Method.invoke(Method.java:498)
[2022-01-17T12:04:17.757Z] E                   	at py4j.reflection.MethodInvoker.invoke(MethodInvoker.java:244)
[2022-01-17T12:04:17.757Z] E                   	at py4j.reflection.ReflectionEngine.invoke(ReflectionEngine.java:380)
[2022-01-17T12:04:17.757Z] E                   	at py4j.Gateway.invoke(Gateway.java:295)
[2022-01-17T12:04:17.757Z] E                   	at py4j.commands.AbstractCommand.invokeMethod(AbstractCommand.java:132)
[2022-01-17T12:04:17.757Z] E                   	at py4j.commands.CallCommand.execute(CallCommand.java:79)
[2022-01-17T12:04:17.757Z] E                   	at py4j.GatewayConnection.run(GatewayConnection.java:251)
[2022-01-17T12:04:17.757Z] E                   	at java.lang.Thread.run(Thread.java:748)
[2022-01-17T12:04:17.757Z] E                   Caused by: ai.rapids.cudf.CudaException: an illegal instruction was encountered
[2022-01-17T12:04:17.757Z] E                   	at ai.rapids.cudf.Cuda.memcpyOnStream(Native Method)
[2022-01-17T12:04:17.757Z] E                   	at ai.rapids.cudf.Cuda.memcpy(Cuda.java:475)
[2022-01-17T12:04:17.758Z] E                   	at ai.rapids.cudf.Cuda.memcpy(Cuda.java:291)
[2022-01-17T12:04:17.758Z] E                   	at ai.rapids.cudf.BaseDeviceMemoryBuffer.copyFromHostBuffer(BaseDeviceMemoryBuffer.java:43)
[2022-01-17T12:04:17.758Z] E                   	at ai.rapids.cudf.BaseDeviceMemoryBuffer.copyFromHostBuffer(BaseDeviceMemoryBuffer.java:105)
[2022-01-17T12:04:17.758Z] E                   	at ai.rapids.cudf.HostColumnVector.copyToDevice(HostColumnVector.java:198)
[2022-01-17T12:04:17.758Z] E                   	at ai.rapids.cudf.HostColumnVector$ColumnBuilder.buildAndPutOnDevice(HostColumnVector.java:1290)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.GpuColumnVector$GpuColumnarBatchBuilder.buildAndPutOnDevice(GpuColumnVector.java:402)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.GpuColumnVector$GpuColumnarBatchBuilderBase.build(GpuColumnVector.java:277)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.RowToColumnarIterator.$anonfun$buildBatch$3(GpuRowToColumnarExec.scala:656)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.Arm.withResource(Arm.scala:28)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.Arm.withResource$(Arm.scala:26)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.RowToColumnarIterator.withResource(GpuRowToColumnarExec.scala:585)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.RowToColumnarIterator.$anonfun$buildBatch$1(GpuRowToColumnarExec.scala:655)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.Arm.withResource(Arm.scala:28)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.Arm.withResource$(Arm.scala:26)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.RowToColumnarIterator.withResource(GpuRowToColumnarExec.scala:585)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.RowToColumnarIterator.buildBatch(GpuRowToColumnarExec.scala:612)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.RowToColumnarIterator.next(GpuRowToColumnarExec.scala:608)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.RowToColumnarIterator.next(GpuRowToColumnarExec.scala:585)
[2022-01-17T12:04:17.758Z] E                   	at scala.collection.Iterator$$anon$10.next(Iterator.scala:459)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.CollectTimeIterator.$anonfun$next$1(GpuExec.scala:196)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.Arm.withResource(Arm.scala:28)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.Arm.withResource$(Arm.scala:26)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.RebaseHelper$.withResource(RebaseHelper.scala:25)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.CollectTimeIterator.next(GpuExec.scala:195)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.AbstractGpuCoalesceIterator.hasNext(GpuCoalesceBatches.scala:248)
[2022-01-17T12:04:17.758Z] E                   	at scala.collection.Iterator$$anon$11.hasNext(Iterator.scala:489)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.ColumnarToRowIterator.$anonfun$fetchNextBatch$2(GpuColumnarToRowExec.scala:240)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.Arm.withResource(Arm.scala:28)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.Arm.withResource$(Arm.scala:26)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.ColumnarToRowIterator.withResource(GpuColumnarToRowExec.scala:188)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.ColumnarToRowIterator.fetchNextBatch(GpuColumnarToRowExec.scala:239)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.ColumnarToRowIterator.loadNextBatch(GpuColumnarToRowExec.scala:216)
[2022-01-17T12:04:17.758Z] E                   	at com.nvidia.spark.rapids.ColumnarToRowIterator.hasNext(GpuColumnarToRowExec.scala:256)
[2022-01-17T12:04:17.758Z] E                   	at scala.collection.Iterator$$anon$10.hasNext(Iterator.scala:458)
[2022-01-17T12:04:17.758Z] E                   	at org.apache.spark.sql.execution.collect.UnsafeRowBatchUtils$.encodeUnsafeRows(UnsafeRowBatchUtils.scala:80)
[2022-01-17T12:04:17.758Z] E                   	at org.apache.spark.sql.execution.collect.Collector.$anonfun$processFunc$1(Collector.scala:178)
[2022-01-17T12:04:17.758Z] E                   	at org.apache.spark.scheduler.ResultTask.$anonfun$runTask$3(ResultTask.scala:75)
[2022-01-17T12:04:17.758Z] E                   	at com.databricks.spark.util.ExecutorFrameProfiler$.record(ExecutorFrameProfiler.scala:110)
[2022-01-17T12:04:17.758Z] E                   	at org.apache.spark.scheduler.ResultTask.$anonfun$runTask$1(ResultTask.scala:75)
[2022-01-17T12:04:17.758Z] E                   	at com.databricks.spark.util.ExecutorFrameProfiler$.record(ExecutorFrameProfiler.scala:110)
[2022-01-17T12:04:17.758Z] E                   	at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:55)
[2022-01-17T12:04:17.758Z] E                   	at org.apache.spark.scheduler.Task.doRunTask(Task.scala:150)
[2022-01-17T12:04:17.758Z] E                   	at org.apache.spark.scheduler.Task.$anonfun$run$1(Task.scala:119)
[2022-01-17T12:04:17.758Z] E                   	at com.databricks.spark.util.ExecutorFrameProfiler$.record(ExecutorFrameProfiler.scala:110)
[2022-01-17T12:04:17.758Z] E                   	at org.apache.spark.scheduler.Task.run(Task.scala:91)
[2022-01-17T12:04:17.758Z] E                   	at org.apache.spark.executor.Executor$TaskRunner.$anonfun$run$13(Executor.scala:813)
[2022-01-17T12:04:17.759Z] E                   	at org.apache.spark.util.Utils$.tryWithSafeFinally(Utils.scala:1605)
[2022-01-17T12:04:17.759Z] E                   	at org.apache.spark.executor.Executor$TaskRunner.$anonfun$run$4(Executor.scala:816)
[2022-01-17T12:04:17.759Z] E                   	at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:23)
[2022-01-17T12:04:17.759Z] E                   	at com.databricks.spark.util.ExecutorFrameProfiler$.record(ExecutorFrameProfiler.scala:110)
[2022-01-17T12:04:17.759Z] E                   	at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:672)
[2022-01-17T12:04:17.759Z] E                   	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[2022-01-17T12:04:17.759Z] E                   	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[2022-01-17T12:04:17.759Z] E                   	... 1 more

Tried to re-run the tests in db 9.1 on aws or azure multiple times today, and cannot reproduce.
Seems like the scheduled gpu instances of azure were not working well at that specific moment.

close this for now


Exclude compact.xbf from package if it belongs to other project

Fix #599
To support compact, I injected a to the project for framework package. It introduced problem in _ComputeAppxPackagePayload if more than two projects are references the microsoft.ui.xaml and the two projects have reference relationship too.
For example, we have two projects: C# xUnit project and C# project:
C# xUnit project reference MUX nuget, it copied Compact.xaml to obj and compiled it.
C# project reference MUX nuget, it copied Compact.xaml again.
C# xUnit project reference C# project.
When compile C# xUnit project, _ComputeAppxPackagePayload aggregate Compact.xaml from both project in target _ComputeAppxPackagePayload, and task RemoveDuplicates detects this conflicts.
This just exclude the compact.xbf from packaging if it's matching with the MSBuildProjectName

Please also add a test to the test\MUXControlsReleaseTest project somewhere to verify that the compact dictionary is appearing and the documented URL works as expected in a consuming app. The project gets built and run against both the dll-based and framework pakage-based nuget packages so this would exercise both configurations and make sure this continues to work going forward. Thanks!


Create form that accepts two numbers

Create a simple form that accepts two numbers, and print it directly. Only numbers are allowed.

Can I take this issue?


fix: remove React hydrate deprecation warning by upgrading to hydrateRoot

Pretty straight forward. Will probably do the same with the other stacks if this passes.

This stack is still using React v17.
Once we move to v18, we'll update this as well.

Ah from this tweet I had assumed the stacks were already upgraded this to react 18. My bad. Will just close this PR then.

They were, but it was reverted later on


Create  a background for CHAOSS Education Course Video Recording

We need a background that will be used while recording CHaoss Education Video
Sample:

Hi @iamkingsleey, CHAOSS Education needs a background to be used for all video recordings. Kindly help,

@peculiaruc

Member

Thank you so much @iamkingsleey . These look awesome. I like them.
One last thing, Could you please add Education in front of CHAOSS
This "CHAOSS Education"

@peculiaruc I think this would be a good issue for hacktoberfest contributions.
Ask contributors to add Education in front WDYT?

This issue has been completed. Please help me close it

Great, closing now


Error running your filter

Hello all,
my rules for an index does not get hit and I have the following error for test-rule:
Error running your filter:
TypeError("search() got multiple values for argument 'body'",)
INFO:elastalert:Note: In debug mode, alerts will be logged to console but NOT actually sent.
To send them but remain verbose, use --verbose instead.
1 rules loaded
INFO:apscheduler.scheduler:Adding job tentatively -- it will be properly scheduled when the scheduler starts
INFO:elastalert:Queried rule user deleted from cloud from 2020-01-25 07:22 UTC to 2020-01-26 23:22 UTC: 0 / 0 hits
INFO:elastalert:Queried rule user deleted from cloud from 2020-01-26 23:22 UTC to 2020-01-28 15:22 UTC: 0 / 0 hits
INFO:elastalert:Queried rule user deleted from cloud from 2020-01-28 15:22 UTC to 2020-01-30 07:22 UTC: 0 / 0 hits
INFO:elastalert:Queried rule user deleted from cloud from 2020-01-30 07:22 UTC to 2020-01-31 23:22 UTC: 0 / 0 hits
INFO:elastalert:Queried rule user deleted from cloud from 2020-01-31 23:22 UTC to 2020-02-02 15:22 UTC: 0 / 0 hits
and here is my rule
name: user deleted from cloud
type: any
index: cloud*
filter:
        - query:
            query_string:
                    query: "_type: doc"

quote your name
name: "user deleted from cloud"
type: any
index: cloud*
filter:
        - query:
            query_string:
                    query: "_type: doc"

@daichi703n
thanks for correction
it didn't resolve anything
again I won't get any hits for this index
I also tested on common field which exists on each log but it doesn't get hit

@kasramtm Sorry, I misread the logs...
Does cloud* match some index-pattern? Please test with full index name? not cloud*, cloud-xxx(your index name).
index name is able to be check with curl http(s)://<elasticsearch>:<port>/_cat/indices

you really helped me!!
I used curl with my elastalert user and surprisingly got nothing !!
the problem is I am superuser in kibana and work properly with that index but my elastalert user didn't have permission on that index!
again thx for your quick help and reply