= 0.8.3
=== 3 November, 2010
* GH#8: Nil-check before downcasing attribute key
* GH#25: Proper ruby 1.9 encoding support
* GH#28. Use integers instead of ?? on 1.9, which is just a string.
* including noscript to ElementInclusions , so that hpricot wont fail
when trying to parse a meta tag inside head section when noscript is
present.
* latest changes from fast_xs mainline
* Fixes to get Hpricot running on Rubinius:
* Use free, not XFREE
* Remove RSTRUCT craziness, don't break Array#at
3.0.24
Tagged on GitHub.
* html2haml now properly generates Haml for silent script expressions
nested within blocks.
* IronRuby compatibility. This is sort of a hack: IronRuby reports its
version as 1.9, but it doesn¡Çt support the encoding APIs, so we treat
it as 1.8 instead.
3.0.23
Tagged on GitHub.
* Fix the error message for unloadable modules when running the
executables under Ruby 1.9.2.
* Fix an error when combining old-style and new-style attributes.
3.0.22
Tagged on GitHub.
* Allow an empty line after case but before when.
* Remove vendor/sass, which snuck into the gem by mistake and was causing
trouble for Heroku users (thanks to Jacques Crocker).
* Support the Rails 3.1 template handler API.
3.0.21
Tagged on GitHub.
* Fix the permissions errors for good.
3.0.20
Tagged on GitHub.
* Fix some permissions errors.
3.0.19
Tagged on GitHub.
* Fix the :encoding option under Ruby 1.9.2.
* Fix interpolated if statement when HTML escaping is enabled.
* Allow the --unix-newlines flag to work on Unix, where it¡Çs a no-op.
Changes after 2.2.0 are unknown.
= Change Log
== Version 2.2.0
* Applied patch from Thijs van der Vossen to allow UTF-8 encoded
output when the encoding is UTF-8 and $KCODE is UTF8.
138[tip] 486a5a2a8cd2 2010-09-23 07:15 -0700 ged
Bump version, update the Windows build to use 1.9.2 instead of 1.9.1.
137 1caa0c888dfe 2010-09-17 15:03 -0700 ged
Updated to Discount 1.6.8, caught up with some Discount flags
136 d21afe457b3a 2010-09-17 14:12 -0700 ged
Trying to add a spec to test #68.
135 eb11956b000d 2010-09-17 13:48 -0700 ged
Tried to add a spec to test #67.
134 055519ec5f78 2010-09-17 13:42 -0700 ged
Cleanup, 1.9.2 compatibility, bugfixes.
133 3122e81da65b 2010-09-17 13:25 -0700 ged
Convert to tidy-ext for testing instead of the ffi one (1.9.x compatibility)
132 3f36f96bfb8e 2010-08-16 11:50 -0700 ged
Install extension in arch-specific subdir [RPS]
131 8ccd2cfe599e 2010-08-11 09:54 -0600 ged
Bump version to 2.0.8
130 f2d6de73c6d6 2010-08-11 09:54 -0600 ged
Updated to Discount 1.6.6; add HTML5 tag support.
129 7b1630a0f3b2 2010-08-11 09:27 -0600 ged
Updated for Discount 1.6.4, build system updates.
Sun Nov 14 17:01:07 PST 2010
* Ruby/GSL 1.14.5
* Convert docs from rdtool to rdoc
* Fix object id handling bugs on 64-bit systems
* Fix Vector's handling of Range parameters
Wed Sep 29 00:37:44 BOT 2010
* Modification for ruby-1.9.2
* Replaced STR2CSTR to StringValuePtr
= 0.9.10 ()
* Added Mocha::ObjectMethods#unstub method - https://github.com/floehopper/mocha/issues#issue/6
* Inherit Mocha::ExpectationError from Exception instead of StandardError to reduce the chances of a test passing by accident - thanks to James Sanders (jsanders) - https://github.com/floehopper/mocha/issues#issue/15
* Fixed bug - GitHub README page to link correctly to code examples - https://github.com/floehopper/mocha/issues/closed#issue/11
* Fixed bug - PASSTHROUGH_EXCEPTIONS are defined on MiniTest::Unit::TestCase not in Mocha - thanks to Brian Troutwine (blt) - https://github.com/floehopper/mocha/issues/closed#issue/14
= 0.9.9 (ee3a79db4d52c3339e8acf07505e01236a2b4810)
* Avoid loading bits of the test-unit gem by accident. This is an attempt at
a fix for the problem that James Adam reported [1]. By using 'load' instead
of 'require' to detect the version of Test::Unit, we can avoid rubygems
trying to load bits of the test-unit gem when it's not wanted. [1]
http://floehopper.lighthouseapp.com/projects/22289-mocha/tickets/50#ticket-50-13
* Fix exception when running rake without test-unit gem. When test-unit gem
>=v2.0.0 was installed but the "use_test_unit_gem" MOCHA_OPTIONS was not
specified, a "comparison of Fixnum with Hash failed" exception was being
raised when running the performance tests. This was because bits of the
test-unit gem were being loaded accidentally and a Hash was being
incorrectly supplied to the TestRunner.run method.
* Explicitly require rubygems for running tests via rake using test-unit gem.
* Handle newer versions of test-unit gem (v2.0.2 to v2.0.9)
* Handle newer versions of minitest gem (v1.4.0 to v1.6.0)
* Added warnings about monkey-patching test-unit and minitest to aid
debugging. These are enabled by including "debug" in the MOCHA_OPTIONS
environment variable. This is now a comma-separated list, so that we can
specify multiple options e.g. MOCHA_OPTIONS=debug,use_test_unit_gem
* Eloy Duran (alloy) made the unit tests run on 1.9.2dev r25249.
* Eloy Duran (alloy) also improved some MiniTest TestResult code I'd written
and got the acceptance tests running on Ruby 1.9 HEAD. There are still 4
failures because for some reason the backtrace line numbers are off by
one. And the minitest_test test case does not run when the whole suite is
run with MiniTest. These issues still need investigation.
* Fixed some acceptance tests to run in Ruby 1.9.2 - it's no longer possible
to subvert the protection of a method by calling it via Object#send.
* Fixed "test:performance" rake task so it runs in Ruby 1.9.2.
* Fix test incorrectly failing under Rubinius 1.0. This test imposed too many
constraints. It appears that Object#inspect legitimately calls
Object#object_id in Rubinius. But we're only interested in what 'id'
methods Mocha::ObjectMethods#mocha_inspect calls. By stubbing
Object#inspect we can relax the constraints imposed by the test.
* Luke Redpath (lukeredpath) added new shorthand "any" and "all" composite
parameter matchers using "&" and "|". This provides an alternative syntax
for expecting any or all matchers to pass,
e.g. foo.expects(:bar).with(equals(1) | equals(2)).
* Improved documentation for Expectation#raises. A number of people have
suggested an extension to the API to cope with custom exceptions that have
extra constructor parameters. However, since the arguments supplied to
Expectation#raises are just passed on to Kernel#raise, it's possible to
pass in an instance of an exception. Thus no change to the API is required,
but it does seem worthwhile pointing this out in the docs.
* Corrected RDoc example for Expectation#never thanks to Red David (reddavis).
* Improved RDoc including a change suggested by Rohit Arondekar (rohit).
* Updated gemspec as requested by Sam Woodard (shwoodard).
== 1.0.0 / 2010-11-30
* Major improvements
* Better handling of non-ruby thread callbacks
* Support for releasing the GIL during C function calls
* Minor improvements
* code cleanups
For Ruby 1.9 support, needs ruby-debug-base19 (unpackaged yet).
Changes:
Merged with ruby-debug-ide19, compatibility with ruby 1.9 Fixed segfaults on 1.9
0.10.4
10/27/10
- Various bug fixes:
* reload command.
* plain 'info' command
* improve list and list - (backwards) handling when hitting end of file
- Add ability to specify port to debug on
- Allow breakpoints at class methods
- "quit!" is same as "quit unconditionally"
- irb improvements: Access to non-executing rdebug commands inside irb via
"dbgr" method
- Go over documentation including that created by rdoc.
- For emacs package: add README, INSTALL, AUTHORS.
0.10.4
10/27/10
- Various bug fixes:
* reload command.
* plain 'info' command
* improve list and list - (backwards) handling when hitting end of file
- Add ability to specify port to debug on
- Allow breakpoints at class methods
- "quit!" is same as "quit unconditionally"
- irb improvements: Access to non-executing rdebug commands inside irb via
"dbgr" method
- Go over documentation including that created by rdoc.
- For emacs package: add README, INSTALL, AUTHORS.
=== 2.7.0 / 2010-11-15
* 2 minor enhancements:
* Added new plugin: gem_prelude_sucks. (jbarnette)
* Activate under 1.9 if you don't want it messing with you.
* Added rspec2 support (bleything)
* 1 bug fix:
* require uri in hoe/deps (raggi)
=== 1.3.2 / 2010-10-30 / RubyConf Uruguay Edition!
* Enhancements:
* Windows: build against 3.7.3 version of SQLite3
* SQLite3::Database can now be open as readonly
db = SQLite3::Database.new('my.db', :readonly => true)
* Added SQLite3::SQLITE_VERSION and SQLite3::SQLITE_VERSION_NUMBER [nurse]
* Bugfixes
* type_translation= works along with Database#execute and a block
* defined functions are kept in a hash to prevent GC. #7
* Removed GCC specific flags from extconf.
* DEPRECATIONS
* SQLite3::Database#type_translation= will be deprecated in the future with
no replacement.
* SQlite3::Version will be deprecated in 2.0.0 with SQLite3::VERSION as the
replacement.
** Bugfixes and Improvements
- Allow the repairer to improve the health of a file by uploading
some shares, even if it cannot achieve the configured happiness
threshold. This fixes a regression introduced between v1.7.1 and
v1.8.0. (#1212)
- Fix a memory leak in the ResponseCache which is used during mutable
file/directory operations. (#1045)
- Fix a regression and add a performance improvement in the downloader.
This issue caused repair to fail in some special cases. (#1223)
- Fix a bug that caused 'tahoe cp' to fail for a grid-to-grid copy
involving a non-ASCII filename. (#1224)
- Fix a rarely-encountered bug involving printing large strings to
the console on Windows. (#1232)
- Perform ~ expansion in the --exclude-from filename argument to
'tahoe backup'. (#1241)
- The CLI's 'tahoe mv' and 'tahoe ln' commands previously would try
to use an HTTP proxy if the HTTP_PROXY environment variable was set.
These now always connect directly to the WAPI, thus avoiding giving
caps to the HTTP proxy (and also avoiding failures in the case that
the proxy is failing or requires authentication). (#1253)
- The CLI now correctly reports failure in the case that 'tahoe mv'
fails to unlink the file from its old location. (#1255)
- 'tahoe start' now gives a more positive indication that the node
has started. (#71)
- The arguments seen by 'ps' or other tools for node processes are
now more useful (in particular, they include the path of the
'tahoe' script, rather than an obscure tool named 'twistd'). (#174)
** Removed Features
- The tahoe start/stop/restart and node creation commands no longer
accept the -m or --multiple option, for consistency between platforms.
(#1262)
** Packaging
- We now host binary packages so that users on certain operating systems
can install without having a compiler.
<http://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/README.html>
- Use a newer version of a dependency if needed, even if an older
version is installed. This would previously cause a VersionConflict
error. (#1190)
- Use a precompiled binary of a dependency if one with a sufficiently
high version number is available, instead of attempting to compile
the dependency from source, even if the source version has a higher
version number. (#1233)
** Documentation
- All current documentation in .txt format has been converted to
.rst format. (#1225)
- Added docs/backdoors.rst declaring that we won't add backdoors to
Tahoe-LAFS, or add anything to facilitate government access to data.
(#1216)
From Jan Danielsson in private mail. Miscellaneous changes, including:
* (Gordon Tyler) shell now accepts --directory
* shell now run qbzr commands in a subprocess.
* (Max Bowsher) fetch-ghosts now works again. And has tests.
* conflict-diff no longer requires a single file to be specified. Multiple
files or no files can be specified.
Work has gone in to reducing memory usage in the 2.1 series.
This is a small bugfix release. Upgrading is recommended for anyone
running 2.1.0 or earlier.
Bugfixes:
* Avoid malloc(0) in patiencediff, which is non-portable.
* Fix stub sftp test server to call os.getcwdu().
* Merge correctly when this_tree is not a WorkingTree.
* Warn if pyrex is too old to compile the new SimpleSet and StaticTuple
extensions, rather than having the build fail randomly.
* Services' default vsz_limits weren't being enforced correctly in
earlier v2.0 releases. Now that they are enforced, you might notice
that the default limits are too low and you need to increase them.
This problem will show up in logs as "out of memory" errors.
See default_vsz_limit and service { vsz_limit } settings.
* LMTP: In earlier versions if mail was delivered to user+detail@domain
address, LMTP server always attempted to deliver the mail to mailbox
named "detail". This was rather unintentional and shouldn't have been
the default. lmtp_save_to_detail_mailbox=yes setting now preserves
this behavior (default is no).
+ Added systemd support (configure --with-systemdsystemunitdir).
Based on patch by Christophe Fergeau.
+ Replaced broken mbox-snarf plugin with a new more generic snarf
plugin.
- dbox: Fixes to handling external mail attachments
- verbose_proctitle=yes didn't work for all processes in v2.0.7
- imap, pop3: When service { client_count } was larger than 1, the
log messages didn't use the correct prefix. Last logged in user's
prefix was always used, regardless of what user's session actually
logged it. Now the proper log prefix is always used.
- MySQL: Only the first specified host was ever used
