Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Feb 20 23:24

    s-panferov on v3.6.0

    (compare)

  • Feb 20 23:23

    s-panferov on master

    (cargo-release) version 3.6.0 (cargo-release) start next deve… (compare)

  • Feb 20 23:22

    s-panferov on master

    Update dependencies (#71) (compare)

  • Feb 20 23:22
    s-panferov closed #71
  • Feb 20 23:22
    s-panferov closed #70
  • Feb 16 16:30
    glebpom commented #71
  • Jan 25 17:27
    DiD92 opened #19
  • Jan 20 08:13
    izolyomi commented #70
  • Jan 09 16:23
    nickray closed #18
  • Jan 09 16:23
    nickray commented #18
  • Jan 08 19:38
    nickray opened #18
  • Dec 16 2020 15:46
    agavrilov opened #71
  • Dec 16 2020 00:08
    agavrilov commented #70
  • Dec 14 2020 04:03
    JordiPolo opened #70
  • Dec 13 2020 23:13
    jayaddison commented #14
  • Dec 13 2020 20:19

    s-panferov on v3.5.0

    (compare)

  • Dec 13 2020 20:19

    s-panferov on master

    (cargo-release) version 3.5.0 (cargo-release) start next deve… (compare)

  • Dec 13 2020 20:17

    s-panferov on v2.1.0

    (compare)

  • Dec 13 2020 20:17

    s-panferov on master

    (cargo-release) version 2.1.0 (cargo-release) start next deve… (compare)

  • Dec 13 2020 20:15

    s-panferov on master

    add defaults handling (#69) * … (compare)

jaredmdobson
@jaredmdobson
@s-panferov rustless looks incredible man!! Thanks for making it!!
Lukas Kalbertodt
@LukasKalbertodt
Hi I have a stupid question: How should one use versioning? I mean... if I have two version, should I create two Apis with Api::build (for example) and specify different versions in the Api builder? I'm really unsure...
Stanislav Panferov
@s-panferov
@LukasKalbertodt if you have two versions you can mount two APIs to the Root API.
And yes, you need to create two separate API's with different versions.
Lukas Kalbertodt
@LukasKalbertodt
@s-panferov Ok thanks! Being curious: So when using Versioning::Path, there is no difference between using two Apis and using two Namespaces, right? But yeah thanks and keep up the great work ;-)
Stanislav Panferov
@s-panferov
There is a semantic difference between them. And also it gives you the way to define different error-handling logic at an API level using error_formatter
Stanislav Panferov
@s-panferov
@LukasKalbertodt I will appreciate it if you send me your feedback about Rustless after some time of usage.
Lukas Kalbertodt
@LukasKalbertodt
@s-panferov I haven't really looked at error handling yet... I will absolutely send you some feedback!
Milan van Schaik
@milanvanschaik
Hey guys! I'm trying to get started with rustless but I get some errors. I'm new in the Rust world but it looks really interesting. Do I get the errors because I run a 'too new' version of Rust? rustless/rustless#37
Stanislav Panferov
@s-panferov
There are some errors in rustless deps now.
Lukas Kalbertodt
@LukasKalbertodt
Does rustless build with beta?
Lukas Kalbertodt
@LukasKalbertodt
Well ... it does not. It doesn't build with the nightly either... I think I'll try to fix it..
Lukas Kalbertodt
@LukasKalbertodt
I gave up (I actually got valico compiling with nightly, but the tests are failing, if anyone is interested). Please fix rustless for beta ASAP _
Håkon Lerring
@Hakon
i'm experiencing some issues with response time jitter when running a simple serial benchmark
99% of the requests run with 0 ms response times but the last 1% has > 10 seconds response time
sometimes i'm just getting a timeout
Stanislav Panferov
@s-panferov
Could you pleas publish the code?
Mike Lubinets
@mersinvald

Hello. Please guide me how to add cookies to server's response.
I trying to add cookies as it's done in "Secure Example" in GitHub README.md

endpoint.handle(|mut client, params| {
    {
        let has_cookies = match client.request.find_cookie_jar() {
            Some(_) => true,
            None => false
        };

        let cookies = if has_cookies {
            println!("Found cookies");
            client.request.cookies()
        } else {
            println!("Creating new cookie jar");
            client.request.store_cookie_jar(CookieJar::new(b"f8a9eaf1ecfedfd3e5b749c58115441e"));
            client.request.cookies()
        };

        let signed_cookies = cookies.signed();
        let token_cookie = Cookie::new("token".to_owned(), 
                                        "todo_add_encrypted_tokens".to_owned());
        signed_cookies.add(token_cookie);
    }

    client.text("wrote cookies".to_owned())
})

When I run this code and try to get cookies with curl, I cannot see any :(

curl -d 'login_data' http://localhost:8080/api/signin -v  --cookie_jar cookies
*   Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to localhost (127.0.0.1) port 8080 (#0)
> POST /api/signin HTTP/1.1
> Host: localhost:8080
> User-Agent: curl/7.50.2
> Accept: */*
> Content-Type:application/json
> Content-Length: 38
> 
* upload completely sent off: 38 out of 38 bytes
< HTTP/1.1 200 OK
< Date: Wed, 02 Nov 2016 14:39:17 GMT
< Transfer-Encoding: chunked
< Content-Type: text/plain
< 
* Curl_http_done: called premature == 0
* Connection #0 to host localhost left intact
wrote cookies
> cat cookies
>
mmacedo
@mmacedoeu
hey guys
looking for how to enable CORS using rustless/iron/hyper any direction ?
mmacedo
@mmacedoeu
@s-panferov ping
xliiv
@xliiv
i'm running example from v0.9.0 and this line https://github.com/rustless/rustless/blob/master/examples/simple.rs#L148 is not running probabbly because it's blocked

however when i run

    fn hello_world(request: &mut Request) -> IronResult<Response> {           
        Ok(Response::with((iron::status::Ok, "hello")))                       
    }                                                                         
    let http_socket = "localhost:8000";                                       
    let _server = Iron::new(hello_world).http(http_socket).unwrap();          
    println!("serving http on {}", http_socket);

this works

could you tell me what's going on?
Michael Alexander
@beefsack
Hi all, absolutely fantastic framework! Am currently looking for advice on error handling though.
At the moment, whenever there is an internal error in my handlers, I wrap the error in ErrorResult and return that (using try! / ?), but it doesn't appear the errors get output anywhere
Is there some idiomatic way to handle internal errors in Rustless? I had trouble seeing examples in the sample code or docs, any advice would be hugely appreciated.
Also keen to hear about logging in general, would be great to see more verbose access logs output from the server process in development too.
Michael Alexander
@beefsack
To answer my own question: you need to actually include the log crate in your project for errors to be outputted in the server process, appears it might be an iron requirement. Might be worth adding to the docs if it isn't already.
Gustavo de la Cruz Tovar
@gusdelact
Could you provide a Cargo.toml for basic example, please
Dexter
@neoel
Hey, I'm wondering what the state of rustless is, I'm especially interested in valico. It hasn't been updated in a while, and doesn't reflect the changes to Serde
Dexter
@neoel
I've rewritten valico to use serde 1.0 and dropped jsonway as a dep. Tests pass. What would be a good way to publish this versoin of valico on crates.io?
Giancarlos Salas
@giansalex
rustless is dead.