Thank you.

PHD Student of Islamic Azad University Yazd Branch
Faculty Member of Islamic Azad University Shahrekord Branch
Home Page:
http://iaushk.ac.ir/part/pages.aspx?id=74&pid=1
Google Citation :
http://scholar.google.com/citations?user=ZXfOfdQAAAAJ&hl=en
Work Phone: 03833361000 - 403
Cell Phone:09132800436

On Fri, Mar 3, 2017 at 12:47 PM, Sevil Dräxler <notifications@github.com>
wrote:

> You need to run the heuristic by specifying a request file and a network
> file. I just committed some example files you can use. You can make your
> own requests using makeRequestList.py and use other networks if you wish
> to. Pickle files of other SNDlib network topologies are in tops folder.
>
>
> On 03/03/2017 10:04 AM, Pouya Khosravian Dehkordi wrote:
> >
> > I am going to run heuristic file but after run it i give this error:
> > Warning (from warnings module):
> > File "C:\Python27\lib\site-packages\matplotlib_/init/_.py", line 1401
> > warnings.warn(_use_error_msg)
> > UserWarning: This call to matplotlib.use() has no effect
> > because the backend has already been chosen;
> > matplotlib.use() must be called /before/ pylab, matplotlib.pyplot,
> > or matplotlib.backends is imported for the first time.
> >
> > Traceback (most recent call last):
> > ** IDLE Internal Exception:
> > File "C:\Python27\lib\idlelib\run.py", line 325, in runcode
> > exec code in self.locals
> > File "C:\Python27\flexible-service-placement-master\heurun.py", line
> > 15, in
> > reqtype = sys.argv[1]
> > IndexError: list index out of range
> > help me?
> >
> > —
> > You are receiving this because you authored the thread.
> > Reply to this email directly, view it on GitHub
> > <https://github.com/CN-UPB/flexible-service-placement/commit/
> 8ba61a2e2171300405026c5e7fbd313cb726bbe6#commitcomment-21135436>,
> > or mute the thread
> > <https://github.com/notifications/unsubscribe-auth/ABK34yt-
> WAz0LwBuePhRE42t5x9XPYZ9ks5rh9etgaJpZM4MSAHA>.
>
> >
>
> --
> Sevil Dräxler (née Mehraghdam), M.Sc.
> University of Paderborn
> Computer Networks group – https://cs.uni-paderborn.de/cn
> Tel.: +49 5251 / 601755
> Room: O3.161
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/CN-UPB/flexible-service-placement/commit/8ba61a2e2171300405026c5e7fbd313cb726bbe6#commitcomment-21135574>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AP0oQdl-43yZ6GJweAr2ZzeHOn4nFUiLks5rh9qzgaJpZM4MSAHA>
> .
>


A log file will be created if you provide the required arguments
(request name and network name) when running the heuristic.

On 03/03/2017 10:08 AM, Pouya Khosravian Dehkordi wrote:
> can you give me an example to run it by log file?
> thank you
>
> PHD Student of Islamic Azad University Yazd Branch
> Faculty Member of Islamic Azad University Shahrekord Branch
> Home Page:
> http://iaushk.ac.ir/part/pages.aspx?id=74&pid=1
> Google Citation :
> http://scholar.google.com/citations?user=ZXfOfdQAAAAJ&hl=en
> Work Phone: 03833361000 - 403
> Cell Phone:09132800436
>
>
>
>
> On Fri, Mar 3, 2017 at 12:22 PM, Sevil Dräxler <notifications@github.com>
> wrote:
>
> > Hi, you don't need anything there, you can simply comment out all
> > logging commands.
> >
> >
> > On 03/03/2017 09:45 AM, Pouya Khosravian Dehkordi wrote:
> > >
> > > hi
> > > i read these file and i am going to run code but i need log file:
> > > logFile = str(reqtype) + '/' + str(network) + '/' + str(day) + ".log"
> > > please help me
> > > thank you
> > >
> > > —
> > > You are receiving this because you authored the thread.
> > > Reply to this email directly, view it on GitHub
> > > <https://github.com/CN-UPB/flexible-service-placement/commit/
> > 8ba61a2e2171300405026c5e7fbd313cb726bbe6#commitcomment-21135236>,
> > > or mute the thread
> > > <https://github.com/notifications/unsubscribe-
> > auth/ABK34-3Q-JkE7OGh25UF6bvX-dxAob0gks5rh9M5gaJpZM4MSAHA>.
> > >
> >
> > --
> > Sevil Dräxler (née Mehraghdam), M.Sc.
> > University of Paderborn
> > Computer Networks group – https://cs.uni-paderborn.de/cn
> > Tel.: +49 5251 / 601755
> > Room: O3.161
> >
> > —
> > You are receiving this because you commented.
> > Reply to this email directly, view it on GitHub
> >
> <https://github.com/CN-UPB/flexible-service-placement/commit/8ba61a2e2171300405026c5e7fbd313cb726bbe6#commitcomment-21135292>,
> > or mute the thread
> >
> <https://github.com/notifications/unsubscribe-auth/AP0oQTvAZCRJtXxjDPrHl4RLY7uqVT_Gks5rh9TTgaJpZM4MSAHA>
> > .
> >
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/CN-UPB/flexible-service-placement/commit/8ba61a2e2171300405026c5e7fbd313cb726bbe6#commitcomment-21135486>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ABK347OQN1yyhYXtOvLYOgzNwbKga8i7ks5rh9iqgaJpZM4MSAHA>.
>

