From: Dominique Martinet <asmadeus@codewreck.org>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] version
Date: Sun, 18 Feb 2018 09:17:09 +0100 [thread overview]
Message-ID: <20180218081709.GA31140@nautica> (raw)
In-Reply-To: <20180118024338.eklhad@comcast.net>
Karl Dahlke wrote on Sun, Feb 18, 2018:
> And it won't be easy because a lot of those tests are in try catch and don't cause any errors that we can see.
> Can we somehow see errors that are hidden inside try catch?
I'd need to remove some of the dust but my duktape debugger test did log
errors inside try catch.
Definitely not something we want integrated before a release but could
help in a separate branch just to test, will send a mail with some
instructions once I got it to move again
--
Dominique
next prev parent reply other threads:[~2018-02-18 8:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 11:56 Karl Dahlke
2018-02-15 18:48 ` Adam Thompson
2018-02-15 21:04 ` Karl Dahlke
2018-02-16 19:11 ` Adam Thompson
2018-02-18 2:19 ` Karl Dahlke
2018-02-18 2:42 ` Kevin Carhart
2018-02-18 3:03 ` Karl Dahlke
2018-02-18 3:39 ` Kevin Carhart
2018-02-18 7:43 ` Karl Dahlke
2018-02-18 8:17 ` Dominique Martinet [this message]
2018-02-18 8:47 ` Dominique Martinet
2018-02-18 8:30 ` Kevin Carhart
2018-02-18 7:45 ` Kevin Carhart
2018-02-18 8:55 ` Karl Dahlke
2018-02-18 11:29 ` Karl Dahlke
2018-02-18 14:08 ` Karl Dahlke
2018-02-19 1:07 ` [Edbrowse-dev] version / dyndns Kevin Carhart
2018-02-19 3:58 ` [Edbrowse-dev] update on dyndns Kevin Carhart
2018-03-24 16:07 [Edbrowse-dev] version Karl Dahlke
2018-03-25 8:11 ` Kevin Carhart
2018-06-11 15:45 [edbrowse-dev] version Karl Dahlke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180218081709.GA31140@nautica \
--to=asmadeus@codewreck.org \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).