- dancer-users - lists.preshweb.co.uk

Standards of Conduct
by Sawyer X 16 Oct '14

16 Oct '14

As part of the latest Dancer2 release, and part of the upcoming Dancer release, we have added our policy document, which currently indicates our Standards of Conduct. The Standards of Conduct are the standards by which we behave with each other in the community. These are the standards by which we hold each other accountable. We promote the Dancer community as a safe space for everyone. We promote self-awareness, consideration, and self-regulation. We are very strict with our policy and will make sure to enforce it in every realm in which the community comes together. This includes the mailing list, our IRC channel, and Dancer conferences. Please let us know if any issue comes up. We're always here. I'm including the entire text here, in its current released version as of this date, but you can find it at Dancer::Policy <https://metacpan.org/pod/release/YANICK/Dancer-1.3131_1/lib/Dancer/Policy.p…> and Dancer2::Policy <https://metacpan.org/pod/distribution/Dancer2/lib/Dancer2/Policy.pod>. Sawyer, The Dancer Core Devs. STANDARDS OF CONDUCT These standards applies anywhere the community comes together as a group. This includes, but is not limited to, the Dancer IRC channel, the Dancer mailing list, Dancer hackathons, and Dancer conferences. * Always be civil. * Heed the moderators. * Abuse is not tolerated. Civility is simple: stick to the facts while avoiding demeaning remarks and sarcasm. It is not enough to be factual. You must also be civil. Responding in kind to incivility is not acceptable. If the list moderators tell you that you are not being civil, carefully consider how your words have appeared before responding in any way. You may protest, but repeated protest in the face of a repeatedly reaffirmed decision is not acceptable. Unacceptable behavior will result in a public and clearly identified warning. Repeated unacceptable behavior will result in removal from the mailing list and revocation of any commit bit. The first removal is for one month. Subsequent removals will double in length. After six months with no warning, a user's ban length is reset. Removals, like warnings, are public. The list of moderators consists of all active core developers. This includes, in alphabetical order, Alberto Simões, David Precious, Mickey Nasriachi, Russell Jenkins, Sawyer X, Stefan Hornburg (Racke), Steven Humphrey, and Yanick Champoux. This list might additionally grow to active members of the community who have stepped up to help handle abusive behavior. If this should happen, this document would be updated to include their names. Additionally, it's important to understand the self-regulating nature we foster at the Dancer community. This means anyone and everyone in the community - in the channel, on the list, at an event - has the ability to call out unacceptable behavior and incivility to others in the community. Moderators are responsibe for issuing warnings and take disciplenary actions, but anyone may - and is encouraged - to publicly make note of unacceptable treatment of others. As a core principle, abuse is never tolerated. One cannot berate, insult, debase, deride, put-down, or vilify anyone, or act towards anyone in a way intending to hurt them. The community specifically considers as abuse any attempts to otherize anyone, whether by their technical skill, knowledge, gender, sexual orientation, or any other characteristic. The community aims to maintain a safe space for everyone, in any forum it has. If you ever feel this core principle has been compromised, you are strongly urged to contact a moderator. We are always here. Remember, this is your community, as much as it is anyone else's. CREDITS This policy has been adopted and adapted from the policy available for the Perl language development, provided by p5p (the Perl 5 Porters). The original inspiration policy document can be read at perlpolicy.

1 0

send_file and Dancer2
by Jean-Marc Choulet 15 Oct '14

15 Oct '14

Hello, I 'am new to Dancer2 and I tried to migrate some code from mod_perl to Dancer2. Somewhere, I have this mod_perl code : sub handler { ... open my $fh, "<$filename" or die $@; binmode $fh; $req->content_type('application/vnd.oasis.opendocument.spreadsheet'); $req->headers_out->{'Content-Disposition'} = "attachment; filename=$file"; my ($n, $data); while ($n = read($fh, $data, 1024)) { $req->print($data); } close($fh); return Apache2::Const::OK; } The mod_perl code send a OpenOffice document to the client. How can I do the same thing with Dancer2 ? Thanks, Jean-Marc

