Whisper support

Is support for Whisper on the roadmap? Something like https://github.com/ggerganov/whisper.cpp would be great.

Supporting encoder-decoder models is in our roadmap as mentioned in #187. Feel free to join the discussion and potentially contribute!

+1 for this feature

+2 for this feature

+3 for this feature

+555

+1

+1

monitoring

@zhuohan123 I am working on Whisper support.

NO WAY!!!!!!!!!!!!!!!!!!!   THAT WILL BE AWESOME!!!!!!!!!!!!!!!!!!!!!

I am working on this PR, and will soon submit the draft.

THIS IS GOING TO BE HUGE, THX!

Hey @libratiger, I am now working full-time on the same target. Would you like to sync? It would be more efficient to share knowledge, rather than develop the same thing in two silos.

You're right. I've just discovered a discussion about T5 https://github.com/vllm-project/vllm/issues/187#issuecomment-1825244021 , where there are differing opinions on the encoder-decoder model. Perhaps it will improve after that PR is merged?

@dbogunowicz any update on this issue? looking forward

Hi! I am working on the Whisper on our team fork: https://github.com/neuralmagic/nm-vllm/pull/147
The status is: I am running the inference (both prompt prefill as well as autoregressive inference), but I get correctness issues, most likely caused by the erroneous attention mask implementation.

@dbogunowicz  Ok, thank you. Hope it can be used soon

same here, this is going to be really cool!

@dbogunowicz thanks for your work on Whisper! Since there is clearly interest in this feature and its completion timeline, I want to add the context that Whisper support takes a dependency on encoder/decoder support
https://github.com/vllm-project/vllm/issues/187
https://github.com/vllm-project/vllm/pull/3117
which is also WIP (currently works partially but is not quite complete.) I expect to complete encoder/decoder support soon. JFYI for anyone interested in timelines.

+1

See the encoder/decoder support issue (https://github.com/vllm-project/vllm/issues/187) and PR (https://github.com/vllm-project/vllm/pull/4289) for a status update on encoder/decoder support, which is a prereq for Whisper support.

Hi, any update on serving faster-whisper via VLLM?

Hi, any update on serving faster-whisper via VLLM?

Hi @twicer-is-coder ,
Whisper (or any variant thereof) is high of the list of models to add once infrastructure support is in; you can see the roadmap for infrastructure support in this PR:
https://github.com/vllm-project/vllm/pull/4942

FYI, encoder decoder support landed in #4942 and there is an RFC for follow-on encoder/decoder-related tasks, including adding Whisper support. See https://github.com/vllm-project/vllm/issues/187#issuecomment-2278777339

are you kidding me?  is whisper supported now by vllm?

are you kidding me?  is whisper supported now by vllm?

Adding Whisper support will hopefully follow shortly now that we have the encoder/decoder infrastructure landed.

DUDE THIS WILL BE HUGE

I am waiting for this update !!!!

Waiting for this support more than GTA

Do we have any estimates on roadmap/timing on this? Much sought after by us too :)

See:

https://github.com/vllm-project/vllm/issues/7366 for the RFC on encoder-decoder models
https://github.com/vllm-project/vllm/pull/5964 for the PR adding initial Whisper support

Can I help implementing this feature? If someone is already implementing this, let me know, and I will assist you in any coding way possible.

How is this feature looking?


fix bug: rename duplicated loss name

While users use a shared layer to get two different outputs but have one same name, the batch_logs/epoch_logs will only left one loss, because it's a dict.
import numpy as np
from keras.models import *
from keras.layers import *

train_d = np.random.rand(128, 64)
test_d  = np.random.rand(2, 128, 32)

x = Input(shape=(64, ))
a = Dense(32)(x)
b = Dense(32)(x)

shared_dense = Dense(32, name='shared_dense')
out1 = shared_dense(a)
out2 = shared_dense(b)

model = Model(input=x, output=[out1, out2])
model.compile(optimizer='rmsprop', loss='mse')

his = model.fit(train_d, [test_d[0], test_d[1]])

The code above will get output like below, but it should have two shared_dense_loss.

To solve this problem, I rename the duplicates name by appending it a number. Then it works well:

@fchollet Hi, I just rewrite the code. What do you think of it?

LGTM


Conda environment bin directory not in PATH for conda steps

When exploring possible uses for metaflow, I ran into unexpected behaviour with conda steps whereby subprocess calls to commands I'd expect to be available (as if the conda env were active) would fail. This minimal example shows a reproduction as well as a workaround.

Contents of ffmpeg.py
import subprocess
import os
import sys
from functools import wraps

from metaflow import FlowSpec, step, conda, conda_base

def conda_bin_path_decorator(f):
    @wraps(f)
    def wrapper(*args, **kwds):
        bin_dir = os.path.join(sys.exec_prefix, 'bin')
        old = os.environ.get('PATH')
        os.environ['PATH'] = bin_dir + os.pathsep + (old or '')
        try:
            return f(*args, **kwds)
        finally:
            if old is None:
                del os.environ['PATH']
            else:
                os.environ['PATH'] = old
    return wrapper

@conda_base(python='3.8.4', libraries={'boto3': '1.14.47', 'click': '7.1.2', 'requests': '2.24.0', 'coverage': '5.2.1'})
class FFMpegFlow(FlowSpec):
    """
    Example flow
    """
    @conda(libraries={'ffmpeg': '4.3.1'})
    @step
    def start(self):
        """
        Determine ffmpeg version
        """
        self.ffmpeg_which = subprocess.check_output(['which', 'ffmpeg']).decode()
        self.ffmpeg_version = subprocess.check_output(['ffmpeg', '-version']).decode()
        print(self.ffmpeg_which)
        print(self.ffmpeg_version)
        self.next(self.end)

    @conda(disabled=True)
    @step
    def end(self):
        """
        The end.
        """
        print("end")

if __name__ == '__main__':
    FFMpegFlow()

Running this command generates this output
❯ CONDA_CHANNELS=conda-forge python ffmpeg.py --environment=conda run
Metaflow 2.2.2 executing FFMpegFlow for user:andrew
Validating your flow...
    The graph looks good!
Running pylint...
    Pylint is happy!
