beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vascokk <>
Subject [GitHub] beam pull request #2572: [BEAM-1829] MQTT not working on ARM devices
Date Tue, 18 Apr 2017 09:23:12 GMT
GitHub user vascokk opened a pull request:

    [BEAM-1829] MQTT not working on ARM devices

    This fixes BEAM-1829. Updated snappy-java version.
    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [x] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [x] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [x] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](

You can merge this pull request into a Git repository by running:

    $ git pull master

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2572
commit 45975008363d243d09502c7213a25c3486595d7e
Author: Vassil Kolarov <>
Date:   2017-03-29T14:02:36Z

    Changed snappy version to 1.1.4-M3

commit a9b4ad06eff47b2fc033122f4160f0519ee9491b
Author: Vassil Kolarov <>
Date:   2017-03-29T14:02:36Z

    Changed snappy version to 1.1.4-M3

commit bc0936ed6c431fc7d4a8a91afb09d25009b6f8d4
Author: Vassil Kolarov <>
Date:   2017-03-29T15:47:56Z

    Merge branch 'master' of

commit 446a46a7e6db6b043bb08ef6d71a4f90f91a43e7
Author: Vassil Kolarov <>
Date:   2017-04-03T13:59:36Z

    Merge remote-tracking branch 'upstream/master'

commit d03ea27a61715ce30dde626b425eeeb98a8efe9a
Author: Vassil Kolarov <>
Date:   2017-04-18T08:18:28Z

    Merge remote-tracking branch 'upstream/master'


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message