2 1

504 Gateway Timeout Error while processing big data files
by Tushar Dave 14 Oct '14

14 Oct '14

Hello Hughes, Thanks for your solution. Can you elaborate the process by using my code? I am newbie in web development and never worked on AJAX. So I am having little bit hard time to connect front-end and back-end pieces. I hope this make sense. Thanks again for your help. Best, Tushar On Tue, Oct 14, 2014 at 7:00 AM, <dancer-users-request(a)dancer.pm> wrote: > Send dancer-users mailing list submissions to > dancer-users(a)dancer.pm > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > or, via email, send a message with subject or body 'help' to > dancer-users-request(a)dancer.pm > > You can reach the person managing the list at > dancer-users-owner(a)dancer.pm > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of dancer-users digest..." > > > Today's Topics: > > 1. 504 Gateway Timeout Error while processing big data files > (Tushar Dave) > 2. Dancer2 0.152000 on its way to CPAN (Sawyer X) > 3. Re: 504 Gateway Timeout Error while processing big data files > (Hugues) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 13 Oct 2014 09:45:12 -0400 > From: Tushar Dave <tushardave26(a)gmail.com> > To: dancer-users(a)dancer.pm > Subject: [dancer-users] 504 Gateway Timeout Error while processing big > data files > Message-ID: > <CA+8TAD= > AV+-bPirEK_HtJKV6MzPSsicU+hHWES-ZWvDu30AQqg(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hello, > > I am working on my Dancer Project (using Perl 5.20.0, apache2, RHEL 6 and > Dancer) in which I am providing a web form to user. When user submits the > form with appropriate values, a Q-Q plot will be generated by R code on > backend. Once the plot is available on server I am sending user an email > with the link of generated plot. > > My code works completely fine with smaller data file (e.g. 100KB ? 10 MB) > upload. But, if user uploads the large data files (e.g. > 30MB), the upload > works fine but processing of data and generating of plot will take more > time which caused 504 Gateway Time Out Error. I can use below options to > resolve this. > > (1) Change Time Out time in apache configuration file > (2) Submit a job through batch queuing system such as SGE > (3) Use Proc::Simple or Proc::Background to run the process in background > and keep checking whether process is running in background or not. > > I am using the 3rd option. What I am trying to do is I am using > Proc::Simple to run Perl-R-code (i.e. listed in below list as 2) in > background. Then I am using poll() method of Proc::Simple to check whether > the process is running or not. If the process is running, render a template > that shows user that process is still running. When process is finished, > render another template with generated Q-Q plot. Below are my codes: > > (1) Dancer code under lib/ ---- http://pastebin.com/QGCFtq2X > < > http://l.facebook.com/l.php?u=http%3A%2F%2Fpastebin.com%2FQGCFtq2X&h=rAQEet… > > > (2) Perl + R code that generate Q-Q plot ----http://pastebin.com/U5hg45dQ > (3) qqPlot.tt ---- http://pastebin.com/u30XArVr > (4) processing.tt ---- http://pastebin.com/RSH1kptp > < > http://l.facebook.com/l.php?u=http%3A%2F%2Fpastebin.com%2FRSH1kptp&h=RAQE1l… > > > > The problem I am facing right now that my Dancer code (i.e. listed as 1 > above) execute while loop on line 77 of (1) but the template ? > processing.tt? > is not coming up on browser. I don?t know what am I doing wrong? > > Can someone help me to figure out my error? Or please suggest me any other > way to resolve Gateway Time Out Error. > > Thanks for any help. >

1 0

504 Gateway Timeout Error while processing big data files
by Tushar Dave 14 Oct '14

14 Oct '14

