text:
Cant find GIT_FILTER_CLEANin 1.5.0

I have been having some issues with the new 1.5.0 version which are fixed when changing to 1.4.1. I get the following error.
Traceback (most recent call last):
  File "/mnt/beegfs/home/pearl089/src/page-segmentation/./run-pipeline-stage.py", line 17, in <module>
    cfg = params_show(stages=args.stage)
  File "/mnt/beegfs/home/pearl089/.conda/envs/segmentation/lib/python3.10/site-packages/dvc/api/show.py", line 390, in params_show
    params = _repo.params.show(
  File "/mnt/beegfs/home/pearl089/.conda/envs/segmentation/lib/python3.10/site-packages/dvc/repo/params/__init__.py", line 8, in show
    return show(self.repo, *args, **kwargs)
  File "/mnt/beegfs/home/pearl089/.conda/envs/segmentation/lib/python3.10/site-packages/dvc/repo/__init__.py", line 60, in wrapper
    return f(repo, *args, **kwargs)
  File "/mnt/beegfs/home/pearl089/.conda/envs/segmentation/lib/python3.10/site-packages/dvc/repo/params/show.py", line 205, in show
    _hide_workspace(repo.scm, res)
  File "/mnt/beegfs/home/pearl089/.conda/envs/segmentation/lib/python3.10/site-packages/dvc/repo/metrics/show.py", line 176, in _hide_workspace
    active_branch = scm.active_branch()
  File "/mnt/beegfs/home/pearl089/.conda/envs/segmentation/lib/python3.10/site-packages/scmrepo/git/__init__.py", line 299, in _backend_func
    backend = self.backends[key]
  File "/mnt/beegfs/home/pearl089/.conda/envs/segmentation/lib/python3.10/site-packages/scmrepo/git/__init__.py", line 57, in __getitem__
    initialized = backend(*self.args, **self.kwargs)
  File "/mnt/beegfs/home/pearl089/.conda/envs/segmentation/lib/python3.10/site-packages/scmrepo/git/backend/pygit2/__init__.py", line 156, in __init__
    from .filter import LFSFilter
  File "/mnt/beegfs/home/pearl089/.conda/envs/segmentation/lib/python3.10/site-packages/scmrepo/git/backend/pygit2/filter.py", line 5, in <module>
    from pygit2 import GIT_FILTER_CLEAN, Filter, Passthrough
ImportError: cannot import name 'GIT_FILTER_CLEAN' from 'pygit2' (/mnt/beegfs/home/pearl089/.conda/envs/segmentation/lib/python3.10/site-packages/pygit2/__init__.py)
ERROR: failed to reproduce 'pretrain': failed to run: ./run-pipeline-stage.py --job-type gpu --stage pretrain --script train.py --data data/pretrain-dataset/dataset.y

From a cursory glance at the pygit2 repository, it seems that GIT_FILTER_CLEAN was added only recently, 3 weeks ago from what i see. My assumption is that in the conda package for scmrepo the requirement of pygit2 has not been updated to this newly released version.

A new conda build for scmrepo 1.5.0 has been released with the corrected dependency versions.

authors: finlaymorrison pmrowla

repo: iterative/scmrepo


text:
TLB Misses

To obtain measurements that are consistent with an "idealized execution", you map all memory addresses to the same cache set. While this eliminates cache misses, it does not prevent TLB misses.
An example is the 4881c4380800005b5d415c415d415e415f benchmark ("add rsp,0x838; pop rbx; pop rbp; pop r12; pop r13; pop r14; pop r15"). The difference between your measurements/Ithemal (~6 cycles) and IACA (3 cycles) is due to TLB misses.

Thanks for filing this issue. You are correct. How did you detect the TLB misses? I tried using (PERF_COUNT_HW_CACHE_DTLB) | (PERF_COUNT_HW_CACHE_OP_READ << 8) | (PERF_COUNT_HW_CACHE_RESULT_MISS << 16) but got a counter of 0.

I think the counter you mention measures only L2 TLB misses. I used the DTLB_LOAD_MISSES.STLB_HIT counter which counts loads that miss in the L1 TLB but hit in the L2 TLB.

source: gharchive/issue

repo: ithemal/bhive

license: mit

license_type: permissive

license_source: bigquery


text:
Dataset obtention

Hello. I am interested in using this library and was wondering where to get the corresponding data from.
I am a beginner in this topic.
Greetings and thanks

Hi there,
The links to benchmarks data etc. are in the pre-print:
https://arxiv.org/abs/2204.08941
Cheers
Immanuel Trummer Assistant Professor, Cornell University.
Projects: DB-BERT https://itrummer.github.io/dbbert/ SkinnerDB
https://cornelldbgroup.github.io/skinnerdb/ UDO
https://cornelldbgroup.github.io/UDO/
Twitter: @ImmanuelTrummer https://twitter.com/ImmanuelTrummer
Web: www.itrummer.org
On Sat, Apr 23, 2022 at 3:28 PM alanrivetta @.***>
wrote:

Hello. I am interested in using this library and was wondering where to
get the corresponding data from.
I am a beginner in this topic.
Greetings and thanks
—
Reply to this email directly, view it on GitHub
https://github.com/itrummer/CodexDB/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACXKCXAU7VRSEI4CP3PTFXDVGRFPNANCNFSM5UFDYSYA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

authors: alanrivetta itrummer

repo: itrummer/CodexDB

license: MIT

license_source: github-api


text:
クラウド環境を選定する

https://drive.google.com/drive/#folders/0B9u9agREG4r0fk9kV0hJRUI2ZW1vMFFiQkhOeXNxQTVIT2NheFNvMVJ2UmhkVVU4V2xKeU0

価格その他からOpenShift onlineでいいと思います。
＃Bluemixも基本的には無料で使えそうではありますが
クライアントツールを動かすためにRuby（gem）が必要です。
また、既にSSLキーを持っている場合、ツール実行前に適切な場所に置いといた方がよいです。
＃特にPCからVM上のLinuxへコピーした場合はprivate keyのパーミッションが600になってないと利用可能なキーと見做されない
詳細は、https://developers.openshift.com/en/getting-started-debian-ubuntu.html
ドメインは作成しなくてOKです。

authors: eiwasakai t-kunou

repo: its-succ/rabbit


text:
Forge doesn't work in 1.12.2

Describe the problem
The image crashes when you try to run forge in 1.12.2.
Container definition
docker run -it
-p 25565:25565
-e EULA=TRUE
-e TYPE=FORGE
-e VERSION=1.12.2
itzg/minecraft-server
Container logs
[init] Running as uid=1000 gid=1000 with /data as 'drwxrwxr-x 2 1000 1000 4096 Aug  3 18:19 /data'
[init] Resolving type given FORGE
[mc-image-helper] 14:26:31.979 INFO  : Downloading Forge installer 14.23.5.2859 for Minecraft 1.12.2
[mc-image-helper] 14:26:33.257 INFO  : Running Forge installer. This might take a while...
[init] Creating server properties in /data/server.properties
[init] Disabling whitelist functionality
[init] Setting initial memory to 1G and max to 1G
[init] Starting the Minecraft server...
A problem occurred running the Server launcher.java.lang.reflect.InvocationTargetException
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at net.minecraftforge.fml.relauncher.ServerLaunchWrapper.run(ServerLaunchWrapper.java:70)
at net.minecraftforge.fml.relauncher.ServerLaunchWrapper.main(ServerLaunchWrapper.java:34)
Caused by: java.lang.ClassCastException: class jdk.internal.loader.ClassLoaders$AppClassLoader cannot be cast to class java.net.URLClassLoader (jdk.internal.loader.ClassLoaders$AppClassLoader and java.net.URLClassLoader are in module java.base of loader 'bootstrap')
at net.minecraft.launchwrapper.Launch.(Launch.java:34)
at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
... 6 more
2023-08-05T14:26:45.332Z        WARN    mc-server-runner        Minecraft server failed. Inspect logs above for errors that indicate cause. DO NOT report this line as an error.        {"exitCode": 1}
2023-08-05T14:26:45.332Z        INFO    mc-server-runner        Done

What Java version are you running? (Java 8 could be required)

Java 8 is indeed required. Refer to https://docker-minecraft-server.readthedocs.io/en/latest/versions/java/#running-minecraft-server-on-different-java-version

This did indeed fix the issue, thanks!

authors: KillsT3aler69 itzg palivtom

repo: itzg/docker-minecraft-server


text:
pathlib in script/training_curve.py

Checklist
GitHub

[ ] I've given this PR a concise, self-descriptive, and meaningful title
[ ] I've linked relevant issues in the PR body
[ ] I've applied the relevant labels to this PR
[ ] I've assigned a reviewer

PR contents

[ ] I've consulted ivadomed's internal developer documentation to ensure my contribution is in line with any relevant design decisions
[ ] I've added relevant tests for my contribution
[ ] I've updated the relevant documentation for my changes, including argparse descriptions, docstrings, and ReadTheDocs tutorial pages

Description

Linked issues

Pull Request Test Coverage Report for Build 1095218592

15 of 18 (83.33%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.005%) to 70.104%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

ivadomed/scripts/training_curve.py
15
18
83.33%

Totals

Change from base Build 1088103331:
-0.005%

Covered Lines:
4113

Relevant Lines:
5867

💛  - Coveralls

source: gharchive/pull-request

authors: cakester coveralls

repo: ivadomed/ivadomed


text:
Reverse-strand alignment sorted by end position in AlignmentsTrack pileup

Hi Robert, I would like to use Gviz to visualize long-read data alignments. My main issue is a sort/order of reads mapped to the reverse strand. The pileups are by default sorted by start coordinates which makes it difficult to read. Would it be possible to sort the alignments by the end position instead? Maybe only when reverseStrand=T. I believe it would make sense for short-read visualization as well. Another option would be to allow a custom order for the alignments.
Forward strand read alignment looks nice (example here) and I would like the reverse strand read alignment to look the same (right now I have this).  The style I would like to have is the top left corner to the bottom right corner diagonal in the forward strand alignments.

Hi @opplatek,
There is no way how to define the order of the alignments, Gviz tries to order them efficiently for plotting. Have you also tried to set reverseStacking=TRUE ? It will reverse the order of the reads for plotting (from bottom to top).

Hi @ivanek,
Yes, I have tried the  reverseStacking=TRUE, didn't help. So it's really not possible to change the sort from start position to end position? I understand Gviz tries to fit the alignments to a single view but they are obviously sorted by the start position.
If it's not possible I will try to find some other way how to make the visualization look nice and you can close this thread. Thanks.

authors: ivanek opplatek

repo: ivanek/Gviz


text:
Can this be used as a primary key?

For example, right now I'm doing the following:
import uuid
from django.db import models

class YourModel(models.Model):
    id = models.UUIDField(primary_key=True, default=uuid.uuid4, editable=False)

Would it make sense to?
from django.db import models
from django_uidfield.fields import UIDField

class YourModel(models.Model):
    id = UIDField(primary_key=True, editable=False, max_length=20)

Sure, see the appropriate test: https://github.com/ivelum/django-uidfield/blob/master/django_uidfield/tests.py#L41-L47

I mean more not "is it technically possible" but is it a good idea? :)
Is there any advantage of using django-uidfield vs UUIDField from django.models?

