Successfully deployed to following URLs:

* https://operation-code-p483jga2k.now.sh
* https://operation-code.now.sh
* https://operation-code.operation-code.now.sh
* https://operation-code-git-master.operation-code.now.sh


I mentioned it in the F2F since I didn’t remember how we had handled it.


Missing semicolon


You just cannot `app` a `Pi`. You can only `app` sth that is of type `Pi`. We should discuss this on the board what you actually want to do.


The tests are no longer able to resolve the module 'other/file'. I have tried running the actual facade generator on modules declared in different directories and it works fine.


Successfully deployed to following URLs:

* https://glot-frontend-hzkelizxu.now.sh
* https://glot.conceptualsoup.blog
* https://glot-frontend.m4thayus.now.sh
* https://glot-frontend-git-master.m4thayus.now.sh


Somehow this wording hasn't yet made it to https://emcrisostomo.github.io/fswatch/


Kendo UI and Bootstrap added with sample code


There is no 19.1.1 patch. The 19.1.1.xxx versions are reserved for Skyline-daily releases. We would not change the scheme on a patch release. So, 19.1 and patches will stay with the 19.1 schema and 19.11, 19.12, 19.13... will be used for Skyline-daily schema changes.


Here you go, the secret weapon 🔫

```yaml
  - |
    sed -e 's#^function is_countable(#// &#' -i vendor/giacocorsiglia/wordpress-stubs/wordpress-stubs.php
```


Successfully deployed to following URLs:

* https://spotify-b6i1yjgyh.now.sh
* https://spotify-demo.now.sh
* https://spotify.walterzalazarmdp.now.sh
* https://spotify-git-master.walterzalazarmdp.now.sh


Successfully deployed to following URLs:

* https://jwlcloud-h87tir731.now.sh
* https://jwl.cloud
* https://www.jwl.cloud
* https://jwlcloud.jameswlane.now.sh
* https://jwlcloud-git-master.jameswlane.now.sh


@JuliaRegistrator register


