Raspberry pi cannot init server

Hi,
I have followed the instructions to install Kivy on raspbery pi. Additionally, I installed xclip and xsel. However I cannot get it work with the following error:
`
pi@raspberrypi ~/pipivo/gui $ python main.py
[INFO   ] [Logger      ] Record log in /home/pi/.kivy/logs/kivy_16-03-01_17.txt
[INFO   ] [Kivy        ] v1.9.2-dev0
[INFO   ] [Python      ] v2.7.9 (default, Mar  8 2015, 00:52:26)
[GCC 4.9.2]
[INFO   ] [Factory     ] 182 symbols loaded
[INFO   ] [Image       ] Providers: img_tex, img_dds, img_gif, img_sdl2, img_pil (img_ffpyplayer ignored)
[INFO   ] [Text        ] Provider: sdl2
[INFO   ] [Window      ] Provider: egl_rpi
[INFO   ] [GL          ] OpenGL version <OpenGL ES 2.0>
[INFO   ] [GL          ] OpenGL vendor
[INFO   ] [GL          ] OpenGL renderer
[INFO   ] [GL          ] OpenGL parsed version: 2, 0
[INFO   ] [GL          ] Shading version <OpenGL ES GLSL ES 1.00>
[INFO   ] [GL          ] Texture max size <2048>
[INFO   ] [GL          ] Texture max units <8>
[INFO   ] [Shader      ] fragment shader:
[INFO   ] [Shader      ] vertex shader:
[INFO   ] [Window      ] virtual keyboard not allowed, single mode, not docked
(process:881): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
(main.py:881): Gtk-CRITICAL **: gtk_clipboard_get_for_display: assertion 'display != NULL' failed
[INFO   ] [Clipboard   ] Provider: gtk3(['clipboard_dbusklipper'] ignored)
xclip version 0.12
Copyright (C) 2001-2008 Kim Saunders et al.
Distributed under the terms of the GNU GPL
`
Do you have any idea what is this?
Thanks,
Rafal