authors: iceone littlepea

repo: ivelum/django-uidfield


text:
missing parentheses

Frontend build error
Here is the error message:
ERROR in ./src/components/allocation/files.js

  239:11  error  Missing parentheses around multilines JSX                react/jsx-wrap-multilines
  239:11  error  Expected indentation of 8 space characters but found 10  react/jsx-indent
  256:11  error  Missing parentheses around multilines JSX                react/jsx-wrap-multilines
  256:11  error  Expected indentation of 8 space characters but found 10  react/jsx-indent

It seems parentheses are needed in ./src/components/allocation/files.js

Hi @waterdudu
As part of the rewrite in #153 this should be fixed :)
Are you working on a new feature, or just building it for local usage? :)

Thanks @jippi
Just building it for local usage, it's quite a good tool to manage nomad jobs and allocations rather than using nomad status

@waterdudu okay, each release got binaries (go binary) which include everything :)
https://github.com/iverberk/nomad-ui/releases

Great! @jippi

authors: jippi waterdudu

repo: iverberk/nomad-ui


text:
RangeError: Maximum call stack size exceeded

while using gulp-typescript as transcoder for my project I get a Maximum call stack size exceeded.
there is my gulp task :
gulp.task('typescript', function(){
  return gulp.src('./assets/ts/**/*.ts')
    .pipe(ts({
        sortOutput: true,
        noImplicitAny: true,
        out: 'main.js'
      }))
    .pipe(gulp.dest('./assets/js'));
});

here is the error I get
/vagrant/typescript-angular-sass/node_modules/gulp-typescript/release/output.js:
188
                    var references = file.original.ts.referencedFiles.map(functi
on (file) { return tsApi.getFileName(file); });
                                                                      ^

RangeError: Maximum call stack size exceeded
    at Array.map (native)
    at sortedEmit (/vagrant/typescript-angular-sass/node_modules/gulp-typescript
/release/output.js:188:71)
    at sortedEmit (/vagrant/typescript-angular-sass/node_modules/gulp-typescript
/release/output.js:191:25)
    at sortedEmit (/vagrant/typescript-angular-sass/node_modules/gulp-typescript
/release/output.js:191:25)
    at sortedEmit (/vagrant/typescript-angular-sass/node_modules/gulp-typescript
/release/output.js:191:25)
    at sortedEmit (/vagrant/typescript-angular-sass/node_modules/gulp-typescript
/release/output.js:191:25)
    at sortedEmit (/vagrant/typescript-angular-sass/node_modules/gulp-typescript
/release/output.js:191:25)
    at sortedEmit (/vagrant/typescript-angular-sass/node_modules/gulp-typescript
/release/output.js:191:25)
    at sortedEmit (/vagrant/typescript-angular-sass/node_modules/gulp-typescript
/release/output.js:191:25)
    at sortedEmit (/vagrant/typescript-angular-sass/node_modules/gulp-typescript
/release/output.js:191:25)

seems like I have an infinit loop in sortedEmit function on my system
system infos
$ node --version
v5.6.0
$ npm --version
3.6.0
$ gulp --version
[16:56:49] CLI version 1.2.1
[16:56:49] Local version 3.9.1

regards

Can you share your project? I cannot reproduce it with some small projects. I also think that you don't need the sortOutput option, can you try to disable it?

You can see the project there : https://github.com/FlyersWeb/typescript-angular-sass/tree/dev
It worked without sortOutput

