waynezhang / foto Goto Github PK

Here's a weird one, obviously a user error here but I ran into a problem where one of my sections would refuse to appear in a grid layout. All the images would appear full-width in a one-wide list, if that makes sense. I tracked it down to the problem being a duplicated slug identifier for two sections in my TOML, renaming one of them caused the issue to go away.

Naturally slugs ought to be unique and this is technically a user error, maybe some error reporting during building would be enough to address this already, but I figured it's worth reporting here nonetheless.

So the reproduction steps as far as I can tell are:

• Make two sections
• Set their slug names to identical text
• Add layout.minColumn or more images to each section
• The first section defined in the TOML file should appear correctly, the second one will not have a grid layout at all and simply show up as a list of images.

Let me know if you'd need any further information!

I would like to try foto. Can you make a Windows binary?

Hey- I really like this minimal set-up and am trying to get a super simple 'upload from iphone' workflow for a trip log going. I ran into a problem though; the rotation information that gets encoded in the jpegs doesn't seem to be respected? I'm seeing photos taken in landscape show up as portrait on the site eventually.

It's addressed easily enough with some shell scripting but it would definitely be more convenient to not have to do manually.

🦄 ❯ ~/foto preview
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x405668]

goroutine 1 [running]:
github.com/waynezhang/foto/internal/indexer.buildImageSets.func1({0x40000a82b8, 0x12}, {0x0?, 0x0?}, {0x40000ed818?, 0x405408?})
/home/runner/work/foto/foto/internal/indexer/indexer.go:71 +0x28
path/filepath.WalkDir({0x40000a82b8, 0x12}, 0x40000ed878)
/opt/hostedtoolcache/go/1.21.5/x64/src/path/filepath/path.go:530 +0x50
github.com/waynezhang/foto/internal/indexer.buildImageSets({0x40000a82b8, 0x12}, 0x0, {0x40000ed9b8?, 0x40000ed928?})
/home/runner/work/foto/foto/internal/indexer/indexer.go:70 +0xb4
github.com/waynezhang/foto/internal/indexer.Build({0x40000a42d0, 0x2, 0x0?}, {0x0?, 0x0?})
/home/runner/work/foto/foto/internal/indexer/indexer.go:54 +0x20c
github.com/waynezhang/foto/internal/cmd.preview(0x4000180200?, {0x57d042?, 0x4?, 0x57d046?})
/home/runner/work/foto/foto/internal/cmd/preview.go:35 +0x9c
github.com/spf13/cobra.(*Command).execute(0x40001b4600, {0x9f47e0, 0x0, 0x0})
/home/runner/go/pkg/mod/github.com/spf13/[email protected]/command.go:987 +0x828
github.com/spf13/cobra.(*Command).ExecuteC(0x40001b4900)
/home/runner/go/pkg/mod/github.com/spf13/[email protected]/command.go:1115 +0x344
github.com/spf13/cobra.(*Command).Execute(...)
/home/runner/go/pkg/mod/github.com/spf13/[email protected]/command.go:1039
github.com/waynezhang/foto/internal/cmd.Execute()
/home/runner/work/foto/foto/internal/cmd/root.go:38 +0x1b8
main.main()
/home/runner/work/foto/foto/main.go:8 +0x1c

🦄 ❯ foto version
foto v1.2.1+a96a5e3

🦄 ❯ uname -por
5.15.93-rockchip64 aarch64 GNU/Linux

Any thoughts?
I can supply a trace if needed

First I want to say - awesome project! Very simple and I appreciate the ability to customize.

Is lozad working properly for you? I have only tested on my localhost but all images are loaded almost immediately, and in a glitchy manner. It appears like images are fighting for placement as they load. I see the same/similar behavior on firefox, chrome and webkit based browsers, all running in linux.

I should state I have about zero web development experience. If you have any tips on debugging - or anyway I can get you some useful logs please let me know.

Thanks for your time!