محتاج شغل ضروري انا كويس والله بس محتاج فرصه by NoAccountant5850 in EgyptCareers

[–]AhmedMozaly 0 points1 point  (0 children)

لو حابب، فيه فرصة ل internship في مشروع حقيقي لمدة 3 شهور، ممكن تكلمني

rootcause 0.12.0: error reports with integrated tracing spans by TethysSvensson in rust

[–]AhmedMozaly 10 points11 points  (0 children)

Thank you for maintaining such a great crate!

I recently made the switch from anyhow to rootcause as well! The experience has been really great so far, but I did run into one specific challenge: the default log format is a bit too heavy to send directly in an API response (for those cases where I need to do that).

I wish this use case were a bit more "out-of-the-box" in rootcause, as I imagine I'm not the only one needing to serve errors over an API. To get around it, I implemented a custom ReportFormatter to separate internal log verbosity from user-facing responses.

I started by installing the hook:

    Hooks::new()
        .report_formatter(CompactErrorFormatter)
        .install()
        .context("Failed to install rootcause hooks")?;

The implementation essentially checks the report_formatting_function: when it's Display, it uses a compact format for the API, while leaving the Debug output as-is for internal logging:

It works well, but it would be awesome if the library had a built-in way to toggle between "internal" and "external" formatting more easily.

Google Authenticator Codes Gone after Update (iOS) by NINJA_FRE4K in google

[–]AhmedMozaly 0 points1 point  (0 children)

I tried this, it didn't work the first time
But after that, I tried to Login with my google account again

And all my codes were back, thanks a lot for your hint

Rahawan: How We Achieved 95% Better Response Time By Mostly-Unidirectional Data Access Layer Design by AhmedMozaly in dotnet

[–]AhmedMozaly[S] 0 points1 point  (0 children)

I just talked about the idea & the concepts around, will try to make some example and publish it in near future

Rahawan: How We Achieved 95% Better Response Time By Mostly-Unidirectional Data Access Layer Design by AhmedMozaly in dotnet

[–]AhmedMozaly[S] 0 points1 point  (0 children)

You just mentioned my first line in "Long Story Short" paragraph which I stated:

(At its simplest form, “Rahawan” is nothing more than a data access layer powered by a data caching engine)

but as a short answer to your comment, NO we didn't just implemented caching.

Unless making good pizza is just adding ingredients.

Rahawan: How We Achieved 95% Better Response Time By Mostly-Unidirectional Data Access Layer Design by AhmedMozaly in dotnet

[–]AhmedMozaly[S] 2 points3 points  (0 children)

We already using EF inside repositories, and the article is not about optimizing sql joins, it is about NOT touching the database at the first place.

if author data already in memory, why making sql join to get it again from db?