Skip to content
This repository was archived by the owner on Mar 24, 2026. It is now read-only.

Make wicket encode its fortunes response in UTF-8#2664

Merged
NateBrady23 merged 1 commit intoTechEmpower:masterfrom
michaelhixson:wicket-fortune-encoding
Apr 6, 2017
Merged

Make wicket encode its fortunes response in UTF-8#2664
NateBrady23 merged 1 commit intoTechEmpower:masterfrom
michaelhixson:wicket-fortune-encoding

Conversation

@michaelhixson
Copy link
Copy Markdown
Contributor

(This replaces a previous PR #2662, incorporating the feedback.)

This should repair the wicket fortune test on ServerCentral, which is currently failing.

It appeared to be using the system default charset instead, which was not necessarily UTF-8.

I removed the initialCapacity argument for the ArrayList because there's no good reason to set it to 10,000. Since the test requirements state that the list shouldn't be sized using foreknowledge of the row count, we might as well trust ArrayList's defaults.

It appeared to be using the system default charset instead, which was
not necessarily UTF-8.

I removed the initialCapacity argument for the ArrayList because there's
no good reason to set it to 10,000.  Since the test requirements state
that the list shouldn't be sized using foreknowledge of the row count,
we might as well trust ArrayList's defaults.
@mention-bot
Copy link
Copy Markdown

Thanks @michaelhixson for contributing to The Framework Benchmarks! @martin-g and @dashorst, code you've worked on has been modified. If you have the chance, please review. If you wish to unsubscribe from these notices, please open a Pull Request with the commit message [ci skip] and your github name added to the userBlacklist array in the .mention-bot file.

@martin-g
Copy link
Copy Markdown
Contributor

martin-g commented Apr 5, 2017

Thank you, @michaelhixson !

@NateBrady23 NateBrady23 merged commit 80739ce into TechEmpower:master Apr 6, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants