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

Lazy load sources #59

Closed
wants to merge 7 commits into from
Closed

Lazy load sources #59

wants to merge 7 commits into from

Conversation

gbjk
Copy link
Contributor

@gbjk gbjk commented Sep 7, 2014

Same as jhthorsen's original PR.
Rebased and fixed for changes since.

I'll be going through testing of this in the coming week.

Jan Henning Thorsen and others added 5 commits September 5, 2014 18:21
  All tests successful.
  Files=94, Tests=20844, 25 wallclock secs
  Result: PASS

  All database related tests was skipped when running this test suite.
  All tests successful.
  Files=94, Tests=20848, 51 wallclock secs
  Result: PASS
@jhthorsen
Copy link

See also #32 for old discussion.

@gbjk
Copy link
Contributor Author

gbjk commented Sep 7, 2014

Tests failing in new and exciting ways.

I'll work on fixing them, so this can be merged.

Not ignoring, either, riba's comment that this can't be merged until the substrate it's landing in is settled, unless we accept responsibility for ensuring it works both before and after significant changes in the undergrowth it's trying to live in.

Checking the file simply won't work, but even if it would, this wasn't the module name.
The source_registrations gives us a better handle on "has this been vivified or not"
Also noted that it's after namespace autoclean!
@mcsnolte
Copy link

👍 for this feature 😄

@mcsnolte
Copy link

@gbjk did you have any more ideas on how to make this work? Thanks

@gbjk
Copy link
Contributor Author

gbjk commented Dec 15, 2015

I stopped sniffing at this as it felt like the substrate we'd built upon was unsettled.
I think if I recall correctly the issue was that we built this on a branch that didn't end up getting folded into a release at the time. I checked months later, and it still hadn't happened.
I think I need to touch base with @ribasushi about this. I would have done so at LPW but I was unfortunately not able to attend. I'll grab him some time soon to discuss.

For what it's worth, we've actually been running this in production for well over a year now.

@mcsnolte
Copy link

Nice! Thanks for the update @gbjk

@ribasushi
Copy link
Collaborator

Am busy getting things into shape for 0.082830. Will make sure to post an update / future plan / holdup description for my successor before I sign off.

@gbjk
Copy link
Contributor Author

gbjk commented Sep 26, 2023

StaleAF.

@gbjk gbjk closed this Sep 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants