Require the Ruby English library prior to use

The use of English's $ERROR_INFO, rather than the standard $!, causes a warning in Ruby when no exceptions have previously occurred. Requiring the English library preloads and initializes the global and removes this warning.

This is literally the first time I hear about such a thing. Anyways, the build failed, and as I managed to dig up you have to actually require a capital English. Can you please update and send it in again? Also, is there some way we might be able to test this?

Wow, good catch! I think this might be the only standard library in Ruby that I've seen that is required with a titlecased name.
As for testing it, maybe there's something that can be done with a variable defined check, but I kind of doubt it...

And, of course all of the tests pass locally... because MacOS X is case-insensitive by default. :frowning:
I'll force-push a new commit onto my branch and this pull request in a moment.

I attempted to update the code to make the Ruby warnings more apparent, but I'm not seeing the warnings when running the local test suite.
This is the Rakefile modification if you'd like to enable Ruby warnings:
diff --git a/Rakefile b/Rakefile
index fd64fc3..5a92f24 100644
--- a/Rakefile
+++ b/Rakefile
@@ -14,6 +14,7 @@ Rake::Task[:build].prerequisites.unshift :fix_permissions

 require "rspec/core/rake_task"
 RSpec::Core::RakeTask.new(:spec) do |spec|
+  spec.ruby_opts = "-w"
   spec.pattern = FileList["spec/*_spec.rb"]
 end

+1 Using rspec 3.2.0 (no rake task, just the rspec command) with simplecov raises this warning for me.
I'm using the default generated spec_helper (from rspec --init) with the one change that I require and start simplecov at the top of my spec helper.

@colszowka this looks fine to me to merge.
re adding warnings, the problem is that by setting the RUBY_OPTS=-w you'll get a warnings from anything in ruby, so we'd need to filter by SimpleCover.root. See https://github.com/metricfu/metric_fu/blob/master/spec/capture_warnings.rb for a way I've done this

We fixed this a different way, by just not using ERROR_INFO.


Not able to install V 0.1.21

Steps to reproduce
asdf install v 0.1.21
==> Checking whether specified V release/reference exists...
==> Downloading 0.1.21 to /tmp/v_build_S9kr9w/v-version-0.1.21-src.tar.gz from https://github.com/vlang/v/archive/0.1.21.tar.gz
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100   115    0   115    0     0    129      0 --:--:-- --:--:-- --:--:--   129
100 1444k    0 1444k    0     0  45631      0 --:--:--  0:00:32 --:--:-- 69319
==> Copying release into place
==> Checking whether specified release/reference containing v.c exists...
==> Downloading 0.1.21 to /tmp/v_build_S9kr9w/v-version-0.1.21-v.c from https://github.com/vlang/vc/archive/0.1.21.tar.gz
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100   116    0   116    0     0     12      0 --:--:--  0:00:09 --:--:--    29
100    15  100    15    0     0      1      0  0:00:15  0:00:11  0:00:04    22
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
Expected behavior
vlang should have been installed
Actual behavior
vlang should have been installed from tar.gz file but it expects zip format for extraction and installation
Environment
OS: ubuntu
Linux 5.0.0-32-generic #34-Ubuntu
asdf version:
➜ asdf version
version: v0.7.4

Reference : https://github.com/asdf-vm/asdf/issues/580#issuecomment-543936530

Any update!!

Thanks for the information!
I haven't been watching V's changelog for a while... I'll give a look and try to fix it.


BTC / Stablesats explainer

Problem
Too much text explaining the difference between Stablesats and BTC
Solution
Graphical representation and more compact text:
EN: Use your Stablesats account in Blink to keep the money in your wallet stable in fiat (dollar) terms.
ES: Utiliza tu cuenta Stablesats en Blink para mantener el dinero de tu cartera estable en términos fiat (dólares). Utiliza tu cuenta Bitcoin si estás acumulando sats y te parece bien que tu saldo fiat cambie todo el tiempo.
SVG:

while I think that make sense to have stablesats going down if we're tweeting about it - ie: to reflect the inflation, I don't think it will help for the comprehension of stablesats in the first place.
basically, only if you're very advanced in the comprehension of money and finance you get the graphical representation as it is now.
if you're just getting started, having stablesats as a straight line would help in the comprehension imo

You are right.  My maxi-bias is showing. Can we settle on tiny tiny down angle? :)

@nicolasburtey is it ok like this? (image above)


Question: Is there a way to check for the completion of asynchronous operations?

I would be interested in finding a (cost-effective) way to make sure that an asynchronous operation (mainly put operation) is completed. I need to use the asynchronous option, as I would like to do some other work while waiting for operation's completion.
I tried to look for it in the documentation and a bit in the code, but I could not find it.
Thanks in advance.

I'm assuming you're talking about WriteOptions::sync. This is only a flag for synchronous file I/O. The put is actually done when leveldb::DB::Put() returned, but the data may not be on disk yet, and is instead in a filesystem data buffer.

Thanks for your answer. I'd like to use asynchronous file I/O (with WriteOptions::async) and then, later in the code, check for the completion of this operation. Is there a way to do that with LevelDB? Thanks!

No, if your goal is to know that the transaction is on disk, so that, for example, the power plug could be pulled the instant the transaction is done then you need to do synchronous I/O. But, if you only need to protect against a crash then async I/O is sufficient as the data is now in the filesystem buffers, and will land on disk eventually.

Ok, I see. I'm more interested in the first use case you mention (knowing when the transaction is on disk). Do you know if there is any future plan to implement this functionality? Thanks for your clarification!


Feature coinjoin mix 1 round

Issue being fixed or feature implemented

What was done?

How Has This Been Tested?

Breaking Changes

Checklist:

[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated relevant unit/integration/functional/e2e tests
[ ] I have made corresponding changes to the documentation

For repository code-owners and collaborators only

[ ] I have assigned this pull request to a milestone

in the linux CI there is this exception in a test that results in failure.  I will try to fix this in the unit test story that comes next.
org.bitcoinj.quorums.QuorumRotationStateTest > loadFromBootStrapFileV3 FAILED
    java.lang.AssertionError: unable to load bootstrap file
        at org.junit.Assert.fail(Assert.java:89)
        at org.bitcoinj.quorums.QuorumRotationStateTest.loadFromBootStrapFileV3(QuorumRotationStateTest.java:70)


Changing Layout Direction

Hi,
It's a great calendar. The only thing I need is the ability to change the direction of layout. As you know some languages such as Persian or Arabic are written from right to left. I can change the numbers and text to Persian using locale property on NSDateFormatter objects. But the navigation should be exactly reversed so that it feels natural to Persian speaking users. I mean that swiping to right should go to next month instead of previous month. Also I need the days to lay themselves out from right to left in each row; let's say 1 is in the right most location and 7 is in the left most and then 8 is in the right most in the 2nd row and so on. I hope you get what I mean and could help me how to do it. @jonathantribouharet

Ok, i see what i can do.

I added the readFromRightToLeft option to calendarAppearence, just set it to YESand tell me if it's good, i may have miss something. Don't forget to update the pod with pod update.

 I don't know how to thank you. I really didn't except you to update this soon.
I checked. Essentially everything looks OK except for just a little thing. Now the next and previous is literally reversed. Now when we swipe to right, the "Next" page is being loaded. If you check the example you see that the Logs show something else. I think these two methods calls need updating somewhere.

(void)calendarDidLoadPreviousPage;
(void)calendarDidLoadNextPage;

Other than this, everything works perfectly.
Je vous remercie autre fois! ;-)

I hesitate about calendarDidLoadPreviousPage but i let it the way because it loads the previous page but not the previous month.


Documentation Improvements?

I am happy to update the tutorial as I work through it but I don't want to spend effort if it isn't going to be accepted.
I am thinking of removing the section on stack. I couldn't get stack to behave
~/Dropbox/Private/CloudHaskell $ stack build
While constructing the BuildPlan the following exceptions were encountered:

--  Failure when adding dependencies:
      distributed-process: needed (-any), latest is 0.5.5, but not present in build plan
      network-transport-tcp: needed (-any), latest is 0.4.2, but not present in build plan
    needed for package: CloudHaskell-<IP_ADDRESS>

--  While attempting to add dependency,
    Could not find package distributed-process in known packages

--  While attempting to add dependency,
    Could not find package network-transport-tcp in known packages

Recommended action: try adding the following to your extra-deps in /Users/dom/Dropbox/Private/CloudHaskell/stack.yaml
- distributed-process-0.5.5
- network-transport-tcp-0.4.2

You may also want to try the 'stack solver' command

But using cabal did work. I'd suggest just saying something like, "you will need to have the packages distributed-process and network-transport-tcp" available using stack or cabal"

Next problem. The first example does not work. The program runs but no output is produced. Presumably the main thread (not sure of the terminology here) finishes before the child manages to get going.
On the other this worked for me.
import Network.Transport.TCP (createTransport, defaultTCPParameters)
import Control.Distributed.Process
import Control.Distributed.Process.Node

main :: IO ()
main = do
  Right t <- createTransport "<IP_ADDRESS>" "10501" defaultTCPParameters
  node <- newLocalNode t initRemoteTable
  _ <- forkProcess node $ do
    self <- getSelfPid
    send self "hello"
    hello <- expect :: Process String
    liftIO $ putStrLn hello
  c <- getChar
  putStrLn $ show c
  return ()

Thanks for the report. Best to open Github issues regarding the website against the relevant repository: https://github.com/haskell-distributed/haskell-distributed.github.com.

Regarding the first issue: stack build is telling the user exactly what she's supposed to do. Have you tried copy/pasting the lines stack prints in the stack.yaml and check that it works? I don't see any particular issue here.
For the second issue, I pushed the following fix: use runProcess everywhere in that chapter of the tutorial. Not sure why the original author chose to use forkProcess instead.

I tried add the lines to stack.yaml and got
Recommended action: try adding the following to your extra-deps in /Users/dom/Dropbox/Private/CloudHaskell/stack.yaml
- distributed-static-<IP_ADDRESS>
- rank1dynamic-<IP_ADDRESS>

You may also want to try the 'stack solver' command

So I added those lines as well and now I get
~/Dropbox/Private/CloudHaskell $ stack install
While constructing the BuildPlan the following exceptions were encountered:

--  Failure when adding dependencies:
      distributed-process: needed (-any), latest is 0.5.5, but couldn't resolve its dependencies
    needed for package: CloudHaskell-<IP_ADDRESS>

--  Failure when adding dependencies:
      syb: needed (>=0.3 && <0.5), latest is 0.5.1, but 0.5.1 found
    needed for package: distributed-process-0.5.5

I couldn't work out what stack is trying to tell me.


Redesign the Feedback dialog!

Feature Request
The feedback dialog doesn't look so hot, it doesn't blend in with the current UI direction at all and it needs to be fixed!
Design
Use this design as a guideline, it will probably be needed to be tweaked during implementation and that is ok! Use the second image for the text colors as those reflect the design better.

Still needs to scale to mobile support!

@Druage Has this been completed?

This has been developed and migrated to PROD.


chore: bdd-nh-1585371942 to 0.0.1

chore: Promote bdd-nh-1585371942 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Make AssumeSortedStarts easier to use

I'm trying to replace my own range set implementation with this crate, and something I need to do often is merge sorted ranges that are not necessarily disjoint. It seems like UnionIter and AssumeSortedStarts are the right tools for this. There are a few small changes that I think would improve this use case:

Document SortedStarts and AssumeSortedStarts. I find it odd that these have #[doc(hidden)]. It was not obvious that such APIs existed until I snooped around the code a bit.
Add a constructor for AssumeSortedStarts which takes I: IntoIterator. Right now it only takes I: Iterator, so I have to manually call into_iter() when I use it.
Maybe add an extension trait so I can do something like: [0..1, 0..2].assume_sorted() instead of AssumeSortedStarts::new([0..1, 0..2]).

I can probably make a PR with these changes if you like.

