emcodem/ffastrans_webui

An advanced Webinterface for FFAStrans

ffastrans_webui's Issues

Data retention for metrics always defaults to 3

Hi,
I've tried to set the data retention for metrics to 30 days, but it always goes to 3 after I save and restart.

Tnx!

Clone scheduled jobs looses selected workflow

Prerelease for 1.4 (1.3.37) - web ui bugs

1. New icons looks like have rough edges (1080p default zoom):
   

2. CPU info on Farm Hosts page looks like that:
   

3. Help at "Scheduled Jobs [Help]" on "Scheduler" page leads to this:
   
   

4. No visible running jobs in list on "Job status" page:
   

Logs from .Webinterface_new\logs:
database.log
scheduler.log
webint.log

Metrics doesn't show up. Hosts are up and running.

Hi,
I've installed metrics server on main node, and metrics clients on all nodes (including the main node).
I've added hosts under the metrics setup.
And two of them are up, one is down (not sure why).

But, under the job and host metrics there's nothing.

Why?

Thanks!

API Error getting job details

When open job details, I get an error:
ERROR getting workflow of job 20200228-1522-1859-2dac-a15fadb8ee34, possibly FFASTRANS API is offline
If I run server app manually, the console error on Get Job Details is:
Locating file D:\FFAStrans\Processors\db\cache...
However I have my db at D:\INSTALL\FFAStrans1.0.0\Processors...

Did you find any solution for the repetition and hallucination issues in Purview Whisper Standalone for Windows

Hi,

I can't message you on GitHub, so I opened this issue.

Did you find any solution for the repetition and hallucination issues in Purview Whisper Standalone for Windows? You previously solved the issue for the 'const me' version, so have you tried fixing it for Purview Whisper Standalone for Windows?

Thanks alot

Prerelease for 1.4 (1.3.37) - errors in server.exe log

Have some errors in log.

1. "corrupt" directory is empty and "workflows" also didn't have json file in it called "corrupt". I think it tries to parse dir "corrupt" as json file:

2023-11-23 11:17:54: info: [webint]: Could not parse Json from file: \\nas08.tv.lan\FFAStrans\_FFAStrans_\Processors\db\configs\workflows\corrupt [Error: EISDIR: illegal operation on a directory, read] {
  errno: -4068,
  code: 'EISDIR',
  syscall: 'read'
}

2. this error is also common:

2023-11-23 11:00:37: error: [webint]: Error: ENOENT: no such file or directory, stat '\\nas08.tv.lan\FFAStrans\_FFAStrans_\Webinterface_new\alternate-server\css\override.css'

3. this one on startup of server.exe:

2023-11-23 11:25:20: info: [webint]: Internal Error getting Queued Jobs,  http://localhost:3003/tickets Error: connect ECONNREFUSED 127.0.0.1:3003
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16) {
  errno: -4078,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '127.0.0.1',
  port: 3003
}

4. this one on opening "Review Queue" page:

2023-11-23 11:32:14: debug: [webint]: get review called for:
2023-11-23 11:32:14: debug: [webint]: [Error: ENOENT: no such file or directory, scandir '\\nas08.tv.lan\FFAStrans\_FFAStrans_\Processors\db\cache\review\queue'] {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'scandir',
  path: '\\\\nas08.tv.lan\\FFAStrans\\_FFAStrans_\\Processors\\db\\cache\\review\\queue'
}
2023-11-23 11:32:14: error: [webint]: Trace: Global unexpected error:  Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
    at new NodeError (node:internal/errors:399:5)
    at ServerResponse.setHeader (node:_http_outgoing:663:11)
    at ServerResponse.header (\\nas08.tv.lan\FFAStrans\_FFAStrans_\Webinterface_new\rest_service\node_modules\express\lib\response.js:771:10)
    at ServerResponse.send (\\nas08.tv.lan\FFAStrans\_FFAStrans_\Webinterface_new\rest_service\node_modules\express\lib\response.js:170:12)
    at ServerResponse.json (\\nas08.tv.lan\FFAStrans\_FFAStrans_\Webinterface_new\rest_service\node_modules\express\lib\response.js:267:15)
    at Object.get (\\nas08.tv.lan\FFAStrans\_FFAStrans_\Webinterface_new\rest_service\api\controllers\review.js:44:26) {
  code: 'ERR_HTTP_HEADERS_SENT'
}
    at process.<anonymous> (\\nas08.tv.lan\FFAStrans\_FFAStrans_\Webinterface_new\server.js:56:13)
    at process.emit (node:events:513:28)
    at emit (node:internal/process/promises:149:20)
    at processPromiseRejections (node:internal/process/promises:283:27)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:32)
2023-11-23 11:32:14: error: [webint]: Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
    at new NodeError (node:internal/errors:399:5)
    at ServerResponse.setHeader (node:_http_outgoing:663:11)
    at ServerResponse.header (\\nas08.tv.lan\FFAStrans\_FFAStrans_\Webinterface_new\rest_service\node_modules\express\lib\response.js:771:10)
    at ServerResponse.send (\\nas08.tv.lan\FFAStrans\_FFAStrans_\Webinterface_new\rest_service\node_modules\express\lib\response.js:170:12)
    at ServerResponse.json (\\nas08.tv.lan\FFAStrans\_FFAStrans_\Webinterface_new\rest_service\node_modules\express\lib\response.js:267:15)
    at Object.get (\\nas08.tv.lan\FFAStrans\_FFAStrans_\Webinterface_new\rest_service\api\controllers\review.js:44:26)

Logs from .\Webinterface_new\logs:
database.log
scheduler.log
webint.log