---
title: " Siniestros de tránsito fatales en Uruguay, 2013-2017 "
author: "Martínez Matías, Zang Bruno"
date: "21 de junio de 2018"
output: html_document
---

```{r setup, include=FALSE}
knitr::opts_chunk$set(echo = FALSE, fig.pos = 'hbpt', out.extra = '', message = FALSE, warning = FALSE)
```

## Introducción

El presente estudio surge de la curiosidad por conocer el comportamiento de los siniestros de tránsitos en Uruguay y posee como objetivo madre una profunda aplicación de los conocimientos adquiridos en la asignatura "Nuevas técnicas para el análisis de datos", marcando énfasis en un correcto análisis exploratorio y la generación de adecuadas visualizaciones de los datos.
Se analizara tanto los datos del fallecido como lo del suceso.

### Antecedentes:

En su programa de Sistema de Información Nacional de Tránsito (SINATRÁN), donde se extrajo los datos, la Unidad Nacional de Seguridad Vial (UNASEV), genera un informe anual sobre la Siniestralidad Vial en Uruguay para el periodo dado desde 2009 a la actualidad.
Dicho informes se pueden encontrar a través del siguiente enlace:http://unasev.gub.uy/inicio/sinatran/informes_siniestralidad_vial_uruguay/

## Datos obtenidos

Los datos fueron obtenidos de la Unidad Nacional de Seguridad Víal (UNASEV), correspondientes al período comprendido entre 2013 y 2017. Originalmennte los datos correspondían al año 2017, sin embargo se identificó apropiada la utilización de una serie de tiempo por lo cual se mecharon bases desde el año 2013, esto provocó ciertos inconvenientes en cuanto a nombres de variables debido a la utilizacion de tildes o el aumento de variables para ciertos años pero finalmente fueron solucionados y concluimos en una base de datos apta y abarcativa.

Mediante su catálogo de datos abiertos se extraen las bases utilizadas, desde el siguiente url: http://unasev.gub.uy/inicio/sinatran/datos_abiertos/

### Población:

Corresponde a los 2527 fallecidos en accidentes de tránsito dentro del territorio uruguayo para el período antes señalado.

### Descripción de las variables:

Se poseen 15 variables identificadas de la siguiente manera:

- **a:** Año.
- **fecha:** Dia y Mes.
- **hora:** Hora.
- **dep:** Departamento.
- **jur:** Jurisdicción.
- **tipo.sin:** Tipo de Siniestro.
- **vehi:** Vehiculo.
- **rol:** Rol que cumplía.
- **edad:** Edad al fallecer.
- **Sexo:** Sexo de la persona.
- **f.dias:** Dia de supervivencia.
- **otro.vehi:** Otro vehiculo involucrado.
- **dir:** Lugar del accidente.
- **x:** Latitud.
- **y:** Longitud.

## Modelos y herramientas

Es importarte recordar los objetivos del estudio, uno de ellos guía a la implementación de apropiadas visualizaciones. Para esto se utilizará el software estadístico R, con la puntual aplicación de paquete "tidyverse", que proporciona un conjunto de librerías óptimas para el análisis exploratorio de datos.
Con el fin de crear visualizaciónes oportunas se gestará su formación con la librería "ggplot2", perteneciente a tidyverse, la cual al trabajar mediante acumulación de capas (layers) posee una mayor flexibilidad y permite generar gráficos que representen correctamente los datos, sin generar interpretaciones confusas. Toma como referencia una metodología de visualización de datos llamada the Grammar of Graphics (Wilkinson, 2005), que consiste en especificar de manera independiente las componentes del gráfico como si fuesen bloques y luego combinarlas. Además, con ánimos de compartir una visualizacion interactiva en la cual el usuario pueda manipular los gráficos de acuerdo a sus interés, se proveerá del paquete "shiny" que además de tales visualizaciones permite una rápida divulgacion de los estudios y un alto nivel de personalización.

## Preguntas a responder

1 - ¿Cuál es la distribución relativa por sexo y qué comportamiento posee la edad del fallecido en el período dado?

2 - ¿Existe relación entre el rol del fallecido tanto con la edad, como con el vehículo del difunto?

3 -  Para observaciones de vehículo igual a peatón:
¿cuál es la tasa de fallecidos para cada sexo según el departamento en donde ocurrió el accidente? y además,
¿qué vehículo involucrado en fallecimientos de los mismos posee mayor frecuencia acumulada?

4 - ¿Hay relación entre el vehículo del fallecido y otro posible vehículo involucrado en el accidente?

5 - ¿Qué comportamiento posee la jurisdicción por si misma, y según el tipo de siniestro ocurrido?

6 - ¿Cuál es la distribución de los días de supervivencia luego del accidente y qué proporción ocupa cada tipo de siniestro en caso de muerte súbita?

7 - ¿Cuál es la tasa de fallecidos por departamento?

8 - ¿Qué fechas y horarios poseen mayor frecuencia absoluta de difuntos?

## Hipótesis

1 - Se considera que el comportamiento de la edad estará dado por una fuerte densidad para edades cercanas a los 25, ya que se acompaña de poca experiencia al volante y pocas responsabilidades en comparación a mayores edades. Por ende, con respecto a la variable sexo, se preevé una mayor proporción de difuntos para las personas de sexo masculino.

2 -  En relación con la edad, y retomando el punto anterior asumimos una mayor proporción de fallecidos peatones a altas edades, al contrario que en conductores. Los pasajeros poseeran una densidad equilibrada para todas las edades.
    Por cuestiones de seguridad es de esperar frecuencias absolutas mayores para vehículos más débiles en su ensamblaje como motos, bicicletas, autos pequeños, etc. Dicho esto, se considera mayor mortalidad para conductores de los mismos y para los consiguentes vehículos la mortalidad estará dada principalmente en pasajeros, ya que su estructura protege mayormente al conductor.

3 - Las tasas de atropellos a peatones se comportan de manera similar tanto para hombres como  mujeres en la mayoría del territorio uruguayo; salvo para Montevideo y Canelones, donde la población es tal que provoca una disminución en su tasa de peatones fallecidos.

Considerando la concentración de autos en el país y el tamaño promedio del mismo, un impacto contra el mismo generaría mayor daño en el transehúnte en comparación con otro vehículo de igual presencia en el tránsito. Por lo tanto se espera una alta probabilidad de fallecer en  condición de peatón siendo impactado por dicho vehículo.

4 - Colisiones entre un vehiculo de gran magnitud y otro de menor provocaría que el de menor quede expuesto a graves consecuencias, esto genera la hipotesis de una fuerte relacion en fallecimientos en vehiculos como: motos, bicicletas, inclusive peatones, ect; al impactar con autos, camionetas, ómnibus,camiones,ect.

5 - Se prevé mayor proporción de accidentes fatales en rutas nacionales, esto en base principalmente a la práctica de altas velocidades. Tanto despistes como colisiones tendrán mayor propoción de fallecidos en rutas no departamentales, sin embargo he de excluirse atropello de peatones de dicha jurisdicción debido a su nula circulación en las mismas.

6 - Los tipos de siniestros que mayoritariamente se llevan vidas serán colisión entre vehículos e impacto con obstáculos. Esta hipótesis surge en la brusquedad identificada para dichos accidentes.
  Consiguiente a anteriores menciones, tales impactos generían una muerte instantánea o de poca supervivencia para el individuo. Si valoramos posibles traslados desde carretera o largas distancias a un centro de atención médica de calidad (los cuales en mayor grado se encuentran en la capital nacional) las probabilidades de salir con vida de dicho accidente se reducen drasticamente.

7 - Debido a la concentración en zonas metropolitanas tanto en sectores productores, educativos, turísticos, ect; se provocán altos valores de accidentes de tráficos y esto tendrá como consecuencias que, pese a su alta población, dichos departamentos indiquen las mayores tasas de fallecidos en el país.

8- En meses de vacaciones se provocarían mayores accidentes de tráfico producto de congregaciones y movimientos en general. Respecto al día y hora se considera altas frecuencias absolutas para fines de semana en horarios nocturnos.

##

```{r,echo=F,warning=FALSE,error=FALSE}

#Función que instala y carga los paquetes a utilizar
ipack <- function( pkg )
  {

  new.pkg <-  pkg[ ! (pkg %in% installed.packages()[, "Package"]) ]
      if ( length(new.pkg) )
        install.packages(
          new.pkg, dependencies = TRUE )
    sapply( pkg, require, character.only = TRUE )

    }

paquetes.a.utilizar<- c("tidyverse", "ggmosaic", "plotly",
                        "ggmap", "raster", "rgdal","knitr",
                        "scales","lubridate")

ipack(paquetes.a.utilizar)

load("base_datos___fallecidos_transito_uruguay_2013-2017.RData")

colores<-c("darkolivegreen3","turquoise4","tan2","indianred",
           "khaki3", "thistle4", "lightsteelblue","grey80")
```

## Análisis Exploratorio de Datos

```{r}

dim(datos)
str(datos)

```

### Fallecidos por año

```{r,warning=FALSE,echo=F,fig.cap="Gráfico de series de tiempo: frecuencia absoluta de fallecidos por año."}

ggplotly(
   datos %>% dplyr::count(a)  %>%
     ggplot(aes( a, n)) +
     geom_point() + geom_line()+
     theme_minimal()+
     labs(
       x = "Año",
       y = " Frecuencia relativa de fallecidos") +
     theme(plot.title = element_text(
       size =16,
       colour = "grey16"))+
     coord_cartesian(ylim=c(0,600)) )

```

Desde el año 2013 la frecuencia absoluta de fallecidos en tránsito manifestaba un claro descenso. Ésta racha se detuvo en el año 2017 donde sucedieron 24 muertes más que en el año previo. Pese a esto, tal pendiente en la cantidad de fallecidos profiere un correcto desarrollo y accionar en sectores políticos y una alta concientización en los uruguayos para dichos temas.

### Sexo

```{r,echo=F,fig.cap="Gráfico de serie de tiempo: frecuencia absoluta de fallecidos por sexo medido en años."}

ggplotly(
   datos %>% dplyr::count(a, sexo) %>%
     ggplot(
       aes(
         a,
         n,
         colour=sexo)) +
     geom_point()+
     geom_line(cex=1) +
     theme_minimal() +
     labs(
       x = "Año",
       y = "Frecuencia absoluta de fallecidos") +
     guides(colour=guide_legend(title="Sexo:")) +
     theme(
       plot.title = element_text(
         size = 14.4,
         colour = "darkslategrey")) +
     coord_cartesian(ylim = c(0,500)) +
     scale_color_manual( values=colores)  )

```

 Para el sexo masculino se puede ver un decenso significativo de fallecidos para este período trabajado. En cambio, el sexo femenino percibe una continiudad en la frecuencia absoluta que no varía significativamente en los tiempos transcurridos.

### Edad

```{r,echo=F,fig.cap="Gráfico de densidad: distribución en la edad del fallecido según año."}

datos %>% ggplot(aes(edad)) +
  geom_density(
    aes(fill=a),
    size=0.74,
    colour="grey10",
    show.legend = F) +
  labs(
    x="Edad del fallecido",
    y="Densidad") +
  theme(
    axis.title = element_text(
      size=11.5,
      colour="grey20"),
    panel.background = element_rect(
      fill="gray96"))+
   facet_wrap(~a)

```

 Se percibe una fuerte concentración en edades cercanas a los 25 años, la cual es inalterable al paso de los años para el período dado. Sin embargo, la distribución para aproximadamente de 30 a 70 años varía cosiderablemente: de poseer una meseta en el 2013, luego poseer una brusca y cosiderable pendiente decreciente en el año 2014, a retomar lentamente su meseta pero más expandida, llegando a los 70 años con proporciones superiores al 10%.