2020-08-23 14:54:32.889 Bootstrapping conda environment...(this could take a few minutes)
2020-08-23 14:54:34.518 Workflow starting (run-id<PHONE_NUMBER>512993):
2020-08-23 14:54:35.341 [1598208874512993/start/1 (pid 47515)] Task is starting.
2020-08-23 14:54:35.675 [1598208874512993/start/1 (pid 47515)] <flow FFMpegFlow step start> failed:
2020-08-23 14:54:35.676 [1598208874512993/start/1 (pid 47515)]     Internal error
2020-08-23 14:54:35.676 [1598208874512993/start/1 (pid 47515)] Traceback (most recent call last):
2020-08-23 14:54:35.676 [1598208874512993/start/1 (pid 47515)]   File "/tmp/tmppfe3jjqy/metaflow/cli.py", line 883, in main
2020-08-23 14:54:35.676 [1598208874512993/start/1 (pid 47515)]     start(auto_envvar_prefix='METAFLOW', obj=state)
2020-08-23 14:54:35.676 [1598208874512993/start/1 (pid 47515)]   File "/Users/andrew/miniconda3/envs/metaflow_FFMpegFlow_osx-64_eda4fdb429ee6f1e9fc77800c944948b4508d386/lib/python3.8/site-packages/click/core.py", line 829, in __call__
2020-08-23 14:54:35.676 [1598208874512993/start/1 (pid 47515)]     return self.main(args, kwargs)
2020-08-23 14:54:35.676 [1598208874512993/start/1 (pid 47515)]   File "/Users/andrew/miniconda3/envs/metaflow_FFMpegFlow_osx-64_eda4fdb429ee6f1e9fc77800c944948b4508d386/lib/python3.8/site-packages/click/core.py", line 782, in main
2020-08-23 14:54:35.676 [1598208874512993/start/1 (pid 47515)]     rv = self.invoke(ctx)
2020-08-23 14:54:35.676 [1598208874512993/start/1 (pid 47515)]   File "/Users/andrew/miniconda3/envs/metaflow_FFMpegFlow_osx-64_eda4fdb429ee6f1e9fc77800c944948b4508d386/lib/python3.8/site-packages/click/core.py", line 1259, in invoke
2020-08-23 14:54:35.676 [1598208874512993/start/1 (pid 47515)]     return _process_result(sub_ctx.command.invoke(sub_ctx))
2020-08-23 14:54:35.676 [1598208874512993/start/1 (pid 47515)]   File "/Users/andrew/miniconda3/envs/metaflow_FFMpegFlow_osx-64_eda4fdb429ee6f1e9fc77800c944948b4508d386/lib/python3.8/site-packages/click/core.py", line 1066, in invoke
2020-08-23 14:54:35.676 [1598208874512993/start/1 (pid 47515)]     return ctx.invoke(self.callback, ctx.params)
2020-08-23 14:54:35.676 [1598208874512993/start/1 (pid 47515)]   File "/Users/andrew/miniconda3/envs/metaflow_FFMpegFlow_osx-64_eda4fdb429ee6f1e9fc77800c944948b4508d386/lib/python3.8/site-packages/click/core.py", line 610, in invoke
2020-08-23 14:54:35.676 [1598208874512993/start/1 (pid 47515)]     return callback(args, kwargs)
2020-08-23 14:54:35.676 [1598208874512993/start/1 (pid 47515)]   File "/Users/andrew/miniconda3/envs/metaflow_FFMpegFlow_osx-64_eda4fdb429ee6f1e9fc77800c944948b4508d386/lib/python3.8/site-packages/click/decorators.py", line 33, in new_func
2020-08-23 14:54:35.676 [1598208874512993/start/1 (pid 47515)]     return f(get_current_context().obj, args, kwargs)
2020-08-23 14:54:35.677 [1598208874512993/start/1 (pid 47515)]   File "/tmp/tmppfe3jjqy/metaflow/cli.py", line 437, in step
2020-08-23 14:54:35.677 [1598208874512993/start/1 (pid 47515)]     task.run_step(step_name,
2020-08-23 14:54:35.677 [1598208874512993/start/1 (pid 47515)]   File "/tmp/tmppfe3jjqy/metaflow/task.py", line 394, in run_step
2020-08-23 14:54:35.677 [1598208874512993/start/1 (pid 47515)]     self._exec_step_function(step_func)
2020-08-23 14:54:35.677 [1598208874512993/start/1 (pid 47515)]   File "/tmp/tmppfe3jjqy/metaflow/task.py", line 47, in _exec_step_function
2020-08-23 14:54:35.677 [1598208874512993/start/1 (pid 47515)]     step_function()
2020-08-23 14:54:35.677 [1598208874512993/start/1 (pid 47515)]   File "ffmpeg.py", line 36, in start
2020-08-23 14:54:35.677 [1598208874512993/start/1 (pid 47515)]     self.ffmpeg_which = subprocess.check_output(['which', 'ffmpeg']).decode()
2020-08-23 14:54:35.677 [1598208874512993/start/1 (pid 47515)]   File "/Users/andrew/miniconda3/envs/metaflow_FFMpegFlow_osx-64_eda4fdb429ee6f1e9fc77800c944948b4508d386/lib/python3.8/subprocess.py", line 411, in check_output
2020-08-23 14:54:35.677 [1598208874512993/start/1 (pid 47515)]     return run(popenargs, stdout=PIPE, timeout=timeout, check=True,
2020-08-23 14:54:35.724 [1598208874512993/start/1 (pid 47515)]   File "/Users/andrew/miniconda3/envs/metaflow_FFMpegFlow_osx-64_eda4fdb429ee6f1e9fc77800c944948b4508d386/lib/python3.8/subprocess.py", line 512, in run
2020-08-23 14:54:35.724 [1598208874512993/start/1 (pid 47515)]     raise CalledProcessError(retcode, process.args,
2020-08-23 14:54:35.724 [1598208874512993/start/1 (pid 47515)] subprocess.CalledProcessError: Command '['which', 'ffmpeg']' returned non-zero exit status 1.
2020-08-23 14:54:35.724 [1598208874512993/start/1 (pid 47515)]
2020-08-23 14:54:35.726 [1598208874512993/start/1 (pid 47515)] Task failed.
2020-08-23 14:54:35.726 Workflow failed.
2020-08-23 14:54:35.727 Terminating 0 active tasks...
2020-08-23 14:54:35.727 Flushing logs...
    Step failure:
    Step start (task-id 1) failed.

If I instead decorate step with the provided `conda_bin_path_decorator`, the flow succeeds.

❯ CONDA_CHANNELS=conda-forge python ffmpeg.py --environment=conda run
Metaflow 2.2.2 executing FFMpegFlow for user:andrew
Validating your flow...
    The graph looks good!
Running pylint...
    Pylint is happy!
2020-08-23 14:53:46.186 Bootstrapping conda environment...(this could take a few minutes)
2020-08-23 14:54:09.638 Workflow starting (run-id<PHONE_NUMBER>632252):
2020-08-23 14:54:10.582 [1598208849632252/start/1 (pid 47211)] Task is starting.
2020-08-23 14:54:16.766 [1598208849632252/start/1 (pid 47211)] /Users/andrew/miniconda3/envs/metaflow_FFMpegFlow_osx-64_eda4fdb429ee6f1e9fc77800c944948b4508d386/bin/ffmpeg
2020-08-23 14:54:16.817 [1598208849632252/start/1 (pid 47211)]
2020-08-23 14:54:16.817 [1598208849632252/start/1 (pid 47211)] ffmpeg version 4.3.1 Copyright (c) 2000-2020 the FFmpeg developers
2020-08-23 14:54:16.817 [1598208849632252/start/1 (pid 47211)] built with clang version 10.0.1
2020-08-23 14:54:16.817 [1598208849632252/start/1 (pid 47211)] configuration: --prefix=/Users/andrew/miniconda3/envs/metaflow_FFMpegFlow_osx-64_eda4fdb429ee6f1e9fc77800c944948b4508d386 --cc=x86_64-apple-darwin13.4.0-clang --disable-doc --disable-openssl --enable-avresample --enable-gnutls --enable-gpl --enable-hardcoded-tables --enable-libfreetype --enable-libopenh264 --enable-libx264 --enable-pic --enable-pthreads --enable-shared --enable-static --enable-version3 --enable-zlib --enable-libmp3lame
2020-08-23 14:54:16.817 [1598208849632252/start/1 (pid 47211)] libavutil      56. 51.100 / 56. 51.100
2020-08-23 14:54:16.817 [1598208849632252/start/1 (pid 47211)] libavcodec     58. 91.100 / 58. 91.100
2020-08-23 14:54:16.817 [1598208849632252/start/1 (pid 47211)] libavformat    58. 45.100 / 58. 45.100
2020-08-23 14:54:16.817 [1598208849632252/start/1 (pid 47211)] libavdevice    58. 10.100 / 58. 10.100
2020-08-23 14:54:16.818 [1598208849632252/start/1 (pid 47211)] libavfilter     7. 85.100 /  7. 85.100
2020-08-23 14:54:16.818 [1598208849632252/start/1 (pid 47211)] libavresample   4.  0.  0 /  4.  0.  0
2020-08-23 14:54:16.818 [1598208849632252/start/1 (pid 47211)] libswscale      5.  7.100 /  5.  7.100
2020-08-23 14:54:16.818 [1598208849632252/start/1 (pid 47211)] libswresample   3.  7.100 /  3.  7.100
2020-08-23 14:54:16.818 [1598208849632252/start/1 (pid 47211)] libpostproc    55.  7.100 / 55.  7.100
2020-08-23 14:54:16.818 [1598208849632252/start/1 (pid 47211)]
2020-08-23 14:54:16.821 [1598208849632252/start/1 (pid 47211)] Task finished successfully.
2020-08-23 14:54:16.826 [1598208849632252/end/2 (pid 47257)] Task is starting.
2020-08-23 14:54:17.365 [1598208849632252/end/2 (pid 47257)] end
2020-08-23 14:54:17.415 [1598208849632252/end/2 (pid 47257)] Task finished successfully.
2020-08-23 14:54:17.416 Done!

So, my question is should this be handled already by the metaflow conda decorator or should we be doing this extra PATH manipulation ourselves if we need access to entrypoints / cli commands that we might want to call through subprocess?

Good point! We should add this in. @jasonge27 can you take care of this?

Thanks for reporting the issue! As a quick workaround, you can use ffmpeg_path = os.path.join(os.path.dirname(sys.executable), 'ffmpeg') to specify the right executable inside a conda step.
I am a bit hesitant to change the PATH env variable for the whole step as it may have other unintended side effects. As least it could break backward compatibility with some existing metaflow projects. We will figure out a better solution in a future release.
The following code works on my computer:
import subprocess
import os
import sys
from functools import wraps

from metaflow import FlowSpec, step, conda, conda_base

@conda_base(python='3.8.4', libraries={'boto3': '1.14.47', 'click': '7.1.2', 'requests': '2.24.0', 'coverage': '5.2.1'})
class FFMpegFlow(FlowSpec):
    """
    Example flow
    """
    @conda(libraries={'ffmpeg': '4.3.1'})
    @step
    def start(self):
        """
        Determine ffmpeg version
        """
        ffmpeg_path = os.path.join(os.path.dirname(sys.executable), 'ffmpeg')
        self.ffmpeg_version = subprocess.check_output([ffmpeg_path, '-version']).decode()
        print(self.ffmpeg_version)
        self.next(self.end)

    @conda(disabled=True)
    @step
    def end(self):
        """
        The end.
        """
        print("end")

if __name__ == '__main__':
    FFMpegFlow()

That’s ultimately fine with me. Since I can easily write such a decorator or use the explicit form this isn’t a blocker. It may be useful to have an example or documentation for this, as a new user it took a bit of investigation to understand what was going on.
I would caution though that any projects that would break due to this are likely already erroneously calling a system executable that may be in both the conda env and the system PATH.
A non breaking solution might be a flag on the conda decorator to opt in to this behavior? (With future plans to make it default?)
(Also please note the conda deco logic above was just a hack and is not as robust as we may want since it assumes no changes to PATH occurs within the inner call, which may be wrong.)

Thank you @hajapy for the comments. We decide to add conda bin path to PATH in conda steps. Here's the PR https://github.com/Netflix/metaflow/pull/307. It will come out in the next release.

@jasonge27 I have run into an issue with the solution, in that it does not seem to work when executing in batch. I think the problem is that the block is conditional on not being run within a batch context:
https://github.com/Netflix/metaflow/blob/46a3a8e6804300f639e12946b50cca4fa5efe23b/metaflow/plugins/conda/conda_step_decorator.py#L229-L242
Do you have a recommended approach to addressing this? I can work around it with my above solution, but it seems perhaps this is not as fixed as was thought.


Wakatime stats public and still not showing

my stats are not showing I made it public and the username is also right I tried it with @ and onetime without @ and its not working

Hello @prncAzula, I checked your repository. You are using https://github.com/anuraghazra/github-readme-stats project. Also if you are trying to add that stat, it is working and I can see it right now.

Instead, if you are trying to add my project stat in your profile then you need to follow instructions in README in this project. Feel free to ask if you have any doubts.

I am closing this issue if you do not have any further queries. Feel free to reopen if needed.


audio  to text converter

why dont we add an option which enables the users not only type the content  but also using audio we can make the notes
please assign me with this task

kindly explain the technologies you're gonna use to implement this

Hi @yashmandi  , we can use Web Speech API for this, we can have a button as start recording which when clicked by user will start recording user data and button will change into stop recording and when user is done, he/she will click on stop recording and we will save the transcript as a note.
-- For saving it we can have a useState hook as string which will eventually store the text and we can save it in db as we save normal notes.
-- we can transcribe the user's audio into text real-time or when user stops recording.
I would like to work on this feature, please assign it to me.
Or you can assign to umesh, this approach will work.

Yeah I also thought in the same way  but I was not that expert in backend so I doubt whether I can do this in efficient way

no need to worry about the backend! The backend won’t need any significant changes since we’ll be treating the transcribed text just like a regular note. We’ll send the transcribed text to the same API endpoint we’re using for saving normal notes, so the database logic remains the same. If you’re unfamiliar with setting up API routes in Express or need any help, feel free to reach out. I can assist with setting up or modifying the routes to handle this smoothly. Let me know if that works!

Then I will definitely try to do it

hi @prateek2102 , i got your approach, that's good. but i'm assigning @umesh-chilukuri for this task, we'll see how he works on it, if it does'nt meet the requirements, i will assign this task to you ;)
@umesh-chilukuri you can work on this

Thanks for the opportunity

hi @prateek2102 , i got your approach, that's good. but i'm assigning @umesh-chilukuri for this task, we'll see how he works on it, if it does'nt meet the requirements, i will assign this task to you ;)
@umesh-chilukuri you can work on this

Perfect. Best of luck Umesh

thanks man just now completed the task and also learn some new concepts

Add labels and please assign me the task as for gssoc24 extd

@theashikagupta i hope it is completed? else u can assign it to me

@umesh-chilukuri I closed your PR bcz of merge conflicts raise a new pr with screen recording by tomorrow .

u can work on this @prateek2102

you can assign this task to me..


Features Request

Option on "run" to set the container to "fixed" (running without --rm)

Option on "run" to set environment variables


fix: update Kafka prices

What this PR does / why we need it:
Updates the pricing for the Kafka Overview page V2.
Verification steps
Stories for the App Services section have been reorganized a bit to reduce the number of clicks to reach them. For the above change, the relative story is App Services > Kafka Page V2
The relevant copy changes are here https://github.com/redhat-developer/app-services-ui-components/pull/339/files#diff-f1147ddb89bb5329e04408f72041aa062f1c7d6ee95183393889095bac79c49b

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


DSA <IP_ADDRESS> Array Rearrangement Circular arrays

Description
Circular array problem(Maximize sum, maximize difference), left and right shift on the circular array.
Task

[ ] Documentation
[ ] Audio
[ ] Video

Note

While requesting the issue to be assigned, please mention your NAME & BATCH NUMBER.
Kindly refer to Issue Guidelines.
In case you see that the issue has already been assigned, try to request for a different task within the same issue.
Changes should be made inside the DSA/directory & DSA branch.
Name of the file should be same as the issue.
This issue is only for 'GWOC' contributors of 'DSA' Domain.

I hold a good experience in DSA since past year and can present a welll structured documentation on the same.
Could u please assign it to me. @pjdurden
AYUSHI CHAUHAN
Barch-01

I have good knowledge of dsa i can contribute to the documentation please assign this to me!

I would like to work on this issue via the Documentation part .
dsa batch 3
preeti yadav

@preeti-14-7 Go for it, Assigned to you


set packageManager field in package.json for corepack

git log -S '"packageManager"' shows no history of this field ever being set, except in this commit. We use it in the docs repo, is there a reason we haven't used it here yet? If no explicit reason no then this makes working with corepack nicer

We use it in the docs repo

to be fair, iirc we only started to use it there because it's the only way to tell netlify which version to use (also works via corepack though).

We use it in the docs repo

to be fair, iirc we only started to use it there because it's the only way to tell netlify which version to use (also works via corepack though).

ah ok. my recent version of corepack is automatically adding this field to every package.json if it doesn't exist for yarn, npm, pnpm for all my repos


Configurable transaction timeout for sdkClient

Problem
There is no configurable timeout for the sdkClient. It is currently hardcoded to 10s
Solution
Make it possible to configure the transaction timeout period in the sdkClient. Depends on: https://github.com/hashgraph/hedera-sdk-js/issues/1276
Alternatives
No response

timeout support was added to relay


No "returns" tag for named return values

Simple example:
    /// <summary>
    /// Description for DoSomething.
    /// </summary>
    /// <param name="Cust">Parameter of type Record Customer.</param>
    /// <returns>Return variable "Decimal".</returns>
    local procedure DoSomething(var Cust: Record Customer): Decimal
    var
        myInt: Integer;
    begin
        exit(Cust.Balance);
    end;

    /// <summary>
    /// Description for DoSomething2.
    /// </summary>
    /// <param name="Cust">Parameter of type Record Customer.</param>
    local procedure DoSomething2(var Cust: Record Customer) Returnvalue: Decimal
    var
        myInt: Integer;
    begin
        Returnvalue := Cust.Balance;
    end;

/// Return variable "Decimal".
is missing.
Love your extension btw! :D

Thank you for reporting. This is a bug in our signature recognition, we will fix it as soon as possible.
The next version will take some time as we are currently redesigning the extension. We are doing this because of the upcoming release of version BC17 / AL6, which also supports basic documentation functions.


Workbox codelab 👩🔬

Library Affected:
workbox-sw, workbox-build, etc.
Task
Write a codelab for Workbox that takes users through the flow of setting it up for precaching and runtime caching. Perhaps something not using Web Components as we already have a codelab using Web Components and Workbox by Keanu that he'll update separately.
*Ideas

Update the existing sw-precache codelab
Modify an existing codelab to use Workbox like this migration one
Create a new codelab that walks through using Workbox on a new app

Perhaps my only feedback on the current sw-precache codelab is that because its using airhorner its pretty simplistic. That might be fine, but it would also be nice to highlight an app that's a little more dynamic. I also think the current codelab around migrating to a PWA is pretty great as is because it's a pretty straight-forward intro to raw Service Workers and it can be valuable to show this off.
How would you feel about a codelab around a new/different app, @samthor? 🙃

Done via ILT.


[SMALLFIX] Clean up in core module

Small clean up of some classes in the core module.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/10217/
Test PASSed.

LGTM, thanks for the cleanups!


Fixed DNS instruction issues

instructions indicated a CNAME record should be created but specified an IP address. CNAME records for the adding an additional name a DNS name goes by, but A records are intended for IP addresses.
Also fixed minor grammar / syntax issues, and added a note specifying that if IPv6 was used, an additional AAAA record should be created.

#sign-off


Method of dynamically adding data sources

  Fragment 3 libraries, this time need to add to 5 libraries, this time you must modify the code to achieve it? Can you add it dynamically, do not need to restart the application.
  分片3个库,这个时候需要添加到5个库,这个时候必须修改代码才能实现么?能否动态添加呢,不需要重启应用呢.

Can you make English more understanding and remove Chinese words?

Please create new issue if you want discuss and make sure English can be understand, thank you.

i have the same question,now because our datasource config is dead write in config yaml file,can program dynamic config the datasource by listener outside order？


Incorrect indentation

Description:
Refer the below image in [1]. Corresponding .md file is [2]. Without indentation it doesn't look like it belongs to the bullet point of GitHub

[1] https://docs.dv.choreo.dev/integrations/integration-concepts/
[2] https://github.com/wso2/docs-choreo-dev/blob/dev/en/docs/integrations/integration-concepts.md
Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

Fixed via https://github.com/wso2/docs-choreo-dev/pull/28.


Manual entry of burst altitude in predictions.

If I remember well, there was an option to manually enter the burst altitude used by prediction for a given site.  I miss that option very much, as now model got the burst altitude probably based on average for longer period and this lead to some great inaccuracies. We never know when exactly the baloon will burst,  but if the prediction get average from smaller period, let say 3 days, I suppose it will be more adequate. Or better to have a field to enter manually a different than suggested value of burst altitude.
73!

The predictions are run in the sondehub backend, based on our launch site database, so adjusting these values 'on the fly' is not really practical.  The averaging is also done as a 'batch' job, not automatically, so running that over the last few days of data is also not easy to do - we would prefer that there is some human input into the chosen values too, to ensure they don't end up with some weird values.
There was never an option for manually entering in the prediction data - maybe you are thinking of the SondeHub Launch Site Modification Suggestion Form (which is accessed from each of the launch site popups), or perhaps the per-payload prediction settings on amateur.sondehub.org.
If you want to be able to customise the predictions on a per-flight basis, then I'd suggest running something like ChaseMapper at your station, where you can adjust the prediction parameters however you like. I believe the rdz_ttgo_sonde livemap also has custom prediction settings.

Thank you, you are 100% correct on everything. And yes, I mixed up with amateur.sondehub.org, but will take a look at the ChaseMapper. RDZ livemap have also that settings, but for the current fly, no prediction for the next few days. I have observed that under some conditions:
even sondes that usually goes higher to 35km, as Vienna for example, sometimes they burst earlier at lower altitude and when this happens usually happens also to the nearest sites, maybe it could be something related to the pressure at higher altitudes, never researching deeply the reason, but my observations is confirmed few times and I don't think it is just a coincidence, but not 100% sure.
73!

Just to be sure that I am explained well what I mean:
If it is possible the "Average burst altitude" to be in a editable field, so when we press generate predictions they to be generated with burst altitude from that field.
Not important, but could be useful for better short-term prediction for the next few days.

I would prefer to not add custom fields to that popup box.
If you want to do forward-looking predictions for a launch site using custom burst altitude (and I guess descent rate) parameters, then the appropriate tool is https://predict.sondehub.org
For live predictions, then Chasemapper is the appropriate tool.

Yeeees, that was the tool I searching for and somehow miss it.
Thaaaaank you, great!


node-exporter

I apply this:https://github.com/NVIDIA/gpu-monitoring-tools/blob/master/exporters/prometheus-dcgm/k8s/node-exporter/gpu-node-exporter-daemonset.yaml , show failed from pod logs
root@XP005:/home/gpu-monitoring-tools# kubectl logs -f node-exporter-c99c5 -c nvidia-dcgm-exporter
Starting NVIDIA host engine...
Failed to start host engine server
Collecting metrics at /run/prometheus/dcgm.prom every 1000ms...
Stopping NVIDIA host engine...
Host engine successfully terminated.
Done

why?

Did you follow all the pre-reqs listed here https://github.com/NVIDIA/gpu-monitoring-tools/tree/master/exporters/prometheus-dcgm/k8s/pod-gpu-metrics-exporter#prerequisites and the supported GPU
https://github.com/NVIDIA/gpu-monitoring-tools/tree/master/exporters/prometheus-dcgm#dcgm-supported-gpus

Running the exporter on a supported GPU with all pre-reqs in place should solve it. Closing for now. Re-open if the problem still persists.


Update Alchemy Key

We're making sure any SDK or demo that uses Alchemy should be using the same super key.
PM me for the Alchemy key you should be using.

Just emailed you. Thanks for letting us know!


too high non-sense read fraction

When i run:
python longQC.py sampleqc -x pb-hifi -o longqc ccs.bam
I get a message saying too high non-sense read fraction
Non-sense fraction is 0.647
but if I use:
python longQC.py sampleqc -x pb-sequel -o longqc ccs.bam
Non-sense fraction goes down to 0.282
I a trying to analyse a Sequel II Hifi run, which result would be the correct one?
It looks like the only thing that changes for minimap2-coverage are the database kmer size parameter?
HiFi : -k 15
Sequel : -k 12

Hi @grpiccoli,
Thank you for your interest in LongQC.
If your data is HiFi, I mean expected error rate is Q20 or better, the first option is the one. -k 12 is too short for HiFi from our statistics. I'm wondering the coverage might be still insufficient for your target genome/transcriptiome/etc. How coverage plots looks like?
Yoshinori

FastQC tells me I got between Q35 and Q80 but the average is >Q40
Here are the coverage plots using pb-hifi

And here using pb-sequel

And here is the k-mer coverage analysis I got from genomeScope

Let me close this issue. When you encounter problem in this context, feel free to reopen.
Thank you.
Y.


Remove typing from noChange

Removed redundant typing

Ping @rictic @justinfagnani

Thanks @rictic!

np, thanks for the cleanup @stramel :)


