quality/testdays-web
9
0
Fork 0
Code Issues 18 Pull requests 1 Projects Releases Packages Wiki Activity Actions

New event in TestDayApp gives error #8

New issue
Closed
opened 2020-02-03 03:23:54 +00:00 by pnemade · 8 comments
pnemade commented 2020-02-03 03:23:54 +00:00
Copy link

I am trying to create new event in testday app page. If I enter URL with "https://" then this testday app says use "http://" only. If I use URL with "http://" then it gives "Internal Server Error".

Can someone please check if one can successfully create the testday event?

I am trying to create new event in testday app page. If I enter URL with "https://" then this testday app says use "http://" only. If I use URL with "http://" then it gives "Internal Server Error". Can someone please check if one can successfully create the testday event?
kparal commented 2020-02-03 15:28:25 +00:00
Owner
Copy link

@frantisekz @jskladan Can somebody figure out what's wrong? Thanks.

@frantisekz @jskladan Can somebody figure out what's wrong? Thanks.
jskladan commented 2020-02-03 15:34:07 +00:00
Contributor
Copy link

@pnemade Could you please be more specific? What is the metadata URL you are trying to submit to the app?

@pnemade Could you please be more specific? What is the metadata URL you are trying to submit to the app?
pnemade commented 2020-02-03 16:36:49 +00:00
Author
Copy link

https://fedoraproject.org/wiki/Test_Day:2020-03-10_I18N_TestdayApp_Metadata

This link is giving me error message
Testday URL must start with 'http'

https://fedoraproject.org/wiki/Test_Day:2020-03-10_I18N_TestdayApp_Metadata This link is giving me error message `Testday URL must start with 'http' `
jskladan commented 2020-02-03 17:10:19 +00:00
Contributor
Copy link

Thanks for the Info.

First of all, let me say that the error message is rather cryptic, and I understand why you were confused by it (so was I, for a bit).

The problem is not in the http(s) in the metadata url, but in the links you use in the metadata. You are using the wiki-style urls in the metadata, but the app is rather basic, and can't really parse those.
Please make sure to have all urls on the page in the 'expanded' F32 i18n test day;https://fedoraproject.org/wiki/Test_Day:2020-03-10_I18N_Test_Day format instead of the wiki one F32 i18n test day; [[Test_Day:2020-03-10_I18N_Test_Day]]

I'm closing the issue now, but feel free to contact me directly, if you run into any additional issues.

Thanks for the Info. First of all, let me say that the error message is rather cryptic, and I understand why you were confused by it (so was I, for a bit). The problem is not in the http(s) in the metadata url, but in the links you use in the metadata. You are using the wiki-style urls in the metadata, but the app is rather basic, and can't really parse those. Please make sure to have **all urls on the page** in the 'expanded' `F32 i18n test day;https://fedoraproject.org/wiki/Test_Day:2020-03-10_I18N_Test_Day` format instead of the wiki one `F32 i18n test day; [[Test_Day:2020-03-10_I18N_Test_Day]]` I'm closing the issue now, but feel free to contact me directly, if you run into any additional issues.
jskladan commented 2020-02-03 17:10:19 +00:00
Contributor
Copy link

Metadata Update from @jskladan:

  • Issue close_status updated to: Invalid
  • Issue status updated to: Closed (was: Open)
**Metadata Update from @jskladan**: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
pnemade commented 2020-02-04 02:54:48 +00:00
Author
Copy link

Thank you.
My bad actually. Some contributor actually changed expanded form to short form in the old F31 testday metadata page and I blindly copied previous page to this new F32 page and did further changes to it.

Thank you. My bad actually. Some contributor actually changed expanded form to short form in the old F31 testday metadata page and I blindly copied previous page to this new F32 page and did further changes to it.
kparal commented 2020-02-04 09:14:30 +00:00
Owner
Copy link

Is there some documentation/help page where we could highlight this issue, so that people won't trip over it again?

Is there some documentation/help page where we could highlight this issue, so that people won't trip over it again?
jskladan commented 2020-02-04 09:49:53 +00:00
Contributor
Copy link

@kparal yes, there is documentation:
https://fedoraproject.org/wiki/QA:TestdayApp
and linked from that page is:
https://fedoraproject.org/wiki/QA:TestdayAppMetadataDescription

But that won't protect you from a copy-paste error, I think.

I agree, that the error message(s) could/should be way more comprehensive, but let's have that conversation elsewhere: #9

@kparal yes, there is documentation: https://fedoraproject.org/wiki/QA:TestdayApp and linked from that page is: https://fedoraproject.org/wiki/QA:TestdayAppMetadataDescription But that won't protect you from a copy-paste error, I think. I agree, that the error message(s) could/should be way more comprehensive, but let's have that conversation elsewhere: #9
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
develop
fix/97-automated-tests-issues
fix/93-app-revision-in-pod
staging
master
feature/fasusername
feature/faslogin_as_db_username
v1.1
v1.0
0.0.4
Labels
Clear labels   
Closed As
Duplicate
Closed with the reason of Duplicate

  
Closed As
Fixed
Closed with the reason of Fixed

  
Closed As
Invalid
Closed with the reason of Invalid

  
easyfix

   
enhancement
  
Backlog Status
Needs Review
Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  
Backlog Status
Ready
Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and can be worked on immediately when capacity is available.

  
chore

Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

  
documentation

Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

  
points
01
A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down.

  
Priority
Critical
This is for work that is urgent and of critical importance and so and must be addressed immediately with a higher priority than all other work, even if not originally planned for the current sprint.

  
Priority
High
This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
Priority
Low
This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
Priority
Medium
This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
Sprint Status
Blocked
Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

  
Sprint Status
Done
Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
Work items currently being worked on by a team member. Active development, research, or implementation is happening.

  
Sprint Status
Review
Work items that are complete but need review, testing, or approval before being marked as done.

  
Sprint Status
To Do
Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  
Technical Debt

Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

  
Work Item
Bug
Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic
Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  
Work Item
Spike
Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

  
Work Item
Task
Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

  
Work Item
User Story
User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

No labels
Closed As
Duplicate
Closed As
Fixed
Closed As
Invalid
easyfix
enhancement
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
quality/testdays-web#8
No description provided.