```{r,fig.cap="Diagrama de caja: edad del fallecido según sexo."}

ggplotly(
  datos %>%
    ggplot(aes( sexo,
    edad,
    fill=sexo )   ) +
    geom_boxplot(
      alpha=0.4,
      show.legend = F) +
    labs(
      x =  "Sexo",
      y = "Edad en años") +
    theme_bw()+
    theme(axis.title =
            element_text(
              size = 12.6,
              colour = "grey27")) +
    scale_fill_manual(values=colores) )

```

  Para el sexo femenino existe una amplia variación de los datos, ya que pese a corresponder a aproximadamente un 25% de los fallecidos logra poseer un rango intercuartílico mayor al masculino. Los hombres en tanto se concentran a edades menores, con una mediana 6 años menor que la femínea.

### Rol

```{r,fig.cap="Gráfico de densidad: distribución de la edad del fallecido según rol del mismo."}

datos %>% ggplot(aes(edad)) +
  geom_density(
    aes(fill = rol),
    alpha = 0.4,
    show.legend = T) +
  labs(
    x =  "Edad",
    y = "Densidad")  +
  theme_minimal() +
  guides(fill = guide_legend(title = "Rol:")) +
  theme(
    legend.position = "bottom",
    plot.title = (element_text(
      size = 16,
      hjust = 0.33,
      colour = "darkslategray")))+
  scale_fill_manual(values = colores[(c(4,1,2))])

```

 La distribución de la densidad en la edad según el rol del fallecido cambia suntuosamente dependiendo si existe la condición de peatón o no: en el caso de existir se observa una fuerte concentración a edades avanzadas, sin embargo en el caso de no serlo su concentración es mayoritariamente en adultos menores (de 20 a 30 años).
 Los conductores por su parte predominan sobre los pasajeros desde los 17 a los 72 años, fuera de este período la densidad de pasajeros crece debido a que a ciertas edades la persona no está apta para conducir o simplemente decide no hacerlo.

```{r,fig.cap="Gráfico de series de tiempo: frecuencia absoluta de fallecidos según rol para el período dado."}

ggplotly(
  datos %>% dplyr::count(rol, a) %>% group_by(a) %>%
     ggplot(
         aes(
         a,
         n,
         colour=rol)) +
     geom_line(cex=1)  +
     geom_point(cex=1.2) +
     theme_minimal()  +
     labs(
         x="Año",
         y="Frecuencia absoluta de fallecidos") +
     theme_minimal() +
    guides(colour= guide_legend(title="Rol:"))+
     coord_cartesian(y=c(0,400))+
       theme(
         axis.title = element_text(
           colour="grey30")) +
       scale_colour_manual(values =  colores[(c(4,1,2))])
     )
```

Para este período trabajado no parece variar significativamente las frecuencias absolutas de los peatones y pasajeros. La misma tiende a mantenerse en el tiempo con aproximadamente 80 casos al año en ambos, mientras que en fallecidos en rol de conductores denotan un ligero descenso hasta el año 2016.

### Peatones

```{r}
a<-ggplotly(datos %>% filter(vehi=="PEATON")  %>%
  mutate(otro.vehi=ifelse(otro.vehi!="BICICLETA" &
                      otro.vehi!="MOTO" &
                      otro.vehi!="AUTO"  &
                      otro.vehi!= " NADA","OTROS", otro.vehi) ) %>%
  count(a,otro.vehi) %>%
   ggplot(
     aes(
       a,
       n,
       colour=otro.vehi)) +
   geom_line(alpha=0.9,
     stat ="identity",
     show.legend = T,
     cex=1.1 ) +
  geom_point()+ theme_minimal() + labs(x="Año",y="Frecuencia absoluta",colour="Involucrado:")+scale_colour_manual(values=colores) +theme(axis.title = element_text(colour="grey30")))

b<-ggplotly(datos %>% filter(vehi=="PEATON")  %>%
  filter(otro.vehi!="AUTO" & otro.vehi!="MOTO" & otro.vehi!="")  %>%
  count(a,otro.vehi) %>%
   ggplot(
     aes(
       a,
       n,colour=otro.vehi)) +
   geom_line(alpha=0.9,
     stat ="identity",
     show.legend = T,
     cex=1.1 )+geom_point() + theme_minimal() + labs(x="Año",y="Frecuencia absoluta",colour="Involucrado:")+scale_colour_manual(values=colores) +theme(axis.title = element_text(colour="grey30")))

subplot(a,b)
```

```{r}
datos %>% filter(vehi=="PEATON") %>%
count(a,sexo,dep) %>%
ggplot(
aes(
a,
n,
colour=sexo)) +
geom_line(alpha=0.7,
stat ="identity",
show.legend = T,
cex=1.1 ) +
geom_point()+ theme_minimal()+facet_wrap(~dep)
```

### Vehículo

```{r,echo=F,fig.cap="Gráfico de series de tiempo: frecuencia absoluta de difuntos por vehículo para cada año."}

ggplotly(
datos %>% dplyr::count(vehi,a) %>%
  mutate(vehi=ifelse(n<=50,"OTROS",vehi)) %>%
  group_by(vehi,a) %>% summarise(n=sum(n))%>%
   ggplot(
     aes(
       a,
       n,
       colour=vehi)) +
   geom_line(
     stat ="identity",
     show.legend = T,
     cex=1.1 ) +
  geom_point()+
   labs(
     x = "Año",
     y = "Frecuencia absoluta de fallecidos") +
   theme_minimal()+ guides(colour=guide_legend(title="Vehículo:"))+
   theme(axis.title = element_text(
       colour = "grey30"))+
   scale_colour_manual(
     values = colores) +
  coord_cartesian(ylim=c(0,310)))

```

Existe un claro decenso de las motos como vehículo del fallecido y se puede visualizar una clara continuidad en la frecuencia absoluta para los auto, peaton y otros; cabe resaltar que  autos y motos precentaban un decenso a exepcion del año 2017 donde ocurrio un aumento de fallecidos.

```{r,fig.cap=" Gráfico de densidad: distribución de la edad de fallecidos en auto o moto."}

datos %>% filter(vehi== "AUTO" | vehi=="MOTO")%>%
  ggplot(aes(edad)) +
   geom_density(
     aes(fill = vehi),
     alpha = 0.5,
     show.legend = T) +
   labs(
     x =  "Edad",
     y = "Densidad")  +
   theme_minimal() +
   guides(fill = guide_legend(title = "Vehículo:")) +
   theme(
     legend.position = "bottom",
     axis.title  = (element_text(
       size = 12,
       colour = "darkslategray"))) +
  scale_fill_manual (values=colores[c(3,2)])

```

Se denota que próximos a adultos menores exite un notable crecimiento de fallecidos para las motos, alcanzando su tope a la edad cercana de 25 años para luego presentar un paulatino decenso.
En tanto autos representan una distribución aproximadamente constante desde los 25 a los 70 años. Para edades cercanas a 50 años los fallecidos en dicho vehículo comienzan a tener mayores proporciones en contraste con motos.

### Relación vehículo

```{r,echo=F,warning=FALSE,fig.cap="Gráfico de mosaico: proporción de fallecidos en cada rol según vehículo."}

ggplotly(
 datos  %>%  dplyr::count(vehi, rol) %>% filter(vehi!="PEATON")  %>%
    group_by( vehi= ifelse (
     (vehi!="BICICLETA" &
      vehi!="MOTO" &
      vehi!="AUTO" &
      vehi!="BICICLETA" &
      vehi!="CAMIONETA"),"OTROS", vehi ),rol)  %>%
    summarise(n=sum(n))  %>%
    ggplot()  +
    geom_mosaic(aes(
      weight = n,
      x = product(  reorder(abbreviate(vehi, 4),-n)  ),
      fill = abbreviate( rol, 1) ),
      alpha=0.64)  +
    labs(
      x = "Vehículo del fallecido",
      y = "Proporción de fallecidos") +
      guides(fill = guide_legend(title = "Rol")) +
      theme_minimal() +
      theme(
      axis.title =
        element_text(
          size = 12,colour="grey30")) +
      scale_fill_manual(  values = colores[c(2,3,1)]))

```
Se filtraron los datos de manera tal que se removieron las observaciones correspondientes con vehiculos igual a "PEATON", considerando que las mismas poseen como rol el de peaton y esto no aportaba mayor información al gráfico.
Además con la finalidad de una mejor visualización designamos una nueva categoría llamada "OTROS" en los cuales colocamos los niveles de vehículos con pocas obvservaciones.

Es de destacar que quienes sufren la mayor proporción de muertes por accidentes de tránsito son los conductores, principalmente quienes conducen autos y motos, siendo estos últimos los poseedores de la mayor probabilidad de fallecer siendo conductores.

```{r,fig.cap="Gráfico de mosaico: proporción de otro posible vehículo involucrado según el vehículo del fallecido."}

ggplotly(
  datos %>% dplyr::count(vehi, otro.vehi)  %>% filter(vehi!="PEATON")%>%
   mutate(otro.vehi = ifelse( otro.vehi == ""," NADA",otro.vehi),
          vehi = ifelse(vehi!="AUTO" &
          vehi!="MOTO" &
          vehi!="PEATON" &
          vehi!="BICICLETA"  &
          vehi!="CAMIONETA","OTROS",vehi),
          otro.vehi = ifelse(n<30,"OTROS",otro.vehi)) %>%
    group_by(vehi,otro.vehi)%>%
    summarise(n=sum(n)) %>% arrange(desc(n)) %>%
    ggplot() +
    geom_mosaic(aes(
      weight = n,
      x = product(abbreviate(vehi,5)),
      fill = otro.vehi)) +
    labs(
      x = "Vehículo del fallecido",
      y = "Proporción de otro vehículo") +
    guides(  fill = guide_legend( title = "Otro vehículo")) +
    scale_fill_manual(
      values = c("darkseagreen4",colores[3:8])) +
    theme(
      panel.background = element_rect(
        fill="white"),
      axis.title  = element_text(
        colour = "gray37")) )

```

Únicamente incluye las relaciones con frecuencia absoluta mayores o iguales a 30 fallecidos.

La mayor proporción de los accidentes desde el punto de vista del fallecido no involucran otro vehículo.
Es de apreciar que la distribución varía considerablemente dependiendo del vehículo en cuestión.

### Jurisdicción

```{r,echo=F, fig.cap="Gráfica de serie de tiempo: frecuencia absoluta de fallecidos por jurisdicción."}

ggplotly(
datos %>% dplyr::count(jur, a) %>%group_by(a) %>% mutate(prop = n / sum(n))  %>%
  ggplot(
    aes(
      a,
      n,
      colour=jur)) +
  geom_point() +
  geom_line(cex=1.1) +
  labs(
    x = "Jurisdicción",
    y = "Frecuencia absoluta") +
  guides(colour = guide_legend(title = "Jurisdicción:"))+
  scale_colour_manual( values = colores) +
  theme(
    panel.background = element_rect(fill="white"),
    axis.title  = element_text(
      colour = "gray29"),
    legend.position = "bottom") +
  coord_cartesian(y=c(0,400))
)

```

Existe una disminución de la proporción de fallecimientos en jurisdicciones nacionales hasta el año 2015 y luego se comporta con una pendiete creciente hasta el final del período dado, donde supera a los fallecidos en departamentales en el año 2017.

```{r,fig.cap="Gráfico de mosaico: proporción en la existencia o no de otro vehículo involucrado según la jurisdicción en la que ocurrió el accidente."}

datos %>% dplyr::count(involucrado, jur) %>%
  ggplot() +
  geom_mosaic(aes(
    weight = n,
    x = product(jur),
    fill = involucrado),
    alpha=0.5) +
  labs(
    x = "Jurisdicción",
    y = "Proporción involucrado") +
  theme(
    panel.background = element_rect(
      fill="white"),
    plot.title = element_text(
      size = 16,
      face = "italic",
      colour = "grey20",
      vjust = -2),
    axis.title = element_text(
      size=12,
      colour="grey20")) +
  scale_fill_manual(
    values = colores) +
  guides(
    fill= guide_legend("Involucrado"))

```

Si bien para ambas jurisdicciones existe una alta proporción de accidentes fatales con otro vehículo involucrado (aproximadamente un 60%), sobresale en departamental acercándose a un 75% de los accidentes fatales.