Dynamic course grade and category averages

I've had a go at delivering #239 - dynamic course grade and category columns.
This PR relies on PR #245 for the course grade cell refactor.
I've introduced a page scoped event ScoreChangedEvent which is broadcast upon a score changing.  The course grade and category average labels listen for this event and refresh their values upon receiving an event for their studentUuid and/or categoryId.
I have a feeling this solution adds those service calls to the critical path of the input switching back to a label.  But given the async nature of editing, perhaps that won't be too annoying for the user.  Let me know what you think @steveswinsburg.

I'm in a diff branch ATM, but I'm happy to merge this in and test it out if you are confident? I don't think there is a way around adding those service calls to the label switch, it's probably ok. Maybe if it gets slow we can add a throbber. Let me know and we can get it in.

Cool! I feel pretty good about it.  The only issue I found while testing was that businessService.getCourseGrade would return null if course grades were not released to students.  Is there a more reliable way to pull that back for a single student?

Yep this looks good to me. Loving the events. Sorry it took so long to get to the review :grapes:
We need a few more business methods to support getting the new course grade/category score for a single student. Anything else?
Reckon we can merge this then work on rewiring those methods. WDYT?

Hey @steveswinsburg, I think we can merge as is for some testing and feedback.  I've created two new issues to re-assess the service endpoints to better facilitate this feature, so we can use those as "caveats" for the current solution ;)