Hello, I am working on my Dancer Project (using Perl 5.20.0, apache2, RHEL 6 and Dancer) in which I am providing a web form to user. When user submits the form with appropriate values, a Q-Q plot will be generated by R code on backend. Once the plot is available on server I am sending user an email with the link of generated plot. My code works completely fine with smaller data file (e.g. 100KB – 10 MB) upload. But, if user uploads the large data files (e.g. > 30MB), the upload works fine but processing of data and generating of plot will take more time which caused 504 Gateway Time Out Error. I can use below options to resolve this. (1) Change Time Out time in apache configuration file (2) Submit a job through batch queuing system such as SGE (3) Use Proc::Simple or Proc::Background to run the process in background and keep checking whether process is running in background or not. I am using the 3rd option. What I am trying to do is I am using Proc::Simple to run Perl-R-code (i.e. listed in below list as 2) in background. Then I am using poll() method of Proc::Simple to check whether the process is running or not. If the process is running, render a template that shows user that process is still running. When process is finished, render another template with generated Q-Q plot. Below are my codes: (1) Dancer code under lib/ ---- http://pastebin.com/QGCFtq2X <http://l.facebook.com/l.php?u=http%3A%2F%2Fpastebin.com%2FQGCFtq2X&h=rAQEet…> (2) Perl + R code that generate Q-Q plot ----http://pastebin.com/U5hg45dQ (3) qqPlot.tt ---- http://pastebin.com/u30XArVr (4) processing.tt ---- http://pastebin.com/RSH1kptp <http://l.facebook.com/l.php?u=http%3A%2F%2Fpastebin.com%2FRSH1kptp&h=RAQE1l…> The problem I am facing right now that my Dancer code (i.e. listed as 1 above) execute while loop on line 77 of (1) but the template “processing.tt” is not coming up on browser. I don’t know what am I doing wrong? Can someone help me to figure out my error? Or please suggest me any other way to resolve Gateway Time Out Error. Thanks for any help.

2 1

Dancer2 0.152000 on its way to CPAN
by Sawyer X 14 Oct '14

14 Oct '14

Hi everyone! We've done quite a few big things in Dancer2 and I'd like to share them. I haven't sent an email about 0.151000 - released last week - so I'm going to share some information about it too. These two versions provide a few important changes: * Introducing our policy document. * Dancer2 Apps (Dancer2::Core::App) now build proper PSGI applications - *each on its own*. This allows you to create much better PSGI apps, which will interact much better. This will also disallow things we do not recommend, such as "pass" and "forward" between Dancer Apps. The original `psgi_app` keyword (and Dancer2 method) still works, just as before, providing the old behavior. * We added a migration document, for those moving from Dancer to Dancer2, thanks to Snigdha Dagar. * There is a big "chat with us" banner on MetaCPAN.org, to help newbies join the IRC channel. * New 'content' keyword to set content in a declarative manner. The first two are the biggest ones. I will email the list about both of those separately. I would like to congratulate and thank all those who worked on this release: Andy Beverley, Dávid Kovács, DavsX, Paul Cochrane, simbabque, Lindsey Beesley, Snigdha Dagar, Russell Jenkins, and yours truly, Sawyer X. Great work, everyone!

1 0

Dancer1 v1.3131_0 on its way to CPAN
by Yanick Champoux 12 Oct '14

12 Oct '14

Hi all, A new version of Dancer 1 is on its way to CPAN (changelog is copied below). This time around I've decided to do something wild: I'm first releasing a trial version which, provided no issue is found in the meantime, will be promoted to a bona fide general availability release one week from now. As usual, a big, big, BIG thanks to everybody who submitted patches, opened bug reports and helped with the release in any way, shape, or form. Y'all rock. :-) Joy, `/anick 1.3131_0 2014-10-11 [BUG FIXES] - Test was failing under perl 5.8.9. (GH#1057, Tom Hukins) - Don't get tripped by YAML::XS's readonly values. (GH#1070) [DOCUMENTATION] - Minor doc update to detail how to pass protocol information in Apache (GH#1079, Andy Beverley) - Add the Dancer policy POD. [ENHANCEMENTS] - Dancer::Template::TemplateToolkit now supports DATA-embedded templates. (GH#1061, Jochen Lutz) - New function 'param_array'. (GH#1055, Yanick Champoux) - D::Serializer::YAML and Dancer::Config can now use 'YAML::XS'. [MISC] - Add 'YAML' as a recommended dependency. (GH#1080) [STATISTICS] - code churn: 14 files changed, 348 insertions(+), 30 deletions(-)