I believe the xclip package requires the X server to be running...
I have been using Kivy on Raspberry Pi with this error with few problems. It seems xclip and xsel are not critical to Kivy operation, unless you are using the text box widgets (and then you don't need xclip unless you use cut/paste operations).

Every clipboard implementation we have for Linux requires X11. I suppose we could make a Kivy-only clipboard, it just wouldn't be quite as useful as it won't share that clipboard data with other apps - though that probably isn't much of an issue on RPi. I wouldn't count on it happening, as it's a rare use case with little benefit.

Thanks for comments,
I reinstalled everything and the init error seems to be caused by upgrade in RPi. Now, however, the simple app (just label) is running without errors but there is nothing displayed only console. The log is:
[INFO              ] Logger: Record log in /home/pi/.kivy/logs/kivy_16-03-02_6.txt
[INFO              ] Kivy: v1.9.2-dev0
[INFO              ] Python: v2.7.9 (default, Mar  8 2015, 00:52:26)
[GCC 4.9.2]
[INFO              ] Factory: 182 symbols loaded
[DEBUG             ] Cache: register <kv.lang> with limit=None, timeout=None
[DEBUG             ] Cache: register <kv.image> with limit=None, timeout=60
[DEBUG             ] Cache: register <kv.atlas> with limit=None, timeout=None
[INFO              ] Image: Providers: img_tex, img_dds, img_gif, img_pygame, img_pil (img_ffpyplayer ignored)
[DEBUG             ] Cache: register <kv.texture> with limit=1000, timeout=60
[DEBUG             ] Cache: register <kv.shader> with limit=1000, timeout=3600
[INFO              ] Text: Provider: pygame
[DEBUG             ] App: Loading kv <./my.kv>
[DEBUG             ] App: kv <./my.kv> not found
[INFO              ] Window: Provider: egl_rpi
[DEBUG             ] Window: Actual display size: 720x480
[INFO              ] GL: OpenGL version <OpenGL ES 2.0>
[INFO              ] GL: OpenGL vendor
[INFO              ] GL: OpenGL renderer
[INFO              ] GL: OpenGL parsed version: 2, 0
[INFO              ] GL: Shading version <OpenGL ES GLSL ES 1.00>
[INFO              ] GL: Texture max size <2048>
[INFO              ] GL: Texture max units <8>
[INFO              ] Shader: fragment shader:
[DEBUG             ] Shader: Fragment compiled successfully
[INFO              ] Shader: vertex shader:
[DEBUG             ] Shader: Vertex compiled successfully
[DEBUG             ] ImagePygame: Load </usr/local/lib/python2.7/dist-packages/kivy/data/glsl/default.png>
[INFO              ] Window: virtual keyboard not allowed, single mode, not docked
[DEBUG             ] Resource: add </usr/share/fonts/truetype> in path list
[DEBUG             ] Resource: add </usr/share/fonts/truetype/dejavu> in path list
[DEBUG             ] Resource: add </usr/share/fonts/truetype/roboto> in path list
[DEBUG             ] Resource: add </usr/share/fonts/truetype/openoffice> in path list
[DEBUG             ] Resource: add </usr/share/fonts/truetype/droid> in path list
[DEBUG             ] Resource: add </usr/share/fonts/truetype/freefont> in path list
[DEBUG             ] Resource: add </usr/share/fonts/truetype/gentium-basic> in path list
[DEBUG             ] Resource: add </usr/local/share/fonts> in path list
[DEBUG             ] Resource: add </usr/local/lib/python2.7/dist-packages/kivy/data/fonts> in path list
[INFO              ] OSC: using  for socket
[DEBUG             ] Base: Create provider from mouse
[DEBUG             ] Base: Create provider from probesysfs,provider=mtdev
[DEBUG             ] ProbeSysfs: using probesysfs!
[DEBUG             ] ProbeSysfs: found device: Logitech USB Receiver at /dev/input/event0
[INFO              ] ProbeSysfs: device match: /dev/input/event0
[INFO              ] MTD: Read event from </dev/input/event0>
[DEBUG             ] ProbeSysfs: found device: Logitech USB Receiver at /dev/input/event1
[INFO              ] ProbeSysfs: device match: /dev/input/event1
[INFO              ] MTD: Read event from </dev/input/event1>
[DEBUG             ] ProbeSysfs: found device: stmpe-ts at /dev/input/event2
[INFO              ] ProbeSysfs: device match: /dev/input/event2
[INFO              ] MTD: Read event from </dev/input/event2>
[DEBUG             ] Base: Create provider from probesysfs,provider=hidinput
[DEBUG             ] ProbeSysfs: using probesysfs!
[DEBUG             ] ProbeSysfs: found device: Logitech USB Receiver at /dev/input/event0
[INFO              ] ProbeSysfs: device match: /dev/input/event0
[INFO              ] HIDInput: Read event from </dev/input/event0>
[DEBUG             ] ProbeSysfs: found device: Logitech USB Receiver at /dev/input/event1
[INFO              ] ProbeSysfs: device match: /dev/input/event1
[INFO              ] HIDInput: Read event from </dev/input/event1>
[DEBUG             ] ProbeSysfs: found device: stmpe-ts at /dev/input/event2
[INFO              ] ProbeSysfs: device match: /dev/input/event2
[INFO              ] HIDInput: Read event from </dev/input/event2>
[INFO              ] Base: Start application main loop
[INFO              ] MTD: </dev/input/event0> range position X is 0 - 0
[INFO              ] MTD: </dev/input/event0> range position Y is 0 - 0
[INFO              ] MTD: </dev/input/event0> range touch major is 0 - 0
[INFO              ] MTD: </dev/input/event0> range touch minor is 0 - 0
[INFO              ] MTD: </dev/input/event0> range pressure is 0 - 255
[INFO              ] MTD: </dev/input/event1> range position X is 0 - 0
[INFO              ] MTD: </dev/input/event1> range position Y is 0 - 0
[INFO              ] MTD: </dev/input/event1> range touch major is 0 - 0
[INFO              ] MTD: </dev/input/event2> range position X is 0 - 4095
[INFO              ] MTD: </dev/input/event2> range position Y is 0 - 4095
[INFO              ] MTD: </dev/input/event2> range touch major is 0 - 0
[INFO              ] MTD: </dev/input/event0> axes invertion: X is 0, Y is 0
[INFO              ] MTD: </dev/input/event0> rotation set to 0
[INFO              ] MTD: </dev/input/event1> range touch minor is 0 - 0
[INFO              ] MTD: </dev/input/event1> range pressure is 0 - 255
[INFO              ] MTD: </dev/input/event2> range touch minor is 0 - 0
[INFO              ] MTD: </dev/input/event2> range pressure is 0 - 255
[INFO              ] HIDMotionEvent: using
[INFO              ] MTD: </dev/input/event1> axes invertion: X is 0, Y is 0
[INFO              ] MTD: </dev/input/event1> rotation set to 0
[INFO              ] HIDMotionEvent: using
[INFO              ] MTD: </dev/input/event2> axes invertion: X is 0, Y is 0
[INFO              ] MTD: </dev/input/event2> rotation set to 0
[INFO              ] GL: NPOT texture support is available
[INFO              ] HIDMotionEvent: using
[INFO              ] HIDMotionEvent:  range ABS X position is 0 - 4095
[INFO              ] HIDMotionEvent:  range ABS Y position is 0 - 4095
[INFO              ] HIDMotionEvent:  range ABS pressure is 0 - 255
My setup is RPi + 2.8 TFT. I tried to start kivy from gui, from ssh and from command line mode including sudo. This is my configuration file:
[kivy]
keyboard_repeat_delay = 300
keyboard_repeat_rate = 30
log_dir = logs
log_enable = 1
log_level = debug
log_name = kivy_%y-%m-%d_%_.txt
window_icon =
keyboard_mode =
keyboard_layout = qwerty
desktop = 1
exit_on_escape = 1
pause_on_minimize = 0
config_version = 14
[graphics]
display = 1
fullscreen = 1
height = 240
left = 0
maxfps = 60
multisamples = 2
position = auto
rotation = 0
show_cursor = 1
top = 0
width = 320
resizable = 1
borderless = 1
window_state = visible
minimum_width = 0
minimum_height = 0
[input]
mouse = mouse
mtdev_%(name)s = probesysfs,provider=mtdev
hid_%(name)s = probesysfs,provider=hidinput
[postproc]
double_tap_distance = 20
double_tap_time = 250
ignore = []
jitter_distance = 0
jitter_ignore_devices = mouse,mactouch,
retain_distance = 50
retain_time = 0
triple_tap_distance = 20
triple_tap_time = 375
[widgets]
scroll_timeout = 250
scroll_distance = 20
scroll_friction = 1.
scroll_stoptime = 300
scroll_moves = 5
[modules]
I have no clue why nothing is displayed.

The Raspberry Pi automatically outputs the screen to the HDMI port. The
Kivy docs suggest this output can be redirected, but I've not been able to
make that work.
I've resorted to using a program called fbcp to copy the display from fb0
to fb1.I just start and run it in the background.
On Wed, Mar 2, 2016 at 12:27 AM, guma44<EMAIL_ADDRESS>wrote:

Thanks for comments,
I reinstalled everything and the init error seems to be caused by upgrade
in RPi. Now, however, the simple app (just label) is running without errors
but there is nothing displayed only console. The log is:
[INFO ] Logger: Record log in /home/pi/.kivy/logs/kivy_16-03-02_6.txt
[INFO ] Kivy: v1.9.2-dev0
[INFO ] Python: v2.7.9 (default, Mar 8 2015, 00:52:26)
[GCC 4.9.2]
[INFO ] Factory: 182 symbols loaded
[DEBUG ] Cache: register with limit=None, timeout=None
[DEBUG ] Cache: register with limit=None, timeout=60
[DEBUG ] Cache: register with limit=None, timeout=None
[INFO ] Image: Providers: img_tex, img_dds, img_gif, img_pygame, img_pil
(img_ffpyplayer ignored)
[DEBUG ] Cache: register with limit=1000, timeout=60
[DEBUG ] Cache: register with limit=1000, timeout=3600
[INFO ] Text: Provider: pygame
[DEBUG ] App: Loading kv <./my.kv>
[DEBUG ] App: kv <./my.kv> not found
[INFO ] Window: Provider: egl_rpi
[DEBUG ] Window: Actual display size: 720x480
[INFO ] GL: OpenGL version
[INFO ] GL: OpenGL vendor
[INFO ] GL: OpenGL renderer
[INFO ] GL: OpenGL parsed version: 2, 0
[INFO ] GL: Shading version
[INFO ] GL: Texture max size <2048>
[INFO ] GL: Texture max units <8>
[INFO ] Shader: fragment shader:
[DEBUG ] Shader: Fragment compiled successfully
[INFO ] Shader: vertex shader:
[DEBUG ] Shader: Vertex compiled successfully
[DEBUG ] ImagePygame: Load
[INFO ] Window: virtual keyboard not allowed, single mode, not docked
[DEBUG ] Resource: add in path list
[DEBUG ] Resource: add in path list
[DEBUG ] Resource: add in path list
[DEBUG ] Resource: add in path list
[DEBUG ] Resource: add in path list
[DEBUG ] Resource: add in path list
[DEBUG ] Resource: add in path list
[DEBUG ] Resource: add in path list
[DEBUG ] Resource: add in path list
[INFO ] OSC: using for socket
[DEBUG ] Base: Create provider from mouse
[DEBUG ] Base: Create provider from probesysfs,provider=mtdev
[DEBUG ] ProbeSysfs: using probesysfs!
[DEBUG ] ProbeSysfs: found device: Logitech USB Receiver at
/dev/input/event0
[INFO ] ProbeSysfs: device match: /dev/input/event0
[INFO ] MTD: Read event from
[DEBUG ] ProbeSysfs: found device: Logitech USB Receiver at
/dev/input/event1
[INFO ] ProbeSysfs: device match: /dev/input/event1
[INFO ] MTD: Read event from
[DEBUG ] ProbeSysfs: found device: stmpe-ts at /dev/input/event2
[INFO ] ProbeSysfs: device match: /dev/input/event2
[INFO ] MTD: Read event from
[DEBUG ] Base: Create provider from probesysfs,provider=hidinput
[DEBUG ] ProbeSysfs: using probesysfs!
[DEBUG ] ProbeSysfs: found device: Logitech USB Receiver at
/dev/input/event0
[INFO ] ProbeSysfs: device match: /dev/input/event0
[INFO ] HIDInput: Read event from
[DEBUG ] ProbeSysfs: found device: Logitech USB Receiver at
/dev/input/event1
[INFO ] ProbeSysfs: device match: /dev/input/event1
[INFO ] HIDInput: Read event from
[DEBUG ] ProbeSysfs: found device: stmpe-ts at /dev/input/event2
[INFO ] ProbeSysfs: device match: /dev/input/event2
[INFO ] HIDInput: Read event from
[INFO ] Base: Start application main loop
[INFO ] MTD: range position X is 0 - 0
[INFO ] MTD: range position Y is 0 - 0
[INFO ] MTD: range touch major is 0 - 0
[INFO ] MTD: range touch minor is 0 - 0
[INFO ] MTD: range pressure is 0 - 255
[INFO ] MTD: range position X is 0 - 0
[INFO ] MTD: range position Y is 0 - 0
[INFO ] MTD: range touch major is 0 - 0
[INFO ] MTD: range position X is 0 - 4095
[INFO ] MTD: range position Y is 0 - 4095
[INFO ] MTD: range touch major is 0 - 0
[INFO ] MTD: axes invertion: X is 0, Y is 0
[INFO ] MTD: rotation set to 0
[INFO ] MTD: range touch minor is 0 - 0
[INFO ] MTD: range pressure is 0 - 255
[INFO ] MTD: range touch minor is 0 - 0
[INFO ] MTD: range pressure is 0 - 255
[INFO ] HIDMotionEvent: using
[INFO ] MTD: axes invertion: X is 0, Y is 0
[INFO ] MTD: rotation set to 0
[INFO ] HIDMotionEvent: using
[INFO ] MTD: axes invertion: X is 0, Y is 0
[INFO ] MTD: rotation set to 0
[INFO ] GL: NPOT texture support is available
[INFO ] HIDMotionEvent: using
[INFO ] HIDMotionEvent: range ABS X position is 0 - 4095
[INFO ] HIDMotionEvent: range ABS Y position is 0 - 4095
[INFO ] HIDMotionEvent: range ABS pressure is 0 - 255
My setup is RPi + 2.8 TFT. I tried to start kivy from gui, from ssh and
from command line mode including sudo. This is my configuration file:
[kivy]
keyboard_repeat_delay = 300
keyboard_repeat_rate = 30
log_dir = logs
log_enable = 1
log_level = debug
log_name = kivy_%y-%m-%d_%_.txt
window_icon =
keyboard_mode =
keyboard_layout = qwerty
desktop = 1
exit_on_escape = 1
pause_on_minimize = 0
config_version = 14
[graphics]
display = 1
fullscreen = 1
height = 240
left = 0
maxfps = 60
multisamples = 2
position = auto
rotation = 0
show_cursor = 1
top = 0
width = 320
resizable = 1
borderless = 1
window_state = visible
minimum_width = 0
minimum_height = 0
[input]
mouse = mouse
mtdev_%(name)s = probesysfs,provider=mtdev
hid_%(name)s = probesysfs,provider=hidinput
[postproc]
double_tap_distance = 20
double_tap_time = 250
ignore = []
jitter_distance = 0
jitter_ignore_devices = mouse,mactouch,
retain_distance = 50
retain_time = 0
triple_tap_distance = 20
triple_tap_time = 375
[widgets]
scroll_timeout = 250
scroll_distance = 20
scroll_friction = 1.
scroll_stoptime = 300
scroll_moves = 5
[modules]
I have no clue why nothing is displayed.
—
Reply to this email directly or view it on GitHub
https://github.com/kivy/kivy/issues/4050#issuecomment-191125871.

Thanks a lot, this thingy with redirection of buffers worked out! I needed only to adjust the rotations of the kivy and it is now really good. I think somebody can close this.

@kived we have dummy clipboard which does copy/paste within kivy.


Add projects, interests and achievements in portfolio.

All sections in portfolio are complete. If formatting issues still arise, they may be resolved once portfolio is deployed in case the issue is due to any dependency. Otherwise I will readjust formatting.

Please add website screenshot in description to help me visualise changes.

Screenshots for reference:


Updated Arr null key behavior

No point in retrieving whole array on null key if you already provided the default you'd like returned if no match is found.
// Wrong
Arr::get([], null, 'default');
// returns
[]

// Right
Arr::get([], null, 'default');
// returns
'default'

Huge breaking changes, and has been tried before. #36726 #36728 #36736

Huge breaking changes, and has been tried before. #36726 #36728 #36736

I suppose there is an actual value in refactoring the failing part for the next major release?


LinktaFlow orientation is displayed in "portrait" orientation to allow for easier full screen viewing

Related User Story

Related Tickets

Ensure LinktaFlow object is displayed properly #352
Acceptance Criteria

LinktaFlow created from LLM response using Dagre is generally in "portrait" orientation
Subtasks
<!-- If necessary, break down the ticket into smaller, actionable subtasks. Create issues accordingly.>

We may decide to close this task.
Research shows that nothing in a prompt or tool will cause the LLM to consider token count when constructing the response. However, manipulating the prompt to limit the total number of nodes and the number of child nodes at each level has made a significant improvement.
Before:

After:


Support completions that require changing from dot to bracket access

Fixes #19433
Must wait on Microsoft/vscode#39893 first.
This adds a completion for a property even if it can't follow a . -- and adds a code action to change the style from x.| to x["|"].

@mjbvz I just pushed a commit using replacementSpan and insertText (ref: #20730).

As I mentioned last week, there are people who've been using spaces in names to use as part of type system hacks.
@RyanCavanaugh had an idea of excluding names that start with a non-identifier character.
I think another idea might be is to de-prioritize names that aren't valid property accesses.

@DanielRosenwasser We could set sortText to a different value for anything that needs brackets, would that work?


Structured logging needs a performance-critical usage pattern

It needs to have a way for parameters to be typed, and for format lookup and parsing to be done once, and for a short-circuit of is enabled to have an allocation-free path.

Just talked to @lodejard.  Moving is issues to RC2.

This is implemented by recent "define message" static methods added to logging


option to edit which projects/tasks don't require notes

If the user says that some projects or tasks don't require notes (#61), there should also be a way to see which projects/tasks that's true of, and remove them from the list (and thus have them require notes again).

Won't do. See comment in #39.


Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble

Trying to set this up but keep getting this "Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble"
the first time after a restart it will act like its trying to work for a few seconds then it will just throw the error immediately when I try to add integration.
I am on docker and have Network :host set

nevermind, For future readers... Update Home assistant.


Paper ID 2758

Low-Level and Physics-based Vision section
High-Resolution Document Shadow Removal via A Large-Scale Real-World Dataset and A Frequency-Aware Shadow Erasing Net.
Repo: https://github.com/CXH-Research/DocShadow-SD7K
Page: https://cxh-research.github.io/DocShadow-SD7K/

Hi @xuhangc, 👋
Thank you for providing this information.
The article, along with all additional information, has been successfully added. If you wish to make any changes, please feel free to submit modifications or additions via a pull request, as outlined in the contributions section.


Incorrect file path while copying unzipped package.

Issue: Currently after unzipping the package, it's copied in to ./site-packages directory instead of ./site-packages/youtube_dl.
Possible solution is to change shutil.move(youtubedl_unarchive_location+youtubedl_dir, youtubedl_location) to shutil.move(youtubedl_unarchive_location+youtubedl_dir, youtubedl_location+youtubedl_dir) here, since here you pass location youtubedl_location+youtubedl_dir.
Currently this leads to Incorrect file path error while executing the file.

Thanks I have made that change, let me know if you still have issues


Addresses two shutdown-related crashes in MICore

VS Bug 275468 ([Feedback] GDB remote debugging reliability problems) complains of many crashes. The two stacks that seem to be MIEngine related are below. Both seem to be related to multithreading issues when closing the debugger.
.Net Runtime Event Log entries:
EventTime:9/26/2016 3:52:41 PM
Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at System.IO.StreamWriter.Flush(Boolean, Boolean)
at System.IO.StreamWriter.Write(Char[], Int32, Int32)
at System.IO.TextWriter.WriteLine(System.String)
at MICore.StreamTransport.Echo(System.String)
at MICore.StreamTransport.Send(System.String)
at MICore.Debugger+d__174.MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.b__6_1(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
EventTime:8/22/2016 2:38:37 PM
Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
at System.Threading.Tasks.TaskCompletionSource`1[[System.__Canon, mscorlib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089]].SetException(System.Exception)
at MICore.Debugger+d__121.MoveNext()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
at MICore.Debugger+d__118.MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.b__6_1(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

LGTM :shipit:


Handling .gif

It doesn't seem like Imagemin is moving gifs over to the 'dest' directory. My task is as follows:
imagemin: {
    dist: {
        files: [{
          expand: true,
          cwd: '<%= yeoman.app %>/img',
          src: '{,*/}*.{png,jpg,jpeg,gif,webp}',
          dest: '<%= yeoman.dist %>/img'
        }]
      }
    }

What was the resolve on this? Can we use it for GIFs? I don't see in the readme where it states it wont process GIFs.


Add arm32v7 builds for Azure Functions (Isolated)

Looking to run Azure Functions on a Raspberry Pi, Docker platform linux/arm/v7
The dotnet sdk has a build for this architecture and platform, but Azure Functions (Isolated) does not. Please could we have this?

@andrewbuckingham , if you have RPI 4 (arm64/v8) then you can try the following: As-is, no support etc. and don't use in production.
https://hub.docker.com/r/mohsinonxrm/azure-functions-dotnet/tags

We currently have no plans to support this architecture.


Fix the dictionary editor

Fix the problem dictionary with int type key can't change key in editor.
Add support to dictionary editor with key type as char, bool, or other number type, and can modify key now.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: D3ZAX:x: liuningliuning seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

It appears that the CLA show wrong user for this pull request and I can't sign CLA with that user. I will try another pull request.


getting error in istio pilot

HI,I am getting below line after implematation ISTIO in my project. its running successfully but getting below line. is its error?:
2019-01-10T06:04:30.333979Z\u0009info\u0009ads\u0009ADS: \"<IP_ADDRESS>:52312\" sidecar~<IP_ADDRESS>~app-name-56cd986847-n6swf.<nameepace>~<nameepace>.svc.cluster.local-782 terminated rpc error: code = Canceled desc = context canceled

Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.0", GitCommit:"ddf47ac13c1a9483ea035a79cd7c10005ff21a6d", GitTreeState:"clean", BuildDate:"2018-12-03T21:04:45Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"linux/amd64"}Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.11", GitCommit:"637c7e288581ee40ab4ca210618a89a555b6e7e9", GitTreeState:"clean", BuildDate:"2018-11-26T14:25:46Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
and istio 1.0.2

and below is istio pilot logs:

> 2019-01-10T06:39:31.601136Z	info	ads	ADS:CDS: REQ <IP_ADDRESS>:52310 sidecar~<IP_ADDRESS>~agreement-service-64dd4b9b8b-z8wdc.cap-staging~cap-staging.svc.cluster.local-959 119.358µs raw: version_info:"2019-01-10T03:14:12Z" node:<id:"sidecar~<IP_ADDRESS>~agreement-service-64dd4b9b8b-z8wdc.cap-staging~cap-staging.svc.cluster.local" cluster:"agreement-service" metadata:<fields:<key:"INTERCEPTION_MODE" value:<string_value:"REDIRECT" > > fields:<key:"ISTIO_PROXY_SHA" value:<string_value:"istio-proxy:99cfc3f74c414dd4fa4aa784a0f8b13e22b81893" > > fields:<key:"ISTIO_PROXY_VERSION" value:<string_value:"1.0.2" > > fields:<key:"ISTIO_VERSION" value:<string_value:"1.0.2" > > fields:<key:"POD_NAME" value:<string_value:"agreement-service-64dd4b9b8b-z8wdc" > > fields:<key:"istio" value:<string_value:"sidecar" > > > build_version:"0/1.8.0-dev//RELEASE" > type_url:"type.googleapis.com/envoy.api.v2.Cluster" response_nonce:"2019-01-10 06:34:31.151561371 +0000 UTC m=+12037.004657786"
> 2019-01-10T06:39:31.601896Z	info	ads	CDS: PUSH 2019-01-10T03:14:12Z for agreement-service-64dd4b9b8b-z8wdc.cap-staging "<IP_ADDRESS>:52310", Clusters: 78, Services 46
> 2019-01-10T06:39:31.630783Z	info	ads	ADS: "<IP_ADDRESS>:52310" sidecar~<IP_ADDRESS>~xca-ksm-service-676454cd48-klz8f.cap-staging~cap-staging.svc.cluster.local-938 terminated rpc error: code = Canceled desc = context canceled
> 2019-01-10T06:39:31.638036Z	info	ads	LDS: PUSH for node:agreement-service-64dd4b9b8b-z8wdc.cap-staging addr:"<IP_ADDRESS>:52310" listeners:45
> 2019-01-10T06:39:31.657596Z	info	ads	ADS: RDS: PUSH for node: agreement-service-64dd4b9b8b-z8wdc.cap-staging addr:<IP_ADDRESS>:52310 routes:13
> 2019-01-10T06:39:31.730562Z	info	ads	ADS:CDS: REQ <IP_ADDRESS>:52312 sidecar~<IP_ADDRESS>~email-service-5856f849d-m46g2.cap-staging~cap-staging.svc.cluster.local-960 1.674356ms raw: version_info:"2019-01-10T03:14:12Z" node:<id:"sidecar~<IP_ADDRESS>~email-service-5856f849d-m46g2.cap-staging~cap-staging.svc.cluster.local" cluster:"email-service" metadata:<fields:<key:"INTERCEPTION_MODE" value:<string_value:"REDIRECT" > > fields:<key:"ISTIO_PROXY_SHA" value:<string_value:"istio-proxy:99cfc3f74c414dd4fa4aa784a0f8b13e22b81893" > > fields:<key:"ISTIO_PROXY_VERSION" value:<string_value:"1.0.2" > > fields:<key:"ISTIO_VERSION" value:<string_value:"1.0.2" > > fields:<key:"POD_NAME" value:<string_value:"email-service-5856f849d-m46g2" > > fields:<key:"istio" value:<string_value:"sidecar" > > > build_version:"0/1.8.0-dev//RELEASE" > type_url:"type.googleapis.com/envoy.api.v2.Cluster" response_nonce:"2019-01-10 06:34:31.306668095 +0000 UTC m=+12037.159764674"
> 2019-01-10T06:39:31.733451Z	info	ads	CDS: PUSH 2019-01-10T03:14:12Z for email-service-5856f849d-m46g2.cap-staging "<IP_ADDRESS>:52312", Clusters: 78, Services 46
> gc 1207 @12337.581s 0%: 0.006+12+7.1 ms clock, 0.012+3.2/4.4/9.4+14 ms cpu, 23->23->11 MB, 24 MB goal, 2 P
> 2019-01-10T06:39:31.767003Z	info	ads	ADS: "<IP_ADDRESS>:52310" sidecar~<IP_ADDRESS>~reseller-service-c6b557dd-jmpx6.cap-staging~cap-staging.svc.cluster.local-939 terminated rpc error: code = Canceled desc = context canceled
> 2019-01-10T06:39:31.780212Z	info	ads	LDS: PUSH for node:email-service-5856f849d-m46g2.cap-staging addr:"<IP_ADDRESS>:52312" listeners:45
> 2019-01-10T06:39:31.798280Z	info	ads	ADS: RDS: PUSH for node: email-service-5856f849d-m46g2.cap-staging addr:<IP_ADDRESS>:52312 routes:13
> 2019-01-10T06:39:31.826768Z	info	ads	ADS: "<IP_ADDRESS>:52310" sidecar~<IP_ADDRESS>~account-service-bc6d965d7-nc8nd.cap-staging~cap-staging.svc.cluster.local-940 terminated rpc error: code = Canceled desc = context canceled
> 2019-01-10T06:39:31.898773Z	info	ads	ADS: "<IP_ADDRESS>:52312" sidecar~<IP_ADDRESS>~auth-service-66bc56c9f5-g65nl.cap-staging~cap-staging.svc.cluster.local-941 terminated rpc error: code = Canceled desc = context canceled
> 2019-01-10T06:39:31.911226Z	info	ads	ADS: "<IP_ADDRESS>:52312" sidecar~<IP_ADDRESS>~download-service-75d5cdb4b9-ntcr9.cap-staging~cap-staging.svc.cluster.local-942 terminated rpc error: code = Canceled desc = context canceled
> 2019-01-10T06:39:31.942325Z	info	ads	ADS:CDS: REQ <IP_ADDRESS>:52310 sidecar~<IP_ADDRESS>~reseller-service-c6b557dd-jmpx6.cap-staging~cap-staging.svc.cluster.local-961 116.227µs raw: version_info:"2019-01-10T03:14:12Z" node:<id:"sidecar~<IP_ADDRESS>~reseller-service-c6b557dd-jmpx6.cap-staging~cap-staging.svc.cluster.local" cluster:"reseller-service" metadata:<fields:<key:"INTERCEPTION_MODE" value:<string_value:"REDIRECT" > > fields:<key:"ISTIO_PROXY_SHA" value:<string_value:"istio-proxy:99cfc3f74c414dd4fa4aa784a0f8b13e22b81893" > > fields:<key:"ISTIO_PROXY_VERSION" value:<string_value:"1.0.2" > > fields:<key:"ISTIO_VERSION" value:<string_value:"1.0.2" > > fields:<key:"POD_NAME" value:<string_value:"reseller-service-c6b557dd-jmpx6" > > fields:<key:"istio" value:<string_value:"sidecar" > > > build_version:"0/1.8.0-dev//RELEASE" > type_url:"type.googleapis.com/envoy.api.v2.Cluster" response_nonce:"2019-01-10 06:34:31.629400507 +0000 UTC m=+12037.482496830"
> 2019-01-10T06:39:31.942945Z	info	ads	CDS: PUSH 2019-01-10T03:14:12Z for reseller-service-c6b557dd-jmpx6.cap-staging "<IP_ADDRESS>:52310", Clusters: 78, Services 46
> gc 1208 @12337.796s 0%: 0.008+10+7.2 ms clock, 0.016+4.3/5.1/7.2+14 ms cpu, 22->22->11 MB, 23 MB goal, 2 P
> 2019-01-10T06:39:31.992923Z	info	ads	LDS: PUSH for node:reseller-service-c6b557dd-jmpx6.cap-staging addr:"<IP_ADDRESS>:52310" listeners:45
> 2019-01-10T06:39:32.012088Z	info	ads	ADS: RDS: PUSH for node: reseller-service-c6b557dd-jmpx6.cap-staging addr:<IP_ADDRESS>:52310 routes:13
> gc 1209 @12337.864s 0%: 0.005+7.7+7.2 ms clock, 0.011+1.0/0.80/11+14 ms cpu, 21->21->11 MB, 22 MB goal, 2 P
> 2019-01-10T06:39:32.034406Z	info	ads	ADS:CDS: REQ <IP_ADDRESS>:52310 sidecar~<IP_ADDRESS>~xca-ksm-service-676454cd48-klz8f.cap-staging~cap-staging.svc.cluster.local-962 48.072µs raw: version_info:"2019-01-10T03:14:12Z" node:<id:"sidecar~<IP_ADDRESS>~xca-ksm-service-676454cd48-klz8f.cap-staging~cap-staging.svc.cluster.local" cluster:"xca-ksm-service" metadata:<fields:<key:"INTERCEPTION_MODE" value:<string_value:"REDIRECT" > > fields:<key:"ISTIO_PROXY_SHA" value:<string_value:"istio-proxy:99cfc3f74c414dd4fa4aa784a0f8b13e22b81893" > > fields:<key:"ISTIO_PROXY_VERSION" value:<string_value:"1.0.2" > > fields:<key:"ISTIO_VERSION" value:<string_value:"1.0.2" > > fields:<key:"POD_NAME" value:<string_value:"xca-ksm-service-676454cd48-klz8f" > > fields:<key:"istio" value:<string_value:"sidecar" > > > build_version:"0/1.8.0-dev//RELEASE" > type_url:"type.googleapis.com/envoy.api.v2.Cluster" response_nonce:"2019-01-10 06:34:31.551813468 +0000 UTC m=+12037.404909906"
> 2019-01-10T06:39:32.034844Z	info	ads	CDS: PUSH 2019-01-10T03:14:12Z for xca-ksm-service-676454cd48-klz8f.cap-staging "<IP_ADDRESS>:52310", Clusters: 78, Services 46
> 2019-01-10T06:39:32.069598Z	info	ads	LDS: PUSH for node:xca-ksm-service-676454cd48-klz8f.cap-staging addr:"<IP_ADDRESS>:52310" listeners:45
> 2019-01-10T06:39:32.099049Z	info	ads	ADS: RDS: PUSH for node: xca-ksm-service-676454cd48-klz8f.cap-staging addr:<IP_ADDRESS>:52310 routes:13
> gc 1210 @12337.939s 0%: 0.007+13+9.7 ms clock, 0.014+3.0/4.6/8.6+19 ms cpu, 21->22->12 MB, 22 MB goal, 2 P
> 2019-01-10T06:39:32.166577Z	info	ads	ADS:CDS: REQ <IP_ADDRESS>:52312 sidecar~<IP_ADDRESS>~download-service-75d5cdb4b9-ntcr9.cap-staging~cap-staging.svc.cluster.local-963 105.202µs raw: version_info:"2019-01-10T03:14:12Z" node:<id:"sidecar~<IP_ADDRESS>~download-service-75d5cdb4b9-ntcr9.cap-staging~cap-staging.svc.cluster.local" cluster:"download-service" metadata:<fields:<key:"INTERCEPTION_MODE" value:<string_value:"REDIRECT" > > fields:<key:"ISTIO_PROXY_SHA" value:<string_value:"istio-proxy:99cfc3f74c414dd4fa4aa784a0f8b13e22b81893" > > fields:<key:"ISTIO_PROXY_VERSION" value:<string_value:"1.0.2" > > fields:<key:"ISTIO_VERSION" value:<string_value:"1.0.2" > > fields:<key:"POD_NAME" value:<string_value:"download-service-75d5cdb4b9-ntcr9" > > fields:<key:"istio" value:<string_value:"sidecar" > > > build_version:"0/1.8.0-dev//RELEASE" > type_url:"type.googleapis.com/envoy.api.v2.Cluster" response_nonce:"2019-01-10 06:34:31.772027047 +0000 UTC m=+12037.625123463"

Hi @hzxuzhonghu
While is it info, I would like to understand while this is happening.
In my  case, I am seeing the same issue, that is, every 5 minutes, I see that error in istio pilot:
2019-03-20T15:29:22.319792Z	info	ads	ADS: "<IP_ADDRESS>:38278" router~<IP_ADDRESS>~istio-ingressgateway-97f4b5d5d-vsngh.istio-system~istio-system.svc.cluster.local-47280 terminated rpc error: code = Canceled desc = context canceled
2019-03-20T15:29:22.319831Z	info	ads	ADS: "<IP_ADDRESS>:38278" router~<IP_ADDRESS>~istio-egressgateway-58748db45f-5jnzv.istio-system~istio-system.svc.cluster.local-47279 terminated rpc error: code = Canceled desc = context canceled
2019-03-20T15:29:22.333196Z	info	ads	ADS: "<IP_ADDRESS>:38234" sidecar~<IP_ADDRESS>~test-app-0.grpc-istio~grpc-istio.svc.cluster.local-47291 terminated rpc error: code = Canceled desc = context canceled
.......
.......

2019-03-20T15:34:22.545998Z	info	ads	ADS: "<IP_ADDRESS>:38234" sidecar~<IP_ADDRESS>~test-app-0.grpc-istio~grpc-istio.svc.cluster.local-47300 terminated rpc error: code = Canceled desc = context canceled
2019-03-20T15:34:22.624420Z	info	ads	ADS: "<IP_ADDRESS>:38278" router~<IP_ADDRESS>~istio-ingressgateway-97f4b5d5d-vsngh.istio-system~istio-system.svc.cluster.local-47303 terminated rpc error: code = Canceled desc = context canceled
2019-03-20T15:34:22.775363Z	info	ads	ADS: "<IP_ADDRESS>:38278" router~<IP_ADDRESS>~istio-egressgateway-58748db45f-5jnzv.istio-system~istio-system.svc.cluster.local-47309 terminated rpc error: code = Canceled desc = context canceled
.......
.......

2019-03-20T15:39:22.849114Z	info	ads	ADS: "<IP_ADDRESS>:38278" router~<IP_ADDRESS>~istio-ingressgateway-97f4b5d5d-vsngh.istio-system~istio-system.svc.cluster.local-47321 terminated rpc error: code = Canceled desc = context canceled
2019-03-20T15:39:22.953582Z	info	ads	ADS: "<IP_ADDRESS>:38278" router~<IP_ADDRESS>~istio-egressgateway-58748db45f-5jnzv.istio-system~istio-system.svc.cluster.local-47324 terminated rpc error: code = Canceled desc = context canceled
2019-03-20T15:39:22.958638Z	info	ads	ADS: "<IP_ADDRESS>:38234" sidecar~<IP_ADDRESS>~test-app-0.grpc-istio~grpc-istio.svc.cluster.local-47323 terminated rpc error: code = Canceled desc = context canceled

On the sidecar containers running the istio-proxy, I see that a full proxy conf reload is happening, closing any established connection and creating a new one. This is having a side effect on the application client side, where I see a 'Transient failure' error when trying to connect to the upstream service vía istio-proxy.
I saw a related issue 6981, but dont know if any body else have seen this problem now.

a full proxy conf reload   this can happen in some scene.

In your env, does these logs always occur?

In 1.1,  --keepaliveMaxServerConnectionAge 30m is added to pilot discovery.  This implies pilot will disconnect connection every 30 minutes. I am not sure if this can influence proxy long-running connections.  @dsanchor Could you remove keepaliveMaxServerConnectionAge  option and test again?
2019-03-21T08:24:04.374541Z	info	ads	ADS: "<IP_ADDRESS>:55788" sidecar~<IP_ADDRESS>~sleep-6df94d7667-cv5xg.default~default.svc.cluster.local-1560 terminated rpc error: code = Canceled desc = context canceled
2019-03-21T08:52:59.013560Z	info	ads	ADS: "<IP_ADDRESS>:38896" sidecar~<IP_ADDRESS>~sleep-6df94d7667-cv5xg.default~default.svc.cluster.local-1564 terminated rpc error: code = Canceled desc = context canceled
2019-03-21T09:21:23.058317Z	info	ads	ADS: "<IP_ADDRESS>:50712" sidecar~<IP_ADDRESS>~sleep-6df94d7667-cv5xg.default~default.svc.cluster.local-1568 terminated rpc error: code = Canceled desc = context canceled
2019-03-21T09:52:46.882176Z	info	ads	ADS: "<IP_ADDRESS>:34098" sidecar~<IP_ADDRESS>~sleep-6df94d7667-cv5xg.default~default.svc.cluster.local-1572 terminated rpc error: code = Canceled desc = context canceled
2019-03-21T10:21:31.694785Z	info	ads	ADS: "<IP_ADDRESS>:46924" sidecar~<IP_ADDRESS>~sleep-6df94d7667-cv5xg.default~default.svc.cluster.local-1576 terminated rpc error: code = Canceled desc = context canceled

@PiotrSikora can you help?

@hzxuzhonghu I just removed keepaliveMaxServerConnectionAge and took the value 2562047h47m16.854775807s by defaut.
I see the same errors every 5 minutes, causing my gRPC application long-running connections to be closed and forcing the client to re-connect (while failing during couple of seconds.. which it seems it is what it takes to reload istio-proxy).

do you see envoy restarted? check the istio-proxy sidecar.
And any special configuration for pilot?

No special configuration from pilot.
This is what I recurrently see on every istio-proxy:
[2019-03-22 13:22:08.327][24][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:102] gRPC config stream closed: 13,   | [2019-03-22 13:22:08.671][24][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.Listener.use_original_dst'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md  for details.   | [2019-03-22 13:27:08.721][24][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:102] gRPC config stream closed: 13,   | [2019-03-22 13:27:09.130][24][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.Listener.use_original_dst'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md  for details.   | [2019-03-22 13:32:09.201][24][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:102] gRPC config stream closed: 13,   | [2019-03-22 13:32:09.754][24][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.Listener.use_original_dst'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md  for details.   | [2019-03-22 13:37:09.843][24][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:102] gRPC config stream closed: 13,   | [2019-03-22 13:37:09.927][24][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.Listener.use_original_dst'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md  for details.   | [2019-03-22 13:37:16.588][24][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.Listener.use_original_dst'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md  for details.   | [2019-03-22 13:42:16.907][24][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:102] gRPC config stream closed: 13,   | [2019-03-22 13:42:17.073][24][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.Listener.use_original_dst'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md  for details.   | [2019-03-22 13:47:18.015][24][warning][config] [bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_stream_lib/common/config/grpc_stream.h:102] gRPC config stream closed: 13,   | [2019-03-22 13:47:18.529][24][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.Listener.use_original_dst'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md  for details.

Previously, I donot think reconnect of envoy will cause the proxied connections drain.

Have no idea why 5 minutes periodically disconnect client(envoy) connection.

@rshriram

I met the same issue in istio 1.1.0, any update for this issue?

$ istioctl proxy-status
Error: error execing into eric-mesh-controller-5b45854df6-fckmv/istio-system discovery container: command terminated with exit code 126
---pilot discovery log
2019-04-08T07:41:49.381821Z     info    ads     LDS: PUSH for node:istio-egressgateway-677f6765cd-tjrck.istio-system addr:"<IP_ADDRESS>:37378" listeners:0 106
2019-04-08T07:41:50.641579Z     info    ads     ADS: "<IP_ADDRESS>:54212"  terminated rpc error: code = Canceled desc = context canceled
2019-04-08T07:41:51.446677Z     info    ads     ADS: "<IP_ADDRESS>:54212"  terminated rpc error: code = Canceled desc = context canceled
2019-04-08T07:41:55.047283Z     info    Handling event update for pod productpage-v1-7dfb78b57f-8p5w8 in namespace hobby -> <IP_ADDRESS>
2019-04-08T07:41:55.050358Z     info    Handling event delete for pod productpage-v1-7dfb78b57f-8p5w8 in namespace hobby -> <IP_ADDRESS>
2019-04-08T07:41:55.063139Z     info    Handling event update for pod reviews-v2-5b99f6bb68-52fds in namespace hobby -> <IP_ADDRESS>
2019-04-08T07:41:55.067472Z     info    Handling event delete for pod reviews-v2-5b99f6bb68-52fds in namespace hobby -> <IP_ADDRESS>
2019-04-08T07:41:56.785872Z     info    ads     ADS: RDS: PUSH for node: istio-ingressgateway-75b684df9-gx2kc.istio-system addr:<IP_ADDRESS>:51776 routes:0
2019-04-08T07:42:09.456069Z     info    ads     ADS: "<IP_ADDRESS>:54212"  terminated rpc error: code = Canceled desc = context canceled
2019-04-08T07:42:24.917735Z     info    transport: loopyWriter.run returning. connection error: desc = "transport is closing"
gc 115 @3790.212s 0%: 0.008+2.3+0.068 ms clock, 0.032+0.48/2.2/5.9+0.27 ms cpu, 14->14->7 MB, 15 MB goal, 4 P
2019-04-08T07:42:27.544387Z     info    ads     ADS: "<IP_ADDRESS>:55180"  terminated rpc error: code = Canceled desc = context canceled
2019-04-08T07:42:40.830324Z     info    ads     ADS: "<IP_ADDRESS>:55180"  terminated rpc error: code = Canceled desc = context canceled
2019-04-08T07:42:51.089188Z     info    ads     ADS: "<IP_ADDRESS>:55180"  terminated rpc error: code = Canceled desc = context canceled
2019-04-08T07:43:14.070789Z     info    ads     ADS: "<IP_ADDRESS>:55180"  terminated rpc error: code = Canceled desc = context canceled
2019-04-08T07:43:32.686539Z     info    ads     ADS: "<IP_ADDRESS>:55180"  terminated rpc error: code = Canceled desc = context canceled
gc 116 @3858.477s 0%: 0.008+3.1+0.064 ms clock, 0.035+0.22/2.5/6.7+0.25 ms cpu, 14->14->7 MB, 15 MB goal, 4 P
2019-04-08T07:44:02.688642Z     info    ads     ADS: "<IP_ADDRESS>:55180"  terminated rpc error: code = Canceled desc = context canceled
#-----pilot proxy log
[2019-04-08 08:40:07.831][60][critical][main] [external/envoy/source/server/server.cc:86] error initializing configuration '/etc/istio/proxy/envoy.yaml': Invalid path: /etc/certs/cert-chain.pem
Invalid path: /etc/certs/cert-chain.pem
2019-04-08T06:40:07.834391Z     warn    Epoch 0 terminated with an error: exit status 1
2019-04-08T06:40:07.834407Z     warn    Aborted all epochs
2019-04-08T06:40:07.834423Z     warn    Failed to delete config file /etc/istio/proxy/envoy-rev0.json for 0, remove /etc/istio/proxy/envoy-rev0.json: no such file or directory
2019-04-08T06:40:07.834428Z     info    Epoch 0: set retry delay to 51.2s, budget to 1
2019-04-08T06:40:19.066888Z     info    watchFileEvents: "/etc/certs//..2019_04_08_06_40_19.139100566": CREATE
2019-04-08T06:40:19.066936Z     info    watchFileEvents: "/etc/certs//..2019_04_08_06_40_19.139100566": MODIFY|ATTRIB
2019-04-08T06:40:19.067031Z     info    watchFileEvents: "/etc/certs//key.pem": CREATE
2019-04-08T06:40:19.067090Z     info    watchFileEvents: "/etc/certs//root-cert.pem": CREATE
2019-04-08T06:40:19.067128Z     info    watchFileEvents: "/etc/certs//cert-chain.pem": CREATE
2019-04-08T06:40:19.067171Z     info    watchFileEvents: "/etc/certs//..data_tmp": CREATE
2019-04-08T06:40:19.067187Z     info    watchFileEvents: "/etc/certs//..data_tmp": RENAME
2019-04-08T06:40:19.067192Z     info    watchFileEvents: "/etc/certs//..data": CREATE
2019-04-08T06:40:19.067225Z     info    watchFileEvents: "/etc/certs//..2019_04_08_06_39_15.332221871": DELETE
2019-04-08T06:40:29.067049Z     info    watchFileEvents: notifying
2019-04-08T06:40:29.067191Z     info    Received new config, resetting budget
2019-04-08T06:40:29.067204Z     info    Reconciling retry (budget 10)
2019-04-08T06:40:29.067226Z     info    Epoch 0 starting
2019-04-08T06:40:29.067255Z     info    Envoy command: [-c /etc/istio/proxy/envoy.yaml --restart-epoch 0 --drain-time-s 45 --parent-shutdown-time-s 60 --service-cluster istio-pilot --service-node sidecar~<IP_ADDRESS>~eric-mesh-controller-5b45854df6-fckmv.istio-system~istio-system.svc.cluster.local --max-obj-name-len 189 --allow-unknown-fields -l warning]
[2019-04-08 08:40:29.086][65][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.listener.Filter.config'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-04-08 08:40:29.086][65][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.listener.Filter.config'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.
[2019-04-08 08:40:29.086][65][warning][misc] [external/envoy/source/common/protobuf/utility.cc:129] Using deprecated option 'envoy.api.v2.listener.Filter.config'. This configuration will be removed from Envoy soon. Please see https://github.com/envoyproxy/envoy/blob/master/DEPRECATED.md for details.

I think i find the 5min periodically  disconnect come from,
this https://www.envoyproxy.io/docs/envoy/latest/api-v2/config/filter/network/http_connection_manager/v2/http_connection_manager.proto.html stream_idle_timeout

I just updated to Istio 1.1.2 and dont see this issue anymore

I have deployed istio in aws kube cluster. Facing the same issue

also having the same issue on istio 1.2.3 with the following logs every 5m
transport: http2Server.HandleStreams failed to read frame: read tcp <IP_ADDRESS>:15010-><IP_ADDRESS>:36838: use of closed network connection
istio-pilot-aaa-bbbb discovery 2019-08-21T14:00:54.823655Z	info	transport: loopyWriter.run returning. connection error: desc = "transport is closing"
istio-pilot-aaa-bbbb discovery 2019-08-21T14:00:54.823703Z	info	ads	ADS: "<IP_ADDRESS>:36838" sidecar~<IP_ADDRESS>~podname.svc.cluster.local-34312 terminated rpc error: code = Canceled desc = context canceled

This is normal , the pilot periodically disconnect connection with sidecar to better balance the load between multi pilot.
Please check the --keepaliveMaxServerConnectionAge flag of pilot

This is normal , the pilot periodically disconnect connection with sidecar to better balance the load between multi pilot.
Please check the --keepaliveMaxServerConnectionAge flag of pilot

hi,  after the the pilot disconnect the connection, it seems that the sidecar cannot connect to pilot immediately at some time.
however the sidecar don't log any connect logs. what i can ensure is that after disconnect the pilot don't push to the sidecar until 10 minutes later.
if the backends endpoints change at this time, which will lead to much request error
i use 1.1.3

It is normal for connection to close ever 5 min due to keepalive. If you want to change it the option is configurable. Based on this I don't think there is any action items here left


Test Open data cam 2.0.0-beta.4 on Jetson Nano - TX2

cc @b-g @mmmmmmmmmmmmmmmm  @florianporada
2.0.0-beta.1 ready 🎉:
After lots of "docker" pain, I managed it ! To have a one line command install & run for opendatacam v2.
Also it runs at 12 FPS on TX2 with Yolo v2 voc weight... 4 FPS more than Opendatacam v1
See Install Experience (30s)

It actually takes only 3 min on a good connexion to get opendatacam ready to use... what a change from v1 😉
For @florianporada :
Would be helpful if you can try to run the 2.0.0-beta.1 on the TX2 and give me some feedback . You will need first to re-flash the jetson with jetpack 4.2, see README: https://github.com/moovel/lab-opendatacam/tree/v2
PS: it might not work on the xavier as I need to build a different docker image adapted for Xavier architecture
For @b-g @mmmmmmmmmmmmmmmm  :
If you want to play with the UI, I added a section on the README on how to run opendatacam in simulation mode on your local machine: https://github.com/moovel/lab-opendatacam/tree/v2#run-simulation-mode

Know issue:
Already seen that it can crash after a while, will need to investigate
{
 "frame_id":18393,
 "objects": [
  {"class_id":8, "name":"chair", "relative_coordinates":{"center_x":0.817841, "center_y":0.739374, "width":0.341478, "height":0.508410}, "confidence":0.879339},
  {"class_id":8, "name":"chair", "relative_coordinates":{"center_x":0.097692, "center_y":0.740505, "width":0.181534, "height":0.506625}, "confidence":0.368568}
 ]
}
SyntaxError: Unexpected token , in JSON at position 528
    at JSON.parse (<anonymous>)
    at IncomingMessage.<anonymous> (/lab-opendatacam/server/Opendatacam.js:490:46)
    at IncomingMessage.emit (events.js:189:13)
    at addChunk (_stream_readable.js:284:12)
    at readableAddChunk (_stream_readable.js:265:11)
    at IncomingMessage.Readable.push (_stream_readable.js:220:10)
    at HTTPParser.parserOnBody (_http_common.js:122:22)
    at Socket.socketOnData (_http_client.js:442:20)
    at Socket.emit (events.js:189:13)
    at addChunk (_stream_readable.js:284:12)
2019-04-04T21:27:52.998+0000 I NETWORK  [conn4] end connection <IP_ADDRESS>:47762 (0 connections now open)
==== HTTP Stream closed by darknet, reset UI, might be running from file and ended it or have troubles with webcam and need restart =====
Pheew ....! Something unexpected happened. This should be handled more gracefully. I am sorry. The culprit is:  Error: Cannot stop process that is not run

@tdurand Wow + mega! 🎉

@tdurand
Thanks for the update :)
It's really an improvement to the old installation process 😁
I'll give you feedback as soon as possible

@tdurand Wow, super cool! Thanks!

Just document the scope of 2.0 quickly:
2.0

Demo mode for online "playback" demos in website
Emphasis on Nano
Docker support for: Nano, TX2, Xavier and docker nvidia
docker nvidia -> enables "cloud support"
maybe: external ip cam input

Out (maybe later)

Support of additional third party neural nets via tensorflow.js in node.js
License plate detection

Thanks @b-g !
I added a first docker image compatible with Jetson nano for testing, see README of v2: https://github.com/moovel/lab-opendatacam/tree/v2#2-install-and-start-opendatacam-3-min-
For now it will run slow at 4 FPS as it is still running YOLOv2 + VOC , but next week I'll work on making the neural network runned configurable.

Ok I've reorganized a bit the repo issues, now we have a v2 milestone: https://github.com/moovel/lab-opendatacam/milestone/1 , and this issue is now for feedback from testing the First beta on jetson.

I have three tx2 for my project, and I am mainly using this application on them to count cars and trucks. what kind of test results are you interested in, maybe I can be of some assistance.

Hi @shams3049 , many thanks for your message. Mainly just looking to test it on other jetsons than mine to see if it works, and maybe feedback on new the install process...
If you want to try the new version just follow this guide: https://github.com/moovel/lab-opendatacam/tree/v2#-get-started-quick-setup . You will need to flash one of your jetson with the new jetpack 4.2.

Installing and running the application works perfectly. No issues.
I still have to figure out why it happens. But running the application for longer then 4 to 5 hours tends to crash or have no response what so ever.

@shams3049 , great ! thanks for feedback and the long test, I still need to do those myself....
Two things you can try if you want:

When it crashes / freeze, try to have a look at the logs: I think with sudo docker logs
More time consuming, but try to install it without docker and see if it has the same problem (maybe it is docker related): https://github.com/moovel/lab-opendatacam/blob/v2/doc/RUN_WITHOUT_DOCKER.md

I am running two Jetson TX2 with Jetpack 4.2 one with docker and one without. Will leave them running over night and compair the results 2mro morning. So far both looks okay.
However I have to add, that the device with Docker is running a Webcam, where as the device running without the docker is running a CSI-2 camera sensor from e-con

@shams3049 Awesome , many thanks, let's see what comes out of it...
Just curious, the CSI-2 camera works out of the box with opendatacam ?

No totally not, they are one of the tedious and fragile part of the whole setup. I want to generate data in night and day, so I dont have much choice of low light sensors.
So far both the vendors that manufacturer CSI-2 camera censors for Jetson TX2 board are behind on every aspect regarding drivers and interfacing.

Ok ! and did you notice any tracker accuracy difference with night footage ? I'm not sure if YOLO is trained for low light environments.

YOLO is pretty good at it actually. The trained model are looking for feature set (shape and all). The low light sensor are good at contours. So win/win.
My biggest problem is indefinite run time.
Pretty much out of options on how to make the system stable for longer and longer runs, as the systems are deployed at remote locations,

Ok, let's see if we can improve this, but yes it isn't the goal of this project, I mean we want it to be able to run at least a day without crashing and more if possible, but we do not test it much more than this...
With v1 how long did it last before crashing ?

V1 crashed more often actually.
I totally understand as its not the goal of this project.
As most of the requirements for my project are met thanks to this project. So I have much time to work on the stability of this project.
So in case you want me to look at a specific part, that you think can improve stability, I would be glad to do so. Feel free to tag me along any performance issue that need in depth analysis.

Thanks, well, let's see what comes ou of those test, I guess if it is the core YOLO implem: https://github.com/AlexeyAB/darknet that is crashing we can't do much.. But maybe as now the software we built around it is much better than v1 we could have a way to detect a crash and restart it automaticly after this and restore the current counting areas configuration...

FYI install process is broken for v2.0.0-beta.1 as I'm working on v2.0.0-beta.2 which will introduce configurable neural network weights, choose input video (file, difference webcam types...)
v2.0.0-beta.2 Should be ready by the end of the week, of early next week.

I just released v2.0.0-beta.2 💪
It features:

Opendatacam app improvements ( see https://github.com/moovel/lab-opendatacam/issues/60#issuecomment-488832532 )
Configurable settings (neural network run, run from files), See config documentation to get a sense of what is configurable https://github.com/moovel/lab-opendatacam/blob/v2.0.0-beta.2/doc/CONFIG.md
Docker setup improvements to be able to change settings
Lots more documentation

See new README quick start on how to install this new version: https://github.com/moovel/lab-opendatacam/tree/v2#2-install-and-start-opendatacam-3-min-
For now I just did docker builds for jetson nano and jetson tx2 : https://hub.docker.com/r/opendatacam/opendatacam/tags
Any feedback is useful if you test v2.0.0-beta.2 😎

@tdurand Yay!

Error when install on jetson TX2
docker: Error response from daemon: error while creating mount source path '/usr/lib/aarch64-linux-gnu/libGL.so': mkdir /usr/lib/aarch64-linux-gnu/libGL.so: file exists.
nvidia@nvidia-TX2:~/openDataCam$ sudo ./install-opendatacam.sh --platform tx2
Installing opendatacam docker image
Stop any running docker container...
Installing opendatacam v2.0.0-beta.2 for platform: tx2 ...
Download run script for docker ...
--2019-05-18 17:09:06--  https://raw.githubusercontent.com/moovel/lab-opendatacam/v2.0.0-beta.2/docker/run-jetson/run-docker.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... <IP_ADDRESS>
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2837 (2.8K) [text/plain]
Saving to: ‘run-docker.sh’
run-docker.sh       100%[==================>]   2.77K  --.-KB/s    in 0s
Last-modified header missing -- time-stamps turned off.
2019-05-18 17:09:07 (6.19 MB/s) - ‘run-docker.sh’ saved [2837/2837]
Download config file ...
--2019-05-18 17:09:07--  https://raw.githubusercontent.com/moovel/lab-opendatacam/v2.0.0-beta.2/config.json
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... <IP_ADDRESS>
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1287 (1.3K) [text/plain]
Saving to: ‘config.json’
config.json         100%[==================>]   1.26K  --.-KB/s    in 0s
Last-modified header missing -- time-stamps turned off.
2019-05-18 17:09:07 (24.2 MB/s) - ‘config.json’ saved [1287/1287]
Create the directory to run on files ...
Download demo video ...
WARNING: timestamping does nothing in combination with -O. See the manual
for details.
--2019-05-18 17:09:07--  https://github.com/moovel/lab-opendatacam/raw/v2.0.0-beta.2/static/demo/demo.mp4
Resolving github.com (github.com)... <IP_ADDRESS>
Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://raw.githubusercontent.com/moovel/lab-opendatacam/v2.0.0-beta.2/static/demo/demo.mp4 [following]
--2019-05-18 17:09:08--  https://raw.githubusercontent.com/moovel/lab-opendatacam/v2.0.0-beta.2/static/demo/demo.mp4
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... <IP_ADDRESS>
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|<IP_ADDRESS>|:443... connected.

Hum.. And it works when you comment out this line ? Do you have a clean Jetpack 4.2 ?

Yes, it is a clean 4.2 Jetpack installation.
Worked fine with “file” option, but hangs at usbcam and raspberrycam.
Thanks
On Mon, May 20, 2019 at 3:34 AM Thibault Durand<EMAIL_ADDRESS>wrote:

Hum.. And it works when you comment out this line ? Do you have a clean
Jetpack 4.2 ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/moovel/lab-opendatacam/issues/70?email_source=notifications&email_token=ABLKVMA6CBLZTKFLT5TITADPWJ5EHA5CNFSM4HDXA2OKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVYMWWI#issuecomment-493931353,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLKVMCKH6ZRAIH7ISTZI7TPWJ5EHANCNFSM4HDXA2OA
.

Weird you had to edit the run-docker script for a clean jetpack 4.2 install... I'll try to reproduce this myself later this week

Make sure you connect the usbcam before starting the jetson , and that only one of the camera is connected to it... (Raspberry Pi isn't supported yet with docker installation but will be soon) . You can run this command ls dev/video* to see if you have a video0 appearing which means you're camera is detected. Also you can do a sudo docker container list & sudo docker logs <containerID> and look at the logs and send me the logs.

Findings from testing the odc on tx2 and nano:

When flashing the Jetson I had some issues caused by the SDK Manager. Make sure that python is installed. Did the trick for me. (sudo apt-get install python)

When I tried to run the install-opendatacam.sh script after a clean setup. The script failed with:

Installing opendatacam docker image
Stop any running docker container...
"docker stop" requires at least 1 argument.

Since there are no docker containers to stop this error will appear. Quickfix: Run docker run hello-world to have a container in the list.

If the account is used, which is created during the flashing, I think putting it in the docker group from the beginning makes things easier so the whole sudo prefixing will disappear. (sudo usermod -aG docker $USER + restart/re-login).

Unless you are logged in, the services does not seem to work. After logging in via ssh or directly (not with root) and checking if the container is running via docker ps the service is available via browser. (Which account did you use? @tdurand)

After the install-opendatacam.sh script finished, the usb cam was not recognized by the default config ("usbcam": "v4l2src ! video/x-raw, framerate=30/1, width=640, height=360 ! videoconvert ! appsink") . Adding device=/dev/video1 (or the path where the camera is reachable) after v4l2src solved the issue for me. (Possible Improvement: Introduce a device variable which can be modified in the config file as well.)

It seems that the JSON data for the path feature generates non valid JSON:

{
 "frame_id":8383,
 "objects": [
  {"class_id":14, "name":"person", "relative_coordinates":{"center_x":0.013917, "center_y":0.808672, "width":0.027029, "height":0.171619}, "confidence":0.317677},
  {"class_id":14, "name":"person", "relative_coordinates":{"center_x":0.278547, "center_y":0.735929, "width":0.041525, "height":0.156780}, "confidence":0.275129},
  {"class_id":6, "name":"car", "relative_coordinates":{"center_x":0.432426, "center_y":0.803255, "width":0.122990, "height":0.129827}, "confidence":0.770144},
  {"class_id":6, "name":"car", "relative_coordinates":{"center_x":0.215096, "center_y":0.890960, "width":0.157477, "height":0.144858}, "confidence":0.642485},
  {"class_id":6, "name":"car", "relative_coordinates":{"center_x":0.575315, "center_y":0.742808, "width":0.095191, "height":0.093791}, "confidence":0.561879},
  {"class_id":6, "name":"car", "relative_coordinates":{"center_x":0.062624, "center_y":0.936735, "width":0.119383, "height":0.140294}, "confidence":0.523762},
  {"class_id":6, "name":"car", "relative_coordinates":{"center_x":0.745875, "center_y":0.935939, "width":0.103746, "height":0.110257}, "confidence":0.452738},
  {"class_id":6, "name":"car", "relative_coordinates":{"center_x":0.866210, "center_y":0.785294, "width":0.106178, "height":0.172627}, "confidence":0.367681},
  {"class_id":6, "name":"car", "relative_coordinates":{"center_x":0.630859, "center_y":0.959244, "width":0.181323, "height":
SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at IncomingMessage.<anonymous> (/lab-opendatacam/server/Opendatacam.js:490:46)
    at IncomingMessage.emit (events.js:189:13)
    at addChunk (_stream_readable.js:284:12)
    at readableAddChunk (_stream_readable.js:265:11)
    at IncomingMessage.Readable.push (_stream_readable.js:220:10)
    at HTTPParser.parserOnBody (_http_common.js:122:22)
    at Socket.socketOnData (_http_client.js:442:20)
    at Socket.emit (events.js:189:13)
    at addChunk (_stream_readable.js:284:12)
Error with msg send by YOLO, not valid JSON
0.085623}, "confidence":0.311012},
  {"class_id":6, "name":"car", "relative_coordinates":{"center_x":0.524645, "center_y":0.747425, "width":0.088093, "height":0.107299}, "confidence":0.295245},
  {"class_id":6, "name":"car", "relative_coordinates":{"center_x":0.649867, "center_y":0.721911, "width":0.074840, "height":0.071174}, "confidence":0.271292},
  {"class_id":6, "name":"car", "relative_coordinates":{"center_x":0.871647, "center_y":0.794196, "width":0.162976, "height":0.306448}, "confidence":0.268356},
  {"class_id":5, "name":"bus", "relative_coordinates":{"center_x":0.168569, "center_y":0.656027, "width":0.204142, "height":0.246275}, "confidence":0.257718}
 ]
}
SyntaxError: Unexpected token } in JSON at position 8
    at JSON.parse (<anonymous>)
    at IncomingMessage.<anonymous> (/lab-opendatacam/server/Opendatacam.js:490:46)
    at IncomingMessage.emit (events.js:189:13)
    at addChunk (_stream_readable.js:284:12)
    at readableAddChunk (_stream_readable.js:265:11)
    at IncomingMessage.Readable.push (_stream_readable.js:220:10)
    at HTTPParser.parserOnBody (_http_common.js:122:22)
    at Socket.socketOnData (_http_client.js:442:20)
    at Socket.emit (events.js:189:13)
    at addChunk (_stream_readable.js:284:12)
Error with msg send by YOLO, not valid JSON

Could this be a streaming issue?

I tried to adjust the resolution for the camera but it failed for all resolutions I tried. (I used lsusb -s 001:002 -v | egrep "Width|Height" to get the available resolutions)

VIDEOIO ERROR: V4L: device v4l2src device=/dev/video1 ! video/x-raw, framerate=30/1, width=1280, height=720 ! videoconvert ! appsink: Unable to query number of channels

Opening a second browser window is opened, the boundingboxes, counters and pathviz will freeze on the old window (active on the new window) - but I think we can ignore this 'issue', since most of the time only one connection will be open at the time.

Nano only: After installation and starting the service - it became close to unusable since the input lag on the nano was very high (~20 seconds).

Nano only: The live stream of the camera has also a big delay (IMO: can also be ignored since the detections are good and just don't match the camera stream. Which is also just for calibration and initial setup)

Nano only: Also the nano crashes if the voltage is not set to 5W via command line. (assuming that the power supply only provides 5W)

Besides those little bugs, the installation process is super easy and straight forward. Including the feature update it is a super huge improvement to v1 👍👍😃

@florianporada  , many thanks for this , very helpful

Python issue with sdk manager : Could you add a line in "Common issues" in https://github.com/moovel/lab-opendatacam/blob/v2/doc/FLASH_JETSON.md ?

For the docker stop yes I already fixed this but didn't release a new beta yet

Interesting that you can avoid the sudo ... Not sure I quite understand everything.. For now you just don't log in, the docker hub images of opendatacam are public.. You say that if you do not login to a docker account the services of auto-restart doesn't work ? Maybe we can have a quick call to discuss docker improvements

Yes I think we should try to detect which device usbcam is available, for now we assume it will be 0 .. Did you had more than one thing connected .. not sure why it was on video1 .. Also the gstreamer pipeline is "v4l2src device=/dev/video1 ! video/x-raw, framerate=30/1, width=640, height=360 ! videoconvert ! appsink" for alternative video devices... I'll document this in the next beta I'll release..

Yes darknet sends not valid JSON on each tick but I also fixed this mess by doing some more hacking around the JSON streams lately, will also be released in next beta

To adjust the camera resolution, you need to change it in the Gstreamer pipeline (one of the reasons we use gstreamer now) .. Here is how you do it: "v4l2src device=/dev/video1 ! video/x-raw, framerate=30/1, width=1280, height=720 ! videoconvert ! appsink" ... Need to document this.. but the idea is to limit it to a low resolution so the video stream is fast, and YOLO just needs  400x400 in input.

Yes this is a limitation of opendatacam, only one client working at a time.... Will see in the future if we want to invest time on this

Yes nano takes almost 30s to load YOLO and start..

This is not normal, maybe related to the non valid json, shouldn't have stream lag with the detections

For the power setting for nano, yes, need to document this also.

I'll release a new beta by the end of the week so you can test some improvements

Concerning Interesting that you can avoid the sudo ... Not sure I quite understand everything..

sudo usermod -aG docker $USER only adds the current logged in user to the docker linux group and gives it permission to use the docker without sudo. - So this has nothing to do with the docker registry :). A proposal would be to add this command: $ sudo usermod -aG docker $USER to the install-opendatacam.sh script.

the Auto restart of the container on reboot works. But I have to ssh on the jetson (and apparently run a docker command like: docker ps) in order to be able to use the opendatacam via the browser. Maybe docker is stuck or something - are you able to start the the opendatacam without ssh-ing onto the hardware?

Camera resolution: I tried adjust the resolution as described by you but it results in the VIDEOIO ERROR: V4L: device v4l2src device=/dev/video1 ! video/x-raw, framerate=30/1, width=1280, height=720 ! videoconvert ! appsink: Unable to query number of channels  error. I curious if higher resolution leads to better results in this case.

I'll update the docs accordingly

Ok, will try this, good suggestion !

Hum... yes, docker container starts on boot and start the node.js app... On the nano it takes time though, but after 5 min you should be able to open your browser at IPOFJETSON:8080 which sshing into it..

Ah yes sorry, I need to write more doc on this, but you need to specify a width and height supported by the webcam :  in order to find out which resolution are supported, try this:

sudo apt-get install v4l-utils
v4l2-ctl --list-formats-ext

Higher resolution won't help with better detections as YOLO resize the input to 412x412 px anyway.. But the default for the height is lower than that so I should put at least a bit more.

BTW the command that start the docker container is: sudo ./run-docker.sh run -d --restart unless-stopped opendatacam/opendatacam:$VERSION-$PLATFORM  if you want to investigate whever the container is starting at boot

FYI:
The status of docker was Inactive on startup ($ systemctl show --property ActiveState docker)
I think for me, running $ sudo systemctl enable docker did the trick.
After restarting, I was able to connect via the browser to the jetson board. ✌

Ok, good to know, maybe you cam add this to the TROUBLESHOOTING ;-)

I've tagged a v2.0.0-beta.4 and released Jetson Nano and TX2 images.
Still need to work on some setup improvements discuss here, and this release make me thing that we need an upgrade script, for now need to re-run the install script, which should work
PS: I may be half broken, just after pushing the docker image, I found out that the data page in the app was crashing... will investigate next week.

FYI beta.4 was half broken because I didn't update my config.json file after updating the docker container, I added a note about this (upgrading from v2.x to v2.x): https://github.com/moovel/lab-opendatacam/tree/v2#2-bis-optional-upgrade-opendatacam-from-v2x-to-another-v2x-version

Closing this in favor or https://github.com/opendatacam/opendatacam/issues/100

I am trying to use the opendatacam with nvidia docker and a webcam and I am getting countless of errors "Video-stream stopped!" can you do a simple change there with a counter or something to not have 100.000 same errors on log? so the log is unreadable after all of those and I cannot find out why the stream don't open

Hi, yes I feel you.. We would need add some kind of filter...
If you have lots of errors this means that YOLO seems to start...
Please try to restart the docker container, open the app and immediatly click on the show details > download log button so we see the first part of the log.

Also please comment directly on #100 or create a dedicated new issue, I closed this issue 😉


Update House of Force Version Info

The main page claims that libc < 2.29 is vulnerable to the House of Force attack, but the malloc(): corrupted top size check seems to have been backported to previous versions.  My 2.28 libc contains this check.  Prior versions may have received the fix as well.

libc is always updating. If we keep update with the latest protections, it will be much harder for beginner to start and hard to maintain.
Here the libc means the libc shipped in  ubuntu. So libc-2.28 means the libc shipped in ubuntu-18.10

Makes sense.  My libc was from Debian 10.  It might be nice to specify that those version numbers are specifically for Ubuntu, though, so others don't get confused like I did.


data/presets: add surveillance and camera related properties

https://wiki.openstreetmap.org/wiki/Tag:man_made%3Dsurveillance
https://wiki.openstreetmap.org/wiki/Proposed_features/Extended_tags_for_Key:Surveillance
These are mandatory tags:

surveillance
surveillance:type

I do not feel that the following are important, they can be selected from
the drop down manually anyway:

operator
name

These tags are well established:

camera:type has 15k users
camera:mount has 13k users
surveillance:zone has 17k users (mostly traffic is noted)
camera:direction has 6k users

These tags are in the proposed status:

contact:webcam usage is only starting
height

People used various tags instead of contact:webcam in the past
because of it being a recent tag, and/or a lack of knowledge or being
mislead by the dropdown.
Thus it is difficult to quote an exact number, but by using complex
regexp queries, I could find thousands of usages for webcam links
when properly combining man_made/surveillance/camera and various
(sometimes invalid) keywords in the key or value part of a tag:

website
image
uri, url, link, http, contact
stream
webcam

Thank you for the insightful comments. I will probably have some time tomorrow to do the fix-ups.

Requested changes done. Added camera:direction as well and ordered options by occurrence.

Thanks @bkil I made a few small cleanups and merged..
BTW, you don't need to include the filename in the commit message - GitHub makes it really easy for me to see what files were changed.   It's better to use those words to include a summary that I can scan quickly when I'm looking over the commits with git log.
How to Write a Git Commit Message


Multiple errors after upgrade to 1.3.5

What version of Remix are you using?
1.3.5
Steps to Reproduce
Note: You must have created a firebase application and downloaded the service account json file, as well as adding GOOGLE_APPLICATION_CREDENTIALS="serviceAccount.json" to a .env file

Create new remix package yarn create remix firebase-remix using the Remix App server
Install firebase-admin yarn add firebase-admin
Add FirebaseAdmin.ts and insert the following:

import { applicationDefault, getApp, initializeApp } from 'firebase-admin/app';

import type { App } from 'firebase-admin/app';

// Admin app instance
let app: App;

try {
  app = getApp();
} catch {
  app = initializeApp({
    credential: applicationDefault(),
  });
}

export { app };

Import the app into routes/index.tsx

import '~/utils/FirebaseAdmin';

export default function Index() {
  return (

Welcome to Remix

            15m Quickstart Blog Tutorial

            Deep Dive Jokes App Tutorial

            Remix Docs

  );
}

Expected Behavior
Expected behavior is that no errors are thrown.
Actual Behavior
The following is outputted:
➜  remix-firebase-admin yarn dev
yarn run v1.22.17
$ remix dev
Loading environment variables from .env
Watching Remix app in development mode...
▲ [WARNING] Ignoring this import because "app/utils/FirebaseAdmin.ts" was marked as having no side effects

    route:/Users/jason/Projects/remix-firebase-admin/app/routes/index.tsx:1:7:
      1 │ import '~/utils/FirebaseAdmin';
        ╵        ~~~~~~~~~~~~~~~~~~~~~~~

  "sideEffects" is false in the enclosing "package.json" file

    package.json:6:2:
      6 │   "sideEffects": false,
        ╵   ~~~~~~~~~~~~~

✘ [ERROR] [plugin server-bare-modules] Package subpath './package.json' is not defined by "exports" in /Users/jason/Projects/remix-firebase-admin/node_modules/firebase-admin/package.json

    node_modules/@remix-run/dev/compiler/plugins/serverBareModulesPlugin.js:125:32:
      125 │   let packageJsonFile = require.resolve(`${packageName}/package.j...
          ╵                                 ^

    at new NodeError (node:internal/errors:371:5)
    at throwExportsNotFound (node:internal/modules/esm/resolve:453:9)
    at packageExportsResolve (node:internal/modules/esm/resolve:729:3)
    at resolveExports (node:internal/modules/cjs/loader:482:36)
    at Function.Module._findPath (node:internal/modules/cjs/loader:522:31)
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:919:27)
    at Function.resolve (node:internal/modules/cjs/helpers:108:19)
    at warnOnceIfEsmOnlyPackage (/Users/jason/Projects/remix-firebase-admin/node_modules/@remix-run/dev/compiler/plugins/serverBareModulesPlugin.js:125:33)
    at /Users/jason/Projects/remix-firebase-admin/node_modules/@remix-run/dev/compiler/plugins/serverBareModulesPlugin.js:95:11
    at callback (/Users/jason/Projects/remix-firebase-admin/node_modules/esbuild/lib/main.js:920:34)

  This error came from the "onResolve" callback registered here:

    node_modules/@remix-run/dev/compiler/plugins/serverBareModulesPlugin.js:46:12:
      46 │       build.onResolve({
         ╵             ~~~~~~~~~

    at setup (/Users/jason/Projects/remix-firebase-admin/node_modules/@remix-run/dev/compiler/plugins/serverBareModulesPlugin.js:46:13)
    at handlePlugins (/Users/jason/Projects/remix-firebase-admin/node_modules/esbuild/lib/main.js:842:23)

  The plugin "server-bare-modules" was triggered by this import

    app/utils/FirebaseAdmin.ts:1:58:
      1 │ ...licationDefault, getApp, initializeApp } from 'firebase-admin/app';
        ╵                                                  ~~~~~~~~~~~~~~~~~~~~

Build failed with 1 error:
node_modules/@remix-run/dev/compiler/plugins/serverBareModulesPlugin.js:125:32: ERROR: [plugin: server-bare-modules] Package subpath './package.json' is not defined by "exports" in /Users/jason/Projects/remix-firebase-admin/node_modules/firebase-admin/package.json
💿 Built in 465ms

I have also tried to change package.json to include sideEffects: true but it just removes the error about that particular change and still produces the other errors.
The weird thing is that I've tried to install 1.3.4 and it produces the same error.  However, I've got another project that I started a week ago that uses 1.3.4 and doesn't produce any errors.

So I was finally able to track this down and it all stems from firebase-admin not export package.json.
exports: {
....
"./package.json": "./package.json"
}

Doing this fixes the errors. However, I'm not sure why it all of sudden broke when the two have been working fine over the last few weeks.

1.3.5 introduced a bug that should be fixed in the upcoming release. Can you try the experimental release mentioned in #2691 and tell us if it fixes your issue?


x4 Upscaling inference time

Hi,
is 38 seconds normal for the upscaling model to run?
How fast do you expect it to run on a V100?

try https://www.deepspeed.ai/inference/


-t overshadowed by jekyll built-in -t

-t is already claimed by the --trace option. We should choose another short flag or remove it, since it doesn't work as documented.

I'm thinking -m --markup would be good. We could also use either -e or -x with --extension, or just drop -t and leave the --type long flag.

I like both!

Fixed in eca6e26ad995ac7bc51fa0ea3b7d192ee6557f05


Update or remove What's New? section in README.md

This section is out-of-date: https://github.com/instructlab/instructlab?tab=readme-ov-file#-whats-new
Should be updated or removed (not sure what the original motivation here was)

I can work on this


make memcached an optional dependency

This PR does:

rename titiler.db submodule to titiler.cache
make memcached an optional requirements
move get_cache from titiler.utils to titiler.dependencies
simplify cache method (get/set) to enable more cache options (not just imagery)

Nope let's get rid of caching!
Will add an example how to implement caching at app level later


Port to NAN

:+1:

You are now my favorite person @zhangyuanwei :)
I'll take a look trough this and merge it in ASAP. Thanks a ton for the work

Thanks again for doing this work!
It's not clear to me why yet, but there's something wrong with the module after your change (and maybe before? not sure...)
If you run the sample app in the examples directory, you can probably hear the audio dropping out. I'm very low on time (as evidenced by how long it took for me to respond), but I might be able to check it out at some point.

Actually I had setup a bad audio configuration, and I believe things are working. :+1:


[#804] OPTIONS request mocking support

Initial commit for OPTIONS request mocking. Does not work yet, throwing:
TypeError: this.pretender[verb] is not a function

When options is trying to get mocked.

Looks like Pretender supports OPTIONS.
Regarding the shorthand handler, I agree it should have its own handler. Should there even be a shorthand for OPTIONS? What would the behavior be?
Perhaps we can start with just adding the verb, and letting users use the function handler, e.g.
this.options('/some/url', () => {
  // normal function handler response
});

@samselikoff I developed a PR but it looks too similar to this one to add it to the repo. the sad part though is that neither seems to address allowing a passthrough of a OPTIONS & POST pairing.

Ok, my last comment is a bit misleading. I had in earlier testing removed the "options" from the my config.js. Now that it is correct to read:
this.passthrough('https://www.googleapis.com/identitytoolkit/v3/relyingparty/verifyPassword', ['post', 'head', 'options']);

I'm back to my state from yesterday where it is fails on the "options" verb of the pretender object:
https://github.com/samselikoff/ember-cli-mirage/blob/master/addon/server.js#L179

Sorry to be so verbose but ... another update ...
I switched the URL to a shortened version with wildcard characters:
this.passthrough('https://www.googleapis.com/**', ['post', 'head', 'options']);

this DOES work with this PR. 👍

Any chance we could merge this in? even with the fully qualified URL it is an improvement I think.

I need to fix the style validation errors and see what else is failing. Either way you can use a git commit as the version in package.json if you just want to use it now :)
git+https://github.com/riklaunim/ember-cli-mirage.git#abae084fe2046648a7b26b31e49df2841c9f90fb

should do the trick.

yup @riklaunim that's what I'm doing for now. glad you got to this 18 days before me. :) Thanks for the PR.
One last note, working off your code base I noticed that even though my shortened URL works the passthrough call will fail when explicitly asking for 'options'.

@riklaunim in fact I can't use yours yet as it fails on the same line as it was with base ember-cli-mirage. I had added one piece of defensive code into my clone of your PR:
verbs.forEach(verb => {
  paths.forEach(path => {
    let fullPath = this._getFullPath(path);
    if(this.pretender[verb]) {
      this.pretender[verb](fullPath, this.pretender.passthrough);
    } else {
      console.warn(`Call to a non-existant pretender method: "${verb}". Pretender is: `, this.pretender);
    }
  });
});

Not sure whether this is worth having in the final code once everything is sorted but it does get this to working.

Well, I was wondering why Pretender doesn't have my options and other changes visible. Turns out the installed dependency isn't the one that is being used (that's from a docker container):
./bower_components/pretender/pretender.js
./node_modules/ember-cli-mirage/node_modules/pretender/pretender.js

node_modules/ember-cli-mirage/node_modules/pretender/pretender.js is used and not the version I install with my project as ./bower_components/pretender/pretender.js
And Pretender seems to need this https://github.com/pretenderjs/pretender/pull/166 to work. When I added that to the used pretender.js file - options do mock:
this.options('/campaigns', function () {
      return .....;
});

@riklaunim got a bit confused on your npm versus bower Pretender versions comment. I'd expect that Mirage is only using the npm version but I think that's what you're saying. Anyway, glad to see your PR on Pretender as I pretty sure it had to originate from there based on what we were seeing hanging off the Pretender object. Sounds like you've nailed that.

One other dimension to this that I've now noticed, is that as soon as I add the passthrough to my config.js this somehow interferes with Mirage using my scenarios/default.js which is loading my fixtures and factories. It's very reproducible but haven't had time to dig into one might effect the other.
@samselikoff does anything jump out at you WRT to this?

installing ember-cli-mirate adds pretender to bower dependencies so I expected it will use it from bower_components or if its want it in node_modules then it will be in node_modules and not /node_modules/subfolder/node_modules/ -- which is pretty hidden.

Oh yes that is confusing. @samselikoff is there a reason for this?

btw, removing my above comment until I can dig into it a bit further ... it's not as reproducible as i thought 😬

@riklaunim I have forked your PR and pointed to your Pretender PR in the package.json so I get the full end-to-end effect. Works. I can send you the PR if you want but I'm guessing you'd prefer to keep these two PR separate even though the Mirage PR depends on the Pretender one.

I can confirm though that a side effect does seem to be introduced. When I use this PR paired with the Pretender PR, I get no errors but Mirage does not use my config/default.js configuration and therefore fixtures and factories are not used.
Use Case 1: PR breaks scenarios
Use Case 2: PR solves options problem
So to be clear, use case 1a:

using published Mirage 0.2.1
remove all passthrough configuration in mirage/config.js ... without which no OPTIONS calls will be made
load an application page who's model ('forecast') has an associated fixture associated with it
the GET /forecasts request results in the expected 80 rows that come from the fixture
no error, expected outcome

Use case 1b:

Use this PR alongside the Pretender PR
exact same setup as 1a, outcome though is different ... no error, just no results

Use Case 2a:

using default Mirage 0.2.1
go to a page where POST https://www.googleapis.com is called (and indirectly the OPTIONS call)
add passthrough --this.passthrough('https://www.googleapis.com/**', ['post', 'head', 'options']); -- to mirage/config.js.
immediately fails on any page with the above mentioned "_this.pretender[verb] is not a function" error

Use Case 2b:

using Mirage and Pretender PR's (see link)
No error, network request goes out as expected ... desired behaviour.

Pretender needs to merge the PR and push a new version, then this can use it and not a github commit (which would be pretty odd for a production release).

yes that was my point 👍
I just did the fork for my immediate needs of seeing the two together.

the issue above does need addressing though as Mirage will not work correctly without addressing this

I use it with a big client panel demo and it works. If the are problems - test should show them too - when the verb problem is solved by newer pretender.

so you're loading fixtures and/or factories to initialise your state?

Mostly factories, few custom responses. I have some passthrough in another project, can check it too.

would you let me know how that comes out? I have to shift to a different project for a day but if you're not seeing this behaviour I'll dig into mine again and see what else could be causing it.

Tested, works.

I'd love the tl;dr from your convo & experiments - what should our next steps be here? Are we blocked by the Pretender pr?

At least some tests won't pass as Pretender.options does not exist. Then there may be some other options tests for fixing. It's also odd that node_modules/ember-cli-migrage/node_modules/.... subfolders shows up with Pretender - and not just the one in bower_components. I had to hand modify the Pretender code there instead of getting it from a git version in bower dependencies.
I'll see about the Pretender additional tests, then see those tests here.

Awesome, thank you. So we should hold off on this PR until those are sorted out, right?

Now fixture tests fail for some reason.

You have some failures, are your tests passing locally?

nop, as I commented above - few fixture related tests fail and I don't why.

Can you help me with this? It seems like even adding options to the list - https://github.com/samselikoff/ember-cli-mirage/pull/841/commits/14523a7d52163e9f6dd44acb4fd989f766e40bd6#diff-3da129bcd0b0367d1b65b28e9ecc34c9 - causes the fixtures tests to fail. For some reason visit() return 404 - like if some mock or something stopped working.

Closing due to inactivity


git: add generic backend implementation for reading git config

prerequisites for https://github.com/iterative/scmrepo/pull/278

Codecov Report
Attention: 36 lines in your changes are missing coverage. Please review.

Files
Coverage Δ

src/scmrepo/git/__init__.py
85.57% <100.00%> (+0.09%)
:arrow_up:

src/scmrepo/git/backend/base.py
81.94% <100.00%> (+0.78%)
:arrow_up:

src/scmrepo/git/config.py
100.00% <100.00%> (ø)

tests/test_git.py
100.00% <100.00%> (ø)

src/scmrepo/git/backend/dulwich/__init__.py
77.35% <71.87%> (-1.36%)
:arrow_down:

src/scmrepo/git/backend/gitpython.py
64.11% <25.00%> (-2.15%)
:arrow_down:

src/scmrepo/git/backend/pygit2/__init__.py
70.54% <53.84%> (-3.18%)
:arrow_down:

... and 4 files with indirect coverage changes
:loudspeaker: Thoughts on this report? Let us know!


[1.12.2] Fueling Station crashes when inserting Forestry Cans

Minecraft Version: 1.12.2
Forge Version: <IP_ADDRESS>5
LibVulpes Version: 0.2.6
Advanced Rocketry Version: 1.2.3
Crash Report: https://pastebin.com/yJG4mLsQ
Putting Forestry Cans filled with Rocket Fuel into the Fueling Station causes the game to crash.
My guess is that it doesn't properly handle the fact that Cans don't give an item when emptied.

I think your guess is spot on


Rename basics Concept Exercises to use story/theme

In the beginning of v3 development, Concept Exercises were named after their Concepts. However, we've later on changed this to have the Concept Exercises be named after their story/theme.
The basics Concept Exercise should be updated to use a story/theme-based name and slug.
See https://github.com/exercism/v3-launch/issues/49

Seems straightforward enough, I'll like to try this as my first issue


Confidence on training NLU model is 0 for most intents

Rasa version: rasa-core                     0.14.1
rasa-core-sdk                0.14.0
rasa-nlu                      0.15.0
Python version: 3.6.8
Operating system (windows, osx, ...): Linux 18.04.1
Issue:
I'm building a model which allows users' to be able to check the price of various airlines through the chatbot I am training my RASA NLU model on 5 intents and proving some training data for each. However, the confidence score for many of the intents post NLU training is still 0. Is there something I am doing wrong?
Content of configuration file (config.yml):
language: "en"
pipeline:

name : "nlp_spacy"
name: "tokenizer_whitespace"
name: "intent_entity_featurizer_regex"
name: "ner_crf"
name: "ner_synonyms"
name: "intent_featurizer_count_vectors"
name: "intent_classifier_tensorflow_embedding"
intent_tokenization_flag: true
intent_split_symbol: "+" `

Content of domain file (domain.yml) (if used & relevant):
- greeting
- flight
- inform
- affirmation
- deny

entities:
- location
- date

slots:
   from:
            type: text
   to:
            type: text
   date:
            type: text

actions:
- utter_greeting
- utter_boarding
- utter_destination
- utter_date
- utter_confirm
- utter_check_another_one
- utter_thanks
- utter_unclear
- action_save_origin
- action_save_destination
- action_save_date
- action_get_flight
- action_slot_reset

templates:
  utter_greeting:
  - text: "hello!"

  utter_boarding:
  - text: "We'll help you find the latest flight schedule. First, please provide your origin airport code?"

  utter_destination:
  - text: "And the destination airport code?"

  utter_date:
  - text: "What is the date for your travel(in dd-mm-yyyy)?"

  utter_confirm:
  - text: "I will be making inquiry for flight from {from} to {to} on {date}. Is that correct?"

  utter_check_another_one:
  - text: "Do you want to make another inquiry?"

  utter_thanks:
  - text: "Thanks for contacting us. Have a good day!"

-Nice to meet you.
-How do you do?
-Hi, nice to meet you.
-It is a pleasure to meet you.
-Top of the morning to you!
-What's up?

## intent:flight
-hey! I want latest flight schedule
-can you provide me flight schedule
-i want the flight schedule
-i want to know the flight schedule
-what is the flight schedule?
-give me some flight information
-i need information about a few flights
-i need information on a flight
-i need to know about a flight
-can you tell me fligh prices?
-please tell me flight prices
-please provide latest flight info
-is it possible to get latest flight information
-flight schedule
-flight information
-flight info

## intent:inform
-[DEL](location)
-[BOM](location)
-[CCU](location)
-[BLR](location)
-[HYD](location)
-[MAA](location)
-[PNQ](location)
-[IXC](location)
-[09-01-2019](date)
-[20-05-2019] (date)
- I want for [09-02-2019](date)
- i want to travel on [21-04-2019](date)

## intent:affirmation
-ok
-yeah
-yes
-definitely
-ya
-yup
-exactly
-right
-definitely
-absolutely
-certainly
-exactly
-right
-affirmative
-yes to that
-correct
-yep
-yes sir
-si
-correcto
-allright
-i agree
-that is correct
-that is right
-you got that
-yes that is right
-yup that is correct
-yeah that is right
-sounds good

## intent:deny
-no
-not yet
-never
-not now
-nope
-nah
-na
-wrong
-negative
-not correct
-incorrect
-no sir
-dont agree on that
-didnt meant that
-dont mean that
-not what i want
-not correct
-bad
-im not ok with that
-not good
-that is wrong
-im not good with that
-ok its not fine
-definitely no
-not good for me
-its not ok
-its not correct

**Content of CORE data file (stories.md)**

## fallback
- utter_unclear

## Story 1
* greeting
    -utter_greeting
* flight
    - utter_boarding
* inform{"location": "BOM"}
    - action_save_origin
    - slot{"from": "BOM"}
    - utter_destination
* inform{"location": "DEL"}
    - action_save_destination
    - slot{"to": "DEL"}
    - utter_date
* inform{"date": "20-01-2019"}
    - action_save_date
    - slot{"date": "20-01-2019"}
    - utter_confirm
* affirmation
    - action_get_flight
	- utter_check_another_one
* deny
	- utter_thanks
	- action_restart

## Story 2-multiple steps
* greeting
    -utter_greeting
* flight
    - utter_boarding
* inform{"location": "CCU"}
    - action_save_origin
    - slot{"from": "CCU"}
    - utter_destination
* inform{"location": "BLR"}
    - action_save_destination
    - slot{"to": "BLR"}
    - utter_date
* inform{"date": "03-02-2019"}
    - slot{"date": "03-02-2019"}
    - action_save_date
    - slot{"date": "03-02-2019"}
    - utter_confirm
* affirmation
    - action_get_flight
    - utter_check_another_one
* affirmation
	- action_slot_reset
	- reset_slots
    - utter_boarding
* inform{"location": "BOM"}
    - action_save_origin
    - slot{"from": "BOM"}
    - utter_destination
* inform{"location": "DEL"}
    - action_save_destination
    - slot{"to": "DEL"}
    - utter_date
* inform{"date": "10-02-2019"}
    - slot{"date": "10-02-2019"}
    - action_save_date
    - slot{"date": "10-02-2019"}
    - utter_confirm
* affirmation
    - action_get_flight
    - utter_check_another_one
* deny
    - utter_thanks
    - action_restart

Thanks for raising this issue, @Ghostvv  will get back to you about it soon.

even those from training data?

Solved this issue.. I'm facing another problem now. I am trying the Berlin Rasa Workshop project uploaded on your Git. (https://github.com/RasaHQ/rasa-workshop-pydata-berlin)
The issue that I'm facing is that while testing my NLU model, it is supposed to show the performance metrics for F1 score, precision, recall and a confusion matrix too, instead it shows everything in the form of a Dictionary/Json format making it easy to interpret the output.
I've attached screenshots for reference. (RASA.png is my implementation while the other is from the Berlin workshop notebook)
Do i need to convert the dictionary to some other format and then plot it? TIA.

Since original issue is resolved, I'll close it, please create a separate issue in the corresponding GitHub repo


[AD] SP/Group list commands never seem to complete

Running az ad sp list or az ad group list seem to hang, and I've never seen either one actually complete. When I add the --debug flag, it appears like they're just continuously pinging the server, even though they seem to be getting 200 responses back.

@lostintangent, the result is paged, and command is trying to grab all items before display it. This will take a long time particularly you are in microsoft tenant.
We are looking at whether we can start to display it before reach to the end

Same with #1150