OK this one is in :)


Build Error: Paho-MQTT

CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:43 (message):
Command failed: C:/Program Files/CMake/bin/cmake.exe;C:/src/vcpkg/buildtrees/paho-mqtt/src/paho.mqtt.c-1.1.0;-DPAHO_
WITH_SSL=TRUE;-DBUILD_SHARED_LIBS=OFF;-DVCPKG_TARGET_TRIPLET=x86-windows-static;-DCMAKE_CXX_FLAGS= /DWIN32 /D_WINDOWS /W
3 /utf-8 /GR /EHsc /MP ;-DCMAKE_C_FLAGS= /DWIN32 /D_WINDOWS /W3 /utf-8 /MP ;-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON;-DCMAK
E_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON;-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON;-DCMAKE_INSTALL_SYSTEM_RUNTIME_
LIBS_SKIP=TRUE;-DCMAKE_VERBOSE_MAKEFILE=ON;-DVCPKG_APPLOCAL_DEPS=OFF;-DCMAKE_TOOLCHAIN_FILE=C:/src/vcpkg/scripts/buildsy
stems/vcpkg.cmake;-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON;-DCMAKE_CXX_FLAGS_RELEASE=/MT /O2 /Oi /Gy /DNDEBUG /Z
i ;-DCMAKE_C_FLAGS_RELEASE=/MT /O2 /Oi /Gy /DNDEBUG /Zi ;-DCMAKE_SHARED_LINKER_FLAGS_RELEASE=/DEBUG /INCREMENTAL:NO /OPT
:REF /OPT:ICF ;-DCMAKE_EXE_LINKER_FLAGS_RELEASE=/DEBUG /INCREMENTAL:NO /OPT:REF /OPT:ICF ;-G;Visual Studio 14 2015;-DCMA
KE_BUILD_TYPE=Release;-DCMAKE_INSTALL_PREFIX=C:/src/vcpkg/packages/paho-mqtt_x86-windows-static
Working Directory: C:/src/vcpkg/buildtrees/paho-mqtt/x86-windows-static-rel
See logs for more information:
C:\src\vcpkg\buildtrees\paho-mqtt\config-x86-windows-static-rel-out.log
C:\src\vcpkg\buildtrees\paho-mqtt\config-x86-windows-static-rel-err.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_configure_cmake.cmake:170 (vcpkg_execute_required_process)
ports/paho-mqtt/portfile.cmake:12 (vcpkg_configure_cmake)
scripts/ports.cmake:73 (include)
Error: Building package paho-mqtt:x86-windows-static failed with: BUILD_FAILED
err.log:
CMake Error at CMakeLists.txt:29 (STRING):
string sub-command STRIP requires two arguments.

@atkawa7 Could you take a look at this?

@ras0219-msft @jmin911 Thank you. There is problem with cmake with the latest version. It was fixed in this build-cmake-fix-windows pull request. However they haven't released new versions. Can you please try with --head to install from the master.

Hi @jmin911 , thanks for reporting this issue!
Please open a new issue if this is still a problem for you.
Thx.


Select kernel from list on load

Also get our kernel code inline with the intentions of the API.

Coverage decreased (-0.01%) to 83.284% when pulling 5b7d4f8733354346ef71cf4a9c3185940c749372 on briansteffens:fix-kernels into 2ab0fbd83b9b36fdd1921b9ed687bc2d279f5fd7 on linode:master.


all-in-one jaeger crashes with SIGSEGV

Describe the bug
all-in-one jaeger crashes with SIGSEGV
To Reproduce
Steps to reproduce the behavior:
1.set up ruby's gRPC environment
1-1) install ruby
(my environment is "ruby 2.5.5p157 (2019-03-15 revision 67260) [x86_64-linux-gnu]")
1-2) installing related gem(for gRPC)
       # gem install grpc
       # gem install grpc-tools

2.check jaeger's logfile
execute in controller node.
  #kubectl logs istio-tracing-954c9b595-bpd9p -n istio-system -f

3.execute this code(do this procedure)
  $ git clone https://github.com/miyakz1192/jaeger-idl.git
  $ cd jaeger-idl
  $ git checkout support_ruby
  $ cd proto-gen-ruby/
  $ ruby -I . sample.rb

4.you will get panic error log like that
  panic: runtime error: invalid memory address or nil pointer dereference
  [signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x114add8]

  goroutine 269 [running]:
  github.com/jaegertracing/jaeger/cmd/query/app.(*GRPCHandler).GetTrace(0xc005a6f860, 0xc006008600, 0x1d1e740, 0xc005fa76f0, 0xc005a6f860, 0x20)
  	/home/travis/gopath/src/github.com/jaegertracing/jaeger/cmd/query/app/grpc_handler.go:60 +0x368
  github.com/jaegertracing/jaeger/proto-gen/api_v2._QueryService_GetTrace_Handler(0x13c3d80, 0xc005a6f860, 0x1d1bec0, 0xc005aaa240, 0x2848bc0, 0xc000380700)
  	/home/travis/gopath/src/github.com/jaegertracing/jaeger/proto-gen/api_v2/query.pb.go:955 +0x109
  github.com/jaegertracing/jaeger/vendor/google.golang.org/grpc.(*Server).processStreamingRPC(0xc005a6af00, 0x1d22a00, 0xc005c30480, 0xc000380700, 0xc005a96300, 0x2811360, 0x0, 0x0, 0x0)
  	/home/travis/gopath/src/github.com/jaegertracing/jaeger/vendor/google.golang.org/grpc/server.go:1211 +0xb22
  github.com/jaegertracing/jaeger/vendor/google.golang.org/grpc.(*Server).handleStream(0xc005a6af00, 0x1d22a00, 0xc005c30480, 0xc000380700, 0x0)
  	/home/travis/gopath/src/github.com/jaegertracing/jaeger/vendor/google.golang.org/grpc/server.go:1291 +0xd30
  github.com/jaegertracing/jaeger/vendor/google.golang.org/grpc.(*Server).serveStreams.func1.1(0xc00032e384, 0xc005a6af00, 0x1d22a00, 0xc005c30480, 0xc000380700)
  	/home/travis/gopath/src/github.com/jaegertracing/jaeger/vendor/google.golang.org/grpc/server.go:722 +0xbb
  created by github.com/jaegertracing/jaeger/vendor/google.golang.org/grpc.(*Server).serveStreams.func1
  	/home/travis/gopath/src/github.com/jaegertracing/jaeger/vendor/google.golang.org/grpc/server.go:720 +0xa1

Expected behavior
Jaeger will return trace data to ruby client.
Screenshots
No screenshots, because of above reproduction procedure is.
Version (please complete the following information):

OS: Ubuntu 19.04
Jaeger version: jaegertracing/all-in-one:latest
Deployment: [Kubernetes]

root@kubecon1:~/documents/jaeger-idl/proto-gen-ruby# kubectl get deployments.apps istio-tracing -o yaml -n istio-system
apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
    deployment.kubernetes.io/revision: "3"
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"apps/v1","kind":"Deployment","metadata":{"annotations":{},"labels":{"app":"jaeger","operator.istio.io/component":"AddonComponents","operator.istio.io/managed":"Reconcile","operator.istio.io/version":"1.5.2","release":"istio"},"name":"istio-tracing","namespace":"istio-system"},"spec":{"selector":{"matchLabels":{"app":"jaeger"}},"template":{"metadata":{"annotations":{"prometheus.io/port":"14269","prometheus.io/scrape":"true","sidecar.istio.io/inject":"false"},"labels":{"app":"jaeger","release":"istio"}},"spec":{"affinity":{"nodeAffinity":{"preferredDuringSchedulingIgnoredDuringExecution":[{"preference":{"matchExpressions":[{"key":"beta.kubernetes.io/arch","operator":"In","values":["amd64"]}]},"weight":2},{"preference":{"matchExpressions":[{"key":"beta.kubernetes.io/arch","operator":"In","values":["ppc64le"]}]},"weight":2},{"preference":{"matchExpressions":[{"key":"beta.kubernetes.io/arch","operator":"In","values":["s390x"]}]},"weight":2}],"requiredDuringSchedulingIgnoredDuringExecution":{"nodeSelectorTerms":[{"matchExpressions":[{"key":"beta.kubernetes.io/arch","operator":"In","values":["amd64","ppc64le","s390x"]}]}]}}},"containers":[{"env":[{"name":"POD_NAMESPACE","valueFrom":{"fieldRef":{"apiVersion":"v1","fieldPath":"metadata.namespace"}}},{"name":"BADGER_EPHEMERAL","value":"false"},{"name":"SPAN_STORAGE_TYPE","value":"badger"},{"name":"BADGER_DIRECTORY_VALUE","value":"/badger/data"},{"name":"BADGER_DIRECTORY_KEY","value":"/badger/key"},{"name":"COLLECTOR_ZIPKIN_HTTP_PORT","value":"9411"},{"name":"MEMORY_MAX_TRACES","value":"50000"},{"name":"QUERY_BASE_PATH","value":"/jaeger"}],"image":"docker.io/jaegertracing/all-in-one:1.16","imagePullPolicy":"IfNotPresent","livenessProbe":{"httpGet":{"path":"/","port":14269}},"name":"jaeger","ports":[{"containerPort":9411},{"containerPort":16686},{"containerPort":14250},{"containerPort":14267},{"containerPort":14268},{"containerPort":14269},{"containerPort":5775,"protocol":"UDP"},{"containerPort":6831,"protocol":"UDP"},{"containerPort":6832,"protocol":"UDP"}],"readinessProbe":{"httpGet":{"path":"/","port":14269}},"resources":{"requests":{"cpu":"10m"}},"volumeMounts":[{"mountPath":"/badger","name":"data"}]}],"volumes":[{"emptyDir":{},"name":"data"}]}}}}
  creationTimestamp: "2020-05-10T08:05:27Z"
  generation: 3
  labels:
    app: jaeger
    operator.istio.io/component: AddonComponents
    operator.istio.io/managed: Reconcile
    operator.istio.io/version: 1.5.2
    release: istio
  name: istio-tracing
  namespace: istio-system
  resourceVersion: "12489320"
  selfLink: /apis/apps/v1/namespaces/istio-system/deployments/istio-tracing
  uid: ec652920-f710-44fa-9e0a-2d551fc46824