Duncan,
Thanks for looking at using RangeSetBlaze!
These seem like great changes. I welcome your PR.
I wonder if we should also create a new constructor for RangeSetBlaze, itself, something like from_sorted_starts? That way, people who have sorted starts would not need to learn about UnionIter.
-- Carl
p.s. I'm working on adding RangeMapBlaze, a map. I leave on a 1-week vacation in a few days.

I wonder if we should also create a new constructor for RangeSetBlaze, itself, something like from_sorted_starts? That way, people who have sorted starts would not need to learn about UnionIter.

That could be nice! I don't personally use RangeSetBlaze, but maybe I would if it were serde-serializable. Actually, if we had a RangeSetBlaze::into_inner that returned the BTreeMap, that would make it trivially serializable.

Duncan, it's published! Thanks for your contribution.
https://crates.io/crates/range-set-blaze
The only change I made was to remove one .into_iter() that Clippy said wasn't needed. I appreciate that you cleaned up the many now-not-needed .into_iters() in the tests. Also, replacing RangeSetBlaze with Self was good.
Finally, thanks for even noticing the SortedDisjoint/SortedStarts features. It's my favorite part of the code but is hidden from most users.


Create docker config for patient/caregiver app

Create docker config.
Add ecareplan domain for patient/caregiver. Use my.ecareplan.org

New requirement from RTI/OHSU, if possible:  Create a v2 patient app Docker config that appears to be the SAME APP as they deployed in v1, including:

same client ID at OHSU
same launch and redirect URLs

If possible, they would like to reuse the existing Epic app config, but launch the new v2 app.

@swmuir After more discussion with RTI and OHSU, they decided that OHSU would like to allow both v1 and v2 patient apps to be available at the same time.  So the the v2 app should allow for a different app client ID in their Epic config and a different launch/redirect URL.
Please work with Matt at OHSU to test installation of the v2 app Docker.  They would like to get a proof-of-concept install running for testing differences from v1 for inviting patients to access the app.

I don't know how custom deployment config files are included in Docker container so that OHSU can add their own app client ID.  I am using a .env.local file (which is not committed to GitHub for security of IDs).  How would they provide their own .env.local?  Matt said something about a file system directory outside of the Docker container?  I attached my .env.local used for testing and current deployment on GitHub.io
Epic production client config
REACT_APP_CLIENT_ID_epic=ea547248-2c6b-4df5-aa52-847e17e19225
Epic Sandbox for USCDI app
REACT_APP_CLIENT_ID_epic_sandbox=b62c9e05-83ac-4fd7-921d-7554e9b4d585
#Cerner sandbox
REACT_APP_CLIENT_ID_cerner=bd18953e-af7d-41b3-8585-58b0924a044f
Logica
REACT_APP_CLIENT_ID_logica=7cbe9095-f665-4bee-8857-0451ddb72e90
Meld
REACT_APP_CLIENT_ID_meld_mcc=2dbe1620-7232-4ab7-a5e5-4ee85112a74e
REACT_APP_CLIENT_ID_meld_qa=0e440b74-e49d-4975-9da7-a6afdea9e426
REACT_APP_CLIENT_ID_meld_synthea=2ce6fc18-6f3f-4e8a-b50f-540634aaf26b
ACF ODH Sandbox
REACT_APP_CLIENT_ID_acf_odh=3dc692db-72eb-41a0-97ea-2e7d3a3b769d

QA: when Matt Storer is able to run this.

@swmuir docker name: mcc ecare


can it support multi axis pptx

hello man ,I want to build a pptx with two axes,how can i do to realize it

Hi @MyronKing123456 ,
I'm not sure what you're asking for... a chart of some kind?

well, if i have two series of data, No1:[1,2,3,4]  No2:[1000,2000,3000,4000], if they share just one value axis,the chart will be terrible,so ,i need a sub axis to represent it ,i just want to know if it's possible

Hi @MyronKing123456 ,
No, Charts can only have one axis.
However, I did have another user who created a cleaver work-around.  He used low opacity and place one chart on top of another...

Well,I got it ,Thanks very much~


Error starting up Coordinator

Hi I am having an issue starting up the coordinator using version 3.1.8.  I am not sure if this is a bug or user error.
This is the command i am using to launch the coordinator
 sudo /usr/sbin/arangod --server.authentication=false --server.endpoint tcp://$HOSTNAME:28530 --cluster.my-address tcp://$HOSTNAME:28530 --cluster.my-local-info osdi-03-coordinator --cluster.my-role COORDINATOR --cluster.agency-endpoint tcp://$HOSTNAME:25001 /data/data/arango/cordinator
And here's the error message i am getting.  Please let me know how i can resolve this
2017-01-22T20:22:06Z [15360] INFO file-descriptors (nofiles) hard limit is 999999, soft limit is<PHONE_NUMBER>-01-22T20:22:06Z [15360] INFO created database directory '/data/data/arango/cordinator'. 2017-01-22T20:22:06Z [15360] INFO WAL directory '/data/data/arango/cordinator/journals' does not exist. creating it... 2017-01-22T20:22:06Z [15360] INFO JavaScript using startup '//usr/share/arangodb3/js', application '/var/lib/arangodb3-apps' 2017-01-22T20:22:09Z [15360] INFO Cluster feature is turned on. Agency version: {"server":"arango","version":"3.1.8","license":"community"}, Agency endpoints: http+tcp://osdi-03:25001, server id: 'Coordinator001', internal address: tcp://osdi-03:28530, role: COORDINATOR 2017-01-22T20:22:09Z [15360] INFO using heartbeat interval value '1000 ms' from agency 2017-01-22T20:22:09Z [15360] INFO In database '_system': No version information file found in database directory. 2017-01-22T20:22:09Z [15360] INFO In database '_system': Database is up-to-date (30108/cluster-local/init) 2017-01-22T20:22:09Z [15360] INFO using endpoint 'http+tcp://osdi-03:28530' for non-encrypted requests 2017-01-22T20:22:09Z [15360] INFO In database '_system': Found 14 defined task(s), 12 task(s) to run 2017-01-22T20:22:09Z [15360] INFO In database '_system': state coordinator-global/init, tasks setupGraphs, setupUsers, createUsersIndex, addDefaultUserSystem, createModules, createRouting, insertRedirectionsAll, setupAqlFunctions, createStatistics, createFrontend, setupQueues, setupJobs 2017-01-22T20:22:09Z [15360] WARNING {cluster} createCollectionCoordinator: replicationFactor is too large for the number of DBservers 2017-01-22T20:22:15Z [15360] WARNING {cluster} createCollectionCoordinator: replicationFactor is too large for the number of DBservers 2017-01-22T20:22:25Z [15360] ERROR In database '_system': Executing task #4 (addDefaultUserSystem: add default root user for system database) failed with exception: ArangoError 502: could not determine number of documents in collection (while optimizing plan) ArangoError: could not determine number of documents in collection (while optimizing plan) 2017-01-22T20:22:25Z [15360] ERROR     at Error (native) 2017-01-22T20:22:25Z [15360] ERROR     at ArangoStatement.execute (/usr/share/arangodb3/js/server/modules/@arangodb/arango-statement.js:81:16) 2017-01-22T20:22:25Z [15360] ERROR     at ArangoDatabase._query (/usr/share/arangodb3/js/server/modules/@arangodb/arango-database.js:79:45) 2017-01-22T20:22:25Z [15360] ERROR     at SimpleQueryByExample.execute (/usr/share/arangodb3/js/server/modules/@arangodb/simple-query.js:137:42) 2017-01-22T20:22:25Z [15360] ERROR     at SimpleQueryByExample.SimpleQuery.toArray (/usr/share/arangodb3/js/common/modules/@arangodb/simple-query-common.js:340:8) 2017-01-22T20:22:25Z [15360] ERROR     at ArangoCollection.firstExample (/usr/share/arangodb3/js/server/modules/@arangodb/arango-collection.js:287:71) 2017-01-22T20:22:25Z [15360] ERROR     at Object.exports.save (/usr/share/arangodb3/js/server/modules/@arangodb/users.js:135:22) 2017-01-22T20:22:25Z [15360] ERROR     at Object.addTask.task (/usr/share/arangodb3/js/server/upgrade-database.js:510:21) 2017-01-22T20:22:25Z [15360] ERROR     at runTasks (/usr/share/arangodb3/js/server/upgrade-database.js:274:27) 2017-01-22T20:22:25Z [15360] ERROR     at upgradeDatabase (/usr/share/arangodb3/js/server/upgrade-database.js:346:16) 2017-01-22T20:22:25Z [15360] ERROR In database '_system': Executing task #4 (addDefaultUserSystem: add default root user for system database) failed. Aborting init procedure. 2017-01-22T20:22:25Z [15360] ERROR In database '_system': Please fix the problem and try starting the server again. 2017-01-22T20:22:25Z [15360] ERROR upgrade-database.js for cluster script failed! 2017-01-22T20:22:25Z [15360] WARNING {cluster} createCollectionCoordinator: replicationFactor is too large for the number of DBservers 2017-01-22T20:22:35Z [15360] ERROR ArangoError: could not determine number of documents in collection (while optimizing plan) 2017-01-22T20:22:35Z [15360] ERROR     at Error (native) 2017-01-22T20:22:35Z [15360] ERROR     at ArangoStatement.execute (/usr/share/arangodb3/js/server/modules/@arangodb/arango-statement.js:81:16) 2017-01-22T20:22:35Z [15360] ERROR     at ArangoDatabase._query (/usr/share/arangodb3/js/server/modules/@arangodb/arango-database.js:79:45) 2017-01-22T20:22:35Z [15360] ERROR     at SimpleQueryAll.execute (/usr/share/arangodb3/js/server/modules/@arangodb/simple-query.js:96:42) 2017-01-22T20:22:35Z [15360] ERROR     at SimpleQueryAll.SimpleQuery.hasNext (/usr/share/arangodb3/js/common/modules/@arangodb/simple-query-common.js:388:8) 2017-01-22T20:22:35Z [15360] ERROR     at refillCaches (/usr/share/arangodb3/js/server/modules/@arangodb/foxx/manager.js:265:17) 2017-01-22T20:22:35Z [15360] ERROR     at Object.initializeFoxx (/usr/share/arangodb3/js/server/modules/@arangodb/foxx/manager.js:1483:3) 2017-01-22T20:22:35Z [15360] ERROR     at Object.foxxes (/usr/share/arangodb3/js/server/bootstrap/foxxes.js:64:47) 2017-01-22T20:22:35Z [15360] ERROR     at server/bootstrap/cluster-bootstrap.js:51:54 2017-01-22T20:22:35Z [15360] ERROR     at server/bootstrap/cluster-bootstrap.js:55:2 2017-01-22T20:22:35Z [15360] ERROR JavaScript exception in file<EMAIL_ADDRESS>at 108,7: TypeError: Cannot read property 'save' of undefined 2017-01-22T20:22:35Z [15360] ERROR !      throw err; 2017-01-22T20:22:35Z [15360] ERROR !      ^ 2017-01-22T20:22:35Z [15360] FATAL error during execution of JavaScript file 'server/bootstrap/coordinator.js'

can you please post your error message enclosed with tripple backticks.
Thanks in advance.

