profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/yagebu/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

beetbox/beets 10411

music library manager and MusicBrainz tagger

beancount/fava 1088

Fava - web interface for Beancount

beancount/fava-plugins 17

A collection of Beancount plugins

aumayr/fava-electron 3

Electron-wrapper for fava

yagebu/tree-sitter-beancount 3

tree-sitter grammar for Beancount

yagebu/dotfiles 1

my dotfiles

yagebu/asus-fancontrol 0

Asus UX31A fan speed regulation

yagebu/beancount 0

Official Beancount repository.

yagebu/fava 0

fava - Web interface for beancount

push eventbeancount/fava

Jakob Schnitzer

commit sha 05d553990fd10e8d11f26acf11e6160e223e969a

Update gh-pages

view details

push time in 3 days

push eventbeancount/fava

Jakob Schnitzer

commit sha a6d5bf4cf6ecdb3c8811ffa81c85dd534a6805e0

update changes

view details

push time in 3 days

created tagbeancount/fava

tagv1.20.1

Fava - web interface for Beancount

created time in 3 days

delete branch yagebu/fava

delete branch : fix-translations-frontend

delete time in 3 days

push eventyagebu/fava

Jakob Schnitzer

commit sha b49d054086d1bb4bc5818252f279a790286ff3f9

fix loading of translations in frontend

view details

push time in 3 days

PR merged beancount/fava

fix loading of translations in frontend

<!-- Hi, thank you for opening a PR!

Please ensure that your change passes tests and the various linters by running make test and make lint. If testable, your changes should be covered by unit tests.

Explain your changes below and link to related issues. -->

+24 -16

0 comment

5 changed files

yagebu

pr closed time in 3 days

push eventbeancount/fava

Jakob Schnitzer

commit sha b49d054086d1bb4bc5818252f279a790286ff3f9

fix loading of translations in frontend

view details

push time in 3 days

PR opened beancount/fava

fix loading of translations in frontend

<!-- Hi, thank you for opening a PR!

Please ensure that your change passes tests and the various linters by running make test and make lint. If testable, your changes should be covered by unit tests.

Explain your changes below and link to related issues. -->

+24 -16

0 comment

5 changed files

pr created time in 3 days

create barnchyagebu/fava

branch : fix-translations-frontend

created branch time in 3 days

issue commentlektor/lektor

Project future

The deploy.yml for lektor-website implies that there were (at least at one time, or in planning) secrets configured for the repo which allowed publishing updates to the website. If those don't currently work, can we fix them?

I think those secrets are for the (attempted) GH pages deployment. I believe the working secrets for getlektor.com were only on the now defunct travis-ci.org. It seems to me that for getting deployments to flow.srv.pocoo.org and hence getlektor.com working again, we only need to have those secrets added to the GH repo.

goanpeca

comment created time in 3 days

issue openedlektor/lektor

fix flaky windows test

The CI tests that try to install the (non-Python) dependencies imagemagick and ffmpeg fail pretty regularly when trying to install those two packages with chocolatey. This seems to happen most often due to the imagemagick URL 404ing on us as far as I can tell. These steps are currently allowed to fail (which means that the parts of Lektor relying on those tools are not consistently tested on Windows), since those failures are not highlighting any problems in Lektor itself.

However, it would be nice if Windows didn't exist we could get consistent tests on Windows as well. winget as an alternative package manager was suggested in #933, that might be worth a shot (it doesn't have ffmpeg but then the ffmpeg install doesn't seem as problematic with chocolatey).

created time in 3 days

PullRequestReviewEvent

delete branch yagebu/fava

delete branch : makefile-adjustments

delete time in 4 days

push eventyagebu/fava

Jakob Schnitzer

commit sha da663e07b139ec172dc9a54307c84aa3716e0256

setup: add project_urls

view details

Jakob Schnitzer

commit sha 6adac24902c6c4c2583b69c4d3ccf33bb6713c12

makefile: use find to get all deps

view details

push time in 4 days

PR merged beancount/fava

makefile: use find to get all deps

<!-- Hi, thank you for opening a PR!

Please ensure that your change passes tests and the various linters by running make test and make lint. If testable, your changes should be covered by unit tests.

Explain your changes below and link to related issues. -->

+13 -8

0 comment

2 changed files

yagebu

pr closed time in 4 days

push eventbeancount/fava

Jakob Schnitzer

commit sha 6adac24902c6c4c2583b69c4d3ccf33bb6713c12

makefile: use find to get all deps

view details

push time in 4 days

push eventyagebu/fava

Jakob Schnitzer

commit sha 6adac24902c6c4c2583b69c4d3ccf33bb6713c12

makefile: use find to get all deps

view details

push time in 4 days

PR opened beancount/fava

