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

Can I convert App::Notifier::Service from Dancer 1 to Dancer2?
by Shlomi Fish 07 Aug '15

07 Aug '15

Hi all, Is there a good reason why I should *not* convert https://metacpan.org/pod/App::Notifier::Service from Dancer 1 to Dancer2? It's a simple web app, meant to run synchronously, and I can debug it by using perl -d, and last time I tried doing s/Dancer/Dancer2/g everything worked nicely. Is there a good enough reason to stay with Dancer 1? Regards, Shlomi Fish -- ----------------------------------------------------------------- Shlomi Fish http://www.shlomifish.org/ http://www.shlomifish.org/humour/bits/Can-I-SCO-Now/ - "Can I SCO Now?" If it isn’t in my email, it doesn’t exist. And if the whole world says one thing and my email says something different, email will conquer. — an Israeli Linuxer. Please reply to list if it's a mailing list post - http://shlom.in/reply .

6 7

Incorrect attempts to serialize HTML
by Andrew Beverley 23 Nov '14

23 Nov '14

Hi guys, I apologise in advance that this is rather vague, but I'm hoping that someone might be able to point me in the right direction of where I should be looking. I'm getting some strange problems with Dancer2 and the "auto serializer". I have set serializer => 'JSON'; in my app, but under some circumstances it is trying to serialize HTML content, with the subsequent errors that you would expect of such an action. The problems seem to be related to my error handling (using Log::Report). My implementation is currently rather poor and complicated, so I won't go into the details here, but I wondered whether someone can point me to the relevant parts of the Dancer2 code that I should start poking around in (in particular the code which detects whether to serialize the data). I've looked at serialize() in Serializer::Mutuble, but as far as I can tell this function is not being called. Where else should I look? If I remove the aforementioned serializer statement then everything works as expected. Thanks, Andy

2 6

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

23 Oct '14

Hey everyone! Another Dancer2 release is upon us. Dancer2 version 0.153000 is uploading as we speak. The changelog is as follows: [ ENHANCEMENT ] * Internal: Move the implementation of send_file from DSL to App. (Russell Jenkins) [ BUG FIXES ] * GH #634, #687: Fix file logger defaults. (Russell Jenkins, Dávid Kovács, Sawyer X) * GH #730: Make App use app-level config for behind_proxy. (Sawyer X) * GH #727: Disable regex metachars when calculating app location in tests (Gregor Herrmann) * GH #681, #682, #712: Clear session engine within destroy_session. (DavX, Russell Jenkins) * Ignore :tests in importing, don't suggest :script. (Sawyer X) [ DOCUMENTATION ] * GH #728: Typos in Policy document. (Olaf Alders, Sawyer X) I want to thank everyone who was involved in this release (in no particular order): Russell Jenkins, Dávid Kovács, Gregor Herrmann, DavX, Olaf Alders, and Sawyer X. Enjoy!

1 0

Example of pagination with DBIC?
by John Stoffel 22 Oct '14

22 Oct '14

Hi all, My google-fu is weak and I haven't been able to find a good example of how to do pagination with Dancer, DBIC and ideally some basic Javascript to make it look good. Here's my basic code that I'm working with right now, which I know is semi busted, but I just keep hitting roadblocks. The goal here is to let me spin up quick, but nice search forms for read only mysql DBs for a library I work with in my spare time. Ideally a CRUD interface down the line to allow end users to add/edit records. DBIC looks to be the way to go with this down the line, since it can do proper records and transactions. At least I think it can. Any way, my code: package TestDBIC; use Dancer ':syntax'; use Dancer::Plugin::DBIC qw(schema resultset rset); # cd TestDBIC; # TestDBIC::Schema 'dbi:mysql:dbname=emina;host=quad' emina our $VERSION = '0.1'; get '/' => sub { template 'search'; }; post '/results' => sub { my $name = param 'Name'; my $sex = param 'Sex'; my $city = param 'City'; my $state = param 'State'; my $id = param 'MummyID'; my @rows; my $query; my $q = {}; my $limit = 10; my $opts = {}; $opts->{order_by} = { -desc => 'id' }; $opts->{rows} = $limit if defined $limit; # We need to join in several tables from the schema $opts->{page} = 1; $opts->{limit} = 15; $opts->{order_by} = { 'desc' => 'name'}; my $rs = schema->resultset('MummyInNorthAmerica'); if ($name) { if ($query) { $query .= " AND "; } $query .= "Name LIKE $name"; $q->{name} = { like => "%$name%" } ; } if ($sex) { if ($query) { $query .= " AND "; } $query .= "Sex = $sex"; $q->{sex} = $sex; } @rows = $rs->search($q,$opts)->pager; template 'results', { query => $query, mummies => \@rows, rows => 1000 }; }; true;

3 10

Dancer2 Release Cycles and Feature/Bugfix Release Planning
by burnersk 21 Oct '14

21 Oct '14

Hi Sawyer, here is my draft of the introduction email... --- DRAFT --- Hi folks. I was wondering recently when the feature X or the bug Y will be fixed. So I try to look up it in the GitHub Milestones[1]. I saw that milestones was used but starting from 0.14100 there was no progress at all with milestones (progress with issues itself was made of course). For me as a developer milestones are nice because I can see what is on the schedule for the next release. From the user point I can see when my beloved feature X or hated bug Y is going to be fixed. I think GitHub Milestones are a great way to communicate to developers and users at the same time. So I asked on #dancer if there where any plans to proceed with release planning based on GitHub Milestones. It turns out that the intention was there but time was missing to organize. Sawyer asked me to attend to help with release planning. I'm not sure that this is true but I had in mind, that the Dancer2 release cycle supposed to be 2 weeks. So that every second week there will be a new release with new great features and fixed bugs. I'd like to check with all of you folks, developers or users, if you want this or not. Please discuss this idea. I can imagine the following "process". Basic environment: * develop period: 12 days (freeze on day 13 and 14, release on day 14) * develop time per developer: 1 hour / day (5 days a week, 10 hours a period) * developers: 8 core developer (some may not work "all the time" but we have other contributors) * total work hours per period: 80 hours Milestone calculation (break on first match, it's just a guideline - not a strict rule): * estimate severity and popularity * very_next_release means the very next release even if it's barely possible (no left *planed* development time) * next_possible_release means the next possible release according on the development time left for the milestone * next_but_one_possible_release means the possible release(ses) after next_possible_release according on the development time left for the milestone 1. for severity in (Blocker, Critical) set milestone to very_next_release 2. for type in (Bug) and severity in (Major) and popularity in (High) set milestone to very_next_release 3. for severity in (Medium) and popularity in (High) and complexity in (Easy) set milestone to next_possible_release 4. for severity in (Medium) and popularity in (High) and complexity in (Moderate) set milestone to next_possible_release 5. for severity in (Medium) and popularity in (High) and complexity in (Hard) set milestone to next_but_one_possible_release 6. for others set milestone to next_but_one_possible_release I'd soft estimate the severity and popularity, check back with the core developers and finally assign the milestone. Furthermore I'll (or a small team will) set severity, popularity and complexity initially when they are checked by the core team. According to the release cycle the milestone due dates will be set. Issues which are not become final within the desired milestone will be moved to the next milestone. Due to this circumstance there will be reserve of 10 working hours within every milestone for those delayed issues. The affected issues will be flagged as delayed. What do you think about all of it? [1] https://github.com/PerlDancer/Dancer2/milestones -- Cheers, burnersk

2 2

Dancer2::Manual::Migration
by Sawyer X 20 Oct '14

20 Oct '14

Hi all, as I mentioned in the release email, Dancer2 now has a migration document for users coming from Dancer, Dancer2::Manual::Migration <https://metacpan.org/pod/distribution/Dancer2/lib/Dancer2/Manual/Migration.…> [1]. This is a living document describing the few differences between Dancer and Dancer2, and is meant to help you convert your applications and adjust your way of doing things to fit Dancer2. You can help! If you see something wrong, if you think something could be described better, if you wish to add anything that is missing, please let us know. Either send a pull request, a Github issue, an RT ticket, or just shoot us an email - to the list or to one of the core devs personally. Whatever you prefer. The migration document has been assembled and written by an OPW (Outreach Program for Women) applicant, Snigdha Dagar. I want to thank her for her work (which is not done yet!) and to all those who reported and helped collect all the various issues that are mentioned in the migration document. Good job! Dance away, Sawyer. [1] https://metacpan.org/pod/distribution/Dancer2/lib/Dancer2/Manual/Migration.…

5 4

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