Since sortOutput has been removed in version 3 (see #413), this shouldn't happen any more.

authors: FlyersWeb ivogabe

repo: ivogabe/gulp-typescript


text:
execute multiple commands with &

hr currently doesn't seem to support chaining commands with &
hr -c "go build & ./server"

Currently it is not my top priority. One workaround is to put multiple commands in single script, and then execute that script. If you are interested in PR, they are welcome.

Fixed by https://github.com/ivpusic/go-hotreload/pull/6

authors: ivpusic prabirshrestha

repo: ivpusic/go-hotreload


text:
Support downloading config file from S3 bucket

If you are running separate yace instances in test and production, it would be convenient if you would be able to use same docker image in both places and simply tell that download yace config file from s3://bucket_name/s3_object_key
The reason, why we have to specify AWS_REGION (you can override that as well when you specify env variable for CONFIG_FILE) is that we have to specify some region for the AWS session that would download the config file from S3 bucket.

Hey @jylitalo thanks for your contributions.
I think this adds too much complexity for a rare use case.
I would suggest that you solve your problem by building your own image e.g.:
You could add your config file, and then run this image on both environments.
FROM quay.io/invisionag/yet-another-cloudwatch-exporter:vxxxx
ADD config /etc/config.yml

Sorry to disappoint you here.
Greetings, Thomas

No worries!
First I thought that I would build entrypoint script, which would use awscli to copy a config file from S3 to the local filesystem, but our base mage doesn't have awscli and I thought that it wouldn't make sense to add it, since I already have all the relevant libraries in golang.
Anyways, we already have our local builds and this is something that we can always rebase on top of yace master, so this is not big issue for us.

authors: jylitalo thomaspeitz

repo: ivx/yet-another-cloudwatch-exporter


text:
run on replit?

hey , i know its a dumb question but is there a way to run it on replit?

Hello, I have never tested it on replit but I think yes, It'll work.
And also I don't recommend it, because you'll share your secrets keys on the cloud which should stay between you and your computer.

i have premium stuff so its private and uh i think basically like what language should i use?


text:
🛑 Takagi is down

In f0cdc02, Takagi (https://lixingyong.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Takagi is back up in a99d721.

repo: iwyang/check


text:
🛑 21Eurkon is down

In ec34ac9, 21Eurkon (https://blog.eurkon.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 21Eurkon is back up in e2061a6 after 18 minutes.


text:
CDEBUG_WORKSPACE points to the sidecar filesystem root

Motivation
I have a kind cluster with at least 1 worker and I'd like to use cdebug to instrument a sidecar with enough tooling to run the kubelet in debug mode.
The sidecar is built from a custom image with the following things:

A systemd service for kubelet-debug, this is similar to the kubelet systemd service but instrumented to run the kubelet through delve
An entrypoint script that's run through cdebug exec, when the entrypoint script is executed:

it copies all the tooling to the target image, in this case dlv and the new systemd service
stops the kubelet service and starts the kubelet-debug service

At this point a target container (e.g. kind-worker) is running the kubelet through dlv, then editors can connect to it to start a debugging session.
Steps:

Create an image for the sidecar with tooling to provide debugging tools

FROM golang:bullseye AS go
RUN apt update && apt install git -y
RUN go install github.com/go-delve/delve/cmd/dlv@latest
RUN git clone https://github.com/garabik/grc.git /go/src/github.com/garabik/grc

FROM debian:bullseye
RUN apt update && apt install --only-upgrade bash -y
RUN mkdir -p /app/bin
COPY --from=go /go/bin/dlv /app/bin/dlv
COPY --from=go /go/src/github.com/garabik/grc /app/grc

WORKDIR /app
ADD . .
RUN (cd ./grc && ./install.sh)

ENTRYPOINT ["sleep", "infinity"]

In the Dockerfile workspace there are additional files related to the kubeadm setup of the kubelet
10-kubeadm.conf

Click me
# Note: This dropin only works with kubeadm and kubelet v1.11+
# from the worker node /etc/systemd/system/kubelet.service.d
#
# Override: ExecStart runs the kubelet through delve

[Service]
Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf"
Environment="KUBELET_CONFIG_ARGS=--config=/var/lib/kubelet/config.yaml"
# This is a file that "kubeadm init" and "kubeadm join" generates at runtime, populating the KUBELET_KUBEADM_ARGS variable dynamically
EnvironmentFile=-/var/lib/kubelet/kubeadm-flags.env
# This is a file that the user can use for overrides of the kubelet args as a last resort. Preferably, the user should use
# the .NodeRegistration.KubeletExtraArgs object in the configuration files instead. KUBELET_EXTRA_ARGS should be sourced from this file.
EnvironmentFile=-/etc/default/kubelet
# On cgroup v1, the /kubelet cgroup is created in the entrypoint script before running systemd.
# On cgroup v2, the /kubelet cgroup is created here. (See the comments in the entrypoint script for the reason.)
ExecStartPre=/bin/sh -euc "if [ -f /sys/fs/cgroup/cgroup.controllers ]; then create-kubelet-cgroup-v2; fi"
# on WSL2 (and potentially other distros without systemd) /sys/fs/cgroup/systemd is created after the entrypoint, during /sbin/init.
# This eventually leads to kubelet failing to start, see: https://github.com/kubernetes-sigs/kind/issues/2323
ExecStartPre=/bin/sh -euc "if [ ! -f /sys/fs/cgroup/cgroup.controllers ] && [ ! -d /sys/fs/cgroup/systemd/kubelet ]; then mkdir -p /sys/fs/cgroup/systemd/kubelet; fi"
ExecStart=
# I got these args by looking at how skaffold sets up debugging.
ExecStart=dlv exec --headless --continue --accept-multiclient --listen=:56268 --api-version=2 /usr/bin/kubelet-debug -- $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_KUBEADM_ARGS $KUBELET_EXTRA_ARGS --cgroup-root=/kubelet --v=2

kubelet-debug-entrypoint.sh

Click me
#!/bin/bash

set -euo pipefail

install() {
  # setup systemd kubelet-debug.service unit
  systemd=/etc/systemd/system
  mkdir -p "${systemd}/kubelet-debug.service.d"
  cp $CDEBUG_WORKSPACE/app/kubelet-debug.service "${systemd}"
  cp $CDEBUG_WORKSPACE/app/10-kubeadm.conf "${systemd}/kubelet-debug.service.d/10-kubeadmin.conf"

  # copy kubelet to a debug file if it doesn't exist already
  if [[ ! -f /usr/bin/kubelet-debug ]]; then
    cp /usr/bin/kubelet /usr/bin/kubelet-debug
  fi

  # copy dlv if not already there
  if [[ ! -f /usr/bin/dlv ]]; then
    cp $CDEBUG_WORKSPACE/app/bin/dlv /usr/bin/dlv
  fi

  # start kubelet-debug unit and disable kubelet unit
  systemctl daemon-reload
  systemctl disable kubelet && systemctl stop kubelet
  systemctl enable kubelet-debug && systemctl start kubelet-debug
}

restore() {
  # restore kubelet systemd unit
  systemctl disable kubelet-debug && systemctl stop kubelet-debug
  systemctl enable kubelet && systemctl start kubelet
}

install
trap restore exit

bash

kubelet-debug.service

Click me
# slightly modified from:
# https://github.com/kubernetes/kubernetes/blob/ba8fcafaf8c502a454acd86b728c857932555315/build/debs/kubelet.service
[Unit]
Description=kubelet: The Kubernetes Node Agent
Documentation=http://kubernetes.io/docs/
# NOTE: kind deviates from upstream here to avoid crashlooping
# This does *not* support altering the kubelet config path though.
# We intend to upstream this change but first need to solve the upstream
# Packaging problem (all kubernetes versions use the same files out of tree).
ConditionPathExists=/var/lib/kubelet/config.yaml

[Service]
ExecStart=/usr/bin/kubelet
Restart=always
StartLimitInterval=0
# NOTE: kind deviates from upstream here with a lower RestartSecuse
RestartSec=1s

[Install]
WantedBy=multi-user.target

Build the image: docker build -t kubelet-debug:latest .
Run cdebug targeting the kind-worker container cdebug exec --image kubelet-debug:latest -it docker://kind-worker '$CDEBUG_WORKSPACE/app/kubelet-debug-entrypoint.sh'
Exec into the kind-worker container and check the status of the systemd services

○ kubelet.service - kubelet: The Kubernetes Node Agent
     Loaded: loaded (/etc/systemd/system/kubelet.service; disabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/kubelet.service.d
             └─10-kubeadm.conf
     Active: inactive (dead)
       Docs: http://kubernetes.io/docs/

root@kind-worker:/# systemctl status kubelet-debug
● kubelet-debug.service - kubelet: The Kubernetes Node Agent
     Loaded: loaded (/etc/systemd/system/kubelet-debug.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/kubelet-debug.service.d
             └─10-kubeadmin.conf
     Active: active (running) since Thu 2023-01-26 05:02:50 UTC; 13s ago

Check that the dlv server started

root@kind-worker:/# journalctl -u kubelet-debug
...
Jan 26 05:02:50 kind-worker dlv[632591]: API server listening at: [::]:56268
...

At this point we can start a debugging session

At this point is where I'd sync the kubelet compiled in debug mode (I wrote the instructions on how to do that here: https://github.com/mauriciopoppe/kubernetes-playground/blob/master/docs/kubelet.md#normal-workflow) and I'd sync it to the directory created by the sidecar and restart the kubelet-debug service

To end the session hit ctrl-c on the terminal where the sidecar is running as part of the teardown most of the instrumentation code will be removed and it'll leave the original kubelet running as it was before

Implementation details
This is possible by creating a special envvar CDEBUG_WORKSPACE that points to the location of the sidecar root filesystem, the sidecar image can use this var to install tooling on the target container as seen above in the cdebug exec execution

Friendly ping, what do you think about this proposal?

Sorry, was (and still am) really short on time for the past few weeks. From first sight, having this flexibility makes perfect sense. But I'll have to give it another look with a clearer head. Hopefully, this weekend. Thanks for your contribution!

Pinging back, what do you think about this proposal?

@iximiuz Sure, I've changed the env var to be CDEBUG_ROOTFS I also added some instructions about how I tested it in the description.

authors: iximiuz mauriciopoppe

repo: iximiuz/cdebug


text:
Update getting started guide in README

Current guide to getting started appears out of date.
Should include copyinig the .env.example file to .env
But the current example.env file does not actually work. At least this URL is incorrect - https://block_sync_pandora.ixo.world/
Note also links to IXO Module and IXO Keyserver both seem to go to this https://github.com/wmonk/create-react-app-typescript

@wip-abramson thanks for this! This is being rectified along with better documentation elsewhere

Cleared.

authors: demondayza wip-abramson

repo: ixofoundation/ixo-webclient


text:
Automatic arrow direction

There should be an automatic arrow direction option, because we might not know where the popover fits best.
If you try to display it too close to the edge of the screen the popover renders truncated:

My current solution is to add this to the button from you're launching the popover:
@State private var buttonRect: CGRect = .zero

  var pickerDirection: MCPickerArrowDirection {
    if buttonRect.minY < 300 {
      return .up
    } else {
      return .down
    }
  }

Either use a Geometry Reader on the background of the button, or a helper method like I do:
.onRectChange(onChangeRect: {
        buttonRect = $0
      })
      .emojiPicker(isPresented: $isShowingEmojiPicker,
                   selectedEmoji: $selectedEmoji,
                   arrowDirection: pickerDirection)

repo: izyumkin/MCEmojiPicker


text:
NPE in DefaultRulesEngine when Rules/Facts are null

org.jeasy
easy-rules-core
4.1.0

DefaultRulesEngine defaultEngine = new DefaultRulesEngine();
defaultEngine.fire(new Rules(), null);
The above code will report a NullPointerException

Fixed in #335 .

repo: j-easy/easy-rules


text:
typo correction

a small typo in a comment

Thanks!

authors: B-Gaudeul j-fu


text:
Make use of oneShot?

The oneShot special function can be used to identify a function as being called a maximum of one time. This can allow for more aggressive optimisations. Is it possible to mark out continuations with this?

Couple thoughts:

Would this be as simple as making a smart constructor for Internal.Parsec that just wraps the supplied continuations with oneShots?
It is probably best to have some benchmarking to see if it is worth it, I guess.


text:
Differential pair pins: require unique label?

I'm attempting to find and ideal way to document differential pair pins with pinout.
If you have experience with them and opinions on how you would like to see them documented in a pinout diagram feel free to post and comment on the discussion here :)

Lattice has an application note: Using Differential I/O that has just a dotted line around the pairs:

Perhaps something similar to "group" the pinout labels?

Depends a bit if they are always diff pairs or not to begin with. In a FPGA it's often configurable whether they act as a diff pair or not.
But in general just having a + / - signs on the respective pins and a common prefix for the name is enough, don't really need anything fancy. It gets more complicated when the pins are not next to each other :/  And yeah, that happens ...

@j0ono0
Few ideas borrowed from various places:

Appending _P _N to the pin names (some software routines can even account on this rule)
Highlighting the pins using + - extra symbols (plus even _P and _N on the labels)
Add a special symbol on traces (or right on pins) like Altium(TM) CAD does it.

IMO that Lattice(TM) diagram with dotted/dashed lines is counter-intuitive (my mind thinks to some parasitic shielding).

Thanks for the fast responses and comments everyone!
some notes of my own (largely in response and extending other comments)...
Label text as an indicator for differential pair pins - Label content is 100% user supplied so this can be catered for as users preprocess content. Python is also well suited to list manipulation via list-comprehensions -- so my feeling is to leave this up to users rather than build in some enforced standard.
I've given some thought to a method of graphically linking pin locations:

...technically it would only require a new leader-line but might through up some complexities around how user would document x2 pins for labels.
On further reflection I wondered if compactness is not such a good goal  - especially for complex hardware that is likely to have printed/PDF docs in A4 (or Letter) format. On that thought I mocked up what a full pinout graphic might be:

By pulling out each set of pins it:

leaves less potential ambiguity
allows ability to include notes for sets of pins
caters for pins to be labelled independently (ie not as pairs) without re-configuring a preexisting template
An assumption > would allow pin functions of a programmed FPGA board to be documented, without re-configuring a preexisting template

On capability to achieve such a layout with pinout,  I think it might already technically possible, but need try/review/amend before claiming that victory.
So, after a day of pondering it, I feel the latter example might be a better goal to aim for? Open to other opinions and input to my thinking.

A plus por minus sign after the name is simple and clear enough IMO

@j0ono0
I personally like idea A (elegant and compact label) with some amends:

add +/- extra symbol or _P _N to label
longer arrow line to touch booth physical pins/holes (now touches one)
add | symbol in between physical pins/holes (just like it is between the labels)

Another rule: In 99% of cases diff pair pins will be in the same places (as pair) otherwise it fails the impedance constrains on the very PCB, so YES this compactization (idea A) of label pairs can be a main rule. Probably some slow diff signals like RS485 may afford pins that not at the same place but those are labeled as A and B by whole industry (not even highlighting their differential nature).

@j0ono0
I personally like idea A (elegant and compact label) with some amends:

add +/- extra symbol or _P _N to label
longer arrow line to touch booth physical pins/holes (now touches one)
add | symbol in between physical pins/holes (just like it is between the labels)

Another opinion (last):  Variant C (of arrow) in your second graph/draw solves all my last two amends in most elegant way.

I also like the idea of _P and _N naming.

Feedback seems to suggest naming conventions are adequate to communicate the diferential-pair relation. I still haven't ruled out creating some graphical icon down the track. Some twitter posts combined with a recent layout experiment matched up nicely so I thought it worth recording here --
'double-layer' sample generated with pinout (thanks to @somhi for suggesting it):

Mockup of possible 'joining' icon:

authors: cbalint13 gojimmypi j0ono0 pkatarzynski smunaut suarezvictor


text:
Disabling modules "volume" (reason: Cannot find simple element)

Saw quite a few posts on this, none of the solutions worked for me.
Polybar was compiled with Alsa support.
Here's the output of amixer scontrols:
Simple mixer control 'Master',0 Simple mixer control 'Capture',0

My dumb ass had config stuff wrong, sorry!

repo: jaagr/polybar


text:
fix(mpd): Check state before calling playback controls

Hello.
This should fix #500
I also  added checks before play(), pause() and stop() for consistency, if you have any concerns please let me know.

Looks good to me, thanks!

authors: TonCherAmi jaagr


text:
Expression vtable missing under ld or gold

After #71, Zircon cannot be built using ld or gold. For some reason, they cnanot find the vtables generated in expr.cpp.o. It is possibly an issue with them determining the key function, but since both lld and mold work it is puzzling.

Resolved by #97


text:
Find an easy way to disable "non essentials" Docker compose services for testing purposes in local

https://stackoverflow.com/questions/37254881/is-there-any-way-to-disable-a-service-in-docker-compose-yml

  usecase1a:
    image: ghcr.io/jabrena/usecase1-a:buildpacks-jvm.0.0.1-SNAPSHOT
    ports:
      - 8084:8084
    environment:
      - SERVER_PORT=8084
      - USE_CASE_B=http://usecase1b:8081/
    depends_on:
      - "usecase1b"
    networks:
      - usecase1
    profiles:
      - donotstart


text:
Feature/1066 Capture commissioner conflicts

What's included?
Closes #1066
Who should test?
✅ Product owner
✅ Developers
✅ UTG
How to test?
Example vacancy: https://jac-apply-develop--pr1087-feature-1066-capture-s74e5f8l.web.app/vacancy/ONqUjAzhDS7rjh6dFJLB/

Apply for the vacancy.
Complete the "Commissioner Conflicts" section.
Check if the answers are saved on the review page.

Risk - how likely is this to impact other areas?
🟢 No risk - this is a self-contained piece of work
Additional context
Demo:
https://github.com/jac-uk/apply/assets/79906532/347f6dce-fc16-41c3-9058-4fc33b09d73d

PREVIEW:DEVELOP
can be OFF, DEVELOP or STAGING

In the commissioner conflict page, after I selected the options , I was unable to save and cotinue. The page was static hence my options were not save neither was it labelled as DONE.

@Franceswog Could you provide a screenshot, please?

@HalcyonJAC Could you pls amend the first sentence of text at the top of the page to:
Members of the Judicial Appointments Commission (JAC) come from a wide background to ensure the Commission has a breadth of knowledge, expertise and independence.

@HalcyonJAC I have requested Welsh translation for the content of this page

@HalcyonJAC Please see translation below to enable creation of parallel page in Welsh:
Commissioner conflicts
Members of the Judicial Appointments Commission (JAC) come from a wide background to ensure the Commission has a breadth of knowledge, expertise and independence. Are you related to, or known to any of the JAC Commissioners? If you are in any doubt then please select 'Yes' in the list below:
Gwrthdaro buddiannau
Mae Aelodau’r Comisiwn Penodiadau Barnwrol (JAC) yn dod o amrywiaeth eang o gefndiroedd i sicrhau bod gan y Comisiwn wybodaeth, profiad ac annibyniaeth eang. Ydych chi’n perthyn i unrhyw un o Gomisiynwyr y JAC neu a ydynt yn gwybod pwy ydych chi? Os oes gennych unrhyw amheuon dewiswch ‘Ydw’ yn y rhestr isod:
Please provide details of your relationship.
Rhowch fanylion eich perthynas.
I do not have a pre-existing relationship with any of the commissioners
Nid oes gennyf unrhyw fath o berthynas ag unrhyw un o’r comisiynwyr
Yes
Ydw
No
Nac ydw
Save and continue
Cadw a pharhau

@HalcyonJAC Please see translation below to enable creation of parallel page in Welsh:
Commissioner conflicts Members of the Judicial Appointments Commission (JAC) come from a wide background to ensure the Commission has a breadth of knowledge, expertise and independence. Are you related to, or known to any of the JAC Commissioners? If you are in any doubt then please select 'Yes' in the list below: Gwrthdaro buddiannau Mae Aelodau’r Comisiwn Penodiadau Barnwrol (JAC) yn dod o amrywiaeth eang o gefndiroedd i sicrhau bod gan y Comisiwn wybodaeth, profiad ac annibyniaeth eang. Ydych chi’n perthyn i unrhyw un o Gomisiynwyr y JAC neu a ydynt yn gwybod pwy ydych chi? Os oes gennych unrhyw amheuon dewiswch ‘Ydw’ yn y rhestr isod:
Please provide details of your relationship. Rhowch fanylion eich perthynas.
I do not have a pre-existing relationship with any of the commissioners Nid oes gennyf unrhyw fath o berthynas ag unrhyw un o’r comisiynwyr
Yes Ydw
No Nac ydw
Save and continue Cadw a pharhau

@nickaddy The Welsh translations have been updated.

Can't be released yet due to live exercises.

authors: HalcyonJAC nickaddy

repo: jac-uk/apply


text:
Colorbox Popup not coming in center in the iPad

When i am opening color box popup in iPad then popup is not coming in the center of the ipad body.
sometimes when i changes the mode from portrait to landscape or landscape to portrait then it seems fine but that happen once in a while.
Please suggest a solution?

Also noticing this issue on the latest version of IOS. On other browsers/devices the Colorbox appears in the center, on IOS it seems to be at the top of the page so the user is required to scroll up to it. Has anyone found a fix for this?

repo: jackmoore/colorbox


text:
Does not work for custom data type

I have a geometry column in one of my tables and for that I have defined a custom data type with Scan and Value methods like this:
type Point struct {
	X float64
	Y float64
	Z float64
}

type Coordinate Point

// Scan scan value into geom.Point, implements sql.Scanner interface
func (c *Coordinate) Scan(value interface{}) error {

	b, ok := value.([]byte)
	if !ok {
		return errors.New("not a byte" array)
	}
	dst := make([]byte, len(b))
	_, err := hex.Decode(dst, b)
	if err != nil {
		return err
	}
	gt, err := ewkb.Unmarshal(dst)
	if err != nil {
		return err
	}
	c.X = gt.FlatCoords()[0]
	c.Y = gt.FlatCoords()[1]
	return nil
}

// Converting cordinate to geom.point
func (c Coordinate) Value() (driver.Value, error) {
	b := geom.NewPoint(geom.XY)
	b.SetCoords(geom.Coord{c.X, c.Y})
	a, err := wkt.Marshal(b)
	s := fmt.Sprintf("SRID=%d;%s", 4326, a)
	return s, err
}

And this Coordinate type is used in the DB struct like show below:
type Survey struct {
        SurveyID         string    `db:"survey_id"`
	CompanyName      string    `db:"company_name"`
        Gcps []Gcp
}

type Gcp struct {
	GcpID           int64       `db:"gcp_id"`
	PointID string      `db:"point_id"`
	Coordinate      *Coordinate `db:"coordinate"`
}

When I try to map the DB rows to the Survey model, all the fields are mapped but the coordinate is left out and its Scan method is never called.
Following is the code snippet:
	rows, err := i.db.Query(query)
	if err != nil {
		log.Error(err)
		return nil, err
	}
	fs := []model.Survey{}
	err = carta.Map(rows, &fs)
	if err != nil {
		log.Error(err)
		return nil, err
	}

which database are you using. In addition, what is the underlying data type of the Point type in the database?

I am using postgresql with postgis extension. Data type in DB is geometry

repo: jackskj/carta


text:
need tests

I think plotting is too hard to test.  Sad.  So that leaves...

[ ] bardensr.spot_calling.estimate_density_iterative
[x] bardensr.spot_calling.estimate_density_singleshot
[x] bardensr.spot_calling.find_peaks
[x] bardensr.registration.apply_translations
[x] bardensr.registration.find_translations_using_model
[x] bardensr.preprocessing.background_subtraction
[x] bardensr.preprocessing.minmax
[x] bardensr.preprocessing.preprocessing_tf.gaussian_filter_1d
[x] bardensr.preprocessing.preprocessing_tf.minmax

well.  do i really want to test iterative?  at this time -- i do not.

repo: jacksonloper/bardensr


text:
add biff.crux/submit-tx-as-user

Currently, biff.crux/submit-tx bypasses authorization functions (but not specs). It's assumed that you're doing your own authorization before calling submit-tx. However there are cases where you'd want to submit a transaction from the back-end but still rely on Biff's authorization rules.
After this is done, we could add a /api/submit-tx endpoint that receives a POST with form parameters. It would be very handy for multi-page applications.

biff.crux/submit-tx now takes a :biff.crux/authorize (default false) which handles this.

repo: jacobobryant/biff


text:
how to write code in restangular?))

how to write code in restangular? For example, in angular, I wrote in the html
ng-click="paginateBack()"
and
$scope.paginateBack = function () {}
in controller,
how to implement it here? The video in YouTube is explained only form, but how do other things not shown dynamic.Sorry for my english , it is google translate.

@normann1993 there's no difference, you can use it just like we used it in the screencasts
Make sure to check the official documentation for Restangular


text:
File css/final.css not defined in asset manifest.

File css/final.css not defined in asset manifest. (View: C:\xampp\htdocs\laravel5-angular-material-starter\resources\views\index.blade.php)

I'm submitting a ...
[ ] bug report
[ ] feature request
[ ] support request
[ ] other (Please specify)
Provide information & explanation
Got code samples?
Make sure to use 3 backticks (and javascript or php after it to show your code) More info
Also make sure to click on the Preview button to double check your code formatting
Laravel & Angular version: 3.2.0

Hi @markib
Thanks for creating an issue
Can you elaborate more on what the problem is?

Feel free to re-open with more information!

authors: jadjoubran markib


text:
Does it work with downloaded Videos?

Hi,
I did not find any comment on this topic yet, so here again.
I am using cordova 5 with API22, having a working Video (played it successfully on my Galaxy S4 mini).
What I am doing now is creating an app that either streams the videos (that part works fine)
or downloads them to the local filesystem i.e. file://data/data/com.kosmoskosmos.myproject/9999.mp4,
once you klick a specific button. Download etc. works finde. iOS doesn't have any problem with it (also playing from this source).
I understood that the plugin is requiring to have the files kept in  $PROJECT_ROOT/platforms/android/res/raw
Does anyone have a hint how to solve this issue?

You can also load videos from your data directory, however you need to make them WORLD_READABLE. Check the copyResourceFileToDataDir() function in the Java file to see how to do that.

authors: kosmonowt odbol


text:
Jaeger  Operator not create query & collector pods

After I deployed the Jaeger operator on my cluster with the following configuration :
on kubernetes version 1.12.8
works with Elasticsearch operator as the DB source
apiVersion: jaegertracing.io/v1
kind: Jaeger
metadata:
  name: jaeger-operator
spec:
  strategy: production
  ingress:
    hosts:
      - jaeger-stg.nextinsurance.io
  storage:
    type: elasticsearch
    options:
      es:
        server-urls: https://jaeger-storage-es-http:9200
        tls:
          ca: /es/certificates/ca.crt
        num-shards: 1
        num-replicas: 0
    secretName: jaeger-secret
    esIndexCleaner:
      enabled: true
      image: jaegertracing/jaeger-es-index-cleaner:1.16.0
      numberOfDays: 7
      resources: {}
      schedule: 55 23 * * *
  volumeMounts:
    - name: certificates
      mountPath: /es/certificates/
      readOnly: true
  volumes:
    - name: certificates
      secret:
        secretName: jaeger-storage-es-http-certs-public

I try to deploy it again on a new cluster with version 1.16.9
And it didn't create the jaeger collector and the query pods.
What is missing?
Is there any way to find logs the show Jaeger errors?

Can you share your jaeger-operator deployment specification e.g. k get deploy jaeger-operator?
It might be that the operator is not watching the namespace where the CR is created.

Here is the jaeger deployment on the new k8s cluster:
ku -n observability get deployment jaeger-operator -o yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: jaeger-operator
  namespace: observability
  resourceVersion: "1184256"
  selfLink: /apis/apps/v1/namespaces/observability/deployments/jaeger-operator
  uid: 3ddfdaae-55cc-47e9-983a-59aec1658e49
spec:
  progressDeadlineSeconds: 600
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      name: jaeger-operator
  strategy:
    rollingUpdate:
      maxSurge: 25%
      maxUnavailable: 25%
    type: RollingUpdate
  template:
    metadata:
      creationTimestamp: null
      labels:
        name: jaeger-operator
    spec:
      containers:
      - args:
        - start
        env:
        - name: WATCH_NAMESPACE
        - name: POD_NAME
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.namespace
        - name: OPERATOR_NAME
          value: jaeger-operator
        image: jaegertracing/jaeger-operator:1.16.0
        imagePullPolicy: Always
        name: jaeger-operator
        ports:
        - containerPort: 8383
          name: metrics
          protocol: TCP
        resources: {}
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
      dnsPolicy: ClusterFirst
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext: {}
      serviceAccount: jaeger-operator
      serviceAccountName: jaeger-operator
      terminationGracePeriodSeconds: 30

I saw that there were differences in ServiceAccount on the new k8s cluster that the Jaeger Operator would move to
Here is the old version
apiVersion: v1
kind: ServiceAccount
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","kind":"ServiceAccount","metadata":{"annotations":{},"name":"jaeger-operator","namespace":"monitoring-stg"}}
  creationTimestamp: "2020-05-11T11:30:59Z"
  labels:
    app: jaeger
    app.kubernetes.io/component: service-account
    app.kubernetes.io/instance: jaeger-operator
    app.kubernetes.io/managed-by: jaeger-operator
    app.kubernetes.io/name: jaeger-operator
    app.kubernetes.io/part-of: jaeger
  name: jaeger-operator
  namespace: monitoring-stg
  ownerReferences:
  - apiVersion: jaegertracing.io/v1
    controller: true
    kind: Jaeger
    name: jaeger-operator
    uid: 85d742d2-76f3-4ba2-9808-555d7725006e
  resourceVersion: "1189791"
  selfLink: /api/v1/namespaces/monitoring-stg/serviceaccounts/jaeger-operator
  uid: 02f986d8-1456-4672-bbf4-0c1765d458ea
secrets:
- name: jaeger-operator-token-vwwql

and the new version looks like this
apiVersion: v1
kind: ServiceAccount
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","kind":"ServiceAccount","metadata":{"annotations":{},"name":"jaeger-operator-new","namespace":"monitoring-stg"}}
  creationTimestamp: "2020-05-13T14:18:51Z"
  name: jaeger-operator-new
  namespace: monitoring-stg
  resourceVersion: "1733099"
  selfLink: /api/v1/namespaces/monitoring-stg/serviceaccounts/jaeger-operator-new
  uid: 791497f6-7ecb-4824-883a-27ef22ff3950
secrets:
- name: jaeger-operator-new-token-k5tlv

after I comper between them, the resources were created on the new cluster

+1

here is the jaeger-operator.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
    deployment.kubernetes.io/revision: "1"
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"apps/v1","kind":"Deployment","metadata":{"annotations":{},"name":"jaeger-operator","namespace":"observability"},"spec":{"replicas":1,"selector":{"matchLabels":{"name":"jaeger-operator"}},"template":{"metadata":{"labels":{"name":"jaeger-operator"}},"spec":{"containers":[{"args":["start"],"env":[{"name":"WATCH_NAMESPACE","valueFrom":{"fieldRef":{"fieldPath":"metadata.namespace"}}},{"name":"POD_NAME","valueFrom":{"fieldRef":{"fieldPath":"metadata.name"}}},{"name":"POD_NAMESPACE","valueFrom":{"fieldRef":{"fieldPath":"metadata.namespace"}}},{"name":"OPERATOR_NAME","value":"jaeger-operator"}],"image":"jaegertracing/jaeger-operator:1.18.0","imagePullPolicy":"Always","name":"jaeger-operator","ports":[{"containerPort":8383,"name":"metrics"}]}],"serviceAccountName":"jaeger-operator"}}}}
  creationTimestamp: "2020-05-29T07:57:49Z"
  generation: 2
  name: jaeger-operator
  namespace: observability
  resourceVersion: "493461"
  selfLink: /apis/apps/v1/namespaces/observability/deployments/jaeger-operator
  uid: 60487a2b-1ad9-403e-902f-c842b33ad09b
spec:
  progressDeadlineSeconds: 600
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      name: jaeger-operator
  strategy:
    rollingUpdate:
      maxSurge: 25%
      maxUnavailable: 25%
    type: RollingUpdate
  template:
    metadata:
      creationTimestamp: null
      labels:
        name: jaeger-operator
    spec:
      containers:
      - args:
        - start
        env:
        - name: WATCH_NAMESPACE
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.namespace
        - name: POD_NAME
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.namespace
        - name: OPERATOR_NAME
          value: jaeger-operator
        image: jaegertracing/jaeger-operator:1.18.0
        imagePullPolicy: Always
        name: jaeger-operator
        ports:
        - containerPort: 8383
          name: metrics
          protocol: TCP
        resources: {}
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
      dnsPolicy: ClusterFirst
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext: {}
      serviceAccount: jaeger-operator
      serviceAccountName: jaeger-operator
      terminationGracePeriodSeconds: 30
status:
  availableReplicas: 1
  conditions:
  - lastTransitionTime: "2020-05-29T08:10:49Z"
    lastUpdateTime: "2020-05-29T08:10:49Z"
    message: ReplicaSet "jaeger-operator-547567dddb" has successfully progressed.
    reason: NewReplicaSetAvailable
    status: "True"
    type: Progressing
  - lastTransitionTime: "2020-06-01T01:16:19Z"
    lastUpdateTime: "2020-06-01T01:16:19Z"
    message: Deployment has minimum availability.
    reason: MinimumReplicasAvailable
    status: "True"
    type: Available
  observedGeneration: 2
  readyReplicas: 1
  replicas: 1
  updatedReplicas: 1

I'm having the same problem with a docker-for-desktop getting started with the all-in-one deployment.

@surlyengineer, could you please share the jaeger-operator logs?
$ kubectl logs -n observability deployment/jaeger-operator

Sure - coming back to this this morning has been weird because we have:
kubectl logs -n observability deployment/jaeger-operator
time="2020-08-11T18:07:14Z" level=info msg=Versions arch=amd64 identity=observability.jaeger-operator jaeger=1.17.1 jaeger-operator=v1.17.1 operator-sdk=v0.15.1 os=linux version=go1.13.3
time="2020-08-11T18:07:15Z" level=info msg="Consider running the operator in a cluster-wide scope for extra features"
time="2020-08-11T18:07:15Z" level=info msg="Auto-detected the platform" platform=kubernetes
time="2020-08-11T18:07:15Z" level=info msg="Automatically adjusted the 'es-provision' flag" es-provision=no
time="2020-08-11T18:07:15Z" level=info msg="Automatically adjusted the 'kafka-provision' flag" kafka-provision=no
time="2020-08-11T18:07:15Z" level=info msg="The service account running this operator has the role 'system:auth-delegator', enabling OAuth Proxy's 'delegate-urls' option"
time="2020-08-11T18:07:17Z" level=info msg="Install prometheus-operator in your cluster to create ServiceMonitor objects" error="no ServiceMonitor registered with the API"

After I first noticed the issue (note the timestamp from two days ago).  The kubectl get jaegers command works just fine but no pods are created in response.  The logs are silent until the next day I start seeing:
time="2020-08-12T11:22:39Z" level=error msg="error getting a list of deployments to analyze in namespace" error="Get https://10.96.0.1:443/apis/apps/v1/namespaces/observability/deployments: http2: server sent GOAWAY and closed the connection; LastStreamID=78745, ErrCode=NO_ERROR, debug=\"\"" namespace=observability
E0812 11:23:17.841840       1 reflector.go:280] pkg/mod/k8s.io/client-go@v0.0.0-20191016111102-bec269661e48/tools/cache/reflector.go:96: Failed to watch *v1.Jaeger: Get https://10.96.0.1:443/apis/jaegertracing.io/v1/namespaces/observability/jaegers?allowWatchBookmarks=true&resourceVersion=9452135&timeoutSeconds=422&watch=true: dial tcp 10.96.0.1:443: i/o timeout
E0812 11:23:18.316640       1 reflector.go:280] pkg/mod/k8s.io/client-go@v0.0.0-20191016111102-bec269661e48/tools/cache/reflector.go:96: Failed to watch *v1.Namespace: Get https://10.96.0.1:443/api/v1/namespaces?allowWatchBookmarks=true&resourceVersion=9452033&timeoutSeconds=329&watch=true: dial tcp 10.96.0.1:443: connect: connection refused
E0812 11:23:18.320099       1 reflector.go:280] pkg/mod/k8s.io/client-go@v0.0.0-20191016111102-bec269661e48/tools/cache/reflector.go:96: Failed to watch *v1.Deployment: Get https://10.96.0.1:443/apis/apps/v1/namespaces/observability/deployments?allowWatchBookmarks=true&resourceVersion=9452090&timeoutSeconds=411&watch=true: dial tcp 10.96.0.1:443: connect: connection refused
time="2020-08-12T11:23:18Z" level=error msg="error getting a list of existing jaeger instances in namespace" error="Get https://10.96.0.1:443/apis/jaegertracing.io/v1/namespaces/observability/jaegers: dial tcp 10.96.0.1:443: connect: connection refused" namespace=observability
time="2020-08-12T11:23:18Z" level=info msg="failed to determine the platform capabilities, auto-detected properties will fallback to their default values." error="Get https://10.96.0.1:443/api?timeout=32s: dial tcp 10.96.0.1:443: connect: connection refused"