--
Sevil Dräxler (née Mehraghdam), M.Sc.
University of Paderborn
Computer Networks group – https://cs.uni-paderborn.de/cn
Tel.: +49 5251 / 601755
Room: O3.161


Yep, if you start rinCheat SE with wifi on it should be automatically downloaded from the Repository with the whole databases for both rinCheat SE and standard rinCheat.


@shibukawa @tk0miya the merge of stable into master branch creates flake8 error, but does not seem related to this particularly. Sorry, because Travis currently fails on master.


whtat does this do?


TeamCity CI BACKEND :: TEST_CHAIN :: template_ci [Build 316](https://teamcity.forcity.io/viewLog.html?buildId=12603&buildTypeId=TestChain_TemplateCi) outcome was **SUCCESS**
Summary: Tests failed: 1, passed: 2 Build time: 00:00:46


Thanks for reply
But still I am confuse about how the map is made? How will I make the make the map of original situation where my tag is?
Kindly can you share video of entire process.
Regards


Hey, not sure if I should open new issue but this commit breaks my completion.

I use AUTO_CD and prior to this commit inputting 'doc' would present list of completion candidates, with above changes it automatically completes to 'docker'. Problem is very annoying as even 'docu' gets completed to 'docker' (per _approximate completer).

Could you please revisit this commit as it alters user's zsh configuration.

Thanks.


升级到 6.x


yes indeed!


A nivel de diseño recuerda que puede ser interesante separar las clases de actividades/hilos del las clases que instancian objetos pasivos. Mejora la comprensión estructural pero incrementa el tamaño del código  puesto que  el hilo necesita recibir las referencias de objetos pasivos en el constructor. Tu propuesta es correcta, el comentario tiene un enfoque más didáctico.


I think I've seen 'c' in some tests.


```java
return populating.get() == Boolean.TRUE;
```


это для наглядности, забыл убрать, менять не нужно


nice


Thank you


ほーこんな風にかかれるのか〜


Sure thing, I'll keep an eye in here.


yes it is. I have been struggling with this and cannot get rid of them completely without major rewriting. I'm not convinced that the approach I have taken of creating an enormous hash is the best way. I want to do some testing and then may be able to rationalise it more. But fundamentally it's work in progress..


Thanks for pointing this, I'll change it.


yeah - slipped through. Shouldn't be there. Well spotted.


Improve your English expression. It is not "Opt".


La solución empleada para resolver la práctica utiliza tantos hilos como bolas para representar su movimiento. Además utiliza un hilo especial para repintar el tablero. Me parece correcta.
 Otra alternativa es tener tantos hilos como bolas y en el método run se invoque al movimiento de la bola y al repintado del tablero. Esta es la solución que da Doug Lea en el ejemplo de las transparencias.


The map is created using a ROS based robot mounted with a 2D lidar sensor. https://linorobot.org. It's a two separate process. Once you have a map, drag the .pgm and yaml file to the map folder and update the launch file https://github.com/grassjelly/ros_dwm1000/blob/master/launch/localize.launch#L2 .


Usually, we would not say "it save overhead" but "it reduces the overhead".


Isn't it already covered by "recipients"?


activity


if it was the only thing, I'd probably leave but since there are other bits to change, let's do it.


Don't track file "time.txt" in GIT repository.


As mentioned before. We need to fix the logo in navbar..


@shibukawa @tk0miya the [flake8 error](https://travis-ci.org/sphinx-doc/sphinx/jobs/207294049#L559) seems to be

    ./sphinx/builders/gettext.py:21:1: F401 'six.StringIO' imported but unused

but I am not sure if F401 is warning or error and if  simply removing this import would fix this. Sorry if I messed up something during merge.


This breaks assert in pyethereum, see
https://github.com/ethereum/pyethereum/issues/440


bomber man deeree togtoo bizdee all


![](https://github.trello.services/images/mini-trello-icon.png) [#2201 - Генератор номера карточки VISA](https://trello.com/c/0B4HrQND/20-2201-visa)


Respecto a la seguridad de los objetos de tipo bola para ejecutarse en entornos concurrentes. No cumplir ninguna de las reglas de básicas de sincronización.
 . Realizar siempre bloqueo durante la actualización de campos.
2. Realizar siempre bloque durante el acceso a posibles actualizadores de campos de objetos
3. Nunca realizar bloqueos cuando se invoquen a métodos de otros objetos.


[Your benchmark job](https://github.com/JuliaLang/julia/commit/ea37c3c35eb3fe6bbaa0962a048c6b26e11e5ac7#commitcomment-21133899) has completed - possible performance regressions were detected. A full report can be found [here](https://github.com/JuliaCI/BaseBenchmarkReports/blob/4af2ac73337724fe8b8285c05eeea2d44fc467ee/ea37c3c_vs_3c9d753/report.md). cc @jrevels


StringIO was introduced in this commit:

https://github.com/sphinx-doc/sphinx/pull/3490/files

It is used to cache output before writing to avoid unnecessary overwriting.


I'm ok!


Currently the output is this:

```
\hypertarget{refs}{}
\leavevmode\hypertarget{ref-Atzeni:1982}{}%
Atzeni, Paolo, and D Stott Parker Jr. 1982. “Assumptions in Relational
Database Theory.” In \emph{Proceedings of the 1st Acm Sigact-Sigmod
Symposium on Principles of Database Systems}, 1–9. Los Angeles, CA.

\leavevmode\hypertarget{ref-SPARC:1975}{}%
“Interim Report: ANSI/X3/SPARC Study Group on Data Base Management
Systems 75-02-08.” 1975. \emph{FDT - Bulletin of ACM SIGMOD} 7 (2):
1–140.
```

I don't see any horizontal space with this setup.

Perhaps we should add a % after the first hypertarget too,
but this didn't make any visible difference when I tried it.


function multiplyByNineFifths(celsius) {
  return celsius * (9/5);
}

function getFahrenheit(celsius) {
  return multiplyByNineFifths(celsius) + 32;
}


This warning and comment looks a bit off here, since this code branch is not for D2


主要是因为 browser 端使用。

github 源码上都没有 => 了，发布一个 patch 版本 ？


Hi Yoni, this means that you're doing an awful lot of work wrapped within the try-block. It is now less obvious that you only expect the strip.error.CardError to occur in the stripe.Customer.create call. Would it not be better to do:

    try:
         customer = stripe.Customer.create ....
     except strip.error.CardError, e:
          customer = None
          messages.error(request, "Your card was declined!")
     .. Then as before.


Unnecessary empty line


Me ha despistado el título de commit. Sugiero "Mejora de formateo textual de código"


PS. You should be able to get a compiled version from
pandoc-nightly

+++ Václav Haisman [Mar 02 17 09:20 ]:
>   [1]@jgm I have noticed small visual issue while constructing test case
>   for [2]#3255. I have not compiled this patched Pandoc yet but I have
>   noticed that if the resulting LaTeX looks like this, without % on the
>   second line, there is small horizontal space at the start of the
>   reference:
>
>\leavevmode\hypertarget{refs}{}%
>\hypertarget{ref-aiid3749018}{}
>Text
>
>   I think the % needs to be added to both lines or the text should
>   immediately follow the \hypertarget without the intervening new line.
>
>   —
>   You are receiving this because you were mentioned.
>   Reply to this email directly, [3]view it on GitHub, or [4]mute the
>   thread.
>
>References
>
>   1. https://github.com/jgm
>   2. https://github.com/jgm/pandoc/issues/3255
>   3. https://github.com/jgm/pandoc/commit/46135ac8758c4fbb9dfe676b1462463f5476bbff#commitcomment-21125527
>   4. https://github.com/notifications/unsubscribe-auth/AAAL5LFjOBZYZwG8fsZ3qUGVx2_ImlVaks5rhvpOgaJpZM4MRR4K


I realize I need to remove this commit and the last one!


Una buena práctica es agrupar todas las sentencias de comprobación de invariante en un métodos privado que se suele llamar checkInvariante(). De esta forma se mejora la legibilidad del código.

Recuerda que la postcondición es el chequeo del invariante en la última sentencia de un método público.


Past tense of split is split


Mismo comentario que en método Move.
Una buena práctica es agrupar todas las sentencias de comprobación de invariante en un métodos privado que se suele llamar checkInvariante(). De esta forma se mejora la legibilidad del código.

Recuerda que la postcondición es el chequeo del invariante en la última sentencia de un método público.


@mniami I think that makes sense. To give you a bit more context in the naming. Usually in Polymorphic typed FP names are `F[_]`, `G[_]`... for type constructors and `A`, `B`, ... for subsequent references to other generics not of a higher kind. In this case we us a `List` because I can't abstract over `MonadFilter` or `Foldable` or any of the common typeclasses to write polymorphic code since Kotlin does not support Higher Kinds. The idea is that once you raise the abstraction level app you loose the concept of the domain you are operating on. In this case the function implementation folds over a Promise parameterized with an Either and in the case of left continues applying a function until it finds a right. The actual purpose of such operation is defined at the call site and not on this definition. Most FP programmers will be familiar with names such as fa, a, b... but I understand this is not common practice in Kotlin since people tend to write monomorfic code tailored to a specific domain more often than polymorphic code. Having said all of this I'll be happy to merge a PR with naming more according to what people would expect in Kotlin. If you are interested in this particular topic of naming in polymorphic code this is a good article http://degoes.net/articles/insufficiently-polymorphic


Correcto.


> @RKathees Hi, i am having one simple basic kafka Producer class which is used to send  data with initializing connection every time, so I visit [your code](https://github.com/RKathees/esb-connector-kafka/blob/master/src/main/java/org/wso2/carbon/connector/KafkaConnectionPoolManager.java)

> Can you suggest me which class should I used for connection pool for my kafka producer class?Thanks

`
import java.util.Properties;
import org.apache.log4j.Logger;
import com.bisil.report.queue.QueueDBFeederService;

import kafka.javaapi.producer.Producer;
import kafka.producer.KeyedMessage;
import kafka.producer.ProducerConfig;

public class KafkaProducer1 implements ProducerService {
			private static Producer<Integer, String> producer;
			private static final String topic= "mytopic1";
			private Logger logger = Logger.getLogger(KafkaProducer1.class);
@Override
public void initialize() {
		try {
			Properties producerProps = new Properties();
			producerProps.put("metadata.broker.list", "192.168.21.182:9092");
			producerProps.put("serializer.class", "kafka.serializer.StringEncoder");
			producerProps.put("request.required.acks", "1");
			ProducerConfig producerConfig = new ProducerConfig(producerProps);
			producer = new Producer<Integer, String>(producerConfig);
		} catch (Exception e) {
			logger.error("Exception while sending data to server "+e,e);

		}
		logger.info("Test Message");
	}
public void publishMessage(String jsonPacket) {
			KeyedMessage<Integer, String> keyedMsg = new KeyedMessage<Integer, String >(topic, jsonPacket);
			producer.send(keyedMsg);
		 // This publishes message on given topic
	}
public void callMessage(String jsonPacket){
			initialize();
			// Publish message
			publishMessage(jsonPacket);
			//Close the producer
			producer.close();
	}
}
`


@shibukawa sorry I introduced error in merging, cutting out your code. I hope I got it right now, could you please check sphinx/builders/gettext.py is ok on master ?


Utiliza un nombre más descriptivo en la clase. Sugiero "HiloMovimientoBola"


Solución correcta.


unnecessary space after `==`


@jfbu It seems OK


You have setup you tuning test wrong.
Both new and base tag have to be the the tuning branch.


AsyncTask version can **Cancel** the downloading task.

![image](https://cloud.githubusercontent.com/assets/12508109/23546264/bccd9cde-0039-11e7-9e9e-27c11c38538d.png)


code cần format nhé :))
```java
private static final String HOST_NAME = "localhost";
```


static fields thì cần đặt tên theo kiểu chữ hoa và cách nhau bằng _
```java
	public static final String DB_NAME = "MyWorld";
```


Hebrew will not be added to this version?


Bluemix Toolchain: This commit has been deployed to Stagging5


dumny


Hi :)

what I have done in the past was to add "14" to the MrMC returned version number, so MrMC v1 is seen as kodi 15, v2 as kodi 16 and so on. My question is: isn't MrMC major version numbering following kodi major version numbering steps? I mean both MrMC version 2 and version 3 are based on Kodi v16?


But this option is not taken into account if you're using a bar or pie chart (it's overriden in the line coming immediately after it).


男孩


[Your benchmark job](https://github.com/JuliaLang/julia/commit/b08227b24619737d0e5966e3863268267ecb9ad5#commitcomment-21134282) has completed - possible performance regressions were detected. A full report can be found [here](https://github.com/JuliaCI/BaseBenchmarkReports/blob/a6ee444f941d696448409d0c8d77bdd0b39cd3f5/b08227b_vs_3c9d753/report.md). cc @jrevels


我不知道你想干什么


Thanks @shibukawa I am very sorry about my mistake. In resolving conflicts I thought master branch was more recent than stable. I also did a mistake with @tk0miya 811df6b2e3eaef0b4f92b4fc37d041747b566ac5 update to sphinx/ext/intersphinx.sty.

I will now try to clean up my mess. Sincere apologies.


Thank you friend for reply
Hey can you please provide me your email address so that I can share my research with you to get your guidance.
Thanks


Could you try this?

http://forum.arduino.cc/index.php?topic=385377.0

`Wire.requestFrom(FPGA_ADDRESS, 1, FPGA_REG, 1, true);`


SQL injection attacks are possible. We should always use the prepared statements to inject the param values. Need to fix this in whole file


yes, thanks, a mistake here


jimenojmm@gmail.com


Correcto. Has implementado seguridad a nivel de concurrencia en el objeto pasivo.


The 'lithium' example is just right for a simple example.

But John's example of combination with our root-finding is really useful and very widely applicable, so it would be really good to have an example like that as well.  This is just what lots of people, many C++ novices, will want to achieve. I see you are working on doing it - and efficiently too.


Maybe we want Hash=4?


I've filed #2486


change input pattern to allow a deicmal on mobile. Maybe pattern="[0-9.]*" will do this,


Yes, merge


@tim-field how about this for simplification?

surely some of it can be improved (eg actionSelector to use App's actionsSelector) but no need for view sagas, constants, many of the selectors...


What I did was create a second class that handles the widget (GLWidget), and use your class as an element that is drawn in that widget.


could you please tell me where does this constant come from exactly?


I promoted the GLWidget from QOpenGLWidget with the help of QDesigner


after here is not a single element, but a list of them. So the body would be accesible via after[0] . I suggest you do:
```js
let after = document.querySelector("body");
```


Is there a reason that those routes are not restricted to administrator only? I think they should also have `admin.permission:allow,administrator` middleware.


Release version 3.0.0-beta.2

Demo: quicktests | fiddle


That would be me... 😞


@marcparadise If you're putting this in the Gemspec, then it can't require a bundle install to work. Otherwise anything that depends on oc-chef-pedant is borked.


ups! this shouldnt be here!


It seems like cameraNum passed by Squeak use 1-based convention, while apple uses 0-based.
Maybe use

     [devices objectAtIndex: cameraNum-1]

If we convert image side to 0-base, then we must check

    if (cameraNum >= [devices count])


It makes a clone of opts, so that the original input object isn't modified.


Beyond1Airloop (mjwitte) - x86_64-MacOS-10.9-clang: OK (2470 of 2471 tests passed, 596 test warnings)

 * 596 tests had: AUD diffs.
 * 523 tests had: BND diffs.
 * 10 tests had: EIO diffs.
 * 2 tests had: ESO small diffs.
 * 2 tests had: Table small diffs.
 * 2 tests had: RDD diffs.

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


I think the problem is solved. I'd appreciate a check to be sure. The problem was that the MathJax support files were not being uploaded (I had deleted them since I thought they were unnecessary given how I (mis?)-understood the NDS/presentations readme.


6010_ConstantCOPChiller (Nigusse) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (1279 of 1279 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-36.98%25-green.png)


Date Range Input (#70)

Preview: docs
Coverage: core | datetime


else deviceID is unset???
Does that mean that we must provide a deviceNum >= deviceCount to make it work?


<details>

<summary>Submitting the task to TaskCluster failed. Details</summary>

```js

Schema Validation Failed!
Rejecting Schema: http://schemas.taskcluster.net/queue/v1/create-task-request.json#
Errors:
  * data.metadata.owner should match format "email"
----
method:     createTask
errorCode:  InputValidationError
statusCode: 400
time:       2017-03-04T00:20:56.155Z
```

</details>


Tohle je pořád na úrovni jen lepšího switch/case, který najdeme např. v Ruby či Groovy. Pattern matching je mocnější (mj.) v tom, že lze matchovat složitější struktury a „vytahovat“ z nich hodnoty.

Lepší ukázka z referenční [dokumentace](https://doc.rust-lang.org/book/patterns.html):

```rust
struct Point {
    x: i32,
    y: i32,
}

def main() {
    let origin = Point { x: 0, y: 0 };

    match origin {
        Point { x: x1, y: y1 } => println!("({},{})", x1, y1),
    }
}
```

Pro obohacení bych do ní ještě přidal _binding_, _range_ a _guard_:

```rust
struct Point {
    x: i32,
    y: i32,
}

fn main() {
    let origin = Point { x: 0, y: 0 };
    match origin {
        Point { x: x1 @ 0...5, y: y1 @ 0...5 } => {
            println!("({},{})", x1, y1);
        }
        Point { x: x1, y: y1 } if x1 < 0 || y1 < 0 => {
            println!("Point is in negative space");
        }
        _ => println!("Point is out of range")
    }
}
```


Oops... sorry bout that...


Oui Jeune Pawadane, les ficelles du debuggage Jedi, t'apprendre je le
promet...

Le 3 mars 2017 à 13:19, Charlotte Weil <notifications@github.com> a écrit :

> C'est beau ce que tu dis ! Tu m'apprendras à mettre des breaks points
> conditionnels ?
>
> Good Luck Pour L'interview ! Frozen Yogurt in a few hours yeehee !
>
> Charlotte Weil
> Visiting student researcher at Stanford University
> Master student at École Polytechnique de Lausanne
> *_________________________________________*
> « Be the change you wish to see in the world » [Mahatma Gandhi]
>
> Le 3 mars 2017 à 13:10, Chabbey François <notifications@github.com> a
> écrit
> :
>
> > La reponse me parait simple : en me mettant a l'ecoute du cosmos ...
> >
> > En fait, j'ai mis en break point dans pie, et j'ai suivi l'execution pas
> a
> > pas de la bestiole ( en fait j'ai mis un breakpoint conditionnel pour que
> > ca s'arrete QUE quand tu cliques sur la table avec le slider enclenche...
> > ). Apres j'ai vu que ca petait dans une certaine methode, j'ai regarde la
> > methode, et apres j'ai remis un breakpoint la, et j'ai vu que c'etait la
> > boucle for, j'ai mis un breakpoint dessus j'ai vu que les valeurs de
> depart
> > et de fin etait egales... et la verite m'aveugla alors de sa clarte
> > aveuglante
> >
> > 2017-03-03 9:33 GMT-08:00 Charlotte Weil <notifications@github.com>:
> >
> > > mmmmmh
> > > Donc en gros ça faisait une boucle infinie si jamais newExt c'était une
> > > valeur unique genre [2,2]..?
> > >
> > > Comment t'as trouvé ça quoi ? (Parce que, j'ai cherché !)
> > >
> > > —
> > > You are receiving this because you are subscribed to this thread.
> > > Reply to this email directly, view it on GitHub
> > > <https://github.com/charlottegiseleweil/webviz_natcap/commit/
> > c60c0e6ac63e5ecf2dd81addd41f74e1df9193bd#commitcomment-21142299>,
> > > or mute the thread
> > > <https://github.com/notifications/unsubscribe-
> > auth/AGdKpGV7hAYWhPQviWiw9bC_MYBtxY7Tks5riE8HgaJpZM4MSiTO>
> > > .
> > >
> >
> > —
> > You are receiving this because you commented.
> > Reply to this email directly, view it on GitHub
> > <https://github.com/charlottegiseleweil/webviz_natcap/commit/
> c60c0e6ac63e5ecf2dd81addd41f74e1df9193bd#commitcomment-21145727>,
> > or mute the thread
> > <https://github.com/notifications/unsubscribe-auth/
> ARh7KVN2KXCBONNZotlRZqJ6uhxPT60nks5riIGwgaJpZM4MSiTO>
> > .
> >
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/charlottegiseleweil/webviz_natcap/commit/c60c0e6ac63e5ecf2dd81addd41f74e1df9193bd#commitcomment-21145850>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AGdKpJUdnsSuM6RVVo1R9RsXKX_QzIQKks5riIPngaJpZM4MSiTO>
> .
>


Ještě tip, možná by bylo užitečné někam přidat odkaz na „pískoviště“ https://play.rust-lang.org/, kde si lidé mohou Rust snadno vyzkoušet bez nutnosti instalace rustc.


why do I get this error?
from keras.layers import containers
ImportError: cannot import name containers


w.l.o.g it is :P


bad


@a-frobot docs-v0.5.0


nice


ok


Should be ((avail > XML_MAX_TEXT_LENGTH) && ((ctxt->options & XML_PARSE_HUGE) == 0)), like everywhere else.
As it is, it leads to O(N^2) for CDATA sections; a file with a single 300MB CDATA block was parsed 42 hours (profiling the code showed that we spent all the time in xmlParseTryOrFinish; additional logging showed that this condition triggered the calls once we're past 10M bytes).
After the fix the same file takes 7 sec. to parse.


Tim and Bob brought it up but I think the plugin needs to go with 1-based
convention.  Sorry for not getting around fixing it, but that is the way to
go...

On Fri, Mar 3, 2017 at 4:19 PM, Nicolas Cellier <notifications@github.com>
wrote:

> else deviceID is unset???
> Does that mean that we must provide a deviceNum >= deviceCount to make it
> work?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/d92b2be5b1c374741015edb00faeedeecf5029a5#commitcomment-21148175>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAMCgcM2xwM2HMdTYrb3Ji4spnAHBUiYks5riK4QgaJpZM4MS44H>
> .
>

--
-- Yoshiki


Doh... Thanks for notifying cafd49d


@ajafff can you release a patch with this change?


9530用了，显卡没法驱动啊


Why was this change made? As far as I can tell, `dist/bin` was correct.


That was actually new to me too. Details here: http://webaim.org/techniques/tables/data <http://webaim.org/techniques/tables/data> (relevant bits below)

18F is using it in their code examples as well, so I’m assuming it’s real and not made up.

The scope attribute
The scope attribute identifies whether a table header is a column header or a row header. Here is the markup for the table, using the scope attribute:

Shelly's Daughters

Name
Age
Birthday

Jackie
5
April 5

Beth
8
January 14

The scope attribute tells the browser and screen reader that everything within a column that is associated to the header with scope="col" in that column, and that a cell with scope="row" is a header for all cells in that row.
All  elements should generally always have a scope attribute. While screen readers may correctly guess whether a header is a column header or a row header based on the table layout, assigning a scope makes this unambiguous.
________________
Michael Stanaland
202-352-1943

> On Mar 3, 2017, at 6:06 PM, Nat Burgwyn <notifications@github.com> wrote:
>
> Scope=col?
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub <https://github.com/n8mellis/uswds-react/commit/21c99a41b54177023ef5b7b67788e343621cb60e#commitcomment-21147561>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADcfF1sPv1mB7Uhtbv1_Xt1RzvHCERoyks5riJz4gaJpZM4MS2Vf>.
>


helloworld


Rename this to ProfileActivity. And not ProfileActivityActivity. This is too redundant


These routes are be enabled in `app/Admin/routes.php`, so you can add any permission you want to protect them.


These routes be enabled in `app/Admin/routes.php`, so you can add any permission you want to protect them.


Hey, @Robert-Frampton. Return an object makes it more flexible. But I couldn't figure out a scenario where we can order the plugin execution. Would it be by an index?

I can imagine dependencies between plugins when we need to guarantee that an `autoprefixer` will run after the `sass` plugin. But once a plugin is independent, we will need to develop a single plugin to cover those two tasks like this:
```javascript
.pipe(sass(...)).pipe(autoprefixer(...))
```

One option to be returned by the plugin could be the `life cycle` that it will run. We might want to create a plugin to run only into the `deploy` task. Like:

```javascript
return {
    name: 'sass',
    flow: 'deploy'
}
```

What do you think?


,xm


This if for IK-57. Not IK-58.


Backed out - Yandex wanted to push an unacceptable agreement contract that was different from what was agreed in e-mail for the partnership.
On top, the PR agent of Yandex called me rude for pointing out some serious legal issues and not wanting to sign, so they've burnt their bridges in that respect.


This takes about 2 seconds to run through, which for a max input of 10,000 is a really long time. If another problem comes up like this with a higher max value a new way to find the divisors will have to be found.


Remove the comma after OCF_LDAP_PEOPLE.


Same misspelling here


test editing readme.md


Excellent use of the grid system


use macroS. makes code portable


surely there must be a better way to access the global entities here...


> Ofc, this is not related.

So this doesn't fix #93?


verify all of these are needed


you should `return False` rather than `sys.exit`. right now everything is c-style error handling.


Assume this should be "oic.r.csr"?


what about regions that in this chunk, but don't contain the specific location?


Looking back at this, it's a pretty neat solution! @sumirolabs


Fall through?


When using max media queries, the other might affect the result. As a recommendation, go from greatest to lowest when doing desktop development first. The opposite when using min.


Yeah.


This rule is exactly the same as in 134 to 139. Since this is a lower unit, having it declared here might not be needed.


What I get for trying to briefly skimming logs on my phone instead of actually paying attention


Fixed commit: https://github.com/kevinmkane/security-models/commit/8dae0e7956f22ecf4833cecd0e923c38e010c83c


@Daelkyr13 get on discord


This stiring bpy.ops.mesh.delete_loose()
Make something like this:
http://prnt.sc/efrin6


w


Yep! That's the ticket, I hope :-)


Just noticed lol


手误，多谢指出，已修正：https://github.com/youngwind/fake-webpack/commit/faf8cc34e20bce0163e2a50108cfd67215d67d1b


this is a raw image. it is unknown what it contains. you can try flashing it to your block device using dd.
the command is dd if=mmcblk0p25.img of=/dev/block/mmcblk0p25


I think you probably want to remove this.


This is a comment


```.stream().filter(r -> r.getCuboid().contains(loc.getX(), loc.getY(), loc.getZ()).sorted(Comparator.comparingInt(Region::getPriority)).collect(toList())```


@jcumming check here: https://github.com/NixOS/nixpkgs/issues/23431


Did this ever get committed to the VEDA release https://github.com/veda-consulting/uk.co.vedaconsulting.payment.gocardlessdd/releases

I am guessing not since the date here is July 12, 2016, and the last Veda release was June 21, 2016

Any reason this isn't going through as a PR to the main release?


Yeah


#5922-OutputVariable-Facility-Total-HVAC-Electric-Demand-Power-does-not-show-in-the-rdd (rraustad) - Win64-Windows-7-VisualStudio-14: OK (2478 of 2478 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)


Also wondering whether this will get in to the main release


Some VPS already come with support enabled... Oh I see what you mean.
Well yeah. We could delete that.


I've recently determined that these are wrong in all the sec RAMLs.

This one should be "/oic/sec/csr:"


Great use of media queries.


6010_ConstantCOPChiller (Nigusse) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1880 of 1880 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.47%25-green.png)


Bluemix Toolchain: This commit has been deployed to TestEnv


6010_ConstantCOPChiller (Nigusse) - 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)


Prints slow down the calculations a lot. Have you tried without them?


@repetier : thanks, this fixes #641 but there is a spelling mistake : `DELA` should be `DELTA`


Ты лучший, я информат ставил для этого! Удолять теперь...


I no longer support this code.


So is the idea here that there's just one CSR in-process at a time? I was assuming one would UPDATE/POST a CSR. Guess I'd better go look at the CR... ;^J


Can these be used with stable?


Prepare Release v1.11.0 (#774)

Preview: docs
Coverage: core | datetime


fd


The `hashed_item.key == key` is redundant. In the previous condition you check `hashed_item.key  != key`, meaning the only way it would get passed that condition is if they were equal.


has already happened a while ago! :)


dffdf


Right, I agree, this can get confusing but the change makes sense. pid() is what you see with "ps", and tid() is the kernel's unique per-task ID (which it calls "pid").


Overall, I would have liked to see more combinations in the use of the `col` class. eg: `col-xs-6 col-md-3 col-lg-1`.


There is actually a method called `sum` on strings that does this for you;  the method body here could just be `key.sum`


You can get the same effect more concisely by just giving the fence a description. There's already a rule that will say the description.


Scandalous!
;-)


Also, you have to keep track of the strings you add so that once you get a collision you can add the appropriate ones to the file. Here's an example:
You are keeping track of each random string you add in a list called catStrings[] and dogStrings[], then you find a collision between chash10[3981] and dhash[9897] so you add all strings in catStrings from 0 - 3981 to cat.jpg and then you add all strings from 0 - 9897 to dog.jpg.


@chrismccord @josevalim WDYT about moving tests to `test/myapp` as was proposed way back by @Gazler in https://github.com/phoenixframework/phoenix/pull/1871#issuecomment-240030736? This would make editor tooling trivial to switch between prod & test.

Just to reiterate: `lib/my_app/web/controllers/page_controller.ex` would match `test/my_app/web/controllers/page_controller_test.exs` etc.

and this context test would be as `test/my_app/blog/blog_test.exs`

if you want a side-by-side comparison vs what we have on master & what I'm proposing it's here:
- [master](https://github.com/wojtekmach/phoenix_example/tree/fa7d2cb42c15ed9f69d8aa8ac1584d351c92658d/dummy/test)
- [new](https://github.com/wojtekmach/phoenix_example/tree/f12af4650efa6e517ea37e1e18fa1f765c5df5c3/dummy/test)


这个修改比较成功！！！


**Whoops!**

There were *107 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#L28`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L28) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L47`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L47) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L62`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L62) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L81`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L81) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L104`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L104) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L141`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L141) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L148`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L148) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L171`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L171) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L217`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L217) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L238`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L238) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L280`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L280) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L284`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L284) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L301`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L301) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L328`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L328) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L357`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L357) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L380`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/common-notification-patterns.md#L380) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L33`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L33) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L72`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L72) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L82`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/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/75e021405480714085ed61019b1e9ec4dadaa630/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#L90`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L90) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L95`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L95) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L97`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L97) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L105`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L105) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L107`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L107) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L115`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L115) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L125`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L125) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L129`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L129) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L148`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L148) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L158`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L158) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L162`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L162) - 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/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L177) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L187`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L187) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L191`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L191) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L211`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L211) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L252`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L252) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L266`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L266) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L303`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L303) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L327`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L327) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L331`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L331) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L343`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L343) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L361`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L361) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L377`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L377) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L420`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/display-a-notification.md#L420) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/faq.md#L53`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/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/75e021405480714085ed61019b1e9ec4dadaa630/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`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/handling-messages.md) - Unable to read file, was it deleted?
[`src/content/en/fundamentals/engage-and-retain/push-notifications/how-push-works.md#L82`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/how-push-works.md#L82) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/non-standards-browsers.md#L73`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/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/75e021405480714085ed61019b1e9ec4dadaa630/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#L91`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/non-standards-browsers.md#L91) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/non-standards-browsers.md#L103`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/non-standards-browsers.md#L103) - 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/75e021405480714085ed61019b1e9ec4dadaa630/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/75e021405480714085ed61019b1e9ec4dadaa630/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/75e021405480714085ed61019b1e9ec4dadaa630/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/non-standards-browsers.md#L124`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/non-standards-browsers.md#L124) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/non-standards-browsers.md#L158`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/non-standards-browsers.md#L158) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/non-standards-browsers.md#L192`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/non-standards-browsers.md#L192) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L41`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L41) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L68`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L68) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L116`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L116) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L144`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L144) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L155`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L155) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L166`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L166) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L170`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L170) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L181`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L181) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L186`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L186) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L197`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L197) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L217`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L217) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L240`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L240) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L260`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/notification-behaviour.md#L260) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L49`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L49) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L58`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L58) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L63`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L63) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L97`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L97) - Line must be at most 100 characters
[`src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L102`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/permission-ux.md#L102) - 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/75e021405480714085ed61019b1e9ec4dadaa630/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/permissions-subscriptions.md`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/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/push-events.md#L24`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/push-events.md#L24) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/push-events.md#L46`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/push-events.md#L46) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/push-events.md#L79`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/push-events.md#L79) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/push-events.md#L99`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/push-events.md#L99) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/push-events.md#L159`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/push-events.md#L159) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L56`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L56) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L83`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L83) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L90`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L90) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L115`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L115) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L138`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L138) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L179`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L179) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L194`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L194) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L202`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L202) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L232`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L232) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L239`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L239) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L258`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L258) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L293`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages-with-web-push-libraries.md#L293) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/sending-messages.md`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/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#L26`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/subscribing-a-user.md#L26) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/subscribing-a-user.md#L55`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/subscribing-a-user.md#L55) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/subscribing-a-user.md#L96`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/subscribing-a-user.md#L96) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/subscribing-a-user.md#L142`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/subscribing-a-user.md#L142) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/subscribing-a-user.md#L274`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/subscribing-a-user.md#L274) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/subscribing-a-user.md#L298`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/subscribing-a-user.md#L298) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/subscribing-a-user.md#L321`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/subscribing-a-user.md#L321) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/subscribing-a-user.md#L342`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/subscribing-a-user.md#L342) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/subscribing-a-user.md#L368`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/subscribing-a-user.md#L368) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/web-push-protocol.md#L86`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/web-push-protocol.md#L86) - Code blocks should be indented
[`src/content/en/fundamentals/engage-and-retain/push-notifications/web-push-protocol.md#L98`](https://github.com/Google/WebFundamentals/blame/75e021405480714085ed61019b1e9ec4dadaa630/src/content/en/fundamentals/engage-and-retain/push-notifications/web-push-protocol.md#L98) - Code blocks should be indented


Change to:
 ClearTimer(T1);
while(abs(getMotorEncoder(wheelBL)) < 90 || timer1[T1] < 400);


Np anytime.


fixed issue #18


Default Password: wso


You can also make the hands a _part_ of the person. The main difference is that a part, by default, would not be removable. There's also some difference in how it's reported in response to the "inventory" command. So it depends on what you're going for.


Correção do presentation error.


I _really_ like this one. It actually makes note of the constant speed versus "it is super fast". Remind me during our next meeting to talk about examples where constant is actually slower than some others.


@mhorowitz Found an issue when trying to generate an archive. Looks like double-conversion doesn't work when building for generic ios device. You can repro in xcode by choosing 'Generic iOS Device' as the target and building.

`Target architecture was not detected as supported by Double-Conversion.`


I am considering implement delay by something like` _.debounce`, but not sure which method is good. 1. copy that method into moquilib, 2. introduce dependece on underscore.


Here is the first draft of html. What do you think @Goredbirds?