spec:
  progressDeadlineSeconds: 600
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      app: jaeger
  strategy:
    rollingUpdate:
      maxSurge: 25%
      maxUnavailable: 25%
    type: RollingUpdate
  template:
    metadata:
      annotations:
        prometheus.io/port: "14269"
        prometheus.io/scrape: "true"
        sidecar.istio.io/inject: "false"
      creationTimestamp: null
      labels:
        app: jaeger
        release: istio
    spec:
      affinity:
        nodeAffinity:
          preferredDuringSchedulingIgnoredDuringExecution:
          - preference:
              matchExpressions:
              - key: beta.kubernetes.io/arch
                operator: In
                values:
                - amd64
            weight: 2
          - preference:
              matchExpressions:
              - key: beta.kubernetes.io/arch
                operator: In
                values:
                - ppc64le
            weight: 2
          - preference:
              matchExpressions:
              - key: beta.kubernetes.io/arch
                operator: In
                values:
                - s390x
            weight: 2
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
            - matchExpressions:
              - key: beta.kubernetes.io/arch
                operator: In
                values:
                - amd64
                - ppc64le
                - s390x
      containers:
      - env:
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.namespace
        - name: BADGER_EPHEMERAL
          value: "false"
        - name: SPAN_STORAGE_TYPE
          value: badger
        - name: BADGER_DIRECTORY_VALUE
          value: /badger/data
        - name: BADGER_DIRECTORY_KEY
          value: /badger/key
        - name: COLLECTOR_ZIPKIN_HTTP_PORT
          value: "9411"
        - name: MEMORY_MAX_TRACES
          value: "50000"
        - name: QUERY_BASE_PATH
          value: /jaeger
        - name: LOG_LEVEL
          value: debug
        image: docker.io/jaegertracing/all-in-one:latest
        imagePullPolicy: IfNotPresent
        livenessProbe:
          failureThreshold: 3
          httpGet:
            path: /
            port: 14269
            scheme: HTTP
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 1
        name: jaeger
        ports:
        - containerPort: 9411
          protocol: TCP
        - containerPort: 16686
          protocol: TCP
        - containerPort: 14250
          protocol: TCP
        - containerPort: 14267
          protocol: TCP
        - containerPort: 14268
          protocol: TCP
        - containerPort: 14269
          protocol: TCP
        - containerPort: 5775
          protocol: UDP
        - containerPort: 6831
          protocol: UDP
        - containerPort: 6832
          protocol: UDP
        readinessProbe:
          failureThreshold: 3
          httpGet:
            path: /
            port: 14269
            scheme: HTTP
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 1
        resources:
          requests:
            cpu: 10m
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /badger
          name: data
      dnsPolicy: ClusterFirst
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext: {}
      terminationGracePeriodSeconds: 30
      volumes:
      - emptyDir: {}
        name: data
status:
  availableReplicas: 1
  conditions:
  - lastTransitionTime: "2020-05-10T08:05:28Z"
    lastUpdateTime: "2020-07-25T11:53:54Z"
    message: ReplicaSet "istio-tracing-954c9b595" has successfully progressed.
    reason: NewReplicaSetAvailable
    status: "True"
    type: Progressing
  - lastTransitionTime: "2020-07-26T01:53:51Z"
    lastUpdateTime: "2020-07-26T01:53:51Z"
    message: Deployment has minimum availability.
    reason: MinimumReplicasAvailable
    status: "True"
    type: Available
  observedGeneration: 3
  readyReplicas: 1
  replicas: 1
  updatedReplicas: 1
root@kubecon1:~/documents/jaeger-idl/proto-gen-ruby#

root@kubecon1:~/documents/jaeger-idl/proto-gen-ruby# kubectl get pods istio-tracing-954c9b595-bpd9p -n istio-system  -o yaml
apiVersion: v1
kind: Pod
metadata:
  annotations:
    prometheus.io/port: "14269"
    prometheus.io/scrape: "true"
    sidecar.istio.io/inject: "false"
  creationTimestamp: "2020-07-25T11:53:17Z"
  generateName: istio-tracing-954c9b595-
  labels:
    app: jaeger
    pod-template-hash: 954c9b595
    release: istio
  name: istio-tracing-954c9b595-bpd9p
  namespace: istio-system
  ownerReferences:
  - apiVersion: apps/v1
    blockOwnerDeletion: true
    controller: true
    kind: ReplicaSet
    name: istio-tracing-954c9b595
    uid: c082684a-f77a-4a64-9f98-3d262f25c172
  resourceVersion: "12489310"
  selfLink: /api/v1/namespaces/istio-system/pods/istio-tracing-954c9b595-bpd9p
  uid: 6770e7ff-2869-4c3e-87e0-25eebd7baa13
spec:
  affinity:
    nodeAffinity:
      preferredDuringSchedulingIgnoredDuringExecution:
      - preference:
          matchExpressions:
          - key: beta.kubernetes.io/arch
            operator: In
            values:
            - amd64
        weight: 2
      - preference:
          matchExpressions:
          - key: beta.kubernetes.io/arch
            operator: In
            values:
            - ppc64le
        weight: 2
      - preference:
          matchExpressions:
          - key: beta.kubernetes.io/arch
            operator: In
            values:
            - s390x
        weight: 2
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
        - matchExpressions:
          - key: beta.kubernetes.io/arch
            operator: In
            values:
            - amd64
            - ppc64le
            - s390x
  containers:
  - env:
    - name: POD_NAMESPACE
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: metadata.namespace
    - name: BADGER_EPHEMERAL
      value: "false"
    - name: SPAN_STORAGE_TYPE
      value: badger
    - name: BADGER_DIRECTORY_VALUE
      value: /badger/data
    - name: BADGER_DIRECTORY_KEY
      value: /badger/key
    - name: COLLECTOR_ZIPKIN_HTTP_PORT
      value: "9411"
    - name: MEMORY_MAX_TRACES
      value: "50000"
    - name: QUERY_BASE_PATH
      value: /jaeger
    - name: LOG_LEVEL
      value: debug
    image: docker.io/jaegertracing/all-in-one:latest
    imagePullPolicy: IfNotPresent
    livenessProbe:
      failureThreshold: 3
      httpGet:
        path: /
        port: 14269
        scheme: HTTP
      periodSeconds: 10
      successThreshold: 1
      timeoutSeconds: 1
    name: jaeger
    ports:
    - containerPort: 9411
      protocol: TCP
    - containerPort: 16686
      protocol: TCP
    - containerPort: 14250
      protocol: TCP
    - containerPort: 14267
      protocol: TCP
    - containerPort: 14268
      protocol: TCP
    - containerPort: 14269
      protocol: TCP
    - containerPort: 5775
      protocol: UDP
    - containerPort: 6831
      protocol: UDP
    - containerPort: 6832
      protocol: UDP
    readinessProbe:
      failureThreshold: 3
      httpGet:
        path: /
        port: 14269
        scheme: HTTP
      periodSeconds: 10
      successThreshold: 1
      timeoutSeconds: 1
    resources:
      requests:
        cpu: 10m
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /badger
      name: data
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: default-token-87tws
      readOnly: true
  dnsPolicy: ClusterFirst
  enableServiceLinks: true
  nodeName: kubenode11
  priority: 0
  restartPolicy: Always
  schedulerName: default-scheduler
  securityContext: {}
  serviceAccount: default
  serviceAccountName: default
  terminationGracePeriodSeconds: 30
  tolerations:
  - effect: NoExecute
    key: node.kubernetes.io/not-ready
    operator: Exists
    tolerationSeconds: 300
  - effect: NoExecute
    key: node.kubernetes.io/unreachable
    operator: Exists
    tolerationSeconds: 300
  volumes:
  - emptyDir: {}
    name: data
  - name: default-token-87tws
    secret:
      defaultMode: 420
      secretName: default-token-87tws
status:
  conditions:
  - lastProbeTime: null
    lastTransitionTime: "2020-07-25T11:53:17Z"
    status: "True"
    type: Initialized
  - lastProbeTime: null
    lastTransitionTime: "2020-07-26T01:53:51Z"
    status: "True"
    type: Ready
  - lastProbeTime: null
    lastTransitionTime: "2020-07-26T01:53:51Z"
    status: "True"
    type: ContainersReady
  - lastProbeTime: null
    lastTransitionTime: "2020-07-25T11:53:17Z"
    status: "True"
    type: PodScheduled
  containerStatuses:
  - containerID: docker://efe61bba25986afaa0160ef5288880d5b701f20fcc6ba80395d4723fc06f5446
    image: jaegertracing/all-in-one:latest
    imageID: docker-pullable://jaegertracing/all-in-one@sha256:13646d75e8c33ab1c9e12a5c7269e3fe4f7b122a9f79d82d2b6f9cf25aad2d98
    lastState:
      terminated:
        containerID: docker://abf1ddacff4e7f22c90d6dba61bd3998baa9aa0a053cae8c97bf5162007fd1ec
        exitCode: 2
        finishedAt: "2020-07-26T01:53:36Z"
        reason: Error
        startedAt: "2020-07-25T11:59:10Z"
    name: jaeger
    ready: true
    restartCount: 2
    started: true
    state:
      running:
        startedAt: "2020-07-26T01:53:44Z"
  hostIP: <IP_ADDRESS>
  phase: Running
  podIP: <IP_ADDRESS>
  podIPs:
  - ip: <IP_ADDRESS>
  qosClass: Burstable
  startTime: "2020-07-25T11:53:17Z"
root@kubecon1:~/documents/jaeger-idl/proto-gen-ruby#

What troubleshooting steps did you try?
Try to follow https://www.jaegertracing.io/docs/latest/troubleshooting/ and describe how far you were able to progress and/or which steps did not work.
I read those document but I couldn't found solution.

