Topic: [ANN][XEL] Elastic Project - The Decentralized Supercomputer - page 276. (Read 450524 times)

Awesome. So we get back to work. Happy coding weekend!

unvoid, ignore the Account exceptions. There is still a lot of debug stuff enabled which can be safely ignored. The exception you have seen always is fired when you log into an account that has not been used before. I will make sure to strip the massive amounts of outputs. And I will try to name the commits a bit more "obvious" ;-)

Thanks for trying out everything. Feel free to change whatever you like and commit / create a pull request. I appreciate every helping hand.

elastic@srv:~/elastic/elastic-reference-client$ screen ./run.sh
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:626)
        at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:546)
        at java.lang.Thread.run(Thread.java:745)
nxt.http.ParameterException
        at nxt.http.ParameterParser.getAccount(ParameterParser.java:243)
        at nxt.http.GetAccountTransactions.processRequest(GetAccountTransactions.java:28)
        at nxt.http.APIServlet.process(APIServlet.java:209)
        at nxt.http.APIServlet.doGet(APIServlet.java:153)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:800)
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1125)
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1059)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
        at org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:52)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
        at org.eclipse.jetty.server.Server.handle(Server.java:497)
        at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:313)
        at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:248)
        at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:626)
        at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:546)
        at java.lang.Thread.run(Thread.java:745)

# Hosts from which to allow http/json API requests, if enabled. Set to * to allow all.
# Can also specify networks in CIDR notation, e.g. 192.168.1.0/24.
nxt.allowedBotHosts=127.0.0.1; localhost; 192.168.1.2; [0:0:0:0:0:0:0:1];

# Host interface on which to listen for http/json API request, default localhost only.
# Set to 0.0.0.0 to allow the API server to accept requests from all network interfaces.
nxt.apiServerHost=0.0.0.0

@unvoid: A file was missing. Sorry! It should be fixed now!

@unvoid: A file was missing. Sorry! It should be fixed now!

Current UI

Well, everyone can setup an own testnet using the instructions here:
https://bitcointalksearch.org/topic/m.16030417

For the "real" testnet I must fix one small bug which allows charging back more XEL than allowed upon work cancellation. This one will take a few days. Also I am not sure if we should do the hackathon first and then launch a testnet or do them simultaneourly.
Also I am not sure how we will handle "updates" to the software. We need some kind of way to invalidate old testnets and enforce new ones when a major update comes in (which is expected in the first days of public testing). What do you think?

elastic@srv:~/elastic/elastic-reference-client$ ./compile.sh
src/java/nxt/WorkLogicManager.java:954: error: cannot find symbol
        public ArrayList> getDataForPlot(long id, int limit_minutes) {
                         ^
  symbol:   class Quartett
  location: class WorkLogicManager
src/java/nxt/http/GetAccountWorkEfficiencyPlot.java:11: error: cannot find symbol
import nxt.Quartett;
          ^
  symbol:   class Quartett
  location: package nxt
src/java/nxt/WorkLogicManager.java:956: error: cannot find symbol
                ArrayList> ret = new ArrayList>();
                          ^
  symbol:   class Quartett
  location: class WorkLogicManager
src/java/nxt/WorkLogicManager.java:956: error: cannot find symbol
                ArrayList> ret = new ArrayList>();
                                                                                  ^
  symbol:   class Quartett
  location: class WorkLogicManager
src/java/nxt/WorkLogicManager.java:968: error: cannot find symbol
                                Quartett d = new Quartett((int) check.getInt(1),stime,(String) check.getString(2), 0L);
                                ^
  symbol:   class Quartett
  location: class WorkLogicManager
src/java/nxt/WorkLogicManager.java:968: error: cannot find symbol
                                Quartett d = new Quartett((int) check.getInt(1),stime,(String) check.getString(2), 0L);
                                                                           ^
  symbol:   class Quartett
  location: class WorkLogicManager
src/java/nxt/http/GetAccountWorkEfficiencyPlot.java:78: error: cannot find symbol
                ArrayList> ret_pre = WorkLogicManager.getInstance().getDataForPlot(workId, last_num);
                          ^
  symbol:   class Quartett
  location: class GetAccountWorkEfficiencyPlot
src/java/nxt/http/GetAccountWorkEfficiencyPlot.java:79: error: cannot find symbol
                for(Quartett t : ret_pre){
                    ^
  symbol:   class Quartett
  location: class GetAccountWorkEfficiencyPlot
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
8 errors
elastic@srv:~/elastic/elastic-reference-client$ java -version
java version "1.8.0_101"
Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)
elastic@srv:~/elastic/elastic-reference-client$

Current UI

so when will we have a testnet?

dear， you didn't follow the step and finished the vote.

after voting, you will find your address.