spf13

spf13

13x engineer • @golang Product Lead @Google • Prior EVP @Docker, @MongoDB, @Drupal board • @gohugoio, Cobra & spf13-vim creator

Member Since 12 years ago

@Google, NYC

Experience Points
1.11w
follower
Lessons Completed
78
follow
Lessons Completed
794
stars
Best Reply Awards
102
repos

81 contributions in the last year

Pinned
⚡ The Go programming language
⚡ The world’s fastest framework for building websites.
⚡ The ultimate vim distribution
⚡ A Commander for modern Go CLI interactions
⚡ Go configuration with fangs
⚡ A FileSystem Abstraction System for Go
Activity
Jan
15
4 days ago
push

spf13 push spf13/dotfiles

spf13
spf13

adding some additional mac programs & zsh path

commit sha: 6b12bc8bddd8958fe52b291ad76daae6fd237976

push time in 3 days ago
Dec
22
4 weeks ago
Activity icon
issue

spf13 issue comment mikelawrence/aiosenseme

spf13
spf13

feat: support smartmode params

In support of: https://github.com/mikelawrence/senseme-hacs/issues/33

Adds support for setting and reading smartmode parameters

spf13
spf13

I tried that approach and if I remember correctly it wanted me to remove the mikelawrence one first, which meant removing all of my devices and setting them all up again. Is there a way to do that without removing the mikelawrence one first?

Message ID: @.***>

Dec
21
4 weeks ago
started
started time in 4 weeks ago
Dec
17
1 month ago
push

spf13 push spf13/dotfiles

spf13
spf13

adding additional install packages

commit sha: bd11f3803cfc5dbd259e05ada4da13f95b57a743

push time in 1 month ago
Dec
16
1 month ago
Activity icon
issue

spf13 issue estruyf/vscode-front-matter

spf13
spf13

Issue: front matter is case sensitive

After a good amount of troubleshooting I found that the reason that several hundred of my articles were missing from the dashboard and the editing window was that front matter expects all fieldnames to be all lowercase or at least case sensitive.

Hugo doesn't have this requirement and it took me a long time to notice that the initial caps used in some front matter was causing FrontMatter to not parse the articles at all.

I'm not sure if this is a bug or not, but the behavior was surprising especially since it worked differently than Hugo does.

Activity icon
issue

spf13 issue comment estruyf/vscode-front-matter

spf13
spf13

Issue: front matter is case sensitive

After a good amount of troubleshooting I found that the reason that several hundred of my articles were missing from the dashboard and the editing window was that front matter expects all fieldnames to be all lowercase or at least case sensitive.

Hugo doesn't have this requirement and it took me a long time to notice that the initial caps used in some front matter was causing FrontMatter to not parse the articles at all.

I'm not sure if this is a bug or not, but the behavior was surprising especially since it worked differently than Hugo does.

spf13
spf13

I wrote a quick script to lower initial case my front matter keys, so closing this but agree that a diagnostics feature would be broadly helpful

Dec
12
1 month ago
started
started time in 1 month ago
Dec
7
1 month ago
push

spf13 push spf13/dotfiles

spf13
spf13

zoxide working on windows, add delta to win install

commit sha: 2058c9ee448a8c3fbe3e1d82ab0194ba30ca8590

push time in 1 month ago
Activity icon
issue

spf13 issue comment ajeetdsouza/zoxide

spf13
spf13

Parse error on initialization - zsh & windows

The error I get is:

(eval):43: parse error near 'elif'

Using windows w/ zsh 5.8 (x86_64-pc-msys)

Tried using the POSIX initialization with the same result.

zoxide v0.7.9

spf13
spf13

Thank you, that worked well enough.

Dec
6
1 month ago
started
started time in 1 month ago
Dec
4
1 month ago
Dec
3
1 month ago
push

spf13 push spf13/dotfiles

spf13
spf13

Putting the readme in the right place

commit sha: 91c2faa6057ee6904e63db6fc46f7078d5f5de8f

push time in 1 month ago
Activity icon
fork

spf13 forked renemarc/dotfiles

⚡ ~/. Cross-platform, cross-shell configuration files. ⚙️💻
spf13 MIT License Updated
fork time in 1 month ago
started
started time in 1 month ago
push

spf13 push spf13/dotfiles

spf13
spf13

Add warning to PowerShell Profile

commit sha: 7b4ad01ce8726ae4fa0c52bb186dda801c431df9

push time in 1 month ago
push

spf13 push spf13/dotfiles

spf13
spf13

Add warnings to files & powershell profile