I believe this might have been fixed already. Here's what I see when running Jaeger from the current tip of the master branch:
Your reproducer:
$ ruby -I . sample.rb
Traceback (most recent call last):
	7: from sample.rb:13:in `<main>'
	6: from sample.rb:10:in `test'
	5: from sample.rb:10:in `map'
	4: from sample.rb:10:in `each'
	3: from /usr/local/share/gems/gems/grpc-1.30.2-x86_64-linux/src/ruby/lib/grpc/generic/active_call.rb:337:in `each_remote_read_then_finish'
	2: from /usr/local/share/gems/gems/grpc-1.30.2-x86_64-linux/src/ruby/lib/grpc/generic/active_call.rb:169:in `receive_and_check_status'
	1: from /usr/local/share/gems/gems/grpc-1.30.2-x86_64-linux/src/ruby/lib/grpc/generic/active_call.rb:180:in `attach_status_results_and_complete_call'
/usr/local/share/gems/gems/grpc-1.30.2-x86_64-linux/src/ruby/lib/grpc/generic/active_call.rb:29:in `check_status': 5:trace not found: trace not found. debug_error_string:{"created":"@1595834670.748965007","description":"Error received from peer ipv6:[::1]:16686","file":"src/core/lib/surface/call.cc","file_line":1055,"grpc_message":"trace not found: trace not found","grpc_status":5} (GRPC::NotFound)

Jaeger Query:
{"level":"error","ts":1595834670.7487974,"caller":"app/grpc_handler.go:59","msg":"trace not found","error":"trace not found","stacktrace":"github.com/jaegertracing/jaeger/cmd/query/app.(*GRPCHandler).GetTrace\n\t/home/jpkroehling/Projects/src/github.com/jaegertracing/jaeger/cmd/query/app/grpc_handler.go:59\ngithub.com/jaegertracing/jaeger/proto-gen/api_v2._QueryService_GetTrace_Handler\n\t/home/jpkroehling/Projects/src/github.com/jaegertracing/jaeger/proto-gen/api_v2/query.pb.go:955\ngoogle.golang.org/grpc.(*Server).processStreamingRPC\n\t/home/jpkroehling/go/pkg/mod/google.golang.org/grpc@v1.27.1/server.go:1237\ngoogle.golang.org/grpc.(*Server).handleStream\n\t/home/jpkroehling/go/pkg/mod/google.golang.org/grpc@v1.27.1/server.go:1317\ngoogle.golang.org/grpc.(*Server).serveStreams.func1.1\n\t/home/jpkroehling/go/pkg/mod/google.golang.org/grpc@v1.27.1/server.go:722"}

My Ruby versions, installed fresh on an up to date Fedora 32:
$ ruby -v
 ruby 2.7.1p83 (2020-03-31 revision a0c7c23c9c) [x86_64-linux]

In fact, I wasn't able to reproduce it even on an ancient Jaeger version (1.12), which makes me wonder the actual version you are using. Would you be able to get the container SHA that you are running? Or perhaps could you please try setting a fixed, recent version (1.18.1, for instance)?

@jkandasa just pointed out that there's a SHA in your original report, so I went ahead and tried to reproduce it without success:
$ podman run -p 16686 jaegertracing/all-in-one@sha256:13646d75e8c33ab1c9e12a5c7269e3fe4f7b122a9f79d82d2b6f9cf25aad2d98
{"level":"info","ts":1595835573.0093844,"caller":"flags/service.go:116","msg":"Mounting metrics handler on admin server","route":"/metrics"}
{"level":"info","ts":1595835573.0098934,"caller":"flags/admin.go:120","msg":"Mounting health check on admin server","route":"/"}
{"level":"info","ts":1595835573.0099263,"caller":"flags/admin.go:126","msg":"Starting admin HTTP server","http-addr":":14269"}
{"level":"info","ts":1595835573.0099432,"caller":"flags/admin.go:112","msg":"Admin server started","http.host-port":"[::]:14269","health-status":"unavailable"}
{"level":"info","ts":1595835573.0429375,"caller":"memory/factory.go:61","msg":"Memory storage initialized","configuration":{"MaxTraces":0}}
{"level":"info","ts":1595835573.05047,"caller":"server/grpc.go:76","msg":"Starting jaeger-collector gRPC server","grpc.host-port":":14250"}
{"level":"info","ts":1595835573.0504975,"caller":"server/http.go:44","msg":"Starting jaeger-collector HTTP server","http host-port":":14268"}
{"level":"info","ts":1595835573.0506194,"caller":"server/zipkin.go:48","msg":"Listening for Zipkin HTTP traffic","zipkin host-port":":0"}
{"level":"info","ts":1595835573.0677428,"caller":"grpc/builder.go:66","msg":"Agent requested insecure grpc connection to collector(s)"}
{"level":"info","ts":1595835573.067788,"caller":"grpc@v1.27.1/clientconn.go:106","msg":"parsed scheme: \"\"","system":"grpc","grpc_log":true}
{"level":"info","ts":1595835573.068015,"caller":"grpc@v1.27.1/clientconn.go:106","msg":"scheme \"\" not registered, fallback to default scheme","system":"grpc","grpc_log":true}
{"level":"info","ts":1595835573.0680413,"caller":"passthrough/passthrough.go:48","msg":"ccResolverWrapper: sending update to cc: {[{:14250  <nil> 0 <nil>}] <nil> <nil>}","system":"grpc","grpc_log":true}
{"level":"info","ts":1595835573.06813,"caller":"grpc@v1.27.1/clientconn.go:948","msg":"ClientConn switching balancer to \"round_robin\"","system":"grpc","grpc_log":true}
{"level":"info","ts":1595835573.0688906,"caller":"command-line-arguments/main.go:206","msg":"Starting agent"}
{"level":"info","ts":1595835573.0688972,"caller":"base/balancer.go:196","msg":"roundrobinPicker: newPicker called with info: {map[0xc00020bc30:{{:14250  <nil> 0 <nil>}}]}","system":"grpc","grpc_log":true}
{"level":"info","ts":1595835573.0689435,"caller":"querysvc/query_service.go:137","msg":"Archive storage not created","reason":"archive storage not supported"}
{"level":"info","ts":1595835573.0689585,"caller":"app/flags.go:113","msg":"Archive storage not initialized"}
{"level":"info","ts":1595835573.0689614,"caller":"app/agent.go:69","msg":"Starting jaeger-agent HTTP server","http-port":5778}
{"level":"info","ts":1595835573.0693355,"caller":"app/server.go:133","msg":"Query server started","port":16686,"addr":":16686"}
{"level":"info","ts":1595835573.06936,"caller":"healthcheck/handler.go:128","msg":"Health Check state change","status":"ready"}
{"level":"info","ts":1595835573.0693824,"caller":"app/server.go:171","msg":"Starting CMUX server","port":16686,"addr":":16686"}
{"level":"info","ts":1595835573.069387,"caller":"app/server.go:161","msg":"Starting GRPC server","port":16686,"addr":":16686"}
{"level":"info","ts":1595835573.0693805,"caller":"app/server.go:148","msg":"Starting HTTP server","port":16686,"addr":":16686"}
{"level":"error","ts":1595835575.6054332,"caller":"app/grpc_handler.go:59","msg":"trace not found","error":"trace not found","stacktrace":"github.com/jaegertracing/jaeger/cmd/query/app.(*GRPCHandler).GetTrace\n\tgithub.com/jaegertracing/jaeger/cmd/query/app/grpc_handler.go:59\ngithub.com/jaegertracing/jaeger/proto-gen/api_v2._QueryService_GetTrace_Handler\n\tgithub.com/jaegertracing/jaeger/proto-gen/api_v2/query.pb.go:955\ngoogle.golang.org/grpc.(*Server).processStreamingRPC\n\tgoogle.golang.org/grpc@v1.27.1/server.go:1237\ngoogle.golang.org/grpc.(*Server).handleStream\n\tgoogle.golang.org/grpc@v1.27.1/server.go:1317\ngoogle.golang.org/grpc.(*Server).serveStreams.func1.1\n\tgoogle.golang.org/grpc@v1.27.1/server.go:722"}

Thank you for your reply and sorry for my late reply.
I tried image(sha256:13646d75e8c33ab1c9e12a5c7269e3fe4f7b122a9f79d82d2b6f9cf25aad2d98) but situation was not changed.
[jaeger side logs]
  panic: runtime error: invalid memory address or nil pointer dereference
  [signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x10e7586]

  goroutine 288 [running]:
  github.com/jaegertracing/jaeger/cmd/query/app.(*GRPCHandler).GetTrace(0xc005fb87e0, 0xc005abab10, 0x1c94a80, 0xc000118b60, 0xc005fb87e0, 0x20)
        github.com/jaegertracing/jaeger/cmd/query/app/grpc_handler.go:66 +0x3d6
  github.com/jaegertracing/jaeger/proto-gen/api_v2._QueryService_GetTrace_Handler(0x1336600, 0xc005fb87e0, 0x1c91c60, 0xc000370240, 0x26995e8, 0xc0002
5cf00)
        github.com/jaegertracing/jaeger/proto-gen/api_v2/query.pb.go:955 +0x109
  google.golang.org/grpc.(*Server).processStreamingRPC(0xc005fb2300, 0x1c988c0, 0xc0006dd080, 0xc00025cf00, 0xc005fbacc0, 0x2653f20, 0x0, 0x0, 0x0)
        google.golang.org/grpc@v1.27.1/server.go:1237 +0xcd1
  google.golang.org/grpc.(*Server).handleStream(0xc005fb2300, 0x1c988c0, 0xc0006dd080, 0xc00025cf00, 0x0)
        google.golang.org/grpc@v1.27.1/server.go:1317 +0xcd6
  google.golang.org/grpc.(*Server).serveStreams.func1.1(0xc0002880c0, 0xc005fb2300, 0x1c988c0, 0xc0006dd080, 0xc00025cf00)
        google.golang.org/grpc@v1.27.1/server.go:722 +0xa1
  created by google.golang.org/grpc.(*Server).serveStreams.func1
        google.golang.org/grpc@v1.27.1/server.go:720 +0xa1
  root@kubecon1:/home/miyakz#

[client side output]
  root@eng-app-app-57cf6f7bb9-2tq66:/jaeger-idl/proto-gen-ruby# ruby -I . sample.rb
  Traceback (most recent call last):
        7: from sample.rb:13:in `<main>'
        6: from sample.rb:10:in `test'
        5: from sample.rb:10:in `map'
        4: from sample.rb:10:in `each'
        3: from /var/lib/gems/2.5.0/gems/grpc-1.30.2-x86_64-linux/src/ruby/lib/grpc/generic/active_call.rb:337:in `each_remote_read_then_finish'
        2: from /var/lib/gems/2.5.0/gems/grpc-1.30.2-x86_64-linux/src/ruby/lib/grpc/generic/active_call.rb:169:in `receive_and_check_status'
        1: from /var/lib/gems/2.5.0/gems/grpc-1.30.2-x86_64-linux/src/ruby/lib/grpc/generic/active_call.rb:180:in `attach_status_results_and_complete_call'
  /var/lib/gems/2.5.0/gems/grpc-1.30.2-x86_64-linux/src/ruby/lib/grpc/generic/active_call.rb:29:in `check_status': 14:Socket closed. debug_error_string:{"created":"@1597501484.472667844","description":"Error received from peer ipv4:<IP_ADDRESS>:30858","file":"src/core/lib/surface/call.cc","file_line":1055,"grpc_message":"Socket closed","grpc_status":14} (GRPC::Unavailable)
  root@eng-app-app-57cf6f7bb9-2tq66:/jaeger-idl/proto-gen-ruby#