Looks like your cluster is out of resources? The operator creates a deployment only, which then causes a replica set to be created, which in turn creates the actual pod.
Could you please check whether you have deployments and replica sets for the expected pods? Like:
$ kubectl get deployments
NAME       READY   UP-TO-DATE   AVAILABLE   AGE
simplest   1/1     1            1           4m

$ kubectl get replicasets
NAME                  DESIRED   CURRENT   READY   AGE
simplest-77b8c6fc95   1         1         1       4m8s

$ kubectl get pods
NAME                        READY   STATUS    RESTARTS   AGE
simplest-77b8c6fc95-22pr6   1/1     Running   0          4m15s

If you see a replica set but not a pod, check the replica's status object for the causes. If you don't even see a deployment, then it's certainly something wrong with the operator.

I don't even see the deployment.
$ kubectl get jaegers
NAME       STATUS   VERSION   STRATEGY   STORAGE   AGE
simplest                                           46h
$ kubectl get deploy -A | grep simplest

Thanks! That does sound odd. Would you please provide the debug logs? In your operator.yaml, add the following flag to the args:
        args: ["start", "--log-level=debug"]

That didn't seem to change the output:
$ kubectl logs -n observability deployment/jaeger-operator -f
time="2020-08-17T13:17:31Z" level=info msg=Versions arch=amd64 identity=observability.jaeger-operator jaeger=1.17.1 jaeger-operator=v1.17.1 operator-sdk=v0.15.1 os=linux version=go1.13.3
time="2020-08-17T13:17:31Z" level=info msg="Consider running the operator in a cluster-wide scope for extra features"
time="2020-08-17T13:17:32Z" level=info msg="Auto-detected the platform" platform=kubernetes
time="2020-08-17T13:17:32Z" level=info msg="Automatically adjusted the 'es-provision' flag" es-provision=no
time="2020-08-17T13:17:32Z" level=info msg="Automatically adjusted the 'kafka-provision' flag" kafka-provision=no
time="2020-08-17T13:17:32Z" level=info msg="The service account running this operator has the role 'system:auth-delegator', enabling OAuth Proxy's 'delegate-urls' option"
time="2020-08-17T13:17:33Z" level=info msg="Install prometheus-operator in your cluster to create ServiceMonitor objects" error="no ServiceMonitor registered with the API"

