Re: [Catalyst] Migrate from SHA hashed passwords to Bcrypt crypted passwords
Pavel Karoukin hipp...@gmail.com writes: Right now I am using SHA hashed passwords in my Catalyst application (https://github.com/hippich/Bitcoin-Poker-Room). While SHA is better then MD5, I still want to migrate to Bcrypt. I have two questions: 1) Catalyst::Authentication::Credential::Password seems to not support Bcrypt since it relies on Digest and Digest do not have Bcrypt as an option. Most of the time, using the self_check method provided by the password credential is the way to go. Should I use DBIx::Class::EncodedColumn with Crypt::Eksblowfish::Bcrypt ? That's one way, yes. 2) How I should update my application to have first check against new hashing algorithm and if password returns incorrect, try old one (SHA)? That's certainly possible. An other alternative would be to store the hashing method used by your passwords right next to them. In fact, that's exactly what DBIx::Class::PassphraseColumn does, and your problem is exactly the reason it has been written. It supports every hashing scheme supported by Authen::Passphrase. Authen::Passphrase itself supports both Digest with SHA through A::P::SaltedDigest and bcrypt through A::P::BlowfishCrypt. Should I do it through realms, or just check password in my authentication controller directly instead? If you really want to check hashes twice instead of just storing the hashing method, the most sensible point for that to happen seems to be the check_password method in your user class. Do note that, as the author of DBIx::Class::PassphraseColumn, I'm biased. pgpMeA8OmAwlc.pgp Description: PGP signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
[Catalyst] [ANNOUNCE] Catalyst-Runtime-5.89002-TRIAL PSGI Catalyst - third development release
Hi It gives me great pleasure to announce the third development release of the next major version of Catalyst. The changes from the previous PSGI development release include fixes for various test failures as well as refactoring of the API for retrieving PSGI application code references for Catalyst applications. See the end of this mail for the full changelog. This is a development release, and we need people to start trying to use it _NOW_, and to tell us about the issues you find with your real world applications. Otherwise we're going to be unable to fix those issues before a final release. There are still some known problems with the current release, and the upgrading documentation is at this stage anything but complete. However, we have been working hard to keep this release as compatible as possible with previous versions, and the documentation for upgrading will greatly improve before the final version.. Known issues: * lighttpd versions below 1.4.23 are known to be broken (this should be able to be worked around using Plack::Middleware::LighttpdScriptNameFix - we would love some people using earlier versions of lighttpd to help test this) * IIS6 is believed to be broken (fix will be forthcoming - please shout up if you will be able to test this for us). Other than this list of known issues, everything should continue working as it did beforehand for all users (including current users of Catalyst::Engine::PSGI). You shouldn't have to do _anything_ to upgrade to the new release, other than ensure your application scripts (as generated by catalyst.pl) to use the Catalyst::Script:: classes. Please test the release out and let us know how you get on. The release can be found at: http://search.cpan.org/~flora/Catalyst-Runtime-5.89002-TRIAL/ Please report your successes (and/or failures) to the list, or come find us on irc. We'll be trying to get a new dev release out every couple of weeks now until people stop finding issues.. Thanks in advance -- 5.89002 2011-03-02 11:30:00 (TRIAL release) Bug fixes: - Fix a couple of test failures caused by optional dependencies such as FCGI not being installed. Refactoring: - Simplified the API for getting a PSGI application code reference for a Catalyst application for use in, for example, .psgi files. See Catalyst::Upgrading for details. pgpJgTtFvckZI.pgp Description: PGP signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] [ANNOUNCE] Catalyst-Runtime-5.89002-TRIAL PSGI Catalyst - third development release
Many thanks for testing this release. Pedro Melo m...@simplicidade.org writes: I've noticed a small difference with Catalyst::Test. The latest stable version include two headers, 'host' and 'https'. They are missing from this version. Is this a documented change that I missed or a bug? It's certainly not the former, but I'm not sure it's the latter either. When doing local requests using Catalyst::Test (i.e. without CATALYST_SERVER to do remote testing set), HTTP::Request::AsCGI used to be used. We got rid of that and switched to using the infrastructure provided by Plack::Test instead. For local requests, Plack::Test::MockHTTP will now be used, so the HTTP::Requests from your tests will be turned into PSGI env hashes and then handled by your app. Apparently Plack::Test::MockHTTP doesn't set either HOST or HTTPS headers like HTTP::Request::AsCGI does. Instead it provides the server host in the SERVER_NAME header, and the uri scheme (http or https) in psgi.url_scheme. I'm not sure if this change of behaviour is something we should fix though. The engine knows that a request is secure by checking psgi.url_scheme, and applications can ask for that using $ctx-request-secure. Similarly, the request host was, is, and probably always will be available as $ctx-request-host. Did these changes actually cause your app to break? If so, what exactly does the code that broke look like? pgps0QXWUCAjN.pgp Description: PGP signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] [ANNOUNCE] Catalyst-Runtime-5.89002-TRIAL PSGI Catalyst - third development release
Pedro Melo m...@simplicidade.org writes:
On Wed, Mar 2, 2011 at 3:27 PM, Florian Ragwitz r...@debian.org wrote:
I'm not sure if this change of behaviour is something we should fix
though. The engine knows that a request is secure by checking
psgi.url_scheme, and applications can ask for that using
$ctx-request-secure. Similarly, the request host was, is, and probably
always will be available as $ctx-request-host.
Right now I don't need https/secure, but I do need the host.
At first I assumed that something like $ctx-request-host would be
available but its not:
[error] Caught exception in E5::Sites::Gestao::View::HTML-process
Can't locate object method host via package Catalyst::Request
Sorry, I meant to say $ctx-request-uri-host
Did these changes actually cause your app to break? If so, what
exactly does the code that broke look like?
Yes, it did because the app switched template paths based on the
hostname used to access the app.
The code I was using was:
my $host = $c-request-headers-header('Host');
$host =~ s/:\d+$//;
I guess pretty much every webserver will set a Host header, so we should
probably do that as well in Plack::Test::MockHTTP, or at least in
Catalyst::Test::local_request only for back-compat. I'll see what Plack
upstream thinks about doing this in ::MockHTTP.
pgpecc0mP1lJf.pgp
Description: PGP signature
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
[Catalyst] [ANNOUNCE] Catalyst-Runtime-5.89001-TRIAL PSGI Catalyst - second development release
Hi It gives me great pleasure to announce the second development release of the next major version of Catalyst. The changes from the previous PSGI development release include merging all changes of the non-PSGI releases 5.80031 and 5.80032, much improved upgrading documentation, and fixes for various test failures. See the end of this mail for the full changelog. This is a development release, and we need people to start trying to use it _NOW_, and to tell us about the issues you find with your real world applications. Otherwise we're going to be unable to fix those issues before a final release. There are still some known problems with the current release, and the upgrading documentation is at this stage anything but complete. However, we have been working hard to keep this release as compatible as possible with previous versions, and the documentation for upgrading will greatly improve before the final version.. Known issues: * lighttpd versions below 1.4.23 are known to be broken (this should be able to be worked around using Plack::Middleware::LighttpdScriptNameFix - we would love some people using earlier versions of lighttpd to help test this) * IIS6 is believed to be broken (fix will be forthcoming - please shout up if you will be able to test this for us). Other than this list of known issues, everything should continue working as it did beforehand for all users (including current users of Catalyst::Engine::PSGI). You shouldn't have to do _anything_ to upgrade to the new release, other than ensure your application scripts (as generated by catalyst.pl) to use the Catalyst::Script:: classes. Please test the release out and let us know how you get on. The release can be found at: http://search.cpan.org/~flora/Catalyst-Runtime-5.89001-TRIAL/ Please report your successes (and/or failures) to the list, or come find us on irc. We'll be trying to get a new dev release out every couple of weeks now until people stop finding issues.. Thanks in advance -- 5.89001 2011-03-01 15:27:00 (TRIAL release) Bug fixes: - Fixed command-line argument passing in Catalyst::Script::FastCGI. - Fixed Catalyst::Engine::Stomp compatibility. Applications using Catalyst::Engine::Stomp are believed to continue working without any changes with the new Catalyst major version. - Fixed issues auto-loading engine with older scripts. Known problems: - Catalyst::Engine::Wx is officially unsupported and BROKEN. If you are using this engine then please get in touch with us and we'll be happy to help with the changes it needs to be compatible with the new major version of Catalyst. Documentation: - The section of Catalyst::Upgrading describing how to upgrade to version 5.90 of Catalyst has been much improved. pgp9Vll8qShVA.pgp Description: PGP signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
[Catalyst] [ANNOUNCE] Catalyst-Runtime 5.80030
Hi It gives me great pleasure to announce a new and improved version of Catalyst-Runtime. This fixes a couple of small bugs which were causing issues for a couple of people. There's also a few of minor new features. The most visible change is probably the ability to set the response body to `undef' to indicate that no body should be sent. Version 0.15 of Catalyst::Action::RenderView, which is mentioned in the changelog and which is required to make use of the aforementioned feature, will appear on CPAN later today. Full changelog below as always. Cheers rafl --- 5.80030 2011-01-04 13:13:02 New features: - Add a --proc_title option to the FCGI script to set the process title. - Allow the response body to be set to `undef' explicitly to indicate the absence of a body. It can be used to indicate that no body should be sent at all and processing of views should be skipped. This is especially useful for things like X-Sendfile, which now no longer require providing fake response bodies to suppress view processing. In order for this to work, you will also have upgrade Catalyst::Action::RenderView to at least version 0.15. Bug fixes: - Deal correctly with GLOB file handles in the response body (setting the Content-Length header appropriately) - Chained dispatch has been fixed to always prefer paths with the minimum number of captures (rather than the maximum number of actions). This means that (for example) a URI path /foo/* made out of 2 actions will take preference to a URI path /*/* made out of 3 actions. Please check your applications if you are using chained action and please write new test to report failing case. - Stop relying on bugs in the pure-perl version of Package::Stash. New versions of Package::Stash load Package::Stash::XS if available. Package::Stash::XS fixes some of the bugs of the pure-perl version, exposing our faulty assumption and breaking things. We now work with both old and new versions of Package::Stash, both with and without Package::Stash::XS being installed. Older versions of Catalyst-Runtime also work with both old and new versions of Package::Stash, but only if Package::Stash::XS is *not* installed. Documentation: - Clarify that when forwarding or detaching, the end action associated with the original dispatched action will be run afterwards (fallen) pgpjTblJ8tB0h.pgp Description: PGP signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Leak tests
Bill Moseley mose...@hank.org writes: I've used CatalystX::LeakChecker in the past but not sure how to incorporate that into a .t file. Check out Catalyst-Runtime's and CatalystX::LeakChecker's test suite. They both do that. pgpqpfTRJTtTw.pgp Description: PGP signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] perms on gen script/ files differ between platforms
On Mon, Jun 21, 2010 at 07:05:56PM -0700, Darren Duncan wrote: On Mac OS X, the initial 5 files in script/ had these permissions: -rwx-- ... where the owner can execute but no one else can do anything. On CentOS, the same files had these permissions: -rw-rw-r-- ... where no one can execute but everyone can read. So what is the reason for this difference? Is it intentional or a bug? I'm guessing your umask settings on both systems differ. -- BOFH excuse #10: hardware stress fractures signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] nmake manifest
The manifest target generated by ExtUtils::MakeMaker never removes entries from MANIFEST unless they're matched by anything in MANIFEST.SKIP. That's a feature. To completely regenerate it from scratch you'll have to delete it first. If you want your manifest target to do something else, you can simply make your Makefile.PL emit a different manifest target, or just define a custom target that does what you mean. -- BOFH excuse #336: the xy axis in the trackball is coordinated with the summer solstice signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Adding build scripts to Makefile.PL
On Mon, May 10, 2010 at 06:15:03PM -0700, Bill Moseley wrote: I have a number of scrips that need to be run when building an application. �For example, I have a script that minifies javascript and css. �In many cases it's a real Makefile�dependency�-- need to run a command to turn one file into another -- but in some cases don't know the sources of the targets (i.e. a script just finds all .css files and minifies them) so might just want to run a command every time make is run. You can do globbing in your Makefile.PL, or use a script to just find the files, and have a target that depends on whatever the script outputed, or whatever. Anyone have examples of how to set this up in Makefile.PL (which uses Module::Install)? Module::Install has a postamble() command to add makefile snippets to the generated Makefile.PL -- BOFH excuse #260: We're upgrading /dev/null signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Catalyst::Plugin::Authentication uses NEXT, which is deprecated.
On Sun, May 09, 2010 at 05:23:37PM -0700, Paul Makepeace wrote: On Sun, May 9, 2010 at 17:01, Florian Ragwitz r...@debian.org wrote: Running perl -MV=Catalyst::Plugin::Authentication will tell. Hmm, how's this supposed to work? $ perl -MV=Catalyst::Plugin::Authentication Can't locate V.pm in @INC By installing V.pm from cpan :) -- BOFH excuse #257: That would be because the software doesn't work. signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
[Catalyst] [ANNOUNCE] Call for testers: Compound Primary Key support in Catalyst::Authentication::Store::DBIx::Class
Short version: If you're using Catalyst::Authentication::Store::DBIx::Class, install FLORA/Catalyst-Authentication-Store-DBIx-Class-0.1100-TRIAL.tar.gz and report any problems. Long version: I just uploaded a development release of Catalyst::Authentication::Store::DBIx::Class to CPAN. It adds support for authenticating against a user table with a compound primary key. In order to add that feature, a couple of internal changes had to be made. Those changes also affect the usage of the module with a single-column primary key in the user table. Therefore, it's important that you test your existing applications using the DBIx::Class auth store against the above development release, even if you don't care about the new feature at all. Please tell us about the results of your testing, both success and failure, on the mailing list or in #catalyst-dev on irc. Thanks in advance -- BOFH excuse #208: Your mail is being routed through Germany ... and they're censoring us. signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] GSoC
On Mon, Mar 29, 2010 at 08:17:00PM -0400, Caleb Cushing wrote: On Sat, Mar 27, 2010 at 5:33 PM, Tomas Doran bobtf...@bobtfish.net wrote: However, as a mild warning, most of the 'easy' stuff here is done (and working) in a branch (zby++). to be an ignoramous where is this branch? I suspected runtime... but my git-svn checkout doesn't show one of that name. maybe it didn't grab it for some reason? basic-app-ctx-separation basic-app-ctx-separation-cleaned basic-app-ctx-separation-cleaned-appnotcomponent are the related branches IIRC, students need to write an individual proposal up of some form. Can you look into what's actually required of you, and get to work knocking one up, then highlight potential/registered mentors for technical input and people in the doc team for copy editing? working on it now that it's available to do. http://socghop.appspot.com/gsoc/student_proposal/private/google/gsoc2010/xenoterracide/t126990737897 No need to announce that on the public list. Only the prospective mentors will be able to view it anyway. have a few things I've marked TBD because I'm not sure what to put at this instant. I'm sure other things could be improved too. perhaps I suck at writing proposal's. No worries. You can always edit your proposal until the submission deadline arrives, but it'd probably be good to let the mentors know when you think you're done, for example by commenting on your own proposal, so the mentors can start giving actual feedback. -- BOFH excuse #53: Little hamster in running wheel had coronary; waiting for replacement to be Fedexed from Wyoming signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Requiring a certain module version in Makefile.PL
On Sun, Feb 21, 2010 at 07:54:26PM +0200, Octavian Rasnita wrote: In Makefile.PL I have the following line: requires 'DBIx::Class::Schema::Loader' = '0.05003'; When I do perl Makefile.PL shouldn't that line require and install this version of DBIx::Class::Schema::Loder? I have a 0.04... version, but after `perl Makefile.PL` the new version was not installed and it happened the same with other modules. You're confusing requires() with auto_install(). If you want stuff being installed instead of just reported, you'll need the latter. -- BOFH excuse #239: CPU needs bearings repacked signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] CatalystX::SimpleLogin and auto
On Tue, Feb 09, 2010 at 11:50:45PM -0800, Ovid wrote:
Note that leaving the method there but removing the if ($c) {} allows
the form to show up again. I've no idea why this is happening :)
Note that the return value of auto actions can modify dispatching. See
http://dev.catalyst.perl.org/attachment/wiki/WikiStart/catalyst-flow.png
--
BOFH excuse #449:
greenpeace free'd the mallocs
signature.asc
Description: Digital signature
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Use CatalystX::SimpleLogin Globally
Catalyst::Controller::ActionRole documents how to apply roles to all actions of a controller, without specifying the roles for each action individually. -- BOFH excuse #302: microelectronic Riemannian curved-space fault in write-only file system signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
[Catalyst] [ANNOUNCE] Catalyst-Runtime 5.80020
I'm happy to announce the next release of Catalyst-Runtime (5.80020). This release adds a new feature allowing components to specify additional components to be set up by overriding the expand_modules method. Full changelog included below as always. Cheers rafl -- 5.80020 2010-02-04 06:51:18 New features: - Allow components to specify additional components to be set up by overriding the expand_modules method. (Oliver Charles) signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
[Catalyst] [ANNOUNCE] Catalyst-Runtime 5.80019
I'm happy to announce the next release of Catalyst-Runtime (5.80019).
This release adds a new feature allowing to pass arbitrary arguments to
the construction of action objects. It also fixes a couple of minor
issues mostly related to encoded paths.
Full changelog included below as always.
Cheers
rafl
--
5.80019 2010-01-29 01:04:09
Bug fixed:
- Calls to $c-uri_for with private paths as strings (e.g.
$c-uri_for('controller/action', 'arg1', 'arg2') ) no longer have
/ encoded to %2F. This is due to $c-uri_for('static', 'css/foo', $bar)
which should not be encoded.
Calls with an action object (rather than a string), or uri_for action
will still encode / in args and captures to %2F
- The above noted / = %2F encoding in uri_for_action or uri_for with
an action object has been fixed to not just encode the first slash in
any set of args/captures.
- nginx and lighttpd FCGI requests with URI encoded sections as the first
path part have been fixed to operate correctly.
- A source of bogus warnings in Catalyst::Component::BUILDARGS has been
removed.
Documentation:
- Improve the documentation about -Home and how Catalyst finds the home path
for applications.
- Various minor typo fixes.
New features:
- Allow passing additional arguments to action constructors.
signature.asc
Description: Digital signature
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] lib question
On Fri, Jan 15, 2010 at 05:15:13PM +, Dermot wrote: I had a search on the archives but I can't see anything. I doubt that it's an oversight, so can someone tell me the reason why the tests that are created by Catalyst::Helper do not have use FindBin and set lib accordingly? My guess is because they don't need to. Things like prove and make test will set up @INC to contain your applications lib/ directory. The FindBin thingy is usually used to set up @INC to contain extra libraries used only for testing from something like t/lib/. I'm not aware of any generated test that does that. -- BOFH excuse #321: Scheduled global CPU outage signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
[Catalyst] [ANNOUNCE] Catalyst-Runtime 5.80018
I'm happy to announce the next release of Catalyst-Runtime (5.80018).
This release makes Catalyst ready for the upcoming release of
HTTP::Request::AsCGI by fixing a bug that's hidden by a bug in current versions
of AsCGI. It also adds a new warning for a deprecated usage of Catalyst::Test.
Full changelog included below as always.
Cheers
rafl
--
5.80018 2010-01-12 22:24:20
Bug fixed:
- Call -canonical on URI derived from $ENV{REQUEST_URI} to get
paths correctly decoded. This bug was previously hidden by a bug
in HTTP::Request::AsCGI
Documentation:
- Clarify that uri_for_action works on private paths, with example.
Deprecations:
- Saying use Catalyst::Test; (without an application name or () to stop
the importer running is now deprecated and will issue a warning.
You should be saying use Catalyst::Test ();
signature.asc
Description: Digital signature
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
[Catalyst] [ANNOUNCE] Catalyst-Runtime 5.80017
I'm happy to announce the next release of Catalyst-Runtime (5.80017). This release mainly cures all issues reported with upgraded scripts (or applications generated with the latest release of Catalyst::Devel) and makes Catalyst compatible with upcomming versions of Moose. This release also started being more strict about the deprecated usage of NEXT. We're not surpressing any Class::C3::Adopt::NEXT warnings anymore. See the changelog for details. Full changelog included below as always. Cheers rafl -- 5.80017 2010-01-10 02:27:29 Documentation: - Fix docs for -forward method when passed a class name - this should be a component name (e.g. View::HTML, not a full class name, like MyApp::View::HTML). Bug fixes: - --daemon and -d options to Catalyst::Script::FastCGI are fixed. - Fix the debug dump for applications which use Catalyst::Plugin::Session (RT#52898) - Fix regression in the case where mod_rewrite is being used to rewrite requests into a path below your application base introduced with the %2F related fixes in 5.80014_02. - Do not crash on SIGHUP if Catalyst::Engine::HTTP-run is not passed the argv key in the options hash. - Correctly pass the arguments to Catalyst::Script::Server through to Catalyst::Engine::HTTP-run so that the server can restart itself with the correct options on SIGHUP. - Require new MooseX::MethodAttributes to be compatible with Moose versions = 0.93_01 - Require new MooseX::Role::WithOverloading to be compatible with Moose versions = 0.93_01 Cleanups: - Stop suppressing warnings from Class::C3::Adopt::NEXT now that most plugins have been updated to not use NEXT. If you get warnings then please upgrade your components or log a bug with the component author if an upgrade is not available. The Class::C3::Adopt::NEXT documentation contains information about how to suppress the warnings in your application if you need to. signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Perl code attributes in Moose roles
On Sat, Dec 19, 2009 at 10:51:36PM +0100, Bernhard Graf wrote: I am writing an admin application based on Cat. Much of it is the typical CRUD stuff, so I had the idea to put that into Roles. Is there a solution for this problem yet? Yes, it's referred to from several places in the docs and is called MooseX::MethodAttributes::Role. -- BOFH excuse #143: had to use hammer to free stuck disk drive heads. signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Bug in latest Catalyst::Runtime?
On Fri, Dec 18, 2009 at 12:53:52PM +0200, Octavian Râşniţă wrote: I found that in Catalyst::Runtime 5.80016 the following error still appears when there is a bug in the current application: Yes, that's a regression in 5.80016, introduce with the changes to not dump the __MOP__ attribute of certain objects. -- BOFH excuse #80: That's a great computer you have there; have you considered how it would work as a BSD machine? signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
[Catalyst] [ANNOUNCE] Catalyst-Runtime-5.80011
We're having a great week so far. Yet another regression in 5.80008 has been found. This regression caused failure on systems where older versions of the removed restarter engine weren't available anymore. Catalyst-Runtime 5.80011 has just been uploaded, and corrects that problem, with no other changes. The Changelog is included below as always. Cheers rafl Bug fixes: - Remove leftovers of the restarter engine. The removed code caused test failures, which weren't apparent for anyone still having an old version installed in @INC. -- BOFH excuse #35: working as designed signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Advice needed on porting 5.7 plugin (monkeypatches Cat::Request)
On Fri, Aug 21, 2009 at 11:37:00AM +0100, Pedro Melo wrote: Reading through the docs, I see that I can subclass the Catalyst::Request class and use the $c-request_class to setup the new one. I've done that like this: It's probably better to create a role to apply to the request class and, optionally, use CatalystX::RoleApplicator to apply it. See Catalyst::TraitFor::Request::BrowserDetect for an example. * is it possible for a plugin, at setup time, to set the request_class()? Yes. See Catalyst::Plugin::Browser for that. * is there a better way? Other than not doing it and using CX::RoleApplicator instead? None that i've found so far. -- BOFH excuse #383: Your processor has taken a ride to Heaven's Gate on the UFO behind Hale-Bopp's comet. signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
[Catalyst] [ANNOUNCE] Catalyst-Runtime-5.80010
Apparently the issue fixed in 5.80009 wasn't the only regression introduced in 5.80008. Catalyst-Runtime 5.80010 has just been uploaded, which corrects and adds tests for yet another issue, with no other changes. The Changelog is included below as always. Cheers rafl Bug fixes: - Fix and add tests for a regression introduced by 5.80008. Catalyst::Engine is now able to send out data from filehandles larger than the default chunksize of 64k again. -- BOFH excuse #315: The recent proliferation of Nuclear Testing signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] RenderView install problem
On Tue, Jun 30, 2009 at 05:04:36PM -0500, Peter Karman wrote: apologies if this has been reported elsewhere. That was a regression iN Catalyst-Runtime 5.80006. It's fixed in 5.80007. -- BOFH excuse #129: The ring needs another token signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Upgrading Catalyst and issues with Class::MOP
On Wed, Apr 29, 2009 at 05:08:38PM +0100, Adam Witney wrote: I upgraded Catalyst to 5.80002 the other day, and my applications started beginning with a warning: The compute_all_applicable_attributes method has been deprecated. Use get_all_attributes instead. at /usr/local/lib/perl5/site_perl/5.8.9/darwin-thread-multi-2level/ Class/MOP/Class.pm line 946 Please upgrade to the latest version of Data::Visitor. We'll bump the required version in Action::RenderView. Thanks for letting us know about this. -- BOFH excuse #334: 50% of the manual is in .pdf readme files signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] [PATCH] Catalyst::DispatchType::Chained (5.7101, 5.80001)
On Mon, Apr 20, 2009 at 05:16:55AM +0300, Oleg Kostyuk wrote: This bug is present in 5.7101: created Text::SimpleTable with 3 columns, while we need only two. This is fixed in the latest stable release of Catalyst-Runtime. Please upgrade. -- BOFH excuse #414: tachyon emissions overloading the system signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Catalyst 5.8 NEXT deprecated warnings
On Tue, Mar 31, 2009 at 12:52:53PM +0100, Anthony Gladdish wrote: Catalyst::Plugin::Session::Store::DBIC is trying to use NEXT, which is deprecated. Please see the Class::C3::Adopt::NEXT documentation for details The svn version of Session-Store-DBIC is already converted to MRO::Compat. Not uploaded yet because its maintainer asked to review the changes before I release, which hasn't happened yet. -- BOFH excuse #155: Dumb terminal signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] IO::Pipe and the Catalyst Server
On Wed, Feb 04, 2009 at 10:25:15PM -0800, Bill Moseley wrote: I have a module that uses IO::Pipe and when I run it under the Catalyst server the pipe doesn't work (see below). Please try to reproduce with Catalyst-Runtime-5.8000_06. It has a fix related to spawning external processes from the dev server. -- BOFH excuse #311: transient bus protocol violation signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] IO::Pipe and the Catalyst Server
On Thu, Feb 05, 2009 at 12:51:18PM +, Peter Edwards wrote: Was that the change to the catching of signal SIGCHLD ? Exactly. -- BOFH excuse #66: bit bucket overflow signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] IO::Pipe and the Catalyst Server
On Thu, Feb 05, 2009 at 07:10:07AM -0800, Bill Moseley wrote: Same problem. Would you mind preparing a testcase for this? TestApp::Controller::Fork / t/live_fork.t already has similar tests. You can run them against the dev server using t/optional_http-server.t. -- BOFH excuse #86: Runt packets signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] [PATCH] [RFC] Seed the RNG in Catalyst::Engine::FastCGI
On Mon, Feb 02, 2009 at 05:09:21PM -0600, Andrew Rodland wrote: Attached is a patch that does an srand in each child immediately after invoking pm_manage, if we are running our own process manager. applied to 5.80/trunk as r9178. -- BOFH excuse #147: Party-bug in the Aloha protocol. signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
[Catalyst] Re: Patch for Catalyst/Engine/FastCGI.pm
Thanks, applied as r8436. -- BOFH excuse #206: Police are examining all internet packets in the search for a narco-net-trafficker signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Patch for Catalyst::View::Mason
On Fri, Mar 07, 2008 at 10:10:25PM +0100, David Jack Wange Olrik wrote:
On 07/03/2008, at 19.26, Jonathan Rockway wrote:
To do what David wanted would have to use a heuristic to determine
whether $c-stash-{template} is the actual template name, or the
template name minus the extension. By definition, that's never going
to work.
No need to do any heuristics, you could just decide that you always
supply the template without extention and let the View module add it.
(But this change will indeed break all existing apps unless some
heuristics are applied, and that is not sane).
I want to keep the default behaviour to not break existing code and to
be consistent with most other catalyst views.
However I'll think about implementing a new configuration option that,
when enabled, will always append template_extension.
-Flo
--
BOFH excuse #189:
SCSI's too wide.
signature.asc
Description: Digital signature
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
[Catalyst] ::Session::Store::FastMmap issues
Hi, there is an issue with the Cache::FastMmap store for the Session plugin. When $c-session contains some large very data structures Cache::FastMmap refuses to store them for whatever reason and returns false when calling -set on it. However Catalyst::Plugin::Session::Store::FastMmap doesn't check the return value of set and therefor causes session data to be lost silently. This sucks and I'd like to be able to see when that happens to ease debugging. Loudly failing would probably not be a good solution here, but a warning would probably be helpful. -Flo -- BOFH excuse #297: Too many interrupts signature.asc Description: Digital signature ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ Dev site: http://dev.catalyst.perl.org/
