Welcome! This is the text-based companion guide to get you joined to the private development mesh and running collaborative tasks with FloCode.
amesh peer serve.
| export QUEUE='~/dev/amesh/.debug-queue/chris-enrollment' 13:58 [50/1997] | |
| ssh "$FLO_SSH" "mkdir -p $QUEUE; touch $QUEUE/incoming.md $QUEUE/status.md; tail -n +1 -f $QUEUE/status.md $QUEUE/incoming.md" | |
| Terminal 2: run debug + one join attempt | |
| bash <<'CHRIS_DEBUG' | |
| set -u | |
| export FLO_SSH='floleibert@192.168.68.60' |
| Standard Signal | |
| Standard Signal is the first hedge fund that researches and executes trades purely with AI. Our custom models discover and trade on new fundamental truths about the world before humans can. | |
| How today’s quant funds work | |
| In today’s quantitative finance landscape, there are generally two types of trading strategies. | |
| The first, known as high-frequency trading or HFT, uses deterministic and (by today’s standards) primitive ML models to quickly predict the future price of a security over a time horizon of milliseconds. These techniques do not care about the fundamentals of the underlying securities – they just seek to take advantage of noisy and rapid price movements. |
| interface: wg0 | |
| public key: I5utO6dP+N/CiMgUVjMNAufIOG4s17P88s9HOLBU7G4= | |
| private key: (hidden) | |
| listening port: 51820 | |
| peer: FDH2CNk5Dup/DaFEuoBkJSqZ+qgJvu+F+CU5L946Ph8= | |
| endpoint: 95.133.252.17:51820 | |
| allowed ips: 10.10.0.5/32 | |
| latest handshake: 2 seconds ago | |
| transfer: 365.10 KiB received, 827.73 KiB sent |
| be real: 10 GB is nothing in pretraining terms. it *can* move the needle for linux/bash—but only if you do it right (CPT + careful mixing), otherwise you just induce weird overfitting + forget general skills. | |
| --- | |
| ## what you actually want (afaict) | |
| you’re describing **continued pretraining (CPT)** on top of something like Google DeepMind’s Gemma. | |
| goal: |
| Nov 12 07:26:31 kt22 poseidon[12726]: #015#015 Could not connect to archive.cloudera.com:80 (184.73.217.71). - connect (110: Connection timed out)#015 | |
| Nov 12 07:26:31 kt22 poseidon[12726]: #015#015Err http://archive.cloudera.com/cdh4/ubuntu/precise/amd64/cdh/ precise-cdh4/contrib bigtop-utils all 0.6.0+140-1.cdh4.4.0.p0.24~precise-cdh4.4.0#015 | |
| Nov 12 07:26:31 kt22 poseidon[12726]: #015#015 Unable to connect to archive.cloudera.com:http:#015 | |
| Nov 12 07:26:31 kt22 poseidon[12726]: #015#015Err http://archive.cloudera.com/cdh4/ubuntu/precise/amd64/cdh/ precise-cdh4/contrib zookeeper all 3.4.5+23-1.cdh4.4.0.p0.24~precise-cdh4.4.0#015 | |
| Nov 12 07:26:31 kt22 poseidon[12726]: #015#015 Unable to connect to archive.cloudera.com:http:#015 | |
| Nov 12 07:26:31 kt22 poseidon[12726]: #015#015Err http://archive.cloudera.com/cdh4/ubuntu/precise/amd64/cdh/ precise-cdh4/contrib hadoop all 2.0.0+1475-1.cdh4.4.0.p0.23~precise-cdh4.4.0#015 | |
| Nov 12 07:26:31 kt22 poseidon[12726]: #015#015 Unable to connect to archive.cloudera.com:http:# |
| 10.235.22.60 ec2-50-19-155-11.compute-1.amazonaws.com | |
| 10.159.54.170 ec2-54-235-22-116.compute-1.amazonaws.com | |
| 10.168.15.46 ec2-107-20-130-87.compute-1.amazonaws.com | |
| 10.168.39.24 ec2-54-234-7-167.compute-1.amazonaws.com | |
| 10.182.167.70 ec2-54-227-192-125.compute-1.amazonaws.com | |
| 10.158.64.117 ec2-23-20-194-160.compute-1.amazonaws.com | |
| 10.170.45.42 ec2-54-234-95-249.compute-1.amazonaws.com | |
| 10.158.21.134 ec2-54-221-87-42.compute-1.amazonaws.com | |
| 10.157.31.208 ec2-50-16-34-254.compute-1.amazonaws.com | |
| 10.29.211.230 ec2-54-226-202-167.compute-1.amazonaws.com |
| #!/bin/bash | |
| ip=`ifconfig eth0|grep -o -e "inet addr:[0-9\.]*"|sed 's/.*://g'` | |
| name=`hostname` | |
| echo $ip $name |
| for parameter 1 at org.jclouds.cloudstack.handlers.InvalidateSessionAndRetryOn401AndLogoutOnClose.<init>(InvalidateSessionAndRetryOn401AndLogoutOnClose.java:51) | |
| at org.jclouds.cloudstack.config.CloudStackHttpApiModule.configure(CloudStackHttpApiModule.java:82) | |
| 19) No implementation for org.jclouds.cloudstack.features.SessionClient was bound. | |
| while locating org.jclouds.cloudstack.features.SessionClient | |
| for parameter 0 at org.jclouds.cloudstack.loaders.LoginWithPasswordCredentials.<init>(LoginWithPasswordCredentials.java:37) | |
| at org.jclouds.cloudstack.config.CloudStackHttpApiModule.provideLoginResponseCache(CloudStackHttpApiModule.java:142) | |
| 20) No implementation for org.jclouds.cloudstack.CloudStackClient was bound. | |
| at org.jclouds.cloudstack.compute.config.CloudStackComputeServiceContextModule.listOSCategories(CloudStackComputeServiceContextModule.java:162) | |
| 21) No implementation for org.jclouds.cloudstack.CloudStackClient was bound. | |
| at org.jclouds.cloudstack.compute.config.CloudStackComputeServ |
| 13/08/08 19:33:00 INFO mapred.JobTracker: Creating the system directory | |
| 13/08/08 19:33:00 WARN mapred.JobTracker: Failed to operate on mapred.system.dir (hdfs://10.145.214.207/tmp/hadoop/mapred/system) because of permissions. | |
| 13/08/08 19:33:00 WARN mapred.JobTracker: This directory should be owned by the user 'mapred (auth:SIMPLE)' | |
| 13/08/08 19:33:00 WARN mapred.JobTracker: Bailing out ... | |
| org.apache.hadoop.security.AccessControlException: Permission denied: user=mapred, access=EXECUTE, inode="/tmp/hadoop":ubuntu:hadoop:drwx------ | |
| at org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:224) | |
| at org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkTraverse(FSPermissionChecker.java:177) | |
| at org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:142) | |
| at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkPermission(FSNamesystem.java:4716) | |
| at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkPermission(FSN |