Hi Sorry for the bad formatting.  Below is the  full error message.
2017-01-23T13:25:58Z [14499] ERROR In database '_system': Executing task #4 (addDefaultUserSystem: add default root user for system database) failed with exception: ArangoError 502: could not determine number of documents in collection (while optimizing plan) ArangoError: could not determine number of documents in collection (while optimizing plan)
2017-01-23T13:25:58Z [14499] ERROR     at Error (native)
2017-01-23T13:25:58Z [14499] ERROR     at ArangoStatement.execute (/usr/share/arangodb3/js/server/modules/@arangodb/arango-statement.js:81:16)
2017-01-23T13:25:58Z [14499] ERROR     at ArangoDatabase._query (/usr/share/arangodb3/js/server/modules/@arangodb/arango-database.js:79:45)
2017-01-23T13:25:58Z [14499] ERROR     at SimpleQueryByExample.execute (/usr/share/arangodb3/js/server/modules/@arangodb/simple-query.js:137:42)
2017-01-23T13:25:58Z [14499] ERROR     at SimpleQueryByExample.SimpleQuery.toArray (/usr/share/arangodb3/js/common/modules/@arangodb/simple-query-common.js:340:8)
2017-01-23T13:25:58Z [14499] ERROR     at ArangoCollection.firstExample (/usr/share/arangodb3/js/server/modules/@arangodb/arango-collection.js:287:71)
2017-01-23T13:25:58Z [14499] ERROR     at Object.exports.save (/usr/share/arangodb3/js/server/modules/@arangodb/users.js:135:22)
2017-01-23T13:25:58Z [14499] ERROR     at Object.addTask.task (/usr/share/arangodb3/js/server/upgrade-database.js:510:21)
2017-01-23T13:25:58Z [14499] ERROR     at runTasks (/usr/share/arangodb3/js/server/upgrade-database.js:274:27)
2017-01-23T13:25:58Z [14499] ERROR     at upgradeDatabase (/usr/share/arangodb3/js/server/upgrade-database.js:346:16)
2017-01-23T13:25:58Z [14499] ERROR In database '_system': Executing task #4 (addDefaultUserSystem: add default root user for system database) failed. Aborting init procedure.
2017-01-23T13:25:58Z [14499] ERROR In database '_system': Please fix the problem and try starting the server again.
2017-01-23T13:25:58Z [14499] ERROR upgrade-database.js for cluster script failed!
2017-01-23T13:25:58Z [14499] WARNING {cluster} createCollectionCoordinator: replicationFactor is too large for the number of DBservers
2017-01-23T13:26:08Z [14499] ERROR ArangoError: could not determine number of documents in collection (while optimizing plan)
2017-01-23T13:26:08Z [14499] ERROR     at Error (native)
2017-01-23T13:26:08Z [14499] ERROR     at ArangoStatement.execute (/usr/share/arangodb3/js/server/modules/@arangodb/arango-statement.js:81:16)
2017-01-23T13:26:08Z [14499] ERROR     at ArangoDatabase._query (/usr/share/arangodb3/js/server/modules/@arangodb/arango-database.js:79:45)
2017-01-23T13:26:08Z [14499] ERROR     at SimpleQueryAll.execute (/usr/share/arangodb3/js/server/modules/@arangodb/simple-query.js:96:42)
2017-01-23T13:26:08Z [14499] ERROR     at SimpleQueryAll.SimpleQuery.hasNext (/usr/share/arangodb3/js/common/modules/@arangodb/simple-query-common.js:388:8)
2017-01-23T13:26:08Z [14499] ERROR     at refillCaches (/usr/share/arangodb3/js/server/modules/@arangodb/foxx/manager.js:265:17)
2017-01-23T13:26:08Z [14499] ERROR     at Object.initializeFoxx (/usr/share/arangodb3/js/server/modules/@arangodb/foxx/manager.js:1483:3)
2017-01-23T13:26:08Z [14499] ERROR     at Object.foxxes (/usr/share/arangodb3/js/server/bootstrap/foxxes.js:64:47)
2017-01-23T13:26:08Z [14499] ERROR     at server/bootstrap/cluster-bootstrap.js:51:54
2017-01-23T13:26:08Z [14499] ERROR     at server/bootstrap/cluster-bootstrap.js:55:2
2017-01-23T13:26:08Z [14499] ERROR JavaScript exception in file<EMAIL_ADDRESS>at 108,7: TypeError: Cannot read property 'save' of undefined
2017-01-23T13:26:08Z [14499] ERROR !      throw err;
2017-01-23T13:26:08Z [14499] ERROR !      ^
2017-01-23T13:26:08Z [14499] FATAL error during execution of JavaScript file 'server/bootstrap/coordinator.js'

if i run the coordinator again for the next time the first error messages goes away see below:
2017-01-23T13:27:03Z [14669] INFO ArangoDB 3.1.8 [linux] 64bit, using VPack 0.1.30, ICU 54.1, V8 <IP_ADDRESS>, OpenSSL 1.0.1e-fips 11 Feb 2013
2017-01-23T13:27:03Z [14669] INFO using SSL options: SSL_OP_CIPHER_SERVER_PREFERENCE, SSL_OP_TLS_ROLLBACK_BUG
2017-01-23T13:27:03Z [14669] INFO Waiting for DBservers to show up...
2017-01-23T13:27:04Z [14669] INFO Waiting for DBservers to show up...
2017-01-23T13:27:05Z [14669] INFO Waiting for DBservers to show up...
2017-01-23T13:27:06Z [14669] INFO Waiting for DBservers to show up...
2017-01-23T13:27:07Z [14669] INFO Waiting for DBservers to show up...
2017-01-23T13:27:08Z [14669] INFO Waiting for DBservers to show up...
2017-01-23T13:27:09Z [14669] INFO Waiting for DBservers to show up...
2017-01-23T13:27:10Z [14669] INFO Waiting for DBservers to show up...
2017-01-23T13:27:11Z [14669] INFO Waiting for DBservers to show up...
2017-01-23T13:27:12Z [14669] INFO Waiting for DBservers to show up...
2017-01-23T13:27:13Z [14669] INFO Waiting for DBservers to show up...
2017-01-23T13:27:14Z [14669] INFO Waiting for DBservers to show up...
2017-01-23T13:27:15Z [14669] INFO Waiting for DBservers to show up...
2017-01-23T13:27:16Z [14669] INFO Waiting for DBservers to show up...
2017-01-23T13:27:17Z [14669] INFO Waiting for DBservers to show up...
2017-01-23T13:27:18Z [14669] INFO Waiting for DBservers to show up...
2017-01-23T13:27:18Z [14669] INFO Found 1 DBservers.
2017-01-23T13:27:18Z [14669] INFO file-descriptors (nofiles) hard limit is 999999, soft limit is 999999
2017-01-23T13:27:18Z [14669] INFO JavaScript using startup '//usr/share/arangodb3/js', application '/var/lib/arangodb3-apps'
2017-01-23T13:27:21Z [14669] INFO Cluster feature is turned on. Agency version: {"server":"arango","version":"3.1.8","license":"community"}, Agency endpoints: http+tcp://osdi-03:25001, server id: 'Coordinator001', internal address: tcp://osdi-03:8530, role: COORDINATOR
2017-01-23T13:27:21Z [14669] INFO using heartbeat interval value '1000 ms' from agency
2017-01-23T13:27:21Z [14669] INFO In database '_system': Database is up-to-date (30108/cluster-local/existing)
2017-01-23T13:27:21Z [14669] INFO using endpoint 'http+tcp://osdi-03:8530' for non-encrypted requests
2017-01-23T13:27:21Z [14669] ERROR JavaScript exception in file<EMAIL_ADDRESS>at 108,7: TypeError: Cannot read property 'save' of undefined
2017-01-23T13:27:21Z [14669] ERROR !      throw err;
2017-01-23T13:27:21Z [14669] ERROR !      ^
2017-01-23T13:27:21Z [14669] FATAL error during execution of JavaScript file 'server/bootstrap/coordinator.js'

I have been blocked on this issue for a while now.  If you have any ideas and/or suggestions please let me know.
Thanks

https://github.com/arangodb/arangodb/blob/v3.1.8/js/server/modules/%40arangodb/foxx/queues/index.js#L108
Do you run a existing setup or a new one?

I am running arango agency, primary db, and coordinator services on just one node currently and the intent will to scale it once it works.  The root data directory is /data/data/arango which is an empty directory. the agency will write to /data/data/arango/agency, and so forth.
Below is how I am running the services and the log messages that are associated with each service
First I run the agency which works:
sudo /usr/sbin/arangod --agency.activate true --server.endpoint tcp://<IP_ADDRESS>:25001 --server.authentication false --agency.size 1 --agency.supervision true --database.directory /data/data/arango/agency

2017-01-23T16:03:49Z [21166] INFO ArangoDB 3.1.8 [linux] 64bit, using VPack 0.1.30, ICU 54.1, V8 <IP_ADDRESS>, OpenSSL 1.0.1e-fips 11 Feb 2013
2017-01-23T16:03:49Z [21166] INFO using SSL options: SSL_OP_CIPHER_SERVER_PREFERENCE, SSL_OP_TLS_ROLLBACK_BUG
2017-01-23T16:03:49Z [21166] INFO file-descriptors (nofiles) hard limit is 999999, soft limit is 999999
2017-01-23T16:03:49Z [21166] INFO created database directory '/data/data/arango/agency'.
2017-01-23T16:03:49Z [21166] INFO WAL directory '/data/data/arango/agency/journals' does not exist. creating it...
2017-01-23T16:03:49Z [21166] INFO JavaScript using startup '//usr/share/arangodb3/js', application '/var/lib/arangodb3-apps'
2017-01-23T16:03:53Z [21166] INFO In database '_system': No version information file found in database directory.
2017-01-23T16:03:53Z [21166] INFO In database '_system': Found 14 defined task(s), 12 task(s) to run
2017-01-23T16:03:53Z [21166] INFO In database '_system': state standalone/init, tasks setupGraphs, setupUsers, createUsersIndex, addDefaultUserSystem, createModules, createRouting, insertRedirectionsAll, setupAqlFunctions, createStatistics, createFrontend, setupQueues, setupJobs
2017-01-23T16:03:53Z [21166] INFO In database '_system': init successfully finished
2017-01-23T16:03:53Z [21166] INFO using endpoint 'http+tcp://<IP_ADDRESS>:25001' for non-encrypted requests
2017-01-23T16:03:58Z [21166] INFO ArangoDB (version 3.1.8 [linux]) is ready for business. Have fun!

Then I run the primary db server which also seems to work:
/usr/sbin/arangod --server.authentication=false --server.endpoint tcp://<IP_ADDRESS>:8529 --cluster.my-address tcp://$HOSTNAME:8529 --cluster.my-local-info $HOSTNAME-primary --cluster.my-role PRIMARY --cluster.agency-endpoint tcp://$HOSTNAME:25001 --database.directory /data/data/arango/db

2017-01-23T16:13:51Z [21820] INFO ArangoDB 3.1.8 [linux] 64bit, using VPack 0.1.30, ICU 54.1, V8 <IP_ADDRESS>, OpenSSL 1.0.1e-fips 11 Feb 2013
2017-01-23T16:13:51Z [21820] INFO using SSL options: SSL_OP_CIPHER_SERVER_PREFERENCE, SSL_OP_TLS_ROLLBACK_BUG
2017-01-23T16:13:51Z [21820] INFO file-descriptors (nofiles) hard limit is 999999, soft limit is 999999
2017-01-23T16:13:51Z [21820] INFO created database directory '/data/data/arango/db'.
2017-01-23T16:13:51Z [21820] INFO WAL directory '/data/data/arango/db/journals' does not exist. creating it...
2017-01-23T16:13:51Z [21820] INFO JavaScript using startup '//usr/share/arangodb3/js', application '/var/lib/arangodb3-apps'
2017-01-23T16:13:55Z [21820] INFO Cluster feature is turned on. Agency version: {"server":"arango","version":"3.1.8","license":"community"}, Agency endpoints: http+tcp://osdi-03:25001, server id: 'DBServer001', internal address: tcp://osdi-03:8529, role: PRIMARY
2017-01-23T16:13:55Z [21820] INFO using heartbeat interval value '1000 ms' from agency
2017-01-23T16:13:55Z [21820] INFO In database '_system': No version information file found in database directory.
2017-01-23T16:13:55Z [21820] INFO In database '_system': Database is up-to-date (30108/cluster-local/init)
2017-01-23T16:13:55Z [21820] INFO using endpoint 'http+tcp://<IP_ADDRESS>:8529' for non-encrypted requests
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO In database '_system': Database is up-to-date (-/db-server-local/init)
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO bootstraped DB server DBServer001
2017-01-23T16:13:55Z [21820] INFO ArangoDB (version 3.1.8 [linux]) is ready for business. Have fun!

