Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot select "No field type" in Data Referece #5276

Closed
joshuashort opened this issue Jun 6, 2017 · 14 comments · Fixed by #22367
Closed

Cannot select "No field type" in Data Referece #5276

joshuashort opened this issue Jun 6, 2017 · 14 comments · Fixed by #22367
Assignees
Labels
.Frontend Organization/Data Reference Priority:P3 Cosmetic bugs, minor bugs with a clear workaround .Reproduced Issues reproduced in test (usually Cypress) Type:Bug Product defects
Milestone

Comments

@joshuashort
Copy link
Contributor

  • Your browser and the version: Safari 10.1.1

  • Your operating system: macOS 10.12.5

  • Your databases: MariaDB

  • Metabase version: 0.24.1

  • Metabase hosting environment: Docker

  • Metabase internal database: H2

  • Repeatable steps to reproduce the issue
    -- Admin user at http://localhost:3000/reference/databases
    -- Select a database
    -- Click "Tables in this database"
    -- Select a table
    -- Click "Fields in this table"
    -- If "Field type" is already blank
    --- Selecting another type works
    --- Selecting "No field type" works
    -- If "Field type" isn't blank
    --- Selecting "No field type" leaves the previous field type instead of the expected behavior

@mazameli
Copy link
Contributor

mazameli commented Jun 6, 2017

I was unable to reproduce this bug on either Safari or Chrome. It's possible it has been fixed since version 0.24.1.

@mazameli mazameli closed this as completed Jun 6, 2017
@joshuashort
Copy link
Contributor Author

Ok.. but this occurred on the official Docker image of Metabase. Was it not reproducible in that environment?

@joshuashort
Copy link
Contributor Author

I can't see what I'm doing wrong -- I was using metabase/metabase:latest, and I tried removing the image, thinking it might be out of sync.. looking on hub.docker.com, :latest is still set to v0.24.1. I manually set to the latest docker hub tag (i.e. v0.24.2), and the issue is still there. Maybe I'm reporting this in the wrong place, and maybe it's actually a different problem?

@joshuashort
Copy link
Contributor Author

Same problem with metabase/metabase-head:

Thanks for using Metabase!
You're on version v0.25.0-snapshot
Built on 2017-05-11
Branch: master
Hash: 2222f41

(can't select "No field type" on a field that already has a type in the Data Reference 'tab')

I'm just running docker run -d -p 3000:3000 --name metabase -v "$(pwd)"/data:/metabase-data -e MB_DB_FILE=/metabase-data/metabase.db metabase/metabase-head

@mazameli mazameli reopened this Jun 7, 2017
@mazameli
Copy link
Contributor

mazameli commented Jun 7, 2017

Cool, I'll reopen this, but I'll need some help from the other @metabase/core-developers to see if this is a Docker-specific or MariaDB-specific issue, because I'm still unable to reproduce this.

@joshuashort
Copy link
Contributor Author

Thanks! I just noticed this issue (#5280) about the version on DockerHub. Time for me to dig a little more.

@Varunram
Copy link
Contributor

Varunram commented Jun 8, 2017

@joshuashort @mazameli Turns out I am able to reproduce the error on OSX 10.12.5. I used the default Metabase h2 db and am running the Metabase Docker image on Docker Edge. Funny thing is even after changing the field type 2-3 times, it defaults to the previous value if we select "No Field Type" in the end.

@joshuashort
Copy link
Contributor Author

I'm also getting this on Docker on Ubuntu 16.04.2 with Metabase v0.24.1 (haven't tried v0.24.2 or :head) on this server yet.

@salsakran
Copy link
Contributor

@Varunram + @joshuashort can you check the JS and server logs for errors? Is the field being set or is there an error on that call? should be something like PUT /api/metadata/field/1111 or something similar.

@joshuashort
Copy link
Contributor Author

joshuashort commented Jun 12, 2017

@salsakran I don't see any browser console messages while trying to select "No field type"; and there's never a PUT call on the server log; the selection doesn't happen on the client side. I'll check in Chrome.. (edit: same behavior)

@Varunram
Copy link
Contributor

@salsakran Nope, logs look clean on my side. What do you suspect the issue is though?

@flamber flamber added Organization/Data Reference Priority:P3 Cosmetic bugs, minor bugs with a clear workaround Type:Bug Product defects and removed .Unable to Reproduce labels Aug 20, 2020
@ranquild ranquild self-assigned this May 2, 2022
@ranquild
Copy link
Contributor

ranquild commented May 2, 2022

Checked docker images for both v0.42 and v.043-rc1 and couldn't reproduce the issue.

@ranquild ranquild closed this as completed May 2, 2022
@ranquild ranquild modified the milestones: 0.43, 0.42 May 2, 2022
@flamber flamber removed this from the 0.42 milestone May 2, 2022
@flamber
Copy link
Contributor

flamber commented May 2, 2022

This is not fixed:

Screencast-2022-05-02_13.42.08.mp4

@flamber flamber reopened this May 2, 2022
@ranquild ranquild self-assigned this May 3, 2022
This was referenced Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
.Frontend Organization/Data Reference Priority:P3 Cosmetic bugs, minor bugs with a clear workaround .Reproduced Issues reproduced in test (usually Cypress) Type:Bug Product defects
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants