github.com/mailgun/mailgun-go vendored in at rev
17e8bd11e87cb660ba5da8d635bbeae44b9443ac
github.com/pkg/errors vendored in at rev
f15c970de5b76fac0b59abb32d62c17cc7bed265
Fixes#980
Change-Id: I824ee3aa7493e062e6d916030dd62e0bd51ce477
Update myitcv.io/react to revision:
bca7c66b77ed8a5b86fb77cff70914c4a7cc3ce5
Update react, react-dom to v15.6.2 based on instructions in
https://reactjs.org/blog/2017/09/25/react-v15.6.2.html
Add vendor/embed/react/update.sh script to assist with future updates
Update mobile UI to fix problems documented here:
https://reactjs.org/warnings/legacy-factories.html
Update mobile.html and debug_console.html to use minified js
Fixes#977
Change-Id: I15ea81822e4f85669b321d5b3eb8b169f534def7
This switches most usages of the pre-1.7 context library to use the
standard library. Remaining usages are in:
app/publisher/main.go
pkg/fs/...
Change-Id: Ia74acc39499dcb39892342a2c9a2776537cf49f1
When on the permanode details aspect, and navigating from one permanode
to the next, if some change had already been started on the new
attribute row, the change would "propagate" to the next permanode, which
is not desirable.
That is because the state of the new attribute row was not reset on
navigation, which this change does.
Fixes#923
Change-Id: I6dee8763b2c1fcac4b3592b21adc954eab9d0ffe
This package has migrated away from code.google.com/p/go.crypto but
it's actually unused so just remove it.
Change-Id: I12882263471a396eda4b4b4580e919cd00a6b141
to Rev 48b2ede4844e13f1a2b7ce4d2529c9af7e359fc5
The qr package has moved from code.google.com/p/rsc/qr to it's new
canonical home at rsc.io/qr
Change-Id: Ibb04ee7e83c9707ff253a91abb4f60f9b150d61c
to Rev 9dfe39835686865bff950a07b394c12a98ddc811 for golang.org/x/html
to Rev 88f656faf3f37f690df1a32515b479415e1a6769 for golang.org/x/text
These packages moved from code.google.com to their new home
in golang.org/x/html and golang.org/x/text
Change-Id: I4ee45ae1e18eb05ef7b0a8ec69e2f1f11d140340
To rev 9dfe39835686865bff950a07b394c12a98ddc811
The xsrftoken package now lives in golang.org/x/net instead of code.google.com.
Change-Id: I4d98b1e50099dc7a1e1188f5c4311cd28c79f44a
Due to a change in the Android NDK (starting from r16), building the
docker container fails with an error during the installation of
gomobile:
fatal error: 'stdlib.h' file not found
This issue was addressed in more recent versions of gomobile, which
are compatible with the new NDK.
See https://github.com/golang/go/issues/21802
This CL simply updates gomobile to the most recent commit.
Change-Id: I87c468c34de441bc6acd40b717d1d950014e5a99
The ~/.gradle and ~/.android dirs are mounted as volumes for the docker
container when building the app, because we want the gradle and android
deps to be cached on the host after they've been downloaded.
The build process was assuming that these dirs always already existed,
and this assumption makes the building process fail if they actually
don't.
Therefore this change creates the directories on the host if they don't
already exist.
Change-Id: I90b5f73db0ffcbe76adc12157e142091808bde2b
It seems that on other (more modern?) configurations, the cgroup for
processes in docker is /system.slice/docker.service instead of /docker.
I have not been able to reproduce such a configuration. But until we have
a better way to detect whether a process is in docker, it's probably ok
to just add the new path to validate the detection, which this change
does.
Fixes#973
Change-Id: I9d52bcd79a906fdc1f8310b2c8063930cf9807fb
This CL addresses issues #685 and #862.
The general problem is that some critical errors, that lead clients such
as camput to exit with failure, are not displayed when not running in
verbose mode.
The reason that happens is because of code such as:
if *cmdmain.FlagVerbose {
log.SetOutput(cmdmain.Stderr)
} else {
log.SetOutput(ioutil.Discard)
}
which means that in non-verbose mode we discard absolutely all log
messages, even those that would be printed during a Fatal* call.
To address that problem, we introduce a logger, as well as the Printf
and Logf functions using it, in pkg/cmdmain. These two functions only
output when *cmdmain.FlagVerbose is true.
Commands such as camput or camtool should now always:
1) log.SetOutput(cmdmain.Stderr) in init().
2) use log.Printf for messages that should always be printed.
3) use cmdmain.Printf/Logf for messages that should only be printed when
*cmdmain.FlagVerbose is true.
4) use log.Fatal for critical errors.
5) optionally, set the Verbose and Logger of the client(s) they are
using.
Also, camput and camtool are now relying on the global -verbose flag
from cmdmain, instead of having to define one for each subcommand.
fixes#685fixes#862
Change-Id: I088032fd28184a201076097bf878894b22a8a120
I had pasted them from an example when I started to work on the map
aspect, and forgot to look up their meaning/use afterwards.
Fixes#964
Change-Id: Ic92dcd9641a7fad49707c24f114b370f2c887828
According to https://golang.org/pkg/html/template/#ErrorCode
(ErrPredefinedEscaper), the template engine already performs
sanitization equivalent to urlquery on any pipeline, and therefore makes
this extra urlquery call unnecessary, and even maybe harmful.
Change-Id: I7fcce395bf015b64022d1ac66b42069cdefb69eb
mpl