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.

Sign up for GitHub

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

Jump to bottom

On initial probe creation "probe_created_at" field is null and probe_modified_at is not null #241

Open
vqmarkman opened this issue Sep 5, 2023 · 2 comments
Open

On initial probe creation "probe_created_at" field is null and probe_modified_at is not null #241

vqmarkman opened this issue Sep 5, 2023 · 2 comments

Comments

@vqmarkman
Copy link
Contributor

It seems to me that it should be other way around.

Screenshot 2023-09-05 at 3 39 10 PM
@jinfengni
Copy link
Contributor

Thanks for finding this bug. @vqmarkman ! This is a bug I introduced in the pr for #28 .

I added this PROBE_CREATE_AT column to probes table, but did not change the other places to handle this new column.

vqmarkman added a commit to vqmarkman/OpsCenter that referenced this issue Sep 6, 2023
@vqmarkman
Issue sundeck-io#152: probes unit tests.
78666a8 
            - renamed one of the tests to reflect what it actually does.
	    - when  sundeck-io#241 is fixed, tests will need to be adjusted as well.
@vqmarkman
Copy link
Contributor Author

When this bug is fixed, please adjust test/unit/test_probe_procs.py (it will fail)

vqmarkman added a commit that referenced this issue Sep 6, 2023
@vqmarkman
Issue #152: probes unit tests. (#253)
bd7bb02 
- renamed one of the tests to reflect what it actually does.
	    - when  #241 is fixed, tests will need to be adjusted as well.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
OpsCenter Project
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jinfengni @vqmarkman