RawKeyboard listener not working as expected when holding a key on Android

RawKeyboard listener don't seem to produce the correct behavior when a key is hold down, the callback keeps getting called with key down and key up events, even when the key is not released yet. I have tested on beta and master channel.
Steps to Reproduce

Run flutter create bug.
Update the main method to the following code:

void main() {
  WidgetsFlutterBinding.ensureInitialized();
  RawKeyboard.instance.addListener((e) {
    print(e);
  });
  runApp(MyApp());
}

Expected results:
When I hold a key down, it should print a key down event and when I release the key, a key up should be printed
Actual results:
Multiple key up and key downs are printed one after another as long as the key is pressed, like this log below:
I/flutter (27288): RawKeyDownEvent#d8ba9(logicalKey: LogicalKeyboardKey#00061(keyId: "0x00000061", keyLabel: "a", debugName: "Key A"), physicalKey: PhysicalKeyboardKey#70004(usbHidUsage: "0x00070004", debugName: "Key A"))
I/flutter (27288): RawKeyUpEvent#d1186(logicalKey: LogicalKeyboardKey#00061(keyId: "0x00000061", keyLabel: "a", debugName: "Key A"), physicalKey: PhysicalKeyboardKey#70004(usbHidUsage: "0x00070004", debugName: "Key A"))
I/flutter (27288): RawKeyDownEvent#90489(logicalKey: LogicalKeyboardKey#00061(keyId: "0x00000061", keyLabel: "a", debugName: "Key A"), physicalKey: PhysicalKeyboardKey#70004(usbHidUsage: "0x00070004", debugName: "Key A"))
I/flutter (27288): RawKeyUpEvent#91e0c(logicalKey: LogicalKeyboardKey#00061(keyId: "0x00000061", keyLabel: "a", debugName: "Key A"), physicalKey: PhysicalKeyboardKey#70004(usbHidUsage: "0x00070004", debugName: "Key A"))
I/flutter (27288): RawKeyDownEvent#2fcef(logicalKey: LogicalKeyboardKey#00061(keyId: "0x00000061", keyLabel: "a", debugName: "Key A"), physicalKey: PhysicalKeyboardKey#70004(usbHidUsage: "0x00070004", debugName: "Key A"))

Logs
[✓] Flutter (Channel master, 1.26.0-2.0.pre.103, on macOS 11.0.1 20B29 darwin-x64, locale pt-BR)
    • Flutter version 1.26.0-2.0.pre.103 at /Users/erick.zanardo/flutter
    • Framework revision 32741c0ec8 (17 hours ago), 2020-12-21 18:34:02 -0600
    • Engine revision af6889a600
    • Dart version 2.12.0 (build 2.12.0-169.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/erick.zanardo/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = /Users/erick.zanardo/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.1, Build version 12A7403
    • CocoaPods version 1.10.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] IntelliJ IDEA Community Edition (version 2020.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] Connected device (2 available)
    • AOSP on IA Emulator (mobile) • emulator-5554 • android-x86    • Android 9 (API 28) (emulator)
    • Chrome (web)                 • chrome        • web-javascript • Google Chrome 87.0.4280.88

• No issues found!

Issue replicable on latest master. Tapping on key is logging keyUp and keyDown events simultaneously.
I/flutter (21298): RawKeyDownEvent#43916(logicalKey: LogicalKeyboardKey#700e1(keyId: "0x1000700e1", keyLabel: "", debugName: "Shift Left"), physicalKey: PhysicalKeyboardKey#00000(usbHidUsage: "0x00000000", debugName: "None"))
I/flutter (21298): RawKeyUpEvent#4ab6f(logicalKey: LogicalKeyboardKey#700e1(keyId: "0x1000700e1", keyLabel: "", debugName: "Shift Left"), physicalKey: PhysicalKeyboardKey#00000(usbHidUsage: "0x00000000", debugName: "None"))
I/flutter (21298): RawKeyDownEvent#9c971(logicalKey: LogicalKeyboardKey#7002a(keyId: "0x10007002a", keyLabel: "", debugName: "Backspace"), physicalKey: PhysicalKeyboardKey#00000(usbHidUsage: "0x00000000", debugName: "None"))
I/flutter (21298): RawKeyUpEvent#7927c(logicalKey: LogicalKeyboardKey#7002a(keyId: "0x10007002a", keyLabel: "", debugName: "Backspace"), physicalKey: PhysicalKeyboardKey#00000(usbHidUsage: "0x00000000", debugName: "None"))
I/flutter (21298): RawKeyDownEvent#821c2(logicalKey: LogicalKeyboardKey#700e1(keyId: "0x1000700e1", keyLabel: "", debugName: "Shift Left"), physicalKey: PhysicalKeyboardKey#00000(usbHidUsage: "0x00000000", debugName: "None"))
I/flutter (21298): RawKeyUpEvent#8b8f6(logicalKey: LogicalKeyboardKey#700e1(keyId: "0x1000700e1", keyLabel: "", debugName: "Shift Left"), physicalKey: PhysicalKeyboardKey#00000(usbHidUsage: "0x00000000", debugName: "None"))
I/flutter (21298): RawKeyDownEvent#9af4a(logicalKey: LogicalKeyboardKey#700e1(keyId: "0x1000700e1", keyLabel: "", debugName: "Shift Left"), physicalKey: PhysicalKeyboardKey#00000(usbHidUsage: "0x00000000", debugName: "None"))
I/flutter (21298): RawKeyUpEvent#ae4f1(logicalKey: LogicalKeyboardKey#700e1(keyId: "0x1000700e1", keyLabel: "", debugName: "Shift Left"), physicalKey: PhysicalKeyboardKey#00000(usbHidUsage: "0x00000000", debugName: "None"))
I/flutter (21298): RawKeyDownEvent#683aa(logicalKey: LogicalKeyboardKey#7002a(keyId: "0x10007002a", keyLabel: "", debugName: "Backspace"), physicalKey: PhysicalKeyboardKey#00000(usbHidUsage: "0x00000000", debugName: "None"))
I/flutter (21298): RawKeyUpEvent#3ebb1(logicalKey: LogicalKeyboardKey#7002a(keyId: "0x10007002a", keyLabel: "", debugName: "Backspace"), physicalKey: PhysicalKeyboardKey#00000(usbHidUsage: "0x00000000", debugName: "None"))
I/flutter (21298): RawKeyDownEvent#a00ae(logicalKey: LogicalKeyboardKey#7002a(keyId: "0x10007002a", keyLabel: "", debugName: "Backspace"), physicalKey: PhysicalKeyboardKey#00000(usbHidUsage: "0x00000000", debugName: "None"))
I/flutter (21298): RawKeyUpEvent#94426(logicalKey: LogicalKeyboardKey#7002a(keyId: "0x10007002a", keyLabel: "", debugName: "Backspace"), physicalKey: PhysicalKeyboardKey#00000(usbHidUsage: "0x00000000", debugName: "None"))
I/flutter (21298): RawKeyDownEvent#d84ea(logicalKey: LogicalKeyboardKey#7002a(keyId: "0x10007002a", keyLabel: "", debugName: "Backspace"), physicalKey: PhysicalKeyboardKey#00000(usbHidUsage: "0x00000000", debugName: "None"))
I/flutter (21298): RawKeyUpEvent#53d3c(logicalKey: LogicalKeyboardKey#7002a(keyId: "0x10007002a", keyLabel: "", debugName: "Backspace"), physicalKey: PhysicalKeyboardKey#00000(usbHidUsage: "0x00000000", debugName: "None"))

flutter doctor -v
[✓] Flutter (Channel master, 1.26.0-2.0.pre.117, on Mac OS X 10.15.4 19E2269 darwin-x64, locale
    en-IN)
    • Flutter version 1.26.0-2.0.pre.117 at /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision 15c009b805 (6 hours ago), 2020-12-22 20:09:03 -0500
    • Engine revision b7cd3f8e70
    • Dart version 2.12.0 (build 2.12.0-173.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS (Xcode 12.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.0.1, Build version 12A7300
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds
        to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see https://guides.cocoapods.org/using/getting-started.html#installation for
      instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.51.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.16.0

[✓] Connected device (3 available)
    • SM A260G (mobile) • 5200763ebcfa861f • android-arm    • Android 8.1.0 (API 27)
    • macOS (desktop)   • macos            • darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)      • chrome           • web-javascript • Google Chrome 87.0.4280.88

! Doctor found issues in 1 category.

May be similar / related to : https://github.com/flutter/flutter/issues/70020

cc @gspencergoog

I am trying to look on this issue, and I discovered where this behavior originates, I discovered that this simultaneously triggering of the events happens on the dispatchKeyEvent of the FlutterView class.
I have made a small native android example to test, and it seems that this behavior that we are seeing, is indeed how the android behaves on that method, this is the code I made to test:
package com.example.mykeyboardexample

import android.os.Bundle
import android.util.Log
import android.view.KeyEvent
import androidx.appcompat.app.AppCompatActivity

class MainActivity : AppCompatActivity() {

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
    }

    override fun dispatchKeyEvent(event: KeyEvent?): Boolean {
        val type = if (event?.action == KeyEvent.ACTION_DOWN) "Down" else "Up";
        Log.d("AAAA",  " ${event?.keyCode} ${type} ${event?.repeatCount.toString()}");
        return super.dispatchKeyEvent(event)
    }
}