One point of curiosity - in the logs there we have Consider running the operator in a cluster-wide scope for extra features but I have the cluster roles enabled.  That's a little odd, no?

Huh - Okay.  Made some progress.  The key seemed to be this line in the README:

You probably also want to download and customize the operator.yaml, setting the env var WATCH_NAMESPACE to have an empty value, so that it can watch for instances across all namespaces.

Once I did that, it was able to create the query pods and whatnot, but it's creating them in the default namespace which seems off.

@surlyengineer about not changing the output: you might be affected by #1129 , could you try the master image? Here's what to expect when you run the Jaeger Operator in the observability namespace and created an instance named simplest in the same observability namespace:
$ kubectl logs jaeger-operator-fcb558d65-hshmp
time="2020-08-17T13:31:20Z" level=info msg=Versions arch=amd64 identity=default.jaeger-operator jaeger=1.18.1 jaeger-operator=master operator-sdk=v0.18.2 os=linux version=go1.14.4
I0817 13:31:21.997539       1 request.go:621] Throttling request took 1.039002289s, request: GET:https://172.25.0.1:443/apis/storage.k8s.io/v1beta1?timeout=32s
time="2020-08-17T13:31:39Z" level=info msg="Consider running the operator in a cluster-wide scope for extra features"
I0817 13:31:40.972175       1 request.go:621] Throttling request took 1.047980702s, request: GET:https://172.25.0.1:443/apis/storage.k8s.io/v1?timeout=32s
time="2020-08-17T13:31:42Z" level=info msg="Auto-detected the platform" platform=openshift
time="2020-08-17T13:31:42Z" level=info msg="Auto-detected ingress api" ingress-api=networking
time="2020-08-17T13:31:42Z" level=info msg="Automatically adjusted the 'es-provision' flag" es-provision=no
time="2020-08-17T13:31:42Z" level=info msg="Automatically adjusted the 'kafka-provision' flag" kafka-provision=no
time="2020-08-17T13:31:42Z" level=info msg="The service account running this operator does not have the role 'system:auth-delegator', consider granting it for additional capabilities"
time="2020-08-17T13:31:48Z" level=warning msg="could not create ServiceMonitor object" error="servicemonitors.monitoring.coreos.com \"jaeger-operator-metrics\" already exists"
time="2020-08-17T13:31:48Z" level=info msg="OAuthProxy ImageStream namespace and/or name not defined" name= namespace=
time="2020-08-17T13:31:48Z" level=debug msg="Reconciling Jaeger" execution="2020-08-17 13:31:48.723313894 +0000 UTC" instance=simplest namespace=default
time="2020-08-17T13:31:48Z" level=debug msg="Strategy chosen" instance=simplest namespace=default strategy=allinone
time="2020-08-17T13:31:48Z" level=debug msg="Creating all-in-one deployment" instance=simplest namespace=default
time="2020-08-17T13:31:48Z" level=debug msg="Assembling the UI configmap" instance=simplest namespace=default
time="2020-08-17T13:31:48Z" level=debug msg="Assembling the Sampling configmap" instance=simplest namespace=default
time="2020-08-17T13:31:48Z" level=debug msg="CA: Creating the trustedCABundle configmap" instance=simplest namespace=default
time="2020-08-17T13:31:48Z" level=debug msg="CA: Creating the service CA configmap" instance=simplest namespace=default
time="2020-08-17T13:31:48Z" level=debug msg="Assembling an all-in-one deployment" instance=simplest namespace=default
time="2020-08-17T13:31:48Z" level=debug msg="found a volume mount with the trusted-ca" instance=simplest namespace=default
time="2020-08-17T13:31:48Z" level=debug msg="skipping agent daemonset" instance=simplest namespace=default strategy=
time="2020-08-17T13:31:48Z" level=debug msg="updating service account" account=simplest-ui-proxy instance=simplest namespace=default
time="2020-08-17T13:31:48Z" level=debug msg="updating service account" account=simplest instance=simplest namespace=default
time="2020-08-17T13:31:48Z" level=debug msg="creating config maps" configMap=simplest-service-ca instance=simplest namespace=default
time="2020-08-17T13:31:48Z" level=debug msg="updating config maps" configMap=simplest-ui-configuration instance=simplest namespace=default
time="2020-08-17T13:31:48Z" level=debug msg="updating config maps" configMap=simplest-sampling-configuration instance=simplest namespace=default
time="2020-08-17T13:31:48Z" level=debug msg="updating config maps" configMap=simplest-trusted-ca instance=simplest namespace=default
time="2020-08-17T13:31:48Z" level=debug msg="updating service" instance=simplest namespace=default service=simplest-collector-headless
time="2020-08-17T13:31:48Z" level=debug msg="updating service" instance=simplest namespace=default service=simplest-collector
time="2020-08-17T13:31:48Z" level=debug msg="updating service" instance=simplest namespace=default service=simplest-query
time="2020-08-17T13:31:48Z" level=debug msg="updating service" instance=simplest namespace=default service=simplest-agent
time="2020-08-17T13:31:48Z" level=debug msg="updating deployment" deployment=simplest instance=simplest namespace=default
time="2020-08-17T13:31:48Z" level=debug msg="Deployment has stabilized" desired=1 name=simplest namespace=default ready=1
time="2020-08-17T13:31:48Z" level=debug msg="updating route" instance=simplest namespace=default route=simplest
time="2020-08-17T13:31:48Z" level=debug msg="Reconciling Jaeger completed" execution="2020-08-17 13:31:48.723313894 +0000 UTC" instance=simplest namespace=default

