PR_opened/Fix_FiniteDiffTest_Failure_when_serially_run (jmarrec) - 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)


The tutorial is pretty good. Good on ya for keeping at it.


PR_opened/Fix_FiniteDiffTest_Failure_when_serially_run (jmarrec) - x86_64-Linux-Ubuntu-18.04-custom_check: OK (8 of 8 tests passed, 0 test warnings)

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


@JuliaRegistrator register


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

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.1.4 -m "<description of version>" ab1cc9773453891d80e66b6270baaae24bc78072
git push origin v0.1.4
```


PlantComponentContinuedNoBoilers (Myoldmopar) - x86_64-Linux-Ubuntu-18.04-gcc-7.4: OK (2448 of 2451 tests passed, 138 test warnings)

Messages:\n
 * 141 tests had: BND diffs.
 * 95 tests had: MDD diffs.
 * 98 tests had: MTD diffs.
 * 97 tests had: RDD diffs.
 * 3 tests had: Table big diffs.

Failures:\n

regression Test Summary
 * Passed: 672
 * Failed: 3

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


Successfully aliased the URL <https://testing-service-eho18o8y0.now.sh> to the following aliases.

* https://testing-service.dinosowermurky.now.sh
* https://testing-service-git-master.dinosowermurky.now.sh


Switched to upper bound of 0.01 for beta0_gsic to help improve its convergence. Originally, calibrations would often get stuck at a local likelihood maximum where full melt takes place. The converged value is typically < 1 order of magnitude less than 0.01.


Yes, please give more details!


Successfully aliased the URL <https://laneconsultingco-3nk99ueyh.now.sh> to the following aliases.

* https://laneconsulting.co
* https://www.laneconsulting.co
* https://laneconsultingco.jameswlane.now.sh
* https://laneconsultingco-git-master.jameswlane.now.sh


@Gluka #1 should set it to 15


Design System [Figma File](https://www.figma.com/file/aWgwMrzdAuv9VuPdtst64uuw/Style-Guide?node-id=211%3A0)


^ what Joe said.
Adding such lexer classes would really be about providing better
"metadata", not moving "policy" to the ableC grammar.  A lexer class for
numeric literals could be useful e.g. for an extension to use in specifying
lexical precidence for a new terminal.
Eric- not sure why this would require us to be able to "aspect on" more
lexer classes for a terminal defined somewhere else?

On Fri, May 31, 2019, 6:58 AM Joe Blanchard <notifications@github.com>
wrote:

> I think Lucas is thinking that we should add lexer classes when they are
> general enough that they might be useful in more than just Atom
> highlighters. Thus, instead of specifically adding the lexer class such as
> AtomConstantNumeric. We just add a lexer class to identify terminals that
> are numeric literals or we add a lexer class that identifies which
> terminals represent types. Thus, we don't specify a mapping to coloring in
> the Silver grammar itself. Instead, we make it easier to specify the
> mapping in the specification language since we have lexer classes that do a
> better job of generally saying what the terminal represents. With that
> being said, I don't have a strong preference one way or the other as this
> current spec file, while long, did not take long to write so I don't know
> if its necessary to add these lexer classes. However, it may be generally
> useful to increase the specificity of these general lexer classes because I
> don't know where or what they are currently used for in ableC. This would
> make writing specs easier and shorter, but I don't think its necessary to
> add the lexer classes solely for this purpose.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/melt-umn/ableC/commit/552192d7c67a654e5fdabdd25137e3c8db05eb77?email_source=notifications&email_token=ACATLCX3VONF6NJZ6A2YU23PYEVI5A5CNFSM4HRQXDO2YY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBAF672#commitcomment-33750010>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ACATLCUYIKHNHUBZO5N7UW3PYEVI5ANCNFSM4HRQXDOQ>
> .
>


## Jenkins Build Summary

Built from [this commit](https://github.com/ximinez/rippled/commit/2a2a59ac19be27905731335163f1152e741d6e66)

Built at __20190531 - 15:42:52__

### Test Results

Build Type | Log | Result | Status
---------- | --- | ------ | ------
msvc.Debug | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/unl_cast_ripd-1673/13//artifact/msvc.Debug.txt) | 1178 cases, 0 failed, t: 567s | PASS :white_check_mark:
gcc.Release
-Dassert=ON,
MANUAL_TESTS=true | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/unl_cast_ripd-1673/13//artifact/gcc.Release_Dassert_ON_MANUAL_TESTS_true.txt) | 915 cases, 0 failed, t: 4m53s | PASS :white_check_mark:
docs,
TARGET=docs | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/unl_cast_ripd-1673/13//artifact/docs_TARGET_docs.txt) | 1 cases, 0 failed, t: 0m1s | PASS :white_check_mark:
gcc.Debug
-Dcoverage=ON,
TARGET=coverage_report,
SKIP_TESTS=true | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/unl_cast_ripd-1673/13//artifact/gcc.Debug_Dcoverage_ON_TARGET_coverage_report_SKIP_TESTS_true.txt) | 1178 cases, 0 failed, t: 16m32s | PASS :white_check_mark:
clang.Debug | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/unl_cast_ripd-1673/13//artifact/clang.Debug.txt) | 1178 cases, 0 failed, t: 2m44s | PASS :white_check_mark:
msvc.Debug,
NINJA_BUILD=true | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/unl_cast_ripd-1673/13//artifact/msvc.Debug_NINJA_BUILD_true.txt) | 1178 cases, 0 failed, t: 596s | PASS :white_check_mark:
clang.Debug
-Dunity=OFF | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/unl_cast_ripd-1673/13//artifact/clang.Debug_Dunity_OFF.txt) | 1177 cases, 0 failed, t: 3m40s | PASS :white_check_mark:
gcc.Debug | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/unl_cast_ripd-1673/13//artifact/gcc.Debug.txt) | 1178 cases, 0 failed, t: 2m55s | PASS :white_check_mark:
gcc.Debug
-Dunity=OFF | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/unl_cast_ripd-1673/13//artifact/gcc.Debug_Dunity_OFF.txt) | 1177 cases, 0 failed, t: 4m3s | PASS :white_check_mark:
clang.Release
-Dassert=ON | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/unl_cast_ripd-1673/13//artifact/clang.Release_Dassert_ON.txt) | 1178 cases, 0 failed, t: 4m45s | PASS :white_check_mark:
rpm | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/unl_cast_ripd-1673/13//artifact/rpm.txt) | 1178 cases, 0 failed, t: n/a | PASS :white_check_mark:
gcc.Release
-Dassert=ON | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/unl_cast_ripd-1673/13//artifact/gcc.Release_Dassert_ON.txt) | 1178 cases, 0 failed, t: 4m50s | PASS :white_check_mark:
gcc.Debug
-Dstatic=OFF | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/unl_cast_ripd-1673/13//artifact/gcc.Debug_Dstatic_OFF.txt) | 1178 cases, 0 failed, t: 2m53s | PASS :white_check_mark:
msvc.Debug
-Dunity=OFF | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/unl_cast_ripd-1673/13//artifact/msvc.Debug_Dunity_OFF.txt) | 1177 cases, 0 failed, t: 1098s | PASS :white_check_mark:
gcc.Debug,
NINJA_BUILD=true | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/unl_cast_ripd-1673/13//artifact/gcc.Debug_NINJA_BUILD_true.txt) | 1178 cases, 0 failed, t: 2m44s | PASS :white_check_mark:
gcc.Debug
-Dstatic=OFF -DBUILD_SHARED_LIBS=ON | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/unl_cast_ripd-1673/13//artifact/gcc.Debug_Dstatic_OFF_DBUILD_SHARED_LIBS_ON.txt) | 1178 cases, 0 failed, t: 2m50s | PASS :white_check_mark:
msvc.Release | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/unl_cast_ripd-1673/13//artifact/msvc.Release.txt) | 1178 cases, 0 failed, t: 402s | PASS :white_check_mark:
clang.Debug
-Dunity=OFF -Dsan=undefined,
PARALLEL_TESTS=false | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/unl_cast_ripd-1673/13//artifact/clang.Debug_Dunity_OFF_Dsan_undefined_PARALLEL_TESTS_false.txt) | 1177 cases, 0 failed, t: 11m9s | PASS :white_check_mark:
clang.Debug
-Dunity=OFF -Dsan=address,
PARALLEL_TESTS=false,
DEBUGGER=false | [logfile](http://ci.ops.ripple.com/job/ed-rippled/job/unl_cast_ripd-1673/13//artifact/clang.Debug_Dunity_OFF_Dsan_address_PARALLEL_TESTS_false_DEBUGGER_false.txt) | 1177 cases, 0 failed, t: 11m9s | PASS :white_check_mark:


Successfully aliased the URL <https://enworld-twitterbot-o2zbi8ll3.now.sh> to the following aliases.

* https://enworld-twitterbot.wesbaker.now.sh
* https://enworld-twitterbot-git-master.wesbaker.now.sh


@lentschi Can you tell me why you added the peer dependency on the angular/common and angular/core versions to add an upper limit?  With Angular 8 released, this library no longer is working.  Were I to submit a PR, I would like to take this into consideration. - thanks


Yea, you added so many things my eyes are bleeding with so many commits!!!


Nice commit man, got to love them spaces, very intelligent!


<!DOCTYPE html>
<html lang="en">
      <head>
          <meta charset="UTF-8" />
       <title> Bonjour from Cannes !</title>
<head/>
    <body>

</body>
</html>


Successfully aliased the URL <https://monorepo-nextjs-example-enceskj1o.now.sh> to the following aliases.

* https://monorepo-nextjs-example.now.sh
* https://monorepo-nextjs-example.marcin-czenko.now.sh
* https://monorepo-nextjs-example-git-master.marcin-czenko.now.sh


PlantComponentContinuedNoBoilers (Myoldmopar) - 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)


Successfully aliased the URL <https://laneconsultingco-r8zy1ufjo.now.sh> to the following aliases.

* https://laneconsulting.co
* https://www.laneconsulting.co
* https://laneconsultingco.jameswlane.now.sh
* https://laneconsultingco-git-master.jameswlane.now.sh


Wowz, very privatez!! Much skillz!!


Gif


edit menu


this should use apply_ext_one() with scope reference


@JuliaRegistrator register


Successfully aliased the URL <https://puppetron-qrvpdrr28.now.sh> to the following aliases.

* https://puppetron.now.sh
* https://puppetron.cheeaun.now.sh
* https://puppetron-git-master.cheeaun.now.sh


the piece of code does not work, a indefinitely loop happened.


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

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.1.2 -m "<description of version>" 91217d445619ba716bfb4748c29bfb2cbb34d3c7
git push origin v0.1.2
```