```{r,fig.cap="Gráfico de mosaicos: jurisdicción del accidente de tránsito según tipo de siniestro."}

datos %>% dplyr::count(tipo.sin, jur) %>%
  mutate(tipo.sin=ifelse(n <= 60,"OTROS",tipo.sin) ) %>%
  ggplot() +
  geom_mosaic(
    aes(
      weight = n,
      x = product( abbreviate(tipo.sin, 5) ),
      fill = jur),
    alpha=0.5) +
  theme(
      legend.position = "bottom",
      panel.background = element_rect(
        fill="white"),
          axis.title =
      element_text(
        colour="grey24")) +
  labs(
    x = "Tipo de siniestro",
    y = "Proporción jurisdicción",
    fill = "Jurisdicción") +
  scale_fill_manual(
    values =  colores )

```

Salvo despistes y atropellos de animales, los restantes tipos de siniestros predominan en jurisdicciones departamentales. El tipo de accidente con mayor proporción de difuntos es la colisión entre vehículos, acompañada de los despiestes y atropellos de peatones respectivamente.

### Días de supervivencia

```{r,fig.cap="Gráfico de barras y Pareto: proporción de fallecidos según los días de supervivencia luego del accidente, acompañado de la frecuencia relativa acumulada para los mismos."}

ggplotly(
  ggplot() +
    geom_bar(
      data= (datos %>% dplyr::count(f.dias) %>% mutate(n = n / sum(n))) ,
      aes(f.dias, n),
      stat ="identity") +
    stat_ecdf(
      data=datos,
      aes(f.dias),
      cex=1.09,
      geom = "line",
      colour=colores[2]) +
   labs(
     x = "Días de supervivencia luego del accidente" ,
     y = "Proporción de fallecidos") +
   theme_get()+
   theme(
     plot.title = element_text(
     hjust = 0.4,
     size = 16,
     colour = "gray27"),
    axis.title = element_text(
      size=11.6,
      colour="grey20")))

```

La curva azul corresponde al diagrama de Pareto y representa la frecuencia relativa acumulada hasta *x* día.

Existe una probabilidad cercana a un 60% de fallecer en el instante o no superar las 24 horas.

```{r,fig.cap="Gráfico de barras: proporción de fallecidos en muerte súbita según tipo de siniestro."}

datos %>% filter(f.dias == 0) %>% dplyr::count(tipo.sin) %>%
  mutate(n = n / sum(n)) %>%  ggplot() +
  geom_bar(
  aes(reorder(abbreviate(tipo.sin, 6),-n), n),
  stat = "identity",
  show.legend = F) + theme_minimal() +
  labs(
    x = "Tipo de Siniestro" ,
    y = "Proporción de fallecidos") +
  theme(
    axis.title = element_text(
      size=13,
      colour="grey26")  )
```

Muerte súbita hace alución a la persona que falleció en el acto o en menos de 24 horas luego de ocurrido el accidente.

De igual manera que para el total, colisiones entre vehiculos, despistes y atropello de peaton son los tres tipos de siniestros que mayor proporción de fallecios en muerte súbita poseen.

### Departamento

```{r,warning=FALSE,echo=FALSE}

uruguay <- getData("GADM", country = "UY", level = 0)
uruguay_states <- getData("GADM", country = "UY", level = 1)
uystates_UTM <-spTransform(uruguay_states, CRS("+init=EPSG:5383"))
NAME_1 <- uystates_UTM@data$NAME_1

# Función mapa
mapeo<-  function(n)
  {

  df <- data.frame(NAME_1,n)
  uystates_UTM@data$id <- rownames(uystates_UTM@data)
  uystates_UTM@data <- plyr::join(uystates_UTM@data, df, by="NAME_1")
  uystates_df <- fortify(uystates_UTM)
  uystates_df <- plyr::join(uystates_df,uystates_UTM@data, by="id")
  uystates_df <-uystates_df %>% filter(!(NAME_1=="Rivera"& lat<6400000))

  theme_opts <-  list(  theme(
    panel.grid.minor = element_blank(),
    panel.grid.major = element_blank(),
    panel.background = element_blank(),
    plot.background =  element_blank(),
    axis.line =    element_blank(),
    axis.text.x =  element_blank(),
    axis.text.y =  element_blank(),
    axis.ticks =   element_blank(),
    axis.title.x = element_blank(),
    axis.title.y = element_blank(),
    plot.title =   element_text(
      size=16.4,
      colour="darkslategrey",
      hjust=0.25))   )

    ggplot() + geom_polygon(
    data = uystates_df,
    aes(
      x = long,
      y = lat,
      group = group,
      fill = n),
    color = "black",
    size = 0.25) +
    theme(aspect.ratio = 1) +
    theme_opts

  }

```

```{r,echo=F,fig.cap="Gráfico de barras: frecuencia absoluta de fallecidos por departamento."}

ggplot(
  (datos %>% count(dep)  ),
  aes (reorder(abbreviate(dep,4),+n),n)) +
 geom_bar(stat="identity") +
 labs(
   x="Departamento",
   y="Frecuencia absoluta de fallecidos") +
 coord_flip() +
 theme_minimal() +
 theme(
   axis.title  =
     element_text(
       colour="grey30")) +
 geom_hline(
   yintercept = mean(  (datos %>% count(dep))$n   ),
   cex=1.2,
   colour="#d8b960")

```

La recta de color mostaza corresponde a la media  de fallecidos por deparatamento para todo el período designado.

El área metropolitana conformada por los departamentos de Montevideo, Maldonado, Canelones y San José superan la media de fallecidos en el país, lo que implica una clara concentracíon de los accidentes fatales en la zona sur del territorio nacional.

```{r}

# Censo 2011, fuente: INE.
censo<- c(73378,520187,84698,123203,57088,
          25050,67048,58815,164300,1319108,
          113124,54765,103493,68088,124878,
          108309,82595,90053,48134)

# Tasa de fallecidos cada 10.000 habitantes.
pob.dep<- cbind((datos %>% count(dep) %>% arrange(dep)),censo)%>% mutate(tasa=(n/censo)*10000)

```

```{r,echo=F,fig.cap="Gráfico de mapas: tasa de fallecidos en accidentes de tránsito cada 10 mil habitantes por departamento."}

  mapeo(   cbind((datos %>% count(dep) %>% arrange(dep)),censo)%>%
          mutate(n=(n/censo)*10000)    ) +
  labs(fill = "Tasa",
  x = NULL,
  y = NULL) +
  scale_fill_gradient2(
  low = "#d8b365",
    mid = "white",
    high = "#5ab4ac",
    midpoint = mean(pob.dep$tasa))

```

```{r,fig.cap="Gráfico de mapas: tasa de fallecidos en accidentes de tránsito cada 10 mil habitantes por departamento, faceteado por año."}

mapeo(n= (cbind((datos %>% count(a,dep) %>% arrange(a)), rep(censo,5)) %>%
          mutate(n=(n/censo)*10000))  ) +
  labs(
    fill = "Tasa",
    x = NULL,
    y = NULL) +
  scale_fill_gradient2(
    low = "#d8b365",
    mid = "white",
    high = "#5ab4ac",
    midpoint = mean(
      (cbind((datos %>% count(a,dep) %>% arrange(a)), rep(censo,5)) %>%
                       mutate(n=(n/censo)*10000))$n )) +
  facet_wrap( ~ a)

```

El punto medio corresponde a 90 fallecidos. Este valor es elegido arbitrariamente con el fin de mejorar la visualizacion, debido a que la tanto la media como mediana poseen la mayoría de los departamentos a frecuencias absolutas muy disipersas.

### Fecha y hora

```{r,warning=FALSE,echo=F}
fecha<-    datos %>% separate(  fecha,c("dia","mes")  ) %>%
    mutate( f.h=  paste( paste(a,mes,dia,sep="-") ,  hora )  ) %>%
    mutate( f.h=  as.POSIXct(f.h, format="%Y-%m-%d  %H:%M:%S",tz="GMT"))%>%
    dplyr::select(f.h)

n.dia <-  weekdays(       as.Date(  as.vector(t (fecha[1])  )    ) )

f<- data.frame(fecha,n.dia)

```

```{r,fig.cap="Gráfico de serie de tiempo: frecuencia absoluta de fallecidos según año y mes."}

f %>%
  count(  a.mes=    floor_date(f.h, "1 month"))  %>%
     ggplot(
       aes(as_date(a.mes),n,group=1) ) +
     geom_point()  +
  geom_line(
    stat="identity")+
  geom_smooth(
    method = "loess",
    colour=colores[2],cex=1.4)+
     labs(
         x = "Año",
         y = "Frecuencia absoluta de fallecidos") +
     theme_minimal() +
     theme(
       axis.title = element_text(
         colour="grey30",
         size=12),
       axis.text =element_text(
            colour = "grey27",
            size=9)       )  +
 scale_x_date(
   date_labels =("%Y"),
   date_breaks = "1 year" )

```

 Se nota una leve tendencia en la frecuencia absoluta de fallecidos por mes, siendo decreciente hasta el año 2016 y luego retomando lentamente el crecimieto en 2017.
Existe un valor que si bien no llega a ser un dato atípico posee un gran desvío con repecto a la regresión lineal.

```{r,fig.cap="Diagrama térmico: frecuencia absoluta de fallecidos según día y hora del accidente."}

f %>% count(n.dia, hrs= format(f.h,"%H")) %>%
  ggplot(aes(hrs, ordered(
    n.dia,
    levels = c( "lunes",  "martes",  "miércoles",
                "jueves",  "viernes","sábado", "domingo" )))) +
  geom_tile(aes(fill = n)) +
  scale_fill_gradient2(
    low = "white",
    high = "midnightblue",
    mid = "turquoise",
    midpoint = mean(
      (f %>% count(n.dia, hrs=format(f.h,"%H")))$n  )) +
  labs(
    x = "Hora",
    y = "Día",
    fill="Fallecidos") +
  theme(
    axis.title = element_text(
      size=13,
      colour="grey34",
      face="bold"),
    axis.text = element_text(
      size=10.4),
    panel.background = element_rect(
      colour="white"))

```

Los accidentes se concentran de 16:00 a 20:00 horas, aumentando paulativamente a medida se acercan los días correspondientes al fin de semana.


I don't see why we couldn't. Want to PR it?


I don't think this is needed. `headers` can be a plain object


This selector can be added to `textarea`; `resize` and `tab-size` won't have any effect on it.


yes, it should.


I'd add a link to `https://github.com/settings/tokens` inside `strong`