I have two worker nodes.
  root@kubecon1:/home/miyakz# kubectl get nodes
  NAME         STATUS   ROLES    AGE    VERSION
  kubecon1     Ready    master   308d   v1.16.1
  kubenode11   Ready    <none>   308d   v1.16.1
  root@kubecon1:/home/miyakz#

And jaeger images on each worker nodes are following.
  root@kubecon1:/home/miyakz# docker image list | grep jaeger
  jaegertracing/protobuf                      0.2.0                          8817b24a4c9e        7 weeks ago         153MB
  jaegertracing/thrift                        0.13                           46013df3cf70        3 months ago        126MB
  root@kubecon1:/home/miyakz#

  root@kubenode11:/home/miyakz# docker image list | grep jaeger
  jaegertracing/all-in-one                    <none>                         5ef5c2d8e8d1        5 weeks ago         47.4MB
  root@kubenode11:/home/miyakz#

  root@kubenode11:/home/miyakz# docker inspect --format='{{.RepoDigests}}'  5ef5c2d8e8d1
  [jaegertracing/all-in-one@sha256:13646d75e8c33ab1c9e12a5c7269e3fe4f7b122a9f79d82d2b6f9cf25aad2d98]
  root@kubenode11:/home/miyakz#

Needless to say, jaeger tracing container runs on kubenode11.
istio-system   istio-tracing-6dd48c455-2snw5          1/1     Running   1          19m     <IP_ADDRESS>    kubenode11   <none>           <none>

My Intuition is CPU misconfiguration or bug. My CPU environment is the following.
root@kubenode11:/home/miyakz# lscpu
Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
Address sizes:       40 bits physical, 48 bits virtual
CPU(s):              7
On-line CPU(s) list: 0-6
Thread(s) per core:  1
Core(s) per socket:  1
Socket(s):           7
NUMA node(s):        1
Vendor ID:           AuthenticAMD
CPU family:          6
Model:               6
Model name:          QEMU Virtual CPU version 2.5+
Stepping:            3
CPU MHz:             3593.254
BogoMIPS:            7186.50
Virtualization:      AMD-V
L1d cache:           64K
L1i cache:           64K
L2 cache:            512K
L3 cache:            16384K
NUMA node0 CPU(s):   0-6
Flags:               fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx lm nopl cpuid pni cx16 hypervisor lahf_lm svm 3dnowprefetch vmmcall
root@kubenode11:/home/miyakz#

Could you any comments?

Additional information.
I found that jaeger-all-in-one works on VM doesn't crash.
I pulled jaeger source from github.
root@dockerbuild:/home/miyakz/jaeger/cmd/all-in-one# git remote -v
origin	https://github.com/jaegertracing/jaeger.git (fetch)
origin	https://github.com/jaegertracing/jaeger.git (push)
root@dockerbuild:/home/miyakz/jaeger/cmd/all-in-one# git log | head
commit 5f4fc8da4d4e5d80cff7f8e06bad9c8e271abcf1
Author: Sreevani K V S<EMAIL_ADDRESS>Date:   Fri Aug 14 22:12:18 2020 +0530

    Fix panic in collector when Zipkin server is shutdown (#2392)

    Signed-off-by: Sreevani871<EMAIL_ADDRESS>
commit 5daae75911e36b842b45279d8a599bcc5d56eabf
Author: rjs211<EMAIL_ADDRESS>root@dockerbuild:/home/miyakz/jaeger/cmd/all-in-one#

and I built all-in-one binary and try to reproduce the problem but the problem didn't appear.
[server side log]
{"level":"error","ts":1597551056.6664784,"caller":"app/grpc_handler.go:59","msg":"trace not found","error":"trace not found","stacktrace":"github.com/jaegertracing/jaeger/cmd/query/app.(*GRPCHandler).GetTrace\n\tgithub.com/jaegertracing/jaeger/cmd/query/app/grpc_handler.go:59\ngithub.com/jaegertracing/jaeger/proto-gen/api_v2._QueryService_GetTrace_Handler\n\tgithub.com/jaegertracing/jaeger/proto-gen/api_v2/query.pb.go:955\ngoogle.golang.org/grpc.(*Server).processStreamingRPC\n\tgoogle.golang.org/grpc@v1.31.0/server.go:1427\ngoogle.golang.org/grpc.(*Server).handleStream\n\tgoogle.golang.org/grpc@v1.31.0/server.go:1507\ngoogle.golang.org/grpc.(*Server).serveStreams.func1.2\n\tgoogle.golang.org/grpc@v1.31.0/server.go:843"}

[client side log]
root@dockerbuild:/home/miyakz/jaeger-idl/proto-gen-ruby# ruby -I . sample.rb
Traceback (most recent call last):
        7: from sample.rb:15:in `<main>'
        6: from sample.rb:12:in `test'
        5: from sample.rb:12:in `map'
        4: from sample.rb:12:in `each'
        3: from /var/lib/gems/2.5.0/gems/grpc-1.30.2-x86_64-linux/src/ruby/lib/grpc/generic/active_call.rb:337:in `each_remote_read_then_finish'
        2: from /var/lib/gems/2.5.0/gems/grpc-1.30.2-x86_64-linux/src/ruby/lib/grpc/generic/active_call.rb:169:in `receive_and_check_status'
        1: from /var/lib/gems/2.5.0/gems/grpc-1.30.2-x86_64-linux/src/ruby/lib/grpc/generic/active_call.rb:180:in `attach_status_results_and_complete_call'
/var/lib/gems/2.5.0/gems/grpc-1.30.2-x86_64-linux/src/ruby/lib/grpc/generic/active_call.rb:29:in `check_status': 5:trace not found: trace not found. debug_error_string:{"created":"@1597551056.685024015","description":"Error received from peer ipv4:<IP_ADDRESS>:16686","file":"src/core/lib/surface/call.cc","file_line":1055,"grpc_message":"trace not found: trace not found","grpc_status":5} (GRPC::NotFound)
root@dockerbuild:/home/miyakz/jaeger-idl/proto-gen-ruby#

I think there is something wrong with container environment.
anyone knows a similar problem?

Additional information.
Just in case, I created jaeger all-in-one with  scripts/travis/build-all-in-one-image.sh and push to my dockerhub repo(https://hub.docker.com/repository/docker/miyakz1192/jaeger-all-in-one)
the container created from that image crashed with SIGSEGV.
[note]
when I exec build-all-in-one-image.sh, I set BRANCH environment valuable with "master".

Would you have detailed instructions on how to reproduce this? Based on your last messages, I assumed that it would happen with Jaeger deployed on Kubernetes, so, I started minikube, deployed the Jaeger Operator, deployed a Jaeger instance, did a port-forward for the 16686 port, but still couldn't hit the problem:
$ minikube start --vm-driver kvm2 --cpus 6 --memory 20480 --container-runtime=crio

$ kubectl create namespace observability
$ kubectl apply -f deploy/crds/jaegertracing.io_jaegers_crd.yaml
$ kubectl apply -f deploy/service_account.yaml
$ kubectl apply -f deploy/role.yaml
$ kubectl apply -f deploy/role_binding.yaml
$ kubectl apply -f deploy/operator.yaml

$ kubectl apply -f deploy/examples/simplest.yaml
$ kubectl port-forward service/simplest-query 16686

Your reproducer:
$ ruby -I . sample.rb
Traceback (most recent call last):
	7: from sample.rb:13:in `<main>'
	6: from sample.rb:10:in `test'
	5: from sample.rb:10:in `map'
	4: from sample.rb:10:in `each'
	3: from /home/jpkroehling/.gem/ruby/gems/grpc-1.30.2-x86_64-linux/src/ruby/lib/grpc/generic/active_call.rb:337:in `each_remote_read_then_finish'
	2: from /home/jpkroehling/.gem/ruby/gems/grpc-1.30.2-x86_64-linux/src/ruby/lib/grpc/generic/active_call.rb:169:in `receive_and_check_status'
	1: from /home/jpkroehling/.gem/ruby/gems/grpc-1.30.2-x86_64-linux/src/ruby/lib/grpc/generic/active_call.rb:180:in `attach_status_results_and_complete_call'
/home/jpkroehling/.gem/ruby/gems/grpc-1.30.2-x86_64-linux/src/ruby/lib/grpc/generic/active_call.rb:29:in `check_status': 5:trace not found: trace not found. debug_error_string:{"created":"@1597658073.663623997","description":"Error received from peer ipv6:[::1]:16686","file":"src/core/lib/surface/call.cc","file_line":1055,"grpc_message":"trace not found: trace not found","grpc_status":5} (GRPC::NotFound)

The Jaeger logs:
{"level":"error","ts":1597658068.1243339,"caller":"app/grpc_handler.go:59","msg":"trace not found","error":"trace not found","stacktrace":"github.com/jaegertracing/jaeger/cmd/query/app.(*GRPCHandler).GetTrace\n\tgithub.com/jaegertracing/jaeger/cmd/query/app/grpc_handler.go:59\ngithub.com/jaegertracing/jaeger/proto-gen/api_v2._QueryService_GetTrace_Handler\n\tgithub.com/jaegertracing/jaeger/proto-gen/api_v2/query.pb.go:955\ngoogle.golang.org/grpc.(*Server).processStreamingRPC\n\tgoogle.golang.org/grpc@v1.27.1/server.go:1237\ngoogle.golang.org/grpc.(*Server).handleStream\n\tgoogle.golang.org/grpc@v1.27.1/server.go:1317\ngoogle.golang.org/grpc.(*Server).serveStreams.func1.1\n\tgoogle.golang.org/grpc@v1.27.1/server.go:722"}

Do let us know. At this point, this is a mystery to me :-)

Thank you for your response.
I try to re-install ubuntu as 20.04LTS and ran minikube with your instruction.
I didn't encounter odd symptoms.
miyakz@lily2:~/source/jaeger-idl/proto-gen-ruby$ ruby -I . sample.rb
Traceback (most recent call last):
	7: from sample.rb:13:in `<main>'
	6: from sample.rb:10:in `test'
	5: from sample.rb:10:in `map'
	4: from sample.rb:10:in `each'
	3: from /var/lib/gems/2.7.0/gems/grpc-1.31.1-x86_64-linux/src/ruby/lib/grpc/generic/active_call.rb:337:in `each_remote_read_then_finish'
	2: from /var/lib/gems/2.7.0/gems/grpc-1.31.1-x86_64-linux/src/ruby/lib/grpc/generic/active_call.rb:169:in `receive_and_check_status'
	1: from /var/lib/gems/2.7.0/gems/grpc-1.31.1-x86_64-linux/src/ruby/lib/grpc/generic/active_call.rb:180:in `attach_status_results_and_complete_call'
/var/lib/gems/2.7.0/gems/grpc-1.31.1-x86_64-linux/src/ruby/lib/grpc/generic/active_call.rb:29:in `check_status': 5:trace not found: trace not found. debug_error_string:{"created":"@1598681485.188116118","description":"Error received from peer ipv4:<IP_ADDRESS>:16686","file":"src/core/lib/surface/call.cc","file_line":1062,"grpc_message":"trace not found: trace not found","grpc_status":5} (GRPC::NotFound)
miyakz@lily2:~/source/jaeger-idl/proto-gen-ruby$

I think my environment had something wrong with KVM/qemu.
After re-install it seems to everything fine.

Feel free to reopen if needed.


Add several nodes to better support textobject queries

Needed call arguments for proper textobject queries for call arguments.
The special builtin __loc was missing an only detected as an identifier. Now it can be highlighted as a builtin variable.
Add a node for named_argument to catch the name and the value
Added a node for all members to support @class.inside captures.

@amaanq I did the rewording in my fork. Whenever you are ready, lets do the 0.3 thing


I was trying to upgrade pip but error occurs

Please tell me how to solve it. I am working on windows.
Thankyou

This error is unrelated to this repo.


Usage docs

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@e19b57d). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             master     #2   +/-   ##
=======================================
  Coverage          ?   100%
