Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error: failed to update card #27

Open
iKrushYou opened this issue Apr 23, 2024 · 4 comments
Open

error: failed to update card #27

iKrushYou opened this issue Apr 23, 2024 · 4 comments

Comments

@iKrushYou
Copy link

iKrushYou commented Apr 23, 2024

Hey, currently getting an error when trying to create a card from the user interface

uhppoted-httpd  | 2024/04/23 00:58:29 WARN   423137505  failed to update card 1234567

I went to cards, clicked +, added a user name, card number, end date, and hit check. then got this in the console. I haven't been able to find a working combination (I've tried others). I can confirm that users created in the stock web UI and the CLI show up eventually.

as a comparison, I set up the uhppoted-cli as well and was able to successfully add a card that way.

running using docker compose, with image

ghcr.io/uhppoted/httpd   latest    e47723788c1c   3 weeks ago   30.3MB

What kind of information would be helpful to provide?

@iKrushYou iKrushYou changed the title failed to update card error: failed to update card Apr 23, 2024
@uhppoted
Copy link
Owner

uhppoted commented Apr 23, 2024

I've been able to reproduce this on my own system and it doesn't appear to be any of the problems I thought it could be - let me look into it and get back to you..

@iKrushYou
Copy link
Author

Thanks for such prompt responses! Do you happen to have a discord server or a less formal place to chat? I have minor questions but don't want to keep raising GitHub issues

@uhppoted
Copy link
Owner

Ah - got it! You need to provide both a card start date and a card end date (From and To) for the controller to accept a card.

The UI doesn't require a card start and end date because you might be e.g. preloading a set of cards which will get assigned to actual people for actual use later - it's only showing up as a problem now in uhppoted-httpd because of a recent system-wide change to make card date/time handling more robust.

I'm going to have to think about this one a bit because automatically assigning a default card start and end date is potentially problematic (e.g. a temporary access card may be unexpectedly valid) - but hopefully the workaround will get you up and running for now.

re. less formal place to chat. Most people seem to just use the overarching uhppote discussions area - which is quite nice because it created a centralised, searchable repository for ad hoc information and ideas. Discussions are enabled for this repo too if you prefer something more topic specific.

@iKrushYou
Copy link
Author

thank you! I found the start / end date requirements interesting. I would want all of the cards I am entering to have an infinite or indeterminate end date. Especially since there doesn't seem to be a bulk way to extend card end dates. We're going to have a couple hundred cards saved into the system that will all be active "indefinitely." I could set the end date myself to something very far out, but also I wouldn't want to rely on future admins to have to know what to set the end date to

I'd likely want to make a change to create a default "MAX" end date

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

No branches or pull requests

2 participants