PlantComponentContinuedNoBoilers (Myoldmopar) - x86_64-Linux-Ubuntu-18.04-custom_check: OK (8 of 8 tests passed, 0 test warnings)

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


add test in andriod studio


PR_opened/UTF_8 (jmarrec) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-IntegrationCoverage-Debug: OK (660 of 660 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.46%25-green.png)


Successfully aliased the URL <https://laneconsultingco-oi5k4z43v.now.sh> to the following aliases.

* https://laneconsulting.co
* https://www.laneconsulting.co
* https://laneconsultingco.jameswlane.now.sh
* https://laneconsultingco-git-master.jameswlane.now.sh


There were the following issues with your Pull Request

  * Subject must be equal or less than 50

Guidelines are available at https://github.com/OpenNebula/one/blob/master/share/doc/dev/COMMIT_MESSAGES.md

---
This message was auto-generated by https://gitcop.com


Successfully aliased the URL <https://cantyoujust-b3j59i7xz.now.sh> to the following aliases.

* https://cantyouju.st
* https://www.cantyouju.st
* https://cantyoujust.jameswlane.now.sh
* https://cantyoujust-git-master.jameswlane.now.sh


That's great to hear! Although it still slows me down a lot...

I have created issues for *most* of the problems I encountered in [YousefED/typescript-json-schema](https://github.com/YousefED/typescript-json-schema/issues). I had to switch to that module because conditional types (particularily `Omit`) are not supported yet.

But there's something else I want to discuss. There are currently 3 modules that accomplish basically the same goal (at least that I know of), and they all have a **lot** of issues.
[vega/ts-json-schema-generator](https://github.com/vega/ts-json-schema-generator) seems to be the best overall solution, featuring clean(er) code and proper type alias support. However, it doesn't support conditional types (#100), which means `Omit`, `Pick`, `Exclude` etc. arent' supported either (#71, #93). This makes this module completely unusable for me because I heavily use these language features. [YousefED/typescript-json-schema](https://github.com/YousefED/typescript-json-schema) does support these constructs, but it contains a **lot** of bugs (I have reported 8 so far). There's also [xiag-ag/typescript-to-json-schema](https://github.com/xiag-ag/typescript-to-json-schema), but I have no idea what the difference is between this module and it's 'ancestor' (the README only says that this is an 'extended' version).

I see 3 possible solutions for this *forkmania* (though there could be more):

1. Fix [YousefED/typescript-json-schema](https://github.com/YousefED/typescript-json-schema). This can sortof be seen as the 'default' option, as it would leave the current situation mostly untouched. This isn't my preferred solution because the architecture of [vega/ts-json-schema-generator](https://github.com/vega/ts-json-schema-generator) looks a lot better and it doesn't *really* solve the *forkmania*.

2. Write a new generator from scratch, using the knowledge and experience from the other three. If we were to do this we'd of course have the amazing power of hindsight and shared knowledge, which would allow us to write a clean, well-designed and future proof generator. However, this would be very time-consuming and since [vega/ts-json-schema-generator](https://github.com/vega/ts-json-schema-generator) is already very well designed I don't see much reason to do this.

3. Merge all the good parts into [vega/ts-json-schema-generator](https://github.com/vega/ts-json-schema-generator) and 'opening it up' for general usage. I think this would be the best option because it will actually fix the fork issue without consuming a **lot** of time and effort. I think this module currently has the best/cleanest code and I don't see a reason for using one of the others if we increased flexibility and supported more use cases than what vega is doing.

If you're interested I can write up a more detailed overview in a couple of hours. No matter what option you/we choose I'd love to help/fix/develop/maintain.


Ok danke, hatte überlesen das gethostbyname nur IPv4 unterstützt...


AXJB'[ZXB


Collaborator: Review for this commit was created. [Link to review](http://tests-a.collabdevteam.net:8080/ui#review:id=63)


🔥 Device tests completed (Failed) on TvOS on [Azure DevOps](https://dev.azure.com/devdiv/DevDiv/_build/index?buildId=2723355)(TvOS): [Html Report](http://xamarin-storage/jenkins/xamarin-macios/group-xml-results/e21c51044d4e31c9e8fa0be103dc0a4eb57df787/2723355/device-tests/jenkins-results/tests/index.html) 🔥

# Test results

<details>
<summary>113 tests failed, 0 tests passed.</summary>

## Failed tests

 * monotouch-test/tvOS - device/Debug: Failed
 * framework-test/tvOS - device/Debug: Failed
 * interdependent-binding-projects/tvOS - device/Debug: Failed
 * fsharp/tvOS - device/Debug: Failed
 * dont link/tvOS - device/Debug: Failed
 * link all/tvOS - device/Debug: Failed
 * link sdk/tvOS - device/Debug: Failed
 * mono-native-compat/tvOS - device/Debug: Failed
 * mono-native-unified/tvOS - device/Debug: Failed
 * [NUnit] Mono BCL tests group 1/tvOS - device/Debug: Failed
 * [NUnit] Mono BCL tests group 2/tvOS - device/Debug: Failed
 * [xUnit] Mono BCL tests group 3/tvOS - device/Debug: Failed
 * [xUnit] Mono BCL tests group 4/tvOS - device/Debug: Failed
 * mscorlib/tvOS - device/Debug: Failed
 * [xUnit] Mono BCL tests group 6/tvOS - device/Debug: Failed
 * monotouch-test/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * monotouch-test/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * monotouch-test/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * monotouch-test/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * monotouch-test/tvOS - device/Release: Failed
 * monotouch-test/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * monotouch-test/tvOS - device/Debug (dynamic registrar): Failed
 * monotouch-test/tvOS - device/Release (all optimizations): Failed
 * monotouch-test/tvOS - device/Debug (all optimizations): Failed
 * monotouch-test/tvOS - device/Debug: SGenConc: Failed
 * framework-test/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * framework-test/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * framework-test/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * framework-test/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * framework-test/tvOS - device/Release: Failed
 * framework-test/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * interdependent-binding-projects/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * interdependent-binding-projects/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * interdependent-binding-projects/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * interdependent-binding-projects/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * interdependent-binding-projects/tvOS - device/Release: Failed
 * interdependent-binding-projects/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * fsharp/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * fsharp/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * fsharp/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * fsharp/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * fsharp/tvOS - device/Release: Failed
 * fsharp/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * dont link/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * dont link/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * dont link/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * dont link/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * dont link/tvOS - device/Release: Failed
 * dont link/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * link all/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * link all/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * link all/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * link all/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * link all/tvOS - device/Release: Failed
 * link all/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * link sdk/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * link sdk/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * link sdk/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * link sdk/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * link sdk/tvOS - device/Release: Failed
 * link sdk/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * mono-native-compat/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * mono-native-compat/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * mono-native-compat/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * mono-native-compat/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * mono-native-compat/tvOS - device/Release: Failed
 * mono-native-compat/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * mono-native-unified/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * mono-native-unified/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * mono-native-unified/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * mono-native-unified/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * mono-native-unified/tvOS - device/Release: Failed
 * mono-native-unified/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * [NUnit] Mono BCL tests group 1/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * [NUnit] Mono BCL tests group 1/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * [NUnit] Mono BCL tests group 1/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * [NUnit] Mono BCL tests group 1/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * [NUnit] Mono BCL tests group 1/tvOS - device/Release: Failed (MT1032: This application executable might be too large (853 MB) to execute on device. If bitcode was enabled you might want to disable it for development, it is only required to submit applications to Apple.)
 * [NUnit] Mono BCL tests group 1/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * [NUnit] Mono BCL tests group 2/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * [NUnit] Mono BCL tests group 2/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * [NUnit] Mono BCL tests group 2/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * [NUnit] Mono BCL tests group 2/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * [NUnit] Mono BCL tests group 2/tvOS - device/Release: Failed (MT1032: This application executable might be too large (975 MB) to execute on device. If bitcode was enabled you might want to disable it for development, it is only required to submit applications to Apple.)
 * [NUnit] Mono BCL tests group 2/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * [xUnit] Mono BCL tests group 3/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * [xUnit] Mono BCL tests group 3/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * [xUnit] Mono BCL tests group 3/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * [xUnit] Mono BCL tests group 3/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * [xUnit] Mono BCL tests group 3/tvOS - device/Release: Failed (MT1032: This application executable might be too large (708 MB) to execute on device. If bitcode was enabled you might want to disable it for development, it is only required to submit applications to Apple.)
 * [xUnit] Mono BCL tests group 3/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * [xUnit] Mono BCL tests group 4/tvOS - device/AssemblyBuildTarget: dylib (debug): BuildFailure
 * [xUnit] Mono BCL tests group 4/tvOS - device/AssemblyBuildTarget: SDK framework (debug): BuildFailure
 * [xUnit] Mono BCL tests group 4/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): BuildFailure
 * [xUnit] Mono BCL tests group 4/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): BuildFailure
 * [xUnit] Mono BCL tests group 4/tvOS - device/Release: BuildFailure
 * [xUnit] Mono BCL tests group 4/tvOS - device/AssemblyBuildTarget: SDK framework (release): BuildFailure
 * mscorlib/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * mscorlib/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * mscorlib/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * mscorlib/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * mscorlib/tvOS - device/Release: Failed (MT1032: This application executable might be too large (982 MB) to execute on device. If bitcode was enabled you might want to disable it for development, it is only required to submit applications to Apple.)
 * mscorlib/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed (MT1032: This application executable might be too large (559 MB) to execute on device. If bitcode was enabled you might want to disable it for development, it is only required to submit applications to Apple.)
 * mscorlib/tvOS - device/Debug: SGenConc: Failed
 * mscorlib/tvOS - device/Debug (interpreter): Failed
 * mscorlib/tvOS - device/Debug (interpreter -mscorlib): BuildFailure
 * mscorlib/tvOS - device/Release (interpreter -mscorlib): BuildFailure
 * [xUnit] Mono BCL tests group 6/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * [xUnit] Mono BCL tests group 6/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * [xUnit] Mono BCL tests group 6/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * [xUnit] Mono BCL tests group 6/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * [xUnit] Mono BCL tests group 6/tvOS - device/Release: Failed
 * [xUnit] Mono BCL tests group 6/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
</details>


Successfully aliased the URL <https://cantyoujust-5hkawar8i.now.sh> to the following aliases.

* https://cantyouju.st
* https://www.cantyouju.st
* https://cantyoujust.jameswlane.now.sh
* https://cantyoujust-git-master.jameswlane.now.sh


This has to be set back to os.path to work on other systems


Successfully aliased the URL <https://angular-swapi-app-h2xom9ogo.now.sh> to the following aliases.

* https://angular-swapi-app.lonwi.info
* https://angular-swapi-app.lonwi.now.sh
* https://angular-swapi-app-git-master.lonwi.now.sh


could change this to `&& m_uiCouncilDeathCount < 4` encase there is ever a case where m_uiCouncilDeathCount goes higher than 4? Not sure if that would happen, but its a fail-safe at least.


also was this fix a required PR?


Successfully aliased the URL <https://cantyoujust-7a6x3sgz5.now.sh> to the following aliases.

* https://cantyouju.st
* https://www.cantyouju.st
* https://cantyoujust.jameswlane.now.sh
* https://cantyoujust-git-master.jameswlane.now.sh


TeamCity Glyssen / Glyssen pull requests [Build *.*.317.7ebb4ea346400c58ac3e1855ba5e39c5c572d828](http://build.palaso.org/viewLog.html?buildId=152821&buildTypeId=Glyssen_GlyssenPullRequests2) outcome was **SUCCESS**
Summary: Tests passed: 2158, ignored: 18 Build time: 00:08:58


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):
~~~


@registriren You might want to check https://github.com/Neolysion/WTT-Bridge/pull/7


Successfully aliased the URL <https://regexbuilder-le7mhhbl1.now.sh> to the following alias.

* https://regexbuilder-git-master.nieleben.now.sh


🔥 Device tests completed (Failed) on iOS on [Azure DevOps](https://dev.azure.com/devdiv/DevDiv/_build/index?buildId=2723337)(iOS): [Html Report](http://xamarin-storage/jenkins/xamarin-macios/master/26a33946237ea0d9434687a03fb637ab90682445/2723337/device-tests/jenkins-results/tests/index.html) 🔥

# Test results

<details>
<summary>113 tests failed, 0 tests passed.</summary>

## Failed tests

 * monotouch-test/iOS Unified 64-bits - device/Debug: Failed
 * framework-test/iOS Unified 64-bits - device/Debug: Failed
 * interdependent-binding-projects/iOS Unified 64-bits - device/Debug: Failed
 * fsharp/iOS Unified 64-bits - device/Debug: Failed
 * dont link/iOS Unified 64-bits - device/Debug: Failed
 * link all/iOS Unified 64-bits - device/Debug: Failed
 * link sdk/iOS Unified 64-bits - device/Debug: Failed
 * mono-native-compat/iOS Unified 64-bits - device/Debug: Failed
 * mono-native-unified/iOS Unified 64-bits - device/Debug: Failed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/Debug: Failed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/Debug: Failed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/Debug: Failed
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/Debug: Failed
 * mscorlib/iOS Unified 64-bits - device/Debug: Failed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/Debug: Failed
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Failed
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * monotouch-test/iOS Unified 64-bits - device/Release: Failed
 * monotouch-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Failed
 * monotouch-test/iOS Unified 64-bits - device/Debug (dynamic registrar): Failed
 * monotouch-test/iOS Unified 64-bits - device/Release (all optimizations): Failed
 * monotouch-test/iOS Unified 64-bits - device/Debug (all optimizations): Failed
 * monotouch-test/iOS Unified 64-bits - device/Debug: SGenConc: Failed
 * framework-test/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Failed
 * framework-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * framework-test/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * framework-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * framework-test/iOS Unified 64-bits - device/Release: Failed
 * framework-test/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Failed
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Failed
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * interdependent-binding-projects/iOS Unified 64-bits - device/Release: Failed
 * interdependent-binding-projects/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Failed
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Failed
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * fsharp/iOS Unified 64-bits - device/Release: Failed
 * fsharp/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Failed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Failed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * dont link/iOS Unified 64-bits - device/Release: Failed
 * dont link/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Failed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Failed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * link all/iOS Unified 64-bits - device/Release: Failed
 * link all/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Failed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Failed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * link sdk/iOS Unified 64-bits - device/Release: Failed
 * link sdk/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Failed
 * mono-native-compat/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Failed
 * mono-native-compat/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * mono-native-compat/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * mono-native-compat/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * mono-native-compat/iOS Unified 64-bits - device/Release: Failed
 * mono-native-compat/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Failed
 * mono-native-unified/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Failed
 * mono-native-unified/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * mono-native-unified/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * mono-native-unified/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * mono-native-unified/iOS Unified 64-bits - device/Release: Failed
 * mono-native-unified/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Failed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Failed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/Release: Failed
 * [NUnit] Mono BCL tests group 1/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Failed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Failed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/Release: Failed
 * [NUnit] Mono BCL tests group 2/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Failed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Failed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/Release: Failed
 * [xUnit] Mono BCL tests group 3/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Failed
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): BuildFailure
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): BuildFailure
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): BuildFailure
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): BuildFailure
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/Release: BuildFailure
 * [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): BuildFailure
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Failed
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * mscorlib/iOS Unified 64-bits - device/Release: Failed
 * mscorlib/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Failed
 * mscorlib/iOS Unified 64-bits - device/Debug: SGenConc: Failed
 * mscorlib/iOS Unified 64-bits - device/Debug (interpreter): TimedOut
 * mscorlib/iOS Unified 64-bits - device/Debug (interpreter -mscorlib): BuildFailure
 * mscorlib/iOS Unified 64-bits - device/Release (interpreter -mscorlib): BuildFailure
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug): Failed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/Release: Failed
 * [xUnit] Mono BCL tests group 6/iOS Unified 64-bits - device/AssemblyBuildTarget: SDK framework (release): Failed
