cori / astronomical-twitterbot Goto Github PK

View Code? Open in Web Editor NEW

0.0 0.0 0.0 41 KB

Glitch twitterbot to-be

License: The Unlicense

JavaScript 93.64% CSS 6.36%

astronomy glitch twitter

astronomical-twitterbot's People

Contributors

Watchers

astronomical-twitterbot's Issues

handle the final error model

*** Horizons ERROR/Unexpected Results ***

opened via imdone.io from a code comment on 3f671125 by cori

astronomical-twitterbot/server.js

Lines 140 to 146 in 7c3c10e

 // TODO: handle the final error model id:5 gh:8 ic:gh 

 // *** Horizons ERROR/Unexpected Results *** 

 // Cannot interpret date. Type "?!" or try YYYY-Mon-Dy {HH:MM} format.

how to organize the "API" vs the bot?

opened via imdone.io from a code comment on 441b05ed by cori

astronomical-twitterbot/server.js

Lines 2 to 7 in 23e6ba2

 // TODO: how to organize the "API" vs the bot? id:1 gh:3 ic:gh 

 // TODO: logging? id:8 gh:12 ic:gh 

 // TODO: data persistance? id:7 gh:11 ic:gh 

 // TODO: set up cron id:9 gh:13 ic:gh 

 // TODO: reply immediately if 2*lt < ~5 minutes (the period I'll poll twitter for new messages) id:10 gh:14 ic:gh

add bot-ness

opened via imdone.io from a code comment on 441b05ed by cori

astronomical-twitterbot/server.js

Lines 1 to 6 in 23e6ba2

 // TODO: add bot-ness id:0 gh:2 ic:gh 

 // TODO: how to organize the "API" vs the bot? id:1 gh:3 ic:gh 

 // TODO: logging? id:8 gh:12 ic:gh 

 // TODO: data persistance? id:7 gh:11 ic:gh 

 // TODO: set up cron id:9 gh:13 ic:gh 

 // TODO: reply immediately if 2*lt < ~5 minutes (the period I'll poll twitter for new messages) id:10 gh:14 ic:gh

set up cron

opened via imdone.io from a code comment on 7c3c10e7 by cori

astronomical-twitterbot/server.js

Lines 5 to 10 in 23e6ba2

 // TODO: set up cron id:9 gh:13 ic:gh 

 // TODO: reply immediately if 2*lt < ~5 minutes (the period I'll poll twitter for new messages) id:10 gh:14 ic:gh 

 // init project 

 var express = require('express'); 

 var app = express();

Proper error handling?

opened via imdone.io from a code comment on e677a7da by cori

astronomical-twitterbot/server.js

Lines 227 to 232 in 23e6ba2

 /* TODO: Proper error handling? */ 

 console.log('Error!'); 

 console.log(err); 

 } 

 else{ 

 fs.writeFile(__dirname + '/last_mention_id.txt', status.id_str, function (err) {

some kind of race condition here; on occasion time_boundries is undefined when we get here

particularly (it seems) when there are multiple tweets/dms to handle

opened via imdone.io from a code comment on 5935f153 by cori

astronomical-twitterbot/server.js

Lines 289 to 295 in ec2f6ec

 // TODO some kind of race condition here; on occasion time_boundries is undefined when we get here 

 // particularly (it seems) when there are multiple tweets/dms to handle 

 var lt = output.split(time_boundaries.start)[2].split(time_boundaries.end)[0].trimLeft(); 

 return lt; 

 } 

 function convert_owlt_to_round_trip( one_way_light_time ) {

it seems like this doesn't always reset the session id, because we're getting back the same time for multiple bodies in one run

j = requestor.jar(); // need a new jar on every request to reset the session

opened via imdone.io from a code comment on 5935f153 by cori

astronomical-twitterbot/server.js

Lines 128 to 134 in ec2f6ec

 // TODO: it seems like this doesn't always reset the session id, because we're getting back the same time for multiple bodies in one run 

 // j = requestor.jar(); // need a new jar on every request to reset the session 

 return requestor.post({ jar: j, url: horizonsUri, form: {sstr:name, body_group:'all', find_body:'Search', mb_list:'planet'}}) 

 .then( function( html ) { 

 var dom = cheerio.load(html); 

 var errorNode = dom('.error'); 

 var settings = dom('h3').next();

use the start_time to find the appropriate row in the output table, then grab the 1-way_LT column's value

opened via imdone.io from a code comment on 3f671125 by cori

astronomical-twitterbot/server.js

Lines 166 to 167 in 6f24d6e

 // TODO: use the start_time to find the appropriate row in the output tablbe, then grab the 1-way_LT column's value 

 }

Error handling?

opened via imdone.io from a code comment on e677a7da by cori

astronomical-twitterbot/server.js

Lines 271 to 276 in 23e6ba2

 /* TODO: Error handling? */ 

 }); 

 } 

 }); 

 }); 

 } else {

send query and respond to dm

opened via imdone.io from a code comment on 95407804 by cori

astronomical-twitterbot/server.js

Lines 392 to 397 in 1e07b17

 // TODO send query and respond to dm id:18 gh:24 ic:gh 

 }); 

 } else if (err) { 

 console.log(err); 

 } else { 

 /* No new DMs since the last time we checked. */

should the step requests just be chained? They're just building up the session data for the final request.

opened via imdone.io from a code comment on 441b05ed by cori

astronomical-twitterbot/server.js

Lines 27 to 32 in 2f50e6e

 // TODO: should the step requests just be chained? They're just building up the session data for the final request. 

 horizons_find_astro_body_step(); 

 // response.send('This is an api for testing'); 

 }); 

 // listen for requests :)