Lastly I run the the coordinator and it errors out
/usr/sbin/arangod --server.authentication=false --server.endpoint tcp://$HOSTNAME:8530 --cluster.my-address tcp://$HOSTNAME:8530 --cluster.my-local-info $HOSTNAME-coordinator --cluster.my-role COORDINATOR --cluster.agency-endpoint tcp://osdi-03:25001 /data/data/arango/coordinator

2017-01-23T16:16:07Z [22740] INFO ArangoDB 3.1.8 [linux] 64bit, using VPack 0.1.30, ICU 54.1, V8 <IP_ADDRESS>, OpenSSL 1.0.1e-fips 11 Feb 2013
2017-01-23T16:16:07Z [22740] INFO using SSL options: SSL_OP_CIPHER_SERVER_PREFERENCE, SSL_OP_TLS_ROLLBACK_BUG
2017-01-23T16:16:07Z [22740] INFO Waiting for DBservers to show up...
2017-01-23T16:16:08Z [22740] INFO Waiting for DBservers to show up...
2017-01-23T16:16:09Z [22740] INFO Waiting for DBservers to show up...
2017-01-23T16:16:10Z [22740] INFO Waiting for DBservers to show up...
2017-01-23T16:16:11Z [22740] INFO Waiting for DBservers to show up...
2017-01-23T16:16:13Z [22740] INFO Waiting for DBservers to show up...
2017-01-23T16:16:14Z [22740] INFO Waiting for DBservers to show up...
2017-01-23T16:16:15Z [22740] INFO Waiting for DBservers to show up...
2017-01-23T16:16:16Z [22740] INFO Waiting for DBservers to show up...
2017-01-23T16:16:17Z [22740] INFO Waiting for DBservers to show up...
2017-01-23T16:16:18Z [22740] INFO Waiting for DBservers to show up...
2017-01-23T16:16:19Z [22740] INFO Waiting for DBservers to show up...
2017-01-23T16:16:20Z [22740] INFO Waiting for DBservers to show up...
2017-01-23T16:16:21Z [22740] INFO Waiting for DBservers to show up...
2017-01-23T16:16:22Z [22740] INFO Waiting for DBservers to show up...
2017-01-23T16:16:23Z [22740] INFO Waiting for DBservers to show up...
2017-01-23T16:16:23Z [22740] INFO Found 1 DBservers.
2017-01-23T16:16:23Z [22740] INFO file-descriptors (nofiles) hard limit is 999999, soft limit is 999999
2017-01-23T16:16:23Z [22740] INFO created database directory '/data/data/arango/coordinator'.
2017-01-23T16:16:23Z [22740] INFO WAL directory '/data/data/arango/coordinator/journals' does not exist. creating it...
2017-01-23T16:16:23Z [22740] INFO JavaScript using startup '//usr/share/arangodb3/js', application '/var/lib/arangodb3-apps'
2017-01-23T16:16:26Z [22740] INFO Cluster feature is turned on. Agency version: {"server":"arango","version":"3.1.8","license":"community"}, Agency endpoints: http+tcp://osdi-03:25001, server id: 'Coordinator001', internal address: tcp://osdi-03:8530, role: COORDINATOR
2017-01-23T16:16:26Z [22740] INFO using heartbeat interval value '1000 ms' from agency
2017-01-23T16:16:26Z [22740] INFO In database '_system': No version information file found in database directory.
2017-01-23T16:16:26Z [22740] INFO In database '_system': Database is up-to-date (30108/cluster-local/init)
2017-01-23T16:16:27Z [22740] INFO using endpoint 'http+tcp://osdi-03:8530' for non-encrypted requests
2017-01-23T16:16:27Z [22740] INFO In database '_system': Found 14 defined task(s), 12 task(s) to run
2017-01-23T16:16:27Z [22740] INFO In database '_system': state coordinator-global/init, tasks setupGraphs, setupUsers, createUsersIndex, addDefaultUserSystem, createModules, createRouting, insertRedirectionsAll, setupAqlFunctions, createStatistics, createFrontend, setupQueues, setupJobs
2017-01-23T16:16:27Z [22740] WARNING {cluster} createCollectionCoordinator: replicationFactor is too large for the number of DBservers
2017-01-23T16:16:32Z [22740] WARNING {cluster} createCollectionCoordinator: replicationFactor is too large for the number of DBservers
2017-01-23T16:16:42Z [22740] ERROR In database '_system': Executing task #4 (addDefaultUserSystem: add default root user for system database) failed with exception: ArangoError 502: could not determine number of documents in collection (while optimizing plan) ArangoError: could not determine number of documents in collection (while optimizing plan)
2017-01-23T16:16:42Z [22740] ERROR     at Error (native)
2017-01-23T16:16:42Z [22740] ERROR     at ArangoStatement.execute (/usr/share/arangodb3/js/server/modules/@arangodb/arango-statement.js:81:16)
2017-01-23T16:16:42Z [22740] ERROR     at ArangoDatabase._query (/usr/share/arangodb3/js/server/modules/@arangodb/arango-database.js:79:45)
2017-01-23T16:16:42Z [22740] ERROR     at SimpleQueryByExample.execute (/usr/share/arangodb3/js/server/modules/@arangodb/simple-query.js:137:42)
2017-01-23T16:16:42Z [22740] ERROR     at SimpleQueryByExample.SimpleQuery.toArray (/usr/share/arangodb3/js/common/modules/@arangodb/simple-query-common.js:340:8)
2017-01-23T16:16:42Z [22740] ERROR     at ArangoCollection.firstExample (/usr/share/arangodb3/js/server/modules/@arangodb/arango-collection.js:287:71)
2017-01-23T16:16:42Z [22740] ERROR     at Object.exports.save (/usr/share/arangodb3/js/server/modules/@arangodb/users.js:135:22)
2017-01-23T16:16:42Z [22740] ERROR     at Object.addTask.task (/usr/share/arangodb3/js/server/upgrade-database.js:510:21)
2017-01-23T16:16:42Z [22740] ERROR     at runTasks (/usr/share/arangodb3/js/server/upgrade-database.js:274:27)
2017-01-23T16:16:42Z [22740] ERROR     at upgradeDatabase (/usr/share/arangodb3/js/server/upgrade-database.js:346:16)
2017-01-23T16:16:42Z [22740] ERROR In database '_system': Executing task #4 (addDefaultUserSystem: add default root user for system database) failed. Aborting init procedure.
2017-01-23T16:16:42Z [22740] ERROR In database '_system': Please fix the problem and try starting the server again.
2017-01-23T16:16:42Z [22740] ERROR upgrade-database.js for cluster script failed!
2017-01-23T16:16:42Z [22740] WARNING {cluster} createCollectionCoordinator: replicationFactor is too large for the number of DBservers
2017-01-23T16:16:52Z [22740] ERROR ArangoError: could not determine number of documents in collection (while optimizing plan)
2017-01-23T16:16:52Z [22740] ERROR     at Error (native)
2017-01-23T16:16:52Z [22740] ERROR     at ArangoStatement.execute (/usr/share/arangodb3/js/server/modules/@arangodb/arango-statement.js:81:16)
2017-01-23T16:16:52Z [22740] ERROR     at ArangoDatabase._query (/usr/share/arangodb3/js/server/modules/@arangodb/arango-database.js:79:45)
2017-01-23T16:16:52Z [22740] ERROR     at SimpleQueryAll.execute (/usr/share/arangodb3/js/server/modules/@arangodb/simple-query.js:96:42)
2017-01-23T16:16:52Z [22740] ERROR     at SimpleQueryAll.SimpleQuery.hasNext (/usr/share/arangodb3/js/common/modules/@arangodb/simple-query-common.js:388:8)
2017-01-23T16:16:52Z [22740] ERROR     at refillCaches (/usr/share/arangodb3/js/server/modules/@arangodb/foxx/manager.js:265:17)
2017-01-23T16:16:52Z [22740] ERROR     at Object.initializeFoxx (/usr/share/arangodb3/js/server/modules/@arangodb/foxx/manager.js:1483:3)
2017-01-23T16:16:52Z [22740] ERROR     at Object.foxxes (/usr/share/arangodb3/js/server/bootstrap/foxxes.js:64:47)
2017-01-23T16:16:52Z [22740] ERROR     at server/bootstrap/cluster-bootstrap.js:51:54
2017-01-23T16:16:52Z [22740] ERROR     at server/bootstrap/cluster-bootstrap.js:55:2
2017-01-23T16:16:52Z [22740] ERROR JavaScript exception in file<EMAIL_ADDRESS>at 108,7: TypeError: Cannot read property 'save' of undefined
2017-01-23T16:16:52Z [22740] ERROR !      throw err;
2017-01-23T16:16:52Z [22740] ERROR !      ^
2017-01-23T16:16:52Z [22740] FATAL error during execution of JavaScript file 'server/bootstrap/coordinator.js'

I rechecked using the 3.1.10 release in which we incorporated dozens of fixes related to cluster stability and everything went well. Can you recheck using this release?

Seems to be solved by 3.1.10 and beyond.

I'm seeing this exact same issue as @aznwarmonkey

2017-01-23T13:27:21Z [14669] ERROR JavaScript exception in file<EMAIL_ADDRESS>at 108,7: TypeError: Cannot read property 'save' of undefined
2017-01-23T13:27:21Z [14669] ERROR !      throw err;
2017-01-23T13:27:21Z [14669] ERROR !      ^
2017-01-23T13:27:21Z [14669] FATAL error during execution of JavaScript file 'server/bootstrap/coordinator.js'