</details>


Platform independent, starts with the low bit.


I think the worst case can be gotten as the following

[1]    1 token + 2 additional litLen bytes + 15 + 255 (literal) + 2 bytes offset + 4 bytes match, because 5 bytes cannot generate any data, plus 4 bytes match , therefore could be contributed  1 byte extra margin, therefore
32 + compressedsize / (255 + 15)

[2]    1 token + 3 additional litLen bytes + 15 + 255 + 255 (literal) + 2 byte offset + 4 bytes match, 6 bytes cannot generate any data, plus 4 bytes match , therefore could be contributed  2 byte extra margin, therefore
32 + compressedsize /  (255*2 + 15) * 2 === 32 + compressed / (255 + 15/2)
....
[3]    1 token + 4 additional litLen bytes + 15 + 255 + 255 + 255 (literal) + 2 bytes offset + 4 bytes match
32 + compressedsize /  (255*3 + 15) * 3 == 32 + compressedsize / (255 + 15/3)
...

Therefore I think 32 + compressedsize / 255 is the strictly lower bound... But I am not 100% sure, but I will try with
32 + compressedsize / 255.

And I hope this feature get merged into lz4 upstream :)


sharing is caring (yeah I'm snooping your fork hehe) what do these resolve?


This image didn't seem to upload properly.


Now could not deploy this pull request since it contains the following references to invalid secrets in the `env` sections of the `now.json` file:

* `piggy-api-key` (in env: `PIGGY_API_KEY)`

Add those secrets or remove them from the `env` maps in the `now.json` file.


what does this resolve?


Successfully aliased the URL <https://cantyoujust-ms5oe99c9.now.sh> to the following aliases.

* https://cantyouju.st
* https://www.cantyouju.st
* https://cantyoujust.jameswlane.now.sh
* https://cantyoujust-git-master.jameswlane.now.sh


Successfully aliased the URL <https://home-ri675rian.now.sh> to the following aliases.

* https://home.marcelolcarvalho.now.sh
* https://home-git-master.marcelolcarvalho.now.sh


项目讨论


Successfully aliased the URL <https://monorepo-nextjs-example-enceskj1o.now.sh> to the following aliases.

* https://monorepo-nextjs-example.now.sh
* https://monorepo-nextjs-example.marcin-czenko.now.sh
* https://monorepo-nextjs-example-git-master.marcin-czenko.now.sh


Collaborator: Review for this commit was created. [Link to review](http://tests-a.collabdevteam.net:8080/ui#review:id=65)


May be it is possible like "orphanRemoval" `$this->em->getUnitOfWork()->scheduleOrphanRemoval($element);`.
It just need some code...
like
```
        if ($this->orphanRemovals) {
            foreach ($this->orphanRemovals as $orphan) {
                $this->remove($orphan);
            }
        }
```
in UnitOfWork::commit()


Fixed from **trade** to **available**.
Official documentation states that:
- trade: in open orders
- available: for trading
Source: [(https://www.livecoin.net/api/userdata#paymentbalances)]


test


Angelica se necesita realizar cambio en final si.


Successfully aliased the URL <https://home-be12g47xd.now.sh> to the following aliases.

* https://home.marcelolcarvalho.now.sh
* https://home-git-master.marcelolcarvalho.now.sh


[vg CI tests](https://ucsc-ci.com/vgteam/vg/pipelines/827) complete for merge to master.  View the [full report here](http://vg-data.s3.amazonaws.com/vg_ci/vgci_reports/branch/master/index.html).

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

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


Successfully aliased the URL <https://angular-swapi-app-n1moktmu3.now.sh> to the following aliases.

* https://angular-swapi-app.lonwi.info
* https://angular-swapi-app.lonwi.now.sh
* https://angular-swapi-app-git-master.lonwi.now.sh


❌ [Build was (probably) aborted](https://jenkins.internalx.com/job/macios/job/group-xml-results/9/display/redirect)

🔥 [Jenkins job](https://jenkins.internalx.com/job/macios/job/group-xml-results/9/display/redirect) (on internal Jenkins) failed in stage(s) 'Test run, Test run' 🔥

✅ [Build succeeded](https://jenkins.internalx.com/job/macios/job/group-xml-results/9//console)
✅ Packages: [xamarin.ios-12.15.0.212.pkg](https://bosstoragemirror.blob.core.windows.net/wrench/jenkins/group-xml-results/e21c51044d4e31c9e8fa0be103dc0a4eb57df787/9/package/xamarin.ios-12.15.0.212.pkg) [xamarin.mac-5.15.0.212.pkg](https://bosstoragemirror.blob.core.windows.net/wrench/jenkins/group-xml-results/e21c51044d4e31c9e8fa0be103dc0a4eb57df787/9/package/xamarin.mac-5.15.0.212.pkg)
✅ [API Diff (from stable)](http://xamarin-storage/jenkins/xamarin-macios/group-xml-results/e21c51044d4e31c9e8fa0be103dc0a4eb57df787/9/jenkins-results/api-diff/index.html)
🔥 [Failed to compare API and create generator diff](https://jenkins.internalx.com/job/macios/job/group-xml-results/9//console) 🔥
    ** Error: Working directory isn't clean:
    HEAD detached at e21c5104
    Untracked files:
    (use "git add <file>..." to include in what will be committed)

    tests/bcl-test/BCL tests group 1.csproj
    tests/bcl-test/BCL tests group 2.csproj
    tests/bcl-test/BCL tests group 3.csproj
    tests/bcl-test/BCL tests group 4.csproj
    tests/bcl-test/BCL tests group 6.csproj
    tests/bcl-test/Mac OS X BCL tests group 1-mac-full.csproj
    tests/bcl-test/Mac OS X BCL tests group 1-mac-modern.csproj
    tests/bcl-test/Mac OS X BCL tests group 2-mac-full.csproj
    tests/bcl-test/Mac OS X BCL tests group 2-mac-modern.csproj
    tests/bcl-test/Mac OS X BCL tests group 3-mac-full.csproj
    tests/bcl-test/Mac OS X BCL tests group 3-mac-modern.csproj
    tests/bcl-test/Mac OS X BCL tests group 4-mac-full.csproj
    tests/bcl-test/Mac OS X BCL tests group 4-mac-modern.csproj
    tests/bcl-test/generated/
    tests/bcl-test/mscorlib-mac-full.csproj
    tests/bcl-test/mscorlib-mac-modern.csproj
    tests/bcl-test/mscorlib.csproj

    nothing added to commit but untracked files present (use "git add" to track)
    Search for `Comparing API & creating generator diff` in the log to view the complete log.
🔥 [Test run failed](http://xamarin-storage/jenkins/xamarin-macios/group-xml-results/e21c51044d4e31c9e8fa0be103dc0a4eb57df787/9/jenkins-results/tests/index.html) 🔥

# Test results

<details>
<summary>2 tests failed, 169 tests passed.</summary>

## Failed tests

 * monotouch-test/watchOS 32-bits - simulator/Release (all optimizations): Crashed
 * introspection/watchOS 32-bits - simulator/Debug (watchOS 2.0): Crashed
</details>


Setting state to `success` for all statuses.

Only 🤥 (gred) issues found.


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):
~~~


You are not K4.9


oh, sorry. small mistake in this commit


Successfully aliased the URL <https://wes-so-bhuxr2gwm.now.sh> to the following aliases.

* https://wes.dev
* https://wes-so.wessouza.now.sh
* https://wes-so-git-master.wessouza.now.sh


Successfully aliased the URL <https://subway-time-77dhtnnxw.now.sh> to the following aliases.

* https://subwayti.me
* https://subway-time.wessouza.now.sh
* https://subway-time-git-master.wessouza.now.sh


Ref https://github.com/ChildMindInstitute/MATTER-spec-docs/issues/5


Got it. I believe if you retrain with pytorch 1.1 (which is the version fastai recommends now) your models should work again.

On Fri, May 31, 2019 at 2:29 AM, Jack Finnegan < notifications@github.com > wrote:

>
>
>
> I trained it on fast. ai ( http://fast.ai/ ) 's deep learning part 1 google
> cloud setup a few weeks ago. I'm not sure which pytorch it was on.
>
>
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub (
> https://github.com/render-examples/fastai-v3/commit/ce6b234025d52e8a3fa6e4d3efa37a994bb24fd0?email_source=notifications&email_token=AAAOUANHCRGU2JMU4CIVTMTPYDVXBA5CNFSM4HP5UIMKYY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBAF345#commitcomment-33746845
> ) , or mute the thread (
> https://github.com/notifications/unsubscribe-auth/AAAOUAP6BKDLFSWLEAIAAMDPYDVXBANCNFSM4HP5UIMA
> ).
>
>
>


PlantComponentContinuedNoBoilers (Myoldmopar) - Win64-Windows-10-VisualStudio-16: OK (2408 of 2411 tests passed, 138 test warnings)

Messages:\n
 * 141 tests had: BND diffs.
 * 95 tests had: MDD diffs.
 * 98 tests had: MTD diffs.
 * 97 tests had: RDD diffs.
 * 2 tests had: MTR small diffs.
 * 3 tests had: Table big diffs.

Failures:\n

regression Test Summary
 * Passed: 652
 * Failed: 3

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


I think this causes an issue with:
https://github.com/pypa/pip/issues/6230


Successfully aliased the URL <https://subway-time-m0bez08ab.now.sh> to the following aliases.

* https://subwayti.me
* https://subway-time.wessouza.now.sh
* https://subway-time-git-master.wessouza.now.sh


Successfully aliased the URL <https://geeksessionsio-nx2les7wp.now.sh> to the following aliases.

* https://geeksessions.io
* https://geeksessionsio.geeksessions.now.sh
* https://geeksessionsio-git-master.geeksessions.now.sh


PlantComponentContinuedNoBoilers (Myoldmopar) - x86_64-MacOS-10.13-clang: OK (2408 of 2411 tests passed, 138 test warnings)

Messages:\n
 * 141 tests had: BND diffs.
 * 95 tests had: MDD diffs.
 * 98 tests had: MTD diffs.
 * 97 tests had: RDD diffs.
 * 3 tests had: Table big diffs.
 * 1 test had: MTR small diffs.

Failures:\n

regression Test Summary
 * Passed: 652
 * Failed: 3

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


I'm glad to hear that you sorted it out.


Now could not deploy this pull request since the `now.json` file does not contain valid JSON.

	Click here to see the contents of `now.json`

{
  "version": 2,
  "builds": [{ "src": ./start.js "./server.js", "use": "@now/node-server" }]
}

For more information on now.json visit https://zeit.co/docs/features/configuration#now.json.


:tada: :+1: :1st_place_medal:


Successfully aliased the URL <https://subway-time-n62skuir0.now.sh> to the following aliases.

* https://subwayti.me
* https://subway-time.wessouza.now.sh
* https://subway-time-git-master.wessouza.now.sh


... wobei das ja an dieser Stelle fast noch egal wäre, anscheinend wird die Auflösung des Hostname nur als Online-Test genutzt ...
... allerdings ist es generell unschön, 2019 noch IPv4-only-Code irgendwo einzubauen und ich habe hier tatsächlich Boxen, die schon IPv6-only laufen ...


`@JuliaRegistrator register()`


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

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.2 -m "<description of version>" 7be78e331464c6526f38874ab57494570051ad13
git push origin v0.8.2
```


Successfully aliased the URL <https://jameswlanecom-g3t0tzt9f.now.sh> to the following aliases.

* https://jameswlane.com
* https://www.jameswlane.com
* https://jameswlanecom.jameswlane.now.sh
* https://jameswlanecom-git-master.jameswlane.now.sh


That's really strange.


Angelica se necesita realizar cambio en final si.


Properties should be ordered font-size, line-height, margin-top


Properties should be ordered align-items, display, flex-grow


@dutchTender @serra-trinh @JackieBabos ready for integration


做得很好\/\/\/\/


Deployment failed with the following error:

~~~
One or more invalid build specification(s) found
~~~


Successfully aliased the URL <https://jameswlanedev-f8qkyv3kv.now.sh> to the following aliases.

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


Successfully aliased the URL <https://subway-time-76epqdsil.now.sh> to the following aliases.

* https://subwayti.me
* https://subway-time.wessouza.now.sh
* https://subway-time-git-master.wessouza.now.sh


Thank you for letting me know; I have uploaded them again I think they
should be there now.

Thanks,
Chelsea

On Fri, May 31, 2019 at 12:59 AM edouard66 <notifications@github.com> wrote:

> Hi, it seems that plot2.R, plot3.R and plot4.R didn't upload correctly.
> You may want to add them so they can be reviewed.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/cfrench575/ExData_Plotting1/commit/d9f250138a3b755812f59a6710df49a9eb4f5d43?email_source=notifications&email_token=AEHJKUQLJE7NKKFWGXYS6LTPYDLEJA5CNFSM4HRVXN42YY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBAF24N#commitcomment-33745805>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AEHJKUWASE42REVODULG2RLPYDLEJANCNFSM4HRVXN4Q>
> .
>


since you mentioned me in the commit message, now I will be thanked over and over every time somebody pushes this commit to their forks...
it's ok, i'm just flattered :)


For anyone NOT aware, the Sekiro profile addition to the "HitCounterManager.xml" is NOT included in the initial download, so you either a) need to just make the profile yourself, or b) in the above copy lines 1677 thru 1772 and then scroll to the end of the xml to then insert just above "</ProfileList>.


Thanks for the notification, I'll search for the whole commit.


Successfully aliased the URL <https://jameswlanedev-o14cx1vtw.now.sh> to the following aliases.

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


Successfully aliased the URL <https://gatsby-theme-carbon-2vfklxpy2.now.sh> to the following aliases.

* https://gatsby-theme-carbon.now.sh
* https://gatsby-theme-carbon.carbon-design-system.now.sh
* https://gatsby-theme-carbon-git-master.carbon-design-system.now.sh


@JuliaRegistrator register


Error while trying to register: Changing package repo URL not allowed, please submit a pull request with the URL change to the target registry and retry.


Successfully aliased the URL <https://nicollis-jrb4fn0br.now.sh> to the following aliases.

* https://nic.oll.is
* https://nick.oll.is
* https://nicholas.oll.is
* https://nicollis.nicollis.now.sh
* https://nicollis-git-master.nicollis.now.sh


Successfully aliased the URL <https://jameswlanecom-4mhjfw8wv.now.sh> to the following aliases.

* https://jameswlane.com
* https://www.jameswlane.com
* https://jameswlanecom.jameswlane.now.sh
* https://jameswlanecom-git-master.jameswlane.now.sh


备份一下啊  make


PR_opened/Fix_FiniteDiffTest_Failure_when_serially_run (jmarrec) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-UnitTestsCoverage-Debug: OK (1099 of 1099 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-42.12%25-green.png)


Successfully aliased the URL <https://subway-time-o7erj4t64.now.sh> to the following aliases.

* https://subwayti.me
* https://subway-time.wessouza.now.sh
* https://subway-time-git-master.wessouza.now.sh


Collaborator: Review for this commit was created. [Link to review](http://tests-a.collabdevteam.net:8080/ui#review:id=67)


I think @ollierob is correct here - this type is incorrect. If I have time, I will make a new PR next week.


Successfully aliased the URL <https://jameswlanedev-n9jmz98yk.now.sh> to the following aliases.

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


Sorry,
but your suggestion seams to bring  up a  conflict by
"the continuous-integration/appveyor/pr — AppVeyor build failed"

2 hours ago by hgh-esn (committed by GitHub)
4.0-dev c9f1f2c3 ← 4.0-dev 1c1a246c  Failed 2 hours ago in 4 min 34 sec Jobs Job name Tests Duration
Environment: php_ver_target=7.2     4 min 34 sec
Environment: php_ver_target=7.3               47 sec     **-> here it stops**


@ksemaev Needed it to run the exporter with the coin in a pod. But kuberneetes still miss the `depends_on` feature: https://github.com/kubernetes/kubernetes/issues/65502
The alternative was to wrap it a shell script.


Successfully aliased the URL <https://jameswlanecom-2kro4homz.now.sh> to the following aliases.

* https://jameswlane.com
* https://www.jameswlane.com
* https://jameswlanecom.jameswlane.now.sh
* https://jameswlanecom-git-master.jameswlane.now.sh


Successfully aliased the URL <https://paulkinlanme-rjozmlfu1.now.sh> to the following aliases.

* https://paul.kinlan.me
* https://paulkinlanme.kinlan.now.sh
* https://paulkinlanme-git-main.kinlan.now.sh


159行不太明白


Successfully aliased the URL <https://subway-time-iaperhggl.now.sh> to the following aliases.

* https://subwayti.me
* https://subway-time.wessouza.now.sh
* https://subway-time-git-master.wessouza.now.sh


For reference: https://github.com/JuliaRegistries/General/pull/1101


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

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

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

### Deployments updated

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

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


jhljkñ


Hej Henrik!

Såg precis ditt meddelande på slack! Är inte så aktiv i den slacken längre, men fick ett mail om ditt meddelande här. Jag är intresserad av ditt förslag och skrev ett lite längre svar på slacken.

Mvh
Rasmus


Properties should be ordered font-size, line-height, margin-top


Properties should be ordered align-items, display, flex-grow


Successfully aliased the URL <https://subway-time-nxhgwy81y.now.sh> to the following aliases.

* https://subwayti.me
* https://subway-time.wessouza.now.sh
* https://subway-time-git-master.wessouza.now.sh


> 159行不太明白

159行我后面注释掉了，是失误（


I will update this, I don't really need 7.x specific API features.

Question, which parent version should I take? latest?


//coment


Interesting.. shouldn't be required.
https://lerner.co.il/2015/01/18/dont-use-python-close-files-answer-depends/

I'm curious what sort of issue this was causing not having the close?


When I was looking on google I found something on the mailing list talking explicitly about this. http://mail-archives.apache.org/mod_mbox/guacamole-user/201812.mbox/%3CCALKeL-M_WY+DkzKLoefEMMGOqQVS4zQbJDtxYuTq-0RAU1gWwg@mail.gmail.com%3E

I can confirm a few people I know personally who are experiencing this problem.

Would you be kind enough to please like the JIRA ticket here?


Thanks, learning a lot from it haven't build a website from scratch in a
while.

On Fri, May 31, 2019, 11:38 AM Graysen Anson <notifications@github.com>
wrote:

> The tutorial is pretty good. Good on ya for keeping at it.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/jpinfanti/MyProjects/commit/d30612a96f6d7621e729db5c28d71317ff2e0bc9?email_source=notifications&email_token=ADNMIIKTETZBHWQD5NP7SCDPYFA7DA5CNFSM4HR32MIKYY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBAGAJS#commitcomment-33751346>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ADNMIIOKHAUC4V3VATWLDFTPYFA7DANCNFSM4HR32MIA>
> .
>


PlantComponentContinuedNoBoilers (Myoldmopar) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-UnitTestsCoverage-Debug: OK (1099 of 1099 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-41.8%25-green.png)


I will update the code to use org.sonar.api.utils.log.Logger. Better I guess?


As mentioned before, if the compressed block starts with a long run of literals, the distance between `ip` and `op` actually increases, therefore getting farther away from any risk of overwrite.

To get into trouble, the compressed block must start with a match.

Then, presuming we have this condition that `compressedSize < decompressedSize`, the shrinkage perspective of this first match depends on how much local expansion is possible by a _later_ along run of literals. That's where the `/ 255` happens.
However, the `/ 255` proportion is _on the literals_, not on the _total_ compressed nor decompressed size.

If one uses the decompressed size as base, the total size also includes the match length, which must be at least as large as the nb of additional bytes for literal length, in order to respect the condition `compressedSize < decompressedSize`.

If one uses the compressed size as base, the nb of literals cannot represent the whole compressed data : at most it represents 255/266 of compressed data, because the 256th byte is the additional byte for literal length.

So, in both cases, `/ 256`, hence `>> 8`, seems to work properly.

I can replace `>> 8` by `/ 256` if that feels proper. On `unsigned` value, the compiler _should_ be smart enough to make this transformation. On `signed` values, that's less clear, because I'm not sure if rounding is the same. But that could be considered a topic of secondary importance.

Using `compressedSize` as base instead of `decompressedSize` has the perspective of making the margin smaller, which is good. However, it also requires the user to provide both values (`compressedSize` and `decompressedSize`) in order to calculate `LZ4_DECOMPRESS_INPLACE_BUFFER_SIZE()`, making this macro slightly more complex to use.
Yet that doesn't sound unreasonable. In order for in-place decompression to work, it seems mandatory to know both sizes anyway.


I created a different branch for this: https://github.com/troosan/sonar-scm-jazzrtc/tree/update_to_latest_lts_version


no destructors?


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

Created multidev environment [ci-253](https://dashboard.pantheon.io/sites/2266d250-4a93-49c0-b38f-25a486e2eaf9#ci-253) for maginative.


Раскомментируй строчку, иначе у тебя не будет какого-либо таймаута регена маны и ХП. Т.е. они будут прокать каждые __critterIdle (выставленный в 5 внутри config.fos) секунд.


"return;" void-функциям не нужен.


🔥 Device tests completed (Failed) on TvOS on [Azure DevOps](https://dev.azure.com/devdiv/DevDiv/_build/index?buildId=2723338)(TvOS): [Html Report](http://xamarin-storage/jenkins/xamarin-macios/master/26a33946237ea0d9434687a03fb637ab90682445/2723338/device-tests/jenkins-results/tests/index.html) 🔥

# Test results

<details>
<summary>113 tests failed, 0 tests passed.</summary>

## Failed tests

 * monotouch-test/tvOS - device/Debug: Failed
 * framework-test/tvOS - device/Debug: Failed
 * interdependent-binding-projects/tvOS - device/Debug: Failed
 * fsharp/tvOS - device/Debug: Failed
 * dont link/tvOS - device/Debug: Failed
 * link all/tvOS - device/Debug: Failed
 * link sdk/tvOS - device/Debug: Failed
 * mono-native-compat/tvOS - device/Debug: Failed
 * mono-native-unified/tvOS - device/Debug: Failed
 * [NUnit] Mono BCL tests group 1/tvOS - device/Debug: Failed
 * [NUnit] Mono BCL tests group 2/tvOS - device/Debug: Failed
 * [xUnit] Mono BCL tests group 3/tvOS - device/Debug: Failed
 * [xUnit] Mono BCL tests group 4/tvOS - device/Debug: Failed
 * mscorlib/tvOS - device/Debug: Failed
 * [xUnit] Mono BCL tests group 6/tvOS - device/Debug: Failed
 * monotouch-test/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * monotouch-test/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * monotouch-test/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * monotouch-test/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * monotouch-test/tvOS - device/Release: Failed
 * monotouch-test/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * monotouch-test/tvOS - device/Debug (dynamic registrar): Failed
 * monotouch-test/tvOS - device/Release (all optimizations): Failed
 * monotouch-test/tvOS - device/Debug (all optimizations): Failed
 * monotouch-test/tvOS - device/Debug: SGenConc: Failed
 * framework-test/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * framework-test/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * framework-test/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * framework-test/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * framework-test/tvOS - device/Release: Failed
 * framework-test/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * interdependent-binding-projects/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * interdependent-binding-projects/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * interdependent-binding-projects/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * interdependent-binding-projects/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * interdependent-binding-projects/tvOS - device/Release: Failed
 * interdependent-binding-projects/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * fsharp/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * fsharp/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * fsharp/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * fsharp/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * fsharp/tvOS - device/Release: Failed
 * fsharp/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * dont link/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * dont link/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * dont link/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * dont link/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * dont link/tvOS - device/Release: Failed
 * dont link/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * link all/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * link all/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * link all/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * link all/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * link all/tvOS - device/Release: Failed
 * link all/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * link sdk/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * link sdk/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * link sdk/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * link sdk/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * link sdk/tvOS - device/Release: Failed
 * link sdk/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * mono-native-compat/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * mono-native-compat/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * mono-native-compat/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * mono-native-compat/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * mono-native-compat/tvOS - device/Release: Failed
 * mono-native-compat/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * mono-native-unified/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * mono-native-unified/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * mono-native-unified/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * mono-native-unified/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * mono-native-unified/tvOS - device/Release: Failed
 * mono-native-unified/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * [NUnit] Mono BCL tests group 1/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * [NUnit] Mono BCL tests group 1/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * [NUnit] Mono BCL tests group 1/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * [NUnit] Mono BCL tests group 1/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * [NUnit] Mono BCL tests group 1/tvOS - device/Release: Failed (MT1032: This application executable might be too large (853 MB) to execute on device. If bitcode was enabled you might want to disable it for development, it is only required to submit applications to Apple.)
 * [NUnit] Mono BCL tests group 1/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed (Install failed, exit code: 137.)
 * [NUnit] Mono BCL tests group 2/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * [NUnit] Mono BCL tests group 2/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * [NUnit] Mono BCL tests group 2/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * [NUnit] Mono BCL tests group 2/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * [NUnit] Mono BCL tests group 2/tvOS - device/Release: Failed (MT1032: This application executable might be too large (975 MB) to execute on device. If bitcode was enabled you might want to disable it for development, it is only required to submit applications to Apple.)
 * [NUnit] Mono BCL tests group 2/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed (Install failed, exit code: 137.)
 * [xUnit] Mono BCL tests group 3/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * [xUnit] Mono BCL tests group 3/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * [xUnit] Mono BCL tests group 3/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * [xUnit] Mono BCL tests group 3/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * [xUnit] Mono BCL tests group 3/tvOS - device/Release: Failed (MT1032: This application executable might be too large (708 MB) to execute on device. If bitcode was enabled you might want to disable it for development, it is only required to submit applications to Apple.)
 * [xUnit] Mono BCL tests group 3/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * [xUnit] Mono BCL tests group 4/tvOS - device/AssemblyBuildTarget: dylib (debug): BuildFailure
 * [xUnit] Mono BCL tests group 4/tvOS - device/AssemblyBuildTarget: SDK framework (debug): BuildFailure
 * [xUnit] Mono BCL tests group 4/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): BuildFailure
 * [xUnit] Mono BCL tests group 4/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): BuildFailure
 * [xUnit] Mono BCL tests group 4/tvOS - device/Release: BuildFailure
 * [xUnit] Mono BCL tests group 4/tvOS - device/AssemblyBuildTarget: SDK framework (release): BuildFailure
 * mscorlib/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * mscorlib/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * mscorlib/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * mscorlib/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * mscorlib/tvOS - device/Release: Failed (Install failed, exit code: 137.)
 * mscorlib/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed (Install failed, exit code: 137.)
 * mscorlib/tvOS - device/Debug: SGenConc: Failed
 * mscorlib/tvOS - device/Debug (interpreter): Failed
 * mscorlib/tvOS - device/Debug (interpreter -mscorlib): BuildFailure
 * mscorlib/tvOS - device/Release (interpreter -mscorlib): BuildFailure
 * [xUnit] Mono BCL tests group 6/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * [xUnit] Mono BCL tests group 6/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * [xUnit] Mono BCL tests group 6/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * [xUnit] Mono BCL tests group 6/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * [xUnit] Mono BCL tests group 6/tvOS - device/Release: Failed
 * [xUnit] Mono BCL tests group 6/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
</details>


why did you drop these field
fields_to_drop = ['instant', 'dteday', 'season', 'weathersit',
'weekday', 'atemp', 'mnth', 'workingday', 'hr']
beause create ddummy variable for season,weather,weekday,month,hr but for  'instant', 'dteday', atemp,workingday why?


J


Во-первых, опечатка: "ST_ST_MANA != ST_MANA"
Во-вторых, к тому же, это не "ParamBase", а "StatBase", т.к. "ST_ST_MANA" находится в диапазоне до 200-го индекса.


Нет точки вызова данной функции. Да и в целом, данный функционал выглядит подозрительно.


Исправь, расширь, дополни. И там посмотрим. Пока что я это не могу залить на мейн.
I'm sorry, but your "push request" was denied.


That's good to hear. Thanks @dominikh! Looks like I was running this update
around that time so I ran into this issue.

On our end this commit still makes sense because we shouldn't install lint
dependencies if we're not going to run lint.


Possibly a better clean-up was possible here, but this should do.


Deployment failed with the following error:

~~~
The property `dotenv` is not allowed in now.json when using Now 2.0 – please remove it.
~~~


Hola @Nandosoga,
Me alegra que el documento te haya resultado útil.
Para descargar los datos puedes entrar en el archivo, pinchar en RAW y después guardar la página.

Saludos!


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

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

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

### Deployments updated

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

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


Would you mind writing meaningful commit messages, it will help the community understand what you are doing. Thank you 😃


@JuliaRegistrator register


Deployment failed with the following error:

~~~
Builds rate limit exceeded (0 of 32 remaining). Try again in 60m
~~~


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

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.2 -m "<description of version>" fe25c8111a980942ff5ab8e675507e084118979f
git push origin v0.6.2
```


Deployment failed with the following error:

~~~
Uploading failed. Please try again.
~~~


@SOF3 you can check plugin ? but because it's been a long time since I updated and posted the draft


Aquí creamos la misión de Red Skull. #9

Blah Blah Blah


点头，我修改完id以后也发现应该这样做，我发现我没办法及时收到github的评论回复


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 6, column 9) 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/UnknownBallin/ServerInfoUI/settings/hooks) — see the webhook starting with `https://poggit.pmmp.io/webhooks.gh.repo` and look for the delivery with ID `4f0a07b2-83c4-11e9-9f9e-6d5ff87c4472`.

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


增加 CourseRepository 和 StudentCourseRepository


lol. invalidated the key.


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 6, column 9) 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/UnknownBallin/ServerInfoUI/settings/hooks) — see the webhook starting with `https://poggit.pmmp.io/webhooks.gh.repo` and look for the delivery with ID `96b81a72-83c4-11e9-8b50-f591816180a1`.

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

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


This 'Login' project is a code that creates a login window at the beginning of the program.
'Mainprocess' is the class that makes the login run.
'LoginWindow' is a class that creates buttons and configurations in the login window
'TestFrm' is a class that creates a window that opens upon successful login

From KIMMIJEONG


hey i just noticed that you were pushing some commits directly to master - our standard guidelines are to create a branch and PR instead.  I'm happy to give a full walkthrough on the process sometime if you'd like too


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 6, column 9) 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/UnknownBallin/ServerInfoUI/settings/hooks) — see the webhook starting with `https://poggit.pmmp.io/webhooks.gh.repo` and look for the delivery with ID `e0a335ea-83c4-11e9-91a2-cef066d20d49`.

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


增加  StudentCourseRepository 和 CourseRepository


aho


On Fedora 30 it's this in case anyone is here

    $ sudo dnf install gtk3-devel
    $ sudo dnf install libappindicator-gtk3-devel.x86_64


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 6, column 9) 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/UnknownBallin/ServerInfoUI/settings/hooks) — see the webhook starting with `https://poggit.pmmp.io/webhooks.gh.repo` and look for the delivery with ID `0dd727e2-83c5-11e9-8312-cf0aa90d4980`.

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


please add units here


Again, units


Successfully aliased the URL <https://gatsby-theme-carbon-kf4a7qez3.now.sh> to the following aliases.

* https://gatsby-theme-carbon.now.sh
* https://gatsby-theme-carbon.carbon-design-system.now.sh
* https://gatsby-theme-carbon-git-master.carbon-design-system.now.sh


i think ok


You can select up to 200 call agents belonging to the following groups or mailing lists:

- Office 365 group
- Security group
- Distribution list

Call agents must be either:


Successfully aliased the URL <https://ollis-2muuncg4k.now.sh> to the following aliases.

* https://oll.is
* https://api.oll.is
* https://ollis.nicollis.now.sh
* https://ollis-git-master.nicollis.now.sh


yes. the variable "isTriangle" will be set to either true or false based on what is value is returned from the javascript function.


Successfully aliased the URL <https://blackdogmetalwood-hby2z4i2g.now.sh> to the following aliases.

* https://blackdogmetalwood.jrusk.now.sh
* https://blackdogmetalwood-git-master.jrusk.now.sh


Can you walk us through the bugs that are fixed or features that are added by each bump?


Successfully aliased the URL <https://mdx-9cpfnbgom.now.sh> to the following aliases.

* https://mdxjs.com
* https://www.mdxjs.com
* https://mdx.mdx.now.sh
* https://mdx-git-master.mdx.now.sh


There should be `;` here, rigtht?


Deployment failed with the following error:

~~~
Builds rate limit exceeded (32 of 32 remaining). Try again in 60m
~~~


wa ga naii


Corregido en 125903bffb3ca82fbc227c9fb066c3829cbd3cd2


CAN YOU RE UPLOAD THE MAIN.PY FILE PLEASE?


l


En la configuración, le faltó más cosas para que en cada prueba de  toda la carpeta se reinicie la db.


Hola Rafa!! he refactorizado un poco el codigo que hemos hecho esta mañana, he incorporado la clase que ya habia prediseñada y he añadido alguna funcion mas, miratelo a ver como lo ves y si podemos hacer algo mejor. En todo caso he comentado cada linea de codigo, espero que se entienda. Saludos!


Meant for #148


@oleavr This maybe should have been a PR


Successfully aliased the URL <https://jolveradev-1xz1bqupa.now.sh> to the following aliases.

* https://jolvera.dev
* https://jolvera.now.sh
* https://jolveradev.jolvera.now.sh
* https://jolveradev-git-master.jolvera.now.sh


帮大忙了ψ(｀∇´)ψ


PlantMassFlowRatesChangeForTankSourceSide (yzhou601) - x86_64-MacOS-10.13-clang: OK (2412 of 2412 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)


Successfully aliased the URL <https://blackdogmetalwood-f5ltxd24e.now.sh> to the following aliases.

* https://blackdogmetalwood.com
* https://www.blackdogmetalwood.com
* https://blackdogmetalwood.jrusk.now.sh
* https://blackdogmetalwood-git-master.jrusk.now.sh


Probably yes (if you need it in C). Try it :).

I'd suggest you to experiment with micro changes in separate branch. Those type fixes do not require good js knowledge.


@AHOHNMYC, зайди в мумбель, если где-то поблизости.


Вадим, А зачем так делать? Почти все методы помеченные устаревшими, реально нигде не используются. Их можно было просто сразу снести. Из всех методов испльзуется только 1. И тоже только в одном классе. Может было проще сразу переписать класс на новые методы. Чем оставлять в коде кучу мусора. который не понятно когда будет удален.


Thx


Yeah sorry for jumping the gun on this one.


@tatikamsetti This removed the core change that was introduced in https://github.com/netspotau/moodle-mod_mediagallery/commit/d38cbd3b1841b68e0e1f6a201ab61c9ee6f988a7#diff-4e7bb40584b55a44f4657b188986bff4R100


Incredible work here.


Wo agreed of that? You just broke wifi on cooker.


@vweevers Should I revert it and clean up my mess? Sorry again.


If I calculate it correctly, this will wrap around ~ every 24 days:

2147483647 / 1000 / 86400


Successfully aliased the URL <https://uzhackintosh-n4ie33ne9.now.sh> to the following aliases.

* https://uzhackintosh.sakhib.now.sh
* https://uzhackintosh-git-master.sakhib.now.sh


Successfully aliased the URL <https://jinzhe-blog-loqbqe9g4.now.sh> to the following aliases.

* https://jinzhe-blog.njzjz.now.sh
* https://jinzhe-blog-git-hexo.njzjz.now.sh


I'm sure you are still working on this but "len" is defined as size_t before this resulting in "error: conflicting types for 'len'" during compilation


LOG_WARNING or you redefining to LOG_WARN?


save에 레벨도 포함해야함


It's probably fine, I don't have enough context. Could you explain what changed between `cmakejs` v3 and v5 that necessitates a major bump here?


Здесь абсолютно зря добавлена дублирующая ссылка на NSubstitute.


@tatikamsetti This looks like it should have been included in the previous core edit https://github.com/ccle/moodle-mod_mediagallery/commit/f11940d8fef911c34b9a48ed3d28af894177b22f


PlantMassFlowRatesChangeForTankSourceSide (yzhou601) - x86_64-Linux-Ubuntu-18.04-gcc-7.4: OK (2452 of 2452 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)


Successfully aliased the URL <https://athleticgeekr2h-rmbovroai.now.sh> to the following aliases.

* https://athleticgeekr2h.kmkee.now.sh
* https://athleticgeekr2h-git-master.kmkee.now.sh


Successfully aliased the URL <https://notice-andres-coello-h83xkryf6.now.sh> to the following aliases.

* https://notice-andres-coello.goyeselcoca.now.sh
* https://notice-andres-coello-git-master.goyeselcoca.now.sh


Successfully aliased the URL <https://athleticgeekr2h-bj8bq8ce4.now.sh> to the following aliases.

* https://athleticgeekr2h.kmkee.now.sh
* https://athleticgeekr2h-git-master.kmkee.now.sh


sure, missed this


The two changes I found are:
- It no longer selects C++11, so native modules relying on this behavior will fail to compile.
- npm config integration is now case-sensitive.


old version


是我我也偷


good looking now


Now could not deploy this pull request since the `now.json` file does not contain valid JSON.

	Click here to see the contents of `now.json`

{
  "version": 2,
  "alias": "ariesliving.com",
  "builds": [{ "src": "next.config.js", "use": "@now/next@canary" }]
  // "routes": [
  //   {
  //     "src": "/learn/?",
  //     "status": 301,
  //     "headers": { "Location": "/learn/basics/getting-started" }
  //   },
  //   {
  //     "src": "/features/?",
  //     "status": 301,
  //     "headers": { "Location": "/features/static-exporting" }
  //   },
  //   {
  //     "src": "/features/ssr/?",
  //     "status": 301,
  //     "headers": { "Location": "/features/server-side-rendering" }
  //   },
  //   {
  //     "src": "/case-studies/?",
  //     "status": 301,
  //     "headers": {
  //       "Location": "/case-studies/hulu"
  //     }
  //   },
  //   {
  //     "src": "/showcase/(?<item>[^/]*)",
  //     "dest": "/www/showcase?item=$item"
  //   },
  //   {
  //     "src": "/feed.xml",
  //     "dest": "/www/_next/static/feed.xml"
  //   },
  //   { "src": "(.*)", "dest": "/www$1" }
  // ]
}

For more information on now.json visit https://zeit.co/docs/features/configuration#now.json.


PlantMassFlowRatesChangeForTankSourceSide (yzhou601) - 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)


Successfully aliased the URL <https://jinzhe-blog-5anxfy9rf.now.sh> to the following aliases.

* https://jinzhe-blog.njzjz.now.sh
* https://jinzhe-blog-git-hexo.njzjz.now.sh


hey No issues so far so i will leave it alone


PlantMassFlowRatesChangeForTankSourceSide (yzhou601) - x86_64-Linux-Ubuntu-18.04-custom_check: OK (8 of 8 tests passed, 0 test warnings)

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


Successfully aliased the URL <https://athleticgeekr2h-iucestoys.now.sh> to the following aliases.

* https://athleticgeekr2h.kmkee.now.sh
* https://athleticgeekr2h-git-master.kmkee.now.sh


Downloaded from https://usc.data.socrata.com/widgets/atat-mmad


Bruh wakelock are removed from k4.9 and converted into wakeup sources


> As mentioned before, if the compressed block starts with a long run of literals, the distance between `ip` and `op` actually increases, therefore getting farther away from any risk of overwrite.
>
> To get into trouble, the compressed block must start with a match.
>
> Then, presuming we have this condition that `compressedSize < decompressedSize`, the maximum shrinkage perspective of this first match depends on how much local expansion is possible by a _later_ run of literals. That's where the `/ 255` happens.
> However, the `/ 255` proportion is _on the number of literals_, not on the _total_ compressed nor decompressed size.
>
> If one uses the decompressed size as base, the total size also includes the match length, which must be at least as large as the nb of additional bytes for literal length, in order to respect the condition `compressedSize < decompressedSize`.
>
> If one uses the compressed size as base, the nb of literals cannot represent the whole compressed data : at most it represents 255/266 of compressed data, because the 256th byte is the additional byte for literal length.
>
> So, in both cases, `/ 256`, hence `>> 8`, seems to work properly.
>
> I can replace `>> 8` by `/ 256` if that feels proper. On `unsigned` value, the compiler _should_ be smart enough to make this transformation. On `signed` values, that's less clear, because I'm not sure if rounding is the same. That could be considered a topic of secondary importance though.
>
I think agree with your detailed analysis.

> Using `compressedSize` as base instead of `decompressedSize` has the perspective of making the margin smaller, which is good. However, it also requires the user to provide both values (`compressedSize` and `decompressedSize`) in order to calculate `LZ4_DECOMPRESS_INPLACE_BUFFER_SIZE()`, making this macro slightly more complex to use.
> Yet that doesn't sound unreasonable. In order for in-place decompression to work, it seems mandatory to know both sizes anyway.

But I wonder why need both compressedSize and decompressedSize? If my understanding is correct.
Since decompressedSize > compressedSize, user can give any value which is not less than compressedSize.

Could you give an exact expression in advance? I think we are getting the end, and I will use it for my scenerio...


I'm unsure what you're suggesting?


Successfully aliased the URL <https://athleticgeekr2h-6mrra3og7.now.sh> to the following aliases.

* https://athleticgeekr2h.kmkee.now.sh
* https://athleticgeekr2h-git-master.kmkee.now.sh


just pick this https://github.com/SOVIET-ANDROID/android_device_xiaomi_mido/commit/59249e1aad24306a4ba8211b4213cf30c6375b5c

if you get the error in sepolicy while compiling comment out a change in sepolicy/vendor/file_contexts

Additionally you will need configs for your chip for msm8953 just use this from Tissot

https://github.com/SOVIET-ANDROID/android_device_xiaomi_mido/commit/4f33c4378229c104b8e627b9ae0c343da36a3346
they haven't changed till may pie update


not bad


LGTM 😉

I'll leave this hanging for a day (cc @ralphtheninja @lovell) before publishing to npm.


Successfully aliased the URL <https://amikom-1u7tlsrp5.now.sh> to the following aliases.

* https://amikom.now.sh
* https://amikom.r5u.now.sh
* https://amikom-git-master.r5u.now.sh


The missing DependencyParser class has to do with the way that Eclipse finds/loads in files while debugging, can either use a different IDE or just run straight (or modify files/classpaths); when running without debugger it runs out of memory - not sure if this is standard or -?


i know so far far no issues are caused by this commit so i dont see point of reverting it


No, thank YOU!


PR_opened/Fix_FiniteDiffTest_Failure_when_serially_run (jmarrec) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-IntegrationCoverage-Debug: OK (660 of 660 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.46%25-green.png)


eeee rabotaet


Successfully aliased the URL <https://roadtohire-prkr0zw0j.now.sh> to the following aliases.

* https://roadtohire.tivler.now.sh
* https://roadtohire-git-master.tivler.now.sh


Actually here are all changes

Device tree

https://github.com/SOVIET-ANDROID/android_device_xiaomi_mido/commit/35bc3c1336f9cad6d780e952fef51c6bdb125741

https://github.com/SOVIET-ANDROID/android_device_xiaomi_mido/commit/59249e1aad24306a4ba8211b4213cf30c6375b5c

https://github.com/SOVIET-ANDROID/android_device_xiaomi_mido/commit/4f33c4378229c104b8e627b9ae0c343da36a3346

Vendor

https://github.com/SOVIET-ANDROID/proprietary_vendor_xiaomi/commit/1cc7bfdc795befadc7b0de283908a1c121610b22


Lighthouse scores

Tested url: https://jimbir.ch/

Best scores across 3 parallel runs:

✅ performance: 99/90

✅ accessibility: 100/90

✅ best-practices: 93/90

✅ seo: 100/90

Detailed reports: run 1, run 2, run 3


NOTE: Superseded by XmlNotepad tool. See repo.


大山有木兮


> But I wonder why need both compressedSize and decompressedSize? If my understanding is correct.
> Since decompressedSize > compressedSize, user can give any value which is not less than compressedSize.

It's indeed not _necessary_.
The current `LZ4_DECOMPRESS_INPLACE_BUFFER_SIZE()` macro only uses `decompressedSize`, resulting  in a margin which is "large enough".

Using the `compressedSize` instead to calculate `LZ4_DECOMPRESS_INPLACE_MARGIN` is only useful to _reduce_ the margin to some minimum length.
It's more a refinement than a necessity.


Created multidev environment [index-to-records#ci-179](https://dashboard.pantheon.io/sites/d8404382-ee59-443c-94c3-1ba439cfbe46#ci-179).

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


> No, that should be fine. `const` means you can't reassign the variable again. What you are thinking about is immutable objects (which there is no such keyword in JS).

There is a good library for this though:
https://github.com/immutable-js/immutable-js
https://www.npmjs.com/package/immutable


This is a concern. Have a look here for a detailed description: https://blog.b9lab.com/selfdestruct-is-a-bug-9c312d1bb2a5

What I would suggest you do is migrate your `isAlive` feature to `Pausable` and make it so a killed contract is Paused and cannot be restarted. Try to roll all of that up into Pausable so the implementation contract doesn't need to be concerned with it.


@jongalloway Phil is listed twice ... https://dotnetfoundation.org/about


I was mulling this over and my intuition was that it would be better to have Windows code similar independent of compiler...

What's strange is it compiles at all, which makes me think this is dead code?

Anyway I'm don't feel strongly about this, say what you prefer and I'll go with it.


Hi Palmer,
I have modified this document locally and would like to check if the way I revise it is no problem to you and RISC-V folks. I just revised some of the content of the original one you committed.  Do you mind to give me the right to PR and check the modifications I made? That will be not the real pull request, just the preview. We can delete it later.
Abner


You can push this concern into the Pausable contract so this contract doesn't need to be concerned with it.


TeamCity Glyssen / Glyssen pull requests [Build *.*.318.124b0d57a1fcedd77f2e83fc3e2d9cdaab574c61](http://build.palaso.org/viewLog.html?buildId=152828&buildTypeId=Glyssen_GlyssenPullRequests2) outcome was **SUCCESS**
Summary: Tests passed: 2157, ignored: 18 Build time: 00:08:51


Successfully aliased the URL <https://roadtohire-hz5mo01nx.now.sh> to the following aliases.

* https://roadtohire.tivler.now.sh
* https://roadtohire-git-master.tivler.now.sh


> > But I wonder why need both compressedSize and decompressedSize? If my understanding is correct.
> > Since decompressedSize > compressedSize, user can give any value which is not less than compressedSize.
>
> It's indeed not _necessary_.
> The current `LZ4_DECOMPRESS_INPLACE_BUFFER_SIZE()` macro only uses `decompressedSize`, resulting in a margin which is "large enough".
>
> Using the `compressedSize` instead to calculate `LZ4_DECOMPRESS_INPLACE_MARGIN` is only useful to _reduce_ the margin to some minimum length.
> It's more a refinement than a necessity.

Yes, it depends on you :) but erofs will use LZ4_DECOMPRESS_INPLACE_BUFFER_SIZE and pass compressedSize for our usage.

Thanks for taking time and your kindly help. I think I have no problem about this feature. :)

Thanks,
Gao Xiang


$guid relece with this X4323GFSERGF43454GSFGBCCB3


Cool. Please check spelling and grammar for the new text. Much like testing your code before creating a pull request, check your text before sending it through to me. Please?


I think you can address these modes with Pausable so the Remittance contract doesn't get cluttered up details. It will be easier to see the logic of it when it's all in one place.


Successfully aliased the URL <https://athleticgeekr2h-befpnrlca.now.sh> to the following aliases.

* https://athleticgeekr2h.kmkee.now.sh
* https://athleticgeekr2h-git-master.kmkee.now.sh


s/Ddata/Data/

I just tried to upload field notes and got a 500 error.


Czemu metoda jest zakomentowana?


Successfully aliased the URL <https://roadtohire-hkl4sfksd.now.sh> to the following aliases.

* https://roadtohire.tivler.now.sh
* https://roadtohire-git-master.tivler.now.sh


Zmiany dotyczące heroku powinny być wrzucane na gita w heroku, tutaj nie powinny być widoczne


Changed to read the port from gsql.cfg.


don't forget the DS renders 18-bit color :P

rârp


The alias `SiteWeb.ScheduleController.LineController` is not alphabetically ordered among its group.


Thanks @bavariancake  I checked, everything is as it should be. when I click print screen again, it doesn't turn my trackpad back on. i'll have to play around in the bios and figure it out.


Здесь email можно взять из user'а


И это тогда будет не нужно


Note : you can use `compressedSize` for `LZ4_DECOMPRESS_INPLACE_MARGIN()`,
but don't use it for `LZ4_DECOMPRESS_INPLACE_BUFFER_SIZE()` !
This would result in a wrong buffer size calculation.

As mentioned earlier, I suspect your use case only needs `LZ4_DECOMPRESS_INPLACE_MARGIN()`, where it's fine to use `compressedSize`.

I'll update the documentation to make sure this difference is clearly understood.


@JuliaRegistrator register


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

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.7 -m "<description of version>" cffec2b5e4543177d060c57ba46f9a730cebd115
git push origin v0.3.7
```
Also, note the warning: Version 0.3.7 skips over 0.3.6
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.


Moduł dodany dwa razy


PR_opened/UTF_8 (jmarrec) - Win64-Windows-10-VisualStudio-16: OK (2411 of 2411 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)


i meant to say did the header all the way down.


Маловатый шрифт :)