something's up with the times - I'm either getting or no matter what body names I use.

     Argh! for some bodies there are multiple possible responses, and you've got to select amongst them

opened via imdone.io from a code comment on 3c22b297 by cori

astronomical-twitterbot/server.js

Lines 100 to 106 in 1e07b17

 // TODO: something's up with the times - I'm either getting 16:33 or 20:27 no matter what body names I use. id:17 gh:23 ic:gh 

 // Argh! for some bodies there are multiple possible responses, and you've got to select amongst them 

 /****************** multi-body selection ****************** 

 <form method="post" action="https://ssd.jpl.nasa.gov/horizons.cgi#top" enctype="multipart/form-data"> 

 <h3>select from 2 matching bodies:</h3> 

 <select name="body" size="2">

data persistance?

opened via imdone.io from a code comment on 7c3c10e7 by cori

astronomical-twitterbot/server.js

Lines 4 to 9 in 23e6ba2

 // TODO: data persistance? id:7 gh:11 ic:gh 

 // TODO: set up cron id:9 gh:13 ic:gh 

 // TODO: reply immediately if 2*lt < ~5 minutes (the period I'll poll twitter for new messages) id:10 gh:14 ic:gh 

 // init project 

 var express = require('express');

Proper error handling?

opened via imdone.io from a code comment on e677a7da by cori

astronomical-twitterbot/server.js

Lines 265 to 270 in 23e6ba2

 /* TODO: Proper error handling? */ 

 console.log('Error!'); 

 console.log(err); 

 } 

 else{ 

 fs.writeFile(__dirname + '/last_dm_id.txt', dm.id_str, function (err) {

parse the reponse body, looking for this content, or a subset thereof, and return, skipping the rest of the chain

missing celestial body results in

opened via imdone.io from a code comment on 441b05ed by cori

astronomical-twitterbot/server.js

Lines 49 to 55 in 2f50e6e

 // TODO: parse the reponse body, looking for this content, or a subset thereof, and return, skipping the rest of the chain 

 // missing celestial body results in  

 /* 

 <div class="error"> 

 <a name="top"><b>&nbsp; ERROR:</b> 

 </a><ul> 

 <li>no matching body found

Handle proper responses based on whether the tweets succeed, using Promises. For now, let's just return a success message no matter what.

opened via imdone.io from a code comment on e677a7da by cori

astronomical-twitterbot/server.js

Lines 283 to 285 in 23e6ba2

 /* TODO: Handle proper responses based on whether the tweets succeed, using Promises. For now, let's just return a success message no matter what. */ 

 response.sendStatus(200); 

 });

reply immediately if 2*lt < ~5 minutes (the period I'll poll twitter for new messages)

opened via imdone.io from a code comment on 7c3c10e7 by cori

astronomical-twitterbot/server.js

Lines 6 to 11 in 23e6ba2

 // TODO: reply immediately if 2*lt < ~5 minutes (the period I'll poll twitter for new messages) id:10 gh:14 ic:gh 

 // init project 

 var express = require('express'); 

 var app = express();

extract the request pattern

opened via imdone.io from a code comment on 3f671125 by cori

astronomical-twitterbot/server.js

Lines 50 to 55 in 7c3c10e

 // TODO: extract the request pattern id:4 gh:7 ic:gh 

 function horizons_find_astro_body_step( name ) { 

 console.clear(); 

 // curl -d sstr=sedna -d body_group=all -d find_body=Search -d mb_list=planet https://ssd.jpl.nasa.gov/horizons.cgi -v  

 requestor.post({ jar: j, url: horizonsUri, form: {sstr:name, body_group:'all', find_body:'Search', mb_list:'planet'}}, function( error, response, body ) {

logging?

opened via imdone.io from a code comment on 7c3c10e7 by cori

astronomical-twitterbot/server.js

Lines 3 to 8 in 23e6ba2

 // TODO: logging? id:8 gh:12 ic:gh 

 // TODO: data persistance? id:7 gh:11 ic:gh 

 // TODO: set up cron id:9 gh:13 ic:gh 

 // TODO: reply immediately if 2*lt < ~5 minutes (the period I'll poll twitter for new messages) id:10 gh:14 ic:gh 

 // init project

Error handling?

opened via imdone.io from a code comment on e677a7da by cori

astronomical-twitterbot/server.js

Lines 233 to 238 in 23e6ba2

 /* TODO: Error handling? */ 

 }); 

 } 

 }); 

 }); 

 } else {

send query and respond

opened via imdone.io from a code comment on 95407804 by cori

astronomical-twitterbot/server.js

Lines 368 to 373 in 1e07b17

 // TODO send query and respond id:16 gh:22 ic:gh 

 }); 

 } else if (err) { 

 console.log(err); 

 } else { 

 /* No new mentions since the last time we checked. */

	// TODO: handle the final error model id:5 gh:8 ic:gh
	// * Horizons ERROR/Unexpected Results *




	// Cannot interpret date. Type "?!" or try YYYY-Mon-Dy {HH:MM} format.

	// TODO: how to organize the "API" vs the bot? id:1 gh:3 ic:gh
	// TODO: logging? id:8 gh:12 ic:gh
	// TODO: data persistance? id:7 gh:11 ic:gh
	// TODO: set up cron id:9 gh:13 ic:gh
	// TODO: reply immediately if 2*lt < ~5 minutes (the period I'll poll twitter for new messages) id:10 gh:14 ic:gh

	// TODO: add bot-ness id:0 gh:2 ic:gh
	// TODO: how to organize the "API" vs the bot? id:1 gh:3 ic:gh
	// TODO: logging? id:8 gh:12 ic:gh
	// TODO: data persistance? id:7 gh:11 ic:gh
	// TODO: set up cron id:9 gh:13 ic:gh
	// TODO: reply immediately if 2*lt < ~5 minutes (the period I'll poll twitter for new messages) id:10 gh:14 ic:gh

	// TODO: set up cron id:9 gh:13 ic:gh
	// TODO: reply immediately if 2*lt < ~5 minutes (the period I'll poll twitter for new messages) id:10 gh:14 ic:gh

	// init project
	var express = require('express');
	var app = express();

	/* TODO: Proper error handling? */
	console.log('Error!');
	console.log(err);
	}
	else{
	fs.writeFile(__dirname + '/last_mention_id.txt', status.id_str, function (err) {

	// TODO some kind of race condition here; on occasion time_boundries is undefined when we get here
	// particularly (it seems) when there are multiple tweets/dms to handle
	var lt = output.split(time_boundaries.start)[2].split(time_boundaries.end)[0].trimLeft();
	return lt;
	}

	function convert_owlt_to_round_trip( one_way_light_time ) {

	// TODO: it seems like this doesn't always reset the session id, because we're getting back the same time for multiple bodies in one run
	// j = requestor.jar(); // need a new jar on every request to reset the session
	return requestor.post({ jar: j, url: horizonsUri, form: {sstr:name, body_group:'all', find_body:'Search', mb_list:'planet'}})
	.then( function( html ) {
	var dom = cheerio.load(html);
	var errorNode = dom('.error');
	var settings = dom('h3').next();

	// TODO: use the start_time to find the appropriate row in the output tablbe, then grab the 1-way_LT column's value
	}

	// TODO send query and respond to dm id:18 gh:24 ic:gh
	});
	} else if (err) {
	console.log(err);
	} else {
	/* No new DMs since the last time we checked. */

	// TODO: should the step requests just be chained? They're just building up the session data for the final request.
	horizons_find_astro_body_step();
	// response.send('This is an api for testing');
	});

	// listen for requests :)

	// TODO: something's up with the times - I'm either getting 16:33 or 20:27 no matter what body names I use. id:17 gh:23 ic:gh
	// Argh! for some bodies there are multiple possible responses, and you've got to select amongst them

	/**************** multi-body selection ****************
	<form method="post" action="https://ssd.jpl.nasa.gov/horizons.cgi#top" enctype="multipart/form-data">
	<h3>select from 2 matching bodies:</h3>
	<select name="body" size="2">

	// TODO: parse the reponse body, looking for this content, or a subset thereof, and return, skipping the rest of the chain
	// missing celestial body results in
	/*
	<div class="error">
	<a name="top"><b>  ERROR:</b>
	</a><ul>
	<li>no matching body found

	/* TODO: Handle proper responses based on whether the tweets succeed, using Promises. For now, let's just return a success message no matter what. */
	response.sendStatus(200);
	});

	// TODO: extract the request pattern id:4 gh:7 ic:gh
	function horizons_find_astro_body_step( name ) {
	console.clear();
	// curl -d sstr=sedna -d body_group=all -d find_body=Search -d mb_list=planet https://ssd.jpl.nasa.gov/horizons.cgi -v
	requestor.post({ jar: j, url: horizonsUri, form: {sstr:name, body_group:'all', find_body:'Search', mb_list:'planet'}}, function( error, response, body ) {

	// TODO send query and respond id:16 gh:22 ic:gh
	});
	} else if (err) {
	console.log(err);
	} else {
	/* No new mentions since the last time we checked. */

cori / astronomical-twitterbot Goto Github PK

astronomical-twitterbot's People

Contributors

Watchers

astronomical-twitterbot's Issues

Recommend Projects

Recommend Topics

Recommend Org