commit sha: 3ce809cb72e998ff7cf5f662c6d64b6d3033ad65

push time in 1 month ago
Activity icon
issue

spf13 issue ajeetdsouza/zoxide

spf13
spf13

Parse error on initialization - zsh & windows

The error I get is:

(eval):43: parse error near 'elif'

Using windows w/ zsh 5.8 (x86_64-pc-msys)

Tried using the POSIX initialization with the same result.

push

spf13 push spf13/dotfiles

spf13
spf13

getting it all working on windows with zsh

commit sha: 5419a5503102c6965029262dec14d47405b3d61c

push time in 1 month ago
started
started time in 1 month ago
Activity icon
fork

spf13 forked alexsarmiento/gitportable-pacman

⚡ Script to install pacman in git for Windows portable
spf13 Updated
fork time in 1 month ago
Dec
1
1 month ago
Activity icon
issue

spf13 issue comment fwestenberg/reolink_dev

spf13
spf13

Motion Sensors do not work - Usually Unavailable

Hi,

Can't get the sensors to operate. Connected via RLN16-410 NVR with the latest firmware 3.0.0.148. Cameras are RLC-810A and RLC-820A with the latest firmware 3.0.0.494. Have set internal URL, and enabled ONVIF on the NVR.

In the log I can see the following: Logger: reolink.subscription_manager Source: /usr/local/lib/python3.9/site-packages/reolink/subscription_manager.py:103 First occurred: 18:57:00 (126 occurrences) Last logged: 19:02:00

Subscription process ended with wrong HTTP status: 400: Bad Request

And the following: Logger: custom_components.reolink_dev.base Source: custom_components/reolink_dev/base.py:376 Integration: Reolink IP camera (documentation, issues) First occurred: 18:57:00 (42 occurrences) Last logged: 19:02:00

Host 192.168.1.248 error renewing the Reolink subscription

Occasionally, I can see some data from the sensors, but these are mostly unavailable.

What I could be missing? What additional information/log can I provide?

Thanks.

spf13
spf13

@bfeige or @Fannangir can you share the configuration you used as you described? Sounds like it's the way to go.

Activity icon
issue

spf13 issue comment mikelawrence/aiosenseme

spf13
spf13

feat: support smartmode params

In support of: https://github.com/mikelawrence/senseme-hacs/issues/33

Adds support for setting and reading smartmode parameters

spf13
spf13

I'd really like to use this functionality and understand that @mikelawrence isn't active right now.

Is there an easy way to use @barlock's fork from home assistant? I've been searching in the docs and via Google and I'm not seeing any way to do this without uninstalling the integration and then installing from another source, but doing that would require removing all my integrations.

Or alternatively would @mikelawrence be willing to add @barlock as a maintainer to help move this project forward a bit?

I'm happy to help with the occasional review if that helps.

Nov
30
1 month ago
Activity icon
issue

spf13 issue comment spf13/cobra

spf13
spf13

Support subcommands checking for suggestions

Resolves #636 Resolves #834 Resolves https://github.com/alexellis/arkade/issues/525

Till now, only the root command looked for suggestions. Now findSuggestions works for nested commands as well.

For example

Error: unknown command "rewin" for "root times"

Did you mean this?
	rewind

Run 'root times --help' for usage.
spf13
spf13

I hadn't considered the breaking change this would introduce.

I disagree that changing undocumented behavior is ok. The code implicitly is the documentation. It's hard to say someone has done something wrong when it worked for them.

I agree with @marckhouzam

Maybe a backwards-compatible approach can be defined? At a minimum an opt-in solution would be backwards-compatible, but there may be something even better; I haven't looked into it myself.

I think we should consider how large the impact this is. If Helm is expecting the current behavior still and others are as well we can take 3 approaches.

  1. Make this functionality opt in.
  2. Make this the default functionality but provide an opt in for folks wanting to use the legacy behavior (a simple path to working with the fix in place)
  3. Wait a release, put some notice / warning in this release that this will change in the next release and since it's a bugfix, it's not a "new version" change.
push

spf13 push spf13/dotfiles

spf13
spf13

adding macInitialization script

commit sha: c64d826299e77573b4278fa4af3d9842ed913930

push time in 1 month ago
started
started time in 1 month ago
Activity icon
created branch

spf13 in spf13/dotfiles create branch main

createdAt 1 month ago
Activity icon
created repository

spf13 in spf13/dotfiles create repository

createdAt 1 month ago
started
started time in 1 month ago
started
started time in 1 month ago
Previous