Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 14:16
    realaravinth opened #2216
  • 11:27

    github-actions[bot] on gh-pages

    Deploying to gh-pages from @ f… (compare)

  • 11:24
    robjtede synchronize #2215
  • 11:24

    robjtede on move-internal-err

    cleanup ws test (#2213) Merge branch 'master' into move… (compare)

  • 11:24

    robjtede on test_ws

    (compare)

  • 11:24

    robjtede on master

    cleanup ws test (#2213) (compare)

  • 11:24
    robjtede closed #2213
  • 11:19
    robjtede review_requested #2215
  • 11:19
    robjtede review_requested #2215
  • 11:19
    robjtede edited #2215
  • 11:17
    robjtede ready_for_review #2215
  • 11:17
    robjtede edited #2215
  • 11:16
    robjtede edited #2215
  • 11:16
    robjtede synchronize #2215
  • 11:16

    robjtede on move-internal-err

    update changelog (compare)

  • 11:13
    robjtede labeled #2215
  • 11:13
    robjtede labeled #2215
  • 11:13
    robjtede edited #2215
  • 11:12
    robjtede opened #2215
  • 11:12

    robjtede on move-internal-err

    alias body to anybody move internal error to actix-web (compare)

Henk Poley
@HenkPoley
Well, they are deleted.
Nikolay Kim
@fafhrd91
Did you try to get link from deleted issue and try yourself? Or you just like everyone else?
Henk Poley
@HenkPoley
After reading up on the issue a bit, this seems to be one of these things where you can tell rust 'trust me this unsafe-tagged code is going to be okay', and in general if you can proof that consumers of your API will never see the unsound behaviour, that is okay. People took issue that one unsafe part in Actix could be done in a safe way. But that part is in principle not broken, if everyone keeps paying attention while modifying Actix internal code.
I would recommend steering people towards forking and maintaining a separate patchset if they like, instead of seeding extra hostility.
Nikolay Kim
@fafhrd91
Nobody wants to do any work, they just prefer relies on others work
That is reality of open source
Henk Poley
@HenkPoley
btw, Deleting Github issues is one of the worst ways to handle it. The Gottman Institute has done research on that, and calls it 'stonewalling'. Any of these talks should be a decent explanation: https://www.youtube.com/results?search_query=gottman+institute+stonewalling
I kind of understand the difficulties of open source.
Nikolay Kim
@fafhrd91
It doesn’t matter already. It is not first time. Damage to reputation is done. It is time to move on to something else
Henk Poley
@HenkPoley
Cool, no need to detonate the project though. It seems work decently, trying to erlang-ify Rust.
Anyways, properly handling relationships always matters. Especially in open source.
Farkal
@Farkal
@shirshak55 do you have any code exemple ? How can the request handle without blocking the actix thread ?
Farkal
@Farkal
Should i use Actor ? I try to put heavy computing in an async fn (but i simulate heavy computing with thread::sleep(Duration::from_secs(5))) so i don't know if it represent real heavy computing) and the results are the same
Evgeniy Tatarkin
@estin
@Farkal try to use actix_web::web::block
When you make heavy computing inside async fn handler you can block to accept and process other requests until computing done.
Delegate heavy computing to another thread. Sorry I have not example...
Stefano Probst
@senden9
Hi all! I use actix/actix-rt. No actix-web. Is there a way to handle a Message in an asynchronous way? Like let handle actix::Handler return a future.
Background: I need to spawn a external process in a Actor that i want to pack into a tokio::task::spawn_blocking.
Farkal
@Farkal
@estin Thank you very much ! It work ! but i read that it was using actix thread and could crash actix is it true ? -> https://stackoverflow.com/questions/58766267/should-diesel-be-run-using-a-sync-actor-actix-webwebblock-or-futures-cpupoo
This guy said that it should be better to use futures-cpupool
Evgeniy Tatarkin
@estin
@Farkal I don't believe about crashing actix by this way) But you must not believe me too ))) I'm not have enough experience. Check source code of actix-threadpoll wich used for ::block() and don't wary to use it right now.
Martin Schöpf
@csaf4370
@fafhrd91 i hope you reconsider your move to delete actix(-web) ... I totally understand your reasons, but I would just hope that this awesome project could be kept alive. You (and the other contributors) did an astonishing job. Thank you
context https://github.com/actix/actix-web ... Actix prject postmortem
Rob Ede
@robjtede
^^^ I whole-heartedly second this. You onboarded dozens of people to the Actix contributors group not that long ago. We're willing to take more leading roles in the evolution of this fantastic project.
Nikolay Kim
@fafhrd91
No one showed any sign of project architecture understanding
Rob Ede
@robjtede
Maybe this is the kick we need.
tbh, i can see the actix ecosystem being forked under a different name or living on here with different maintainers
Nikolay Kim
@fafhrd91
I am highly skeptical about fork viability
Rob Ede
@robjtede
how come, because people don't understand it really ?
Shirshak
@shirshak55
honestly actix is very good framework and it supports lot of stuff like routing, database, graphql etc.
willlllllio
@willlllllio
@fafhrd91 hi, just wanted to say thank you for everything you've done and I wish you the best of luck in the future!
Shirshak
@shirshak55
Yea I cannot imagine how much effort has to be done to make actix this much better.
Thanks for everything you have given to us. Best of luck for future endeavors
Joshua Barretto
@zesterer
@fafhrd91 I want to echo the sentiment of others: when I first found out that Actix was created by just one core developer, I was shocked. It's some seriously impressive work and it would be a shame for Actix to vanish from the entire ecosystem entirely.
If I may, I think taking some time off is a good idea. Burnout is really unpleasant, and taking the time to put things into perspective really helps. I'm currently on a burnout hiatus from Veloren. I founded the project and wrote most of the initial architecture. As the community grew, I found it very difficult to let go of control of the codebase: but I've since realised that delegating decisions was the best possible choice for the project, community, - and me.
Shirshak
@shirshak55
Actix is used for very good purpose also https://github.com/dessalines/lemmy.
changlizhi
@changlizhi
我是中文社区的rust新手,谢谢哥们你开发的actix-web,这是rust社区的一个好项目。在这里问候一下那些对这个项目口吐芬芳的人的母亲,免费用一个软件还哔哔个啥,不喜欢不用就行了别他妈像个傻逼一样指点江山。英语看得我似懂非懂的,不过不管啥原因都希望作者继续下去,rust开源社区才是初级阶段,会出现各种问题,坚持就是胜利!另外建议作者您创建一个组织一起做这个项目,一个人撑不住的时候互相支持就能坚持下去
Farkal
@Farkal
@fafhrd91 Yes thank you for your work ! I wanted you to know that actix make each of my days at work ! I started rust less than a year ago and i am making a tile service software (like this one https://github.com/nasa-gibs/onearth ), i needed to be as fast as possible (because we have lot of heavy computing like reprojection...) and i choose actix. From that day i have never be desapointed by this awesome lib. You helped me to prove to all the company how rust can be powerfull as a web server (everybody speak about the tile server now and ask me new features). I didn't find any lib that have so much features and so good doc and that compile with rust stable (hello rocket). Look at this https://github.com/flosse/rust-web-framework-comparison you have the only lib that implements all the features ! It's not like in js were there is ton of libs doing the same thinks a bit differently. Here we speak about core features and actix is the only lib that check all the boxes :)
Please reconsider you decision because I am sure there will be a fork and of course some lib can have bad reputation (it's easy to criticize) but it change over the time and all my team have very good opinion of your work !
If you really don't want to continue the actix adventure you can add the best contributors to maintainers but i really don't think deleted this is the solution. One day you will show this project to your child and you could really say that you make the world better !
Evgeniy Tatarkin
@estin
@zesterer YES! I was shocked too. Too many useful features created by one person in production quality. So sad about Rust community or may be about whole opensource community.
Boscop
@Boscop
@fafhrd91 Thanks for your hard work on actix. I don't think its reputation is damaged too badly (at least not in the eyes of the actual actix users who like it). Now that you have everyone's attention, it's a huge opportunity for you. I think the reputation can be fixed by taking this opportunity (while the attention is still on you) to create a positive vision for the future of actix. It's not too late!
Darin Gordon
@Dowwie
:thumbsup:
Oron Sharabi
@oronsh
@fafhrd91 thank you for everything. The end of actix is a great loss for the entire rust ecosystem and the community. It had been one of the greatest and most promising rust projects! I hope you will rethink of it... there are a lot of people (like me) who based their entire projects on actix... I am super sad with that :( but I do understand you and respect your decision... hope to hear from you again!
enzious
@enzious
I know you're upset, and in a lot of ways you're justified, but people have invested time into Actix in their own way. I've spent 2 years developing a project on Actix. The least you could do is leave it up. This leaves me just completed dumbfounded. What the fuck have I been doing? What will I do now?
tglman
@tglman
@fafhrd91 Thank you for all your work so far and your active support for questions and issues, you did a great job, If you choose to move on we will be sad, but we will understand
enzious
@enzious
I'll probably be fine, Actix works well enough for me as it is. I just worry about the future. Seems like amid tensions things got a little too rash.
Jonathas Conceição
@Jonathas-Conceicao
@fafhrd91 Thank you very much for all the work you've done in the Actix ecosystem. I have been using it for the most of my projects on the past year and the project has never disappointed me. Burnout if a really bad thing and you need to take your time from open software do it, if and when you decide to comeback I'm sure the Rust community will welcome you back.
fbucek
@fbucek
@fafhrd91 Thank you for you work. I have made monitoring tool for tablets ( room booking ) at spaceti.com I have used version 1.0 and move it fo 2.0 recently with no problem. It was pleasure to work with actix.
rustrust
@rustrust
@fafhrd91 thanks for your hard work on actix-web, it is the best web framework in any language i have used
Nikolay Kim
@fafhrd91
Repos are still available, anyone can clone them
Tinco Andringa
@tinco
hey @fafhrd91 sorry to see you've had such a hard time, just want to let you know that I think your attitude towards achieving optimal design is awesome, and I really hope you won't delete the repositories from your personal account because they are a real achievement I feel you should be proud of
Yuri Titov
@ytitov
I did not realize this was being coded by one person. First I'd like to say that I am grateful for the library, and I think it has a great API. It must be overwhelming to do this much work and get criticized for your design decisions (of which I know nothing about). My suggestion is to take a breath and ask for help from the community for help with maintaining this project, and move away from the central role as the sole architect/maintainer (if this is what you wish). I can see how that can be extremely stressful. I am hoping someone will step up from the community. I've been pushing for rust at my company and this will not help. I hope we can all figure this out, and very soon. Again, I want to express that I have been very happy with actix and I am hoping for a good resolution for this project to continue on.
Nikolay Kim
@fafhrd91
I hope people won’t harass pyo3 project, because I started it
Tinco Andringa
@tinco
I don't think he should step away from being the central leader, he's driven actix with his vision, if he was not the leader of the project it would not have become what it is today