Please remove this comment as it is no longer needed.


if you're going to pass, then you don't need the `else`


Yes, I agree. I am usually using 120s for "risky" operations. I think that additional comment regarding this scroll timeout will suffice, I guess we don't want to pollute simple usage example.


[inst/makeData.R:41:78:](https://github.com/mlr-org/mlr/blob/18b76878f21ad229f478f8fbd2616d991e80790f/inst/makeData.R#L41) *style:* **Commas should always have a space after.**
```r
iris.oneclass.task = makeOneClassTask("iris-one-class-example", data = iris[,-5])
                                                                             ^
```
[tests/testthat/helper_objects.R:56:21:](https://github.com/mlr-org/mlr/blob/18b76878f21ad229f478f8fbd2616d991e80790f/tests/testthat/helper_objects.R#L56) *style:* **Commas should always have a space after.**
```r
oneclass.df = iris[,-5]
                    ^
```
[tests/testthat/helper_objects.R:57:31:](https://github.com/mlr-org/mlr/blob/18b76878f21ad229f478f8fbd2616d991e80790f/tests/testthat/helper_objects.R#L57) *style:* **Commas should always have a space after.**
```r
oneclass.truth = ifelse(iris[,5] == "versicolor", TRUE, FALSE)
                              ^
```


Fixing the 'Header Search Path' in the XCode project allows the compiler to find the .h files without having to append a path to any include statement. This allows us to remove the 'React/' prefixes. It also fixes another related issue...Facebook made breaking changes in react-native by moving some files under new subdirectories which broke some of the 'React/' includes.


This should have been
include "config.php";


> Твой мод завязан на изменении FID?

Нет, просто тестировал определенные моменты и обнаружил, что FID возвращается неправильный.
Будет время и желание потом создам ISSUE.


Hm. Not clear. Why it's skipped?


I feel like there is no need for the whole loop "did you play the game" "do you want to rate the game". You could just add another command `update`, something like
`$ inventory update <gamename> --stars 5`


the date format string should go in a constant at the top of the file


Please remove this if function as it is only for testing.


A compile time assert in env_dpdk/env.c would be fine.


no need for a yaml file here, and if you want a yaml file, because you want to store multiple settings in the future, then don't use space for keys (`Default list`>`default_list`)


remove this as this is for testing


Is SpeechToTextV1 supposed to remain removed?


good catch ;-)


@akerekes
This release has dev appserver 1 update and changes flex staging to only copy app.yaml


@SosyalAlkolik This may not be a CentOS 7 package:
http://mirror.centos.org/centos/7/os/x86_64/Packages/


Little question here. Airfoil Satellite forwards its remote control commands (PlayPause, Next, Prev) back to Airfoil, which then forwards them to a target application (such as iTunes, Spotify, etc).

Only problem is, Airfoil Satellite doesn't actually know the -state- of the target application. It has no idea if iTunes is playing or paused. It just knows how to send a PlayPause command.

So I can implement an "isPlaying", but it would just be "is connected and can handle commands". Perhaps reading the track title length is best in the end?


I would prefer to evaluate this change separately from the rest of this patch which is focused on the env API.

I think we have other places in SPDK that do implicit void pointer arithmetic.  If so, we should fix all of them (or at least convince ourselves this is the only one that needs fixing.)


According to Pavel Durov on Twitter, the updated source code should be published very soon.

https://twitter.com/durov/status/847454485882355713

*“Definitely, updated source codes will be online later today.”*


@matthieugomez, I like your solution to automatically pad based on console width.

The only situation where this seems too spaced-out is for 1-way tabulations. Here is a possible compromise that would keep the width of 1-way tabulations comfortably wide:

```r
  width <- (getOption("width") %/% length(colnames(df))) - 4L
  if (padding == "stata" & length(colnames(df)) == 4L) {
    colnames(df) <- str_pad(colnames(df), width %/% 1.5, pad = " ")
  }
  else {
    colnames(df) <- str_pad(colnames(df), width, pad = " ")
  }
```


OK.  It's entirely possible that you did run our format script but astyle didn't catch the extra space.


LGTM


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/796793bb-fc0f-4fe6-99f9-f7bd31c31a31 "serverquiz2"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/c96aaaf8-b52b-4774-a3ca-8aaefd6cb092 "serverquiz2") deployed this commit to [test](https://console.ng.bluemix.net/apps/58674aad-b12e-47ae-ad6d-4a98bcaefca8 "ibm:yp:us-south:kalle.kindvall@ibm.com:test")


Just saying: we did that already in December of 2016 ... four month ago.


Yes.


master (evanweaver) - x86_64-MacOS-10.10-clang: Build Failed

![Build Badge](http://img.shields.io/badge/build%20status-failing-red.png) ![Test Badge](http://img.shields.io/badge/tests%20passed-NA-red.png)


Hi Thom. After cloning the repo and run vagrant up I got an error with the box version
`vagrant up
Bringing machine 'beetbox' up with 'virtualbox' provider...
==> beetbox: Box 'beet/box' could not be found. Attempting to find and install...
    beetbox: Box Provider: virtualbox
    beetbox: Box Version: ~> 0.5.0
==> beetbox: Loading metadata for box 'beet/box'
    beetbox: URL: https://atlas.hashicorp.com/beet/box
The box you're attempting to add has no available version that
matches the constraints you requested. Please double-check your
settings. Also verify that if you specified version constraints,
that the provider you wish to use is available for these constraints.

Box: beet/box
Address: https://atlas.hashicorp.com/beet/box
Constraints: ~> 0.5.0
Available versions: 0.2.0, 0.2.1, 0.2.2, 0.2.4, 0.2.5, 0.2.6, 0.2.7, 0.2.8, 0.3.0, 0.3.1, 0.3.2, 0.3.3, 0.3.4, 0.3.5, 0.3.6, 0.4.0, 0.4.1, 0.4.2, 0.4.3, 0.4.4
`
I've changed default vagrant config on .beetbox/Vagrantfile to 'vagrant_box_version' => '~> 0.4.4', and the problem is solved.


TeamCity Xbim :: Xbim Geometry :: XbimGeometry [Build 347](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=1521&buildTypeId=Xbim_XbimGeometry_XbimGeometry) outcome was **SUCCESS**
Summary: Running Build time: 00:35:48


TeamCity Xbim :: Xbim Windows UI :: XbimWindowsUi [Build 27](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=1522&buildTypeId=Xbim_XbimWindowsUi_XbimWindowsUi) is now running


What's the exact difference?


hello


TeamCity Xbim :: Xbim Windows UI :: XbimWindowsUi [Build 27](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=1522&buildTypeId=Xbim_XbimWindowsUi_XbimWindowsUi) outcome was **SUCCESS**
Summary: Running Build time: 00:00:52


TeamCity Xbim :: XbimMvdXML :: XbimMvdXML [Build 21](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=1523&buildTypeId=Xbim_XbimMvdXML_XbimMvdXML) is now running


Thanks @mseemann ! I created #607


If you are working in _master_ use `git pull --rebase` rather than `git pull`.

Use a graphical tool such as `gitk` to review what you are about to push.


TeamCity Xbim :: XbimMvdXML :: XbimMvdXML [Build 21](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=1523&buildTypeId=Xbim_XbimMvdXML_XbimMvdXML) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:33


Do you mean adding a CONFIG_ISCSI option?

Regarding iSCSI on FreeBSD - there is something Linux-specific we are doing in our iSCSI library right now that it keeps it from compiling or running on FreeBSD.  It's entirely possible that has been resolved already.  I'll have to take a look.


this was fixed (unnecessary change)


I don't think dropdown_sections.pt needed updating here. The previous version of dropdown_sections.pt  already had the expected behaviour for annotating the top level sections. And this version breaks the Home tab, see #31.


TeamCity Chorus :: chorus-precise64-master Continuous [Build 2.6.763.f0ab6d1186451966c1d67faf8ac70ebbb0d9f7e1](http://build.palaso.org/viewLog.html?buildId=87203&buildTypeId=bt323) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:38


Upsert and find endpoints are passing tests. Other endpoints yet untested.


TeamCity Chorus :: chorus-win32-master Continuous [Build 2.6.401.f0ab6d1186451966c1d67faf8ac70ebbb0d9f7e1](http://build.palaso.org/viewLog.html?buildId=87204&buildTypeId=bt2) outcome was **FAILURE**
Summary: Compilation error: src\LibChorus\LibChorus.csproj (new) Build time: 00:00:42


Hmm, what's the reasoning for this change? On Debian/koreader it's sent at WARNING, so this times out every time. In fact, why is the level checked at all, is CTRL-EVENT-SCAN-RESULTS sent multiple times?


Unused variable.


> Freeciv-web already has a authentication system.

Perhaps it is the moment to review the authentication in Freeciv-web. Especially since our passwords are stored as MD5 hashes.

I have started to look at where the autentication in freeciv-web is used to understand which code path are impacted.

I don't know a lot about the freeciv project itself, for what cases authentication in needed?


Thanks for replying, after 5 years..

I understand it is raised to p-norm, but I still have doubt max/min distance is a tight bound even when each bounding box is a tight bound ( I think the current version of ckdtree guarentees that).

See the example figure. We have two nodes each with two points at the corner. The tight bound is `dx**2` but max_distance is` dx**2 + dy**2`.. Did I missing something here?

![sketch](https://cloud.githubusercontent.com/assets/138060/24527507/476f4f18-1557-11e7-94ee-825f97c2d6ac.png)

I noticed the miningthesky paper (on which this algorithm is based) didn't have this optimization; they used s_lo and s_hi which suggests a single bin -- in that case if the bounds falls in all pairs fall into that bin.


mostly personal preference. in some case `getAccessToken` could check what function returns.


Hey with this commit would you be able to provide an example of how this would work when defining a component. My existing components are now not rendering as they require a container component to be defined as a function.


- Edited Readme.md


We can do better but it's a moving target...
MuseScore 2.0.X users who will update will need the My_First_Score.mscz file in the MuseScore binary because the path is stored in their binary. We could copy My_First_Score.mscz to Untitled.mscz, so new users will have the right behavior (but a larger binary). However, even in this case, non english users will have a wrong translation, so we need to keep the createDefaultName(). If they reopen from recent files, the translated named will be removed though... If we keep the createDefaultName, MuseScore 2.0.X users with My_First_Score will get "Untitled" as a title. So... my change is small, it does have remaining issue but it's consistent for 2.0.X and 2.1 users and doesn't add anything in the binary.


revert-6039-NewErrorWhenHoursShownInFirstColumnOfTable (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1895 of 1895 tests passed, 0 test warnings)

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


revert-6039-NewErrorWhenHoursShownInFirstColumnOfTable (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-custom_check: OK (0 of 0 tests passed, 0 test warnings)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.png)


Is it intentional that an implementation of handle_RCPT can return None to get the default behavior? If so, that needs to be documented carefully, since it makes a crucial difference between "return None" and "return '250 OK'" in a user's handle_RCPT.


Seriously.


Awesome, I had forgotten how to get the window to pop up.


Why do these tests add options to envelope.rcpt_options, but not address to envelope.rcpt_tos? This behavior should certainly be allowed by aiosmtpd, but it is a weird behavior to put on display in aiosmtpd's unit tests, since it is almost certainly never what you want to do in user code.


Is it not used below?


What do you mean exactly?


I guess so.  Only django_membersuite_auth/backends.py is the only user.


Hey @Pamross looking good here. Check out the issue I filed. The .DS_Store is a Mac OS file that tells finder what is in the directory for searches. Basically a junk file as far as your code is concerned. If you need help let me know.


develop (evanweaver) - x86_64-Linux-Ubuntu-14.04-clang-3.5: Build Failed

![Build Badge](http://img.shields.io/badge/build%20status-failing-red.png) ![Test Badge](http://img.shields.io/badge/tests%20passed-NA-red.png)


@DevStarks Dope! If it ever comes up, we could also consider adding a param to toggle for whether or not to include these extra codes.


You're right. I will correct.


Next time it would be really useful to use a pull request to update templates, and ping for a review before merging it.


with the protocol designed as-is, these events are optional. I'll rename it to usb_id but the basic premise here is that if it doesn't have a USB id, it just gets omitted. And we can introduce a GPIO-id later if once we figure out how


Delete unused Button import (#916)

Preview: docs
Coverage: core | datetime


New issue #22: [Move security.models.PortalUser.generate_username() into django-membersuite-auth](https://github.com/AASHE/python-membersuite-api-client/issues/22)


Also fixes boost at <= 1.58


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/9fd13314-c90c-489c-8cc2-4680ddfd420e "chatbox-sotaque-brasileiro"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/cd85c099-dfc2-4461-b0a8-e54c35d16f34 "chatbox-sotaque-brasileiro") deployed this commit to [dev](https://console.ng.bluemix.net/apps/3a9222d2-784c-4b25-94f2-87e2260d9a46 "ibm:yp:us-south:Mozino:dev")


dunno, I just copied this from the tablet protocol and it seemed useful :)

I'm trying to avoid the compositor having too much specific knowledge because the interpretation of these is highly susceptible to implementations. string/value properties are easy, but then we have to agree on some (external) dictionary of those, otherwise we have to bump the protocol all the time. If you think that's sane, we can go for it.


[Table] Add back fixed size to table example but increase width (#913)

Preview: docs
Coverage: core | datetime


Build plottable.min.js with webpack (#3318)

Demo: quicktests | fiddle


no, I really meant out → in, to signal that you may lose the fd a few times but you don't need to recheck whether the device is the same as before (unless you get a removed event). I'll try to reword that.


preparing release 3.0.0-rc.1

Demo: quicktests | fiddle


develop (evanweaver) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: Build Failed

![Build Badge](http://img.shields.io/badge/build%20status-failing-red.png)


@jyemin, thanks!

Will there be a jackson-compatible converter provided (since it has become the standard for Java JSON serialization) in the java libs? Or are we expected to create one ourselves using this framework?


master (evanweaver) - x86_64-Linux-Ubuntu-14.04-clang-3.5: Build Failed

![Build Badge](http://img.shields.io/badge/build%20status-failing-red.png) ![Test Badge](http://img.shields.io/badge/tests%20passed-NA-red.png)


OK, I see you just committed today's work. Nice.


maybe add more stuff...


@HoldYourWaffle Congratulations 😄


develop (Myoldmopar) - x86_64-MacOS-10.9-clang: OK (1892 of 1892 tests passed, 0 test warnings)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.png) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.png)


Commit


On Mar 30, 2017, at 02:51 PM, Mathias Rav wrote:

>Is it intentional that an implementation of handle_RCPT can return None to
>get the default behavior? If so, that needs to be documented carefully, since
>it makes a crucial difference between "return None" and "return '250 OK'" in
>a user's handle_RCPT.

It's somewhat a side-effect of using a None return from _call_handler_hook()
to mean "there was no handler hook, use the default behavior".  OT1H that's
kind of nice in that if a handle_*() method like handle_RCPT() were to return
None, you'd get the default status.  OTOH, it might be a bug magnet.

The alternative would be to use an internal value to signal "there was no
handler hook, use the default behavior" and to treat a handler_*() method
returning None as an error.

I can't yet decide, so opinions welcome!

And for sure, the exact semantics will be documented if this PR is acceptable.


@lk-geimfari the next language is Clojure? :)


OK, I see the problem - the portal root url will always match context.absolute_url().
We rather use ``selected_tab``, which is defined in line 24 but nowhere used.
I'll prepare a PR.


This option hasn't been sufficiently replaced yet.  Need to solve in https://github.com/gulp-sourcemaps/rename-sourcemap


,Vaibhav Aggarwal


Conceptual implementation (#1)
Part 2b: Receiver UI
- [x] Show notification to receiving user


On Mar 30, 2017, at 02:53 PM, Mathias Rav wrote:

>Why do these tests add options to envelope.rcpt_options, but not address to
>envelope.rcpt_tos? This behavior should certainly be allowed by aiosmtpd, but
>it is a weird behavior to put on display in aiosmtpd's unit tests, since it
>is almost certainly never what you want to do in user code.

It's really just an omission of no consequence for the test, but I think it's
a good idea to add it in case people use the test suite as an example.  Good
catch, thanks.


@mcconkiee how come this is red? or it some weird compile issue


master (evanweaver) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: Build Failed

![Build Badge](http://img.shields.io/badge/build%20status-failing-red.png)


Ah okay. Should I revert the changes now?


@seaneking just a gotcha to watch out for - missing a `() => ` which is causing `test` to run anytime any gulp task is run


Oh I see there were already a lot of automated changes and strings for `it`. Who should be reviewing `templates` changes?


why not?


Modified description to include filename format


@donmccurdy @mrdoob anything to document here why the metallicRoughness channels were swapped from the original glTF boombox example texture?

https://github.com/KhronosGroup/glTF-Sample-Models/blob/master/2.0/BoomBox/glTF-pbrSpecularGlossiness/BoomBox_metallicRoughness.png

With this change we detach from the original glTF 2.0 sample files. (WebGL/OpenGL)

I think it would be useful to document this issue while exporting maps from texturing applications and posible helpful to glTF exporters be aware to swap channels for an specific reason. I'll be happy to extend the documentation on this.

I think this can produce unexpected results if something is not following to the original specification or an issue is solved without documenting why.

Thanks.

-Antonio


The following doc(s) have been deployed to the [audittaxon](https://audittaxon-static-docs.pantheonsite.io/docs) Multidev environment:
- [app/config/sculpin_site.yml](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/app/config/sculpin_site.yml)
- [docs/getting-started](https://audittaxon-static-docs.pantheonsite.io/docs/getting-started)
- [docs/site-owner-faq](https://audittaxon-static-docs.pantheonsite.io/docs/site-owner-faq)
- [source/_partials/footer_scripts.html](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/_partials/footer_scripts.html)
- [source/_partials/topics/automate.html](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/_partials/topics/automate.html)
- [source/_partials/topics/develop.html](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/_partials/topics/develop.html)
- [source/_partials/topics/get-started.html](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/_partials/topics/get-started.html)
- [source/_partials/topics/go-live.html](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/_partials/topics/go-live.html)
- [source/_partials/topics/manage.html](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/_partials/topics/manage.html)
- [source/_partials/topics/performance.html](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/_partials/topics/performance.html)
- [source/_partials/topics/platform.html](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/_partials/topics/platform.html)
- [source/_partials/topics/troubleshoot.html](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/_partials/topics/troubleshoot.html)
- [source/_views/topic.html](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/_views/topic.html)
- [source/docs.html](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/docs.html)
- [source/docs/assets/css/main.css](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/docs/assets/css/main.css)


At this point we need to keep them in (we would lose translations), and I would be the right person to review the PR to templates (just for a sanity check).


cc @chrisseaton

removing the forgotten todos in next commit


The asprintf() family is nice, but it isn't portable


@boy0001 Build failed to compile. :(
http://ci.athion.net/job/FastAsyncWorldEdit/608/console


Hmm, maybe I'm a bit thick, but I think I don't understand what you mean by a tight bound here and/or why it matters.  To avoid confusion, let's use the word "point" to mean any arbitrary point, and the word "member" to mean a point that's actually stored in a leaf node of the kd-tree.  So there's an infinite number of "points" but a finite number of "members".

As count_neighbours traverses the nodes of the trees, it keeps track of the min/max distance between a pair of points in rect1 and rect2, respectively, regardless of whether there's a pair of members in rect1 & rect2 that are actually that far away.  In your sketch, the maximum (squared) distance between a point in the left box and a point in the right box really is dx^2 + dy^2.  I'm guessing that by tight-bound you mean the maximum of the pairwise distances between members of `rect1` and of `rect2`.  I'm not seeing why that's a relevant quantity...

As I understood it, the way the minimum and maximum distances are used in count_neighbours is as an optimization that short-circuits the traversal of the nodes in each kd-tree as early as possible.  Meaning you could comment out lines 1549-1551 and completely ignore `min_distance` and `max_distance` without the final counts changing (they'd just be calculated a lot more slowly).  The idea is this: every point inside rect1 is less than `max_distance` away from any point inside `rect2`.  In particular, this is true for every pair of members of rect1 and rect2.  If you're asking for the number of pairs of members within a distance r of each other, and r > max_distance, then every pair of members (a,b) from rect1 and rect2 respectively should be included in the count (because a hyper-sphere of radius r centered at any member in rect1 completely contains rect2).  Conversely, min_distance is the minimum distance between any point in rect1 and any point in rect2.  If that's bigger than r, then no pairs of members (a,b) from those two rectangles will contribute to the count.  If neither of these conditions hold, the count depends on the details: either you do a brute-force O(N^2) count if the nodes are small enough, or you split one or both of the two hyper-rectangles and recurse.

What am I missing?


Yep my bad, was wondering what was causing it, and I did know it had to be called by a function, just didn't spot it


revert-6039-NewErrorWhenHoursShownInFirstColumnOfTable (Myoldmopar) - Win64-Windows-7-VisualStudio-14: OK (0 of 0 tests passed, 0 test warnings)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.png) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.png)


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


Only one GC is needed here?  I thought that for finalizable objects you needed two rounds to free them.


![](https://github.trello.services/images/mini-trello-icon.png) [Philipp_SA_Method 1 (Simple Computation)](https://trello.com/c/gBUr2xHn/4-philipp-sa-method-1-simple-computation)


I changed the wiki and added an example. I'll probably add examples to the other points later.

Thanks @perdjurner 🚨


**Whoops!**

There were *1 warnings* that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.

**WARNINGS**
[`src/content/en/showcase/2017/santa.md#L24`](https://github.com/Google/WebFundamentals/blame/007becff9af4e11bff715acad1a76a637c197cf6/src/content/en/showcase/2017/santa.md#L24) - Line must be at most 100 characters


Is this correct? We want to keep memtable disabled in prepare stage (only write prepare section to WAL, this is current behavior). We want to disable memtable on line 272 and only write to WAL, but this  time only the commit-time WriteBatch + commit marker.


All good, that's the problem with arrow function expressions, they're so subtle it's so easy to miss them.


develop (evanweaver) - i386-Windows-7-VisualStudio-12: Build Failed

![Build Badge](http://img.shields.io/badge/build%20status-failing-red.png) ![Test Badge](http://img.shields.io/badge/tests%20passed-NA-red.png)


Thanks... I have some idea what the issue is now when compiling on Windows, since annotation processors came up as duplicate warnings while compiling. Renaming with mx has different behavior on Unix than on Windows, so renaming to an already-present name probably isn't overwriting on Windows, but is on Unix.


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/4dc7cbbe-841c-4711-bae6-378fdd8e1270 "simple-toolchain-1490904402652"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/002087c1-b379-4310-92ab-6413bc3cfe72 "simple-toolchain-1490904402652") deployed this commit to [Jeff Space](https://console.ng.bluemix.net/apps/c193f73d-4bbe-4124-bd02-f721286f89cc "ibm:yp:us-south:GM Geek Week:Jeff Space")


You are right. I must have messed it up when wrapping up the patch. Will correct it.


develop (evanweaver) - Win64-Windows-7-VisualStudio-12: Build Failed

![Build Badge](http://img.shields.io/badge/build%20status-failing-red.png) ![Test Badge](http://img.shields.io/badge/tests%20passed-NA-red.png)


This simple C program will allow the user to determine which months in a certain year had the greatest amount of rainfall.
This program contains 3 functions:
- DisplayInstructions();
- HigherRainfall();
- DisplayAnswers();

The DisplayAnswers() function will give the user a brief description of what this program is all about.
The HigherRainfall() function will calculate the months with the largest rainfall.
The DisplayAnswers() function will then output the results.

The program will then give the user the option to repeat the process.


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/4dc7cbbe-841c-4711-bae6-378fdd8e1270 "simple-toolchain-1490904402652"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/002087c1-b379-4310-92ab-6413bc3cfe72 "simple-toolchain-1490904402652") deployed this commit to [Jeff Space](https://console.ng.bluemix.net/apps/a083d027-9323-4105-9f18-0ced86c1e058 "ibm:yp:us-south:GM Geek Week:Jeff Space")


master (evanweaver) - i386-Windows-7-VisualStudio-12: Build Failed

![Build Badge](http://img.shields.io/badge/build%20status-failing-red.png) ![Test Badge](http://img.shields.io/badge/tests%20passed-NA-red.png)


> May I know if anyone ever contacted you on using your code to fix/patch Java7

No, but it's unlikely to get fixed in Java 7, since it's already past end-of-life. We've since moved on to Java 8, and once Java 9 is out we'll start looking into migrating to that version. There are many performance improvements in Java 8, so I'd suggest using that version.


Nice job


Right, but the point here is not to free them, but to trigger the situation where a REFZERO would happen during a finalizer run.


Hello, How are you?
I wish we will meet urgently today.
Please send message if you are online.


master (evanweaver) - Win64-Windows-7-VisualStudio-12: Build Failed

![Build Badge](http://img.shields.io/badge/build%20status-failing-red.png) ![Test Badge](http://img.shields.io/badge/tests%20passed-NA-red.png)


I don't see where this is used, but unless you want to make the counts modifiable by some external code, I would suggest to return a `const &` instead of a pointer, and mark the method as `const`:
```c++
std::vector<std::vector<int>> const & read_counts() const {
    return m_counts;
}
```


spacja po `if`


This fixed issue #22 (dangling nodes)!


niepotrzebna spacja po `function`


It looks like the bottom of the commit message was not fully edited on the squash-and-merge


```
m_counts[modIndex][BXid] += count;
```
is equivalent a slightly more readable.


Initial commit. The environment has been set up.


Okay then, heres my email address for google hangouts flyhightech3@gmail.com


The following doc(s) have been deployed to the [audittaxon](https://audittaxon-static-docs.pantheonsite.io/docs) Multidev environment:
- [app/config/sculpin_site.yml](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/app/config/sculpin_site.yml)
- [docs/getting-started](https://audittaxon-static-docs.pantheonsite.io/docs/getting-started)
- [docs/site-owner-faq](https://audittaxon-static-docs.pantheonsite.io/docs/site-owner-faq)
- [source/_partials/footer_scripts.html](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/_partials/footer_scripts.html)
- [source/_partials/topics/automate.html](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/_partials/topics/automate.html)
- [source/_partials/topics/develop.html](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/_partials/topics/develop.html)
- [source/_partials/topics/get-started.html](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/_partials/topics/get-started.html)
- [source/_partials/topics/go-live.html](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/_partials/topics/go-live.html)
- [source/_partials/topics/manage.html](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/_partials/topics/manage.html)
- [source/_partials/topics/performance.html](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/_partials/topics/performance.html)
- [source/_partials/topics/platform.html](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/_partials/topics/platform.html)
- [source/_partials/topics/troubleshoot.html](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/_partials/topics/troubleshoot.html)
- [source/_views/topic.html](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/_views/topic.html)
- [source/docs.html](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/docs.html)
- [source/docs/assets/css/main.css](https://github.com/pantheon-systems/documentation/commit/1b61fd9117a9c1b8ad5cb9ba101f856210e051f6/source/docs/assets/css/main.css)


Commit comment


So to be clear, the first mark-and-sweep rounds detects finalizable objects and executes the finalizers (unless a prevent count blocks that). The problem beevik found occurs at this stage. The second mark-and-sweep round is needed for the rescue/free decision, but it's not really important for this test (and happens anyway in heap destruction).


What was all this about? Just curious. Why the initial diff, then the revert? Double linking when OPAM was globally installed?


This paragraph seems to contradict itself. Either Node 7 supports `async/await` natively or it requires experimental flags.

In fact, Node 7.6.0 and newer support `async/await` natively (previous v7 versions didn't) and no flags are required.


prepublish does build the ts?


Ah, I see, I was thinking the finalizer didn't get called until the second round (which I believe is the case in, e.g. the .NET CLR).  Thanks for the clarification, just wanted to make sure the test was correct.


That's a good idea, @pshrmn. Running everything every time on every browser does seem like overkill.


nice


The reason to remove sass is it uses native code and adds complexity to the website build.


Ah. I see it now.

The bounds do not need to be tight for the counting to be correct. The undetermined queries are probed later, such that the result is correct.

Thanks!


To be really technical, in Duktape 2.1 finalizer execution now happens between mark-and-sweep rounds. Typically it happens right after round 1 is finished, but if something blocks it, finalizers may be executed by a refcount dropping to zero for example. So one doesn't typically need to wait for the next mark-and-sweep round for pending finalizers to run, which is one nice benefit of using finalize_list for both refcount and mark-and-sweep finalization.

Prior to this change, round 1 of GC might not be able to run finalizers (because they were prevented by some call site), and you'd wait for round 2. If that, too, prevented finalizers, you'd wait for round 3, potentially for a long time. Now it's much less likely for finalizers to be "starved" this way.


If you want to use AtomicBoolean in this way, you can use if(closed.compareAndSet(false, true)) to ensure only a single thread gets through. You may also be able to remove the synchronized check unless you want other threads to block while the close procedure occurs.


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


> Thanks for the clarification, just wanted to make sure the test was correct.

Attention to detail very much appreciated :)


Can we hide this inside `node_modules`? That way it's one less folder for users to get confused.


IsHpBarBeingRendered*


@zheng-xq Why is `TF_AVGPOOL_USE_CUDNN` defaulted to false?


wouldn't be below message more informative and friendly? :)
```
globalData.pendingErrors += (() => (s"Instead of ${dst.input}.resized := ${src}   Try use this ${dst.input} := ${src}.resized for padding by zeros OR this ${dst.input}:= SomePaddedValue\n ${dst.input}($src.range) := ${src}  .\n$trace")
```


The existing logic should be nested in the else from the if (failed) check...


**Whoops!**

There were **6 critical errors** that broke the build and prevented it from being automatically deployed.

There were *12 warnings* that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.

**ERRORS**
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L17`](https://github.com/Google/WebFundamentals/blame/2f7b779b36ac4675503c9417540e4808a58bebd4/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L17) - Do not hard code `developers.google.com` in links.
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L51`](https://github.com/Google/WebFundamentals/blame/2f7b779b36ac4675503c9417540e4808a58bebd4/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L51) - Don’t use multiple top level headings (51:1)
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L146`](https://github.com/Google/WebFundamentals/blame/2f7b779b36ac4675503c9417540e4808a58bebd4/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L146) - Don’t use multiple top level headings (146:1)
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L185`](https://github.com/Google/WebFundamentals/blame/2f7b779b36ac4675503c9417540e4808a58bebd4/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L185) - Don’t use multiple top level headings (185:1)
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L218`](https://github.com/Google/WebFundamentals/blame/2f7b779b36ac4675503c9417540e4808a58bebd4/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L218) - Don’t use multiple top level headings (218:1)
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L238`](https://github.com/Google/WebFundamentals/blame/2f7b779b36ac4675503c9417540e4808a58bebd4/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L238) - Don’t use multiple top level headings (238:1)

**WARNINGS**
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L12`](https://github.com/Google/WebFundamentals/blame/2f7b779b36ac4675503c9417540e4808a58bebd4/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L12) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L28`](https://github.com/Google/WebFundamentals/blame/2f7b779b36ac4675503c9417540e4808a58bebd4/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L28) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L80`](https://github.com/Google/WebFundamentals/blame/2f7b779b36ac4675503c9417540e4808a58bebd4/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L80) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L94`](https://github.com/Google/WebFundamentals/blame/2f7b779b36ac4675503c9417540e4808a58bebd4/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L94) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L108`](https://github.com/Google/WebFundamentals/blame/2f7b779b36ac4675503c9417540e4808a58bebd4/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L108) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L122`](https://github.com/Google/WebFundamentals/blame/2f7b779b36ac4675503c9417540e4808a58bebd4/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L122) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L136`](https://github.com/Google/WebFundamentals/blame/2f7b779b36ac4675503c9417540e4808a58bebd4/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L136) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L159`](https://github.com/Google/WebFundamentals/blame/2f7b779b36ac4675503c9417540e4808a58bebd4/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L159) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L167`](https://github.com/Google/WebFundamentals/blame/2f7b779b36ac4675503c9417540e4808a58bebd4/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L167) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L171`](https://github.com/Google/WebFundamentals/blame/2f7b779b36ac4675503c9417540e4808a58bebd4/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L171) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L175`](https://github.com/Google/WebFundamentals/blame/2f7b779b36ac4675503c9417540e4808a58bebd4/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L175) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L245`](https://github.com/Google/WebFundamentals/blame/2f7b779b36ac4675503c9417540e4808a58bebd4/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L245) - Line must be at most 100 characters


fixes #19


I actually had a look at the code and my first gut feeling turned out to be right. The following single line change in `Buffer.h` effectively moves the check from the constructor back into the decoder loop:
```
@@ -68,6 +68,7 @@ public:
   Buffer& operator=(const Buffer& rhs);

   Buffer getSubView(size_type offset, size_type size_) const {
+    size_ = std::min(size_, size - offset);
     return Buffer(getData(offset, size_), size_);
   }
   Buffer getSubView(size_type offset) const {
```
Or limit the effect to the LJPEGDecompressors:
```
@@ -141,7 +141,8 @@ class AbstractLJpegDecompressor
 public:
   AbstractLJpegDecompressor(const Buffer& data, Buffer::size_type offset,
                             Buffer::size_type size, const RawImage& img)
-      : input(data, offset, size, getHostEndianness() == big), mRaw(img) {}
+      : input(data, offset, std::min(size, data.getSize() - offset),
+              getHostEndianness() == big), mRaw(img) {}
   AbstractLJpegDecompressor(const Buffer& data, Buffer::size_type offset,
                             const RawImage& img)
       : AbstractLJpegDecompressor(data, offset, data.getSize() - offset, img) {}
```

It basically does what your (not pushed) version does but does so for all the decompressors at once. It is safe, too, because any later access outside of the (cropped) sub-buffer will throw when it happens.


In fact, that's what you can see in Node 7.6.0 or newer in `node --v8-options`:
```
  --harmony_async_await (enable "harmony async-await")
        type: bool  default: true
```
so this flag is already turned on.


I love that you decided to randomize test data! Food for thought... what if we optimize it like this?
var randomNum = [];
for (var i = 0; i < 10; i++) {
    randomNum.push( Math.floor(Math.random() * 10 );
}
`


<details>

<summary>No TaskCluster jobs started for this pull request</summary>

```js

The `allowPullRequests` configuration for this repository (in `.taskcluster.yml` on the
default branch) does not allow starting tasks for this pull request.
```

</details>


ce truc c'est la meme chose en fait, c'est juste qu'on l'appelle singleton 😃


@mapasteper sorry you'll need to set `vagrant_box: beet/dev` should really make this the default due to https://github.com/beetboxvm/beetbox/issues/391#issue-209679900

Will likely be version jumping a lot more..


For what it is worth, here is the fix of my code for truncated files the way I would have done it:
```
@@ -101,10 +101,11 @@ public:
     assert(nbits <= Cache::MaxGetBits);
     if (cache.fillLevel < nbits) {
 #if BUFFER_PADDING==0
+      constexpr int MaxRequiredBytes = 8;
       // disabling this run-time bounds check saves about 1% on intel x86-64
-      if (pos + Cache::MaxGetBits/8 > size) {
+      if (pos + MaxRequiredBytes > size) {
         if (pos < size) {
-          uchar8 tmp[4] = {0, 0, 0, 0};
+          uchar8 tmp[MaxRequiredBytes] = {};
           memcpy(tmp, data + pos, size - pos);
           pos += fillCache(tmp);
         } else if (pos < size + 4) {
```


renommer en isSameSetAndList


Please revert this file back to the original file, there is no need to make any adjustments to this file


Also you should only be cloning the project if you're wanting to contribute.

see. https://github.com/beetboxvm/beetbox#quickstart


Hey @NathanWalker I think I have a fix which removes all this wacky-ness. Will push now.


The following doc(s) have been deployed to the [earlyaccess](https://earlyaccess-static-docs.pantheonsite.io/docs) Multidev environment:
- [docs/free-https](https://earlyaccess-static-docs.pantheonsite.io/docs/free-https)
- [source/_partials/footer_scripts.html](https://github.com/pantheon-systems/documentation/commit/ca4b08b401b329b98cab3d72460375b6e64ccf78/source/_partials/footer_scripts.html)
- [docs/errors-and-server-responses](https://earlyaccess-static-docs.pantheonsite.io/docs/errors-and-server-responses)
- [docs/timeouts](https://earlyaccess-static-docs.pantheonsite.io/docs/timeouts)


@hellofornow lemme merge this, then we can put your PR on master


I have tests fixed now.


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/4b4c94fd-7671-4165-8e6a-7c3978f083ef "jce-test-operations1"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/b7f6ce9a-64ec-49f2-bf7a-24a79958b3ca "jce-test-ops-pipeline") deployed this commit to [testops](https://console.ng.bluemix.net/apps/ea2de859-62a2-4d8b-96a0-5dba0535fb0a "ibm:yp:us-south:jceorg:testops")


date table


I think it would be a bug magnet. Introducing a `_no_handler = object()` marker would make it explicit that handlers wrap use aiosmtpd's default behavior, and ensuring that the handler result is of type str (or bytes?) makes it clear that a status code must be returned.


**Whoops!**

There were **6 critical errors** that broke the build and prevented it from being automatically deployed.

There were *6 warnings* that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.

**ERRORS**
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L19`](https://github.com/Google/WebFundamentals/blame/1d458aa642907629fede532d1320b032306e117b/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L19) - Do not hard code `developers.google.com` in links.
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L53`](https://github.com/Google/WebFundamentals/blame/1d458aa642907629fede532d1320b032306e117b/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L53) - Don’t use multiple top level headings (53:1)
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L150`](https://github.com/Google/WebFundamentals/blame/1d458aa642907629fede532d1320b032306e117b/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L150) - Don’t use multiple top level headings (150:1)
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L197`](https://github.com/Google/WebFundamentals/blame/1d458aa642907629fede532d1320b032306e117b/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L197) - Don’t use multiple top level headings (197:1)
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L230`](https://github.com/Google/WebFundamentals/blame/1d458aa642907629fede532d1320b032306e117b/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L230) - Don’t use multiple top level headings (230:1)
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L250`](https://github.com/Google/WebFundamentals/blame/1d458aa642907629fede532d1320b032306e117b/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L250) - Don’t use multiple top level headings (250:1)

**WARNINGS**
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L83`](https://github.com/Google/WebFundamentals/blame/1d458aa642907629fede532d1320b032306e117b/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L83) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L98`](https://github.com/Google/WebFundamentals/blame/1d458aa642907629fede532d1320b032306e117b/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L98) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L112`](https://github.com/Google/WebFundamentals/blame/1d458aa642907629fede532d1320b032306e117b/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L112) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L126`](https://github.com/Google/WebFundamentals/blame/1d458aa642907629fede532d1320b032306e117b/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L126) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L140`](https://github.com/Google/WebFundamentals/blame/1d458aa642907629fede532d1320b032306e117b/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L140) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L257`](https://github.com/Google/WebFundamentals/blame/1d458aa642907629fede532d1320b032306e117b/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L257) - Line must be at most 100 characters


I'm guessing you don't have https://github.com/LineageOS/android_external_ahbottomnavigation


This temp dir will be in the root of `electric` not the project itself, so technically it will be inside `node_modules`.


This probably should be in all blocks that implement `IBlockWithFacing`, maybe handle it generically?


**Whoops!**

There were *6 warnings* that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.

**WARNINGS**
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L83`](https://github.com/Google/WebFundamentals/blame/1d4a849b444764b9f62049c1e36202a5626f47d5/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L83) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L98`](https://github.com/Google/WebFundamentals/blame/1d4a849b444764b9f62049c1e36202a5626f47d5/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L98) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L112`](https://github.com/Google/WebFundamentals/blame/1d4a849b444764b9f62049c1e36202a5626f47d5/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L112) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L126`](https://github.com/Google/WebFundamentals/blame/1d4a849b444764b9f62049c1e36202a5626f47d5/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L126) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L140`](https://github.com/Google/WebFundamentals/blame/1d4a849b444764b9f62049c1e36202a5626f47d5/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L140) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L257`](https://github.com/Google/WebFundamentals/blame/1d4a849b444764b9f62049c1e36202a5626f47d5/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L257) - Line must be at most 100 characters


Sorry, I was waiting for your or Markus  confirmation about that property.


**Whoops!**

There were *6 warnings* that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.

**WARNINGS**
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L83`](https://github.com/Google/WebFundamentals/blame/62bd40380830c58433d3781193a38cee780865eb/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L83) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L98`](https://github.com/Google/WebFundamentals/blame/62bd40380830c58433d3781193a38cee780865eb/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L98) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L112`](https://github.com/Google/WebFundamentals/blame/62bd40380830c58433d3781193a38cee780865eb/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L112) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L126`](https://github.com/Google/WebFundamentals/blame/62bd40380830c58433d3781193a38cee780865eb/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L126) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L140`](https://github.com/Google/WebFundamentals/blame/62bd40380830c58433d3781193a38cee780865eb/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L140) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L257`](https://github.com/Google/WebFundamentals/blame/62bd40380830c58433d3781193a38cee780865eb/src/content/en/fundamentals/engage-and-retain/push-notifications/common-issues-and-reporting-bugs.md#L257) - Line must be at most 100 characters


What the hell


Me perdi


ohhh got it!


super


![](https://github.trello.services/images/mini-trello-icon.png) [Сделать 3 экрана в приложении (основной - карта, дополнительный - в виде списка, экран просмотра (переход на него происходит при нажатии на метку или позицию в списке из экрана 2))](https://trello.com/c/BVm0Qw8C/9-3-2)


I'm not sure there's much need for this. With a keyboard that supports speech-to-text there's no changes needed in the app to do this.


So the reason for changing this was that "My_First_Score" was not being translated?


Alright, will call you tomorrow(your tomorrow) ~ say in about 18-20ish hours (using hours so we don't have timezone confusion). Will you be able to make it by that time?

Going to sleep now. Somehow couldn't code as much today, tired. Good night


Thanks! BitHub has sent payment of  $58.08USD for this commit.


Correction: 'If they are set, SlackNotification routes requests through a proxy.'


Are you sure you can't see a black and white "Edit" button, top middle of the page when logged in with the same github account?


It might be best to not use **spaces** in the file name.  The operating system requires you to put the names in quotes if you do something with them from the `command` line.


Unfortunately, this still won't work. Let's talk tomorrow.


preparing release 3.0.0-rc.1 (#3320)

Demo: quicktests | fiddle


where is the source for devmem2 ? We should include it in `resources/`


i still cant get right


@Widmaer hey, please don't push to master


@Widmaer hey please don't push to master branch


Изменения по 1 пункту


What was the reason of going back to beta version?


update circle.yml to accept beta or rc tags

Demo: quicktests | fiddle


The following doc(s) have been deployed to the [earlyaccess](https://earlyaccess-static-docs.pantheonsite.io/docs) Multidev environment:
- [docs/free-https](https://earlyaccess-static-docs.pantheonsite.io/docs/free-https)
- [source/_partials/footer_scripts.html](https://github.com/pantheon-systems/documentation/commit/ca4b08b401b329b98cab3d72460375b6e64ccf78/source/_partials/footer_scripts.html)
- [docs/errors-and-server-responses](https://earlyaccess-static-docs.pantheonsite.io/docs/errors-and-server-responses)
- [docs/timeouts](https://earlyaccess-static-docs.pantheonsite.io/docs/timeouts)


@kuncevic - see https://github.com/angular/flex-layout/blob/master/CHANGELOG.md


The problem with removing unused variables and members is that it doesn't work when reflection is used to access them. Eclipse keeps removing them because they are not referenced at compile time, only at runtime.
I don't see many options, either remove the save actions or change the code to not abuse reflection.


nice


https://github.com/PowerShell/Win32-OpenSSH/issues/642
https://github.com/PowerShell/Win32-OpenSSH/issues/643


No problem, thank you! :)


@quxiaofeng where did this commit sha come from? https://github.com/quxiaofeng/ProjectiveDictionaryPairLearning.jl/commit/202c366bd1ec1d367289689410ce12aa9fc040e0 does not exist, gives a 404


modify-ctf-restrictions (nealkruis) - x86_64-MacOS-10.9-clang: OK (2487 of 2488 tests passed, 94 test warnings)

 * 95 tests had: EIO diffs.
 * 6 tests had: ESO small diffs.
 * 6 tests had: MTR small diffs.
 * 5 tests had: Table small diffs.
 * 1 test had: ESO big diffs.

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.png) ![Test Badge](http://img.shields.io/badge/tests%20passed-99.96%25-yellow.png)


This final commit was correcting branch merge conflicts. Challenge completed at 3 hours 30 mins


update circle.yml to accept beta or rc tags (#3321)

Demo: quicktests | fiddle


Change this to ui-sref model.  See vc-list.html as an example: "ui-sref="p.vc.edit({vcId:o._id})">"


fixes #16


Please have a look at RUNTIME log  searching for FAILED


-a c'est legit le cancer de git


wtf


reference the date of the commit, prior to 7.6.0. not sure why you chose to bikeshed this, but a component/app/program/script can have native support for a feature with which a flag is required to activate it. I appreciate the interest in the module, but this could have been a new issue requesting an update to README, or a really simple PR, rather than the pair of comments (we do have an edit button for comments too) on an old commit.


The commit message should say "added css and updated index.html"


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/f3af8dee-f277-43ef-9465-9e22e6377b45 "sam-iot"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/c884975f-1685-491d-a673-4964cfefedbc "sam-iot") deployed this commit to [dev](https://console.ng.bluemix.net/apps/cfa264ae-cc12-43f0-b8c1-b06e1ac8f5f1 "ibm:yp:us-south:azad.sm:dev")


@mwatson2, can you please take a look and give us your feedback via the issue tracker?  Thanks!


Cahnges the class name mscl_sms_api to sms_api


like a world


I'm just playing around here


Probably both @JoryHogeveen?


Changes are made from the forked sscalendar repository found here:
https://github.com/srchang8/sscalendar/commits/master


@jordivs este cambio se supone debe ya restringir la navegación a la carpeta del template.


Please do "NOT" I don't think you should put that lol..


Deprecated


Yeah now i c, it just wasn't there back then


> Slightly longer answer: IFD that points to itself, i think, basically.

I see. A bit worried about the invasiveness of your change, I had a look and created a test for an infinite IFD loop and found that the check for the tree depth overflow was at the wrong spot for this type of invalid input. The stack blows up before the check gets executed even once. What is missing is the same check inside the `TiffIFD` constructor (just as you did above). But there is no need to introduce all the other explicit `parent` handling noise. The patch should be something like a 10-line diff limited to TiffIFD.cpp/h.

P.S. my offer to look into issues with my code as soon as they show up still stands.


_sans-serf_ should be _sans-serif_


ok


https://youtu.be/px6ZhgLsurw    - Payload URL: `https://us-central1-<FIREBASE_PROJECT_ID>.cloudfunctions.net/githubWebhook`


@gfinak @ptvan @raphg @jkrijthe
I tweaked the c code a bit and now it can reduce the time to `1/4` with `4` cores .
```r
> library(Rtsne)
> microbenchmark(tsne_out <- Rtsne.multicore(mat, num_threads = 4), tsne_out <- Rtsne(mat), times = 10)
Unit: milliseconds
                                              expr       min       lq      mean    median        uq       max
 tsne_out <- Rtsne.multicore(mat, num_threads = 4)  397.5955  420.316  443.3131  443.8844  472.0137  500.7039
                            tsne_out <- Rtsne(mat) 1513.6374 1565.089 1649.1845 1632.9498 1708.1396 1876.7073
 neval
    10
    10
```


We also want to remove this line so that we are not writing our batch to the WAL twice.


0 is the normal exit status. Non-zero implies the process exited with an error


+ - Install dependencies locally by running: `cd functions; npm install; cd -`


Since this is the full instruction, opcode probably isn't the proper var name


Only commit-time batch + commit marker. GetWriteBatch()->GetWriteBatch() was written to WAL during prepare phase.


It appears that feeding dateutil.parser a datetime object no longer raises an AttributeError, but instead raises a TypeError in dateutil >v2.2


bt a la verga angel
atentamente yo


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/067fcae6-6179-4a7f-96dd-484c68400da7 "simple-toolchain-1490840845266"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/a0958ec0-e460-45cb-b70a-b2760ea335c7 "simple-toolchain-1490840845266") deployed this commit to [test](https://console.ng.bluemix.net/apps/d022f1cc-d799-4781-84b5-18d47b079c7e "ibm:yp:us-south:talabal:test")


Needed to properly create post in controller when post is nested below topics. Also needed to assign topic and user when building new post for test.


I'd like to get this Chapter 3 section (Increasing/Decreasing) wrapped up and a print version ready to hand out to the 251 instructors next term.


It contains hdfs-site.xml, etc. not just hbase configurations.


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/067fcae6-6179-4a7f-96dd-484c68400da7 "simple-toolchain-1490840845266"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/a0958ec0-e460-45cb-b70a-b2760ea335c7 "simple-toolchain-1490840845266") deployed this commit to [test](https://console.ng.bluemix.net/apps/35c95b39-a11f-4487-b434-1bc93fe5223e "ibm:yp:us-south:talabal:test")


你為什麼空白還要留著啊XD


1. Create a FeatureLayer and add it to a map
2. Create a PopupTemplate object and add a title
3. Add content to the PopupTemplate
4. Use fieldInfos to format field values
5. Set the PopupTemplate on the layer


Bluemix [toolchain](https://console.ng.bluemix.net/devops/toolchains/d82d830c-d81f-47da-8a0d-926eb78fbb91 "ArtesianBore"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/0b93f73a-9ee8-4e41-844e-8354a83495f8 "ArtesianBore") deployed this commit to [WaterCorp](https://console.ng.bluemix.net/apps/9b6a2818-beb1-4fd8-a364-2e2394f7bb6e "ibm:yp:us-south:dwoo@nz1.ibm.com:WaterCorp")


hh


TEsting this shit...


Forgot to add...

This update to the Teams App implements TeamID hashing, which deprecates most of the done towards "Aliasing" files when there are updates or edits to Team or User names. *shudder*

This update also improves security by removing the TeamName from the way HRCloud2 stores the Team. When looking at a standard, un-encrypted Team directory all the Team directory names and cache files will have hashed filenames (from HRC2 Admin salts). This is consistent with the way UserID's are handled through HRC2.


Looks good.


现在有一个这样的工具类可以展示的，封装好的。


Should we 1.0 soon? Are there any kinks to be worked out? Now that we no longer manually build libfuzzer in a separate dir and have a good CLI not sure if there's any polish left to be done.


Maybe we should open an issue talking about what 1.0 should look like.


**Whoops!**

There were *52 warnings* that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.

**WARNINGS**
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L4`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L4) - WF Tag `wf_updated_on` must be within the last 7 days.
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L260`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L260) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L264`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L264) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L4`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L4) - WF Tag `wf_updated_on` must be within the last 7 days.
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L78`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L78) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L82`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L82) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L86`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L86) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L91`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L91) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L93`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L93) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L101`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L101) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L103`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L103) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L119`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L119) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L123`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L123) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L150`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L150) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L154`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L154) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L177`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L177) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L181`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L181) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L239`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L239) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L253`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L253) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L311`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L311) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L315`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L315) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/faq.md#L4`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/faq.md#L4) - WF Tag `wf_updated_on` must be within the last 7 days.
[`src/content/en/fundamentals/engage-and-retain/push-notifications/faq.md#L53`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/faq.md#L53) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/good-notification.md`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/good-notification.md) - Unable to read file, was it deleted?
[`src/content/en/fundamentals/engage-and-retain/push-notifications/handling-messages.md#L4`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/handling-messages.md#L4) - WF Tag `wf_updated_on` must be within the last 7 days.
[`src/content/en/fundamentals/engage-and-retain/push-notifications/how-push-works.md#L4`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/how-push-works.md#L4) - WF Tag `wf_updated_on` must be within the last 7 days.
[`src/content/en/fundamentals/engage-and-retain/push-notifications/how-push-works.md#L69`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/how-push-works.md#L69) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/index.md#L5`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/index.md#L5) - WF Tag `wf_updated_on` must be within the last 7 days.
[`src/content/en/fundamentals/engage-and-retain/push-notifications/non-standards-browsers.md#L4`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/non-standards-browsers.md#L4) - WF Tag `wf_updated_on` must be within the last 7 days.
[`src/content/en/fundamentals/engage-and-retain/push-notifications/non-standards-browsers.md#L73`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/non-standards-browsers.md#L73) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/non-standards-browsers.md#L78`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/non-standards-browsers.md#L78) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/non-standards-browsers.md#L108`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/non-standards-browsers.md#L108) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/non-standards-browsers.md#L112`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/non-standards-browsers.md#L112) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/non-standards-browsers.md#L116`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/non-standards-browsers.md#L116) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/non-standards-browsers.md#L120`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/non-standards-browsers.md#L120) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L4`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L4) - WF Tag `wf_updated_on` must be within the last 7 days.
[`src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L138`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L138) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L158`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L158) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L171`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L171) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L185`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L185) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L4`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L4) - WF Tag `wf_updated_on` must be within the last 7 days.
[`src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L48`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L48) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L57`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L57) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L62`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L62) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L106`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L106) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L111`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L111) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L115`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L115) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/permissions-subscriptions.md`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/permissions-subscriptions.md) - Unable to read file, was it deleted?
[`src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L4`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L4) - WF Tag `wf_updated_on` must be within the last 7 days.
[`src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages.md`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages.md) - Unable to read file, was it deleted?
[`src/content/en/fundamentals/engage-and-retain/push-notifications/subscribing-a-user.md#L4`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/subscribing-a-user.md#L4) - WF Tag `wf_updated_on` must be within the last 7 days.
[`src/content/en/fundamentals/engage-and-retain/push-notifications/web-push-protocol.md#L4`](https://github.com/Google/WebFundamentals/blame/966bf84b4e74baef4ad7cd52efe81c6c2372a49f/src/content/en/fundamentals/engage-and-retain/push-notifications/web-push-protocol.md#L4) - WF Tag `wf_updated_on` must be within the last 7 days.


It's not necessary. You can use multiple buildpacks: [
Using Multiple Buildpacks for an App](https://devcenter.heroku.com/articles/using-multiple-buildpacks-for-an-app). Example here https://github.com/jincod/AspNet5DemoApp


**对方是否都是**


ff


Wow, thanks for the tip. Didn't occur to me to use an extra buildpack. Appreciate it!


In minigbm, HAL_PIXEL_FORMAT_YCbCr_420_888 resolve_format is DRM_FORMAT_YVU420, which plane num is 3. But DRM_FORMAT_NV12 plane num is 2.


感觉可以用map


   <?php
function convertBin($decimalNum)
{

 $binaryNum = '';
 do
  {
   $binaryNum = bcmod($decimalNum,'2') . $binaryNum;
   $decimalNum = bcdiv($decimalNum,'2');
  } while (bccomp($decimalNum,'0'));

 return($binaryNum);
}
?>

<?php
echo convertBin('90');
?>


![](https://github.trello.services/images/mini-trello-icon.png) [Lessons don't refresh when one is deleted.](https://trello.com/c/FsCL5yEh/66-lessons-don-t-refresh-when-one-is-deleted)


I've just read the CppCoreGuidelines and they also recommend using braced syntax always (recommended read btw, makes mane things more clear).


@brewsfab
Ooohhh I got it!!!! Thank you!
I must have not been listening too hard on the lesson.


![](https://github.trello.services/images/mini-trello-icon.png) [The user is erroneously presented with a blank lesson level.](https://trello.com/c/26tIVVpZ/65-the-user-is-erroneously-presented-with-a-blank-lesson-level)


yeah, I was thinking about it


@depay this line has an error, you have added one more `)` at the end.


initial


second one


I am learning Proland too. Now i am dealing with ork ~~...
you have any suggestions on this learning procedure ?


I think there's a problem with the api on Kodi 17. The method is expecting image and not icon for the name of info, warning, and error image attribute. ATTR_ICON from const.py is icon
from kodi 17 jsonrpc:
```
"GUI.ShowNotification": {
			"description": "Shows a GUI notification",
			"params": [
				{
					"name": "title",
					"required": true,
					"type": "string"
				},
				{
					"name": "message",
					"required": true,
					"type": "string"
				},
				{
					"default": "",
					"name": "image",
					"type": [
						{
							"enums": [
								"info",
								"warning",
								"error"
							],
							"type": "string"
						},
						{
							"type": "string"
						}
					]
				},
				{
					"default": 5000,
					"description": "The time in milliseconds the notification will be visible",
					"minimum": 1500,
					"name": "displaytime",
					"type": "integer"
				}
			],
			"returns": {
				"type": "string"
			},
			"type": "method"
		}
```

from const.py:
```
# Icon to use in the frontend
ATTR_ICON = 'icon'
```


You've generated some buzz here: https://www.reddit.com/r/wowservers/comments/629qgy/showcase_of_l4g_devs_skill_xd/