And the output on logcat is pretty much what we are seeing on Flutter
2020-12-23 16:40:02.939 28917-28917/com.example.mykeyboardexample D/AAAA:  29 Down 0
2020-12-23 16:40:02.942 28917-28917/com.example.mykeyboardexample D/AAAA:  29 Up 0
2020-12-23 16:40:06.231 28917-28917/com.example.mykeyboardexample D/AAAA:  29 Down 0
2020-12-23 16:40:06.232 28917-28917/com.example.mykeyboardexample D/AAAA:  29 Up 0
2020-12-23 16:40:06.731 28917-28917/com.example.mykeyboardexample D/AAAA:  29 Down 0
2020-12-23 16:40:06.732 28917-28917/com.example.mykeyboardexample D/AAAA:  29 Up 0
2020-12-23 16:40:06.815 28917-28917/com.example.mykeyboardexample D/AAAA:  29 Down 0
2020-12-23 16:40:06.816 28917-28917/com.example.mykeyboardexample D/AAAA:  29 Up 0
2020-12-23 16:40:06.899 28917-28917/com.example.mykeyboardexample D/AAAA:  29 Down 0
...

I am going to continue investigating this and will report if I find anything new.

I did further investigation, and I discovered that when testing on a real device, this runs as expected  (my first tests were executed on an emulator), I have connected a bluetooth keyboard on a real device and now when I press down and hold a key, a get various key down events with the correct repeat count, but only once I release the key I get a key up event. This is the log of my test on a real device with a bluetooth keyboard:
I/flutter (19754): Up - Repeat: 0
I/flutter (19754): Down - Repeat: 0
I/flutter (19754): Down - Repeat: 1
I/flutter (19754): Down - Repeat: 2
I/flutter (19754): Down - Repeat: 3
I/flutter (19754): Down - Repeat: 4
...
I/flutter (19754): Up - Repeat: 0

For that test I have updated my step to reproduce code to only print if it is a key down or up and the repeat count.
So I am confident that this is not an issue with flutter, but an issue with Android Emulators. Before closing this, I just wonder if we should add any hint about this weird behavior of android emulators somewhere in the docs?

Emulators are already pretty well known to have many differences from actual hardware, especially where input is concerned. It wouldn't hurt to add a comment in the docs explaining that, though.

Emulators are already pretty well known to have many differences from actual hardware, especially where input is concerned. It wouldn't hurt to add a comment in the docs explaining that, though.

I also can reproduce this issue on the latest stable and master channels with Android Emulator. As above investigation and comments, I'm going to update appropriate labels for this issue.

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.3.10, on macOS 13.0.1 22A400 darwin-x64, locale en-VN)
    • Flutter version 3.3.10 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 135454af32 (13 hours ago), 2022-12-15 07:36:55 -0800
    • Engine revision 3316dd8728
    • Dart version 2.18.6
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5591.52/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.73.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.54.0

[✓] Connected device (3 available)
    • SM T225 (mobile) • R9JT3004VRJ • android-arm64  • Android 12 (API 31)
    • macOS (desktop)  • macos       • darwin-x64     • macOS 13.0.1 22A400 darwin-x64
    • Chrome (web)     • chrome      • web-javascript • Google Chrome 108.0.5359.124

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[!] Flutter (Channel master, 3.7.0-13.0.pre.92, on macOS 13.0.1 22A400 darwin-x64, locale en-VN)
    • Flutter version 3.7.0-13.0.pre.92 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 4e08ebb2bf (2 hours ago), 2022-12-27 19:31:24 -0500
    • Engine revision 8294e2693a
    • Dart version 3.0.0 (build 3.0.0-66.0.dev)
    • DevTools version 2.20.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14B47b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Users/huynq/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5591.52/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.74.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.56.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • macOS 13.0.1 22A400 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 108.0.5359.124

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.


incorrect croppedAreaPixels when restrictPosition is true and original image is smaller than cropSize

Describe the bug
incorrect croppedAreaPixels when restrictPosition is true and original image is smaller than cropSize.
When restrictPosition is false, this issue won't exist.
To Reproduce
Steps to reproduce the behavior:

Go to https://codesandbox.io/s/patient-smoke-kxduw2
Click choose file to choose a image which is smaller than cropSize { width: 200, height: 100}
see the width or height of original image is always > croppedAreaPixels
Expected behavior
width and height of original image is always === croppedAreaPixels

From what I see the croppedAreaPixels width and height are matching the actual original size. I think this is the correct behavior.
To be transparent, I've never actually used the cropSize property and I believe it should be avoided.  See https://github.com/ValentinH/react-easy-crop/issues/186


added staline.nvim to the statusline list.

Adding tamton-aquib/staline.nvim to the statusline list.

Thank you @tamton-aquib ! Looks cool


Add compound item check in repo item tab

Add compound item check in repo item tab - We won't initially allow the use of repo compound object

Added check for compound objects and provide message for user.


don't process math blocks

Would it be possible to have an extension that doesn't process math blocks (that could be rendered by mathjax afterwards) ?

Could you please add some example?

@dikmax
There are a couple of places where LaTeX math blocks and markdown are conflicting. I think the best would be to have an extension that doesn't process anything between:
$ 1+1 = 2 $

$$ 1+1 = 2 $$

\( 1+1 = 2 \)

\[ 1+1 = 2 \]

This is an example where things go wrong:

Also braces are eaten up:

I'll surely make math extension at least with $ and $$ as delimiters. I'll take pandoc description, but I'm not sure about \[ and \(, because it breaks links escaping.

@dikmax that would be great.
Would like to have also \[ and \( but I see that this really breaks markdown normal behaviour (although maybe in practice people rarely escape links).

Fixed in 0.7.4.
Both syntaxes are supported by enabling different extensions. Look README for more details.

@dikmax awesome, thank you!


Datadog agents running on centos6/7 getting TLS handshake timeout issue

Agent-Status
Getting the status from the agent.

===============
Agent (v7.32.1)
===============

  Status date: 2021-12-08 05:15:11.738 EST / 2021-12-08 10:15:11.738 UTC<PHONE_NUMBER>738)
  Agent start: 2021-12-08 04:26:52.655 EST / 2021-12-08 09:26:52.655 UTC<PHONE_NUMBER>655)
  Pid: 27344
  Go Version: go1.16.7
  Python Version: 3.8.11
  Build arch: amd64
  Agent flavor: agent
  Check Runners: 4
  Log Level: info

  Paths
  =====
    Config File: /etc/datadog-agent/datadog.yaml
    conf.d: /etc/datadog-agent/conf.d
    checks.d: /etc/datadog-agent/checks.d

  Clocks
  ======
    NTP offset: -21m18.524226s
    NTP offset is high. Datadog may ignore metrics sent by this Agent.
    System time: 2021-12-08 05:15:11.738 EST / 2021-12-08 10:15:11.738 UTC<PHONE_NUMBER>738)

  Host Info
  =========
    bootTime: 2021-11-18 03:13:54 EST / 2021-11-18 08:13:54 UTC<PHONE_NUMBER>000)
    kernelArch: x86_64
    kernelVersion: 3.10.0-862.el7.x86_64
    os: linux
    platform: centos
    platformFamily: rhel
    platformVersion: 7.9.2009
    procs: 105
    uptime: 481h13m5s

  Hostnames
  =========
    hostname: sc**********
    socket-fqdn: sc****************
    socket-hostname: sc***********
    hostname provider: os
    unused hostname providers:
      aws: not retrieving hostname from AWS: the host is not an ECS instance and other providers already retrieve non-default hostnames
      azure: azure_hostname_style is set to 'os'
      configuration/environment: hostname is empty
      gce: unable to retrieve hostname from GCE: Get "http://<IP_ADDRESS>/computeMetadata/v1/instance/hostname": dial tcp <IP_ADDRESS>:80: connect: network is unreachable

  Metadata
  ========
    hostname_source: os

=========
Collector
=========

  Running Checks
  ==============

    cpu
    ---
      Instance ID: cpu [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/cpu.d/conf.yaml.default
      Total Runs: 193
      Metric Samples: Last Run: 9, Total: 1,730
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2021-12-08 05:14:57 EST / 2021-12-08 10:14:57 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-12-08 05:14:57 EST / 2021-12-08 10:14:57 UTC<PHONE_NUMBER>000)

    disk (4.4.0)
    ------------
      Instance ID: disk:e5dffb8bef24336f [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/disk.d/conf.yaml.default
      Total Runs: 193
      Metric Samples: Last Run: 108, Total: 20,844
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 23ms
      Last Execution Date : 2021-12-08 05:15:04 EST / 2021-12-08 10:15:04 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-12-08 05:15:04 EST / 2021-12-08 10:15:04 UTC<PHONE_NUMBER>000)

    file_handle
    -----------
      Instance ID: file_handle [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/file_handle.d/conf.yaml.default
      Total Runs: 193
      Metric Samples: Last Run: 5, Total: 965
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2021-12-08 05:15:11 EST / 2021-12-08 10:15:11 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-12-08 05:15:11 EST / 2021-12-08 10:15:11 UTC<PHONE_NUMBER>000)

    io
    --
      Instance ID: io [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/io.d/conf.yaml.default
      Total Runs: 193
      Metric Samples: Last Run: 65, Total: 12,500
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2021-12-08 05:15:03 EST / 2021-12-08 10:15:03 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-12-08 05:15:03 EST / 2021-12-08 10:15:03 UTC<PHONE_NUMBER>000)

    load
    ----
      Instance ID: load [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/load.d/conf.yaml.default
      Total Runs: 193
      Metric Samples: Last Run: 6, Total: 1,158
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2021-12-08 05:15:10 EST / 2021-12-08 10:15:10 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-12-08 05:15:10 EST / 2021-12-08 10:15:10 UTC<PHONE_NUMBER>000)

    memory
    ------
      Instance ID: memory [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/memory.d/conf.yaml.default
      Total Runs: 193
      Metric Samples: Last Run: 18, Total: 3,474
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2021-12-08 05:15:02 EST / 2021-12-08 10:15:02 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-12-08 05:15:02 EST / 2021-12-08 10:15:02 UTC<PHONE_NUMBER>000)

    network (2.4.0)
    ---------------
      Instance ID: network:d884b5186b651429 [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/network.d/conf.yaml.default
      Total Runs: 193
      Metric Samples: Last Run: 37, Total: 7,141
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 4ms
      Last Execution Date : 2021-12-08 05:15:09 EST / 2021-12-08 10:15:09 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-12-08 05:15:09 EST / 2021-12-08 10:15:09 UTC<PHONE_NUMBER>000)

    ntp
    ---
      Instance ID: ntp:d884b5186b651429 [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/ntp.d/conf.yaml.default
      Total Runs: 4
      Metric Samples: Last Run: 1, Total: 4
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 4
      Average Execution Time : 1.591s
      Last Execution Date : 2021-12-08 05:11:57 EST / 2021-12-08 10:11:57 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-12-08 05:11:57 EST / 2021-12-08 10:11:57 UTC<PHONE_NUMBER>000)

    uptime
    ------
      Instance ID: uptime [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/uptime.d/conf.yaml.default
      Total Runs: 193
      Metric Samples: Last Run: 1, Total: 193
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2021-12-08 05:15:01 EST / 2021-12-08 10:15:01 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2021-12-08 05:15:01 EST / 2021-12-08 10:15:01 UTC<PHONE_NUMBER>000)