1 1

Official Docker image for Dancer?
by Jakob Voß 09 Oct '14

09 Oct '14

Hi, Peter Martini has created a Docker image for Dancer, which I have contributed to: https://github.com/PeterMartini/docker-dancer https://registry.hub.docker.com/u/petermartini/docker-dancer/ If this is ok to Peter, I'd prefer this to be an official repository at https://github.com/PerlDancer. You should also create an Docker organization account for the Dancer community: https://hub.docker.com/account/organizations/ The current documentation could be extended to a tutorial. Rob N already did good work here: http://robn.io/docker-perl/ (I'm not sure we should recommend the git glone approach as *only* way to build your dancer application image, one could also use "COPY" in a Dockerfile and "docker build"). A similar tutorial for another language is https://docs.docker.com/examples/nodejs_web_app/. Anyway: I think that an (or multiple) official Docker images for Dancer could improve the visibility and usability of Dancer framework a lot. Cheers, Jakob P.S: If Task::Dancer wasn't stalled (no updates since 2012?!) I'd recommend to install Task::Dancer instead of just Dancer -- Jakob Voß <jakob.voss(a)gbv.de> Verbundzentrale des GBV (VZG) / Common Library Network Platz der Goettinger Sieben 1, 37073 Göttingen, Germany +49 (0)551 39-10242, http://www.gbv.de/

6 5

Dancer Plugins Maintainers team on Github
by Sawyer X 08 Oct '14

08 Oct '14

Hi all! :) I've just created a new team on Github's PerlDancer organization called Plugins Maintainers[1]. This team will consist on anyone and everyone that want to help maintain Dancer (both D1 and D2) plugins. I've already added all the plugin repos that we have under the organization. Team members are able to both read and write to the repos. If you're unsure about a change, feel free to just discuss it with the other team. Open an issue, request responses. We're all here for each other. I'd like to thank all the volunteers we have in the community. I hope this will make it easier on you to contribute in the future. If you want to help with plugins, please oh please let us know and we'll add you to the team. :) [1] https://github.com/orgs/PerlDancer/teams/plugins-maintainers/

7 10

JSON exception return values
by Jeff Boes 06 Oct '14

06 Oct '14

When one of my Dancer (1) JSON-enabled routes dies, I get an object back that looks like this: { "exception" : "some text here", "error" : "some text here" } Recently, I accidentally added a "die" statement with a parameter that wasn't a scalar. (Spoiler: it was a hashref.) I was surprised to see this: { "exception" : { "state_iso_code" : "'(undef)' not a US state or province'", "address" : "blank" }, "error" : "HASH(0x731ce28)" } Woo, that's pretty cool, I thought. I can use that. But how the heck did I do that? I'd like to have a bit more control, like supplying a general "your form failed" message instead of the "HASH()" stringified value. I searched the code base, but as you may expect, "exception" and "error" are grep-proof strings to some extent. -- Jeff Boes <>< jeff(a)endpoint.com 269-408-0811

1 0

Bug with setting behind_proxy in config file?
by Andrew Beverley 05 Oct '14

05 Oct '14

Hi guys, It seems that behind_proxy can't be set in a config file. As far as I can tell, the default settings in _build_config() in Dancer2::Core::Runner are taking precedence (behing_proxy => 0) If I "set behind_proxy => 1" in my application then everything works as expected, but not if I specify it in a config file. I'm happy to investigate further and provide patches as required, but thought it worth running it by this mailing list first. Thanks, Andy

1 0