why can't login ? myself compile and run

[pkptzx]

i download u code , compile release and run ,
signed up is ok.
click "signed in", but can't login, it always redirect to login page.

and , found err by signed up , use name : 123456

thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: SkyError(UnexpectedDataType)', src/handlers/signup.rs:88:41        
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace 

[ohsayan]

Hey, which version of Skytable are you using locally? Jotsy depends on the latest version (the one in the next branch, and also the one available with the latest docker image for Skytable).

[hohowt]

me,too. but I installed it through the commands in README

[ohsayan]

Looks like this is the offending line:

jotsy/src/handlers/signup.rs

Line 88 in 6d17a9b

con.switch(crate::TABLE_AUTH).await.unwrap();

So the switch is causing a panic. Let me investigate this

[ohsayan]

@5waker Couldn't repro this locally. Which tag of jotsy are you running? Try running docker-compose images from the jotsy directory

sayan@sayan-workstation:~/jotsy$ docker-compose images
  Container      Repository      Tag       Image Id       Size  
----------------------------------------------------------------
jotsy_app_1     ohsayan/jotsy   latest   b7ce5a361dad   132.1 MB
jotsy_skydb_1   skytable/sdb    latest   588363ebf129   137.4 MB

[hohowt]

@ohsayan

Container      Repository      Tag       Image Id       Size  
----------------------------------------------------------------
jotsy_app_1     ohsayan/jotsy   latest   0efaed216bc2   133.1 MB
jotsy_skydb_1   skytable/sdb    latest   806c014286f6   137.5 MB```

[ohsayan]

@5waker run this:

sudo docker pull ohsayan/jotsy && sudo docker-compose up -d

[ohsayan]

This should update your image

[hohowt]

ok, let me try

[ohsayan]

Hey, @pkptzx, it seems like I can reproduce this, even with the latest tag 1797097a9515. Working on a fix now

[ohsayan]

This has been fixed in #8. If you still have issues, feel free to re-open the issue

[pkptzx]

Because cookie set "Secure", the login is always directed to the login page without https.

can u customer set ? when test/dev in locally

[ohsayan]

@pkptzx If I understand you correctly, you want to be able to disable the setting of the Secure attribute for Set-Cookie? Why would you want to do that, however?

Quoting from MDN docs, using the Secure attribute only works with HTTPS, with the exception for localhost:

A cookie with the Secure attribute is only sent to the server with an encrypted request over the HTTPS protocol. It's never sent with unsecured HTTP (except on localhost), which means man-in-the-middle attackers can't access it easily. Insecure sites (with http: in the URL) can't set cookies with the Secure attribute. However, don't assume that Secure prevents all access to sensitive information in cookies. For example, someone with access to the client's hard disk (or JavaScript if the HttpOnly attribute isn't set) can read and modify the information.

[pkptzx]

It doesn't matter, I solve it myself. Since I am remote development is not local access.

👀　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　　👀

[ohsayan]

Great! If you have anything else to report, don't hesitate to create an issue :)