========
JMXFetch
========

  Information
  ==================
  Initialized checks
  ==================
    no checks

  Failed checks
  =============
    no checks

=========
Forwarder
=========

  Transactions
  ============
    Cluster: 0
    ClusterRole: 0
    ClusterRoleBinding: 0
    CronJob: 0
    DaemonSet: 0
    Deployment: 0
    Dropped: 0
    HighPriorityQueueFull: 0
    Job: 0
    Node: 0
    PersistentVolume: 0
    PersistentVolumeClaim: 0
    Pod: 0
    ReplicaSet: 0
    Requeued: 94,687
    Retried: 6,174
    RetryQueueSize: 253
    Role: 0
    RoleBinding: 0
    Service: 0
    ServiceAccount: 0
    StatefulSet: 0

  Transaction Errors
  ==================
    Total number: 123
    Errors By Type:
      TLSErrors: 123

  API Keys status
  ===============
    API key ending with 456ed: Unable to validate API Key

==========
Endpoints
==========
  https://app.datadoghq.com - API Key ending with:
      - 456ed

==========
Logs Agent
==========

  Logs Agent is not running

=========
APM Agent
=========
  Status: Running
  Pid: 27346
  Uptime: 2898 seconds
  Mem alloc: 8,268,328 bytes
  Hostname: sc-sretest-01
  Receiver: localhost:8126
  Endpoints:
    https://trace.agent.datadoghq.com

  Receiver (previous minute)
  ==========================
    No traces received in the previous minute.
    Default priority sampling rate: 100.0%

  Writer (previous minute)
  ========================
    Traces: 0 payloads, 0 traces, 0 events, 0 bytes
    Stats: 0 payloads, 0 stats buckets, 0 bytes

=========
Aggregator
=========
  Checks Metric Sample: 51,105
  Dogstatsd Metric Sample: 23,041
  Event: 1
  Events Flushed: 1
  Number Of Flushes: 193
  Series Flushed: 52,927
  Service Check: 1,552
  Service Checks Flushed: 1,742
=========
DogStatsD
=========
  Event Packets: 0
  Event Parse Errors: 0
  Metric Packets: 23,040
  Metric Parse Errors: 0
  Service Check Packets: 0
  Service Check Parse Errors: 0
  Udp Bytes: 1,765,731
  Udp Packet Reading Errors: 0
  Udp Packets: 17,165
  Uds Bytes: 0
  Uds Origin Detection Errors: 0
  Uds Packet Reading Errors: 0
  Uds Packets: 0
  Unterminated Metric Errors: 0

**A number of my datadog agents are working fine but a few new installations and the agents which were restarted recently facing similar issues. Error logs attached.
2021-12-08 04:33:18 EST | CORE | ERROR | (pkg/forwarder/transaction/transaction.go:108 in func4) | TLS Handshake failure: net/http: TLS handshake timeout 2021-12-08 04:33:18 EST | CORE | ERROR | (pkg/forwarder/worker.go:183 in process) | Error while processing transaction: error while sending transaction, rescheduling it: Post "https://*-**-*-app.agent.datadoghq.com/intake/?api_key=******************************": net/http: TLS handshake timeout**

A new dd agent installation on centOS-6/centOS-7 machine is having this issue.

Hi @Suchit8 -- thanks for getting in touch!
DataDog support will be best able to help you with this issue.


3.4.1

Far from ready for any merges. Also fully mostly annotated

So now that I've decided I'm no longer going to use require in the plugin the only place using the "scope" is the global fallback which I currently wouldn't mind putting the current logic for getting the scope there (in a pcall most likely). Of course if there is an official way to get the scope at some point I'd switch to that.
With that in mind which parts of this PR would you say are still incomplete? I'd basically be waiting on that before I merge files into one.
(I've decided I'm not going to generate that file, I'm just going to merge them in source as well. Generating it is over complicating it way too much, the plugin really isn't that big to need multiple files).
But too be clear I'm not in a rush, just letting you know that I'm ready any time to merge the PR

Disregarding the require stuff, good to go.
In its current state, I get 0 problems in many different workspace setups included, excluded, workspace code-workspace, .luarc settings, multiple different settings in a mult workspace
I don't even think a pcall is needed.
Language server runs once , and gathers everything into a collection
for each workspace (with a runtime.plugin defined) it re-loads the plugin into the environment for that workspace hence the multiple loads you see. This could be a sumneko bug, or it could not.
I.E if you have a 5 folders in a code.workspace file, and the code.workspace contains runtime.plugin it will get loaded into all 5 workspaces as each workspace is separate.  If workspace.runtime.plugin is blank but 3 workspaces have runtime.plugin in their settings.json it will only get loaded for those three.

runtime.path needs to be set to either at the workspace level or folder level to include "?.lua" and "absolute/path/to/mods/?.lua"

This was tested with runtime.pathstrict I don't know if its needed if that is disabled though

Hmmm I think changing to name = name:gsub("^__(.-)__[%./]", "") will be the better way to go, as I can't get it to work without it, and adding the root folder to the library is just a no go. plus this will make for easier setup of not having to deal with runtime.path

Bug #2 the scope for global is wrong somehow

Let me know your thoughts on the two recent commits, It should cover 85% of the use cases out there

I'm not sure about that global one. I mean I agree that if that previous code was broken it shouldn't exist, but what I had planned was to use the hack that I'm currently using to get the scope and use that for global. Current master is going that if you want to look again. Which is why I said pcall it, since it would break with internal changes in sumneko.lua (like it has at least 5 times by now).
The __modname__ one is unfortuante but considering how gigantic of a pain it is to use the strict path setting it actually doesn't really make it all that much worse. Though I see you've dropped support for \ :thinking: Which is guess is fine since using \ in factorio is asking for trouble since it's all cross platform. Yea this is good.

Btw I'm not asking you to implement the hack for global, I actually plan on merging this PR and then making another PR myself just for that thing so we can have a discussion about it there

The problem for both global and require is there are 2 ways to use a workspace:

Each mod is opened as root in its own workspace or multi-workspace
mods_folder is opened as root (the bleh way)

re: global
The correct way to get the path for global in either situation is the workspace.getRootUri(uri)
In a mods_folder as root workspace setup the getRootUri is mods_folder. If the mods_folder is named mods this works correctly due to the shortcut of trying to parse mods first before getRootUri
re: require
Following that same path using mods_folder as root does allow the original __modname__/a -> modname/ to work with path.strict as true or false however the change to remove the mod identifier altogether https://github.com/JanSharp/FactorioSumnekoLuaPlugin/pull/3/commits/71643b11d68148cb3e74808e3a128d166576fda3 would only work with path.strict = false and I am not sure if I am a big fan of this option even though I don't use mods as root
To summarize:
in option 1:  getRootUri is correct, and removing the modname from the require is correct
in option 2: getRootUri is incorrect and removeing the modname from the require is incorrect
Some options:

Force the correct individual folder workspace setup
Have 2 versions of the plugin depending on your setup.
Have a config variable in plugin.lua to allow the user set the mode between 1 or 2 from above
PR Sumneko to add support for calling an init function with config parameters
Do hacky failure prone things to get the path which I don't see working correctly ever

I am all for 1 or 2 or 4

I think Sumneko pushed a fix that might handle the requires better ... but at the same time it broke plugin usage sooooooo

Sumneko next release will support runtime.path "../?.lua
Current but with sumeko is that it requires absolute path to plugin, hopefully it gets fixed

I think I have a PR about ready for Sumneko that will add runtime.pluginArgs and even though you are possibly going to a single file adding the plugin path