The only two differences is I'm running arangodb, or trying to do so, in cluster on a kubernetes cluster. I've tried every version since 3.1.10 up to 3.1.14, and it always ends up not wanting to start the coordinators with that exact same error (I've cleaned all EBS storage between deployments of different versions).
I tried incresing the logging level, but it doesn't yield anything else to go on sadly.

i got same error when bootstrap coordinator.
2017-04-05T05:56:25Z [2592] INFO Cluster feature is turned on. Agency version: , Agency endpoints: http+tcp://<IP_ADDRESS>:5001, http+tcp://<IP_ADDRESS>:5001, http+tcp://<IP_ADDRESS>:5001, server id: 'Coordinator001', internal address: tcp://<IP_ADDRESS>:8529, role: COORDINATOR
2017-04-05T05:56:25Z [2592] INFO using heartbeat interval value '1000 ms' from agency
2017-04-05T05:56:25Z [2592] INFO changing state of COORDINATOR server from STARTUP to SERVING
2017-04-05T05:56:25Z [2592] INFO In database '_system': Database is up-to-date (30012/cluster-local/existing)
2017-04-05T05:56:26Z [2592] INFO using endpoint 'http+tcp://<IP_ADDRESS>:8529' for non-encrypted requests
2017-04-05T05:56:26Z [2592] INFO Authentication is turned off
2017-04-05T05:56:26Z [2592] ERROR JavaScript exception in file<EMAIL_ADDRESS>at 105,7: TypeError: Cannot read property 'save' of undefined
2017-04-05T05:56:26Z [2592] ERROR !      throw err;
2017-04-05T05:56:26Z [2592] ERROR !      ^
2017-04-05T05:56:26Z [2592] FATAL error during execution of JavaScript file 'server/bootstrap/coordinator.js'

this issue already solve btw ?

I got the same issue as well in v3.1.17. Been stuck at it for hours. Just cannot get the coordinator started.
2017-04-12T20:04:24Z [14884] INFO Found 2 DBservers.
2017-04-12T20:04:24Z [14884] INFO Authentication is turned on
2017-04-12T20:04:24Z [14884] INFO Authentication system only
2017-04-12T20:04:24Z [14884] INFO Authentication for unix sockets is turned on
2017-04-12T20:04:24Z [14884] INFO file-descriptors (nofiles) hard limit is 1048576, soft limit is 1048576
2017-04-12T20:04:24Z [14884] INFO JavaScript using startup '//usr/share/arangodb3/js', application '/var/lib/arangodb3-apps'
2017-04-12T20:04:24Z [14884] INFO Cluster feature is turned on. Agency version: {"server":"arango","version":"3.1.17","license":"community"}, Agency endpoints: http+tcp://<IP_ADDRESS>:8521, http+tcp://<IP_ADDRESS>:8521, http+tcp://<IP_ADDRESS>:8522, server id: 'CRDN-b9febea6-c8f4-4a0e-b94f-f94023371839', internal address: tcp://<IP_ADDRESS>:8530, role: COORDINATOR
2017-04-12T20:04:24Z [14884] INFO using heartbeat interval value '1000 ms' from agency
2017-04-12T20:04:24Z [14884] INFO using endpoint 'http+tcp://<IP_ADDRESS>:8530' for non-encrypted requests
2017-04-12T20:04:24Z [14884] ERROR JavaScript exception in file<EMAIL_ADDRESS>at 108,7: TypeError: Cannot read property 'save' of undefined
2017-04-12T20:04:24Z [14884] ERROR !      throw err;
2017-04-12T20:04:24Z [14884] ERROR !      ^
2017-04-12T20:04:24Z [14884] FATAL error during execution of JavaScript file 'server/bootstrap/coordinator.js'```

Obviously unsolved :face_with_head_bandage:

The error indicates that not all collections have been created. @mtanvir @idris-khanafi can you post an agency dump somewhere?
curl -L <IP_ADDRESS>:4001/_api/agency/read -d '[["/"]]' | jq .
replace <IP_ADDRESS>:4001 with you agency endpoint

Dump attached as text file. Thanks for looking into this. I'm running it on Oracle Linux 7.1 if that matters.
2283-agency-dump.txt

Same problem on 3.1.18

Yes. Tested again with 3.1.18 and same issue.

Duplicates #2027

I tried https://github.com/arangodb-helper/ArangoDBStarter. I can consistently reproduce on centos 7 with 3.1.19.
2017-05-02T23:41:32Z [21413] INFO ArangoDB 3.1.19 [linux] 64bit, using VPack 0.1.30, ICU 54.1, V8 <IP_ADDRESS>, OpenSSL 1.0.1e-fips 11 Feb 2013 2017-05-02T23:41:32Z [21413] INFO using SSL options: SSL_OP_CIPHER_SERVER_PREFERENCE, SSL_OP_TLS_ROLLBACK_BUG 2017-05-02T23:41:32Z [21413] INFO Starting up with role COORDINATOR 2017-05-02T23:41:32Z [21413] INFO {agency} ["arango/Target/MapLocalToID/tcp%3A%2F%2F<IP_ADDRESS>%3A9002"] 2017-05-02T23:41:32Z [21413] INFO Waiting for DBservers to show up... 2017-05-02T23:41:32Z [21413] INFO Found 3 DBservers. 2017-05-02T23:41:32Z [21413] INFO file-descriptors (nofiles) hard limit is 1048576, soft limit is 1048576 2017-05-02T23:41:32Z [21413] INFO JavaScript using startup '/usr/share/arangodb3/js', application '/fpdb/adb-cluster/coordinator9002/apps' 2017-05-02T23:41:32Z [21413] INFO Cluster feature is turned on. Agency version: {"server":"arango","version":"3.1.19","license":"community"}, Agency endpoints: http+tcp://<IP_ADDRESS>:9001, http+tcp://<IP_ADDRESS>:9001, http+tcp://<IP_ADDRESS>:9006, server id: 'CRDN-dba72cab-95da-480b-b74f-6da10072f071', internal address: tcp://<IP_ADDRESS>:9002, role: COORDINATOR 2017-05-02T23:41:32Z [21413] INFO using heartbeat interval value '1000 ms' from agency 2017-05-02T23:41:32Z [21413] INFO using endpoint 'http+tcp://[::]:9002' for non-encrypted requests 2017-05-02T23:41:32Z [21413] ERROR JavaScript exception in file<EMAIL_ADDRESS>at 108,7: TypeError: Cannot read property 'save' of undefined 2017-05-02T23:41:32Z [21413] ERROR !      throw err; 2017-05-02T23:41:32Z [21413] ERROR !      ^ 2017-05-02T23:41:32Z [21413] FATAL error during execution of JavaScript file 'server/bootstrap/coordinator.js'

I am sorry but I simply cannot reproduce this. I need more input on your environment. Can you please specify more details on your environment? Also please provide ALL logs you can find. Are you memory limited? is this docker? are you using a VM?
I just tried it using a centos7 docker container (centos7 was the only thing I could see here):
Agency:
[root@d971f2515bb8 ~]# arangod --server.uid 0 --server.gid 0 --agency.activate true --agency.size 1 --server.endpoint tcp://<IP_ADDRESS>:4001 --server.authentication false --database.directory agency --agency.supervision true
2017-05-03T17:44:48Z [418] INFO ArangoDB 3.1.19 [linux] 64bit, using VPack 0.1.30, ICU 54.1, V8 <IP_ADDRESS>, OpenSSL 1.0.1e-fips 11 Feb 2013
2017-05-03T17:44:48Z [418] INFO using SSL options: SSL_OP_CIPHER_SERVER_PREFERENCE, SSL_OP_TLS_ROLLBACK_BUG
2017-05-03T17:44:48Z [418] INFO Starting up with role AGENT
2017-05-03T17:44:48Z [418] INFO file-descriptors (nofiles) hard limit is 1048576, soft limit is 1048576
2017-05-03T17:44:48Z [418] INFO created database directory 'agency'.
2017-05-03T17:44:48Z [418] INFO WAL directory 'agency/journals' does not exist. creating it...
2017-05-03T17:44:48Z [418] INFO JavaScript using startup '//usr/share/arangodb3/js', application '/var/lib/arangodb3-apps'
2017-05-03T17:44:50Z [418] INFO using endpoint 'http+tcp://<IP_ADDRESS>:4001' for non-encrypted requests
2017-05-03T17:44:51Z [418] INFO ArangoDB (version 3.1.19 [linux]) is ready for business. Have fun!

Coordinator:
[root@d971f2515bb8 /]# arangod --server.uid 0 --server.gid 0 --server.endpoint tcp://<IP_ADDRESS>:8530 --server.authentication false --database.directory coordinator1 --cluster.agency-endpoint tcp://<IP_ADDRESS>:4001 --cluster.my-role COORDINATOR --cluster.my-address tcp://<IP_ADDRESS>:8530
2017-05-03T17:44:55Z [480] INFO ArangoDB 3.1.19 [linux] 64bit, using VPack 0.1.30, ICU 54.1, V8 <IP_ADDRESS>, OpenSSL 1.0.1e-fips 11 Feb 2013
2017-05-03T17:44:55Z [480] INFO using SSL options: SSL_OP_CIPHER_SERVER_PREFERENCE, SSL_OP_TLS_ROLLBACK_BUG
2017-05-03T17:44:55Z [480] INFO Starting up with role COORDINATOR
2017-05-03T17:44:55Z [480] INFO {agency} ["arango/Target/MapLocalToID/bogus_hass_hund"]
2017-05-03T17:44:55Z [480] INFO Waiting for DBservers to show up...
2017-05-03T17:44:56Z [480] INFO Waiting for DBservers to show up...
2017-05-03T17:44:57Z [480] INFO Waiting for DBservers to show up...
2017-05-03T17:44:58Z [480] INFO Waiting for DBservers to show up...
2017-05-03T17:44:59Z [480] INFO Waiting for DBservers to show up...
2017-05-03T17:45:00Z [480] INFO Waiting for DBservers to show up...
2017-05-03T17:45:01Z [480] INFO Waiting for DBservers to show up...
2017-05-03T17:45:01Z [480] INFO Found 2 DBservers.
2017-05-03T17:45:01Z [480] INFO file-descriptors (nofiles) hard limit is 1048576, soft limit is 1048576
2017-05-03T17:45:01Z [480] INFO WAL directory '/coordinator1/journals' does not exist. creating it...
2017-05-03T17:45:01Z [480] INFO JavaScript using startup '/usr/share/arangodb3/js', application '/var/lib/arangodb3-apps'
2017-05-03T17:45:02Z [480] INFO Cluster feature is turned on. Agency version: {"server":"arango","version":"3.1.19","license":"community"}, Agency endpoints: http+tcp://<IP_ADDRESS>:4001, server id: 'CRDN-1392179f-de18-4567-af23-3d37fe6c923a', internal address: tcp://<IP_ADDRESS>:8530, role: COORDINATOR
2017-05-03T17:45:02Z [480] INFO using heartbeat interval value '1000 ms' from agency
2017-05-03T17:45:02Z [480] INFO using endpoint 'http+tcp://<IP_ADDRESS>:8530' for non-encrypted requests
2017-05-03T17:45:05Z [480] INFO Waiting for initial replication of system collections...
2017-05-03T17:45:17Z [480] INFO bootstrapped coordinator CRDN-1392179f-de18-4567-af23-3d37fe6c923a
2017-05-03T17:45:17Z [480] INFO ArangoDB (version 3.1.19 [linux]) is ready for business. Have fun!

DBServer1:
[root@d971f2515bb8 /]# arangod --server.uid 0 --server.gid 0 --server.endpoint tcp://<IP_ADDRESS>:8629 --server.authentication false --cluster.agency-endpoint tcp://<IP_ADDRESS>:4001 --database.directory dbserver1 --cluster.my-role PRIMARY --cluster.my-address tcp://<IP_ADDRESS>:8629
2017-05-03T17:44:57Z [484] INFO ArangoDB 3.1.19 [linux] 64bit, using VPack 0.1.30, ICU 54.1, V8 <IP_ADDRESS>, OpenSSL 1.0.1e-fips 11 Feb 2013
2017-05-03T17:44:57Z [484] INFO using SSL options: SSL_OP_CIPHER_SERVER_PREFERENCE, SSL_OP_TLS_ROLLBACK_BUG
2017-05-03T17:44:57Z [484] INFO Starting up with role PRIMARY
2017-05-03T17:44:57Z [484] INFO {agency} ["arango/Target/MapLocalToID/bogus_hass_hund"]
2017-05-03T17:44:58Z [484] INFO file-descriptors (nofiles) hard limit is 1048576, soft limit is 1048576
2017-05-03T17:44:58Z [484] INFO WAL directory '/dbserver1/journals' does not exist. creating it...
2017-05-03T17:44:58Z [484] INFO JavaScript using startup '/usr/share/arangodb3/js', application '/var/lib/arangodb3-apps'
2017-05-03T17:44:58Z [484] INFO Cluster feature is turned on. Agency version: {"server":"arango","version":"3.1.19","license":"community"}, Agency endpoints: http+tcp://<IP_ADDRESS>:4001, server id: 'PRMR-aba721b7-880c-44b1-bf36-63a8c9d90fb1', internal address: tcp://<IP_ADDRESS>:8629, role: PRIMARY
2017-05-03T17:44:58Z [484] INFO using heartbeat interval value '1000 ms' from agency
2017-05-03T17:44:59Z [484] INFO using endpoint 'http+tcp://<IP_ADDRESS>:8629' for non-encrypted requests
2017-05-03T17:44:59Z [484] INFO bootstrapped DB server PRMR-aba721b7-880c-44b1-bf36-63a8c9d90fb1
2017-05-03T17:44:59Z [484] INFO ArangoDB (version 3.1.19 [linux]) is ready for business. Have fun!

DBServer2:
[root@d971f2515bb8 /]# arangod --server.uid 0 --server.gid 0 --server.endpoint tcp://<IP_ADDRESS>:8630 --server.authentication false --cluster.agency-endpoint tcp://<IP_ADDRESS>:4001 --database.directory dbserver2 --cluster.my-role PRIMARY --cluster.my-address tcp://<IP_ADDRESS>:8630
2017-05-03T17:45:00Z [543] INFO ArangoDB 3.1.19 [linux] 64bit, using VPack 0.1.30, ICU 54.1, V8 <IP_ADDRESS>, OpenSSL 1.0.1e-fips 11 Feb 2013
2017-05-03T17:45:00Z [543] INFO using SSL options: SSL_OP_CIPHER_SERVER_PREFERENCE, SSL_OP_TLS_ROLLBACK_BUG
2017-05-03T17:45:00Z [543] INFO Starting up with role PRIMARY
2017-05-03T17:45:00Z [543] INFO {agency} ["arango/Target/MapLocalToID/bogus_hass_hund"]
2017-05-03T17:45:00Z [543] INFO {cluster} Fresh start. Persisting new UUID PRMR-9d09181b-8ce2-4410-91bd-97845732e3d3
2017-05-03T17:45:00Z [543] INFO file-descriptors (nofiles) hard limit is 1048576, soft limit is 1048576
2017-05-03T17:45:00Z [543] INFO WAL directory 'dbserver2/journals' does not exist. creating it...
2017-05-03T17:45:00Z [543] INFO JavaScript using startup '/usr/share/arangodb3/js', application '/var/lib/arangodb3-apps'
2017-05-03T17:45:01Z [543] INFO Cluster feature is turned on. Agency version: {"server":"arango","version":"3.1.19","license":"community"}, Agency endpoints: http+tcp://<IP_ADDRESS>:4001, server id: 'PRMR-9d09181b-8ce2-4410-91bd-97845732e3d3', internal address: tcp://<IP_ADDRESS>:8630, role: PRIMARY
2017-05-03T17:45:01Z [543] INFO using heartbeat interval value '1000 ms' from agency
2017-05-03T17:45:01Z [543] INFO using endpoint 'http+tcp://<IP_ADDRESS>:8630' for non-encrypted requests
2017-05-03T17:45:01Z [543] INFO bootstrapped DB server PRMR-9d09181b-8ce2-4410-91bd-97845732e3d3
2017-05-03T17:45:01Z [543] INFO ArangoDB (version 3.1.19 [linux]) is ready for business. Have fun!
2017-05-03T17:45:02Z [543] INFO {replication} connected to master at tcp://<IP_ADDRESS>:8629, id<PHONE_NUMBER>580, version 3.1, last log tick 2010012
2017-05-03T17:45:03Z [543] INFO {replication} connected to master at tcp://<IP_ADDRESS>:8629, id<PHONE_NUMBER>580, version 3.1, last log tick 2010237
2017-05-03T17:45:05Z [543] INFO {replication} connected to master at tcp://<IP_ADDRESS>:8629, id<PHONE_NUMBER>580, version 3.1, last log tick 2010749
2017-05-03T17:45:05Z [543] INFO {replication} connected to master at tcp://<IP_ADDRESS>:8629, id<PHONE_NUMBER>580, version 3.1, last log tick 2011194
2017-05-03T17:45:07Z [543] INFO {replication} connected to master at tcp://<IP_ADDRESS>:8629, id<PHONE_NUMBER>580, version 3.1, last log tick 2011242
2017-05-03T17:45:08Z [543] INFO {replication} connected to master at tcp://<IP_ADDRESS>:8629, id<PHONE_NUMBER>580, version 3.1, last log tick 2011337
2017-05-03T17:45:09Z [543] INFO {replication} connected to master at tcp://<IP_ADDRESS>:8629, id<PHONE_NUMBER>580, version 3.1, last log tick 2011426
2017-05-03T17:45:11Z [543] INFO {replication} connected to master at tcp://<IP_ADDRESS>:8629, id<PHONE_NUMBER>580, version 3.1, last log tick 2011611
2017-05-03T17:45:12Z [543] INFO {replication} connected to master at tcp://<IP_ADDRESS>:8629, id<PHONE_NUMBER>580, version 3.1, last log tick 2011709
2017-05-03T17:45:13Z [543] INFO {replication} connected to master at tcp://<IP_ADDRESS>:8629, id<PHONE_NUMBER>580, version 3.1, last log tick 2011716
2017-05-03T17:45:14Z [543] INFO {replication} connected to master at tcp://<IP_ADDRESS>:8629, id<PHONE_NUMBER>580, version 3.1, last log tick 2011808
2017-05-03T17:45:15Z [543] INFO {replication} connected to master at tcp://<IP_ADDRESS>:8629, id<PHONE_NUMBER>580, version 3.1, last log tick 2011899

It just works. Also we are using DC/OS on CentOS (vms) internally so that works as well. I need more input and hopefully some common environment stuff that you all @mtanvir @khamin @idris-khanafi are using. It must be some subtle thing.

Hi, many thanks for looking into this again. My environment is as below. I meant to say Oracle Linux 7. Apologies I mistyped late night and all that.
Oracle Linux 7.1 running in OpenStack VM.
No Docker.
Installed Arangodb using yum.
Previously tried to do fiddly manual process Cluster setup but now using Arangodb Starter which is much better.
I'll set verbose flag or Log level to trace and record the logs tonight.

@m0ppers
I'm trying to achieve master/master config with 2 VMs. I understand that 3 agencies are needed to form the cluster, and while one node can run 2 agencies, failure of that node will bring down the cluster.
I start the cluster using ArangodbStarter as below
On Host 1:
arangodb --masterPort 9000 --ownAddress <IP_ADDRESS> --verbose true

On Host 2:
arangodb --dataDir=./db2 --join <IP_ADDRESS> --masterPort 9000 --ownAddress <IP_ADDRESS> --verbose true

On Host 2 again:
arangodb --dataDir=./db --join <IP_ADDRESS> --masterPort 9000 --ownAddress <IP_ADDRESS> --verbose true

All agencies startup as normal, db servers comes online too but coordinator consistently fails to start on all hosts. Same error as in the issue. I have attached the attached the db directories generated by ArangoDB Starter. Logs for agencies, db servers and coordinator for all nodes are inside. Only change I made to generated config today is to set log level to TRACE.
adb-cluster.zip
Hope this helps,
Thanks

@m0ppers
OS: Ubuntu 17.04
ArangoDB: nightly 3.2.devel.20170502
Cluster: 3 x (agency, dbserver, coordinator) using bundled arangodb tool (<IP_ADDRESS> is master)
Configuration: 3 x bare metal servers (no vm, no docker, no memory limit)
More info: issue2283.zip
Hope this helps,
Thanks

Are you passing any arguments to arangodb?

System.d service files are packed into archive I've attached above.

I made a quick test locally using ubuntu 17.04 in vms using your systemd files. It just works :( (I don't have any spare bare metal servers here but I think vm should be ok).
Is there maybe some network issue (or a firewall?) installed in between the servers? There is not a single combination in our tests which reveals any errors like that :S

How can I help diagnose this? This is the last hindrance in our adoption. I'll really appreciate any help. I've tried with Docker on the same VMs and it works just fine. So that rules out any network issues. Sadly Docker is not an option in production environment for us. Clearly its impacting couple of other users as well so there is an issue in coordinator. Is OL 7 which is Cent OS 7 based, not a supported platform?

If we would have access to such a machine and might be able to deploy a specially crafted version with some more debug hints I am sure we would be able to sort this out.
You are right that Oracle Linux is not supported. We do support Cent OS though. However I don't see why this issue should be distribution related and as @khamin reported he had the same errors on ubuntu (which we do support).
Right now we are putting every effort into getting a 3.2 beta out but after that we will surely be able to look at this issue provided one of you can give us access to such a failing machine.

These are rather large vms with 8 core x 64GB RAM so I won't have them for very long just for testing. Once I return to work, I'll try to get the VM images archived and runnable with VirtualBox. You can revisit at later date when convenient.

I think i can provide reproducible vagrant/virtualbox environment.
@m0ppers is that applicable for you?

Same problem in 3.1.20 if anyone cares.

We care. But we are desperate for recreating the issue here. Anyone out there with this problem. Could any of you please do the following:
Edit /usr/share/arangodb3/js/server/upgrade-database.js with the editor of your choice.
Navigate to line 511 insert the following line here:
console.error('This is the place ***************************************************');
Edit<EMAIL_ADDRESS>Navigate to line 137 and insert these to lines there:
console.error(query);
console.error(bindVars);
startup the cluster the way it did fail.
That would be so greatly appreciated. We tried and tried and just couldn't reproduce the problem, which is obviously happening to some you.

@kvahed Would it help if you use the VM images that @khamin offered?

sure. but we haven't gotten them yet.

I made the changes on each nodes as you suggested. Attached are full db directories with logs and generated config etc. I couldn't see new debug messages in there though. As there was 3.1.21 release available in yum repo, I tested with that. Same result.
adb-cluster-3.1.21.zip

Thx a lot. I appreciate it.
And we are not a single step further. If any of you folks could envision us having access to the box, were this happens. We'd send you a public ssh key. I'd toss in some t-shirts 🥇. Does anybody sense the level of desperation here?

@kvahed I've set up an webex invite for you to come and poke around these VMs. Details in your email & ArangoDB slack channel.

@mtanvir perfect

@mtanvir was kind enough to provide a webex that allowed us to look around on the cluster and the issue we found was trivial as well as embarassing:
Under the hood we are using cURL for HTTP communication and apparently we didn't dig into all the settings of curl. On @mtanvir 's  machines a HTTP proxy is configured and the way we are communicating seems to break proxied communication.
This showed multiple issues in arangodb:

error handling. the proxy was returning HTML. The error handling/messages MUST be improved so that we don't dig in the dark like this
we have to think about how (and if?) we are working with proxies. My initial thought would be to disable proxies for curl completely. Please yell very loudly if you think you will need cluster internal (!) communication through a proxy.

We will discuss proper solutions for the upcoming 3.2 release.
In the meantime please remove any proxy environment variables that curl is using before starting your arangodb clusters like so:
https://askubuntu.com/questions/251003/how-to-permanently-disable-http-proxy
Please note that the environment variable is case sensitive so it MUST be lowercase.
@khamin can you verify that this is the same problem you are facing?

Thank you for detailed explanation and work around. Also another work around is to user Docker if possible. Host machine proxies setting doesn't bleed into containers by default so you'll be shielded from this bug.
I vote for proxy support going forward though. In most corporate environments, firewall and proxies are just given. Nothing works without them. Here I had full control over the VMs in test environment so I was able to disable the proxies. Although in production, sysadmins won't allow this. Installing patches and packages from centos repo & internet connectivity from the boxes will be broken without proxy settings.

Do you mean that you need proxy support to even communicate within the same internal network of the cluster (like <IP_ADDRESS> to <IP_ADDRESS>?). How would you implement a different clustered database on such a network which is not using HTTP but a non-proxyable proprietary protocol? also this of course would have severe performance implications. Is this really necessary?
My initial thought would be that cluster internal communication should simply ignore any proxy settings. Of course stuff like foxx which might be pulling foxx packages from github for example must be capable of supporting proxies (which is does not right now I think).

No that's not what I meant. As long as next release doesn't require unsetting the proxies for the cluster to work, I'm happy. And yes Foxx packages from Github doesn't work in my environment behind proxy. Doesn't bother me as it's not critical for my use.

@m0ppers we do not use any kind of http proxy.
Seems that my case is bad value of net.ipv4.tcp_tw_recycle which causes random tcp handshake issues.
I think it would be useful to log warn if value != 0 (just like nofile warn).

Just to double check @khamin : You didn't enable the recycle at any point because arangodb forced you to do so (could indicate for example that persistent connections could be broken or something like that). The flag was enabled because of a simple non-arangodb related misconfiguration?
Logging a warning is actually a very good idea. Will implement that now (for 3.2). Fix for the proxy problem is also coming along very soon :)

Yeah, it was unrelated to arangodb misconfiguration.

ArangoDB Version 3.1.22 containing this fix is available for download - closing.
Thanks for bearing with us and helping us to resolve this issue.

I have upgrade to 3.1.25, but still have such issue
[root@gp2 coordinator]# 2017-07-17T03:16:47Z [26314] INFO ArangoDB 3.1.25 [linux] 64bit, using VPack 0.1.30, ICU 54.1, V8 <IP_ADDRESS>, OpenSSL 1.0.1e-fips 11 Feb 2013 2017-07-17T03:16:47Z [26314] INFO using SSL options: SSL_OP_CIPHER_SERVER_PREFERENCE, SSL_OP_TLS_ROLLBACK_BUG 2017-07-17T03:16:47Z [26314] INFO Starting up with role COORDINATOR 2017-07-17T03:16:47Z [26314] INFO {agency} ["arango/Target/MapLocalToID/coord2"] 2017-07-17T03:16:47Z [26314] INFO Waiting for DBservers to show up... 2017-07-17T03:16:47Z [26314] INFO Found 2 DBservers. 2017-07-17T03:16:47Z [26314] INFO file-descriptors (nofiles) hard limit is 262144, soft limit is 65536 2017-07-17T03:16:47Z [26314] INFO JavaScript using startup '//usr/share/arangodb3/js', application '/var/lib/arangodb3-apps' 2017-07-17T03:16:48Z [26314] INFO Cluster feature is turned on. Agency version: {"server":"arango","version":"3.1.25","license":"community"}, Agency endpoints: http+tcp://<IP_ADDRESS>:5001, http+tcp://<IP_ADDRESS>:5001, http+tcp://<IP_ADDRESS>:5001, server id: 'CRDN-0580770a-48d3-4e08-b7ff-d5fe667e31f0', internal address: tcp://<IP_ADDRESS>:8532, role: COORDINATOR 2017-07-17T03:16:48Z [26314] INFO using heartbeat interval value '1000 ms' from agency 2017-07-17T03:16:48Z [26314] INFO using endpoint 'http+tcp://<IP_ADDRESS>:8532' for non-encrypted requests 2017-07-17T03:16:48Z [26314] ERROR JavaScript exception in file<EMAIL_ADDRESS>at 108,7: TypeError: Cannot read property 'save' of undefined 2017-07-17T03:16:48Z [26314] ERROR !      throw err; 2017-07-17T03:16:48Z [26314] ERROR !      ^ 2017-07-17T03:16:48Z [26314] FATAL error during execution of JavaScript file 'server/bootstrap/coordinator.js' ^C [root@gp2 coordinator]# env | grep proxy [root@gp2 coordinator]#

@zlfsimon is that happening everytime at startup?

@fceller  we install three nodes by rmp package.
rpm -ivh arangodb-3.1.25-1.x86_64.rpm
no error at startup.
In fact, we have such error  when use v3.1.21, after reading this post we decide to upgrade to new version 3.1.25, test but still have this error.
we just upgrade arangodb self, and reuse the data file, below are parts of running commands:
nohup arangod --server.endpoint tcp://<IP_ADDRESS>:5001 --agency.my-address tcp://<IP_ADDRESS>:5001 --server.authentication false --agency.activate true --agency.size 3 --agency.supervision true --database.directory /gp/data/arangodb/agency &

nohup arangod --server.authentication=false --server.endpoint tcp://<IP_ADDRESS>:8530 --cluster.my-address tcp://<IP_ADDRESS>:8530 --cluster.my-local-info db2 --cluster.my-role PRIMARY --cluster.agency-endpoint tcp://<IP_ADDRESS>:5001 --cluster.agency-endpoint tcp://<IP_ADDRESS>:5001 --cluster.agency-endpoint tcp://<IP_ADDRESS>:5001 --database.directory /gp/data/arangodb/primary2 &

nohup arangod --server.authentication=false --server.endpoint tcp://<IP_ADDRESS>:8531 --cluster.my-address tcp://<IP_ADDRESS>:8531 --cluster.my-local-info coord2 --cluster.my-role COORDINATOR --cluster.agency-endpoint tcp://<IP_ADDRESS>:5001 --cluster.agency-endpoint tcp://<IP_ADDRESS>:5001 --cluster.agency-endpoint tcp://<IP_ADDRESS>:5001 --database.directory /gp/data/arangodb/coordinator &

@fceller  we try to run in  standalone mode, it works, but error in a cluster mode

anyone can give some suggestion?

anyone can give some suggestion?

--cluster.system-replication-factor dafault value is 2. Decrease this value to 1 if only one data server in cluster


Historical Data Entry | Government Analyst can complete a transaction using the Historical Data Entry feature |2|

https://trello.com/c/MDt5FmpZ/768-historical-data-entry-government-analyst-can-complete-a-transaction-using-the-historical-data-entry-feature-2#
Issue:
An IDIR user assigned the Government Analyst role receives an error message when trying to add a transaction to the queue within the Historical Data Entry feature (see attached screenshot).
Resolution:
Allow the Government Analyst role to be able to fully use the Historical Data Entry feature, including adding transactions to the queue and committing them.
Note: Granting the Gov't Analyst role permission to use the Historical Data Entry feature should be kept separate from the ability to approve credit transactions within TFRS (Credit Transfer Proposals & PVRs). Meaning, a Gov't Analyst should be able to use the Historical Data Entry tool to commit transactions but they should not be able to approve "normal" transactions within TFRS (e.g. Credit Transfer Proposals and PVRs).

 Historical Data Entry | Government Analyst can complete a transaction using the Historical Data Entry feature |2|


k8s could not pull openpai/cleaner images

k8s seems to pull cleaner:v0.8.0. actually there has no tag named v0.8.0

Cleaner is disabled now, so PAI won't publish cleaner image. Could you please use our release branch instead of master since it's more stable. Our latest release version is v0.8.2


[gatsby-plugin-now] Remove temporary

Remove gatsby-plugin-now temporarily.

@styfle only temporary, since it is not needed at the moment and won't be for a while

@AndyBitz My understanding is that this plugin is currently injected into all gatsby deployments so removing it would be a breaking change (which is why you had to remove the @now/static-build tests).
Adding @lucleray to review this PR too.

As we've ascertained on the call, it's not being invoked.


New Bug Report Template based on YAML

Why are the changes needed?

See https://gh-community.github.io/issue-template-feedback/structured/
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Codecov Report

Merging #1036 (a10522d) into master (057bac1) will increase coverage by 0.01%.
 Consider uploading reports for the commit e3094ce to get more accurate results

@@             Coverage Diff              @@
##             master    #1036      +/-   ##
============================================
+ Coverage     80.65%   80.67%   +0.01%
  Complexity       14       14
============================================
  Files           159      159
  Lines          5837     5837
  Branches        657      657
============================================
+ Hits           4708     4709       +1
  Misses          734      734
+ Partials        395      394       -1

Impacted Files
Coverage Δ

...pache/kyuubi/sql/KyuubiQueryStagePreparation.scala
80.39% <0.00%> (+0.98%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 057bac1...e3094ce. Read the comment docs.

thanks, merging to master


fix(hiccup-svg): fix #142, add missing exports (ellipse, image)

Hope this helps!

Thank you for this @arcticnoah! :) Welcome to the club!


Allow selecting authentication type of the traffic

Looking forward to having 100% predictable tests

Testing your own 3scale products should allow 100%predictable traffic


[master] Update GitHub Actions

Copied from https://github.com/knative-sandbox/.github/tree/master/workflow-templates.
/assign n3wscott shashwathi tanzeeb
/cc n3wscott shashwathi tanzeeb

first
/lgtm


Stub out parent class ('ExpressBridge')

Pre, Post handlers.
processEvent method to kick off handling of incoming event, kicking off matcher, and invoking handlers.

Addressed in #33


feat: French translation

Built and launched a local version.
Seems to work okay except some texts that were not in src\_data\sites\en.yml, so they remain in English.

Thanks! It looks like there are a couple of commits that maybe @Brack0 worked on? Those commits aren't properly tied to a GitHub ID, which is why the CLA check is failing. @Brack0 can you update those commits and sign the CLA?

@darahak it looks like we are stuck on those missing commits. Would you be able to remove them and resubmit?

@nzakas I'll have a look this weekend.

@nzakas I amended the faulty commits with the right user ID, but it's still failing.
@Brack0 Did you sign the CLA?

@Brack0 Did you sign the CLA?

Yep, should be good now.

Thanks! Everything looks good, so I'll merge this and we can handle updates in separate PRs as necessary.

@Brack0 can you send us an email at contact (at) eslint (dot) org so we can pay you for this contribution? :)
(I already have @darahak's email address)
Thanks!


Hints displaying over tooltip

The problem here is that document.elementFromPoint doesn't return the tooltip but what's behind it.

The problem here is that the popup has pointer-events: none, what makes that when we call elementFromPoint in elementIsObscured we don't get the popup element as per the specification.
A possible solution could be to keep track of every element with pointer-events: none and then in elementIsObscured set pointer-events: auto for each of those elements and then reset them. The problem in this specific case is that the popup is wrapped in an overlay modal so then every element becomes obscured, and we get no hints. A possible solution for this is using z-index, which is also complicated because we have to calculate the z-index not only of the target element but also every element that's behind the hint. Calculating the z-index of an element is also not trivial because we have to take into account stacking contexts and whatnot. But I think eventually we'll have to go for this solution as I think it will be a more sturdy solution than our current implementation.


Components to use microphone / camera

Is your feature request related to a problem? Please describe
With some fantastic new components like text and image annotators enabling seamless data science workflows, it would be cool to take it one step further by using microphones and cameras.
Describe the solution you'd like
Components that can capture audio or video using available microphone / camera device from directly inside an app and make the audio / video files available for the app for processing / inferencing.
Additional context
This would greatly benefit some of the deep learning apps on audio/video projects, especially Automatic Speech Recognition, Speech-To-Text, Face/Gesture Recognition, Video Inferencing, etc.
cc: @leecming82

Possible with some JS using: https://medium.com/@unusualcode/record-audio-in-h2o-wave-apps-fcd6c0b05e59
Thanks @mturoci !


[FLINK-8837] [DataStream API] add @Experimental annotation and properly annotate some classes

What is the purpose of the change

add @Experimental annotation
properly annotate some classes with @Experimental

Brief change log

add @Experimental annotation
properly annotate some classes with @Experimental

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

The public API, i.e., is any changed class annotated with @Public(Evolving): (yes)

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? (JavaDocs)

cc @StephanEwen @tillrohrmann @zentol

merging.


ModuleNotFoundError: No module named 'openai'

Thanks for your work.
Steps I took,

Cloned the repo
Used the example/main_prompt and filled with instructions
Ran pip install -r requirements.txt
I'm using python3 so ran python3 main.py example
and go this error

Traceback (most recent call last):
  File "/Users//Documents//gpt-engineer/./main.py", line 5, in <module>
    import openai
ModuleNotFoundError: No module named 'openai'

Not a py coder, what could I be doing wrong?

I think your default pip is not attached to your default python
pip3 install ... might work
Or:
python3 -m pip install ...


[Fix #3191] Allow arbitrary comments after cop names in CommentConfig lines

Allow arbitrary comments after cop names
e.g.
# rubocop:disable SomeCop this is why it's disabled

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[x] Used the same coding conventions as the rest of the project.
[x] Feature branch is up-to-date with master (if not - rebase it)
[x] Squashed related commits together.
[x] Added tests.
[x] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] All tests are passing.
[x] The new code doesn't generate RuboCop offenses.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.

:+1: Makes sense. Code looks good.

❤ thx!


Expose NewEventFromException

Currently there appears to be no way to reuse logic in Client.eventFromException and then modify the event to add addition information (e.g. user info, etc).
This change exposes this logic as a new NewEventFromException function.

At the moment the proposed patch breaks the existing tests.

modify the event to add addition information (e.g. user info, etc).

Would you mind explaining the problem at hand? What are you trying to achieve and why?
Have you considered using BeforeSend?

Have you considered using BeforeSend?

Yes, it would have worked if it wasn't global to the Sentry client.

Would you mind explaining the problem at hand? What are you trying to achieve and why?

The problem is that I want to attach a user ID, but this ID depends on the request data, and it's not global as BeforeSend assumes.

At the moment the proposed patch breaks the existing tests.

Indeed, but I haven't figured out why that internal method name is not filtered from the stack trace.
And I cannot change the stack trace depth, because that exposed function will be used by both client and SDK code. I can refactor the function to accept a stack depth parameter, but maybe there is a better way?

The problem is that I want to attach a user ID

This can be done by using Scope, see https://docs.sentry.io/enriching-error-data/scopes/?platform=go.
I've sent a PR to https://github.com/athenianco/metadata/pull/92/ showing how to do it without copying SDK internals and without exposing new APIs.

Since the use case (attach user info to events) is already supported by the SDK via a more general method (Scopes), we'll not export a new symbol.
@dennwc feel free to open a new issue if there's something the SDK cannot do. In general, it is desirable to discuss a problem in an issue before sending a code change, as it might turn out that some design discussion needs to take place, or we may simply find out that something is already possible with the current API.
Thank you for using Sentry and helping making it better!


Feature flag/toggle UX design

A user can turn on or off the ability to see experimental features in OSIO.
Stage 1:
Experimental features on/off
Stage 2:
Allow user to turn on or off certain experimental features

https://martinfowler.com/articles/feature-toggles.html

We have an Epic for this at https://github.com/openshiftio/openshift.io/issues/278

Initial work happening in this fabric8-ux story:  https://github.com/fabric8-ui/fabric8-ux/issues/510
You can see user flows and some design ideas forming here:  https://redhat.invisionapp.com/share/WJCDBEBYM

@joshuawilson - main question I have for Dev team - if you look at user flows I have a Phase 1, 2, 3.  Do those phases make sense to you?  Are Phase 1 and 2 useful distinctions especially to get this done in a more timely fashion?  Reviewed with @qodfathr and he was happy with the direction of these user flows.  Designs still need more work.

@catrobson the designs look like what I thought it should be. How would the Phases work?
Long term we may want to be more specific and have a whole page in the profile to check off the areas that you want enable and maybe the features/phases for them.

Stage 1 has been completed.  Will create stories for stage 2 separately.


App Crashes when Home Button is pressed

When i used UITableViewController in UINavigationStack, it worked fine in foreground. But loading a UITableViewController and then unLoad UITableViewController. Now pressing iPhone Home Button crashed the application with this error:
[UITableViewController applicationWillSuspend]: message sent to deallocated instance.
Now, tell me what to do with this?

Thanks a lot.

Hello My Other Views have fixed the crash after doing this dealloc replacement but there in uncertain crash now at this giving EXCESS BAD ACCESS
if ([self.delegate respondsToSelector:@selector(heightForAirMenuRow)]) {

Class : PHAirViewController.m in reloadData function

You should open a new issue. Alternatively there are newer pods for
achieving this menu these days, i'd consider looking for others.
On Wed, Jul 15, 2015 at 10:42 PM, Rappier<EMAIL_ADDRESS>wrote:

Hello My Other Views have fixed the crash after doing this dealloc
replacement but there in uncertain crash now at this giving EXCESS BAD
ACCESS
if ([self.delegate respondsToSelector:@selector(heightForAirMenuRow)]) {
Class : PHAirViewController.m in reloadData function
—
Reply to this email directly or view it on GitHub
https://github.com/TaPhuocHai/PHAirViewController/issues/13#issuecomment-121604033
.


Search Term is empty when I go to next page

Hello,
when I search for something and I will get multiple result pages my search term will be empty after going to page 2.
Example: I search for order where first_name is "max". Everything is right. When I go to page 2 of the results I will get all orders and not only orders where first_name is max.
My Code:
 $term = $request->query('term'); // i.e Max

    $orders = Search::add(Order::orderBy('created_at', 'desc'), ['invoice_number', 'first_name', 'last_name', 'street', 'additional_address', 'city', 'state', 'house_number', 'zip_code'])
        ->beginWithWildcard()
        ->paginate(10)
        ->get($term);

You need to use the withQueryString method: https://laravel.com/docs/8.x/pagination#appending-query-string-values

I work with laravel since a few years now but never noticed this function 😅
May you add this to the documentation please?


Single camera Tracking not working with Kinect v1

Operating system: Ubuntu 16.04 LTS
Depth Sensor: Microsoft Kinect v1
Installed using the Doc mentioned in Readme file.
Command run: roslaunch tracking single_camera_tracking_node.launch
I am not getting any camera view as attached below.
It seems as if my Kinect v1 isn't detected, but libfreenect works fine.

Kinect1 support deprecated.


Remove .validation for manifests\r\rammichael\7+TaskbarTweaker - Empty directory

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/115585&drop=dogfoodAlpha

[Policy] Needs Manual Merge


broke tantivy go-wrapper into tantivy package

basic tests with Tantivy support in it's own package


GitHub registry

This PR

replaces Docker Hub with the GitHub registry in the GitHub workflow and updates the used GitHub actions
fixes the lint workflow

Needed for https://github.com/OpenTOSCA/opentosca-docker/pull/57

LGTM


Replace ex_twilio, make hackney configurable

Drops the dependancy on ex_twilio and makes API calls directly in the adapter. Includes support for passing options to hackney so that timeouts, pools, etc can be configured by the caller.

@swelham updated


Scheme detection fails depending on read order

I've encountered some strange behaviour where Viridian throws a KeyError if reads which can assemble fine are in a different order. Attached is a small MRE with latest docker image including logs and the exact commands run. Presumably this behaviour might change in the forthcoming release, but I'd be v grateful if you could replicate and/or comment. These are simulated reads and may be fundamentally unsound, however this behaviour is surprising as a user.

deepak-testcase-partial-viridian-repro.zip
2022-07-22 Diff fastqs.html.gz

This is a very interesting bug @bede , thanks for raising it!
Thanks also for providing a MRE - i don't see any file showing what the Key error was or when it happened?
Would it be possible to add a readme to explain the contents of the deepak zip? It looks to me like A-08a84971 failed with no json output, but A-08a84971.8c3 passed/succeeded, is that right?
But for D-f27c0b3e.085, it seems to have failed and provided a json. And that json ends with
"read_and_primer_stats": null,   "read_sampling": null,   "viridian": null,   "self_qc": null
which means we didn't even get as far as finishing processing the reads ready for assembly.
Are you providing 2 examples , each with 2 attempts with reads in different orders (which you have deliberately reordered?), and in one case it failed with no output and one with a json? Which had the key error and what was the exact output?
We'll take a look but @martinghunt is away on holiday for the next week, so

Thanks Zam, sorry I didn't provide the KeyError, and I'm afraid there is a defect with my example anyway which makes it far less interesting – the reads are valid pairs but the L and R reads appear to be duplicated, so it's not surprising viridian encounters issues, feel free to close for now while I investigate.

ah, well, if the L and R reads are duplicated, i expect viridian might say "these aren't behaving right for any of our amplicons", but i wouldn't expect a key error, it would just say there was "no good data". OK closing, feel free to re-raise

Agree with your comments – here's that KeyError for reference:
(base) bede@yoshina ~ % docker run -v /Users/bede/Desktop/deepak-testcase-partial-viridian-repro:/data ghcr.io/iqbal-lab-org/viridian_workflow:latest viridian_workflow run_one_sample --tech illumina --ref_fasta /data/MN908947v3.fasta --reads1 /data/D-f27c0b3e/085c811a-587d-5f6f-4977-130026e90eb2.reads_1.fastq --reads2 /data/D-f27c0b3e/085c811a-587d-5f6f-4977-130026e90eb2.reads_2.fastq --outdir /data/D-f27c0b3e.085
[2022-07-22T13:35:06 viridian_workflow INFO] Start running viridian_workflow, output dir: /data/D-f27c0b3e.085
[2022-07-22T13:35:06 viridian_workflow INFO] No primer schemes provided. Using all built in schemes
[2022-07-22T13:35:06 viridian_workflow INFO] Processed amplicon scheme files. Amplicon scheme names: COVID-AMPLISEQ-V1,COVID-ARTIC-V3,COVID-ARTIC-V4,COVID-MIDNIGHT-1200
[2022-07-22T13:35:06 viridian_workflow INFO] Mapping reads to reference
[M::mm_idx_gen::0.008*0.54] collected minimizers
[M::mm_idx_gen::0.010*0.61] sorted minimizers
[M::main::0.010*0.62] loaded/built the index for 1 target sequence(s)
[M::mm_mapopt_update::0.010*0.62] mid_occ = 1000
[M::mm_idx_stat] kmer size: 21; skip: 11; is_hpc: 0; #seq: 1
[M::mm_idx_stat::0.010*0.62] distinct minimizers: 4989 (99.98% are singletons); average occurrences: 1.002; average spacing: 5.979; total length: 29903
[M::worker_pipeline::11.662*0.30] mapped 99000 sequences
[M::main] Version: 2.17-r974-dirty
[M::main] CMD: minimap2 -R @RG\tID:1\tSM:sample -t 1 -a -x sr /data/MN908947v3.fasta /data/D-f27c0b3e/085c811a-587d-5f6f-4977-130026e90eb2.reads_1.fastq /data/D-f27c0b3e/085c811a-587d-5f6f-4977-130026e90eb2.reads_2.fastq
[M::main] Real time: 11.674 sec; CPU: 3.533 sec; Peak RSS: 0.106 GB
[2022-07-22T13:35:18 viridian_workflow INFO] Detecting amplicon scheme and gathering read statistics
Traceback (most recent call last):
  File "/usr/local/bin/viridian_workflow", line 8, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.8/dist-packages/viridian_workflow/__main__.py", line 215, in main
    args.func(args)
  File "/usr/local/lib/python3.8/dist-packages/viridian_workflow/tasks/run_one_sample.py", line 13, in run
    one_sample_pipeline.run_one_sample(
  File "/usr/local/lib/python3.8/dist-packages/viridian_workflow/one_sample_pipeline.py", line 447, in run_one_sample
    pipeline.run()
  File "/usr/local/lib/python3.8/dist-packages/viridian_workflow/one_sample_pipeline.py", line 418, in run
    self.initial_read_map_and_detect_amplicon_scheme()
  File "/usr/local/lib/python3.8/dist-packages/viridian_workflow/one_sample_pipeline.py", line 191, in initial_read_map_and_detect_amplicon_scheme
    self.amplicon_tsv = self.amplicon_scheme_name_to_tsv[chosen_scheme]
KeyError: None

that's super helpful, thanks! This was a regrettably poor error message for when the amplicon scheme fails to be detected in v0.3.7.
The newer images throw an exception with a proper explanation:
https://github.com/jeff-k/viridian_workflow/blob/0317b31804075719b96a4fb17182a7217be06f4a/viridian_workflow/readstore.py#L203

So...why was it read order dependent??

I don't think the issue was with the read order. In the failed case the R1 and R2 reads were the same, this would cause the fragments to amplicon identification.

Jeff is spot on. This has turned into a KeyError report rather than viridian-behaves-weirdly-due-to-read-order report. Sorry for misleading, and thanks!

For the record, uploading an empty fastq reproduces this KeyError in 0.3.7 with docker and in gpas-dev.


Allow controlling of the maximum queue size for daemons

This came up with the Gunyah integration testing with CrosVM. As their implementation has a fairly small amount of memory in the shared memory portion they couldn't fit the QUEUE_SIZE queue in it. This was solved with a local patch for the demo but obviously it would be nice to control this via an option/config.

I think they just hardcoded it for the purposes of the demo.