When building Android on Ubuntu 16.04 LTS, this fixes an error for a missing header file:
In file included from ./src/android/io_realm_react_RealmReactModule.cpp:19:0:
/usr/lib/jvm/java-8-oracle/include/jni.h:45:20: fatal error: jni_md.h: No such file or directory
^
compilation terminated.
make: *** [/home/ashwinp/projects/realm-js/react-native/android/build/tmp/buildReactNdkLib/local/armeabi-v7a/objs-debug/realmreact/src/android/io_realm_react_RealmReactModule.o] Error 1
make: *** Waiting for unfinished jobs....
make: Leaving directory `/home/ashwinp/projects/realm-js/react-native/android/src/main/jni'
:buildReactNdkLib FAILED
FAILURE: Build failed with an exception.
* Stop trying to kill the server twice after testing
* Fix test targets to run before publishing
* ...
* Remove electron runner from publish for now
* Update changelog
* First take on running the tests inside an Electron render process
* Making progress
* Making it possible to override the location of the admin token
* Ignoreing the realm-object-server files
* Fixing a console.log to return a string instead of a boolean
But it should probably be removed entirely
* Making the downloaded ROS log less
* Adjusting comments in the test.sh
* Checking number of windows to determine an Electron crash
* Added a test that triggers garbage collection of ArrayBuffers
* Enabled the ability to run the tests in Electrons main process
* Run tests first in main process and the render
* Added a README.md that documents how Electron tests can be run
* Added a comment on why the garbage-collection test was added.
* Waiting with reading the admin token, until it is actually used
* Disabling the GarbageCollectionTests for now
Instead of manually allocating a chunk of memory and asking V8 to create an ArrayBuffer around it, have V8 create an ArrayBuffer with its own allocator and copy the data in it. (fixes#1197)
Remove an extra copy when reading data from ArrayBufferViews.
Remove TODOs for Node.js versions older than 4.
Instead of rethrowing the JavaScript error emitted from a callback function, we should instead pass it to `node::FatalException`.
Callbacks are employed when there is no other JavaScript frame on the stack prior so rethrowing the JS error as a C++ exception is not going to propagate the error back to JavaScript. `node::FatalException` will raise the `uncaughtError` event on the `process` object , print the error and stacktrace, and alert the debugger is there is one attached. This would make our async callbacks behave consistently with Node’s own async callbacks such as `setTimeout` when encountering an error.
Using a path relative to the `docs/conf.json` file seems to fix the `FATAL: Unable to load template: Cannot find module 'docs/jsdoc-template/template/publish'` issue.
See 0830c6e2f9.
agerson
Ashwin Phatak
Kenneth Geisshirt
Brian Munkholm
Jennifer Hooper
kristiandupont
blagoev
Kræn Hansen
Yavor Georgiev
Jagdeep Nagpal
toanz
Yavor Georgiev
Avi Warner
David Shore
Nikola Irinchev