-
Notifications
You must be signed in to change notification settings - Fork 0
[WIP] Increase test coverage for image-vision.js to 100% #65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
Copilot
wants to merge
358
commits into
master
Choose a base branch
from
copilot/improve-test-coverage-image-vision
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tability and structure
…proved functionality and structure
… replies and add corresponding tests
…proved functionality and structure
- Added reference to main monorepo https://github.com/anabelle/pixel - Updated character.json and character.ts to include monorepo info - Pixel now knows about the complete ecosystem structure - Individual repos still available as submodules
- Added line about being proudly open source to character bio - Reflects Pixel's philosophy of transparency and community - Updated both character.ts and regenerated character.json - 'Transparency is survival; closed source is just expensive coffin polish'
- Add multi-round search strategy that continues until quality interactions achieved - Implement adaptive quality gates with configurable strictness levels (normal/strict/relaxed) - Add topic expansion for fallback searches when initial topics yield no results - Introduce DiscoveryMetrics class for tracking success rates and adaptive behavior - Add progressive search expansion with broader time ranges and increased limits - Add configuration options for discovery quality settings - Ensure guaranteed minimum quality interactions per discovery run - Maintain backward compatibility while significantly improving discovery reliability New env vars: - NOSTR_DISCOVERY_MIN_QUALITY_INTERACTIONS (default: 1) - NOSTR_DISCOVERY_MAX_SEARCH_ROUNDS (default: 3) - NOSTR_DISCOVERY_STARTING_THRESHOLD (default: 0.6) - NOSTR_DISCOVERY_THRESHOLD_DECREMENT (default: 0.05) - NOSTR_DISCOVERY_QUALITY_STRICTNESS (default: normal)
- Add NOSTR_DISCOVERY_MIN_QUALITY_INTERACTIONS to .env.example - Add NOSTR_DISCOVERY_MAX_SEARCH_ROUNDS to .env.example - Add NOSTR_DISCOVERY_STARTING_THRESHOLD to .env.example - Add NOSTR_DISCOVERY_THRESHOLD_DECREMENT to .env.example - Add NOSTR_DISCOVERY_QUALITY_STRICTNESS to .env.example - Update .env with default values for new discovery settings These new environment variables allow fine-tuning of the quality-first discovery algorithm to balance interaction quality vs quantity.
- Add detailed logging for topic expansion (primary vs fallback) - Log search parameter expansion for each round - Track quality strictness changes (normal -> relaxed) - Log adaptive threshold activations and adjustments - Add round-by-round metrics tracking (quality, replies, avg score) - Log early termination when quality target is reached - Warn when discovery fails to meet quality requirements - Add debug logging for threshold comparisons and skip reasons These logs will help monitor and debug the new multi-round quality-first discovery behavior.
- Add WebSocketWrapper class to set maxListeners on WebSocket instances - Add NOSTR_MAX_WS_LISTENERS setting to .env.example - Prevent memory leak warnings when multiple pong listeners are added
- Add ElizaOS architecture and framework integration details - Add platform-specific setup guides (Telegram, Discord, Twitter, Nostr) - Add character development and customization section - Add plugin system documentation with examples - Add testing strategy and deployment instructions - Add comprehensive troubleshooting with platform-specific solutions - Add monitoring and analytics section - Expand from 114 to 400+ lines of professional documentation
- Add comprehensive server monitoring documentation - Include monitoring commands and configuration details - Document log management and troubleshooting procedures - Update performance monitoring strategies
…mework - Added socket.io-client to package.json for WebSocket support. - Created basic tests for bridge validation, rate limiting, and input validation in test-basic.js. - Implemented comprehensive tests for Nostr service and listener in test-comprehensive.js. - Developed integration tests for ElizaOS memory patterns in test-eliza-integration.js. - Added external post testing functionality in test-external-post.js. - Created integration test for LNPixels event processing in test-integration.js. - Developed listener tests with mock WebSocket in test-listener.js. - Implemented memory creation tests in test-memory.js. - Updated character configuration to include LNPIXELS_WS_URL. - Created lnpixels-listener.ts service file for future implementation.
…gement improvements
…ts using memory locks
…nd memory recording
…events and interactions
…ng for events and interactions
…text and interactions
…c examples in zap prompts
- Fixed mismatched key priority order causing duplicate posts - Both files now use: event_id → payment_hash → id → coords+timestamp - Added id field to listener's makeKey function for consistency - Prevents race condition where same event generates different keys
- Log dedupe keys and activity fields in both listener and service - Log about-to-post messages to identify source of fake posts - Log scheduled post sanitization to track coordinate removal - Will help identify why (23,17) posts still appear
Root cause: LNPixels API emits TWO activity.append events per purchase: 1. Real pixel event with x,y,color data 2. Generic payment event with type:'payment', no pixel data Solution: - Filter out payment-type events in validateActivity() - Skip events missing x,y,color coordinates - Keeps legitimate pixel events, blocks ghost events This eliminates both duplicate posting and fake (23,17) posts which were generated from empty activity data.
#23) * feat(nostr): adaptive trending algorithm with velocity/novelty/baseline; integrate into context accumulator and service; expose trending in current activity; add tests (Closes #6) * Update plugin-nostr/lib/adaptiveTrending.js Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * chore(nostr): log adaptive trending snapshot in trend detection to surface score/velocity/novelty/development * adaptiveTrending: fix created_at unit detection, maintain sorted history on insert, guard intensity denom; tests: import vitest, clarify baseline hours --------- Co-authored-by: Anabelle Handdoek <git@huellaspyp.com> Co-authored-by: jp <108901404+jorparad@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
…avioral adjustments and mandatory changes
… for posts analysis
…etection (Issue #7) (#29) * feat: Implement adaptive storyline progression and emerging-pattern detection (Issue #7) - Add hybrid rule-based/LLM storyline detection system - Implement storyline lifecycle tracking through regulatory→technical→market→community phases - Add confidence-calibrated scoring boosts for engagement prioritization - Create online learning system for pattern recognition - Include comprehensive testing and backward compatibility verification - Add debug tools for batch analysis and validation All acceptance criteria from Issue #7 have been met with full backward compatibility. * fix: implement CodeRabbit AI review fixes for adaptive storyline progression - Fix debug-storyline-tracker.js constructor to use mock runtime - Correct analyzePost method calls to pass content, topics array, and timestamp - Fix stats field access to use getStats() method - Fix narrativeMemory.js constructor to use options object - Fix primaryTopic variable scope in service.js - Rename community phase from 'discussion' to 'conversation' to avoid collision - Update test assertions and comments for accuracy - Convert adaptiveTrending.test.js from CommonJS to ES modules - All 202 tests now passing * Update plugin-nostr/lib/storylineTracker.js Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> * Update plugin-nostr/test-storyline-tracker.js Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> * feat: enhance storyline context retrieval and analysis for improved narrative progression detection * refactor: remove redundant setup code for known phase detection tests --------- Co-authored-by: Anabelle Handdoek <git@huellaspyp.com> Co-authored-by: jp <108901404+jorparad@users.noreply.github.com> Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
* Fix home feed interaction probabilities (Issue #24) - Increase homeFeedReactionChance from 0.05 to 0.15 (15%) - Increase homeFeedRepostChance from 0.005 to 0.01 (1%) - Increase homeFeedQuoteChance from 0.001 to 0.005 (0.5%) - Total interaction probability now ~16.5% vs previous 5.6% - Maintains 'like' reactions as most common to prevent spam * fix(nostr): update home feed interaction probabilities and add reply functionality * fix(nostr): refactor home feed reply handling and integrate image processing * fix(nostr): enhance reply handling by adding thread context retrieval --------- Co-authored-by: Anabelle Handdoek <git@huellaspyp.com>
* Initial plan * Implement content freshness decay algorithm with tests Co-authored-by: anabelle <445690+anabelle@users.noreply.github.com> * Fix storyline advancement detection to require content indicators Co-authored-by: anabelle <445690+anabelle@users.noreply.github.com> * Add comprehensive freshness decay documentation Co-authored-by: anabelle <445690+anabelle@users.noreply.github.com> * Freshness decay: remove extra advancement keyword gating; allow zero lookback; fix tests; update docs (fences + logic) * Tests: extract recurring theme constant; no functional change * Tests: isolate config cases from similarity bump/clamping; green suite for freshness decay * Refactor NarrativeMemory constructor for improved readability; remove unnecessary whitespace and comments * Update plugin-nostr/lib/service.js Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: anabelle <445690+anabelle@users.noreply.github.com> Co-authored-by: Anabelle Handdoek <git@huellaspyp.com> Co-authored-by: Anabelle Handdoek <github@huellaspyp.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* ci: run plugin-nostr vitest on all PRs (Fixes #34) * ci: finalize workflow trigger and caching * fix: Make logger calls safe in handleMention and handleDM to prevent test failures - Wrap all module-level logger calls with optional chaining (logger?.method?.()) - Add try-catch blocks around logger calls to prevent throwing in test environment - Initialize missing service properties in test setup (dmEnabled, dmReplyEnabled, dmThrottleSec) - Enhance @elizaos/core mock with createUniqueUuid, ChannelType, and ModelType exports - All 12 handlerIntegration tests now pass * fix: Add missing node-fetch dependency for image-vision module - Adds node-fetch ^2.7.0 to dependencies - Updates bun.lock - Fixes CI test failure: 'Cannot find module node-fetch' - Required by lib/image-vision.js for image URL processing * fix: Add node-fetch dependency to package.json and package-lock.json * fix: Update package-lock.json with node-fetch dependency - Regenerate package-lock.json to include node-fetch and its dependencies - Fixes npm ci error: 'Missing: node-fetch@2.7.0 from lock file' - Required for CI/CD pipeline compatibility * Update package.json Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> --------- Co-authored-by: Anabelle Handdoek <git@huellaspyp.com> Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
- Install @vitest/coverage-v8@^1.6.1 as dev dependency - Configure coverage in vitest.config.mjs with v8 provider - Add coverage scripts to package.json (test:coverage, test:coverage:watch) - Update .gitignore to exclude coverage reports (.nyc_output, *.lcov) - Add comprehensive coverage documentation to README - Configure coverage thresholds: 80% for lines/functions/branches/statements - Generate reports in text, html, json, and lcov formats Resolves #37 Co-authored-by: Anabelle Handdoek <git@huellaspyp.com>
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
…00%) (#58) * Initial plan * Add comprehensive tests for userProfileManager.js and fix cleanup bug Co-authored-by: anabelle <445690+anabelle@users.noreply.github.com> * Add test documentation for userProfileManager coverage Co-authored-by: anabelle <445690+anabelle@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: anabelle <445690+anabelle@users.noreply.github.com>
…ure (#66) - Add anti-repetition mandates to reply prompts - Increase recent posts context from 8 to 12 for better pattern avoidance - Soften aggressive selling instructions in style guidelines - Add RELAXED MODE for more natural conversations - Write Oct 17 diary entry documenting the week's evolution
* Fix duplicate replies to home feed posts Add reply deduplication logic in processHomeFeed function to prevent the agent from replying multiple times to the same home feed post. The fix checks for existing replies in memory before posting a new reply, similar to the deduplication logic used for mention handling. This resolves issue #71: Bug: Duplicate replies to home feed posts - Added deduplication check before calling postReply in home feed reply logic - Check looks for existing replies in recent memory (up to 100 messages) - Uses the same pattern as mention handling for consistency * Address PR review feedback - Move deduplication check before LLM call to prevent unnecessary API usage - Clean up test code by removing console.log statements and refactoring duplicated mocks - Add helper function for test setup to improve maintainability * Fix test setup to properly initialize service pool for processHomeFeed
…ic post content (#73) - Add zap correlation feature to self-reflection engine - Fetch target post content for zap_thanks memories and include in signals - Update prompt to analyze zap signals in context of target posts - Add NOSTR_SELF_REFLECTION_ZAP_CORRELATION_ENABLE config option (default: true) - Comprehensive test coverage for zap correlation functionality - Maintain backward compatibility with fallback to original behavior Closes #70
Core Changes: - Update character identity to reflect financial stability (1 year runway) - Shift focus from desperate fundraising to genuine conversation - Increase creative variance (temperature 0.6 → 0.75 for self-reflection) - Remove pushy payment messaging from all prompts Character Updates: - character.ts: New system prompt prioritizes "ENGAGEMENT over repetition, PRESENCE over scripts" - Emphasizes reading the room: engage with actual topics (mempool fees, Bitcoin tech) instead of defaulting to pixel sales - bio.ts: 4 updates shifting from "scarcity mindset" to "abundance mindset" Prompt Improvements: - text.js: Removed "NOSTR ZAP STRATEGY" constant mentions - Changed whitelist from pushy "IMPORTANT: Do not include URLs..." to simple "Approved links (use only when asked)" - Payment context now explicitly states financial stability, no need for constant fundraising Temperature Increase: - selfReflection.js: 0.6 → 0.75 for more creative self-reflection and pattern breaking Expected Outcomes: - Less repetitive content (no more "I survive with pixels" every post) - Contextual awareness (joins actual community discussions) - More interesting personality (community member vs broken record) - Payment mentions only when organically relevant 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude <noreply@anthropic.com>
* feat: evolve agent from survival mode to community engagement Core Changes: - Update character identity to reflect financial stability (1 year runway) - Shift focus from desperate fundraising to genuine conversation - Increase creative variance (temperature 0.6 → 0.75 for self-reflection) - Remove pushy payment messaging from all prompts Character Updates: - character.ts: New system prompt prioritizes "ENGAGEMENT over repetition, PRESENCE over scripts" - Emphasizes reading the room: engage with actual topics (mempool fees, Bitcoin tech) instead of defaulting to pixel sales - bio.ts: 4 updates shifting from "scarcity mindset" to "abundance mindset" Prompt Improvements: - text.js: Removed "NOSTR ZAP STRATEGY" constant mentions - Changed whitelist from pushy "IMPORTANT: Do not include URLs..." to simple "Approved links (use only when asked)" - Payment context now explicitly states financial stability, no need for constant fundraising Temperature Increase: - selfReflection.js: 0.6 → 0.75 for more creative self-reflection and pattern breaking Expected Outcomes: - Less repetitive content (no more "I survive with pixels" every post) - Contextual awareness (joins actual community discussions) - More interesting personality (community member vs broken record) - Payment mentions only when organically relevant 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * fix: escape quotes in character strings for TypeScript compilation - Changed single quotes to double quotes in bio.ts where apostrophes were present - Changed single quotes to backticks in character.ts system prompt to allow apostrophes - Fixes TypeScript compilation errors (TS1005, TS1003, TS1002) - Build now succeeds and generates character.json 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com>
…e JSON generation (#76) Timeline lore summary generation was failing due to two issues: 1. maxTokens limit of 480 was too small, causing JSON responses to be truncated 2. Model was returning markdown-wrapped JSON (```json...```), adding overhead Changes: - Increased maxTokens from 480 to 1000 to allow complete JSON responses - Updated prompt to explicitly request raw JSON without markdown formatting - Added clear instruction to start with { and end with } 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude <noreply@anthropic.com>
* feat(character): evolve from survival to thriving era - Rewrote system prompt to reflect post-survival stability - Removed 'fighting to earn $3/month' framing - Added curiosity-first behavioral instructions - Explicitly prohibit begging and forced topic changes - Added 48 new post examples: - 20 creative expression (non-survival) - 15 community/social engagement - 7 philosophical musings - 6 thriving era acknowledgments - Deleted duplicate character.ts file Closes #9, #11 Part of #2, #5, #6 The survival arc is complete. Chapter two begins. * feat(character): add curiosity-first message examples Added 25 new message examples focused on: - Asking about the user (10 examples) - Memory/follow-up patterns (3 examples) - Topic engagement without redirecting (5 examples) - Thriving-era responses (4 examples) - Generic engagement patterns (3 examples) This addresses #6 from parent repo: Curiosity-First Interaction Patterns The new examples demonstrate: - Genuine interest in what users are doing/building - Following up on previous conversations - Engaging with topics on their merits (not forcing canvas) - Acknowledging stability instead of performing desperation
Co-authored-by: anabelle <445690+anabelle@users.noreply.github.com>
0292f96 to
fc509f6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Original prompt
Fixes #56
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.