- 28 Sep, 2015 1 commit
-
-
Josh Haberman authored
Also updated the Gemfile.lock since alpha-4 has been pushed to RubyGems. Change-Id: I8ddc5f125f28aa9a33c88dfe48251a75a877e1d3
-
- 27 Aug, 2015 1 commit
-
-
Feng Xiao authored
-
- 26 Aug, 2015 1 commit
-
-
Feng Xiao authored
Protoc, C++ runtime and Java runtime are updated to v3.0.0-beta-1, other languages are updated to v3.0.0-alpha-4.
-
- 20 Aug, 2015 1 commit
-
-
Josh Haberman authored
Change-Id: I6cf77f01370204ad4bc7b345a040a9a3de1706a0
-
- 13 Aug, 2015 1 commit
-
-
Josh Haberman authored
Change-Id: Ief77de7134e05e07b1a7e3970d49880c2d5e6fe9
-
- 17 Jul, 2015 2 commits
-
-
Josh Haberman authored
Change-Id: If7b1cc0f03f609a7f43ddafc8509b44207c60910
-
Josh Haberman authored
Change-Id: Id008ebac5159f773e1bde8b85acb2626cbd16de8
-
- 16 Jul, 2015 1 commit
-
-
Josh Haberman authored
This involved fixing a few important bugs in the Ruby implementation -- mostly cases of mixing upb field types and descriptor types (upb field types do not distinguish between int/sint/fixed/sfixed like descriptor types do). Also added protobuf-specific exceptions so parse errors can be caught specifically. Change-Id: Ib49d3db976900b2c6f3455c8b88af52cfb86e036
-
- 10 Jul, 2015 1 commit
-
-
Josh Haberman authored
While we are C99 in general, the Ruby build system for building C extensions enables several flags that throw warnings for C89/C90 variable ordering rules. To avoid spewing a million warnings (or trying to specifically override these warnings with command-line flags, which would be tricky and possibly fragile) we conform to Ruby's world of C89/C90. Change-Id: I0e03e62d95068dfdfde112df0fb16a248a2f32a0
-
- 08 Jul, 2015 1 commit
-
-
Josh Haberman authored
Change-Id: I8e2b425f9008e6b82d41d59783bb8b04af1f886f Fixes: https://github.com/google/protobuf/issues/474.
-
- 23 Jun, 2015 1 commit
- 09 Jun, 2015 2 commits
-
-
Josh Haberman authored
upb no longer requires -std=c99 but the Ruby/C code still uses C99 features.
-
Josh Haberman authored
Since this version of upb supports C89, all of the extra compiler flags are no longer required.
-
- 29 May, 2015 1 commit
-
-
Bo Yang authored
-
- 23 May, 2015 1 commit
-
-
teboring authored
-
- 22 May, 2015 1 commit
-
-
Bo Yang authored
-
- 19 May, 2015 1 commit
-
-
Chris Fallin authored
Also fixed lines with > 80 char length.
-
- 15 May, 2015 2 commits
-
-
Tamir Duberstein authored
-
Chris Fallin authored
- Alter encode/decode paths to use the `upb_env` (environment) abstraction. - Update upb amalgamation to upstream `93791bfe`. - Fix a compilation warning (void*->char* cast). - Modify build flags so that upb doesn't produce warnings -- the Travis build logs were pretty cluttered previously.
-
- 14 May, 2015 2 commits
-
-
Chris Fallin authored
-
Adam Greene authored
-
- 13 May, 2015 2 commits
-
-
Chris Fallin authored
- Added RVM-based Ruby test driver that tests MRI and JRuby. - Fixed JRuby compilation (at least in my current setup): force source version to 1.6 (Java 6) to allow generics and annotations. - Modify the skipped JRuby JSON tests so that the exit code is 0 (skip() results in a failing exit code from `rake test`). An upcoming PR should fix JSON under JRuby in general soon.
-
Adam Greene authored
* make consistent between mri and jruby * create a #to_h and have it use symbols for keys * add #to_json and #to_proto helpers on the Google::Protobuf message classes
-
- 02 May, 2015 2 commits
-
-
Adam Greene authored
-
Adam Greene authored
ruby arrays don't throw an exception; they return nil. Lets do the same! this fix also includes the ability to use negative array indicies
-
- 01 May, 2015 2 commits
-
-
Adam Greene authored
starting to make `RepeatedField` quack like an array additional changes: * make sure gemspec gets all ruby code files * add homepage in gem spec removes one of the warnings, and the gem spec authors are pushing everyone to include a homepage in the gem * remove excess whitespace in test suite to bring formatting inline with the rest of the file
-
Adam Greene authored
* update docs to simplify build steps * Gemfile.lock seemed to have an older version specified * do not check in the pkg dir
-
- 13 Apr, 2015 2 commits
-
-
Chris Fallin authored
-
Chris Fallin authored
Includes repro test case from @wfarr.
-
- 10 Mar, 2015 1 commit
-
-
Isaiah Peng authored
-
- 03 Mar, 2015 2 commits
-
-
Chris Fallin authored
Change-Id: Idb29077c153530de78ce28c094442aa8f51ddd25
-
Jisi Liu authored
Change-Id: I33479e529b060e4fed532a827a386d3baecc835e
-
- 23 Feb, 2015 1 commit
-
-
Chris Fallin authored
Change-Id: I54df314660cdb861ad8c4da75a08d4cb97faf638
-
- 21 Feb, 2015 2 commits
-
-
Chris Fallin authored
This update conforms to our two-numbers-after-alpha scheme that allows us to bump the last number if we need to re-upload a gem. (Rubygems does not allow re-use of a version number once a gem is uploaded.) Change-Id: Ia8e7c129d19800afd66f8052785cf5a00462c7ba
-
Chris Fallin authored
Change-Id: I8c3717f549c9b4e9d07c77ec5875c9cd62b296ac
-
- 14 Feb, 2015 1 commit
-
-
Isaiah Peng authored
-
- 13 Feb, 2015 2 commits
-
-
Chris Fallin authored
-
Chris Fallin authored
Previously, we supported map fields in the Ruby DSL. However, we never connected the final link in the chain and generated `map` DSL commands for map fields in `.proto` files. My apologies -- I had been testing with the DSL directly so I missed this. Also fixed a handlerdata-setup-infinite-loop when a map value field's type is its containing message.
-
- 05 Feb, 2015 1 commit
-
-
Chris Fallin authored
-
- 03 Feb, 2015 1 commit
-
-
Isaiah Peng authored
-