=======================================
  Files             ?      2
  Lines             ?     49
  Branches          ?      0
=======================================
  Hits              ?     49
  Misses            ?      0
  Partials          ?      0

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 e19b57d...1c261b9. Read the comment docs.


[Feature Request] whitespace in assay folder name

Not sure if we want this:

@HLWeil

In the test folders?

what? 😅

Damn it, good question. I think this is a ARC created with ARCtrl and FileSystem paths for an assay with identifier "My Assay", which will, to my understanding, translate to on-disc directories

I see, maybe we can auto-update faulty user input when creating the object.
So:
ArcAssay(Identifier = "My Assay")

will result in
ArcAssay {Identifier = "My_Assay")

This should be handled by checkValidIdentifiers or by any write functions. Closed until issues arise


Improvements to DynamicForm to support creation of document sets

Current implementation of DynamicForm is not working when adding new Document Set instances. This PR fixes the issue and makes it fully functional with Document Set creation.

Thank you @PaoloPia!


Chat

I am sorry if this is a big pull request. Basically, what I do here includes both of the front-end and back-end of the messaging function. At first, you pick a person who you get matched before to chat with. Currently, on the profile page, it has 5 people with unique IDs inputted manually. After choosing a person, it will direct the user to another page with a pop-up form where the user can type in the message. The previous messages the user sent and received from his/her match (which are stored in Message entity) will be displayed on the screen as well. Currently, it hasn't had real-time update, which means the user needs to reload to update the latest message).
I am currently working on Message Handler Test. After that, I will go back to the front-end to figure out how to display the messages.

This PR is continued on PR #15


BOSH ssh can not read the stdin from the pipe

I want to use the bosh ssh to logon to the target server and then sudo to get the root privilege. So, the sample command should be :
bosh ssh node/0 "echo password | sudo -S "
Error happened, the output :
[sudo] password for bosh_6q228n3ps: Sorry, try again.
[sudo] password for bosh_6q228n3ps:
sudo: 1 incorrect password attempt

Currently users created by bosh are not passwordless sudoers, so CLI asks for a password or expects a password to be provided by --default_password flag. We are planning to make them passwordless sudoers soon; meanwhile you can try something like this:
bosh ssh node 0 --default_password p "echo p | sudo -S something"

I verified. The workaround you mentioned works well!
Many thanks!

Hola,
I had the same problem and I am now trying to use the same command. Thank in advance for the workaround @goupeng212, but unfortunately this is not working for me. Did I overlook something :smiley:?
$ bosh ssh mongodb 0 --default_password p "echo p | sudo -S ls -l /"
Acting as user 'admin' on deployment 'mongodb-warden' on 'Bosh Lite Director'
Executing `echo p | sudo -S ls -l /' on mongodb/0
Target deployment is `mongodb-warden'

Setting up ssh artifacts

Director task 4496

Task 4496 done

mongodb/0
[sudo] password for bosh_pcd4t9xyk: Sorry, try again.
[sudo] password for bosh_pcd4t9xyk:
sudo: 1 incorrect password attempt

Cleaning up ssh artifacts

Director task 4497

Task 4497 done
$

@fabianschwarzfritz works nicely for me:
$ bosh ssh redis_leader_z1 0 --gateway_host <redacted>  --gateway_user vcap --gateway_identity_file <redacted> --default_password abc "echo abc | sudo -S ls -l /"
Acting as user 'admin' on deployment 'redis-aws-ec2' on 'my-bosh'
Executing `echo abc | sudo -S ls -l /' on redis_leader_z1/0
Target deployment is `redis-aws-ec2'

Setting up ssh artifacts

Director task 20

Task 20 done

redis_leader_z1/0
[sudo] password for bosh_1aku9fikm: total 73
drwxr-xr-x   2 root root  4096 Oct  5 23:41 bin
drwxr-xr-x   3 root root  4096 Oct  5 23:44 boot
drwxr-xr-x  15 root root  4060 Oct 16 04:17 dev
drwxr-xr-x  83 root root  4096 Oct 16 04:26 etc
drwxr-xr-x   3 root root  4096 Oct  5 23:43 home
lrwxrwxrwx   1 root root    33 Oct  5 23:42 initrd.img -> boot/initrd.img-3.19.0-30-generic
drwxr-xr-x  17 root root  4096 Oct  5 23:42 lib
drwxr-xr-x   2 root root  4096 Oct  5 23:40 lib64
drwx------   2 root root 16384 Oct 14 18:06 lost+found
drwxr-xr-x   2 root root  4096 Oct  5 23:39 media
drwxr-xr-x   2 root root  4096 Apr 10  2014 mnt
drwxr-xr-x   2 root root  4096 Oct  5 23:39 opt
dr-xr-xr-x 100 root root     0 Oct 16 04:16 proc
drwx------   3 root root  4096 Oct 16 04:17 root
drwxr-xr-x  15 root root   620 Oct 16 04:26 run
drwxr-xr-x   2 root root  4096 Oct 14 18:07 sbin
drwxr-xr-x   2 root root  4096 Oct  5 23:39 srv
dr-xr-xr-x  13 root root     0 Oct 16 04:16 sys
drwxrwx---   3 root vcap  1024 Oct 16 04:26 tmp
drwxr-xr-x  11 root root  4096 Oct 14 17:46 usr
drwxr-xr-x  12 root root  4096 Oct  5 23:42 var
lrwxrwxrwx   1 root root    30 Oct  5 23:42 vmlinuz -> boot/vmlinuz-3.19.0-30-generic

Cleaning up ssh artifacts

Director task 21

Task 21 done

Ignore the gateway arguments above – if you are not on AWS you most likely don't need a gateway to get to your job VM.


Write a GO program to convert seconds to hours

Description
Write a GO program to convert seconds to hours
1 hour = 60 minutes = 3600 seconds
Input  : 18000
Output : 5

How to contribute

Save the solution in program/convert_seconds_to_hours.go file
Add convert_seconds_to_hours.go file in convert-seconds-to-hours folder

!assign

Hey @astitva0011,
This issue has been assigned to you for more than 15 days.
We are unassigning you from this issue.
If you are still interested in contributing to this issue, please get auto-assigned on the issue by commenting !assign again.
Thanks for your contributions :)

!assign


Need help on upload the assets in github using Unirest

Need help for the uploading the assets in gitHUb using unirest api. please help on this.
curl -X POST -H 'Authorization: token <token>' -H "Content-Type:octet-stream" --data-binary @temp/file.exe "http://<upload_url>/repos/:owner/:repo/releases/:id/assets?name=file.zip"

unirest.post('http://mockbin.com/request')
.headers({'Content-Type': 'multipart/form-data'})
.field('parameter', 'value') // Form field
.attach('file', '/tmp/file') // Attachment
.end(function (response) {
  console.log(response.body);
});

Example of how to upload a file from the readme, you can change the headers in the headers method to your required headers.


Problems with executing bot.js

https://gyazo.com/5c936724b9a694f1f5f842cb3918a03b
I get this whenever trying to execute the file
My code is the example code just with the message changed
Help please!

You dont run the js file with windows, do node bot.js


Add basic sync command

This command needs to create the request-review branch if necessary, cherry pick the patch into it, associate the request review branch with the patch if necessary, and push that branch up to the remote as a remote branch. a.k.a. syncing the patch with the remote.
This is basically going to do the branch, and sync.

This has been integrated into mainline.


Build fails on amd64: error: call to 'getDataSafe' is ambiguous

/wrkdirs/usr/ports/graphics/ospray/work/ospray-2.9.0/modules/cpu/fb/LocalFB.cpp:56:7: error: call to 'getDataSafe' is ambiguous
      getDataSafe(accumBuffer),
      ^~~~~~~~~~~
/usr/local/include/rkcommon/memory/../common.h:74:6: note: candidate function [with T = rkcommon::math::vec_t<float, 4, false>, A = rkcommon::containers::aligned_allocator<rkcommon::math::vec_t<float, 4, false>, 64>]
  T *getDataSafe(std::vector<T, A> &v)
     ^
/wrkdirs/usr/ports/graphics/ospray/work/ospray-2.9.0/modules/cpu/fb/LocalFB.cpp:12:11: note: candidate function [with T = rkcommon::math::vec_t<float, 4, false>, A = rkcommon::containers::aligned_allocator<rkcommon::math::vec_t<float, 4, false>, 64>]
static T *getDataSafe(std::vector<T, A> &v)
          ^

Version: 2.9.0
clang-13
FreeBSD 13.1

Hi @yurivict , you should use rkcommon v1.9.0 when building OSPRay 2.9, let us know if that fixes the issue. We moved this function into rkcommon for the OSPRay 2.10 & rkcommon 1.10.0 release, but this means that OSPRay 2.9 isn't compatible with rkcommon 1.10, and OSPRay 2.10 isn't compatible with rkcommon 1.9.

We have rkcommon-1.10.0 in ports.
I should wait for the OSPRay release then.

Oh in that case try out OSPRay 2.10 https://github.com/ospray/ospray/releases/tag/v2.10.0 , which we just recently released


⚠ Bofrost.at has degraded performance

In 1c8b59d, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1536 ms

Resolved: Bofrost.at performance has improved in fd3754b.


PowerPack: ability to customize widget visibility

This issue has been mirrored in Jira: https://reddata.atlassian.net/browse/GROK-17034