Invalid Time Value

[lukepolo]

I am currently running into an error

vendor.9ab39863a68553288dec.js:2 RangeError: Invalid time value
    at V (vendor.9ab39863a68553288dec.js:2)
    at G (main.5c5b0f89ccd1be55a12f.js:1)
    at X (main.5c5b0f89ccd1be55a12f.js:1)
    at ni (vendor.9ab39863a68553288dec.js:2)
    at Bl (vendor.9ab39863a68553288dec.js:2)
    at ku (vendor.9ab39863a68553288dec.js:2)
    at bu (vendor.9ab39863a68553288dec.js:2)
    at yu (vendor.9ab39863a68553288dec.js:2)
    at du (vendor.9ab39863a68553288dec.js:2)
    at vendor.9ab39863a68553288dec.js:2

We should probably not render the whole page cause of an invalid time.

[felixmosh]

Can you elaborate please?

[lukepolo]

Sure, im not 100% sure what happened, (hence few details). I got into a bad state where I was having too many connections on my queue and I started to have lots of delayed / waiting jobs.

This is much as I have to go off, feel free to close, but I figured we could at least catch the exception and gracefully fail so we can view which jobs are the culprits.

[felixmosh]

Hi, I've saw the same issue, it happened when I've added a delayed task (using the example) since the endpoint config, the delay at the server side comes as a string (which is invalid).

I've made a PR to fix the example.

Let me know if you have the same / similar issue.

[Jivings]

Also getting this error when I have stalled jobs 👍

[felixmosh]

@Jivings how can I reproduce this issue? can you provide a small reproduction repo?

[Jivings]

I'm not certain, but it was definitely happening when I had some stalled jobs. But also could have been a 2020/2021 issue becuase stalled jobs were from before the year date line 😅

Now it's not happening, so not sure how to reproduce.

[Jivings]

Just got it now and it looks like one of the Jobs in the response doesn't have any data so I guess that will do it!

[felixmosh]

@Jivings thank you, but how this can happen?

[leorcvargas]

Just got it now and it looks like one of the Jobs in the response doesn't have any data so I guess that will do it!

I'm also facing this problem, but I'm not sure what makes it happens

[deanshub]

Hey man,
first of all, awesome project, helped me a-lot!
I tried version 1.4.1 but I still get the exception and the white screen

Anything I can do to help?

[felixmosh]

@deanshub I'm glad it helps you!

I've tested this case (timestamp = null), and every thing is working as expected

Can you add here an entire queue object, so I will test with it? or any other method that I will be able to reproduce it on my machine :]

[deanshub]

{
  "stats": {
    "redis_version": "4.0.11",
    "used_memory": "1001928",
    "mem_fragmentation_ratio": "6.81",
    "connected_clients": "7",
    "blocked_clients": "0",
    "total_system_memory": "16521273344"
  },
  "queues": [
    {
      "name": "plugin-execution",
      "counts": {
        "waiting": 0,
        "active": 0,
        "completed": 0,
        "failed": 1,
        "delayed": 0,
        "paused": 0
      },
      "jobs": [
        {
          "id": "b8676711-f817-4f34-a588-e59aeae80f47",
          "timestamp": null,
          "processedOn": 1614203068243,
          "finishedOn": 1614203068358,
          "progress": 0,
          "attempts": 1,
          "delay": 0,
          "failedReason": "Cloning into '.'...\nremote: Repository not found.\nfatal: repository 'https://x-access-token:[email protected]/undefined/undefined.git/' not found\n",
          "stacktrace": [
            "Error: Cloning into '.'...\nremote: Repository not found.\nfatal: repository 'https://**:**@github.com/undefined/undefined.git/' not found\n\n    at toError (/app/node_modules/simple-git/promise.js:90:14)\n    at /app/node_modules/simple-git/promise.js:61:36\n    at Git.<anonymous> (/app/node_modules/simple-git/src/git.js:214:18)\n    at Function.Git.fail (/app/node_modules/simple-git/src/git.js:1475:18)\n    at fail (/app/node_modules/simple-git/src/git.js:1433:20)\n    at /app/node_modules/simple-git/src/git.js:1442:16\n    at processTicksAndRejections (internal/process/task_queues.js:97:5)"
          ],
          "opts": {
            "attempts": 1,
            "delay": 0,
            "timestamp": 1614370058912
          },
          "data": {},
          "name": "__default__",
          "returnValue": null
        }
      ],
      "readOnlyMode": false
    }
  ]
}

[felixmosh]

I've tried your json, and it loads as expected, (pay attention that the start time is 1970, since timestamp field is null)

[deanshub]

Sorry, GAing issues, thanks!

[felixmosh]

Sorry, GAing issues, thanks!

So, it works? :)

[deanshub]

So, it works? :)

Perfectly

[deanshub]

I want to add A PR but not sure how it would best be implemented

[deanshub]

I'll open a new issue so we can discuss it

[PlkMarudny]

I just add a repeatable job and it goes to the "DELAYED" tab, clicking on it produces:

Data:

{
  "data": {
    "marketCode": "XADS",
    "marketName": "Abu Dhabi Securities Exchange",
    "tickerCode": "ADAVIATI",
    "type": "MINMAX",
    "data": {
      "timePeriod": {
        "id": 3,
        "value": "52 weeks"
      },
      "option": true
    },
    "destinations": [
      {
        "id": 1,
        "handle": "@first"
      }
    ]
  },
  "returnValue": null
}

Options:

{
  "attempts": 1,
  "delay": 164999195991598050,
  "repeat": {
    "count": 1,
    "key": "__default__:6920637091843936256::60000",
    "every": "60000",
    "jobId": "6920637091843936256"
  },
  "jobId": "repeat:254c393220ad65e02a77708fe6e39344:165000846000060000",
  "timestamp": 1650008461958,
  "prevMillis": "165000846000060000"
}

[PlkMarudny]

A job submitted with 'cron' option however, does not produce an error:

{
  "attempts": 1,
  "delay": 182326,
  "repeat": {
    "count": 1,
    "key": "__default__:6920639842099400704:::*/5 * * * *",
    "cron": "*/5 * * * *",
    "jobId": "6920639842099400704"
  },
  "jobId": "repeat:b9f81f6ee398a0ca527fad568357688f:1650009300000",
  "timestamp": 1650009117674,
  "prevMillis": 1650009300000
}

[PlkMarudny]

OK, "every" should be a number, not a string. This is the source of an error.

[felixmosh]

@PlkMarudny if this is a new bug, pls open a new ticket with reproduction steps

[PlkMarudny]

No, not really. Just a comment to the previous one.

…

On Fri, 15 Apr 2022, 12:57 Felix Mosheev, ***@***.***> wrote: @PlkMarudny <https://github.com/PlkMarudny> if this is a new bug, pls open a new ticket with reproduction steps — Reply to this email directly, view it on GitHub <#203 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABBI25234C7RY6Z5P4OKMODVFEVPNANCNFSM4VBHRSKQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>