You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When a seeding log is created using a sub-request to set the log_category the timestamp and purchase_date are set to 01/20/1970 instead of the current date.
To Reproduce
The following code uses a farm instance to create a seeding log with the log_category set to seeding_tray, which exists in the taxonomy_term--log_category vocabulary of the farmOS instance being used:
The output in the second case has the correct timestamp as well as quite a bit of additional other information suggesting that these two types of creation are being handled differently.
Expected behavior
The log created with the subrequest should have a timestamp of the current date and time.
Screenshots
Here are the two logs created as shown on the farmOS "logs" page:
Desktop (please complete the following information):
OS: [Linux]
Browser [firefox]
Additional context
The code samples were run in Node 18.17.1
The text was updated successfully, but these errors were encountered:
Describe the bug
When a seeding log is created using a sub-request to set the
log_category
thetimestamp
andpurchase_date
are set to 01/20/1970 instead of the current date.To Reproduce
The following code uses a
farm
instance to create a seeding log with thelog_category
set toseeding_tray
, which exists in thetaxonomy_term--log_category
vocabulary of the farmOS instance being used:The output generated is:
This can be compared to the results when creating a seeding log not using a subrequest:
Which produces the output:
The output in the second case has the correct
timestamp
as well as quite a bit of additional other information suggesting that these two types of creation are being handled differently.Expected behavior
The log created with the subrequest should have a
timestamp
of the current date and time.Screenshots
Here are the two logs created as shown on the farmOS "logs" page:
Desktop (please complete the following information):
Additional context
The code samples were run in Node 18.17.1
The text was updated successfully, but these errors were encountered: