Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

context is not defined - showPaths issue

See original GitHub issue

Describe the bug I am testing the v 1.26.0 release and configured Telegram notifications and would like some clarification on the chatIds: and default: options in the configuration.

Provide an example

- file: reportTelegram
channels: 
- hijack
- newprefix
- visibility
- path
- misconfiguration
- rpki
params:
showPaths: 5 # Amount of AS_PATHs to report in the alert
botUrl: https://api.telegram.org/bot12345678:XXXXXXXXXXXX/sendMessage         <- Bot ID and API token. 
Validated via _getUpdates_ endpoint                                                                                                                                      
chatIds: 
default: xxxxx <- ID of the group chat that the bot and the users are in.
Bot can see messages posted there via the /getUpdates endpoint

Expected behavior I would expect that events are being sent to the chat ID of the default user group. In prefixes.yml I do have the monitored ASN allocated to the “default” group.

options:
  monitorASns:
    '212996':
      group: default

E-mail alerts work OK.

I have chatIds blank because I just want it to send to the default group

Are you using the binary or the source code? The binary on Ubuntu 20.04 as a systemd service.

Your information Michael Felden, AS212996

Issue Analytics

State:
Created 3 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

massimocandelacommented, Jul 23, 2020

I found where the issue is for the latest message. I’m patching it now, thanks for reporting. I will probably issue a minor release.

In the meanwhile, disable showPaths by setting it to 0. Thanks again for reporting.

0reactions

massimocandelacommented, Jul 23, 2020

Released patch in v1.26.1. I created tests to cover the issue. We don’t use the showPaths feature so I didn’t notice it before. Sorry for the inconvenience.

Top Results From Across the Web

context is not defined JavaScript - jquery - Stack Overflow

It means that the variable context is undefined: is it the HTMLtemplate(context) function defined as well? Otherwise it should be EmployeeView.template in that ......

ReferenceError: context is not defined · Issue #111 - GitHub

I am trying to use the checkPropertyExists method and I am getting an error about the context not being defined.

Use Context Filters - Tableau Help

However, you can set one or more categorical filters as context filters for the view. You can think of a context filter as...

Change log for Multi Commander

FIXED - Changing Hotkey was not saved if change was done from the User Defined Command dialog. FIXED - Progress dialog will no...

An Easy Way to Create Complex Animations in MotionLayout

motion:touchRegionId — defines the view that needs to be dragged to progress the animation. If it's not defined, a user might swipe anywhere...