Skip to content

Conversation

@jxd23
Copy link

@jxd23 jxd23 commented Nov 12, 2025

Context

Carnegie Mellon University has a large population of international students and students whose first language is not English. Currently, NodeBB does not support non-English posts and assumes all users’ posts are in English. Non-English users cannot fully participate in the Q&A forum because their posts may not be understood by the majority English-speaking community; specifically, faculty cannot assist students who ask questions in their native languages due to this communication barrier. Users are left to manually translate content, which is a hassle for users and discourages engagement and connection. To promote inclusivity and community, the platform needs a fast, reliable, accurate translation system.

Changes in the Code

UI Integration: Referenced a lot of file changes from class:
CMU-313/NodeBB#460

Testing
Verified translation requests locally using the LLM translator microservice to ensure the button appeared.
Tested with both English and non-English sample posts, with the hard-coded responses and not.

image image

Issues

Minor issue with English posts:
image

Timing:
Wait times on posts range from about 7 seconds to 20 seconds, based on individual local testing.

@github-actions
Copy link

✅ Artillery Performance Test Results - PASSED

Note: This is an informational check only. Results do not block PR merging.

Load Test Summary

  • Total Scenarios: 600
  • Completed: 600
  • Failed: 0
  • Total Requests: 1800
  • Error Rate: 0.00%

Response Times

  • Median: 3ms
  • P95: 5ms
  • P99: 8.9ms
  • Max: 21ms

Threshold Analysis (Advisory)

  • Error Rate: 0.00% ✅ (recommended: <5%)
  • P99 Latency: 8.9ms ✅ (recommended: <1000ms)

Performance metrics look great!

HTTP Response Codes
  • 200: 1800 requests

@github-actions
Copy link

✅ Artillery Performance Test Results - PASSED

Note: This is an informational check only. Results do not block PR merging.

Load Test Summary

  • Total Scenarios: 600
  • Completed: 600
  • Failed: 0
  • Total Requests: 1800
  • Error Rate: 0.00%

Response Times

  • Median: 3ms
  • P95: 5ms
  • P99: 10.1ms
  • Max: 38ms

Threshold Analysis (Advisory)

  • Error Rate: 0.00% ✅ (recommended: <5%)
  • P99 Latency: 10.1ms ✅ (recommended: <1000ms)

Performance metrics look great!

HTTP Response Codes
  • 200: 1800 requests

@coveralls
Copy link

coveralls commented Nov 12, 2025

Pull Request Test Coverage Report for Build 19309111224

Details

  • 19 of 25 (76.0%) changed or added relevant lines in 4 files are covered.
  • 6 unchanged lines in 1 file lost coverage.
  • Overall coverage decreased (-0.02%) to 75.991%

Changes Missing Coverage Covered Lines Changed/Added Lines %
src/translate/index.js 12 18 66.67%
Files with Coverage Reduction New Missed Lines %
src/activitypub/index.js 6 48.48%
Totals Coverage Status
Change from base Build 18962382418: -0.02%
Covered Lines: 24214
Relevant Lines: 30047

💛 - Coveralls

@rebeccals05 rebeccals05 marked this pull request as ready for review November 12, 2025 05:36
…changes work (I think), with Ollama installed via CLI in the hosted ssh (team17@17313-team17)
@github-actions
Copy link

✅ Artillery Performance Test Results - PASSED

Note: This is an informational check only. Results do not block PR merging.

Load Test Summary

  • Total Scenarios: 600
  • Completed: 600
  • Failed: 0
  • Total Requests: 1800
  • Error Rate: 0.00%

Response Times

  • Median: 3ms
  • P95: 5ms
  • P99: 10.1ms
  • Max: 42ms

Threshold Analysis (Advisory)

  • Error Rate: 0.00% ✅ (recommended: <5%)
  • P99 Latency: 10.1ms ✅ (recommended: <1000ms)

Performance metrics look great!

HTTP Response Codes
  • 200: 1800 requests

