Yuras: > In your particular case `ExceptT AppError IO` is almost certainly an anti-pattern though, because you never do exhaustive pattern matching on `AppError`. (In fact I didn’t find where you pattern match on it at all, but I didn’t dig too deep.) You’re right actually, I’m never pattern matching on the `AppError`. All it does at the moment is to print them as they are and calling `fail` so it prints `"user error: MyErrorType x y z"`. This was useful for me for debugging on the command line, but probably not for users (if there will ever be any). This reminds me I should handle those `AppError`s. For the CLI I suppose I could just map them to a nice error message. Later on, when I eventually add a web interface (that was the original idea behind the app - to be able to handle those playlists in a browser), I’ll handle them somehow..

Thank you all very much for your input, I did some refactoring using `ExceptT` as suggested, and it works just fine. Initially, I changed the types of my helper functions from `IO (Either AppError x)` to `ExceptT AppError IO x` in order to be able to rewrite the top-level functions as handleMakePlaylist opts = either print (putStr . renderResolvedPlaylist) =<< runExceptT do lib <- readLibFromFile_E opts.libraryPath mkPlaylistE lib opts.firstTrack opts.maxTracks (as initially suggested by @mixphix). But then I realized I could just keep the helper functions unchanged and use the `ExceptT` constructor to wrap my existing functions: handleMakePlaylist opts = either print (putStr . renderResolvedPlaylist) =<< runExceptT do lib <- ExceptT $ readLibFromFile_ opts.libraryPath ExceptT $ mkPlaylist lib opts.firstTrack opts.maxTracks So I continued refactoring the remaining functions ending up with a similar pattern, but had to fiddle a bit inserting `pure` here and there to make the types match handleShowLibrary o = either print (putStr . renderTrackCatalog) =<< runExceptT do lib <- ExceptT $ readLibFromFile_ o.libraryPath pure $ getTracks lib o.title o.key handleSuggestNextTracks o = either print (putStr . renderResolvedTransitions) =<< runExceptT do lib <- ExceptT $ readLibFromFile_ o.libraryPath ExceptT $ pure $ getTransitions lib o.track o.maxTracks (that’s because e.g. `getTracks` just returns a plain `MusicLibrary`, and `getTransitions` returns a `Either AppError [ResolvedTransition]` (no `IO` on that one!). How does this look? Any improvement/cleanup that can be done? Thanks again!

It's been a few days now. This is the error when loading some movie page: AppError: something went wrong at title (/opt/app/.next/server/pages/title/[titleId].js:1901:15) at process.processTicksAnd...

Facing the "Snapchat is a camera app" error on iPhone? Learn how to fix missing camera options, and resolve the issue with effective troubleshooting steps.

로이드, 할리팩스, 스코틀랜드 은행 등 영국의 대형 금융 기관들이 자사 모바일 앱의 대규모 접속 장애로 몸살을 앓고 있습니다. 일상적인 송금이나 결제를 하려던 수백만 명의 사용자가 갑작스러운 서비스 먹통으로 큰 불편을 겪었는데요. 이번 영국 은행 앱 오류 사태의 원인과 현장 상황을

liteflow10: > Is it okay to leave for example database errors as they are and send them straight to client? I've worked with 3rd party APIs that thought it would be completely fine to just dump a whole stack trace as part of an error response. I personally wouldn't do that and neither does crates.io, as far as I can tell: github.com/rust-lang/crates.io #### src/util/errors.rs `966666d3b` 129. impl<E: Error + Send + 'static> AppError for E { 130. fn response(&self) -> axum::response::Response { 131. error!(error = %self, "Internal Server Error"); 132. 133. sentry::capture_error(self); 134. 135. server_error_response(self.to_string()) 136. } 137. } github.com/rust-lang/crates.io #### src/util/errors.rs `966666d3b` 266. fn server_error_response(error: String) -> axum::response::Response { 267. ( 268. StatusCode::INTERNAL_SERVER_ERROR, 269. Extension(ErrorField(error)), 270. "Internal Server Error", 271. ) 272. .into_response() 273. }

I haven't checked the controllers or the middleware, but that's how I interpret the `util::errors` module, too. The helper functions rely on `CustomApiError`, which has a different response body than the generic implementation of `AppError` implementation for `E: Error`.

I was a bit confused with `dyn AppError` and implementations of `AppError` trait, but now i see how that works. Thank you for help <3

trait CopySliceIndex { } impl CopySliceIndex for std::ops::RangeTo<usize> {} trait CloneSliceIndex { } impl CloneSliceIndex for std::ops::RangeFrom<usize> {} pub(crate) trait StrIndexExt<I: std::slice::SliceIndex<str>> { fn get_or_err(&self, i: I) -> Result<&I::Output, AppError>; } impl<I: std::slice::SliceIndex<str> + std::fmt::Debug + Copy + CopySliceIndex> StrIndexExt<I> for str { fn get_or_err(&self, i: I) -> Result<&I::Output, AppError> { match self.get(i) { Some(v) => Ok(v), None => Err(AppError::StrSliceError { string: self.to_string(), slice: format!("{:?}", i), }), } } } impl<I: std::slice::SliceIndex<str> + std::fmt::Debug + CloneSliceIndex> StrIndexExt<I> for str { fn get_or_err(&self, i: I) -> Result<&I::Output, AppError> { match self.get(i) { Some(v) => Ok(v), None => Err(AppError::StrSliceError { string: self.to_string(), slice: "unknown".into(), }), } } } error[E0119]: conflicting implementations of trait `StrIndexExt<_>` for type `str` --> toytool/src/aux.rs:94:1 | 82 | impl<I: std::slice::SliceIndex<str> + std::fmt::Debug + Copy + CopySliceIndex> StrIndexExt<I> for str { | ----------------------------------------------------------------------------------------------------- first implementation here ... 94 | impl<I: std::slice::SliceIndex<str> + std::fmt::Debug + CloneSliceIndex> StrIndexExt<I> for str { | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ conflicting implementation for `str` Can I solve this? I want to impl two versions by `I: Copy` or not.

Hello team , I have created an sample private space using the gradio temple for chatbot (no change done), that space is working fine . I am trying to access it and display it in another public space but it gives an error like below This is the error in app where I am trying to access raise AppError( gradio_client.exceptions.AppError: The upstream Gradio app has raised an exception: ‘NoneType’ object is not subscriptable This is the message in the chatbot app message_serialized, history = self._process_msg_and_trim_history( File “/usr/local/lib/python3.10/site-packages/gradio/chat_interface.py”, line 605, in _process_msg_and_trim_history history = history_with_input[:-1] TypeError: ‘NoneType’ object is not subscriptable Code for chatbot app -default code from template for gradio Code for app which is trying to access import os import gradio as gr from huggingface_hub import login # Authenticate with Hugging Face HF_TOKEN = os.getenv(“HF_TOKEN”) # Set your Hugging Face token in the environment login(token=HF_TOKEN) # Authenticate using the token # Load the private Space (replace with the correct Space ID) with gr.Blocks() as demo: gr.load(“xxx/privateapp”,token=HF_TOKEN, src=“spaces”) demo.launch(show_error=True) I have also tried making private app public but still the same error You can also try this and it’s very easy to replicate Any help here would really help me Thank you

As the error message says, the author of Spaces has turned off debug messages, so we don’t know the exact cause. However, that error often occurs when the version of Gradio used in the Space is different from the version of Gradio installed on your local machine. Please try matching the version of Gradio on your local machine to the version used in the Space. huggingface.co ### levihsu/OOTDiffusion · The Gradio API isn't working. The Gradio API is giving error when trying to predict using the gradio client. It seems that the gradio app errors out whenever accessed via the given api definition. Should there be a change in th... pip install -U gradio

Either with AppError class for Dart.

For developers struggling to integrate different error types in Rust error handling, this article explains a cohesive design pattern using a custom `AppError` enum and the `From` trait.

TL;DR: Github repo. Are you tired of writing the same verbose error handling boilerplate in your Axum handler? Me too! 🙄By making a ritual AppError new type that wraps anyhow::Error and implementation IntoResponse , FromYou Can Ditch All Those Ugly Matching Statements and Adopt Beautiful ? Operator. Your handler functions go from dirty error-matching shenanigans to clean, readable code that automatically converts any errors into proper HTTP responses. It's like magic, but with more crabs! Lately I've been doing a lot of digging into Exum crates for one of my Rust web projects.

The Story Behind This Package Every time I started a new Node.js backend project, I found myself doing the same thing. npm install bcrypt npm install joi # copy-paste AppError class from some...

Define a base AppError class with a status code and error code, then subclass it for specific errors (NotFoundError, ValidationError, UnauthorizedError). Register a global error-handling middleware...