Registration pull request created: [JuliaRegistries/General/3769](https://github.com/JuliaRegistries/General/pull/3769)

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if [Julia TagBot](https://github.com/apps/julia-tagbot) is installed, or can be done manually through the github interface, or via:
```
git tag -a v0.6.0 -m "<description of version>" 216c13037d880d9d11ed5c04dcce02dad29b9ce4
git push origin v0.6.0
```


Successfully deployed to following URLs:

* https://tji-nextjs-oljxp6h0g.now.sh
* https://tji-nextjs.now.sh
* https://tji-nextjs.evaruth.now.sh
* https://tji-nextjs-git-master.evaruth.now.sh


It is possible that I misunderstood this.  For me *myArray is the same as if I would write myArray[0].  I see it now why this doesn't work the way it's supposed to. It will only find the last number which is bigger than the first and not the highest number.


Thank you


Good


Hi Miracle

I'm not sure why we have this action - please explain it to me.
Thanks


Actually sounds like a good idea to ensure correctness. If previous commands fail, this should prevent issues.


Обнуление параметров намеренно вернул или случайно?


Successfully deployed to following URLs:

* https://cmsclubs-lm5wgghbq.now.sh
* https://utsccms.club
* https://www.utsccms.club
* https://cmsclubs.csec.now.sh
* https://cmsclubs-git-master.csec.now.sh


What is the version of the 19.1 patch going to be?


TRestsdlwd ealf aeof;ofqd


sorry all, this was to fix a mistake I made in the previous commit


Yes.  The USB-C plug is connected to an FTDI chip which is connected to the Tx/Rx of the board.  That's the "normal" way of talking to it.  The USB-C connection also provides the power.

The micro-usb on the left side is for the direct USB connections.  You need to put the Bee in bypass *and* enable direct USB and then flip the USB direct dip-switches to the left to connect to USB direct.  I thought there were directions as such in that zip.

Note:  you must keep the USB-C plug connected while using the micro-USB or the thing won't have power.


Deployment failed with the following error:

~~~
You defined 1 build that did not match any source files (please ensure they are NOT defined in .nowignore):
~~~


Would be good to add this to the other workshop repo as well. Note: haven’t checked to see if you have added it there as well 😄


Was the comment-in of this line on purpose?


Successfully deployed to following URLs:

* https://jwlcloud-8eriddms0.now.sh
* https://jwl.cloud
* https://www.jwl.cloud
* https://jwlcloud.jameswlane.now.sh
* https://jwlcloud-git-master.jameswlane.now.sh


Successfully deployed to following URLs:

* https://website-fel3egp1h.now.sh
* https://mikemcbride.me
* https://website.mcbridem.now.sh
* https://website-git-master.mcbridem.now.sh


Successfully deployed to following URLs:

* https://bot-ionic-rcee2fmbe.now.sh
* https://bot-ionic.alexanderendon.now.sh
* https://bot-ionic-git-master.alexanderendon.now.sh


19.1.0.xxx where xxx is the day number of the final commit on the skyline_19_1 branch before the patch is built. Like 19.1.0.266 if that were today.


.    It’s an isolated room for babies which has sensors to sense the level of temperature and humidity continuously and display it on 7-segment displays, the system compares the measured values with default values which are also displayed on 7-segment displays so that the user can change it by pressing push buttons. When the measured values exceed the default values by a fixed percent, the system turns on a fan, buzzer or heater depending on the state.


Successfully deployed to following URLs:

* https://experimentwithcom-3v03b433y.now.sh
* https://experimentwith.com
* https://www.experimentwith.com
* https://experimentwithcom.jameswlane.now.sh
* https://experimentwithcom-git-master.jameswlane.now.sh


Successfully deployed to following URLs:

* https://cmsclubs-jch9upk1d.now.sh
* https://utsccms.club
* https://www.utsccms.club
* https://cmsclubs.csec.now.sh
* https://cmsclubs-git-master.csec.now.sh


Thinking about this a bit more, I'd like to remove `uom_type_id` from the form altogether.
Rather move the `default_uom_type_id` method to the repo.

Then in the interactor's create method, do something like:
```ruby
res.to_h.merge(uom_type_id: repo.default_uom_type_id)
```
That way it's a bit more explicit and we remove any unnecessary reference to the type from the UI.


So the third number is always 0 or 1?


Successfully deployed to following URLs:

* https://operation-code-mfp86ive1.now.sh
* https://operation-code.now.sh
* https://operation-code.operation-code.now.sh
* https://operation-code-git-master.operation-code.now.sh


Yeah, added


test text


I had forked with the code and ended up getting rid of lines 4 - 6 and instead added:

`input_file =r'C:\Users\bmevans\Downloads\Takeout\Location History\Location History.json' #in python IDE, use print os.path.abspath()
output_file =r'C:\Users\bmevans\Desktop\output.csv' #Place your own absolute path here for output, I put it in my desktop
`

 This was giving me a unicode error so I put 'r' before inputting the proper paths for both the input and output file paths. While I didn't do much to change the code (only making it easier for me to compile it) this code returns an empty .csv file. How can I go about changing that?


Hmmm... I guess my shortening of the final number to 3 digits implies that I will need to use day number + 365 when releasing a patch for last year's release. E.g. if we were to release a patch for 19.1 on January 18, that would need to be 19.1.0.383. Still plenty of room to stay 3 digits without ever running into a desire to patch, say a 3-year-old release.


la tecnologia que estoy utilizando es el MVC5 y los datos extraídos a las tablas responsivas  vienen de una base de datos SQL server.


And I should merge the 19.12 schema in this PR into the 19.11 file? And schema 19.2 will be more recent than 19.11, 19.12, 19.13, etc? (that last bit is quite confusing if true)


Successfully deployed to following URLs:

* https://alepachecodev-9ijt1xdjc.now.sh
* https://www.alepacheco.dev
* https://alepachecodev.alepacheco.now.sh
* https://alepachecodev-git-master.alepacheco.now.sh


The 3rd number is always 0 for a major release. It is 1 during ongoing development and changes to 9 once we are feature complete. So, normally just 3 states 0, 1, and 9.


Thanks for sharing.

I had the same with LTE-M modems I purchased from Digikey last week.

For 11413 it no longer supports bypass mode. -release note http://ftp1.digi.com/support/firmware/release_notes/xbee3_cell_ltem_att/93001302_G.pdf

I haven't upgraded to A.0.04, hope to be testing with it later this week - release notes are here.
https://www.u-blox.com/sites/default/files/SARA-R410M-02B-01_PCN_%28UBX-19024506%29.pdf

General XBee3 release info at
https://www.digi.com/support/productdetail?pid=5635&type=firmware
Seems there is now an upgrade for the App direct with firmware 11413 (ie without XBIB-CU-TH) - see  "u-blox Over the Wire Update Script"

There is a new  2019Sept Rev L version of the XBee3 manual
https://www.digi.com/resources/documentation/digidocs/PDFs/90002258.pdf
PdfPg28 describes a new way of updating App from firmware 11413 - but probably takes longer than EasyFlash (I'll try it later)


Copy of this build can be found at
https://www.mewbuilds.com/build/b0e50b9fb7674901e02d955a5bc6d64f46d18c41/index.html
                       https://www.cloudflare-ipfs.com/ipfs/QmVHoj25QjVFQotATPmZZ5Fh7zaddw1TWiqCDKkHAzCrp4
                       Virus Total analysis
                       https://www.virustotal.com/file/d15a795f3b4ed2b221c7a12de28e3d9e89c237dcc69f6a82a4e333d6d33d4561/analysis/1569258292/


To make sure the `schema.rb` gets updated with the newest schema, after this extra change, you can run the following locally:

```shell
rails db:migrate:redo && RAILS_ENV=test rails:db:migrate:redo
```


Successfully deployed to following URLs:

* https://backend-6utckehb1.now.sh
* https://backend.art-portfolio.now.sh
* https://backend-git-master.art-portfolio.now.sh


I've bumped version to 1.3.1


Successfully deployed to following URLs:

* https://bot-ionic-l9lfkhjua.now.sh
* https://bot-ionic.alexanderendon.now.sh
* https://bot-ionic-git-master.alexanderendon.now.sh


Successfully deployed to following URLs:

* https://cast-bucket-api-e1tp2qhnt.now.sh
* https://cast-bucket-api.cast-bucket-api-team1.now.sh
* https://cast-bucket-api-git-master.cast-bucket-api-team1.now.sh


Successfully deployed to following URLs:

* https://sirena-project-3sqo7sh9f.now.sh
* https://sirena-project.juanpernu.now.sh
* https://sirena-project-git-master.juanpernu.now.sh


Successfully deployed to following URLs:

* https://phase-ten-scorer-nextjs-qbrta0oo1.now.sh
* https://phase-ten-scorer-nextjs.barrymay.now.sh
* https://phase-ten-scorer-nextjs-git-master.barrymay.now.sh


Successfully deployed to following URLs:

* https://jestexpress-ftxkhq2dq.now.sh
* https://jest.express
* https://www.jest.express
* https://jestexpress.jameswlane.now.sh
* https://jestexpress-git-master.jameswlane.now.sh


Looks good. I built my multi clock 7series project with it and all was fine.

I've merged it with my #227 pull request and made the required changes there.


(Note also that after pushing this schema change to GitHub, and having the Heroku review app get updated, you'll need to run the above commands on the review app too, so it can use the updated schema).


Thank you. Yes, I've reading the instructions that are included, which have helped clarify a good bit in the last half hour. I've also found helpful directions on USB Direct here: https://www.digi.com/resources/documentation/Digidocs/90002258/#Concepts/c_mode_usb_direct_lte-m.htm

Part of my question is related to whether I can use XBIB-U-Dev RevF board that came with my XK3-C-A2-UT-U Development Kit (https://www.digi.com/products/models/xk3-c-a2-ut-u).
It doesn’t look the same as https://www.digi.com/products/models/xbib-cu-th, such as not having a USB-C port, etc. I think it should also work, from what I can tell, but I just reached out to Digi to ask. I'll report on what I discover.

The sequence of entering these commands all sounds quite complicated and I'm wondering how much it might be worth it or not for the 12 LTE-M modules on my desk.


Yes. 19.2 will go with the 19.2 release. Why confusing? Maybe you are thinking of this something other than a decimal number where 19.2 is bigger than 19.11, 19.12, etc. If we got all the way to 19.19 before we were ready to go to 19.2, we would need to start using 19.191, 19.192, etc. But that seems pretty unlikely.

To be clear 19.11 is not trying to stand in for 19.1.1. It is not a series of 3 integers, but a decimal number which is monotonically increasing with a relatively stable pattern.


nmnm


Successfully deployed to following URLs:

* https://jwlcloud-b5rezruoq.now.sh
* https://jwl.cloud
* https://www.jwl.cloud
* https://jwlcloud.jameswlane.now.sh
* https://jwlcloud-git-master.jameswlane.now.sh


Successfully deployed to following URLs:

* https://pikbet-7a26jsdw2.now.sh
* https://pikbet.ru
* https://pikbet.vitaliks1.now.sh
* https://pikbet-git-master.vitaliks1.now.sh


Agreed. After some changes I made we should do this now in `src/model/grammar/grammarRules.ts`, and there we can define whatever syntaxes we need for each operation


Now I've had some time to look at this...

> I'm not sure how this is better. Ignoring ./build means we ignore the top-level build directory.

No, and you didn't test this on your system, because if you had you'd know you're wrong.  The build directory isn't ignored at all.  `.` doesn't have the same meaning as it does in normal paths, it means a literal '.'. So your `.gitignore` rule failed to match the build directory.

> Ignoring build/* means we ignore any filename which matches the regex build/*. i.e. the files in scripts/build/.

No. It doesn't. It means ignore the build directory and anything contained within it.  The '*' is actually redundant.  Just ignoring the directory with `build/` is enough.  To get the behaviour you're describing you'd need `**/build`.

If you create an _empty_ build directory somewhere else in the repo it won't show up in `git status` which I'm guessing is what you saw.

> Which is why I changed the ignore rule from build to ./build.

Preventing it from matching the build directory.


[inst/examples/example-slicer.R:8:1:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/inst/examples/example-slicer.R#L8) *style:* **Variable and function name style should be camelCase.**
```r
DT <- reactive({
^~
```
[R/generator.R:103:4:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/generator.R#L103) *style:* **Commented code should be removed.**
```r
  #ns <- NS(id)
   ^~~~~~~~~~~~
```
[R/generator.R:107:4:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/generator.R#L107) *style:* **Commented code should be removed.**
```r
  #tabContent <- paste0(module$name, "UI(\"", ns(module$id), "\"", parameters, ")")
   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/generator.R:205:4:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/generator.R#L205) *style:* **Commented code should be removed.**
```r
  #ns <- NS(id)
   ^~~~~~~~~~~~
```
[R/generator.R:209:4:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/generator.R#L209) *style:* **Commented code should be removed.**
```r
  #callModuleDirective <- paste0("callModule(", name, ", \"", ns(id), "\"", renderedParameters, ")")
   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/histogramForRaster.R:76:9:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/histogramForRaster.R#L76) *style:* **Commented code should be removed.**
```r
    #   numeric()
        ^~~~~~~~~
```
[R/histogramForRaster.R:78:9:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/histogramForRaster.R#L78) *style:* **Commented code should be removed.**
```r
    #   ras[]
        ^~~~~
```
[R/pkgInfo.R:46:8:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/pkgInfo.R#L46) *style:* **`%>%` should always have a space before it and a new line after it, unless the full pipeline fits on one line.**
```r
  }) %>% unlist()
     ~~^
```
[R/polygonList.R:26:1:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/polygonList.R#L26) *style:* **Lines should not be more than 100 characters.**
```r
#' @note This is a temporary workaround until we resolve inheritance of S3 classes (see \code{.polygonList}).
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/rastersOverTime.R:132:37:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/rastersOverTime.R#L132) *style:* **Commented code should be removed.**
```r
  tilesGroup <- "Time since fire" # session$ns("tiles")
                                    ^~~~~~~~~~~~~~~~~~~
```
[R/rastersOverTime.R:139:37:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/rastersOverTime.R#L139) *style:* **Commented code should be removed.**
```r
  tilesGroup <- "Time since fire" # session$ns("tiles")
                                    ^~~~~~~~~~~~~~~~~~~
```
[R/rastersOverTime.R:150:6:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/rastersOverTime.R#L150) *style:* **Commented code should be removed.**
```r
    #grep(rasterFilename, gsub("www/", "", rctUrlTemplate()), value = TRUE)
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/rastersOverTime.R:192:6:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/rastersOverTime.R#L192) *style:* **Commented code should be removed.**
```r
    #sp1 <- SpatialPoints(t(bbox(mapBoundsAsExtent)), proj4string = CRS(proj4stringLFLT))
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/rastersOverTime.R:193:6:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/rastersOverTime.R#L193) *style:* **Commented code should be removed.**
```r
    #sp2 <- spTransform(sp1, crs(rast))
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/rastersOverTime.R:194:6:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/rastersOverTime.R#L194) *style:* **Commented code should be removed.**
```r
    #tryCatch(crop(rast, sp2), error = function(x) NULL) ## TODO: why error? why NULL?
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/rastersOverTime.R:204:7:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/rastersOverTime.R#L204) *style:* **Commented code should be removed.**
```r
    # Cache(.sampleRasterToRAM, ras)
      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/shine.R:87:1:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/shine.R#L87) *style:* **functions should have cyclomatic complexity of less than 15, this has 52.**
```r
setMethod(
^
```
[R/simOutputs.R:89:6:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/simOutputs.R#L89) *style:* **Commented code should be removed.**
```r
    #Plot(demoArea, addTo = "map") ## TO DO: use study area from inside simList
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/slicer.R:24:9:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/slicer.R#L24) *style:* **Commented code should be removed.**
```r
      # setkeyv(datatable, chosenCategories[[len]])
        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/slicer.R:26:11:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/slicer.R#L26) *style:* **Commented code should be removed.**
```r
      #   subtable <- na.omit(datatable[chosenValues[[len]]])
          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/slicer.R:134:6:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/slicer.R#L134) *style:* **Commented code should be removed.**
```r
    #assertthat::assert_that(is.data.table(datatable()))
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/slicer.R:159:7:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/slicer.R#L159) *style:* **Closing curly-braces should always be on their own line, unless it's followed by an else.**
```r
      } %>% unique()
      ^
```
[R/slicer.R:165:9:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/slicer.R#L165) *style:* **Closing curly-braces should always be on their own line, unless it's followed by an else.**
```r
        } %>% unique()
        ^
```
[R/slicer.R:171:11:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/slicer.R#L171) *style:* **Closing curly-braces should always be on their own line, unless it's followed by an else.**
```r
          } %>% unique()
          ^
```
[R/slicer.R:195:6:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/slicer.R#L195) *style:* **Commented code should be removed.**
```r
    #Cache(.slicer, dtFull, categories, possibleValues, serverFunction, uiSequence, ...)
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/slicer.R:274:6:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/slicer.R#L274) *style:* **Commented code should be removed.**
```r
    #assertthat::assert_that(is.data.table(datatable()))
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/slicer.R:292:6:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/slicer.R#L292) *style:* **Commented code should be removed.**
```r
    #Cache(.slicer2, dtFull, categories, possibleValues, serverFunction, uiSequence, ...)
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/slicer.R:303:7:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/slicer.R#L303) *style:* **Closing curly-braces should always be on their own line, unless it's followed by an else.**
```r
      } %>% unique()
      ^
```
[R/slicer.R:309:9:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/slicer.R#L309) *style:* **Closing curly-braces should always be on their own line, unless it's followed by an else.**
```r
        } %>% unique()
        ^
```
[R/spades.R:19:1:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/spades.R#L19) *style:* **Variable and function name style should be camelCase.**
```r
spades_simInit <- function(input, output, session, ...) {
^~~~~~~~~~~~~~
```
[R/spades.R:52:1:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/spades.R#L52) *style:* **Variable and function name style should be camelCase.**
```r
spades_expt <- function(input, output, session, sim, reps, seed, objectsToHash,
^~~~~~~~~~~
```
[R/spades.R:57:6:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/spades.R#L57) *style:* **Commented code should be removed.**
```r
    #initialRun1 <- spades(Copy(sim), debug = TRUE)
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/uploadPolygon.R:59:1:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/uploadPolygon.R#L59) *style:* **Lines should not be more than 100 characters.**
```r
        p("Upload a shapefile by selecting .shp and its associated files (or upload a single .zip file)."),
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/uploadPolygon.R:60:1:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/uploadPolygon.R#L60) *style:* **Lines should not be more than 100 characters.**
```r
        p("Each polygon should have a \"shinyLabel\" attribute, otherwise a generic default will be used."),
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
[R/zzz.R:4:1:](https://github.com/PredictiveEcology/SpaDES.shiny/blob/c7aca246ab47cd7cae5769404a9858dbc8c5a68f/R/zzz.R#L4) *style:* **Lines should not be more than 100 characters.**
```r
  .pkgEnv$menuItemTemplatePath <- system.file(package = "SpaDES.shiny", "templates/menuItem.template")
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```


OK, let's leave it out and we look into it after 2.07 is released. It does work well here though!


CurrentEnvironment_EMSGuide_7303 (Unknown) - Win64-Windows-10-VisualStudio-16: OK (2534 of 2557 tests passed, 631 test warnings)

Messages:\n
 * 611 tests had: EIO diffs.
 * 619 tests had: ESO small diffs.
 * 7 tests had: EDD diffs.
 * 492 tests had: Table small diffs.
 * 480 tests had: MTR small diffs.
 * 26 tests had: ERR diffs.
 * 18 tests had: ESO big diffs.
 * 10 tests had: MTR big diffs.
 * 183 tests had: ZSZ small diffs.
 * 17 tests had: Table big diffs.
 * 3 tests had: AUD diffs.
 * 1 test had: MTD diffs.
 * 32 tests had: SSZ small diffs.
 * 2 tests had: JSON big diffs.

Failures:\n

regression Test Summary
 * Passed: 645
 * Failed: 23

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


Successfully deployed to following URLs:

* https://website-fq3lhfezw.now.sh
* https://mikemcbride.me
* https://website.mcbridem.now.sh
* https://website-git-master.mcbridem.now.sh


Successfully deployed to following URLs:

* https://bot-ionic-5tmlz27jn.now.sh
* https://bot-ionic.alexanderendon.now.sh
* https://bot-ionic-git-master.alexanderendon.now.sh


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 995fdbb5ba83c3e548bf123e0d38c98b0a6c9cb0.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


I commented in a previous commit in line with 'merge together et al.' since 'mesh' is included in the BLEND_TOGETHER, but that rule is disabled, so I reverted.
What are the exception to blend together?


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit ace4379ea6211604d7c9d0abd1181c0d3122c337.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


I wondering if just checking if the context info is null, and if it is, calling the original code to handle the back button push would be good enough to fix the problem


Not a bug. I have only noticed later that the rule is disabled by default. What are the exception to blend together?


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 1ca92f8eb74c0fa56890278b4a52fca941f94b7b.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


@SRGDamia1, from what I understand, as long as I have XBee-LTE-M version >11410 and Ublox version >A.02.01 then the latest release should work OK. Is that correct?

If so, what are the main benefits of upgrading beyond that?

I see that the UBlox A.02.04 updates the carrier profiles, and adds Sprint. Is a major benefit that the firmware upgrade will now allow us to access carriers other than AT&T with our Hologram SIMs?


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit e11508bf08d60e3a1dd4794ec1f2d1fe6a10b780.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


@Crissb75 what does it have to do with CoreELEC?


`info` looks like a pretty weird choice given the content of the log.


Successfully deployed to following URLs:

* https://website-9y5imw4r0.now.sh
* https://mikemcbride.me
* https://website.mcbridem.now.sh
* https://website-git-master.mcbridem.now.sh


✅ Device tests passed on iOS on [Azure DevOps](https://dev.azure.com/devdiv/DevDiv/_build/index?buildId=3066569)(iOS): [Html Report](http://xamarin-storage/jenkins/xamarin-macios/d16-3/300ee13e98821e40c5eb8ebc7def949162bd49fc/3066569/device-tests/jenkins-results/tests/index.html) ✅

# Test results

# All 70 tests passed


Deployment failed with the following error:

~~~
The domain somosantitesis.com is not verfied and cannot be used as an alias
~~~


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 152156374c7e4290372d25e6a5b624f52cbee0a0.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit b5e37ded7c8ea9350df9bcb9f924d7226426eb3c.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


Sorting on format as a 3rd column should help with the diffs comparison, too.


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit ac70909d34dc978cb07cd24071342be4f51b7d71.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


Copy of this build can be found at
https://www.mewbuilds.com/build/d18a815f41a22e39f05400a54ebc96ed2421fcda/index.html
                       https://www.cloudflare-ipfs.com/ipfs/QmX1L4YMfnAxTyL85DxvE9iVsQWFHs3JnPRj6bwagbvM69
                       Virus Total analysis
                       https://www.virustotal.com/file/84937f26726c2a3cacb4f42fb13b0ae88cb768274d84713bd98b8f7b700ed4b4/analysis/1569258834/


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 0bd2b4550cb74bf2f56de382b637f272c7347a84.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 15a6b82bd36b826aacbaeb884f8c47f451afe45b.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


Successfully deployed to following URLs:

* https://jsconf-kt0yr7cr7.now.sh
* https://jsconf.stiwarasprilla.now.sh
* https://jsconf-git-master.stiwarasprilla.now.sh


I think we could save the selections in the config, in this way even if user referesh's or comes back to the editor his / her preferences / selections are retained.


[vg CI tests](https://ucsc-ci.com/vgteam/vg/pipelines/1732) complete for branch fix-map-memory-leak.  View the [full report here](http://vg-data.s3.amazonaws.com/vg_ci/vgci_reports/commit/134916cf6d70f26fb9a6da0a5d7d6d764bb21406/index.html).

19 tests passed, 0 tests failed and 0 tests skipped in 13134 seconds

Tests produced 361 warnings. 361 were for lower-than-expected alignment scores


Successfully deployed to following URLs:

* https://spec-next-rguac6i7s.now.sh
* https://spec.fm
* https://spec-next.specfm1.now.sh
* https://spec-next-git-master.specfm1.now.sh


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit a08a65bf43ad8791462e7bc549e3538cf9531788.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit d2de3710914a012fdc5c9642a8b560a3730ae8e5.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit b86c43ee6309f42205605e52c9d4d636fe2ad73a.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit edc3e7653384fdb7d90ef2690db26be7e15d5e52.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


Successfully deployed to following URLs:

* https://alaincodes-4xyr90oxh.now.sh
* https://alain.codes
* https://alaincodes.alaincodes.now.sh
* https://alaincodes-git-master.alaincodes.now.sh


Successfully deployed to following URLs:

* https://test-nest-zeit-q8mqu6qxb.now.sh
* https://test-nest-zeit.dstanfield.now.sh
* https://test-nest-zeit-git-master.dstanfield.now.sh


Successfully deployed to following URLs:

* https://next-portfolio-k96eny2y5.now.sh
* https://tim-soft.now.sh
* https://timellenberger.now.sh
* https://timellenberger.com
* https://next-portfolio.tim-soft.now.sh
* https://next-portfolio-git-master.tim-soft.now.sh


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit c909a2aa697d5a53e27412c0cbacde05b57add53.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


    /*row_number() 是没有重复值的排序(即使两天记录相等也是不重复的)，可以利用它来实现分页
    dense_rank() 是连续排序，两个第二名仍然跟着第三名
    rank()       是跳跃拍学，两个第二名下来就是第四名*/


![](https://github.trello.services/images/mini-trello-icon.png) [[table]-[add]: general](https://trello.com/c/A60bQ5hm/72-table-add-general)


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

Created multidev environment [p-merge](https://dashboard.pantheon.io/sites/8205aa31-0dde-4c46-b172-53a6aae7d18d#p-merge) for edpack-archetype.


Successfully deployed to following URLs:

* https://reader-d7fpsd76k.now.sh
* https://reader.oacore.now.sh
* https://reader-git-master.oacore.now.sh


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:

```
Error parsing .poggit.yml: Level 0: yaml_parse(): scanning error
encountered during parsing: mapping values are not allowed in this context
(line 9, column 14) in /poggit/src/poggit/webhook/PushHandler.php#85
```

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/goldentouch74/BookSystem/settings/hooks) — see the webhook starting with `https://poggit.pmmp.io/webhooks.gh.repo` and look for the delivery with ID `563e216e-de26-11e9-99c0-7d1580ead01d`.

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


Could the `key` inputs be const references instead to avoid unnecessary copies in case the `KeyType` is a large type?


# Spring Boot MVC + Thymeleaf + JPA + banco PostgreSQL
## 09 - Editando cadastro com Thymeleaf e Spring Boot

Vamos editar nossos cadastros.

Vamos criar um novo link na tabela que será o **Editar**
**th:href** - Tag de link do Thymeleaf
Editar

Nesse link será passado a **URL** no controller assim como o parâmetro passado
Editar

Agora no lado do controller precisamos criar um mapeamento tanto da **url** quando da **paramento**

Criando método editar
Vamos retornar um objeto para um url - Vamos precisar do objeto ModelAndView

Vou precisar pegar a variável( id ) que eu estou editando que será o "idpessoa"

Existe outro forma de anotar o método usando o **@GetMapping**. Ele irá substituir o:
`@RequestMapping(method = RequestMethod.GET`

Ai precisamos inserir somente a url e o parâmetro usado. O método fica assim...
```
@GetMapping("/editarpessoa/{idpessoa}")
	public ModelAndView editar( @PathVariable("idpessoa") Long idpessoa ) {

		Optional<Pessoa> pessoa = pessoaRepository.findById(idpessoa);

		ModelAndView modelAndView = new ModelAndView("cadastro/cadastropessoa");
		modelAndView.addObject("pessoaobj",pessoa.get());
		return modelAndView;
	}
```

Jogando os dados na tela

Precisamos dizer pro thymeleaf que estamos trabalhando com um objeto. A partir dele vamos inserir o valor no formulário.

O formulário fica assim:
```
<form action="salvarpessoa" method="POST" th:object="${ pessoaobj }">

		<label>ID</label>
		<input name="id" th:field="*{ id }">

		<label>Nome</label>
		<input name="nome" th:field="*{ nome }">

		<label>Sobrenome</label>
		<input name="sobrenome" th:field="*{ sobrenome }">

		<label>Idade</label>
		<input name="idade" th:field="*{ idade }">

		<button class="btn waves-effect waves-light" type="submit"
			name="/salvarpessoa">
			Submit <i class="material-icons right">send</i>
		</button>
	</form>
```

Como a tela irá esperar um objeto  ... method="POST" th:object="${ pessoaobj }"> ...  Será preciso iniciar um objeto vazio no método acima
```
@RequestMapping(method = RequestMethod.GET, value = "/cadastropessoa")
	public ModelAndView incio() {

		ModelAndView modelAndView = new ModelAndView("cadastro/cadastropessoa");
		modelAndView.addObject("pessoaobj", new Pessoa());
		return modelAndView;
	}
```


It's confusing because as a decimal number, 2 isn't bigger than 11. You are treating it effectively as a series of 3 integers which collides when the 3rd digit goes over 10, as you mentioned. Obviously not a big deal and not at all worth changing, but one has to know the system. :)

Did the last daily go out with the 19.11 schema? That would be deciding whether this change goes in 11 or 12, right?


abc


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit bf88f1e1479f3eb8f9904ac7d368d84dce16e174.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


Successfully deployed to following URLs:

* https://test-nest-zeit-6g5g1f1xr.now.sh
* https://test-nest-zeit.dstanfield.now.sh
* https://test-nest-zeit-git-master.dstanfield.now.sh


new code


This could be factored out as a `add-message` function.


Successfully deployed to following URLs:

* https://aremycolorsaccessible-h1iep78dq.now.sh
* https://aremycoloursaccessible.com
* https://aremycolorsaccessible.com
* https://www.aremycolorsaccessible.com
* https://www.aremycoloursaccessible.com
* https://aremycolorsaccessible.sitaggart.now.sh
* https://aremycolorsaccessible-git-master.sitaggart.now.sh


Successfully deployed to following URLs:

* https://nitro-fkjg3ilxl.now.sh
* https://nitro.williamluke.now.sh
* https://nitro-git-master.williamluke.now.sh


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 8a53d4236458edbaa66d30a2fd30ac80f318f956.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


Hé pk le changement de lecteur ?


newArr не походит, лучше место него wizards - массив, множ число, без сокращений, указываем на сущность


Successfully deployed to following URLs:

* https://sirena-project-f06mrfy3d.now.sh
* https://sirena-project.juanpernu.now.sh
* https://sirena-project-git-master.juanpernu.now.sh


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit f3397ba92161ac214d371eb5b51999383b14f564.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


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:

```
Error parsing .poggit.yml: Level 0: yaml_parse(): scanning error
encountered during parsing: mapping values are not allowed in this context
(line 9, column 14) in /poggit/src/poggit/webhook/PushHandler.php#85
```

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/goldentouch74/BookSystem/settings/hooks) — see the webhook starting with `https://poggit.pmmp.io/webhooks.gh.repo` and look for the delivery with ID `df752a2c-de26-11e9-8a23-e3f7fd946767`.

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


заглавная для конструкторов, не нужно объект называть массивом, нам нужна сущность которая хранится в переменной, wizard например


Error while importing module. This commit is **removed** on the following commits.


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 099b131fa82b2c2f250dd74781a1eb2c0ecfca8b.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit ce0e00e998755abc56298a730293a04da7140a1c.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 3d1f0e2fa3a8df5bbd7910bd6c2762c66c9c611d.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


Successfully deployed to following URLs:

* https://jsconf-74nufjry4.now.sh
* https://jsconf.stiwarasprilla.now.sh
* https://jsconf-git-master.stiwarasprilla.now.sh


BEFORE:
evawyf.github.com --> evawyf.netlify.com
AFTER:
evawyf.github.com  or  evawyf.netlify.com  will both redirect to  evawyf.com.


Is this the same file that use for the code below:
 // extract an array of dictionaries from CSV file with columns "className", "bentleyId" and "jsonProperties"
    fs.readFile("assets/data.txt", "utf8", (_err, data) => {
      parse(data, {delimiter: ",", columns: ["className", "bentleyId", "jsonProperties"]}, async (_Err: any, output: any) => {
        for (const property of output) {
          this.updateJsonProperties(iModelDb, property.className, property.bentleyId, property.jsonProperties);
        }
        // push changes from local briefcase to iModelHub
        if (pushChanges) {
          await iModelDb.pushChanges(actx, () => "jsonProperties Update");
          fs.appendFileSync("assets/ledger.txt", "-------------PUSHED-------------\n\n");
        }
      });
    });


You will need to clarify this a bit more. You want to know how you can read a text file into a Java program (there plenty of examples on the internet)? What does this have to do with this repository and corresponding blog?


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit a8c762bd8eb8e7c280106f9e5c049b75e0d70744.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


@neilh10, Thank you for those links!
This "u-blox A.02.01 EasyFlash Update" file in particular provides very detailed step-by-step instructions.
https://www.digi.com/resources/documentation/digidocs/PDFs/90002353.pdf

It also clearly answers my questions. I need to get a XBIB-CU-TH development board, because my XBIB-U-DEV development board doesn't fully support USB Direct mode.


Successfully deployed to following URLs:

* https://surname-site-hx01xtvzu.now.sh
* https://stickajones.org
* https://surname-site.keplersj.now.sh
* https://surname-site-git-master.keplersj.now.sh


Can we use the environment "GOPATH" if it is set without needing to invoke "go"? And/or can we create a field on the workspace struct to cache the library folders so we don't need to invoke "go" for every buffer? Maybe we can change `library-folders-fn` to be called when the workspace is created rather than every time we run `lsp` for a buffer? I'm considering the case where someone starts Emacs with 1000 go buffers open.


Typo "Wheather"


Callaté lokere 💃


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 6ec83fa663185c4e05010abdcded101bacd7458a.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


Successfully deployed to following URLs:

* https://reader-3gkelvfl2.now.sh
* https://reader.oacore.now.sh
* https://reader-git-master.oacore.now.sh


I am checking those RSA related codes currently. This is a really nice contribution! Thanks @Xiangrui2019

But currently, I am still considering to simplify the private key and public key storage. As you know it has about 7 arguments which require to set. Do you have any good idea?


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 8d00af57a6c318c42ce4ecaea98e9613d60fa093.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


develop (mjwitte) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-UnitTestsCoverage-Debug: OK (1233 of 1233 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-43.2%25-green.png)


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit b8f33229d06d6504eee6ed350618529da7244244.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 43f4e3a737b9a9537508eb5a99e0802446a99b6f.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 52dea5458f86ca99f35a5616a8b2c378ac064193.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


Why keep the original if all we need is the small version?


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 03412baabfcfbb6561d3bc56953b5ae81bad7a15.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


I'm thinking it's simple to only keep one size of an image, at least for how the gallery works right now.


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 62f9704901234b32b78979e47bdaf9705d6ac8da.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


Successfully deployed to following URLs:

* https://bot-ionic-gazuzle9r.now.sh
* https://bot-ionic.alexanderendon.now.sh
* https://bot-ionic-git-master.alexanderendon.now.sh


Добавление подписи


`@JuliaRegistrator register()`


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 49f8eaf87848fabf6838f52ae5ccc4dd53ed3f90.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


Registration pull request created: [JuliaRegistries/General/3770](https://github.com/JuliaRegistries/General/pull/3770)

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if [Julia TagBot](https://github.com/apps/julia-tagbot) is installed, or can be done manually through the github interface, or via:
```
git tag -a v0.3.0 -m "<description of version>" f179e7447b6e19b702845893a0964691a54bca20
git push origin v0.3.0
```


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit a4ae0a1610a9dda39e0b7aa7e9e1fea2221d71ee.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 9632d8a3c8ab8114eb7e0a6beb31d6e764b9a7b8.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


FYI in an earlier incarnation of the HUD, I felt like Safari was measuring text correctly and chrome was "off", but I didn't dig-in to any numbers, I was just going off of how things looked.


Successfully deployed to following URLs:

* https://antitesis-6onkx79v9.now.sh
* https://somosantitesis.com
* https://antitesis.fobossalmeron.now.sh
* https://antitesis-git-master.fobossalmeron.now.sh


Successfully deployed to following URLs:

* https://bot-ionic-j9fx1x5pv.now.sh
* https://bot-ionic.alexanderendon.now.sh
* https://bot-ionic-git-master.alexanderendon.now.sh


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit c4a390f21c94f6a596ac1c85f75d5416783a2422.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


TeamCity Identity and Access Management / Identity - ManagementPortal [Build 531-IDAM-9-Lock-and-unlo](https://teamcity.nice.org.uk/viewLog.html?buildId=58538&buildTypeId=IdentityandAccessManagement_BuildRoleManagementPortal) outcome was **UNKNOWN**
Summary: Canceled (Execution timeout (new); Step 10/19) Build time: 01:26:41


Successfully deployed to following URLs:

* https://test-nest-zeit-ox8ux5ujc.now.sh
* https://test-nest-zeit.dstanfield.now.sh
* https://test-nest-zeit-git-master.dstanfield.now.sh


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 3e74af7eb35cb22756015e2fe62c295393547eb6.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit ff2b0d8e80ea91c2b5ea47ec6541efe1ece007ba.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


Registration pull request created: [JuliaRegistries/General/3771](https://github.com/JuliaRegistries/General/pull/3771)

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if [Julia TagBot](https://github.com/apps/julia-tagbot) is installed, or can be done manually through the github interface, or via:
```
git tag -a v0.8.5 -m "<description of version>" b30db9c99b2bca039cf984f1675e0e5977695341
git push origin v0.8.5
```


aaa


Should be tag = tag_ instead of just assigning the same thing (tag_ = tag_)


Successfully deployed to following URLs:

* https://cmsclubs-1pbfij1ny.now.sh
* https://utsccms.club
* https://www.utsccms.club
* https://cmsclubs.csec.now.sh
* https://cmsclubs-git-master.csec.now.sh


content: 0.8852291163134716


Text: 0.2834788650664364


Text: 0.21150958580278756


Successfully deployed to following URLs:

* https://reader-gduaadr48.now.sh
* https://reader.oacore.now.sh
* https://reader-git-master.oacore.now.sh


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 190981a19bfe74fb701c457fdbe4d86e2266efe9.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 70a3031f113f3f73f31c12f5517f0f090a9beb32.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


You are pushing commits at a very fast pace (accross the whole organization).
Due to that, we cannot deploy the commit 9be6aa8dfce6ea1623e533f8e7617b880b2c530c.

You can try again later or [upgrade](https://zeit.co/account/plan) your plan.


Deployment failed with the following error:

~~~
Your `package.json` file is missing a `build` property inside the `script` property.
~~~


Successfully deployed to following URLs:

* https://phase-ten-scorer-nextjs-mq5swc1w8.now.sh
* https://phase-ten-scorer-nextjs.barrymay.now.sh
* https://phase-ten-scorer-nextjs-git-master.barrymay.now.sh


With this, on a package with no patches that does '%autosetup -S git_am', I get: [https://gist.github.com/vathpela/2d5be09b557d309997f648490764147c](https://gist.github.com/vathpela/9718e5035086ef41f532af51944f48cc)
On a package with lots of patches, I get: [https://gist.github.com/vathpela/9718e5035086ef41f532af51944f48cc](https://gist.github.com/vathpela/9718e5035086ef41f532af51944f48cc)


Car celui la est bien plus complet Il propose en autre :
- Les notification sous Android
- La lecture en background est déjà fonctionnel dessus
- Si on change de page le lecteur conserve ce que l'on a regardé ainsi que le buffering accumuler


Successfully deployed to following URLs:

* https://bot-ionic-ae23w76c9.now.sh
* https://bot-ionic.alexanderendon.now.sh
* https://bot-ionic-git-master.alexanderendon.now.sh


CurrentEnvironment_EMSGuide_7303 (Unknown) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-IntegrationCoverage-Debug: OK (671 of 673 tests passed, 0 test warnings)

Failures:\n

integration Test Summary
 * Passed: 671
 * Timeout: 2

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


Successfully deployed to following URLs:

* https://react-portfolio-cedhjloxk.now.sh
* https://react-portfolio.rrankawat.now.sh
* https://react-portfolio-git-master.rrankawat.now.sh


my 2cents would be to suggest we use a specific version of sw (11413) to do all testing against.

From release notes of 11413-11411 these are the reasons why it might be best to use the latest 11413 as a reference test and hope for 11414

11413Known Issues
(UGH!!) 12. Modules registering to the AT&T network have been observed infrequently to get stuck in the PSM
dormant state (AI=0x2c). This state persists until the XBee is reset. [XBCELL-4812]
Bug Fixes
1. Reduce the time it takes to reach AI = 0x00 on NB-IoT networks. [XBCELL-5191

For 11412 bug fixes
1. Reduced the chance of encountering a critical bug that causes the cellular component to stop
working. This bug only happens with a specific cellular component firmware version which can be
determined by the output of the ATMV command. On firmware versions prior to 11412 the
problematic cellular component firmware version will be displayed as “L0.0.00.00.05.06 [Feb 03
2018 13:00:41]” and on version 11412 it will be displayed as “L0.0.00.00.05.06,A.02.00”.

For 11411
New Features
1. Cellular Network Time command (ATDT)
Reports the local time of the XBee device, if time has been synchronized with the network.
Read the number of seconds since Jan 1 2000 00:00:00 UTC, or an ISO 8601-formatted
timestamp
Bug Fixes
2. ATAI stuck at 0x22 after fixing an incorrect ATAN value. [XBCELL-4508]


Successfully deployed to following URLs:

* https://bot-ionic-qpebgypr3.now.sh
* https://bot-ionic.alexanderendon.now.sh
* https://bot-ionic-git-master.alexanderendon.now.sh


Why also 19.03?  Aren't such changes better avoided on stable branches?  (19.09 isn't out yet, so I expect it's perfectly fine)


Successfully deployed to following URLs:

* https://csecfrontend-8juxhgk0u.now.sh
* https://csec.club
* https://www.csec.club
* https://csecfrontend.csec.now.sh
* https://csecfrontend-git-master.csec.now.sh


Successfully deployed to following URLs:

* https://jsconf-5vdctlrzj.now.sh
* https://jsconf.stiwarasprilla.now.sh
* https://jsconf-git-master.stiwarasprilla.now.sh


added "see example below"


Change the way small values are corrected in the HD module in the case where small_values_method='replace' (and when hd_energy=T). Now, when the pressure is below small_pressure while the density is still above small_density, we correct the pressure but not the density (neither the components of the linear momentum).

To do so, we had to permute, in hd_check_w, the 2 checks. Now, we check first whether there is any pressure in the block which goes below small_pressure and then whether there is any density in the block which goes below small_density. Doing so, flag takes the value 0 if there is no need for correction, rho_ if density and pressure (and linear momentum) need to be corrected and e_ if only pressure needs to be corrected.


XBIB-CU-TH : if you are in a hurry - (though Digikey might be easy ground next day for you :)
Seems there is now an upgrade for the App direct with firmware 11413 (ie without XBIB-CU-TH) - see "u-blox Over the Wire Update Script"
https://www.digi.com/support/productdetail?pid=5635&type=firmware


Successfully deployed to following URLs:

* https://carbon-website-b6ix5bsag.now.sh
* https://carbondesignsystem.now.sh
* https://carbon-website.carbon-design-system.now.sh
* https://carbon-website-git-master.carbon-design-system.now.sh


Successfully deployed to following URLs:

* https://jameswlanedev-chk023dfn.now.sh
* https://jameswlane.dev
* https://jameswlanedev.jameswlane.now.sh
* https://jameswlanedev-git-master.jameswlane.now.sh


Successfully deployed to following URLs:

* https://builder-vwzmdnzaje.now.sh
* https://builder-staging.now.sh


TeamCity Bvcms / Build [Build 2211](https://builds.tpsdb.com/viewLog.html?buildId=8802&buildTypeId=Bvcms_Build) is now running


html tag


Fixed in commit ae79c3253036e47b4acb1e286fb0e253543b1475.


I agree that for development purposes your CRC solution is awesome and better.  But this at least ensures that regular folks are not going to suffer the kind of stale cache problem I caused with my change.


OK.


Successfully deployed to following URLs:

* https://antitesis-kbzgyoge1.now.sh
* https://somosantitesis.com
* https://antitesis.fobossalmeron.now.sh
* https://antitesis-git-master.fobossalmeron.now.sh


Successfully deployed to following URLs:

* https://experimentwithcom-9vkmvo4xd.now.sh
* https://experimentwith.com
* https://www.experimentwith.com
* https://experimentwithcom.jameswlane.now.sh
* https://experimentwithcom-git-master.jameswlane.now.sh


That sounds good to me.


Unfortunately I used different config or version of clang-format (I don't really know), so, indention style is changed (again).


Successfully deployed to following URLs:

* https://jwlcloud-c64n2uv8b.now.sh
* https://jwl.cloud
* https://www.jwl.cloud
* https://jwlcloud.jameswlane.now.sh
* https://jwlcloud-git-master.jameswlane.now.sh


very interesting, but I strongly suggest to keep `score += make_score(v, v * (r - 2) / 4);`
you can try to simplify that with some other test.


TeamCity Identity and Access Management / Identity - ManagementPortal [Build 532-IDAM-9-Lock-and-unlo](https://teamcity.nice.org.uk/viewLog.html?buildId=58539&buildTypeId=IdentityandAccessManagement_BuildRoleManagementPortal) outcome was **FAILURE**
Summary:
       "/etc/teamcity/work/fb824473f3038a96/NICE.Identity.Management.sln" (default target) (1) ->
       (Restore target) ->
         /usr/share/dotnet/sdk/2.2.401/NuGet.targets(123,5): error : Problem starting the plugin '/etc/teamcity/plugins/nuge... Build time: 00:03:04


Thanks a lot, it works :100:


Successfully deployed to following URLs:

* https://experimentwithcom-obruh4nq0.now.sh
* https://experimentwith.com
* https://www.experimentwith.com
* https://experimentwithcom.jameswlane.now.sh
* https://experimentwithcom-git-master.jameswlane.now.sh


My reasoning is that we only want to update messages-content when echoing (like Emacs).  Otherwise an `add-message` function would imply that other sites can add messages, without prompting the user in the status buffer.
Thoughts?


Still need to test all of that cleaning up though, I've probably broken a few things along the way. Congrats on your work on hotbox_designer by the way! Really cool and powerful piece of software. I'm planning on adding a few more shape options and charge the way it handles the path for images and shared hotboxes to facilitate it's use on a centralized repository on a mixed os environment. I'll let you know how that goes.

________________________________
From: Lionel Brouyère <notifications@github.com>
Sent: Monday, September 23, 2019 1:32 PM
To: dgirondi/hotbox_designer
Cc: Diogo Girondi; Author
Subject: Re: [dgirondi/hotbox_designer] Code cleanup (937c000)

Hey, I didn't know that was possible ! Cool :)

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://github.com/dgirondi/hotbox_designer/commit/937c000c5263b2d03b5d3e994c1a21a57be3147d?email_source=notifications&email_token=AAD6ZYRQ3LP2O5TVOPX3PB3QLDVQTA5CNFSM4IZNCO52YY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBBSEOX#commitcomment-35197399>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAD6ZYRR47JYJEUHM3ZGZXTQLDVQTANCNFSM4IZNCO5Q>.


Mistakenly edited directly  on master - hope it is fine, @tiagobento >.<


Done


Successfully deployed to following URLs:

* https://20192pirogi-8ophl9rzi.now.sh
* https://20192pirogi.ivanshport98.now.sh
* https://20192pirogi-git-dev.ivanshport98.now.sh


Ignore this... was writing some simple tests to understand AST construction


Nice - this fixes all tests on my end regarding this issue.


I don't see where you need this function.


Can you make this cvar also block the double duck in the air?


With this, a package with no patches has '%autosetup -S git_am' expand to something like: [https://gist.github.com/vathpela/65d392dcd4c6d972a6392276fc62ea94](https://gist.github.com/vathpela/65d392dcd4c6d972a6392276fc62ea94)
A package with several patches expands to something like: [https://gist.github.com/vathpela/290ee67047a03aa75da57ed4f43e734e](https://gist.github.com/vathpela/290ee67047a03aa75da57ed4f43e734e)


so, are we good to close this PR and call it done?


Event comes after state change (and before external call like `transfer` or another contract function).


Use `indexed`


Problem with `selfdestruct` is that it removes the contract code from the network so if someone accidentally sends funds to that contract, they are trapped forever.
A better approach would be to mimic the `pause` functionality (state variable, modifier, kill function) but only difference is that you cannot resume a killed contract.


Successfully deployed to following URLs:

* https://20192pirogi-a5isz0ctq.now.sh
* https://20192pirogi.ivanshport98.now.sh
* https://20192pirogi-git-dev.ivanshport98.now.sh


Hi! This is the friendly automated conda-forge-webservice.

I updated the Github team because of this commit.

- @hhslepicka was added to this feedstock maintenance team.

You should get push access to this feedstock and CI services.

Feel free to join the community [chat room](https://gitter.im/conda-forge/conda-forge.github.io).

NOTE: Please make sure to not push to the repository directly.
      Use branches in your fork for any changes and send a PR.
      More details [here](https://conda-forge.org/docs/maintainer/updating_pkgs.html#forking-and-pull-requests)


@Araq whats idiomatic? Return, result or none?


Thanks @HenryGeorgist  for WPF and View Model training.


7041_ElectricEquipment_ITE_AirCooled (Unknown) - x86_64-Linux-Ubuntu-18.04-cppcheck: OK (0 of 0 tests passed, 0 test warnings)

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


user.id 가 아니고 user._id 인것 같습니다!!
post.user.id 가 아니고 post.user._id 인거같습니다.!!


Hi! This is the friendly automated conda-forge-webservice.

I updated the Github team because of this commit.

- @zivy was added to conda-forge. Welcome to conda-forge!
  Go to https://github.com/orgs/conda-forge/invitation see your invitation.

- @blowekamp was added to this feedstock maintenance team.

You should get push access to this feedstock and CI services.

Feel free to join the community [chat room](https://gitter.im/conda-forge/conda-forge.github.io).

NOTE: Please make sure to not push to the repository directly.
      Use branches in your fork for any changes and send a PR.
      More details [here](https://conda-forge.org/docs/maintainer/updating_pkgs.html#forking-and-pull-requests)


Думаю, здесь можно было в цикле все-таки пробежаться по октетам и сравнить с 46.


<details>

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

Internal Server Error, incidentId a6f6c970-df9c-4226-a8b1-e8e8b2731417.

---

* method:     createTask
* errorCode:  InternalServerError
* statusCode: 500
* time:       2019-09-23T17:50:19.622Z

</details>


7041_ElectricEquipment_ITE_AirCooled (Unknown) - x86_64-Linux-Ubuntu-18.04-custom_check: OK (10 of 11 tests passed, 0 test warnings)

Failures:\n

 Test Summary
 * Passed: 10
 * : 1

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


Or you can use the `mod` operation which calculates the remainder...but anyway the remainder is always `1 Wei`.


You will need this function once you implement the kill functionality the way I advised you too 🙂 make sure it can be run only by the owner when the contract is killed.


Yeah let's revert the change in 5e845ace8452acc9694d70c467a1e3921b8798e7 to avoid breaking any overrides.


Successfully deployed to following URLs:

* https://vithack2019-7odnove5z.now.sh
* https://vithack2019.priyankkaushik.now.sh
* https://vithack2019-git-master.priyankkaushik.now.sh


IBM Cloud [toolchain](https://cloud.ibm.com/devops/toolchains/89e3eeae-88cc-41a2-a25b-50372c1b884a?env_id=ibm%3Ayp%3Aeu-de "dave-db-app-toolchain"): [Delivery Pipeline](https://cloud.ibm.com/devops/pipelines/cd993f68-eb6a-4cbe-af15-6597a19f0cab "dave-db-app-toolchain") deployed [davedb-app](https://github.com/oavkdtv/davedb-app/releases/tag/deploy-ibm-yp-eu-de-dave-db-dave-db-space-20190923-175355 "deploy-ibm-yp-eu-de-dave-db-dave-db-space-20190923-175355") to [dave-db-space](https://console.bluemix.net/apps/5ea3e05f-c78e-4fd2-b564-b425e4fc74be?env_id=ibm:yp:eu-de "ibm:yp:eu-de:dave-db:dave-db-space"), including this commit


Hi! This is the friendly automated conda-forge-webservice.

I updated the Github team because of this commit.

- @zivy was added to conda-forge. Welcome to conda-forge!
  Go to https://github.com/orgs/conda-forge/invitation see your invitation.

You should get push access to this feedstock and CI services.

Feel free to join the community [chat room](https://gitter.im/conda-forge/conda-forge.github.io).

NOTE: Please make sure to not push to the repository directly.
      Use branches in your fork for any changes and send a PR.
      More details [here](https://conda-forge.org/docs/maintainer/updating_pkgs.html#forking-and-pull-requests)


How do I test this?
Installed version from AMO ,not work bypass on ouo.today


Константы с которыми приходится работать лучше где-то обьявить в одном месте. В будущем их можно будет менять и не надо будет углубляться в дебри кода, чтобы поменять константу.


This method is not advised because it takes the average of gas used in the last few transactions/blocks.
Use this `const gasPrice = tx.gasPrice` (you defined `tx` above); this way you get the exact gas price that was used for your transaction.


You can change the brackets no problem :ok_hand:  @the-j0k3r


Reverted in 19.03 in 5051f5435ea and cherry-picked in 19.09 in d0d296fb805


Reverted in 19.03 in 5051f54 and cherry-picked in 19.09 in d0d296f


What is this change about ?


@stephencelis Is there a plan to release this commit soon? I believe all carthage builds on Swift 5 will be broken until this is released.  Currently I am pointing at master, but would prefer to point to a specific release.


Still need to implement:
1. Using `.call` before the actual call
2. Using `on('transactionHash')`
3. Using `on('receipt')`


hum ok faudras trouver pour l'aspect ratio la c'est pas top


Resolve o erro "invalid debit" com o método payment/pay, devido ao parâmetro dueDate estar inválido.
Erro detectado em Linx, BBC e MRD.


describe what the variable is referring to
private TextView textViewProgressCaption


[Circle has built](https://circleci.com/gh/cypress-io/cypress/153778) the `linux x64` version of the Test Runner.

You can install this pre-release platform-specific build using instructions at [https://on.cypress.io/installing-cypress#Install-pre-release-version](https://on.cypress.io/installing-cypress#Install-pre-release-version).

You will need to use custom `CYPRESS_INSTALL_BINARY` url and install Cypress using an url instead of the version.

    export CYPRESS_INSTALL_BINARY=https://cdn.cypress.io/beta/binary/3.5.0/linux-x64/circle-develop-e0fb38fcab6cde257ef54f357b6c9aff135ce600-153743/cypress.zip
    npm install https://cdn.cypress.io/beta/npm/3.5.0/circle-develop-e0fb38fcab6cde257ef54f357b6c9aff135ce600-153751/cypress.tgz


Аргументы в скобки. >> сделано
Можно сразу поезд передавать в метод, а не номер >> метод add_wagon_to_train вызывается только классом UserInterface, который оперирует только чтением данных от пользователя и передачей их. Таким образом, мне кажется, что передача номера в данном случае подходит.


e


mmh so, a this point the 4th option is the better but i think it's better perform clean cache at every addon upgrade, so there is no need to act for any other breakages


Successfully deployed to following URLs:

* https://carbon-website-l5877slxm.now.sh
* https://carbondesignsystem.now.sh
* https://carbon-website.carbon-design-system.now.sh
* https://carbon-website-git-master.carbon-design-system.now.sh


k


Yep car hormis ce probleme de ratio et le fait que je n'ai pas encore reussit a lire les vidéo en local sinon ce lecteur est vraiment bon ^^


asdf


Successfully deployed to following URLs:

* https://movaxfccom-878jw7pr6.now.sh
* https://www.movaxfc.com
* https://movaxfc.com
* https://movaxfccom.johno1.now.sh
* https://movaxfccom-git-master.johno1.now.sh


Код достаточно простой и понятный. Считаю для лучшей читаемости кода его следует разбить на функции, дав им имена, обозначающие их наполнение. Тут наверно не важно, что функция будет вызываться только один раз, важнее, то как код будет поддерживаться в будущем.
И покрытие тестами конечно нужно, а для этого тоже нужны функции.


testing...


for stuff that's pretty complicated taken from stackoverflow, should leave a comment describing what it's doing and a link back to the stackoverflow post


> AppImage should be genarated on a "old" distribution to be sure that
libc versions are compatible.

To be precise, what goes __into__ AppImages.

> However, we need at least ubuntu bionic to have QWebEngine packaged.

Why do you think this?
https://launchpad.net/~beineri/+archive/ubuntu/opt-qt-5.12.3-xenial has QWebEngine for xenial.

> Let's prepare our AppDir directory in bionic and generate the appimage
in xenial.

That entirely defeats the purpose, as , what goes __into__ AppImages must be built on the oldest still-supported LTS release of Ubuntu.

> By using a small launcher script, we check that libc versions are
compatible and else print a nice message instead of crash.

That doesn't make it work, does it?


hi!!!!


@matepapp  ezt direkt raktam bele, hogy ne legyen átlátszó mert így belelógnak a pattern részei a szövegbe és volt, hogy nem volt olvasható főleg a gémkapocsnál


TeamCity Bvcms / Build [Build 2211](https://builds.tpsdb.com/viewLog.html?buildId=8802&buildTypeId=Bvcms_Build) outcome was **SUCCESS**
Summary: Tests passed: 121 Build time: 00:23:07


TeamCity Bvcms / Build [Build 2212](https://builds.tpsdb.com/viewLog.html?buildId=8803&buildTypeId=Bvcms_Build) is now running


Successfully deployed to following URLs:

* https://indgila-portfolio-ab5kls251.now.sh
* https://indgila-portfolio.razdvapoka.now.sh
* https://indgila-portfolio-git-master.razdvapoka.now.sh


No. You are still thinking of the period as separating 2 integers, 2 and 11, which is not how this works.

0.2 is bigger than 0.11

Or if you prefer integers, then 20 > 11, and if we go to 0.191

0.2 is bigger than 0.191 and 200 > 191

Stop using the period as an integer separator and return to considering it as a decimal separator where digits closer to the separator are larger than digits further from it, or just add the implied zeros before you compare your two integers.

Yes. The code that starts using 19.11 has been released. So, there are users out there creating files with 19.11 in their schema version field and those installations will not understand your changes. So, 19.12 is appropriate, and this is the right consideration to use in deciding.


[AppVeyor has built](https://ci.appveyor.com/project/cypress-io/cypress/builds/27606396/job/yahw6v99k8031s5o) the `win32 ia32` version of the Test Runner.

You can install this pre-release platform-specific build using instructions at [https://on.cypress.io/installing-cypress#Install-pre-release-version](https://on.cypress.io/installing-cypress#Install-pre-release-version).

You will need to use custom `CYPRESS_INSTALL_BINARY` url and install Cypress using an url instead of the version.

    set CYPRESS_INSTALL_BINARY=https://cdn.cypress.io/beta/binary/3.5.0/win32-ia32/appveyor-develop-e0fb38fcab6cde257ef54f357b6c9aff135ce600-27606396/cypress.zip
    npm install https://cdn.cypress.io/beta/binary/3.5.0/win32-ia32/appveyor-develop-e0fb38fcab6cde257ef54f357b6c9aff135ce600-27606396/cypress.zip


develop (Myoldmopar) - Win64-Windows-10-VisualStudio-16: OK (1904 of 1904 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)


<img width="611" alt="Screenshot 2019-09-23 at 20 04 10" src="https://user-images.githubusercontent.com/31661071/65450405-501d9c80-de3d-11e9-850c-bda37d798dde.png">


szerintem igy jobban nez ki sokkal, az a neutral nem volt olyan fasza, max ha megprobaljuk hatterrel egy 30%-os opacityvel


[AppVeyor has built](https://ci.appveyor.com/project/cypress-io/cypress/builds/27606396/job/g100pbq8r6047ab5) the `win32 x64` version of the Test Runner.

You can install this pre-release platform-specific build using instructions at [https://on.cypress.io/installing-cypress#Install-pre-release-version](https://on.cypress.io/installing-cypress#Install-pre-release-version).

You will need to use custom `CYPRESS_INSTALL_BINARY` url and install Cypress using an url instead of the version.

    set CYPRESS_INSTALL_BINARY=https://cdn.cypress.io/beta/binary/3.5.0/win32-x64/appveyor-develop-e0fb38fcab6cde257ef54f357b6c9aff135ce600-27606396/cypress.zip
    npm install https://cdn.cypress.io/beta/binary/3.5.0/win32-x64/appveyor-develop-e0fb38fcab6cde257ef54f357b6c9aff135ce600-27606396/cypress.zip


With this, a package with no patches has '%autosetup -S git_am' expand to something like: [https://gist.github.com/vathpela/c45ec2b37a4595639bd4924d007291dd](https://gist.github.com/vathpela/c45ec2b37a4595639bd4924d007291dd)
A package with several patches expands to something like: [https://gist.github.com/vathpela/fec43486f0d14af43e2e1d8d83860ca7](https://gist.github.com/vathpela/fec43486f0d14af43e2e1d8d83860ca7)


be descriptive with your variable names. e.g. switchUseless or textViewCaption


Да, хорошо. Опять же все упирается в функции, которые я не реализовал.


Successfully deployed to following URLs:

* https://webi-6dq330bli.now.sh
* https://webi.enesshala.now.sh
* https://webi-git-master.enesshala.now.sh


Successfully deployed to following URLs:

* https://webi-e3xbue12m.now.sh
* https://webi.enesshala.now.sh
* https://webi-git-master.enesshala.now.sh


7041_ElectricEquipment_ITE_AirCooled (Unknown) - x86_64-Linux-Ubuntu-18.04-gcc-7.4: OK (2613 of 2613 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)


Ahh okay, I understand the purpose of `AnnotationMatchingPointcutTests` and `AsyncMethodsSpringTestContextIntegrationTests` now.

Thanks for enlightening me @sbrannen! :+1:


Deployment failed with the following error:

~~~
The chosen alias "preloader.now.sh" is already in use by another account.
~~~


Yeah, it's the difference between `Schwab` and `******1234`. I dunno, maybe there's a better way to do it. It does feel pretty special case.


Можно было бы, но здесь по моему мнению не сильно запутанный код для подобной манипуляции. Цикл это инициализация переменной и её инкремент. Возможно компилятор всё упростит, но это не точно.


It's gonna be in Universal Bypass 11.3


What's the plan?


Спасибо за ревью.


Why did you remove all this documentation? Please put it back in.


Sure, why not. Unfortunately, I do not own a Saturn. So I have to get one first  :)


why


Please **always** use PyCharm!
Please conform to the standard Python code conventions.


Why did you remove these? Also the placeholders? Please put back in.


Please undo these changes.


! in the wrong spot maybe?


Please undo.


That seems to be another regression: https://trac.cppcheck.net/ticket/9367


Need to clean up and organize values.


[Circle has built](https://circleci.com/gh/cypress-io/cypress/153784) the `darwin x64` version of the Test Runner.

You can install this pre-release platform-specific build using instructions at [https://on.cypress.io/installing-cypress#Install-pre-release-version](https://on.cypress.io/installing-cypress#Install-pre-release-version).

You will need to use custom `CYPRESS_INSTALL_BINARY` url and install Cypress using an url instead of the version.

    export CYPRESS_INSTALL_BINARY=https://cdn.cypress.io/beta/binary/3.5.0/darwin-x64/circle-develop-e0fb38fcab6cde257ef54f357b6c9aff135ce600-153776/cypress.zip
    npm install https://cdn.cypress.io/beta/npm/3.5.0/circle-develop-e0fb38fcab6cde257ef54f357b6c9aff135ce600-153774/cypress.tgz


ZEIT Now cannot deploy this project to production due to following domain related issues:

 * `free-blog.vuetifyjs.com`(for alias `free-blog.vuetifyjs.com`) is not found inside your account. [Add it](https://zeit.co/dashboard/domains?action=add&domain=free-blog.vuetifyjs.com).


Done


Now could not deploy this pull request since the "files" configuration in `now.json` lists these files or directories which do not exist:

* `dist`

These paths may be missing from the GitHub repository because of a `.gitignore` file.
Consider committing them to GitHub or removing them from the "files" list and generating the paths on Now instead using a [build script for a Node.js deployment](https://zeit.co/docs/deployment-types/node), or within your `Dockerfile` for a [docker deployment](https://zeit.co/docs/deployment-types/docker).

For more information on the "files" configuration in now.json, visit [https://zeit.co/docs/features/configuration#files(array)](https://zeit.co/docs/features/configuration#files(array))


Why? Please undo.


Indentation is off.


Please write standard Python code.


new commit


Also undo this anyway.


Successfully deployed to following URLs:

* https://now-mongo-answers-ppe1c1r1d.now.sh
* https://now-mongo-answers.lollymay.now.sh
* https://now-mongo-answers-git-master.lollymay.now.sh


Successfully deployed to following URLs:

* https://jameswlanedev-mn73vc3w6.now.sh
* https://jameswlane.dev
* https://jameswlanedev.jameswlane.now.sh
* https://jameswlanedev-git-master.jameswlane.now.sh


Never add uncommented code (but maybe this was anyway not meant to be final...).


Note that in the patch description I accidentally said '%autosetup -S git' instead of '%autosetup -S git_am'.


Why should this be needed? Either you have it all inside the graph, i.e. you assume it to be there in some format, or you have it all in an external file, e.g. JSON. But sth mixed does not make much sense.


Code...


Successfully deployed to following URLs:

* https://serve-md-7o9wo3bd2.now.sh
* https://serve-md.charlesdlandau.net
* https://serve-md.charlesdlandau.now.sh
* https://serve-md-git-master.charlesdlandau.now.sh


Who is decreasing the values in `tv.tv_sec` and `tv.tv_usec` ?
The way I see it, this loop will always max out on the timeout


What if we make the field hold the entire message `"Withdrawing $100 from your Schwab bank account *****1234."`? Anchors may come in all shapes, as an example an anchor that charges an amount to your phone bill directly. In that case displaying text to the user like `Withdrawing...` is strange, and it'd more likely be something like `"Charging $100 to your <Carrier> phone number <phonenumber>."`


I found something here https://rexus2019.wordpress.com but its only for sale. I would love to solder my own like I did from Your Project for Dreamcast :)


Successfully deployed to following URLs:

* https://jameswlanedev-7phbjazd7.now.sh
* https://jameswlane.dev
* https://jameswlanedev.jameswlane.now.sh
* https://jameswlanedev-git-master.jameswlane.now.sh


szerintem is igy sokkal termeszetesebb es nem veszesen zavaro a pattern


I see it like this:
* have a VERSION file in python dir within the image version value,
* then introduce variable `BUILD_IMAGE_VERSION`, evaluating it like `${BUILD_IMAGE_VERSION:-<VERSION}`.

So it should cover both cases - ci build (where timestamped version will be propagated to the script(s) via env var) and local builds, where the version will be picked up from VERSION file.

cc @porridge @samvantran


Почему то персонажи располагаются не горизонтально. Нужно как то изменить стили?


yeah that's my thought.  Also if its a check that has a routing and account
number then you need 3 fields, or end up putting multiple values in one
field.  Might as well just make it one field instead of trying to tie
anchors implementations to wallets UI choices

On Mon, Sep 23, 2019 at 11:16 AM Leigh McCulloch <notifications@github.com>
wrote:

> What if we make the field hold the entire message "Withdrawing $100 from
> your Schwab bank account *****1234."? Anchors may come in all shapes, as
> an example an anchor that charges an amount to your phone bill directly. In
> that case displaying text to the user like Withdrawing... is strange, and
> it'd more likely be something like "Charging $100 to your <Carrier> phone
> number <phonenumber>."
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/stellar/stellar-protocol/commit/bc1433a7aaa52bffb0126e7a174f25bf73919465?email_source=notifications&email_token=AABHK3ZY3ITSZTZJMHURLC3QLEBXZA5CNFSM4IY3PVU2YY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBBSGCP#commitcomment-35199055>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AABHK376Z44AKRV75JGMIULQLEBXZANCNFSM4IY3PVUQ>
> .
>


### TinyCI build failure:
[cmake --build .] returned [1]:
```[1/5] Building CXX object CMakeFiles/Template.dir/data/tinyci_build/daid/SeriousProton2/src/window.cpp.o
FAILED: CMakeFiles/Template.dir/data/tinyci_build/daid/SeriousProton2/src/window.cpp.o
/usr/bin/c++    -I/data/tinyci_build/daid/SeriousProton2/include -I/data/tinyci_build/daid/SeriousProton2/extlibs/bullet -I/usr/include/SDL2 -I/data/tinyci_build/daid/SeriousProton2/extlibs -I/data/tinyci_build/daid/SeriousProton2/extlibs/miniz -I/data/tinyci_build/daid/SeriousProton2/extlibs/freetype-2.9/include -O3 -DNDEBUG  -O3 -funsafe-math-optimizations   -Wall -Wno-psabi -Wno-strict-aliasing -Werror=suggest-override -std=gnu++11 -MD -MT CMakeFiles/Template.dir/data/tinyci_build/daid/SeriousProton2/src/window.cpp.o -MF CMakeFiles/Template.dir/data/tinyci_build/daid/SeriousProton2/src/window.cpp.o.d -o CMakeFiles/Template.dir/data/tinyci_build/daid/SeriousProton2/src/window.cpp.o -c /data/tinyci_build/daid/SeriousProton2/src/window.cpp
/data/tinyci_build/daid/SeriousProton2/src/window.cpp:12:21: fatal error: stb/gif.h: No such file or directory
 #include <stb/gif.h>
                     ^
compilation terminated.
[2/5] Building CXX object CMakeFiles/Template.dir/data/tinyci_build/daid/SeriousProton2/src/graphics/graphicslayer.cpp.o
[3/5] Building CXX object CMakeFiles/Template.dir/src/main.cpp.o
[4/5] Building CXX object CMakeFiles/Template.dir/data/tinyci_build/daid/SeriousProton2/src/engine.cpp.o
ninja: build stopped: subcommand failed.

```


edit this program.


### TinyCI build failure:
[make -j 3] returned [2]:
```[  5%] Built target lua
[ 14%] Built target box2d
[ 15%] Built target json11
[ 16%] Built target miniz
[ 43%] Built target sp2freetype
[ 73%] Built target bullet
Scanning dependencies of target ZeroRho
[ 73%] Building CXX object CMakeFiles/ZeroRho.dir/src/main.cpp.o
[ 73%] Building CXX object CMakeFiles/ZeroRho.dir/home/tinyci/builds/daid/SeriousProton2/src/engine.cpp.o
[ 73%] Building CXX object CMakeFiles/ZeroRho.dir/home/tinyci/builds/daid/SeriousProton2/src/graphics/graphicslayer.cpp.o
[ 73%] Building CXX object CMakeFiles/ZeroRho.dir/home/tinyci/builds/daid/SeriousProton2/src/window.cpp.o
CMakeFiles/ZeroRho.dir/build.make:3350: recipe for target 'CMakeFiles/ZeroRho.dir/home/tinyci/builds/daid/SeriousProton2/src/window.cpp.o' failed
CMakeFiles/Makefile2:72: recipe for target 'CMakeFiles/ZeroRho.dir/all' failed
Makefile:83: recipe for target 'all' failed

/home/tinyci/builds/daid/SeriousProton2/src/window.cpp:12:21: fatal error: stb/gif.h: No such file or directory
 #include <stb/gif.h>
                     ^
compilation terminated.
make[2]: *** [CMakeFiles/ZeroRho.dir/home/tinyci/builds/daid/SeriousProton2/src/window.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/ZeroRho.dir/all] Error 2
make: *** [all] Error 2
```


develop (mjwitte) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-IntegrationCoverage-Debug: OK (674 of 674 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-68.44%25-green.png)


### TinyCI build failure:
[make -j 3] returned [2]:
```[  1%] Built target miniz
[  6%] Built target lua
[ 15%] Built target box2d
[ 16%] Built target json11
[ 42%] Built target sp2freetype
[ 71%] Built target bullet
Scanning dependencies of target Geronimo
[ 71%] Building CXX object CMakeFiles/Geronimo.dir/src/main.cpp.o
[ 71%] Building CXX object CMakeFiles/Geronimo.dir/home/tinyci/builds/daid/SeriousProton2/src/engine.cpp.o
[ 71%] Building CXX object CMakeFiles/Geronimo.dir/home/tinyci/builds/daid/SeriousProton2/src/graphics/graphicslayer.cpp.o
[ 71%] Building CXX object CMakeFiles/Geronimo.dir/home/tinyci/builds/daid/SeriousProton2/src/window.cpp.o
CMakeFiles/Geronimo.dir/build.make:3758: recipe for target 'CMakeFiles/Geronimo.dir/home/tinyci/builds/daid/SeriousProton2/src/window.cpp.o' failed
CMakeFiles/Makefile2:72: recipe for target 'CMakeFiles/Geronimo.dir/all' failed
Makefile:83: recipe for target 'all' failed

/home/tinyci/builds/daid/SeriousProton2/src/window.cpp:12:21: fatal error: stb/gif.h: No such file or directory
 #include <stb/gif.h>
                     ^
compilation terminated.
make[2]: *** [CMakeFiles/Geronimo.dir/home/tinyci/builds/daid/SeriousProton2/src/window.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Geronimo.dir/all] Error 2
make: *** [all] Error 2
```


This is a (very minorly) breaking change, but if its only anchor USD we can
ask them to just roll with it.  Do any wallets respect this?

On Mon, Sep 23, 2019 at 11:18 AM Michael Feldstein <msfeldstein@gmail.com>
wrote:

> yeah that's my thought.  Also if its a check that has a routing and
> account number then you need 3 fields, or end up putting multiple values in
> one field.  Might as well just make it one field instead of trying to tie
> anchors implementations to wallets UI choices
>
> On Mon, Sep 23, 2019 at 11:16 AM Leigh McCulloch <notifications@github.com>
> wrote:
>
>> What if we make the field hold the entire message "Withdrawing $100 from
>> your Schwab bank account *****1234."? Anchors may come in all shapes, as
>> an example an anchor that charges an amount to your phone bill directly. In
>> that case displaying text to the user like Withdrawing... is strange,
>> and it'd more likely be something like "Charging $100 to your <Carrier>
>> phone number <phonenumber>."
>>
>> —
>> You are receiving this because you authored the thread.
>> Reply to this email directly, view it on GitHub
>> <https://github.com/stellar/stellar-protocol/commit/bc1433a7aaa52bffb0126e7a174f25bf73919465?email_source=notifications&email_token=AABHK3ZY3ITSZTZJMHURLC3QLEBXZA5CNFSM4IY3PVU2YY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBBSGCP#commitcomment-35199055>,
>> or mute the thread
>> <https://github.com/notifications/unsubscribe-auth/AABHK376Z44AKRV75JGMIULQLEBXZANCNFSM4IY3PVUQ>
>> .
>>
>


### TinyCI build failure:
[make -j 3] returned [2]:
```[  0%] Built target miniz
[  9%] Built target box2d
[ 15%] Built target lua
[ 42%] Built target sp2freetype
[ 42%] Built target json11
[ 72%] Built target bullet
Scanning dependencies of target BitAndNibbly
[ 72%] Building CXX object CMakeFiles/BitAndNibbly.dir/src/main.cpp.o
[ 72%] Building CXX object CMakeFiles/BitAndNibbly.dir/data/tinyci_build/daid/SeriousProton2/src/engine.cpp.o
[ 72%] Building CXX object CMakeFiles/BitAndNibbly.dir/data/tinyci_build/daid/SeriousProton2/src/graphics/graphicslayer.cpp.o
[ 73%] Building CXX object CMakeFiles/BitAndNibbly.dir/data/tinyci_build/daid/SeriousProton2/src/window.cpp.o
CMakeFiles/BitAndNibbly.dir/build.make:3494: recipe for target 'CMakeFiles/BitAndNibbly.dir/data/tinyci_build/daid/SeriousProton2/src/window.cpp.o' failed
CMakeFiles/Makefile2:183: recipe for target 'CMakeFiles/BitAndNibbly.dir/all' failed
Makefile:83: recipe for target 'all' failed

/data/tinyci_build/daid/SeriousProton2/src/window.cpp:12:21: fatal error: stb/gif.h: No such file or directory
 #include <stb/gif.h>
                     ^
compilation terminated.
make[2]: *** [CMakeFiles/BitAndNibbly.dir/data/tinyci_build/daid/SeriousProton2/src/window.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/BitAndNibbly.dir/all] Error 2
make: *** [all] Error 2
```


Agreed thanks, Will keep it for now.


:point_right: click here to view a full list of the events :point_left:


![](https://github.trello.services/images/mini-trello-icon.png) [Acordar reunión con el de TAG](https://trello.com/c/BSjz8pn0/10-acordar-reuni%C3%B3n-con-el-de-tag)


We can't rely on the `content-length` header. Since it might contains binary data and `wxString` can't cope with that well. This is why we have the 'FindCompleteMessage` method. It parses the output and searches for a complete JSON message


Нет, не нужно.


### TinyCI build failure:
[make -j 3] returned [2]:
```[  1%] Built target json11
[  9%] Built target box2d
[ 10%] Built target miniz
[ 15%] Built target lua
[ 40%] Built target sp2freetype
[ 68%] Built target bullet
Scanning dependencies of target Mario
[ 68%] Building CXX object CMakeFiles/Mario.dir/src/editor.cpp.o
[ 68%] Building CXX object CMakeFiles/Mario.dir/src/camera.cpp.o
[ 68%] Building CXX object CMakeFiles/Mario.dir/src/coin.cpp.o
[ 68%] Building CXX object CMakeFiles/Mario.dir/src/enemy/smb/blooper.cpp.o
[ 68%] Building CXX object CMakeFiles/Mario.dir/src/enemy/smb/bowser.cpp.o
[ 68%] Building CXX object CMakeFiles/Mario.dir/src/enemy/smb/bullitBill.cpp.o
[ 68%] Building CXX object CMakeFiles/Mario.dir/src/enemy/smb/buzzyBeetle.cpp.o
[ 69%] Building CXX object CMakeFiles/Mario.dir/src/enemy/smb/cheepCheep.cpp.o
[ 69%] Building CXX object CMakeFiles/Mario.dir/src/enemy/smb/cheepCheepJump.cpp.o
[ 69%] Building CXX object CMakeFiles/Mario.dir/src/enemy/smb/goomba.cpp.o
[ 69%] Building CXX object CMakeFiles/Mario.dir/src/enemy/smb/hammerBrother.cpp.o
[ 69%] Building CXX object CMakeFiles/Mario.dir/src/enemy/smb/koopa.cpp.o
[ 69%] Building CXX object CMakeFiles/Mario.dir/src/enemy/smb/lakitu.cpp.o
[ 70%] Building CXX object CMakeFiles/Mario.dir/src/enemy/smb/piranhaPlant.cpp.o
[ 70%] Building CXX object CMakeFiles/Mario.dir/src/enemy/smb/podoboo.cpp.o
[ 70%] Building CXX object CMakeFiles/Mario.dir/src/enemy/smb/spiny.cpp.o
[ 70%] Building CXX object CMakeFiles/Mario.dir/src/fireball.cpp.o
[ 70%] Building CXX object CMakeFiles/Mario.dir/src/hammer.cpp.o
[ 70%] Building CXX object CMakeFiles/Mario.dir/src/main.cpp.o
[ 71%] Building CXX object CMakeFiles/Mario.dir/src/pickup/pickup.cpp.o
[ 71%] Building CXX object CMakeFiles/Mario.dir/src/pickup/smb/life.cpp.o
[ 71%] Building CXX object CMakeFiles/Mario.dir/src/playerGhost.cpp.o
[ 71%] Building CXX object CMakeFiles/Mario.dir/src/playerPawn.cpp.o
[ 71%] Building CXX object CMakeFiles/Mario.dir/src/questionBlock.cpp.o
[ 71%] Building CXX object CMakeFiles/Mario.dir/src/randomLevelGenerator.cpp.o
[ 72%] Building CXX object CMakeFiles/Mario.dir/src/savegame.cpp.o
[ 72%] Building CXX object CMakeFiles/Mario.dir/src/smbLevelBuilder.cpp.o
[ 72%] Building CXX object CMakeFiles/Mario.dir/src/stageSelect.cpp.o
[ 72%] Building CXX object CMakeFiles/Mario.dir/home/tinyci/builds/daid/SeriousProton2/src/engine.cpp.o
[ 72%] Building CXX object CMakeFiles/Mario.dir/home/tinyci/builds/daid/SeriousProton2/src/graphics/graphicslayer.cpp.o
[ 73%] Building CXX object CMakeFiles/Mario.dir/home/tinyci/builds/daid/SeriousProton2/src/window.cpp.o
CMakeFiles/Mario.dir/build.make:4214: recipe for target 'CMakeFiles/Mario.dir/home/tinyci/builds/daid/SeriousProton2/src/window.cpp.o' failed
CMakeFiles/Makefile2:72: recipe for target 'CMakeFiles/Mario.dir/all' failed
Makefile:83: recipe for target 'all' failed

/home/tinyci/builds/daid/SeriousProton2/src/window.cpp:12:21: fatal error: stb/gif.h: No such file or directory
 #include <stb/gif.h>
                     ^
compilation terminated.
make[2]: *** [CMakeFiles/Mario.dir/home/tinyci/builds/daid/SeriousProton2/src/window.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Mario.dir/all] Error 2
make: *** [all] Error 2
```


### TinyCI build failure:
[make -j 3] returned [2]:
```[  1%] Built target miniz
[  1%] Built target json11
[  7%] Built target lua
[ 34%] Built target sp2freetype
[ 44%] Built target box2d
[ 74%] Built target bullet
Scanning dependencies of target ZeroRho
[ 74%] Building CXX object CMakeFiles/ZeroRho.dir/src/main.cpp.o
[ 74%] Building CXX object CMakeFiles/ZeroRho.dir/home/tinyci/builds/daid/SeriousProton2/src/engine.cpp.o
[ 74%] Building CXX object CMakeFiles/ZeroRho.dir/home/tinyci/builds/daid/SeriousProton2/src/graphics/graphicslayer.cpp.o
[ 74%] Building CXX object CMakeFiles/ZeroRho.dir/home/tinyci/builds/daid/SeriousProton2/src/window.cpp.o
CMakeFiles/ZeroRho.dir/build.make:3254: recipe for target 'CMakeFiles/ZeroRho.dir/home/tinyci/builds/daid/SeriousProton2/src/window.cpp.o' failed
CMakeFiles/Makefile2:72: recipe for target 'CMakeFiles/ZeroRho.dir/all' failed
Makefile:83: recipe for target 'all' failed

/home/tinyci/builds/daid/SeriousProton2/src/window.cpp:12:21: fatal error: stb/gif.h: No such file or directory
 #include <stb/gif.h>
                     ^
compilation terminated.
make[2]: *** [CMakeFiles/ZeroRho.dir/home/tinyci/builds/daid/SeriousProton2/src/window.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/ZeroRho.dir/all] Error 2
make: *** [all] Error 2
```


I think the version being in a file is a good enough compromise.

Would it work if CI just overrode the file? That way there's no need of having to introduce a CI-related environment variable into the main script (which ideally shouldn't have any CI-related concepts in it)?


### TinyCI build failure:
[make -j 3] returned [2]:
```[  6%] Built target lua
[ 16%] Built target box2d
[ 16%] Built target json11
[ 17%] Built target miniz
[ 47%] Built target bullet
[ 74%] Built target sp2freetype
Scanning dependencies of target TheArcade
[ 74%] Building CXX object CMakeFiles/TheArcade.dir/src/main.cpp.o
[ 74%] Building CXX object CMakeFiles/TheArcade.dir/data/tinyci_build/daid/SeriousProton2/src/engine.cpp.o
[ 74%] Building CXX object CMakeFiles/TheArcade.dir/data/tinyci_build/daid/SeriousProton2/src/graphics/graphicslayer.cpp.o
[ 74%] Building CXX object CMakeFiles/TheArcade.dir/data/tinyci_build/daid/SeriousProton2/src/window.cpp.o
CMakeFiles/TheArcade.dir/build.make:3278: recipe for target 'CMakeFiles/TheArcade.dir/data/tinyci_build/daid/SeriousProton2/src/window.cpp.o' failed
CMakeFiles/Makefile2:72: recipe for target 'CMakeFiles/TheArcade.dir/all' failed
Makefile:83: recipe for target 'all' failed

/data/tinyci_build/daid/SeriousProton2/src/window.cpp:12:21: fatal error: stb/gif.h: No such file or directory
 #include <stb/gif.h>
                     ^
compilation terminated.
make[2]: *** [CMakeFiles/TheArcade.dir/data/tinyci_build/daid/SeriousProton2/src/window.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/TheArcade.dir/all] Error 2
make: *** [all] Error 2
```