cosmicespresso/bot_or_not

2019 Mozilla Creative Awards: Truth or Dare with a 🤖or a 🤷‍♀️

bot_or_not's Issues

TypeError: Failed to execute 'connect' on 'AudioNode': No function was found that matched the signature provided.

(sometimes)

Install GA

click events return null sometimes - no pattern

{"errorType":"Error","errorMessage":"14 UNAVAILABLE: Stream refused by server","trace":["Error: 14 UNAVAILABLE: Stream refused by server"," at Object.

seems to be a gRPC issue. added a try-catch to wrap around the server call, but it's hard to test as this error very occasional, and nobody seems very sure what's causing it.

if you see it, lmk!

set timeout for bot to speak in round1 (step 5)

In the first Chat round, we currently expect the player to initiate conversation. This is to avoid the impression that the bot is somehow 'in control' of the interaction, but we run the risk that the interaction could be very slow/awkward to start if both parties remain silent.

Thus, perhaps building in a 4-8 second timeout window, after which the bot will initiate conversation might be a good way to handle the interaction. Unsure of the do's and dont's of this WRT the current react flow but happy to look at this later this week.

shop button removes AudioVis but doesn't render Chat

recorder keeps running

where are the dots?

'not very convincing' bot responses thread 🤔

bot no longer starting truth round

How this worked before:
When a new bot was configured before starting a round, if the bot was the 'truth challenge bot' (the one that challenges the player) then a function called chooseTruth would be called. This would select a truth challenge from a list on the backend, and append it to the chat at the start of the round.

What happens now:
chooseTruth() is getting called (twice, actually -- eek), but the bot appends nothing to the chat window, until the player says something.

I assume this is because botQueue is now getting cleared at the start of each round.

What I assume needs to happen:
chooseTruth() needs to get called after botQueue is cleared. unsure why getting called twice though.

@Kallirroi does this seem right? lmk if there's anything I'm missing, happy to look into this this afternoon.

Can we rename the repo?

setting chat round timer > 60 causes it to loop back around

We're unlikely to want to do this so it's not really an issue per se, but wanted to check that this was expected behaviour!

59 seconds continues as normal
60 seconds loops back round to 0, then continues
61 seconds loops back round to 0, then continues

I reckon it's because of this line in Utils.js:

  var seconds = (Math.floor(time / 1000) % 60);

refactor timer to only get triggered when playing

handle this.state.currentBot.name better

let context = this.state.currentBot.name === "truth_bot_answering" ? "truthChallenge" : "other"

sometimes bot typing time overly-long

noticed this during the bot queue debugging: we can just add a cap here, but might be good to know why the timing is getting so high. It seems to go up when you overload the bot with messages, though perhaps this is just a coincidence.

how to order bots

Round 1: bot speaks first
Round 2: user speaks first
Round 3: bot speaks first (?) or random (?)

header issues

audioVis appears to keep recording after leaving the page

or else, for some reason the thing gathering sound data keeps printing to the console:

safari input bar style

'Your browser does not support recording audio'

context set is 'undefined'

every so often the context doesn't set properly, need to figure out why

after Stop button is pressed Visualization doesn't show

the number has become very small :3

on Google Chrome, responsive design mode, iPhone 6/7/8

submit button from bar doesn't respond

crashes on Firefox (scrollintoviewifneeded)

move chat processing functions to a separate helper file?

Just a sanity check about general architecture: right now App.js holds the state for pretty much everything, and controls the events for everything too. The other components are just recyclable UI. Does that make sense?

I would ideally want to separate the functions that handle the messaging (in a separate function or encapsulate them in the Chat component itself) but worry it might break things, especially bc I'm not sure how the bot array exactly works.

What exactly does App.js need to hold as state, and feed it through the lifecycle methods?

Curious to hear thoughts :)

clear message queue between rounds

currently, if you spam the bot by typing too fast, the queued messages get stored and then append to the chat next round.

I tried just setting botQueue to [] each time the bot changes, but i think that the messages are getting stuck in the timeout in Chat.js. Have verified that in this instance the POST request delay isn't the issue (they're returning on average about 145ms), though we might also want to make sure that that isn't a problem for slower internet speeds...

how to handle transition from NarratorWait to next steps?

so that the user thinks the other end is trying to come up with something

can we change the repo name?

finalize opponent names

https://github.com/dariusk/corpora/tree/master/data/humans

properly parse round number from Header.js

introducing timeout does not render visualization

bot dots on user side at start of interaction

they go back to the bot side after the bot first speaks

npm / webpack issues for bot integration

My version:

Cannot read property 'isUser' of undefined

I see this often when I breeze through the steps super fast, first time I see it when I take a while to chat

safari and firefox complain about speech recognition

Double update when chat times out

'context set is __system_counters__'

🤔

Scale BOT_SPEED to how long the incoming response is (currently random)

^ This can't actually be done by DF directly, but I can add a programmable delay in the middleware

this.props.onInputFocus is not a function

I get this on both Chrome and Firefox: is it a package I'm missing?

disable autozoom on mobile

context: https://stackoverflow.com/questions/2989263/disable-auto-zoom-in-input-text-tag-safari-on-iphone

size of text on Chrome, Firefox

'function invocation took longer than 10 seconds'

need error handling for occasional server snafu: perhaps local store of default fallbacks

handle Truth/Dare choice

we need to reset [messages] between rounds but not between AudioVis<-->Chat component transitions

handle "is it a bot/is it a human" choice

refactor serial parsing of StateMap since won't know exactly what the user has chosen

refactor CSS

stream refused by server error

some kind of gross JSON bug, need some error handling on this guy

{"errorType":"SyntaxError","errorMessage":"Unexpected end of JSON input","trace":["SyntaxError: Unexpected end of JSON input"," at JSON.parse ()"," at Runtime.exports.handler (/var/task/runSample.js:1:1204)"," at Runtime.handleOnce (/var/runtime/Runtime.js:66:25)"," at runNextTicks (internal/process/task_queues.js:59:5)"," at processImmediate (internal/timers.js:412:9)"]}

scrolling is broken :/

can't read property 'isUser' of undefined

bug you get by having unprocessed async responses after the app leaves the chat window. need some way to handle these