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

Server-side Swift / Linux support #49

Closed
rexmas opened this issue Apr 29, 2023 · 4 comments
Closed

Server-side Swift / Linux support #49

rexmas opened this issue Apr 29, 2023 · 4 comments

Comments

@rexmas
Copy link

rexmas commented Apr 29, 2023

Please add support for server-side swift / linux. Thank you.

@nikz
Copy link
Collaborator

nikz commented May 15, 2024

hi @rexmas, what would you need in order for this to work?

@rexmas
Copy link
Author

rexmas commented May 15, 2024

Please see this thread https://forums.swift.org/t/backtraces-in-swift/61736
for this library https://github.com/swift-server/swift-backtrace
though swift 5.9 has built in backtracing as shown in the readme of that github
and I believe this evolution proposal will improve the api in short time https://github.com/apple/swift-evolution/blob/main/proposals/0419-backtrace-api.md

overall at least to support swift 5.9 on the server, the raygun library needs to be completely implemented in standard swift (no objective-c) and rely on built-in backtracing for captures so it seems.

@sumitramanga
Copy link
Collaborator

Hi @rexmas !

Thank you for your request :) We really appreciate it when folk point out where our provider can be improved.

We won't be taking on this in the near future as we have some awesome upcoming work but I can add it to our product feedback tool for our team to look into priortising. Feel free to also make noise via our forums as well - https://raygun.com/forums

Thank you again,

Sumitra Manga
Team Lead, Senior Engineer @ Raygun

@sumitramanga
Copy link
Collaborator

Hi team,

We've decided to close this issue out for now since this is an 'eventually we'll do but not for while' task. It’ll also come automatically with the change to Swift overall.

We haven't forgotten about it and will keep in mind!

@rexmas - If you have anything else in mind, please do make us aware!

Thank you again,
Sumitra

@sumitramanga sumitramanga closed this as not planned Won't fix, can't repro, duplicate, stale Jun 30, 2024
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

3 participants