Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / ntex-rs/ntex issues and pull requests
#505 - Cpu affinity support for server workers
Pull Request -
State: closed - Opened by fafhrd91 17 days ago
- 1 comment
#505 - Cpu affinity support for server workers
Pull Request -
State: closed - Opened by fafhrd91 17 days ago
- 1 comment
#504 - Allow to access io write destination buffer
Pull Request -
State: closed - Opened by fafhrd91 27 days ago
- 1 comment
#503 - Clippy fixes
Pull Request -
State: closed - Opened by fafhrd91 about 1 month ago
- 1 comment
#502 - Retry middleware
Pull Request -
State: closed - Opened by fafhrd91 about 1 month ago
#501 - Future on-drop helper
Pull Request -
State: closed - Opened by fafhrd91 about 1 month ago
#500 - Add EitherService/EitherServiceFactory
Pull Request -
State: closed - Opened by fafhrd91 about 1 month ago
- 1 comment
#499 - Clippy fixes
Pull Request -
State: closed - Opened by fafhrd91 about 1 month ago
- 1 comment
#498 - Fix status badge
Pull Request -
State: closed - Opened by fafhrd91 about 1 month ago
#497 - Incorrect shared mutable state example at website ntex.rs
Issue -
State: closed - Opened by justforcomment about 1 month ago
- 7 comments
#496 - Feature/runtime macro panic
Pull Request -
State: closed - Opened by jamescarterbell about 2 months ago
- 3 comments
#495 - Relax runtime requirements
Pull Request -
State: closed - Opened by fafhrd91 about 2 months ago
- 1 comment
#494 - Enable rustls/std feature
Pull Request -
State: closed - Opened by fafhrd91 about 2 months ago
- 1 comment
#493 - Fix error log
Pull Request -
State: closed - Opened by fafhrd91 about 2 months ago
- 1 comment
#492 - An error occurred during the upgrade
Issue -
State: closed - Opened by WuJiY about 2 months ago
- 3 comments
#491 - Add workflow job which adds basic checks for build failures
Pull Request -
State: closed - Opened by metent about 2 months ago
- 2 comments
#490 - REUSEPORT and single-thread
Issue -
State: closed - Opened by alidehghan about 2 months ago
- 1 comment
#489 - Tune shutdown logging
Pull Request -
State: closed - Opened by fafhrd91 about 2 months ago
- 1 comment
#488 - Compress middleware Brotli compression not working
Issue -
State: closed - Opened by JeanRomain about 2 months ago
- 2 comments
#487 - #[tokio::main] and #[ntex::main] conflict
Issue -
State: closed - Opened by alidehghan about 2 months ago
#485 - Remove Unpin requirements for Arbiter::spawn()
Pull Request -
State: closed - Opened by fafhrd91 2 months ago
#484 - Notify Specific WebSocket Clients from REST API Using Ntex Framework
Issue -
State: open - Opened by anchalshivank 2 months ago
#482 - Better error handling
Pull Request -
State: closed - Opened by fafhrd91 2 months ago
- 1 comment
#481 - Added Service::poll() method
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#480 - Add time::Sleep::elapse() method
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#479 - Depend on individual compio packages
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#478 - Fix handling unconsumed payload in h1 dispatcher #477
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#477 - BUG: `TestServer`'s request fails in a very specific way: post().send_body() -> response.body() -> post().send_json()
Issue -
State: closed - Opened by fadeevab 3 months ago
- 2 comments
#474 - Move body related types from ntex::http
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#473 - Disable default features for compio runtime
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#472 - App state is not configured, to configure use App::state()
Issue -
State: closed - Opened by anchalshivank 3 months ago
- 6 comments
#471 - Update to compio 0.13
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#470 - Prep util release
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#469 - ntex-util: debug print
Issue -
State: closed - Opened by leon3s 3 months ago
- 2 comments
#468 - How does a custom tokio runtime work with ntex::rt::System::new().run_local()?
Issue -
State: closed - Opened by svanharmelen 3 months ago
- 2 comments
#467 - Use Cell instead of RefCell for timer
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#466 - Add client timeout test
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#465 - Is the docs up to date ?
Issue -
State: closed - Opened by call-me-q 3 months ago
- 4 comments
#465 - Is the docs up to date ?
Issue -
State: closed - Opened by call-me-q 3 months ago
- 4 comments
#465 - Is the docs up to date ?
Issue -
State: closed - Opened by call-me-q 3 months ago
- 4 comments
#465 - Is the docs up to date ?
Issue -
State: closed - Opened by call-me-q 3 months ago
- 4 comments
#465 - Is the docs up to date ?
Issue -
State: closed - Opened by call-me-q 3 months ago
- 4 comments
#465 - Is the docs up to date ?
Issue -
State: closed - Opened by call-me-q 3 months ago
- 4 comments
#465 - Is the docs up to date ?
Issue -
State: closed - Opened by call-me-q 3 months ago
- 4 comments
#465 - Is the docs up to date ?
Issue -
State: closed - Opened by call-me-q 3 months ago
- 4 comments
#465 - Is the docs up to date ?
Issue -
State: closed - Opened by call-me-q 3 months ago
- 4 comments
#465 - Is the docs up to date ?
Issue -
State: closed - Opened by call-me-q 3 months ago
- 4 comments
#464 - Run un-readiness check in separate task
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#464 - Run un-readiness check in separate task
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#464 - Run un-readiness check in separate task
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#464 - Run un-readiness check in separate task
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#464 - Run un-readiness check in separate task
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#464 - Run un-readiness check in separate task
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#464 - Run un-readiness check in separate task
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#464 - Run un-readiness check in separate task
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#464 - Run un-readiness check in separate task
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#464 - Run un-readiness check in separate task
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#464 - Run un-readiness check in separate task
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#464 - Run un-readiness check in separate task
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#463 - Check service readiness once per decoded item
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#463 - Check service readiness once per decoded item
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#463 - Check service readiness once per decoded item
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#463 - Check service readiness once per decoded item
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#463 - Check service readiness once per decoded item
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#463 - Check service readiness once per decoded item
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#463 - Check service readiness once per decoded item
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#463 - Check service readiness once per decoded item
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#463 - Check service readiness once per decoded item
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#463 - Check service readiness once per decoded item
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#462 - Fix un-needed wakeups for unready future
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#462 - Fix un-needed wakeups for unready future
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#462 - Fix un-needed wakeups for unready future
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#462 - Fix un-needed wakeups for unready future
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#462 - Fix un-needed wakeups for unready future
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#462 - Fix un-needed wakeups for unready future
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#462 - Fix un-needed wakeups for unready future
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#462 - Fix un-needed wakeups for unready future
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#462 - Fix un-needed wakeups for unready future
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#462 - Fix un-needed wakeups for unready future
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#462 - Fix un-needed wakeups for unready future
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#462 - Fix un-needed wakeups for unready future
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#462 - Fix un-needed wakeups for unready future
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#461 - Last update spikes WebSocket CPU usage to 100%
Issue -
State: closed - Opened by JeanRomain 3 months ago
- 2 comments
#461 - Last update spikes WebSocket CPU usage to 100%
Issue -
State: closed - Opened by JeanRomain 3 months ago
- 2 comments
#461 - Last update spikes WebSocket CPU usage to 100%
Issue -
State: closed - Opened by JeanRomain 3 months ago
- 2 comments
#461 - Last update spikes WebSocket CPU usage to 100%
Issue -
State: closed - Opened by JeanRomain 3 months ago
- 2 comments
#461 - Last update spikes WebSocket CPU usage to 100%
Issue -
State: closed - Opened by JeanRomain 3 months ago
- 2 comments
#461 - Last update spikes WebSocket CPU usage to 100%
Issue -
State: closed - Opened by JeanRomain 3 months ago
- 2 comments
#461 - Last update spikes WebSocket CPU usage to 100%
Issue -
State: closed - Opened by JeanRomain 3 months ago
- 2 comments
#461 - Last update spikes WebSocket CPU usage to 100%
Issue -
State: closed - Opened by JeanRomain 3 months ago
- 2 comments
#461 - Last update spikes WebSocket CPU usage to 100%
Issue -
State: closed - Opened by JeanRomain 3 months ago
- 2 comments
#461 - Last update spikes WebSocket CPU usage to 100%
Issue -
State: closed - Opened by JeanRomain 3 months ago
- 2 comments
#461 - Last update spikes WebSocket CPU usage to 100%
Issue -
State: closed - Opened by JeanRomain 3 months ago
- 2 comments
#461 - Last update spikes WebSocket CPU usage to 100%
Issue -
State: closed - Opened by JeanRomain 3 months ago
- 2 comments
#461 - Last update spikes WebSocket CPU usage to 100%
Issue -
State: closed - Opened by JeanRomain 3 months ago
- 2 comments
#460 - Compilation error while upgrading from 2.7 to 2.8
Issue -
State: closed - Opened by leon3s 3 months ago
- 22 comments
#460 - Compilation error while upgrading from 2.7 to 2.8
Issue -
State: closed - Opened by leon3s 3 months ago
- 22 comments
#459 - Do not rely on not_ready(), always check service readiness
Pull Request -
State: closed - Opened by fafhrd91 3 months ago
- 1 comment
#458 - Periodically check readiness
Pull Request -
State: closed - Opened by fafhrd91 4 months ago
- 1 comment
#457 - Optimize service readiness handling
Pull Request -
State: closed - Opened by fafhrd91 4 months ago
- 1 comment