so I'm not entirely sure what to do. While this PR is ready and done I don't feel like it's actually in a good enough state to be released like this. global behaves differently and I wouldn't want to release an update for that and then like a week later release another one that changes it again ( #5 ). So I feel like the best bet would be to just wait until #5 is ready, right? It's not like current master is broken, it's just outdated

This is a meh kind of call, I have thought of a way to automatically determine which mode to use mods or folder when the setting isn't passed, I haven't implemented it yet but it works in my head.
Have you come up with a decision on one plugin file or keeping the requires?
My camp is keep the separate requires. If @justarandomgeek can work with downloading it correctly. Of course this requires 3.5.next for requires to work correctly.  I am also of that camp that user3dParty should be used for both the typedefs and the plugin (which is currently broken in 3.5 but fixed for 3.5.next). This will handle loading the typedefs and the plugin without any additional settings needed other than a path to 3rd party and will allow Jarg to store the typedefs and plugins in workspace storage thingie from what I understand.
On the Sumneko side of things I am currently working on both adding a plugin sandbox as right now anything required inside a plugin is actually kept in package.loaded which doesn't get removed when a plugin is reset or another WS scope is loaded. And additionally adding plugin support for the color picker.

That WIP branch uses the color picker to update the table and I like it!  but the current events system would require plugin support to add different ways of representing the color picker  (another reason I am of team multiple files)
re: Sumneko Scopes
When a workspace is loaded it becomes the the first scope and workspace.rootURI and its children belongs to this scope. Additional workspaces add additional scopes. 3.5.1 will allow one scope to index into the other with .../?.lua in Lua.runtime.path`. I have not tested if this works for all scopes or just scopes that are part of the parent path.
Same for Sumneko settings I believe each scope reads first from luarc.jsonc then workspace/.vscode/settings.lua then workspace.code-workspace settings then from user settings then from fallback settings (default) The closest setting is not overwritten by settings up the line.

Have you come up with a decision on one plugin file or keeping the requires?
My camp is keep the separate requires. If @justarandomgeek can work with downloading it correctly.

I'm good with whatever style of packaging works best for everybody else, as long as there's an easy way for me to tell what version the current install is, whether there's a new version available, and if so where to get it from.


Lines between rulesets

Add lines-between-rulesets option.
Taking over where #436 left off; apologies that the history looks a bit messy.
@sodatea Please review. Thanks!

And why not add sass support for this rule? It should be quite trivial to do so.

I'll take a stab at sass support and see how it goes.

Fow now, sass support is buggy. Seems that gonzales-pe returns false for some .is('space'). Maybe it's because they are declarationDelimiter type rather than simple space nodes in sass.

Okay! I think I got it working. Please take a look when you get a chance. Thanks!

Good job! I think this PR is almost good to go.
But I've got a small problem with comments:
Source:
.foo {
    background: red;
}
/* comment */
.bar {
    border: 1px solid red;
}

After csscomb:
.foo {
    background: red;
}
/* comment */

.bar {
    border: 1px solid red;
}

Notice the position of the comment block. Not sure if this behavior is acceptable.

I would consider that behavior unacceptable, given that it's a fair assumption the comment belongs to the block below. It was a bit tricky, but I think I got the code to correctly handle this case for one or more single-line or multi-line comments preceding a ruleset. Please have a look.

Hi @sodatea, have you had a chance to review this yet? Please let me know if there's anything further you'd like me to change. Thanks!

@ravasthi Sorry, I was on vacation for the last few days and the network connection was too poor.
There are still problems with comments in your PR.
Before:
.foo {background: red;}/*comment*/.bar{border: 1px solid red;}

After:
.foo {background: red;}/*comment*/.bar{border: 1px solid red;}

This was an easy fix; just one small thing I wasn't checking for. Should be all working now.

OK. It looks pretty good now.
Finally, just before merging this branch, it would be much appreciated if you could rebase and squash your commits to get a clean commit history.

Okay, squashed!

@ravasthi Thanks!

:+1: Looking forward to the next release!

Looking forward to it!

Is there any word on this working for Sass?


The JSON DDL request failed with the following error: The 'Name' property cannot contain any of the following characters

When I am trying to deploy differential change, its failing with error "The JSON DDL request failed with the following error: The 'Name' property cannot contain any of the following characters"
I have checked my column & measure names, none of it contain mentioned special character.

This is a known bug. The fix is waiting to be deployed but held up by deployment freezes due to the current climate.
The workaround is to remove special characters from all database names in the workspace (not just the one you're deploying to).
If you choose to use the workaround, can you confirm it worked for you?

I was having having this error with Power BI ALM Toolkit 5.0.5.  On the service I renamed two datasets with parentheses in the name.  That DID NOT resolve the problem, but when I deleted the datasets I was able to successfully UPDATE the model on the service from the Power BI ALM Toolkit application.
Thank you!

Thank you for the context and workaround (I removed special characters and it worked)
This is not happening if pushing datasets to PowerBi Services (using TOM API) but only to my local instance of Analysis Services.
Same behavior is expected on both platforms I guess.
Ticket has been closed; can we still expect a fix?
Thank you @christianwade

The fix I was referring to in the thread was actually for Power BI (not on prem SSAS). It seems the Power BI one has been fixed. For on-prem SSAS, unless we specifically choose to include in a service pack, changes normally show up in the next major version. We are due a major version of SSAS soon, so I'd expect it there.


[Task] Implement the Lenra OAuth module to register/login into Lenra

Implement the Lenra OAuth module to register/login into lenra using the authorization code flow WITH PKCE.
Use a existing library like flutter oauth2_client

Test on Android/Desktop

Remove the "checkAuthenticated" guard to use a Widget instead. The widget would be situated just above the navigator and will check if the user is authenticated. To make sure that the authentication status is regularly checked, we should trigger the widget if an API request ends with a "Authentication failed" error.

It seems that it does not work on Desktop and Mobile because the redirection is done on http but there is nothing that corresponds to that.
See these 3 links to fix Linux, Windows, IOS, macos and Android
https://stackoverflow.com/questions/68716993/google-microsoft-oauth2-login-flow-flutter-desktop-macos-windows-linux/68716994#68716994
https://stackoverflow.com/questions/65458903/socketexception-connection-failed-os-error-operation-not-permitted-errno-1
https://stackoverflow.com/questions/11485271/google-oauth-2-authorization-error-redirect-uri-mismatch


import  in the JAX namespace

Why? It is already implicitly imported:
>>> import jax
>>> jax.tree_util
<module 'jax.tree_util' from '/Users/vanderplas/github/google/jax/jax/tree_util.py'>

But using it like this falls afoul of some linters/type checkers, because the name is not declared in the jax namespace.
I can think of no downside to including it in the namespace explicitly.

CI lint failure fixed in #7705


Do I need to implement my own heartbeat mechanism？

I killed my android app, but the server didn't trigger close。Is this a bug in my code or is it not affected by the heartbeat mechanism?

Check server options related to WebSocketServer and its TCP based heartbeat mechanism.

Check server options related to WebSocketServer and its TCP based heartbeat mechanism.


Develop/split api gui server

This basically splits the dispatcher_gui.py web server into api_server and gui_server. This enables the user to have their own customized GUI while using the existing API server to interact with RMF. Setup and details are mentioned in the rmf_demo_panel/README.md.
On the side note, all dashboard_config.json files have been moved to the respective world in rmf_dashboard_resources.
This also comes along with repo cleanups.

Works great! Thanks for this @tanyouliang95 :100:

Works great! Thanks for this @tanyouliang95 :100:


missing .json file HBN QSIprep dataset

Hi @arokem,
I just added a small function to download the QSIprep-processed HBN data from OSF. However, given the current state outlined in PR 24 the respective .json would be missing. For now, I only included the data of sub-NDAREK918EC2 (based on the QC scores).
Could you maybe have a look/provide some pointers re the json file? I looked on S3 but didn't find the fitting one and was thus wondering if this is due to my lack of knowledge or if it's actually not there.
It would be great to hear from you re this.
Cheers, Peer

No, you're correct that qsiprep did not produce the json files, but I think that it would be rather straightforward to generate the json in this case, based on the instructions here:

{
    "Sources": ["bids:raw:sub-NDAREK918EC2/ses-HBNsiteSI/dwi/sub-NDAREK918EC2_ses-HBNsiteSI_acq-64dir_dwi.nii.gz",
                "bids:raw:sub-NDAREK918EC2/ses-HBNsiteSI/dwi/sub-NDAREK918EC2_ses-HBNsiteSI_acq-64dir_dwi.bval",
                "bids:raw:sub-NDAREK918EC2/ses-HBNsiteSI/dwi/sub-NDAREK918EC2_ses-HBNsiteSI_acq-64dir_dwi.bvec",
                "bids:raw:sub-NDAREK918EC2/ses-HBNsiteSI/anat/sub-NDAREK918EC2_ses-HBNsiteSI_T1w.nii.gz",
                "bids:raw:sub-NDAREK918EC2/ses-HBNsiteSI/fmap/sub-NDAREK918EC2_ses-HBNsiteSI_magnitude1.nii.gz",
                "bids:raw:sub-NDAREK918EC2/ses-HBNsiteSI/fmap/sub-NDAREK918EC2_ses-HBNsiteSI_magnitude2.nii.gz",
                "bids:raw:sub-NDAREK918EC2/ses-HBNsiteSI/fmap/sub-NDAREK918EC2_ses-HBNsiteSI_phasediff.nii.gz"
],
    "SpatialReference": "bids:raw:sub-NDAREK918EC2/ses-HBNsiteSI/anat/sub-NDAREK918EC2_ses-HBNsiteSI_T1w.nii.gz"
}

In addition to propagating the original metadata that are in the json for the raw data files that are here

Hi Ariel,
thank you very much for your message and helpful information.
Just to be sure: I would need to create the json via two steps:

get the metadata from the corresponding raw data files
add the information re sources and SpatialReference you provided

However, shouldn't there also be pipeline-related information? Sorry, I haven't work with that type of derivative yet.
Thanks again, best, Peer

Yes. I think that's all correct.
I think that you can use the dataset_description file here for the pipeline information.

Yes. I think that's all correct.
I think that you can use the dataset_description file here
for the pipeline information.
On Tue, Dec 6, 2022 at 1:42 PM Peer Herholz @.***>
wrote:

Hi Ariel,
thank you very much for your message and helpful information.
Just to be sure: I would need to create the json via two steps:

get the metadata from the corresponding raw data files
add the information re sources and SpatialReference you provided

However, shouldn't there also be pipeline-related information? Sorry, I
haven't work with that type of derivative yet.
Thanks again, best, Peer
—
Reply to this email directly, view it on GitHub
https://github.com/PeerHerholz/bids_bep16_conv/issues/1#issuecomment-1340048512,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA46NU4LPS6IHBQ7B6CX5TWL6XMPANCNFSM6AAAAAASRZ7XHM
.
You are receiving this because you were mentioned.Message ID:
@.***>


Renamed HeadingOutput to GNSSHeadingOutput.

Changes

Renamed HeadingOutput to GNSSHeadingOutput to distinguish between GNSS heading measurements and the nav engine's YPR estimate

@anathan FYI


Commits Not Showing up on Profile Page

My profile page says that I have not made any commits (when I have made commits).  My profile page is connected with my Github and project (and it's Github page).

It would help if you provided more information. Like how many commits you expected to show up and to what repository? Also, were your commits to the master branch or a different branch?

I have made 74 commits this semester, so that is the number I would expect to show up if only commits to my project is counted (I made a pull request that got merged in Scikit-learn, so 75 if that is counted too even though it's not my RCOS project).  The project is SoulEngine and the commits were made to master.

So, if you go on your project page this feature should be implemented. The feature has not yet been added for users yet unfortunately.


Unable to resolve 'Microsoft.AspNetCore.SpaServices (>= 2.0.0)

I am getting the following error after downloading the latest dev branch (Angular2Spa) during package restore:
Unable to resolve 'Microsoft.AspNetCore.SpaServices (>= 2.0.0)' for '.NETCoreApp,Version=v2.0'.
I have the latest preview version of VS2017 and
dotnet --version =  2.0.0-preview1-005977
I am able to go into VS2017 Preview and create a new ASP.NET Core Web API application using 2.0.0 and everything works fine. I see this in the .csproj:
<PackageReference Include="Microsoft.AspNetCore.All" Version="2.0.0-preview1-final" />
Not sure why the error is occurring after downloading the dev branch and adding the AngularSpa template to the same solution with the .NET Core 2.0 Web API.

Until the 2.0.0 packages are published as final releases, you probably just need to add a NuGet.config file that configures your tooling to fetch packages from the prerelease MyGet feed, like this: https://github.com/aspnet/JavaScriptServices/blob/dev/NuGet.config
Note for anyone else reading: If you just use the project templates here in the regular way (e.g., via dotnet new), then this will not affect you - you'll still be using the 1.x packages that are published as final versions. The only way it affects anyone is if you pull sources directly from this repo rather than using the template packages.


[MRG] ENH Current Source Density Feature Add

Fixes https://github.com/mne-tools/mne-python/issues/4480
Adds a current source density estimate function that converts EEG data using the Laplacian of the sensor data.

@sherdim, thanks for the gist, I used it to base the example of off.
https://gist.github.com/sherdim/28b069c8ebca17073f24322e8e721e1f
Would you like your name and email there as an author?

@agramfort now would be okay to review

@alexrockhill

Would you like your name and email there as an author?
I do not mind. It is honorable for me

I had to do it myself, but I didn’t. So go ahead!

@alexrockhill

Would you like your name and email there as an author?

I do not mind. It is honorable for me
I had to do it myself, but I didn’t. So go ahead!

@sherdim I can add it but I don't know your name and email...

Hey I'm getting error when I run "make test" locally but they're all timeout errors. Anyone know how to fix that?
(base) Alexs-MacBook-Pro:mne-python alexrockhill$ make test
python setup.py build_ext -i
running build_ext
rm -f .coverage
py.test -m 'not ultraslowtest' mne
========================================== test session starts ===========================================
platform darwin -- Python 3.6.8, pytest-5.2.0, py-1.8.0, pluggy-0.13.0
rootdir: /Users/alexrockhill/software/mne-python, inifile: setup.cfg
plugins: cov-2.7.1, arraydiff-0.3, remotedata-0.3.2, doctestplus-0.4.0, openfiles-0.4.0
collected 1302 items / 20 errors / 1282 selected
================================================= ERRORS =================================================
__________________________ ERROR collecting mne/commands/tests/test_commands.py __________________________
mne/commands/tests/test_commands.py:206: in
@pytest.mark.timeout(600)  # took ~400 sec on a local test
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324: in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html
__________________________ ERROR collecting mne/commands/tests/test_commands.py __________________________
mne/commands/tests/test_commands.py:206: in
@pytest.mark.timeout(600)  # took ~400 sec on a local test
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324: in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html
_________________ ERROR collecting mne/datasets/sleep_physionet/tests/test_physionet.py __________________
mne/datasets/sleep_physionet/tests/test_physionet.py:62: in
@pytest.mark.timeout(60)
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324: in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html
_________________ ERROR collecting mne/datasets/sleep_physionet/tests/test_physionet.py __________________
mne/datasets/sleep_physionet/tests/test_physionet.py:62: in
@pytest.mark.timeout(60)
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324: in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html
________________________ ERROR collecting mne/forward/tests/test_make_forward.py _________________________
mne/forward/tests/test_make_forward.py:120: in
@pytest.mark.timeout(60)  # can take longer than 30 sec on Travis
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324: in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html
________________________ ERROR collecting mne/forward/tests/test_make_forward.py _________________________
mne/forward/tests/test_make_forward.py:120: in
@pytest.mark.timeout(60)  # can take longer than 30 sec on Travis
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324: in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html
_____________________ ERROR collecting mne/inverse_sparse/tests/test_mxne_inverse.py _____________________
mne/inverse_sparse/tests/test_mxne_inverse.py:44: in
@pytest.mark.timeout(120)  # ~30 sec on AppVeyor and Travis Linux
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324: in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html
_____________________ ERROR collecting mne/inverse_sparse/tests/test_mxne_inverse.py _____________________
mne/inverse_sparse/tests/test_mxne_inverse.py:44: in
@pytest.mark.timeout(120)  # ~30 sec on AppVeyor and Travis Linux
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324: in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html
______________________ ERROR collecting mne/inverse_sparse/tests/test_mxne_optim.py ______________________
mne/inverse_sparse/tests/test_mxne_optim.py:158: in
@pytest.mark.timeout(60)  # ~30 sec on Travis OSX and Linux OpenBLAS
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324: in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html
______________________ ERROR collecting mne/inverse_sparse/tests/test_mxne_optim.py ______________________
mne/inverse_sparse/tests/test_mxne_optim.py:158: in
@pytest.mark.timeout(60)  # ~30 sec on Travis OSX and Linux OpenBLAS
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324: in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html
______________________ ERROR collecting mne/io/artemis123/tests/test_artemis123.py _______________________
mne/io/artemis123/tests/test_artemis123.py:45: in
@pytest.mark.timeout(60)  # ~25 sec on Travis Linux OpenBLAS
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324: in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html
______________________ ERROR collecting mne/io/artemis123/tests/test_artemis123.py _______________________
mne/io/artemis123/tests/test_artemis123.py:45: in
@pytest.mark.timeout(60)  # ~25 sec on Travis Linux OpenBLAS
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324: in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html
__________________________ ERROR collecting mne/io/eeglab/tests/test_eeglab.py ___________________________
mne/io/eeglab/tests/test_eeglab.py:183: in
@pytest.mark.timeout(60)  # ~60 sec on Travis OSX
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324: in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html
__________________________ ERROR collecting mne/io/eeglab/tests/test_eeglab.py ___________________________
mne/io/eeglab/tests/test_eeglab.py:183: in
@pytest.mark.timeout(60)  # ~60 sec on Travis OSX
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324: in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html
____________________________ ERROR collecting mne/tests/test_source_space.py _____________________________
mne/tests/test_source_space.py:306: in
@pytest.mark.timeout(60)  # can be slow on OSX Travis
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324: in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html
____________________________ ERROR collecting mne/tests/test_source_space.py _____________________________
mne/tests/test_source_space.py:306: in
@pytest.mark.timeout(60)  # can be slow on OSX Travis
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324: in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html
___________________________ ERROR collecting mne/utils/tests/test_fetching.py ____________________________
mne/utils/tests/test_fetching.py:9: in
@pytest.mark.timeout(60)
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324: in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html
___________________________ ERROR collecting mne/utils/tests/test_fetching.py ____________________________
mne/utils/tests/test_fetching.py:9: in
@pytest.mark.timeout(60)
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324: in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html
_______________________________ ERROR collecting mne/viz/tests/test_3d.py ________________________________
mne/viz/tests/test_3d.py:425: in
@pytest.mark.timeout(60)  # can sometimes take > 60 sec
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324: in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html
_______________________________ ERROR collecting mne/viz/tests/test_3d.py ________________________________
mne/viz/tests/test_3d.py:425: in
@pytest.mark.timeout(60)  # can sometimes take > 60 sec
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324: in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/latest/mark.html
------------- generated xml file: /Users/alexrockhill/software/mne-python/junit-results.xml --------------
======================================== short test summary info =========================================
FAILED mne/commands/tests/test_commands.py - pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeo...
FAILED mne/commands/tests/test_commands.py - pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeo...
FAILED mne/datasets/sleep_physionet/tests/test_physionet.py - pytest.PytestUnknownMarkWarning: Unknown ...
FAILED mne/datasets/sleep_physionet/tests/test_physionet.py - pytest.PytestUnknownMarkWarning: Unknown ...
FAILED mne/forward/tests/test_make_forward.py - pytest.PytestUnknownMarkWarning: Unknown pytest.mark.ti...
FAILED mne/forward/tests/test_make_forward.py - pytest.PytestUnknownMarkWarning: Unknown pytest.mark.ti...
FAILED mne/inverse_sparse/tests/test_mxne_inverse.py - pytest.PytestUnknownMarkWarning: Unknown pytest....
FAILED mne/inverse_sparse/tests/test_mxne_inverse.py - pytest.PytestUnknownMarkWarning: Unknown pytest....
FAILED mne/inverse_sparse/tests/test_mxne_optim.py - pytest.PytestUnknownMarkWarning: Unknown pytest.ma...
FAILED mne/inverse_sparse/tests/test_mxne_optim.py - pytest.PytestUnknownMarkWarning: Unknown pytest.ma...
FAILED mne/io/artemis123/tests/test_artemis123.py - pytest.PytestUnknownMarkWarning: Unknown pytest.mar...
FAILED mne/io/artemis123/tests/test_artemis123.py - pytest.PytestUnknownMarkWarning: Unknown pytest.mar...
FAILED mne/io/eeglab/tests/test_eeglab.py - pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeou...
FAILED mne/io/eeglab/tests/test_eeglab.py - pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeou...
FAILED mne/tests/test_source_space.py - pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - ...
FAILED mne/tests/test_source_space.py - pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - ...
FAILED mne/utils/tests/test_fetching.py - pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout ...
FAILED mne/utils/tests/test_fetching.py - pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout ...
FAILED mne/viz/tests/test_3d.py - pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is thi...
FAILED mne/viz/tests/test_3d.py - pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is thi...
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 20 errors during collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
=========================================== 20 error in 9.92s ============================================
make: *** [test] Error 2

These are not timeouts. This is your version of pytest not knowing about the "timeout" mark:
E pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout
Also I noticed you're in the"base" conda env, maybe that's the problem...
On October 5, 2019 5:34:50 PM PDT, Alex Rockhill<EMAIL_ADDRESS>wrote:

Hey I'm getting error when I run "make test" locally but they're all
timeout errors. Anyone know how to fix that?
(base) Alexs-MacBook-Pro:mne-python alexrockhill$ make test
python setup.py build_ext -i
running build_ext
rm -f .coverage
py.test -m 'not ultraslowtest' mne
========================================== test session starts
platform darwin -- Python 3.6.8, pytest-5.2.0, py-1.8.0, pluggy-0.13.0
rootdir: /Users/alexrockhill/software/mne-python, inifile: setup.cfg
plugins: cov-2.7.1, arraydiff-0.3, remotedata-0.3.2, doctestplus-0.4.0,
openfiles-0.4.0
collected 1302 items / 20 errors / 1282 selected
================================================= ERRORS
__________________________ ERROR collecting
mne/commands/tests/test_commands.py __________________________
mne/commands/tests/test_commands.py:206: in
@pytest.mark.timeout(600)  # took ~400 sec on a local test
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324:
in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is
this a typo?  You can register custom marks to avoid this warning - for
details, see https://docs.pytest.org/en/latest/mark.html
__________________________ ERROR collecting
mne/commands/tests/test_commands.py __________________________
mne/commands/tests/test_commands.py:206: in
@pytest.mark.timeout(600)  # took ~400 sec on a local test
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324:
in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is
this a typo?  You can register custom marks to avoid this warning - for
details, see https://docs.pytest.org/en/latest/mark.html
_________________ ERROR collecting
mne/datasets/sleep_physionet/tests/test_physionet.py __________________
mne/datasets/sleep_physionet/tests/test_physionet.py:62: in
@pytest.mark.timeout(60)
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324:
in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is
this a typo?  You can register custom marks to avoid this warning - for
details, see https://docs.pytest.org/en/latest/mark.html
_________________ ERROR collecting
mne/datasets/sleep_physionet/tests/test_physionet.py __________________
mne/datasets/sleep_physionet/tests/test_physionet.py:62: in
@pytest.mark.timeout(60)
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324:
in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is
this a typo?  You can register custom marks to avoid this warning - for
details, see https://docs.pytest.org/en/latest/mark.html
________________________ ERROR collecting
mne/forward/tests/test_make_forward.py _________________________
mne/forward/tests/test_make_forward.py:120: in
@pytest.mark.timeout(60)  # can take longer than 30 sec on Travis
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324:
in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is
this a typo?  You can register custom marks to avoid this warning - for
details, see https://docs.pytest.org/en/latest/mark.html
________________________ ERROR collecting
mne/forward/tests/test_make_forward.py _________________________
mne/forward/tests/test_make_forward.py:120: in
@pytest.mark.timeout(60)  # can take longer than 30 sec on Travis
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324:
in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is
this a typo?  You can register custom marks to avoid this warning - for
details, see https://docs.pytest.org/en/latest/mark.html
_____________________ ERROR collecting
mne/inverse_sparse/tests/test_mxne_inverse.py _____________________
mne/inverse_sparse/tests/test_mxne_inverse.py:44: in
@pytest.mark.timeout(120)  # ~30 sec on AppVeyor and Travis Linux
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324:
in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is
this a typo?  You can register custom marks to avoid this warning - for
details, see https://docs.pytest.org/en/latest/mark.html
_____________________ ERROR collecting
mne/inverse_sparse/tests/test_mxne_inverse.py _____________________
mne/inverse_sparse/tests/test_mxne_inverse.py:44: in
@pytest.mark.timeout(120)  # ~30 sec on AppVeyor and Travis Linux
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324:
in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is
this a typo?  You can register custom marks to avoid this warning - for
details, see https://docs.pytest.org/en/latest/mark.html
______________________ ERROR collecting
mne/inverse_sparse/tests/test_mxne_optim.py ______________________
mne/inverse_sparse/tests/test_mxne_optim.py:158: in
@pytest.mark.timeout(60)  # ~30 sec on Travis OSX and Linux OpenBLAS
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324:
in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is
this a typo?  You can register custom marks to avoid this warning - for
details, see https://docs.pytest.org/en/latest/mark.html
______________________ ERROR collecting
mne/inverse_sparse/tests/test_mxne_optim.py ______________________
mne/inverse_sparse/tests/test_mxne_optim.py:158: in
@pytest.mark.timeout(60)  # ~30 sec on Travis OSX and Linux OpenBLAS
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324:
in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is
this a typo?  You can register custom marks to avoid this warning - for
details, see https://docs.pytest.org/en/latest/mark.html
______________________ ERROR collecting
mne/io/artemis123/tests/test_artemis123.py _______________________
mne/io/artemis123/tests/test_artemis123.py:45: in
@pytest.mark.timeout(60)  # ~25 sec on Travis Linux OpenBLAS
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324:
in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is
this a typo?  You can register custom marks to avoid this warning - for
details, see https://docs.pytest.org/en/latest/mark.html
______________________ ERROR collecting
mne/io/artemis123/tests/test_artemis123.py _______________________
mne/io/artemis123/tests/test_artemis123.py:45: in
@pytest.mark.timeout(60)  # ~25 sec on Travis Linux OpenBLAS
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324:
in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is
this a typo?  You can register custom marks to avoid this warning - for
details, see https://docs.pytest.org/en/latest/mark.html
__________________________ ERROR collecting
mne/io/eeglab/tests/test_eeglab.py ___________________________
mne/io/eeglab/tests/test_eeglab.py:183: in
@pytest.mark.timeout(60)  # ~60 sec on Travis OSX
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324:
in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is
this a typo?  You can register custom marks to avoid this warning - for
details, see https://docs.pytest.org/en/latest/mark.html
__________________________ ERROR collecting
mne/io/eeglab/tests/test_eeglab.py ___________________________
mne/io/eeglab/tests/test_eeglab.py:183: in
@pytest.mark.timeout(60)  # ~60 sec on Travis OSX
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324:
in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is
this a typo?  You can register custom marks to avoid this warning - for
details, see https://docs.pytest.org/en/latest/mark.html
____________________________ ERROR collecting
mne/tests/test_source_space.py _____________________________
mne/tests/test_source_space.py:306: in
@pytest.mark.timeout(60)  # can be slow on OSX Travis
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324:
in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is
this a typo?  You can register custom marks to avoid this warning - for
details, see https://docs.pytest.org/en/latest/mark.html
____________________________ ERROR collecting
mne/tests/test_source_space.py _____________________________
mne/tests/test_source_space.py:306: in
@pytest.mark.timeout(60)  # can be slow on OSX Travis
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324:
in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is
this a typo?  You can register custom marks to avoid this warning - for
details, see https://docs.pytest.org/en/latest/mark.html
___________________________ ERROR collecting
mne/utils/tests/test_fetching.py ____________________________
mne/utils/tests/test_fetching.py:9: in
@pytest.mark.timeout(60)
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324:
in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is
this a typo?  You can register custom marks to avoid this warning - for
details, see https://docs.pytest.org/en/latest/mark.html
___________________________ ERROR collecting
mne/utils/tests/test_fetching.py ____________________________
mne/utils/tests/test_fetching.py:9: in
@pytest.mark.timeout(60)
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324:
in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is
this a typo?  You can register custom marks to avoid this warning - for
details, see https://docs.pytest.org/en/latest/mark.html
_______________________________ ERROR collecting
mne/viz/tests/test_3d.py ________________________________
mne/viz/tests/test_3d.py:425: in
@pytest.mark.timeout(60)  # can sometimes take > 60 sec
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324:
in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is
this a typo?  You can register custom marks to avoid this warning - for
details, see https://docs.pytest.org/en/latest/mark.html
_______________________________ ERROR collecting
mne/viz/tests/test_3d.py ________________________________
mne/viz/tests/test_3d.py:425: in
@pytest.mark.timeout(60)  # can sometimes take > 60 sec
../anaconda3/lib/python3.6/site-packages/_pytest/mark/structures.py:324:
in getattr
PytestUnknownMarkWarning,
E   pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is
this a typo?  You can register custom marks to avoid this warning - for
details, see https://docs.pytest.org/en/latest/mark.html
------------- generated xml file:
/Users/alexrockhill/software/mne-python/junit-results.xml
======================================== short test summary info
FAILED mne/commands/tests/test_commands.py -
pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeo...
FAILED mne/commands/tests/test_commands.py -
pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeo...
FAILED mne/datasets/sleep_physionet/tests/test_physionet.py -
pytest.PytestUnknownMarkWarning: Unknown ...
FAILED mne/datasets/sleep_physionet/tests/test_physionet.py -
pytest.PytestUnknownMarkWarning: Unknown ...
FAILED mne/forward/tests/test_make_forward.py -
pytest.PytestUnknownMarkWarning: Unknown pytest.mark.ti...
FAILED mne/forward/tests/test_make_forward.py -
pytest.PytestUnknownMarkWarning: Unknown pytest.mark.ti...
FAILED mne/inverse_sparse/tests/test_mxne_inverse.py -
pytest.PytestUnknownMarkWarning: Unknown pytest....
FAILED mne/inverse_sparse/tests/test_mxne_inverse.py -
pytest.PytestUnknownMarkWarning: Unknown pytest....
FAILED mne/inverse_sparse/tests/test_mxne_optim.py -
pytest.PytestUnknownMarkWarning: Unknown pytest.ma...
FAILED mne/inverse_sparse/tests/test_mxne_optim.py -
pytest.PytestUnknownMarkWarning: Unknown pytest.ma...
FAILED mne/io/artemis123/tests/test_artemis123.py -
pytest.PytestUnknownMarkWarning: Unknown pytest.mar...
FAILED mne/io/artemis123/tests/test_artemis123.py -
pytest.PytestUnknownMarkWarning: Unknown pytest.mar...
FAILED mne/io/eeglab/tests/test_eeglab.py -
pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeou...
FAILED mne/io/eeglab/tests/test_eeglab.py -
pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeou...
FAILED mne/tests/test_source_space.py -
pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - ...
FAILED mne/tests/test_source_space.py -
pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout - ...
FAILED mne/utils/tests/test_fetching.py -
pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout ...
FAILED mne/utils/tests/test_fetching.py -
pytest.PytestUnknownMarkWarning: Unknown pytest.mark.timeout ...
FAILED mne/viz/tests/test_3d.py - pytest.PytestUnknownMarkWarning:
Unknown pytest.mark.timeout - is thi...
FAILED mne/viz/tests/test_3d.py - pytest.PytestUnknownMarkWarning:
Unknown pytest.mark.timeout - is thi...
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 20 errors during
collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
=========================================== 20 error in 9.92s
make: *** [test] Error 2

Thanks, I could have figured that out my bad

@alexrockhill somehow you have a bunch of conflicts in unrelated files

I'm having some weird issues with tests failing... I'm not sure why files not related to this PR were being modified but I think I fixed that. When I run "make test" most of the tests pass but I get a few errors like
E               FileNotFoundError: [Errno 2] No such file or directory: 'mne_compensate_data': 'mne_compensate_data'
/Users/alexrockhill/software/mne-python/mne/preprocessing/_peak_finder.py:45: DocTestFailure
E       AssertionError: SNR (worst 2.55) < 3.50 for 18/306 channels (/Users/alexrockhill/mne_data/MNE-testing-data/SSS/test_move_anon_raw.fif)
I'm not sure what these are about. Using a fresh install of the mnedev environment. Here's just the first part of the stack trace:
(mnedev) alexrockhill@Alexs-MacBook-Pro mne-python % make test
python setup.py build_ext -i
running build_ext
rm -f .coverage
py.test -m 'not ultraslowtest' mne
Test session starts (platform: darwin, Python 3.7.4, pytest 5.2.1, pytest-sugar 0.9.2)
rootdir: /Users/alexrockhill/software/mne-python, inifile: setup.cfg
plugins: sugar-0.9.2, timeout-1.3.3, cov-2.7.1, mock-1.10.4
collecting ...
mne/annotations.py s                                              0%
mne/dipole.py s                                                   0%
mne/epochs.py ss                                                  0%
mne/event.py s✓                                                   0% ▏
mne/filter.py ✓                                                   0% ▏
―――――――――――――――――― [doctest] mne.filter.construct_iir_filter ―――――――――――――――――――
103     >>> iir_params = construct_iir_filter(iir_params, 40, 50, 1000, 'low')  # doctest:+SKIP
104     >>> print((2 * len(iir_params['sos']), iir_params['padlen']))  # doctest:+SKIP
105     (6, 439)
106
107     Padding and/or filter coefficients can also be manually specified. For
108     a 10-sample moving window with no padding during filtering, for example,
109     one can just do:
110
111     >>> iir_params = dict(b=np.ones((10)), a=[1, 0], padlen=0)
112     >>> iir_params = construct_iir_filter(iir_params, return_copy=False)
Expected nothing
Got:

/Users/alexrockhill/software/mne-python/mne/filter.py:112: DocTestFailure
mne/filter.py ⨯                                                   1% ▏
――――――――――――――――――――――――― [doctest] mne.filter.detrend ―――――――――――――――――――――――――
cc @jasmainak @larsoner @drammock

@alexrockhill are all the changes here related to this PR?

They are or should be now. For some reason there were other files changed but I checked the file change diffs and that should be fixed. Now they are all just the files I had to change for csd

Good catch, the _optical_density was unrelated. The interpolation is because one function was already used there so I just imported it and put the other analogous function there as well. @drammock

Just an update, I thought it would be a good check to run make test on master (after pulling from upstream master) and that test failed also so I'm not sure what's wrong with my setup but I'm looking into it.
(mnedev) alexrockhill@Alexs-MacBook-Pro mne-python % make test
python setup.py build_ext -i
running build_ext
rm -f .coverage
py.test -m 'not ultraslowtest' mne
Test session starts (platform: darwin, Python 3.7.4, pytest 5.2.1, pytest-sugar 0.9.2)
rootdir: /Users/alexrockhill/software/mne-python, inifile: setup.cfg
plugins: sugar-0.9.2, timeout-1.3.3, cov-2.7.1, mock-1.10.4
collecting ...
mne/annotations.py s                                              0%
mne/dipole.py s                                                   0%
mne/epochs.py ss                                                  0%
mne/event.py s✓                                                   0% ▏
mne/filter.py ✓                                                   0% ▏
―――――――――――――――――― [doctest] mne.filter.construct_iir_filter ―――――――――――――――――――
103     >>> iir_params = construct_iir_filter(iir_params, 40, 50, 1000, 'low')  # doctest:+SKIP
104     >>> print((2 * len(iir_params['sos']), iir_params['padlen']))  # doctest:+SKIP
105     (6, 439)
106
107     Padding and/or filter coefficients can also be manually specified. For
108     a 10-sample moving window with no padding during filtering, for example,
109     one can just do:
110
111     >>> iir_params = dict(b=np.ones((10)), a=[1, 0], padlen=0)
112     >>> iir_params = construct_iir_filter(iir_params, return_copy=False)
Expected nothing
Got:

/Users/alexrockhill/software/mne-python/mne/filter.py:112: DocTestFailure
mne/filter.py ⨯                                                   1% ▏
――――――――――――――――――――――――― [doctest] mne.filter.detrend ―――――――――――――――――――――――――
1534
1535     Examples
1536     --------
1537     As in :func:scipy.signal.detrend::
1538
1539         >>> randgen = np.random.RandomState(9)
1540         >>> npoints = int(1e3)
1541         >>> noise = randgen.randn(npoints)
1542         >>> x = 3 + 2*np.linspace(0, 1, npoints) + noise
1543         >>> (detrend(x) - noise).max() < 0.01
UNEXPECTED EXCEPTION: RuntimeWarning("internal gelsd driver lwork query error, required iwork dimension not returned. This is likely the result of LAPACK bug 0038, fixed in LAPACK 3.2.2 (released July 21, 2010). Falling back to 'gelss' driver.")
Traceback (most recent call last):
File "/Users/alexrockhill/software/anaconda3/envs/mnedev/lib/python3.7/doctest.py", line 1329, in __run
compileflags, 1), test.globs)
File "<doctest mne.filter.detrend[4]>", line 1, in
File "/Users/alexrockhill/software/mne-python/mne/filter.py", line 1556, in detrend
y = detrend(x, axis=axis, type=fit)
File "/Users/alexrockhill/.local/lib/python3.7/site-packages/scipy/signal/signaltools.py", line 2535, in detrend
coef, resids, rank, s = linalg.lstsq(A, newdata[sl])
File "/Users/alexrockhill/.local/lib/python3.7/site-packages/scipy/linalg/basic.py", line 1225, in lstsq
warn(mesg, RuntimeWarning, stacklevel=2)
RuntimeWarning: internal gelsd driver lwork query error, required iwork dimension not returned. This is likely the result of LAPACK bug 0038, fixed in LAPACK 3.2.2 (released July 21, 2010). Falling back to 'gelss' driver.
/Users/alexrockhill/software/mne-python/mne/filter.py:1543: UnexpectedException
mne/filter.py ⨯✓

A bunch of minor stuff @alexrockhill, I think it's getting close! We (mostly) just need to work out with @agramfort how to prevent people from source localizing CSD-transformed data.
One option is actually to extend custom_ref_applied. It's actually written as an int but we only use 0 (not applied) or 1 (applied) currently. We could make this an enumeration, where 2 is now CSD-transformed data. If info['custom_ref_applied'] > 1, then don't let them change the reference, or do source loc.
This change will be a bit of a pain, though, so I could make a first quick PR to make the reference-setting code respect values other than False/True (0 or 1) to start.

Not without introducing new constants, or using info['comps'] in a way we probably shouldn't

then it seems we have a working solution

What do I have to do to resolve? :
changes/latest.inc:17: WARNING: Unknown target name: "alex rockhill".
This is in the make html_dev-noplot

Also not sure how to fix:
WARNING: dot command 'dot' cannot be run (needed for graphviz output), check the graphviz_dot setting
changes/latest.inc:17: WARNING: undefined label: compute_current_source_density (if the link has no caption the label must precede a section header)

Add your name and URL to names.inc so that there's a target to link to.

for the dot command, you need to install graphviz.  Are you seeing that error locally? it shouldn't happen on our CIs...

for the undefined label warning, you need to make sure that compute_current_source_density is in doc/python_reference.rst

also, instead of using the :ref: role, you should link to it using something like
:func:`mne.compute_current_source_density`

(or wherever it lives in the mne namespace)

for the undefined label warning, you need to make sure that compute_current_source_density is in doc/python_reference.rst

I think I put it in the right place already... is here wrong:
:py:mod:mne.preprocessing:
.. currentmodule:: mne.preprocessing
.. automodule:: mne.preprocessing
:no-members:
:no-inherited-members:
.. autosummary::
:toctree: generated/
ICA
Xdawn
compute_current_source_density
...

I think I put it in the right place already

that looks right. but a generic :ref: role won't work, you have to use
:func:`mne.preprocessing.compute_current_source_density`

WIP Eric comments almost done

:) Let me know when I should look again, go go go @alexrockhill !

Pushed commits to https://github.com/mne-tools/fiff-constants/pull/23 and #7000 to add:

FIFF.FIFF_UNIT_V_M2 = 117  # V/m^2
FIFF.FIFFV_COIL_EEG_CSD               = 6

I think we'll want both of these in the CSD code, and we'll want to do:
info['chs'][ii].update(coil_type=FIFF.FIFFV_COIL_EEG_CSD,
                       unit=FIFF.FIFF_UNIT_V_M2)

This means that all of the picking and plotting functions can and will need to be updated properly. But this seems to be the cleanest approach.
To figure out at least some of the updates, we can look to see what we did to support FIFFV_COIL_EEG_BIPOLAR           = 5 properly.

Is this how it should be? :
for ch in inst.info['chs']:
if ch['coil_type'] == FIFF.FIFFV_COIL_EEG:
ch.update(coil_type=FIFF.FIFFV_COIL_EEG_CSD,
unit=FIFF.FIFF_UNIT_V_M2)
Not sure if it should just change eeg (not accessory channels) and if this is the best way to do that.

Also, I checked and the units were not changed in the example plots... @larsoner is there something else that has to be done for these?

Ok so I'm getting some errors that are in scripts that are pretty incomprehensible to me. If someone wouldn't mind helping me take this over the finish line to pass the last couple of checks that would be really helpful. cc @larsoner

I can look tomorrow and push some commits

@alexrockhill I was about to look at this, are you working on it currently or is now a good time for me to try?

@alexrockhill I was about to look at this, are you working on it currently or is now a good time for me to try?

Now is a great time, just rebased to master now not touching it.

Okay @alexrockhill pushed a commit to fix the errors and tweak the example. Take a look and see if it makes sense

Okay @alexrockhill pushed a commit to fix the errors and tweak the example. Take a look and see if it makes sense

Looks great! Yeah retrospectively the parameter search was superfluous with the default values. Thanks for doing that for me. I understand a bit better about the constants for different channel types but I had messed that up a bit so I really appreciate the help, it would have taken me a long time to figure that out.

I understand a bit better about the constants for different channel types but I had messed that up a bit so I really appreciate the help, it would have taken me a long time to figure that out.

It's not really documented anywhere so it's really opaque :)
@agramfort since @alexrockhill and I are happy, this is ready for review/merge I think

Checking on review, anyone up for this?

@drammock do you want to look?

Okay @drammock pushed commits that hopefully took care of those things

Okay @drammock pushed commits that hopefully took care of those things

Thanks @drammock and @larsoner!

Let's wait for @agramfort to look then merge

So trying to help, I looked into this error but it looks like it has to do with triaging meg types for ctf. I'm not sure why this was effected but it seems pretty complicated and unexpected that it was.

I'm not sure why this was effected but it seems pretty complicated and unexpected that it was.

One of my commits messed with picking functions. It's always a little bit dangerous because that code is quite complex to support a bunch of different use cases that evolved over time.
I'll pull the current version to see if things pass and if not, push some commits.

Tests pass locally now, it was missing a ref_meg=False

I saw that it had to do with a false positive meg_ref, I just couldn't figure out at which level (tests, epochs, viz.epochs or viz.utils) so I'm glad you figured it out :)

@agramfort I'm not sure if there was a versioning issue but there weren't any evo in the last one, they had all been changed to evoked... not sure what happened there. Anyway, I did as you suggested, and it should be good to go now.

thx heaps @alexrockhill for leading this effort !


icompta - It seems the symlink source is not there

Hello,
I tried to install icompta, but I've got this error:
➜  $ brew cask install icompta
==> Satisfying dependencies
complete
==> Downloading http://www.icompta-app.com/files/iCompta_Demo.zip
######################################################################## 100,0%
==> No checksum defined for Cask icompta, skipping verification
Error: It seems the symlink source is not there: '/opt/homebrew-cask/Caskroom/icompta/latest/iCompta.app'

How can I fix this problem?

How can I fix this problem?

By downloading it and checking how the name of the app in the DMG changed.
Fixed in https://github.com/caskroom/homebrew-cask/pull/19953.


should we update models to json schema draft v6?

regardless, probably it would be useful to add the schema version reference in all the schemas.
"$schema": "http://json-schema.org/draft-04/schema#",

what's new in v6?

http://json-schema.org/draft-06/json-schema-migration-faq.html
anyhow, i think we should be consistent, not in all schema we define the version.

everything align with latest JSON Schema. we can reopen if needed


Why can't I configure it anymore

Can't configure and change what programs it applies to

Try running the ResetConfig.reg in the zip.


Heading not in a logical sequence

We should not skip a heading (going from h1 directly to h3)

Was put wrongly in #137

Will be solved with SWG-18

Headings hierarchy has been reviewed in version 3.0.0.


run-local.bash was not found

$AMBERHOME/miniconda/bin/python GHOAT.py -i input.in -s equil
This command will create an ./equil folder, with one folder inside for each of the guests. In order to run the simulations for each guest, you can use the run-local.bash script (to run them locally), or the PBS-run script...
in the ./equil/run_files folder, there are
local-equil.bash   local-lig.bash   PBS-create   PBS-fe    PBS-sdr        run-rest.bash           run-sdr-missing.bash local-fe.bash      local-sdr.bash   PBS-equil    PBS-lig   run-all.bash   run-rest-missing.bash   run-sdr-site.bash
files, and run-local.bash was not found

The run-local.bash file is already in the simulation folders, the ones you listed are the different templates to build it.

The run-local.bash file is already in the simulation folders, the ones you listed are the different templates to build it.

Thanks a lot. I found it in the guest-1 or guest-3 folder.


Newly loaded videos - not supported in "Recents"

There seems to be a problem with the newly loaded videos in the "Recents". Video format is not supported.

Looks like the Recent subjects array is returning empty for the new subjects. Video encoding doesn't appear to have any relation.

Can you do anything? Message says (in German) no supported videos are found.

Yeah, it's falling back to the error message for the html video tag, which I made to be about video format. But, the call for Recents isn't returning SubjectsForRecent, so the video sources aren't being set. I'm taking a look at it now to make sure it isn't something in the front end code.

I think I know what's causing this. I should have it fixed today.

Recents should be working again now.


Expose the current animation tree and player to AnimationNode

Exposes the tree and player members of AnimationNode::State available in C++ to scripts, enabling their use in custom nodes.
Without this various obtuse and potentially problematic workarounds are required.
For example, with this patch, the following code can be changed from this (which has undesired side effects):
# seek the animation to its beginning, which will cause `blend_node` to
# return its length
duration = blend_node(animation_node_name, animation_node, 0.0, true, false,
	0.0, AnimationNode.FILTER_IGNORE, true)

To the more obvious and direct form:
duration = get_player().get_animation(animation_name).length

There is related issue as https://github.com/godotengine/godot/issues/23629#issuecomment-1001020829; this means accessing a scene from a resource, which may cause problems when there are multiple scenes that use the same animation.


Task 'j2objcBuild' not found in project ':core'.

According to your instructions you say run build_framework.sh, but it points to a target in core project which does not exist.
So how do I run this for iOS?
Also, you point to a branch that doesn't exist anymore in Podfile:
pod 'HanekeSwift', git: 'https://github.com/Haneke/HanekeSwift.git', branch: 'feature/swift-2.3'
should be replaced by
pod 'HanekeSwift', git: 'https://github.com/Haneke/HanekeSwift.git', branch: 'feature/swift-3'

Sorry, I should've updated readme, latest master doesn't support j2objc anymore.
Tag 1.1.1 is the last supported one.

Master branch reverted to tag 1.1.1


About hardware source

I would like to train this model of yours or train a model using your data. I'm interested in knowing the approximate duration for training this model and some hardware information. It seems that the paper doesn't appear to have this information.
Thanks！

For BLIP2, using 64 V100s, training is < 1 day.
For Flamingo, using 8 A100s, training is < 7 days


small name changes

I forgot to change the name from "simple image classifier"

should we change the folder name too? the idea was to have each example have a unique id at the beginning


Allow for IBM i PASE Support

While working on getting appmetrics (uses omr-agentcore as a sub-module) installed on PASE, I ran into problems compiling on IBM i. I had to include some if defined checks for PASE and implementation some different implementation when on PASE. Since PASE uses an AIX-like environment some paths were identical, while at times the two diverged. I am working on PR that would allow for PASE support , and plan submit next week.

Update PR is now open https://github.com/RuntimeTools/omr-agentcore/pull/69

@abmusse Change has been merged - can you please retest and close this issue if it has been resolved?


Add "gateway.networking.k8s.io/policy" label to policy CRDs

Requried as per https://gateway-api.sigs.k8s.io/geps/gep-2648/#standard-label-on-crd-objects
/assign @briantkennedy

Thanks!


Update the contribution-guide.md

Need to refactor this page contribution-guide.md :

Explain how to build ubiquity by using the new Docker images.
Update golang version to 1.9.1
How to use glide
And how to run ubiquity UT from docker image  (we also need to provide dockerfile for UT stage)
Update how to install section, which totally change in the GA release.

The same for ubiquity-k8s repository
Note: thanks Joseph W Cropper for raising this documentation issue.

items 2, 3 and 5 were already updated for GA 1.1.0.
Still left to finish item 1 and 4.
So I will close this ticket, and reopen another ticket for the left overs.


Adjust all the document to add text module

What type of PR is this?
/kind documentation
What does this PR do / why do we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewers:

LGTM