Checkin time always show 12AM

[szalayzoli11]

Debug mode

• I have enabled debug mode
• I have read checked the Common Issues page

Describe the bug

When you try to check in an asset the dashboard always show 12AM checkin time

Reproduction steps

...

Expected behavior

show correct check in time

Screenshots

No response

Snipe-IT Version

5.4.1; 6.0

Operating System

win

Web Server

apache2

PHP Version

7.4

Operating System

No response

Browser

No response

Version

No response

Device

No response

Operating System

No response

Browser

No response

Version

No response

Error messages

No response

Additional context

No response

[john159753]

I can confirm I see this issue as well.
Version v5.4.1 - build 6746
MariaDB v10.7
PHP v7.4

According to the action_logs table - it seems like only the "checkin from" action that is not recording time data in the "action_date" field.

Let me know if I can provide more detail!

[szalayzoli11]

thx I have an suspicion, that someone play with the github contents also.. :( I know huge task check the all code, but that is a strange thing, that something workable, and after few days i see something changed a little and the same version generate this errors... john159753 ***@***.***> (időpont: 2022. ápr. 6., Sze, 16:11) ezt írta:

I can confirm I see this issue as well. Version v5.4.1 - build 6746 MariaDB v10.7 PHP v7.4 According to the action_logs table - it seems like only the "checkin from" action that is not recording time data in the "action_date" field. Let me know if I can provide more detail! — Reply to this email directly, view it on GitHub <#10866 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APYAXWC36OVPO2WVDKPMIG3VDWLR3ANCNFSM5RPASXAA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Tisztelettel: Szalay Zoltán

[snipe]

thx I have an suspicion, that someone play with the github contents also.. :(

I don't know what that means - all of our changes are public. https://github.com/snipe/snipe-it/commits/master

I know huge task check the all code, but that is a strange thing, that something workable, and after few days i see something changed a little and the same version generate this errors...

We push changes often and only tag a release once every few weeks or so (if that). I don't think there's anything nefarious happening here.

Can anyone reproduce this on the demo? https://demo.snipeitapp.com (admin/password).

@inietov - can you take a peek?

GitHub

Commits · snipe/snipe-it

A free open source IT asset/license management system - Commits · snipe/snipe-it

Snipe-IT Asset Management Demo

[szalayzoli11]

Yes that was teprictable on demo version also! Az iPhone-omról küldve

…

2022. ápr. 7. dátummal, 15:14 időpontban snipe ***@***.***> írta:  thx I have an suspicion, that someone play with the github contents also.. :( I don't know what that means - all of our changes are public. https://github.com/snipe/snipe-it/commits/master I know huge task check the all code, but that is a strange thing, that something workable, and after few days i see something changed a little and the same version generate this errors... We push changes often and only tag a release once every few weeks or so (if that). I don't think there's anything nefarious happening here. Can anyone reproduce this on the demo? https://demo.snipeitapp.com (admin/password). @inietov - can you take a peek? GitHub Commits · snipe/snipe-it A free open source IT asset/license management system - Commits · snipe/snipe-it Snipe-IT Asset Management Demo — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.

[snipe]

@inietov @Godmartinz Two things here:

1. I can reproduce this on develop and master.

master:

This artifact seems to happen when we clear out the "checkin date" field or let the system input it. (I'd expect 12:00 if you set a checkin date there, since we don't know what time, but if we're just using "now" as the checkin date time, it should honor the current date and time.)

2. On develop, we may have introduced a new bug.

Same issue exists with checkin time, but also we're adding extra entries into the action_logs table here for each of the side-effects:

I'm not sure what changed, but can you two work together (via slack or however) to see what might be happening here?

Thanks!