App crashes when accessing diff #415
Labels
No labels
⌚ Major-release
⌚ Minor-release
⚔️ Wontfix
⚙️ CI
⛏️ Breaking
✨ Duplicate
❌ Invalid
❓ Question
❤️ Support
➡️ Frontport
➡️ Needs-frontport
🔙 Backport
💭 Brainstorming
🐛 Bug
🔭 Cannot-reproduce
🧺 Cleanup
🧾 Confirmed
💬 Discussion
📄 Documentation
🎯 Enhancement
🩹 External-dependecy
📱 F-droid
🎉 Feature
👋 Good-first-issue
🤾 Google-play
🔙 Has-backport
🚀 Improvement
🚨 Investigate
🌠 Long-term
🔙 Needs-backport
🧺 Needs-cleanup
📡 Needs-feedback
📈 Performance
📌 Priority-critical
📌 Priority-high
📍 Priority-low
📍 Priority-medium
🥑 Ready
🪒 Refactor
🔙 Regression
📸 Release
🔒 Security
💡 Suggestion
🧪 Testing
🌐 Translation
💻 UI/UX
🪜 Upstream
🟦 Website
🙇♂️ Needs-help
🛰️ API-dependency
🛡️ Blocked
🏗️ Build
🗒️ Changelog
🗄️ Repository
🗓️ Summary
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: gitnex/GitNex#415
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
# What do you want to address?
(This step is required; examples are shown below)
# Describe your matter briefly
When accessing the diff of #413 the app closes. This is not related to the actual changes made in #413. It happens with the current master branch too.
I had a look at this, but i'm probably not doing well in fixing it. I think this is more likely something for @6543.
What did you expect? (Useful when addressing bugs)
(This step is optional)
Some additional details (Useful, when we are trying to reproduce a bug)
(This step is optional; an example is shown below)
We would appreciate some screenshots or stacktrace's, but this is also not required.
Thank you for your time.
https://github.com/go-gitea/gitea/issues/10921
https://github.com/go-gitea/gitea/issues/10933
if they are done we have a nice api to work with
@6543 I still feel like this issue is somehow related to the API.
There is no API for this yet. Diffs are rendered directly from the web.
@mmarif I think that there is a parsing error (or an error induced by the API), because it works for all other PRs.
Yes there is parsing error in the adapter. It's because the data is random and checking and parsing each bit is hard.
This can be closed (#537)