ameobea / tickgrinder Goto Github PK

Compiling tickgrinder-util v0.1.0 (/home/rustmann/RustProjects/tickgrinder/util)
error[E0583]: file not found for module conf
--> src/lib.rs:27:9
|
27 | pub mod conf;
| ^^^^
|
= help: name the file either conf.rs or conf/mod.rs inside the directory "src"

error: aborting due to previous error

For more information about this error, try rustc --explain E0583.
error: Could not compile tickgrinder-util.

To learn more, run the command again with --verbose.
Makefile:171: recipe for target 'test' failed
make: *** [test] Error 101

Hello~I just visited here. It looks cool project.
Is there some way to test this, or sample project?

$ make test
# copy libstd to the dist/lib directory if it's not already there
if [[ ! -f dist/lib/$(find $(rustc --print sysroot)/lib | grep -E "libstd-.*\.so" | head -1) ]]; then \
	cp $(find $(rustc --print sysroot)/lib | grep -E "libstd-.*\.so" | head -1) dist/lib; \
fi;
cd configurator && LD_LIBRARY_PATH="../../dist/lib" RUSTFLAGS="-L ../../util/target/debug/deps -L ../../dist/lib -C prefer-dynamic" cargo test --no-fail-fast
   Compiling bit-set v0.4.0
   Compiling cursive v0.6.4
   Compiling toml v0.4.5
   Compiling rand v0.3.19
   Compiling termion v1.5.1
   Compiling num-integer v0.1.35
   Compiling serde_json v0.8.6
   Compiling num-complex v0.1.41
   Compiling indoc v0.1.15
   Compiling num-iter v0.1.34
   Compiling num-bigint v0.1.41
   Compiling chan v0.1.19
error[E0061]: this function takes 2 parameters but 1 parameter was supplied
  --> /home/caio/.cargo/registry/src/github.com-1ecc6299db9ec823/indoc-0.1.15/src/lib.rs:87:30
   |
87 |             let unindented = parse::str_lit(&unindent(&name.as_str()));
   |                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected 2 parameters

error: aborting due to previous error

error: Could not compile `indoc`.
warning: build failed, waiting for other jobs to finish...
error: build failed
make: *** [Makefile:173: test] Error 101

Probably related to dtolnay/indoc#10

Since I do most of my development on mac these days, it will be very helpful to be able to build and run the platform on it. In addition, many people use mac and being able to have it install there without having to go through extra hassle is a great bonus.

In the future, I'd like to get it building on Windows as well, but as I don't really have a way to test that (and it's not a priority for me right now) that will have to wait for another time.

When spawning instances, it's possible that high network delay may cause the instance to take a while to actually spawn, leading the Spawner to think it's dead before it's actually started listening for Ping commands to respond to. The Spawner should put the instance in a Pending queue and either give it a long time to spawn or wait for a Successfully Spawned message from the instance.

Users should be able to set up and run the entire platform through Docker. This will be useful for the continuous integration and will make things like automatic deployments much easier as well.

This project could really benefit from some kind of CI that automatically builds the platform in its entirety and runs the full battery of tests. This will require a significant amount of effort but will probably be worth it in the long run.

The first step should be to get all of the tests to pass successfully. Tests involving functionality that no longer exists or must be changed significantly should be removed or disabled until such a time as they can be re-implemented correctly.

Ideally, an automatic deployment system such as now.sh would be set up as well with a full demo version of the platform, but this isn't necessarily in the scope of this issue.

Currently, the log viewer in the MM is a very simple implementation, simply listening to messages arriving over the wire and adding them to the log table.

I'd love to implement a react-virtualized approach with an infinitely-scrolling list that's populated from the PostgreSQL server. I honestly can't remember very well just how far along it was in development, but it should also have full support for sorting, filtering, etc.

All dependencies in use by the platform should be updated to their latest versions. The goal is to peg the entire platform to one version of Rust nightly which can then be incrementally updated as development continues.