One point of curiosity - in the logs there we have Consider running the operator in a cluster-wide scope for extra features but I have the cluster roles enabled. That's a little odd, no?

Cluster-wide means setting WATCH_NAMESPACE to empty, so that it watches all namespaces in the cluster.

it was able to create the query pods and whatnot, but it's creating them in the default namespace which seems off.

If you are creating the Jaeger CR in the default namespace, then it will create all the pods/deployments in the default namespace. This might explain why you are not seeing any pods: you are creating the CR in a namespace that the operator isn't watching.

That seems off, though, since CR's aren't namespaced (https://kubernetes.io/docs/reference/access-authn-authz/rbac/#clusterrole-example) right?  Possible I'm missing something obvious though.

@surlyengineer about not changing the output: you might be affected by #1129 , could you try the master image? Here's what to expect when you run the Jaeger Operator in the observability namespace and created an instance named simplest in the same observability namespace:

I'll give this a shot this afternoon (US East)

That seems off, though, since CR's aren't namespaced

Not all of them. The one you linked (ClusterRole) certainly is, as it's about creating a role that is valid for the whole cluster. Jaeger instances are indeed namespaced, like Deployment, Service, Pod, and other resources, making it easier to protect and isolate them.

For reference, you may check which custom resources are namespaced and which aren't by looking into the .Spec.Scope field. Here's Jaeger's: https://github.com/jaegertracing/jaeger-operator/blob/f443e78e18d14e8e18d9ce2ed162346cf90583ad/deploy/crds/jaegertracing.io_jaegers_crd.yaml#L35

@jpkrohling I also met a similar issue.. my question is that even I have set spec.strategy = production as below.
apiVersion: jaegertracing.io/v1
kind: Jaeger
metadata:
  name: jaeger-production
  namespace: istio-system
spec:
  strategy: production
  collector:
    options:
      log-level: debug
    replicas: 3
    resources:
      limits:
        cpu: 100m
        memory: 128Mi
    storage:
      type: elasticsearch
      options:
        es:
          server-urls: http://x.x.x.x:9200
          username: xxx
          password: xxx
          index-prefix: jaeger-
  query:
    options:
      log-level: debug
  ingress:
    enabled: false

The operator log is still like strategy=allinone as follows...
time="2020-09-15T10:17:47Z" level=debug msg="Strategy chosen" instance=jaeger-production namespace=istio-system strategy=allinone
time="2020-09-15T10:17:47Z" level=debug msg="Creating all-in-one deployment" instance=jaeger-production namespace=istio-system
time="2020-09-15T10:17:47Z" level=debug msg="Assembling the UI configmap" instance=jaeger-production namespace=istio-system
time="2020-09-15T10:17:47Z" level=debug msg="Assembling the Sampling configmap" instance=jaeger-production namespace=istio-system
time="2020-09-15T10:17:47Z" level=debug msg="Assembling an all-in-one deployment" instance=jaeger-production namespace=istio-system
time="2020-09-15T10:17:47Z" level=debug msg="skipping agent daemonset" instance=jaeger-production namespace=istio-system strategy=
time="2020-09-15T10:17:47Z" level=debug msg="updating service account" account=jaeger-production instance=jaeger-production namespace=istio-system
time="2020-09-15T10:17:47Z" level=debug msg="updating config maps" configMap=jaeger-production-ui-configuration instance=jaeger-production namespace=istio-system
time="2020-09-15T10:17:47Z" level=debug msg="updating config maps" configMap=jaeger-production-sampling-configuration instance=jaeger-production namespace=istio-system
time="2020-09-15T10:17:47Z" level=debug msg="updating service" instance=jaeger-production namespace=istio-system service=jaeger-production-collector
time="2020-09-15T10:17:47Z" level=debug msg="updating service" instance=jaeger-production namespace=istio-system service=jaeger-production-query
time="2020-09-15T10:17:47Z" level=debug msg="updating service" instance=jaeger-production namespace=istio-system service=jaeger-production-agent
time="2020-09-15T10:17:47Z" level=debug msg="updating service" instance=jaeger-production namespace=istio-system service=jaeger-production-collector-headless
time="2020-09-15T10:17:47Z" level=debug msg="updating deployment" deployment=jaeger-production instance=jaeger-production namespace=istio-system
time="2020-09-15T10:17:47Z" level=debug msg="Deployment has stabilized" desired=1 name=jaeger-production namespace=istio-system ready=1
time="2020-09-15T10:17:47Z" level=debug msg="Reconciling Jaeger completed" execution="2020-09-15 10:17:47.391648149 +0000 UTC" instance=jaeger-production namespace=istio-system

And when I get the YAML of Jaeger, Got the same result...
API Version:  jaegertracing.io/v1
Kind:         Jaeger
Metadata:
  Creation Timestamp:  2020-09-15T10:17:43Z
  Generation:          3
  Resource Version:    130744391
  Self Link:           /apis/jaegertracing.io/v1/namespaces/istio-system/jaegers/jaeger-production
  UID:                 ab4e0750-da72-4846-b4ca-7637a20b2b4e
Spec:
  Agent:
    Config:
    Options:
    Resources:
  All In One:
    Config:
    Options:
    Resources:
  Collector:
    Config:
    Options:
      Log - Level:  debug
    Replicas:       3
    Resources:
      Limits:
        Cpu:     100m
        Memory:  128Mi
  Ingester:
    Config:
    Options:
    Resources:
  Ingress:
    Enabled:  false
    Openshift:
    Options:
    Resources:
    Security:  none
  Query:
    Options:
      Log - Level:  debug
    Resources:
  Resources:
  Sampling:
    Options:
  Storage:
    Cassandra Create Schema:
    Dependencies:
      Resources:
      Schedule:  55 23 * * *
    Elasticsearch:
      Node Count:         3
      Redundancy Policy:  SingleRedundancy
      Resources:
        Limits:
          Memory:  16Gi
        Requests:
          Cpu:     1
          Memory:  16Gi
      Storage:
    Es Index Cleaner:
      Number Of Days:  7
      Resources:
      Schedule:  55 23 * * *
    Es Rollover:
      Resources:
      Schedule:  0 0 * * *
    Options:
    Type:    memory
  Strategy:  allinone
  Ui:
    Options:
      Menu:
        Items:
          Label:  Documentation
          URL:    https://www.jaegertracing.io/docs/1.19
        Label:    About
Status:
  Phase:    Running
  Version:  1.19.2
Events:     <none>

My Operator version is 1.19.0, and the Kubernetes version is 1.16.1. I am wondering is there any other configuration that affects the strategy chosen of Jaeger Operator? Any advice would be very helpful. thank you

It looks like your storage node is misaligned. Yours is under .spec.collector.storage, and should be directly under .spec. As the operator can't find the storage node, it assumes you want a default one (all in one).
In any case, the operator seems to have created a Jaeger deployment:
time="2020-09-15T10:17:47Z" level=debug msg="updating deployment" deployment=jaeger-production instance=jaeger-production namespace=istio-system

Do you see pods for this deployment?

It looks like your storage node is misaligned. Yours is under .spec.collector.storage, and should be directly under .spec. As the operator can't find the storage node, it assumes you want a default one (all in one).
In any case, the operator seems to have created a Jaeger deployment:
time="2020-09-15T10:17:47Z" level=debug msg="updating deployment" deployment=jaeger-production instance=jaeger-production namespace=istio-system

Do you see pods for this deployment?

Thanks a lot. It indeed solves the problem, Now i got the production strategy. Yes, I deed see these logs after every time of change the Jaeger YAML, So I thought the configuration is OK. Sorry, my Bad, I should double-check... But is really trick that other field would affect the way how Jaeger is deployed, and the log does not show any error msg.

authors: YonaLugassi jpkrohling kidrocknroll pavolloffay surlyengineer tanjunchen

repo: jaegertracing/jaeger-operator


text:
How to find my k8s service in jaeger-query UI?

Hello,I annotationed my deployment and service with the sidecar of jaeger instance,updated the ingress as well. Where was wrong?I could not see my service in the jaeger-query UI dashboard.
Here are details:
apiVersion: io.jaegertracing/v1alpha1
kind: Jaeger
metadata:
  name: simplest
spec:
  strategy: allInOne
  storage:
    type: elasticsearch
    options:
      es:
        server-urls: http://elasticsearch-client:9200
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: nginx
  name: simplest-query
spec:
  rules:
    - host: jaeger.test.env
      http:
        paths:
          - backend:
              serviceName: simplest-query
              servicePort: 16686
            path: /

the annotation of my deployment and service
annotations:
    inject-jaeger-agent: "simplest"
    sidecar.jaegertracing.io/inject: "simplest"

Thanks for any help!

Is your application being instrumented? Which Jaeger Client are you using (Go, Java, Python, ...)?

@jpkrohling Thanks,I think I got it.
The jaeger in Istio,it seems that jaeger does not need my application be instrumented.So I thought k8s does not need either.
Thank you very much!

I'm closing this issue then, but if you still have questions, feel free to reopen.

@jpkrohling Hello,has something changed?
I found the Jaeger version became v1 instead of v1alpha1,so I used the newest yaml to installing the operator,but my pod was ERROR.
The logs :
kubectl logs -f  jaeger-operator-7b8f94854d-cd6gn -n dev
time="2019-03-08T07:38:17Z" level=info msg=Versions arch=amd64 jaeger-operator=1.10.0 operator-sdk=v0.4.1 os=linux version=go1.11.1
time="2019-03-08T07:38:17Z" level=info msg="Auto-detected the platform" platform=kubernetes
time="2019-03-08T07:38:17Z" level=info msg="Automatically adjusted the 'es-provision' flag" es-provision=false
time="2019-03-08T07:38:17Z" level=fatal msg="no matches for kind \"Jaeger\" in version \"io.jaegertracing/v1alpha1\""

Is the jager-operator incubator ? Where can I find the stable version?

What are the complete steps you executed to install the operator? The version 1.10.0 should still use io.jaegertracing/v1alpha1, not the new (and unreleased) jaegertracing.io/v1.
What you might be missing is the installation of the CRD file:
$ kubectl create -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/v1.10.0/deploy/crds/io_v1alpha1_jaeger_crd.yaml

I follow the README.adoc, the crd file:
kubectl create -f https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/crds/jaegertracing_v1_jaeger_crd.yaml

@jpkrohling  Thanks,I'll try it again.

Right, that's the new CRD. The readme already reflects the changes in master.

Thank you very much!


text:
Jaeger collector crashed

Describe the bug
Crash of Jaeger Collector
To Reproduce
Unfortunately, it happens sometimes with 1.17.0 and is more freqent with 1.18.0 so I stay in 1.17.0
Screenshots
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x402540]