makefile: use find to get all deps

<!-- Hi, thank you for opening a PR!

Please ensure that your change passes tests and the various linters by running make test and make lint. If testable, your changes should be covered by unit tests.

Explain your changes below and link to related issues. -->

+13 -8

0 comment

2 changed files

pr created time in 4 days

create barnchyagebu/fava

branch : makefile-adjustments

created branch time in 4 days

push eventyagebu/lektor

Jakob Schnitzer

commit sha 5b7372279001bc11b3ba1f05c95fdda53d3d849a

readme: remove node badge

view details

Jakob Schnitzer

commit sha 66e29b3f144281c56010bc1f8b114e25e9aa1264

frontend: require at least node 14

view details

Jakob Schnitzer

commit sha c885070586daf227509be6b879e368476b80e677

Merge pull request #940 from yagebu/bump-node-requirement frontend: require at least node 14

view details

Jakob Schnitzer

commit sha c435316768e9456dceb013d5dec22c2a2b582cbd

rewrite Sidebar with hooks

view details

Jakob Schnitzer

commit sha ed7874cd0b29d0ee1083ca9032157470719a111e

AddAttachmentsPage: rewrite with hooks

view details

Jakob Schnitzer

commit sha 9ef9807f332b79c3b87e4ad37331f3dcdabcc044

BreadCrumbs: rewrite with hooks

view details

Jakob Schnitzer

commit sha 549c40dcdae005ef1d7d8accb8ab0524765bf4d0

ServerStatus: rewrite with hooks

view details

Jakob Schnitzer

commit sha 6f09304a5d8ba282c0221322ba37a6ae51329b1a

AddChildPage: rewrite with hooks

view details

Jakob Schnitzer

commit sha 5cbba63ed6a0bf75151c4164a4b34d7f67b9d12b

DeletePage: rewrite with hooks

view details

Jakob Schnitzer

commit sha 862b05e8940f45f4bb250988757eeb4a761ea928

FindFiles: rewrite with hooks

view details

Jakob Schnitzer

commit sha 31acccb83504f4ca6c6692fcf41914cd2fa422e6

Publish: rewrite with hooks

view details

Jakob Schnitzer

commit sha 58f5353b3273e6a54defbe7b71fed123abaa7cdd

PreviewPage: rewrite with hooks

view details

Jakob Schnitzer

commit sha 61cb398ccccbfc9834fc1d62b351622d10926f8b

EditPage: rewrite with hooks

view details

Jakob Schnitzer

commit sha 841dbb096eaa504a6e27ae6417a35ce6a98552c4

CheckBoxesWidget: rewrite with hooks; move serialisation inside

view details

Jakob Schnitzer

commit sha f7d6b81f3f12c7318ec42fb1f480934e87c40dab

BooleanInputWidget: rewrite with hooks

view details

Jakob Schnitzer

commit sha f4e84044b0c11a8ea6ede727cc856ae0e025881f

flow: split up into components, better memoization, use hooks

view details

push time in 6 days

push eventyagebu/lektor

Jakob Schnitzer

commit sha 5b7372279001bc11b3ba1f05c95fdda53d3d849a

readme: remove node badge

view details

Jakob Schnitzer

commit sha 66e29b3f144281c56010bc1f8b114e25e9aa1264

frontend: require at least node 14

view details

Jakob Schnitzer

commit sha c885070586daf227509be6b879e368476b80e677

Merge pull request #940 from yagebu/bump-node-requirement frontend: require at least node 14

view details

push time in 6 days

delete branch yagebu/lektor

delete branch : bump-node-requirement

delete time in 6 days

push eventlektor/lektor

Jakob Schnitzer

commit sha 5b7372279001bc11b3ba1f05c95fdda53d3d849a

readme: remove node badge

view details

Jakob Schnitzer

commit sha 66e29b3f144281c56010bc1f8b114e25e9aa1264

frontend: require at least node 14

view details

Jakob Schnitzer

commit sha c885070586daf227509be6b879e368476b80e677

Merge pull request #940 from yagebu/bump-node-requirement frontend: require at least node 14

view details

push time in 6 days

PR merged lektor/lektor

frontend: require at least node 14

Only test on node 14 (and also 16 on linux). The node 12 tests on Windows were disabled a while ago due to some intermittent failures, so it's better to just bump the requirement in general. The engines setting in package.json should result in a warning/error on older node versions.

Also, remove the (very outdated) node badge from the README, I find it odd to list it there since it's just a build dependency basically.

+8 -8

0 comment

4 changed files

yagebu

pr closed time in 6 days

issue commentlektor/lektor

Project future

I would guess that dropping support for Python < 3.5 is "breaking" enough that the next release (after 3.2.x) should be 4.0 (assuming that we are committed to SemVer.)