@github-actions
Copy link

✅ Artillery Performance Test Results - PASSED

Note: This is an informational check only. Results do not block PR merging.

Load Test Summary

  • Total Scenarios: 600
  • Completed: 600
  • Failed: 0
  • Total Requests: 1800
  • Error Rate: 0.00%

Response Times

  • Median: 2ms
  • P95: 4ms
  • P99: 10.1ms
  • Max: 21ms

Threshold Analysis (Advisory)

  • Error Rate: 0.00% ✅ (recommended: <5%)
  • P99 Latency: 10.1ms ✅ (recommended: <1000ms)

Performance metrics look great!

HTTP Response Codes
  • 200: 1800 requests

@github-actions
Copy link

✅ Artillery Performance Test Results - PASSED

Note: This is an informational check only. Results do not block PR merging.

Load Test Summary

  • Total Scenarios: 600
  • Completed: 600
  • Failed: 0
  • Total Requests: 1800
  • Error Rate: 0.00%

Response Times

  • Median: 3ms
  • P95: 5ms
  • P99: 12.1ms
  • Max: 24ms

Threshold Analysis (Advisory)

  • Error Rate: 0.00% ✅ (recommended: <5%)
  • P99 Latency: 12.1ms ✅ (recommended: <1000ms)

Performance metrics look great!

HTTP Response Codes
  • 200: 1800 requests

@github-actions
Copy link

✅ Artillery Performance Test Results - PASSED

Note: This is an informational check only. Results do not block PR merging.

Load Test Summary

  • Total Scenarios: 600
  • Completed: 600
  • Failed: 0
  • Total Requests: 1800
  • Error Rate: 0.00%

Response Times

  • Median: 3ms
  • P95: 4ms
  • P99: 8.9ms
  • Max: 26ms

Threshold Analysis (Advisory)

  • Error Rate: 0.00% ✅ (recommended: <5%)
  • P99 Latency: 8.9ms ✅ (recommended: <1000ms)

Performance metrics look great!

HTTP Response Codes
  • 200: 1800 requests

@github-actions
Copy link

✅ Artillery Performance Test Results - PASSED

Note: This is an informational check only. Results do not block PR merging.

Load Test Summary

  • Total Scenarios: 600
  • Completed: 600
  • Failed: 0
  • Total Requests: 1800
  • Error Rate: 0.00%

Response Times

  • Median: 2ms
  • P95: 4ms
  • P99: 10.1ms
  • Max: 24ms

Threshold Analysis (Advisory)

  • Error Rate: 0.00% ✅ (recommended: <5%)
  • P99 Latency: 10.1ms ✅ (recommended: <1000ms)

Performance metrics look great!

HTTP Response Codes
  • 200: 1800 requests

@github-actions
Copy link

✅ Artillery Performance Test Results - PASSED

Note: This is an informational check only. Results do not block PR merging.

Load Test Summary

  • Total Scenarios: 600
  • Completed: 600
  • Failed: 0
  • Total Requests: 1800
  • Error Rate: 0.00%

Response Times

  • Median: 3ms
  • P95: 5ms
  • P99: 8.9ms
  • Max: 26ms

Threshold Analysis (Advisory)

  • Error Rate: 0.00% ✅ (recommended: <5%)
  • P99 Latency: 8.9ms ✅ (recommended: <1000ms)

Performance metrics look great!

HTTP Response Codes
  • 200: 1800 requests

Copy link

@heesunp heesunp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello, I tested the button locally and it seems to work properly! However, it should be noted that the translation process takes a while to run.

Copy link

@rebeccals05 rebeccals05 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great! I tested it locally, and it runs well. The only thing I would consider changing is to try and get the LLM to respond to English text properly. Ignoring the longer wait times, the translation from non-English works well!

@rebeccals05 rebeccals05 merged commit 2ba86d4 into main Nov 12, 2025
4 checks passed
@rebeccals05
Copy link

Not working in deployment
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants