Update descriptions as follows:

 "202": {
            "description": "The provisioning service resource provider always returns a 202 Accepted status code with valid Location and Retry-After headers. The resource provider also sets the Azure-AsyncOperation header with a URL that points to the operation resource for this operation. Subsequent GET attempts on the resource after a DELETE operation return a resource representation that indicates a transitional provisioning state (such as Terminating). To retrieve the status of the operation, a client can either poll the URL returned in the Location header after the Retry-After interval, get the provisioning service status directly, or query the operation resource.",
          "200": {
            "description": "This is returned as a response to the status polling request for the delete operation. The body contains the resource representation that indicates a transitional provisioning state.",
          "204": {
            "description": "Once the long running delete operation completes successfully, a 204 No Content status code is returned when the status polling request finds the provisioning service metadata in the service and the status of the delete operation is set to a completed state."
          },
          "404": {
            "description": "After the long running delete operation completes successfully, a 404 Not Found is returned when the status polling request no longer finds the provisioning service metadata in the service.",


This regex was found somewhere in regex101. It's the tidiest thing I could find for matching escapable strings and words without quotation marks.


Sure but now I have scripts that rely on the posix shell and several other external tools. This could be replaced with a (similar) set of tools which run inside dosemu. We'd just need to build them from source so that they'd be eligible for packaging in the major distros. Still I think even a very simple dos would already cover a lot of basic usecases.


Thanks for the hint! Changed in https://github.com/leanprover/mathlib/commit/a8a1a91b3df1d9790c9ee29c6020ac2f95658254

Btw: Thanks for implementing the simplification of `let`-bindings!


We will use KMongo library to load/save data to MongoDB


## 문제 & 개선
**1. 루트 디렉토리 즉, 드라이브 폴더에 닿았을 때 드라이브를 선택할 수 있어야 한다.**
> 어떻게 운영체제에 설치된 볼륨 목록을 텍스트로 가져올 수 있을까.

**2. 파일 또는 디렉토리의 간단한 편집기능을 구현한다.**
> system call을 통해서 robocopy나 기존 cmd 명령어의 이용?

**3. 공백을 가진 파일 또는 디렉토리의 이름을 인식하지 못한다.**
> 공백을 가진 디렉토리의 문자열을  `"" (Double quota)` 로 감싸야한다.


minimised minimized.
thats how they spell it on the window minimize icon tooltip. :)


La branche 'doc' sera la seule ou je t'autoriserai a parler anglais ^^
C'est une branche temporaire juste pour nous. Sinon merci de tout garder en anglais ;)


to import from current packege use from .plotsettings import ... More pythonic way


Oui je t'ai fait une doc a la barbare, c'est juste pour avoir les routes / idees a plat.
Les routes front on en parlera ;)


Poprawione


@chdefrene Do not spoil, have it on my watch list.

@mbuvarp  English is in case we have non Norwegian readers contributing to the project.


dump of latest backed up source code - all files


Not a best way to use OO thread programming. But it's ok, even in production. Instead use your own "worker" class that would be a thread body. say no to inheritance


You rock, this fixes:
```
java.lang.RuntimeException:
  at android.app.ActivityThread.performResumeActivity (ActivityThread.java:3421)
  at android.app.ActivityThread.handleResumeActivity (ActivityThread.java:3461)
  at android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:2730)
  at android.app.ActivityThread.-wrap12 (ActivityThread.java)
  at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1473)
  at android.os.Handler.dispatchMessage (Handler.java:102)
  at android.os.Looper.loop (Looper.java:154)
  at android.app.ActivityThread.main (ActivityThread.java:6123)
  at java.lang.reflect.Method.invoke (Native Method)
  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:867)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:757)
Caused by: java.lang.RuntimeException:
  at com.frostwire.android.gui.services.EngineThreadPool.verifyTask (EngineThreadPool.java:64)
  at com.frostwire.android.gui.services.EngineThreadPool.submit (EngineThreadPool.java:52)
  at com.frostwire.android.gui.Peer.finger (Peer.java:58)
  at com.frostwire.android.gui.fragments.MyFilesFragment.updateHeader (MyFilesFragment.java:440)
  at com.frostwire.android.gui.fragments.MyFilesFragment.onResume (MyFilesFragment.java:262)
  at android.app.Fragment.performResume (Fragment.java:2398)
  at android.app.FragmentManagerImpl.moveToState (FragmentManager.java:1032)
  at android.app.FragmentManagerImpl.moveToState (FragmentManager.java:1171)
  at android.app.FragmentManagerImpl.moveToState (FragmentManager.java:1153)
  at android.app.FragmentManagerImpl.dispatchResume (FragmentManager.java:2051)
  at android.app.FragmentController.dispatchResume (FragmentController.java:198)
  at android.app.Activity.performResume (Activity.java:6797)
  at android.app.ActivityThread.performResumeActivity (ActivityThread.java:3398)
```

Thanks for fixing right away


Please sign your commits with the same identity as your Github account.
To configure only locally: git config user.name ... git config user.email ...


First test.

The good:
- Flag is `false` after (re)starting deCONZ, no events;
- Rule with condition on flag false doesn't execute after restart;
- Rule with condition on flag and dx on lastupdated executes as expected;

The bad:
- Lastupdated is changed after (re) starting deCONZ (presumably setting the flag to false a second time after startup?)
- When setting flag to current value, a state changed event is issued with only lastupdated;  I'd expect an event with both flag and lastupdated.
- When setting flag to different value, _two_ state changed events are issues: one with flag and lastupdated, one with only lastupdated;  I'd expect a single event with both flag and lastupdated.
- Indeed, rule with condition on flag and dx executes _twice_ when setting flag to the same value.


We still need to figure out what angles we're going to be doing it for. I put the placeholder text [angle] in the description. We can change it whenever we decide. The specification thing said it could be anything other than 0 or 180.


<img src="https://media.giphy.com/media/11TU6Q1wz3UkWk/giphy.gif"/>


Add:
        "summary": "Get all the provisioning services in a subscription.",
        "description": "Get all the provisioning services in a subscription.",

Remove:
"consumes": [],
"produces": ["application/json"],


This is Zsh running the oh-my-zsh framework, with the theme `powerlevel-9k` installed. The terminal emulator is termite, using the font `Inconsolata for Powerline`, and a slightly custom colorscheme created using a glorious website called [terminal.sexy](http://terminal.sexy). Zsh config file [here](https://github.com/C7C8/Dotfiles/blob/sathanas/zsh/zshrc), and the termite config file is [here](https://github.com/C7C8/Dotfiles/blob/sathanas/termite/config).


This is test commit


Add content to new pages


there is an another way in python to have "private" variables with getters/setters - [http://www.python-course.eu/python3_properties.php](url)


"description": "This is a synchronous operation. The body contains a JSON-serialized array of the metadata from all the provisioning services in the subscription.",


You removed the duplicate term setting, but the other line sets the terminal to 'screen-25**5**color'


Скрипт для копирования RGE формата в другую директорию с лимитами по валюте/сумме по полю 32A


awesome, true. I saw the other day that submit() was returning a future and I thought we don't really return anything like that, didn't stop to think that this would unnecessarily createa a future. Wonder if was just returning `null`


Commenting/Modifying the file


不要好了

這一段都移除掉
要改都在 synonym 裡面去針對字串做處理
不然會在其他地方出問題


shouldn't this be And() not Or()?


![](https://github.trello.services/images/mini-trello-icon.png) [99877: Save kayako ticketmaskid as ticket ref.](https://trello.com/c/p7HLMCzO/4104-99877-save-kayako-ticketmaskid-as-ticket-ref)


Memory Savings. GC taking less time to clear stuff that won't be there baby
<img src="https://media.giphy.com/media/3ornkdtVzQfIRpwfug/giphy.gif"/>


Moooo


DRY - don't repeat yourself


that's American influence on me.   proper English is se, sorry


@afgane This seems prone to a race condition (if there are two parallel launches in the same network)?


Hi Lukas,
unless I missed out something in your patches,
this is not the actual voltage table for it, so as https://github.com/TeamNexus/android_kernel_samsung_exynos7420/commit/202ed2e8a255132ea7971ecef830f5e649d37315
The real voltage table is here: https://github.com/TeamNexus/android_kernel_samsung_exynos7420/blob/nx-8.0/arch/arm64/mach-exynos/include/mach/asv-exynos7420.h

The other changes looks great tho, hope this helps.
Keep it up, cheers.

Frank


we should've kept Minut for Danish influence.


Jesse Hooke ReadMe.txt


Попробуй вместо `<td>` в этой строке использовать `<th>`


Remove:
"consumes": [],
"produces": ["application/json"],

Add:
        "summary": "Get the list of valid SKUs for a provisioning service.",
        "description": "Get the list of valid SKUs for a provisioning service.",


check this - might be a spacing issue


thanks for this, just was trying to figure out why there was no space between the facet name and the double chevron in the "more_facets_link" in my sufia 7.3, this fixes it in hyrax already.


Ok. I'm still a bad person though.


@mmastand Did I goof this and add .'s back in that you had removed?


@transfluxus nen checkpoint? eventuell unter v4 speichern?


"description": "This is a synchronous operation. The body contains a JSON-serialized array of the valid SKUs for this provisioning service.",


spotted bug #1-php
<?php the_header_image_tag(); ?>


use "...".format(...) or you can use new python 3.6 feature called f-strings [https://docs.python.org/3/reference/lexical_analysis.html#f-strings](url). Also you should use os.path module for more portability


Better not commit `node_modules`.


Nope, they needed to be there.


It may be insecure to place the pid file in /tmp, since it's world readable: https://www.stigviewer.com/stig/apache_server_2.2windows/2015-08-27/finding/V-26305

We could place it in a custom directory within /var/run/cloudlaunch as suggested here: https://serverfault.com/questions/159334/what-permission-to-write-pid-file-in-var-run

Or we could place it in the cloudlaunch installation folder I guess.


For safety you could restrict this function to only when in off mode.


Done in a59af1597759959e7065037eea35f434bdd3b473. Thanks!


not working in compile PGB =[

"/tmp/gimlet/22137080/2788568/www_android/project/cordova/plugins/cordova-plugin-caribe-laser-barcode-scanner/src/android/libs/ScanSDK.jar" not found!


Replace all instances with "ProvisioningServiceDesciptionListResult".


this is example


This commit fixes CVE-2017-1000249


https://www.ffmpeg.org/ffmpeg.html

https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/speech-synthesis-markup-language-ssml-reference#audio


what?


I'm not sure if you'll agree to this, @palazzem. If we short-circuit the configuration block here we prevent options like `debug: true` from being set.


Remove:
"consumes": ["application/json"],
"produces": ["application/json"],

Add:
        "summary": "Check if a provisioning service name is available.",
        "description": "Check if a provisioning service name is available.",


An interesting remark in the code. Consider having a look at the SafeMath library. It helps avoid overflow/underflow and other issues. I'm very curious about what came up in the unit tests because this feels like a bit of a workaround.


Add:
    "description": "Set the name parameter in the OperationInputs structure to the name of the provisioning service to check.",


Second test.

Rules with three conditions, two on flag value, one on flag lastupdated dx executes as expected.

Here's the transcript:
```
Tue Sep  5 21:24:17 CEST 2017: Testing v2.04.73
Tue Sep  5 21:24:17 CEST 2017: /sensors/4: {
  "config": {
    "on": true,
    "reachable": true
  },
  "etag": "65b10ae72e5d238670bd27229ada42d9",
  "manufacturername": "homebridge-hue",
  "modelid": "CLIPGenericFlag",
  "name": "Test 1",
  "state": {
    "flag": false
  },
  "swversion": "1",
  "type": "CLIPGenericFlag",
  "uniqueid": "/sensors/1"
}
Tue Sep  5 21:24:17 CEST 2017: /sensors/5: {
  "config": {
    "on": true,
    "reachable": true
  },
  "etag": "65b10ae72e5d238670bd27229ada42d9",
  "manufacturername": "homebridge-hue",
  "modelid": "CLIPGenericFlag",
  "name": "Test 2",
  "state": {
    "flag": false
  },
  "swversion": "1",
  "type": "CLIPGenericFlag",
  "uniqueid": "/sensors/2"
}
Tue Sep  5 21:24:17 CEST 2017: /rules/5: {
  "actions": [
    {
      "address": "/groups/1/scenes/1/recall",
      "body": {},
      "method": "PUT"
    }
  ],
  "conditions": [
    {
      "address": "/sensors/4/state/flag",
      "operator": "eq",
      "value": "true"
    },
    {
      "address": "/sensors/4/state/lastupdated",
      "operator": "dx"
    },
    {
      "address": "/sensors/5/state/flag",
      "operator": "eq",
      "value": "true"
    }
  ],
  "created": "2017-09-05T19:24:17",
  "etag": "65b10ae72e5d238670bd27229ada42d9",
  "lasttriggered": "none",
  "name": "Test On",
  "owner": "philipshue",
  "periodic": 0,
  "status": "enabled",
  "timestriggered": 0
}
Tue Sep  5 21:24:18 CEST 2017: /rules/6: {
  "actions": [
    {
      "address": "/groups/1/scenes/2/recall",
      "body": {},
      "method": "PUT"
    }
  ],
  "conditions": [
    {
      "address": "/sensors/4/state/flag",
      "operator": "eq",
      "value": "false"
    },
    {
      "address": "/sensors/4/state/lastupdated",
      "operator": "dx"
    },
    {
      "address": "/sensors/5/state/flag",
      "operator": "eq",
      "value": "true"
    }
  ],
  "created": "2017-09-05T19:24:17",
  "etag": "65b10ae72e5d238670bd27229ada42d9",
  "lasttriggered": "none",
  "name": "Test Off",
  "owner": "philipshue",
  "periodic": 0,
  "status": "enabled",
  "timestriggered": 0
}
Tue Sep  5 21:24:18 CEST 2017: /sensors/4/state: {"lastupdated": , "flag": false}
Tue Sep  5 21:24:18 CEST 2017: /sensors/5/state: {"lastupdated": , "flag": false}
Tue Sep  5 21:24:18 CEST 2017: /rules/5: {"lasttriggered": "none", "timestriggered": 0}
Tue Sep  5 21:24:18 CEST 2017: /rules/6: {"lasttriggered": "none", "timestriggered": 0}

Tue Sep  5 21:24:22 CEST 2017: /sensors/4/state: set flag to false...
Tue Sep  5 21:24:23 CEST 2017: /sensors/4/state: {"lastupdated": "2017-09-05T19:24:22", "flag": false}
Tue Sep  5 21:24:23 CEST 2017: /sensors/5/state: {"lastupdated": , "flag": false}
Tue Sep  5 21:24:23 CEST 2017: /rules/5: {"lasttriggered": "none", "timestriggered": 0}
Tue Sep  5 21:24:23 CEST 2017: /rules/6: {"lasttriggered": "none", "timestriggered": 0}

Tue Sep  5 21:24:27 CEST 2017: /sensors/4/state: set flag to false...
Tue Sep  5 21:24:29 CEST 2017: /sensors/4/state: {"lastupdated": "2017-09-05T19:24:27", "flag": false}
Tue Sep  5 21:24:29 CEST 2017: /sensors/5/state: {"lastupdated": , "flag": false}
Tue Sep  5 21:24:29 CEST 2017: /rules/5: {"lasttriggered": "none", "timestriggered": 0}
Tue Sep  5 21:24:29 CEST 2017: /rules/6: {"lasttriggered": "none", "timestriggered": 0}

Tue Sep  5 21:24:33 CEST 2017: /sensors/4/state: set flag to true...
Tue Sep  5 21:24:34 CEST 2017: /sensors/4/state: {"lastupdated": "2017-09-05T19:24:33", "flag": true}
Tue Sep  5 21:24:34 CEST 2017: /sensors/5/state: {"lastupdated": , "flag": false}
Tue Sep  5 21:24:34 CEST 2017: /rules/5: {"lasttriggered": "none", "timestriggered": 0}
Tue Sep  5 21:24:34 CEST 2017: /rules/6: {"lasttriggered": "none", "timestriggered": 0}

Tue Sep  5 21:24:38 CEST 2017: /sensors/4/state: set flag to true...
Tue Sep  5 21:24:39 CEST 2017: /sensors/4/state: {"lastupdated": "2017-09-05T19:24:38", "flag": true}
Tue Sep  5 21:24:40 CEST 2017: /sensors/5/state: {"lastupdated": , "flag": false}
Tue Sep  5 21:24:40 CEST 2017: /rules/5: {"lasttriggered": "none", "timestriggered": 0}
Tue Sep  5 21:24:40 CEST 2017: /rules/6: {"lasttriggered": "none", "timestriggered": 0}

Tue Sep  5 21:24:44 CEST 2017: /sensors/5/state: set flag to false...
Tue Sep  5 21:24:45 CEST 2017: /sensors/4/state: {"lastupdated": "2017-09-05T19:24:38", "flag": true}
Tue Sep  5 21:24:45 CEST 2017: /sensors/5/state: {"lastupdated": "2017-09-05T19:24:44", "flag": false}
Tue Sep  5 21:24:45 CEST 2017: /rules/5: {"lasttriggered": "none", "timestriggered": 0}
Tue Sep  5 21:24:45 CEST 2017: /rules/6: {"lasttriggered": "none", "timestriggered": 0}

Tue Sep  5 21:24:49 CEST 2017: /sensors/5/state: set flag to false...
Tue Sep  5 21:24:50 CEST 2017: /sensors/4/state: {"lastupdated": "2017-09-05T19:24:38", "flag": true}
Tue Sep  5 21:24:50 CEST 2017: /sensors/5/state: {"lastupdated": "2017-09-05T19:24:49", "flag": false}
Tue Sep  5 21:24:51 CEST 2017: /rules/5: {"lasttriggered": "none", "timestriggered": 0}
Tue Sep  5 21:24:51 CEST 2017: /rules/6: {"lasttriggered": "none", "timestriggered": 0}

Tue Sep  5 21:24:55 CEST 2017: /sensors/5/state: set flag to true...
Tue Sep  5 21:24:56 CEST 2017: /sensors/4/state: {"lastupdated": "2017-09-05T19:24:38", "flag": true}
Tue Sep  5 21:24:56 CEST 2017: /sensors/5/state: {"lastupdated": "2017-09-05T19:24:55", "flag": true}
Tue Sep  5 21:24:56 CEST 2017: /rules/5: {"lasttriggered": "none", "timestriggered": 0}
Tue Sep  5 21:24:56 CEST 2017: /rules/6: {"lasttriggered": "none", "timestriggered": 0}

Tue Sep  5 21:25:00 CEST 2017: /sensors/5/state: set flag to true...
Tue Sep  5 21:25:01 CEST 2017: /sensors/4/state: {"lastupdated": "2017-09-05T19:24:38", "flag": true}
Tue Sep  5 21:25:01 CEST 2017: /sensors/5/state: {"lastupdated": "2017-09-05T19:25:00", "flag": true}
Tue Sep  5 21:25:01 CEST 2017: /rules/5: {"lasttriggered": "none", "timestriggered": 0}
Tue Sep  5 21:25:02 CEST 2017: /rules/6: {"lasttriggered": "none", "timestriggered": 0}

Tue Sep  5 21:25:06 CEST 2017: /sensors/4/state: set flag to false...
Tue Sep  5 21:25:07 CEST 2017: /sensors/4/state: {"lastupdated": "2017-09-05T19:25:06", "flag": false}
Tue Sep  5 21:25:07 CEST 2017: /sensors/5/state: {"lastupdated": "2017-09-05T19:25:00", "flag": true}
Tue Sep  5 21:25:07 CEST 2017: /rules/5: {"lasttriggered": "none", "timestriggered": 0}
Tue Sep  5 21:25:07 CEST 2017: /rules/6: {"lasttriggered": "2017-09-05T21:25:06", "timestriggered": 1}

Tue Sep  5 21:25:11 CEST 2017: /sensors/4/state: set flag to false...
Tue Sep  5 21:25:12 CEST 2017: /sensors/4/state: {"lastupdated": "2017-09-05T19:25:11", "flag": false}
Tue Sep  5 21:25:12 CEST 2017: /sensors/5/state: {"lastupdated": "2017-09-05T19:25:00", "flag": true}
Tue Sep  5 21:25:12 CEST 2017: /rules/5: {"lasttriggered": "none", "timestriggered": 0}
Tue Sep  5 21:25:12 CEST 2017: /rules/6: {"lasttriggered": "2017-09-05T21:25:11", "timestriggered": 2}

Tue Sep  5 21:25:16 CEST 2017: /sensors/4/state: set flag to true...
Tue Sep  5 21:25:18 CEST 2017: /sensors/4/state: {"lastupdated": "2017-09-05T19:25:17", "flag": true}
Tue Sep  5 21:25:18 CEST 2017: /sensors/5/state: {"lastupdated": "2017-09-05T19:25:00", "flag": true}
Tue Sep  5 21:25:18 CEST 2017: /rules/5: {"lasttriggered": "2017-09-05T21:25:17", "timestriggered": 1}
Tue Sep  5 21:25:18 CEST 2017: /rules/6: {"lasttriggered": "2017-09-05T21:25:11", "timestriggered": 2}

Tue Sep  5 21:25:22 CEST 2017: /sensors/4/state: set flag to true...
Tue Sep  5 21:25:23 CEST 2017: /sensors/4/state: {"lastupdated": "2017-09-05T19:25:22", "flag": true}
Tue Sep  5 21:25:23 CEST 2017: /sensors/5/state: {"lastupdated": "2017-09-05T19:25:00", "flag": true}
Tue Sep  5 21:25:23 CEST 2017: /rules/5: {"lasttriggered": "2017-09-05T21:25:22", "timestriggered": 2}
Tue Sep  5 21:25:23 CEST 2017: /rules/6: {"lasttriggered": "2017-09-05T21:25:11", "timestriggered": 2}
```
And the event log:
```
Tue Sep 05 2017 21:24:22: /sensors/4/state: {"lastupdated":"2017-09-05T19:24:22"}
Tue Sep 05 2017 21:24:27: /sensors/4/state: {"lastupdated":"2017-09-05T19:24:27"}
Tue Sep 05 2017 21:24:33: /sensors/4/state: {"flag":true,"lastupdated":"2017-09-05T19:24:33"}
Tue Sep 05 2017 21:24:33: /sensors/4/state: {"lastupdated":"2017-09-05T19:24:33"}
Tue Sep 05 2017 21:24:38: /sensors/4/state: {"lastupdated":"2017-09-05T19:24:38"}
Tue Sep 05 2017 21:24:44: /sensors/5/state: {"lastupdated":"2017-09-05T19:24:44"}
Tue Sep 05 2017 21:24:49: /sensors/5/state: {"lastupdated":"2017-09-05T19:24:49"}
Tue Sep 05 2017 21:24:55: /sensors/5/state: {"flag":true,"lastupdated":"2017-09-05T19:24:55"}
Tue Sep 05 2017 21:24:55: /sensors/5/state: {"lastupdated":"2017-09-05T19:24:55"}
Tue Sep 05 2017 21:25:00: /sensors/5/state: {"lastupdated":"2017-09-05T19:25:00"}
Tue Sep 05 2017 21:25:06: /sensors/4/state: {"flag":false,"lastupdated":"2017-09-05T19:25:06"}
Tue Sep 05 2017 21:25:06: /sensors/4/state: {"lastupdated":"2017-09-05T19:25:06"}
Tue Sep 05 2017 21:25:06: /lights/1/state: {"on":true}
Tue Sep 05 2017 21:25:06: /lights/1/state: {"colormode":"ct"}
Tue Sep 05 2017 21:25:06: /lights/1/state: {"ct":250}
Tue Sep 05 2017 21:25:06: /groups/1/state: {"any_on":true}
Tue Sep 05 2017 21:25:06: /groups/1/scenes/2
Tue Sep 05 2017 21:25:11: /sensors/4/state: {"lastupdated":"2017-09-05T19:25:11"}
Tue Sep 05 2017 21:25:11: /groups/1/scenes/2
Tue Sep 05 2017 21:25:17: /sensors/4/state: {"flag":true,"lastupdated":"2017-09-05T19:25:17"}
Tue Sep 05 2017 21:25:17: /sensors/4/state: {"lastupdated":"2017-09-05T19:25:17"}
Tue Sep 05 2017 21:25:17: /lights/1/state: {"ct":454}
Tue Sep 05 2017 21:25:17: /groups/1/scenes/1
Tue Sep 05 2017 21:25:22: /sensors/4/state: {"lastupdated":"2017-09-05T19:25:22"}
Tue Sep 05 2017 21:25:22: /groups/1/scenes/1
Tue Sep 05 2017 21:25:23: {"e":"deleted","r":"sensors","sensor":{"id":"4"},"t":"event"}
Tue Sep 05 2017 21:25:24: {"e":"deleted","r":"sensors","sensor":{"id":"5"},"t":"event"}
Tue Sep 05 2017 21:25:43: /lights/1/state: {"colormode":"xy"}
```


@AlexGStapleton Please, can you pull develop and test as well as doing a review on the above. Thanks. Will push as soon as you've okayed it.


"description": "This is a synchronous operation. The body contains a JSON-serialized response that specifies whether the provisioning service name is available. If the name is not available, the body contains the reason.",


A bit of a style thing. I would `if(!allowed) revert()` and then do away with the `{} else {}` blocks.


應該是不用 `coordinateLonLat`
用 [geolib.sexagesimal2decimal](https://github.com/manuelbieh/Geolib#geolibsexagesimal2decimalstring-coord) 就可以了

```js
import {sexagesimal2decimal} from 'geolib';

const replaceComma = word => (
  word.replace(/,/, '° ')
    .replace(/,/, '\' ')
);

resolve: data => (/,/g).test(data[latKey]) ?
  sexagesimal2decimal(`${replaceComma(data[latKey])}" N`) :
  parseFloat(data[latKey])
```


I am sure there is a way to fix whatever compiling issues you have without having to hacki libFLAC, which should be actually higly portable and configurable through Makefiles. Removing sys/param.h like that also probably breaks compilation elsewhere


Thank is work but : have new bug next button


- [ ] remove `.nyc_output` folder.
- [ ] remove `coordinateLonLat.js`


Add:
        "summary": "Get the security metadata for a provisioning service.",
        "description": "Get the security metadata for a provisioning service.",

Remove:

"consumes": [],
"produces": ["application/json"],


"description": "This is a synchronous operation. The body contains a JSON-serialized array of shared access policies, including keys, that you can use to access the provisioning service endpoints.",


Haha, good catch! Fixed in my latest commit 👍


Now it looks clear. Thanks.


Third test - toggle rules.  Works as expected.

Transcript:
```
ue Sep  5 21:33:52 CEST 2017: Testing v2.04.73
Tue Sep  5 21:33:52 CEST 2017: /sensors/6: {
  "config": {
    "on": true,
    "reachable": true
  },
  "etag": "70cf09b51a29b0c8706f5455e04be7fc",
  "manufacturername": "homebridge-hue",
  "modelid": "CLIPGenericFlag",
  "name": "Test 1",
  "state": {
    "flag": false
  },
  "swversion": "1",
  "type": "CLIPGenericFlag",
  "uniqueid": "/sensors/1"
}
Tue Sep  5 21:33:52 CEST 2017: /sensors/7: {
  "config": {
    "on": true,
    "reachable": true
  },
  "etag": "70cf09b51a29b0c8706f5455e04be7fc",
  "manufacturername": "homebridge-hue",
  "modelid": "CLIPGenericFlag",
  "name": "Test 2",
  "state": {
    "flag": false
  },
  "swversion": "1",
  "type": "CLIPGenericFlag",
  "uniqueid": "/sensors/2"
}
Tue Sep  5 21:33:53 CEST 2017: /rules/7: {
  "actions": [
    {
      "address": "/sensors/7/state",
      "body": {
        "flag": true
      },
      "method": "PUT"
    },
    {
      "address": "/groups/1/scenes/1/recall",
      "body": {},
      "method": "PUT"
    }
  ],
  "conditions": [
    {
      "address": "/sensors/6/state/flag",
      "operator": "eq",
      "value": "true"
    },
    {
      "address": "/sensors/6/state/lastupdated",
      "operator": "dx"
    },
    {
      "address": "/sensors/7/state/flag",
      "operator": "eq",
      "value": "false"
    }
  ],
  "created": "2017-09-05T19:33:53",
  "etag": "bce5d11c0fa64eac544423aa93b50cb7",
  "lasttriggered": "none",
  "name": "Test Toggle On",
  "owner": "philipshue",
  "periodic": 0,
  "status": "enabled",
  "timestriggered": 0
}
Tue Sep  5 21:33:53 CEST 2017: /rules/8: {
  "actions": [
    {
      "address": "/sensors/7/state",
      "body": {
        "flag": false
      },
      "method": "PUT"
    },
    {
      "address": "/groups/1/scenes/2/recall",
      "body": {},
      "method": "PUT"
    }
  ],
  "conditions": [
    {
      "address": "/sensors/6/state/flag",
      "operator": "eq",
      "value": "true"
    },
    {
      "address": "/sensors/6/state/lastupdated",
      "operator": "dx"
    },
    {
      "address": "/sensors/7/state/flag",
      "operator": "eq",
      "value": "true"
    }
  ],
  "created": "2017-09-05T19:33:53",
  "etag": "bce5d11c0fa64eac544423aa93b50cb7",
  "lasttriggered": "none",
  "name": "Test Toggle Off",
  "owner": "philipshue",
  "periodic": 0,
  "status": "enabled",
  "timestriggered": 0
}
Tue Sep  5 21:33:53 CEST 2017: /sensors/6/state: {"lastupdated": , "flag": false}
Tue Sep  5 21:33:53 CEST 2017: /sensors/7/state: {"lastupdated": , "flag": false}
Tue Sep  5 21:33:53 CEST 2017: /rules/7: {"lasttriggered": "none", "timestriggered": 0}
Tue Sep  5 21:33:53 CEST 2017: /rules/8: {"lasttriggered": "none", "timestriggered": 0}

Tue Sep  5 21:33:57 CEST 2017: /sensors/6/state: set flag to false...
Tue Sep  5 21:33:58 CEST 2017: /sensors/6/state: {"lastupdated": "2017-09-05T19:33:57", "flag": false}
Tue Sep  5 21:33:58 CEST 2017: /sensors/7/state: {"lastupdated": , "flag": false}
Tue Sep  5 21:33:59 CEST 2017: /rules/7: {"lasttriggered": "none", "timestriggered": 0}
Tue Sep  5 21:33:59 CEST 2017: /rules/8: {"lasttriggered": "none", "timestriggered": 0}

Tue Sep  5 21:34:03 CEST 2017: /sensors/6/state: set flag to false...
Tue Sep  5 21:34:04 CEST 2017: /sensors/6/state: {"lastupdated": "2017-09-05T19:34:03", "flag": false}
Tue Sep  5 21:34:04 CEST 2017: /sensors/7/state: {"lastupdated": , "flag": false}
Tue Sep  5 21:34:04 CEST 2017: /rules/7: {"lasttriggered": "none", "timestriggered": 0}
Tue Sep  5 21:34:04 CEST 2017: /rules/8: {"lasttriggered": "none", "timestriggered": 0}

Tue Sep  5 21:34:08 CEST 2017: /sensors/6/state: set flag to true...
Tue Sep  5 21:34:09 CEST 2017: /sensors/6/state: {"lastupdated": "2017-09-05T19:34:08", "flag": true}
Tue Sep  5 21:34:09 CEST 2017: /sensors/7/state: {"lastupdated": "2017-09-05T19:34:08", "flag": true}
Tue Sep  5 21:34:09 CEST 2017: /rules/7: {"lasttriggered": "2017-09-05T21:34:08", "timestriggered": 1}
Tue Sep  5 21:34:10 CEST 2017: /rules/8: {"lasttriggered": "none", "timestriggered": 0}

Tue Sep  5 21:34:14 CEST 2017: /sensors/6/state: set flag to true...
Tue Sep  5 21:34:15 CEST 2017: /sensors/6/state: {"lastupdated": "2017-09-05T19:34:14", "flag": true}
Tue Sep  5 21:34:15 CEST 2017: /sensors/7/state: {"lastupdated": "2017-09-05T19:34:14", "flag": false}
Tue Sep  5 21:34:15 CEST 2017: /rules/7: {"lasttriggered": "2017-09-05T21:34:08", "timestriggered": 1}
Tue Sep  5 21:34:15 CEST 2017: /rules/8: {"lasttriggered": "2017-09-05T21:34:14", "timestriggered": 1}

Tue Sep  5 21:34:19 CEST 2017: /sensors/6/state: set flag to false...
Tue Sep  5 21:34:20 CEST 2017: /sensors/6/state: {"lastupdated": "2017-09-05T19:34:19", "flag": false}
Tue Sep  5 21:34:20 CEST 2017: /sensors/7/state: {"lastupdated": "2017-09-05T19:34:14", "flag": false}
Tue Sep  5 21:34:20 CEST 2017: /rules/7: {"lasttriggered": "2017-09-05T21:34:08", "timestriggered": 1}
Tue Sep  5 21:34:20 CEST 2017: /rules/8: {"lasttriggered": "2017-09-05T21:34:14", "timestriggered": 1}

Tue Sep  5 21:34:24 CEST 2017: /sensors/6/state: set flag to false...
Tue Sep  5 21:34:26 CEST 2017: /sensors/6/state: {"lastupdated": "2017-09-05T19:34:25", "flag": false}
Tue Sep  5 21:34:26 CEST 2017: /sensors/7/state: {"lastupdated": "2017-09-05T19:34:14", "flag": false}
Tue Sep  5 21:34:26 CEST 2017: /rules/7: {"lasttriggered": "2017-09-05T21:34:08", "timestriggered": 1}
Tue Sep  5 21:34:26 CEST 2017: /rules/8: {"lasttriggered": "2017-09-05T21:34:14", "timestriggered": 1}

Tue Sep  5 21:34:30 CEST 2017: /sensors/6/state: set flag to true...
Tue Sep  5 21:34:31 CEST 2017: /sensors/6/state: {"lastupdated": "2017-09-05T19:34:30", "flag": true}
Tue Sep  5 21:34:31 CEST 2017: /sensors/7/state: {"lastupdated": "2017-09-05T19:34:30", "flag": true}
Tue Sep  5 21:34:31 CEST 2017: /rules/7: {"lasttriggered": "2017-09-05T21:34:30", "timestriggered": 2}
Tue Sep  5 21:34:31 CEST 2017: /rules/8: {"lasttriggered": "2017-09-05T21:34:14", "timestriggered": 1}

Tue Sep  5 21:34:35 CEST 2017: /sensors/6/state: set flag to true...
Tue Sep  5 21:34:37 CEST 2017: /sensors/6/state: {"lastupdated": "2017-09-05T19:34:35", "flag": true}
Tue Sep  5 21:34:37 CEST 2017: /sensors/7/state: {"lastupdated": "2017-09-05T19:34:35", "flag": false}
Tue Sep  5 21:34:37 CEST 2017: /rules/7: {"lasttriggered": "2017-09-05T21:34:30", "timestriggered": 2}
Tue Sep  5 21:34:37 CEST 2017: /rules/8: {"lasttriggered": "2017-09-05T21:34:35", "timestriggered": 2}
```
Event log:
```
Tue Sep 05 2017 21:33:57: /sensors/6/state: {"lastupdated":"2017-09-05T19:33:57"}
Tue Sep 05 2017 21:34:03: /sensors/6/state: {"lastupdated":"2017-09-05T19:34:03"}
Tue Sep 05 2017 21:34:08: /sensors/6/state: {"flag":true,"lastupdated":"2017-09-05T19:34:08"}
Tue Sep 05 2017 21:34:08: /sensors/6/state: {"lastupdated":"2017-09-05T19:34:08"}
Tue Sep 05 2017 21:34:08: /sensors/7/state: {"flag":true,"lastupdated":"2017-09-05T19:34:08"}
Tue Sep 05 2017 21:34:08: /sensors/7/state: {"lastupdated":"2017-09-05T19:34:08"}
Tue Sep 05 2017 21:34:08: /lights/1/state: {"colormode":"ct"}
Tue Sep 05 2017 21:34:08: /groups/1/scenes/1
Tue Sep 05 2017 21:34:14: /sensors/6/state: {"lastupdated":"2017-09-05T19:34:14"}
Tue Sep 05 2017 21:34:14: /sensors/7/state: {"flag":false,"lastupdated":"2017-09-05T19:34:14"}
Tue Sep 05 2017 21:34:14: /sensors/7/state: {"lastupdated":"2017-09-05T19:34:14"}
Tue Sep 05 2017 21:34:14: /lights/1/state: {"ct":250}
Tue Sep 05 2017 21:34:14: /groups/1/scenes/2
Tue Sep 05 2017 21:34:19: /sensors/6/state: {"flag":false,"lastupdated":"2017-09-05T19:34:19"}
Tue Sep 05 2017 21:34:19: /sensors/6/state: {"lastupdated":"2017-09-05T19:34:19"}
Tue Sep 05 2017 21:34:25: /sensors/6/state: {"lastupdated":"2017-09-05T19:34:25"}
Tue Sep 05 2017 21:34:30: /sensors/6/state: {"flag":true,"lastupdated":"2017-09-05T19:34:30"}
Tue Sep 05 2017 21:34:30: /sensors/6/state: {"lastupdated":"2017-09-05T19:34:30"}
Tue Sep 05 2017 21:34:30: /sensors/7/state: {"flag":true,"lastupdated":"2017-09-05T19:34:30"}
Tue Sep 05 2017 21:34:30: /sensors/7/state: {"lastupdated":"2017-09-05T19:34:30"}
Tue Sep 05 2017 21:34:30: /lights/1/state: {"ct":454}
Tue Sep 05 2017 21:34:31: /groups/1/scenes/1
Tue Sep 05 2017 21:34:35: /sensors/6/state: {"lastupdated":"2017-09-05T19:34:35"}
Tue Sep 05 2017 21:34:35: /sensors/7/state: {"flag":false,"lastupdated":"2017-09-05T19:34:35"}
Tue Sep 05 2017 21:34:35: /sensors/7/state: {"lastupdated":"2017-09-05T19:34:35"}
Tue Sep 05 2017 21:34:35: /lights/1/state: {"ct":250}
Tue Sep 05 2017 21:34:36: /groups/1/scenes/2
Tue Sep 05 2017 21:34:37: {"e":"deleted","r":"sensors","sensor":{"id":"6"},"t":"event"}
Tue Sep 05 2017 21:34:37: {"e":"deleted","r":"sensors","sensor":{"id":"7"},"t":"event"}
Tue Sep 05 2017 21:34:59: /lights/1/state: {"colormode":"xy"}
```


Add:
        "summary": "Get a shared access policy by name from a provisioning service.",
        "description": "Get a shared access policy by name from a provisioning service.",

Remove:
"consumes": [],
"produces": ["application/json"],


[R/plots-heatmap.R:5:2:](https://github.com/hbc/bcbioSingleCell/blob/a577a2c098c9690960d464350cb499af325dd69e/R/plots-heatmap.R#L5) *style:* **Commented code should be removed.**
```r
##'   ideas and code from: http://slowkow.com/notes/heatmap-tutorial/
 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```


Add:
"description": "The name of the resource group that contains the provisioning service.",


We have more targets than any conceivable emulator out there, targeting platforms as far back as Windows 95, and we have no such issues removing sys/param.h.


"description": "This is a synchronous operation. The body contains a JSON-serialized shared access policy, including keys, that you can use to access one or more provisioning service endpoints.",


edited more


By event do you mean the websocket event or internal events which are used by rules?

> The bad:

> When setting flag to its current value, a state changed event is now issued. However, it only contains lastupdated; I'd expect an event with both flag and lastupdated;

So flag should be treated like button events? I thought equal values should not yield events except button events.

> Indeed, a rule with two conditions, one on flag value and one on lastupdated dx, executes twice when setting the flag to a different value.

That's really bad, can you please provide the example rule?

> Lastupdated is changed after (re) starting deCONZ (presumably when setting the flag to false). The Hue bridge sets the value to "none".

Yes it tries to be clever and restores the last known state, modifying it if it is too fresh (2 minutes).

https://github.com/dresden-elektronik/deconz-rest-plugin/blob/master/sensor.cpp#L605

It could also be set to *none* but then the information is lost, some sensors only send a value after hours, so if the raspberry is restarted after an update it would not show valid data. (the example might be weak ;)


```js
var childPKProp;
if (arePhysical) {
  childPkProp = ChildWLModel.attributes[ChildWLModel.primaryKey].columnName;
}
else {
  childPkProp = ChildWLModel.primaryKey;
}
```


TeamCity Code :: 1. Development :: DDK :: Feature [Build 449](http://mp-ci.centralus.cloudapp.azure.com/viewLog.html?buildId=30251&buildTypeId=Code_Development_Ddk_Feature) is now running


такое не делай.


@brianarnold789 Do you think you will be able to build and update the module at https://www.magentocommerce.com/magento-connect/litle-payments.html so the Magento Downloader can automatically upgrade without manual code insertions?


ширину не задавай фиксированую


TeamCity Code :: 1. Development :: DDK :: Feature [Build 449](http://mp-ci.centralus.cloudapp.azure.com/viewLog.html?buildId=30251&buildTypeId=Code_Development_Ddk_Feature) outcome was **SUCCESS**
Summary: Tests passed: 65 Build time: 00:01:20


ну ширину тут тоже не надо задавать.. т.к блок должен тянутся..


Final test: rules with two conditions, both on flag value (no dx) execute as expected.

Transscript:
```
Tue Sep  5 21:40:00 CEST 2017: Testing v2.04.73
Tue Sep  5 21:40:00 CEST 2017: /sensors/8: {
  "config": {
    "on": true,
    "reachable": true
  },
  "etag": "a8734ffa7e3431fb855de8b3ff6c7d31",
  "manufacturername": "homebridge-hue",
  "modelid": "CLIPGenericFlag",
  "name": "Test 1",
  "state": {
    "flag": false
  },
  "swversion": "1",
  "type": "CLIPGenericFlag",
  "uniqueid": "/sensors/1"
}
Tue Sep  5 21:40:00 CEST 2017: /sensors/9: {
  "config": {
    "on": true,
    "reachable": true
  },
  "etag": "a8734ffa7e3431fb855de8b3ff6c7d31",
  "manufacturername": "homebridge-hue",
  "modelid": "CLIPGenericFlag",
  "name": "Test 2",
  "state": {
    "flag": false
  },
  "swversion": "1",
  "type": "CLIPGenericFlag",
  "uniqueid": "/sensors/2"
}
Tue Sep  5 21:40:00 CEST 2017: /rules/9: {
  "actions": [
    {
      "address": "/groups/1/scenes/1/recall",
      "body": {},
      "method": "PUT"
    }
  ],
  "conditions": [
    {
      "address": "/sensors/8/state/flag",
      "operator": "eq",
      "value": "true"
    },
    {
      "address": "/sensors/9/state/flag",
      "operator": "eq",
      "value": "true"
    }
  ],
  "created": "2017-09-05T19:40:00",
  "etag": "a8734ffa7e3431fb855de8b3ff6c7d31",
  "lasttriggered": "none",
  "name": "Test On",
  "owner": "philipshue",
  "periodic": 0,
  "status": "enabled",
  "timestriggered": 0
}
Tue Sep  5 21:40:00 CEST 2017: /rules/10: {
  "actions": [
    {
      "address": "/groups/1/scenes/2/recall",
      "body": {},
      "method": "PUT"
    }
  ],
  "conditions": [
    {
      "address": "/sensors/8/state/flag",
      "operator": "eq",
      "value": "false"
    },
    {
      "address": "/sensors/9/state/flag",
      "operator": "eq",
      "value": "true"
    }
  ],
  "created": "2017-09-05T19:40:00",
  "etag": "a8734ffa7e3431fb855de8b3ff6c7d31",
  "lasttriggered": "none",
  "name": "Test Off",
  "owner": "philipshue",
  "periodic": 0,
  "status": "enabled",
  "timestriggered": 0
}
Tue Sep  5 21:40:00 CEST 2017: /sensors/8/state: {"lastupdated": , "flag": false}
Tue Sep  5 21:40:00 CEST 2017: /sensors/9/state: {"lastupdated": , "flag": false}
Tue Sep  5 21:40:01 CEST 2017: /rules/9: {"lasttriggered": "none", "timestriggered": 0}
Tue Sep  5 21:40:01 CEST 2017: /rules/10: {"lasttriggered": "none", "timestriggered": 0}

Tue Sep  5 21:40:05 CEST 2017: /sensors/8/state: set flag to false...
Tue Sep  5 21:40:06 CEST 2017: /sensors/8/state: {"lastupdated": "2017-09-05T19:40:05", "flag": false}
Tue Sep  5 21:40:06 CEST 2017: /sensors/9/state: {"lastupdated": , "flag": false}
Tue Sep  5 21:40:06 CEST 2017: /rules/9: {"lasttriggered": "none", "timestriggered": 0}
Tue Sep  5 21:40:06 CEST 2017: /rules/10: {"lasttriggered": "none", "timestriggered": 0}

Tue Sep  5 21:40:10 CEST 2017: /sensors/8/state: set flag to false...
Tue Sep  5 21:40:11 CEST 2017: /sensors/8/state: {"lastupdated": "2017-09-05T19:40:10", "flag": false}
Tue Sep  5 21:40:11 CEST 2017: /sensors/9/state: {"lastupdated": , "flag": false}
Tue Sep  5 21:40:11 CEST 2017: /rules/9: {"lasttriggered": "none", "timestriggered": 0}
Tue Sep  5 21:40:12 CEST 2017: /rules/10: {"lasttriggered": "none", "timestriggered": 0}

Tue Sep  5 21:40:16 CEST 2017: /sensors/8/state: set flag to true...
Tue Sep  5 21:40:17 CEST 2017: /sensors/8/state: {"lastupdated": "2017-09-05T19:40:16", "flag": true}
Tue Sep  5 21:40:17 CEST 2017: /sensors/9/state: {"lastupdated": , "flag": false}
Tue Sep  5 21:40:17 CEST 2017: /rules/9: {"lasttriggered": "none", "timestriggered": 0}
Tue Sep  5 21:40:17 CEST 2017: /rules/10: {"lasttriggered": "none", "timestriggered": 0}

Tue Sep  5 21:40:21 CEST 2017: /sensors/8/state: set flag to true...
Tue Sep  5 21:40:22 CEST 2017: /sensors/8/state: {"lastupdated": "2017-09-05T19:40:21", "flag": true}
Tue Sep  5 21:40:22 CEST 2017: /sensors/9/state: {"lastupdated": , "flag": false}
Tue Sep  5 21:40:22 CEST 2017: /rules/9: {"lasttriggered": "none", "timestriggered": 0}
Tue Sep  5 21:40:22 CEST 2017: /rules/10: {"lasttriggered": "none", "timestriggered": 0}

Tue Sep  5 21:40:26 CEST 2017: /sensors/9/state: set flag to false...
Tue Sep  5 21:40:28 CEST 2017: /sensors/8/state: {"lastupdated": "2017-09-05T19:40:21", "flag": true}
Tue Sep  5 21:40:28 CEST 2017: /sensors/9/state: {"lastupdated": "2017-09-05T19:40:26", "flag": false}
Tue Sep  5 21:40:28 CEST 2017: /rules/9: {"lasttriggered": "none", "timestriggered": 0}
Tue Sep  5 21:40:28 CEST 2017: /rules/10: {"lasttriggered": "none", "timestriggered": 0}

Tue Sep  5 21:40:32 CEST 2017: /sensors/9/state: set flag to false...
Tue Sep  5 21:40:33 CEST 2017: /sensors/8/state: {"lastupdated": "2017-09-05T19:40:21", "flag": true}
Tue Sep  5 21:40:33 CEST 2017: /sensors/9/state: {"lastupdated": "2017-09-05T19:40:32", "flag": false}
Tue Sep  5 21:40:33 CEST 2017: /rules/9: {"lasttriggered": "none", "timestriggered": 0}
Tue Sep  5 21:40:33 CEST 2017: /rules/10: {"lasttriggered": "none", "timestriggered": 0}

Tue Sep  5 21:40:37 CEST 2017: /sensors/9/state: set flag to true...
Tue Sep  5 21:40:38 CEST 2017: /sensors/8/state: {"lastupdated": "2017-09-05T19:40:21", "flag": true}
Tue Sep  5 21:40:38 CEST 2017: /sensors/9/state: {"lastupdated": "2017-09-05T19:40:37", "flag": true}
Tue Sep  5 21:40:39 CEST 2017: /rules/9: {"lasttriggered": "2017-09-05T21:40:37", "timestriggered": 1}
Tue Sep  5 21:40:39 CEST 2017: /rules/10: {"lasttriggered": "none", "timestriggered": 0}

Tue Sep  5 21:40:43 CEST 2017: /sensors/9/state: set flag to true...
Tue Sep  5 21:40:44 CEST 2017: /sensors/8/state: {"lastupdated": "2017-09-05T19:40:21", "flag": true}
Tue Sep  5 21:40:44 CEST 2017: /sensors/9/state: {"lastupdated": "2017-09-05T19:40:43", "flag": true}
Tue Sep  5 21:40:44 CEST 2017: /rules/9: {"lasttriggered": "2017-09-05T21:40:37", "timestriggered": 1}
Tue Sep  5 21:40:44 CEST 2017: /rules/10: {"lasttriggered": "none", "timestriggered": 0}

Tue Sep  5 21:40:48 CEST 2017: /sensors/8/state: set flag to false...
Tue Sep  5 21:40:49 CEST 2017: /sensors/8/state: {"lastupdated": "2017-09-05T19:40:48", "flag": false}
Tue Sep  5 21:40:49 CEST 2017: /sensors/9/state: {"lastupdated": "2017-09-05T19:40:43", "flag": true}
Tue Sep  5 21:40:49 CEST 2017: /rules/9: {"lasttriggered": "2017-09-05T21:40:37", "timestriggered": 1}
Tue Sep  5 21:40:49 CEST 2017: /rules/10: {"lasttriggered": "2017-09-05T21:40:48", "timestriggered": 1}

Tue Sep  5 21:40:53 CEST 2017: /sensors/8/state: set flag to false...
Tue Sep  5 21:40:55 CEST 2017: /sensors/8/state: {"lastupdated": "2017-09-05T19:40:54", "flag": false}
Tue Sep  5 21:40:55 CEST 2017: /sensors/9/state: {"lastupdated": "2017-09-05T19:40:43", "flag": true}
Tue Sep  5 21:40:55 CEST 2017: /rules/9: {"lasttriggered": "2017-09-05T21:40:37", "timestriggered": 1}
Tue Sep  5 21:40:55 CEST 2017: /rules/10: {"lasttriggered": "2017-09-05T21:40:48", "timestriggered": 1}

Tue Sep  5 21:40:59 CEST 2017: /sensors/8/state: set flag to true...
Tue Sep  5 21:41:00 CEST 2017: /sensors/8/state: {"lastupdated": "2017-09-05T19:40:59", "flag": true}
Tue Sep  5 21:41:00 CEST 2017: /sensors/9/state: {"lastupdated": "2017-09-05T19:40:43", "flag": true}
Tue Sep  5 21:41:00 CEST 2017: /rules/9: {"lasttriggered": "2017-09-05T21:40:59", "timestriggered": 2}
Tue Sep  5 21:41:00 CEST 2017: /rules/10: {"lasttriggered": "2017-09-05T21:40:48", "timestriggered": 1}

Tue Sep  5 21:41:04 CEST 2017: /sensors/8/state: set flag to true...
Tue Sep  5 21:41:05 CEST 2017: /sensors/8/state: {"lastupdated": "2017-09-05T19:41:04", "flag": true}
Tue Sep  5 21:41:06 CEST 2017: /sensors/9/state: {"lastupdated": "2017-09-05T19:40:43", "flag": true}
Tue Sep  5 21:41:06 CEST 2017: /rules/9: {"lasttriggered": "2017-09-05T21:40:59", "timestriggered": 2}
Tue Sep  5 21:41:06 CEST 2017: /rules/10: {"lasttriggered": "2017-09-05T21:40:48", "timestriggered": 1}
```

Log
```
Tue Sep 05 2017 21:40:05: /sensors/8/state: {"lastupdated":"2017-09-05T19:40:05"}
Tue Sep 05 2017 21:40:10: /sensors/8/state: {"lastupdated":"2017-09-05T19:40:10"}
Tue Sep 05 2017 21:40:16: /sensors/8/state: {"flag":true,"lastupdated":"2017-09-05T19:40:16"}
Tue Sep 05 2017 21:40:16: /sensors/8/state: {"lastupdated":"2017-09-05T19:40:16"}
Tue Sep 05 2017 21:40:21: /sensors/8/state: {"lastupdated":"2017-09-05T19:40:21"}
Tue Sep 05 2017 21:40:26: /sensors/9/state: {"lastupdated":"2017-09-05T19:40:26"}
Tue Sep 05 2017 21:40:32: /sensors/9/state: {"lastupdated":"2017-09-05T19:40:32"}
Tue Sep 05 2017 21:40:37: /sensors/9/state: {"flag":true,"lastupdated":"2017-09-05T19:40:37"}
Tue Sep 05 2017 21:40:37: /sensors/9/state: {"lastupdated":"2017-09-05T19:40:37"}
Tue Sep 05 2017 21:40:37: /lights/1/state: {"colormode":"ct"}
Tue Sep 05 2017 21:40:37: /lights/1/state: {"ct":454}
Tue Sep 05 2017 21:40:37: /groups/1/scenes/1
Tue Sep 05 2017 21:40:43: /sensors/9/state: {"lastupdated":"2017-09-05T19:40:43"}
Tue Sep 05 2017 21:40:48: /sensors/8/state: {"flag":false,"lastupdated":"2017-09-05T19:40:48"}
Tue Sep 05 2017 21:40:48: /sensors/8/state: {"lastupdated":"2017-09-05T19:40:48"}
Tue Sep 05 2017 21:40:48: /lights/1/state: {"ct":250}
Tue Sep 05 2017 21:40:48: /groups/1/scenes/2
Tue Sep 05 2017 21:40:54: /sensors/8/state: {"lastupdated":"2017-09-05T19:40:54"}
Tue Sep 05 2017 21:40:59: /sensors/8/state: {"flag":true,"lastupdated":"2017-09-05T19:40:59"}
Tue Sep 05 2017 21:40:59: /sensors/8/state: {"lastupdated":"2017-09-05T19:40:59"}
Tue Sep 05 2017 21:40:59: /lights/1/state: {"ct":454}
Tue Sep 05 2017 21:40:59: /groups/1/scenes/1
Tue Sep 05 2017 21:41:04: /sensors/8/state: {"lastupdated":"2017-09-05T19:41:04"}
Tue Sep 05 2017 21:41:06: {"e":"deleted","r":"sensors","sensor":{"id":"8"},"t":"event"}
Tue Sep 05 2017 21:41:06: {"e":"deleted","r":"sensors","sensor":{"id":"9"},"t":"event"}
```


вложенность до 2-х лучше делать
и что такой за класс "два"?


No, not without a redirector.
This is really a show-stopper, I
see no use-cases for that no matter
how hard I think of it. :)


зачем тебе этот враппер?


что первый?


лого в ссылке должен быть


не пиши капсом..


что big? small?
меняй названия


это не параграфы...


Sorry for that!


br не злоупотребляй. Без него можно обходиться.


Created multidev environment [fwg8#ci-1](https://dashboard.pantheon.io/sites/bc49d219-7e11-4e3b-9111-f31c41ea62d4#ci-1).

[![Visit Site](https://raw.githubusercontent.com/pantheon-systems/ci-drops-8/0.1.0/data/img/visit-site-36.png)](https://ci-1-fwg8.pantheonsite.io/)


@goldenapples May I delete https://github.com/wp-shortcake/shortcake/tree/maser ?


No worries! That's what the automated tests are there for 👍


Pier side change is wrong, because german mounts can observe some degrees in both sides of meridian with the telescope either west or east of pier.

Also in circumpolar stars, both sides of the pier are possible, but each one implies different dome positions.


We're just starting to run this code. Why do I need to have the sysroot set to use an alternate remotes configuration directory? I have a repo manager program that uses it's own remotes configuration directory (so it doesn't get mixed up in the repo/config file that needs to be public), and this would break it unless I pretend that it's also the system ostree repo.


@pgleeson for `docker build -t ca1 .` I still got an error: _Cannot connect to the Docker daemon. Is the docker daemon running on this host?_ - but `sudo` solves that!


縮寫：
```js
return word.split(',')
  .slice(0, 3)
  .map(d => parseFloat(d))
  .reduce((result, data, index) => {
    return result + (
      index === 0 ? data : data / Math.pow(60, index)
    );
  }, 0)
  .toFixed(6);
```

可以避免如果word 是 `11,22` 會 `throw error`.
然後如果變數只會有一次賦值 用 `const` 不要用 `let`


Created multidev environment [d8-workflow-test#ci-1](https://dashboard.pantheon.io/sites/2f87721e-86d1-4b55-9049-063156438b6c#ci-1).

[![Visit Site](https://raw.githubusercontent.com/pantheon-systems/ci-drops-8/0.1.0/data/img/visit-site-36.png)](https://ci-1-d8-workflow-test.pantheonsite.io/)


@szepeviktor Yes. :grimacing: Every commit on that branch is also in `master`.  Looks like a typo somewhere along the line got pushed here.


Используйте equals вместо eq


@patrickgomes1968
Had the same problem. Solved by not adding a migration when initially adding the DbSet<Movie> but instead also adding the Genre class first and then making the required changes to the movie class AND THEN making the 'AddMovie' migration.
Hope this helps


Can you file a new issue with a bit more information?  I'm particularly interested in a bit more info about the program not using `/etc/ostree/remotes.d`.


Не распарсится,  предлагаю использовать апи скала, которое умеет работать с пустыми строками и null в том числе.


Missing assignment


missing assignment


huh ?


what else ... ?


Created multidev environment [d8-workflow-test#pr-slogan](https://dashboard.pantheon.io/sites/2f87721e-86d1-4b55-9049-063156438b6c#pr-slogan).

[![Visit Site](https://raw.githubusercontent.com/pantheon-systems/ci-drops-8/0.1.0/data/img/visit-site-36.png)](https://pr-slogan-d8-workflow-test.pantheonsite.io/)


Are you sure sorting doesn't negatively influence scanning results?


Created multidev environment [d8-workflow-test#pr-slogan-1](https://dashboard.pantheon.io/sites/2f87721e-86d1-4b55-9049-063156438b6c#pr-slogan-1).

[![Visit Site](https://raw.githubusercontent.com/pantheon-systems/ci-drops-8/0.1.0/data/img/visit-site-36.png)](https://pr-slogan-1-d8-workflow-test.pantheonsite.io/)


change template "README.md"


@WuNanliang


The .empty() method is intended to be the fastest way to do this check. That is not to say that another method (like comparing to an empty string) might be just as fast -- or perhaps imperceptibly slower -- but to have the best shot at optimal behavior, the .empty() method is the way to go.

I think that the "more obvious" and "more intuitive" claims are based more on experience than anything else. We're used to seeing comparisons to the empty string. I'd recommend giving the change an honest chance and see if you change your mind about being less obvious/intuitive after seeing the other approach for a few months or so.


Typos


新しいリポジトリ作成


@dameng03 `includes` isn't it not yet supported in iOS?


个人主页


# Notas

Entiendo porque agregaste a Deadshot, lo necesitaremos


Why? Check issue #2 - Help needed!


开启超时重传  超时间隔1000ms  重传次数5次


Created multidev environment [wp-circle-001-006#ci-1](https://dashboard.pantheon.io/sites/7aebb4ef-3313-47cb-91dd-2d7fb7693976#ci-1).

[![Visit Site](https://raw.githubusercontent.com/pantheon-systems/ci-drops-8/0.1.0/data/img/visit-site-36.png)](https://ci-1-wp-circle-001-006.pantheonsite.io/)


more modern (readable?) ways might be:
- `whitelist.forEach(url => appendUrl(url))` or
- `for (url in whitelist) appendUrl(url)`

... not that it matters


Cierto! se me pasó ponerlo al final del nombre con el que pensaba guardarlo, una disculpa.


Code  Issues 0  Pull requests 0  Pulse
_posts/2016-12-26-welcome-to-jekyll.markdown

layout	title	date	categories
post
Welcome to Jekyll!
2016-12-25 08:11:50 -0800
jekyll update
You’ll find this post in your _posts directory. Go ahead and edit it and re-build the site to see your changes. You can rebuild the site in many different ways, but the most common way is to run jekyll serve, which launches a web server and auto-regenerates your site when a file is updated.

To add new posts, simply add a file in the _posts directory that follows the convention YYYY-MM-DD-name-of-post.ext and includes the necessary front matter. Take a look at the source for this post to get an idea about how it works.

Jekyll also offers powerful support for code snippets:

{% highlight ruby %} def print_hi(name) puts "Hi, #{name}" end print_hi('Tom') #=> prints 'Hi, Tom' to STDOUT. {% endhighlight %}

Check out the Jekyll docs for more info on how to get the most out of Jekyll. File all bugs/feature requests at Jekyll’s GitHub repo. If you have questions, you can ask them on Jekyll Talk.
 Desktop version


It could be the error. I will try it and if fixes the problem I will open a PR.


0 <-> false
1 <-> true


date_default_timezone_set() 函数设置脚本中所有日期/时间函数使用的默认时区。
东八区为PRC;
发送邮件前，如果未设置时区 ，Smtp.class.php中的date()函数，报date() is not safety的错误


This is where I added the third heading


![](https://github.trello.services/images/mini-trello-icon.png) [1a](https://trello.com/c/BAwydRjB/1-1a)


@piroor Should this be "switch"?


Awesome! 👍🏼 Thanks! 🙌🏽


欢迎大家star


this commit removed all the icons for me on mac


Some robots store tool poses in an array.  Tool0 actually refers to the too at index zero, typically defined as all zeros.  Tool1 implies the tool at index 1.


OK, I understand now what you're talking about.
I fixed it using bluebird Promise.map instead (http://bluebirdjs.com/docs/api/promise.map.html)
Please let me know if this looks OK to you.
Thank you for the thorough review.


The advantage of .empty() is it is unambiguous in the face of Unicode. Consider, there are zero-width codepoints such that ("" != "") where one is an empty string and the other a zero-width strung.


Oops, thanks!


ok, I got it now.


test on line


new add


Why does any of that need to be in a compilation-unit?


initial upload


In the file R_code, we provide the code used for the analysis of the COPD cohort study.

Multiple Correspondence Analysis, Principal Component Analysis, Agglomerative Hoerarchical Clustering using Ward.D2 method.

All the code is written in R.

Libraries used provided in Step0_libraries file.

For the Results section;
***NOTE: BEFORE RUN ANY CODE, FIRST RUN THE Step0_libraries***
1.Research Cohort Creation-->Castalbi_et_all_pca_article
2.In order to obtain the final cluster run the following starting from Step1, Step2, until  Step5
   Individuals and Co-variates-->Step1_Final_manip
   Simple Explanatory Analysis-->Step1_Final_manip
   Multiple Correspondence Analysis-->Step2_Final_mca_drugs+dis
   Principal Components Analysis-->STEP3_Final_pca_cont
   Case Study 1 & Case Study 2-->STEP4_Final_ahc, Step4ii_Final_HCindex-
                                                         wss_for_clusters_from_Practical_Data_Science_with_R_Zumel_Mount,
                                                         Step5_Final_interval calculation

NOTE: FOR THE HC INDEX WE USED THE CODE OF ZUMEL AND MOUNT AS THEY PROVIDED IN THEIR BOOK "PRACTICAL DATA SCIENCE WITH R"


范德萨发


this is just ``with-test-directory``...!


ok


哦


@ArkSource VitaIni was compiled with GCC / G++ 5.1 instead of the newer 6.0, please just include the .cpp files


Interesting. This is exactly what I implemented in my own odoo setup some months ago.
I refined it a little bit further with the concept of 'Count Teams' (handy for very large stocktakes)
Good to see this officially addressed @nim-odoo


Bluemix [toolchain](https://console-regional.ng.bluemix.net/devops/toolchains/de742651-8462-4286-b78d-3e94ac013f9f "compromisos"): [Delivery Pipeline](https://console-regional.ng.bluemix.net/devops/pipelines/0d0e8b6d-930b-40fc-ac1c-2a7d8ad5ef0b "compromisos") deployed [compromisos](https://github.com/eschuler7/compromisos/releases/tag/deploy-ibm-yp-us-south-eschuler-pe.ibm.com-dev-20170905-025010 "deploy-ibm-yp-us-south-eschuler-pe.ibm.com-dev-20170905-025010") to [dev](https://console.bluemix.net/apps/6f3a0e56-815a-41fc-aa5f-5ec09678068d?env_id=ibm:yp:us-south "ibm:yp:us-south:eschuler@pe.ibm.com:dev"), including this commit


Github link is provided in open source section in header table.


Bluemix [toolchain](https://console-regional.ng.bluemix.net/devops/toolchains/de742651-8462-4286-b78d-3e94ac013f9f "compromisos"): [Delivery Pipeline](https://console-regional.ng.bluemix.net/devops/pipelines/0d0e8b6d-930b-40fc-ac1c-2a7d8ad5ef0b "compromisos") deployed [compromisos](https://github.com/eschuler7/compromisos/releases/tag/deploy-ibm-yp-us-south-eschuler-pe.ibm.com-dev-20170905-025225 "deploy-ibm-yp-us-south-eschuler-pe.ibm.com-dev-20170905-025225") to [dev](https://console.bluemix.net/apps/6f3a0e56-815a-41fc-aa5f-5ec09678068d?env_id=ibm:yp:us-south "ibm:yp:us-south:eschuler@pe.ibm.com:dev"), including this commit


# Wake me up inside


GopherCI found **2** issues in the last **2** commits, see: https://gci.gopherci.io/analysis/1012


but about the beautiful formatting you mention, I must think 🤔


k近邻算法训练及测试数据


聊天内容存在了session里，不能实现多人聊天功能。
应该存在application里。
其实应该实时存进数据库里。


Until this point, it is basic Java based application with dummy implementation of fetching a customer record.

Now we will move ahead and use the Spring magic to bring dependency injection between the interacting objects in this object model.
Also going forward, on a constant basis, we would keep maturing our scope with spring functionalities.


I think/hope this will be very helpful to the #337 sub-issue (f) cause.


Ок.


Created multidev environment [d8-workflow-test#pr-slogan-2](https://dashboard.pantheon.io/sites/2f87721e-86d1-4b55-9049-063156438b6c#pr-slogan-2).

[![Visit Site](https://raw.githubusercontent.com/pantheon-systems/ci-drops-8/0.1.0/data/img/visit-site-36.png)](https://pr-slogan-2-d8-workflow-test.pantheonsite.io/)


being dodgy


Parse error.  Expected a command name, got unquoted argument with text "?".


node has 7 elements (1 manually assigned, 6 auto assigned from 6-element array);
node->next prints out 8 memory addresses: the pointers to 7 elements, plus the final null memory value;
array in this case only prints out 6 values (b/c it relies on size of array which is only 6).  if i iterate 's' by 1 in print_array, it prints 7 values, but it skips last memory pointer of node, instead going from second-to-last memory value straight to null value.
...
aha: see next commit for apparent (non-elegant) fix.


Puzzle `54-44c7c538` disappeared in [`test/CMakeLists.txt`](https://github.com/DronMDF/2out/blob/master/test/CMakeLists.txt), that's why I closed #93.


FIROptions does not appear to have a property named `bundleID` on iOS.


Anyway, I am fine with if you want to do the legwork and figure out how to make it work for all these platforms, it's just that I personally am not going to do it. These changes are necessary as far as I am concerned, and I see no need to seek different solutions.


I would add the zip as part of the commit and do something like:

```
 ADD openshift-elasticsearch-plugin-2.4.4.14-SNAPSHOT.zip /
 ENV OSE_ES_URL=file:///openshift-elasticsearch-plugin-2.4.4.14-SNAPSHOT.zip
```
Then we  can test.  We don't have access to the snapshot otherwise


Pier side is coming from mount hour angle, so it will change as the telescope moves past meridian.  This does track the circumpolar stars correctly, validated 'in the real world' with my setup.  Where it can go wrong is when tracking past meridian, but, no way to deal with that without mounts correctly geting pier side messages to the dome.  FYI, my mount (eq8 with eqmod) it reports exactly backwards in the mount displays, says 'East pointing west' when the telescope is on the west side, and vice versa, but that info never gets into the base dome.  When I first cobbled together something in the snoop stuff to try get it, the messages still never arrived, so I left this as it is for now.

To correctly 'finish' this, need a bunch more state vars.  One is to use this math when a mount never does report side of pier (not all of them do).  then for a mount that does, need to allow a config setup variable to override for mounts that report wrong.


The following doc(s) have been deployed to the [hotfixhotf](https://hotfixhotf-static-docs.pantheonsite.io/docs) Multidev environment:
- [/docs/hotfixes](https://hotfixhotf-static-docs.pantheonsite.io/docs/hotfixes)


Yeah. It's sorta embarrassing :(


@RRShieldsCutler Oops, I think I accidentally overwrite this.

Could you re-commit and also add hyphen and period support for the R1 and R2 stuff, just in case it's not an underscore? (Down the line we probably won't need this but for now...)


good


@jcantrill thx I will try


Guess I have to change my secrets.


Oops, it should be https. I will correct.


Still, I think that hacking up things like that just to 'make things compile' on your side is not the correct way to do. I would prefer if you first expose the build issues and exact error messages you are having and then we try to find a solution. I really don't care how much 'clean' is the code or how much you 'like' it but I care if non-libretro stuff get broken by changes in the core that were only tested with libretro ports. For the record, it compiled fine for me using mingW (both my SDL port and libretro port).


Sekanam Louis Akpabio, Slack: @sekaiz5 , GitHub: @Sekaiz5


Think we can leave it be None for now, I'll ask around Slack channel in case we need to set it to something else


Also, adding OptCenter to OptVector is wrong.

In a previous version of this file (see change https://github.com/indilib/indi/commit/93c3f970c628c62c77e8a1fea339c20b98ccf4b5) OptCenter was added to OptVector inside  OpticalVector() function, and later substacted in the Intersection() function, so and optimizations was applied and both operation were deleted.

If you take a look at the Spread Sheet (https://docs.google.com/spreadsheets/d/1FWN0S7kG-GXSfSMPWPi-0CfIg6iGlPFXpROcL2svHIo/edit?usp=sharing) this optimization was not applied and OptCenter is substracted from OptVector in dp variable.


Merge in changes to add -noroot option


>properly


lake-sky-reflection-water-clouds

https://pixabay.com/en/lake-sky-reflection-water-clouds-1611044/
-
https://cdn.pixabay.com/photo/2016/08/21/23/29/lake-1611044_960_720.jpg


locomotive and rolling stock are riding 1 block above rail and locomotives are 1 block offset from rail

![2017-09-05_16 00 01](https://user-images.githubusercontent.com/22108822/30081332-c14496ca-9254-11e7-87f8-916e4def6c06.png)
![2017-09-05_15 59 48](https://user-images.githubusercontent.com/22108822/30081336-c6c9fa36-9254-11e7-839d-2949b7f0e8f5.png)


Well, I think the sentence is technically correct as is.  but I tried to clarify it some (and thank her for the review for me).


The spreadsheet as I downloaded it does add the optical vector.

The photos here demonstrate how well this change works.
http://astro.rozehaven.ca/astro/?p=223

Before I applied these changes, in many areas of the sky, my telescope would end up pointing at the dome instead of the slit.  With this change in place, it nails the center of the slit in every direction, every time.


This CL broke sandboxed builds with the following error:
+ external/local_jdk/bin/jar cMf bazel-out/linux_gnu_x86-opt/genfiles/tensorflow/java/ops/java_op_gen_sources.srcjar -C bazel-out/linux_gnu_x86-opt/genfiles/tensorflow/java/ops .
external/local_jdk/bin/jar: error while loading shared libraries: libjli.so: cannot open shared object file: No such file or directory

I found a similar issue in bazelbuild (https://github.com/bazelbuild/bazel/issues/444), seems to be the case that this error is produced when a (e.g, the genrule in line 476) is missing the JDK as an input to the action.
I created a pull request with a fix (https://github.com/tensorflow/tensorflow/pull/12827).


My mount (FS2) don't report pier side, so my only option is to allow to infor this to de mount, as was done so far. If we delete this option I can work at all.

I agree mount should inform this, but until it does, it will be better to left as it was, in my opinion.


Fine, we will do it your way. I will keep you informed of build errors when/if they happen.


Does this mean it only applies for MacOS?


It should update those as it's submodule for scripts. Did it not update taglist or not ? If so I will fix it in morning

On September 5, 2017 7:37:42 PM GMT+02:00, da3dsoul <notifications@github.com> wrote:
>Did you update scripts as well? TagBlacklist got an update
>
>--
>You are receiving this because you were mentioned.
>Reply to this email directly or view it on GitHub:
>https://github.com/bigretromike/nakamori/commit/c1547edb15137399620dd936da5941fbc4c2d3b6#commitcomment-24095646

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


because it was a very broken and confusing sentence, and slightly repetitious.  So I killed it rather than fixed it.  Open to suggested replacements though :-)


are you in northern or southern hemisphere ?  Is the difference a hemisphere things.


I get the following error when I try to compile with Bazel:

```shell
cathal@thinkum:~/localapps/tensorflow$ ./configure
........
You have bazel 0.5.4 installed.
Please specify the location of python. [Default is /usr/bin/python]: /usr/bin/python3
Found possible Python library paths:
  /usr/local/lib/python3.5/dist-packages
  /home/cathal/localapps/hipCaffe/python
  /usr/lib/python3/dist-packages
Please input the desired Python library path to use.  Default is [/usr/local/lib/python3.5/dist-packages]

Using python library path: /usr/local/lib/python3.5/dist-packages
Do you wish to build TensorFlow with MKL support? [y/N]
No MKL support will be enabled for TensorFlow
Please specify optimization flags to use during compilation when bazel option "--config=opt" is specified [Default is -march=native]:
Do you wish to use jemalloc as the malloc implementation? [Y/n] n
jemalloc disabled
Do you wish to build TensorFlow with Google Cloud Platform support? [y/N]
No Google Cloud Platform support will be enabled for TensorFlow
Do you wish to build TensorFlow with Hadoop File System support? [y/N]
No Hadoop File System support will be enabled for TensorFlow
Do you wish to build TensorFlow with the XLA just-in-time compiler (experimental)? [y/N] y
XLA JIT support will be enabled for TensorFlow
Do you wish to build TensorFlow with VERBS support? [y/N]
No VERBS support will be enabled for TensorFlow
Do you wish to build TensorFlow with OpenCL support? [y/N]
No OpenCL support will be enabled for TensorFlow
Do you wish to build TensorFlow with CUDA support? [y/N]
No CUDA support will be enabled for TensorFlow
Do you wish to build TensorFlow with ROCM support? [y/N] y
CUDA support will be enabled for TensorFlow
Do you wish to build TensorFlow with MPI support? [y/N]
MPI support will not be enabled for TensorFlow
Configuration finished
cathal@thinkum:~/localapps/tensorflow$ bazel build --config=opt --config=rocm /tools/pip_package:build_pip_package
ERROR: no such package '@local_config_rocm//': Traceback (most recent call last):
	File "/home/cathal/localapps/tensorflow/third_party/gpus/rocm_configure.bzl", line 555
		_create_local_rocm_repository(repository_ctx)
	File "/home/cathal/localapps/tensorflow/third_party/gpus/rocm_configure.bzl", line 506, in _create_local_rocm_repository
		_tpl(repository_ctx, "rocm:build_defs.b...", ...)})
	File "/home/cathal/localapps/tensorflow/third_party/gpus/rocm_configure.bzl", line 238, in _tpl
		repository_ctx.template(out, Label(("//third_party/gpus/%s...)), ...)
Unable to load package for //third_party/gpus/rocm:build_defs.bzl.tpl: not found.
INFO: Elapsed time: 1.434s
FAILED: Build did NOT complete successfully (3 packages loaded)
```

Not really sure what's going on here; I tried it with "/usr/bin/python" just in case it was a legacy-only thing, but same result.


Go ahead and do the simple change. I might leave the helper class until the next release since we have a high enough bug potential in this release already :)

StereoParams - let's leave it for now, because I'm not 100% certain what people have used it for. I suspect everywhere it has been used could be just as well served by res_width/height and we could probably switch it to that, but I'd feel more comfortable making that call after grepping through all the shaders in my mirror to see what it has been used for. I can't really think of a likely situation where we specifically need the primary display resolution from the driver that wouldn't be better served by some other value, but maybe I'm missing something. One thing worth noting is that rt_width/height didn't exist when the resolution was added to StereoParams, and every example I've posted of render target size filtering since then has used res_width/height == rt_width/height, so hopefully anyone doing render target size filtering have followed that example.

For the sampler you should definitely create a new class instead of extending CustomResource, and thinking about how it will fit in with the rest of the resource copying infrastructure I'm actually thinking it might be best to also make a separate SamplerCopyOperation and separate ParseCommandListSamplerCopyDirective, because there is so much logic in the existing resource copying code that just doesn't apply to samplers (no views, no need to do full copies, no format, stride, offset, etc), and the custom samplers and sampler copy implementation can be a lot simpler if we keep it separate.


#6200-UnitarySystem-unexpected-fan-operation (mjwitte) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (2147 of 2148 tests passed, 0 test warnings)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-99.95%25-yellow.svg) ![Coverage Badge](http://img.shields.io/badge/coverage%20status-71.91%25-green.svg)


Hi Sylvain,

Okay, I will push a new commit with `get_conv_z_i_2d_bound` broken into smaller parts. I will also add an almost equal test for `k=30` (which passes) but for higher k we get the `pm > 1 - d --- no inversion to pp possible` error. I'll also add some unit tests for some of the new functions.

Christoph


@Tsoccerguy3 is it just the render or are the hitboxes wrong too?


It's strange. I'm now in my observatory testing the last version of indidome (just upgraded) and it point much worst than previous version. It point well outside the slit in most directions.

Spread Sheet and indidome calculate the same azimuth for you?


Hello, first of all great job with this repository and sorry for writing here but do not know how to contact you.
I am trying to do something similar with java but are not able to make the correct call for authorization. Do you think you are able to assist me?  please contact me on: gustav.bergsten@hotmail.com


libchdr/libzma/libFLAC will all need to be made C89-compatible, since we have a MSVC 2010 and earlier targets and we want to have full-featured Genesis Plus GX cores for those.

Can we agree on this? If we can't, I will still have to diverge from your upstream regardless.


I prefer to preserve arrow functions wherever possible. Depending on how they are written, a **function** will change its behavior based on how you reference it, where an **arrow function** will not. This is critical in higher order functions. I will, however, use `function` when I need access to `arguments` or the `new` keyword.


Note that this is for the table Match only.

More research into integrating dummy data for table Users is needed due to SHA256 hashes being used.


This hardcoded uses of "java" executable causes an exception when SO provides a JRE instead of expected JDK java executable.

If you configure your inside your PATH env variable java as ${JRE_HOME}/bin, EvoSuite doesn't find needed **/lib/tools.jar** library

Maybe you could be interested in passing the full path of your JDK installation thru a Plugin Parameter, or indicate in documentation that is not possible to run this Maven plugin if JRE is used instead of JDK


👍 `const` FTW!


This commit has been mentioned on **Discourse Meta**. There might be relevant details there:

https://meta.discourse.org/t/pull-4961-question/69429/1


> By event do you mean the websocket event or internal events which are used by rules?

Sorry, web socket events.  I didn't look at the deCONZ log.

> So flag should be treated like button events? I thought equal values should not yield events except button events.

Currently (v2.04.73 and many versions before), for ZigBee sensors, a web socket event containing the value and lastupdated is issued, when the the value is refreshed, regardless whether the value has changed, regardless whether the refresh is because of attribute reporting or reading the attributes in the deCONZ GUI.  Personally, I like this, and I think CLIP sensors should mimic this behaviour.

I guess I could live with an event containing only the changed attributes (i.e. only lastupdated when the value didn't change).  When the value did change, I don't think sending two events is correct, one with the value and lastupdated, and one with only lastupdated.  Also, when the lightlevel changes, I would want one event with the changed lightlevel, lux, lastupdated, and, when applicable, dark and daylight.  I understand that would require some significant refactoring...  Incidentally, currently there's no events for lux?

> That's really bad, can you please provide the example rule?

I added the transcript and web socket event log.

> Lastupdated is changed after (re) starting deCONZ (presumably when setting the flag to false). The Hue bridge sets the value to "none".

> Yes it tries to be clever and restores the last known state, modifying it if it is too fresh (2 minutes).

That's not what I observe:
```
$ ph_put /sensors/100/state '{"flag":true}'
$ ph_get /sensors/100
{
  "config": {
    "on": true,
    "reachable": true
  },
  "etag": "cb0f06abde564bd57245e031da700977",
  "manufacturername": "homebridge-hue",
  "modelid": "CLIPGenericFlag",
  "name": "Home",
  "state": {
    "flag": true,
    "lastupdated": "2017-09-05T20:15:37"
  },
  "swversion": "0",
  "type": "CLIPGenericFlag",
  "uniqueid": "/sensors/100-100"
}
$ ph_restart
pi2: restarting deCONZ gateway ..
$ ph_get /sensors/100
{
  "config": {
    "on": true,
    "reachable": true
  },
  "etag": "6a3a7f3cf4108cee88e0c0085d88a751",
  "manufacturername": "homebridge-hue",
  "modelid": "CLIPGenericFlag",
  "name": "Home",
  "state": {
    "flag": false
  },
  "swversion": "0",
  "type": "CLIPGenericFlag",
  "uniqueid": "/sensors/100-100"
}
```


The question was meant what makes the extension suddenly beta.


чем complete отличается от success ?


каждый раз делать jquery обект из ноды, накладно. $(btn)
Можно закешировать и передавать параметром


Since the check cheks for `input`, the parameter, maybe change the error message to include that.


I downloaded the spreadsheet about 10 days ago, and have used that to compare.
Spreadsheet and indidome here now agree within a half degree in all directions.  Before these changes, they differed by as much as 10 degrees in places.

Wondering if we have something else out of sync in the code here.  Are you working directly from the github repository, or a local repository synced with github ?


But do we even need to throw?


I like `/var/run/cloudlaunch` so will move it there.
(I put in `/tmp` because that's where it used to be (https://github.com/galaxyproject/ansible-cloudlaunch/commit/28851389e5fe8a04654ff6376f17a9b15596cbca#diff-c289154d2cb2159fd3b89d9b60ba6d4bL2) although it didn't feel right.)


complete работает на любой респонс, а success только на success


These are the build errors with PS3 -

In file included from core/cd_hw/libchdr/deps/libFLAC/bitreader.c:42:
./core/cd_hw/libchdr/deps/libFLAC/include/private/macros.h:53:23: error: sys/param.h: No such file or directory
make: *** [Makefile.libretro:394: core/cd_hw/libchdr/deps/libFLAC/bitreader.o] Error 1
make: *** Waiting for unfinished jobs....
In file included from core/cd_hw/libchdr/deps/libFLAC/bitwriter.c:41:
./core/cd_hw/libchdr/deps/libFLAC/include/private/macros.h:53:23: error: sys/param.h: No such file or directory
make: *** [Makefile.libretro:394: core/cd_hw/libchdr/deps/libFLAC/bitwriter.o] Error 1

You'd need to put an #ifndef __CELLOS_LV2__ around #include <sys/param.h> .


Brandon Maxwell


packaging.env?

and should there be disambiguation between env-for-my-package vs env-for-packages-using-me-to-compile?


A test on uploading files


:drum: introducing...


hi


To break , I think i had to hit the model . Model textures were also missing . I will turn on view hitboxes and take a screenshot

![2017-09-05_16 15 31](https://user-images.githubusercontent.com/22108822/30081797-90ce7b80-9256-11e7-815b-4aaf1b5ba3fa.png)


also... cleaner...

    ${BOSH_PACKAGES_DIR:-/var/vcap/packages}


<!Doctype html>


I really think we should prefix these; github org prefix? `bosh-packages-golang-release`


I don't mind about C89 compatibility, I initially tried to compile all these stuff with -ansi GCC flag but there was too many things to fix in rtisserand original codebase soI gave up on this (many C++ comment or delayed variable declarations I think). You surely had similar issues with other emulators that had libchdr support added?


Does this change (or the others for oss-fuzz-reported bugs) deserve a test?
Our [recommendation](https://github.com/google/oss-fuzz/blob/master/docs/ideal_integration.md) is to commit the reproducer that caused the bug alongside the fix, and ensure that the fuzz target runs on all of such inputs (and the rest of the seed corpus) in the project's CI. This works as a great regression test.


Created multidev environment [napcs2017#pr-content](https://dashboard.pantheon.io/sites/23095a75-4a68-4e85-ba90-d57a28c216b6#pr-content).

[![Visit Site](https://raw.githubusercontent.com/pantheon-systems/ci-drops-8/0.1.0/data/img/visit-site-36.png)](https://pr-content-napcs2017.pantheonsite.io/)


darwin package rather than windows?


First push on Lab 1.


wir hatten das problem mit miui 8 glaub auch schon, müsste mal nachgucken wie das dort gehandhabt wurde. ich war mir nicht mehr sicher, aber eventuell haben wird das einfach data saver genannt weil es nichts passendes gab das auch kurz genug war. wenn euch der begriff aus windows bekannt ist, dürft ihr den gerne auch benützen sofern er korrekt ist, bei miui 8 haben wir in einzelnen fällen das so benannt wie es der mehrheit von windows her bekannt ist. es ist einfacher etwas zu erklären was bereits bekannt ist. es gibt bei xiaomi.eu eine übersicht über bestimmte begriffe, weiss nur nicht mehr ob das ein thread im german forum ist oder eine pn mit 10 empfängern.

ps: hier unten, zeile 53/54, "vom senden blockiert", erstens ist senden gross weil es das senden ist (verb wird zum nomen) und zweitens würde ich es anders formulieren, leider versteh ich nicht wirklich was der englische satz mir sagen will. was will er nicht senden?


Now pointing my telescope to Azimuth 118 deg. and Altitude 47 deg., Spreadsheet calculates an azimuth of 125 deg. but indi calculates 70 deg.

Indi is clearly wrong.


I updated libchdr support in those repos so that it compiled as C89, and I think Romain was fine with it. Same with liblzma/libFLAC.

I also converted the C++ comments to C. It was a lot of work but I put the time in to make it happen.

So, what is your decision here? I really need this for the MSVC cores, otherwise I will still have to diverge from your upstream repo. You would be able to get the changes from the other repos that got CHD support - like mednafen saturn/pcfx/pc engine/etc.


test


Fix #2


These commits only exist outside of master and TER releases so I'm not sure what you're asking.


Bluemix [toolchain](https://console-regional.ng.bluemix.net/devops/toolchains/6b8b7163-1ec8-4616-82fa-aa467a17af03 "storybook-toolchain-v2"): [Delivery Pipeline](https://console-regional.ng.bluemix.net/devops/pipelines/b84aaac8-8484-4a1e-902a-ebb526eb7998 "storybook-toolchain-v2") deployed [carbon-components-react](https://github.com/carbon-design-system/carbon-components-react/releases/tag/deploy-ibm-yp-us-south-chrisdhanaraj_org-Bluemix-Design-System-20170905-202836 "deploy-ibm-yp-us-south-chrisdhanaraj_org-Bluemix-Design-System-20170905-202836") to [Bluemix Design System](https://console.bluemix.net/apps/edd401fd-37f9-4365-8993-c2e2bcc73b62?env_id=ibm:yp:us-south "ibm:yp:us-south:chrisdhanaraj_org:Bluemix Design System"), including this commit


Maybe we should add an "async" param then (if that's not already the case). It should really not affect it. I know sometimes AJAX calls are still considered as being part of the page, but I also know we can avoid that, somehow.


@tiberiuichim the basestring change you mentioned is already in place since 1.6.3, isn't it?
See: https://github.com/plone/Products.CMFPlacefulWorkflow/commit/24b85984b810fd5682e68ae8e7c3d0531f38660c#diff-9f1b0562ad5cace017a6ebf7675eadc4R109


I deleted the extra release note file that was in there and squashed the patch down to a single commit with a decent message


I've built this version today and the system is printing the "Build package failed" message even when ret_status = 0

I guess you forgot the use spaces between $ret_status, == and 1.
The correct would be:
```bash
if [ $ret_status == 1 ]
```


i have a same warning
did you find a solv for it??


I got this error on Raspberry Pi 3

make: *** No rule to make target 'core/cd_hw/libchdr/deps/libFLAC/bitwriter.o', needed by 'genesis_plus_gx_libretro.so'.  Stop.
make: *** Waiting for unfinished jobs....
/home/pi
Could not successfully build lr-genesis-plus-gx


> Philips hue motion sensor use only name from ZHAPresence resource

Cool!  Can I add a check that the node for the ubisys D1 uses only the name from the Dimmable Light endpoint?


@thet Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.app.iterate/36/violations
```
plone/app/iterate/policy.py:57:45: C812 missing trailing comma
plone/app/iterate/policy.py:66:11: T000 Todo note found.
plone/app/iterate/interfaces.py:321:23: C812 missing trailing comma
plone/app/iterate/interfaces.py:328:22: C812 missing trailing comma
plone/app/iterate/__init__.py:48:78: C812 missing trailing comma
plone/app/iterate/setuphandlers.py:11:27: C812 missing trailing comma
plone/app/iterate/containers.py:72:50: C812 missing trailing comma
plone/app/iterate/containers.py:73:14: C812 missing trailing comma
plone/app/iterate/browser/checkout.py:70:33: C812 missing trailing comma
plone/app/iterate/dexterity/copier.py:75:19: T000 Todo note found.
plone/app/iterate/dexterity/copier.py:165:50: C812 missing trailing comma
plone/app/iterate/tests/test_iterate.py:153:11: T000 Todo note found.
plone/app/iterate/tests/test_iterate.py:288:34: S001 found module formatter
plone/app/iterate/tests/test_doctests.py:19:50: C812 missing trailing comma
plone/app/iterate/tests/test_doctests.py:27:53: C812 missing trailing comma
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


For you PS3 build issue, just remove -DHAVE_SYS_PARAM_H from DEFINES in Makefile.libretro

PS: not sure why you modified Makefile.common but you added a bunch of .c files that are not needed (and not present in my initial commit). I actually made some effort to clean original libchdr deps from unneeded files.


You should put all these files in the main directory. Don't have a "src" directory. It doesn't make sense as a package


See #1133.


There is already a logging system, you should just use it.


You should ignore ~ files


Make the Math's section optional?


@vinkla, you've broken our ability to access specific commits as far as I can tell.  You added Laravel 5.4 support after you required PHP 7.0 in your tagged releases.

This made it impossible to run this package on Laravel 5.4 on a PHP 5.6 box.

We've been utilizing your package via

```
"vinkla/hashids": "dev-master#7dcdf0918e3aaa36970486f43a8ea32d24082232
```

As far as I can tell, you aliasing 3.3-dev as dev-master has broken this.  I'm no composer expert though.


Do messages come on stdin/stdout? I thought it was an HTTP server? If so, you should just use the Web server and make this a servlet.


Yep because that's a public method


For C89 stuff, just update the files that get you compiling errors with your fixed ones, as I said, I don't mind C89 compatibility fix.


I updated Makefile.common already to take out the files that are not there.


Correct the Typos. Change the Css


Would still prefer a general-purpose regex like api-compiler's to an edge case, but I'm not going to block approval on it, since we only have one real-world example where this is problematic.


it was intended to be an abstract class, looks like we just left out the keyword by mistake


I just sent my telescope to azimuth 114 azimuth 43.  The calculation comes out to 124.2 in indi here. and my camera shows telescope is dead center on the slit.

What is different between your and my setups ?  I have 1.18m for dome radius, 0.60 shutter width, 0.05 for N displacement, -0.07 for E displacement, -0.15 for Up displacement, and 0.30 for OTA offset.


> dollchan.css

Чистого css у нас нет. Наш код имеет множество условий, тернарных операций в строках, и т.д.


The spreadsheet you download adds the optical center to optical vector  (Cells F18 to F20 : OV.x =**F11**+cos(F15)*SIN(F16) , where F11 is the Optical Center) but just in cells F22 to F44 is substacted and used for subsequent calculus. F18 to F20 cells are no longer used.

I'm apologise because code is a bit confusing and it don't exactly mach Spreadsheed because some later changes.

Also is rare you are getting good pointing with this changes. Can you post an output log with driver debug enabled? I will take a look.


note: I believe the preferred syntax is `raise ArgumentError, 'Must provide at least one shard'` though either will work. See https://apidock.com/ruby/Kernel/raise


The following doc(s) have been deployed to the [enablement](https://enablement-static-docs.pantheonsite.io/docs) Multidev environment:
- [app/config/sculpin_site.yml](https://github.com/pantheon-systems/documentation/commit/7828c0f4610725b01ed2c1a80e3874234d19b6e9/app/config/sculpin_site.yml)
- [/docs/multidev](https://enablement-static-docs.pantheonsite.io/docs/multidev)
- [/docs/solr](https://enablement-static-docs.pantheonsite.io/docs/solr)
- [/docs/terminus](https://enablement-static-docs.pantheonsite.io/docs/terminus)
- [source/_partials/content/ctas/automate-enablement.html](https://github.com/pantheon-systems/documentation/commit/7828c0f4610725b01ed2c1a80e3874234d19b6e9/source/_partials/content/ctas/automate-enablement.html)
- [source/_partials/content/ctas/performance-enablement.html](https://github.com/pantheon-systems/documentation/commit/7828c0f4610725b01ed2c1a80e3874234d19b6e9/source/_partials/content/ctas/performance-enablement.html)
- [source/_partials/content/ctas/workflows-enablement.html](https://github.com/pantheon-systems/documentation/commit/7828c0f4610725b01ed2c1a80e3874234d19b6e9/source/_partials/content/ctas/workflows-enablement.html)
- [source/docs/assets/css/main.css](https://github.com/pantheon-systems/documentation/commit/7828c0f4610725b01ed2c1a80e3874234d19b6e9/source/docs/assets/css/main.css)
- [/docs/cache-control](https://enablement-static-docs.pantheonsite.io/docs/cache-control)
- [/docs/caching-advanced-topics](https://enablement-static-docs.pantheonsite.io/docs/caching-advanced-topics)
- [/docs/composer-drupal-8](https://enablement-static-docs.pantheonsite.io/docs/composer-drupal-8)
- [/docs/domains](https://enablement-static-docs.pantheonsite.io/docs/domains)
- [/docs/drupal-8-cache](https://enablement-static-docs.pantheonsite.io/docs/drupal-8-cache)
- [/docs/drupal-cache](https://enablement-static-docs.pantheonsite.io/docs/drupal-cache)
- [/docs/drupal-redis](https://enablement-static-docs.pantheonsite.io/docs/drupal-redis)
- [/docs/git-faq](https://enablement-static-docs.pantheonsite.io/docs/git-faq)
- [/docs/global-cdn](https://enablement-static-docs.pantheonsite.io/docs/global-cdn)
- [/docs/guides/github-pull-requests](https://enablement-static-docs.pantheonsite.io/docs/guides/github-pull-requests)
- [/docs/guides/quickstart/next-steps](https://enablement-static-docs.pantheonsite.io/docs/guides/quickstart/next-steps)
- [/docs/https](https://enablement-static-docs.pantheonsite.io/docs/https)
- [/docs/kalabox](https://enablement-static-docs.pantheonsite.io/docs/kalabox)
- [/docs/kill-mysql-queries](https://enablement-static-docs.pantheonsite.io/docs/kill-mysql-queries)
- [/docs/new-relic](https://enablement-static-docs.pantheonsite.io/docs/new-relic)
- [/docs/pantheon-workflow](https://enablement-static-docs.pantheonsite.io/docs/pantheon-workflow)
- [/docs/quicksilver](https://enablement-static-docs.pantheonsite.io/docs/quicksilver)
- [/docs/sftp](https://enablement-static-docs.pantheonsite.io/docs/sftp)
- [/docs/solr-drupal-7](https://enablement-static-docs.pantheonsite.io/docs/solr-drupal-7)
- [/docs/solr-drupal-8](https://enablement-static-docs.pantheonsite.io/docs/solr-drupal-8)
- [/docs/wordpress-redis](https://enablement-static-docs.pantheonsite.io/docs/wordpress-redis)
- [/docs/wordpress-solr](https://enablement-static-docs.pantheonsite.io/docs/wordpress-solr)
- [/docs/pantheon-yml](https://enablement-static-docs.pantheonsite.io/docs/pantheon-yml)
- [/docs/guides/quickstart/next-steps](https://enablement-static-docs.pantheonsite.io/docs/guides/quickstart/next-steps)


OK I checked , Hit boxes are correct , render is wrong by offset
![2017-09-05_16 38 32](https://user-images.githubusercontent.com/22108822/30082518-131683e2-9259-11e7-8bd3-347f9dc7e3e9.png)
![2017-09-05_16 39 08](https://user-images.githubusercontent.com/22108822/30082522-16ed4d66-9259-11e7-9785-58b3c6c33c7c.png)


"//example.com" is also valid URL, and will default to using the current page's protocol.


LocalStorageService should be used instead of direct localstorage


@charlievieth srsly?


No la mejor forma de implementarlo


Are we ok that both files are now useless, no?


remove this


TeamCity Gribble ORM :: Deploy [Build 1.6.147.0](http://build.mikeobrien.net/viewLog.html?buildId=3399&buildTypeId=gribble&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:25


Some commens


[R/storage_management.R:86:21:](https://github.com/Azure/doAzureParallel/blob/baf75ad28605bf01c0fbd1901abdb2e9eac0f4ef/R/storage_management.R#L86) *style:* **Commas should always have a space after.**
```r
  attr(storageFiles,"containerName") <- container
                    ^
```


if (!localStorage...)


> То же самое и для svg

SVG в сурсах во многом отличаются от svg в коде. В папке images многие иконки избыточны, кнопки постов содержат повторяющийся background, например. Сделано это для того, чтобы их было видно в файловом менеджере так, как они отображаются в браузере.


255u - colormap[2].B
Etc


`width: '100%'` fixes the problem and still allows the DatePicker to naturally scale to fit the width of the parent container.


This is an entry in the hello-world file.
My name is David and I am starting to use Git


I would change this to
```
if (!isset($pageInfo['data']['hreflang_' . $language])) {
    return;
}
$url = Navigation::getUrl($pageInfo['data']['hreflang_' . $language], $language);
```
or something


Thank you again for your support @stilor !


TeamCity Gribble ORM :: Deploy [Build 1.6.148.0](http://build.mikeobrien.net/viewLog.html?buildId=3400&buildTypeId=gribble&guest=1) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:16


we never change the content of activeLanguages so I would just use `BL::getActiveLanguages()` where you need it


That's a pity.
I think it is the biggest nuisance in Notepad++.

However, don't rush with the removal since a lot work is already done.
It might be sufficient for the moment to insert a note in the readme
that this feature is broken (for version higher than...).

Best
Robert

On 05/09/2017, Derek Riemer <notifications@github.com> wrote:
> Remove the key mapper support, because it seems to break every version of
> npp, and I can't waste any more time fixing it.
> @Robert-J-H can you update your translations, please?
>
> --
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub:
> https://github.com/derekriemer/nvda-notepadPlusPlus/commit/547cd2ab39836462d73e87b75e4a3cd41a8c835c
>


Here is a log, it started at the above mentioned point, then I slewed it to something about 30 degrees away by just selecting slew in kstars.

https://pastebin.ca/3864121

Camera on the telescope shows that it's dead center in the middle of the slit.