it appears you have **removed** `bootstrap-jqueryui` from Core-2.0 branch. you cannot do that. You can deprecate it, but not remove it until 2.1 (technically, it shouldn't be removed until 3.0 actually). Please reinstate the lib into 2.0 branch.


Created multidev environment [riveralive-cms#pr-11](https://dashboard.pantheon.io/sites/ced938b0-bbbf-4ed2-ba1c-98b66d8ba2be#pr-11).

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


Thank you for the reply, Ronald. Your point is well-taken.

While I am still dubious that a SPRT(-3,1) test with an LOS in the mid-80's should be considered conclusive enough for a revert, I'm sure testing resources could be better used elsewhere than on a straight-up "re-revert" of this patch.

An alternative course of action would have been tuning f268123 to have more up-to-date constants rather than reverting it entirely as this patch did. To me, the fact that a patch with such a promising debut isn't as potent of an ELO-gainer anymore suggests the need for tuning, not necessarily that it is "redundant" as the commit's author hypothesized.


# Specs execution successful
:scroll: [View logs](http://bamboo.comnull)
### Plans updated

Bamboo specs have been successfully imported and the following plans have been updated.

Project | Plan | Build
---|---|---
[Test](http://bamboo.com/browse/TEST) | [Comment test](http://bamboo.com/browse/TEST-CTEST)  | :white_check_mark: [\#1](http://bamboo.com/browse/TEST-CTEST-1)
[New project](http://bamboo.com/browse/NEW) | [Disabled plan](http://bamboo.com/browse/NEW-DISABLED) **disabled** | :white_check_mark: [\#1](http://bamboo.com/browse/NEW-DISABLED-1)

### Deployments updated

Bamboo specs have been successfully imported and the following deployment projects have been updated.

|Deployment project |
----|
[Deployment test](http://bamboo.com/deploy/viewDeploymentProjectVersions.action?id=2162689)|


Created multidev environment [rail-uga-stellar#ci-130](https://dashboard.pantheon.io/sites/05f5afa3-c1ec-448f-915a-9234103f2409#ci-130).

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


Fixed issue #1


Rather than implementing each of these yourself, I think you should be able to call [`memoryUsage()`](https://github.com/ImageEngine/cortex/blob/master/include/IECore/Object.h#L131-L132) assuming those are all TypedDatas.


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


@CyTheRabbit Good tip! I've pushed change now.


Wouldn't it be more "correct" to use `Headers`, since it's a part of the Fetch API?


foi feita a função soma das linhas e a das colunas.


Спасибо ! Вот только недавно столкнулся с ошибкой nonce.)) Надеюсь больше ее не встречу)


158368465-Improve-error-#6375 (lgu1234) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (2967 of 2967 tests passed, 11 test warnings)

Messages:

 * 11 tests had: AUD diffs.

![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)


`Headers` is low-level. If the `fetch` API allows for higher-level usage we don't need to get our hands dirty with that, lengthening the code.


TeamCity Glyssen :: Glyssen pull requests - untagged [Build *.*.8.8b938473339b43bc4a94f7ed124b0d39b8e2f953](http://build.palaso.org/viewLog.html?buildId=122544&buildTypeId=Glyssen_GlyssenPullRequestsUntagged) outcome was **FAILURE**
Summary: Failed to resolve artifact dependency Build time: 00:00:28


hfhhh


TeamCity Glyssen :: Glyssen pull requests [Build *.*.701.8b938473339b43bc4a94f7ed124b0d39b8e2f953](http://build.palaso.org/viewLog.html?buildId=122545&buildTypeId=Glyssen_GlyssenPullRequests) outcome was **FAILURE**
Summary: Compilation error: GlyssenShared\GlyssenShared.csproj Build time: 00:00:39


## Global

| Changed         |   Status |
|:----------------|---------:|
| `coverage`      |     -0.1 |
| `nodes_count`   |  -1546   |
| `texts_passing` |     -1   |

## Words

| Changed   |   Status |
|:----------|---------:|
| `lat`     |   -10217 |

## Units

| Changed                                                 | Status   |
|:--------------------------------------------------------|:---------|
| `./data/phi0119/phi004/phi0119.phi004.perseus-lat2.xml` | Failing  |

*[Hook UI build recap](http://ci.perseids.org/repo/PerseusDL/canonical-latinLit/4361)*


More or less guessing here, but maybe this still needs to be set? /cc @Ericson2314


I realized that we don't need to throttle this because it's only ever checked upon the game loop asking for momentum. The keydown listener is different though because it can change momentum in between game loop runs. Joy cannot, only changes momentum at runtime. So it essentially has `handledInput` check built-in.


Update plots folder


158368465-Improve-error-#6375 (lgu1234) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed, 0 test warnings)

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


[R/addins.R:9:7:](https://github.com/inbo/INBOmd/blob/650c77fa5bbdfe6e2d7907ce6caa79daf379a991/R/addins.R#L9) *error:* **unexpected symbol**
```r
<U+200B>Enter your Markdown here. Last line should be blank.
      ^
```
[R/addins.R:34:1:](https://github.com/inbo/INBOmd/blob/650c77fa5bbdfe6e2d7907ce6caa79daf379a991/R/addins.R#L34) *style:* **Trailing blank lines are superfluous.**
```r
<U+200B>
^
```
[R/inbo_poster.R:165:19:](https://github.com/inbo/INBOmd/blob/650c77fa5bbdfe6e2d7907ce6caa79daf379a991/R/inbo_poster.R#L165) *warning:* **Do not use absolute paths.**
```r
<U+200B>    text <- gsub("\\\\b(.*)block", "\\\\begin{\\1block}", text)
                  ^~~~~~~~~~~~~~
```
[R/inbo_poster.R:165:37:](https://github.com/inbo/INBOmd/blob/650c77fa5bbdfe6e2d7907ce6caa79daf379a991/R/inbo_poster.R#L165) *warning:* **Do not use absolute paths.**
```r
<U+200B>    text <- gsub("\\\\b(.*)block", "\\\\begin{\\1block}", text)
                                    ^~~~~~~~~~
```
[R/inbo_poster.R:166:19:](https://github.com/inbo/INBOmd/blob/650c77fa5bbdfe6e2d7907ce6caa79daf379a991/R/inbo_poster.R#L166) *warning:* **Do not use absolute paths.**
```r
<U+200B>    text <- gsub("\\\\e(.*)block", "\\\\end{\\1block}", text)
                  ^~~~~~~~~~~~~~
```
[R/inbo_poster.R:166:37:](https://github.com/inbo/INBOmd/blob/650c77fa5bbdfe6e2d7907ce6caa79daf379a991/R/inbo_poster.R#L166) *warning:* **Do not use absolute paths.**
```r
<U+200B>    text <- gsub("\\\\e(.*)block", "\\\\end{\\1block}", text)
                                    ^~~~~~~~
```


@DatGuyJonathan - I ran into an issue today where my SFDX CLI was in a partial state since I was developing. I was astonished to find that it caused the entire salesforcedx-vscode-core package to not load (this is from the installation from the marketplace). The error message is not very clear as well since it happened during the `activate` sequence.

I think putting such a big command like `setupGlobalDefaultUserIsvAuth()` , i.e., an operation that can throw, error without a try.. catch is a mistake. If this fails the entire salesforcedx-vscode-core doesn't load, which means the other packages that depend on it (e.g., apex replay debugger, debugger, etc) *all* fail to load as well.


hmmm


158368465-Improve-error-#6375 (lgu1234) - Win64-Windows-7-VisualStudio-14: OK (2927 of 2927 tests passed, 11 test warnings)

Messages:

 * 11 tests had: AUD diffs.

![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)


[R/addins.R:9:7:](https://github.com/inbo/INBOmd/blob/6c8c647cb76a7225e1111303bc7cafd40f62dc7f/R/addins.R#L9) *error:* **unexpected symbol**
```r
<U+200B>Enter your Markdown here. Last line should be blank.
      ^
```
[R/addins.R:34:1:](https://github.com/inbo/INBOmd/blob/6c8c647cb76a7225e1111303bc7cafd40f62dc7f/R/addins.R#L34) *style:* **Trailing blank lines are superfluous.**
```r
<U+200B>
^
```
[R/inbo_poster.R:165:19:](https://github.com/inbo/INBOmd/blob/6c8c647cb76a7225e1111303bc7cafd40f62dc7f/R/inbo_poster.R#L165) *warning:* **Do not use absolute paths.**
```r
<U+200B>    text <- gsub("\\\\b(.*)block", "\\\\begin{\\1block}", text)
                  ^~~~~~~~~~~~~~
```
[R/inbo_poster.R:165:37:](https://github.com/inbo/INBOmd/blob/6c8c647cb76a7225e1111303bc7cafd40f62dc7f/R/inbo_poster.R#L165) *warning:* **Do not use absolute paths.**
```r
<U+200B>    text <- gsub("\\\\b(.*)block", "\\\\begin{\\1block}", text)
                                    ^~~~~~~~~~
```
[R/inbo_poster.R:166:19:](https://github.com/inbo/INBOmd/blob/6c8c647cb76a7225e1111303bc7cafd40f62dc7f/R/inbo_poster.R#L166) *warning:* **Do not use absolute paths.**
```r
<U+200B>    text <- gsub("\\\\e(.*)block", "\\\\end{\\1block}", text)
                  ^~~~~~~~~~~~~~
```
[R/inbo_poster.R:166:37:](https://github.com/inbo/INBOmd/blob/6c8c647cb76a7225e1111303bc7cafd40f62dc7f/R/inbo_poster.R#L166) *warning:* **Do not use absolute paths.**
```r
<U+200B>    text <- gsub("\\\\e(.*)block", "\\\\end{\\1block}", text)
                                    ^~~~~~~~
```


This will become obsolete once https://github.com/getgrav/grav/commit/bd7706a38e86b563b559f12211d0fb7497b942b2 is merged to `master`.


Their actual roles, like Game Master, or Participant


Grazie per avere speso del tempo per osservare il mio lavoro. Spero sia piaciuto! =


Yes.


Per vedere  il lavoro =


vai alla Home =


Fine if it works - slightly worried that the cygwin directory might have bash, but we can see...


Husk at det var Christoffer der skrev kommentarerne; Joachim flyttede dem over manuelt fra hans branch.


need to remove the original files


The problem with original text should disappear if we move the parser to processors, so we don't need EidosDocument anymore.

It passes TestSerialization if I run it alone (both for 2.11 and 2.12). Actually, I have got some successful runs of the whole test suite, but it crashes many times. I will try to move the beta versions of deeplearning4j (move means patch it again) and see if the behavior is more stable.


Set classnames v2.2.5

Preview: documentation | landing | table


- Cerca delle risposte ad alcune FAQ -


@fujita , while working on https://github.com/osrg/gobgp/issues/1736, I noticed that each `NewGobgpApiClient()` call creates a socket and the socket does not close until app exits. When you tested the exporter, did you see incremented number of open network sockets with `netstat -antlp`?


Hmm
I use it here, because I update check status in `check_param_values()`.
But now I see there is a redundancy, I will fix that, thank you!


Good catch (sorry for the delay)! @aerydna ping


Thank you for pointing that out!


Could we please keep the ordering in alphabetical order?

Also Bahasa Indonesian is the standardized dialect of Malay (the most of Indonesian) and only the following specialized languages variants for Indonesian are known: id (Indonesian) jv (Javanese) su (Sundanese). So the language should simply named 'Indonesian' or 'Indonesian (Indonesian)'.

http://www.i18nguy.com/unicode/language-identifiers.html


I would expect this to be a pointer, should not compile unless we use `*inst.ProtectedFromScaleIn`


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f501da27-3f39-4c54-afa4-5872435d654b?env_id=ibm%3Ayp%3Aus-south "cloud-native-toolchain-tutorial-20180613201110556"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/ddaba6a0-88e3-41a4-83a9-270608d5160d?env_id=ibm%3Ayp%3Aus-south "sample-cloud-native-toolchain-tutorial-20180613201110556") deployed [sample-cloud-native-toolchain-tutorial-20180613201110556](https://github.com/kcreed713/sample-cloud-native-toolchain-tutorial-20180613201110556/releases/tag/deploy-ibm-yp-us-south-kcreed-us.ibm.com-test-20180614-193041 "deploy-ibm-yp-us-south-kcreed-us.ibm.com-test-20180614-193041") to [test](https://console.bluemix.net/apps/19bc4262-347f-4f5f-9956-5fbf287e7b3e?env_id=ibm:yp:us-south "ibm:yp:us-south:kcreed@us.ibm.com:test"), including this commit


Happy to help!


Sapien's Graphics, ecco il nome del canale YT che mira a stare al  passo con questo sito Web, quindi non so se lo tradurrai oppure andrai a lasciarlo uguale


This is 1st commit


Is it nice?


Ah, @vak2ve, I think I misread the previous commit!  If you need me out of the file, let me know.

I'm going to work on those undated `date` in 1873p2v3 right now.


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/f501da27-3f39-4c54-afa4-5872435d654b?env_id=ibm%3Ayp%3Aus-south "cloud-native-toolchain-tutorial-20180613201110556"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/ddaba6a0-88e3-41a4-83a9-270608d5160d?env_id=ibm%3Ayp%3Aus-south "sample-cloud-native-toolchain-tutorial-20180613201110556") deployed [sample-cloud-native-toolchain-tutorial-20180613201110556](https://github.com/kcreed713/sample-cloud-native-toolchain-tutorial-20180613201110556/releases/tag/deploy-ibm-yp-us-south-kcreed-us.ibm.com-prod-20180614-193359 "deploy-ibm-yp-us-south-kcreed-us.ibm.com-prod-20180614-193359") to [prod](https://console.bluemix.net/apps/a9a4ef1d-fd0b-4a3f-823f-e943fa46843d?env_id=ibm:yp:us-south "ibm:yp:us-south:kcreed@us.ibm.com:prod"), including this commit


Yes i used audit2allow as it was the first time i was working with sepolicy stuff btw what do you recommend should i remove write access and leave open access?


o(n*k) time seems more accurate


@everyone @here


Not that it matters much, but since this is a library, it seems like we don't need to version this.

(Same with sha512 since that never changes.)


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


Looks like the BEAGLE v2.1.2 installer places `libhmsbeagle-jni.jnilib` in `/Library/Java/Extensions`. I forgot to do that for the 3.0 installer. Will work on an update.


@jgvictores Opened an issue (#1749) since there is no way I can keep track of comments on commits :wink:


<script>
window['_fs_debug'] = false;
window['_fs_host'] = 'fullstory.com';
window['_fs_org'] = 'CRT6E';
window['_fs_namespace'] = 'FS';
(function(m,n,e,t,l,o,g,y){
    if (e in m) {if(m.console && m.console.log) { m.console.log('FullStory namespace conflict. Please set window["_fs_namespace"].');} return;}
    g=m[e]=function(a,b){g.q?g.q.push([a,b]):g._api(a,b);};g.q=[];
    o=n.createElement(t);o.async=1;o.src='https://'+_fs_host+'/s/fs.js';
    y=n.getElementsByTagName(t)[0];y.parentNode.insertBefore(o,y);
    g.identify=function(i,v){g(l,{uid:i});if(v)g(l,v)};g.setUserVars=function(v){g(l,v)};
    g.shutdown=function(){g("rec",!1)};g.restart=function(){g("rec",!0)};
    g.consent=function(a){g("consent",!arguments.length||a)};
    g.identifyAccount=function(i,v){o='account';v=v||{};v.acctId=i;g(o,v)};
    g.clearUserCookie=function(){};
})(window,document,window['_fs_namespace'],'script','user');
</script>


R code for applying Natural Language Processing on the text data and predicting the class of genetic mutation


Их несколько. Сделай пулл реквест. Если полезно, сделаю мердж.


CUBA US Embassy Sound


yarn.lock

Preview: documentation | landing | table


I have resolved most of the issue. Some minor fixes are pending


I wouldn't write this test like this, it's too trivial to test that one-liner like this.

But instead i'd enhance the tests for getInstance to also take into account this protected flag.


What version directive is GPUShader using? and how can i set it? i wanna user version directive 330


Added Sharing executables content to DITA source


Created multidev environment [ci-project#gnam-312b](https://dashboard.pantheon.io/sites/f25fa188-adfb-4c8e-b7fb-5fcfeb7d7b28#gnam-312b).

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


Not sure where to comment really, but according to Windows 10 this version is a Virus?


uncomment and set to log.debug


jmhjk


Dan ... with all these changes are we able to consider a more general dark theme to xLights ... or is it at some point going to be dependent upon something uniquely in OSX?


Hmm, good point. Feel free to fix it, I don't have time right now.


I don't know where, but `asciidoctor` should be included as a dependency/requirement, shouldn't it ?


This merge commit looks a bit out of control, is the diff accurate? A bit worried that it becomes hard to trace misalignments - which is why i always suggest merging through pull requests, it makes it very easy to track the changesets.


158368465-Improve-error-#6375 (lgu1234) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (1679 of 1679 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-40.35%25-green.png)


zmien na `/card/`, bo teraz usuwanie kart nie dziala


It helps even if you just open the PR and merge it immediately, since the "Files changed" tab tends to be very reasonable -- with very rare exceptions e.g. forcing the branch to a weird state.


test it, please


@fujita , what do you think about adding `Global.GetRouterId()` and `Global.GetAs()` as Labels to the `up` metric?


Ah crap, I'm sorry. I didn't know it would break your code 😞 is it possible for you to move it back?


Thanks, that makes sense. Maybe one day there'll be an optimized Refaster compiler ;)


closes #15


Looks more like you need to label the path vibrator hal is writing/reading with sysfs_vibrator.


все иконки выносятся в отдельный компонент…


0 is abs function, should it be [2,2,2] ?


I don't think this is a good idea. It's just rild scanning for netmanager. Not every denial you see needs / should be fixed.


так делать нельзя, это костыль адовый…


[2,2,2] ?


Понял, вынесу просто иконки и всё.


nieusuniety komentarz


3x nowa linia (niepoprawne formatowanie)


klasa encji nie powinna byc beanem springa


to co wczesniej


outstanding!


![](https://github.trello.services/images/mini-trello-icon.png) [Howto : egyszerű adatok megjelenítése](https://trello.com/c/1LMIPbb1/11-howto-egyszer%C5%B1-adatok-megjelen%C3%ADt%C3%A9se)


~on~


jezeli jakis wyjatek sie pojawi to nawet nie zostanie wyswietlony i bardzo ciezko bedzie Ci dojsc do tego "czemu nie dziala"


This isn't grammatical and it's still tech-heavy. Can we soften here?

...layout properties and tweaks made based on the size of the display area


taka sciezka tez powinna zostac przetestowana


Not really, I have tested this solution and it is not correct because sometimes (for some test cases) the application subtracts digest from payload and this info is stored in a way in request->auth_icv_offset so we still have to base on this offset.


needs a comma


@drakeltheryuujin solid improvement. Fix these andI think it'll be good to merge.


I'm seeing if it has to be named index.html


He was a sailor boy, she said see you later boy


맞팔 ^^


jKSlsadlasjdkjASKJDkasdj


영광입니다...ㅎㅎ


@eviltrout can you please review this commit?


소스에 마구니가 가득하구나..


Build version: __`0.10.0-master.152`__ :crossed_fingers: [`master`](https://github.com/streamich/ci-scripts/tree/master) on [*CircleCI*](https://circleci.com/gh/streamich/ci-scripts/152) :tada:


哎呀妈呀,良哥得打你


leetcode刷题来巩固数据结构和算法


Build version: __`0.10.0-master.229`__ :crossed_fingers: [`master`](https://github.com/streamich/ci-scripts/tree/master) on [*Travis*](https://travis-ci.org/streamich/ci-scripts/builds/392048320) :tada:


영광입니다..ㅎㅎ


+iOS 版本号：v15.5.5 修改时间：2018-06-12


needs to be finished... Not finished yet.


마구니가 끼었어!!!


as electron pulse


-contract CGCC {


Don't exclude URL's from security filter, instead do role action mapping with this URL and PUBLIC role and commit the migration file in implementation.


@austin987

Well technically you don't disable `Z:/ -> /` mappings when running **isolate_home** as that requires you to manually remove the `/` symlink as well!

But I'll remove the registry key reference from the **isolate_home** verb... To ensure the functionality is 100% as intended!


이건 지워야겠네요 조장대행님.


ㅎㅎ


<details>

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

You do not have sufficient scopes. You are missing the following scopes:

{
  "AnyOf": \[
    {
      "AnyOf": \[
        "queue:create\-task:highest:aws\-provisioner\-v1/servo\-docker\-worker",
        "queue:create\-task:very\-high:aws\-provisioner\-v1/servo\-docker\-worker",
        "queue:create\-task:high:aws\-provisioner\-v1/servo\-docker\-worker",
        "queue:create\-task:medium:aws\-provisioner\-v1/servo\-docker\-worker",
        "queue:create\-task:low:aws\-provisioner\-v1/servo\-docker\-worker",
        "queue:create\-task:very\-low:aws\-provisioner\-v1/servo\-docker\-worker",
        "queue:create\-task:lowest:aws\-provisioner\-v1/servo\-docker\-worker"
      \]
    },
    {
      "AnyOf": \[
        "queue:create\-task:aws\-provisioner\-v1/servo\-docker\-worker",
        {
          "AllOf": \[
            "queue:define\-task:aws\-provisioner\-v1/servo\-docker\-worker",
            "queue:task\-group\-id:taskcluster\-github/ESpIocJIS9mi1Qn0okt3Zg",
            "queue:schedule\-task:taskcluster\-github/ESpIocJIS9mi1Qn0okt3Zg/ESpIocJIS9mi1Qn0okt3Zg"
          \]
        }
      \]
    }
  \]
}

You have the scopes:

```
\[
  "assume:project:taskcluster:mozilla\-github\-repository",
  "assume:repo:github.com/servo/servo:pull\-request",
  "notify:email:\*",
  "notify:irc\-channel:\*",
  "notify:irc\-user:\*",
  "queue:create\-task:aws\-provisioner\-v1/github\-worker",
  "queue:create\-task:aws\-provisioner\-v1/github\-worker\-windows",
  "queue:create\-task:aws\-provisioner\-v1/servo",
  "queue:create\-task:aws\-provisioner\-v1/win2012r2",
  "queue:route:garbage.\*",
  "queue:route:index.garbage.\*",
  "queue:route:notify.email.\*",
  "queue:route:notify.irc\-channel.\*",
  "queue:route:notify.irc\-user.\*",
  "queue:scheduler\-id:taskcluster\-github",
  "secrets:get:garbage/\*",
  "secrets:set:garbage/\*"
\]
```

This request requires you to satisfy this scope expression:

```
{
  "AllOf": \[
    {
      "AnyOf": \[
        {
          "AllOf": \[
            "queue:scheduler\-id:taskcluster\-github",
            {
              "AnyOf": \[
                "queue:create\-task:highest:aws\-provisioner\-v1/servo\-docker\-worker",
                "queue:create\-task:very\-high:aws\-provisioner\-v1/servo\-docker\-worker",
                "queue:create\-task:high:aws\-provisioner\-v1/servo\-docker\-worker",
                "queue:create\-task:medium:aws\-provisioner\-v1/servo\-docker\-worker",
                "queue:create\-task:low:aws\-provisioner\-v1/servo\-docker\-worker",
                "queue:create\-task:very\-low:aws\-provisioner\-v1/servo\-docker\-worker",
                "queue:create\-task:lowest:aws\-provisioner\-v1/servo\-docker\-worker"
              \]
            }
          \]
        },
        {
          "AnyOf": \[
            "queue:create\-task:aws\-provisioner\-v1/servo\-docker\-worker",
            {
              "AllOf": \[
                "queue:define\-task:aws\-provisioner\-v1/servo\-docker\-worker",
                "queue:task\-group\-id:taskcluster\-github/ESpIocJIS9mi1Qn0okt3Zg",
                "queue:schedule\-task:taskcluster\-github/ESpIocJIS9mi1Qn0okt3Zg/ESpIocJIS9mi1Qn0okt3Zg"
              \]
            }
          \]
        }
      \]
    }
  \]
}
```
----
method:     createTask
errorCode:  InsufficientScopes
statusCode: 403
time:       2018-06-14T02:19:46.644Z

</details>


范德萨


(_ ( 'การเข้ารหัสและถอดรหัสไม่ได้ใช้งานโดย{} ' ) รูปแบบ ( self .device ) )


TEST RUN GITHUB


Wow, thanks for your comments, I'm very appreciating that 👍


Gud


The original design intent was to all the author the take complete control of their document when they chose to override the header and footer.  This has proven to be an inferior design decision.  I have had over six authors struggle with their document layout when they chose to override tlc-article default header and footer.  The problem presents itself when the table of contents expands a single page.  To resolve this problem, I have moved line 182 outside of the if-then-else construct.


qwe


`NA` here is an indicator for missingness that has a universal type (generally it's given as a `logical()`). Why are these options being switched to `character()`? Some look `numeric`/`integer` in nature.


Much better! Thanks.


some changes


ㅊㅋㅊㅋ!!!


Why was CoreMinimal.h added everywhere instead of the main PCH file?


actually it is in the OceanPluginPrivatePCH.h file... why was this needed?


Small change


@satyaki07 because we have one group of words ( the phrase) that do not have any emoji. therefore if we edit the previous one. it will have errors, because you don't have input for that group.


Test


Boa noite, fiz a função cancelar_produto e disponibilizar_produto.
Coloquei no github se puder analisar estar em #funções.
Desde já agradeço.

2018-05-21 14:41 GMT-03:00 César Vasconcelos <notifications@github.com>:

> Oi, Mércia.
> Fiz o upload dos módulos 1 e 2.
> []s
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/cesarvasconcelos/ifpb-python/commit/fec069a41be07be0e66fed42a9e7b0481e4c2509#commitcomment-29063977>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AlWBkL_DYU2NWTD5q31guYVNMfXdSsz-ks5t0vxmgaJpZM4UEBoB>
> .
>

--
*Mércia Regina da Silva*
Estudante do Curso Superior de Bacharelado em Engenharia de Computação
Instituto Federal da Paraíba - Campus Campina Grande
Tel.: +55 (83) 98667-7269 / Residencial: +55 (83) 3077-5645
Skype: merciareginacg


done


改啥该你个二傻子


c++


修改了js文件


Thank you!
By this same problem, I waste my 2 days.
This code save me a lot. :)


GOOD


## What is this for???

Please explain this line better


write my first git


## Commit Comment
looking


ということはalarmtimeintervalint自体が期限-なうと言うこと??
試してみたい


test


Pet turecek


### Lipsum? This was the __best__ filler you could come up with?


Not seeing it


Unfortunately thats to display a single backslash and a comma


1. Pre-requisite


is there a problem with the build process? actually i'm not able to build the admin.... :(


Sure this can be implemented inside the class


### Lipsum?

This was the __best__ I could come up with?


Created multidev environment [riveralive-cms#pr-11](https://dashboard.pantheon.io/sites/ced938b0-bbbf-4ed2-ba1c-98b66d8ba2be#pr-11).

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


Hi @WaxCylinderRevival,

I know the structural changes I made involved the nesting of divs within the General Appendix and ch7 in particular but I can't remember what they were exactly...I think I'm turned around with the restructuring of frus1873p1v2, which is much tougher than I'd anticipated!

If you uploaded my most recent version of the file to your localhost and the TOC looks right to you (another sign that it's the right version is that there shouldn't be any more all-caps in the heads) then I suppose whatever I did worked?

I do have uncommitted changes in 1873p1v2 (again, a lot of restructuring) but should be done with that by the end of the day!


Hey I have Coding of Duel, where two IDs Duel with each other automatically and Give credits.
I don't know why it is not wotking
Can you check if i give you both the files ?


Odd, IGeometry already had a Envelope method that returns a IGeometry. I turned it into a property so now this is identical to NTS. The difference is still that NTS has no BoundingBox at all and Mapsui depends on it heavily.


Alright


Wrong folder


Okay, I'll stay out of 1873p1v2!

In 1873p2v3, I added `date/@notBefore | @notAfter` to undated `date` and added `div/@frus:doc-dateTime-min | @frus:doc-dateTime-max`. I'm committing now.  Since there's only two schema errors that will remain, I'll go ahead and run the rest of the transformations on that volume!

I'll be out of the office until the Wednesday after next so I'll touch base when I return to see if you need me to look at any volumes.  Feel free to keep @ me in the meantime!

Thanks again!


Is it ever possible get false out of this expression?


Dear Poggit user,

This is an automatic message from Poggit-CI. Poggit-CI was triggered by this commit, but failed to create builds due to the following error:

```
Resend this delivery later. This commit is triggered by user Zadezter, who
has created 60 Poggit-CI builds in the past 168 hours.

Contact @SOF3 [on Discord](https://discord.gg/NgHf9jt) to request for extra
quota. We will increase your quota for free if you are really contributing
to open-source plugins actively without abusing Git commits.
```

As a result, no builds could be created from this commit. More details might be available for repo admins at [the webhook delivery response log](https://github.com/ImpladeDeveloped/Implactor/settings/hooks) — see the webhook starting with `https://poggit.pmmp.io/webhooks.gh.repo` and look for the delivery with ID `12eb34be-700f-11e8-8136-19e5a09054de`.

Shall you need any assistance, you may contact us on [on Discord](https://discord.gg/NgHf9jt), or more publicly, [on GitHub](https://github.com/poggit/support/issues). Commenting on this commit directly will **not** notify any Poggit staff.

Regards,
Poggit Bot (@poggit-bot)
The official Poggit automation account


This is not really an optimization, although it should allow more efficient database transaction handling when updating many thousands of locations, which we are planning to test soon.


kk eae CircleCI aprova aí


## Global

| Changed         |   Status |
|:----------------|---------:|
| `coverage`      |     -0.2 |
| `nodes_count`   |  -1606   |
| `texts_passing` |     -2   |

## Words

| Changed   |   Status |
|:----------|---------:|
| `lat`     |   -17990 |

## Units

| Changed                                                 | Status   |
|:--------------------------------------------------------|:---------|
| `./data/phi0119/phi004/phi0119.phi004.perseus-lat2.xml` | Failing  |
| `./data/phi1348/abo014/phi1348.abo014.perseus-lat2.xml` | Failing  |

*[Hook UI build recap](http://ci.perseids.org/repo/PerseusDL/canonical-latinLit/4363)*


This is not really an optimization, although it should  allow more efficient database transaction handling when updating many  thousands of locations, which we are planning to test soon.


It might be mistaking the keystroke capture functionality for a virus


P.S. It would be a good idea to format and indent before committing any changes to 1873p1v2. It'll reduce reconciliation issues.


I just updated it.


So I've investigated this and this is what I've found:
- BEAST v1.8.4 appears to look for BEAGLE `jnilib` in `/usr/local/lib`. If `libhmsbeagle-jni.jnilib` is only in `/Library/Java/Extensions` it does not find BEAGLE.
- BEAST v1.10.0 appears to look for BEAGLE `jnilib` in `/Library/Java/Extensions`. If `libhmsbeagle-jni.jnilib` is only in `/usr/local/lib` it does not find BEAGLE.

The latest BEAGLE installer (v3.0.1) places `libhmsbeagle-jni.jnilib` only in `/usr/local/lib`.  I can change it to place it in `/Library/Java/Extensions` or in both locations but then the user (for macOS 10.11 or later) will get a scary warning message because I'm modifying a `Library` folder. The message looks like this:

https://www.dropbox.com/s/4hwr5kdgcr3jc93/beagle-install-error.png?dl=0

So maybe the best option is to modify BEAST v1.10?


Created multidev environment [nhtv#ci-57](https://dashboard.pantheon.io/sites/a5faca03-4b4c-4936-95b8-6410ab7b2c55#ci-57).

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


This really works. We can do both initialisation of every particular member of array, or init of first member and rest zeroes.


Style zmieniamy w CSS, a nie bezpośrednio w HTML.


Projekt Titanic


Oh you mean we could do the testing within one of the examples code?


Znowu nie ma polskich znaków?


![](https://github.trello.services/images/mini-trello-icon.png) [T135: Schriftarten einfügen](https://trello.com/c/uKouEVYy/154-t135-schriftarten-einf%C3%BCgen)


Updating docs: https://github.com/rails/rails/pull/33136


Here's a verbatim example:

```
mqudsi@freebsd ~> service smartd -v
/usr/local/etc/rc.d/smartd: unknown directive '-v'.
Usage: /usr/local/etc/rc.d/smartd [fast|force|one|quiet](start|stop|restart|rcvar|enabled|describe|extracommands|reload|report|status|poll)
```

With `stop`, `faststop`, `forcestop`, etc. all being valid commands. So I transform `[a|b|c](1|2|3)` to `{,a,b,c}{1,2,3}` and expand.

I think we need a `expand` builtin that safely evaluates the expansion of an argument without having to resort to a potentially dangerous `eval` call.


Może jestem nie w temacie, ale dlaczego "za godzinę"? Ten czas jest gdzieś ustalony?


Updated TODO list


Yes, but it seems to me that it should replace the path...
The actuator will know the path, only needs to know the id...


If "c:\a" and "c:\b\" gives "..\b\" I would expect "c:\a\b" and "c:\a\" to give "..\" ?


I might've spoken too soon.. now I'm getting the macOS warning even when not modifying `/Library` but yet the previous installer runs fine. Will keep investigating..


so I guess https://github.com/spesmilo/electrum/commit/0438bbc2c26d32ec17c76a0c8f1beb69255142f2 was not exactly the best idea..


Or do we consider `..` and `..\` interchangeable forms


## Global

| Changed         |   Status |
|:----------------|---------:|
| `coverage`      |     -0.2 |
| `nodes_count`   |  -1606   |
| `texts_passing` |     -2   |

## Words

| Changed   |   Status |
|:----------|---------:|
| `lat`     |   -17990 |

## Units

| Changed                                                 | Status   |
|:--------------------------------------------------------|:---------|
| `./data/phi0119/phi004/phi0119.phi004.perseus-lat2.xml` | Failing  |
| `./data/phi1348/abo014/phi1348.abo014.perseus-lat2.xml` | Failing  |

*[Hook UI build recap](http://ci.perseids.org/repo/PerseusDL/canonical-latinLit/4364)*


Wystarczy if (!flagReason)


I wasn't able to retrieve PDD puzzles from the code base and submit them to GitHub. If you think that it's a bug on our side, please submit it to [yegor256/0pdd](https://github.com/yegor256/0pdd/issues):

> no implicit conversion of String into Integer

Please, copy and paste this stack trace to GitHub:

```
TypeError
no implicit conversion of String into Integer
/app/objects/job.rb:39:in `dig'
/app/objects/job.rb:39:in `proceed'
/app/objects/job_starred.rb:33:in `proceed'
/app/objects/job_recorded.rb:32:in `proceed'
/app/objects/job_emailed.rb:35:in `proceed'
/app/objects/job_commiterrors.rb:36:in `proceed'
/app/objects/job_detached.rb:48:in `exclusive'
/app/objects/job_detached.rb:36:in `block in proceed'
/app/objects/job_detached.rb:36:in `fork'
/app/objects/job_detached.rb:36:in `proceed'
/app/0pdd.rb:342:in `block in <top (required)>'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1634:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1634:in `block in compile!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:992:in `block (3 levels) in route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1011:in `route_eval'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:992:in `block (2 levels) in route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1039:in `block in process_route'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1037:in `catch'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1037:in `process_route'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:990:in `block in route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:989:in `each'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:989:in `route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1096:in `block in dispatch!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1075:in `block in invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1075:in `catch'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1075:in `invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1093:in `dispatch!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:924:in `block in call!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1075:in `block in invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1075:in `catch'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1075:in `invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:924:in `call!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:913:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.1/lib/rack/protection/xss_header.rb:18:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.1/lib/rack/protection/path_traversal.rb:16:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.1/lib/rack/protection/json_csrf.rb:26:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.1/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.1/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.1/lib/rack/protection/frame_options.rb:31:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.5/lib/rack/logger.rb:15:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.5/lib/rack/common_logger.rb:33:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:231:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:224:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.5/lib/rack/head.rb:12:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.5/lib/rack/method_override.rb:22:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:194:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1957:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1501:in `block in call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1728:in `synchronize'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1501:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.5/lib/rack/handler/webrick.rb:86:in `service'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/webrick/httpserver.rb:140:in `service'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/webrick/httpserver.rb:96:in `run'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/webrick/server.rb:296:in `block in start_thread'
```


lets rename 'General approach'  -> 'General'

@sankerust help us with names ;)


Now url also added in card view. Working !
Task Pending :  Glide Is left to be added.


You can go nuts and add `function changeOwner(address newOwner) public onlyOwner returns(bool success) {`


maybe we can make somethng better that that


Can you see how it would be possible to remove this hash when you use hashes to file the structs in the mapping? One would need the "secret" to even find it ...


Who seriously did this?


We don't for "." either. We can look at other heuristics for Future if people are interested.


or do you think we should retire least used entires when cache reaches certain size?


Using `constant` here looks strange to me.


Tu nie będzie pasować porównanie data.error ze zmienną tooManyReportError?


I cannot get pip to install the egg for the life of me!

Win7 64 bit python 3.6.  Is this even supported?  I'm also having lots of trouble trying to build the egg due to .net 46 being installed... can anyone help me?  i've attempted every .whl file you have and no matter what i always get "Requirement 'pyrfc-1.9.7-cp36-cp36m-win_amd64.whl' looks like a filename, but the file does not exist
pyrfc-1.9.7-cp36-cp36m-win_amd64.whl is not a supported wheel on this platform.
"
please help!


Ah, TIL :) thanks!


textContent zamiast innerHTML


There's that redundancy. You're using this as the key in the mapping, so you can save some gas and not store it again.


Oops! Meant to say this repository: https://github.com/projectEndings/html_diagnostics


@WaxCylinderRevival  Did so and done in 1873v1p2! Am I going to introduce conflicts if I attempt to commit it now? If so I'll pull your changes in first and try to reconcile them on my end.


Hey, sounds like a fun thing, you can join the support server and we'll try to help you


Looks good!


The difference is that Envelope returns a IGeometry and BoundingBox returns a BoundingBox. The implementation of Envelope uses the BoundingBox to create the Geometry. From a BoundingBox it easy to get the min and max values an for Geometries it is not clear what is the easiest way to determine that.


I could roll back my changes on that volume, if you want.  Let me try that before you commit...


lgtm


`transfer` _must_ be the last thing you do. You have important state changes _after_ this surrender of flow control and that makes the function vulnerable to re-entrance attack. It goes:

1. Optimistic accounting - get the state in order.
2. Transfer (or call or send) to an untrusted contract. Check the result.
3. If the result is "failed" then revert the state changes.

`transfer` does step 2 and 3 in one move.


Маладца хорошо зделал


Hey @akre54, I think you didn't update the npm package with this fix, did you?


Created multidev environment [sfgov#ci-371](https://dashboard.pantheon.io/sites/91d50373-c4cf-40e4-a646-cb73e16a140c#ci-371).

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


Changing the other behavior is more likely to introduce other issues. Thinking of things like `C:\` to `D:`. Which I also see that I don't have a specific test for. :)  Adding that one.


Okay, I reverted the commit.  Fingers crossed!


@motecshine This was backported down to 7.1.19. It missed 7.2 RC by a day so it should be available in 7.1.19 + 7.2.8 + 7.3.0.


It looked like you have an "i = 0;" line in the "-g o" processing (which otherwise only differs from this by saving the preferences file), to solve something with argument ordering, does it belong in this new mode also?


^ @vak2ve


Nope. Haven't yet. If I don't get to it by next week feel free to bug me again. Otherwise point your commit to a git hash in the meantime


If you look at how other open source frameworks are developed, there is a second folder which houses all of the test assertions that will eventually get run automatically. Is that what you mean?


Catsmart


`msg.sender.transfer` is a classic error. This function relies on no one other than the intended recipient knowing the passwords ahead of time, right?

After someone sends this transaction, the payload will be on the blockchain, so everyone will be able to see the solution, right? This makes a fairly obvious problem. You need to take a step to ensure no one uses the same password again, in case Alice isn't very disciplined. If a previously seen hash appears, then anyone will be able to figure out the "solution" to the "puzzle".

Then, bad things can happen, because `msg.sender` could be anyone and they will get the money if they know the password. See it?

It gets worse.

Can you think of why everyone will know the password before the first time it's used in a mined transaction? Suppose that's true (it is), then doesn't that mean anyone can come along and take the money? Yes, they can.

I don't want to give away the whole game. Ping me back if you're stumped.


Czy kod w tym bloku IF nie robi tego samego, oprócz wstawienia innego tekstu, co kod w bloku z linii 52? Jeśli tak, to lepiej owinąć go w funkcję, do której parametrem prześlesz tekst do wstawienia i tą funkcję wywołać tu i w bloku z linii 52.


yep! thats the one.


>I think we need a expand builtin that safely evaluates the expansion of an argument without having to resort to a potentially dangerous eval call.

Yes, we do. See #751.


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/16a0231c-3073-4ed9-b377-d9fb2b41675d?env_id=ibm%3Ayp%3Aus-south "vince-tc-20180614"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/b17bc381-bc2c-4b97-9719-6c2c10e4a6e7?env_id=ibm%3Ayp%3Aus-south "sample-vince-tc-20180614") deployed [sample-vince-tc-20180614](https://github.com/vgonzalesmu/sample-vince-tc-20180614/releases/tag/deploy-ibm-yp-us-south-vgonzal-us.ibm.com-test-20180614-203954 "deploy-ibm-yp-us-south-vgonzal-us.ibm.com-test-20180614-203954") to [test](https://console.bluemix.net/apps/47dbe932-81ee-49f9-9d95-6fb9b32e13a3?env_id=ibm:yp:us-south "ibm:yp:us-south:vgonzal@us.ibm.com:test"), including this commit


Sure, check removeServicesFlag introduced on https://github.com/OpenPLi/enigma2/commit/67eb1a2ac67abfc0e7c450faf2154488adcea266

We can use eDVBDB.getInstance().removeServicesFlag(...)  before starting EPG import in order to reset flag no EIT.


@P013onEr Most people in the issues section change to that model to be able to boot or install the OS, there aren't any effects


Looks good to me!


This can be `pure` because it doesn't need to access the blockchain. That can be very useful.

In case you haven't faced it yet, you might have some trouble getting clients to calculate a hash the same way the contract does. Further, we have no way of knowing it will always be convenient to do that in the future. A read-only contract function can give clients a way to fetch it quite easily, with assurance they are computing keys the same way the compiled contract does it.


To jest stary fragment kodu - był jeszcze jeden nowszy commit - facade, gdzie to już zostało poprawione. Cała sekcja clean up była zastąpiona @Transactional.


I much prefer a stoppable or pausable pattern over selfdestruct. You would put a modifier on state-changing functions, `onlyIfRunning`. It's far better to throw an error and return the money instead of creating a sinkhole that just swallows funds.


I wasn't able to retrieve PDD puzzles from the code base and submit them to GitHub. If you think that it's a bug on our side, please submit it to [yegor256/0pdd](https://github.com/yegor256/0pdd/issues):

> no implicit conversion of String into Integer

Please, copy and paste this stack trace to GitHub:

```
TypeError
no implicit conversion of String into Integer
/app/objects/job.rb:39:in `dig'
/app/objects/job.rb:39:in `proceed'
/app/objects/job_starred.rb:33:in `proceed'
/app/objects/job_recorded.rb:32:in `proceed'
/app/objects/job_emailed.rb:35:in `proceed'
/app/objects/job_commiterrors.rb:36:in `proceed'
/app/objects/job_detached.rb:48:in `exclusive'
/app/objects/job_detached.rb:36:in `block in proceed'
/app/objects/job_detached.rb:36:in `fork'
/app/objects/job_detached.rb:36:in `proceed'
/app/0pdd.rb:342:in `block in <top (required)>'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1634:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1634:in `block in compile!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:992:in `block (3 levels) in route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1011:in `route_eval'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:992:in `block (2 levels) in route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1039:in `block in process_route'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1037:in `catch'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1037:in `process_route'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:990:in `block in route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:989:in `each'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:989:in `route!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1096:in `block in dispatch!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1075:in `block in invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1075:in `catch'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1075:in `invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1093:in `dispatch!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:924:in `block in call!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1075:in `block in invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1075:in `catch'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1075:in `invoke'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:924:in `call!'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:913:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.1/lib/rack/protection/xss_header.rb:18:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.1/lib/rack/protection/path_traversal.rb:16:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.1/lib/rack/protection/json_csrf.rb:26:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.1/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.1/lib/rack/protection/base.rb:50:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-protection-2.0.1/lib/rack/protection/frame_options.rb:31:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.5/lib/rack/logger.rb:15:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.5/lib/rack/common_logger.rb:33:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:231:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:224:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.5/lib/rack/head.rb:12:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.5/lib/rack/method_override.rb:22:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:194:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1957:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1501:in `block in call'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1728:in `synchronize'
/app/vendor/bundle/ruby/2.3.0/gems/sinatra-2.0.1/lib/sinatra/base.rb:1501:in `call'
/app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.5/lib/rack/handler/webrick.rb:86:in `service'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/webrick/httpserver.rb:140:in `service'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/webrick/httpserver.rb:96:in `run'
/app/vendor/ruby-2.3.3/lib/ruby/2.3.0/webrick/server.rb:296:in `block in start_thread'
```


Chyba analogiczny przypadek co w blokach #52 i #80 - wywołać funkcję z przekazaniem tekstu jako parametr.


Screw it. Published


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/16a0231c-3073-4ed9-b377-d9fb2b41675d?env_id=ibm%3Ayp%3Aus-south "vince-tc-20180614"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/b17bc381-bc2c-4b97-9719-6c2c10e4a6e7?env_id=ibm%3Ayp%3Aus-south "sample-vince-tc-20180614") deployed [sample-vince-tc-20180614](https://github.com/vgonzalesmu/sample-vince-tc-20180614/releases/tag/deploy-ibm-yp-us-south-vgonzal-us.ibm.com-prod-20180614-204315 "deploy-ibm-yp-us-south-vgonzal-us.ibm.com-prod-20180614-204315") to [prod](https://console.bluemix.net/apps/0a25568a-adb6-4975-b7ef-d20f8f74d3b7?env_id=ibm:yp:us-south "ibm:yp:us-south:vgonzal@us.ibm.com:prod"), including this commit


There are issues in some systems with that commit, reverting until I can troubleshoot and fix.


Created multidev environment [riveralive-cms#pr-11](https://dashboard.pantheon.io/sites/ced938b0-bbbf-4ed2-ba1c-98b66d8ba2be#pr-11).

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


@joshtynjala I will make the adjustment to the code completion list tomorrow morning my time. We have prefixes from you so my custom code is no longer needed.


OK, there's a new BEAGLE v3.0.2 installer that should work for both BEAST v1.8.4 and BEAST v1.10.0. It copies `libhmsbeagle-jni.jnilib` to both `/usr/local/lib` and `/Library/Java/Extensions`. I haven't had the macOS warning issue any longer so it should work fine for everyone.


Puzzle `2-e5e616d7` disappeared from [`.circleci/config.yml`](https://github.com/DronMDF/zold-lazy-node/blob/master/.circleci/config.yml), that's why I closed #12. Please, remember that the puzzle was not necessarily removed in this particular commit. Maybe it happened earlier, but we discovered this fact only now.


Puzzle `12-5eb5fcd6` discovered in   [`.circleci/config.yml`](  https://github.com/DronMDF/zold-lazy-node/blob/master/.circleci/config.yml)   and submitted as #14. Please, remember that the puzzle was not   necessarily added in this particular commit. Maybe it was added earlier, but   we discovered it only now.


Puzzle `12-991eb218` discovered in   [`.circleci/config.yml`](  https://github.com/DronMDF/zold-lazy-node/blob/master/.circleci/config.yml)   and submitted as #15. Please, remember that the puzzle was not   necessarily added in this particular commit. Maybe it was added earlier, but   we discovered it only now.


The best solution here I can come up with is to transform it into `a|b|c 1|2|3`, do a `while read -l -d' ' first second`, append both (split on pipes) to different lists and then after the while-loop (in case this can ever be more than one line) do `printf '%s\n' $prefix$suffix`.

Not beautiful, but it should get the job done and still be better than eval.


I believe this needs an  wxOVERRIDE


Hi @srikanth1620 if you have any issue please open an "issue" in the related section with some additional details


Or the return of the sexagesimal system.


thanks for rise this issue:
it's my mistake:

@@ -8,7 +8,7 @@ import {
	GET_ONE,
	UPDATE
} from "ra-core/lib/dataFetchActions";

import { stringify } from "query-string";
/**
 * Maps react-admin queries to a postgrest API
 *

i will fix and clean up soon.


Would it make sense to add a unit test for Topics (in addition to Queues) just in case there is something different internally with how Topics work?


There's a work-around for the text.  Are you sure about serialization when the model is present?  I get
```
[info] TestSerialization:
[info] Standard Serializer
[info] - should serialize and deserialize mentions *** FAILED ***
[info]   java.io.NotSerializableException: org.clulab.timenorm.field.UNSPECIFIED$
[info]   at java.io.ObjectOutputStream.writeObject0(Unknown Source)
[info]   at java.io.ObjectOutputStream.defaultWriteFields(Unknown Source)
[info]   at java.io.ObjectOutputStream.writeSerialData(Unknown Source)
[info]   at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source)
[info]   at java.io.ObjectOutputStream.writeObject0(Unknown Source)
[info]   at java.io.ObjectOutputStream.defaultWriteFields(Unknown Source)
[info]   at java.io.ObjectOutputStream.writeSerialData(Unknown Source)
[info]   at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source)
[info]   at java.io.ObjectOutputStream.writeObject0(Unknown Source)
[info]   at java.io.ObjectOutputStream.defaultWriteFields(Unknown Source)
```


@longbinzhang I saw your [posts](https://github.com/AnyBody/support/wiki/error) on the wiki site. Please use the [anyscript forum](http://forum.anyscript.org) for support questions.

I believe the problem you reported was regarding the old ManMachine demo model from the old webcast. Is that correct? The model was not compatible with the newest model repository. I have [uploaded a new version](https://github.com/AnyBody/support/wiki/Example-from-the-Man-Machine-webcast) to the wiki which does work. Just keep in mind that the demo is good for learning AnyBody concepts, but it is not the best example to start your own model.


Yeah, you're absolutely right, Michael. I'm just basically replacing every date with a script for this :-)


On 06/14/2018 03:48 PM, Deyan Ginev wrote:
> It helps even i

Jeez, can't get away with anything around here....


Watch your language. :-)


Sox moet er in de toekomst helemaal uit!


That works for me, thanks. I hadn't notice this before as I still had BEAGLE 2 installed on my Macs.


Why are we changing every email and adding all of this to vagrant?


You call that an improvement? :-P


Created multidev environment [rail-uga-stellar#pr-12](https://dashboard.pantheon.io/sites/05f5afa3-c1ec-448f-915a-9234103f2409#pr-12).

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


saver is supposed to be initiated before training, so I will include it in Network.train()


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/16a0231c-3073-4ed9-b377-d9fb2b41675d?env_id=ibm%3Ayp%3Aus-south "vince-tc-20180614"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/b17bc381-bc2c-4b97-9719-6c2c10e4a6e7?env_id=ibm%3Ayp%3Aus-south "sample-vince-tc-20180614") deployed [sample-vince-tc-20180614](https://github.com/vgonzalesmu/sample-vince-tc-20180614/releases/tag/deploy-ibm-yp-us-south-vgonzal-us.ibm.com-test-20180614-205218 "deploy-ibm-yp-us-south-vgonzal-us.ibm.com-test-20180614-205218") to [test](https://console.bluemix.net/apps/4b661bab-7da4-4ec1-b668-2de606bc7603?env_id=ibm:yp:us-south "ibm:yp:us-south:vgonzal@us.ibm.com:test"), including this commit


No, depending on asciidoctor just to build the man page is not worth it.

The man page is tracked in the git repo in troff/groff/gnurf/blorf/Idontknow
format. I just have to build and commit it whenever something's changed.


I guess we missed the gateway filter spec


Okay I will join. give me the link of your server.
I know you will able to run it.
Lets see


there are ubuntu only commands in the 002 script


The results of the _config.yaml_ looks like this in the end:
```bash
http_proxy: http://10.0.2.104:3128
https_proxy: http://10.0.2.104:3128
no_proxy: # YAML
 - 10.0.7.135
 - 10.0.7.83
 - 10.0.6.127
```


This should be a static const to avoid memory allocation every time.


Created multidev environment [ooc-site#ci-4](https://dashboard.pantheon.io/sites/8bb80151-8cc0-4e15-809a-b702e6d46ef7#ci-4).

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


Changement de la clé name


Thanks, well spotted. :)

I've committed and tested a change.

On 14 Jun 2018, 9:11 pm, at 9:11 pm, Messminotaur <notifications@github.com> wrote:
>Is it ever possible get false out of this expression?
>
>--
>You are receiving this because you authored the thread.
>Reply to this email directly or view it on GitHub:
>https://github.com/orderoftheflame/volumio-plugins/commit/1f49cd62fe5c3ed4359149185ccf5d67eb0f99d0#commitcomment-29369297


I think this should be a static to avoid memory allocation every time.


its in the read.me @DuelvsDuel


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


IBM Cloud [toolchain](https://console.ng.bluemix.net/devops/toolchains/16a0231c-3073-4ed9-b377-d9fb2b41675d?env_id=ibm%3Ayp%3Aus-south "vince-tc-20180614"): [Delivery Pipeline](https://console.ng.bluemix.net/devops/pipelines/b17bc381-bc2c-4b97-9719-6c2c10e4a6e7?env_id=ibm%3Ayp%3Aus-south "sample-vince-tc-20180614") deployed [sample-vince-tc-20180614](https://github.com/vgonzalesmu/sample-vince-tc-20180614/releases/tag/deploy-ibm-yp-us-south-vgonzal-us.ibm.com-prod-20180614-205539 "deploy-ibm-yp-us-south-vgonzal-us.ibm.com-prod-20180614-205539") to [prod](https://console.bluemix.net/apps/172ce956-1074-4686-a55b-d008cf769b90?env_id=ibm:yp:us-south "ibm:yp:us-south:vgonzal@us.ibm.com:prod"), including this commit


@WaxCylinderRevival Success with the commit :)

There are still more errors remaining than usual because of the irregular nature of this volume, but I did the best I could with it! Hopefully there isn't too much work for you to do/redo on it. I'd love to hear any feedback you might have when you get back!


เปิด


The `string[] format` should be a static to avoid memory allocation every time the method is called.  Which can be a lot because it's a JsonConverter


![](https://github.trello.services/images/mini-trello-icon.png) [Stress teszt -](https://trello.com/c/Rej66a9x/10-stress-teszt)


This should not be committed. Please remove the comment slashes.


Please move the packe as import to the top.


Looks good.


Created multidev environment [riveralive-cms#pr-11](https://dashboard.pantheon.io/sites/ced938b0-bbbf-4ed2-ba1c-98b66d8ba2be#pr-11).

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


TeamCity Architecture Team :: Java Platform :: otj-filterorder :: BuildTest [Build 28](https://teamcity.otenv.com/viewLog.html?buildId=8740561&buildTypeId=ArchitectureTeam_JavaPlatform_OtjFilterorder_BuildTest) is now running


TeamCity Architecture Team :: Java Platform :: otj-filterorder :: BuildTest [Build 29](https://teamcity.otenv.com/viewLog.html?buildId=8740562&buildTypeId=ArchitectureTeam_JavaPlatform_OtjFilterorder_BuildTest) is now running


TeamCity Architecture Team :: Java Platform :: otj-filterorder :: BuildTest [Build 29](https://teamcity.otenv.com/viewLog.html?buildId=8740562&buildTypeId=ArchitectureTeam_JavaPlatform_OtjFilterorder_BuildTest) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:03


original commits is needed


Everything I introduced is between our #ifdef guards


TeamCity Architecture Team :: Java Platform :: otj-filterorder :: BuildTest [Build 28](https://teamcity.otenv.com/viewLog.html?buildId=8740561&buildTypeId=ArchitectureTeam_JavaPlatform_OtjFilterorder_BuildTest) outcome was **SUCCESS**
Summary: Tests passed: 7 Build time: 00:00:46


Problem is that bytes are flushed to the wire - I am sure that i construct wrong reqeust :/ I am working on run local SMF server (docker).


pull request review


I introduced a new file because all consistency levels use the same counting algorithm.


I use std::vectors for managing scoped data structures. I mention it because I never saw a std::vector in Gecode. Maybe I should use the Heap allocator with my vectors or replace them?


TeamCity Architecture Team :: Java Platform :: otj-kafka :: BuildTest [Build 171](https://teamcity.otenv.com/viewLog.html?buildId=8740595&buildTypeId=ArchitectureTeam_JavaPlatform_OtjKafka_BuildTest) is now running


TeamCity Architecture Team :: Java Platform :: otj-kafka :: BuildTest [Build 171](https://teamcity.otenv.com/viewLog.html?buildId=8740595&buildTypeId=ArchitectureTeam_JavaPlatform_OtjKafka_BuildTest) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:00:03


TeamCity Architecture Team :: Java Platform :: otj-kafka :: BuildTest [Build 172](https://teamcity.otenv.com/viewLog.html?buildId=8740596&buildTypeId=ArchitectureTeam_JavaPlatform_OtjKafka_BuildTest) is now running


Can we start a discussion about this? Should this really be enabled by default? Preventing programs from having persistent cache directories overall has many negative impacts.

- Most email clients cache emails to allow various functionality and downloading them can take many minutes
- Caching makes webpages load faster
- Most music players cache album art from libraries
- Mapping programs (gnome-maps, viking) don't need to constantly redownload tiles
- Mesa shader cache improves graphics load performance
- General waste of bandwith of clients/servers
- General increase in recomputing things
- General potential increase in disk I/O


TeamCity Architecture Team :: Java Platform :: otj-kafka :: BuildTest [Build 172](https://teamcity.otenv.com/viewLog.html?buildId=8740596&buildTypeId=ArchitectureTeam_JavaPlatform_OtjKafka_BuildTest) outcome was **FAILURE**
Summary: Exit code 1 Build time: 00:00:04


This surprisingly works:

```fish
~> # set -l tokens (service smartd -v 2>| string match -r '\[(.*)\]\((.*)\)' | string replace -a '|' ',')
~> set -l tokens (echo "Usage: /usr/local/etc/rc.d/smartd [fast|force|one|quiet](start|stop|restart|rcvar|enabled|describe|extracommands|reload|report|status|poll)" | string match -r '\[(.*)\]\((.*)\)' | string replace -a '|' ',')
~> echo {(echo $tokens[2])}{(echo $tokens[3])}
faststart forcestart onestart quietstart faststop forcestop onestop quietstop fastrestart forcerestart onerestart quietrestart fastrcvar forcercvar onercvar quietrcvar fastenabled forceenabled oneenabled quietenabled fastdescribe forcedescribe onedescribe quietdescribe fastextracommands forceextracommands oneextracommands quietextracommands fastreload forcereload onereload quietreload fastreport forcereport onereport quietreport faststatus forcestatus onestatus quietstatus fastpoll forcepoll onepoll quietpoll
```

But I think that's a bug 😂, process expansion is being evaluated _before_ brace expansion and not after, and its contents are not escaped against brace expansion. Which is a huge security risk and the reason why `eval` is such a bad idea.

Whereas this doesn't work:

```fish
~> # set -l tokens (service smartd -v 2>| string match -r '\[(.*)\]\((.*)\)' | string replace -a '|' ',')
~> set -l tokens (echo "Usage: /usr/local/etc/rc.d/smartd [fast|force|one|quiet](start|stop|restart|rcvar|enabled|describe|extracommands|reload|report|status|poll)" | string match -r '\[(.*)\]\((.*)\)' | string replace -a '|' ',')
~> echo {$tokens[2]}{$tokens[3]}
fast,force,one,quiet start,stop,restart,rcvar,enabled,describe,extracommands,reload,report,status,poll
```

Probably because the variable substitution happens after the brace expansion. Oops.


158368465-Improve-error-#6375 (lgu1234) - 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)


If variable cardinalities are too big (here above 400), we throw an exception because we didn't precompute factors above that.


wprowadzone.


wprowadzone


@mckaygerhard were you able to test? If you confirm it works I will merge. Please take some time to go through the csrf issues you reported.


Do I put you in the copyright?


Ouch!


Yes, that error solved when I changed the variable anchor in EidosDocument to "@transient lazy val anchor".  Do you have this change? Otherwise, could you paste me the full stacktrace?