Troubleshooting

This guide helps diagnose and resolve common issues encountered when interacting with the library.

Common Error Codes

COFFEE_LEVEL_LOW

Symptom: Slow response times, reduced output quality, increased typo rate.

Solution:

// Check current levels
const status = await daniel.getCoffeeLevel();
// => { level: 'critically-low', nextRefill: '10:30 CET' }

// Resolution: wait for automatic refill cycle, or provide external coffee
await daniel.refuel({ type: 'flat-white', origin: 'specialty' });

CONTEXT_SWITCH_ERROR

Symptom: Confused responses after rapid topic changes.

Solution: Allow a minimum 15-minute buffer between unrelated tasks. The library performs best with extended single-topic sessions.

TIMEZONE_MISMATCH

Symptom: Meeting scheduled at 3 AM CET.

Solution:

// Always check timezone before scheduling
console.log(daniel.timezone); // => 'Europe/Copenhagen'
// Note: The library was compiled in Australia but is deployed in Denmark.
// It still occasionally emits timestamps in AEST during periods of homesickness.

Frequently Encountered Issues

"What exactly do you research?"

Error: RESEARCH_DESCRIPTION_UNDERFLOW — Insufficient context provided.

Resolution:

"What's a Graph Neural Network?"

Error: PREREQUISITE_MISSING — Concept not found in caller's knowledge base.

Resolution:

"How is ML used in particle physics?"

Error: DOMAIN_BRIDGE_REQUIRED — Cross-domain translation needed.

Resolution:

"Are you available for [talk/seminar/workshop]?"

Status: Generally AVAILABLE — check current capacity:

const availability = await daniel.checkAvailability({
  type: 'talk',
  format: ['in-person', 'remote', 'hybrid'],
  topics: ['GNNs', 'tracking', 'ML-for-physics', 'open-science']
});

"Can I join your group / collaborate?"

Resolution: See the Contributing Guide for collaboration protocols.

Debug Mode

If unexpected behavior persists, enable verbose logging:

const daniel = new Daniel({
  debug: true,
  logLevel: 'verbose',
  // Warning: may produce excessive output about particle physics
});