IMHO dropping Python 2 (or early Python 3 users) is not a breaking change according to semver and thanks to python_requires (at least how I understand it should work) it shouldn't really be breaking in any other sense to Python 2 users, right? They'll just never "see" that package being installed by their package manager.

What other breaking changes are being considered?

Mainly the deprecation cleanups that I've added to the corresponding milestone. And I'd really want the website to work again before we announce a major release (I've asked around for getting deployments to work again, but getting those accesses worked out might just take some time).

goanpeca

comment created time in 6 days

push eventyagebu/lektor

Jakob Schnitzer

commit sha 68eef7801a25025e0f623509d5b086c493cd155f

makefile: remove build and dist dirs before building

view details

Jakob Schnitzer

commit sha 599b5d1d191a93f274fec00ce399e05572f4859c

changes for v3.2.2

view details

Jakob Schnitzer

commit sha 0fd7ab0761e7d6cee924d227c3c3b1587d909538

setup: set version to 4.0.dev for now

view details

Jakob Schnitzer

commit sha 8f56a7f49891f246a157b73ef0edfe2d37302b11

packages: avoid editable install

view details

Jakob Schnitzer

commit sha 9f89cd2dcd0dd3703726bc726de2f2ddfac4952c

packages: use format string to create requirement specifier

view details

Jakob Schnitzer

commit sha 39cffb4883c839f9876a0d2249de9d842b701537

packages: always reinstall local packages for now

view details

Jakob Schnitzer

commit sha 322ed64d10a1bf1afaaf7497e3ecdf9390e06512

packages: use more f-strings; add tests for manifest

view details

Jakob Schnitzer

commit sha f9b35d3e6058364b44d5b90c0879b025604d9276

packages: install packages in one go; use only one function

view details

Jakob Schnitzer

commit sha cb7420694488089ab9090d6f4efd69c825b88e24

packages: add unit test for list_local_packages

view details

Jakob Schnitzer

commit sha a46e9252493788c653b7478e1a56aadbd2c5a3ba

packages: add function to get hash of directory

view details

Jakob Schnitzer

commit sha b26b092a66974d9c1896a7c8c0010da10caf1eb0

packages: use checksums to determine need of install of local packages

view details

Jakob Schnitzer

commit sha 82ccb3bccf98e8401c1d7daedd14469291da7cc6

packages: explicit encoding

view details

Jakob Schnitzer

commit sha 8bdd82d5916bec0e90f5ef43e99134e5af5e902c

packages: call load_packages in background builder

view details

push time in 6 days

pull request commentlektor/lektor

Avoid editable installs

I'm with you that the --target option is the bigger culprit, but of the two problematic option it is the one we can't drop without creating an even bigger mess (installing packages into users current environment without their knowledge) or basically taking on re-implementing the complexity of pipenv or poetry to build a package manager into Lektor that can deal with the horrible mess that is Python packaging.

Would it be horrible to deprecate Lektor's plugin-installation features? At it's simplest, this would move away with automatic installation of stuff in the packages directory and the [packages] section of the project file, encouraging users instead to install plugins in whatever virtualenv is hosting their project's Lektor installation. Perhaps we could come up with a little sugar to help with that process — I haven't thought it through very completely.

Yes, please. The main reason for this PR is that I just had too much of my time wasted because some broken local package in lektor-website or the like broke my development Python environment for all Lektor projects. I just want to fix that horrible bug, then deprecate this whole mess and rip it out in a couple of years.

I'd suggest we recommend pipenv instead for people who want that "little sugar". I've recently moved all my (production) Lektor projects to pipenv and that has worked quite well. But that's really a topic for a new issue...

A way to disable/enable the use of specific plugins on a per-project basis (i.e. via the project file) would probably need to be added back. Thus different projects running off the same virtualenv could still use different sets of plugins.

This doesn't even work currently due to the editable installs ending up as system-wide or virtualenv-wide installs. In that case we should just recommend per-project virtualenvs or "pipenvs"/Pipfiles.

yagebu

comment created time in 6 days

pull request commentbeancount/fava

Add before_insert_entry hook

I don't know why the rebase/merge is failing.

Maybe try an interactive rebase against the main branch and remove all commits but yours.

And in any case, I don't see how that hook does anything yet (except being called, but then why have it in addition to the after_insert_entry hook). A test would also be good too.

pandu-rao

comment created time in 6 days

push eventbeancount/fava

Jakob Schnitzer

commit sha 6fbf3cd9ad5d3555f63ed6c9fb760263d227b98c

Update gh-pages

view details

push time in 6 days

created tagbeancount/fava

tagv1.20

Fava - web interface for Beancount

created time in 6 days