goroutine 131 [running]:
strings.Count(0x0, 0xc000150e70, 0x1454335, 0x1, 0x10)
        strings/strings.go:84 +0xf2
strings.Replace(0x0, 0xc000150e70, 0x1454335, 0x1, 0x1454342, 0x1, 0xffffffffffffffff, 0x7fff3666f6c5, 0x9)
        strings/strings.go:934 +0x9b
github.com/jaegertracing/jaeger/plugin/storage/es/spanstore/dbmodel.FromDomain.convertKeyValuesString(0x13ec301, 0xc000320cc0, 0x1454342, 0x1, 0xc0007a8800, 0x14, 0x22, 0xc000f001c0, 0x10, 0x0, ...)
        github.com/jaegertracing/jaeger/plugin/storage/es/spanstore/dbmodel/from_domain.go:96 +0x1a4
github.com/jaegertracing/jaeger/plugin/storage/es/spanstore/dbmodel.FromDomain.convertProcess(...)
        github.com/jaegertracing/jaeger/plugin/storage/es/spanstore/dbmodel/from_domain.go:123
github.com/jaegertracing/jaeger/plugin/storage/es/spanstore/dbmodel.FromDomain.convertSpanEmbedProcess(0x70e3601, 0xc000320cc0, 0x1454342, 0x1, 0xc000d2b0e0, 0xc000572680)
        github.com/jaegertracing/jaeger/plugin/storage/es/spanstore/dbmodel/from_domain.go:64 +0x145
github.com/jaegertracing/jaeger/plugin/storage/es/spanstore/dbmodel.FromDomain.FromDomainEmbedProcess(...)
        github.com/jaegertracing/jaeger/plugin/storage/es/spanstore/dbmodel/from_domain.go:43
github.com/jaegertracing/jaeger/plugin/storage/es/spanstore.(*SpanWriter).WriteSpan(0xc000430cb0, 0xc000d2b0e0, 0x0, 0x0)
        github.com/jaegertracing/jaeger/plugin/storage/es/spanstore/writer.go:137 +0xae
github.com/jaegertracing/jaeger/storage/spanstore.(*CompositeWriter).WriteSpan(0xc0004a0a00, 0xc000d2b0e0, 0x21049e0, 0x0)
        github.com/jaegertracing/jaeger/storage/spanstore/composite.go:39 +0x9c
github.com/jaegertracing/jaeger/cmd/collector/app.(*spanProcessor).saveSpan(0xc00050c000, 0xc000d2b0e0)
        github.com/jaegertracing/jaeger/cmd/collector/app/span_processor.go:143 +0x9a
github.com/jaegertracing/jaeger/cmd/collector/app.ChainedProcessSpan.func1(0xc000d2b0e0)
        github.com/jaegertracing/jaeger/cmd/collector/app/model_consumer.go:35 +0x4d
github.com/jaegertracing/jaeger/cmd/collector/app.(*spanProcessor).processItemFromQueue(0xc00050c000, 0xc000578060)
        github.com/jaegertracing/jaeger/cmd/collector/app/span_processor.go:174 +0x53
github.com/jaegertracing/jaeger/cmd/collector/app.NewSpanProcessor.func1(0x118dac0, 0xc000578060)
        github.com/jaegertracing/jaeger/cmd/collector/app/span_processor.go:75 +0x45
github.com/jaegertracing/jaeger/pkg/queue.(*BoundedQueue).StartConsumers.func1(0xc0004b01a0, 0xc000493860)
        github.com/jaegertracing/jaeger/pkg/queue/bounded_queue.go:77 +0xc3
created by github.com/jaegertracing/jaeger/pkg/queue.(*BoundedQueue).StartConsumers
        github.com/jaegertracing/jaeger/pkg/queue/bounded_queue.go:68 +0xc0

Version (please complete the following information):

OS: Centos 7
Jaeger version: 1.17.0 ({"gitCommit":"00985cadeb757886ac158f10e4b8229067797b65","GitVersion":"v1.17.0","BuildDate":"2020-02-24T18:55:12Z"})
Deployment: baremetal

What troubleshooting steps did you try?
I look at the code : https://github.com/jaegertracing/jaeger/blob/v1.17.0/plugin/storage/es/spanstore/dbmodel/from_domain.go#L96
According to the 0x00 address, we can suppose it is the kv.Key that is nil but I don't understand how it is possible as the Key field in a KeyValue object is a string and so is normally initialized to "" and not nil .
Additional context
Starting script
export ES_USERNAME=
export ES_PASSWORD=
export SPAN_STORAGE_TYPE=elasticsearch,kafka
Agents are in tchannel : --reporter.tchannel.host-port=localhost:14267
Collector have the following optinos :
        --es.server-urls=xxx\
        --es.num-replicas=1\
        --es.tags-as-fields.all\
        --kafka.producer.brokers xxx\
        --kafka.producer.encoding json\
        --kafka.producer.topic jaeger-spans\
        --collector.tags "collector=xxx,region=yyy,az=zzz"

@Etienne-Carriere Seems to imply a problem with the data being reported - what client/version are you using?
Even so, would be worth adding a guard (and possibly some debug logging) to prevent it from causing a panic. Would you be interested in submitting a PR?

I didn't reproduced it and now in 1.26 I don't have any issues. I close the ticket.

authors: Etienne-Carriere objectiser

repo: jaegertracing/jaeger


text:
[Bug Report] Title Here

Bug Description
Bot automatically disconnects from voice chat after trying to play a song.
The bot connects, but then disconnects immediately after.
Steps to Reproduce

Used play command
bot connects
bot disconnects

Expected Result
Expected bot to stay on and play thes ong
Debug Output
[04:08:40] [INFO] [JMusicBot]: Loaded config from C:\Users\Administrator\Documents\music\config.txt
[04:08:41] [INFO] [JDA]: Login Successful!
[04:08:41] [INFO] [WebSocketClient]: Connected to WebSocket
[04:08:41] [INFO] [JMusicBot]: JMusicBot
[04:08:41] [INFO] [JDA]: Finished Loading!
[08:04:26] [ERROR] [SignatureCipherManager]: Problematic YouTube player script /s/player/2f238d39/player_ias.vflset/en_US/base.js detected (issue detected with script: no n function match). Dumped to C:\Users\ADMINI~1\AppData\Local\Temp\2\lavaplayer-yt-player-script15148451604831530413.js
[08:04:27] [ERROR] [LocalAudioTrackExecutor]: Error in playback of gndkFhYh5Mo
com.sedmelluq.discord.lavaplayer.tools.FriendlyException: Something broke when playing the track.
at com.sedmelluq.discord.lavaplayer.tools.ExceptionTools.wrapUnfriendlyExceptions(ExceptionTools.java:45)
at com.sedmelluq.discord.lavaplayer.track.playback.LocalAudioTrackExecutor.execute(LocalAudioTrackExecutor.java:121)
at com.sedmelluq.discord.lavaplayer.player.DefaultAudioPlayerManager.lambda$executeTrack$2(DefaultAudioPlayerManager.java:339)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1583)
Caused by: java.lang.RuntimeException: Not success status code: 403
at com.sedmelluq.discord.lavaplayer.tools.io.PersistentHttpStream.validateStatusCode(PersistentHttpStream.java:88)
at com.sedmelluq.discord.lavaplayer.tools.io.PersistentHttpStream.attemptConnect(PersistentHttpStream.java:124)
at com.sedmelluq.discord.lavaplayer.tools.io.PersistentHttpStream.connect(PersistentHttpStream.java:106)
at com.sedmelluq.discord.lavaplayer.tools.io.PersistentHttpStream.internalRead(PersistentHttpStream.java:158)
at com.sedmelluq.discord.lavaplayer.tools.io.PersistentHttpStream.read(PersistentHttpStream.java:174)
at java.base/java.io.DataInputStream.readUnsignedByte(DataInputStream.java:295)
at java.base/java.io.DataInputStream.readByte(DataInputStream.java:275)
at com.sedmelluq.discord.lavaplayer.container.matroska.format.MatroskaEbmlReader.readEbmlInteger(MatroskaEbmlReader.java:39)
at com.sedmelluq.discord.lavaplayer.container.matroska.format.MatroskaFileReader.readNextElement(MatroskaFileReader.java:47)
at com.sedmelluq.discord.lavaplayer.container.matroska.MatroskaStreamingFile.readFile(MatroskaStreamingFile.java:94)
at com.sedmelluq.discord.lavaplayer.container.matroska.MatroskaAudioTrack.loadMatroskaFile(MatroskaAudioTrack.java:52)
at com.sedmelluq.discord.lavaplayer.container.matroska.MatroskaAudioTrack.process(MatroskaAudioTrack.java:35)
at com.sedmelluq.discord.lavaplayer.track.DelegatedAudioTrack.processDelegate(DelegatedAudioTrack.java:25)
at dev.lavalink.youtube.track.YoutubeAudioTrack.processStatic(YoutubeAudioTrack.java:148)
at dev.lavalink.youtube.track.YoutubeAudioTrack.processWithClient(YoutubeAudioTrack.java:116)
at dev.lavalink.youtube.track.YoutubeAudioTrack.process(YoutubeAudioTrack.java:71)
at com.sedmelluq.discord.lavaplayer.track.playback.LocalAudioTrackExecutor.execute(LocalAudioTrackExecutor.java:109)
... 4 common frames omitted
[08:04:27] [ERROR] [AudioHandler]: Track gndkFhYh5Mo has failed to play
com.sedmelluq.discord.lavaplayer.tools.FriendlyException: Something broke when playing the track.
at com.sedmelluq.discord.lavaplayer.tools.ExceptionTools.wrapUnfriendlyExceptions(ExceptionTools.java:45)
at com.sedmelluq.discord.lavaplayer.track.playback.LocalAudioTrackExecutor.execute(LocalAudioTrackExecutor.java:121)
at com.sedmelluq.discord.lavaplayer.player.DefaultAudioPlayerManager.lambda$executeTrack$2(DefaultAudioPlayerManager.java:339)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1583)
Caused by: java.lang.RuntimeException: Not success status code: 403
at com.sedmelluq.discord.lavaplayer.tools.io.PersistentHttpStream.validateStatusCode(PersistentHttpStream.java:88)
at com.sedmelluq.discord.lavaplayer.tools.io.PersistentHttpStream.attemptConnect(PersistentHttpStream.java:124)
at com.sedmelluq.discord.lavaplayer.tools.io.PersistentHttpStream.connect(PersistentHttpStream.java:106)
at com.sedmelluq.discord.lavaplayer.tools.io.PersistentHttpStream.internalRead(PersistentHttpStream.java:158)
at com.sedmelluq.discord.lavaplayer.tools.io.PersistentHttpStream.read(PersistentHttpStream.java:174)
at java.base/java.io.DataInputStream.readUnsignedByte(DataInputStream.java:295)
at java.base/java.io.DataInputStream.readByte(DataInputStream.java:275)
at com.sedmelluq.discord.lavaplayer.container.matroska.format.MatroskaEbmlReader.readEbmlInteger(MatroskaEbmlReader.java:39)
at com.sedmelluq.discord.lavaplayer.container.matroska.format.MatroskaFileReader.readNextElement(MatroskaFileReader.java:47)
at com.sedmelluq.discord.lavaplayer.container.matroska.MatroskaStreamingFile.readFile(MatroskaStreamingFile.java:94)
at com.sedmelluq.discord.lavaplayer.container.matroska.MatroskaAudioTrack.loadMatroskaFile(MatroskaAudioTrack.java:52)
at com.sedmelluq.discord.lavaplayer.container.matroska.MatroskaAudioTrack.process(MatroskaAudioTrack.java:35)
at com.sedmelluq.discord.lavaplayer.track.DelegatedAudioTrack.processDelegate(DelegatedAudioTrack.java:25)
at dev.lavalink.youtube.track.YoutubeAudioTrack.processStatic(YoutubeAudioTrack.java:148)
at dev.lavalink.youtube.track.YoutubeAudioTrack.processWithClient(YoutubeAudioTrack.java:116)
at dev.lavalink.youtube.track.YoutubeAudioTrack.process(YoutubeAudioTrack.java:71)
at com.sedmelluq.discord.lavaplayer.track.playback.LocalAudioTrackExecutor.execute(LocalAudioTrackExecutor.java:109)
... 4 common frames omitted
[08:06:49] [ERROR] [LocalAudioTrackExecutor]: Error in playback of ENXvZ9YRjbo
com.sedmelluq.discord.lavaplayer.tools.FriendlyException: Something broke when playing the track.
at com.sedmelluq.discord.lavaplayer.tools.ExceptionTools.wrapUnfriendlyExceptions(ExceptionTools.java:45)
at com.sedmelluq.discord.lavaplayer.track.playback.LocalAudioTrackExecutor.execute(LocalAudioTrackExecutor.java:121)
at com.sedmelluq.discord.lavaplayer.player.DefaultAudioPlayerManager.lambda$executeTrack$2(DefaultAudioPlayerManager.java:339)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1583)
Caused by: java.lang.RuntimeException: Not success status code: 403
at com.sedmelluq.discord.lavaplayer.tools.io.PersistentHttpStream.validateStatusCode(PersistentHttpStream.java:88)
at com.sedmelluq.discord.lavaplayer.tools.io.PersistentHttpStream.attemptConnect(PersistentHttpStream.java:124)
at com.sedmelluq.discord.lavaplayer.tools.io.PersistentHttpStream.connect(PersistentHttpStream.java:106)
at com.sedmelluq.discord.lavaplayer.tools.io.PersistentHttpStream.internalRead(PersistentHttpStream.java:158)
at com.sedmelluq.discord.lavaplayer.tools.io.PersistentHttpStream.read(PersistentHttpStream.java:174)
at java.base/java.io.DataInputStream.readUnsignedByte(DataInputStream.java:295)
at java.base/java.io.DataInputStream.readByte(DataInputStream.java:275)
at com.sedmelluq.discord.lavaplayer.container.matroska.format.MatroskaEbmlReader.readEbmlInteger(MatroskaEbmlReader.java:39)
at com.sedmelluq.discord.lavaplayer.container.matroska.format.MatroskaFileReader.readNextElement(MatroskaFileReader.java:47)
at com.sedmelluq.discord.lavaplayer.container.matroska.MatroskaStreamingFile.readFile(MatroskaStreamingFile.java:94)
at com.sedmelluq.discord.lavaplayer.container.matroska.MatroskaAudioTrack.loadMatroskaFile(MatroskaAudioTrack.java:52)
at com.sedmelluq.discord.lavaplayer.container.matroska.MatroskaAudioTrack.process(MatroskaAudioTrack.java:35)
at com.sedmelluq.discord.lavaplayer.track.DelegatedAudioTrack.processDelegate(DelegatedAudioTrack.java:25)
at dev.lavalink.youtube.track.YoutubeAudioTrack.processStatic(YoutubeAudioTrack.java:148)
at dev.lavalink.youtube.track.YoutubeAudioTrack.processWithClient(YoutubeAudioTrack.java:116)
at dev.lavalink.youtube.track.YoutubeAudioTrack.process(YoutubeAudioTrack.java:71)
at com.sedmelluq.discord.lavaplayer.track.playback.LocalAudioTrackExecutor.execute(LocalAudioTrackExecutor.java:109)
... 4 common frames omitted
[08:06:49] [ERROR] [AudioHandler]: Track ENXvZ9YRjbo has failed to play
com.sedmelluq.discord.lavaplayer.tools.FriendlyException: Something broke when playing the track.
at com.sedmelluq.discord.lavaplayer.tools.ExceptionTools.wrapUnfriendlyExceptions(ExceptionTools.java:45)
at com.sedmelluq.discord.lavaplayer.track.playback.LocalAudioTrackExecutor.execute(LocalAudioTrackExecutor.java:121)
at com.sedmelluq.discord.lavaplayer.player.DefaultAudioPlayerManager.lambda$executeTrack$2(DefaultAudioPlayerManager.java:339)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1583)
Caused by: java.lang.RuntimeException: Not success status code: 403
at com.sedmelluq.discord.lavaplayer.tools.io.PersistentHttpStream.validateStatusCode(PersistentHttpStream.java:88)
at com.sedmelluq.discord.lavaplayer.tools.io.PersistentHttpStream.attemptConnect(PersistentHttpStream.java:124)
at com.sedmelluq.discord.lavaplayer.tools.io.PersistentHttpStream.connect(PersistentHttpStream.java:106)
at com.sedmelluq.discord.lavaplayer.tools.io.PersistentHttpStream.internalRead(PersistentHttpStream.java:158)
at com.sedmelluq.discord.lavaplayer.tools.io.PersistentHttpStream.read(PersistentHttpStream.java:174)
at java.base/java.io.DataInputStream.readUnsignedByte(DataInputStream.java:295)
at java.base/java.io.DataInputStream.readByte(DataInputStream.java:275)
at com.sedmelluq.discord.lavaplayer.container.matroska.format.MatroskaEbmlReader.readEbmlInteger(MatroskaEbmlReader.java:39)
at com.sedmelluq.discord.lavaplayer.container.matroska.format.MatroskaFileReader.readNextElement(MatroskaFileReader.java:47)
at com.sedmelluq.discord.lavaplayer.container.matroska.MatroskaStreamingFile.readFile(MatroskaStreamingFile.java:94)
at com.sedmelluq.discord.lavaplayer.container.matroska.MatroskaAudioTrack.loadMatroskaFile(MatroskaAudioTrack.java:52)
at com.sedmelluq.discord.lavaplayer.container.matroska.MatroskaAudioTrack.process(MatroskaAudioTrack.java:35)
at com.sedmelluq.discord.lavaplayer.track.DelegatedAudioTrack.processDelegate(DelegatedAudioTrack.java:25)
at dev.lavalink.youtube.track.YoutubeAudioTrack.processStatic(YoutubeAudioTrack.java:148)
at dev.lavalink.youtube.track.YoutubeAudioTrack.processWithClient(YoutubeAudioTrack.java:116)
at dev.lavalink.youtube.track.YoutubeAudioTrack.process(YoutubeAudioTrack.java:71)
at com.sedmelluq.discord.lavaplayer.track.playback.LocalAudioTrackExecutor.execute(LocalAudioTrackExecutor.java:109)
... 4 common frames omitted
Additional Info
No response
Checklist

[X] I have looked for information about this within the documentation
[X] I have searched for similar issues on the issues page
[X] I am using an official release from the releases page

JMusicBot Version
0.4.3

I also have this issue. Logs say the same thing

i have same problem

Duplicate of #1682

authors: MichailiK bozoboo teksek

repo: jagrosh/MusicBot